TIBCO Silver Fabric Enabler for Adapter for Database Users ... · TIBCO Silver ® Fabric Enabler...

Two-Second Adv

TIBCO Silver® Fabric Enabler for Adapter for Database

User’s GuideSoftware Release 2.0February 2013

antage®

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, Two-Second Advantage, TIBCO Silver, TIBCO Silver Fabric, TIBCO ActiveMatrix Adapter for Database, TBICO ActiveMatrix BusinessWorks, TIBCO Rendezvous, TIBCO Administrator, TIBCO Enterprise Message Service, TIBCO InConcert, TIBCO Policy Manager, TIBCO Runtime Agent, and TIBCO Hawk are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.Copyright © 2011-2013 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xTIBCO Silver Fabric Enabler for Adapter for Database Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xOther TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiiiHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiiiHow to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiiiHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii

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

Product Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Main Functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2 Creating a TIBCO Silver Fabric Enabler for Adapter for Database Stack . . . . . . . . . .5

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Creating a TIBCO Administrator Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Creating TIBCO Silver Fabric Enabler for Adapter for Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Creating a TIBCO Silver Fabric Enabler for Adapter for Database Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Dependency Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Adapter for Database Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Running TIBCO Silver Fabric Enabler for Adapter for Database Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Updating TIBCO Silver Fabric Enabler for Adapter for Database Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 3 Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Adapter for Database Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Retained Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

TIBCO Silver® Fabric Enabler for Adapter for Database User’s Guide

iv |

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61


| v

Figures

Figure 1 TIBCO Silver Fabric Enabler for Adapter for Database Components . . . . . . . . . . . . . . . . . . . . . . . . 3

Figure 2 Creating a TIBCO Administrator Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Figure 3 Configuring General Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Figure 4 Choosing TIBCO Product Distribution Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Figure 5 Editing TIBCO Administrator Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Figure 6 TIBCO Administrator LDAP Configuration using UI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Figure 7 LDAP Configuration using an XML File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Figure 8 Configuring an independent TIBCO EMS Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Figure 9 TIBCO Rendezvous® and TIBCO Hawk® Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Figure 10 HTTP Base Port settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Figure 11 TIBCO Administrator Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Figure 12 HTTPS Configuration using a Self-Signed Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Figure 13 HTTPS Configuration with a CA-Signed Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Figure 14 LDAP Configuration using UI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Figure 15 LDAP Configuration using an XML File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Figure 16 TIBCO Administrator and Hawk Agent Running Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Figure 17 Editing a Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Figure 18 Name and Describe the Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Figure 19 Choose TIBCO Product Distribution Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Figure 20 Upload a JDBC Driver for TIBCO Domain Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Figure 21 Configure the TIBCO Domain Machine Name (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Figure 22 Uploading Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Figure 23 TIBCO Administrator and Hawk Agent Running Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Figure 24 Upload, Add, Customize, or Remove Content Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Figure 25 Customize a selected text file using the simple text editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Figure 26 Editing a Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Figure 27 Add or remove Adapter for Databse Component Runtime Statistics . . . . . . . . . . . . . . . . . . . . . . . . 42

Figure 28 Edit the Configuration File page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44


vi |

Figure 29 Creating a Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Figure 30 Stack Builder Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Figure 31 Setting Administrator Component Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Figure 32 Creating Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Figure 33 Statistics available with the Silver Fabric Enabler for Adapter for Database Component . . . . . . . . 52

Figure 34 Running a Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Figure 35 Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58


| vii

Tables

Table 1 General Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Table 2 Retained TIBCO Hawk® Agent Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Table 3 Retained TIBCO Administrator Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Table 4 Retained TIBCO Adapter for Database Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60


viii |


| ix

Preface

Topics

• Related Documentation, page x

• Typographical Conventions, page xi

• Connecting with TIBCO Resources, page xiii


x |

Related Documentation

This section lists documentation resources you may find useful.

TIBCO Silver Fabric Enabler for Adapter for Database DocumentationThe following documents form the TIBCO Silver Fabric Enabler for Adapter for Database documentation set:

• TIBCO Silver® Fabric Enabler for Adapter for Database Installation Read this manual for instructions on site preparation and installation.

• TIBCO Silver® Fabric Enabler for Adapter for Database User’s Guide Read this manual for instructions on using the product.

• TIBCO Silver® Fabric Enabler for Adapter for Database Release Notes Read the release notes for a list of new and changed features. This document also contains lists of known issues and closed issues for this release.

Other TIBCO Product DocumentationTIBCO Silver Fabric Enabler for Adapter for Database empowers TIBCO Silver® Fabric private cloud infrastructure to run TIBCO Adapter for Database.

You may find it useful to read documentation related to the following TIBCO products:

• TIBCO Silver® Fabric

• TIBCO ActiveMatrix® Adapter for Database

• TIBCO Designer™

• TIBCO Administrator™

• TIBCO Rendezvous®

• TIBCO Hawk®

• TIBCO Runtime Agent™

• TIBCO Enterprise Message Service™


| xi

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME

ENV_HOME

SFDB_HOME

SILVERFABRIC_HOME

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

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

TIBCO Silver Fabric Enabler for Adapter for Database is installed into a directory that is referenced in documentation as SFDB_HOME. The value of SFDB_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco\sfdb

TIBCO Silver Fabric is installed into a directory that is referenced in documentation as SILVERFABRIC_HOME. The value of SILVERFABRIC_HOME depends on the operating system. For example, on Windows systems, the default value can be C:\fabric.

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]


xii |

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO Adapter for Database 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.

Table 1 General Typographical Conventions (Continued)

Convention Use


| xiii

Connecting with TIBCO Resources

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

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

http://docs.tibco.com

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, please 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

Access to this site is restricted to designated customer contacts, but you can request a user login when you have a valid maintenance or support contract.


http://www.tibcommunity.com

http://docs.tibco.com

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

https://support.tibco.com

xiv |


| 1

Chapter 1 Introduction

This chapter briefly introduces this product.

Topics

• Product Overview, page 2

• Main Functionalities, page 2

• Components, page 3


2 |

Product Overview

TIBCO Silver® Fabric Enabler for Adapter for Database is a complementary software component. It allows TIBCO ActiveMatrix® Adapter for Database projects to be published in cloud environments based on TIBCO Silver® Fabric and leverage Silver® Fabric capabilities. This accelerates publishing of Adapter for Database projects, enforces its industry best practices, and provides elastic optimization of computing resources.

Main FunctionalitiesTIBCO Silver Fabric Enabler for Adapter for Database provides the following main functionality:

• It enables you to quickly set up an environment on multiple machines. A TIBCO administrator can then publish Adapter for Database projects onto this environment using traditional tools, such as the TIBCO Administrator User Interface or its command-line tools.

• It enables you to quickly define, set up, and publish a complete application based on Adapter for Database projects onto a set of virtual or physical machines. These actions include installation of this software, creation of TIBCO Domain, starting up TIBCO Administrator Server, and publishing of the Adapter for Database projects on one or multiple machines.

• It ensures that all publishing follows a set of recommended and supported TIBCO practices to implement fault tolerance, load balancing, software updates, and application updates.

• It collects Adapter for Database metrics from Adapter for Database engines to be used in TIBCO Silver® Fabric rules. It scales up and down the number of Adapter for Database engines required to process the workload. Therefore, it provides elasticity and optimization of computing resources.

• Enables creation of a pool of TIBCO Domain Machines (TLM) for scaling up and scaling down TIBCO Silver Fabric Enabler for Adapter for Database Engines, Component Archives, and Adapters.

• Gathers and reports statistics from each TIBCO Silver Fabric Enabler for Adapter for Database service instance published by TIBCO Silver® Fabric to support automated rule-based scaling from archive statistics.

• Supports TLM restart for engines from shared drives. Planned TLM restarts are streamlined so that large numbers of applications with multiple archives each can be restarted more quickly.


| 3

ComponentsTIBCO Silver Fabric Enabler for Adapter for Database consists of the following components, as shown in Figure 1, TIBCO Silver Fabric Enabler for Adapter for Database Components:

• TIBCO Administrator Container

It is used to configure, start, and manage one or more TIBCO Domains.

• TIBCO Adapter for Database Container

It is used to configure, start, and manage Adapter for Database engines.

• A set of distributions that includes all the software pieces required to run a Adapter for Database environment: TIBCO Runtime Agent, TIBCO Administrator, TIBCO Rendezvous®, TIBCO Hawk®, and TIBCO Adapter for Database.

Figure 1 TIBCO Silver Fabric Enabler for Adapter for Database Components


4 |


| 5

Chapter 2 Creating a TIBCO Silver Fabric Enabler for Adapter for Database Stack

This chapter explains how to configure and publish TIBCO Silver Fabric Enabler for Adapter for Database Stack.

Topics

• Overview, page 6

• Creating a TIBCO Administrator Component, page 7

• Creating TIBCO Silver Fabric Enabler for Adapter for Database Components, page 31

• Running TIBCO Silver Fabric Enabler for Adapter for Database Stack, page 53

• Dependency Requirements, page 48

• Adapter for Database Statistics, page 50

• Running TIBCO Silver Fabric Enabler for Adapter for Database Stack, page 53

• Updating TIBCO Silver Fabric Enabler for Adapter for Database Stack, page 54


6 |

Overview

TIBCO Silver Fabric Enabler for Adapter for Database is an entity that runs inside TIBCO Silver® Fabric. It facilitates component configuration and executes all the components necessary for publishing the Adapter for Database platform and to publish Adapter for Database projects.

A TIBCO Silver Fabric Enabler for Adapter for Database Stack consists of a TIBCO Administrator component, and one or more Adapter for Database Components.

To build and run a TIBCO Silver Fabric Enabler for Adapter for Database Stack, you need to perform the following tasks:

• Create and publish one TIBCO Administrator component. Refer to Creating a TIBCO Administrator Component on page 7

• Create and publish one or more Adapter for Database Components. Refer to Creating TIBCO Silver Fabric Enabler for Adapter for Database Components on page 31.

• Create a TIBCO Silver Fabric Enabler for Adapter for Database Stack. Refer to Creating a TIBCO Silver Fabric Enabler for Adapter for Database Stack on page 46.

• Set a dependency to the TIBCO Administrator Component for each Adapter for Database Components. Refer to Dependency Requirements on page 48.

• Optionally set rules for TIBCO Silver® Fabric Engines. Refer to Adapter for Database Statistics on page 50.

After completing these tasks, you can run and update a TIBCO Silver Fabric Enabler for Adapter for Database Stack. See page 53 for information on how to run and update a Stack.


| 7

Creating a TIBCO Administrator Component

This Component will create a TIBCO Domain, and start TIBCO Hawk® services and a TIBCO Administrator server.

To create and configure a TIBCO Administrator component, perform the following tasks:

• Task A, Create a TIBCO Administrator Component, page 8

• Task B, Configure TIBCO Domain Values, page 11

• Task C, Configure TIBCO EMS Connection Configuration, page 17

• Task D, Configure TIBCO Rendezvous® and TIBCO Hawk® Connections, page 18

• Task E, Set the HTTP Base Ports, on page 20

• Task F, Configure the TIBCO Administrator Database, page 21

• Task G, Configure HTTPS using a Self-Signed Certificate (optional), on page 24

• Task H, Configure HTTPS with a CA Certificate (optional), on page 25

• Task I, Configure TIBCO Administrator LDAP using either UI or XML, on page 27

• Task J, Configure Running Conditions, on page 29

• Task K, Add or Edit Container-specific Runtime Context Variables, on page 30

• Task L, Finish Configuring the Component, page 30

After you complete these tasks, the TIBCO Administrator component should be published with the following URL:http://SilverFabricBroker:BrokerPort/TIBCO_DOMAIN_NAME/administrator/servlet/tibco_administrator

This will automatically redirect to the machine where TIBCO Administrator is running with the port calculated using the base port set in Task E, Set the HTTP Base Ports, on page 20.


8 |

Task A Create a TIBCO Administrator Component

1. In TIBCO Silver® Fabric Administration Tool - select Stacks > Components.

2. In the Components page, select Create New TIBCO Administrator Component from the Global Actions menu list:

Figure 2 Creating a TIBCO Administrator Component


| 9

3. [Optional] When two or more container versions are installed, then the "Create New TIBCO Administrator Component" will be displayed so you can select the Enabler you want to use. Click OK to proceed.

4. Provide a name for the Component and select the version of the Container you want this Component to run.

Figure 3 Configuring General Properties

5. Choose the TIBCO product distribution versions where the Component to run as shown in Figure 4.

Select a version of each of the installed distributions. It is generally a good practice to use the latest version of a product distribution. Refer to the TIBCO Silver Fabric Enabler for Adapter for Database Readme for more information on supported distributions. The product versions which are displayed are compatible with the component being defined.

Figure 4 Choosing TIBCO Product Distribution Versions


10 |

6. Click the Next button after selecting the TIBCO product distribution versions and the TIBCO Administrator Basic Configuration panel is displayed as is shown in Task B, Configure TIBCO Domain Values, on page 11.


| 11

Task B Configure TIBCO Domain Values

The TIBCO Administrator Basic Configuration page and each of the configuration parameters are described here. Enter appropriate values for each field as applicable.

Figure 5 Editing TIBCO Administrator Basic Configuration

• Administrator Domain

Choose a name that clearly identifies the Administrator Domain. The Administrator Domain value will also be the name of the server itself.

If an Administrator Server is already running in the sub net, you cannot use that name for a second server with the same TIBCO Rendezvous® parameters. Don’t re-use the name of a Network Domain.

Domain name length must be less than 64 characters. Alphanumeric characters, hyphens (-) and underscores (_) are accepted, but other characters including periods and commas are not allowed.


12 |

• User Name - Password

Values entered here will create a new TIBCO Administrator profile.

Alphanumeric characters, hyphens (-), and underscores (_) are allowed. The password is not case-sensitive and can’t start with ! or !#.

The default value is admin. It is strongly recommended that you change it.

• Domain Encoding

The character set selected is used for all communication between the administration server and its clients, servers in the administration domain.

The default domain encoding is ISO8859-1 (Latin-1). Choose the character encoding most appropriate for your implementation.

• Enable HTTPS

Choose either Disabled, Self_Signed_Certificate, or CA_Signed_Certificate.

When disabled TIBCO Administrator uses HTTP for messaging.

When either of the other two options are selected HTTPS will be enabled for messaging between components and another configuration page is added to this Component Wizard so that configurations can be set to use the Certificate Authority (CA) issued certificate or the self-signed certificate.

The configuration panels for the Self_Signed_Certificate, or CA_Signed_Certificate options are described here: Configure HTTPS using a Self-Signed Certificate (optional) on page 24 and here: Configure HTTPS with a CA Certificate (optional) on page 25.

• Enable LDAP

Choose either Disabled, UI, or XML. UI and XML settings enable LDAP configuration with settings made with either a graphical user interface or an uploaded XML settings file. An LDAP configuration page is added to the Component Wizard when UI or XML are selected.

When LDAP is enabled with the UI option, the LDAP Configuration Using User Interface page is added to the wizard for setting basic LDAP properties. the configuration wizard page that appears later is pictured here to help you evaluate whether the LDAP configuration using the UI will be adequate for your environment implementation.

For more information on LDAP configuration properties refer to the section: Configure TIBCO Administrator LDAP using either UI or XML on page 27

TIBCO Administrator Enabler transport using TIBCO EMS does not yet support SSL.


| 13

Figure 6 TIBCO Administrator LDAP Configuration using UI

If your implemented LDAP environment is more complex and requires configuration settings that are not exposed by this UI, then you should use an XML settings file to configure LDAP for the component. You can set all of the LDAP parameters in an XML file and upload it.

Figure 7 LDAP Configuration using an XML File

For more information on "Creating a Domain that integrates with an LDAP Directory Server" refer to the section of the same name in the TIBCO Runtime Agent™ Domain Utility User’s Guide.


14 |

For more information on configuration of LDAP for use with SSL connections refer to the TIBCO Runtime Agent™ Domain Utility User’s Guide section on "Configuring LDAP Integration With SSL Connections."

• Store Domain Information in a Database

This checkbox allows you to switch from storing domain data in files (unchecked) or in a database (checked). When you check this box the TIBCO Administrator Database Configuration page is added to this wizard.

When the TIBCO Administrator is configured to use a database for domain storage then a larger number of applications can be published.

The following three parameters are not used and ignored in the LDAP XML.<DomainName>ldap_domain</DomainName>

<AdministratorUsername>a</AdministratorUsername>

<AdministratorPassword>a</AdministratorPassword>


| 15

• Use EMS as Transport

TIBCO Administrator messaging can be configured to use either the TIBCO Enterprise Message Service™ (TIBCO EMS) or TIBCO Rendezvous®.

This check box defines whether the TIBCO Administrator will use TIBCO EMS (checked) or TIBCO Rendezvous® (unchecked). A messaging configuration specific page is added to the wizard depending on this check box setting. For more information on the configuration of the Component to use the specific messaging platform chosen. Refer to the description on the applicable page: TIBCO EMS Connection Configuration or TIBCO Rendezvous® Configuration.

For more information on these settings refer to the TIBCO Rendezvous documentation.

• Use Dependent EMS Server

When you check this checkbox and publish a dependent TIBCO Silver® Fabric Enabler for TIBCO EMS Server, the connection and configuration settings will be set automatically and the TIBCO EMS Connection Configuration page will not be displayed.

Check the box to "Use EMS as Transport" if TIBCO EMS is to be used as a dependent application. When this setting is used, you must also make the TIBCO Silver® Fabric Enabler for TIBCO EMS Component a dependent application of the TIBCO Administrator Component in the Stack setting.

If the Component messaging will be independent of the TIBCO Administrator publishing, then leave this check box unchecked and enter connection settings values on the TIBCO EMS Connection Configuration page.

If TIBCO EMS is used for the transport messaging then a database will be required to store domain information. Check the box to "Store Domain Information in a Database" if TIBCO EMS is to be used.

If TIBCO Rendezvous is used for the transport of TIBCO Administrator Domain traffic you must do one of the following to ensure proper communication:

— Use the same sub-net for all Silver Fabric engine host machines used to run TIBCO Domains, or...

— Enable TIBCO Rendezvous Multicast with a TTL setting so that the TIBCO Rendezvous Daemon (RVD) can multicast packets across specified subnets, or...

— Set up a TIBCO Rendezvous Routing Daemon (RVRD) to bridge RVD traffic across the relevant subnets.


16 |

• Fault Tolerance (FT) Mode

This checkbox specifies whether TIBCO Administrator (hosted on a TIBCO Silver Fabric Engine) will run in Fault Tolerance mode. Fault tolerance mode provides for system resilience because hardware and network failures occur. Using the Fault Tolerance mode is strongly recommended.

When FT mode is enabled (checked), if a TIBCO Silver® Fabric Engine stops responding for whatever reason, then a new TIBCO Administrator instance will be restarted using the existing domain data on the next available TIBCO Silver Fabric Engine.

If FT mode is not enabled (default is unchecked) and the TIBCO Silver® Fabric Engine suspends for whatever reason, then TIBCO Administrator will restart on another available Silver® Fabric Engine and re-create a new TIBCO Domain without the existing domain data information. When Fault Tolerance is not enabled, restart of the TIBCO Administrator even with a database domain does not synchronize the domain information from the previous instance. In other words, the existing domain data would not be available to the new instance.

Admin Root Path for FT

Fault Tolerance (FT) requires connection with a shared drive path used to store the Domain configuration data. The Admin Root Path for FT value specifies the path for that shared drive path.

The Admin Root Path must be a valid path across all the machines where the TIBCO Administrator will run. For example on a Unix/Linux based platforms:

/ShareDrive/TIBCODomain/MyDomainName

If FT mode is disabled (unchecked) the Admin Root Path value does not apply.

Use the Next button to proceed with your Component configuration. Changes are saved when you click the Finish button.

FT mode requires that allocated TIBCO Administrators use the same shared drive available to all Engines. FT mode is not fully compatible with Windows operating systems because Windows services don’t have access to shared drives. It is strongly recommended that implementations requiring FT mode target operating systems other than Windows based resources. This can be accomplished by defining a Resource Preference - Allocation Rule to specify the OS Platform as equal to a preferred operating system. If Windows platforms must be used then the Silver Fabric Engines can be run as applications by the desktop user so that the Silver Fabric Engine and child processes can use mapped drives.


| 17

Task C Configure TIBCO EMS Connection Configuration

If your TIBCO Administrator Component is configured to use independent EMS as a transport, then the Configure TIBCO EMS Connection Configuration page will be displayed to allow entry of the URL, port, and login profile.

Figure 8 Configuring an independent TIBCO EMS Connection

• EMS Server URL

The URL of the TIBCO Enterprise Message Service™ server is in the following format: tcp://hostname:port

Multiple Enterprise Message Service™ servers may be configured for use by the Administrator Component for fault-tolerance by specifying all of them here. Enter multiple EMS Server URL by separating them with a comma between entries. For example:

tcp://host1:7222,tcp://host2:7222

• EMS User Name and Password

This is the EMS user profile (username and password) used to connect to the EMS Server. If multiple EMS are set up for fault tolerance they must all be able to use the same user profile for creating a connection between the Administrator Component and the Enterprise Message Service™.

When TIBCO EMS is used a transport, the TIBCO Administrator Domain information must be stored using a Database.

TIBCO Administrator transport using TIBCO EMS does not yet support SSL.


18 |

Task D Configure TIBCO Rendezvous® and TIBCO Hawk® Connections

TIBCO Rendezvous® (RV) is used as the transport when your implementation does not use EMS as a transport (TIBCO Administrator Basic Configuration page > Use EMS as transport is unchecked). The TIBCO Rendezvous Configuration page provides an interface for configuration of Rendezvous and TIBCO Hawk.

• RV Daemon (required)

Specify the protocol and port for client server communication between the TIBCO Administrator Component and the TIBCO Rendezvous® daemon. The default value is tcp:7500

Figure 9 TIBCO Rendezvous® and TIBCO Hawk® Configuration

Using a remote TIBCO Rendezvous® Daemon

Using a remote TIBCO Rendezvous® daemon is not recommended.

When you are using a remote daemon, there is only one Rendezvous® daemon running for the entire Application (TIBCO Domain). TIBCO Administrator and Adapter for Database are using the same daemon running on the TIBCO Administrator machine. If the machine where the remote daemon is running suspends due to a network problem or other reasons, then your entire system will also suspend.


| 19

In the following conditions, you can use a remote daemon:

— Your working environment has no UDP network protocol.

— All your machines are part of the TIBCO Silver® Fabric Cloud in different networks, but there are no TIBCO Rendezvous® daemons between the networks.

To use a remote TIBCO Rendezvous® Router Daemon, set the RV Daemon value to:

tcp:ADMINMACHINE:port_number

The placeholder value, ADMINMACHINE, will be automatically replaced during runtime by the value of the machine name or IP address where TIBCO Administrator is running.

For example you can set the value to tcp:ADMINMACHINE:7500. This will start TIBCO Rendezvous® on the TIBCO Administrator machine. All machines that join this TIBCO Domain will use this remote daemon.

• RV Network

This specifies the TIBCO Rendezvous® network used for client-server communication. This variable only needs only to be set on computers with more than one network interface. If specified, the TIBCO Rendezvous® daemon uses that network for all outbound messages.

• RV Service (required)

This specifies the TIBCO Rendezvous® Service used for client-server communication. The Rendezvous® daemon divides the network into logical partitions. Each transport communicates on a single service. A transport can communicate only on the same service with other transports.

The default TIBCO Rendezvous port setting is 7500. Unless you are using a non-default TIBCO Rendezvous® configuration, you need to use the default value: 7500.

• Hawk Daemon (required)

This specifies TIBCO Rendezvous® Daemon used for communication with TIBCO Hawk®. The default value is tcp:7474

Like the RV Daemon, if you need to use a remote daemon, you can set the value to tcp:ADMINMACHINE:port_number, for example, tcp:ADMINMACHINE:7474.

• Hawk Network

This specifies the TIBCO Rendezvous® network used for communication with TIBCO Hawk®. Use the default value unless you are an experienced TIBCO


20 |

Rendezvous® user. See TIBCO Hawk® Installation and Configuration for details about this parameter.

• Hawk Service (required)

This specifies the TIBCO Rendezvous® service used for communication with TIBCO Hawk®. Use the default unless you are an experienced TIBCO Rendezvous® user. The default value is 7474. See TIBCO Hawk® Installation and Configuration for details about this parameter.

Task E Set the HTTP Base Ports

The TIBCO Administrator Server Port Configuration sets the HTTP Base Port.

When HTTPS is enabled by the setting on the Basic Configuration page this configuration page is not shown and instead an HTTPS configuration page for the type of server certificate selected is shown though it affects the same set of Adapter for Database process starters.

• HTTP Base Port

In order to avoid HTTP port conflicts for TIBCO Administrator when more than one TIBCO Administrator servers are running on the same machine, TIBCO Silver Fabric Enabler for Adapter for Database automatically sets the port to the following value:

HTTP Base Port + EngineInstanceValue

The EngineInstanceValue is the Engine number of the TIBCO Administrator.

For example, on a dual core machine, the default number of Engines is 2 (one per core). The first Engine has the number 0, the second one has the number 1.

As an example if you set the HTTP Base Port to 8483, the HTTP ports used by TIBCO Administrator would be 8483 and 8484 for the first and second engines respectively.

Figure 10 HTTP Base Port settings


| 21

• HTTP Shutdown Base Port

In order to avoid shutdown port conflicts for TIBCO Administrator when many TIBCO Administrator servers stop working on the same machine, TIBCO Silver Fabric Enabler for Adapter for Database automatically sets the shutdown port to the following value:

HTTP Shutdown Base Port + EngineInstanceValue

The value is calculated in the same way as the TIBCO Administrator HTTP Base Port described previously.

Task F Configure the TIBCO Administrator Database

The TIBCO Administrator Database Configuration allows for specification of the JDBC Driver, Database URL, user login, connection pool size min and max sizes. This screen is made available when the checkbox for "Store Domain information in a Database" is checked on the TIBCO Administrator Basic Configuration page otherwise it will not be displayed by the wizard.

Figure 11 TIBCO Administrator Database Configuration

• JDBC Driver (required)

Specify the JDBC driver to be used by the TIBCO Administrator.

One of the following native drivers may be used:— Oracle Thin: oracle.jdbc.driver.OracleDriver

— MSSQL Server: com.microsoft.sqlserver.jdbc.SQLServerDriver


22 |

Refer to the TIBCO Runtime Agent™ documentation for information on supported TIBCO Administrator Domain databases.

If this field is specified, TIBCO Domain will be stored in a database.

• Database URL (required)

This Database URL provides the connection information to your database.

Enter the Database URL for your specific implementation.

— Oracle Thin: jdbc:oracle:thin:@host:port:SID

— MSSQL Server:

jdbc:sqlserver://host:port;databaseName=databaseName

• User Name (required) and Password (required)

Use a database administrative user profile that allows for table creation/deletion, as well as read, write, update, and deletion of data.

• Minimum JDBC Connection Pool Size

When your Application starts up, it initializes this number of connections to the database. For optimal performance, this number should be equal to the number of subscribers that you expect to connect to the database at any time.

When you specify the minimum connections, keep the following in mind:

— At startup, each instance opens its specified number of connections.

— Setting higher number of connections are better for Application instances, but may have adverse results for the rest of the system.

— The correct setting is whatever the complete system can handle on a sustained basis without taxing other system resources.

When TIBCO Domain is stored in a database, you must upload the JDBC driver so that it can be published with the TIBCO Administrator and Adapter for Database Components.

The JDBC drivers jars must use their standard, generic file names for proper loading as is listed here below:

— Oracle 11 driver: ojdbc6.jar

— Oracle 10 driver: ojdbc14.jar

— MS SQL driver: sqljdbc4.jar

Use the Upload button in the "Upload a JDBC driver..." field below for this.


| 23

• Maximum JDBC Connection Pool Size

The number of simultaneous connections cannot exceed the number set in this field. The database must be able to simultaneously handle the total maximum number of connections for all instances.

Make sure that you set Maximum JDBC Connection Pool Size to a number greater than the number for Minimum JDBC Connection Pool Size otherwise you will get an error message.

• Upload a JDBC Driver for this Database

If you use a database as the domain storage, you must upload a JDBC driver that matches the database type specified in the JDBC Driver field.


24 |

Task G Configure HTTPS using a Self-Signed Certificate (optional)

When Enable HTTPS is set to Self-Signed Certificate on the Basic Configuration page, then the TIBCO Administrator HTTPS Configuration Self-Signed Certificate page is displayed to provide an interface for configuring TIBCO Administrator to use your certificate.

When you are generating your own certificate you will have to note the parameter values you used to create it, so the TIBCO Administrator will have the proper values to use the certificate.

Figure 12 HTTPS Configuration using a Self-Signed Certificate

• HTTPS Base Port (required)

This setting helps the system avoid HTTPS port conflicts for the TIBCO Administrator when more than one TIBCO Administrator servers are running on the same machine. TIBCO Silver Fabric Enabler for Adapter for Databasesets the port to the following value:

HTTPS Base Port(value) + EngineInstanceValue

The EngineInstanceValue is the Engine number where TIBCO Administrator will run.


| 25


If for example you set the HTTPS Base Port to 8483, the HTTPS ports used by TIBCO Administrator would be 8483 and 8484 for the first and second engines respectively.

• HTTPS Shutdown Base Port

To avoid shutdown port conflicts for TIBCO Administrator, TIBCO Silver Fabric Enabler for Adapter for Database automatically sets the shutdown port to the following value:

HTTPS Shutdown Base Port + EngineInstanceValue

• Keystore Password

Enter your unique alpha-numeric string.

• Self-Signed Certification - Server Contact Information

Enter your Email Address, Common Name (CN), Organizational Unit (OU), Organization (O), City/Locality, State (required), Country Code (two letters), and Validity. These values are required.

Task H Configure HTTPS with a CA Certificate (optional)

This configuration page appears only when the HTTPS Enabled field on the Basic Configuration page is set to CA_Signed_Certificate.

Figure 13 HTTPS Configuration with a CA-Signed Certificate


26 |

• HTTPS Base Port (required)

This setting helps the system avoid HTTPS port conflicts for the TIBCO Administrator when more than one TIBCO Administrator servers are running on the same machine. TIBCO Silver Fabric Enabler for Adapter for Database sets the port to the following value:

HTTPS Base Port(value) + EngineInstanceValue

The EngineInstanceValue is the Engine number where TIBCO Administrator will run.


For example if you set the HTTPS Base Port to 8483, the HTTPS ports used by TIBCO Administrator would be 8483 and 8484 for the first and second engines respectively.

• HTTPS Shutdown Base Port

To avoid shutdown port conflicts for TIBCO Administrator, TIBCO Silver Fabric Enabler for Adapter for Database automatically sets the shutdown port to the following value:

HTTPS Shutdown Base Port + EngineInstanceValue

• Keystore Password

Enter your unique alpha-numeric string.

• Server Certificate

Upload the server Certificate returned from the third-party Certificate Authority using the Upload button to browse for the proper file.

• CA Certificate (optional)

The CA chain certificate is optional. Use the Upload button to browse for the proper file.

• key.p8

Because this process uses an already existing certificate; you don’t need to go through the step of generating a CSR for each component server, the certificate must be in PEM (Privacy Enhanced Mail) format and a private key (in the PKCS#8 format) is required. The name of the private key file must be "key.p8". Use the Upload button to browse for the proper file.


| 27

Task I Configure TIBCO Administrator LDAP using either UI or XML

When Enable LDAP is set to UI on the Basic Configuration page, then the TIBCO Administrator LDAP Configuration Using User Interface page is added to the Component Configuration Wizard for setting basic LDAP properties.

Enter appropriate LDAP values for your environment.

Figure 14 LDAP Configuration using UI

Refer to your LDAP implementation for details on how to connect with it.

If your implemented LDAP environment is more complex and requires configuration settings that are not exposed by this UI, then you should use an XML settings file to configure LDAP for the component. If this is the case use the Menu button to go back the TIBCO Administrator Basic Configuration page and set LDAP Enabled to "xml".

You can set all of the LDAP parameters in an XML file and upload it.


28 |

A template to help with correctly specifying the LDAP parameters in an XML file is located in the TIBCO Runtime Agent directory:

TIBCO_HOME/tra/version/template/domainutility/cmdline/

ModifyLDAPConfiguration.xml

Copy this file, make your modifications, and after choosing the Enable LDAP XML option, the Component Wizard displays a page for uploading the file.

Figure 15 LDAP Configuration using an XML File

For more information on "Creating a Domain that integrates with an LDAP Directory Server" refer to the section with that same name in the TIBCO Runtime Agent™ Domain Utility User’s Guide.

To configure LDAP for use with SSL connections refer to the TIBCO Runtime Agent™ Domain Utility User’s Guide section on "Configuring LDAP Integration With SSL Connections."

The following three LDAP XML parameters are not used and ignored.<DomainName>ldap_domain</DomainName>

<AdministratorUsername>a</AdministratorUsername>

<AdministratorPassword>a</AdministratorPassword>


| 29

Task J Configure Running Conditions

• Polling Period for detection of TIBCO Administrator or Hawk Agent not running (required)

Verification that TIBCO Administrator and TIBCO Hawk Agent are still running is tested frequently based upon a configurable interval period. Enter an integer to specify the number of seconds between checks. If either TIBCO Administrator or TIBCO Hawk Agent become unresponsive to this verification the process it is automatically restarted.

Figure 16 TIBCO Administrator and Hawk Agent Running Conditions

• Automatically Restart Silver Fabric Engine if TIBCO Administrator fails to restart N successive times (required)

Enter an integer to specify the number of restart retries for the TIBCO Administrator before the TIBCO Silver Fabric Engine Container will be restarted. A successful restart will reset the count.

• Automatically Restart Silver Fabric Engine if TIBCO Hawk Agent fails to restart N successive times (required)

Enter an integer to specify the number of restart retries for the TIBCO Hawk Agent before the TIBCO Silver Fabric Engine Container will be restarted. A successful restart will reset the count.


30 |

Task K Add or Edit Container-specific Runtime Context Variables

Container-specific runtime context variables may be added to the Administrator Component. Add String, Environment, System, or Encrypted variables by first selecting a variable type from the Add Variable selector if you wish to add or edit a variable.

Figure 17 Editing a Variable

Variables from the container may be changed as well. Use the Add from Container button to change the values of container-specific context variables.

Task L Finish Configuring the Component

The remaining screens of the Component Wizard are generic for all Silver® Fabric Containers. The configuration of these is optional for TIBCO Administrator component.

Refer to TIBCO Silver® Fabric User’s Guide for more information on these configuration screens.

After you click the Finish button, make sure that the Component is published to make it available to create an Application.

To do this, select Publish Unpublished Components in the Actions drop-down list located at the line of the Component you just created.


| 31

Creating TIBCO Silver Fabric Enabler for Adapter for Database

Components

This Component will perform the following tasks:

• Add a virtual machine to TIBCO Domain.

• Start TIBCO Hawk® Agent.

• Publish one or more Adapter for Database projects. This task is optional.

If you do not upload the Adapter for Database projects, you still can publish the Adapter for Database projects on the machine where Adapter for Database registers to TIBCO Domain using the TIBCO Administrator GUI.

To configure the Adapter for Database Component, perform these tasks:

• Task A, Specify Component Name, page 32

• Task B, Select the Software Version, page 33

• Task C, Upload a JDBC Driver (optional), page 33

• Task D, Set the Domain Machine Name (optional), page 34

• Task E, Set the Fast TLM Restart shared drive, page 35

• Task F, Setup the ODBC connection parameters (optional), page 36

• Task G, Upload a Project, page 37

• Task H, Configure TIBCO Hawk Agent Running Condition, page 39

• Task I, Controlling Content Files, on page 39

• Task J, Add or Edit Runtime Context Variables (optional), page 41

• Task K, Add or Remove Adapter for Database Statistics, page 42

• Task L, Finish Configuring the Component, page 42


32 |

Task A Specify Component Name

1. Using the TIBCO Silver® Fabric Administration Tool, select Applications > Components.

2. On the Components page, select Create New TIBCO ActiveMatrix Adapters Component in the Global Actions list.

3. (Optional) If there are two or more versions of the Adapter for Database Container then an Enabler version select dialog will appear to allow you to select the container version you want to create. Make a selection and click OK.

4. Provide a name and description for the Component.

Figure 18 Name and Describe the Component


| 33

Task B Select the Software Version

You can select the version of the distribution you want TIBCO Adapter for Database to run, as shown in Figure 19.

You can select any version of the distributions installed in the Silver® Fabric Broker. By default, the latest versions of the distributions are displayed. All versions of the distributions are compatible.

Figure 19 Choose TIBCO Product Distribution Versions

Task C Upload a JDBC Driver (optional)

When the TIBCO Administrator instantiated on the TIBCO Silver Fabric Engine uses a database as the domain storage, you must upload a JDBC driver. The JDBC driver must match the database type defined in Task F, Configure the TIBCO Administrator Database, on page 21, which the TIBCO Administrator uses.

The procedure is the same as uploading a JDBC driver for TIBCO Administrator component.


34 |

Figure 20 Upload a JDBC Driver for TIBCO Domain Storage

Refer to Task F, Configure the TIBCO Administrator Database, on page 21 for the uploading steps.

Task D Set the Domain Machine Name (optional)

The TIBCO Domain Machine Name (also known as the TIBCO Logical Machine - TLM) provides for a singular publishing of a unique Component. The TIBCO Domain Machine is an optional feature that virtualizes the machine so that Component publishing can maintain state when the targeted engine is changed for whatever reason.

If for example, the target machine is restarted because of an OS update or a hardware change, TLM allows for the virtualized machine to be restarted on different hardware.

Each Adapter for Database Component has dependency on TIBCO Administrator. Refer to Dependency Requirements on page 48 to learn how to set the dependency.

When the TIBCO Domain Machine name is set, the Component .EAR (.JAR) files are republished and started on the new virtual machine hardware.

When Adapter for Database Applications have been previously published via TIBCO Administrator (or via the AppManage command line interface) those previous deployments will also be published again and restarted on the new hardware.


| 35

Figure 21 Configure the TIBCO Domain Machine Name (optional)

TIBCO Domain machine name - To activate use of the TIBCO Domain Machine Name enter a value in the TIBCO Domain machine name field. The TIBCO Domain machine name can use alphanumeric characters, hyphen (-), or underscore (_) characters. Other special characters, including period and comma, are not allowed. The name length must be less than 64 characters.

Use of a TIBCO Domain Machine name ensures that the Component is instantiated only one time. The Delete Application on shutdown option will have no effect for all service instances running on that machine.

TIBCO Services state after TLM restarted - Sets the desired services state when the TIBCO Logical Machine is restarted. When the TLM is restarted Adapter for Database service instances will be republished and either started or stopped.

The stopped services state setting may be convenient for developers who are testing machines with many services that don’t need to be started for every logical machine change.

Task E Set the Fast TLM Restart shared drive

Fast TIBCO Logical Machine Restart provides for accelerated restart of the Engine and redeploying of many archives within a reduced amount of time. Enhanced restart times are achieved by using a saved state stored on a shared Network File System drive instead of synchronizing with the domain repository. To set your expectations properly, "fast" does not mean instantaneous or even amazingly fast, but it is faster than if the archives were loaded from the domain repository.


36 |

The shared NFS directory drive for Fast TLM Restart requires the following:

— The shared drive must be READ/WRITE accessible to all engine daemons running as TIBCO Logical Machines in a TIBCO Silver Cloud.

— All TLM in a Stack must run the same OS.

— Domain configuration changes made in the period between the TLM stop and the TLM restart will not be captured.

Fast TLM Restart - To enable Fast TIBCO Logical Machine Restart simply enter the directory path of the shared NFS drive (on Windows servers - a mapped drive) and make sure that the host grants permissions allowing the user who launches the engines to read and write in that location.

Task F Setup the ODBC connection parameters (optional)

When your implementation will use TIBCO AMX Adapter for Database to gain access to data sources using ODBC, the ODBC initialization file and the ODBC driver must be readied before you run the Adapter for Database agent on TIBCO Silver Fabric.

Upload the ODBC.ini File

For TIBCO Silver Fabric Engines hosted on UNIX-based platforms, the runtime host machine will require an ODBC initialization file (odbc.ini) and the ODBC driver (either a native driver provided by the data base vendor or the DD driver) to configure the connection for your implementation. The odbc.ini file will define parameters like the ODBC DSN on the machine on which the adapter will be running. You must also set parameters like IANAAppCodePage to match your database encoding. Refer to TIBCO ActiveMatrix® Adapter for Database documentation for more information.

Install TIBCO ActiveMatrix® Adapter for Database to get easy access to the Data Direct driver for access to Oracle, Sybase, MSSQL, DB2, and MySQL data sources. For Teradata data sources use their native drivers.

TIBCO Silver Fabric Engines on Windows platforms will require that you upload the ODBC driver for your database and that you configure a DSN on that Engine host using the Windows (GUI)> Data Sources (ODBC) interface. Refer to the Windows documentation for configuration of the ODBC DSN.


| 37

Use the Upload button to select and upload that file for use by the Silver Fabric Broker. The odbc.ini will be published to the Silver Fabric Broker directory:

DSEngine_Home\work\Engine_Instance\fabric\odbc\odbc.ini

Task G Upload a Project

If you want TIBCO Silver Fabric Enabler for Adapter for Database Applications to publish and run one or more Adapter for Database projects, you need to upload one or more EAR files (or ZIP files) of these projects as follows:

1. Click the Add button in the Upload, Remove, or Reorder Archive Files panel, as shown in Figure 22.

Figure 22 Uploading Archives

2. Click the Browse button in the Upload A File panel to navigate to the EAR or ZIP file and click the OK button.

You can upload one of two types of archive files:

• EAR FileWhen you upload a Adapter for Database EAR file, the deployment uses the default value of the global variables set in TIBCO Designer.

• ZIP FileYou can create a ZIP file that contains an EAR file and optionally an XML properties file. The XML file can contain all the deployment configurations, deployment path name, global variables, and so on.

Alternatively the odbc.ini file may be placed in a shared location, but the user must define the runtime context variable: ODBC_SHARED_DIRECTORY setting the value to a valid shared directory accessible to the Silver Fabric Broker. When the odbc.ini is obtained from a valid share directory uploading the file using the interface is not necessary.

Refer to: Task J, Add or Edit Runtime Context Variables (optional), on page 41 for more information on setting the variable.


38 |

To create an XML properties file for the project follow these steps:

a. In TIBCO_HOME/tra/tra_version/bin, run the following command:AppManage –export –ear EarFile.ear -out DeploymentConfig.xml

b. Edit the file and set the value for the deployment.

c. Create a ZIP file with the file EarFile.ear and DeploymentConfig.xml.

For details about the creation of the DeploymentConfig.xml file, refer to the TIBCO Runtime Agent documentation, Scripting Deployment User’s Guide.

A CustomFolder.properties file put in the zip archive can specify the deployment path. For example create the CustomFolder.properties file with content "ApplicationFullPath=aaa/bbb/ccc".


| 39

Task H Configure TIBCO Hawk Agent Running Condition

• Polling Period (in seconds) for detection of TIBCO Hawk Agent running verification (required)

Enter an integer to specify the number of seconds between periodic verification checks that the TIBCO Hawk Agent is still running. If the TIBCO Hawk Agent becomes unresponsive to this verification then the process is automatically restarted.

Figure 23 TIBCO Administrator and Hawk Agent Running Conditions

• Automatically Restart Silver Fabric Engine if TIBCO Hawk Agent fails to restart N successive times (required)

Enter an integer to specify the number of restart retries for the TIBCO Hawk Agent before the TIBCO Silver Fabric Engine Container will be restarted. A successful restart will reset the count.

Task I Controlling Content Files

Content files may be uploaded, added from a container, edited with a simple text editor, or removed using the "Add/override/customize Container and Component-specific content files" page.


40 |

Figure 24 Upload, Add, Customize, or Remove Content Files.

Figure 25 Customize a selected text file using the simple text editor

To remove unwanted JAR files use the Menu button to display the list of Wizard configuration steps and select Add/Override/Customize Container and Component-specific content files. Relative paths to external jar files that were added, may be removed with that window.


| 41

Task J Add or Edit Runtime Context Variables (optional)

Variables may be added to define runtime specific context variables. String, Environment, System, or Encrypted variables may be added. Select a variable type from the Add Variable selector if you wish to add or edit a variable.

Figure 26 Editing a Variable

Variable values from the container may be changed as well. Use the Add from Container button to change values of container-specific context variables.


42 |

Task K Add or Remove Adapter for Database Statistics

You can see the list of Component runtime statistics that will be tracked during when the Adapter for Database Component is published and running. You can remove or later add back those statistics according to your implementation needs.

Figure 27 Add or remove Adapter for Databse Component Runtime Statistics

for more information on using these statistics for scaling refer to Adapter for Database Statistics on page 50

Task L Finish Configuring the Component

Almost all of the other screens are generic for TIBCO Silver® Fabric Containers.


| 43

These final configurations are optional for Adapter for Database Components. Refer to TIBCO Silver® Fabric User’s Guide for more information on these configuration screens.

Click the Finish button to save your changes and then you can publish the Component as part of an Application Stack.

To do this, select Publish Unpublished Components in the Actions list located at the line of the Component you just created.


44 |

One page that must be used only with extreme caution is the Edit the Configuration File page. It should not be used unless the configuration.xml is backed up and specific knowledge about the TIBCO Silver Fabric system is being applied. This interface is being exposed to allow for more advanced customizations and normally it should be left alone.

For more information refer to "The configure.xml File" section in the TIBCO Silver® Fabric Developer’s Guide.

Figure 28 Edit the Configuration File page

As an example, if a user needed to replace the property tibco.env.CUSTOM_PATH, tibco.env.CUSTOM_LIB_PATH and tibco.env.ODBCINI in ${TIBCO_HOME}/adapter/adadb/6.3/bin, then the XML example code below could accomplish this when used in the Edit configuration file text field.

<?xml version='1.0' encoding='utf-8' standalone='yes' ?><containerConfig> <configFiles baseDir="${TIBCO_HOME}/adapter/adadb/6.3/bin"

include="adbagent.tra"><regex pattern="tibco\.env\.CUSTOM_PATH"

replacement="tibco.env.CUSTOM_PATH xxxx" /></configFiles><configFiles baseDir="${TIBCO_HOME}/adapter/adadb/6.3/bin"

include="adbagent.tra"><regex pattern="tibco\.env\.CUSTOM_LIB_PATH.*"

replacement="tibco.env.CUSTOM_LIB_PATH xxxx" /></configFiles>

WARNING! Changes to the configuration.xml can break the installation. Before making any changes to the configuration.xml please back it up and secure it. Please consult an expert to ensure that any distribution changes are properly made. More information on use of the configuration.xml may be found in the TIBCO Silver Fabric documentation.


| 45

<configFiles baseDir="${TIBCO_HOME}/adapter/adadb/6.3/bin" include="adbagent.tra"><regex pattern="tibco\.env\.ODBCINI.*"

replacement="tibco.env.ODBCINI xxxx" /></configFiles>

</containerConfig>

The property, baseDir, in the <configFiles> element is used to specify the path that includes the file to be updated. It can be modified if needed. For example, if the TIBCO ActiveMatrix Adapter for Database (adadb) version was 6.3 instead of 6.2, then the baseDir value would be ${TIBCO_HOME}/adapter/adadb/6.3/bin

The property, include, in <configFiles> element is used to specify which file(s) need to be replaced. It can specify whatever files you want to change. The asterisk wild card may be used to represent a string of characters like for instance: "*.tra" to change all of the .tra files in %baseDir%.

The property, pattern, in the <regex> element is used to specify the contents that need to be replaced within the previously specified files. The value of pattern can be a regular expression.

The property, replacement, in <regex> element is used to specify the new contents of the node specified by the pattern property value.

Where "xxxx"would be the path in your implementation environment.


46 |

Creating a TIBCO Silver Fabric Enabler for Adapter for Database

Stack

A TIBCO Silver Fabric Enabler for Adapter for Database Stack must contain a single TIBCO Administrator Component and one or more TIBCO Adapter for Database Components. After creating and publishing the above Components, you can create TIBCO Silver Fabric Enabler for Adapter for Database Stack.

Each TIBCO_DOMAIN has one TIBCO Silver Fabric Enabler for Adapter for Database Stack. After starting an Stack, you can update it by adding or removing Adapter for Database Components.

To create a TIBCO Silver Fabric Enabler for Adapter for Database Stack:

1. In the TIBCO Silver® Fabric Administration Tool, select Stacks > Stacks.

2. In the Global Actions list, select Create New Stack as shown in Figure 29.

Figure 29 Creating a Stack

3. Enter a Stack name in the Stack Builder page as shown in Figure 30.

4. In the Components area, add one TIBCO Administrator Component and one or more Adapter for Database Components.


| 47

5. In the Policies area, expand the Component you just added to view the details of the Component.

Figure 30 Stack Builder Page


48 |

Dependency Requirements

Each Adapter for Database Component, must have a component dependency set on one TIBCO Administrator Component. You must set this Component Dependency for each of your Adapter for Database Components. Those components without defined Component Dependencies will not have enough information for proper publishing.

The Adapter for Database Component must have the TIBCO Administrator configuration information so that it may publish, unpublish, and communicate with other components (if required) successfully. A connection is supported between the Adapter for Database Component and one instance of the TIBCO Administrator Component. Connecting with more than one TIBCO Administrator Component is not supported. After setting the dependency, TIBCO Adapter for Database will start after TIBCO Administrator is up and running.

To set the dependency, follow these steps:

1. During creation or during edit of the Adapter for Database Component, select "Add/edit default rule settings" from the Menu of the Component Wizard.

2. Use the Add Rule pull down to select the Component Dependency option.

Figure 31 Setting Administrator Component Dependency

3. In the "Reference Component" field, select the name of the TIBCO Administrator Component that runs inside your Application.

This step is required. If you do not set the dependency, TIBCO Silver Fabric Enabler for Adapter for Database will not work.


| 49

If you run TIBCO Administrator in the Fault Tolerant mode, uncheck the Shutdown Dependency checkbox. Otherwise, all Adapter for Database Components will stop if TIBCO Administrator stops working.

If the Administrator Component was configured to "Use dependent EMS server" then that dependency must be set here as well.

When using a dependent TIBCO Enterprise Message Service™ server, the dependency should be set in the TIBCO Administrator Component, which must also have a dependency on TIBCO EMS Server Component.


50 |

Adapter for Database Statistics

If you want Adapter for Database Components to scale (add new Engines) automatically, you can define rules that add or remove TIBCO Silver® Fabric Engines based on Engine statistics.

Data collected are aggregated. The aggregate is used to average raw statistic values by using a source ID. The average is calculated by individually averaging the statistic values for each source ID (for example, for each Engine), and then averaging the results across all Engines.

If the aggregated value triggers the rule, but the normalized geometric variance across the Engines is less than 0.85, then it does not add an Engine. Removing Engines is not affected by variance.

When an Engine is added, it will automatically publish the Adapter for Database project on a new Engine.

You can set up rules on Enablement Condition. The Engine will start upon statistics rules on other Engines. You also can setup rules on threshold activation, which is the statistic on the Engine itself or other Engines.

To set up rules for an Engine, follow these steps:

1. In the Policies area of the TIBCO Silver Fabric Enabler for Adapter for Database application builder page, select the component you want to set up rules.

2. Select Threshold Activation or Enablement Condition in the Add A Rule list.

Scaling using statistics is not supported when TIBCO Silver Fabric publishes the Adapter for Database Components to a single TIBCO Domain Machine.


| 51

3. If you select Threshold Activation, specify the following parameters in the Create Threshold Activation Rule panel:

— In Condition Type list: select the Component Statistic item.

— In the Action list, select Add Engine or Remove Engine.

— In the Component list, select the Component where the statistic rules apply.

— In the Statistics list, select the statistics property on which the activation will be based.

— In the Comparison list, select the operator such as: Greater Than or Less Than.

— In the Value field, set the value of the measure that will serve as the threshold or defining line that will trigger the action when criteria is met.

— In the Sampling Window field, set the time interval (in seconds). It specifies how often the statistics are evaluated against the criteria defined to trigger the action selected.

Figure 32 Creating Rules

Statistics consist of Engine and machine measures that are independent of Adapter for Database, and any other statistical information gathered from the Adapter for Database via TIBCO Hawk® when that is applicable.


52 |

You can see the statistics that are tracked by the Component created to publish the Adapter for Database by selecting that Component in the rule creation window.

Figure 33 Statistics available with the Silver Fabric Enabler for Adapter for Database Component


| 53

Running TIBCO Silver Fabric Enabler for Adapter for Database

Stack

After you have created your Application, you need to publish it. Then click Run Stack In Manual Mode in the Actions drop-down list as shown in Figure 34.

Figure 34 Running a Stack

If you defined a policy schedule while creating the Stack, you can run the Stack in the Auto mode. The Stack will run given the schedule defined. For more information on creating and running Stacks refer to the TIBCO Silver Fabric documentation.


54 |

Updating TIBCO Silver Fabric Enabler for Adapter for Database

Stack

After running an Stack, you can add or remove the Adapter for Database Component or change the rules.

Save the project. In the Actions list in the main Stack page, select Apply Changes. The specified Engines will be affected by the changes immediately.

If you want to add a new Adapter for Database Component, you do not need to stop and restart your entire Stack, just update it.


| 55


56 |


| 57

Chapter 3 Log Files

This chapter introduces log files.

Topics

• Adapter for Database Log Files, page 58

• Retained Log Files, page 59


58 |

Adapter for Database Log Files

You can retrieve TIBCO Administrator and Adapter for Database log files from the TIBCO Silver® Fabric Administration Tool. To do so, follow these steps:

1. In TIBCO Silver® Fabric Administration Tool, select Engines > Log Search.

2. Select the Component from which you want to see the log files, as shown in Figure 35.

3. Optionally you can search for a regular expression using the Expression field.

4. Select the Start Time to see the logs since that time.

Figure 35 Log Files


| 59

Retained Log Files

In addition to the Engine log file, the following log files are retained:

• TIBCO Hawk Agent Log Files, page 59

• TIBCO Administrator Log Files, page 59

• Adapter for Database Log Files, page 58

TIBCO Hawk Agent Log Files

For both TIBCO Administrator Components and Adapter for Database Components, TIBCO Silver Fabric Enabler for Adapter for Database uses TIBCO Hawk® and TIBCO Hawk® Agent. Table 2 lists the retained TIBCO Hawk® log files.

TIBCO Administrator Log Files

When TIBCO Administrator runs in the Fault Tolerant mode, all files are not located under the TIBCO Silver® Fabric $ENGINE_WORK_DIR directory. The Hawk® log files do not appear in the TIBCO Silver® Fabric Administrator GUI.

Table 2 Retained TIBCO Hawk® Agent Log Files

Name Location Purpose of the Log

Hawk.log $ENGINE_WORK_DIR/domaindata/tra/TIBCO_DOMAIN/logs

Log file of the Hawk call in the Hawk® Agent.

tsm.log $ENGINE_WORK_DIR/domaindata/tra/TIBCO_DOMAIN/logs

Log file of the Hawk® Agent.

msghma.log $ENGINE_WORK_DIR/domaindata/tra/TIBCO_DOMAIN/logs

Log file for tibhawkhma.

When TIBCO Administrator runs in the Fault Tolerant mode, all files are not located under the TIBCO Silver® Fabric $ENGINE_WORK_DIR directory. The TIBCO Administrator log files do not appear in the TIBCO Silver® Fabric Administration Tool.


60 |

Table 3 lists the retained TIBCO Administrator Log Files.

Adapter for Database Deployment Log Files

Table 4 lists the retained Adapter for Database Log Files.

Table 3 Retained TIBCO Administrator Log Files


audit.log $ENGINE_WORK_DIR/domaindata/admin/TIBCO_DOMAIN/logs

All information about TIBCO Administrator activities.

tomcat.log $ENGINE_WORK_DIR/domaindata/admin/TIBCO_DOMAIN/tomcat/logs

Technical log of TIBCO Administrator that runs on Tomcat.

domainutility.log

$ENGINE_WORK_DIR/tibco/tra/tra_version_2digits/logs

Log file of the domainUtilitty command used to create the domain or add the machine. This file is common for all Engines.

Table 4 Retained TIBCO Adapter for Database Log Files


ApplicationManagement.log

$ENGINE_WORK_DIR/domaindata/tra/TIBCO_DOMAIN/logs

Generated by Appmanage, which publishes Adapter for Database Applications.

domainutility.log $ENGINE_WORK_DIR/tibco/tra/tra_version_2digits/logs

Log file of the domainUtilitty command used to create a domain or add a machine. This file is common for all Engines.

Adapter for Database Application Name, for example, OrderConsolidation-

Order_Consolidation

.log

$ENGINE_WORK_DIR/domaindata/tra/TIBCO_DOMAIN/application/logs

These are the most important log files, as they are the log files from Adapter for Database and trace all activities that have happened.


| 61

Index

A

Administrator Componentpublish 30, 43

Administrator Domain 11

B

Basic ConfigurationUser Name - Password 12

C

CA Certificate 26Component, containers 3Components 3Components, creating 31Configuring the Component, task list 31Creating a Stack 46Creating an application 46customer support xiii

D

DB_URL 22Dependency Requirements 48dependency, setting 48distributions 3, 9, 33Documentation x, x, xiiiDomain Encoding 12Domain Machine Name 34

E

EAR File 37Edit Configuration File 44EMS Server URL 17EMS User Name 17, 17EMS_SERVER_URL 20Enable HTTPS 12Enable LDAP 12Enablement condition 50entity 6

F

Fault Tolerance 16Fault Tolerance (FT) Mode 16Fault Tolerant 49Functionalities 2

H

Hawk Daemon 19Hawk Network 19Hawk Service 20HTTP Base Port 20HTTP Shutdown Base Port 21, 26HTTPS Base Port 24, 26HTTPS Shutdown Base Port 25

J

JDBC Driver 21, 23JDBC_DRIVER 21


62 |

K

key.p8 26Keystore Password 25, 26

L

LDAP Integration With SSL Connections 14, 28Log Files

Administrator 59Log files 58log files

ApplicationManagement.log 60audit.log 60domainutility.log 60, 60Hawk.log 59msghma.log 59tomcat.log 60tsm.log 59

Log Files, Deployment 60Log Files, Hawk Agent 59Log Files, retained 59

M

Maximum JDBC Connection Pool Size 23Minimum JDBC Connection Pool Size 22

P

Product_HOME xi

R

remote Daemon 19Rendezvous® Daemon, remote 18

RuntimeContextVariableDB_URL 22EMS_SERVER_URL 20JDBC_DRIVER 21

RV DAEMON 18RV Network 19RV Service 19

S

Server Certificate 26SILVERFABRIC_HOME xisource ID 50Statistics 50Store Domain Information in a Database 14support, contacting xiii

T

tasks, creating Administrator component 7tasks, creating an application 6technical support xiiiThreshold Activation 50TIBCO Administrator 7TIBCO Administrator Container 3TIBCO Domain 7TIBCO Domain Logical Machine Name 34TIBCO Hawk® connection configuration 18TIBCO Rendezvous® Daemon, remote 18TIBCO Silver Fabric Enabler, updating 54TIBCO Silver Fabric Engine 50TIBCO_HOME xiTIBCOmmunity xiiiTLM 34

U

Upload projects 37Use Dependent EMS Server 15


| 63

Use EMS as Transport 15

X

XML file 37, 38

Z

ZIP File 37


64 |


Date post:	15-Jun-2020
Category:	Documents
Upload:	others
View:	2 times
Download:	0 times

TIBCO Silver Fabric Enabler for Adapter for Database Users ... · TIBCO Silver ® Fabric Enabler...

Documents