How to: |
This topic describes how to create a process flow with iWay Designer and bind it to the sample channel as a route. These instructions replace Defining a Route.
For details on the full features of iWay Designer, and additional information on using its capabilities, see the iWay Designer User's Guide.
You will complete the following high-level steps to define the route.
The Designer Project Information dialog box opens, prompting you for a project name and optional description.
In the Description field, type Defining a route for EDI inbound processing using iWay Designer to describe the project.
The Designer Project Bindings dialog box opens.
The iWay Process Configuration dialog box opens.
In the Description field, type Process flow for EDI route for channel for inbound processing.
The new EDI_Process_Flow node appears under the Processes folder, and the workspace displays a Start object.
You are ready to build the EDI_Process_Flow by adding objects to it and specifying their relationships.
The copy service redirects an output document to a destination.
The Service Name and Description dialog box opens.
The Service Type dialog box opens.
The Define Service dialog box opens.
Do not select the check box, since you do not want to use this service in other process flows.
The Properties dialog box opens.
The new EDI_PFlow_Copy Service object appears in the workspace.
Now you need to connect the Start object to the Copy Service object.
The Line Configuration dialog box opens.
This option indicates that there are no conditions that affect the path, and that the path between the two objects will always be followed.
A line appears between the objects to indicate that a relationship has been established.
All processing paths must terminate with an End object.
The End Name and Description dialog box opens.
The End Name Schema dialog box opens.
The Properties dialog box opens.
The new CopyEnd object appears in the workspace.
The Line Configuration dialog box opens.
This option indicates that there are no conditions that affect the path and that the path between the two objects will always be followed.
Your process flow will look similar to the following. The EDI_PFlow_Copy Service object is a unit of work that redirects the XML output to a defined destination through a custom emit. The CopyEnd object terminates this single process.
You can reposition the objects as desired.
You will add an acknowledgement Service object to return a functional acknowledgement (997) to the originator of the input document. The acknowledgement indicates that the input document was received and validated for structure. The acknowledgement does not indicate that business processing was performed on the document.
The Service Name and Description dialog box opens.
The Service Type dialog box opens.
The Define Service dialog box opens.
Do not select the check box, since you do not want to use this service in other process flows.
The Properties dialog box opens.
The new EDI_PFlow_Ack Service object appears in the workspace. The process flow will look similar to the following.
The Line Configuration dialog box opens.
A line appears between the objects to indicate that a relationship has been established.
All processing paths must terminate with an End object.
The End Name and Description dialog box opens.
The End Name Schema dialog box opens.
The Properties dialog box opens.
The new AckEnd object appears in the workspace.
The process flow is now complete. It will look similar to this.
Validating a process flow ensures that its structure is correct. Publishing a process flow makes it available in the Registry for use in channel configuration.
For instructions on validating and publishing the process flow, see the iWay Designer User's Guide.
Your next step is to add a new route to the Registry of the iWay Service Manager Administration Console and associate the process flow with it.
Parameter |
Value |
---|---|
Name * |
EDItoXML_Route_PFlow |
Description |
Route for EDI to XML using process flow. |
You are prompted for the type of component to associate with the route.
The route, with its associated process flow, has been successfully defined.
iWay Software |