TIBCO ActiveMatrix® Administration

Software Release 2.2 March 2009

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 LICENSE.PDF) 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 ActiveMatrix, TIBCO Adapter, TIBCO Administrator, TIBCO AutoMeditate, TIBCO Enterprise Message Service, ActiveMatrix, AutoMediate, Predictive Business, Information Bus, The Power of Now, and TIBCO Rendezvous are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries. EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. PLEASE SEE THE README.TXT 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-2009 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information

| iii

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii TIBCO ActiveMatrix Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Third Party Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx How to Contact TIBCO Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii

Chapter 1 TIBCO ActiveMatrix Administrator Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 TIBCO ActiveMatrix Administrator Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 ActiveMatrix Administrator Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Life Cycle of the ActiveMatrix Runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Runtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two-Step Configuration: First Define, Then Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting Installed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deploying Service Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two-Step Deployment: First Configure, Then Deploy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Life Cycle Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7 7 8 8 8 9 9

Shared Resource Life Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Customizing HTTP Shared Resource Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2 Infrastructure Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
ActiveMatrix Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Database Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 HSQLDB Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 TIBCO Management Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting TIBCO Management Daemon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UDP, Discovery, and Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Management Daemon Status Reporting and Polling Intervals. . . . . . . . . . . . . . . . . . . . . . . . . . . 17 17 18 19

TIBCO ActiveMatrix Administration

iv

| Contents
TIBCO Enterprise Message Service™ Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Starting the TIBCO Enterprise Message Service Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 TIBCO Administrator™ and TIBCO Hawk® . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Starting TIBCO Administrator and TIBCO Hawk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 3 ActiveMatrix Administrator Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Creating the First ActiveMatrix Administrator Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before Running the ActiveMatrix Administrator Server Creation Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the ActiveMatrix Administrator Server Creation Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ActiveMatrix Administrator Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting the ActiveMatrix Administrator Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Authentication Realm Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local XML File Realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TIBCO Administrator Realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LDAP Realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating the Authentication Realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Configuration Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating the Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pre-creating ActiveMatrix Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 26 27 29 30 31 31 32 35 39 44 47 47 49 52

Default Runtime Node Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Starting and Stopping the ActiveMatrix Administrator Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Starting and Stopping the ActiveMatrix Administrator Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Chapter 4 ActiveMatrix Administrator Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
ActiveMatrix Administrator Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Graphical Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Command-Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 ActiveMatrix Administrator Graphical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging in to the ActiveMatrix Administrator Graphical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Graphic Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Perspective Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with the Graphical User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ActiveMatrix Administrator Command-Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Invoking the Command-Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AMXAdminTask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AMXAdminConfigTask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 65 67 68 72 77 77 78 85 87 97

TIBCO ActiveMatrix Administration

Contents v

|

Chapter 5 Configuring Enterprise Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Managing Machines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Binding Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unbinding Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bound Machines Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bound Machine Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add Search Parameters Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Search Parameters Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovered Machines Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Shared Resource Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Shared Resource Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing a Shared Resource Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting a Shared Resource Definition Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Shared Resource Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resource Definition Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Users, Groups, and Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Users and Groups Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Keystores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Keystores Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an Internal Keystore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an External Keystore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Keystore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing a Keystore Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reloading an Internal Keystore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Keystore Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing ActiveMatrix Administrator Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Plug-ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ActiveMatrix Administrator Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with Substitution Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Substitution Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Substitution Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing a Substitution Variable Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 100 105 109 109 110 111 112 112 114 114 115 115 117 118 137 137 138 143 145 156 156 157 158 158 158 158 159 160 160 161 161 161 163 167 167 167 167

Managing UDDI Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

TIBCO ActiveMatrix Administration

vi

| Contents
Chapter 6 Defining Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Environments Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Environments Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Creating an Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environment Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Messaging Bus Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 172 172 172

Working with Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Deleting an Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Editing an Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Configuring Messaging Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Configuring Messaging Bus Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Managing Messaging Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Enabling Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Machines in an Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling Machines in an Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Machines Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling UDDI Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling UDDI Servers in an Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling UDDI Servers in an Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UDDI Servers Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 182 182 183 184 184 184 184

Working with Shared Resource Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Enabling and Disabling Shared Resource Definitions in an Environment . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Chapter 7 Configuring Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Working with Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Assets in Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing and Uninstalling Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting and Stopping Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing a Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Node Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Permissions for Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing a Shared Library in a Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Multiple Messaging Servers in Multinode Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 189 190 192 193 194 195 197 197 197 198

Working with the Default Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Default Connector Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Working with Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling and Disabling Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating and Deactivating a Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Container Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TIBCO ActiveMatrix Administration

202 202 204 204

Contents vii

|

Working with Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling and Disabling Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing and Uninstalling Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling and Disabling Resource Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shared Resource Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with Substitution Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overriding a Substitution Variable Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reverting a Substitution Variable Back to the Global Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local Substitution Variables Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

207 207 208 208 209 211 211 211 212

Working With Logging Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Chapter 8 Deploying Service Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Deployment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Configuring Service Assemblies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Deploying a Service Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Uploading a Service Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Importing Shared Resource Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Service Assemblies Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Configuring a Service Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Configuring Service Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Mapping Shared Resource Profiles to Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Working with Service Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deploying and Redeploying Service Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting and Stopping Service Assemblies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Service Assembly Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating a Service Assembly Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading a Service Assembly Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Service Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Undeploying Service Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Service Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 221 222 223 227 228 228 229 229

Working with Service Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Service Units Table Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Service Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Mapping Shared Resource Profiles to Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Shared Resource Profiles Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Working with Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Topics Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Working with Substitution Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Working with Logging Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Working with Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Services Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

TIBCO ActiveMatrix Administration

viii

| Contents
Chapter 9 Monitoring Infrastructure and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Enabling Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Monitoring Configuration Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Accessing the Monitor & Manage Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Dashboard View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Service Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 System Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Infrastructure View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environment View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Machine View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Node View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 248 251 254

Service View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Searching for Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Integrated Service View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Provides & Consumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UDDI Publishing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Instance View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Instance Trail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Instance Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environment View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Assembly View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Unit View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 263 263 264 266 271 273 278 278 279 280 281 283 283 285 286

Browse Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

Chapter 10 Managing Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting and Stopping the TIBCO Common Logging Plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 295 295 299

Working with Log Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Creating a Log Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Setting the Default Log Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

TIBCO ActiveMatrix Administration

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 Oracle Native Thin Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Messages in JMS Container Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ActiveMatrix Node Keystores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Log Event Details . . . . 347 Enabling Secure Connections Between Nodes and ActiveMatrix Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 Enabling Secure Connections to LDAP Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 316 317 321 324 325 327 Server Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 Enabling Secure Connections to UDDI Servers . . . . . . . . . . . . Displaying the Log Viewer . . . . . . . . . . . 302 302 303 306 Working with Logging Configurations . . . . . . . . . . . . . . . . . . . . . . . Working with the Query Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling HTTPS in ActiveMatrix Administrator Clients . . . 308 Logging Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 Enabling Secure Connections Between Nodes and ActiveMatrix Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 Securing JDBC Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Formats . . . . . . . . . . . . . . . . 347 Enabling Secure Communications Between Nodes and Messaging Servers . . . . . . ActiveMatrix Administrator Server Keystores . . . . . . . . . . . . . 338 338 339 340 341 342 342 342 343 Enabling SSL for Management Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ActiveMatrix Administrator Command-line Tool Keystores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purging a Log Service Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing a Log Service . . . . . . . . . . . . . . . 336 Keystores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 TRA File Locations. . . . . . . . . . . . . . . 353 Race Condition Between Consumer and Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Appendix A Securing TIBCO ActiveMatrix Communication Channels . . . Deleting a Log Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 TIBCO ActiveMatrix Administration . . . . . . . Working with the Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents ix | Starting and Stopping a Log Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management Daemon Keystores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 Appendix B Messaging Scenarios for In-only MEPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 Messages In AMX Binding Queue . . . . 349 Enabling Secure Connections to Auxiliary Servers . . . . . . . . Enabling HTTPS in ActiveMatrix Administrator Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling HTTPS for ActiveMatrix Administrator Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Using the Log Viewer. . . . . . . . . . . . . . Setting up ActiveMatrix Administrator Keystores . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 ActiveMatrix Administrator Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 Best Practices . . . 372 Acceptor-Thread Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 Allocated Memory Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 360 360 361 361 361 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 Adding Permission to Publish to a Business . 377 TIBCO ActiveMatrix Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 Overview . . . . . . . Stop . . . . . . . . . . . . . . . . . . . . . . . . . . Session Count and Max Pool Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Appendix E Publishing Services to ActiveMatrix Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 364 364 364 365 Appendix D ActiveMatrix Server Performance Tuning . . . . . . . . . Local Invocations . . . . . . . . . . . . . . . . . . Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .x | Contents Appendix C Session and Thread Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 Using Client and Server Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Number of Web-worker Threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Session Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 Enabling Non-Administrator Users to Publish to the ActiveMatrix Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Life Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 JVM Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 TIBCO ActiveMatrix Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 SQL Server DDL User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Configure Environments Perspective . . . . . . . 318 Model Selection Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Services and Service Instances . . . . . . . . . . . . . . . . . . . . . 54 Welcome Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Node and Container Logging Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Deploy to Environment Perspective . . . 309 Service Assembly and Service Unit Logging Configurations . . . . . . . . . . . . . . . . . . . . . . . . . 71 Monitor & Manage Perspective . . . . . . . . . . . . . . . . . . . . . . . . 68 Configure Enterprise Assets Perspective. . . . . . . . . . . . . 53 SQL Server DML User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Container Status Life Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Service Assembly State . . . . . . . . . . . . . 76 Parent-Child Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Enterprise Assets Tab Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . and Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Log Navigator and Log Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 System Messages . . . . . . . . . . . . . . 105 Components . . . . . 146 Node Status Life Cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Relationships between ActiveMatrix Administrator. . . 274 ActiveMatrix Logging Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Shared Resource Status Life Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Local Network Discovery . . . . . . . . . . . . . . 81 Object Association . . . . . 309 Query Builder . . . . . . . . . . . . . . . . . . . 101 Bridged Network Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Machines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| xi Figures Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 16 Figure 20 Figure 21 Figure 22 Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 TIBCO ActiveMatrix Administrator . . . . . . . . . . . . . . . 259 UDDI Publishing Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . 326 TIBCO ActiveMatrix Communication Channels. . . . . . . .xii | Figures Figure 28 Figure 29 Figure 30 Figure 31 Filter Area . . . . . . . . . 324 Log Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 TIBCO ActiveMatrix Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Log . . .

. . . . . . . . . . . . 118 Identity Shared Resource Reference . . . . . . . . . . . . 92 Options . . . . . . . . . . . . . . . . . . . . . . . . . 87 Supported Objects and Their Attribute Reference Sections. . . . . . . . 111 Search Parameters Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 TIBCO ActiveMatrix Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Local XML File Realm Reference. . . . . . 110 Add Search Parameters Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| xiii Tables Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Table 22 Table 23 Table 24 Table 25 Table 26 Table 27 Table 28 General Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Discovered Machines Reference . . . . . . . . . . . . . 123 JMS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Superuser Registration Reference . . . . . . . . . . . . . 109 Bound Machine Reference. . . . 112 HTTP Server Shared Resource Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Database Configuration Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Database Drivers and URL Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 TIBCO Administrator Realm Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Database Realm Authentication Superuser Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Syntax Typographical Conventions . . . . . . . . . . . . 126 JNDI Shared Resource Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Options . . . . . . . . . . . . . . . . . . . 47 Default Runtime Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 LDAP Realm Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Bound Machines Reference . . . . . . . . . . 40 Search Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 JDBC Shared Resource Reference . . . . 41 LDAP Mapping Details Reference . . . 59 Actions and Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii ActiveMatrix Administrator Reference . . . . . . . . . . . . . . . . . . . . . . . . . 34 Database Realm Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Service Assemblies Reference . . . . . . 165 Environments Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Service Units Table Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Machines Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 TIBCO ActiveMatrix Administration . . . . . . . . . . . . . . . . . . . . . 165 Administrator Server Reference . . . . . . . . . . . . . . . . . . . . . 235 Substitution Variables Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Mapped Nodes Reference . . . . . . . . . . . . . . . . . . . . . . . . 132 SSL Server Shared Resource Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Keystore Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Rendezvous Shared Resource Reference . . . . . . . . . . . 163 Administrator Servers Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Environment Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Groups List Reference . . . . . . . . . . . . . . . . . . . . 219 Service Assembly Reference . . . . . . . . . . . . . . . . . . . . . . . 160 Plug-ins Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 UDDI Server Reference. . . . . . . . . . . . . . . . . . 172 Messaging Server Reference . . . . . . . . . . . . 234 Topics Reference . . . . . . . .xiv | Tables Table 29 Table 30 Table 31 Table 32 Table 33 Table 34 Table 35 Table 36 Table 37 Table 38 Table 39 Table 40 Table 41 Table 42 Table 43 Table 44 Table 45 Table 46 Table 47 Table 48 Table 49 Table 50 Table 51 Table 52 Table 53 Table 54 Table 55 Table 56 Table 57 Table 58 Table 59 Table 60 JNDI SSL Application Properties. . . . . . . . . . . 199 Container Type Attribute Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Database Configuration Reference . . . . . . 190 Node Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Local Substitution Variables Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Container Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Default Connector Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Substitution Variables . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Services Reference . . . . . . . . . . . . . . . . . . 204 Shared Resource Reference . . . . . . . . . . . . . . . . . . . . . 185 Nodes Reference . . . . . . . . . . . . . . . . . . 233 Shared Resource Profiles Reference . . . . . . . . . . . . . . . . . . . . . . . . . . 145 UDDI Server Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Actions and Service Assembly Status Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Top 20 Hits . . . . 267 Interface Consumed By . . . 257 Services . . . . . . . 269 Composite Reference Provides . . . . . . . . . 257 Service Instances . . . . . . . . 270 Interfaces and Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Endpoint Chosen for Publication . . . . . . . 245 Top 20 Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 TIBCO ActiveMatrix Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Machine Details . . . . . . . . 272 UDDI Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Performance . . . . . . . . 270 Interface Consumed By . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Services Details . . . . . . . . . . . . . . . . . . . . 248 Nodes . . . . . . . . . . . . 255 Containers . . . . . . . . . . . . . . . . . . 267 Consumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Interface Invokes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Service Trail . . . . . . . . . . . . . . . . . . . . . . . 251 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Interface Invokes . . . . . . . . . . . . . . . . . . . . . . 277 Service Instance Trail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Node Details. . . . . . . . . . . .Tables xv | Table 61 Table 62 Table 63 Table 64 Table 65 Table 66 Table 67 Table 68 Table 69 Table 70 Table 71 Table 72 Table 73 Table 74 Table 75 Table 76 Table 77 Table 78 Table 79 Table 80 Table 81 Table 82 Table 83 Table 84 Table 85 Table 86 Table 87 Table 88 Table 89 Table 90 Table 91 Table 92 Monitoring Configuration . . . . . . . . . . . . . . . . . . . . . 252 Node Trail. . . . . . . . . . . . . . . . . . . . 246 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Provides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Metadata . . . . . . . . . . . . . . . . 271 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Composite Service Consumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. 308 Object Logging Configuration Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 Log Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Server Log Locations . . . . . . . . . . . . . . . . . . . . . . . . . . 369 TIBCO ActiveMatrix Administration . . . . . . . . 281 Interface and Operations . . . . . . . 304 Parent-Child Logging Configuration Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Log Service Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 Filter Operators . . .xvi | Tables Table 93 Table 94 Table 95 Table 96 Table 97 Table 98 Table 99 Table 100 Table 101 Table 102 Table 103 Table 104 Table 105 Table 106 Table 107 Table 108 Table 109 Table 110 Table 111 Table 112 Table 113 Table 114 Table 115 Table 116 Table 117 Service Instance Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 JNDI SSL Application Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 Service Assembly Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Performance . . . . . . . . . . . . . . . . . 308 Object Logging Configuration Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 BW Engine Event Format Attribute Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 TRA File Locations . . . . . . . . . . . . . . . . . . 320 Base Event Format Attribute Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 Service Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Service Assembly Trail . . . 287 Service Unit Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 JVM Client and Server Mode Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 287 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . and Session/Thread Pool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Situation Types . . . . . . . . . . . . . . 352 Role (Consumer/Provider). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Service Assemblies . . . . . . . . . . . MEP. . . . . . . . . . . . . 286 Service Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 Engine Event Format Attribute Reference. . . . . . . . . . . . . . . . . . . . . .

page xx How to Contact TIBCO Support. page xviii Typographical Conventions. Topics • • • Related Documentation. deploying. ActiveMatrix provides a scalable and extensible platform for developing. page xxiii TIBCO ActiveMatrix Administration .| xvii Preface The TIBCO ActiveMatrix® Administrator is a web-based user interface and server for configuring ActiveMatrix® environments and deploying ActiveMatrix services into them. and managing applications that conform to a service-oriented architecture.

The other manuals in the documentation set assume you are familiar with the information in this manual. TIBCO ActiveMatrix Administration: Read this manual to learn how to manage the ActiveMatrix runtime and deploy and manage ActiveMatrix services.xviii Related Documentation | Related Documentation This section lists documentation resources you may find useful. This manual describes terminology and concepts of the ActiveMatrix platform. TIBCO ActiveMatrix Composite Editor User’s Guide: Read this manual to learn how to develop and package ActiveMatrix composites. TIBCO ActiveMatrix Documentation The following documents form the core of the TIBCO ActiveMatrix documentation set: • TIBCO ActiveMatrix Concepts: Read this manual before reading any other manual in the documentation set. • • Other TIBCO Product Documentation You may find it useful to read the documentation for the following TIBCO products: • • • • • • • • • • TIBCO ActiveMatrix® Service Bus TIBCO ActiveMatrix® Service Grid TIBCO ActiveMatrix® BusinessWorks TIBCO ActiveMatrix® Registry TIBCO ActiveMatrix® Policy Manager TIBCO Enterprise Message Service™ TIBCO Adapter™ TIBCO Administrator™ TIBCO Hawk® TIBCO Rendezvous® TIBCO ActiveMatrix Administration .

oasis-open.php?cat=ws — UDDI Version 3 OASIS Standard http://www.org/TR/2000/NOTE-SOAP-20000508/ — WSDL 1.org/specs/index.w3.org/committees/tc_cat.org/TR/wsdl • OASIS http://www.w3.org/2002/ws/ — Simple Object Access Protocol (SOAP) 1.1 W3C Note http://www.org/display/Main/Service+Component+Architecture+Sp ecifications World Wide Web Consortium web services activity http://www.w3.php#uddiv2 • TIBCO ActiveMatrix Administration .1 W3C Note http://www.oasis-open.osoa.Preface xix | Third Party Documentation TIBCO ActiveMatrix software supports the following standards: • Service Component Architecture http://www.

Other TIBCO products are installed into an installation environment. filenames. The value of TIBCO_HOME depends on the operating system. Path The directory into which the product is installed. TIBCO ActiveMatrix Administrator installs into a directory inside ENV_HOME. on Windows systems the default value is C:\tibco. TIBCO ActiveMatrix Administration . code font Code font identifies commands. • • Description Provides information about what the environment contains or is used for. The value of ENV_HOME depends on the operating system. on Windows systems the default value is C:\tibco\amxadministrator\. This directory is referenced in documentation as AMX_HOME. An installation environment consists of the following properties: • Name Identifies the installation environment. This directory is referenced in documentation as TIBCO_HOME. TIBCO ActiveMatrix installs into a directory inside ENV_HOME. pathnames.xx | Typographical Conventions Typographical Conventions The following typographical conventions are used in this manual. Incompatible products and multiple instances of the same product must be installed into different installation environments. For example. This directory is referenced in documentation as ENV_HOME. on Windows systems the default value is C:\tibco. A product installed into an installation environment does not access components in other installation environments. Table 1 General Typographical Conventions Convention TIBCO_HOME ENV_NAME ENV_HOME AMX_HOME AMX_ADMIN_HOME Use Many TIBCO products are installed within the same home directory. The value of AMX_ADMIN_HOME depends on the operating system. For example: Use MyCommand to start the foo process. and output displayed in a command window. For example. This directory is referenced in documentation as AMX_ADMIN_HOME. code examples. For example. This directory is referenced in documentation as ENV_NAME. The value of AMX_HOME depends on the operating system. For example. The name is appended to the name of Windows services created by the installer and is used in the path to the product in the Windows Start > All Programs menu. on Windows systems the default value is C:\tibco\amx\.

for example. for example. To indicate a variable in a command or code syntax that you must replace. In large code samples. Key names separated by a comma and space indicate keys pressed one after the other. to indicate the parts of the sample that are of particular interest. for example. Ctrl+Q. Portlets are mini-applications that run in a portal. In command syntax. For example: MyCommand pathname Key combinations Key name separated by a plus sign indicate keys pressed simultaneously. MyCommand is enabled: MyCommand [enable | disable] italic font Italic font is used in the following ways: • • • To indicate a document title. The tip icon indicates an idea that could be useful. data loss or corruption if certain steps are taken or not taken.Preface xxi | Table 1 General Typographical Conventions (Cont’d) Convention bold code font Use Bold code font is used in the following ways: • • • In procedures. to indicate the default parameter for a command. To introduce new terms For example: A portal page may contain several portlets. TIBCO ActiveMatrix Administration . For example: See TIBCO ActiveMatrix BusinessWorks Concepts. For example: Ctrl+C. to indicate what a user types. if no parameter is specified. For example: Type admin. an additional action required only in certain circumstances. a way to apply the information provided in the current section to achieve a specific result. For example. The note icon indicates information that is of special interest or importance. The warning icon indicates the potential for a damaging situation. For example: Esc.

MyCommand param1 [param2] {param3 | param4} TIBCO ActiveMatrix Administration .xxii | Typographical Conventions Table 2 Syntax Typographical Conventions Convention [ ] Use An optional item in a command or code syntax. the command can accept either two or three parameters. For example: MyCommand [optional_parameter] required_parameter | A logical ’OR’ that separates multiple items of which only one may be chosen. or the pair param3 and param4. You can optionally include param2 as the second parameter. the following command requires two parameters. And the last parameter is either param3 or param4. MyCommand {param1 param2} | {param3 param4} In the next example. For example. For example. The first parameter must be param1. Other syntax notations may appear within each logical group. you can select only one of the following parameters: MyCommand para1 | param2 | param3 { } A logical group of items in a command. 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. which can be either the pair param1 and param2.

• For an overview of TIBCO Support. please contact TIBCO Support as follows.tibco. TIBCO ActiveMatrix Administration . If you do not have a user name. visit this site: https://support.Preface xxiii | How to Contact TIBCO Support For comments or problems with this manual or the software it addresses.com/services/support • If you already have a valid maintenance or support contract.tibco. and information about getting started with TIBCO Support. visit this site: http://www.com Entry to this site requires a user name and password. you can request one.

xxiv How to Contact TIBCO Support | TIBCO ActiveMatrix Administration .

page 2 Life Cycle of the ActiveMatrix Runtime. page 7 Shared Resource Life Cycle. Topics • • • Introduction. page 10 TIBCO ActiveMatrix Administration .|1 Chapter 1 TIBCO ActiveMatrix Administrator Overview This chapter summarizes the tasks involved in setting up a TIBCO ActiveMatrix runtime using TIBCO ActiveMatrix Administrator.

the relationship between ActiveMatrix Administrator and other processes. shared resources. TIBCO ActiveMatrix Administration . service units. These objects include enterprise assets. manage. containers. machines. service assemblies. and services. and relationship between TIBCO ActiveMatrix Administrator and ActiveMatrix machines and nodes. read at least the first chapter in TIBCO ActiveMatrix Concepts. and monitor various objects in the ActiveMatrix runtime. This manual does not explain basic ActiveMatrix concepts. Figure 1 on page 3 shows TIBCO ActiveMatrix Administrator components. environments.2 | Chapter 1 TIBCO ActiveMatrix Administrator Overview Introduction This manual explains how to set up and administer a TIBCO ActiveMatrix runtime. TIBCO ActiveMatrix Administrator Architecture TIBCO ActiveMatrix Administrator is the utility used to create. If you are not yet familiar with them. nodes. configure.

ActiveMatrix Administrator servers within a cluster share a database and authentication realm and are kept synchronized. and interacts withTIBCO Management Daemon to manage nodes. • ActiveMatrix Database Stores ActiveMatrix administration data.Introduction 3 | Figure 1 TIBCO ActiveMatrix Administrator AMA Cient Machine www AMA Command-Line Interface Management Daemon AMA Graphical UI AM Node AMA Machine 2 AMA Server 2 AM Machine 1 AMA Server 1 AMA Machine 1 Authentication Realm Management Daemon AM Node AM Machine 2 AMA Cluster Legend Database AM TIBCO ActiveMatrix AMA TIBCO ActiveMatrix Administrator The TIBCO ActiveMatrix Administrator administration architecture consists of the following components: • ActiveMatrix Administrator Server Gathers management data from nodes. interacts with the authentication realm to authenticate users. • ActiveMatrix Administrator Cluster Groups one or more ActiveMatrix Administrator servers. TIBCO ActiveMatrix Administration . responds to requests from the ActiveMatrix Administrator graphical and command-line UIs.

Management Daemon Gathers installation information and exposes ActiveMatrix node life cycle operations. TIBCO ActiveMatrix Administration . For details. Relationship to TIBCO Administrator™ Software TIBCO Administrator software and ActiveMatrix Administrator perform some similar functions for different TIBCO product families. and monitoring tasks for products in their respective product families. ActiveMatrix Administrator Command-Line Interface Provides a script-based interface. Relationship to TIBCO® Management Daemon Software ActiveMatrix Administrator uses TIBCO Management Daemon software to enable configuration and management of ActiveMatrix infrastructure. It runs on all the machines where ActiveMatrix software is installed.4 | Chapter 1 TIBCO ActiveMatrix Administrator Overview • Authentication Realm Manages user authentication data. While TIBCO Administrator uses TIBCO Rendezvous® and TIBCO Hawk® for communication. management. ActiveMatrix Administrator uses the protocols SOAP/HTTP and JMX/JMXMP. see Relationship to TIBCO® Management Daemon Software on page 4. The authentication realm can be provided either by TIBCO Administrator (see Relationship to TIBCO Administrator™ Software) or by another server or a file. Machine. and environments. ActiveMatrix Administrator Setup This section gives an overview of the relationships you set up between ActiveMatrix Administrator servers. TIBCO Management Daemon provides bootstrap and machine-level management functionality. See ActiveMatrix Administrator Cluster. machines. TIBCO Administrator software is required in an ActiveMatrix Administrator runtime only if you use the TIBCO Administrator authentication realm (see on page 23). • • • ActiveMatrix Administrator Graphical UI Provides a graphical user interface. and Environment Relationships on page 104 for more details on these relationships. Both allow you to perform deployment. clusters. From ActiveMatrix Administrator you specify Management Daemon process properties so you can administer the ActiveMatrix runtime on the machines managed by those processes.

one for each geographic region of a global enterprise. Within each cluster. Thus. that is. an environment can be administered by only one cluster. This is particularly recommended in production systems. ActiveMatrix Administrator automatically keeps the servers within a cluster synchronized. not just for that particular server. AllActiveMatrix Administrator servers in a cluster use the same database tables and you cannot change databases after you create the first server in the cluster. or you may require more. This keeps different sets of environments administered by different clusters separate from each other for better management.Introduction 5 | TIBCO ActiveMatrix Administrator Servers and Clusters The first step in setting upActiveMatrix Administrator is to create one or more ActiveMatrix Administrator servers. Authentication Realms An authentication realm describes the method of storing information about ActiveMatrix Administrator users and groups. Access to ActiveMatrix Administrator UI functions and ActiveMatrix runtimes is controlled based on permissions granted to specific users and groups. Database Tables ActiveMatrix Administrator data is stored in a database. The database tables are used only for servers in that cluster and not for any other cluster. Conversely. ActiveMatrix Administrator servers are members of a cluster. it is recommended that you create more than one server for the following reasons: • • To permit one server to take over from another in the event of server failure. All ActiveMatrix Administrator servers in the same cluster use the same authentication realm and you cannot change realms after you create the first server in the cluster. when you invoke the URL of any server in a cluster in the ActiveMatrix Administrator user interface you access the administration data for the entire cluster. You may need only one cluster. To enable flexibility in administering multiple ActiveMatrix runtimes. Therefore. before you create the first ActiveMatrix TIBCO ActiveMatrix Administration . The cluster is created when the first server is created. You select and configure the authentication realm when creating the first server in a cluster. You select and configure database tables when creating the first server in a cluster. different sets of ActiveMatrix environments and their nodes. for example. Each cluster administers a different set of environments.

you bind machines to the ActiveMatrix Administrator cluster. or LDAP. Using the ActiveMatrix Administrator graphical or command-line interfaces. You choose machines that to use for the ActiveMatrix runtime administered by this cluster. Database. TIBCO Administrator. See the following sections for feature and configuration information for the different types of realms: • • • • Local XML File Realm on page 31 TIBCO Administrator Realm on page 32 Database Configuration on page 47 LDAP Realm on page 39 Binding Machines to ActiveMatrix Administrator Clusters ActiveMatrix software must be installed on all machines that participate in the ActiveMatrix runtime that you are to setting up. Finally.6 | Chapter 1 TIBCO ActiveMatrix Administrator Overview Administrator server in a cluster. you specify which environments can use the ActiveMatrix installations it manages. TIBCO ActiveMatrix Administration . decide which kind of authentication realm you will use: Local XML File. for each bound machine.

Configuring the Runtime After you have bound machines to use in your ActiveMatrix runtime. and Permissions on page 137. The plan determines where service units run. These define connection details for physical resources required by the deployed service units. See Managing Users. Configuring shared resource definitions. Enterprise asset configuration involves: • • • Configuring UDDI servers. Configuring nodes and containers for each environment and installing them. Setting up users. Specifying shared resources for each node. See Managing Shared Resource Definitions on page 114. Defining Environments. Registering keystores. Before You Begin Before you set up the runtime. and Permissions on page 137. It also specifies the interactions with enterprise applications outside the ActiveMatrix platform. Groups. and permissions.Life Cycle of the ActiveMatrix Runtime 7 | Life Cycle of the ActiveMatrix Runtime After you have created and started the servers and connected the Management Daemon process on machines you want to use. groups. you are ready to configure and start the TIBCO ActiveMatrix runtime and deploy services to it. • • Environment configuration involves the following activities: • • Configuring Messaging Bus settings and setting up the messaging server or servers for each environment. TIBCO ActiveMatrix Administration • . ensure that you have a clear deployment plan. See Managing Users. you use the ActiveMatrix Administrator user interface to configure enterprise assets and define and configure one or more environments on those machines. See Working with Nodes on page 188 and Working with Containers on page 202. See Managing Keystores on page 156. and what physical resources are needed by the service units that are deployed to the various containers. See Defining Environments on page 169. These enable the services deployed in each node’s containers to connect with physical resources as required. Each shared resource points to a shared resource definition for connection details. See Configuring Messaging Bus on page 174. Groups.

Configuring the service assembly. Deployment involves the following activities: • • Uploading a service assembly archive. The objects are installed onto machines that have been bound to the ActiveMatrix Administrator cluster. You may define a node. installed. This involves determining on which nodes the service assembly’s service units will be deployed and which shared resources to use for the shared resource profiles specified in the service units. Then Install When you are configuring an environment’s nodes and shared resources you first define each object and then you install it. As needed. The definitions persist even if you uninstall an installed object. This way you can ensure that your runtime is working as expected at each step. install it. you can also override substitution variables set in the service assembly archive. The object definitions are stored in the database. install. Deploying the service assembly. Starting the service assembly. You can later reinstall it as needed. See Working with Nodes on page 188 and Working with Containers on page 202 for related procedures. Deploying Service Assemblies After you have configured. Then change the definition as required. and then start it to ensure that it is running correctly. Two-Step Configuration: First Define.8 | Chapter 1 TIBCO ActiveMatrix Administrator Overview The indirection introduced by shared resources enables you to control use of the physical resource at the node level (after deployment). Starting Installed Nodes You can define. Before you can deploy a service assembly. and started the nodes. you are ready to deploy. first uninstall it. See Working with Shared Resources on page 207. the nodes and containers that service units will deploy into must be running. • • TIBCO ActiveMatrix Administration . then start them all. and installed the shared resources you need in each node. Or you can define several nodes. and install it again. and start nodes following different practices to suit your needs. Before you can change the definition of an installed object.

for example. Deploying Service Assemblies. deploying into different nodes. see TIBCO ActiveMatrix Composite Editor User’s Guide and TIBCO ActiveMatrix Service Grid Component Developer’s Guide product. TIBCO ActiveMatrix Administration . Two-Step Deployment: First Configure.Life Cycle of the ActiveMatrix Runtime 9 | You can upload and deploy multiple service assemblies. For more details on the design-time activities whose output is the service assembly. or into a different environment. configuring the service assembly differently in each case. See Chapter 8. you configure it before deployment. You can upload multiple service assembly archives and configure each of them. you perform life cycle management on the nodes and containers and service assemblies as required. configuring it for different deployment needs each time. and continue to make configuration changes as the runtime develops over time. on page 215 for details on these activities. Life Cycle Management After this point. You can then start and stop each one separately. and you can upload one service assembly multiple times. You can also upload the same service assembly archive multiple times. providing each one with a unique service assembly name. Then Deploy After you upload a service assembly archive. You save each configuration with a different service assembly name. as needed. You can start and stop each service assembly separately.

TIBCO ActiveMatrix Administration . and references do not explicitly contain connection details. services. The profiles may then bound to shared resources or may be left unbound. 5. If a shared resource definition is enabled for a node after the node is started. See Working with Shared Resources on page 207. 4.10 | Chapter 1 TIBCO ActiveMatrix Administrator Overview Shared Resource Life Cycle Shared resources provide connection details for specific physical resources used by services. Enable shared resource definitions in an environment. and references. shared resource profiles are mapped to shared resources available on the nodes on which the assembly will be deployed. When the service assembly is configured for deployment. component. See Working with Shared Resource Definitions on page 186. You create a node’s shared resources from shared resource definitions defined at the enterprise assets level. Upload service assembly. The life cycle of shared resources and the interaction of the life cycle with service assembly deployment is: 1. See Mapping Shared Resource Profiles to Shared Resources on page 234. components. a composite or component developer specifies a shared resource profile that declares the types of physical resources the service. Create shared resource definitions in enterprise assets. See Managing Shared Resource Definitions on page 114. you must manually install the shared resource in the node. shared resources are installed in the node for each enabled definition. Map shared resource profiles to shared resources. 3. 2. If a node to which you have mapped the service assembly is missing shared resources that you have specified in the mapping between shared resource profiles and shared resource. Instead. or reference require. When you start the node. During development. See Uploading a Service Assembly on page 218. components. If a shared resource definition required by the service assembly is not present in the environment. you can import shared resources defined in the service assembly to the enterprise and environment when you upload a service assembly. Enable shared resource definitions in a node. you can add them to the node.

override the port property value for each node. Depending on your requirements (multiple nodes on one machine or multiple nodes on multiple machines or a mixture of both). If the nodes are running on the same machine. If the nodes run on the same machine. • TIBCO ActiveMatrix Administration . However. the HTTP server shared resources on each node must use different port numbers to avoid conflicts. An HTTP server shared resource must be available on all nodes where that SOAP service runs. because a single HTTP server shared resource definition is used to create the shared resource. the shared resource profile is mapped to exactly one shared resource of type HTTP server.Shared Resource Life Cycle 11 | Customizing HTTP Shared Resource Definitions At design-time. override the hostname property value for each node. The solution is to use a template shared resource definition that can be customized for each node. the HTTP server shared resources on each node must use a different host name. Suppose you want to run this SOAP service on multiple nodes for load balancing or fault tolerance or both. A template shared resource definition has at least one property bound to a substitution variable. The nodes may be running on one machine or across multiple machines. When the service assembly is configured for deployment. but can be overridden at the node level. If the nodes run on different machines. when configuring the definition you cannot explicitly specify the hostname and port number variations required to run it on multiple nodes. Substitution variables are constants specified at the enterprise level. often the resource that was imported. When the service assembly containing the resource is uploaded the shared resource is imported into the enterprise as an HTTP server shared resource definition. you bind the hostname and port properties to substitution variables in the shared resource definition and customize the substitution variables per node as follows: • If the node is running on a different machine than the value specified in the shared resource definition. This constraint can lead to scalability limitations. a service with a SOAP binding uses a HTTP shared resource profile which is mapped to an HTTP shared resource.

12 | Chapter 1 TIBCO ActiveMatrix Administrator Overview TIBCO ActiveMatrix Administration .

Topics • • • • ActiveMatrix Database Server. other administrators may be responsible for some or all the servers. page 17 TIBCO Enterprise Message Service™ Server. In a production environment.| 13 Chapter 2 Infrastructure Servers This chapter discusses the infrastructure servers that must be running in order for the ActiveMatrix runtime to be operational. page 22 TIBCO Administrator™ and TIBCO Hawk®. page 23 TIBCO ActiveMatrix Administration . ActiveMatrix administrators may be responsible for all these servers. page 14 TIBCO Management Daemon. however. In a development or test setting.

The sa user has DBA privileges by default. All new datastores use the following default user credentials: username sa and no password. Setting up the Database Server Setting up HSQLDB You can use the HSQLSDB database server provided with ActiveMatrix products. not the system tables) in an Oracle. Database Overview This section describes how to set up and start the ActiveMatrix database server. you specify a datastore name. Setting up Oracle. One database (datastore). is available without any prior setup. If you use the provided database with the default user credentials. To add users to HSQLDB or change existing user attributes. follow the procedure described in Creating a New HSQLDB Datastore on page 15. When you complete the Database Details dialog during ActiveMatrix Administrator server creation. you can use a client tool such as DBVisualizer.14 | Chapter 2 Infrastructure Servers ActiveMatrix Database Server The ActiveMatrix database server maintains ActiveMatrix administration data. You specify the user and database information in the Database Details dialog during installation. ensure that you have the credentials of a user with connect and resource privileges to user-defined tables. TIBCO ActiveMatrix Administration . Before you create the ActiveMatrix Administrator server. You must start the database server before creating or running an ActiveMatrix Administrator server (see ActiveMatrix Administrator Server on page 25) or creating or starting an ActiveMatrix node (see Working with Nodes on page 188). amx. or Sybase database. SQL server. or Sybase Each cluster requires exclusive use of user-defined tables (that is. To create a another datastore. SQL Server. you do not have to do any setup ahead of time.

HSQLDB Database This section describes how to start the HSQLDB database server and how to create a new HSQLDB datastore. You can use the HSQLDB database provided with ActiveMatrix software.dbname.database. select All Programs > TIBCO > TIBCO ActiveMatrix > Start HSQLDB Server Windows or UNIX From the command line./data/amx server..silent=true server. The first line specifies location of the data files for the datastore..port=1234 server. you specify this datastore name. To start the HSQLDB database server.trace=false TIBCO ActiveMatrix Administration . It shows two lines added for a datastore called acme: #database connection url would be 'jdbc:hsqldb:hsql://localhost:<server. When you create an ActiveMatrix Administrator server.dbname.0=amx server.properties file. Starting the HSQLDB Database Server The HSQLDB database server stores environment configuration data. or another supported database.port>/<server.0=. To start the HSQLDB server. The second line specifies the datastore name. Here is an example properties file. To do this you create a datastore for each cluster by adding two lines in the server. run AMX_HOME/hsqldb/bin/amx-db.ActiveMatrix Database Server 15 | Starting the Database Server You must start your database server before you start the ActiveMatrix Administrator server creation wizard. Creating a New HSQLDB Datastore You can serve multiple ActiveMatrix Administrator clusters using one HSQLDB database server. consult your database product documentation for the procedure.dbname. If you are using a third-party database product. See the installation manual for your product for details on which database products are supported.database. follow the procedure in Starting the HSQLDB Database Server on page 15. do one of the following • • Windows From the Start menu./dataAcme/acme server.0>' server.1=.1=acme server.

/Filepath/DbName server. and To Create a New HSQLDB Datastore 1. TIBCO ActiveMatrix Administration . Save the file.n specifies the location of the directory that holds the datastore’s data files and the prefix for the data file names.properties.16 | Chapter 2 Infrastructure Servers Note that the number is incremented to 1 in both lines. Use the same number for each pair of lines used to define a datastore’s properties.lck. the directory is AMX_HOME/hsqldb/dataAcme and the data files in that directory are acme.. acme.properties 2. acme.. if you specify .n=DbName 3.database. the number must be different for each datastore. For each datastore. Open the following file for editing: AMX_HOME/hsqldb/bin/server. The directory path is relative to the installation directory of the database server.database. Specifying the Location of the Datastore Data Files The value of the line server./dataAcme/acme. For example. add a section (as explained in the introduction) using the following format: server.log..n=.dbname.

Open Control Panel > Administrative Tools > Services. Right-click the service TIBCO Management Daemon 2. ********************* ActiveMatrix Daemonlet Started ********************* Due to a limitation of JDK 1.launch. Starting TIBCO Management Daemon To start Management Daemon. to fine tune the configuration of the UDP listening port by following the instructions in the next section. When the Management Daemon process starts up. • Windows or UNIX From the command line. b. run ENV_HOME/managementdaemon/2. you may observe exceptions on the Management Daemon console for interfaces that are not connected. The Management Daemon process on each machine running ActiveMatrix software must be running at all times.0 and select Start. TIBCO ActiveMatrix Administration . Management Daemon broadcasts on all available network interfaces on the machine.0 > Management Daemon You can also start the Management Daemon Windows service as follows: a.Activator main INFO: TIBCO Launch Activator launched at 10/26/07 5:18 PM. how to configure ports that it listens on.TIBCO Management Daemon 17 | TIBCO Management Daemon TIBCO Management Daemon software bootstraps the management infrastructure and supports node life cycle operations.neo. Machine names having underscore "_" characters in their hostname are not supported by TIBCO Management Daemon. and how to configure status reporting and polling intervals.tibco. which indicate the connected interfaces. You can ignore the exceptions or use the error messages. 2007 5:18:35 PM com. select All Programs > TIBCO > ENV_NAME > TIBCO Management Daemon 2.osgi. This section describes how to start the TIBCO Management Daemon process.0/bin/managementdaemon The last lines of the output are similar to the following: Oct 26.5. do one of the following: • Windows From the Start menu.

100. • Discovery Port By default. TIBCO ActiveMatrix Administration . the port on which Management Daemon listens for node management requests is set to 9998.106. Management Daemon reads its port from its configuration file: ENV_HOME/managementdaemon/2. Management Port By default.107:port#interface interface is the name of the network interface to use in the multicast. to prohibit discovery.100. the port on which Management Daemon listens for JMX discovery requests is set to 9999. The address format can be: • • udp://239.106.5 implementation choose one.xml The information is located in the discoverySocketAddresses element.18 | Chapter 2 Infrastructure Servers UDP.107:1965</string> </list> There can be multiple items in the list. Management Daemon multicasts on all network interfaces.100. The discovery policy can be ALWAYS. and Management Ports UDP Listening Port By default. and any errors are logged as SEVERE. or NEVER. That is. For example: <string name="discoveryJMXAddress"> service:jmx:jmxmp://Hostname:9999 </string> <string name="discoveryPolicy">ALWAYS</string> where Hostname is the hostname of the machine running the Management Daemon process. udp://239. In many cases this works as expected. The JMX discovery URL is set in the discoveryJMXAddress element.107:port#* The wildcard fragment instructs Management Daemon to multicast on the default network interface. to enable discovery. For example: <list name="discoverySocketAddresses"> <string>udp://239. udp://239.106. it does not specify a network interface and lets the JDK 1.107:port With no fragment.0/config/configuration. the port on which the Management Daemon processes listen for requests sent using the UDP protocol is set to 1965. Discovery.106.100.

txt file in a text editor. TIBCO ActiveMatrix Administration . if you know that software inventory on machines do not change very often.TIBCO Management Daemon 19 | The JMX management port is set in the managementAddress element. For example: <string name="managementAddress"> service:jmx:jmxmp://Hostname:9998 </string> Changing the Port Values To change the default port values used by Management Daemon: 1. Changing Management Daemon Status Reporting and Polling Intervals You can change Management Daemon status reporting and polling intervals to suit your requirements. — Discovery Port set discoveryJMXAddress service:jmx:jmxmp://Hostname:Port — Management Port set managementJMXAddress service:jmx:jmxmp://Hostname:Port 3. 2. in nonproduction environments.0/bin/managementscript. you may not need very up-to-date status on nodes and daemons. Add the appropriate commands before the exit command: — UDP Listening Port clear discoverySocketAddresses add discoverySocketAddress address where address is in one of the formats described in UDP Listening Port on page 18. so you would increase the value of the nodePollingInterval and daemonStatusInterval properties. on the other hand. For example. Run ENV_HOME/managementdaemon/2.0/managementscript. you can set a large interval for inventory polling to save some processing power on the machines. On the other hand. In a mission-critical production environment. Open the ENV_HOME/managementdaemon/2. you may want to get status updates every 15 seconds instead of the default of 30 seconds.

They report directly to the ActiveMatrix Administrator servers. In a production system where software is not installed or uninstalled very often. Set the interval according to how critical it is to know the current node state. TIBCO ActiveMatrix Administration . you can set this interval to a very large number. it updates the databases of all ActiveMatrix Administrator servers bound to the machine on which it is running. Node Polling Interval A Management Daemon process uses JMX to ping all nodes on the machine and report if they are alive. The server databases therefore hold accurate information about containers and installed software. It is strongly recommended that you set the interval to 20 seconds or more. Editing the Reporting and Polling Intervals You edit the intervals for each Management Daemon process in a configuration file in the Management Daemon installation directory.20 | Chapter 2 Infrastructure Servers Status Reporting Interval Management Daemon processes report the status of the nodes installed on their machines to all the ActiveMatrix Administrator servers. To configure this polling interval. edit the nodePollingInterval property. To configure the interval between each ping. Intervals of less than 20 seconds can result in performance degradation. The file is created after you bind the machine on which the Management Daemon process running to an ActiveMatrix Administrator cluster and associate the machine with an environment. They also report status of the Management Daemon process itself. edit the inventoryPollingInterval property. Inventory Polling Interval A Management Daemon process periodically checks (polls) the local file system for the following changes: • • Addition of new containers and removal of existing containers Installation of new versions of installed products or uninstallation of existing products When a Management Daemon process encounters such a change.

org/XMI" xmlns:mgmtdaemonmodel="http://xsd.0" encoding="ASCII"?> <xmi:XMI xmi:version="2.com/matrix/models/mgmt daemonmodel"> <mgmtdaemonmodel:ManagementDaemonStore adminClusterDetails="/1" inventoryPollingInterval="30000" nodePollingInterval="30" daemonStatusInterval="30" pluginPollingInterval="30000"/> <mgmtdaemonmodel:AdminClusterDetails dbDriver="org.matrix. Other time units are seconds. 3.hsqldb. Locate the entries whose interval you want to change and change them as desired.tns. Example <?xml version="1.TIBCO Management Daemon 21 | To Change the Reporting and Polling Intervals 1. TIBCO ActiveMatrix Administration .tibco.xmi 2. Save the file.jdbcDriver" dbURL="jdbc:hsqldb:hsql://hostname:1234/amx" clusterName="amx"> <dbCredentials username="sa" password=""/> </mgmtdaemonmodel:AdminClusterDetails> </xmi:XMI> The time unit for inventoryPollingInterval is milliseconds.tibco.omg.0" xmlns:xmi="http://www. open the following file for editing: ENV_HOME/managementdaemon/2. On the machine running the Management Daemon process.0/daemonlets/com.dae monlet/amxdaemonlet.

Right-click TIBCO EMS Server and select Start. Using Log and Monitoring services. • You can choose to use the same Enterprise Message Service server for all of these operations. on page 239. run TIBCO_HOME/ems/bin/tibemsd. on page 293 and Chapter 9. See Starting and Stopping Nodes on page 193. Select All Programs > Administrative Tools > Services. See Creating a Shared Resource Definition on page 114. See Chapter 10.22 | Chapter 2 Infrastructure Servers TIBCO Enterprise Message Service™ Server ActiveMatrix software uses TIBCO Enterprise Message Service server for the Messaging Bus communications backbone. To start the messaging server or servers do one of the following: • Windows From the Start menu. For information on installing and configuring the server. Viewing statistics about or logs from a node is dependent on these two services. This section describes how to start the Enterprise Message Service server. select All Programs > TIBCO > TIBCO EMS version > Start EMS Server The Enterprise Message Service server is installed as an Windows service. Monitoring Infrastructure and Services. Starting the TIBCO Enterprise Message Service Server TIBCO Enterprise Message Service is the messaging backbone for the ActiveMatrix runtime. You can create and start TIBCO ActiveMatrix Administrator before running the Enterprise Message Service server. Managing Logging. The Enterprise Message Service server must be running before invoking the following operations: • • Starting a node. so you can also start the server as follows: a. see TIBCO Enterprise Message Service product documentation. TIBCO ActiveMatrix Administration . Testing the connection when creating a JMS shared resource definition. b. • Windows or UNIX From the command line.

see TIBCO Administrator product documentation.exe TIBCO ActiveMatrix Administration . Useful information is written to a command window when you start the services in this way. This section describes how to start the TIBCO Administrator server and TIBCO Hawk agent. To start the services on Windows. Starting TIBCO Administrator and TIBCO Hawk When you use a TIBCO Administrator authentication realm. You can also start the TIBCO Administrator and TIBCO Hawk services using the command-line versions of these services. To stop a service. the TIBCO Administrator server and TIBCO Hawk agent for your domain must be running. For information on how to configure TIBCO Administrator to be an ActiveMatrix Administrator authentication realm see Creating a TIBCO Administrator Authentication Realm on page 33. Repeat for the TIBCO Hawk Agent (domain) entry. Find the entry for TIBCO Administrator version (domain) and click Start. For complete information on configuring TIBCO Administrator. close its window.exe To start TIBCO Hawk agent at the command line.TIBCO Administrator™ and TIBCO Hawk® 23 | TIBCO Administrator™ and TIBCO Hawk® TIBCO Administrator and TIBCO Hawk are required only if you authenticate ActiveMatrix users using a TIBCO Administrator authentication realm. To start TIBCO Administrator server at the command line. run the following: TIBCO_HOME/tra/domain/domainName/bin/hawkagent_domainName. you can use the Services dialog. run the following: TIBCO_HOME/administrator/domain/domainName/bin/tibcoadmin_domainName.

24 | Chapter 2 Infrastructure Servers TIBCO ActiveMatrix Administration .

page 31 Database Configuration. Topics • • • • • Creating the First ActiveMatrix Administrator Server. and default runtime node. configure the authentication realm. page 59 Starting and Stopping the ActiveMatrix Administrator Server. page 60 TIBCO ActiveMatrix Administration . and start and stop the ActiveMatrix Administrator server. page 26 Authentication Realm Configuration. database. page 47 Default Runtime Node Configuration.| 25 Chapter 3 ActiveMatrix Administrator Server This chapter explains how to create the first ActiveMatrix Administrator server in a cluster.

If you are using a TIBCO Administrator authentication realm for your cluster perform the tasks described in Creating a TIBCO Administrator Authentication Realm on page 33 before starting the ActiveMatrix Administrator server creation utility. it can be started as part of the installation process. The same database server can be used for the authentication realm. on page 335. The ActiveMatrix Administrator server creation utility cannot connect to the database if a firewall is running on your machine. For information on authentication realms. if you are using a database for authentication. Database. see Appendix A. Start the ActiveMatrix Administrator cluster database server. Before Running the ActiveMatrix Administrator Server Creation Utility Before running the ActiveMatrix Administrator server creation utility you must do the following: • Decide whether you want to secure the communication channels between ActiveMatrix components. All ActiveMatrix Administrator servers in the same cluster must use the same authentication realm. You can also configure a different database server for use with the cluster.26 | Chapter 3 ActiveMatrix Administrator Server Creating the First ActiveMatrix Administrator Server This section describes how to create the first ActiveMatrix Administrator server in a cluster using the ActiveMatrix Administrator server creation utility. Doing so allows you to run ActiveMatrix with a database user that has minimum privileges. or LDAP. • Choose an authentication realm: Local XML File. The firewall must be disabled before running the utility. Pre-creating Database Tables by Running DDL Scripts You can pre-create the ActiveMatrix schema (database tables) before running the ActiveMatrix Administrator server creation utility. see Authentication Realm Configuration on page 31. See Pre-creating ActiveMatrix Schema on page 52 for details. • TIBCO ActiveMatrix Administration . TIBCO Administrator. If you plan to use the packaged HSQLDB database. For detailed instructions on how to configure the components. Once you have created the first Administrator server you can use the ActiveMatrix Administrator graphical interface (see Creating an ActiveMatrix Administrator Server on page 163) to create additional servers. Securing TIBCO ActiveMatrix Communication Channels.

and then run ActiveMatrix Administrator server creation utility using a database account with no permissions to create database tables. Create the database schema for all tables the same. TIBCO ActiveMatrix Administration . you can run the utility in interactive mode. In all modes you provide configuration details following the guidelines in the sections: — Database Configuration on page 47 — ActiveMatrix Administrator Configuration on page 29 — Authentication Realm Configuration on page 31 — Database Configuration on page 47 — Default Runtime Node Configuration on page 59.Creating the First ActiveMatrix Administrator Server 27 | If you are using Microsoft SQL Server and have pre-created the database tables by running DDL scripts generated with dbscriptgenerator. for example db_owner and the same schema must be set as the default schema for the database user provided in the JDBC parameters in the ActiveMatrix Administrator server creation utility. console mode. or silent mode. If you are using Sybase as the TIBCO ActiveMatrix Administrator database you can run the utility only in silent mode. If you do not run the utility during installation. For example: Running the ActiveMatrix Administrator Server Creation Utility During installation you are prompted to run the ActiveMatrix Administrator server creation utility to create the first server. you must: • • Create the administration server cluster table with an upper case name AMXADM_CLUSTER_NAME_IN_CAPS.

Run passwordobfuscator. the utility does not prompt for any inputs.2/bin/. From the command line. Values for password fields can either be entered as clear text or as obfuscated passwords (see Creating an Obfuscated Password) using .properties. The properties file must specify all the properties you would provide to the wizard. The directory contains the sample properties file createadminserver.2/bin/. the inputs are read from a properties file provided as a command-line parameter.2/bin/. From the command line. run createadminserver. the utility prompts for input in a series of dialogs. To create an obfuscated password: 1. To run the utility in silent mode: Windows or UNIX Change directory to AMX_ADMIN_HOME/2. From the command line. Console Mode In console mode. the utility prompts for input in the command window. To run the utility in GUI mode: Windows From the Start menu. Instead. Creating an Obfuscated Password The password obfuscator obfuscates passwords two encryption algorithms: TIBCO or Platform Server.2/bin/.28 | Chapter 3 GUI Mode ActiveMatrix Administrator Server In GUI mode. select All Programs > TIBCO > TIBCO ActiveMatrix > Administrator Server Creation Wizard Windows or UNIX Change directory to AMX_ADMIN_HOME/2. run: createadminserver -console Silent Mode In silent mode. You must replace the variable @HOSTNAME@ in this file with your hostname and edit values for other parameters as needed. run createadminserver -silent propertiesFilePath. To run the utility in console mode: Windows or UNIX change directory to AMX_ADMIN_HOME/2. Change directory to AMX_ADMIN_HOME/2. 2. TIBCO Encryption Syntax: passwordobfuscator password Example: passwordobfuscator tibco TIBCO ActiveMatrix Administration .

A cluster name is required even if you do not plan to add more servers to the cluster. contained in brackets: [#!LjNSm/lIwW7uwiLvcZQwuA==] Platform Server Encryption Syntax: passwordobfuscator -p username password Example: passwordobfuscator -p root tibco ActiveMatrix Administrator Configuration Table 3 on page 29 describes the fields that define the ActiveMatrix Administrator cluster and server. See Authentication Realm Configuration on page 31. Table 3 ActiveMatrix Administrator Reference Field Server Name Description A name to identify the server. TIBCO ActiveMatrix Administration . LDAP. TIBCO Administrator. Default: admin Cluster Name A name to identify the cluster. The name must be less than 23 characters long and can contain only alphanumeric and underscore (_) characters. Database. A name must be a valid directory name in Windows or UNIX operating systems. Default: 8120 Management Port Port on which the ActiveMatrix Administrator server for node management and control functions using JMX protocol. Default: amx HTTP Port Port on which the web container that hosts the ActiveMatrix Administrator user interface listens.Creating the First ActiveMatrix Administrator Server 29 | Output: Encrypted password. A name must be a valid directory name in Windows or UNIX operating systems. Default: 8110 Authentication Realm The method of storing authentication information about users and groups: Local XML File. The name must be unique among servers on the machine. The name must be less than 23 characters long and can contain only alphanumeric and underscore (_) characters.

30 | Chapter 3 ActiveMatrix Administrator Server Deleting the ActiveMatrix Administrator Windows Service On Windows. on Windows for a cluster named amx and ActiveMatrix Administrator server named admin: 1. Run deleteadminserver .xml file./data/cluster_server. TIBCO ActiveMatrix Administration . you delete the ActiveMatrix Administrator Window service by invoking the deleteadminserver utility against the AMX_ADMIN_HOME/data/cluster_server. A DDL (Data Definition Language) user must manually remove the tables from the database... 2. For example. Change directory to AMX_ADMIN_HOME/2./. the deleteadminserver utility does not drop the tables from the database because the DML user does not have sufficient privileges. The database server used by the ActiveMatrix Administrator server must be running. If the ActiveMatrix Administrator server creation utility was run by a DML (Data Manipulation Language) user.xml.2/bin/.

Local XML File Realm is an appropriate choice for demonstration installations and other non-production uses. There is one screen to configure the Local XML File Realm: • Local XML File Realm Table 4 Local XML File Realm Reference Field Username Password Description The username root. xml in a text editor. You must use the same password for all servers in a cluster. see Updating the Authentication Realm on page 44.Authentication Realm Configuration 31 | Authentication Realm Configuration When you configure the first ActiveMatrix Administrator server in a cluster you specify an authentication realm. Local XML File Realm on page 31 Adding a User to a Local XML File Realm To add a new user (user1) to a local XML file realm: 1. A password of your choice. All servers in the same ActiveMatrix Administrator cluster use the same authentication realm. Open the file AMX_ADMIN_HOME/data/clustername/servername/config/system-security. For reference information for each type of realm supported by ActiveMatrix Administrator see the sections: • • • • Local XML File Realm on page 31 TIBCO Administrator Realm on page 32 Database Realm on page 35 LDAP Realm on page 39 Local XML File Realm When you use the local XML file realm. TIBCO ActiveMatrix Administration . For a description of how to change the authentication realm after you have created the first server in a cluster. one username—root—and a password of your choice is stored in a local file.

You also specify a file-based location of the certificate. One TIBCO administration domain and one certificate can be shared by all ActiveMatrix Administrator clusters in your enterprise.2/bin/. 6. When you create the ActiveMatrix Administrator server.32 | Chapter 3 ActiveMatrix Administrator Server 2. all users who can authenticate to this TIBCO Administrator domain can also authenticate to the ActiveMatrix Administrator servers you create. 5. users are authenticated against the HTTPS-enabled TIBCO Administrator domain shared by every server in a cluster. 3. which can be either a self-signed or third-party certificate. Run cluster_server -uploadconfig. The final step is to add the ActiveMatrix Administrator user credentials to the TIBCO Administrator domain.xml file. As a result of the setup. Add the new user and password under the <users> tag within a <user> tag. <users> <user> <name>root</name> <password>toiP3D2RYKw=</password> </user> <user> <name>user1</name> <password>297SLWvlCAY=</password> </user> <user> <name>guest</name> <password>30ojcikAopk=</password> </user> </users> <group-mapping> <group-name>administrator</group-name> <user-name>root</user-name> <user-name>user1</user-name> </group-mapping> 4. Create an obfuscated password for the new user using the -p option (see Creating an Obfuscated Password on page 28). TIBCO Administrator Realm When you use the TIBCO Administrator realm. Change to the directory AMX_ADMIN_HOME/2. Save and exit the system-security. Full details about how to add users to the TIBCO Administrator domain are provided in that product’s documentation. Users and groups in this realm can only be edited with TIBCO Administrator user management tools. you provide the authority URL for the TIBCO Administrator server and the credentials for the domain superuser. TIBCO ActiveMatrix Administration . You can optionally add the user to a group using the <group-mapping> tag.

4. select Domain Configuration > Create a new administration domain. select Domain Configuration > Enable HTTPS. A list of all certificates and their alias names displays (followed by the date). In the Server Settings dialog. 2.Authentication Realm Configuration 33 | Creating a TIBCO Administrator Authentication Realm This section explains how to create a TIBCO Administrator authentication realm for use by ActiveMatrix Administrator servers. Install a supported version of TIBCO Administrator software on a machine or use an existing installation.) Select the domain and provide the superuser credentials. See TIBCO ActiveMatrix Service Grid Installation for supported versions of required hardware and software. select the appropriate option to suit your needs: Self Signed Certificate. In the HTTPS Configuration dialog. (At the Select a Task dialog. (At the Select a Task dialog. Using Domain Utility. execute this command: keytool -keystore KeystoreFile -list When prompted for the password. Click Next. or a Third Party Certificate option. The username and password you enter for the domain are the superuser credentials. At the command line. Domain Utility performs various tasks and creates a keystore in the location: TIBCO_HOME/tibco/administrator/domain/DomainName/SSL/keystore Task B Extract the Certificate with Keytool 1.) This domain is for use by the ActiveMatrix Administrator cluster (or clusters). use Domain Utility to create a domain. provide the server certificate details. In the Server Certificate dialog. Task A Create an HTTPS-enabled TIBCO Administrator Domain 1. TIBCO ActiveMatrix Administration . enable HTTPS. a. Note the alias name of the certificate for use in the next step. 3. c. Open a command window and navigate to the following directory: TIBCO_HOME/tibco/administrator/domain/DomainName/SSL/ 2. enter the port numbers or accept the defaults. On the machine where you installed TIBCO Administrator. b. Also enter the username and password for the keystore. enter changeit (the default) or the current password value.

34 | Chapter 3 ActiveMatrix Administrator Server 3. and HTTPSPort is the HTTPS port you defined in the Domain Utility Server Settings dialog.cer KeystoreFile -export -alias AliasName -file The certificate is exported to the file filename. where Hostname is the URL you use to login to the TIBCO Administrator GUI. At the command line. The superuser password defined for the TIBCO Administrator domain. The format of the URL is Hostname:HTTPSPort. Configuring the TIBCO Administrator Authentication Realm There is one screen to configure the TIBCO Administrator Realm: • TIBCO Administrator Realm Reference on page 34. The client certificate file. 4. execute this command: keytool -keystore filename. Default: localhost:8080 Note that the default port in Domain Utility is 8443. Table 5 TIBCO Administrator Realm Reference Field Authority URL Description The URL used to log in to TIBCO Administrator. TIBCO ActiveMatrix Administration . Click Browse to locate and select the file you specified in step 4 in the preceding section.cer in the SSL directory. Username Password Client Certificate The superuser username defined for the TIBCO Administrator domain. Put the certificate in a file system location accessible to the machine on which you run the ActiveMatrix Administrator server.

There are two screens to configure the Database Realm: • • Database Realm on page 36 Database Authentication Superuser on page 37 TIBCO ActiveMatrix Administration .Authentication Realm Configuration 35 | Database Realm When you use the database realm. For information on how to enable secure connections to Oracle database servers. TIBCO ActiveMatrix supports secure access to Oracle databases. users and groups are declared in a database shared by every server in a cluster. You also have the option to use the same database for authentication data and ActiveMatrix administration data (see Database Configuration on page 47). Users and groups in this realm can be edited within ActiveMatrix Administrator. see Securing JDBC Connections on page 345.

jdbc.jdbc. Note: If you use localhost as the hostname. and database instance name (SID). you can only connect to Management Daemon processes running on the local machine. Default: jdbc:hsqldb:hsql://hostname:1234/amx.jdbcDriver For Oracle: tibcosoftwareinc.hsqldb.sqlserver. and database instance name (databaseName). TIBCO ActiveMatrix Administration . You can select from a list of supported drivers. the Database URL field is populated with a template for the URL of the driver. For HSQLDB the template is: jdbc:hsqldb:hsql://<hostname>:<portnumber>/amx You must supply the hostname and port number. Username A name for the database user. For Microsoft SQL Server. Default: sa. port number.SQLServerDriver Default: org.oracleOracleDriver For Microsoft SQL Server: tibcosoftwareinc.databaseNam e=<databaseName> You must supply the hostname. the template is: jdbc:tibcosoftwareinc:sqlserver://<host>:<port>. A template of the URL is supplied for the selected JDBC driver.36 | Chapter 3 ActiveMatrix Administrator Server Database Realm Table 6 Database Realm Reference Field Database Driver Description The name of the JDBC driver class.jdbcDriver. the template is: jdbc:tibcosoftwareinc:oracle://<host>:<port>. For Oracle. For HSQL: org. When you select a driver.hsqldb. Database URL The URL to use to connect to the database.SID=<SID> You must supply the hostname. You must supply the portions of the URL shown between angle brackets and remove the angle brackets. port number.

The database is an existing user database populated with users. Database Authentication Superuser The Database Authentication Realm User screen allows you to specify an ActiveMatrix Administrator user. in which case the user is added. A user added through this screen is automatically a superuser. You enter a username and password. Click the text box and type the password. it is ignored. The lack of visibility of the text box does not affect the function. leaving all the fields empty. Note: On 64 bit Linux the password text box for the database authentication realm screen in the Administrator Server Creation Wizard is not rendered. TIBCO ActiveMatrix Administration . Default: 30 seconds. There are two cases that can occur: • • The database has no users. or you can also choose to enter a new username and password.You can skip the Database Authentication Realm User screen. Max Connections Maximum number of simultaneous connections to the database that can be open. A user is added to the user database. Default: 5 Login Timeout Amount of time in seconds allowed for login before giving up the attempt.Authentication Realm Configuration 37 | Table 6 Database Realm Reference (Cont’d) Field Password Description A password for the database user. See Superusers on page 138. If an existing username is entered.

Create build.xml files with the appropriate action. Restart all ActiveMatrix nodes and ActiveMatrix Administrator servers. For example: Table 7 Database Realm Authentication Superuser Reference Field Username Password Confirm Password Description A name for an ActiveMatrix superuser. the database authentication realm user specified must have the db_owner permission set.38 | Chapter 3 ActiveMatrix Administrator Server If you are using Microsoft SQL Server. and username and obfuscated password (see Creating an Obfuscated Password on page 28). Run the command-line. 3. 2. To update bootstrap credentials: 1.xml and datafile. The password provided in the Password field. If you want to update the database realm superuser credentials after running the ActiveMatrix Administrator server creation utility. A password for an ActiveMatrix superuser. TIBCO ActiveMatrix Administration . you use the ActiveMatrix Administrator command-line interface (see ActiveMatrix Administrator Command-Line Interface on page 77).

xml <BootStrapUser username="username" password="password"/> LDAP Realm When you use the LDAP authentication realm. TIBCO ActiveMatrix supports secure access to LDAP servers.xml <target name="edit_bootstrapUser"> <AMXAdminTask .. There are four screens to configure the LDAP realm: • • • • LDAP Realm on page 40 Search on page 40 LDAP Mapping on page 42 Superuser Registration on page 42 TIBCO ActiveMatrix Administration . action="edit" dataFile="datafile.xml" objectSelector="AdminCluster/BootStrapUser" overwrite="true" merge="true" createIfNotExists="true" fore="true" failOnError="true"/> </target> datafile.Authentication Realm Configuration 39 | For example: build. For information on how to enable secure connections to LDAP servers.. To use non-default LDAP attributes as usernames. users and groups are managed by an LDAP server shared by every server in a cluster. see Enabling Secure Connections to LDAP Servers on page 351. see Configuring LDAP Attributes as Usernames on page 42. Users and groups in this realm can only be edited with LDAP server management tools. The LDAP server must be running before configuring it for the ActiveMatrix Administrator server.

If the Base DN to search users and Base DN to search groups is the same (that is. see Enabling Secure Connections to LDAP Servers on page 351. Default: com. Strong. Default: Simple Search In the search screen you provide user and group configuration details. A strong authentication mechanism requires you to possess a Public Key Certificate (PKC).ldap. For example. Default: Unchecked. or None. Authentication Type Authentication type to be used for connection to LDAP Server. enter more specific LDAP queries that differentiate users and groups for the Search Filter for Users and Search Filter for Groups parameters.40 | Chapter 3 ActiveMatrix Administrator Server LDAP Realm Table 8 LDAP Realm Reference Field Context Factory Description The factory object that provides the starting point for resolution of names within the LDAP server. For addition configuration requirements. Default: cn=Directory Manager Password Use SSL LDAP server password. the ActiveMatrix Administrator server can communicate with an LDAP Server over SSL. When checked. you enter: (&(objectClass=person)(uid=%U)) TIBCO ActiveMatrix Administration .LdapCtxFactory LDAP Server URL The URL used to log in to the LDAP server. This enables secure communication between the LDAP server and ActiveMatrix Administrator. One of Simple. if in Search Filter for Users.sun.jndi. users and groups are under the same tree node in the LDAP hierarchy). Default: ldap_server:port Username (Bind DN) The superuser's distinguished name or superuser's name to be used to connect to the server.

you enter: (&(objectClass=groupOfUniqueNames)(cn=%G)) The LDAP search query filter for users never matches groups.dc=com Search Filter for Users Filter to be used for searching a user. Base distinguished name from which the search for the group starts. An example for this filter is (OU=%G).dc=<--->. An example for this filter is (CN=%U). Use SubTree to search for the user in the subtree as well. Base DN to Search Groups TIBCO ActiveMatrix Administration . Default: ou=<--->. Specifies whether to search only under the Group base distinguished name or traverse into the subtree.dc=<--->. You can define any complex filter like (&(cn=%U)(objectClass=account)).Authentication Realm Configuration 41 | and in Search Filter for Groups. Table 9 Search Reference Field Base DN to Search Users Description Base distinguished name from which the search starts. '%U' is replaced by the username being searched for. Possible values for this are SubTree and OneLevel. Use OneLevel to search for the user immediately under the Base distinguished name. Here '%G' is replaced by the group name being searched at the runtime. This is a required condition. Possible values are OneLevel and Subtree. Default: (uid=%U) Search Scope for Users Scope for searching for the user. and the LDAP search query filter for groups never matches users.dc=com Default: The value in Base DN to Search Users. Default: (OU=%G) Search Scope for Groups Scope for searching the group. Search Filter for Groups Filter to be used for searching a group. ou=<--->.

The value for the Group attribute key with which the parent group is associated with this user/subgroup. Stop the ActiveMatrix Administrator server. Password for the user. TIBCO ActiveMatrix Administration . Table 10 LDAP Mapping Details Reference Field Group has User and Subgroup as its Attributes User/Subgroup has Group as Attribute User DN has Group Superuser Registration The LDAP user you provide becomes a superuser in ActiveMatrix Administrator. The Key name for the group in the user distinguished name. 2.xml. See Superusers on page 138. Existing ActiveMatrix Administrator Server To apply this configuration change to an existing ActiveMatrix Administrator server: 1. Edit the file: AMX_ADMIN_HOME/data/cluster/server/config/security-config. Configuring LDAP Attributes as Usernames When using an LDAP authentication realm by default the value of the CN attribute is used as the username. The attribute keys refer to the keys with which Users and Subgroups are associated with the Group. Table 11 Superuser Registration Reference Field Username Password Description Name of an existing user in the LDAP server to register as an ActiveMatrix superuser. Description The values for User and Subgroup attribute keys.42 | Chapter 3 ActiveMatrix Administrator Server LDAP Mapping Select one field and provide the mapping details. You can configure a different LDAP attribute (such as sAMAccountName in the case of Microsoft Active Directory) to display as a username in the Users tab of the Enterprise Assets perspective.

insert a new entry element and replace sAMAccountName in the example with your LDAP attribute name.. The UserFilter may also specify filter additional criteria (such as objectClass=person). <entry> <name>GroupUniqueAttribute</name> <value>sAMAccountName</value> </entry> Ensure that the GroupFilter uses the same attribute name as specified in GroupUniqueAttribute and if necessary change it in the existing XML entry.</name> <value>..</value> </entry> . </init-options> </user-manager> </realm> .. 6. <entry> <name>UserUniqueAttribute</name> <value>sAMAccountName</value> </entry> Ensure that the UserFilter uses the same attribute name as specified in UserUniqueAttribute and if necessary change it in the existing XML entry... insert a new entry element. This entry is optional.administration. If absent. change UserFilter from (CN=%U) to (sAMAccountName=%U). To specify a different attribute for username. then the leftmost attribute occurring in the DN (typically CN) is used for the group name. In the realm element. change GroupFilter from (CN=%G) to (sAMAccountName=%G). </security-service> 4.Authentication Realm Configuration 43 | 3. For example. If absent.tibco.. To specify a different attribute for group name.matrix. The GroupFilter may also specify additional filter criteria (such as objectClass=groupofuniquenames). add new entry subelements: <security-service> . then the leftmost attribute occurring in the DN (typically CN) is used for the username. and replace sAMAccountName in the example with your LDAP attribute name..TibcoLD APUserManager</class-name> <init-options> <entry> <name>. For example.. 5.. Locate the following entry and change the value from 1 (default value) to 10: TIBCO ActiveMatrix Administration . This entry is optional.util. <realm> <realm-name>system</realm-name> <user-manager> <class-name>com..server.

2/bin/cluster_server –uploadconfig The server starts. Updating the Authentication Realm Once you have created a cluster you may decide to change from one realm to another or to change realm properties. create the cluster using the createadminserver utility in silent mode (see Silent Mode on page 28).ldap. If you decide to change to another type of realm. and upgrades the ActiveMatrix Administrator server. stores the LDAP configuration changes to the database.group_unique_attribute to specify a different attribute for group name. Stop and restart the ActiveMatrix Administrator server without any parameters.realm.user_unique_attribute to specify a different attribute for username.ldap.user_unique_attribute=sAMAccountName cluster.ldap. enable (by deleting the '#' comment instruction from the beginning of the lines). the current bootstrap user of the ActiveMatrix Administrator server must be present in the new realm with same password. New ActiveMatrix Administrator Cluster To enable a non-default attribute as a username in a new ActiveMatrix Administrator cluster.properties file. 8. and replace sAMAccountName with your attribute name (the default is valid for Microsoft Active Directory).realm. the following LDAP realm settings: cluster. To update the authentication realm after running the ActiveMatrix Administrator server creation utility use the ActiveMatrix Administrator command-line interface (see ActiveMatrix Administrator Command-Line Interface on page 77).realm.44 | Chapter 3 ActiveMatrix Administrator Server <entry> <name>RetrievalPageSize</name> <value>10</value> </entry> 7. Enable cluster.group_unique_attribute=sAMAccountName Enable cluster.ldap. In the createadminserver. Ensure that the ActiveMatrix database is running and start the ActiveMatrix Administrator server with the -uploadconfig option: AMX_ADMIN_HOME/2.realm. To update the authentication realm: TIBCO ActiveMatrix Administration .

Edit the properties in the AMX_ADMIN_HOME/data/clustername/servername/config/security-config.hsqldb. Example The following sections contain example build and data files for updating the authentication realm. xml password <realm> <realm-name>system</realm-name> TIBCO ActiveMatrix Administration .xml files with the appropriate action and realm configuration. build.xml and datafile.xml" objectSelector="AdminCluster/AuthenticationRealm" adminServerName="servername" adminClusterName="clustername" failOnError="true"/> </target> datafile.Authentication Realm Configuration 45 | 1. file for one ActiveMatrix Administrator server in the cluster. Run the command-line with the specified files. 2.xml <AdminCluster> <AuthenticationRealm xsi:type="amxdata:AuthenticationRealm"> <RealmDetails realmType="DatabaseAuthentication"> <DatabaseAuthenticationProperties driver="org. 3. Create build.xml <target name="edit_realm_details"> <AMXAdminConfigTask username="${username}" password="${password}" action="edit" dataFile="datafile. Restart all ActiveMatrix Administrator servers. In the entries provide an obfuscated password created using TIBCO encryption (see Creating an Obfuscated Password on page 28).jdbcDriver" url="jdbc:hsqldb:hsql://host:1234/amx" userName="user" password="password" maxConnections="10" > </DatabaseAuthenticationProperties> </RealmDetails > </AuthenticationRealm> </AdminCluster> Manual Recovery To recover from an error: 1.

username</name> <value>sa</value> </entry> <entry> <name>hibernate.url</name> <value>jdbc:hsqldb:hsql://hostname:1234/amx</value> </entry> <entry> <name>hibernate.hsqldb.connection.hsqldb.2/bin/. </options> </config-entry> </login-module-configuration> <configuration> 2.jdbcDriver</value> </entry> <entry> <name>username</name> <value>sa</value> </entry> .password</name> <value>#!IvK2PkOuX9laHarIhbxoyA==</value> </entry> .jdbcDriver</value> </entry> <entry> <name>hibernate. 3.driver_class</name> <value>org. Change to the directory AMX_ADMIN_HOME/2. TIBCO ActiveMatrix Administration .connection.. <init-options> <entry> <name>url</name> <value>jdbc:hsqldb:hsql://hostname:1234/amx</value> </entry> <entry> <name>password</name> <value>#!IvK2PkOuX9laHarIhbxoyA==</value> </entry> <entry> <name>driver</name> <value>org.... <options> <entry> <name>hibernate. Restart the other ActiveMatrix Administrator servers in the cluster.46 | Chapter 3 ActiveMatrix Administrator Server <user-manager> .connection... Run cluster_server -uploadconfig 4. </init-options> </user-manager> </realm> <configuration> <login-module-configuration> <realm-name>system</realm-name> <config-entry> ...connection.

For a description of how to pre-create the tables. see Updating the Database Configuration on page 49. the text fields are editable and should be set according to the fields described in this table. Default: Checked. The ActiveMatrix Administrator server creation utility creates the ActiveMatrix administration data tables. All servers in the same ActiveMatrix Administrator cluster use the same database. each field value is copied from the Database Authentication Realm screen into this screen and all the text fields are noneditable. see Securing JDBC Connections on page 345. Database Configuration Reference The fields in Table 12 are used to configure the ActiveMatrix Administrator database. When you run the ActiveMatrix Administrator server creation utility you specify the database configuration. TIBCO ActiveMatrix supports secure access to Oracle databases.Database Configuration 47 | Database Configuration The ActiveMatrix database server maintains ActiveMatrix administration data. TIBCO ActiveMatrix Administration . See ActiveMatrix Database Server on page 14 for details. Table 12 Database Configuration Reference Field Use Configuration Details from Database Authentication Realm Description Indicates whether to use the same database for ActiveMatrix administration data as used for authentication data (see Database Realm on page 35). If unchecked. If checked. For a description of how to update the database configuration after you have created the first server in a cluster. see Pre-creating ActiveMatrix Schema on page 52. For information on how to enable secure connections to Oracle database servers.

sqlserver.SID=<SID> You must supply the hostname.jdbc. For HSQLDB the template is: jdbc:hsqldb:hsql://<hostname>:<port>/<Datastore> You must supply the hostname. TIBCO ActiveMatrix Administration . the template is: jdbc:tibcosoftwareinc:sqlserver://<hostname>:<port#>. port number.hsqldb. and database instance name (SID).databa seName=<databaseName> You must supply the hostname. the Database URL field is populated with a template for the URL of the driver. Default: sa.jdbcDriver For Oracle: tibcosoftwareinc. Default: jdbc:tibcosoftwareinc:sqlserver://<hostname>:1433. the template is: jdbc:tibcosoftwareinc:oracle://<hostname>:<port#>. you can only connect to Management Daemon processes running on the local machine. port number. For HSQLDB: org.jdbc. When you select a driver.SID=XE For Microsoft SQL server. and database instance name (databaseName).oracleOracleDriver For Microsoft SQL Server: tibcosoftwareinc.48 | Chapter 3 ActiveMatrix Administrator Server Table 12 Database Configuration Reference (Cont’d) Field Database Driver Description The name of the JDBC driver class. A template of the URL is supplied for the selected JDBC driver. Default: jdbc:hsqldb:hsql://<hostname>:1234/amx For Oracle.databaseName=<da tabase> Note: If you use localhost as the hostname. and the datastore name. You can select from a list of supported drivers. Maximum number of simultaneous connections to the database that can be open. Password Max Connections A password for the database user.SQLServerDriver Database URL The URL to use to connect to the database. Username The database user name. port number. Default: jdbc:tibcosoftwareinc:oracle://<host>:1521. You must supply the portions of the URL shown between angle brackets and remove the angle brackets.

2. Run the command-line. Restart all ActiveMatrix nodes and ActiveMatrix Administrator servers.xml <target name="edit_db_details"> <AMXAdminConfigTask username="${username}" password="${password}" action="edit" URL Driver class Username and password Maximum number of connections TIBCO ActiveMatrix Administration .Database Configuration 49 | Table 12 Database Configuration Reference (Cont’d) Field Login Timeout Description Amount of time in seconds allowed for login before giving up the attempt. Create build. 3. You can update the following parameters: • • • • Example The following sections contain example build and data files for updating the database configuration. Updating the Database Configuration To update the database configuration after running the ActiveMatrix Administrator server creation utility use the ActiveMatrix Administrator command-line interface (see ActiveMatrix Administrator Command-Line Interface on page 77). A partial success is also supported when some Management Daemon processes are unavailable. Default: 30 seconds. The Management Daemon processes on all machines must be bound and available. To update database configuration properties: 1.xml files with the appropriate action and new database configuration.xml and datafile. build.

and does not work if you don’t perform the migration. <target name="edit_db_realm_details"> <AMXAdminConfigTask username="${username}" password="${password}" action="edit" dataFile="datafile. you should keep in mind the implications of the following use cases: • Parameters reference the old database The application database remains the same.50 | Chapter 3 ActiveMatrix Administrator Server dataFile="datafile. and JDBC URL still uses the same application database. even when some parameters are updated. In some cases.hsqldb. the application database is still the same. may cause the JDBC connection to use a new database. when the password is changed. Using a new database is supported only when you migrate all tables.xml" objectSelector="AdminCluster/DBParameters | AdminCluster/AuthenticationRealm" adminServerName="servername" adminClusterName="clustername" TIBCO ActiveMatrix Administration . even changing the username. • Parameters reference a new database Some parameters. driver. then you must first update the authentication realm database (see Updating the Authentication Realm on page 44). For example. changing the hostname in the JDBC URL. rules and data from the old database to the new database.jdbcDriver" username="sa" password="" > </DBParameters> </AdminCluster> Use Cases When updating the database configuration.xml <AdminCluster> <DBParameters url="jdbc:hsqldb:hsql://hostname:1234/amx" driver="org. Restart the ActiveMatrix Administrator server only after both updates are completed. and then the application database. ActiveMatrix Administrator does not do this automatically. • Database shared with authentication realm If your installation uses the same database for both the application and authentication realm. for example.xml" objectSelector="AdminCluster/DBParameters" adminServerName="servername" adminClusterName="clustername" failOnError="true"/> </target> datafile. views.

Stop all nodes from the ActiveMatrix Administrator UI.jdbc.xml files: <configuration-persistence use="db"> <persistence type="file"/> <persistence type="db"> <property name="driver" value="tibcosoftwareinc. The errors indicate where the propagation of new database parameters has failed. • Failed command A failure will occur for a given machine if the Management Daemon is down.SQLServerDriver"/> <property name="url" value="jdbc:tibcosoftwareinc:sqlserver://host:1433. or not bound. b.. the ActiveMatrix Administrator server will not start. you must go to each machine and manually stop the nodes.Database Configuration 51 | failOnError="true"/> </target> Failure Scenarios Failure may occur in the following scenarios: • Incorrect parameters If you run the command with incorrect parameters. To manually recover from an error: a. unreachable.sqlserver. This matters only if there were runtime nodes or administration servers on that machine.databaseName=amx "/> <property name="user" value="amx"/> <property name="password" value="TX1DOe1AvDc="/> . — ActiveMatrix Administrator server: TIBCO ActiveMatrix Administration . Edit the boldface items in the ActiveMatrix Administrator and node server-config. Manually edit certain files for each node or admin server on the machines where the failures occurred.. </persistence> </configuration-persistence> In the password entry provide an obfuscated password created using the -p option (see Creating an Obfuscated Password on page 28). If you see database related errors while doing this. You must rerun the command using correct parameters before starting the ActiveMatrix Administrator server. There are two recovery options: • • Restart the Management Daemon on that machine and execute the command-line again.

update. Two types of database users are involved when setting up the ActiveMatrix schema: a data definition language (DDL) user and a data manipulation language (DML) user. A DDL user can create and drop tables and is used when pre-creating the ActiveMatrix schema before running the ActiveMatrix Administrator server creation utility.52 | Chapter 3 ActiveMatrix Administrator Server AMX_ADMIN_HOME/data/clustername/servername/config/server-config . but insert. To pre-create schema for the supported databases. Doing so allows you to run ActiveMatrix with a database user that has minimum privileges (no table create or drop. nodes use the new database credentials. the Management Daemon processes use the new database credentials. and delete table records and is used by ActiveMatrix when running the ActiveMatrix Administrator server creation utility. Start nodes from the ActiveMatrix Administrator UI. e. unbind all machines. Upon restart they use the new database credentials.xm l c. In the ActiveMatrix Administrator UI > Configure Enterprise Assets > Machines tab. Pre-creating ActiveMatrix Schema You can pre-create the ActiveMatrix schema (database tables) before running the ActiveMatrix Administrator Server creation utility. Discover and rebind to the same machines Upon rebind. A DML user can insert. Restart all ActiveMatrix Administrator servers.xml — Each node on all remote machines: AMX_HOME/data/environmentname/nodename/config/server-config. and delete table records). see the sections: • • • Microsoft SQL Server on page 53 Oracle on page 54 Sybase on page 57 TIBCO ActiveMatrix Administration . Upon restart. d. update.

The DML user has the following roles: db_datareader and db_datawriter. b.Database Configuration 53 | Microsoft SQL Server To pre-create ActiveMatrix schema in Microsoft SQL Server: 1. See Figure 3 on page 54. Figure 2 SQL Server DDL User TIBCO ActiveMatrix Administration . and db_owner. The DDL user and the DML user must have the same default schema. c. Configure users: a. db_datawriter. See Figure 2 on page 53. The DDL user has the following roles: db_datareader.

3. The DBA creates a DML user and then temporarily grants the user connect and resource permissions. Oracle In Oracle the DML user temporarily functions as DDL user. 5. Run the ActiveMatrix Administrator server creation utility as described in Running the ActiveMatrix Administrator Server Creation Utility on page 56. The DBA logs in as the DML user and runs the DDL and SQL files to create the schema as described in Creating the ActiveMatrix Schema on page 55. Generate the DDL files and edit the cluster schema SQL file as described in Creating the ActiveMatrix Schema Files on page 55. TIBCO ActiveMatrix Administration . To pre-create ActiveMatrix schema: 1. Use the DML username and password to create a cluster following the procedure described in Creating the ActiveMatrix Tables on page 55. Create the tables following the instructions in Creating the ActiveMatrix Schema Files on page 55.54 | Chapter 3 ActiveMatrix Administrator Server Figure 3 SQL Server DML User 2. and Creating the ActiveMatrix Tables on page 55. 2. Give the files to the Oracle DBA and request the creation of a DML user and schema using the DDL and SQL files. 4. 3. Creating the ActiveMatrix Schema on page 55.

SQLServer Studio for SQLServer.2/bin/dbscriptgenerator/dbscriptgenerator. <ENV_NAME_IN_CAPS> is the ActiveMatrix environment (in upper case). 7. the DBA must create a new schema for the environment. Each you create a new environment. 2.sql. and so on) and run the script you created in the preceding section.p roperties with the database properties and DDL username and password here.2/scripts/ddl/createclusterschema_db.Database Configuration 55 | 6. Note that you can duplicate the statements if you want to create several environments. Edit AMX_ADMIN_HOME/2. or sqlserver depending on the database you are using. The DBA revokes the resource permission to the DML user. <ENV_NAME_IN_CAPS>.2/bin/. 2. Create the ActiveMatrix Administrator cluster and the environment tables. oracle. Run the ActiveMatrix Administrator server creation utility as described in Running the ActiveMatrix Administrator Server Creation Utility on page 56. where db is hsql. <ADMIN_CLUSTER_NAME> is the ActiveMatrix administration cluster (in upper case). (and <USER_SCHEMA> for Oracle) by the values you want to use. <USER_SCHEMA> is the DML user that is utilized by ActiveMatrix (in upper case). Creating the ActiveMatrix Tables To create the ActiveMatrix tables: 1. Edit the SQL file and replace <ADMIN_CLUSTER_NAME>. Scripts for creating these tables are in AMX_ADMIN_HOME/2. Creating the ActiveMatrix Schema Files To create the ActiveMatrix schema files: 1. TIBCO ActiveMatrix Administration . Creating the ActiveMatrix Schema To create the ActiveMatrix schema: • Log in as the DDL user to any SQL tool permitted by your database system (SqlPlus for Oracle. Open an terminal window and change to the directory AMX_ADMIN_HOME/2.

Run dbscriptgenerator. and create sequence statements into a file named usermanagement_dbcreateschema.matrix. If you are going to use the database authentication realm.dbscriptgen. and so on) and run dbcreateschema.2/scripts/models/auth/usermgmt. TIBCO ActiveMatrix Administration . alter. 4. 7.mapping. alter. Copy the create. and create sequence statements into a file named dbcreateschema.ddl to usermanagement_dbschema.dbscriptgen.models=AMX_ADMIN_ HOME/2.matrix. c.inheritance to JOINED. SQLServer Studio for SQLServer.dbscriptgen. Use the environment name you have given for <ENV_NAME_IN_CAPS> above (in lower case or upper case).sql.2/scripts/ddl/usermanagement_dbschema. Comment the line containing the com.persistence. The ActiveMatrix tables are created. Set com.sql (and usermanagement_dbcreateschema.56 | Chapter 3 ActiveMatrix Administrator Server 3.tibco.tibco.persistence.tibco.ddl containing drop and create SQL statements.model replacing AMX_ADMIN_HOME with the location of the ActiveMatrix Administrator directory. b. rerun dbscriptgenerator after making following changes in AMX_ADMIN_HOME/2. 6. The script creates the file AMX_ADMIN_HOME/2.sql if you performed step 5 and step 6).2/scripts/ddl/dbschema.modelsfolder property. Set teneo.2/bin/dbscriptgenerator/dbscriptgenerator. Login with the DDL user to any SQL tool permitted by your database system (it can be SqlPlus for Oracle.ddl containing drop and create SQL statements. Add the line com. Running the ActiveMatrix Administrator Server Creation Utility When running the ActiveMatrix Administrator server creation utility: • • Use the administration cluster you have given for <ADMIN_CLUSTER_NAME> (in lower case or upper case).persistence. d. 5. Copy the create.matrix.ddl. The script creates the file AMX_ADMIN_HOME/2.sql.p roperties: a.

Generating the Schema Using DB Script Generator 1.2/scripts/ddl/dbschema. 4. 6. 4.properties. where sandbox-db-name is the database you created in step 1.ddl. Change the owner of the current database to the user you created in step 3. Go to Logins and click Add Login. Type go and press Enter. Go to Databases and click Add Database on the right hand side.exe -file AMX_ADMIN_HOME/2. 3. the schema are created in AMX_ADMIN_HOME/2. TIBCO ActiveMatrix Administration . Set the username and password to the values you specified in the preceding section and in the #Sybase Properties section. Creating a User and a Database in Sybase 15. Sybase This section describes how to create a non-sa user and sandbox database in a Sybase instance and create the ActiveMatrix schema in the sandbox database. defdb. 3. 2. 1. Type go and press Enter.x This section describes how to create a sandbox database for a user in your Sybase instance. Type sp_modifylogin sandbox-user-name.exe. Run sybase-home-dir/OCS-15_0/bin/isql. Set the sandbox user's default database to the sandbox database. press Enter. Create a new database named sandbox-db-name. 2. Open a command window.exe -U sa -P sa-password -D sandbox-db-name. Package and install the Sybase native driver as described in Packaging and Installing Native Database Drivers in TIBCO ActiveMatrix Service Grid Installation. set the correct driver URL for the Sybase driver. Run Sybase Central and log in as sa.2/bin/dbscriptgenerator. 5.Database Configuration 57 | • Use the DML username and password when the utility asks for the database parameters.tra. Edit dbscriptgenerator. Type sp_changedbowner sandbox-user-name. By default. If you have a centralized production Sybase database you will probably want such a sandbox database and user. Change to ENV_HOME/tools/bin and run flattener. Run dbscriptgenerator. Create a user named sandbox-user-name. sandbox-db-name and press Enter.

When you create the schema you will see the following warning messages. 3. Warning: Row size (17617 bytes) could exceed row size limit. Non-clustered index (index id = 2) is being rebuilt. These can be ignored as they are benign. Cut the create/alter part of the schema from the dbschema. 2. because ActiveMatrix generates schema with some names quoted and this is not the default for Sybase. Enable quoted identifiers. Type go in the next line. is 1962 bytes. Warning: Row size (2129 bytes) could exceed row size limit. Type set quoted_identifier on and press Enter.. Warning: Row size (5426 bytes) could exceed row size limit. but iAnywhere does not support 30 byte table name length used by ActiveMatrix. Non-clustered index (index id = 2) is being rebuilt.58 | Chapter 3 ActiveMatrix Administrator Server Creating Schema Generated by DB Script Generator You cannot create schema in the database using the iAnywhere graphical tool because Sybase 15 server allows up to 255 byte table names. is 1962 bytes. is 1962 bytes. Warning: Row size (2110 bytes) could exceed row size limit.exe -U sandbox-user-name -P sandbox-user-password (if you followed the instructions in Creating a User and a Database in Sybase 15. is 1962 bytes.. which which which which which TIBCO ActiveMatrix Administration . Run sybase-home-dir/OCS-15_0/bin/isql.ddl file created in Generating the Schema Using DB Script Generator on page 57 and paste it into isql. Non-clustered index (index id = 2) is being rebuilt.x on page 57. Non-clustered index (index id = 2) is being rebuilt. 4. . The schema is created. Warning: Row size (3463 bytes) could exceed row size limit. To create the schema: 1. by default the database is the sandbox database). is 1962 bytes.

Default: http://localhost:7222. Username The messaging server user name for the node’s connection to the Enterprise Message Service server. Default:9992. Default: node1.Default Runtime Node Configuration 59 | Default Runtime Node Configuration The fields in Table 13 are used to configure the default runtime node. Node Management Port Management port on which the node listens and responds for management and control functions using JMX protocol. Default: admin. For detailed information on node properties and behavior. Provider URL The messaging server provider URL that specifies the Enterprise Message Service server that the node connects to. Default: development. see Working with Nodes on page 188. The name must be less than 23 characters in length and can contain only alphanumeric and underscore (_) characters. Default: No password. TIBCO ActiveMatrix Administration . Table 13 Default Runtime Node Field Environment Name Description The name of the environment that contains the default node. The fields are active when the Create a default runtime node checkbox is checked in the ActiveMatrix Administrator server creation utility. Password The password for the messaging server user name account. The name must be less than 23 characters in length and can contain only alphanumeric and underscore (_) characters. Node Name The default node’s name.

See Starting the Database Server on page 15. In the following sections.) If you cannot log in to the user interface. After you have performed one of the startup procedures described in the following sections. Starting and Stopping the ActiveMatrix Administrator Server This section describes procedures for starting up an ActiveMatrix Administrator server on all platforms. The database server must be running.60 | Chapter 3 ActiveMatrix Administrator Server Starting and Stopping the ActiveMatrix Administrator Server This section describes how to start and stop the ActiveMatrix Administrator server you created in Creating the First ActiveMatrix Administrator Server on page 26. The authentication realm must be available. If you accept the default values when you create the server. you can add ActiveMatrix Administrator servers to the cluster and manage all the servers in a cluster using the procedures described in ActiveMatrix Administrator Servers on page 163. cluster is amx and server is admin. review the log (see Server Logs on page 334) for error conditions. cluster is the name of the cluster and server is the name of the server you provide when you create the server. After you have started the first ActiveMatrix Administrator server in a cluster. The following preconditions must be satisfied before starting the server: • • • The TIBCO Management Daemon process must be running. TIBCO ActiveMatrix Administration . you can confirm that the server has started successfully by logging in to the ActiveMatrix Administrator user interface (see Logging in to the ActiveMatrix Administrator Graphical Interface on page 65. page 17. See Starting TIBCO Management Daemon. First-time startup is slower than subsequent startups because the ActiveMatrix Administrator web application is deployed.

bat. Wait a few minutes after the Services application reports that startup is complete before attempting to access the ActiveMatrix Administrator GUI. Open Control Panel > Administrative Tools > Services.exe --uninstall. To stop the server. 2.Starting and Stopping the ActiveMatrix Administrator Server 61 | Windows The ActiveMatrix Administrator server is installed as an Windows service with its Startup Type set to Manual. Control Panel 1. Change directory to AMX_ADMIN_HOME/data/clustername/servername/bin. 2. Run cluster_server. Batch Script To start the ActiveMatrix Administrator server in console mode: 1.ear 7:07:48 AMAuto Deploy directory : [C:\tibco\ amxadministrator\data\amx\admin\archives\ TIBCO ActiveMatrix Administration . right-click the service and select Stop. The last lines of the output are similar to the following: ********************************************************** TIBCO ActiveMatrix Administrator Server is initialized and ready. You can start the server in the Control Panel or via a batch script. To configure the server to start automatically when the machine starts.exe --install. 2. change the Startup Type to Automatic. If you start the server from this script. The first time you start the service the Services application reports that the service has started before it has completely deployed and initialized.Started Application : amxadministrator. To add the ActiveMatrix Administrator server to Services: 1. you can stop it by Ctrl+C termination. Run cluster_server. Change directory to AMX_ADMIN_HOME/2.2/bin. To remove the ActiveMatrix Administrator server from Services: 1. Right-click the service with a name of the form: TIBCO ActiveMatrix Administrator Server (cluster:server) and select Start. Run cluster_server. You can access it using the URL: http://AdminMachineName:8120/amxadministrator/ ********************************************************** 7:07:47 AM.

run the following in a terminal window: AMX_ADMIN_HOME/2.sh & You can log out of the terminal and the ActiveMatrix Administrator server continues to run.Configuration files backup [ OK ] 7:07:50 AM.Started Application : default_defaultApp 7:07:48 AM.sh To start the ActiveMatrix Administrator server in background mode. UNIX To start the ActiveMatrix Administrator server in console mode.Server [admin] started [ OK ] Thread[pool-1-thread-2] registered with management daemon: .C:\tibco Thread[pool-1-thread-1] registered with management daemon: MDMachine.JSP precompilation is off.Deploying Application : default_defaultApp 7:07:48 AM.Application [default_defaultApp] successfully Deployed 7:07:48 AM.C:\tibco SUN version 1.5 where AdminMachineName is the name of the machine on which the ActiveMatrix Administrator server is running and MDMachine is the name of the machine on which a Management Daemon process is running. Skipping JSP pre-compilation for [default_defaultApp] 7:07:48 AM.2/bin/cluster_server. You see one such line for each Management Daemon process bound to the ActiveMatrix Administrator server.Accepting Web client requests: 7:07:48 AMStarting 5 HTTP Acceptor Threads [ OK ] 7:07:48 AMStarting 50 Worker Threads with max [ OK ] keep-alive waiting threads 10. TIBCO ActiveMatrix Administration .2/bin/cluster_server. run the following in a terminal window: nohup AMX_ADMIN_HOME/2. 7:07:49 AM.62 | Chapter 3 ActiveMatrix Administrator Server autodeploy] 7:07:48 AMAuto Deploy poll interval : [5 seconds] 7:07:48 AM.

| 63 Chapter 4 ActiveMatrix Administrator Interfaces This chapter describes the ActiveMatrix Administrator user interfaces. page 65 ActiveMatrix Administrator Command-Line Interface. page 64 ActiveMatrix Administrator Graphical Interface. Topics • • • ActiveMatrix Administrator Interfaces Overview. page 77 TIBCO ActiveMatrix Administration .

editing. see ActiveMatrix Administrator Command-Line Interface on page 77. For information on how to create the required files and run the interface. In particular. ActiveMatrix Administrator Graphical Interface on page 65 describes how to log in to the ActiveMatrix Administrator graphical interface and provides an overview of the standard perspectives. To use command-line interface you set up a data file that specifies the objects on which to perform actions and a build file that specifies the actions to be performed. it supports adding. The product-specific functionality is added to ActiveMatrix Administrator by uploading and deploying a plug-in containing new features. installing and uninstalling. A perspective is a set of controls used to carry out a category of administration tasks. to ActiveMatrix Administrator. In the ActiveMatrix Administrator graphical interface functionality is divided into perspectives. Extending the perspectives TIBCO ActiveMatrix Administrator is extensible. see Plug-ins on page 161. Command-Line Interface The command-line interface provides access to most ActiveMatrix Administrator functions. This means that other TIBCO products can add functionality. and deploying and undeploying objects. such as new perspectives and new screens within the standard perspectives. TIBCO ActiveMatrix Administration . The remaining chapters in this book provide extensive task and reference information on each perspective. For information on managing plug-ins. and deleting ActiveMatrix objects and actions such as starting and stopping. Graphical Interface The graphical interface provides access to all ActiveMatrix Administrator functionality through a browser. You use the command-line interface for repetitive application of standard actions on large numbers of objects.64 | Chapter 4 ActiveMatrix Administrator Interfaces ActiveMatrix Administrator Interfaces Overview ActiveMatrix Administrator provides two interfaces for interacting with the ActiveMatrix Administrator server: graphical and command line.

Domain. type a URL of the following format: http://Hostname.ActiveMatrix Administrator Graphical Interface 65 | ActiveMatrix Administrator Graphical Interface This section describes how to log in to the ActiveMatrix Administrator graphical interface and provides an overview of the perspectives available in the interface. Logging in to the ActiveMatrix Administrator Graphical Interface To Access the Login Page From a Browser Window In your browser’s address field. You see a list of ActiveMatrix Administrator servers installed on the local machine.:8120/amxadministrator. Click the name of a server: TIBCO ActiveMatrix Administration .acme. The port is the HTTP port you specified for the server when you created it.com:HTTPPort/amxadministrator For example: http://amxserver. (The domain name may not be required by your browser. Select All Programs > TIBCO > TIBCO ActiveMatrix > Administrator Servers.) To Access the Login Page From the Windows Start Menu 1. 2.com.

enter a valid username and password: The ActiveMatrix Administrator session timeout is set to 15 minutes. TIBCO ActiveMatrix Administration . If you do not actively use the ActiveMatrix Administrator graphical interface for a length of time equal to the timeout period you are automatically logged out the next time you interact with the interface.66 | Chapter 4 ActiveMatrix Administrator Interfaces To Log in to the ActiveMatrix Administrator Graphical Interface At the login screen.

TIBCO ActiveMatrix Administration . from which you can choose an environment. changing the current user’s password (see Changing a User Password on page 141). the Environment drop-down list.ActiveMatrix Administrator Graphical Interface 67 | Graphic Interface Overview Once you have logged into the graphical user interface. The page is divided into header and welcome areas. displays just below it. Figure 4 Welcome Page Header The main control in the header area is the Perspective drop-down list from which you can choose a perspective. displaying online help (see Help on page 75). displaying information about ActiveMatrix Administrator. and system messages (see System Messages on page 75). you see the Welcome page shown in Figure 4. The header appears in all screens in the graphical interface. The header also has links for logging out. If you select either the Configure an Environment or Deploy to an Environment perspectives.

You select a perspective by clicking a perspective in the list. a description of the perspective displays to the right of the perspective list. Figure 5 Enterprise Assets Tab Bar The Configure Environments and Deploy to an Environment perspective have an Environment drop-down list in the header that allows you to select the environment on which to work. you leave the Welcome page. To return to the Welcome page you must log out and log in again. Clicking one of the environments opens the selected environment in the parent perspective. a menu listing available environments appears just below the perspective.68 | Chapter 4 ActiveMatrix Administrator Interfaces Welcome Area The welcome area contains a list of perspectives (see Perspective Overview on page 68). The remaining chapters in this manual provide complete task and reference information for each perspective. When you mouse over a perspective. TIBCO ActiveMatrix Administration . The remaining sections in this chapter provide an overview of each perspective and the standard behaviors of the graphical interface. it displays only those perspectives that you have the right to use (see Permissions on page 145). Once you open a perspective from the Welcome page. Clicking any other perspective simply opens the perspective. This list is permissions-based. Perspective Overview This section provides an overview of the four standard perspectives provided when ActiveMatrix Administrator is installed: • • • • Configure Enterprise Assets on page 69 Configure Environments on page 70 Deploy to an Environment on page 70 Monitor & Manage on page 71 The Configure Enterprise Assets and Monitor & Manage perspectives have a tab bar below the header that allows you to select screens within each perspective. For example. If you click either the Configure an Environment or Deploy to an Environment perspectives. the Configure Enterprise Assets tab bar has the tabs shown in Figure 5.

on page 169. on page 99 and Chapter 6. registry. software. messaging. TIBCO ActiveMatrix Administration . Figure 6 Configure Enterprise Assets Perspective For details on the functionality offered in this perspective.ActiveMatrix Administrator Graphical Interface 69 | Configure Enterprise Assets In the Configure Enterprise Assets perspective . and other enterprise assets that are made available to an ActiveMatrix runtime. an IT administrator manages the hardware. the administrator uses this perspective to perform the following actions on enterprise assets: • • • • • • Binds machines to the administrator cluster Creates environments and allocates machines to environments Configures administrator. database. Specifically. and policy servers Creates a user base and assigns permissions to users Creates shared resource definitions Creates a central keystore and populates it Figure 6 on page 69 shows the Configure Enterprise Assets perspective. see Chapter 5. Configuring Enterprise Assets. Defining Environments.

Specifically the architect installs runtime components on allocated machines and configures them. allocation of service units to nodes. a TIBCO ActiveMatrix architect manages service assemblies: uploading. Figure 7 Configure Environments Perspective For details on the functionality offered in this perspective. and life cycle functions. on page 187. see Chapter 7. deployment. a TIBCO ActiveMatrix architect configures and manages the life cycle of ActiveMatrix runtime components: nodes. Deploy to an Environment In the Deploy to an Environment perspective . configures them and deploys Performs initial verification and monitoring of system health and performance TIBCO ActiveMatrix Administration . containers. Specifically the architect • • Distributes deployment artifacts to various nodes. Configuring Environments. and shared resources. Figure 7 on page 70 shows the Configure Environments perspective.70 | Chapter 4 ActiveMatrix Administrator Interfaces Configure Environments In the Configure Environments perspective .

see Chapter 8. Troubleshoots problems by — Viewing current and historic statistics — Tracking dependencies — Viewing logs for infrastructure objects and services • Takes corrective actions. on page 215. Specifically. Figure 9 on page 72 shows the Monitor & Manage perspective. Deploying Service Assemblies. restarts infrastructure objects or services.ActiveMatrix Administrator Graphical Interface 71 | Figure 8 on page 71 shows the Deploy to Environment perspective. For example. Figure 8 Deploy to Environment Perspective For details on the functionality offered in this perspective. TIBCO ActiveMatrix Administration . Monitor & Manage In the Monitor & Manage perspective . the engineer • • Monitors the health and performance of infrastructure and services. an operations engineer manages the ActiveMatrix infrastructure and services deployed on the infrastructure.

The following icons are used across all perspectives: Defined. Monitoring Infrastructure and Services. Not Active Out of sync Install Failed Uninstall Failed Start Failed Stop Failed Unknown Status Icons on page 72 Screens on page 73 Fields on page 73 Tables on page 73 Help on page 75 System Messages on page 75 Help on page 75 TIBCO ActiveMatrix Administration . Active Installed/Stopped. Deployed Uninstalled Running. on page 239.72 | Chapter 4 ActiveMatrix Administrator Interfaces Figure 9 Monitor & Manage Perspective For details on the functionality offered in this perspective. Not Deployed Installed. Working with the Graphical User Interface The following sections describe various facets of working with the graphical user interface: • • • • • • • Status Icons The user interface employs a rich set of icons to convey the status of components. see Chapter 9.

The pencil icon can appear multiple times in one screen. See System Messages on page 75 for more information. The error is displayed in an Error dialog with an OK button. The Edit button is displayed in View mode. allowing you to fix the error. displays to the left of the Screens support view mode and edit mode. Within a screen there may be more than one area that can be edited. the object remains in Edit mode. Save saves the changes and returns to View mode. Tables Selecting Rows When a screen containing a table is displayed. When an area is in Edit mode. The dialog describes the problem and is dismissed by clicking OK. You do not have to save changes before switching to another area. Cancel cancels any changes before saving. A dialog. An area in Edit mode displays Cancel and Save buttons. Fields Mandatory fields are indicated with an asterisk * at the end of the field label. If an object could not be successfully created or added. When there is a field-level problem. such as a validation error. Edit Mode Edit mode allows you to edit objects. a pencil icon is displayed to the left of the screen selected icon. The display remains in Edit mode so the object can be edited. and cancelled independently. View Mode View mode provides a read-only view of object details. saved.ActiveMatrix Administrator Graphical Interface 73 | Delete Delete Failed Other icons used in specific contexts are described in the following sections. with an OK button. The error message gives enough information so that you can fix the error. there is no default row selection. the requested action cannot be completed. View mode is displayed by default. TIBCO ActiveMatrix Administration . When an item is successfully created or added. Screens When a screen is selected. the screen selected icon screen label. allowing you to click Edit to edit the selection. is displayed and the screen behind is grayed out.

For example. no properties are displayed in the form below the table. the rows toggle between being sorted according to ascending or descending values in the column. press Shift or Ctrl and click the rows. you could multiselect several nodes and click the Start button to start all of the nodes at once. click the nonhierarchical list icon Performing Actions The actions supported by entries in a table appear as buttons across the top of the table. click the column header. click the row. Some tables support multiselect. Tables that support filtering have one or more View drop-down lists where you can select the objects to display in the table. If you click the column header more than once. . To toggle from a hierarchical to flat list. Sorting Table Rows To sort table based on the value of a specific column. In a hierarchical list. Filtering Table Entries Some tables allow you to filter the entries displayed in the table by usage or type. in the Monitor & Manage > Infrastructure > Machine view you can toggle the Nodes list to display the environments and the nodes within each environment or as a list of nodes. click the hierarchical list icon To toggle from a flat to hierarchical list. When you select multiple rows. the Enterprise Assets > Shared Resource Definitions table allows you to display specific types of definitions. For example. the row is colored with a yellow gradient and details about the properties of the selected object are displayed in a form below the table. you toggle between displaying only the parent or the parent and it’s child objects by clicking the + to the left of the parent. Once a row that has been selected. Multiple rows TIBCO ActiveMatrix Administration . . For example.74 | Chapter 4 ActiveMatrix Administrator Interfaces Single row To select a single row in the table. Hierarchical Lists Some tables display their entries alternately as hierarchical and nonhierarchical lists. The actions are specific to the objects listed in the table. To select multiple rows.

click the Help link in the header. Running. starting . Defined or Uninstall Failed. TIBCO ActiveMatrix Administration . The dialog refers you to system messages for details. To update the object status for such operations. You can clear the messages by clicking the delete icon in the dialog frame. such as installing and starting a node. A dialog. You can also manually update the status of objects by clicking the Refresh icon located at the top right of the table. click the help icon title. the user interface automatically updates the status to Installed or Install Failed. You can then click the Messages link in the right side of the header next to the screen to view the most recent system messages. Once you click the link to view the messages. Certain long-running operations. Help To display the online help for ActiveMatrix Administrator. such as a server communication problem or an environment name in use when attempting a delete operation. To display help about a specific screen. This means that the user interface continues to respond to user actions while the operation is in progress and does not automatically update the status. with an OK button.ActiveMatrix Administrator Graphical Interface 75 | Updating Object Status While the operations are in progress. System Messages When there is a system-level problem. is displayed. stopping . are performed asynchronously. As shown in Figure 10 on page 76. or Installed/Stopped. the icon disappears. the user interface displays the Working icon in the header and "working" icons—installing . you must click the Refresh button . the requested action cannot be completed. When the operation has completed. The system messages alert icon displays next to the link when there are messages that haven’t been viewed. the messages contains details about all errors that have occurred since the Messages link was last cleared. and deleting —in the status column of the object. uninstalling .

but the status has not yet been updated in ActiveMatrix Administrator to show the node as Installed/Stopped. containers. In some cases the status of nodes.76 | Chapter 4 ActiveMatrix Administrator Interfaces Figure 10 System Messages Limitations The user interface is not the definitive source of information about the state of the ActiveMatrix system. the Monitoring & Management perspective displays the state of the system when you retrieve information from the monitoring service. For example: • A node is running. A node is stopped. but the status has not yet been updated in ActiveMatrix Administrator to show the node as Running. after some time has elapsed since running the query the Log Viewer does not show the most recent log entries. • • The Log Viewer displays the log entries in existence when you run a query. You can configure the Log to periodically refresh itself. A node is running. but the Management Daemon process is stopped and the but the node status is shown as Unknown. TIBCO ActiveMatrix Administration . and shared resources shown in ActiveMatrix Administrator may not reflect the actual status of the objects. Since log entries are generated continuously. but instead is shown as Running. The data on every screen in this perspective is updated every minute. Similarly. but instead is shown as Installed/Stopped.

Runtime Actions These actions modify the state of the objects contained in the ActiveMatrix runtime. Delete is also used to delete associations between objects. Add is also used to add associations between objects. In particular. • • Edit Edits an object in the ActiveMatrix Administrator database. After that you can delete the environment and all of its children. such as between an environment and a shared resource definition. Delete Deletes an existing object from the ActiveMatrix Administrator database. the entire tree rooted at the object is deleted starting at the leaves. how to specify the objects. such as between an environment and a shared resource definition. you must stop and uninstall all nodes contained in the environment. the objects on which you can perform actions. Actions This section describes the actions that can be performed with the command-line interface. • Add Adds an object to the ActiveMatrix Administrator database. Database Actions These actions modify the objects contained in the ActiveMatrix Administrator database. When you delete an object. • • • • • • Start Starts an object Stop Stops an object Install Installs an object Uninstall Uninstalls an object Activate Activates a container Deactivate Deactivates a container TIBCO ActiveMatrix Administration .ActiveMatrix Administrator Command-Line Interface 77 | ActiveMatrix Administrator Command-Line Interface This section describes the actions you can perform with the command-line interface. Sometimes you must do some cleanup before you can delete an environment. and how to invoke the command-line interface.

Machine. The rest of the attributes are referred to as description attributes. LogServiceConfiguration. AdminServer. Container. ServiceAssembly. Group. AuthenticationRealm. UIElement. relationships between objects. Service. Supported Objects The objects supported by the command-line interface are: Enterprise. and SharedResourceProfile. SubstitutionVariable. We refer to such identifying attributes as ID attributes. Environment. Logger. ServiceUnit. Topic. see Supported Objects and Attribute Reference on page 92. Table 14 summarizes the actions and the objects that support those actions. Some of these attributes. and the formats for expressing objects. AdminCluster. and ServiceUnit are container objects that do not support any actions. Each object has a set of attributes that describe that object. AdminCluster. object attributes. For information about the attributes. can be used to uniquely identify a particular object assuming the location of the object in the data hierarchy is known. Table 14 Actions and Objects (Sheet 1 of 3) Add Edit Delete Start Stop Install Uninstall Deploy Undeploy Activate Deactivate Environment Machine User Environment Environment Machine User User TIBCO ActiveMatrix Administration . Node. such as the name of the object. DefaultConnector. SubstitutionVariable. MessagingBus. MessagingServer. SharedResourceDefinition. Enterprise.78 | Chapter 4 ActiveMatrix Administrator Interfaces • • • Deploy Deploys a service assembly Redeploy Redeploys a service assembly. Permissions. ListOfSuperUser. MonitoringConfiguration. DBParameters. BootStrapUser. Undeploy Undeploys a service assembly Objects This section describes the objects that can be accessed from the command-line interface. SharedResource. UDDIServer. Keystore. User.

ActiveMatrix Administrator Command-Line Interface 79 | Table 14 Actions and Objects (Sheet 2 of 3) Add Edit Delete Start Stop Install Uninstall Deploy Undeploy Activate Deactivate ListOf SuperUser Group Keystore Shared Resource Definition UDDIServer Group Keystore Shared Resource Definition UDDIServer UIElement Substitution Variable Substitution Variable Permissions Admin Server Admin Server LogService Configuration Monitoring Configuration BootStrapUser DBParameters Authentication Realm Messaging Bus Messaging Server Node Messaging Server Node ListOf SuperUser Group Keystore Shared Resource Definition UDDIServer Substitution Variable Admin Server LogService Configuration Admin Server Messaging Server Node Node Node TIBCO ActiveMatrix Administration .

one of the objects is a child of the other object and is contained in that parent object. each object has relationships with other objects. In the figure. parents are on the left and children are on the right. such as that between an Environment and a Node. Relationships can be either parent-child or associative. Logger Shared Resource Service Assembly Service Assembly Shared Resource Service Assembly TIBCO ActiveMatrix Administration . The possible parent-child relationships are illustrated in Figure 11 on page 81. User and Group are marked with an asterisk because they are children of Enterprise only when using the Database authentication realm.80 | Chapter 4 ActiveMatrix Administrator Interfaces Table 14 Actions and Objects (Sheet 3 of 3) Add Edit Delete Start Stop Install Uninstall Deploy Undeploy Activate Deactivate Container Default Connector Shared Resource Service Assembly Service Assembly Substitution Variable Topic Service Logger Logger Shared Resource Profile Inter-Object Relationships Aside from attributes. In a parent-child relationship.

the referencing objects are on the left and the referenced objects are on the right. The possible associative relationships are illustrated in Figure 12. In such situations you must create a reference from one object to the other object. one object is not a child of the other. such as that between an Environment and a Machine.ActiveMatrix Administrator Command-Line Interface 81 | Figure 11 Parent-Child Relationships Permissions Environment Machine Node User* ListOfSuperUser Enterprise Group* Keystore Group* Topic Permissions Permissions SharedResource Definition UDDIServer UIElement Permissions Logger Permissions UIElement Service Unit Service Logger SharedResource SubstitutionVariable Service Assembly SharedResource Profile SubstitutionVariable Container Logger MessagingBus MessagingServer DefaultConnector Permissions SubstitutionVariable Logger Permissions SubstitutionVariable Admin Cluster AdminServer* LogService Configuration Monitoring Configuration BootStrapUser DBParameters AuthenticationRealm In an associative relationship. but the two objects need to work with each other. In the figure. TIBCO ActiveMatrix Administration .

parent-child relationships. ActiveMatrix Administrator provides XSD schemas for the data files that capture all of the ID attributes. Every object is described in an XML element. description attributes. The cardinality of the relationship between SharedResourceDefinition and Environment is many-to-many. and associative relationships of ActiveMatrix objects (see Data File Schemas on page 92). The data file is input to the command-line interface along with a build file that specifies the actions to be performed on the data. In these schemas. or many-to-many. Base Format • • • Captures the ID attributes of an object as XML attributes Captures the parent-child relationships of an object as XML elements Doesn’t capture any parent information about the object as that information is derived from the XML structure You use the base format to: • • Delete an object Perform a runtime action on an object TIBCO ActiveMatrix Administration . many-to-one. every ActiveMatrix object can be specified in three types of formats: base. Object Formats You specify the objects on which the command-line interface operates in an XML data file. the cardinality of the relationship a set of objects can have with each other can be one-to-one. and reference.82 | Chapter 4 ActiveMatrix Administrator Interfaces Figure 12 Object Association Machine UDDI Server Shared Resource Profile Shared Resource Definition Shared Resource Definition Group ListOf SuperUser Service Unit User User Node Environment SharedResource Definition UDDIServer Regardless of the type of relationship. The cardinality of the relationship between Node and Environment is many-to-one. For example. The attributes of that object (both ID and descriptive) are attributes of the XML element. the cardinality of the relationship between Environment and MessagingBus is one-to-one. full. and the relationships this object has with other objects are subelements of the XML element.

matrix.0"/> </Node> An node in full format has: • • • ID attribute: name Other required attributes: hostname. DefaultConnector Data file element: <Node name="node1"> <Container type="com.javase. and so on Description attribute: description TIBCO ActiveMatrix Administration .tibco.runtime" version="2.container. productInstallDirectory.ActiveMatrix Administrator Command-Line Interface 83 | • • Add a child to an object Perform an action on a child of an object Full Format • • • • Is derived from base format Captures the ID and description attributes of an object as XML attributes Captures the parent-child and associative relationships of an object as XML elements Doesn’t capture any parent information about the object as that information is derived from the XML structure You use full format: • • Whenever the base format can be used To add or edit an object Reference Format • • Captures the ID attributes of an object as XML attributes Objects not residing directly under the Enterprise have parent information because it cannot be derived from the XML structure You use reference format: • When associating that object to another object Examples A node in base format has: • • ID attribute: name Parent-child relationships: Container.0.

it’s just a convenience to only have to use it when overriding default types in schemas.. In the schema.2.0. so you don’t have the ability to override what type to use. Thus there would never be a reason why you should need xsi:type for associating Nodes with ServiceUnits. For example.container.. you need to use the xsi:type attribute to tell the XML parser that you are using a different type than the default. TIBCO ActiveMatrix Administration . You must include the xsi:type attribute only when you want to override the default type as specified in the XSD.0"/> </Node> A node in reference format has: • • Id attributes: nodeName Parent attribute: environmentName Data file element: <ServiceUnit xsi:type="amxdata:ServiceUnit" name="SOAP SU"> .tibco. DefaultConnector Data file element: <Node xsi:type="amxdata:Node" name="node1" description="desc" hostName="Hostname" tibcoHome="ENV_HOME" productInstallDirectory="AMX_HOME" productVersion="2. then you don’t need to include an xsi:type attribute required because that is what is declared in the XSD. You should note that the XML parser parses elements even if you do use xsi:type attribute. if you want to define an Environment object under the Enterprise. then you don’t have to use xsi:type because that is what is specified in the schema. <Node environmentName="env1" nodeName="node1"/> . an Enterprise contains zero or more Environment_base objects. where Environment is a type that derives from Environment_base. As another example. </ServiceUnit> Notice that when using the base format you do not need to include the xsi:type attribute in the node element because the base format is the default format expected by the Enterprise object. a ServiceUnit can have a list of zero or more Node_references. If you want to create an Environment_base object.. If you intend to use the Node_reference type. The XML parser internally verifies that the type used derives from the default type.runtime" version="2.matrix. in amxdata_base. Also there is nothing in the schemas that derives from Node_reference. However. consider associating a Node with a ServiceUnit..84 | Chapter 4 ActiveMatrix Administrator Interfaces • Parent-child relationships: Container.0" messagingServerName="ms1" namingPort="namingPort > <Container type="com.javase.

2/bin. target. Change to the directory AMX_ADMIN_HOME/2.command.. The following sections describe the structure of the build file and the syntax of AMXAdminTask and AMXAdminConfigTask.ant.org).administration. It is implemented as an Ant tasks named AMXAdminTask (see AMXAdminTask on page 87) and AMXAdminConfigTask (see AMXAdminConfigTask on page 97). <project default="target"> <taskdef .line. Build File The build file must contain the following four elements: project. Run admincmdline build.ActiveMatrix Administrator Command-Line Interface 85 | Invoking the Command-Line Interface The command-line interface is based on Ant.AMXAdm inConfigTask"/> TIBCO ActiveMatrix Administration . To invoke the command-line interface: 1. AMXAdminTask is used for operations on most objects.administration.apache. an XML format build configuration file that is the input to the tool admincmdline. You specify one these Ant tasks in a build target within a build file.. /> <target name="target" . 2.xml file. project Element The project element declares the default build target for the build.. AMXAdminConfigTask is used to change the properties of the cluster objects DBParameters and AuthenticationRealm.tibco.matrix.xml.AMXAdm inTask"/> or <taskdef name="AMXAdminConfigTask" classname="com. It must include the name and classname attributes defined exactly as follows: <taskdef name="AMXAdminTask" classname="com. taskdef and target are subelements of project.command. where build is the name of the build configuration file. and AMXAdminTask or AMXAdminConfigTask. The value of the name attribute of the target element must be the same as the value of the default attribute of the project element.matrix..ant.line. an open source build tool (http://ant. taskdef. /> </project> taskdef Element The taskdef element specifies the class that implements the Ant task.tibco.

.86 | Chapter 4 ActiveMatrix Administrator Interfaces target Element The target element specifies the actions performed for an execution of the command line interface via the AMXAdminTask or AMXAdminConfigTask subelement. <target name="target"> <AMXAdminTask . /> </target> TIBCO ActiveMatrix Administration . /> </target> or <target name="target"> <AMXAdminConfigTask ....

Deactivate. — For the most part. Start.AMXAdminTask 87 | AMXAdminTask Ant Task Description Syntax Specifies the administrative action and objects on which the action is performed. Undeploy: breadth first — Delete. Objects not in this format are skipped.xml or in response to a prompt. Add and Edit are applied only to objects specified in full format. Edit. See Creating an Obfuscated Password on page 28. The action is case insensitive. Activate. the action is applied to every object in the data file. Options Table 15 Options (Sheet 1 of 4) Attribute action Type String Req? Yes Description One of the actions listed in Actions on page 77. The method used is determined by the action. Stop. • • Unless objectSelector is specified. Uninstall: depth first • Some actions are not performed against certain object formats (see Object Formats on page 82). Install. The order in which the action is applied to the objects is either breadth first or depth first. — Add. TIBCO ActiveMatrix Administration . Deploy. <AMXAdminTask action="action" dataFile="dataFile" adminURL="URL" username="username" password="password" [actionTimeoutSecs="timeout"] [failOnError="{true|false}"] [objectSelector="XPath_Expression"] [overwrite="{true|false}"] [merge="{true|false}"] [createIfNotExists ="{true|false}"] [force="{true|false}"] /> </AMXAdminTask> You authenticate from the command-line interface either by providing a username and obfuscated password in build.

dataFile failOnError String Boolean Yes No The absolute path to the XML file containing the object data.tra. Note that the tool does not stop the actions when the timeout is reached but continues processing the rest of the objects in the data file. TIBCO ActiveMatrix Administration .timeout in the file AMX_ADMIN_HOME/bin/admin_cmdline. If an object is to be edited but doesn’t yet exist and this flag is true. Relevant to the Edit action. See Data File on page 92. The default timeout time is configurable. then the object is added. The default timeout is 180 seconds.property. Default: false.action.88 | Chapter 4 ActiveMatrix Administrator Interfaces Table 15 Options (Sheet 2 of 4) Attribute actionTimeoutSecs Type String Req? No Description Set the timeout for node actions that are performed asynchronously (install. The timeout controls how long the tool waits for the actions to complete. start. stop). adminURL createIfNotExists URL Boolean Yes No The URL of the ActiveMatrix Administrator server. set the property java.node. To set the default timeout time. Causes the Ant task to fail when an unrecoverable error is reported.runtime. uninstall.

The old object's children. A node must be in the Uninstalled state before it can be deleted and it must be Stopped before it can be uninstalled.AMXAdminTask 89 | Table 15 Options (Sheet 3 of 4) Attribute force Type Boolean Req? No Description Relevant to the Delete and Uninstall actions. If this flag is false but the overwrite flag is true. • Default: false. A service assembly must be in the Undeployed state before it can be deleted and it must be Stopped before it can be undeployed. and force is true. are lost in the process. If any problems occur moving the service assembly to one of these states. That is. the node is deleted even if it is not in the uninstalled state or uninstalled even if it is not stopped. then the existing object is deleted altogether and replaced by the new object. If an object to be added already exists and • If this flag is true and the overwrite flag is true. merge Boolean No Relevant to the Add action. Force delete is supported for service assemblies and nodes and force uninstall is supported for nodes. the old object's data is updated with the new object's data. If any problems occur moving the node to one of these states. TIBCO ActiveMatrix Administration . if any. the service assembly is deleted even if it is not in the Undeployed state. Default: false. then the existing object is overwritten by merging with the new object. and only if the overwrite flag was used and is true. and force is true.

There are two ways in which an object can be overwritten: it can be merged. username Examples String Yes The name of the ActiveMatrix user executing the task. objectSelector • objectSelector="//*" Process all objects.w3. If an object to be added already exists and this flag is true. The strategy used is determined by the merge flag. TIBCO ActiveMatrix Administration . This section contains examples of the AMXAdminTask task attributes and describes the effect of using the attributes. password Obfuscated String Yes The obfuscated password of the ActiveMatrix user executing the task. Note: The password is not masked when you type it into the command line.90 | Chapter 4 ActiveMatrix Administrator Interfaces Table 15 Options (Sheet 4 of 4) Attribute objectSelector Type String Req? No Description Specifies the set of objects to be processed. or created from scratch. • objectSelector=”/Environment[@name=’env1’]/Node[@name=’node1’]" Process node1 in environment env1.org/TR/xpath. See Creating an Obfuscated Password on page 28. The set of objects is defined by an XPath expression. The heuristic used to determine the order in which the objects are processed depends on the action attribute. If this attribute is not specified: • • All of the objects in the data file are processed. see http://www. overwrite Boolean No Relevant to the Add action. then the existing object is overwritten. Default: false. For information on the XPath language. • objectSelector="//Node" Process all nodes.

the interface processes node1 (depth-first search). With overwrite = true and merge = false. it deletes it. — The stop or uninstall fails. It deletes the existing env1 and replaces it with the new env1. TIBCO ActiveMatrix Administration . determines that it already exists. determines that it doesn’t exist. and updates the existing env1 with data from the new env1. and does nothing. and updates the existing node1 with data from the new node1. the interface processes env1. and does nothing. node1 is deleted. If you do a delete and • force = false. There are two possible outcomes: — The stop and uninstall are successful. node1 is in the Started state. The interface processes env1 and since env1 doesn’t support life cycle management. The interface then quits out of the delete command. The interface then processes node1. Your data file has environment env1 and a node node1. If you do an edit and • create = false. determines that it already exists. With overwrite = true and merge = false. determines that it already exists. the interface processes env1.AMXAdminTask 91 | overwrite and merge Assume you have a data file with environment env1 and node node1. The old node1 is deleted in the process. • • create Assume you have an environment env1 in the database. and attempts to stop it and then uninstall it. and does nothing. and adds node1 to env1. determine that it already exists. notices that it is in the Started state. it doesn’t exist yet and so it is just added. It then processes node1. create = true. determines that it already exists. and edits the data to match that of the new env1. force Assume you have an environment env1 and node node1 in both the database and the data file. determines that it doesn’t exist. the interface processes env1. When the interface processes node1 in the data file. • and edits the data to match that of the new env1. node1 is not in the uninstalled state so it cannot be deleted. It processes node1. determines that it already exists. You add both objects. If you then do another add with the same data file • With overwrite = false (merge is then ignored). determines that it already exists. and nothing in the database. the interface processes env1. It then processes node1. the interface processes env1.

You cannot perform any actions on the objects defined in this schema. There are two possible outcomes: — The stop and uninstall are successful. notices that it is in the Started state. Data File Schemas The data file schemas are located in AMX_ADMIN_HOME/2. The interface processes env1 and since env1 doesn’t support life cycle management. Default Connector Reference on page 199.2/schemas and are named • • • amxdata. the interface processes the node1 (depth-first search). Configuring Enterprise Assets on page 99. and attempts to stop it and then uninstall it. This section describes the data file schemas and the location of reference information for object attributes.92 | Chapter 4 ActiveMatrix Administrator Interfaces • force = true. and logger appenders. Supported Objects and Attribute Reference Table 16 lists the objects specified in the schema and provides links to the sections containing attribute reference information. node1 is not in the uninstalled state but it is forcefully deleted. amxdata_base.xsd • Reference format definitions. amxdata_detailed. permissions. Container Reference on page 204. Table 16 Supported Objects and Their Attribute Reference Sections Object AdminServer Container DefaultConnector Enterprise Attribute Reference Section Administrator Server Reference on page 165.xsd Details of shared resource definitions.xsd Full format definitions. The interface processes env1 and since env1 doesn’t support life cycle management. deletes it. — The stop or uninstall fails. Base format definitions. node1 is deleted. Data File The data file is an XML file that specifies attributes of the objects that are operated on by the AMXAdmin task.xsd amxdata_reference. TIBCO ActiveMatrix Administration . deletes it.

Managing Keystores on page 156. Resource Definition Reference on page 118. Permissions on page 145. Services Reference on page 238. Service Assembly Reference on page 224. Substitution Variables Tab on page 233. Node Reference on page 195. Messaging Server Reference on page 178. Configuring Messaging Bus on page 174. Local Substitution Variables Reference on page 212. Object Logging Configuration Reference on page 314. Users on page 138. Bound Machine Reference on page 110. Service Units Table Reference on page 231. Substitution Variables on page 116. Shared Resource Reference on page 209. Shared Resource Profiles Reference on page 234.AMXAdminTask 93 | Table 16 Supported Objects and Their Attribute Reference Sections Object Environment Group Keystore ListofSuperUser Logger Machine MessagingBus MessagingServer Node Permissions Service ServiceAssembly ServiceUnit SharedResource SharedResourceDefinition SharedResourceProfile SubstitutionVariable Topic UDDIServer User Attribute Reference Section Working with Environments on page 173. Superusers on page 138. Topics Reference on page 235. UDDI Server Reference on page 155. Groups on page 143. TIBCO ActiveMatrix Administration .

<project default="main"> <property file="login. build.xml file. single_node_data.command.properties"/> <taskdef name="AMXAdminTask" classname="com.tibco.ant. a node and its containers.AMXAdm inTask"/> . <target name="init" description="Set up Environment.administration.line.xml The tasks in build.94 | Chapter 4 Examples ActiveMatrix Administrator Interfaces This section contains an example build.xml add a machine.2/samples/. referenced in the build.xml" objectSelector="Environment/Node | Environment/Node/Container" overwrite="true" merge="true" createIfNotExists="true" force="true"/> </target> <target name="sr-add" description="Add Shared Resource Definitions"> <AMXAdminTask TIBCO ActiveMatrix Administration .xml file and an example data file. an environment. The machine is enabled for the environment. For more examples.. a shared resource definition. and the shared resource definition is enabled for the environment and the shared resource is enabled for the node. Machine. and a shared resource.xml.xml" objectSelector="Machine | Environment | Environment/MessagingBus/MessagingServer | Environment/Machine" overwrite="true" merge="true" createIfNotExists="true" failOnError="true" force="true"/> </target> <target name="node-add" description="Add Nodes and Containers"> <AMXAdminTask adminURL="http://localhost:8120/amxadministrator" username="${username}" password="${password}" action="add" dataFile="single_node_data. the containers are enabled for the node. see AMX_ADMIN_HOME/2.matrix. Messaging Bus"> <AMXAdminTask adminURL="http://localhost:8120/amxadministrator" username="${username}" password="${password}" action="add" dataFile="node_data..

. <Machine xsi:type="amxdata:Machine" hostName="sbodoff-lt" tibcoHome="C:/tibco" managementURL="service:jmx:jmxmp://sbodoff-lt:9998"/> <Environment xsi:type="amxdata:Environment" name="env1" description="desc"> <Machine hostName="sbodoff-lt" tibcoHome="C:/tibco"/> <SharedResourceDefinition name="conn8989"/> <MessagingBus <MessagingServer xsi:type="amxdata:MessagingServer" name="ms1" description="desc" clientID="" username="admin" password=""> <DirectConfiguration providerURL="tcp://localhost:7222" useXAConnectionFactory="false"/> </MessagingServer> </MessagingBus> <Node xsi:type="amxdata:Node" TIBCO ActiveMatrix Administration .AMXAdminTask 95 | adminURL="http://localhost:8120/amxadministrator" username="${username}" password="${password}" action="add" dataFile="node_data. a node named node1. a shared resource definition named conn8989.xml" objectSelector="SharedResourceDefinition | Environment/SharedResourceDefinition | Environment/Node/SharedResource" overwrite="true" merge="true" createIfNotExists="true" force="true"/> </target> </project> single_node_data. <amxdata_base:Enterprise . a messaging server named ms1. and a shared resource in the node. containers in the node.xml This data file creates an environment named env1..

0" managementPort="4432"> <Container type="com.soapbinding.matrix.matrix.runtime" version="2.tibco.0.0"> </Container> <Container type="com.tibco.0"> </Container> <SharedResource xsi:type="amxdata_reference:SharedResourceDefinition_reference" name="conn8989"/> <MessagingServer name="ms1"/> </Node> </Environment> <SharedResourceDefinition name="conn8989" xsi:type="amxdata:SharedResourceDefinition"> <HTTPSharedResourceDefinition port="8989" host="sbodoff-lt" connectionTimeoutMillis="20000" disableUploadTimeout="false" enableDnsLookups="true" maxPostSizeBytes="1000" maxThreads="150" minThreads="25" redirectPort="12346" /> </SharedResourceDefinition> </amxdata_base:Enterprise> TIBCO ActiveMatrix Administration .runtime" version="2.2" productVersion="2.javase.0.96 | Chapter 4 ActiveMatrix Administrator Interfaces name="node1" description="desc" hostName="sbodoff-lt" tibcoHome="C:/tibco" productInstallDirectory="C:/tibco/amx/2.2.

Options Table 17 Options (Sheet 1 of 2) Attribute action Type String Req? Yes Description One of the actions listed in Actions on page 77. Uninstall: depth first • Some actions are not performed against certain object formats (see Object Formats on page 82). Add and Edit are applied only to objects specified in full format. Stop. <AMXAdminConfigTask action="action" dataFile="dataFile" adminServerName="server" adminClusterName="cluster" username="username" password="password" [failOnError="{true|false}"] [objectSelector="XPath_Expression"] </AMXAdminTask> You authenticate from the command-line interface either by providing a username and obfuscated password in build. Undeploy: breadth first — Delete.xml or in response to a prompt.AMXAdminConfigTask 97 | AMXAdminConfigTask Ant Task Description Syntax Specifies the administrative action and objects on which the action is performed. Edit. adminClusterName adminServerName String String Yes Yes The name of the ActiveMatrix Administrator cluster. The order in which the action is applied to the objects is either breadth first or depth first. Start. — For the most part. • • Unless objectSelector is specified. The method used is determined by the action. Install. Activate. The name of the ActiveMatrix Administrator server. See Creating an Obfuscated Password on page 28. the action is applied to every object in the data file. The action is case insensitive. Deploy. — Add. Objects not in this format are skipped. TIBCO ActiveMatrix Administration . Deactivate.

The heuristic used to determine the order in which the objects are processed depends on the action attribute.org/TR/xpath. If this attribute is not specified: • • All of the objects in the data file are processed. See Creating an Obfuscated Password on page 28. Causes the Ant task to fail when an unrecoverable error is reported. TIBCO ActiveMatrix Administration . Specifies the set of objects to be processed. username String Yes The name of the ActiveMatrix user executing the task.98 | Chapter 4 ActiveMatrix Administrator Interfaces Table 17 Options (Sheet 2 of 2) Attribute dataFile failOnError objectSelector Type String Boolean String Req? Yes No No Description The absolute path to the XML file containing the object data. See Data File on page 92. The set of objects is defined by an XPath expression. password Obfuscated String Yes The obfuscated password of the ActiveMatrix user executing the task.w3. see http://www. Note: The password is not masked when you type it into the command line. For information on the XPath language.

software. page 114 Managing Users. page 137 Managing UDDI Servers. page 156 Managing ActiveMatrix Administrator Clusters.| 99 Chapter 5 Configuring Enterprise Assets This chapter describes how to configure the hardware. page 160 Working with Substitution Variables. Topics • • • • • • • Managing Machines. page 100 Managing Shared Resource Definitions. and other enterprise assets used by an ActiveMatrix runtime. Groups. page 167 TIBCO ActiveMatrix Administration . and Permissions. page 154 Managing Keystores.

Local Network Discovery Figure 13 on page 101 illustrates how you discover machines running on local networks using multicast or broadcast URLs. then broadcast or multicast to discover other machines in the subnet. and Management Ports on page 18. Discovery of machines on the same subnet is achieved using broadcast or multicast. Overview This section describes how ActiveMatrix Administrator discovers and binds to machines. ActiveMatrix Administrator supports discovery in a wide variety of network topologies which include point to point. you can use only the machines associated with that environment. Discovering Machines You can discover machines on the same subnet and on different subnets using search parameters that you define and save for reuse.100 | Chapter 5 Configuring Enterprise Assets Managing Machines You use ActiveMatrix Administrator to discover and bind to machines you want to include in the ActiveMatrix runtime. You associate each bound machine with one or more environments. To determine the current settings for the port number. Discovery of machines on a different subnet is achieved using JMX to tunnel to one machine on the subnet. When you configure an environment. By default. Discovery. TIBCO ActiveMatrix Administration . multicast. depending on configuration. Ask your network administrator for the multicast and broadcast IP addresses used in your network. see UDP. Some companies choose not to use broadcast addresses. The broadcast address for a subnet is determined by a combination of the subnet mask and network class defined by the network administrator. The default broadcast mask is often 255. the port on which the Management Daemon processes listen for requests sent using the UDP protocol is set to 1965. and broadcast. but it can be more or less in any network.

Bridged Network Discovery Figure 14 on page 102 illustrates how you discover machines running on a different subnet from ActiveMatrix Administrator.Managing Machines 101 | Figure 13 Local Network Discovery Admin Cluster 1 Legend AS M MD Administrator server Machine TIBCO Management Daemon AS1 on M1 AS2 on M2 User enters search parameters and discovers Management Daemon instances on remote machines MD3 on M3 Br oa dc as t/M ult ic as t MD5 on M5 MD8 on M8 Each Management Daemon process returns a datagram with the following information: • • • Management Daemon process name and description TIBCO home that the Management Daemon process is managing The Management Daemon’s discovery JMX address Then ActiveMatrix Administrator uses the discovery JMX addresses to query the Management Daemon processes for the management JMX address you can use to connect to and control the nodes on each machine. TIBCO ActiveMatrix Administration . That machine discovers other machines on its subnet using broadcast or multicast. First you connect to one machine using the JMX discovery URL and initiate the discovery process.

returns all discovered management JMX URLs to AS1. When you execute the search. you enter the hostname and JMX port for the Management Daemon you plan to use. Discovery. The format for the URL is: service:jmx:jmxmp://Hostname:Port To determine the current settings for the port number. ActiveMatrix Administrator uses this information to construct the JMX discovery URL. ActiveMatrix Administrator establishes the JMX connection with the Management Daemon process (step 1 in Figure 14). and Management Ports on page 18. Broa 2 dcas t/Mu lticas t In addition to the multicast or broadcast and UDP information. Then the Management Daemon process issues the broadcast or multicast discovery requests (step 2 in Figure 14). TIBCO ActiveMatrix Administration . on a different subnet XM /JM MX P J MD12 on M12 MD14 on M14 MD16 on M16 M16 broadcasts to subnet.102 | Chapter 5 Configuring Enterprise Assets Figure 14 Bridged Network Discovery Legend AS Administrator server M Machine MD TIBCO Management Daemon Admin Cluster 1 AS1 on M1 AS2 on M2 1 User enters JMX discovery URL and initiates discovery process with Management Daemon M16. see UDP.

where hostname is the literal hostname of the machine. 2. then you must manually discover and bind to the machine. the ActiveMatrix Administrator server starts up normally. If auto-bind has failed at startup. In order for automatic binding to occur. you select the ones you want to bind to. the ActiveMatrix Administrator server performs the following steps: 1. Up-to-date status on the bound machines and the ActiveMatrix software installed on the machines displays in the Machines list available in the Configure Enterprise Assets perspective.Managing Machines 103 | Binding Machines Of the available machines that meet your discovery search criteria. For details on how to bind machines. see Binding Machines on page 105. then the machine is listed in the Bound Machines table with status Connected | Available. If the machine was never bound in the past. a warning is logged and displayed. it is listed in the Bound Machines table with status Connected | Unavailable. Reads the Management Daemon configuration file and extracts the bind URL. If the machine was already bound in the past. If this operation fails for any reason. then it is not listed in the Bound Machines table. or if a ping hostname command fails. Automatically Binding to the ActiveMatrix Administrator Server Machine During startup of an ActiveMatrix Administrator server. There is no task in the server that attempts the auto-bind operation after server startup. the Management Daemon is not running. Auto-bind Success If the auto-bind operation is successful. then auto-bind fails. the server attempts to automatically bind to the machine on which the server is running. Auto-bind Failure The auto-bind operation is attempted only when the ActiveMatrix Administrator server starts up. the Management Daemon process on the machine must be running before the ActiveMatrix Administrator server is started. To bind to the machine. Binding connects the ActiveMatrix Administrator cluster to the ActiveMatrix installations that you use for your ActiveMatrix runtime. Attempts to bind to the machine (equivalent to a manual bind action as described in the preceding section). TIBCO ActiveMatrix Administration . If at that time. Whether the auto-bind operation is successful or not.

the ActiveMatrix runtime still runs but cannot be administered. A machine can be bound to more than one ActiveMatrix Administrator cluster. see Enabling Machines on page 182. Admin Cluster 2 administers Environment 2 and Environment 3. Machine. Environment 1 is administered by Admin Cluster 1 and Environment 2 and Environment 3 are administered by Admin Cluster 2. During the design and configuration phase of setting up your ActiveMatrix runtime. You can change the list of machines enabled in an environment at any time. changes in plan may require changes in the configurations you have set up. One ActiveMatrix Administrator cluster can administer multiple environments. If you disable a machine in an environment. and environments: • An environment is administered by only one ActiveMatrix Administrator cluster. for example. You define new environments using the Environment Definition screen available at the Configure Enterprise Assets perspective. • • If you bind a machine to more than one cluster. ActiveMatrix Administrator Cluster. TIBCO ActiveMatrix Administration . In Figure 15. you can install an environment’s nodes on any machine that is enabled in the environment. administration can resume. Specifically.104 | Chapter 5 Configuring Enterprise Assets Enabling Bound Machines in Environments For each bound machine. and Environment Relationships Figure 15 illustrates the possible relationships that can exist between ActiveMatrix Administrator clusters. For details on how to enable machines. when you bind the machine to the second cluster. the clusters must have different names. machines. you specify which machines are enabled in a given environment. Machine 1 is bound to Admin Cluster 1 and Admin Cluster 2. If you later enable the machine in the environment again. The environment can be administered from any of the ActiveMatrix Administrator servers within the cluster. You add new environments in the Configure Enterprise Assets perspective and then enable one or more machines. Otherwise. the first cluster’s configuration maintained by the machine is overwritten by the second cluster’s configuration and the following message appears on the Management Daemon console on that machine: "Will overwrite old datastore: firstcluster".

Machines. Click Discover. Select Configure Enterprise Assets from the Perspective drop-down list. TIBCO ActiveMatrix Administration . The Add Search Parameters dialog displays. and Environments Database1 Admin Cluster 1 Database2 Admin Cluster 2 Bo un d u Bo nd un Bo d Machine 1 Administer Administer Administer Machine 2 Environment 1 Environment 2 Environment 3 Binding Machines To bind machines to an ActiveMatrix Administrator cluster: 1. Click the Machines link. 2.Managing Machines 105 | Figure 15 Relationships between ActiveMatrix Administrator. Add search parameters 4. The Discover Machines dialog is displayed. 3. Click Add.

b.106 | Chapter 5 Configuring Enterprise Assets See Discovering Machines on page 100 and Add Search Parameters Reference on page 111 for details on specifying search parameters and for default values. — Bridged Searches for machines on a different subnet from the ActiveMatrix TIBCO ActiveMatrix Administration . select one of the following: — Local Searches for machines on the same subnet as the ActiveMatrix Administrator cluster. In the Subnet field. a. Enter a name and description to help you identify the purpose of this search parameter.

enter the hostname and JMX discovery port of the Management Daemon on one machine in that network. If you selected Bridged in the Subnet field.Managing Machines 107 | Administrator cluster. c. Enter the broadcast or multicast address and UDP port for the search. The parameter you added appears in the Search Parameters list. TIBCO ActiveMatrix Administration . d. e. Click Add.

You can view various details about the bound machines. Bridged searches iterate through the entire timeout period and then return the result. Select and bind machines 6. In the Discovered Machines table. The list of machines matching the search parameters displays in the Discovered Machines table. 7. In the Timeout field. select the machines to which you want to bind and click Bind. Each bound machine must be enabled in one or more environments. Command-Line Interface The discovery process described in the preceding section applies when you are binding using the graphical interface. When you use multiple search parameters. the combination functions as a union rather than an intersection. that is. Set the timeout value appropriately. The bound machines appear in the Bound Machines table on the left. Dismiss the dialog. and Management Ports on page 18) and provide it as an attribute when you bind the machine to the enterprise as follows: <Machine TIBCO ActiveMatrix Administration . Local searches return matching machines as soon as they are discovered. a. a superset is returned. Discovery.108 | Chapter 5 Configuring Enterprise Assets Select search parameters and search 5. Select one or more search parameters in the table. If you are using the command-line interface. Bridged searches usually need a larger timeout value. The amount of time it takes to discover machines varies depending on the network topology and load. you must determine the JMX management URL by examining the Management Daemon configuration file (see UDP. See Enabling Machines in an Environment on page 182 for details. See Bound Machine Reference on page 110. b. Click Search. specify a timeout value as desired.

Agent Down The machine is not accessible.Managing Machines 109 | xsi:type="amxdata:Machine" hostName="Hostname" tibcoHome="TIBCO_HOME" managementURL="service:jmx:jmxmp://Hostname:9998"/> Unbinding Machines You can bind and unbind machines to suit your needs. If you unbind a machine. ActiveMatrix nodes still runs but you can’t perform management actions because ActiveMatrix Administrator is not able to determine node status. This could be because it stopped or because the network connection failed. (On UNIX there can be more than one TIBCO home on a machine). Click the Machines link. Table 18 Bound Machines Reference Column Hostname TIBCO Home OS Status Description Name of the machine. The status of the machine. select the machines you want to unbind and click Unbind. Bound | Not Available The machine has been bound to the ActiveMatrix Administrator cluster but is not available. The operating system installed on the machine. In the Bound Machines table. 3. TIBCO ActiveMatrix Administration . 2. Select Configure Enterprise Assets from the Perspective drop-down list. To unbind machines from an ActiveMatrix Administrator cluster: 1. Possible values are: • • • Bound | Available The machine has been bound to the ActiveMatrix Administrator cluster and is available. Bound Machines Table This table displays view-only details about the machines in the Bound Machines table. Installation directory for ActiveMatrix software installed on this machine.

Discovery URL Management URL Operating System Daemon Name Daemon Description TIBCO ActiveMatrix Administration . The URL is empty if the machine has been bound through the command-line interface because the management URL is not discovered. The JMX URL used to communicate node status and send life cycle commands such as Stop and Start to the node. If the machine has been bound automatically (see Automatically Binding to the ActiveMatrix Administrator Server Machine on page 103). A JMX URL used to discover the management URL. (On UNIX there can be more than one TIBCO home on a machine). The user that bound the machine.110 | Chapter 5 Configuring Enterprise Assets Bound Machine Reference This area displays view-only details about the machine currently selected in the Bound Machines table. See Command-Line Interface on page 108. Installation directory for ActiveMatrix software installed on the machine. A short description of the Management Daemon process. Table 19 Bound Machine Reference Field Hostname TIBCO Home Bound By Description Name of the machine. The name of the Management Daemon process managing the TIBCO resources on the machine. the field displays (auto-bound). The operating system installed on the machine.

If you want to specify the network interface. The UDP port used for search. Discovery. See Bridged Network Discovery on page 101. Multicast or Broadcast Address UDP Port The address used for multicast or broadcast search. JMX Port TIBCO ActiveMatrix Administration .100. A short description of the search parameter. Default: 1965.Managing Machines 111 | Add Search Parameters Reference Table 20 Add Search Parameters Reference Field Name Description Network Interface Description A name for the search parameter. The discovery JMX port of the machine whose hostname you specified in Hostname field. Displays only when Bridged is selected for Subnet. and Management Ports on page 18. In most cases.xml file of the Management Daemon. Subnet A drop-down list specifying the subnet in which to search for machines: • • Hostname Bridged Search for machines running in a different subnet from the one where ActiveMatrix Administrator is running.106. Local Search for machines in the same subnet as the one where ActiveMatrix Administrator is running. Default: 9999. The JMX port is declared in the configuration. The machine must be running a Management Daemon process.107. The hostname of a machine on the subnet. Displays only when Bridged is selected for Subnet. use the value in the Management Daemon configuration file described in UDP. The name displays in the Search Parameters table. this field can be left blank. The name of the network interface used by the Management Daemon process. Default: 239.

Used for bridged subnet search only.107. TIBCO ActiveMatrix Administration . (On UNIX there can be more than one TIBCO home on a machine).112 | Chapter 5 Configuring Enterprise Assets Search Parameters Reference Table 21 Search Parameters Reference Column Name Multicast/ Broadcast Address UDP Port Description The name of the search parameter. Installation directory for ActiveMatrix software installed on the machine. A number of seconds after which the search stops if no machines are found using the search parameter or parameters.100.106. Discovery URL A JMX URL used to connect to the Management Daemon process on the machine to discover the management URL. Default: 239. The address used for multicast or broadcast search. The UDP port used for search. The JMX URL used to communicate node status and send life cycle commands such as Stop and Start to the node. Timeout Discovered Machines Reference Table 22 Discovered Machines Reference Column Name TIBCO Home Management URL Description The name of the machine. Default: 1965.

Managing Machines 113 | Table 22 Discovered Machines Reference (Cont’d) Column Status Description The binding status of the machine. Bound | Available The machine has been bound to the ActiveMatrix Administrator cluster and is available. The Management Daemon could not reach the machine. Bound | Not Available The machine has been bound to the ActiveMatrix Administrator cluster but is not available. • Not Bound The machine is not bound and a connection has been attempted. One of: • • • Binding ActiveMatrix Administrator is attempting to bind to the machine. TIBCO ActiveMatrix Administration . Rebinding might solve the problem.

How JNDI Shared Resource Definitions Are Used All shared resource definition types except JNDI are used when defining shared resources of the same type. JNDI shared resource definitions are used only when defining JDBC and JMS shared resource definitions. click New > Type. If a shared resource definition changes. For example.114 | Chapter 5 Configuring Enterprise Assets Managing Shared Resource Definitions A shared resource definition is a template for a shared resource. See Importing Shared Resource Definitions on page 218. all shared resources that reference it are updated with the changes when you restart the node on which the shared resource is installed. Shared resource definitions specify connection details for specific physical resources. When you define a JDBC or JMS shared resource definition. Click Shared Resource Definitions. If you don’t know what shared resource definitions are required by the services you plan to deploy. TIBCO ActiveMatrix Administration . you use an HTTP server shared resource definition when defining an HTTP shared resource. Creating multiple shared resources from one shared resource definition allows you to reuse definitions and control use of the resources at the node level. 3. From the Shared Resource Definitions screen you can perform the following tasks: • • • Creating a Shared Resource Definition on page 114 Editing a Shared Resource Definition on page 115 Deleting a Shared Resource Definition on page 117 Creating a Shared Resource Definition To create a shared resource definition: 1. Select Configure Enterprise Assets from the Perspective drop-down list. you can select the JNDI connection type. You then choose a JNDI shared resource definition that provides the necessary connection details. 2. where Type is one of the available shared resource types shown next. In the Shared Resource Definitions panel. you can import the definitions when you upload a service assembly. Once you have created shared resource definitions. you instantiate the definitions by installing them as shared resource objects in nodes.

In the right panel. In the right panel. Uninstall and reinstall the shared resources on all nodes that use this shared resource definition. To edit a shared resource definition: 1.Managing Shared Resource Definitions 115 | 4. 4. Click an existing shared resource definition. but other fields are editable. 5. Changes to a shared resource definition are picked up by the shared resources that use the definition after you restart the node on which they are installed. click Edit and then modify properties as described in Setting a Shared Resource Definition Property on page 115. Select Configure Enterprise Assets from the Perspective drop-down list. 6. 2. Click Save. See Installing and Uninstalling Shared Resources on page 208 for details. Click Shared Resource Definitions. 6. Editing a Shared Resource Definition Once a shared resource definition has been created you cannot edit its name. Setting a Shared Resource Definition Property There are three ways to set the value of a shared resource property: • • Inline on page 116 Substitution Variables on page 116 TIBCO ActiveMatrix Administration . Test the connection to a JDBC or JMS resource by clicking the Test Connection button. complete the details as explained in the reference section: — HTTP Server See HTTP Server Shared Resource Definition Reference on page 118 — Identity See Identity Shared Resource Definition Reference on page 121 — JDBC See JDBC Shared Resource Definition Reference on page 121 — JMS See JMS Shared Resource Definition Reference on page 125 — JNDI See JNDI Shared Resource Definition Reference on page 128 — Rendezvous See Rendezvous Shared Resource Definition Reference on page 132 — SSL Server SSL Server Shared Resource Definition on page 135 5. 3. Click Save.

the port number must be between 1 and 65536. The value %%subvarname%%:subvarvalue displays in the field. Clearing a Binding Between a Shared Resource Property and a Substitution Variable To clear a binding between a shared resource property and a substitution variable. Some reasons bind properties to variables are described in Customizing HTTP Shared Resource Definitions on page 11. an error citing the limitations on the value of the property displays. TIBCO ActiveMatrix Administration . Substitution Variables Certain properties of an HTTP server shared resource definition (see HTTP Server Shared Resource Definition Reference on page 118) can be bound to a substitution variable. For example. type the value in the property field. A dialog box containing substitution variables of the appropriate type displays. The value of a substitution variable is validated when it is applied. The icon displays to the left of the field. a. The icon to the left of the field disappears. click the field and type a new value.116 | Chapter 5 Configuring Enterprise Assets • Inline Shared Resources on page 117 To set the value of a shared resource property. Binding a Shared Resource Property to a Substitution Variable Shared resource properties can be bound to substitution variables (see Working with Substitution Variables on page 167). Click the icon to the right of the field. Click the row of a substitution variable to apply to the target property and close the dialog box. If invalid. To bind a shared resource configuration property to a substitution variable: 1.

disassociate from the node. In the case of shared resources. if an HTTP server shared resource definition is referencing an SSL server shared resource definition. uninstall the shared resource from the node (which also disassociates it from the node). use the service assembly. Import a shared resource definition from a service assembly. install the shared resource on a running node. click the desired definition. uninstall all shared resources that use the definition.Managing Shared Resource Definitions 117 | Shared Resources Binding a Shared Resource Property to a Shared Resource Sometimes the value of a shared resource property definition is another shared resource definition. Such properties are configured in two ways: • Clicking a link named Choose XXX Configuration. Deleting a Shared Resource Definition Before you can delete a shared resource definition. Clicking the link displays a dialog containing a list of matching definitions. associate with a node. For example. associate with a node. install the shared resource on a running node. you must first remove the reference to the SSL server definition from the HTTP server definition before you can delete the SSL server definition. where XXX is the type of shared resource definition. Associate with an environment. The following sections summarize the various scenarios in which a shared resource definition can be deleted: • • • Associate with an environment. • TIBCO ActiveMatrix Administration . The link is displayed when the number of items in the list is expected to be too long for a drop-down list. See Working with Shared Resources on page 207 for details. • To configure such properties: 1. uninstall the shared resource from the node. Associate with an environment. you must remove any references to it from other shared resource definitions or shared resources. Edit the resource definition as described in Editing a Shared Resource Definition on page 115. the SSL Configuration property of an HTTP server is an SSL Server shared resource definition. Click the link. delete the service assembly. For example. and click OK or select the definition from the drop-down list. Selecting from a drop-down list of definitions. 2.

Shared Resource Type Description HTTP Server. TIBCO ActiveMatrix Administration . Deleting a Shared Resource Definition To delete a shared resource definition: 1. The name must be unique across all shared resource definitions in all environments administered by the same ActiveMatrix Administrator cluster. Click Delete. Table 23 HTTP Server Shared Resource Reference Field Name Description The name of the resource. Default: HTTP Server Shared Resource Definition. Short description of the resource. Dereference the shared resource definition from the first definition or delete the first definition. Click Shared Resource Definitions.118 | Chapter 5 Configuring Enterprise Assets • Reference a shared resource definition from another shared resource definition. Select Configure Enterprise Assets from the Perspective drop-down list. Click an existing shared resource definition. 4. Resource Definition Reference HTTP Server Shared Resource Definition Reference An HTTP server shared resource describes an HTTP connection. Names are case sensitive. 2. 3. HTTP server shared resources are used by services.

Default: localhost. the default value localhost specifies the current machine. the request is redirected to the port you specify here. TIBCO ActiveMatrix Administration . If the HTTP connection supports non-SSL requests. Therefore make certain that all HTTP connection resources that use the same host name specify different port numbers. For machines that have only one network card. after accepting a connection. Default: 80. This property can be bound to a substitution variable. all network cards on the machine will listen for incoming HTTP requests on the specified port. Note that localhost signifies the host on which the ActiveMatrix node is running. If there is more than one network card on the machine. Maximum size allowed for HTTP POST data. For machines that have more than one network card. This property can be bound to a substitution variable. Port Port number on which to listen for incoming HTTP requests. Enable DNS Lookups Maximum Post Size Redirect Port Enables a Domain Name System (DNS) lookup for HTTP clients so that the IP address is resolved to a DNS name. Unit is milliseconds. Default: 0. Default: 8081. Only one HTTP server can be started on each port. This property can be bound to a substitution variable.Managing Shared Resource Definitions 119 | Table 23 HTTP Server Shared Resource Reference (Cont’d) Field Host Description Specifies the name of the host that accepts the incoming requests. for the specific URI the request is sending to be presented. Connection Timeout The number of milliseconds the connector waits. and you specify localhost in this field. this field specifies the host name of the card that will be used to accept incoming HTTP requests. and a request received requires SSL transport. so enable this field only when required. This can adversely affect throughput. not the ActiveMatrix Administrator server.

the ActiveMatrix node returns a ConnectionRefused exception to the client. an additional connection timeout period is used while a SOAP message is being executed. the additional timeout period is not used. This property can be bound to a substitution variable. Default: 10. Default: 75. TIBCO ActiveMatrix Administration . The HTTP server creates the number of threads specified by this parameter when it starts up. Default: No. Disable Upload Timeout? If not checked. Use SSL? Check to require SSL encrypted communication with the connection. Default: false (not checked). The field label is a link to the resource. Maximum Threads The maximum number of threads available for incoming HTTP requests. This property can be bound to a substitution variable. When a client sends a request that cannot be processed because no threads are available. If checked.120 | Chapter 5 Configuring Enterprise Assets Table 23 HTTP Server Shared Resource Reference (Cont’d) Field Minimum Threads Description The minimum number of threads available for incoming HTTP requests. The HTTP server will not create more than the number of threads specified by this parameter. This property can be bound to a substitution variable. SSL Configuration Name The SSL server shared resource to use for the connection.

The password used to access the private key. Names are case sensitive. The name must be unique across all shared resource definitions in all environments administered by the same ActiveMatrix Administrator cluster. See Public Key Identity. The drop-down list displays keystores already created in the Enterprise Assets > Keystores screen. Select from the drop-down list of keystore. When you choose an identity type. JDBC Shared Resource Definition Reference A JDBC shared resource describes a JDBC connection. Short description of the resource. Entry Alias Alias Password A private key in the keystore that identifies a user. Type the keystore URL or Browse to one by clicking the Browse button. Public Key Identity Keystore URL The URL to the keystore. Table 24 Identity Shared Resource Reference Field Name Description The name of the resource. Default: Identity. Shared Resource Type Description Identity Type IDENTITY. appropriate fields display for you to enter the values required: Public Key Identity A keystore provides the identity. JDBC connections are used by components and logging configurations TIBCO ActiveMatrix Administration .Managing Shared Resource Definitions 121 | Identity Shared Resource Definition Reference An identity shared resource contains identity information that is used to authorize a connection. Identity resources are used by SSL servers.

hsqldb. see Table 26 on page 123. The name must be unique across all shared resource definitions in all environments administered by the same ActiveMatrix Administrator cluster. Shared Resource Type Description Connection Type JDBC.jdbcDriver. When you select a driver.. Short description of the resource. Using Custom Drivers To use a custom JDBC driver. page 123 JDBC Connection Type JDBC Driver Required. The name of the JDBC driver class. follow the procedure described in Packaging and Installing Native Database Drivers in your installation manual. TIBCO ActiveMatrix Administration . appropriate fields appear for you to enter the values required: • • JDBC See JDBC Connection Type. Table 25 JDBC Shared Resource Reference Field Name Description The name of the resource. Names are case sensitive. the Database URL field is populated with a template for the URL of the driver. When you choose a connection type. Default: org. Default: JDBC Shared Resource Definition. For a list of drivers in the drop-down list. page 122 JNDI See JNDI Connection Type. See Enabling SSL Connections on page 124.122 | Chapter 5 Configuring Enterprise Assets You can configure a JDBC shared resource so that it communicates with the database server over an SSL connection. You can select from a drop-down list of supported drivers or type the name of a custom driver.

the value of this field is ignored.SQLServerDriver jdbc:tibcosoftwareinc:sqlserver://<hostname>:<port# >. You must supply the portions of the URL shown between angle brackets and remove the angle brackets. If the JDBC driver does not support connection timeouts. Default: 0.sqlser ver. A template of the URL is supplied for the driver you select in the JDBC Driver field or you can type the name of a custom URL. Most JDBC drivers support connection timeouts.hsqldb. The minimum value that can be specified is 0. see Table 26 on page 123.jdbc. Time (in seconds) to wait for a successful database connection.databaseName=<databaseName> TIBCO ActiveMatrix Administration . The maximum number of database connections to allocate. Table 26 Database Drivers and URL Templates Database HSQLDB Driver org.Managing Shared Resource Definitions 123 | Table 25 JDBC Shared Resource Reference (Cont’d) Field Database URL Description Required. Password Maximum Connections Login Timeout Password to use when connecting to the database. Default: jdbc:hsqldb:hsql://localhost:<port#>/<db_instancename>. For a list of templates. Default: Your username. JNDI Connection Type JNDI Configuration Name Datasource Name The JNDI Configuration shared resource definition that specifies the JNDI connection information. Username User name to use when connecting to the database. Default: 10. Only JDBC drivers that support connection timeouts can use this configuration field. The URL to use to connect to the database. The JNDI name of the data source that is registered in the JNDI provider.jdbcDriver URL Template jdbc:hsqldb:hsql://localhost:<port#>/<db_instancena me> Microsoft SQL Server DataDirect driver tibcosoftwareinc.

SI D=<db_instancename> jdbc:tibcosoftwareinc:oracle://host:port.SQLServerDriver URL Template jdbc:sqlserver://<host>:<port#>. TIBCO ActiveMatrix Administration .sybase.10 6)(PORT=2484)))(CONNECT_DATA=(SERVICE_NA ME=orcl)(SERVER=dedicated))) jdbc. Import the issuer certificate of the Oracle server’s certificate into the ActiveMatrix Administrator server and the ActiveMatrix node trusted certificate stores.microsoft.databaseName=<dat abaseName> SSL Sybase1 1. 2. Oracle and Sybase native drivers are not distributed with ActiveMatrix products and the driver class and URL template are not available in the drop-down lists for those fields.107.jdbc.SID=SID. To enable SSL connections on ActiveMatrix Administrator server and ActiveMatrix nodes: 1.jdbc .107.jdbc.url_template=jdbc:sybase:Tds:<host>:<port#>/ <databaseName> Driver com.7.Encr yptionMethod=SSL jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=( ADDRESS=(PROTOCOL=TCP)(HOST=10.106) (PORT=1521)))(CONNECT_DATA=(SERVICE_NAME =orcl)(SERVER=dedicated))) jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=( ADDRESS=(PROTOCOL=TCPS)(HOST=10. install the Oracle driver as described in the Packaging and Installing Native Database Drivers section in the Post-Installation Procedures in the installation manual for your product on the ActiveMatrix Administrator server machine and the machines on which you run ActiveMatrix nodes.7.SybDriver jdbc. Shut down the ActiveMatrix Administrator server and ActiveMatrix nodes.driver=com.sqlserver.driver.171.jd bc3. 3. Enabling SSL Connections SSL connections are supported only with Oracle databases. OracleDriver jdbc:tibcosoftwareinc:oracle://<hostname>:<port#>.oracle. If you are using the Oracle thin driver.124 | Chapter 5 Configuring Enterprise Assets Table 26 Database Drivers and URL Templates (Cont’d) Database Microsoft SQL Server native driver Oracle DataDirect driver SSL Oracle native driver1 oracle. type the driver class and URL into the fields and follow the Custom Drivers instructions in JDBC Driver on page 122.171.OracleDri ver tibcosoftwareinc.jdbc. To use the native drivers.

Managing Shared Resource Definitions 125

|

4. Perform the procedures described in Managing the Trusted Keystore on page 338 and Managing the Trusted Keystore on page 340. 5. In the ActiveMatrix Administrator UI, create a JDBC shared resource that uses the SSL URI .

JMS Shared Resource Definition Reference A JMS shared resource describes a JMS connection. JMS connections are used by services and references. SSL Configuration You can configure a JMS shared resource so that it communicates with the JMS server over an SSL connection. SSL communication is supported only when the connection type of the JMS shared resource is JNDI lookup. Direct connection to the JMS server is not supported. To create an SSL connection to the JNDI server configure the JNDI shared resource for SSL. A JMS shared resource can be enabled for both server and client verification. Server Verification The JMS client can verify the Enterprise Message Service server before creating a secure connection. To configure the Enterprise Message Service server for server verification, perform the steps in Configure Server Credentials on page 128.

TIBCO ActiveMatrix Administration

126

| Chapter 5

Configuring Enterprise Assets

Client Verification The Enterprise Message Service server can verify the JMS client before creating a secure connection. To configure the Enterprise Message Service server for client verification, perform the steps in Configure Client Credentials on page 128 and set the Client Certificate Password field. Table 27 JMS Settings Field Name Description The name of the resource. Names are case sensitive. The name of a shared resource definition must be unique across all shared resource definitions in all environments administered by the same ActiveMatrix Administrator cluster. Default: JMS Shared Resource Definition. Shared Resource Type Description Username JMS. Short description of the resource. User name used to create a connection from the connection factory. If the JMS provider does not require access control, this field can be empty. Not all JMS servers require user names and passwords. Refer to your JMS provider documentation and consult your system administrator to determine if your JMS server requires a user name and password. Password Password used to create a connection from the connection factory. If the JMS provider does not require access control, this field can be empty. Connection Type When you choose a connection type, appropriate fields display for you to enter the values required:
Direct See the Direct Connection Type section. JNDI See the JNDI Connection Type section.

Direct Connection Type Provider URL The server URL used to create the connection factory. This field is required only for connections to a TIBCO Enterprise Message Service server. See documentation for TibjmsConnectionFactory in TIBCO Enterprise Message Service product documentation (Javadoc) for more information. Default: tcp://localhost:7222.

TIBCO ActiveMatrix Administration

Managing Shared Resource Definitions 127

|

Table 27 JMS Settings (Cont’d) Field Connection Factory Description The factory for creating connections to the JMS server. Set to com.tibco.tibjms.TibjmsConnectionFactory for Enterprise Message Service or progress.message.jclient.ConnectionFactory for SonicMQ. Default: com.tibco.tibjms.TibjmsConnectionFactory. JNDI Connection Type JNDI Configuration Connection Factory A JNDI shared resource definition that specifies the JNDI connection information. The ConnectionFactory object stored in JNDI. This object is used to create a topic or queue connection with a JMS application. See your JNDI provider documentation for more information about creating and storing ConnectionFactory objects. Default: GenericConnectionFactory. To create an SSL connection to the JMS server, specify SSLGenericConnectionFactory or any other connection factory with SSL configuration provisioned on the JNDI server. Client Certificate Password The password of the client certificate used to verify the identity of SSL clients.

Enabling SSL for the JMS Server To enable SSL for the JMS server you configure server and client credentials. The supported file formats for the credentials are: • Single URI Identity — PKCS12 • Public Private Identity — PEM, P7 for public identity — P8 for private key • Trusted CAs — PEM

TIBCO ActiveMatrix Administration

128

| Chapter 5

Configuring Enterprise Assets

To enable SSL for the JMS server do the following tasks: Task A Configure Server Credentials To configure server credentials: 1. Create an SSL connection factory in the TIBCO Enterprise Message Service server by adding the following properties to ENV_HOME/ems/version/bin/factories.conf:
[SSLGenericConnectionFactory] type = generic url = ssl://7243 ssl_vendor = entrust61 ssl_verify_host = enabled ssl_trusted = certs/server_root.cert.pem ssl_identity = certs/client_identity.p12 ssl_verify_hostname = enabled ssl_expected_hostname = server

2. Restart the Enterprise Message Service server with the command
ENV_HOME/ems/version/bin/tibemsd –config tibemsdssl.conf.

Task B Configure Client Credentials To configure client credentials: 1. Edit ENV_HOME/ems/version/bin/tibemsdssl.conf and set the properties:
ssl_require_client_cert = disabled ssl_server_trusted = certs/client_root.cert.pem

2. Restart the Enterprise Message Service server with the command
ENV_HOME/ems/version/bin/tibemsd –config tibemsdssl.conf.

JNDI Shared Resource Definition Reference The JNDI shared resource provides a way to specify JNDI connection information that can be shared by other resources. This resource can be referenced in any resource that permits JNDI connections. JDBC and JMS shared resources can use JNDI connections.

TIBCO ActiveMatrix Administration

Managing Shared Resource Definitions 129

|

You can configure a JNDI shared resource so that it communicates with the JNDI server over an SSL connection. A JNDI connection can be only be enabled to perform server verification. You enable SSL by configuring security application properties as described in SSL Configuration Properties on page 130. Table 28 JNDI Shared Resource Reference Field Name Description The name of the resource. Names are case sensitive. The name must be unique across all shared resource definitions in all environments administered by the same ActiveMatrix Administrator cluster. Default: JNDI Shared Resource Definition. Shared Resource Type Description Context Factory JNDI. Short description of the resource. The name of the JNDI context factory. You can select from a drop-down list of supported initial context factory classes for accessing a JNDI service provider. (javax.naming.Context.INITIAL_CONTEXT_FACTORY) or type the name of a custom context factory class. Default: com.tibco.tibjms.naming.TibJmsInitialContextFactory. To use a custom context factory class, you must copy the custom JNDI driver JARs to two locations: •
AMX_ADMIN_HOME/2.2/lib/ext/ on the machine hosting the

ActiveMatrix Administrator server. This allows you to test the connection from the ActiveMatrix Administrator server. •
AMX_HOME/2.2/server/lib/ext/ on the machines hosting nodes that

will access the driver. This allows services running on those nodes to access the driver. Context URL The URL to the JNDI service provider (javax.naming.Context.PROVIDER_URL). An example URL is provided when one of the supported JNDI context factory classes is selected. See your JNDI provider documentation for the syntax of the URL. To configure SSL , specify tibjmsnaming://localhost:7243. See SSL Configuration Properties, page 130.

TIBCO ActiveMatrix Administration

130

| Chapter 5

Configuring Enterprise Assets

Table 28 JNDI Shared Resource Reference (Cont’d) Field Username Description User name for logging into the JNDI server (javax.naming.Context.SECURITY_PRINCIPAL). If the JNDI provider does not require access control, this field can be empty. Password for logging into the JNDI server (javax.naming.Context.SECURITY_CREDENTIALS). If the JNDI provider does not require access control, this field can be empty. You can add and define application properties as needed. The name of the property. Names are case sensitive. Default: Application_Property. Type Value Data type of the property. Value of the property.

Password

Application Properties Name

SSL Configuration Properties In the Application Properties area, add the following properties and values prepending each property name with com.tibco.tibjms.naming. Table 29 JNDI SSL Application Properties Property security_protocol ssl_vendor ssl_enable_verify_host Value ssl entrust61 true Notes ssl is the only security protocol supported. Required. entrust61 is the only supported vendor. Required. Specifies whether the client should verify the server’s certificate. Required.

TIBCO ActiveMatrix Administration

Managing Shared Resource Definitions 131

|

Table 29 JNDI SSL Application Properties (Cont’d) Property ssl_enable_verify_hostname Value true Notes Set to true if the name on the server's certificate must be verified against the server's hostname. If the server's hostname is different than the name on the certificate, SSL connection will fail. The name on the certificate can be verified against another name by specifying the ssl_expected_hostname property. Contains the CAs the client trusts for server verification. Required only if ssl_enable_verify_host is set to true. Hostname given at the time of creating the certificate. Required only if ssl_enable_verify_hostname is set to true. Required. May be specified for SSL tracing. May be specified for SSL debug tracing.

ssl_trusted_certs

/certs/server_root.cer.pem

ssl_expected_hostname

server

ssl_trace ssl_debug_trace

true true

TIBCO ActiveMatrix Administration

132

| Chapter 5

Configuring Enterprise Assets

Rendezvous Shared Resource Definition Reference A Rendezvous shared resource describes a TIBCO Rendezvous transport. Rendezvous resources are used by services and references. See the TIBCO Rendezvous documentation for more information about specifying these fields. Rendezvous character encoding represents the encoding of Rendezvous messages when they are sent across the network.The default Rendezvous character encoding is UTF-8. To change Rendezvous character encoding to another encoding such as ISO-8859-1, add the following line to AMX_HOME/data/envName/nodeName/bin/envName_nodeName.tra file for all nodes on which Rendezvous shared resources are installed:
java.property.com.tibco.matrix.rv.character.encoding=ISO8859-1

Table 30 Rendezvous Shared Resource Reference (Sheet 1 of 3) Field Name Description The name of the resource. Names are case sensitive. The name must be unique across all shared resource definitions in all environments administered by the same ActiveMatrix Administrator cluster. Default: Rendezvous Shared Resource Definition. Shared Resource Type Description Daemon Network Service Connection Type Rendezvous. Short description of the resource. The host name followed by the socket number of the machine on which the Rendezvous daemon is running. The network to be used by the Rendezvous daemon. Contains the host name, IP address, network name, or interface name. Service name in one of the following formats: service_name or port_number. When you choose a delivery method, appropriate fields display for you to enter the values required:
Certified See Certified, page 133. Distributed Queue See Distributed Queue, page 133. Reliable No additional settings are required when you choose Reliable.

See TIBCO Rendezvous documentation for details.

TIBCO ActiveMatrix Administration

Default: 0. it receives inbound messages immediately. The relay agents store inbound certified messages and labeled messages (and other messages related to certified delivery features) on behalf of their disconnected client programs. The name and location of the persistent ledger file that tracks certified messages. the certified message ledger is kept in memory only. Relative worker weights assist the scheduler in assigning tasks. it assigns the task to the available worker with the greatest worker weight. Default: No. Default: 1 Description Sync Ledger File? Require Old Messages? TIBCO ActiveMatrix Administration . When a client is connected. Relay agents are useful when clients are disconnected from the network from time to time. Distributed Queue CMQ Name Worker Weight The name of the distributed queue. Specifies whether to keep the ledger file synchronous with the current messages. Default: No. not to BusinessWorks process engines). When the scheduler receives a task. This name is in the same format as Rendezvous subject names. The weight of the worker (this pertains to the worker processing queue requests. These messages will be resent. Message Timeout The time limit (in seconds) for certified message delivery. This name is in the same format as Rendezvous subject names. Relay Agent Name of the relay agent to use. Specifies whether to require the retention of messages for which delivery has not been confirmed.Managing Shared Resource Definitions 133 | Table 30 Rendezvous Shared Resource Reference (Sheet 2 of 3) Field Certified CM Name Ledger File The name of the delivery-tracking session. If not specified.

If the worker process does not complete in the specified period. Cooperating distributed queue transports use relative scheduler weight values to elect one transport as the scheduler. members with higher scheduler weight take precedence. The value must be positive. Scheduler Activation When the heartbeat signal from the scheduler has been silent for this interval (in seconds). the scheduler reassigns the message to another worker. All members with the same name must specify the same value for this parameter. Acceptable values range from 1 to 65535.1. Default: 0. TIBCO ActiveMatrix Administration . Scheduler Heartbeat The scheduler sends heartbeat messages at this interval (in seconds). Default: 1. the worker cannot accept additional tasks until it completes one or more of them.134 | Chapter 5 Configuring Enterprise Assets Table 30 Rendezvous Shared Resource Reference (Sheet 3 of 3) Field Worker Tasks Description Sets the task capacity for the worker (this pertains to the worker processing queue requests). The value must be positive. the member with the greatest scheduler weight takes its place as the new scheduler. All members with the same name must specify the same value for this parameter. Scheduler Weight Weight represents the ability of this member to fulfill the role of scheduler. Default: 10 Worker Complete Time The amount of time the scheduler waits for a worker process to complete.3. Task capacity is the maximum number of tasks that a worker can accept. relative to other members with the same name. Default: 0. Default: 0. When the number of accepted tasks reaches this maximum.

The location must be the URL of an object accessible over the network. Trusted Certificate Authorities File Type Certificate Store URL Password Only the Java keystore type is supported. Specifies the number of bits in the key used to encrypt data. Short description of the resource. • • • • • Client Authentication Required? No Restriction No Export Grade At Least 128 More Than 128 At Least 256 When checked clients are required to present their digital certificate before connecting to the HTTP server. Default: SSL Server Shared Resource Definition. SSL server shared resources are used by HTTPS server shared resources. TIBCO ActiveMatrix Administration . the Trusted Certificate Authorities fields will be displayed. The greater the number of bits in the key (cipher strength). The password for the certificate store. Names are case sensitive. Table 31 SSL Server Shared Resource Reference Field Name Description The name of the resource. The name must be unique across all shared resource definitions in all environments administered by the same ActiveMatrix Administrator cluster. Shared Resource Type Description Identity Cipher Strength SSL Server.Managing Shared Resource Definitions 135 | SSL Server Shared Resource Definition An SSL server shared resource describes an SSL server. The location of the certificate store. the more possible key combinations and the longer it would take to break the encryption. An identity shared resource of type public key identity. When checked.

136 | Chapter 5 Configuring Enterprise Assets TIBCO ActiveMatrix Administration .

2. To manage users. You can manually add users and groups to the realm. 3. Groups. a user with the appropriate permissions can define which users and groups should have access to ActiveMatrix Administrator features and ActiveMatrix runtime objects. Hence. Log in to ActiveMatrix Administrator as a superuser. Click a button based on the type of configuration you want to perform: — Users on page 138 — Groups on page 143 — Permissions on page 145 Users and Groups Overview Users and groups can be searched for. • Database Realm Read-write access provided within ActiveMatrix Administrator. 4. Authorization (or permission) to access ActiveMatrix objects can be assigned to users and groups. Managing Users in the Database Authentication Realm on page 139. Authorization for all ActiveMatrix runtime objects is provided by the ActiveMatrix Administrator server. An ActiveMatrix user is a person that has an authentication credential. groups. The asterisk wildcard is supported in all search areas in Users and Groups. Groups. TIBCO ActiveMatrix Administration .Managing Users. and Permissions 137 | Managing Users. Using ActiveMatrix Administrator. and permissions: 1. and Permissions The ActiveMatrix Administrator supports centralized authentication and authorization. and optionally edited. Click the Users & Groups link. An ActiveMatrix group is a collection of users. The availability of editing capability depends on the type of authentication realm you have chosen: • Local XML File Realm Read-only access provided within ActiveMatrix Administrator. See Adding a User to a Local XML File Realm on page 31 and Group Hierarchy on page 143. Select Configure Enterprise Assets from the Perspective drop-down list. viewed. a server must be running and connectivity must be available from each ActiveMatrix node for any kind of management action on the nodes.

Password Required. A group had been granted Owner permission for an object. For example: • • • An owner of an object is on vacation. If a superuser is deleted from LDAP server. I18n characters are allowed. the two users left the company. The object's permissions were unchanged during this time. Edit functionality is limited to that provided by your LDAP vendor. A string containing at least one character. Caution must be exercised when assigning superuser privileges. the users must be present in the LDAP server. leaves the company. • LDAP Realm Read-only access provided within ActiveMatrix Administrator. From then on. and each one got removed from that group. for the LDAP realm. because of the potential for a rogue superuser to vandalize the system. User ID Required. All superusers are users in the ActiveMatrix Administrator authentication realm.138 | Chapter 5 Configuring Enterprise Assets • TIBCO Administrator Realm Read-only access provided within ActiveMatrix Administrator. but effectively it has no owner. For example. A current login session still treats the user as a superuser. A string identifier that is unique within the realm. Superusers can manage objects that have no owners. The group initially had 2 users. You must use TIBCO Administrator to edit users and groups (roles). or is otherwise unreachable. Users A user has the following attributes: • • Superusers ActiveMatrix Administrator defines a category of users—called superusers—that have implicit Owner permission (see Permissions on page 145) for all objects. Over a period of time. TIBCO ActiveMatrix Administration . For this reason. the object has no explicit owner. An owner of an object removes himself from the Owner permissions and saves the object. ActiveMatrix Administrator does not allow adding groups as superusers. the user loses superuser privilege only in the next login session.

Type a wildcard expression in the text box to the left of the Search button. and Permissions 139 | Resetting the Superuser Password When you create an ActiveMatrix Administrator cluster you specify the superuser username and password. 2. 3. If you forget the superuser password. A paginated list of users matching the expression is returned. Creating a User To create a user: 1. 4. Click the Users & Groups link. type the user identifier. reset user passwords. Click the Search button. Start the ActiveMatrix Administrator UI. Run AMX_ADMIN_HOME/2. add and remove superusers. and add and remove users from groups. When the wizard prompts you for a superuser username and password enter a new username and password.2/bin/createadminserver and add a second ActiveMatrix Administrator server to the ActiveMatrix Administrator cluster. 5. 4. Select Configure Enterprise Assets from the Perspective drop-down list. The new user you specify is added to the user database. Start an ActiveMatrix Administrator server. Managing Users in the Database Authentication Realm In the database authentication realm you can search for users. Follow the procedure in Changing a User Password on page 141 to reset the password for the original user for whom you forgot the password. 6. Searching for Users To search for users: 1. In the User ID field. 5.Managing Users. Click New. 3. Log in using the new username and password. 2. 3. Groups. TIBCO ActiveMatrix Administration . The maximum number of users is limited to 500. 2. create and delete users. you can reset it as follows: 1. Click the Users button.

In the Confirm Password field. Select Configure Enterprise Assets from the Perspective drop-down list. Drag the users from the left to the right panel. Select the user in the Users list. Click Save. Click the Search button. 3. e. Click the Users & Groups link. c. 2. 4. In the Password field. Adding Superusers To add superusers: 1. type a password with at least one character. Deleting a User To delete a user: 1. 5. Click the Users button.140 | Chapter 5 Configuring Enterprise Assets 6. type the same password. Select Configure Enterprise Assets from the Perspective drop-down list. 3. Click Delete. f. 8. 2. TIBCO ActiveMatrix Administration . Click the Users & Groups link. Click the Users button. Click the Superusers button. The Superusers dialog displays. d. 3. b. Dismiss the dialog. Removing Superusers To remove superusers: 1. 7. Optionally type a wildcard expression to narrow the list of users. Click the Add Users button. 4. Select Configure Enterprise Assets from the Perspective drop-down list. Click Save. a. 2. Click the Users button. Click the Users & Groups link.

2. The Superusers dialog displays. Click the Superusers button. Select Configure Enterprise Assets from the Perspective drop-down list. Changing a User Password There are two ways to change a user password: • Click the Profile link in the top right corner of the header. Click the Users & Groups link. The Reset Password dialog is displayed and requires you to enter the new password and confirm the password. The groups are added to the Groups list in the right panel. Click the Reset Password button. Click the Users link. 4. Groups. Select groups from the Add Group list and drag them to the right panel. Users area • To add a user to groups through the Users area: 1. Adding a User to Groups Before you can add a user to a group you must add a root group or subgroup following the procedures described in Managing Groups in the Database Authentication Realm on page 144. 1. There are two ways to add a user to groups: through the Users area and through the Groups area. a. 2. TIBCO ActiveMatrix Administration . Select a user in the Users list. Click Save. b. Click the Users & Groups link. Dismiss the dialog.Managing Users. 3. The Add Groups dialog displays. 6. b. and Permissions 141 | 4. Click the Search button. The Change Password dialog is displayed and requires you to enter the old and new passwords and confirm the new password. Click Remove in the row of the user to remove. 5. Click the Add Groups button in the Groups area. Select the user in the Users list. A superuser can change the password of any user. Select the Configure Enterprise Assets perspective: a. Type a wildcard expression in the text box. Click the Users button. d. a. c.

6. 2. 5. The Add Users dialog displays. a. Type a wildcard expression in the text box. Click the Groups link. Select Configure Enterprise Assets from the Perspective drop-down list. The users are added to the Users list in the right panel. Click the Users & Groups link. 2. 3. 3. Click the Add Users button in the Users area. Click Save.142 | Chapter 5 Configuring Enterprise Assets Groups area To add a user to groups through the Groups area: 1. Click the Users link. Removing a User from a Group 1. Select users from the Add User list and drag them to the right panel. Click the Search button. Select a group in the Groups list. TIBCO ActiveMatrix Administration . 4.

if the Company Staff group contains the City Staff group. Group Hierarchy Groups can exist within a hierarchy. Select a user in the Users list. For example. The parent-subgroup relationship always implies membership inclusion from subgroups to parent groups. the members of the City Staff group are also members of the Company Staff group. A string identifier that is unique among all groups. A string that describes the group. and Permissions 143 | 4. The existence and nature of a group hierarchy depends on the type of the authentication realm. ActiveMatrix Administrator allows multiple groups at the root level. Database The Database authentication realm supports a group hierarchy. I18n characters are allowed. In the Groups list on the right panel. A group is either at the root level. TIBCO ActiveMatrix Administration . click the Remove link in the row containing the group from which you want to remove the user. Description Optional. or it has one and only one parent group. For information on the file syntax. Only a direct member (see Member Type on page 145) can be removed. A change in the structure in LDAP is reflected in ActiveMatrix Administrator. Groups A group is a collection of users. LDAP The LDAP authentication realm supports a group hierarchy as it exists in your LDAP server.Managing Users. Groups. Members A list of users that belong to that group. groups do not have a common root element. 5. but only after a cache-expiry interval. This section describes the group hierarchy available in each type of authentication realm. A user may belong to zero or more groups. see Adding a User to a Local XML File Realm on page 31. Local XML File The local XML file authentication realm supports a default group named administrator and you can add groups. It has the following attributes: • • • Name Required. In the Database realm. A group can contain zero or more subgroups.

TIBCO ActiveMatrix Administration . The group is added to the Groups list as a subgroup of the parent group. 2. Select Configure Enterprise Assets from the Perspective drop-down list. 5. Click a root group to serve as the parent group. 3. Click New Subgroup. In the Description field. Click Save. Select Configure Enterprise Assets from the Perspective drop-down list. type a name for the group. 6. Click the Groups button. 6. 3. In TIBCO Administrator. 7. Select New Root Group. 8. In the Name field. Managing Groups in the Database Authentication Realm In the database realm you can create root and subgroups and delete groups. Click the Users & Groups link. type a description.144 | Chapter 5 Configuring Enterprise Assets TIBCO Administrator The TIBCO Administrator authentication realm supports a group hierarchy. Creating a Subgroup To create a subgroup: 1. Creating a Root Group To create a root group: 1. 4. Deleting a Group or Groups Within ActiveMatrix Administrator you can delete groups only within the Database realm. 7. In the Name field. 5. In the Description field. Click the Users & Groups link. type a name for the group. 4. 2. type a description. Click Save. Click the Groups button. a role (functionally identical to a group) can have multiple parents.

If the group is a parent group. The group description. The following sections describe the interaction of permissions with the following ActiveMatrix Administrator features: • • User Interface Functions on page 145 Objects on page 147 User Interface Functions Permissions affect user interface functions in the following ways: • ActiveMatrix Administrator displays UI components for which you have View permission. The type of membership the user has in the group. One of: • • Direct The user is a direct member of this group. 2. The group or groups are removed from the Groups list. Figure 16 on page 146 shows the UI components for which permissions can be granted. This occurs when the group is a parent group and the user is a member of a subgroup of the parent group. The name of the group. the subgroups are promoted to parent-level status. Permissions Access to ActiveMatrix Administrator features is enabled by permissions. Select the group or groups in the Groups list.Managing Users. Required. ActiveMatrix Administrator displays ActiveMatrix objects for which you have View permission. Click Delete. Groups. Groups List Reference Table 32 Groups List Reference Column Name Description Member Type Description Required. Remove Link to remove the user from group. and Permissions 145 | To delete a group: 1. Indirect The user is an indirect member of this group. • TIBCO ActiveMatrix Administration .

ActiveMatrix Administrator disables or hides UI components. Figure 16 Components TIBCO ActiveMatrix Administration . if you do not have permission for the corresponding actions.146 | Chapter 5 Configuring Enterprise Assets • You are only allowed to perform actions for which you are authorized. such as buttons and menu items.

and so on have permissions that grant access of a particular type to a single user or a group of users. stop. deploy. activate. uninstall. Edit Allows you to Configure an Environment > Nodes Deploy to an Environment > Service Assemblies — Perform all the actions allowed with View permission — Edit the properties of an object. edit. Groups. — Add items to a parent object. install. deactivate. and Permissions 147 | Objects Objects such as nodes. — Perform runtime actions such as start. ActiveMatrix Administrator allows you to set permissions on objects displayed in the following screens: • Configure Enterprise Assets — Environment Definition > Environments — Shared Resource Definitions > Shared Resource Definitions — Servers > UDDI Servers — Keystores > Keystores — Administrator Cluster > Plug-ins • • Permission Types There are three types of permissions: view.Managing Users. See Adding Child Objects to a Parent Object on page 148. and owner. Each type provides different capabilities: • • View Allows you to browse objects in a list or view details for the objects. shared resource definitions. and undeploy on the object • Owner Allows you to — Perform all the actions allowed with Edit permission — View and modify the object’s permissions — Delete the object TIBCO ActiveMatrix Administration .

Objects To display object permissions: 1. provided that you do not already gain ownership by virtue of the parent object’s permissions. Click one or more objects. Click the Set Permission button. Displaying Permissions UI Components To display permissions for the UI components in Figure 16 on page 146: 1. Navigate to one of the screens described in Objects on page 147 containing the objects to which you are adding the permission. The Set Permission button displays. Select Configure Enterprise Assets from the Perspective drop-down list. Click the Users & Groups link. When you add an object. 3.148 | Chapter 5 Configuring Enterprise Assets Adding Child Objects to a Parent Object You are allowed to add child objects to parent objects for which you have Edit permission. both add and remove are accomplished from the same dialog. Click a UI component in the Permissions tree. add and remove are accomplished with two different dialogs. then you can add a node to that environment. Since environments have no parent. the you are granted Owner permission for that object. enterprise permissions cover them. For a single object. 2. Click the Permissions button. TIBCO ActiveMatrix Administration . For example. or any other type of object that belongs to an environment. Granting Edit permissions to the enterprise allows you to create environments. Additionally. 4. as well as multiple objects. Setting Permissions You can set permissions for single objects. service assemblies. shared resource definitions. For multiple selections. if a you have Edit permission for an environment. its parent’s permissions are copied into that new object. Figure 11 on page 81 illustrates the parent-child relationships supported by ActiveMatrix Administrator. 3. 2.

click the Users button. click the Groups button. c. a. a. Display permissions as described in Displaying Permissions on page 148. To add a permission for a user. d. Click Save. To narrow the list of users or groups. b. click the Edit button over the permissions table. type a wildcard expression in the text box and click Search. The Add Users and Groups to Permissions dialog displays. 2. To add a permission for a group. To add permissions for a runtime object. Select one or more users or groups in the list and drag to a permission type box in the right column. To add permissions for a UI component. Groups.Managing Users. and Permissions 149 | Single Object To add permissions to users or groups for one or more UI components or a single object: 1. TIBCO ActiveMatrix Administration . click the Set Permission button over the object table.

To overwrite all existing permissions with your new selections. Click Save. To add a permission for a group. Select one or more users or groups in the list and drag to a permission type box in the right column. To add a permission for a user. click the Overwrite existing permissions? checkbox. The Add Users and Groups to Permissions dialog displays. type a wildcard expression in the text box and click Search. b. Display permissions as described in Displaying Permissions on page 148.150 | Chapter 5 Configuring Enterprise Assets Multiple Objects To add permissions to users or groups for multiple objects: 1. select Set Permission > Add Permission over the object table. click the Groups button. To add permissions for runtime objects. To narrow the list of users or groups. a. click the Users button. 2. d. e. c. TIBCO ActiveMatrix Administration .

Multiple Objects To remove permissions from users or groups for multiple objects: 1. Display permissions as described in Displaying Permissions on page 148.Managing Users. Groups. Click the icon next to the users or groups for which you want to remove a permission. and Permissions 151 | Removing Permissions Single Object To remove permissions from users or groups from a UI component or a single object: 1. 3. 2. Display permissions as described in Displaying Permissions on page 148. TIBCO ActiveMatrix Administration . Click Save.

b.152 | Chapter 5 Configuring Enterprise Assets 2. — Remove from Edit permissions Removes only Edit permissions for the TIBCO ActiveMatrix Administration . To remove permissions for runtime objects. The Remove Permissions dialog displays. select Set Permission > Remove Permission over the object table. Click Deselect All to turn off all selections. — Remove from View permissions Removes only View permissions for the selected users or groups. Click Select All to select all users and groups. Use the option buttons at the bottom of the dialog to select the type of permission to remove for the selected users: — Remove from all permissions Removes all permissions for the selected users or groups. a.

and Permissions 153 | selected users or groups.Managing Users. — Remove from Owner permissions Removes only Owner permissions for the selected users or groups. c. Groups. TIBCO ActiveMatrix Administration . Click Save.

Click the Edit button in the server details panel and edit the server details according to the descriptions in Table 33 on page 155 TIBCO ActiveMatrix Administration . Select the UDDI server in the UDDI Servers list. XML-based framework for describing services. Select Configure Enterprise Assets from the Perspective drop-down list. TIBCO ActiveMatrix supports secure access to UDDI servers.4). For information on how to enable secure connections to UDDI servers. Editing a UDDI Server To edit a UDDI server: 1. UDDI servers enable service providers to publish service listings and consumers to discover service providers. 2. Specify the server details according to the descriptions in Table 33 on page 155. see Enabling Secure Connections to UDDI Servers on page 351. Adding a UDDI Server To add a UDDI server: 1. the format of the URLs are described in the Installation Summary section (2. 2. Click the Add button.154 | Chapter 5 Configuring Enterprise Assets Managing UDDI Servers UDDI is a platform-independent. you can publish ActiveMatrix services (see UDDI Publishing on page 273) to the UDDI servers registered as an enterprise asset. 3. 2. discovering businesses. To perform all tasks described in this section: 1. the UDDI server must also be enabled in the environment (see Enabling UDDI Servers in an Environment on page 184). In the Monitor & Manage perspective. Before a service can be published. Click the Servers link.2) of TIBCO ActiveMatrix Registry Installation Guide and the registry startup scripts in the Command-line Scripts section (2. If you are using TIBCO ActiveMatrix Registry. and integrating business services. Click Save. This section describes how to manage UDDI servers.3.

Password for the specified user. Specifies the HTTP proxy host to be used for accessing the UDDI server. if one is required. Click Save. if one is required. TIBCO ActiveMatrix Administration . UDDI Server Reference Table 33 UDDI Server Reference Field Name Inquiry URL Publish URL Username Password Authentication Model Description The name of the UDDI server. Removing a UDDI Server To remove a UDDI server: 1. The provided username and password are used as the authentication credentials. Use Proxy? Host Port Use an HTTP proxy to access the UDDI server.Managing UDDI Servers 155 | 3. Specifies the password for the proxy host for HTTP proxy authentication. the Host. and Proxy fields are displayed. Port. Default: 8080. Specifies the HTTP proxy port to be used for accessing the UDDI server. When checked. Select the UDDI server in the UDDI Servers list. The URL to use when publishing to the UDDI server. The URL to use when performing inquiries on the UDDI server. Username. Click the Remove button. 2. Name of the user that has publish access to the UDDI server. The mechanism to use to authenticate with the UDDI server: • Basic Authentication Use basic authentication to authenticate with the UDDI server. Username Password Specifies the user name for the proxy host for HTTP proxy authentication.

It is called a trusted certificate because the keystore owner trusts that the public key in the certificate belongs to the identity identified by the subject (owner) of the certificate. • Trusted certificate This type of entry contains a single public key certificate. these aliases distinguish among the different ways in which the entity may authenticate itself.156 | Chapter 5 Configuring Enterprise Assets Managing Keystores Keystores Overview A keystore is a database of keys and certificates. See Identity Shared Resource Definition Reference on page 121 and SSL Server Shared Resource Definition on page 135. For example. the entity may authenticate itself using different certificate authorities. Private keys and certificate chains are used by a given entity for self-authentication. which is optionally stored in a protected format to prevent unauthorized access. An alias may also identify the purpose of the key. TIBCO ActiveMatrix Administration . This type of entry can be used to authenticate other parties. A keystore password is required to access or modify the keystore. which serve as identities for participants in SSL sessions. Identifying Keystore Entries Each entry in a keystore is identified by an alias. In the case of private keys and their associated certificate chains. Keystore Entries A keystore has two types of entries: • Private key This type of entry holds a cryptographic private key. An alias is could also be named after a particular role in which the keystore owner uses the associated key. Keystores contain keystore entries. or using different public key algorithms. It is also accompanied by a certificate chain for the corresponding public key. Certificates of trusted entities are typically imported into a keystore as trusted certificates.

Type a name and description. 4. those keys cannot be recovered. Click Save. An internal keystore is one that has been uploaded into the database of the ActiveMatrix Administrator server. 2. Reloading a keystore file is supported on internal keystores. TIBCO ActiveMatrix Administration . 3.. 2. Select the keystore and click Open. which may or may not be the same as the password that protects the keystore's overall integrity. each private key in the keystore can be protected using its own individual password. button next to the Location field and navigate to the directory containing the keystore. Click the Keystores link. which should be several words long. If the password is lost. An external keystore is a reference to a keystore via a URL. Type the password used to access the keystore in the Password field. Click New > Internal Keystore. Select Configure Enterprise Assets from the Perspective drop-down list. Click the Browse. The private keys are encrypted using the keystore password. 5.Managing Keystores 157 | Protecting Keystore Entries The private keys in a keystore are stored in encrypted form to make it difficult to disclose these keys inappropriately. The URL can point to a keystore managed by another ActiveMatrix Administrator server or a keystore in a file system. Keystore Types Keystores are internal or external. From the keystores screen you can perform the following tasks: • • • • • Creating an Internal Keystore on page 157 Creating an External Keystore on page 158 Deleting a Keystore on page 158 Editing a Keystore Description on page 158 Reloading an Internal Keystore on page 158 Creating an Internal Keystore To create an internal keystore: 1. a.. To manage keystores: 1. In addition.

3. Click New > External Keystore. 4. Click the Browse button to the right of the Keystore Location field and browse to the location of the keystore. select an internal keystore. 2. Edit the description. Type a name and description. a. Reloading an Internal Keystore To reload an internal keystore: 1. Click Save. 4. Select a keystore from the Keystores table. 4. Click the Edit button on the right. TIBCO ActiveMatrix Administration . 3. Click Delete.158 | Chapter 5 Configuring Enterprise Assets Creating an External Keystore To create an external keystore: 1. In the Keystore URL field. In the Keystores table. 3. Editing a Keystore Description To edit a keystore’s description: 1. type a URL (protocol http: or file:) that when accessed returns a keystore file. 1. Click Save. Type the password used to access the keystore in the Password field. To URL format for a keystore in an ActiveMatrix Administrator server is: http://hostname:port/amxadministrator/keystorefetch?name=keystorename. 2. 2. 2. Select the keystore and click Open. Deleting a Keystore To delete a keystore. Click the Reload Keystore button on the right. Select a keystore from the Keystores table.

Managing Keystores 159

|

Keystore Reference
Table 34 Keystore Reference Field Name Type Description Password Description The name that identifies the keystore. The type of the keystore: External or Internal. A short description of the keystore. The password used to access the keystore.

TIBCO ActiveMatrix Administration

160

| Chapter 5

Configuring Enterprise Assets

Managing ActiveMatrix Administrator Clusters
To manage ActiveMatrix Administrator clusters: 1. Select Configure Enterprise Assets from the Perspective drop-down list. 2. Click the Administrator Cluster link. The Administrator Cluster screen displays. The heading of the screen is Administrator Cluster (cluster: server) where cluster is the cluster whose properties are accessed and server is the ActiveMatrix Administrator server to which you are connected. 3. Click a link based on the type of configuration you want to perform: — Database Details on page 160 — Monitoring Configuration on page 161 — Log Services on page 161 — Plug-ins on page 161 — ActiveMatrix Administrator Servers on page 163

Database Details
A database configuration describes the connection attributes of the database containing ActiveMatrix Administrator configuration and runtime data. The attributes are configured when you create the ActiveMatrix Administrator cluster and first server (see Creating the First ActiveMatrix Administrator Server on page 26). In the Database Details screen, the attributes are read-only. To view the database configuration, click the Database Details link. To update the database configuration, follow the procedure in Updating the Database Configuration on page 49. Table 35 Database Configuration Reference Field Driver URL Username Password Description The name of the JDBC driver class. The URL used to connect to the database. The database user name. A password for the database user.

TIBCO ActiveMatrix Administration

Managing ActiveMatrix Administrator Clusters 161

|

Monitoring Configuration
For information on how to configure monitoring, see Enabling Monitoring on page 242.

Log Services
For information on how to configure log services, see Working with Log Services on page 300.

Plug-ins
TIBCO ActiveMatrix Administrator is extensible. This means that other TIBCO products can add functionality, such as new perspectives and new screens within the standard perspectives, to ActiveMatrix Administrator. The product-specific functionality is added to ActiveMatrix Administrator by uploading and deploying a plug-in containing new features. The plug-in is packaged as a WAR file. You can deploy, start, stop, and undeploy plug-ins without restarting the ActiveMatrix Administrator server. A plug-in automatically gets deployed to all other servers. Also, the state of a plug-in is the same on all servers. Both the Metrics Manager (see Metrics Manager Server on page 243) and the Log Service and Log Viewer (see Working with Log Services on page 300 and Using the Log Viewer on page 316) are implemented as plug-ins to ActiveMatrix Administrator. This section describes how to manage the life cycle of a plug-in. Deploying a Plug-in Only one version of a plug-in can be deployed at any point in time. There are two ways to deploy a plug-in: automatically and manually. To automatically deploy a plug-in, copy the WAR file containing the plug-in to the AMX_ADMIN_HOME/plugins directory. Plug-ins are automatically started when they are deployed. To manually deploy a plug-in: 1. Click the Plug-ins link. 2. Click Deploy. 3. Click Browse.... Navigate to a directory containing the plug-in and select the plug-in WAR file.

TIBCO ActiveMatrix Administration

162

| Chapter 5

Configuring Enterprise Assets

4. Click Open. 5. Click Upload. 6. Click OK. Undeploying a Plug-in Plug-ins are automatically stopped when they are undeployed. To undeploy a plug-in: 1. Click the Plug-ins link. 2. In the Plug-ins table, select the plug-in you want to undeploy. 3. Click Undeploy. You cannot undeploy a plug-in by deleting the WAR file from the AMX_ADMIN_HOME/plugins directory. Starting and Stopping a Plug-in To start or stop a plug-in: 1. Click the Plug-ins link. 2. In the Plug-ins table, select the plug-in. 3. Click Start or Stop.

TIBCO ActiveMatrix Administration

Managing ActiveMatrix Administrator Clusters 163

|

Plug-ins Reference Table 36 Plug-ins Reference Column Display Name Version State Uploaded By Uploaded Date Description The name of the plug-in. The version of the plug-in. The state of the plug-in. The user that uploaded the plug-in. The date the plug-in was uploaded.

ActiveMatrix Administrator Servers
This section describes how to mange ActiveMatrix Administrator servers once you have already created the first server in a cluster (see Creating the First ActiveMatrix Administrator Server on page 26). Creating an ActiveMatrix Administrator Server The first ActiveMatrix Administrator server in a cluster is created with the ActiveMatrix Administrator server creation utility. The ActiveMatrix Administrator server creation action creates additional server replicas within the cluster. The primary reason to create ActiveMatrix Administrator servers is to achieve fault-tolerance. See TIBCO ActiveMatrix Administrator Servers and Clusters on page 5. To create an ActiveMatrix Administrator server: 1. Click the Administrator Servers link. 2. Click the New button on top of the Administrator Servers table. 3. Provide values for the properties described in Table 38 on page 165. 4. When you are finished editing, click the Save button. The newly created ActiveMatrix Administrator server is automatically installed on the machine.

TIBCO ActiveMatrix Administration

164

| Chapter 5

Configuring Enterprise Assets

Deleting an ActiveMatrix Administrator Server There are various reasons why you might want to delete an ActiveMatrix Administrator server. For example, you may want to use that machine on which the server is running for another purpose, and create a replacement server on another machine. When you delete a server, the database entries for the server are also deleted. All runtime configuration data, however, is preserved. A server can only be deleted when it has the following status: Installed/Stopped, Install Failed, Delete Failed, or Unknown. To delete an ActiveMatrix Administrator server: 1. Click the Administrator Servers link. 2. Select a server in the Administrator Servers table. 3. Click the Delete button. Starting and Stopping ActiveMatrix Administrator Servers To start or stop ActiveMatrix Administrator servers: 1. Click the Administrator Servers link. 2. Select one or more servers in the Administrator Servers table. 3. Select Start or Stop. If you stop all the servers in a cluster, the runtime administered by that cluster becomes unusable. Editing Administrator Server Properties To edit the properties of an ActiveMatrix Administrator server: 1. Click the Administrator Servers link. 2. Select an server in the Administrator Server table. 3. Click the Edit button. 4. Edit the non-read-only properties described in Table 38 on page 165. 5. Click Save.

TIBCO ActiveMatrix Administration

Managing ActiveMatrix Administrator Clusters 165

|

Administrator Servers Reference Table 37 Administrator Servers Reference Column Name Hostname TIBCO Home Status Description The name of the ActiveMatrix Administrator server. The name of the machine on which the ActiveMatrix Administrator server is running. Installation directory for ActiveMatrix software installed on this machine. (On UNIX there can be more than one TIBCO home directory on a machine). The status of the ActiveMatrix Administrator server: • • • • •
Installing Server configuration files are in the process of being generated on

the machine.
Installed/Stopped The server configuration files have been installed on the

machine but it is not running.
Running The server has been started successfully. Uninstalling Server configuration files are in the process of being removed

from the machine.
Unknown The status of the server cannot be determined.

Administrator Server Reference Table 38 Administrator Server Reference Field Name Management Port Description The name of the ActiveMatrix Administrator server. Port on which the ActiveMatrix Administrator server listens and responds for management and control functions using JMX protocol. Default: 8110 HTTP Port Port on which the web container that hosts the ActiveMatrix Administrator user interface listens and responds. Default: 8120 Description A short description of the ActiveMatrix Administrator server.

TIBCO ActiveMatrix Administration

166

| Chapter 5

Configuring Enterprise Assets

Table 38 Administrator Server Reference (Cont’d) Field Hostname Description The name of the machine hosting the server. One of the machines listed in the drop-down list containing the names of machines bound to the cluster. A Management Daemon process must be running on the machine before you create the ActiveMatrix Administrator server. TIBCO Home Installation directory for ActiveMatrix software installed on this machine. (On UNIX there can be more than one TIBCO home directory on a machine).

TIBCO ActiveMatrix Administration

2. Click Save. Click the New button above the Substitution Variables table. Click the Edit button above the Substitution Variables table. 2. To delete a substitution variable: 1. Click the variable in the table. type a name. In the Value column type a value. 3. 3. Edit the variable’s value. In the Type column. The name must be unique and the name and value are case sensitive. The value of a substitution variable can be overridden at the node level (see Working with Substitution Variables on page 211). Deleting a Substitution Variable Deleting a substitution variable being used in a shared resource is not allowed. Select Configure Enterprise Assets from the Perspective drop-down list. Creating a Substitution Variable To create a substitution variable: 1. 2. A new row is added to the table. 2. Click the Delete button above the table. Editing a Substitution Variable Value To edit a substitution variable value: 1. 5. To work with substitution variables: 1. Click the variable in the Substitution Variables table. Click the Substitution Variables link. In the Name column. TIBCO ActiveMatrix Administration . 4.Working with Substitution Variables 167 | Working with Substitution Variables Substitution variables are global variables defined at the enterprise assets level and are bound to shared resource definition properties (see Binding a Shared Resource Property to a Substitution Variable on page 116) such as HTTP servers. select the variable’s type from the drop-down list.

and start the service assembly after you reinstall the shared resource. The new value does not take effect in a running node using that shared resource definition. There are two caveats you should keep in mind when editing substitution variables used by shared resource definitions: • Changing the value of a substitution variable does not trigger validation of shared resource definition properties. redeploy. changing the value could invalidate the shared resource definition. You must restart the node or reinstall the shared resource. If the substitution variable is used in a resource referenced by a service assembly running on that node.168 | Chapter 5 Configuring Enterprise Assets 4. • TIBCO ActiveMatrix Administration . which would prevent you from installing the shared resource definition on a node. Therefore. Click Save. you must undeploy.

page 184 Working with Shared Resource Definitions. Topics • • • • • • • Environments Overview. page 174 Enabling Machines. page 186 TIBCO ActiveMatrix Administration . It provides procedures for adding and deleting environments and configuring hardware and software used by the environments.| 169 Chapter 6 Defining Environments This chapter explains at a high level how to define environments. page 171 Working with Environments. page 182 Enabling UDDI Servers. page 170 Creating an Environment. page 173 Configuring Messaging Bus.

2. To access environment definition functions: 1. Short description of the environment. The user that created the environment. TIBCO ActiveMatrix Administration .170 | Chapter 6 Defining Environments Environments Overview This chapter explains how to define environments. Description Created By Created On Description Name of the environment. The next chapter explains how to work with an environment’s nodes. The date the environment was created. Select Configure Enterprise Assets from the Perspective drop-down list. From the environment definition screen you can perform the following tasks: • • • • • • Creating an Environment on page 171 Working with Environments on page 173 Configuring Messaging Bus on page 174 Enabling Machines on page 182 Enabling UDDI Servers on page 184 Working with Shared Resource Definitions on page 186 Environments Reference Table 39 Environments Reference Field Name. and the containers and shared resources required by each node. Click the Environment Definition link.

Click Save. even those administered by different ActiveMatrix Administrator clusters. 2. Enter a name and description for the environment. TIBCO ActiveMatrix Administration . Click the New button over the Environments table. Each environment created on a machine must have a unique name.Creating an Environment 171 | Creating an Environment To create an environment perform the following in the environment definition screen: 1. 3.

See Configuring Messaging Bus Settings on page 174. The name can contain only alphanumeric characters. underscores. The node’s name. The name must also be unique among environments on one machine. including environments created in different ActiveMatrix Administrator clusters. To enable an asset. and click Save. you must enable one or more machines in the environment. hyphens.172 | Chapter 6 Defining Environments Environment Reference Table 40 Environment Reference Field Name Description Required. check the Yes radio button in the row containing the asset you want to enable. TIBCO ActiveMatrix Administration . See Enabling Machines on page 182 for details. you must specify that the asset is enabled in the environment. Configure Messaging Bus Settings Before you can configure an environment’s nodes. Before you can configure a new environment’s nodes. you must also configure the environment’s Messaging Bus settings to define the transport for messages between the various nodes and containers. The name must be unique among all environments administered by the same ActiveMatrix Administrator cluster. These include: • • • Machines UDDI servers Shared resource definitions In order to use these assets within a particular environment. Enable Assets Certain assets used by environments are specified at the enterprise level. Names are not case sensitive. The name must be a valid directory name in the Windows and UNIX operating systems. Description A description for the environment. Spaces are not permitted. When you are configuring an environment each of the asset types contains a table of available assets and information on whether they have been enabled in the environment. and dots (periods). click the Edit button over the table listing the assets.

containers.Working with Environments 173 | Working with Environments At the environment level. TIBCO ActiveMatrix Administration . 2. Click Delete. Editing an Environment To edit an environment: 1. Edit the Description field. Confirm the deletion. Select an environment in the Environments table. Click Save. Click the Edit button. First uninstall any installed nodes. Select an environment in the Environments table. 3. See Installing and Uninstalling Nodes on page 192 for details. Click the General Information link. 2. 4. Deleting an Environment You can’t delete an environment if any of its nodes are installed. and shared resources are also deleted. When you delete an environment all the defined nodes. you can delete an environment and change the environment’s description. To delete an environment: 1. 5.

Click Edit. 2. you can also configure Messaging Bus properties at the node level. Select an environment in the Environments table.174 | Chapter 6 Defining Environments Configuring Messaging Bus You must define a Messaging Bus for each environment and configure its quality of service setting. Once nodes have been added to an environment. 4. Session and Thread Pools. In addition. Although there is no adverse implication of mismatch in QoS setting across different nodes QoS changes should be applied uniformly to across the environment. Configuring Messaging Bus Settings Each environment has one Messaging Bus. A typical distributed in-out message exchange it is comprised of two JMS messages (one for request and other for reply). you create o one or more messaging servers that you want to use for the environment. perform the following in the environment definition screen: 1. Or if one or more nodes in an environment have been restarted after changes to QoS configuration while some other nodes have not been restarted. on page 359. This may happen if environment is configured with multiple Messaging Bus configurations using different QoS settings. Choose the desired setting for — Quality of Service See Quality of Service on page 174. The selected QoS applies to each message in a message exchange. Messaging servers can be shared across multiple environments. Quality of Service The quality of service (QoS) setting determines message delivery qualities for message exchanges. any changes to the QoS must be carefully considered. When you configure the Messaging Bus. An individual TIBCO ActiveMatrix Administration . 3. The Messaging Bus uses TIBCO Enterprise Message Service servers to provide messaging services between nodes in the environment. Click the Messaging Bus link. It is important to note that QoS applies to each JMS message that is sent. See Appendix C. Message exchanges may not be impacted if nodes in an environment are using different QoS settings. Click Save. 5. To configure the Messaging Bus for an environment. (These are called messaging servers).

node1 restarted after a QoS change may start sending messages using Best Effort QoS while node2 which did not restart may continue to send messages using At Most Once QoS. For example. messages are delivered when the node is up (whether or not the Enterprise Message Service server continues running without restarting in the interim). Best Effort Also known as Reliable Delivery. messages are delivered when the node is up. Duplicate messages can be delivered if Messaging Bus fails to acknowledge the message. Throughput performance is not as good as At Most Once and Best Effort. At Least Once Also known as Persistent. or if acknowledgement is not received by the server. A message confirming message receipt by the server is sent to the message sender (and this adversely affects performance). This is because messages are stored for delivery when the server restarts. Messages are guaranteed to be delivered at least once. The characteristics of Best Effort delivery are: • • • Messages can be dropped if the server has undelivered messages and is then restarted. Messages are resent if the Enterprise Message Service server or target node is down. Messages are logged to persistent storage. provided the Enterprise Message Service server continues running without restarting in the interim. If the target node is down.Configuring Messaging Bus 175 | node uses the QoS setting that it retrieves from the database during startup. • • • TIBCO ActiveMatrix Administration . Duplicate messages can be delivered if Messaging Bus fails to acknowledge the message. If the target node is down. Messages are not logged to persistent storage. or if acknowledgement is not received by the server. Best Effort mode has the best throughput performance of the available quality of service modes. Messages are resent if the Enterprise Message Service server or target node is down. The characteristics of At Least Once delivery are: • Messages are not dropped if the server has undelivered messages and if server is restarted.

Managing Messaging Servers You must configure a connection to one or more TIBCO Enterprise Message Service servers used for an environment’s Messaging Bus. See TIBCO Enterprise Message Service product documentation and Starting the TIBCO Enterprise Message Service Server on page 22 for details. messages are delivered when the node is up. Select an environment in the Environments table. In the Messaging Bus screen you can perform the following tasks: • • Adding a Messaging Server to an Environment on page 176 Removing a Messaging Server from an Environment on page 181 Adding a Messaging Server to an Environment 1.176 | Chapter 6 Defining Environments At Most Once Also known as non-persistent. It is only when authorization is in effect that performance slows with At Most Once mode. 2. The name must be unique within the environment. The panel on the right displays configuration fields. To manage an environment’s messaging servers: 1. Messages are resent if the Enterprise Message Service server or target node is down. Enter a name and description. Duplicate messages cannot be delivered (Messaging Bus discards messages if the JMXRedelivered header is set). 2. In the Messaging Servers area. provided the Enterprise Message Service server continues running without restarting in the interim. Click the Messaging Bus link. Messages are not logged to persistent storage. click Add. If the target node is down. If authorization is turned off in the TIBCO Enterprise Message Service product. The characteristics of At Most Once delivery are: • • • Messages can be dropped if the server has undelivered messages and is then restarted. you must install and configure TIBCO Enterprise Message Service software. there is little difference in throughput performance between Best Effort and At Most Once. TIBCO ActiveMatrix Administration . Before you can add and configure connections to messaging servers.

TIBCO ActiveMatrix Administration . Complete the values according to the descriptions in Table 41 on page 178. select one of the following and complete the values as appropriate: — Direct Defines a direct connection to the server. then you must create a JNDI Shared Resource as described in Managing Shared Resource Definitions on page 114 and then select the JNDI Configuration. 4. 6. You see the Choose JNDI Configuration dialog.Configuring Messaging Bus 177 | 3. Select a JNDI Configuration from the list and click Choose. — JNDI Defines a connection based on JNDI lookup. You return to the Messaging Bus dialog. as follows: a. In the Connection Type field. Click the JNDI Configuration link. If you select JNDI. Click Save. b. 5.

Description Reconnect Attempt Count Reconnect Attempt Delay Connection Type When you choose a connection type. 1 The amount of time to delay between attempts to reconnect to the messaging server. 1 Password used to create a connection to the connection factory. EMS Username EMS Password User name used to create a connection to the connection factory. fields display for you to enter the values required for the connection type. Names are not case sensitive. A short description of the messaging server. Applies only to connections of type Direct. JNDI See JNDI Connection. The number of attempts that should be made to connect to the messaging server.1 The type of the connection to the messaging server: • • Direct See Direct Connection. leave this field empty. If a password has not been defined. A name that is unique across all messaging servers and shared resource definitions in all environments administered by the same ActiveMatrix Administrator cluster.178 | Chapter 6 Defining Environments Messaging Server Reference Table 41 Messaging Server Reference Field Name Description Required. 1 TIBCO ActiveMatrix Administration . Applies only to connections of type Direct.

Configuring Messaging Bus 179 | Table 41 Messaging Server Reference (Cont’d) Field Direct Connection Description TIBCO ActiveMatrix Administration .

TIBCO ActiveMatrix Administration . 1Once • • The following use cases may be considered useful: • • Adding a second URL to enable reconnection Restarting all nodes in environment after applying provider URL changes. nodes are created within an environment. Under some circumstances it is quite useful. For example. you should change the host portion of the Provider URL to a fully-qualified hostname and confirm the server port. any modification of the provider URL must be carefully considered. see the API documentation for TibjmsConnectionFactory in TIBCO Enterprise Message Service product documentation.flight message exchanges may result in orphan requests or replies depending on the location of consumers and providers in running nodes and consumer and providers in restarted nodes. Message exchanges between nodes pointing to old server may continue seemingly inconsistent with broken interaction with nodes using the new server. Message exchanges between nodes using the new server may take place seemingly inconsistent with broken interaction with nodes using the old server. Default: tcp://localhost:7222 The default setting for the Provider URL works in the following circumstances: • • All nodes created in the environment are collocated with the TIBCO Enterprise Message Service server The TIBCO Enterprise Message Service server is configured to use the default port of 7222 Since in most cases all nodes in an environment are collocated with the TIBCO Enterprise Message Service server. For more information. Changing the provider URL to a completely different server has the following implications: • • Message exchanges between nodes may break down between nodes using the old server and nodes using a new server.180 | Chapter 6 Defining Environments Table 41 Messaging Server Reference (Cont’d) Field Provider URL Description The server URL used to create the connection factory. In. adding second a URL to enable reconnection.

2. Changes to the JNDI configuration change are considered safe with no implications since it is only a conduit to lookup the connection factory.Configuring Messaging Bus 181 | Table 41 Messaging Server Reference (Cont’d) Field JNDI Connection JNDI Configuration Choose a JNDI shared resource definition that specifies the JNDI connection information. the connection factory is used to make the actual connection. Description 1. Default: GenericConnectionFactory. See Provider URL on page 180. see JNDI Shared Resource Definition Reference on page 128. Removing a Messaging Server from an Environment 1. See Enabling Secure Communications Between Nodes and Messaging Servers on page 347. Connection Factory The ConnectionFactory object stored in JNDI. Client Certificate Password The password of the certificate of messaging server clients. In the Messaging Servers area. See your JNDI provider documentation for more information about creating and storing ConnectionFactory objects. For information on how to create a JNDI shared resource definition. Click Remove. Only nodes that have restarted after the configuration changes were applied use the modified parameter. TIBCO ActiveMatrix Administration . Nodes that have not been restarted continue to use the old parameter. Any modification of the parameter takes effect when nodes in the environment are restarted. select a messaging server. The implications of modifying the connection factory are identical to those for modifying the provider URL change because the provider URL is embedded in the connection factory.

2. Before you can define nodes in an environment. If the machine you want to use does not appear in the list. you must enable the machines where you want to install the nodes. 3. Click Edit. then you must first bind it to the ActiveMatrix Administrator cluster. To specify which machines are enabled and disabled for an environment. with 1. Click the Machines link.000 containers installed across them. Click Edit. Machines are specified at the enterprise assets level. Each machine where ActiveMatrix software is installed has one or more Management Daemon process. Windows machines have one TIBCO home.182 | Chapter 6 Defining Environments Enabling Machines When you plan an environment. 2. Click Save. Select an environment in the Environments table. perform the following in the environment definition screen: 1. you decide where its nodes (and their containers and shared resources) will be installed. Click the Yes radio button next to the machines you want to enable. TIBCO ActiveMatrix Administration . UNIX machines can have more than one. To enable machines in an environment: 1.000 nodes and 10. See Binding Machines on page 105 for instructions. Disabling Machines in an Environment To disable machines in an environment: 1. one for each TIBCO home. From the Machines screen you can perform the following tasks: • • Enabling Machines in an Environment on page 182 Disabling Machines in an Environment on page 182 Enabling Machines in an Environment The Machines link in the Environment Definition screen shows a list of all machines bound to the ActiveMatrix Administrator cluster. A well-developed environment might span 300 machines located anywhere in the network.

The version of the available features. 3. When you expand a machine node. Machines Reference The Machines table contains the machines available to the selected environment. Click Save.Enabling Machines 183 | 2. Installation directory for ActiveMatrix software installed on this machine. Software Type Version Enabled? The type of the features available in the installation directory. The properties of the features on each machine are described by the columns listed in Table 42. Indicates whether the machine is enabled for this environment. Click the No radio button next to the machines you want to disable. (On UNIX platforms there can be more than one TIBCO home on a machine). Table 42 Machines Reference Column Name TIBCO Home Description The name of the machine. under the directory are the ActiveMatrix installation version and the features in the ActiveMatrix installation. TIBCO ActiveMatrix Administration .

Click Save. Click the No radio button next to the UDDI servers you want to disable. Click Save. you can publish ActiveMatrix services in the Monitor & Manage perspective. Select an environment in the Environments table. Disabling UDDI Servers in an Environment To disable UDDI servers in an environment: 1. perform the following in the environment definition screen: 1. See UDDI Publishing on page 273. Click Edit.184 | Chapter 6 Defining Environments Enabling UDDI Servers UDDI servers are specified at the enterprise assets level. Once you have enabled a UDDI server for an environment. Click the Yes radio button next to the UDDI servers you want to enable. The properties of the features on each server are described by the columns listed in Table 43 on page 185. TIBCO ActiveMatrix Administration . 3. 2. 3. Click the UDDI Servers link. To specify which UDDI servers are enabled in an environment. UDDI Servers Reference The UDDI Servers table contains the UDDI servers available to the selected environment. 2. See Managing UDDI Servers on page 154. Click Edit. 2. From the UDDI Servers screen you can perform the following tasks: • • Enabling UDDI Servers in an Environment Disabling UDDI Servers in an Environment Enabling UDDI Servers in an Environment To enable UDDI servers in an environment: 1.

The provided username and password are used as the authentication credentials. TIBCO ActiveMatrix Administration . The mechanism to use to authenticate with the UDDI server: • Basic Authentication Use basic authentication to authenticate with the UDDI server.Enabling UDDI Servers 185 | Table 43 UDDI Server Reference Column Name Publish URL Authentication Model Description The name of the UDDI server. Enabled? Indicates whether the machine is enabled for this environment. The URL to use when publishing to the UDDI server.

Only parent resources like HTTP. do not appear. Click Save. All referenced resources. 2. Select an environment in the Environments table. JDBC. and so on are visible in the Shared Resource Definitions screen. 2. such as Identity and JNDI. 3. JMS. TIBCO ActiveMatrix Administration . Click the Shared Resource Definitions link. Click Edit. Click the Yes radio button next to the shared resource definitions you want to enable and the No radio button next to the shared resource definitions you want to disable. See Managing Shared Resource Definitions on page 114. To specify which shared resource definitions are enabled in an environment. Rendezvous. perform the following in the environment definition screen: 1. Such resources are automatically enabled by enabling the parent resource. From the Shared Resource Definitions screen you can perform the following tasks: • Enabling and Disabling Shared Resource Definitions in an Environment Enabling and Disabling Shared Resource Definitions in an Environment To enable or disable a shared resource definition in an environment: 1.186 | Chapter 6 Defining Environments Working with Shared Resource Definitions Shared resource definitions are specified at the enterprise assets level.

| 187 Chapter 7 Configuring Environments This chapter describes how to configure the nodes managed by the environment. page 211 Working With Logging Configurations. Topics • • • • • • Working with Nodes. and the connector. and keystore entries contained in the nodes. page 202 Working with Shared Resources. shared resources. page 188 Working with the Default Connector. page 213 TIBCO ActiveMatrix Administration . containers. page 207 Working with Substitution Variables. page 199 Working with Containers.

you must click the Refresh button . Select Configure an Environment from the Perspective drop-down list. When you are setting up an environment. 2. Node operations are described in the following sections: • • • • • • • • Enabling Assets in Nodes on page 189 Creating a Node on page 190 Installing and Uninstalling Nodes on page 192 Starting and Stopping Nodes on page 193 Editing a Node on page 194 Setting Permissions for Nodes on page 197 Installing a Shared Library in a Node on page 197 Deleting Nodes on page 197 TIBCO ActiveMatrix Administration . Certain long-running operations. Select the environment you want to configure from the Environment drop-down list. you can create all the nodes. A node must be running before you can perform deploy service assemblies to it. For example. Then you install the nodes and start them. Node configuration could also be done using a different order. then install and start them all. install it and start it. and then configure its containers and shared resources. To access this screen: 1. One approach to setting up the environment is to create one node. Then move on to the next node and do the same kinds of actions again. such as installing and starting a node. To update a node’s status for such operations. This means that the user interface continues to respond to user actions while the operation is in progress and does not automatically update the status. you add as many nodes as are needed for your architecture and specify on which machines they will be installed.188 | Chapter 7 Configuring Environments Working with Nodes A node is a Java virtual machine running ActiveMatrix containers and Messaging Bus. are performed asynchronously. All procedures in this section are performed in the Nodes screen.

To enable an asset. click the Edit button over the table of assets. In order to use such an asset within a particular node. In the ActiveMatrix Administrator graphical interface. when you are configuring a node. TIBCO ActiveMatrix Administration . These include: • • Containers Containers are enabled by default. but disabled. you must specify that the asset is enabled in the node. viewing one of the asset types displays a table of available assets and information on whether they have been enabled in the node.Working with Nodes 189 | Enabling Assets in Nodes Certain assets used by nodes may be available to the nodes. and click Save. Shared resources Shared resources are disabled by default. check the Yes radio button in the row containing the asset you want to enable.

on page 335. Ensure that the values of the node’s default connector are unique. TIBCO ActiveMatrix Administration .190 | Chapter 7 Configuring Environments Creating a Node Before you create the first node in an environment. Click Save. When you create a node. perform the configuration changes described in Appendix A. The General panel displays configuration fields. its details are stored in the database. If you want secure communications. the node appears in the Nodes table. Complete the rest of the fields following the guidelines in Table 45 on page 195. 5. See Working with the Default Connector on page 199. Securing TIBCO ActiveMatrix Communication Channels. decide whether you want communications between the environment’s nodes and other ActiveMatrix components to be secured. Table 44 describes the Nodes table columns. Table 44 Nodes Reference Column Name Description The node’s name. 4. which contains all the nodes that have been added to the selected environment. Click the New button above the Nodes table. 2. 3. After a few seconds. To create a node: 1. Type a name in the name field.

Machine The machine on which the node is installed. Unknown The status of the node cannot be determined.Working with Nodes 191 | Table 44 Nodes Reference (Cont’d) Column Status Description The node’s status: • • • • • Defined The node is defined in the database but the configuration files have not been installed on the machine. Install Failed1 Node installation has failed. The status is a link that you can click to display a screen with information about the error. TIBCO ActiveMatrix Administration . Running1 The node is running. but whether the node process is running or stopped is not known. Stopping The node is in the process of being stopped. Uninstalling Node configuration files are in the process of being removed from the machine. • • • • • • • • Start Failed1 Node startup has failed. See Figure 17 on page 192. Uninstall Failed1 Node uninstallation has failed. Stop Failed1 Node stop has failed. Starting The node is in the process of being started. This state occurs after the node has been installed but before it has been started or after it has been started and then stopped. 1. Installing Node configuration files are in the process of being generated on the machine. Installed/Stopped1 The node configuration files have been installed on the machine but the node is not running. Installed Node configuration files have been successfully generated on the machine.

Click the Refresh button located at the top right of the table until the node’s status changes to Installed/Stopped. the Containers and Shared Resources links display information about the containers and shared resources that are available on this node. The node executable is located in the bin subdirectory of the installation directory and is named environmentname_nodename.192 | Chapter 7 Configuring Environments Figure 17 Node Status Life Cycle [failure] Stop Failed Stop Stopping [success] New Defined Delete [success] Uninstall [failure] Install Installing [failure] [success] Installed/Stopped Start Starting Stop [success] Running Install Failed Uninstall [failure] Uninstall Failed Uninstall Uninstalling Uninstall Start Failed When the node has been fully configured. To install a node: 1. TIBCO ActiveMatrix Administration . A node installation directory is created in AMX_HOME/data/environmentname/nodename/. The nodes’ status changes to Installing. 2. select the nodes you want to install and click Install. In the Nodes table. See Working with Containers on page 202 and Working with Shared Resources on page 207 for more details.exe. Installing and Uninstalling Nodes Installing Nodes Installing a node creates configuration files on the machine on which the node will run.

Click the Refresh button located at the top right of the table until the nodes’ status changes to Defined. 2. select one or more nodes and click Uninstall. Starting and Stopping Nodes After you have installed a node you can perform life cycle actions on it such as start and stop.bat containing the following commands: @echo off if {%1}=={} @echo Syntax: SvcTimeOut TimeOutMilliseconds&goto :EOF @echo REG ADD "HKLM\SYSTEM\CurrentControlSet\Control" /V ServicesPipeTimeout /T REG_DWORD /F /D %1 TIBCO ActiveMatrix Administration . Create a file name SvcTimeOut. Windows On Windows platforms. In the Nodes table. To modify this timeout period. The node must be stopped and all service units unmapped from the node before you can uninstall it. select one or more nodes and click Start. The nodes’ status changes to Starting. you have the option to install the node as a Windows service. To uninstall a node: 1. When you uninstall a node. Starting Nodes To start a node: 1. all its containers and shared resources are also uninstalled. follow these steps: 1. 2. The nodes’ status changes to uninstalling.Working with Nodes 193 | Uninstalling Nodes Uninstallation removes the node’s configuration files from the machine where you installed it. Click the Refresh button located at the top right of the table until the nodes’ status changes to Running. In the Nodes table. The node status appears incorrect for some time and then is corrected. The node definition remains in the database and the node status changes to Defined. When you attempt to start the node from the Services application in the Control Panel a timeout error may be displayed. This occurs because the default timeout period Windows applies to services is too small for nodes.

which is 10 minutes. Select Automatic from the Startup type drop-down list. you can edit the node definition and change the machine on which the node will be installed. Windows Server 2003.194 | Chapter 7 Configuring Environments REG ADD "HKLM\SYSTEM\CurrentControlSet\Control" /V ServicesPipeTimeout /T REG_DWORD /F /D %1 uses REG. When you stop a node. 2. 3. Run SvcTimeOut TimeOutMilliseconds. where TimeOutMilliseconds is the number of milliseconds that the Service Control Manager should wait. you must add a node startup script to the UNIX startup configuration files that control daemon startup. Right-click the Windows service and select Properties. 2. Click the Refresh button located at the top right of the table until the nodes’ status changes to Installed/Stopped. Starting a Node on Machine Startup When you create a node you can specify whether the node should be started when the machine on which it is installed is started. Open the Windows Services application.bat 2. 3. Editing a Node Before you install a node (or after you uninstall it). and later. its containers are also stopped. or installed from the Windows 2000 Support Tools. TimeOutMilliseconds should be at least 600000. select one or more nodes and click Stop. built into Windows XP. TIBCO ActiveMatrix Administration . UNIX On UNIX platforms. Shut down and restart your computer. SvcTimeOut.EXE. The nodes’ status changes to Stopping. Stopping Nodes To stop a node: 1. In the Nodes table. Windows To configure a Windows service node to start when the machine starts: 1.

1. Description Messaging Server A short description of the node. See Table 45 for details on all the fields. Required. Management Port Required. For example.Working with Nodes 195 | When a node is installed. select a node. Each node is associated with one messaging server. The node’s name. You cannot edit the name after you install the node. click Edit. The messaging server to use for this node’s transport requirements. you must configure routes between the servers. the only editable field is the Description field. 2. If the nodes in an environment are using different messaging servers. 3. Spaces are not permitted. In the Nodes table. Click the General Information link. The name must be a valid directory name in the Windows and UNIX operating systems. TIBCO ActiveMatrix Administration . The name can contain only alphanumeric characters. and dots (periods). Port on which the node listens and responds for management and control functions using JMX protocol. Names are not case sensitive. If you want to make more changes. See Configuring Multiple Messaging Servers in Multinode Scenarios on page 198. hyphens. you must first uninstall the node. If the node is not yet installed. If it is installed. in geographically distributed environments. The name must be unique within the environment. underscores. Select a machine from the drop-down list containing the messaging servers in the environment. Click Save. you can edit all fields in this section. you might use a messaging server in the same region in which the node is created. you can edit only the description. Node Reference Table 45 Node Reference (Sheet 1 of 2) Field Name Description Required. In the General Information area.

You cannot edit this setting after you install the node. Select a machine from the drop-down list containing the machines enabled in the environment. Windows Service? Specify whether the node runs as a Windows service. The path to the ActiveMatrix installation directory on the machine on which the node is installed. TIBCO ActiveMatrix Administration . The machine on which the node will run. Product Required. The name of the Windows service is TIBCO ActiveMatrix environmentname_nodename ENV_NAME. If you want to use a machine that is not in the drop-down list you must bind the machine as described in Binding Machines on page 105 and enable it in the environment as described in Enabling Machines in an Environment on page 182.196 | Chapter 7 Configuring Environments Table 45 Node Reference (Sheet 2 of 2) Field Machine Name Description Required. The startup type is Manual. Default: No.

4. In the Nodes table. 2. Click the Set Permission button. 3. To force the delete. Click Delete. 3. TIBCO ActiveMatrix Administration . 2.2/server/bin. If the delete fails. To install a library: 1. Installing a Shared Library in a Node Sometimes you might want to share a library between multiple service units running on a node instead of packaging the library into every service unit. 2. select the nodes you want to delete. Change to the directory AMX_HOME/2. In the Nodes table. The library must be in the format of an Eclipse feature. ActiveMatrix allows you to install a library in a node. Run SyncInstallation.Working with Nodes 197 | Setting Permissions for Nodes To set permissions for nodes: 1. Unzip the library into the ENV_HOME/components/eclipse folder on the machine where the node is installed. A dialog displays offering you the option to force anyway. you must stop and uninstall the node if it has been installed and started. Deleting Nodes Before you can delete a node. select the node or nodes for which you want to set permissions. Follow the procedures described in Permissions on page 145. 3. To delete nodes: 1. click the Resolve link. Click Yes to complete the delete. the node status changes to Delete Failed and a Resolve link appears in the column to the right of the status column.

conf Add the following queue names to the Enterprise Message Service server 1 file: EnvironmentName.Destination@EMS-Serv er3 global TIBCO ActiveMatrix Administration .Node1. Enable the route property in tibemsd.conf file.JavaContainerName.Node2.conf Add the following queue names to the Enterprise Message Service server 2 file: EnvironmentName.Java (Node3) For this scenario you must configure the Enterprise Message Service server configuration files as follows: • • • tibemsd.Destination global EnvironmentName. you must enable routing at the Enterprise Message Service server level. By default this property is disabled.198 | Chapter 7 Configuring Environments Configuring Multiple Messaging Servers in Multinode Scenarios It is possible to configure ActiveMatrix environment with multiple messaging servers and assign different servers to the nodes within the environment.conf Create a unique name for each Enterprise Message Service server in the file.Queue.Queue.JavaContainerName.Queue.Java (Node2) .Node2.JavaContainerName. For example. If the nodes in an environment are configured to use a different Enterprise Message Service server for each node.Queue.Java (Node1) .Node3. assume you have three nodes in an environment and 3 Enterprise Message Service servers: • • • Node1 is configured to use Enterprise Message Service server 1 Node2 is configured to use Enterprise Message Service server 2 Node3 is configured to use Enterprise Message Service server 3 Suppose you deploy a service assembly across the nodes as follows: SOAP .Destination global EnvironmentName.Destination@EMS-Serv er2 global • queues. queues.JavaContainerName.

3. 3. TIBCO ActiveMatrix Administration . all network cards on the machine listen for incoming HTTP requests on the specified port. select a node. the default value localhost specifies the current machine. provided by a node. Select Configure an Environment from the Perspective drop-down list. such as WSDL generation. this field specifies the host name of the card that used to accept incoming HTTP requests. For machines that have only one network card. Therefore make certain that all HTTP connection resources that use the same host name specify different port numbers. To edit the default connector: 1. Select the environment you want to configure from the Environment drop-down list. If there is more than one network card on the machine. All procedures in this section are performed in a node’s Default Connector screen. Click Save. Default Connector Reference Table 46 Default Connector Reference Field Host Description Specifies the name of the host that accepts the incoming requests. For machines that have more than one network card. 4. To access this screen: 1. 2. Click the Edit button. Click the Default Connector link. Edit the fields according to the descriptions in Table 46. Default: localhost. 2. and you specify localhost in this field.Working with the Default Connector 199 | Working with the Default Connector The default connector is used to access system services. Only one HTTP server can be started on each port. In the Nodes list.

This can adversely affect throughput. Default: 20000. Default: 150 TIBCO ActiveMatrix Administration . Minimum Threads The minimum number of threads available for incoming HTTP requests. and a request received requires SSL transport. the request is redirected to the port you specify here. If the HTTP connection supports non-SSL requests. Maximum size allowed for HTTP POST data. Unit is milliseconds. Default: 10866. Default: 1000. Unit is bytes. the ActiveMatrix node returns a ConnectionRefused exception to the client. for the specific URI the request is sending to be presented.200 | Chapter 7 Configuring Environments Table 46 Default Connector Reference (Cont’d) Field Port Description Port number on which to listen for incoming HTTP requests. so enable this field only when required. Connection Timeout The number of milliseconds the connector waits. When a client sends a request that cannot be processed because no threads are available. Status Enable DNS Lookups Maximum Post Size Redirect Port The status of HTTP server shared resource that implements the default connector: Installed. Default: 25 Maximum Threads The maximum number of threads available for incoming HTTP requests. after accepting a connection. The HTTP server does create more than the number of threads specified by this parameter. Note: If you create more that one node on a machine you should ensure that the port numbers are unique. The HTTP server creates the number of threads specified by this parameter when it starts up. Default: 8081. Enables a Domain Name System (DNS) lookup for HTTP clients so that the IP address is resolved to a DNS name.

an additional connection timeout period is used while a SOAP message is being executed. If checked. Default: false (not checked) TIBCO ActiveMatrix Administration . the additional timeout period is not used.Working with the Default Connector 201 | Table 46 Default Connector Reference (Cont’d) Field Disable Upload Timeout Description If not checked.

you would disable the JMS container so that it does not consume resources when the node is started. the containers available on the nodes can be either enabled or disabled and active or not active. Click the No radio button next to the containers you want to disable. Click Save. and starting nodes. On the other hand. Enabling and Disabling Containers To enable or disable containers: 1. 3. For example. Click the Containers link. select a node. Disabled containers are not activated when the node is started. by default the containers whose software is available on the machine are enabled. 4. if you will not be deploying any services with JMS bindings. Select Configure an Environment from the Perspective drop-down list. you must manually activate the container. 2. The ActiveMatrix software installed on a machine determines what containers are available to nodes on that machine. If you disable a container when the node is running. 5. All procedures in this section are performed in a node’s Containers screen. installing. Select the environment you want to configure from the Environment drop-down list. When a node is created. activate and deactivate are transient actions that is they don’t affect any configuration permanently. In the Nodes list. While you are defining. 2. You can disable a container at any point in the container’s life cycle. if you re-enable a container when the node is running.202 | Chapter 7 Configuring Environments Working with Containers Containers are the runtime environments for a component implementations and service and reference bindings. TIBCO ActiveMatrix Administration . To access this screen: 1. In summary. Click the Edit button. then you must manually deactivate the container. click the Yes radio button next to the containers you want to enable. Enabled containers are activated when the node is started and only active containers can run service units. In the Enabled at Startup column. Conversely. enabling and disabling a container permanently affects the container’s behavior across node startup. they simply change the state of a container on a running node.

0" messagingServerName="messagingServerName" namingPort="namingPort" </Node> <target name="container-add" description="Add Container"> <AMXAdminTask serviceBaseURL="serviceURL" username="userName" password="password" action="add" dataFile="dataFile" objectSelector="Environment/Node/Container" overwrite="true" merge="true" createIfNotExists="true" forceDelete="true"/> </target> <Node name="nodeName" <Container type="com.runtime" version="2.Working with Containers 203 | Command-Line Interface To enable or disable a container. The container element requires a type attribute in the format: com.2.containerNamecontainerType.runtime where the values that containerName and containerType can assume are listed in Table 47 Table 47 Container Type Attribute Components Container Java .2.tibco.container.javase. use the following AMXAdminTask definitions and data file elements: <target name="node-add" description="Add Node"> <AMXAdminTask serviceBaseURL="serviceURL" username="userName" password="password" action="add" dataFile="dataFile" objectSelector="Environment/Node" overwrite="true" merge="true" createIfNotExists="true" forceDelete="true"/> </target> <Node xsi:type="amxdata:Node" name="nodeName" hostName="hostname" tibcoHome="ENV_HOME" productInstallDirectory="AMX_HOME" productVersion="2.NET Mediation Adapter SOAP JMS containerName java clr mediation adapter soap jms containerType se se se binding binding binding For example. to add a node and then enable the Java container.matrix.container.0" /> TIBCO ActiveMatrix Administration .matrix.tibco. you add or delete a container to a node in full or base format.

When specifying the version in the command-line interface data file you are required to provide only as much of the version as you know. Container Reference Table 48 Container Reference Field Name Version Description The name of the container.1 but don’t know the version qualifier. Click the Containers link.204 | Chapter 7 Configuring Environments </Node> Activating and Deactivating a Container A container of the required type must be activated on a node in order for a service unit to be deployed to that node. In the Containers list. 4.1 and choose the one with the highest version qualifier. 3. To activate a container.1. click the Deactivate button. In the Nodes list.0 and choose the one with the highest maintenance version. select a node.0. you can specify the version as 1. For example. TIBCO ActiveMatrix Administration . The version of the container.0. if you know that you have a container of version 1. The command-line interface finds all containers of version 1. either of the following actions activates the container: • • Explicitly invoking the activate action for the container Restarting the node To explicitly invoke the activate or deactivate actions: 1.0. To deactiveate a container.0. If you don’t know the maintenance version. click the Activate button. you can specify 1. 2. If a container is enabled for a node. select a container. The command-line interface finds all containers of version 1.

If any service units in a service assembly have been bound to this container you cannot change the setting. Unknown The status is unknown. Deploying Service Assemblies. Error An error occurred while attempting to activate or deactivate the container. on page 215 for more details on deploy-time activities. the container is not activated. the container is activated. See Figure 18. Enabled at Startup? Indicates whether the container is enabled for this node. A service unit cannot be deployed to a node without at least one active container of the required type. Marked for Activation The contained has been enabled. One of • • • • • • Active The container is active. When the node starts up.Working with Containers 205 | Table 48 Container Reference (Cont’d) Field Status Description The status of the container. Marked for Deactivation The container has been disabled.) TIBCO ActiveMatrix Administration . When the node starts up. (See Chapter 8. Not Active The container is not activated.

206 | Chapter 7 Configuring Environments Figure 18 Container Status Life Cycle Activate Not Active Deactivate Active Start Node Deactivate Enabled Disabled Activate Start Node Marked for Deactivation Marked for Activation TIBCO ActiveMatrix Administration .

To enable or disable shared resources: 1. Once the definition has been created you first enable the resource for the node and then you install the resource in the node. Click the Shared Resources link. you must have created the shared resource definition that it uses. once a shared resource has been disabled for a node. Click the Edit button. ActiveMatrix Administrator enables you to specify resources that can be shared across all the services running on a node. see Mapping Shared Resource Profiles to Shared Resources on page 234. 3. click the Yes radio button next to the shared resources you want to enable. For further information. either of the following actions uninstalls the resource: • • Explicitly uninstalling the resource through a user interface command Restarting the node HTTP shared resources can be customized through the use of local substitution variables. installing and uninstalling. 4. In the Enabled at Startup column. 2. Before you can enable and install a shared resource. TIBCO ActiveMatrix Administration . Select a node. Once a shared resource is enabled for a node. Click the No radio button next to the shared resources you want to disable. Enabling and Disabling Shared Resources You cannot disable a shared resource if it is installed or if a shared resource profile is mapped to the resource. The actions you perform on shared resources are enabling and disabling. Click Save.Working with Shared Resources 207 | Working with Shared Resources A shared resource enables services to connect with physical resources they need to function. See Managing Shared Resource Definitions on page 114 for an overview and more details. 5. either of the following actions installs the resource: • • Explicitly installing the resource through a user interface command Restarting the node Similarly. Installing a resource allocates files on the node. See Customizing HTTP Shared Resource Definitions on page 11 and Overriding a Substitution Variable Value on page 211.

208 | Chapter 7 Configuring Environments Installing and Uninstalling Shared Resources Installing Shared Resources After you enable shared resources you install the resources on the nodes. See WS-Addressing in TIBCO ActiveMatrix Composite Editor User’s Guide. The resource functions are: • WS-Addressing An HTTP server shared resource with the WS-Addressing resource function enable must be installed in any node hosting SOAP references that require non-anonymous WS-Addressing support. first restart the node. Once the resource is installed. You cannot uninstall a shared resource if any shared resource profile is mapped to it. The installation will fail if the IP of the machine hosting the node changes after the node is created. enable the resources. its files are removed from the node where you earlier installed it and it is disabled. select one or more shared resources and click Install. Enabling and Disabling Resource Functions Resource functions modify the behavior of the shared resource. • If the node status is Installed/Stopped. and start the node. You can install the resource only if no other shared resource of the same name has been installed on the node. the shared resource is enabled to receive WS-Addressing reply and fault messages. and start the node. disable the resources. TIBCO ActiveMatrix Administration . To proceed with installation. select one or more shared resources. To install shared resources: • If the node status is Running. select one or more shared resources. To uninstall shared resources: • • If the node status is Running. If the node status is Installed/Stopped. select one or more shared resources and click Uninstall. Uninstalling Shared Resources When you uninstall a shared resource. See Mapping Shared Resource Profiles to Shared Resources on page 234.

after you uninstall the resource. it installs when the node is restarted. 2. 3. b. Installed After you install the resource or restart a node and the resource was • • • Marked for Install. Deploying Service Assemblies. Shared Resource Reference Table 49 Shared Resource Reference Field Name Type Status Description Required. The Select Resource Functions dialog box displays. 4. The status of the shared resource: • Uninstalled Before the shared resource is enabled for the first time. See Figure 19 on page 210. See Chapter 8. A name that is unique within the node where it is installed.link. To disable the function. To enable a resource function for a shared resource: 1. Marked for Uninstall After you disable an installed resource. To enable the function. after you restart a node and the resource was Marked for Uninstall. Select the resource. only one shared resource can have a resource function enabled. (Names can be the same across nodes. it is uninstalled when the node is restarted.Working with Shared Resources 209 | For each node. Click the -Select. Click Save. TIBCO ActiveMatrix Administration . If you enable the resource. Marked for Install After you enable a resource. on page 215 for details on deploy-time procedures. Click the Edit button. Enabled on Startup? Indicates whether the shared resource is enabled for this node. Click Apply. uncheck the checkbox. If you disable the resource.) Names are not case sensitive. If any service units in a service assembly have been bound to this resource you cannot change the setting. check the checkbox next to the function. The type of the shared resource. a.

210 | Chapter 7 Configuring Environments Table 49 Shared Resource Reference (Cont’d) Field Resource Functions Description The resource function enabled for the shared resource. Figure 19 Shared Resource Status Life Cycle Install Uninstalled Uninstall Installed Start Node Uninstall Enabled Disabled Install Start Node Marked for Uninstall Marked for Install TIBCO ActiveMatrix Administration . The field is empty if no resource functions have been enabled for the shared resource.

• Reverting a Substitution Variable Back to the Global Value To revert a substitution variable value back to the value defined at the enterprise assets level: 1. Select Configure an Environment from the Perspective drop-down list. 2. Click Save. 2. 2. Therefore. There are two caveats you should keep in mind when overriding substitution variables used by shared resource definitions: • Changing the value of a substitution variable does not trigger validation of shared resource definition properties. 3. Click Save. 3. The value of a substitution variable can be overridden at the node level. Click the Edit button above the Local Substitution Variables table. Click the Edit button above the Local Substitution Variables table. which would prevent you from installing the shared resource definition on the node. TIBCO ActiveMatrix Administration . Click the Revert link. changing the value could invalidate the shared resource definition.Working with Substitution Variables 211 | Working with Substitution Variables Substitution variables are global variables defined at the enterprise assets level (see Working with Substitution Variables on page 167) and bound to shared resources. To work with substitution variables: 1. Click the Local Substitution Variables link. Edit the variable’s type or value. You must restart the node or reinstall the shared resource. such as HTTP servers (see Binding a Shared Resource Property to a Substitution Variable on page 116). Overriding a Substitution Variable Value To override a substitution variable value: 1. The new value does not take effect in a running node using that shared resource definition.

The variable’s type. TIBCO ActiveMatrix Administration .212 | Chapter 7 Configuring Environments Local Substitution Variables Reference Table 50 Local Substitution Variables Reference Column Name Type Value Description The variable’s name. The variable’s value. Either a Revert link. which indicates that the value has been overridden locally or text. which indicates that the global value is being used.

Working With Logging Configurations 213 | Working With Logging Configurations See Working with Logging Configurations on page 308. TIBCO ActiveMatrix Administration .

214 | Chapter 7 Configuring Environments TIBCO ActiveMatrix Administration .

page 234 Working with Topics. page 237 Working with Services. page 236 Working with Logging Configurations. Topics • • • • • • • • • • Deployment Overview. page 231 Mapping Shared Resource Profiles to Shared Resources. configure it. and deploy it. page 238 TIBCO ActiveMatrix Administration . page 216 Uploading a Service Assembly. page 221 Working with Service Units. page 220 Working with Service Assemblies. page 218 Configuring a Service Assembly.| 215 Chapter 8 Deploying Service Assemblies This chapter explains how to upload a service assembly archive. page 235 Working with Substitution Variables.

All procedures in this chapter are performed in the Deploy to an Environment screen. the configuration details are retained and you can redeploy it without having to go through the configuration steps again. TIBCO ActiveMatrix Administration .216 | Chapter 8 Deploying Service Assemblies Deployment Overview At deploy time you upload an archive containing a service assembly. so even if you undeploy a service assembly. Map shared resource profiles to shared resources. Select Deploy to an Environment from the Perspective drop-down list. you: • • • • Upload the service assembly and choose whether to import shared resource definitions. Configuring Service Assemblies To configure a service assembly. Select the environment you want to deploy to from the Environment drop-down list. and each service unit might have one to 100 services. To access this screen: 1. 2. and deploy it. Service assembly configuration details are stored in the ActiveMatrix Administrator database. A service assembly might have 1-50 service units. Map service units to nodes. The service units contained in the service assemblies are deployed to the appropriate containers on those nodes. The archive is the output of the design-time ActiveMatrix activities. configure it. Edit substitution variables as needed.

Deploying a Service Assembly After the service assembly is configured you can deploy it. you might want to deploy the same archive in environments set up for different geographical regions. You can create more than one service assembly configuration using one archive. all containers required for the deployment must be activated. After a service assembly is deployed and running. All nodes required for the deployment must be running. and all shared resources must be installed. or to implement different service level agreements. Then you can configure and deploy it as needed. It is not possible to deploy more than one service assembly with the same namespace in an environment. the Deployable status of all other service assemblies with the same namespace is No. or for testing and later for staging. For example. You can also undeploy it. TIBCO ActiveMatrix Administration .Deployment Overview 217 | Reusing Archives Each archive contains files for one service assembly. You can upload the same service assembly archive or different archives with the same namespace but if any one of these service assemblies is deployed. To do so you upload the archive file again and give it a different service assembly name. you can start and stop the service assembly and shut it down.

.218 | Chapter 8 Deploying Service Assemblies Uploading a Service Assembly Uploading a service assembly transfers a local service assembly archive file to the ActiveMatrix Administrator database. digits. and Namespace properties (see Service Assembly Reference on page 224). A service assembly archive file has a . To upload a service assembly archive file: 1. 5. You can select the service assembly you just added and the General Information screen for the service assembly displays the Name. 3. In the Name field. enter a name for the service assembly.’. the imported resource is named HTTPSR_1.. If the shared resource name already exists within the enterprise.zip extension. Import shared resource definitions 4. '-'. where N is an increasing integer. the Import Shared Resource Definitions option creates the shared resource definition in the enterprise and enables it for the environment.. TIBCO ActiveMatrix Administration . the name is appended with the string _N. HTTP client and SSL client shared resources defined in a service assembly archive are not supported in ActiveMatrix Administrator and cannot be imported. See Importing Shared Resource Definitions. Check the Import Shared Resource Definitions checkbox to create shared resources definitions from definitions in the service assembly archive. Click OK. The service assembly is added to the Service Assemblies table. The service assembly status is Not Deployed and the Deployable? column is No. The name can contain only letters. Archive File. 2. and so on. Table 51 on page 219 describes the Service Assemblies table columns. Importing Shared Resource Definitions During service assembly upload. Click Browse. For example. if you upload a resource named HTTPSR and that resource name already exists. Click Upload Service Assembly. '_' and '. to choose a service assembly archive file from the file system.

The date and time that the service assembly was last modified. Service Assemblies Reference Table 51 Service Assemblies Reference Column Name Version Deployable? Status Packaged By Last Modified By Last Modified On Deployed By Description The name of the service assembly. Once the property values are hardcoded. The status of the service assembly. you cannot edit the value of the resource properties by edited the value of the substitution variables in the service assembly (see Substitution Variables Reference on page 233) or service unit (see Working with Substitution Variables on page 236). the property values are hardcoded with the value of the substitution variables at the time of upload. The user that created the service assembly. The version of the service assembly. The user that last modified the service assembly.Uploading a Service Assembly 219 | If you import shared resource definitions from the service assembly archive and those definitions use substitution variables for the value of resource properties. TIBCO ActiveMatrix Administration . Once the upload is complete. The user that deployed the service assembly. Indicates whether the service assembly has been configured for deployment or whether the service assembly’s namespace is unique. you must enable and install the shared resource on each nodes where the shared resource is used (see Working with Shared Resources on page 207).

Shared resource profiles are defined at design time and packaged in the service assembly archive. Configuring Service Units To configure the service units in a service assembly: 1. Before deployment you must map each shared resource profile to a shared resource available in the node that the service unit is mapped to as described in Mapping Shared Resource Profiles to Shared Resources on page 234. 2. Select the service unit in the Service Units table. Mapping Shared Resource Profiles to Shared Resources A shared resource profile specifies the kind of physical resource needed by services. Map service units to nodes Edit substitution variables b. For each service unit in the service assembly: a. Follow the procedure described in Substitution Variables Reference on page 233. TIBCO ActiveMatrix Administration . Click the Substitution Variable tab if you want to edit the substitution variables for the service unit. c. map the service units to nodes as described in Mapping Service Units to Nodes on page 231. In the Service Assemblies table.220 | Chapter 8 Deploying Service Assemblies Configuring a Service Assembly Configuring a service assembly requires you to specify the nodes on which service units in the service assembly are deployed. In the Node Mapping tab. You must also map shared resource profiles to shared resources as appropriate for the service assembly. Click the Service Units button. 3. select the service assembly or assemblies.

In some cases the status of nodes. and stop actions. page 229 Deleting Service Assemblies. but instead is shown as Installed/Stopped. and the target namespace of the composite packaged in the service assembly is unique within the environment. However. and shared resources shown in ActiveMatrix Administrator may not reflect the actual state of the objects. but instead is shown as Running. the service assembly’s value the Deployable? column is Yes. but the Management Daemon process is stopped and the but the node status is shown as Unknown. but the status has not yet been updated in ActiveMatrix Administrator to show the node as Installed/Stopped. The node is running. all containers required for the deployment must be activated. The node is stopped. Deploying and Redeploying Service Assemblies A service assembly is considered deployable only when all service units are mapped to nodes. page 222 Editing Service Assembly Configurations on page 223 Updating a Service Assembly Archive on page 227 Downloading a Service Assembly Archive on page 228 Updating Service Assemblies on page 228 Undeploying Service Assemblies.Working with Service Assemblies 221 | Working with Service Assemblies After you have uploaded and configured one or more service assemblies. all shared resource profiles are mapped to shared resources. but the status has not yet been updated in ActiveMatrix Administrator to show the node as Running. and all shared resources must be installed. containers. page 229 Nodes must be running in order to execute the deploy. • • TIBCO ActiveMatrix Administration . start. all nodes required for the deployment must be running. to actually deploy the service assembly. For example: • The node is running. these actions are available: • • • • • • • • Deploying and Redeploying Service Assemblies on page 221 Starting and Stopping Service Assemblies. When all of these conditions are met.

After resolving the errors (the status is a link you can click to display a screen with information about the error) click the Redeploy button to start the assembly. select one or more service assemblies and click Deploy. In such cases. If there are errors. select one or more service assemblies. The Status column changes to Starting. stop it. Stopping Service Assemblies The service assemblies must be started in order for you to stop them. the reported status of containers and shared resources may be different than the actual status. 2. then Deployed. After resolving deployment errors (the status is a link you can click to display a screen with information about the error) click the Redeploy button to complete deployment. In the Service Assemblies table. Starting and Stopping Service Assemblies After a service assembly has been successfully deployed. The Status column changes to Deploying. In the Service Assemblies table. If the service assembly is deployed successfully. 2. Click Stop. If the service assembly starts successfully the Status column changes to Running. in the Service Assemblies table. You can also redeploy a service assembly after changing the mapping of service units to nodes. and. Starting Service Assemblies To start service assemblies: 1. you can start it. If any object is not in the correct state. an error is returned when you try to deploy the service assembly describing why it could not be deployed. select one or more service assemblies. To deploy a service assembly. Status changes to Stopping. See Updating Service Assemblies on page 228. if you know that the object is in the correct state you can optimistically attempt to deploy the service assembly. Click Start. To stop service assemblies: 1. as needed. TIBCO ActiveMatrix Administration . the status changes to Deployed. If there are errors. the Status column changes to Deployed with Errors. the Status column changes to Running with Errors.222 | Chapter 8 Deploying Service Assemblies Likewise.

Once you save the settings the service assembly’s status is Out of Sync and you must update the service assembly. To edit service assembly configurations: 1. 5. 6. Click the Edit button. Click the General Information link. 3. Click the General Settings button. as well as those that are not deployed. select the service assembly. See Table 52 for details on all the fields. As needed. See Updating Service Assemblies on page 228. edit the fields in the General Information area.Working with Service Assemblies 223 | Editing Service Assembly Configurations You can edit the configuration of service assemblies that are deployed. Click Save. 4. TIBCO ActiveMatrix Administration . 2. In the Service Assemblies table.

TIBCO ActiveMatrix Administration . The user that packaged the service assembly. The name is a link that you can click to download the file. In order for the service assembly to be deployable. Descriptive information about the service assembly. The name of the service assembly archive file that contains the service units to be deployed. the namespace must be unique within an environment. Contact information for the maintainer of the service assembly. The namespace defined in the service assembly.224 | Chapter 8 Deploying Service Assemblies Service Assembly Reference Table 52 Service Assembly Reference Field Name Archive File Description Packaged By Contact Namespace Description Name of the service assembly.

• • Running The service assembly is running. • Redeployable Indicates that configuration changes have been made to a deployed or running service assembly and the service assembly must be redeployed by clicking the Redploy button. click the Redeploy button to complete starting the assembly. • • Not Deployed The service assembly archive has been uploaded but has not been deployed or has been deployed and then undeployed. the status columns can display two flags: • Out of Sync Indicates that configuration changes have been made to a deployed or running service assembly. For further information on the circumstances that cause this flag. see Updating Service Assemblies on page 228. After you resolve the errors. and the service assembly in the node does not match the version in the database. Not Deployed with Errors1 The service assembly has been undeployed with errors. see Updating Service Assemblies on page 228. TIBCO ActiveMatrix Administration . click the Redeploy button to complete deployment. but errors need to be resolved before it can be started. One of: • • Deployed The service assembly has been deployed but has not been started. See Figure 16 on page 227. Deployed with Errors1 The service assembly has been deployed. In addition. Running with Errors1 The service assembly has been started on some nodes. For the appropriate action to take.Working with Service Assemblies 225 | Table 52 Service Assembly Reference (Cont’d) Field Status Description Current status of the service assembly. After you resolve the errors. but errors need to be resolved before it can be started on all nodes.

Default: External. External Only external endpoints are exposed to Policy Manager. requests are not load balanced among other provider instances available on other nodes. • • None No endpoints are exposed to Policy Manager. Since topic messages are always go through Enterprise Message Service server. One of the following values: • All Both internal and external endpoints are exposed to Policy Manager. An external endpoint has a binding that provides access to consumers outside the ActiveMatrix environment. Since messages are not routed through the Enterprise Message Service server. Prefer Local Providers? If checked and the consumer and provider are collocated on same node then requests are routed to the local provider. This option does not apply to topics because topic messages are always routed through the Enterprise Message Service server. TIBCO ActiveMatrix Administration . An internal endpoint is accessible only to consumers within an ActiveMatrix environment.226 | Chapter 8 Deploying Service Assemblies Table 52 Service Assembly Reference (Cont’d) Field Expose Endpoints Description Determines which endpoints in the service assembly are exposed to Policy Manager when deployed. multiple deployments of the provider wired a topic are always automatically load balanced. Note: Policy Manager does not enforce policies for out-only endpoints. Default: Yes.

a. 5. When you update a service assembly archive file the service assembly configuration is retained. 3. 2. Figure 16 Service Assembly State Redeployable Out of Sync Change Node Mapping Change Configuration Stop Start [success] Deployed Start [failure] Running Redeploy Undeploy Change Configuration Undeploy Change Node Mapping Redeploy Upload Not Deployed Delete Deploy [failure] Deploy [success] Undeploy [failure] Deployed with Errors Undeployed with Errors Running with Errors Updating a Service Assembly Archive Often you need to update the archive file of a service assembly after it has been deployed. 4. Click Browse and navigate to the directory containing the updated archive file. click the Update button next to the Archive File field. You can drill down to the Service Unit node mapping level to see the details. In the Service Assemblies table. Saving the configuration allows you to repeatedly update a service assembly while ensuring that configuration is performed once. For example. In the General Information area. Click the General Settings button. Click the Edit button at the right of the Service Assemblies table. click the service assembly. A browse dialog displays. b. during iterative development you might need to fix a defect in a component implementation. To update a service assembly archive: 1. The status is a link you can click to display a screen with information about the error.Working with Service Assemblies 227 | 1. Select the archive file and click OK. TIBCO ActiveMatrix Administration . Click the Stop button and then click the Undeploy button.

Table 53 shows the various types of changes you can make to the service assembly. 3. Start Redeploy. Deploy. Updating Service Assemblies When you update a service assembly. The action undeploys the service units from the removed nodes. For example. TIBCO ActiveMatrix Administration . and the actions you must perform to update the service assembly on the nodes given the state of the service assembly when the changes were made. 4. it does not contain any service assembly configuration data. The redeploy action deploys and starts the service units on the newly added nodes and has no effect on the service units on existing nodes. The Redeploy action deploys the service units on the newly added nodes. Undeploy. Running or Running with Errors Stop. Specify the location to save the file and exit the dialog. In the General Information area. Click the General Settings button.228 | Chapter 8 Deploying Service Assemblies Downloading a Service Assembly Archive You can download the archive file of any service assembly you have uploaded. Redeploy. The action undeploys the service units from the removed nodes. The downloaded archive is in its original form. Deploy Redeploy. The browser displays a file save dialog. click the service assembly. you must propagate the changes to the nodes on which the assembly is deployed. In the Service Assemblies table. if you remove a node mapping when the service assembly status is Deployed. Remove mapping between one or more service units and one or more nodes Redeploy. To download a service assembly archive: 1. you must first undeploy and then deploy the service assembly Table 53 Actions and Service Assembly Status Changes Service Assembly Status Action Update service assembly Add mapping from one or more service units to one or more nodes Deployed or Deployed with Errors Undeploy. 2. click the link in the value of the Archive File field.

it is stopped. Click Delete. if you are unable to stop and undeploy the assembly you can force it to be deleted by checking the Force delete the service assembly if necessary checkbox that is displayed in the delete confirmation dialog. 2. However. Start Undeploying Service Assemblies When you undeploy a service assembly. select one or more service assemblies. Deploy.Working with Service Assemblies 229 | Table 53 Actions and Service Assembly Status Changes (Cont’d) Service Assembly Status Action Update: • • • • • Expose Endpoints and Prefer Local Providers Topic queue Service queue Shared resource profile to shared resource mapping Substitution variable Deployed or Deployed with Errors Undeploy. To undeploy service assemblies. In general. When you confirm the delete action on the service assembly. The status changes to Not Deployed. Deploy Running or Running with Errors Stop. in the Service Assemblies table. Undeploy. and then it is deleted. select one or more service assemblies and click Undeploy. the configuration values you set up are retained in the database. the service assembly archive and all the configuration values are removed from the database. In the Service Assemblies table. When you initiate the undeploy action on a running service assembly. Deleting Service Assemblies When you delete a service assembly. you must stop and undeploy the assembly. A confirmation dialog is displayed. You can redeploy with the same configuration. it is stopped and then it is undeployed. To delete services assemblies: 1. or you can edit the settings and then redeploy. before deleting a service assembly. then undeployed. TIBCO ActiveMatrix Administration .

230 | Chapter 8 Deploying Service Assemblies 3. TIBCO ActiveMatrix Administration . Click Yes to confirm the deletion.

2. In the Service Assemblies table. Service Units Table Reference Table 54 Service Units Table Reference Column Name Version Type Description The name of the service unit. Service Units To view the properties of a service unit. Click the Service Units button. The service unit’s properties are displayed in two tabs: • • Node Mapping Tab The contents of the Node Mapping tab varies depending on whether you are in View or Edit mode. that is. and a list of mapped nodes. click the service unit in the Service Units table. select the service assembly. The type of the service unit. In Edit mode. which are the nodes to which the service unit is deployed when the service assembly containing the service unit is deployed. In View mode. The service units in the service assembly will display in the Service Units table whose columns are described in Table 54.Working with Service Units 231 | Working with Service Units To view the service units in a service assembly: 1. The version of the service unit. the Node Mapping tab contains a list of mapped nodes. nodes running containers whose type matches the service unit. For TIBCO ActiveMatrix Administration Node Mapping Tab on page 231 Substitution Variables Tab on page 233 . Mapping Service Units to Nodes A service unit specifies a container type and a compatible version range. the Node Mapping tab contains a list of available nodes.

and click the right arrow button or drag the nodes from the Available to Selected Nodes list. Click the Service Units button. versions 1. 3. TIBCO ActiveMatrix Administration . A service unit deployed on both N1 and N2 is deployed to Java 2. Click the right arrow button.0. In case of multiple container software versions.0. 2. If the nodes that you want to deploy to do not appear in the table.0 Java container. If the nodes you want to deploy to do not appear in the table.0 on N1 and Java 1. Click Save.0. and node N2 has a 1. select the service unit. Select the nodes that you want to deploy to from the Available Nodes list. To map service units to nodes: 1. You map a service unit to a node.0. The selected nodes are moved from the Mapped Nodes to the Mapped Nodes list. follow the procedure in Adding Nodes to the Mapped Nodes List on page 232 to add the nodes. Click Save. Adding Nodes to the Mapped Nodes List To add nodes to the Mapped Nodes list on the Node Mapping tab: 1. and a mapped icon will display next to the service unit in the Service Units table. 3. Removing Nodes from the Mapped Nodes List To remove nodes from the Mapped Nodes list on the Node Mapping tab: 1. select the nodes that you want to deploy the service unit to in the Available Nodes list. If a service unit is deployed to multiple nodes that host different versions of a container. 4.0. 2. follow the procedure in Creating a Node on page 190 to add the node to the environment.0 to 2. The mapped nodes will appear in the Mapped Nodes table. 4. In the Node Mapping tab.0 on N2. the highest version that falls within the specified compatible range is used.0. suppose node N1 has two Java containers with different versions 1.0.232 | Chapter 8 Deploying Service Assemblies example Java container.0 and 2. For example.0. the highest version of a container is picked for deployment and may resolve to different versions on different nodes. In the Service Units table.0. The nodes will appear in the Mapped Nodes list. Click the Edit button. Click the Edit button.

Value TIBCO ActiveMatrix Administration . The selected nodes are moved from the Mapped Nodes to the Available Nodes list. Mapped Nodes Reference Table 55 Mapped Nodes Reference Column Node Name Status Machine Description The name of the node on which the service unit is deployed. Substitution Variables Reference Table 56 Substitution Variables Column Name Descriptions The name of the variable you want to set. The status of the node. The type of the value you enter is validated when you save. Substitution Variables Tab The Substitution Variables tab allows you to specify the value of a service unit’s substitution variables. 3.Working with Service Units 233 | 2. The folder path acts like a namespace allowing use of different sets of substitution variables. Select the nodes that you want to remove from the Mapped Nodes list and click the left arrow button. including the path to the variable if it is contained in a folder. The value for the substitution variable. Click Edit to change any values as needed. When you edit any substitution variable in a service unit. Click Save. Subsequent changes made at the service assembly level do not affect the service unit’s substitution variables. The machine on which the node is running. you break the connection between all the service unit’s substitution variables and those maintained at the service assembly level.

To map a shared resource profile to a shared resource: 1. profile name. Click Save. Click Close to dismiss the dialog. The combination of service unit. Click Create to install the shared resource on the nodes. Click the Shared Resources link. Shared resource profiles are defined at design time and packaged in the service assembly archive. and composite element name identifies each profile uniquely.234 | Chapter 8 Deploying Service Assemblies Mapping Shared Resource Profiles to Shared Resources A shared resource profile specifies the kind of physical resource needed by services in the service unit. 4. Click the General Settings button. 7. TIBCO ActiveMatrix Administration . 5. The name of the composite element that references the profile. select the service assembly. In the Service Assemblies table. Shared Resource Profiles Reference Table 57 Shared Resource Profiles Reference Column Name Parent Name Description The name of the shared resource profile. the Create New Shared Resource dialog is displayed where you can choose to install the shared resource on the nodes. 2. 3. In the row containing the shared resource profile to map. If a shared resource does not yet exist on the nodes to which you are deploying the service assembly. 6. select the shared resource in the drop-down list in the Shared Resources column. Parent Type Shared Resource The type of the composite element that references the profile. Name of the shared resource that has been mapped to this profile. Click the Edit button over the Shared Resource Profiles table. Before deployment you must map each shared resource profile to a shared resource available in the node that the service unit is mapped to. A dialog is displayed the results of the create operation.

The message exchange pattern supported by the topic. The port type supported by the topic.Working with Topics 235 | Working with Topics Topics are implemented by topics in the Enterprise Message Service server. 4. In the Service Assemblies table. The topic name that implements the topic in the Enterprise Message Service server. TIBCO ActiveMatrix Administration . In the row containing the topic you want to modify. Topics Reference Table 58 Topics Reference Column Name MEP Port Type Physical Name Description The name of the topic. edit the value in the Physical Name column. then Messaging Bus automatically creates the bridge from topic to queue. Topic subscribers get messages sent to a topic from a queue. For information on how to create a bridge. see the Enterprise Message Service documentation. Click the Topics link. A bridge from topic to the queue must be created in the Enterprise Message Service server. 5. Topics are automatically mapped to default topic names. 3. 2. Otherwise you must manually create the bridge. select a service assembly. To edit a topic name: 1. If you specify a username and password in the messaging server configuration (see Adding a Messaging Server to an Environment on page 176). Click the Edit button above the Topics table. Click Save.

including the path to the variable if it is contained in a folder.236 | Chapter 8 Deploying Service Assemblies Working with Substitution Variables Substitution variables specify constants that can be used throughout the service assembly. Click Edit to change any values as needed. Table 59 Substitution Variables Reference Column Name Description The name of the variable you want to set. The value for the substitution variable. The data type of the values you enter is validated when you save. The folder path acts like a namespace allowing use of different sets of substitution variables. Value TIBCO ActiveMatrix Administration . See Substitution Variables Tab on page 233 for the relationship between substitution variables specified at the service assembly and service unit levels.

Working with Logging Configurations 237 | Working with Logging Configurations See Working with Logging Configurations on page 308. TIBCO ActiveMatrix Administration .

edit the value in the Queue column. or Composite Reference. 3. Composite Service. Component. Click the Edit button above the Services table. The type of the service. To edit the queue names used by a service: 1. In the Service Assemblies table. Click the Services link. TIBCO ActiveMatrix Administration . In the row containing the queue you want to modify. 5. Services are automatically mapped to default queue names. 2.238 | Chapter 8 Deploying Service Assemblies Working with Services Services are implemented by queues in the Enterprise Message Service server. The name of the internal Messaging Bus queue to which messages for the service are sent. select a service assembly. 4. Click Save. Services Reference Table 60 Services Reference Column Name Resource Type Queue Description The name of the service.

page 283 Browse Mode. page 289 TIBCO ActiveMatrix Administration .| 239 Chapter 9 Monitoring Infrastructure and Services This chapter describes how to monitor the performance of the ActiveMatrix infrastructure and the services running on the infrastructure. infrastructure. It provides various views such as dashboard. page 245 Infrastructure View. page 278 Deployment View. page 242 Accessing the Monitor & Manage Perspective. page 259 Integrated Service View. page 262 Service Instance View. page 248 Service View. Topics • • • • • • • • • • Overview. deployment. service. page 240 Enabling Monitoring. page 244 Dashboard View. and log view.

You can start and stop nodes and service assemblies. You can monitor performance at various levels such as environment. and services. Some content-based metrics are used to measure the service performance. applications. availability of services. TIBCO ActiveMatrix Administration . This chapter explains how you can monitor the overall health and performance of the infrastructure. node. consumer. and service units. and provider? If needed.240 | Chapter 9 Monitoring Infrastructure and Services Overview TIBCO ActiveMatrix Administrator not only allows you to configure and deploy applications. machine. These metrics provide real-time values by fetching data every minute and updating the values of the metrics. service assembly. node. Monitoring the system performance is not a one time activity but needs to be performed on a day-to-day basis. you can take corrective actions to get the system back to normal. Monitoring is performed in the Monitor & Manage perspective. and machines? Which are the top 20 most used services? Which are the top 20 faulting services? What is the performance of a service based on interface. service usage. operation. nodes. you can get answers to the following questions: • • • • • • • • What is the overall health of my system? Which nodes or services are currently down? What is the performance of machines that host my environment? Which services are deployed in a service assembly? Which service instances are running on the given environments. but also lets you monitor and manage the deployed applications. Using the Monitor & Manage perspective. This real time data is then displayed in a web-based dashboard provided with pre-defined views and visual alerts. and the number of successful to faulty service responses. Views The Monitor & Manage perspective provides the following views: • Dashboard View View summary information about the overall health of the services and system.

containers. shared resources. nodes. and service instances running on nodes. and • • services in service units. service assemblies. TIBCO ActiveMatrix Administration . Log View Build log queries and view log entries. Service View Search for services along with their details such as service provider and consumer. Deployment View View environments.Overview 241 | • • Infrastructure View Monitor environments. machines. You can search for a specific service and get details of a service instance. service units.

the messaging channel on which monitoring messages are received from nodes. 6. In addition to configuring the monitoring service. 3. Click Save. To enable monitoring: 1. Click the Monitoring Configuration link. you must also configure at least one node in an environment before any data is displayed in any views of the Monitor & Manage perspective. Table 61 Monitoring Configuration Field Enable Monitoring? Description Determines whether monitoring is enabled. Messages accumulate until the Metrics Manager plug-in is restarted. and which ActiveMatrix Administrator server in a cluster is responsible for managing monitoring messages. Enabling monitoring starts the Metrics Manager engine and starts the service probes running on nodes sending messages. all ActiveMatrix Administrator servers and all runtime nodes are notified of the new configuration. Click the Edit button. Stopping the Metrics Manager plug-in without disabling monitoring stops the Metrics Manager engine but nodes continue to send messages on the JMS connection. Monitoring Configuration Reference The Monitoring Configuration specifies whether monitoring is enabled. Click the Administrator Cluster link. The Metrics Manager plug-in (see Plug-ins on page 161) needs to be running to either enable or disable monitoring. TIBCO ActiveMatrix Administration . 4. 5. Configure the fields according to the descriptions in Table 61. 2.242 | Chapter 9 Monitoring Infrastructure and Services Enabling Monitoring You can view metrics data in the Monitor & Manage perspective only if you enable monitoring. Select Configure Enterprise Assets from the Perspective drop-down list. When you save a Monitoring Configuration.

when SSL is configured via JNDI the monitoring system assumes that a topic connection factory with the name SSLTopicConnectionFactory exists on the JMS server. TIBCO ActiveMatrix Administration . If you change the JMS shared resource definition referenced by this field you must restart the Metrics Manager plug-in. The Monitoring and Management perspective queries this database for metrics. you can specify the factory name as a JNDI property named com. If you have configured the JMS server with a different topic connection factory name. you must select a new Metrics Manager. If the ActiveMatrix Administrator server that is configured as the Metrics Manager becomes unavailable. Before selecting a connection you must configure a JMS shared resource definition as described in JMS Shared Resource Definition Reference on page 125. Periodically (once in 5 minutes) Metrics Manager persists changed objects to a database. The messages are delivered to the JMS connection. In the case of non-SSL.topic_connection_factory. A drop-down list containing existing JMS shared resource definitions. the default topic connection factory name is TopicConnectionFactory. By default. When a new Metrics Manager becomes active it immediately starts processing the stored messages. To configure SSL connections to the JMS server set the Connection Factory field to SSLQueueConnectionFactory. Selecting a JMS shared resource restarts the Metrics Manager engine with the new JMS configuration. Selecting a Metrics Manager server stops the currently running Metrics Manager engine and starts a new Metrics Manager engine on a different ActiveMatrix Administrator server.tibjms. Metrics Manager processes metrics messages from service probes on nodes and aggregates them into a monitoring model. While the Metrics Manager is unavailable.Enabling Monitoring 243 | Table 61 Monitoring Configuration (Cont’d) Field JMS Connection Description The JMS connection on which all the ActiveMatrix Administrator servers in a cluster receive metrics information.tibco. nodes keep collecting statistics. Metrics Manager Server The ActiveMatrix Administrator server within the cluster responsible for managing the flow of metrics information from nodes.naming. See Plug-ins on page 161. A drop-down list containing the all the servers in the cluster. If the Connection Type of the JMS shared resource is JNDI you must set the Connection Factory field to QueueConnectionFactory.

Select a view from the view selection bar: — Dashboard Observe the overall health and status of the system or the selected environment. See Deployment View on page 283. 4. and nodes. — Since Started Provides metrics since the component was started or monitoring was enabled. By default. — Log Build log queries and view log entries. — Past 7 Days Provides metrics for the past 7 days. Metrics are displayed based on the period that you select. You can check details about the service assemblies and service units belonging to the environment. select any of the following options from the Period drop-down list: — Past Hour Provides metrics for the past hour. See Service View on page 259. see Using the Log Viewer on page 316. — Infrastructure Monitor environments. Select view 2. Select environment 3. — Deployment Display deployment data in an environment. See Infrastructure View on page 248. Select Monitor & Manage from the Perspective drop-down list. you can view the metrics data for the past 24 hours. Only the system and service metrics belonging to that environment are displayed. For details on this view. See Dashboard View on page 245. Select period TIBCO ActiveMatrix Administration . If available for the selected view. To change the period for monitoring.244 | Chapter 9 Monitoring Infrastructure and Services Accessing the Monitor & Manage Perspective To view the monitoring and management screens: 1. — Service Search for services. machines. — Past 24 Hours Provides metrics for the past 24 hours. select the name of the environment from the Environment drop-down list to view metrics data related to a specific environment.

The columns in the table specify the following details about a service. Number of times the service has been invoked. The Dashboard view displays the overall health of the system including a summary of service and system performance. Top 20 Hits The top 20 services that were the most active with respect to the specified period are displayed in this table. The Dashboard view is divided into two areas: • • Service Metrics on page 245 System Metrics on page 246 Service Metrics The service metrics area allows you to view the services with respect to the specified period.Dashboard View 245 | Dashboard View When you select the Monitor & Manage perspective. you enter in the Dashboard view by default. You can click the service name to view the details of the service in the Service view as described in Service View on page 259. A graphical representation of the hit history over the specified time period is displayed as a bar graph next to the Hits value. TIBCO ActiveMatrix Administration . The dashboard is an operational view of services and is updated automatically without intervention at regular frequency. Table 62 Top 20 Hits Column Name Hits Description The service name.

either Stopped or Running. yellow. and red values indicate the amount of memory consumed by the machine (Green = 0-50%. and Red = 76-100%). Hostname is a link that you can click to see the details of the machine. For example. The amount of memory consumed by the services running on the machine against the available memory is displayed as a bar graph. if the bar becomes red. The bar signifies the amount of memory in use. The current status of the service. the details are displayed as described in Machine View on page 251.246 | Chapter 9 Monitoring Infrastructure and Services Top 20 Faults The top 20 services that were failing the most with respect to the specified period are displayed in this table. Machines The Machines table displays information about machines enabled in the selected environment. After you click Hostname. it signifies that the memory consumption is very high and it may degrade the system performance. Yellow = 51-75%. OS Memory TIBCO ActiveMatrix Administration . The green. Number of times the service failed to fulfill the request. System Metrics The system metrics area allows you to view machine and node details with respect to the specified environment. The columns in the table specify the following details about a service. The details of the operating system available on the machine. The properties of the features on each machine are described by the columns listed in the following table. Table 64 Machines Column Hostname Description The name of the machine. Table 63 Top 20 Faults Column Name Status Faults Description The service name. You can click the service name to view the details of the service in the Service view as described in Service View on page 259.

yellow. The name of the machine on which the node is running. the number 68/120 specifies that 68 MB is in use from the total 120 MB available. Running. After you click Hostname. The properties of each node are described by the columns described in Table 65. Yellow = 51-75%. the details are displayed as described in the Node View on page 254. The bar signifies the amount of memory in use.Dashboard View 247 | Nodes The Nodes table displays information about the nodes added in the selected environment. Name is a link that you can click to see the details of the node. the details are displayed as described in Machine View on page 251. For example. and Red = 76-100%). Number of services deployed on the node. The JVM memory consumed by various services from the total available memory is displayed as a bar graph in Megabytes. StartFailed. The number of fault to successful responses of services on a node. Table 65 Nodes Column Name Description The name of the node. either Installed/Stopped. Status # of Services Faults/Successes JVM Memory Hostname TIBCO ActiveMatrix Administration . Starting. Hostname is a link that you can click to see the details of the machine. The current status of the node. The green. After you click Name. and red values indicate the amount of memory consumed by the machine (Green = 0-50%.

select a value in the Environments. and then click View Environment. Total number of active nodes against the total number of available nodes in the selected environment. the details are displayed as described in Machine View on page 251. Hostname is a link that you can click to see the details of the machine. Machines The Machines table displays details of the machines enabled in the selected environment. The following machine properties are displayed as columns in the table. Machines. or View Node. In Browse mode (see Browse Mode on page 289). Table 66 Machines Column Hostname Description The name of the machine. After you click Hostname. Total number of active services against the total number of available services in the selected environment. The Infrastructure view consists of three subviews: • • • Environment View on page 248 Machine View on page 251 Node View on page 254 Environment View In the top area. click Infrastructure. You can navigate to the Infrastructure view by using either of the following ways: • • Click the Infrastructure link.248 | Chapter 9 Monitoring Infrastructure and Services Infrastructure View The Infrastructure view allows you to see the status of machines and nodes within an environment. or Node columns. the following details are displayed: • • • The name of the selected environment. View Machine. TIBCO ActiveMatrix Administration .

the yellow bar turns green. if the memory usage is too high.Infrastructure View 249 | Table 66 Machines (Cont’d) Column OS Memory Description The operating system running on the machine. The amount of memory in use. Table 67 Nodes Column Name Description The name of the node. Name is a link that you can click to see the details of the node. The following properties of nodes are displayed as columns in the table. Yellow = 51-75%. If the memory usage is low. However. Nodes The Nodes table displays the details of the nodes in the selected environment. The green. The bar signifies the amount of memory in use. TIBCO ActiveMatrix Administration . the details are displayed as described in the Node View on page 254. yellow. the yellow bar turns red. After you click Name. and Red = 76-100%). The memory usage is displayed as a bar graph where the used memory is displayed as a yellow bar against the total available memory. and red values indicate the amount of memory consumed on the machine (Green = 0-50%.

The number of fault to successful responses of services on a node. Installed Node configuration files have been successfully generated on the machine. hours. The number of services deployed on the node. hours. The number of containers on the node. The CPU time is displayed in terms of days. Uninstalling Node configuration files are in the process of being removed from the machine.250 | Chapter 9 Monitoring Infrastructure and Services Table 67 Nodes (Cont’d) Column Status Description The node’s status: • • Defined The node is defined in the database but the configuration files have not been installed on the machine. The amount of CPU time consumed by the node since the node was started. • • • • • • • • # of Services # of Containers Uptime CPU Time Faults/Successes Start Failed1 Node startup has failed. The amount of time that has elapsed since the node was started. Starting The node is in the process of being started. Installed/Stopped1 The node configuration files have been installed on the machine but the node is not running. TIBCO ActiveMatrix Administration . Running1 The node is running. Stop Failed1 Node stop has failed. This state occurs after the node has been installed but before it has been started or after it has been started and then stopped. The uptime is displayed in terms of days. Unknown The status of the node cannot be determined. Uninstall Failed1 Node uninstallation has failed. and minutes. • • • Installing Node configuration files are in the process of being generated on the machine. and minutes. Stopping The node is in the process of being stopped. Install Failed1 Node installation has failed. but whether the node process is running or stopped is not known.

The green.100%). You can click the hostname to get more details about the machine as described in Machine View. yellow.Infrastructure View 251 | Table 67 Nodes (Cont’d) Column JVM Memory Description The amount of JVM used by the node against the total available memory (in use/Total MB) is displayed as a bar graph. and red values indicate the amount of memory consumed by the machine (Green = 0-50%. The status is a link that you can click to display a screen with information about the error. Hostname 1. The operating system running on the machine. The name of the machine on which the node is running. Overview The overview contains the following information about the selected machine. The bar signifies the amount of memory in use. click a machine name in the Machines table. TIBCO ActiveMatrix Administration . Machine View To open the Machine view. View Logs Select the View Logs button to open the View Logs dialog where you choose the logs to view for the selected element. See Using the Log Viewer on page 316 for details. The path where TIBCO products are installed on the machine. Yellow = 51-75%. The Machine view provides details of a particular machine and information about the nodes running in various environments on that machine. and Red = 76 . Table 68 Machine Details Metric Name OS TIBCO Home Description The name of the machine.

TIBCO ActiveMatrix Administration . If the bar becomes orange. Table 69 Nodes Column Name Description The names of the nodes added to different environments on the selected machine are displayed. Bound | Not Available The machine has been bound to the ActiveMatrix Administrator cluster but is not available. and red values indicate the amount of memory consumed by the machine (Green = 0-50%.252 | Chapter 9 Monitoring Infrastructure and Services Table 68 Machine Details (Cont’d) Metric Memory Description The amount of memory consumed by the services running on the machine against the available memory is displayed as a bar graph. This could be because it stopped or because the network connection failed. The bar signifies the amount of memory in use. and Red = 76 . yellow. The green. Yellow = 51-75%. Agent Down The machine is not accessible. it signifies that the memory consumption is very high and it may degrade the system performance. Possible values are: • • • Bound | Available The machine has been bound to the ActiveMatrix Administrator cluster and is available. The following details of each node are displayed as columns in this table. The green bar signifies the amount of memory in use. You can click the node name to get details of the node as described in Node View on page 254.100%). Nodes The Nodes table displays all the nodes configured on the specified machine in different environments. Status The status of the machine.

hours. # of Services # of Containers Uptime CPU Time Total number of services deployed on the node. Install Failed1 Node installation has failed.Infrastructure View 253 | Table 69 Nodes (Cont’d) Column Status Description The node’s status: • • Defined The node is defined in the database but the configuration files have not been installed on the machine. • • • Installing Node configuration files are in the process of being generated on the machine. Installed/Stopped1 The node configuration files have been installed on the machine but the node is not running. Running1 The node is running. hours. but whether the node process is running or stopped is not known. Stopping The node is in the process of being stopped. Uninstalling Node configuration files are in the process of being removed from the machine. The amount of CPU time consumed by the nodes running on that machine. The CPU time is displayed in terms of days. Uninstall Failed1 Node uninstallation has failed. The amount of time that has elapsed since the node was installed. Faults/Successes TIBCO ActiveMatrix Administration . and minutes. Total number of containers activated on the node. This state occurs after the node has been installed but before it has been started or after it has been started and then stopped. The uptime is displayed in terms of days. Installed Node configuration files have been successfully generated on the machine. Unknown The status of the node cannot be determined. Starting The node is in the process of being started. The number of fault to successful responses. • • • • • • • Start Failed1 Node startup has failed. Stop Failed1 Node stop has failed. and minutes.

click a node name in the Nodes table.100%). The green. and Red = 76 . Node View To display the Node view. shared resources. and service instances in a tabular format. Hostname 1.254 | Chapter 9 Monitoring Infrastructure and Services Table 69 Nodes (Cont’d) Column JVM Memory Description The amount of JVM memory used by the node against the total available memory is displayed as a bar graph. The Node view provides overview and details about containers. The Node view is divided into the following areas: • • • • • Node Trail on page 255 Overview on page 255 Containers on page 256 Shared Resources on page 257 Service Instances on page 257 TIBCO ActiveMatrix Administration . The bar signifies the amount of memory in use. yellow. The status is a link that you can click to display a screen with information about the error. You can click the hostname to get more details about the machine as described in Machine View on page 251. Yellow = 51-75%. The name of the machine on which the node is running. and red values indicate the amount of memory consumed by the machine (Green = 0-50%.

When you click machineName. click the Refresh icon located at the top right of the table until the node’s status changes to Running or Installed/Stopped. The description of the node. The View Logs button opens the View Logs dialog where you choose the logs to view for the selected element. it opens the Machine subview of the Infrastructure view. Physical Displays the physical trail to the node. In either case. Table 71 Node Details Metric Name Description Date Installed Description The name of the node. TIBCO ActiveMatrix Administration .Infrastructure View 255 | Node Trail The node trail is displayed in the top area as shown: Table 70 Node Trail Column envName Description envName is the name of environment containing the node. The date and time when the node was installed on the machine. Overview Below the node trail. The following details about the selected node are displayed in the overview section. it opens the Environment subview of the Deployment view. You can start and stop the node using the Start or Stop button. When you click envName. The trail shows where the node was physically installed as follows: PHYSICAL machineName where machineName is the name of the machine. the node name and its status is displayed.

The bar signifies the amount of memory in use. Each node is associated with one messaging server. Time Period The amount of time when the node was down against the time Availability when the node was up and running (that is. Yellow = 51-75%. Since Started The number of faults encountered since the node was started. and Red = 76 . downtime versus uptime percentage) since the node was started. The amount of time that has elapsed since the node was started.100%). Faults Time Period The number of faults encountered in the selected period. The following properties of containers are displayed as columns of this table. Since Started The number of successful responses since the node was started. downtime versus uptime percentage) in the selected period. and red values indicate the amount of memory consumed by the machine (Green = 0-50%. Since Started The amount of time when the node was down against the time when the node was up and running (that is. The amount of CPU time consumed by the node since the node was started. The date and time when the node was started. Successes Time Period The number of successful responses in the selected period. The green. The version of the container. The amount of JVM memory consumed by the node against the total amount of memory available is displayed along with a bar graph.256 | Chapter 9 Monitoring Infrastructure and Services Table 71 Node Details Metric Installed By Messaging Server Start Date Uptime CPU Time JVM Memory Description The name of the person who installed the node. The messaging server used for this node’s transport requirements. Containers The Containers table displays the containers enabled on the selected node. yellow. TIBCO ActiveMatrix Administration . Table 72 Containers Column Name Version Description The name of the container running on the selected node.

use the Filter option on the top bar. and Implementation type. To limit the number of services. Table 74 describes the properties of the services. In the top bar right corner. Rendezvous. You can set the filter criteria based on the number Hits. JNDI. The type of resource: • • Composite Service Specifies that this service belongs to an outside Description The name of the shared resource available on the selected node. For information on how to set the filter criteria.Infrastructure View 257 | Shared Resources The Shared Resources table displays the shared resources available on the selected node. see Specify the service filter on page 260. Fault/Success Ratio. The type of service implementation in a container such as TIBCO ActiveMatrix Java. The version of the service. and .NET. Adapter. JMS. Composite Reference Specifies that this service is not provided by the same composite and is referenced externally to services provided by an outside composite. or SSL. JDBC. the total number of services displayed in the table against the total number of services available is displayed. You can click Name to get details about the service as described in Service Instance View on page 278. Mediation. Table 74 Service Instances Column Name Version Container Type Resource Type Description The name of the service. SOAP. Table 73 Shared Resources Column Name Type Service Instances The Service Instances table displays the services running on the selected node. TIBCO ActiveMatrix Administration . JMS. • Component Specifies the name of the component to which the service belongs in the same composite. composite. The type of the shared resource: HTTP.

258 | Chapter 9 Monitoring Infrastructure and Services Table 74 Service Instances (Cont’d) Column Start Date Uptime Hits Fault/Successes Throughput Description The date the service was started. calculated as response count/interval. Responses per second during the interval. The uptime is displayed in terms of days. The number of service invocations per second. The number of service invocations since the service was started or the time period was set. Average Response Time The mean response time (in milliseconds) of all successful responses to request messages during the interval. and minutes. whichever is later. The amount of time that has elapsed since the service was started. hours. TIBCO ActiveMatrix Administration . Number of requests that resulted in a fault message/Number of request messages that arrived at the endpoint.

S2. the value of a service metric is the average over all the service instances. Detailed information about services can be viewed in one of the following subviews: • • Integrated Service View on page 262 Provides details about services. and SI3—in the Service Instance view. For average metrics. Service Instance View on page 278 Provides details about service instances. In this configuration there are three services—S1.Service View 259 | Service View The Service view allows you to search for and see a summary of the status of services. and S3—whose metrics you would view in the Integrated Service view. consider the configuration illustrated in Figure 20. S1and S2 each have two service instances: S1 has service instances SI1a and SI2b and S2 has service instances SI2a and SI2b. To understand the difference between services and service instances. SI2b. the value of a service metric is simply the sum of the values of that metric for all the service’s instances. Service S3 has only one instance. SI3. Figure 20 Services and Service Instances S1 S2 S3 SI1a SI1b SI2a SI2b SI3 Node 1 Node 2 Node 3 TIBCO ActiveMatrix Administration . SI2a. For absolute metrics. SI1b. You view the metrics of service instances—SI1a.

The services matching the specified search criteria are displayed in the Services table in the search results area. The endpoints of the slider are the minimum and maximum values of hits from the service results. The filter criteria are: — Hits Set the arrows on the slider to define a range for filtering the services based on the number of hits. The default is All Types. — Faults/Hits Ratio Set the arrows on the slider to define a range for filtering the services based on the Fault/Hits ratio. Based on the Service Instances displayed in the table. If you specify no fields. The endpoints of the slider are the minimum and maximum values of the Fault/Hits ratio based on the service results. Click Search to get results matching the search criteria. This is a matching string search. — Resource Type The resource type. — Namespace The service namespace. 2. so no wild cards are allowed. — Interface Name The name of interface. Specify zero or more of the search criteria fields: — Name The name of the service you are searching for. You can filter the services further by defining filter criteria. all service names beginning with Ser are displayed. Only the services with hits within the specified range are displayed in the results area. Table 75 on page 261 describes the properties of services. if you enter Ser for the name. The names of all the services identified with the specified namespace are displayed. — Container Type Select the services of specific implementation type from the drop-down list. You can select Composite Service.260 | Chapter 9 Monitoring Infrastructure and Services Searching for Services To search for services: Specify search criteria 1. All Types is selected. For example. Component. all services are returned. or Composite Reference from the drop-down list. the container types are displayed in the drop-down. TIBCO ActiveMatrix Administration . The area expands and displays the existing filter criteria. By default. Specify the service filter 3. Click Filter on the to display the filter criteria. The names of all the services implementing the specified interface are displayed. Only the services with ratio within the specified range are displayed in the results area. if other criteria are met.

Composite Reference Specifies that this service is not provided by the same composite and is referenced externally to services provided by an outside composite. hours. the first 500 matching results are displayed. TIBCO ActiveMatrix Administration . click the Reset button. The type of resource: • • Composite Service Specifies that this service belongs to an outside Version Container Type Resource Type composite. Adapter. • Start Date Uptime Hits Faults/Successes Throughput (requests/minute) Average Response Time Component Specifies the name of the component to which the service belongs in the same composite. Click the service name to get details about the service as described in Integrated Service View on page 262. To discard the filter criteria and display all the services. The data changes for the selected time period. The types can be TIBCO ActiveMatrix Java. in ascending alphabetical order. and minutes. The service version. and . The amount of time that has elapsed since the service was started. all the results are sorted by service name. JMS. By default. If there are too many results. The ratio of number of failed hits to the number of successful hits for the selected service for the selected period. The uptime is displayed in terms of days. The type of the service implementation. SOAP. The average amount of time in milliseconds between receiving a request and returning a response over the selected period. The number of times the service has been invoked during the selected period.Service View 261 | Click the Refresh icon to display the results based on the filter criteria.NET. The date and time when the service was started. The performance data such as the average number of requests processed per minute for the selected period. Mediation. Table 75 Services Column Name Description The name of the service that satisfies the search criteria.

After you select a service unit. Click Service and specify a Search Criteria to view only the required services. You navigate to the Integrated Service view as follows: • • Click Dashboard and select a service name link from the Service Metrics tables.262 | Chapter 9 Monitoring Infrastructure and Services Integrated Service View The Integrated Service view provides a view of services. Click the service name in the Services table from the displayed results in the search results area. Service Assemblies. click the View Services On Service Unit button. — Click Deployment and select a value in the Environments. click the View Services On Service Assembly button. The Integrated Service view is divided into the following areas: • • • Service Trail on page 263 Service Details on page 263 Tabbed Notebook: — Overview on page 264 — Provides & Consumes on page 266 — Deployment Details on page 271 — UDDI Publishing on page 273 • TIBCO ActiveMatrix Administration . and Service Units columns. In Browse mode (see Browse Mode on page 289): — Click Deployment and select a value in the Environments and Service Assemblies columns. After you select a service assembly.

For example. it opens the respective subview of the Deployment view. envName When you click envName. • • serviceAssemblyName is the service assembly with which this service is serviceAssemblyName > serviceUnitName associated. TIBCO ActiveMatrix Administration . myService on 10 Nodes. The name of the service and number of nodes the service is deployed to are also displayed. LOGICAL where. Logical Displays the logical trail to the service. Service Details The top section displays the service name with number of nodes that the service is deployed to.Integrated Service View 263 | Service Trail The service trail is provided in the top area: Table 76 Metric Service Trail Description envName is the name of environment containing the node. When you click a name. serviceUnitName is the service unit with which this service is associated. See Using the Log Viewer on page 316 for details. The trail shows how the service was deployed. it opens the Environment subview of the Deployment view. View Logs The View Logs button opens the View Logs dialog where you choose the logs to view for the selected element.

wsdl or display the file. WSDL is generated. number of requests. The type of the service implementation: TIBCO ActiveMatrix Java. JMS. and performance data. Concrete. You are offered the option to save a file named service. SOAP. Table 77 Services Details Metric Name Description Implementation Namespace Faults/Successes The number of failed hits to successful hits for the selected period is displayed as a pie chart. Overview The Overview tab provides information about the service such as name. Adapter. TIBCO ActiveMatrix Administration . not abstract. You cannot generate WSDL for a component service or a composite reference. description. The namespace that identifies the web service that implements the service. The description of the service.NET.264 | Chapter 9 Monitoring Infrastructure and Services Generate WSDL The Generate WSDL button is displayed if the service is a composite service. Mediation. To download the WSDL file. Description The name of the service. and . the WSDL file is displayed in a dialog. The available periods are Time Period or Since Started. Click the Cancel button to dismiss the dialog. click the Click to download file link. When you click the button.

Table 78 Metric Start Date Availability Performance Description The date and time when the service was started. The data in the graph builds from left to right in real time and moves relative to the selected period. The total number of requests. Total Requests A graph. is displayed and updated in real time. The values of the metrics are updated every minute and displayed in the graph. Performance The Performance table provides details about the service performance. The X-axis represents the selected period and the Y-axis displays the response time in milliseconds. Uptime TIBCO ActiveMatrix Administration . The amount of time when the service was down against the time when the service was up and running (that is. The uptime is displayed in terms of days. The percentage is displayed in color: green indicates a percentage in the range 51-100% and red represents 0 – 50%. are plotted on the Y-axis. and response time. The graph in green displays the number of successful hits and the graph in red displays the number of faults at the given time. The amount of time that has elapsed since the service was started. and minutes. number of successes. hours. downtime versus uptime percentage). Moving the cursor on the graph opens a pop-up windows that provides details such as Successful Requests % and Faults %. categorized into successes and faults.Integrated Service View 265 | The data on the graph is displayed in color where green represents successful hits and red represents failed hits. number of faults. Table 78 describes the details about a service performance. Note that the graph is to scale. A bar graph below the Total Requests graph shows the service response time in milliseconds. The selected period is displayed on the X-axis. Selecting a location on the graph opens a pop-up window that provides details such as date and time. plotted between the number of requests against the selected period.

The tables that appear depend on the type of the service: • • • Component on page 267 Composite Service on page 268 Composite Reference on page 269 TIBCO ActiveMatrix Administration . This is the average per minute since the start date and time. Provides & Consumes The Provides & Consumes tab display details on the interfaces provided and consumed by the service. Since Started The total number of requests processed by the service per minute. If the period is already set to Since Started. the column Since Started does not appear in the Performance table.266 | Chapter 9 Table 78 Metric Monitoring Infrastructure and Services Performance (Cont’d) Description The performance data for the selected period. Average Response Time The average amount of time in milliseconds between receiving a request and returning a response over the selected period: • • Time Period The average request response time in milliseconds. Since Started The average request response time in milliseconds. This is the average since the start date and time. This is the average over the selected period. The data changes for the type of period: • • Time Period The average number of requests processed per minute in Throughput (requests/minute) the selected time period. Total Requests The total number of service requests received in the selected period and since the service was started.

The names are sorted in ascending alphabetical order. Table 80 Interface Consumed By Column Name Description The names of the services. Table 79 describes the details about the interfaces. The ratio of faults to successful hits for the selected period. page 278. Click the service to see information about the service as described in the Service Instance View. Type Fault/Success Hits TIBCO ActiveMatrix Administration . The number of times the service is invoked for the selected period. The composite element type of the consuming service. Table 80 describes the details about the services. The number of times the service is invoked for the selected period. The port type supported by the service. Table 79 Provides Column Interface Name Port Type Fault/Success Hits Description The name of the interface. The ratio of faults to successful hits for the selected period. Interface Consumed By The services consumed by the interface selected in the Provides table are displayed in the Interface Consumed By table.Integrated Service View 267 | Component Provides The Provides table gives details on the provided interface. The services are sorted in ascending alphabetical order.

The ratio of failed to successful hits for the selected period. Table 81 Consumes Column Interface Name Port Type Fault/Success Hits Description The name of the interface implemented by the consumed service. The composite element type of the consumed service. The ratio of faults to successful hits for the selected period. Table 82 Interface Invokes Column Name Type Fault/Success Hits Composite Service A composite service is a provider and provides a binding URL for external access. page 278. The number of times the service is invoked for the selected period. Table 81 describes the details about the consumer interface. The names appear in ascending order. The port type supported by the consumed service. Click the service to see information about the service as described in the Service Instance View. which is the binding URL provided by the composite service. External Endpoint The provided service can be accessed from external services using an external endpoint.268 | Chapter 9 Monitoring Infrastructure and Services Consumes The Consumes table provides details about the interfaces that are implemented by a consumed service. Table 82 describes the details about the services. The number of times the service is invoked for the selected period. Description The name of the service. TIBCO ActiveMatrix Administration . You can generate a concrete WSDL file for a composite service. Interface Invokes The services consumed by the interface selected in the Consumes table are displayed in the Interface Invokes table.

S3R1 is selected. The names appear in ascending order. The number of times the service is invoked for the selected period. The ratio of faults to successful hits for the selected period.Integrated Service View 269 | Consumes The Consumes table lists the services the composite service is consuming. Component Service S4I1 is pre-selected in the Provides table and in the Interfaces Consumed By table. The ratio of faults to successful hits for the selected period. Table 83 Composite Service Consumes Column Interface Name Port Type Fault/Success Hits Description The name of the service being consumed by the service. the Provides & Consumes tab for Component S4 is opened. Composite Reference A composite reference is a provider and consumes an external binding URL. The port type being consumed by the service. Table 84 describes the details about the services. Type Fault/Success Hits The composite element type of the consumed service. Table 84 Interface Invokes Column Name Description The name of the service consumed by the selected interface. For example. Table 83 describes the details of the services. if you select interface S3R1 in the Consumes table and select Component Service S4I1 in the Interface Invokes table. TIBCO ActiveMatrix Administration . The number of time the service is invoked for the selected period. Interface Invokes The services invoked by the interface selected in the Consumes table are displayed in the Interface Invokes table.

The number of times the service is invoked for the selected period. Table 85 Composite Reference Provides Column Interface Name Port Type Fault/Success Hits Description The name of the interface. Interface Consumed By The services consuming the interface that you select in the Provides table appear in Interface Consumed By table. the Provides & Consumes link for Component S2 is opened. In the Interface Invokes table. Table 86 Interface Consumed By Column Name Description The name of the service consuming the selected interface. The services are sorted in ascending alphabetical order. Table 85 describes the details about the provided interfaces. Table 86 describes the details about the services. if you select interface S1I1 in the Provides table and select Component Reference S2R1 in the Interfaces Consumed By table. TIBCO ActiveMatrix Administration . Type Fault/Success Hits The composite element type of the provided service. The ratio of faults to successful hits for the selected period. S1I1 is selected. The ratio faults to successful hits for the selected period. You can click the S1I1 link to return to this screen. The number of times the service is invoked for the selected period. External Endpoint The binding URL referenced by the composite reference. For example. The port type supported by the service.270 | Chapter 9 Monitoring Infrastructure and Services Provides The Provides table displays information about the interfaces the composite reference provides. Component Reference S2R1 is pre-selected in the Consumes table.

Number of requests per minute for the selected time period across all nodes the service is deployed to. You can expand or collapse the data for each interface. It also provides performance details by interface and operation across all nodes. Interfaces & Operations The Interfaces & Operations table lists all the operations defined in services deployed on nodes.Integrated Service View 271 | Deployment Details The Deployment Details tab provides deployment details for the service. Table 87 Interfaces and Operations Column Name Description The interface and operation names. Average The average request response time for the selected operation. This is across all nodes the service is deployed to. The average response time for the selected operation for the selected period categorized by: • • • Message Size (KB) Minimum The minimum request response time for the selected operation. This is across all nodes the service is deployed to. The interfaces and operations are sorted in ascending alphabetical order. including the nodes the service is deployed to. Maximum The maximum message size for the selected operation. The operations are grouped under interfaces. TIBCO ActiveMatrix Administration . The ratio of the number of failed hits to the number of successful hits for the selected period. Hits Fault/Success Throughput Response Time (millisecond) The average message size for the selected operation for the selected period categorized by: • • • Minimum The minimum message size for the selected operation. Maximum The maximum request response time for the selected operation. Average The average message size for the selected operation. The total number of requests for the selected operation for the selected time period.

there are three transient states that can be displayed: Installing. Link to the Service Instance view on the specified node as described in Service Instance View. Table 88 Nodes Column Node Name Status Description The names of the nodes on which the service is deployed. and Stopping. Installed/Stopped The node has been installed on the machine but the node is currently not running. The status can be: • • • • Defined The node definition is added but the node is not installed or has been uninstalled after installation. If there is a problem. Running The node process is running. TIBCO ActiveMatrix Administration . Table 88 describes the details of the service. page 278. • • • • In addition.272 | Chapter 9 Monitoring Infrastructure and Services Service Deployed to N Nodes This table provides details about how the selected service is deployed across all nodes. Same status as Uninstalled. This state occurs after the node has been installed but before it has been started or after it has been started and then stopped. Fault/Success Hits View Service Instance Details The ratio of failed to successful hits for the selected period across all nodes on which the service is deployed. Installed Node configuration files have been successfully generated on the machine. Number of times the service is used. Start Failed Node startup failed. Stop Failed The node stop routine has failed to stop the node process. The status of the node on which service is running. Starting. an error icon is displayed next to the message. Unknown The state of the node cannot be determined. Install Failed Node installation has failed. but whether the node process is running or stopped is not known.

In the Action column. 4. Optionally add metadata. See Adding a UDDI Server on page 154 and Enabling UDDI Servers in an Environment on page 184 Publishing a Service To publish a service: 1. • • To sync or unpublish a service: 1. click Publish. and sync the publish state of a service. For example. Syncing or Unpublishing a Service You may need to resynchronize the publish status of a service with the UDDI server for the following reasons: • The service is out of sync with the deployed service instances. 2. The system crashed during a publish and the service was not published across all UDDI servers. 2. Only UDDI servers added to the enterprise and enabled for the environment are available. 3. UDDI Publishing Reference Figure 21 on page 274 shows the UDDI Publishing tab for the service JavaSOAPService. Select a UDDI server.Integrated Service View 273 | UDDI Publishing UDDI Publishing tab allows you to publish. Select a UDDI server. See UDDI Servers on page 274. you may have deployed the service to a new node after you initially published to the UDDI server. In the Action column. Permission to publish to a business was not granted to the user. See Metadata on page 276. Select a business. click Sync or Unpublish. You can publish a composite service to any number of UDDI servers. See Business on page 275. unpublish. The service is published to one UDDI server. The areas of the tab are described in the sections: • • • UUID on page 274 UDDI Servers on page 274 Metadata on page 276 TIBCO ActiveMatrix Administration .

See Enabling Non-Administrator Users to Publish to the ActiveMatrix Registry on page 374. TIBCO ActiveMatrix Administration . If you are publishing to ActiveMatrix Registry and you are not the admin user of the registry.274 | Chapter 9 Monitoring Infrastructure and Services • Endpoint Chosen for Publication on page 277 Figure 21 UDDI Publishing Tab UUID The UUID (universally unique identifier) for the service. you must first transfer ownership of a specific tModel to a non-admin user. UDDI Servers Table 89 UDDI Servers Column Name Description The name of the UDDI server. Publish URL The publish URL of the UDDI server.

Publish Incomplete Displays for one of the following reasons: — The service is out of sync with the deployed service instances. The business name must contain only alphanumeric characters. For example. ^. you may have deployed the service to a new node after you initially published to the UDDI server. Unpublished The service is not published. -Select. the business name does not appear in the list. The Business is set to -Select- and the Action button is set to Publish. If not yet published. TIBCO ActiveMatrix Administration . The Action button is set to Unpublish. For strict control. group. — The system crashed during a publish and the service was not published across all UDDI servers. If the business name contains special character such as $.Integrated Service View 275 | Table 89 UDDI Servers (Cont’d) Column Status Description The publish status: • • • Published The service has been published to the selected UDDI server.is displayed as the first item in the drop-down list and the Publish button is enabled. For ActiveMatrix Registry. or &. For details. system#everyone group can be granted read access and the publishing user can be granted read and write access. and access permissions for the business to a special group that contains all users (such as user. write. and system). Business A drop-down list of the businesses registered in the selected UDDI server. see Adding Permission to Publish to a Business on page 376. %. — Permission to publish to a business was not granted to the user. you must provide read. correct access permissions need to be granted. In order for a user to publish services to a business created by another user. The Action buttons are set to Publish and Unpublish.

the following buttons display: • Unpublish Unpublishes to the selected Publish URL and Business. If the UDDI server is unavailable when you perform this action. Table 90 Metadata Column Name Value Description The name of the metadata. c. Click Save.276 | Chapter 9 Monitoring Infrastructure and Services Table 89 UDDI Servers (Cont’d) Column Action Description Based on the status. You must remove the service from the UDDI server when it is available. You delete the metadata by clicking the Remove link in the same row. b. • Publish Publishes to the selected UDDI server and business. The value of the metadata. If status is set to Unpublished. the status changes to Unpublished and the button label changes to Publish reflecting the publish status of the service in the ActiveMatrix Administrator database. If status is set to Published. ActiveMatrix Administrator automatically publishes the metadata to all UDDI servers. Metadata To add metadata at the logical service level (that is. a. the button state is Unpublish. but the service is not removed from the UDDI server. The Add Metadata dialog appears. TIBCO ActiveMatrix Administration . parent service): 1. the button state is Publish. Enter data in the Name and Value text fields. Click Add.

you must manually edit the service instance endpoint and replace it with the URL of the load balancer. The node on which the service instance is deployed. Therefore. Table 91 Endpoint Chosen for Publication Column Service Instance Name Node Unique ID Description The name of the service instance. most enterprises will maintain a load balance URL for the service that will dispatch requests to the service instances. To use the load balance URL. TIBCO ActiveMatrix Administration . only one of those service instances is chosen to be published to the UDDI server. The UUID (Universally Unique Identifier) for the service instance. However.Integrated Service View 277 | Endpoint Chosen for Publication A composite service that has been deployed to multiple nodes has multiple service instances. Table 91 displays the deployment details of the service instance chosen for publication for the selected service.

278

| Chapter 9

Monitoring Infrastructure and Services

Service Instance View
You navigate to the Service Instance view as follows: • Open the Integrated Service view as described in Integrated Service View on page 262 and click the Deployment Details tab. Click the View Service Instance Details link. Select the Infrastructure link and click a node in the Nodes table. Select the service name link from the Service Instances table. In Browse mode (see Browse Mode on page 289), click Infrastructure and select a values in the Environments, Machines, and Nodes columns. After you select an environment, machine, or node, click the View Service Instances button. From the displayed list of services, select a service name from the Name column.

• •

The Service Instance view is divided into the following areas: • • • Service Instance Trail on page 278 Service Instance Details on page 279 Tabbed Notebook: — Overview on page 280 — Operations on page 281

Service Instance Trail
The service instance trail is displayed in the top area:

Table 92 Service Instance Trail Column envName Description
envName is the name of environment containing the service instance.

When you click envName, it opens the Environment subview of the Deployment view.

TIBCO ActiveMatrix Administration

Service Instance View 279

|

Table 92 Service Instance Trail (Cont’d) Column Logical Description Displays the logical trail of the service instance. The trail shows how the service instance was deployed as follows: LOGICAL where • •
serviceAssemblyName: The service assembly the service instance is serviceAssemblyName > serviceUnitName

associated with.
serviceUnitName: The service unit this service instance is associated with.

When you click a name, it opens the respective subview of the Deployment view. Physical Displays the physical trail to the service instance. The trail shows where the service was physically deployed as follows: PHYSICAL where • •
machineName: The name of the machine the service instance is running on. nodeName: The name of the node the service instance is deployed to. machineName > nodeName

When you click a name, it opens the respective subview of the Infrastructure view.

Service Instance Details
Below the service instance trail, the service name with the associated node is displayed. For example, myService on Node32. Click View Service on All Nodes to open the Deployment Details tab where you view interface and operation deployment details for the service. The View Logs button opens the View Logs dialog where you choose the logs to view for the selected element. See Using the Log Viewer on page 316 for details.

TIBCO ActiveMatrix Administration

280

| Chapter 9

Monitoring Infrastructure and Services

Overview
The Overview tab provides summary of service instances. Table 93 Service Instance Overview Metric Name Description Implementation Namespace Faults/Successes The the number of failed hits to the successful hits for the selected period is displayed as a Pie chart. The available periods are Time Period or Since Started. The data on the graph is displayed in color where green represents successful hits and red represents failed hits. Total Requests A graph, plotted between the number of requests against the selected period, is displayed and updated in real time. Total number of requests, categorized into successes and faults, are plotted on the Y-axis. The selected period is displayed on the X-axis. Note that the graph is not to scale. The data in the graph builds from left to right in real time and moves relative to the selected period. The values of the metrics are updated every minute and displayed in the graph. The graph in green displays the number of successful hits and the graph in red displays the number of faults at the given time. Selecting a location on the graph opens a pop-up window that provides details such as date and time, number of faults, number of successes, and response time. A bar graph below the requests graph shows the service response time in milliseconds for that moment in time. The X-axis represents the selected period and the Y-axis displays the response time in milliseconds. Description The name of the service instance. The description of the service instance. The type of the service implementation. It can be TIBCO ActiveMatrix Java, SOAP, JMS, Mediation, Adapter, and .NET. The namespace that identifies the web service that implements the service.

TIBCO ActiveMatrix Administration

Service Instance View 281

|

Performance The chart shows performance data for the service instance per selected period and since the service started. Table 94 Performance Column Start Date Availability Description The date and time that the service was started. The amount of time as a percentage that the service was down against the time when the service was up and running (that is, downtime versus uptime percentage). The percentage is displayed in color: green indicates a percentage in the range of 51-100% and red represents 0 – 50%. The amount of time that has elapsed since the service was started. The uptime is displayed in terms of days, hours, and minutes. The performance data for the selected period. The data changes for the selected period: • • Average Response Time
Time Period The average number of requests processed per minute in

Uptime Throughput (requests/minute)

the specified period. Past 24 hours is the default period.
Since Started The total number of requests processed by the service per

minute. This is the average per minute since the start date and time. The average amount of time in milliseconds between receiving a request and returning a response during the selected period: • • Total Requests
Time Period The average request response time in milliseconds in the

specified period. Past 24 hours is the default period.
Since Started The average request response time in milliseconds. This

is the average per millisecond since the start date and time. The total number of service requests received in the specified period and since the service started. If Period is already set to Since Started, the column Since Started does not appear in the Performance table.

Operations
The Operations tab provides list of interfaces and operations available in the service instance.

TIBCO ActiveMatrix Administration

282

| Chapter 9

Monitoring Infrastructure and Services

Interfaces & Operations The Interfaces and Operations table lists all the operations supported by the service instance. The operations are grouped under various interfaces. Table 95 describes the details of the operations. Table 95 Interface and Operations Column Name Description The interface and operation name. The interfaces and operations are sorted in ascending alphabetical order. You can expand or collapse the data for each interface. Hits Fault/Success Throughput Response Time (milliseconds) Number of times the operation has been invoked. The number of fault and successful responses. The number of times the operation is invoked per second. The average response time for the selected operation for the selected period. It is categorized into: • • • Message Size (KB)
Minimum The minimum response time for the selected operation. Maximum The maximum response time for the selected operation. Average The average response time for the selected operation.

The average message size for the selected operation for the selected period. • • •
Minimum The minimum message size for the selected operation. Maximum The maximum message size for the selected operation. Average The average message size for the selected operation.

TIBCO ActiveMatrix Administration

Deployment View 283

|

Deployment View
In the Deployment view you view data about service assemblies and service units. You navigate to the Deployment view as follows: • • Click the Deployment link. In Browse mode (see Browse Mode on page 289), click Deployment, select a values from the Environments, Service Assemblies, or Service Units columns, and then click View Service Assembly or View Service Unit.

The Deployment view consists of three subviews: • • • Environment View on page 283 Service Assembly View on page 285 Service Unit View on page 286

Environment View
In the top area, the environment details are displayed:

• • •

The name of the environment. Total number of active service assemblies against the total number of available service assemblies in the selected environment. Total number of active services against the total number of available services in the selected environment.

Service Assemblies After you select the environment and period for monitoring, all the data related to service assemblies in the selected environment is displayed in the Service Assemblies table.

TIBCO ActiveMatrix Administration

284

| Chapter 9

Monitoring Infrastructure and Services

Based on the current status of a selected service assembly, you can start or stop the service assembly by clicking the Start and Stop buttons. The columns in the table specify the following details about the service assemblies. Table 96 describes the details of the service assemblies. Table 96 Service Assemblies Column Name Description The service assembly name. Name is a link that you can click to see the details of the service units bundled in that service assembly. After you click Name, the service assembly details are displayed as described in Service Assembly View on page 285. The status of the service assembly. • • • • • • Deployability
Deployed The service assembly has been deployed but has not been

Status

started.
Deployed with Errors1 The service assembly has been deployed, but

errors need to be resolved before it can be started.
Running The service assembly is running. Running with Errors1 The service assembly is running with errors. Not Deployed The service assembly archive has been uploaded but has

not been deployed or has been deployed and then undeployed.
Not Deployed with Errors1 The service assembly has been undeployed

with errors. The relationship between the deployed service assembly versus the service assembly configuration in the ActiveMatrix Administrator database. Displays one of the following: • •
In Sync Indicates that the deployed service assembly matches the version in the database. Out of Sync Indicates that changes have been made to the service

assembly configuration, and the deployed service assembly does not match the version in the database. Redeployment is necessary. # of Service Units Total number of service units bundled in a service assembly.

1. The status is a link that you can click to display a screen with information about the error. You can drill down to the Service Unit node mapping level to see the details.

TIBCO ActiveMatrix Administration

Deployment View 285

|

Service Assembly View
The Service Assembly view is divided into three areas: • • • Service Assembly Trail on page 285 Service Assembly Details on page 285 Service Units Table on page 286

Service Assembly Trail The service assembly trail is provided in the top area:

Table 97 Metric

Service Assembly Trail Description
envName is the name of environment containing the service assembly.

envName

When you click envName, it opens the Environment subview of the Deployment view. Service Assembly Details Below the service assembly trail, the service assembly name and its status is displayed. You can start and stop the service assembly using the Start or Stop button. Select the View Logs button to open the View Logs dialog where you choose the logs to view for the selected element. See Using the Log Viewer on page 316 for details. The following details about the selected service assembly are also displayed: Table 98 Service Assembly Details Metric Name Description Date Deployed Deployed By Description The name of the service assembly. The description of the service assembly. The date and time when the service assembly was deployed. The user who deployed this service assembly.

TIBCO ActiveMatrix Administration

Description The current status of the service assembly.javase. Table 99 Service Units Metric Name Description The name of the service unit.matrix.286 | Chapter 9 Monitoring Infrastructure and Services Table 98 Service Assembly Details (Cont’d) Metric Status Deployable? Service Units Table The details about the service units bundled in the selected service assembly are displayed in the Service Units table.tibco. You can click a node name to view its details as described in the Node View on page 254. The columns in the table specify the properties of each bundled service unit in the service assembly.container. The data displayed in the table is updated every minute. After you click Name. Name is a link that you can click to see the details about the service unit. The Service Unit view is divided into three areas: • • • Service Unit Trail on page 287 Overview on page 287 Services on page 288 TIBCO ActiveMatrix Administration . For example. The current status of the service unit. Status Version Type Nodes Mapped Service Unit View The details about a service unit are displayed in the Service Unit view.matrix. Whether the service assembly has been configured for deployment.tibco. The version of the service unit.runtime or com.soapbinding.container. the service unit details are displayed as described in Service Unit View on page 286. The name of the container type. com. The names of the nodes on which the service unit is deployed.runtime.

The trail shows how the service was deployed.runtime.container.runtime or com.matrix. Table 101 Service Unit Details Metric Name Type Description The name of the service unit. envName When you click envName.matrix.soapbinding. The name of the container type.tibco.javase.tibco.container. It also displays the Node table which contains the names of the nodes on which the service unit is deployed. Overview The Overview tab displays the following details about the selected service unit. Below the trail the name of the selected service unit is displayed with details provided in the Overview and Services tabs. Logical Displays the logical trail of the service. The version of the service unit. com. it opens the Service Assembly subview of the Deployment view. For example. it opens the Environment subview of the Deployment view. When you click serviceAssemblyName.Deployment View 287 | Service Unit Trail The service unit trail is provided in the top area: Table 100 Metric Service Trail Description envName is the name of environment containing the node. Version TIBCO ActiveMatrix Administration . LOGICAL serviceAssemblyName where serviceAssemblyName is the service assembly containing the service unit.

The amount of JVM memory consumed by the nodes against the total amount of memory available is displayed as a bar graph. and Red = 76 . You can click Name to display the details of that node as described in Node View on page 254. The green. hours. For example. The properties of each service are displayed as columns in the Services table. yellow. and minutes. Total number of services deployed on the selected node. and red values indicate the amount of memory consumed by the machine (Green = 0-50%. Status # of Services # of Containers Uptime CPU Time Fault/Successes JVM Memory Hostname Services The Services tab displays the Services table which lists the names of services in the selected service unit. For information about the Services table. see Table 75 on page 261.288 | Chapter 9 Monitoring Infrastructure and Services Nodes The Nodes table displays the list of nodes on which the service unit is deployed. if the bar becomes red. it signifies that the memory consumption is very high and it may degrade the system performance. The name of the machine on which the node is running. Total number of containers activated on the selected node. The status of the node.100%). Yellow = 51-75%. Table 102 Nodes Column Name Description The name of the node on which the selected service unit is deployed. The amount of time that has elapsed since the service was deployed on the node. You can click the hostname to get more details about the machine as described in Machine View on page 251. The bar signifies the amount of memory in use. The number of faulty and successful responses. Total amount of CPU time consumed by the node since the node was started. TIBCO ActiveMatrix Administration . The columns in the table displays the following data corresponding to each node. The uptime is displayed in terms of days.

After you select an environment. then drill down to monitor the data in different ways. Browse mode is available in all the views and allows you to view physical data or deployment data. data is displayed in the Nodes column. — Deployment Allows you to browse deployment data. To get details about a machine. Based on the selected environment. A window shade appears on your screen. see Service View on page 259. When the default option All Machines is selected. View Service Instances On Environment Details about the services running in the selected environment in the Service view. For details about this view. • If you select Infrastructure. 2. Machines. Based on the selected machine name(s). By default All Machines is selected. and Nodes appear on the window shade. To access data in Browse mode: 1. Click one of the following: — Infrastructure Allows you to browse physical data. Select an environment from the Environments column to drill down the data. For details about this view. data is displayed in the Machines column. columns for Environments.Browse Mode 289 | Browse Mode Using the Browse mode enables you to browse for data. the names of all the nodes existing on all the machines TIBCO ActiveMatrix Administration . select a machine name in the Machines column. a. b. see Environment View on page 248. the following buttons appear: View Environment Details about the selected environment in the Environment View. Click the Browse button on the top right corner of any view.

After you select a node name. To get details about a node. data is displayed in the Service Assemblies column. For details about this view. see Node View on page 254. After you select a machine name.290 | Chapter 9 Monitoring Infrastructure and Services are displayed in the Nodes column. Based on the selected environment. • If you select Deployment. select a node name in the Nodes column. For details about this view. For details about this view. For details about this view. After you select an environment. see Service View on page 259. View Node Details about the selected node in the Node View. see Environment View on page 248. see Machine View on page 251. Select an Environment to drill down the data. View Service Instances On Machine Details about the services running on the selected machine in the Service view. c. the following buttons appear: View Environment Details about the selected environment in the Environment View. columns for Environments. TIBCO ActiveMatrix Administration . see Service View on page 259. View Service Instances On Node Details about the services running on the selected node in the Service view. and Service Units appear on the window shade. see Service View on page 259. the following buttons appear on the window. Service Assemblies. For details about this view. View Services On Environment Details about the services running in the selected environment in the Service view. a. For details about this view. the following buttons appear: View Machine Details about the selected machine in the Environment View.

For details about this view. c. View Services On Service Assembly Details about the services running in the selected service assembly in the Service view. see Service Unit View on page 286. the following buttons appear on the window: View Service Unit Details about the selected node in the Service Unit subview of the Deployment view. After you select a service unit name. To get details about a service assembly. For details about this view. select the name of the service unit in the Service Units column. see Service Assembly View on page 285. Based on the selected service assembly names. To get details about a service unit.Browse Mode 291 | b. the following buttons appear: View Service Assembly Details about the selected service assembly in the Service Assembly subview of the Deployment view. 1. select a service assembly name in the Service Assemblies column. Click Close to close the window shade. For details about this view. TIBCO ActiveMatrix Administration . After you select a service assembly name. For details about this view. see Service View on page 259. data is displayed in the Service Units column. View Services On Service Unit Details about the services running in the selected service unit in the Service view. see Service View on page 259.

292 | Chapter 9 Monitoring Infrastructure and Services TIBCO ActiveMatrix Administration .

page 334 TIBCO ActiveMatrix Administration . page 316 Server Logs. create logging configurations. page 300 Working with Logging Configurations.| 293 Chapter 10 Managing Logging This chapter describes how to create log services. page 308 Using the Log Viewer. Topics • • • • • Overview. use the Log Viewer to query for and display log events and view server logs. page 294 Working with Log Services.

analyzed using the Log Viewer. • Event generator An ActiveMatrix runtime object (node or object running on a node) that generates log events. log service. Log events are sent to destinations by log event generators and log services. or forwarded for further processing. ActiveMatrix supports the following destination types: console. database. file. You specify the destination to which nodes TIBCO ActiveMatrix Administration . Figure 22 ActiveMatrix Logging Environment www Log Viewer UI Legend AM TIBCO ActiveMatrix AMA TIBCO ActiveMatrix Administrator EMS TIBCO Enterprise Message Service LS Log Service Q Log Service Queue AMA Server TIBCO Common Logging Plug-in AM Node 1 Console Log Viewer LS 1 LS 2 LS 3 (Default) Database AM Node 2 Log File Log File Q1 Log Event Processor Q3 (Default) EMS Server Q2 An ActiveMatrix logging environment involves five types of participants: • Event destination A consumer of log events. Events logged to log services can be stored to a database. An ActiveMatrix logging environment is depicted in Figure 22.294 | Chapter 10 Managing Logging Overview ActiveMatrix supports a flexible logging architecture that enables runtime objects to log events to a variety of destinations.

org/tptp/platform/documents/resources/cbe101spec/Co mmonBaseEvent_SituationData_V1. It includes the most common attributes of an event.1. See BW Engine Event Format Attribute Reference on page 332. In Figure 22 on page 294. This section describes: • • • Log File Generation on page 296 Importing Log Files into a Log Service Database on page 296 Viewing Log Files on page 297 TIBCO ActiveMatrix Administration .eclipse. see the CBE specification at http://www. Log Files ActiveMatrix logging architecture works with log files in Common Base Event (CBE) format. • • Log Viewer A browser-based server and client UI for viewing log events stored to or loaded into a database. For information about the CBE file format. Node 2 sends messages to a log file and the default log service. See Working with Log Services on page 300. TIBCO Common Logging Plug-in ActiveMatrix Administrator server plug-in that implements log services and the Log Viewer. Node 1 sends message to the console. The supported event models are: • Base Event Format (BEF) The root of all event formats. • Engine Event Format (EEF) Adds engine-level attributes to the Base Event Format. See Base Event Format Attribute Reference on page 328. See Engine Event Format Attribute Reference on page 332. See Logging Configurations on page 308. See Starting and Stopping the TIBCO Common Logging Plug-in on page 299. Log services store events to files and databases and forward events for further processing.Overview 295 | and ActiveMatrix objects send log events in a logging configuration.0. • Log service A destination that accepts events that conform to specific types of event models. See Using the Log Viewer on page 316.pdf. This is the default model. Event Models An event model specifies the type of attributes associated with a log event. • BW Engine Event Format Adds BusinessWorks-specific engine attributes to the Engine Event Format.

See Logging Configurations on page 308. When an ActiveMatrix logging configuration appender is set to a file. action="add" dataFile="datafile" objectSelector="AdminCluster/LogServiceConfiguration" overwrite="true" merge="true" createIfNotExists="true" force="true" failOnError="true"/> Data File <AdminCluster> <LogServiceConfiguration> <ImportLogFile>PathToLogFile</ImportLogFile> <ImportDestination>LogServiceName</ImportDestination> </LogServiceConfiguration> </AdminCluster> TIBCO ActiveMatrix Administration . See Exporting Log Events to a File on page 325. The LogServiceConfiguration element contains the following subelements: • • ImportLogFile The fully-qualified path to the CBE format log file. The name of a log service whose destination is a ImportDestination database. you must import the log file into a log service whose destination is database... The following sections contain example build file task definition and data file elements. Build File <AMXAdminTask . See Working with Log Services on page 300. When log events displayed in the Log Viewer are exported to a log file. To import a log file you use the ActiveMatrix Administrator command-line interface (see ActiveMatrix Administrator Command-Line Interface on page 77).296 | Chapter 10 Managing Logging Log File Generation Log files are generated in the following circumstances: • • • When the destination of a log service is a file. Importing Log Files into a Log Service Database If you want to view the log events in a log file in the Log Viewer. invoking the add action on a AdminCluster/LogServiceConfiguration object in the build file and specifying a value for the LogServiceConfiguration element in the data file.

For information on how to use the profiling and analysis tools. TIBCO Business Studio If you have installed the design component of ActiveMatrix you can also analyze a log file using the profiling and analysis tools available in TIBCO Business Studio. Start TIBCO Business Studio and create an ActiveMatrix SOA project following the procedures described in Starting TIBCO Business Studio and Creating an ActiveMatrix SOA Project in TIBCO ActiveMatrix Composite Editor User’s Guide. Log Viewer allows more complex and sophisticated query capability than the log viewer available in TIBCO Business Studio. To import the exported log file and display the profiling and analysis perspective: 1.Overview 297 | Viewing Log Files There are two ways to view log files: • • Log Viewer TIBCO Business Studio Log Viewer In order to view a log file in the Log Viewer (see Using the Log Viewer on page 316) you must first import the file into a log service database by following the procedure described in Importing Log Files into a Log Service Database on page 296. see Help > Help Contents > Monitoring and profiling applications. TIBCO ActiveMatrix Administration .

select Common Base Event XML log. Figure 23 Log Navigator and Log Viewer TIBCO ActiveMatrix Administration . The Add Log File dialog will display. a. Select File > Import.. The Import log sets dialog will display. f. A dialog asking whether you want to switch to the Profiling and Logging Perspective will display. The Log Navigator will display. Click Finish.298 | Chapter 10 Managing Logging 2. Click OK twice. The import wizard will display. click Browse to the right of the Common Base Event XML log file path field. d. i. b... In the Filter table. Click Yes. h. Click the Browse button next to the From directory field and navigate to the directory containing the log file you have exported and saved to disk. Click Next. g. j. e. c. In the Log details area. The Log Viewer will display. Select Profiling and Logging > Log File. Expand the Logs node and click the Common Base Event XML log node. Check the checkbox next to the log file. Click Add.

Overview 299

|

Starting and Stopping the TIBCO Common Logging Plug-in
When you restart the TIBCO Common Logging plug-in, all the contained log services are restarted. To start and stop the TIBCO Common Logging Plug-in: 1. Select Configure Enterprise Assets from the Perspective drop-down list. 2. Click the Administrator Cluster link. 3. Click the Plug-ins link. 4. In the Plug-ins table, select TIBCO Common Logging. 5. Click Start or Stop. If you stop the TIBCO Common Logging plug-in, objects that are configured to send log events to a log service (see Logging Configurations on page 308) will continue to generate log events. The log events will accumulate in the TIBCO Enterprise Message Service server and the log services will process those messages the next time the plug-in starts up. To configure the log message queue to handle the messages, see TIBCO Enterprise Message Service User’s Guide.

TIBCO ActiveMatrix Administration

300

| Chapter 10

Managing Logging

Working with Log Services
Log services encapsulate a destination and a set of event models. Log services can: — Collect log events across the entire enterprise — Collect specific class(es) of events, such as audit events, SPM events, or alerts — Collect log events and forward to another process — Import log events from a file — Send events to a database or log file For example, in Figure 22 on page 294: — Log service LS1 receives events on Q1. A queue bridge routes the events to another process. — Log service LS2 receives events on Q2 and stores them in a log file. — Log service LS3 is the default log service. It receives events on Q3 and stores them in a database. It also imports the log file created by Node 2. ActiveMatrix nodes and objects running on the nodes can log only to the log service designated as the default log service. Operations on log services are described in the following sections: • • • • • • Creating a Log Service on page 300 Setting the Default Log Service on page 301 Starting and Stopping a Log Service on page 302 Editing a Log Service on page 302 Deleting a Log Service on page 303 Purging a Log Service Database on page 306

Creating a Log Service
To create a log service: 1. Select Configure Enterprise Assets from the Perspective drop-down list. 2. Click the Administrator Cluster link. 3. Click the Log Services link.

TIBCO ActiveMatrix Administration

Working with Log Services 301

|

4. Click the New button. The Log Service dialog displays. a. Edit the fields according to the descriptions in Table 104 on page 304. For example:

b. Click Save. The dialog is dismissed and the log service is added to the Log Services table. 5. Start the log service following the procedure described in Starting and Stopping a Log Service.

Setting the Default Log Service
ActiveMatrix nodes and objects running on the nodes can log only to the log service designated as the default log service. To set the default log service: 1. Select Configure Enterprise Assets from the Perspective drop-down list. 2. Click the Administrator Cluster link. 3. Click the Log Services link. 4. In the Log Services table, click a log service. 5. Click the Set Default button.

TIBCO ActiveMatrix Administration

302

| Chapter 10

Managing Logging

6. Start the log service following the procedure described in Starting and Stopping a Log Service. After performing these steps, the Log Service table event for the log service will appear similar to:

Starting and Stopping a Log Service
To start or stop a log service: 1. Select Configure Enterprise Assets from the Perspective drop-down list. 2. Click the Administrator Cluster link. 3. Click the Log Services link. 4. In the Log Services table, click a log service. 5. Click the Start or Stop button.

Editing a Log Service
To edit a log service: 1. Select Configure Enterprise Assets from the Perspective drop-down list. 2. Click the Administrator Cluster link. 3. Click the Log Services link. 4. In the Log Services table, click a log service. 5. Click Edit. 6. Edit the fields according to the descriptions in Table 104 on page 304. 7. Click Save. 8. Restart the log service. Whenever you change the JMS Connection setting you must also restart all nodes that satisfy the following conditions: • • The node’s logging configuration appender is set to JMS. The node hosts objects (containers, service assemblies, or service units) whose logging configuration appender is set to JMS.

TIBCO ActiveMatrix Administration

Working with Log Services 303

|

Deleting a Log Service
To delete a log service: 1. Select Configure Enterprise Assets from the Perspective drop-down list. 2. Click the Administrator Cluster link. 3. Click the Log Services link. 4. In the Log Services table, click the log service. 5. Click Stop. 6. Click Delete.

TIBCO ActiveMatrix Administration

304

| Chapter 10

Managing Logging

Log Services Reference Table 103 Log Services Column Name JMS Connection JMS Queue Destination Pending Messages Default? Status Description The name of the log service. The JMS connection from which the log service receives events. The queue on which the log service receives log events from ActiveMatrix objects. The destination to which the log service sends log events. The number of log events in the queue. Indicates whether the log service is the default log service. The status of the log service.

Log Service Reference Table 104 Log Service Reference Field Name JMS Connection Description The name of the log service. The JMS connection on which the service receives log events. A drop-down list containing existing JMS shared resource definitions. Before selecting a connection you must configure a JMS shared resource definition as described in JMS Shared Resource Definition Reference on page 125. The queue on which a log service receives log events from ActiveMatrix objects. By default, all ActiveMatrix objects are configured to send the log events to the default log service’s JMS queue. For configuring a log client to use a queue for a non-default log service, contact TIBCO product support. If the queue doesn't exist on the Enterprise Message Service server, the log service will create the queue.

JMS Queue

TIBCO ActiveMatrix Administration

Working with Log Services 305

|

Table 104 Log Service Reference (Cont’d) Field Destination Description The destination to which the log service sends log events. One of: •
Database Append events to a database. Database drop-down list specifies the

JDBC shared resource definition for the database. Before selecting a connection you must configure a JDBC shared resource definition as described in JDBC Shared Resource Definition Reference on page 121. If you want the JDBC shared resource definition to use a log datastore in the HSQLDB database, you must first configure the datastore as described in Creating a New HSQLDB Datastore on page 15. •
File Append events to a CBE format log file (see Log Files on page 295). The

The File field specifies the file name and optionally the location. If the file location is not specified, the file location defaults to AMX_ADMIN_HOME/data/cluster/server/logs. The file name is appended with a number as described in Max Backup Index. — Max File Size The maximum size of each log file. — Max Backup Index The number of log files you wish to keep. When a log file reaches the maximum size, a new log file is created. After the number of files matches the number specified, the oldest is deleted when a new file is created. Each file is appended with a number. •
No Configuration The messages are not directed to a destination. The log

service acts as a bridge for log events consumed by another process listening on the queue. Models The types of event models handled by the log service. Use the left and right arrows to move models between the Available Models and Selected Models lists.

Command-Line You can also configure a log service from the ActiveMatrix Administrator command-line interface (see ActiveMatrix Administrator Command-Line Interface on page 77). To configure a log service, you invoke the edit action in the build file and specify a value for the LogServiceConfiguration element in the data file. The format of a LogServiceConfiguration varies depending on the type of the destination. All LogServiceConfiguration elements have subelements: LogServiceName, JMSSharedResourceName, QueueName, Destination, and ModelList. The following sections contain example build file task definition and data file elements.

TIBCO ActiveMatrix Administration

306

| Chapter 10

Managing Logging

Build File
<AMXAdminTask ... action="edit" dataFile="datafile" objectSelector="AdminCluster/LogServiceConfiguration" overwrite="true" merge="true" createIfNotExists="true" force="true" failOnError="true"/>

Data File
<AdminCluster> <LogServiceConfiguration> <LogServiceName>test</LogServiceName> <JMSSharedResourceName>test_JMS</JMSSharedResourceName> <QueueName>test_queue</QueueName> <Destination>DB</Destination> <JDBCSharedResourceName>test_jdbc</JDBCSharedResourceName> <ModelList> <ModelName>BaseEventFormat</ModelName> <ModelName>EngineEventFormat</ModelName> </ModelList> </LogServiceConfiguration> </AdminCluster>

Purging a Log Service Database
To purge a log service database of log events you use ActiveMatrix Administrator command-line interface (see ActiveMatrix Administrator Command-Line Interface on page 77) invoking the delete action in the build file and specifying a value for the PurgeCommandParameter element in the data file. The possible values for PurgeCommandParameter are: • • •
all

Delete all log data. Delete all logging data created before the specified date. Delete all log data created before the specified

–d <yyyy-MM-dd>

-t <yyyy-MM-dd hh:mm:ss>

time. Examples
• all -d <2007-08-10> -t <2007-08-10 13:05:00>

• •

TIBCO ActiveMatrix Administration

Working with Log Services 307 | The following sections contain example build file task definition and data file elements. Build File <AMXAdminTask .. action="delete" dataFile="datafile" objectSelector="AdminCluster/LogServiceConfiguration" overwrite="true" merge="true" createIfNotExists="true" force="true" failOnError="true"/> Data File <AdminCluster> <LogServiceConfiguration> <PurgeDestination>log service</PurgeDestination> <PurgeCommandParameter>all</PurgeCommandParameter> </LogServiceConfiguration> </AdminCluster> TIBCO ActiveMatrix Administration ..

You configure how objects log in a logging configuration. Logging Configurations A logging configuration specifies the type of events an ActiveMatrix object logs and the destination for log events. a file. For information on how to generate log events from component implementations. Logging configurations are organized in the parent-child sets shown in Table 105. the child object inherits its parent’s logging configuration. see TIBCO ActiveMatrix Service Grid Component Developer’s Guide and TIBCO ActiveMatrix Service Grid Mediation Design Guide. containers. Table 106 shows how to navigate to the screen where you configure the logging configuration for each type of parent-child set. TIBCO ActiveMatrix Administration . Table 105 Parent-Child Logging Configuration Set Parent Node Service assembly Child Container Service unit A child logging configuration is set in the logging configuration screen of its parent. If you do not specify a logging configuration for a child object. service assemblies.308 | Chapter 10 Managing Logging Working with Logging Configurations ActiveMatrix objects (nodes. Table 106 Object Logging Configuration Screens Parent Node Service assembly Screen Configure an Environment > node Deploy to an Environment > service assembly Figure 24 on page 309 illustrates various types of node and container logging configurations and Figure 25 on page 309 illustrates various types of service assembly and service unit logging configurations. or a log service. and service units) can send log events to the console.

Working with Logging Configurations 309 | Figure 24 Node and Container Logging Configurations Figure 25 Service Assembly and Service Unit Logging Configurations Editing a Logging Configuration To edit a logging configuration: 1. Navigate to a screen containing a logging configuration according to Table 106 on page 308. Edit the parameters of the logging configuration following the descriptions in Table 107 on page 314. 2. 5. Click the Apply button. 4. 4. Click the Edit button above the Logging Configurations table. Click Logging Configurations. Check the checkboxes next to the child objects you want to log. Click the Logging Configurations link. 3. click a configuration. 2. 6. Adding Child Logging Configurations To add child logging configurations: 1. 3. 5. In the Logging Configurations table. where XXX can be either Container or Service Unit. TIBCO ActiveMatrix Administration . Click Save. Click the XXX Logging button above the Logging Configurations table. The Choose XXX to Log dialog appears. Navigate to a screen containing a logging configuration according to Table 106 on page 308.

Adding Logging Configurations to Objects TIBCO ActiveMatrix uses the log4j mechanism to write log events to the desired location.xml is applied to each hierarchy when bootStrap.xml: 1.">. Appenders describe locations to append log events. The same is true for the service assembly-service unit hierarchy.. In the same directory. A node's logging configuration captured inside the base_hierarchy tag is the default for the container unless container has its own configuration via the tag <hierarchy name=". TIBCO ActiveMatrix Administration . specify the parameters of the logging configuration following the procedure described in Editing a Logging Configuration on page 309. A default appender and logger is provided for the default logging behavior.html. bootStrap. 2. locate the logging configuration template file bootStrap. You can add additional loggers to the objects running on a particular node by defining them in the bootStrap. You can also view the log4j documentation at http://logging.org/log4j/1.xml are merged with the logging configurations you specify in the ActiveMatrix Administrator GUI. The loggers specified in bootStrap. Loggers describe the items that you wish to log and the associated appender to use to write the log event. has a base_hierachy tag and system-defined hierarchy tags. There are a variety of third-party references that describe the complete set of log4j functionality. Open the working copy in a text or XML editor. There are two hierarchies relevant to TIBCO ActiveMatrix logging configurations: node-container and service assembly-service unit.xml To edit bootStrap. make a copy of the template file with a different suffix. The log4j mechanism uses appenders and loggers. The ActiveMatrix Administrator GUI allows you to define only one logging configuration (or logger) per object..xml.xml and TIBCO ActiveMatrix configuration is merged at runtime. before modifying bootStrap. a logger is called a logging configuration.xml as your working copy. In the directory AMX_HOME/data/environmentname/nodename/config.apache. In the ActiveMatrix Administrator GUI.2/index.310 | Chapter 10 Managing Logging 6. For each child logging configuration. You can modify the default configuration or add appenders and loggers as needed. The two pairs do not share a hierarchy. The base hierarchy configuration in bootStrap.xml file in AMX_HOME/data/environmentname/nodename/config.

Add an appender. • A logger that specifies a level and references the file appender TIBCO ActiveMatrix Administration .tibco. 4.Working with Logging Configurations 311 | 3.tibco. see: — Example 1 Adding a Logging Configuration with a FIle Appender on page 311 — Example 2 Adding a Logging Configuration with a JMS Appender on page 312 — Example 3 Configuring BEFJMSAppender to Support JNDI and SSL Connections to the Enterprise Message Service Server on page 312.commonlogging.commonlogging. create appender and logger elements of the following form before the closing log4j:configuration tag. For example appenders.example"> <level value ="INFO"/> <appender-ref ref="ExampleFileAppender"/> </logger> .appender. Bold type indicates values that you can modify. <log4j:configuration> </base_hierarchy> The element properties are: • A file appender with the following configurable properties: — File The log file name.tibco..appender.log"/> <param name="MaxFileSize" value="1024KB"/> <param name="MaxBackupIndex" value="4"/> <layoutclass="com. — MaxBackupIndex The number of log files you wish to keep. <base_hierarchy> <log4j:configuration xmlns:log4j="http://jakarta.CommonRollingFileAppender" > <param name="File" value="example. Save the modified configuration file. The configuration is automatically loaded by the node.. <appender name="ExampleFileAppender" class="com..BEF2CBELayout "/> </appender> <logger name="com..org/log4j/"> . — MaxFileSize The maximum size of each log file.apache. Example 1 Adding a Logging Configuration with a FIle Appender To configure logging to a file.

— queueName The JMS queue on which the default log service is listening (see JMS Queue on page 304).tibco.312 | Chapter 10 Managing Logging Example 2 Adding a Logging Configuration with a JMS Appender To define a logging configuration with a JMS appender.apache. create appender and logger elements of the following form before the closing log4j:configuration element. • A logger that specifies a level and references the JMS appender. See JMS Shared Resource Definition Reference on page 125. <log4j:configuration> </base_hierarchy> The element properties are: • A JMS appender with the following configuration properties: — serverURL The Provider URL property of the JMS shared resource selected for the log service.tibco.org/log4j/"> TIBCO ActiveMatrix Administration . — userName The username property of the JMS shared resource definition selected for the log service.. <base_hierarchy> <log4j:configuration xmlns:log4j="http://jakarta. <base_hierarchy> <log4j:configuration xmlns:log4j="http://jakarta.. — retry The number of attempts that should be made to connect to the messaging server represented by the JMS shared resource.org/log4j/"> .appender.example"> <level value ="INFO"/> <appender-ref ref="ExampleJMSAppender"/> </logger> .BEFJMSAppender"> <param name="serverUrl" value="tcp://localhost:7222"/> <param name="retry" value="1"/> <param name="queueName" value="DefaultLogServiceQueue"/> <param name="userName" value="admin"/> </appender> <logger name="com.. Example 3 Configuring BEFJMSAppender to Support JNDI and SSL Connections to the Enterprise Message Service Server To configure BEFJMSAppender to support JNDI and SSL connections to the Enterprise Message Service server. <appender name="ExampleJMSAppender" class="com.commonlogging. add an appender using BEFJMSAppender and a logger referring to this appender into the configuration of the hierarchy.apache. Bold type indicates values that you should configure..

tibco..commonlogging.tibjms. serverUrl Must be declared as tibjmsnaming://address:port instead of tcp://address:port to support JNDI lookup.cert..naming..BEFJMSAppender" name="JMSAppender"> <param name="queueName" value="queue_ssl"/> <param name="userName" value="admin"/> <param name="password" value="#!SDSJWPVWFm51lmPQCkDYug=="/> <param name="type" value="jndi"/> <param name="serverUrl" value="tibjmsnaming://localhost:7243"/> <param name="providerContextFactory" value="com.naming. </log4j:configuration> </base_hierarchy> The password element should be obfuscated (see Creating an Obfuscated Password on page 28) The properties for JNDI support include: • • • type Set as jndi to use JNDI connections to Enterprise Message Service server.naming.commonlogging" additivity="false"> <level value="INFO"/> <appender-ref ref="JMSAppender"/> </logger> .tibco.tibjms.appender.tibco. The properties for SSL support include: • ssl Set as true to support SSL connections. TIBCO ActiveMatrix Administration . If the parameter isn't declared.TibjmsInitialContextFactory"/ > <param name="retry" value="1"/> <param name="ssl" value="true"/> <param name="sslVerifyHostName" value="true"/> <param name="sslExpectedHostName" value="server"/> <param name="sslVerifyHost" value="true"/> <param name="sslTrustedCertificates" value="ENV_HOME/ems/version/bin/certs/server_root.. <appender class="com.TibjmsInitialContextFactory or some other context factories.TibjmsInitialContextFactory as the default value.tibco. providerContextFactory Should be declared as com.tibjms.Working with Logging Configurations 313 | .tibco.pem"/> <param name="sslVendor" value="entrust61"/> <param name="sslPassword" value="#!aMzD1eOJOkGgLfKujKD8NeXN7npa+7rBwqDjfJgUDCk="/> </appender> <logger name="com. JMSAppender will use com.

the expected name is the hostname of the server. If this parameter is not set.conf. It should be obfuscated (see Creating an Obfuscated Password on page 28) and the original password should match the value of ssl_password property set in the file ENV_HOME/ems/version/bin/factories. Object Logging Configuration Reference Table 107 Object Logging Configuration Reference Column objectName Description The object for which you are configuring logging.conf. sslTrustedCertificates The name of certificate keystores containing the issuer certificates of Enterprise Message Service server certificates.conf. • • sslVendor The vendor name of the SSL implementation that the appender uses.314 | Chapter 10 Managing Logging • • sslVerifyHostName Specifies whether the appender should verify the name in the CN field of the Enterprise Message Service server’s certificate. sslExpectedHostName The name the appender expects in the CN field of the Enterprise Message Service server’s certificate. This property is used when sslVerifyHost is set as true and should match the value of the ssl_trusted property set in the file ENV_HOME/ems/version/bin/factories. sslPassword Private key or password for the Enterprise Message Service server’s certificate. This property is used when sslVerifyHostName is set as true and should match the value of the ssl_expected_hostname property set in the file ENV_HOME/ems/version/bin/factories. • • sslVerifyHost Specifies whether the appender should verify the Enterprise Message Service server’s certificate. TIBCO ActiveMatrix Administration .

the File. If the file location is not specified.out or System. The number of log files you wish to keep. Each file is appended with a number. the file location defaults to AMX_HOME/data/environmentname/nodename/logs. Max File Size. The filename is appended with a number as described in Max Backup Index. Displayed if Appender is set to File. Default: Warn. Error Application errors that allow the application to continue running. Only log events appended to the • JMS appender are viewable in the Log Viewer (see Using the Log Viewer on page 316). JMS Append events to a log service. Determines the destination to which log events are appended: • File Append events to a CBE format log file (see Log Files on page 295). If File is the selected. Fatal Very severe errors that will cause the process to abort. After the number of files matches the number specified. Warn Potentially harmful events. Appender Required. • • • • Info Coarse-grained informational messages that highlight the progress of the application. the oldest is deleted when a new file is created. When a log file reaches the maximum size. The maximum size of each log file. and Max Backup Index fields are displayed and required. File The name and optionally the location of the file. Note: You should not use Debug severity with the JMS appender for an extended period of time.err. Max File Size Max Backup Index TIBCO ActiveMatrix Administration .Working with Logging Configurations 315 | Table 107 Object Logging Configuration Reference (Cont’d) Column Severity Description Required. Determines the type of events that to be logged: • • All All events. Default: Console. Displayed if Appender is set to File. a new log file is created. • Console Append events to System. Displayed if Appender is set to File. Debug Fine-grained informational events used for debugging an application. Debug severity generates a large volume of messages which could overwhelm a log service.

For information on log services. TIBCO ActiveMatrix Administration . see Monitoring Infrastructure and Services on page 239. The Log Viewer will display. For further information. see Working with Log Services on page 300. You can also view log events by clicking the View Logs button that appears in various screens in the Monitor & Manage perspective. Select Monitor & Manage from the Perspective drop-down list. Click the Log link in the Monitor & Manage heading. 2. The Log link in the Monitor & Manage heading does not display until you configure at least one log service with a database destination.316 | Chapter 10 Managing Logging Using the Log Viewer The Log Viewer provides extensive facilities for querying ActiveMatrix object logs and customizing the query display. Displaying the Log Viewer To display the Log Viewer: 1.

Using the Log Viewer 317 | 3. TIBCO ActiveMatrix Administration . Working with the Query Builder The query builder is illustrated in Figure 26 on page 318. Log Detail Displays the details of a log event selected in the Log area. Log Displays the log events that satisfy the query parameters. Select the log service whose events you want to view from the Log Service drop-down list. The Log Viewer contains three areas: • • • Query Builder Contains the attributes and attribute values used to filter log events and actions to perform various types of queries.

and deleting queries. Minimizing the query builder provides more real estate for viewing log events. Building. Maximizing and Minimizing the Query Builder The Log Viewer allows you to control the screen real estate used by the query builder. Maximizing the query builder gives you full access to all query builder functions. TIBCO ActiveMatrix Administration . To minimize the query builder. selecting and running queries. Displaying query result hints and running queries. saving. Filter Contains a canvas displaying the active filters. and clearing the filter area. Model Contains an event model selector and a tree of the attributes available for each type of event model. click the Minimize button in the toolbar. See Building Queries on page 321 and Saving and Deleting Queries on page 322. Toolbar Contains actions for displaying the query builder. but you can only view saved queries. See Running Queries on page 322. To maximize the query builder.318 | Chapter 10 Managing Logging Figure 26 Query Builder The query builder is divided into three areas: • • • Toolbar Area The toolbar provides action buttons for: • • • Maximizing and minimizing the query builder. click the Maximize button.

As shown in Figure 27 on page 319. Figure 27 Model Selection Control Setting the Model To set the model. all the filters displayed in the filter area are cleared. Only attributes from the currently selected model are displayed in the attribute tree. When you change the model selection.Using the Log Viewer 319 | Model Area The Log Viewer allows you to query for and view log events based on different log event models. select the model from the Model drop-down list. TIBCO ActiveMatrix Administration . all extensions to the BEF model. including BEF itself are listed in the model selection control. The models in the drop-down list are limited to the models that you selected when you created the log service (see Creating a Log Service on page 300).

The creation time filter is always present in the Filter area. The Log Viewer supports the operators listed in Table 108: Table 108 Filter Operators Operator = Description The attribute value you provide exactly matches (strings) or equals (numbers) the attribute value in the log event. To set a relative creation time. Figure 28 shows the filter area with the creation time filter and two optional filters: ActiveMatrix Logical Component ID and EEF Severity. Filter Operators Some filters allow you to provide an attribute value against which the attribute in log event is compared. For example. See Building Queries on page 321 for information on how to add and remove filters.320 | Chapter 10 Filter Area Managing Logging You create new queries by adding filters to the filter area. To set an absolute creation time. Figure 28 Filter Area BEF Creation Time Filter The BEF Creation Time filter causes log events to be filtered based on when the events were created. click the Absolute radio button and specify From and To date and times using the respective date and time pickers. click the Relative radio button and select a time from the drop-down list. TIBCO ActiveMatrix Administration . the filter in Figure 28 shows the = operator selected for the EEF Severity filter. You can set the creation time filter as a relative or absolute time.

The attribute value you provide is less than or equal to the attribute value in the log event. Double-click the attributes from the model attributes tree. XXXMyContextXXX Working with Queries This section describes the operations you can perform on queries: • • • Building Queries Adding Filters There are four ways to add filters to queries: • • • • Drag and drop attributes from the model to the filter area. matches the following Context ID values: MyContext. For example.Using the Log Viewer 321 | Table 108 Filter Operators (Cont’d) Operator >= <= CONTAINS Description The attribute value you provide is greater than or equal to the attribute value in the log event. This operation appends the selected cell value to the filter area. Click the Clear Filters button. the value MyContext for a Context ID attribute. The attribute value you provide contains a substring of the attribute value in the log event. Available only for EEF Severity and EEF Priority. Select a row and then drag and drop a cell from the Log to the filter area. Right-click a cell in the Log and select Add filter with cell value. Building Queries on page 321 Saving and Deleting Queries on page 322 Running Queries on page 322 Removing Filters There are three ways to remove filters displayed in the filter area: • • Click the icon next to a filter. MyContextXXX. TIBCO ActiveMatrix Administration . Available only for EEF Severity and EEF Priority.

The result count is displayed next to the Hint button. Saving and Deleting Queries Saving a Query To save a query: 1. Check the appropriated checkboxes to make the query visible to other users or to mark it as the default query that is executed every time the Log Viewer is started.322 | Chapter 10 Managing Logging • Change the model selected in the Model drop-down list. a. Since a large number of events would be difficult to retrieve and view. or a modified query. Select Saved Queries > Save Query. a. The BEF Creation Time filter is mandatory. Running Queries The Log Viewer supports a flexible approach to running queries. Click Save. type a name in the Name list. The Delete Query dialog is displayed. You can run newly constructed queries. This action removes all the filters. To overwrite an existing query. the result count hint allows you to decide whether to first narrow a query by specifying more filters before actually running it. Obtaining the Result Count Hint Before running a query you can obtain the approximate number of events that would be returned by the query. Click Delete. queries that are stored in the session. select an query from the Name drop-down list. click the Hint button. The Save Query dialog is displayed. Before running a query you can obtain an estimate of the number of events that would be returned by a query. saved queries. TIBCO ActiveMatrix Administration . b. To create a new query. b. Check the checkboxes next to the queries you want to delete. c. Deleting Saved Queries To delete a saved query: - 1. To obtain the result count hint. Select Saved Queries > Delete Queries. so is not removed by any method.

Select a query from the Saved Queries drop-down list. TIBCO ActiveMatrix Administration . Click the Run Query button. Select a query from the Prev Queries drop-down list. Running an Existing Query All the queries that you perform during a given session are stored in the Prev Queries drop-down list.Using the Log Viewer 323 | Running a Query To run a new query: 1. Running a Saved Query To run a saved query: 1. The queries are identified by the time that you ran the query. Right-click a cell within the row and select: — Add filter with cell value and run query Adds a filter with the cell value to the filter area and runs the query. — Replace filters with cell value and run query Replaces all the filters in the filter area with a filter with the cell value and runs the query. Click the Run Query button. 2. select a row in the Log. 2. 2. all the queries in the Prev Queries list are removed. The filters specified in the query are displayed in the query builder. 2. Click the Run Query button. After running a query. Running a Modified Query To run a modified query: 1. To run an existing query: 1. When you change perspective or restart ActiveMatrix Administrator. Build a new query using the query builder.

Highlighting Log Events with Error Severity You can highlight log events whose severity is Error or Fatal. There are two ways to highlight log events whose severity is Error or Fatal: • Through the display customization dialog. By default. To invoke this dialog and enable highlighting: a. 2. Click Customize Display.324 | Chapter 10 Managing Logging Working with the Log The Log displays log events retrieved by queries. Click Customize Display. Click Save. see Event Formats on page 327. c. TIBCO ActiveMatrix Administration . red font. When log events are highlighted. An example Log is displayed in Figure 29. b. follow the procedure in Customizing the Log Columns on page 324. To customize the columns. For descriptions of the columns. 3. Figure 29 Log Customizing the Log Columns To customize the Log columns: 1. When you change perspective or restart ActiveMatrix Administrator. they are displayed in bold. the display reverts to the default state. Check the Highlight error entries checkbox. all BEF attributes are displayed. Click Save. Check the checkboxes next to the attributes you wish to display.

so choosing one changes the setting in the other method. A file named LogExport. TIBCO ActiveMatrix Administration .xml. To export events. Select a row in the Log. 5. The two methods reflect the same setting. Viewing Log Event Details There are three ways to view details of a specific event in the Log: • • Click the Show Detail button above the Log. or 30 seconds. click the Export button over the log. Paging Through the Log When a large number of events is returned from a query the Log is split into multiple pages. click the arrows in the page control above the Log or type a page number in the text box. uncheck the checkbox or deselect Highlight error entries. Setting the Log Refresh Rate The Log displays the log events in existence when you run a query. To set the rate at which the events in the Log are refreshed. click the Refresh Rate drop-down list and select one of the available rates: Off. Since log events are generated continuously. To turn off highlighting. You can choose to display the file or save it to disk in the file LogExport. Only one page of 20 events is displayed at a time. then right-click and select Show detail of this entry. 20. Exporting Log Events to a File You can export the log events returned from a query to a file in Common Base Event (CBE) format.xml containing the log events is created. The default rate is Off. Only the log events currently displayed in the log viewer are exported. 10.Using the Log Viewer 325 | • Right-click a row in the log and select Highlight error entries. The Log Details area displays the details of the currently selected log event. You can configure the Log to refresh itself to display newly generated log events. To scroll through the pages. after some time has elapsed since the query was run the Log will not show the most recent log events.

Event Detail The Event Detail screens shows the attributes of Base Event Format. Logical Component. Figure 30 Log Detail The log event details are displayed in five screens: Event Detail.eclipse. A spyglass will display with the log details. Figure 30 on page 326 shows an example log detail.pdf. see the CBE specification at http://www. and Additional Attributes. See Table 109 on page 328. Situation The Situation screen shows the details of the situation that caused the log event to be generated. See Logical Component ID on page 328.1. See Physical Component ID on page 328. Physical Component The Physical Component screen shows the details of the components of the physical component ID. the structure of the URN field is constructed from situation details as follows: • Start Situation startSituation:successDisposition:situationQualifier TIBCO ActiveMatrix Administration . Physical Component.org/tptp/platform/documents/resources/cbe101spec/Co mmonBaseEvent_SituationData_V1. In the Situation screen.326 | Chapter 10 Managing Logging • Hover over the Creation Time column in the log event. Logical Component The Logical Component screen shows the details of the components of the logical component ID.0. Situation. For the list of situation types and the contexts in which the situation applies.

See Table 111 on page 332 and Table 112 on page 332. Event Formats This section provides attribute reference information for the event formats supported by the Log Viewer: • • • Base Event Format Attribute Reference on page 328 Engine Event Format Attribute Reference on page 332 BW Engine Event Format Attribute Reference on page 332 TIBCO ActiveMatrix Administration .Using the Log Viewer 327 | • • • • • • • • • • • Additional Attributes Stop Situation stopSituation:successDisposition:situationQualifier Connect Situation connectSituation:successDisposition:situationDisposition Configure Situation configureSituation:successDisposition Request Situation requestSituation:successDisposition:situationQualifier Feature Situation featureSituation:featureDisposition: Dependency Situation dependencySituation:dependencyDisposition Available Situation availableSituation:operationDisposition:availabilityDisposition: processingDisposition Create Situation createSituation:successDisposition Destroy Situation destroySituation:successDisposition Report Situation reportSituation:reportCategory Other Situation otherSituation The Additional Attributes screen shows the attributes of the two models—Engine Event Format and BW Engine Event Format—that extend Base Event Format.

Logical component identifier category. Used to search for log events that don't have a scheme or whose scheme is not supported by the Log Viewer. Contains a scheme field and fields defined by the scheme. A generic physical component identifier. The ActiveMatrix scheme identifier is amx. Subcategories are either generic or identified by a scheme. The ActiveMatrix scheme identifier is amx. The ID is: amx#environment name#machine name#node name#container name. Contains a scheme field and up to eight fields defined by the scheme. An identifier of the context with which the log event is associated. The time the log event was created. An ActiveMatrix logical component identifier. An identifier of the parent of the context with which the log event is associated. Physical component identifier category. Contains a scheme field and up to eight fields defined by the scheme. Contains a scheme field and fields defined by the scheme. an application could specify a Generic Physical Component ID with field1 named cluster_name and field2 called machine_name. A physical address that corresponds to the location of a component. The ID is: amx#service assembly name#service unit name#service name#operation name. For example. An ActiveMatrix physical component identifier. A generic logical component identifier. AMX Physical Component ID Logical Component ID Generic Logical Component ID AMX Logical Component ID TIBCO ActiveMatrix Administration . Used to search for log events that don't have a scheme or whose scheme is not supported by the Log Viewer.328 | Chapter 10 Managing Logging Base Event Format Attribute Reference Table 109 Base Event Format Attribute Reference Attribute Global Instance ID Creation Time Location ID Context ID Parent Context ID Physical Component ID Generic Physical Component ID Description Globally unique identifier of the log event. Subcategories are either generic or identified by a scheme.

The authenticated entity that created the log event. The name and the value are strings composed of any alphanumeric characters. stopping. The name of the destination for the log events. Identifier of the log event message. For the list of situation types and the contexts in which the situation type applies. stopped. or that the stopping process has failed. that it has stopped. Supports searching for log events based on log event contents. Deals with the component shutdown process. initializing. Existing messages include words such as: stop. Table 110 Situation Types (Sheet 1 of 3) Situation Type StartSituation Description Deals with the component startup process. Existing messages include words such as: starting. Security Principal Msg ID Msg Scheme Logger Name Class Loader Hierarchy StopSituation TIBCO ActiveMatrix Administration . For example. The hierarchy of entities when the event was logged. Messages indicate that a component has finished the startup process or that it has aborted the startup process. Messages indicate that a component has begun to stop. The class loader active at the time the event was logged. completed. started. The event message string. and initialized. see Table 110. Table 110 enumerates the situation types that cause components to log events and describes the types of contexts in which the situation applies. The logger name’s type: amx or bw. and exiting.Using the Log Viewer 329 | Table 109 Base Event Format Attribute Reference (Cont’d) Attribute Classifiers Description A set of name-value pairs. you could search for log records with the following classifiers: classifierA: name=PONumber value=0001 classifierB: name=BuyerName value=aBuyer Situation The situation that caused the log event to be generated.

and process ID. Messages indicate that a connection failed. RequestSituation ConfigureSituation AvailableSituation ReportSituation CreateSituation DestroySituation TIBCO ActiveMatrix Administration . and offline.330 | Chapter 10 Managing Logging Table 110 Situation Types (Sheet 2 of 3) Situation Type ConnectSituation Description Deals with aspects of a component’s connection to another component. Existing messages include words such as: port number ID. address ID. Deals with the situations reported from the component. Deals with the situations documenting when a component creates an entity. buffer size is. Existing message include words such as: was created. Deals with components identifying their configuration. Deals with the situations documenting when a component removes or destroys an entity. about to create. connection failed. and failed to get a connection. or that a connection was ended. Messages indicate that a document was destroyed or a file was deleted. such as heartbeat or performance information. Deals with component operational state and availability. about to create. that a connection was created. and now exists. Typically these requests are complex management tasks or transactions that a component undertakes on behalf of a requestor and not the mainline simple requests or transactions. Any changes that a component makes to its configuration or that describe current configuration state should be logged using this category. Messages indicate a document was created or a file was created. and now exists. Deals with the situations that identify the completion status of a request. Messages indicate current CPU utilization and current memory heap size. Provides a context for operations that can be performed on the component by distinguishing if a product is installed. and number of threads is. Existing messages include words such as: ready to take requests. or operational and ready or not ready to process management requests. Existing messages include words such as: utilization value is. Existing messages include words such as: connection reset. operational and ready to process functional requests. online. Existing messages include words such as: configuration synchronization started and backup procedure complete. Existing messages include words such as: was created.

DependencySituation OtherSituation TIBCO ActiveMatrix Administration . Existing messages include words such as: now available.Using the Log Viewer 331 | Table 110 Situation Types (Sheet 3 of 3) Situation Type FeatureSituation Description Deals with the situations that announce that a feature of a component is ready (or not ready) for service requests. Existing messages include words such as: could not find and no such component. currently available. and transport is listening on port 123. Deals with the situations in which components cannot find some component or feature that they require. or that the expected version of a component was not found. Messages indicate a resource was not found. Message indicate services being available and services or features being unavailable. that an application or subsystem that was unavailable. Provides support for product-specific situations other than the predefined categories.

332 | Chapter 10 Managing Logging Engine Event Format Attribute Reference Table 111 Engine Event Format Attribute Reference Attribute Severity Description The perceived severity of the status the event is describing in the context of the application that reports the event: • • • • • Priority Thread ID OS Process ID Class Name Debug Fine-grained informational events used for debugging an application. Info Coarse-grained informational messages that highlight the progress of the application. BW Engine Event Format Attribute Reference Table 112 BW Engine Event Format Attribute Reference Attribute Host Name Engine Name Job ID Process Name Activity Project Name Starter Name Tracking Info Description The name of the machine hosting the BusinessWorks engine. Medium. BusinessWorks engine name. BusinessWorks process name. The name of the class that implements the engine. BusinessWorks job ID. Warn Potentially harmful events. The importance of the event: Low. The thread ID of the component or subcomponent that generated the event. or High. BusinessWorks tracking identifier. BusinessWorks activity name. Fatal Very severe errors that will cause the process to abort. The ID of the operating system process hosting the engine. TIBCO ActiveMatrix Administration . Error Application errors that allow the application to continue running. BusinessWorks process starter name. BusinessWorks project name.

Using the Log Viewer 333 | Table 112 BW Engine Event Format Attribute Reference (Cont’d) Attribute Custom ID Description BusinessWorks custom identifier. TIBCO ActiveMatrix Administration .

Table 113 Server Log Locations Server HSQLDB Management Daemon ActiveMatrix Administrator Log Location AMX_HOME/hsqldb/data/amx.log Audit Log cluster_server_audit.log Server Creation Utility amxadministrator.n All logs are stored in AMX_ADMIN_HOME/data/logs/.log. The log file names for specific components are: • • • • Server cluster_server. The logs are text files and can be viewed in a text editor.log Command-Line admincmdline. The default is no log.log Enterprise Message Service Configured in tibemsd.conf. TIBCO ActiveMatrix Administration .log ENV_HOME/managementdaemon/logs/managementdaemon.334 | Chapter 10 Managing Logging Server Logs Table 113 lists the locations of logs for all servers used in the ActiveMatrix runtime.

page 351 TIBCO ActiveMatrix Administration . page 344 Securing JDBC Connections. page 345 Enabling Secure Connections Between Nodes and ActiveMatrix Components. page 336 Keystores. page 338 Enabling HTTPS for ActiveMatrix Administrator Servers.| 335 Appendix A Securing TIBCO ActiveMatrix Communication Channels This appendix describes how to protect communication channels between TIBCO ActiveMatrix components. page 347 Enabling Secure Connections to Auxiliary Servers. page 342 Enabling SSL for Management Daemon. Topics • • • • • • • Overview.

SSL encrypts the segments of network connections at the Transport Layer end-to-end. This appendix describes the steps to protect TIBCO ActiveMatrix components. The communication occurs by different communication protocols. SSL is a cryptographic protocol that provides security and data integrity for communications over TCP/IP networks. The server sends back its identification in the form of a digital certificate. The client may contact the server that issued the certificate (the trusted CA as above) and confirm that the certificate is authentic before proceeding. the trusted certificate authority (CA). These components communicate with each other and with third-party applications. these communication protocols are not secure. they can be secured by configuring the communication channels to use the Secure Sockets Layer (SSL) protocol. TIBCO ActiveMatrix Administration . However. The certificate usually contains the server name. By default.336 | Appendix A Securing TIBCO ActiveMatrix Communication Channels Overview The TIBCO ActiveMatrix platform is partitioned across many components. 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 components and communication channels are illustrated in Figure 31 on page 337. and the server's public encryption key. An SSL client and server negotiate a stateful connection by using a handshaking procedure. It describes the impact of those steps on other components in the system and details the steps to configure those components to communicate securely with the protected components.

Overview 337 | Figure 31 TIBCO ActiveMatrix Communication Channels AMA AMA Command-Line Graphical UI Interface www Management Daemon JMX/SSL AM Node HTTPS HTTPS HTTPS JMX/SSL HTTPS UDDI Registry AMA Server JMX/SSL JMX/SSL LDAP/SSL JDBC/SSL. DE AM Node Management Daemon JMX/SSL AM Machine 1 HTTPS JDBC/SSL DE Authentication Realm LDAP/SSL Legend AM TIBCO ActiveMatrix createadminserver deleteadminserver Utilties AMA TIBCO ActiveMatrix Administrator DE Data Encryption Database AM Machine 2 SSL TIBCO Enterprise Message Service TIBCO ActiveMatrix Administration .

TIBCO ActiveMatrix Administration .ssl.trustStorePassword. Obtain a server certificate from a CA using the CSR. 3. Import the server certificate into the servercerts keystore: keytool -keystore -file AMX_ADMIN_HOME/data/cluster/server/config/servercerts -import servercert -storepass pramati 4. Generate a key and a CSR in the servercerts keystore. ActiveMatrix Administrator Server Keystores Managing the Server Keystore Installing a Server Certificate The ActiveMatrix Administrator server loads the server certificate from the keystore located at: AMX_ADMIN_HOME/data/cluster/server/config/servercerts By default the servercerts keystore contains a self-signed test certificate. 2. Managing the Trusted Keystore Configuring the Keystore Location and Password To configure the ActiveMatrix Administrator server so that it loads trusted certificates from the trustedcacerts file. add the following property to the ActiveMatrix Administrator server TRA file (see ActiveMatrix Administrator Server on page 352): java.2/bin/ cluster_server.obfuscated=obfuscated password where obfuscated password is the trusted keystore password that has been obfuscated using the command for TIBCO encryption described in Creating an Obfuscated Password on page 28.338 | Appendix A Securing TIBCO ActiveMatrix Communication Channels Keystores This section describes how to configure TIBCO ActiveMatrix component keystores.bat -uploadconfig.property. To use a commercial certificate: 1.javax.net. Restart the ActiveMatrix Administrator server from the command line: AMX_ADMIN_HOME/2.

TIBCO ActiveMatrix Administration . follow the procedure described in Installing a Server Certificate on page 338. type help change_trusted_store_password and follow the instructions. Open the ActiveMatrix Administrator TRA file (see ActiveMatrix Administrator Server on page 352). 6. To change the server keystore password type help change_server_store_password and follow the instructions. ActiveMatrix Node Keystores Installing a Server Certificate ActiveMatrix nodes load the server certificate from the keystore located at: AMX_HOME/data/environment/node/config/servercerts To install a server certificate in an ActiveMatrix node. To change the password of the server or trusted certificate keystore: 1.Keystores 339 | Importing Issuer Certificates To import an issuer certificate into the trustedcacerts keystore execute the command: keytool -keystore AMX_ADMIN_HOME/data/cluster/server/config/trustedcacerts -import -file cacert -storepass pramati Restart the ActiveMatrix Administrator server using the -uploadconfig option from the command line every time a new certificate is imported into the trustedcacerts keystore. 2. Open a terminal window and run AMX_ADMIN_HOME/data/cluster/server/bin/cluster_server. 5. To change the trusted certificate password. Changing Keystore Passwords The default password for the servercerts and trustedcacerts keystores is pramati. 4.args and remove the command line argument -noshell true 3.exe. Locate the string application. At the command prompt j2eeadmin@admin> type secsh.

TIBCO ActiveMatrix Administration . follow the procedures described in Managing the Trusted Keystore on page 338.javax.ssl. Changing Keystore Passwords The default password for the servercerts and trustedcacerts keystores is pramati. The location of ActiveMatrix node TRA files is described in ActiveMatrix Node on page 352. Restart the node using the -uploadconfig option from the command line every time a new certificate is imported into the trustedcacerts keystore. Management Daemon Keystores Management Daemon loads its server certificate from the keystore located at: ENV_HOME/managementdaemon/2. To change keystore passwords for an ActiveMatrix node.keystore The password for this keystore is specified in the configuration.property.340 | Appendix A Securing TIBCO ActiveMatrix Communication Channels Managing the Trusted Keystore To manage the trusted keystore for an ActiveMatrix node.trustStore property to any keystore that contains issuer certificates required by Management Daemon to communicate with other components.net. it is sufficient to do this for one node in that environment. The location of the Management Daemon TRA file is described in Management Daemon on page 352): The usage of the keystores should be consistent in all Management Daemon SSL configurations. follow the procedures described in Managing the Trusted Keystore on page 338.xml file located in the same folder in the following XML element: <password name=keyStorePassword">#!bXxkZESHjW95pKS0JiaM6HB9yRxvWm1Cyarg55U8I rk="</password> Managing the Trusted Keystore To manage the trusted keystore for Management Daemon. In the Management Daemon TRA file set the java.0/config/configuration. If there are multiple nodes in an environment. follow the procedure described in Changing Keystore Passwords on page 339.

net.ssl.Keystores 341 | ActiveMatrix Administrator Command-line Tool Keystores Managing the Trusted Keystore To manage the trusted keystore for the ActiveMatrix Administrator command-line tool to be consistent with other ActiveMatrix components. set the java. follow the procedures described in Managing the Trusted Keystore on page 338. You can use the same keystore as that used by Management Daemon. The location of the ActiveMatrix Administrator command-line tool TRA file is described ActiveMatrix Administrator Command-line Tool on page 352.trustStore property to the same keystore that contains issuer certificates required by ActiveMatrix Administrator command-line tool to communicate with other components.property. In the ActiveMatrix Administrator command-line tool TRA file.javax. TIBCO ActiveMatrix Administration .

3. Enable HTTPS in ActiveMatrix Administrator server clients.bat -uploadconfig.2/bin/ cluster_server. 3. To protect communication between a browser and an ActiveMatrix Administrator server.xml by the property https-port. Setting up ActiveMatrix Administrator Keystores For the details on how to set up the keystores used by ActiveMatrix Administrator server see ActiveMatrix Administrator Server Keystores on page 338. Enabling HTTPS for ActiveMatrix Administrator servers involves three steps: 1. TIBCO ActiveMatrix Administration . 2. 2. 4. Restart the ActiveMatrix Administrator server from the command line: AMX_ADMIN_HOME/2. Open the file AMX_ADMIN_HOME/data/cluster/server/config/web-config. Enable HTTPS in the ActiveMatrix Administrator configuration file.xml. To disable the HTTP port. you enable the HTTPS listener. The HTTPS port used by this server is defined in AMX_ADMIN_HOME/data/cluster/server/config/server-config.342 | Appendix A Securing TIBCO ActiveMatrix Communication Channels Enabling HTTPS for ActiveMatrix Administrator Servers ActiveMatrix Administrator servers are accessed from a browser and from the ActiveMatrix Administrator command-line tool over the HTTP protocol. set the property http-enabled to false. Enabling HTTPS in ActiveMatrix Administrator Server To enable HTTPS in an ActiveMatrix Administrator server: 1. Search for the element ssl-enabled and set the value to true. By default the web server starts an HTTP listener. The ActiveMatrix Administrator server is a web application deployed and run inside a web server. Install an ActiveMatrix Administrator server certificate into the ActiveMatrix Administrator server keystore following the procedure in Installing a Server Certificate on page 339.

Edit the file AMX_HOME/data/environment/node/config/security-config. 2.exe -uploadconfig. Therefore. Change the URL in the Ant build file to use the https protocol instead of http. Enabling HTTPS in ActiveMatrix Nodes To enable HTTPS in ActiveMatrix nodes: 1. 2. and the ActiveMatrix Administrator command-line tool all communicate with ActiveMatrix Administrator server on HTTP as clients. TIBCO ActiveMatrix Administration . Change the value of the two instances of scheme property from http to https.Enabling HTTPS for ActiveMatrix Administrator Servers 343 | Enabling HTTPS in ActiveMatrix Administrator Clients ActiveMatrix nodes. Restart the node from the command line using the following command: AMX_HOME/data/environment/node/environment_node.xml. Enabling HTTPS in ActiveMatrix Administrator Command-line Tool To enable the ActiveMatrix Administrator command-line tool to communicate with ActiveMatrix Administrator server using HTTPS: 1. Import the issuer certificate of the ActiveMatrix Administrator server into the trusted certificate store of the command-line tool following the procedures described in ActiveMatrix Administrator Command-line Tool Keystores on page 341. Management Daemon. If the ActiveMatrix Administrator server is enabled with HTTPS. when ActiveMatrix Administrator server is enabled with HTTPS import the issuer certificate of the ActiveMatrix Administrator server into the trusted certificate store of Management Daemon following the procedures described in Management Daemon Keystores on page 340. For the details on the keystores used by ActiveMatrix nodes see ActiveMatrix Node Keystores on page 339. 4. Enabling HTTPS in Management Daemon Management Daemon communicates with ActiveMatrix Administrator server on HTTPS. 3. Import the issuer certificate of the ActiveMatrix Administrator server into the trusted certificate store of the node. then configure each of these components to access ActiveMatrix Administrator on HTTPS.

Refer to Management Daemon Keystores on page 340 for more details.xml and it uses the keystore located in the same folder to load the server certificate. The configuration can be found in the file ENV_HOME/managementdaemon/2.0/config/configuration.344 | Appendix A Securing TIBCO ActiveMatrix Communication Channels Enabling SSL for Management Daemon By default Management Daemon is configured to use SSL. Additional configuration required for Management Daemon to communicate over SSL with other components is described in the context of those components. TIBCO ActiveMatrix Administration .

Before you can use this driver in any TIBCO ActiveMatrix components you must package it as a feature and deploy it to the environment following the instructions in Post-Installation Procedures in the installation manual for your product. Data Encryption Task A Configure Data Encryption in Oracle Server For the steps to configure data encryption in Oracle server. TIBCO ActiveMatrix packages and supports DataDirect drivers for Oracle. For further information. TIBCO ActiveMatrix supports Oracle native thin drivers but does not ship these drivers.htm Oracle's native thin driver supports all the features available in ASO. DataDirect's JDBC driver does not support native data encryption in Oracle's ASO. For complete details on ASO refer to Oracle's documentation. data encryption. This section describes the steps to configure these security features in various types of components. TIBCO ActiveMatrix supports data encryption and data integrity.com/products/security/documentation/wwhelp/wwhi mpl/js/html/wwhelp. TIBCO ActiveMatrix Administration . and data integrity. This section describes how to configure secure JDBC connections to Oracle databases for the two supported drivers.datadirect. TIBCO ActiveMatrix supports two types of Oracle database drivers: DataDirect and Oracle native thin. The Oracle database server supports a variety of security features under its Advanced Security Option (ASO).Securing JDBC Connections 345 | Securing JDBC Connections TIBCO ActiveMatrix components use JDBC connections to access application and authentication data. refer to the Oracle documentation. This section focuses on three features of ASO: SSL. Oracle Native Thin Driver Oracle native thin drivers support all the features of the ASO. see: http://www. however it supports SSL.

encryption_types_client=Encryption Algorithm For the names of the supported encryption algorithms. ActiveMatrix Administrator server. Add the following properties to the TRA file (see TRA File Locations on page 352) of each component: java.net. refer to the Oracle documentation. Data Integrity Task A Configure Data Integrity in Oracle Server For the steps to configure data integrity in Oracle server. Add the following properties to the TRA file (see TRA File Locations on page 352) of each component: java. java. ActiveMatrix Administrator server.property.crypto_checksum_types_client = Checksum Algorithm For the names of the supported checksum algorithms.property. Management Daemon. Restart the component.oracle.346 | Appendix A Securing TIBCO ActiveMatrix Communication Channels Task B Configure Data Encryption in ActiveMatrix Clients To encrypt the JDBC data from the createadminserver and deleteadminserver utilities.oracle. Task B Configure Data Integrity in ActiveMatrix Clients To ensure the integrity of JDBC data from the createadminserver and deleteadminserver utilities.net. and ActiveMatrix nodes to an Oracle server: 1. and ActiveMatrix nodes to an Oracle server: 1.property oracle.crypto_checksum_client = REQUIRED 2.oracle.property. java. Restart the component after adding the properties. refer to the Oracle documentation.net.net. Management Daemon.encryption_client=REQUIRED 2. TIBCO ActiveMatrix Administration . refer to the Oracle documentation.

Enabling Secure Connections Between Nodes and ActiveMatrix Components 347 | Enabling Secure Connections Between Nodes and ActiveMatrix Components Enabling Secure Communications Between Nodes and Messaging Servers You can secure connections between nodes and messaging servers only when the connection to the messaging server is achieved via JNDI lookup. add the following properties and values prepending each property name with com. Select New > JNDI. select Shared Resource Definitions. The following sections contain the steps to configure messaging server authentication to ActiveMatrix nodes and how to configure ActiveMatrix node client authentication to messaging servers.tibjms. Required. In the ActiveMatrix Administrator UI Configure Enterprise Assets Perspective. 2. Configuring Messaging Server To configure messaging server to use SSL: 1.naming. Table 114 JNDI SSL Application Properties Property security_protocol ssl_vendor ssl_enable_verify_host Value ssl entrust61 true Notes ssl is the only security protocol supported. Specifies whether the client should verify the server’s certificate. Required. Required. TIBCO ActiveMatrix Administration . To secure communication for all the nodes in an environment you configure the messaging server to use SSL and configure SSL in the Enterprise Message Service server for the ActiveMatrix node clients.tibco. In the Application Properties area. entrust61 is the only supported vendor.

p em 1 ssl_expected_hostname server ssl_trace ssl_debug_trace true true 1. 4.cert.tibjms.348 | Appendix A Securing TIBCO ActiveMatrix Communication Channels Table 114 JNDI SSL Application Properties (Cont’d) Property ssl_enable_verify_hostname Value true Notes Set to true if the name on the server's certificate must be verified against the server's hostname. May be specified for SSL tracing. 3. Contains the CAs the client trusts for server verification. If it is set via a substitution variable the JNDI configuration can be used on multiple nodes.ssl_trusted_certs property could be either absolute or set via a substitution variable. Required.tibco.naming. SSL connection will fail. Required only if ssl_enable_verify_hostname is set to true. click the Messaging Bus link. select an environment in the Environments table. Hostname given at the time of creating the certificate. The trusted certificates path specified in the com. The name on the certificate can be verified against another name by specifying the ssl_expected_hostname property. Required only if ssl_enable_verify_host is set to true. ssl_trusted_certs AMX_HOME/2. In the environment details area. In the ActiveMatrix Administrator UI Configure Enterprise Assets Perspective. May be specified for SSL debug tracing. The substitutable value would be replaced with either an environment variable or a system property defined for the JVM. If the server's hostname is different than the name on the certificate.2/server/templa tes/certs/server_root. Required. Required. TIBCO ActiveMatrix Administration .

conf. b. ssl_identity 2. described in the following section. You must also set the ssl_identity property. Restart the Enterprise Message Service server with the command ENV_HOME/ems/version/bin/tibemsd –config tibemsdssl. ActiveMatrix nodes communicate with each other over JMX. set the Client Certificate Password field to the password of the client certificate used by the nodes accessing the server. In addition. If you enable SSL. a. If this property is set. select JNDI.conf: [SSLGenericConnectionFactory] type = generic url = ssl://7243 ssl_vendor = entrust61 ssl_verify_host = enabled ssl_trusted = certs/server_root. click Add.pem ssl_identity = certs/client_identity. TIBCO ActiveMatrix Administration . Configuring SSL in TIBCO Enterprise Message Service Server To configure SSL in TIBCO Enterprise Message Service server: 1.p12 ssl_verify_hostname = enabled ssl_expected_hostname = server is required only if you want ActiveMatrix nodes to authenticate themselves to the messaging server. Enabling Secure Connections Between Nodes and ActiveMatrix Servers ActiveMatrix Administrator servers and Management Daemon communicate with ActiveMatrix nodes using Java Management Extension (JMX) protocol. In the Connection Type drop-down list. in the TIBCO Enterprise Message Service server configuration file. you must do it for all the nodes in an environment.cert. then set the client certificate password when you create the messaging server. Create an SSL connection factory in the TIBCO Enterprise Message Service server by adding the following properties to ENV_HOME/ems/version/bin/factories. In the Messaging Servers table. To protect the communication between the JMX servers you can enable SSL for the JMX server in ActiveMatrix nodes. If you want to enable client authentication for the nodes.Enabling Secure Connections Between Nodes and ActiveMatrix Components 349 | 5.

Refer to ActiveMatrix Node Keystores on page 339 for details on the location of the keystore. You import the certificates into the last node added to the environment as follows: a. Restart the node from the command line using the following command: AMX_HOME/data/environment/node/environment_node. Therefore you must import the issuer certificate of the server certificate used by all nodes in the environment into the trusted certificate keystore of the ActiveMatrix nodes. c. Restart the nodes. ActiveMatrix nodes act as clients to each other over JMX/SSL. Import the server certificate into the node’s server keystore. Enable JMX/SSL in the nodes’ configuration file: a.exe -uploadconfig. Refer to ActiveMatrix Administrator Server Keystores on page 338 and Management Daemon Keystores on page 340 for the details on the location of the keystores. Import the issuer certificate into the trusted keystore. ActiveMatrix Administrator and Management Daemon act as JMX/SSL clients.xml b. Set the value of the ssl-protocol-enabled attribute of the rmi-properties element to true. Therefore you must import the issuer certificate of the server certificate of the ActiveMatrix nodes into the trusted certificate keystores of those components. 2. c.350 | Appendix A Securing TIBCO ActiveMatrix Communication Channels Enabling JMX/SSL for ActiveMatrix Nodes Enabling JMX/SSL involves two steps: 1. TIBCO ActiveMatrix Administration . b. Edit the file: AMX_HOME/data/environment/node/config/server-config. Import certificates into the last node added to the environment and restart the node to upload the changed configuration.

See LDAP Realm on page 39. The ActiveMatrix Administrator server and the ActiveMatrix Administrator server management utilities createadminserver and deleteadminserver can be configured to access the LDAP server over SSL. Refer to ActiveMatrix Administrator Server Keystores on page 338 for the location of the keystore. Refer to Management Daemon Keystores on page 340 for the location of keystore. they act as an SSL client to the LDAP server. Refer to ActiveMatrix Administrator Server Keystores on page 338 for the location of keystore. Enabling Secure Connections to LDAP Servers ActiveMatrix Administrator supports the LDAP authentication realm. 2. the ActiveMatrix Administrator server acts as an SSL client to the UDDI server. Import the issuer certificate of the LDAP server certificate into the createadminserver and deleteadminserver trusted certificate keystore. To enable SSL connections between ActiveMatrix Administrator servers and server management utilities and the LDAP server: 1. See Adding a UDDI Server on page 154. Enabling Secure Connections to UDDI Servers ActiveMatrix Administrator allows you to publish services to UDDI registries. Import the issues certificate of the UDDI Registry server certificate into the ActiveMatrix Administrator trusted certificate keystore.Enabling Secure Connections to Auxiliary Servers 351 | Enabling Secure Connections to Auxiliary Servers This section describes how to enable secure connections to auxiliary servers. Import the issuer certificate of the LDAP server certificate into the ActiveMatrix Administrator trusted certificate keystore. When ActiveMatrix Administrator server and utilities are configured to access the LDAP server over SSL. Specify the HTTPS protocol in the URLs you provide when you add the UDDI server to the enterprise. 3. 2. TIBCO ActiveMatrix Administration . To enable SSL connections between ActiveMatrix Administrator servers and the UDDI server: 1. Check the Use SSL checkbox when you configure the LDAP authentication realm for an ActiveMatrix Administrator cluster. When a UDDI server is configured with HTTPS.

0/bin/managementdaemon.tra AMX_ADMIN_HOME/2.tra TIBCO ActiveMatrix Administration .tra AMX_ADMIN_HOME/2.2/bin/deleteadminserver.tra or AMX_HOME/2. Table 115 lists the locations of the TRA files: Table 115 TRA File Locations Component ActiveMatrix Administrator Server ActiveMatrix Node Management Daemon ActiveMatrix Administrator Command-line Tool createadminserver deleteadminserver TRA File Location AMX_ADMIN_HOME/data/cluster/server/cluster_server.2/server/bin/server.tra AMX_ADMIN_HOME/2.352 | Appendix A Securing TIBCO ActiveMatrix Communication Channels TRA File Locations To enable security features requires you to add properties to ActiveMatrix component TRA files.2/bin/createadminserver.tra AMX_HOME/data/environment/node/environment_node.tra ENV_HOME/managementdaemon/2.2/bin/admincmdline.

TIBCO Enterprise Message Service 4. page 357 TIBCO ActiveMatrix Administration . You enable guaranteed message delivery by configuring the Messaging Bus' quality of service as At Least Once (see Quality of Service on page 174). To prevent message loss when processing In-only MEPs in addition to the configuration steps described in this appendix you must also enable guaranteed message delivery (which by default is disabled) in the Messaging Bus. because messages are persisted in TIBCO Enterprise Message Service server and message delivery is transacted. Guaranteed message delivery incurs overhead.4 is the minimum required version for guaranteed message delivery. Topics • • • Race Condition Between Consumer and Provider.| 353 Appendix B Messaging Scenarios for In-only MEPs This appendix describes mechanisms for handling message loss scenarios in services that use In-only MEPs. page 355 Messages in JMS Container Queue. page 354 Messages In AMX Binding Queue.

amxframework.amxframework.matrix.matrix.tra.messaging. TIBCO ActiveMatrix Administration . so by default retry is not enabled. restart the node. you can configure the retry count and the interval between retries of AMX bindings by specifying the following properties in the node’s TRA file: AMX_HOME/data/environment/node/bin/environment_node.messaging.354 | Appendix B Messaging Scenarios for In-only MEPs Race Condition Between Consumer and Provider During the startup of a service assembly messages received in the interval between the startup of a consumer service unit and its associated provider service unit are sometimes lost and result in a "Provider not up" error. To mitigate message loss.targetendpoint.targetendpoint.retrycount com. After modifying the properties.retryinterv al AMX binding reports "Provider not up" only after retrying a configurable number of times and it is expected that provider will eventually come up during the retries. com. The default value for these properties are 0 and 1 second.tibco.tibco.

tra. puts it on the error queue. which is not desired behavior. for example a node crash. you can configure ActiveMatrix to perform a delayed rollback by specifying the property com.transaction. but the provider is not able to process the message and throws javax. and logs the exception.matrix. delegates the message to provider. To mimic timeout redelivery.timeout (default value 10 seconds) in the node’s TRA file: AMX_HOME/data/environment/node/bin/environment_node.TransactionRolledbackException. is used for error messages. The Enterprise Message Service error queue. To avoid overloading the system with a wrong message. • An AMX binding fetches message from its queue. The error is sent back to the AMX binding. SourceDestinationType (Provider queue type) and DeliveryFailureReason (The reason behind delivery failure). The AMX binding performs a JMS local transaction and commits in case of success and rolls back in case of failure.matrix. the following properties are set for postprocessing: SourceDestinationName (Provider queue name).redelivery. occurs.amxframework. If a node crashes before that.maxcount (default value 30) in the TRA file. Before the provider can process the message some unforeseen event. So it throws any exception other than TransactionRolledbackException. after certain number of failed redelivery attempts the message is put on an error queue. • An AMX binding fetches message from its queue.tibco.tibco. You can configure the redelivery count by specifying the property com.Messages In AMX Binding Queue 355 | Messages In AMX Binding Queue This section describes the behavior of the ActiveMatrix runtime in various scenarios when messages are handled by AMX bindings. Before the error message is put on the error queue.redelivery. A message is committed only upon successful return from provider.messaging. AMX binding checks that the exception is not TransactionRolledbackException and removes the message from original queue. • An AMX binding fetches a message from its queue. the message does not get committed so it will still be on AMX binding queue. On node restart the message will be delivered again.messaging. A rollback causes the message to be delivered again immediately. which is $sys. TIBCO ActiveMatrix Administration . delegates the message to provider but provider is not able to process the message but it also wants message to be discarded.amxframework.undelivered.

A provider should throw an exception for message to be delivered again.356 | Appendix B Messaging Scenarios for In-only MEPs • An AMX binding fetches a message from its queue and delegates the message to the provider. The provider does not process the message but does not throw any error. TIBCO ActiveMatrix Administration . The message will be removed from the queue.

On error the JMS container puts the message on an error queue named SourceQueue. JMS container will send a message to the corresponding error queue. So whatever retry logic is put in JMS container. there is a good chance that Enterprise Message Service server is down and if will remain down for some time.Messages in JMS Container Queue 357 | Messages in JMS Container Queue This section describes the behavior of the ActiveMatrix runtime in various scenarios when messages are handled by JMS bindings. TIBCO ActiveMatrix Administration . In this case the message will not get acknowledged and will remain in the JMS container queue. The node crashes when message is somewhere in memory before being put on provider queue. • The JMS container fetches a message from its queue and delegates the message to AMX binding. The JMS container acknowledges the message only upon successful delivery to AMX binding. When node restarts the message will be processed again. • The JMS container fetches message from its queue. The format of message is wrong and ActiveMatrix reports a "Wrong format format" error. and throws an error back to the JMS container. Spline layer is fixed for reporting the error back to JMS container. The message delivery is guaranteed only in case when the service assembly is deployed with the prefer local provider property set to false. If the JMS binding is not able to put message on a provider queue. AMX binding reports "Provider is not up" only after retrying (see Messages In AMX Binding Queue on page 355). it’s likely that the message will end up in the error queue eventually. On error the JMS container puts the message on the corresponding error queue. The AMX binding reports a "Provider is not up" error.errorqueue. • The JMS container fetches message from its queue. It should be noted that message delivery is not retried in the same manner as the AMX binding. The AMX binding is not able to put message to AMX provider queue. • The JMS container fetches a message from its queue and delegates the message to AMX binding.

358 | Appendix B Messaging Scenarios for In-only MEPs TIBCO ActiveMatrix Administration .

Topics • • • • Overview. page 363 Best Practices. page 362 Interaction. page 360 Usage. page 364 TIBCO ActiveMatrix Administration .| 359 Appendix C Session and Thread Pools This appendix describes the session and thread pools provided by the ActiveMatrix Messaging Bus implementation.

amxframework.property.matrix.messaging.tibco. expected quality of service). Session and thread pool configuration enables fine-grained control over appropriation of such resources as JMS sessions and threads enabling efficient management of message flows depending on certain business criteria (for example. The session is used by the JMS provider to process one or more messages that have arrived. It is important to understand the implication of session and thread pool configuration on the system and their inter-relationships. The node must be restarted to apply the new settings. throughput and scaling.sessioncount This property determines the maximum number of JMS sessions that may be created to handle incoming messages from the server.tra. Thread and Thread Pool The thread pool implemented by ActiveMatrix Messaging Bus is intended to provide flexibility for concurrent message processing. Configuration Properties There are two system properties defined in a node TRA file.amxframework. java. java.com. Like max thread pool property. This property is applicable to every service deployed on that node.com. located in AMX_HOME/data/environment/node/bin/environment_node. TIBCO ActiveMatrix Administration . A session may create and service multiple message producers and consumers. Definitions Session and Session Pool The session represents a JMS session.maxpoolsize This property determines the maximum thread pool size. this property also applies to every service deployed on that node.360 | Appendix C Session and Thread Pools Overview The session and thread pool configuration influences the message processing on a ActiveMatrix node vis-à-vis service providers and consumers. only limited by the available system resources.matrix.messaging. The sessioncount property represents a pool of such session objects. The threads in the thread pool are used to deliver and process the messages for the service. Availability of thread pool to the service has the potential for better performance.tibco.property. You can edit these properties at any time.

The normalization of such a configuration enhances message reliability as it limits the sessions (for message delivery) to same as thread pool size (for message processing).Overview 361 | Session Count and Max Pool Size Normalization must be greater than or equal to sessioncount. If maxpoolsize is less than sessioncount then the sessioncount is made equal to maxpoolsize. Stop The sessions and thread pool are removed when the service is stopped. Additional threads may be created as required until pool size reaches maximum count. TIBCO ActiveMatrix Administration . The thread pool does orderly shutdown by finishing all running threads. maxpoolsize Life Cycle Start The sessions and thread pool are created when the service is started. The thread pool may contain minimum number of threads during its creation.

The session object in turn tries to get a thread from the thread pool thus providing thread of control to invoke message listeners. the JMS provider tries to get a session object from the session pool to deliver the messages. This architecture provides tremendous reliability to the application as messages are safely stored in the Enterprise Message Service server instead of getting backed up in the application process. It avoids any interference or contention for threads by other services running in the node. In case of distributed message processing.362 | Appendix C Usage Session and Thread Pools The session and thread pool are intertwined when it comes to message processing. TIBCO ActiveMatrix Administration . The session pool may serve as throttling mechanism to limit the delivery of messages from the Enterprise Message Service server. The thread pool may serve as sandbox available to every service for concurrent message processing.

It must be noted that if consumer is invoking one way message exchanges (that is. components. The initialization of an ActiveMatrix service results in the creation of sessions and thread pool for the service. But if the consumer is invoking request-response (that is. there is ActiveMatrix service and ActiveMatrix reference. in-out) type of message exchanges then session and thread pool is created to process the responses. If a component is both provider and a consumer then the thread pool is shared for requests (from consumers) and responses (from services it consumes). Each port type is assigned a corresponding ActiveMatrix binding during serialization to a composite file. Table 116 maps the session and thread pool creation vis-à-vis consumer-provider roles and message exchange patterns. Like all other bindings. MEP.tra file so it is coarse grained as it applies to all services deployed in that node. and Session/Thread Pool MEP Role Session Pool Thread Pool N Y Y Y Y N Y Y C N in-only P Y C Y in-out P Y C Y out-only P N C Y out-in P Y TIBCO ActiveMatrix Administration . Table 116 Role (Consumer/Provider).Interaction 363 | Interaction The services. The initialization of an ActiveMatrix reference also results in the creation of sessions and thread pool for the consumer to process the responses. The properties are configured in the node’s . in-only) then no session or thread pool is created. and references in a composite are internally wired through ActiveMatrix bindings.

Since every service has its own session and thread pool the services that have demanding QoS (quality of service) may not be affected by “slower” services deployed on the same node as the “slower” services will have its own session and thread pool to process its messages. For example. Local Invocations It must be noted that the sessioncount property is only applicable for messages exchanged in a distributed environment i.364 | Appendix C Session and Thread Pools Best Practices Session Count and Max Pool Size The maxpoolsize property almost always must be set to higher value than session count. one of the available threads from thread pool is utilized to initiate the provider processing. average response time. The maxpoolsize property is applicable for both local and distributed service invocation. By increasing the sessioncount and maxpoolsize for a service enables the messaging bus to dramatically increase concurrent message delivery and processing. In case of local invocation. It is best to control message flow limit via sessioncount property so that message delivery is blocked until a session is available. a thread from the thread pool) must be always available when the message is received from Enterprise Message Service server for processing. The message delivery and its subsequent processing rely on making one of the available threads from the thread pool as the thread of control.g. This is especially useful in case of services whose average response time is very small or services whose throughput must be high. The rationale being the system resource (that is.e. Service Optimization Service message processing optimization is possible by fine tuning the sessioncount and maxpoolsize properties based on some pre-defined business criteria for e. It is particularly important to set maxpoolsize value higher than the sessioncount if the service is expected to be invoked by both local and remote consumers. TIBCO ActiveMatrix Administration . If thread pool does not have idle threads then the processing will continue on the consumer’s thread. messages delivered by Enterprise Message Service server. if the service is expected to be invoked in equal measure by local and remote consumers then desirable maxpoolsize is two times the value of sessioncount. That results in more reliable message delivery since the messages continue to be persisted in Enterprise Message Service server.

Since the message listener invokes the service synchronously the session is blocked until the service processing is complete.Best Practices 365 | Session Release The JMS session is not released back to the session pool until the message listener is finished. TIBCO ActiveMatrix Administration . This makes message delivery more reliable as newer messages are not delivered until there is session available from the session pool.

366 | Appendix C Session and Thread Pools TIBCO ActiveMatrix Administration .

page 372 TIBCO ActiveMatrix Administration . page 369 ActiveMatrix Administrator Server Configuration. page 368 JVM Configuration.| 367 Appendix D ActiveMatrix Server Performance Tuning This appendix covers various options that can be modified to tune the performance of ActiveMatrix Administrator servers and Management Daemon processes. Topics • • • Overview.

In non-production environments the load is minimal and the memory footprint is expected to be low.368 | Appendix D ActiveMatrix Server Performance Tuning Overview The use cases this appendix addresses are: • • Production environments Non-production environments These two use cases have different requirements. The factors discussed in the following sections can be managed according to the use case. In production environments load can be high and faster response time is more important. These factors can be categorized into two categories: • • JVM Configuration on page 369 ActiveMatrix Administrator Server Configuration on page 372 The factors discussed in the JVM section are applicable to both ActiveMatrix Administrator server and Management Daemon. TIBCO ActiveMatrix Administration . The factors discussed in the ActiveMatrix Administrator Server section are applicable only to the ActiveMatrix Administrator server.

TIBCO ActiveMatrix Administration . Client Intended for executing applications with shorter life span which need fast start-up time or smaller runtime memory footprint. Slower startup time as the compiler tries to proactively perform all possible optimizations. Specially tuned to maximize peak operating speed.tra Using Client and Server Modes The JVM used to run ActiveMatrix Administrator server and Management Daemon can run in one of two modes: client or server. when client mode is used.0/bin/managementdaemon. More code optimizations require a larger footprint. which need the fastest possible operating speed. it requires a smaller memory footprint. the JVM de-allocates unused memory space faster.tra Management Daemon ENV_HOME/managementdaemon/2. This section describes some of these modifications. Table 117 JVM Client and Server Mode Properties Server Application Types Intended for executing long-running server applications. Faster startup time as the compiler does not try to execute complex optimizations. Startup Time Memory Usage In addition. which you perform in the following TRA configuration files: • • ActiveMatrix Administrator AMX_ADMIN_HOME/data/cluster/server/bin/cluster_server. Hence in both cases you can make modifications to the Java Virtual Machine (JVM) configuration to achieve desired performance. This option requires a larger memory footprint. Table 117 shows some of the differences between the modes:.JVM Configuration 369 | JVM Configuration Both ActiveMatrix Administrator server and Management Daemon are Java-based software systems. As the client doesn't perform optimizations proactively.

env.0/bin/server tibco.5.JVM_LIB_PATH=C:/tibco/tibcojre/1.env. This behavior is different from the behavior on Windows. Allocated Memory Size Performance is affected by size of the allocated memory and garbage collection (GC) mechanisms.env. the size of the virtual memory is close to the actual memory allocated.size. the VM throws an OutOfMemory exception.max properties. On Linux.JVM_LIB_PATH=%TIBCO_JVM_LIB_SERVER_ESC% tibco.heap.env.JVM_LIB_PATH and tibco.JVM_LIB_DIR=%TIBCO_JVM_LIB_SERVER_DIR_ESC% tibco. Allocating insufficient amount of memory can lead to OutOfMemory exceptions.JVM_LIB_DIR=C:/tibco/tibcojre/1.max controls the size of the virtual memory allocated. Memory is managed in generations as memory pools holding objects of different ages. To avoid this situation.dll tibco. these settings are specified in the java.env.size. uncomment the server options and comment the client options.dll #tibco.JVM_LIB_PATH=C:/tibco/tibcojre/1.370 | Appendix D ActiveMatrix Server Performance Tuning Both ActiveMatrix Administrator and Management Daemon have client mode enabled by default. The relevant TRA file properties are tibco. When this happens.env. To avoid this situation.heap.5.env. In the following example the -client option is active: #tibco. In the TRA file.env.JVM_LIB_PATH=%TIBCO_JVM_LIB_CLIENT_ESC% #tibco.heap.heap. the memory size specified in java.max can be lowered. On Windows. the value of java. these should be updated to use server mode.size. TIBCO ActiveMatrix Administration . GC occurs in each generation when the memory fills up. In production environments though. Hence for non-production environments running on Linux. make sure that enough memory is allocated to the VM.JVM_LIB_DIR.0/bin/client To switch from client (default) to server mode.0/bin/server/jvm. make sure that enough heap memory is allocated to the VM. These values can be set based on a continuous monitoring of the system.JVM_LIB_DIR=%TIBCO_JVM_LIB_DIR_ESC% If the value of ENV_HOME is C:/tibco. This memory is finite and can be exhausted if too many objects are created.env.5. if VM size is a concern. The JVM allocates memory for these objects at runtime.initial and java.env.JVM_LIB_DIR=C:/tibco/tibcojre/1.5. the properties would be: #tibco. This is the ideal option for environments which require these processes to run with low memory footprint. Heap Size Objects in Java are created using the new operator.size.0/bin/client/jvm.

Currently. the higher bound can be increased. TIBCO ActiveMatrix Administration . More plug-ins mean more space is required for loading the classes. for ActiveMatrix Administrator. In cases where there are requirements to support more resource intensive service engines. This is the part of the memory where classes and long term objects are loaded.JVM Configuration 371 | Permanent Generation Size The TRA file also specifies a PermSize attribute of the java. An OutOfMemory exception generated because of permanent generation size will mention 'PermGen space' in the exception message. the lower bound is set at 64 MB and higher bound at 128 MB.properties property.extended.

static pages. you can set the count to 20 or 30. the ActiveMatrix Administrator server must be started once from the command line with the -uploadconfig parameter.372 | Appendix D ActiveMatrix Server Performance Tuning ActiveMatrix Administrator Server Configuration ActiveMatrix Administrator server runs as an application on a web server.xml. the worker thread count value should be lower. The value can be modified as follows: • For a lower request rate with high process time. The web server spawns worker threads to support the load experienced by applications. The value can be decreased to 1/10th of total number requests received at peak loads collected by statistics. The following sections discuss two settings that control the number of threads that web server creates in the file: AMX_ADMIN_HOME/data/cluster/server/config/webconfig. • Web sites with many hits but less processing time. After updating web-config.xml is: <worker-thread-count>15</worker-thread-count> The default value is 15. If set to a higher value.xml. The entry in web-config. the inactive threads consume memory and flood the listener sockets to check with new requests. many requests are queued before they can be processed. • Acceptor-Thread Count Acceptor-thread count is the number of threads that accept client connections. the count can be 200 or more. and dynamic pages with lower process times should have high worker thread count. All instances in an ActiveMatrix Administrator cluster share the uploaded parameters. The value can be increased depending on the load on the server. For a high load server. This degrades the VM performance.xml is: <acceptor-thread-count>3</acceptor-thread-count> The default value is 3. TIBCO ActiveMatrix Administration . If set to a lower value. The entry in web-config. Number of Web-worker Threads Worker-thread count is the number of requests that can be processed concurrently by the web server. Web sites having high processing time with comparably low hit rate.

| 373 Appendix E Publishing Services to ActiveMatrix Registry Topics • • Enabling Non-Administrator Users to Publish to the ActiveMatrix Registry. page 376 TIBCO ActiveMatrix Administration . page 374 Adding Permission to Publish to a Business.

2. To transfer ownership of a tModel to a non-administrator user. 6. Click Request transfer token. 4. Edit the required fields.374 | Appendix E Publishing Services to ActiveMatrix Registry Enabling Non-Administrator Users to Publish to the ActiveMatrix Registry This section describes how to publish to the ActiveMatrix Registry when you are a non-admin user of the ActiveMatrix Registry. Click Account management. 3. Custom keys can be accepted by the ActiveMatrix Registry either if they are being used by the admin user. start and log in to the ActiveMatrix Registry Administration Console and follow the tasks listed below. 2. Click the PUBLISH tab. Task E Create the Transfer Token 1. or by a non-administrator user who has ownership of a tModel in the UDDI server named uddi:custom-key-generator:keyGenerator. Click Add tModel. In the name field. 3. In the Publish area. Click Create account. 4. Task D Add a tModel 1. 5. 2. For details on the Administration Console see the ActiveMatrix Registry product documentation. Click Create Account 5. Task C Add a Non-Administrator User 1. In the tModel key field. Click Custody transfer. enter uddi:amx:keyGenerator. Log in to the ActiveMatrix Registry Administration Console as the admin user. click Add tModel. TIBCO ActiveMatrix Administration . The UDDI publish functionality in ActiveMatrix Administrator generates custom UDDI keys (of the form uddi:custom-key-generator:custom-key) rather than standard UDDI keys generated by the ActiveMatrix Registry. enter a name for the tModel. Click MANAGE.

Task F Transfer Custody to a Non-Administrator User Log in as non-admin user you created in Task C. 4. on page 374 has been added.Enabling Non-Administrator Users to Publish to the ActiveMatrix Registry 375 | 3. Click Browse and navigate to the file you saved in Task E. on page 374. Click Transfer custody. 3. Click Transfer. Click PUBLISH. Add a Non-Administrator User. Expand the tModels node. 4. on page 374. 6. Notice that the tModel you created in Task D. 5. 1. Click Save to file. 8. Click PUBLISH. Check the checkbox next to the tModel you created in Task D. Click the file and click Open. Log out of the ActiveMatrix Registry Administration Console. on page 374. Add a tModel. 5. 2. Click Request transfer token. Click Custody transfer. Click Load from file. 7. 9. Create the Transfer Token. 6. TIBCO ActiveMatrix Administration . Add a tModel.

Click the edit icon in the system#everyone row. Click the business. TIBCO ActiveMatrix Administration . Click Search. 4. 5. Check the system#everyone checkbox. Click Add selected groups. 10. Select allowed in all the drop-down lists. 7. Click Edit. Click Find business. 12. Click the Permissions tab. 2. 6.376 | Appendix E Publishing Services to ActiveMatrix Registry Adding Permission to Publish to a Business To add permission to a publish to a business to the system#everyone group: 1. 3. Click Save changes. Click the group radio button. 8. 9. 11. Click MANAGE.

306. 94 building queries 321 BW Engine Event Format Attribute reference 332 TIBCO ActiveMatrix Administration . 49. machine. 296.| 377 Index A Acceptor-Thread count 372 access the login page from a browser window 65 access the login page from the Windows Start Menu 65 accessing the Monitor & Manage perspective 244 actions 77 activating and deactivating a container 204 ActiveMatrix Administrator cluster. and environment relationships 104 ActiveMatrix Administrator command-line interface 77 ActiveMatrix Administrator command-line tool keystores 341 ActiveMatrix Administrator configuration 29 ActiveMatrix Administrator graphical interface 65 ActiveMatrix Administrator interfaces overview 64 ActiveMatrix Administrator server configuration 372 ActiveMatrix Administrator server keystores 338 ActiveMatrix Administrator servers 163 ActiveMatrix Administrator setup 4 ActiveMatrix database server 14 ActiveMatrix node keystores 339 Add Search Parameters reference 111 adding a messaging server to an environment 176 adding a UDDI server 154 adding a user to a local XML File realm 31 adding a user to groups 141 adding child logging configurations 309 adding child objects to a parent object 148 adding filters 321 adding logging configurations to objects 310 adding nodes to the Mapped Nodes list 232 adding permission to publish to a business 376 adding superusers 140 additional attributes 327 Administrator Server reference 165 Administrator Servers reference 165 allocated memory size 370 At Least Once 175 At Most Once 176 Authentication realm configuration 31 Authentication realms 5 Auto-bind failure 103 Auto-bind success 103 automatically binding to the ActiveMatrix Administrator server machine 103 B Base Event Format Attribute reference 328 Base Format 82 Batch script 61 BEF Creation Time filter 320 before running the ActiveMatrix Administrator Server creation utility 26 before you begin 7 Best Effort 175 best practices 364 binding a shared resource property to a shared resource 117 binding a shared resource property to a substitution variable 116 binding machines 103.xml 39. 45. 307 build. 105 binding machines to ActiveMatrix Administrator clusters 6 Bound Machine reference 110 Bound Machines table 109 bridged network discovery 101 browse mode 289 build file 85.

306.x 57 creating an ActiveMatrix Administrator server 163 creating an environment 171 creating an external keystore 158 creating an internal keystore 157 creating an obfuscated password 28 creating schema Generated by DB Script Generator 58 creating the ActiveMatrix schema 55 creating the ActiveMatrix schema files 55 creating the ActiveMatrix tables 55 creating the First ActiveMatrix Administrator server 26 customizing HTTP shared resource definitions 11 customizing the log columns 324 D dashboard view 245 data encryption 345 data file 92. 45.xml 39. 50 default connector reference 199 default runtime node configuration 59 definitions 360 . 108. 307 data file schemas 92 data integrity 346 database 143 database actions 77 database authentication superuser 37 database configuration 47 database configuration reference 47 database details 160 database overview 14 database realm 35. 36 database tables 5 datafile. 203 component 267 composite reference 269 composite service 268 configuration properties 360 configure enterprise assets 69 configure environments 70 configure Messaging Bus settings 172 configuring a service assembly 220 configuring LDAP attributes as usernames 42 configuring Messaging Bus 174 configuring Messaging Bus settings 174 configuring messaging server 347 configuring multiple messaging servers in multinode scenarios 198 configuring service assemblies 216 configuring service units 220 configuring SSL in TIBCO Enterprise Message Service server 349 configuring the keystore location and password 338 configuring the runtime 7 configuring the TIBCO Administrator authentication realm 34 connection type JDBC shared resources 121 console mode 28 consumes 268. 340 changing Management Daemon status reporting and polling intervals 19 changing the port values 19 clearing a binding between a shared resource property and a substitution variable 116 command-line 305 command-line interface 64. 296. 269 container reference 204 containers 256 control panel 61 create 91 create a new HSQLDB datastore 16 creating a log service 300 creating a new HSQLDB datastore 15 TIBCO ActiveMatrix Administration creating a node 190 creating a root group 144 creating a shared resource definition 114 creating a subgroup 144 creating a substitution variable 167 creating a TIBCO Administrator authentication realm 33 creating a user 139 creating a user and a database in Sybase 15.378 | Index C change the reporting and polling intervals 21 changing a user password 141 changing keystore passwords 339.

118 deleting a substitution variable 167 deleting a user 140 deleting an ActiveMatrix Administrator server 164 deleting an environment 173 deleting nodes 197 deleting saved queries 322 deleting service assemblies 229 deleting the ActiveMatrix Administrator Windows service 30 deploy to an Environment 70 deploying a plug-in 161 deploying a service assembly 217 deploying and redeploying service assemblies 221 deploying service assemblies 8 deployment details 271 deployment overview 216 deployment view 283 direct connection 179 Direct connection type. 283 environments overview 170 environments reference 170 TIBCO ActiveMatrix Administration . in JMS shared resources 126 disabling machines in an environment 182 disabling UDDI Servers in an environment 184 Discovered Machines reference 112 discovering machines 100 discovery port 18 displaying permissions 148 displaying the log viewer 316 downloading a service assembly archive 228 E edit mode 73 editing a keystore description 158 editing a log service 302 editing a logging configuration 309 editing a node 194 editing a shared resource definition 115 editing a substitution variable value 167 editing a UDDI server 154 editing Administrator Server properties 164 editing an environment 173 editing service assembly configurations 223 editing the reporting and polling intervals 20 enable assets 172 enabling and disabling containers 202 enabling and disabling resource functions 208 enabling and disabling shared resource definitions in an environment 186 enabling and disabling shared resources 207 enabling assets in nodes 189 enabling bound machines in environments 104 enabling HTTPS for ActiveMatrix Administrator servers 342 enabling HTTPS in ActiveMatrix Administrator clients 343 enabling HTTPS in ActiveMatrix Administrator command-line tool 343 enabling HTTPS in ActiveMatrix Administrator server 342 enabling HTTPS in ActiveMatrix nodes 343 enabling HTTPS in Management Daemon 343 enabling JMX/SSL for ActiveMatrix nodes 350 enabling machines 182 enabling machines in an environment 182 enabling monitoring 242 enabling non-administrator users to publish to the ActiveMatrix Registry 374 enabling secure communications between nodes and messaging servers 347 enabling secure connections between nodes and ActiveMatrix components 347 enabling secure connections between nodes and ActiveMatrix servers 349 enabling secure connections to auxiliary servers 351 enabling secure connections to LDAP servers 351 enabling secure connections to UDDI servers 351 enabling SSL for Management Daemon 344 enabling UDDI servers 184 enabling UDDI servers in an environment 184 endpoint chosen for publication 277 engine event format attribute reference 332 environment reference 172 environment view 248.Index 379 | deleting a group or groups 144 deleting a keystore 158 deleting a log service 303 deleting a shared resource definition 117.

380 | Index event detail 326 event formats 327 event models 295 Example 45 example 21. 306 existing ActiveMatrix Administrator server 42 exporting log events to a file 325 external endpoint 268. 270 H header 67 heap size 370 help 75 hierarchical lists 74 highlighting log events with error severity 324 host and port HTTP shared resources 119 how JNDI shared resource definitions are used 114 how to contact TIBCO support xxiii HSQLDB database 15 HTTP server shared resource definition reference 118 HTTP shared resources 118 host and port 119 minimum and maximum threads 120 F failure scenarios 51 faults/successes 264. 282 inter-object relationships 80 introduction 2 inventory polling interval 20 invoking the command-line interface 85 G generate WSDL 264 generating the schema using DB Script Generator 57 graphic interface overview 67 graphical interface 64 group hierarchy 143 groups 143 groups list reference 145 GUI mode 28 TIBCO ActiveMatrix Administration . 94. 339 installing a shared library in a node 197 installing and uninstalling nodes 192 installing and uninstalling shared resources 208 installing nodes 192 installing shared resources 208 integrated service view 262 interaction 363 interface consumed by 267. 270 interface invokes 268. 280 fields 73 filter area 320 filter operators 320 filtering table entries 74 force 91 full format 83 I Identity shared resource definition reference 121 importing issuer certificates 339 importing log files into a log service database 296 importing shared resource definitions 218 infrastructure view 248 inline 116 installing a server certificate 338. 49 Example 1 Adding a Logging Configuration with a FIle Appender 311 Example 2 Adding a Logging Configuration with a JMS Appender 312 Example 3 Configuring BEFJMSAppender to Support JNDI and SSL Connections to the Enterprise Message Service Server 312 examples 83. 269 interfaces & operations 271.

in JDBC shared resources 123 JNDI connection type. 248 machines reference 183 Management Daemon keystores 340 management port 18 managing ActiveMatrix Administrator clusters 160 managing groups in the database authentication realm 144 managing keystores 156 managing machines 100 managing messaging servers 176 managing shared resource definitions 114 managing the server keystore 338 managing the trusted keystore 338. groups.Index 381 | J JDBC connection type. 40 life cycle management 9 life cycle of the ActiveMatrix runtime 7 life cycle 361 limitations 76 local invocations 364 local network discovery 100 local substitution variables reference 212 local XML file 143 local XML File Realm 31 local XML file realm 31 log file generation 296 . 340. 340. and permissions 137 manual recovery 45 mapped nodes reference 233 mapping service units to nodes 231 mapping shared resource profiles to shared resources 220. 341 managing UDDI servers 154 managing users in the database authentication realm 139 managing users. in JMS shared resources 127 JNDI shared resource definition reference 128 JVM configuration 369 log files 295 log in to the ActiveMatrix Administrator graphical interface 66 log service reference 304 log services 161 log services reference 304 log viewer 297 logging configurations 308 logging in to the ActiveMatrix Administrator graphical interface 65 logical component 326 M machine view 251 machines 246. in JDBC shared resources 122 JDBC drivers and database URLs 122 JDBC shared resource definition reference 121 JDBC shared resources 121 connection type 121 JDBC connection type 122 JNDI connection type 123 JMS shared resource definition reference 125 JMS shared resources 125 direct connection type 126 JNDI connection type 127 JNDI connection 181 JNDI connection type. 234 maximizing and minimizing the query builder 318 messages In AMX binding queue 355 messages in JMS container queue 357 messaging server reference 178 metadata 276 Microsoft SQL Server 53 TIBCO ActiveMatrix Administration K keystore reference 159 keystores 338 keystores overview 156 L LDAP 143 LDAP mapping 42 LDAP realm 39.

147. 281 performing actions 74 permanent generation size 371 permission types 147 TIBCO ActiveMatrix Administration . 249. 288 number of web-worker threads 372 Q quality of service 174 O object formats 82 object logging configuration reference 314 objects 78. 151 permissions 145 perspective overview 68 physical component 326 platform server encryption 29 plug-ins 161 plug-ins reference 163 pre-creating ActiveMatrix schema 52 pre-creating database tables by running DDL scripts 26 project element 85 provides 267 provides & consumes 266 publishing a service 273 purging a log service database 306 N new ActiveMatrix Administrator cluster 44 node mapping tab 231 node polling interval 20 node reference 195 node trail 255 node view 254 nodes 247. 148 objectselector 90 obtaining the result count hint 322 operations 281 Oracle 54 Oracle native thin driver 345 overriding a substitution variable value 211 overwrite and merge 91 R race condition between consumer and provider 354 reference format 83 related documentation xviii relationship to TIBCO Administrator™ Software 4 relationship to TIBCO® Management Daemon Software 4 reloading an internal keystore 158 removing a messaging server from an environment 181 removing a UDDI server 155 removing a user from a group 142 removing filters 321 removing nodes from the mapped nodes list 232 removing permissions 151 removing superusers 140 Rendezvous shared resource definition reference 132 Rendezvous shared resources 132 resetting the superuser password 139 resource definition reference 118 reusing archives 217 P paging through the log 325 performance 265. HTTP shared resources 120 model area 319 monitor & manage 71 monitoring configuration 161 monitoring configuration reference 242 multiple objects 150. 252.382 | Index minimum and maximum threads.

Index 383 | reverting a substitution variable back to the global value 211 running a modified query 323 running a query 323 running a saved query 323 running an existing query 323 running queries 322 running the ActiveMatrix Administrator Server creation utility 27. SQL Server. 60 starting and stopping the TIBCO Common Logging Plug-in 299 starting installed nodes 8 starting nodes 193 TIBCO ActiveMatrix Administration . 56 runtime actions 77 S saving a query 322 saving and deleting queries 322 screens 73 search 40 search parameters reference 112 searching for services 260 searching for users 139 securing JDBC connections 345 selecting rows 73 server logs 334 service assemblies 283 service assemblies reference 219 service assembly details 285 service assembly reference 224 service assembly trail 285 service assembly view 285 service deployed to n nodes 272 service details 263 service instance details 279 service instance trail 278 service instance view 278 service instances 257 service metrics 245 service optimization 364 service trail 263 service unit trail 287 service unit view 286 service units 231 service units table 286 service units table reference 231 service view 259 services 288 services reference 238 session and session pool 360 session count and max pool size normalization 361 session count and max pool size 364 session release 365 setting a shared resource definition property 115 setting permissions 148 setting permissions for nodes 197 setting the default log service 301 setting the log refresh rate 325 setting the model 319 setting up ActiveMatrix Administrator keystores 342 setting up HSQLDB 14 setting up Oracle. 151 single_node_data.xml 95 situation 326 sorting table rows 74 specifying the location of the datastore data files 16 SSL server shared resource definition 135 starting a node on machine startup 194 starting and stopping a log service 302 starting and stopping a plug-in 162 starting and stopping ActiveMatrix Administrator servers 164 starting and stopping nodes 193 starting and stopping service assemblies 222 starting and stopping the ActiveMatrix Administrator server 60. 257 HTTP 118 JDBC 121 JMS 125 Rendezvous 132 silent mode 28 single object 149. or Sybase 14 setting up the database server 14 shared resource life cycle 10 shared resource profiles reference 234 shared resource reference 209 shared resources 117.

discovery. then install 8 two-step deployment first configure. then deploy 9 U UDDI publishing 273 UDDI publishing reference 273 UDDI server reference 155 UDDI servers 274 UDDI servers reference 184 UDP listening port 18 UDP. and management ports 18 UI components 148 unbinding machines 109 undeploying a plug-in 162 undeploying service assemblies 229 uninstalling nodes 193 uninstalling shared resources 208 UNIX 62.384 | Index starting service assemblies 222 starting the database server 15 starting the HSQLDB Database server 15 starting the TIBCO Enterprise Message Service server 22 starting TIBCO Administrator and TIBCO Hawk 23 starting TIBCO Management Daemon 17 start 361 status icons 72 status reporting interval 20 stopping nodes 194 stopping service assemblies 222 stop 361 substitution variables 116 substitution variables reference 233 substitution variables tab 233 superuser registration 42 superusers 138 supported objects 78 supported objects and attribute reference 92 sybase 57 syncing or unpublishing a service 273 system messages 75 system metrics 246 top 20 faults 246 top 20 hits 245 topics reference 235 total requests 265. 194 updating a service assembly archive 227 updating object status 75 updating service assemblies 228 updating the authentication realm 44 updating the database configuration 49 uploading a service assembly 218 usage 362 use cases 50 user interface functions 145 users 138 users and groups overview 137 using client and server modes 369 using the log viewer 316 UUID 274 T tables 73 target element 86 taskdef element 85 thread and thread pool 360 TIBCO ActiveMatrix Administrator architecture 2 TIBCO ActiveMatrix Administrator servers and clusters 5 TIBCO Administrator 144 TIBCO Administrator realm 32 TIBCO Administrator™ and TIBCO Hawk® 23 TIBCO Business Studio 297 TIBCO Encryption 28 TIBCO Enterprise Message Service™ Server 22 TIBCO Management Daemon 17 TIBCO_HOME xx toolbar area 318 TIBCO ActiveMatrix Administration . 280 TRA file locations 352 two-step configuration first define.

263 view mode 73 viewing log event details 325 viewing log files 297 views 240 W welcome area 68 working with containers 202 working with environments 173 working with log services 300 working with logging configurations 213.Index 385 | V view logs 251. 236 working with the default connector 199 working with the graphical user interface 72 working with the log 324 working with the query builder 317 working with topics 235 TIBCO ActiveMatrix Administration . 237. 308 working with nodes 188 working with queries 321 working with service assemblies 221 working with service units 231 working with services 238 working with shared resource definitions 186 working with shared resources 207 working with substitution variables 167. 211.

386 | Index TIBCO ActiveMatrix Administration .

Sign up to vote on this title
UsefulNot useful