webMethods Product Suite  | Complete Installation and Upgrade Information for Software AG Products | Upgrading Software AG Products | Migrate Software AG Designer, Business Process Runtime Data, and Closed Loop Analytics | Migrate Business Process Runtime Data
 
Migrate Business Process Runtime Data
Note: If you have running process instances that are based on a process model created before you upgraded, and you now want to regenerate that process model in the new Software AG Designer, change the version number of the process model to the next sequence number before regenerating it. If you do not do so, the process instances will not behave as expected. When you enable the new version of the process model for execution in My webMethods Server, you will be asked if you want to upgrade running processes; respond No.
Note: Steps for Microservices Runtime are identical to those for Integration Server.
1. If you migrated business process packages that were generated by users from Software AG Designer, make sure the packages exist in the new_Software AG_directory/IntegrationServer/instances/instance_name/packages directory. The package names are the project names or custom names you specified in Software AG Designer.
2. Open Integration Server Administrator and point to new Integration Servers that host Process Engines. Go to the Settings > JDBC Pools page and connect the ProcessEngine and ProcessAudit functions to their database components. For instructions, see Installing Software AG Products.
3. In Integration Server Administrator, go to the Package > Management page and click for the WmMonitor package.
4. If your old and new product installations are on different machines and you want to be able to resubmit processes and process steps that ran before you upgraded, follow the steps below.
If the new Integration Server that hosts Monitor is connected to a messaging product and has process model fragments, select the Resubmit to local IS check box, click Submit, and then reload the package.
If the new Integration Server that hosts Monitor is not connected to any messaging product and has no process model fragments, clear the Resubmit to local IS check box, click Submit, and then reload the package.
5. Go to the Settings > Messaging > webMethods Messaging Trigger Management page and make sure document retrieval is enabled for all webMethods Messaging triggers on new Integration Servers. For instructions, see webMethods Integration Server Administrator’s Guide.
Copyright © 2007-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.