TIB Adadb 6.3.0 Installation

TIBCO ActiveMatrix® Adapter
for Database
Installation
Software Release 6.3
October 2012
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR
BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED
ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED
SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY
OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A
LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT,
OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT
WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS
DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR
CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF
THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR
USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part
of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.
TIBCO, The Power of Now, TIBCO ActiveMatrix BusinessWorks, TIBCO Adapter SDK, TIBCO Administrator, TIBCO
Database Drivers Supplement, TIBCO Designer, TIBCO Enterprise Message Service, TIBCO Hawk, TIBCO Rendezvous,
and TIBCO Runtime Agent are either registered trademarks or trademarks of TIBCO Software Inc. in the United States
and/or other countries.
EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems,
Inc. in the U.S. and other countries.
All other product and company names and marks mentioned in this document are the property of their respective owners and
are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL
OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME
TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC
OPERATING SYSTEM PLATFORM.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES
ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED
IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR
CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR
INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT
NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.
Copyright © 1999-2012 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
| iii
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Changes from the Previous Release of this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
TIBCO ActiveMatrix Adapter for Database Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
How to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
Chapter 1 Installation Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Installation Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Installation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Installer Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Installer Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
System Memory Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Adapter Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Supported Databases and Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
ODBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Pre-installation Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Adapter Machine Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 2 Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Different Modes of Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
TIBCO ActiveMatrix Adapter for Database Installation

iv
| Contents
GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Different Modes of Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Chapter 3 Post-installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Post-installation Tasks on Microsoft Windows Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Configuring the Database Account Used by the Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Configuring the Adapter in TIBCO Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Optionally Installing Custom ODBC Drivers and Adding to PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Configuring the ODBC System Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Connecting to Different Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Installing Additional TIBCO Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Additional Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Post-installation Tasks on UNIX Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Setting Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Setting Directory Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Configuring the Adapter in TIBCO Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Configuring the ODBC System Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Optionally Installing Custom ODBC Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Installing Additional TIBCO Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Running the 32-bit Adapter on 64-bit TIBCO Runtime Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Chapter 4 Installation FAQs and Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Setting the DISPLAY Variable on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
JRE and JVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Fail to Install the Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Figures v
|
Figures
Figure 1 TIBCO Installation Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Figure 2 Custom Installation Profile Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 3 TIBCO Installation Manager Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 4 Product Uninstallation Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 5 System DSN in ODBC Data Source Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 6 Selecting an ODBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 7 General Tab in the ODBC Oracle Drivers Setup Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 8 Advanced Tab in the ODBC Driver Setup Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 9 Testing the Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 10 Selecting the DB2 Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 11 General Tab in the ODBC DB2 Driver Setup Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 12 Modify Bindings Tab in the ODBC DB2 Driver Setup Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 13 ODBC Driver for Teradata Setup and Options Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 14 Selecting the PostgreSQL Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 15 Filling in Fields on the ODBC Driver Setup for PostgreSQL Database . . . . . . . . . . . . . . . . . . . . . . 36
Figure 16 Testing the Connection to PostgreSQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 17 Selecting the EnterpriseDB Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 18 Filling in Fields on the ODBC Driver Setup for EnterpriseDB Database . . . . . . . . . . . . . . . . . . . . . 38

vi
| Figures

Tables vii
|
Tables
Table 1 General Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Table 2 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Table 3 TIBCO Adapter Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Table 4 ODBC Driver Supported Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Table 5 Adapter Machine Information Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Table 6 Database Information Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

viii
| Tables

| ix
Preface
This software may be available on multiple operating systems. However, not all
operating system platforms for a specific software version are released at the same
time. Please see the readme file for the availability of this software version on a
specific operating system platform.
TIBCO ActiveMatrix Adapter for Database software is a bidirectional gateway between

databases and applications configured for the TIBCO environment. The adapter supports
publication, subscription, and request-response interactions.
Topics
• Changes from the Previous Release of this Guide, page x

• Related Documentation, page xi
• Typographical Conventions, page xii
• Connecting with TIBCO Resources, page xiv

x
| Changes from the Previous Release of this Guide
Changes from the Previous Release of this Guide
This section itemizes the major changes from the previous release of this guide.
Support for DataDirect 7.0 ODBC Drivers

This release adds support for DataDirect 7.0 ODBC Drivers. See Post-installation Tasks
on page 23 for more details about installation.
Support for Using DataDirect Drivers to Connect to MySQL Database and

Teradata Database
This release adds support for using DataDirect drivers to connect to MySQL database and
Teradata database. See Supported Databases and Drivers on page 8 for more details.
Support for PostgreSQL Database and Postgres Plus Advanced Server

Database (EnterpriseDB)
This release adds support for PostgreSQL 9.1 database and EnterpriseDB 9.1 database.
See Supported Databases and Drivers on page 8 and Post-installation Tasks on page 23 for
more details about installation.
In this manual, EnterpriseDB is used to refer to the Postgres Plus Advanced Server
Database.
Running the 32-bit Adapter on 64-bit TIBCO Runtime Agent

This release adds the specification of how the 32-bit adapter works with the 64-bit TIBCO
Runtime Agent 5.7.3 and 5.7.4 in Windows platforms. See Running the 32-bit Adapter on
64-bit TIBCO Runtime Agent on page 47 for more details.

Preface xi
|
Related Documentation
This section lists documentation resources you may find useful.
TIBCO ActiveMatrix Adapter for Database Documentation

The following documents form the TIBCO ActiveMatrix Adapter for Database
documentation set:
• TIBCO ActiveMatrix Adapter for Database Concepts Read this manual to gain an
understanding of adapters in general that you can apply to the various tasks you may
undertake.
• TIBCO ActiveMatrix Adapter for Database Installation Read this manual to learn
how to install TIBCO ActiveMatrix Adapter for Database.
• TIBCO ActiveMatrix Adapter for Database Configuration and Deployment Read this
manual to understand how to create and configure adapter projects. Information on
deploying adapter projects is also included.
• TIBCO ActiveMatrix Adapter for Database Examples Read this manual to work
through the examples provided with the adapter.
• TIBCO ActiveMatrix Adapter for Database Release Notes Read this manual for a list
of new and changed features. This manual also contains lists of closed and known
issues for this release.
Other TIBCO Product Documentation

You may find it useful to read the documentation for the following TIBCO products:
• TIBCO® Adapter SDK
• TIBCO Administrator™
• TIBCO ActiveMatrix BusinessWorks™
• TIBCO® Database Drivers Supplement
• TIBCO Designer™
• TIBCO Enterprise Message Service™
• TIBCO Hawk®
• TIBCO Rendezvous®
• TIBCO Runtime Agent™

xii
| Typographical Conventions
Typographical Conventions
The following typographical conventions are used in this manual.
Table 1 General Typographical Conventions
Convention Use
ENV_NAME TIBCO products are installed into an installation environment. A product installed
into an installation environment does not access components in other installation
TIBCO_HOME
environments. Incompatible products and multiple instances of the same product
TIB_ADADB_HOME must be installed into different installation environments.
An installation environment consists of the following properties:
• Name Identifies the installation environment. The name is appended to the
name of Windows services created by the installer and is a component of the
path to the product in the Windows Start > All Programs menu. This directory is
referenced in documentation as ENV_NAME.
• Path The folder into which the product is installed. This folder is referenced in
documentation as TIBCO_HOME.
TIBCO ActiveMatrix Adapter for Database installs into a directory within a
TIBCO_HOME. This directory is referenced in documentation as TIB_ADADB_HOME.
The default value of TIB_ADADB_HOME depends on the operating system. For
example on Windows systems, the default value is C:\tibco\adapter\adadb\version.
code font Code font identifies commands, code examples, filenames, pathnames, and output
displayed in a command window. For example:
Use MyCommand to start the foo process.
bold code font Bold code font is used in the following ways:
• In procedures, to indicate what a user types. For example: Type admin.
• In large code samples, to indicate the parts of the sample that are of particular
interest.
• In command syntax, to indicate the default parameter for a command. For
example, if no parameter is specified, MyCommand is enabled:
MyCommand [enable | disable]

Preface xiii
|
Table 1 General Typographical Conventions (Cont’d)
Convention Use
italic font Italic font is used in the following ways:
• To indicate a document title. For example: See TIBCO ActiveMatrix
BusinessWorks Concepts.
• To introduce new terms. For example: A portal page may contain several
portlets. Portlets are mini-applications that run in a portal.
• To indicate a variable in a command or code syntax that you must replace. For
example: MyCommand PathName
Key combinations Key names separated by a plus sign indicate keys pressed simultaneously. For
example: Ctrl+C.
Key names separated by a comma and space indicate keys pressed one after the
other. For example: Esc, Ctrl+Q.
The note icon indicates information that is of special interest or importance, for
example, an additional action required only in certain circumstances.
The tip icon indicates an idea that could be useful, for example, a way to apply the
information provided in the current section to achieve a specific result.
The warning icon indicates the potential for a damaging situation, for example, data
loss or corruption if certain steps are taken or not taken.

xiv
| Connecting with TIBCO Resources
Connecting with TIBCO Resources
How to Join TIBCOmmunity

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

You can access TIBCO documentation here:
http://docs.tibco.com
How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, contact TIBCO
Support as follows:
• For an overview of TIBCO Support, and information about getting started with
TIBCO Support, visit this site:
http://www.tibco.com/services/support
• If you already have a valid maintenance or support contract, visit this site:
https://support.tibco.com
Entry to this site requires a username and password. If you do not have a username,
you can request one.

|1
Chapter 1 Installation Introduction
This chapter explains installation modes, requirements, and other options you should be
aware of before starting the installation. Before you install the adapter, read this chapter
and fill out the Pre-installation Worksheets on page 10.
Topics
• Installation Overview, page 2

• Installation Requirements, page 5
• Adapter Components, page 7
• Supported Databases and Drivers, page 8
• Pre-installation Worksheets, page 10

2
| Chapter 1 Installation Introduction
Installation Overview
This section gives an overview of the installer.
Installation Modes
Three installation modes are available: GUI, Console, and Silent.
GUI Mode
In the GUI Mode, the installer presents panels that allow you to make choices about
product selection, product location, and so on. To invoke the installer in GUI Mode,
double-click the executable.
Console Mode
Console Mode allows you to run the installer from the command prompt or terminal
window. This is useful if your machine does not have a GUI environment.
Silent Mode
Silent Mode installs the product using either default or custom settings that are saved in a
response file. Silent Mode installs the product without prompting you for information.
Installation Types
Two installation types are available: Typical and Custom.
• Typical Choose this type to install all components that are contained in the adapter.
• Custom Choose this type to select components to be installed in the adapter.
Installer Account
Microsoft Windows
You must have administrator privileges for the machine on which this product is installed.
If you do not have administrator privileges, the installer exits. You must then log out of the
system and log in as a user with the required privileges, or request your system
administrator to assign the privileges to your account.
If you intend to install the product on a network drive, ensure that the account used for
installation has permission to access the network drive.

Installation Overview 3
|
Installing on Microsoft Windows 2003 Terminal Server

There are two modes in Windows Terminal Server: Execute and Install. Users are logged
on by default in Execute mode, which allows them to run applications. To install an
adapter so that everyone can use it, log on as administrator in Install mode. When the
adapter is installed in the Install mode, the installation registry is maintained in
SystemDrive:\WINDOWS\.
Windows Terminal Server must be running in remote admin mode, not application sharing
mode. The adapter is not supported if installed on a machine that is using Windows
Terminal Server in application sharing mode.
The best way to install the adapter on Windows Terminal Server is to use the Add/Remove
Programs control panel applet. This automatically sets your mode to Install during the
installation and then back to Execute afterwards. Alternatively, you can manually change
your mode to Install before starting the installation by typing the following at a command
prompt:
C:\> change user /install
Change back to Execute mode after installation is complete by typing:

C:\> change user /execute
To check your current mode, type the following:

C:\> change user /query
UNIX
TIBCO ActiveMatrix Adapter for Database can be installed by any type of user:
• Regular user (non-root)
• Super-user (root)
While installing this product on UNIX platforms, ensure that the same installer account is
used to install all TIBCO Adapters products.
A graphic environment, such as CDE or X Windows is required to run the installer in GUI
Mode.
Installer Log File

The installer log file, tibco_universal_installer.username_install.log, is written to the
.TIBCO/install_timestamp folder of the user’s home directory. To change the location of the
installer log file, specify the option -V logFile=“myLogFile” when you run the installer.
The installer log file captures the following information:

4
• Installation environment details, such as user that invoked the installer, host name,
Java home in the environment, operating system details, and so on.
• List of assemblies installed.
• Information related to the Ant scripts that are executed by the installer.

Installation Requirements 5
|
Installation Requirements
This section describes the system memory requirements, software requirements, and
supported platforms for this product.
System Memory Requirements

A minimum of 256 MB of physical memory is required.
Supported Platforms
See the readme file for more details on the supported platforms, versions, and required
patches.
Software Requirements
You can install the software on different machines and use them across the network. For
example, you can use TIBCO Designer on one machine to configure a TIBCO
ActiveMatrix Adapter for Database adapter on another machine.
Table 2 lists the required and optional software products. The software products below are
distributed and installed separately from this product. See the readme file for the
supported versions.
Table 2 Software Requirements
Software Description
TIBCO Rendezvous Required. If you are going to use TIBCO Runtime Agent 5.7.1, you need to
install TIBCO Rendezvous 8.3.x separately before installing TIBCO Runtime
Agent.
TIBCO Runtime Agent Required. TIBCO Runtime Agent includes TIBCO Designer along with a
number of TIBCO and third-party libraries used by the adapter and other
TIBCO products. You must install TIBCO Runtime Agent before you install
TIBCO ActiveMatrix Adapter for Database.
Note: If the adapter is installed on 64-bit TIBCO Runtime Agent version 5.7.3
or 5.7.4, the adapter installation will be different. See Running the 32-bit
Adapter on 64-bit TIBCO Runtime Agent on page 47 for details.

6
Table 2 Software Requirements (Cont’d)
Software Description
TIBCO Administrator Required for deployment. TIBCO Administrator includes the following
modules:
• User Management. Management of authentication, roles and users, that is,
connecting roles (groups) and users to access control lists (ACLs). This
includes security for server-based projects at design time and for deployed
applications at runtime.
• Resource Management. Monitoring of machines and of all running
applications in a TIBCO administration domain. Alerts can be created, for
example, to notify an administrator if the number of processes or disk
usage exceeds a certain number.
• Application Management. Uploading of Enterprise Archive (EAR) files,
creation, configuration, deployment, and monitoring of applications. This
console is also used to start and stop applications.
TIBCO Administrator is available as a separate installation and can be
installed after installing the adapter.
TIBCO Enterprise Message Service Required. TIBCO Enterprise Message Service is used as the notification and
messaging backbone for TIBCO ActiveMatrix Adapter for Database. TIBCO
ActiveMatrix Adapter for Database is not necessarily installed on the machine
on which TIBCO Enterprise Message Service is installed.
Note that TIBCO Enterprise Message Service is also used by the TIBCO
ActiveMatrix SOAP and JMS binding types. The TIBCO ActiveMatrix
Adapter for Database license does not cover this usage of the included TIBCO
Enterprise Message Service software. You must separately license TIBCO
Enterprise Message Service or another supported JMS product for this usage
TIBCO Enterprise Message Service is available as a separate installation and
can be installed after the adapter is installed.
TIBCO Database Drivers Supplement Optional. TIBCO Database Drivers Supplement provides the licensed
DataDirect database JDBC drivers that can be used with TIBCO ActiveMatrix
Adapter for Database.
TIBCO ActiveMatrix BusinessWorks Optional. TIBCO ActiveMatrix BusinessWorks is a scalable, extensible, and
easy-to-use integration platform that allows you to develop integration
projects. TIBCO Adapters are typically part of integration projects created
using TIBCO ActiveMatrix BusinessWorks.
TIBCO ActiveMatrix BusinessWorks is available as a separate installation,
and can be installed after installing the adapter.

Adapter Components 7
|
Adapter Components
Table 3 describes the components of the adapter installation package.
Table 3 TIBCO Adapter Components
Component Description
Runtime This process does the actual work of passing and converting data to and from the vendor
application. Also, the required ODBC drivers are included in TIBCO ActiveMatrix Adapter
for Database software packages. See ODBC Drivers on page 8.
Design time Adapter-specific GUI that is loaded in TIBCO Designer (see next section for details) at
configuration time.
This component includes the palette and samples that demonstrate how TIBCO
ActiveMatrix Adapter for Database interacts with TIBCO ActiveMatrix BusinessWorks.
Documentation This component is required for context sensitive help.
The adapter installation package does not include JDBC drivers. For more information
about required JDBC drivers, see JDBC Drivers on page 9.

8
Supported Databases and Drivers
One of the following databases must be installed and configured for your system before
installing TIBCO ActiveMatrix Adapter for Database. You must be able to connect to the
database before starting installation. On Oracle, both the Enterprise Edition and Standard
Edition are supported.
The adapter supports both 32-bit and 64-bit versions, where applicable, for the databases
listed below.
The supported databases can be hosted on any platform supported by the database vendor.
ODBC Drivers
TIBCO ActiveMatrix Adapter for Database uses ODBC to access your database during
runtime. The adapter supports the ODBC driver that is supplied with the adapter
installation package as well as ODBC driver that is provided separately by the database
vendor listed in Table 4, ODBC Driver Supported Platform, on page 8.
Connecting to Remote Databases

TIBCO ActiveMatrix Adapter for Database can remotely connect to databases running on
other machines or different platforms, including a DB2 database running on z/OS or
iSeries systems. See Connecting to a DB2 z/OS Database on page 30 for details.
TIBCO ActiveMatrix Adapter for Database cannot be installed on an z/OS or iSeries

system.
ODBC Driver Documentation

The DataDirect documentation is available in the TIB_ADADB_HOME\odbc\help directory.
Table 4 shows the compatibility of the databases and the adapter supported operating
systems. Yes indicates that the adapter is supported on the operation system with the
databases listed. No indicates that the adapter is not supported on the operation system
with the databases listed.
Table 4 ODBC Driver Supported Platform
Adapter Supported Operating Systems

Database Windows Solaris Solaris AIX Linux SUSE HP HPUX
x861 SPARC x86 Power x86 x86 PA-RISC IA
Oracle Yes Yes Yes Yes Yes Yes Yes Yes

Supported Databases and Drivers 9
|
Table 4 ODBC Driver Supported Platform
Adapter Supported Operating Systems

Database Windows Solaris Solaris AIX Linux SUSE HP HPUX
x861 SPARC x86 Power x86 x86 PA-RISC IA
SQL Server Yes Yes Yes Yes Yes Yes Yes Yes
Sybase ASE Yes Yes Yes Yes Yes Yes Yes Yes
Sybase Anywhere Yes Yes Yes Yes Yes Yes Yes Yes
DB2 UDB Yes Yes Yes Yes Yes Yes Yes Yes
DB2 for z/OS2 Yes Yes Yes Yes Yes Yes Yes Yes
DB2 for iSeries2 Yes Yes Yes Yes Yes Yes Yes Yes
MySQL1 Yes Yes Yes Yes Yes Yes Yes Yes
Teradata1 Yes Yes Yes Yes Yes No Yes Yes
PostgreSQL Yes Yes Yes Yes Yes Yes Yes Yes
EnterpriseDB3 Yes No No No No No No No
1. Both vendor drivers included with the server installation and DataDirect drivers are supported.
2. Through remote connection only.
3. Only vendor drivers are supported.
JDBC Drivers
TIBCO ActiveMatrix Adapter for Database uses JDBC to access your database during
design time. The adapter design-time palette supports the JDBC drivers included in
TIBCO Database Drivers Supplement, as well as the JDBC drivers that are provided
separately by the database vendors. When configuring the adapter, you specify the JDBC
URL and the correct driver is automatically loaded.
The JDBC URLs are documented in TIBCO ActiveMatrix Adapter for Database
Configuration and Deployment.

10
Pre-installation Worksheets
The most time-consuming part of an adapter installation is the collection of environment

information and parameters. This section helps you complete this process. Use these
forms to gather information from the various system administrators and other sources
within your organization before installing the adapter.
• Adapter Machine Information, page 10
• Database Information, page 11
Adapter Machine Information

The information below is required during installation of TIBCO ActiveMatrix Adapter for
Database.
If you are connecting to a DB2 for z/OS database, you will need additional information, as
described for Windows in Post-installation Tasks on Microsoft Windows Platforms on
page 24, or for UNIX in Post-installation Tasks on UNIX Platforms on page 40.
Table 5 Adapter Machine Information Worksheet
Adapter Description Value for Your Machine

Information
Hostname Name of the machine on which the adapter is being installed.
(Example: adapter1.tibco.com)
IP address IP address of the machine on which the adapter is being

installed.
TIBCO home This is the directory where TIBCO Runtime Agent was
directory path installed. TIBCO Runtime Agent must be installed on each
machine where the adapter will be installed.
(By default, this is C:\tibco on Microsoft Windows)
Installer user Account to log on to the machine with and run the installer. This
account user must have write permission to the TIBCO home directory.
(Example: administrator)
Installer user Password for the installer user account above.

password
Installer user Network domain to which the user account above belongs.
domain (Windows (Example: ENGR2)
only)

Pre-installation Worksheets 11
|
Table 5 Adapter Machine Information Worksheet (Cont’d)
Adapter
Description Value for Your Machine
Information
Adapter installation Obtain the correct TIBCO ActiveMatrix Adapter for Database
package installation package. This is available on CD, FTP, network
drive, or http://download.tibco.com as appropriate.
ODBC driver The correct ODBC driver version for your database, see
version Supported Databases and Drivers on page 8.
ODBC driver The full path of the ODBC driver directory. Drivers are installed
directory path with the adapter or can also be third-party, see Supported
Databases and Drivers on page 8.
(By default, TIB_ADADB_HOME\odbc\Drivers)
Database Information
Most supported databases require you to enter these parameters to configure the adapter.
The specific parameter names and the type of information required depends on the
database and driver you are using. Check with your database administrator to determine
exactly what information will be needed for your system.
If you are connecting to a DB2 for z/OS database, you will need additional information, as
described for Microsoft Windows in Post-installation Tasks on Microsoft Windows
Platforms on page 24, or for UNIX in Post-installation Tasks on UNIX Platforms on
page 40.
Table 6 Database Information Worksheet
Database
Description Value for Your Database
Information
Data Source Name and A name and description you create that identifies this
description database configuration in the system.
(Example: Accounting)
Port Number The port number of the database listener.
SID The System Identifier that refers to the instance of the

database running on the server.
(Example: ORCL)

12
Table 6 Database Information Worksheet (Cont’d)
Database
Description Value for Your Database
Information
Server (or Host) The name, IP address, client connection string, or other
identifier of the database server and database to which the
adapter will connect.
(Example: Oracleserver or 199.226.224.34)
Database administrator Account that has database administration privileges and

account can create users.
Database administrator Password for the database administrator account.

password
Service name Name of the service to use when executing commands as

the database administrator.
(Example: adbsol27)
Database access New account created by the database administrator during

account configuration. The adapter uses this account to connect to
the database.
(Example: jsmith)
Database access Password for the database access account above.

account password

| 13
Chapter 2 Installation Steps
This chapter explains how to install and uninstall this product.
Topics
• Different Modes of Installation, page 14

• Different Modes of Uninstallation, page 19

14
| Chapter 2 Installation Steps
Different Modes of Installation
The following sections describe the installation process in the available installation
modes:
• GUI Mode, page 14
• Console Mode, page 16
• Silent Mode, page 17
GUI Mode
To install this product in GUI Mode, complete the following steps:
1. Open the physical media or download the installation package.
2. Extract the contents of the package to a temporary directory.
3. Navigate to the temporary directory.
4. Run TIBCOUniversalInstaller. You can do so in one of the following ways:
— Double-click the installer icon.
— On the command prompt, provide the absolute path of the installer file without
specifying any options. The installer defaults to GUI Mode.
5. Click the Next button on the Welcome dialog.
6. Read through the license text when the License Agreement dialog is displayed, select
the I Accept The Terms Of The License Agreement radio button, then click the
Next button.
7. Select the Use An Existing TIBCO_HOME radio button, and then click the Next
button on the TIBCO Installation Home dialog, as shown in Figure 1.

Different Modes of Installation 15
|
Figure 1 TIBCO Installation Home
An installation environment isolates product installations. A product installed into an

installation environment does not access components in other installation
environments. An installation environment consists of a name and path.
— Create A New TIBCO_HOME To install the product into a new installation
environment. This option is not suitable for the adapter. The adapter must be
installed into the existing TIBCO_HOME directory where TIBCO Rendezvous and
TIBCO Runtime Agent are installed.
— Use An Existing TIBCO_HOME To install the product into an existing installation
environment, select the environment from the drop-down list.
8. The Typical installation type is selected by default, and the checkboxes for all adapter
features are selected on the Installation Profile Selection dialog. You can directly click
the Next button without making any changes to continue the installation steps.
Or you can check the Customize Installation checkbox and select the adapter features
that you want to install from the following list, as shown in Figure 2.

16
Figure 2 Custom Installation Profile Selection
— Documentation includes the TIBCO ActiveMatrix Adapter for Database

documentation. The documentation is installed in the TIB_ADADB_HOME\doc
directory.
— Runtime includes the runtime tools for TIBCO ActiveMatrix Adapter for
Database.
— Design includes the palette and samples for TIBCO ActiveMatrix Adapter for
Database
9. Click the Next button, verify the list of products selected for installation in the
Pre-Install Summary dialog. Click the Install button to start the installation process.
10. Review the information listed in the Post-Install Summary dialog, then click the
Finish button to complete the installation process and exit the install wizard.
Console Mode
To install this product in Console Mode, complete the following steps:
3. Navigate to the temporary directory by using a console window.
4. Run TIBCOUniversalInstaller -console.
5. Complete the installation by responding to the console window prompts.

Different Modes of Installation 17
|
Silent Mode
In Silent Mode, the universal installer does not prompt for any inputs during installation.
Instead, the inputs are read from a response file that can be provided as a command-line
parameter. If no value is specified, the installer uses the default
TIBCOUniversalInstaller_adadb_version.silent file.
The TIBCOUniversalInstaller_adadb_version.silent file is packaged in the directory that contains the

universal installer. Edit the file with information for your environment before launching
the silent installation. The file includes comments that describe the installation properties
you can set. While you can use the TIBCOUniversalInstaller_adadb_version.silent file, it is good
practice to copy the file to a different name and use that file for the silent install.
The following procedure explains how to install the adapter in Silent Mode. If errors occur
during the installation, they will be listed in the installation log file located in the
User_Home/.TIBCO directory.
3. Navigate to the temporary directory by using a console window.
4. Make a copy of the TIBCOUniversalInstaller_adadb_version.silent file and rename the file.
5. Open the copied file by using a text editor, and update the install location, ENV_NAME,
and features to install as follows:
— Update the install location TIBCO ActiveMatrix Adapter for Database must be
installed in the same directory where other TIBCO adapters are installed. For
example, update the directory as follows:
<entry key="installationRoot">C:\tibco</entry>
— Update the ENV_NAME TIBCO ActiveMatrix Adapter for Database must use the
same ENV_NAME that other TIBCO adapters use.
For example, update ENV_NAME as follows:
<entry key="createNewEnvironment">false</entry>
<entry key="environmentName">TIBCO_HOME</entry>
— Update features to install Set the features that you want to install to true as
follows:
<entry key="feature_Adapter_adadb">true</entry>
<entry key="feature_Palette_adadb">true</entry>
<entry key="feature_Samples_adadb">true</entry>
<entry key="feature_ADB Documentation_adadb">true</entry>
6. Run the following commands:

Windows TIBCOUniversalInstaller.cmd -silent -V responseFile="myfilename.silent"

18
UNIX TIBCOUniversalInstaller.bin -silent -V responseFile="myfilename.silent"

Different Modes of Uninstallation 19
|
Different Modes of Uninstallation
This section describes how to uninstall TIBCO ActiveMatrix Adapter for Database in the
following available modes:
• GUI Mode, page 19
• Console Mode, page 21
GUI Mode
To uninstall the adapter, complete the following steps:
1. Shut down all running TIBCO Adapters applications.
2. Navigate to the TIBCO_HOME/tools/universal_installer directory and run
TIBCOUniversalInstaller. The TIBCO Installation Manager dialog is displayed.
3. Select the Uninstall Products From A TIBCO Home Location radio button, and
choose the TIBCO_HOME location from the TIBCO Home Location drop-down list on
the TIBCO Installation Manager dialog, as shown in Figure 3.
Figure 3 TIBCO Installation Manager Dialog
Click the Next button. The Welcome dialog is displayed.

4. Click the Next button on the Welcome dialog. The Uninstallation Type dialog is
displayed.

20
5. Select one of the following uninstallation options on the Uninstallation Type dialog:
— Custom Uninstall You can select the products to be removed.
If you select this option, click the Next button. The Product Uninstall Selection
dialog is displayed, as shown in Figure 4.
— Typical Uninstall The universal uninstaller removes all the products in the
TIBCO_HOME.
If you select this option, click the Next button, and go to step 7.
Figure 4 Product Uninstallation Selection Dialog
6. Check the checkboxes of products that you want to uninstall on the Product Uninstall
Selection dialog, and then click the Next button.
7. Review the Pre-Uninstall Summary on the Pre-Uninstall Summary dialog, and click
the Uninstall button to start the uninstallation process.
8. Review the Post-Uninstall Summary, and click the Finish button to exit the uninstall
wizard.

Different Modes of Uninstallation 21
|
Console Mode
To uninstall this product in Console Mode, complete the following steps:
1. Using a command window, navigate to the TIBCO_HOME\tools\universal_installer directory.
2. Type the following command at the command prompt:
TIBCOUniversalInstaller.exe -console
3. Complete the uninstallation by responding to the console window prompts.

22

| 23
Chapter 3 Post-installation Tasks
This chapter explains the tasks to perform after installation.
Topics
• Post-installation Tasks on Microsoft Windows Platforms, page 24

• Post-installation Tasks on UNIX Platforms, page 40
• Running the 32-bit Adapter on 64-bit TIBCO Runtime Agent, page 47

24
| Chapter 3 Post-installation Tasks
Post-installation Tasks on Microsoft Windows Platforms
Before running TIBCO ActiveMatrix Adapter for Database on Microsoft Windows

platforms, you need to complete the following tasks:
• Configuring the Database Account Used by the Adapter, page 24
• Configuring the Adapter in TIBCO Designer, page 25
• Optionally Installing Custom ODBC Drivers and Adding to PATH, page 25
• Configuring the ODBC System Data Source, page 26
• Connecting to Different Databases, page 30
• Installing Additional TIBCO Software, page 39
• Additional Tasks, page 39
Configuring the Database Account Used by the Adapter

SQL scripts are provided to set up the database account used by the adapter. The
TIB_ADADB_HOME\config directory contains subdirectories for supported databases. Each
subdirectory contains one or more scripts that are specific to that database vendor.
The create_user script creates a database user account with the necessary privileges required
for the adapter. If you are using Oracle and will be using the alerter, this user also needs
the privilege to access the alerter package.
1. Open a command window and change directory to your database directory. For
example, for Oracle:
cd TIB_ADADB_HOME\config\oracle
2. Change the create_user script by using a text editor to identify the account name and
password for the database user who will run the adapter. If you are using Oracle and
will be using the alerter, also provide the account name to use. For example, for
Oracle:
CREATE USER karlh IDENTIFIED BY adbuser;
GRANT CONNECT, RESOURCE TO karlh IDENTIFIED BY adbuser;
-- For Alerter use only

GRANT EXECUTE on DBMS_AQ to karlh;
GRANT EXECUTE on DBMS_AQADM to karlh;
This account is used to connect to the database and access tables created when
configuring an adapter. Note that a publication source table or subscription destination
table can belong to a different schema than the default specified in the create_user script.

Post-installation Tasks on Microsoft Windows Platforms 25
|
For more information, see TIBCO ActiveMatrix Adapter for Database Configuration
and Deployment.
3. Execute the create_user script as the database administrator. For example, for Oracle:
sqlplus dba_user_id/dba_password@service @create_user.sql
4. If you are using Oracle and will be using the alerter, also execute the alerter.sql script.
This script sets up the tables used by the alerter. Use the database user account created
in step 2. For example:
sqlplus dba_user_id/dba_password@service @alerter.sql
Configuring the Adapter in TIBCO Designer
The step applies to MySQL, PostgreSQL, and Teradata database.
When configuring the adapter instance in TIBCO Designer, you need to add the JDBC
driver file into the adapter installation library directory: TIB_ADADB_HOME\lib
For example:
For MySQL database:
TIB_ADADB_HOME\lib\mysql-connector-java-version-bin.jar
For Teradata database:
TIB_ADADB_HOME\lib\tdgssconfig.jar
TIB_ADADB_HOME\lib\terajdbc4.jar
For PostgreSQL database:
TIB_ADADB_HOME\lib\postgresql-9.0-801.jdbc3.jar
TIB_ADADB_HOME\lib\postgresql-9.0-801.jdbc4.jar
Optionally Installing Custom ODBC Drivers and Adding to PATH

Perform the following procedure, only if you are using database drivers supplied by your
database vendor, instead of the database drivers provided by TIBCO.
If you are using Oracle with a non-wire protocol driver, you must provide the
ORACLE_HOME\bin location to the tibco.env.CUSTOM_PATH property in the adapter TRA
properties file: TIB_ADADB_HOME\bin\adbagent.tra.
If you are using Teradata, you must specify the shared ICU library path and Teradata client
utility (CLI) path in the adapter TRA properties file: TIB_ADADB_HOME\bin\adbagent.tra.
tibco.env.CUSTOM_PATH
TERADATA_HOME/Client/version/CLIv2;TERADATA_HOME/Client/version/Shared ICU Libraries for
Teradata/lib

26
1. Install the ODBC drivers according to the instructions provided by your database
vendor.
2. Add the location of your drivers to the PATH system variable according to the
instructions provided by your database vendor.
3. Continue with Configuring the ODBC System Data Source on page 26.
Configuring the ODBC System Data Source

If you are using a DB2 z/OS database, proceed to Connecting to a DB2 z/OS Database on
page 30. If you are using a Teradata database, proceed to Connecting to a Teradata
Database on page 33. If you are using a PostgreSQL database, proceed to Connecting to a
PostgreSQL Database on page 35. This task applies to all other databases.
You must define a System DSN, not a User DSN. If you define a User DSN, the adapter
will not be visible in the TIBCO Administrator GUI.
If your Microsoft Windows platform is a 64-bit one, you have to open the 32-bit ODBC
Administrator located at C:\WINDOWS\sysWOW64\odbcad32.exe to view and configure the 32-bit
ODBC driver data sources.
1. Navigate to the Control Panel window, then locate and double-click the Data Sources
(ODBC) icon.
2. Click the System DSN tab, then click the Add... button on the ODBC Data Source
Administrator dialog, as shown in Figure 5.

|
Figure 5 System DSN in ODBC Data Source Administrator
3. Select an ODBC driver and click the Finish button on the Create New Data Source
dialog, as shown in Figure 6.
Figure 6 Selecting an ODBC Driver
4. Click the Configure... button on the ODBC Data Source Administrator dialog, the
ODBC Driver Setup dialog is displayed. Click the General tab and type appropriate
values in the fields. Click the Help button for an explanation of each field.

28
Figure 7 General Tab in the ODBC Oracle Drivers Setup Dialog
5. Click the Advanced tab, check the Procedure Returns Results checkbox. This is
necessary for the ODBC driver to return retrieved data from stored procedures for
Request-Reply operations.
Also, check the Enable Timestamp with Timezone checkbox. For more information,
see TIBCO ActiveMatrix Adapter for Database Configuration and Deployment.
Fill in the other fields as required for your configuration, or accept the defaults.

|
Figure 8 Advanced Tab in the ODBC Driver Setup Dialog
6. Click the Apply button, then click the Test Connect button to test the connection.
Type the username and password, then click the OK button.
Figure 9 Testing the Connection
7. Click the OK button in the ODBC Driver Setup dialog to save the object, then click
the OK button to exit.

30
Connecting to Different Databases

This section takes several databases as examples to explain how to connect different
databases:
• Connecting to a DB2 z/OS Database, page 30
• Connecting to a Teradata Database, page 33
• Connecting to a PostgreSQL Database, page 35
• Connecting to an EnterpriseDB, page 37
Connecting to a DB2 z/OS Database

The adapter can connect to a DB2 database running on z/OS. (The adapter itself cannot
run on z/OS.)
In order to do so, you need to create ODBC and JDBC packages on the machine where
DB2 z/OS is running. Once the packages are created, they can be used by PUBLIC. The
packages can be used as long as you are using the TIBCO 5.00 DB2 Wire Protocol driver.
If you upgrade to a newer driver, you will need to repeat these procedures with the new
driver.
For this procedure, the z/OS system logon and password must have DB2 BIND authority.
For more information, see the section Configuring and Connecting to Data Sources in
Chapter 5, The DB2 Wire Protocol Driver in the Progress DataDirect Connect Series for
ODBC User’s Guide, available in TIB_ADADB_HOME\odbc\help.
To create the ODBC packages on the machine where DB2 z/OS database is running,
follow these steps:
1. On the machine where TIBCO ActiveMatrix Adapter for Database is installed,
navigate to the Control Panel, then locate and double-click the Data Sources
(ODBC) icon.
2. Click the System DSN tab, then click the Add... button. The Create New Data Source
dialog is displayed.
3. Select the TIBCO 7.0.0 DB2 Wire Protocol item from the driver list, and click the
Finish button.

|
Figure 10 Selecting the DB2 Driver
4. Fill in the fields on the ODBC DB2 Wire Protocol Driver Setup dialog according to
the configuration of the machine where DB2 for z/OS is running. The dialog below
shows sample data. Click the Help button for the field descriptions.
Figure 11 General Tab in the ODBC DB2 Driver Setup Dialog

32
5. Click the Modify Bindings tab. Fill in the fields according to the configuration of the
machine where DB2 for z/OS is running. Figure 12 shows sample data. Click the Help
button for field descriptions.
Figure 12 Modify Bindings Tab in the ODBC DB2 Driver Setup Dialog
6. Click the Modify Bindings button to generate the ODBC packages on the machine
where DB2 for z/OS is running. You will need your z/OS system logon and password.
A status message displays when the packages are created.
To verify the packages, submit a SQL statement to execute in DB2 for z/OS using, for
example, SPUFI from TSO/ISPF or DB2 Command Center from NT. The following
statement uses the values shown in step 4 above; use values that are appropriate to your
configuration.
SELECT * FROM SYSIBM.SYSPACKAGE where name like ’DEF00%’ and COLLI = ’DATADIRECT00’
If output similar to the following appears, the packages have been successfully created.
LOCATION COLLID NAME CONTOKEN
---------+---------+---------+---------+---------+-------
DATADIRECT00 DEF00A ìàâàêà .
DATADIRECT00 DEF00B ìàâàêà .
DATADIRECT00 DEF00C ìàâàêà .

|
To create the JDBC packages on the machine where DB2 for z/OS is running, follow these
steps:
1. On the machine where TIBCO ActiveMatrix Adapter for Database is installed, start
TIBCO Designer and display the Connection tab for the adapter.
2. Enter the following JDBC driver and URL information:
— JDBC Driver tibcosoftwareinc.jdbc.db2.DB2Driver
— JDBC URL jdbc:tibcosoftwareinc:db2://server_name:port;

locationName=DB2_location_name;collectionName=DATADIRECT00;packageName=DEF00;createD
efaultPackage=true;embedded=true
3. Click the Test Connection button to generate the JDBC packages on the machine
where DB2 for z/OS is running. You will need your z/OS system logon and password.
When the packages are created, a Successful Connection message displays and three
packages are cataloged in DB2 for z/OS.
To verify the packages, submit a SQL statement to execute in DB2 for z/OS using, for
example, SPUFI from TSO/ISPF or DB2 Command Center from NT. The following
statement uses the values shown in step 2 above; use values that are appropriate to your
configuration.
SELECT * FROM SYSIBM.SYSPACKAGE where name like 'DEF00%' and COLLID = 'DATADIRECT00'
If output similar to the following appears, the packages have been successfully created.
LOCATION COLLID NAME CONTOKEN
---------+---------+---------+---------+---------+-------
DATADIRECT00 DEF00A ¢àâä.àâ.
DATADIRECT00 DEF00B ¢àâä.àâ.
DATADIRECT00 DEF00C ¢àâä.àâ.
Connecting to a Teradata Database
The following instruction is based on the Windows Server 2008 R2 platform.
To connect to a Teradata database, complete the following steps:

(ODBC) icon.

34
dialog is displayed.
3. Select the Teradata item from the Name column, and click the Finish button.
4. Fill in the fields on the ODBC Driver Setup For Teradata Database dialog according to
the configuration of the machine where Teradata database is running. Click the Help
button for the field descriptions.
5. Click the Options >> button on the ODBC Driver Setup For Teradata Database
dialog. The Teradata ODBC Driver Options dialog is displayed, as shown in
Figure 13.
Figure 13 ODBC Driver for Teradata Setup and Options Dialog

|
Complete the following settings, then click the OK button:

— Check the Run In Quiet Mode checkbox. This option controls whether message
boxes are displayed.
— Check the Disable CALL To EXEC Conversion checkbox. This option
implements the CALL statement with an escape clause: CALL name (...).
— Check the Use Regional Settings for Decimal Symbol checkbox. This option
allows the ODBC Driver for Teradata to use regional settings to determine the
decimal symbol.
— Check the Use Native Large Object Support checkbox. This option enforces
native LOB data type mapping, and it is the default mapping for a Teradata
database with LOB support:
ODBC data type SQL_LONGVARBINARY is mapped to the Teradata BLOB
feature.
ODBC data type SQL_LONGVARCHAR is mapped to the Teradata CLOB
feature.
— Check the Return Output Parameters As ResultSet checkbox. This option
retrieves the stored procedure output parameters by ODBC Driver for Teradata,
and the value of INOUT and OUT parameters are returned the same way as the result
set.
— Check the Enable Extended Statement Information checkbox. This option
allows the ODBC Driver for Teradata requests and uses extended statement
information from the database if the database supports it.
6. Click the OK button on the ODBC Driver Setup dialog to save the object, then click
the OK button to exit.
Connecting to a PostgreSQL Database

To connect to a PostgreSQL database, complete the following steps:
(ODBC) icon. The ODBC Data Source Administrator dialog is displayed.

36
Figure 14 Selecting the PostgreSQL Driver
3. Select the TIBCO 7.00 PostgreSQL Wire Protocol item from the Name column, and
then click the Finish button in the Create New Data Source dialog. The ODBC
PostgreSQL Wire Protocol Driver Setup dialog is displayed, as shown in Figure 15.
Figure 15 Filling in Fields on the ODBC Driver Setup for PostgreSQL Database
4. Fill in the fields on the ODBC PostgreSQL Wire Protocol Driver Setup dialog
according to the configuration of the machine where the PostgreSQL database is
running. Click the Apply button to save the configuration. Then click the Test

|
Connect button to test the connection. The Logon to PostgreSQL Wire Protocol
5. Type the username and password in the Logon to PostgreSQL Wire Protocol dialog,
then click the OK button.
Figure 16 Testing the Connection to PostgreSQL
6. Click the OK button in the ODBC Driver Setup dialog to save the configuration.
7. Click the OK button in the ODBC Data Source Administrator dialog to exit.
Connecting to an EnterpriseDB
To connect to an EnterpriseDB, complete the following steps:
(ODBC) icon.

38
Figure 17 Selecting the EnterpriseDB Driver
3. Select the EnterpriseDB 9.1 (ANSI) or EnterpriseDB 9.1 (UNICODE) item from
the Name column, and click the Finish button. The EnterpriseDB ODBC Driver
Figure 18 Filling in Fields on the ODBC Driver Setup for EnterpriseDB Database
4. Fill in the fields on the dialog according to the configuration of the machine where
EnterpriseDB database is running. Then, click the Test button to test the connection.
The Connection Test dialog is displayed.
5. Click the OK button in the Connection Test dialog if it successfully connected. Click
the Save button to save the configuration in the EnterpriseDB ODBC Driver dialog.
6. Click the OK button in the ODBC Data Source Administrator dialog to exit.

|
Installing Additional TIBCO Software

If you will be using any of the following TIBCO products, install them now. These
products are not provided with TIBCO ActiveMatrix Adapter for Database.
Additional Tasks
If using the SSL feature for ODBC drivers, the path to the driver libraries need to be added
to the environment variable PATH.
For example, set PATH=TIB_ADADB_HOME\odbc\Drivers;%PATH%
TIBCO ActiveMatrix Adapter for Database is now installed. See TIBCO ActiveMatrix
Adapter for Database Configuration and Deployment for additional configuration tasks
and instructions to perform various procedures, including tutorials.

40
Post-installation Tasks on UNIX Platforms
Before running TIBCO ActiveMatrix Adapter for Database on a UNIX platform, you need
to complete the following tasks:
• Setting Environment Variables, page 40
• Setting Directory Permissions, page 40
• Configuring the Adapter in TIBCO Designer, page 41
• Configuring the ODBC System Data Source, page 42
• Optionally Installing Custom ODBC Drivers, page 42
• Installing Additional TIBCO Software, page 46
Setting Environment Variables

Certain changes to the environment variable settings are required before running TIBCO
ActiveMatrix Adapter for Database. Execute the appropriate file to automatically make
these changes.
When using the Oracle non-wire protocol driver, ODBC_HOME/lib must always appear in
LD_LIBRARY_PATH before any database vendor's lib directory, such as ORACLE_HOME/lib.
For csh, execute TIB_ADADB_HOME/bin/adbagent_env.csh, as shown:

% source adbagent_env.csh
For sh and ksh, execute TIB_ADADB_HOME/bin/adbagent_env.sh, as shown:

$ . adbagent_env.sh
The file modifies the following environment variables on UNIX platforms:

• SHLIB_PATH (on HP-UX only)
• LD_LIBRARY_PATH (on Solaris, Red Hat Linux, and SUSE Linux)
• LIBPATH (on AIX only)
Setting Directory Permissions

Depending on whether a repository server is used, and whether TIBCO Administrator is
used to set access permissions, users may need a TIBCO Administrator account. See your
TIBCO Administrator guide for details.

Post-installation Tasks on UNIX Platforms 41
|
Make sure that all adapter users have read and write permissions for the odbc.ini file. This
file is located in TIB_ADADB_HOME/odbc.
Make sure that all adapter users have read, write, and execute permissions for the
following directories where the adapter files and configuration information are stored:
TIB_ADADB_HOME/bin
TIB_ADADB_HOME/logs
TIB_ADADB_HOME/ledger
TIB_ADADB_HOME/sql
TIBCO_HOME/tra/TRA_version/logs
TIBCO_HOME/logs
For example, if you install the adapter in /opt/tibco, you can make these directories writable
for all other users by executing the following commands:
% chmod a+w /opt/tibco/adapter/adadb/version/bin
% chmod a+w /opt/tibco/adapter/adadb/version/logs
% chmod a+w /opt/tibco/adapter/adadb/version/ledger
% chmod a+w /opt/tibco/adapter/adadb/version/sql
% chmod a+w /opt/tibco/tra/TRA_version/logs
Configuring the Adapter in TIBCO Designer
The step applies to MySQL and Teradata database.
When configuring the adapter instance in TIBCO Designer, you need to add the JDBC
driver file into the adapter installation library directory: TIB_ADADB_HOME/lib
For example:
For MySQL database:
TIB_ADADB_HOME/lib/mysql-connector-java-version-bin.jar
For Teradata database:
TIB_ADADB_HOME/lib/tdgssconfig.jar
TIB_ADADB_HOME/lib/terajdbc4.jar
For PostgreSQL database:
TIB_ADADB_HOME/lib/postgresql-9.0-801.jdbc3
TIB_ADADB_HOME/lib/postgresql-9.0-801.jdbc4

42
Configuring the ODBC System Data Source
This step applies to DataDirect database drivers only.
The data source on UNIX systems is configured by using the odbc.ini file. This file is
located in TIB_ADADB_HOME/odbc.
See the ODBC driver documentation for information on configuring your system data
sources.
For Oracle, the EnableTimestampWithTimeZone parameter in the odbc.ini file is set to 1. For more
information, see TIBCO ActiveMatrix Adapter for Database Configuration and
Deployment.
The adapter can connect to a DB2 database running on z/OS. (TIBCO ActiveMatrix
Adapter for Database itself cannot run on z/OS.)
In order to connect to the database, you need to create ODBC and JDBC packages on the
machine where DB2 for z/OS is running. Once the packages are created, they can be used
by PUBLIC. The packages can be used as long as you are using the TIBCO 5.30 DB2
Wire Protocol driver. If you upgrade to a newer driver, you will need to repeat these
procedures with the new driver.
To connect to a DB2 for z/OS database, follow the instructions in the section Configuring
and Connecting to Data Sources in Chapter 5, The DB2 Wire Protocol Driver in Progress
DataDirect Connect Series for ODBC User’s Guide, available at TIB_ADADB_HOME/doc/help.
For this procedure, the z/OS system logon and password must have DB2 BIND authority.
Optionally Installing Custom ODBC Drivers
This step applies to the vendor ODBC driver on UNIX only.

The current version of the adapter supports MySQL and Teradata ODBC drivers.
If you are using a MySQL database, proceed to Connecting to a MySQL Database on

page 43. If you are using a Teradata database, proceed to Connecting to a Teradata

|
Database on page 45.
Connecting to a MySQL Database

To set up the vendor ODBC driver, follow these steps:
1. Download unixODBC source code from http://www.unixodbc.org.
2. Compile and generate unixODBC libraries and programs as follows:
a. Unzip the source code tar.gz file to a folder, for example:
/home/adb/odbc/installation/unixODBC-2.2.14
b. Open the folder and run the ./Configure command. By default, the files are installed
into the /usr/local directory. As is usual with configure, this location can be changed
by altering the prefix option to configure.
./configure --prefix=/home/adb/unixODBC --enable-gui=no
c. Run the make command.

d. Run the make install command.
The /home/adb/unixODBC folder is generated, and referenced as unixODBC_HOME in
the following section. In this folder, there are lib, bin, include, and etc folders.
3. Install the ODBC driver from MySQL on UNIX.
a. Download MySQL ODBC driver from http://www.mysql.com.
b. Unzip the tar.gz file into a folder, for example:
/home/adb/odbc/installation/mysql/mysql-connector-odbc-5.1.5-linux-x86-32bit
c. Enter the lib directory of this folder, and find the MySQL ODBC driver library,
libmyodbc5.so, and the MySQL ODBC setup library for ODBCConfig GUI tool of
unixODBC, libmyodbc3S.so.
Use odbcinst tool of unixODBC to register the MySQL ODBC driver.
Go to the $unixODBC_HOME/bin directory, and find the odbcinst command there.
Create an odbcinst_mysql.ini template file for MySQL ODBC driver. For example:
[MySQL ODBC 5.1 Driver]
Description = MySQL 5.1 Driver for Linux
Driver = /home/adb/odbc/installation/mysql/mysql-connector-odbc-5.1.5-linux-x86-32bit/lib/libmyodbc5.so
SETUP =
/home/adb/odbc/installation/mysql/mysql-connector-odbc-5.1.5-linux-x86-32bit/lib/libmyodbc3S.so
Run the following command:

./odbcinst -i -d -f <Path of odbcinst_mysql.ini>

44
The args to odbcinst are as follows:

-i install
-d driver
-f name of template file
d. Use odbcinst tool of unixODBC to add a DSN for MySQL.

Create an odbc_mysql.ini template file for MySQL ODBC driver. For example:
[MySQL-test]
Description = MySQL test database
Driver = MySQL ODBC 5.1 Driver
SERVER = localhost
USER = ODBC
PASSWORD =
PORT = 3306
DATABASE = test
option = 0
initstmt =
socket =
sslca =
sslcapath =
sslcert =
sslcipher =
sslkey =
charset =
sslverify =
readtimeout =
writetimeout =
Run the following command:

/odbcinst -i -s -h -f path_of_odbc_mysql.ini
The args to odbcinst are as follows:

-i install

|
-s data source
-h user dsn
-f name of template file
4. Test the DSN connection

You can choose one of the following two ways to test the DSN connection:
— Use DataManager GUI tool provided by unixODBC.
— Use isql command tool provided by unixODBC:
./isql dsn user password
Both of them are in the $unixODBC_HOME/bin directory.

5. Set up the environment for the adapter.
— After finishing Setting Environment Variables on page 40, run the following
commands:
export LD_LIBRARY_PATH=unixODBC_HOME/lib:$LD_LIBRARY_PATH
export ODBCINI=path_of_odbc_mysql.ini
— Make the following changes in the adapter TRA properties file:

TIB_ADADB_HOME/bin/adbagent.tra
tibco.env.ODBCINI /home/adb/unixODBC/dsn_template/MySQL_dsn_template.ini
tibco.env.CUSTOM_LIB_PATH unixODBC_HOME/lib%PSP%%TIB_ADADB_HOME%/odbc/lib
Connecting to a Teradata Database

To set up the vendor ODBC driver, follow these steps:
1. Download the Teradata ODBC driver from http://www.teradata.com.
2. Install the Teradata ODBC driver.

46
3. Set up the environment for the adapter.

— After completing Setting Environment Variables on page 40, run the following
commands:
export
LD_LIBRARY_PATH=TERADATA_HOME/teradata_version/client/odbc_32/lib:$LD_LIBRARY_
PATH
export ODBCINI=path_of_odbc_tera.ini
— Make the following changes in adapter TRA properties file:

TIB_ADADB_HOME/bin/adbagent.tra
tibco.env.ODBCINI path_of_odbc_tera.ini
tibco.env.CUSTOM_LIB_PATH
TERADATA_HOME/teradata_version/client/odbc_32/lib:path_of_other library files
On HP-UX IA platform, the adapter uses a 64-bit driver, so for all the ODBC driver paths,
you must point to the odbc_64 directory instead of odbc_32.
Installing Additional TIBCO Software

If you will be using any of the following TIBCO products, install them now. These
products are not provided with TIBCO ActiveMatrix Adapter for Database.

Running the 32-bit Adapter on 64-bit TIBCO Runtime Agent 47
|
Running the 32-bit Adapter on 64-bit TIBCO Runtime Agent
• Do not install the 32-bit TIBCO RV using installing 32-bit TIBCO TRA which
embeds the 32-bit TIBCO RV installation.
• The following procedure applies for all versions Windows platforms supported by
TIBCO ActiveMatrix Adapter for Database.
• The following procedure applies only for 64-bit TRA 5.7.3 and 5.7.4.
To ensure 32-bit TIBCO ActiveMatrix Adapter for Database can run on 64-bit TIBCO
Runtime Agent version 5.7.4, you need to complete the following steps:
1. Install 64-bit TIBCO Rendezvous (RV) and TIBCO Runtime Agent (TRA) 5.7.3 or
5.7.4 in one installation environment. For example: 64BIT_TIBCO_HOME.
2. Install 32-bit TIBCO RV and TRA 5.7.3 or 5.7.4 in a new installation environment.
For example: 32BIT_TIBCO_HOME.
3. Install 32-bit TIBCO ActiveMatrix Adapter for Database in 64BIT_TIBCO_HOME.
4. Make the following changes in the adbagent.tra file which is in the
TIB_ADADB_HOME\bin directory.
— Update the tibco.env.RV_HOME parameter to point to the 32-bit TIBCO RV libraries.

For example: tibco.env.RV_HOME 32BIT_TIBCO_HOME/tibrv/RV_version
— Add the 32-bit TRA binary directory to the CUSTOM_PATH variable:
tibco.env.CUSTOM_PATH 32BIT_TIBCO_HOME/tra/TRA_version/bin
— Add %TIB_SDK_HOME%/bin before %TIB_SDK_HOME%/BIN/64 to the tibco.env.PATH

parameter.

48

| 49
Chapter 4 Installation FAQs and Troubleshooting
This section lists some common installation errors along with their causes and solutions.
Topics
• Setting the DISPLAY Variable on UNIX, page 50

• JRE and JVM, page 51
• Fail to Install the Adapter, page 52

50
| Chapter 4 Installation FAQs and Troubleshooting
Setting the DISPLAY Variable on UNIX
The installer on UNIX usually opens an additional window for graphics when operating in
GUI Mode. The DISPLAY environment variable tells the installer on which computer to
open the window. If this variable is not set, the installer will either wait or abort after
displaying the following output:
InstallShield Wizard
Initializing InstallShield Wizard...
Preparing Java(tm) Virtual Machine...
...................................
...................................
........
You set the DISPLAY variable to the IP address or name of the computer on which the
installer graphics window are to be displayed, followed by a screen address, which can be
:0.0. For example:
# Bourne shell
DISPLAY=ip_address:0.0; export DISPLAY
# Korn shell
export DISPLAY=ip_address:0.0
# C-shell
setenv DISPLAY ip_address:0.0
For example, consider a scenario where you need to install the adapter on a remote
HP-UX machine (named itaska). Because you have a Solaris 5.6 machine (named alaska) that
has a video card and monitor installed, you can run an X-window application on it. So you
decide to telnet to itaska from alaska.
When you telnet to itaska, you will not get access to itaska's monitor and will be unable to
display an X-window application. That is why you must set the DISPLAY variable, which
instructs the X-server to redirect all windows to the computer set in the variable. Before
doing so, the computer (specified in the DISPLAY variable) must give permissions to share
its monitor.
alaska> xhost + # give permission for all to its share monitor
alaska> telnet itaska
Welcome to HP-UX itaska 11.00
User:
Password:
itaska> export DISPLAY=alaska:0.0 # set display on alaska
itaska> installation_package

JRE and JVM 51
|
JRE and JVM
What should I do if JVM crashes when I run the installer

The installer first extracts the bundled JVM into a temporary area, then uses it to launch
itself. If the JVM crashes, you can still run the installer using another JVM, preferably
JVM 1.5 or higher. The syntax is shown below.
• For Windows:
installation_package -s -a -is:javahome C:\j2sdk1.6.0
• For UNIX (using Solaris 8 as an example):
installation_package -is:javahome /opt/jre160
The javahome directory must contain bin/java.exe or bin/java.

The installer will use your JRE to launch itself.

52
| Chapter 4 Installation FAQs and Troubleshooting
Fail to Install the Adapter
On HP-UX and AIX platforms, even though the correct version of TIBCO Runtime Agent
is already installed on the system, installation of an adapter that depends on TIBCO
Runtime Agent may fail in the dependency resolution.
The TIBCO product installer maintains the registry information in the
vpd.properties.tibco.system_name file. The value for system_name is determined by
InetAddress.getLocalHost().getHostName(). However, the method getHostName(), returns different
values based on the JRE versions used. For example, on AIX, JRE 1.3.1 returns only
system_name, whereas JRE 1.4.0 returns system_name.domain_name. Because of this, the
installer is not able to load the correct registry file.
Resolution
On UNIX platforms, the installer registry file vpd.properties.tibco.system_name is located in the
user's home directory.
Case 1: If the vpd.properties.tibco.system_name file exists:
$ cd user's_home_directory
$ ln -s vpd.properties.tibco.system_name vpd.properties.tibco.system_name.domain_name
For example:
$ cd ~
$ ln -s vpd.properties.tibco.upside vpd.properties.tibco.upside.tibco.com
where upside is system_name, and tibco.com is domain_name

Case 2: If the vpd.properties.tibco.system_name.domain_name file exists:
$ cd user's_home_directory
$ ln -s vpd.properties.tibco.system_name.domain_name vpd.properties.tibco.system_name
For example:
$ cd ~
$ ln -s vpd.properties.tibco.upside.tibco.com vpd.properties.tibco.upside
where upside is system_name, and tibco.com is domain_name.

| 53
Index
C O
changes from the previous release of TIBCO ActiveMatrix ODBC drivers documentation 8
Adapter for Database Installation x
configuring the ODBC system data source 26, 42
connecting to different databases 30
customer support xiv S
support, contacting xiv
E
ENV_NAME xii T
technical support xiv
TIB_ADADB_HOME xii
I TIBCO_HOME xii
installation modes
Console Mode 2
GUI Mode 2 U
Silent Mode 2
installation procedure uninstallation
Console Mode 16 Console Mode 21
GUI Mode 14 GUI Mode 19
Silent Mode 17
installation requirements
software requirements 5
supported platforms 5
system memory requirements 5
installation steps 13
installation type
custom 2
typical 2
installer account 3
installer log file 4

TIB Adadb 6.3.0 Installation

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

TIB Adadb 6.3.0 Installation

Hochgeladen von

Copyright:

Verfügbare Formate

TIBCO ActiveMatrix® Adapter

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

Chapter 2 Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

TIBCO ActiveMatrix Adapter for Database Installation

Chapter 3 Post-installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 4 Installation FAQs and Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

TIBCO ActiveMatrix Adapter for Database Installation

Figure 1 TIBCO Installation Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

TIBCO ActiveMatrix Adapter for Database Installation

TIBCO ActiveMatrix Adapter for Database Installation

Table 1 General Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

TIBCO ActiveMatrix Adapter for Database Installation

TIBCO ActiveMatrix Adapter for Database Installation

TIBCO ActiveMatrix Adapter for Database software is a bidirectional gateway between

• Changes from the Previous Release of this Guide, page x

TIBCO ActiveMatrix Adapter for Database Installation

Changes from the Previous Release of this Guide

Support for DataDirect 7.0 ODBC Drivers

Support for Using DataDirect Drivers to Connect to MySQL Database and

Support for PostgreSQL Database and Postgres Plus Advanced Server

Running the 32-bit Adapter on 64-bit TIBCO Runtime Agent

TIBCO ActiveMatrix Adapter for Database Installation

This section lists documentation resources you may find useful.

TIBCO ActiveMatrix Adapter for Database Documentation

Other TIBCO Product Documentation

TIBCO ActiveMatrix Adapter for Database Installation

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

TIBCO ActiveMatrix Adapter for Database Installation

Table 1 General Typographical Conventions (Cont’d)

TIBCO ActiveMatrix Adapter for Database Installation

Connecting with TIBCO Resources

How to Join TIBCOmmunity

How to Access TIBCO Documentation

How to Contact TIBCO Support

TIBCO ActiveMatrix Adapter for Database Installation

Chapter 1 Installation Introduction

• Installation Overview, page 2

TIBCO ActiveMatrix Adapter for Database Installation

This section gives an overview of the installer.

TIBCO ActiveMatrix Adapter for Database Installation

Installing on Microsoft Windows 2003 Terminal Server

Change back to Execute mode after installation is complete by typing:

To check your current mode, type the following:

Installer Log File

TIBCO ActiveMatrix Adapter for Database Installation

TIBCO ActiveMatrix Adapter for Database Installation

System Memory Requirements

Table 2 Software Requirements

TIBCO ActiveMatrix Adapter for Database Installation

Table 2 Software Requirements (Cont’d)

TIBCO ActiveMatrix Adapter for Database Installation

Table 3 describes the components of the adapter installation package.

Table 3 TIBCO Adapter Components

Documentation This component is required for context sensitive help.

TIBCO ActiveMatrix Adapter for Database Installation

Supported Databases and Drivers

Connecting to Remote Databases

TIBCO ActiveMatrix Adapter for Database cannot be installed on an z/OS or iSeries

ODBC Driver Documentation

Table 4 ODBC Driver Supported Platform

Adapter Supported Operating Systems

TIBCO ActiveMatrix Adapter for Database Installation

Table 4 ODBC Driver Supported Platform