Configuring Trading Networks for a Clustered Environment
When you cluster Trading Networks instances, you can configure the instances so that data cached in memory, user accounts, and properties are synchronized on all instances in the cluster. However, the Integration Servers that host the Trading Networks instances need not be in cluster. For more information on clustering Integration Servers, refer webMethods Integration Server Clustering Guide.
Use the following procedure to configure Trading Networks for a clustered environment.
Important: When you save the properties you edit in this procedure,
Trading Networks will update all properties, including those that you did not edit. In a clustered environment, this will cause
Trading Networks to synchronize all properties. If you want the
Trading Networks instances in the cluster to maintain different values for some properties, set the
tn.cluster.notifyPropertyChange property to
false, and maintain the properties for each server individually.
To configure
Trading Networks for a clustered environment
1. On each Integration Server in the cluster, create a remote server alias for the other Integration Servers in the cluster. For instructions, see webMethods Integration Server Administrator’s Guide.
Important: If you have already created a remote server alias so the Integration Server is part of a cluster without Trading Networks, you must create an additional remote server alias for the Integration Server that is specifically for the Trading Networks cluster.
2. To update the Trading Networks properties.cnf file for each Trading Networks instance in the cluster, do the following:
a. In My webMethods: Administration > Integration > B2B Settings > Configure Properties.
b. Add or edit the properties:
The following table lists the properties:
Property | Setting |
| Remote server aliases you created in step 1. |
| Number of rows of query results for Trading Networks to store in the session object. When clustered, Trading Networks should not store query results in the session object; set this property to “-1”. for example: tn.query.threshold=-1 |
c. Set these properties to true:
Property value to set | Notification to all the servers in the cluster |
| Change to data cached in memory. |
| New user accounts. |
| Change to Trading Networks properties. |
d. Click Save.
3. Trading Networks data cached in memory, user accounts, and properties are automatically synchronized on all Integration Servers in the cluster. To turn one of these synchronizations off for a Trading Networks instance, modify the appropriate property in the Trading Networks properties.cnf file. For example, if you want to manually control user account creation, turn off the tn.cluster.notifyProfileAddUser property.