installation and configuration - tibco software information some tibco software embeds or bundles...

Two-Second Adv

TIBCO ActiveMatrix® BPM

Installation and ConfigurationSoftware Release 2.1February 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, The Power of Now,TIBCO ActiveMatrix, TIBCO Business Studio, and TIBCO Enterprise Message Server are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or 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 © 2005-2013 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

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

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

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

HOW TO USE THIS GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

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

ActiveMatrix BPM System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4High Availability, Fault Tolerant BPM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Distributed BPM System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Basic BPM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Multiple Installations of BPM Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Installation Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Disaster Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2 Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10System Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Disk Space Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Platform and Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Supported Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Supported Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Database and Platform Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

TIBCO Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16TIBCO Enterprise Message Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Other TIBCO ActiveMatrix Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Third-party Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Apache Ant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Eclipse Standard Web Toolkit (SWT) Graphical Tool Kit (GTK) Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Hibernate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Java Virtual Machine (JVM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

TIBCO ActiveMatrix BPM Installation and Configuration

iv | Contents

JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19LDAP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Web Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

User Account Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Microsoft Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22UNIX or Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Additional System Requirements for a High Availability or Distributed BPM Configuration . . . . . . . . . . . . . . . . . 23Load Balancer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Shared File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Server Time Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

I - INSTALLATION AND UPGRADE SCENARIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 3 Installing and Configuring a Basic ActiveMatrix BPM System. . . . . . . . . . . . . . . . . 31

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Task1: Install ActiveMatrix BPM Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Task 2: Configure JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Task 3: Create a BPM Node and Administrator Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 4 Installing and Configuring a High Availability, Fault Tolerant ActiveMatrix BPM System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Task 1: Primary Machine - Install ActiveMatrix BPM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Task 2: Primary Machine - Configure JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Task 3: Primary Machine - Create a BPM Node and Administrator Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Task 4: Remote Machine - Install ActiveMatrix BPM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Task 5: Remote Machine - Configure JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Task 6: Remote Machine - Create an Administrator Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Task 7: Remote Machine - Create a BPM Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 5 Installing and Configuring a Distributed ActiveMatrix BPM System . . . . . . . . . . . . 51

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52


Task 2: Primary Machine - Configure JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Task 3: Primary Machine - Create a BPM Node and Administrator Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56


Task 5: Remote Machine - Create a TIBCO Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Task 6: Remote Machine - Create a Node of the Required Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60


Contents | v

Chapter 6 Upgrading an ActiveMatrix BPM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64


Task 2: Remote Machine - Upgrade the TIBCO Host Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66


Task 4: Primary Machine - Upgrade ActiveMatrix BPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Task 5: Post-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

II - INSTALLATION AND UPGRADE PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Chapter 7 Preparing for Installation or Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Check For Any Late Breaking Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Check the System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Configure TIBCO Enterprise Message Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Configure an External ActiveMatrix Administrator Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Configuring an External Microsoft SQL Server 2008 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Configuring an External Oracle 11g Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Configuring an External DB2 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Configure the ActiveMatrix BPM Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Configuring Microsoft SQL Server 2008. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Configuring Oracle 11g. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Configuring DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Configure the External LDAP Directory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Configure the Maximum Number of Open Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Configure Apache Ant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Download Required Software Assemblies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Download ActiveMatrix BPM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Pre-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Backup the Existing ActiveMatrix BPM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Backup Workspace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Other Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Chapter 8 Installing ActiveMatrix BPM Software (TIBCO Universal Installer) . . . . . . . . . . . . . .91

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Using a New or an Existing Installation Environment (TIBCO_HOME) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Installing in GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Installing in Console mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Installing in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99


vi | Contents

Chapter 9 Configuring ActiveMatrix BPM Runtime Objects (TIBCO Configuration Tool) . . . 101

Configuring ActiveMatrix BPM in GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Manually Running the ActiveMatrix BPM Database Creation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104ActiveMatrix BPM Database Creation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Configuring ActiveMatrix BPM in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Silentinstall Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108The build.properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Example - Using silentinstall to Configure a Basic ActiveMatrix BPM System . . . . . . . . . . . . . . . . . . . . . . 110

Chapter 10 Distributing the ActiveMatrix BPM Application to a Remote Node . . . . . . . . . . . 113

Distributing the ActiveMatrix BPM Application in a High Availability, Fault Tolerant BPM System . . . . . . . . . . . 114

Distributing the ActiveMatrix BPM Application in a Distributed BPM System . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Chapter 11 Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Create Any Other Required LDAP Connections to LDAP Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Configure Client Communications Through the Load Balancer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Install the Mediation Product Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Configure Transaction Recovery (Oracle only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Set Transaction Verification Property (SQL Server Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Chapter 12 Upgrading ActiveMatrix BPM Runtime Objects (Upgrade Utility) . . . . . . . . . . . . 127

Upgrade Impact. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

The Upgrade Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Running the Upgrade Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

III - TIBCO CONFIGURATION TOOL WIZARD REFERENCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Chapter 13 Configure TIBCO ActiveMatrix BPM Server Node Type Wizard . . . . . . . . . . . . . . 137

Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

ActiveMatrix BPM Node Type: Administrator Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

ActiveMatrix BPM Node Type: Host and Node Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

ActiveMatrix BPM Node Type: Sizing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

ActiveMatrix BPM Node Type: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Chapter 14 Create TIBCO ActiveMatrix BPM Server Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146


Contents | vii

ActiveMatrix BPM: Database Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

ActiveMatrix BPM: Runtime Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

ActiveMatrix BPM: Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

ActiveMatrix BPM: Sizing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

ActiveMatrix BPM: JMS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

ActiveMatrix BPM: LDAP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

ActiveMatrix BPM: Administrator Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

ActiveMatrix BPM: Host and Node Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Chapter 15 Create TIBCO ActiveMatrix Administrator Server Wizard . . . . . . . . . . . . . . . . . . .159

Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Administrator Server Configuration: Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Administrator Server Configuration: TIBCO Host Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Administrator Server Configuration: Connection Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Administrator Server Configuration: Internal HTTP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Administrator Server Configuration: Notification and Messaging Bus Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Administrator Server Configuration: Database Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Administrator Server Configuration: Authentication Realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Administrator Server Configuration: Database Authentication Realm Details . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Administrator Server Configuration: LDAP Authentication Realm Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Administrator Server Configuration: Credential Server Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Administrator Server Configuration: Credential Server Keystore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Administrator Server Configuration: Monitoring Notification Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Administrator Server Configuration: Monitoring Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Administrator Server Configuration: Monitoring Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Administrator Server Configuration: Log Service Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Administrator Server Configuration: Payload Service Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Administrator Server Configuration: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Chapter 16 Create TIBCO Host Instance Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183

Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

TIBCO Host instance Configuration: Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

TIBCO Host instance Configuration: Notification Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

TIBCO Host instance Configuration: Administrator Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187


viii | Contents

Chapter 17 Configure Third-Party Driver Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Third-Party Driver: Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Third-Party Driver: JAR Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

IV - APPENDICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Appendix A Troubleshooting Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Installer Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Sanitizing After a Failed Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Appendix B Restoring ActiveMatrix BPM from a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Appendix C Uninstalling an ActiveMatrix BPM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Uninstalling ActiveMatrix BPM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Using the Uninstaller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Appendix D Disaster Recovery Using Data-Level Replication . . . . . . . . . . . . . . . . . . . . . . . . 203

Data-Level Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Configuring TIBCO ActiveMatrix BPM for Disaster Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Recovering TIBCO ActiveMatrix BPM if the Primary Site Fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Before Starting TIBCO ActiveMatrix BPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218After Starting TIBCO ActiveMatrix BPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Appendix E Disaster Recovery Using Device-Level Replication . . . . . . . . . . . . . . . . . . . . . . 221

Appendix F Securing Communication Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Appendix G TIBCO Enterprise Message Service Server Configuration . . . . . . . . . . . . . . . . . 227

Appendix H Using Third-Party Solutions to Configure a High Availability, Fault Tolerant ActiveMatrix BPM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231


| ix

Preface

TIBCO ActiveMatrix BPM is TIBCO’s next-generation business process management platform. This guide provides the information needed to install and configure the product.

Topics

• Typographical Conventions, page x

• Connecting with TIBCO Resources, page xiii

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.


x | Typographical Conventions

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

ENV_NAME

TIBCO_HOME

BPM_HOME

TIBCO products are installed into an installation environment. A product installed into an installation environment does not access components in other installation environments. Incompatible products and multiple instances of the same product must be installed into different installation environments.

An installation environment consists of the following properties:

• Name Identifies the installation environment. This name is referenced in documentation as ENV_NAME. On Microsoft Windows, the name is appended to the name of Windows services created by the installer and is a component of the path to the product shortcut in the Windows Start > All Programs menu.

• Path The folder into which the product is installed. This folder is referenced in documentation as TIBCO_HOME.

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

CONFIG_HOME The directory that stores the TIBCO ActiveMatrix BPM configuration information, such as property and log files. The value of CONFIG_HOME depends on the operating system. For example, on Windows systems, the default value is C:\ProgramData\amx-bpm\tibco\data.

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.


Preface | xi

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]

italic font Italic font is used in the following ways:

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

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 (Cont’d)

Convention Use


xii | Typographical Conventions

Table 2 Syntax Typographical Conventions

Convention Use

[ ] An optional item in a command or code syntax.

For example:

MyCommand [optional_parameter] required_parameter

| A logical OR that separates multiple items of which only one may be chosen.

For example, you can select only one of the following parameters:

MyCommand para1 | param2 | param3

{ } A logical group of items in a command. Other syntax notations may appear within each logical group.

For example, the following command requires two parameters, which can be either the pair param1 and param2, or the pair param3 and param4.

MyCommand {param1 param2} | {param3 param4}

In the next example, the command requires two parameters. The first parameter can be either param1 or param2 and the second can be either param3 or param4:

MyCommand {param1 | param2} {param3 | param4}

In the next example, the command can accept either two or three parameters. The first parameter must be param1. You can optionally include param2 as the second parameter. And the last parameter is either param3 or param4.

MyCommand param1 [param2] {param3 | param4}


Preface | xiii

Connecting with TIBCO Resources

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

How to Access TIBCO DocumentationYou can access TIBCO documentation here:

http://docs.tibco.com

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, contact TIBCO Support as follows:

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

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

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

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


http://www.tibcommunity.com

http://docs.tibco.com

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


xiv | Connecting with TIBCO Resources


| 1

HOW TO USE THIS GUIDE

1. Read Introduction on page 3.

2. Read Installation Requirements on page 9 and make sure that you have everything in place.

3. Refer to I - INSTALLATION AND UPGRADE SCENARIOS and determine your installation/upgrade scenario.

4. Follow the high-level procedures for that scenario to install/upgrade your BPM system.

To help you find the right information at the right time, this guide is divided into the following parts.

Part Description

I - INSTALLATION AND UPGRADE SCENARIOS

These chapters describe the most common ActiveMatrix BPM installation/upgrade scenarios, and provide high-level procedures for how to implement them.

Find the scenario that matches your requirements and follow the high-level procedures. (Direct links to more detailed information in the other parts of this guide are provided where appropriate.)

II - INSTALLATION AND UPGRADE PROCEDURES

These chapters provide detailed information about specific installation and upgrade procedures. Which of these you need to use will depend upon your particular installation/upgrade scenario,

Use these chapters as directed by the high-level procedures for your installation/upgrade scenario.

III - TIBCO CONFIGURATION TOOL WIZARD REFERENCE

These chapters provide detailed reference information about the individual TIBCO Configuration Tool wizards.

Use these chapters as directed by the high-level procedures for your installation/upgrade scenario.

IV - APPENDICES The appendices provide additional information that you may need when installing or upgrading ActiveMatrix BPM.


2 | HOW TO USE THIS GUIDE


| 3

Chapter 1 Introduction

This chapter describes some issues you should consider before attempting to install or upgrade TIBCO ActiveMatrix BPM.

Topics

• ActiveMatrix BPM System Architecture, page 4

• Multiple Installations of BPM Systems

• Installation Profiles, page 6

• Disaster Recovery, page 7


4 | Chapter 1 Introduction

ActiveMatrix BPM System Architecture

The method you use to install ActiveMatrix BPM depends upon your chosen system architecture. See TIBCO ActiveMatrix BPM Concepts for more information about supported BPM system architectures.

High Availability, Fault Tolerant BPM SystemActiveMatrix BPM software provides active/active clustering capabilities. You can use these capabilities, along with a suitable underlying architecture, to configure an TIBCO ActiveMatrix BPM system to provide high availability and fault tolerance.

See Installing and Configuring a High Availability, Fault Tolerant ActiveMatrix BPM System on page 37 for more information.

Distributed BPM SystemA distributed system enables you to scale only certain components of the BPM runtime so as to boost the performance of your system. The logical nodes can be distributed to different physical nodes, thus enabling horizontal scalability to suit the needs of an enterprise.

Some example scenarios that a distributed system can cater to include:

• an enterprise whose focus is on straight-through processing and enterprise integration may want to direct more resources to Process Manager nodes.

• a call center-based enterprise may require more Work Manager nodes.

See Installing and Configuring a Distributed ActiveMatrix BPM System on page 51 for more information.

Basic BPM SystemA basic system consists of a simple installation with all the components installed on a single machine

See Installing and Configuring a Basic ActiveMatrix BPM System on page 31 for more information.

TIBCO recommend the use of the active/active clustering capabilities of ActiveMatrix BPM to provide high availability and fault tolerance. However, you can also use third-party solutions - see Using Third-Party Solutions to Configure a High Availability, Fault Tolerant ActiveMatrix BPM System for more information.


Multiple Installations of BPM Systems | 5

Multiple Installations of BPM Systems

Multiple BPM systems (that is, two or more instances of the BPM application) cannot be administered by the same ActiveMatrix Administrator instance. This means that the following installation options are not currently possible:

• More than one BPM Environment within a single ActiveMatrix Enterprise.

• More than one BPM system within a single ActiveMatrix Environment.

• More than one BPM system on a single physical host machine.

A BPM system can use either a basic, distributed, or high availability, fault tolerant architecture - see ActiveMatrix BPM System Architecture.



Installation Profiles

Throughout this guide, you will be instructed to perform different tasks on either a primary machine or a remote machine.

A primary machine is the machine on which the ActiveMatrix Administrator server is running. For a basic configuration, the primary machine is the only machine.

A remote machine is any other machine used only in a distributed or high availability, fault-tolerant configuration.

For a high availability, fault tolerant configuration, the machine on which the replicated ActiveMatrix Administrator server is running is regarded as a second primary machine.


Disaster Recovery | 7

Disaster Recovery

There are two approaches you can use if you want to provide a Disaster Recovery (DR) capability for an ActiveMatrix BPM system:

• Data-level replication. This approach:

— requires only file-based and database-based replication software.

— ensures that data on the DR site will be in a consistent state across the various TIBCO ActiveMatrix BPM datastores and will therefore start-up when required.

See Disaster Recovery Using Data-Level Replication for more information.

• Device-level replication. This approach:

— requires dedicated device-level replication hardware and software (with commensurate higher costs).

— ensures that state information held in the file system or database remains synchronized after replication to the DR site.

See Disaster Recovery Using Device-Level Replication for more information.

If the primary site fails, there may be some data loss or lost state changes within executing business processes. The extent of this loss is determined by the latency of the replication of changes on the primary site to the DR site.


| 9

Chapter 2 Installation Requirements

This chapter describes the basic system requirements that must be in place before you can install an ActiveMatrix BPM system.

Topics

• Hardware Requirements, page 10

• Platform and Database Requirements, page 12

• TIBCO Software Requirements, page 16

• Third-party Software Requirements, page 18

• User Account Requirements, page 22

• Additional System Requirements for a High Availability or Distributed BPM Configuration, page 23


10 | Chapter 2 Installation Requirements

Hardware Requirements

TIBCO recommends the following minimum specification for any server used to host ActiveMatrix BPM.

ProcessorTwo 3GHz dual processors.

System Memory8 GB of virtual memory available for user applications

Disk Space RequirementThe installer requires space in the temporary directory before installation, and additional space in the temporary directory for running the installer. You must also make sure sufficient space is in the directory you want to use as the installation environment (TIBCO_HOME) directory.

While performing installation, avoid running other processes that consume disk space in TIBCO_HOME. If another process consumes disk space while the installer is copying the files, the installer might fail and display a failure message.

Directory Disk Space Requirement

Temporary directory used to hold the installer

Before you start the installation process, extract the contents of the installation archive to a temporary directory. The installer files consume up to 900 MB of disk space.

Temporary directory used during installation

The installer requires at least 900 MB of free space in the temporary directory used by the installer. On Microsoft Windows, this directory is typically:

%SystemDrive%:\Documents and Settings\user_name\LocalSettings\Temp

If your system does not have sufficient disk space in the default temporary area, you can run the installer with a different temporary directory by using the following option when starting the installer:

-is:tempdir /new_temp

where /new_temp has sufficient free disk space.


Hardware Requirements | 11

Installation environment directory (TIBCO_HOME)

The installer calculates the disk space required in the installation environment directory for the selected components. The calculation is done before the actual installation (copying of files to the system) begins. The installer will proceed only if sufficient free disk space is available in the installation environment directory.

ActiveMatrix BPM can consume up to 5 GB of free space under TIBCO_HOME.

Directory Disk Space Requirement



Platform and Database Requirements

Supported PlatformsThe following table lists the different combinations of operating system and processor architecture that can be used to host ActiveMatrix BPM. The Supported Versions specified are the minimum versions of each operating system that are supported by ActiveMatrix BPM:

• Any subsequent service packs/patches/updates/fix packs released for the same major version are also supported.

• Higher major versions must be validated by TIBCO to determine if they are supported by ActiveMatrix BPM. If you wish to use a higher major version of one of these operating systems with ActiveMatrix BPM, contact TIBCO Support to find out if that version is supported. Major versions are defined in this context as:

— Microsoft Windows Server 2008

— Microsoft Windows Server 2008 R2

— Novell SUSE Linux Enterprise Server 11

— Red Hat Enterprise Linux Server v5

— Red Hat Enterprise Linux Server v6

— Solaris 10

— IBM AIX v6

— HP-UX 11i V3

Operating System Supported Versions

Supported Processor Architectures

Windows (64-bit)

Microsoft Windows Server 2008 (with any subsequent service packs for this version)

x86-64

Microsoft Windows Server 2008 R2 with SP1 (and any subsequent service packs for this version)


Platform and Database Requirements | 13

Linux (64-bit) Novell SUSE Linux Enterprise Server 11 (and any subsequent service packs for this version)

x86-64

Red Hat Enterprise Linux Server v5.5 (and any subsequent v5.x updates)

Red Hat Enterprise Linux Server v6 (and any subsequent v6.x updates)

Solaris (64-bit) Solaris 10 (and any subsequent patches for this version) x86-64, SPARC

AIX (64-bit) IBM AIX v6.1 (and any subsequent fix packs for this version) POWER

HP-UX (64-bit) HP-UX 11i V3 (and any subsequent updates for this version) Itanium 2

Operating System Supported Versions

Supported Processor Architectures



Supported DatabasesThe following table lists the different database versions that can be used to host the ActiveMatrix BPM and ActiveMatrix Administrator databases.

The Supported Versions specified are the minimum versions of each database that are supported by ActiveMatrix BPM:

• Any subsequent service packs/patches/updates/fix packs released for the same major version are also supported.

• Higher major versions must be validated by TIBCO to determine if they are supported by ActiveMatrix BPM. (Major versions are defined in this context as: Microsoft SQL Server 2008, Microsoft SQL Server 2008 R2, Oracle 11g R2 and DB2 9.7) If you wish to use a higher major version of one of these databases with ActiveMatrix BPM, contact TIBCO Support to find out if that version is supported.

Some database configuration is required before installing ActiveMatrix BPM, depending on the database used and the installation scenario. See Preparing for Installation or Upgrade on page 73 for more information.

Database Supported Versions Supported Editions

Microsoft SQL Server 2008 (64-bit)

2008 (with any subsequent service packs for this version)

Standard or higher

2008 R2 (with any subsequent service packs for this version)

Standard or higher

Oracle 11g R2 (64-bit)

11.2.0.2 (with any subsequent 11.2.0.x patch sets) Standard or higher (with or without RAC enabled)

DB2 (64-bit) 9.7.3 or later 9.7.x (with Fix pack 4 or later for this version)

Workgroup or higher

The platform being used to host ActiveMatrix BPM also affects which database can be used - see Database and Platform Compatibility for more information.


Platform and Database Requirements | 15

Database and Platform CompatibilityThe following table shows the different Supported Databases that can be used to host the ActiveMatrix BPM and ActiveMatrix Administrator databases, according to the Supported Platforms on which ActiveMatrix BPM is running,

Each supported database is listed as either "Supported" or "Not tested" against each supported platform. These terms have the following specific meanings:

• Supported - When ActiveMatrix BPM is hosted on this platform, this database can be used to host the ActiveMatrix BPM and ActiveMatrix Administrator databases. In this case, either:

— TIBCO has extensively tested and validated this platform/database combination against this version or an earlier version of ActiveMatrix BPM, or

— According to the database vendor this version of the database is compatible with the specified platform.

• Not tested - When ActiveMatrix BPM is hosted on this platform, TIBCO has not validated use of this database to host the ActiveMatrix BPM and ActiveMatrix Administrator databases.

Platform hosting ActiveMatrix BPM

Microsoft SQL Server 2008/2008 R2 Oracle 11g R2 DB2

Microsoft Windows Server 2008/2008 R2

Supported Supported Supported

Novell SUSE Linux Enterprise Server 11, Red Hat Enterprise Linux Server v5.5 (or later v5.x) or V6.x

Supported Supported Supported

Solaris 10 Not tested Supported Not tested

IBM AIX v6.1 Not tested Supported Supported

HP-UX (64-bit) Not tested Supported Not tested

Please contact TIBCO Support first if you want to use ActiveMatrix BPM with this platform/database combination.



TIBCO Software Requirements

TIBCO ActiveMatrix BPM software includes the following required and optional software components. See the TIBCO ActiveMatrix BPM Readme file for details of required versions.

TIBCO Enterprise Message ServiceActiveMatrix BPM requires TIBCO Enterprise Message Service (EMS):

• TIBCO Enterprise Message Service is used as the notification and messaging backbone for TIBCO ActiveMatrix BPM.

• You must install TIBCO Enterprise Message Service before you install TIBCO ActiveMatrix BPM. (See Configure TIBCO Enterprise Message Service on page 76).

• TIBCO Enterprise Message Service does not have to be installed on the same machine as TIBCO ActiveMatrix BPM. (You will specify the connection details needed to contact the EMS Server as part of the installation and configuration process.)

• TIBCO Enterprise Message Service can also be used by the TIBCO ActiveMatrix SOAP and JMS binding types. The TIBCO ActiveMatrix BPM license does not cover this usage of the included TIBCO Enterprise Message Service software. You must separately license TIBCO Enterprise Message Service for this usage.

These components are distributed and installed separately from TIBCO ActiveMatrix BPM software. You can download them from the TIBCO Software Product Download Site (https://download.tibco.com/tibco/), from Products Home > TIBCO ActiveMatrix BPM-version > TIBCO ActiveMatrix BPM Software version.


https://download.tibco.com/tibco/

TIBCO Software Requirements | 17

Other TIBCO ActiveMatrix Software ComponentsThe following TIBCO ActiveMatrix software components are not required to install ActiveMatrix BPM, but can be used with ActiveMatrix BPM if desired.

Product Description

TIBCO ActiveMatrix Runtime UDDI Server

TIBCO ActiveMatrix Runtime UDDI Server provides an integrated UDDI registry that can be used by TIBCO ActiveMatrix for discovery and registration of services during service execution.

TIBCO ActiveMatrix Binding Type for Adapters

TIBCO ActiveMatrix Binding Type for Adapters integrates a legacy TIBCO adapter into the ActiveMatrix environment.

TIBCO ActiveMatrix Binding Type for EJB

TIBCO ActiveMatrix Binding Type for EJB is an interface for EJB components to the Service Oriented Architecture (SOA) world.

TIBCO ActiveMatrix Implementation Type for C++

TIBCO ActiveMatrix Implementation Type for C++ integrates C++ applications into the TIBCO ActiveMatrix environment.

Note: On the TIBCO Software Product Download Site, from Products Home, use Search for Components by Name to find this component.



Third-party Software Requirements

Apache AntApache Ant is required to run TIBCO Configuration Tool scripts, TIBCO ActiveMatrix runtime objects upgrade, or TIBCO ActiveMatrix Administrator CLI scripts.

Apache Ant 1.7.1 is supplied as part of the ActiveMatrix BPM software distribution.

Eclipse Standard Web Toolkit (SWT) Graphical Tool Kit (GTK) ModuleIf you are installing ActiveMatrix BPM on a Linux or Solaris platform, the Eclipse SWT GTK module software assemblies are required. (These assemblies are not required if you are installing ActiveMatrix BPM on any other platform.)

You can obtain the Eclipse SWT GTK module in two ways:

• You can download the assemblies automatically when you run the ActiveMatrix BPM installer, if the machine on which you are running the installer has internet access.

• You can download the assemblies from the TIBCO Software Product Download Site (https://download.tibco.com/tibco/), before you install ActiveMatrix BPM.

You should do this if the machine on which you are running the ActiveMatrix BPM installer does not have internet access. See Download Required Software Assemblies for more information.

HibernateActiveMatrix BPM requires Hibernate version 3.2.7. You can obtain this version of Hibernate in two ways:

• You can download Hibernate automatically when you run the ActiveMatrix BPM installer, if the machine on which you are running the installer has internet access.

• You can download Hibernate from the TIBCO Software Product Download Site (https://download.tibco.com/tibco/), before you install ActiveMatrix BPM.




Third-party Software Requirements | 19

You should do this if the machine on which you are running the ActiveMatrix BPM installer does not have internet access. See Download Required Software Assemblies for more information.

Java Virtual Machine (JVM)ActiveMatrix BPM requires a 32-bit or 64-bit JVM.

Java Runtime Environment (JRE) 1.6 is supplied as part of the ActiveMatrix BPM software distribution.

JDBC DriversActiveMatrix BPM requires JDBC drivers for the databases that will be used to host the ActiveMatrix BPM and ActiveMatrix Administrator databases, as shown in the following table:

Refer to your database documentation for information on how to obtain these JDBC drivers.

When downloading Hibernate, the number in the package name refers to the assembly number and not the version of Hibernate. This can be misleading as the assembly number is not the same as the Hibernate version number. For example, the package name when downloading Hibernate Version 3.2.7 is assembly_tibco_com_tpcl_ord_hibernate_feature_3.2.400.001.zip.

Database Required JDBC driver

Microsoft SQL Server 2008 Microsoft SQL Server JDBC Driver 3.0 (sqljdbc4.jar)

Oracle 11g R2 ojdbc6.jar

DB2 db2jcc4.jar



You will need to configure these JDBC drivers for use with ActiveMatrix BPM as part of the installation process.

LDAP ServerAll users who may need to log in to ActiveMatrix BPM (using Openspace, Workspace or a custom client application) must exist in one or more LDAP directories that are accessible to ActiveMatrix BPM.

ActiveMatrix BPM requires one or more LDAP servers that use the Lightweight Directory Access Protocol (LDAP) version 3.

If you are installing:

• a High Availability, Fault Tolerant BPM System or a Distributed BPM System, or any system that is intended for production use, you must use an external LDAP directory server.

• a Basic BPM System that is not intended for production use, you can either use an external LDAP directory server, or the internal LDAP directory server that is provided with ActiveMatrix BPM.

Web BrowsersActiveMatrix BPM requires a web browser to run Openspace, Workspace and the ActiveMatrix Administrator GUI.

The following sections list the web browsers that are supported by the different ActiveMatrix BPM runtime user interfaces.

The Supported Versions specified are the minimum versions of each browser that are supported by ActiveMatrix BPM. Unless otherwise specified, you can use a more recent version of a browser as long as the vendor claims the recent version to be compatible with the specified version.

In the event of a problem with a more recent browser version, TIBCO will employ best efforts to provide support on that browser version. However, TIBCO may request that you reproduce the problem on a supported version of the browser. This may mean that you potentially change to a different version that does not exhibit the issue; ideally only on a temporary basis.


Third-party Software Requirements | 21

Openspace and Workspace

TIBCO ActiveMatrix Administrator (GUI)

Browser Supported versions Notes

Internet Explorer

7 • Google Chrome Frame plug-in version 21.0 or later must also be installed.

• The Openspace Spotfire gadget is not supported.

8 • Use of Google Chrome Frame plug-in is optional, but if used, must be version 21.0 or later.

9 • Use of Google Chrome Frame plug-in is optional, but if used, must be version 21.0 or later.

• Compatibility View is not supported.

Mozilla Firefox

3.6, 15.0 • Versions between 3.6 and 15.0 are not supported.

• The Openspace Spotfire gadget is not supported.

Safari 5 • The Openspace Spotfire, Organization Browser and Event Views gadgets are not supported.

• Openspace is not supported when running Safari on iOS4.

• Openspace - Mobile is only supported when running Safari on iOS4 or iOS5.

• Safari 5 can be used at runtime to access the Workspace client application, or custom applications created with TIBCO Workspace client components (WCC components). However, TIBCO General Interface Builder is not supported - Safari cannot be used at design-time to create applications created with WCC components.

Browser Supported versions Notes

Mozilla Firefox

3.6, 15.0 Versions between 3.6 and 15.0 are not supported.

Internet Explorer

8 With SP2



User Account Requirements

To install on Microsoft Windows or on UNIX, you must have the appropriate privileges.

The privileges differ for the different platforms.

Microsoft WindowsYou must have administrator privileges for the machine on which this product is installed. If you do not have administrator privileges, the installer exits. You must then log out of the system and log in as a user with the required privileges, or request your system administrator to assign the privileges to your account.

If you intend to install the product on a network drive, ensure that the account used for installation has permission to access the network drive.

UNIX or LinuxAny type of user (regular (non-root) user or super-user (root)) can install this product. While installing this product on UNIX platforms, ensure that the same installer account is used to install all TIBCO ActiveMatrix products.

A graphic environment such as CDE or X Windows is required to run the installer in GUI mode.


Additional System Requirements for a High Availability or Distributed BPM Configuration | 23

Additional System Requirements for a High Availability or Distributed BPM Configuration

The following table lists additional architectural requirements for a highly available or distributed ActiveMatrix BPM system.

Requirement Description

Primary and remote machines:

The primary machine hosts an ActiveMatrix BPM node (of type BPM) and an ActiveMatrix Administrator server instance. In:

• a high availability configuration: a second primary machine hosts a second ActiveMatrix BPM node (of node type BPM) and a replicated ActiveMatrix Administrator server instance.

• a distributed configuration: each remote node hosts one or more additional ActiveMatrix BPM nodes of the desired node types.

Load Balancer Manages HTTP requests from ActiveMatrix BPM clients across the primary and remote machines.

Shared File System Holds shared configuration data used by ActiveMatrix BPM and/or ActiveMatrix Administrator.

LDAP Server Must be external. Do not use the internal LDAP server supplied with ActiveMatrix BPM.

The load balancer, shared file system, database server, LDAP server, SMTP server (if used) and TIBCO Enterprise Message Service server must each be available to both the primary and remote machines.

For a high availability configuration, they must also each be configured to provide high availability and fault tolerance.



Load BalancerThe load balancer must be configured as follows:

• The following ports must be configured for load balancing across the primary and remote machines:

— ActiveMatrix Administrator external HTTP port (default 8120) - used for communication between ActiveMatrix Administrator and external web/CLI clients and Business Studio.

— ActiveMatrix Administrator internal HTTP port (default 19767) - used for communication between ActiveMatrix Administrator and hosts/nodes.

— ActiveMatrix BPM HTTP port (default 8080) - used for communication between ActiveMatrix BPM and external clients (Openspace, Workspace and custom clients).

• Sticky connections should be used so that client session context is maintained. (If the server hosting this session dies the client will be logged out and need to log back in again.)

For a high availability configuration, where the Administrator server is replicated on two machines, you should use an HTTP load balancer so that traffic between hosts and Administrator will support a load-balanced and fault-tolerant mode. Without a load balancer, if one Administrator is unavailable, hosts and nodes will not be able to download software artifacts.



Shared File SystemThe shared file system must:

• be available to the primary machine and each remote machine.

• be mounted in an identical location on each machine.

• contain the folders shown in the following table (where SHARED_DIR is the root folder of the shared file system).

Folder1 Notes

SHARED_DIR\amx_work\shared Shared work folder used by ActiveMatrix Administrator.

Note: This folder is only required for a high availability configuration, where the Administrator server is replicated on two machines.

When configuring the ActiveMatrix Administrator on the primary machine, use this location for the sharedWorkFolder attribute of the AdminConfigFolders element in the integration_create_admin_data.xml script - see Task 3: Primary Machine - Create a BPM Node and Administrator Server.

SHARED_DIR\amx_work\shared\repo

Shared work folder used by ActiveMatrix Administrator.

Note: This folder is only required for a high availability configuration, where the Administrator server is replicated on two machines.

When configuring the ActiveMatrix Administrator on the primary machine, use this location for the location attribute of the SCMDetails element in the integration_create_admin_data.xml script - see Task 3: Primary Machine - Create a BPM Node and Administrator Server

SHARED_DIR\bpm_config Shared configuration folder in which ActiveMatrix BPM stores BPM properties files.

Use this location when configuring ActiveMatrix BPM on:

• the primary node - see ActiveMatrix BPM: Configuration

• a remote node - see ActiveMatrix BPM: Host and Node Configuration



SHARED_DIR\keystores Shared authentication folder in which ActiveMatrix BPM stores keystores (or trust stores) used for SSL and/or WSS authentication. This folder is created automatically if you select Override BPM Configuration Folder in the ActiveMatrix BPM: Configuration screen of the Create TIBCO ActiveMatrix BPM Server Wizard.

To ensure that authentication operates correctly, you must:

1. store any keystores needed for SSL or WSS authentication in this folder.

2. reference this folder as the location of any keystores as required, either:

— from TIBCO Configuration Tool dialogs (for example, when defining SSL connections)

— when configuring a Keystore Provider resource template in TIBCO Administrator.

See TIBCO ActiveMatrix BPM - BPM Administration, for more information about enabling SSL and configuring TIBCO ActiveMatrix BPM to use SSO for authentication.

1. amx_work and bpm_config are suggested names for these folders. However, you can use any namesthat you wish for these folders.

Folder1 Notes

The following user accounts must have at least read/write permissions to these folders:

• the account used to install ActiveMatrix BPM.

• any accounts that will be used to run ActiveMatrix BPM (specifically the tibcohost process).



Server Time SynchronizationThe primary and remote machines must have their time/date synchronized with each other. If server times are offset (even by a few seconds), the ActiveMatrix BPM node log file:

CONFIG_HOME\tibcohost\Admin-enterpriseName-adminServerName\nodes\nodeName\logs\BPM.log

may show significant numbers of errors like the following:

05 Jun 2011 14:12:02,465 [QuartzScheduler_PVM:Quartz Scheduler-LINAramis1307296618457_ClusterManager] [WARN ] com.tibco.pvm.persist.quartz.jdbcjobstore.IpmQuartzJobStoreTX - This scheduler instance (LINAramis1307296618457) is still active but was recovered by another instance in the cluster. This may cause inconsistent behavior

25 Jan 2012 01:33:48,698 [QuartzScheduler_PVM:Quartz Scheduler-mjkmssqlbe1327088686491_ClusterManager] [INFO ] com.tibco.pvm.persist.quartz.jdbcjobstore.IpmQuartzJobStoreTX - ClusterManager: Scanning for instance "threemjkv121327089184017"'s failed in-progress jobs.

25 Jan 2012 01:33:56,200 [QuartzScheduler_PVM:Quartz Scheduler-mjkmssqlbe1327088686491_ClusterManager] [INFO ] com.tibco.pvm.persist.quartz.jdbcjobstore.IpmQuartzJobStoreTX - ClusterManager: detected 1 failed or restarted instances.

30 Jan 2012 09:43:38,067 [QuartzScheduler_PVM:Quartz Scheduler-twomjkv121327596401015_ClusterManager] [WARN ] com.tibco.pvm.persist.quartz.jdbcjobstore.IpmQuartzJobStoreTX - This scheduler instance (twomjkv121327596401015) is still active but was recovered by another instance in the cluster. This may cause inconsistent behavior.


| 29

I - INSTALLATION AND UPGRADE SCENARIOS

The following chapters describe the most common ActiveMatrix BPM installation/upgrade scenarios, and provide high-level procedures for how to implement them.

Topics

• Installing and Configuring a Basic ActiveMatrix BPM System, page 31

• Installing and Configuring a High Availability, Fault Tolerant ActiveMatrix BPM System, page 37

• Installing and Configuring a Distributed ActiveMatrix BPM System, page 51

• Upgrading an ActiveMatrix BPM System, page 63


30 | I - INSTALLATION AND UPGRADE SCENARIOS


| 31

Chapter 3 Installing and Configuring a Basic ActiveMatrix BPM System

This chapter describes how to install and configure a BPM system using a basic configuration (with all components installed on a single machine).

Topics

• Overview, page 32

• Task1: Install ActiveMatrix BPM Software, page 34

• Task 2: Configure JDBC Drivers, page 35

• Task 3: Create a BPM Node and Administrator Server, page 36


32 | Chapter 3 Installing and Configuring a Basic ActiveMatrix BPM System

Overview

A basic configuration consists of a simple installation where ActiveMatrix BPM is installed on a single machine.

Figure 1 shows an example of a basic ActiveMatrix BPM configuration. Note that:

• ActiveMatrix BPM and the ActiveMatrix Administrator Server instance are both hosted on the same machine.

• The ActiveMatrix BPM database and ActiveMatrix Administrator database are hosted in the same database server. They can be hosted in different databases and/or on different machines.

• TIBCO Enterprise Message Service is installed on a separate machine. It can be installed on the same machine as ActiveMatrix BPM.

The basic configuration is intended for proof-of-concept, testing and validation or demonstration purposes. It is not intended for use in a production environment and TIBCO recommend that you do not use it in a production environment.


Overview | 33

Figure 1 ActiveMatrix BPM basic configuration



Task1: Install ActiveMatrix BPM Software

1. Perform all required pre-installation tasks. (See Preparing for Installation or Upgrade.)

2. Log on to the primary machine.

3. Run TIBCOUniversalInstaller to install ActiveMatrix BPM software. (See Installing ActiveMatrix BPM Software (TIBCO Universal Installer).)

4. Make sure that you complete the following screens/fields as shown.

See Installing ActiveMatrix BPM Software (TIBCO Universal Installer) for full details of the data you need to enter in this wizard.

Screen Requirement

Installation Profile Selection

Select the Primary machine profile.

TIBCO Installation Home

Select Create a new TIBCO_HOME.

Post-Install summary Select Launch TIBCO Configuration Tool.


Task 2: Configure JDBC Drivers | 35

Task 2: Configure JDBC Drivers

1. Make sure that the jar files for the required JDBC drivers are available on the primary machine. (See JDBC Drivers on page 19.)

2. In TIBCO Configuration Tool, choose the Configure Third-Party Driver Wizard.

3. Configure the JDBC driver needed for the database server that will be used to host the ActiveMatrix BPM database. This must be one of the following drivers:

— TIBCO enabled JDBC driver for Microsoft SQL Server 3.0

— TIBCO enabled JDBC driver for Oracle 11.1.0

— TIBCO enabled JDBC driver for IBM DB2 4.12.55

4. If a different database server will be used to host the Administrator database, configure the JDBC driver for that database server as well.

5. Return to the Create new configurations screen, but do not close TIBCO Configuration Tool.



Task 3: Create a BPM Node and Administrator Server

1. In TIBCO Configuration Tool, choose the Create TIBCO ActiveMatrix BPM Server Wizard.


See Create TIBCO ActiveMatrix BPM Server Wizard and Create TIBCO ActiveMatrix Administrator Server Wizard for full details of the data you need to enter in this wizard.

A BPM node and Administrator server are started on the host machine.

4. Perform any required post-installation tasks. See Post-Installation Tasks.

Screen Requirement

ActiveMatrix BPM: Database Administrator

Enter the details of the database server that will be used to host the ActiveMatrix BPM database. See Configure the ActiveMatrix BPM Database Server.

ActiveMatrix BPM: Runtime Database Configuration

Enter the details of the ActiveMatrix BPM database.

ActiveMatrix BPM: Configuration

Make sure that Override BPM Configuration Folder is cleared.

ActiveMatrix BPM: Administrator Server Configuration

Clear Use Existing ActiveMatrix Administrator Server.

When you click Next, the Administrator Server Configuration: Details screen is displayed. This wizard allows you to configure the ActiveMatrix Administrator server.

Administrator Server Configuration: Summary

1. Make sure that Create TIBCO ActiveMatrix Administrator server and Create ActiveMatrix BPM are selected.

2. If you chose to manually create the ActiveMatrix BPM database, make sure that the database administrator has run the database creation scripts and that TIBCO Configuration Tool can successfully connect to the database before you click Configure from this screen. See Manually Running the ActiveMatrix BPM Database Creation Scripts on page 104 for more information.

3. Click Configure.


| 37

Chapter 4 Installing and Configuring a High Availability, Fault Tolerant ActiveMatrix BPM System

This chapter describes how to configure a TIBCO ActiveMatrix BPM system to provide high availability and fault tolerance.

Topics

• Overview

• Task 1: Primary Machine - Install ActiveMatrix BPM Software

• Task 2: Primary Machine - Configure JDBC Drivers

• Task 3: Primary Machine - Create a BPM Node and Administrator Server

• Task 4: Remote Machine - Install ActiveMatrix BPM Software

• Task 5: Remote Machine - Configure JDBC Drivers

• Task 6: Remote Machine - Create an Administrator Server

• Task 7: Remote Machine - Create a BPM Node


38 | Chapter 4 Installing and Configuring a High Availability, Fault Tolerant ActiveMatrix BPM System

Overview

ActiveMatrix BPM software provides active/active clustering capabilities. You can use these capabilities, along with a suitable underlying architecture, to configure an TIBCO ActiveMatrix BPM system to provide high availability and fault tolerance.

Figure 2 shows an example of such a configuration:

• ActiveMatrix Administrator and ActiveMatrix BPM run on both the primary and secondary machines in an active/active configuration.

• Underlying resources are available to both machines.

• In the event of a system-affecting failure on either the primary or secondary node, load is switched to the remaining machine.

• ActiveMatrix BPM and the ActiveMatrix Administrator Server instance are both hosted on the same machine. They can be hosted on different machines.

• The ActiveMatrix BPM database and ActiveMatrix Administrator database are hosted in the same database server. They can be hosted in different databases, database types and/or on different machines.


Overview | 39

Figure 2 ActiveMatrix BPM High Availability Configuration



Task 1: Primary Machine - Install ActiveMatrix BPM Software






Screen Requirement







Task 2: Primary Machine - Configure JDBC Drivers | 41

Task 2: Primary Machine - Configure JDBC Drivers


2. Run TIBCO Configuration Tool.

3. Enter a local location for the TIBCO configuration folder (CONFIG_HOME), or click OK to use the default location.

4. Run the Configure Third-Party Driver Wizard.









Task 3: Primary Machine - Create a BPM Node and Administrator Server

Task A Generate Configuration Scripts



Screen Requirement





ActiveMatrix BPM: Configuration 1. Select Override BPM Configuration Folder.

2. In the Configuration Folder field, enter the location of the configuration folder on the shared file system. For example, SHARED_DIR\bpm_config - see Shared File System.

ActiveMatrix BPM: LDAP Configuration

If the LDAP server is SSL enabled, the Trust Store Location must be SHARED_DIR\keystores - see Shared File System.



Administrator Server Configuration: Internal HTTP Settings

Select Use Load Balancer for Internal HTTP Communication and enter the Load Balancer URL. See Load Balancer.

Administrator Server Configuration: Database Details

Enter the details of the database server that hosts the Administrator database, making sure that the Database URL field contains a DNS name. See Configure an External ActiveMatrix Administrator Database.

Administrator Server Configuration: Credential Server Details

Ensure that Bind to Network Adapter is set to 0.0.0.0.


Task 3: Primary Machine - Create a BPM Node and Administrator Server | 43

See Create TIBCO ActiveMatrix BPM Server Wizard for full details of the data you need to enter in this wizard.

Task B Edit the Generated Configuration Scripts

1. Using a text editor, open the file:

CONFIG_HOME\tct\bpm\timestamp\scripts\integration_create_admin_data.xml.

2. Set the sharedWorkFolder attribute of the AdminConfigFolders element to a folder in the shared file system. The path must end in "\shared" - for example, SHARED_DIR\amx_work\shared - see Shared File System.

3. Set the location attribute of the SCMDetails element to a different folder in the shared file system. The path must end in "\shared\repo" - for example, SHARED_DIR\amx_work\shared\repo.

4. Set the value of the Svar element named ArtifactServerInternalSharedLocationSvar to the same value as the sharedWorkFolder attribute - for example, SHARED_DIR\amx_work\shared.

5. Save the file.

Task C Run the Configuration Scripts

1. If you chose to manually create the ActiveMatrix BPM database when you created the configuration scripts, make sure that the database administrator has run the database creation scripts before continuing. See Manually Running the ActiveMatrix BPM Database Creation Scripts for more information.

2. Open a command window and navigate to:

TIBCO_HOME\bpm\version\scripts\silent



2. Click Save to save the configuration details to the Session Scripts and Log Folder (by default, CONFIG_HOME\tct\bpm\timestamp\scripts).

3. Click Cancel.

Note: Do not click Configure from this screen.

Screen Requirement



where version is the version of BPM that you are installing and configuring - for example, 2.0.

3. Run the command:

silentinstall bpm tct_output_folder

where tct_output_folder is the location of the configuration scripts you created earlier - in this example, CONFIG_HOME\tct\bpm\timestamp\scripts.

A BPM node and Administrator server are started on the host machine.


Task 4: Remote Machine - Install ActiveMatrix BPM Software | 45

Task 4: Remote Machine - Install ActiveMatrix BPM Software

1. Perform any required pre-installation tasks that are needed for the remote machine. (See Preparing for Installation or Upgrade.)

2. Log on to the remote machine.




Screen Requirement



TIBCO Installation Home 1. Select Create a new TIBCO_HOME.

2. Enter a location that is identical to the value of TIBCO_HOME on the primary machine. For example, if the location of TIBCO_HOME on the primary machine is C:\tibco\amx-bpm, the location of TIBCO_HOME on the secondary machine must also be C:\tibco\amx-bpm.




Task 5: Remote Machine - Configure JDBC Drivers

1. Make sure that the jar files for the required JDBC drivers are available on the remote machine. (See JDBC Drivers on page 19.)

2. Run TIBCO Configuration Tool.

3. Enter an identical location for the TIBCO configuration folder (CONFIG_HOME) to the one that you used on the primary machine. (See Task 2: Primary Machine - Configure JDBC Drivers.)

4. Run the Configure Third-Party Driver Wizard.

5. Configure the JDBC driver needed for the database server that will be used to host the ActiveMatrix Administrator database.

6. Return to the Create new configurations screen, but do not close TIBCO Configuration Tool. (You will use it again in Task 7: Remote Machine - Create a BPM Node.)


Task 6: Remote Machine - Create an Administrator Server | 47

Task 6: Remote Machine - Create an Administrator Server

Task A Copy Configuration Scripts From the Primary Machine

Copy the entire contents of the CONFIG_HOME\tct\bpm\date-time\scripts folder from the primary machine to the same location on the secondary machine.

Task B Edit the Generated Configuration Scripts

1. In TIBCO_HOME\administrator\n.n\scripts\instance-mgmt.xml, remove the configure.tcs and start.tcs targets from the deploy-admin target's depends attribute, To do this, replace the following line:

<target name="deploy-admin" depends="-define-macros, create-dir-structure, bootstrap.admin.archive.th, configure.tcs, start.tcs, updateCallbackUrlTrustConfig, create.admin.cli.keystore, install.artifact.server, deploy.admin.ui.dashboard"/>

with

<target name="deploy-admin" depends="-define-macros, create-dir-structure, bootstrap.admin.archive.th, updateCallbackUrlTrustConfig, create.admin.cli.keystore, install.artifact.server, deploy.admin.ui.dashboard"/>

2. In TIBCO_HOME\administrator\n.n\scripts\governance/governance_integration_build.xml, remove the target add.factory.aggregator.config from the setup target’s depends attribute.

3. Edit the following files in the CONFIG_HOME\tct\bpm\date-time\scripts folder:

TIBCO recommend that you create an additional backup copy of this folder in case you need to use it when recovering from configuration errors during the replication process.

File Required changes

admin-envt-data.xml Comment out the Environment element.

admin-instance.properties Update the adminURL property with the host name of the replicated instance.



Task C Run the Configuration Scripts

1. Open a command window and navigate to:

TIBCO_HOME\bpm\version\scripts\silent

where version is the version of BPM that you are installing and configuring - for example, 2.0.

2. Run the command:

silentinstall admin tct_output_folder

where tct_output_folder is the location of the configuration scripts you have just edited- in this example, CONFIG_HOME\tct\bpm\timestamp\scripts.

A TIBCO Host instance with the specified name is created and started. A node with the specified name is created in the environment named SystemEnvironment and started. The replicated Administrator server runs on the specified node.

For example, in Figure 2, a TIBCO Host instance named SystemHost2 is created and started. A node named SystemNode2 is created in the environment named SystemEnvironment and started. The replicated Administrator server runs on SystemNode2.

When you log in to either of the Administrator servers there will be two hosts in the Infrastructure > Hosts screen and two nodes in the SystemEnvironment environment in the Infrastructure > Nodes screen. Requests can be processed by either Administrator server. If one node is unavailable, the other will be able to process requests.

build.properties Update the th.jmx.host and th.jmx.url properties with the host name of the replicated instance. Ensure that the tcs.host property is set to 0.0.0.0.

All files in this folder In each file:

1. Replace all instances of SystemNode with another node name (for example, SystemNode2).

2. Replace all instances of SystemHost with another host name (for example, SystemHost2).

File Required changes

In case of configuration errors during the replication process, you have to first delete the replicated TIBCO ActiveMatrix Administrator server instance before re-trying the replication process.


Task 7: Remote Machine - Create a BPM Node | 49

Task 7: Remote Machine - Create a BPM Node

1. In TIBCO Configuration Tool, run the Configure TIBCO ActiveMatrix BPM Server Node Type Wizard.


See Configure TIBCO ActiveMatrix BPM Server Node Type Wizard for full details of the data you need to enter in this wizard.

Screen Requirement

ActiveMatrix BPM Node Type: Administrator Server Configuration

Specify the details of the Administrator server being used by the existing BPM node.

ActiveMatrix BPM Node Type: Host and Node Configuration

1. Node Type: Select BPM Node Type.

2. Node Name: Enter a unique name for the node (for example, in Figure 2, BPMNode2).

3. Node Port: Enter a unique port number.

4. Host: Enter the name of the host that is running on this machine (for example, in Figure 2, SystemHost2).

5. HTTP Port: Enter a unique port number.

6. Environment Name: Enter the name of the BPM environment that contains the existing BPM node (for example, in Figure 2, BPMEnvironment).

7. Override BPM Configuration Folder: Select this.

8. Configuration Folder: Enter the location of the configuration folder on the shared file system. For example, SHARED_DIR\bpm_config - see Shared File System.

ActiveMatrix BPM Node Type: Summary 1. Select Create new ActiveMatrix BPM Server

Node Type.

2. Click Configure.



A BPM node is started on the specified host, and the BPM environment extended to include the new node.

For example, in Figure 2, BPMNode2 is started on RemoteHost2 on the secondary machine. The BPMEnvironment is extended to include BPMNode2.

3. Close TIBCO Configuration Tool.

4. Distribute the BPM application to the new node. See Distributing the ActiveMatrix BPM Application in a High Availability, Fault Tolerant BPM System for more information about how to do this.


| 51

Chapter 5 Installing and Configuring a Distributed ActiveMatrix BPM System

This chapter describes how to configure an TIBCO ActiveMatrix BPM system to provide horizontal scalability.

Topics

• Overview

• Task 1: Primary Machine - Install ActiveMatrix BPM Software

• Task 2: Primary Machine - Configure JDBC Drivers

• Task 3: Primary Machine - Create a BPM Node and Administrator Server

• Task 4: Remote Machine - Install ActiveMatrix BPM Software

• Task 5: Remote Machine - Create a TIBCO Host

• Task 6: Remote Machine - Create a Node of the Required Type


52 | Chapter 5 Installing and Configuring a Distributed ActiveMatrix BPM System

Overview

ActiveMatrix BPM software provides specialization and horizontal scalability capabilities. You can use these capabilities, along with a suitable underlying architecture, to distribute ActiveMatrix BPM logical nodes to different physical nodes.

Figure 3 shows an example of such a configuration. Note that:

• Underlying resources are available to both machines.

• ActiveMatrix BPM and the ActiveMatrix Administrator Server instance are both hosted on the same machine. They can be hosted on different machines.

• The ActiveMatrix BPM database and ActiveMatrix Administrator database are hosted in the same database server. They can be hosted in different databases and/or on different machines.

See "TIBCO ActiveMatrix BPM Architecture" in TIBCO ActiveMatrix BPM Concepts for more information about the different types of logical node and their use.

If ActiveMatrix BPM and the ActiveMatrix Administrator Server instance are hosted on different machines:

— the machine hosting the ActiveMatrix Administrator Server instance is the primary machine.

— the machine hosting ActiveMatrix BPM is a remote machine.


Overview | 53

Figure 3 ActiveMatrix BPM Distributed Configuration









Screen Requirement







Task 2: Primary Machine - Configure JDBC Drivers | 55

Task 2: Primary Machine - Configure JDBC Drivers


2. In TIBCO Configuration Tool, choose the Configure Third-Party Driver Wizard.









Task 3: Primary Machine - Create a BPM Node and Administrator Server



Screen Requirement





ActiveMatrix BPM: Configuration 1. Select Override BPM Configuration Folder.

2. In the Configuration Folder field, enter the location of the configuration folder on the shared file system. For example, SHARED_DIR\bpm_config - see Shared File System.


If the LDAP server is SSL enabled, the Trust Store Location must be SHARED_DIR\keystores - see Shared File System.




Enter the details of the database server that hosts the Administrator database, making sure that the Database URL field contains a DNS name. See Configure an External ActiveMatrix Administrator Database.


Ensure that Bind to Network Adapter is set to 0.0.0.0.


Task 3: Primary Machine - Create a BPM Node and Administrator Server | 57

See Create TIBCO ActiveMatrix BPM Server Wizard for full details of the data you need to enter in this wizard.

A BPM node and Administrator server are started on the host machine. See Figure 3.



2. If you chose to manually create the ActiveMatrix BPM database, make sure that the database administrator has run the database creation scripts and that TIBCO Configuration Tool can successfully connect to the database before you click Configure from this screen. See Manually Running the ActiveMatrix BPM Database Creation Scripts on page 104 for more information.

3. Click Configure.

Screen Requirement




1. Perform any required pre-installation tasks that are needed for the remote machine. (See Preparing for Installation or Upgrade.)





Screen Requirement


Select the Remote machine profile.





Task 5: Remote Machine - Create a TIBCO Host | 59

Task 5: Remote Machine - Create a TIBCO Host

1. In TIBCO Configuration Tool, choose the Create TIBCO Host Instance Wizard.


See Create TIBCO Host Instance Wizard for full details of the data you need to enter in this wizard.

A TIBCO Host instance is started on the remote machine and bound to the Administrator server on the primary machine. See Figure 3.


Screen Requirement

TIBCO Host instance Configuration: Details

Enterprise Name: Specify the name that you used when creating the Administrator server on the primary machine (in Administrator Server Configuration: Details).

TIBCO Host instance Configuration: Notification Server

Specify the details of the TIBCO Enterprise Message Service server.

TIBCO Host instance Configuration: Administrator Server

Select Bind to Administrator Server and specify the details of the Administrator server that you created on the primary machine.

Note: If the Administrator server is SSL enabled, the Trust Store Location must be SHARED_DIR\keystores - see Shared File System.

TIBCO Host Instance Configuration: Summary

Select:

• Create TIBCO Host instance

• Launch TIBCO Host instance

• Register TIBCO Host instance to the Administrator server



Task 6: Remote Machine - Create a Node of the Required Type

1. In TIBCO Configuration Tool, run the Configure TIBCO ActiveMatrix BPM Server Node Type Wizard.


Screen Requirement


Specify the details of the Administrator server being used by the existing BPM node.


1. Node Type: Select the appropriate logical node type that you want to create (for example, in Figure 3, Work Manager Node Type.)

2. Node Name: Enter a unique name for the node (for example, in Figure 3, BPMNode2).

3. Node Port: Enter a unique port number.

4. Host: Enter the name of the host that is running on the secondary machine (for example, in Figure 3, RemoteHost2).

5. HTTP Port: Enter a unique port number.

6. Environment Name: Enter the name of the BPM environment that contains the existing BPM node (for example, in Figure 3, BPMEnvironment).

7. Override BPM Configuration Folder: Select this.

8. Configuration Folder: Enter the location of the configuration folder on the shared file system. For example, SHARED_DIR\bpm_config - see Shared File System.

ActiveMatrix BPM Node Type: Summary 1. Select Create new ActiveMatrix BPM Server

Node Type.

2. Click Configure.


Task 6: Remote Machine - Create a Node of the Required Type | 61

See Configure TIBCO ActiveMatrix BPM Server Node Type Wizard for full details of the data you need to enter in this wizard.

A BPM node (of type Work Manager) is started on the specified host, and the BPM environment extended to include the new node.

For example, in Figure 3, BPMNode2 is started on RemoteHost2 on the remote machine. The BPMEnvironment is extended to include BPMNode2.

3. Close TIBCO Configuration Tool.

4. Distribute the BPM application to the new node. See Distributing the ActiveMatrix BPM Application in a Distributed BPM System for more information about how to do this.


| 63

Chapter 6 Upgrading an ActiveMatrix BPM System

This chapter describes how to upgrade an ActiveMatrix BPM system (basic, distributed or high availability, fault tolerant).

Topics


• Task 1: Remote Machine - Install ActiveMatrix BPM Software, page 65

• Task 2: Remote Machine - Upgrade the TIBCO Host Instance, page 66

• Task 3: Primary Machine - Install ActiveMatrix BPM Software, page 67

• Task 4: Primary Machine - Upgrade ActiveMatrix BPM

• Task 5: Post-Upgrade Tasks


64 | Chapter 6 Upgrading an ActiveMatrix BPM System

Overview

You can upgrade to this version of TIBCO ActiveMatrix BPM from an existing installation of any earlier version of TIBCO ActiveMatrix BPM.

Make sure that you have performed all necessary pre-installation and pre-upgrade tasks before upgrading - see Preparing for Installation or Upgrade.

If you are upgrading:

• a distributed or high availability, fault-tolerant system, you must start by upgrading each remote machine - go to Task 1: Remote Machine - Install ActiveMatrix BPM Software.

• a basic system that is installed on a single machine, skip the remote machine tasks and go to Task 3: Primary Machine - Install ActiveMatrix BPM Software instead.

IMPORTANT: Do NOT attempt to upgrade an existing BPM system that uses a replicated ActiveMatrix Administrator instance (for example, as shown in Figure 2 on page 39).

Contact TIBCO Support for assistance in this situation.

IMPORTANT: You cannot use the TIBCO ActiveMatrix BPM Upgrade utility to upgrade your BPM system if, when installing it, you created the ActiveMatrix Administrator server using the Create TIBCO ActiveMatrix Administrator Server Wizard.

Contact TIBCO Support for assistance in this situation.

If you are unsure about the exact upgrade sequence to follow for your particular installation, contact TIBCO Support for advice before upgrading.


Task 1: Remote Machine - Install ActiveMatrix BPM Software | 65



2. Stop the TIBCO Host instance. For example, using the command:

CONFIG_HOME\tibcohost\Admin-enterpriseName-adminServerName\host\bin\tibcohost.exe stop -wait true

See "Stopping a TIBCO Host Instance" in TIBCO ActiveMatrix BPM - SOA Administration for more information.




Screen Requirement


Select the Remote machine profile.

TIBCO Installation Home 1. Select Use an existing TIBCO_HOME.

2. Select the TIBCO_HOME location used by the existing installation.

Warning dialog If a Warning dialog appears, prompting you to re-install any existing features, click NO.

Post-Install summary Clear Launch TIBCO Configuration Tool.



Task 2: Remote Machine - Upgrade the TIBCO Host Instance

1. Open a command window and navigate to the location of the upgrade utility:

TIBCO_HOME\bpm\n.n\scripts\upgrade

2. Run the following upgrade utility command:

upgrade tibcohost tct_output_folder

where tct_output_folder is the full pathname of the folder that contains the scripts generated by TIBCO Configuration Tool when you originally installed ActiveMatrix BPM. For example:

CONFIG_HOME\tct\bpm\date-time\scripts

3. Follow the prompts displayed by the utility to upgrade the TIBCO Host instance. See Running the Upgrade Utility for more information.

The upgrade process restarts the TIBCO Host instance when it has finished.

4. Repeat Task 1: Remote Machine - Install ActiveMatrix BPM Software and Task 2: Remote Machine - Upgrade the TIBCO Host Instance on each remote machine that is part of the ActiveMatrix BPM system.

Do not move on to upgrade the primary machine until you have upgraded every remote machine.


Task 3: Primary Machine - Install ActiveMatrix BPM Software | 67




3. Stop the TIBCO Host instance. For example, using the command:

CONFIG_HOME\tibcohost\Admin-enterpriseName-adminServerName\host\bin\tibcohost.exe stop -wait true

See "Stopping a TIBCO Host Instance" in TIBCO ActiveMatrix BPM - SOA Administration for more information.



Screen Requirement



TIBCO Installation Home 1. Select Use an existing TIBCO_HOME.

2. Select the TIBCO_HOME location used by the existing installation.

Warning dialog If a Warning dialog appears, prompting you to re-install any existing features, click NO.

Post-Install summary Clear Launch TIBCO Configuration Tool.



Task 4: Primary Machine - Upgrade ActiveMatrix BPM




upgrade all tct_output_folder



3. Follow the prompts displayed by the utility to upgrade the ActiveMatrix BPM system. See Running the Upgrade Utility for more information.

The upgrade process restarts ActiveMatrix BPM when it has finished.


Task 5: Post-Upgrade Tasks | 69

Task 5: Post-Upgrade Tasks

1. Run the nodeutil utility to identify and (if necessary) fix any missing application dependencies. See "Missing Application Dependencies" in ActiveMatrix BPM Troubleshooting for detailed information on how to do this.

2. On each machine that is part of the BPM system:

a. Using a text editor, open the following file:

CONFIG_HOME\tibcohost\Admin-AMX BPM-AMX BPM Server\nodes\BPMNode\bin\tibamx_BPMNode.tra

b. Remove the following entry from the java.extended.properties:

-Dcom.tibco.amf.sharedresource.runtime.core.sv.ems.

factory.MessageSenderPool.size=-1

c. Save the file.


| 71

II - INSTALLATION AND UPGRADE PROCEDURES

The following chapters provide detailed information about specific installation and upgrade procedures. Which of these you need to use will depend upon your particular installation/upgrade scenario.

Topics

• Preparing for Installation or Upgrade, page 73

• Installing ActiveMatrix BPM Software (TIBCO Universal Installer), page 91

• Post-Installation Tasks, page 119

• Configuring ActiveMatrix BPM Runtime Objects (TIBCO Configuration Tool), page 101

• Upgrading ActiveMatrix BPM Runtime Objects (Upgrade Utility), page 127


72 | II - INSTALLATION AND UPGRADE PROCEDURES


| 73

Chapter 7 Preparing for Installation or Upgrade

This chapter describes the tasks you may need to do before installing or upgrading.

Topics

• Check For Any Late Breaking Information, page 74

• Check the System Requirements, page 75

• Configure TIBCO Enterprise Message Service, page 76

• Configure an External ActiveMatrix Administrator Database, page 77

• Configure the ActiveMatrix BPM Database Server, page 79

• Configure the External LDAP Directory Server, page 82

• Configure the Maximum Number of Open Files, page 83

• Configure Apache Ant, page 84

• Download Required Software Assemblies, page 85

• Download ActiveMatrix BPM Software on page 86

• Pre-Upgrade Tasks, page 87

The tasks you need to perform vary according to your installation/upgrade scenario.

Use the information in this chapter in the context of your particular installation/upgrade scenario. See I - INSTALLATION AND UPGRADE SCENARIOS.


74 | Chapter 7 Preparing for Installation or Upgrade

Check For Any Late Breaking Information

Check if there any restrictions, known issues or other late-breaking information that may affect your installation, but that were not known about when this guide was published.

Procedure1. Read the Release Notes and Readme documents for this version of the

ActiveMatrix BPM software.

These documents are available from:

— the TIBCO Software Product Download Site (https://download.tibco.com/tibco/), in Products Home > TIBCO ActiveMatrix BPM-version > TIBCO ActiveMatrix BPM Software version.

— the TIBCO Product Documentation site (https://docs.tibco.com/), in Business Process Management > BPM in the Enterprise > TIBCO ActiveMatrix BPM. Select the appropriate Versions tab.

2. Consult the "Late Breaking News > Current News" section of the TIBCO Support Web (at https://support.tibco.com).

If you are upgrading, pay particular attention to the "Migration Issues" section in the Release Notes.



https://docs.tibco.com/


Check the System Requirements | 75

Check the System Requirements

Make sure that your environment meets all the requirements described in Installation Requirements on page 9.



Configure TIBCO Enterprise Message Service

If TIBCO Enterprise Message Service is currently:

• not installed, you must install it before you install ActiveMatrix BPM.

• installed, you may need to upgrade it before you install or upgrade ActiveMatrix BPM. See the ActiveMatrix BPM Readme to see which versions of TIBCO Enterprise Message Service are supported.

Procedure1. If necessary, install or upgrade TIBCO Enterprise Message Service according

to the instructions in the product’s Installation and Configuration guide.

2. If the TIBCO Enterprise Message Service server user does not have administrator privileges, reconfigure the server as described in Appendix G, TIBCO Enterprise Message Service Server Configuration.

3. Make sure that the TIBCO Enterprise Message Service server is running.

4. Make sure that the clocks of all machines within the same enterprise are synchronized to within to 30 minutes of each other. (You can run an NTP synchronization daemon on each machine to achieve synchronization.)

5. If you intend to enable SSL communications, make sure that the TIBCO Enterprise Message Service server is enabled with SSL and configured with a certificate file that contains both the server and issuer certificates.

TIBCO Enterprise Message Service does not have to be installed on the same machine as TIBCO ActiveMatrix BPM. (You will specify the connection details needed to contact the EMS Server as part of the configuration process. See Administrator Server Configuration: Notification and Messaging Bus Server on page 167.)

On Windows, if you manually start the TIBCO Enterprise Message Service server, make sure that you use the same configuration files as the Windows service. Use the following command:

TIBCO_HOME/ems/version number/bin/tibemsd -configEMS_CONFIG_HOME/tibco/cfgmgmt/ems/data/tibemsd.conf

where EMS_CONFIG_HOME is the configuration directory for TIBCO Enterprise Message Service.


Configure an External ActiveMatrix Administrator Database | 77

Configure an External ActiveMatrix Administrator Database

Configure the external database that will be used by the ActiveMatrix Administrator server. You must do this unless you intend to use an existing ActiveMatrix Administrator server.

You will identify this database using the Database URL field in the Administrator Server Configuration: Database Details screen when you run the Create TIBCO ActiveMatrix BPM Server Wizard or Create TIBCO ActiveMatrix Administrator Server Wizard.

Procedure See:

• Configuring an External Microsoft SQL Server 2008 Database

• Configuring an External Oracle 11g Database

• Configuring an External DB2 Database

Configuring an External Microsoft SQL Server 2008 Database1. Create an empty database which will be used to hold the ActiveMatrix

Administrator database tables.

2. Enable snapshot isolation by setting the ALLOW_SNAPSHOT_ISOLATION ON database option - for example, by using the following statements:

ALTER DATABASE DatabaseName SET READ_COMMITTED_SNAPSHOT ON

3. Create a database user (or identify an existing one) for ActiveMatrix BPM to use to connect to the ActiveMatrix Administrator database - for example, sa. This user must:

— be a member of the db_owner database role.

— have the database assigned as their default database.

You will specify this user in the Username field of the Administrator Server Configuration: Database Details screen when you run the Create TIBCO ActiveMatrix BPM Server Wizard or Create TIBCO ActiveMatrix Administrator Server Wizard.

4. Ensure that the database is set to use case insensitive (CI) collation.

5. Make sure that the database is available.

The following procedures briefly describe what you need to do on the database server, but do not describe in detail how to perform each task. If necessary, you should work with your database administrator to perform these tasks.



Configuring an External Oracle 11g Database1. Create an empty database which will be used to hold the ActiveMatrix


2. Create a database user (or identify an existing one) for ActiveMatrix BPM to use to connect to the ActiveMatrix Administrator database. This user must:

— not possess "dba" privileges.

— have connect and resource privileges.

— be assigned to the default schema.

You will specify this user in the Username field of the Administrator Server Configuration: Database Details screen when you run the Create TIBCO ActiveMatrix BPM Server Wizard or Create TIBCO ActiveMatrix Administrator Server Wizard.


Configuring an External DB2 Database1. Create a new, empty database that will be used to hold the ActiveMatrix


2. Set the database page size to 32768.

3. Make sure that the DB2 cur_commit database configuration parameter is set to ON.

4. Create an operating system user account for ActiveMatrix BPM to use to connect to the ActiveMatrix Administrator database - for example, bpmuser. (Alternatively, you can identify an existing operating system account to use.)

You will specify this user in the Username field of the ActiveMatrix BPM: Runtime Database Configuration screen when you run the Create TIBCO ActiveMatrix BPM Server Wizard.


The ActiveMatrix BPM database and ActiveMatrix Administrator server database must use separate Oracle database users/schemas. Use of separate tablespaces is also advised.

The ActiveMatrix BPM database tables and ActiveMatrix Administrator server database tables must be stored in separate databases.


Configure the ActiveMatrix BPM Database Server | 79

Configure the ActiveMatrix BPM Database Server

Configure the external database server that will be used to store the ActiveMatrix BPM database.

Procedure See:

• Configuring Microsoft SQL Server 2008

• Configuring Oracle 11g

• Configuring DB2

Configuring Microsoft SQL Server 20081. Create a SQL Server instance that will be used to hold the ActiveMatrix BPM

database.

2. Configure the SQL Server instance to use mixed (Windows and SQL Server) authentication.

3. Enable the TCP/IP network protocol for the SQL Server instance. For example:

a. In SQL Server Configuration Manager, expand SQL Server Network Configuration.

b. Click Protocols for instance_name where instance_name is the name of the SQL Server instance.

c. Right-click TCP/IP and click Enable.

When you run the Create TIBCO ActiveMatrix BPM Server Wizard, TIBCO Configuration Tool will either create the BPM database for you, or generate the necessary scripts that a database administrator can use to create the database.

The following procedures briefly describe what you need to do on the database server, but do not describe in detail how to perform each task. If necessary, you should work with your database administrator to perform these tasks.

The ActiveMatrix BPM database and ActiveMatrix Administrator server database can, if desired, use the same SQL Server database instance.



4. Enable support for XA transactions. To do this:

a. Download and install the Microsoft SQL Server JDBC Driver. See JDBC Drivers on page 19 for details of supported versions.

b. Copy the extended stored procedure dll (sqljdbc_xa.dll) from the location where you installed the Microsoft SQL Server JDBC Driver to the SQL Server instance's Binn folder - for example, to C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn.

c. Run SQL Server 2008 Management Studio as an administrator of the SQL Server instance.

d. From the location where you installed the Microsoft SQL Server JDBC Driver, run the sqljdbc_n.n\enu\xa\xa_install.sql script against the master database, where n.n is the version number of the Microsoft SQL Server JDBC Driver you are using.

e. Click Control Panel > Administrative Tools.

f. Double-click Component Services.

g. Right-click Component Services > Computer > My Computer > Distributed Transaction > Local DTC and select Properties.

h. Click Security. Select Enable XA transactions.

5. Restart the SQL Server instance.

Configuring Oracle 11g1. Create an Oracle database instance that will be used to hold the ActiveMatrix

BPM database.

2. Set the OPEN_CURSORS initialization parameter to a value of 400 or greater.

3. Configure the Oracle database instance to use AL32UTF8 as the database character set.

4. Start the Oracle database instance.

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.

The ActiveMatrix BPM database and ActiveMatrix Administrator server database must use separate Oracle database users/schemas. Use of separate tablespaces is also advised.


Configure the ActiveMatrix BPM Database Server | 81

Configuring DB21. Create a new, empty database that will be used to hold the ActiveMatrix BPM

database tables.

You will specify this database name as part of the URL field in the ActiveMatrix BPM: Database Administrator and ActiveMatrix BPM: Runtime Database Configuration screens when you run the Create TIBCO ActiveMatrix BPM Server Wizard.

2. Set the database page size to 16384.

3. Make sure that the DB2 cur_commit database configuration parameter is set to ON.

4. Make sure that the SYSTOOLSPACE tablespace exists. If it does not, create it. Some BPM installation scripts require access to this tablespace.

5. Create an operating system user account for ActiveMatrix BPM to use to connect to the BPM database - for example, bpmuser. (Alternatively, you can identify an existing operating system account to use.)

You will specify this user in the Username field of the ActiveMatrix BPM: Runtime Database Configuration screen when you run the Create TIBCO ActiveMatrix BPM Server Wizard.

6. Start the database.

The ActiveMatrix BPM database tables and ActiveMatrix Administrator server database tables must use separate databases.



Configure the External LDAP Directory Server

If you have decided to use an external LDAP directory server (see LDAP Server on page 20), make sure that:

• the LDAP server is running.

• an LDAP directory on this server contains the user that you want to use as the tibco-admin user.

• the user that you want to use as the tibco-admin user has at least read access to the LDAP directory that you intend to use.

You will use this information in the ActiveMatrix BPM: LDAP Configuration screen when you run the Create TIBCO ActiveMatrix BPM Server Wizard.

This LDAP directory may also hold details of other LDAP users who may need to log in to ActiveMatrix BPM, but it does not have to. You can configure additional LDAP connections to other LDAP directories as a post-installation task - see Create Any Other Required LDAP Connections to LDAP Directories on page 120.


Configure the Maximum Number of Open Files | 83

Configure the Maximum Number of Open Files

The maximum number of open files/file descriptors that a user can open is controlled by the operating system. However, the default threshold on Linux systems is typically too low and has to be increased.

TIBCO recommend that you set the system-wide, hard limit to a value of at least 10000, on each machine that will be part of the ActiveMatrix BPM system.

You only need to do this if you are installing on a Linux or UNIX platform. See Supported Platforms.



Configure Apache Ant

Configure Apache Ant as follows:

1. Create an environment variable that points to TIBCO_HOME.

2. Open a command window.

3. Run the following commands:

On Windows

set JAVA_HOME=%TIBCO_HOME%\tibcojre\1.6.0set CLASSPATH=%TIBCO_HOME%\tools\lib\antpackage.jarset RUN_ANT="%JAVA_HOME%/bin/java" -XX:MaxPermSize=1024m -cp "%CLASSPATH%" org.apache.tools.ant.Mainset ANT_OPTS=-Xmx1024m -XX:MaxPermSize=1024m -Xms256

On UNIX/Linux

JAVA_HOME=$TIBCO_HOME/tibcojre64/1.6.0CLASSPATH=$TIBCO_HOME/tools/lib/antpackage.jarRUN_ANT="$JAVA_HOME/bin/java -XX:MaxPermSize=1024m -cp $CLASSPATH org.apache.tools.ant.Main"ANT_OPTS="-Xmx1024m -XX:MaxPermSize=1024m -Xms256"export JAVA_HOME RUN_ANT ANT_OPTS


Download Required Software Assemblies | 85

Download Required Software Assemblies

If the machine on which you will be running the ActiveMatrix BPM installer does not have internet access, you must download the following software assemblies before you install ActiveMatrix BPM:

• Hibernate

• Eclipse LGPL (only required if you are installing on a Linux or Solaris platform. See Supported Platforms.)

To do this:

1. Log in to the TIBCO Software Product Download Site (https://download.tibco.com/tibco/).

2. Navigate to Products Home > TIBCO ActiveMatrix BPM-version > TIBCO ActiveMatrix BPM Software version

3. Click Download for the Hibernate Installation Link:

TIB_assembly_tibco_com_tibco_tpcl_org_hibernate_feature_3.2.4.001_all html

4. Save the assembly_tibco_com_tibco_tpcl_org_hibernate_feature_3.2.400.001

.zip file to a temporary directory accessible to the machine on which you will be running the ActiveMatrix BPM installer.

5. If you are installing on a Linux or Solaris platform, click Download for the Eclipse LGPL assembly listed with the software for your chosen platform:

TIB_product_tibco_eclipse_lgpl_3.5.2.001_OSplatform.html

6. Save the product_tibco_eclipse_lgpl_3.5.2.001_OSplatform.zip file to a temporary directory accessible to the machine on which you will be running the ActiveMatrix BPM installer.




Download ActiveMatrix BPM Software

To obtain the TIBCO ActiveMatrix BPM software:

1. Log in to the TIBCO Software Product Download Site (https://download.tibco.com/tibco/).

2. Navigate to Products Home > TIBCO ActiveMatrix BPM-version > TIBCO ActiveMatrix BPM Software version

3. Click Download for the TIBCO ActiveMatrix BPM software package for your platform.

4. Extract the ActiveMatrix BPM archive file to a temporary, empty directory on the machine on which you intend to install ActiveMatrix BPM.

On a Linux system, open a terminal window and use the unzip command to unzip the file. Do not double-click the archive file to extract it - doing so may cause a problem if you try to launch TIBCO Configuration Tool after running the installer.



Pre-Upgrade Tasks | 87

Pre-Upgrade Tasks

If you are upgrading an existing ActiveMatrix BPM installation, perform the following additional tasks.

Backup the Existing ActiveMatrix BPM SystemA backup of your system ensures that a stable version of your system is available for use in case the running system runs into problems and gets corrupted. In such a case, you can restore your system using the backup to the last backed up stable state. Depending on the backup mechanism employed, there may be some amount of data loss.

Before taking a backup, ensure that the system is in a state where a back-up can be performed. This means that the system needs to be in a stable state, and either shutdown or offline as applicable.

Backing up your BPM runtime involves saving the following components or folders of your system:

• Installation folders on all the machines where TIBCO ActiveMatrix BPM has been installed. If you have a distributed or a HA-FT system, ensure that you repeat the process for all the machines in the cluster that have TIBCO ActiveMatrix BPM installed on them.

• TIBCO_HOME and CONFIG_HOME directories

• TIBCO ActiveMatrix BPM database

• TIBCO ActiveMatrix Administration server database

• TIBCO Enterprise Message Service (EMS) server

Ensure that you preserve the file timestamps when taking a backup. This is important when restoring from a backup because the file timestamps are used to decide the right order to recreate components.

If you are using a Workspace custom configuration, you may need to back up the TIBCO Workspace configuration files to ensure that the custom configuration is not lost when you upgrade the software. Also, if you are running a custom WCC application, you may need to repackage and redeploy your applications to pick up any changes in the upgraded software. See Backup Workspace for details.



Backup WorkspaceIf you are using a Workspace custom configuration, you may need to back up the TIBCO Workspace configuration files to ensure that the custom configuration is not lost when you upgrade the software. Also, if you are running a custom WCC application, you may need to repackage and redeploy your applications to pick up any changes in the upgraded software.

The procedure differs depending on whether you are using the default Workspace application or a custom WCC application, as outlined in the following sections.

Default Workspace Application on the Runtime Machine

When you choose to upgrade your software, the installer overwrites all the existing Workspace configuration files on the runtime machine. If you are using the default Workspace application, you need to back up files before running the installer to upgrade the software, as described:

• If you had made configuration changes to Workspace using the Configuration Administrator, these changes are saved in the database. Consequently, you need NOT back up any files. When you start Workspace after upgrading the software, it will read the configuration from the database.

• If you had made configuration changes by directly modifying files on the runtime machine (for example, config.xml, userAccess.xml, and so on), you must back up those files prior to running the installer. After completing the upgrade, replace the installed configuration files with the backed up configuration files.

Custom WCC Application on Your Development Machine

When you upgrade the software, the installer installs the design-time WCC software on your development machine. Upgrading the design-time WCC software will not affect any custom WCC applications that were previously developed. However, to pick up the changes available in the upgraded software, you need to perform the following tasks:

1. Create a new WAR file for your custom application.

2. Copy the WAR file to TIBCO Business Studio.

3. Create a DAA for the application.

4. Undeploy the previously deployed custom application using TIBCO Administrator.

5. Deploy the DAA created in Step 3. to the runtime node using TIBCO Administrator.


Pre-Upgrade Tasks | 89

See TIBCO Workspace Configuration and Customization for details on how to deploy a custom application.

Other ChecksEnsure that you check the following before upgrading TIBCO ActiveMatrix BPM:

• Installer account - The installer account used to perform an upgrade must have the appropriate privileges required for that platform. User Account Requirements on page 22 describes the installer account you should use when upgrading TIBCO ActiveMatrix BPM.

• Installer log file - The location of the upgrade log files. See Installer Log File on page 195 for details.

• Shutdown the existing TIBCO ActiveMatrix BPM server that you wish to upgrade.

• Remove any indexes added to the BPM database.

If you have added any indexes to your BPM database, these should be removed before you upgrade. This is because, as part of the upgrade, a new database schema is supplied that may include new indexes. If the new indexes have the same name as your original indexes, this could result in duplicate indexes which, in turn, would adversely effect the performance of TIBCO ActiveMatrix BPM.

• Optionally, back up your TIBCO Workspace configuration files. See Backup Workspace, page 88 for details.

• Back up your system. See Backup the Existing ActiveMatrix BPM System, page 87 for detailed instructions to back up your ActiveMatrix BPM system and restore the system from a backup.

To back up your ActiveMatrix BPM system, copy the following to a different location (possibly on a different machine):

It is important that you shutdown the existing TIBCO ActiveMatrix BPM before upgrading, otherwise the upgrade will fail.

Make sure that the following are in a state where a back-up can be performed. This means they should be either shutdown or offline, as applicable.



— the machine(s) where TIBCO ActiveMatrix BPM has been installed.

— the TIBCO_HOME and CONFIG_HOME directories for the TIBCO ActiveMatrix BPM installation. If the BPM configuration files are on a different location, you must back up these files as well.

— the TIBCO ActiveMatrix BPM database. You must back up all the databases that contain BRM, EC, WP, PVM, and DE database tables. Refer to the documentation supplied with your database for information on how to take a backup.

— the TIBCO ActiveMatrix Administrator server database. Refer to the documentation supplied with TIBCO ActiveMatrix Administrator for information on how to do this.

— the TIBCO EMS server. Refer to the documentation supplied with TIBCO EMS for information on performing back-ups.

Repeat the process for all the machines in the cluster that have TIBCO ActiveMatrix BPM installed on them.


| 91

Chapter 8 Installing ActiveMatrix BPM Software (TIBCO Universal Installer)

This chapter describes how to use the TIBCO Universal Installer to install ActiveMatrix BPM software on a machine.

Topics


• Installing in GUI Mode, page 93

• Installing in Console mode, page 98

• Installing in Silent Mode, page 99

How, when and where you need to install ActiveMatrix BPM software depends on your installation/upgrade scenario.



92 | Chapter 8 Installing ActiveMatrix BPM Software (TIBCO Universal Installer)

Overview

You can install ActiveMatrix BPM software on a machine using one of the following installation modes:

• GUI mode - In the GUI mode, the installer presents panels that allow you to make choices about product selection, product location, and so on. To invoke the installer in GUI mode, double-click the executable. See Installing in GUI Mode on page 93.

• Console mode - Console mode allows you to run the installer from the command prompt or terminal window. This is useful if your machine does not have a GUI environment. See Installing in Console mode on page 98.

• Silent mode - Silent mode installs the product using either default or custom settings that are saved in a response file and does not prompt for inputs. See Installing in Silent Mode on page 99.

Using a New or an Existing Installation Environment (TIBCO_HOME)Before installing TIBCO ActiveMatrix BPM, you must decide whether to install the product into a new, empty installation environment (TIBCO_HOME) separate from other TIBCO products, or into an existing installation environment. TIBCO recommends the following:

• If you are upgrading an existing installation of TIBCO ActiveMatrix BPM, use the existing TIBCO_HOME.

• If you are installing TIBCO ActiveMatrix BPM to work together with other TIBCO products that are already installed, such as TIBCO ActiveMatrix BusinessWorks Service Engine, and to share the same TIBCO Administrator as these products, then use the existing TIBCO_HOME in which these products are installed.

• If you are installing TIBCO ActiveMatrix BPM for the first time, and either there will be no other TIBCO products that share TIBCO Administrator or else you have not yet installed any such products, then select a new TIBCO_HOME.


Installing in GUI Mode | 93

Installing in GUI Mode

1. Navigate to the temporary directory containing the extracted ActiveMatrix BPM archive file. (See Download ActiveMatrix BPM Software on page 86.)

2. Run TIBCOUniversalInstaller.

3. Click Next in the Welcome screen. The License Agreement screen displays.

4. Review the terms of the license agreement and, if you agree to them, click I accept the terms of the license agreement. Click Next to proceed 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 screen displays.

5. Select an installation profile in the left-hand pane. The right-hand pane displays the features selected by default for the chosen profile.

To customize the features to be installed, check Customize Installation and select the features to be installed.

On a Linux system, run TIBCOUniversalInstaller from the command line. Do not double-click the file to run it - doing so may cause a problem if you try to launch TIBCO Configuration Tool after running the installer.



6. Click Next. The TIBCO Installation Home screen displays. Select either a new installation environment (TIBCO-HOME) or an existing one, as described in Using a New or an Existing Installation Environment (TIBCO_HOME):

— For a new installation environment, select Create a New TIBCO_HOME. Specify the properties:

— For an existing installation environment, select Use an Existing TIBCO_HOME. Select the home from the drop-down list.

Click Next.

7. 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. Click Next to proceed with the installation.

On Linux and Solaris The LPGL License Agreement screen displays. After reading through the license text, click I accept the terms of the license agreement.

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

8. Click Next. If the Hibernate software is not in the assemblies subdirectory of your temporary directory, the Download Hibernate screen displays. Choose a download option:

— Download Hibernate assembly from TIBCO Choose this option if you are connected to the Internet or do not want to use a previously downloaded assembly. The assembly is automatically downloaded and stored into the

Directory The directory into which the product is installed. The directory cannot be the same as the directory of an existing installation environment.

Accept the default location, type a directory, or click Browse to choose the directory. The directory path cannot contain special characters such as "*", "#", "?", ">", "<", "%", "&", "$", "`" or "|".

Name Identifies the installation environment. The installer automatically creates a default environment name for the location you specify, which is amx-bpm.

The name cannot contain special characters such as "*", "?", ">", "<", ":", "|", "/", "\", or quotes (").



assemblies subdirectory of the directory where you extracted TIBCO ActiveMatrix TIBCO <Product> software.

— Select the Hibernate assembly previously downloaded from TIBCO Choose this option if you are not connected to the Internet. Click Browse to navigate to the directory where a Hibernate assembly that was previously downloaded is stored. Select the assembly and click Open.

9. The Download Hibernate screen displays. Select one of the following:

— Download Hibernate assembly from TIBCO: Choose to let the installer download the Hibernate from TIBCO. The installer downloads Hibernate and stores into the folder where you extracted the product software.

— Select the Hibernate assembly previously downloaded from TIBCO: Choose to provide the location where a Hibernate assembly that was previously downloaded from TIBCO is stored. Browse and select the directory containing the Hibernate assembly.

10. Click Next. If you chose to download Hibernate, a screen displays the Hibernate assembly download process.

11. Linux and Solaris If you choose to install TIBCO Host and the product_tibco_eclipse_lgpl_3.5.2.001 assembly is not in the assemblies subdirectory of your temporary directory, the LPGL Assembly Download screen displays. Choose a download option:

— Download Gnome Binding assembly from TIBCO Choose this option if you are connected to the Internet or do not want to use a previously downloaded assembly. The assembly is automatically downloaded and stored into the assemblies subdirectory of the directory where you extracted TIBCO ActiveMatrix BPM software.

— Provide the location for the assembly previously downloaded from TIBCO Choose this option if you are not connected to the Internet. Click Browse to navigate to the directory where the product_tibco_eclipse_lgpl_3.5.2.001 assembly that was previously downloaded is stored.

Select the assembly and click Open.

12. Linux and Solaris Click Next. If you chose to download the assembly, a screen displays the assembly download process.

13. The TIBCO Configuration Directory screen displays. The configuration directory (CONFIG_HOME) stores BPM configuration information, for example, the properties for Workspace and Openspace. Click Next to accept the default location or Browse and select the directory where you want your



configuration information to be stored. Ensure that the selected directory is not the configuration directory for another TIBCO installation environment.

14. The Pre-Install Summary screen displays. Verify the list of products/components selected for install.

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

15. Click Install. While the installer performs the necessary installation tasks, the Installing Component n of NN screen displays, where NN is the total number of components to be installed. After all the components are installed, the Running Product ANT Tasks screen displays. Click Show Details on the dialog to see the tasks that the installer is performing.

16. Once the installer completes the installation tasks, the Post-Install summary screen is displayed. Review the list of features that have been installed.

Launch TIBCO Configuration Tool is selected by default. TIBCO Configuration Tool provides a set of wizards that allow you to configure the runtime objects and drivers required by TIBCO ActiveMatrix BPM. Clear Launch TIBCO Configuration Tool if you do not want to configure the product right away.

17. Click Finish to complete the installation process and close the installer window. If you left Launch TIBCO Configuration Tool selected, the TIBCO Configuration Tool is launched. See Configuring ActiveMatrix BPM Runtime Objects (TIBCO Configuration Tool) on page 101 for details on using the tool.

Note that the TIBCO Configuration Directory specifies a different default location for the configuration directory than the actual location. For example, c:\ProgramData\amx-bpm\tibco\cfgmgt when the actual location is c:\ProgramData\amx-bpm\tibco\data.This is because the TIBCO Configuration Tool specifies a different location for the configuration folder than the TIBCO ActiveMatrix BPM installer. The TIBCO Configuration Tool will use the location you have specified in the TIBCO ActiveMatrix BPM installer

There is a slight delay while the installer deletes the temporary files before closing the installer window.



On a Linux system, selecting Launch TIBCO Configuration Tool may not start the TIBCO Configuration Tool. This problem only occurs if you double-clicked the installer zip file to unzip it, then double-clicked the executable file to run the installer.

To avoid this problem, run the installer using the following procedure:

1. Move the installer zip file to its own directory.

2. In a terminal window, use the unzip command to unzip the file.

3. Run the installer from the command line.



Installing in Console mode

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

2. Extract the archive file to a temporary directory.

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

4. Run TIBCOUniversalInstaller -console.

5. Complete the installation by responding to the console window prompts.

6. Once the installation completes, you can create the TIBCO ActiveMatrix BPM server and TIBCO ActiveMatrix Administrator server using TIBCO Configuration Tool (TIBCO Configuration Tool). See Configuring ActiveMatrix BPM Runtime Objects (TIBCO Configuration Tool) on page 101 for details.


Installing in Silent Mode | 99

Installing in Silent Mode

In silent mode, the universal installer does not prompt for any inputs during installation. Instead, the installer uses the values specified in the TIBCOUniversalInstaller-amx-bpm_n.n.n.silent file.

The TIBCOUniversalInstaller-amx-bpm_n.n.n.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 .silent file includes comments that describes the installation properties that you can set.

To install the product in silent mode:

1. Download the TIBCO ActiveMatrix BPM package.

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-amx-bpm_version.silent file and rename it.

5. Using a text editor, open the TIBCOUniversalInstaller-amx-bpm_n.n.n.silent file and specify the following entry keys. Refer to the file for a description of each entry key.

It is a good practice to make a copy of the original TIBCOUniversalInstaller-amx-bpm_n.n.n.silent file before making any changes to it.

Entry key Default value

acceptLicense true

installationRoot C:\tibco\amx-bpm

createNewEnvironment true

environmentName amx-bpm

downloadHibernate true

hibernatePath

useInstallProfile true

selectedProfiles Primary machine



6. Run the command:

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

configDirectoryRoot C:\ProgramData\amx-bpm

Entry key Default value

Make sure that all drive letters are specified in upper case, otherwise the silent installation may fail.


| 101

Chapter 9 Configuring ActiveMatrix BPM Runtime Objects (TIBCO Configuration Tool)

This chapter describes how to use TIBCO Configuration Tool to configure ActiveMatrix BPM runtime objects.

Topics

• Configuring ActiveMatrix BPM in GUI Mode on page 102

• Manually Running the ActiveMatrix BPM Database Creation Scripts, page 104

• Configuring ActiveMatrix BPM in Silent Mode, page 108

How, when and where you need to use TIBCO Configuration Tool depends on your installation/upgrade scenario.



102 | Chapter 9 Configuring ActiveMatrix BPM Runtime Objects (TIBCO Configuration Tool)

Configuring ActiveMatrix BPM in GUI Mode

This section describes running TIBCO Configuration Tool to create the runtime objects required for an ActiveMatrix BPM setup:

1. Execute TIBCO_HOME/tct/n.n/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. The configuration folder is referred to as CONFIG_HOME.

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 listed Table 3.

4. Choose a wizard and configure according to the wizard reference.

Table 3 Configuration Wizards

Wizard Function

Configure TIBCO ActiveMatrix BPM Server Node Type Wizard

Allows you to create an TIBCO ActiveMatrix BPM Node. You can create the following node types:

• BPM Node Type

• Process Manager Node Type

• Work Manager Node Type

• Web Components Node Type

Create TIBCO ActiveMatrix BPM Server Wizard

Allows you to configure the TIBCO ActiveMatrix BPM database and runtime clients for TIBCO ActiveMatrix BPM.

Create TIBCO ActiveMatrix Administrator Server Wizard

Allows you to configure the TIBCO ActiveMatrix Administrator server.

Create TIBCO Host Instance Wizard

Specify the communication and management properties of a standalone TIBCO Host instance and optionally create and launch the TIBCO Host instance.

Configure Third-Party Driver Wizard

Package and install third-party client driver libraries that implement APIs such as JDBC and JMS into the ActiveMatrix Administrator server software repository.


Configuring ActiveMatrix BPM in GUI Mode | 103

Click Load... if you want to load the values saved from a previous configuration session.

5. Optionally select Configure to Secure All Communication with SSL. When checked, the wizards containing communication channels display SSL configuration fields. For information on the supported communication channels, see Securing Communication Channels on page 223.

6. In the Summary screen, the wizard reports the configuration tasks it will perform:

a. Select or clear individual configuration tasks.

b. Click Configure to execute the tasks and save the configuration settings. The wizard reports the status of tasks as it completes them.

Alternatively, you can:

— Click Save to save a configuration for later use.

— Click Cancel to return to the wizard selector screen.

If the following configuration task is listed.

Create ActiveMatrix BPM [Not Creating Database Instance]

see Manually Running the ActiveMatrix BPM Database Creation Scripts before continuing.

c. On Windows systems, after the TIBCO Host instance is started, if a dialog is displayed asking if you want to keep blocking TIBCO Java Launcher, click Unblock.



Manually Running the ActiveMatrix BPM Database Creation Scripts

If you clear Create BPM Database Instance in the ActiveMatrix BPM: Database Administrator screen, the database administrator must manually run the TIBCO ActiveMatrix BPM database creation scripts to create the BPM database before TIBCO Configuration Tool can successfully configure ActiveMatrix BPM.

If the Summary dialog lists the following configuration task:

Create ActiveMatrix BPM [Not Creating Database Instance]

proceed as shown in the following table.

If... Do this...

Your database administrator has already manually run the TIBCO ActiveMatrix BPM database creation scripts to create the BPM database

Click Configure to configure TIBCO ActiveMatrix BPM.

The wizard reports the status of tasks as it completes them. Once the status is Successful! Click Close to exit TIBCO Configuration Tool. The installation and configuration of TIBCO ActiveMatrix BPM is complete.

Your database administrator has not yet run the TIBCO ActiveMatrix BPM database creation scripts

1. Click Save to save the configuration information in a session script that can be used by TIBCO Configuration Tool to configure TIBCO ActiveMatrix BPM at a later date.

2. Click Cancel to exit the Create TIBCO ActiveMatrix BPM Server wizard.

3. Get the database administrator to manually run the ActiveMatrix BPM Database Creation Scripts.

4. Run the Create TIBCO ActiveMatrix BPM Server wizard again (or use the silentinstall bpm command - see Configuring ActiveMatrix BPM in Silent Mode).

5. Load the saved configuration information.

6. From the Summary dialog, click Configure to complete the configuration of TIBCO ActiveMatrix BPM.


Manually Running the ActiveMatrix BPM Database Creation Scripts | 105

ActiveMatrix BPM Database Creation ScriptsThe structure of the CONFIG_HOME/bpm/database directory is shown below:

The admin directory contains the database administrator scripts that contain the commands needed to create the schema itself. In Oracle, this means creating the tablespaces and in SQL Server, creating the logins that will own the schema and database.

The rest of the directories contain the SQL scripts required to create and/or upgrade the tables for each BPM component. These are for reference only.

To manually create the BPM database, your database administrator needs to run the following scripts in the order shown. (Make sure you read the database-specific notes that follow this table before running these scripts.)

Script Description Run As

CONFIG_HOME/bpm/database/admin/setup-admin.sql

These scripts contain the commands needed prior to creating the schema itself. On:

• SQL Server - this means creating the logins that own the schema and database.

• Oracle - this means creating the tablespaces

• DB2 - this script is not needed

Database Administrator

CONFIG_HOME/bpm/database/admin/createdb-admin.sql

These scripts contain the commands required to create the database and/or schema.


CONFIG_HOME/bpm/database/ProcessManagerCreate.sql

These scripts create the schema objects required for the process manager component.

BPM User



CONFIG_HOME/bpm/database/WorkManagerCreate.sql

These scripts create the schema objects required for the work manager component. When running this script manually to create schema objects in DB2, you must set the statement termination character to ’/’ (forward-slash) rather than a ’;’(semi-colon). See Configure the ActiveMatrix BPM Database Server on page 79 for details.

BPM User

DB2 - Set the Appropriate Statement Termination Character

Not all the scripts use the same termination character. For example, the termination character for WorkManagerCreate.sql is ’/’ and for createdb-admin.sql and ProcessManagerCreate.sql scripts is ’;’.

Ensure that you examine the scripts and set the appropriate termination character using the DB2 Control Center. Doing so ensures that the scripts can be used from either the DB2 Control Center or the DB2 Command Line Processor.

You can set the statement termination character from the DB2 Control Center.

SQL Server - Remove ANSI_PADDING ON and ANSI_PADDING OFF Statements

When manually running scripts, incorrect use of ANSI_PADDING statements may change the ANSI_PADDING setting for SQL Server, causing all tables created subsequently during the same query session to have the wrong setting.

Before manually running any SQL scripts, ensure that you do the following:

1. Delete any SET ANSI_PADDING ON and SET ANSI_PADDING OFF statements in the script.

2. Check the database query session settings and ensure that ANSI_PADDING is turned ON. To do this, right click the query window and select Query Options, then select the Execution->ANSI section and ensure that SET ANSI_PADDING is selected.

Script Description Run As


Manually Running the ActiveMatrix BPM Database Creation Scripts | 107

Oracle - Remove Blank Lines

If you need to manually amend any of the BPM database creation scripts, make sure that you do not include any blank lines. If there are any blank lines, you will receive an error similar to the ones below:

SP2-0734: unknown command beginning "CONSTRAINT..."SP2-0042: unknown command ")"

and the rest of the line is ignored. To resolve this, you can:

• remove all blank lines from the script

• set sqlblanklines on on the sqlplus session



Configuring ActiveMatrix BPM in Silent Mode

You can use the TIBCO_HOME\bpm\n.n\scripts\silent\silentinstall utility to generate and run TIBCO Configuration Tool scripts to configure ActiveMatrix BPM runtime objects in silent mode.

Silentinstall Commandssilentinstall provides two types of commands - script generation and script execution.

Script Generation Commands

Script generation commands provide a series of prompts at which you can enter the data you would enter in the equivalent GUI wizards. The command then generates a set of scripts that can be subsequently used with the Script Execution Commands.

To run a script generation command, use the command:

silentinstall command

where command is one of the commands listed in the following table.

Command Description

config-bpm Generate scripts that can be used subsequently with the admin, bpmonly, bpm, bpmnodetype and tibcohost commands. Running this script collects the same data that you supply using the Create TIBCO ActiveMatrix BPM Server Wizard.

This command creates a configuration scripts folder TIBCO_HOME\data\tct\silent\bpm\scripts

config-tpcl Generate scripts that can be used subsequently with the tpcl command. Running this script collects the same data that you supply using the Configure Third-Party Driver Wizard.

This command creates a configuration scripts folder TIBCO_HOME\data\tct\silent\tpcl\scripts


Configuring ActiveMatrix BPM in Silent Mode | 109

Script Execution Commands

Script execution commands allow you to configure ActiveMatrix BPM runtime objects without user input, using a previously generated set of configuration files.

To run a script execution command:

1. If necessary, edit the appropriate build.properties file - see The build.properties File.

2. Use the command:

silentinstall command tct_output_folder

where:

• command is one of the commands listed in the following table.

• tct_output_folder is a configuration scripts folder containing a previously generated set of configuration files, generated either:

— by using one of the Script Generation Commands.

— by running one of the TIBCO Configuration Tool wizards in GUI mode. When you click Configure or Save in the Summary screen, a configuration scripts folder is created under the location defined in the Session Scripts and Log Folder field. By default, this folder is CONFIG_HOME\tct\wizardType\timestamp.

Command Description

admin Create an ActiveMatrix Administrator server.

bpmonly Create a BPM node (using an existing ActiveMatrix Administrator server).

bpm Create a BPM node and an ActiveMatrix Administrator server.

bpmnodetype Create a remote BPM node (of the desired type).

tibcohost Create a TIBCO Host instance.

tpcl Configure JDBC drivers.



The build.properties FileEvery configuration scripts folder contains a build.properties file. This file contains a set of configuration properties that are used by the Script Execution Commands.

There are two types of property:

• General settings, such as the value for TIBCO_HOME.

• ActiveMatrix Administrator Server settings, as would be generated by running the Create TIBCO ActiveMatrix Administrator Server Wizard.

For example:

# --------------------------------------------------------------------------# General settings# Tibco home, tibco config management home and the directory in which the# default set of silent install scripts can be found# --------------------------------------------------------------------------TIBCO_HOME=C:/Program Files/tibco/amx-bpmtibco.config.mgmt.home=C:/Program Files/tibco/amx-bpm/datatct.scripts.dir=C:/Program Files/tibco/amx-bpm/data/tct/silent/bpm/scripts

# --------------------------------------------------------------------------# Administrator Server Configuration: Details# Enter configuration details for the ActiveMatrix Administrator server# Enterprise Name and Server Name# --------------------------------------------------------------------------admin.enterprise.name=AMX BPMadmin.instance.name=AMX BPM Server

Example - Using silentinstall to Configure a Basic ActiveMatrix BPM SystemTo silently configure a basic ActiveMatrix BPM system (as described in Installing and Configuring a Basic ActiveMatrix BPM System):

1. Run:

silentinstall config-tpcl

to generate the scripts that will be used to configure JDBC drivers.

2. If necessary, edit:

TIBCO_HOME\data\tct\silent\tpcl\scripts\build.properties

You should check and, if necessary, edit these property values before you run any Script Execution Commands that use the configuration scripts folder that contains this build.properties file.


Configuring ActiveMatrix BPM in Silent Mode | 111

3. Run:

silentinstall tpcl TIBCO_HOME\data\tct\silent\tpcl\scripts

to configure JDBC drivers.

4. Run:

silentinstall config-bpm

to generate the scripts that will be used to create the BPM node and ActiveMatrix Administrator server.

5. If necessary, edit:

TIBCO_HOME\data\tct\silent\bpm\scripts\build.properties

6. Run:

silentinstall bpm TIBCO_HOME\data\tct\silent\bpm\scripts

to create the BPM node and ActiveMatrix Administrator server.


| 113

Chapter 10 Distributing the ActiveMatrix BPM Application to a Remote Node

This chapter explains how to distribute the BPM application to a remote node (when you are using a distributed or high availability, fault tolerant BPM system).

Topics

• Distributing the ActiveMatrix BPM Application in a High Availability, Fault Tolerant BPM System, page 114

• Distributing the ActiveMatrix BPM Application in a Distributed BPM System

How, when and where you need to distribute the BPM application depends on your installation/upgrade scenario.



114 | Chapter 10 Distributing the ActiveMatrix BPM Application to a Remote Node

Distributing the ActiveMatrix BPM Application in a High Availability, Fault Tolerant BPM System

1. Log on to TIBCO ActiveMatrix Administrator. (You can log in on either machine, or through the load balancer.)

2. In the Applications pane, select the authentication application amx.bpm.auth.system.

3. On the Distribution tab, select amx.bpm.auth.system.

4. In the Available Nodes section, select the BPM node on the remote machine and add it to the Selected Nodes section.

5. Click Save. The application’s Synchronization status changes to Out of Sync. (You may need to refresh the display to see this change.)

6. Repeat steps 2 to 5 for the following applications:

a. the remaining authentication applications, amx.bpm.auth.easyAs and amx.bpm.auth.wss.asp.

b. the main ActiveMatrix BPM application, amx.bpm.app.

7. In the Applications pane, select the amx.bpm.auth.* applications and click Deploy.

8. Wait (and, if necessary, refresh the display) until the applications’ status has changed to:

— Runtime State: Running

— Synchronization: InSync

indicating that the applications have been successfully distributed to the new node.

You do not need to manually distribute the internal organization model, amx.bpm.sysorgmodel, as it is automatically distributed with amx.bpm.app.

When you modify the amx.bpm.app distribution, amx.bpm.sysorgmodel will also go Out of Sync.

Deploying the authentication applications before amx.bpm.app ensures that users cannot try to log in to ActiveMatrix BPM before it is fully deployed to both nodes.


Distributing the ActiveMatrix BPM Application in a High Availability, Fault Tolerant BPM System | 115

9. In the Applications pane, select amx.bpm.app and click Deploy. A dialog is displayed, prompting you to also deploy amx.bpm.sysorgmodel.

10. Click Deploy.

11. Wait (and, if necessary, refresh the display) until both applications’ status has changed to:



indicating that the applications have been successfully distributed to the new node. (Depending on the system load, this operation may take some time.)

ActiveMatrix BPM is now running on both the primary and remote machines.



Distributing the ActiveMatrix BPM Application in a Distributed BPM System

1. Log on to TIBCO ActiveMatrix Administrator.

2. In the Applications pane, select the main ActiveMatrix BPM application, amx.bpm.app.

3. On the Distribution tab, expand the amx.bpm.app application to display the logical nodes that make up the application. These are:

— ProcessManager

— WorkManager

— WebComponents

4. Select the appropriate entity that you want to distribute to the remote node, as shown in the following table:

You must distribute the entity that is appropriate to the type of the remote node that you defined in Task 6: Remote Machine - Create a Node of the Required Type.

5. In the Available Nodes section, select the BPM node on the remote machine and add it to the Selected Nodes section.

6. Click Save. The application’s Synchronization status changes to Out of Sync. (You may need to refresh the display to see this change.)

7. In the Applications pane, select amx.bpm.app and click Deploy. A dialog is displayed, prompting you to also deploy amx.bpm.sysorgmodel.

If the remote node type is... Select the...

BPM amx.bpm.app application

Process Manager ProcessManager logical node

Work Manager WorkManager logical node

Web Components WebComponents logical node

You do not need to manually distribute the internal organization model, amx.bpm.sysorgmodel, as it is automatically distributed with amx.bpm.app.

When you modify the amx.bpm.app distribution, amx.bpm.sysorgmodel will also go Out of Sync.


Distributing the ActiveMatrix BPM Application in a Distributed BPM System | 117

8. Click Deploy.

9. Wait (and, if necessary, refresh the display) until both applications’ status has changed to:



indicating that the applications have been successfully distributed to the new node. (Depending on the system load, this operation may take some time.)

ActiveMatrix BPM is now distributed across both the primary and remote machines.


| 119

Chapter 11 Post-Installation Tasks

This chapter describes the tasks you may need to do after installing ActiveMatrix BPM software.

Topics

• Create Any Other Required LDAP Connections to LDAP Directories, page 120

• Configure Client Communications Through the Load Balancer, page 121

• Install the Mediation Product Application, page 124

• Configure Transaction Recovery (Oracle only), page 125

• Set Transaction Verification Property (SQL Server Only), page 126

The tasks you need to perform vary according to your installation/upgrade scenario.



120 | Chapter 11 Post-Installation Tasks

Create Any Other Required LDAP Connections to LDAP Directories

Create LDAP connections to additional LDAP directories that contain details of users who may need to log in to ActiveMatrix BPM using Openspace, Workspace or a custom client application.

1. Log in to ActiveMatrix Administrator.

2. Create the necessary shared resources to define an LDAP connection to each required LDAP directory. These resources are:

— LDAP Connection resource template

— LDAP Connection resource instance

3. Create the necessary shared resources to authenticate login attempts against users in that LDAP directory. These resources are:

— LDAP Authentication resource template

— LDAP Authentication resource instance

— LDAP Authentication Provider application

See the following references for more detailed information about these steps:

• "Configuring TIBCO ActiveMatrix BPM to Use a New LDAP Directory Server" in TIBCO ActiveMatrix BPM - BPM Administration

• "Resource Templates" in TIBCO ActiveMatrix BPM - SOA Administration

You only need to do this if the LDAP directory that you specified when running the Create TIBCO ActiveMatrix BPM Server Wizard (in the ActiveMatrix BPM: LDAP Configuration screen) does not contain details of all users who may need to log in to ActiveMatrix BPM using Openspace, Workspace or a custom client application.

You can then use the Organization Browser (logging in as tibco-admin) to create BPM resources (users) from the LDAP users available in each LDAP container. For more information, see:

• "Creating the Organization Model" in TIBCO ActiveMatrix BPM Concepts

• TIBCO ActiveMatrix BPM Organization Browser User’s Guide


Configure Client Communications Through the Load Balancer | 121

Configure Client Communications Through the Load Balancer

If you have installed a BPM system using a distributed or highly available, fault tolerant configuration, you must configure the system to be able to communicate properly with OpenSpace and Workspace via the load balancer.

Task D Configure Properties Files

In the CONFIG_HOME\bpm\configuration\wpextender.properties file, change the UseHttpRequestContextURL and formContextURL properties to the following values:

UseHttpRequestContextURL=false

formContextURL=http://webServerHost:port/bpmresources

where webServerHost and port are the IP address/hostname and port number of the load balancer that exposes the Openspace and Workspace applications.

webServerHost and port should match the hostname and port found in the Location bar in the internet browser used to access Openspace or Workspace so as to comply with the same-origin policy enforced by most internet browsers.

See "Configuring TIBCO ActiveMatrix BPM Components" in TIBCO ActiveMatrix BPM - BPM Administration for more information about property files.

Task E Configure Launch Pages to Handle Context-Switching

The load balancer may use context-switching (for example, to allow dynamic routing of endpoints) in the URL that it uses to access Openspace or Workspace - for example:

loadbalancer:port/context/openspace

If multiple contexts are used, for example:

loadbalancer:port/context1/context2/openspace

Openspace and Workspace cannot by default resolve the URL properly to load the TIBCO Forms runtime and display a form.

If you do not do this, you will not be able to display work item forms or start business services.

You may need to clear the cache in a browser session to pick up these changes.



To correct this, you must edit the appropriate Openspace or Workspace HTML launch page(s) to account for the different format of the URL:

1. Identify each Openspace or Workspace HTML launch page that you need to edit, depending on the client types that you use. The following table lists the different launch pages - there are two copies of each launch page, one in each of the following folders:

— CONFIG_HOME\tibcohost\Admin-enterpriseName-serverName\host\plugins\

— TIBCO_HOME\components\shared\1.0.0\plugins\

You should edit both copies.

2. In each file:

a. Find the following entry:

<scripttype="text/javascript" language="javascript"src="../bpmresources/formsclient/formsclient.nocache.js">

</script>

b. Prefix the src path with an additional "../" for each additional nesting level used in the context path of the load balancer URL.

c. Save the file.

File Description

com.tibco.openspace.login_version\resources\openspace.html Openspace launch page

com.tibco.openspace.login_version\resources\mobile\mobile.html

Openspace - Mobile launch page

com.tibco.openspace.login_version\resources\openform\openform.html

Openspace launch page for pushed work items

com.tibco.n2.rtc.ws_version\resources\workspace.html Workspace launch page

com.tibco.n2.rtc.ws_version\resources\openworkitem.html Workspace launch page for pushed work items


Configure Client Communications Through the Load Balancer | 123

Example

If the URL used to access Openspace from the load balancer is:

loadbalancer:port/context1/context2/openspace

change the entry in the launch page to:

<scripttype="text/javascript" language="javascript"src="../../bpmresources/formsclient/formsclient.nocache.js">

</script>

Openspace or Workspace can, by default, resolve a request and display a form if the URL used to access Openspace or Workspace from the load balancer has the format:

loadbalancer:port/BPMclient

or

loadbalancer:port/context/BPMclient

For example, if the URL used to access Openspace from the load balancer is:

loadbalancer:port/openspace

or

loadbalancer:port/openspace.html

or

loadbalancer:port/context1/openspace.html

no additional configuration of launch pages is required.



Install the Mediation Product Application

The Mediation product application is not deployed by default on the BPMNode when you install ActiveMatrix BPM. It implements mediation for 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 TIBCO ActiveMatrix Mediation Implementation Type 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.

Mediation involves virtualizing and managing service interactions between communicating participants. Refer to the Administration documentation for your runtime environment for more information on mediation.


Configure Transaction Recovery (Oracle only) | 125

Configure Transaction Recovery (Oracle only)

Ensure that the BPM database user has sufficient privileges to enable the ActiveMatrix BPM runtime to perform transaction recovery:

1. Connect to the Oracle database server as a user that has SYSDBA system privilege. For example:

SQL > connect sys/password as sysdba

2. Execute the following SQL statements:

GRANT SELECT ON sys.dba_pending_transactions TO userGRANT EXECUTE ON sys.dbms_xa TO userGRANT SELECT ON sys.dba_2pc_pending TO user

where user is the name of the BPM database user (as defined by the Username in the ActiveMatrix BPM: Runtime Database Configuration screen of the Create TIBCO ActiveMatrix BPM Server Wizard - for example, bpmuser).

ActiveMatrix shared resources that are XA-enabled participate in global transactions (coordinated by the transaction manager within a TIBCO host instance). If the TIBCO host instance fails, the shared resources can update themselves to the decided state of the global transaction when they recover. For more information, see "Transaction Recovery" in TIBCO ActiveMatrix BPM - SOA Administration.



Set Transaction Verification Property (SQL Server Only)

Microsoft SQL Server currently cannot handle the scenario where commits return successfully (in XA mode) even when the transaction has not completed. Consequently, duplicate work items can occur when the BPM runtime is running against a Microsoft SQL Server.

1. Log in to TIBCO ActiveMatrix Administrator as root user and select Infrastructure > Nodes.

2. Select the node BPMNode and click the Configuration tab.

3. Select the link JVM Arguments.

4. Under the Properties heading, click Add to add a new JVM property.

5. Enter the property name as com.tibco.pvm.txVerification.enable and value as true.

6. Click Save to save the changes.

7. Stop and Restart the BPMNode.

There is a case open with Microsoft for this issue (Case Reference 112010377500682). You must set the following property until Microsoft provides a fix for this issue. Once the fix is applied, this property must be removed.


| 127

Chapter 12 Upgrading ActiveMatrix BPM Runtime Objects (Upgrade Utility)

This chapter describes how to use the Upgrade utility to upgrade ActiveMatrix runtime objects on an existing BPM system to the new version of ActiveMatrix BPM.

Topics

• Upgrade Impact on page 128

• The Upgrade Utility on page 129

• Running the Upgrade Utility on page 131

• Troubleshooting on page 133

How, when and where you need to use the Upgrade utility depends on your upgrade scenario.



128 | Chapter 12 Upgrading ActiveMatrix BPM Runtime Objects (Upgrade Utility)

Upgrade Impact

No configuration is required prior to an upgrade and upgrade does not affect any of the configuration of your existing installation. For example, if an upgrade is performed:

• All existing process instances deployed on your existing installation will still be available.

• Process instances and work items with a status of In Progress continue to be processed.

• Configured LDAP containers, users and organization memberships will still be available.

Note that:

• While the ActiveMatrix Administrator server is being upgraded, deployed applications will continue to run without service interruption. However, the Administrator server itself will be unavailable, which means you cannot perform functions such as deploying new applications and managing existing applications, and managing infrastructure.

• While a TIBCO Host instance and its nodes are being upgraded, the applications deployed on the nodes will be stopped. As a result, clients of those applications will experience service interruption.

Depending on the size of your system, upgrade can take some time. You should allow sufficient time for the upgrade to be performed.


The Upgrade Utility | 129

The Upgrade Utility

The upgrade utility is called:

• On Windows: upgrade.bat

• On UNIX/Linux: upgrade

and is located in TIBCO_HOME\bpm\n.n\scripts\upgrade.

The upgrade utility is created when you install the new version of TIBCO ActiveMatrix BPM. It uses the configuration information from your existing installation of TIBCO ActiveMatrix BPM to configure the upgraded TIBCO ActiveMatrix BPM.

The required configuration information is located in the TIBCO Configuration Folder that stores the scripts that are generated by TIBCO Configuration Tool. For example, CONFIG_HOME\tct\bpm\date-time\scripts, where date-time is the date and time the scripts were created when you first installed TIBCO ActiveMatrix BPM.

The upgrade utility provides a script that allows you to upgrade the individual components of TIBCO ActiveMatrix BPM. The table below describes the components that are updated using the upgrade script. The components should be upgraded in the order specified below:

Component Upgrade Command

TIBCO Host upgrade tibcohost

TIBCO Administrator upgrade admin

TIBCO ActiveMatrix BPM Node upgrade bpmnodes

TIBCO ActiveMatrix BPM Database

upgrade bpm-database

TIBCO ActiveMatrix BPM Application

upgrade bpm-app



The following table describes the commands that you can run using the upgrade utility.

However, you can run the upgrade commands individually if required. This may be necessary, for example, if a problem occurs during upgrade that causes an upgrade script to exit. For example, when you are prompted by the upgrade script to enter information, you must type the information exactly as it is required. Otherwise, this can cause the upgrade script to exit. If this happens, you can run the rest of the upgrade scripts individually to complete the upgrade.

Troubleshooting on page 133 describes example scenarios and possible resolutions to complete the upgrade process.

Command Runs the following...

upgrade all upgrade tibcohost

upgrade admin

upgrade bpmnodes

upgrade bpm-database

upgrade bpm-app

upgrade platform upgrade tibcohost

upgrade admin

upgrade bpmnode

upgrade bpm upgrade bpm-database

upgrade bpm-app

Refer to the instructions in Upgrading an ActiveMatrix BPM System to determine which version of the upgrade command you should use in a particular situation.

You should only use other upgrade commands when dealing with a problem during upgrade, or when asked to do so by TIBCO Support. See Troubleshooting for more information.

TIBCO ActiveMatrix BPM 2.1 requires that all ActiveMatrix platform components are at version 3.1.505 (that is, version 3.1.5 with HotFix 5).

Before using the upgrade bpm, upgrade bpm-database or upgrade bpm-app commands, make sure that TIBCO Host instance(s), TIBCO Administrator (and TIBCO Administrator database) and BPM node(s) are all at version 3.1.5 with HotFix 5.


Running the Upgrade Utility | 131

Running the Upgrade Utility

To run the upgrade utility:




upgrade all tct_output_folder



Depending on the configuration and the number of applications deployed, upgrade can take varying amounts of time to complete.

For example, upgrading a lightly-loaded, single node could take about an hour. Upgrading a lightly-loaded, high availability system could take 2 - 3 hours to complete.

Ensure that you allow sufficient time for the upgrade to be completed.

Upgrade will fail if you have reconfigured the ActiveMatrix Administrator server in any of the following ways since creating it with TIBCO Configuration Tool:

• Deleted the initial superuser or changed the superuser password.

• Changed the port of the external HTTP connector or enabled or disabled SSL for the connector.

On Windows, you must escape any space characters in the tct_output_folder path. If you do not do this, the path is truncated at the space character and the command will fail.

To do this, use the short name (that is, the 8.3 DOS filename) of the affected part of the path - you can determine this by using the DIR /X command.

For example, if the path is:C:\ProgramData\amx-bpm 1.3.1\tibco\data\tct\bpm\2012-11-06-10-44-29\scripts

run the command as:

upgrade all C:\ProgramData\amx-bp~1.1\tibco\data\tct\bpm\

2012-11-06-10-44-29\scripts



3. The script prompts you to shutdown the TIBCO Host instances and all node processes

stop processes? (yes|no) :

Enter yes to continue. Upgrade shuts down TIBCO Host, upgrades and restarts it. The script informs you when this has completed.

TIBCO Host instance has been upgraded.

4. The script prepares to upgrade TIBCO ActiveMatrix Administrator. Upgrade has to interrupt service for the applications running on the nodes.

interrupt service? (yes|no) :

5. Press Return. Upgrade now needs to upgrade the TIBCO ActiveMatrix BPM database.

Automatically upgrade database? (yes, no)

To:

— allow the script to automatically upgrade the TIBCO ActiveMatrix BPM database, type yes. Go to step 6.

— manually upgrade the TIBCO ActiveMatrix BPM database, type no. If you type no, the upgrade utility generates the two required SQL upgrade scripts:

—/bpm/database/WorkManagerUpgrade.sql

—/bpm/database/ProcessManagerUpgrade.sql

and prompts you as follows:

Database upgraded? (yes, no) :

Your DBA must execute these scripts as the BPM User against the TIBCO ActiveMatrix BPM database before you can continue with the upgrade process - see Manually Running the ActiveMatrix BPM Database Creation Scripts. Once your TIBCO ActiveMatrix BPM database has been upgraded, type yes.

6. The utility upgrades the TIBCO ActiveMatrix BPM application.

7. Once these scripts have run, Build Successful should be returned and the upgrade of TIBCO ActiveMatrix BPM is complete.


Troubleshooting | 133

Troubleshooting

When running the upgrade utility, if the script exits with an error on or before upgrading all the components, depending on the error, it may be possible to complete the upgrade process by running the individual commands rather than restoring the system to its pre-upgrade state then running an upgrade again. Following example scenarios describe the scripts to be run when the upgrade scripts exits before completion.

Scenario 1

If you have run upgrade all, and the script exits after upgrading TIBCO Host but before upgrading TIBCO Administrator, you could run the following commands in the order specified below:

1. upgrade admin - to upgrade TIBCO Administrator

2. upgrade bpmnodes - to upgrade TIBCO ActiveMatrix BPM Node

3. upgrade bpm - to upgrade TIBCO ActiveMatrixDatabase and TIBCO ActiveMatrix Application

Scenario 2

If you have run upgrade all, and the script exits after upgrading TIBCO ActiveMatrix BPM node but before upgrading TIBCO ActiveMatrix BPM database, you could run the following command:

upgrade bpm-app


| 135

III - TIBCO CONFIGURATION TOOL WIZARD REFERENCE

The following chapters provide detailed reference information about the individual TIBCO Configuration Tool wizards.

Topics

• Configure TIBCO ActiveMatrix BPM Server Node Type Wizard, page 137

• Create TIBCO ActiveMatrix BPM Server Wizard, page 145

• Create TIBCO ActiveMatrix Administrator Server Wizard, page 159

• Create TIBCO Host Instance Wizard, page 183

• Configure Third-Party Driver Wizard, page 189


136 | III - TIBCO CONFIGURATION TOOL WIZARD REFERENCE


| 137

Chapter 13 Configure TIBCO ActiveMatrix BPM Server Node Type Wizard

This chapter provides reference information about the TIBCO Configuration Tool Configure TIBCO ActiveMatrix BPM Server Node Type wizard.

Topics

• Welcome, page 138

• ActiveMatrix BPM Node Type: Administrator Server Configuration, page 139

• ActiveMatrix BPM Node Type: Host and Node Configuration, page 141

• ActiveMatrix BPM Node Type: Sizing Configuration, page 143

• ActiveMatrix BPM Node Type: Summary, page 144

This wizard can be run directly on the remote machine (where the node is to be configured), or on the primary node. Where it can, TIBCO Configuration Tool validates data entered in this wizard before performing the actual configuration, and reports any errors that it detects.

TIBCO recommend that you run this wizard on the remote machine, as TIBCO Configuration Tool is able to perform more extensive validation.


138 | Chapter 13 Configure TIBCO ActiveMatrix BPM Server Node Type Wizard

Welcome

Field/Button Description

Configure to Secure All Communication with SSL

Whether all communication channels used by ActiveMatrix BPM should be secured with SSL.

Select this to pre-select all "SSL enabled" check boxes in subsequent pages of this wizard. (You will be able to override this choice and select or clear those check boxes on their individual pages.)

Default: Cleared


ActiveMatrix BPM Node Type: Administrator Server Configuration | 139



Machine Name Name of the machine on which the ActiveMatrix Administrator server is running.

Default: Name of the machine on which TIBCO Configuration Tool is being executed.

Port Browser port used to access the ActiveMatrix Administrator server.

Note: If ActiveMatrix BPM nodes are distributed over different machines (to provide high availability and/or scalability), this port should be configured for load balancing across all required machines - see Load Balancer.

Default: 8120

Username ID of the ActiveMatrix Administrator superuser.

Default: root

Password Password of the ActiveMatrix Administrator superuser.

Default: t

Admin server is SSL enabled

Whether the Administrator server internal port is enabled for SSL. When selected, the SSL Keystore Configuration fields are enabled.

Note: If ActiveMatrix BPM nodes are distributed over different machines (to provide high availability and/or scalability), the Trust Store Location must be SHARED_DIR\keystores - see Shared File System.

Test Connection Verifies that TIBCO Configuration Tool can connect to the Administrator server using the information supplied on this page.



SSL Keystore Configuration:

Create a Trust Store Obtains certificates from the specified TIBCO Administrator server and creates a new trust store, which will be used to establish the trust relationship with the TIBCO Administrator server:

1. Click Create a Trust Store.

2. Specify a password to protect the keystore and click Next >. The SSL setup wizard displays the certificates imported from the TIBCO Administrator server.

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

If you do not click Create a Trust Store, you must specify the details of an existing trust store that can be used to establish the trust relationship with the TIBCO Administrator server.

Trust Store Location

Either:

• the location in which the created trust store will be stored, or

• the location of the trust store to be uploaded to ActiveMatrix Administrator. (You can either type this directly or use the Browse button to find it.)

Trust Keystore Type

The type of the created or uploaded trust store: JKS or JCEKS.

Default: JKS.

Trust Store Password

Either:

• the password specified in the Create a Trust Store wizard, or

• the password required to access the trust store that is to be uploaded.



ActiveMatrix BPM Node Type: Host and Node Configuration | 141



Node Type Type of the (logical) BPM node to be created. One of:

• BPM Node Type

• Process Manager Node Type

• Work Manager Node Type

• Web Components Node Type

See "Introduction > TIBCO ActiveMatrix BPM Architecture" in TIBCO ActiveMatrix BPM Concepts for more information about these node types.

Default: BPM Node Type

Node Name Unique name to be used for this BPM node. This name must be unique both in the environment and in the enterprise.

Default: BPMNode

Node Port Management port number used by this BPM node. This port must not be in use by another node on the same machine.

Default: 6031

Host Name of an existing host on which this BPM node will run.

Default: BPMHost

HTTP Port HTTP port number used by this BPM node for communication with external clients (Openspace, Workspace and custom client applications).

This port must not be in use by another node on the same machine.


Default: 8080

Environment Name

Name of an existing environment in which this BPM node will run.

Default: BPMEnvironment



Override BPM Configuration Folder

Whether to override the default location of the BPM configuration folder. Select this if ActiveMatrix BPM nodes are distributed over different machines (to provide high availability and/or scalability).

If selected, the Configuration Folder field is displayed.

Default: Cleared

Configuration Folder

Location of the BPM configuration folder.

If ActiveMatrix BPM nodes are distributed over different machines (to provide high availability and/or scalability), this must be a location on the shared file system. For example, SHARED_DIR\bpm_config - see Shared File System.

Default: CONFIG_HOME\bpm



ActiveMatrix BPM Node Type: Sizing Configuration | 143

ActiveMatrix BPM Node Type: Sizing Configuration


Environment Type of environment being set up. Choose from the options: Development and Production.

The environment you choose in this field determines the default values provided for the remaining fields on this screen.

Default: Development

Max Java PermGen Size

Maximum size for Java PermGen.

Default:

• Development - 256

• Production - 1024

Ranged Parameters:

Java Heap Size Range for the Java heap size.

Default:

• Development - Minimum: 512 Maximum: 1024

• Production - Minimum: 1024 Maximum: 4096



ActiveMatrix BPM Node Type: Summary


Session Scripts and Log Folder

The location where the server scripts and log folders are stored.

Default: CONFIG_HOME\tct\bpmnodetype\timestamp

Create New ActiveMatrix BPM Server Node Type

Whether to create a New ActiveMatrix BPM Server Node Type.

Default: Selected


| 145

Chapter 14 Create TIBCO ActiveMatrix BPM Server Wizard

This chapter provides reference information about the TIBCO Configuration Tool Configure TIBCO ActiveMatrix BPM Server wizard.

Topics


• ActiveMatrix BPM: Database Administrator, page 147

• ActiveMatrix BPM: Runtime Database Configuration, page 148

• ActiveMatrix BPM: Configuration, page 149

• ActiveMatrix BPM: Sizing Configuration, page 152

• ActiveMatrix BPM: JMS Configuration, page 153

• ActiveMatrix BPM: LDAP Configuration, page 154

• ActiveMatrix BPM: Administrator Server Configuration, page 156

• ActiveMatrix BPM: Host and Node Configuration, page 157


146 | Chapter 14 Create TIBCO ActiveMatrix BPM Server Wizard

Welcome




Select this check box to pre-select all "SSL enabled" check boxes in subsequent pages of this wizard. (You will be able to override this choice and select or clear those check boxes on their individual pages.)

Default: Cleared


ActiveMatrix BPM: Database Administrator | 147



Create BPM Database Instance

Whether TIBCO Configuration Tool should automatically create the ActiveMatrix BPM database. When selected, the remaining fields on this page are available.

When cleared, you must manually create the database instead, using the scripts generated from the ActiveMatrix BPM: Runtime Database Configuration screen. See Manually Running the ActiveMatrix BPM Database Creation Scripts for more information about how to do this.

Default: Selected

Database Driver Database driver used to connect to the database server that hosts the BPM database. The drivers available are those that have been previously installed using the TIBCO Configuration Tool Configure Third-Party Driver Wizard.

URL JDBC connection string needed to connect to the database server.

DBA Username Credentials of a database server user account that has system administrator privileges.

TIBCO Configuration Tool will use this account to connect to the database server to create the BPM database.

DBA Password Password for the specified DBA Username.

Tablespace Name Name of the Oracle tablespace in which the BPM database will be created:

• TIBCO Configuration Tool will create this tablespace if it does not already exist.

• The BPM and Administrator databases must use separate tablespaces.

If the BPM database is being hosted on SQL Server or DB2 this field is ignored.

Default: bpm_tablespace

Test Connection Verifies that TIBCO Configuration Tool can connect to the database server using the information supplied on this page.





URL JDBC connection string that ActiveMatrix BPM should use to connect to the ActiveMatrix BPM database.

Username Database server user account that ActiveMatrix BPM should use to connect to the ActiveMatrix BPM database. TIBCO Configuration Tool automatically creates the specified account if it does not already exist.

If you are using a DB2 database, this must be the name of an existing operating system user - see Configuring DB2 on page 81.

Default: bpmuser

Password Password for the specified Username.

Confirm Password Password for the specified Username.

Test Connection Verifies that TIBCO Configuration Tool can connect to the ActiveMatrix BPM database using the information supplied on this page.

This field is only enabled if you chose to manually create the database in the ActiveMatrix BPM: Database Administrator screen. Connection will only be possible when:

1. You have generated the database creation scripts (by clicking Generate Scripts).

2. The database administrator has run the database creation scripts.

Note: The database administrator must run the database creation scripts before you click Configure in the Summary screen at the end of this wizard.

Generate Scripts Generates the SQL scripts needed to create the ActiveMatrix BPM database. The scripts are saved in the folder CONFIG_HOME\bpm\database.

You should generate the database creation scripts if you chose to manually create the database in the ActiveMatrix BPM: Database Administrator screen. See Manually Running the ActiveMatrix BPM Database Creation Scripts for more information about how to manually create the database.


ActiveMatrix BPM: Configuration | 149

ActiveMatrix BPM: Configuration


HTTP Work Presentation Host

Name used to externally identify the machine that hosts ActiveMatrix BPM.

This name is used when Work Manager distributes work using the push distribution model. When a user receives an email notification of a work item, the specified name is embedded in the URL in the email body that the user clicks to access the work item. (See "Work Management > Distributing Work to Users" in TIBCO ActiveMatrix BPM Concepts for more information.)

Note: If ActiveMatrix BPM nodes are distributed over different machines (to provide high availability and/or scalability), this should be the name of the load balancer. See Load Balancer.

This name must be specified using a fully qualified domain name or IP address that is accessible to external clients. For example, this may be the name of the machine itself or of a proxy server.

Default: localhost

HTTP Port HTTP port number used by this BPM node for communication with external clients (Openspace, Workspace and custom client applications).

This port must not be in use by another node on the same machine.


Default: 8080

SMTP Host Name of the machine that hosts the SMTP server that is used by ActiveMatrix BPM to send pushed email work notifications and to execute email service tasks.

If the machine is not the one on which TIBCO ActiveMatrix BPM is running, its name must be specified using a fully qualified domain name or IP address.

Default: localhost

SMTP Port Port number on which the SMTP server is running.

Default: 25



Override BPM Configuration Folder

Whether to override the default location of the BPM configuration folder. Select this if ActiveMatrix BPM nodes are distributed over different machines (to provide high availability and/or scalability).

If selected, the Configuration Folder field is displayed.

Default: Cleared

Configuration Folder

The location of the BPM configuration folder.

If ActiveMatrix BPM nodes are distributed over different machines (to provide high availability and/or scalability), this must be a location on a suitable shared network drive. For example, SHARED_DIR\bpm_config - see Shared File System.

Default: CONFIG_HOME\bpm

Enable SSL for HTTP Port

Whether communication between ActiveMatrix BPM and clients (Workspace, Openspace or custom client applications) should be secured by SSL.

Note: If this option is enabled when ActiveMatrix BPM nodes are distributed over different machines (to provide high availability and/or scalability):

• The keystore containing the certificate to be used when a client requests an SSL connection using the httpConnector (by default, install-server-store.jks) must be stored in SHARED_DIR\keystores - see Shared File System.

• In TIBCO Administrator, the Keystore Provider resource template (by default, KeystoreCspRT) must be configured to reference the keystore on the shared network drive.

See "Enabling SSL Communication with TIBCO ActiveMatrix BPM Runtime Clients" in TIBCO ActiveMatrix BPM - BPM Administration for more information.

Default: Follows the value selected for Configure to Secure All Communication with SSL.

SSL Configuration fields (only visible if Enable SSL for HTTP Port is selected)

Self-signed Certificate

Indicates that ActiveMatrix BPM will identify itself to clients with a self-signed certificate generated by the TIBCO Credential Server (see Administrator Server Configuration: Credential Server Details).

Note: Do not use a self-signed certificate in a production environment.

Default: Selected



ActiveMatrix BPM: Configuration | 151

Imported Certificate

Indicates that ActiveMatrix BPM will identify itself to clients with a certificate that should be imported into ActiveMatrix Administrator.

When selected, the Keystore fields are enabled.

Default: Cleared

Keystore Location The location of the keystore to import.

Keystore Type The type of the keystore: JCEKS, JKS or PKCS12

Default: JKS

Keystore Password The password required to access the keystore.

Key Alias The key alias that identifies the ActiveMatrix BPM entry in the keystore.

Key Password The password required to access the key alias.

Verify Keystore Verifies that TIBCO Configuration Tool can connect to the keystore and retrieve the alias using the information supplied on this page.




ActiveMatrix BPM: Sizing Configuration


Environment Type of environment being set up. Choose from the options: Development and Production.

The environment you choose in this field determines the default values provided for the remaining fields on this screen.

Default: Development

Database Connection Pool Size

Number of database connections available for each of the ActiveMatrix BPM DataSource resource templates.

Development default: 10

Production default: 50

Database Statement Cache Size

Number of prepared statements that can be cached by each connection in the DataSource resource template pool. Caching prepared statements improves the performance but it uses more memory.



Number of Process Engine Threads

Number of threads in the Process Engine background thread pool.



Max Java PermGen Size

Maximum size for Java PermGen.



Number of Message Threads

Range for the message threads.

Development default: Core: 5 Maximum: 10

Production default: Core: 10 Maximum: 20

Java Heap Size Range for the Java heap size.

Development default: Minimum: 512 Maximum: 1024

Production default: Minimum: 1024 Maximum: 4096


ActiveMatrix BPM: JMS Configuration | 153

ActiveMatrix BPM: JMS Configuration

This information is used to create the following BPM runtime resource templates/instances, which ActiveMatrix BPM uses to communicate with the EMS server.

See "Resource Templates > Shared Resource Templates" in TIBCO ActiveMatrix BPM - SOA Administration for more information about these shared resources.


JMS Url The URL of the EMS server to be used by ActiveMatrix BPM. (See Configure TIBCO Enterprise Message Service on page 76.)

Default: tibjmsnaming://localhost:7222

Initial Context The initial context factory to use for the JNDI lookup of the EMS server. TIBCO recommend that you do not change the default value.

Default: com.tibco.tibjms.naming.TibjmsInitialContextfactory

Connection Factory

The name of the connection factory used to create the connection to the EMS server. TIBCO recommend that you do not change the default value.

Default: GenericConnectionFactory

amxbpm request queue

The name of the EMS server queue that ActiveMatrix BPM uses to receive messages. TIBCO recommend that you do not change the default value.

Default: queue.sample

Type Name Description

JNDI Connection amx.bpm.userapp.jndiConnConf Provides a JNDI connection to look up the EMS server.

JMS Connection Factory Configuration

amx.bpm.userapp.jmsConnFactoryConf These two are used (with the JNDI Connection) to establish inbound communication with the EMS server.

JMS Destination Configuration

amx.bpm.userapp.jms.request.conf

JMS Connection Factory

amx.bpm.userapp.jmsConnFactory Used (with the JNDI Connection) to establish outbound communication with the EMS server.





Deploy Internal LDAP Server

Whether to use the internal LDAP Directory Server provided with ActiveMatrix BPM. When selected, the Port Number field is enabled.

Note: If ActiveMatrix BPM nodes are distributed over different machines (to provide high availability and/or scalability), an external LDAP server must be used. See Additional System Requirements for a High Availability or Distributed BPM Configuration.

Default: Selected

Port Number Port number used by the internal LDAP server.

Default: 10801

Use External LDAP Server

Whether to use an external LDAP directory server (see Configure the External LDAP Directory Server on page 82). When selected, the LDAP Provider Details fields are enabled.

Default: Cleared

Provider Details:

URL URL used to log in to the external LDAP server.

Default: ldap://localhost:10389

Base DN Base Distinguished Name (DN) from which to search/navigate the LDAP directory.

Default: OU=system

Username: Distinguished Name of the LDAP user who will be used as the tibco-admin user.

Note: This user must have (at least) read access to the LDAP directory specified by Base DN.

Default:uid=admin,ou=system

Password: Password of the specified LDAP user.


ActiveMatrix BPM: LDAP Configuration | 155

LDAP Server is SSL Enabled

Whether the external LDAP server is enabled for SSL. When selected, the SSL Trust Store Configuration fields are enabled.


Test Connection

Verifies that TIBCO Configuration Tool can connect to the LDAP server using the information supplied on this page.

SSL Trust Store Configuration:

Create a Trust Store

Obtains certificates from the specified LDAP server and creates a new trust store, which will be used to establish the trust relationship with the external LDAP server:

1. Click Create a Trust Store.

2. Specify a password to protect the keystore and click Next >. The SSL setup wizard displays the certificates imported from the external LDAP server.

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

If you do not click Create a Trust Store, you must specify the details of an existing trust store that can be used to establish the trust relationship with the external LDAP server.

Trust Store Location

Either:

• the location in which the created trust store will be stored, or

• the location of the trust store to be uploaded to ActiveMatrix Administrator. (You can either type this directly or use the Browse button to find it.)

Trust Keystore Type

The type of the created or uploaded trust store: JKS or JCEKS.

Default: JKS.

Trust Store Password

Either:

• the password specified in the Create a Trust Store wizard, or

• the password required to access the trust store that is to be uploaded.






Use Existing ActiveMatrix Administrator Server

Whether to use an existing ActiveMatrix Administrator server. If selected the remaining fields on the screen are enabled. (In this case, the ActiveMatrix BPM: Host and Node Configuration screen is displayed when you click Next on this screen.)

When cleared, you use subsequent screens in the wizard to create a new ActiveMatrix Administrator server - see Create TIBCO ActiveMatrix Administrator Server Wizard on page 159 for more detailed information about the remaining screens. (In this case, the Administrator Server Configuration: Details screen is displayed when you click Next on this screen.)

Default: Selected

Machine Name

Name of the machine on which the ActiveMatrix Administrator server is running. The value of this property must either be a hostname resolvable through DNS or 0.0.0.0; it cannot be an IP address.

Port Browser port used to access the ActiveMatrix Administrator server.


Default: 8120

Username ID of the ActiveMatrix Administrator superuser.

Default: root

Password Password of the ActiveMatrix Administrator superuser.

Default: t

Admin server is SSL enabled

Whether the Administrator server internal port is enabled for SSL. When selected, the SSL Keystore Configuration fields are enabled.


Test Connection

Verifies that TIBCO Configuration Tool can connect to the Administrator server using the information supplied on this page.


ActiveMatrix BPM: Host and Node Configuration | 157

ActiveMatrix BPM: Host and Node Configuration

This screen is only displayed if you selected Use Existing ActiveMatrix Administrator Server in the ActiveMatrix BPM: Administrator Server Configuration screen.

The Administrator Server Configuration: Summary screen is displayed when you click Next on this screen.


Host Name of the TIBCO Host instance on which the Administrator Server is running.

Default: None

Environment Name

Name of the environment that contains the BPM node.

Default: BPMEnvironment

Node Name Name of the BPM node.

Default: BPMNode

Node Management Port

Management port number used by the node. This port must not be in use by another node on the same machine.

Default: 6031


| 159

Chapter 15 Create TIBCO ActiveMatrix Administrator Server Wizard

This chapter provides reference information about the TIBCO Configuration Tool Configure TIBCO ActiveMatrix Administrator Server wizard.

Topics


• Administrator Server Configuration: Details, page 162

• Administrator Server Configuration: TIBCO Host Configuration, page 163

• Administrator Server Configuration: Connection Settings, page 164

• Administrator Server Configuration: Internal HTTP Settings, page 166

• Administrator Server Configuration: Notification and Messaging Bus Server, page 167

• Administrator Server Configuration: Database Details, page 168

• Administrator Server Configuration: Authentication Realm, page 169

• Administrator Server Configuration: Database Authentication Realm Details, page 170

• Administrator Server Configuration: LDAP Authentication Realm Details, page 171

• Administrator Server Configuration: Credential Server Details, page 174

• Administrator Server Configuration: Credential Server Keystore, page 175

• Administrator Server Configuration: Monitoring Notification Server, page 176

• Administrator Server Configuration: Monitoring Database Configuration, page 177

• Administrator Server Configuration: Monitoring Configuration, page 178

• Administrator Server Configuration: Log Service Database Configuration, page 179


160 | Chapter 15 Create TIBCO ActiveMatrix Administrator Server Wizard

• Administrator Server Configuration: Payload Service Database Configuration, page 180

• Administrator Server Configuration: Summary, page 181


Welcome | 161

Welcome




Default: Cleared



Administrator Server Configuration: Details

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.

The TIBCO Enterprise Message Service server that you specify in Administrator Server Configuration: Notification and Messaging Bus Server acts as the notification server for the enterprise.

Note: If multiple enterprises exist, each must use a different TIBCO Enterprise Message Service server.

Default: AMX BPM.

Server Name The name of the ActiveMatrix Administrator server.

Default: AMXBPM Server.


Administrator Server Configuration: TIBCO Host Configuration | 163

Administrator Server Configuration: TIBCO Host Configuration

Field Description

Machine Name

Name of the machine on which the TIBCO Host instance runs. The value of this property must either be a hostname resolvable through DNS or 0.0.0.0; it cannot be an IP address.

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

Port Management port of the TIBCO Host instance.

Default: 6051

Register as Windows Service

Indicate whether the TIBCO Host instance should be registered as a Windows service named TIBCO ActiveMatrix Admin-enterpriseName-serverName with startup type Automatic. The service is not started.

Default: Cleared

Create Windows Shortcut

Indicate whether a shortcut named TIBCO ActiveMatrix Admin-enterpriseName-serverName that points to CONFIG_HOME\tibcohost\Admin-enterpriseName-serverName\host\bin\tibcohost.exe should be added to the Windows desktop.

Default: Cleared

Customize BPM Node

Indicate whether to customize the BPM environment and node. When selected, the Environment Name, Node Name, and Node Management Port fields display.

Default: Selected

Environment Name

Name of the environment that contains the node.

Default: BPM Environment

Node Name Name of the BPM node.

Default: BPMNode

Node Management Port

Management port of the BPM node.

Default: 6031



Administrator Server Configuration: Connection Settings

Field Description

Bind to Network Adapter

The address of the network adapter on the machine on which the ActiveMatrix Administrator server runs. The default is set to 0.0.0.0 so that ActiveMatrix Administrator will listen on all network adapters (including http://localhost and http://hostname) so that clients can connect to the ActiveMatrix Administrator server using any of the conventions (localhost, IP address, hostname). The value of this property must either be a hostname resolvable through DNS or 0.0.0.0; it cannot be an IP address.

Default: 0.0.0.0

Management Port

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

Default: 6021

External HTTP Port

The number of the external ActiveMatrix Administrator HTTP port.

Default: 8120

Browser Idle Session Timeout(m)

The length of time before an ActiveMatrix Administrator GUI login session times out due to inactivity. This value cannot be changed after the ActiveMatrix Administrator server is created.

Default: 30 (minutes)

Enable SSL for External HTTP Port

Indicate whether communication between ActiveMatrix Administrator server and clients should be secured with SSL. When selected, the Self-Signed Certificate and Imported Certificate radio buttons display.

Default: Cleared

Self-Signed Certificate

Indicate that ActiveMatrix Administrator server will identify itself to clients with a self-signed certificate generated by TIBCO Credential Server (see Administrator Server Configuration: Credential Server Details). This option is selected by default.

A self-signed certificate should not be employed in production environments.

Imported Certificate

Indicate that ActiveMatrix Administrator server will identify itself to clients with a certificate imported into ActiveMatrix Administrator server. When selected, the Keystore fields are enabled.


Administrator Server Configuration: Connection Settings | 165

Keystore Location

The location of the keystore to import.

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

Default: JKS

Keystore Password

The password that protects the keystore.

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

Key Password The password that protects the key alias.

Field Description



Administrator Server Configuration: Internal HTTP Settings

Field Description

Internal HTTP Port

The number of the internal ActiveMatrix Administrator HTTP port.

Default: 19767

Enable SSL for Internal HTTP Port

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

Default: Cleared

Use Load Balancer for Internal HTTP Communication

Indicate that an HTTP load balancer will be used to distribute requests from hosts to the ActiveMatrix Administrator server’s internal HTTP port.

When the ActiveMatrix Administrator server is replicated on two machines, you should use an HTTP load balancer so that traffic between hosts and ActiveMatrix Administrator server will support a load-balanced and fault-tolerant mode. Without a load balancer if one ActiveMatrix Administrator server is unavailable, hosts will be unable to download software artifacts. When selected, the Load Balancer 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.


Administrator Server Configuration: Notification and Messaging Bus Server | 167

Administrator Server Configuration: Notification and Messaging Bus Server


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.

Username A username for the TIBCO Enterprise Message Service server. The user must have administrator privileges in the TIBCO Enterprise Message Service server. If the user does not have administrator privileges, see TIBCO Enterprise Message Service Server Configuration.

Default: admin

Password A password for the TIBCO Enterprise Message Service user.

Default: None

TIBCO Enterprise Message Service Server is SSL Enabled

Indicate that the TIBCO Enterprise Message Service server is enabled for SSL. When selected, the SSL Keystore Configuration fields are enabled. The TIBCO Enterprise Message Service server usually listens on port 7243 when SSL-enabled and you must update the value in the Machine Name Port List field before proceeding with SSL configuration.





Use Default In-Process Database

Indicate that the ActiveMatrix Administrator server database is an embedded in-process database. If cleared, the external database configuration fields display.

Default: Cleared

Database Driver

The driver for the external database.

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

Max Connections

The maximum number of database connections to allocate.

Default: 10

Database Server is SSL Enabled

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

Test Connection

Verifies that TIBCO Configuration Tool can connect to the database server using the information supplied on this page.


Administrator Server Configuration: Authentication Realm | 169

Administrator Server Configuration: Authentication Realm

Field Description

Authentication Realm

Realm Type The type of the authentication realm: Database or LDAP. If Database, the Administrator Server Configuration: Database Authentication Realm Details screen displays. If LDAP, the Administrator Server Configuration: LDAP Authentication Realm Details screens display.

Superuser Credentials

Username The ID of the initial superuser.

Default: root

Password The password of the superuser.

Default: t



Administrator Server Configuration: 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: Selected. If cleared, the database configuration fields in Administrator Server Configuration: Database Details display.

Database Driver

The driver for the external database.

Default: org.hsqldb.jdbcDriver




Default: sa


Default: None

Max Connections

The maximum number of database connections to allocate.

Default: 10

Database Server is SSL Enabled

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


Administrator Server Configuration: LDAP Authentication Realm Details | 171

Administrator Server Configuration: 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. To achieve fault tolerance, you can specify multiple URLs separated by spaces. For example, ldaps://server1.example.com:686 ldaps:server2.example.com:1686.

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 (ms)

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

Default: -1, which means to use the provider’s default.



Field Description

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.

Default: Group Has User Members.

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.

Attribute with group’s name The name of the attribute in the user object that lists the groups to which the user belongs.

Default: None


Administrator Server Configuration: LDAP Authentication Realm Details | 173

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.

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.

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 Server is SSL-enabled

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

Field Description




Field Description

Bind to Network Adapter The address of the network adapter on the machine on which the Credential Server runs. The default is set to 0.0.0.0 so that the Credential Server will listen on all network adapters (including http://localhost and http://hostname) so that clients can connect to the Credential Server using any of the conventions (localhost, IP address, hostname). The value of this property must either be a hostname resolvable through DNS or 0.0.0.0; it cannot be an IP address.

Default: 0.0.0.0

Port The management port number of the node, SystemNode, that runs the TIBCO Credential Server.

Default: 6041

Username A user identifier for TIBCO Credential Server clients.

Default: user1

Password The password for the client.

Default: password1


Administrator Server Configuration: Credential Server Keystore | 175

Administrator Server Configuration: Credential Server Keystore

Field Description

Auto-generated Keystore

Indicate 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

Indicate that the TIBCO Credential Server keystore will be provided. When selected, the keystore fields display.

Keystore Location

The location of the keystore.

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.



Administrator Server Configuration: Monitoring Notification Server

Field Description

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



Default: admin


Default: None




Administrator Server Configuration: Monitoring Database Configuration | 177

Administrator Server Configuration: Monitoring Database Configuration

Field Description

Use ActiveMatrix Administrator Server Database

Indicate that the monitoring service should use the same database as the ActiveMatrix Administrator server.

Default: Selected. If cleared, the notification server fields in Administrator Server Configuration: Database Details display.

Database Driver The driver for the external database.

Default: org.hsqldb.jdbcDriver




Default: sa


Default: None

Max Connections The maximum number of database connections to allocate.

Default: 30

Database Server is SSL Enabled Indicate that the database server is enabled for SSL. When selected, the SSL Keystore Configuration fields are enabled.



Administrator Server Configuration: Monitoring Configuration

Field Description

Enable Extended Monitoring

Indicate that the monitoring system should capture extended statistics. Basic statistics include the 1 hour and since started time windows and a selected number of important metrics such as status, hits, faults, response time. Extended statistics provide more time windows and additional metrics and thus impose a larger processing burden.

Default: Cleared


Administrator Server Configuration: Log Service Database Configuration | 179

Administrator Server Configuration: Log Service Database Configuration

Field Description


Indicate that the log service should use the same database as the ActiveMatrix Administrator server.

Default: Selected. If cleared, the remaining fields display.

Use Default In-Process Database Indicate that the ActiveMatrix Administrator server database is an embedded in-process database. If unchecked, the external database configuration fields display.

Default: Checked.


Default: org.hsqldb.jdbcDriver.


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


Default: sa.


Default: None.


Default: 5.

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



Administrator Server Configuration: Payload Service Database Configuration

Field Description


Indicate that the payload service should use the same database as the ActiveMatrix Administrator server.

Default: Selected. If cleared, the remaining fields display.

Use Default In-Process Database Indicate that the ActiveMatrix Administrator server database is an embedded in-process database. If unchecked, the external database configuration fields display.

Default: Checked.


Default: org.hsqldb.jdbcDriver.


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


Default: sa.


Default: None.


Default: 5.

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


Administrator Server Configuration: Summary | 181



Session Scripts and Log Folder

The location where the server scripts and log folders are stored.

Default: If you are running the:

• Create TIBCO ActiveMatrix Administrator Server Wizard - CONFIG_HOME\tct\admin\timestamp

• Create TIBCO ActiveMatrix BPM Server Wizard - CONFIG_HOME\tct\bpm\timestamp

Administrator URL The URL to be used to access the ActiveMatrix Administrator web interface.

Default: http://machineName:port/amxadministrator/loginForm.jsp

where:

• machineName is the name of the machine on which you are running TIBCO Configuration Tool.

• port is the External HTTP Port number specified in the Administrator Server Configuration: Connection Settings screen.

Click Configure to execute the following actions:

Create TIBCO ActiveMatrix Administrator server

Whether to create the ActiveMatrix Administrator server.

Note: If you are running the Create TIBCO ActiveMatrix BPM Server Wizard, this option is only displayed if you cleared Use Existing ActiveMatrix Administrator Server in the ActiveMatrix BPM: Administrator Server Configuration screen.

Default: Selected

Deploy Monitoring Service

Whether to deploy the ActiveMatrix monitoring service.

Default: Selected

Deploy Log Service Whether to deploy the ActiveMatrix logging service.

Default: Selected



Create ActiveMatrix BPM Whether to create the ActiveMatrix BPM runtime and the ActiveMatrix BPM database.

Note: This option is only displayed if you are running the Create TIBCO ActiveMatrix BPM Server Wizard.

The message [Not Creating Database Instance] is displayed if you chose not to create the ActiveMatrix BPM database in the ActiveMatrix BPM: Database Administrator screen (by clearing Create BPM Database Instance).

In this case, TIBCO Configuration Tool will not automatically create the ActiveMatrix BPM database, and you must manually create it instead - see Manually Running the ActiveMatrix BPM Database Creation Scripts for more information.

Default: Selected

Select the products to deploy

TIBCO ActiveMatrix Mediation Implementation Type Application

Note: This option is only displayed if you are running the Create TIBCO ActiveMatrix Administrator Server Wizard.

Default: Selected



| 183

Chapter 16 Create TIBCO Host Instance Wizard

This chapter provides reference information about the TIBCO Configuration Tool Create TIBCO Host Instance wizard.

Topics


• TIBCO Host instance Configuration: Details, page 185

• TIBCO Host instance Configuration: Notification Server, page 186

• TIBCO Host instance Configuration: Administrator Server, page 187


184 | Chapter 16 Create TIBCO Host Instance Wizard

Welcome



Whether all communication channels used by this TIBCO Host instance should be secured with SSL.

Select this check box to pre-select all "SSL enabled" check boxes in subsequent pages of this wizard. (You will be able to override this choice and select or clear those check boxes on their individual pages.)

Default: Cleared


TIBCO Host instance Configuration: Details | 185

TIBCO Host instance Configuration: Details

Field Description

Name The name of the TIBCO Host instance. The name must be unique within the enterprise.

Default: None

Enterprise Name

The name of the 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. The value of this property must either be a hostname resolvable through DNS or 0.0.0.0; it cannot be an IP address.

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

Indicate whether the TIBCO Host instance should be registered as a Windows service named TIBCO ActiveMatrix instanceName, where instanceName is the name you specified in the Name field, with startup type Automatic. The service is not started.

Default: Cleared

Create Windows Shortcut

Indicate whether to create a shortcut named instanceName, where instanceName is the name you specified in the Name field, that points to CONFIG_HOME\tibcohost\instanceName\host\bin\tibcohost.exe, to the Windows desktop.

Default: Cleared



TIBCO Host instance Configuration: Notification Server

Field Description


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



Default: admin


Default: None




TIBCO Host instance Configuration: Administrator Server | 187

TIBCO Host instance Configuration: Administrator Server

Field Description

Bind to Administrator Server Indicate whether to bind the TIBCO Host instance to an Administrator server. When selected the Administrator server configuration fields are enabled.

Default: Selected

Machine Name The name of the machine on which the Administrator server is running. The value of this property must either be a hostname resolvable through DNS or 0.0.0.0; it cannot be an IP address.

Port The browser port used to access the Administrator server.

Default: 8120

Username The ID of the initial superuser.

Default: root

Password The password of the superuser.

Default: t

Admin Server is SSL Enabled Indicate that the Administrator server internal port (see Administrator Server Configuration: Internal HTTP Settings) is enabled for SSL. When selected, the SSL Keystore Configuration fields are enabled.


| 189

Chapter 17 Configure Third-Party Driver Wizard

This chapter provides reference information about the TIBCO Configuration Tool Configure Third-Party Driver wizard.

Topics

• Third-Party Driver: Details, page 190

• Third-Party Driver: JAR Folder, page 191


190 | Chapter 17 Configure Third-Party Driver Wizard

Third-Party Driver: Details

Field Description

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

Default: JDBC

Driver The supported drivers:

• JDBC







• JMS

— TIBCO enabled JMS client for Sonic 6.1.0

— TIBCO enabled JMS client for WebSphere 7.0.03

Silentinstall prompt: tpcl.

1. Not supported for ActiveMatrix BPM.

2. Not supported for ActiveMatrix Administrator and ActiveMatrix JDBC resource templates.

3. Support for WebSphere MQ 6.0 is based on the backward compatibility of the Websphere MQ 7.0 client library. When a JMS binding is configured with JMS topics and needs to work with WebSphere MQ 6.0, you must provide the 7.0.1.3 version of the client library.


Third-Party Driver: JAR Folder | 191

Third-Party Driver: JAR Folder

Field Description

JAR Folder The folder containing the client driver JARs to install in the ActiveMatrix Administrator server software repository.

Silentinstall prompt: source.jar.folders


192 | Chapter 17 Configure Third-Party Driver Wizard


| 193

IV - APPENDICES

The following appendices provide additional information that you may need when installing or upgrading ActiveMatrix BPM.

Topics

• Troubleshooting Installation, page 195

• Restoring ActiveMatrix BPM from a Backup, page 197

• Uninstalling an ActiveMatrix BPM System, page 199

• Disaster Recovery Using Data-Level Replication, page 203

• Disaster Recovery Using Device-Level Replication, page 221

• Securing Communication Channels, page 223

• TIBCO Enterprise Message Service Server Configuration, page 227

• Using Third-Party Solutions to Configure a High Availability, Fault Tolerant ActiveMatrix BPM System, page 231


194 | IV - APPENDICES


| 195

Appendix A Troubleshooting Installation

If you encounter problems with installation, make sure that your system meets all prerequisites. Next, check the installer log file for potential problems.

Installer Log FileThe installer log file, tibco_universal_installer.username_install.log, is written to the .TIBCO/install_timestamp folder of the user’s home directory. To change the location of the installer log file, specify the option -V logFile="myLogFile" when you run the installer.

The installer log file captures the following information:

• Installation environment details such as user that invoked the installer, operating system details, installer mode, host name, JAVA_HOME and the Java version available in that environment, and so on.

• List of assemblies installed.

• Information related to the Ant scripts that are executed by the installer is logged in separate log files antTask_log_scriptname_timestamp under the folder install_timestamp.

Sanitizing After a Failed InstallationAn installation process can fail at various stages and the installer may not be able to clean up the environment before exiting. It is recommended that you clean up the environment manually before trying to re-install the product.

Consider a simple environment with a single node (BPMNode) on a single host. To sanitize this environment after a failed installation, perform the following steps in the specified order.

1. Shutdown TIBCO Configuration Tool (TIBCO Configuration Tool).

2. Stop any processes running from CONFIG_HOME. For example, tibcohost, tibamx_SystemNode, and tibamx_BPMNode.

3. Delete the BPM configuration directory specified during the installation. For example, if you chose to use the default configuration directory when


196 | Appendix A Troubleshooting Installation

installing on Windows, delete the folder C:\ProgramData\amx-bpm\tibco\data.

The above steps are applicable for a single node environment. Similar steps may be applied to clean up an active-active or a distributed environment. The actual steps however will have to be customized to the environment that needs to be cleaned.


| 197

Appendix B Restoring ActiveMatrix BPM from a Backup

To restore TIBCO ActiveMatrix BPM from a backup, do the following:

1. Shutdown TIBCO ActiveMatrix BPM. Refer to TIBCO ActiveMatrix BPM - BPM Administration for more information.

2. Shutdown the TIBCO Enterprise Message Service server. Refer to the documentation supplied with TIBCO Enterprise Message Service for information.

3. Copy the contents of TIBCO_HOME and CONFIG_HOME directories from the backup to their original location.

4. Recover the TIBCO ActiveMatrix BPM database and make sure the database is online. Refer to the documentation provided with your database for information.

5. Recover the TIBCO ActiveMatrix Administrator database. Refer to the documentation provided with TIBCO ActiveMatrix Administrator for information.

6. Recover the TIBCO Enterprise Message Service server. Refer to the documentation supplied with TIBCO EMS for information.

7. Restart the TIBCO Enterprise Message Service server. Refer to the documentation supplied with TIBCO EMS Server for information.

8. Restart TIBCO ActiveMatrix BPM. Refer to TIBCO ActiveMatrix BPM - BPM Administration for more information.

9. Check that all the TIBCO ActiveMatrix BPM components are running. To do this:

a. Login to TIBCO Administrator.

b. Click Applications.

— Make sure the TIBCO ActiveMatrix BPM applications have a status of Running.

— Make sure your project applications are in the correct state (in other words, in the same state as they were at the time of back-up).


198 | Appendix B Restoring ActiveMatrix BPM from a Backup


| 199

Appendix C Uninstalling an ActiveMatrix BPM System

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

1. Stop the TIBCO Host instance, node processes, and TIBCO Business Studio.

2. Use the uninstaller provided with TIBCO ActiveMatrix BPM. See Using the Uninstaller on page 199

3. Manually delete the TIBCO ActiveMatrix BPM directories under TIBCO_HOME.

4. Manually delete the TIBCO ActiveMatrix BPM directories under CONFIG_HOME.

Using the UninstallerTo use the uninstaller:

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

— On Windows: log in as a user with Administrator privileges. You must have Administrator privileges to uninstall this software.

— On UNIX/Linux: you should uninstall as the same user who did the installation. If more than one product installation has been made to the same environment and you want to uninstall them all, you should uninstall using the root user.

2. Do one of the following:

On Windows:

— Go to Start > All Programs > TIBCO > env_name and click on Uninstall. Alternately, you can navigate to the installation_environment\tools\universal_installer folder and run TIBCOUniversalInstaller.exe.


200 | Appendix C Uninstalling an ActiveMatrix BPM System

On UNIX/Linux:

— Navigate to the installation_environment/tools/universal_installer folder and run ./TIBCOUniversalInstaller-platform_id.extension

3. The TIBCO Installation Manager screen is displayed. Choose the option Uninstall Products from Selected TIBCO Home Location and then choose the location of TIBCO Home from the drop-down. Click Next.

4. The TIBCO Universal Uninstaller is launched and the Welcome screen is displayed. Click Next.

5. Select either Custom Uninstall (to select the products in this environment to be uninstalled) or Typical Uninstall to uninstall all products in this environment.

If you selected Typical Uninstall, continue with step 7.

If you selected Custom Uninstall, continue with the next step.

6. The Product Uninstall Selection screen is displayed.

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

7. The Pre-Uninstall Summary screen is displayed.

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

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

The uninstaller removes the software product you specified.

9. The Running ANT Tasks screen is displayed while the selected components are uninstalled. When prompted for the clean up of the /tools directory, click Yes, clean it up.

You can choose to uninstall the product in either GUI or console mode. Uninstalling the product in the silent mode is not supported.


Uninstalling an ActiveMatrix BPM System | 201

10. The Post Uninstall Summary is displayed. Review the information and then click Finish. The uninstaller exits and cleans up any temporary files.

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

— (UNIX/Linux only) - If an error message similar to the following is displayed after uninstallation, log out and log in again for the uninstaller changes to take effect:

The wizard requires that you logout and log back in


202 | Appendix C Uninstalling an ActiveMatrix BPM System


| 203

Appendix D Disaster Recovery Using Data-Level Replication

This appendix describes how to use file-based and database-based data replication solutions to provide a disaster recovery capability for a TIBCO ActiveMatrix BPM system.

Topics

• Data-Level Replication

• Configuring TIBCO ActiveMatrix BPM for Disaster Recovery on page 206

• Recovering TIBCO ActiveMatrix BPM if the Primary Site Fails on page 218


204 | Appendix D Disaster Recovery Using Data-Level Replication

Data-Level Replication

The data-level replication approach:

• requires only file-based and database-based replication software.

• ensures that data on the Disaster Recovery (DR) site will be in a consistent state across the various TIBCO ActiveMatrix BPM datastores and will therefore start-up when required.

TIBCO ActiveMatrix BPM maintains key system configuration and transaction data both on the file system and within relational databases. This data must be reliably replicated to the DR site.

Figure 4 provides an example of how this can be done, showing the data that needs to be replicated between the primary and DR site and the replication methods employed.

There are two types of data:

• non-operational - data that changes only as a result of management actions being performed upon the system (items 1 and 2 in the diagram).

• operational - data that changes continuously during the operation of the system (items 3, 4 and 5 in the diagram). This data must be consistent between the primary and DR sites. Synchronous replication of operational data is not a requirement, but asynchronous replication may cause loss of data.

If the primary site fails, there may be some data loss or lost state changes within executing business processes. The extent of this loss is determined by the latency of the replication of changes on the primary site to the DR site.


Data-Level Replication | 205

Figure 4 TIBCO ActiveMatrix BPM Disaster Recovery Configuration



Configuring TIBCO ActiveMatrix BPM for Disaster Recovery

To configure TIBCO ActiveMatrix BPM for disaster recovery, perform the following tasks:

• Task A, Create Host Aliases for TIBCO ActiveMatrix BPM System Components

• Task B, Create Service Name Aliases for TIBCO ActiveMatrix BPM Databases

• Task C, Store EMS Queues in the Oracle Database

• Task D, Run TIBCO Configuration Tool to configure TIBCO ActiveMatrix BPM to Use Aliases

• Task E, Enable Halt on Error Behavior

• Task F, Replicate TIBCO ActiveMatrix BPM File-Based Data

• Task G, Replicate TIBCO ActiveMatrix BPM Database-Based Data

This section provides a high-level overview of the steps involved in implementing a data-level replication solution for TIBCO ActiveMatrix BPM.

Familiarity with the following topics is assumed:

• underlying disaster recovery concepts, techniques and technologies

• file-based and database-based replication software

• TIBCO ActiveMatrix BPM architecture, installation and operation

• TIBCO Enterprise Message Service

Examples used in this section assume the use of the UNIX operating system, Oracle databases and Oracle Data Guard replication technology.

Contact TIBCO if you require further information about how the solution described in this section would apply to your specific TIBCO ActiveMatrix BPM implementation.


Configuring TIBCO ActiveMatrix BPM for Disaster Recovery | 207

Task A Create Host Aliases for TIBCO ActiveMatrix BPM System Components

On both the primary site and the DR site, create matching aliases for the hosts of the following TIBCO ActiveMatrix BPM system components:

• TIBCO ActiveMatrix BPM

• TIBCO ActiveMatrix BPM database server

• TIBCO ActiveMatrix Administrator

• TIBCO ActiveMatrix Administrator database server

• Enterprise Message Service server

• LDAP server

• SMTP server (if used)

• Public load balancer

Use a method that resolves host name aliases at the network level, such as a local in-datacenter DNS solution or a matching set of entries in the hosts files on both the primary site and the DR site. For example:

# TIBCO ActiveMatrix BPM - server: ip hostname aliasxx.xxx.xx.xx BPM_server_hostname amx-bpm-host

# TIBCO ActiveMatrix BPM - Database Server: ip hostname aliasxx.xxx.xx.xx Oracle_server_hostname amx-bpm-db-host

# TIBCO ActiveMatrix Administrator - server: ip hostname aliasxx.xxx.xx.xx Administrator_server_hostname amx-bpm-admin-host

# TIBCO ActiveMatrix Administrator - Database Server: ip hostname aliasxx.xxx.xx.xx Oracle_server_hostname amx-bpm-admin-db-host

# TIBCO ActiveMatrix Enterprise Message Service server: ip hostname aliasxx.xxx.xx.xx EMS_server_hostname amx-bpm-ems-host

# TIBCO ActiveMatrix BPM - LDAP Server: ip hostname aliasxx.xxx.xx.xx LDAP_server_hostname amx-bpm-ldap-host

# TIBCO ActiveMatrix BPM - SMTP Server: ip hostname aliasxx.xxx.xx.xx SMTP_server_hostname amx-bpm-smtp-host

# Public load balancer machine: ip hostname aliasxx.xxx.xx.xx Public_load_balancer_hostname amx-bpm-public-load-balancer



You will identify each component by its alias when you configure BPM - see Task D, Run TIBCO Configuration Tool to configure TIBCO ActiveMatrix BPM to Use Aliases.



Task B Create Service Name Aliases for TIBCO ActiveMatrix BPM Databases

On both the primary site and the DR site, create a service name alias that TIBCO ActiveMatrix BPM can use to identify the database to which it connects.

TIBCO ActiveMatrix BPM uses a JDBC connect string to identify the Oracle database to which it connects. The connect string identifies the database by its service name which, by default, is the same as its SID.

Because the databases on the primary and DR site have different SIDs, you must define an Oracle service name that TIBCO ActiveMatrix BPM can use as an alias, allowing it to connect to the database whether it is currently running on the primary system or the DR system.

The JDBC connect string can then be specified as:

jdbc:oracle:thin:@db-host-name:db-port-num/alias-service-name

instead of the default:

jdbc:oracle:thin:@db-host-name:db-port-num:service-name

You will specify the JDBC connect string when you configure:

• the EMS server - see Task C, Store EMS Queues in the Oracle Database.

• TIBCO ActiveMatrix BPM - see Task D, Run TIBCO Configuration Tool to configure TIBCO ActiveMatrix BPM to Use Aliases.

For example, to define an alias service name of amxbpmdb, run the following commands:

1. On the primary system database (which has a SID of main):

a. Verify that the SERVICE_NAMES parameter only contains a single name, which is the SID:

SHOW PARAMETER SERVICE_NAMES ;

b. Modify the SERVICE_NAMES parameter to add the amxbpmdb alias:

ALTER SYSTEM SET SERVICE_NAMES = 'main,amxbpmdb' ;

The use of an alias means that the physical location of the DBMS makes no difference to the recovery scenario.

Note that the service-name is preceded by a forward-slash character (’/’) not a colon (’:’).



2. Use the same commands on the DR system database (which has a SID of second):

SHOW PARAMETER SERVICE_NAMES ;ALTER SYSTEM SET SERVICE_NAMES = 'second,amxbpmdb' ;

The JDBC connect string can then be specified as:

jdbc:oracle:thin:@db-host-name:db-port-num/amxbpmdb



Task C Store EMS Queues in the Oracle Database

This section assumes that EMS is either installed on both the primary and DR sites, or else installed on the primary site and replicated on the DR site.

EMS messages used by BPM are written to queues in the EMS server’s $sys.nonfailsafe default store. By default, this is a file-based store on the EMS server.

To ensure that messages written to these queues are replicated, change the EMS server configuration so that $sys.nonfailsafe is defined as a database store in the same Oracle database used by BPM.

To do this, edit the $sys.nonfailsafe entry in the EMS server’s stores.conf file. Set the following fields:

• type - must be dbstore.

• dbstore_driver_url - must be the aliased JDBC connect string that identifies the Oracle database used by BPM (seeTask B, Create Service Name Aliases for TIBCO ActiveMatrix BPM Databases).

For example:

[$sys.nonfailsafe] type = dbstore dbstore_driver_url = jdbc:oracle:thin:@db-host-name:db-port-num/amxbpmdb dbstore_driver_username = username dbstore_driver_password = password

See the TIBCO Enterprise Message Service User’s Guide for more information.

Note that if you are using Windows rather than UNIX, installation of EMS creates services, which are not automatically replicated.

The $sys.nonfailsafe default store is not used exclusively by BPM, so this configuration may also result in non-BPM related messages being stored in the database.



Task D Run TIBCO Configuration Tool to configure TIBCO ActiveMatrix BPM to Use Aliases

Run the Tibco Configuration Tool and configure TIBCO ActiveMatrix BPM to use the created hostname and DB aliases:

1. On the Create TIBCO ActiveMatrix BPM Server wizard, use the indicated aliases in the following screens and fields.

2. On the Create TIBCO ActiveMatrix Administrator Server wizard, use the indicated aliases in the following screens and fields.

Screen Field Enter Example


URL Aliased JDBC connect string that identifies the Oracle database used by BPM

jdbc:oracle:thin:@amx-bpm-db-host:db-port-num/amxbpmdb

Runtime Database Configuration

URL Aliased JDBC connect string that identifies the Oracle database used by BPM


Client Configuration

HTTP Work Presentation Host

Hostname alias that identifies the public load balancer

amx-bpm-public-load-balancer

SMTP Host Hostname alias that identifies the SMTP server

amx-bpm-smtp-host

LDAP Configuration

URL Hostname alias that identifies the LDAP server

amx-bpm-ldap-host


TIBCO Host Instance

Machine Name Hostname alias that identifies the TIBCO ActiveMatrix Administrator server

amx-bpm-amx-host



Internal HTTP Port

Load Balancer URL (If required) Hostname alias that identifies the load balancer

amx-bpm-int-load-balancer

Notification and Messaging Bus Server


Hostname alias (and port) that identifies the EMS server used by TIBCO ActiveMatrix Administrator

amx-bpm-ems-host:7222

Database Details Database URL Aliased JDBC connect string that identifies the Oracle database used by BPM



If all of the TIBCO ActiveMatrix BPM components are installed on the same server, localhost can be specified as the hostname in all the fields defined above, with the exception of HTTP Work Presentation Host, which must use the defined alias. (This is because the hostname is embedded in the URL in work item notification emails for remote access from clients, so the URL must be the public address that clients use to access TIBCO ActiveMatrix BPM.)



Task E Enable Halt on Error Behavior

Enable TIBCO ActiveMatrix BPM’s haltOnError behavior so that, if the primary site fails, Process Manager halts any process instances that throw a Java exception as a result of the system error. You will then be able to resume the halted process instances when you restart TIBCO ActiveMatrix BPM on the DR site.

See "Configuring Error Handling Behavior for Process Instances" in TIBCO ActiveMatrix BPM - BPM Administration for more information.



Task F Replicate TIBCO ActiveMatrix BPM File-Based Data

Using your chosen file-based replication solution, replicate the contents of the following directories from the primary site to the DR site.

Directory Contents Replication requirements

TIBCO_HOME TIBCO ActiveMatrix BPM system software

Replicate this directory whenever there has been a change to the deployed TIBCO runtime software. For example, when:

• software has been installed.

• a hotfix, service pack or upgrade to an existing software component has been added.

CONFIG_HOME deployed application data (definitions and configurations)

Replicate this directory whenever there has been a change to any deployed applications or their configuration. For example, when:

• a change is made using ActiveMatrix Administrator (UI or CLI).

• an application is deployed or undeployed from TIBCO Business Studio.

Note: TIBCO ActiveMatrix BPM Transaction Manager state log files should not be replicated - see Transaction Manager Log Files.

EMS_CONFIG_HOME

configuration for TIBCO EMS

Replicate this directory whenever there has been a change to the EMS application or its configuration.

EMS_HOME TIBCO EMS software

Optional: you can either install EMS on the DR site, or else replicate this directory. See Task C, Store EMS Queues in the Oracle Database for further details.

Replicate this directory when there has been a change to the EMS runtime software.

The entire contents of each directory, including all child directories, must be replicated.



Transaction Manager Log Files

Each BPM node (for example, BPMNode), and the System node (SystemNode), has an embedded Transaction Manager (TxM), which logs its transaction state to files in the following directories:

CONFIG_HOME/tibcohost/Admin-enterpriseName-adminServerName/nodes/nodeName/work/HowlLogs

CONFIG_HOME/tibcohost/Admin-enterpriseName-adminServerName/nodes/nodeName/work/GeronimoTMID

Although transaction state data is stored in the file system, it changes as rapidly as other operational data. Consequently, if the primary site fails, some in-progress transactions may be lost.

To ensure data consistency between the primary and DR sites, TIBCO recommend that you do not replicate the HowlLogs and TxM GeronimoTMID log directories to the DR site.

If you do replicate the HowlLogs and TxM GeronimoTMID log directories to the DR site, you must remove any files from the HowlLogs and TxM GeronimoTMID log directories on the DR site before starting TIBCO ActiveMatrix BPM. See Before Starting TIBCO ActiveMatrix BPM.

TIBCO recommends the use of a real-time replication solution so that any update to either the TIBCO_HOME or CONFIG_HOME directory structure is automatically and immediately replicated. This removes any risk of administration changes performed on the primary site not being moved to the DR site within a suitable time.

If you chose to use a scheduled (e.g. nightly) rather than real-time solution, you should:

• initiate on-demand replication as the result of any administrative changes made on the primary site during the working day

• be willing to accept the risk of changes made between scheduled replications not being present on the DR site, along with any potential system corruption risks in the event that the DR site needs to be activated.



Task G Replicate TIBCO ActiveMatrix BPM Database-Based Data

Using your chosen database replication software, replicate the following databases from the primary site to the DR site:

Database Description

TIBCO ActiveMatrix BPM

Stores the runtime state of the TIBCO ActiveMatrix BPM system. Its rate of change is entirely dependent on flow of transactions (end user activity) through the BPM system.

TIBCO ActiveMatrix Administrator

Stores information pertaining to your TIBCO ActiveMatrix enterprise - for example, deployed applications.

EMS datastore Stores the EMS Server messages. See Store EMS Queues in the Oracle Database.

Custom database(s) Any custom databases required by the customer application.



Recovering TIBCO ActiveMatrix BPM if the Primary Site Fails

If the primary site fails, you can recover the system by starting TIBCO ActiveMatrix BPM on the secondary site. There are a number of tasks that you must do before, and after, starting TIBCO ActiveMatrix BPM.

Before Starting TIBCO ActiveMatrix BPMPerform the following tasks:

1. Promote your Oracle Data Guard DBMS on the secondary site to online status, and start all required support software (such as EMS) on the secondary site.

2. Roll back and purge any outstanding global transactions in the Oracle database associated with TIBCO ActiveMatrix BPM:

a. Using a text editor, open the script:

TIBCO_HOME\bpm\n.n\samples\DRscripts\clean-ora-tran.sh

b. In the line:

SQL_OS_USER=bpmuser

Replace the example value bpmuser with the name of the operating system account that runs TIBCO ActiveMatrix BPM. Save the file.

c. Using the Oracle system DBA account, run the clean-ora-tran.sh script. This script identifies any outstanding global transaction records associated with TIBCO ActiveMatrix BPM, and generates a bpm-tx-rollback.sql file that contains a set of SQL commands to purge them.

d. Review the generated bpm-tx-rollback.sql script to ensure that you are happy with the changes it will make to the database. For example, depending on what applications use the BPM database in your particular environment, there might be non-BPM transactions in the database: if so, do these need to be rolled back or not?

e. Using the Oracle SQLPlus utility, run the bpm-tx-rollback.sql script to purge the outstanding global transactions.


Recovering TIBCO ActiveMatrix BPM if the Primary Site Fails | 219

3. Purge all pending transactions in EMS. To do this:

a. As the EMS admin user, run the following script:

TIBCO_HOME\bpm\n.n\samples\DRscripts\clean-ems-tran.sh

(Make sure that the EMS server’s bin directory is in the PATH.) This script identifies any pended transactions, and generates an emsrollback.sh file that contains a set of tibemsadmin commands to purge them.

b. Review the generated emsrollback.sh script to ensure that you are happy with the changes it will make to the EMS datastore.

c. Use the following command to run the script and purge all pending transactions:

tibemsadmin -script emsrollback.sh

See the TIBCO Enterprise Message Service User’s Guide for more information.

4. Remove any TIBCO ActiveMatrix BPM nodename TxM log files from the following locations (if they exist):

CONFIG_HOME/tibcohost/Admin-enterpriseName-adminServerName/nodes/nodeName/work/HowlLogs

CONFIG_HOME/tibcohost/Admin-enterpriseName-adminServerName/nodes/nodeName/work/GeronimoTMID

where nodeName is the name of each node on the system - for example, BPMnode and SystemNode. See Transaction Manager Log Files for more information.

5. Remove the following lock files, if they exist. (These files may or may not exist, depending on the file replication system being used.)

CONFIG_HOME/tibcohost/Admin-enterpriseName-adminServerName/nodes/nodeName/bin/node.lck

where nodeName is the name of each node on the system - for example, BPMnode and SystemNode.



After Starting TIBCO ActiveMatrix BPMIn TIBCO ActiveMatrix Administrator, check that BPM has started correctly and that all other required applications are running.

Using Workspace or Openspace, resume any process instances that are now suspended because the primary site failed (see Enable Halt on Error Behavior).

You can resume a suspended process instance by selecting it and clicking Resume - see the TIBCO Openspace User’s Guide or TIBCO Workspace User’s Guide for more information.


| 221

Appendix E Disaster Recovery Using Device-Level Replication

The device-level replication approach:

• requires dedicated device-level replication hardware and software (with commensurate higher costs).

• ensures that state information held in the file system or database remains synchronized after replication to the DR site.

The data from following parts of a TIBCO ActiveMatrix BPM system must be replicated on a separate system such that all data sources are consistent.

• TIBCO_HOME and CONFIG_HOME directories for the TIBCO ActiveMatrix BPM installation. If the BPM configuration files are in a different location, you must replicate them as well.

• TIBCO ActiveMatrix BPM database

• TIBCO ActiveMatrix Administrator database

• TIBCO Enterprise Message Service server

• Corporate LDAP system.

The method for replicating this data depends on your specific company practices and policies.

The following diagram shows an example of this type of configuration.


222 | Appendix E Disaster Recovery Using Device-Level Replication

Replicated Backup System

Highly Available Active-Active System

Third-party software solution to replicate essential system data


| 223

Appendix F Securing Communication Channels

The TIBCO ActiveMatrix BPM platform is partitioned across many components. These components communicate with each other and with third-party applications over various communication protocols. The components and communication channels are illustrated in Figure 5 on page 223.

Figure 5 TIBCO ActiveMatrix Communication Channels

By default, these communication channels are not secure. However, they can be secured by configuring the channels to use the Secure Sockets Layer (SSL) protocol. SSL is a cryptographic protocol that provides security and data integrity for communications over TCP/IP networks. SSL encrypts the segments of point-to-point connections at the Transport Layer.


224 | Appendix F Securing Communication Channels

An SSL client and server negotiate a stateful connection by using a handshaking procedure. During this handshake, the client and server agree on various parameters to establish the connection's security. The handshake begins when a client connects to an SSL-enabled server requesting a secure connection. The server sends back its identification in the form of a digital certificate. The certificate usually contains the server name, the trusted certificate authority (CA), and the server's public encryption key.

You can specify the SSL configuration of the communication channels at various times in the life cycle of a TIBCO ActiveMatrix BPM enterprise. Table 4 on page 224 lists how to perform the initial SSL configuration and how to upgrade, downgrade, and change the configuration of each channel. Detailed steps for each procedure are provided in Configuring ActiveMatrix BPM Runtime Objects (TIBCO Configuration Tool) and TIBCO ActiveMatrix BPM - SOA Administration.

Table 4 SSL Configuration Summary

Key Channel Initial Configuration Upgrade, Downgrade or Change Configuration

1 TIBCO ActiveMatrix Administrator server (external HTTP port) - web and CLI clients

When creating ActiveMatrix Administrator server in TIBCO Configuration Tool.

Upgrade or downgrade: ActiveMatrix Administrator CLI

Change SSL configuration: ActiveMatrix Administrator CLI

2 TIBCO ActiveMatrix Administrator server (internal HTTP port) - hosts and nodes


Upgrade or downgrade: ActiveMatrix Administrator web UI or CLI

Change SSL configuration: ActiveMatrix Administrator web UI or CLI

3 TIBCO ActiveMatrix Administrator server - TIBCO Enterprise Message Service server


Upgrade or downgrade: ActiveMatrix Administrator web UI or CLI

Change SSL configuration: ActiveMatrix Administrator web UI or CLI

4 TIBCO Host instance - TIBCO Enterprise Message Service server

When creating ActiveMatrix Administrator server or TIBCO Host instance in TIBCO Configuration Tool.

Upgrade or downgrade: ActiveMatrix Administrator CLI



Securing Communication Channels | 225

5 TIBCO ActiveMatrix Administrator server - external database and LDAP servers



6 TIBCO ActiveMatrix Administrator server - hosts and nodes (management)


Upgrade: ActiveMatrix Administrator web UI


7 TIBCO ActiveMatrix Administrator server -UDDI server

1. Manually import the UDDI server certificate into the ActiveMatrix Administrator server trust store using keytool.

2. Enable secure communication in ActiveMatrix Administrator web UI or CLI.

Same procedure as initial configuration

8 TIBCO ActiveMatrix Administrator server (external HTTP port) - TIBCO Business Studio

ActiveMatrix Administrator - When creating ActiveMatrix Administrator server in TIBCO Configuration Tool.

TIBCO Business Studio - When you connect to ActiveMatrix Administrator.

ActiveMatrix Administrator Upgrade or downgrade: ActiveMatrix Administrator CLI


9 Resource instances (JMS, SMTP, LDAP, JDBC, HTTP) - external servers

ActiveMatrix Administrator web UI or CLI

ActiveMatrix Administrator web UI or CLI

Table 4 SSL Configuration Summary (Cont’d)

Key Channel Initial Configuration Upgrade, Downgrade or Change Configuration


226 | Appendix F Securing Communication Channels


| 227

Appendix G TIBCO Enterprise Message Service Server Configuration

This appendix describes the configuration changes that are required if your TIBCO ActiveMatrix BPM infrastructure connects to its TIBCO Enterprise Message Service servers with users that do not have administrator privileges. It presents the most restrictive permissions necessary.

1. Set permissions for the Administrator servers.

In the following commands, replace username and password with the username and password values appropriate for each bus.

— Messaging Bus

delete queue >delete topic >create user username "Description of the user"

password=passwordcreate queue AMX_SV.>grant queue AMX_SV.> user=username create, delete, modify,

send, receive

— Notification Bus, propagates status messages between Administrator, hosts, and nodes


password=passwordcreate topic EMSGMS.>grant topic EMSGMS.> user=username create, modify,

subscribe, publishgrant topic $sys.monitor.connection.* user=<username>

subscribegrant admin user=username view-connection

— Management Bus, which handles the internal Administrator queues, currently grouped with the Notification Bus


password=passwordcreate queue com.tibco.amf.admin.deploymentServerQueue.>grant queue com.tibco.amf.admin.deploymentServerQueue.>

user=username create, delete, send, receive

— Common Logging and Payload Bus


228 | Appendix G TIBCO Enterprise Message Service Server Configuration


password=passwordcreate queue cl_logservice_queue.physicalcreate queue cl_payload_queue.physicalgrant queue cl_logservice_queue.physical user=username

send, receivegrant queue cl_payload_queue.physical user=username send,

receivecreate jndiname cl_logservice_queue queue

cl_logservice_queue.physicalcreate jndiname cl_payload_queue queue

cl_payload_queue.physical

— Monitoring Bus


password=passwordcreate queue amx.governance.statsgrant queue amx.governance.stats user=username send,

receive

2. However, the Notification, Management, and Messaging Buses are initially grouped together as are the Monitoring, Common Logging, and Payload Buses. As a result, their constraints need to be grouped before they are manually separated, if required.

— Messaging, Notification, and Management Buses


password=passwordcreate queue AMX_SV.>grant queue AMX_SV.> user=username create, delete, modify,

send, receivecreate topic EMSGMS.>grant topic EMSGMS.> user=username create, modify,

subscribe, publishgrant topic $sys.monitor.connection.* user=username

subscribegrant admin user=username view-connectioncreate queue com.tibco.amf.admin.deploymentServerQueue.>grant queue com.tibco.amf.admin.deploymentServerQueue.>

user=username create, delete, send, receive

— Monitoring, Common Logging, and Payload Buses


password=passwordcreate queue cl_logservice_queue.physicalcreate queue cl_payload_queue.physical


TIBCO Enterprise Message Service Server Configuration | 229

create queue amx.governance.statsgrant queue cl_logservice_queue.physical user=username

send, receivegrant queue cl_payload_queue.physical user=username send,

receivegrant queue amx.governance.stats user=username send,

receivecreate jndiname cl_logservice_queue queue

cl_logservice_queue.physicalcreate jndiname cl_payload_queue queue

cl_payload_queue.physical

3. Create the Administrator server and TIBCO Host instance using TIBCO Configuration Tool, see Configuring ActiveMatrix BPM Runtime Objects (TIBCO Configuration Tool).


230 | Appendix G TIBCO Enterprise Message Service Server Configuration


| 231

Appendix H Using Third-Party Solutions to Configure a High Availability, Fault Tolerant ActiveMatrix BPM System

In the event of a hardware failure resulting in the failure of TIBCO ActiveMatrix BPM, a highly available, fault tolerant system starts TIBCO ActiveMatrix BPM on another machine, thus ensuring limited service interruption and no loss of data or messages.

Figure 6 below illustrates the use of third-party solutions to provide highly available, fault tolerant capabilities to your BPM runtime.

Figure 6 High Availability ActiveMatrix BPM System Using Third-Party Solutions

The setup requires at least three machines, say M1, M2, and M3, where:


232 | Appendix H Using Third-Party Solutions to Configure a High Availability, Fault Tolerant ActiveMatrix BPM System

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

• TIBCO ActiveMatrix BPM and TIBCO ActiveMatrix Administrator are installed and running on one machine (M1).

• The other machines (M2 and M3) are:

— connected to a shared file system

— part of an active-passive clustering setup. At any given time, one of the machines will have access to the shared file system on which the TIBCO ActiveMatrix BPM Node is installed/running.

In case of any catastrophic event such as power loss, hardware failure, network disruption, or operating system crash, the cluster software detects it and fails over to the next available server.

— One of these two machines should have a fully operational TIBCO ActiveMatrix BPM node installed and running.
