Running the BusinessEvent Project

You can run the BusinessEvent project to see how to use the Oracle Business Event oracle.apps.per.api.person.update_person to listen to the update of a person’s information from Oracle Advanced Queue.

1. Review the business event:
   1. Log in to the Oracle E-Business Suite website as the sysadmin user.
   2. Select Workflow Administrator Web Applications > Administrator Workflow > Business Events.
   3. Enter oracle.apps.per.api.person.update_person in the Name field, and click Go to review the status of the business event.
   The following figure shows the disabled business event:

   

2. Enable the business event:
   1. Click the icon to update the business event.
   2. In the Status list in the Update Event panel, select Enabled to enable the business events.
   3. Click Apply.
   The following figure shows the enabled business event:

   

3. In the Project Explorer view, expand the BusinessEvent project.
4. Configure the Oracle E-Business Suite connection:
   1. Expand Resources > businessevent.
   2. Double-click OEBSConnectionResource.oebsconnectionResource.
   3. In the OEBS Connection editor, edit the resource connection, and then click Test Connection to validate your connection.

   See Oracle E-Business Suite Connection for more details about how to configure the connection.

5. Open the process:
   1. Expand Processes > businessevent.
   2. Double-click update_person_event.bwp.
6. Execute the generated SQL script:
   1. Click Generate SQL Script in the General tab to generate the SQL scripts.
      See Oracle Business Event General Tab for more details.
   2. Execute the SQL script on the command line to grant insertion privileges to the plug-in user for the interface table.
7. Trigger an event in Oracle E-Business Suite:
   1. Log in to the Oracle E-Business Suite system as the Operations user. The default password is welcome.
   2. Select Human Resources, Vision Enterprises > People > Enter and Maintain.
   3. Enter A% in the Full Name field in the Find Person dialog to find a person’s name that begins with an A, and then click Find.
   4. Select Alexander, and click OK to review the person’s information.
   5. Update the value in the Office field from Building 500 to Building 1000, and then click the icon. Click Update in the pop-up dialog.

   The following figure shows the updated personal information of Alexander:

   

8. Get the event attributes in TIBCO Business Studio.

   Click Get Event Attributes in the Event Attributes tab.

   If you do not generate or execute the SQL script, an error JAM-143: Queue must be specified occurs.

   If you do not trigger an event first, an error Please trigger an event in Oracle E-Business Suite first occurs.

   The following figure shows the event attributes:

   

9. Save the project.
10. From the menu, Click Run > Debug Configurations, or click Debug > Debug Configurations.
11. Click BusinessWorks Application > BWApplication in the left panel in the Debug Configurations window.
    By default, all applications in the current workspace are selected in the Applications tab.
12. Click Deselect All in the Applications tab, and select the check box next to the project you want to run.
13. Click Debug to run the process.
14. Click the Terminate icon in the Console view to stop the running process.

    You can check the activity output in the Output tab in the Job Data view. The following figure shows a sample of the activity output:

    

    Note: If you want to use the bw.application.job.flowlimit.application_name.application VM argument when running the activity, you must set the isFlowlimitForOebs argument to true. The configuration of the argument is as follows:

    • Design time: in the Run Configurations or Debug Configurations dialog, select BusinessWorks Application > BWApplication on the left, and click the Arguments tab on the right; then enter -DisFlowlimitForOebs=true in the VM arguments text box.
    • Run time: add isFlowlimitForOebs=true to the config.ini configuration file, which is located in the TIBCO_HOME\bw\version_number\domains\domain_name\appnodes\appspace_name\appnode_name directory.