12
Managing Business Processes and Roles

This chapter describes the business process and role management tasks required to design an integration. This chapter contains these topics:

• Business Process and Role Management Tasks Overview

• Business Process and Role Management Tasks Graphical View

• Business Process and Role Creation Methods

• Viewing the Metadata Modeling Diagrams

• Managing Business Processes

• Managing Role Types

• Managing Role Ports

• Managing Role Data Flow

• Managing Steps

• Managing Step Ports

• Managing Step Data Flow

• Managing Step Control Flow

• Managing Condition Expressions in Steps

• Designing Roles to Ensure Proper Validation

• Role Runtime Behavior

• Common User Errors

• Chapter Summary

  See Also: "Modeling Metadata Design" for conceptual details about business processes, role types, ports, data flows, steps, and control flows

Business Process and Role Management Tasks Overview

The Oracle Application Server ProcessConnect user interface tool enables you to perform the business process and role management tasks required for integrations. These tasks consist of managing the components in Figure 12-1 and Figure 12-2.

Figure 12-1 Business Process and Role Management Tasks (Part 1 of 2)

Text description of the illustration modelinga.gif

Figure 12-2 Business Process and Role Management Tasks (Part 2 of 2)

Text description of the illustration modeling2.gif

After design is complete and the integration is deployed, these components enable the business process to be executed and events to flow from role to role.

Table 12-1 describes each component shown in Figure 12-1 and Figure 12-2 and provides references for more information. You must perform these tasks to define the role type and business process portions of an integration.

Table 12-1  Role and Business Process Management Tasks

Key	Component	Description	See Section...
1	Business process	The business process spans all parties (each a separate spoke) in an integration to implement business logic and manage the movement of business events. Create one business process for an integration.	"Managing Business Processes" "Business Process"
1	Role types	Roles define how events are executed. Create at least one of each role type for each party participating in an integration (native role, translation binding role, application role, transformation binding role, and business role). These role types comprise a spoke.	"Managing Role Types" "Native-Level Concepts" "Application-Level Concepts" "Business-Level Concepts"
2	Role ports	Role ports represent an input or output parameter of a role containing events. Role ports of different roles are connected together by role data flow. This enables events to move from role to role. Create role ports for all role types.	"Managing Role Ports" "Role Ports"
3	Role data flows	Role data flows connect the role ports of roles together, which enable events to move through roles. Create role data flows for all role types.	"Managing Role Data Flow" "Data Flow"
4	Steps	Steps define the execution logic in a role. Create steps within all role types.	"Managing Steps" "Steps"
5	Step ports	Step ports work with data flows to connect steps inside roles together. Step ports also work with data flows to connect incoming role ports to incoming step ports and outgoing step ports to outgoing role ports. Create steps ports for all steps.	"Managing Step Ports" "Step Ports"
6	Step data flows	Step data flows connect the ports of steps together and the ports of steps and roles together. This enables events to move through steps and roles.	"Managing Step Data Flow" "Data Flow"
7	Step control flows	Control flows between steps indicate the execution order of steps. Control flows connect directly to steps and do not use step ports.	"Managing Step Control Flow" "Control Flow"

Business Process and Role Management Tasks Graphical View

The Oracle Application Server ProcessConnect user interface tool enables you to perform the management tasks shown in Figure 12-1 and Figure 12-2 and described in Table 12-1. Figure 12-3 through Figure 12-5 provide a high-level overview of the location of these management tasks within the Oracle Application Server ProcessConnect user interface tool, with references provided to the management task key number shown in Table 12-1. The locations of these management tasks are described in detail throughout this chapter.

Figure 12-3 displays the business process and role management tasks identified by key number one in Figure 12-1.

Figure 12-3 Business Process and Role Management Tasks Graphical View (Part 1 of 3)

Text description of the illustration modeling3.gif

The upper page of Figure 12-4 displays the data port, data flow group, and step management tasks identified by key numbers two, three, and four, respectively, in Figure 12-1. The lower page of Figure 12-4 displays the step port and step control flow management tasks identified by key numbers five and seven, respectively, in Figure 12-2.

Figure 12-5 displays the step data flow management tasks identified by key number six in Figure 12-2.

Figure 12-4 Business Process and Role Management Tasks Graphical View (Part 2 of 3)

Text description of the illustration modeling7.gif

Figure 12-5 Business Process and Role Management Tasks Graphical View (Part 3 of 3)

Text description of the illustration modeling10.gif

Business Process and Role Creation Methods

The Oracle Application Server ProcessConnect user interface tool provides two methods for creating business process and role modeling metadata:

• You can quickly create business process and role modeling metadata by using several modeling wizards that prompt you for answers to basic questions and, based on these answers, create the rest of the modeling metadata for you. This method is quicker, but does not provide you with the flexibility of manual creation. For example, you may want to create more complex steps in roles than those automatically created by the modeling wizards.

• You can manually create business process and role modeling metadata by following the procedures described in this chapter. These procedures enable you to define all parts of business process and role modeling metadata. This method offers flexibility, but takes time to complete.

Select a creation method based on your level of modeling metadata design expertise and the needs of your environment. A common method is to first use the modeling wizards to create the modeling metadata, including the business process and roles with default steps, ports, and data flows. You can then manually modify and create additional modeling metadata to add more complex processing.

Note: If you want to use data flow criteria, you can either manually create all roles or start with the Create Spoke wizard, delete the business role, and use data flow criteria with the existing business role

See Also: "Managing Role Data Flow" for details about data flow criteria Chapter 9, "Creating Metadata with the Modeling Wizards" for instructions on using the modeling wizards

Viewing the Metadata Modeling Diagrams

The Oracle Application Server ProcessConnect user interface tool includes several modeling metadata diagrams that provide a graphical view of your integration. As you create, update, or delete modeling metadata, these diagrams are updated to reflect your changes. Oracle recommends that you view these graphics frequently when creating or changing modeling metadata for an integration. Table 12-2 lists these diagrams and the locations from which they can be accessed. When you access these diagrams, additional options are provided for accessing more detailed graphical views of modeling metadata, and for creating, updating, and deleting modeling metadata.

Table 12-2  Accessing the Modeling Metadata Diagrams

Accessible From...	Integration Diagram	Process Diagram	Event Flow Diagram	Step Binding Diagram	See...
Diagram columns at top of Business Processes page	Yes	Yes	Yes	No	Upper page of Figure 12-15
Diagram columns at top of type Roles page where type is either Native, Application, Business, or Binding	Yes	Yes	Yes	No	Upper page of Figure 12-16
Links at bottom of Business Process Details : name page where name is the business process name	Yes	Yes	Yes	No	Lower page of Figure 12-15
Links at bottom of type Role Details : name page	Yes	Yes	Yes	No	Lower page of Figure 12-16
Links at bottom of Data Port Details : name page (for role ports)	No	Yes	Yes	No	Lower page of Figure 12-17
Links at bottom of Data Flow Group Details : name page	Yes	No	Yes	No	"Viewing a Role Data Flow"
Links at bottom of Step Details : name page	No	Yes	Yes	Yes	"Viewing a Step"
Links at bottom of Data Port Details : name page (for step ports)	No	Yes	Yes	Yes	"Viewing a Step Port"

Accessing the Metadata Modeling Diagrams

Follow these instructions to access the metadata modeling diagrams:

• Accessing the Diagrams from the Business Processes or Roles Pages

• Accessing the Diagrams from the Business Process Details : Name and Role Name Pages

• Accessing the Diagrams from the Data Port Details : Name Page (For Role Ports)

• Accessing the Diagrams from the Data Flow Group Details : Name Page

• Accessing the Diagrams from the Step Details : Name Page

• Accessing the Diagrams from the Data Port Details : Name Page (For Step Ports)

• Accessing Diagram Details

Accessing the Diagrams from the Business Processes or Roles Pages

1. Select the Modeling tab.

2. Select to view either a business process or role.

   To View a...	Select the...	Go To Step...
   Business Process	Business Processes tab to access the Business Processes page	4
   Role	Roles tab to access the Business Roles page	3

3. If you want to view a specific type of role, select one of the following types at the top of the page:
   • Application Roles

   • Native Roles

   • Binding Roles

4. Select the metadata modeling diagram to view from the Integration Diagram, Event Flow Diagram, or Process Diagram column at the top of the page.

5. See "Accessing Diagram Details" to access diagram details about your selection.

Accessing the Diagrams from the Business Process Details : Name and Role Name Pages

1. Follow the instructions in "Accessing the Diagrams from the Business Processes or Roles Pages" to access the Business Processes or Roles page.

2. Select a specific business process or role in the Name column.

3. Select the metadata modeling diagram to view from the Integration Diagram, Event Flow Diagram, or Process Diagram links at the bottom of the page.

4. See "Accessing Diagram Details" to access diagram details about your selection.

Accessing the Diagrams from the Data Port Details : Name Page (For Role Ports)

1. Follow the instructions in "Accessing the Diagrams from the Business Processes or Roles Pages" to access the Business Processes or Roles page.

2. Select a specific business process or role in the Name column.

3. Select a specific role port in the Name column of the Data Ports section.

4. Select the Event Flow Diagram or Process Diagram links at the bottom of the page.

5. See "Accessing Diagram Details" to access diagram details about your selection.

Accessing the Diagrams from the Data Flow Group Details : Name Page

1. Follow the instructions in "Accessing the Diagrams from the Business Processes or Roles Pages" to access the Business Processes or Roles page.

2. Select a specific business process or role in the Name column.

3. Select a specific role port in the Name column of the Data Flow Groups section.

4. Select the metadata modeling diagram to view from the Integration Diagram or Event Flow Diagram links at the bottom of the page.

5. See "Accessing Diagram Details" to access diagram details about your selection.

Accessing the Diagrams from the Step Details : Name Page

1. Follow the instructions in "Accessing the Diagrams from the Business Processes or Roles Pages" to access the Business Processes or Roles page.

2. Select a specific business process or role in the Name column.

3. Select a specific step in the Name column of the Steps section.

4. Select the metadata modeling diagram to view from the Process Diagram, Event Flow Diagram, or Step Binding Diagram list at the bottom of the page.

5. See "Accessing Diagram Details" to access diagram details about your selection.

Accessing the Diagrams from the Data Port Details : Name Page (For Step Ports)

1. Follow the instructions in "Accessing the Diagrams from the Business Processes or Roles Pages" to access the Business Processes or Roles page.

2. Select a specific business process or role in the Name column.

3. Select a specific step in the Name column of the Steps section.

4. Select a specific step port in the Name column of the Data Ports section.

5. Select the metadata modeling diagram to view from the Process Diagram, Event Flow Diagram, or Step Binding Diagram links at the bottom of the page.

6. See "Accessing Diagram Details" to access diagram details about your selection.

Accessing Diagram Details

See the following sections for details about the diagram type you selected:

If You Selected...	Description	See...
Integration Diagram	Displays the roles and business process in an integration	"Viewing an Integration Diagram"
Event Flow Diagram	Displays events moving through the selected business process or role	"Viewing an Event Flow Diagram"
Process Diagram	Displays events, steps, ports, data flows, and control flows for the selected business process or role	"Viewing a Process Diagram"
Step Binding Diagram	Displays the current state of a step, including its step ports, role ports, and data flows	"Viewing a Step Binding Diagram"

Viewing an Integration Diagram

Follow these instructions to view an Integration Diagram:

To view an Integration Diagram:

1. Ensure that you followed the instructions in "Accessing the Metadata Modeling Diagrams" to access the page for viewing an Integration Diagram.

   The Integration Diagram displays the selected business process or role. Figure 12-6 shows the Integration diagram for the approve-BP business process early in the design stage.

   Figure 12-6 Early Stages of Integration Diagram

   

   Text description of the illustration modeling26.gif

   As you add additional roles, these changes are reflected in the Integration Diagram. For example, creating two spokes of roles, role ports, data flows, steps, step ports, and control flow with the business process approve-BP in the middle causes the changes shown in Figure 12-7 to display in the Integration Diagram.

   Figure 12-7 Later Stages of Integration Diagram

   

   Text description of the illustration modeling27.gif

2. If the native role in your integration is currently part of an agreement (notification-NR in this example), click the Agreement icon beneath the Agreement header to display the details page for the agreement. (See left side of Figure 12-7.) If the native role is not currently part of an agreement (approval-NR in this example), only the Agreement header appears. (See right side of Figure 12-7.)

3. View specific details or select a task from the Action list of the Diagram Actions section and click a role in the diagram:

   Action	Description	See Section...
   Display Details (default selection)	Displays the details page for the role or business process	"Viewing a Business Process" or "Viewing a Role"
   Drill Down to Event Flow diagram	Displays the Event Flow Diagram for the selected role or business process	"Viewing an Event Flow Diagram"
   Drill Down to Process Diagram	Displays the Process Diagram for the selected role or business process	"Viewing a Process Diagram" or "Viewing a Role"
   Create Spoke	Starts the Create Spoke wizard, which enables you to create a single spoke (extending from the native role to this business process) and a single event flow	"Creating a Single Spoke"
   Delete Spoke	Deletes the spoke of which this business process or role is a part. The business process is not deleted. Note: Select a role to delete other than the business process. This is because the business process does not uniquely define a spoke. (It is in the middle of several spokes.)	"Deleting a Spoke"

   Note: Enter a value in the Scale (%) field of the Display Options section and click Refresh to adjust the diagram size. This is beneficial when the size of the diagram is too large to fit on one page.

4. Check the Integration Diagram frequently as you create modeling metadata. This helps ensure that you create and connect all of the necessary roles.

Viewing an Event Flow Diagram

Follow these instructions to view an Event Flow Diagram:

To view an Event Flow Diagram:

1. Ensure that you followed the instructions in "Accessing the Metadata Modeling Diagrams" to access the page for viewing an Event Flow Diagram.

   The Event Flow Diagram displays the selected business process or role. Figure 12-8 shows the Event Flow diagram for the approve-BP business process early in the design stage.

   Figure 12-8 Early Stages of Event Flow Diagram

   

   Text description of the illustration modeling21.gif

   As you create additional roles and role steps, these changes are reflected in the Event Flow Diagram. For example, if you perform the following tasks:

   • Create an approval-BR business role, approval-TX transformation binding role, and approval-AR application role

   • Create appropriate steps inside all three roles and the business process

   • Connect all roles and steps with ports and data flows

     These tasks cause the changes shown in Figure 12-9 to display in the Event Flow Diagram. Incomplete modeling metadata displays in red, such as a business event with no event body element or a transformation step with no defined event transformation maps. You must complete this modeling metadata before it can be included in a deployed configuration.

   Figure 12-9 Later Stages of Event Flow Diagram

   

   Text description of the illustration modeling24.gif

2. View specific details or select a task from the Action list in the Diagram Actions section and click a step or a role in the diagram. The Event Flow Diagram provides several options for viewing different aspects of the integration.

   Action	Description
   Display Details (default selection)	Displays the details page for the selected role, step, business event, or adapter interaction
   Drill Down to Process or Step Binding diagram	Displays the Process Diagram if you click a role or the Step Binding Diagram if you click a step or port
   Create Spoke	Starts the Create Spoke wizard, which enables you to create a single spoke (extending from the native role to the business process) and a single event flow
   Add Event Flow	Starts the Add Event Flow wizard, which enables you to add an additional event flow to a single spoke extending from the native role to the business process
   Add End-To-End Basic Event Flow	Starts the Add End-To-End Basic Event Flow wizard, which enables you to add an event flow to two existing spokes
   Delete Spoke	Deletes the spoke of which this business process or role is a part. The business process is not deleted; you must separately delete it. Note: Select a role to delete other than the business process. This is because the business process does not uniquely define a spoke. (It's in the middle of several spokes.)

3. Perform other appropriate tasks in the Display Options section and click Refresh:

   Action	Description
   Show	Select either of the following: All Roles in Two Spokes Displays all roles, steps, and events in two spokes (this diagram can be very long) Role and Adjacent Roles Displays the selected role and both of the role's adjacent role neighbors
   Role Contents	Select either of the following: Steps (Simple) Displays simple steps in the role. Simple steps have only one input data flow from a role port and one output data flow to a role port. For more complicated steps, only the role port appears. Ports Displays all inbound and outbound ports for the roles Complete Process Diagram Displays a comprehensive view of modeling metadata, including all steps, data flows, control flows, and ports. This creates a large diagram that can take a long time to appear.
   Scale	Enter a value in the Scale (%) field to adjust the diagram size. This is beneficial when the size of the diagram is too large to fit on one page. A smaller scale also helps performance because the smaller the diagram, the more quickly it displays onscreen.

4. If you have created multiple spokes using the same business process that you want to view, the two spokes that initially display are based on how you accessed the Event Flow Diagram. For example, if you performed the following steps:
   • Clicked on a role in the Integration Diagram, the spoke that includes that role and a default spoke appear.

   • Added an event flow using the modeling wizards, the spokes included in that event flow appear.

5. Perform the following steps to display additional spokes:
   1. Select All Roles in Two Spokes from the Show list.

   2. Click Refresh.

      The Event Flow Diagram refreshes to display the Spoke (left side) and Spoke (right side) lists.

      

      Text description of the illustration modeling28.gif

      Both lists display the same native roles of the current business process.

   3. Select the native roles of the spokes you want to view from both lists.

   4. Click Refresh.

      The Event Flow Diagram refreshes to show the two selected spokes.

6. If you want to view a specific role and its adjacent roles in a spoke, perform the following step:
   1. Select Role and Adjacent Roles from the Show list.

   2. Click Refresh.

      The Event Flow Diagram refreshes to display the Role list.

      

      Text description of the illustration modeling18.gif

   3. Select the role to view.

   4. Click Refresh.

      The Event Flow Diagram refreshes to show the selected role and its adjacent neighbor roles.

7. Check the Event Flow Diagram and its diagram tasks and display options frequently as you create modeling metadata. This helps ensure that you create and connect all of the necessary events, roles, and role steps.

   Note: A link at the bottom of the Event Flow Diagram enables you to access the Integration Diagram.

Viewing a Process Diagram

Follow these instructions to view a Process Diagram:

To view a Process Diagram:

1. Ensure that you followed the instructions in "Accessing the Metadata Modeling Diagrams" to access the page for viewing a Process Diagram.

   When fully created, the Process Diagram displays events, steps, ports, data flows, and control flows for the selected business process or role. Figure 12-10 shows the Process Diagram for the approve-BP business process early in design.

   Figure 12-10 Early Stages of Process Diagram

   

   Text description of the illustration modeling14.gif

   Note: Each business process or role automatically includes a Start and End step.

   As you add steps, ports, data flows, and control flows to the business process or role, these changes are reflected in the Process Diagram. Unbound step and role ports for which data flow is not yet defined (such as return code ports of transformation, translation, or condition steps) appear. For example, creating the SetParty step, role data flows, step data flows, control flows, and events causes the changes shown in Figure 12-11 to display in the Process Diagram.

   Figure 12-11 Later Stages of Process Diagram

   

   Text description of the illustration modeling17.gif

   Incomplete modeling metadata displays in red, such as unbound step ports with no defined data flows or a SetParty step in a business process that must be updated with a destination party. You must complete this modeling metadata before it can be included in a deployed configuration.

2. View specific details in the Process Diagram or select a task from the Action list in the Diagram Actions section and click the step or port that you want to manage in the role:

   Action	Description	See Also
   Display Details (Step or Port)	Click the step, step port, or role port to display the details page for a step or port.	"Viewing a Step" "Viewing a Step Port" "Viewing a Role Port"
   Drill Down to Step Bindings Diagram	Click the step, step port, or role port to display the Step Binding Diagram.	"Viewing a Step Binding Diagram"
   Create Step	Click the step after which you want the new step inserted.	"Creating a Step"
   Create Step Port	Click the step or step port to display the page for creating a step port. If you click a role port, an error message appears.	"Creating a Step Port"
   Create Role Port	Click anywhere to display the page for creating a role port.	"Creating a Role Port"
   Update (Step or Port)	Click the step, step port, or role port to display the page for updating a step, step port, or role port, respectively.	"Updating a Step" "Updating a Step Port" "Updating a Role Port"
   Delete (Step or Port)	Click the step, step port, or role port to display the page for deleting a step, step port, or role port, respectively.	"Deleting a Step" "Deleting a Step Port" "Deleting a Role Port"
   Create Data Flow	Click the unbound step port or role port (such as a return code port) to display the page for creating a data flow to another port. If the port is already data flow-bound, an error message appears. If you click a step, the step details page displays all data ports for this step. You must choose the port for which to create a data flow.	"Creating a Data Flow Between a Role Port and a Step Port" "Creating a Role Data Flow Group" "Creating a Step Data Flow"
   Delete Data Flow	Click the step port or role port to display the details page for your selection. From this page, choose the data flow to delete. Click the step to display the details page for the step. From this page, choose the port, then choose the data flow to delete.	"Deleting a Data Flow Between a Role Port and a Step Port" "Deleting a Role Data Flow" "Deleting a Step Data Flow"
   Create Control Flow	Click the step or step port to display the page for creating a control flow to another step. If you click a role port, an error message appears.	"Creating a Step Control Flow"
   Delete Control Flow	Click the step or step port to display the details page for your selection. From this page, choose the control flow to delete. If you click a role port, an error message appears.	"Deleting a Step Control Flow"

   When you click Apply or Cancel on an action page (create, update, or delete page) you are returned to the Process Diagram. A confirmation or error message appears at the top of the diagram to indicate whether the apply action was successful or not. If successful, the diagram reflects the modification that was made.

3. Perform other appropriate tasks in the Display Options section:

   Action	Description
   Show Event and Datatype Names (default selection)	Displays the event and datatype names used in the business process or role (for example, displays the incoming and outgoing events). This is a larger diagram because all names appear. If you deselect this box, the event and datatype names do not appear.
   Scale	Enter a value in the Scale (%) field and click Refresh to adjust the diagram size. This is beneficial when the size of the diagram is too large to fit on one page. A smaller scale also helps performance because the smaller the diagram, the more quickly it displays onscreen.

   Note: Links at the bottom of the Process Diagram also enable you to access the Integration Diagram and Event Flow Diagram.

4. Check the Process Diagram frequently as you create modeling metadata. This helps ensure that you create and connect all of the necessary steps, data flows, and control flows in a business process or role.

Viewing a Step Binding Diagram

Follow these instructions to view a step binding diagram:

To view a step binding diagram:

1. Ensure that you followed the instructions in "Accessing the Metadata Modeling Diagrams" to access the page for viewing a step binding diagram.

   The Step Binding Diagram page displays the current state of a step, including its step ports, role ports, and data flows. In Figure 12-12, the SetParty step displays early after creation. A destination party has been set in the SetParty step (named Human Resources), but no events or data flows have been defined.

   Figure 12-12 Early Stages of Step Binding Diagram

   

   Text description of the illustration modeling29.gif

   As you add additional steps, step ports, role ports, and role data flow to an integration, these changes are reflected in the Step Binding Diagram. For example, creating the FailureNotification-IN and FailureNotification-OUT step ports and role ports, and connecting these step ports to these role ports with role data flows causes the changes shown in Figure 12-13 to display in the Step Binding Diagram.

   Figure 12-13 Later Stages of Step Binding Diagram

   

   Text description of the illustration modeling30.gif

2. View specific details or select a task and click an element in the diagram:

   Action	Description	See Also
   Display Details (Step or Port)	Click the step, step port, or role port to display the details page for a step or port.	"Viewing a Step" "Viewing a Step Port" "Viewing a Role Port"
   Display Another Step Bindings Diagram	Click to display the step binding diagram for the selected step	This section
   Create Step Port	Click the step or step port to display the page for creating a step port. If you click a role port, an error message appears.	"Creating a Step Port"
   Update (Step or Port)	Click the step, step port, or role port to display the page for updating a step, step port, or role port, respectively.	"Updating a Step" "Updating a Step Port" "Updating a Role Port"
   Delete (Step or Port)	Click the step, step port, or role port to display the page for deleting a step, step port, or role port, respectively.	"Deleting a Step" "Deleting a Step Port" "Deleting a Role Port"
   Create Data Flow	Click the unbound step port or role port (such as a return code port) to display the page for creating a data flow to another port. If the port is already data flow-bound, an error message appears. If you click a step, the step details page displays all data ports for this step. You must choose the port for which to create a data flow.	"Creating a Data Flow Between a Role Port and a Step Port" "Creating a Role Data Flow Group" "Creating a Step Data Flow"
   Delete Data Flow	Click the step port or role port to display the details page for your selection. From this page, choose the data flow to delete. Click the step to display the details page for the step. From this page, choose the port, then choose the data flow to delete.	"Deleting a Data Flow Between a Role Port and a Step Port" "Deleting a Role Data Flow" "Deleting a Step Data Flow"

   Note: Enter a value in the Scale (%) field of the Display Options section and click Refresh to adjust the diagram size. This is beneficial when the size of the diagram is too large to fit on one page.

   When you click Apply or Cancel on an action page (create, update, or delete page) you are returned to the Step Binding Diagram. A confirmation or error message appears at the top of the diagram to indicate whether the apply action was successful or not. If successful, the diagram reflects the modification that was made.

3. Check the Step Binding Diagram frequently as you create modeling metadata. This helps ensure that you create and connect all of the necessary steps, step ports, role ports, and role data flow.

Managing Business Processes

The Oracle Application Server ProcessConnect user interface tool enables you to perform the business process management tasks shown in Figure 12-14 and Figure 12-15. These tasks are described in detail in this section. The business process is the center of the integration and implements the business logic and manages business events. The business process hides the unique characteristics of each party in an integration. The business process can contain all types of steps except translation steps. Ports in business processes can only be bound to business events. No port in a business process can be bound to a native event or application event.

Figure 12-14 Business Process Management Tasks (Part 1 of 2)

Text description of the illustration modeling19.gif

Selecting a business process in the Name column causes a details page such as that shown in Figure 12-15 to appear.

Figure 12-15 Business Process Management Tasks (Part 2 of 2)

Text description of the illustration modeling31.gif

Table 12-3 identifies the business process management tasks shown in Figure 12-14 and Figure 12-15 and provides references to procedures for performing these tasks.

Table 12-3  Business Process Management Tasks

Business Processes Page Elements	Management Task	First See Section...	Then See Section...
Shortcuts section in Business Processes page of Figure 12-14	Take a shortcut to: Create modeling metadata with the modeling wizards Manage event types and datatypes	N/A	"Modeling Wizards Concepts Overview" "Managing Business Datatypes" "Importing XSD Datatypes" "Managing Business Event Types"
Create button in Business Processes page of Figure 12-14	Create a business process	"Accessing Business Process Management Tasks"	"Creating a Business Process"
Delete column in Business Processes page of Figure 12-14	Delete a business process		"Deleting a Business Process"
Update column in Business Processes page of Figure 12-14	Update a business process		"Updating a Business Process"
Name column in Business Processes page of Figure 12-14 (To access the details page shown in Figure 12-15)	View details about a business process		"Viewing a Business Process"

Note: The Oracle Application Server ProcessConnect user interface tool views business processes and roles as the same type of component. Therefore, most pages for managing the steps, ports, data flows, and control flows of a business process begin with the word Role.

See Also: "Business Process" for conceptual details about business processes

Accessing Business Process Management Tasks

Follow these instructions to access the business process management tasks shown in Figure 12-14 and Figure 12-15:

To access business process management tasks:

1. Select the Modeling tab.

2. Select the Business Processes tab.

   The Business Processes page appears. (See Figure 12-14.)

3. Select a task to perform and see the referenced section for instructions:

   To...	Then...	See Section...
   Create a business process	Click Create.	"Creating a Business Process"
   Delete a business process	Select a specific business process in the Delete column.	"Deleting a Business Process"
   Update a business process	Select a specific business process in the Update column.	"Updating a Business Process"
   View details about a business process	Select a specific business process in the Name column.	"Viewing a Business Process"

Creating a Business Process

Follow these instructions to create a business process:

To create a business process:

1. Ensure that you followed the instructions in "Accessing Business Process Management Tasks" to access the page for creating a business process.

   The Create Business Process page appears.

2. Enter a unique and recognizable name for the business process in the Name field (for example, approve-BP).

3. Enter an optional description in the Description field.

4. Click Apply.

   The business process is created and the Business Process Details : name page for the new business process appears. This page enables you to manage ports, data flows, and steps, and view diagrams of the business process. From the step page (accessible from the Business Process Details : name page), you can manage step ports, step data flows, and step control flows.

5. View a graphical status of the business process by selecting the following diagrams at the bottom of the Business Process Details : name page.

   Diagram	See Section...
   Integration Diagram	"Viewing an Integration Diagram"
   Event Flow Diagram	"Viewing an Event Flow Diagram"
   Process Diagram	"Viewing a Process Diagram"

Deleting a Business Process

Follow these instructions to delete a business process:

Caution: Deleting a business process also deletes any associated steps, data ports, data flow groups, and control flow.

To delete a business process:

1. Ensure that you followed the instructions in "Accessing Business Process Management Tasks" to access the page for deleting a business process.

2. Click Yes when prompted to delete a business process.

   The business process is deleted and the Business Processes page appears.

Updating a Business Process

Follow these instructions to update a business process:

To update a business process:

1. Ensure that you followed the instructions in "Accessing Business Process Management Tasks" to access the page for updating a business process.

   The Update Business Process page appears.

2. Make appropriate changes. (See Step 2 through Step 3 of "Creating a Business Process" for a list of fields that you can update.)

3. Click Apply.

   The business process is updated and the Business Process Details : name page for the updated business process appears.

Viewing a Business Process

Follow these instructions to view details about a specific business process:

To view a business process:

1. Ensure that you followed the instructions in "Accessing Business Process Management Tasks" to access the page for viewing a business process.

   The Business Process Details : name page appears for the selected business process.

   

   Text description of the illustration modeling32.gif

2. View specific details, including the role ports (under the Data Ports section), data flow (under the Data Flow Groups section), and steps (under the Steps section) associated with this business process. This page, as with the Business Processes page shown in Figure 12-14, enables you to delete or update the selected business process.

3. Click Return to List to return to the Business Processes page.

Managing Role Types

The Oracle Application Server ProcessConnect user interface tool enables you to perform the role management tasks shown in Figure 12-16. These tasks are described in detail in this section. Each task applies to all roles, regardless of the role type you are creating. Regardless of whether you are managing a native, application, business, translation binding, or transformation binding role, the same management pages appear. Only the page titles are different.

Figure 12-16 Role Management Tasks

Text description of the illustration modeling33.gif

This section briefly describes each role type you can create:

• Native Role

• Translation Binding Role

• Application Role

• Transformation Binding Role

• Business Role

Native Role

Native roles manage the interaction between native events. Pass-through steps and consume steps are typically used in native roles. Since the syntax of a native event is not known to Oracle Application Server ProcessConnect, transformations, conditions, and other steps cannot be performed. In most cases, the native event is passed through to the binding role for translation. Native roles can also be used to ignore native events that are not necessary for the integration (for example, acknowledgment events being sent as part of a protocol). In such cases, a consume step can be used in the native role to consume (prevent further processing from occurring) the event and not pass it onto the translation binding role.

Ports in native roles can only be bound to native events. No port in a native role can be bound to an application event or business event.

See Also: "Native Roles"

Translation Binding Role

Translation binding roles operate as a bridge between native and application roles. This role translates the native event to an application event, and vice versa. This role can also consume native events and perform error processing for translations. For this reason, a translation binding role typically contains translation steps, consume steps, and conditions steps.

Additionally, a translation binding role can generate acknowledgments. In these cases, the translation binding role can contain transformation steps and split steps.

See Also: "Translation Binding Role"

Application Role

As with native events, application events are processed in a specific order. The order is determined by the construction of the application role. The application role usually contains pass-through steps and consume steps. Application roles can also generate acknowledgments instead of the translation binding role. Application role ports can only be bound to application events. No port in an application role can be bound to a native event or business event.

See Also: "Application Roles"

Transformation Binding Role

Transformation binding roles act as a bridge between business roles and application roles. This role transforms an application event to a business event, and vice versa. This role can also consume application events and perform the error processing for transformations. For this reason, a transformation binding role typically contains transformation steps, consume steps, split steps, and condition steps. A transformation binding role can also be used in event addressing (using event header rules) and in the creation of new events.

Transformation binding role ports that are bound to an application role through a data flow can only be connected to application events. Transformation binding role ports bound to a business role through a data flow can only be connected to business events.

See Also: "Transformation Binding Role"

Business Role

As with native events and application events, business events must be processed in a predetermined order. A business role describes the processing of business events. The business role also isolates the business process from the rest of the processing and determines the branching of events (see data flow criteria). The business role typically contains pass-through steps and consume steps. This role can also contain transformation steps to generate new business events.

Business role ports can only be bound to business events. No port in a business role can be bound to a native event or application event.

See Also: "Business Roles"

Table 12-4 identifies the role management tasks shown in Figure 12-16 and provides references to procedures for performing these tasks.

Table 12-4  Role Management Tasks

Roles Page Elements	Management Task	First See Section...	Then See Section...
Shortcuts section in Native Roles page of Figure 12-16	Take a shortcut to: Create business process and role metadata with the modeling wizards Manage event types and datatypes	N/A	"Modeling Wizards Concepts Overview" "Managing Native Event Types"
Create button in Native Roles page of Figure 12-16	Create a role	"Accessing Role Management Tasks"	"Creating a Role"
Delete column in Native Roles page of Figure 12-16	Delete a role		"Deleting a Role"
Update column in Native Roles page of Figure 12-16	Update a role		"Updating a Role"
Name column in Native Roles page of Figure 12-16 (To access the details page shown in the lower page of Figure 12-16)	View details about a role		"Viewing a Role"

See Also: The following sections for conceptual details about the different roles types: "Native Roles" "Application Roles" "Translation Binding Role" "Business Roles" "Transformation Binding Role"

Accessing Role Management Tasks

Follow these instructions to access the role management tasks shown in Figure 12-16:

To access role management tasks:

1. Select the Modeling tab.

2. Select the Roles tab.

   The Business Roles page appears by default.

3. If you want to manage a role other than a business role, select one of the following types at the top of the page:
   • Application Roles

   • Native Roles

   • Binding Roles

4. Select a task to perform and see the referenced section for instructions:

   To...	Then...	See Section...
   Create a role	Click Create.	"Creating a Role"
   Delete a role	Select a specific role in the Delete column.	"Deleting a Role"
   Update a role	Select a specific role in the Update column.	"Updating a Role"
   View details about a role	Select a specific role in the Name column.	"Viewing a Role"

Creating a Role

Follow these instructions to create a role:

To create a role:

1. Ensure that you followed the instructions in "Accessing Role Management Tasks" to access the page for creating a role.

   The Create type Role page appears.

   where type is native, application, binding, or business.

2. Enter a unique and recognizable name for the role in the Name field (for example, expense-NR).

3. Enter an optional description in the Description field.

4. Click Apply.

   The role is created and the type Role Details : name page for the new role appears. This page enables you to manage ports, data flows, and steps, and view diagrams of the role. From the step page (accessible from the type Role Details : name page), you can manage step ports, step data flows, and step control flows.

5. View a graphical status of the role by selecting the following diagrams at the bottom of the type Role Details : name page.

   Diagram	See Section...
   Integration Diagram	"Viewing an Integration Diagram"
   Event Flow Diagram	"Viewing an Event Flow Diagram"
   Process Diagram	"Viewing a Process Diagram"

6. Repeat these steps to create any necessary translation binding, application, transformation binding, and business roles.

Deleting a Role

Follow these instructions to delete a role:

Caution: Deleting a role also deletes any associated steps, data ports, data flow groups, and control flow.

To delete a role:

1. Ensure that you followed the instructions in "Accessing Role Management Tasks" to access the page for deleting a role.

2. Click Yes when prompted to delete a role.

   The role is deleted and the type Role page appears.

Updating a Role

Follow these instructions to update a role:

To update a role:

1. Ensure that you followed the instructions in "Accessing Role Management Tasks" to access the page for updating a role.

   The Update type Role page appears.

2. Make appropriate changes. (See Step 2 through Step 3 of "Creating a Role" for a list of fields that you can update.)

3. Click Apply.

   The role is updated and the type Role Details : name page for the updated role appears.

Viewing a Role

Follow these instructions to view details about a specific role:

To view a role:

1. Ensure that you followed the instructions in "Accessing Role Management Tasks" to access the page for viewing a role.

   The type Role Details : name page appears for the selected role (in this example, a native role).

   

   Text description of the illustration modeling34.gif

2. View specific details, including the role ports (under the Data Ports section), data flow (under the Data Flow Groups section), and steps (under the Steps section) associated with this role.

   This page, as with the type Roles page shown in the upper figure of Figure 12-16, enables you to delete or update the selected role.

3. Click Return to List to return to the type Roles page.

Managing Role Ports

The Oracle Application Server ProcessConnect user interface tool enables you to perform the role port management tasks shown in Figure 12-17. These tasks are described in detail in this section. Role ports represent an input or output parameter of a role containing events. Role ports of roles are connected together by role data flow. This enables events to move from role to role.

Figure 12-17 Role Port Management Tasks (Part 1 of 2)

Text description of the illustration modeling35.gif

Selecting a role port in the Name column of the Data Ports section causes a details page such as that shown in Figure 12-18 to appear.

Figure 12-18 Role Port Management Tasks (Part 2 of 2)

Text description of the illustration modeling4.gif

Table 12-5 identifies the role port management tasks shown in Figure 12-17 and Figure 12-18 and provides references to procedures for performing these tasks.

Table 12-5  Role Port Management Tasks

Page Elements	Management Task	First See Section...	Then See Section...
Create button in Data Ports section of Figure 12-17	Create a role port	"Accessing Role Port Management Tasks"	"Creating a Role Port"
Delete column in Data Ports section of Figure 12-17	Delete a role port		"Deleting a Role Port"
Update column in Data Ports section of Figure 12-17	Update a role port		"Updating a Role Port"
Name column in Data Ports section of Figure 12-17 (To access details page shown in Figure 12-18)	View details about a role port		"Viewing a Role Port"
Create button in Data Flows Within Role section of Figure 12-18	Create a data flow between a role port and a step port		"Creating a Data Flow Between a Role Port and a Step Port"
Delete column in Data Flows Within Role section of Figure 12-18	Delete a data flow between a role port and a step port		"Deleting a Data Flow Between a Role Port and a Step Port"

See Also: "Role Ports" for conceptual details about role ports "Creating a Role Data Flow Group" for creating a data flow between roles like that shown in the Data Flows Between Roles section of the Data Port Details : name page shown in Figure 12-18 The Manage Role Ports section of Figure 12-1 for the graphical location of role ports

Accessing Role Port Management Tasks

Follow these instructions to access the role port management tasks shown in Figure 12-17 and Figure 12-18:

To access role port management tasks:

1. Select the Modeling tab.

2. Select the appropriate tab:

   If You Select the...	This Page Appears...	Go To Step...
   Roles tab	Business Roles page	3
   Business Processes tab	Business Processes page	4

3. If you want to manage a role other than a business role, select one of the following types at the top of the page:
   • Application Roles

   • Native Roles

   • Binding Roles

4. Select the specific role or business process on which to manage role ports in the Name column.

   The details page for the selected role or business process appears.

5. Go to the Data Ports section. (See Figure 12-17.)

6. Select a task to perform and see the referenced section for instructions:

   To...	Then...	See Section...
   Create a role port	Click Create.	"Creating a Role Port"
   Delete a role port	Select a specific role port in the Delete column.	"Deleting a Role Port"
   Update a role port	Select a specific role port in the Update column.	"Updating a Role Port"
   View details about a role port	Select a specific role port in the Name column.	"Viewing a Role Port"
   Create a data flow within a role	Select a specific role port in the Name column with which to create a data flow with a step port.	"Creating a Data Flow Between a Role Port and a Step Port"
   Delete a data flow within a role	Select a specific role port in the Name column from which to delete a data flow with a step port.	"Deleting a Data Flow Between a Role Port and a Step Port"

   You can also manage some aspects of role ports from within a Process Diagram or Step Binding Diagram.

   See Also: "Viewing a Process Diagram" and "Viewing a Step Binding Diagram" for details on role port management capabilities

Creating a Role Port

Follow these instructions to create a role port:

To create a role port:

1. Ensure that you followed the instructions in "Accessing Role Port Management Tasks" to access the page for creating a role port.

   The Create Data Port on Role name page appears.

2. Enter a unique and recognizable role port name in the Name field. (for example, expense-OUT)

3. Enter an optional description.

4. Select Input or Output from the Direction list. For example, select Input for this role port to receive inbound event data.

5. If you want to automatically create two ports with a pass-through step in between, select the with pass-through box.

   Pass-through steps send events to the next role without any processing. These steps are useful when no processing other than sending events is required. This option automatically creates two ports in the role:

   • The first port accepts an inbound event and passes it through a pass-through step.

   • The second port receives the event on the other side of the pass-through step and passes it to the outbound port of the role.

   If you do not select this box, you must manually create the second port and the step in between at a later time.

6. Go to the Assign Port Type section to select an event (or native role interaction) for this port.

7. Select either Application Event, Business Event, or Native Event from the Classification list. For example, if you are creating a port for a native role, select Native Event Type.

8. Click the flashlight next to the Name field of the Assign Port Type section.

9. Select the event type and click Select. For example, select expense.

   Your selection appears in the Name field.

10. If you are creating a role port for a native role, you can select an interaction from the Interaction list. The Interaction list contains only complete interactions. This selection assigns the native event to the port. A port associated with an interaction sends and receives events to and from the adapter. Ports not associated with an interaction send and receive events to and from the translation binding role. In these cases, the ports are associated with a data flow group.

11. Click Apply.

    The role port is created and the Data Port Details : name page for the new role port of the role appears.

12. Select Event Flow Diagram at the bottom of the Data Port Details : name page.

13. Select Ports from the Role Contents list in the Display Options section and click Refresh to display graphical details about the role port.

14. Repeat these steps to create any necessary ports.

Deleting a Role Port

Follow these instructions to delete a role port:

To delete a role port:

Caution: Deleting a role port also deletes the data flows to another role or to a step within a role or business process.

1. Ensure that you followed the instructions in "Accessing Role Port Management Tasks" to access the page for deleting a role port.

2. Click Yes when prompted to delete a role port.

   The role port is deleted and the type Role Details : name page appears.

Updating a Role Port

Note: If you change the event type of a port, but the port has a data flow to another port of a different event type, then an error occurs. You must first update the event type of the other port or delete the data flow between the ports.

Follow these instructions to update a role port:

To update a role port:

1. Ensure that you followed the instructions in "Accessing Role Port Management Tasks" to access the page for updating a role port.

   The Update Data Port on Role name page appears.

2. Make appropriate changes. (See Step 2 through Step 10 of "Creating a Role Port" for a list of fields that you can update.)

3. Click Apply.

   The role port is updated and the Data Port Details : name page for the updated role port appears.

Viewing a Role Port

Follow these instructions to view details about a specific role port:

To view a role port:

1. Ensure that you followed the instructions in "Accessing Role Port Management Tasks" to access the page for viewing a role port.

   The Data Port Details : name page for the selected role port appears.

   

   Text description of the illustration modeling36.gif

2. View specific details, including the role ports in another role with which this role port is associated and the step ports in this role with which this role port is associated. If this is a native role port associated with an interaction, an Interaction field appears under the Details section.

   This page, as with the type Role Details : name page shown in Figure 12-17, enables you to delete or update the selected role port.

Creating a Data Flow Between a Role Port and a Step Port

Follow these instructions to create a data flow between a role port and a step port:

To create a data flow between a role port and a step port:

1. Ensure that you followed the instructions in "Accessing Role Port Management Tasks" to access the page for creating a data flow between a role port and a step port.

   The Data Port Details : name page appears. (See Figure 12-18.)

2. Go to the Data Flows Within Role section.

3. Click Create.

   The Create Data Flow page appears with a list of compatible ports. Ports that are compatible for data flow have the following characteristics:

   • There is a compatible direction. For example, if the port on the role is an input port, then the port on the step must also be an input port (the same direction).

   • They must be of the same event type, or a port that has no event type can be data flow-bound to a port with any (or no) datatype.

   • The step port must not already be data flow-bound to any other port.

   When a data flow is created between a port to which a datatype or event type is already assigned and a port to which no type is assigned, the port with no assigned type inherits the type of the assigned port (either datatype or event type).

4. Select the step with which to create a data flow in the Select column (for example, a step port called expense-OUT in a pass-through step).

5. Click Apply.

   The Data Port Details : name page appears. The data flow you created appears in the Data Flows Within Role section.

6. If this is a Data Port Details : name page for a step, select Process Diagram or Step Binding Diagram at the bottom of the page. If this is a Data Port Details : name page for a role, select Process Diagram at the bottom of the page.

7. Click inside the expense-OUT role port.

   The Step Binding diagram displays the expense-OUT output role port connected through a data flow with the expense-OUT step port of a pass-through step.

8. Repeat these steps to create any necessary data flows within this role or on other roles.

Deleting a Data Flow Between a Role Port and a Step Port

Follow these instructions to delete a data flow between a role port and a step port:

To delete a role port a data flow between a role port and a step port:

1. Ensure that you followed the instructions in "Accessing Role Port Management Tasks" to access the page for deleting a data flow.

   The Data Port Details : name page appears.

2. Go to the Data Flows Within Role section.

3. Select a data flow within a role to delete in the Delete column.

4. Click Yes when prompted to delete a data flow between a role port and a step port.

   The data flow is deleted and the Data Port Details : name page appears.

Managing Role Data Flow

The Oracle Application Server ProcessConnect user interface tool enables you to perform the role data flow management tasks shown in Figure 12-19. These tasks are described in detail in this section. Role data flows connect the role ports of roles together, which enable events to move from role to role.

Figure 12-19 Role Data Flow Management Tasks

Text description of the illustration modeling37.gif

A data flow group is a collection of role data flows between any two given roles. During runtime, data flow groups route events when a role can be connected to more than one role. Data flow criteria is used by the runtime to choose the data flow to use when the same port is the source for more than one data flow.

For example, a company's purchasing system is connected to two trading partners (for this example, TP1 and TP2). If both trading partners use the same business-to-business (B2B) protocol, purchase order processing is the same and the same set of roles is used. A third trading partner is then added that uses a different protocol. For the third trading partner, a different transformation, translation, and set of roles are required. In this case, purchase order processing is the same until transformation is performed. The business role outbound port is connected to a port of a transformation binding role (named TBR1, for example). When a third partner is added (for this example, TP3), the same outbound port of the business role must be connected to a port of a different transformation binding role (named TBR2, for example) containing the new transformation.

Data flow criteria enables you to achieve this requirement. For example, there are two data flow groups:

• DFG1 (between the business role and the first transformation binding role named TBR1)

• DFG2 (between the business role and the second transformation binding role named TBR2)

During design, you specify the conditions during which to use DFG1 and during which to use DFG2. These conditions are specified by setting a data flow criteria for the data flow group. In this scenario, DFG2 is used by the third trading partner (TP3) only.

DFG1 is used by trading partners TP1 and TP2. The data flow criteria for DFG2 is set to the third trading partner. There is no criteria required for DFG1, as this is the default.

If an additional branch is required, the same procedure is followed. When more than one data flow group is associated with a criteria, the priority is also specified. Oracle Application Server ProcessConnect then executes the criteria in the same order for every integration. Oracle Application Server ProcessConnect currently supports only simple party-based criteria.

Table 12-6 identifies the role port management tasks shown in Figure 12-19 and provides references to procedures for performing these tasks.

Table 12-6  Role Data Flow Management Tasks

Page Elements	Management Task	First See Section...	Then See Section...
Create button in Data Flow Groups section of Figure 12-19	Create a role data flow group	"Accessing Role Data Flow Management Tasks"	"Creating a Role Data Flow Group"
Delete column in Data Flow Groups section of Figure 12-19	Delete a role data flow		"Deleting a Role Data Flow"
Update column in Data Flow Groups section of Figure 12-19	Update a role data flow		"Updating a Role Data Flow"
Other Role column in Data Flow Groups section of Figure 12-19	View the other role to which the role data flow is connected		"Viewing the Other Role Connected to the Role Data Flow"
Name column in Data Flow Groups section of Figure 12-19	View details about a role data flow		"Viewing a Role Data Flow"

See Also: "Data Flow" for conceptual details about role data flow The Manage Role Data Flows section of Figure 12-1 for the graphical location of role data flows

Accessing Role Data Flow Management Tasks

Follow these instructions to access the role data flow management tasks shown in Figure 12-19:

To access role data flow management tasks:

1. Select the Modeling tab.

2. Select the appropriate tab:

   If You Select the...	This Page Appears...	Go To Step...
   Roles tab	Business Roles page	3
   Business Processes tab	Business Processes page	4

3. If you want to manage a role other than a business role, select one of the following types at the top of the page:
   • Application Roles

   • Native Roles

   • Binding Roles

4. Select the specific role or business process on which to manage role data flow in the Name column.

   The details page for the selected role or business process appears.

5. Go to the Data Flow Groups section. (See Figure 12-19.)

6. Select a task to perform and see the referenced section for instructions:

   To...	Then...	See Section...
   Create a role data flow group	Click Create.	"Creating a Role Data Flow Group"
   Delete a role data flow	Select a specific role data flow in the Delete column.	"Deleting a Role Data Flow"
   Update a role data flow	Select a specific role data flow in the Update column.	"Updating a Role Data Flow"
   View the other role to which the role data flow is connected	Select a specific role in the Other Role column.	"Viewing the Other Role Connected to the Role Data Flow"
   View details about a role data flow	Select a specific role data flow in the Name column.	"Viewing a Role Data Flow"

Creating a Role Data Flow Group

A data flow group is a collection of all the data flows between two roles. Two roles are bound both by a data flow group (as seen in the Integration Diagram) and by one or more data flows (as seen in the Event Flow Diagram).

Two roles have only a single data flow group between them. You use the Create Data Flow Group page described in this section to create a data flow group and one or more data flows. If you need to add more data flows after the data flow group is created, use the Update Data Flow Group page described in "Updating a Role Data Flow". Data flows within a role (that is, role to step and step to step data flows) are not grouped into data flow groups. These data flows belong to the role itself.

If you are creating a data flow group between a business role and a transformation binding role, you can also optionally provide a data flow criteria for this group. This feature enables the business role to be data flow-bound more than once to different transformation binding roles (in different data flow groups with different data flow criteria for each). A data flow criteria is defined by specifying a party (application or trading partner) and a priority value that determines the order of execution. For example, your organization may be conducting business with two parties. One party has slightly different transformation requirements than the other party. You can create one data flow group from the business role that branches to one transformation binding role for one party, and another data flow group that branches to another transformation binding role for the other party. You specify a priority value for the data flow group of the party that you want to execute first. For the other party, known as the default data flow group, you do not specify a priority value. The Integration Diagram shows this role branching and displays the criteria for each branch.

You can set the party before (the typical method) or during design time for data flow criteria. If you know the party at design time, use the SetParty step and explicitly route an event to an outbound spoke. If the party is not known at design time, use the transformation step in the transformation binding role of the inbound spoke to set the party into the event header, and then use the data flow criteria on the data flow group between the outbound business role and (multiple) outbound transformation binding roles to choose the correct spoke by party.

Follow these instructions to create a role data flow group and one or more data flows, and also to optionally create a data flow criteria between a business role and a transformation binding role.

To create a role data flow group:

1. Ensure that you followed the instructions in "Accessing Role Data Flow Management Tasks" to access the page for creating a role data flow group.

   The first Create Data Flow Group page appears.

   

   Text description of the illustration ex_cdf1.gif

   This page enables you to select the target role to connect with a data flow group to the source role selected in Step 4 (for this example, native role approval-NR). After complete, the data flow group connects the role port of this role (the source role) and the role port of another role (the target role).

2. Select a target role in the Select column. The list is filtered to display only those roles to which the data flow group for this role can connect. For example:

   Source Role	Possible Target Role
   Native role	Binding roles
   Binding role	Native roles, application roles, and business roles
   Application role	Binding roles
   Business role	Binding roles and business processes
   Business process	Business roles

3. If, for example, the specified direction is for inbound events, and the out port is for native role expense-NR role, select the expense-TL translation binding role for the target role.

   The second Create Data Flow Group page appears. The fields that display are based on the type of roles for which you are creating a data flow group.

4. If you are creating a data flow group between any roles except for a business role and a transformation binding role, perform Step 4a through Step 4c. Otherwise, go to Step 5.

   

   Text description of the illustration ex_cdf2.gif

   1. Enter a name for the data flow group to connect the role port of the source role expense-NR and the role port of the target role (expense-NR-TL for this example).

   2. Enter an optional description.

   3. Go to Step 6.

5. If you are creating a data flow group between a business role and a transformation binding role, perform Step 5a through Step 5e to create a data flow criteria.

   

   Text description of the illustration ex_dfc.gif

   1. Enter a name for the data flow group to connect the source role and target role.

   2. Enter an optional description.

   3. If you want to use data flow criteria, select a party from the Party list (an application or trading partner).

   4. If you want to use data flow criteria, enter a unique numeric value in the Priority field. Entering a value of 1 ensures that this data flow group is executed first. Note that you must leave the Priority field blank for at least one data flow group. For example, if you are creating three data flow groups, leave the Priority field blank for one of the data flow groups; this becomes the default data flow group.

   5. Go to Step 6.

6. Go to the Assign Ports section. For each port in the source role, a list of target role ports that are compatible for data flow is provided. Compatible for data flow means that the ports have the following characteristics:
   • There is a compatible direction. For example, if the port on one role is an input port, then the port on the other role must be an output port, and vice versa.

   • They must be of the same event type, or a port that has no event type can be data flow-bound to a port with any (or no) datatype.

   • The port must not already be data flow-bound to another role port. The only exception is a data flow group between a business role and a transformation binding role, which allows the same port in the business role to be data flow-bound more than once to ports in different binding roles (in different data flow groups that have different data flow criteria for each).

   When a data flow is created between a port to which a datatype or event type is already assigned and a port to which no type is assigned, the port with no assigned type inherits the type of the assigned port (either datatype or event type).

7. Select a role port for the target role from the Available Ports on Role target_role list. This is the target role you selected in Step 2.

   Selection	Description
   No compatible unbound ports	Displays when the selected target role has no ports that match the rules described in Step 6.
   Create new role port	Creates a new port on the target role and creates the data flow to it. The created port is compatible in that it has the same event type as the source port and is of the opposite direction.
   Create new role ports with pass-through step	The same as Create new role port, plus it creates the pass-through step, the step ports, the role port on the other side, and the data flow groups between the step and role ports.

8. Click Create Data Flow Group.

   This creates a data flow group between the role port of the source role and the role port of the target role. The Data Flow Group Details : name page for the created data flow appears.

   See Also: "Creating an Event Header Rule"

Deleting a Role Data Flow

Follow these instructions to delete a role data flow:

To delete a role data flow:

Caution: Deleting a role data flow can leave role ports disconnected.

1. Ensure that you followed the instructions in "Accessing Role Data Flow Management Tasks" to access the page for deleting a role data flow.

2. Click Yes when prompted to delete a role data flow.

   The role data flow is deleted and the type Role Details : name page appears.

Updating a Role Data Flow

You can update role data flow from this page by adding new data flows or deleting data flows by deselecting them. Follow these instructions to update a role data flow:

To update a role data flow:

1. Ensure that you followed the instructions in "Accessing Role Data Flow Management Tasks" to access the page for updating a role data flow.

   The Update Data Flow Group page appears.

2. Make appropriate changes. (See Step 2 through Step 7 of "Creating a Role Data Flow Group" for a list of fields that you can update.)

3. Click Update Data Flow Group.

   The role data flow is updated and the Data Flow Group Details : name page for the updated role data flow appears.

Viewing the Other Role Connected to the Role Data Flow

Follow these instructions to view details about the other role (the target role) connected to the role data flow:

To view the other role connected to the role data flow:

1. Ensure that you followed the instructions in "Accessing Role Data Flow Management Tasks" to access the page for viewing the target role connected with role data flow to the source role.

   The type Role Details : name page appears (for example, if the other role was a binding role):

   

   Text description of the illustration modeling41.gif

2. View specific details, including the other role connected to the current role by the role data flow group, by clicking a role in the Other Role column.

Viewing a Role Data Flow

Follow these instructions to view details about a specific role data flow:

To view a role data flow:

1. Ensure that you followed the instructions in "Accessing Role Data Flow Management Tasks" to access the page for viewing a role data flow.

   The Data Flow Group Details : name page for the selected role data flow appears.

   

   Text description of the illustration modeling42.gif

2. View specific details, including the roles with which this role data flow is associated. This page enables you to perform the following tasks from this page:
   1. Delete a data flow group by clicking Delete at the top of the page. Deleting the data flow group also deletes all the data flows belonging to it.

   2. Update a data flow by clicking Update. The Update Data Flow group page enables you to add new data flows or delete data flows by deselecting them.

   3. Delete an individual data flow by clicking Delete in the Delete column.

Managing Steps

The Oracle Application Server ProcessConnect user interface tool enables you to perform the step management tasks shown in Figure 12-20. These tasks are described in detail in this section.

Figure 12-20 Step Management Tasks

Text description of the illustration modeling43.gif

Each role and business process consists of a set of steps. A step defines execution logic that is applied to one or more events or control flows and data flows in a role. There are two types of steps:

• Steps that process events: pass-through, translation, transformation, condition, consume, split, and SetParty

• Steps that manage control flows: Start, End, Or, and And

Some of these steps have ports that represent the input and output parameters. Steps with ports can have data flows associated with these ports. In addition, steps can have incoming and outgoing control flows.

See Also: "Data Flow" and "Control Flow"

Types of Steps

This section provides details about each step type that you can create and design:

• Start Step

• End Step

• Pass-through Step

• Transformation Step

• Translation Step

• Condition Step

• SetParty Step

• Consume Step

• Split Step

• Or Step

• And Step

Start Step

This step is a pseudo-step that indicates the start of a role. It is automatically created when a new role is created.

Supported Ports

This step has no IN ports and no OUT ports.

Supported Control Flows and Data Flows

There can be any number of outgoing control flows from this step. This step can have no incoming control flows or data flows.

Supported Roles

This step must exist in every role in the integration.

Execution

This step is executed after the role has an event on its initiating IN port.

End Step

This step indicates completion of role processing. This step is automatically created when a new role is created.

Supported Ports

This step has no IN ports and no OUT ports.

Supported Control Flows and Data Flows

There can be any number of incoming control flows coming into this step. This step cannot have any outgoing control flows or data flows.

Supported Roles

This step must exist in every role in the integration.

Execution

This step is executed after all incoming control flows have been executed. After execution of this step, the role processing is complete and the role instance is marked as WorkflowComplete. If all events on the outbound ports of the role have been picked up as well, then the role instance is Complete.

Pass-through Step

This step passes through the event or datatype on its IN port to its OUT port. The event contents are not altered.

See Also: "Error Handling with Step Return Code Ports" for an example of a role that uses a pass-through step

Supported Ports

This step has exactly one IN port and one OUT port. These ports can be associated with an event type or a datatype. Both the IN port and the OUT port must be associated with the same event type or datatype.

Supported Control Flows and Data Flows

This step can have one incoming data flow and one outgoing data flow. There can be any number of incoming control flows and outgoing control flows.

Supported Roles

This step is typically used in the native role, application role, or business role if there is no party-specific event processing required. This step can be used in other roles, if required.

Execution

This step is executed after all incoming control flows and data flows have executed. The event or datatype moves to the OUT port if the step successfully executes.

Transformation Step

This step transforms a set of events or datatypes into another set of events or datatypes. This step is associated with a transformation map. The transformation map parameters must correspond to the types on the IN ports and OUT ports. The events or datatypes to be transformed are on the IN ports. The new events or datatypes created after transformation are put on the OUT ports.

See Also: "Error Handling with Step Return Code Ports" for an example of a role that uses a transformation step

Supported Ports

This step can have multiple IN ports and multiple OUT ports. These ports can be associated with an event type or a datatype (based on the return values from the transformation map). This step also has a return code port that is associated with the returnCode datatype.

Supported Control Flows and Data Flows

This step can have any number of incoming control flows and outgoing control flows. Each IN port must have an incoming data flow. Each OUT port must have an outgoing data flow. Data flow from the return code port is optional.

Supported Roles

This step can only operate on application datatypes or event types, or business datatypes or event types. This step is ideally used only in the transformation binding role, but it can be used in all roles except the native role.

Execution

This step is executed after all incoming control flows and data flows have executed. The transformation map is invoked when there is data on all the IN ports. After the transformation step has executed, the return code port is populated with a datatype that indicates success or failure. If transformation is successful, the OUT ports and return code port are populated. If there is a failure, the OUT ports are not filled; only the return code port is populated with a datatype containing the error code and error message. The events or datatypes on the IN port are marked as consumed.

Translation Step

This step translates a native event type or datatype to an application event type or datatype, and vice versa. The IN port must be associated with the event or datatype to be translated. The OUT port must be associated with the translated event or datatype. The translation step converts the syntax from the native format to the interpretable application format, or vice versa.

The new event or datatype created after translation is put on the OUT ports.

See Also: "Application Events and Translation" for additional details about translation

Supported Ports

This step has one IN port and two OUT ports. There is one OUT port for the translated event or datatype and one for the return code port (which is associated with the returnCode datatype).

The IN and OUT ports can be associated with native or application event types or datatypes. If the IN port is associated with a native event type, the OUT port must be associated with the application event, and vice versa. You cannot have a datatype associated with the IN port and an event type associated with the OUT port. Both ports must be associated with either datatypes or event types.

Supported Control Flows and Data Flows

This step can have one incoming data flow and one outgoing data flow. There can be any number of incoming control flows and outgoing control flows. Data flow from the return code port is optional.

Supported Roles

This step is typically used in the translation binding role.

Execution

This step is executed after all incoming control flows and data flows have executed. The translation is done when there is a data or event instance on the IN port. After the translation step has executed, the return code port is populated with a datatype that indicates success or failure. If translation is successful, both the OUT port and return code port are populated. If there is a failure, the OUT port is not filled, only the return code port is populated with a datatype containing the error code and error message. The event on the IN port is consumed.

Condition Step

This step evaluates a specific condition on an event type or datatype. This step is associated with a condition expression. The datatype for the IN port is automatically selected based on the datatype or event type used by the condition expression. After the condition expression is evaluated, one of the outgoing control flows (either true or false) is executed.

See Also: "Designing Roles to Ensure Proper Validation" for examples of roles that use condition steps "Error Handling with Step Return Code Ports" for an example of a role that uses a condition step

Supported Ports

This step has one IN port and one OUT port (other than the return code port). This OUT port is a return code port associated with the returnCode datatype. The IN port can be associated with an application or business event or datatype. This is automatically selected based on the condition expression used for the step.

Supported Control Flows and Data Flows

This step must have one incoming data flow. There can be any number of incoming control flows and exactly two outgoing control flows: one for true guard value and one for false guard value. Data flow from the return code port is optional.

Supported Roles

This step can only operate on application datatypes or event types, or business datatypes or event types. This step is ideally used only in the transformation binding role, but can be used in all roles except the native role.

Execution

This step is executed after all incoming control flows and data flows have executed. The condition expression is evaluated when there is a data or event instance on the IN port. After the condition step has executed, the return code port is populated with a datatype that indicates success or failure. If expression evaluation is complete, based on the result (true or false), one of the outgoing control flows is executed. If there is a failure when evaluating the condition expression, the outgoing control flow is not executed and the return code port is populated with a datatype containing the error code and error message.

SetParty Step

This step sets a specific destination party (application or trading partner) for an event type or datatype.

See Also: "Selecting the Destination Party in the SetParty Step" for an example of a role that uses a SetParty step

Supported Ports

This step has exactly one IN port and one OUT port. These ports can be associated with an event type or a datatype. Both the IN port and the OUT port are associated with the same event type or datatype.

Supported Control Flows and Data Flows

This step can have one incoming data flow and one outgoing data flow. There can be any number of incoming control flows and outgoing control flows.

Supported Roles

This step is typically used in the business role or business process.

Execution

This step is executed after all incoming control flows and when there is data on the IN port. The event type or datatype header is updated with the destination party and then moved to the OUT port.

Consume Step

This step consumes and prevents further processing of an event or datatype. The IN port must be associated with the event or datatype to be consumed. This step is typically used to consume acknowledgments.

See Also: "Acknowledgment Consumption and Generation" for an example of a role that uses a consume step

Supported Ports

This step has one IN port and no OUT ports.

Supported Control Flows and Data Flows

This step must have one incoming data flow. There are no outgoing data flows from this step. There can be any number of incoming control flows and outgoing control flows.

Supported Roles

This step can operate on any type of event or datatype, and can be used in any role.

Execution

This step is executed after all incoming control flows have executed and when there is data on the IN port. The incoming event is marked as consumed and further processing is disabled.

Split Step

This step makes multiple copies of an event. The event on the IN port is copied and the new events are placed on each of the OUT ports.

See Also: "Error Handling with Step Return Code Ports" for an example of a role that uses a split step

Supported Ports

This step has one IN port and multiple OUT ports. The IN port can be associated with an event or datatype.

Supported Control Flows and Data Flows

Each IN port must have an incoming data flow. Each OUT port must have an outgoing data flow. There can be any number of incoming control flows and outgoing control flows.

Supported Roles

This step can operate on any type of event or datatype, and can be used in any role.

Execution

This step is executed after all incoming control flows have executed and when there is data on the IN port. The incoming event is marked as consumed and copies of the event are placed on the OUT ports.

Or Step

This step waits for at least one incoming control flow. The step is executed as soon as one of the incoming control flows is executed.

Supported Ports

This step has no IN ports or OUT ports.

Supported Control Flows and Data Flows

This step can have any number of incoming control flows and outgoing control flows. This step does not have any data flows.

Supported Roles

This step can be used in any role.

Execution

This step is executed after any incoming control flow has executed. In all other steps, the steps are executed only when all the incoming control flows have executed. This is the only case where the step is executed after any one of the incoming control flows. Ensure that the incoming control flows are coming from mutually exclusive paths. Otherwise, the role processing is not deterministic.

See Also: "Designing Roles to Ensure Proper Validation" for examples of roles that use Or steps.

And Step

This step waits for all incoming control flows, and executes after all incoming control flows have executed. This step is not typically required since all steps (except an Or step), implicitly provide AND step behavior for the incoming control flows.

Supported Ports

This step has no IN ports or OUT ports.

Supported Control Flows and Data Flows

This step can have any number of incoming control flows and outgoing control flows. This step does not have any data flows.

Supported Roles

This step can be used in any role.

Execution

This step is executed after all of the incoming control flows have executed. Ensure that the incoming control flows are not coming from mutually exclusive paths. Otherwise, this step may never execute and role processing may halt here.

Table 12-7 identifies the step management tasks shown in Figure 12-20 and provides references to procedures for performing these tasks.

Table 12-7  Step Management Tasks

Page Elements	Management Task	First See Section...	Then See Section...
Create button in Steps section of Figure 12-20	Create a step	"Accessing Step Management Tasks"	"Creating a Step"
Delete column in Steps section of Figure 12-20	Delete a step		"Deleting a Step"
Update column in Steps section of Figure 12-20	Update a step		"Updating a Step"
Name column in Steps section of Figure 12-20	View details about a step		"Viewing a Step"

See Also: "Steps" for conceptual details about steps The Manage Steps section of Figure 12-1 for the graphical location of steps

Accessing Step Management Tasks

Follow these instructions to access the step management tasks shown in Figure 12-20:

To access step management tasks:

1. Select the Modeling tab.

2. Select the appropriate tab:

   If You Select the...	This Page Appears...	Go To Step...
   Roles tab	Business Roles page	3
   Business Processes tab	Business Processes page	4

3. If you want to manage a role other than a business role, select one of the following types at the top of the page:
   • Application Roles

   • Native Roles

   • Binding Roles

4. Select the specific role or business process on which to manage a step in the Name column.

   The details page for the selected role or business process appears.

5. Go to the Steps section. (See Figure 12-20.)

6. Select a task to perform and see the referenced section for instructions:

   To...	Then...	See Section...
   Create a step	Click Create.	"Creating a Step"
   Delete a step	Select a step in the Delete column.	"Deleting a Step"
   Update a step	Select a specific step in the Update column.	"Updating a Step"
   View details about a step	Select a specific step in the Name column.	"Viewing a Step"

   You can also manage steps from within a Process Diagram or Step Binding Diagram.

   See Also: "Viewing a Process Diagram" and "Viewing a Step Binding Diagram" for details on step management

Creating a Step

Follow these instructions to create a step:

Note: Each business process or role automatically includes a Start and End step to indicate the beginning and end of a step. You cannot manually create these two steps. These steps have no in and out ports.

To create a step:

1. Ensure that you followed the instructions in "Accessing Step Management Tasks" to access the page for creating a step.

   The Create Step in Role name page appears.

2. Enter a unique and recognizable name for the step in the Name field (for example, Passthrough_expense).

3. Enter an optional description in the Description field.

4. Review the following step types. The step types available for creation are based on the type of role or business process in which you are creating the step.

   Step	Native Role	Translation Binding Role	Application Role	Transformation Binding Role	Business Role	Business Process
   And	Yes	Yes	Yes	Yes	Yes	Yes
   Condition	No	Yes	Yes	Yes	Yes	Yes
   Consume	Yes	Yes	Yes	Yes	Yes	Yes
   Or	Yes	Yes	Yes	Yes	Yes	Yes
   Pass-through	Yes	Yes	Yes	Yes	Yes	Yes
   SetParty	No	No	No	No	Yes	Yes
   Split	Yes	Yes	Yes	Yes	Yes	Yes
   Transformation	No	Yes	Yes	Yes	Yes	Yes
   Translation	No	Yes	Yes	Yes	No	No

5. Select a step from the Type list based on the types described in "Types of Steps" (for this example, Pass-through is selected).

   The page refreshes based on the step type selected in Step 5.

   For most steps that have both an input and output port, the ports must have the same event type or datatype. For example, a SetParty step or pass-through step have input and output ports of the same event or datatype. The only exceptions to this are the transformation and translation steps, which can convert the event or datatype between the in and out ports.

6. If you selected one of the following steps, additional lists appear and prompt you for a selection.

7. Make a selection from the list for your step type. Otherwise, go to Step 8.

   If You Select...	Then...
   Condition step	Select the condition expression to use from the Condition Expression list. A port is created for each parameter in the condition expression. This is the condition expression you created in "Managing Condition Expressions in Steps".
   SetParty Step	Select the destination party (trading partner or application) to use from the Party list. See Also: "Creating an Application" and "Creating a Remote Trading Partner" (The host trading partner automatically displays for selection in the Party list.)
   Transformation Step	Select the datatype transformation map (for example, copy:from=string->to=string) to use from the Transformation Map list. A port is created for each parameter in the transformation map. See Also: "Managing Transformation Statements"

8. Go to the Control Flows section. Control flows between steps define the execution order of steps. The number of after and before sections of the Sequence lists that display are based on the step type you selected.

9. Select the step sequence to use. For example, if you are creating a pass-through step, select the Start step from the after section of the Sequence list and the End step from the before section of the Sequence list. This places the pass-through step after the Start step and before the End step in the role.

   Field	Description
   Sequence after Step	Select a step. The step you select is executed before the step you selected in Step 5.
   Sequence before Step	Select a step. The step you select is executed after the step you selected in Step 5.
   Guard Value Note: This field only displays for a condition step.	A guard value is only required for a condition step for the before section of the Sequence list. This means that the value only has meaning on a control flow that is going out of a condition step. True If the condition expression evaluates to true, use this control flow. False If the condition expression evaluates to false, use this control flow. After control flow creation, the guard value displays in the Guard Value column of the Control Flows section, as shown in Figure 12-23.

10. Click Apply.

    The step is created and the Step Details : name page appears. Step type-specific metadata also appears in the Details section of the Step Details : name page. (See the page in "Viewing a Step" for an example.) Some step types include links to other pages. For example, the transformation step includes a link to the Transformation Map Details page for the transformation map selected in Step 7.

    Based on the type of step created, various input ports (named Input1), output ports (named Output1 and Output2), or return code ports are also automatically created. These ports have no event type or datatype assigned to them. The ports must have an assigned type before they can be included in a deployed configuration. A port with no assigned type often inherits the type of a port to which it is data flow-bound (either datatype or event type) or the type of another port in the same step.

    The following table lists the ports automatically created.

    For This Step...	Input1 Port Created?	Output1 Port Created?	Output2 Port Created?	Return Code Port Created?
    AndFoot 1	No	No	No	No
    Condition	Yes	No	No	Yes
    Consume	Yes	No	No	No
    Or1	No	No	No	No
    Pass-through	Yes	Yes	No	No
    SetParty	Yes	Yes	No	No
    Split	Yes	Yes	Yes	No
    Translation	Yes	Yes	No	Yes
    Transformation	Yes	Yes	No	Yes

    1 No ports are created; only control flows, which do not use ports, are used with this step type.

11. Select Step Binding Diagram, Event Flow Diagram, and Process Diagram at the bottom of the Step Details : name page to view graphical details about the step, including role ports, step ports, steps, and events.

12. Repeat these steps to create any necessary steps for this role or other roles.

    See Also: "Creating a Step Port" to create additional step ports

Deleting a Step

Follow these instructions to delete a step:

Caution: Deleting a step also deletes its control flows, ports, and data flows, and can leave other steps unconnected.

To delete a step:

1. Ensure that you followed the instructions in "Accessing Step Management Tasks" to access the page for deleting a step.

2. Click Yes when prompted to delete a step.

   The step is deleted and the type Role Details : name page appears.

Updating a Step

You can update step-specific details. For example, for a SetParty step, you can change the party with which the step is associated by selecting a different party from the list. For a transformation step, if you chose a different transformation map, a new set of ports are created that correspond to the new map parameters. The data flows of the old ports are reconnected to the new ports if the event type or datatype of the ports match. The old ports are then deleted. The same situation also applies for condition steps and conditional expressions.

Follow these instructions to update a step:

To update a step:

1. Ensure that you followed the instructions in "Accessing Step Management Tasks" to access the page for updating a step.

   The Update Step in Role name page appears.

2. Make appropriate changes. (See Step 2 through Step 5 of "Creating a Step" for a list of fields that you can update.)

3. Click Apply.

   The step is updated and the Step Details : name page appears.

Viewing a Step

Follow these instructions to view details about a specific step:

To view a step:

1. Ensure that you followed the instructions in "Accessing Step Management Tasks" to access the page for viewing a step.

   The Step Details : name page appears.

   

   Text description of the illustration modeling47.gif

This page enables you to view details about a step. The Data Ports section of this page lists the data ports for the role. This page, as with the type Role Details : name page shown in Figure 12-20, enables you to delete or update the selected step.

Note: If this is a transformation step, the Details section at the top of the Step Details : name page includes a link to the transformation map you created. Click the transformation map to access its details page. If this is a SetParty step, the destination party also displays in the Details section at the top of the Step Details : name page

Managing Step Ports

The Oracle Application Server ProcessConnect user interface tool enables you to perform the step port management tasks shown in Figure 12-21. These tasks are described in detail in this section. Step ports are the input and output parameters of steps in roles. Step ports work with data flows and control flows to connect steps in roles together. Step ports also work with data flows to connect incoming role ports to incoming step ports and outgoing step ports to outgoing role ports.

Figure 12-21 Step Port Management Tasks

Text description of the illustration modeling48.gif

Table 12-8 identifies the step port management tasks shown in Figure 12-21 and provides references to procedures for performing these tasks.

Table 12-8 Step Port Management Tasks

Step Details Page Elements	Management Task	First See Section...	Then See Section...
Create button in Data Ports section of Figure 12-21	Create a step port	"Accessing Step Port Management Tasks"	"Creating a Step Port"
Delete column in Data Ports section of Figure 12-21	Delete a step port		"Deleting a Step Port"
Update column in Data Ports section of Figure 12-21	Update a step port		"Updating a Step Port"
Name column in Data Ports section of Figure 12-21 (To access the details page in the lower page of Figure 12-21)	View details about a step port		"Viewing a Step Port"

See Also: "Step Ports" for conceptual details about step ports The Manage Step Ports section of Figure 12-2 for the graphical location of step ports

Accessing Step Port Management Tasks

Follow these instructions to access the step port management tasks shown in Figure 12-21:

To access step port management tasks:

1. Select the Modeling tab.

2. Select the appropriate tab:

   If You Select the...	This Page Appears...	Go To Step...
   Roles tab	Business Roles page	3
   Business Processes tab	Business Processes page	4

3. If you want to manage a role other than a business role, select one of the following types at the top of the page:
   • Application Roles

   • Native Roles

   • Binding Roles

4. Select the specific role or business process on which to manage role data flow in the Name column.

   The details page for the selected role or business process appears.

5. Go to the Steps section. (See Figure 12-20.)

6. Select the specific step in the Name column.

   The Step Details : name page appears.

7. Go to the Data Ports section. (See the upper page of Figure 12-21.)

8. Select a task to perform and see the referenced section for instructions:

   To...	Then...	See Section...
   Create a step port	Click Create.	"Creating a Step Port"
   Delete a step port	Select a specific step port in the Delete column.	"Deleting a Step Port"
   Update a step port	Select a specific step port in the Update column.	"Updating a Step Port"
   View details about a step port	Select a specific step port in the Name column.	"Viewing a Step Port"

   You can also manage some aspects of step ports from within a Process Diagram or Step Binding Diagram.

   See Also: "Viewing a Process Diagram" and "Viewing a Step Binding Diagram" for details on step port management capabilities

Creating a Step Port

Several default step ports are automatically created when you create a step. You can also create additional step ports, as needed. Follow these instructions to create a step port:

Note: If you are creating a step port on a consume or a condition step, the port can only be an input port. You cannot create step ports on an And step or an Or step. These steps only use control flows, which do not require step ports.

To create a step port:

1. Ensure that you followed the instructions in "Accessing Step Port Management Tasks" to access the page for creating a step port.

   The Create Data Port on Step Details : name page appears.

2. Enter a unique and recognizable role port name in the Name field (for example, expense-OUT).

3. Enter an optional description.

4. If you are creating a step port on a transformation step that has a transformation map assigned to it, follow Step 4a through Step 4c. Otherwise, go to Step 5.
   1. Go to the Assign Port Type section.

   2. Select a map parameter from the list. If you select a parameter, the direction and the datatype of the port are determined by the parameter selected.

   3. Go to Step 11.

5. If you are creating a step port on a condition step that has a condition expression assigned to it, follow Step 5a through Step 5c. Otherwise, go to Step 6. Since a condition step only permits a single input port, the direction is automatically selected and cannot be changed.
   1. Go to the Assign Port Type section.

   2. Select a condition parameter from the list. The datatype of the port is determined by the parameter selected.

   3. Go to Step 11.

6. If you are creating a step port on any other step type, select Input or Output from the Direction list. For example, select Input for this step port to receive inbound event data. Since a consume step only permits a single input port, the direction is automatically selected and cannot be changed.

7. Go to the Assign Port Type section.

8. Select Datatype or Event Type from the Type list.

   The page refreshes to display additional fields.

9. If you selected Datatype, perform Step 9a through Step 9e. Otherwise, go to Step 10.
   1. Select either Application Datatype, Business Datatype, or Native Datatype from the Classification Class list. For example, if you are creating a step port for a native role, select Native Datatype.

   2. Select a namespace for the datatype from the Namespace list.

   3. Click the flashlight next to the Name field of the Assign Port Type section.

   4. Select the datatype and click Select.

      Your selection appears in the Name field.

   5. Go to Step 11.

10. If you selected Event Type, perform Step 10a through Step 10c.
    1. Select either Application Event, Business Event, or Native Event from the Classification Class list. For example, if you are creating a step port for a native role, select Native Event.

    2. Click the flashlight next to the Name field of the Assign Port Type section.

    3. Select the event type and click Select.

       Your selection appears in the Name field.

11. Click Apply.

    The step port is created, and you are returned to the Step Details : name page.

12. Select Step Binding Diagram at the bottom of the Step Details : name page to view graphical details about the step port.

13. Repeat these steps to create any necessary step ports for this step or other steps.

Deleting a Step Port

Follow these instructions to delete a step port:

Caution: Deleting a step port also deletes data flow for this port, and can leave other ports unconnected.

To delete a step port:

1. Ensure that you followed the instructions in "Accessing Step Port Management Tasks" to access the page for deleting a step port.

2. Click Yes when prompted to delete a step port.

   You are returned to the Step Details : name page.

Updating a Step Port

Follow these instructions to update a step port:

To update a step port:

1. Ensure that you followed the instructions in "Accessing Step Port Management Tasks" to access the page for updating a step port.

   The Update Data Port on Step name page appears.

2. Make appropriate changes. (See Step 2 through Step 10c of "Creating a Step Port" for a list of fields that you can update.)

3. Click Apply.

   The step port is updated and the Data Port Details : name page appears.

Viewing a Step Port

Follow these instructions to view details about a specific step port:

To view a step port:

1. Ensure that you followed the instructions in "Accessing Step Port Management Tasks" to access the page for viewing a step port.

   The Data Port Details : name page appears.

   

   Text description of the illustration modeling5.gif

This page enables you to view details about a step port. This page, as with the Step Details : name page shown in the upper page of Figure 12-21, enables you to delete or update the selected step port.

Managing Step Data Flow

The Oracle Application Server ProcessConnect user interface tool enables you to perform the step data flow management tasks shown in Figure 12-22. These tasks are described in detail in this section. Step data flows connect the ports of steps together, which enable events to move through steps.

Figure 12-22 Step Data Flow Management Tasks

Text description of the illustration modeling6.gif

Table 12-9 identifies the step data flow management tasks shown in Figure 12-22 and provides references to procedures for performing these tasks.

Table 12-9  Step Data Flow Management Tasks

Page Elements	Management Task	First See Section...	Then See Section...
Create button in upper page of Figure 12-22	Create a step data flow	"Accessing Step Data Flow Management Tasks"	"Creating a Step Data Flow"
Delete column in upper page of Figure 12-22	Delete a step data flow		"Deleting a Step Data Flow"
Port column in upper page of Figure 12-22 (To access the details page in the lower page of Figure 12-22)	View the target port for the step data flow		"Viewing the Target Port of a Step Data Flow"

See Also: "Data Flow" for conceptual details about step data flow "Viewing a Business Process" or "Viewing a Role" (this page is accessible from the Owner column of the Data Flows section in the upper page of Figure 12-22) The Manage Step Data Flow section of Figure 12-2 for the graphical location of step data flows "Managing Role Ports" for details about the tasks available from the Data Flows Within Role section shown in the lower page of Figure 12-17

Accessing Step Data Flow Management Tasks

Follow these instructions to access the step data flow management tasks shown in Figure 12-22:

To access step data flow management tasks:

1. Select the Modeling tab.

2. Select the appropriate tab:

   If You Select the...	This Page Appears...	Go To Step...
   Roles tab	Business Roles page	3
   Business Processes tab	Business Processes page	4

3. If you want to manage a role other than a business role, select one of the following types at the top of the page:
   • Application Roles

   • Native Roles

   • Binding Roles

4. Select the specific role or business process on which to manage role data flow in the Name column.

   The details page for the selected role or business process appears.

5. Go to the Steps section. (See Figure 12-20.)

6. Select a specific step in the Name column.

   The Step Details : name page for the selected step appears. (See the upper page of Figure 12-21.)

7. Go to the Data Ports section.

8. Select a specific step port in the Name column.

   The Data Port Details : name page for the selected data port appears. (See the upper page of Figure 12-22.)

9. Select a task to perform and see the referenced section for instructions:

   To...	Then...	See Section...
   Create a step data flow	Click Create.	"Creating a Step Data Flow"
   Delete a step data flow	Select a specific step data flow in the Delete column.	"Deleting a Step Data Flow"
   View the target port for the step data flow	Select a step port in the Port column.	"Viewing the Target Port of a Step Data Flow"

   You can also manage some aspects of step data flows from within a Process Diagram or Step Binding Diagram.

   See Also: "Viewing a Process Diagram" and "Viewing a Step Binding Diagram" for details on step data flow management capabilities

Creating a Step Data Flow

You can create step data flows for all steps with the exception of an And step and an Or step. Follow these instructions to create a step data flow:

To create a step data flow:

1. Ensure that you followed the instructions in "Accessing Step Data Flow Management Tasks" to access the page for creating a step data flow.

   The Create Data Flow page appears.

   A step port can be data flow-bound to either a role port or another step port. For a role port, the direction of the ports is the same. For example, an input step port is bound to an input role port, whereas an input step port is bound to an output step port.

2. Click Select for the step port with which to create a step data flow for this step port. For example, you may want to create a step data flow to a split step in this role. The list of ports contains only compatible ports. Compatible for data flow means that the ports have the following:
   • There is a compatible direction. For example, if the port on one step is an input port, then the port on the other step must be an output port, and vice versa.

   • They must be of the same event type, or a port that has no event type can be data flow-bound to a port with any (or no) datatype.

   When a data flow is created between a port to which a datatype or event type is already assigned and a port to which no type is assigned, the port with no assigned type inherits the type of the assigned port (either datatype or event type).

3. Click Apply.

   The step data flow is created and the Data Port Details : name page appears.

4. Select the Process Diagram, Event Flow Diagram, or Step Binding Diagram at the bottom of the Step Details : name page to view graphical details about the step data flow.

5. Repeat these steps to create any necessary step data flow for this step or other steps.

Deleting a Step Data Flow

Follow these instructions to delete a step data flow:

Caution: Deleting a step data flow can leave ports unconnected.

To delete a step data flow:

1. Ensure that you followed the instructions in "Accessing Step Data Flow Management Tasks" to access the page for deleting a step data flow.

2. Click Yes when prompted to delete a step data flow.

   You are returned to the Data Port Details : name page.

Viewing the Target Port of a Step Data Flow

Follow these instructions to view details about the target port of a step data flow:

To view the target port of a step data flow:

1. Ensure that you followed the instructions in "Accessing Step Data Flow Management Tasks" to access the page for viewing the target port of a step data flow.

   The Data Port Details : name page appears.

   

   Text description of the illustration ex_step_port2.gif

This page enables you to view details about the target port of a step data flow. In this example, the target port is part of a step.

Managing Step Control Flow

The Oracle Application Server ProcessConnect user interface tool enables you to perform the step control flow management tasks shown in Figure 12-23. These tasks are described in detail in this section. Control flows between steps indicate the execution order of steps. You can also create step control flows when you create a step.

Figure 12-23 Step Control Flow Management Tasks

Text description of the illustration modeling9.gif

Table 12-10 identifies the step control flow management tasks shown in Figure 12-23 and provides references to procedures for performing these tasks.

Table 12-10  Step Control Flow Management Tasks

Step Details Page Elements	Management Task	First See Section...	Then See Section...
Create button in Control Flows section of Figure 12-23	Create a step control flow	"Accessing Step Control Flow Management Tasks"	"Creating a Step Control Flow"
Delete column in Control Flows section of Figure 12-23	Delete a step control flow		"Deleting a Step Control Flow"
Update column in Control Flows section of Figure 12-23	Update a step control flow		"Updating a Step Control Flow"

See Also: "Creating a Step Control Flow" for details about the Guard Value column of the Control Flows section in Figure 12-23 "Control Flow" for conceptual details about step control flows The Manage Control Data Flows section of Figure 12-2 for the graphical location of step control flows

Accessing Step Control Flow Management Tasks

Follow these instructions to access the step control flow management tasks shown in Figure 12-23:

To access step control flow management tasks:

1. Select the appropriate tab:

   If You Select the...	This Page Appears...	Go To Step...
   Roles tab	Business Roles page	3
   Business Processes tab	Business Processes page	4

2. If you want to manage a role other than a business role, select one of the following types at the top of the page:
   • Application Roles

   • Native Roles

   • Binding Roles

3. Select the specific role or business process on which to manage role data flow in the Name column.

   The details page for the selected role or business process appears.

4. Go to the Steps section. (See Figure 12-20.)

5. Select a specific step in the Name column.

   The Step Details : name page for the selected step appears. (See Figure 12-23.)

6. Go to the Control Flows section.

7. Select a task to perform and see the referenced section for instructions:

   To...	Then...	See Section...
   Create a step control flow	Click Create	"Creating a Step Control Flow"
   Delete a step control flow	Select a specific step control flow in the Delete column.	"Deleting a Step Control Flow"
   Update a step control flow	Select a specific step control flow in the Update column.	"Updating a Step Control Flow"

   You can also manage control flow from within a Process Diagram.

   See Also: "Viewing a Process Diagram"

Creating a Step Control Flow

Follow these instructions to create a step control flow:

To create a step control flow:

1. Ensure that you followed the instructions in "Accessing Step Control Flow Management Tasks" to access the page for creating a step control flow.

   The Create Control Flow for Step name page appears.

2. Select the step sequence to use.

   Field	Description
   Sequence *	Select the order in which to perform this step (either after or before).
   Step *	Select the step to perform in sequence with the step you are creating.
   Guard Value Note: This field only displays if you are creating a step control flow for a condition step.	A guard value is only required for a condition step if before is selected from the Sequence list. This means that the value only has meaning on a control flow that is going out of a condition step. True If the condition expression evaluates to true, use this control flow. False If the condition expression evaluates to false, use this control flow. After control flow creation, the guard value displays in the Guard Value column of the Control Flows section in Figure 12-23.

3. Click Apply.

   The step control flow is created and the Step Details : name page appears.

4. Click Process Diagram at the bottom of the Step Details : name page to view the step control flow. The guard value displays on the Process Diagram as T (for true), F (for false), or E (for error) when the language is English.

5. Repeat these steps to create any necessary control flows for this step or other steps.

   Note: Control flows do not have ports. Only data flows require ports.

Deleting a Step Control Flow

Follow these instructions to delete a step control flow:

Caution: Deleting a control flow can leave other steps unconnected.

To delete a step control flow:

1. Ensure that you followed the instructions in "Accessing Step Control Flow Management Tasks" to access the page for deleting a step control flow.

2. Click Yes when prompted to delete a step control flow.

   The step control flow is deleted and the Step Details : name page appears.

Updating a Step Control Flow

Follow these instructions to update a step control flow:

To update a step control flow:

1. Ensure that you followed the instructions in "Accessing Step Control Flow Management Tasks" to access the page for updating a step control flow.

   The Update Control Flow on Step name page appears.

2. Make appropriate changes. (See Step 2 of "Creating a Step Control Flow" for a list of fields that you can update.)

3. Click Apply.

   The step control flow is updated and the Step Details : name page appears.

Managing Condition Expressions in Steps

The Oracle Application Server ProcessConnect user interface tool enables you to perform the condition expression management tasks shown in Figure 12-24. These tasks are described in detail in this section. Condition expressions enable you to define that a specific action be performed in a condition step based on the result of an expression. For example, you can specify that a specific condition be performed if the price field of a purchase order is over a specific number, such as notifying a second approver before the purchase order can be approved.

Figure 12-24 Condition Expression Management Tasks

Text description of the illustration modeling11.gif

Table 12-11 identifies the condition expression management tasks shown in Figure 12-24 and provides references to procedures for performing these tasks.

Table 12-11  Condition Expression Management Tasks

Page Elements	Management Task	First See Section...	Then See Section...
Create button in Condition Expressions page of Figure 12-24	Create a condition expression	"Accessing Condition Expression Management Tasks"	"Creating a Condition Expression"
Delete column in Condition Expressions page of Figure 12-24	Delete a condition expression		"Deleting a Condition Expression"
Update column in Condition Expressions page of Figure 12-24	Update a condition expression		"Updating a Condition Expression"
Name column in Condition Expressions page of Figure 12-24 (To access the details page in the lower page of Figure 12-24)	View details about a condition expression		"Viewing a Condition Expression"
Create button in Condition Parameters section of Condition Expression Details page of Figure 12-24	Create a condition parameter		"Creating a Condition Parameter"
Delete column in Condition Expression Details page of Figure 12-24	Delete a condition parameter		"Deleting a Condition Parameter"
Update column in Condition Expression Details page of Figure 12-24	Update a condition parameter		"Updating a Condition Parameter"
Create button in Details section in Condition Expression Details page of Figure 12-24	Build a condition expression		"Building a Condition Expression"
Name column in Condition Expression Details page of Figure 12-24	View a condition parameter		"Viewing a Condition Parameter"

See Also: The following sections for viewing datatype and event type details that are accessible from the Type column of the Condition Parameters section in the lower page of Figure 12-24: "Viewing a Complex Datatype" or "Viewing a Scalar Datatype" "Viewing a Business Event Type"

Accessing Condition Expression Management Tasks

Follow these instructions to access the condition expression management tasks shown in Figure 12-24:

To access condition expression management tasks:

1. Select the Modeling tab.

2. Select the Condition Expressions tab.

   The Condition Expressions page appears. (See the upper page of Figure 12-24.)

3. Select a task to perform and see the referenced section for instructions:

   To...	Then...	See Section...
   Create a condition expression	Click Create.	"Creating a Condition Expression"
   Delete a condition expression	Select a specific condition expression in the Delete column.	"Deleting a Condition Expression"
   Update a condition expression	Select a specific condition expression in the Update column.	"Updating a Condition Expression"
   View details about a condition expression	Select a specific condition expression in the Name column.	"Viewing a Condition Expression"
   Create a condition parameter	Select a specific condition expression in the Name column for which to create a condition parameter.	"Creating a Condition Parameter"
   Delete a condition parameter	Select a specific condition expression in the Name column for which to delete a condition parameter.	"Deleting a Condition Parameter"
   Update a condition parameter	Select a specific condition expression in the Name column for which to update a condition parameter.	"Updating a Condition Parameter"
   Build a condition expression with a condition parameter	Select a specific condition expression in the Name column with which to build an expression. Note: You cannot build a condition expression if there are no condition parameters.	"Building a Condition Expression"
   Viewing a condition parameter	Select a specific condition expression in the Name column for which to view a condition parameter.	"Viewing a Condition Parameter"

Creating a Condition Expression

Follow these instructions to create a condition expression:

To create a condition expression:

1. Ensure that you followed the instructions in "Accessing Condition Expression Management Tasks" to access the page for creating a condition expression.

   The Create Condition Expression page appears.

2. Enter a unique and recognizable name for the condition expression in the Name field.

3. Click Apply.

   The condition expression is created and the Condition Expression Details page for the created condition expression appears.

   See Also: "Creating a Condition Parameter" to add condition parameters to the condition expression

Deleting a Condition Expression

Follow these instructions to delete a condition expression:

Note: Deleting a condition expression also deletes all of its condition parameters. When you delete a condition step associated with a condition expression, the associated ports and map parameters are also removed.

To delete a condition expression:

1. Ensure that you followed the instructions in "Accessing Condition Expression Management Tasks" to access the page for deleting a condition expression.

2. Click Yes when prompted to delete a condition expression.

   The condition expression is deleted and the Condition Expressions page appears.

Updating a Condition Expression

Follow these instructions to update a condition expression:

To update a condition expression:

1. Ensure that you followed the instructions in "Accessing Condition Expression Management Tasks" to access the page for updating a condition expression.

   The Update Condition Expression page appears.

2. Make appropriate changes. (See Step 2 of "Creating a Condition Expression" for a list of fields that you can update.)

3. Click Apply.

   The condition expression is updated and the Condition Expression Details page for the updated condition expression appears.

Viewing a Condition Expression

Follow these instructions to view details about a specific condition expression:

To view a condition expression:

1. Ensure that you followed the instructions in "Accessing Condition Expression Management Tasks" to access the page for viewing a condition expression.

   The Condition Expression Details page for the selected condition expression appears.

   

   Text description of the illustration details_cond_express.gif

2. View specific details, including details about the condition parameters created for this condition expression. You use the condition parameters to build a condition expression.

   This page, as with the Condition Expressions page shown in the upper page of Figure 12-24, enables you to delete or update the selected condition expression.

3. Click Return to List to return to the Condition Expressions page.

Creating a Condition Parameter

Follow these instructions to create a condition parameter for a condition expression:

To create a condition parameter:

1. Ensure that you followed the instructions in "Accessing Condition Expression Management Tasks" to access the page for creating a condition parameter.

   The Condition Expression Details page for the selected condition expression appears.

2. Go to the Condition Parameters section. (See the lower page of Figure 12-24.)

3. Click Create.

   The Create Condition Parameter page appears.

4. Enter a unique and recognizable parameter name in the Name field of the General section.

5. Select Datatype or Event Type from the Type list of the Type section.

   The page refreshes to display additional fields.

6. If you selected Datatype, perform Steps 6a through Steps 6d.
   1. Select Application Datatype, Business Datatype, or Core Datatype from the Classification list.

   2. Select a namespace for the datatype from the Namespace list.

   3. Select a datatype name by clicking the flashlight next to the Name field.

   4. Click Apply.

7. If you selected Event Type, perform Steps 7a through Steps 7c.
   1. Select Application Event Type or Business Event Type from the Classification list.

   2. Select an event type name by clicking the flashlight next to the Name field.

   3. Click Apply.

   The condition parameter is created and the Condition Parameter details page for the created condition parameter appears.

8. Create additional condition parameters, if needed. Only one is required to build a condition expression.

   See Also: "Building a Condition Expression" to build a condition expression of condition parameters

Deleting a Condition Parameter

Follow these instructions to delete a condition parameter:

To delete a condition parameter:

1. Ensure that you followed the instructions in "Accessing Condition Expression Management Tasks" to access the page for deleting a condition parameter.

   The Condition Expression Details page for the selected condition expression appears.

2. Go to the Condition Parameters section. (See the lower page of Figure 12-24.)

3. Select a specific condition parameter to delete in the Delete column.

4. Click Yes when prompted to delete a condition parameter.

   The condition parameter is deleted and the Condition Parameter Details page appears.

Updating a Condition Parameter

Follow these instructions to update a condition parameter:

To update a condition parameter:

1. Ensure that you followed the instructions in "Accessing Condition Expression Management Tasks" to access the page for updating a condition parameter.

   The Condition Expression Details page for the selected condition expression appears.

2. Go to the Condition Parameters section. (See the lower page of Figure 12-24.)

3. Select a specific condition parameter to update in the Update column.

   The Update Condition Parameter page appears.

4. Make appropriate changes. (See Step 4 through Step 7 of "Creating a Condition Parameter" for a list of fields you can update.)

5. Click Apply.

   The condition parameter is updated and the Condition Parameter Details page for the updated condition parameter appears.

Building a Condition Expression

Follow these instructions to build a condition expression. This expression uses the condition parameters created in "Creating a Condition Parameter".

Note: You must first create at least one condition parameter before you can build a condition expression.

To build a condition expression:

1. Ensure that you followed the instructions in "Accessing Condition Expression Management Tasks" to access the page for building a condition expression.

   The Condition Expression Details page for the selected condition expression appears.

2. Go to the Condition Parameters section. (See the lower page of Figure 12-24.)

3. Click Create in the Details section.

   The Create Condition page appears.

4. Select Condition expression not specified.

5. Click Update to build a new condition expression.

   The Create Expression page appears.

6. Click Expand All for both columns to display all condition parameters.

   

   Text description of the illustration create_cond_express.gif

7. Select an element in the Left Operand section.

   Note: You can only select parameters of scalar datatypes as left and right operands.

8. Perform one of the following tasks in the Right Operand section:

   If You Want To...	Then...
   Enter a value	Click Constant and enter a value in the Constant field. For example, enter 50 for a scalar integer parameter named amount. Note: Only left operands can be assigned constant values.
   Select a parameter	Click Variable and select a parameter from the list of elements. For example, enter a parameter whose value is a company named ABCCompany for a scalar string parameter named ebe1.

9. Select an operator from the Operator list:
   • != (not equal to)

   • < (less than)

   • <= (less than or equal to)

   • = (equal to)

   • > (greater than)

   • >= (greater than or equal to)

   • Exists

10. Click Apply.

    The condition expression is built.

    

    Text description of the illustration details_condition_expression.gif

11. If you want to add more complicated logic to this condition expression, click Insert AND or Insert OR.

    You can now select this condition expression when creating a condition step type in a role on the Create Step in Role name page:

    

    Text description of the illustration create_condition_step.gif

    See Also: "Creating a Step" for instructions on creating a condition step type and selecting a condition expression (for this example, condition expression exp1 appears)

Viewing a Condition Parameter

Follow these instructions to view a condition parameter:

To view a condition parameter:

1. Ensure that you followed the instructions in "Accessing Condition Expression Management Tasks" to access the page for viewing a condition parameter.

   The Condition Expression Details page for the selected condition expression appears.

2. Go to the Condition Parameters section. (See the lower page of Figure 12-24.)

3. Select a specific condition parameter to view in the Name column.

   The Condition Parameter Details page appears.

   

   Text description of the illustration view_cond_param.gif

4. View specific details, including details including the datatype or namespace that can be associated with this parameter.

   This page, as with the Condition Expression Details page shown in the lower page of Figure 12-24, enables you to delete or update the selected condition parameter.

5. Click Return to List to return to the Condition Expression Details page.

Designing Roles to Ensure Proper Validation

This section provides examples of valid and invalid step, port, data flow, and control flow designs. Methods for avoiding these design problems are also described.

This section contains these topics:

• Loops

• Invalid Or Steps

• Invalid And Steps

• Invalid Merging of Data Flows from Step Ports to Role Port

• Invalid Merging of Data Flows Between Role Ports

• Current Modeling Restrictions

Loops

A loop is a series of steps connected either through data flows or control flows in which the last step connects back to the first step. Loops can be inside a single role or can span multiple roles. Do not create loops when designing steps in roles even though the Oracle Application Server ProcessConnect user interface tool does not prevent you from this activity. If you create loops, integration validation fails when you attempt to create a configuration to deploy.

Figure 12-25 shows a loop within a single transformation binding role. The highlighted data flow and control flow between Transformation 1 and Transformation 2 of Figure 12-25 identifies the invalid loop.

Figure 12-25 Loops Within a Single Role

Text description of the illustration modeling44.gif

Figure 12-26 shows a loop that spans a transformation binding role and a business role. The highlighted data flow and control flow between Transformation 1, Transformation 3, Split, and Transformation 2 identifies the invalid loop.

Figure 12-26 Loops Spanning Multiple Roles

Text description of the illustration ipusr071.gif

Invalid Or Steps

To ensure valid use of Or steps, only design mutually-exclusive control flows going into an Or step. Mutually-exclusive flows are a set of paths, with only one path possible at runtime. Valid Or steps prevent race conditions from occurring at runtime, which prevent nondeterminicity in the system.

Note: A condition step is the only means of introducing mutual exclusiveness in flows. Use Or steps only to merge paths coming directly or indirectly out of a condition step.

Invalid And Steps

To ensure valid use of And steps, only design nonmutually-exclusive data flows or control flows going into an And step. Nonmutually-exclusive control flows are paths that can be taken simultaneously at runtime. Valid And steps prevent infinite waits at these steps, which cannot execute because all of the incoming flows do not occur.

Note: Use And steps only to merge parallel paths not coming directly or indirectly out of a condition step.

Invalid Merging of Data Flows from Step Ports to Role Port

To ensure valid merging of data flows, do not design nonmutually-exclusive data flows going into one port. Nonmutually exclusive data flows are paths that can be taken simultaneously at runtime. Valid merging of data flows prevents repopulating of a currently-populated port.

This section provides detailed examples of valid and invalid Or steps, And steps, and mergings of data flows from step ports to role ports. Figure 12-27 provides an example of step design within a business process that is then described in detail.

Figure 12-27 Step Design

Text description of the illustration ipusr070.gif

In Figure 12-27 shows the following details:

• All paths along the isPOValid condition step (false) path are mutually exclusive with all paths along the isPOValid condition step (true) path (meaning that only one isPOValid condition step path (either true or false) is taken at runtime).

• All paths along the isPOValid condition step (false) path are nonmutually exclusive among themselves as long as there are no more condition steps encountered along the path (meaning that all paths are taken simultaneously at runtime).

• All paths along the isPOValid condition step (true) path to the isPOAmountGT1000 condition step path are nonmutually exclusive. After that, all paths along the isPOAmountGT1000 condition step (true) path are mutually exclusive with all paths of the isPOAmountGT1000condition step (false) path.

Table 12-12 shows the mutually exclusive and nonmutually exclusive paths in Figure 12-27.

Table 12-12  Mutually Exclusive and Nonmutually Exclusive Paths

Mutually Exclusive Paths

Nonmutually Exclusive Paths

isPOValid (false) and isPOValid (true) isPOValid (false)/generatePORejectMessage and isPOValid (true)/generatePOApproval isPOValid (false)/generatePORejectMessage and isPOValid (true)/generatePOApproval/Split2/isPOAmountGT1000 (true)/SetParty4 isPOValid (false)/generatePORejectMessage and isPOValid (true)/generatePOApproval/Split2/isPOAmountGT1000 (false)/SetParty3 isPOValid (false)/generatePORejectMessage/SetParty1 and isPOValid (true)/generatePOApproval/Split2/SetParty2 isPOValid (false)/generatePORejectMessage/SetParty1 and isPOValid (true)/generatePOApproval/Split2/isPOAmountGT1000 (false)/SetParty3 isPOValid (true)/generatePOApproval/Split2/isPOAmountGT1000 (false)/SetParty3 and isPOValid (true)/generatePOApproval/Split2/isPOAmountGT1000 (true)/SetParty4

isPOValid (true)/generatePOApproval/Split2/SetParty2 and isPOValid (true)/generatePOApproval/Split2/isPOAmountGT1000 (false)/SetParty3 isPOValid (true)/generatePOApproval/Split2/SetParty2 and isPOValid (true)/generatePOApproval/Split2/isPOAmountGT1000 (false)/SetParty4

If you want to connect all SetParty steps in Figure 12-27 to an End step, Table 12-13 describes the invalid possibilities.

Table 12-13  Connecting SetParty Steps to an End Step - Invalid Possibilities

Connection Tasks	Reason for Status
Connect all four SetParty steps to an End Step	There are mutually exclusive paths coming into an End step that are invalid. For example: isPOValid (false)/generatePORejectMessage/SetParty1 and isPOValid (true)/generatePOApproval/Split2/SetParty2
Connect all four SetParty steps to an Or step Connect the Or step to an End step	There are nonmutually exclusive paths coming into an Or Step that are invalid. For example: isPOValid (true)/generatePOApproval/Split2/SetParty2 and isPOValid (true)/generatePOApproval/Split2/isPOAmountGT1000 (false)/SetParty3
Connect SetParty1 and SetParty2 to an Or step (Or1) Connect SetParty3 and SetParty4 to another Or step (Or2) Connect the two Or steps to the End step	The status of these steps is as follows: Or1 step (Valid) All paths coming from SetParty1 are mutually exclusive with all paths coming from SetParty2. Or2 step (Valid) All paths coming from SetParty3 are mutually exclusive with all paths from SetParty4. End step (Invalid) Not all paths coming from Or1 are nonmutually exclusive with those from Or2. This is the same as saying that a path exists from Or1 that is mutually exclusive with a path from Or2. This can result in an infinite wait at runtime. For example: isPOValid (false)/generatePORejectMessage/SetParty1 and isPOValid (true)/generatePOApproval/Split2/isPOAmountGT1000 (false)/SetParty3

If you want to connect all SetParty steps in Figure 12-27 to an End step, Table 12-14 describes the valid possibilities.

Table 12-14  Connecting SetParty Steps to an End Step - Valid Possibilities

Connection Tasks	Reason for Status
Connect SetParty3 and SetParty4 to an Or Step (Or1) Connect SetParty2 and Or1 to an And Step (And1) Connect SetParty1 and And1 to an Or Step (Or2) Connect Or2 to End Step	The status of these steps is as follows: Or1 step (Valid) Paths coming from SetParty3 are mutually exclusive with paths from SetParty4. And1 step (Valid) All paths coming from Or1 are nonmutually exclusive with all paths from SetParty2. Or2 (Valid) Paths coming from SetParty1 are mutually exclusive with paths from And1. End (Valid) All paths are coming from only Or2 and are nonmutually exclusive.

If all four SetParty steps in Figure 12-27 have their own outbound role port (named p1, p2, p3, p4), Table 12-15 describes valid and invalid methods for merging data flows from the step ports on to a role port.

Table 12-15  SetParty Steps with Outbound Role Port

Connection Tasks	Status	Reason for Status
Connect p1, p2, p3, and p4 to one outbound role port using four different data flows	Invalid	Data flows from SetParty2 and SetParty3 (and therefore from p2 and p3) are nonmutually exclusive. At runtime, there can potentially be more than one event placed on the same port, which is illegal.
Connect p1 and p2 to one outbound role port	Valid	Paths from SetParty1 and SetParty2 (and therefore from p1 and p2) are mutually exclusive.
Connect p2 and p4 to one outbound role port	Invalid	Data flows from SetParty2 and SetParty4 (and therefore from p2 and p4) are nonmutually exclusive.
Connect p3 and p4 to one outbound role port	Valid	Paths from SetParty3 and SetParty4 (and therefore from p3 and p4) are mutually exclusive.

Invalid Merging of Data Flows Between Role Ports

This section describes the invalid merging of data flows from role ports on different transformation binding roles (that is, different spokes) to one role port on a business role in the inbound direction.

Do not merge data flows coming from various spokes, whose corresponding native roles are correlated, to one inbound role port on the business role. This is to prevent repopulating of an already-populated inbound role port on the business role. Correlated native roles mean that it is possible for the two spokes to be part of one coordination at runtime. Therefore, the possibility exists for repopulating the business role port. Figure 12-28 shows this behavior.

Figure 12-28 Native Event Correlation with Multiple Spokes

Text description of the illustration ipusr079.gif

Current Modeling Restrictions

There may be situations in which you know that given paths are mutually exclusive, but Oracle Application Server ProcessConnect does not. Oracle Application Server ProcessConnect therefore mandates that an And step be used in place of an Or step, which you may think is the correct choice. However, this action results in an infinite wait. In cases where this infinite wait cannot be avoided, design your steps so that this wait happens only at the End step and that there are no processing steps following this potentially indefinitely-waiting And step.

This results in the corresponding role instances not closing since their corresponding End steps have not executed. Consequently, the corresponding coordinations are also never closed. For these coordinations, you must explicitly close them through the Reports tab pages. Figure 12-29 shows this behavior:

Figure 12-29 Modeling Restrictions

Text description of the illustration ipusr073.gif

Assume only one of the ack or nack data flow always comes into Oracle Application Server ProcessConnect. There is currently no method in Oracle Application Server ProcessConnect to capture mutual exclusiveness properly across events entering Oracle Application Server ProcessConnect. Therefore, Oracle Application Server ProcessConnect assumes that both ack and nack always enter Oracle Application Server ProcessConnect. Consequently, Oracle Application Server ProcessConnect detects the design in Figure 12-29 as invalid. Figure 12-30 provides an example of how to validly design this situation without using an Or step.

Figure 12-30 Valid Role Data Flows

Text description of the illustration modeling20.gif

See Also: Chapter 23, "Creating Reports"

Role Runtime Behavior

This section describes the behavior of roles during runtime. This section contains these topics:

• Coordination

• Error Handling

Coordination

A coordination represents the execution of the business transaction represented by the business process. A coordination consists of the full set of role instances and event instances bound to a specific business process.

A native event instance is created from the wire message received by the adapter framework. As the event is processed by various roles in Oracle Application Server ProcessConnect, the appropriate role instances are created. The event can be translated into an application event instance and transformed into a business event instance before executing the business process.

The coordination is created when the initiating native event instance for the business process is raised by the adapter framework and picked up by the native role. As the event instance is being processed through the various roles, role instances are created for each of the role types in the business process. When a new native event is raised by the adapter framework, native event correlation is performed to match it with other native events that have been raised before this event.

There are two possibilities:

• If a correlated native event is not found, then the adapter framework tries to determine if there is a native role that can accept this event at its inbound port. This is done using the agreements between the party (application or trading partner) and native roles. If a native role is found, then a coordination is created. If a native role is not found, then an error occurs.

• If a correlated native event is found, then the newly-raised native event instance is sent to the same native role instance (and coordination) as the original native event instance. In this scenario, the new event instance joins the existing coordination.

The coordination is automatically closed when all the role instances are complete and there are no event instances waiting to be processed on any of the role ports.

The coordination may not close in one of the following scenarios:

• Scenario 1

  If all the events required by the business process have not been received; therefore, some of the steps have not been executed.

• Scenario 2

  If there is an error during the execution of any steps. If there is a system error during processing of the event or datatype instance, the operation is automatically retried. If there is a domain error that has not been designed, then coordination processing halts. The step does not produce an event on its OUT port and there is a returnCode datatype with the error message on the return code port. In this case, Oracle Application Server ProcessConnect automatically aborts the coordination.

• Scenario 3

  If there is an error in the way the roles have been designed, leading to a step that is waiting forever for data or events to appear. For example, if you have a condition step with two control flows (one for true and one for false), and these control flows are eventually connected to an AND step. In this case, there are mutually exclusive paths leading to an AND step, and this step never executes.

If the coordination is open and no new events are expected (as previously described in Scenario 1), then you can gracefully close the coordination from the Process Monitoring reports page in the design tool.

The coordination may also be open because of one of the error scenarios previously described in Scenario 2 and Scenario 3. In this case, the coordination must be aborted. This can be performed using the Process Monitoring reports page.

See Also: "Event Types and Event Instances" "Native Event Correlation" Chapter 3, "Oracle Application Server ProcessConnect Concepts" for additional details on event instances and role instances Chapter 23, "Creating Reports" for additional details about closing and aborting coordinations

Error Handling

If any errors occur during the processing of an event, Oracle Application Server ProcessConnect logs and handles the error depending on whether it is a system error or domain error.

See Also: Chapter 21, "Oracle Application Server ProcessConnect Error Handling" for additional details on diagnosing runtime problems and handling errors Chapter 23, "Creating Reports"

Common User Errors

The following are common business process and role management user errors.

• Ensure that you updated the SetParty step to point to the destination party in the agreement.

• Verify that data flow groups are created only between roles that can have data flows between them. For example, a translation binding role can only have data flows to either native roles or application roles. Verify this by clicking the integration diagram for each modeled business process.

• Modeling metadata must be deleted in a specific order. Otherwise, you receive errors. See "Design-Time Troubleshooting of Modeling Metadata Dependencies" for details.

Chapter Summary

This chapter describes how to manage business processes and roles, which includes managing role types, role ports, role data flow, steps, step ports, step data flow, and step control flow, as well as managing condition expressions in steps. With condition steps, you can define an action based on the evaluation of an expression. Role design to ensure proper validation and the behavior of role during runtime are also discussed.