9
Creating Metadata with the Modeling Wizards

This chapter describes how to create integration modeling metadata with the assistance of the Oracle Application Server ProcessConnect modeling wizards.

This chapter contains these topics:

• Modeling Wizards Concepts Overview

• Modeling Wizards Overview

• Prerequisites to Using the Modeling Wizards

• Starting the Modeling Wizards

• Creating Two Spokes

• Adding Event Flow to Two Spokes

• Creating a Single Spoke

• Adding Event Flow to a Single Spoke

• Reviewing Modeling Metadata Before Creation

• Reviewing Modeling Metadata After Creation

• Tasks to Perform after Modeling Metadata Creation

• Deleting a Spoke

• Common Modeling Wizard Errors

• Chapter Summary

  See Also: "Business Process and Role Creation Methods" for recommendations on when to create modeling metadata automatically with the wizards or manually

Modeling Wizards Concepts Overview

The Oracle Application Server ProcessConnect user interface tool provides several modeling wizards that enable you to create modeling metadata. Before using these wizards, it is important to understand several key modeling wizard concepts:

• Single Spoke

• Multiple Spokes with a Business Process

• Event Flow in a Spoke

  See Also: Chapter 3, "Oracle Application Server ProcessConnect Concepts" for additional details about modeling metadata

Single Spoke

A single spoke consists of a role set extending from the native role to the business process. Role ports and data flow connect the role set together. A native role can belong to only a single spoke. This means that a spoke is uniquely identified by its native role. Figure 9-1 shows an Integration Diagram of a single spoke with the expense-NR native role.

Figure 9-1 Integration Diagram of a Single Spoke

Text description of the illustration spoke.gif

See Also: "Viewing an Integration Diagram" for instructions on viewing an Integration Diagram

Multiple Spokes with a Business Process

Multiple spokes connected by a single business process comprise an integration. A business process uniquely identifies an integration. The business process resides in the middle to connect all spokes in an integration. Figure 9-2 shows a single business process (Placing Ad) connecting two spokes. Each spoke has its own native role (HR Placing Ad-NR and Global NP Placing Ad-NR).

Figure 9-2 Integration Diagram of Multiple Spokes with a Business Process

Text description of the illustration model_wizards2.gif

Spokes consist of two types:

• An initiating spoke that contains the first inbound event and the native role bound to the first inbound interaction (for example, native role HR Placing Ad-NR at the far left of Figure 9-2)

• An invoked spoke that contains the first outbound event and the native role bound to the first outbound interaction (for example, native role Global NP Placing Ad-NR at the far right of Figure 9-2)

  See Also: Figure 9-3 for an Event Flow Diagram that shows the location of an interaction (far left) "Viewing an Integration Diagram" for instructions on viewing an Integration Diagram

Event Flow in a Spoke

An event flow is the complete path a single event takes through a spoke. An inbound event flow begins with an inbound interaction that produces an inbound native event. As the event flows from the native role to the business process, the native event is translated to an application event and the application event is transformed to a business event. An outbound event flow takes an event in the opposite direction, going from a business event in a business process to an outbound interaction bound to the native role.

Figure 9-3 shows a portion of the event flow in a spoke. The Event Flow Diagram shows the events and the role steps that process and pass the events (HR Ad in this example) through a spoke.

Figure 9-3 Event Flow Diagram of a Portion of a Spoke

Text description of the illustration wizard1.gif

See Also: "Viewing an Event Flow Diagram" for instructions on viewing an Event Flow Diagram

Modeling Wizards Overview

This section describes the four modeling wizards that enable you to create modeling metadata.

These modeling wizards provide different types of functionality:

• The Create End-to-End Basic Integration and Add End-to-End Basic Event Flow wizards create or update two spokes, respectively with a minimum of user input. Default values are provided for the names of business events and the transformation map to use. If these business events or transformation maps already exist, they are automatically used.

• The Create Spoke and Add Event Flow wizards only create or update a single spoke at a time, but provide you with more options. Both these wizards enable you to either select existing business events and transformation maps or specify the names of new ones to create.

This section contains these topics:

• Create End-To-End Basic Integration Wizard

• Add End-To-End Basic Event Flow Wizard

• Create Spoke Wizard

• Add Event Flow Wizard

• Features Common to All Wizards

Create End-To-End Basic Integration Wizard

The Create End-to-End Basic Integration wizard creates two spokes (with a new business process in the middle) and a single event flow that extends from the initiating spoke's native role to the invoked spoke's native role. Additional (end-to-end) event flows can be added with the Add End-to-End Basic Event Flow wizard. There are no options for selecting existing business events or transformation maps. All metadata is newly created.

The business event names generated are the same as the application event that is associated with the inbound interaction and native event selected. If this name matches an existing business event, the existing business event is used. The Create End-to-End Basic Integration wizard also uses an existing transformation map if there is a map that uses the same application event and business event as source and target parameters.

Figure 9-4 shows all the roles in an integration between two spokes.

Figure 9-4 Integration Diagram of Two Spokes

Text description of the illustration model_wizards17.gif

See Also: "Creating Two Spokes" to use the Create End-to-End Basic Integration wizard

Add End-To-End Basic Event Flow Wizard

The Add End-to-End Basic Event Flow wizard adds an additional event flow to two spokes extending from the native role in the initiating spoke to the native role in the invoked spoke. These two spokes and initial event flow are typically created with the Create End-to-End Basic Integration wizard. There are no options for selecting existing business events or transformation maps. In this case, all metadata is newly created.

You can also use the Add End-To-End Basic Event Flow wizard to add an event flow to two spokes that were created manually without the Create End-to-End Basic Integration wizard. In this case, ensure that both spokes are completely created before you use the Add End-to-End Basic Event Flow wizard. (that is, all roles and data flow groups connecting them are completely created). Otherwise, errors occur when you attempt to add event flow with the Add End-To-End Basic Event Flow wizard.

All generated pass-through, transformation, translation, and SetParty steps appear at the bottom of each role's Process Diagram with a control flow from the previous last step and another control flow to the end step.

The business event names generated are the same as the application event that is associated with the inbound interaction and native event selected. If this name matches an existing business event, the existing business event is used. The Add End-to-End Basic Event Flow wizard also uses an existing transformation map if there is a map that uses the same application event and business event as source and target parameters.

Figure 9-5 shows three roles in an event flow before running the Add End-To-End Basic Event Flow wizard.

Figure 9-5 Event Flow Diagram with One Event Flow

Text description of the illustration wizard2.gif

Figure 9-6 shows the same roles in the event flow after running the wizard. A second event flow is added.

Figure 9-6 Event Flow Diagram with Two Event Flows

Text description of the illustration event_flow_after.gif

See Also: "Adding Event Flow to Two Spokes" to use the Add End-to-End Basic Event Flow wizard

Create Spoke Wizard

The Create Spoke wizard creates a single spoke (extending from the native role to the business process) and a single event flow. This single spoke can be created for use in several places, including the following:

• As an additional spoke added to an end-to-end integration created with the Create End-to-End Basic Integration wizard

• As an initial or additional spoke added to an existing business process created manually without a wizard

Additional event flows can be added to this single spoke with the Add Event Flow wizard. This wizard performs the following tasks based on input you provide:

• Binds the spoke to an existing business process or creates a new business process

• Uses an existing business event or creates a new business event

• Uses an existing transformation map or creates a new map

When the business role ports are data flow-bound to ports on an existing business process, all unbound business process ports are searched for a correct match in event type and direction. If one exists, it is used. If one does not exist, a new business process port is created (and also a pass-through step and port with the opposite flow). If multiple ports match, the first matching unbound port is used. Figure 9-7 shows the third spoke that is added to an end-to-end basic integration.

Figure 9-7 Integration Diagram with Third Spoke

Text description of the illustration model_wizards10.gif

See Also: "Creating a Single Spoke" to use the Create Spoke wizard

Add Event Flow Wizard

The Add Event Flow wizard adds an additional event flow to a single spoke extending from the native role to the business process. This wizard performs the following tasks based on input you provide:

• Uses an existing business event or creates a new business event

• Uses an existing transformation map or creates a new map

• All generated pass-through, transformation, and translation steps appear at the end of each role's Process Diagram with a control flow from the previous last step and another control flow to the end step.

The event flow is added to the single spoke shown in the lower portion of Figure 9-7.

When the business role ports are data flow-bound to ports on an existing business process, all unbound business process ports are searched for a correct match in event type and direction. If one exists, it is used. If one does not exist, a new business process port is created (and also a pass-through step and port with the opposite flow). If multiple ports match, the first matching unbound port is used.

See Also: "Adding Event Flow to a Single Spoke" to use the Add Event Flow wizard

Features Common to All Wizards

This section describes several features common to all wizards:

• Diagrams

• Disabling a Native Event

• Modeling Metadata Name Creation

• Interactions

Diagrams

You can view diagrams that show various stages of modeling wizards design. Modeling metadata that is incomplete and requires you to perform additional steps outside the modeling wizards is highlighted in red in all diagrams.

• Integration Diagram

• Event Flow Diagram

• Process Diagram

• Step Binding Diagram

  See Also: "Viewing the Metadata Modeling Diagrams" for a detailed description of the tasks you can perform with the modeling metadata diagrams

Integration Diagram

Figure 9-8 shows an Integration Diagram, which identifies each role in the end-to-end integration. Click a specific role to view its steps in an Event Flow Diagram.

Figure 9-8 Integration Diagram of End-To-End Basic Integration

Text description of the illustration model_wizards4.gif

See Also: "Viewing an Integration Diagram" for instructions on viewing an Integration Diagram

Event Flow Diagram

Figure 9-9 shows a portion of the Event Flow Diagram, which identifies the events and role steps that process and pass the events through the two spokes of the end-to-end basic integration.

Figure 9-9 Event Flow Diagram of a Portion of an End-to-End Basic Integration

Text description of the illustration event_flow.gif

See Also: "Viewing an Event Flow Diagram" for instructions on viewing an Event Flow Diagram

The Event Flow Diagram includes three selections available from the Role Contents list under the Display Options section. (See Figure 9-13.)

• The Ports option displays the ports of a role or business process.

• The Steps (Simple) option displays the steps of each role or business process that have a single input and single output data flow (what the wizards create).

• The Complete Process Diagram option provides a comprehensive view of modeling metadata, including all steps, data flows, control flows, and ports.

Process Diagram

Each business process or role has a Process Diagram. Figure 9-10 shows a Process Diagram for a specific role or business process of the end-to-end basic integration. The Process Diagram identifies the events, steps, control flows, and data flows.

Figure 9-10 Process Diagram of a Role or Business Process

Text description of the illustration model_wizards7.gif

See Also: "Viewing a Process Diagram" for instructions on viewing a Process Diagram

Step Binding Diagram

Figure 9-11 shows a Step Binding Diagram.

Figure 9-11 Step Binding Diagram

Text description of the illustration diagram_sb2.gif

See Also: "Viewing a Step Binding Diagram" for instructions on viewing a Step Binding Diagram

Disabling a Native Event

If you select an outbound interaction that includes both an inbound request and an outbound response, you are prompted for additional information for handling the response. For the two End-To-End wizards, when one spoke has a response, you are prompted to select another interaction to handle the response at the other spoke. For the Create Spoke and Add Event Flow wizards, if there is a response, then you are prompted to create (or select existing) business events and transformation maps for both the request and the response event flows. Optionally, you can click the ignore box to specify that the response native event must be consumed in the inbound native role (preventing further processing from occurring). In this case, there is no event flow for the response.

Modeling Metadata Name Creation

Names are created that are not always unique. In some cases, you receive an error. For example, if a generated role name already exists, you must enter a different name in the Role Naming Convention field. In other cases, the name is made unique by appending a sequence number to the end. For example, if an event named ack flows multiple times in the same spoke, there are multiple role ports with the generated name of ack-OUT. The wizards make the port names unique by appending a sequence number, such as ack-OUT1 or ack-OUT2.

Interactions

The modeling wizards only list interactions for selection that are defined as complete. Incomplete interactions do not have a record type or have a record type that is not associated with a native event type or a native event that is not associated with an application event. The modeling wizards do not list these interactions.

Prerequisites to Using the Modeling Wizards

Ensure that you add the adapter interactions you want to use before using these wizards. The interactions are then selectable in the wizard pages. Interactions represent unique actions that can be performed with a specific adapter (such as requesting a purchase order, confirming a purchase order, and so on).

Ensure that you also create a native event for the interaction and specify a translator. You can perform this task either during or after you add an adapter interaction.

See Also: "Adding an Adapter Interaction" to add adapter interactions "Managing Native Event Types" to create native events and select translators

Starting the Modeling Wizards

Table 9-1 describes the locations from which the modeling wizards can be started.

Table 9-1  Starting the Modeling Wizards

Wizard	Start From Modeling Tab?	Start From Business Process Tab?	Start From Roles Tab?	Start From Event Flow Diagram?	Start From Integration Diagram?
Create End-To-End Basic Integration	Yes	Yes	No	No	No
Add End-To-End Basic Event Flow	Yes	Yes	Yes	Yes	No
Create Spoke	Yes	Yes	Yes	Yes	Yes
Add Event Flow	Yes	Yes	Yes	Yes	No

Starting From the Modeling Tab

1. Click the Modeling tab.

2. Click the appropriate modeling wizard listed under the Shortcuts section.

Starting From the Business Processes Tab or Roles Tab

1. Click the Modeling tab.

2. Click the Business Processes tab or Roles tab.

3. Click the appropriate modeling wizard under the Shortcuts section.

Starting From the Event Flow Diagram

1. Click the Modeling tab.

2. Click the Business Processes or Roles tab.

3. Select an event flow diagram from the Event Flow Diagram column.

4. Select the appropriate modeling wizard in the Action list.

5. Click inside the role in the Event Flow Diagram.

   Note: When you start a modeling wizard from the Event Flow Diagram, the current business process appears as the default selection in the wizard pages. Similar defaults exist for native roles. For the Add Event Flow Wizard, the native role defaults to the one selected in the Event Flow Diagram. For the Add End-to-End Basic Event Flow wizard, the two native roles default to the two that are displayed in the Event Flow Diagram.

Starting From the Integration Diagram

1. Click the Modeling tab.

2. Click the Business Processes or Roles tab.

3. Select an integration diagram from the Integration Diagram column.

4. Select Create Spoke in the Action list.

5. Click inside a role or business process in the Integration Diagram.

Creating Two Spokes

Use the Create End-To-End Basic Integration wizard to create two spokes.

1. Start the Create End-To-End Basic Integration wizard by following the instructions in "Starting the Modeling Wizards".

   The Create End-To-End Basic Integration page appears.

2. Enter a business process to create in the Business Process field.

3. Go to the Initiating Spoke section to initiate a request.

4. Select an inbound interaction from the Inbound Interaction list.

   The page refreshes to display the native event associated with this interaction.

   Note: If the inbound and outbound interactions you select on this page have a record associated with multiple native events, the page is refreshed to include a list from which to choose the appropriate native event.

5. Enter a role naming convention to use as the prefix for all initiating roles in the Role Naming Convention field.

6. Go to the Invoked Spoke section to initiate a response.

7. Select an outbound interaction from the Outbound Interaction list.

   The page refreshes to display the native event associated with this interaction.

   If you select an outbound interaction that includes both an outbound request and an inbound response, the page refreshes and prompts you to enter an additional interaction.

8. Enter a role naming convention to use as the prefix for all invoked roles in the Role Naming Convention field.

9. Click Next.

10. Go to "Reviewing Modeling Metadata Before Creation" to review an example of the final page of a wizard.

Adding Event Flow to Two Spokes

Use the Add End-To-End Basic Event Flow wizard to add additional event flow to two spokes.

1. Start the Add End-To-End Basic Event Flow wizard by following the instructions in "Starting the Modeling Wizards".

   The Add End-To-End Basic Event Flow page appears.

2. Select the business process that is used with the two spokes from the Business Process list.

3. Go to the Initiating Spoke section.

4. Select the native role of the initiating spoke from the Native Role list.

   Note: Only native roles that have the selected business process appear in the list.

5. Select an interaction from the Interaction list for the event flow of the initiating spoke.

   The page refreshes to display the native event associated with this interaction.

   Note: If the selected interaction has a record associated with multiple native events, the page is refreshed to include a list from which to choose the appropriate native event.

   Note: If you selected an outbound interaction that included both an outbound request and an inbound response, the page refreshes and prompts you to enter an additional interaction.

6. Go to the Invoked Spoke section.

7. Select the native role of the invoked spoke from the Native Role list.

8. Select an interaction from the Interaction list for the event flow of the invoked spoke.

   The page refreshes to display the native event associated with this interaction.

   If you select an outbound interaction that included both an outbound request and an inbound response, the page refreshes and prompts you to enter an additional interaction.

9. Click Next.

   If the business event and transformation map names to be used exist, they are included in the spoke.

10. Go to "Reviewing Modeling Metadata Before Creation" to review an example of the final page of a wizard.

Creating a Single Spoke

Use the Create Spoke wizard to create a single spoke. This single spoke can be created for use in several places, including the following:

• As an additional spoke added to an end-to-end integration created with the Create End-to-End Basic Integration wizard

• As an initial or additional spoke added to an existing business process created manually without a wizard

1. Start the Create Spoke wizard by following the instructions in "Starting the Modeling Wizards".

   The Create Spoke: Business Process page appears.

2. Specify the business process to use for the event flow.

   To...	Then...
   Create a new business process	Select Create New. Enter a business process name.
   Use an existing business process	Select Use Existing. Select a business process name from the list.

3. Click Next.

   The Create Spoke: Interactions page appears.

4. Select an interaction from the Interaction list from which to create the first event flow in the spoke. The direction of the selected interaction (inbound or outbound) determines the direction of the first event flow.

5. Click Next.

   The Create Spoke: Roles page appears.

6. Enter the role naming convention to use as the prefix for all role names in the spoke in the Role Naming Convention field.

7. Click Next.

   The Create Spoke: Events page appears.

8. Specify the business event to use for the event flow. The interaction that displays (either inbound or outbound) is based on the interaction you selected in Step 4.

   To...	Then...
   Create a new business event	Select Create New. Enter a business event name. This creates a business event with no event body element.
   Use an existing business event	Select Use Existing. Select a business event name from the list.

   Note: If the selected interaction has a record associated with multiple native events, a list of these native events from which to select is displayed.

   If you selected an outbound interaction in Step 4 that included both an outbound request and an inbound response, you are prompted to create business events for both.

9. Click Next.

   The Create Spoke: Transformations page appears.

10. Specify the transformation maps to use for the event flow.

    To...	Then...
    Create a new transformation map	Select Create New. Enter a transformation map name. This creates a transformation map with no rules defined.
    Use an existing transformation map	Select Use Existing. Select a transformation map name from the list.

    For an inbound event flow, the list of existing transformation maps includes only maps that have the application event as the source parameter and the business event as the target parameter. For an outbound event flow, the list of existing transformation maps includes only maps that have the business event as the source parameter and the application event as the target parameter.

    If you selected an outbound interaction in Step 4 that included both an outbound request and an inbound response, you are prompted to create transformation maps for both.

11. Click Next.

12. Go to "Reviewing Modeling Metadata Before Creation" to review an example of the final page of a wizard.

Adding Event Flow to a Single Spoke

You can create additional event flows for an existing single spoke.

1. Start the Add Event Flow wizard by following the instructions in "Starting the Modeling Wizards".

   The Add Event Flow: Interaction page appears.

2. Select the business process of the spoke from the Business Process list.

3. Select the native role of the spoke from the Native Role list.

   Note: Only native roles that use the selected business process appear in the list.

4. Select an interaction from the Interaction list for creating the event flow. The direction of the selected interaction (inbound or outbound) determines the direction of the first event flow.

5. Click Next.

   The Add Event Flow: Events page appears.

6. Specify the business event to use for the event flow. The interaction that displays (either inbound or outbound) is based on the direction you selected in Step 4.

   To...	Then...
   Create a new business event	Select Create New. Enter a business event name. This creates a business event with no event body element.
   Use an existing business event	Select Use Existing. Select a business event name from the list.

   If you selected an outbound interaction in Step 4 that included both an outbound request and an inbound response, you are prompted to create business events for both.

7. Click Next.

   The Add Event Flow: Transformations page appears.

8. Specify the transformation map to use for the event flow. The interaction that displays (either inbound or outbound) is based on the direction you selected in Step 4.

   To...	Then...
   Create a new transformation map	Select Create New. Enter a transformation map name. This creates a transformation map name with no rules defined.
   Use an existing transformation map	Select Use Existing. Select a transformation map name from the list.

   For an inbound event flow, the list of existing transformation maps includes only maps that have the application event as the source parameter and the business event as the target parameter. The application event is associated with the native event. The native event is associated with the record type that is associated with the chosen interaction.

   For an outbound event flow, the list of existing transformation maps includes only maps that have the business event as the source parameter and the application event as the target parameter.

   If you selected an outbound interaction in Step 4 that included both an outbound request and an inbound response, you are prompted to create transformation maps for both.

9. Click Next.

10. Go to "Reviewing Modeling Metadata Before Creation" to review an example of the final page of a wizard.

Reviewing Modeling Metadata Before Creation

The review page displays details about the type of modeling metadata for the wizard to create. Figure 9-12 provides an example of the type of information that displays for the review page of the Create End-To-End Basic Integration wizard.

Figure 9-12 Wizard Review Page

Text description of the illustration model_wizards11.gif

Table 9-2 describes the review page sections shown in Figure 9-12.

Table 9-2 Wizard Review Page

Page Element	Description
Role columns of the Initiating Spoke and Invoked Spoke sections	Identifies the roles involved in the event flow. The Create Spoke and Create End-to-End Basic Integration wizards create new roles, as indicated by the star symbol after the role name. The business process can be created new or an existing one can be selected. The Add Event Flow and the Add End-To-End Event Flow wizards always use existing roles.
Event columns of the Initiating Spoke and Invoked Spoke sections	Identifies the events and their directional flow through the roles. The native role to business process direction is inbound. A down arrow identifies the event flow direction as inbound. The business process to native role direction is outbound. An up arrow identifies the event flow direction as outbound. A business event may be created new (without an event body element) as indicated by a star symbol or an existing business event can be used. You must create the event body element separately.
Step columns of the Initiating Spoke and Invoked Spoke sections	Identifies the steps to be created in each role. Event transformation maps are created in transformation steps with no defined rules. You must define the rules separately. A SetParty step is also created in the business process. You must update the target party of the SetParty step separately.
New metadata (Identified by a sun icon)	Identifies modeling metadata to be newly created by the wizard.
Incomplete metadata (Identified by an exclamation point icon within a triangle)	Identifies incomplete modeling metadata that must be manually created outside of the wizard for your integration to be valid. Examples include the following: Event transformation maps with no defined rules, which display this message: You will need to populate the rules for this transformation map. Business events with no event body elements, which display this message: You will need to define the elements for this business event. SetParty steps that must be updated with the correct target party, which display this message: You will need to select a party for this SetParty step.
Business Process for both the Initiating Spoke and Invoked Spoke sections	Identifies the business process. When you create two spokes with the Create End-to-End Basic Integration wizard, the same business process is used for both spokes.

Table 9-3 through Table 9-5 provide additional details about the naming conventions for the modeling metadata to create.

Roles names are appended with the suffixes shown in Table 9-3. These details also display in the review page shown in Figure 9-12.

Table 9-3  Role Naming Conventions

For Role...	Suffix Is...	For Role...	Suffix Is...
Native role	-NR	Transformation binding role	-TX
Translation binding role	-TL	Business role	-BR
Application role	-AR

Data flow groups are appended with the suffixes shown in Table 9-4.

Table 9-4  Data Flow Group Naming Conventions

Data Flow Group Between...	Suffix Is...	Data Flow Group Between...	Suffix Is...
Native role and translation binding role	-NR-TL	Transformation binding role and business role	-TX-BR
Translation binding role and application role	-TL-AR	Business role and business process	-BR-BP
Application role and transformation binding role	-AR-TX

Port, step, and events follow the naming conventions shown in Table 9-5.

Table 9-5  Port, Step, and Event Naming Conventions

Metadata	Naming Convention	Example
Ports	Uses the event name appended with -IN or -OUT depending on whether it is an inbound or outbound port	HR Ad-IN where HR Ad is the inbound business event name
Pass-through steps	Uses the name Passthrough appended with the input event name	Passthrough HR Ad where HR Ad is the input event name
Translation steps	Named Translate and appended with the input event name	Translate HR Ad where HR Ad is the input event name
Transformation steps	Named Transform and appended with the input event name	Transform HR Ad where HR Ad is the input event name
Transformation maps	Named with the input event name	Transform HR Ad where Transform HR Ad is the input event name
Business events	Named the same as the inbound application event name. For an end-to-end wizard where there is both an inbound and outbound application event, the name of the application event in the initiating role is used.	HR Ad where HR Ad is the application event name
SetParty step	Named SetParty and appended with the inbound event name	SetParty for HR Ad where HR Ad is the inbound event name

1. Review the modeling metadata shown in Figure 9-12.
   1. To modify this modeling metadata, click the Back button of the modeling wizard to return to the previous pages. When you complete modifications, click Next until you access the review page; then click Finish.

   2. If you are satisfied with this modeling metadata, click Finish.

2. If modeling metadata creation is successful, the Event Flow Diagram appears. Go to "Reviewing Modeling Metadata After Creation".

3. If modeling metadata creation is unsuccessful, the wizard either returns you to the page requiring modifications or displays errors on the review page. Make appropriate modifications to the modeling metadata.

   Note: Do not use the Back or Forward buttons of your Web browser. Instead, use the Back and Next buttons specifically provided by the modeling wizards.

Reviewing Modeling Metadata After Creation

If event flow creation is successful, the Event Flow Diagram appears (in this example, the Event Flow Diagram that shows modeling metadata created by the Create End-to-End Basic Integration wizard). The Event Flow Diagram is very large. For this reason, it is broken down into four diagrams, as show in Figure 9-13 through Figure 9-16.

Figure 9-13 Event Flow Diagram: First Part

Text description of the illustration wizard1.gif

Note: The Event Flow Diagram identifies in red the business events that have no event body elements, transformation maps that have no defined rules, and the business process SetParty step that must be updated. You must separately complete these tasks to make your modeling metadata valid.

Figure 9-14 Event Flow Diagram: Second Part

Text description of the illustration wizard2.gif

Figure 9-15 Event Flow Diagram: Third Part

Text description of the illustration wizard3.gif

Figure 9-16 Event Flow Diagram: Fourth Part

Text description of the illustration wizard4.gif

Figure 9-17 shows the Integration Diagram of the two spokes created by the Create End-to-End Basic Integration wizard. The Agreement header displays for both native roles. When you add the native role of a spoke to an agreement, an Agreement icon displays beneath the Agreement header. You can click this icon to display the details page for the agreement.

Figure 9-17 Integration Diagram

Text description of the illustration model_wizards15.gif

See Also: "Viewing an Integration Diagram" for details about the Agreement icon that displays beneath the Agreement header

Figure 9-18 shows the Process Diagram of a role created by the Create End-to-End Basic Integration wizard. For this example, one of the transformation binding roles and its transformation step are shown.

Figure 9-18 Process Diagram

Text description of the illustration model_wizards16.gif

Tasks to Perform after Modeling Metadata Creation

After wizard creation, you must complete several additional steps to make your modeling metadata valid. You can also customize your modeling metadata by creating additional steps, ports, data flows, and control flows.

This section contains these topics:

• Create Event Body Elements for Business Events

• Define Transformation Rules for Event Transformation Maps

• Create Additional Steps, Ports, Data Flows, and Control Flows

• Update the Target Party of the SetParty Step

Create Event Body Elements for Business Events

Create event body elements for business events created by the wizards. You can access the page for creating event body elements in either of two ways:

• Access the Business Event from the Event Flow Diagram

• Access the Business Event from the Main Menu

Access the Business Event from the Event Flow Diagram

1. Click the business event name in red in the Event Flow Diagram. The business event name displays in red between each role from the inbound transformation binding role to the outbound transformation binding role.

2. Follow the instructions in "Managing Business Event Types" to create event body elements.

Access the Business Event from the Main Menu

1. Click Modeling > Event Types.

2. Select the business event created by the wizard in the Name column.

3. Follow the instructions in "Managing Business Event Types" to create event body elements.

Define Transformation Rules for Event Transformation Maps

Define transformation rules for event transformation maps created by the wizards. You can access the page for creating event transformation maps in either of two ways:

• Access the Event Transformation Map from the Event Flow Diagram

• Access the Event Transformation Map from the Main Menu

Access the Event Transformation Map from the Event Flow Diagram

1. Select Display Details from the Action list of the Event Flow Diagram.

2. Click the Transform input_event_name step in red in the Transformation Binding Role of the Event Flow Diagram.

3. Click the Transformation Map link in the Details section of the Step Transform input_event_name page.

4. Follow the instructions in "Managing Transformation Statements" to define transformation rules for event transformation maps.

Access the Event Transformation Map from the Main Menu

1. Click Modeling > Transformations.

2. Select the event transformation map created by the wizard in the Name column.

3. Follow the instructions in "Managing Transformation Statements" to define transformation rules for event transformation maps.

Create Additional Steps, Ports, Data Flows, and Control Flows

You can customize your modeling metadata by manually creating additional steps, ports, data flows, and control flows.

1. Go to Chapter 12, "Managing Business Processes and Roles" for instructions on manually creating additional steps, ports, data flows, and control flows.

Update the Target Party of the SetParty Step

Events originate from parties and are sent to parties. At some point in event processing, event addressing must be performed. Event addressing enables you to update the SetParty step with the target party with which to integrate. You can access the page for updating the target party in the SetParty step in either of two ways:

• Access the SetParty Step from the Event Flow Diagram

• Access the SetParty Step from the Main Menu

Access the SetParty Step from the Event Flow Diagram

1. Select Display Details from the Action list of the Event Flow Diagram.

2. Click the SetParty for input_event_name step that displays in red in the business process of the Event Flow Diagram.

3. Click Update at the top of the Step SetParty for input_event_name page to select the target party.

4. Select the correct target party from the Party list.

5. Click Apply.

Access the SetParty Step from the Main Menu

1. Click Modeling > Business Processes.

2. Select the business process in the Name column for which to update the SetParty step.

3. Go to the Steps section and select SetParty for input_event_name.

4. Click Update.

5. Select the correct target party from the Party list.

6. Click Apply.

Deleting a Spoke

Follow these instructions to delete a spoke.

Notes: When you delete a spoke, the business process is not deleted. You must separately delete the business process after deleting the spoke. If you delete a spoke that includes roles shared by another spoke (that is, there is data flow group branching), the shared roles are not deleted. The data flows to the shared roles are deleted (reducing the reuse count). When the last spoke that shares a role is deleted, the role is deleted.

1. Click the Modeling tab.

2. Click the Business Processes or Roles tab.

3. Select the Event Flow Diagram from the Event Flow Diagram column for the spoke that you want to delete.

4. Select Delete Spoke in the Action list.

5. Click inside the role in the Event Flow Diagram.

   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.)

6. Click Yes when prompted to delete the spoke.

Common Modeling Wizard Errors

This section describes common modeling wizard user errors.

• Using the Wrong Wizard

• Specifying a Previously-Used Role

Using the Wrong Wizard

The most common user error is using the wrong wizard. Specifically, you attempt to use the Create End-To-End Basic Integration wizard when you really want to add a spoke or an event flow to an existing business process.

The Create End-To-End Basic Integration wizard always creates a new integration, including a new business process. If you attempt to specify an existing business process, the Create End-To-End Basic Integration wizard tries to create a new business process with the same name and you get a UNIQUE CONSTRAINT VIOLATION error.

Error : There was an error creating the business process. 
Error -: AIP-16012: Parameter: owning Composite Step is unique for object 
Composite Step OwningCompositeStep.CompositeStep - 

Error -: AIP-11052: Writing following objects: Composite Step failed due to 
following constraint violation: COMPOSITESTEP_UK. UNIQUE CONSTRAINT VIOLATION 
Name - 

Error -: AIP-11052: Writing following objects: Composite Step
failed due to following constraint violation: COMPOSITESTEP_UK. UNIQUE 
CONSTRAINT VIOLATION 

The first error line is from the wizard, which identifies what it was doing at the time of the error. The two errors following that one are what the repository reports.

Specifying a Previously-Used Role

A similar problem occurs when you specify a role naming convention that was already used in another integration. This results in the wizard creating duplicate role names. You see the following error:

Error : There was an error creating native role bp1in-NR . 
Error -: AIP-16012: Parameter: owning Composite Step is unique for object 
Composite Step 
OwningCompositeStep.CompositeStep - 
Error -: AIP-11052: Writing following objects: Composite Step failed due to 
following constraint violation: COMPOSITESTEP_UK. UNIQUE CONSTRAINT VIOLATION  
Name - 
Error -: AIP-11052: Writing following objects: Composite Step failed due to 
following constraint violation: COMPOSITESTEP_UK. UNIQUE CONSTRAINT VIOLATION 

Chapter Summary

This chapter describes how to use the modeling wizards. With the modeling wizards, you can perform the following tasks:

• Create an end-to-end basic integration with the Create End-To-End Basic Integration wizard (that is, create two spokes with a new business process in the middle and a single event flow that extends from the native role of the initiating spoke to the native role of the invoked spoke).

• Add an additional event flow to two spokes with the Add End-To-End Basic Event Flow wizard (extending from the native role in the initiating spoke to the native role in the invoked spoke).

• Create a single spoke and event flow with the Create Spoke wizard (extending from the native role to the business process).

• Add an additional event flow to a single spoke with the Add Event Flow wizard (extending from the native role to the business process).