Orchestration Tasks for OS 2200 UTS Projects

The following tasks are unique to OS 2200 UTS projects.

Connecting to a Server

By default, the initial orchestration for an OS 2200 UTS data source project already includes the necessary Connect activity in the On Client Session Start event handler, so, by default, you do not need to do anything. However, the procedure below outlines the steps for explicitly adding a connection if you removed the default Connect activity or need to add a connection in another location.

When an OS 2200 UTS data source project is created, the following server messages are supplied automatically. These messages can be used if a fixed terminal ID is required or if a DPS LOGON must be performed.

Server MessageProvided FieldsExplanation

connect_TerminalID

Terminal_ID

Indicates the terminal ID used when connecting to the OS 2200 Server.

connect_DPS_Logon

Terminal_ID

Indicates the terminal ID used when connecting to the OS 2200 Server.

Transaction_Code

Name of the DPS LOGON transaction.

Default: LOGON

UserID

A user ID defined in the DPS password file.

Password

The password defined for the above user ID.

Adding a connection when a fixed terminal ID is required

  1. Open the On Client Session Start event handler or any On event handler that needs the connection.

  2. Drag the Connect activity from the Toolbox to the Start node of the event handler.

  3. In the Properties window, select the connect_TerminalID server message for the Message property.

    The server message appears in the Server Messages node of the event.

Example: Adding a Connection with a User-solicited Terminal ID

  1. Create a client message that includes the Terminal_ID found in the connect_TerminalID message. Refer to the topic Creating Client Messages for more information.

  2. In the ePortal Message window, select the client message that you created in step 1, and drag it to the On Client Session Start event handler.

    This creates a ReplyToClient action.

    If a Connect activity already appears in the On Client Session Start event handler, delete it. In addition, delete the Receive and Reply activities if they exist.

  3. In the ePortal Message window, select the client message that you created in step 1, and drag it to the root of the orchestration tree.

    The On node is added to the tree and the client message appears in the Client Messages node of the event.

  4. Drag the Connect activity from the Toolbox to the Start node of the new event handler.

  5. In the Properties window, perform the following steps:

    1. Set the Message property to connect_TerminalID.

    2. Click the MessageData property and click the select button on the right.

    3. In the Assign From column for Terminal ID, select Variable.

      The Data Value column for the field is preset to the clientMessage.TerminalID.

  6. Click OK.

  7. Drag the ReceiveServer activity from the Toolbox to the Start node of the new event handler.

  8. Drag the ReplyToClient activity from the Toolbox to the Start node of the new event handler.

  9. In the Properties window set the Message property to Orch.Message.

Adding a Connection when a DPS Logon is Required

  1. Open the On Client Session Start event handler or any On event handler that needs the connection.

  2. Drag the Connect activity from the Toolbox to the Start node of the event handler.

  3. In the Properties window, select the connect_DPS_Logon server message for the Message property.

    The server message appears in the Server Messages node of the event.

Example: Adding a Connection with a User Solicited UserID and Password

  1. Create a client message that includes the necessary fields of the connect_DPS_Logon message. Refer to Creating Client Messages.

  2. In the ePortal Message window, select the client message that you created in step 1 and drag it to the On Client Session Start event handler.

    This creates a ReplyToClient action.

    If a Connect activity already appears in the On Client Session Start event handler, delete it. In addition, delete the Receive and Reply activities if they exist.

  3. In the ePortal Message window, select the client message created in step 1 and drag to the root of the orchestration tree.

    The On node is added to the tree and the client message appears in the Client Messages node of the event.

  4. Drag the Connect activity from the Toolbox to the Start node of the new event handler.

  5. In the Properties window, perform the following steps:

    1. Set the Message property to connect_DPS_Logon.

    2. Click the MessageData property and click the select button on the right.

    3. In the Assign From column for for both UserID and Password, select Variable.

      The Data Value columns for the fields are preset to clientMessage.UserID and clientMessage.Password, respectively.

    4. Optionally, repeat step c for Terminal ID and Transaction Code.

  6. Click OK.

  7. Drag the ReceiveServer activity from the Toolbox to the Start node of the new event handler.

  8. Drag the ReplyToClient activity from the Toolbox to the Start node of the new event handler.

  9. In the Properties window set the Message property to Orch.Message.