A service flow project containing the following empty
subprojects:- Interface definition subproject
- Terminal applications subproject
- Nonterminal applications subproject
- Outbound Web services subproject
|
- This part is always created.
- You can specify custom names for the subprojects.
|
|
| A service interface for the service flow project. |
- You decide whether to create this part.
- You can create a basic service interface or import an interface definition
from a WSDL file (.wsdl), a COBOL file (.cbl, .cob, .cpy, .ccp), or a PL/I file (.pli, .inc, .mac).
|
|
| A flow containing a sequence of operations to be performed. |
- You decide whether to create this part.
- You can create:
- An empty flow.
- A flow containing empty nodes to be filled in later.
- A flow containing Invoke nonterminal nodes.
- A flow containing Invoke screen operation nodes.
|
|
| A flow containing a series of Invoke nonterminal nodes,
each node invoking a particular nonterminal application. |
- You specify the nonterminal applications.
- For each nonterminal application, you specify the name of the interface
operation file and the COBOL structures or PL/I structures for
the input and output messages.
|
|
- A host connection file, opened in the host editor.
- The opportunity to record a flow.
|
- You define the host connection properties.
- You record the flow.
|
|
| A flow containing a sequence of Invoke nodes, each of
which you can later associate with an operation or a flow. |
- You specify the number and order of Invoke nodes.
- You can select to have the wizard connect the Invoke nodes in the flow
or not.
|
|
| Your selections are stored and are later retrieved when
you run the New Generation Properties wizard. |
- Compiler information
- Storage layout
- Compile options
|
|