|
Oracle® Application Server ProcessConnect User’s Guide
10g (9.0.4) Part No. B12121-02 |
|
|
|
|
Oracle® Application Server ProcessConnect User’s Guide
10g (9.0.4) Part No. B12121-02 |
|
|
|
|
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:
|
See Also: "Business Process and Role Creation Methods" for recommendations on when to create modeling metadata automatically with the wizards or manually |
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:
|
See Also: Chapter 3, "Oracle Application Server ProcessConnect Concepts" for additional details about modeling metadata |
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.
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
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:
|
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.
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:
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
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-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
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.
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.
This section describes several features common to all wizards:
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.
|
See Also: "Viewing the Metadata Modeling Diagrams" for a detailed description of the tasks you can perform with the modeling metadata diagrams |
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
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
The Event Flow Diagram includes three selections available from the Role Contents list under the Display Options section. (See Figure 9-14.)
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.
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
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.
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.
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.
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:
|
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 |
Click the Modeling tab.
Click the appropriate modeling wizard listed under the Shortcuts section.
Click the Modeling tab.
Click the Business Processes tab or Roles tab.
Click the appropriate modeling wizard under the Shortcuts section.
Click the Modeling tab.
Click the Business Processes or Roles tab.
Select an event flow diagram from the Event Flow Diagram column.
Select the appropriate modeling wizard in the Action list.
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. |
Use the Create End-To-End Basic Integration wizard to create two spokes.
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.
Enter a business process to create in the Business Process field.
Go to the Initiating Spoke section to initiate a request.
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. |
Enter a role naming convention to use as the prefix for all initiating roles in the Role Naming Convention field.
Go to the Invoked Spoke section to initiate a response.
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.
Enter a role naming convention to use as the prefix for all invoked roles in the Role Naming Convention field.
Click Next.
Go to "Reviewing Modeling Metadata Before Creation" to review an example of the final page of a wizard.
Use the Add End-To-End Basic Event Flow wizard to add additional event flow to two spokes.
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.
Select the business process that is used with the two spokes from the Business Process list.
Go to the Initiating Spoke section.
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. |
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. |
Go to the Invoked Spoke section.
Select the native role of the invoked spoke from the Native Role list.
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.
Click Next.
If the business event and transformation map names to be used exist, they are included in the spoke.
Go to "Reviewing Modeling Metadata Before Creation" to review an example of the final page of a wizard.
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
Start the Create Spoke wizard by following the instructions in "Starting the Modeling Wizards".
The Create Spoke: Business Process page appears.
Specify the business process to use for the event flow.
| To... | Then... |
|---|---|
| Create a new business process |
|
| Use an existing business process |
|
Click Next.
The Create Spoke: Interactions page appears.
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.
Click Next.
The Create Spoke: Roles page appears.
Enter the role naming convention to use as the prefix for all role names in the spoke in the Role Naming Convention field.
Click Next.
The Create Spoke: Events page appears.
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 |
|
| Use an existing business event |
|
|
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.
Click Next.
The Create Spoke: Transformations page appears.
Specify the transformation maps to use for the event flow.
| To... | Then... |
|---|---|
| Create a new transformation map |
|
| Use an existing transformation map |
|
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.
Click Next.
Go to "Reviewing Modeling Metadata Before Creation" to review an example of the final page of a wizard.
You can create additional event flows for an existing single spoke.
Start the Add Event Flow wizard by following the instructions in "Starting the Modeling Wizards".
The Add Event Flow: Interaction page appears.
Select the business process of the spoke from the Business Process list.
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. |
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.
Click Next.
The Add Event Flow: Events page appears.
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 |
|
| Use an existing business event |
|
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.
Click Next.
The Add Event Flow: Transformations page appears.
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 |
|
| Use an existing transformation map |
|
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.
Click Next.
Go to "Reviewing Modeling Metadata Before Creation" to review an example of the final page of a wizard.
The review page displays details about the type of modeling metadata for the wizard to create. Figure 9-12 and Figure 9-13 provide 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 (Upper Part: Initiating Spoke)
Figure 9-13 Wizard Review Page (Lower Part: Invoked Spoke)
Table 9-2 describes the review page sections shown in Figure 9-12 and Figure 9-13.
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:
|
| 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 and Figure 9-13.
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 |
Review the modeling metadata shown in Figure 9-12 and Figure 9-13.
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.
If you are satisfied with this modeling metadata, click Finish.
If modeling metadata creation is successful, the Event Flow Diagram appears. Go to "Reviewing Modeling Metadata After Creation".
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. |
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-14 through Figure 9-17.
|
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-18 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.
|
See Also: "Viewing an Integration Diagram " for details about the Agreement icon that displays beneath the Agreement header |
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 created by the wizards. You can access the page for creating event body elements in either of two ways:
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.
Follow the instructions in "Managing Business Event Types" to create event body elements.
Click Modeling > Event Types.
Select the business event created by the wizard in the Name column.
Follow the instructions in "Managing Business Event Types" to create event body elements.
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:
Select Display Details from the Action list of the Event Flow Diagram.
Click the Transform input_event_name step in red in the Transformation Binding Role of the Event Flow Diagram.
Click the Transformation Map link in the Details section of the Step Transform input_event_name page.
Follow the instructions in "Managing Transformation Statements" to define transformation rules for event transformation maps.
Click Modeling > Transformations.
Select the event transformation map created by the wizard in the Name column.
Follow the instructions in "Managing Transformation Statements" to define transformation rules for event transformation maps.
You can customize your modeling metadata by manually creating additional steps, ports, data flows, and control flows.
Go to Chapter 12, " Managing Business Processes and Roles " for instructions on manually creating additional steps, ports, data flows, and control flows.
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:
Select Display Details from the Action list of the Event Flow Diagram.
Click the SetParty for input_event_name step that displays in red in the business process of the Event Flow Diagram.
Click Update at the top of the Step SetParty for input_event_name page to select the target party.
Select the correct target party from the Party list.
Click Apply.
Click Modeling > Business Processes.
Select the business process in the Name column for which to update the SetParty step.
Go to the Steps section and select SetParty for input_event_name.
Click Update.
Select the correct target party from the Party list.
Click Apply.
Follow these instructions to delete a spoke.
|
Notes:
|
Click the Modeling tab.
Click the Business Processes or Roles tab.
Select the Event Flow Diagram from the Event Flow Diagram column for the spoke that you want to delete.
Select Delete Spoke in the Action list.
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.) |
Click Yes when prompted to delete the spoke.
This section describes common modeling wizard user errors.
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.
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
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).
