Tib Amx BPM Install
Tib Amx BPM Install
Tib Amx BPM Install
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN TIBCO N2 INSTALLATION GUIDE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE LICENSE FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc. TIB, TIBCO, TIBCO Software, TIBCO Adapter, Predictive Business, Information Bus, The Power of Now and TIBCO Business Studio are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries. EJB, Java EE, J2EE, JMS and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only. THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. PLEASE SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM. THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME. THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES. Copyright 2005-2010 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information
| iii
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi How to Contact TIBCO Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
iv
| Contents
|v
Preface
Topics
Documentation Conventions, page vi How to Contact TIBCO Support, page viii
vi
| Documentation Conventions
Documentation Conventions
The following conventions are used throughout this guide: The following typographical conventions are used in this manual. Table 1 General Typographical Conventions Convention
code font
Use Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example: Use MyCommand to start the TIBCO foo process.
Bold code font is used in the following ways: In procedures, to indicate what a user types. For example: Type the username
admin.
In large code samples, to indicate the parts of the sample that are of particular interest. In command syntax, to indicate the default value.
italic font
Italic font is used in the following ways: To indicate a document title. For example: See TIBCO BusinessWorks Concepts for more details. To introduce new terms. For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal. To indicate a variable in a command or code syntax that you must replace. For example: MyCommand pathname
Key combinations
Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C. Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.
Preface vii
Installation Directories
The following variables are used throughout this guide to refer to directories where BPM components are installed: Variable
TIBCO_HOME
Refers to... Many TIBCO products must be installed within the same home directory. This directory is referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME depends on the operating system. For example, on Windows systems, the default value is C:\Program Files\tibco\. TIBCO ActiveMatrix BPM installs into a directory within
<TIBCO_HOME>. This directory is referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME depends on the operating system. For
example on Windows systems, the default value is C:\Program Files\TIBCO\amx-bpm\ PATH The PATH variable specifies the location of programs that are required by other programs. In this case, it specifies the pathname to the home directory for Java and the bin directory for Apache Ant, programs that are used by TIBCO ActiveMatrix BPM. For example, if you have installed Java in the \Program Files\Java\jdk1.6.0_18 directory, set PATH to \Program Files\Java\jdk1.6.0_18\bin. The pathname to the directory where you have installed Java. For example, if you have installed Java in the \Program Files\Java\jdk1.6.0_18 directory, set JAVA_HOME to \Program Files\Java\jdk1.6.0_18.
JAVA_HOME
viii
|1
Chapter 1
Topics
System Requirements, page 2 Installation Overview, page 5 Installing TIBCO ActiveMatrix BPM, page 12 Post-Installation Tasks on page 18
| Chapter 1
System Requirements
To be able to run this version of TIBCO ActiveMatrix BPM, your computer must meet the following hardware and software requirements.
Hardware Requirements
TIBCO recommend the following hardware requirements: The minimum server machine specification is a an x86-based, Dual 2.5 Ghz processor with 4 GB of memory. You should allow 2 GB of free space on the local drive where you are installing TIBCO ActiveMatrix BPM.
Software Requirements
Make sure that your target computer meets the following software requirements before installing TIBCO ActiveMatrix BPM. Operating System and Database Requirements TIBCO ActiveMatrix BPM is supported on the following operating systems and database combinations:
SQL Server SP2 Standard (32 Bit) with SQL Server 2008 SP1 Yes SQL Server R2 Standard (64 Bit) with SQL Server 2008 SP1 No Oracle 11g Enterprise Edition Release R2 Yes
Platform Windows Server 2008 (x86) Windows Server 2008 (x64) Red Hat Enterprise Linux v5.4 (32 Bit and 64 Bit) SUSE Enterprise Linux 11 (64 Bit) Sun SPARC Solaris 10 (64 bit)
No
Yes
Yes
No
No
Yes
No
No
Yes
No
No
Yes
System Requirements 3
SQL Server SP2 Standard (32 Bit) with SQL Server 2008 SP1 No
SQL Server R2 Standard (64 Bit) with SQL Server 2008 SP1 No
The Microsoft SQL Server must be configured for XA Transactions, see Configure Your Microsoft SQL Server 2008 Database to Support XA Transactions on page 10. You must have a valid JDBC Driver for each database type, as you are asked to supply the location of your JDBC Driver during installation, see Make the JDBC Drivers Available on page 9. Java Requirements TIBCO ActiveMatrix BPM requires Java Developer Kit (JDK) Version 1.6.0_20. Browser Requirements TIBCO ActiveMatrix BPM includes the following browser based features; TIBCO Workspace and TIBCO Openspace. Shown below are the browsers that are supported for each of these features: Browser Internet Explorer 8 Mozilla Firefox 3.0 and 3.5 Safari 4 TIBCO Workspace Yes Yes No TIBCO Openspace Yes Yes Yes
LDAP Requirements TIBCO ActiveMatrix BPM requires an LDAP compatible Directory Server is required to store and authenticate users within ActiveMatrix BPM. Apache Directory Server Version 1.5.5 Ensure that the Apache Directory Server service is running before installing TIBCO ActiveMatrix BPM.
| Chapter 1
Any Directory Server used must be accessible using the Lightweight Directory Access Protocol(LDAP). Typically this will be an existing corporate LDAP; however if a corporate LDAP is not accessible or does not exist, a local LDAP such as Apache Directory Server, may be installed and used. Other Requirements TIBCO ActiveMatrix BPM requires: TIBCO Enterprise Message Service Version 5.1.5 Before installing TIBCO ActiveMatrix BPM, you must map emshost to localhost, see Configure TIBCO EMS Host on page 9. Hibernate 3.2.7 is required. During the installation process for TIBCO ActiveMatrix BPM, you can either: Make sure you are online and the installer will automatically install Hibernate, or Download Hibernate from the TIBCO download site, before installing TIBCO ActiveMatrix BPM. During installation, you will be asked to specify the directory where you downloaded Hibernate.
Installation Overview 5
Installation Overview
The following section describes what you need to know before installing TIBCO ActiveMatrix BPM.
Installation Profiles
There are three different installation profiles available that allow you to customize the installation of TIBCO ActiveMatrix BPM components. Selecting one of these profiles installs a subset of TIBCO ActiveMatrix BPM components. The following table describes the profiles: Installation Profile Install BPM, Administrator & TIBCO Host Install Administrator & TIBCO Host Install TIBCO Host Only Description Installs a complete BPM node on your machine. Installs TIBCO ActiveMatrix Administrator server and TIBCO Host only. Installs TIBCO Host only.
Using a profile results in an installation with the fewest possible steps, as it only installs the components you require. If you want to add or remove individual features, you should select Customize Installation.
| Chapter 1
The following table describes each feature: Feature BPM Administration Environment Description Installs a complete BPM node. TIBCO ActiveMatrix Administrator server is the utility used to create, configure, monitor, and manage objects in BPM at runtime. See TIBCO ActiveMatrix Administration for more information. TIBCO Host is the runtime object that serves as the point of contact between BPM nodes and Administrator server. TIBCO Host has a staging area that contains product and custom features available to the nodes it manages. It performs operations such as software distribution, node creation, node life cycling, and application deployment. Installs the TIBCO ActiveMatrix BPM documenation in <TIBCO_HOME>\bpm\1.0\doc\doc.
TIBCO Host
The following table describes the features that are selected for each profile. Install BPM, Administrator & TIBCO Host Yes Yes Yes Yes Install Administrator & TIBCO Host No Yes Yes Yes Install TIBCO Host Only No No Yes Yes
Installation Overview 7
Installation Directory
TIBCO recommends that you install TIBCO ActiveMatrix BPM into a new, empty installation environment (separate from other TIBCO products). To do this, install BPM as described in Installing TIBCO ActiveMatrix BPM on page 12. Specify a new, empty directory as the environment location or create a new, empty installation environment.
Installer Account
Windows Server 2008 You must have administrator privileges for the machine on which TIBCO ActiveMatrix BPM is installed. If you do not have administrator privileges, the installer exits. You must then log out of the system and log in as a user with the required privileges, or request your system administrator to assign the privileges to your account. If you intend to install the product on a network drive, you must ensure that the account used for installation has permission to access the network drive. Linux There are no restrictions on the type of user you should use to install TIBCO ActiveMatrix BPM. However, TIBCO recommends that you install as the user you plan to use for TIBCO ActiveMatrix BPM to avoid any potential permissions issues.
| Chapter 1
For example, C:\Documents and Settings\user-name\.TIBCO\install_03-02-2010.132827 Linux $HOME/.TIBCO/install_identifier directory where identifier is in the form of the date and time TIBCO ActiveMatrix BPM was installed and a unique number used to identify this particular installation. For example, /home/user1/.TIBCO/install_03-02-2010.132827
Pre-Installation Tasks 9
Pre-Installation Tasks
Before installation, perform the tasks described in this section as applicable.
10
| Chapter 1
Check that Port 1433 is Enabled For Your Microsoft SQL Server 2008 Database
This only applies to Microsoft SQL Server 2008. If you are using Microsoft SQL Server 2008, check that port 1433 is enabled. To do this: 1. In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration. 2. In the console pane, click Protocols for <instance name> where instance name is the name of the TIBCO ActiveMatrix BPM database. 3. In the Details pane, right-click the protocol you want to change, and then click Enable.
Pre-Installation Tasks 11
6. Double-click Component Services. The Component Services dialog is displayed. 7. Drill down to Component Services > Computer > My Computer > Distributed Transaction > Local DTC. 8. Right-click Local DTC and select Properties. The Local DTC Properties dialog is displayed. 9. Click Security. Make sure the Enable XA transactions check box is selected.
12
| Chapter 1
These messages are harmless and can be ignored. If you do not wish to see such messages, edit the environment variable PATH as shown:
PATH=/usr/ucb: $PATH; export PATH
6. Review the information in the Welcome dialog and click Next. The License Agreement dialog is displayed. 7. Review the terms of the license agreement and, if you agree to them, click I accept the terms of the license agreement. Then click Next to continue with the installation. If you do not agree to the terms of the license agreement, click Cancel to exit from the installation process. The Installation Profile Selection dialog is displayed.
14
| Chapter 1
8. Choose a profile from the list in the left hand pane. (See Installation Profiles on page 5). The right hand pane displays the features that are selected for each profile. If you select Customize Installation, all the features are selected. You can add or remove individual features, depending on your requirements. 9. The TIBCO Installation Home dialog displays. TIBCO_HOME is the preferred top level installation directory for all TIBCO products on your system. Select either: Create a new TIBCO_HOME. Click Browse to specify an environment location (a directory path to an empty folder into which the software will be installed), or accept the default environment location (which is the last directory in the path selected). Use an existing TIBCO_HOME. Select an existing TIBCO_HOME from the drop-down list. The installer automatically creates an environment name for the location you specify. The default environment name is amx-bpm. If this is not the first installation of TIBCO software, you can edit the environment name to differentiate this installation of TIBCO software from the previous installations. Click Next. 10. The Hibernate License Agreement dialog displays. Review the terms of the license agreement and, if you agree to them, click I accept the terms of the license agreement. Then click Next to continue with the installation. If you do not agree to the terms of the license agreement, click Cancel to exit from the installation process. 11. The Download Hibernate dialog displays. Click Download Hibernate assembly from TIBCO to automatically install Hibernate. To automatically install Hibernate 3.2.7, make sure you are online. See Software Requirements on page 2 for more information. Click Select the Hibernate assembly previously downloaded from TIBCO and click Browse to browse to the location if you have previously downloaded Hibernate from TIBCO. Click Next.
12. The TIBCO Configuration Directory dialog displays. The configuration directory stores BPM configuration information, for example, the properties for Workspace and Openspace. Click Next to accept the default location or Browse to browse to the location where you want your configuration information to be stored. 13. The Pre-Install Summary dialog displays. Review the information displayed in the dialog and make sure that it is correct. To change any of your choices, click Back to step back through the dialogs to the appropriate point. You can then restart the installation process from that point. 14. Click Install. The installer now performs the necessary installation tasks. 15. Once the installer has finished the installation tasks, the Running Product ANT Tasks dialog displays while the installer now performs the necessary tasks to initialize the installation. Click Show Details to see the tasks that the installer is performing. 16. The Post Install Summary dialog displays. Click Finish to exit from the installer. There is a slight delay while the installer deletes temporary files. 17. You must now run the TIBCO Configuration Tool to configure TIBCO Active Matrix BPM (see Running TIBCO Configuration Tool on page 20). The TIBCO Configuration Tool provides a set of wizards that allow you to configure the runtime objects and drivers required by TIBCO ActiveMatrix BPM. The following table describes the wizards you should run and the order in which they should be run, depending on the installation profile you chose in step 8: Installation Profile Install BPM, Administrator & TIBCO Host Wizard 1. Configure Third-Party Driver to configure the JDBC Drivers for your database. 2. Create TIBCO ActiveMatix BPM Server - V1.1 to configure TIBCO ActiveMatrix BPM. This wizard not only contains the configuration dialogs for TIBCO ActiveMatrix BPM but also incorporates the dialogs for the Create TIBCO ActiveMatrix Administrator Server - V1.1 and the Create TIBCO Host Instance - V3.1 wizards as well. Once you have completed the dialogs that are specific to TIBCO Active Matrix BPM, you can click Finish to accept the defaults for the rest of the dialogs.
16
| Chapter 1
Wizard 1. Configure Third-Party Driver to configure the JDBC Drivers for your database. 2. Create TIBCO ActiveMatrix Administrator Server V1.1 to configure your TIBCO ActiveMatrix Administrator Server.
1. Configure Third-Party Driver to configure the JDBC Drivers for your database. 2. Create TIBCO Host Instance - V3.1 to configure your TIBCO Host.
You can ignore wizards that are not relevant to the profile you selected.
When you get to the Summary screen, you must uncheck: Deploy Monitoring Service Deploy Log Service This is because it adversely effects the performance of TIBCO ActiveMatrix BPM.
2. Extract the contents of the package to a temporary directory. 3. Using a console window, navigate to the temporary directory. 4. Make a copy of the TIBCOUniversalInstaller.silent file and rename the file. 5. Using a text editor, open the copied file and update the install location and features to install. 6. Run the following:
Windows TIBCOUniversalInstaller.exe -silent -V responseFile="myfilename.silent" Linux TIBCOUniversalInstaller -silent -V responseFile="myfilename.silent"
When installation completes, a line similar to the following is written to the installer log file:
Install, com.tibco.installer.util.TIBCOInstaller, dbg.Debug, The installation has completed. Please check the log file for additional information.
7. Go to step 17 to find out how to run the TIBCO Configuration Tool to configure TIBCO Active Matrix BPM.
18
| Chapter 1
Post-Installation Tasks
The Mediation product application is not deployed by default on the BPMNode when you install ActiveMatrix BPM. Once you have installed ActiveMatrix BPM, you must manually deploy the Mediation product application. To do this: 1. From the Administrator interface in BPM runtime, go to Applications. 2. Add a new application named com.tibco.amx.it.mediation.app using the existing application template. 3. Distribute the application to the BPM Node. 4. Deploy the application by selecting Deploy with Start. Once the above application is running, you can deploy the mediation samples to check that mediation is now available. Refer to the Administration documentation for your runtime environment for more information on adding, distributing and starting your application.
| 19
Chapter 2
TIBCO Configuration Tool provides a set of wizards that allow you to configure runtime objects and drivers required by the TIBCO ActiveMatrix platform.
Topics
Running TIBCO Configuration Tool, page 20 Saving and Applying a TIBCO Configuration Tool Configuration on page 23 Configure Third-Party Driver Wizard on page 24 Create TIBCO Host Instance Wizard on page 25 Create TIBCO ActiveMatrix Administrator Server on page 27 Replicating an Administrator Server on page 43 Configure TIBCO ActiveMatrix BPM Server on page 45 Securing Communication Channels, page 47
20
| Chapter 2
The properties you specify include the database that serves as a persistent store for ActiveMatrix Administrator server and the monitoring, logging, and payload services. If you intend to use an external database other than HyperSQL you must first package and install the database driver using the Configure Third-Party Driver Wizard and start the database server before running this wizard.
Table 2 Configuration Wizards Wizard Create TIBCO Host Instance Wizard on page 25 Configure Third-Party Driver Wizard on page 24 Configure TIBCO ActiveMatrix BPM Server on page 45 Function This wizard allows you to specify the communication and management properties of a standalone TIBCO Host instance and then optionally creates and launches the TIBCO Host instance. This wizard allows you to package and deploy third-party client driver libraries, such as JDBC and JMS, into TIBCO ActiveMatrix Administrator server so that ActiveMatrix Administrator server and ActiveMatrix applications can access third-party servers. This wizard allows you to configure the BPM database and runtime clients for TIBCO ActiveMatrix BPM Server.
4. Click Load to load the values saved from a previous configuration session. The default locations of the saved configuration sessions are
CONFIG_FOLDER/tct/[admin|tibcohost|tpclshells]/date-randomNumber,
where CONFIG_FOLDER is the folder you specified in step 2. 5. Choose a wizard and configure according the wizard reference. 6. Optionally check the Configure to Secure All Communication with SSL checkbox. When checked, all wizards offering configuration options for communication channels present fields for specifying SSL configuration to secure those communication channels. The supported communication channels are between TIBCO ActiveMatrix Administrator server and TIBCO ActiveMatrix runtime objects (hosts and nodes) TIBCO ActiveMatrix Administrator server and external servers (TIBCO Enterprise Message Service, LDAP, database, UDDI) TIBCO ActiveMatrix Administrator server and its clients (GUI and CLI) Applications and resource instances (JMS, SMTP, LDAP, HTTP) 7. On any screen, click Finish to accept default values for all the configuration properties and jump to the Summary screen.
22
| Chapter 2
8. In the Summary screen, the wizard reports the configuration tasks it will perform. Do one of the following: Click Save to save configuration session settings. Click Cancel to return to the wizard selector screen. Execute the configuration tasks: a. Uncheck the checkboxes next to tasks you do not want executed. If you are running the Configure TIBCO ActiveMatrix BPM Server wizard, you must uncheck: Deploy Monitoring Service Deploy Log Service This is because it adversely effects the performance of TIBCO ActiveMatrix BPM. b. Click Configure to execute the tasks and save the configuration settings. The wizard reports the status of tasks as it completes them. On Windows systems, after the TIBCO Host instance is started, click Unblock if you see the following dialog pop up:
1. Run a wizard in TIBCO Configuration Tool. a. In the Summary screen, click the Save button. b. A confirmation dialog displays. Click OK to dismiss the dialog. c. Note the location of the configuration folder in the Session Scripts and Log Folder field. d. Click Cancel. 2. Copy the folder Session Scripts and Log Folder to the machine on which the configuration will be applied. 3. Open a command window in Session Scripts and Log Folder/scripts and run ant.
24
| Chapter 2
26
| Chapter 2
Table 6 Field
TIBCO Enterprise Message Service Server (Contd) Description A username for the TIBCO Enterprise Message Service server. Default: admin.
Username
Password
A password for the TIBCO Enterprise Message Service user. Default: None.
Enable SSL
Indicate that the TIBCO Enterprise Message Service server is enabled for SSL. When checked, the SSL Keystore Configuration fields are enabled. Choose whether to create or upload a trust store keystore.
Table 7 SSL Keystore Configuration Field SSL Config Keystore Location Keystore Type Description Specify that the trust store will be created. The location of the uploaded keystore. The type of the uploaded keystore: JKS or JCEKS. Default: JKS. Keystore Password The password that protects the uploaded keystore.
Provide the name and management port of the development node and the name of the environment that contains the node. If you intend to complete the tutorials in TIBCO ActiveMatrix Administration Tutorials, you must create the development node and accept the default values for the environment and node names. Provide the name of the communication group within which status messages are exchanged and the name of the ActiveMatrix Administrator server. Provide communication properties for the ActiveMatrix Administrator server.
ActiveMatrix Administrator server See ActiveMatrix Administrator Server on page 30. See Connection Settings on page 31.
28
| Chapter 2
Table 8 Component Options Component Notification Server See TIBCO Enterprise Message Service Server on page 25. Database See Database Details on page 33. Function Propagates status messages between hosts, nodes, and the ActiveMatrix Administrator server. Options and Actions Provide configuration details for the TIBCO Enterprise Message Service server.
Choose an internal or external database. If the latter, provide configuration details for database server. If you choose an external database, the database server must be running before running this wizard. The driver for HyperSQL database, org.hsqldb.jdbcDriver, is provided with TIBCO ActiveMatrix software. To use another database, you must first package and install the driver using the wizard Configure Third-Party Driver Wizard on page 24.
Choose a database or LDAP authentication realm. Provide configuration details for the authentication realm. A database authentication realm stores user and group authentication data in a database. Users and groups in this realm can be edited within ActiveMatrix Administrator. You also have the option to use the same database for authentication data and administration data. An LDAP authentication realm stores user and group authentication data in an LDAP server. Users and groups in this realm can only be edited with LDAP server management tools. If you choose database, and are using a database different than the one the ActiveMatrix Administrator server uses, the database server must be running before running the wizard. If you choose an LDAP realm, the LDAP server must be running.
Table 8 Component Options Component TIBCO Credential Server See Credential Server Details on page 1. Monitoring Service See Monitoring Notification Server on page 41 and Monitoring Database on page 41. Logging Service See Log Service Database on page 41. Payload Service See Payload Service Database on page 42. Aggregates and stores log entry data. Function Provides credentials to enable secure interactions between ActiveMatrix Administrator servers, hosts, and nodes. Aggregates monitoring data. Options and Actions Choose an autogenerated or external keystore. If you choose an external keystore, provide configuration details for the keystore.
Choose the ActiveMatrix Administrator notification server and database or another notification server and database. If the latter, provide the notification server and database configuration details and ensure that the database is running before running the wizard. Choose the ActiveMatrix Administrator database or another database. If the latter, provide database configuration details and ensure that the database is running before running the wizard. Choose the ActiveMatrix Administrator database or another database. If the latter, provide database configuration details and ensure that the database is running before running the wizard.
Store large payloads associated with log entries. (Internal use only.)
Table 9 Welcome Field Configure to Secure All Communication with SSL Description Check to indicate that all communication channels will be secured with SSL. When checked, the Enable SSL checkboxses on the If you choose this option, the TIBCO Enterprise Message Service server that functions as the notification server and ActiveMatrix Administratordatabase must be enabled with SSL before running the wiz
30
| Chapter 2
Table 10 ActiveMatrix Administrator Server Field Enterprise Name Description Defines a communication group for notification messages sent between ActiveMatrix Administrator server, the hosts that are bound to the server, and the nodes that are managed by those hosts. Default: AMX BPM. Server Name The name of the ActiveMatrix Administrator server. Default: AMX BPM Server. Table 11 TIBCO Host Instance Field Machine Name Description The name of the machine on which the TIBCO Host instance runs. Default: hostname, where hostname is the machine on which TIBCO Configuration Tool is being executed. The management port of the TIBCO Host instance. Default: 6051. Create Development Node Environment Name Node Name Specify whether to create a development environment and node. When checked, the Environment Name, Node Name, and Node Management Port fields display. Default: Checked. The name of the development environment that contains the development node. Default: BPMEnvironment. The name of the development node. Default: BPMNode. Node Management Port The management port of the development node. Default: 6031.
Port
. Table 12 Connection Settings Field Machine Name Management Port Description The name of the machine on which the ActiveMatrix Administrator server runs. Default: 0.0.0.0. The management port of the node, SystemNode, that runs the ActiveMatrix Administrator server. Default: 6021. Browser HTTP Port The port on which ActiveMatrix Administrator clients access the ActiveMatrix Administrator server. Default: 8120. Enable SSL for Browser HTTP Port Self-signed Certificate (Not for production) Imported Certificate Keystore Location Keystore Type Indicate whether communication between ActiveMatrix Administrator server and clients are secured with SSL. Indicate that ActiveMatrix Administrator server will identify itself to clients with a self-signed certificate.
Indicate that ActiveMatrix Administrator server will identify itself to clients with a certificate imported into ActiveMatrix Administrator server. The location of the keystore to import. The type of the uploaded keystore: JKS or JCEKS. Default: JKS.
The password that protects the keystore. The key alias that identifies entry identifying the ActiveMatrix Administrator server. The password that protects the key alias.
32
| Chapter 2
Table 13 Internal HTTP Settings Field Internal HTTP Port Enable SSL Browser Idle Session Timeout(m) Use HTTP Load Balancer Load Balancer URL Description The number of the internal HTTP port used by host and nodes to download artifacts from the ActiveMatrix Administrator server. Indicate whether communication between ActiveMatrix Administrator server and hosts and nodes are secured with SSL. The length of time before the login session of the ActiveMatrix Administrator GUI times out. Default: 30. Specify that an HTTP load balancer will be used to distribute requests from hosts and nodes to the ActiveMatrix Administrator server. When checked, the Server Base URL field displays. The base URL for the ActiveMatrix Administrator server load balancer. Default: http://hostname:port, where hostname is the ActiveMatrix Administrator server hostname and port is the ActiveMatrix Administrator server port. Configuration details of the TIBCO Enterprise Message Service server that will be used to deliver notifications and serve as the Messaging Bus for the environments created in the ActiveMatrix Administrator server. Table 14 Field Machine Name Port List TIBCO Enterprise Message Service Server Description A comma separated list of machinename:port addresses for a TIBCO Enterprise Message Service server. Default: machinename:port, where machinename is the machine on which TIBCO Configuration Tool is being executed and port is 7222 or 7243 (when SSL enabled). Username A username for the TIBCO Enterprise Message Service server. Default: admin. Password A password for the TIBCO Enterprise Message Service user. Default: None. Enable SSL Indicate that the TIBCO Enterprise Message Service server is enabled for SSL. When checked, the SSL Keystore Configuration fields are enabled.
Choose whether to create or upload a trust store keystore. Table 15 SSL Keystore Configuration Field SSL Config Keystore Location Keystore Type Description Specify that the trust store will be created. The location of the uploaded keystore. The type of the uploaded keystore: JKS or JCEKS. Default: JKS. Keystore Password The password that protects the uploaded keystore.
Table 16 Database Details Field Use Default In-Process Database Database Driver Description Specify that the ActiveMatrix Administrator server database is an embedded in-process database. If unchecked, the database configuration fields display. Default: Checked. The driver for the external database. The driver for HyperSQL database, org.hsqldb.jdbcDriver, is provided with TIBCO ActiveMatrix software. To use another database you must first package and install the driver using the Configure Third-Party Driver Wizard on page 24. Default: org.hsqldb.jdbcDriver. Database URL The URL of the external database. Default: jdbc:hsqldb:hsql://localhost:1234/amx. Username The external database username. Default: sa. Password The external database password. Default: None.
34
| Chapter 2
Table 16 Database Details Field Max Connections Enable SSL Description The maximum number of database connections to allocate. Default: 5. Indicate that the database server is enabled for SSL. When checked, the SSL Keystore Configuration fields are enabled.
Trust Keystore Table 17 SSL Keystore Configuration Field Create a Trust Store... Keystore Location Keystore Type Description Invokes a wizard to import certificates from a server and create the trust store. The location of the keystore. The type of the keystore: JKS or JCEKS. Default: JKS. Keystore Password The password that protects the keystore.
a. Click Create a Trust Store.... b. Specify a password to protect the keystore and click Next >. The SSL setup wizard displays certificates imported from trusted servers. c. In the Trust Selected Certifications area, check the checkboxes next to the certificates to trust and click Finish. The wizard fills in the Keystore Location, Keystore Type, and Keystore Password fields.
Upload
a. Click Browse and navigate to the location of the keystore. b. Click the keystore and click Open. The wizard fills in the Keystore Location field. c. In the Keystore Type drop-down list, select the keystore type. d. Type the keystore password. e. Click Test Connection.
Authentication Realm Realm Type The type of the authentication realm: Database or LDAP. If Database, the Table 19 on page 35 screen displays. If LDAP, the LDAP Authentication Realm Details on page 1, Group Settings on page 1, and LDAP Server Settings on page 3 screens display.
Superuser Credentials Username The ID of the initial superuser. Default: root. Password The password of the superuser. Default: t.
Table 19 Database Authentication Realm Details Field Use ActiveMatrix Administrator Database Description Specify whether the database authentication realm should use the same database as the ActiveMatrix Administrator server. Default: Checked. If unchecked, the database configuration fields in Database Details on page 33 display.
36
| Chapter 2
Table 20 LDAP Authentication Realm Details Field Bind DN Name Description 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 Context Factory LDAP server password. The factory object that provides the starting point for resolution of names within the LDAP server. Default: com.sun.jndi.ldap.LdapCtxFactory. Server URL The URL used to log in to the LDAP server. Default: ldap://localhost:389. User Search Configuration User Search Base DN User Search Expression Base distinguished name from which the search starts. Default: ou=people,ou=na,dc=example,dc=org. The expression used for searching a user. For example: (CN=%U). '%U' is replaced by the username being searched for. You can define any complex filter such as (&(cn=%U)(objectClass=account)). Default: (&(uid={0})(objectclass=person)). Attribute Name to Get User's Name Search Timeout (sec) The name of the attribute in the user object that represents the user's name. Default: uid. The time to wait for a response from the LDAP directory server. Default: 10.
Table 21 Group Settings Field Group Search Base DN Description Base distinguished name from which the search for the group starts. Default: ou=groups,ou=na,dc=example,dc=org.
Table 21 Group Settings (Contd) Field Group Search Expression Description Search by matching this expression against potential groups. Default: uniquemember={0}. Group Attribute Users Name The name of the attribute in each group object denoting its users. Example: uniqueMember (OpenLDAP) or member (ActiveDirectory). Default: uniqueMember. Group Attribute Groups Name The name of the attribute in each group object that contains the name of the group. Example: cn (OpenLDAP) or sAMAccountName (ActiveDirectory). Default: cn. Group Attribute Subgroup Name The name of the attribute in each group denoting subgroups. Example: uniqueMember (OpenLDAP) or member (ActiveDirectory). Default: uniqueMember. Group Indication Specifies how a users group memberships are found. Group information is used by the Administrator when a user, once authenticated, performs other activities in the system. Options: Group Has User Members A list of users that belong to the group. User Has Group Memberships A list of groups to which the user belongs. User DN Hierarchy Implies Group Memberships The DN with a list of groups to which the user belongs.
Default: Group Has User Members. Group Search Scope Subtree When searching the group, indicate whether to traverse into the subtree or to search only under the group base distinguished name. Default: Checked (enabled).
38
| Chapter 2
Table 22 LDAP Server Settings Field LDAP Realm User Search Scope Subtree (optional) Key Password (optional) Search the entire subtree starting at the base DN, otherwise search only the nodes one level below the base DN. Default: Checked (enabled). The value of the password protecting the key for the admin's password. Only used when logging in as the Administrator. Default: No default for Key Password. Security Authentication Security protocol to be used by JNDI. SimpleUsername and password are required. StrongSSL with client-side authentication is enabled. NoneNo log-in is performed, any other settings are ignored, and the LDAP client is anonymous. Description
Default: Simple. LDAP Authentication User DN Template The template by which the User DN, used to connect to the LDAP server, is generated. Because the full DN is always supplied, the template should always be 0 (zero). Default: uid={0},ou=people,ou=na,dc=org User Attributes Extra (optional) Enable SSL An optional list of user attributes to retrieve from the LDAP directory during authentication. Default: Empty (no additional attributes will be retrieved for the user). Indicate that the LDAP server is enabled for SSL. When checked, the SSL Keystore Configuration fields are enabled.
Trust Keystore Table 23 SSL Keystore Configuration Field Create a Trust Store... Keystore Location Keystore Type Description Invokes a wizard to import certificates from a server and create the trust store. The location of the keystore. The type of the keystore: JKS or JCEKS. Default: JKS. Keystore Password The password that protects the keystore.
a. Click Create a Trust Store.... b. Specify a password to protect the keystore and click Next >. The SSL setup wizard displays certificates imported from trusted servers. c. In the Trust Selected Certifications area, check the checkboxes next to the certificates to trust and click Finish. The wizard fills in the Keystore Location, Keystore Type, and Keystore Password fields.
Upload
a. Click Browse and navigate to the location of the keystore. b. Click the keystore and click Open. The wizard fills in the Keystore Location field. c. In the Keystore Type drop-down list, select the keystore type. d. Type the keystore password. e. Click Test Connection.
40
| Chapter 2
Table 24 Credential Server Details Field Machine Name Port List Description A comma separated list of machinename:port addresses for the TIBCO Credential Server. Default: machinename:port, where machinename is the machine on which ActiveMatrix Administrator server runs and port is 6041. Username A user identifier for TIBCO Credential Server clients. Default: user1. Password The password for the client. Default: password1. Choose whether to use a self-signed keystore generated by TIBCO Credential Server or a keystore that has been signed by a CA. Table 25 Credential Server Keystore Field Auto-generated Keystore Common Name Description Specify that the TIBCO Credential Server keystore will be generated. When selected, the Common Name field displays. The TIBCO Credential Servers issuer name. Default: amxadmin. Provided Keystore Keystore Location Specify that the TIBCO Credential Server keystore will be provided. When selected, the keystore fields displays. The location of the keystore. Default:
TIBCO_HOME/tibcohost/1.2/templates/admin.default.ssl.trust.store
.ts.
Keystore Type
Keystore Password
Table 25 Credential Server Keystore Field Key Alias Key Password Description The name of the alias used to access the identity. The password for the alias.
Table 26 Monitoring Notification Server Field Use ActiveMatrix Administrator Notification Server Description Specify whether the monitoring service should use the same notification server as the ActiveMatrix Administrator server. Default: Checked. If unchecked, the notification server fields in TIBCO Enterprise Message Service Server on page 1 display.
Table 27 Monitoring Database Field Use ActiveMatrix Administrator Database Description Specify whether the monitoring service should use the same database as the ActiveMatrix Administrator server. Default: Checked. If unchecked, the notification server fields in Database Details on page 33 display.
Table 28 Log Service Database Field Use ActiveMatrix Administrator Database Description Specify whether the log service should use the same database as the ActiveMatrix Administrator server. Default: Checked. If unchecked, the database server fields in Database Details on page 33 display.
42
| Chapter 2
Table 29 Payload Service Database Field Use ActiveMatrix Administrator Database Description Specify whether the payload service should use the same database as the ActiveMatrix Administrator server. Default: Checked. If unchecked, the database server fields in Table 16, Database Details, on page 33 display.
1. Perform step 1 in Saving and Applying a TIBCO Configuration Tool Configuration on page 23. Choose the Create TIBCO ActiveMatrix Administrator Server wizard. a. In the Connection Settings screen, select the Use HTTP Load Balancer checkbox and specify the load balancer URL. The load balancer should have sticky connections so that the client session context is maintained. b. In the Database Details screen, specify an external database. Ensure that the URL in the Database URL field contains a DNS name. 2. Edit the file Session Scripts and Log
Folder/scripts/integration_create_admin_data.xml.
a. Set the instanceWorkFolder attribute of the AdminConfigFolders element to a folder that is the same on all machines. b. Set the sharedWorkFolder attribute of the AdminConfigFolders element to a folder in the shared file system. c. Set the location attribute of the SCMDetails element to a location in the shared file system. d. Save the file. 3. Perform step 3 in Saving and Applying a TIBCO Configuration Tool Configuration on page 23. A TIBCO Host instance named SystemHost is created and started. A node named SystemNode is created in the environment named SystemEnvironment and started. The Administrator server runs on SystemNode. 4. Perform step 2 in Saving and Applying a TIBCO Configuration Tool Configuration on page 23. Choose the machine on which to replicate the Administrator server.
44
| Chapter 2
5. Edit files in the Session Scripts and Log Folder/scripts folder on the replica machine: a. In the admin-envt-data.xml file, comment out the Environment element. b. In the admin-tibcohost-instance.properties file, replace machineOriginal with machineReplica in the amx.th.trinity.tcs.url and amx.th.hpa.jmx.interface properties. c. In the cl_logservice_data.xml, cl_payloadservice_data.xml, integration_create_admin_data.xml files, replace all instances of SystemNode with another node name, SystemNodeReplica and all instances of SystemHost with another host name, SystemHostReplica. d. In the file integration_create_admin_data.xml replace all instances of machineOriginal with machineReplica, except for the instances in the StatusTransportDetails, JdbcResourceTemplate > Direct, and SystemMessagingBus elements. 6. Edit TIBCO_HOME/administrator/3.0/scripts/instance-mgmt.xml on the replica machine: a. In the file, replace
<target name="full-setup" depends="-define-macros, create-dir-structure, standalone-tcs, start-th, deploy-admin, -maybe-create-dev-node, deploy-mediation, configure.tcs, start.tcs"/>
with
<target name="full-setup" depends="-define-macros, create-dir-structure, start-th, deploy-admin, -maybe-create-dev-node, deploy-mediation"/>
7. If you installed third-party drivers before running the Create TIBCO ActiveMatrix Administrator Server wizard, install the drivers using the Configure Third-Party Driver Wizard on the replica machine. 8. Perform step 3 in Saving and Applying a TIBCO Configuration Tool Configuration on page 23. A TIBCO Host instance named SystemHostReplica is created and started. A node named SystemNodeReplica is created in the environment named SystemEnvironment and started. The replica Administrator server runs on SystemNodeReplica. When you log in to either of the Administrator servers (or access the load balancing URL), there will be two hosts in Infrastructure > Hosts screen and two nodes in the SystemEnvironment environment in the Infrastructure > Nodes screen. Requests can be processed by either of servers. If one node is unavailable, the other will able to process requests.
DBA Username
Table 31 ActiveMatrix BPM: Runtime Database Configuration Field JDBC URL Username Description The JDBC URL field is automatically completed with the connection string used in the JDBC connection to the BPM database. Specify the user name of the login that you want BPM to use to connect to the BPM database. The TIBCO Configuration Tool automatically creates the username you specify. Default: bpmuser. Password Confirm Password Enter the password for the specified user login. Enter the password for the specified user login again to confirm it.
46
| Chapter 2
Table 32 ActiveMatrix BPM: Client Configuration Field HTTP Work Presentation Host Description The machine name that hosts Workspace. If the machine is different from the machine where you are running BPM, then this should be a fully qualified domain name or IP address. The machine name you specfiy is also the name used in the default security certificate. Default: localhost HTTP Port The port for Workspace. Default: 8080. Enable SSL SMTP Host Specify to enable secure communication for Workspace and Openspace. The machine name that hosts the SMTP server that is used by Workspace. If the machine is different from the machine where you are running BPM, then this should be a fully qualified domain name or IP address. Default: localhost. SMTP Port The port number used by the SMTP server. Default: 25.
Table 33 SSL Configuration Workflows Channel TIBCO ActiveMatrix Administrator server and TIBCO ActiveMatrix runtime objects (hosts and nodes) Initial Configuration Secured by TCS: TCS Configuration Internal Port Number Checkbox to enable SSL Update Configuration CLI Action to upgrade/downgrade SSL and change port number Configure external load-balancer (virtual host:port)
TIBCO ActiveMatrix Administrator server and external servers (LDAP, database, UDDI)
enable SSL for LDAP, DB in admin creation Allows keystore to be provided in two ways: Offers trust workflow (do you want to trust this url?) Upload a user-created truststore
TIBCO ActiveMatrix Administrator server and external servers (TIBCO Enterprise Message Service
option for keystore location and keystore passwords for trust store
Provide CLI/UI Option to enable, disable QIN with SSL and change QIN configuration Provide UI Option to upload keystore, password and host it internally (Through KCP) Provide a trust workflow in UI.
48
| Chapter 2
Table 33 SSL Configuration Workflows Channel TIBCO ActiveMatrix Administrator server and its clients (GUI and CLI) Initial Configuration Upload your keystore with identity certificate We generate a self-signed identity certificate (demos-only) Auto-configures CLI on local machine to enable SSL connectivity Writes the keystore to a known location. Update Configuration CLI-only (no UI) action to upgrade & downgrade to SSL CLI-only (no UI) action to change SSL configuration
SSL Setup Wizard that has the trust-workflow. Auto-create the chain of resource templates. Host keystores in Administrator or externally
| 49
Chapter 3
Why and how should I set the DISPLAY variable on Solaris for GUI mode? The installer on Solaris opens an additional window, generally for graphics. It uses the DISPLAY environment variable to tell it on which computer to open the window. If the environment variable is not set, the installer will either wait or abort after displaying:
InstallShield Wizard Initializing InstallShield Wizard... Preparing Java(tm) Virtual Machine... ................................... ................................... ........
Set the DISPLAY variable to the IP address or name of the computer (on which the installer graphics window is to be displayed), followed by a screen address, which can be :0.0. For example:
# Bourne shell DISPLAY=ip_address:0.0; export DISPLAY # Korn shell export DISPLAY=ip_address:0.0 # C-shell setenv DISPLAY ip_address:0.0
For example, consider a scenario where you need to install TIBCO ActiveMatrix Service Grid on a remote Solaris machine (named itaska). Because you have a Solaris 5.6 machine (named alaska) that has a video card and monitor installed, you can run an X-window application on it. So you decide to telnet to itaska from alaska. When you telnet to itaska, you will not get access to itaska's monitor and will be unable to display an X-window application. That is why you must set the DISPLAY variable, which instructs the X-server to redirect all windows to the computer set in the variable. Before doing so, the computer (specified in the DISPLAY variable) must give permissions to share its monitor.
alaska> xhost + # give permission for all to its share monitor alaska> telnet itaska Welcome to HPUX itaska 11.00 User: Password: itaska> export DISPLAY=alaska:0.0 # set display on alaska itaska> tar -xvf TIB_tra-suite_5.0.0_h7_11.tar
50
| Chapter 3
| 51
Chapter 4
This chapter explains how to uninstall TIBCO ActiveMatrix BPM from your computer.
Topics
Uninstalling TIBCO ActiveMatrix BPM on page 52
52
| Chapter 4
54
| Chapter 4
| 55
Appendix A
This chapter explains how to configure TIBCO ActiveMatrix BPM in a high availability standby implementation.
Topics
Configuring TIBCO ActiveMatrix BPM in a High Availability Implementation on page 56
56
| Appendix A
Shared Storage
BPM Node or BPM Data files Oracle RAC Datafiles
Machine 2
Machine 3
Oracle RAC
Machine 1
Administrator Server
To implement this scenario, at least three machines are required. Machine 1: TIBCO ActiveMatrix BPM software is installed TIBCO ActiveMatrix Administrator server is installed and running. Machines 2 and 3: are connected to a shared file system (like SAN storage, for example). are part of an active-passive clustering setup. At any given time, either Machine 2 or Machine 3 has access to the SAN shared file system on which TIBCO ActiveMatrix BPM node is installed/running. If there are catastrophic events such as power loss, hardware failure, network disruption, or operating system crash, the cluster software will detect and fail over to the next available server. on either machine 2 or 3: a fully operational TIBCO ActiveMatrix BPM node is installed and running. TIBCO ActiveMatrix BPM (or at least the data folder) needs to be on the shared file system and should only be vailable to the machine that has a fully operational TIBCO ActiveMatrix BPM node installed and running.
On Machine 1
Install the TIBCO ActiveMatrix BPM software and create a TIBCO ActiveMatrix Administrator server. To do this: 1. Install TIBCO ActiveMatrix BPM using the Install BPM, Administrator & TIBCO Host profile, see Installing TIBCO ActiveMatrix BPM on page 12. 2. Using TIBCO Configuration Tool, run the Create TIBCO ActiveMatrix Administrator Server - V3.0 wizard to create a TIBCO Administrator server, see Create TIBCO ActiveMatrix Administrator Server on page 27.
On Machine 2 or 3
Install a fully operational TIBCO ActiveMatrix BPM server. To do this: 1. Install TIBCO ActiveMatrix BPM using the Install BPM, Administrator & TIBCO Host profile, see Installing TIBCO ActiveMatrix BPM on page 12.
58
| Appendix A
2. Using TIBCO Configuration Tool: a. Run the Create TIBCO Host Instance - V3.0 wizard to create a TIBCO Host, see Create TIBCO Host Instance Wizard on page 25. From the TIBCO Host Instance Configuration: Administrator Server dialog, select Bind this TIBCO Host instance with an existing Administrator server box and enter the details of TIBCO ActiveMatrix Administrator server that you created on machine 1. b. Run the Configure Third-Party Driver wizard to register the JDBC drivers for your BPM database, see Configure Third-Party Driver Wizard on page 24. c. Run the Create TIBCO ActiveMatrix BPM Server - V1.0 wizard, see Configure TIBCO ActiveMatrix BPM Server on page 45. From the ActiveMatrix BPM: Administrator Server Configuration: dialog, select the Use Existing ActiveMatrix Administrator Server check box. In the Machine Name box, type the name of the TIBCO ActiveMatrix Administrator server you created on machine 1. In the Host box, type the name of the TIBCO Host you created in step a.