The proxy is the connecting link between the resource adapter on one side and the EIS on the other side.
It serves as container for configuration properties of the communication partners and holds all information on services, communication endpoints and message endpoints.
The proxy is responsible for transporting the messages and ensures that they are assigned to the corresponding partners and services. It provides functions for transactional security and for verification of access rights (user ID and password) on requests to and from UTM or CICS applications. The proxy stores asynchronous messages (inbound and outbound) until they are sent to the EIS partner or the message endpoint application.
The bulk of the BeanConnect configuration is done by configuring the proxy.
The proxy contains the proxy container which is based on the UTM transaction monitor openUTM V6.5.
You can use the Management Console to configure the proxy in three different ways
As an UTM proxy which communicates exclusively with EIS partners of type openUTM.
An UTM proxy consists only of the proxy container.
As a CICS proxy which communicates exclusively with EIS partners of type CICS.
A CICS proxy requires additional components to communicate with CICS applications. A separate license is required for CICS communication.
As a combined proxy
A combined proxy communicates both with EIS partners of type UTM and with EIS partners of type CICS. A further, separate license is required for CICS communication.
Components of a CICS proxy
For communications with CICS applications, the proxy additionally consists of the following internal components:
the openUTM-LU62 Gateway, implementing the LU6.2 protocol stack for interconnection with EIS partners supporting the SNA protocol LU6.2. Both transactional and non-transactional connections with CICS applications are supported.
Communication service:
This is a third-party product that implements the SNA stackThis is SNAP-IX for Solaris Systems from Metaswitch Networks Ltd or IBM's Communications Server for Linux and Windows. These products are not included in the BeanConnect scope of delivery.
The following figure shows the components of the proxy for communications with CICS applications:
Figure 4: BeanConnect proxy components of a CICS proxy
The proxy and all the proxy components are managed and administered using the Management Console. The openUTM-LU62 Gateway and communication service proxy components may run either on the same computer as the proxy container or together on a separate computer as required.
If a component that is to be administered (proxy, gateway, communication service) runs on a different host from the Management Console, then an MC-CmdHandler must be installed on this separate host, see also BeanConnect tools .
Please note that the communication service must be installed under a user ID which has SNA authorization.
The BeanConnect proxy is used for outbound communication via the OSI-TP and LU6.2 protocols as well as for inbound communication.
In the case of outbound communication with EIS partners of type openUTM via the UPIC protocol, the proxy is not used.