ManageSoft Element

This element contains all the information needed for connection to the central compliance database.

Examples

Running on the central application server in an on-premises implementation, using the database connection string specified in the registry, and executing separate updates without wrapping them in a single transaction for speed (as distinct from a single database transaction, where rollback is supported in the event of any failure to the updates):

<ManageSoft ConnectionType="ECM" RunInTransaction="False" />

In connected mode, when access is available to the central compliance database using Windows authentication, and the connection string has not been encrypted (the connection string attribute should be all on one line):

<ManageSoft AccountIsEncrypted="False"
    ConnectionString="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=FNMP;
    Data Source=WIN2K8SRV2"/> 

In disconnected mode, when the adapter is exercised on an inventory beacon with no access to the central compliance database:

<ManageSoft ConnectionType="Default" RunInTransaction="False" />

In connected mode, when access is available to the central compliance database but the connection string has been encrypted (which locks the adapter file to use on this same computer). The encrypted connection string has been shortened in this example for printing purposes.

  <ManageSoft ConnectionType="Specific"
      ConnectionString="1|2Y728ZndMMMpMwQMc...WikVzdsnJvxL"
      RunInTransaction="False" AccountIsEncrypted="True" />

Contains

<ManageSoft /> is an empty element, containing no child elements. (See attributes listed below.)

Contained by

<root> is the parent.

Supported attributes

AccountIsEncrypted

Mandatory. Boolean:

• True when the ConnectionString has been encrypted
• False when the ConnectionString is interpreted as plain text. (Use this value also in disconnected mode.)

For details about encrypting connection strings in an adapter XML file, see Command Line for Business Importer.

Note: The AccountIsEncrypted attribute is used by the Business Importer to determine whether the ConnectionString value is encrypted. Setting the value to false once the connection string has been encrypted results in a connection error when the Business Importer is run with this adapter file.

Tip: To remove encryption, you must do all of the following three things:

• Set AccountIsEncrypted to false.
• Replace the encrypted string value for ConnectionString with a valid plain text version.
• Repeat the plain text replacement for all other connection strings defined for each <Import> in the XML file. (The single use of the /Encrypt switch on the command line for the Business Importer also encrypts all ConnectionString values for each import object in the adapter XML file.)

ConnectionString

Defines the OLE-DB connection string to the central compliance database. This value may be plain text (when AccountIsEncrypted is False), or may contain unreadable character data when the connection string has been encrypted (AccountIsEncrypted is True). For details about encrypting connection strings in an adapter XML file, see Command Line for Business Importer.

The attribute is mandatory in connected mode (with access to the central compliance database) when ConnectionType is omitted or has the value Specific; and is forbidden in disconnected mode (where data must be written to an intermediate file on an inventory beacon for subsequent upload and import).

The unencrypted form of the connection string value depends on which type of authentication is used to connect to the central SQL Server database:

• For Windows authentication:

  ConnectionString="Integrated Security=SSPI;Persist Security 
  Info=False;Initial Catalog=databaseName;Data Source=SQLServerName"

• For SQL authentication:

  ConnectionString="Password=SQLPassword;Persist Security Info=True;User 
  ID=SQLAccount;Initial Catalog=databaseName;Data Source=SQLServerName"

In either case, substitute your values for the following placeholders as required:

• SQLServerName — The server name or IP address (or dot for connection on the current server) of the SQL Server hosting the central compliance database. Using the server name requires that a DNS is accessible and operating, to resolve the server name.
• databaseName — The name of the central compliance database. (In a default installation, this database name is commonly FNMSCompliance; or in an upgraded implementation, it may be ManageSoft.)
• SQLAccount — The user name (or account) permitted access to the central compliance database.
• SQLPassword — The password for the above account, needed to complete the credentials for accessing the compliance database.

Tip: If you do not wish to type in a value for ConnectionString, you can build a connection string using a UDL file. For more information, see Validating Connection Strings.

ConnectionType

Optional. Defines the method for determining the connection. Valid values are:

• Default or Specific — One of these synonyms is the only permitted value when the Business Importer is running on an inventory beacon in disconnected mode (Default may be best practice here, being easier to understand in the context). In this case, no ConnectionString can be provided, since there is no connection to the target database. For an on-premises implementation, when the adapter is running in connected mode on an application server, either of these values requires that the ConnectionString value is used to connect to SQL Server to access the operations databases.
• ECM — The ConnectionString value is ignored, and connection is made using the details stored in the registry at HKLM\SOFTWARE\ManageSoft Corp\ManageSoft\Reporter\CurrentVersion\DatabaseConnectionString. This registry is only populated (and the ECM value is only valid) when the Business Importer is running on the central application server for FlexNet Manager Suite, in an on-premises implementation.

RunInTransaction

Optional. Boolean:

• True — All imports run from this adapter XML file are wrapped as a single transaction in the central database. This allows for transaction roll-back in the event of any difficulties.
• False — Data transactions (insert, update or delete) on the central compliance database are actioned individually. This reduces the risk of issues around table locking during business imports disrupting other processes.

When this attribute is not specified, the default depends on where the adapter is running:

• In an on-premises implementation when the Business Importer is running on the central application server, the default is True.
• For adapters created in disconnected mode on an inventory beacon, RunInTransaction is set to false.