Anatomy of a DP Application › Server Execution Environments › Transaction Processing Monitor (TP Monitor)

Transaction Processing Monitor (TP Monitor)

The TP Monitor that hosts the server application usually defines a server execution environment. A TP Monitor is the execution environment that hosts the server application. The TP Monitor provides the capacity, control, and management support necessary to concurrently execute one or more transaction applications.

A CA Gen DPS is generated for a specific TP Monitor. The following list describes the TP Monitors supported by CA Gen:

• CA Gen Transaction Enabler (TE)
• IBM CICS
• IBM IMS
• Oracle Tuxedo
• Java Enterprise JavaBeans (EJBs)
• Microsoft .NET Component Services
• NonStop Pathway using TMF
• EJB Web Services

In addition to the TP Monitors mentioned in the previous list, IBM WebSphere MQ can also be considered a TP Monitor when it is used separate from CICS and IMS. WebSphere MQ triggers the target DPS's execution where the server executes as a stand-alone process operating directly on the host system.

The choice of TP Monitor limits other characteristics that shape a server execution environment.

Example:

• Operating System
  • CICS and IMS are TP Monitors only available on z/OS
  • Tuxedo is only available on UNIX
  • EJB is only available on a Java Platform JVM
  • Transaction Enabler is only available on Windows and UNIX
  • NonStop Pathway is only available on NonStop systems
• Language
  • CICS and IMS servers are generated in COBOL
  • Transaction Enabler and Tuxedo servers are generated in C
  • EJB servers are generated in Java
  • .NET servers are generated in C# (C sharp)
  • NonStop Pathway servers are generated in C
• Database

  For information about databases that are offered within a particular server execution environment, see the current version of CA Gen Technical Requirements document.