Legacy platform

Setting up runtime utilities on Apache ActiveMQ

Apache ActiveMQ JMS requires the jars that are listed here.

Note: The class path information that is provided in this section is intended as a starting point for your implementation. Depending upon the JMS, JNDI, and JDK that you are using, you might need to add or remove the JAR files from the list that is given here.
Complete the following steps for setting up runtime utilities on Apache ActiveMQ.
  1. If you are using the Apache ActiveMQ JMS, use install3rdparty.sh to include the following files from ActiveMQ_HOME/lib in the AGENTDynamicclasspath.cfg or the APPDynamicclasspath.cfg.
    • activemq-client-5.15.8.jar
    • geronimo-j2ee-management_1.1_spec-1.0.1.jar
    • geronimo-jms_1.1_spec-1.1.1.jar
    • hawtbuf-1.11.jar
  2. You must configure the jndi.properties file and it must be accessible for the Sterling Order Management System Software application. The best way is to add the jndi.properties file to a custom JAR file such as activemq_custom.jar and then add it to the class path. For more information, see Configuring a jndi.properties file.
Note: If you get the javax.naming.NamingException, it means that the jndi.properties file is not accessible. Ensure that the jndi.properties file is packaged in a custom JAR and is installed as a third-party JAR for both APP and AGENT dynamic class paths.