Starting in Data Exchange 5.0, multiple versions of Data Exchange (excluding DEMS) can be installed on the same Windows partition or transformation source host. For example, if you already have Data Exchange 4.0 installed, you can then install Data Exchange 5.0 on the same machines.
Now that multiple versions of Data Exchange can be installed on the same machine, it is possible to test a new version of Data Exchange without using an additional partition.
When installing the 5.0 version of Runtime Administration and Runtime Service, you can choose to create new internal databases with initialized data or with data copied from the 4.0 version of the database. If you choose to install with data copied from the 4.0 version of the database, then all the runtime information of the deployed transformations are copied to the new internal databases.
If you have tested the later version of Data Exchange on another partition and you want to run all the deployed transformations in 5.0 after the installation (the transformations will then no longer run in version 4.0), then choose the copy data option during installation.
If you want to test the later version of Data Exchange on the same partition before using it, then select the initialize data option during installation. You can migrate the tracking information from an earlier version of Data Exchange to the later version after the tests and verification of the operations of the later version are complete.
Testing the later version of Data Exchange on the same partition
To test a new version of Data Exchange on the same partition,
Export the transformation from DDW 4.0 and import it to DDW 5.0.
Redirect the target data store schema to a different target data store schema.
Deploy the transformation to the Administration site.
Open the Administration Site.
If you encounter a product version mismatch, click Troubleshoot, and then Edit Connection and update any or all of following connection settings for the current version of Data Exchange, as necessary:
Agent TCP Port
Runtime Service Host
Runtime Service TCP Port
This resolves the product version mismatch.
Start the transformation.
After you complete the tests for the later version, you can use the stored procedure to migrate the tracking data of the source data store from the earlier version to the later version, the procedure for which is explained in the below scenario.
Migrating a transformation post installation
You can migrate the transformation source from an earlier version of Data Exchange to the later version after the tests and verification of the operations of the later version are complete.
To do so,
Export the transformation from the DDW 4.0 and import it DDW 5.0.
Update the source and target schema.
Deploy the transformation to the Administration Site.
Using SQL Server Management Studio, inspect the contents of the later version of Tracking database table [dbo].[DataStoreMap] (eg. [UnisysDExchTrackingDB-5016].[dbo].[DataStoreMap]), and acquire the Identifier of the required source data store.
Using this Identifier, run the stored procedure [dbo].[RemoveBDTRecordsForSourceId] to remove all tracking information of the Bulk Data Transformation tests.
You can perform this using either of the following procedures:
Procedure 1:
Expand the tracking data store of the version 5.0.
Expand Programmability, and then expand Stored Procedures.
Right click [dbo].[RemoveBDTRecordsForSourceId] and select Execute Stored Procedure….
In the Execute Procedure dialog box, enter the Identifier of the source data store enclosed in single quotes.
Click OK.
Procedure 2:
Click New Query
Enter the following code:
USE [UnisysDExchTrackingDB-5016] GO DECLARE @return_value int EXEC @return_value = [dbo].[RemoveBDTRecordsForSourceId] @SourceIdentifier = '00000000-0000-0000-0000-000000000000' SELECT 'Return Value' = @return_value GO
Replace “[UnisysDExchTrackingDB-5016]” with the required tracking database and “00000000-0000-0000-0000-000000000000” with the Identifier of your source data store.
Execute the query.
Using the same Identifier and procedure as above, run the stored procedure [dbo].[RemoveCDTRecordsForSourceId] to remove all tracking information of the Changed Data Transformation tests.
Stop the transformation running in Data Exchange 4.0.
Using SQL Server Management Studio, inspect the contents of an earlier version of Tracking database table [dbo].[DataStoreMap] (eg. [UnisysDExchTrackingDB].[dbo].[DataStoreMap]), and acquire the Identifier of the required source data store.
Using this Identifier, run the stored procedure [dbo].[MigrateSourceFromRel4Dot0] in the tracking data store of the later version of Data Exchange.
You can perform this using either of the following procedures:
Procedure 1:
Expand the tracking data store of the version 5.0.
Expand Programmability, and then expand Stored Procedures.
Right click [dbo].[MigrateSourceFromRel4Dot0] and select Execute Stored Procedure….
In the Execute Procedure dialog box, enter the Identifier of the source data store enclosed in single quotes.
Click OK.
Procedure 2:
Click New Query
Enter the following code:
USE [UnisysDExchTrackingDB-5016] GO DECLARE @return_value int EXEC @return_value = [dbo].[MigrateSourceFromRel4Dot0] @SourceIdentifier = '00000000-0000-0000-0000-000000000000' SELECT 'Return Value' = @return_value GO
Replace “[UnisysDExchTrackingDB-5016]” with the required tracking database and “00000000-0000-0000-0000-000000000000” with the Identifier of your source data store.
Execute the query.
This transfers the tracking information of the selected source to the tracking database in the later version.
Open the Administration Site.
If you encounter a product version mismatch, click Troubleshoot, and then Edit Connection and update any or all of following connection settings, as necessary:
Agent TCP Port
Runtime Service Host
Runtime Service TCP Port
This resolves the product version mismatch.
Resume the transformation in the later version of Data Exchange.
Note: When you migrate a transformation to a later version and resume it in the later version , the transformation records of this transformation are disabled in the earlier version. Therefore, you will not be able to resume the transformation in the earlier version of Data Exchange. This avoids duplicate transformation runs in the two different versions of Data Exchange.