Determining sender contexts in the OLTP message-driven bean

An OLTP message-driven bean can obtain information about the sender via the object OltpMessageContext. This includes, for example, the application name and host name of the EIS partner and the inbound service with which the OLTP message-driven bean was called in the proxy. It may, for example, be of interest to identify the inbound service, if several different inbound services have been assigned to a message endpoint in the proxy container.

The object OltpMessageContext provides the following methods for querying the sender context:

• String getBCProxyName()

  Name of the proxy application, fixed length of 8 characters

• String getBCProxyHost()

  Name of the host on which the proxy is running, fixed length of 64 characters.

• String getBCProxyInboundService()

  Name of the called inbound service in the proxy, fixed length of 8 characters.

• enum BCCommunicationProtocolType getBCCommunicationProtocol()

  Identifier for the communication protocol via which the EIS partner called the inbound service.

  • In the case of dialog communication, the type of communication protocol (or client protocol) can be determined from the enumeration class BCCommunicationProtocolType.

  • In the case of asynchronous communication, the protocol type of the logical access point in the proxy is passed, see also getBCProxyLocalPartnerName().

  BCCommunicationProtocolType returns the following values:

  '2' corresponds to the protocol type OSI-TP

  '3' corresponds to the protocol type UPIC

  '5' corresponds to the protocol type RFC1006

  '6' corresponds to the protocol type SOCKET

• String getBCPartnerTransportSelector()

  String with a fixed length of 8 characters. In the case of asynchronous communication, blanks are passed.

  In the case of dialog communication, the following elements are passed depending on the protocol type:

  • Protocol type UPIC, RFC1006 or SOCKET: Partner name of the client in the proxy

  • Protocol type OSI-TP and UTM partner in BS2000 systems: BCAM application name of the remote host

  • Protocol type OSI-TP and UTM partner on open platforms: The partner application's T selector

  • Protocol type OSI-TP and CICS partner: TRANSPORT-SELECTOR which is assigned to the CICS partner in the openUTM-LU62 Gateway

• String getBCPartnerNetworkSelector()

  String with fixed length of 64 characters. In the case of asynchronous communication, blanks are passed.

  In the case of dialog communication, the following elements are passed depending on the protocol type:

  • Protocol type UPIC, RFC1006 or SOCKET: Processor name of the client

  • Protocol type OSI-TP and UTM partner in BS2000 systems: BCAM processor name of the host on which the partner application is located

  • Protocol type OSI-TP and UTM partner on open platforms: Host name of the partner computer

  • Protocol type OSI-TP and CICS partner: NETWORK-SELECTOR assigned to the CICS partner in the openUTM-LU62 Gateway

• String getBCProxyTransportSelector()

  String with fixed length of 8 characters. In the case of asynchronous communication, blanks are passed.

  In the case of dialog communication, the following elements are passed depending on the protocol type:

  • Protocol type UPIC, RFC1006 or SOCKET: Application name in the proxy application (BCAMAPPL name)

  • Protocol type OSI-TP and UTM partner: TRANSPORT-SELECTOR of the ACCESS-POINT in the proxy application

  • Protocol type OSI-TP and CICS partner: TRANSPORT-SELECTOR of the associated ACCESS-POINT in the openUTM-LU62 Gateway.

• String getBCProxyUserId()

  User ID in the proxy application or, if the protocol type is OSI-TP and the EIS partner has not passed any user ID, the connection name (ASSOCIATION name). Fixed length of 8 characters.

• String getBCProxyLocalPartnerName()

  Name of the logical access point in the proxy application. In the case of the protocol type OSI-TP, this is the OSI-LPAP name; for all other protocol types, it is the LTERM name. Fixed length of 8 characters.

• String getBCRaMessageEndpointName()

  Name of the called message endpoint.

• boolean isBCPartnerXATMI()

  true if the EIS partner communicates with the BeanConnect proxy via the XATMI interface, otherwise false.

• boolean isBCPartnerXATMIConversational()

  true if the EIS partner communicates with the BeanConnect proxy via the XATMI interface and has selected the conversational communication paradigm, otherwise false (i.e. request/reply paradigm).

Strings which are returned with a fixed length of 8 or 64 may be padded with blanks at the end if necessary.