OnRamp for Commerce One MarketSite 3.5 SP1 | webMethods OnRamp for Commerce One MarketSite Adapter Documentation | webMethods OnRamp for CommerceOne MarketSite Adapter Installation and User’s Documentation | Using the Partner Manager | Building and Maintaining the Routing Rules | Creating a Routing Rule | Configuring the IS Service Transport
 
Configuring the IS Service Transport
Use the following procedure to complete the configuration parameters on the Edit Routing Rule screen if you are creating a routing rule that uses the IS Service transport. The IS Service transport passes the document to a specified service on a local or remote Integration Server.
To configure the IS Service transport, in the Configure IS Service section of the Edit Routing Rule screen, complete the following fields:
In this field...
Do the following...
Server Alias
Select the Integration Server on which the service resides, or select (local) if the service resides on the same server as the Partner Manager. (If the Integration Server you need does not appear in this list, you must create an alias for it. For information about defining aliases for remote Integration Servers, refer to the webMethods Integration Server Administrator’s Guide for your release.)
Folder
Type the name of the folder in which the service resides.
Service
Type the name of the service to which you want to pass the document.
Scope
Specify how you want to maintain the routing service’s connection information in cases where the document is routed to a service on a remote server.
*Select SESSION if you want to maintain connection information within the routing service’s session. This preserves this information for the routing service’s exclusive use while it is connected to the remote server. Use this option if the routing service will perform stateful interactions with the remote server.
*Select GLOBAL if you want to maintain connection information in a shared session pool, making it available for use by other services that may need to connect to the same server. Because the data in this session is not protected from other services, you should only use this option if the routing service’s interaction with the remote server is stateless (i.e., it is not dependent on the availability of session information after a connection has been established).