Upgrading from ebXML Module 6.0.1

1. Back up your existing ebXML Module 6.0.1 installation and all custom packages that are used by ebXML Module 6.0.1.

2. Export the ebXML Module 6.0.1 Trading Networks profiles, custom ebXML Document Types, custom processing rules, and TPAs, from Trading Networks 6.5. For instructions, see the webMethods Trading Networks User’s Guide for your release.

3. If you are running earlier, unsupported version of Integration Server and Trading Networks, upgrade to supported versions. For instructions, see the Upgrading Software AG Products for your release.

4. Start Integration Server.

5. Note the actions defined for each ebXML Module 6.0.1 processing rules. Using Trading Networks, remove all ebXML Module 6.0.1 processing rules manually.

6. Copy the ebXML Module 6.0.1 custom packages and all other packages that depend on the ebXML Module 6.0.1 from the backup directory to the Integration Server_directory \packages directory.

Important:
Do not copy the WmebXML package or the WmebXMLSample package from ebXML Module 6.0.1, because these packages will not work with the Integration Server versions that ebXML Module 7.1 SP1 supports.

7. Shut down the Integration Server.

8. Install webMethods ebXML Module 7.1 SP1. For instructions, see Installing ebXML Module 7.1 SP1.

9. Update the ebXML Module 7.1 SP1 config.cnf file in the WmebXML\config directory with applicable settings from the equivalent ebXML Module 6.0.1 file. Some of the properties in the ebXML Module 6.0.1 configuration file are not applicable for ebXML Module 7.1 SP1. For information on the revised properties, see the webMethods ebXML Module7.1 SP1readme.

10. Start the Integration Server.

11. Verify the migration of the Trading Networks database from Trading Networks 6.5 to the supported version. To do so, start the Trading Networks Console and make sure the ebXML TN document types, ebXML processing rules (including the custom processing rules) and TPAs were migrated successfully. If the migration was not successful, import the ebXML Trading Networks profiles, document types, processing rules, and TPAs from the export file created in step 2 into Trading Networks. For instructions, see the webMethods Trading Networks Administrator’s Guide for your release.

12. Verify the ebXML Module 7.1 installation, as described in Installing ebXML Module 7.1 SP1.

13. Update the following, if applicable:

Custom services that were dependent on theebXML Module 6.0.1 built-in services with the ebXML Module 7.1 SP1 built-in services.

TN document types that were dependent on the ebXML Module 6.0.1 TN document types (for example, custom services, process models) with ebXML Module 7.1 TN document types.

ebXML Module 6.0.1 TPAs to ebXML Module 7.1 TPAs by invoking the wm.ip.ebxml.util:migrateTPA service. For information about the parameters for this service, see Built-In Services.

14. Make sure the ebXML Module 7.1 SP1 can successfully exchange a ping message with its Trading Partners. For instructions, see Initiating the ebXML Module Handshake.

15. Update ebXML Module 6.0.1 services that use the ping, route, send, and status services to use the services provided in ebXML Module 7.1, as follows:

Update your ebXML Module 6.0.1 services that use....	To use these ebXML Module 7.1 services
ping	pingUsingTPA
route	routeUsingTPA
send	sendUsingTPA
status	statusUsingTPA

16. For information about ebXML Module 7.1 SP1 services, see Built-In Services.

17. Verify the services that theebXML Module provides by exchanging the ebXML messages with the trading partners. For instructions, see Working with ebXML Messages.

Note:
The ebXML Module can exchange messages with any MSH that uses previous versions of the ebXML Module. This includes exchanging messages using the ebXML Message Service Version 1.0 Specification and ebXML Message Service Version 2.0 Specification.