Middleware is a collection of software that serves the following purposes:
CA Gen supports the following server execution environments:
A third-party vendor such as IBM, Microsoft, Oracle, or HP provides all but the CA Gen Transaction Enabler software. The third-party vendor middleware defines the underlying transport protocol that is used for the exchange of a request and a reply between a client and a server. Regardless of which middleware an application developer chooses, the application protocol between a DPC and a DPS remains the same. For more information, see Request/Reply Application Protocol.
CA Gen provides the communications runtime for each server execution environment that is supported but only supports the minimum functionality that is required for the execution of a DPS application. The third-party middleware offers some features that are not available. The CA Gen communication runtimes supports only features required to support the execution of a DPS.
CA Gen supports three major communication and middleware components. The first major component is the Transaction Processing Monitor (TP Monitor). The TP Monitor provides the execution environment for the servers.
The next two major components exist external to the server execution environment. They provide the mechanisms that use client applications to communicate with a specific server. These communications and middleware components are as follows:
|
Copyright © 2014 CA.
All rights reserved.
|
|