TIBCO ActiveMatrix BusinessWorks™ Plug-in for Database ...

TIBCO ActiveMatrixBusinessWorks™ Plug-in forDatabase

Examples GuideVersion 8.5.0

February 2022

Copyright © 1999-2022. TIBCO Software Inc. All Rights Reserved.

Contents

Examples Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Importing a Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Data Event Poller Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Data Event Poller: Parent Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Data Event Poller: DB2UDBParent Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Data Event Poller DB2UDBParent: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Data Event Poller DB2UDBParent: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Data Event Poller: MSSQLServerParent Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Data Event Poller MSSQLServerParent: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Data Event Poller MSSQLServerParent: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Data Event Poller: OracleParent Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Data Event Poller OracleParent: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Data Event Poller OracleParent: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Data Event Poller: ParentChild Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Data Event Poller: DB2ParentChild Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Data Event Poller DB2UDBParentChild: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Data Event Poller DB2UDBParentChild: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Data Event Poller: MSSQLServerParentChild Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Data Event Poller MSSQLServerParentChild: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Data Event Poller MSSQLServerParentChild: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Data Event Poller: OracleParentChild Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Data Event Poller OracleParentChild: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Data Event Poller OracleParentChild: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Data Event Poller: PublishByReference Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Data Event Poller: DB2UDBPublishByReference Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Data Event Poller DB2UDBPublishByReference: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Data Event Poller DB2UDBPublishByReference: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Data Event Poller: MSSQLPublishByReference Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Data Event Poller MSSQLServerPublishByReference: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Data Event Poller MSSQLServerPublishByReference: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Data Event Poller: OraclePublishByReference Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Data Event Poller OraclePublishByReference: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Data Event Poller OraclePublishByReference: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Data Merger Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Data Merger: Parent Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Data Merger: DB2UDBDataMergerParent Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Data Merger DB2UDBParent: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

2

TIBCO ActiveMatrix BusinessWorks™ Plug-in for Database Examples Guide

Data Merger DB2UDBParent: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Data Merger: MSSQLServerDataMergerParent Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Data Merger MSSQLServerParent: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

Data Merger MSSQLServerParent: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Data Merger: OracleDataMergerParent Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Data Merger OracleParent: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Data Merger OracleParent: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Data Merger: ParentChild Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Data Merger: DB2UDBDataMergerParentChild Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Data Merger DB2UDBParentChild: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Data Merger DB2UDBParentChild: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Data Merger: MSSQLServerDataMergerParentChild Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Data Merger MSSQLServerParentChild: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Data Merger MSSQLServerParentChild: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Data Merger: OracleDataMergerParentChild Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Data Merger OracleDataMergerParentChild: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Data Merger OracleDataMerger ParentChild: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Data Requester Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Data Requester DB2AS400DataRequester_CustomRPC Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Data Requester DB2AS400DataRequester_CustomRPC: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Data Requester DB2AS400: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Data Requester: MSSQLDataRequester Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Data Requester MSSQLDataRequester: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Data Requester MSSQLDataRequester: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

DataRequester: MSSQLDataRequester_CustomRPC Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

DataRequester MSSQLCustomRPCDataRequester: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

DataRequester: MSSQLCustomRPCDataRequester: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Data Requester: OracleDataRequester Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Data Requester OracleDataRequester: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Data Requester OracleDataRequester: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Data Requester: OracleDataRequester_CustomRPC Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Data Requester OracleDataRequester_CustomRPC: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Data Requester OracleCustomRPCDataRequester: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Data Requester: SybaseDataRequester Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

Data Requester SybaseDataRequester: Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Data Requester SybaseDataRequester: Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

TIBCO Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Legal and Third-Party Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

3


Examples Overview

To help you understand how TIBCO ActiveMatrix BusinessWorks™ Plug-in for Database operates, somesample projects are packaged with the installer.

After the plug-in is installed, the sample projects are available in the TIBCO_HOME\bw\palettes\adb\version_number\samples directory. You must import the sample projects to TIBCO Business Studio™. Tosee more about importing projects, see Importing a Sample Project.

● Sample projects for the Data Event Poller Activity

— Parent - The Data Event Poller activity polls the change in a stage table in a specified time interval.The configuration allows you to generate the required trigger SQL script file to create stage tableand triggers. The following sample projects are provided with the plug-in:

— DB2UDBParent

— MSSQLServerParent

— OracleParent

— ParentChild - The Data Event Poller activity polls the change in a stage table in a specified timeinterval by using the parent-child relationship specified by the user key. The configuration allowsyou to generate the required trigger SQL script file to create stage table and triggers. The followingsample projects are provided with the plug-in:

— DB2UDBParentChild

— MSSQLServerParentChild

— OracleParentChild

— PublishByReference - The Data Event Poller activity polls the change in a stage table in a specifiedtime interval. Only the key values of the changed event are stored in the stage table and data ofother columns is retrieved through the table's join operation. The following sample projects areprovided with the plug-in:

— DB2UDBPublishByReference

— MSSQLPublishByReference

— OraclePublishByReference

● Sample Projects for the Data Merger Activity

— Parent - The Data Merger activity performs the insert, update, and delete operations on the parenttable. The configuration allows you to generate the required exception table SQL script file to createexception tables in the database. If an exception occurs while performing a database operation, therecord is inserted in the created exception or opaque table. The following sample projects areprovided with the plug-in:

— DB2UDBDataMergerParent

— MSSQLServerDataMergerParent

— OracleDataMergerParent

— ParentChild - The Data Merger activity performs the insert, update, and delete operations on theparent-child table. The configuration allows you to generate the required exception table SQL scriptfile to create exception tables in the database. If an exception occurs while performing a databaseoperation on the child table, the record is inserted in the created child exception or opaque table.The following sample projects are provided with the plug-in:

4


— DB2UDBDataMergerParentChild

— MSSQLServerDataMergerParentChild

— OracleDataMergerParentChild

● Sample Projects for the Data Requester Activity

— RR_mode - The Data Requester activity allows an application to submit one or more SQLstatements and procedures to be processed. The plug-in processes the request and returns theresults as a reply.

— RPC_SQLEXECUTE - The Data Requester activity with mode as RPC and operation asSQL_EXECUTE is used to configure the plug-in to act as a remote procedure call server on behalf ofa client with a single SQL statement to be processed.

— RPC_SQLBATCHEXECUTE - The Data Requester activity with mode as RPC and operation asSQL_BATCHEXECUTE is used to configure the plug-in to act as a remote procedure call server onbehalf of a client with a sequence of SQL statements to be processed.

— RR_callprocedure - The Data Requester activity allows an application to submit one or moreprocedures to be processed and is used to configure the plug-in to act as a remote procedure callserver on behalf of a client.

— Custom_RPC - The Data Requester activity allows an application to submit one or more storedprocedures, and functions to be processed and is used to configure the plug-in to act as a remoteprocedure call server on behalf of a client.

The following sample projects are provided with the plug-in:

— DB2AS400_DataRequester_CustomRPC

— MSSQLDataRequester

— MSSQL_DataRequester_CustomRPC

— OracleDataRequester

— Oracle_DataRequester_CustomRPC

— SybaseDataRequester

Importing a Sample ProjectTo run a sample project, you must import the project to TIBCO Business Studio™.

Procedure

1. Start TIBCO Business Studio and click File > Import.

2. In the Import window, expand the General folder, select the Existing Studio Projects into Workspaceitem, and then click Next.

3. To locate the sample, in the Import Projects dialog box, click Browse next to the Select archive file fieldto navigate to the sample.The sample projects are located in the TIBCO_HOME\bw\palettes\adb\version_number\samplesdirectory.

4. In the samples directory, select a sample (for example, select the MSSQLServerParent.zip) and clickOpen.

5. In the Import window, click Finish.The selected project (for example, MSSQLServerParent) is imported to TIBCO Business Studio.

5


Data Event Poller ProjectsThe plug-in includes the following projects for the Data Event Poller activity:

● Parent

● ParentChild

● PublishByReference

Data Event Poller: Parent ProjectsThe plug-in includes the following Parent projects for the Data Event Poller activity.:

● DB2UDBParent

● MSSQLServerParent

● OracleParent

Data Event Poller: DB2UDBParent Project

The DB2UDBParent project contains one process: db2udbparent.PublishParentData process. This projectdemonstrates how the plug-in handles polling of data from a publishing table.

PublishParentData Process

In this example, the DataEventPoller activity polls the data from the publishing table. The following figureshows the PublishParentData process:

6


JDBC Connection Resource

In this example, the JDBC Connection resource is configured as follows:

ADB Configuration Resource

In this example, the ADB Configuration resource is configured as follows:

7


The table schema is defined by using the Schemas tab. The different tabs on the right are shown below.

The Configuration tab:

The Schema tab:

6in

The Options tab:

8


The Child Table Order By tab:

The DB2 tab

Data Event Poller DB2UDBParent: Setting Up the Project

Before running the project, you must set it up.

Prerequisites

● Run the database scripts located in the TIBCO_HOME/bw/palettes/adb/version_number/Samples/Data Event Poller/Parent directory in the following order:

1. DB2UDBParent.cleanup.sql - cleanup script

2. Db2UDBParent.sql - DDL script

9


3. ParentChild_ins_db2udb.sql - insert script

● Import the DB2UDBParent project before setting it up. For more information, see Importing a SampleProject.

Procedure

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

2. Expand the Module Descriptors resource, and then double-click Module Properties.

3. In the Module Properties panel, complete the following tasks:a) Set the value of the userName field as the username of the database.b) Set the value of the password field to access the database.c) Set the value of the dbDriver field to the database driver name. For example:

tibcosoftwareinc.jdbc.db2.DB2Driver

d) Set the value of the dbUrl field to the database URL name. For example:jdbc:tibcosoftwareinc:db2://<host>:<port>;DatabaseName=<dbname>

4. From the menu bar, click File > Save to save the project.

Data Event Poller DB2UDBParent: Running the Project

After setting up the project, you can run it.

Procedure

1. In the Project Explorer view, expand the Module Descriptors resource, and then double-clickComponents.

2. In the Components editor, select the process that you want to run.

3. On the toolbar, click the Save icon.

4. To run the selected process, on the menu bar, click Run > Debug Configurations.

5. In the Debug Configurations dialog box, expand BusinessWorks Application, and then clickBWApplication.

6. In the right panel, click the Applications tab, and then select the check box next todb2udbparent.PublishParentData under DB2UDBParent.application

7. Click Debug to run the process.

8. Click the Stop icon to stop the process.

Result

When the PublishParentData process runs successfully, it polls the data from the publishing table.

10


Data Event Poller: MSSQLServerParent Project

The MSSQLServerParent project contains one process: mssqlserverparent.PublishParentData process.This project demonstrates how the plug-in polls data from the publishing table.



11






The table schema is defined by using the Schema tab. The different tabs on the right are shown below.


12


The Schema tab:

The Options tab:


Data Event Poller MSSQLServerParent: Setting Up the Project


13


Prerequisites


1. MSSQLServerParent.cleanup.sql - cleanup script

2. MSSQLServerParent.sql - DDL script

3. Parent_ins_ms.sql - insert script

● Import the MSSQLServerParent project before setting it up. For more information, see Importing aSample Project.

Procedure




tibcosoftwareinc.jdbc.sqlserver.SQLServerDriver

d) Set the value of the dbUrl field to the database URL name. For example:jdbc:tibcosoftwareinc:sqlserver://<host>:<port>;DatabaseName=<dbname>

e) Set the value of the dbSchema field to the default schema name.


Data Event Poller MSSQLServerParent: Running the Project


Procedure






6. In the right panel, click the Applications tab, and then select the check box next tomssqlserverparent.PublishParentData under MSSQLServerParent.application.



Result


14


Data Event Poller: OracleParent Project

The OracleParent project contains one process: oracleparent.PublishParentData process. The projectshows how the plug-in handles polling of data from publishing table.





15






16


The Schema tab:

6in

The Options tab:


17


Data Event Poller OracleParent: Setting Up the Project


Prerequisites


1. OracleParent.cleanup.sql - cleanup script

2. OracleParent.sql - DDL script

3. Parent_ins_ora.sql - insert script● Import the OracleParent project before setting it up. For more information, see Importing a Sample

Project.

Procedure




tibcosoftwareinc.jdbc.oracle.OracleDriver

d) Set the value of the dbUrl field to the database URL name. For example:jdbc:tibcosoftwareinc:oracle://<host>:<port>;ServiceName=<serviceName>


Data Event Poller OracleParent: Running the Project


Procedure


18






6. In the right panel, click the Applications tab, and then select the check box next tooracleparent.PublishParentData under OracleParent.application



Result


Data Event Poller: ParentChild ProjectThe plug-in includes the following ParentChild projects for the Data Event Poller activity:

● DB2UDBParentChild

● MSSQLServerParentChild

● OracleParentChild

Data Event Poller: DB2ParentChild Project

The DB2UDBParentChild project contains one process: db2udbparentchild.PublishParentChildDataprocess. This project demonstrates how the plug-in handles polling of data from publishing table.

PublishParentChildData Process

In this example, the DataEventPoller activity polls data from the publishing table and corresponding datafrom the child table. The following figure shows the PublishParentChildData process:

19






20




The Schema tab:

21


The Options tab:


The DB2 tab

22


Data Event Poller DB2UDBParentChild: Setting Up the Project


Prerequisites

● Run the database scripts located in the TIBCO_HOME/bw/palettes/adb/version_number/Samples/Data Event Poller/ParentChild directory in the following order:

1. DB2UDBParentChild.cleanup.sql – cleanup script

2. DB2UDBParentChild.sql – DDL script

● Import the DB2UDBParentChild project before setting it up. For more information, see Importing aSample Project.

Procedure








Data Event Poller DB2UDBParentChild: Running the Project


Procedure



23





6. In the right panel, click the Applications tab, and then select the check box next todb2udb_parentchild.PublishParentData under DB2UDB_ParentChild.application.



Result

When the PublishParentChildData process runs successfully, it polls the data from the publishing table andthe child table.

Data Event Poller: MSSQLServerParentChild Project

The MSSQLServerParentChild project contains one process: mssqlserverparentchild.PublishParentChildData process. This project demonstrates how the plug-in handles polling of data fromthe publishing table. The corresponding data from the child table is also fetched.


In this example, the DataEventPoller activity polls the data from the publishing table. The correspondingdata from the child table is also fetched. The following figure shows the PublishParentChildData process:

24






25




The Schema tab:

26


The Options tab:

27



Data Event Poller MSSQLServerParentChild: Setting Up the Project


Prerequisites


1. MSSQLServerParentChild.cleanup.sql – cleanup script

2. MSSQLServerParentChild.sql – DDL script

3. ParentChild_ins_ms.sql – insert script

● Import the MSSQLServerParentChild project before setting it up. For more information, see Importinga Sample Project.

Procedure








28


Data Event Poller MSSQLServerParentChild: Running the Project


Procedure






6. In the right panel, click the Applications tab, and then select the check box next toMSSQLServerParentChild.application.



Result


29


30


Data Event Poller: OracleParentChild Project

The OracleParentChild project contains one process: oracleparentchild.PublishParentChildDataprocess. This project demonstrates how the plug-in handles polling of data from publishing table.


In this example, the DataEventPoller activity polls data from the publishing table and corresponding datafrom the child table. The following figure shows the PublishParentChildData process:





31




The Schema tab:

32


The Options tab:

33



Data Event Poller OracleParentChild: Setting Up the Project


Prerequisites


1. OracleParentChild.cleanup.sql – cleanup script

2. OracleParentChild.sql – DDL script

3. ParentChild_ins_ora.sql – insert script

● You have to import the OracleParentChild project before setting it up. For more information, see Importing a Sample Project.

Procedure







34


Data Event Poller OracleParentChild: Running the Project


Procedure






6. In the right panel, click the Applications tab, and then select the check box next toOracleParentChild.application.



Result


35


Data Event Poller: PublishByReference ProjectThe plug-in includes the following PublishByReference projects for the Data Event Poller activity:

● DB2UDBPublishByReference

● MSSQLPublishByReference

● OraclePublishByReference

Data Event Poller: DB2UDBPublishByReference Project

The MSSQLPublishByReference project contains one process: db2udbpublishbyreference.PubByRefprocess. This project demonstrates how the plug-in handles polling of data from a referenced object.

PubByRef Process

In this example, the DataEventPoller activity polls the data from the referenced object. The following figureshows the PubByRef process:

36






37




The Schema tab:

The Options tab:

38



The DB2 tab:

Data Event Poller DB2UDBPublishByReference: Setting Up the Project


39


Prerequisites

● Run the database scripts located in the TIBCO_HOME/bw/palettes/adb/version_number/Samples/Data Event Poller/PublishByReference directory in the following order:

1. DB2UDBPubByRef.cleanup.sql – cleanup script

2. DB2UDBPubByRef.sql – DDL script

3. pubbyref_ins_db2udb.sql – insert script

● Import the DB2UDBPublishByReference project before setting it up. For more information, see Importing a Sample Project.

Procedure








Data Event Poller DB2UDBPublishByReference: Running the Project


Procedure






6. In the right panel, click the Applications tab, and then select the check box next todb2udbpublishbyreference.PubByRef under DB2UDBPublishByReference.application.



Result

When the PubByRef process runs successfully, it polls the data from the publishing table and the childtable.

40


Data Event Poller: MSSQLPublishByReference Project

The MSSQLPublishByReference project contains one process: mssqlpublishbyreference.PubByRefprocess. This project demonstrates how the plug-in handles polling of data from referenced object.

PubByRef Process




41






The Schema tab:

42


The Options tab:


Data Event Poller MSSQLServerPublishByReference: Setting Up the Project


Prerequisites


1. MSSQLPubByRef.cleanup.sql – cleanup script

2. MSSQLPubByRef.sql – DDL script

3. pubbyref_ins_ms.sql – insert script

● Import the MSSQLPublishByReference project before setting it up. For more information, see Importinga Sample Project.

43


Procedure








Data Event Poller MSSQLServerPublishByReference: Running the Project


Procedure






6. In the right panel, click the Applications tab, and then select the check box next tomssqlserverpublishbyreference.PubByRef under MSSQLPublishByReference.application.



Result

When the PubByRef process runs successfully, it polls the data from the publishing table and the childtable.

44


Data Event Poller: OraclePublishByReference Project

The OraclePublishByReference project contains one process: oraclepublishbyreference.PubByRefprocess. This project demonstrates how the plug-in handles polling of data from a referenced object.

PubByRef Process




45




The table schema is defined by using the Schemas tab. The different tabs on the right are shown below


The Schema tab:

46


The Options tab:


Data Event Poller OraclePublishByReference: Setting Up the Project


Prerequisites


47


1. OraclePubByRef.cleanup.sql – cleanup script

2. OraclePubByRef.sql – DDL script

3. pubbyref_ins_ora.sql – insert script

● Import the OraclePublishByReference project before setting it up. For more information, see Importing aSample Project.

Procedure







Data Event Poller OraclePublishByReference: Running the Project


Procedure






6. In the right panel, click the Applications tab, and then select the check box next tooraclepublishbyreference.OraclePubByRefOraclePublishByReference.application.



Result

When the PubByRef process runs successfully, it polls the data from the referenced object.

48


Data Merger ProjectsThe plug-in includes the following projects for the Data Merger activity:

● Parent

● ParentChild

Data Merger: Parent ProjectsThe plug-in includes the following Parent projects for the Data Merger activity:

● DB2UDBDataMergerParent

● MSSQLServerDataMergerParent

● OracleDataMergerParent

Data Merger: DB2UDBDataMergerParent Process

The DB2UDBDataMergerParent project contains one process: db2udbdatamergerparent.ParentDataprocess. This process demonstrates how the plug-in inserts data in the parent table.

ParentData Process

The following figure shows the ParentData process:

49






50




The Schema tab:

The Options tab:

The Child Exception Table Mappings tab:

51


The DB2 tab:

Data Merger DB2UDBParent: Setting Up the Project


Prerequisites

● Run the database script - DB2UDB_DataMerger_Parent.sql, located in the TIBCO_HOME/bw/palettes/adb/version_number/Samples/Data Merger/Parent directory.

● Import the DB2UDBDataMergerParent project before setting it up. For more information, see Importinga Sample Project.

Procedure







Data Merger DB2UDBParent: Running the Project


52


Procedure


2. In the Components editor, select the process that you want to run.3. On the toolbar, click the Save icon.4. To run the selected process, on the menu bar, click Run > Debug Configurations.5. In the Debug Configurations dialog box, expand BusinessWorks Application, and then click

BWApplication.6. In the right panel, click the Applications tab, and then select the check box next to

db2udbdatamergerparent.ParentData under DB2UDBDataMergerParent.application7. Click Debug to run the process.8. Click the Stop icon to stop the process.

Result

When the ParentData process runs successfully, it inserts the data to the parent table.

53


Data Merger: MSSQLServerDataMergerParent Process

The MSSQLServerDataMergerParent project contains one process: mssqldatamergerparent.ParentDataprocess. This process demonstrates how the plug-in inserts data in the parent table.

ParentData Process






54




The Schema tab:

The Options tab:

55



Data Merger MSSQLServerParent: Setting Up the Project


Prerequisites

● Run the database script - MSSQLServer_DataMerger_Parent.sql, located in the TIBCO_HOME/bw/palettes/adb/version_number/Samples/Data Merger/Parent directory.

● Import the MSSQLServerDataMergerParent project before setting it up. For more information, see Importing a Sample Project.

Procedure








56


Data Merger MSSQLServerParent: Running the Project


Procedure






6. In the right panel, click the Applications tab, and then select the check box next tomssqlserverdatamergerparent.ParentData under MSSQLServerDataMergerParent.application.



Result

When the ParentData process runs successfully, it inserts the data in the parent table.

Data Merger: OracleDataMergerParent Process

The OracleDataMergerParent project contains one process: oracledatamergerparent.ParentDataprocess. This process demonstrates how the plug-in inserts data in the parent table.

ParentData Process


57






58




The Schema tab:

The Options tab:


59


Data Merger OracleParent: Setting Up the Project


Prerequisites

● Run the database script - Oracle_DataMerger_Parent.sql, located in the TIBCO_HOME/bw/palettes/adb/version_number/Samples/Data Merger/Parent directory.

● Import the OracleDataMergerParent project before setting it up. For more information, see Importinga Sample Project.

Procedure

1. Expand the imported project in the Project Explorer view.2. Expand the Module Descriptors resource, and then double-click Module Properties.3. In the Module Properties panel, complete the following tasks:

a) Set the value of the userName field as the username of the database.b) Set the value of the password field to access the database.c) Set the value of the dbDriver field to the database driver name. For example:




Data Merger OracleParent: Running the Project


Procedure


2. In the Components editor, select the process that you want to run.3. On the toolbar, click the Save icon.4. To run the selected process, on the menu bar, click Run > Debug Configurations.5. In the Debug Configurations dialog box, expand BusinessWorks Application, and then click

BWApplication.6. In the right panel, click the Applications tab, and then select the check box next to

oracledatamergerparent.ParentData under OracleDataMergerParent.application.

60




Result

When the ParentData process runs successfully, it inserts the data to the parent table.

Data Merger: ParentChild ProjectsThe plug-in includes the following ParentChild projects for the Data Merger activity:

● DB2UDBDataMergerParentChild

● MSSQLServerDataMergerParentChild

● OracleDataMergerParentChild

Data Merger: DB2UDBDataMergerParentChild Project

The DB2UDBDataMergerParentChild project contains one process:db2udbdatamergerparentchild.ParentChildData process. This process demonstrates how the plug-ininserts data in the parent table and the child table.

ParentChildData Process

The following figure shows the ParentChildData process:

61






62




The Schema tab:

63


The Options tab:

64


The Child Exception Table Mapping tab:

The DB2 tab:

Data Merger DB2UDBParentChild: Setting Up the Project


Prerequisites

● Run the database script - DB2UDB_DataMerger_ParentChild.sql, located in the TIBCO_HOME/bw/palettes/adb/version_number/Samples/Data Merger/ParentChild directory.

● Import the DB2UDBDataMergerParentChild project before setting it up. For more information, see Importing a Sample Project.

Procedure




65




Data Merger DB2UDBParentChild: Running the Project


Procedure






6. In the right panel, click the Applications tab, and then select the check box next todb2udbdatamergerparentchild.ParentChildData underDB2UDBDataMergerParentChild.application.



Result

When the ParentChildData process runs successfully, it inserts the data to the parent table and the childtable.

66


Data Merger: MSSQLServerDataMergerParentChild Project

The MSSQLServerDataMergerParentChild project contains one processmssqldatamergerparentchild.ParentChildData process. This project demonstrates how the plug-inhandles inserting of data in the parent table and the child table.


In this example, the Data Merger activity inserts data in the parent table and the child table. The followingfigure shows the ParentChildData process:

67






68




The Schema tab:

69


The Options tab:

70


The Child Exception Table Mapping tab:

Data Merger MSSQLServerParentChild: Setting Up the Project


Prerequisites

● Run the database script - MSSQLServer_ParentChild.sql located in the TIBCO_HOME/bw/palettes/adb/version_number/Samples/Data Merger/ParentChild directory.

● Import the MSSQLServerDataMergerParentChild project before setting it up. For more information, see Importing a Sample Project.

Procedure





e) Set the value of the dbSchema field to the default schema name.4. From the menu bar, click File > Save to save the project.

Data Merger MSSQLServerParentChild: Running the Project


Procedure


71






6. In the right panel, click the Applications tab, and then select the check box next tomssqlserverdatamergerparentchild.ParentChildData underMSSQLServerDataMergerParentChild.application.



Result

When the ParentChildData process runs successfully, it inserts data in the parent table and the child table.

Data Merger: OracleDataMergerParentChild Project

The OracleDataMergerParentChild project contains one process:oracledatamergerparentchild.ParentChildData process. This process demonstrates how the plug-ininserts data in the parent table and the child table.

72



The following figure shows the ParentChildData process:





73




The Schema tab:

74


The Options tab:

75



Data Merger OracleDataMergerParentChild: Setting Up the Project


Prerequisites

● Run the database script - Oracle_DataMerger_ParentChild.sql, located in the TIBCO_HOME/bw/palettes/adb/version_number/Samples/Data Merger/ParentChild directory in the followingorder:

● You have to import the OracleDataMergerParentChild project before setting it up. For moreinformation, see Importing a Sample Project.

Procedure






Data Merger OracleDataMerger ParentChild: Running the Project


Procedure


76






6. In the right panel, click the Applications tab, and then select the check box next tooracledatamergerparentchild.ParentChildData underOracleDataMergerParentChild.application



Result

When the ParentChildData process runs successfully, it inserts the data to the parent table.

77


Data Requester ProjectsThe plug-in includes the following projects for the Data Requester activity:

● DB2AS400DataRequester_CustomRPC

● MSSQLDataRequester

● MSSQLDataRequester_CustomRPC

● OracleDataRequester

● OracleDataRequester_CustomRPC

● SybaseDataRequester

Data Requester DB2AS400DataRequester_CustomRPC ProjectThe DB2AS400DataRequester_CustomRPC project contains three processes demonstrating remoteprocedure call mode using stored procedures and functions.

The processes in this project are:

● Execute_procedure_GETPRICE

● Execute_procedure_PARAMTEST

● Execute_procedure_SETDESCRIPTION



ADB Connection Resource


78


The Configuration tab is used to specify the mode and to select custom operations. The structure of theselected stored procedure is displayed on the Schema tab. In the following figure, RPC mode with customoperations has been selected.

Execute_procedure_GETPRICE Process

The following figure shows the General tab of the Execute_procedure_GETPRICE process:

Execute_procedure_PARAMTEST Process

The following figure shows the General tab of the Execute_procedure_PARAMTEST process:

79


Execute_procedure_SETDESCRIPTION Process

The following figure shows the General tab of the Execute_procedure_SETDESCRIPTION process:

Data Requester DB2AS400DataRequester_CustomRPC: Setting Up the Project


Prerequisites

● Run the database script - DB2AS400_DataRequester_CustomRPC.sql, located in the TIBCO_HOME/bw/palettes/adb/version_number/Samples/Data Requester/Parent directory.

● Import the DB2AS400_DataRequester_CustomRPC project before setting it up. For more information, see Importing a Sample Project.

Procedure





80




Data Requester DB2AS400: Running the Project


Procedure






6. In the right panel, click the Applications tab, and then underDB2AS400_DataRequester_customRPC.application select the check box next to the process you wantto run.



Result

When the Execute_procedure_GETPRICE process runs successfully, it returns the price of the item whoseID you have provided as input.

When the Execute_procedure_PARAMTEST process runs successfully, it returns the informationcorresponding to the input you have provided.

81


When the Execute_procedure_SETDESCRIPTION process runs successfully, it updates the database withthe information you have provided as input.

Data Requester: MSSQLDataRequester ProjectThe MSSQLDataRequester project contains three processes demonstrating remote procedure call mode andthe request reply mode. They also demonstrate SQL batch execute and SQL execute operations.


● RequestReply

● RPC_SQLBATCHEXECUTE

● RPC_SQLEXECUTE



82




The Configuration tab is used to configure the schema. In the following figure, RPC mode has beenselected.

83


RequestReply Process

The following figure shows the General tab of the RequestReply process:

RPC_SQLBATCHEXECUTE Process

The following figure shows the General tab of the RPC_SQLBATCHEXECUTE process:

RPC_SQLEXECUTE Process

The following figure shows the General tab of the RPC_SQLEXECUTE process:

84


Data Requester MSSQLDataRequester: Setting Up the Project


Prerequisites

● Run the database script - MSSQLDataRequester.sql, located in the TIBCO_HOME/bw/palettes/adb/version_number/Samples/Data Requester directory.

● Import the MSSQL_DataRequester project before setting it up. For more information, see Importing aSample Project.

Procedure




tibcosoftwareinc.jdbc.mssql.SQLServerDriver.d) Set the value of the dbUrl field to the database URL name. For example:

jdbc:tibcosoftwareinc:sqlserver://<host>:<port>;DatabaseName=<databaseName>


Data Requester MSSQLDataRequester: Running the Project


Procedure






6. In the right panel, click the Applications tab, and then under MSSQLDataRequester.application,select the check box next to the process you want to run.



Result

After the RequestReply process runs successfully, its input and output can be seen as follows:

85


After the RPC_SQLBATCHEXECUTE process runs successfully, its input and output can be seen as follows:

After the RPC_SQLEXECUTE process runs successfully, its input and output can be seen as follows:

86


DataRequester: MSSQLDataRequester_CustomRPC ProjectThe MSSQLDataRequester_CustomRPC project contains four processes demonstrating remote procedurecall mode using stored procedures and functions.


● Execute_procedure_EMPLOYEEDATA








87


The Configuration tab is used to configure the schema. In the following figure, RPC mode with customoperations has been selected.

Execute_procedure_EMPLOYEEDATA Process

The following figure shows the General tab of the Execute_procedure_EMPLOYEEDATA process:



88






DataRequester MSSQLCustomRPCDataRequester: Setting Up the Project


Prerequisites

● Run the database script - MSSQLDataRequester_CustomRPC.sql, located in the TIBCO_HOME/bw/palettes/adb/version_number/Samples/Data Requester directory.

● Import the MSSQL_DataRequester project before setting it up. For more information, see Importing aSample Project.

89


Procedure




tibcosoftwareinc.jdbc.mssql.SQLServerDriver.d) Set the value of the dbUrl field to the database URL name. For example:

jdbc:tibcosoftwareinc:oracle://<host>:<port>;ServiceName=<serviceName>


DataRequester: MSSQLCustomRPCDataRequester: Running the Project


Procedure






6. In the right panel, click the Applications tab, and then underMSSQL_DataRequester_CustomRPC.application, select the check box next to the process you want torun.



Result

After the Execute_procedure_EMPLOYEEDATA process runs successfully, its input and output can be seen asfollows:

90


After the Execute_procedure_GETPRICE process runs successfully, its input and output can be seen asfollows:

After the Execute_procedure_PARAMTEST process runs successfully, its input and output can be seen asfollows:

After the Execute_procedure_SETDESCRIPTION process runs successfully, its input and output can be seenas follows:

91


Data Requester: OracleDataRequester ProjectThe OracleDataRequester project contains four processes demonstrating remote procedure call mode andthe request reply mode. They also demonstrate SQL batch execute and SQL execute operations.


● RPC_SQLBATCHEXECUTE

● RPC_SQLEXECUTE

● RR_callprocedure

● RR_mode





92


The Configuration tab is used to configure the schema. In the following figure, RPC mode has beenselected.

RPC_SQLBATCHEXECUTE Process

The following figure shows the General tab of the RPC_SQLBATCHEXECUTE process:

93


RPC_SQLEXECUTE Process

The following figure shows the General tab of the RPC_SQLEXECUTE process:

RR_callprocedure Process

The following figure shows the General tab of the RR_callprocedure process:

RR_mode Process

The following figure shows the General tab of the RR_mode process:

94


Data Requester OracleDataRequester: Setting Up the Project


Prerequisites

● Run the database script - OracleDataRequester.sql, located in the TIBCO_HOME/bw/palettes/adb/version_number/Samples/Data Requester directory.

● Import the Oracle_DataRequester project before setting it up. For more information, see Importing aSample Project.

Procedure







Data Requester OracleDataRequester: Running the Project


Procedure





95



6. In the right panel, click the Applications tab, and then under OracleDataRequester.applicationselect the check box next to the process you want to run.



Result

After the RPC_SQLBATCHEXECUTE process runs successfully, its input and output can be seen as follows:

After the RPC_SQLEXECUTE process runs successfully, its input and output can be seen as follows:

96


After the RR_callprocedure process runs successfully, its input and output can be seen as follows:

After the RR_mode process runs successfully, its input and output can be seen as follows:

Data Requester: OracleDataRequester_CustomRPC ProjectThe OracleDataRequester_CustomRPC project contains four processes demonstrating remote procedurecall mode using stored procedures and functions.


● Execute_procedure_FINDORDERS




97






The structure of the selected stored procedure is displayed on the Schema tab. The Configuration tab isused to specify the mode and to select custom operations. In the following figure, RPC mode with customoperations has been selected.

98


Execute_procedure_FINDORDERS Process

The following figure shows the General tab of the Execute_procedure_FINDORDERS process:



99






100


Data Requester OracleDataRequester_CustomRPC: Setting Up the Project


Prerequisites

● Run the database script - OracleDataRequester_CustomRPC.sql, located in the TIBCO_HOME/bw/palettes/adb/version_number/Samples/Data Requester directory.

● Import the Oracle_DataRequester_CustomRPC project before setting it up. For more information, see Importing a Sample Project.

Procedure







Data Requester OracleCustomRPCDataRequester: Running the Project


Procedure






6. In the right panel, click the Applications tab, and then underOracle_DataRequester_CustomRPC.application select the check box next to the process you want torun.



Result

After the Execute_procedure_FINDORDERS process runs successfully, its input and output can be seen asfollows:

101


After the Execute_procedure_GETPRICE process runs successfully, its input and output can be seen asfollows:

After the Execute_procedure_PARAMTEST process runs successfully, its input and output can be seen asfollows:

102


After the Execute_procedure_SETDESCRIPTION process runs successfully, its input and output can be seenas follows:

Data Requester: SybaseDataRequester ProjectThe SybaseDataRequester project contains one process demonstrating the request reply mode.



For more information about configuring a custom JDBC driver for Sybase, see "Configuring SybaseDatabase by Using Custom JDBC Driver" in TIBCO ActiveMatrix BusinessWorks™ Plug-in for Database User'sGuide.



103


The table schema is defined by using the Schema tab. The Configuration tab is used to configure theschema. In the following figure, the Request Reply mode.

Process Process

The following figure shows the General tab of the Process process:

104


Data Requester SybaseDataRequester: Setting Up the Project


Prerequisites

● Run the database script - SybaseDataRequester.sql, located in the TIBCO_HOME/bw/palettes/adb/version_number/Samples/Data Requester directory.

● Import the Sybase_DataRequester project before setting it up. For more information, see Importing aSample Project.

Procedure



3. In the Module Properties panel, complete the following tasks:a) Set the value of the userName field as the username of the database.b) Set the value of the password field to access the database.c) Set the value of the dbDriver field to the database driver name. For example: custom.jdbc.driver.

For more information about setting up the database driver, see "Configuring Sybase Database usingCustom JDBC Driver" in the TIBCO ActiveMatrix BusinessWorks™ Plug-in for Database User's Guide.

d) Set the value of the dbUrl field to the database URL name. For example:jdbc:tibcosoftwareinc:sybase://<host>:<port>;DatabaseName=<DatabaseName>


Data Requester SybaseDataRequester: Running the Project


Procedure






6. In the right panel, click the Applications tab, and then under SybaseDataRequester.applicationselect the check box next to the process you want to run.



Result

After the Process process runs successfully, its input and output can be seen as follows:

105


106


TIBCO Documentation and Support Services

How to Access TIBCO Documentation

Documentation for TIBCO products is available on the TIBCO Product Documentation website, mainly inHTML and PDF formats.The website is updated frequently and is more current than any other documentation included with theproduct.

Product-Specific Documentation

The following documents for this product are available on the TIBCO ActiveMatrix BusinessWorks™ Plug-in for Database Product Documentation page.

● TIBCO ActiveMatrix BusinessWorks Plug-in for Database Release Notes

● TIBCO ActiveMatrix BusinessWorks Plug-in for Database Installation

● TIBCO ActiveMatrix BusinessWorks Plug-in for Database User's Guide

● TIBCO ActiveMatrix BusinessWorks Plug-in for Database Examples

The following documents provide additional information and can be found on the TIBCO ProductDocumentation website:

● TIBCO ActiveMatrix BusinessWorks documentation

● TIBCO Enterprise Administrator documentation

How to Contact TIBCO Support

Get an overview of TIBCO Support. You can contact TIBCO Support in the following ways:

● For accessing the Support Knowledge Base and getting personalized content about products you areinterested in, visit the TIBCO Support website.

● For creating a Support case, you must have a valid maintenance or support contract with TIBCO. Youalso need a user name and password to log in to TIBCO Support website. If you do not have a username, you can request one by clicking Register on the website.

How to Join TIBCO Community

TIBCO Community is the official channel for TIBCO customers, partners, and employee subject matterexperts to share and access their collective experience. TIBCO Community offers access to Q&A forums,product wikis, and best practices. It also offers access to extensions, adapters, solution accelerators, andtools that extend and enable customers to gain full value from TIBCO products. In addition, users cansubmit and vote on feature requests from within the TIBCO Ideas Portal. For a free registration, go to TIBCO Community.

107


https://docs.tibco.com/

https://docs.tibco.com/products/tibco-activematrix-businessworks-plug-in-for-database

https://docs.tibco.com/products/tibco-activematrix-businessworks-plug-in-for-database

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

https://support.tibco.com/

https://support.tibco.com/

https://ideas.tibco.com/

https://community.tibco.com

Legal and Third-Party Notices

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCHEMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (ORPROVIDE 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 AND CONDITIONSOF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSEAGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USERLICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THESOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCHSOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THELICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT ISSUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTEACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.

This document is subject to U.S. and international copyright laws and treaties. No part of this documentmay be reproduced in any form without the written authorization of TIBCO Software Inc.

TIBCO, the TIBCO logo, the TIBCO O logo, ActiveMatrix BusinessWorks, Business Studio, TIBCO BusinessStudio, and TIBCO ActiveMatrix BusinessWorks Plug-in for Database are either registered trademarks ortrademarks of TIBCO Software Inc. in the United States and/or other countries.

Java and all Java based trademarks and logos are trademarks or registered trademarks of Oracle and/or itsaffiliates.

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, not all operating system platformsfor a specific software version are released at the same time. See the readme.txt file for the availability ofthis software version on a specific operating system platform.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, 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 WILLBE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKEIMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBEDIN 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, INCLUDINGBUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

This and other products of TIBCO Software Inc. may be covered by registered patents. Please refer toTIBCO's Virtual Patent Marking document (https://www.tibco.com/patents) for details.

Copyright © 1999-2022. TIBCO Software Inc. All Rights Reserved.

108


https://www.tibco.com/patents

TIBCO ActiveMatrix BusinessWorks™ Plug-in for Database ...

Documents