Updating Internal HTTP Connector Configuration

An internal HTTP connector is used by TIBCO Administrator to provide certain files that runtime Hosts and Nodes need to access. It is used only for internal communications in the product. Updating an internal HTTP Connector configuration involves re-installing the internal HTTP Connector Resource Instance, updating the notification transport for Hosts, and re-installing Keystore Resource Instances for Nodes.

Previously, updating the internal HTTP Connector configuration posed many challenges in a large scale setup. For example:

  • There was no way to track the progress of various keystore resource instances being updated, which could be a problem in a setup with a very large number of nodes.
  • Re-installing keystore resource instances on a selection of nodes was not possible, that is, all the keystore resource instances on all nodes in the enterprise would have to be updated.
  • The process of updating the internal HTTP Connector was time consuming.
  • All available database connections were consumed.

With this enhancement, the ActiveMatrix Administrator CLI provides a stable approach for updating the internal HTTP Connector configuration.

Details of Updating the Internal HTTP Connector Configuration

An internal HTTP Connector runs on the ActiveMatrix Administrator server. Hosts and nodes use this HTTP Connector to download files from the ActiveMatrix Administrator server. The internal HTTP Connector configuration is stored in the ActiveMatrix Administrator database and is deployed to the SystemNode. The URL of the internal HTTP Connector is stored in the notification.xml of the host and the Keystore Resource instances on all nodes as well.

Editing the internal HTTP Connector configuration results in:

  1. Updating the internal HTTP Connector Resource Template in the ActiveMatrix Administrator database with the new configuration.
  2. Re-installing the internal HTTP Connector Resource instance on the system node.
  3. Updating the notification.xml file for all Hosts, if the URL of the internal HTTP Connector has been updated.
  4. Re-installing the Keystore Resource Instances with the new internal HTTP Connector URL on all nodes, if URL of internal HTTP Connector has been changed.

Enabling the Internal HTTP Connector Configuration Updates

Note: The approach described in this section is supported only through the ActiveMatrix Administrator CLI. It is not supported through ActiveMatrix Administrator UI.

This approach is enabled by default. If the enterprise has more than 50 nodes, the option to update the internal HTTP Connector from the ActiveMatrix Administrator UI is disabled and the CLI target must be used. If the enterprise has 50 or less than 50 Nodes, the internal HTTP Connector Configuration can be updated using the GUI.

To skip checking number of Node and always use ActiveMatrix Administrator UI to update Internal HTTP Connector configuration, set the TRA property com.tibco.amx.admin.internal.http.connector.update.disable.node.number.checking to true on the SystemNode.

If the URL of the internal HTTP Connector has not been changed, but for some reason, Host Notification Transport and Keystores need to be updated, the operation can be executed with the "forceUpdateKeystores" options as shown below. 

<target name="update.internal.http" depends="-test.targets.order">
<AMXAdminTask
remote="true"
propsFile="${instanceProperties}"
action="updateInternalHttpConnector"
dataFile="${dataFile}"
objectSelector="ResourceTemplate"
overwrite="true"
incrementalEdit="true"
merge="false"
createIfNotExists="true"
force="false"
failOnError="true"/>			
<options="forceUpdateKeystores">
</target>