Hot Deployment Overview

You can reinitialize various configured objects at run time without requiring a server restart. In other words, as soon as values are changed, the Administrator can issue a request to reconfigure the application.

Prior to TIBCO MDM 7.1, all configuration properties were defined in the ConfigValues.xml file, segregated based on various categories, and marked within appropriate tags <ConfigValue>. Changes to the properties were updated through MqRevivify (invoking PropManager.refresh()). This approach enabled a reread of all properties from the ConfigValues.xml file.

However, reinitialization of already configured objects did not happen, such as init classes (where sequences may have been changed or new classes may have been added), JMS sender and receiver managers involved in integration with TIBCO MDM, Email, FTP, LDAP server configurations, and so on.

Previously, JMX was used in the backend. In the TIBCO MDM 9.1.0 release, the JRM dependency has been replaced with RESTful service. The Node URL property is added in Configurator (Node ID > Configuration Outline > Application Server. Specify the hostname and port number in the value. By default, the value is http://localhost:8080.
Note:
  • For the JBoss WildFly application server, the port number must be the same that is specified in the standalone.xml file. For information, refer to the section, "Configuring TIBCO MDM for JBoss WildFly Application Server" in TIBCO MDM Installation and Configuration Guide.
  • For the cluster set up, clone the members. For information on cloning, refer to Cloning a Cluster Member.

Limitation

Node ID does not work on the https host. Therefore, do not include https in the value of the Node URL property.