Setting up runtime utilities on Apache ActiveMQ Artemis

Apache ActiveMQ Artemis 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 Artemis.

If you are using the Apache ActiveMQ Artemis JMS, use the <INSTALL_DIR>/bin/install3rdparty.sh script to install the artemis-jms-client-all-2.6.0.jar file and include it in the AGENTDynamicclasspath.cfg and the APPDynamicclasspath.cfg dynamic class path file.
Command to add the install3rdparty.sh syntax to AGENTDynamicclasspath.cfg:
```
install3rdParty.sh activemq 2_6_0 -j ${ARTEMIS_HOME}/lib/client/artemis-jms-client-all-2.6.0.jar -targetJVM AGENT
```
Command to add the install3rdparty.sh syntax to APPDynamicclasspath.cfg:
```
install3rdParty.sh activemq 2_6_0 -j ${ARTEMIS_HOME}/lib/client/artemis-jms-client-all-2.6.0.jar -targetJVM APP
```
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 artemis_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.