tib_amx_bpm_install

TIBCO ActiveMatrix® BPM

Installation Software Version 1.0.3December 2010

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 TIBCO N2 INSTALLATION GUIDE) 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.TIB, TIBCO, TIBCO Software, TIBCO Adapter, Predictive Business, Information Bus, The Power of Now and TIBCO Business Studio are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.EJB, Java EE, J2EE, JMS 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. PLEASE 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 © 2005-2010 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

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

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

How to Contact TIBCO Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Chapter 1 Installing TIBCO ActiveMatrix BPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installing TIBCO ActiveMatrix BPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 2 TIBCO Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Running TIBCO Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Saving and Applying a TIBCO Configuration Tool Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Configure Third-Party Driver Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Create TIBCO Host Instance Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Create TIBCO ActiveMatrix Administrator Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Replicating an Administrator Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Configure TIBCO ActiveMatrix BPM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Securing Communication Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 3 Frequently Asked Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 4 Uninstalling TIBCO ActiveMatrix BPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Uninstalling TIBCO ActiveMatrix BPM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Appendix A Configuring TIBCO ActiveMatrix BPM in a High Availability Implementation . . 55

Configuring TIBCO ActiveMatrix BPM in a High Availability Implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

TIBCO ActiveMatrix BPM Installation Guide

iv | Contents


| v

Preface

This guide explains how to install TIBCO ActiveMatrix BPM.

Topics

• Documentation Conventions, page vi

• How to Contact TIBCO Support, page viii


vi | Documentation Conventions

Documentation Conventions

The following conventions are used throughout this guide:

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

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

Use MyCommand to start the TIBCO 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 the username admin.

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

• In command syntax, to indicate the default value.

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO BusinessWorks Concepts for more details.

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

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

Key combinations

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

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


Preface | vii

Installation DirectoriesThe following variables are used throughout this guide to refer to directories where BPM components are installed:

Variable Refers to...

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

TIBCO ActiveMatrix BPM installs into a directory within <TIBCO_HOME>. This directory is referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME depends on the operating system. For example on Windows systems, the default value is C:\Program Files\TIBCO\amx-bpm\

PATH The PATH variable specifies the location of programs that are required by other programs. In this case, it specifies the pathname to the home directory for Java and the bin directory for Apache Ant, programs that are used by TIBCO ActiveMatrix BPM. For example, if you have installed Java in the \Program Files\Java\jdk1.6.0_18 directory, set PATH to \Program Files\Java\jdk1.6.0_18\bin.

JAVA_HOME The pathname to the directory where you have installed Java. For example, if you have installed Java in the \Program Files\Java\jdk1.6.0_18 directory, set JAVA_HOME to \Program Files\Java\jdk1.6.0_18.


viii | How to Contact TIBCO Support

How to Contact TIBCO Support

For 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

Entry to this site requires a user name and password. If you do not have a user name, you can request one.


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

https://support.tibco.com

| 1

Chapter 1 Installing TIBCO ActiveMatrix BPM

This chapter explains how to install TIBCO ActiveMatrix BPM.

Topics

• System Requirements, page 2

• Installation Overview, page 5

• Installing TIBCO ActiveMatrix BPM, page 12

• Post-Installation Tasks on page 18


2 | Chapter 1 Installing TIBCO ActiveMatrix BPM

System Requirements

To be able to run this version of TIBCO ActiveMatrix BPM, your computer must meet the following hardware and software requirements.

Hardware RequirementsTIBCO recommend the following hardware requirements:

• The minimum server machine specification is a an x86-based, Dual 2.5 Ghz processor with 4 GB of memory.

• You should allow 2 GB of free space on the local drive where you are installing TIBCO ActiveMatrix BPM.

Software RequirementsMake sure that your target computer meets the following software requirements before installing TIBCO ActiveMatrix BPM.

Operating System and Database Requirements

TIBCO ActiveMatrix BPM is supported on the following operating systems and database combinations:

PlatformSQL Server SP2 Standard (32 Bit) with SQL Server 2008 SP1

SQL Server R2 Standard (64 Bit) with SQL Server 2008 SP1

Oracle 11g Enterprise Edition Release R2

Windows Server 2008 (x86)

Yes No Yes

Windows Server 2008 (x64)

No Yes Yes

Red Hat Enterprise Linux v5.4 (32 Bit and 64 Bit)

No No Yes

SUSE Enterprise Linux 11 (64 Bit)

No No Yes

Sun SPARC Solaris 10 (64 bit)

No No Yes


System Requirements | 3

Java Requirements

TIBCO ActiveMatrix BPM requires Java Developer Kit (JDK) Version 1.6.0_20.

Browser Requirements

TIBCO ActiveMatrix BPM includes the following browser based features; TIBCO Workspace and TIBCO Openspace. Shown below are the browsers that are supported for each of these features:

LDAP Requirements

TIBCO ActiveMatrix BPM requires an LDAP compatible Directory Server is required to store and authenticate users within ActiveMatrix BPM.

• Apache Directory Server Version 1.5.5

Sun Solaris (x86) (32 bit/64 bit)

No No Yes

The Microsoft SQL Server must be configured for XA Transactions, see Configure Your Microsoft SQL Server 2008 Database to Support XA Transactions on page 10.

You must have a valid JDBC Driver for each database type, as you are asked to supply the location of your JDBC Driver during installation, see Make the JDBC Drivers Available on page 9.

PlatformSQL Server SP2 Standard (32 Bit) with SQL Server 2008 SP1

SQL Server R2 Standard (64 Bit) with SQL Server 2008 SP1

Oracle 11g Enterprise Edition Release R2

Browser TIBCO Workspace TIBCO Openspace

Internet Explorer 8 Yes Yes

Mozilla Firefox 3.0 and 3.5 Yes Yes

Safari 4 No Yes

Ensure that the Apache Directory Server service is running before installing TIBCO ActiveMatrix BPM.



Any Directory Server used must be accessible using the Lightweight Directory Access Protocol(LDAP). Typically this will be an existing corporate LDAP; however if a corporate LDAP is not accessible or does not exist, a local LDAP such as Apache Directory Server, may be installed and used.

Other Requirements

TIBCO ActiveMatrix BPM requires:

• TIBCO Enterprise Message Service Version 5.1.5

• Hibernate 3.2.7 is required. During the installation process for TIBCO ActiveMatrix BPM, you can either:

— Make sure you are online and the installer will automatically install Hibernate, or

— Download Hibernate from the TIBCO download site, before installing TIBCO ActiveMatrix BPM. During installation, you will be asked to specify the directory where you downloaded Hibernate.

Before installing TIBCO ActiveMatrix BPM, you must map emshost to localhost, see Configure TIBCO EMS Host on page 9.


Installation Overview | 5

Installation Overview

The following section describes what you need to know before installing TIBCO ActiveMatrix BPM.

TIBCO ActiveMatrix BPM ArchitectureYou must install TIBCO ActiveMatrix BPM on a single server. A node cluster architecture is not supported in this release.

Installation ProfilesThere are three different installation profiles available that allow you to customize the installation of TIBCO ActiveMatrix BPM components. Selecting one of these profiles installs a subset of TIBCO ActiveMatrix BPM components. The following table describes the profiles:

Using a profile results in an installation with the fewest possible steps, as it only installs the components you require. If you want to add or remove individual features, you should select Customize Installation.

Installation Profile Description

Install BPM, Administrator & TIBCO Host Installs a complete BPM node on your machine.

Install Administrator & TIBCO Host Installs TIBCO ActiveMatrix Administrator server and TIBCO Host only.

Install TIBCO Host Only Installs TIBCO Host only.



The following table describes each feature:

The following table describes the features that are selected for each profile.

Feature Description

BPM Installs a complete BPM node.

Administration Environment TIBCO ActiveMatrix Administrator server is the utility used to create, configure, monitor, and manage objects in BPM at runtime. See TIBCO ActiveMatrix Administration for more information.

TIBCO Host TIBCO Host is the runtime object that serves as the point of contact between BPM nodes and Administrator server. TIBCO Host has a staging area that contains product and custom features available to the nodes it manages. It performs operations such as software distribution, node creation, node life cycling, and application deployment.

AMX BPM Documentation Installs the TIBCO ActiveMatrix BPM documenation in <TIBCO_HOME>\bpm\1.0\doc\doc.

Feature

Install BPM, Administrator & TIBCO Host

Install Administrator & TIBCO Host

Install TIBCO Host Only

BPM Yes No No

Administration Environment

Yes Yes No

TIBCO Host Yes Yes Yes

AMX BPM Documenation

Yes Yes Yes


Installation Overview | 7

Installation DirectoryTIBCO recommends that you install TIBCO ActiveMatrix BPM into a new, empty installation environment (separate from other TIBCO products).

To do this, install BPM as described in Installing TIBCO ActiveMatrix BPM on page 12. Specify a new, empty directory as the environment location or create a new, empty installation environment.

Installer Account

Windows Server 2008

You must have administrator privileges for the machine on which TIBCO ActiveMatrix BPM 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, you must ensure that the account used for installation has permission to access the network drive.

Linux

There are no restrictions on the type of user you should use to install TIBCO ActiveMatrix BPM. However, TIBCO recommends that you install as the user you plan to use for TIBCO ActiveMatrix BPM to avoid any potential permissions issues.



Installer Log FileThe installer log file is written to the following locations.

Windows Server 2008

User_Home\.TIBCO\install_identifier directory where identifier is in the form of the date and time TIBCO ActiveMatrix BPM was installed and a unique number used to identify this particular installation.

For example, C:\Documents and Settings\user-name\.TIBCO\install_03-02-2010.132827

Linux

$HOME/.TIBCO/install_identifier directory where identifier is in the form of the date and time TIBCO ActiveMatrix BPM was installed and a unique number used to identify this particular installation.

For example, /home/user1/.TIBCO/install_03-02-2010.132827


Pre-Installation Tasks | 9

Pre-Installation Tasks

Before installation, perform the tasks described in this section as applicable.

Configure TIBCO EMS HostBefore installing TIBCO ActiveMatrix BPM, you must map emshost to localhost in the hosts file. To do this:

1. Open the

— for Windows: %windir%\system32\drivers\etc\hosts file

— for Linux: etc\hosts file

in a text editor.

2. Edit the following line as follows:127.0.0.1 localhost emshost

3. Save and exit the file.

Make the JDBC Drivers AvailableTo connect with the database, TIBCO ActiveMatrix BPM requires a JDBC driver for the database you are using. During installation, you are asked for the location of the JDBC Driver. Therefore, you need to have a local copy of the JDBC Driver for the database you are using before you start installing TIBCO ActiveMatrix BPM.

If you are using:

• SQL Server 2008 with Service Pack 1 or later:

a. Download Microsoft SQL Server JDBC Driver 2.0 from http://www.microsoft.com/downloads/details.aspx?FamilyID=99B21B65-E98F-4A61-B811-19912601FDC9&displaylang=en

b. Follow the instructions to install the driver.

c. See Configure Third-Party Driver Wizard, page 24 for information on how to specify the JDBC driver when configuring TIBCO ActiveMatrix BPM.

• Oracle 11g Release 2, 32-bit and 64-bit, when installing TIBCO ActiveMatrix BPM, specify ojdbc6.jar from your Oracle installation.


http://www.microsoft.com/downloads/details.aspx?FamilyID=99B21B65-E98F-4A61-B811-19912601FDC9&displaylang=en


Check that Port 1433 is Enabled For Your Microsoft SQL Server 2008 Database This only applies to Microsoft SQL Server 2008.

If you are using Microsoft SQL Server 2008, check that port 1433 is enabled. To do this:

1. In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration.

2. In the console pane, click Protocols for <instance name> where instance name is the name of the TIBCO ActiveMatrix BPM database.

3. In the Details pane, right-click the protocol you want to change, and then click Enable.

Configure Your Microsoft SQL Server 2008 Database to Support XA Transactions

This only applies to Microsoft SQL Server 2008.

If you are using Microsoft SQL Server 2008, you must configure your database to support XA transactions. To do this:

1. If you have not already done so, download the Microsoft SQL Server JDBC Driver 2.0 from the following location:


2. Connect to SQL Server 2008 as an administrator of the SQL Server Instance.

3. From the location where you downloaded the Microsoft SQL Server JDBC Driver 2.0, run the sqljdbc_2.0\enu\xa\xa_install.sql script against the master database. The first time you run this you may see errors about failing to drop procedures. These errors may be ignored as the procedures do not exist yet.

4. Depending on your operating system, from the location where you downloaded the Microsoft SQL Server JDBC Driver 2.0, copy either

— sqljdbc_2.0\enu\xa\x86\sqljdbc_xa.dll, or

— sqljdbc_2.0\enu\xa\IA64\ sqljdbc_xa.dll, or

— sqljdbc_2.0\enu\xa\x64\ sqljdbc_xa.dll file

to the Binn folder of the SQL server being used, for example C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn.

5. Click Control Panel > Administrative Tools.



Pre-Installation Tasks | 11

6. Double-click Component Services. The Component Services dialog is displayed.

7. Drill down to Component Services > Computer > My Computer > Distributed Transaction > Local DTC.

8. Right-click Local DTC and select Properties. The Local DTC Properties dialog is displayed.

9. Click Security. Make sure the Enable XA transactions check box is selected.



Installing TIBCO ActiveMatrix BPM

Install TIBCO ActiveMatrix BPM using one of the following modes:

• Install in GUI Mode on page 12

• Installing in Silent Mode on page 16

Install in GUI Mode1. Log in to the system on which you want to install TIBCO ActiveMatrix BPM

(for more information, see Installer Account, page 7).

2. Open the physical media or download the TIBCO ActiveMatrix BPM package to the machine on which you want to install TIBCO ActiveMatrix BPM.

3. Extract the TIBCO ActiveMatrix BPM archive file to a temporary directory.

4. Navigate to the folder where you unzipped the archive file.

5. Run TIBCOUniversalInstaller. The Welcome dialog is displayed.

If you want the installer to automatically install Hibernate 3.2.7, make sure you are online. See Software Requirements on page 2 for more information.

Note that:

— The Installer contains some long pathnames. To avoid path length problems, TIBCO recommends that you install TIBCO ActiveMatrix BPM on a local drive.

— If you want to recover the disk space used by the installation files that you extracted, delete them after you have installed TIBCO ActiveMatrix BPM.

When installing on Solaris (SPARC or x86) platform, the following error messages may appear on the console:Verifying JVM../TIBCOUniversalInstaller-sol-x86.bin: whoami: not found Extracting Installation Archive../TIBCOUniversalInstaller-sol-x86.bin: whoami: not found./TIBCOUniversalInstaller-sol-x86.bin: whoami: not found

These messages are harmless and can be ignored. If you do not wish to see such messages, edit the environment variable PATH as shown: PATH=/usr/ucb: $PATH; export PATH


Installing TIBCO ActiveMatrix BPM | 13

6. Review the information in the Welcome dialog and click Next. The License Agreement dialog is displayed.

7. Review the terms of the license agreement and, if you agree to them, click I accept the terms of the license agreement. Then click Next to continue with the installation.

If you do not agree to the terms of the license agreement, click Cancel to exit from the installation process.

The Installation Profile Selection dialog is displayed.



8. Choose a profile from the list in the left hand pane. (See Installation Profiles on page 5). The right hand pane displays the features that are selected for each profile. If you select Customize Installation, all the features are selected. You can add or remove individual features, depending on your requirements.

9. The TIBCO Installation Home dialog displays. TIBCO_HOME is the preferred top level installation directory for all TIBCO products on your system. Select either:

— Create a new TIBCO_HOME. Click Browse to specify an environment location (a directory path to an empty folder into which the software will be installed), or accept the default environment location (which is the last directory in the path selected).

— Use an existing TIBCO_HOME. Select an existing TIBCO_HOME from the drop-down list.

The installer automatically creates an environment name for the location you specify. The default environment name is amx-bpm. If this is not the first installation of TIBCO software, you can edit the environment name to differentiate this installation of TIBCO software from the previous installations.

Click Next.

10. The Hibernate License Agreement dialog displays.

Review the terms of the license agreement and, if you agree to them, click I accept the terms of the license agreement. Then click Next to continue with the installation.

If you do not agree to the terms of the license agreement, click Cancel to exit from the installation process.

11. The Download Hibernate dialog displays.

— Click Download Hibernate assembly from TIBCO to automatically install Hibernate.

— Click Select the Hibernate assembly previously downloaded from TIBCO and click Browse to browse to the location if you have previously downloaded Hibernate from TIBCO.

Click Next.

To automatically install Hibernate 3.2.7, make sure you are online. See Software Requirements on page 2 for more information.



12. The TIBCO Configuration Directory dialog displays. The configuration directory stores BPM configuration information, for example, the properties for Workspace and Openspace. Click Next to accept the default location or Browse to browse to the location where you want your configuration information to be stored.

13. The Pre-Install Summary dialog displays. Review the information displayed in the dialog and make sure that it is correct.

To change any of your choices, click Back to step back through the dialogs to the appropriate point. You can then restart the installation process from that point.

14. Click Install. The installer now performs the necessary installation tasks.

15. Once the installer has finished the installation tasks, the Running Product ANT Tasks dialog displays while the installer now performs the necessary tasks to initialize the installation. Click Show Details to see the tasks that the installer is performing.

16. The Post Install Summary dialog displays. Click Finish to exit from the installer. There is a slight delay while the installer deletes temporary files.

17. You must now run the TIBCO Configuration Tool to configure TIBCO Active Matrix BPM (see Running TIBCO Configuration Tool on page 20). The TIBCO Configuration Tool provides a set of wizards that allow you to configure the runtime objects and drivers required by TIBCO ActiveMatrix BPM. The following table describes the wizards you should run and the order in which they should be run, depending on the installation profile you chose in step 8:

Installation Profile Wizard

Install BPM, Administrator & TIBCO Host

1. Configure Third-Party Driver to configure the JDBC Drivers for your database.

2. Create TIBCO ActiveMatix BPM Server - V1.1 to configure TIBCO ActiveMatrix BPM.

This wizard not only contains the configuration dialogs for TIBCO ActiveMatrix BPM but also incorporates the dialogs for the Create TIBCO ActiveMatrix Administrator Server - V1.1 and the Create TIBCO Host Instance - V3.1 wizards as well. Once you have completed the dialogs that are specific to TIBCO Active Matrix BPM, you can click Finish to accept the defaults for the rest of the dialogs.



Installing in Silent ModeIn 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.silent file.

The TIBCOUniversalInstaller.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.silent file, it’s 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 TIBCO ActiveMatrix BPM in silent mode. If errors occur during installation, they will be listed in the installation log file contained in User_Home/.TIBCO directory.

1. Open the physical media or download the TIBCO ActiveMatrix BPM package.

Install Administrator & TIBCO Host 1. Configure Third-Party Driver to configure the JDBC Drivers for your database.

2. Create TIBCO ActiveMatrix Administrator Server - V1.1 to configure your TIBCO ActiveMatrix Administrator Server.

Install TIBCO Host Only 1. Configure Third-Party Driver to configure the JDBC Drivers for your database.

2. Create TIBCO Host Instance - V3.1 to configure your TIBCO Host.

You can ignore wizards that are not relevant to the profile you selected.

When you get to the Summary screen, you must uncheck:

— Deploy Monitoring Service

— Deploy Log Service

This is because it adversely effects the performance of TIBCO ActiveMatrix BPM.

Installation Profile Wizard



2. Extract the contents of the package to a temporary directory.

3. Using a console window, navigate to the temporary directory.

4. Make a copy of the TIBCOUniversalInstaller.silent file and rename the file.

5. Using a text editor, open the copied file and update the install location and features to install.

6. Run the following:

Windows TIBCOUniversalInstaller.exe -silent -V

responseFile="myfilename.silent"

Linux TIBCOUniversalInstaller -silent -V

responseFile="myfilename.silent"

When installation completes, a line similar to the following is written to the installer log file:Install, com.tibco.installer.util.TIBCOInstaller, dbg.Debug, The installation has completed. Please check the log file for additional information.

7. Go to step 17 to find out how to run the TIBCO Configuration Tool to configure TIBCO Active Matrix BPM.



Post-Installation Tasks

The Mediation product application is not deployed by default on the BPMNode when you install ActiveMatrix BPM. Once you have installed ActiveMatrix BPM, you must manually deploy the Mediation product application. To do this:

1. From the Administrator interface in BPM runtime, go to Applications.

2. Add a new application named com.tibco.amx.it.mediation.app using the existing application template.

3. Distribute the application to the BPM Node.

4. Deploy the application by selecting Deploy with Start.

Once the above application is running, you can deploy the mediation samples to check that mediation is now available.

Refer to the Administration documentation for your runtime environment for more information on adding, distributing and starting your application.


| 19

Chapter 2 TIBCO Configuration Tool

TIBCO Configuration Tool provides a set of wizards that allow you to configure runtime objects and drivers required by the TIBCO ActiveMatrix platform.

Topics

• Running TIBCO Configuration Tool, page 20

• Saving and Applying a TIBCO Configuration Tool Configuration on page 23

• Configure Third-Party Driver Wizard on page 24

• Create TIBCO Host Instance Wizard on page 25

• Create TIBCO ActiveMatrix Administrator Server on page 27

• Replicating an Administrator Server on page 43

• Configure TIBCO ActiveMatrix BPM Server on page 45

• Securing Communication Channels, page 47

TIBCO ActiveMatrix BPM Installation

20 | Chapter 2 TIBCO Configuration Tool

Running TIBCO Configuration Tool

1. Execute ENV_HOME/tct/1.0/TIBCOConfigurationTool. The TIBCO Configuration Folder dialog displays.

A TIBCO configuration folder stores configuration data generated by TIBCO products. Configuration data can include sample scripts, session data, configured binaries, logs, and so on.

2. Accept the default folder, type a folder name, or click Browse to select a folder.

3. Click OK. TIBCO Configuration Tool displays with links to the configuration wizards:

While running the Create TIBCO Host Instance and Create TIBCO ActiveMatrix Administrator Server wizards, you select a TIBCO Enterprise Message Service server that acts as a notification server for the host andActiveMatrix Administrator server and the Messaging Bus for the environments created in the ActiveMatrix Administrator server.

Each enterprise must use a different TIBCO Enterprise Message Service server and the TIBCO Enterprise Message Service server must be running before you start either wizard.

Table 2 Configuration Wizards

Wizard Function

Create TIBCO ActiveMatrix Administrator Server on page 27

This wizard allows you to

• Specify the properties of an ActiveMatrix Administrator server and optionally create the server. The TIBCO Host instance named SystemHost and SystemNode node that runs ActiveMatrix Administrator server and the development node will be started.

• Optionally specify a development environment and node and start the node.

• Specify the properties of monitoring, logging, and payload services running on SystemNode and optionally deploy the monitoring and logging services.

The properties you specify include the database that serves as a persistent store for ActiveMatrix Administrator server and the monitoring, logging, and payload services. If you intend to use an external database other than HyperSQL you must first package and install the database driver using the Configure Third-Party Driver Wizard and start the database server before running this wizard.


Running TIBCO Configuration Tool | 21

4. Click Load to load the values saved from a previous configuration session. The default locations of the saved configuration sessions are CONFIG_FOLDER/tct/[admin|tibcohost|tpclshells]/date-randomNumber, where CONFIG_FOLDER is the folder you specified in step 2.

5. Choose a wizard and configure according the wizard reference.

6. Optionally check the Configure to Secure All Communication with SSL checkbox. When checked, all wizards offering configuration options for communication channels present fields for specifying SSL configuration to secure those communication channels. The supported communication channels are between

— TIBCO ActiveMatrix Administrator server and TIBCO ActiveMatrix runtime objects (hosts and nodes)

— TIBCO ActiveMatrix Administrator server and external servers (TIBCO Enterprise Message Service, LDAP, database, UDDI)

— TIBCO ActiveMatrix Administrator server and its clients (GUI and CLI)

— Applications and resource instances (JMS, SMTP, LDAP, HTTP)

7. On any screen, click Finish to accept default values for all the configuration properties and jump to the Summary screen.

Create TIBCO Host Instance Wizard on page 25

This wizard allows you to specify the communication and management properties of a standalone TIBCO Host instance and then optionally creates and launches the TIBCO Host instance.

Configure Third-Party Driver Wizard on page 24

This wizard allows you to package and deploy third-party client driver libraries, such as JDBC and JMS, into TIBCO ActiveMatrix Administrator server so that ActiveMatrix Administrator server and ActiveMatrix applications can access third-party servers.

Configure TIBCO ActiveMatrix BPM Server on page 45

This wizard allows you to configure the BPM database and runtime clients for TIBCO ActiveMatrix BPM Server.

Table 2 Configuration Wizards

Wizard Function



8. In the Summary screen, the wizard reports the configuration tasks it will perform. Do one of the following:

— Click Save to save configuration session settings.

— Click Cancel to return to the wizard selector screen.

— Execute the configuration tasks:

a. Uncheck the checkboxes next to tasks you do not want executed.

b. Click Configure to execute the tasks and save the configuration settings. The wizard reports the status of tasks as it completes them. On Windows systems, after the TIBCO Host instance is started, click Unblock if you see the following dialog pop up:

If you are running the Configure TIBCO ActiveMatrix BPM Server wizard, you must uncheck:

— Deploy Monitoring Service

— Deploy Log Service

This is because it adversely effects the performance of TIBCO ActiveMatrix BPM.


Saving and Applying a TIBCO Configuration Tool Configuration | 23

Saving and Applying a TIBCO Configuration Tool Configuration

1. Run a wizard in TIBCO Configuration Tool.

a. In the Summary screen, click the Save button.

b. A confirmation dialog displays. Click OK to dismiss the dialog.

c. Note the location of the configuration folder in the Session Scripts and Log Folder field.

d. Click Cancel.

2. Copy the folder Session Scripts and Log Folder to the machine on which the configuration will be applied.

3. Open a command window in Session Scripts and Log Folder/scripts and run ant.

TIBCO_HOME must be the same on all machines running the configuration.



Configure Third-Party Driver Wizard

Table 3 Details

Field Description

Driver Type The type of driver being configured: JDBC or JMS.

Default: JDBC.

Driver The supported drivers:

• JDBC - Microsoft SQL Server 2.0.0, Oracle 11.1.0

• JMS - SonicMQ 6.1.0, WebSphere 7.0.0

Table 4 JAR Folder

Field Description

JAR Folder The folder containing the client driver JARs to deploy to the ActiveMatrix Administrator server.


Create TIBCO Host Instance Wizard | 25

Create TIBCO Host Instance Wizard

Configuration details for the TIBCO Enterprise Messaging Service server that will be used by this TIBCO Host instanceto deliver notifications.

Table 5 TIBCO Host Instance Details

Field Description

Name The name of the TIBCO Host instance.

Default: TibcoHostInstance.

Enterprise Name

Defines a communication group for notification messages sent between ActiveMatrix Administrator server and the hosts that are bound to the server.

Default: amxadmin.

Machine Name

The name of the machine on which the TIBCO Host instance will run.

Default: machinename, where machinename is the machine on which TIBCO Configuration Tool is being executed.

Management Port

The management port of the TIBCO Host instance.

Default: 6001.

Register as Windows Service

If checked, the TIBCO Host instance is registered as a Windows service with the name TIBCO ActiveMatrix hostName with startup type Automatic. The service is not started.

Default: Unchecked.

Create Windows Shortcut

If checked, a shortcut named hostName that points to CONFIG_FOLDER\tibcohost\hostName\host\bin\tibcohost.exe is added to your Windows desktop.

Default: Unchecked.

Table 6 TIBCO Enterprise Message Service Server

Field Description

Machine Name Port List

A comma separated list of machinename:port addresses for a TIBCO Enterprise Message Service server.

Default: machinename:port, where machinename is the machine on which TIBCO Configuration Tool is being executed and port is 7222 or 7243 (when SSL enabled).



Choose whether to create or upload a trust store keystore.

Username A username for the TIBCO Enterprise Message Service server.

Default: admin.

Password A password for the TIBCO Enterprise Message Service user.

Default: None.

Enable SSL Indicate that the TIBCO Enterprise Message Service server is enabled for SSL. When checked, the SSL Keystore Configuration fields are enabled.

Table 6 TIBCO Enterprise Message Service Server (Cont’d)

Field Description

Table 7 SSL Keystore Configuration

Field Description

SSL Config Specify that the trust store will be created.

Keystore Location

The location of the uploaded keystore.

Keystore Type The type of the uploaded keystore: JKS or JCEKS.

Default: JKS.

Keystore Password

The password that protects the uploaded keystore.


Create TIBCO ActiveMatrix Administrator Server | 27

Create TIBCO ActiveMatrix Administrator Server

Table 8 summarizes the components that are configured in the Create TIBCO ActiveMatrix Administrator Server wizard, their function, and the decisions you must make, the information you must gather, and actions you must take before running the wizard.

The Create TIBCO ActiveMatrix Administrator Server wizard takes 15 minutes or more to complete depending on the configuration options.

Table 8 Component Options

Component Function Options and Actions

TIBCO Host Instance

See TIBCO Host Instance on page 30

The TIBCO Host instance that manages the SystemNode node on which the ActiveMatrix Administrator server runs.

Provide configuration details for the TIBCO Host instance.

Development Node

See TIBCO Host Instance on page 30.

A development node on which to deploy applications managed by the TIBCO Host instance.

Provide the name and management port of the development node and the name of the environment that contains the node. If you intend to complete the tutorials in TIBCO ActiveMatrix Administration Tutorials, you must create the development node and accept the default values for the environment and node names.

ActiveMatrix Administrator server

See ActiveMatrix Administrator Server on page 30.

See Connection Settings on page 31.

The ActiveMatrix Administrator server.

Provide the name of the communication group within which status messages are exchanged and the name of the ActiveMatrix Administrator server.

Provide communication properties for the ActiveMatrix Administrator server.



Notification Server

See TIBCO Enterprise Message Service Server on page 25.

Propagates status messages between hosts, nodes, and the ActiveMatrix Administrator server.

Provide configuration details for the TIBCO Enterprise Message Service server.

Database

See Database Details on page 33.

Stores ActiveMatrix Administrator configuration data.

Choose an internal or external database. If the latter, provide configuration details for database server.

If you choose an external database, the database server must be running before running this wizard. The driver for HyperSQL database, org.hsqldb.jdbcDriver, is provided with TIBCO ActiveMatrix software. To use another database, you must first package and install the driver using the wizard Configure Third-Party Driver Wizard on page 24.

Authentication Realm

See Authentication Realm on page 35.

Stores user and group data. Choose a database or LDAP authentication realm. Provide configuration details for the authentication realm.

A database authentication realm stores user and group authentication data in a database. Users and groups in this realm can be edited within ActiveMatrix Administrator. You also have the option to use the same database for authentication data and administration data.

An LDAP authentication realm stores user and group authentication data in an LDAP server. Users and groups in this realm can only be edited with LDAP server management tools.

If you choose database, and are using a database different than the one the ActiveMatrix Administrator server uses, the database server must be running before running the wizard. If you choose an LDAP realm, the LDAP server must be running.





TIBCO Credential Server

See Credential Server Details on page 1.

Provides credentials to enable secure interactions between ActiveMatrix Administrator servers, hosts, and nodes.

Choose an autogenerated or external keystore. If you choose an external keystore, provide configuration details for the keystore.

Monitoring Service

See Monitoring Notification Server on page 41 and Monitoring Database on page 41.

Aggregates monitoring data.

Choose the ActiveMatrix Administrator notification server and database or another notification server and database.

If the latter, provide the notification server and database configuration details and ensure that the database is running before running the wizard.

Logging Service

See Log Service Database on page 41.

Aggregates and stores log entry data.

Choose the ActiveMatrix Administrator database or another database. If the latter, provide database configuration details and ensure that the database is running before running the wizard.

Payload Service

See Payload Service Database on page 42.

Store large payloads associated with log entries. (Internal use only.)

Choose the ActiveMatrix Administrator database or another database. If the latter, provide database configuration details and ensure that the database is running before running the wizard.



Table 9 Welcome

Field Description

Configure to Secure All Communication with SSL

Check to indicate that all communication channels will be secured with SSL. When checked, the Enable SSL checkboxses on the If you choose this option, the TIBCO Enterprise Message Service server that functions as the notification server and ActiveMatrix Administratordatabase must be enabled with SSL before running the wiz



Table 10 ActiveMatrix Administrator Server

Field Description

Enterprise Name

Defines a communication group for notification messages sent between ActiveMatrix Administrator server, the hosts that are bound to the server, and the nodes that are managed by those hosts.

Default: AMX BPM.

Server Name The name of the ActiveMatrix Administrator server.

Default: AMX BPM Server.

Table 11 TIBCO Host Instance

Field Description

Machine Name

The name of the machine on which the TIBCO Host instance runs.

Default: hostname, where hostname is the machine on which TIBCO Configuration Tool is being executed.

Port The management port of the TIBCO Host instance.

Default: 6051.

Create Development Node

Specify whether to create a development environment and node. When checked, the Environment Name, Node Name, and Node Management Port fields display.

Default: Checked.

Environment Name

The name of the development environment that contains the development node.

Default: BPMEnvironment.

Node Name The name of the development node.

Default: BPMNode.

Node Management Port

The management port of the development node.

Default: 6031.



.

Table 12 Connection Settings

Field Description

Machine Name

The name of the machine on which the ActiveMatrix Administrator server runs.

Default: 0.0.0.0.

Management Port

The management port of the node, SystemNode, that runs the ActiveMatrix Administrator server.

Default: 6021.

Browser HTTP Port

The port on which ActiveMatrix Administrator clients access the ActiveMatrix Administrator server.

Default: 8120.

Enable SSL for Browser HTTP Port

Indicate whether communication between ActiveMatrix Administrator server and clients are secured with SSL.

Self-signed Certificate (Not for production)

Indicate that ActiveMatrix Administrator server will identify itself to clients with a self-signed certificate.

Imported Certificate

Indicate that ActiveMatrix Administrator server will identify itself to clients with a certificate imported into ActiveMatrix Administrator server.

Keystore Location

The location of the keystore to import.


Default: JKS.

Keystore Password

The password that protects the keystore.

Key Alias The key alias that identifies entry identifying the ActiveMatrix Administrator server.

Key Password The password that protects the key alias.



Configuration details of the TIBCO Enterprise Message Service server that will be used to deliver notifications and serve as the Messaging Bus for the environments created in the ActiveMatrix Administrator server.

Table 13 Internal HTTP Settings

Field Description

Internal HTTP Port

The number of the internal HTTP port used by host and nodes to download artifacts from the ActiveMatrix Administrator server.

Enable SSL Indicate whether communication between ActiveMatrix Administrator server and hosts and nodes are secured with SSL.

Browser Idle Session Timeout(m)

The length of time before the login session of the ActiveMatrix Administrator GUI times out.

Default: 30.

Use HTTP Load Balancer

Specify that an HTTP load balancer will be used to distribute requests from hosts and nodes to the ActiveMatrix Administrator server. When checked, the Server Base URL field displays.

Load Balancer URL

The base URL for the ActiveMatrix Administrator server load balancer.

Default: http://hostname:port, where hostname is the ActiveMatrix Administrator server hostname and port is the ActiveMatrix Administrator server port.

Table 14 TIBCO Enterprise Message Service Server

Field Description


A comma separated list of machinename:port addresses for a TIBCO Enterprise Message Service server.

Default: machinename:port, where machinename is the machine on which TIBCO Configuration Tool is being executed and port is 7222 or 7243 (when SSL enabled).

Username A username for the TIBCO Enterprise Message Service server.

Default: admin.

Password A password for the TIBCO Enterprise Message Service user.

Default: None.

Enable SSL Indicate that the TIBCO Enterprise Message Service server is enabled for SSL. When checked, the SSL Keystore Configuration fields are enabled.



Choose whether to create or upload a trust store keystore.


Field Description

SSL Config Specify that the trust store will be created.

Keystore Location

The location of the uploaded keystore.


Default: JKS.

Keystore Password

The password that protects the uploaded keystore.

Table 16 Database Details

Field Description

Use Default In-Process Database

Specify that the ActiveMatrix Administrator server database is an embedded in-process database. If unchecked, the database configuration fields display.

Default: Checked.

Database Driver

The driver for the external database. The driver for HyperSQL database, org.hsqldb.jdbcDriver, is provided with TIBCO ActiveMatrix software. To use another database you must first package and install the driver using the Configure Third-Party Driver Wizard on page 24.

Default: org.hsqldb.jdbcDriver.

Database URL The URL of the external database.

Default: jdbc:hsqldb:hsql://localhost:1234/amx.

Username The external database username.

Default: sa.

Password The external database password.

Default: None.



Trust Keystore

Choose the source of the trust store keystore:

• Create

a. Click Create a Trust Store....

b. Specify a password to protect the keystore and click Next >. The SSL setup wizard displays certificates imported from trusted servers.

c. In the Trust Selected Certifications area, check the checkboxes next to the certificates to trust and click Finish. The wizard fills in the Keystore Location, Keystore Type, and Keystore Password fields.

Max Connections

The maximum number of database connections to allocate.

Default: 5.

Enable SSL Indicate that the database server is enabled for SSL. When checked, the SSL Keystore Configuration fields are enabled.

Table 16 Database Details

Field Description


Field Description

Create a Trust Store... Invokes a wizard to import certificates from a server and create the trust store.

Keystore Location The location of the keystore.

Keystore Type The type of the keystore: JKS or JCEKS.

Default: JKS.

Keystore Password The password that protects the keystore.



• Upload

a. Click Browse and navigate to the location of the keystore.

b. Click the keystore and click Open. The wizard fills in the Keystore Location field.

c. In the Keystore Type drop-down list, select the keystore type.

d. Type the keystore password.

e. Click Test Connection.

Table 18 Authentication Realm

Field Description

Authentication Realm

Realm Type The type of the authentication realm: Database or LDAP. If Database, the Table 19 on page 35 screen displays. If LDAP, the LDAP Authentication Realm Details on page 1, Group Settings on page 1, and LDAP Server Settings on page 3 screens display.

Superuser Credentials

Username The ID of the initial superuser.

Default: root.

Password The password of the superuser.

Default: t.

Table 19 Database Authentication Realm Details

Field Description

Use ActiveMatrix Administrator Database

Specify whether the database authentication realm should use the same database as the ActiveMatrix Administrator server.

Default: Checked. If unchecked, the database configuration fields in Database Details on page 33 display.



Table 20 LDAP Authentication Realm Details

Field Description

Bind DN Name

The superuser's distinguished name or superuser's name to be used to connect to the server.

Default: uid=Manager,ou=people,dc=example,dc=com.

Password LDAP server password.

Context Factory

The factory object that provides the starting point for resolution of names within the LDAP server.

Default: com.sun.jndi.ldap.LdapCtxFactory.

Server URL The URL used to log in to the LDAP server.

Default: ldap://localhost:389.

User Search Configuration

User Search Base DN

Base distinguished name from which the search starts.

Default: ou=people,ou=na,dc=example,dc=org.

User Search Expression

The expression used for searching a user. For example: (CN=%U). '%U' is replaced by the username being searched for. You can define any complex filter such as (&(cn=%U)(objectClass=account)).

Default: (&(uid={0})(objectclass=person)).

Attribute Name to Get User's Name

The name of the attribute in the user object that represents the user's name.

Default: uid.

Search Timeout (sec)

The time to wait for a response from the LDAP directory server.

Default: 10.

Table 21 Group Settings

Field Description

Group Search Base DN Base distinguished name from which the search for the group starts.

Default: ou=groups,ou=na,dc=example,dc=org.



Group Search Expression Search by matching this expression against potential groups.

Default: uniquemember={0}.

Group Attribute Users Name The name of the attribute in each group object denoting its users.

Example: uniqueMember (OpenLDAP) or member (ActiveDirectory).

Default: uniqueMember.

Group Attribute Groups Name

The name of the attribute in each group object that contains the name of the group.

Example: cn (OpenLDAP) or sAMAccountName (ActiveDirectory).

Default: cn.

Group Attribute Subgroup Name

The name of the attribute in each group denoting subgroups.

Example: uniqueMember (OpenLDAP) or member (ActiveDirectory).

Default: uniqueMember.

Group Indication Specifies how a user’s group memberships are found. Group information is used by the Administrator when a user, once authenticated, performs other activities in the system.

Options:

• Group Has User Members— A list of users that belong to the group.

• User Has Group Memberships— A list of groups to which the user belongs.

• User DN Hierarchy Implies Group Memberships — The DN with a list of groups to which the user belongs.

Default: Group Has User Members.

Group Search Scope Subtree When searching the group, indicate whether to traverse into the subtree or to search only under the group base distinguished name.

Default: Checked (enabled).

Table 21 Group Settings (Cont’d)

Field Description



Table 22 LDAP Server Settings

Field Description

LDAP Realm

User Search Scope Subtree (optional)

Search the entire subtree starting at the base DN, otherwise search only the nodes one level below the base DN.

Default: Checked (enabled).

Key Password (optional)

The value of the password protecting the key for the admin's password. Only used when logging in as the Administrator.

Default: No default for Key Password.

Security Authentication

Security protocol to be used by JNDI.

• Simple—Username and password are required.

• Strong—SSL with client-side authentication is enabled.

• None—No log-in is performed, any other settings are ignored, and the LDAP client is anonymous.

Default: Simple.

LDAP Authentication

User DN Template

The template by which the User DN, used to connect to the LDAP server, is generated. Because the full DN is always supplied, the template should always be 0 (zero).

Default: uid={0},ou=people,ou=na,dc=org

User Attributes Extra (optional)

An optional list of user attributes to retrieve from the LDAP directory during authentication.

Default: Empty (no additional attributes will be retrieved for the user).

Enable SSL Indicate that the LDAP server is enabled for SSL. When checked, the SSL Keystore Configuration fields are enabled.



Trust Keystore

Choose the source of the trust store keystore:

• Create

a. Click Create a Trust Store....

b. Specify a password to protect the keystore and click Next >. The SSL setup wizard displays certificates imported from trusted servers.

c. In the Trust Selected Certifications area, check the checkboxes next to the certificates to trust and click Finish. The wizard fills in the Keystore Location, Keystore Type, and Keystore Password fields.

• Upload

a. Click Browse and navigate to the location of the keystore.

b. Click the keystore and click Open. The wizard fills in the Keystore Location field.

c. In the Keystore Type drop-down list, select the keystore type.

d. Type the keystore password.

e. Click Test Connection.


Field Description

Create a Trust Store... Invokes a wizard to import certificates from a server and create the trust store.

Keystore Location The location of the keystore.

Keystore Type The type of the keystore: JKS or JCEKS.

Default: JKS.

Keystore Password The password that protects the keystore.



Choose whether to use a self-signed keystore generated by TIBCO Credential Server or a keystore that has been signed by a CA.

Table 24 Credential Server Details

Field Description


A comma separated list of machinename:port addresses for the TIBCO Credential Server.

Default: machinename:port, where machinename is the machine on which ActiveMatrix Administrator server runs and port is 6041.

Username A user identifier for TIBCO Credential Server clients.

Default: user1.

Password The password for the client.

Default: password1.

Table 25 Credential Server Keystore

Field Description

Auto-generated Keystore

Specify that the TIBCO Credential Server keystore will be generated. When selected, the Common Name field displays.

Common Name The TIBCO Credential Server’s issuer name.

Default: amxadmin.

Provided Keystore

Specify that the TIBCO Credential Server keystore will be provided. When selected, the keystore fields displays.

Keystore Location

The location of the keystore.

Default: TIBCO_HOME/tibcohost/1.2/templates/admin.default.ssl.trust.store.ts.

Keystore Type The type of the keystore.

Default: JCEKS.

Keystore Password

The password for the keystore.



Key Alias The name of the alias used to access the identity.

Key Password The password for the alias.

Table 25 Credential Server Keystore

Field Description

Table 26 Monitoring Notification Server

Field Description

Use ActiveMatrix Administrator Notification Server

Specify whether the monitoring service should use the same notification server as the ActiveMatrix Administrator server.

Default: Checked. If unchecked, the notification server fields in TIBCO Enterprise Message Service Server on page 1 display.

Table 27 Monitoring Database

Field Description


Specify whether the monitoring service should use the same database as the ActiveMatrix Administrator server.

Default: Checked. If unchecked, the notification server fields in Database Details on page 33 display.

Table 28 Log Service Database

Field Description


Specify whether the log service should use the same database as the ActiveMatrix Administrator server.

Default: Checked. If unchecked, the database server fields in Database Details on page 33 display.



Table 29 Payload Service Database

Field Description


Specify whether the payload service should use the same database as the ActiveMatrix Administrator server.

Default: Checked. If unchecked, the database server fields in Table 16, Database Details, on page 33 display.


Replicating an Administrator Server | 43

Replicating an Administrator Server

1. Perform step 1 in Saving and Applying a TIBCO Configuration Tool Configuration on page 23. Choose the Create TIBCO ActiveMatrix Administrator Server wizard.

a. In the Connection Settings screen, select the Use HTTP Load Balancer checkbox and specify the load balancer URL. The load balancer should have sticky connections so that the client session context is maintained.

b. In the Database Details screen, specify an external database. Ensure that the URL in the Database URL field contains a DNS name.

2. Edit the file Session Scripts and Log Folder/scripts/integration_create_admin_data.xml.

a. Set the instanceWorkFolder attribute of the AdminConfigFolders element to a folder that is the same on all machines.

b. Set the sharedWorkFolder attribute of the AdminConfigFolders element to a folder in the shared file system.

c. Set the location attribute of the SCMDetails element to a location in the shared file system.

d. Save the file.

3. Perform step 3 in Saving and Applying a TIBCO Configuration Tool Configuration on page 23. A TIBCO Host instance named SystemHost is created and started. A node named SystemNode is created in the environment named SystemEnvironment and started. The Administrator server runs on SystemNode.

4. Perform step 2 in Saving and Applying a TIBCO Configuration Tool Configuration on page 23. Choose the machine on which to replicate the Administrator server.

• TIBCO_HOME must be the same on all machines running Administrator server replicas.

• There must be a shared file system with the same path mounted on all machines running Administrator server replicas.

• The Administrator server replicas must use an external database.



5. Edit files in the Session Scripts and Log Folder/scripts folder on the replica machine:

a. In the admin-envt-data.xml file, comment out the Environment element.

b. In the admin-tibcohost-instance.properties file, replace machineOriginal with machineReplica in the amx.th.trinity.tcs.url and amx.th.hpa.jmx.interface properties.

c. In the cl_logservice_data.xml, cl_payloadservice_data.xml, integration_create_admin_data.xml files, replace all instances of SystemNode with another node name, SystemNodeReplica and all instances of SystemHost with another host name, SystemHostReplica.

d. In the file integration_create_admin_data.xml replace all instances of machineOriginal with machineReplica, except for the instances in the StatusTransportDetails, JdbcResourceTemplate > Direct, and SystemMessagingBus elements.

6. Edit TIBCO_HOME/administrator/3.0/scripts/instance-mgmt.xml on the replica machine:

a. In the file, replace

<target name="full-setup" depends="-define-macros, create-dir-structure, standalone-tcs, start-th, deploy-admin, -maybe-create-dev-node, deploy-mediation, configure.tcs, start.tcs"/>

with

<target name="full-setup" depends="-define-macros, create-dir-structure, start-th, deploy-admin, -maybe-create-dev-node, deploy-mediation"/>

7. If you installed third-party drivers before running the Create TIBCO ActiveMatrix Administrator Server wizard, install the drivers using the Configure Third-Party Driver Wizard on the replica machine.

8. Perform step 3 in Saving and Applying a TIBCO Configuration Tool Configuration on page 23. A TIBCO Host instance named SystemHostReplica is created and started. A node named SystemNodeReplica is created in the environment named SystemEnvironment and started. The replica Administrator server runs on SystemNodeReplica. When you log in to either of the Administrator servers (or access the load balancing URL), there will be two hosts in Infrastructure > Hosts screen and two nodes in the SystemEnvironment environment in the Infrastructure > Nodes screen. Requests can be processed by either of servers. If one node is unavailable, the other will able to process requests.


Configure TIBCO ActiveMatrix BPM Server | 45

Configure TIBCO ActiveMatrix BPM Server

Table 30 ActiveMatrix BPM: Database Administrator

Field Description

Database Driver The database driver you want to use for the BPM database.

URL Once you have selected the database driver, the Admin JDBC URL field is automatically completed with the connection string used in the JDBC connection to the Administrator database.

DBA Username The user name of the login that you want BPM to use to connect to the BPM database. The TIBCO Configuration Tool automatically creates the username you specify.

DBA Password The password for the specified user login.

Confirm Password The password for the specified user login again to confirm it.

Tablespace Name The name of the tablespace that is used to store the BPM tables.

Default: bpm_tablespace.

Test Connection Click Test Connection to test the connection to your database.

Table 31 ActiveMatrix BPM: Runtime Database Configuration

Field Description

JDBC URL The JDBC URL field is automatically completed with the connection string used in the JDBC connection to the BPM database.

Username Specify the user name of the login that you want BPM to use to connect to the BPM database. The TIBCO Configuration Tool automatically creates the username you specify.

Default: bpmuser.

Password Enter the password for the specified user login.

Confirm Password Enter the password for the specified user login again to confirm it.



Table 32 ActiveMatrix BPM: Client Configuration

Field Description

HTTP Work Presentation Host

The machine name that hosts Workspace. If the machine is different from the machine where you are running BPM, then this should be a fully qualified domain name or IP address. The machine name you specfiy is also the name used in the default security certificate.

Default: localhost

HTTP Port The port for Workspace.

Default: 8080.

Enable SSL Specify to enable secure communication for Workspace and Openspace.

SMTP Host The machine name that hosts the SMTP server that is used by Workspace. If the machine is different from the machine where you are running BPM, then this should be a fully qualified domain name or IP address.

Default: localhost.

SMTP Port The port number used by the SMTP server.

Default: 25.


Securing Communication Channels | 47

Securing Communication Channels

Table 33 SSL Configuration Workflows

Channel Initial Configuration Update Configuration

TIBCO ActiveMatrix Administrator server and TIBCO ActiveMatrix runtime objects (hosts and nodes)

Secured by TCS: TCS Configuration

Internal Port Number

Checkbox to enable SSL

CLI Action to upgrade/downgrade SSL and change port number

Configure external load-balancer (virtual host:port)

TIBCO ActiveMatrix Administrator server and external servers (LDAP, database, UDDI)

enable SSL for LDAP, DB in admin creation

Allows keystore to be provided in two ways:

Offers “trust workflow” (do you want to trust this url?)

Upload a user-created truststore

CLI action to change the ldap, DB configuration

TIBCO ActiveMatrix Administrator server and external servers (TIBCO Enterprise Message Service

option for keystore location and keystore passwords for trust store

Provide CLI/UI Option to enable, disable QIN with SSL and change QIN configuration

Provide UI Option to upload keystore, password and host it internally (Through KCP)

Provide a “trust workflow” in UI.



TIBCO ActiveMatrix Administrator server and its clients (GUI and CLI)

Upload your keystore with identity certificate

We generate a self-signed identity certificate (demos-only)

Auto-configures CLI on local machine to enable SSL connectivity

Writes the keystore to a known location.

CLI-only (no UI) action to upgrade & downgrade to SSL

CLI-only (no UI) action to change SSL configuration

Applications and resource instances (JMS, SMTP, LDAP, HTTP)

“SSL Setup Wizard” that has the trust-workflow.

Auto-create the chain of resource templates.

Host keystores in Administrator or externally

Table 33 SSL Configuration Workflows

Channel Initial Configuration Update Configuration


| 49

Chapter 3 Frequently Asked Questions

Why and how should I set the DISPLAY variable on Solaris for GUI mode?

The installer on Solaris opens an additional window, generally for graphics. It uses the DISPLAY environment variable to tell it on which computer to open the window. If the environment variable is not set, the installer will either wait or abort after displaying:

InstallShield WizardInitializing InstallShield Wizard...Preparing Java(tm) Virtual Machine.................................................................................

Set the DISPLAY variable to the IP address or name of the computer (on which the installer graphics window is to be displayed), followed by a screen address, which can be :0.0. For example:

# Bourne shellDISPLAY=ip_address:0.0; export DISPLAY

# Korn shellexport DISPLAY=ip_address:0.0# C-shellsetenv DISPLAY ip_address:0.0

For example, consider a scenario where you need to install TIBCO ActiveMatrix Service Grid on a remote Solaris 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 monitoralaska> telnet itaskaWelcome to HPUX itaska 11.00User:Password:itaska> export DISPLAY=alaska:0.0 # set display on alaska

itaska> tar -xvf TIB_tra-suite_5.0.0_h7_11.tar


50 | Chapter 3 Frequently Asked Questions


| 51

Chapter 4 Uninstalling TIBCO ActiveMatrix BPM

This chapter explains how to uninstall TIBCO ActiveMatrix BPM from your computer.

Topics

• Uninstalling TIBCO ActiveMatrix BPM on page 52


52 | Chapter 4 Uninstalling TIBCO ActiveMatrix BPM

Uninstalling TIBCO ActiveMatrix BPM

If you want to uninstall TIBCO ActiveMatrix BPM from your system, perform the following steps:

Linux

Use the uninstaller provided with TIBCO ActiveMatrix BPM.

Windows

Either:

• Use the uninstaller provided with TIBCO ActiveMatrix BPM or

• Remove the installation using the Add/Remove Programs option on your PC.

Using the UninstallerTo use the uninstaller:

1. Log in to the system on which you want to uninstall software.

2. The Welcome dialog is displayed. Click Next.

3. Select either Custom (to choose products in this environment to uninstall) or Typical to uninstall all products in the environment.

If you selected Typical, continue with step 5.

If you selected Custom, continue with the next step.

4. The Product Uninstall Selection dialog is displayed.

Select the products (for example, TIBCO ActiveMatrix BPM 1.0) you want to uninstall and click Next.

5. The Ready to Uninstall dialog is displayed.

If you want to change any of your choices, click Back to step back through the dialogs to the appropriate point. You can then restart the uninstallation process from that point.

6. When you are satisfied with your choices, click Uninstall.

The uninstaller removes the software product you specified.

The TIBCO ActiveMatrix BPM entries in the Start menus may appear after the uninstallation. To correct this log out, then log in again.


Uninstalling TIBCO ActiveMatrix BPM | 53

Using Add/Remove Programs (Windows Only)To remove the installation using the Add/Remove Programs option on your PC:

1. Log in to Windows as a user with system administrator privileges. You must have system administrator privileges to uninstall this software.

2. In the Control Panel, double-click the Add or Remove Programs.

3. In the Add/Remove Programs dialog, select TIBCO Universal Installer (installation_environment_n), where installation_environment_n is the directory corresponding to the installation environment you want to uninstall. If you have installed more than one TIBCO product, there will be multiple entries in Add/Remove programs (for example, TIBCO Universal Installer (c:\tibco\env_1), TIBCO Universal Installer (c:\tibco\env_2), and so on).

4. Click Change/Remove.

The uninstaller launches. Follow the uninstallation steps in Using the Uninstaller on page 52.


54 | Chapter 4 Uninstalling TIBCO ActiveMatrix BPM


| 55

Appendix A Configuring TIBCO ActiveMatrix BPM in a High Availability Implementation

This chapter explains how to configure TIBCO ActiveMatrix BPM in a high availability standby implementation.

Topics

• Configuring TIBCO ActiveMatrix BPM in a High Availability Implementation on page 56


56 | Appendix A Configuring TIBCO ActiveMatrix BPM in a High Availability Implementation

Configuring TIBCO ActiveMatrix BPM in a High Availability Implementation

TIBCO ActiveMatrix BPM uses third party solutions such as Microsoft Cluster, HP ServiceGuard or Oracle RAC to provide high availability and/or fault tolerance. In the event of a hardware failure on a machine that causes TIBCO ActiveMatrix BPM to fail, the cluster software restarts TIBCO ActiveMatrix BPM on another machine, with limited service interruption and no data or messages being lost.

The following diagram illustrates this scenario:

Machine 2 Machine 3

Machine 1

Microsoft Cluster (or similar)

BPM

Shared Storage

Oracle RAC Oracle RAC

Administrator Server

BPM Node or BPM Data filesOracle RAC Datafiles


Configuring TIBCO ActiveMatrix BPM in a High Availability Implementation | 57

To implement this scenario, at least three machines are required.

• Machine 1:

— TIBCO ActiveMatrix BPM software is installed

— TIBCO ActiveMatrix Administrator server is installed and running.

• Machines 2 and 3:

— are connected to a shared file system (like SAN storage, for example).

— are part of an active-passive clustering setup. At any given time, either Machine 2 or Machine 3 has access to the SAN shared file system on which TIBCO ActiveMatrix BPM node is installed/running. If there are catastrophic events such as power loss, hardware failure, network disruption, or operating system crash, the cluster software will detect and fail over to the next available server.

— on either machine 2 or 3: a fully operational TIBCO ActiveMatrix BPM node is installed and running.

• TIBCO ActiveMatrix BPM (or at least the data folder) needs to be on the shared file system and should only be vailable to the machine that has a fully operational TIBCO ActiveMatrix BPM node installed and running.

To implement this scenario, do the following:

On Machine 1Install the TIBCO ActiveMatrix BPM software and create a TIBCO ActiveMatrix Administrator server. To do this:

1. Install TIBCO ActiveMatrix BPM using the Install BPM, Administrator & TIBCO Host profile, see Installing TIBCO ActiveMatrix BPM on page 12.

2. Using TIBCO Configuration Tool, run the Create TIBCO ActiveMatrix Administrator Server - V3.0 wizard to create a TIBCO Administrator server, see Create TIBCO ActiveMatrix Administrator Server on page 27.

On Machine 2 or 3Install a fully operational TIBCO ActiveMatrix BPM server. To do this:

1. Install TIBCO ActiveMatrix BPM using the Install BPM, Administrator & TIBCO Host profile, see Installing TIBCO ActiveMatrix BPM on page 12.


58 | Appendix A Configuring TIBCO ActiveMatrix BPM in a High Availability Implementation

2. Using TIBCO Configuration Tool:

a. Run the Create TIBCO Host Instance - V3.0 wizard to create a TIBCO Host, see Create TIBCO Host Instance Wizard on page 25. From the TIBCO Host Instance Configuration: Administrator Server dialog, select Bind this TIBCO Host instance with an existing Administrator server box and enter the details of TIBCO ActiveMatrix Administrator server that you created on machine 1.

b. Run the Configure Third-Party Driver wizard to register the JDBC drivers for your BPM database, see Configure Third-Party Driver Wizard on page 24.

c. Run the Create TIBCO ActiveMatrix BPM Server - V1.0 wizard, see Configure TIBCO ActiveMatrix BPM Server on page 45. From the ActiveMatrix BPM: Administrator Server Configuration: dialog,

— select the Use Existing ActiveMatrix Administrator Server check box.

— In the Machine Name box, type the name of the TIBCO ActiveMatrix Administrator server you created on machine 1.

— In the Host box, type the name of the TIBCO Host you created in step a.
