openUTM can act as a client of a Java EE application server when the UTM application initiates communication by sending a message to the J2EE application server. This is inbound communication from the point of view of the J2EE server. The OSI TP protocol or a transport system protocol can be used for communication, see the following figure:
Figure 9: openUTM as a client of a Java EE application server
The link between openUTM and the Java EE application operates via the BeanConnect Proxy component. The messages sent by the UTM application are sent to message endpoint applications (message-driven Beans) on the Java EE application server.
Communication can take place via OSI TP or the transport system protocol:
When the OSI TP protocol is used, you can work with or without transaction management. Asynchronous communication and communication in the dialog is possible.
If a transport system protocol such as Socket or RFC1006 is used, then communication is always asynchronous and non-transactional.
To establish a link, you must modify the generation of the UTM application and configure the BeanConnect Proxy accordingly.
| Use the BeanConnect Management Console to configure BeanConnect Proxy. For further information, refer to the manual "BeanConnect". |
