A production SAS Fraud Management SAS OnDemand Decision Engine host can have more than one SAS OnDemand Decision Engine if you implement horizontal clustering of SAS OnDemand Decision Engines.

In another scenario, you can install and run several SAS Fraud Management environments or SAS OnDemand Decision Engines on a single, non-production environment.

In a SAS OnDemand Decision Engine host with multiple SAS OnDemand Decision Engines, you need to update the default Java Management Extension (JMX) Remote Method Invocation (RMI) port of SAS OnDemand Decision Engine to prevent port conflict.

Complete the following steps to update the SAS OnDemand Decision Engine JMX RMI port:

1. Stop SAS OnDemand Decision Engine by issuing the following command:
   ./ose.sh stop tail
   
   
2. Add the config.jmxPort property to the ose bean in the ose.xml file.
   

   <bean id="ose" class="com.sas.finance.fraud.engine.OSE">

    

           <constructor-arg name="meh" ref="sqlMEH" />

           <constructor-arg name="sas" ref="sas" />

           <constructor-arg name="connectors">

               <array>

                  <ref bean="queue1" />

                  <!--

                   <ref bean="socket1" />

                   <ref bean="usc" />

                   <ref bean="queue1" />

                   <ref bean="messageListener"/>

                   -->

               </array>

           </constructor-arg>

    

           <property name="cluster" ref="cluster" />

           <property name="credentialsStore" ref="credentialsStore" />

           <property name="config.serverMode" value="${MODE}" />

           <property name="config.threadCoreCount" value="4" />

           <property name="config.threadLimit" value="8" />

           <property name="config.jmxPort" value="2099" />

           <!--

           Uncomment the line in ose.sh that adds javax.net.ssl.keyStore if jmxSsl is enabled.

           -->

           <property name="config.jmxSslEnabled" value="false" />

           <property name="metadataService" ref="metadataService" />

           <property name="alertService" ref="alertService" />

    

   </bean>
   
   

3. Save the updated ose.xml file.
   
   
4. Take a backup ofcluster.xml, which is located in the Network File System (NFS)/shared mount and update the file with the new JMX port.
   
   Original: <member host="abc123.test.com" jmxPort="1099" useSSL="false" />
   Updated: <member host="abc123.test.com" jmxPort="2099" useSSL="false" />
   
   Note: Updating cluster.xml does not require you to restart the SAS Fraud Management middle-tier services.
   
   
5. Start up the OnDemand Decision Engine by issuing the following command:
   ./ose.sh start tail
   
   
6. Once SAS OnDemand Decision Engine is up, check the SAS OnDemand Decision Engine log file or the messages on the terminal from where you started SAS OnDemand Decision Engine to confirm that the JMX started on the new port:
   
   [main] INFO  OSE MBeanServer bound to service:jmx:rmi:///jndi/rmi://localhost:2099/jmxrmi