Processing patterns
Processing patterns support the deployment patterns that are used by service flow project tools to generate the service flows.
- Request processing patterns for simple service flows
Simple service flows conform to the single connector pattern. Simple service flows are processed in slightly different ways, depending on whether the service flow is persistent. If the service flow is not persistent, the command that DFHMADPL uses to create the navigation manager process has an additional option. - Reply processing pattern for a simple service flow
When a Link3270 or FEPI server adapter completes its processing, the application response is stored in a data-container called ADAPTER.OUTPUT. The status of the server adapter processing is also stored in a data-container called ADAPTER.STATUS. - Request processing patterns for complex service flows
Complex service flows conform to the aggregate connector pattern. Complex service flows are processed in slightly different ways, depending on whether the service flow is persistent. If the service flow is not persistent, the command that DFHMADPL uses to create the navigation manager process has an additional option. - Reply processing pattern for complex service flows
When each server adapter completes normally, it stores the application response and its status in data-containers and returns control to the flow navigator.
dfhcr_procpatterns.html |
Last updated: Sunday, 4 June 2017