You are here:

Upgrading An Older DTS

Prior to Insight version 7.9.0, all connection configuration information was stored within the DTS that used the connection. Starting with Insight 7.9.0, connection configuration information is stored in a global pool of connections in the Scribe Internal Database, and each connection is available to any DTS created in the Workbench. The Console does not have access to Scribe Internal Database connection information for publishers or reports.

Information that defines the connection to a data source, such as the database name on the data source, is saved in the Scribe Internal Database. If that connection information changes, when you open and run any other DTS file that uses that connection, you do not need to change the DTS to enable it to use the modified connection information. Some connection types, such as SQL, Dynamics CRM, and Salesforce, include adapter-specific parameters as part of the connection. For more information, see the Adapter Help in the TIBCO Scribe® Insight Help Library.

Note:

Global connection information saved in the Scribe Internal Database includes the database name and server name used with that connection. If you modify this information, the updated database or server name is used by every DTS using that connection as a source or a target.

See Best Practices, below, for suggestions on how to prepare your DTS files for the most efficient upgrade.

Note:

A DTS file that contains a converted connection cannot be opened in version 7.8.0 or earlier of Insight.

Best Practices

If multiple DTS files use similar connections and you want to minimize the number of redundant connections defined when you convert, before you begin the upgrade process:

Back up existing DTS files — Save all of your DTS files before you convert the connections defined in those DTS files.
Compare the existing connections — Determine the connection properties that each DTS requires and identify DTS files that use similar connections. Then, as you upgrade one DTS file through the Workbench, direct Insight to convert matching connections in other DTS files that require the same type of connections.

Set a connection naming convention — Define a connection naming convention that indicates the information you use to differentiate a connection, such as the connection type and usage or properties. As you upgrade different DTS files and define new DTS files, you must be able to distinguish one connection from another to select the connection whose properties are best for each DTS.

Insight can cascade connection information to other DTS files during the upgrade process, identifying connections that match the original, unconverted connection name and have matching connection parameters, converting those connections, and renaming them in both the database and the other upgraded DTS files.

Note:

After a connection is converted, if you change the name of that connection while in a DTS, the connection is saved to the Scribe Internal Database with the new name. The new connection name is not saved to the DTS until you save the DTS. When you open another DTS file that uses the renamed connection, the new connection name is displayed in the Workbench, but the new name is not stored in the DTS until it is saved.