An OSI-TP connection can be used for both outbound communication and inbound communication. An OSI-TP connection enables both transactional and non-transactional communication.
An OSI-TP connection between BeanConnect and openUTM requires an OSI-LPAP and an OSI-CON statement within the EIS partner's UTM generation (KDCDEF).
On the proxy side the generation is processed as described in Configuring the EIS partners . On the EIS partner side the BeanConnect Management Console generates these statements in a text file in the directory <MC_Home>/genfiles.
In the case of a single proxy, the name of the generated input file is:
ProxyID.<p-id>.EisPartnerID.<e-id>.UTM.txt
In the case of a proxy cluster, the name of the generated input file is:
ClusterID.<c-id>.EisPartnerID.<e-id>.UTM.txt
<p-id>, <e-id> and <c-id> designate the IDs for the proxy, EIS partner and proxy cluster assigned by the Management Console.
BeanConnect does not transfer this configuration file to the EIS platform. The generated input file has to be transferred to the EIS partner host using common file transfer mechanisms. After that, the UTM administrator can use the file to carry out the configuration activities.