![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The EDI Migration tool is a command line tool used to migrate TIBCO BusinessConnect EDI Protocol powered by Instream configuration repository data from the release 5.x to the release 6.x.
• You cannot use this tool to migrate between TIBCO BusinessConnect EDI Protocol powered by Instream 6.x, such as from version 6.4 to 6.6. Use the normal TIBCO BusinessConnect configuration import from the GUI or from the tool BCAppManage.
• To migrate TIBCO BusinessConnect EDI Protocol powered by Instream 5.4.0 installed with TIBCO BusinessConnect 5.3.3 to TIBCO BusinessConnect EDI Protocol powered by Instream 6.x installed with TIBCO BusinessConnect 6.x, you must first migrate it to version 6.x installed with TIBCO BusinessConnect 5.3.3, and then migrate it to version 6.x installed with TIBCO BusinessConnect 6.x.To perform migration using the EDI Migration tool, the .csx file exported from the release 5.x is required. In addition, you have to configure the file path for this .csx file and the JDBC information for the target repository.
The EDI Migration tool is located in the BC_HOME\protocols\tibedi\tools\migration directory consists of the following files:
• edimigrator.exe Executable file to perform the migration
• edimigrator.tra This file contains various environmental and other variables to be set for using this tool.
• tibedimigration.jar .This is the executable JAR file for this tool.
• edimigator.log This file is generated after migration is performed and contains the migration logs.Steps for migrating TIBCO BusinessConnect EDI Protocol powered by Instream using this tool are explained in the Migration and Compatibility section in TIBCO BusinessConnect EDI Protocol powered by Instream Release Notes.After you run edimigrator.exe by using a command line, the following information is displayed:
Any transport URL information that was configured under Trading Partner > Enabled Protocol from the previous version of TIBCO BusinessConnect EDI Protocol powered by Instream will not be changed. This URL is the outbound URL that the protocol will communicate to the trading partner. If users require this information to be updated, they must use TIBCO BusinessConnect ConfigStore Management Interface Protocol to modify the URLs.The inbound URL for TIBCO BusinessConnect EDI Protocol powered by Instream requires the appropriate URI change for X12, Gateway, TEXT, TRADACOMS, and EDIFACT as mentioned in Exchanging URI Definitions, and this information must be indicated to their trading partners as a part of the URI information exchange.User-specific properties defined under System Settings> Activated Protocol Plug-ins and Properties> tibEDI will not be migrated to TIBCO BusinessConnect EDI Protocol powered by Instream version 6.x unless they are given by TIBCO Support, or are pertinent to the new conversion engine.To continue using these properties, users have to enter them manually under System Settings> Activated Protocol Plug-ins and Properties> tibEDI.Certain manual changes are required from users migrating from TIBCO BusinessConnect EDI Protocol 5.x to TIBCO BusinessConnect EDI Protocol powered by Instream Version 6.x and later:
− The package name of Service protocol interfaces has been changed to com.tibco.ax.tibedi.runtime.service and implementers of these interfaces need to refactor their code. The new protocol name is Service, rather than Service.
− TIBCO BusinessConnect EDI Protocol 5.x runtime table names have been changed from EDI_ to TIBEDI_ in TIBCO BusinessConnect EDI Protocol powered by Instream version 6.x and above. Users who depend on these table names for the Service protocol must change these names appropriately in their implementation.
• Users migrating from TIBCO BusinessConnect EDI version 5.x who had previously used custom scripts should change them manually to adapt to TIBCO BusinessConnect EDI Protocol powered by Instream version 6.x and later as follows:
− The package name of EDI-specific custom script object interfaces have been changed to com.tibco.ax.tibedi.runtime.transport and implementers of these interfaces need to refactor their code if they are using TIBCO BusinessConnect EDI Protocol powered by Instream version 6.x and later.
• Guidelines, schemas etc files under operations in the operations editor and under the operation bindings in business agreements are not migrated from 5.x to 6.x by using the EDI migration tool. Instead, users have to run explicitly the operations updater tool to upload these files after migration.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |