TIBCO ActiveMatrix BusinessWorks Plug-in for Oracle E ......for Oracle E-Business Suite User's Guide...

TIBCO ActiveMatrix BusinessWorks™ Plug-infor Oracle E-Business Suite User's GuideSoftware Release 6.0May 2014

Two-Second Advantage®

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCHEMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY(OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THEEMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANYOTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS ANDCONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTEDSOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THECLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOADOR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE)OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USERLICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THESOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, ANDYOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BEBOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright lawsand treaties. No part of this document may be reproduced in any form without the writtenauthorization of TIBCO Software Inc.

TIBCO, Two-Second Advantage, TIBCO ActiveMatrix BusinessWorks, TIBCO ActiveMatrixBusinessWorks Plug-in for Oracle E-Business Suite, TIBCO Business Studio, and TIBCO EnterpriseAdministrator are either registered trademarks or trademarks of TIBCO Software Inc. in the UnitedStates and/or other countries.

Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform EnterpriseEdition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks ofOracle Corporation in the U.S. and other countries.

All other product and company names and marks mentioned in this document are the property of theirrespective owners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOTALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASEDAT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWAREVERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICALERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESECHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCOSOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright © 2010-2014 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

2

TIBCO ActiveMatrix BusinessWorks™ Plug-in for Oracle E-Business Suite User's Guide

Contents

TIBCO Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Oracle E-Business Suite Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Plug-in Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Prerequisites of Using the Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Installing the Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Connecting to Oracle Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Creating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Creating an Oracle E-Business Suite Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Designing a Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Testing and Debugging an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Deploying an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Shared Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

OEBSConnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Oracle E-Business Suite Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Oracle API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Custom API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Oracle Concurrent Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Custom Concurrent Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Oracle Business Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Working with Sample Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Importing the Sample Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Running a BusinessWorks Process in Debug Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Working with the Oracle API Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Configuring and Running the prepare_purchased_items Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Checking Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Configuring and Running the subassembly_item_and_bom_bill Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49


Working with the Custom API Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Configuring and Running the CustomAPI Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Working with the Oracle Concurrent Program Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

WICMLP Concurrent Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Configuring and Running the OracleCP Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59


Working with the Custom Concurrent Program Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

INCOIN Concurrent Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Configuring and Running the CustomCP Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67


3


Working with the Oracle Business Event Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Oracle API and Custom API Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Oracle Concurrent Program and Custom Concurrent Program Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

SRS Concurrent Program and Non-SRS Concurrent Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Sample Non-SRS Concurrent Program: GLBBSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Checking the Type and Parameters of a Concurrent Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Checking the Type of a Concurrent Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Finding the Parameters for a Concurrent Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Submitting a Request Using Oracle E-Business Suite Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Submitting a Standard Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Submitting a Non-Standard Request Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Submitting a Request Using Plug-in Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Using the Oracle Concurrent Program Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Using the Custom Concurrent Program Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Introduction to Oracle Integration Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Searching for a Business Service Interface in Oracle Integration Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Introduction to Oracle Database JPublisher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

Wrapper and Non-Wrapper Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

Oracle JPublisher Usage in the Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Installing JPublisher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Supported Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Using JPublisher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Granting the Privilege for the Running Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Running JPublisher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

JPublisher Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104

JPublisher Wrapper Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Updating the Oracle JDBC Library or Oracle Advanced Queuing Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Log Table Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

4


TIBCO Documentation and Support Services

All TIBCO documentation is available in the TIBCO Documentation Library, which can be found here:

https://docs.tibco.com

Product-Specific Documentation

The following documents for this product can be found in the TIBCO Documentation Library:

● TIBCO ActiveMatrix BusinessWorks Plug-in for Oracle E-Business Suite User's Guide Read this manualfor the concepts relating to the plug-in, the applications with which the plug-in interacts,configuration and deployment information, and examples.

● TIBCO ActiveMatrix BusinessWorks Plug-in for Oracle E-Business Suite Installation Read this manual forinstructions on site preparation and installation.

● TIBCO ActiveMatrix BusinessWorks Plug-in for Oracle E-Business Suite Release Notes Read the releasenotes for a list of new and changed features. This document also contains lists of known issues andclosed issues for this release.

How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, contact TIBCO Support asfollows:

● For an overview of TIBCO Support, and information about getting started with TIBCO Support,visit this site:

http://www.tibco.com/services/support

● If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you canrequest one.

How to Join TIBCOmmunity

TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is aplace to share and access the collective experience of the TIBCO community. TIBCOmmunity offersforums, blogs, and access to a variety of resources. To register, go to:

http://www.tibcommunity.com

5


https://docs.tibco.com

http://www.tibco.com/services/support

https://support.tibco.com

http://www.tibcommunity.com

Oracle E-Business Suite Overview

Oracle E-Business Suite (EBS) is a complete set of business applications for managing and automatingprocesses for your enterprise. It is also known as Oracle Enterprise Resource Planning (ERP), OracleApps, Oracle Applications, and Oracle Financials on the market.

It is a comprehensive suite of integrated, global business applications that provides:

● a complete, integrated business intelligence portfolio● an adaptable global business platform● a customer-focused applications strategy

Oracle E-Business Suite Architecture

The Oracle E-Business Suite Architecture is a framework for multi-tiered, distributed computing thatsupports Oracle E-Business Suite products. In this model, various servers or services are distributedamong three levels, or tiers.

6


Plug-in Overview

TIBCO ActiveMatrix BusinessWorks Plug-in for Oracle E-Business Suite plugs into TIBCOActiveMatrix BusinessWorks. You can use this plug-in to configure a connection to Oracle E-BusinessSuite, and then use activities to integrate with Oracle E-Business Suite.

TIBCO ActiveMatrix BusinessWorks is an easy to use integration product suite for enterprise, web, andmobile applications. The product uses the Eclipse graphical user interface (GUI) provided by TIBCOBusiness Studio to define business processes and generate deployable artifacts in the form of EnterpriseArchives (EAR files).

TIBCO ActiveMatrix BusinessWorks Plug-in for Oracle E-Business Suite extends the palettefunctionality provided by TIBCO ActiveMatrix BusinessWorks. After installing the plug-in, a SharedResource and a Oracle E-Business Suite Palette become available in TIBCO Business Studio. You canadd the plug-in activities in the palette to the business processes you are designing, and integrate theminto the process flow. At runtime, the plug-in activities are executed as part of the TIBCO ActiveMatrixBusinessWorks process execution.

TIBCO ActiveMatrix BusinessWorks Plug-in for Oracle E-Business Suite provides the followingfeatures:

● Support for Oracle E-Business Suite. (See the readme file for supported versions.)

● Support for Oracle BusinessEvents as outbound Business Objects.● Support for both PL/SQL API from Oracle Integration Repository and API defined by the customer.● Support for both Concurrent Programs from Oracle Integration Repository and Concurrent

Programs defined by the customer.● Support for Custom Oracle BusinessEvents. This is a way to register a user created event in Oracle

E-Business Suite, which allows it to be searchable in Oracle Integration Repository.

7


Prerequisites of Using the Plug-in

Before you can start configuring the plug-in, you need to complete the prerequisite tasks.

Installing the Plug-inBefore starting to configure the plug-in, ensure that all the required software products have beeninstalled and is operating correctly.See TIBCO ActiveMatrix BusinessWorks Plug-in for Oracle E-Business Suite Installation for details.

Connecting to Oracle Database ServerA connection to the Oracle Database Server is required by the plug-in for configuration of the basicsettings. As part of the installation, two SQL scripts need to be executed. You should have an OracleDatabase system administrator’s account to create a plug-in user and an Oracle E-Business Suiteapplication administrator’s account to grant privileges to the plug-in user.

These two SQL scripts set up the infrastructure in the Oracle E-Business Suite database that are used bysome of the features of the plug-in:

● create_user.sql

This script creates the database user that the plug-in will use to interact with the database. Atruntime, the plug-in user will be used to execute all SQL against the database. This design allowsmore fine grain control over the privileges granted to the plug-in.

● common_all.sql

This script grants the plug-in user with privileges to access the Oracle Database Dictionary tables,Oracle Integration Repository tables, and Oracle Concurrent Program infrastructure packages andprocedures. The script also creates the log table and SQL package used by the plug-in to record theprogress and result of every transaction.

8


Procedure

1. Log on to Oracle SQL*Plus.On the command line, type sqlplus. Enter the Oracle Database system administrator’s usernameand password. The following figure shows a sample logon screen.

9


2. Create a plug-in user.The plug-in requires a user that can access the various schema, object, and data in the Oracle E-Business Suite system. Run the create_user.sql file that is located in the TIBCO_HOME/bw/palettes/oracleebs/version/config directory. Enter the username and password on thecommand line.

10


3. Initialize the plug-in user.Run the common_all.sql file that is located in the TIBCO_HOME/bw/palettes/oracleebs/version/config directory to initialize the plug-in user. You will be prompted to enter values forthe following parameters:

● dba_username: typically system

● dba_password: typically manager

● db_connectstring: net service name

● plug-in username: as created in Step 2

● plug-in password: as created in Step 2

● apps_username: typically apps

● apps_password: typically apps

The following figure shows the script execution screen.

11


Getting Started

A typical workflow for using the plug-in to achieve different goals includes creating a project,designing a process, running and debugging, and deploying the application.

TIBCO ActiveMatrix BusinessWorks enables users to create services and integrate applications usingTIBCO Business Studio, which is an Eclipse-based integration development environment, and deploythem at runtime using the bwadmin utility.

1. Creating a Project

2. Creating an Oracle E-Business Suite Connection

3. Designing a Process

4. Testing and Debugging an Application

5. Deploying an Application

Creating a ProjectBusinessWorks application modules are Eclipse projects that are created in TIBCO Business Studio,which contain various resources.

Procedure

1. Start TIBCO Business Studio.

2. Select File > New > BusinessWorks Resources.

3. Click the BusinessWorks Application Module resource in the BusinessWorks Resource wizard.Click Next.

4. Type a name for the project that you are creating in the Project name field.

5. Select the Create empty process check box and type a process name in the Name field.

6. Select the Create Application check box and type an application name in the Name field. ClickFinish.

Result

A project with the default settings is opened in the Project Explorer view. Two project folders arecreated: project_name, and project_name.application.

The Process editor is displayed automatically.

12


Creating an Oracle E-Business Suite ConnectionCreate and configure a connection resource for connecting with Oracle E-Business Suite.

Procedure

1. Expand the created project in the Project Explorer view.

2. Right-click the Resources folder and select New > OEBSConnection.

3. Type a name for the shared resource in the editor. Click Finish.

4. Configure the connection resource in the editor. See Oracle E-Business Suite Connection regardingthe configuration fields.

5. Click Test Connection to validate the connection.

6. Save the project.

Result

A connection resource is created: connection_name.oebsconnectionResource. The connectionresource is saved in the Resources > project_name directory by default or the directory youspecified.

Designing a ProcessProcesses capture and manage the flow of business information in an enterprise between different datasources and destinations. You can design a process by using activities and adding conditions.

By default, an empty process is created when Creating a Project with the Create empty process checkbox selected.

13


See TIBCO ActiveMatrix BusinessWorks Getting Started for more details about creating processes.

Procedure

1. Select an activity from the Palette view and drop it to the Process editor.For example, select and drag the Timer activity from the General Activities folder and the OracleAPI activity from the Oracle E-Business Suite folder.

2. Click the icon to create links between the activities.

3. Configure the added activities as described in Oracle E-Business Suite Palette.

4. Save the project.

Result

The process with configured activities is saved: process_name.bwp. The process is saved in theProcess > project_name directory by default or the directory you specified.

Testing and Debugging an ApplicationTest the application you have created to ensure the application configuration is correct.

Procedure

1. Click Run > Run to run an application.

2. Optional: Click Run > Debug to debug an application.The perspective changes to Debug from Modeling.

Result

An instance of the application starts running and debugging messages are displayed in the Consoleview.

Deploying an ApplicationGenerate an EAR file for an application, and deploy it using the bwadmin utility.See TIBCO ActiveMatrix BusinessWorks Administration for more details.

Prerequisites

Create the domain, AppSpace, and AppNode.

Procedure

1. Generate an .ear file in TIBCO Business Studio.a) In the Project Explorer view, expand application_name.application > Package Unit and double

click Overview.b) In the editor, click the Export Application for Deployment link.c) In the opened dialog, specify the EAR Location field or click Browser to select the folder where

you want to generate the .ear file and click Finish.The generated .ear file is created in the specified location.

14


2. Deploy the .ear file using the bwadmin utility.a) Start the BusinessWorks agent: on the command line, navigate to TIBCO_HOME\bw\version\bin

and type bwagent.b) Start the bwadmin utility: in the same command line, type bwadmin.c) Upload the .ear file to my_domain which contains my_AppSpace by using the following

command:bwadmin[admin@my_domain/my_AppSpace]> upload -d my_domain C:/EAR_file_path/EAR_file_name

d) Deploy the .ear file to my_domain by using the following command:bwadmin[admin]> Deploy -d my_domain -a my_AppSpace EAR_file_name

Result

You can use the bwadmin show command or TEA web client to view the deployed applications.

15


Shared Resource

Shared resources are specifications that are shared among activities. This plug-in contains one sharedresource: OEBSConnection.

OEBSConnectionThe OEBSConnection resource contains the information that is necessary to establish a connection poolat runtime to the Oracle E-Business Suite server and is used by the activities to obtain connections tothe server.

General Panel

The General panel contains the following fields.

FieldModuleProperty? Description

Name No Name of the Oracle E-Business Suite connection. The default isoebsconnectionResource.

Description No Description of the resource.

OEBSConnection Configuration Panel

The OEBSConnection Configuration panel contains the following fields.

Field

ModuleProperty? Description

Database URL Yes The standard Oracle JDBC connection string. Forexample,

jdbc:oracle:thin:@192.168.71.209:1521:vis

APPS User Name Yes Username of an Oracle E-Business Suite applicationadministrator used to access Oracle E-BusinessSuite.

APPS User Password Yes Password of an Oracle E-Business Suite applicationadministrator used to access Oracle E-BusinessSuite. This is used only at design time. At runtime,this password is not used and it can be invalid. Thisis one strategy to protect the real password of theruntime environment.

Plug-in User Name Yes Username used to run the plug-in.

Plug-in User Password Yes Password used to run the plug-in.

Maximum Number of ReconnectAttempts

Yes Maximum number of reconnection attempts tomake when the connection is lost.

16


Field

ModuleProperty? Description

Interval between ReconnectAttempts (ms)

Yes Time interval in milliseconds to elapse betweeneach reconnection attempt.

Maximum Connections Yes Maximum number of connections between theplug-in and Oracle E-Business Suite that aremaintained in the plug-in connection pool. Theimportance of this number becomes clear atruntime. When a project has more than one processsimultaneously triggered at runtime, the processesmay need to request more connections than areallowed by the maximum number. In this casesome processes will be suspended until freeconnections are released

Login Timeout (s) Yes Timeout interval required to log in.

Test Connection No The Test Connection button is used to test whetherthe connection to Oracle E-Business Suite can beestablished. This will test whether the JDBClibraries are correctly referenced and whether theprovided credentials are correct.

17


Oracle E-Business Suite Palette

Oracle E-Business Suite Palette includes several activities to integrate with Oracle E-Business Suite. Theactivities encapsulate routing rules for communication messages and custom configurationinformation.

Oracle APIThe Oracle API activity allows the plug-in to call the PL/SQL APIs that are listed in Oracle IntegrationRepository. This activity can inspect the Integration Repository for parameter input and outputinformation and present this information in a friendly user interface for configuration.

Introduction

The Oracle API activity provides the following functions:

● At design time

— Loads the PL/SQL procedure information from Oracle Integration Repository.— Saves this information to a file.

● At runtime

— Loads the PL/SQL procedure information from the file.— Generates a calling SQL statement.— Calls the PL/SQL procedure.

Oracle Integration Repository is shipped with Oracle E-Business Suite 12.0.x and 12.1.x, thus the OracleAPI activity is applicable in these versions. See Introduction to Oracle Integration Repository fordetails. A comparison between Oracle API activity and Custom API activity is provided in Oracle APIand Custom API Comparison.

General Tab

The API Procedure Name label in the General tab refers to the API procedure or function. It is labeledas API Procedure Name due to the limited space available.

When conducting searches for the API Package Name, API Procedure Name, Wrapper Package Name,and Wrapper Procedure Name, it is recommended that you provide the name prefixes, or as much asyou know about the name into the name fields before clicking the search buttons in order to reduce thesearch time.

The General tab contains the following fields.


Name No Name of the resource. The default is OracleAPI.

18



SharedConnection

Yes Shared configuration resource containing the Oracle E-BusinessSuite connection information.

To select a shared connection resource, click the Choose/Create

Default Resource icon. All usable connections are listed in theopened dialog. Select one to apply to your current activity. If nomatching connection resource is found, click Create SharedResource to create one. See Oracle E-Business Suite Connectionfor more details.

API PackageName

No Business service interface that is exposed by Oracle E-BusinessSuite.

Click Search Package or the text field. Then input a part of thepackage name in the opened dialog and click Search. Select apackage in the opened dialog and click OK.

API ProcedureName

No A procedure from the API Package.

Click Search Procedure or the text field. Then input a part of theprocedure name in the opened dialog and click Search. Select aprocedure in the opened dialog and click OK.

Wrapper PackageName

No Name given to a package of wrapper procedures or functions.This field is shown only when a wrapper package is needed.


Some business objects in the Oracle database cannot be accessedthrough the Oracle JDBC driver directly. In this case, you need tocreate the wrapper package first using Oracle JPublisher. See Introduction to Oracle Database JPublisher for details on how tocreate a wrapper package using JPublisher.

WrapperProcedure Name

No Name given to a wrapper procedure or function used to delegatean API procedure or function. This field is shown only when awrapper procedure or function is needed.


Call ProcedureTimeout(s)

Yes Maximum waiting time for calling the procedure. If the procedurecall exceeds this limit, the attempt will be stopped.

The default is 60 seconds. Entering 0 will result in an unlimitedwaiting time.

19



Generate SQLScript

No After configuring the Oracle API activity, click the Generate SQLScript button. The scripts to be generated are displayed in theopened dialog. Click Generate and the following two SQL scriptsare created in the TIBCO_HOME/bw6/bw/palettes/oracleebs/version/sql directory:

● ProcessName_ActivityName_APIPackageName.APIProcedur

eName.sql


eName_undo.sql

Run theProcessName_ActivityName_APIPackageName.APIProcedureNa

me.sql script in the connected Oracle database before starting theprocess.

The script is used to grant privileges to the plug-in user,so that it can access the objects being configured. It usesthe apps user entered in the Oracle E-Business SuiteConnection resource to get the information to generatethis script. Once this script is executed, the plug-in userwill be able to access the tables and proceduresconfigured for the activity.

The script with the _undo suffix reverses the privilegegranted thus undoing the changes to the database. Thispermits the cleansing of the privileges for objects thatare no longer used by obsolete or unwanted activities.

Description Tab

Provide a short description for the activity.

Prerequisite Tab

The Prerequisite tab allows you to call some Set Client Info and Initialization procedures before callingthe main procedure picked in the General tab. You can add new procedure calls and theircorresponding package information in the Prerequisite tab. When the procedure needs to be wrapped,you need to enter a wrapper package and select a procedure for the wrapper package.

If the procedure name for the wrapper package contains a single dollar sign ($), the $ in the procedurename will be converted to a hyphen (-) in the Input and Output tabs.

20


PLSQL API Details Tab

The PLSQL API Details tab provides the details on the API procedure and Wrapper procedure (ifwrapper procedure exists), which are configured in the General tab. The details are listed in theParameter Name, Parameter Type, and Parameter Direction columns.

● The following figure shows the PLSQL API details without a wrapper package.

● The following figure shows the PLSQL API details with a wrapper package.

If the API procedure contains parameters of the PLSQL data types, such as the PLSQL record type, andthe PLSQL table type which is defined in the PLSQL package, and the BOOLEAN type, the plug-inrequires the related wrapper package and procedure generated from Oracle JPublisher. You shouldexecute the wrapper SQL generated by JPublisher under apps user.

The Parameter Direction column shows whether the parameter is an input, output or both for the APIprocedure.

The Return parameter in the PLSQL API Details tab specifies thatGL_JOURNAL_IMPORT_PKG.GET_LAST_SQL is an Oracle database function, and the return value can beused as an output.

Input Tab

The Input tab lists the input data for the activity. All the parameters of the API procedure or Wrapperprocedure with the Parameter Direction IN or IN/OUT in the PLSQL API Details tab are listed in theActivity Input column.

The parameters listed in the Activity Input column can be configured manually or automatically bydefining a module property. For how to define module properties, see "Using Process and ModuleProperties" in TIBCO ActiveMatrix BusinessWorks Samples.

Output Tab

The Arguments node in the Output tab lists all the parameters of the API procedure or Wrapperprocedure with the Parameter Direction OUT or IN/OUT in the PLSQL API Details tab. The

21


Error_Messages node lists the FND (Oracle Application Object Library) error message when the APIencounters error in the Oracle E-Business Suite system.

Fault Tab

The Fault tab lists the following exceptions thrown by this activity.

See Error Messages for more information about error codes and corrective actions to take.

Fault Thrown When ...

OracleEBSPaletteAQConnectionException The AQ Connection does not initialize.

OracleEBSPaletteConnectionNotFoundException The connection cannot be created.

OracleEBSPaletteSQLException A SQL Exception happens.

OracleEBSPaletteTimeoutException Calling the procedure for PLSQL API.

Custom APIThe Custom API activity provides the ability to call packages that are created by the customer tointegrate with Oracle E-Business Suite that is not been registered with the Oracle IntegrationRepository. In such cases, the metadata that defines this package is not contained in the OracleIntegration Repository. The plug-in instead uses the Oracle database dictionary to get detailedinformation about this API.

Introduction

The Custom API activity provides the following functions:

● At design time

— Loads the PL/SQL procedure information from Oracle Database Dictionary.— Saves this information to a file.

● At runtime

— Loads the PL/SQL procedure information from the file.— Generates a calling SQL statement.— Calls the PL/SQL procedure.

A comparison between Oracle API activity and Custom API activity is provided in Oracle API andCustom API Comparison. If you create a Custom API, and register it into the Integration Repository, itbecomes a regular Oracle E-Business Suite API and will be treated as such.

General Tab



Name No Name of the resource. The default is CustomAPI.

22



SharedConnection



Default Resource icon. All usable connections are listed in theopened dialog. Select one to apply to your current activity. If nomatching connection resource is found, click Create SharedResource to create one. See Oracle E-Business Suite Connectionfor more details.

API PackageName

No Business service interface that is exposed by Oracle E-BusinessSuite.


API ProcedureName

No A procedure from the API Package.


Wrapper PackageName

No Name given to a package of wrapper procedures or functions.This field is shown only when a wrapper package is needed.


Some business objects in the Oracle database cannot be accessedthrough the Oracle JDBC driver directly. In this case, you need tocreate the wrapper package first using Oracle JPublisher. See Introduction to Oracle Database JPublisher for details on how tocreate a wrapper package using JPublisher.

WrapperProcedure Name

No Name given to a wrapper procedure or function used to delegatean API procedure or function. This field is shown only when awrapper procedure or function is needed.


Call ProcedureTimeout(s)

Yes Maximum waiting time for calling the procedure. If the procedurecall exceeds this limit, the attempt will be stopped.

The default is 60 seconds. Entering 0 will result in an unlimitedwaiting time.

23



Generate SQLScript

No After configuring the Custom API activity, click the GenerateSQL Script button. The scripts to be generated are displayed inthe opened dialog. Click Generate and the following two SQLscripts are created in the TIBCO_HOME/bw6/bw/palettes/oracleebs/version/sql directory:


eName.sql


eName_undo.sql

Run theProcessName_ActivityName_APIPackageName.APIProcedureNa

me.sql script in the connected Oracle database before starting theprocess.

The script is used to grant privileges to the plug-in user,so that it can access the objects being configured. It usesthe apps user entered in the Oracle E-Business SuiteConnection resource to get the information to generatethis script. Once this script is executed, the plug-in userwill be able to access the tables and proceduresconfigured for the activity.

The script with the _undo suffix reverses the privilegegranted thus undoing the changes to the database. Thispermits the cleansing of the privileges for objects thatare no longer used by obsolete or unwanted activities.

Description Tab


Prerequisite Tab

The Prerequisite tab allows you to call some Set Client Info and Initialization procedures before callingthe main procedure picked in the General tab. You can add new procedure calls and theircorresponding package information in the Prerequisite tab. When the procedure needs to be wrapped,you need to enter a wrapper package and select a procedure for the wrapper package.

If the procedure name for the wrapper package contains a single dollar sign ($), the $ in the procedurename will be converted to a hyphen (-) in the Input and Output tabs.

PLSQL API Details Tab

The PLSQL API Details tab provides the details on the API procedure and Wrapper procedure (ifwrapper procedure exists), which are configured in the General tab. The details are listed in theParameter Name, Parameter Type, and Parameter Direction columns.

The following figures shows the PLSQL API Details tab.

24


If the API procedure contains parameters of PLSQL data type, such as PLSQL record type, and PLSQLtable type which defined in the PLSQL package and BOOLEAN type, the plug-in requires the relatedwrapper package and procedure generated from Oracle JPublisher. And you should execute thewrapper SQL generated by JPublisher under apps user.

The Parameter Direction column shows whether the parameter is an input, output or both for the APIprocedure.

Input Tab

The Input tab lists the input data for the activity. All the parameters of the API procedure or Wrapperprocedure with the Parameter Direction IN or IN/OUT in the PLSQL API Details tab are listed in theActivity Input column.

The parameters listed in the Activity Input column can be configured manually or automatically bydefining a module property. For how to define module properties, see "Using Process and ModuleProperties" in TIBCO ActiveMatrix BusinessWorks Samples.

Output Tab

The Arguments node in the Output tab lists all the parameters of the API procedure or Wrapperprocedure with the Parameter Direction OUT or IN/OUT in the PLSQL API Details tab. TheError_Messages node lists the FND (Oracle Application Object Library) error message when the APIencounters error in the Oracle E-Business Suite system.

Fault Tab

The Fault tab lists the following exceptions thrown by this activity. See Error Messages for moreinformation about error codes and corrective actions to take.





OracleEBSPaletteTimeoutException Calling the procedure for PLSQL API.

Oracle Concurrent ProgramThe Oracle Concurrent Program activity allows the plug-in to populate Oracle interface tables, executeConcurrent Programs, and retrieve status information about the execution. This activity can inspect the

25


Integration Repository for the schema of the interface tables for the selected Concurrent Programs aswell as the parameters required to execute the Concurrent Program and present this information in afriendly user interface for configuration.

Introduction

The Oracle Concurrent Program activity provides the following functions:

● At design time

— Loads Concurrent Program parameters from the FND table.— Loads Inbound Interface Tables or Views from Oracle Integration Repository.— Saves the information to a file.

● At runtime

— Loads Concurrent Program parameters and Interface Tables or Views from the file.— Uses JDBC to insert data into Interface Tables or Views.— Uses JDBC to submit a Concurrent Program request.

Oracle Concurrent Program is applicable in Oracle E-Business Suite 12.0.x and 12.1.x. See Introductionto Oracle Integration Repository for details.

A comparison between Oracle Concurrent Program and Custom Concurrent Program is provided here.

General Tab



Name No Name of the resource. The default is OracleConcurrentProgram.

SharedConnection



Default Resource icon. All usable connections are listed in theopended dialog. Select one to apply to your current activity. If nomatching connection resource is found, click Create SharedResource to create one. See Oracle E-Business Suite Connectionfor more details.

Language No Language that the Oracle E-Business Suite user interface is shownin.

Click Search Language and specify the search criteria in theopened dialog. All the languages that are installed in Oracle E-Business Suite and match the search criteria are listed in thedialog. Then select a language in the opened dialog and click OK.The contents of the Concurrent Program Name, ResponsibilityName, and Output will change accordingly.

26



ConcurrentProgram Name

No Programs that can be called by a concurrent manager.

Click Search Concurrent Program Name and specify the searchcriteria in the opened dialog. Then select a Concurrent Programfrom the Concurrent Program List dialog and click OK.

ResponsibilityName

No A responsibility is a level of authority in Oracle E-Business Suitethat lets users access only those functions and data appropriate totheir roles in the organization.

Click Search Responsibility Name and specify the search criteriain the opened dialog. Then select a Concurrent Program from theConcurrent Program List dialog and click OK.

User Name No Name of the user whose information is stored in Oracle E-Business Suite.

Click Search User Name and specify the search criteria in theopened dialog. Then select a user name from the User Name Listdialog and click OK.

ConcurrentResponse

No If this check box is selected, the plug-in will insert records intointerface tables and submit the concurrent request. Otherwise, theplug-in will only insert records into interface tables.

Wait forResponse

No Select this check box if you want the Concurrent Program toretrieve the REQUEST_ID, PHASE, STATUS, and MESSAGEinformation, which will be shown in the Output tab. If this checkbox is cleared, the response time will be shorter, but only theREQUEST_ID will be retrieved.

Check Interval (s) Yes Time interval for checking the result of executing the ConcurrentProgram. The default is 15 seconds.

Wait Time (s) Yes Total amount of time allowed for checking the result of executingthe Concurrent Program. The time set in this field should be amultiple of the time set in the Check Interval (s) field. The defaultis 0, which means the plug-in will wait until the ConcurrentProgram execution is completed.

27



Generate SQLScript

No After configuring the Oracle Concurrent Program activity, clickGenerate SQL Script. The scripts to be generated are displayed inthe opened dialog. Click Generate and the following two SQLscripts are created in the TIBCO_HOME/bw6/bw/palettes/oracleebs/version/sql directory:

● ProcessName_ActivityName_ConcurrentProgramName.sql

● ProcessName_ActivityName_ConcurrentProgramName_undo

.sql

Run theProcessName_ActivityName_ConcurrentProgramName.sql

script in the Oracle database that the plug-in is connected tobefore starting the process in which the Oracle API activity hasbeen added.

The plug-in generates these scripts to grant privileges tothe plug-in user so that it can access the objects beingconfigured. It uses the apps user entered in the OracleE-Business Suite Connection resource to get theinformation to generate this script. Once this script isexecuted, the plug-in user will be able to access thetables and procedures configured for the activity.

The script with the _undo suffix reverses the privilegegrants thus undoing the changes to the database. Thispermits the cleansing of the privileges for objects thatare no longer used by obsolete or unwanted activities.

If the execution of the Concurrent Program takes a significant time, you can clear the Wait forResponse check box, and just get the REQUEST_ID in the Output tab. Or it is recommended that youselect the Wait for Response check box, and set the Wait Time (s) field to a limited time, so that theConcurrent Program will return the output data no matter the execution of the Concurrent Program iscompleted or not.

Description Tab


Concurrent Program Details Tab

The procedures in the plug-in user schema and the related Interface Tables or Views (if they exist) aredisplayed in this tab.

Input Tab

The Input tab lists the input data for the activity. The parameters in the Activity column correspond tothose shown in the Concurrent Program Details tab, with the following exceptions: application,program, description, start_time, and sub_request.

28


Select the Concurrent Request check box in the General tab to show FND_REQUEST.SUBMIT_REQUEST.

The ResponsibilityName and UserName are dynamic parameters. They are configured in the Generaltab. The plug-in also supports the ability to change the ResponsibilityName and UserName parametersin the Input tab during runtime.

The parameters set in the Input tab takes precedence over those set in the General tab.

Output Tab

The Output tab lists the output information for the activity. If the Wait for Response check box isselected in the General tab, the REQUEST_ID, PHASE, STATUS, and MESSAGE information will all bedisplayed in this tab. Otherwise, only the REQUEST_ID will be retrieved.

If you clear the Concurrent Request check box in the General tab, the output will be empty.

Fault Tab





A JMSException happens during anincoming message delivery.



Custom Concurrent ProgramThe Custom Concurrent Program activity allows the plug-in to call custom concurrent programswritten to integrate with Oracle E-Business Suite that are not registered with the Oracle IntegrationRepository. In this case, the plug-in activity will require the user to specify more information about theconcurrent program and interface tables. Once this information is provided, the plug-in activity allowsfor easy configurability through the user interface.

Introduction

The Custom Concurrent Program activity provides the following functions:

● At design time

— Loads Concurrent Program parameters from the FND table.— Loads Inbound Interface Tables or Views from the database manually.— Saves the information to a file.

● At runtime

— Loads Concurrent Program parameters and Interface Tables or Views from the file.— Uses JDBC to insert data into Interface Tables or Views.— Uses JDBC to submit a Concurrent Program request.

29


Custom Concurrent Program is applicable in Oracle E-Business Suite 11.5.10.x and above.

A comparison between Oracle Concurrent Program and Custom Concurrent Program is provided here.If you create a Custom Concurrent Program, and register it into the Integration Repository, it becomesa regular Oracle Concurrent Program and will be treated as such.

General Tab



Name No The name of the resource. The default isCustomConcurrentProgram.

SharedConnection




Language No Language that the Oracle E-Business Suite user interface is shownin.

Click Search Language and specify the search criteria in theopened dialog. All the languages that are installed in Oracle E-Business Suite and match the search criteria are listed in thedialog. Then select a language in the opened dialog and click OK.The contents of the Concurrent Program Name, ResponsibilityName, and Output will change accordingly.

ConcurrentProgram Name

No Language that the Oracle E-Business Suite user interface is shownin.

Click Search Language and specify the search criteria in theopened dialog. All the languages that are installed in Oracle E-Business Suite are listed in the dialog. Then select a package in theopened dialog and click OK. The contents of the ConcurrentProgram Name, Responsibility Name, and Output will changeaccordingly.

ResponsibilityName

No A responsibility is a level of authority in Oracle E-Business Suitethat lets users access only those functions and data appropriate totheir roles in the organization.

Click Search Responsibility Name and specify the search criteriain the opened dialog. Then select a Concurrent Program from theConcurrent Program List dialog and click OK.

30



User Name No Name of the user whose information is stored in Oracle E-Business Suite.

Click Search User Name and specify the search criteria in theopened dialog. Then select a user name from the User Name Listdialog and click OK.

ConcurrentResponse

No If this check box is selected, the plug-in will insert records intointerface tables and submit the concurrent request. Otherwise, theplug-in will only insert records into interface tables.

Wait forResponse

No Select this check box if you want the Concurrent Program toretrieve the REQUEST_ID, PHASE, STATUS, and MESSAGEinformation, which will be shown in the Output tab. If this checkbox is cleared, the response time will be shorter, but only theREQUEST_ID will be retrieved.

Check Interval (s) Yes This field shows the time interval for checking the result ofexecuting the Concurrent Program. The default is 10 seconds.

Wait Time (s) Yes Total amount of time allowed for checking the result of executingthe Concurrent Program. The time set in this field should be amultiple of the time set in the Check Interval (s) field. The defaultis 0, which means the plug-in will wait until the ConcurrentProgram execution is completed.

Interface TableConfiguration

No Click this button to add the Interface Tables or Views (if theyexist) related to the Concurrent Program.

Different with the Oracle Concurrent Program,Integration Repository does not provide the relevantinformation of Interface Table for Custom ConcurrentProgram. Therefore, you should get such informationfrom custom defined Interface Table configured in theInterface Table Configuration dialog, or from theOracle documentation and Oracle Support.

31



Generate SQLScript

No After configuring the Custom Concurrent Program activity, clickGenerate SQL Script. The scripts to be generated are displayed inthe opened dialog. Click Generate and the following two SQLscripts are created in the TIBCO_HOME/bw6/bw/palettes/oracleebs/version/sql directory:

● ProcessName_ActivityName_ConcurrentProgramName.sql

● ProcessName_ActivityName_ConcurrentProgramName_undo

.sql

Run theProcessName_ActivityName_ConcurrentProgramName.sql

script in the Oracle database that the plug-in is connected tobefore starting the process in which the Oracle API activity hasbeen added.

The plug-in generates these scripts to grant privileges tothe plug-in user so that it can access the objects beingconfigured. It uses the apps user entered in the OracleE-Business Suite Connection resource to get theinformation to generate this script. Once this script isexecuted, the plug-in user will be able to access thetables and procedures configured for the activity.

The script with the _undo suffix reverses the privilegegrants thus undoing the changes to the database. Thispermits the cleansing of the privileges for objects thatare no longer used by obsolete or unwanted activities.

If the execution of the Concurrent Program takes a significant time, you can clear the Wait forResponse check box, and just get the REQUEST_ID in the Output tab. Or it is recommended that youselect the Wait for Response check box, and set the Wait Time (s) field to a limited time, so that theConcurrent Program will return the output data no matter the execution of the Concurrent Program iscompleted or not.

Description Tab


Concurrent Program Details Tab

The FND_REQUEST.OPTION and FND_REQUEST.SUBMIT_REQUEST procedures in the plug-in userschema and the related Interface Tables or Views (if they exist) are displayed in this tab.

Input Tab

The Input tab lists the input data for the activity.

The parameters in the Activity column correspond to those shown in the Concurrent Program Detailstab, with the following exceptions: application, program, description, start_time, andsub_request.

32


Select the Concurrent Request check box in the General tab to show FND_REQUEST.SUBMIT_REQUEST.The parameters of the FND_REQUEST.SUBMIT_REQUEST procedure, argument1 to argument100, arelisted without showing the name of each parameter or whether the parameter is required. This is thestandard implementation for FND_REQUEST.SUBMIT_REQUEST procedure. You can find the realarguments by the scripts in Working with the Sample Project. Also, for non-SRS Concurrent Programs,you must use this standard way. See Oracle Concurrent Program and Custom Concurrent ProgramComparison for more details.

The ResponsibilityName and UserName are dynamic parameters. They are configured in the Generaltab. The plug-in also supports the ability to change the ResponsibilityName and UserName parametersin the Input tab at runtime.

The parameters set in the Input tab takes precedence over those set in the General tab.

Output Tab

The Output tab lists the output information for the activity.

If the Wait for Response check box is selected in the General tab, the REQUEST_ID, PHASE, STATUS, andMESSAGE information will all be displayed in this tab. Otherwise, only the REQUEST_ID will be retrieved.

If you clear the Concurrent Request check box in the General tab, the output will be empty.

Fault Tab





A JMSException happens during anincoming message delivery.



Oracle Business EventThe Oracle Business Event activity listens for an Oracle Business Event triggered in the Oracle E-Business Suite application. Upon the triggering of this event, the activity pulls the event data from theOracle event queue and make the data available to the TIBCO environment. Custom business eventsconfigured in Oracle E-Business Suite and registered to the Oracle Integration Repository arecompatible with this activity.

Introduction

A business event represents an action or occurrence triggered by a business process in an application orsystem. This event may be significant to other programs, applications, processes or external agents. InOracle E-Business Suite, events can be triggered by business object manipulation (such as an update orchange) or by different processes (such as the approval of a purchase order).

33


The Oracle Business Event activity provides the following functions:

● At design time

— Generates PL/SQL scripts to help users subscribe a Business Event to a specified OracleAdvance Queue (AQ).

— Connects to the AQ, retrieves an event, and parses the event schema.● At runtime

— Connects to the AQ and listens to the message (event) from AQ.— Parses the event content.

General Tab



Name No Name of the resource. The default is OracleBusinessEvent.

SharedConnection




Event Name No Name of the Business Event. For example,oracle.apps.per.api.person.update_person.

Always click Search Event to search for and select anOracle Business Event from the Oracle Business EventList even if you know the event name. By selecting anEvent Name from the list, certain backgroundoperations will be executed. The Business Event can bechecked in Oracle E-Business Suite.

There are two types of Business Events, Event andGroup. Only the Event type Business Events aresupported in this release.

34



Generate SQLScript

No After configuring the Oracle Business Event activity, clickGenerate SQL Script. The scripts to be generated are displayed inthe opened dialog. Click Generate and the following two SQLscripts are created in the TIBCO_HOME/bw6/bw/palettes/oracleebs/version/sql directory:

● ProcessName_ActivityName_EventName.sql

● ProcessName_ActivityName_EventName_undo.sql

Run the ProcessName_ActivityName_EventName.sql scriptbefore starting the process that this Oracle Business Event isadded to.

The script generated creates the necessaryinfrastructure that will allow the event to be availablefor use by the plug-in Oracle Business Event activitywithout having to manually configure this event inOracle E-Business Suite. This involves the creation of asubscription, an agent, and the required linking of theOracle business event to these entities. The script withthe _undo suffix will undo all the changes wrought bythe creation script, permitting a rollback of the changesto the database by this activity.

Description Tab


Event Attributes Tab

The attributes of an Oracle Business Event will be parsed from XML format and displayed in this tab.

Advanced Tab

The Advanced tab contains the following fields.


Select an existingagent?

No Select this check box to use an existing agent. If this check box isselected, the Agent Name, Queue Name, and Queue Table Namefields will gray out and the Select Agent button will beapplicable.

Agent Name No Enter a name for the Agent that you intend to create to receivemessages from Oracle Business Event System.

Queue Name No Enter a name for the Queue to receive messages from the Agent.

Queue TableName

No Enter a name for the Queue Table.

35



MultipleConsumer

No Select this check box, if you want the message to be consumed bymultiple subscribers. In this case, the message will be propagateusing the topic method. Otherwise, it will be propagated usingthe queue method.

Subscriber Name No Enter a name of the subscriber you want to consume the messageor click Select Subscriber to select an existing subscriber. Thisfield is applicable only when the Multiple Consumer check box isselected.

ValidateConfiguration

No Validate the configuration of the Agent Name, Queue Name, andQueue Table Name fields.

Sequence Key No This field can contain an XPath expression that specifies whichprocesses should run in order. Process instances with sequencingkeys that evaluate to the same value will be executed sequentiallyin the order the process instance was created.

See the TIBCO ActiveMatrix BusinessWorks documentation formore information.

Custom Job Id No This field can contain an XPath expression that specifies a customID for the process instance.

See the TIBCO ActiveMatrix BusinessWorks documentation formore information.

When specifying the Agent Name, Queue Name, Queue Table Name, and Subscriber Name, the textentered will be capitalized automatically.

36


When a Business Event is triggered in Oracle E-Business Suite, the plug-in will listen to the event.

● If you want this event message to be received by only one consumer, create a new set of Agent,Queue, and Queue Table for the subscription, or use an existing set of Agent, Queue, and QueueTable for the same Business Event.

— To create a new set of Agent, Queue, and Queue Table, give their names in their respectivefields and clear the Select an existing agent check box, as shown in the following figure. TheAgent, Queue, and Queue Table will be created in Oracle E-Business Suite after running theSQL script that will be generated according to the instructions provided in Generate SQL Script.

— To use an existing set of Agent, Queue, and Queue Table, select the Select an existing agentcheckbox. In this case, the Agent Name, Queue Name, and Queue Table Name fields will grayout and the Select Agent button will be applicable. Click Select Agent to select an existingAgent for the subscription, and the related Queue and Queue Table will be obtainedsimultaneously, as shown in the following figure.

37


● If you want the event message to be received by multiple consumers, you should first create a set ofAgent, Queue, and Queue Table for the subscription of event messages.

— To create a new set of Agent, Queue, and Queue Table for the subscription of event messages tobe received by multiple consumers, clear the Select an existing agent check box and give thenames for Agent, Queue, and Queue Table in their respective fields. Select the MultipleConsumer check box and give a name for the subscriber that will receive the event message inthe specific configuration, as shown in the following figure. The Agent, Queue, Queue Table,and Subscriber will be created in Oracle E-Business Suite after running the SQL script that willbe generated as shown in Generate SQL Script.

— To use this set of Agent, Queue, and Queue Table in other configurations, for example, in thefollowing figure, select the Select an existing agent check box and then choose this Agent. Therelated Queue and Queue Table will also be obtained simultaneously. Give a name for thesubscriber. It will be created in Oracle E-Business Suite after running the SQL script that will begenerated as shown in Generate SQL Script. This subscriber can then receive messages from thesame set of Agent, Queue, and Queue Table.

38


Conversations Tab

You can initiate the Conversation here. Click Add New Conversation to initiate multiple conversations.

For details about Conversations, see TIBCO ActiveMatrix BusinessWorks Samples.

Output Tab

The Output tab lists the output information for the activity.

39


Working with Sample Projects

Working through the sample projects helps you understand how to use the activities of TIBCOActiveMatrix BusinessWorks Plug-in for Oracle E-Business Suite in dealing with inbound andoutbound business objects between the TIBCO environment and Oracle E-Business Suite.

Importing the Sample ProjectsYou need to import the project to TIBCO Business Studio before running each project.

Procedure


2. Click File > Import.

3. In the Import window, expand the General folder and select Existing Studio Projects intoWorkspace. Click Next.

4. Click Browse next to the Select root directory field to locate the sample. Click Finish.The sample projects are located in the TIBCO_HOME\bw\palettes\oracleebs\6.0\examplesdirectory.

Result

The sample projects are imported to TIBCO Business Studio.

Running a BusinessWorks Process in Debug ModeBy running a BusinessWorks process in Debug mode, you can view the output of each includedactivity.

Procedure

1. Configure the process components of the project.a) In Project Explorer, expand the project directory, and click Module Descriptors.b) Click Components.

c) In the Components editor, click the Create Process Component icon to add the process youwant to run, or click to remove the process.

d) Save the project.

2. Run the process in Debug mode.a) Run > Debug Configurations.b) Expand BusinessWorks Application in the Debug Configurations window and click

BWApplication.c) Click Deselect All in the Applications tab and select the check box next to the project you want

to run.d) Click Debug.e) Click the Terminate icon in the Console view to stop the running process.

Result

You can view the output of each activity through the Job Data view in the Debug perspective.

40


Working with the Oracle API ActivityIn this example, the OracleAPI project demonstrates how to create the Inventory items and the BOM(Bill of Material) bills by Oracle PL/SQL Interface through the TIBCO ActiveMatrix BusinessWorksPlug-in for Oracle E-Business Suite.Two processes are preconfigured in the OracleAPI project, prepare_purchased_items process andsubassembly_item_and_bom_bill process respectively. In these two processes, BOM Bill, AssemblyItem, and Inventory Item are created, as shown in the following figure.

This example requires the use of the Vision Demo environment. It relies on the responsibility, users,and data in the demo installation.

This example is configured to work against the Oracle E-Business Suite Vision Demo Environment. Allthe inputs are valid under this environment.

Configuring and Running the prepare_purchased_items ProcessThe prepare_purchased_items process creates inventory items for Oracle E-Business Suite by using theOracle API activities.

Prerequisites

Before running the project, you need to importing the sample project to TIBCO Business Studio.

Procedure


41


2. Configure the Oracle E-Business Suite connection.a) From Project Explorer, expand OracleAPI > Resources > oracleapi.b) Double-click oebsconnectionResource.oebsconnectionResource.

The connection resources is opened in the editor.

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

3. Open the process.a) From Project Explorer, expand OracleAPI > Processes > oracleapi.b) Double-click EGO_ITEM_PUB.bwp.

The process is opened in the editor.

42


4. Configure the Oracle API activities.

In this example, there are five activities created, TIB_CPU, TIB_HD, TIB_RAM, TIB_RAM1, andTIB_MAINBOARD.

You can just create one activity by changing the value of the parameters to generatedifferent items, or you can create several activities at a time to generate different itemssimultaneously.

The following figure shows a sample of configuring the TIB_CPU activity.

As defined in Oracle Integration Repository, EGO_ITEM_PUB.PROCESS_ITEM is aconvenience wrapper to Process_Item. Use this API to create or update an item by passingonly the most important and/or commonly used item attributes.

43


5. Grant privilege to the plug-in user by the apps user and create the synonym EGO_ITEM_PUB forapps.EGO_ITEM_PUB under the plug-in user.a) Click Generate SQL Script in the General tab.

See Oracle API General Tab for more details.b) Execute the generate SQL script.

The following figure shows the command line about how to grant privilege and create thesynonym.

44


6. Configure the input of the Oracle API activities.

The following figure shows the TIB_CPU activity input screen.

The EGO_ITEM_PUB.PROCESS_ITEM API contains 74 parameters. In this example, you need toconfigure 17 parameters among them. The following table lists the type and input of eachparameter.

Parameter Type Input

P_API_VERSION NUMBER 1.0

P_INIT_MSG_LIST VARCHAR2 T

P_COMMIT VARCHAR2 T

P_TRANSACTION_TYPE VARCHAR2 CREATE

P_LANGUAGE_CODE VARCHAR2 US

P_TEMPLATE_ID NUMBER 259

P_TEMPLATE_NAME VARCHAR2 Purchased Item

P_ITEM_NUMBER VARCHAR2 TIB_CPU

P_SEGMENT1 VARCHAR2 TIB_CPU

P_ORGANIZATION_ID NUMBER 204

P_ORGANIZATION_CODE VARCHAR2 V1

P_CATALOG_STATUS_FLAG VARCHAR2 N

P_DESCRIPTION VARCHAR2 TIBCO EBS Plug-in CreateCPU item

P_PRIMARY_UOM_CODE VARCHAR2 Ea

P_INVENTORY_ITEM_STATUS_CODE VARCHAR2 Active

45



P_BOM_ENABLED_FLAG VARCHAR2 Y

P_ENG_ITEM_FLAG VARCHAR2 N

These parameters can be configured manually or automatically by defining a moduleproperties. For how to define module properties, see "Using Process and ModuleProperties" in TIBCO ActiveMatrix BusinessWorks Samples.

7. Run the process in Debug mode.

See Running a BusinessWorks Process in Debug Mode for details.

Result

● Output in TIBCO Business Studio: To check if the process runs successfully, you can check the valueof X_RETURN_STATUS in the Output tab in the Job Data view. "S" stands for success, and "E" standsfor error. The following figure shows a sample running result. In this example, the output for eachactivity is successful.

● Request result in Oracle E-Business Suite: Follow the procedure described in Checking Results afterRunning the prepare_purchased_items Process in order to check the result.

Checking Results after Running the prepare_purchased_items Process

After running the process in TIBCO Business Studio, you can verify the result in Oracle E-BusinessSuite.

Procedure

1. Log in to the Oracle E-Business Suite system with username MFG and password welcome.

46


2. Select Inventory > Items > Master Items to open Oracle Applications with the Navigator -Inventory dialog and the Organizations dialog displayed.

3. Select V1 organization from the Organization dialog, and click OK.

47


4. Search the created master items:a) Click the Find icon.b) In the Find Master Items (V1) dialog, specify the search filter in the Item field. For example, TIB_

%.c) Click Find.

The following figure shows the screen with notes on the three steps.

Result

The result is shown in the pop-up System Items dialog.

48


Configuring and Running the subassembly_item_and_bom_bill ProcessThe subassembly_item_and_bom_bill process creates the BOM bills for Oracle E-Business Suite byusing the Oracle API activities.

Prerequisites

Run the EGO_ITEM_PUB.bwp process successfully. See Configuring and Running theprepare_purchased_items Process for details.

Procedure

1. Open the process.a) From Project Explorer, expand OracleAPI > Processes > oracleapi.b) Double-click BOM_BO_PUB.bwp.


49


2. Configure the Oracle API activities.

In this example, there are two activities created, namely, the TIB_MainMachine activity andOracleAPI activity. The following figures show the configuration of these two activities.

As defined in Oracle Integration Repository, you can use theBOM_BO_PUB.PROCESS_BOM method for creating, updating, or deleting entities of asingle Structure/BOM. The method takes in a single Structure/BOM Header, all itsComponents, Revisions, Reference Designators, and Substitute Components.

3. Execute the BOM_BO_PUB.sql file using the apps user on the command line.

Because the BOM_BO_PUB.PROCESS_BOM procedure contains package types, you should useJPublisher to generate wrapper package first. In this example, there are two PL/SQL files generated,namely, BOM_BO_PUB.sql and BOM_BO_PUB_drop.sql. See Introduction to Oracle DatabaseJPublisher for more details.

50


4. Grant privilege to the plug-in user by the apps user and create the synonym TIB_BOM_BO_PUB forapps.TIB_BOM_BO_PUB under the plug-in user.a) Click Generate SQL Script in the General tab of the OracleAPI activity to generate the SQL

scripts.

See Oracle API General Tab for more details.b) Execute the script.

The following figure shows the command line about how to grant privilege and create thesynonym.

51


5. Configure the input of the Oracle API activities.

The following figures show examples of the TIB_MainMachine activity and OracleAPI activityinput screens respectively.

In this example, the value of the BOM_BILL_ITEM module property is TIB_MainMachine.It can be used automatically to configure inputs. For how to define module properties, see"Using Process and Module Properties" in TIBCO ActiveMatrix BusinessWorks Samples.

BOM_BO_PUB.PROCESS_BOM (Process Single Structure/BOM) has 21 parameters with thePL/SQL Table types and PL/SQL Record types defined in the package. The following table lists themain parameters and associated inputs of BOM Header, Revision, Components, ReferenceDesignators, and Substitute Components.

Parameter Input

P_BOM_HEADER_REC ASSEMBLY_ITEM_NAME TIB_MainMachine

ORGANIZATION_CODE V1

52


Parameter Input

TRANSACTION_TYPE CREATE

P_BOM_REVISION_TBL REVISION B

P_COMPONENT_TBL COMPONENT_ITEM_NAME TIB_CPU orTIB_HD orTIB_RAM orTIB_MAINBOARD

P_BOM_REF_DESIGNATOR_TBL REF_DESIGNATOR_COMMENT This is TIBCOCPU

P_BOM_SUB_COMPONENT_TBL COMPONENT_ITEM_NAME TIB_RAM

SUBSTITUTE_COMPONENT_NAME

TIB_RAM1



Result

● Output in TIBCO Business Studio: To check if the process runs successfully, you can check the valueof RETURN_STATUS in the Output tab in the Job Data view. "S" stands for success, and "E" stands forerror.

● Request result in Oracle E-Business Suite: Follow the procedure described in Checking Results afterRunning the subassembly_item_and_bom_bill Process in order to check the result.

Checking Results after Running the subassembly_item_and_bom_bill Process


Procedure

1. Log in to the Oracle E-Business Suite System with the username MFG and password welcome.

2. Select Manufacturing and Distribution Manager > Bills of Materials > Bills > Bills to open theNavigator - Manufacturing and Distribution Manager dialog.

53


3. Select V1 organization as show in the following figure, and click OK.

54


4. Click the button as shown in the following figure, enter TIB% in the Item field, and click Findto review the search result.

Result

The following figure shows the result in the Oracle E-Business Suite web system.

55


Working with the Custom API ActivityThe CustomAPI project demonstrates how to use the Custom API activity to call a PL/SQL procedurefrom the Oracle Database Dictionary.Custom API is used to execute the packages that are in Oracle Database Dictionary, but not in OracleIntegration Repository. Custom API is also used to execute customized packages that are created by thecustomer.


ACCOUNT_MGR Package

The ACCOUNT_MGR package is the test package provided by Oracle that is in Oracle DatabaseDictionary, but not in Oracle Integration Repository.

Configuring and Running the CustomAPI Project

Prerequisites


56


Procedure


2. Configure the Oracle E-Business Suite connection.a) From Project Explorer, expand CustomAPI > Resources > customapi.b) Double-click oebsconnectionResource.oebsconnectionResource.



3. Open the process.a) From Project Explorer, expand CustomAPI > Processes > customapi.b) Double-click Custom_package.bwp.


4. Configure the ACCOUNT_MGR package.

The following figure shows a sample configuration of the ACCOUNT_MGR package.

5. Grant privilege to the plug-in user by the apps user.a) Click Generate SQL Script in the General tab.

See Custom API General Tab for more details.b) Execute the script.

57


6. Configure the input of the Custom API activity.

The following table lists the inputs of the activity.


API_VERSION NUMBER 1.0

P_PARTY_ID NUMBER 4509



Result

To check if the process runs successfully, you can check the value of RETURN in the Output tab.

The following figure shows an example of the activity output.

Working with the Oracle Concurrent Program ActivityThe OracleCP project demonstrates how to use the Oracle Concurrent Program WICMLP to call JDBCto insert data into interface tables, and to submit a Concurrent Program request.


● WICMLP Concurrent Program on page 58● Configuring and Running the OracleCP Project

WICMLP Concurrent ProgramThe WICMLP Concurrent Program executes the open interface for work orders. It can be used either tocreate a new job or schedule, or update an existing job or schedule information. It processes the recordsfrom the following tables: WIP_JOB_SCHEDULE_INTERFACE, WIP_JOB_DTLS_INTERFACE.

Parameters

Name Type Required Displayed Description

Group ID FND_NUMBER15_REQUIRED Yes Yes Used to batch theinterface records.

58


Name Type Required Displayed Description

ValidationLevel

FND_NUMBER15 Yes No Indicates whatvalidation shouldbe performed.

Print Report WIP_SRS_YES_NO_MAND Yes Yes Indicates whetherthe report isprinted.

Open Interface Tables or Views

Name Direction Status Description

WIP_JOB_SCHEDULE_INTERFACE Inbound Active Contains the requests to createor modify discrete jobs orrepetitive schedules.

WIP_JOB_DTLS_INTERFACE Inbound Active Contains requests to add,delete, and modify materialand/or resource requirementsfor existing discrete jobs orrepetitive schedules.

Configuring and Running the OracleCP Project

In this example, the plug-in will perform the following tasks:

1. Import the Job Header.

The plug-in inserts the jobs (tib_job01 and tib_job02) into the interface tableWIP_JOB_SCHEDULE_INTERFACE.

The name of the jobs (tib_job01 and tib_job02) are defined in the process property WIP_input.

2. Submit the CP request.

The plug-in submits the CP request.

The request group ID (request_group_id) is defined in the process property WIP_input. Users cancreate new jobs with different request group IDs by changing the process property.

Prerequisites


Procedure


2. Configure the Oracle E-Business Suite connection.a) From Project Explorer, expand OracleCP > Resources > oraclecp.b) Double-click oebsconnectionResource.oebsconnectionResource.



59


3. Open the process.a) From Project Explorer, expand OracleCP > Processes > oraclecp.b) Double-click WICMLP.bwp.


4. Configure the WICMLP Concurrent Program.

You need to select a valid responsibility, and then select the user related to that responsibility.

The responsibility and the user selected in this example are valid in the Vision Demoenvironment.

The following figure shows a sample configuration of the WICMLP Concurrent Program.

5. Execute the SQL scripts.a) Click Generate SQL Script in the General tab to generate the SQL scripts.

See Oracle Concurrent Program General Tab for more details.b) Execute the SQL script on the command line to grant the insert privilege to the plug-in user for

the interface table.

60


6. Enter the data for the interface table and the concurrent request.

The following table lists the inputs of the WICMLP Concurrent Program.


Group_ID VARCHAR2 See process property WIP_input/Request_GroupID

Print_Report VARCHAR2 2

The following table lists the important inputs of the interface tables.


Group_ID NUMBER See process property WIP_input/Request_GroupID

SOURCE_CODE VARCHAR2 WICDOL

ORGANIZATION_ID NUMBER 207

CLASS_CODE VARCHAR2 Discrete

JOB_NAME VARCHAR2 See process property WIP_input/JobName1

DESCRIPTION VARCHAR2 See process property WIP_input/JobName1

ORGANIZATION_CODE VARCHAR2 M1

ROUTING_REVISION VARCHAR2 A

BOM_REVISION VARCHAR2 A

COMPLETION_SUBINVENTORY VARCHAR2 FGI

ALLOW_EXPLOSION VARCHAR2 Y

If you use the Concurrent Program activity to insert the data into the interface table, youneed to clear the Concurrent Request check box in the General tab. You may also use theTIBCO BusinessWorks JDBC activity or other tools to insert the records into the interfacetable.

The Group_ID input value should be identical within the example. Otherwise, an emptyrequest will be submitted.



61


Result

● Output in TIBCO Business Studio: To check if the process runs successfully, you can check the valueof STATUS in the Output tab in the Job Data view. "Normal" stands for success, and "Error" standsfor error. The following figure shows a sample running result. In this example, the output for theactivity is successful.

● Request result in Oracle E-Business Suite: Follow the procedure described in Checking Results afterRunning the OracleCP Project in order to check the result.

Checking Results after Running the OracleCP Project


Procedure

1. Log in to the Oracle E-Business Suite application with username MFG and password welcome.

62


2. Verify the concurrent request result in Oracle E-Business Suite.a) Select Manufacturing and Distribution Manager > Other > Concurrent to open the Find

Requests dialog.

The following figure shows the dialog.

b) Click Find to view the search result.

The following figure shows the sample search results.

63


64


3. Verify the job header in Oracle E-Business Suite.a) Close the Requests dialog. .b) In the Navigator - Manufacturing and Distribution Manager dialog, expand WIP > Discrete,

and then double-click Discrete Jobs.c) In the Organizations dialog, select the M1 organization that is defined in the input, and then click

OK.The following figure shows the opened Organizations dialog.

d) In the Find Discreet Jobs (M1) dialog, enter tib_job0% in the Find field, and then click Find.The following figure shows the Jobs dialog.

65


e) Click OK to view the Discrete Jobs details.The following figure shows the Discrete Jobs details.

Working with the Custom Concurrent Program ActivityThe CustomCP project demonstrates how to use the custom Concurrent Program INCOIN to call JDBCto insert data into interface tables, and to submit a Concurrent Program request.


● INCOIN Concurrent Program● Configuring and Running the CustomCP Project

66


INCOIN Concurrent ProgramYou can import items from any source into Oracle Inventory and Oracle Engineering using the INCOINItem Open Interface. With this interface, you can convert inventory items from another inventorysystem, migrate assembly and component items from a legacy manufacturing system, convertpurchased items from a custom purchasing system, and import new items from a product datamanagement package.

Open Interface Tables or Views

The INCOIN Concurrent Program contains 5 interface tables, as listed in the following table.

Name Description

INV.MTL_SYSTEMS_ITEM_INTERFACE Use this table for your new item numbers and allitem attributes. This is the main Item OpenInterface table. It may be the only table that youchoose to use.

INV.MTL_ITEM_REVISIONS_INTERFACE Use this table if you are importing revision detailsfor your new items. This table is used only forrevision information. It is not required.

INV.MTL_ITEM_CATEGORIES_INTERFACE Use this table to import item categoryassignments. It stores data about itemassignments to category sets, and categories to beimported into the Oracle InventoryMTL_ITEM_CATEGORIES table.

INV.MTL_DESC_ELEM_VAL_INTERFACE Use this table to describe elements that apply toyour item.

INV.MTL_DESC_ELEM_VAL_INTERFACE Use this table to record error messages for failedrecords in the interface table.

The open interface is not exposed in Oracle E-Business Suite Integration Repository, therefore you mustgo through the plug-in Custom Concurrent Program activity to access it. You need to implement thisactivity using the standard parameters for calling FND_REQUEST.SUBMIT_REQUEST. So do not putthe arguments’ name for Concurrent Program and replace them with argument number.

Configuring and Running the CustomCP Project

In this example, the plug-in will perform the following tasks:

1. Import the inventory items.

The plug-in inserts the inventory items into the interface tableINV.MTL_SYSTEMS_ITEM_INTERFACE.

This example only uses the INV.MTL_SYSTEMS_ITEM_INTERFACE table to import theitems.

2. Submit the CP request.

Procedure

1. Open the CustomCP project in TIBCO Business Studio.

67


2. Configure the Oracle E-Business Suite connection.


3. Configure the INCOIN Concurrent Program.

The following figure shows a sample of configuring the INCOIN Concurrent Program.

4. Configure the interface table.

In this example, the interface table has already been configured. Therefore you may skipthis step.

a) Click the Interface Table Configuration buttonb) In the Interface Table Configuration dialog, click Add to add an interface table.c) Select INV > MTL_SYSTEM_ITEMS_INTERFACE, and click OK.d) In the Interface Table Configuration dialog, review the selected table, and click Apply.

5. Execute the SQL scripts.a) Click Generate SQL Script in the General tab to generate the SQL scripts.

See Custom Concurrent Program General Tab for more details.b) Execute the SQL script on the command line to grant the insert privilege to the plug-in user for

the interface table.

68


6. Enter the data for the interface table and the concurrent request.

The following table lists the inputs of the INCOIN Concurrent Program.


argument1 VARCHAR2 204





argument6 VARCHAR2 See process property INCOIN_input/arg6_set_process_id


The following table lists the important inputs of the interface tables.


ORGANIZATION_ID NUMBER 204

DESCRIPTION VARCHAR2 See process propertyINCOIN_input/item_name

SEGMENT1 VARCHAR2 See process propertyINCOIN_input/item_name

ATTRIBUTE1 VARCHAR2 2001

CUSTOMER_ORDER_FLAG VARCHAR2 Y

CUSTOMER_ORDER_ENABLED_FLAG VARCHAR2 Y

PROCESS_FLAG NUMBER 1

ORGANIZATION_CODE VARCHAR2 V1

TRANSACTION_TYPE VARCHAR2 CREATE

SET_PROCESS_ID NUMBER See process propertyINCOIN_input/arg6_set_process_id

69


7. Execute the following SQL script to find the Concurrent Program parameters:

SELECT cp.concurrent_program_name CP_Name, -- The Concurrent Program namedfcu.end_user_column_name Column_name, -- The real argument name lv.meaning data_type, -- The data type of argumentffv.maximum_size, -- The lenght of the argumentdfcu.required_flag, -- The argument required or notdfcu.display_flag, -- The argument displayed or not on Oracle Form dfcu.default_value, -- The default value of the argumentdfcu.column_seq_num -- The argument sequence number FROM fnd_concurrent_programs_vl cp LEFT OUTER JOIN fnd_descr_flex_col_usage_vl dfcu ON dfcu.descriptive_flexfield_name ='$SRS$.'||cp.concurrent_program_name LEFT OUTER JOIN fnd_flex_value_sets ffv ON ffv.flex_value_set_id = dfcu.flex_value_set_id LEFT OUTER JOIN fnd_lookup_values_vl lv ON lv.lookup_code = ffv.format_type AND lv.lookup_type = 'FIELD_TYPE'AND lv.enabled_flag = 'Y'AND lv.security_group_id = 0AND lv.view_application_id = 0WHERE cp.CONCURRENT_PROGRAM_NAME LIKE UPPER('&CONC_PROG_NAME' || '%')ORDER BY cp.concurrent_program_name, dfcu.column_seq_num;

You can execute the SQL script in one of the following ways:

● Execute the SQL script on the command line by the apps user.● Execute the SQL script with Oracle SQL Developer.

The following table shows the result of the INCOIN Concurrent Program parameters.

No CP_NAME ARGUMENT COLUMN_NAME DATA_TYPE

MAXIMUM_SIZE

1 INCOIN argument1 p_org_id Number 15

2 INCOIN argument2 p_all_org Char 80

3 INCOIN argument3 p_val_item_flag Char 80

4 INCOIN argument4 p_pro_item_flag Char 80

5 INCOIN argument5 p_del_rec_flag Char 80

6 INCOIN argument6 p_xset_id Number 15

7 INCOIN argument7 p_run_mode Char 1



70


Result

● Output in TIBCO Business Studio: To check if the process runs successfully, you can check theOutput tab in the Job Data view. The following figure shows a sample running result.

● Request result in Oracle E-Business Suite: Follow the procedure described in Checking Results afterRunning the CustomCP Project in order to check the result.

Checking Results after Running the CustomCP Project


Procedure

1. Log in to the Oracle E-Business Suite application with username MFG and password welcome.

71


2. Verify the concurrent request result in Oracle E-Business Suite.a) Select Manufacturing and Distribution Manager > Inventory > Requests to open the Find

Requests dialog.The following figure shows the dialog.

b) Click Find to view the search result.The following figure shows the sample search results.

72


3. Verify the inventory items in Oracle E-Business Suite.a) Select Inventory > Items > Master Items.b) In the Organizations dialog, select the V1 organization that is defined in input, and then click

OK.The following figure shows the opened Organizations dialog.

c) In the Item field in the Find Master Items (V1) dialog, enter TIBCO%, and click Find.The following figure shows the Jobs dialog.

73


d) In the Enter Reduction Criteria for Long-List dialog, click OK to view the search details.The following figure shows the master item details.

74


Working with the Oracle Business Event ActivityThe BusinessEvent project demonstrates how to use the Oracle Business Eventoracle.apps.per.api.person.update_person to listen to the update of a person’s information from OracleAdvanced Queue.

Prerequisites


Procedure

1. Review the business event.a) Log in to the Oracle E-Business Suite web site as the sysadmin user.b) Select Workflow Administrator Web Applications > Administrator Workflow > Business

Events.c) 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.

75


2. Enable the business event.

a) Click the icon to update the business event.b) In the Status list in the Update Event panel, select Enabled to enable the business events.c) Click Apply.The following figure shows the enabled business event.


4. Configure the Oracle E-Business Suite connection.a) From Project Explorer, expand BusinessEvent > Resources > businessevent.b) Double-click oebsconnectionResource.oebsconnectionResource.



76


5. Open the process.a) From Project Explorer, expand BusinessEvent > Processes > businessevent.b) Double-click BusinessEvent.bwp.


77


6. Configure the Oracle Business Event activity.a) Select the activity.

Click Search Event in the General tab, select the enabled business event, and then click OK. Seethe following figure.

b) Configure the Agent, Queue, and Queue Table.

Click the Advanced tab as shown in the following figure. In the Advanced tab, add suffix _PERto the value of the Agent Name, Queue Name, and Queue Table Name fields. Click Apply.

c) Click Generate SQL Script in the General tab to generate the SQL scripts.See Oracle Business Event General Tab for more details.

d) Execute the SQL script on the command line to grant the insert privilege to the plug-in user forthe interface table.

78


7. Trigger an event in Oracle E-Business Suite.a) Log in to the Oracle E-Business Suite application as the Operations user. The default password

is welcome.b) Select Human Resources, Vision Enterprises > People > Enter and Maintain.c) 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.d) Select Alexander, and click OK to review the person’s information.e) 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 person information of Alexander.

79


8. Get the event attributes in TIBCO Business Studio.

Click Get Event Attributes in the Event Attributes tab to get the event attributes.

If you do not generate or execute the SQL script, an error JAM-143: Queue must bespecified will occur.

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

The following figure shows the event attributes.

80


9. Run the process in Debug mode and review the output for the information you updated.


The following figure shows the activity output.

If you want to use thebw.application.job.flowlimit.application_name.application VM argumentwhen running the activity, you need to 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 Argumentstab on the right, then add -DisFlowlimitForOebs=true in the VM arguments textbox.

● Runtime: Add isFlowlimitForOebs=true to the config.ini configuration file,which is located in the following directory: TIBCO_HOME\bw\domains\domain_name\appnodes\appspace_name\appnode_name\

81


Oracle API and Custom API Comparison

The supported Oracle E-Business Suite configuration is different between an Oracle API and a CustomAPI.

In TIBCO Business Studio, Oracle API and Custom API use different palettes.

● Oracle API loads the PL/SQL package and procedure parameters information from OracleIntegration Repository.

● Custom API loads the PL/SQL package or procedure parameters information from Oracle DatabaseDictionary.

82


Oracle Concurrent Program and Custom ConcurrentProgram Comparison

The configuration and type of concurrent programs are different between an Oracle API and a CustomAPI.

The differences between Oracle Concurrent Program and Custom Concurrent Program are listed asfollows:

● Configuration: In TIBCO Business Studio, Oracle Concurrent Program and Custom ConcurrentProgram use difference palettes.

● Oracle Concurrent Program loads the Inbound Interface Tables or Views from Oracle IntegrationRepository.

● Custom Concurrent Program requires you to select Interface Tables or Views from the databasemanually.

● Concurrent Program

There are two types of Concurrent Programs in Oracle Integration Repository:

● Standard Request Submission (SRS) Concurrent Program● non-SRS Concurrent Program

The concurrent program activities supported by each activity is different:

● Oracle Concurrent Program only supports the SRS Concurrent Program.● Custom Concurrent Program supports both the SRS Concurrent Program and non-SRS

Concurrent Program.

See SRS Concurrent Program and Non-SRS Concurrent Program for more details about the differentbetween the two types of Concurrent Programs and how to use them.

SRS Concurrent Program and Non-SRS Concurrent ProgramDepending on the approach to submit a request in Oracle E-Business Suite, two types of ConcurrentPrograms are available in Oracle Integration Repository.

● Standard Request Submission (SRS) is an Oracle E-Business Suite feature that allows you to select andrun your Concurrent Programs from a single, standard form (Submit Request) or window (ScheduleRequest). Requests to run Concurrent Programs are called concurrent requests.

● Non-Standard Request Submission is not available through Standard Request Submission. You can runa non-SRS Concurrent Program by submitting a non-standard request form.

This section explains how to check the type and parameters of a Concurrent Program, anddemonstrates the right and wrong activity configuration when invoking a sample non-SRS ConcurrentProgram, GLBBSU. If you are unfamiliar with the concepts, it is recommended that you read throughthe following topics. If you have already had some knowledge about these concepts, you can read only Using the Custom Concurrent Program Activity for the right configuration using the plug-in.

● Sample Non-SRS Concurrent Program: GLBBSU● Checking the Type and Parameters of a Concurrent Program on page 84● Submitting a Request Using Oracle E-Business Suite Client● Submitting a Request Using Plug-in Activities

83


Sample Non-SRS Concurrent Program: GLBBSUGLBBSU is a non-SRS Concurrent Program, which means you cannot run the program by submitting astandard request form provided by Oracle E-Business Suite. To run the program, you have to submit anon-standard request form.

The details of GLBBSU is shown in the following figure.

You can view the details of a Concurrent Program in Oracle Integration Repository available withOracle E-Business Suite. See Introduction to Oracle Integration Repository for details.

Checking the Type and Parameters of a Concurrent ProgramSome parameters for a non-SRS Concurrent Program are not visible from both TIBCO Business Studioand Oracle Integration Repository. To run such non-SRS Concurrent Programs, it is recommended thatyou use the Custom Concurrent Program activity. You should validate the parameters before startingthe activity.

Checking the Type of a Concurrent Program

Check the type of a Concurrent Program before you make decision on which activity to use. For an SRSConcurrent Program, you can use either the Oracle Concurrent Program activity or the Custom

84


Concurrent Program activity. For a non-SRS Concurrent Program, you can only use the CustomConcurrent Program activity.

Procedure

1. Log on to Oracle SQL*Plus.On the command line, type sqlplus. Enter the Oracle Database system administrator's usernameand password.

2. Run the SQL query for the Concurrent Program of your interest.For example:

select CONCURRENT_PROGRAM_ID, CONCURRENT_PROGRAM_NAME,

SRS_FLAG,ENABLED_FLAG,USER_CONCURRENT_PROGRAM_NAME from

fnd_concurrent_programs_vl where concurrent_program_name='GLBBSU'

Y stands for SRS Concurrent Program, and N stands for non-SRS Concurrent Program.

Finding the Parameters for a Concurrent Program

Check the type of a Concurrent Program before you make decision on which activity to use.

Procedure

1. Log on to Oracle SQL*Plus.

On the command line, type sqlplus . Enter the Oracle Database system administrator's usernameand password.

2. Run the SQL query for the Concurrent Program of your interest.For example:SELECT cp.concurrent_program_name CP_Name, -- The Concurrent Program namedfcu.end_user_column_name Column_name, -- The real argument name lv.meaning data_type, -- The data type of argumentffv.maximum_size, -- The lenght of the argumentdfcu.required_flag, -- The argument required or notdfcu.display_flag, -- The argument displayed or not on Oracle Form dfcu.default_value, -- The default value of the argumentdfcu.column_seq_num -- The argument sequence number FROM fnd_concurrent_programs_vl cp LEFT OUTER JOIN fnd_descr_flex_col_usage_vl dfcu ON dfcu.descriptive_flexfield_name ='$SRS$.'||cp.concurrent_program_name LEFT OUTER JOIN fnd_flex_value_sets ffv ON ffv.flex_value_set_id = dfcu.flex_value_set_id LEFT OUTER JOIN fnd_lookup_values_vl lv ON lv.lookup_code = ffv.format_type AND lv.lookup_type = 'FIELD_TYPE'AND lv.enabled_flag = 'Y'AND lv.security_group_id = 0AND lv.view_application_id = 0WHERE cp.CONCURRENT_PROGRAM_NAME = 'GLBBSU'ORDER BY cp.concurrent_program_name, dfcu.column_seq_num;

85


Submitting a Request Using Oracle E-Business Suite ClientYou can run a non-SRS Concurrent Program by submitting a non-standard request form. Non-StandardRequest Submission is not available through Standard Request Submission.

Submitting a Standard Form

This task shows the issues encountered when submitting a standard request form for the GLBBSUConcurrent Program.

Procedure

1. Log on to Oracle E-Business Suite Client as the OPERATIONS user.

2. Select General Ledger, Vision Operations (USA) > Other > Requests.

3. In Oracle Applications, click Submit a New Request in the Find Requests dialog.

4. In the Submit a New Request dialog, click Single Request, and click OK.

86


5. In the Submit Request dialog, click the browse button next to the Name field.The Reports dialog is displayed as shown in the following figure. But since GLBBSU (UploadBudget Amounts) is not a non-SRS Concurrent Program, you cannot find it in the listed programs.

Submitting a Non-Standard Request Form

This task shows how to submit a non-standard request form for the GLBBSU Concurrent Program.

Procedure

1. Log on to Oracle E-Business Suite Client as the OPERATIONS user.

2. Select General Ledger, Vision Operations (USA) > Other > Requests.

3. In Oracle Applications, close the Find Requests dialog.

87


4. In the Navigator dialog, expand Budgets > Enter > Upload, and double click Upload to show theUpload Budgets window.

88


5. Enter the input for this Concurrent Program. The following figure shows an input sample.

The input is different from the parameters shown in Oracle Integration Repository.

6. Click Upload to submit the request.

Result

In Oracle Applications, click View > Requests from the main menu. In the Find Requests dialog,specify the search criteria and click Find.

The following figure shows the request detail in Oracle E-Business Suite Client.

89


Submitting a Request Using Plug-in ActivitiesYou need to use the Custom Concurrent Program activity when running a non-SRS ConcurrentProgram. You can use the Oracle Concurrent Program activity, but it will not execute the requestsuccessfully and will result in an error.

Using the Oracle Concurrent Program Activity

This task shows the configuration of the required input of GLBBSU in the Custom Concurrent Programactivity and the running results.

Prerequisites

1. Create a project in TIBCO Business Studio.

2. Create a process in the project.

Procedure

1. Add the Oracle Concurrent Program activity to the process.

90


2. Configure the activity and its input.

The following figure shows a sample input configuration.


91


Result

● Output in TIBCO Business Studio: The following figure shows the output of the activity. TheSTATUS field is Error, indicating that the process runs with an error, and the request is executedwith an error.

● Request results in Oracle E-Business Suite: The following figure shows the request detail in OracleE-Business Suite.

92


Using the Custom Concurrent Program Activity

This task shows the configuration of the required input of GLBBSU in the Custom Concurrent Programactivity and the running results.

Prerequisites

1. Create a project in TIBCO Business Studio.

2. Create a process in the project.

Procedure

1. Add the Custom Concurrent Program activity to the process.

2. Configure the Custom Concurrent Program activity, in particular, the input of the activity.

GLBBSU requires 7 arguments. For details about the type and parameters, see Checking the Typeand Parameters of a Concurrent Program.

The following figure shows a sample input configuration.


93


Result

● Output in TIBCO Business Studio: The STATUS field is Warning, indicating that the process runswithout an error, and the request is executed successfully with warnings.

● Request results in Oracle E-Business Suite: The following figure shows the request detail in OracleE-Business Suite.

94


Introduction to Oracle Integration Repository

The Oracle Integration Repository is a compilation of information about the service endpoints exposedby the Oracle E-Business Suite of applications. It provides a complete catalog of Oracle E-BusinessSuite's business service interfaces.

Searching for a Business Service Interface in Oracle Integration RepositoryYou can view the details of a business service interface in Oracle Integration Repository

Procedure

1. Log on to Oracle E-Business Suite using a system administrator’s account.

95


2. Expand Integrated SOA Gateway > Integration Repository in the Main Menu panel.

The welcome page of Oracle Integration Repository is displayed, as shown in the following figure.

96


3. Click Search in the upper right corner to show the search page.

97


4. Enter the Internal Name of a business service interface, select the Interface Type from the list, andthen click Go to show its details.

For example, enter the Oracle API Package name BOM_BO_PUB in the Internal Name field. In theInterface Type field, select PL/SQL from the list. Click Go. The API Package BOM_BO_PUB will befound in Oracle E-Business Suite.

98


5. Click the name of the business service interface to show its details.

99


Introduction to Oracle Database JPublisher

Oracle Database JPublisher is maintained by Oracle, and the packaging and usage are subject to change.If any of the following information is no longer valid, check with Oracle Support or contact TIBCOSupport for more information.

When supplied with the correct parameters, JPublisher generates two types of output:

● It generates a PL/SQL script that exposes the custom data types, stored procedures and functionscontained in a package by creating SQL types, and a wrapper package that permits the internals ofthe original package to be more accessible and callable.

● It generates Java classes which utilize the generated wrapper PL/SQL scripts. These wrapper Javaclasses model the database objects and can be used programmatically to execute the contents of theselected package.

Wrapper and Non-Wrapper Data TypesThe wrapper and non-wrapper data types are different.

Wrapper Data Types

● PLSQL BOOLEAN● TABLE● PLSQL TABLE● RECORD● VARRAY

The following code block shows an example that uses some wrapper data types:CREATE OR REPLACE PACKAGE WRAPPER_DATA_TYPE_PKGASTYPE PER_INFO_RECORD IS RECORD (FIRST_NAME VARCHAR2 (20), LAST_NAME VARCHAR2 (20), SEX VARCHAR2 (1)), AGE NUMBER (3), PER_ID NUMBER)TYPE PER_TAB IS table of PER_INFO_RECORD;PROCEDURE CREATE_PERSONS (P_PERS PER_TAB, P_COMMIT BOOLEAN);PROCEDURE CREATE_PERSON (P_PER PER_INFO_RECORD, P_STATUS VARCHAR2);END;

In this example, P_COMMIT is PLSQL BOOLEAN type, P_PERS is TABLE type, and P_PER is PLSQLRECORD type.

Non-Wrapper Data Types

● VARCHAR2● LONG● CHAR● CLOB● NUMBER● INTEGER● DATE● FLOAT

100


● BINARY_INTEGER● PLS_INTEGERThe difference between the wrapper and non-wrapper data type is shown in the following diagram:

Oracle JPublisher Usage in the Plug-inTIBCO ActiveMatrix BusinessWorks Plug-in for Oracle E-Business Suite relies on Oracle JPublisher togenerate PL/SQL scripts in some instances where programmatically accessing the database objects isnot possible.

TIBCO ActiveMatrix BusinessWorks Plug-in for Oracle E-Business Suite does not need the generatedJava classes, because the plug-in utilizes a general framework that allows the invocation of the storedpackages’ procedures.

In particular, Oracle E-Business Suite APIs that require data structures defined within the API packagesrequire the wrappers generated by Oracle JPublisher, because these data structure definitions are notaccessible outside of the package.

Using the wrappers, TIBCO ActiveMatrix BusinessWorks Plug-in for Oracle E-Business Suite can thusinvoke the procedures contained inside the Oracle E-Business Suite APIs packages.

Only Oracle E-Business Suite APIs that contain complex types such as table types and record typesrequire Oracle JPublisher PL/SQL wrappers.

Installing JPublisherOracle JPublisher is maintained by Oracle, and the packaging and usage are subject to change. If any ofthe information conveyed here is no longer valid, check with Oracle Support or contact TIBCO Supportfor more information.

Prerequisites

Ensure that your system meets the following requirements:

● Java JDK 1.5 or higher is installed on your system.● The bin directory is in the path. On Windows systems, you need to verify that Java is accessible by

typing java –version in a command line window. Although it is not required, it is recommendedthat you verify the Javac is accessible in order to reduce the chance of errors.

Procedure

1. Download a supported version of Oracle JPublisher from the Oracle web site: http://www.oracle.com/technetwork/database/features/jdbc/index-091264.html.Check whether the version of your JPublisher is supported. See Supported JPublisher Versions fordetails.

101


http://www.oracle.com/technetwork/database/features/jdbc/index-091264.html


2. Extract the package to a local folder in your system.

3. Reference runtime12.jar, translator.jar, and the JDBC library in the Java classpath.

● On Microsoft Windows platforms:

1. Select Start > Control Panel > System.

2. In the System Properties dialog, click the Advanced tab, and then click the EnvironmentVariables button in this tab.

3. In the System variables area, select CLASSPATH and click the Edit button.

4. Add runtime12.jar, translator.jar, and the JDBC library to the Variable value field. Click theOK button.

● On Windows platforms using console window:

Execute the following command: set CLASSPATH=JPUB_LIB_DIR/runtime12.jar;JPUB_LIB_DIR/translator.jar;JPUB_LIB_DIR/ojdbc5.jar

● On UNIX platforms:

Execute the following command: export CLASSPATH=JPUB_LIB_DIR/runtime12.jar:JPUB_LIB_DIR/translator.jar:JPUB_LIB_DIR/ojdbc5.jar

It is recommended that you put the JDBC library in the same folder as the runtime12.jarand translator.jar directory.

Supported Versions

The following versions of Oracle JPublisher from Oracle web site can generate compatible PL/SQLwrappers for the plug-in:

● Oracle JPublisher 10.2● Oracle JPublisher 10.1.0.3● Oracle JPublisher 9.2.0.1

And you can make the Oracle JPublisher 11.x shipped with Oracle database 11.x by copying theruntime12.jar, and translator.jar from ORACLE_HOME/oc4j/sqlj/lib directory to theBW_HOMEbw/palettes/oracleebs/6.0/examples/jpublisher/lib directory.

Oracle JPublisher requires JDBC libraries, which can be downloaded from the Oracle web site http://www.oracle.com/technetwork/database/features/jdbc/index-091264.html.

The following are examples of the names of these JDBC Java libraries:

● ojdbc14.jar

● ojdbc5.jar

● ojdbc6.jar

JDBC Java library ojdbc14.jar is for JPublisher 9.2.0.1, 10.1.x, and 10.2.x; ojdbc5.jar and ojdbc6.jarare for JPublisher 11.x.

102




Using JPublisherOracle Database JPublisher is a command line utility that accepts a few parameters for specifying theconnection, user, and script file details. Before running the utility, you may need to grant the privilegesto the desired package.

JPublisher: Granting the Privilege for the Running AccountThe execution of Oracle JPublisher requires the logged-in user to have access to the package, and alldatabase objects related to the package for which the wrapper is being generated from.The apps user typically has access to all the packages. It is highly recommended that the apps user isused to execute Oracle JPublisher for script generation. If the apps user cannot be used directly,privilege to the desired package should be granted to the plug-in user by the apps user.

Prerequisites

Conduct an exhaustive exercise to identify all the procedures, related packages, tables, and other itemsused by the package for which the wrapper is being generated from.

Procedure

● Execute the following SQL statements.GRANT EXECUTE ON BOM_BO_PUB TO username;CREATE SYNONYM BOM_BO_PUB FOR APPS.BOM_BO_PUB;

Tables, other packages and the tables they may reference, and other objects accessed byany dependent packages will also need to be accessible by the plug-in user to run thisscript. As such, it is advisable to run this script using the apps user once, and privilegesneed not be granted to the plug-in user.

Running JPublisher

Procedure

● Open a command line window and execute the following example command:java oracle.jpub.Main -user=apps/apps -url=jdbc:oracle:thin:@10.105.176.40:1521:VIS -sql=BOM_BO_PUB -plsqlpackage=TIB_BOM_BO_PUB -plsqlmap=always -dir=java/BOM_BO_PUB -plsqlfile=sql/BOM_BO_PUB/BOM_BO_PUB.sql

Execution may take some time depending on the size of the API package specified and thedatabase server resources available (a few minutes for each PL/SQL wrapper). Duringexecution, JPublisher will list the database types that have been wrapped.

JPublisher may attempt to compile the Java classes generated by running the Javacompiler. This step may fail because -plsqlmap=always was selected. However, it doesnot affect the generation of the PL/SQL wrappers themselves.

Result

Once JPublisher has executed successfully, two SQL scripts are generated, including a wrapper file anda file undoing the wrapper changes. See JPublisher Wrapper Detailsfor more details.

103


JPublisher Parameters

Parameter Description

-user Specifies the credentials to use to log in to the database to extract the APIinformation. Note that this login will need to have all the privileges to theAPI packages as well as Oracle’s data dictionary tables. It is recommendedthat the apps user be used here to avoid any privilege issues.

-url Contains the JDBC connection string used to connect to the database.Typically, the format is jdbc:oracle:thin:@[Database Server]:[Port]:[SID]. For example, jdbc:oracle:thin:@oracle-ebs-server:1521:VIS.

-plsqlmap Initializes Oracle JPublisher to generate the PL/SQL script wrapper. Its valueis always. For example, -plsqlmap=always.

-sql Specifies the package name in Oracle database which should be used togenerate the PL/SQL wrapper.

-plsqlpackage Specifies the name of the generated wrapper package which is user-defined.It is recommended that the TIB_ be used as a prefix for the API packagename. For example, if -sql=BOM_BO_PUB, then -plsqlpackage=TIB_BOM_BO_PUB.

-plsqlfile Specifies the filename of the generated PL/SQL wrapper. It is recommendedthat you use either the SQL package name or the PLS package name (forexample, BOM_BO_PUB or TIB_BOM_BO_PUB) so that the filename can beused to identify the package referenced by the PL/SQL wrapper.

-dir Specifies the directory to save the PL/SQL wrapper file.

JPublisher Wrapper DetailsOnce JPublisher has executed successfully, two PL/SQL files will be generated. One is the wrapper filewhich exposes data structure types and stored procedures for execution through JDBC. The other filegenerated with the drop suffix contains scripts to undo the changes of the wrapper, allowing thedatabase to return to its prior state.

For example, the files generated by JPublisher using the commands in Running JPublisherare:

● BOM_BO_PUB.sql

● BOM_BO_PUB_drop.sql

Inspection of the generated wrapper file shows that package types are mapped to general SQL types,and package procedures and functions are mapped to identical procedures in the generated wrapperpackage. The SQL type and wrapper package are accessible by the Oracle E-Business Suite apps user orusers with equivalent privileges.

It is possible to edit this file to restrict the access of certain procedures and types so that the entirepackage content need not be exposed. However, this will require extensive knowledge of PL/SQL, theAPI package, and API and type relationships for the particular API that is being configured. It isrecommended that the unmodified file is run in its entirety.

Using an SQL execution tool such as Oracle SQL Developer, login as the plug-in user if the privilege tothe package has been granted, or simply use the apps user and execute this script.

104


Execution of the wrapper files may require a SQL tool that can accommodate very long individuallines. It is recommended that Oracle SQL Developer be used to execute this script, since SQL*Plus mayencounter problems executing lines that are very long, even after increasing the line size.

105


Updating the Oracle JDBC Library or Oracle AdvancedQueuing Library

To update these library files, you need to manually replace the .jar library files in the installeddirectories of the plug-in.

Procedure

1. Exit TIBCO Business Studio.

2. Copy the .jar library files to both of the following directories:

● BW_HOME/palettes/oracleebs/version/design/plugins

● BW_HOME/palettes/oracleebs/version/runtime/oracleebs.thirdpart.runtime/

runtime/plugins/com.tibco.bw.palette.oracleebs.thirdpart

3. Rename the files in both directories as follows:

● Oracle JDBC library: ojdbc.jar

● Oracle Advanced Queuing library: aqapi.jar

106


Error Messages

The error messages for the plug-in are listed with corresponding description and resolution.

TIBCO-BW-PALETTE-ORACLEEBS-510001: JMS Exception: %1

Role errorRole

Category BW-Plug-in

Description A JMS exception occurred. The diagnosis depends on the error messagereturned.

Resolution Check the JMS server status.

TIBCO-BW-PALETTE-ORACLEEBS-510002: Failed to create connection pool: %1

Role errorRole

Category BW-Plug-in

Description The creation of the connection pool failed.

Resolution Check the Oracle connection parameters.

TIBCO-BW-PALETTE-ORACLEEBS-510010: SQL Exception: %1

Role errorRole

Category BW-Plug-in

Description A SQL execution failed.

Resolution Ensure that you are connecting to the right database.

TIBCO-BW-PALETTE-ORACLEEBS-510011: Timeout Exception: %1

Role errorRole

Category BW-Plug-in

Description A SQL execution timeout occurs.

Resolution Ensure that you are connecting to the right database.

TIBCO-BW-PALETTE-ORACLEEBS-510012: Load Resource Exception: %1

Role errorRole

107


Category BW-Plug-in

Description Cannot find the Shared Resource name. The Oracle Connection cannot belocated.

Resolution Ensure that you select a connection resource for the activity.

TIBCO-BW-PALETTE-ORACLEEBS-510013: Exception: %1

Role errorRole

Category BW-Plug-in

Description General exception.

Resolution Inspect the error message to diagnose the issue.

TIBCO-BW-PALETTE-ORACLEEBS-510016: Advanced Queue connection failed: %1

Role errorRole

Category BW-Plug-in

Description The connection to Oracle Advanced Queue failed.

Resolution Check the connection parameters and the Oracle database.

TIBCO-BW-PALETTE-ORACLEEBS-510018: PLSQL API or Concurrent Program Execute Error:

%1

Role errorRole

Category BW-Plug-in

Description An error occurred when executing SQL commands submitted by PLSQL APIor Concurrent Program.

Resolution Inspect the error message to diagnose the error.

TIBCO-BW-PALETTE-ORACLEEBS-510019: Connection to AQ server failed. Can't get

connection.

Role errorRole

Category BW-Plugin

Description The connection to Oracle Advanced Queue failed.

Resolution Check the connection parameters and the Oracle Database.

108


Log Table Structure

Oracle E-Business Suite keeps a record of the plug-in activities in the TIB_BW_EBS_LOG table.

The structure of the TIB_BW_EBS_LOG table is shown in the following table.

The common_all SQL script contains the create script for the Log Table. It also contains the commonprocedure for all records into the Log Table.

Column Names Data Type Null?DefaultValue Description

ID NUMBER No An auto incrementsequence ID.

PROCESS_ID VARCHAR2 (20) Yes Sequence ID; Createdautomatically for eachprocess by TIBCOBusinessWorks.

NAME VARCHAR2 (100) No The name of the API/Wrapper procedure,Concurrent Program,or business event.

TYPE VARCHAR2 (50) No The type of theactivity configured inTIBCO BusinessStudio.

REQUEST_ID VARCHAR2 (20) Yes The ID of the requestto run a ConcurrentProgram in Oracle E-Business Suite.

LOG_TIME DATE Yes SYSDATE The time when theprocess is recorded.

STATUS VARCHAR2 (50) No The status of theprocess: Success,Error, or Ignore.

EVENT_QUEUE VARCHAR2 (50) Yes This field applies toOracle Business Eventonly. The name of theQueue that receivedthe message from theEvent Agent.

109


Column Names Data Type Null?DefaultValue Description

EVENT_AGENT VARCHAR2 (50) Yes This field applies toOracle Business Eventonly. The name of theAgent that receivedthe message from theOracle Business EventSystem.

EVENT_SUBSCRIBER VARCHAR2 (50) Yes This field applies toOracle Business Eventonly. The name of theSubscriber thatconsumed themessage.

EVENT_DATA APPS.WF_EVENT_T

Yes This field applies toOracle Business Eventonly. The user data ofthe business eventmessage. For moreinformation, refer totheAPPS.WF_EVENT_Tdata type definition inOracle Database.

DESCRIPTION VARCHAR2 (4000) Yes The simple formatoutput result forOracle API, CustomAPI, Oracle CP, andCustom CP.

110


Date post:	12-Mar-2020
Category:	Documents
Upload:	others
View:	3 times
Download:	0 times

TIBCO ActiveMatrix BusinessWorks Plug-in for Oracle E ......for Oracle E-Business Suite User's Guide...

Documents