Replicating Packages and Configuration Information to Integration Servers
Each Integration Server in the cluster should contain an identical set of packages that you define using Ariba Supplier OnRamp. To ensure consistency, make sure that you create all packages on one server and replicate these packages to the other servers. If you allow different servers to contain different packages, you might not derive the full benefits of clustering. For example, if a client requests a service that resides in only one server, and that server is unavailable, the request cannot be redirected to another server.
Ariba Supplier OnRamp stores configuration information updated in the Ariba Supplier OnRamp Configuration screen as flow services within packages and in the database (JDBC pools).
When using Ariba Supplier OnRamp without Trading Networks, the configuration information includes the following items:
cXML Request Document handlers
PunchOutOrderMessage mapping services
Event service stubs that are invoked at various stages of punchout processing
Logging services
A
payloadID creation service
When using Ariba Supplier OnRamp with Trading Networks, the configuration information includes all of the above items as well as the following items:
Document attributes and type definitions
PunchOutSetupRequest, OrderRequest, ProfileRequest, MasterAgreementRequest, and InvoiceDetailRequest processing rules
The configuration information is visible only to the server on which it resides; it does not share a common storage facility. Therefore, whenever you change the above information, you should replicate the configuration information in the packages as well as in the Ariba Supplier OnRamp Configuration screen across all the nodes in the cluster.
When using Ariba Supplier OnRamp in a clustered environment, all of the above configuration information have to be replicated except the processing rules. Processing rules are in the database, which is common for all the clustered nodes.
Note:
Ensure that the Document Attributes, Document Type definitions, and Processing Rules are available in the Integration Server where the configuration information is replicated.
To replicate the configuration
1. All the clustered Integration Server nodes should point to the same JDBC Pools.
2. The flow services and packages should be replicated using the export - import mechanism or Designer. For information about replicating packages, see the webMethods Service Development Help for your release.
3. The user should replicate the configurations set on the Ariba Supplier OnRamp Configuration screen.