installation and configuration - tibco software · tibco activematrix® bpm installation and...

Two-Second Adv

TIBCO ActiveMatrix® BPM

Installation and ConfigurationSoftware Release 3.0May 2014

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

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvHow to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

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

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

ActiveMatrix BPM System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Distributed BPM System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Basic BPM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Primary, Second Primary and Remote Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Multiple Installations of BPM Systems in the Same ActiveMatrix Enterprise. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Upgrading From an Earlier Version of ActiveMatrix BPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Upgrade Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Disaster Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Network Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

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

Platform and Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Supported Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Supported Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Database and Platform Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

TIBCO Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21TIBCO Enterprise Message Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21TIBCO Business Studio™ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21TIBCO ActiveMatrix® Decisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Other TIBCO ActiveMatrix Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Third-party Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

TIBCO ActiveMatrix BPM Installation and Configuration

iv | Contents

Apache Ant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Eclipse Standard Web Toolkit (SWT) Graphical Tool Kit (GTK) Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Hibernate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Java Virtual Machine (JVM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24LDAP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Oracle Java 7 Elliptic Curve Cryptography (ECC) Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Web Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

User Account Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Operating System User Account Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Database User Account Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Additional System Requirements for a Distributed BPM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Load Balancer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Shared File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Server Time Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

I - INSTALLATION AND UPGRADE SCENARIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 3 Creating a Basic ActiveMatrix BPM System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

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

Task 1: Perform Required Pre-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Task 2: Install ActiveMatrix BPM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Task 3: Configure JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Task 4: Create a BPM Node and Administrator Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Task 5: Perform Required Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 4 Creating an ActiveMatrix Administrator Server (Single or Replicated) . . . . . . . . . . 47

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Task 1: Perform Required Pre-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Task 2: Primary Machine - Install ActiveMatrix BPM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Task 3: Primary Machine - Configure JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Task 4: Primary Machine - Create the Administrator Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Task 5: Primary Machine - Move the ActiveMatrix Administrator Server Staging Area to the Shared File System55

Task 6: Second Primary Machine - Install ActiveMatrix BPM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Task 7: Second Primary Machine - Configure JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Task 8: Second Primary Machine - Replicate the ActiveMatrix Administrator Server . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 5 Creating a Distributed ActiveMatrix BPM System . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62


Contents | v

Task 1: Perform Required Pre-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Task 2: Remote Machine 1 - Install ActiveMatrix BPM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Task 3: Remote Machine 1 - Create a Host Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Task 4: Primary Machine - Create a BPM Node on Remote Machine 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Task 5: Remote Machine 2 - Install ActiveMatrix BPM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Task 6: Remote Machine 2 - Create a Host Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Task 7: Remote Machine 2 - Create a BPM Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72


Chapter 6 Adding an Additional ActiveMatrix BPM System to an Existing ActiveMatrix Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Task 1: Perform Required Pre-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Task 2: Production Machine - Install ActiveMatrix BPM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Task 3: Production Machine - Configure JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Task 4: Production Machine - Create a Host Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Task 5: Production Machine - Create a BPM Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83


Chapter 7 Upgrading an ActiveMatrix BPM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Task 1: Perform Required Pre-Upgrade Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Task 2: Second Primary Machine - Install ActiveMatrix BPM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Task 3: Second Primary Machine - Upgrade the ActiveMatrix Host Instance and ActiveMatrix Administrator . . . 92

Task 4: Primary Machine - Install ActiveMatrix BPM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Task 5: Primary Machine - Upgrade the ActiveMatrix Host Instance and ActiveMatrix Administrator . . . . . . . . . . 95

Task 6: Remote Machine - Install ActiveMatrix BPM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Task 7: Remote Machine - Upgrade the ActiveMatrix Host Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Task 8: Primary Machine - Upgrade ActiveMatrix BPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Task 9: Perform Post-Upgrade Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

II - INSTALLATION AND UPGRADE PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

Chapter 8 Preparing for Installation or Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Check For Any Late Breaking Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Check the System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Configure TIBCO Enterprise Message Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108


vi | Contents

Create the External ActiveMatrix Administrator Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Creating the ActiveMatrix Administrator Database Using SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Creating the ActiveMatrix Administrator Database Using Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Creating the ActiveMatrix Administrator Database Using DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Configure the BPM Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Configuring SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Configuring Oracle 11g . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Configuring DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Create a Database to Hold the BDS Case Data Store (DB2 Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Configure the External LDAP Directory Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Configure System Parameters on UNIX or Linux Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Configure Apache Ant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Download Required Third-Party Software Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Download ActiveMatrix BPM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Take a Backup of the Existing ActiveMatrix BPM System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Remove any Indexes Added to the BPM Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Back Up Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Back Up Openspace Customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Chapter 9 Installing ActiveMatrix BPM Software (TIBCO Universal Installer) . . . . . . . . . . . . 127

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

Installing in GUI Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Installing in Console mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Installing in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Chapter 10 Configuring ActiveMatrix BPM Runtime Objects (TIBCO Configuration Tool) . . 135

Using TIBCO Configuration Tool to Configure ActiveMatrix BPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136TIBCO Configuration Tool Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Running TIBCO Configuration Tool in GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Running TIBCO Configuration Tool in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Running a TIBCO Configuration Tool Wizard in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146The build.properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148A Simple Example - Adding a New Work Manager Node to a Distributed System . . . . . . . . . . . . . . . . . . . 149

Manually Creating the BPM Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Manually Upgrading the BPM Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Method 1 - Stop the BPM Application Before Upgrading It . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Method 2 - Perform the Upgrade in Two Stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152


Contents | vii

Manually Running BPM Database Creation or Upgrade Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154BPM Database Creation Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155BPM Database Upgrade Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Chapter 11 Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157

Configure the DataSourceBDS Shared Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

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

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

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

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

Reorganize Event Collector Tables after Upgrade (DB2 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Upgrade your Oracle JDBC Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Upgrade the Openspace GlobalHubPolicy Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Verify the Event Collector Rules Files (After Upgrade) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Edit TIBCO Hawk® Rulebase Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Set up Openspace Language Use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Restore any Openspace Customizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

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

Chapter 12 Configure Third-Party Driver Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175

Third-Party Driver: Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

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

Third-Party Driver: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Chapter 13 Create TIBCO ActiveMatrix BPM Server Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . .179

Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

ActiveMatrix BPM: Database Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

ActiveMatrix BPM: Runtime Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

ActiveMatrix BPM: BDS Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

ActiveMatrix BPM: Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

ActiveMatrix BPM: Sizing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

ActiveMatrix BPM: JMS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

ActiveMatrix BPM: LDAP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

ActiveMatrix BPM: SiteMinder Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

ActiveMatrix BPM: Administrator Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

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


viii | Contents

Administrator Server Configuration: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Chapter 14 Create TIBCO ActiveMatrix Administrator Server Wizard. . . . . . . . . . . . . . . . . . . 207

Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Administrator Server Configuration: Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Administrator Server Configuration: TIBCO Host Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Administrator Server Configuration: Connection Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

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

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

Administrator Server Configuration: Database Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Administrator Server Configuration: Authentication Realm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

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

Administrator Server Configuration: LDAP Authentication Realm Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223Administrator Server Configuration: LDAP Authentication Realm Details (Screen 2) . . . . . . . . . . . . . . . . . 224Administrator Server Configuration: LDAP Authentication Realm Details (Screen 3) . . . . . . . . . . . . . . . . . 225

Administrator Server Configuration: Credential Server Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Administrator Server Configuration: Credential Server Keystore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Administrator Server Configuration: Monitoring Notification Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Administrator Server Configuration: Monitoring Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

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

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


Chapter 15 Create TIBCO Host Instance Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

TIBCO Host instance Configuration: Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

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

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

TIBCO Host instance Configuration: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Chapter 16 Configure TIBCO ActiveMatrix BPM Server Node Type Wizard . . . . . . . . . . . . . . 249

Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

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

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

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

ActiveMatrix BPM Node Type: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256


Contents | ix

Chapter 17 Replicate TIBCO ActiveMatrix Administrator Server Wizard . . . . . . . . . . . . . . . . .257

Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Remote Administrator Server Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Create Replicated Instance Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Administrator Server Configuration Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Administrator Server TIBCO Host Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Administrator Server Connection Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Administrator Server Notification and Messaging Bus Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Administration Server Database Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Administrator Server Database Authentication Realm Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Administrator Server Configuration LDAP Authentication Realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Administrator Server Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Chapter 18 Edit TIBCO ActiveMatrix BPM Instance Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . .271

TIBCO ActiveMatrix BPM Server Edit Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

ActiveMatrix BPM Edit: Administrator Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

ActiveMatrix BPM: SOAP Version Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

ActiveMatrix BPM: Authentication Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

ActiveMatrix BPM: SiteMinder Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

ActiveMatrix BPM Edit: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Chapter 19 Upgrade TIBCO ActiveMatrix BPM Instance Wizard . . . . . . . . . . . . . . . . . . . . . . . .281

Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

ActiveMatrix BPM Upgrade: Administrator Server Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

ActiveMatrix BPM Upgrade: Upgrade Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

ActiveMatrix BPM Upgrade: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Chapter 20 Delete TIBCO ActiveMatrix BPM Instance Wizard. . . . . . . . . . . . . . . . . . . . . . . . . .289

Using the Delete TIBCO ActiveMatrix BPM Instance Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

ActiveMatrix BPM Deletion: Administrator Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

ActiveMatrix BPM Deletion: Instance Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

ActiveMatrix BPM Deletion: Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Chapter 21 Edit TIBCO ActiveMatrix Administrator Server Configuration Wizard . . . . . . . . .297

Edit ActiveMatrix Administrator Server Configuration: Administrator Server Selection . . . . . . . . . . . . . . . . . . . . 298


x | Contents

Edit ActiveMatrix Administrator Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

Administrator Server Configuration: Edit HTTP Connection Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Administrator Server Configuration: Edit Database Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Administrator Server Configuration: Edit Authentication Realm Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Administrator Server Configuration: Edit Database Authentication Realm Details . . . . . . . . . . . . . . . . . . . . . . . 304

Administrator Server Configuration: Edit LDAP Authentication Realm Details . . . . . . . . . . . . . . . . . . . . . . . . . . 305Administrator Server Configuration: LDAP Authentication Realm Details (Screen 2) . . . . . . . . . . . . . . . . . 306Administrator Server Configuration: LDAP Authentication Realm Details (Screen 3) . . . . . . . . . . . . . . . . . 307


IV - ADDITIONAL INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

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

Appendix B Restoring a BPM System from a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

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

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

Data-Level Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

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

Recovering TIBCO ActiveMatrix BPM if the Primary Site Fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336Before Starting TIBCO ActiveMatrix BPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336After Starting TIBCO ActiveMatrix BPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

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

Appendix F Deleting a Replica ActiveMatrix Administrator Server . . . . . . . . . . . . . . . . . . . . 341

Appendix G Securing Communication Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

Appendix H TIBCO Enterprise Message Service Server Configuration . . . . . . . . . . . . . . . . . 347

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


| xi

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 xii

• Connecting with TIBCO Resources, page xv

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.


xii | 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 | xiii

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


xiv | 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 | xv

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


xvi | Connecting with TIBCO Resources


| 1

HOW TO USE THIS GUIDE

1. Read the Introduction. It contains important information that you should be aware of before you try to install or upgrade TIBCO ActiveMatrix BPM.

2. Read System Requirements 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 - ADDITIONAL INFORMATION

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 provides important information that you should be aware of before you try to install or upgrade TIBCO ActiveMatrix BPM.

Topics

• ActiveMatrix BPM System Architecture, page 4

• Primary, Second Primary and Remote Machines, page 6

• Multiple Installations of BPM Systems in the Same ActiveMatrix Enterprise, page 7

• Upgrading From an Earlier Version of ActiveMatrix BPM, page 8

• Disaster Recovery, page 10

• Network Support, page 11


4 | Chapter 1 Introduction

ActiveMatrix BPM System Architecture

A BPM system comprises a single instance of the BPM application, including all nodes on which that BPM application is distributed.

A BPM system can use either a distributed or basic architecture. Your choice of architecture impacts the method you use to install or upgrade ActiveMatrix BPM.

Distributed BPM SystemIn a production environment, TIBCO recommend the use of a distributed configuration for ActiveMatrix BPM (along with a suitable underlying architecture). This configuration can provide the following advantages:

• Scalability: ActiveMatrix BPM software provides specialization and horizontal scalability capabilities. You can:

— add BPM logical nodes to boost the capacity of the BPM system in the required areas - web tier, process management or work management.

— distribute BPM logical nodes to different TIBCO Host instances and physical machines as required.

See "TIBCO ActiveMatrix BPM Logical Nodes and Services" in BPM Concepts for more information about the different types of BPM logical node and their uses.

• High availability and fault tolerance: ActiveMatrix BPM software provides active/active clustering capabilities. Adding a second BPM logical node (of type BPM) provides high availability and fault tolerance. In the event of a system-affecting failure on one node, load is automatically switched to the remaining node.

See TIBCO ActiveMatrix BPM Concepts for more information about supported BPM system architectures.

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.


ActiveMatrix BPM System Architecture | 5

See Creating a Distributed ActiveMatrix BPM System on page 61 for more information.

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

See Creating a Basic ActiveMatrix BPM System on page 37 for more information.

TIBCO recommend that the ActiveMatrix Administrator server is hosted independently from ActiveMatrix BPM, using its own set of TIBCO Host instances.

You should create the ActiveMatrix Administrator server (if it does not already exist) before the distributed BPM system. See Creating an ActiveMatrix Administrator Server (Single or Replicated) for more information about how to do this.

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.



Primary, Second Primary and Remote Machines

Throughout this guide, you will be instructed to perform different installation and configuration tasks on either a primary machine, second primary machine or a remote machine. These terms have the following specific meanings in the context of this document:

• Primary means the machine that hosts the ActiveMatrix Administrator server, whether or not that machine also hosts any BPM nodes.

• Second primary means the machine that hosts a replicated ActiveMatrix Administrator server, whether or not that machine also hosts any BPM nodes.

• Remote means any other machine that hosts a BPM node (of any type, but not an ActiveMatrix Administrator server.

A basic BPM system consists only of a primary machine. See Figure 1.

A distributed BPM system contains:

• a primary machine. See Figure 2.

• optionally, a second primary machine. See Figure 3.

• one or more remote machines. See Figure 4


Multiple Installations of BPM Systems in the Same ActiveMatrix Enterprise | 7

Multiple Installations of BPM Systems in the Same ActiveMatrix Enterprise

ActiveMatrix BPM version 2.2 (which is coupled with version 3.3 of the ActiveMatrix Platform and ActiveMatrix Administrator) allows multiple BPM systems to be installed in the same ActiveMatrix enterprise.

If the ActiveMatrix enterprise is managed by a version 3.3.0 (or later) ActiveMatrix Administrator server, multiple version 2.2 (or later) BPM systems can be installed:

• in the same ActiveMatrix environment, or in separate ActiveMatrix environments.

• on the same physical machine or on different physical machines.

• using any combination of basic or distributed architectures - see ActiveMatrix BPM System Architecture

• on the same TIBCO Host instance or on different TIBCO Host instances.

When multiple BPM systems are installed in the same ActiveMatrix enterprise, the following rules must be observed:

• Each instance of the BPM application must have a unique name within an ActiveMatrix environment. This name identifies that BPM system within that ActiveMatrix environment. (The combination of the environment name and application name uniquely identifies that BPM system within the ActiveMatrix enterprise.)

• An ActiveMatrix node can only host a single BPM system (or part of a distributed BPM system).

• Every BPM system in the ActiveMatrix enterprise must already be at version 2.2 (or later) before you add another BPM system to that enterprise. You must upgrade any existing pre-version 2.2 BPM system in the enterprise to version 2.2 before adding an additional BPM system.

BPM systems that share a TIBCO Host instance cannot be independently lifecycled or upgraded at the host level. For example, if (on a Microsoft Windows system) the TIBCO Host instance is installed as a service, stopping that service would stop all BPM systems hosted by that service.

As a result, TIBCO recommend that each discrete BPM system should use its own set of TIBCO Host instances. (If BPM systems do need to share a TIBCO Host instance, they must be upgraded at the same time.)



Upgrading From an Earlier Version of ActiveMatrix BPM

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

Upgrade ImpactNo 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

If you want to upgrade an existing, pre-version 3.3 ActiveMatrix Administrator to version 3.3, you must upgrade any pre-version 2.2 BPM system on the same TIBCO Host instance(s) to BPM version 2.2 at the same time.

If you are upgrading a distributed ActiveMatrix BPM system, configuration of the ActiveMatrix Administrator internal HTTP port (default 19767) for load balancing is no longer necessary.

In pre-2.2 versions of ActiveMatrix BPM, the ActiveMatrix Administrator internal HTTP port needed to be configured for load balancing across the replicated ActiveMatrix Administrator machines. This was so that, in the event of the primary ActiveMatrix Administrator instance failing, TIBCO Host instances could still download artifacts that they needed (such as keystores or software features) from the replicated ActiveMatrix Administrator instance. In ActiveMatrix BPM version 2.2, the ActiveMatrix platform now provides the necessary download capabilities internally.

Depending on the size of your system, upgrade can take some time. You should allow sufficient time for the upgrade to be performed.


Upgrading From an Earlier Version of ActiveMatrix BPM | 9

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.



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.


Network Support | 11

Network Support

Verson 3.0 of ActiveMatrix BPM supports Internet Protocol version 6 (IPv6) and version 4 (IPv4).

ActiveMatrix BPM supports:

• pure IPv4 configurations

• mixed-mode configurations where each network interface may have both IPv6 and IPv4 addresses

• pure IPv6 configurations

For more information on the use of IPv6 please see "Network Configuration > IPv6 Support" in SOA Administration.

Use of IPv6 requires an IPv6 compatible version of TIBCO Enterprise Message Service (EMS).

Wherever you need to provide a machine name (or hostname) when using ActiveMatrix BPM, TIBCO recommend that you use names that are resolved by the system address translation mechanism (DNS aliases or local host files) rather than literal IPv6 or IPv4 addresses.


| 13

Chapter 2 System Requirements

This chapter describes the basic system requirements that must be in place before you can install or upgrade to this version of ActiveMatrix BPM.

Topics

• Hardware Requirements, page 14

• Platform and Database Requirements, page 16

• TIBCO Software Requirements, page 21

• Third-party Software Requirements, page 23

• User Account Requirements, page 28

• Additional System Requirements for a Distributed BPM System, page 30


14 | Chapter 2 System Requirements

Hardware Requirements

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

ProcessorTwo 3 GHz 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 | 15

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 2012, 2008 or 2008 R2

— Novell SUSE Linux Enterprise Server 11

— Red Hat Enterprise Linux Server v5 or v6

— CentOS Linux v5 or v6

— Oracle Linux v5 or v6

— Sun Solaris 10

— Oracle Solaris 11

— IBM AIX v6 or v7

— HP-UX 11i V3

Operating System Supported Versions

Supported Processor Architectures

Windows (64-bit)

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

x86-64

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

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


Platform and Database Requirements | 17

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.9 (and any subsequent v5.x updates)



CentOS Linux v5.9 (and any subsequent v5.x updates)

CentOS Linux v6.4 (and any subsequent v6.x updates)

Oracle Linux v5.9 (and any subsequent v5.x updates)

Oracle Linux v6.4 (and any subsequent v6.x updates)

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

Oracle Solaris 11 (and any subsequent patches for this version)

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

IBM AIX v7.1 (and any subsequent fix packs for this version)

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, ActiveMatrix Administrator and (if required) BDS case data store 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 2012, 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 105 for more information.

Database Supported Versions Supported Editions

Microsoft SQL Server 2012 (64-bit)

2012 (with cumulative update package 3 for SQL Server 2012 Service Pack 1, or any subsequent service packs for this version)

Standard or higher

Microsoft SQL Server 2008 (64-bit)

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 (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 | 19

Database and Platform CompatibilityThe following table shows the different Supported Databases that can be used to host the ActiveMatrix BPM, ActiveMatrix Administrator and (if required) BDS case data store 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, ActiveMatrix Administrator and (if required) BDS case data store 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.

Platform hosting ActiveMatrix BPM

Microsoft SQL Server 2012 or 2008 R2

Oracle 11g R2 DB2

Microsoft Windows Server 2012/2008/2008 R2

Supported Supported Supported

Novell SUSE Linux Enterprise Server 11


Red Hat Enterprise Linux Server v5.6 (or later v5.x) or V6.x


CentOS Linux v5.9 (or later v5.x) or v6.4 (or later v6.x)


Oracle Linux v5.9 (or later v5.x) or v6.4 (or later v6.x)


Sun Solaris 10 or Oracle Solaris 11

Not tested Supported Not tested

IBM AIX v6.1 or v7.1 Not tested Supported Supported

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



• Not tested - When ActiveMatrix BPM is hosted on this platform, TIBCO has not validated use of this database to host the ActiveMatrix BPM, ActiveMatrix Administrator and (if required) BDS case data store databases.

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


TIBCO Software Requirements | 21

TIBCO Software Requirements

TIBCO ActiveMatrix BPM software uses the following required and optional TIBCO ActiveMatrix 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) (Version 6.0.0 - 8.0.x):

• 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 108).

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

TIBCO Business Studio™ TIBCO Business Studio - BPM Edition 3.7 is required to model processes and deploy them.

TIBCO ActiveMatrix® DecisionsTIBCO ActiveMatrix Decisions 1.1.1 is required to execute decision services on TIBCO ActiveMatrix BPM.

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/


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 Binding Type for REST

TIBCO ActiveMatrix Binding Type for REST allows users to expose and consume RESTful service in a composite application..

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

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 is supplied as part of the ActiveMatrix BPM software distribution. (See Configure Apache Ant.)

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






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

Java Runtime Environment (JRE) 1.7 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:

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 or 2012

Microsoft SQL Server JDBC Driver 3.0 or 4.0 (sqljdbc4.jar)

Oracle 11g R2 Version 11.2.0.4.0 (ojdbc6.jar). To determine if you have the correct version, open the JAR file, and examine the file META-INF/MANIFEST.MF for the following entry:Implementation-Version: 11.2.0.4.0



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

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 system that is intended for production use (generally a Distributed BPM System), 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.

Oracle Java 7 Elliptic Curve Cryptography (ECC) LibraryIf you are installing ActiveMatrix BPM on a Windows, Linux or Solaris platform, the Oracle Java 7 ECC library is required. (This library is not required if you are installing ActiveMatrix BPM on any other platform.)

You can obtain the Oracle Java 7 ECC library in two ways:

• You can download a software assembly 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 assembly from the TIBCO Software Product Download Site (https://download.tibco.com/tibco/), before you install ActiveMatrix BPM.


DB2 db2jcc4.jar

Database Required JDBC driver




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.

Openspace and Workspace

In the event of a problem with a more recent browser version, TIBCO will employ reasonable 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.

Browser Supported versions Notes

Internet Explorer

8

9, 10 Compatibility View is not supported.

Mozilla Firefox

26 The Openspace Spotfire gadget is not supported.

Google Chrome

32

Safari (on iOS7)

7 The Openspace Spotfire, Organization Browser, and Event Views gadgets are not supported.

Safari (on OS10.8.x)

6 The Openspace Spotfire, Organization Browser, and Event Views gadgets are not supported.



TIBCO ActiveMatrix Administrator (GUI)

Browser Supported versions Notes

Internet Explorer

8 SP2 is required

9, 10 Compatibility View is not supported.

Mozilla Firefox

26



User Account Requirements

Installing and configuring ActiveMatrix BPM requires the involvement of the following roles:

• BPM installer - responsible for installing and configuring ActiveMatrix BPM.

• Database administrator (DBA) - responsible for creating and upgrading the ActiveMatrix Administrator server and BPM server databases.

Operating System User Account RequirementsThe user account used to install or upgrade ActiveMatrix BPM must have the appropriate privileges:

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

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

• UNIX or Linux - Any 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.

Database User Account RequirementsWhen you create or upgrade a BPM system, you can allow TIBCO Configuration Tool to automatically create or upgrade the ActiveMatrix BPM database.

To do this, you must have the username and password of a database server user account that has database administrator privileges (a DBA user). You will need to specify these credentials in the ActiveMatrix BPM: Database Administrator screen of the Create TIBCO ActiveMatrix BPM Server Wizard.

Depending on your operational and security environment, these roles can be performed either by the same person, or by different departments or individuals.


User Account Requirements | 29

If you do not have the credentials of a DBA user, a DBA user will need to manually create the BPM database before you can complete installation and configuration with TIBCO Configuration Tool. See Manually Creating the BPM Database.



Additional System Requirements for a Distributed BPM System

The following table lists additional architectural requirements for a distributed ActiveMatrix BPM system (see Figure 4).

Requirement Description

Load Balancer Manages HTTP requests from ActiveMatrix BPM clients across the machines hosting BPM nodes.

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 each machine that is part of the BPM system.

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


Additional System Requirements for a Distributed BPM System | 31

Load BalancerThe load balancer must be configured as follows:

• The following ports must be configured for load balancing across the relevant machines:

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

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

If you are upgrading a distributed ActiveMatrix BPM system, configuration of the ActiveMatrix Administrator internal HTTP port (default 19767) for load balancing is no longer necessary.

In pre-2.2 versions of ActiveMatrix BPM, the ActiveMatrix Administrator internal HTTP port needed to be configured for load balancing across the replicated ActiveMatrix Administrator machines. This was so that, in the event of the primary ActiveMatrix Administrator instance failing, TIBCO Host instances could still download artifacts that they needed (such as keystores or software features) from the replicated ActiveMatrix Administrator instance. In ActiveMatrix BPM version 2.2, the ActiveMatrix platform now provides the necessary download capabilities internally.



Shared File SystemThe shared file system must:

• be available to each machine that is part of the BPM system.

• be mounted in an identical location on each machine. For example, if you create a network drive or folder on machine 1 and map it to x:\shared on the primary machine , the shared drive or folder must be mapped to x:\shared on each remote machine as well.

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

Folder Notes

SHARED_DIR\admin\enterpriseName\shared

Shared staging area 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.

Use this folder when configuring the ActiveMatrix Administrator on the primary machine - see Task 5: Primary Machine - Move the ActiveMatrix Administrator Server Staging Area to the Shared File System.

SHARED_DIR\bpm_config Shared configuration folder in which ActiveMatrix BPM stores BPM properties files. (bpm_config is the suggested name for this folder, but you can use any name that you wish.)

Use this location when configuring ActiveMatrix BPM on:

• the main BPM node - see ActiveMatrix BPM: Configuration

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


Additional System Requirements for a Distributed BPM System | 33

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.

Folder 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\data_3.2.x\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.


| 35

I - INSTALLATION AND UPGRADE SCENARIOS

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

Topics

• Creating a Basic ActiveMatrix BPM System, page 37

• Creating an ActiveMatrix Administrator Server (Single or Replicated), page 47

• Creating a Distributed ActiveMatrix BPM System, page 61

• Adding an Additional ActiveMatrix BPM System to an Existing ActiveMatrix Enterprise

• Upgrading an ActiveMatrix BPM System, page 87


36 | I - INSTALLATION AND UPGRADE SCENARIOS


| 37

Chapter 3 Creating 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 38

• Task 1: Perform Required Pre-Installation Tasks

• Task 2: Install ActiveMatrix BPM Software, page 41

• Task 3: Configure JDBC Drivers, page 42

• Task 4: Create a BPM Node and Administrator Server, page 43

• Task 5: Perform Required Post-Installation Tasks, page 45


38 | Chapter 3 Creating 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 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 | 39

Figure 1 Example ActiveMatrix BPM system using a basic configuration



Task 1: Perform Required Pre-Installation Tasks

Perform the following pre-installation tasks:

1. Check For Any Late Breaking Information

2. Check the System Requirements

3. Configure TIBCO Enterprise Message Service

4. Create the External ActiveMatrix Administrator Database

5. Configure the BPM Database Server

6. Configure the External LDAP Directory Server (Optional - you can use the internal LDAP Directory Server provided with ActiveMatrix BPM if you wish.)

7. Configure System Parameters on UNIX or Linux Platforms

8. Configure Apache Ant

9. Download Required Third-Party Software Assemblies

10. Download ActiveMatrix BPM Software


Task 2: Install ActiveMatrix BPM Software | 41

Task 2: Install ActiveMatrix BPM Software

1. Log on to the primary machine.

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

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

Screen Requirement

Installation Profile Selection

Select the Primary machine profile.

Note: If the ActiveMatrix Administrator server is installed on a separate machine, you should select the Remote machine profile instead.

TIBCO Installation Home

Select Create a new TIBCO_HOME.

Post-Install summary Select Launch TIBCO Configuration Tool.



Task 3: 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 24.)

2. In TIBCO Configuration Tool, enter a local location for the TIBCO configuration folder (CONFIG_HOME), or click OK to use the default location.

3. Run the Configure Third-Party Driver Wizard.

4. 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 or 4.0

— TIBCO enabled JDBC driver for Oracle 11.2.0.4.0

— TIBCO enabled JDBC driver for IBM DB2 4.12.55

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

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


Task 4: Create a BPM Node and Administrator Server | 43

Task 4: Create a BPM Node and Administrator Server

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

Make sure that you complete the following screens/fields as shown. (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.)

Screen Requirement

Welcome If you want to perform an Express installation, clear Configure for Standard Installation of all details.

An Express installation allows you to quickly create a new BPM system and ActiveMatrix Administrator server, using mostly default configuration options.

ActiveMatrix BPM: Database Administrator

Enter the details of the database server that will be used to host the ActiveMatrix BPM database. (See Configure the 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: SiteMinder 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.

Note: This screen is not displayed if you have chosen to do an Express installation.

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 Create the External ActiveMatrix Administrator Database.)



TIBCO Configuration Tool creates the ActiveMatrix Administrator server and a BPM node on the host machine.

2. Click Close to exit TIBCO Configuration Tool.

Administrator Server Configuration: Credential Server Details

Ensure that Bind to Network Adapter is set to 0.0.0.0.

Note: This screen is not displayed if you have chosen to do an Express installation.

Administrator Server Configuration: Summary

Select Create TIBCO ActiveMatrix Administrator server and Create ActiveMatrix BPM, then:

• If the string [Creating Database Instance] is appended to the Create ActiveMatrix BPM action (indicating that you chose to automatically create the ActiveMatrix BPM database), click Configure.

• If the string [Not Creating Database Instance] is appended to the Create ActiveMatrix BPM action (indicating that you chose to manually create the ActiveMatrix BPM database:

a. Click Save to save the configuration information gathered in the preceding screens to the specified Session Scripts and Log Folder.

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

c. Get a database administrator to manually create the BPM database - see Manually Running BPM Database Creation or Upgrade Scripts.

d. Run the Create TIBCO ActiveMatrix BPM Server wizard again.

e. Click Load, then select the Session Scripts and Log Folder in which you saved the configuration information.

f. Click OK when the Loaded data model successful message is displayed.

g. Click Next repeatedly until you reach the ActiveMatrix BPM: Runtime Database Configuration screen, then click Test Connection (to verify that TIBCO Configuration Tool can connect to the BPM database).

h. Click Next repeatedly until you reach the Administrator Server Configuration: Summary screen, then click Configure.

Screen Requirement


Task 5: Perform Required Post-Installation Tasks | 45

Task 5: Perform Required Post-Installation Tasks

Perform the following post-installation tasks:

1. Create Any Other Required LDAP Connections to LDAP Directories (if required)

2. Configure Transaction Recovery (Oracle only)

3. Set Transaction Verification Property (SQL Server Only)

4. Edit TIBCO Hawk® Rulebase Files (optional)

5. Set up Openspace Language Use (optional)


| 47

Chapter 4 Creating an ActiveMatrix Administrator Server (Single or Replicated)

This chapter describes how to install and configure an ActiveMatrix Administrator server on a separate machine from any BPM systems. This configuration is recommended for use in a production environment.

Topics

• Overview


• Task 2: Primary Machine - Install ActiveMatrix BPM Software

• Task 3: Primary Machine - Configure JDBC Drivers

• Task 4: Primary Machine - Create the Administrator Server

• Task 5: Primary Machine - Move the ActiveMatrix Administrator Server Staging Area to the Shared File System

• Task 6: Second Primary Machine - Install ActiveMatrix BPM Software

• Task 7: Second Primary Machine - Configure JDBC Drivers

• Task 8: Second Primary Machine - Replicate the ActiveMatrix Administrator Server


48 | Chapter 4 Creating an ActiveMatrix Administrator Server (Single or Replicated)

Overview

In a production environment, TIBCO recommend that the ActiveMatrix Administrator server is hosted independently from ActiveMatrix BPM, using its own set of TIBCO Host instances.

If a high availability, fault tolerant configuration is required, the ActiveMatrix Administrator server should also be replicated.

Figure 2 shows an example configuration for a single ActiveMatrix Administrator server.

Figure 3 shows an example configuration for a replicated ActiveMatrix Administrator server.


Overview | 49

Figure 2 Example configuration for a single ActiveMatrix Administrator server

For details of the associated configuration for a distributed ActiveMatrix BPM system, see Figure 4.



Figure 3 Example configuration for a replicated ActiveMatrix Administrator server

For details of the associated configuration for a distributed ActiveMatrix BPM system, see Figure 4.


Task 1: Perform Required Pre-Installation Tasks | 51






4. Create the External ActiveMatrix Administrator Database







Task 2: Primary Machine - Install ActiveMatrix BPM Software




Screen Requirement







Task 3: Primary Machine - Configure JDBC Drivers | 53

Task 3: Primary Machine - 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 24.)


3. In the Create new configurations screen, choose the Configure Third-Party Driver Wizard.

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




Task 4: Primary Machine - Create the Administrator Server

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


TIBCO Configuration Tool creates the ActiveMatrix Administrator server on the primary machine.


Screen Requirement

Administrator Server Configuration: TIBCO Host Configuration

Clear Create Development Node.


1. Clear Use Default In-Process Database.

2. Enter the details of the database server that hosts the Administrator database, making sure that the Database URL field contains a DNS name. (See Create the External ActiveMatrix Administrator Database.)


Ensure that Bind to Network Adapter is set to 0.0.0.0.


Select Create TIBCO ActiveMatrix Administrator server then click Configure.

See Create TIBCO ActiveMatrix Administrator Server Wizardfor full details of the information that you need to enter in this wizard.

If you want to replicate the ActiveMatrix Administrator server, perform the remaining tasks (5 to 8) in this chapter.


Task 5: Primary Machine - Move the ActiveMatrix Administrator Server Staging Area to the Shared File System | 55

Task 5: Primary Machine - Move the ActiveMatrix Administrator Server Staging Area to the Shared File System

1. Copy the folder CONFIG_HOME\admin\enterpriseName\shared to a location on the shared file system (see Shared File System). For example:

SHARED_DIR\admin\enterpriseName\shared

2. Open a command window in the TIBCO_HOME\administrator\n.n\scripts folder.

3. Run the following command to update the ActiveMatrix Administrator server with the new staging area location:

ant -f sharedWorkFolder_build.xml

-Dadmin.shared.folder="sharedFileSystemLocation"-Dconfig.home="CONFIG_HOME"-Denterprise.name="enterpriseName"

where sharedFileSystemLocation is the location on the shared file system from step 1 above.

4. Open a command window in the CONFIG_HOME\tibcohost\Admin-enterpriseName-hostName\host\bin folder.

5. Run the following commands to stop and restart the system node (thereby restarting the ActiveMatrix Administrator server:

tibcohost.exe stopNodes -nodeName SystemNode

tibcohost.exe startNodes -nodeName SystemNode



Task 6: Second Primary Machine - Install ActiveMatrix BPM Software

1. Log on to the second primary 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-admin, the location of TIBCO_HOME on the second primary machine must also be C:\tibco\amx-admin.



Task 7: Second Primary Machine - Configure JDBC Drivers | 57

Task 7: Second Primary 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 24.)

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

3. In the Create new configurations screen, run the Configure Third-Party Driver Wizard.

4. Configure the JDBC driver needed for the database server that was used to host the ActiveMatrix Administrator database on the primary machine. (See Task 3: Primary Machine - Configure JDBC Drivers.)




Task 8: Second Primary Machine - Replicate the ActiveMatrix Administrator Server

1. Copy the content of the CONFIG_HOME\tct\keystore folder from the primary machine to the same location on the second primary machine. (Create this folder on the second primary machine if it does not already exist.)

2. In TIBCO Configuration Tool, run the Replicate TIBCO ActiveMatrix Administrator Server Wizard.


TIBCO Configuration Tool:

— creates the specified SystemHost instance and SystemNode.

— replicates the ActiveMatrix Administrator server. The replicated server runs on the specified SystemNode.

For example, in Figure 3, a TIBCO Host instance named SystemHostReplica is created and started. A node named SystemNodeReplica is created in the

Screen Requirement

Remote Administrator Server Details

Specify the details of the Administrator server that you created on the primary machine.

Administrator Server Configuration Details 1. Enter a unique Host Name for the SystemHost

instance that will be associated with the replicated ActiveMatrix Administrator server (SystemHostReplica in Figure 3).

2. Enter a unique Node Name for the SystemNode instance that will be associated with the replicated ActiveMatrix Administrator server (SystemNodeReplica in Figure 3).

Administrator Server Configuration Summary

1. Select Replicate TIBCO ActiveMatrix Administrator server.

2. Click Configure.

See Replicate TIBCO ActiveMatrix Administrator Server Wizardfor full details of the information that you need to enter in this wizard.


Task 8: Second Primary Machine - Replicate the ActiveMatrix Administrator Server | 59

environment named SystemEnvironment and started. The replicated Administrator server runs on SystemNodeReplica.

3. Return to the Create new configurations screen, then close TIBCO Configuration Tool.

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 can process requests.


| 61

Chapter 5 Creating a Distributed ActiveMatrix BPM System

This chapter describes how to install and configure a BPM system using a distributed configuration (with components distributed across multiple machines to provide scalability and/or high availability and fault tolerance).

Topics

• Overview


• Task 2: Remote Machine 1 - Install ActiveMatrix BPM Software

• Task 3: Remote Machine 1 - Create a Host Instance

• Task 4: Primary Machine - Create a BPM Node on Remote Machine 1

• Task 5: Remote Machine 2 - Install ActiveMatrix BPM Software

• Task 6: Remote Machine 2 - Create a Host Instance

• Task 7: Remote Machine 2 - Create a BPM Node

• Task 8: Perform Required Post-Installation Tasks


62 | Chapter 5 Creating a Distributed ActiveMatrix BPM System

Overview

In a production environment, TIBCO recommend the use of a distributed configuration for ActiveMatrix BPM (along with a suitable underlying architecture). This configuration can provide the following advantages:

• Scalability: ActiveMatrix BPM software provides specialization and horizontal scalability capabilities. You can:

— add BPM logical nodes to boost the capacity of the BPM system in the required areas - web tier, process management or work management.

— distribute BPM logical nodes to different TIBCO Host instances and physical machines as required.

See "TIBCO ActiveMatrix BPM Logical Nodes and Services" in BPM Concepts for more information about the different types of BPM logical node and their uses.

• High availability and fault tolerance: ActiveMatrix BPM software provides active/active clustering capabilities. Adding a second BPM logical node (of type BPM) provides high availability and fault tolerance. In the event of a system-affecting failure on one node, load is automatically switched to the remaining node.

Figure 4 shows an example configuration for a distributed ActiveMatrix BPM system

TIBCO also recommend that the ActiveMatrix Administrator server is hosted independently from ActiveMatrix BPM, using its own set of TIBCO Host instances.

You must create the ActiveMatrix Administrator server (if it does not already exist) before you create the distributed BPM system. See Creating an ActiveMatrix Administrator Server (Single or Replicated) for more information about how to do this.


Overview | 63

Figure 4 Example configuration for a distributed ActiveMatrix BPM system

For details of the associated ActiveMatrix Administrator server configuration, see Figure 2 (single server) or Figure 3 (replicated server).







3. Create an ActiveMatrix Administrator server (if it does not already exist). See Creating an ActiveMatrix Administrator Server (Single or Replicated) for more information about how to do this



6. Configure the External LDAP Directory Server






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

Task 2: Remote Machine 1 - Install ActiveMatrix BPM Software

1. Log on to machine 1.


3. In the installer wizard, make sure that you complete the following screens/fields as shown.

Screen Requirement


Select the Remote machine profile.






Task 3: Remote Machine 1 - Create a Host Instance

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


TIBCO Configuration Tool creates the specified TIBCO host instance (if it does not already exist), binding it to the ActiveMatrix Administrator server that manages this ActiveMatrix enterprise.

For example, in Figure 4, BPMHost1 is created on BPM_Machine1 and bound to the ActiveMatrix Administrator server.

Screen Requirement

TIBCO Host instance Configuration: Details 1. Enter a unique Name for this TIBCO Host instance (BPMHost1 in

Figure 4).

2. Enter the ActiveMatrix Enterprise Name (AMX BPM Enterprise in Figure 4).

TIBCO Host instance Configuration: Administrator Server

1. Select Bind to Administrator server.

2. Enter the Machine Name on which the ActiveMatrix Administrator server is running.


Select:

• Create TIBCO Host instance

• Launch TIBCO Host instance

• Register TIBCO Host instance to the Administrator server

then click Configure.


Task 4: Primary Machine - Create a BPM Node on Remote Machine 1 | 67

Task 4: Primary Machine - Create a BPM Node on Remote Machine 1

1. Log on to the primary machine (on which ActiveMatrix Administrator is running).



Screen Requirement


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


Enter the details of the ActiveMatrix BPM database.

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 (in which BPM properties files are to be stored). 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.


1. Select Use Existing ActiveMatrix Administrator Server.

2. Specify the details of the ActiveMatrix Administrator server being used by the ActiveMatrix enterprise (AMX BPM Enterprise in Figure 4).



ActiveMatrix BPM: Host and Node Configuration

1. Host: Enter the name of the TIBCO Host instance on which the BPM system will be created. This must be an existing host that is bound to the specified ActiveMatrix Administrator server (BPMHost1 in Figure 4).

2. Environment Name: Enter the name of the new ActiveMatrix environment in which the BPM system will be created (BPMEnvironment in Figure 4).

3. Node Name: Enter a unique name for the ActiveMatrix node on which the BPM system will be created (BPMNode1 in Figure 4).

4. Node Management Port: Enter a unique port number.


Select Create ActiveMatrix BPM, then:


• If the string [Not Creating Database Instance] is appended to the Create ActiveMatrix BPM action (indicating that you chose to manually create the ActiveMatrix BPM database:









Screen Requirement


Task 4: Primary Machine - Create a BPM Node on Remote Machine 1 | 69


— creates and starts a BPM node (of type BPM Node) on the specified TIBCO host instance.

— creates the specified ActiveMatrix environment and adds the new node to it.

For example, in Figure 4:

— BPMNode1 is started on BPMHost1.

— BPMEnvironment is created to include BPMNode1.




Task 5: Remote Machine 2 - Install ActiveMatrix BPM Software

1. Log on to the second 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 machine 1. For example, if the location of TIBCO_HOME on machine 1 is C:\tibco\amx-bpm, the location of TIBCO_HOME on the second primary machine must also be C:\tibco\amx-bpm.



Task 6: Remote Machine 2 - Create a Host Instance | 71

Task 6: Remote Machine 2 - Create a Host Instance



TIBCO Configuration Tool creates the specified TIBCO host instance (if it does not already exist), binding it to the ActiveMatrix Administrator server.

For example, in Figure 4, BPMHost2 is created on BPM_Machine2 and bound to the ActiveMatrix Administrator server.

Screen Requirement

TIBCO Host instance Configuration: Details 1. Enter a unique Name for this TIBCO Host instance (BPMHost2 in

Figure 4).

2. Enter the ActiveMatrix Enterprise Name (AMX BPM Enterprise in Figure 4).





Select:




then click Configure.



Task 7: Remote Machine 2 - Create a BPM Node

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


Screen Requirement

ActiveMatrix BPM Node Type: Administrator Server Configuration

Specify the details of the ActiveMatrix Administrator server.

ActiveMatrix BPM Node Type: Host and Node Configuration

1. Node Type: Select:

— BPM if you want to provide high availability and fault tolerance to the BPM system.

— BPM, Process Manager, Work Manager or Web Components, as appropriate, if you want to scale that particular component of the BPM runtime so as to boost the performance of the BPM system.

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

3. Node Port: Enter a unique port number.

4. Host: Enter the name of the host that is running on this machine (BPMHost2 in Figure 4).

5. HTTP Port: Enter a unique port number.

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

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.


Task 7: Remote Machine 2 - Create a BPM Node | 73


— starts a BPM node of the specified type on the specified TIBCO host instance.

— adds the new node to the specified ActiveMatrix environment (creating that environment if necessary).

— distributes the BPM application to the new node.

For example, in Figure 4, BPMNode2 is started on BPMHost2. The BPMEnvironment is extended to include BPMNode2. The BPM application is distributed to BPMNode2.

3. Close TIBCO Configuration Tool.

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

Node Type.

2. Click Configure.

Screen Requirement






2. Configure Client Communications Through the Load Balancer




6. Set up Openspace Language Use (optional)


| 75

Chapter 6 Adding an Additional ActiveMatrix BPM System to an Existing ActiveMatrix Enterprise

Topics


• Task 1: Perform Required Pre-Installation Tasks, page 79

• Task 2: Production Machine - Install ActiveMatrix BPM Software, page 80

• Task 3: Production Machine - Configure JDBC Drivers, page 81

• Task 4: Production Machine - Create a Host Instance, page 82

• Task 5: Production Machine - Create a BPM Node, page 83

• Task 6: Perform Required Post-Installation Tasks, page 86


76 | Chapter 6 Adding an Additional ActiveMatrix BPM System to an Existing ActiveMatrix Enterprise

Overview

Multiple BPM systems (version 2.2 or later) can be installed in the same ActiveMatrix enterprise, administered by the same ActiveMatrix Administrator server (version 3.3 or later).

Figure 5 shows a simple example in which a development BPM system and a production BPM system are installed in the same ActiveMatrix enterprise. Note the following points about this example.

Every BPM system in an ActiveMatrix enterprise must already be at version 2.2 (or later) before you add another BPM system to that enterprise.

You must upgrade any existing pre-version 2.2 BPM system in the enterprise to version 2.2 before adding an additional BPM system.

In this example... In general, in the same ActiveMatrix Enterprise...

Development and production BPM systems are both managed by the same ActiveMatrix Administrator server.

Each ActiveMatrix host that hosts (any part of) a BPM system must be bound to the same ActiveMatrix Administrator server.

Development and production BPM systems are hosted on separate physical machines.

Multiple BPM systems can be hosted on the same physical machine.

Development and production BPM systems both use the basic architecture (although ActiveMatrix Administrator is hosted separately).

Multiple BPM systems can use different (basic or distributed) architectures as required.

Development and production BPM systems are hosted on separate ActiveMatrix Host instances.

TIBCO recommend that:

• each discrete BPM system is hosted on its own set of TIBCO Host instances.

• ActiveMatrix Administrator is hosted on its own set of TIBCO Host instances.


Overview | 77

Development and production BPM systems use different ActiveMatrix environments.

Multiple BPM systems can either share the same ActiveMatrix environment or use different ActiveMatrix environments:

• A shared environment allows each BPM system to access shared services, using service virtualization.

• Using separate environments allows each BPM system to be completely isolated from other BPM systems.

Development and production BPM systems are hosted on separate ActiveMatrix nodes.

Each BPM system must be hosted on a separate set of ActiveMatrix nodes.

The BPM application in the Development system is called BPM_Dev_App.

The BPM application in the Production system is called BPM_Prod_App.

Each instance of a BPM application in the same environment must have a unique name.

Development and production BPM databases are hosted on the same database server.

Multiple BPM systems can use different database servers, and different types of database. (For example, one system may use Oracle, another SQL Server.)

The same LDAP and SMTP servers are used by both BPM systems.

Multiple BPM systems can either use the same or separate LDAP or SMTP servers.

The same EMS server is used by both BPM systems.

BPM systems that share the same ActiveMatrix environment must use the same EMS server.

BPM systems in different ActiveMatrix environments can use different EMS servers.

The starting point for this procedure assumes that a (version 2.2) development BPM system, has already been installed, and that the ActiveMatrix Administrator server has been separately created. (See Creating an ActiveMatrix Administrator Server (Single or Replicated).)

In this example... In general, in the same ActiveMatrix Enterprise...



Figure 5 Example - Two separate BPM systems in a single ActiveMatrix Enterprise


Task 1: Perform Required Pre-Installation Tasks | 79







5. Configure the External LDAP Directory Server







Task 2: Production Machine - Install ActiveMatrix BPM Software

1. Log on to the Production machine.



Screen Requirement







Task 3: Production Machine - Configure JDBC Drivers | 81

Task 3: Production Machine - Configure JDBC Drivers

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


3. In the Create new configurations screen, run the Configure Third-Party Driver Wizard.

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

— TIBCO enabled JDBC driver for Microsoft SQL Server 3.0 or 4.0

— TIBCO enabled JDBC driver for Oracle 11.1.0



You can skip this task if the machine on which you want to install the new BPM system already contains the appropriate configured JDBC driver.



Task 4: Production Machine - Create a Host Instance



TIBCO Configuration Tool creates the specified TIBCO host instance (if it does not already exist), binding it to the ActiveMatrix Administrator server.

For example, in Figure 5, BPM_Prod_Host is created on the Production machine and bound to the ActiveMatrix Administrator server.

Screen Requirement

TIBCO Host instance Configuration: Details 1. Enter a unique Name for this TIBCO Host instance.

2. Enter the ActiveMatrix Enterprise Name.





Select:





Task 5: Production Machine - Create a BPM Node | 83

Task 5: Production Machine - Create a BPM Node



Screen Requirement


Enter the details of the database server that will be used to host the ActiveMatrix BPM database for the new ActiveMatrix BPM system. (See Configure the BPM Database Server.)

This can either be the same database server that is hosting any existing ActiveMatrix BPM databases, or a different database server.


Enter the details of the ActiveMatrix BPM database for the new ActiveMatrix BPM system.


Change AMX-BPM Application Name to a unique name (not used by any other BPM system) in this ActiveMatrix environment.


Select Use External LDAP Server and specify the connection details for an external LDAP server.


1. Select Use Existing ActiveMatrix Administrator Server.

2. Specify the details of the ActiveMatrix Administrator server being used by the development BPM system.




1. Host: Enter the name of the TIBCO Host instance on which the BPM system will be created. This must be an existing host that is bound to the specified ActiveMatrix Administrator server (for example, in Figure 5, BPM_Prod_Host).

2. Environment Name: Enter the name of the ActiveMatrix environment in which the BPM system will be created. This can be either:

— a new environment (for example, in Figure 5, BPMProdEnvironment), or

— an existing environment that is part of the ActiveMatrix enterprise managed by the specified ActiveMatrix Administrator server.

3. Node Name: Enter a unique name for the ActiveMatrix node on which the BPM system will be created (for example, in Figure 5, BPM_Prod_Node).

4. Node Management Port: Enter a unique port number.

Screen Requirement


Task 5: Production Machine - Create a BPM Node | 85


— creates and starts a BPM node (of type BPM Node) on the specified TIBCO host instance.

— adds the new node to the specified ActiveMatrix environment (creating that environment if necessary).

For example, in Figure 5:

— BPM_Prod_Node is started on BPM_Prod_Host.

— BPMProdEnvironment is created to include BPM_Prod_Node.


Select Create ActiveMatrix BPM, then:


• If the string [Not Creating Database Instance] is appended to the Create ActiveMatrix BPM action (indicating that you chose to manually create the ActiveMatrix BPM database):









Screen Requirement


Upgrading an ActiveMatrix BPM System | 87

Chapter 7 Upgrading an ActiveMatrix BPM System

This chapter describes how to upgrade an ActiveMatrix BPM system.

Topics


• Task 1: Perform Required Pre-Upgrade Tasks, page 90

• Task 2: Second Primary Machine - Install ActiveMatrix BPM Software, page 91

• Task 3: Second Primary Machine - Upgrade the ActiveMatrix Host Instance and ActiveMatrix Administrator, page 92

• Task 4: Primary Machine - Install ActiveMatrix BPM Software, page 94

• Task 5: Primary Machine - Upgrade the ActiveMatrix Host Instance and ActiveMatrix Administrator

• Task 6: Remote Machine - Install ActiveMatrix BPM Software, page 97

• Task 7: Remote Machine - Upgrade the ActiveMatrix Host Instance, page 98

• Task 8: Primary Machine - Upgrade ActiveMatrix BPM, page 99

• Task 9: Perform Post-Upgrade Tasks, page 101


88 | Chapter 7 Upgrading an ActiveMatrix BPM System

Overview

A BPM system can range in scale from a basic, single machine system (see Figure 1), to a distributed, multi-machine system involving many BPM nodes and a separate ActiveMatrix Administrator server (see Figure 4 and Figure 3).

Whatever the system topology, the upgrade procedure requires two main steps - installing BPM software and running the Upgrade TIBCO ActiveMatrix BPM Instance Wizard - on each machine that is part of the BPM system. To perform the upgrade successfully:

• You must upgrade the machines that make up the BPM system in the correct sequence.

• You must upgrade the ActiveMatrix Administrator server first (if necessary), and then the BPM hosts, nodes and application.

• When you install BPM software on a machine, you must use the correct installation profile.

• When you run the Upgrade TIBCO ActiveMatrix BPM Instance Wizard on a machine, you must perform the appropriate set of configuration actions.

The following table summarizes these requirements.

Upgrade machines in this order... ...using this Installation Profile

... and executing these Configuration Actions

First, upgrade the ActiveMatrix Administrator server (if necessary)...

1. Second Primary - the machine that hosts the replicated ActiveMatrix Administrator server, if there is one (whether or not it also hosts any BPM nodes).

Primary • Upgrade ActiveMatrix TIBCO Host Instance

• Upgrade ActiveMatrix Administrator

2. Primary - the machine that hosts the ActiveMatrix Administrator server (whether or not it also hosts any BPM nodes).

Primary • Upgrade ActiveMatrix TIBCO Host Instance

• Upgrade ActiveMatrix Administrator

...then, upgrade all BPM hosts, nodes and application

3. Remote - each machine that is hosting a BPM node but not an ActiveMatrix Administrator server.

Remote • Upgrade ActiveMatrix TIBCO Host Instance


Overview | 89

You should perform each upgrade action that is required by the particular configuration of your ActiveMatrix enterprise. For example:

• If ActiveMatrix Administrator is not replicated there is no second primary machine to upgrade.

• If you are upgrading two BPM systems in the same enterprise, you would upgrade the first system as shown in the preceding table. You would not then need to upgrade the ActiveMatrix Administrator server when upgrading the second system.

4. Primary - the machine that hosts the ActiveMatrix Administrator server (whether or not it also hosts any BPM nodes).

Primary (unless you already installed the software in step 2.)

• Upgrade Nodes Hosting ActiveMatrix BPM Instance

• Upgrade ActiveMatrix BPM Instance Application

Upgrade machines in this order... ...using this Installation Profile

... and executing these Configuration Actions

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

Note the following if you are performing an upgrade with a replicated TIBCO ActiveMatrix Administrator on TIBCO ActiveMatrix BPM 2.1.0 with platform 3.1.5-HF11 and SSL-enabled for TIBCO Enterprise Message Service.

Installing TIBCO ActiveMatrix BPM 2.2.0 and upgrading tibcohost on second primary machine are successful, but upgrading Adminisrtator on second primary machine fails. This is indicated by the TIBCO Enterprise Message Service log file containing the following error:

2013-09-10 18:41:45.442 SSL handshake failed: ret=-1, reason=decryption failed or bad record mac2013-09-10 18:41:45.442 [OpenSSL Error]: file=ossl.c, line=17042013-09-10 18:41:45.442 2:error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac:.\ssl\s3_pkt.c:431:

If this happens, edit tibemsd.conf, setting cipher to RC4-MD5 in TIBCO Enterprise Message Service server's config during the upgrade. You can remove it afterwards:ssl_server_ciphers = !DHE-RSA-AES128-SHA:ALL



Task 1: Perform Required Pre-Upgrade Tasks

Perform the following pre-upgrade tasks:


2. Check the System Requirements (and make any upgrades required)



5. Take a Backup of the Existing ActiveMatrix BPM System

6. Remove any Indexes Added to the BPM Database

7. Back Up Workspace

8. Back Up Openspace Customizations

9. Make sure that the ActiveMatrix Administrator server and the BPM system that you want to upgrade are running.

If you are upgrading a system that includes a replicated ActiveMatrix Administrator server, make sure that the version of ActiveMatrix platform software installed on the second primary machine is exactly the same - including hotfixes applied - as on the primary machine.


Task 2: Second Primary Machine - Install ActiveMatrix BPM Software | 91

Task 2: Second Primary Machine - Install ActiveMatrix BPM Software

1. Log on to the second primary machine.


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

CONFIG_HOME\tibcohost\Admin-ActiveMatrixEnterpriseName-ActiveMatrixServerName\host\bin\tibcohost.exe stop -wait true

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


5. Start the TIBCO Host instance. For example, use the command:

CONFIG_HOME\tibcohost\Admin-ActiveMatrixEnterpriseName-ActiveMatrixServerName\host\bin\tibcohost.exe

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

If the ActiveMatrix enterprise does not contain a replicated ActiveMatrix Administrator server, skip this step and instead go straight on to Task 4: Primary Machine - Install ActiveMatrix BPM Software.

Screen Requirement




Select Use an existing TIBCO_HOME, then 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 3: Second Primary Machine - Upgrade the ActiveMatrix Host Instance and ActiveMatrix Administrator

1. If you are running on a Windows platform, make sure that the TIBCO Host configuration folder, or any sub-folder or file in this folder’s hierarchy, is not currently locked by Windows. This folder is:

CONFIG_HOME\tibcohost\Admin-ActiveMatrixEnterpriseName-ActiveMatrixServerName

For example, a folder is locked if it is displayed in Windows Explorer or if a command shell is open with the folder as the current directory.

2. In TIBCO Configuration Tool, click Edit ActiveMatrix BPM > Upgrade TIBCO ActiveMatrix BPM Instance.

3. In the wizard, make sure that you complete the following screens/fields as shown.

If a folder or file in this hierarchy is locked, the Upgrade ActiveMatrix TIBCO Host Instance configuration task will fail.

Screen Requirement

ActiveMatrix BPM Upgrade: Administrator Server Configuration

Enter the details of the ActiveMatrix Administrator server that manages the BPM system that you want to upgrade.

ActiveMatrix BPM Upgrade: Upgrade Configuration

1. In the ActiveMatrix Platform Upgrade Details section, select the TIBCO Host Instance that hosts the replicated ActiveMatrix Administrator server.

2. In the ActiveMatrix BPM Upgrade Details section, enter the Application Name and Environment Name of the BPM system that you want to upgrade.


Task 3: Second Primary Machine - Upgrade the ActiveMatrix Host Instance and ActiveMatrix Administrator | 93


1. upgrades SystemHost to the new version of the ActiveMatrix platform.

2. upgrades ActiveMatrix Administrator to the new version.

ActiveMatrix BPM Upgrade: Summary 1. Select the following options:

— Upgrade ActiveMatrix TIBCO Host Instance

— Upgrade ActiveMatrix Administrator

2. Clear the following options (if they are present):

— Upgrade Nodes Hosting ActiveMatrix BPM Instance

— Upgrade ActiveMatrix BPM Instance Application

3. Click Configure.

Screen Requirement



Task 4: Primary Machine - Install ActiveMatrix BPM Software



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

CONFIG_HOME\tibcohost\Admin-ActiveMatrixEnterpriseName-ActiveMatrixServerName\host\bin\tibcohost.exe stop -wait true




CONFIG_HOME\tibcohost\Admin-ActiveMatrixEnterpriseName-ActiveMatrixServerName\host\bin\tibcohost.exe


Screen Requirement






Post-Install summary Clear Launch TIBCO Configuration Tool.


Task 5: Primary Machine - Upgrade the ActiveMatrix Host Instance and ActiveMatrix Administrator | 95

Task 5: Primary Machine - Upgrade the ActiveMatrix Host Instance and ActiveMatrix Administrator







Screen Requirement




1. In the ActiveMatrix Platform Upgrade Details section, select the TIBCO Host Instance that hosts the BPM system you want to upgrade.





1. upgrades SystemHost to the new version of the ActiveMatrix platform.

2. upgrades ActiveMatrix Administrator to the new version.

ActiveMatrix BPM Upgrade: Summary 1. Select the following options:

— Upgrade ActiveMatrix TIBCO Host Instance

— Upgrade ActiveMatrix Administrator

2. Clear the following options (if they are present):

— Upgrade Nodes Hosting ActiveMatrix BPM Instance

— Upgrade ActiveMatrix BPM Instance Application

Note: If the BPM system does not contain any remote machines (that host a BPM node but not an ActiveMatrix Administrator server), you can instead select these options, allowing you to upgrade ActiveMatrix BPM as part of the same operation - see ActiveMatrix BPM Upgrade: Summary on Task 8: Primary Machine - Upgrade ActiveMatrix BPM for more information.

3. Click Configure.

Screen Requirement


Task 6: Remote Machine - Install ActiveMatrix BPM Software | 97

Task 6: Remote Machine - Install ActiveMatrix BPM Software

1. Log on to the remote machine.

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

CONFIG_HOME\tibcohost\hostName\host\bin\tibcohost.exe stop -wait true





CONFIG_HOME\tibcohost\hostName\host\bin\tibcohost.exe


Screen Requirement









Task 7: Remote Machine - Upgrade the ActiveMatrix Host Instance


CONFIG_HOME\tibcohost\InstanceName




TIBCO Configuration Tool upgrades the specified TIBCO Host instance to the new version of the ActiveMatrix platform.


Screen Requirement




In the ActiveMatrix Platform Upgrade Details section, select the TIBCO Host Instance that hosts the BPM system that you want to upgrade.

ActiveMatrix BPM Upgrade: Summary 1. Select Upgrade ActiveMatrix TIBCO Host Instance.

2. Click Configure.

If the BPM system contains additional remote machines, repeat Task 6: Remote Machine - Install ActiveMatrix BPM Software and Task 7: Remote Machine - Upgrade the ActiveMatrix Host Instance on each remote machine.

Do not proceed to Task 8: Primary Machine - Upgrade ActiveMatrix BPM until you have upgraded each remote machine.


Task 8: Primary Machine - Upgrade ActiveMatrix BPM | 99

Task 8: Primary Machine - Upgrade ActiveMatrix BPM







Screen Requirement




1. In the ActiveMatrix Platform Upgrade Details section, select the TIBCO Host Instance that hosts the BPM system you want to upgrade.





1. upgrades each BPM node to the new version of the ActiveMatrix platform.

2. upgrades the ActiveMatrix BPM application on each node to the new version.

ActiveMatrix BPM Upgrade: Summary

Select the following options:

• Upgrade Nodes Hosting ActiveMatrix BPM Instance

• Upgrade ActiveMatrix BPM Instance Application

Then:

• If the string [Upgrading Database Instance] is appended to the Upgrade ActiveMatrix BPM Instance Application action (indicating that you chose to automatically upgrade the ActiveMatrix BPM database), click Configure.

• If the string [Not Upgrading Database Instance] is appended to the Upgrade ActiveMatrix BPM Instance Application action (indicating that you chose to manually upgrade the ActiveMatrix BPM database), see Manually Upgrading the BPM Database for information about how to complete the configuration process.

Screen Requirement


Task 9: Perform Post-Upgrade Tasks | 101

Task 9: Perform 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-ActiveMatrixEnterpriseName-ActiveMatrixServerName\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.

3. Restore any Openspace Customizations.


| 103

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 105

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

• Post-Installation Tasks, page 157

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

• Post-Installation Tasks, page 157


104 | II - INSTALLATION AND UPGRADE PROCEDURES


| 105

Chapter 8 Preparing for Installation or Upgrade

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

Topics

• Check For Any Late Breaking Information, page 106

• Check the System Requirements, page 107

• Configure TIBCO Enterprise Message Service, page 108

• Create the External ActiveMatrix Administrator Database, page 109

• Configure the BPM Database Server, page 112

• Create a Database to Hold the BDS Case Data Store (DB2 Only), page 115

• Configure the External LDAP Directory Server, page 116

• Configure System Parameters on UNIX or Linux Platforms, page 117

• Configure Apache Ant, page 118

• Download Required Third-Party Software Assemblies, page 119

• Download ActiveMatrix BPM Software, page 121

• Take a Backup of the Existing ActiveMatrix BPM System, page 122

• Remove any Indexes Added to the BPM Database, page 123

• Back Up Workspace, page 124

• Back Up Openspace Customizations, page 126

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.


106 | Chapter 8 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 | 107

Check the System Requirements

Make sure that the following meet all the requirements described in System Requirements:

• the machine on which you wish to install the BPM system.

• any supporting infrastructure.



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 H, 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 a TIBCO ActiveMatrix BPM system. (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 216.)

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.


Create the External ActiveMatrix Administrator Database | 109

Create the External ActiveMatrix Administrator Database

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:

• Creating the ActiveMatrix Administrator Database Using SQL Server

• Creating the ActiveMatrix Administrator Database Using Oracle

• Creating the ActiveMatrix Administrator Database Using DB2

Creating the ActiveMatrix Administrator Database Using SQL Server1. Create an empty database which will be used to hold the ActiveMatrix

Administrator database tables - for example, amx.

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 the system to use to connect to the ActiveMatrix Administrator database - for example, amx_db_user. This user:

— must be a member of the db_owner role for this database

— must have this 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

You only need to perform this task if you intend to create an ActiveMatrix Administrator server. You can skip this task if you intend to use an existing ActiveMatrix Administrator server.

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 (for each BPM system) and ActiveMatrix Administrator database can, if desired, use the same SQL Server database instance.



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.

Creating the ActiveMatrix Administrator Database Using Oracle1. Create an empty database which will be used to hold the ActiveMatrix


2. Create a database user (or identify an existing one) for the system to use to connect to the ActiveMatrix Administrator database - for example, amx_db_user. This user:

— must not possess "dba" privileges.

— must have connect and resource privileges.

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


Creating the ActiveMatrix Administrator Database Using DB21. 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.

The ActiveMatrix BPM database (for each BPM system) and ActiveMatrix Administrator database must use separate Oracle database users/schemas. Use of separate tablespaces is also advised.

The ActiveMatrix BPM database tables (for each BPM system) and ActiveMatrix Administrator database tables must be stored in separate databases.


Create the External ActiveMatrix Administrator Database | 111

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

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.




Configure the BPM Database Server

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

Procedure See:

• Configuring SQL Server

• Configuring Oracle 11g

• Configuring DB2

Configuring SQL Server1. 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 (for each BPM system) and ActiveMatrix Administrator database can, if desired, use the same SQL Server instance.


Configure the BPM Database Server | 113

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

a. Download and install the Microsoft SQL Server JDBC Driver. See JDBC Drivers on page 24 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 (for each BPM system) and ActiveMatrix Administrator database must use separate Oracle database users/schemas. Use of separate tablespaces is also advised.



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 a suitable 32K temporary tablespace. For example:

db2 "CREATE BUFFERPOOL tbsp_pool PAGESIZE 32K"db2 "CREATE SYSTEM TEMPORARY TABLESPACE tmp_tbsp PAGESIZE

32K MANAGED BY SYSTEM USING ('/tmp/tmp_tbsp') BUFFERPOOL tbsp_pool"

6. Create an operating system user account for the BPM system 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.

7. Start the database.

The ActiveMatrix BPM database tables (for each BPM system) and ActiveMatrix Administrator database tables must use separate databases.


Create a Database to Hold the BDS Case Data Store (DB2 Only) | 115

Create a Database to Hold the BDS Case Data Store (DB2 Only)

Procedure1. Create an empty database which will be used to hold the BDS case data store -

for example, cds.

2. Create a database user (or identify an existing one) for the BPM system to use to connect to this database - for example, bpm_cds_user. Make sure that the user exists in the database. Make sure that the database is available.

You only need to perform this task if you intend to host the BDS case data store on a separate DB2 database to the ActiveMatrix BPM database.

You can skip this task if you intend to host the BDS case data store in the ActiveMatrix BPM database, or if you intend to use a separate BDS database on a platform other than DB2 (in that case, the database is created automatically).

If you are upgrading, you cannot specify the details of this database as part of the upgrade process (when you run the Upgrade TIBCO ActiveMatrix BPM Instance Wizard).

Instead, you will need to manually configure the DataSourceBDS JDBC resource template with these details as a post-installation task. See



Configure the External LDAP Directory Server

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

• the LDAP server is running.

• an LDAP directory on this LDAP 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.

If you are installing a system that is intended for production use (generally a Distributed BPM System), you must use an external LDAP directory server.

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


Configure System Parameters on UNIX or Linux Platforms | 117

Configure System Parameters on UNIX or Linux Platforms

1. Set the maximum number of open files/file descriptors.

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.

2. If you are using IBM AIX v6.x or v7.x, make sure that the system-wide, soft limit for the data user process resource is set to a value of at least 512Mb. If this limit is set to a lower value, the ActiveMatrix system node and any BPM nodes will fail to start, with an "OutOfMemory Native memory exhausted" error.

The following is an example of how you can set this value:

a. Log in as root and run the following command:

$ chuser data=1048576 root

where 1048576 is the number of 512-byte blocks needed.

b. Log in as the BPM user and run the following command (as the root user)$ ulimit -Sd

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



Configure Apache Ant

On each machine that will be part of the ActiveMatrix BPM system, 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%\tibcojre64\1.7.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.7.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 Third-Party Software Assemblies | 119

Download Required Third-Party 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 third-party LGPL software assemblies before you install ActiveMatrix BPM:

• Hibernate

• Eclipse SWT GTK module (only required if you are installing on a Linux or Solaris platform)

• Oracle Java 7 Elliptic Curve Cryptography (ECC) library (only required if you are installing on a Linux, Solaris or Windows platform)

You will make these assemblies available to the ActiveMatrix BPM installer as part of the installation process. (See Installing ActiveMatrix BPM Software (TIBCO Universal Installer).)

To download the required software assemblies:

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:

a. Click Download for the Eclipse SWT GTK module installation link, which is listed with the software for your chosen platform as:

TIB_product_tibco_eclipse_lgpl_3.5.2.001_OSplatform.html

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




6. If you are installing on a Windows, Linux or Solaris platform:

a. Click Download for the Oracle ECC library installation link, which is listed with the software for your chosen platform as:

TIB_product_tibco_sunec_1.7.0.021_OSplatform.html

b. Save the product_tibco_sunec_1.7.0.021_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 | 121

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 will be running the ActiveMatrix BPM installer.

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.




Take a Backup of the Existing ActiveMatrix BPM System

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

To take a backup of the BPM system, copy the following to a different location (possibly on a different machine):

• Installation folders on all the machines 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 BPM database and ActiveMatrix Administrator database. Refer to the documentation supplied with your database server for information on how to do this.

• the EMS server. See the TIBCO Enterprise Message Service documentation for more information on how to do this.

You only need to perform this task if you are upgrading an existing BPM system.

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


Remove any Indexes Added to the BPM Database | 123

Remove any Indexes Added to the BPM Database

If you have added any indexes to your BPM database, you should remove them 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.




Back Up Workspace

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.

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.



Back Up Workspace | 125

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.

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



Back Up Openspace Customizations

1. Back up any Openspace configuration files that you have changed under the following location:

CONFIG_HOME\tibcohost\Admin-enterpriseName-adminServerName\host\plugins\com.tibco.openspace.login_version\resources

See TIBCO Openspace Customization Guide for more information.

After completing the upgrade, you will need to replace the installed configuration files with the backed up configuration files.

2. If you have changed the configuration of the Standard persona (themes, layouts, tabs and/or gadgets), make a note of the changes. The upgrade process resets the Standard persona configuration to be the same as the Default persona. You will therefore need to re-apply your changes to the Standard persona after completing the upgrade.


The location of the Openspace resources folder has changed in ActiveMatrix BPM version 2.2 to:

CONFIG_HOME\tibcohost\Admin-enterpriseName-adminServerName\data_version\host\plugins\com.tibco.openspace.login_version\resources


| 127

Chapter 9 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 129

• Installing in Console mode, page 132

• Installing in Silent Mode, page 133

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



128 | Chapter 9 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 129.

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

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

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

Installing in GUI Mode

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

2. Run TIBCOUniversalInstaller.

3. Read through the license agreement, select I accept the terms of the license agreement, and click Next.

4. Choose a new installation environment (TIBCO_HOME) or an existing installation environment, 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.

5. Click Next.

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.

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 (").



6. In the Installation Profile Selection screen, select:

— Primary machine, if you are installing BPM software on a machine that will (or does already) host an ActiveMatrix Administrator server (whether or not it also hosts any BPM nodes).

— Remote machine, if you are installing BPM software on a machine that will (or does already) host a BPM node (of any type) but not an ActiveMatrix Administrator server.

7. In the TIBCO Configuration Directory screen, select the directory where configuration information for this BPM system will be stored (CONFIG_HOME). Make sure that the selected directory is not the configuration directory for another TIBCO installation environment.

8. Click Next. An LGPL License Agreement screen appears - this is for Hibernate.

9. Read the text and click I accept the terms of the license agreement, then click Next. If the Hibernate software assembly is not already in the assemblies subdirectory of your temporary directory, the Download Hibernate screen displays. Choose either:

— Download Hibernate assembly from TIBCO to let the installer download the Hibernate assembly from TIBCO. Click Next. The installer downloads the assembly to the assemblies subdirectory of the temporary directory containing the extracted ActiveMatrix BPM archive file.

— Select the Hibernate assembly previously downloaded from TIBCO to select the location of a previously downloaded Hibernate assembly that the installer can use (see Download Required Third-Party Software Assemblies). Click Next.

10. If you are installing on a Linux or Solaris platform, an LGPL License Agreement screen appears - this is for the Eclipse SWT GTK module. Accept the license agreement and download or select the assembly in the same way that you did for Hibernate. (Note that the Download screen refers to the Eclipse GNOME Binding assembly.)

11. If you are installing on a Windows, Linux or Solaris platform, an LGPL License Agreement screen appears - this is for the Oracle Elliptic Curve Cryptography library. Accept the license agreement and download or select the assembly in the same way that you did for Hibernate.

You will now need to accept license agreements for third-party LGPL assemblies that are required by the installer, and make those assemblies available to the installer


Installing in GUI Mode | 131

12. In the Pre-Install Summary screen, verify the list of products selected for installation, then click Install.

13. When the Post-Install Summary screen is displayed:

a. Review the list of products that have been installed.

b. Select or Clear Launch TIBCO Configuration Tool, as appropriate for your particular installation/upgrade scenario and stage. (See I - INSTALLATION AND UPGRADE SCENARIOS.)

c. Click Finish to complete the installation process and close the installer window.



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) for details.


Installing in Silent Mode | 133

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 required entry keys. Refer to the file for a description of each entry key.

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.

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.

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


| 135

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

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

Topics

• Using TIBCO Configuration Tool to Configure ActiveMatrix BPM, page 136

• Running TIBCO Configuration Tool in GUI Mode, page 138

• Running TIBCO Configuration Tool in Console Mode, page 143

• Running a TIBCO Configuration Tool Wizard in Silent Mode, page 146

• Manually Creating the BPM Database, page 150

• Manually Upgrading the BPM Database, page 151

• Manually Running BPM Database Creation or Upgrade Scripts, page 154

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



136 | Chapter 10 Configuring ActiveMatrix BPM Runtime Objects (TIBCO Configuration Tool)

Using TIBCO Configuration Tool to Configure ActiveMatrix BPM

You can use TIBCO Configuration Tool to perform a number of different ActiveMatrix BPM configuration tasks (as shown in Table 3, TIBCO Configuration Tool Wizards available on a primary machine).

TIBCO Configuration Tool ModesYou can run TIBCO Configuration Tool in three modes:

• GUI mode presents a number of different wizards. Each wizard allows you to enter the necessary configuration data, then choose and execute the relevant configuration actions. You can also save the configuration data for subsequent editing and use in silent mode. See Running TIBCO Configuration Tool in GUI Mode.

• Console mode presents a number of different menus and pages that you can use from the command line. (These menus and pages correspond to the wizards and screens provided in GUI mode.) Each menu allows you to enter the necessary configuration data, then choose and execute the relevant configuration actions. You can also save the configuration data for subsequent editing and use in silent mode. See Running TIBCO Configuration Tool in Console Mode.

• Silent mode allows you to run a particular TIBCO Configuration Tool wizard without any user interaction, using configuration data saved (and subsequently edited as required) from an earlier GUI or console mode session. See Running a TIBCO Configuration Tool Wizard in Silent Mode.

LoggingWhen you run a TIBCO Configuration Tool wizard to perform a particular configuration task, log files are created and stored under the folder specified in the Session Scripts and Log Folder field of the wizard’s Summary screen.

By default this folder is:

CONFIG_HOME\tct\wizardID\timestamp

For ease of explanation, the instructions for specific installation or upgrade scenarios (see I - INSTALLATION AND UPGRADE SCENARIOS) assume the use of GUI mode. You can instead use console mode or (where appropriate) silent mode.


Using TIBCO Configuration Tool to Configure ActiveMatrix BPM | 137

where wizardID is one of the values in the following table.

The logs sub-folder contains a separate log file for each configuration action executed by TIBCO Configuration Tool. Log files are created when you click Save or Configure from a wizard screen.

Examination of log files may assist you if you encounter a problem when running a TIBCO Configuration Tool wizard.

wizardID Wizard

tpclshells Configure Third-Party Driver Wizard

bpm Create TIBCO ActiveMatrix BPM Server Wizard

admin Create TIBCO ActiveMatrix Administrator Server Wizard

tibcohost Create TIBCO Host Instance Wizard

bpmnodetype Configure TIBCO ActiveMatrix BPM Server Node Type Wizard

admin.replicate Replicate TIBCO ActiveMatrix Administrator Server Wizard

bpmedit Edit TIBCO ActiveMatrix BPM Instance Wizard

bpmupgrade Upgrade TIBCO ActiveMatrix BPM Instance Wizard

bpmdelete Delete TIBCO ActiveMatrix BPM Instance Wizard

admin.editor Edit TIBCO ActiveMatrix Administrator Server Configuration Wizard



Running TIBCO Configuration Tool in GUI Mode

1. If you are using an HP-UX (64-bit)/Itanium platform, make sure that the external libraries listed in Required External Libraries on an HP-UX (64-bit)/Itanium Platform are installed on the machine on which you are trying to run TIBCO Configuration Tool. If any of these libraries are missing, TIBCO Configuration Tool will not run in GUI mode.

2. Run TIBCO_HOME\bpm\n.n\bin\tct.

3. In the TIBCO Configuration Folder dialog, enter (or select) the location of the TIBCO configuration folder to be used by this BPM system., then click OK.

This is the location (referred to as CONFIG_HOME) in which configuration data generated by the BPM system - scripts, session data, configured binaries, logs, and so on - is stored.

4. In the Create new configurations screen, click the wizard that you want to run. Which wizards are available depends on whether you installed ActiveMatrix BPM software on this machine using the Primary machine or Remote machine installation profile:

— Table 3 lists the available wizards (which are grouped by function) on a primary machine.

— Table 4 lists the available wizards on a remote machine.

Table 3 TIBCO Configuration Tool Wizards available on a primary machine

Wizard Function

Create ActiveMatrix BPM

Configure Third-Party Driver Wizard

Package and install third-party client driver libraries required by ActiveMatrix BPM.

Create TIBCO ActiveMatrix BPM Server Wizard

Create a new BPM system in an ActiveMatrix enterprise.

You use this wizard to create a new BPM system in an ActiveMatrix enterprise (whether it uses a basic or distributed architecture). See I - INSTALLATION AND UPGRADE SCENARIOS.

Create TIBCO ActiveMatrix Administrator Server Wizard

Create the ActiveMatrix Administrator server for an ActiveMatrix enterprise.


Running TIBCO Configuration Tool in GUI Mode | 139

ActiveMatrix BPM HA/FT Configurations

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.

Replicate TIBCO ActiveMatrix Administrator Server Wizard

Replicate the ActiveMatrix Administrator server in an ActiveMatrix enterprise to provide high availability/fault tolerance.

See Creating an ActiveMatrix Administrator Server (Single or Replicated).

Configure TIBCO ActiveMatrix BPM Server Node Type Wizard

Add a new BPM node to an existing BPM system.

You can use this wizard to add a node of type BPM, Work Manager, Process Manager or Web Components. See Creating a Distributed ActiveMatrix BPM System.

Edit ActiveMatrix BPM

Edit TIBCO ActiveMatrix BPM Instance Wizard, page 271

Perform specific edits to the configuration of an existing BPM system. Currently the only available option is to change the SOAP version used by the BPM system. (SOAP versions 1.1 and 1.2 are supported.)

Upgrade TIBCO ActiveMatrix BPM Instance Wizard

Upgrade an existing BPM system. See Upgrading an ActiveMatrix BPM System.

Delete TIBCO ActiveMatrix BPM Instance Wizard

Delete an existing BPM system.

Edit TIBCO ActiveMatrix Administrator Server Configuration Wizard

Edit the existing ActiveMatrix Administrator server configuration.

Table 3 TIBCO Configuration Tool Wizards available on a primary machine

Wizard Function



5. Complete the wizard to perform the appropriate configuration task:

— Follow the instructions provided for your specific installation or upgrade scenario. See I - INSTALLATION AND UPGRADE SCENARIOS.

— For full details of the screens and fields available in each wizard, see III - TIBCO CONFIGURATION TOOL WIZARD REFERENCE.

— Use the following buttons to navigate through and control the actions of the wizard.

Table 4 TIBCO Configuration Tool Wizards available on a remote machine

Wizard Function

ActiveMatrix BPM HA/FT Configurations

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 TIBCO ActiveMatrix BPM Server Node Type Wizard

Add a new BPM node to an existing BPM system.

You can use this wizard to add a node of type BPM, Work Manager, Process Manager or Web Components. See Creating a Distributed ActiveMatrix BPM System.

Edit ActiveMatrix BPM

Edit TIBCO ActiveMatrix BPM Instance Wizard, page 271

Perform specific edits to the configuration of an existing BPM system. Currently the only available option is to change the SOAP version used by the BPM system. (SOAP versions 1.1 and 1.2 are supported.)

Upgrade TIBCO ActiveMatrix BPM Instance Wizard

Upgrade an existing BPM system. See Upgrading an ActiveMatrix BPM System.

Button Description

Load Load a set of configuration data saved from an earlier session of this wizard.

Save Save the current configuration data (to the location specified in the Session Scripts and Log Folder field of the Summary screen.)

Back Go to the previous screen of the wizard.


Running TIBCO Configuration Tool in GUI Mode | 141

Next Go to the next screen of the wizard.

Finish Skip the remaining screens of the wizard and go directly to the Summary screen, from which you can execute the appropriate configuration actions using the specified configuration data. (Default values will be used for all fields on skipped screens.)

Note: This button is only enabled if subsequent screens do not contain any empty fields that you must complete.

Configure Clicking Configure performs the following:

• Executes the configuration action(s) selected on the Summary screen.

• Reports and logs the progress of the configuration actions as it executes them.

• Saves the configuration data.

Logs and scripts are saved to the location specified in the Session Scripts and Log Folder field of the Summary screen.

Note: This button only appears on the Summary screen.

Cancel Discard your changes, exit the wizard without performing any configuration actions and return to the Create new configurations screen.

Close Exit the wizard and return to the Create new configurations screen.

Note: This button only appears on the Summary screen when the wizard has successfully completed execution of the selected configuration tasks.

Button Description

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.



Required External Libraries on an HP-UX (64-bit)/Itanium Platform

Before trying to run TIBCO Configuration Tool in GUI mode on an HP-UX (64-bit)/Itanium platform, make sure that the following libraries are installed on the machine on which you are trying to run TIBCO Configuration Tool:

• gtk+2-2.24.10-ia64-11.23.depot

• gcc-ia64-4.7.0.depot

• libgcc-4.2.3-ia64-11.23.depot

• glib2-2.32.3-ia64-11.23.depot

• cairo-1.12.2-ia64-11.23.depot

• atk-2.4.0-ia64-11.23.depot

• pixman-0.26.0-ia64-11.23.depot

• gdk_pixbuf-2.26.1-ia64-11.23.depot

• libpng-1.5.12-ia64-11.23.depot

• libXft-2.2.0-ia64-11.23.depot

• libXrender-0.9.7-ia64-11.23.depot

• bzip2-1.0.6-ia64-11.23.depot

• fontconfig-2.9.0-ia64-11.23.depot

• freetype-2.4.10-ia64-11.23.depot

• zlib-1.2.7-ia64-11.23.depot

• expat-2.1.0-ia64-11.23.depot

• libffi-3.0.11-ia64-11.23.depot

• intltool-0.50.2-ia64-11.23.depot

• gettext-0.18.1.1-ia64-11.23.depot

• libiconv-1.14-ia64-11.23.depot

TIBCO Configuration Tool will fail to launch in GUI mode if any of these external libraries are not installed.


Running TIBCO Configuration Tool in Console Mode | 143

Running TIBCO Configuration Tool in Console Mode

1. Open a command window in the TIBCO_HOME\bpm\n.n\bin folder and run the following command:

tct console

2. At the TIBCO Configuration Folder prompt, enter the location of the TIBCO configuration folder to be used by this BPM system.

This is the location (referred to as CONFIG_HOME) in which configuration data generated by the BPM system - scripts, session data, configured binaries, logs, and so on - is stored.

The wizard selection menu is displayed, listing the available wizards (see Table 3 and Table 4). For example, on a primary machine:

Choose one option from the list below.

[X] 1 - Create Express Developer Environment - V3.3[ ] 2 - Delete TIBCO ActiveMatrix BPM Instance - V3.0[ ] 3 - Create TIBCO ActiveMatrix Administrator Server - V3.3[ ] 4 - Create TIBCO ActiveMatrix BPM Server - V3.0[ ] 5 - Configure TIBCO ActiveMatrix BPM Server Node Type - V3.0[ ] 6 - Upgrade TIBCO ActiveMatrix BPM Instance - V3.0[ ] 7 - Edit TIBCO ActiveMatrix BPM Instance - V3.0[ ] 8 - Create TIBCO Host Instance - V3.3[ ] 9 - Configure Third-Party Driver[ ] 10 - Edit TIBCO ActiveMatrix Administrator Server Configuration - V3.3[ ] 11 - Replicate TIBCO ActiveMatrix Administrator Server - V3.3

To select an item enter its number, or enter 'q' to quit: [1]

3. Enter the number for the wizard that you want to run. The menu corresponding to the first screen of the selected wizard is displayed. For example, if you chose option 5 - Configure TIBCO ActiveMatrix BPM Server Node Type, the menu that corresponds to the Welcome screen of this wizard is displayed:

===============================================================================TIBCO ActiveMatrix BPM Server Node Type Creation Wizard===============================================================================Welcome to the ActiveMatrix BPM Server Node Type configuration wizard

This wizard will help you Create new ActiveMatrix BPM Server Node Type on this machine.Refer to TIBCO ActiveMatrix BPM installation guide for details.



[1] Configure to Secure All Communication with SSL: [no]

Choose 'N' for Next Page, 'S' for Save, 'F' for Finish, 'L' for Load File, 'C' for Cancel, or enter field number [1]

4. Complete the wizard to perform the appropriate configuration task:

— Follow the instructions provided for your specific installation or upgrade scenario. See I - INSTALLATION AND UPGRADE SCENARIOS.

— For full details of the screens and fields available in each wizard, see III - TIBCO CONFIGURATION TOOL WIZARD REFERENCE.

— Use the following commands (which are case-insensitive) to navigate through and control the actions of the wizard.

Command Description

n Enter an item’s number to select it.

ENTER Select the default option for the current page. The number of the default item for each page is shown at the end of the prompt - for example [1].

L Load a set of configuration data saved from an earlier session of this wizard.

S Save the current configuration data (to the location specified in the Session Scripts and Log Folder field of the Summary menu.)

N Go to the next page of the wizard.

P Go to the previous page of the wizard.

F Skip the remaining pages of the wizard and go directly to the Summary menu, from which you can execute the appropriate configuration actions using the specified configuration data. (Default values will be used for all fields on skipped pages.)

Note: This command is only available if subsequent pages do not contain any empty fields that you must complete.


Running TIBCO Configuration Tool in Console Mode | 145

G Entering G performs the following:

• Executes the configuration action(s) selected on the Summary menu.

• Reports and logs the progress of the configuration actions as it executes them.

• Saves the configuration data.

• Returns to the wizard selection menu.

Logs and scripts are saved to the location specified in the Session Scripts and Log Folder field of the Summary menu.

Note: This command is only available on the Summary menu.

C Discard your changes, exit the wizard without performing any configuration actions and return to the wizard selection menu.

Q Exit TIBCO Configuration Tool.

Note: This command is only available on the wizard selection menu.

Command Description



Running a TIBCO Configuration Tool Wizard in Silent Mode

1. Generate and save a build.properties file for the wizard that you want to run silently, by running TIBCO Configuration Tool in GUI mode or console mode. See The build.properties File.

2. Using a text editor, edit the build.properties file so that it contains the values you want to use when you run the wizard silently.


tct command propertiesFile

where:

— command is one of the commands listed in Table 5.

— propertiesFile is the full pathname of the build.properties file that contains the configuration data you want to use in this session. (If the pathname includes spaces you must enclose it within quotation marks.)

3. If you are going to run the Create TIBCO ActiveMatrix BPM Server Wizard or Upgrade TIBCO ActiveMatrix BPM Instance Wizard, and you have chosen to manually create or upgrade the BPM database, get a database administrator to manually create or upgrade the database. See Manually Running BPM Database Creation or Upgrade Scripts, page 154. You must do this before you run the wizard silently.

Table 5 TIBCO Configuration Tool Silent Mode Commands

tct command Description

Silent deployment options:

tpcl Runs the Configure Third-Party Driver Wizard.

tibcohost Runs the Create TIBCO Host Instance Wizard.

admin Runs the Create TIBCO ActiveMatrix BPM Server Wizard, but only executes the Create TIBCO ActiveMatrix Administrator server configuration action.

bpmonly Runs the Create TIBCO ActiveMatrix BPM Server Wizard, but only executes the Create ActiveMatrix BPM configuration action.

bpm Runs the Create TIBCO ActiveMatrix BPM Server Wizard.


Running a TIBCO Configuration Tool Wizard in Silent Mode | 147

bpmnodetype Runs the Configure TIBCO ActiveMatrix BPM Server Node Type Wizard.

Upgrade options:

upgrade Runs the Upgrade TIBCO ActiveMatrix BPM Instance Wizard.

upgrade-tibcohost Runs the Upgrade TIBCO ActiveMatrix BPM Instance Wizard, but only executes the Upgrade ActiveMatrix TIBCO Host Instance configuration action.

upgrade-admin Runs the Upgrade TIBCO ActiveMatrix BPM Instance Wizard, but only executes the Upgrade ActiveMatrix Administrator configuration action.

upgrade-bpmnodes Runs the Upgrade TIBCO ActiveMatrix BPM Instance Wizard, but only executes the Upgrade Nodes Hosting ActiveMatrix BPM Instance configuration action.

upgrade-bpm Runs the Upgrade TIBCO ActiveMatrix BPM Instance Wizard, but only executes the Upgrade ActiveMatrix BPM Instance Application configuration action.

downgrade-bpm Enables you to remove a hotfix from a running instance of ActiveMatrix BPM. TIBCO ActiveMatrix BPM only supports downgrading from a hotfix version either to a lower hotfix version, or to the last GA or service release the hotfix was applied to. For example, you can downgrade from 2.2.0_HF001 to 2.2.0 GA but not from 2.2.0 GA to 2.1.0 GA. Please refer to the documentation supplied with your hotfix for information on how to downgrade TIBCO ActiveMatrix BPM.

Edit options:

delete-bpm Runs the Delete TIBCO ActiveMatrix BPM Instance Wizard

edit-bpm Runs the Edit TIBCO ActiveMatrix BPM Instance Wizard

To display usage instructions for TIBCO Configuration tool from the command window, enter the command:

tct help

Table 5 TIBCO Configuration Tool Silent Mode Commands

tct command Description



The build.properties FileWhen you run a TIBCO Configuration Tool wizard to perform a particular configuration task, configuration data gathered and generated by the wizard is stored in the folder specified in the Session Scripts and Log Folder field of the wizard’s Summary screen.

In this folder, the \scripts\build.properties file contains the information collected from the wizard screens. The build.properties file is created when you click Save or Configure from a wizard screen.

For example, the following is an extract from a build.properties file generated by running the Configure TIBCO ActiveMatrix BPM Server Node Type Wizard.

# The following properties may be modifiedtibco.home=C:/Programs/tibco/amx-bpm2.2tibco.config.mgmt.home=C:/ProgramData/amx-bpm2.2/tibco/data/tcttct.scripts.dir=

#BPM Node Type settingbpm.nodetype.host=BPMHostbpm.nodetype.environment=BPMEnvironmentbpm.nodetype.node=BPMNode1bpm.nodetype.node.port=6031bpm.nodetype.node.type=BPMNodebpm.nodetype.http.connector.port=8081bpm.nodetype.app.name=amx.bpm.app

# Database sizing detailsbpm.nodetype.install.size=Developmentbpm.nodetype.jvm.maxpermsize=256bpm.nodetype.jvm.xms=512bpm.nodetype.jvm.xmx=1536

The file contains a set of property/value pairs, grouped by the wizard screens to which they relate. Generally, each property represents a field on the wizard screen. In the example above:

• tibco.home is the TIBCO_HOME folder for this BPM system.

• tibco.config.mgmt.home is the CONFIG_HOME folder for this BPM system (as specified in the TIBCO Configuration Folder dialog).

• the bpm.nodetype.app.name property represents the Application Name field on the ActiveMatrix BPM Node Type: Host and Node Configuration screen. It has the value amx.bpm.app.


Running a TIBCO Configuration Tool Wizard in Silent Mode | 149

A Simple Example - Adding a New Work Manager Node to a Distributed SystemSuppose you have installed and configured a distributed BPM system (as shown in Figure 4 in Creating a Distributed ActiveMatrix BPM System). You now want to add a second Work Manager node to the BPM_Machine2. To do this:

1. Open the CONFIG_HOME\tct\bpmnodetype\timestamp\scripts\build.properties file.

# The following properties may be modifiedtibco.home=C:/Programs/tibco/amx-bpm2.2tibco.config.mgmt.home=C:/ProgramData/amx-bpm2.2/tibco/data/tcttct.scripts.dir=

#BPM Node Type settingbpm.nodetype.host=BPMHost2bpm.nodetype.environment=BPMEnvironmentbpm.nodetype.node=BPMNode2bpm.nodetype.node.port=6031bpm.nodetype.node.type=WorkManagerNodebpm.nodetype.http.connector.port=8081bpm.nodetype.app.name=amx.bpm.app

# Database sizing detailsbpm.nodetype.install.size=Developmentbpm.nodetype.jvm.maxpermsize=256bpm.nodetype.jvm.xms=512bpm.nodetype.jvm.xmx=1536

2. Change the following values (which must be unique to the new node), then save the file.

bpm.nodetype.node=BPMNode3bpm.nodetype.node.port=6033bpm.nodetype.http.connector.port=8082


tct bpmnodetype

C:\ProgramData\amx-bpm2.2\tibco\data\tct\bpmnodetype\timestamp

TIBCO Configuration Tool creates a new Work Manager node, BPMNode3, on BPM_Machine2, as part of the BPM system.



Manually Creating the BPM Database

When you use the Create TIBCO ActiveMatrix BPM Server Wizard to create a BPM system, TIBCO Configuration Tool can automatically create the BPM database, provided you have the username and password of a database server user account that has database administrator privileges (a DBA user).

If you decide that you need to manually create the BPM database, you must perform the following steps:

1. On the ActiveMatrix BPM: Database Administrator screen, clear Create BPM Database Instance.

2. On the ActiveMatrix BPM: Runtime Database Configuration screen, click Generate Scripts to create the SQL scripts required to create the database. TIBCO Configuration Tool writes these scripts to the following folder:

CONFIG_HOME\bpm\BPMApplicationName\database

3. On the Administrator Server Configuration: Summary screen, Save your configuration session data, then Cancel the wizard.

4. Get a database administrator to manually create the BPM database - see Manually Running BPM Database Creation or Upgrade Scripts.

5. Run the Create TIBCO ActiveMatrix BPM Server Wizard again to complete the configuration process, as described in your particular installation scenario.

TIBCO recommend that you allow TIBCO Configuration Tool to automatically create the ActiveMatrix BPM database unless either of the following applies:

• You do not have access to the credentials of a DBA user.

• Your database administrator wants to examine and possibly edit the database creation scripts before they are run - for example, to customize or optimize them for your particular database environment.

Do NOT click Configure at this point!


Manually Upgrading the BPM Database | 151

Manually Upgrading the BPM Database

When you use the Upgrade TIBCO ActiveMatrix BPM Instance Wizard to upgrade an existing BPM system, TIBCO Configuration Tool can automatically upgrade the BPM database if the BPM database user has the appropriate permissions on the BPM database.

If you decide that you need to manually upgrade the BPM database, you must perform the following steps:

1. On the ActiveMatrix BPM Upgrade: Upgrade Configuration screen of the Upgrade TIBCO ActiveMatrix BPM Instance Wizard:

a. Clear Automatically upgrade BPM Database Schema.

b. Click Generate Scripts to create the SQL scripts required to upgrade the database. TIBCO Configuration Tool writes the required upgrade scripts to the following folder:

CONFIG_HOME\bpm\BPMApplicationName\database

2. Click Next. The ActiveMatrix BPM Upgrade: Summary screen is displayed.

3. Use either of the following methods to complete the upgrade:

— Method 1 - Stop the BPM Application Before Upgrading It

— Method 2 - Perform the Upgrade in Two Stages

TIBCO strongly recommend that you allow TIBCO Configuration Tool to automatically upgrade the ActiveMatrix BPM database unless either of the following applies:

• The BPM database user’s permissions have been restricted post-installation - for example, to comply with corporate database usage policies.

The BPM database user is the database server user account that ActiveMatrix BPM uses to connect to the BPM database, as specified when the BPM system was created (in the ActiveMatrix BPM: Runtime Database Configuration screen of the Create TIBCO ActiveMatrix BPM Server Wizard).

• Your database administrator wants to examine and possibly edit the database upgrade scripts before they are run - for example, to customize or optimize them for your particular database environment.

Do NOT click Configure at this point!



Method 1 - Stop the BPM Application Before Upgrading It1. In ActiveMatrix Administrator:

a. Select the BPM application (for example, amx.bpm.app > System > amx.bpm.app), then click Stop.

b. In the Application Dependencies to Stop dialog, clear every application that is selected (as shown in the following example), then click Stop.

c. Refresh the display until the BPM application status displays as Stopped.

2. Get a database administrator to manually upgrade the BPM database - see Manually Running BPM Database Creation or Upgrade Scripts.

3. On the ActiveMatrix BPM Upgrade: Summary screen of the Upgrade TIBCO ActiveMatrix BPM Instance Wizard, click Configure.

Method 2 - Perform the Upgrade in Two Stages1. On the ActiveMatrix BPM Upgrade: Summary screen, click Configure.

2. Get a database administrator to manually upgrade the BPM database - see Manually Running BPM Database Creation or Upgrade Scripts.

The upgrade process will fail when it attempts to execute the Upgrade ActiveMatrix BPM Instance Application configuration task, because the BPM database has not yet been upgraded.


Manually Upgrading the BPM Database | 153

3. On the ActiveMatrix BPM Upgrade: Summary screen, select Upgrade ActiveMatrix BPM Instance Application, then click Configure.



Manually Running BPM Database Creation or Upgrade Scripts

A database administrator can, when required, manually create or update the BPM database by running the necessary scripts, previously generated by TIBCO Configuration Tool. See Manually Creating the BPM Database or Manually Upgrading the BPM Database.

To do this:

1. If necessary, edit the database scripts to run correctly on the target database, as shown in the following table.

Database Changes required

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

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

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

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

Oracle If you need to manually amend any of the BPM database 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


Manually Running BPM Database Creation or Upgrade Scripts | 155

2. Run the required BPM Database Creation Scripts or BPM Database Upgrade Scripts, as appropriate.

BPM Database Creation ScriptsTo manually create the BPM database, run the following scripts in the order shown.

DB2 Not all the database 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.

Database Changes required

Step Run the script... as ... Description

1. CONFIG_HOME\bpm\BPMApplicationName\database\admin\setup-admin.sql

a DBA user On:

• SQL Server: Creates required logins that own the schema and database.

• Oracle: Creates required tablespaces.

• DB2: You do not need to run this script.

2. CONFIG_HOME\bpm\BPMApplicationName\database\admin\createdb-admin.sql

a DBA user Creates the database and/or schema.

3. CONFIG_HOME\bpm\BPMApplicationName\database\ProcessManagerCreate.sql

the BPM database user

Creates the schema objects required by the BPM Process Manager.

4. CONFIG_HOME\bpm\BPMApplicationName\database\WorkManagerCreate.sql


Creates the schema objects required by the BPM Work Manager.



BPM Database Upgrade ScriptsTo manually upgrade the BPM database, run the following scripts in the order shown.

The BPM database user is the database server user account that ActiveMatrix BPM should use to connect to the BPM database, as specified in the ActiveMatrix BPM: Runtime Database Configuration screen of the Create TIBCO ActiveMatrix BPM Server Wizard.

Step Run the script... as the... Description

1. CONFIG_HOME\bpm\BPMApplicationName\database\ProcessManagerUpgrade.sql


Upgrades the schema objects required by the BPM Process Manager.

2. CONFIG_HOME\bpm\BPMApplicationName\database\WorkManagerUpgrade.sql


Upgrades the schema objects required by the BPM Work Manager.

The BPM database user is the database server user account that ActiveMatrix BPM should use to connect to the BPM database, as specified in the ActiveMatrix BPM: Runtime Database Configuration screen of the Create TIBCO ActiveMatrix BPM Server Wizard.


| 157

Chapter 11 Post-Installation Tasks

This chapter describes the tasks you may need to do after creating or upgrading a BPM system.

Topics

• Configure the DataSourceBDS Shared Resource, page 158

• Create Any Other Required LDAP Connections to LDAP Directories, page 159

• Configure Client Communications Through the Load Balancer, page 160

• Configure Transaction Recovery (Oracle only), page 163

• Set Transaction Verification Property (SQL Server Only), page 164

• Reorganize Event Collector Tables after Upgrade (DB2 Only), page 165

• Upgrade your Oracle JDBC Driver, page 166

• Upgrade the Openspace GlobalHubPolicy Data, page 167

• Verify the Event Collector Rules Files (After Upgrade), page 168

• Edit TIBCO Hawk® Rulebase Files, page 169

• Set up Openspace Language Use, page 170

• Restore any Openspace Customizations, page 171

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



158 | Chapter 11 Post-Installation Tasks

Configure the DataSourceBDS Shared Resource

Configure the DataSourceBDS JDBC resource template with the details of the database that will be used to hold the BDS case data store. You should have created this database earlier - see Create a Database to Hold the BDS Case Data Store (DB2 Only).

1. Log in to ActiveMatrix Administrator.

2. Click Applications, then select the ActiveMatrix BPM application (by default, amx.bpm.app).

3. On the Resource Templates tab, click DataSourceBDS. The Resource Template Details dialog is displayed.

4. On the General tab:

— In the Data Source field, select the appropriate entry for the database you are using (DB2, Sql Server or Oracle).

— In the Username and Password fields, enter the details of the database user that you created earlier.

5. On the Advanced tab, enter the Connection Properties needed for the JDBC connection string for this database.

For example, if you are using a SQL Server database, enter the appropriate values for the portNumber, serverName and databaseName.

6. On the Resource Instances tab, select the DataSourceBDS resource instance, Uninstall it, then re-Install it.

You only need to perform this task if:

1. you are upgrading an existing BPM system

and

2. you intend to host the BDS case data store in a separate database to the ActiveMatrix BPM database.


Create Any Other Required LDAP Connections to LDAP Directories | 159

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 the BPM system 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

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 the BPM system using Openspace, Workspace or a custom client application.

These resources must have their scope set to the name of the BPM application that identifies this BPM system. (This is the name specified in the AMX-BPM Application Name field of the ActiveMatrix BPM: Configuration screen, in the Create TIBCO ActiveMatrix BPM Server Wizard.)

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

If you have installed a BPM system using a distributed configuration, you must configure the system to be able to communicate properly with OpenSpace and Workspace via the load balancer.

Task A 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 B 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.


Configure Client Communications Through the Load Balancer | 161

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



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.


Configure Transaction Recovery (Oracle only) | 163

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

3. Click JVM Configuration.

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.


Reorganize Event Collector Tables after Upgrade (DB2 Only) | 165

Reorganize Event Collector Tables after Upgrade (DB2 Only)

After the upgrade, it is likely that the ec_event table needs to be reorganized. To determine if this is the case, connect to the BPM database and enter the following command:

db2 load query table bpmuser.ec_event

If a reorganization is required, the command returns the following:

Tablestate: Reorg Pending

If a reorganization of the ec_event table is required, you must do the following before continuing to use the system:

1. Log into the BPM database.

2. Run the following command :db2 reorg table bpmuser.ec_event

3. After reorganization, the results of the db2 load query table command should return Normal:

db2 load query table bpmuser.ec_eventTablestate: Normal

You only need to perform this task if:

1. you are upgrading an existing BPM system

and

2. your platform is Windows with a DB2 database.

Failing to reorganize the ec_event table can lead to events not being audited, and event views failing to display with error messages. For example:

Event Viewer: My Activity Today - View is unavailable due to server side fault

Also, the following error in the logs indicates that the ec_event table needs to be reorganized:

SQLCODE=-668, SQLSTATE=57016



Upgrade your Oracle JDBC Driver

To use the new case data features of 3.0 on Oracle, you must ensure your JDBC driver meets the minimum version requirement of 11.2.0.4.0.

If you have upgraded TIBCO ActiveMatrix BPM, ensure that you have the correct JDBC driver. You can find out the current version of the Oracle JDBC driver by looking for the following entry in the BPM log file on system startup:

16 Apr 2014 11:03:27,276 [Job_Executor4] [INFO ] org.hibernate.cfg.SettingsFactory -JDBC driver: Oracle JDBC driver, version: 11.2.0.4.0

Alternatively, locate the following folder: TIBCO_HOME/components/shared/1.0.0/plugins/com.tibco.tpcl.gen.orac

le.jdbc_11.2.100.001, open the ojdbc6 JAR file, and examine the file META-INF/MANIFEST.MF for the following entry:

Implementation-Version: 11.2.0.4.0

If your Oracle JDBC driver does not meet the minimum requirement, use the following procedure to upgrade it:

1. Shut down the entire system (Administrator and all BPM nodes on all machines).

2. On all machines, replace the file ojdbc6.jar in the folder TIBCO_HOME/components/shared/1.0.0/plugins/com.tibco.tpcl.gen.o

racle.jdbc_11.2.100.001 with the JDBC driver that meets the minimum requirement (11.2.0.4.0).

3. On all machines, replace the file ojdbc6.jar in the folder TIBCO_CONFIG_HOME/tibcohost/Admin-AMX BPM-AMX BPM

Server/data_3.2.x/host/plugins/com.tibco.tpcl.gen.oracle.jdbc_1

1.2.100.001 with the JDBC driver that meets the minimum requirement (11.2.0.4.0)

4. Start up the entire system (Administrator and all BPM nodes on all machines).


Upgrade the Openspace GlobalHubPolicy Data | 167

Upgrade the Openspace GlobalHubPolicy Data

The upgrade script does not upgrade the Openspace GlobalHubPolicy data automatically. This means that the Calendar is not displayed. To correct this:

1. Log into Openspace and open the preferences panel on any tab except Calendar, then click More Gadgets.

2. Select Manage Gadgets > Communication. The Hub Policy Administrator opens.

3. Click Delete Selected Domain. A warning appears - click OK.

4. Click Save.

5. Select Manage Gadgets > Communication to reopen the Hub Policy Administrator .

6. Click Add Hub Policy.

7. Warnings appear - click OK.

8. More warnings appear - click OK.

9. Expand the OpenspaceApp / Publish Topics to confirm that TranslationEvent2 is listed.

10. Click Save.

11. Close the Hub Policy Administrator and log out of Openspace.

12. Log into Openspace again and the Calendar is available.



Verify the Event Collector Rules Files (After Upgrade)

The event collector rules files ec-probe-rules.xml and ec-event-rules.xml have changed in this release. If you are using modified rules, after upgrade you should verify the following:

• Check that each channel is now defined in the following format:: <channel name='abcde' target='target'>.

• Verify that the rules files are configured as desired.

• Ensure the BPM.log file has no errors pertaining to the parsing of the rules files. For more information, see "Configuring TIBCO ActiveMatrix BPM Auditing" in the TIBCO ActiveMatrix BPM Administration guide.


Edit TIBCO Hawk® Rulebase Files | 169

Edit TIBCO Hawk® Rulebase Files

TIBCO Hawk® is a tool for monitoring and managing distributed applications and operating systems, and the TIBCO Configuration Tool automatically generates TIBCO Hawk rulebase files when you use it to configure your TIBCO ActiveMatrix BPM installation.

If you intend to use TIBCO Hawk, you must edit the rulebase files that were generated automatically. See the section "Editing the Rulebase Files" in the chapter "Monitoring ActiveMatrix BPM Using TIBCO Hawk® Rulebases" in TIBCO ActiveMatrix BPM - BPM Administration.

If you are upgrading ActiveMatrix BPM, or if you are creating a second or subsequent system node, the Hawk rulebase files are not automatically generated. Use the genhawkrulebase utility to create them, as described in "Generating Hawk Rulebases from the Command Line" in TIBCO ActiveMatrix BPM - BPM Administration.



Set up Openspace Language Use

By default, Openspace automatically provides two built-in language packs (American English and British English). Openspace also provides a locale.properties files that lists all 57 known locales that are available.

When Openspace loads, it checks whether any of the language packs for the 57 locales have been installed. If a language pack is installed, then Openspace loads the relevant data for the installed language pack. However, testing for a large number of potential locales can have an impact on the time taken to load Openspace.

To minimize the time that Openspace takes to load, TIBCO recommend that you amend the locale.limit property in the Openspace config.properties file to limit the number of locales that Openspace tests for to suit your requirements.

See "Localizing Openspace Overview > Manually Localizing Openspace Overview", in TIBCO Openspace Customization Guide for information about how to do this.


Restore any Openspace Customizations | 171

Restore any Openspace Customizations

1. Restore any Openspace configuration files that you backed up to the following location:

CONFIG_HOME\tibcohost\Admin-enterpriseName-adminServerName\data_version\host\plugins\com.tibco.openspace.login_version\resources

2. Re-apply any changes that you wanted to keep to the configuration of the Standard persona (themes, layouts, tabs and/or gadgets), then apply the Standard persona to all users.

3. when upgrading a system to 2.2 that uses a theme number that is either not available or has changed allocated number.

If the fifth or sixth theme was referenced previously, it must be re-enabled and mapped to the previous name/colour before users log into Openspace after the upgrade.

See Back Up Openspace Customizations for more information.



| 173

III - TIBCO CONFIGURATION TOOL WIZARD REFERENCE

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

Topics

• Configure Third-Party Driver Wizard, page 175

• Create TIBCO ActiveMatrix BPM Server Wizard, page 179

• Create TIBCO ActiveMatrix Administrator Server Wizard, page 207

• Create TIBCO Host Instance Wizard, page 241

• Configure TIBCO ActiveMatrix BPM Server Node Type Wizard, page 249

• Replicate TIBCO ActiveMatrix Administrator Server Wizard, page 257

• Edit TIBCO ActiveMatrix BPM Instance Wizard, page 271

• Upgrade TIBCO ActiveMatrix BPM Instance Wizard, page 281

• Delete TIBCO ActiveMatrix BPM Instance Wizard, page 289

• Edit TIBCO ActiveMatrix Administrator Server Configuration Wizard, page 297


174 | III - TIBCO CONFIGURATION TOOL WIZARD REFERENCE


| 175

Chapter 12 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 176

• Third-Party Driver: JAR Folder, page 177

• Third-Party Driver: Summary, page 178

You can only run this wizard on a machine if you used the Primary machine installation profile when you installed the ActiveMatrix BPM software on that machine.

If you installed the ActiveMatrix BPM software using the Remote machine installation profile, you cannot run this wizard.


176 | Chapter 12 Configure Third-Party Driver Wizard

Third-Party Driver: Details

Field Description

Driver Type The type of driver being configured.

Default: JDBC

Driver The supported drivers:

• JDBC

— TIBCO enabled JDBC driver for Microsoft SQL Server 3.0

— TIBCO enabled JDBC driver for Microsoft SQL Server 4.0





• JMS

— TIBCO enabled JMS client for Sonic 6.1.0

— TIBCO enabled JMS client for WebSphere 7.0.02

• SiteMinder

— TIBCO enabled SiteMinder SDK libraries for SiteMinder Agent 12.0.0

— TIBCO enabled SiteMinder SDK libraries for SiteMinder Agent 6.0.0

1. Not supported for ActiveMatrix Administrator and ActiveMatrix JDBC resource templates.

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

Third-Party Driver: JAR Folder

Field Description

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


178 | Chapter 12 Configure Third-Party Driver Wizard

Third-Party Driver: Summary

Field/Button Description

Session Scripts and Log Folder

The location where scripts and logs generated by this TIBCO Configuration Tool session are stored.

Default: CONFIG_HOME\tct\tpclshells\timestamp

Click Configure to execute the following action:

Configure Third-Party Driver

Whether to configure the specified third-party driver.

Default: Selected


| 179

Chapter 13 Create TIBCO ActiveMatrix BPM Server Wizard

This chapter provides reference information about the TIBCO Configuration Tool Configure TIBCO ActiveMatrix BPM Server wizard.

Topics

• Welcome, page 180

• ActiveMatrix BPM: Database Administrator, page 181

• ActiveMatrix BPM: Runtime Database Configuration, page 183

• ActiveMatrix BPM: BDS Database Configuration, page 185

• ActiveMatrix BPM: Configuration, page 187

• ActiveMatrix BPM: Sizing Configuration, page 191

• ActiveMatrix BPM: JMS Configuration, page 193

• ActiveMatrix BPM: LDAP Configuration, page 196

• ActiveMatrix BPM: SiteMinder Configuration, page 199


• ActiveMatrix BPM: Host and Node Configuration, page 204

• Administrator Server Configuration: Summary




180 | Chapter 13 Create TIBCO ActiveMatrix BPM Server Wizard

Welcome


Standard Installation (all wizard panels)

Whether to choose a Standard (selected) or Express (cleared) installation.

Choosing Standard gives you access to all configuration options. You have access to all subsequent screens in this wizard.

Note: You must choose Standard if you want to use an existing ActiveMatrix Administrator server.

Choosing Express (cleared) allows you to quickly create a new BPM system and ActiveMatrix Administrator Server, using mostly default configuration options. You only have access to the following screens in this wizard. Settings for all other screens will take their default values (or, those from a previously saved set of configuration data, if you have Loaded one).

1. ActiveMatrix BPM: Database Administrator

2. ActiveMatrix BPM: Runtime Database Configuration

3. ActiveMatrix BPM: Configuration

4. Administrator Server Configuration: Database Details

5. Administrator Server Configuration: Summary

Default: Selected (Standard)

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: Database Administrator | 181



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. See Manually Creating the BPM Database for more information about how to choose whether to automatically or manually create the database.

When cleared, you must manually create the database instead, using the scripts generated from the ActiveMatrix BPM: Runtime Database Configuration screen.

Default: Selected

build.properties entry: bpm.db.create.schema

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.

build.properties entries: bpm.db.type, bpm.db.feature.name, bpm.db.feature.version, bpm.db.driver, bpm.db.xa.driver and bpm.db.dialect. (Do not edit these entries manually.)

URL JDBC connection string needed to connect to the database server.

Note: For a Microsoft SQL Server database:

• you must use the following format for the URL: jdbc:sqlserver://host:port;DatabaseName=dbNname.

• you cannot use a literal IPV6 address for host.

build.properties entry: bpm.db.admin.url

DBA Username Credentials of a database server user account that has database administrator privileges. See Database User Account Requirements.

TIBCO Configuration Tool will use this account to connect to the database server to create the BPM database. If you do not have access to a suitable account, you will need to manually create the BPM database

build.properties entry: bpm.db.admin.username



DBA Password Password for the specified DBA Username.

build.properties entry: bpm.db.admin.password

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 Administrator database and the BPM database must each use a separate tablespace.

• If multiple BPM databases are hosted on this server, each subsequent BPM database must also use a separate tablespace.

If the BPM database is being hosted on SQL Server or DB2 this field is ignored.

Default: bpm_tablespace

build.properties entry: bpm.db.tablespace

Test Connection Verifies that TIBCO Configuration Tool can connect to the database server using the information supplied on this page.



ActiveMatrix BPM: Runtime Database Configuration | 183



URL JDBC connection string that identifies the ActiveMatrix BPM database to be used by this BPM system.

ActiveMatrix BPM will use this string to connect to this ActiveMatrix BPM database.

build.properties entries: bpm.db.url, plus other database specific entries representing the different URL components - for example, on SQL Server: bpm.db.dbname, bpm.db.port and bpm.db.servername.

Username Database server user account that ActiveMatrix BPM should use to connect to this ActiveMatrix BPM database. TIBCO Configuration Tool automatically creates the specified account if it does not already exist.

The specified Username must be unique to this BPM system; you cannot use an existing user account that is used by a different BPM database on this server.

If you are using a DB2 database, this must be the name of an existing operating system user - see Configuring DB2 on page 114.

Default: bpmuser

build.properties entry: bpm.db.username

Password Password for the specified Username.

build.properties entry: bpm.db.password

Confirm Password Password for the specified Username.



Test Connection Verifies that TIBCO Configuration Tool can connect to the specified 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 specified ActiveMatrix BPM database.

You must generate the database creation scripts if you chose to manually create the database in the ActiveMatrix BPM: Database Administrator screen. See Manually Running BPM Database Creation or Upgrade Scripts for more information about how to manually create the database.



ActiveMatrix BPM: BDS Database Configuration | 185

ActiveMatrix BPM: BDS Database Configuration


Use different database to other AMX-BPM components

Whether ActiveMatrix BPM should host the BDS case data store in the ActiveMatrix BPM database or in a separate database.

• When selected, the BDS case data store will be hosted in a separate database. The remaining fields on this page are available. The database type of both BDS case data store and the ActiveMatrix BPM database should be the same.

• When cleared, the BDS case data store will be hosted in the ActiveMatrix BPM database, as specified on the ActiveMatrix BPM: Runtime Database Configuration screen.

Default: Cleared

build.properties entry: bpm.bds.owndatabase

URL JDBC connection string that identifies the database to be used to host the BDS case data store. (See Create a Database to Hold the BDS Case Data Store (DB2 Only).)

In the case of DB2, this database must have been created previously. For other databases, the specified URL will be used to automatically create the database.

ActiveMatrix BPM will use this string to connect to the BDS case data store.

build.properties entries: bpm.bds.url, plus other database specific entries representing the different URL components - for example, on SQL Server: bpm.bds.dbname, bpm.bds.port, bpm.bds.xadriver, bpm.bds.dialect and bpm.bds.servername.

BDS Username Database server (or for DB2, operating system) user account that ActiveMatrix BPM should use to connect to the specified database URL. (See Create a Database to Hold the BDS Case Data Store (DB2 Only).)

If you are using a DB2 database, this must be the name of an existing operating system user - see Create a Database to Hold the BDS Case Data Store (DB2 Only).

Default: bpmuser

build.properties entry: bpm.bds.username



BDS Password Password for the specified BDS Username.

build.properties entry: bpm.bds.password

Tablespace Name Name of the Oracle tablespace in which to create tables for the BDS case data store:

• TIBCO Configuration Tool will create this tablespace if it does not already exist.

• The Administrator database, BPM database and BDS case data store must each use a separate tablespace.

• If multiple BDS case data stores (for different BPM systems) are hosted on this server, each BDS case data store must use a separate tablespace.

If the BDS case data store is being hosted on a SQL Server or DB2 database this field is ignored.

Default: bds_tablespace

build.properties entry: bpm.bds.tablespace

Test Connection Verifies that TIBCO Configuration Tool can connect to the specified database using the information supplied on this page.



ActiveMatrix BPM: Configuration | 187



AMX-BPM Application Name

The name by which to identify this particular ActiveMatrix BPM application instance (that is, this particular BPM system).

Each BPM system in the same ActiveMatrix environment must have a unique application name.

Default: amx.bpm.app

build.properties entry: bpm.app.name

HTTP Work Presentation Host

Name used to externally identify the machine that hosts this BPM system.

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

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.

Note: If this BPM system is distributed across different machines (to provide high availability and/or scalability), this should be the name of the load balancer. See Load Balancer.

Default: localhost

build.properties entry: bpm.http.host

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 any other ActiveMatrix node on the same machine.

Note: If this BPM system is distributed across 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: 8080

build.properties entry: bpm.http.port



SOAP Binding Version

Version of the SOAP specification that will be applied to all SOAP bindings:

• on services exposed by this instance of the ActiveMatrix BPM application.

• on services and references exposed by process applications deployed to this BPM system.

SOAP versions 1.1 and 1.2 are supported.

Default: 1.1

build.properties entry: bpm.soap.version

SMTP Host Name of the machine that hosts the SMTP server that is used by this BPM system 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

build.properties entry: bpm.smtp.host

SMTP Port Port number on which the SMTP server is running.

Default: 25

build.properties entry: bpm.smtp.port

Override BPM Configuration Folder

Whether to override the default location of the BPM configuration folder. Select this option if this BPM system is distributed across different machines (to provide high availability and/or scalability).

If selected, the Configuration Folder field is displayed.

Default: Cleared

build.properties entry: bpm.config.home.root.override

Configuration Folder

The location of the BPM configuration folder.

If this BPM system is distributed across 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

build.properties entry: bpm.config.home.root



ActiveMatrix BPM: Configuration | 189

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 for a BPM system that is distributed across 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.

build.properties entry: bpm.http.secure, bpm.client.enablessl

SSL Configuration fields (only visible if Enable SSL for HTTP Port is selected)

Self-signed Certificate

Indicates that this BPM system 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

build.properties entry: bpm.client. autogeneratekeystore=true

Imported Certificate

Indicates that this BPM system will identify itself to clients with a certificate that should be imported into ActiveMatrix Administrator.

When selected, the Keystore fields are enabled.

Default: Cleared

build.properties entry: bpm.client. autogeneratekeystore=false

Keystore Location The location of the keystore to import.

build.properties entry: bpm.client. keystorelocation




Keystore Type The type of the keystore.

Default: JKS

build.properties entry: bpm.client. keystoretype

Keystore Password The password required to access the keystore.

build.properties entry: bpm.client. keystorepassword

Key Alias The key alias that identifies the entry in the keystore for this BPM system.

build.properties entry: bpm.client. keyalias

Key Password The password required to access the key alias.

build.properties entry: bpm.client. keypassword

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

ActiveMatrix BPM: Sizing Configuration


Environment Type of sizing environment being set up. Choose from the options: Development and Production.

The sizing environment you choose in this field determines the default values provided for the remaining fields on this screen.

Default: Development

build.properties entry: bpm.sizing.install.size (The property value can be either dev or prod.)

Database Connection Pool Size

Number of database connections available for each of the ActiveMatrix BPM DataSource resource templates.

Development default: 10

Production default: 50

build.properties entry: bpm.sizing.database.connection.pool.size

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.



build.properties entry: bpm.sizing.database.stmt.cache.size

Number of Process Engine Threads

Number of threads in the Process Engine background thread pool.



build.properties entry: bpm.sizing.pvm.threads

Max Java PermGen Size

Maximum size for Java PermGen.



build.properties entry: bpm.sizing.jvm.maxpermsize



Number of Message Threads

Range for the message threads.

Development default: Core: 5 Maximum: 10

Production default: Core: 10 Maximum: 20

build.properties entry: (Core) bpm.sizing.core.msg.threads and (Maximum) bpm.sizing.max.msg.threads

Java Heap Size Range for the Java heap size.

Development default: Minimum: 512 Maximum: 1536

Production default: Minimum: 1024 Maximum: 4096

build.properties entry: (Minimum) bpm.sizing.jvm.xms and (Maximum) bpm.sizing.jvm.xmx

Note: The value for Java Heap Size is a starting point. You should monitor the system under load and adjust this value if necessary. For more information, refer to TIBCO ActiveMatrix Performance Tuning and the "Tuning ActiveMatrix BPM" section in TIBCO ActiveMatrix BPM Administration.



ActiveMatrix BPM: JMS Configuration | 193

ActiveMatrix BPM: JMS Configuration


Use internal EMS Server

Whether to use the internal EMS server to handle inbound JMS requests . If this option is:

• selected, the remaining fields show the internal EMS server details. You cannot edit these values.

• cleared, the remaining fields are enabled, allowing you to enter the details of an external JMS server to use instead.

Default: Selected

Server Type The JMS server type.

Default: TIBCO EMS

JMS Url The URL of the JMS server to be used by this BPM system to handle JMS messages. (See Configure TIBCO Enterprise Message Service on page 108.)

Default: tibjmsnaming://localhost:7222

build.properties entry: bpm.userapp.jndi.jms.url

Initial Context The initial context factory to use for the JNDI lookup of the JMS server. TIBCO recommend that you do not change the default value.

Default: com.tibco.tibjms.naming.TibjmsInitialContextfactory

build.properties entry: bpm.userapp.jms.initial.context

Connection Factory

The name of the connection factory used to create the connection to the JMS server. TIBCO recommend that you do not change the default value.

Default: GenericConnectionFactory

build.properties entry: bpm.jms.connection.factory

amxbpm request queue

The name of the JMS server queue that this BPM system uses to receive messages. TIBCO recommend that you do not change the default value.

Default: queue.sample

build.properties entry: bpm.userapp.jms.request

Username: The user account to be used to connect to the JMS server.

Default: admin

build.properties entry: bpm.userapp.jms.username



Password: The password for the user account to be used to connect to the JMS server.

build.properties entry: bpm.userapp.jms.password

JMS Connection is SSL Enabled

Whether the external JMS server is enabled for SSL. When selected, the SSL Trust Store Configuration fields are enabled. (This option is not available if the internal EMS server is being used.)

Note: If this BPM system is distributed across different machines (to provide high availability and/or scalability), the Trust Store Location must be SHARED_DIR\keystores - see Shared File System.

Default: Cleared

build.properties entry: bpm.userapp.jms.enablessl

Test Connection Verifies that TIBCO Configuration Tool can connect to the JMS server using the information supplied on this page.

SSL Trust Store Configuration:

Create a Trust Store

Obtains certificates from the specified JMS server and creates a new trust store, which will be used to establish the trust relationship with the JMS 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 JMS server.

3. In the Trust Selected Certifications area, select 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 JMS 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.)

build.properties entry: bpm.userapp.jms.ssl.keystorelocation



ActiveMatrix BPM: JMS Configuration | 195

This information is used to create the following BPM runtime resource templates/instances, which this BPM system uses to communicate with the JMS server.

See "Resource Templates > Shared Resource Templates" in TIBCO ActiveMatrix BPM - SOA Administration for more information about these shared resources.

Trust Keystore Type

The type of the created or uploaded trust store: JKS or JCEKS.

Default: JKS

build.properties entry: bpm.userapp.jms.ssl.keystoretype

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.

build.properties entry: bpm.userapp.jms.ssl.keystorepassword


Type Name Description

JNDI Connection amx.bpm.userapp.jndiConnConf Provides a JNDI connection to look up the JMS server.

JMS Connection Factory Configuration

amx.bpm.userapp.jmsConnFactoryConf These two are used (with the JNDI Connection) to establish inbound communication with the JMS 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 JMS 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 this BPM system is distributed across different machines (to provide high availability and/or scalability), an external LDAP server must be used. See Additional System Requirements for a Distributed BPM System.

Note: If the internal LDAP Directory Server has already been deployed on this machine (when configuring another BPM system), you must select Use External LDAP Server instead of this option. Do not deploy a second instance of the internal LDAP Directory Server to the same machine.

Default: Selected

build.properties entry: bpm.ldap.useinternal

Port Number Port number used by the internal LDAP server.

Default: 10801

build.properties entry: bpm.ldap.internal.port

Use External LDAP Server

Whether to use an external LDAP directory server (see Configure the External LDAP Directory Server on page 116). When selected, the LDAP Provider Details fields are enabled.

Default: Cleared

build.properties entry: None. This option is automatically selected if bpm.ldap.useinternal=false.

Provider Details:

URL URL used to log in to the external LDAP server.

Default: ldap://localhost:10389

build.properties entry: bpm.ldap.url

Base DN Base Distinguished Name (DN) from which to search/navigate the LDAP directory.

Default: OU=system

build.properties entry: bpm.ldap.basedn


ActiveMatrix BPM: LDAP Configuration | 197

Username: Distinguished Name of the LDAP user who will be used as the tibco-admin user for this BPM system.

Note: This user must have (at least) read access to the LDAP directory specified by Base DN.

Default:uid=admin,ou=system

build.properties entry: bpm.ldap.username

Password: Password of the specified LDAP user.

build.properties entry: bpm.ldap.password

LDAP Server is SSL Enabled

Whether the external LDAP server is enabled for SSL. When selected, the SSL Trust Store Configuration fields are enabled.


build.properties entry: bpm.ldap.enablessl

Test Connection

Verifies that TIBCO Configuration Tool can connect to the LDAP server using the information supplied on this page.



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:


2. Specify a password to protect the keystore and click Next >. The SSL setup wizard displays the certificates imported from the external LDAP server.


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.





Either:



build.properties entry: bpm.ldap.keystorelocation

Trust Keystore Type


Default: JKS.

build.properties entry: bpm.ldap.keystoretype


Either:



build.properties entry: bpm.ldap.keystorepassword



ActiveMatrix BPM: SiteMinder Configuration | 199


This screen is only shown if you selected SiteMinder as the Authentication Type on the Authentication Configuration page.The name of the Shared Resource Instance must be amx.bpm.auth.siteminder.


Agent Name The name of the SiteMinder Wb-Agent (configured on the SiteMinder installation) that will filter authentication requests.

Client IP Address

The IP address of the machine on which the Shared Resource will be installed. This is the client that will contact the SiteMinder service.

Configuration File Options

Selected Configuration File Type

Identifies the location of the SiteMinder generated, host configuration file, from which the remaining configuration properties will be taken. Choose between:

• System Specific Default Location

If the SiteMinder installation is on the same machine as the Shared Resource installation.

• Custom File Location

If the configuration file has been copied to the same machine as the Shared Resource installation.

• Generated

If the configuration file is not available, but the properties are known. Creates a local file at a given location.

The following properties assume Generated has been selected. These values will be available from your SiteMinder installation.

Configuration File Name

The name (without path) of the file that will be generated to record the property values. You can use any name.

Trusted Host Name

A trusted host is a client that is registered with the Policy Server and is, therefore, allowed to connect to the Policy Server. A unique name that represents the host to the Policy Server.



Host Configuration Object

The name of the Host Configuration Object specified in the Policy Server. Names the object that holds parameters for a Trusted Host.

Shared Secret An automatically generated encryption key used for encrypting traffic between the trusted host and the Policy Server.

Policy Server The server IP address and port numbers for the Policy Server that the Trusted Host accesses.



ActiveMatrix BPM: Administrator Server Configuration | 201

ActiveMatrix BPM: Administrator Server Configuration


Use Existing ActiveMatrix Administrator Server

Whether to use an existing ActiveMatrix Administrator server.

When this option is 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.) Select this option if you are installing this BPM system into an existing ActiveMatrix enterprise.

When this option is cleared, you use subsequent screens in the wizard to create a new ActiveMatrix Administrator server - see Create TIBCO ActiveMatrix Administrator Server Wizard 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

build.properties entry: bpm.adminserver.bindadmin

Machine Name

Name of the machine that hosts the ActiveMatrix Administrator server for this ActiveMatrix enterprise. 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: Name of the machine on which Tibco Configuration Tool is running.

build.properties entry: bpm.adminserver.bpm.host

Port Browser port used to access the ActiveMatrix Administrator server.


Default: 8120

build.properties entry: bpm.adminserver.port

Username ID of the ActiveMatrix Administrator superuser.

Default: root

build.properties entry: bpm.adminserver.username



Password Password of the ActiveMatrix Administrator superuser.

Default: t

build.properties entry: bpm.adminserver.password

Admin server is SSL enabled

Whether the Administrator server internal port is enabled for SSL. When selected, SSL Keystore Configuration fields are displayed.


build.properties entry: bpm.adminserver.enablessl

Test Connection

Verifies that TIBCO Configuration Tool can connect to the Administrator server using the information supplied on this page.

SSL Keystore Configuration:


Obtains certificates from the specified Administrator server and creates a new trust store, which will be used to establish the trust relationship with the Administrator server:


2. Specify a password to protect the keystore and click Next >. The SSL setup wizard displays the certificates imported from the Administrator server.


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


Either:



build.properties entry: bpm.adminserver.ssl.truststore



ActiveMatrix BPM: Administrator Server Configuration | 203

Trust Keystore Type


Default: JKS.

build.properties entry: bpm.adminserver.ssl.truststoretype


Either:



build.properties entry: bpm.adminserver.ssl.truststorepassword





This screen is only displayed if you selected Use Existing ActiveMatrix Administrator Server in the ActiveMatrix BPM: SiteMinder 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 BPM system will be created.

This can be either a new host, or an existing host that is bound to the specified ActiveMatrix Administrator server.

Default: None

build.properties entry: bpm.host

Environment Name

Name of the ActiveMatrix environment in which the BPM system will be created.

This can be either a new environment, or an existing environment (that is part of the ActiveMatrix enterprise managed by the specified ActiveMatrix Administrator server).

Default: BPMEnvironment

build.properties entry: dev.envt.name

Node Name Name of the new ActiveMatrix node on which the BPM system will be created. (This node will be a BPM logical node of type BPM Node.)

Default: BPMNode

build.properties entry: dev.node.name

Node Management Port

Management port number used by the specified ActiveMatrix node. This port must not be in use by another ActiveMatrix node on the same machine.

Default: 6031

build.properties entry: dev.node.port


Administrator Server Configuration: Summary | 205


The following description applies to this screen only when it is displayed from the Create TIBCO ActiveMatrix BPM Server Wizard.

If you are using the Create TIBCO ActiveMatrix Administrator Server Wizard, please see the alternative Administrator Server Configuration: Summary description instead.




Default: 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 used by the ActiveMatrix Administrator server (as 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: This option is only displayed if you cleared Use Existing ActiveMatrix Administrator Server in the ActiveMatrix BPM: SiteMinder Configuration screen.

Default: Selected

Deploy Monitoring Service

Whether to deploy the ActiveMatrix monitoring service. TIBCO does not recommend deploying the ActiveMatrix Monitoring service on BPM production systems without first verifying its performance on a test system configured for the desired system usage and load.

Default: Cleared



Deploy Log Service Whether to deploy the ActiveMatrix logging service. TIBCO does not recommend deploying the ActiveMatrix logging service on BPM production systems without first verifying its performance on a test system configured for the desired system usage and load.

Default: Cleared

Create ActiveMatrix BPM Whether to create the BPM system.

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 BPM database, and you must manually create it instead - see Manually Creating the BPM Database for more information. You must do this before clicking Configure from this screen.

Default: Selected



| 207

Chapter 14 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 210

• Administrator Server Configuration: TIBCO Host Configuration, page 211

• Administrator Server Configuration: Connection Settings, page 213

• Administrator Server Configuration: Internal HTTP Settings, page 215

• Administrator Server Configuration: Notification and Messaging Bus Server, page 216

• Administrator Server Configuration: Database Details, page 218

• Administrator Server Configuration: Authentication Realm, page 220

• Administrator Server Configuration: Database Authentication Realm Details, page 221

• Administrator Server Configuration: LDAP Authentication Realm Details, page 223

• Administrator Server Configuration: Credential Server Details, page 228

• Administrator Server Configuration: Credential Server Keystore, page 229

• Administrator Server Configuration: Monitoring Notification Server, page 230




208 | Chapter 14 Create TIBCO ActiveMatrix Administrator Server Wizard

• Administrator Server Configuration: Monitoring Database Configuration, page 232

• Administrator Server Configuration: Log Service Database Configuration, page 234

• Administrator Server Configuration: Payload Service Database Configuration, page 236

• Administrator Server Configuration: Summary, page 238


Welcome | 209

Welcome



Whether all communication channels used by TIBCO Administrator should be secured with SSL. See Securing Communication Channels for background information.

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.

Default: Either:

• AMX BPM - if you are running the Create TIBCO ActiveMatrix BPM Server Wizard, or

• amxadmin - if you are running the Create TIBCO ActiveMatrix Administrator Server Wizard

Server Name The name of the ActiveMatrix Administrator server.

Default: Either:

• AMXBPM Server - if you are running the Create TIBCO ActiveMatrix BPM Server Wizard, or

• instanceOne - if you are running the Create TIBCO ActiveMatrix Administrator Server Wizard


Administrator Server Configuration: TIBCO Host Configuration | 211

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.

This field is only displayed if you are running the Create TIBCO ActiveMatrix BPM Server Wizard. When selected, the Environment Name, Node Name, and Node Management Port fields display.

Default: Selected

Create Development Node

Indicate whether to create a development environment and node.

This field is only displayed if you are running the Create TIBCO ActiveMatrix Administrator Server Wizard. 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: Either:

• BPM environment - if you are running the Create TIBCO ActiveMatrix BPM Server Wizard, or

• DevEnvironment - if you are running the Create TIBCO ActiveMatrix Administrator Server Wizard

Node Name Name of the node.

Default: Either:

• BPMNode - if you are running the Create TIBCO ActiveMatrix BPM Server Wizard, or

• DevNode - if you are running the Create TIBCO ActiveMatrix Administrator Server Wizard

Node Management Port

Management port used by the node.

Default: Either:

• 6031 - if you are running the Create TIBCO ActiveMatrix BPM Server Wizard, or

• 6038 - if you are running the Create TIBCO ActiveMatrix Administrator Server Wizard

Field Description


Administrator Server Configuration: Connection Settings | 213

Administrator Server Configuration: Connection Settings

Field Description

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); clients can then 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

Port on which Administrator clients access the ActiveMatrix Administrator server.

Default: 8120

Browser Idle Session Timeout(m)

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

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 When selected it uses the self signed certificate from the samples folder.

Do not use a self-signed certificate in production environments.

Default: Selected.


Indicate that ActiveMatrix Administrator server will identify itself to clients with a certificate imported into ActiveMatrix Administrator server. When selected, the Keystore fields and Fetch Keystore button are enabled.



Keystore Location

The location of the keystore to import.

Keystore Type The type of the uploaded keystore.

Default: Autodetect (The actual keystore type is displayed when you click Fetch Keystore.)

Keystore Password

The password that protects the keystore.

Fetch Keystore Retrieves the aliases from the specified keystore. The Key Alias field, Key Password field and Verify keystore button are displayed.

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

Key Password The password that protects the specified Key Alias.

Verify Keystore

Verifies that TIBCO Configuration Tool can retrieve the specified keystore alias using the information supplied on this page.

Field Description


Administrator Server Configuration: Internal HTTP Settings | 215

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 is secured with SSL.

Default: Cleared



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: tcp://machinename:7222, where machinename is the machine on which TIBCO Configuration Tool is being executed.

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.

Note: The TIBCO Enterprise Message Service server usually listens on port 7243 when SSL-enabled. You must update the port value(s) in the Machine Name Port List field before proceeding with SSL configuration.

Test Connection

Verifies that TIBCO Configuration Tool can connect to the server using the information supplied on this page.


Administrator Server Configuration: Notification and Messaging Bus Server | 217

SSL KeyStore Configuration:


Invokes a wizard to obtain certificates from the specified server and create the trust store:


2. Specify a password to protect the keystore and click Next. The SSL setup wizard displays the certificates imported from the server.

3. In the Trust Selected Certifications area, select 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 server.

Keystore Location

Either:


• the location of the trust store to be uploaded to ActiveMatrix Administrator. (You can either type this directly or use Browse to find it.)

Keystore Type The type of the created or uploaded trust store: JKS or JCEKS.

Default: JKS

Keystore Password

Either:








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.

Note: Use the embedded in-process database only during development.

Default: Either:

• Cleared - if you are running the Create TIBCO ActiveMatrix BPM Server Wizard, or

• Selected - if you are running the Create TIBCO ActiveMatrix Administrator Server Wizard

Database Driver

The driver for the external database.

Default: TIBCO provided JDBC driver for HSQLDB 1.8.400

Database URL The URL of the external database.

Note: For a Microsoft SQL Server database, you must use the following format for the URL: jdbc:sqlserver://host:port;DatabaseName=dbNname.

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



Administrator Server Configuration: Database Details | 219








Trust Keystore Location

Either:



Trust Keystore Type


Default: JKS

Trust Keystore Password

Either:






Administrator Server Configuration: Authentication Realm

Field Description

Authentication Realm

Realm Type The type of the authentication realm:

• Database - the Administrator Server Configuration: Database Authentication Realm Details screen displays.

• LDAP - the Administrator Server Configuration: LDAP Authentication Realm Details screens display.

Superuser Credentials (This section is only displayed if the LDAP Realm Type is selected.)

Username The ID of the initial superuser.

Default: root

Password The password of the superuser.

Default: t


Administrator Server Configuration: Database Authentication Realm Details | 221

Administrator Server Configuration: Database Authentication Realm Details

This screen is only displayed if you selected Database as the Realm Type on the Administrator Server Configuration: Authentication Realm screen.

Field Description

Use ActiveMatrix Administrator Server 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 display.

Database Driver






Default: sa


Default: None

Max Connections


Default: 10



Test Connection












Either:



Trust Keystore Type


Default: JKS


Either:



Field Description


Administrator Server Configuration: LDAP Authentication Realm Details | 223

Administrator Server Configuration: LDAP Authentication Realm Details

This screen is only displayed if you selected LDAP as the Realm Type on the Administrator Server Configuration: Authentication Realm screen.

Field Description


Comma-separated list of URLs for an LDAP server. To achieve fault tolerance, you can specify multiple URLs. For example:

ldap://server1.example.com:686,ldap://server2.example.com:1686

Default: machineName:389

Fetch DN Retrieves the base DN of the LDAP server.

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

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

User Attribute with User Name

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

Default: uid



Administrator Server Configuration: LDAP Authentication Realm Details (Screen 2)

Search Timeout (ms)

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

Default: 30000

Follow Referrals

Whether to follow LDAP referrals. When selected, requests to LDAP can be redirected to another server.

Select this field to indicate that the LDAP information might be available at another location, or possibly at another server or servers.

Note: Ask your LDAP administrator whether LDAP referrals are used in your domain.

Default: Cleared

Field Description

Field Description

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

Options:

• Group has users — List of users that belong to the group. When selected, the Group Attribute with User Names field is enabled.

• User has groups — List of groups to which the user belongs. When selected, the User Attribute with Group Names field is enabled.

Default: Group has users

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: cn={0}




Group Attribute with User Names

Name of the attribute in the group object containing its users.

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

Default: uniqueMember

Group Attribute with Group Name

Name of the attribute in the group object that contains the name of the group.

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

Default: cn

Group Attribute with Subgroup Names

Name of the attribute in the group object that contains its subgroups.


Default: uniqueMember

User Attribute with Group Names

Name of the attribute in the user object that lists the groups to which the user belongs.

Default: None

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: Selected

Field Description

Field Description

LDAP Realm

User Search Scope Subtree

Whether to search the entire subtree starting at the base DN, or search only the nodes one level below the base DN.

Default: Selected



Security Authentication

Value of Simple Authentication and Security Layer (SASL) authentication protocol to use. Values are implementation-dependent. Some possible values are:

• Simple - Username and password are required.

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

• md-5

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.

Test Connection










Either:



Trust Keystore Type


Default: JKS

Field Description




Either:



Field Description




Field Description

Network Adapter Address of the network adapter on the machine on which TIBCO Credential Server runs. The default is set to 0.0.0.0 so that TIBCO Credential Server will listen on all network adapters (including http://localhost and http://hostname). With the default setting, clients can connect to TIBCO 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 Management port number of the node, SystemNode, that runs TIBCO Credential Server.

Default: 6041

Username User identifier for TIBCO Credential Server clients.

Default: user1

Password Password for the client.


Administrator Server Configuration: Credential Server Keystore | 229

Administrator Server Configuration: Credential Server Keystore

Field Description

Auto-generated Keystore

Indicate that the TIBCO Credential Server keystore will be generated. When selected, Common Name is enabled.

Default: Selected

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

Keystore Location




Keystore Password



Key Alias The key alias that identifies the required entry in the keystore.


Verify Keystore Verifies that TIBCO Configuration Tool can retrieve the specified keystore alias using the information supplied on this page.



Administrator Server Configuration: Monitoring Notification Server

Field Description

Use ActiveMatrix Administrator Notification and Messaging Bus Server

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

Default: Selected. If cleared, the notification server configuration fields are enabled.

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

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


Default: admin


Default: None



Note: The TIBCO Enterprise Message Service server usually listens on port 7243 when SSL-enabled and you must update the Machine Name Port List value before proceeding with SSL configuration.

Test Connection



Administrator Server Configuration: Monitoring Notification Server | 231








Keystore Location

Either:




Default: JKS

Keystore Password

Either:



Field Description



Administrator Server Configuration: Monitoring Database Configuration

Field Description


Indicate that the monitoring service should use the same database as the ActiveMatrix Administrator server.

Default: Selected.

Database Driver The driver for the external database.





Default: sa


Default: None

Max Connections The maximum number of database connections to allocate.

Default: 30



Test Connection Verifies that TIBCO Configuration Tool can connect to the server using the information supplied on this page.


Administrator Server Configuration: Monitoring Database Configuration | 233


Create a Trust Store Invokes a wizard to obtain certificates from the specified server and create the trust store:





Keystore Location Either:




Default: JKS

Keystore Password Either:



Field Description



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






Default: sa


Default: None


Default: 10

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: Log Service Database Configuration | 235












Default: JKS

Keystore Password

Either:



Field Description



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






Default: sa


Default: None


Default: 10


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

Default: Cleared



Administrator Server Configuration: Payload Service Database Configuration | 237












Default: JKS

Keystore Password

Either:



Field Description




The following description applies to this screen only when it is displayed from the Create TIBCO ActiveMatrix Administrator Server Wizard.

If you are using the Create TIBCO ActiveMatrix BPM Server Wizard, please see the alternative Administrator Server Configuration: Summary description instead.




Default: CONFIG_HOME\tct\admin\timestamp



where:


• port is the External HTTP Port number specified in the Administrator Server Configuration: Connection Settings screen.


Create TIBCO ActiveMatrix Administrator server

Whether to create the ActiveMatrix Administrator server.

Default: Selected

Deploy Monitoring Service

Whether to deploy the ActiveMatrix monitoring service. TIBCO does not recommend deploying the ActiveMatrix Monitoring service on BPM production systems without first verifying its performance on a test system configured for the desired system usage and load.

Default: Selected



Deploy Log Service Whether to deploy the ActiveMatrix logging service. TIBCO does not recommend deploying the ActiveMatrix logging service on BPM production systems without first verifying its performance on a test system configured for the desired system usage and load.

Default: Selected

Select the products to deploy:

TIBCO ActiveMatrix Mediation IT

Default: Selected



| 241

Chapter 15 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 243

• TIBCO Host instance Configuration: Notification Server, page 244

• TIBCO Host instance Configuration: Administrator Server, page 246

• TIBCO Host instance Configuration: Summary, page 248

If you use this wizard (version 3.3) to create a TIBCO Host instance, you cannot manage the instance using a pre-3.3 version of the ActiveMatrix Administrator server.


242 | Chapter 15 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 | 243

TIBCO Host instance Configuration: Details

Field Description

Name Name of the TIBCO Host instance. The name must be unique within the enterprise.

Default: None

Enterprise Name

Name that defines a communication group for status messages sent between ActiveMatrix Administrator server and the hosts that are bound to the server.

Default: amxadmin

Machine Name

Name of the machine on which the TIBCO Host instance runs.


Management Port

Management port of the TIBCO Host instance.

Default: 6001


Whether the TIBCO Host instance should be registered as a Windows service named TIBCO ActiveMatrix instanceName, where instanceName is the Name you specified, with startup type Automatic. The service is not started.

Default: Cleared


Whether to create a shortcut named instanceName on the Windows desktop that points to CONFIG_HOME\tibcohost\instanceName\host\bin\tibcohost.exe and launches the TIBCO Host instance.

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: machinename:7222, where machinename is the machine on which TIBCO Configuration Tool is being executed.


Default: admin


Default: None



Note: The TIBCO Enterprise Message Service server usually listens on port 7243 when SSL-enabled and you must update the Machine Name Port List value before proceeding with SSL configuration.

Test Connection










TIBCO Host instance Configuration: Notification Server | 245

Keystore Location

Either:




Default: JKS

Keystore Password

Either:



Field Description




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.

Default: None

Port The browser port used to access the Administrator server.

Default: 8120


Default: root


Default: t

Assign this Host to All Environments

Whether the host is assigned to all environments. When cleared, the host is assigned to no environment initially. You can use ActiveMatrix Administrator to explicitly assign the host to selected environments after configuration is complete.

Default: Selected

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.


TIBCO Host instance Configuration: Administrator Server | 247


Create a Trust Store Invokes a wizard to obtain certificates from the specified server and create the trust store:





Trust Keystore Location Either:



Trust Keystore Type The type of the created or uploaded trust store: JKS or JCEKS.

Default: JKS

Trust Keystore Password Either:



Field Description



TIBCO Host instance Configuration: Summary




Default: CONFIG_HOME\tct\tibcohost\timestamp


Create TIBCO Host instance

Whether to create a new TIBCO Host instance.

Default: Selected

Launch TIBCO Host instance

Whether to launch the new TIBCO Host instance.

Default: Selected

Register TIBCO Host instance to the Administrator server

Whether to bind the new TIBCO Host instance to the specified ActiveMatrix Administrator server.

Default: Selected


| 249

Chapter 16 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


• ActiveMatrix BPM Node Type: Administrator Server Configuration, page 251

• ActiveMatrix BPM Node Type: Host and Node Configuration, page 253

• ActiveMatrix BPM Node Type: Sizing Configuration, page 255

• ActiveMatrix BPM Node Type: Summary, page 256

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.

Do not use this wizard if any of the child user applications that have been deployed to the product application are in a “Failed” state. See "Failures Creating a New BPM Node with TCT" in TIBCO ActiveMatrix BPM Troubleshooting for more information.


250 | Chapter 16 Configure TIBCO ActiveMatrix BPM Server Node Type Wizard

Welcome





Default: Cleared


ActiveMatrix BPM Node Type: Administrator Server Configuration | 251

ActiveMatrix BPM Node Type: Administrator Server Configuration

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.

build.properties entry: bpm.nodetype.admin.host



Default: 8120

build.properties entry: bpm.nodetype.admin.portnumber

Username ID of the ActiveMatrix Administrator superuser.

Default: root

build.properties entry: bpm.nodetype.admin.username

Password Password of the ActiveMatrix Administrator superuser.

Default: t

build.properties entry: bpm.nodetype.admin.password


Whether the Administrator server internal port is enabled for SSL. When selected, the SSL Keystore Configuration fields are enabled.


build.properties entry: bpm.nodetype.adminserver.enablessl

Test Connection Verifies that TIBCO Configuration Tool can connect to the Administrator server using the information supplied on this page.




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:


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.


Either:



build.properties entry: bpm.nodetype.javax.net.ssl.trustStore

Trust Keystore Type


Default: JKS

build.properties entry: bpm.nodetype.javax.net.ssl.trustStoreType


Either:



build.properties entry: bpm.nodetype.javax.net.ssl.trustStorePassword


ActiveMatrix BPM Node Type: Host and Node Configuration | 253

ActiveMatrix BPM Node Type: Host and Node Configuration


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

build.properties entry: bpm.nodetype.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

build.properties entry: bpm.nodetype.node

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

build.properties entry: bpm.nodetype.node.port

Host Name of an existing host on which this BPM node will run.

Default: BPMHost

build.properties entry: bpm.nodetype.host



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

build.properties entry: bpm.nodetype.http.connector.port

Environment Name

Name of an existing environment in which this BPM node will run.


build.properties entry: bpm.nodetype.environment

Application Name

Name of the BPM application that identifies this BPM system.


build.properties entry: bpm.nodetype.app.name

Override BPM Configuration Folder

Whether to override the default location of the BPM configuration folder. Select this option if this BPM system is distributed across different machines (to provide high availability and/or scalability).

If selected, the Configuration Folder field is displayed.

Default: Cleared

build.properties entry: bpm.nodetype.home.root.override


Location of the BPM configuration folder.

If this BPM system is distributed across 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.


build.properties entry: bpm.nodetype.home.root



ActiveMatrix BPM Node Type: Sizing Configuration | 255

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

build.properties entry: bpm.nodetype.install.size

Max Java PermGen Size

Maximum size for Java PermGen.

Default:

• Development - 256

• Production - 1024

build.properties entry: bpm.nodetype.jvm.maxpermsize

Ranged Parameters:

Java Heap Size Range for the Java heap size.

Default:

• Development - Minimum: 512 Maximum: 1536

• Production - Minimum: 1024 Maximum: 4096

build.properties entries: (Minimum) bpm.nodetype.jvm.xms and (Maximum) bpm.nodetype.jvm.xmx



ActiveMatrix BPM Node Type: Summary




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


Replicate TIBCO ActiveMatrix Administrator Server Wizard | 257

Chapter 17 Replicate TIBCO ActiveMatrix Administrator Server Wizard

This chapter provides reference information about the TIBCO Configuration Tool replicate TIBCO ActiveMatrix Administrator Server wizard.

Topics

• Welcome

• Remote Administrator Server Details

• Create Replicated Instance Wizard

• Administrator Server Configuration Details

• Administrator Server TIBCO Host Configuration

• Administrator Server Connection Settings

• Administrator Server Notification and Messaging Bus Server

• Administration Server Database Details

• Administrator Server Database Authentication Realm Details

• Administrator Server Configuration LDAP Authentication Realm

• Administrator Server Configuration Summary




258 | Chapter 17 Replicate TIBCO ActiveMatrix Administrator Server Wizard

Welcome

The Welcome screen lists the information you will need to complete this wizard and the replication requirements that must be in place for you to proceed. These requirements are:

• The TIBCO_HOME location on this machine (the second primary machine) must be the same as on the machine that is running the existing ActiveMatrix Administrator (the primary machine).

• The primary ActiveMatrix Administrator server must use an external database. (See Create the External ActiveMatrix Administrator Database.)

• The staging folder used by the primary ActiveMatrix Administrator server must be on a shared network location. (See Shared File System.)

• The staging folder must be accessible from this machine at the same location used on the primary machine. For example, if you create a network drive or folder on machine 1 and map it to x:\shared , the shared drive or folder must be mapped to x:\shared as well.


Remote Administrator Server Details | 259

Remote Administrator Server Details

Field Description

Machine Name Name of the machine on which the primary Administrator server runs. The value of this property must a hostname resolvable through DNS or an IP address.

Default: None

Port Management port that the primary Administrator server is using.

Default: 8120

Username User name of the administrator of the primary Administrator server.

Default: root

Password The password of the administrator of the primary Administrator server.

Administrator server is SSL enabled

Whether the primary Administrator server is enabled for SSL. When selected, SSL Keystore Configuration fields are displayed.

Test Connection Verifies that TIBCO Configuration Tool can connect to the primary Administrator server using the information supplied on this page.











Either:



Trust Keystore Type


Default: JKS


Either:



Field Description


Create Replicated Instance Wizard | 261

Create Replicated Instance Wizard

The Create Replicated Instance Wizard screen validates your system setup against the replication requirements given in the Welcome screen.

If the system setup meets the replication requirements the following message is displayed:

Retrieve admin config properties successfully, all values are

valid.

If there are problems a suitable error message is displayed, indicating what the problem is.



Administrator Server Configuration Details

Field Description

Enterprise Name The enterprise name of the primary Administrator server. You cannot change this value as both the primary and replica Administrator servers must be in the same enterprise.

Host Name Name of the SystemHost instance that will be associated with the replica Administrator server. The host name must be unique. You cannot use the name you used for the host associated with the primary Administrator server.

Default: SystemHostReplica

Node Name Name of the SystemNode instance that will be associated with the replica Administrator server. The node name must be unique. You cannot use the name you used for the node associated with the primary Administrator server.

Default: SystemNodeReplica


Administrator Server TIBCO Host Configuration | 263

Administrator Server TIBCO Host Configuration

Field Description

Machine Name Name of the machine on which the TIBCO Host instance (for the replica Administrator server) 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.


Port Management port that the TIBCO Host instance will use to communicate with other services in the environment.

Default: 6051


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


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



Administrator Server Connection Settings

Field Description

Network Adapter

Address of the network adapter on the machine on which the Administrator server runs. The default is set to 0.0.0.0 so that Administrator will listen on all network adapters (including http://localhost and http://hostname). If you leave the default, clients can connect to the 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.

Management Port

Management port of the node that runs Administrator server.

Default: 6021.

External HTTP Port

Port on which Administrator clients access the ActiveMatrix Administrator server.

Default: 8120.



Default: Same as for the primary Administrator server.


Indicate that ActiveMatrix Administrator server will identify itself to clients with a self-signed certificate When selected it uses the self signed certificate from the samples folder.

Do not use a self-signed certificate in production environments.

Default: Same as for the primary Administrator server.



Keystore Location





Administrator Server Connection Settings | 265

Keystore Password





Verify Keystore Verifies that TIBCO Configuration Tool can retrieve the specified keystore alias using the information supplied on this page.

Field Description



Administrator Server Notification and Messaging Bus Server

This screen displays the same TIBCO Enterprise Message Service server details that are used by the primary Administrator server. With the exception of the Password field, you cannot edit the configuration.

Click Test Connection to verify that TIBCO Configuration Tool can connect to the server using the information supplied on this page.


Administration Server Database Details | 267

Administration Server Database Details

This screen displays the same database details that are used by the primary Administrator server. You cannot edit the configuration.

1. Enter the Password for the Administrator server database.

2. Click Test Connection to verify that TIBCO Configuration Tool can connect to the server using the information supplied on this page.



Administrator Server Database Authentication Realm Details

This screen displays the same database details that are used by the primary Administrator server. You cannot edit the configuration.

Enter the external database password then click Test Connection to verify that TIBCO Configuration Tool can connect to the server using the information supplied on this page.

This screen is only displayed if you selected Database as the Realm Type on the Administrator Server Configuration: Authentication Realm screen when configuring the primary Administrator server.


Administrator Server Configuration LDAP Authentication Realm | 269

Administrator Server Configuration LDAP Authentication Realm

This screen displays the same LDAP configuration details that are used by the primary Administrator server. You cannot edit the configuration.

Click Test Connection to verify that TIBCO Configuration Tool can connect to the server using the information supplied on this page.

This screen is only displayed if you selected LDAP as the Realm Type on the Administrator Server Configuration: Authentication Realm screen when configuring the primary Administrator server.



Administrator Server Configuration Summary

The Replicate TIBCO ActiveMatrix Administrator Server wizard does not show the configuration details for Monitoring, Logging and Payload services. If those services are configured and deployed on the primary ActiveMatrix Administrator server, they are automatically deployed on the replica server as part of the replication process.




Default: CONFIG_HOME\tct\admin.replicate\timestamp



where:




Replicate TIBCO ActiveMatrix Administrator server

Whether to replicate the primary ActiveMatrix Administrator server.

Default: Selected

if you subsequently wish to delete a replica ActiveMatrix Administrator server, see Deleting a Replica ActiveMatrix Administrator Server.


| 271

Chapter 18 Edit TIBCO ActiveMatrix BPM Instance Wizard

This chapter provides reference information about the TIBCO Configuration Tool Edit TIBCO ActiveMatrix BPM Instance wizard.

Topics

• TIBCO ActiveMatrix BPM Server Edit Wizard, page 272

• ActiveMatrix BPM Edit: Administrator Server Configuration, page 273

• ActiveMatrix BPM: SOAP Version Configuration, page 275

• ActiveMatrix BPM: Authentication Configuration, page 276


• ActiveMatrix BPM Edit: Summary, page 279


272 | Chapter 18 Edit TIBCO ActiveMatrix BPM Instance Wizard

TIBCO ActiveMatrix BPM Server Edit Wizard


AMX-BPM Environment Name

Name of the ActiveMatrix environment that hosts the BPM system to be edited.


build.properties entry: bpm.edit.environment

AMX-BPM Application Name

Name of the BPM application that identifies the BPM system to be edited.


build.properties entry: bpm.edit.app.name

Edit Action to be Performed

The type of edit you want to perform. Select one of the following:

• Edit SOAP Version

• Edit Authentication Configuration

If you want to perform multiple edit actions, you must run this wizard multiple times.

Default: Edit SOAP Version

build.properties entries: bpm.edit.action, bpm.edit.target


ActiveMatrix BPM Edit: Administrator Server Configuration | 273

ActiveMatrix BPM Edit: Administrator Server Configuration


Machine Name Name of the machine that hosts the ActiveMatrix Administrator server (that manages the BPM system being edited).


build.properties entry: bpm.edit.admin.host and bpm.edit.admin.url


Default: 8120

build.properties entry: bpm.edit.admin.portnumber and bpm.edit.admin.url

Username ID of the ActiveMatrix Administrator server superuser.

Default: root

build.properties entry: bpm.edit.admin.username

Password Password of the ActiveMatrix Administrator server superuser.

Default: t

build.properties entry: bpm.edit.admin.password


Whether the port used to access the ActiveMatrix Administrator server is enabled for SSL. When selected, the SSL Keystore Configuration fields are enabled.

Default: Follows the value selected for Configure to Secure All Communication with SSL on the Welcome screen.

build.properties entry: bpm.edit.adminserver.enablessl

Test Connection Verifies that TIBCO Configuration Tool can connect to the ActiveMatrix Administrator server using the information supplied on this page.




Create a Trust Store Obtains certificates from the specified ActiveMatrix Administrator server and creates a new trust store, which will be used to establish the trust relationship with the ActiveMatrix Administrator server:


2. Specify a password to protect the keystore and click Next >. The SSL setup wizard displays the certificates imported from the ActiveMatrix Administrator server.


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 ActiveMatrix Administrator server.


Either:



build.properties entry: bpm.edit.javax.net.ssl.trustStore

Trust Keystore Type


Default: JKS

build.properties entry: bpm.edit.javax.net.ssl.trustStoreType


Either:



build.properties entry: bpm.edit.javax.net.ssl.trustStorePassword



ActiveMatrix BPM: SOAP Version Configuration | 275

ActiveMatrix BPM: SOAP Version Configuration

This screen is only displayed if you chose Edit SOAP Version as the Edit Action to be Performed on the TIBCO ActiveMatrix BPM Server Edit Wizard screeen.


SOAP Binding Version

Version of the SOAP specification that will be applied to all SOAP bindings on services exposed by this BPM system. (These are the services provided by the ActiveMatrix BPM public API - see the TIBCO ActiveMatrix BPM Developer’s Guide.

SOAP versions 1.1 and 1.2 are supported.

Note: If you change the SOAP version used by the BPM system the following applications will no longer work, and must be modified to use the new SOAP version:

• any custom client application that uses the existing SOAP version of the BPM public web service API.

• any custom client application that uses the Java Service Connector API.

Default: 1.1

build.properties entry: bpm.edit.soap.version

Also update SOAP binding Version for child user applications?

Whether to update process applications that are already deployed to this BPM system to use the same SOAP Binding Version specified above.

If you clear this option, the following applications will no longer work:

• any deployed process application that calls a BPM system service.

• any deployed process application that calls another BPM system-hosted process application using a SOAP binding. For example, where an application needs to enforce a security policy to call the internal service.

Note: If you select this option you will also need to update the application project in TIBCO Business Studio to use the new SOAP version before upgrading any of the affected process applications.

Default: Selected

build.properties entry: bpm.edit.handledependencies



ActiveMatrix BPM: Authentication Configuration

This screen is only displayed if you chose Edit Authentication Configuration as the Edit Action to be Performed on the TIBCO ActiveMatrix BPM Server Edit Wizard screeen.


Select Authentication Type

LDAP or SiteMinder

The SiteMinder option is only provided if you set up SiteMinder device driver installation (see Configure Third-Party Driver Wizard) and Shared Resource installation for SiteMiinder (see Create TIBCO ActiveMatrix BPM Server Wizard).

Default: LDAP

build.properties entry: bpm.edit.auth.authtype

Allow also basic username authentication? Default: Selected

build.properties entry: bpm.edit.auth.allowUsername


ActiveMatrix BPM: SiteMinder Configuration | 277



Agent Name The name of the SiteMinder Wb-Agent (configured on the SiteMinder installation) that will filter authentication requests.

Client IP Address

The IP address of the machine on which the Shared Resource will be installed. This is the client that will contact the SiteMinder service.

Configuration File Options

Selected Configuration File Type

Identifies the location of the SiteMinder generated, host configuration file, from which the remaining configuration properties will be taken. Choose between:

• System Specific Default Location

If the SiteMinder installation is on the same machine as the Shared Resource installation.

• Custom File Location

If the configuration file has been copied to the same machine as the Shared Resource installation.

• Generated

If the configuration file is not available, but the properties are known. Creates a local file at a given location.

The following properties assume Generated has been selected. These values will be available from your SiteMinder installation.

Configuration File Name

The name (without path) of the file that will be generated to record the property values. You can use any name.

Trusted Host Name

A trusted host is a client that is registered with the Policy Server and is, therefore, allowed to connect to the Policy Server. A unique name that represents the host to the Policy Server.

Host Configuration Object

The name of the Host Configuration Object specified in the Policy Server. Names the object that holds parameters for a Trusted Host.



Shared Secret An automatically generated encryption key used for encrypting traffic between the trusted host and the Policy Server.

Policy Server The server IP address and port numbers for the Policy Server that the Trusted Host accesses.



ActiveMatrix BPM Edit: Summary | 279

ActiveMatrix BPM Edit: Summary




Default: CONFIG_HOME\tct\bpmedit\timestamp

Click Configure to execute the following upgrade actions:

Setting AMX-BPM SOAP Version to n.n

Whether to configure the specified BPM system to use SOAP version n.n.

Default: Selected

Setting AMX-BPM Authentication Type to typeAsp

Type is either Ldap or SiteMinder.


| 281

Chapter 19 Upgrade TIBCO ActiveMatrix BPM Instance Wizard

This chapter provides reference information about the TIBCO Configuration Tool Upgrade TIBCO ActiveMatrix BPM Instance wizard.

Topics


• ActiveMatrix BPM Upgrade: Administrator Server Configuration, page 283

• ActiveMatrix BPM Upgrade: Upgrade Configuration, page 285

• ActiveMatrix BPM Upgrade: Summary, page 287


282 | Chapter 19 Upgrade TIBCO ActiveMatrix BPM Instance Wizard

Welcome





Default: Cleared


ActiveMatrix BPM Upgrade: Administrator Server Configuration | 283



Machine Name Name of the machine that hosts the ActiveMatrix Administrator server (that manages the BPM system being upgraded).


build.properties entry: bpm.upgrade.admin.host and bpm.upgrade.admin.url


Default: 8120

build.properties entry: bpm.upgrade.admin.portnumber and bpm.upgrade.admin.url


Default: root

build.properties entry: bpm.upgrade.admin.username


Default: t

build.properties entry: bpm.upgrade.admin.password




build.properties entry: bpm.upgrade.adminserver.enablessl











Either:



build.properties entry: bpm.upgrade.javax.net.ssl.trustStore

Trust Keystore Type


Default: JKS

build.properties entry: bpm.upgrade.javax.net.ssl.trustStoreType


Either:



build.properties entry: bpm.upgrade.javax.net.ssl.trustStorePassword



ActiveMatrix BPM Upgrade: Upgrade Configuration | 285



ActiveMatrix Platform Upgrade Details:

TIBCO Host Instance

Name of the TIBCO Host instance (on the local machine) that hosts the BPM node to be upgraded.

A TIBCO Host instance that hosts an ActiveMatrix Administrator server (original or replicated) is identified by the string Admin-ActiveMatrixEnterpriseName-ActiveMatrixServerName.

Other TIBCO Host instances are identified by their host name - for example, ProductionHost.

Note: These names are the folder names of the TIBCO Host instances on the local machine, under CONFIG_HOME\tibcohost.

Default: Admin-ActiveMatrixEnterpriseName-ActiveMatrixServerName

build.properties entry: bpm.upgrade.host.instancename

ActiveMatrix BPM Upgrade Details:

Note: This section is only displayed when you are running this wizard on a machine that hosts an ActiveMatrix Administrator server (that is, a primary or second primary machine).

build.properties entry: bpm.upgrade.host.only - must be true on a machine that hosts an ActiveMatrix Administrator server, and false otherwise.

Application Name

Name of the BPM application that identifies the BPM system to be upgraded.


build.properties entry: bpm.upgrade.app.name

Environment Name

Name of the ActiveMatrix environment that hosts the BPM system to be upgraded.


build.properties entry: bpm.upgrade.environment



Automatically upgrade BPM Database Schema

Whether TIBCO Configuration Tool should automatically upgrade the ActiveMatrix BPM database. Note: TIBCO strongly recommend that you select this option.

See Manually Upgrading the BPM Database for more information about how to decide if you need to manually upgrade the database.

Clearing this field enables Generate Scripts.

Default: Selected

build.properties entry: bpm.upgrade.schema

Generate Scripts

Generates the SQL scripts needed to manually upgrade the ActiveMatrix BPM database. See Manually Running BPM Database Creation or Upgrade Scripts for more information about how to use these scripts.

ActiveMatrix BPM Shared Configuration Folder:


The location of the BPM configuration folder.

If this BPM system is distributed across 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.


build.properties entry: bpm.config.home.root and bpm.config.home.perapp.root



ActiveMatrix BPM Upgrade: Summary | 287

ActiveMatrix BPM Upgrade: Summary




Default: CONFIG_HOME\tct\bpmupgrade\timestamp


Upgrade ActiveMatrix TIBCO Host Instance

Whether to upgrade the specified ActiveMatrix Host instance.

Note: Other ActiveMatrix host instances will not be affected.

Default: Cleared

Upgrade ActiveMatrix Administrator

Whether to upgrade the ActiveMatrix Administrator server.

Default: Cleared

Upgrade Nodes Hosting ActiveMatrix BPM Instance

Whether to upgrade every ActiveMatrix node on which the specified BPM application is distributed to the version of the ActiveMatrix platform software installed earlier.

Note: Other ActiveMatrix nodes will not be affected.

Default: Selected

Upgrade ActiveMatrix BPM Instance Application

Whether to upgrade the specified BPM application to the ActiveMatrix BPM version installed earlier.

Note: Other BPM applications (systems) will not be affected.

The message [Not Upgrading Database] is displayed if you chose not to upgrade the ActiveMatrix BPM database in the ActiveMatrix BPM Upgrade: Upgrade Configuration screen (by clearing Automatically upgrade BPM Database Schema).

In this case, TIBCO Configuration Tool will not automatically upgrade the ActiveMatrix BPM database, and you must manually upgrade it instead - see Manually Upgrading the BPM Database for more information.

Default: Selected


| 289

Chapter 20 Delete TIBCO ActiveMatrix BPM Instance Wizard

This chapter provides reference information about the TIBCO Configuration Tool Delete TIBCO ActiveMatrix BPM Instance wizard.

Topics

• Using the Delete TIBCO ActiveMatrix BPM Instance Wizard, page 290


• ActiveMatrix BPM Deletion: Administrator Server Configuration, page 292

• ActiveMatrix BPM Deletion: Instance Configuration, page 294

• ActiveMatrix BPM Deletion: Summary, page 295




290 | Chapter 20 Delete TIBCO ActiveMatrix BPM Instance Wizard

Using the Delete TIBCO ActiveMatrix BPM Instance Wizard

The Delete TIBCO ActiveMatrix BPM Instance wizard will remove a specific instance of the BPM application and its shared resources.

The wizard does not remove any of the following, as they may be in use by other applications:

• any shared system applications (such as LDAP server applications)

• the nodes on which the BPM application instance was deployed.

• the environment containing the BPM application instance.

• the database used by the BPM application instance.

If you want to remove any of these entities, you should do so separately, after you have run the wizard.

Before you run the Delete TIBCO ActiveMatrix BPM Instance wizard:

• you must undeploy any user applications that are running against this BPM application instance.

• you must delete user applications before deleting a BPM application instance.

The wizard checks for application dependencies before deleting the specified BPM application instance. If the wizard detects any dependent applications other than the system organization model application (for example, amx.bpm.app.sysorgmodel), it exits with a failure message, having made no changes to the system.


Welcome | 291

Welcome





Default: Cleared



ActiveMatrix BPM Deletion: Administrator Server Configuration


Machine Name Name of the machine that hosts the ActiveMatrix Administrator server (that manages the BPM system being deleted).


build.properties entry: bpm.delete.admin.host and bpm.delete.admin.url


Default: 8120

build.properties entry: bpm.delete.admin.portnumber and bpm.delete.admin.url


Default: root

build.properties entry: bpm.delete.admin.username


Default: t

build.properties entry: bpm.delete.admin.password




build.properties entry: bpm.delete.adminserver.enablessl



ActiveMatrix BPM Deletion: Administrator Server Configuration | 293








Either:



build.properties entry: bpm.delete.javax.net.ssl.trustStore

Trust Keystore Type


Default: JKS

build.properties entry: bpm.delete.javax.net.ssl.trustStoreType


Either:



build.properties entry: bpm.delete.javax.net.ssl.trustStorePassword




ActiveMatrix BPM Deletion: Instance Configuration


ActiveMatrix BPM Deletion Details:

Application Name

Name of the BPM application that identifies the BPM system to be deleted.


build.properties entry: bpm.delete.app.name

Environment Name

Name of the ActiveMatrix environment that hosts the BPM system to be deleted.


build.properties entry: bpm.delete.environment


ActiveMatrix BPM Deletion: Summary | 295

ActiveMatrix BPM Deletion: Summary




Default: CONFIG_HOME\tct\bpmdelete\timestamp


Delete ActiveMatrix BPM Instance

Whether to delete the specified BPM system.

Default: Selected

Make sure that you have undeployed any user applications that are running against this BPM application instance before you click Configure.

The wizard checks for application dependencies before deleting the specified BPM application instance. If the wizard detects any dependent applications other than the system organization model application (for example, amx.bpm.app.sysorgmodel), it exits with a failure message, having made no changes to the system.

Deleting the BPM system removes the specified instance of the BPM application and its shared resources. It does not remove any of the following, as they may be in use by other applications:

• any shared system applications (such as LDAP server applications)

• the nodes on which the BPM application instance was deployed.

• the environment containing the BPM application instance.

• the database used by the BPM application instance.

If you want to remove any of these entities, you should do so separately.


Edit TIBCO ActiveMatrix Administrator Server Configuration Wizard | 297

Chapter 21 Edit TIBCO ActiveMatrix Administrator Server Configuration Wizard

This chapter provides reference information about the TIBCO Configuration Tool Edit TIBCO ActiveMatrix Administrator Server wizard.

Topics

• Edit ActiveMatrix Administrator Server Configuration: Administrator Server Selection, page 298

• Edit ActiveMatrix Administrator Server Configuration, page 299

• Administrator Server Configuration: Edit HTTP Connection Settings, page 300

• Administrator Server Configuration: Edit Database Settings, page 302

• Administrator Server Configuration: Edit Authentication Realm Settings, page 303

• Administrator Server Configuration: Edit Database Authentication Realm Details, page 304

• Administrator Server Configuration: Edit LDAP Authentication Realm Details, page 305

• Administrator Server Configuration: Summary, page 309




298 | Chapter 21 Edit TIBCO ActiveMatrix Administrator Server Configuration Wizard

Edit ActiveMatrix Administrator Server Configuration: Administrator Server Selection

Field Description

Server Name Lists the available Administrator servers.

Default: AMX BPM - AMX BPM Server


Edit ActiveMatrix Administrator Server Configuration | 299

Edit ActiveMatrix Administrator Server Configuration

Field Description

Edit HTTP Connection Settings

Whether to edit the connection settings for the ActiveMatrix Administrator server.

Default: Cleared

Edit Database Settings

Whether to edit the configuration settings for the ActiveMatrix Administrator server database.

Default: Cleared

Edit Authentication Realm Settings

Whether to edit the configuration settings for the ActiveMatrix Administrator server authentication realm.

Default: Cleared



Administrator Server Configuration: Edit HTTP Connection Settings

This screen is only displayed if you selected Edit HTTP Connection Settings on the Edit ActiveMatrix Administrator Server Configuration screen.

The default value for each field shows the current configuration setting.

Field Description

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.

External HTTP Port

The number of the external ActiveMatrix Administrator HTTP port.




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.



Keystore Location




Keystore Password



Administrator Server Configuration: Edit HTTP Connection Settings | 301




Verify Keystore

Verifies that TIBCO Configuration Tool can retrieve the specified keystore alias using the information supplied on this page.

Field Description



Administrator Server Configuration: Edit Database Settings

This screen is only displayed if you selected Edit Database Settings on the Edit ActiveMatrix Administrator Server Configuration screen.



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.

Database Driver





Max Connections




Test Connection

Verifies that TIBCO Configuration Tool can connect to the database server using the information supplied on this page.


Administrator Server Configuration: Edit Authentication Realm Settings | 303

Administrator Server Configuration: Edit Authentication Realm Settings

This screen is only displayed if you selected Edit Authentication Realm Settings on the Edit ActiveMatrix Administrator Server Configuration screen.


Field Description

Authentication Realm

Realm Type The type of the authentication realm: Database or LDAP. If Database, the Administrator Server Configuration: Edit Database Authentication Realm Details screen displays. If LDAP, the Administrator Server Configuration: Edit LDAP Authentication Realm Details screens display.

Superuser Credentials





Administrator Server Configuration: Edit 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.

Database Driver





Max Connections





Administrator Server Configuration: Edit LDAP Authentication Realm Details | 305

Administrator Server Configuration: Edit LDAP Authentication Realm Details

Field Description


Comma-separated list of URLs for an LDAP server. To achieve fault tolerance, you can specify multiple URLs. For example:

ldap://server1.example.com:686,ldap://server2.example.com:1686

Fetch DN Retrieves the base DN of the LDAP server.

Bind DN Name

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

Password LDAP server password.

Context Factory

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

User Search Configuration

User Search Base DN

Base distinguished name from which the search starts.

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

User Attribute with User Name

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

Search Timeout (ms)

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

Follow Referrals

Whether to follow LDAP referrals. When selected, requests to LDAP can be redirected to another server.

Select this field to indicate that the LDAP information might be available at another location, or possibly at another server or servers.

Note: Ask your LDAP administrator whether LDAP referrals are used in your domain.




Field Description

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

Options:

• Group has users — List of users that belong to the group. When selected, the Group Attribute with User Names field is enabled.

• User has groups — List of groups to which the user belongs. When selected, the User Attribute with Group Names field is enabled.

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

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

Group Attribute with User Names

Name of the attribute in the group object containing its users.


Group Attribute with Group Name

Name of the attribute in the group object that contains the name of the group.

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

Group Attribute with Subgroup Names

Name of the attribute in the group object that contains its subgroups.


User Attribute with Group Names

Name of the attribute in the user object that lists the groups to which the user belongs.

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.


Administrator Server Configuration: Edit LDAP Authentication Realm Details | 307


Field Description

LDAP Realm

User Search Scope Subtree

Whether to search the entire subtree starting at the base DN, or search only the nodes one level below the base DN.

Security Authentication

Value of Simple Authentication and Security Layer (SASL) authentication protocol to use. Values are implementation-dependent. Some possible values are:

• Simple - Username and password are required.

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

• md-5

LDAP Server is SSL-enabled

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

Test Connection










Either:





Trust Keystore Type



Either:



Field Description




The following description applies to this screen only when it is displayed from the Edit TIBCO ActiveMatrix Administrator Server Configuration Wizard.




Default: ICONFIG_HOME\tct\admin.editor\timestamp



where:




Edit TIBCO ActiveMatrix Administrator server

Whether to apply the configuration changes to the ActiveMatrix Administrator server.

Default: Selected


| 311

IV - ADDITIONAL INFORMATION

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

Topics

• Troubleshooting Installation, page 313

• Restoring a BPM System from a Backup, page 315

• Uninstalling an ActiveMatrix BPM System, page 317

• Disaster Recovery Using Data-Level Replication, page 321

• Disaster Recovery Using Device-Level Replication, page 339

• Securing Communication Channels, page 343

• TIBCO Enterprise Message Service Server Configuration, page 347

• Using Third-Party Solutions to Configure a High Availability, Fault Tolerant ActiveMatrix BPM System, page 351


312 | IV - ADDITIONAL INFORMATION


| 313

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


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


| 315

Appendix B Restoring a BPM System from a Backup

To restore a BPM system from a previously taken backup (see Take a Backup of the Existing ActiveMatrix BPM System):

1. Shut down the BPM system. See TIBCO ActiveMatrix BPM - BPM Administration for more information.

2. Shutdown the EMS server. See the TIBCO Enterprise Message Service documentation for more information.

3. Copy the contents of the TIBCO_HOME and CONFIG_HOME directories from the backup to their original location.

4. Recover the BPM database and ActiveMatrix Administrator server databases and make them available. See the documentation provided with your database server for more information.

5. Recover and restart the EMS server. See the TIBCO Enterprise Message Service documentation for more information.

6. Restart the BPM system. See TIBCO ActiveMatrix BPM - BPM Administration for more information.

7. In TIBCO Administrator:

— Make sure the BPM application has a status of Running.

— Make sure your project applications are in the same state that they were when you took the backup.


316 | Appendix B Restoring a BPM System from a Backup


| 317

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 317

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.


318 | 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 | 319

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


320 | Appendix C Uninstalling an ActiveMatrix BPM System


| 321

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 324

• Recovering TIBCO ActiveMatrix BPM if the Primary Site Fails on page 336


322 | 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 6 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 to 6 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.

Note: The case data store (item 4) can be held as part of the main TIBCO ActiveMatrix BPM database (item 3). See ActiveMatrix BPM: BDS Database Configuration.


Data-Level Replication | 323

Figure 6 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 | 325

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 BPM case data store server (if the case data store is hosted in a separate database from the BPM database itself)

• 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 BPM - BDS Case data store Server: ip hostname aliasxx.xxx.xx.xx Oracle_server_hostname amx-bpm-bds-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.

Screen Field Enter Example

Database Administrator

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


BDS Database Configuration

URL AliasedJDBC connection string that identifies the Oracle database used to host the BDS case data store.


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



2. On the Create TIBCO ActiveMatrix Administrator Server wizard, use the indicated aliases in the following screens and fields.

Screen Field Enter Example

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.

BDS case data store Stores case data.

Note: The case data store can be held as part of the main TIBCO ActiveMatrix BPM database. See ActiveMatrix BPM: BDS Database Configuration.

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

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.


| 339

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.


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


Deleting a Replica ActiveMatrix Administrator Server | 341

Appendix F Deleting a Replica ActiveMatrix Administrator Server

To delete a replica ActiveMatrix Administrator server:

1. On the machine that is running the ActiveMatrix Administrator server instance that you do not want to delete:

a. Make sure that the super user specified in the CONFIG_HOME\admin\enterpriseName\samples\remote_props.properties file has force_delete permission. Only users with explicit force_delete and super user permission are allowed to delete an ActiveMatrix Administrator server instance.

b. Edit the CONFIG_HOME\admin\enterpriseName\samples\deleteAdminInstance_data.xml file to update the node and host name properties.

c. Open a command window in the CONFIG_HOME\admin\enterpriseName\samples folder.

d. Run the following command:

ant -f deleteAdminInstance_build.xml

The replica node is deleted from the environment and the replica host is unregistered. However, if the replica host has any runtime nodes, the replica host is not unregistered.

2. If the replica host is unregistered, go to the machine on which the deleted ActiveMatrix Administrator instance was running and terminate the tibcohost process.

Do not run the deletion script on the machine that is running the ActiveMatrix Administrator instance that you want to delete.

For example, assume your cluster consists of ActiveMatrix Administrator instance A running on machine X and ActiveMatrix Administrator instance B running on machine Y. To delete instance B, run the script from machine X.


342 | Appendix F Deleting a Replica ActiveMatrix Administrator Server


| 343

Appendix G 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 7 on page 343.

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


344 | Appendix G 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 6 on page 344 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 6 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 | 345

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 6 SSL Configuration Summary (Cont’d)

Key Channel Initial Configuration Upgrade, Downgrade or Change Configuration


346 | Appendix G Securing Communication Channels


| 347

Appendix H 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


348 | Appendix H 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 | 349

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


350 | Appendix H TIBCO Enterprise Message Service Server Configuration


| 351

Appendix I 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 8 below illustrates the use of third-party solutions to provide highly available, fault tolerant capabilities to your BPM runtime.

Figure 8 High Availability ActiveMatrix BPM System Using Third-Party Solutions

The setup requires at least three machines, say M1, M2, and M3, where:


352 | Appendix I 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.
