Configuring MCS and an application server

MCS and an application server must be configured to enable remote management of the device repository clients by the drManager utility.

Copy the com.volantis.synergetics.management-jndi-impl-6.3.1.jar file from the ${MCS_HOME}/ext directory to the common libs directory of your application server.
Note:
If your application server exports a fixed set of MBean servers, then you must skip this step.
Add the JNDI configuration to your server.xml file. The name of the JNDI resource must be the same as specified in the mcs-config.xml file.
```
<Resource name="management/MBeanFactory" 
  auth="Container"
  type="javax.management.MBeanServer"
  factory="com.volantis.openapi.synergetics.impl.management.
               jndi.MBeanServerObjectFactory"/>
```
Note:
If your application server exports a fixed set of MBean servers, then you must skip this step.
Configure the MBean server in mcs-config.xml. If your application server supports custom objects in JNDI, then add the jndi-mbean-server element. Make sure it points to the JNDI datasource specified previously.
```
<management>
  <jndi-mbean-server initial-context="/mcs" name="management/MBeanFactory"/>
</management>
```
If your application server exports a fixed set of MBeanServers through JNDI, then add the platform-mbean-server element.
```
<management>
  <platform-mbean-server/>
</management>
```

To enable monitoring, properties like the following must be used when starting the application server. Refer to your application server documentation for further information.

-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=9004
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Djava.rmi.server.hostname=10.20.30.40

Configuring MCS and an application server

Related topics