In this section: |
When you define the connectivity of the CRM gateway to the back-end application environment, you must identify characteristics of this connection. Connection characteristics determine the type of work and class of service used between the CRM gateway and its partner. Speak with your system administrator ahead of time about these considerations so you may select the best choices for your configuration.
In order to connect to a back-end system using the CRM gateway, you must configure your CRM gateway with an APPC connection (or link) to the back-end system. A CRM gateway can only have a single APPC connection to a given back-end system (region).
Discuss the following list of topics with your system administrator. These topics are relevant to both the CRM and back-end application environment.
These parameters are used to configure the connection, when adding a new IMS target. For more information on defining an IMS target using iWay Explorer, see the iWay Transaction Adapter for IMS User's Guide.
The log mode defines the characteristics of the APPC sessions that the CRM gateway establishes across a CRM Link.
The characteristics of different logon modes are tailored to support different types of applications. For example long-running batch applications might use different logon modes than short-lived online applications. Logon modes can define different logical unit protocols, classes of service, packet sizes, and pacing algorithms.
Use the same logon mode for the CRM gateway logical unit and the back-end application logical unit.
When a CRM Link is created, a pool of sessions is allocated to handle requests for that link. If a session is not available to a request, then the request will fail.
The following parameters should be considered when configuring session connections:
The number of maximum sessions that are allowed in the allocated pool. This value determines the number of concurrent requests that can be active at any given time. The CRM and the back-end system must configure their maximum sessions to the same value.
The CRM gateway and the back-end system are pre-allocated with a number of sessions for their use. This value is referred to as minimum winner sessions. The owner of these pre-allocated sessions has priority for its winner sessions; however, they may be reassigned depending on system load.
The total of the minimum winner sessions for both sides must be less than or equal to the maximum session value. If the total is higher than the maximum session value, you will be unable to activate the link.
For best results in determining minimum sessions, evaluate the number of sessions that are required for the CRM and for the back-end system to support concurrent requests.
The security level of a CRM Link defines what security credentials are required for all requests that utilize this link. The following options are available:
In the simplest case, no security credentials are provided with requests sent on the link. This implies that the user has been authenticated in the originating domain, and that no further authentication is required. The value for the CRM would be LOCAL. The corresponding value for the back-end system must be defined in the connection definitions
It is possible that the application processing the request needs to identify the user making the request for access control to application resources. For this case, only a user ID is provided with the request. The value for the CRM would be IDENTIFY. The corresponding value for the back-end system must be defined in the connection definitions
A third possibility is that full security credentials are required for any requests sent on the link. In this case, a user ID and password are required for each request. These credentials are validated against the security configuration in the destination environment. The user ID can then be used for access control to application resources. The value for the CRM would be VERIFY. The corresponding value for the back-end system must be defined in the connection definitions.
| iWay Software |