Configuring a High Availability Environment

Clustered Trading Networks instances must share a single Trading Networks database. When a Trading Networks database is shared:

All configuration data and run-time data (for example, documents received from partners, or the activity log) is shared among all Trading Networks instances in the cluster.

Changes you make to Trading Networks objects (for example, profiles, custom document attributes, document types, and processing rules), are automatically shared among all Trading Networks instances in the cluster.

If you modify Trading Networks properties in My webMethods or by invoking the wm.tn.admin:setProperties service, the changes are automatically replicated to all instances of Trading Networks in the cluster. If you want to modify Trading Networks properties by directly editing the properties.cnf file, you must manually make the changes to the properties.cnf file for each Trading Networks instance. The properties.cnf file is in the Integration Server_directory \instances\instance_name\packages\WmTN\config directory.

Multiple Trading Networks clusters can share a single Trading Networks database. Clustered Trading Networks instances can also share a single database. Non-clustered Trading Networks instances cannot share a single Trading Networks database. You need to create a Trading Networks database for each non-clustered Trading Networks instance. When a Trading Networks database is not shared:

Changes you make to Trading Networks assets or properties are not shared among Trading Networks instances. If you want to keep the instances in sync, you must make the changes to each instance.

Trading Networks instances do not share run-time data.

You cannot relate documents sent to and processed by one Trading Networks instance to documents sent by and processed by other instances. For example, an Acknowledgement document that is sent to instance 1 cannot be related to the Confirmation document if the Confirmation document is sent to instance 2.