TIBCO ActiveMatrix BusinessWorks ... - TIBCO Documentation

TIBCO ActiveMatrix BusinessWorks™ Plug-infor DatabaseUser's GuideSoftware Release 8.0December 2017

Two-Second Advantage®

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCHEMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (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 ANDCONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTEDSOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THECLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOADOR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE)OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USERLICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THESOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, ANDYOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BEBOUND BY THE SAME.

ANY SOFTWARE ITEM IDENTIFIED AS THIRD PARTY LIBRARY IS AVAILABLE UNDERSEPARATE SOFTWARE LICENSE TERMS AND IS NOT PART OF A TIBCO PRODUCT. AS SUCH,THESE SOFTWARE ITEMS ARE NOT COVERED BY THE TERMS OF YOUR AGREEMENT WITHTIBCO, INCLUDING ANY TERMS CONCERNING SUPPORT, MAINTENANCE, WARRANTIES,AND INDEMNITIES. DOWNLOAD AND USE THESE ITEMS IS SOLELY AT YOUR OWNDISCRETION AND SUBJECT TO THE LICENSE TERMS APPLICABLE TO THEM. BY PROCEEDINGTO DOWNLOAD, INSTALL OR USE ANY OF THESE ITEMS, YOU ACKNOWLEDGE THEFOREGOING DISTINCTIONS BETWEEN THESE ITEMS AND TIBCO PRODUCTS.

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

TIBCO, Two-Second Advantage, TIBCO ActiveMatrix BusinessWorks, TIBCO Business Studio, TIBCOActiveMatrix BusinessWorks Plug-in for Database are either registered trademarks or trademarks ofTIBCO Software Inc. in the United States and/or other countries.

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

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

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

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

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

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

2

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

Copyright © 1999-2017 TIBCO Software Inc. All rights reserved.

TIBCO Software Inc. Confidential Information

3


Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

TIBCO Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Comparison between Adapter and Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Creating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Creating a JDBC Connection Shared Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Creating an ADB Configuration Shared Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Configuring a Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Testing a Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Deploying Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Generating an EAR File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

ADB Configuration Shared Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

User Interface Elements of the ADB Configuration Shared Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Creating a Schema Using the ADB Configuration Shared Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Adding a Shared Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Adding a Parent Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Adding a Child Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Setting Up a Relation Between Parent and Child Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Refresh the Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Specify the Columns of an Order By Clause for a Child Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Publishing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Child Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

ADB Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Data Event Poller Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Importing a Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Parent Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

MSSQLServerParent Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Setting Up the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

OracleParent Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39


Running the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

ParentChild Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

MSSQLServerParentChild Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4




OracleParentChild Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51



PublishByReference Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

MSSQLPublishByReference Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58



OraclePublishByReference Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63



Advanced Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Output Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Mapping: Adapter Datatype to Plug-in XSD Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Mapping: MSSQL Datatype to XSD Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Mapping: Oracle Datatype to XSD Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Fault Tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Enabling Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Disabling Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Unlocking the MUTEX Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Entity Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Managing Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Setting Up Log Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Exporting Logs to a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

5


Figures

ADB Configuration shared resource: Connection Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

ADB Configuration shared resource: Schemas Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

ADB Configuration shared resource: Connection Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

ADB Configuration shared resource: Schemas Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Data Event Poller Activity: Fault Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

6


TIBCO Documentation and Support Services

How to Access TIBCO Documentation

Documentation for TIBCO products is available on the TIBCO Product Documentation website, mainlyin HTML and PDF formats.

The TIBCO Product Documentation website is updated frequently and is more current than any otherdocumentation included with the product. To access the latest documentation, visit https://docs.tibco.com.

Documentation for TIBCO ActiveMatrix BusinessWorks™ Plug-in for Database is available on the TIBCO ActiveMatrix BusinessWorks™ Plug-in for Database Product Documentation page.

Product-Specific Documentation

The following documents for this product can be found on the TIBCO Documentation site:

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

● TIBCO ActiveMatrix BusinessWorks Plug-in for Database Installation

● TIBCO ActiveMatrix BusinessWorks Plug-in for Database Release Notes

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

You can contact TIBCO Support in the following ways:

● For an overview of TIBCO Support, visit http://www.tibco.com/services/support.

● For accessing the Support Knowledge Base and getting personalized content about products you areinterested in, visit the TIBCO Support portal at https://support.tibco.com.

● For creating a Support case, you must have a valid maintenance or support contract with TIBCO.You also need a user name and password to log in to https://support.tibco.com. If you do not have auser name, 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 https://community.tibco.com.

7


https://docs.tibco.com

https://docs.tibco.com

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

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

https://support.tibco.com

https://support.tibco.com

https://ideas.tibco.com/

https://community.tibco.com

Product Overview

TIBCO ActiveMatrix BusinessWorks™ Plug-in for Database is an add-on product for TIBCOActiveMatrix BusinessWorks™. The plug-in supports capturing of change data (insert, update, or deletedata) from a relational database. The plug-in supports JDBC-compliant databases such as Oracle andMicrosoft SQL Server.

TIBCO ActiveMatrix BusinessWorks Plug-in for Database will be referred as ADB (Active Database)Plug-in, in the User's Guide.

Using the plug-in, you can do the following main tasks:

● Define the schema of a parent table, parent-child table, and a reference table.

● Select the storage mode, that is, specify how the publishing table stores the event information.

— Publish by value: All the published column information is stored in the stage table.

— Publish by reference: Only the key values of the changed event are stored in the stage table, anddata of other columns is retrieved through the table's join operation.

● Publish data of child table. ("Publish Child Data" option)

● Order the data of the child table in the ascending or descending order. ("Child Table Order By"option)

● Specify the maximum number of database records to be published per event to start aBusinessWorks job. ("Record per event" option)

● Specify a Polling Interval and the maximum number of records to be retrieved for each pollingwhen a polling batch is used. ("Polling Interval" and "Polling Batch Size" options)

● Improve the performance in a high-load scenario by using load balancing. Load balancingdistributes the workload across application nodes.

These features can be implemented using:

● ADB Configuration Shared Resource - The ADB Configuration shared resource uses JDBCConnection shared resource to connect to a database, and create XML schema definition (XSD)schema for plug-in operation. The ADB Configuration shared resource is used by the plug-inactivities.

● Data Event Poller - You can use this activity to poll the change in stage table in a specified interval.

8


Comparison between Adapter and Plug-in

This topic is useful for users, who have previously used the TIBCO ActiveMatrix® Adapter forDatabase, to help understand differences in the plug-in where supported features have overlap withadapter.

FeatureTIBCO ActiveMatrix® Adapterfor Database

TIBCO ActiveMatrixBusinessWorksTM Plug-in forDatabase

Services Provided Publication service,Subscription service and RPCservice, as well as AlerterService

The plug-in is a replacement ofthe ADB Adapter and AEPalette available in TIBCOBusinessWorks. Data EventPoller activity is equivalent toADB Adapter's Publicationservice with an AdapterSubscriber activity.

Transport Type JMS and Rendezvous The plug-in is native to TIBCOBusinessWorks and does notrequire messaging.

Message Format The ADB Adapter is developedusing Adapter SDK librariesand outputs the message usingAE Schema.

The plug-in is native to TIBCOBusinessWorks and outputs themessage as XML based on aXSD.

Support for Load Balancing Configurable Supported by default but canbe configured by the user.

TRA Properties TRA properties are maintainedin TIBCO Administrator

TRA properties are notapplicable in plug-in

UseBetweenClause Default is false Default is true

Referencing an external schema Yes Yes

Storage Mode Publish by value/reference Publish by value/reference

Stage Table Yes Yes

Triggers Generation Direct apply/SQL statementgenerated

Direct apply/SQL statementgenerated

or

save generated SQL into file

DB reconnection attempts DB JDBC connection recovery/reconnect attempts

Reconnection is tried at everypolling interval

Polling Batch size supported supported

9


FeatureTIBCO ActiveMatrix® Adapterfor Database

TIBCO ActiveMatrixBusinessWorksTM Plug-in forDatabase

Group messaging supported renamed as "record per event"

MS SQL WindowsAuthentication

Yes No

Auto Re-Publish(Oracle_failed_rePublish)

Yes No

Look back Yes No

Publishing by Reference Object Yes Yes

Polling performanceenhancement hint

Yes No

Database vendors● IBM DB2

● Microsoft SQL Server

● MySQL

● Oracle Database

● PostgreSQL

● Sybase

● Teradata

● Oracle Database

● Microsoft SQL server

Database Driver support● Native Database Drivers

supported

● DataDirect Driverssupported

● Native Database DriversNOT supported

● DataDirect Driverssupported

Set Database client information Yes No

Publish Batch confirm size/timeout

Yes No

Database Connection Adapter Database Connection JDBC Connection

Database Configuration Adapter Configuration ADB ConfigurationSharedresource

Refresh the existing schema Refind Schema option The Refind Schema option hasbeen renamed to RefreshSchema

10


Getting Started

A typical workflow for using the plug-in to achieve different goals includes creating a process, testing itin the debugger, and deploying the application.

TIBCO ActiveMatrix BusinessWorks uses the Eclipse graphical user interface (GUI) provided by TIBCOBusiness Studio to define business processes and generate Enterprise Archives (EAR files). The EAR fileis deployed and run in the ActiveMatrix BusinessWorks runtime, and also is managed by using TIBCOEnterprise Administrator (TEA).

The typical workflow for using the plug-in is:

1. Creating a Project

2. Creating a JDBC Connection Shared Resource

3. Creating an ADB Configuration Shared Resource

4. Configuring a Process

5. Testing a Process

6. Debugging and Running a Process

7. Deploying Applications

Creating a ProjectThe first task of using a plug-in is creating a project. You can add resources and processes after creatinga project. An Eclipse project is an application module configured for TIBCO ActiveMatrixBusinessWorks. An application module is a resource unit that is named, versioned, and packaged as apart of the application.

Procedure

1. Start TIBCO Business Studio by using one of the following ways:

● Microsoft Windows: click Start > All Programs > TIBCO > TIBCO_HOME > TIBCO BusinessStudio version number > Studio for Designers.

● Linux: run the TIBCO Business Studio executable file located in the TIBCO_HOME/studio/version_number/eclipse directory

2. From the menu, click File > New > BusinessWorks Resources to open the BusinessWorks Resourcewizard.

3. In the "Select a wizard" dialog, click BusinessWorks Application Module and click Next to openthe New BusinessWorks Application Module wizard.

There are several ways to open the New BusinessWorks Application Module dialog boxand create a new project in TIBCO Business Studio. See the TIBCO ActiveMatrixBusinessWorks documentation for more information.

4. In the Project dialog, configure the project you want to create:a) Type a name for the project that you are creating in the Project name field.b) By default, the created project is located in the workspace currently in use. Keep the Use default

location.c) Keep the Create empty process and Create Application check boxes selected to automatically

create an empty process and an application when creating a project.d) Click Finish to create the project.

11


Result

The project with the specified settings is displayed in the Project Explorer view.

Creating a JDBC Connection Shared ResourceTo connect to the database, you must use the JDBC Connection shared resource.

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

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

3. Enter a name in the Resource Name field and click Finish.

4. Configure the JDBC Connection shared resource as described in the following sections.

General

The General section has the following fields.

Field Description

Name The name to be displayed as the label for the shared resource

Description A short description of the shared resource

JDBC Connection

This section has the following fields.

Field

LiteralValue/ModuleProperty? Description

Connection Type None Specifies the kind of JDBC connection you want to create.

12


Field


MaximumConnections

Yes The maximum number of database connections to allocate.The default maximum is 10. The minimum value that can bespecified is 1.

Login Credentials Yes The user name used to connect to the database.

The password used to connect to the database.

JDBC Driver

This section has the following fields.

Field


Database Driver Yes The name of the JDBC driver. If you select a supported driverfrom a list of supported drivers, the Database URL field ispopulated with a template for the URL of the driver.

For example:tibcosoftwareinc.jdbc.sqlserver.SQLServerDriver

Database URL Yes The URL to use to connect to the database. A template of theURL is supplied for the selected JDBC driver. You mustsupply the portions of the URL that are in angle brackets (<>).

For example: jdbc:tibcosoftwareinc:sqlserver://<host>:<port>;DatabaseName=<dbname>

Login Timeout Yes The length of time (in seconds) to wait for a successfuldatabase connection.

Only JDBC drivers that support connection timeouts can usethis field. If the JDBC driver does not support connectiontimeouts, the value of this field is ignored. Most JDBC driverssupport connection timeouts.

Test Connection

Click the Test Connection button to test whether the specified configuration fields result in a validconnection to a database.

Creating an ADB Configuration Shared Resource

Prerequisites

Configure a JDBC Connection shared resource as described in Creating a JDBC Connection SharedResource.

13


Procedure


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

3. Type a name in the Resource Name field in the ADB Configuration Editor dialog. Click Finish.The ADB Configuration shared resource is created. The shared resource consists of two pages:Connection and Schemas.

ADB Configuration shared resource: Connection Page

ADB Configuration shared resource: Schemas Page

4. Configure the ADB Configuration shared resource in the displayed editor, as described in UserInterface Elements of the ADB Configuration Shared Resource.

14


Configuring a ProcessAfter creating a project, an empty process is created. You must configure the process by addingactivities to the empty process to complete a task.

Prerequisites

Ensure that you have created an empty process when creating a project. See Creating a Project for moreinformation.

Procedure

1. In the Project Explorer view, click the created project and open the empty process from theProcesses folder.

2. Select an activity from the Palette view and drop it in the Process editor.For example, select and drop the DataEventPoller activity from the ADB palette. You can add otheractivities similarly.

3. Click an activity in the Process editor and drag the icon to create a transition between theadded activities.

4. Click to create links between two activities and configure the condition types.

5. Configure the DataEventPoller activity as described in Data Event Poller Activity.

An ADB Configuration shared resource is required when configuring this activity. See Creating an ADB Configuration Shared Resource for more details on how to create theshared resource.

6. Click File > Save to save the project.

Testing a ProcessAfter configuring, you might debug or test a process.

Prerequisites

Ensure that you have configured a process, as described in Configuring a Process.

15


Procedure

1. Open the process you have configured in TIBCO Business Studio.

2. On the toolbar, click Debug > Debug Configurations.

3. Click BusinessWorks Application > BWApplication in the left panel.

By default, all the applications in the current workspace are selected in the Applications tab. Ensurethat only the application you want to debug is selected in the Applications tab in the right panel.

4. Click the Advanced tab and click Browse to locate the logback file.By default, the log file resides in the TIBCO_HOME/bw/<version>/config/design/logbackdirectory and error logs are captured. See Managing Logs for more details.

5. Click Debug to test the process in the selected application.TIBCO Business Studio changes to the Debug perspective. The debug information is displayed inthe Console view.

6. In the Debug tab, expand the debugged process and click an activity.

7. In the upper-right panel, click Job Data view, and then click the Output tab to check the activityoutput.

Deploying ApplicationsAfter testing a process, you can deploy the application that contains the configured process into aruntime environment, and then use the bwadmin utility to manage the deployed application.

Prerequisites

Before deploying an application, generate an application archive, which is an enterprise archive (EAR)file created in TIBCO Business Studio. For more information, also see:

● Creating a Project.

● Generating an EAR File.

Deploying an application involves:

1. Uploading an EAR file.

2. Deploying an application.

3. Configuring an application.

4. Starting an application.

See TIBCO ActiveMatrix BusinessWorks Administration for more details about how to deploy anapplication.

Generating an EAR FileApplication archives are enterprise archive (EAR) files that are created in TIBCO Business Studio. AnEAR file is required when deploying an application.

Prerequisites

An application project has already been created, as described in Creating a Project.

There are many ways to generate an EAR file, the following is one such method. For more informationon this, see TIBCO ActiveMatrix BusinessWorks Administration for more information.

16


Procedure

1. Go to the File Explorer view and click the Open Directory to Browse icon.

2. Select the folder where you want to generate the EAR file and click OK.The new folder is displayed in the File Explorer view.

3. Drag the application from the Project Explorer view to the new folder in the File Explorer view.

The EAR file is generated with the name <name>.<application>_<version>.ear.

17


ADB Configuration Shared Resource

You should use the ADB Configuration shared resource to establish a connection from the ActiveMatrixBusinessWorks Plug-in to the database.

The ADB Configuration shared resource utilizes the JDBC connection shared resource to retrieve thedatabase table schema information.

● User Interface Elements of the ADB Configuration Shared Resource

User Interface Elements of the ADB Configuration Shared ResourceThe user interface elements in the ADB Configuration shared resource are described below.

The shared resource consists of two pages: Connection and Schemas.

Connection Page

ADB Configuration shared resource: Connection Page

The ADB Configuration shared resource utilizes the JDBC connection shared resource to retrieve thedatabase table schema information. The JDBC connection shared resource is configured in theConnection page.

The Connection page consists of two sections: General and Configuration.

Shared Resource > Connection Page > General Fields

FieldModuleProperty? Description

Package No The name of the package where the shared resource is added.

Name No The name to be displayed as the label for the shared resource in theprocess.

Description No A short description for the shared resource.

18


Shared Resource > Connection Page > Configuration Fields


JDBCConnection

No Define the JDBC connection by selecting the JDBC shared resource.Oracle and Microsoft SQL Server are the supported vendors. OnlyTIBCO embedded DataDirect JDBC driver is supported by the plug-in.

DefaultSchema

Yes Specify the default schema name.

If no default schema name is specified, it uses the JDBCconnection user name.

ValidateSchema

No Click this button to validate the the JDBC connection and theschemas configured under the shared resource. For the schema, thetables, columns, and column types are validated. If a referred table isprovided, the existence of the table is also validated. An errormessage is displayed if the validation fails.

Once all the issues are resolved, after clicking Validate Schema, youwill receive a "Validation of Schema is successful" message.

Schemas Page

ADB Configuration shared resource: Schemas Page

The type of service and the associated tables to generate XSD schema and database triggers are definedin the Schemas page.The Schemas section on the left lists the schema type. You can add or remove schemas. Currently, youcan add only DBPoller schema type. As soon as a new DBPoller schema is added, a correspondingsection is created on the right that consists of the following four tabs:

● Configuration

● Schema

19


● Options

● Child Table Order By

The Configuration tab contains the following fields:

Shared Resource > Schemas Page > Configuration Tab


Name No You can update the schema name.

See Entity Naming Conventions.

Description No A short description for the schema.

The Schema tab contains the following UI options:

Shared Resource > Schemas Page > Schema Tab

Icon/Option Description

Add a parent table from the connected Database (through JDBC connection).

Add a child table to a parent table.

Refresh the existing schema or change the columns used.

Allow KeyColumns Only

If this check box is selected, the Join To relation between the parent and childtable is applied only on the columns having an User Key. If the check box is notselected, the Join To relation can be applied on any fields.

Join To Set a relation between the parent table and child table.

For setting a relation between the parent table and child table, you must eitherclear the Allow Key Columns Only or at least one column must be enabled asUser Key from the parent.

User Key Select the check box beside the column name to specify that the column mustcontain an unique sets of values. If the user key is defined in a child table andthe parent table has a primary key, it has no impact on the generated triggersand the user key is used for mapping the parent-child relationship.

If the parent table does not have a primary key (rare cases), no update or deletetriggers are generated. To use an user key as the implicit primary key in thetrigger, you must modify and apply the trigger manually.

20



Update Trigger The selected column is updated by the database application.

Update trigger is applicable only for a parent table.

XSD Type Displays the XSD type of the column. This is a read-only column.

The Options tab contains the following fields:

Shared Resource > Schemas Page > Options Tab


Storage Mode No Select how the stage table keeps the event information. You caneither Publish by Value or Publish by Reference.

● Publish by Value: The storage table keeps all the publishedcolumn information in the stage table.

● Publish by Reference: Only the key value(s) of the changed eventare kept in the storage table, and data of other columns isretrieved through the table's join operation.

If you specify a table or view as a referred object, thereferred object must contain columns with the samenames and data types as the primary key columns inthe source table.

The primary key values in the source table must be thesame as the primary key values in the referred object.

PublishingTable

No Displays the stage table name. This name can be modified.

You can use only alphanumeric characters and anunderscore in the table name. No other special charactersare allowed in the table name.

See Publishing Table for more information on the columns in thepublishing table.

21



ReferredObject

No You can add a reference object from the same schema or a differentschema. This option is enabled only when the Storage Mode isPublish by Reference.

You can also download a table or a view as a referred object.

If this field is empty, the plug-in reads data from the source table.

If you specify a table or view as a referred object, thereferred object must contain columns with the samenames and data types as the primary key columns in thesource table. The primary key values in the source tablemust be the same as the primary key values or the subsetof primary key values in the referred object.

For more information on how to add a reference object, see Creatinga Schema Using the ADB Configuration Shared Resource.

Publish ChildData

No Select the check-box if you want to publish the child table data.

The default is true.

You can use Child Table Order By tab to specify the columns of an Order By clause used for each childtable query. The plug-in returns the child table result set in a particular sequence.

The Child Table Order By tab contains the following fields:

Shared Resource > Schemas Page > Child Table Order By Tab


Child TableName

When a child table is added to a parent table, the child table is automaticallyadded to the Child Table Order By tab. The name of table is displayed here.

22



Select Columns The Order By Clause column cannot be edited; you can add the fields of thetable by selecting them using the Select Columns button. The wizard that openscontains a list of all the fields of the child table. You can select the columnsbased on which you want to order the table.

● Check to Use DESC - Identifies the columns based on which you want toorder the table. The default order is the ascending order. To order in thedescending order, you can select the check box beside the column in theCheck to Use DESC panel.

● - Moves the selected column to the Check to Use DESC list.

● - Moves the selected column from the Check to Use DESC list to theleft.

● - Moves the selected column to one level above in the Check to UseDESC list.

● - Moves the selected column to one level below in the Check to UseDESC list.

Creating a Schema Using the ADB Configuration Shared Resource

Adding a Shared Resource

Procedure


2. Right-click the Resources folder and select New > ADB Configuration. Specify the Resource Folder,Package, and Resource Name. Click Finish.

3. On the Connection page, select the JDBC connection in the JDBC Connection field.

4. On the Schemas page, select DBPoller and click Add. As soon as a new DBPoller schema is added,a corresponding section is created on the right.

23


Adding a Parent Table

If you execute a delete operation on a Parent table, the DataEventPoller activity does not publish anychild data.

To add a parent table from the connected Database (through JDBC connection):

Procedure

1. Click the icon. The Select Table wizard appears.

2. Enter a pattern name to search the table.You can also use the % character to search for table names.

3. To fetch data from the default schema, click Fetch beside the Default Schema field. To fetch datafrom any other schema, click Fetch beside the Other Schema.

● For a parent table, only tables are fetched.

● In the same ADB Configuration shared resource, once a table is downloaded, it will notbe in the list when you do the next fetch.

All the tables available in the specified schemas are displayed.

24


4. Click Finish.The table is displayed in the Schema tab on the right.

25


Adding a Child Table

Procedure

1. Select the parent table and click .

A wizard very similar to the one for adding a parent table appears.

2. Fetch the table and click Finish.

● For a child table, both tables and views are fetched.

● In the same ADB Configuration shared resource, once a table or view is downloaded, itwill not be in the list when you do the next fetch.

The child table is added under the parent table and displayed in the Schema tab on the right.

Setting Up a Relation Between Parent and Child TablesYou can set up a relation between the parent and child table using Join To. For applying a Join Torelation between a parent and child table, you need to set at least one field as the User Key in the childtable or uncheck the Allow Key Columns check box.

Procedure

1. If you want to apply the Join To relation only on fields having an user key, select the Allow KeyColumns Only checkbox. If you clear the Allow Key Columns Only check box, the Join To relationis applied on any fields from the parent table.

2. Select the Update Trigger check box to ensure that the selected column is updated by the databaseapplication.

26


Refresh the Schema

Refresh the existing schema or change the columns used using the icon.

Specify the Columns of an Order By Clause for a Child TableWhen a child table is added to a parent table, it is displayed in the Child Table Order By tab. You canspecify the columns of an Order By clause used for each child table query. The plug-in returns the childtable result set in a particular sequence.

Procedure

1. Click Select Columns in the Child Table Order By tab.The Select Child Table Order By Columns wizard appears.

2. Select the fields depending on the order you want and move them to the right panel using .

Similarly, you can use to move them back to the left panel. You can also reorder the sequence

using the and buttons.

3. If you want to get the values of a field in a descending order, select the check box beside theappropriate field in the right panel, that is, the Check to Use DESC panel. The default order is theascending order.

4. Click Finish.

27


Publishing TablePublishing tables mirror tables that you have identified for monitoring. They contain additionalcolumns, primarily a sequence number and delivery status, which are required by the plug-in to detectnew rows. You can create a publishing table for each table you want to activate in TIBCO BusinessStudio.

In addition to a copy of the source table columns, the publishing table has the following additionalcolumns.

Column Name Type Description

ADB_SEQUENCE INTEGER Stores the monotonically increasingsequence number that represents newrows in the publishing table. If a columnwith this name exists, the number isgenerated automatically.

By default, the schema type is string. Theplug-in treats this number as a string. Thisnumber can be larger than an integer if thedatabase supports it.

ADB_TIMESTAMP DATE Time of row insertion in publishing tablethat is used to calculate expiration of rows.The timestamp is generated automatically.

ADB_OPCODE INTEGER Operation code used by the plug-in:

● 1 indicates INSERT

● 2 indicates UPDATE

● 3 indicates DELETE

When working with a parent-child table, it is good practice toset the ADB_OPCODE columnsin the parent and child table tothe same value. Or only set thevalue of the ADB_OPCODEcolumn in the parent table andleave the child table empty.

ADB_REF_OBJECT VARCHAR2(64) When publishing by reference object isused, contains the name of the referenceobject that provides source data.

28


Column Name Type Description

ADB_L_DELIVERY_STATUS CHAR Delivery status of Records:

● N indicates that a new Record hasarrived, but has not yet been published.

● S indicates that one node has got thisrecord, and will not be taken againwhen polling other records.

● C indicates complete.

● F indicates failed.

Also see Child Table.

Child TableTo support incremental parent-child operations, each child row has an opcode, that is, an extraADB_OPCODE field that is added to the child schema. The plug-in determines if the operation is anincremental parent-child operation by checking the first level child opcode. If the first level childopcode is not set, the plug-in treats it as a complete operation. For the subsequent child level, if thechild opcode is not set, it will inherit the parent opcode.

When working with parent-child table, the value of ADB_OPCODE in the parent table and the childtable must be the same. Or only set the value of ADB_OPCODE in the parent table and leave the childtable empty.

Also see Publishing Table.

29


ADB Palette

TIBCO ActiveMatrix BusinessWorks Plug-in for Database achieves it's functionality with the help ofData Event Poller activity.

The Data Event Poller activity uses the ADB Configuration shared resource, created earlier.

Data Event Poller ActivityThe Data Event Poller activity polls the change in a stage table in a specified time interval. Theconfiguration allows you to generate the required trigger SQL script file to create stage table andtriggers.

General

The General tab contains the following fields:

Field

Literal Value/ProcessProperty/ModuleProperty? Description

Name No The name to be displayed as the label for the activity in theprocess.

See Entity Naming Conventions.

ConfigurationResource

Yes Shared configuration resource containing the ADB Plug-inConfiguration connection information.

Schema No The database poller schema which is configured with theschema table. The schema is based on the XSD generated bythe database poller schema.

● Apply Trigger: Applies the trigger script to the database.

● Generate Trigger: Saves the trigger script to a specific fileand can be applied to the database later. You areprompted to select the directory where the trigger filesare to be created. Two files are generated at the specifiedlocation:

— A SQL file containing the script for triggering to thedatabase

— A cleanup SQL file which contains a script to cleanupcreated publishing table, triggers, sequences, and soon.

The filenames are created based on the name of theschema.

You cannot apply or generate the trigger if you areoffline; you must be connected to the database tofetch table metadata.

30


Description

Provide a short description for the activity.

Advanced

This tab has the following fields:

Field

LiteralValue/ProcessProperty/ModuleProperty? Description

SequenceKey

No This field can contain an XPath expression that specifies whichprocesses should run in order. Process instances with sequencingkeys that evaluate to the same value are executed sequentially in theorder the process instance was created.

CustomJob ID

No This field can contain an XPath expression that specifies a custom IDfor the process instance.

Operation Options:

Record PerEvent

Yes Specifies the maximum number of database records to be retrievedper event to start a BusinessWorks job. The default value is 1.

PollingInterval(ms)

Yes Specifies the amount of time in seconds for polling. The default valueis 5000.

Batch Size(MaxRows)

Yes Maximum number of records to be retrieved for each polling, whenpolling batch is used. The default value is 10.

Load Balancing Options:

EnableLoadBalancing

Yes Load balancing distributes the workload across BusinessWorksApplication nodes to improve the performance in a high-loadscenario. BusinessWorks Application nodes with the same mutexname specified are in the same load balance group.

Load balancing is enabled by default.

If you enable Load Balancing, the order of data processingis not sequential.

MutexName

Yes Name of the Mutex table. This name can be changed.

The default name is the first 20 characters of the publishing tablename suffixed with "_MUTEX".

Output

This tab displays the output schema.

31


For more information on how different datatypes are mapped to the XSD type, refer to OutputMapping.

Fault

Data Event Poller Activity: Fault Tab

The Fault tab lists exceptions that are thrown by this activity:

Error Schema Element Data Type Description

ADBSQLException String It has a msg and msgCode field for the exception.

ADBValidationExeption String It has a msg and msgCode field for the exception.

msg String The error message returned by the plug-in.

msgCode String The error code returned by the plug-in.

32


Samples

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

After the plug-in is installed, the following sample projects are available in the TIBCO_HOME\bw\palettes\adb\version_number\samples directory:

● Parent project

— MSSQLServerParent

— OracleParent

● ParentChild project

— MSSQLServerParentChild

— OracleParentChild

● PublishByReference project

— MSSQLPublishByReference

— OraclePublishByReference

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

Procedure

1. Start TIBCO Business Studio.

2. Click File > Import.

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

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

5. In the samples directory, select a sample (for example, select the MSSQLServerParent.zip) andclick Open.

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

33


Parent ProjectThe plug-in includes the following Parent projects:

● MSSQLServerParent project

● OracleParent project

MSSQLServerParent ProjectThe MSSQLServerParent project contains one process: mssqlserverparent.PublishParentDataprocess. The project shows how the plug-in polls data from the publishing table.

PublishParentData Process

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

JDBC Connection Resource

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

34


ADB Configuration Resource

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

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

The Configuration tab:

35


The Schema tab:

The Options tab:

36


The Child Table Order By tab:

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/Parent directory in the following order:

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 a

Sample Project.

37


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

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

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, expand BusinessWorks Application, and then clickBWApplication.

6. In the right panel, click the Applications tab, and then select the check box next toMSSQLServerParent.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.

38


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

PublishParentData Process

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



39




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


40


The Schema tab:

The Options tab:

41





Prerequisites

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

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 Sample

Projects.

42


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>


Running the Project


Procedure






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



Result

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

43


ParentChild ProjectThe plug-in includes the following ParentChild projects:

● MSSQLServerParentChild

● OracleParentChild

MSSQLServerParentChild ProjectThe MSSQLServerParentChild project contains one process: mssqlserverparentchild.PublishParentChildData process. The project shows how the plug-in handles polling of data from thepublishing table. The corresponding data from the child table is also fetched.

PublishParentChildData Process

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

44






45




The Schema tab:

46


The Options tab:

47





Prerequisites

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

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

Importing a Sample Project.

48


Procedure








Running the Project


Procedure




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


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



Result

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

49


50


OracleParentChild ProjectThe OracleParentChild project contains one process: oracleparentchild.PublishParentChildDataprocess. The project shows 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 correspondingdata from the child table. The following figure shows the PublishParentChildData process:

51






52




The Schema tab:

53


The Options tab:

54





Prerequisites

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

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


55


Procedure







Running the Project


Procedure


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




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



Result

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

56


57


PublishByReference ProjectThe plug-in includes the following PublishByReference projects:

● MSSQLPublishByReference

● OraclePublishByReference

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

PubByRef Process

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

58








59


The Schema tab:

The Options tab:

60





Prerequisites

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

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


61


Procedure








Running the Project


Procedure




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


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



Result

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

62


OraclePublishByReference ProjectThe OraclePublishByReference project contains one process: oraclepublishbyreference.PubByRefprocess. The project shows 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 followingfigure shows the PubByRef process:



63




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


64


The Schema tab:

The Options tab:

65





Prerequisites

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

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


66


Procedure







Running the Project


Procedure


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


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


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



Result

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

67


68


Advanced Topics

When you use TIBCO ActiveMatrix BusinessWorks™ Plug-in for Database, you can use advancedconfiguration and deployment.

Output MappingThis section describes how different datatypes are mapped to the XSD type.

Mapping: Adapter Datatype to Plug-in XSD Type

Adapter AE Datatype Plug-in XSD Type

i1 byte

i2 short

i4 int

i8 long

ui1 unsignedByte

ui2 unsignedShort

ui4 unsignedInt

ui8 unsignedLong

r4 float

r8 double

binary base64Binary

string string

adbDateTime string

Mapping: MSSQL Datatype to XSD Type

Database Type XSD Type

nchar(10) string

datetime string

binary(50) base64Binary

decimal(18,0) double

69


Database Type XSD Type

float double

money double

real double

smalldatetime string

smallint int

smallmoney double

tinyint int

uniqueidentifier string

varbinary(50) base64Binary

bit int

bigint long

datetimeoffset string

date string

varchar(max) string

char(10) string

int int

numeric double

nvarchar string

timestamp base64Binary

Mapping: Oracle Datatype to XSD Type

Database Type XSD TypeCases for Numeric andNumber

BLOB base64Binary

CLOB string

CHAR string

DATE string

70


Database Type XSD TypeCases for Numeric andNumber

FLOAT string

LONG string

LONG RAW base64Binary

NCHAR string

NCLOB string

NUMBER double If size is not specified, thedefault is 22.

NUMBER(n) int If size less than 10

NUMBER(p,s) double If size is 10 or more than 10

NVARCHAR2 string

RAW base64Binary

TIMESTAMP string

VARCHAR2 string

NUMBER(n) int If size less than 10

NUMERIC double If size is not specified, thedefault is 22.

NUMERIC(p,s) double

NUMERIC double If size is 10 or more than 10

Fault ToleranceFault Tolerance allows multiple application nodes to substitute for each other. When the primaryapplication node terminates unexpectedly, the token held by the primary application node can be takenover by an application node in the standby state. In the process of replacement, the standby applicationnode is promoted to the primary application node.

To apply Fault Tolerance, you can select one of the following methods:

● In the process designer, right-click and select Show Properties View. Navigate to the Advanced tab.Select Activation as Single AppNode.

● Setup ActiveMatrix BusinessWorks Administrator in a Fault Tolerance group.

For more information on fault tolerance in BusinessWorks, refer to the TIBCO ActiveMatrixBusinessWorks™ Administration guide.

71


Load BalancingThe plug-in provides Load Balancing to distribute the workload across application nodes. This resultsin an improvement of performance in a high-load scenario.

Application nodes with the same mutex name specified are in the same load balancing group.

By default, load balancing is ON.

The default name of the mutex table is the first 20 characters of the publishing table name suffixed with"_MUTEX". You can change the name of the mutex table name and the corresponding mutex table iscreated in the database.

For more information on load balancing and fault tolerance in BusinessWorks, refer to the TIBCOActiveMatrix BusinessWorks™ Administration guide.

Enabling Load BalancingBy default, load balancing is on.

To apply Load Balancing, you can select one of the following methods:

● In the process designer, right-click and select Show Properties View. Navigate to the Advanced tab.Select Activation as Multiple AppNode.

● Setup ActiveMatrix BusinessWorks Administrator in a Group mode.

Disabling Load Balancing

Procedure

1. Click on the DataEventPoller activity in the Process Designer.

2. Navigate to the Properties tab > Advanced section.

3. Clear the Enable Load Balancing check box.Load balancing is disabled.

Unlocking the MUTEX TableA Mutex table could result in lock and unlock situations.

When you publish data, the data is set in the table and the status is also set to N. When an applicationnode is running, the mutex table fetches data with status as N and acquires a lock. When the statuschanges from N to S, the mutex table releases the lock from the table. If you try to forcefully shutdownthe application node, the mutex table gets locked and the configurations associated with Mutex table donot work. To release a lock on a MUTEX table, manual intervention is required.

72


Only DBA users can execute the scripts to unlock the MUTEX table.

Oracle

To fetch the ID and serial number of the locked session, execute the following query:select s.sid, s.serial#, p.spid From v$session s, v$process pwhere s.paddr = p.addr AND s.sid in (select SESSION_ID fromv$locked_object);

To kill the session that has acquired the lock, execute the following query:alter system kill session '<id>, <serial number>';

MSSQL

To fetch the ID and serial number of the locked session, execute the following query:SELECT OBJECT_NAME(P.object_id) ASTableName,Resource_type,request_session_idFROM sys.dm_tran_locks LJOIN sys.partitions PON L.resource_associated_entity_id=p.hobt_idWHERE OBJECT_NAME(P.object_id)='P1Chronolog_IncidentActivityUpdates'

To kill the session that has acquired the lock, execute the following query:Kill session_ID

Entity Naming ConventionsMost of the ActiveMatrix BusinessWorks named entities are modeled as NCNames (or as a subset of anNCNames). These include activity names and schema names.

NCName stands for XML "non-colonized" name. See https://www.w3.org/TR/xmlschema-2/#NCNamefor the W3C definition of NCName. NCName represents the set of characters that conforms to thefollowing restrictions:

● Can include letters or numbers A-Z, a-z (lower case letters), 0-9, -, _ (underscore)

● Cannot include the following characters: @, :, $, %, &, /, +, ,, ;, ), - (hyphen) and white spacecharacters.

● Cannot begin with a number, dot (.), or minus (-) character. However, these characters can appearlater in an NCName.

73


https://www.w3.org/TR/xmlschema-2/#NCName

Managing Logs

Logs are used to trace and troubleshoot the plug-in exceptions.

When an error occurs, you can check the logs to trace and troubleshoot the plug-in exception. Bydefault, error logs are displayed in the Console view when you run a process in the debug mode. Youcan change the log level of the plug-in to trace different messages and export logs to a file. Different loglevels correspond to different messages, as described in Log Levels

A logback.xml file is located in the TIBCO_HOME\bw\<version>\config\design\logback directory.Update this file to set up a log file and export logs to a file.

Log Levels

Different log levels include different information. The plug-in supports the following log levels:

LogLevel Description

Debug Indicates a developer-defined tracing message.

Info Indicates normal plug-in operations. No action is required. A tracing message tagged withInfo indicates that a significant processing step is reached, and logged for tracking orauditing purposes. Only Info messages preceding a tracking identifier are considered assignificant steps.

Error Indicates that an unrecoverable error occurred. Depending on the severity of the error, theplug-in might continue with the next operation or might stop.

Warn Indicates that an abnormal condition occurred. Processing continues, but special attentionfrom an administrator is recommended.

Trace Includes all information regarding the running process.

Setting Up Log LevelsYou can configure different log levels for the plug-in and plug-in activities to trace different messages.By default, the plug-in uses the log level configured for TIBCO ActiveMatrix BusinessWorks. Thedefault log level of TIBCO ActiveMatrix BusinessWorks is Error.

If neither the plug-in log nor the BusinessWorks log is configured in the logback.xml file, the errorlogs of the plug-in are displayed in the Console view by default. If the plug-in log is not configured, butthe BusinessWorks log is configured in the logback.xml file, the configuration for the BusinessWorkslog is implemented by the plug-in.

Procedure

1. Navigate to the TIBCO_HOME\bw\<version>\config\design\logback directory and open thelogback.xml file.

2. Add the following node in the Console Appender area to specify the log level for the plug-in:<logger name="com.tibco.bw.palette.adbplugin.runtime"> <level value="DEBUG"/></logger>

The level tag defines the log level and the value of the level element can be Trace, Info, Error orDebug.

74


When the level is set to Debug, the input and output for the plug-in activities are alsodisplayed in the Console view.

3. Optional: Add the following node in Console Appender area to specify the log level for an activity:<logger name="com.tibco.bw.palette.adbplugin.runtime.ActivityNameActivity"> <level value="DEBUG"/></logger>

See the following examples:

● To set the log level of the Data Event Poller activity to Debug, you must add the following node:<logger name="com.tibco.bw.palette.adbplugin.runtime.datapoller.ADBEventSource"> <level value="DEBUG"/></logger>

● To set the log level of the ADB Configuration shared resource to Debug, you must add thefollowing node:<logger name="com.tibco.bw.sharedresource.adbplugin.runtime"> <level value="DEBUG"/></logger>

For the activities that do not configure with specific log levels, they still inherit log levelconfigured for the plug-in or BusinessWorks.

4. Save the file.

Exporting Logs to a FileModify the logback.xml file to export plug-in logs to a file.

Procedure

1. Navigate to the TIBCO_HOME\bw\<version>\config\design\logback directory and open thelogback.xml file.

When deploying an application in TIBCO Enterprise Administrator, you must navigate tothe TIBCO_HOME\bw\domains\defaultdomain\appnodes\defaultappspace\defaultappnode directory to find the logback.xml file.

2. Add the following node to specify the file location:<appender name="FILE" class="ch.qos.logback.core.FileAppender"> <file>c:/bw6-adbplugin.log</file> <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36}-%msg%n</pattern> </encoder></appender>

The file tag defines the location to which the log is exported and the value is the absolute path ofthe file that is detailed to the file name.

3. Add the following node to the root node at the bottom of the logback.xml file to enable exportingthe logs to a file:<root level="DEBUG"> <appender-ref ref="STDOUT" /> <appender-ref ref="FILE" /></root>

4. Save the file.

75


Error Codes

The following table lists error codes, detailed explanation of each error, and ways to resolve errors(wherever applicable).

Error Code and ErrorMessage Role Category Description Resolution

TIBCO-BW-PALETTE-ADBPLUGIN-100001 .The number of recordsper event is {0}.

Trace BW-Plugin Number of recordsper event is 0.

This is a tracemessage andresolution is notapplicable

TIBCO-BW-PALETTE-ADBPLUGIN-100002.DataEventPoller schema{0} bind fault statusupdater.

Trace BW-Plugin Set parameter valuesfor updatingADB_L_DELIVERY_STATUS in publishingtable from S to F.


TIBCO-BW-PALETTE-ADBPLUGIN-100003.DataEventPoller Schema{0} execute fault statusupdater {1}.

Trace BW-Plugin Execute update ofADB_L_DELIVERY_STATUS in publishingtable from S to F.


TIBCO-BW-PALETTE-ADBPLUGIN-100004.DataEventPoller Schema{0} No record found.

Trace BW-Plugin Polling is in progressand no data is foundin parent or child tablefor publishing


TIBCO-BW-PALETTE-ADBPLUGIN-100005.DataEventPoller Schema{0} execute pub tableupdater {1}.

Trace BW-Plugin SQL query used forupdating publishingtable.


TIBCO-BW-PALETTE-ADBPLUGIN-100006.DataEventPoller Schema{0} batch update {1}.

Trace BW-Plugin Number of recordsupdated during batchprocessing.


TIBCO-BW-PALETTE-ADBPLUGIN-100007.DataEventPoller Schema{0} release multi-threading semaphoreafter marking records.

Trace BW-Plugin Release the publishingtable semaphore toallow other threadspoll the publishingtable


TIBCO-BW-PALETTE-ADBPLUGIN-100008.DataEventPoller Schema{0} release table {1} lockin load balance mode.

Trace BW-Plugin Release the table lockin load balance mode.


76



TIBCO-BW-PALETTE-ADBPLUGIN-100009.DataEventPoller Schema{0} execute publishingtable selector {1}.

Trace BW-Plugin Select columns frompublishing table withADB_L_DELIVERY_STATUS = 'N'


TIBCO-BW-PALETTE-ADBPLUGIN-100010.DataEventPoller Schema {0}builds publishing tableselector.

Trace BW-Plugin Build select statementfor fetching data frompublishing table.


TIBCO-BW-PALETTE-ADBPLUGIN-100011.DataEventPoller Schema {0}binds publishing tableselector, polling batchsize is {1}.

Trace BW-Plugin Set parameter valuesfor the select query onpublishing table.


TIBCO-BW-PALETTE-ADBPLUGIN-100012.DataEventPoller Schema {0}execute publishing tablemax sequence selector{1}.

Trace BW-Plugin SelectMAX(ADB_SEQUENCE) from table whereADB_L_DELIVERY ='N'


TIBCO-BW-PALETTE-ADBPLUGIN-100013.DataEventPoller Schema {0}builds publishing tablemax sequence selector.

Trace BW-Plugin Build select statementfor fetching maximumADB_SEQUENCEvalue


TIBCO-BW-PALETTE-ADBPLUGIN-100014.DataEventPoller Schema {0}execute publishing tablemini sequence selector{1}.

Trace BW-Plugin SELECTMIN(ADB_SEQUENCE) from table whereADB_L_DELIVERY ='N'


TIBCO-BW-PALETTE-ADBPLUGIN-100015.DataEventPoller Schema {0}builds publishing tablemini sequence selector.

Trace BW-Plugin Build select statementfor fetching minimumADB_SEQUENCEvalue


TIBCO-BW-PALETTE-ADBPLUGIN-100016.DataEventPoller Schema {0}selects record data fromreference object table {1}

Trace BW-Plugin SQL query for selectfrom reference objector source table


77



TIBCO-BW-PALETTE-ADBPLUGIN-100017.DataEventPoller Schema {0}builds pub tableupdater.

Trace BW-Plugin Build update queryfor publishing table


TIBCO-BW-PALETTE-ADBPLUGIN-100018.DataEventPoller Schema {0}binds pub table updater.

Trace BW-Plugin Set parameter valuesfor the update queryon publishing table.


TIBCO-BW-PALETTE-ADBPLUGIN-100019.DataEventPoller Schema {0}build 'S' to 'N' updater.

Trace BW-Plugin Build update queryfor publishing table tochangeADB_L_DELIVERY_STATUS from S to N.


TIBCO-BW-PALETTE-ADBPLUGIN-100020.DataEventPoller Schema {0}bind 'S' to 'N' updater.

Trace BW-Plugin Set parameter valuesfor updatingADB_L_DELIVERY_STATUS in publishingtable from S to N.


TIBCO-BW-PALETTE-ADBPLUGIN-100021.DataEventPoller Schema {0}execute 'S' to 'N' updater{1}.

Trace BW-Plugin Execute update ofADB_L_DELIVERY_STATUS in publishingtable from S to N.


TIBCO-BW-PALETTE-ADBPLUGIN-100022.DataEventPoller Schema {0}Child table {1} has nodata to publish.

Trace BW-Plugin Publish Child Data isenabled and there isno data to fetch fromchild table.


TIBCO-BW-PALETTE-ADBPLUGIN-100023.The mutex table {0} alreadyexists.

Trace BW-Plugin The mutex tablealready exists in theDB.


TIBCO-BW-PALETTE-ADBPLUGIN-100024.DataEventPoller Schema {0}bind reference objectselector.

Trace BW-Plugin Set parameter valuesfor selecting data fromreferred table.


TIBCO-BW-PALETTE-ADBPLUGIN-100025.DataEventPoller Schema {0}selects record data fromreference object table.

Trace BW-Plugin Execute select onreferred table.


78



TIBCO-BW-PALETTE-ADBPLUGIN-100026.DataEventPoller Schema {0}builds reference objectselector.

Trace BW-Plugin Build select query forreferred table.


TIBCO-BW-PALETTE-ADBPLUGIN-100027.DataEventPoller Schema {0}constructs the instancebased on the sourcetable.

Trace BW-Plugin If referred table is notmentioned, updatepublishing table basedon the source table.


TIBCO-BW-PALETTE-ADBPLUGIN-100029.DataEventPoller Schema {0}Start to fetch data fromchild table.

Trace BW-Plugin Publish Child Data isenabled and threadstarts to fetch datafrom child table.


TIBCO-BW-PALETTE-ADBPLUGIN-100030.DataEventPoller Schema {0}Finish fetching datafrom child table.

Trace BW-Plugin Publish Child Data isenabled and threadcompleted fetchingdata from child table.


TIBCO-BW-PALETTE-ADBPLUGIN-100031.DataEventPoller Schema {0}Fetch child data from{1}.

Trace BW-Plugin Fetching data fromchild table.


TIBCO-BW-PALETTE-ADBPLUGIN-100032.DataEventPoller Schema {0}execute child selector {1}.

Trace BW-Plugin Select columns forpublishing from childtable.


TIBCO-BW-PALETTE-ADBPLUGIN-100033.DataEventPoller Schema {0}build child selector.

Trace BW-Plugin Build select query forfetching data fromchild table.


TIBCO-BW-PALETTE-ADBPLUGIN-100034.DataEventPoller Schema {0}bind child selector.

Trace BW-Plugin Set parameter valuesfor select query tofetch child data.


TIBCO-BW-PALETTE-ADBPLUGIN-100035.DataEventPoller Schema {0}build fault statusupdater.

Trace BW-Plugin Build update query toupdate status to F


79



TIBCO-BW-PALETTE-ADBPLUGIN-100036.DataEventPoller Schema {0}buildsADB_L_DELIVERY_STATUS N->S marker.

Trace BW-Plugin Build update queryfor Load Balancingmarker


TIBCO-BW-PALETTE-ADBPLUGIN-100037.DataEventPoller Schema {0}builds publishing tableselector whoseADB_L_DELIVERY_STATUS is S.

Trace BW-Plugin Select query for loadbalancing


TIBCO-BW-PALETTE-ADBPLUGIN-100038.DataEventPoller Schema {0}bindsADB_L_DELIVERY_STATUS N -> S marker …

Trace BW-Plugin Set parameter valuesfor the load balancingquery


TIBCO-BW-PALETTE-ADBPLUGIN-100039.DataEventPoller Schema {0}acquire table {1} lock inload balance mode.

Trace BW-Plugin DataEventPollerSchema acquiring lockon a table in the loadbalancing mode


TIBCO-BW-PALETTE-ADBPLUGIN-100040.DataEventPoller Schema {0}executeADB_L_DELIVERY_STATUS N -> S marker ...{1}

Trace BW-Plugin Execute the query inload balancing mode


TIBCO-BW-PALETTE-ADBPLUGIN-100041.Creating the mutex table{0}.

Trace BW-Plugin Creating table in DBlock initialization forload balancing mode


TIBCO-BW-PALETTE-ADBPLUGIN-100042.DataEventPoller Schema {0}selects record data fromsource table.

Trace BW-Plugin If referred table is notmentioned, select datafrom the source table.


TIBCO-BW-PALETTE-ADBPLUGIN-100043.Mutex table {0} is alreadylocked by other node.

Trace BW-Plugin Table is already lockedby other node.


80



TIBCO-BW-PALETTE-ADBPLUGIN-100044.DataEventPoller Schema {0}failed to construct resultbased on source tablebecause no data fetchedfrom {1}

Trace BW-Plugin Object constructionfailed when no datafound in source table.


TIBCO-BW-PALETTE-ADBPLUGIN-100045.DataEventPoller Schema {0}failed to construct resultbased on reference objectbecause no data fetchedfrom {1}

Trace BW-Plugin Object constructionfailed when no datafound in referencedtable.


TIBCO-BW-PALETTE-ADBPLUGIN-200001.Activity {0} generatedoutput:\n{1}

Debug BW-Plugin Show output of datapoller activity in XMLformat.

This is a debugmessage andresolution is notapplicable

TIBCO-BW-PALETTE-ADBPLUGIN-300001.DataEventPoller Schema {0}starts polling message.

Info BW-Plugin Thread starts pollingpublishing table tofetch any changes.

This is a infomessage andresolution is notapplicable

TIBCO-BW-PALETTE-ADBPLUGIN-300002.{0}

Info BW-Plugin Shown if there is lossof connection orreconnection issuccessful.


TIBCO-BW-PALETTE-ADBPLUGIN-400001.DataEventPoller Schema {0}has different referenceobject in SharedResource and PublishingTable. To resolve thisissue, either fix theshared resource or re-generate the trigger.

Warn BW-Plugin Schema has differentreference object inShared Resource andPublishing Table.

To resolve thisissue, either fix theshared resource orre-generate thetrigger.

TIBCO-BW-PALETTE-ADBPLUGIN-500001.DataEventPoller Schema {0}throw exception {1}when update entrystatus.

Error BW-Plugin Thrown if issue occursin updating 'N' to 'C'in publishing tableduring transaction.SQLException isthrown.

Check errors listedin the errormessage, and takean appropriateaction.

81



TIBCO-BW-PALETTE-ADBPLUGIN-500002.DataEventPoller Schema {0}throw exception {1}when execute publishingtable selector.

Error BW-Plugin Thrown whenexecuteQuery fails forpublishing table andSQLException isthrown.


TIBCO-BW-PALETTE-ADBPLUGIN-500003.DataEventPoller Schema {0}throw exception {1}when build publishingtable selector.

Error BW-Plugin Thrown whenprepareStatement failsfor publishing tableand SQLException isthrown.


TIBCO-BW-PALETTE-ADBPLUGIN-500004.DataEventPoller Schema {0}throw exception {1}when bind publishingtable selector.

Error BW-Plugin Thrown when settingparameter fails forpublishing table andSQLException isthrown.


TIBCO-BW-PALETTE-ADBPLUGIN-500005.DataEventPoller Schema {0}throw exception {1}when execute the maxsequence selector

Error BW-Plugin Thrown whenexecuteQuery fails formax sequence selectorand SQLException isthrown.


TIBCO-BW-PALETTE-ADBPLUGIN-500006.DataEventPoller Schema {0}throw exception {1}when build publishingtable max sequenceselector.

Error BW-Plugin Thrown whenprepareStatement failsfor max sequenceselector andSQLException isthrown.


TIBCO-BW-PALETTE-ADBPLUGIN-500007.DataEventPoller Schema {0}throw exception {1}when execute the minisequence selector.

Error BW-Plugin Thrown if there is noDataEventPoller table.


TIBCO-BW-PALETTE-ADBPLUGIN-500008.DataEventPoller Schema {0}throw exception {1}when build publishingtable mini sequenceselector.

Error BW-Plugin Thrown whenprepareStatement failsfor min sequenceselector andSQLException isthrown.


82



TIBCO-BW-PALETTE-ADBPLUGIN-500009.DataEventPoller Schema {0}throw exception {1}when get dbTable whosename ispublishingTableName.

Error BW-Plugin Thrown if there iserror fetching datafrom publishing table.


TIBCO-BW-PALETTE-ADBPLUGIN-500010.DataEventPoller Schema {0}throw exception {1}when build pub tableupdater.

Error BW-Plugin Thrown whenprepareStatement failswhile updatingpublishing table andSQLException isthrown.


TIBCO-BW-PALETTE-ADBPLUGIN-500011.DataEventPoller Schema {0}throw exception {1}when bind pub tableupdater.

Error BW-Plugin Thrown when settingparameter fails whileupdating publishingtable andSQLException isthrown


TIBCO-BW-PALETTE-ADBPLUGIN-500012.DataEventPoller Schema {0}throw exception {1}when manipulate S to Nstatus updater.

Error BW-Plugin Thrown whenupdating status fromS to N fails.



Error BW-Plugin Throws when ADBvalidation fails.


83




Error BW-Plugin Thrown when ADBsql Exception FAultoccurs. Scenario 1:Columns in sharedresource andpublishing table arenot same.Createshared resource withtable T columnscol1,col1. In dataevent poller activity,apply triggers.Thepublishing table P_Twill be generated.Now alter the originaltable T and addcolumn col3. Refindschema in sharedresource and fetchcolumnscol1,col1,col3. Nowrun the process. Inserta new record in tableT.


TIBCO-BW-PALETTE-ADBPLUGIN-500015.DataEventPoller Schema {0}throw exception {1}when constructminstance based onpublishing table

Error BW-Plugin Error fetching row ofpublishing table.SQLException isthrown


TIBCO-BW-PALETTE-ADBPLUGIN-500016.DataEventPoller Schema {0}throw exception {1}when fetch child data.

Error BW-Plugin Error fetching rows ofchild table.SQLException isthrown


TIBCO-BW-PALETTE-ADBPLUGIN-500017.DataEventPoller Schema {0}throw exception {1}when build childselector.

Error BW-Plugin Thrown whenprepareStatement failsfor building childselector.SQLException isthrown


TIBCO-BW-PALETTE-ADBPLUGIN-500018.DataEventPoller Schema {0}throw exception {1}when bind child selector.

Error BW-Plugin Thrown when settingparameter fails whilebuilding the childquery. SQL Exceptionis thrown.


84



TIBCO-BW-PALETTE-ADBPLUGIN-500019.DataEventPoller Schema {0}throw exception {1}when build pub loadbalancing marker.

Error BW-Plugin Thrown whenprepareStatement failswhile building theload balance updatequery. SQL Exceptionis thrown


TIBCO-BW-PALETTE-ADBPLUGIN-500020.DataEventPoller Schema {0}throw exception {1}when build pub loadbalancing pub tableselector.

Error BW-Plugin Thrown whenfetching the rowsfrom publishing tablefor load balancingselector. SQLException is thrown.


TIBCO-BW-PALETTE-ADBPLUGIN-500021.DataEventPoller Schema {0}throw exception {1}when bind pub loadbalancing marker.

Error BW-Plugin Thrown when settingparameters fail whilebuilding loadbalancing query. SQLException is thrown.


TIBCO-BW-PALETTE-ADBPLUGIN-500022.DataEventPoller Schema {0}throw exception {1}when execute pub loadbalancing marker.

Error BW-Plugin Thrown when updatequery fails for loadbalancing. SQLException is thrown.


TIBCO-BW-PALETTE-ADBPLUGIN-500023.DataEventPoller Schema {0}throw exception {1}when initialize theDBLockMechanism.

Error BW-Plugin Initializing the DBLock Mechanism.


TIBCO-BW-SR-ADBPLUGIN-100001.Logs related otStarting,stopping,updating shared resource

Trace BW-Plugin When userstarts,stops,updatesshared resource.


TIBCO-BW-SR-ADBPLUGIN-300001.Adding new configurationfor Shared Resourcewith name [{0}]

Info BW-Plugin Logs when usercreates new sharedresource


85



TIBCO-BW-SR-ADBPLUGIN-300002.Deleting Configuration forShared Resource withname[{0}]

Info BW-Plugin When user deletesconfiguration forshared resource


TIBCO-BW-SR-ADBPLUGIN-500001.Error creating sharedresource {0}. Exception:{1}

Error BW-Plugin If any error whilecreating sharedresource.


86


Documents

TIBCO ActiveMatrix BusinessWorks ... - TIBCO Documentation