Migration: Updating Business-Document versions

Step 1: Importing new Business-Document versions

1. In the FEX installation package, navigate to the directory that contains the Business-Document repositories:
2. \Software\Repository\
2. Locate the sub-directory that contains the message type that you require, for example FIN.
3. Copy the three files (.bat, .sh, .zip) contained in the message directories to the machine where Composer is installed. Uncompress the .zip files.
4. Start Composer, and open a client session. Open the Integration workbench.
5. In the Integration-Services workbench, select Tools > Import Object.
6. Composer displays the Import Wizard.
6. In the Import Wizard, navigate to the file you uncompressed from the FEX installation package.
7. Select one or more Business-Documents to import.
8. Select Update the folder hierarchy.
9. Click Finish.
10. Composer generates a set of Business-Documents based on your selection and deposits them to a newly-created directory in the Mapping Manager tab.

Step 2: Updating Map-Broker associations

Business-Documents are linked as data holders to Map-Brokers. When you change the version of the Business-Document, you must then associate the new version with the Map-Broker in place of the old version.

Prerequisite

Import the new version of the Business-Document.

Procedure

1. In Composer, copy the existing Map-Brokers to a new directory.
2. Open the Map-Brokers in the properties window.
3. In the General tab, change the input Business-Document reference, replacing the old version with the new.
4. From the DecisionPath tab, open the Mapping Rule sub-tab and double-click the Mapping Rule step to open the Mapping Rule properties window.
5. In the Mapping Rule properties window, change the output Business-Document reference, replacing the old version with the new.
6. Save, check and close the object.
7. Recreate the Integration-Process that uses the Map-Broker, using the updated Map-Broker.
8. Recreate Integration-Tasks for any updated Integration-Processes.
9. Deploy the Integration-Task to an Integrator Server.
   • If the updated Integration-Task has Channels that use the same resources and same folders as the old version, first execute a Back to design command on the old version, then execute a Send to production command on the new version.
   • If the updated Integration-Task has Channels that do not use the same resources and same folders as the old version, execute a Send to production command on the new version, and then if required, execute a Back to design command on the old version.