Consolidating Multiple Server Messages into One Client Message

There are several reasons that the consolidation into one client message might be desirable. The following are some possible reasons:

To return a client message that contains information from multiple server messages

In this example, a client message asks for information that requires many exchanges with the ClearPath server application. When all data is gathered, the resulting client message is returned.

  1. Ensure that all of the server messages that are needed in this logic are created.

  2. Create the following client messages. Refer to Creating Client Messages.

    • A client message that asks for the information.

    • A client message that is returned to the client that contains appropriate fields from many server messages.

  3. In the ePortal Message View window, select the client message that asks for the information, and drag it to the root of the orchestration tree. The On <client message name> node is added to the tree and the client message appears in the Client Messages node of the event.

  4. In the ePortal Message View window, select the server message that initiates the inquiry for the first information, such as a checking account, drag it to the Start node of the client event handler, and click InvokeServer. The Send property is set and the server message appears in the Server Messages node of the event.

  5. In the Properties window, do the following:

    1. Select the server message to be received in the Receive property. The server message appears in the Server Messages node of the event.

    2. Click the MessageData property, and click the selection button on the right.

    3. In the Assign Data for Message dialog box, ensure that the fields that came in the client message request are assigned to the appropriate fields in the server message sent to the ClearPath application. Refer to Assign Data for Message Dialog Box for details.

    4. Click OK.

  6. In the ePortal Message window, select that server message that initiates the inquiry for the second information, such as a passbook account, drag it to the Start Node of the client event handler, and click InvokeServer.

  7. In the Properties window, do the following:

    1. Select the server message to be received in the Receive property. The server message appears in the Server Messages node of the event.

    2. Click the MessageData property, and click the selection button on the right.

    3. In the Assign Data for Message dialog box, ensure that the fields that came in the client message request are assigned to the appropriate fields in the server message sent to the ClearPath application.

    4. Click OK.

  8. In the ePortal Message window, select the client message that must be returned to the client, and drag it to the Start node of the client event handle. This creates a ReplyToClient activity and the client message appears in the Client Messages node of the event.

  9. In the Properties window, do the following:

    1. Click the MessageData property, and click the selection button on the right.

    2. In the Assign Data for Message dialog box, ensure that the fields to be sent to the client are assigned.

    3. Click OK.

To return a client message that contains information from multiple returns of the same T27 server message.

In this example, the T27 application expects data to be received and then returns a result screen with a “+” in the action field. This screen is transmitted repeatedly to gather all information until the action field returns a “-“ to indicate there are no other records available.

  1. Ensure that all of the server messages that are needed in this logic are created.

  2. Create the following client messages. Refer to Creating Client Messages.

    • A client message that asks for the information.

    • A client message that is returned to the client that contains appropriate fields from many server messages.

  3. Do the following to create an array of fields that can hold the values being returned from the server application:

    1. Drag the appropriate data type from the Toolbox to the Variables node of the event.

    2. In the Properties window, set the IsArray property to True.

  4. In the ePortal Message View window, select the client message that asks for the information, and drag it to the root of the orchestration tree. The On <client message name> node is added to the tree and the client message appears in the Client Messages node of the event.

  5. In the ePortal Message View window, select the server message that initiates the inquiry for the information, such as a checking account, drag it to the Start node of the client event handler, and click InvokeServer. The Send property is set and the server message appears in the Server Messages node of the event.

  6. In the Properties window, do the following:

    • Select the server message to be received in the Receive property. The server message appears in the Server Messages node of the event.

    • Click the MessageData property, and click the selection button on the right.

    • In the Assign Data for Message dialog box, ensure that the fields that came in the client message request are assigned to the appropriate fields in the server message sent to the ClearPath application. Refer to Assign Data for Message Dialog Box for details.

    • Click OK.

  7. Drag the Assign activity from the Toolbox to the Start node of the event.

  8. In the Properties window, do the following:

    • In the AssignmentType property, set the value to Append.

    • In the From property, identify the received server message field to be copied.

    • In the To property, identify the client message to be returned to the client.

  9. Drag a structured activity, such as a DoWhile activity, to control looping.

  10. In the Properties window, in the Condition property, set the appropriate condition. Refer to the Edit Condition Dialog Box for more details.

  11. In the ePortal Message window, select the server message that is sent to the application to get more results, drag it to the DoWhile node of the client event handler, and click InvokeServer. The Send property is set and the server message appears in the Server Messages node of the event.

  12. In the Properties window, do the following:

    • Select the server message to be received in the Receive property. In this case, it is the same message as what was sent. The server message appears in the Server Messages node of the event.

    • Click the MessageData property, and click the selection button on the right.

    • In the Assign Data for Message dialog box, ensure that the fields that came in the client message request are assigned to the appropriate fields in the server message sent to the ClearPath application.

    • Click OK.

  13. Drag the Assign activity to the Start node of the client event handler.

  14. In the Properties window do the following:

    • In the AssignmentType property, ensure that the value is Append.

    • In the From property, identify the received server message field to be copied.

    • In the To property, identify the client message field to be returned to the client.

  15. In the ePortal Message window, select the client message that must be returned to the client, and drag it to the Start node of the client event handle. This creates a ReplyToClient activity and the client message appears in the Client Messages node of the event.

To return a client message that contains information from multiple returns of the same MCP COBOL server message.

In this example, the MCP COBOL application expects a data request that results in the execution of database FIND. The MCP COBOL program uses a COMS SEND and sets EGI when there are no other records to send. The ePortal runtime must be configured to expect an EGI to denote the last send.

  1. Ensure that all of the server messages that are needed in this logic are created.

  2. Create the following client messages. Refer to Creating Client Messages.

    • A client message that asks for the information.

    • A client message that is returned to the client with the results. Refer to "To create a client message that handles multiple outputs from the MCP application followed by an end-of-group indicator" in Creating Client Messages.

  3. In the ePortal Message View window, select the client message that asks for the information, and drag it to the root of the orchestration tree. The On <client message name> node is added to the tree and the client message appears in the Client Messages node of the event.

  4. In the ePortal Message View window, select that server message that initiates the inquiry for the information, such as a checking account, drag it to the Start node of the client event handler, and click InvokeServer. The Send property is set and the server message appears in the Server Messages node of the event.

  5. In the Properties window, do the following:

    • Select the server message to be received in the Receive property. The server message appears in the Server Messages node of the event.

    • Click the MessageData property, and click the selection button on the right.

    • In the Assign Data for Message dialog box, ensure that the fields that came in the client message request are assigned to the appropriate fields in the server message sent to the ClearPath application. Refer to Assign Data for Message Dialog Box for details.

    • Click OK. When the server message is sent to the MCP application, the ePortal COBOL runtime code issues multiple receives until the EGI indicator is received. At this point all data is sent to the client as items in an array.

  6. In the ePortal Message window, select the client message that must be returned to the client, and drag it to the Start node of the client event handle. This creates a ReplyToClient activity and the client message appears in the Client Messages node of the event.

  7. In the Properties window, click the MessageData property, and click the selection button on the right. When the Assign Data for Message dialog box appears, ensure that the client array is assigned, and click OK.