tibco adapter for oracle applications examples … following documents form the tibco adapter for...

TIBCO Adapter™ for Oracle Applications

Examples GuideSoftware Release 5.4.1June 2011

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.TIBCO, The Power of Now, TIBCO ActiveMatrix BusinessWorks, TIBCO Adapter, TIBCO ActiveEnterprise, TIBCO Rendezvous, TIBCO Designer, TIBCO Administrator, TIBCO IntegrationManager and TIBCO Hawk are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE 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 OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.Copyright © 1999-2011 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viTIBCO Adapter for Oracle Applications Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viOther TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viThird-Party Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Terminology and Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xivHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xivHow to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xivHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv

Chapter 1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Requirements for TIBCO BusinessWorks Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Examples Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2 PreDefined Outbound Business Object: EmployeePub . . . . . . . . . . . . . . . . . . . . . . . .5

Example Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Set Up the Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Test the Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Test in the Command Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Test in TIBCO Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

The Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 3 PreDefined Inbound Business Object: Employee Interface . . . . . . . . . . . . . . . . . . . .16

Example Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Set Up the Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Test the Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Test in the Command Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Test in TIBCO Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

The Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

TIBCO Adapter for Oracle Applications Examples Guide

iv | Contents

Chapter 4 Oracle Applications Inbound Business Object (For R12 Only): SPLIT_LINESub. . 27


Set Up the Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Using the Preconfigured Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Creating Your Own Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Test the Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Test in the Command Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Test in TIBCO Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

The Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Chapter 5 Oracle Applications Inbound Business Object (For R12 Only): PROCESS_BOMSub38


Set Up the Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Using the Preconfigured Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Creating Your Own Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42


The Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 6 Oracle Applications Inbound Business Object (For R12 Only): WICMLPSub. . . . . 50


Set Up the Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52


The Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Chapter 7 JPublisher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61


Set Up the Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Test the Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

The Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67


| v

Preface

TIBCO Adapter™ for Oracle Applications Examples Guide contains examples to further your understanding of the TIBCO Adapter for Oracle Applications product.

Topics

• Related Documentation, page vi

• Typographical Conventions, page ix

• Terminology and Acronyms, page xii

• Connecting with TIBCO Resources, page xiv


vi | Related Documentation

Related Documentation

This section lists documentation resources you may find useful.

TIBCO Adapter for Oracle Applications DocumentationThe following documents form the TIBCO Adapter for Oracle Applications documentation set:

• TIBCO Adapter Concepts Read this manual to gain an understanding of the product that you can apply to the various tasks you may undertake.

• TIBCO Adapter for Oracle Applications User’s Guide — Read this manual to gain an understanding of the product.

• TIBCO Adapter for Oracle Applications Release Notes Read the release notes for a list of new and changed features. This document also contains lists of known issues and closed issues for this release.

• TIBCO Adapter for Oracle Applications readme.txt — Read this document to check the current release number, supported platforms and required software.

• TIBCO Adapter for ActiveDatabase User’s Guide — Read this document to gain an understanding of the TIBCO ActiveMatrix Adapter for Database product, the run-time component of TIBCO Adapter for Oracle Applications.

• TIBCO ActiveMatrix Adapter for Database Release Notes— Read this document for a summary of new features, changes since last release and a description of any open or closed issues that may affect installing or using the adapter.

• TIBCO ActiveMatrix Adapter for Database readme.txt — Read this document to check the current release number, supported platforms and required software.

Other TIBCO Product DocumentationYou may find it useful to read the documentation for the following TIBCO products:


Preface | vii

• TIBCO BusinessWorks™ Software

— TIBCO BusinessWorks Concepts

— TIBCO BusinessWorks QuickStart

— TIBCO BusinessWorks Business Palette Reference

— TIBCO BusinessWorks Process Design Guide

— TIBCO BusinessWorks Error Codes

— TIBCO BusinessWorks Release Notes

• TIBCO Designer™ software:

— TIBCO Designer User’s Guide

— TIBCO Designer Palette Reference

— TIBCO Designer Release Notes

• TIBCO Administrator™ software:— TIBCO Administrator User’s Guide

— TIBCO Administrator Server Configuration Guide

— TIBCO Administrator Release Notes

• TIBCO IntegrationManager™ software:

— TIBCO IntegrationManager Concepts

— TIBCO IntegrationManager Administrator’s Guide

— TIBCO IntegrationManager Process Design Guide

— TIBCO IntegrationManager Reference

— TIBCO IntegrationManager Release Notes

• TIBCO Rendezvous™ software:

— TIBCO Rendezvous Concepts

— TIBCO Rendezvous Administration

— TIBCO Rendezvous Configuration Tools

• TIBCO Enterprise Message Service™ software:

— TIBCO Enterprise Message Service User’s Guide

— TIBCO Enterprise Message Service Installation

— TIBCO Enterprise Message Service Application Integration

— TIBCO Enterprise Message Service Release Notes


viii | Related Documentation

• TIBCO Hawk® software:

— TIBCO Hawk Installation and Configuration

— TIBCO Hawk Administrator’s Guide

• TIBCO Adapter™ SDK

— TIBCO Adapter SDK Concepts

• TIBCO Runtime Agent™— TIBCO Runtime Agent Release Notes

— TIBCO Runtime Agent Installation

— TIBCO Runtime Agent Domain Utility User’s Guide

— TIBCO Runtime Agent Upgrading to Release 5.3

Third-Party DocumentationRefer to the Technical Reference Manual (TRM) included with Oracle Applications 11i when modifying adapter publication and subscription transactions.


Preface | ix

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME

ENV_HOME

ADORAPPS_HOME

Many TIBCO products must be installed within the same home directory. This directory is referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco.

Other TIBCO products are installed into an installation environment. Incompatible products and multiple instances of the same product are installed into different installation environments. The directory into which such products are installed is referenced in documentation as ENV_HOME. The value of ENV_HOME depends on the operating system. For example, on Windows systems the default value is C:\tibco.

TIBCO Adapter for Oracle Applications installs into a directory within TIBCO_HOME. This directory is referenced in documentation as ADORAPPS_HOME. The value of ADORAPPS_HOME depends on the operating system. For example on Windows systems, the default value is C:\tibco\adapter\adorapps\5.4.

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code

font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin.

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]


x | Typographical Conventions

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO ActiveMatrix BusinessWorks Concepts.

• To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand PathName

Key combinations

Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use


Preface | xi

Table 2 Syntax Typographical Conventions

Convention Use

[ ] An optional item in a command or code syntax.

For example:

MyCommand [optional_parameter] required_parameter

| A logical OR that separates multiple items of which only one may be chosen.

For example, you can select only one of the following parameters:

MyCommand para1 | param2 | param3

{ } A logical group of items in a command. Other syntax notations may appear within each logical group.

For example, the following command requires two parameters, which can be either the pair param1 and param2, or the pair param3 and param4.

MyCommand {param1 param2} | {param3 param4}

In the next example, the command requires two parameters. The first parameter can be either param1 or param2 and the second can be either param3 or param4:

MyCommand {param1 | param2} {param3 | param4}

In the next example, the command can accept either two or three parameters. The first parameter must be param1. You can optionally include param2 as the second parameter. And the last parameter is either param3 or param4.

MyCommand param1 [param2] {param3 | param4}


xii | Terminology and Acronyms

Terminology and Acronyms

The following terms and acronyms are used in this document:

Term Definition

Business Object When a Business Transaction occurs, a set of database objects get affected by the transaction. Such a logical set of related database objects for a particular transaction is called a Business Object.

Outbound Business Object

A Business Object associated with the Publication Service is called an Outbound Business Object.

Inbound Business Object

A Business Object associated with the Subscription Service is called an Inbound Business Object.

Predefined Business Object

A Predefined Business Object consists of database objects that are pre-set according to standard Oracle Applications workflow.

RV TIBCO Rendezvous™ protocol; also in certain contexts refers to reliable message delivery quality of service, as opposed to certified message delivery quality of service.

JMS Java Messaging Service

TRA TIBCO Runtime Agent

EAR Enterprise Archive File

Publish to Adapter Sends a message to the specified adapter.

EmployeePublisher activity

Is the name that appears as the label for the Publish to Adapter activity in the process definition. EmployeePublisher activity publishes a message that can be received by an Inbound Employee business object.

OpenItemPublisher activity

Is the name that appears as the label for the Publish to Adapter activity in the process definition. OpenItemPublisher activity publishes a message that can be received by an Inbound OpenItem business object.

OrderEntryPublisher activity

Is the name that appears as the label for the Publish to Adapter activity in the process definition. OrderEntryPublisher activity publishes a message that can be received by an Inbound OrderEntry business object.


Preface | xiii

PurchasingOpenDocsPublisher activity

Is the name that appears as the label for the Publish to Adapter activity in the process definition. PurchasingOpenDocsPublisher activity publishes a message that can be received by an Inbound PurchasingOpenDocs business object.

RecCuctomerPublisher activity

Is the name that appears as the label for the Publish to Adapter activity in the process definition. RecCuctomerPublisher activity publishes a message that can be received by an Inbound Rec Cuctomer business object.

ARCustomersSubscriber activity

Is the name that appears as the label for the Adapter Subscriber activity in the process definition. ARCustomersSubscriber activity starts a process based on the receipt of a message from the Outbound ARCustomers business object.

ItemsSubscriber activity

Is the name that appears as the label for the Adapter Subscriber activity in the process definition. ItemsSubscriber activity starts a process based on the receipt of a message from the Outbound Items business object.

PurchaseOrdersSubscriber activity

Is the name that appears as the label for the Adapter Subscriber activity in the process definition. PurchaseOrdersSubscriber activity starts a process based on the receipt of a message from the Outbound PurchaseOrders business object.

EmployeeSubscriber activity

Is the name that appears as the label for the Adapter Subscriber activity in the process definition. EmployeeSubscriber activity starts a process based on the receipt of a message from the Outbound Employee business object.

AdapterSubscriber activity

Receives a message from the specified adapter and starts a process. It starts a process based on the receipt of a message from the publication service of the specified adapter.

Term Definition


xiv | Connecting with TIBCO Resources

Connecting with TIBCO Resources

How to Join TIBCOmmunityTIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts, a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to http://www.tibcommunity.com.

How to Access All TIBCO DocumentationAfter joining TIBCOmmunity, you can access the documentation for all supported product versions here:

http://docs.tibco.com/TibcoDoc

How to Contact TIBCO SupportFor comments or problems with this document or the software it addresses, contact TIBCO Support as follows:

• 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, click Register with Support.


http://www.tibcommunity.com

http://docs.tibco.com/TibcoDoc

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

https://support.tibco.com

| 1

Chapter 1 Introduction

This chapter provides examples of how to use the Publication service (standalone) and the Subscription service (with TIBCO BusinessWorks). It will give you an overview of the TIBCO Adapter for Oracle Applications.

Topics

• Overview, page 2

• Prerequisites, page 3


2 | Chapter 1 Introduction

Overview

The following examples demonstrate how TIBCO Adapter for Oracle Applications works. The examples also demonstrate the Publication and Subscription features of TIBCO Adapter for Oracle Applications.

• The examples in chapters 2 through 7 demonstrate the integration between the adapter and TIBCO BusinessWorks. These examples can be run on Oracle Applications 11.5.10 and R12.

The examples cover the five most common business objects used for end-to-end, enterprise-wide integration.

The examples for subscription are:

• Example 1 - EmployeeSub

• Example 2 - SPLIT_LINESub

• Example 3 - PROCESS_BOMSub

• Example 4 - WICMLPSub

The following example is for publication:

• Example 1 - EmployeePub

Subscription Service

The examples on Subscription Service demonstrate the usage of the following pre-defined Subscription transactions of the Oracle Application Adapter: EmployeeSub, SPLIT_LINESub, PROCESS_BOMSub, and WICMLPSub.

The adapter subscribes to an Inbound Record for each of the business objects. It also returns the status of the message processed. The status can be Error or Success depending on the validity of the data.

Publication Service

The example on Publication service demonstrates the usage of the pre-defined Publication transactions on EmployeePub of the Oracle Application Adapter.

The adapter publishes the data in the tables of each of the business objects.


Prerequisites | 3

Prerequisites

Before running an adapter example, you need to run the common_all.sql script in the path <adorapps_home>/config/sub as follows:

1. cd <adorapps_home>/config/sub

2. sqlplus <Apps User Id>/ <Apps Password>@<Oracle SID>

3. @common_all.sql

Requirements for TIBCO BusinessWorks Examples If you are using the adapter with TIBCO BusinessWorks, the following software must be installed to run the examples:

• TIBCO BusinessWorks

• TIBCO Administrator

• TIBCO Adapter for Oracle Applications

• Oracle Applications

• TIBCO Runtime Agent

• TIBCO Enterprise Message Service

Refer to the TIBCO Adapter for Oracle Applications Readme.txt for supported software versions.

The TIBCO BusinessWorks examples use TIBCO Designer to create Enterprise Archive Files (EAR) and TIBCO Administrator to deploy the EAR files.

In TIBCO Administrator, make sure all the software components needed by the adapter instance are installed on one or multiple machines that are part of the TIBCO Administration Domain and that the software is registered in the domain.

• To add a machine to a TIBCO Administration Domain, use the TIBCO Domain Utility.

• To register software, select Resource Management>Machines console in TIBCO Administrator.

These topics are explained in the TIBCO Administrator documentation set.

These examples demonstrate how to use the adapter with simple configurations. Refer to the TIBCO ActiveMatrix Adapter for Database User’s Guide for details on adapter configuration.


4 | Chapter 1 Introduction

Examples LocationYou can find the files for the examples and the adapter executable files required to run the examples in:

<adorapps_home>/examples/11.5.10

<adorapps_home>/examples/12.0

The TRA files for Publication and Subscription services are available in the following locations:

<adorapps_home>/examples/11.5.10/EmployeePub

<adorapps_home>/examples/11.5.10/EmployeeSub

<adorapps_home>/examples/12.0/EmployeePub

<adorapps_home>/examples/12.0/EmployeeSub

<adorapps_home>/examples/12.0/SPLIT_LINESub

<adorapps_home>/examples/12.0/PROCESS_BOMSub

<adorapps_home>/examples/12.0/WICMLPSub


| 5

Chapter 2 PreDefined Outbound Business Object: EmployeePub

This example shows how to use the adapter within a TIBCO BusinessWorks process to publish the Outbound EmployeePub business object in an Oracle Application. It also demonstrates the EmployeePubSubscriber activity on the Outbound EmployeePub business object using TIBCO BusinessWorks.

This example uses TIBCO Rendezvous as its transport type.

Topics

• Example Description, page 6

• Set Up the Example, page 7

• Test the Example, page 12

• The Results, page 15


6 | Chapter 2 PreDefined Outbound Business Object: EmployeePub

Example Description

This example illustrates the Publication service in a TIBCO BusinessWorks scenario. The example has one process – ProcessEmployeePub

The ProcessEmployeePub example demonstrates the EmployeePubSubscriber activity. The EmployeePub business object publishes the employee details. The EmployeePubSubscriber activity receives the message.

Once the EmployeePub business object publishes the employee information, the EmployeePubSubscriber activity subscribes to this message. The Outbound data is visible in the Output tab of the EmployeePubSubscriber activity.


Set Up the Example | 7

Set Up the Example

You can use the preconfigured example or create your own. Instructions for using the preconfigured example are listed below. Instructions for creating your own example are listed in Creating Your Own Example on page 9.

Using the Preconfigured Example

Run the following SQL scripts from the SQL*PLus prompt. For more details on these SQL scripts, refer to Chapter 2 of the TIBCO Adapter for Oracle Applications User’s Guide.



3. @create_user.sql (Run this script to create an user with all the required grants and privileges.)

4. @common_all_undo.sql

5. @common_all.sql

Note that you must install the ODBC driver before starting the example.

Before starting the example you must import the sample project ZIP file and convert it to a DAT file. Both files must have the same name. To do this, follow the instructions below. In the TIBCO Designer:

1. Select Project > Import Full Project.

2. Click the ZIP Archive tab and browse to locate the EmployeePub.zip file. The file is located in the <adorapps_home>/examples/<EBSVersionNumber>/EmployeePub folder.

Platforms Installation Instructions

Windows 1. Run the installodbc.exe file under the <adorapps_home>/bin folder in the command prompt.

2. Choose the Install ODBC drivers option by typing 1 when prompted.

3. Enter the path of your DataDirect ODBC drivers as <adorapps_home>/adb/odbc/Drivers when prompted.

4. Close the prompt window after the installation is completed.

UNIX The required drivers are provided automatically for this platform.



All preconfigured instances of the adapter and TIBCO BusinessWorks processes are included in the new project.

3. In the Design-time Connection tab of the Oracle Applications adapter instance and the ActiveDatabase adapter instance, change the values of the JDBC URL, Username and Password fields according to your environment settings. In the Runtime Connection tab of the ActiveDatabase adapter instance, change the value of the ODBC DSN field accordingly.

4. To run this example from the command prompt, export the project as a DAT file using the same name as that of the ZIP file, that is, EmployeePub:

a. Select Project > Export Full Project. The Export Project window appears. The User field appears by default.

b. Enter the Project Name as EmployeePub in the Project Name field, and click the Browse button. Specify the path of the directory: <adorapps_home>/examples/<EBSVersionNumber>/EmployeePub where the local repository DAT file and then click the OK button.

If you change the user name and DSN values here, you must run the common_all.sql and the common_all_undo.sql scripts again.

Platforms Data Source Name Acquisition

Windows 1. Click Start > Control Panel. Double click the Administrative Tools option.

2. Double click the Data Sources (ODBC) option and you will see the ODBC Data Source Administrator window displayed on the screen.

3. Select the System DSN tab and click the Add button to create a new data source.

4. Select the TIBCO 5.30 Oracle Wire Protocol option from the Create New Data Source window and click the Finish button to continue.

5. Enter the correct value in the Data Source Name, Host, Port Number, SID, and Service Name fields.

6. Click the Test Connect button to test the connection. After a successful connection, click the OK button to complete the setup.

7. Copy the value of the Data Source Name into the ODBC DSN field.



Creating Your Own Example

In TIBCO Designer:

1. Restore the Oracle Applications Adapter window in the Palettes tab. Drag the Oracle Apps Business Object Configuration button from the palette panel and drop it into the design panel and rename it to OracleAppsEmployeePub in the Name field in the Configuration panel.

2. Enter the appropriate values in the JDBC URL, Username, and Password fields in the Design-Time Connection tab.

3. Click the Test Connection... button in the Design-time Connection panel. You will get a Connection Successful message if the connection is successful. Click the OK button to continue.

4. Click the OracleAppsEmployeePub button in the project panel. You will find six services in the palette panel.

5. Drag the PreDefined Outbound Business Object button from palette panel and drop it into the design panel.

6. In the Configuration tab, click EmployeePub from the PreDefined Outbound Business object drop-down list and click the Apply button.

7. Ensure the default username in the APPS Username is correct and enter the valid password in the APPS User Password fields in the Configuration tab and click the Apply button.

8. Click the Root folder of the project in the project panel.

9. Drag the Active Database Adapter Configuration button from the palette panel, drop it into the design panel, and then rename it to ADBEmployeePub in the Instance Name field in the Configuration panel.

UNIX 1. Open the odbc.ini file in the <adorapps_home>/adb/odbc/ directory.

2. Search for the [Oracle Wire Protocol] string.

3. Assign the appropriate values to the HostName, LogonID, Password, PortNumber, and SID parameters.

4. Leave the ServerName parameter blank and set the CatalogIncludesSynonyms parameter to 0 (recommended).

5. Change the value of [Oracle Wire Protocol] and put this value into the ODBC DSN field.




10. You will get a warning message box saying By default, database objects for your configurations will be created. Click the OK button to continue.

11. Select the Design-time Connection tab and enter the correct value in the JDBC URL, Username, and Password fields respectively in the Design-time Connection tab.

12. Click the Test Connection... button to test if the connection was successful. After the confirmation message box, click the OK button to continue.

13. Enter the appropriate value in the ODBC DSN field in the Runtime Connection tab.

14. Select the Adapter Services folder under the ADBEmployeePub folder from the Project panel.

15. Drag an OracleApps Publication Service button from the Palettes panel and drop it into the Design panel.

16. Select the button to select a resource. In this example, select EmployeePub under OracleAppsBusinessObject Configuration as the resource from the Select a Resource... window. Click the OK button to confirm the selection.

17. Click the Apply button to apply the changes. The adapter will generate some SQL scripts in the <adorapps_home>/sql directory.

18. Select the Rendezvous option from the Transport Type drop-down list in the Configuration tab.

19. Click the root folder of the project in the project panel.

20. Drag the Process Definition button from the process tab of the palette panel and drop it into the design panel.

21. Enter ProcessEmployeePub in the Name field in the Configuration tab.

22. Click the ProcessEmployeePub folder in the project panel. Drag the Adapter Subscriber button from the palette panel and drop it into the design panel. Rename the Adapter Subscriber object to EmployeePubSubscriber in the Name field of the Configuration tab.

23. Click the button from the TIBCO Designer menu bar. Create a transition by dragging the EmployeePubSubscriber object and dropping it at the End object.

24. Click the button on the right-hand side of the Adapter Service field in the Configuration tab. You will see a Select a Resource window.

25. Select the EmployeePub object under ADBEmployeePub > Adapter Services and click the OK button.

26. Click the Apply button.



27. Save the project.



Test the Example

This section describes the way to deploy, run, and test the example.

In the Configuration tab of the ADBEmployeePub object, if the Write to Database on Save checkbox is not checked, you must manually run the required SQL scripts for the adapter. To do this, perform the following steps.

1. Execute the SQL file OracleAppsEmployeePub_EmployeePub_undo_all.sql in <adorapps_home>/examples/<EBSVersionNumber>/EmployeePub/sql. This file contains the cleanup scripts.

2. Execute the SQL file OracleAppsEmployeePub_EmployeePub_all.sql in the same location.

Test in the Command Prompt1. Click the Tester tab at the left hand side of the Project panel. The Test panel

will appear in the Project panel in TIBCO Designer.

2. Click the button at the left hand side of the Test panel. The Select Processes to Load window will appear in the middle of the screen.

3. Select the ProcessEmployeePub option in the Select Processes to Load window and click the Load Selected button.

The process is now in Test mode.

4. Export the DAT file to a desired directory.

5. Configure the appropriate environment variables to run the adapter in the command prompt. The adapter installation contains the adorappssetenv.sh and adbagent_env.sh file in the <adorapps_home>/bin directory. You must execute this file before using the product.

6. Open the adbagent.tra file under the <adorapps_home>/bin directory and modify the parameters as instructed below:

a. Find tibco.repourl <repourl> in the adbagent.tra file and replace the content within the angle bracket with the DAT file’s absolute path. For more details on the DAT file, refer to step 4 in Using the Preconfigured Example on page 7.

b. Find tibco.configurl <configurl> in the adbagent.tra file and replace the content within the angle bracket with ADBEmployeePub.

7. To start the adapter instance:


Test the Example | 13

If you want to use the adbagent.tra file in the <adorapps_home>/bin directory, go to the <adorapps_home>/bin folder and execute:adbagent

If you want to use the adbagent.tra file in other directories, change the application.args-system:propFile parameter to the directory you want to store the adbagent.tra file and execute:adbagent --propFile

<user_defined_dir>/adbagent.tra

8. Switch back to TIBCO Designer and select the Console tab to monitor the test process.

9. Leave the Console tab open and run SQL*PLus in a command window. For more details on how to run SQL*PLus, refer to Set Up the Example on page 7.

10. Type the following SQL scripts in the SQL*PLus prompt:update PER_ALL_PEOPLE_F set attribute1=’aa’ where person_id=2;

commit;

to update the table.

11. Switch to the Console tab again and observe the changes.

12. Check if the process received published message.

13. Click the button to return to the design mode.

Test in TIBCO Designer1. Click the Tester tab at the left hand side of the Project panel. The Test panel

will appear in the Project panel.


3. Select the ProcessEmployeePub option in the Select Processes to Load window and click the Load Selected button.


4. Click Tools > Show Adapter Tester from the TIBCO Designer menu to open the Adapter Tester window.

5. Select the ADBEmployeePub business object from the left pane of the Adapter Tester window and specify a working directory to store the test data for the adapter in the Working Directory field.

6. Click the Start button to start the test.

7. Select the Console tab to monitor the test process.




9. Type the following SQL scripts in the SQL*PLus prompt:update PER_ALL_PEOPLE_F set attribute1=’aa’ where person_id=2;

commit;

to update the table.

10. Switch to the Console tab again.

11. Check for a published message.



The Results | 15

The Results

The results can be viewed as follows:

1. ProcessEmployeePub — Publishes the data from the Oracle Source tables that comprise the business object. The adapter publishes this message on the TIB. The EmployeePubSubscriber activity subscribes to this message. The Outbound data is visible in the Output tab of the EmployeePubSubscriber activity.

2. The Green Arrow pointing from the EmployeePubSubscriber object to the End object indicates the successful completion of data subscribed from the Outbound EmployeePub business object.


16 | Chapter 3 PreDefined Inbound Business Object: Employee Interface

Chapter 3 PreDefined Inbound Business Object: Employee Interface

This example shows how to use the adapter within a TIBCO BusinessWorks process to subscribe to the Inbound EmployeeSub business object in Oracle Applications. It also demonstrates the EmployeeSubPublisher activity on the Inbound EmployeeSub business object using TIBCO BusinessWorks.

This example uses TIBCO JMS as its transport type.

Topics






Example Description | 17

Example Description

This example illustrates the Subscription service in a TIBCO BusinessWorks scenario. The example has one process – ProcessEmployeeSub.

The ProcessEmployeeSub example demonstrates the EmployeeSubPublisher activity. The EmployeeSubPublisher activity publishes the message and the EmployeeSub business object receives the information.

Once the EmployeeSubPublisher activity publishes the employee information, the EmployeeSub business object subscribes to this message. The Inbound data is visible in the Output tab of the EmployeeSubPublisher activity.



Set Up the Example








5. @common_all.sql

You must install the ODBC driver before starting the example.

Before starting the example you must import the sample project ZIP file and convert it to a DAT file. Both files must have the same name. To do this, in the TIBCO Designer:

1. Select Project >Import Full Project.

2. Click the ZIP Archive tab and browse to locate the EmployeeSub.zip file. The file is located in the <adorapps_home>/examples/<EBSVersionNumber>/EmployeeSub folder.










3. In the Design-time Connection tab of the Oracle Applications adapter instance and the ActiveDatabase adapter instance, change the values of the JDBC URL, Username and Password fields according to your environment settings. In the Runtime Connection tab of the ActiveDatabase adapter instance, change the value of the ODBC DSN field accordingly.

4. To run this example from the command prompt, export the project as a DAT file using the same name as that of the ZIP file, that is, EmployeeSub:

a. Select Project >Export Full Project. The Export Project window appears. The User field appears by default.

b. Enter EmployeeSub in the Project Name field as the Project Name. Click the Browse button and specify the path of the directory: <adorapps_home>/examples/<EBSVersionNumber>/EmployeeSub where you want to save the local repository DAT file and then click the OK button.

If you change the username and DSN values here, you must run the common_all.sql and the common_all_undo.sql scripts again.












In TIBCO Designer:

1. Restore the Oracle Applications Adapter window in the Palettes tab. Drag the Oracle Apps Business Object Configuration button from the palette panel and drop it into the design panel and rename the object to OracleAppsEmployeeSub in the Name field of the Configuration panel.

2. Click the Apply button to apply name changes.

3. Enter the appropriate values in the JDBC URL, Username, and Password fields in the Design-Time Connection tab and click the Apply button.


5. Click the OracleAppsEmployeeSub button in the project panel. You will find six services in the palette panel.

6. Drag the PreDefined Inbound Business Object button from palette panel and drop it into the design panel.

7. In the Configuration tab, click Employee Interface from the PreDefined Inbound Business object drop-down list and click the Apply button.

8. Ensure the default username in the APPS Username is correct; enter the valid password in the APPS User Password fields in the Configuration tab; and click the Apply button.


10. Drag the Active Database Adapter Configuration button from the palette panel and drop it into the design panel. Then rename the object to ADBEmployeeSub in the Instance Name field in the Configuration tab.









11. Click the Apply button to apply name changes.


13. Select the Design-time Connection tab and enter the correct value in the JDBC URL, Username, and Password fields in the Design-time Connection tab and click the Apply button.

14. Click the Test Connection... button to test if the connection was successful. After the confirmation message box, click the OK button to continue.


16. Select the Adapter Services folder under the ActiveDatabaseAdapterConfiguration folder from the Project panel.

17. Drag an OracleApps Subscription Service button from the Palettes panel and drop it into the Design panel.

18. Select the button to select a resource. In this example, select EmployeeSub under OracleAppsEmployeeSub Configuration as the resource from the Select a Resource... window. Click the OK button to confirm the selection.

19. Click the Apply button to apply changes. The adapter will generate SQL scripts in the <adorapps_home>/sql directory.

20. Select the JMS option from the Transport Type drop-down list in the Configuration tab. Ensure that the TIBCO Enterprise for EMS server is running and accessible to the machine which the adapter is installed before running any processes.


22. Drag the Process Definition button from the Process tab of the palette panel and drop it into the design panel.

23. Enter ProcessEmployeeSub in the Name field in the Configuration tab to change the object’s name.

24. Click the ProcessEmployeeSub folder in the project panel. Drag the Publish to Adapter button from the palette panel and drop it into the design panel. Rename the object Publish to Adapter as EmployeeSubPublisher in the Name field of the Configuration tab.

You must execute the OracleAppsEmployeeSub_EmployeeSub_undo_all.sql script followed by the OracleAppsEmployeeSub_EmployeeSub_all.sql script provided in the example package before continue implementing the example.



25. Click the button from the TIBCO Designer menu bar. You need to create two transitions in this example. One is from the Start object to the EmployeeSubPublisher object, the other is from the EmployeeSubPublisher object to the End object.

26. Click the button on the right-hand side of the Adapter Service field in the Configuration tab. You will see the Select a Resource window.

27. Select the EmployeeSub object under ADBEmployeeSub > Adapter Services and click the OK button.





Test the Example


In the Configuration tab of the ADBEmployeeSub object, if the Write to Database on Save checkbox is not checked, you must manually run the required SQL scripts for the adapter. To do this, perform the following steps.

1. Execute the SQL file OracleAppsEmployeeSub_EmployeeSub_undo_all.sql in <adorapps_home>/examples/<EBSVersionNumber>/EmployeeSub/sql. This file contains the cleanup scripts.

2. Execute the SQL file OracleAppsEmployeeSub_EmployeeSub_all.sql in the same location.

Test in the Command Prompt1. Click the ProcessEmployeeSub object on the Project panel and then click the

Input tab in the Configuration panel in TIBCO Designer. Expand the activity input and provide the appropriate values for each field. Click the Apply button to apply the changes.


3. Configure the appropriate environment variables to run the adapter. The adapter installation contains the adorappssetenv.sh and adbagent_env.sh file in the <adorapps_home>/bin directory. You must execute this file before using the product.


a. Find tibco.repourl <repourl> in the adbagent.tra file and replace the content within the angle bracket with the DAT file’s absolute path. This path must be the same as specified in step 2. For more details on the DAT file, refer to step 4 in Using the Preconfigured Example on page 18.

b. Find tibco.configurl <configurl> in the adbagent.tra file and replace the content within the angle bracket with ADBEmployeeSub.

5. To start the EMS server, execute the tibjmsd.exe file in Windows or execute the ./tibemsd & in UNIX under the <TIBC0_HOME>/JMS/bin directory.







7. Click the Tester tab at the left hand side of the Project panel and the Test panel will display in the Project panel.

8. Click the button at the left hand side of the Test panel and the Select Processes to Load window will appear in the middle of the screen.

9. Select the ProcessEmployeeSub option in the Select Processes to Load window and click the Load Selected button.


10. Switch to the Console tab.

11. Check if the process published the message.


Test in TIBCO Designer1. To start the EMS server, execute the tibjmsd.exe file in Windows or execute

the ./tibemsd & in UNIX under the <TIBC0_HOME>/JMS/bin directory.

2. Click the ProcessEmployeeSub object on the Project panel and then click the Input tab in the Configuration panel. Expand the activity input and provide the appropriate values for each field. Click the Apply button to apply the changes.


4. Select the ADBEmployeeSub business object from the left pane of the Adapter Tester window and specify a working directory to store the test data for the adapter in the Working Directory field.




8. Click the Tester tab at the left hand side of the Project panel. The Test panel will appear in the Project panel.




10. Select the ProcessEmployeeSub option in the Select Processes to Load window and click the Load Selected button.







The Results


1. ProcessEmployeeSub — Publishes the data from the Oracle Source tables that comprise the business object. The adapter subscribes to this message on the TIB. The EmployeeSubPublisher activity publishes this message. The Inbound data is visible in the Output tab of the EmployeeSubPublisher activity.

2. The Green Arrow pointing from the EmployeeSubPublisher object to the End object indicates the successful completion of data published from the Inbound EmployeeSub business object.


Oracle Applications Inbound Business Object (For R12 Only): SPLIT_LINESub | 27

Chapter 4 Oracle Applications Inbound Business Object (For R12 Only): SPLIT_LINESub

This example shows how to use the adapter within a TIBCO BusinessWorks process to subscribe to the Inbound SPLIT_LINESub business object in Oracle Applications. It also demonstrates the PROCESS_SPLIT_LINEPublisher activity on the Inbound SPLIT_LINESub business object using TIBCO BusinessWorks.


Topics






28 | Chapter 4 Oracle Applications Inbound Business Object (For R12 Only): SPLIT_LINESub

Example Description

This example illustrates the Subscription service in a TIBCO BusinessWorks scenario. The example has one process – processSPLIT_LINE.

The processSPLIT_LINE example demonstrates the PROCESS_SPLIT_LINEPublisher activity. The PROCESS_SPLIT_LINEPublisher activity publishes the message and the SPLIT_LINESub business object receives the information.

Once the PROCESS_SPLIT_LINEPublisher activity publishes the employee information, the SPLIT_LINESub business object subscribes to this message. The Inbound data is visible in the Output tab of the PROCESS_SPLIT_LINEPublisher activity.



Set Up the Example


Using the Preconfigured ExampleRun the following SQL scripts from the SQL*PLus prompt. For more details on these SQL scripts, refer to Chapter 2 of the TIBCO Adapter for Oracle Applications User’s Guide.



3. @create_user.sql (Run this script to create a user with all the required grants and privileges.)


5. @common_all.sql


Before starting the example you must import the sample project ZIP file and convert it to a DAT file. Both files must have the same name. To do this, follow the instructions below. In TIBCO Designer:


2. Click the ZIP Archive tab and browse to locate the SPLIT_LINESub.zip file. The file is located in the <adorapps_home>/examples/<EBSVersionNumber>/SPLIT_LINESub folder.










3. In the Design-time Connection tab of the Oracle Applications adapter instance and the ActiveDatabase adapter instance, change the values of the JDBC URL, Username, and Password fields according to your environment settings. In the Runtime Connection tab of the ActiveDatabase adapter instance, change the value of the ODBC DSN field accordingly.

4. To run this example from the command prompt, export the project as a DAT file using the same name as that of the ZIP file, that is, SPLIT_LINESub:

a. Select Project >Export Full Project. The Export Project window appears. The User field appears by default.

b. Enter the Project Name as SPLIT_LINESub in the Project Name field, and click the Browse button. Specify the path of the directory as: <adorapps_home>/examples/<EBSVersionNumber>/SPLIT_LINESub where you want to save the local repository DAT file and then click the OK button.




2. Double click the Data Sources (ODBC) option. The ODBC Data Source Administrator window appears.



5. Enter the correct values in the Data Source Name, Host, Port Number, SID, and Service Name fields.


7. Copy the value of the Data Source Name to the ODBC DSN field.



Creating Your Own ExampleIn TIBCO Designer:

1. Create an new project.

2. Restore the Oracle Applications Adapter window in the Palettes tab. Drag the Oracle Apps Business Object Configuration button and drop it into the Design panel and rename the object to OracleAppsSPLIT_LINESub in the Name field of the Configuration panel.

3. Click the Apply button to apply the name changes.



6. Click the OracleAppsSPLIT_LINESub button in the project panel. You will find six services in the palette panel.

7. Drag the Oracle Applications Inbound Business Object (For R12 Only) button from palette panel and drop it into the design panel.

8. In the Configuration tab, select the PL/SQL API option from the Interface Type drop-down list.


10. Enter the appropriate values for the Name, APPS Username, APPS User Password, APPLSYS Username, Interface Name, and Overload fields in the Configuration tab. Note that the Interface Name field must be specified in the format of <packageName>.<methodName>.









11. Click the Browse button at right side of the Overload field. You will see an Input Overload message box. Select the correct option from the Please Select an Existing Overload Value drop-down list and click the OK button.


13. Ensure that the No Wrapper Package Or Function checkbox is checked in the API Wrapper Options tab and click the Apply button.

14. Specify an exception table name in the Exception Table field (name it as SPLIT_LINE_excep in this example) and click the Apply button.


16. Drag the ActiveDatabase Adapter Configuration button from the palette panel and drop it into the design panel. Rename the object to ADBSPLIT_LINESub in the Instance Name field in the Configuration tab.



19. Select the Design-time Connection tab and enter the correct value in the JDBC URL, Username, and Password fields in the Design-time Connection tab. Click the Apply button.

20. Click the Test Connection... button to test if the connection was successful. After viewing the confirmation message box, click the OK button to continue.


22. Select the Adapter Services folder under the ADBSPLIT_LINESub folder from the Project panel.


24. Select the button to select a resource. In this example, select the SPLIT_LINESub object under the OracleAppsSPLIT_LINESub object as the resource from the Select a Resource... window. Click the OK button to confirm the selection.

25. Click the Apply button to apply changes and the adapter will generate some SQL scripts in the <adorapps_home>/sql directory.

You must execute the SQL script provided in the example package before you continue implementing the example.






29. Enter processSPLIT_LINE in the Name field in the Configuration tab.

30. Click the processSPLIT_LINE folder in the project panel. Drag the Publish to Adapter button from the palette panel and drop it into the design panel. Rename the object Publish to Adapter as PROCESS_SPLIT_LINEPublisher in the Name field of the Configuration tab.

31. Click the button from the TIBCO Designer menu bar. You will create two transitions in this example. One is from the Start object to the PROCESS_SPLIT_LINEPublisher object, the other one is from the PROCESS_SPLIT_LINEPublisher object to the End object.

32. Click the button on the right-hand side of the Adapter Service field in the Configuration tab. You will see the Select a Resource window.

33. Select the SPLIT_LINESub object under ADBSPLIT_LINESub > Adapter Services and click the OK button.





Test the Example


In the Configuration tab of the ADBSPLIT_LINESub object, if the Write to Database on Save checkbox is not checked, you must manually run the required SQL scripts for the adapter. To do this, perform the following steps.

1. Execute the SQL file OracleAppsSPLIT_LINESub_SPLIT_LINESub_undo.sql in <adorapps_home>/examples/<EBSVersionNumber>/SPLIT_LINESub/sql. This file contains the cleanup scripts.

2. Execute the SQL file OracleAppsSPLIT_LINESub_SPLIT_LINESub.sql in the same location.

Test in the Command Prompt1. Click the processSPLIT_LINE object on the Project panel and then click the

Input tab in the Configuration panel in TIBCO Designer. Expand the activity input and provide the appropriate value for each field. Click the Apply button to apply the changes.


3. Configure the appropriate environment variables to run the adapter. The adapter installation contains the adorappssetenv.sh and adbagent_env.sh file in the <adorapps_home>/bin directory. You must execute these files before using the product.



b. Find tibco.configurl <configurl> in the adbagent.tra file and replace the content within the angle bracket with ADBSPLIT_LINESub.

5. Start the adapter instance.




If you want to use the adbagent.tra file in another directory, change the application.args-system:propFile parameter to the directory you want to store the adbagent.tra file and execute:adbagent --propFile




8. Select the processSPLIT_LINE option in the Select Processes to Load window and click the Load Selected button.





Test in TIBCO Designer1. Click the processSPLIT_LINE object on the Project panel and then click the

Input tab in the Configuration panel. Expand the activity input and provide the appropriate value for each field. Click the Apply button to apply the changes.


3. Select the ADBSPLIT_LINESub business object from the left pane of the Adapter Tester window and specify a working directory to store the test data for the adapter in the Working Directory field.








9. Select the default option processSPLIT_LINE in the Select Processes to Load window and click the Load Selected button.






The Results | 37

The Results


1. processSPLIT_LINE — Publishes the data from the Oracle Source tables that comprise the business object. The adapter subscribes to this message on the TIB. The PROCESS_SPLIT_LINEPublisher activity publishes this message. The Inbound data is visible in the Output tab of the PROCESS_SPLIT_LINEPublisher activity.

2. The Green Arrow pointing from the PROCESS_SPLIT_LINEPublisher object to the End object indicates the successful completion of data published from the Inbound SPLIT_LINESub business object.


38 | Chapter 5 Oracle Applications Inbound Business Object (For R12 Only): PROCESS_BOMSub

Chapter 5 Oracle Applications Inbound Business Object (For R12 Only): PROCESS_BOMSub

This example shows how to use the adapter within a TIBCO BusinessWorks process to subscribe to the Inbound PROCESS_BOMSub business object in Oracle Applications. It also demonstrates the PROCESS_PROCESS_BOMPublisher activity on the Inbound PROCESS_BOMSub business object using TIBCO BusinessWorks.


Topics







Example Description

This example illustrates the Subscription service in a TIBCO BusinessWorks scenario. The example has one process – processPROCESS_BOM.

The processPROCESS_BOM example demonstrates the PROCESS_BOMPublisher activity. The PROCESS_BOMPublisher activity publishes the message and the PROCESS_BOMSub business object receives the information.

Once the PROCESS_BOMPublisher activity publishes the employee information, the PROCESS_BOMSub business object subscribes to this message. The Inbound data is visible in the Output tab of the PROCESS_BOMPublisher activity.



Set Up the Example


Using the Preconfigured ExampleRun the following SQL scripts from the SQL*PLus prompt. For more details on these SQL scripts, refer to Chapter 2 of the TIBCO Adapter for Oracle Applications User’s Guide.





5. @common_all.sql


Before starting the example you must import the sample project ZIP file and convert it to a DAT file. Both files must have the same name. To do this, in the TIBCO Designer:


2. Click the ZIP Archive tab and browse to locate the PROCESS_BOMSub.zip file. The file is located in the <adorapps_home>/examples/<EBSVersionNumber>/PROCESS_BOMSub folder.











4. To run this example from the command prompt, export the project as a DAT file using the same name as that of the ZIP file, that is, PROCESS_BOMSub:


b. Enter the Project Name as PROCESS_BOMSub in the Project Name field, and click the Browse button. Specify the path of the directory as: <adorapps_home>/examples/<EBSVersionNumber>/PROCESS_BOMSub where you want to save the local repository DAT file and then click the OK button.












Creating Your Own ExampleIn TIBCO Designer:

1. Open TIBCO Designer and create a new project.

2. Restore the Oracle Applications Adapter window in the Palettes tab. Drag the Oracle Apps Business Object Configuration button and drop it into the Design panel. Rename the object to OracleAppsPROCESS_BOMSub in the Name field of the Configuration panel.




6. Click the OracleAppsPROCESS_BOMSub button in the project panel. You will find six services in the palette panel.

7. Drag the Oracle Applications Inbound Business Object (For R12 Only) button from palette panel and drop it into the design panel.

8. In the Configuration tab, click the PL/SQL API option from the Interface Type drop-down list.


10. Enter the appropriate values for the Name, APPS Username, APPS User Password, APPLSYS User Name, Interface Name, and Overload fields in the Configuration tab. Note that you need to specify the Interface Name field in the format of <packageName>.<methodName>.









11. Click the Browse button at the right hand side of the Overload field. You will see an Input Overload message box. Select the correct option from the Please Select an Existing Overload Value drop-down list and click the OK button.


13. Ensure that the No Wrapper Package Or Function checkbox is unchecked in the API Wrapper Options tab and enter the name of the wrapper in the Wrapper Name field.

14. Use the JPublisher utility to get the wrapper name.

15. Set the appropriate JPublisher classpaths and run the JPublisher utility following the format below:java oracle.jpub.Main -user=<apps_username>/<apps_password> -url=jdbc:oracle:thin:@<servername>:1521:<SID> -plsqlmap=always -plsqlfile=<plsqlfilename> -plsqlpackage=<packagename> -sql=<API_Package_Name> -plsqlonly=<ture_or_false> -dir=<base_Dir_For_Generated_Files>

This command will generate two SQL files that are used to get the procedure names for the wrapper.

16. Log in to the database as APPS. Grant the EXECUTE privilege to the user to access the API that the wrapper is appointed to by execute the following:

GRANT EXECUTE ON BOM_BO_PUB TO <username>;

17. Log in to the database as the adapter user which you granted the privilege in the step above and then execute:CREATE SYNONYM BOM_BO_PUB FOR APPS.BOM_BO_PUB;

where BOM_BO_PUB is a package name.

18. Execute the generated SQL scripts under the current adapter user account.

19. Copy and paste the PL/SQL Package Name into the Wrapper Name field as the first part of the wrapper name.

20. Open the generated SQL and find the package name that you just entered in the Wrapper Name field. Select the desired procedure from the package and paste its name into the Wrapper Name field as the second part of the wrapper name. Do not forget to place a dot to separate the two parts of the wrapper name. Click the Apply button.

21. Specify an exception table name in the Exception Table field (name it as PROCESS_BOM_excep in this example) and click the Apply button.


23. Drag the ActiveDatabase Adapter Configuration button from the palette panel and drop it into the design panel. Rename the object to ADBPROCESS_BOM in the Instance Name field in the Configuration tab.




25. You will get a warning message box saying By default, database objects for your configurations will be created. click the OK button to continue.

26. Select the Design-time Connection tab and enter the correct values in the JDBC URL, User Name, and Password fields in the Design-time Connection tab. Click the Apply button.



29. Select the Adapter Services folder under the ADBPROCESS_BOM folder from the Project panel.


31. Select the button to select a resource. In this example, select the PROCESS_BOMSub object under the OracleAppsPROCESS_BOMSub object as the resource from the Select a Resource... window. Click the OK button to confirm the selection.

32. Click the Apply button to apply the changes. The adapter will generate some SQL scripts in the <adorapps_home>/sql directory.




36. Enter processPROCESS_BOM in the Name field in Configuration tab.

37. Click the processPROCESS_BOM folder in the project panel. Drag the Publish to Adapter button from the palette panel and drop it into the design panel. Rename the object Publish to Adapter as PROCESS_BOMPublisher in the Name field of the Configuration tab.

38. Click the button from the TIBCO Designer menu bar. You need to create two transitions in this example. One is from the Start object to the




PROCESS_BOMPublisher object, the other is from the PROCESS_BOMPublisher object to the End object.

39. Click the button on the right-hand side of the Adapter Service field in the Configuration tab. The Select a Resource window appears.

40. Select the PROCESS_BOMSub object under the ADBPROCESS_BOM > Adapter Services and click the OK button.





Test the Example


In the Configuration tab of the ADBPROCESS_BOM object, if the Write to Database on Save checkbox is not checked, you must manually run the required SQL scripts for the adapter. To do this, perform the following steps.

1. Log in to the database as APPS, grant the EXECUTE privilege to the user to access the API that the wrapper appointed to by execute the following:

GRANT EXECUTE ON BOM_BO_PUB TO <username>;

2. Log in to the database as the adapter user which you grant the privilege in the step above, then execute the followings:CREATE SYNONYM BOM_BO_PUB FOR APPS.BOM_BO_PUB;

where BOM_BO_PUB is a package name.

3. Under the <adorapps_home>/examples/<EBSVersionNumber>/PROCESS_BOMSub/sql directory, execute the generated SQL scripts as listed below using the current adapter user account.

a. Execute the SQL file TIB_ORA_BOM_BO_PUB_drop.sql.

b. Execute the SQL file TIB_ORA_BOM_BO_PUB.sql.

c. Execute the SQL file OracleAppsPROCESS_BOMSub_PROCESS_BOMSub_undo.sql. This file contains the cleanup scripts.

d. Execute the SQL file OracleAppsPROCESS_BOMSub_PROCESS_BOMSub.sql.

Test in the Command Prompt1. Click the processPROCESS_BOM object on the Project panel and then click

the Input tab in the Configuration panel in TIBCO Designer. Expand the activity input, provide the appropriate value for each field, and click the Apply button to apply the changes.


3. Configure the appropriate environment variables. Before using the product, you need to run the adorappssetenv.sh and adbagent_env.sh file, which are stored in the <adorapps_home>/bin directory.



4. Open the adbagent.tra file under the <adorapps_home>/bin directory and modify the parameters as follows:


b. Find tibco.configurl <configurl> in the adbagent.tra file and replace the content within the angle bracket with ADBPROCESS_BOM.







8. Select the processPROCESS_BOM option in the Select Processes to Load window and click the Load Selected button.


9. Switch to the Console tab again and observe the changes.



Test in TIBCO Designer1. Click the processPROCESS_BOM object on the Project panel and then click

the Input tab in the Configuration panel. Expand the activity input, provide the appropriate value for each field, and click the Apply button to apply the changes.




3. Select the ADBPROCESS_BOM business object from the left pane of the Adapter Tester window and specify a working directory to store the test data for the adapter in the Working Directory field.






9. Select the processPROCESS_BOM option in the Select Processes to Load window and click the Load Selected button.






The Results | 49

The Results


1. processPROCESS_BOM — Publishes the data from the Oracle Source tables that comprise the business object. The adapter subscribes to this message on the TIB. The PROCESS_BOMPublisher activity publishes this message. The Inbound data is visible in the Output tab of the PROCESS_BOMPublisher activity.

2. The Green Arrow pointing from the PROCESS_BOMPublisher object to the End object indicates the successful completion of data published from the Inbound PROCESS_BOMSub business object.


50 | Chapter 6 Oracle Applications Inbound Business Object (For R12 Only): WICMLPSub

Chapter 6 Oracle Applications Inbound Business Object (For R12 Only): WICMLPSub

This example shows how to use the adapter within a TIBCO BusinessWorks process to subscribe to the Inbound WICMLPSub business object in Oracle Applications. It also demonstrates the WICMLPPublisher activity on the Inbound WICMLPSub business object using TIBCO BusinessWorks.

This example uses TIBCO JMS as its transport type.

Topics







Example Description

This example illustrates the Subscription service in a TIBCO BusinessWorks scenario. The example has one process – processWICMLP.

The processWICMLP example demonstrates the WICMLPPublisher activity. The WICMLPPublisher activity publishes the message and the WICMLPSub business object receives the information.

Once the WICMLPPublisher activity publishes the employee information, the WICMLPSub business object subscribes to this message. The Inbound data is visible in the Output tab of the WICMLPPublisher activity.



Set Up the Example






3. @create_user.sql (Run this script to create a user with all the required grants and privileges.)


5. @common_all.sql


Before starting the example you must import the sample project ZIP file and convert it to a DAT file. Both files must have the same name. To do this, follow the instructions below. In the TIBCO Designer:


2. Click the ZIP Archive tab and browse to locate the WICMLPSub.zip file. The file is located in the <adorapps_home>/examples/<EBSVersionNumber>/WICMLPSub folder.











4. To run this example from the command prompt, export the project as a DAT file using the same name as that of the ZIP file, that is, WICMLPSub:


b. Enter the Project Name as WICMLPSub in the Project Name field, and click the Browse button. Specify the path of the directory as: <adorapps_home>/examples/<EBSVersionNumber>/WICMLPSub where you want to save the local repository DAT file needs to be saved and then click the OK button.













In TIBCO Designer:

1. Open TIBCO Designer and create a new project.

2. Restore the Oracle Applications Adapter window in the Palettes tab. Drag the Oracle Apps Business Object Configuration button from the palette panel and drop it into the Design panel. Rename the object to OracleAppsWICMLPSub in the Name field of the Configuration panel.


4. Enter the appropriate values in the JDBC URL, Username, and Password fields in the Design Time Connection tab and click the Apply button.


6. Click the OracleAppsWICMLPSub button in the project panel. You will find six services in the palette panel.

7. Drag the Oracle Applications Inbound Business Object (For R12 Only) button from the palette panel and drop it into the design panel.

8. In the Configuration tab, click the Concurrent Program option from the Interface Type drop-down list and click the Apply button.

9. Enter the appropriate values for the Name, APPS Username, APPS User Password, APPLSYS User Name, and Interface Name fields in the Configuration tab. Note that the Interface Name field must be entered in the format of <packageName>.<methodName>. Click the Apply button to apply the object configuration.









10. Click the Browse button at the right hand side of the Username field in the Concurrent Program Options tab. A message box will pop up with a list of usernames. Select the appropriate option from the list and click the OK button.

11. Click the Browse button at the right hand side of the Responsibility Name field in the Concurrent Program Options tab. A message box will pop up with a list of responsibility names. Select the desired responsibility from the list and click the OK button.

12. Click the Apply button to apply the concurrent Program Options configuration.

13. Specify an exception table name in the Exception Table field. For this example, name it as WICMLPSub. Click the Apply button.


15. Drag the ActiveDatabase Adapter Configuration button from the palette panel and drop it into the design panel. Rename the object to ADBWICMLPSub in the Instance Name field in the Configuration tab.



18. Select the Design-time Connection tab, enter the correct values in the JDBC URL, Username, and Password fields in the Design-time Connection tab. Click the Apply button.



21. Select the Adapter Services folder under the ADBWICMLPSub folder from the Project panel.


23. Select the button to select a resource. For this example, select the WICMLPSub object under the OracleAppsWICMLPSub object as the resource from the Select a Resource... window. Click the OK button to confirm the selection.



24. Click the Apply button to apply the changes. The adapter will generate SQL scripts in the <adorapps_home>/sql directory.

25. Select the JMS option from the Transport Type drop-down list in the Configuration tab. Ensure that the TIBCO Enterprise for EMS server is running and accessible to the machine which the adapter is installed before running any processes.



28. Enter processWICMLP in the Name field in the Configuration tab.

29. Click the processWICMLP folder in the project panel. Drag the Publish to Adapter button from the palette panel and drop it into the design panel. Rename the Publish to Adapter object as WICMLPPublisher in the Name field of the Configuration tab.

30. Click the button from the TIBCO Designer menu bar. You will create two transitions in this example. One is from the Start object to the WICMLPPublisher object, the other one is from the WICMLPPublisher object to the End object.

31. Click the button on the right-hand side of the Adapter Service field in the Configuration tab. The Select a Resource window will appear.

32. Select the WICMLPSub object under ADBWICMLPSub > Adapter Services and click the OK button.






Test the Example


In the Configuration tab of the ADBWICMLPSub object, if the Write to Database on Save checkbox is not checked, you must manually run the required SQL scripts for the adapter. To do this, perform the following steps.

1. Execute the SQL file OracleAppsWICMLPSub_WICMLPSub_undo.sql in <adorapps_home>/examples/<EBSVersionNumber>/WICMLPSub/sql. This file contains the cleanup scripts.

2. Execute the SQL file OracleAppsWICMLPSub_WICMLPSub.sql in the same location.

Test in the Command Prompt1. Click the processWICMLP object on the Project panel and then click the Input

tab in the Configuration panel in TIBCO Designer. Expand the activity input and provide the appropriate values for each field. Click the Apply button to apply the changes.


3. Configure the appropriate environment variables to run the adapter. Before using the product, you must execute the adorappssetenv.sh and adbagent_env.sh files, which are stored in the <adorapps_home>/bin directory.

4. Open the adbagent.tra file under the <adorapps_home>/bin directory and modify the parameters as follows.


b. Find tibco.configurl <configurl> in the adbagent.tra file and replace the content within the angle bracket with ADBWICMLPSub.

5. To start the EMS server, execute the tibjmsd.exe file in Windows or execute the ./tibemsd & in UNIX under the <TIBC0_HOME>/JMS/bin directory.









9. Select the processWICMLP option in the Select Processes to Load window and click the Load Selected button.





Test in TIBCO Designer1. To start the EMS server, execute the tibjmsd.exe file in Windows or execute

the ./tibemsd & in UNIX under the <TIBC0_HOME>/JMS/bin directory.

2. Click the processWICMLP object on the Project panel and then click the Input tab in the Configuration panel. Expand the activity input, provide the appropriate value for each field, and click the Apply button to apply the changes.


4. Select the ADBWICMLPSub business object from the left pane of the Adapter Tester window and specify the working directory to store the test data for the adapter in the Working Directory field.








10. Select the default option processWICMLP in the Select Processes to Load window and click the Load Selected button.







The Results


1. processWICMLP — Publishes the data from the Oracle Source tables that comprise the business object. The adapter subscribes to this message on the TIB. The WICMLPPublisher activity publishes this message. The Inbound data is visible in the Output tab of the WICMLPPublisher activity.

2. The Green Arrow from the WICMLPPublisher object to the End object indicates the successful completion of data published from the Inbound WICMLPSub business object.


JPublisher | 61

Chapter 7 JPublisher

This example shows how to use JPublisher to convert complex APIs into simple APIs in Oracle Applications.

Topics






62 | Chapter 7 JPublisher

Example Description

This example illustrates how to use JPublisher to simplify the process for TIBCO Adapter for Oracle Applications.

When TIBCO Adapter for Oracle Applications is dealing with the boolean type or special types (for instance, a type defined within the package instead of the Database), it can be challenging. The JPublisher utility generates PL/SQL scripts automatically and encapsulates related procedures and variables. It acts as a wrapper so that complicated types can be treated as simple APIs.



Set Up the Example

You can follow this example to get the wrapper name using the JPublisher utility.

1. You have to configure the JPublisher utility before use.

2. Copy the runtime12.jar and translator.jar file from the <ORACLE_HOME>/sqlj/lib directory to the jpub/lib directory.

3. Copy the classes12.jar file from the <ORACLE_HOME>/jdbc/lib directory to the jpub/lib directory.

4. Set the appropriate JPublisher classpaths and run the JPublisher utility following the format below:java oracle.jpub.Main -user=<username>/<password> -url=jdbc:oracle:thin:@<servername>:1521:<SID> -plsqlmap=always -plsqlfile=<plsqlfilename> -plsqlpackage=<packagename> -sql=<API_Package_Name> -plsqlonly=<ture_or_false> -dir=<base_Dir_For_Generated_Files>

This command will generate two SQL files that will be used as the procedure name for the wrapper.

5. Log in to the database as APPS. Grant the Execute privilege to the user to access the API that the wrapper is appointed to. Execute the generated SQL scripts under the current adapter user account.

6. Use the PL/SQL Package Name as the first part of the wrapper name.

7. Open the generated SQL scripts and find the package you used in step 6. Select the desired procedure from the package and use its name as the second part of the wrapper name. Do not forget to place a dot to separate the two parts.

The JPublisher utility only applies to the PL/SQL API interface type.



Test the Example


1. Enter the <base_Dir_For_Generated_Files> directory by executing the following command. (This directory has been set previously in the JPublisher command in the -dir parameter. You will find the two generated SQL files in the <base_Dir_For_Generated_Files> directory.)

cd <base_Dir_For_Generated_Files>

2. Execute the following command.

sqlplus <Apps User Id>/ <Apps Password>@<Oracle SID>

3. Execute the Tibco_Generated_Script_drop.sql script to clear the object database and then execute the Tibco_Generated_Script.sql script to test if the script will create the object database.


The Results | 65

The Results


After implementing JPublisher, you will see the two generated SQL script files under the directory you specified. This directory has been set previously in the JPublisher command in the -dir parameter.



| 67

Index

C

customer support xiv, xiv

E

EmployeeSubscriber activity 5, 16, 27, 38, 50

P

Publication Service 2

R

RV xii, xii

S

Subscription Service 2support, contacting xiv, xiv

T

technical support xiv, xivTIBCO documentation xivTIBCO_HOME ixTIBCOmmunity xiv

tibco adapter for oracle applications examples … following documents form the tibco adapter for...

Documents