Upgrading from RosettaNet Module 6.0.1
Follow these steps to upgrade and migrate from RosettaNet Module 6.0.1 (and its related service packs) to RosettaNet Module 7.1 SP2.
To migrate... | Use... |
Document types, trading partner agreements, and partner profiles | Trading Networks migration scripts. |
Business process models | |
Packages, folders, and flow services | |
To migrate from
RosettaNet Module 6.0.1 to
RosettaNet Module 7.1 SP2
1. Back up the entire existing webMethods installation directory on each machine, and back up your webMethods databases as instructed by your RDBMS vendor.
2. Install RosettaNet Module 7.1 SP2 on a supported version of Integration Server. For installation instructions, see
Installing
RosettaNet Module 7.1
SP2. For a list of supported Integration Server versions, see webMethods eStandards Modules System Requirements. 3. Migrate Trading Networks document types, trading partner agreements, and partner profiles as described in Upgrading Software AG Products On Premises.
Important:
Do not migrate the PIP 0A1 related TPAs because in RosettaNet Module 7.1 SP2, NOF is handled within the PIP process model and does not require a separate process model.
4. Migrate RosettaNet Module 6.0.1 packages, folders, flow services, and process models as follows:
a. In Designer, import the RosettaNet business process models from RosettaNet Module 6.0.1 to RosettaNet Module 7.1 SP2 using a supported version of Designer (as noted in webMethods eStandards Modules System Requirements).
b. Copy the following to Integration Server_directory\packages directory.
The custom package that contains reference of WmIPRoot services.
The generated package of 6.0.1 process models.
In RosettaNet Module 6.0.1, Notification of Failure (NOF) documents were handled in a separate NOF (PIP 0A1) process model. In RosettaNet Module 7.1 SP2, NOF is handled within the PIP process model and does not require a separate process model. Due to this change, you must not migrate PIP 0A1 related TPAs, IS documents, TN XML documents types, and process models.
c. Build and upload the process models.
d. Use the
pub.estd.rosettaNet:migrate service to migrate the services from the package, generated when uploading the process model. In the service's listOfComponents input parameter, enter the package name. Similarly you can migrate your custom packages and services. e. Edit any custom services that reference the WmRNIF11TRP and WmRNIF20TRP packages to now point to the WmRosettaNet public folder. For example, change wm.ip.rnif11.util:getRNIF11Documents and wm.ip.rnif20.util:getRNIF20Documents to pub.estd.rosettaNet:getRNOMimePart.
Note:
See the nsMap.properties file, located in the WmRosettaNet package\migrate folder for a complete list of services that must be remapped to services in the WmRosettaNet and WmEstdCommonLib packages. Public services that were available in the WmRNIF20TRP and WmRNIF11TRP packages in RosettaNet Module 6.0.1 have been consolidated and moved to the WmRosettaNet package in RosettaNet Module 7.1 SP2. The WmRosettaNet package automatically selects the appropriate protocol-related details for RNIF 1.1 or RNIF 2.0, as governed by the TPA settings.
In RosettaNet Module 6.0.1, focal roles were set in the process models. As of RosettaNet Module 7.1, focal roles are defined in the Trading Partner Agreement associated with the process, as ProcessInfo/SenderFocalRole and ProcessInfo/ReceiverFocalRole, for the sender and receiver, respectively.
f. Restart the Integration Server.
5. In Designer, verify that the upgrade was successful by initiating the RosettaNet business process models. Verify that RosettaNet transactions complete successfully.