Deploying TIBCO MDM on JBoss WildFly Application Server

You need to deploy TIBCO MDM on JBoss WildFly Application Server.

Procedure

  1. Copy the ECM.ear file from $MQ_HOME to the $JBOSS_HOME/standalone/deployments directory.
  2. If you deploy TIBCO MDM on Solaris Sparc,
    1. Add the TMPDIR variable and set it to any directory location.
    2. Specify the following JVM parameter:
      -Djava.io.tmpdir=${TMPDIR}
  3. To improve the performance of TIBCO MDM, add the following JVM parameter while starting the JBoss WildFly Application Server: 
    -Dorg.apache.xml.dtm.DTMManager="org.apache.xml.dtm.ref.DTMManagerDefault"
    If the output does not contain any error or exception messages, you are ready to use the JBoss.
    Note: When the log4j service of TIBCO MDM initializes, it overrides the JBoss rootLogger property and starts writing server logs in the elink.log file. As a workaround, you can comment out the rootLogger property in the $MQ_HOME/config/ConfigValues.xml file: 
    <ConfValue description="The root logging level for the MDM server." name="Root logging Level for MDM Server" propname="log4j.rootLogger" sinceVersion="7.0" visibility="All"> <ConfString default="DEBUG" value="DEBUG"/> </ConfValue>
    It is recommended that you keep this property to change the root logging level for TIBCO MDM.