Previous Topic: Single-Instance Client ManagerNext Topic: Client Manager Features


Multi-Instance Client Manager

A Multi-Instance Client Manager operates similar to a single instance Client Manager with the only difference being that it is intended to operate in a multi-user environment. CA Gen supports Microsoft Windows Terminal Services. This multi-user execution environment provides a thin-client product allowing one or more "user workstations" to share client application resources residing on a single, shared Windows "client workstation." Each logged on "user workstation" is presented with its own, private desktop view executing upon the "client workstation."

The user workstation does not execute any portion of the CA Gen Distributed Processing application. The host client workstation executes the DPC portion of the application as well as the Client Manager instance.

The installed version of Client Manager operates with the expectation that it is being executed in a single user environment. Each user within a multi-user environment must have a unique instance of the Client Manager. To accomplish this, the installed Client Manager delivers a user exit that allows more than one instance of the Client Manager to execute in a multi-user environment. The Client Manager ID user exit (the ci_cm_id entry point) can be modified such that one instance of a Client Manager can be distinguished from another. Typically, customization of the user exit involves making use of a logon user-id or session-id that is unique for a given thin-client user.

Once the Client Manager ID user exit has been customized, each instance of the multi-instance Client Manager behaves the same as the single-instance version.

The modified Client Manager ID user exit resides in its own DLL (CMICXnnN.dll, where "nn" is the CA Gen release number). This DLL is used by the Client Manager and the Client Manager CoopFlow. The Client Manager CoopFlow is the code that supports the inter-process communications between the GUI applications and the Client Manager.

The technique used in the Client Manager ID user exit must, for each user, provide the same unique ID value when executing from an instance of the Client Manager and when executing from instances of a GUI application client. Providing the same Client Manager ID value allows a user's GUI applications to communicate with the unique instance of the Client Manager.

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

More information:

Configuring the Client Manager for Client Communications