Components of a Typical CA Gen Tuxedo System › Client-Side Components of a Typical CA Gen Tuxedo System › C Tuxedo Coopflow

C Tuxedo Coopflow

The C Tuxedo Coopflow (Communications Runtime for Tuxedo) interfaces to the Tuxedo software using the ATMI API. This interface facilitates the client connect and disconnect from Tuxedo, performs Tuxedo buffer management, and performs the synchronous transmission of the cooperative flow to a Tuxedo service application (and so to the CA Gen Server Manager). The C Coopflow is made up of the following subcomponents:

• C Tuxedo MsgObj-Facilitates the transformation of data between the CA Gen import and export views and the View32 buffers of Tuxedo.
• C Tuxedo CoopFlow-Manages the interaction with the Tuxedo software using the ATMI API.
• C Tuxedo Client Exits-Provides exit opportunities to influence the processing of the C Tuxedo CoopFlow component. These exit points allow you to set the user context of a Tuxedo connection. Additionally, the data that is transferred can be viewed, modified, or both, prior to being sent to the server application and upon return from the server. The following Tuxedo Client Exit entry points are invoked by the C Tuxedo CoopFlow processing:
  • ci_c_sec_set()-Allows control of user context of Tuxedo connection.
  • ci_c_user_data_out ()-Provides access to outbound View32 buffer prior to invoking the target service (that is, before tpcall()).
  • ci_c_user_data_in ()-Provides access to inbound View32 buffer on return from the target service (that is, after tpcall()).

Note: For more information about the client user exits, see the User Exit Reference Guide.