webMethods product | Post-Migration Configuration Task |
Universal Messaging | To enable Universal Messaging for JMS messaging, configure: JNDI namespace JMS destinations JMS clients For more information, see
Universal Messaging Configuration. |
Integration Server | To enable the connection between Integration Server and Universal Messaging for JMS messaging, configure: DEFAULT_IS_JNDI_PROVIDER alias or new JNDI provider alias DEFAULT_IS_JMS_CONNECTION alias or new JMS connection alias To enable webMethods Messaging, configure: Document Types Triggers For more information, see
Integration Server Configuration and
webMethods Messaging. |
Optimize | To enable Universal Messaging server discovery, data communication, asset discovery, and server monitoring, configure: JMS Server URL property Universal Messaging asset discovery For more information, see
Optimize Configuration. |
Process Engine | To enable Universal Messaging as the JMS server for publishing the audit messages to Optimize, configure the com.softwareag.eda.nerv.default.jms.provider property. For more information, see
Process Engine Configuration. |
Command Central | To enable centralized Universal Messaging administration and monitoring, configure Universal Messaging server installations and instances in Command Central. For more information, see Software AG Command Central Help. |
Designer | To enable design-time Universal Messaging destination management, JMS trigger creation, and JMS message mapping with the process models, configure the JMS triggers and process models to change the JMS connection alias. For more information, see webMethods Service Development Help and webMethods Integration Server Administrator’s Guide. |
Deployer | To enable Repository-based deployment, configure Deployer connection to the Universal Messaging server. For more information, see webMethods Deployer User’s Guide. |