IBM WebSphere Multichannel Bank Transformation Toolkit, Version 7.1

Implementing the startup and session end processes

The startup operation (StartupClientOp on the client and StartupServerOp on the server) is the first operation launched by a client. Its role is to create a workstation context on the server side that belongs to the client workstation. That is, it provides a context hierarchy that maintains data and services available for all the requests coming from the same workstation, and will provide, on the server, a running environment that is accessible only for a given client. It also determines whether the server uses permanent or dynamic connections to send events to the client.

The startup operation must also add an entry to the session table on the server side. This table is used by the Client/Server Mechanism to chain the operation context of the subsequent operations to the context created in the startup operation. All operation contexts are chained to this workstation context unless they specify the serverOperationParentContext attribute in their operation data. Usually, the startup operation is also used to execute any process prerequisite for the next operations, such as establishing host communications.

Although the startup operation is not mandatory, the need for a client environment on the server is a common requirement and therefore the sample application provides this facility.

The StartupClientOp and StartupServerOp classes are also provided as samples in the com.ibm.dse.samples.appl package.

Each time that a client is loaded, the StartupClientOp operation is executed. This operation searches for the local information about the terminal where it is running, instantiates its operation context (StartupClientContext) and sends a request (with parameters) to the server for execution of the StartupServerOp operation. On the server side, if it is the first client to connect, the operation instantiates the branchServerCtx context; this is the root of the contexts that is created in the hierarchy for the branch. Depending on the parameters of the request, the channelCtx context for the type of client being connected is instantiated, and the particular SessionCtx is added to the hierarchy.



Feedback