The CA Gen DP applications communicate using a request/reply application protocol. The DPC invokes the DPS, providing the DPS with its Import View. With one exception, a DPS returns its Export View to the invoking DPC.
Note: The noted exception is covered as part of the USE ASYNC NO RESPONSE discussion.
From a Server Manager point of view, the request is a DPS Import View and the reply is a DPS Export View.
From a Window Manager point of view, the DPC populates data into a view matching the DPS Import View. The view then flows to the DPS when the DPC executes a cooperative flow (a Dialog Flow, Procedure Step USE or USE ASYNC). The inbound view data is placed into the DPS Import View on entry into the DPS code. The DPS executes and returns data to the DPC in the DPC view that was matched to the target DPS Export View.
Conceptually, server-to-server flows and user-written code behave the same as a Window Manager. They populate a view that matches the DPS Import View. They invoke the DPS with that view as input. The user-written code receives the DPS Export view as output on return from the DPS.
The following illustration depicts a generated Window Manager flowing to a target Server Manager using a Procedure Step USE action language statement. In this illustration, the DPC Import view has been matched to the DPS Import View, and the DPC Export View has been matched to the DPS Export View.
|
Copyright © 2014 CA.
All rights reserved.
|
|