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

Behavior Differences

The generated Server Procedure Steps execute the same regardless of the server execution environment. However, the execution environments can impose operational differences.

Example:

• Distributed Transaction Support is only available when deploying DPS applications as a Tuxedo Server, a Java EJB, or .NET Server.
• Asynchronous cooperative flows between servers are only available when the DPSs are deployed as MQSeries servers.
• Obtaining a user ID context for a DPS that populate the USER_ID system attribute is not available when the DPS operates as a Java EJB or .NET Server.
• EJB and .NET Servers allow a DPS to have multiple database connections.
• Only certain environments support coding non-CA Gen user-written clients without the use of a generated Proxy.

Note: For more information about third-party software that is supported for a particular execution on environment, see the current version of CA Gen Technical Requirements document.