webMethods Deployer 10.3 | webMethods Deployer Documentation 10.3 | Deploying a Project | Post-Deployment Tasks
 
Post-Deployment Tasks
*If you deployed JMS triggers, do the following:
1. Create the same JMS alias connections on the target Integration Servers that exist on the source Integration Servers. Then reload the packages that contain the triggers.
2. Enable the JMS triggers.
3. Configure the queue or topic for each JMS trigger on the message provider for the target Integration Servers.
For instructions, see Using webMethods Integration Server to Build a Client for JMS.
*If you deployed My webMethods Server rules, the order in which the deployed rules are resolved with the existing rules on the target servers might need modification. Review the rule order and modify as necessary.
*If you deployed a process that uses e-forms with the project property Enable process for execution set to No (see Creating a Project), the e-form listener associated with the process cannot be enabled on the target server and therefore the process cannot be triggered on the target server. To make the process triggerable on the target server, enable it for execution and then enable the e-form listener.

Copyright © 2013-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.