Skip Headers

Oracle Fusion Middleware Adapter for Oracle Applications User's Guide
11g Release 1 (11.1.1.4.0)
Part Number E10537-03
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Using Concurrent Programs

This chapter covers the following topics:

Overview of Concurrent Programs

A concurrent program is an instance of an execution file. Concurrent programs use a concurrent program executable to locate the correct execution file. Several concurrent programs may use the same execution file to perform their specific tasks, each having different parameter defaults. Concurrent manager runs in the background waiting for a concurrent program to be submitted. As soon as a concurrent program is submitted, it is put into an execution queue by concurrent manager. Concurrent manager also manages the concurrent execution of concurrent programs.

Concurrent programs associated with the Open Interface Table move the data from interface table to base tables. While other concurrent programs execute the business logic and application-level processing for Oracle E-Business Suite.

Design-Time Tasks for Concurrent Programs

This section describes how to configure the Adapter for Oracle Applications to use concurrent programs. It describes the tasks required to configure Adapter for Oracle Applications using the Adapter Configuration Wizard in Oracle JDeveloper.

BPEL Process Scenario

Take Open Interface: Order Import concurrent program (OEOIMP) as an example. This concurrent program allows you to run the Order Import process to retrieve order details from the Order Management open interface tables to create sales orders.

When a request of creating an order is received, order details will be passed and inserted into Open Interface tables (OE_HEADER_IFACE_ALL and OE_LINES_IFACE_ALL). Once the insertion is completed, the concurrent program is invoked to import order data from Open Interface tables to Order Management base tables.

If the BPEL process is successfully executed after deployment, you should find the order is created in Oracle Applications. The purchase order ID should be the same as the payload input value.

Prerequisites to Configuring Concurrent Programs

Populating Application Context Header Variables

You need to populate certain variables in the BPEL PM in order to provide context information for Oracle Applications. The context information is required for a transaction in order for an Oracle Applications user that has sufficient privileges to run the program.

The context is set taking into account the values passed for the header properties including Username, Responsibility, Responsibility Application, Security Group, and NLS Language. If the values for the new header properties Responsibility Application, Security Group, and NLS Language are not passed, context information will be determined based on Username and Responsibility.

The default Username is SYSADMIN, the default Responsibility is SYSTEM ADMINISTRATOR, the default Security Group Key is Standard, and the default NLS Language is US.

You can change the default values specified in the generated WSDL. This is a static way of changing the context information. These values would apply to all invocations of the deployed business process. However, if you need to provide different context information for different invocations of the business process, then you can dynamically populate the header values. The context information can be specified by configuring an Invoke activity.

For more information about applications context, see Supporting for Normalized Message Properties.

BPEL Process Creation Flow

Based on the process scenario, the following design-time tasks are explained in this chapter:

  1. Create a new BPEL project.

  2. Add partner links.

  3. Add a partner link for File Adapter.

  4. Configure Invoke activities.

  5. Configure Assign activities.

Creating a New BPEL Project

To create a new BPEL project

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

    the picture is described in the document text

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

  3. Enter an appropriate name for the project in the Project Name field. For example, OrderImportConcurrentProgram.

    The Create SOA Application - Name your project Page

    the picture is described in the document text

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

    the picture is described in the document text

  5. In the BPEL Process Name field, enter a descriptive name. For example, OrderImportConcurrentProgram.

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

    the picture is described in the document text

  7. Enter an appropriate name for the BEPL process in the Name field. For example, OrderImportConcurrentProgram.

    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, OrderImportConcurrentProgram.bpel and OrderImportConcurrentProgram.wsdl) and composite.xml are also generated.

Adding Partner Links

The next task is to add a partner link to the BPEL process. A partner link defines the link name, type, and the role of the BPEL process that interacts with the partner service.

Based on the BPEL process scenario discussed earlier, the following two partner links need to be configured:

To add the first partner link

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

  2. Enter a service name in the Service Name field. For example, InsertOrder.

    Click Next. The Service Connection dialog appears.

    Specifying a Database Service Connection

    the picture is described in the document text

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

  4. Click Next in the Service Connection dialog box. You can add a concurrent program by browsing through the list of concurrent programs 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:

    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.

  5. Click Get Object to open the Oracle Applications Module Browser.

    Selecting a Concurrent Program from the Module Browser

    the picture is described in the document text

    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.

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

    Click OK. The Application Interface page appears with the selected open table.

    Adapter Configuration Wizard - Application Interface Page

    the picture is described in the document text

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

    the picture is described in the document text

    Click OK.

  8. Click Next. The Operation Type page is displayed.

    Adapter Configuration Wizard - Operation Type Page

    the picture is described in the document text

    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.

  9. Click Next. The Select Table page is displayed.

    Adapter Configuration Wizard - Select Table Page

    the picture is described in the document text

    Select OE_HEADERS_IFACE_ALL as the root database table for this service's query.

  10. Click Next. The Define Primary Keys page is displayed.

    Adapter Configuration Wizard - Define Primary Keys Page for OE_HEADERS_IFACE_ALL

    the picture is described in the document text

    Select the following primary keys for the OE_HEADERS_IFACE_ALL table:

    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

    the picture is described in the document text

  11. Click Next. The Relationships page appears. Click Create to open the Create Relationship dialog.

    Defining Relationships

    the picture is described in the document text

    Enter the following information to define the relationship between the header and the detail table:

    Click OK. The newly created relationship information appears in the Relationships page.

    Adapter Configuration Wizard - Relationships Page

    the picture is described in the document text

  12. Click Next. The Attribute Filtering page appears. Leave default selections unchanged.

    Adapter Configuration Wizard - Attribute Filtering Page

    the picture is described in the document text

    Click Next. The Advanced Options page appears.

    Click Next.

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

    the picture is described in the document text

  14. Click Apply and then OK. The partner link is created with the required WSDL settings.

To add the second partner link

  1. 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 after the first partner link. The Adapter Configuration Wizard Welcome page appears. Click Next.

  2. Enter a service name in the Service Name field. For example, ImportOrderCP.

    Click Next. The Service Connection dialog appears.

    Specifying a Database Service Connection

    the picture is described in the document text

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

  4. Once you have completed creating a new connection for the service, you can add a concurrent program by browsing through the list available in Oracle Applications.

    Click Next.

    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 appears indicating that Adapter could not find the Oracle Integration Repository data file corresponding to the database you are connecting to Oracle Applications 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:

    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 in the Application Interface dialog to open the Oracle Applications Module Browser.

  5. The Oracle Applications Module Browser combines interface data from Oracle Integration Repository with information about the additional interfaces supported by Oracle Application Adapter, organized in a tree hierarchy.

    Specify a concurrent program from The Oracle Applications Module Browser

    the picture is described in the document text

    Navigate to Order Management Suite (OM_PF) >Order Management (ONT) > Sales Order (ONT_SALES_ORDER) > OpenInterfaces > Order Management Sales Orders Open Interface > ConcurrentPrograms to select a concurrent program OEOIMP (OEOIMP).

  6. Click OK. The Application Interface page appears.

    Adapter Configuration Wizard - Application Interface Page

    the picture is described in the document text

  7. Click Next, then click Finish to complete the process of configuring Adapter for Oracle Applications.

    The wizard generates the WSDL file corresponding to the XML schema. This WSDL file is now available for the partner link.

    Create Partner Link

    the picture is described in the document text

  8. Click Apply and then OK. The partner link is created with the required WSDL settings.

Adding Partner Links for File Adapter

Use this step to configure a BPEL process by synchronously reading payload from an input file to obtain the order details and concurrent program details.

Configure the following two partner links:

  1. To obtain order details from an input file through Synchronous Read operation.

  2. To obtain concurrent program details from an input file through Synchronous Read operation.

To add the first Partner Link for File Adapter to read order details:

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

  2. In the Service Name dialog, enter a name for the File Adapter service, for example, getOrderDetails.

  3. Click Next. The Adapter Interface page appears.

    Specifying the Adapter Interface

    the picture is described in the document text

    Select the Define from operation and schema (specified later) radio button and click Next.

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

    the picture is described in the document text

    Click Next to access the File Directories page.

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

    the picture is described in the document text

    Click Next to open the File Name page.

  6. Enter the name of the file for the synchronous read file operation. For example, enter order_data.xml. Click Next. The Messages page appears.

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

    the picture is described in the document text

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

    the picture is described in the document text

    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.

To add the second Partner Link for File Adapter to read concurrent program details:

  1. 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 after the first File Adapter partner link getOrderDetails. The Adapter Configuration Wizard Welcome page appears.

    Click Next.

  2. In the Service Name page, enter a name for the File Adapter service, such as getCPDetails.

  3. Click Next. The Adapter Interface page appears.

    Specifying the Adapter Interface

    the picture is described in the document text

    Select the Define from operation and schema (specified later) radio button and click Next.

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

    the picture is described in the document text

    Click Next to access the File Directories page.

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

    the picture is described in the document text

    Click Next to open the File Name page.

  6. Enter the name of the file for the synchronous read file operation. For example, enter cp_data.xml. Click Next to open the Messages page.

  7. Select the 'browse for schema file' icon next to the URL field to open the Type Chooser.

    Selecting Schema URL and Element

    the picture is described in the document text

    Click Type Explorer and select Project Schema Files > APPS_XX_BPEL_FND_REQUEST_WRAPPER_SUBMIT_REQUEST.xsd > InputParameters. Click OK.

    The selected schema information will be automatically populated in the URL and Schema Element fields.

    Specifying Message Schema

    the picture is described in the document text

  8. 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 getCPDetails.wsdl.

    Completing the Partner Link Configuration

    the picture is described in the document text

    Click Apply and OK to complete the configuration and create the partner link with the required WSDL settings for the File Adapter service.

    The getCPDetails Partner Link appears in the BPEL process diagram.

Configuring the Invoke Activities

After adding and configuring partner links, you need to configure the following four Invoke activities:

  1. To get the order details by invoking the getOrderDetails partner link through Synchronous Read operation to read the order from an input file.

  2. To get the concurrent program details by invoking the getCPDetails partner link through Synchronous Read operation to read the concurrent program information from an input file.

  3. To insert order data into Open Interface tables by invoking InsertOrder partner link.

  4. To import order data from Open Interface tables to Oracle Applications by invoking ImportOrderCP concurrent program partner link.

To add the first Invoke activity for a partner link to get order details:

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

    the picture is described in the document text

  2. Link the Invoke activity to the getOrderDetails service. The Edit Invoke dialog appears.

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

  4. Select Global Variable, then enter a name for the variable. You can also accept the default name. Click OK.

  5. Click the Create icon next to the Output Variable field to create a new variable. The Create Variable dialog box appears.

  6. 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 picture is described in the document text

    The Invoke activity appears in the process diagram.

To add the second Invoke activity for a partner link to get concurrent program details:

  1. 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 right after the first Invoke activity.

  2. Link the Invoke activity to the getCPDetails service. The Edit Invoke dialog appears.

  3. Repeat Step 3 to Step 6 described in the first Invoke activity procedure.

    The input and output variables should be populated in the Edit Invoke dialog box.

    the picture is described in the document text

To add the third Invoke activity for a partner link to insert order data into Open Interface tables:

  1. In JDeveloper BPEL Designer, select BPEL Activities and Components in the component palette. Drag and drop the third Invoke activity into the center swim lane of the process diagram, between the second Invoke and callbackClient activities.

  2. Link the Invoke activity to the InsertOrder service. The Edit Invoke dialog box appears.

  3. Repeat Step 3 to Step 4 described in the first Invoke activity procedure. Click OK in the Edit Invoke dialog box to finish configuring the second Invoke activity.

    the picture is described in the document text

To add the fourth Invoke activity for a partner link to import the order information to Oracle Applications:

  1. In JDeveloper BPEL Designer, select BPEL Activities and Components in the component palette. Drag and drop the fourth Invoke activity into the center swim lane of the process diagram, between the third Invoke and callbackClient activities.

  2. Link the Invoke activity to the ImportOrderCP service. The Edit Invoke dialog box appears.

  3. Repeat Step 3 to Step 6 described in the first Invoke activity procedure.

    The input and output variables should be populated in the Edit Invoke dialog box.

    the picture is described in the document text

  4. Setting Header Properties for Application Context

    Use the following steps to set the header message properties required to pass application context required to complete the BPEL process:

    1. Select the Properties tab in the Edit Invoke dialog box.

    2. Scroll down to locate the jca.apps.Username property from the list and double click the associated value field to enable the Adapter Property Value icon.

      Setting Header Message Properties

      the picture is described in the document text

    3. Click the icon to open the Adapter Property Value dialog for the selected jca.apps.Username property.

      Entering the Header Message Property Value

      the picture is described in the document text

    4. Select the Expression radio button and enter 'OPERATIONS' as the property value.

      Click OK.

    5. Repeat Step 2 to Step 4 to assign the following properties:

      • 'Order Management Super User, Vision Operations (USA)' for jca.apps.Responsibility.

      • 204 for jca.apps.ORG_ID

      the picture is described in the document text

  5. Click Apply and then OK to complete the Invoke activity.

Configuring Assign Activities

Based on the BPEL process scenario, you need to configure the following two Assign activities:

  1. To pass the output of File Adapter’s Synchronous Read (getOrderDetails) service as an input to the Open InterfaceInsertOrder service.

  2. To set the payload of the Concurrent Program (ImportOrderCP) service.

To add the first Assign activity:

  1. In JDeveloper BPEL Designer, select BPEL Activities and Components in the component palette.

    Drag and drop the first Assign activity into the center swim lane of the process diagram, between the first and second Invoke activities that you just created earlier.

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

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

    the picture is described in the document text

  4. Enter the following parameter information:

  5. Click Apply and then OK to complete the configuration of the Assign activity.

To add the second Assign activity:

  1. In JDeveloper BPEL Designer, select BPEL Activities and Components in the component palette.

    Drag and drop the second Assign activity into the center swim lane of the process diagram, between the third and fourth Invoke activities that you just created earlier.

  2. 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, SetCPDetails.

  3. Select the Copy Operation tab, click the 'Plus' sign icon and select Copy Operation from the menu. The Create Copy Operation window appears.

  4. Enter the following parameter information:

  5. Click Apply and then OK to complete the configuration of the Assign activity.

Completed Concurrent Program BPEL Process Project

the picture is described in the document text

Click the composite.xml to display the Oracle JDeveloper composite diagram:

the picture is described in the document text

Note: Click the Source tab of composite.xml to enter a value for the physical directory inputDir for the reference getOrderDetails and getCPDetails (such as /usr/tmp).

<property name="inputDir" type="xs:string" many="false" override="may">/usr/tmp</property>

Specifying the Physical Directory for the Property

the picture is described in the document text

Run-Time Tasks for Concurrent Programs

After designing the BPEL process, the next step is to deploy, run and monitor it.

  1. Deploy the BPEL process.

  2. Test the BPEL process.

  3. Verify records in Oracle Applications.

Deploying the BPEL Process

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:

To deploy the BPEL process

  1. Select the BPEL project in the Applications Navigator.

  2. Right-click the project name, then select Deploy > [project name] > [serverConnection] from the menu that appears.

    Deploying the BPEL Process

    the picture is described in the document text

  3. The BPEL process is compiled and deployed. You can check the progress in the Messages window.

    Messages Log

    the picture is described in the document text

    Deployment Log

    the picture is described in the document text

Testing the BPEL Process

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 test the BPEL process

  1. Navigate to Oracle Enterprise Manager Fusion Middleware Control Console (http://<servername>:<portnumber>/em). The composite you deployed is displayed in the Applications Navigation tree.

    the picture is described in the document text

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

  3. 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 'OrderImportConcurrentProgram') from the SOA Infrastructure.

    Viewing Deployed SOA Composites

    the picture is described in the document text

    Click Test at the top of the page.

  4. 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 picture is described in the document text

    The test results appear in the Response tab upon completion.

  5. Click on the BPEL process name and then select 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.

    the picture is described in the document text

    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 (orderimportconcurrentprogram_client_ep), BPEL component (OrderImportConcurrentProgram), and reference binding components (getOrderDetails, getCPDetails, InsertOrder and ImportOrderCP). All involved components have successfully received and processed messages.

    Click the Instances tab and then click the latest Instance ID to see the process flow trace.

    The Flow Trace page is displayed.

    Flow Trace Page

    the picture is described in the document text

    If any error occurred during the test, you should find it in the Faults section.

  6. Click your BPEL service component instance link (such as OrderImportConcurrentProgram) 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

To validate the BPEL process, you can log on to Oracle Applications forms to check the status of the Concurrent Program execution. Once it is successfully executed, the purchase order should also be created in Oracle Applications.

To verify records in Oracle Applications

  1. Log in to Oracle Applications with the Order Management Super User, Vision Operations (USA) responsibility.

  2. Choose Orders, Return > Sales Order to open the Sales Orders form.

    the picture is described in the document text

  3. Search for an order by pressing F11 key. In the Customer PO field, enter the order ID present in the xml file. For example, enter order_id_01 and press CTRL+F11 keys to execute the query.

  4. You should find the newly created order appears with order ID order_id_01.

    Select the Line Items tab to verify the quantity and item type of the order which should be the same as that present in the xml file

  5. Alternatively, you can also validate the result by querying the database with the following SQL statement:

    Select orig_sys_document_ref from oe_order_headers_all where orig_sys_document_ref = ‘order_id_01';

Troubleshooting and Debugging

If you experience problems with your concurrent program integration, you can take the following troubleshooting steps:

If you still experience problems with your integration, you can enable debugging.

Enabling Debugging

You can enable debugging using the BPEL Process Manager.

To enable debugging:

  1. Log into your BPEL Process Manager domain.

  2. Select yourdomain.collaxa.cube.ws

  3. Select Debug.

Debugging information is output to the log file for your domain. To examine the log file in the BPEL Process Manager, navigate to Home > BPEL Domains > yourdomain > Logs. The log file is yourdomain.log.