Prerequisites for Invoking the Notification Transport Server Configuration Update Target

Following conditions are a prerequisite for invoking the Notification Transport Server Configuration update using TIBCO ActiveMatrix Administrator CLI:

  • A TIBCO_HOME with this release.
  • An instance of the remote_props.properties file (containing the information for connecting to TIBCO ActiveMatrix Administrator) from CONFIG_HOME/admin/<enterprise-name>/samples, must be copied over to TIBCO_HOME/administrator/<version>/samples.
  • Apache Ant 1.8 or higher. You can use Ant available as part of the TIBCO ActiveMatrix installation located in TIBCO_HOME/amx/<version>/bin/ant/. If you are using an external Ant, the JRE in use must be 1.7 or higher, that is, the JAVA_HOME must point to Java 7 or higher.
    Remember: When you obtain third party software or services, it is your responsibility to ensure you understand the license terms associated with such third-party software or services and comply with such terms.
  • The machine from where the Notification Transport Server Configuration update will be executed needs network access to the TIBCO ActiveMatrix Administrator on which the Notification Transport Server Configuration update is being run.
  • If a Load Balancer is in use while accessing the web interface (UI) of TIBCO ActiveMatrix Administrator, the Load Balancer URL must be used in the remote_props.properties file for accurate results.
  • If TIBCO ActiveMatrix Administrator is secured via SSL, user needs to specify trust store information in the "remote_props.properties" file. For example: 
    # Admin trust store setting for SSL, variable is not allowed
javax.net.ssl.trustStore=C:/tibco330/tibco/data/admin/amxadmin01/samples/adminCliTruststore.jks
javax.net.ssl.trustStoreType=jks
javax.net.ssl.trustStorePassword=#!feiKaElawZazJ+xNFJeyd/67OD8P6feU
  • The user specified in the remote_props.properties file must be a super user in TIBCO ActiveMatrix Administrator.
Note: It is critical that there be no on-going, active deployments in the TIBCO ActiveMatrix Enterprise while the Notification Transport Server Configuration update is in progress.
Note: During Notification Transport Server Configuration update, no Nodes or Applications are restarted. Thus, the update should not cause any business outage.
Note: In a large scale setup, the Notification Transport Server Configuration update could take a considerable amount of time, so it is recommended that the update be launched accordingly, for example, on weekends.