7 Tutorial of an Integration within an Enterprise

This chapter provides a simple tutorial on how to use the Oracle Application Server ProcessConnect user interface tool to design and deploy an integration within an enterprise.

This chapter contains these topics:

• Tutorial Overview

• Preparations before Starting

• Phase A: Creating and Deploying the Initial Configuration

• Phase B1: Manually Design Some Modeling Metadata in an Integration

• Phase B2: Using the Add Event Flow Wizard

• Phase B3: Using the Add Spoke Wizard

• Phase B4: Creating the HR Person Application and Agreement

• Manually Creating the Business Datatypes

• Updating the Interaction, Native Event, and Application Event

• .xsd and .xml Files Used in This Tutorial

• Chapter Summary

  
  

  See Also: Chapter 3, "Oracle Application Server ProcessConnect Concepts" for details on terms used in this chapter

  
  

7.1 Tutorial Overview

This section provides an overview of this tutorial.

7.1.1 Example Scenario

The tutorial describes the initial phase of a hiring process. Human resources must find candidates for a new position that is available within the company. The initial phase of this tutorial describes placing an ad in a newspaper. If there is a problem with placing an ad in the newspaper, a human resources person must be notified. Otherwise, human resources assumes the ad is successfully placed.

The scenario uses the following applications:

• A Human Resources application sends the ad placement request to a Global Newspaper application over a file system.

• The Global Newspaper application receives the request and places a confirmation on the file system.

• If there is a problem with the ad placement request, the Global Newspaper application notifies a Human Resources Person application.

7.1.2 Human Resources Application Details

The Human Resources application places a file on the file system containing one or more ads. The file contains additional information indicating whether this is a new ad or a change request for an existing ad. In the case of multiple ads, all ads must be placed in the same newspaper.

7.1.3 Global Newspaper Application Details

The Global Newspaper application expects the Human Resources application to place an ad as a file on the file system. The newspaper always places a confirmation file back on the file system. The confirmation indicates whether the placement was successful or if there was a problem. Although this tutorial uses the file system, an alternative method can be used, such as using Web services or secure HTTP with a custom XML file.

7.1.4 Human Resources Person Application Details

If a problem occurs, human resources expects the problem to be placed as a file on the file system. Although this tutorial uses the file system, other methods can be used, such as using SMTP and sending an e-mail.

7.1.5 Overview of Phases

This tutorial is divided into two phases:

• Phase A

• Phase B1 through B4

7.1.5.1 Phase A

You perform the following tasks in this phase:

• Create the Human Resources and Global Newspaper applications, add an adapter to each application, and create delivery channels for the adapter of each application

• Validate and approve the applications

• Design the HR_Ad.xsd file to be delivered to the global newspaper. In this task, you create one interaction to read the ad placement request from the human resources file system and a second interaction to write the file to the global newspaper file system.

• Create the native and application events and specify a translator for each application.

• Use the Create End-to-End Basic Integration wizard to create a pass-through process between the two interactions.

• Import the business (common view) datatypes for the business event.

• Create the business event body element and include the imported business datatypes.

• Design the inbound and outbound transformations between the application events and the business event.

• Update the SetParty step in the business process to include the Global Newspaper application as the destination party in this integration.

• Create the application agreements for both applications, and add a delivery channel and native role to each agreement.

• Validate and approve the agreements.

• Deploy and test the integration.

7.1.5.2 Phase B1 through B4

You perform the following tasks in this phase:

• Enhance the business process to notify a Human Resources Person application in case of problems by manually performing some business process modeling.

• Create two new native events: one for the problem notification message to the Human Resources Person application and one for the confirmation message from the Global Newspaper application.

• Use the Add Event wizard to integrate the new native event from the global newspaper with the business event.

• Use the Add Spoke wizard to integrate the native event from the human resources person with the business process.

• Create the Human Resources Person application.

• Validate and approve the application.

• Create the human resources person application agreement, and add a delivery channel and native role.

• Validate and approve the agreement.

• Deploy and test the integration.

  
  

  See Also: Chapter 13, " Managing Transformations" to model additional transformations that use the same example files as this tutorial

  
  

7.2 Preparations before Starting

The following .xsd files are provided in the $ORACLE_HOME/ip/import directory for the different applications used in this tutorial:

• HR_Ad.xsd

• HR_AdProblem.xsd

• Global_Newspaper_Ad.xsd

• Global_NP_AdConfirmation.xsd

• Ad_CommonView.xsd

The following .xml files are also provided in the $ORACLE_HOME/ip/demo/tutorial directory:

• HR_Ad.xml

• Global_NPConfirmation.xml

Perform the following tasks:

1. Ensure that the XML Schema definition .xsd files are in the import directory before starting this tutorial. The import directory is configured as a server property and can be modified through Oracle Enterprise Manager 10g. The directory setting defaults to $ORACLE_HOME/ip/import (where $ORACLE_HOME is the middle-tier Oracle Application Server instance).

   These files are also located at the back of this chapter.

2. Create a directory named tutorial anywhere you want (for example, $ORACLE_HOME/ip/tutorial)

3. Create the following subdirectories under tutorial.

   • human_resources/inbound

   • global_newspaper/inbound

   • global_newspaper/outbound

   • hr_person/outbound

4. Place these two .xml instance files in the tutorial directory:

   • HR_Ad.xml

   • Global_NP_AdConfirmation.xml

     
     

     See Also: "Oracle Application Server ProcessConnect Middle-Tier Instance Configuration Parameters" for instructions on modifying server properties with Oracle Enterprise Manager 10g

     
     

7.2.1 Methods to Designing the Tutorial

There are several methods for designing the tutorial:

• You can start designing the business process completely or partly and integrate the events with the parties.

• You can start designing some of the interactions with the parties and work toward the business process.

• You can start designing datatypes and work toward the process modeling.

• You can start designing the end-to-end process and then design the data details.

This tutorial does not follow one single method; it is a mix that provides many examples used by the different methods.

7.3 Phase A: Creating and Deploying the Initial Configuration

This phase of the tutorial describes how to design and deploy an integration (known as a configuration) between the Human Resources and Global Newspaper applications.

This section contains these topics:

• Task 1: Creating Application Details

• Task 2: Creating the Modeling Metadata

• Task 3: Creating the Agreements

• Task 4: Creating and Deploying a Configuration

• Task 5: Testing the Results

• Task 6: Troubleshooting Any Errors with Log Files and Reports

7.3.1 Task 1: Creating Application Details

This section contains the following tasks:

• Creating the Human Resources Application

• Adding an Adapter to the Human Resources Application

• Creating the Delivery Channel for the Human Resources Application Adapter

• Validating the Human Resources Application

• Sending the Application for Approval

• Approving the Application

• Creating the Global Newspaper Application

• Adding an Adapter to the Global Newspaper Application

• Creating the Delivery Channel for the Global Newspaper Application Adapter

• Validating the Global Newspaper Application

• Sending the Application for Approval

• Approving the Application

  
  

  See Also: The following sections for additional details about tasks covered in this section: "Creating an Application" "Adding an Adapter to an Application" "Creating an Application Delivery Channel" "Managing Application and Agreement Validation and Approval"

  
  

7.3.1.1 Creating the Human Resources Application

Create an application named Human Resources to send the inbound ad.

1. Select the Profiles tab.

2. Select the Applications tab.

3. Click Create.

4. Enter Human Resources in the Name field.

5. Select the Generic application type from the Application Type list. The application type enables you to group applications of a similar type together.

6. Click Apply.

   The Human Resources application is created and the Application Details : Human Resources page appears.

7.3.1.2 Adding an Adapter to the Human Resources Application

Add an adapter to the Human Resources application by selecting from a list of previously-configured adapters provided by Oracle Application Server ProcessConnect. This adapter provides the connectivity that enables the Human Resources application with its unique data formats and interface to communicate with Oracle Application Server ProcessConnect.

1. Click Add in the Adapter Types section of the Application Details : Human Resources page.

2. Select File/FTP Adapter from the Type list.

3. Click Apply.

   The Adapter Type Details page of the adapter appears.

7.3.1.3 Creating the Delivery Channel for the Human Resources Application Adapter

Create a delivery channel for the adapter to use. The delivery channel describes the communication capabilities (such as message exchange and security details) of the specific adapter of the Human Resources application. Each adapter has its own unique delivery channel questions.

1. Click Create in the Delivery Channels section of the Adapter Type Details page of the adapter.

2. Enter the following details:

   Field	Enter/Select
   Name	HR DC
   File or FTP mode	File
   Polling interval in milliseconds (inbound)	10000
   Base directory	start_at_root/ip/tutorial/human_resources where start_at_root must be the absolute path (for example, /private/Oracle). Note: Do not use the $ORACLE_HOME variable when specifying a base directory. This is the directory from which the inbound ad is read and is the directory path you created in Step 2.

   
   

Note: Do not enter information in any other fields; the other fields on this page only apply when using FTP mode with the File/FTP adapter.

3. Click Apply.

7.3.1.4 Validating the Human Resources Application

Validate the application to ensure the correctness of the profile data you entered.

1. Click Return to List.

2. Click Return to List.

3. Click Validate on the Application Details : Human Resources page.

   If validation is successful, the Validate button name changes to Send for Approval. If validation is unsuccessful, error messages appear. Make corrections based on the error messages.

7.3.1.5 Sending the Application for Approval

You can select an approver to approve the profile data of your application (for example, to ensure that the delivery channel details you specified are correct).

1. Click Send for Approval.

2. Select approvers (for example, the user admin) from the Available Approvers list.

3. Click Move to move the approver(s) to the Selected Approvers list.

4. Click Send for Approval.

   Your selection appears in the Approvers section of the Application Details: Human Resources page. The Send For Approval button is replaced with an Approve button and the Validated status that displays in the State field of the Details section is replaced with Pending Approval.

   At this point, you can export the application details to an XML file for submittal to a person for approval. For this tutorial, this task is not performed. Instead, the profile data in this application is assumed to be approved by all persons.

7.3.1.6 Approving the Application

You must approve the application.

1. Click Approve.

2. Click Approve again when prompted to confirm.

7.3.1.7 Creating the Global Newspaper Application

Create a second application named Global Newspaper to receive the ad request and place a confirmation file back on the file system.

1. Select the Profiles tab.

2. Select the Applications tab.

3. Click Create.

4. Enter Global Newspaper in the Name field.

5. Select the Generic application type from the Application Type list.

6. Click Apply.

   The Global Newspaper application is created and the Application Details: Global Newspaper page appears.

7.3.1.8 Adding an Adapter to the Global Newspaper Application

Add an adapter to the Global Newspaper application by selecting from a list of previously-configured adapters provided by Oracle Application Server ProcessConnect. This adapter provides the connectivity that enables the Global Newspaper application with its unique data formats and interface to communicate with Oracle Application Server ProcessConnect.

1. Click Add in the Adapter Types section of the Application Details: Global Newspaper page.

2. Select File/FTP Adapter from the Type list.

3. Click Apply.

   The Adapter Type Details page for the adapter appears.

7.3.1.9 Creating the Delivery Channel for the Global Newspaper Application Adapter

Create a delivery channel for the adapter to use. The delivery channel describes the communication capabilities (such as message exchange and security details) of the specific adapter of the Global Newspaper application. Each adapter has its own unique delivery channel questions.

1. Click Create in the Delivery Channels section of the Adapter Type Details page of the adapter.

2. Enter the following details:

   Field	Enter/Select
   Name	Global NP DC
   File or FTP mode	File
   Polling interval in milliseconds (inbound)	10000
   Base directory	start_at_root/ip/tutorial/global_newspaper where start_at_root must be the absolute path (for example, /private/Oracle). Note: Do not use the $ORACLE_HOME variable when specifying a base directory. This is the directory in which to receive the ad request and is the directory path you created in Step 2.

   
   

3. Click Apply.

7.3.1.10 Validating the Global Newspaper Application

Validate the application to ensure the correctness of the profile data you entered.

1. Click Return to List.

2. Click Return to List.

3. Click Validate on the Application Details : Global Newspaper page.

   If validation is successful, the Validate button name changes to Send for Approval. If validation is unsuccessful, error messages appear. Make corrections based on the error messages.

7.3.1.11 Sending the Application for Approval

You can select an approver to approve the profile data of your application (for example, to ensure that the delivery channel details you specified are correct).

1. Click Send for Approval.

2. Select approvers (for example, the user admin) from the Available Approvers list.

3. Click Move to move the approver(s) to the Selected Approvers list.

4. Click Send for Approval.

   Your selection appears in the Approvers section of the Application Details: Global Newspaper page. The Send For Approval button is replaced with an Approve button and the Validated status that displays in the State field of the Details section is replaced with Pending Approval.

   At this point, you can export the application profile data to a file for submittal to a person for approval. For this tutorial, this task is not performed. Instead, the profile data in this application is assumed to be approved by all persons.

7.3.1.12 Approving the Application

You must approve the application.

1. Click Approve.

2. Click Approve again when prompted to confirm.

3. Click the Applications tab to see the newly created Human Resources and Global Newspaper applications displayed in the Name column of the Applications page. Click these applications to see the details about the adapters and delivery channels that you associated with these applications.

7.3.2 Task 2: Creating the Modeling Metadata

This section contains the following tasks:

• Creating the Inbound Interaction for the Human Resources Application Adapter

• Creating the Native Event, Translation, and Application Event for the Human Resources Application

• Creating an Event Map for the HR New Ad Native Event

• Creating the Outbound Interaction for the Global Newspaper Application Adapter

• Creating the Native Event, Translation, and Application Event for the Global Newspaper Application

• Creating an Event Map for the Global NP Ad Native Event

• Creating the Modeling Metadata with the Modeling Wizards

• Creating the Business Event Datatypes

• Creating the Business Event Body Element

• Creating the Rules for the Inbound Event Transformation Map

• Creating the Rules for the Outbound Event Transformation Map

• Selecting the Destination Party in the SetParty Step

  
  

  See Also: The following sections for additional details about tasks covered in this section: "Managing Adapter Interactions" "Creating Native and Application Event Types and Body Elements" "Creating Two Spokes" with the Create End-To-End Basic Integration wizard "Importing XSD Datatypes" "Managing Business Event Types" "Transformation Statements Overview" "Managing Steps"

  
  

7.3.2.1 Creating the Inbound Interaction for the Human Resources Application Adapter

For the File/FTP adapter you added in "Adding an Adapter to the Human Resources Application" to read the file from an inbound directory, an inbound interaction must be defined. An interaction provides the adapter with the details to deliver and retrieve events to and from Oracle Application Server ProcessConnect. Interactions represent unique actions that can be performed with a specific adapter.

This task creates the interaction to read files with the extension xml from the human_resources directory (the subdirectory of tutorial that you specified in the delivery channel questions at Step 2). The questions that display onscreen are unique to the File/FTP adapter. The native format must be provided to describe the contents of the body element of the native event (that is, what comes in as an Oracle record from the adapter). Based on the native format, a number of extractors (and later also translators) are available. The extractor is used for event map and correlation.

1. Select the Modeling tab.

2. Select the Interactions tab.

3. Click Add.

4. Expand Adapter Providers > Oracle.

5. Select the File/FTP Adapter.

6. Expand Adapter Exchange Protocols > Inbound > File.

7. Select Read File(FileRecord).

8. Enter the following details:

   Field	Enter/Select
   Directory (relative path) for incoming files	inbound Note: You created this directory in Step 3 of "Preparations before Starting". Note also the relationship to the delivery channel directory you created in Step 2; inbound is a subdirectory of human_resources.
   Maximum number of files to read for each poll	1
   File extension for the incoming files - for example, txt *	xml

   
   
   
   

   Note: Recheck your answers in Step 8 to ensure their correctness. Updating an interaction at a later time is difficult.

   
   

9. Click Apply.

10. Ensure that the Create Native Event Type box is selected.

11. Click Apply on the Add Interaction : Review page.

12. Ensure that XSD is selected in both the Native Format list and the Extractor list.

13. Click Apply.

    
    

    See Also: "Updating the Interaction, Native Event, and Application Event" to update an interaction used with a business process

    
    

7.3.2.2 Creating the Native Event, Translation, and Application Event for the Human Resources Application

The inbound ad request of the Human Resources application initially appears in its own unique native format that Oracle Application Server ProcessConnect cannot interpret. This native format can consist of several different parts, including headers, attachments, and payloads. The payload can identify details such as the person submitting the ad request, their phone number, the date, and so on.

The native format received by Oracle Application Server ProcessConnect is represented as an Oracle record on the Oracle Application Server ProcessConnect boundary. A native event is created from the Oracle record. A native event is the Oracle Application Server ProcessConnect internal implementation of the business data contained in an Oracle record. The different parts of the native format (such as the payload) are placed into different parts called body elements in a native event. In addition, the transmission structure of the native format is removed (such as encoding, packaging, signing, or encryption).

When you create a native event, you also specify a translator to translate the contents of the inbound native event into an inbound application event, which represents an interpretable syntactic format understood by Oracle Application Server ProcessConnect.

1. Enter HR New Ad in the Name field of the Create Native Event Type page.

2. Click Next.

3. Select XSD from the Translator list.

4. Enter HR Ad in the Name field of the Native Datatype section.

5. Click Browse next to the Content field.

6. Select HR_Ad.xsd.

   Your selection appears in the Content field.

7. Click Next.

8. Select XSD from the Translator list. The translators available for selection are limited to those that can handle the native format you selected in Step 12.

9. Select Yes from the Preserve Namespaces for Native Instances list.

10. Select None from the Doctype for Native Instances list. The page refreshes.

11. Click Next.

12. Review your selections and click Finish on the Review page.

    The native event and application event are created.

13. Click HR New Ad in the Name column of the Native Event Types page.

    The steps you performed in this section took the inbound ad request in its native format, created a native event named HR New Ad, and placed the payload part of the native format into a native event body element (named PAYLOAD):

Description of the illustration tut_net.gif

14. Click Event Types > Application Event Types to review the newly created application event.

15. Select HR New Ad in the Name column. (Note that the application event has the same name as the native event.)

16. Click Expand All in the Event Body Elements section.

    The steps you performed in this section translated the inbound native event into an inbound application event named HR New Ad and created an event body element (named PAYLOAD) for the payload part that includes the following application event datatypes. Application events contain no native formats. The particular native format of the Human Resources application cannot be identified, and any specific syntactic properties have been removed.

Description of the illustration tut_ae2.gif

Remember these datatypes. Later in this tutorial in "Creating the Rules for the Inbound Event Transformation Map", you create a transformation rule to transform this source inbound application event and its application datatypes to a target inbound business event and its business datatypes.

7.3.2.3 Creating an Event Map for the HR New Ad Native Event

Event maps determine the native event type for a specific record type from an interaction. In this tutorial, the File/FTP adapter reads any file with an .xml extension.

1. Select the Modeling tab.

2. Select the Event Types tab.

3. Select Native Event Types.

4. Select HR New Ad in the Name column.

5. Click Create in the Event Map section.

6. Select Condition expression not specified.

7. Click Update to create a new event map.

8. Click Expand All on the Create Condition Expression page.

9. Select Action.

10. Select = from the Operator list.

11. Enter HR New Ad Request in the Constant Value field.

12. Click Apply.

13. Click Apply on the Create Event Map page. The event map condition displays in the Event Map section.

Description of the illustration tut_em1.gif

7.3.2.4 Creating the Outbound Interaction for the Global Newspaper Application Adapter

For the File/FTP adapter you added in "Adding an Adapter to the Global Newspaper Application" to write the file to an outbound directory, an outbound interaction must also be defined.

This task creates the outbound interaction to write an ad_%TIME%.xml file to the outbound directory.

1. Select the Modeling tab.

2. Select the Interactions tab.

3. Click Add.

4. Expand Adapter Providers > Oracle.

5. Select the File/FTP Adapter.

6. Expand Adapter Exchange Protocols > Outbound > File.

7. Select Write File(FileRecord).

8. Enter the following details:

   Field	Enter/Select
   Directory (relative path) for incoming files	outbound Note: You created this directory in Step 3 of "Preparations before Starting". Note also the relationship to the delivery channel directory you created in Step 2; outbound is a subdirectory of global_newspaper.
   Staging directory (relative path) for outgoing files	Leave this field blank.
   File naming convention for outgoing files (without extension) - for example, po_%TIME%	%TIME%
   File extension for the incoming files - for example, txt *	xml

   
   
   
   

   Note: Recheck your answers in Step 8 to ensure their correctness. Updating an interaction at a later time is difficult.

   
   

9. Click Apply.

10. Ensure that the Create Native Event Type box is selected.

11. Click Apply.

12. Ensure that XSD is selected in both the Native Format list and the Extractor list.

13. Click Apply.

7.3.2.5 Creating the Native Event, Translation, and Application Event for the Global Newspaper Application

You must also create a native event and specify a translator to translate the outbound application event to an outbound native event. This is similar to what you did for the Human Resources application in "Creating the Native Event, Translation, and Application Event for the Human Resources Application". The only difference is that it operates in the outbound direction.

1. Enter Global NP Ad in the Name field of the Create Native Event Type page.

2. Click Next.

3. Select XSD from the Translator list.

4. Select Create New in the Native Datatype section.

5. Enter Global NP Ad in the Name field.

6. Click Browse next to the Content field.

7. Select Global_Newspaper_Ad.xsd and click Select.

   Your selection appears in the Content field.

8. Click Next.

9. Select XSD from the Translator list. The translators available for selection are limited to those that can handle the native format you selected in Step 12.

10. Select Yes from the Preserve Namespaces for Native Instances list.

11. Select None from the Doctype for Native Instances list. The page refreshes.

12. Click Next.

13. Review your selection and Click Finish on the Review page.

    The native and application events are created.

14. Click Global NP Ad in the Name column of the Native Event Types page.

    The Native Event Type Details page appears:

Description of the illustration tut_net_out.gif

15. Click Event Types > Application Event Types to review the newly created application event.

16. Select Global NP Ad in the Name column.

17. Click Expand All in the Event Body Elements section.

    The steps you performed in this section translated the outbound application event and its event body element of application event datatypes into an outbound native event with an event body element for the payload (named PAYLOAD).

Description of the illustration tut_notif_event.gif

Remember these datatypes. Later in this tutorial in "Creating the Rules for the Outbound Event Transformation Map", you create a transformation rule to transform the outbound business event and its business datatypes to an outbound application event and its application datatypes.

At this point the Human Resources application includes its own inbound native event, translator, application event, and event body elements of datatypes. The Global Newspaper application includes its own outbound native event, translator, application event, and event body elements of datatypes.

7.3.2.6 Creating an Event Map for the Global NP Ad Native Event

Event maps determine the native event type for a specific record type from an interaction.

1. Select the Modeling tab.

2. Select Event Types.

3. Select Native Event Types.

4. Select Global NP Ad in the Name column.

5. Click Create in the Event Map section.

6. Select Condition expression not specified.

7. Click Update to create a new event map.

8. Click Expand All in the Create Condition Expression page.

9. Select Action.

10. Select = from the Operator list.

11. Enter Global NP Ad in the Constant Value field.

12. Click Apply.

13. Click Apply on the Create Event Map page.

    The event map condition displays in the Event Map section.

Description of the illustration tut_em2.gif

7.3.2.7 Creating the Modeling Metadata with the Modeling Wizards

For the events you have created to move through and be executed by Oracle Application Server ProcessConnect, you must create roles, a business process, and other modeling metadata. Roles define how events are executed and implement the behavior of the Human Resources and Global Newspaper applications (known as the parties), and the entire integration. The business process spans both applications to coordinate the sending and receiving of events. This management ensures that the Human Resources and Global Newspaper applications send and receive the correct data. Business processes also hide the unique characteristics of the Human Resources and Global Newspaper applications from the integration.

Use the modeling wizard to create the modeling metadata, including the following:

• The Human Resources application native role, translation binding role, application role, transformation binding role, and business role

• The Global Newspaper application native role, translation binding role, application role, transformation binding role, and business roles

• The business process that operates in the middle of these roles

• The event transformation maps for both applications with no defined rules (you define these rules later in this tutorial)

• The third and final event, known as the business event. At this point, you have already created the native and application events. This business event includes no event body element (you create that element later in this tutorial).

Follow these procedures to create this modeling metadata:

1. Select the Modeling tab.

2. Select the Business Processes tab.

3. Click Create End-To-End Basic Integration in the Shortcuts section.

4. Enter Placing Ad in the Business Process field.

5. Select Read File - inbound (xmlRecord) - Inbound from the Inbound Interaction list (for the inbound ad request sent by the Human Resources application). This interaction is available for selection because you:

   • Added Read File(FileRecord) as the inbound interaction in Step 7 of "Creating the Inbound Interaction for the Human Resources Application Adapter".

   • Entered xml as the file extension for the incoming file in Step 8.

6. Select HR New Ad from the Native Event list. This is the native event you created in Step 0 of "Creating the Native Event, Translation, and Application Event for the Human Resources Application".

7. Enter HR Placing New Ad in the Role Naming Convention field as the naming convention to use for inbound roles.

8. Select Write File - %TIME%(xmlRecord) - Outbound from the Outbound Interaction list (for the outbound ad request received by the Global Newspaper application). This interaction is available for selection because you:

   • Added Write File(FileRecord) as the outbound interaction in Step 7 of "Creating the Outbound Interaction for the Global Newspaper Application Adapter".

   • Entered %TIME% as the file naming convention for the outgoing file in Step 8.

9. Select Global NP Ad from the Native Event list. This is the native event you created in Step 0 of "Creating the Native Event, Translation, and Application Event for the Global Newspaper Application".

10. Enter Placing Ad at Global NP in the Role Naming Convention field as the naming convention to use for outbound roles.

11. Click Next.

12. Review your selections on the Review page. This page displays two tables:

    • The upper table, called the Initiating Spoke, shows the roles and events from the Read File - inbound (xmlRecord) - Inbound interaction up through the business process. This is the modeling metadata to be created for the inbound ad request and enables the ad request to be read from the inbound directory of the Human Resources application.

    • The lower table, called the Invoked Spoke, shows the roles and events from the Write File - %TIME%(xmlRecord) - Outbound interaction up through the business process. This is the modeling metadata that enables the ad request to be written to the outbound directory.

    The following messages appear to remind you of tasks to perform after running the modeling wizards.

    • Beneath both transformation steps:

      You will need to populate the rules for this transformation map.
      
      

    • Beneath both SetParty steps:

      You will need to select a party for this SetParty step.
      
      

    • Beneath both business events:

      You will need to define the elements for this business event.
      
      

Description of the illustration tut_rev.gif

13. Click Finish.

    The Event Flow Diagram displays after the modeling wizard has completed. This diagram shows the events moving through the various roles of your integration. (See the following portion of the event flow diagram.) The Event Flow Diagram displays after the modeling wizard has completed. This diagram shows the events moving through the various roles of your integration.

Description of the illustration tut_event_flow.gif

14. Click Integration Diagram at the bottom of the Event Flow Diagram to see all the newly created roles and the business process for which you provided names.

Description of the illustration tut_int_diag.gif

Note that the word Agreement displays in two places. The one on the left is for the Human Resources application and the one on the right is for the Global Newspaper application. After you create agreements for both the Human Resources and Global Newspaper applications (described later in this tutorial), an icon appears beneath each. When you click one of these icons, the details page appears for that application agreement.

7.3.2.8 Creating the Business Event Datatypes

The different datatypes of the Human Resources and Global Newspaper applications that you created earlier must be represented as a single, common set of business datatypes to communicate with Oracle Application Server ProcessConnect and participate in integrations. You can manually create business datatypes or import XSD native formats of datatypes into Oracle Application Server ProcessConnect. In this section of the tutorial, you import these datatypes. As an alternative, you can also manually create datatypes by following the instructions in "Manually Creating the Business Datatypes".

You later add these datatypes to the event body element that you create in "Creating the Business Event Body Element".

1. Select the Modeling tab.

2. Select Datatypes.

3. Click Import in the Business Datatypes page.

4. Select Ad_CommonView.xsd on the Select XSD File page.

5. Review details about the XSD when prompted on the Translator Properties page.

6. Select None from the Namespace for Business Datatypes to be Created list.

7. Click Apply.

   The Business Datatypes page appears.

8. Select name from the Search list.

9. Enter Ad_Request in the field to the right.

10. Click Go.

    The Ad_Request business datatype appears in the Name column.

11. Click Ad_Request.

12. Click Expand All in the Datatype Members section to view the business datatypes.

Description of the illustration tut_bdt.gif

7.3.2.9 Creating the Business Event Body Element

The modeling wizard you ran in "Creating the Modeling Metadata with the Modeling Wizards" created a business event with no event body element. The business event establishes a common event structure and event vocabulary across the Human Resources and Global Newspaper applications. Business events are completely removed from any Human Resources or Global Newspaper application-specific properties, including data structure and vocabulary. All related events from both applications follow the same structure and the same vocabulary once they are translated and transformed into business events.

The event body element of the business event must contain a complete set of business data (for this tutorial, the business event datatypes created in "Creating the Business Event Datatypes"). You must create an event body element inside this business event that contains the business event datatypes created in "Creating the Business Event Datatypes".

1. Select the Modeling tab.

2. Select Event Types.

3. Select HR_New_Ad from the Name column of the Business Event Types page. This is the business event automatically created with the modeling wizard in "Creating the Modeling Metadata with the Modeling Wizards".

4. Click Update.

5. Rename the event type to Ad Request. This gives the event type a more meaningful name.

6. Click Apply.

7. Click Create in the Event Body Elements section.

8. Enter Ad in the Name field.

9. Select Business Datatype from the Classification list.

10. Select Unspecified from the Namespace list.

11. Click the flashlight next to the Name field.

    
    

    Note: To quickly search a long list of datatypes, enter Ad% in the Search field and click Go.

    
    

12. Select Ad Request and click Select. These are the business datatypes you imported in "Creating the Business Event Datatypes".

    Your selection appears in the Name field.

13. Click Apply.

    The Ad event body element is created and the datatypes imported in "Creating the Business Event Datatypes" are added to this Ad event body element.

14. Click Return to Event Type Details page.

15. Click Expand All in the Event Body Elements section to view the event body element and its datatypes.

Description of the illustration tut_bet2.gif

Both the incoming business role and outgoing business role contain this single, common business event and event body element of business datatypes. You use these business datatypes later in this tutorial to create the following transformation rules:

• Transform an inbound application event into an inbound business event in "Creating the Rules for the Inbound Event Transformation Map".

• Transform an outbound business event into an outbound application event in "Creating the Rules for the Outbound Event Transformation Map".

At this point, the Human Resources and Global Newspaper applications include their own native events, translators, application events, business events, and event body elements of datatypes.

7.3.2.10 Creating the Rules for the Inbound Event Transformation Map

The Human Resources and Global Newspaper applications use different vocabulary in their messages. This creates a vocabulary mismatch. Transformation enables you to standardize on the vocabulary used by both applications in an integration and establish a common structure and vocabulary. To establish this common vocabulary, you must create transformation rules. Transformation rules describe how to transform one data item to another (in this section, from the Human Resources application’s inbound source application event and its application datatypes to an inbound target business event and its business datatypes).

When you ran the modeling wizard in "Creating the Modeling Metadata with the Modeling Wizards", an inbound event transformation map was created with no defined rules. In this section, you define the transformation rules so that a common vocabulary can be established. First, you rename the event transformation map to a more meaningful name.

1. Select the Modeling tab.

2. Select Transformations.

3. Click Update for the first Transform HR New Ad in the Name column. This is the map with an application event type in the Source Parameter Types column and a business event type in the Target Parameter Types column.

4. Rename the map to HR Ad to Common View.

5. Click Apply.

6. Go to the Sources and Targets section.

7. Click Expand All for both the Sources table and the Targets table. The mapping you perform in this section is very simple and intended for testing purposes.

8. Select the Ad_ID integer in the Sources table. The application datatypes that appear in the Sources table are the same datatypes you created in "Creating the Native Event, Translation, and Application Event for the Human Resources Application". (View these application datatypes under Step 16.)

9. Select the Ad_ID integer in the Targets table. The business datatypes in the Targets table are the same datatypes you imported in Step 3 of "Creating the Business Event Datatypes" and included in the business event body element in Step 12 of "Creating the Business Event Body Element". (View these business datatypes under Step 15.)

10. Select copy:from=integer->to=integer from the Datatype Transformation Map list.

    The Transformation Map Details page appears as follows with the selections you made in Steps 8 through 9.

Description of the illustration tut_transf_in.gif

11. Click Append.

    This maps the vocabulary of the source inbound application event to the vocabulary of the target inbound business event. The rule you created displays in the Statements section of this page.

Description of the illustration tut_st1.gif

See Also: "Transformation Statements Overview" for additional examples of event transformation mapping

7.3.2.11 Creating the Rules for the Outbound Event Transformation Map

When you ran the modeling wizard in "Creating the Modeling Metadata with the Modeling Wizards", an outbound event transformation map was also created with no defined rules. In this section, you create transformation rules for the Global Newspaper application’s outbound source business event and its business datatypes to the outbound target application event and its application datatypes.

1. Select the Modeling tab.

2. Select the Transformations tab.

3. Click Update for the remaining map named Transform HR Ad in the Name column. This is the map with a business event type in the Source Parameter Types column and an application event type in the Target Parameter Types column.

4. Rename the map to Common View to Global NP Ad.

5. Click Apply.

6. Click Expand All for both the Sources table and the Targets table.

7. Select the Ad_ID integer in the Sources table. The business datatypes in the Sources table are the same datatypes you imported in Step 3 of "Creating the Business Event Datatypes" and included in the business event body element in Step 12 of "Creating the Business Event Body Element". (View these business datatypes under Step 15.)

8. Select the Ad_ID integer in the Targets table. The application datatypes in the Targets table are the same datatypes you created in "Creating the Native Event, Translation, and Application Event for the Global Newspaper Application". (View these application datatypes at Step 17.)

9. Select copy:from=integer->to=integer from the Datatype Transformation Map list.

10. Click Append.

    This maps the vocabulary of the outbound source business event to the vocabulary of the outbound target application event. The rule you created displays in the Statements section of this page.

Description of the illustration tut_st2.gif

11. Select copy:from=string->to=string from the Datatype Transformation Map list.

12. Click Append. This takes you to the Advanced Transformation Rules page.

13. Click Expand All for the Targets table.

14. Select copy:from=string->to=string from the Datatype Transformation Map list.

15. Select the Action string in the Targets table.

16. Click Bind Target.

17. Enter Global NP Ad in the Constant Value field.

18. Click Bind Source.

19. Click Apply.

7.3.2.12 Selecting the Destination Party in the SetParty Step

Events are sent to and from the Human Resources and Global Newspaper applications. To ensure that events are sent through the correct roles and arrive at the correct party address, you must update the destination party (in this tutorial, the Global Newspaper application) inside the SetParty step. The modeling wizard automatically created a SetParty step in the business process in "Creating the Modeling Metadata with the Modeling Wizards".

1. Select the Modeling tab.

2. Select the Business Processes tab.

3. Select the process diagram in the Process Diagram column for the Placing Ad business process.

4. Select Update (Step or Port) from the Action list.

5. Select SetParty for HR New Ad in the Process Diagram.

6. Rename to Deliver Ad to Global NP.

7. Select Global Newspaper from the Party list.

8. Click Apply.

7.3.3 Task 3: Creating the Agreements

This section contains the following tasks:

• Creating the Human Resources Application Agreement

• Adding the Delivery Channel for the Human Resources Application Adapter

• Adding the Human Resources Application Native Role to the Agreement

• Validating the Human Resources Application Agreement

• Sending the Agreement for Approval

• Creating the Global Newspaper Application Agreement

• Adding the Delivery Channel for the Global Newspaper Application Adapter

• Adding the Global Newspaper Application Native Role to the Agreement

• Validating the Global Newspaper Application Agreement

• Sending the Agreement for Approval

  
  

  See Also: Chapter 15, " Managing Applications and Application Agreements" for additional details about creating application agreements, adding delivery channels and native roles to application agreements, validating application agreements, and sending agreements for approval

  
  

7.3.3.1 Creating the Human Resources Application Agreement

To participate in an integration, electronic agreements for the Human Resource and Global Newspaper applications must be created. Create one agreement for each application. You also select a native role and delivery channel to use in each agreement. Approvers representing both the Human Resources and Global Newspaper applications must review the contents of these agreements and approve them before they can be deployed in an integration.

Create the application agreement for the Human Resources application.

1. Select the Profiles tab.

2. Select the Agreements tab.

3. Click Create in the Application Agreements page.

4. Enter the following information:

   In this Field...	Enter/Select
   Name	HR Agreement
   Agreement Id	1
   Effective From Date	Leave this field blank
   Effective To Date	Leave this field blank
   Application Participant	Human Resources

   
   

5. Click Apply.

7.3.3.2 Adding the Delivery Channel for the Human Resources Application Adapter

Add the delivery channel that describes the communication capabilities (such as message exchange and security details) of the adapter for the Human Resources application. You created this delivery channel in "Creating the Delivery Channel for the Human Resources Application Adapter".

1. Click Add in the Delivery Channels Used section of the Application Participant Details: Human Resources Agreement page

2. Select HR DC from the Delivery Channel list.

3. Click Apply.

7.3.3.3 Adding the Human Resources Application Native Role to the Agreement

Add the native role of the Human Resources application to the agreement. The native role implements the behavior of the Human Resources application agreement. You created this native role with the modeling wizard in Step 7 of "Creating the Modeling Metadata with the Modeling Wizards".

1. Click Add in the Native Roles section of the Agreement Details: Human Resources Agreement page.

2. Select HR Placing New Ad-NR from the Native Role list.

3. Click Apply.

7.3.3.4 Validating the Human Resources Application Agreement

1. Click Validate on the Agreement Details: Human Resources Agreement page.

   If validation is successful, the Validate button is replaced with a Send For Approval button and the Draft status that displays in the State field of the Details section is replaced with Validated.

7.3.3.5 Sending the Agreement for Approval

The agreement can be approved by specific persons before it can be deployed in an integration. Approval typically involves assigning these persons as approvers in the Oracle Application Server ProcessConnect user interface tool and exporting the contents of the agreement to an XML file for submittal to these approvers for review. For this tutorial, you do not perform Steps 5 and 6 in this section, during which the XML file is submitted for approval.

1. Click Send for Approval.

2. Select approvers (for example, the user admin) from the Available Approvers list.

3. Click Move to move the approver(s) to the Selected Approvers list.

4. Click Send for Approval.

   Your selection appears in the Approvers section of the Application Details: Human Resources page. The Send For Approval button is replaced with an Approve button and the Validated status that displays in the State field of the Details section is replaced with Pending Approval.

5. Click Export to export the agreement to an XML file for submittal to a person for approval.

6. Submit the file to the approvers(s) you selected in Step 5 for approval.

7. Click Approve. Typically, you perform this task after your approvers notify you that they are satisfied with the agreement. For this tutorial, you do not wait for an approver.

8. Click Approve again when prompted to confirm.

7.3.3.6 Creating the Global Newspaper Application Agreement

Create the application agreement for the Global Newspaper application.

1. Select the Profiles tab.

2. Select the Agreements tab.

3. Click Create.

4. Enter the following information:

   In this Field...	Enter...
   Name	Global NP Agreement
   Agreement Id	2
   Effective From Date	Leave this field blank
   Effective To Date	Leave this field blank
   Application Participant	Global Newspaper

   
   

5. Click Apply.

7.3.3.7 Adding the Delivery Channel for the Global Newspaper Application Adapter

Add the delivery channel that describes the communication capabilities (such as message exchange and security details) of the adapter for the Global Newspaper application. You created this delivery channel in "Creating the Delivery Channel for the Global Newspaper Application Adapter".

1. Click Add in the Delivery Channels Used section of the Application Participant Details: Global Newspaper Agreement page

2. Select Global NP DC from the Delivery Channel list.

3. Click Apply.

7.3.3.8 Adding the Global Newspaper Application Native Role to the Agreement

Add the native role of the Global Newspaper application to the agreement. You created this native role with the modeling wizard in Step 10 of "Creating the Modeling Metadata with the Modeling Wizards".

1. Click Add in the Native Roles section of the Agreement Details: Global Newspaper Agreement page.

2. Select Placing Ad at Global NP-NR from the Native Role list.

3. Click Apply.

7.3.3.9 Validating the Global Newspaper Application Agreement

1. Click Validate on the Agreement Details: Global Newspaper Agreement page.

   If validation is successful, the Validate button is replaced with a Send For Approval button and the Draft status that displays in the State field of the Details section is replaced with Validated.

7.3.3.10 Sending the Agreement for Approval

You can select an approver to approve the profile data of your agreement. For this tutorial, you do not perform Steps 5 and 6 in this section, during which the XML file is submitted for approval.

1. Click Send for Approval.

2. Select approvers (for example, the user admin) from the Available Approvers list.

3. Click Move to move the approver(s) to the Selected Approvers list.

4. Click Send for Approval.

   Your selection appears in the Approvers section of the Application Details: Global Newspaper page. The Send For Approval button is replaced with an Approve button and the Validated status that displays in the State field of the Details section is replaced with Pending Approval.

5. Click Export to export the agreement to an XML file for submittal to a person for approval.

6. Submit the file to the approvers(s) you selected in Step 5 for approval.

7. Click Approve. Typically, you perform this task after your approvers notify you that they are satisfied with the agreement. For this tutorial, you do not wait for an approver.

8. Click Approve again when prompted to confirm.

9. Click the Modeling tab.

10. Click the Business Processes tab.

11. Click the Integration Diagram for the Placing Ad business process.

    Note that both agreements now display as icons in the Integration Diagram. You can click either agreement to display the agreement details page for that application.

Description of the illustration tut_int2.gif

7.3.4 Task 4: Creating and Deploying a Configuration

You are now ready to deploy your integration between the Human Resources and Global Newspaper applications. Deployment first involves creating a feature known as a configuration that includes the integration you designed in this tutorial. This configuration is then validated to ensure that your integration is correct and consistent. If validation is successful, the configuration is created. You can then deploy the configuration from the design-time repository to the runtime repository. If validation is unsuccessful, error messages appear that describe what must be corrected.

1. Select the Deployment tab.

2. Click Create.

3. Enter Placing Ad Phase A as the configuration name.

4. Click Apply. If validation is successful, the configuration is created and the following message appears:

   Creation and validation of configuration Placing Ad successful
   
   

   The Deploy button is now enabled.

   If validation is not successful, correct the errors and click Return To Deployment to retry configuration creation.

5. Click Deploy.

6. Select High from the BI Reporting Level list.

   The business intelligence (BI) level indicates how much the deployment tries to optimize the runtime configuration for performance. Low BI provides the fastest possible performance, but does not log complete information during runtime. This impacts the reports you can later create. High BI provides the most details for reports and troubleshooting.

7. Click Apply.

   If deployment is successful, the configuration is deployed from the design-time repository to the runtime repository and the following message appears:

   Deployment finished successfully for configuration Placing Ad Phase A
   

   
   

   See Also: The following sections for additional details about tasks covered in this section: "Creating a Configuration" "Deploying a Configuration"

   
   

7.3.5 Task 5: Testing the Results

It is now time to test the results of the integration.

1. Ensure that the integration manager and adapter framework components are running. Both are automatically started after installation. If you are unsure, see Chapter 18, " System Management with Oracle Enterprise Manager 10g" for instructions on viewing component status and, if necessary, starting these components from Oracle Enterprise Manager 10g.

2. Copy the HR_Ad.xml file to the /start_at_root/ip/tutorial/human_resources/inbound directory. Note that this directory is a combination of the answers you provided to the Human Resources application delivery channel and interaction questions earlier in this tutorial.

   This directory is polled by the File/FTP adapter every 10 seconds, as you specified in Step 2. The file is read and deleted from the directory, but only when the native event instance is successfully created. The result file %TIME%.xml is found in the /start_at_root/ip/tutorial/global_newspaper/outbound directory. Note that this directory is a combination of the answers you provided to the Global Newspaper application delivery channel and interaction questions earlier in this tutorial.

7.3.6 Task 6: Troubleshooting Any Errors with Log Files and Reports

If the HR_Ad.xml file is not deleted, perform the following troubleshooting tasks:

• Stop and restart the adapter framework.

• Check that the directory in the delivery channel for the Human Resources application in combination with the directory for the Read File - inbound(xmlRecord) interaction matches with the directory in which you placed the HR_Ad.xml file. In this tutorial, the directories are as follows:

  For the...	The Directory Is...
  Delivery channel	/private/Oracle/ip/tutorial/human_resources
  Interaction	inbound
  Location in which to place the .xml file	/private/Oracle/ip/tutorial/human_resources/inbound/

  
  

• Check the adapter framework log file and search for AIP (the prefix for error message codes).

If the file is deleted, but no results file appears:

• Wait several seconds and verify that no file can be found in the expected directory.

• Check that the directory in the delivery channel for the Global Newspaper application in combination with the directory for the Write File - %TIME%(xmlRecord) interaction matches with the directory in which you expect the %TIME%.xml file. In this tutorial, the directories are as follows:

  For the...	The Directory Is...
  Delivery channel	/private/Oracle/ip/tutorial/global_newspaper
  Interaction	outbound
  Location in which the .xml file is written	/private/Oracle/ip/tutorial/global_newspaper/outbound/

  
  

• Create reports

  
  

  See Also: "Oracle Application Server ProcessConnect Monitoring and Administration Tasks" "Creating Reports"

  
  

7.3.6.1 Creating Reports

Create a report to determine if the event is stuck in the integration manager or the adapter framework:

1. Select the Reports tab.

2. Select the Process Monitoring tab.

3. Click Finish.

• If the adapter framework created the native event successfully, there is at least one event. Click the Details button.

• If the event was processed successfully by the integration manager, then there are five events in this list: two native events, two application events, and one business event.

• By clicking on the event, you can follow how the event proceeded through the integration manager. If you went from native event to application event to business event to another application and native event, then all translations and transformations processed successfully.

• You can expand the status of the roles to verify that all the roles and steps have the status completed (you must do this for each event type). The future plan is for coordination reports to show this end-to-end.

  
  

  See Also: The following sections for additional details about tasks covered in this section: "Creating Process Monitoring Reports" "Report Creation Examples"

  
  

7.3.6.2 Checking the Log Files

After installation, the adapter framework and integration manager are automatically started with default logging. To view errors in, for example, translation or transformation, the logging must be set to debug. This can be done in Oracle Enterprise Manager 10g as follows:

1. Select the Oracle Application Server ProcessConnect middle-tier instance.

2. Select the Server Properties link.

3. Change the settings of parameters with oracle.tip.DiagnosticLevel in their name from error to debug. You typically do not need to restart the adapter framework and integration manger (but do it anyhow).

4. Check the integration manager log file and search for AIP.

5. Check the adapter framework log file and search for AIP.

   
   

   See Also: "Managing and Monitoring a Middle-Tier Instance from Oracle Enterprise Manager 10g Application Server Control Console"

   
   

7.3.6.3 More Troubleshooting Tips

Verify that all agreements and applications are approved. You do this by looking at the details of each application and agreement and verifying that none of the following buttons are present:

• Validate

• Send for Approval

• Approve

If any of these buttons are present, click it and follow the steps in "Task 3: Creating the Agreements" to approve the application or agreement.

Verify that all agreements have a native role defined. Do this by looking at the details of each agreement and verifying that the correct native role is listed for that particular agreement.

If you created the business datatypes by hand, verify that you did not use the space (" ") character. To view the business datatypes of your configuration, select each business event and click Expand All in the Event Body Elements section.

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.

See Also: "Updating the Interaction, Native Event, and Application Event" if you must update an application event with a different XSD

7.4 Phase B1: Manually Design Some Modeling Metadata in an Integration

You can also manually model portions of an integration. Up to this point, the tutorial has only used the wizard to generate the metadata for data flow and control flow. Data flows connect step ports and role ports of native, application, and business roles. Control flows between steps indicate the execution order of steps. Control flows connect directly to steps and do not use step ports.

The Create End-to-End Basic Integration wizard generated all the roles, the business process, the ports, the data flows, the control flows, the event types (without the body elements), and the transformation maps (without the rules). In this task, you enhance the existing business process by adding a conditional step and a transformation step. The scenario is as follows: a confirmation comes back from a newspaper. If the confirmation is positive, the business process can finish. If there is an error, human resources must be notified. The transformation step is chosen here simply to show that transformations can also be used in the business process and not only in transformation binding roles. All of the following phases must be completed before a new configuration can be created, deployed, and tested.

This section contains these topics:

• Task 1: Creating the Business Event Types and Body Elements

• Task 2: Creating a Conditional Step

• Task 3: Creating a Transformation Step to Notify Human Resources

• Task 4: Creating an Or Step

• Task 5: Creating a Role Port and Data Flow to Deliver the Ad Problem Event to Human Resources

• Task 6: Creating a Split Step

• Task 7: Creating a Role Port and Data Flow to Splitting the Ad Confirmation Event

• Task 8: Removing Unnecessary Control Flow (Optional)

  
  

  See Also: The following sections for additional details about tasks covered in this section: "Managing Business Event Types" "Managing Steps" "Managing Role Ports" "Managing Role Data Flow"

  
  

7.4.1 Task 1: Creating the Business Event Types and Body Elements

Before beginning, it is helpful to create the business event(s) you want to model in the business process. It is possible to model the data flows in the business process without the business events, but it becomes harder to read because no event names can be displayed. The business event(s) can be created without any body element and thus without importing or creating any datatypes at this time.

7.4.1.1 Importing the Business Event Datatypes from an XSD File

You use the same XSD file in this example to define the business datatypes for the business event body element as you use to define the application datatypes.

1. Select the Modeling tab.

2. Select Datatypes.

3. Click Import on the Business Datatypes page.

4. Select Global_NP_AdConfirmation.xsd on the Select XSD File page.

5. Click Apply.

7.4.1.2 Creating the Ad Confirmation Business Event

1. Select the Modeling tab.

2. Select Event Types.

3. Click Create on the Business Events page.

4. Enter Ad Confirmation in the Name field.

5. Click Apply.

7.4.1.3 Creating a Body Element for the Ad Confirmation Business Event

1. Click Create in the Event Body Elements section.

2. Enter Confirmation in the Name field.

3. Select Business Datatypes from the Classification list.

4. Select http://www.oracle.com/global_newspaper from the Namespace list.

5. Click the flashlight next to the Name field.

6. Select Confirmation and click Select.

7. Click Apply.

   This creates the body element and its datatypes for the Ad Confirmation business event. This business event is sent if the ad request placement is successful.

7.4.1.4 Importing the Business Event Datatypes from an XSD File

1. Select the Modeling tab.

2. Select Datatypes.

3. Click Import on the Business Datatypes page.

4. Select HR_AdProblem.xsd.

5. Click Apply.

7.4.1.5 Creating the Business Event Ad Problem

1. Select the Modeling tab.

2. Select Event Types.

3. Click Create on the Business Event Types page.

4. Enter Ad Problem in the Name field.

5. Click Apply.

7.4.1.6 Creating a Body Element for the Ad Problem Business Event

1. Click Create in the Event Body Elements section.

2. Enter Problem in the Name field.

3. Select Business Datatype from the Classification list.

4. Select http://www.oracle.com/human_resources from the Namespace list.

5. Click the flashlight next to the Name field.

6. Select Problem and click Select.

7. Click Apply.

   This creates the body element and its datatypes for the Ad Problem business event. This business event is sent if there is a problem with the ad request placement.

7.4.2 Task 2: Creating a Conditional Step

In this tutorial, you notify human resources only if there is a problem with the ad placement. If there is no problem, human resources assumes that everything is well. To satisfy these two conditions, you must insert a condition step. A condition step evaluates a specific condition on an event type or datatype. This step is associated with a condition expression. After the condition expression is evaluated, one of the outgoing control flows (either true or false) is executed. In this tutorial, the condition step checks the confirmation event from the newspaper and either ends the process (if placement is successful) or notifies human resources (if a problem occurs).

7.4.2.1 Creating a Condition Expression

Condition expressions enable you to define that a specific action be performed in a condition step based on the result of an expression. The conditional expression can either be created after the step is modeled or before as preparation for later use. In this tutorial, you create the expression now so that it is available for selection when you create the conditional step.

1. Select the Modeling tab.

2. Select Conditional Expressions.

3. Click Create.

4. Enter Ad Placement Confirmed? in the Name field.

5. Click Apply.

6. Click Create in the Condition Parameters section.

7. Enter Ad Confirmation in the Name field.

8. Select Event Type from the Type list. The page refreshes.

9. Select Business Event Type from the Classification list.

10. Click the flashlight next to the Name field.

11. Select Ad Confirmation and click Select.

12. Click Apply.

13. Click Return to List.

14. Click Create to the right of Expression in the Details section.

15. Click Update for Condition expression not specified.

16. Click Expand All for the Left Operand field.

17. Select Confirmed.

18. Select = from the Operator list. The page refreshes.

19. Enter yes in the Constant field.

20. Click Apply.

21. Click Apply on the Create Condition page.

7.4.2.2 Creating the Condition Step Using the Condition Expression

1. Select the Modeling tab.

2. Select Business Processes.

3. Click Process Diagram for the Placing Ad business process.

4. Select Create Step from the Action list.

5. Click the Deliver Ad to Global NP step.

6. Enter Ad Placement Confirmed? in the Name field.

7. Select Condition Step from the Type field. The page refreshes.

8. Select Ad Placement Confirmed? from the Condition Expression list.

9. Select Deliver Ad to Global NP from the Step list of the Sequence after section. This places the Ad Placement Confirmed? step after the Deliver Ad to Global NP step.

10. Select End from the Step list of the first Sequence before section. This places the Ad Placement Confirmed? step before the End step.

11. Select False from the Guard Value list of the first Sequence before section. A guard value specifies the next step to execute based on the outcome of the condition expression (either true or false) in the condition step.

12. Select End from the Step list of the second Sequence before section.

13. Select True from the Guard Value list of the second Sequence before section.

14. Click Apply.

15. View the process diagram by clicking Modeling > Business Processes > Process Diagram (for the Placing Ad business process). After the condition expression is evaluated, one of the outgoing control flows (either true or false) you specified is executed.

7.4.3 Task 3: Creating a Transformation Step to Notify Human Resources

This task creates the notification event for human resources in case there is a problem. Again, the transformation step is used mainly to demonstrate that transformation steps can be used in the business process to generate new event types (that is, not only in the transformation binding roles). As an alternative, you can also use a pass-through step and perform the transformation in one of the transformation steps in the roles.

7.4.3.1 Creating an Event Transformation Map

As with the conditional step, the event transformation map can either be created before creating the step in the business process or at a later time. In this tutorial, you create the map first, because you must define it in the step.

1. Select the Modeling tab.

2. Select Transformations.

3. Click Create in the Event Transformation Maps page.

4. Enter Ad Confirmation to Ad Problem in the Name field.

5. Click Specify Source and Target. The page refreshes.

6. Enter Ad Confirmation in the Name field of the Source section.

7. Select Event Type from the Type list of the Source section. The page refreshes.

8. Select Business Event Type from the Classification list of the Source section.

9. Click the flashlight next to the Name field of the Source section.

10. Select Ad Confirmation and click Select.

11. Enter Ad Problem in the Name field of the Target section.

12. Select Event Type from the Type list of the Target section. The page refreshes.

13. Select Business Event Type from the Classification list of the Target section.

14. Click the flashlight next to the Name field.

15. Select Ad Problem and click Select.

16. Click Apply.

17. Click Expand All for both the Sources table and the Targets table.

7.4.3.2 Copying the Ad_ID Integer

1. Select Ad_ID in the Sources table.

2. Select Ad_ID in the Targets table.

3. Select copy:from=integer->to=integer from the Datatype Transformation Map list.

4. Click Append.

   The rule is added to the Statements section.

7.4.3.3 Copying the Problem_Details String

1. Select Problem_Details in the Sources table.

2. Select Problem_Description in the Targets table.

3. Select copy:from=string->to=string from the Datatype Transformation Map list.

4. Click Append.

   The rule is added to the Statements section.

7.4.3.4 Creating a Transformation Step Using the Transformation Map

1. Select the Modeling tab.

2. Select Business Processes.

3. Click the Process Diagram for the Placing Ad business process.

4. Select Create Step from the Action list.

5. Click the Ad Placement Confirmed? step.

6. Enter Notify HR Person in the Name field.

7. Select Transformation Step from the Type field. The page refreshes.

8. Select Ad Confirmation to Ad Problem(Ad Confirmation->Ad Problem) from the Transformation Map list. This is the transformation map to associate with this transformation step.

9. Select Ad Placement Confirmed? from the Step list of the Sequence after section. This places the Notify HR Person step after the Ad Placement Confirmed? step.

10. Select End from the Step list of the Sequence before section. This places the Notify HR Person step before the End step.

11. Click Apply.

12. View the process diagram by clicking Modeling > Business Processes > Process Diagram (for the Placing Ad business process).

7.4.4 Task 4: Creating an Or Step

Each step is executed when all control flows and data flows reach it. In this example, the End step is only executed when both control flows reach it. Since this is not the behavior you want, you must create an Or step. An Or step waits for at least one incoming control flow. The step is executed as soon as one of the incoming control flows is executed.

1. Select Create Step from the Action list.

2. Click the Notify HR Person step.

3. Enter OR in the Name field.

4. Select Or Step from the Type field. The page refreshes.

5. Select Notify HR Person from the Step list of the first Sequence after section. This places the OR step after the Notify HR Person step.

6. Select Ad Placement Confirmed? from the Step list of the second Sequence after section. This places the OR step after the Ad Placement Confirmed? step.

7. Select End from the Step list of the first Sequence before section. This places the OR step before the End step.

8. Click Apply.

9. View the process diagram for the Placing Ad business process to see your changes.

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

7.4.5 Task 5: Creating a Role Port and Data Flow to Deliver the Ad Problem Event to Human Resources

The Ad Problem business event must be delivered from the Notify HR Person transformation step out of the business process. To do this, a role port must be created. Role ports define the interfaces for a business process (or role), allowing for re-use.

1. Select Create Role Port from the Action list.

2. Click anywhere on the diagram.

3. Enter Ad Problem Out in the Name field.

4. Select Output from the Direction list.

5. Select Business Event Type from the Classification list.

6. Click the flashlight next to the Name field.

7. Select Ad Problem and click Select.

8. Click Apply.

9. Select Create Data Flow from the Action list.

10. Select the role port (this is the single red dot on the boundary of the business process).

11. Click Apply. There is only one available data port already preselected in the list: the output port on the Notify HR Person transformation step.

12. View the process diagram for the Placing Ad business process to see your changes.

7.4.6 Task 6: Creating a Split Step

Two of the steps you created require the same business event. The Ad Placement Confirmed? conditional step and the Notify HR Person transformation step each require the Ad Confirmation business event. The way to model both steps that require the same event type is to use a split step. A split step makes multiple copies of the same event type and passes them to each step with which it is linked.

1. Select Create Step from the Action list.

2. Click the Deliver Ad to Global NP step.

3. Enter SPLIT in the Name field.

4. Select Split Step from the Type list. The page refreshes.

5. Select Deliver Ad to Global NP from the Step list of the Sequence after section. This places the SPLIT step after the Deliver Ad to Global NP step.

6. Select Ad Placement Confirmed? from the Step list of the Sequence before section. This places the SPLIT step before the Ad Placement Confirmed? step.

7. Click Apply.

8. View the process diagram for the Placing Ad business process to see your changes.

7.4.7 Task 7: Creating a Role Port and Data Flow to Splitting the Ad Confirmation Event

1. Select Create Role Port from the Action list.

2. Click anywhere on the diagram.

3. Enter Ad Confirmation In in the Name field.

4. Select Input from the Direction list.

5. Select Business Event Type from the Classification list.

6. Click the flashlight next to the Name field.

7. Select Ad Confirmation and click Select.

8. Click Apply.

9. Select Create Data Flow from the Action list.

10. Select the role port (this is the single role port on the edge of the role).

11. Click Apply. There is only one available data port already preselected in the list: the output port on the Notify HR Person transformation step.

12. Select Input1.

13. Click Apply.

14. Select Create Data Flow from the Action list.

15. Click one of the two step ports without data flow on the SPLIT step.

16. Select Ad Confirmation-In (the Port Owner is Ad Placement Confirmed?).

17. Click Apply.

18. Select Create Data Flow from the Action list.

19. Click the step port without data flow on the SPLIT step.

20. Select Ad Confirmation-In (the Port Owner is Notify HR Person).

21. Click Apply.

22. View the process diagram for the Placing Ad business process to see your changes.

7.4.8 Task 8: Removing Unnecessary Control Flow (Optional)

When there is a data flow between two steps, the control flow is implicit. This makes the control flow between the SPLIT step and the Ad Placement Confirmed? step redundant.

1. Click the SPLIT step.

2. Delete the Ad Placement Confirmed? control flow.

3. Click Yes.

4. View the process diagram for the Placing Ad business process to see your final changes.

7.5 Phase B2: Using the Add Event Flow Wizard

This section describes how to use the Add Event Flow wizard to add an additional event flow to one of the existing spokes you initially created with the End-to-End Basic Integration wizard in "Task 2: Creating the Modeling Metadata". An event flow is the complete path a single event takes through a spoke. A 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.

This section contains these topics:

• Task 1: Creating a Native Event for an Existing Interaction

• Task 2: Creating an Event Map for the Global NP Confirmation Native Event

• Task 3: Creating an Event Correlation

• Task 4: Adding an Event Flow to a Spoke with the Add Event Flow Wizard

• Task 5: Creating Transformation Statements

  
  

  See Also: The following sections for additional details about tasks covered in this section: "Adding Event Flow to a Single Spoke" "Managing Native Event Types" "Managing Event Maps" "Managing Native Event Correlations" "Transformation Statements Overview"

  
  

7.5.1 Task 1: Creating a Native Event for an Existing Interaction

This task creates the third native event for the integration scenario. The global newspaper delivers a confirmation to Oracle Application Server ProcessConnect. The confirmation tells whether or not the ad is placed.

1. Select the Modeling tab.

2. Select Event Types.

3. Select Native Event Types.

4. Click Create.

5. Enter Global NP Confirmation in the Name field.

6. Select Read File - inbound(xmlRecord - Inbound) from the Interaction list.

7. Select xmlRecord from the Record Type list.

8. Click Next.

9. Select XSD from the Translator list.

10. Select Create New.

11. Enter Global NP Confirmation in the Name field.

12. Click Browse next to the Content field.

13. Select Global_NP_AdConfirmation.xsd.

14. Click Next.

15. Select XSD from the Translator list.

16. Select Yes from the Preserve Namespaces for Native instances list.

17. Select None from the Doctype for Native Instances list.

18. Click Next.

19. Click Finish.

7.5.2 Task 2: Creating an Event Map for the Global NP Confirmation Native Event

The native event you created is the second one to use the Read File - inbound(xmlRecord - Inbound) interaction (HR New Ad was the first one). Therefore, you must specify a condition expression to determine which native event to create for the different records passed.

1. Select the Modeling tab.

2. Select Event Types.

3. Select Native Event Types.

4. Select Global NP Confirmation from the Name column.

5. Click Create in the Event Map section.

6. Click Update for Condition expression not specified.

7. Click Expand All for the Left Operand field.

8. Select Action.

9. Select = from the Operator list.

10. Enter Global NP Ad Confirmation in the Constant Value field.

11. Click Apply.

12. Click Apply on the Create Event Map page.

7.5.3 Task 3: Creating an Event Correlation

When the global newspaper confirmations are received back from the newspaper, each one must be correlated to the correct ad placement request for which it is a confirmation. Events are correlated either on the presence of a certain datatype or on the content of a datatype. In this case, you correlate the confirmation to the ad based on the Ad_ID datatype.

1. Select the Modeling tab.

2. Select Event Types.

3. Select Native Event Types.

4. Click Create in the Correlations section.

5. Use the flashlight to select Global NP Confirmation from the Correlating Native Event Type list.

6. Click Select.

7. Use the flashlight to select Global NP Ad from the Correlated Native Event Type list.

8. Click Select.

9. Select True from the Directional list.

10. Click Next.

11. Click Update for Condition expression not specified.

12. Click Expand All in the Correlating Native Event Type and Correlated Native Event Type sections.

13. Select Ad_ID in both sections.

14. Select = from the Operator list.

15. Click Apply.

16. Click Apply.

7.5.4 Task 4: Adding an Event Flow to a Spoke with the Add Event Flow Wizard

The Add Event Flow wizard adds an additional event flow to a single, existing spoke. In this case, you add the event flow to the spoke extending from the Placing Ad at Global NP-NR native role to the Placing Ad business process. This is one of the two spokes you initially created with the End-to-End Basic Integration wizard in "Creating the Modeling Metadata with the Modeling Wizards".

1. Select the Modeling tab.

2. Select Business Processes.

3. Click Add Event Flow in the Shortcuts section.

4. Select Placing Ad from the Business Process list.

5. Select Placing Ad at Global NP-NR from the Native Role list.

6. Select Read File inbound(xmlRecord) - Inbound from the Interaction list.

7. Click Next.

8. Select Global NP Confirmation from the Native Event list.

9. Click Use Existing in the Business Event section.

10. Select Ad Confirmation.

11. Click Next.

12. Click Create New in the Transformation section.

13. Enter Global NP Confirmation to CV.

14. Click Next.

15. Click Finish.

    The Event Flow Diagram appears with the second event flow added to the existing spoke. The following portion of this diagram is shown.

Description of the illustration tut_addeventflow.gif

7.5.5 Task 5: Creating Transformation Statements

1. Select the Modeling tab.

2. Select Transformations.

3. Select Global NP Confirmation to CV from the Name column.

4. Click Expand All for both the Sources table and the Targets table.

7.5.5.1 Copying the Ad_ID Integer

1. Select Ad_ID in the Sources table.

2. Select Ad_ID in the Targets table.

3. Select copy:from=integer->to=integer from the Datatype Transformation Map list.

4. Click Append.

   The statement appears in the Statements section.

7.5.5.2 Copying the Confirmed String

1. Select Confirmed in the Sources table.

2. Select Confirmed in the Targets table.

3. Select copy:from=string->to=string from the Datatype Transformation Map list.

4. Click Append.

   The statement appears in the Statements section.

7.5.5.3 Copying the Problem_Details String

1. Select Problem_Details in the Sources table.

2. Select Problem_Details in the Targets table.

3. Select copy:from=string->to=string from the Datatype Transformation Map list.

4. Click Append.

   The statement appears in the Statements section.

7.6 Phase B3: Using the Add Spoke Wizard

In this phase, you deliver the Ad Problem business event to human resources. You can use the same spoke to model the problem event back to the human resources system. In this tutorial, however, you create a separate spoke (just imagine that you received the request for an ad placement from a human resources application, but want to send the confirmation using e-mail). The spokes are different, because the human resources application behaves differently from the e-mail system. Again, just imagine, because in this tutorial you only use the File/FTP adapter.

• Task 1: Creating a Native Event, Translation, and Application Event

• Task 2: Adding a Spoke

• Task 3: Creating Transformation Statements

  
  

  See Also: The following sections for additional details about tasks covered in this section: "Creating a Single Spoke" "Managing Native Event Types" "Transformation Statements Overview"

  
  

7.6.1 Task 1: Creating a Native Event, Translation, and Application Event

You must also create a native event and specify a translator to translate the outbound application event to an outbound native event.

1. Select the Modeling tab.

2. Select Event Types.

3. Select Native Event Types.

4. Click Create.

5. Enter HR Problem in the Name field.

6. Select Write File %TIME%(xmlRecord) - Outbound from the Interaction list.

7. Select xmlRecord from the Record Type list.

8. Click Next.

9. Select XSD from the Translator list.

10. Select Create New.

11. Enter HR Problem in the Name field.

12. Click Browse next to the Content field.

13. Select HR_AdProblem.xsd.

14. Click Next.

15. Select XSD from the Translator list.

16. Select Yes from the Preserve Namespaces for Native instances list.

17. Select None from the Doctype for Native Instances list.

18. Click Next.

19. Click Finish.

7.6.1.1 Creating an Event Map for the HR Problem Native Event

Because this is the second native event to use the Write File %TIME%(xmlRecord) - Outbound interaction, you must create an event map.

1. Select the Modeling tab.

2. Select Event Types.

3. Select Native Event Types.

4. Select HR Problem.

5. Click Create in the Event Map section.

6. Click Update for Condition expression not specified.

7. Click Expand All for the Left Operand field.

8. Select Action.

9. Select = from the Operator list.

10. Enter HR Problem in the Constant Value field.

11. Click Apply.

12. Click Apply.

7.6.2 Task 2: Adding a Spoke

In this section, you use the Create Spoke wizard to add a spoke to the existing set of roles, business process, transformation maps, and business event you initially created with the End-to-End Basic Integration wizard in "Creating the Modeling Metadata with the Modeling Wizards".

1. Select the Modeling tab.

2. Select Business Processes.

3. Click Create Spoke in the Shortcuts section.

4. Click Use Existing.

5. Select Placing Ad in the Business Process section.

6. Click Next.

7. Select Write File - %TIME%(xmlRecord) - Outbound from the Interaction list.

8. Click Next.

9. Enter Delivering E-Mail in the Role Naming Convention field.

10. Click Next.

11. Select HR Problem from the Native Event list.

12. Select Use Existing in the Business Event section.

13. Select Ad Problem.

14. Click Next.

15. Select Create New in the Transformation section.

16. Enter CV to HR Ad Problem.

17. Click Next.

18. Click Finish.

7.6.3 Task 3: Creating Transformation Statements

1. Select the Modeling tab.

2. Select Transformations.

3. Select CV to HR Ad Problem from the Name column.

4. Click Expand All for both the Sources table and the Targets table.

7.6.3.1 Copying the Ad_ID Integer

1. Select Ad_ID in the Sources table.

2. Select Ad_ID in the Targets table.

3. Select copy:from=integer->to=integer from the Datatype Transformation Map list.

4. Click Append.

   The statement appears in the Statements section.

7.6.3.2 Setting a Default for the Action String

1. Select Rule from the Statement Type list.

2. Click Append.

3. Click Expand All for both the Sources table and the Targets table.

4. Select copy:from=string->to=string.

5. Select System Defined from the Datatype Transformation Map Type list.

6. Select Action in the Targets table.

7. Click Bind in the target section.

8. Enter HR Problem in the Constant Value field.

9. Click Bind in the source section.

10. Click Apply.

    The statement appears in the Statements section.

7.6.3.3 Copying the Problem_Description String

1. Select Problem_Description in the Sources table.

2. Select Problem_Description in the Targets table.

3. Select copy:from=string->to=string from the Datatype Transformation Map list.

4. Click Append.

   The statement appears in the Statements section.

7.6.3.4 Setting the Party to HR Person in an Event Header Rule

In "Selecting the Destination Party in the SetParty Step", you selected the destination party with whom to integrate in the SetParty step of the business process. In this task, you specify the destination party through an alternative method. You set the destination party as part of the event transformation map by using the setToParty event header rule.

1. Select Event Header Rule from the Statement Type list.

2. Click Append.

3. Select setToParty from the Event Header Rule list. The page refreshes.

4. Click Expand All for both the Sources table and the Targets table.

5. Select HR Ad Problem-OUT in the Target Event section.

6. Enter HR Person in the Constant Value field.

7. Click Apply.

7.7 Phase B4: Creating the HR Person Application and Agreement

This section describes how to create the HR Person application and agreement.

This section contains these topics:

• Task 1: Creating a Third Application

• Task 2: Creating a Third Application Agreement

• Task 3: Creating and Deploying a New Configuration

• Task 4: Testing the Results

  
  

  See Also: The following sections for additional details about tasks covered in this section: "Creating an Application" "Adding an Adapter to an Application" "Creating an Application Delivery Channel" "Managing Application and Agreement Validation and Approval" "Creating a Configuration" "Deploying a Configuration"

  
  

7.7.1 Task 1: Creating a Third Application

This task creates a third application, also using the File/FTP adapter and using a directory called hr_person.

7.7.1.1 Creating the Application

1. Select the Profiles tab.

2. Select the Applications tab.

3. Click Create.

4. Enter HR Person in the Name field.

5. Select the Generic application type from the Application Type list. The application type enables you to group applications of a similar type together.

6. Click Apply.

7.7.1.2 Adding an Adapter Type

1. Click Add in the Adapter Types section of the Application Details : HR Person page.

2. Select File/FTP Adapter from the Type list.

3. Click Apply.

7.7.1.3 Creating a Delivery Channel

Create a delivery channel for the adapter to use.

1. Click Create in the Delivery Channels section of the Adapter Type Details page of the adapter.

2. Enter the following details:

   Field	Enter/Select
   Name	HR Person DC
   File or FTP mode	File
   Polling interval in milliseconds (inbound)	10000
   Base directory	start_at_root/ip/tutorial/hr_person where start_at_root must be the absolute path (for example, /private/Oracle). Note: Do not use the $ORACLE_HOME variable when specifying a base directory.

   
   

3. Click Apply.

7.7.1.4 Validating the Application

1. Click the Profiles tab.

2. Select Applications.

3. Select HR Person in the Name column.

4. Click Validate.

7.7.1.5 Sending the Application for Approval

1. Click Send for Approval.

2. Select approvers (for example, the user admin) from the Available Approvers list.

3. Click Move to move the approver(s) to the Selected Approvers list.

4. Click Send for Approval.

7.7.1.6 Approving the Application

1. Click Approve.

2. Click Approve again when prompted to confirm.

7.7.2 Task 2: Creating a Third Application Agreement

In this task, you create an application agreement that enables the Human Resource Person application to participate in an integration.

7.7.2.1 Creating the Application Agreement

1. Select the Profiles tab.

2. Select the Agreements tab.

3. Click Create in the Application Agreements page.

4. Enter the following information:

   In this Field...	Enter...
   Name	HR Person Agreement
   Agreement Id	3
   Effective From Date	Leave this field blank
   Effective To Date	Leave this field blank
   Application Participant	HR Person

   
   

5. Click Apply.

7.7.2.2 Adding the Delivery Channel

1. Click Add in the Delivery Channels Used section.

2. Select HR Person DC from the Delivery Channel list.

3. Click Apply.

7.7.2.3 Adding the Native Role

1. Click Add in the Native Roles section.

2. Select Delivering E-Mail-NR from the Native Role list.

3. Click Apply.

7.7.2.4 Validating the Application Agreement

1. Click Validate.

7.7.2.5 Sending the Agreement for Approval

1. Click Send for Approval.

2. Select approvers (for example, the user admin) from the Available Approvers list.

3. Click Move to move the approver(s) to the Selected Approvers list.

4. Click Send for Approval.

7.7.2.6 Approving the Agreement

1. Click Approve.

2. Click Approve again when prompted to confirm.

7.7.3 Task 3: Creating and Deploying a New Configuration

1. Select the Deployment tab.

2. Click Create.

3. Enter Placing Ad Phase B as the configuration name.

4. Click Apply to create a configuration.

5. Click Deploy to deploy the configuration. (This button is only enabled if Step 4 was successful.)

6. Select High from the BI Reporting Level list.

7. Click Apply.

7.7.4 Task 4: Testing the Results

Perform the following steps:

1. Place the HR_Ad.xml file in the /start_at_root/ip/tutorial/human_resources/inbound directory.

2. Verify that the file is read by the adapter and deleted.

3. Confirm the first part of this tutorial is still working by checking that the file ad_%TIME%.xml is in the /start_at_root/ip/tutorial/global_newspaper/outbound directory.

4. Place the file Global_NP_AdConfirmation.xml in the /start_at_root/ip/tutorial/global_newspaper/inbound directory. This directory is polled by the File/FTP adapter every 10 seconds. The file is read and deleted from the directory, but only when the native event is successfully created.

   The ad%TIME%.xml results file is found in the /start_at_root/ip/tutorial/hr_person/outbound directory.

7.8 Manually Creating the Business Datatypes

This section demonstrates how business datatypes can be manually created instead of through import of an XSD file.

This section contains these topics:

• Task 1: Creating the AdType Complex Datatype and its Datatype Members

• Task 2: Creating the Ad_Request Complex Datatype

  
  

  See Also: "Managing Business Datatypes"

  
  

7.8.1 Task 1: Creating the AdType Complex Datatype and its Datatype Members

1. Select the Modeling tab.

2. Select Datatypes.

3. Click Create on the Business Datatypes page.

4. Select Complex from the Type list.

5. Enter AdType in the Name field.

6. Select Unspecified from the Namespace list.

7. Select Sequence Group from the Model Group list.

8. Click Apply.

7.8.1.1 Creating the Complex Datatype Members of AdType

1. Click Create in the Datatype Members section.

2. Select Scalar from the Type list.

3. Enter Title in the Name field.

4. Select No from the Mandatory list.

5. Select Core Datatype from the Classification list.

6. Select Unspecified from the Namespace list.

7. Use the flashlight to select string for the Name field.

8. Click Apply.

9. Click Return to Datatype Details.

10. Click Create in the Datatype Members section.

11. Select Scalar from the Type list.

12. Enter Text in the Name field.

13. Select No from the Mandatory list.

14. Select Core Datatype from the Classification list.

15. Select Unspecified from the Namespace list.

16. Use the flashlight to select string for the Name field.

17. Click Apply.

18. Click Return to Datatype Details.

    The new datatype members for the AdType complex datatype appear.

Description of the illustration tut_dt.gif

7.8.2 Task 2: Creating the Ad_Request Complex Datatype

1. Select the Modeling tab.

2. Select Datatypes.

3. Click Create on the Business Datatypes page.

4. Select Complex from the Type list.

5. Enter Ad_Request in the Name field.

6. Select Unspecified from the Namespace list.

7. Select Sequence Group from the Model Group list.

8. Click Apply.

7.8.2.1 Creating the Complex Datatype Members of Ad_Request

1. Click Create in the Datatype Members section.

2. Select Scalar from the Type list.

3. Enter Ad_ID in the Name field.

4. Select No from the Mandatory list.

5. Select Core Datatype from the Classification list.

6. Select Unspecified from the Namespace list.

7. Use the flashlight to select integer for the Name field.

8. Click Apply.

9. Click Return to datatype details.

10. Click Create in the Datatype Members section.

11. Select Scalar from the Type list.

12. Enter Date in the Name field.

13. Select No from the Mandatory list.

14. Select Core Datatype from the Classification list.

15. Select Unspecified from the Namespace list.

16. Use the flashlight to select string for the Name field.

17. Click Apply.

18. Click Return to Datatype Details.

19. Click Create in the Datatype Members section.

20. Select Scalar from the Type list.

21. Enter HR_Contact_Name in the Name field.

22. Select No from the Mandatory list.

23. Select Core Datatype from the Classification list.

24. Select Unspecified from the Namespace list.

25. Use the flashlight to select string for the Name field.

26. Click Apply.

27. Click Return to Datatype Details.

28. Click Create in the Datatype Members section.

29. Select Compound from the Type list.

30. Enter Ad in the Name field.

31. Select No from the Mandatory list.

32. Select Business Datatype from the Classification list.

33. Select Unspecified from the Namespace list.

34. Use the flashlight to select AdType for the Name field.

35. Enter 1 in the Minimum field of the Cardinality section.

36. Do not enter a value in the Maximum field of the Cardinality section.

37. Click Apply.

38. Click Return to Datatype Details.

    The new datatype members for the Ad_Request complex datatype appear.

Description of the illustration tut_dt2.gif

You can then include these datatypes in a body element of a business event and in event transformation map statements.

7.9 Updating the Interaction, Native Event, and Application Event

To update an application event (and its corresponding native event), it must first be deleted and then created again. The translator creates the application event based on the record type of a native event. If you use the XSD translator, the application event datatypes are created based on the XSD file provided during the creation of the native event. Before an application event can be deleted, all integration metadata referring to it must no longer do so. For example, when the application event is used in an application role port, the role port must be updated to no longer use that application event. Another example is the transformation. When the application event is used in an event transformation map as a source or target, it must be removed first. The easiest method is to delete the complete spoke before deleting the application event. This works best if the spoke only has a few pass-through steps for handling event flows.

This task demonstrates how to update the HR New Ad application event and delete the HR Placing New Ad spoke after completing phase A of the tutorial (that is, the HR Problem event is not yet modeled).

• Task 1: Deleting a Spoke

• Task 2: Deleting a Transformation Map

• Task 3: Deleting a Native Event

• Task 4: Creating a Native Event

• Task 5: Creating a Spoke

• Task 6: Creating Event Transformation Map Statements

• Task 7: Updating the Agreement to Use a New Native Role

  
  

  See Also: The following sections for additional details about tasks covered in this section: "Creating a Single Spoke" "Deleting a Spoke" "Managing Event Maps" "Transformation Maps Overview" "Transformation Statements Overview" "Managing Native Roles in Application Agreements"

  
  

7.9.1 Task 1: Deleting a Spoke

1. Select the Modeling tab.

2. Select Business Processes.

3. Click the Integration Diagram for the Placing Ad business process.

4. Select Delete Spoke from the Action list.

5. Click HR Placing New Ad-NR.

6. Click Yes when prompted to confirm your selection.

7.9.2 Task 2: Deleting a Transformation Map

1. Select the Modeling tab.

2. Select Transformations.

3. Select HR Ad to Common View in the Delete column.

4. Click Yes when prompted to confirm your selection.

7.9.3 Task 3: Deleting a Native Event

Note: Before deleting the HR New Ad native event described in this task, you must first delete the event map associated with this native event. Delete this event map from the Native Event Type Details: HR New Ad page.

1. Select the Modeling tab.

2. Select Event Types.

3. Select Native Event Types.

4. Select HR New Ad in the Delete column.

5. Click Yes when prompted to confirm your selection.

7.9.4 Task 4: Creating a Native Event

1. Select the Modeling tab.

2. Select Event Types.

3. Select Native Event Types.

4. Click Create.

5. Enter HR New Ad in the Name field.

6. Select Read File -inbound(xmlRecord) - Inbound from the Interaction list.

7. Select xmlRecord from the Record Type list.

8. Click Next.

9. Select XSD from the Translator list.

10. Select Create New.

11. Enter HR Ad in the Name field.

12. Click Browse next to the Content field.

13. Select HR_Ad.xsd.

14. Click Next.

15. Select XSD from the Translator list.

16. Select Yes from the Preserve Namespaces for Native instances list.

17. Select None from the Doctype for Native Instances list.

18. Click Next.

19. Click Finish.

7.9.5 Task 5: Creating a Spoke

1. Select the Modeling tab.

2. Select Business Processes.

3. Click Create Spoke in the Shortcuts section.

4. Click Use Existing.

5. Select Placing Ad from the Business Process list.

6. Click Next.

7. Select Read File -inbound(xmlRecord) - Inbound from the Interaction list.

8. Click Next.

9. Enter HR Placing New Ad in the Role Naming Convention field.

10. Click Next.

11. Select HR New Ad from the Native Event list.

12. Select Use Existing in the Business Event section.

13. Select Ad Request.

14. Click Next.

15. Select Create New in the Transformation section.

16. Enter HR Ad to Common View.

17. Click Next.

18. Click Finish.

7.9.6 Task 6: Creating Event Transformation Map Statements

1. Select the Modeling tab.

2. Select Transformations.

3. Select HR Ad to Common View from the Name column.

4. Click Expand All for both the Sources table and the Targets table.

5. Select Ad_ID in the Sources table.

6. Select Ad_ID in the Targets table.

7. Select copy:from=integer->to=integer from the Datatype Transformation Map list.

8. Click Append.

7.9.7 Task 7: Updating the Agreement to Use a New Native Role

1. Click the Modeling tab.

2. Select Profiles.

3. Select Agreements.

4. Select HR Agreement in the Name column.

5. Click Add in the Native Roles section.

6. Select HR Placing New Ad-NR from the Native Role list.

7. Click Apply.

7.10 .xsd and .xml Files Used in This Tutorial

This tutorial uses the following files:

• HR_Ad.xsd File

• Global_Newspaper_Ad.xsd File

• Ad_CommonView.xsd File

• Global_NP_AdConfirmation.xsd File

• HR_AdProblem.xsd File

• HR_Ad.xml File

• Global_NP_AdConfirmation.xml File

7.10.1 HR_Ad.xsd File

This is the file you selected in Step 6 of "Creating the Native Event, Translation, and Application Event for the Human Resources Application" and in Step 13 of "Task 4: Creating a Native Event".

<?xml version="1.0"?>
<xs:schema targetNamespace="http://www.oracle.com/human_resources" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.oracle.com/human_resources" elementFormDefault="unqualified" attributeFormDefault="unqualified">
   <xs:element name="Ad_Request">
      <xs:annotation>
         <xs:documentation>Comment describing your root element</xs:documentation>
      </xs:annotation>
      <xs:complexType>
         <xs:sequence>
            <xs:element name="Action" type="xs:string"/>
            <xs:element name="Function_Type" type="xs:string"/>
            <xs:element name="Date" type="xs:dateTime"/>
            <xs:element name="HR_Contact_FirstName" type="xs:string"/>
            <xs:element name="HR_Contact_LastName" type="xs:string"/>
            <xs:choice>
               <xs:element name="phone" type="xs:string"/>
               <xs:element name="email" type="xs:string"/>
            </xs:choice>
            <xs:element name="description" type="xs:string" minOccurs="0"/>
            <xs:element name="Ad" type="AdType" maxOccurs="unbounded"/>
         </xs:sequence>
         <xs:attribute name="Ad_ID" type="xs:integer"/>
      </xs:complexType>
   </xs:element>
   <xs:complexType name="AdType">
      <xs:sequence>
         <xs:element name="Title" type="xs:string"/>
         <xs:element name="Text" type="xs:string"/>
      </xs:sequence>
   </xs:complexType>
</xs:schema>

7.10.2 Global_Newspaper_Ad.xsd File

This is the file you selected in Step 7 of "Creating the Native Event, Translation, and Application Event for the Global Newspaper Application".

<?xml version="1.0"?>
<xs:schema targetNamespace="http://www.oracle.com/global_newspaper" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.oracle.com/global_newspaper" elementFormDefault="unqualified" attributeFormDefault="unqualified">
   <xs:element name="Ad_Request">
      <xs:annotation>
         <xs:documentation>Ad placement request definition required by global newspaper</xs:documentation>
      </xs:annotation>
      <xs:complexType>
         <xs:sequence>
            <xs:element name="Action" type="xs:string"/>
            <xs:element name="Date" type="xs:string"/>
            <xs:element name="HR_Contact_Name" type="xs:string"/>
            <xs:element name="Content_Type" type="xs:string"/>
            <xs:element name="Featured" type="xs:boolean"/>
            <xs:choice>
               <xs:element name=" HR_Contact_Phone" type="xs:string"/>
               <xs:element name=" HR_Contact_Email" type="xs:string"/>
            </xs:choice>
            <xs:element name="description" type="xs:string" minOccurs="0"/>
            <xs:element name="Ad" type="AdType" maxOccurs="unbounded"/>
         </xs:sequence>
         <xs:attribute name="Ad_ID" type="xs:integer"/>
      </xs:complexType>
   </xs:element>
   <xs:complexType name="AdType">
      <xs:sequence>
         <xs:element name="Title" type="xs:string"/>
         <xs:element name="Text" type="xs:string"/>
      </xs:sequence>
   </xs:complexType>
</xs:schema>

7.10.3 Ad_CommonView.xsd File

This is the file you selected in Step 4 of "Creating the Business Event Datatypes".

<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="unqualified" attributeFormDefault="unqualified">
   <xs:element name="Ad_Request">
      <xs:annotation>
         <xs:documentation>Comment describing your root element</xs:documentation>
      </xs:annotation>
      <xs:complexType>
         <xs:sequence>
            <xs:element name="Ad_ID" type="xs:integer"/>
            <xs:element name="Date" type="xs:string"/>
            <xs:element name="HR_Contact_Name" type="xs:string"/>
            <xs:element name="Ad" type="AdType" maxOccurs="unbounded"/>
         </xs:sequence>
      </xs:complexType>
   </xs:element>
   <xs:complexType name="AdType">
      <xs:sequence>
         <xs:element name="Title" type="xs:string"/>
         <xs:element name="Text" type="xs:string"/>
      </xs:sequence>
   </xs:complexType>
</xs:schema>

7.10.4 Global_NP_AdConfirmation.xsd File

This is the file you selected in Step 4 of "Importing the Business Event Datatypes from an XSD File" and in Step 13 of "Task 1: Creating a Native Event for an Existing Interaction".

<?xml version="1.0"?>
<xs:schema targetNamespace="http://www.oracle.com/global_newspaper" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.oracle.com/global_newspaper" elementFormDefault="unqualified" attributeFormDefault="unqualified">
   <xs:element name="Confirmation">
      <xs:annotation>
         <xs:documentation>Comment describing your root element</xs:documentation>
      </xs:annotation>
      <xs:complexType>
         <xs:sequence>
            <xs:element name="Ad_ID" type="xs:integer"/>
            <xs:element name="Action" type="xs:string"/>
            <xs:element name="Confirmed" type="xs:string"/>
            <xs:element name="Problem_Details" type="xs:string"/>
         </xs:sequence>
      </xs:complexType>
   </xs:element>
</xs:schema>

7.10.5 HR_AdProblem.xsd File

This is the file you selected in Step 4 of "Importing the Business Event Datatypes from an XSD File".

<?xml version="1.0"?>
<xs:schema targetNamespace="http://www.oracle.com/human_resources" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:hr="http://www.oracle.com/human_resources" elementFormDefault="unqualified" attributeFormDefault="unqualified">
   <xs:element name="Problem">
      <xs:annotation>
         <xs:documentation>Comment describing your root element</xs:documentation>
      </xs:annotation>
      <xs:complexType>
         <xs:sequence>
            <xs:element name="Ad_ID" type="xs:integer"/>
            <xs:element name="Action" type="xs:string"/>
            <xs:element name="Problem_Description" type="xs:string"/>
         </xs:sequence>
      </xs:complexType>
   </xs:element>
   <xs:complexType name="AdType">
      <xs:sequence>
         <xs:element name="Title" type="xs:string"/>
         <xs:element name="Text" type="xs:string"/>
      </xs:sequence>
   </xs:complexType>
</xs:schema>

7.10.6 HR_Ad.xml File

This is the file you specified in Step 2 of "Task 5: Testing the Results" and in Step 0 of "Task 4: Testing the Results".

<?xml version="1.0" encoding="UTF-8"?>
<n:Ad_Request xmlns:n="http://www.oracle.com/human_resources" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Ad_ID="12345">
   <Action>HR New Ad Request</Action>
   <Function_Type>Executive</Function_Type>
   <Date>1999-05-31T13:20:00-05:00</Date>
   <HR_Contact_FirstName>John</HR_Contact_FirstName>
   <HR_Contact_LastName>Do</HR_Contact_LastName>
   <Content_Type>Ad</Content_Type>
   <Importance>6</Importance>
   <HR_Contact_Email>[e-mail]</HR_Contact_Email>
   <Ad>
      <Title>Sales</Title>
      <Text>Position available, please write us.</Text>
   </Ad>
</n:Ad_Request>

7.10.7 Global_NP_AdConfirmation.xml File

This is the file you specified in Step 4 of "Task 4: Testing the Results".

<?xml version="1.0"?>
<n:Confirmation xmlns:n="http://www.oracle.com/global_newspaper" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <Ad_ID>12345</Ad_ID>
   <Action>Global NP Ad Confirmation</Action>
   <Confirmed>no</Confirmed>
   <Problem_Details>Credit check not ok</Problem_Details>
</n:Confirmation>

7.11 Chapter Summary

This chapter provides a tutorial that takes you through the tasks of designing and deploying an integration. The tasks for Phase A include creating application details, creating modeling metadata, creating agreements, creating and deploying the configuration, and testing the results. Phase B covers more advanced topics, such as creating and integrating an additional application, manually creating business datatypes, and updating the interaction, native event, and application event.