The OpenCPIC carrier system is more powerful and also more complex than UPIC. OpenCPIC also allows the server program to initiate communication. The OSI TP protocol is used for communication.
An OpenCPIC client can also communicate with OpenCPIC applications, CPI-C applications and other non-UTM applications as long as these applications also use OSI TP. An OpenCPIC client can also work together with a resource manager via the XA interface. openUTM handles communication with openCPIC clients like server-to-server communication.
In communication with OpenCPIC clients, you can select whether to work with or without global transactions:
In the case of global transaction management, the OpenCPIC client can decide when a global transaction is to begin and end and is therefore included in the global transaction boundary. Transaction control is handled via the X/Open interface TX, while communication is handled via the CPI-C interface.
When you work without global transactions, the OpenCPIC client is included in the openUTM restart concept.
OpenCPIC clients can use the “multi-signon” function. In other words, a number of OpenCPIC clients can sign on under the same UTM user ID if service restarting is dispensed with for this user ID or if you work with global transaction management.
There are clients that use the OpenCPIC carrier system on Unix platforms and Windows platforms.
| Further information on how to use the openUTM security functions when connecting client applications can be found in chapter "Security functions". You will also find more information on the Restart functionality in chapter "Fault tolerance and the restart function". The openUTM-Client products UPIC and OpenCPIC carrier systems each have their own manual. There you will find all the details required regarding programming and connecting client applications. |
