11g Release 1 (11.1.1)
Part Number E10537-02
Contents
Previous
Next
| Oracle Fusion Middleware Adapter for Oracle Applications User's Guide 11g Release 1 (11.1.1) Part Number E10537-02 | Contents | Previous | Next |
This chapter covers the following topics:
Adapter for Oracle Applications uses interface tables to insert and update data in Oracle Applications, and uses interface views to retrieve data from Oracle Applications. This chapter describes the following interfaces:
Interface Tables
Interface Views
Adapter for Oracle Applications use open interface tables to insert data in Oracle Applications. For example, by using interface tables, you can insert a purchase order into Oracle Applications to generate the sales order automatically. Data is never loaded directly into Oracle Applications base tables. Instead, data is first loaded into interface tables, and then Oracle-supplied concurrent programs move data from interface tables to base tables. This ensures that all business logic and processing is handled using Oracle components.
Adapter for Oracle Applications use open interface tables to integrate with Oracle Applications through direct database access. The Adapter for Oracle Applications inserts data into the open interface tables. These interface tables can be used only for insert operations and support only an inbound connection into Oracle Applications.
Interface tables are intermediate tables into which the data is inserted first. Once the data gets inserted into the interface tables, the data is validated, and then transferred to the base tables. Base tables are real application tables that reside in the application database. The data that resides in the interface tables is transferred to the base tables using concurrent programs. A concurrent program is an instance of an execution file. Concurrent programs are scheduled in Oracle Applications to move data from interface tables to base tables. These programs perform the application-level checks and run validation before inserting data into base tables.
Adapter for Oracle Applications uses views to retrieve data from Oracle Applications. For example, by using views, you can retrieve information about your customers from the required tables in Oracle Applications.
Adapter for Oracle Applications uses views to retrieve data from Oracle Applications. Views allow only simple definition. By using views, you can get synchronous data access to Oracle Applications. In Adapter for Oracle Applications, views are created on base tables as well as interface tables. These views can be used only for select operations.
In the Oracle Applications 11.5.10 release, you cannot work on multiple views. A work around to address this would be to create a view that spans multiple views.
This section describes how to configure the Adapter for Oracle Applications to use interface tables. It describes the steps to configure Adapter for Oracle Applications using the Adapter Configuration Wizard in Oracle JDeveloper.
BPEL Process Scenario
Take Open Interface tables (OE_HEADER_IFACE_ALL and OE_LINES_IFACE_ALL) as examples.
When a request of inserting order data into Open Interface tables is received, order details will be retrieved through synchronous read operation from an input file and then inserted into Open Interface tables (OE_HEADER_IFACE_ALL and OE_LINES_IFACE_ALL).
If the BPEL process is successfully executed after deployment, you can validate the result by fetching the inserted data using SQL statement.
Prerequisites to Configure Interface Tables
Define primary keys on all the interface tables being used.
Define parent-child relationships among all the selected interface tables.
BPEL Process Flow
Following is a list of the procedures required to accomplish the design-time tasks.
To create a new BPEL project
Open JDeveloper BPEL Designer. Click New Application in the Application Navigator.
The Create SOA Application - Name your application page is displayed.
The Create SOA Application - Name your application Page
Enter an appropriate name for the application in the Application Name field and select SOA Application from the Application Template list.
Click Next. The Create SOA Application - Name your project page is displayed.
Enter an appropriate name for the project in the Project Name field. For example, InsertOrder.
The Create SOA Application - Name your project Page
In the Project Technologies tab, ensure that SOA is selected from the Available technology list to the Selected technology list.
Click Next. The Create SOA Application - Configure SOA settings page is displayed.
The Create SOA Application - Configure SOA settings Page
In the BPEL Process Name field, enter a descriptive name. For example, InsertOrder.
Select Composite With BPEL from the Composite Template list, and then click Finish. You have created a new application, and an SOA project. This automatically creates an SOA composite.
The Create BPEL Process page is displayed.
Enter an appropriate name for the BEPL process in the Name field. For example, InsertOrder.
Select Asynchronous BPEL Process in the Template field. Click OK.
An asynchronous BPEL process is created with the Receive and Reply activities. The required source files including bpel and wsdl, using the name you specified (for example, InsertOrder.bpel and InsertOrder.wsdl) and composite.xml are also generated.
This section describes how to add a partner link to your BPEL process. A partner link defines the link name, type, and the role of the BPEL process that interacts with the partner service.
To add a partner link to insert order details into selected Open Interface tables
Click BPEL Services in the Component palette.
Drag and drop Oracle Applications from the BPEL Services list into the right Partner Link swim lane of the process diagram. The Adapter Configuration Wizard Welcome page appears. Click Next.
Enter a service name in the Service Name field. For example, InsertOrder.
Click Next. The Service Connection dialog appears.
Specifying a Database Service Connection
You can perform either one of the following options for your database connection:
Note: You need to connect to the database where Oracle Applications is running.
You can create a new database connection by clicking the Create a New Database Connection icon.
How to define a new database connection, see Create a New Database Connection.
You can select an existing database connection that you have configured earlier from the Connection drop-down list.
The Service Connection page will be displayed with the selected connection information. The JNDI (Java Naming and Directory Interface) name corresponding to the database connection appears automatically in the Database Server JNDI Name field. Alternatively, you can specify a JNDI name.
Note: When you specify a JNDI name, the deployment descriptor of the Oracle Applications adapter must associate this JNDI name with configuration properties required by the adapter to access the database.
The JNDI name acts as a placeholder for the connection used when your service is deployed to the BPEL server. This enables you to use different databases for development and later for production.
Note: For more information about JNDI concepts, refer to Oracle Fusion Middleware User's Guide for Technology Adapters.
Click Next in the Service Connection dialog box. You can add an interface table by browsing through the list of interface tables available in Oracle Applications.
For Oracle E-Business Suite Release 12:
If you are connecting to Oracle E-Business Suite Release 12, then the IREP File not present dialog box appears indicating that Adapter could not find the Oracle Integration Repository data file corresponding to the database you are connecting in your workspace. Absence of the data file would make browsing or searching of Integration Repository tree considerably slow. You can choose to extract the data file and create a local copy of the Integration Repository data file. Once it is created successfully, Adapter will pick it up automatically next time and retrieve data from your local Integration Repository.
You can select one of the following options:
Click Yes to extract the Integration Repository data file.
Extracting Integration Repository Data File
After the system successfully creates a local copy of the Integration Repository data file, next time when you connect to the database, you will find the IRep Data File field appears in the Operation dialog box indicating where your local copy exists with the creation date and time as part of the file name.
Using the Local Integration Repository Data File
Click No to query the Integration Repository data file from the live database you are connecting to display the Integration Repository tree.
Note: It is highly recommended that you create a local copy of the Integration Repository data file so that Adapter will query the data next time from the local copy in your workspace to enhance the performance.
For Oracle E-Business Suite pre-Release 11.5.10:
If you are connecting to a pre-11.5.10 Oracle Applications instance, you must select the interface type in the Adapter Configuration Wizard. Select Tables/Views/APIs/Concurrent Programs to proceed.
Click Get Object to open the Oracle Applications Module Browser.
Selecting a Concurrent Program from the Module Browser
Oracle Applications Module Browser includes the various product families that are available in Oracle Applications. For example, Applications Technology or Order Management Suite are product families in Oracle Applications. The product families contain the individual products. For example, Order Management Suite contains the Order Management product. The individual products contain the business entities associated with the product. For example, the Order Management product contains the Sales Order business entity.
Business entities contain the various application modules that are exposed for integration. These modules are grouped according to the interface they provide. concurrent programs can be found under the Open Interfaces category.
Navigate to Order Management Suite (OM_PF) > Order Management (ONT) > Sales Order (ONT_SALES_ORDER) > OpenInterfaces >Order Management Sales Orders Open Interface (OEOIMP) > Tables to select OE_HEADERS_IFACE_ALL.
Note: You can also search for a table by entering the name of the program in the Object Name field. Select the Tables check box, then click Search.
Click OK. The Application Interface page appears with the selected open table.
Adapter Configuration Wizard - Application Interface Page
Click Get Object to open the Oracle Applications Module Browser again to select another open interface table OE_LINES_IFACE_ALL using the same navigation path Order Management Suite (OM_PF) > Order Management (ONT) > Sales Order (ONT_SALES_ORDER) > OpenInterfaces >Order Management Sales Orders Open Interface (OEOIMP) > Tables.
Click OK. The Application Interface page appears with the two selected tables.
Adapter Configuration Wizard - Application Interface Page
Click OK.
Click Next. The Operation Type page is displayed.
Adapter Configuration Wizard - Operation Type Page
Select the Perform an Operation on a Table radio button and then choose the Insert check box. Ensure that the Select check box is deselected.
Click Next. The Select Table page appears which displays the tables that have been previously imported in this JDeveloper project (including tables that were imported for other partner links). This enables you to reuse configured table definitions in multiple partner links.
Adapter Configuration Wizard - Select Table Page
Select OE_HEADERS_IFACE_ALL as the root database table for this service's query.
Click Next. The Define Primary Keys page is displayed.
Adapter Configuration Wizard - Define Primary Keys Page for OE_HEADERS_IFACE_ALL
Select the following primary keys for the OE_HEADERS_IFACE_ALL table:
ORDER_SOURCE_ID
ORIG_SYS_DOCUMENT_REF
Click Next.
Select the same primary keys for the OE_LINES_IFACE_ALL table.
Adapter Configuration Wizard - Define Primary Keys Page for OE_LINES_IFACE_ALL
Click Next. The Relationships page appears. Click Create to open the Create Relationship dialog.
Defining Relationships
Enter the following information to define the relationship between the header and the detail table:
Select the OE_HEADERS_IFACE_ALL as the parent table and OE_LINES_IFACE_ALL as the child table.
Select the mapping type: OE_HEADERS_IFACE_ALL has a 1:M Relationship with OE_LINES_IFACE_ALL
Note: If foreign key constraints between tables already exist in the database, then two relationships are created automatically while importing tables. One of the relationships is 1:M relationship from the source table, which is the table containing the foreign key constraints, to the target table. The other relationship is a 1:1 back pointer from the target table to the source table.
Select the Private Owned check box.
Associate the foreign key fields with the primary key fields:
OE_HEADERS_IFACE_ALL.ORDER_SOURCE_ID: ORDER_SOURCE_ID
OE_HEADERS_IFACE_ALL.ORIG_SYS_DOCUMENT_REF: ORIG_SYS_DOCUMENT_REF
The Relationship Name field is populated automatically by default. You can optionally specify a new name for the relationship you are creating.
Click OK. The newly created relationship information appears in the Relationships page.
Adapter Configuration Wizard - Relationships Page
Click Next. The Attribute Filtering page appears. Leave default selections unchanged.
Adapter Configuration Wizard - Attribute Filtering Page
Click Next. The Advanced Options page appears.
Click Next.
Click Finish. The wizard generates the WSDL file corresponding to the selected interface. This WSDL file is now available for the partner link.
Completing the Partner Link Configuration
Click Apply and then OK. The partner link is created with the required WSDL settings.
Use this step to configure a BPEL process by synchronously reading payload from an input file to obtain the purchase order details.
To add a Partner Link for File Adapter to read order details:
In JDeveloper BPEL Designer, click BPEL Services in the Component palette.
Drag and drop File Adapter from the BPEL Services list into the right Partner Link swim lane before the first partner link InsertOrder. The Adapter Configuration Wizard Welcome page appears.
Click Next.
In the Service Name dialog, enter a name for the File Adapter service, such as getOrderDetails.
Click Next. The Adapter Interface page appears.
Specifying the Adapter Interface
Select the Define from operation and schema (specified later) radio button and click Next.
In the Operation page, specify the operation type. For example, select the Synchronous Read File radio button. This automatically populates the Operation Name field.
Specifying the Operation
Click Next to access the File Directories page.
Select the Logical Name radio button and specify directory for incoming files, such as inputDir.
Ensure the Delete files after successful retrieval check box is not selected.
Configuring the Input File
Click Next to open the File Name page.
Enter the name of the file for the synchronous read file operation. For example, enter order_data.xml. Click Next to open the Messages page.
Select the 'browse for schema file' icon next to the URL field to open the Type Chooser.
Click Type Explorer and select Project Schema Files > InsertOrder_table.xsd > OeHeadersIfaceAllCollection. Click OK.
The selected schema information will be automatically populated in the URL and Schema Element fields.
Specifying Message Schema
Click Next and then Finish. The wizard generates the WSDL file corresponding to the partner link. The main Create Partner Link dialog box appears, specifying the new WSDL file getOrderDetails.wsdl.
Completing the Partner Link Configuration
Click Apply and OK to complete the configuration and create the partner link with the required WSDL settings for the File Adapter service.
The getOrderDetails Partner Link appears in the BPEL process diagram.
After configuring partner links, you need to configure the following two Invoke activities:
To get the acknowledgement data by invoking the ViewAck partner link.
To write acknowledgement data to an XML file by invoking WriteAckdata partner link for File Adapter.
To add the first Invoke activity for a partner link to get acknowledgement data:
In JDeveloper BPEL Designer, select BPEL Activities and Components in the component palette. Drag and drop the first Invoke activity into the center swim lane of the process diagram, between the receiveInput and callbackClient activities.
Adding an Invoke Activity
Link the Invoke activity to the ViewAck service. The Edit Invoke dialog appears.
Enter a name for the Invoke activity, then click the Create icon next to the Input Variable field to create a new variable. The Create Variable dialog box appears.
Select Global Variable, then enter a name for the variable. You can also accept the default name. Click OK.
Click the Create icon next to the Output Variable field to create a new variable. The Create Variable dialog box appears.
Select Global Variable, then enter a name for the variable. You can also accept the default name. Click OK.
Click Apply and OK in the Edit Invoke dialog box to finish configuring the Invoke activity.
The Invoke activity appears in the process diagram.
To add the second Invoke activity for a partner link to insert order data into Open Interface tables:
In JDeveloper BPEL Designer, select BPEL Activities and Components in the component palette. Drag and drop the second Invoke activity into the center swim lane of the process diagram, between the first Invoke and callbackClient activities.
Link the Invoke activity to the InsertOrder service. The Edit Invoke dialog box appears.
Repeat Step 3 and Step 4 described in the first Invoke activity procedure. Click Apply and then OK in the Edit Invoke dialog box to finish configuring the second Invoke activity.
The next task is to add an Assign activity to the process map. This is used to pass the output of File Adapter’s Synchronous Read (getOrderDetails) service as an input to the Open InterfaceInsertOrder service.
To add an Assign activity:
In JDeveloper BPEL Designer, select BPEL Activities and Components in the component palette.
Drag and drop the Assign activity into the center swim lane of the process diagram, between the first and second Invoke activities that you just created earlier.
Double-click the Assign activity to access the Edit Assign dialog.
Click the General tab to enter a name for the Assign activity. For example, SetOrderDetails.
Select the Copy Operation tab, click the 'Plus' sign icon and select Copy Operation from the menu. The Create Copy Operation window appears.
Specifying a Copy Operation Action
Enter the following parameter information:
In the From navigation tree, select type Variable, then navigate to Variable > Process > Variables > Invoke_SynchRead_OutputVariable and select body.
In the To navigation tree, select type Variable, then navigate to Variable > Process > Variables > Invoke_insert_InputVariable and select OeHeadersIfaceAllCollection.
Click OK. The Edit Assign dialog box appears.
Click Apply and then OK to complete the configuration of the Assign activity.
Completed BPEL Process Diagram
Click the composite.xml to display the Oracle JDeveloper composite diagram:
Note: Click the Source tab of composite.xml to enter a value for the physical directory inputDir for the reference getOrderDetails (such as /usr/tmp).
<property name="inputDir" type="xs:string" many="false" override="may">/usr/tmp</property>
After designing the BPEL process, the next step is to deploy, run, and monitor it.
You must deploy the BPEL process before you can run it. The BPEL process is first compiled, and then deployed to the application server (Oracle WebLogic Server) that you have established the connection.
Prerequisites
Before deploying the BPEL process using Oracle JDeveloper, you must ensure the following:
You must have established the connectivity between the deign-time environment and an application server.
For more information, see Configuring the Data Source in Oracle WebLogic Server and Creating an Application Server Connection.
Oracle WebLogic Server has been started.
Before deploying the BPEL process, you need to start the Oracle WebLogic Server that you have established the connection.
If a local instance of the WebLogic Server is used, start the WebLogic Server by selecting Run > Start Server Instance from Oracle JDeveloper.
Once the WebLogic Admin Server "DefaultServer" instance is successfully started, you should find that <Server started in Running mode> and DefaultServer started message in the Running:DefaultServer and Messages logs.
To deploy the BPEL process
Select the BPEL project in the Applications Navigator.
Right-click the project name. Select Deploy from the menu that appears.
Right-click the project name, and then select Deploy > [project name] > [serverConnection] from the menu that appears.
The BPEL process is compiled and deployed. You can check the progress in the Messages window.
Once the BPEL process is deployed, you can manage and monitor the process from the Oracle Enterprise Manager Fusion Middleware Control Console. You can also test the process and the integration interface by manually initiating the process.
To manually initiate and monitor the BPEL process
Navigate to Oracle Enterprise Manager Fusion Middleware Control Console (http://<servername>:<portnumber>/em). The composite you deployed is displayed in the Applications Navigation tree.
Enter username (such as weblogic) and password and click Login to log in to a farm.
You may need to select an appropriate target instance farm if there are multiple target Oracle Enterprise Manager Fusion Middleware Control Console farms.
From the Farm base domain, expand the SOA > soa-infra to navigate through the SOA Infrastructure home page and menu to access your deployed SOA composite applications running in the SOA Infrastructure for that managed server.
Note: The Farm menu always displays at the top of the navigator. As you expand the SOA folder in the navigator and click the links displayed beneath it, the SOA Infrastructure menu becomes available at the top of the page.
Click the SOA composite application that you want to initiate (such as 'OrderInsert') from the SOA Infrastructure.
Click Test at the top of the page.
The Test Web Service page for initiating an instance appears. You can specify the XML payload data to use in the Input Arguments section.
Enter the input string required by the process and click Test Web Service to initiate the process.
Testing Web Service
The test results appear in the Response tab upon completion.
Click on the BPEL process name and then click the Instances tab. The SOA composite application instance ID, name, conversation ID, most recent known state of each instance since the last data refresh of the page are displayed.
In the Instance ID column, click a specific instance ID to show the message flow through the various service components and binding components. The Flow Trace page is displayed.
In the Trace section, you should find the sequence of the message flow for the service binding component (insertorder_client_ep), BPEL component (InsertOrder), and reference binding components (getOrderDetails and InsertOrder). All involved components have successfully received and processed messages.
If any error occurred during the test, you should find it in the Faults section.
Flow Trace Page
Click your BPEL service component instance link (such as InsertOrder) to display the Instances page where you can view execution details for the BPEL activities in the Audit Trail tab.
Click the Flow tab to check the BPEL process flow diagram. Click an activity of the process diagram to view the activity details and flow of the payload through the process.
Validating Records Using SQL
To confirm that the records have been inserted into the selected Open Interface tables, you can write SQL SELECT statements and fetch the results showing the latest records inserted into the open interface tables.
This section describes the steps to configure Adapter for Oracle Applications using the Adapter Configuration Wizard in Oracle JDeveloper.
BPEL Process Scenario
In this example, Adapter for Oracle Applications retrieves purchase order acknowledgement information from Interface Views OE_HEADER_ACKS_V and OE_LINE_ACKS_V. The acknowledgement information will then be written to an XML file as an output for confirmation.
If the BPEL process is successfully executed after deployment, you can validate the output XML file with the same order book reference ID once an order is approved.
Prerequisites to Configure Views
You need to define a uniqueness criteria, which could be a single key or composite keys.
BPEL Process Flow
Based on the scenario, the following design-time tasks are discussed in this chapter.
To create a new BPEL project
Open JDeveloper BPEL Designer. Click New Application in the Application Navigator.
The Create SOA Application - Name your application page is displayed.
The Create SOA Application - Name your application Page
Enter an appropriate name for the application in the Application Name field and select SOA Application from the Application Template list.
Click Next. The Create SOA Application - Name your project page is displayed.
Enter an appropriate name for the project in the Project Name field. For example, WriteAck.
The Create SOA Application - Name your project Page
In the Project Technologies tab, ensure that SOA is selected from the Available technology list to the Selected technology list.
Click Next. The Create SOA Application - Configure SOA settings page is displayed.
The Create SOA Application - Configure SOA settings Page
In the BPEL Process Name field, enter a descriptive name. For example, WriteAck.
Select Composite With BPEL from the Composite Template list, and then click Finish. You have created a new application, and an SOA project. This automatically creates an SOA composite.
The Create BPEL Process page is displayed.
The Create BPEL Process Page
Enter an appropriate name for the BEPL process in the Name field. For example, WriteAck.
Select Asynchronous BPEL Process in the Template field. Click OK.
An asynchronous BPEL process is created with the Receive and Reply activities. The required source files including bpel and wsdl, using the name you specified (for example, WriteAck.bpel and WriteAck.wsdl) and composite.xml are also generated.
A BPEL partner link defines the link name, type, and the role of the BPEL process that interacts with the partner service.
In the scenario described earlier, you need to add a partner link to retrieve order acknowledgement information from selected Open Interface Views.
To add a partner link
Click BPEL Services in the Component palette.
Drag and drop Oracle Applications from the BPEL Services list into the right Partner Link swim lane of the process diagram. The Adapter Configuration Wizard Welcome page appears. Click Next.
Enter a service name in the Service Name field. For example, ViewAck.
Click Next. The Service Connection dialog appears.
Specifying a Database Service Connection
You can perform either one of the following options for your database connection:
Note: You need to connect to the database where Oracle Applications is running.
You can create a new database connection by clicking the Create a New Database Connection icon.
How to define a new database connection, see Create a New Database Connection.
You can select an existing database connection that you have configured earlier from the Connection drop-down list.
The Service Connection page will be displayed with the selected connection information. The JNDI (Java Naming and Directory Interface) name corresponding to the database connection appears automatically in the Database Server JNDI Name field. Alternatively, you can specify a JNDI name.
Note: When you specify a JNDI name, the deployment descriptor of the Oracle Applications adapter must associate this JNDI name with configuration properties required by the adapter to access the database.
The JNDI name acts as a placeholder for the connection used when your service is deployed to the BPEL server. This enables you to use different databases for development and later for production.
Note: For more information about JNDI concepts, refer to Oracle Fusion Middleware User's Guide for Technology Adapters.
Click Next in the Service Connection dialog box. You can add an interface view by browsing through the list of open interface views available in Oracle Applications.
For Oracle E-Business Suite Release 12:
If you are connecting to Oracle E-Business Suite Release 12, then the IREP File not present dialog box appears indicating that Adapter could not find the Oracle Integration Repository data file corresponding to the database you are connecting in your workspace. Absence of the data file would make browsing or searching of Integration Repository tree considerably slow. You can choose to extract the data file and create a local copy of the Integration Repository data file. Once it is created successfully, Adapter will pick it up automatically next time and retrieve data from your local Integration Repository.
You can select one of the following options:
Click Yes to extract the Integration Repository data file.
Extracting Integration Repository Data File
After the system successfully creates a local copy of the Integration Repository data file, next time when you connect to the database, you will find the IRep Data File field appears in the Operation dialog box indicating where your local copy exists with the creation date and time as part of the file name.
Using the Local Integration Repository Data File
Click No to query the Integration Repository data file from the live database you are connecting to display the Integration Repository tree.
Note: It is highly recommended that you create a local copy of the Integration Repository data file so that Adapter will query the data next time from the local copy in your workspace to enhance the performance.
For Oracle E-Business Suite pre-Release 11.5.10:
If you are connecting to a pre-11.5.10 Oracle Applications instance, you must select the interface type in the Adapter Configuration Wizard. Select Tables/Views/APIs/Concurrent Programs to proceed.
Click Get Object to open the Oracle Applications Module Browser.
Selecting a view from the Module Browser
Oracle Applications Module Browser includes the various product families that are available in Oracle Applications. For example, Applications Technology or Order Management Suite are product families in Oracle Applications. The product families contain the individual products. For example, Order Management Suite contains the Order Management product. The individual products contain the business entities associated with the product. For example, the Order Management product contains the Sales Order business entity.
Business entities contain the various application modules that are exposed for integration. These modules are grouped according to the interface they provide. concurrent programs can be found under the Open Interfaces category.
Navigate to Order Management Suite (OM_PF) > Order Management (ONT) > Sales Order (ONT_SALES_ORDER) > Interface_Views to select OE_HEADER_ACKS_V.
Click OK. The Application Interface page appears with the selected interface view.
Adapter Configuration Wizard - Application Interface Page
Click Get Object to open the Oracle Applications Module Browser again to select another interface viewOE_LINE_ACKS_V using the same navigation path Order Management Suite (OM_PF) > Order Management (ONT) > Sales Order (ONT_SALES_ORDER) > Interface_Views.
Click OK. The Application Interface page appears with the two selected views.
Adapter Configuration Wizard - Application Interface Page
Click OK.
Click Next. The Operation Type page is displayed.
Adapter Configuration Wizard - Operation Type Page
Select the Perform an Operation on a Table radio button and then choose the Select check box.
Note: Interface views can be used only for Select operations.
Click Next. The Select Table page is displayed.
Adapter Configuration Wizard - Select Table Page
Select OE_HEADERS_ACKS_V as the root database table for this service's query.
Click Next. The Define Primary Keys page is displayed.
Adapter Configuration Wizard - Define Primary Keys Page for OE_HEADERS_ACKS_V
Select the following primary keys for the OE_HEADERS_ACKS_V table:
ORIG_SYS_DOCUMENT_REF
ORDER_SOURCE_ID
Click Next.
Select the same primary keys for the OE_LINE_ACKS_V table.
Adapter Configuration Wizard - Define Primary Keys Page for OE_LINE_ACKS_V
Click Next. The Relationships page appears.
Click Create to open the Create Relationship dialog.
Defining Relationships
Enter the following information to define the relationship between the header and the detail table:
Select the OE_HEADERS_ACKS_V as the parent table and OE_LINES_ACKS_V as the child table.
Select the mapping type: OE_HEADERS_ACKS_V has a 1:M Relationship with OE_LINES_ACKS_V
Note: If foreign key constraints between tables already exist in the database, then two relationships are created automatically while importing tables. One of the relationships is 1:M relationship from the source table, which is the table containing the foreign key constraints, to the target table. The other relationship is a 1:1 back pointer from the target table to the source table.
Select the Private Owned check box.
Associate the foreign key fields with the primary key fields:
OE_HEADERS_ACKS_V.ORDER_SOURCE_ID: ORDER_SOURCE_ID
OE_HEADERS_ACKS_V.ORIG_SYS_DOCUMENT_REF: ORIG_SYS_DOCUMENT_REF
The Relationship Name field is populated automatically by default. You can optionally specify a new name for the relationship you are creating.
Click Next. The Attribute Filtering page appears. Leave default selections unchanged.
Adapter Configuration Wizard - Attribute Filtering Page
Click Next. The Define Selection Criteria page appears.
Click Add to add a new parameter if necessary. Click Edit to use the graphical expression builder to create the expression. You can define your own custom Select SQL by modifying the predefined SQL string.
Click Next. The Advanced Options page appears.
Click Next.
Click Finish. The wizard generates the WSDL file corresponding to the selected interface. This WSDL file is now available for the partner link.
Click Apply and then OK. The partner link is created with the required WSDL settings.
Use this step to configure a BPEL process by adding a partner link for File Adapter. This allows the acknowledgement data to be written to an XML file.
To add a partner link for the file adapter
In JDeveloper BPEL Designer, click BPEL Services in the Component palette.
Drag and drop File Adapter from the BPEL Services list into the right Partner Link swim lane of the process diagram right after the partner link you just created. The Adapter Configuration Wizard Welcome page appears.
Click Next.
In the Service Name page, enter a name for the file adapter service, such as WriteAckdata.
Specifying the Service Name
Enter a name for the file adapter service, such as WriteAckData.
Click Next. The Adapter Interface page appears.
Specifying the Adapter Interface
Select the Define from operation and schema (specified later) radio button and click Next.
In the Operation page, specify the operation type. For example, select the Write File radio button. This automatically populates the Operation Name field.
Specifying the Operation
Click Next to access the File Configuration page.
Configuring the Output File
For the Directory specified as field, select the Logical Name radio button. Enter outputDir as the Directory for Outgoing Files (logical name) and specify a naming convention for the output file, such as EventAck%yyMMddHHmmss%.xml.
Tip: When you type a percent sign (%), you can choose from a list of date variables or a sequence number variable (SEQ) as part of the filename.
Confirm the default write condition: Number of Messages Equals 1.
Click Next, and the Messages page appears. For the output file to be written, you must provide a schema.
Click Browse to access the Type Chooser.
Expand the node by clicking Project Schema Files > ViewAck_table.xsd and selecting OeHeaderAcksVCollection. Click OK.
The selected schema information will be automatically populated in the URL and Schema Element fields.
Populating the Selected Message Schema
Click Next and then Finish. The wizard generates the WSDL file corresponding to the partner link. The main Create Partner Link dialog box appears, specifying the new WSDL file.
Completing the Partner Link Configuration
Click Apply and then OK to complete the configuration and create the partner link with the required WSDL settings for the File Adapter service.
Based on the scenario described earlier, you need to configure the following two Invoke activities:
To get the purchase order acknowledgement details by invoking the ViewAck partner link.
To write the purchase order acknowledgement information to an XML file by invoking WriteAckdata partner link for File Adapter.
To add the first Invoke activity for a partner link to get acknowledgement details:
In JDeveloper BPEL Designer, select BPEL Activities and Components in the component palette. Drag and drop the first Invoke activity into the center swim lane of the process diagram, between the receiveInput and callbackClient activities.
Link the Invoke activity to the ViewAck service. The Edit Invoke dialog appears.
The value of the Operation field is automatically selected based on the associated partner link. For example, this Invoke activity is associated with an interface table partner link for 'select' operation only, the 'ViewAckSelect' service name with 'Select' operation is populated as the value.
Enter a name for the Invoke activity, then click the Create icon next to the Input Variable field to create a new variable. The Create Variable dialog box appears.
Select Global Variable, then enter a name for the variable. You can also accept the default name.
Click OK.
Create Variable
Click the Create icon next to the Output Variable field to create a new variable. The Create Variable dialog box appears.
Select Global Variable, then enter a name for the variable. You can also accept the default name.
Click OK to close the Create Variable dialog.
Click Apply and then OK in the Edit Invoke dialog box to finish configuring the Invoke activity.
The Invoke activity appears in the process diagram.
To add the second Invoke activity for a File Adapter partner link to write acknowledgement details in an XML file:
In JDeveloper BPEL Designer, select BPEL Activities and Components in the component palette. Drag and drop the first Invoke activity into the center swim lane of the process diagram, right after the first Invoke activity.
Link the Invoke activity to the WriteAckdata service for File Adapter. The Edit Invoke dialog appears.
Enter a name for the Invoke activity, then click the Create icon next to the Input Variable field to create a new variable. The Create Variable dialog appears.
Select Global Variable, then enter a name for the variable. You can also accept the default name. Click OK to return to the Edit Invoke dialog box.
Click Apply and then OK to finish configuring the Invoke activity.
The second Invoke activity appears in the process diagram.
The next task is to add an Assign activity to the process map. This is used to provide values to the input variables.
To configure the Assign activity
In JDeveloper BPEL Designer, select BPEL Activities and Components in the component palette.
Drag and drop the Assign activity into the center swim lane of the process diagram between the two Invoke activities that you just created earlier.
Double-click the Assign activity to access the Edit Assign dialog.
Click the General tab to enter a name for the Assign activity. For example, setAckdata.
Select the Copy Operation tab, click the 'Plus' sign icon and select Copy Operation from the menu. The Create Copy Operation window appears.
Specifying a Copy Operation Action
Enter the parameter information:
In the From navigation tree, select type Variable, then navigate to Variable > Process > Variables > Invoke_1_ViewAckSelect_OutputVariaable >OeHeaderAcksVCollection and select ns3:OeHeaderAcksVCollection.
The XPath field should contain your selected entry.
In the To navigation tree, select type Variable, then navigate to Variable > Process > Variables > Invoke_2_Write_InputVariable > body and select ns3:OeHeaderAcksVCollection. The XPath field should contain your selected entry.
Click OK. The Edit Assign dialog box appears.
After assigning values to the input variables, click Apply and then OK.
The complete BPEL process diagram should be shown:
BPEL Process Diagram
Click the composite.xml to display the Oracle JDeveloper composite diagram:
Note: Click the Source tab of composite.xml to enter a value for the physical directory outputDir for the reference WriteAckdata (such as /usr/tmp).
<property name="outputDir" type="xs:string" many="false" override="may">/usr/tmp</property>
Specifying the Physical Directory for the Property
Oracle JDeveloper Composite Diagram
After designing the BPEL process, the next steps are to deploy, run and monitor it.
You must deploy the BPEL process before you can run it. The BPEL process is first compiled, and then deployed to the application server (Oracle WebLogic Server) that you have established the connection.
Prerequisites
Before deploying the BPEL process using Oracle JDeveloper, you must ensure the following:
You must have established the connectivity between the deign-time environment and an application server.
For more information, see Configuring the Data Source in Oracle WebLogic Server and Creating an Application Server Connection.
Oracle WebLogic Server has been started.
Before deploying the BPEL process, you need to start the Oracle WebLogic Server that you have established the connection.
If a local instance of the WebLogic Server is used, start the WebLogic Server by selecting Run > Start Server Instance from Oracle JDeveloper.
Once the WebLogic Admin Server "DefaultServer" instance is successfully started, you should find that <Server started in Running mode> and DefaultServer started message in the Running:DefaultServer and Messages logs.
To deploy the BPEL process
Select the BPEL project in the Applications Navigator.
Right-click the project name, and then select Deploy > [project name] > [serverConnection] from the menu that appears.
The BPEL process is compiled and deployed. You can check the progress of the compilation in the Messages window.
Messages Window
Once the BPEL process is deployed, you can manage and monitor the process from the Oracle Enterprise Manager Fusion Middleware Control Console. You can also test the process and the integration interface by manually initiating the process.
To manually initiate and monitor the BPEL process
Navigate to Oracle Enterprise Manager Fusion Middleware Control Console (http://<servername>:<portnumber>/em). The composite you deployed is displayed in the Applications Navigation tree.
Enter username (such as weblogic) and password and click Login to log in to a farm.
You may need to select an appropriate target instance farm if there are multiple target Oracle Enterprise Manager Fusion Middleware Control Console farms.
From the Farm base domain, expand the SOA > soa-infra to navigate through the SOA Infrastructure home page and menu to access your deployed SOA composite applications running in the SOA Infrastructure for that managed server.
Note: The Farm menu always displays at the top of the navigator. As you expand the SOA folder in the navigator and click the links displayed beneath it, the SOA Infrastructure menu becomes available at the top of the page.
Click the SOA composite application that you want to initiate (such as 'WriteAck') from the SOA Infrastructure.
Click Test at the top of the page.
The Test Web Service page for initiating an instance appears. You can specify the XML payload data to use in the Input Arguments section.
Enter the input string required by the process and click Test Web Service to initiate the process.
Testing Web Service
The test results appear in the Response tab upon completion.
Click on the BPEL process name and then click the Instances tab. The SOA composite application instance ID, name, conversation ID, most recent known state of each instance since the last data refresh of the page are displayed.
In the Instance ID column, click a specific instance ID to show the message flow through the various service components and binding components. The Flow Trace page is displayed.
In the Trace section, you should find the sequence of the message flow for the service binding component (writeack_client_ep), BPEL component (WriteAck), and reference binding components (ViewAck and WriteAckdata). All involved components have successfully received and processed messages.
If any error occurred during the test, you should find it in the Faults section.
Click your BPEL service component instance link (such as WriteAck) to display the Instances page where you can view execution details for the BPEL activities in the Audit Trail tab.
Click the Flow tab to check the BPEL process flow diagram. Click an activity of the process diagram to view the activity details and flow of the payload through the process.
Verifying Records in Oracle Applications
Log on to Oracle Applications with Purchasing, Vision Operations (USA) responsibility and select Purchase Order from the navigation menu.
The Oracle Applications Forms open up with the Purchase Order forms.
Create a purchase order with the following header values:
Supplier: Enter a supplier information, such as 'Advanced Network Devices'.
Site: Select a site information, such as 'SANTA CLARA-ERS'.
On the Lines tab, enter a data row with the following values:
Type: Goods
Item: CM13139
Quantity: 1
Description: Hard Drive - 8GB
Promised: Enter any future date in the format of dd-mmm-yyyy (such as 23-JUN-2009)
Save your purchase order. The status of the purchase order is 'Incomplete'.
Click Approve. The Approve Document form appears.
Click OK to confirm the approval.
Note: Because the trading partner is set up and valid, the transmission method is automatically set to XML.
The status of the purchase order is now changed to 'Approved'. For future reference, note the value of the PO, Rev field. For example, the PO number 5789.
Once the purchase order is approved, the order details should be recorded in the system.
After deploying the BEPL process, the order acknowledgement information should be retrieved from the OE_HEADER_ACKS_V and OE_LINE_ACKS_V interface views.
Validate the output file EventAck%yyMMddHHmmss%.xml in the specified output directory by opening the xml file to confirm the purchase order details. The document number in the xml file should be the same number you just approved in Oracle Applications.
Copyright © 2005, 2009, Oracle and/or its affiliates. All rights reserved.