To fulfill a service request, a server application can in turn request the services of other applications, i.e. it can send its own jobs to other applications. This is also known as distributed processing. With server-to-server communication, therefore, services in two or more applications work together to process a job issued by a client. A service that requests a service from another application is known as a job-submitting service, and the service that provides the service is called a job-receiving service.
Server-to-server communication also allows you to set up several parallel connections between two applications and process several jobs simultaneously.
An application can not only engage in dialog with other applications, but can also use the openUTM message queuing functionality during server-to-server communication (see section "Sending background jobs to remote services (remote queuing)").
Since server-to-server communication involves much more than the mere exchange of messages, special high-level communication protocols are required. openUTM supports the LU6.1 protocol and the internationally standardized OSI TP protocol. These protocols, which are widely used worldwide, offer the advantage of enabling a UTM application to interact not only with other UTM applications, but also with applications from third party manufacturers, e.g. CICS, IMS or Tuxedo applications. This applies even if these applications are running on other platforms.
The product openUTM-LU62 permits a dialog with applications that use the LU6.2 protocol. openUTM-LU62 converts the OSI TP protocol to the LU6.2 protocol because openUTM communicates in this case by means of OSI TP (see also section "Communication with CICS, IMS and TXSeries applications").
Server-to-server communication is fully compatible with cluster operation, i.e. one or both server applications can be implemented as a UTM cluster application, see also section "Load distribution for distributed processing".