Security Overview

A CA Gen DP application incorporates security in multiple ways. Each portion of the security implementation depends the execution environment hosting the DPC and DPS.

Implementing a security solution for a CA Gen Distributed Processing application can involve processing that occurs at multiple points along the execution path of a cooperative flow.

Example:

Security processing is invoked from within the DPC and DPS application programs.
The security processing that executes as part of or on behalf of a DPC application typically gathers the security data that is supplied by the end user, such as a user ID and password.
The security processing that executes as part of, or on behalf of a DPS application validates the security data that is associated with a client cooperative flow request. Depending on the particular DPS security implementation, additional security data can be provided. For information about how additional security data can be used, see Server Security Processing.
Security processing can be integrated as part of the vendor products. This security processing is invoked as part of the third-party communications products or the TP Monitor that supplies the execution environment for the DPS.
Security processing can be invoked from a CA Gen provided communications program such as the Client Manager or Communications Bridge.

A security solution can involve one or more security processing choices which are as follows:

The CA Gen applications can use security processing that the execution environment provides. This security processing is external to the application itself. For example, Java clients flowing to EJBs use Java EE roll based security.
CA Gen provides programmatic support that application developers can use to implement security such as the USER_ID, CLIENT_USER_ID, and CLIENT_PASSWORD system attributes. This security implementation provides a tight interaction between the CA Gen Distributed Processing application and its execution environment.

The Application developers can also implement a create-your-own security implemented internal to the Distributed Processing application itself. In this case, the security processing is coded as part of the DPC and DPS.