Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Instructions to configure JMS for ADM in WAS

SA-19769

Summary



User has gone through DSM Installation guide and trying to configure JMS for Adaptive Decision Manager(ADM), they have mentioned that the steps mentioned in the DSM Installation document are not clear (page 22). Now, user is looking for the detailed information to setup their DSM.

Error Messages



Not Applicable

Steps to Reproduce



Try installing DSM by creating JMS Services on WebSphere Application Server by referring page 22 and 23 of DSM Installation guide

Root Cause



The DSM installation document does not provide detailed screen shot for JMS Service creation. WebSphere administrators should be able to create the JMS resources with the information provided in the DSM installation guide.

Resolution



Provided detailed step by step instructions to create the JMS services on WebSphere -

Create an unsecured Service Integration Bus (SIB) named ADM Bus.
  

  

 

In the ADM Bus, add the bus members corresponding to the nodes running ADM and PRPC. In the step for improving the messaging performance, it is advisable to accept the default settings for the JVM heap size.   
 

  

  

 


In the ADM Bus, create a new destination with the specifications listed below and save the changes to the master configuration.
• Destination type: topic space
• Identifier: ADMDestination

 

 



 


Go to the JMS providers facilities and select the messaging provider using the same scope as the ADM Bus SIB. In Additional Properties, select Topic Connection Factories, add a new connection factory using the specifications listed below and save the changes to the master configuration.

       • Name: ADM Request Connection Factory
       • JNDI name: jms/admRequestConnectionFactory
       • Bus name: ADM Bus
       • Durable subscription home: it should point to the host that is member of the bus (single server installation), or one member of the bus (cluster installation).
  

  

 

Back in the JMS provider, select the link to create a topic under Additional Properties, add a topic using the specifications listed below and save the changes to the master configuration.   
         • Name: ADM Topic
        • JNDI name: jms/admRequestDestination
        • Bus name: ADM Bus
        • Topic space name: ADMDestination
 

 
 
 

 
 
 


In the JMS provider, add a new activation specification using the details listed below and save the changes to the master configuration

          • Name: ADM Activation Specification
          • JNDI name: jms/admActivationSpecification
          • Destination type: topic
          • Destination JNDI name: jms/admRequestDestination
          • Bus name: ADM Bus
 
 


 

 
Deployment of the ADM EAR
  

 

 

Published February 15, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us