Activating Publication of MCS Events as Strongly-typed MBeans

You can retrieve MCS events as MBeans through a JMX connection to the MCS Server. These MBeans are exposed as strongly-typed Mbeans (integer, long, double or Boolean data types) so that you can monitor the 3DSpace Service with your own monitoring solution.

MCS Mbeans are exclusively published as strongly-typed MBeans. The 3DEXPERIENCE platform's Monitoring Agent does not collect these MBeans because they are meant to be consumed by standard JMX-capable monitoring agents.

See Also
3DSpace Metrics
  1. To activate unauthenticated JMX remote access on a given port, edit the Java Virtual Machine (JVM) arguments of the Java application server hosting the 3DSpace Service web application.

    Methods for activating JMX remote access vary from one application server to another, and even for a given application server type, many options (SOAP, RMI or proprietary transport, authentication schemes, etc.) are available.

    Here are the certified methods for 3DEXPERIENCE supported application servers:

    • Apache TomEE++

      Add the following lines (assuming the JMX port will be 9999, which can be changed) to the mxEnv.sh and mxEnvCAS.sh files:

      export CATALINA_OPTS=" -Dcom.sun.management.jmxremote -
Dcom.sun.management.jmxremote.port=9999 -
Dcom.sun.management.jmxremote.authenticate=false -
Dcom.sun.management.jmxremote.ssl=false"

  2. Optional: To move the display of the MCS Metrics Mbeans under a domain, add the following lines to the mxEnv.sh and mxEnvCAS.sh files: 

    set MCS_METRICS_MBEAN_ROOT=DOMAIN
export MCS_METRICS_MBEAN_ROOT

    where DOMAIN is the domain under which the MCS Metrics will be registered.

    Note: The domain name cannot contain the character : as it is a reserved character in the JMX MBean Object Name syntax. For more information, see http://www.oracle.com/us/technologies/java/best-practices-jsp-136021.html.

  3. Restart the application server.