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

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

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

. . . . . . . . 146 Node Status Life Cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 UDDI Publishing Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Query Builder . . 298 Node and Container Logging Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Shared Resource Status Life Cycle . . . . . . . . . . . . . . . . . 71 Monitor & Manage Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 SQL Server DML User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Local Network Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Services and Service Instances . . . . . . . . . . . . . 76 Parent-Child Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 Model Selection Control . . 70 Deploy to Environment Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 System Messages . . . . . . . 81 Object Association . . . . . . . . . . . . . . . . . . 210 Service Assembly State . . . . . . . . . . . . . . . . . . . 101 Bridged Network Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 SQL Server DDL User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Machines. . . . . . . . . . 319 TIBCO ActiveMatrix Administration . . . . . . . . 67 Enterprise Assets Tab Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| 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 . 54 Welcome Page . . . and Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Configure Enterprise Assets Perspective. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 ActiveMatrix Logging Environment. . . . . . . . . . . . . . . . . . . . . . . . . . 294 Log Navigator and Log Viewer . . . . . . . . . . . . . . . 102 Relationships between ActiveMatrix Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Configure Environments Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Components . . . . . . . . . . . . . . . . 309 Service Assembly and Service Unit Logging Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Container Status Life Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Database Configuration Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 TIBCO ActiveMatrix Administration . . 87 Supported Objects and Their Attribute Reference Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Default Runtime Node . . . . . . . . . . . 111 Search Parameters Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Database Realm Authentication Superuser Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Database Realm Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Superuser Registration Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Search Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Identity Shared Resource Reference . . . . . . . . . . . . . . . . . . . . xxii ActiveMatrix Administrator 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Actions and Objects . . . . . . . . 41 LDAP Mapping Details Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Syntax Typographical Conventions . . . . . . . . . . . . . . . . 109 Bound Machine Reference. . . . . . . . . . . . . 126 JNDI Shared Resource Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Discovered Machines Reference . . . . . . . 38 LDAP Realm Reference . . . . . . 92 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Bound Machines Reference . . . . . . . . . . 78 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Database Drivers and URL Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Local XML File Realm Reference. . . . . . . . . . . 110 Add Search Parameters Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 JDBC Shared Resource Reference . . . . . . . . . . . . . . . . . . . . . . . . . 112 HTTP Server Shared Resource Reference . . . . . . . . . . . . . . . . . . . . . . . . . 123 JMS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 TIBCO Administrator Realm Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Administrator Servers Reference . . . . . . . . . . . . . 233 Substitution Variables . . 185 Nodes Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Default Connector Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Messaging Server Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Service Assembly Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Machines Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Environment Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Plug-ins Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Groups List Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Substitution Variables Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Service Units Table Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 UDDI Server Reference. . . . . . 155 Keystore Reference. . . . . . . . . . . . . . . . . . . . . 130 Rendezvous Shared Resource Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Container Reference . . . . . . . . . . . 132 SSL Server Shared Resource Reference . . . . . 165 Administrator Server Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Shared Resource Profiles Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Node Reference . . . . . . . 159 Database Configuration Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Container Type Attribute Components . . . . . . . . . . . . . . . . . . . 231 Mapped Nodes Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 TIBCO ActiveMatrix Administration . . . . . . . . . . . . . . . . . . . . . . . 234 Topics Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Service Assemblies Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Services Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Shared Resource 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. . . . . . . . . . . . 145 UDDI Server Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Local Substitution Variables Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Actions and Service Assembly Status Changes . . . 165 Environments Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Node Trail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Interface Invokes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Consumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Service Instance Trail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Nodes . . . . 269 Interface Invokes . . . . . . . . . . . . . 274 Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Performance . . . . . 247 Machines . . . 257 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Node Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Interface Consumed By . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Provides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Service Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Endpoint Chosen for Publication . . . . . . . . . . . . . . . 256 Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 UDDI Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Machine Details . . . . . 270 Interfaces and Operations . . . . . . . . . . . . . . . . . . . 267 Interface Consumed By . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Top 20 Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Services Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Service Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Nodes . . . 242 Top 20 Hits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Composite Reference Provides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Composite Service Consumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 Nodes . . . . 278 TIBCO ActiveMatrix Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Log Service Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 Filter Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Parent-Child Logging Configuration Set . 288 Log Services . . . . . . . . . . . . . . . . . and Session/Thread Pool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 Service Unit Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Server Log Locations . . . . . . . . . . . . . . . . . . . . . . MEP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Service Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 BW Engine Event Format Attribute Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Base Event Format Attribute Reference . . . . . . . . . . . . . . . 284 Service Assembly Trail . . . . 347 TRA File Locations . . . . . . . . . . . . . . . . . . . . . . . 308 Object Logging Configuration Reference . . . . . . 308 Object Logging Configuration Screens . . . . . . . . . . . . . . . . . . . . . . . . 329 Engine Event Format Attribute Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Situation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .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 . . . . . . . . . . . . . . . . . . . . . 282 Service Assemblies . . . 285 Service Assembly Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 Role (Consumer/Provider). . . . . . . . . . . . . . . . 369 TIBCO ActiveMatrix Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 JVM Client and Server Mode Properties . . . . . . . . 281 Interface and Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 JNDI SSL Application Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 Service Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

deploying. page xviii Typographical Conventions. ActiveMatrix provides a scalable and extensible platform for developing.| xvii Preface The TIBCO ActiveMatrix® Administrator is a web-based user interface and server for configuring ActiveMatrix® environments and deploying ActiveMatrix services into them. page xxiii TIBCO ActiveMatrix Administration . Topics • • • Related Documentation. page xx How to Contact TIBCO Support. 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.xviii Related Documentation | Related Documentation This section lists documentation resources you may find useful. TIBCO ActiveMatrix Administration: Read this manual to learn how to manage the ActiveMatrix runtime and deploy and manage ActiveMatrix services. • • 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 . 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.

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

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

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

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

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

xxiv How to Contact TIBCO Support | TIBCO ActiveMatrix Administration .

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. page 2 Life Cycle of the ActiveMatrix Runtime. page 7 Shared Resource Life Cycle. Topics • • • Introduction.

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

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. • ActiveMatrix Database Stores ActiveMatrix administration data. ActiveMatrix Administrator servers within a cluster share a database and authentication realm and are kept synchronized. • ActiveMatrix Administrator Cluster Groups one or more ActiveMatrix Administrator servers. responds to requests from the ActiveMatrix Administrator graphical and command-line UIs. interacts with the authentication realm to authenticate users. TIBCO ActiveMatrix Administration . and interacts withTIBCO Management Daemon to manage nodes.

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

before you create the first ActiveMatrix TIBCO ActiveMatrix Administration . You select and configure the authentication realm when creating the first server in a cluster. The cluster is created when the first server is created. or you may require more. Access to ActiveMatrix Administrator UI functions and ActiveMatrix runtimes is controlled based on permissions granted to specific users and groups. ActiveMatrix Administrator servers are members of a cluster. different sets of ActiveMatrix environments and their nodes. This is particularly recommended in production systems. The database tables are used only for servers in that cluster and not for any other cluster. Thus. 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. Within each cluster. You select and configure database tables when creating the first server in a cluster. You may need only one cluster. 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. To enable flexibility in administering multiple ActiveMatrix runtimes. ActiveMatrix Administrator automatically keeps the servers within a cluster synchronized. that is. Therefore. 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. one for each geographic region of a global enterprise. Database Tables ActiveMatrix Administrator data is stored in a database. Each cluster administers a different set of environments. Authentication Realms An authentication realm describes the method of storing information about ActiveMatrix Administrator users and groups. not just for that particular server. for example.Introduction 5 | TIBCO ActiveMatrix Administrator Servers and Clusters The first step in setting upActiveMatrix Administrator is to create one or more ActiveMatrix Administrator servers. an environment can be administered by only one cluster. This keeps different sets of environments administered by different clusters separate from each other for better management. Conversely.

Using the ActiveMatrix Administrator graphical or command-line interfaces. for each bound machine. you bind machines to the ActiveMatrix Administrator cluster. or LDAP. Finally. Database. TIBCO Administrator. TIBCO ActiveMatrix Administration .6 | Chapter 1 TIBCO ActiveMatrix Administrator Overview Administrator server in a cluster. 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. decide which kind of authentication realm you will use: Local XML File. you specify which environments can use the ActiveMatrix installations it manages. You choose machines that to use for the ActiveMatrix runtime administered by this cluster.

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

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

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

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

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

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

ActiveMatrix administrators may be responsible for all these servers. In a production environment. page 17 TIBCO Enterprise Message Service™ Server. page 22 TIBCO Administrator™ and TIBCO Hawk®. page 14 TIBCO Management Daemon. other administrators may be responsible for some or all the servers. however. In a development or test setting. Topics • • • • ActiveMatrix Database Server.| 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 23 TIBCO ActiveMatrix Administration .

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

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

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

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

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

if you know that software inventory on machines do not change very often.txt file in a text editor. so you would increase the value of the nodePollingInterval and daemonStatusInterval properties. you can set a large interval for inventory polling to save some processing power on the machines. Open the ENV_HOME/managementdaemon/2.0/bin/managementscript. TIBCO ActiveMatrix Administration . In a mission-critical production environment. you may not need very up-to-date status on nodes and daemons. on the other hand. you may want to get status updates every 15 seconds instead of the default of 30 seconds. in nonproduction environments. 2. — Discovery Port set discoveryJMXAddress service:jmx:jmxmp://Hostname:Port — Management Port set managementJMXAddress service:jmx:jmxmp://Hostname:Port 3. 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.0/managementscript. 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. Run ENV_HOME/managementdaemon/2. On the other hand.TIBCO Management Daemon 19 | The JMX management port is set in the managementAddress element. For example. Changing Management Daemon Status Reporting and Polling Intervals You can change Management Daemon status reporting and polling intervals to suit your requirements.

it updates the databases of all ActiveMatrix Administrator servers bound to the machine on which it is running.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. They report directly to the ActiveMatrix Administrator servers. edit the nodePollingInterval property. The server databases therefore hold accurate information about containers and installed software. 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. 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. Intervals of less than 20 seconds can result in performance degradation. you can set this interval to a very large number. They also report status of the Management Daemon process itself. edit the inventoryPollingInterval property. Set the interval according to how critical it is to know the current node state. TIBCO ActiveMatrix Administration . Node Polling Interval A Management Daemon process uses JMX to ping all nodes on the machine and report if they are alive. To configure the interval between each ping. 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. To configure this polling interval. In a production system where software is not installed or uninstalled very often. It is strongly recommended that you set the interval to 20 seconds or more.

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

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

exe TIBCO ActiveMatrix Administration . see TIBCO Administrator product documentation. To start TIBCO Administrator server at the command line. You can also start the TIBCO Administrator and TIBCO Hawk services using the command-line versions of these services. To start the services on Windows. Starting TIBCO Administrator and TIBCO Hawk When you use a TIBCO Administrator authentication realm. Find the entry for TIBCO Administrator version (domain) and click Start. This section describes how to start the TIBCO Administrator server and TIBCO Hawk agent. To stop a service. 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. run the following: TIBCO_HOME/tra/domain/domainName/bin/hawkagent_domainName.exe To start TIBCO Hawk agent at the command line. For complete information on configuring TIBCO Administrator.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. close its window. the TIBCO Administrator server and TIBCO Hawk agent for your domain must be running. run the following: TIBCO_HOME/administrator/domain/domainName/bin/tibcoadmin_domainName. you can use the Services dialog. Repeat for the TIBCO Hawk Agent (domain) entry. Useful information is written to a command window when you start the services in this way.

24 | Chapter 2 Infrastructure Servers TIBCO ActiveMatrix Administration .

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

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. See Pre-creating ActiveMatrix Schema on page 52 for details. Securing TIBCO ActiveMatrix Communication Channels. Database. see Appendix A. see Authentication Realm Configuration on page 31. 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. Start the ActiveMatrix Administrator cluster database server. 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. TIBCO Administrator. on page 335.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. If you plan to use the packaged HSQLDB database. The ActiveMatrix Administrator server creation utility cannot connect to the database if a firewall is running on your machine. 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. it can be started as part of the installation process. Doing so allows you to run ActiveMatrix with a database user that has minimum privileges. The same database server can be used for the authentication realm. The firewall must be disabled before running the utility. or LDAP. • TIBCO ActiveMatrix Administration . For information on authentication realms. All ActiveMatrix Administrator servers in the same cluster must use the same authentication realm. if you are using a database for authentication. • Choose an authentication realm: Local XML File. You can also configure a different database server for use with the cluster. For detailed instructions on how to configure the components.

If you do not run the utility during installation.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. you must: • • Create the administration server cluster table with an upper case name AMXADM_CLUSTER_NAME_IN_CAPS. or silent mode. console mode. and then run ActiveMatrix Administrator server creation utility using a database account with no permissions to create database tables. 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. TIBCO ActiveMatrix Administration . 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. Create the database schema for all tables the same. If you are using Sybase as the TIBCO ActiveMatrix Administrator database you can run the utility only in silent mode. you can run the utility in interactive mode. 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.

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

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

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

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. All servers in the same ActiveMatrix Administrator cluster use the same authentication realm. xml in a text editor. 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. TIBCO ActiveMatrix Administration . 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. one username—root—and a password of your choice is stored in a local file. A password of your choice.Authentication Realm Configuration 31 | Authentication Realm Configuration When you configure the first ActiveMatrix Administrator server in a cluster you specify an authentication realm. Open the file AMX_ADMIN_HOME/data/clustername/servername/config/system-security. see Updating the Authentication Realm on page 44. For a description of how to change the authentication realm after you have created the first server in a cluster. You must use the same password for all servers in a cluster. Local XML File Realm is an appropriate choice for demonstration installations and other non-production uses.

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

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

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

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

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

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

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

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

the ActiveMatrix Administrator server can communicate with an LDAP Server over SSL. Default: cn=Directory Manager Password Use SSL LDAP server password. A strong authentication mechanism requires you to possess a Public Key Certificate (PKC).ldap. if in Search Filter for Users. or None. Default: Unchecked. For addition configuration requirements. When checked. Default: ldap_server:port Username (Bind DN) The superuser's distinguished name or superuser's name to be used to connect to the server. If the Base DN to search users and Base DN to search groups is the same (that is. users and groups are under the same tree node in the LDAP hierarchy). For example. Default: com.sun. Strong. see Enabling Secure Connections to LDAP Servers on page 351. you enter: (&(objectClass=person)(uid=%U)) TIBCO ActiveMatrix Administration .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.LdapCtxFactory LDAP Server URL The URL used to log in to the LDAP server.jndi. This enables secure communication between the LDAP server and ActiveMatrix Administrator. One of Simple. Default: Simple Search In the search screen you provide user and group configuration details. 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.

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

The Key name for the group in the user distinguished name. 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. 2. TIBCO ActiveMatrix Administration .42 | Chapter 3 ActiveMatrix Administrator Server LDAP Mapping Select one field and provide the mapping details. Description The values for User and Subgroup attribute keys. Existing ActiveMatrix Administrator Server To apply this configuration change to an existing ActiveMatrix Administrator server: 1. Table 11 Superuser Registration Reference Field Username Password Description Name of an existing user in the LDAP server to register as an ActiveMatrix superuser.xml. Stop the ActiveMatrix Administrator server. The attribute keys refer to the keys with which Users and Subgroups are associated with the Group. Configuring LDAP Attributes as Usernames When using an LDAP authentication realm by default the value of the CN attribute is used as the username. See Superusers on page 138. Password for the user. The value for the Group attribute key with which the parent group is associated with this user/subgroup. 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. Edit the file: AMX_ADMIN_HOME/data/cluster/server/config/security-config.

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

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

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

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

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

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

build. Run the command-line.xml files with the appropriate action and new database configuration. Default: 30 seconds. A partial success is also supported when some Management Daemon processes are unavailable.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. 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).xml and datafile. 2.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 . The Management Daemon processes on all machines must be bound and available. Create build. 3. Restart all ActiveMatrix nodes and ActiveMatrix Administrator servers. You can update the following parameters: • • • • Example The following sections contain example build and data files for updating the database configuration. To update database configuration properties: 1.

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

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

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

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

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

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

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

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

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

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

The authentication realm must be available.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. If you accept the default values when you create the server. Starting and Stopping the ActiveMatrix Administrator Server This section describes procedures for starting up an ActiveMatrix Administrator server on all platforms. The following preconditions must be satisfied before starting the server: • • • The TIBCO Management Daemon process must be running. page 17. TIBCO ActiveMatrix Administration . After you have started the first ActiveMatrix Administrator server in a cluster. See Starting TIBCO Management Daemon. 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. In the following sections. review the log (see Server Logs on page 334) for error conditions. First-time startup is slower than subsequent startups because the ActiveMatrix Administrator web application is deployed. See Starting the Database Server on page 15. cluster is amx and server is admin. The database server must be running. 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 the name of the cluster and server is the name of the server you provide when you create the server.) If you cannot log in to the user interface. After you have performed one of the startup procedures described in the following sections.

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

2/bin/cluster_server.sh & You can log out of the terminal and the ActiveMatrix Administrator server continues to run.62 | Chapter 3 ActiveMatrix Administrator Server autodeploy] 7:07:48 AMAuto Deploy poll interval : [5 seconds] 7:07:48 AM. 7:07:49 AM. TIBCO ActiveMatrix Administration .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.sh To start the ActiveMatrix Administrator server in background mode. Skipping JSP pre-compilation for [default_defaultApp] 7:07:48 AM.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. UNIX To start the ActiveMatrix Administrator server in console mode. run the following in a terminal window: nohup AMX_ADMIN_HOME/2. You see one such line for each Management Daemon process bound to the ActiveMatrix Administrator server.Configuration files backup [ OK ] 7:07:50 AM.Started Application : default_defaultApp 7:07:48 AM.JSP precompilation is off.Deploying Application : default_defaultApp 7:07:48 AM.C:\tibco SUN version 1.C:\tibco Thread[pool-1-thread-1] registered with management daemon: MDMachine. run the following in a terminal window: AMX_ADMIN_HOME/2.Application [default_defaultApp] successfully Deployed 7:07:48 AM.2/bin/cluster_server.Server [admin] started [ OK ] Thread[pool-1-thread-2] registered with management daemon: .

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

In particular. This means that other TIBCO products can add functionality. You use the command-line interface for repetitive application of standard actions on large numbers of objects. and deploying and undeploying objects. editing. The product-specific functionality is added to ActiveMatrix Administrator by uploading and deploying a plug-in containing new features. In the ActiveMatrix Administrator graphical interface functionality is divided into perspectives. see ActiveMatrix Administrator Command-Line Interface on page 77. Extending the perspectives TIBCO ActiveMatrix Administrator is extensible.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. TIBCO ActiveMatrix Administration . such as new perspectives and new screens within the standard perspectives. and deleting ActiveMatrix objects and actions such as starting and stopping. installing and uninstalling. 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. A perspective is a set of controls used to carry out a category of administration tasks. 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. Command-Line Interface The command-line interface provides access to most ActiveMatrix Administrator functions. The remaining chapters in this book provide extensive task and reference information on each perspective. Graphical Interface The graphical interface provides access to all ActiveMatrix Administrator functionality through a browser. see Plug-ins on page 161. For information on how to create the required files and run the interface. it supports adding. For information on managing plug-ins. to ActiveMatrix Administrator.

Select All Programs > TIBCO > TIBCO ActiveMatrix > Administrator Servers. (The domain name may not be required by your browser.com.Domain. The port is the HTTP port you specified for the server when you created it. Logging in to the ActiveMatrix Administrator Graphical Interface To Access the Login Page From a Browser Window In your browser’s address field. 2.com:HTTPPort/amxadministrator For example: http://amxserver.acme. You see a list of ActiveMatrix Administrator servers installed on the local machine.) To Access the Login Page From the Windows Start Menu 1. Click the name of a server: TIBCO ActiveMatrix Administration . 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.:8120/amxadministrator.

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. enter a valid username and password: The ActiveMatrix Administrator session timeout is set to 15 minutes.

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

the Configure Enterprise Assets tab bar has the tabs shown in Figure 5. a menu listing available environments appears just below the perspective. 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. This list is permissions-based. The remaining chapters in this manual provide complete task and reference information for each perspective. For example. Clicking any other perspective simply opens the perspective. If you click either the Configure an Environment or Deploy to an Environment perspectives. 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.68 | Chapter 4 ActiveMatrix Administrator Interfaces Welcome Area The welcome area contains a list of perspectives (see Perspective Overview on page 68). To return to the Welcome page you must log out and log in again. TIBCO ActiveMatrix Administration . a description of the perspective displays to the right of the perspective list. 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. You select a perspective by clicking a perspective in the list. When you mouse over a perspective. Clicking one of the environments opens the selected environment in the parent perspective. you leave the Welcome page. The remaining sections in this chapter provide an overview of each perspective and the standard behaviors of the graphical interface.

on page 169. Configuring Enterprise Assets. 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. see Chapter 5. messaging. database. software. on page 99 and Chapter 6. TIBCO ActiveMatrix Administration . Defining Environments. and other enterprise assets that are made available to an ActiveMatrix runtime. an IT administrator manages the hardware. registry. Specifically.ActiveMatrix Administrator Graphical Interface 69 | Configure Enterprise Assets In the Configure Enterprise Assets perspective . 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. Figure 6 Configure Enterprise Assets Perspective For details on the functionality offered in this perspective.

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

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

on page 239. The following icons are used across all perspectives: Defined. Monitoring Infrastructure and Services.72 | Chapter 4 ActiveMatrix Administrator Interfaces Figure 9 Monitor & Manage Perspective For details on the functionality offered in this perspective. Not Deployed Installed. Active Installed/Stopped. 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 . Deployed Uninstalled Running. 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.

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

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

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

Similarly. containers. Since log entries are generated continuously. The data on every screen in this perspective is updated every minute. but the status has not yet been updated in ActiveMatrix Administrator to show the node as Running. but instead is shown as Installed/Stopped. after some time has elapsed since running the query the Log Viewer does not show the most recent log entries. but instead is shown as Running. TIBCO ActiveMatrix Administration . and shared resources shown in ActiveMatrix Administrator may not reflect the actual status of the objects.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. A node is stopped. In some cases the status of nodes. You can configure the Log to periodically refresh itself. A node is running. • • The Log Viewer displays the log entries in existence when you run a query. the Monitoring & Management perspective displays the state of the system when you retrieve information from the monitoring service. For example: • A node is running. 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.

such as between an environment and a shared resource definition. how to specify the objects.ActiveMatrix Administrator Command-Line Interface 77 | ActiveMatrix Administrator Command-Line Interface This section describes the actions you can perform with the command-line interface. • • • • • • 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 . such as between an environment and a shared resource definition. the entire tree rooted at the object is deleted starting at the leaves. you must stop and uninstall all nodes contained in the environment. When you delete an object. Delete Deletes an existing object from the ActiveMatrix Administrator database. the objects on which you can perform actions. After that you can delete the environment and all of its children. • Add Adds an object to the ActiveMatrix Administrator database. Delete is also used to delete associations between objects. Runtime Actions These actions modify the state of the objects contained in the ActiveMatrix runtime. In particular. Actions This section describes the actions that can be performed 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. Add is also used to add associations between objects. Database Actions These actions modify the objects contained in the ActiveMatrix Administrator database. • • Edit Edits an object in the ActiveMatrix Administrator database.

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

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 .

such as that between an Environment and a Node. User and Group are marked with an asterisk because they are children of Enterprise only when using the Database authentication realm. In a parent-child relationship. In the figure. Relationships can be either parent-child or associative. The possible parent-child relationships are illustrated in Figure 11 on page 81. one of the objects is a child of the other object and is contained in that parent object. Logger Shared Resource Service Assembly Service Assembly Shared Resource Service Assembly TIBCO ActiveMatrix Administration . parents are on the left and children are on the right.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. each object has relationships with other objects.

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. The possible associative relationships are illustrated in Figure 12. one object is not a child of the other. In the figure. TIBCO ActiveMatrix Administration . the referencing objects are on the left and the referenced objects are on the right. such as that between an Environment and a Machine. In such situations you must create a reference from one object to the other object. but the two objects need to work with each other.

ActiveMatrix Administrator provides XSD schemas for the data files that capture all of the ID attributes. The cardinality of the relationship between Node and Environment is many-to-one. 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 . and associative relationships of ActiveMatrix objects (see Data File Schemas on page 92). the cardinality of the relationship between Environment and MessagingBus is one-to-one. For example. full. the cardinality of the relationship a set of objects can have with each other can be one-to-one. In these schemas. The attributes of that object (both ID and descriptive) are attributes of the XML element.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. parent-child relationships. many-to-one. and reference. Object Formats You specify the objects on which the command-line interface operates in an XML data file. description attributes. every ActiveMatrix object can be specified in three types of formats: base. 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. and the relationships this object has with other objects are subelements of the XML element. The cardinality of the relationship between SharedResourceDefinition and Environment is many-to-many. Every object is described in an XML element.

productInstallDirectory.matrix.container. and so on Description attribute: description TIBCO ActiveMatrix Administration .tibco.javase.runtime" version="2.0. DefaultConnector Data file element: <Node name="node1"> <Container type="com.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"/> </Node> An node in full format has: • • • ID attribute: name Other required attributes: hostname.

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

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

/> </target> or <target name="target"> <AMXAdminConfigTask ..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 ....

Install. Activate. TIBCO ActiveMatrix Administration . The method used is determined by the action. — For the most part. • • Unless objectSelector is specified. Deactivate. Edit. The order in which the action is applied to the objects is either breadth first or depth first. Uninstall: depth first • Some actions are not performed against certain object formats (see Object Formats on page 82). 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. Start. Objects not in this format are skipped. Undeploy: breadth first — Delete. The action is case insensitive. Deploy. — Add. Add and Edit are applied only to objects specified in full format. the action is applied to every object in the data file. See Creating an Obfuscated Password on page 28. Stop.xml or in response to a prompt.AMXAdminTask 87 | AMXAdminTask Ant Task Description Syntax Specifies the administrative action and objects on which the action is performed. <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.

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.tra. The timeout controls how long the tool waits for the actions to complete. To set the default timeout time.property. set the property java. start.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.node. adminURL createIfNotExists URL Boolean Yes No The URL of the ActiveMatrix Administrator server.runtime. If an object is to be edited but doesn’t yet exist and this flag is true. dataFile failOnError String Boolean Yes No The absolute path to the XML file containing the object data. The default timeout time is configurable. The default timeout is 180 seconds. Default: false.action. stop). See Data File on page 92. TIBCO ActiveMatrix Administration .timeout in the file AMX_ADMIN_HOME/bin/admin_cmdline. uninstall. Relevant to the Edit action. then the object is added. Causes the Ant task to fail when an unrecoverable error is reported.

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

or created from scratch. There are two ways in which an object can be overwritten: it can be merged. 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. For information on the XPath language. • objectSelector="//Node" Process all nodes.org/TR/xpath. TIBCO ActiveMatrix Administration . If this attribute is not specified: • • All of the objects in the data file are processed. The strategy used is determined by the merge flag.w3. This section contains examples of the AMXAdminTask task attributes and describes the effect of using the attributes. then the existing object is overwritten. The heuristic used to determine the order in which the objects are processed depends on the action attribute. overwrite Boolean No Relevant to the Add action. See Creating an Obfuscated Password on page 28. see http://www. If an object to be added already exists and this flag is true.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. Default: false. username Examples String Yes The name of the ActiveMatrix user executing the task. The set of objects is defined by an XPath expression. objectSelector • objectSelector="//*" Process all objects. • objectSelector=”/Environment[@name=’env1’]/Node[@name=’node1’]" Process node1 in environment env1.

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

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

Topics Reference on page 235. Users on page 138. Substitution Variables on page 116. Permissions on page 145. Services Reference on page 238. Configuring Messaging Bus on page 174. Groups on page 143. Local Substitution Variables Reference on page 212. TIBCO ActiveMatrix Administration . Object Logging Configuration Reference on page 314. Messaging Server Reference on page 178. Managing Keystores on page 156. UDDI Server Reference on page 155. Service Units Table Reference on page 231. Bound Machine Reference on page 110. Service Assembly Reference on page 224. Shared Resource Reference on page 209. Shared Resource Profiles Reference on page 234. Substitution Variables Tab on page 233. Node Reference on page 195. Resource Definition Reference on page 118.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.

a shared resource definition.94 | Chapter 4 Examples ActiveMatrix Administrator Interfaces This section contains an example build. Machine. For more examples.xml add a machine.xml file..xml file and an example data file. <project default="main"> <property file="login. The machine is enabled for the environment. referenced in the build.AMXAdm inTask"/> . build. Messaging Bus"> <AMXAdminTask adminURL="http://localhost:8120/amxadministrator" username="${username}" password="${password}" action="add" dataFile="node_data.2/samples/.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.xml. single_node_data. and a shared resource.xml The tasks in build. see AMX_ADMIN_HOME/2.command.tibco. the containers are enabled for the node.line.properties"/> <taskdef name="AMXAdminTask" classname="com. <target name="init" description="Set up Environment.matrix.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 .. a node and its containers. an environment.administration. and the shared resource definition is enabled for the environment and the shared resource is enabled for the node.ant.

xml" objectSelector="SharedResourceDefinition | Environment/SharedResourceDefinition | Environment/Node/SharedResource" overwrite="true" merge="true" createIfNotExists="true" force="true"/> </target> </project> single_node_data. a node named node1. a messaging server named ms1. a shared resource definition named conn8989.. <amxdata_base:Enterprise . and a shared resource in the node.xml This data file creates an environment named env1.. <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. containers in the node.

96 | Chapter 4 ActiveMatrix Administrator Interfaces name="node1" description="desc" hostName="sbodoff-lt" tibcoHome="C:/tibco" productInstallDirectory="C:/tibco/amx/2.2" productVersion="2.0.tibco.runtime" version="2.runtime" version="2.0"> </Container> <Container type="com.javase.tibco.2.soapbinding.matrix.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 .0.0" managementPort="4432"> <Container type="com.matrix.

The name of the ActiveMatrix Administrator server.xml or in response to a prompt. — For the most part. Deploy. <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. Objects not in this format are skipped. 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. Deactivate.AMXAdminConfigTask 97 | AMXAdminConfigTask Ant Task Description Syntax Specifies the administrative action and objects on which the action is performed. Stop. Start. The action is case insensitive. 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. Activate. See Creating an Obfuscated Password on page 28. Install. Add and Edit are applied only to objects specified in full format. Edit. — Add. Uninstall: depth first • Some actions are not performed against certain object formats (see Object Formats on page 82). • • Unless objectSelector is specified. TIBCO ActiveMatrix Administration . Undeploy: breadth first — Delete. The method used is determined by the action. the action is applied to every object in the data file.

For information on the XPath language.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 http://www. Causes the Ant task to fail when an unrecoverable error is reported. See Data File on page 92. The set of objects is defined by an XPath expression. TIBCO ActiveMatrix Administration . See Creating an Obfuscated Password on page 28. Specifies the set of objects to be processed. The heuristic used to determine the order in which the objects are processed depends on the action attribute. username String Yes The name of the ActiveMatrix user executing the task.w3.org/TR/xpath. If this attribute is not specified: • • All of the objects in the data file are processed. Note: The password is not masked when you type it into the command line. password Obfuscated String Yes The obfuscated password of the ActiveMatrix user executing the task.

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

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

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. First you connect to one machine using the JMX discovery URL and initiate the discovery process. That machine discovers other machines on its subnet using broadcast or multicast. TIBCO ActiveMatrix Administration . Bridged Network Discovery Figure 14 on page 102 illustrates how you discover machines running on a different subnet from ActiveMatrix Administrator.

When you execute the search. you enter the hostname and JMX port for the Management Daemon you plan to use. TIBCO ActiveMatrix Administration . 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. and Management Ports on page 18. Discovery. on a different subnet XM /JM MX P J MD12 on M12 MD14 on M14 MD16 on M16 M16 broadcasts to subnet. Broa 2 dcas t/Mu lticas t In addition to the multicast or broadcast and UDP information. see UDP. ActiveMatrix Administrator establishes the JMX connection with the Management Daemon process (step 1 in Figure 14). Then the Management Daemon process issues the broadcast or multicast discovery requests (step 2 in Figure 14). returns all discovered management JMX URLs to AS1.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.

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

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

Machines. Click the Machines link.Managing Machines 105 | Figure 15 Relationships between ActiveMatrix Administrator. TIBCO ActiveMatrix Administration . Click Add. Select Configure Enterprise Assets from the Perspective drop-down list. 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. Add search parameters 4. Click Discover. The Add Search Parameters dialog displays. The Discover Machines dialog is displayed. 2. 3.

select one of the following: — Local Searches for machines on the same subnet as the ActiveMatrix Administrator cluster. Enter a name and description to help you identify the purpose of this search parameter.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. In the Subnet field. — Bridged Searches for machines on a different subnet from the ActiveMatrix TIBCO ActiveMatrix Administration . b. a.

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

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

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

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

The name displays in the Search Parameters table. Multicast or Broadcast Address UDP Port The address used for multicast or broadcast search.107. Displays only when Bridged is selected for Subnet. The UDP port used for search. Discovery. Displays only when Bridged is selected for Subnet. JMX Port TIBCO ActiveMatrix Administration .100. 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. If you want to specify the network interface. The hostname of a machine on the subnet. Default: 1965. Default: 9999. Default: 239.106. The name of the network interface used by the Management Daemon process. The machine must be running a Management Daemon process. and Management Ports on page 18. The discovery JMX port of the machine whose hostname you specified in Hostname field.xml file of the Management Daemon.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. See Bridged Network Discovery on page 101. A short description of the search parameter. use the value in the Management Daemon configuration file described in UDP. this field can be left blank. Local Search for machines in the same subnet as the one where ActiveMatrix Administrator is running. The JMX port is declared in the configuration. In most cases.

Installation directory for ActiveMatrix software installed on the machine. The UDP port used for search.107. Default: 239. Used for bridged subnet search only. A number of seconds after which the search stops if no machines are found using the search parameter or parameters.100.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. Default: 1965. The JMX URL used to communicate node status and send life cycle commands such as Stop and Start to the node. Discovery URL A JMX URL used to connect to the Management Daemon process on the machine to discover the management URL.106. (On UNIX there can be more than one TIBCO home on a machine). The address used for multicast or broadcast search. Timeout Discovered Machines Reference Table 22 Discovered Machines Reference Column Name TIBCO Home Management URL Description The name of the machine. TIBCO ActiveMatrix Administration .

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

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

4. 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. 6. Editing a Shared Resource Definition Once a shared resource definition has been created you cannot edit its name.Managing Shared Resource Definitions 115 | 4. Click Save. Select Configure Enterprise Assets from the Perspective drop-down list. 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 . 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. To edit a shared resource definition: 1. Click Save. See Installing and Uninstalling Shared Resources on page 208 for details. 2. 5. Uninstall and reinstall the shared resources on all nodes that use this shared resource definition. 6. Test the connection to a JDBC or JMS resource by clicking the Test Connection button. In the right panel. Click an existing shared resource definition. 3. click Edit and then modify properties as described in Setting a Shared Resource Definition Property on page 115. In the right panel. Click Shared Resource Definitions. but other fields are editable.

Click the icon to the right of the field.116 | Chapter 5 Configuring Enterprise Assets • Inline Shared Resources on page 117 To set the value of a shared resource property. The icon displays to the left of the field. The icon to the left of the field disappears. the port number must be between 1 and 65536. Click the row of a substitution variable to apply to the target property and close the dialog box. 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. The value of a substitution variable is validated when it is applied. Some reasons bind properties to variables are described in Customizing HTTP Shared Resource Definitions on page 11. For example. 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. 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). A dialog box containing substitution variables of the appropriate type displays. a. If invalid. TIBCO ActiveMatrix Administration . click the field and type a new value. To bind a shared resource configuration property to a substitution variable: 1. an error citing the limitations on the value of the property displays. type the value in the property field. The value %%subvarname%%:subvarvalue displays in the field.

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

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

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. This property can be bound to a substitution variable. This property can be bound to a substitution variable. TIBCO ActiveMatrix Administration . so enable this field only when required. the default value localhost specifies the current machine. Port Port number on which to listen for incoming HTTP requests. after accepting a connection. Maximum size allowed for HTTP POST data. If there is more than one network card on the machine. This property can be bound to a substitution variable. Only one HTTP server can be started on each port. For machines that have only one network card. not the ActiveMatrix Administrator server. Default: localhost. Therefore make certain that all HTTP connection resources that use the same host name specify different port numbers. Default: 0. This can adversely affect throughput. Default: 80. For machines that have more than one network card. the request is redirected to the port you specify here. 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. If the HTTP connection supports non-SSL requests. Connection Timeout The number of milliseconds the connector waits. this field specifies the host name of the card that will be used to accept incoming HTTP requests. Note that localhost signifies the host on which the ActiveMatrix node is running. Default: 8081. and you specify localhost in this field. for the specific URI the request is sending to be presented. Unit is milliseconds. and a request received requires SSL transport. all network cards on the machine will listen for incoming HTTP requests on the specified port.

an additional connection timeout period is used while a SOAP message is being executed. Default: No. This property can be bound to a substitution variable.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 ActiveMatrix node returns a ConnectionRefused exception to the client. Use SSL? Check to require SSL encrypted communication with the connection. The field label is a link to the resource. TIBCO ActiveMatrix Administration . If checked. the additional timeout period is not used. Default: false (not checked). Default: 10. Default: 75. Disable Upload Timeout? If not checked. This property can be bound to a substitution variable. SSL Configuration Name The SSL server shared resource to use for the connection. 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. The HTTP server creates the number of threads specified by this parameter when it starts up. When a client sends a request that cannot be processed because no threads are available. Maximum Threads The maximum number of threads available for incoming HTTP requests.

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

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

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

To use the native drivers.driver=com. Shut down the ActiveMatrix Administrator server and ActiveMatrix nodes.107.jdbc. 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. If you are using the Oracle thin driver.10 6)(PORT=2484)))(CONNECT_DATA=(SERVICE_NA ME=orcl)(SERVER=dedicated))) jdbc.jdbc .SQLServerDriver URL Template jdbc:sqlserver://<host>:<port#>. Enabling SSL Connections SSL connections are supported only with Oracle databases.sybase.microsoft.driver.171. type the driver class and URL into the fields and follow the Custom Drivers instructions in JDBC Driver on page 122.Encr yptionMethod=SSL jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=( ADDRESS=(PROTOCOL=TCP)(HOST=10.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.sqlserver.jd bc3. 3. Import the issuer certificate of the Oracle server’s certificate into the ActiveMatrix Administrator server and the ActiveMatrix node trusted certificate stores.7.jdbc.171.7. 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.oracle.databaseName=<dat abaseName> SSL Sybase1 1.106) (PORT=1521)))(CONNECT_DATA=(SERVICE_NAME =orcl)(SERVER=dedicated))) jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=( ADDRESS=(PROTOCOL=TCPS)(HOST=10.SybDriver jdbc.SID=SID. OracleDriver jdbc:tibcosoftwareinc:oracle://<hostname>:<port#>. To enable SSL connections on ActiveMatrix Administrator server and ActiveMatrix nodes: 1.107. 2.jdbc.OracleDri ver tibcosoftwareinc.SI D=<db_instancename> jdbc:tibcosoftwareinc:oracle://host:port.url_template=jdbc:sybase:Tds:<host>:<port#>/ <databaseName> Driver com. TIBCO ActiveMatrix Administration .

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

When the scheduler receives a task. Distributed Queue CMQ Name Worker Weight The name of the distributed queue. Message Timeout The time limit (in seconds) for certified message delivery. Default: No. This name is in the same format as Rendezvous subject names. Relay Agent Name of the relay agent to use. Relative worker weights assist the scheduler in assigning tasks. Default: No. it assigns the task to the available worker with the greatest worker weight.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. Specifies whether to keep the ledger file synchronous with the current messages. If not specified. the certified message ledger is kept in memory only. 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. not to BusinessWorks process engines). Relay agents are useful when clients are disconnected from the network from time to time. it receives inbound messages immediately. This name is in the same format as Rendezvous subject names. Default: 1 Description Sync Ledger File? Require Old Messages? TIBCO ActiveMatrix Administration . When a client is connected. These messages will be resent. The weight of the worker (this pertains to the worker processing queue requests. The name and location of the persistent ledger file that tracks certified messages. Default: 0. Specifies whether to require the retention of messages for which delivery has not been confirmed.

TIBCO ActiveMatrix Administration . The value must be positive. Cooperating distributed queue transports use relative scheduler weight values to elect one transport as the scheduler. The value must be positive. the scheduler reassigns the message to another worker. All members with the same name must specify the same value for this parameter.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 worker cannot accept additional tasks until it completes one or more of them. Acceptable values range from 1 to 65535. Default: 0.3.1. Scheduler Heartbeat The scheduler sends heartbeat messages at this interval (in seconds). members with higher scheduler weight take precedence. Default: 0. Scheduler Activation When the heartbeat signal from the scheduler has been silent for this interval (in seconds). All members with the same name must specify the same value for this parameter. Default: 10 Worker Complete Time The amount of time the scheduler waits for a worker process to complete. Scheduler Weight Weight represents the ability of this member to fulfill the role of scheduler. the member with the greatest scheduler weight takes its place as the new scheduler. Default: 0. Task capacity is the maximum number of tasks that a worker can accept. relative to other members with the same name. Default: 1. If the worker process does not complete in the specified period. When the number of accepted tasks reaches this maximum.

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. Table 31 SSL Server Shared Resource Reference Field Name Description The name of the resource. SSL server shared resources are used by HTTPS server shared resources. 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.Managing Shared Resource Definitions 135 | SSL Server Shared Resource Definition An SSL server shared resource describes an SSL server. Default: SSL Server Shared Resource Definition. The location of the certificate store. The greater the number of bits in the key (cipher strength). Names are case sensitive. The name must be unique across all shared resource definitions in all environments administered by the same ActiveMatrix Administrator cluster. the Trusted Certificate Authorities fields will be displayed. Shared Resource Type Description Identity Cipher Strength SSL Server. The password for the certificate store. An identity shared resource of type public key identity. When checked. TIBCO ActiveMatrix Administration . The location must be the URL of an object accessible over the network. the more possible key combinations and the longer it would take to break the encryption.

136 | Chapter 5 Configuring Enterprise Assets TIBCO ActiveMatrix Administration .

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

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

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

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

Type a wildcard expression in the text box. a. and Permissions 141 | 4. a. The groups are added to the Groups list in the right panel. A superuser can change the password of any user. 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. Click the Reset Password button.Managing Users. There are two ways to add a user to groups: through the Users area and through the Groups area. Click the Search button. Click the Users button. c. Click Remove in the row of the user to remove. Select a user in the Users list. The Reset Password dialog is displayed and requires you to enter the new password and confirm the password. Select groups from the Add Group list and drag them to the right panel. TIBCO ActiveMatrix Administration . d. 2. Click the Superusers button. 4. The Change Password dialog is displayed and requires you to enter the old and new passwords and confirm the new password. The Add Groups dialog displays. Select the Configure Enterprise Assets perspective: a. b. b. Users area • To add a user to groups through the Users area: 1. Click the Add Groups button in the Groups area. Select Configure Enterprise Assets from the Perspective drop-down list. 3. 5. Click Save. 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. Select the user in the Users list. 2. 1. Click the Users & Groups link. Click the Users link. Dismiss the dialog. Click the Users & Groups link. Groups. The Superusers dialog displays. 6.

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

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

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

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

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

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. uninstall. Groups. — Perform runtime actions such as start. activate. edit. deactivate. — Add items to a parent object. stop. and so on have permissions that grant access of a particular type to a single user or a group of users. shared resource definitions. See Adding Child Objects to a Parent Object on page 148. 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. and Permissions 147 | Objects Objects such as nodes. and owner. deploy. install. 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 .Managing Users. Each type provides different capabilities: • • View Allows you to browse objects in a list or view details for the objects.

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

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

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

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

— Remove from View permissions Removes only View permissions for the selected users or groups. b. select Set Permission > Remove Permission over the object table. The Remove Permissions dialog displays.152 | Chapter 5 Configuring Enterprise Assets 2. 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. Click Deselect All to turn off all selections. Click Select All to select all users and groups. — Remove from Edit permissions Removes only Edit permissions for the TIBCO ActiveMatrix Administration . To remove permissions for runtime objects.

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

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

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

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

An internal keystore is one that has been uploaded into the database of the ActiveMatrix Administrator server. The private keys are encrypted using the keystore password. those keys cannot be recovered. which should be several words long. 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. which may or may not be the same as the password that protects the keystore's overall integrity. Reloading a keystore file is supported on internal keystores. Click the Browse. Click the Keystores link. The URL can point to a keystore managed by another ActiveMatrix Administrator server or a keystore in a file system. a. Type a name and description. 3. Type the password used to access the keystore in the Password field. Select the keystore and click Open. 4. In addition.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. button next to the Location field and navigate to the directory containing the keystore. 2.. each private key in the keystore can be protected using its own individual password. Click New > Internal Keystore. Click Save. 2. To manage keystores: 1. If the password is lost. 5.. An external keystore is a reference to a keystore via a URL. Keystore Types Keystores are internal or external. TIBCO ActiveMatrix Administration . Select Configure Enterprise Assets from the Perspective drop-down list.

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

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

• TIBCO ActiveMatrix Administration . Therefore. The new value does not take effect in a running node using that shared resource definition. If the substitution variable is used in a resource referenced by a service assembly running on that node. 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. You must restart the node or reinstall the shared resource. which would prevent you from installing the shared resource definition on a node. redeploy. Click Save. changing the value could invalidate the shared resource definition. and start the service assembly after you reinstall the shared resource. you must undeploy.168 | Chapter 5 Configuring Enterprise Assets 4.

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

To access environment definition functions: 1. 2. The next chapter explains how to work with an environment’s nodes. 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. Click the Environment Definition link. The user that created the environment. Description Created By Created On Description Name of the environment.170 | Chapter 6 Defining Environments Environments Overview This chapter explains how to define environments. TIBCO ActiveMatrix Administration . and the containers and shared resources required by each node. Short description of the environment. The date the environment was created.

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

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

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

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

messages are delivered when the node is up. 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. 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). Duplicate messages can be delivered if Messaging Bus fails to acknowledge the message. Messages are resent if the Enterprise Message Service server or target node is down. Messages are not logged to persistent storage. Messages are logged to persistent storage. Best Effort mode has the best throughput performance of the available quality of service modes. • • • TIBCO ActiveMatrix Administration . or if acknowledgement is not received by the server. If the target node is down. The characteristics of Best Effort delivery are: • • • Messages can be dropped if the server has undelivered messages and is then restarted. Duplicate messages can be delivered if Messaging Bus fails to acknowledge the message. provided the Enterprise Message Service server continues running without restarting in the interim. For example.Configuring Messaging Bus 175 | node uses the QoS setting that it retrieves from the database during startup. messages are delivered when the node is up (whether or not the Enterprise Message Service server continues running without restarting in the interim). The characteristics of At Least Once delivery are: • Messages are not dropped if the server has undelivered messages and if server is restarted. This is because messages are stored for delivery when the server restarts. If the target node is down. Messages are resent if the Enterprise Message Service server or target node is down. Messages are guaranteed to be delivered at least once. Best Effort Also known as Reliable Delivery. At Least Once Also known as Persistent. Throughput performance is not as good as At Most Once and Best Effort.

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

Click Save. b. You see the Choose JNDI Configuration dialog. 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. TIBCO ActiveMatrix Administration .Configuring Messaging Bus 177 | 3. as follows: a. 6. Complete the values according to the descriptions in Table 41 on page 178. You return to the Messaging Bus dialog. 5. Select a JNDI Configuration from the list and click Choose. 4. — JNDI Defines a connection based on JNDI lookup. If you select JNDI. Click the JNDI Configuration link. In the Connection Type field.

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

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

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. see the API documentation for TibjmsConnectionFactory in TIBCO Enterprise Message Service product documentation.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. you should change the host portion of the Provider URL to a fully-qualified hostname and confirm the server port. adding second a URL to enable reconnection. In. Under some circumstances it is quite useful. Message exchanges between nodes pointing to old server may continue seemingly inconsistent with broken interaction with nodes using the new server. any modification of the provider URL must be carefully considered. nodes are created within an environment. Message exchanges between nodes using the new server may take place seemingly inconsistent with broken interaction with nodes using the old server.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. For more information. For example. 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. 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. TIBCO ActiveMatrix Administration .

See Provider URL on page 180. Description 1. In the Messaging Servers area. see JNDI Shared Resource Definition Reference on page 128. Changes to the JNDI configuration change are considered safe with no implications since it is only a conduit to lookup the connection factory. Connection Factory The ConnectionFactory object stored in JNDI. select a messaging server. Default: GenericConnectionFactory. For information on how to create a JNDI shared resource definition. See Enabling Secure Communications Between Nodes and Messaging Servers on page 347. See your JNDI provider documentation for more information about creating and storing ConnectionFactory objects. Only nodes that have restarted after the configuration changes were applied use the modified parameter. Removing a Messaging Server from an Environment 1. Click Remove. TIBCO ActiveMatrix Administration . 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.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. 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. the connection factory is used to make the actual connection. Client Certificate Password The password of the certificate of messaging server clients.

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

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

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

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. The URL to use when publishing to the UDDI server. Enabled? Indicates whether the machine is enabled for this environment.Enabling UDDI Servers 185 | Table 43 UDDI Server Reference Column Name Publish URL Authentication Model Description The name of the UDDI server.

All referenced resources. Click Edit. 3. JDBC. 2. Rendezvous.186 | Chapter 6 Defining Environments Working with Shared Resource Definitions Shared resource definitions are specified at the enterprise assets level. perform the following in the environment definition screen: 1. such as Identity and JNDI. Only parent resources like HTTP. 2. and so on are visible in the Shared Resource Definitions screen. do not appear. 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. JMS. Click Save. To specify which shared resource definitions are enabled in an environment. Click the Shared Resource Definitions link. 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. Such resources are automatically enabled by enabling the parent resource. See Managing Shared Resource Definitions on page 114. TIBCO ActiveMatrix Administration . Select an environment in the Environments table.

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

and then configure its containers and shared resources. To access this screen: 1. All procedures in this section are performed in the Nodes screen. 2. For example. Certain long-running 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. 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 .188 | Chapter 7 Configuring Environments Working with Nodes A node is a Java virtual machine running ActiveMatrix containers and Messaging Bus. A node must be running before you can perform deploy service assemblies to it. you must click the Refresh button . you can create all the nodes. When you are setting up an environment. you add as many nodes as are needed for your architecture and specify on which machines they will be installed. To update a node’s status for such operations. Select the environment you want to configure from the Environment drop-down list. Node configuration could also be done using a different order. Then you install the nodes and start them. then install and start them all. Then move on to the next node and do the same kinds of actions again. such as installing and starting a node. are performed asynchronously. One approach to setting up the environment is to create one node. install it and start it. Select Configure an Environment from the Perspective drop-down list.

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

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

Stopping The node is in the process of being stopped. Unknown The status of the node cannot be determined. but whether the node process is running or stopped is not known. • • • • • • • • Start Failed1 Node startup has failed. Uninstalling Node configuration files are in the process of being removed from the machine. Machine The machine on which the node is installed. This state occurs after the node has been installed but before it has been started or after it has been started and then stopped. Uninstall Failed1 Node uninstallation has failed. 1.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. See Figure 17 on page 192. TIBCO ActiveMatrix Administration . Stop Failed1 Node stop has failed. Install Failed1 Node installation has failed. The status is a link that you can click to display a screen with information about the error. Running1 The node is running. Installed Node configuration files have been successfully generated on the machine. Starting The node is in the process of being started. 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.

A node installation directory is created in AMX_HOME/data/environmentname/nodename/. To install a node: 1. select the nodes you want to install and click Install. See Working with Containers on page 202 and Working with Shared Resources on page 207 for more details. TIBCO ActiveMatrix Administration . Installing and Uninstalling Nodes Installing Nodes Installing a node creates configuration files on the machine on which the node will run.exe. In the Nodes table. 2. The node executable is located in the bin subdirectory of the installation directory and is named environmentname_nodename. The nodes’ status changes to Installing. Click the Refresh button located at the top right of the table until the node’s status changes to Installed/Stopped.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. the Containers and Shared Resources links display information about the containers and shared resources that are available on this node.

The nodes’ status changes to uninstalling. The node status appears incorrect for some time and then is corrected. When you attempt to start the node from the Services application in the Control Panel a timeout error may be displayed. follow these steps: 1. Create a file name SvcTimeOut. Click the Refresh button located at the top right of the table until the nodes’ status changes to Running. In the Nodes table. Starting and Stopping Nodes After you have installed a node you can perform life cycle actions on it such as start and stop. To modify this timeout period. The node definition remains in the database and the node status changes to Defined. 2. Click the Refresh button located at the top right of the table until the nodes’ status changes to Defined. Starting Nodes To start a node: 1. To uninstall a node: 1. Windows On Windows platforms. select one or more nodes and click Start. you have the option to install the node as a Windows service. select one or more nodes and click Uninstall.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 . When you uninstall a node. In the Nodes table. 2.Working with Nodes 193 | Uninstalling Nodes Uninstallation removes the node’s configuration files from the machine where you installed it. all its containers and shared resources are also uninstalled. This occurs because the default timeout period Windows applies to services is too small for nodes. The nodes’ status changes to Starting. The node must be stopped and all service units unmapped from the node before you can uninstall it.

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

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

TIBCO ActiveMatrix Administration . The path to the ActiveMatrix installation directory on the machine on which the node is installed. Product Required. Default: No. The machine on which the node will run. Select a machine from the drop-down list containing the machines enabled in the environment. The name of the Windows service is TIBCO ActiveMatrix environmentname_nodename ENV_NAME. You cannot edit this setting after you install the node. Windows Service? Specify whether the node runs as a Windows service. 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. The startup type is Manual.196 | Chapter 7 Configuring Environments Table 45 Node Reference (Sheet 2 of 2) Field Machine Name Description Required.

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

If the nodes in an environment are configured to use a different Enterprise Message Service server for each node.JavaContainerName.Queue. For example. you must enable routing at the Enterprise Message Service server level.JavaContainerName.conf Add the following queue names to the Enterprise Message Service server 1 file: EnvironmentName.conf Create a unique name for each Enterprise Message Service server in the file.Java (Node2) .Destination@EMS-Serv er2 global • queues.Node2.Node2.Queue.Java (Node1) .Queue.Destination global EnvironmentName.Node1.conf Add the following queue names to the Enterprise Message Service server 2 file: EnvironmentName.Queue.conf file.JavaContainerName. By default this property is disabled.JavaContainerName. Enable the route property in tibemsd.Node3. queues.Destination global EnvironmentName.Destination@EMS-Serv er3 global TIBCO ActiveMatrix Administration .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.Java (Node3) For this scenario you must configure the Enterprise Message Service server configuration files as follows: • • • tibemsd. 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 .

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

If the HTTP connection supports non-SSL requests.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. Enables a Domain Name System (DNS) lookup for HTTP clients so that the IP address is resolved to a DNS name. Minimum Threads The minimum number of threads available for incoming HTTP requests. Unit is milliseconds. Default: 10866. Default: 1000. The HTTP server does create more than the number of threads specified by this parameter. Default: 25 Maximum Threads The maximum number of threads available for incoming HTTP requests. Default: 8081. When a client sends a request that cannot be processed because no threads are available. after accepting a connection. Default: 150 TIBCO ActiveMatrix Administration . and a request received requires SSL transport. Maximum size allowed for HTTP POST data. for the specific URI the request is sending to be presented. the ActiveMatrix node returns a ConnectionRefused exception to the client. Default: 20000. 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. This can adversely affect throughput. Unit is bytes. the request is redirected to the port you specify here. so enable this field only when required. Connection Timeout The number of milliseconds the connector waits. Status Enable DNS Lookups Maximum Post Size Redirect Port The status of HTTP server shared resource that implements the default connector: Installed.

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

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

2.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.matrix. The container element requires a type attribute in the format: com.runtime where the values that containerName and containerType can assume are listed in Table 47 Table 47 Container Type Attribute Components Container Java .NET Mediation Adapter SOAP JMS containerName java clr mediation adapter soap jms containerType se se se binding binding binding For example.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.container.runtime" version="2.containerNamecontainerType.Working with Containers 203 | Command-Line Interface To enable or disable a container. you add or delete a container to a node in full or base format. to add a node and then enable the Java container.tibco.tibco.0" /> TIBCO ActiveMatrix Administration .2.container.matrix.

0. 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. 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. If you don’t know the maintenance version.0.0 and choose the one with the highest maintenance version. The command-line interface finds all containers of version 1. In the Containers list. you can specify the version as 1. select a node. The version of the container.1.0. The command-line interface finds all containers of version 1. In the Nodes list. if you know that you have a container of version 1.0. you can specify 1. To deactiveate a container.1 but don’t know the version qualifier. 3. To activate a container. 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. click the Deactivate button. select a container. If a container is enabled for a node. click the Activate button. TIBCO ActiveMatrix Administration . Container Reference Table 48 Container Reference Field Name Version Description The name of the container.1 and choose the one with the highest version qualifier. 4. For example. 2.

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

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

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

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

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 .210 | Chapter 7 Configuring Environments Table 49 Shared Resource Reference (Cont’d) Field Resource Functions Description The resource function enabled for the shared resource. 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. such as HTTP servers (see Binding a Shared Resource Property to a Substitution Variable on page 116). Select Configure an Environment from the Perspective drop-down list. Click the Edit button above the Local Substitution Variables table. Click Save. Edit the variable’s type or value. To work with substitution variables: 1. Overriding a Substitution Variable Value To override a substitution variable value: 1. You must restart the node or reinstall the shared resource. Click Save. TIBCO ActiveMatrix Administration . Therefore. which would prevent you from installing the shared resource definition on the node. 2. changing the value could invalidate the shared resource definition. 2. 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.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. 3. 2. Click the Local Substitution Variables link. Click the Edit button above the Local Substitution Variables table. Click the Revert link. The new value does not take effect in a running node using that shared resource definition. The value of a substitution variable can be overridden at the node level. 3.

The variable’s type. which indicates that the value has been overridden locally or text. The variable’s value. which indicates that the global value is being used. 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. Either a Revert link.

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

214 | Chapter 7 Configuring Environments TIBCO ActiveMatrix Administration .

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

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

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 nodes required for the deployment must be running. Then you can configure and deploy it as needed. For example. the Deployable status of all other service assemblies with the same namespace is No. You can also undeploy it. all containers required for the deployment must be activated. and all shared resources must be installed.Deployment Overview 217 | Reusing Archives Each archive contains files for one service assembly. you can start and stop the service assembly and shut it down. TIBCO ActiveMatrix Administration . or for testing and later for staging. It is not possible to deploy more than one service assembly with the same namespace in an environment. To do so you upload the archive file again and give it a different service assembly name. or to implement different service level agreements. After a service assembly is deployed and running. 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.

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

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). 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. The version of the service assembly. The status of the service assembly. 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. TIBCO ActiveMatrix Administration . 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). The user that last modified the service assembly. The date and time that the service assembly was last modified. the property values are hardcoded with the value of the substitution variables at the time of upload. Once the property values are hardcoded. The user that created 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.

Follow the procedure described in Substitution Variables Reference on page 233. You must also map shared resource profiles to shared resources as appropriate for the service assembly. map the service units to nodes as described in Mapping Service Units to Nodes on page 231. 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.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. select the service assembly or assemblies. Click the Service Units button. Mapping Shared Resource Profiles to Shared Resources A shared resource profile specifies the kind of physical resource needed by services. For each service unit in the service assembly: a. 3. Map service units to nodes Edit substitution variables b. Click the Substitution Variable tab if you want to edit the substitution variables for the service unit. Select the service unit in the Service Units table. Shared resource profiles are defined at design time and packaged in the service assembly archive. In the Service Assemblies table. Configuring Service Units To configure the service units in a service assembly: 1. c. 2. TIBCO ActiveMatrix Administration . In the Node Mapping tab.

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

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

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

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 user that packaged the service assembly. Contact information for the maintainer of the service assembly. The namespace defined in the service assembly. the namespace must be unique within an environment. The name of the service assembly archive file that contains the service units to be deployed. TIBCO ActiveMatrix Administration .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.

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

Since messages are not routed through the Enterprise Message Service server. External Only external endpoints are exposed to Policy Manager. This option does not apply to topics because topic messages are always routed through the Enterprise Message Service server. • • None No endpoints are exposed to Policy Manager. requests are not load balanced among other provider instances available on other nodes. 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: External. One of the following values: • All Both internal and external endpoints are exposed to Policy Manager.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. Default: Yes. TIBCO ActiveMatrix Administration . Since topic messages are always go through Enterprise Message Service server. An internal endpoint is accessible only to consumers within an ActiveMatrix environment. Prefer Local Providers? If checked and the consumer and provider are collocated on same node then requests are routed to the local provider. An external endpoint has a binding that provides access to consumers outside the ActiveMatrix environment.

For example. a.Working with Service Assemblies 227 | 1. 4. The status is a link you can click to display a screen with information about the error. TIBCO ActiveMatrix Administration . 2. In the Service Assemblies table. 5. You can drill down to the Service Unit node mapping level to see the details. click the service assembly. 3. Click the Stop button and then click the Undeploy button. To update a service assembly archive: 1. 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. When you update a service assembly archive file the service assembly configuration is retained. Saving the configuration allows you to repeatedly update a service assembly while ensuring that configuration is performed once. A browse dialog displays. b. during iterative development you might need to fix a defect in a component implementation. Click the General Settings button. Select the archive file and click OK. Click Browse and navigate to the directory containing the updated archive file. In the General Information area. Click the Edit button at the right of the Service Assemblies table. click the Update button next to the Archive File field.

228 | Chapter 8 Deploying Service Assemblies Downloading a Service Assembly Archive You can download the archive file of any service assembly you have uploaded. 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. Table 53 shows the various types of changes you can make to the service assembly. The Redeploy action deploys the service units on the newly added nodes. 3. The downloaded archive is in its original form. Undeploy. In the General Information area. if you remove a node mapping when the service assembly status is Deployed. Click the General Settings button. Running or Running with Errors Stop. Deploy. 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. Specify the location to save the file and exit the dialog. click the link in the value of the Archive File field. Deploy Redeploy. it does not contain any service assembly configuration data. Remove mapping between one or more service units and one or more nodes Redeploy. The action undeploys the service units from the removed nodes. 4. For example. 2. The action undeploys the service units from the removed nodes. 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. you must propagate the changes to the nodes on which the assembly is deployed. The browser displays a file save dialog. To download a service assembly archive: 1. click the service assembly. Redeploy. In the Service Assemblies table. TIBCO ActiveMatrix Administration . Updating Service Assemblies When you update a service assembly. Start Redeploy.

Deleting Service Assemblies When you delete a service assembly. it is stopped. When you initiate the undeploy action on a running service assembly. or you can edit the settings and then redeploy. Deploy. Deploy Running or Running with Errors Stop. To delete services assemblies: 1. 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. in the Service Assemblies table.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. TIBCO ActiveMatrix Administration . A confirmation dialog is displayed. In the Service Assemblies table. You can redeploy with the same configuration. select one or more service assemblies and click Undeploy. you must stop and undeploy the assembly. To undeploy service assemblies. The status changes to Not Deployed. When you confirm the delete action on the service assembly. Click Delete. Start Undeploying Service Assemblies When you undeploy a service assembly. the service assembly archive and all the configuration values are removed from the database. before deleting a service assembly. Undeploy. select one or more service assemblies. then undeployed. 2. and then it is deleted. In general. However. it is stopped and then it is undeployed. the configuration values you set up are retained in the database.

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

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

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

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

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

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

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

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

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

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. deployment. It provides various views such as dashboard. page 248 Service View. page 242 Accessing the Monitor & Manage Perspective. infrastructure. page 245 Infrastructure View. page 283 Browse Mode. Topics • • • • • • • • • • Overview. service. page 278 Deployment View. page 244 Dashboard View. and log view. page 262 Service Instance View. page 240 Enabling Monitoring. page 259 Integrated Service View.

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

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

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

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

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

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. Table 62 Top 20 Hits Column Name Hits Description The service name. The Dashboard view displays the overall health of the system including a summary of service and system performance. The dashboard is an operational view of services and is updated automatically without intervention at regular frequency. Number of times the service has been invoked.Dashboard View 245 | Dashboard View When you select the Monitor & Manage perspective. The columns in the table specify the following details about a service. TIBCO ActiveMatrix Administration . A graphical representation of the hit history over the specified time period is displayed as a bar graph next to the Hits value. you enter in the Dashboard view by default. 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. Top 20 Hits The top 20 services that were the most active with respect to the specified period are displayed in this table.

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

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

Total number of active nodes against the total number of available nodes in the selected environment. click Infrastructure. The following machine properties are displayed as columns in the table. After you click Hostname. the details are displayed as described in Machine View on page 251. or View Node. Table 66 Machines Column Hostname Description The name of the machine. and then click View Environment.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. Machines. select a value in the Environments. In Browse mode (see Browse Mode on page 289). TIBCO ActiveMatrix Administration . Total number of active services against the total number of available services in the selected environment. the following details are displayed: • • • The name of the selected environment. or Node columns. 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. You can navigate to the Infrastructure view by using either of the following ways: • • Click the Infrastructure link. View Machine. 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.

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

Stopping The node is in the process of being stopped. hours. The CPU time is displayed in terms of days. and minutes. Starting The node is in the process of being started. The uptime is displayed in terms of days. Installed/Stopped1 The node configuration files have been installed on the machine but the node is not running. • • • Installing Node configuration files are in the process of being generated on the machine. Uninstall Failed1 Node uninstallation has failed. 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. Stop Failed1 Node stop has failed. Running1 The node is running. The number of fault to successful responses of services on a node. but whether the node process is running or stopped is not known. Install Failed1 Node installation 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. • • • • • • • • # of Services # of Containers Uptime CPU Time Faults/Successes Start Failed1 Node startup has failed. The number of services deployed on the node. The amount of CPU time consumed by the node since the node was started. hours. Unknown The status of the node cannot be determined. and minutes. The amount of time that has elapsed since the node was started. Installed Node configuration files have been successfully generated on the machine. The number of containers on the node. TIBCO ActiveMatrix Administration .

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

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

hours. # of Services # of Containers Uptime CPU Time Total number of services deployed on the node. Faults/Successes TIBCO ActiveMatrix Administration . The number of fault to successful responses. The CPU time is displayed in terms of days. Uninstall Failed1 Node uninstallation has failed. and minutes. Installed/Stopped1 The node configuration files have been installed on the machine but the node is not running. but whether the node process is running or stopped is not known. Uninstalling Node configuration files are in the process of being removed from the machine. Total number of containers activated on the node. The uptime is displayed in terms of days. Install Failed1 Node installation has failed. Stop Failed1 Node stop has failed. and minutes. Stopping The node is in the process of being stopped. Starting The node is in the process of being started. Installed Node configuration files have been successfully generated on the machine. Unknown The status of the node cannot be determined. • • • Installing Node configuration files are in the process of being generated on the machine. The amount of time that has elapsed since the node was installed. • • • • • • • Start Failed1 Node startup 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. Running1 The node is running. The amount of CPU time consumed by the nodes running on that machine.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. hours.

Yellow = 51-75%. You can click the hostname to get more details about the machine as described in Machine View on page 251. click a node name in the Nodes table. and service instances in a tabular format. Node View To display the Node view. The status is a link that you can click to display a screen with information about the error. and red values indicate the amount of memory consumed by the machine (Green = 0-50%. The name of the machine on which the node is running.100%). The bar signifies the amount of memory in use. 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 . yellow. The green. and Red = 76 . shared resources.

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

The amount of CPU time consumed by the node since the node was started. Since Started The number of successful responses since the node was started. Table 72 Containers Column Name Version Description The name of the container running on the selected node. Yellow = 51-75%. The green. Since Started The amount of time when the node was down against the time when the node was up and running (that is. The messaging server used for this node’s transport requirements. Each node is associated with one messaging server. The following properties of containers are displayed as columns of this table.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 date and time when the node was started. The amount of JVM memory consumed by the node against the total amount of memory available is displayed along with a bar graph. downtime versus uptime percentage) in the selected period. 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. The version of the container. TIBCO ActiveMatrix Administration . and Red = 76 .100%). Since Started The number of faults encountered since the node was started. Successes Time Period The number of successful responses in the selected period. Faults Time Period The number of faults encountered in the selected period. The bar signifies the amount of memory in use. Containers The Containers table displays the containers enabled on the selected node. The amount of time that has elapsed since the node was started. and red values indicate the amount of memory consumed by the machine (Green = 0-50%. downtime versus uptime percentage) since the node was started.

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

and minutes. Average Response Time The mean response time (in milliseconds) of all successful responses to request messages during the interval. The amount of time that has elapsed since the service was started. The number of service invocations since the service was started or the time period was set. The uptime is displayed in terms of days. The number of service invocations per second. whichever is later. hours. Responses per second during the interval. TIBCO ActiveMatrix Administration .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. Number of requests that resulted in a fault message/Number of request messages that arrived at the endpoint.

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

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

Adapter.Service View 261 | Click the Refresh icon to display the results based on the filter criteria. The performance data such as the average number of requests processed per minute for the selected period. and . If there are too many results. TIBCO ActiveMatrix Administration . The service version. Composite Reference Specifies that this service is not provided by the same composite and is referenced externally to services provided by an outside composite. in ascending alphabetical order. Table 75 Services Column Name Description The name of the service that satisfies the search criteria. JMS.NET. The date and time when the service was started. and minutes. The amount of time that has elapsed since the service was started. The data changes for the selected time period. The number of times the service has been invoked during the selected period. The type of the service implementation. 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 resource: • • Composite Service Specifies that this service belongs to an outside Version Container Type Resource Type composite. The types can be TIBCO ActiveMatrix Java. By default. Mediation. hours. click the Reset button. The average amount of time in milliseconds between receiving a request and returning a response over the selected period. the first 500 matching results are displayed. To discard the filter criteria and display all the services. all the results are sorted by service name. • 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. SOAP.

After you select a service assembly. click the View Services On Service Assembly button. and Service Units columns. After you select a service unit. click the View Services On Service Unit button. You navigate to the Integrated Service view as follows: • • Click Dashboard and select a service name link from the Service Metrics tables. Click the service name in the Services table from the displayed results in the search results area.262 | Chapter 9 Monitoring Infrastructure and Services Integrated Service View The Integrated Service view provides a view of services. — Click Deployment and select a value in the Environments. Click Service and specify a Search Criteria to view only the required services. In Browse mode (see Browse Mode on page 289): — Click Deployment and select a value in the Environments and Service Assemblies columns. 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 . Service Assemblies.

serviceUnitName is the service unit with which this service is associated. LOGICAL where. View Logs 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. The name of the service and number of nodes the service is deployed to are also displayed. myService on 10 Nodes. Logical Displays the logical trail to the service. For example. it opens the respective subview of the Deployment view. envName When you click envName. The trail shows how the service was deployed.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. • • serviceAssemblyName is the service assembly with which this service is serviceAssemblyName > serviceUnitName associated. When you click a name. Service Details The top section displays the service name with number of nodes that the service is deployed to. TIBCO ActiveMatrix Administration . it opens the Environment subview of the Deployment view.

SOAP. You are offered the option to save a file named service.NET. Concrete. and . You cannot generate WSDL for a component service or a composite reference. Description The name of the service. JMS.264 | Chapter 9 Monitoring Infrastructure and Services Generate WSDL The Generate WSDL button is displayed if the service is a composite service. description. Mediation. The available periods are Time Period or Since Started. The namespace that identifies the web service that implements the service. TIBCO ActiveMatrix Administration . The type of the service implementation: TIBCO ActiveMatrix Java. the WSDL file is displayed in a dialog. Click the Cancel button to dismiss the dialog. and performance data. When you click the button.wsdl or display the file. number of requests. The description of the service. WSDL is generated. Adapter. click the Click to download file link. 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. not abstract. To download the WSDL file. Overview The Overview tab provides information about the service such as name.

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

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 since the start date and time. Since Started The average request response time in milliseconds. This is the average per minute since the start date and time. 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. Since Started The total number of requests processed by the service per minute. Total Requests The total number of service requests received in the selected period and since the service was started. 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. Provides & Consumes The Provides & Consumes tab display details on the interfaces provided and consumed by the service.266 | Chapter 9 Table 78 Metric Monitoring Infrastructure and Services Performance (Cont’d) Description The performance data for the selected period. This is the average over the selected period. If the period is already set to Since Started. the column Since Started does not appear in the Performance table.

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

Table 82 describes the details about the services. which is the binding URL provided by the composite service. The number of times the service is invoked for the selected period. Interface Invokes The services consumed by the interface selected in the Consumes table are displayed in the Interface Invokes table. TIBCO ActiveMatrix Administration . page 278. The names appear in ascending order. External Endpoint The provided service can be accessed from external services using an external endpoint. The port type supported by the consumed service. The ratio of failed to successful hits for the selected period.268 | Chapter 9 Monitoring Infrastructure and Services Consumes The Consumes table provides details about the interfaces that are implemented by a consumed service. Table 81 describes the details about the consumer interface. The ratio of faults to successful hits for the selected period. Description The name of the service. Click the service to see information about the service as described in the Service Instance View. The composite element type of the consumed service. You can generate a concrete WSDL file for a composite service. 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. The number of times the service is invoked 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 port type being consumed by the service. For example. Composite Reference A composite reference is a provider and consumes an external binding URL. The number of time the service is invoked for the selected period. S3R1 is selected. Component Service S4I1 is pre-selected in the Provides table and in the Interfaces Consumed By table. the Provides & Consumes tab for Component S4 is opened. Type Fault/Success Hits The composite element type of the consumed service.Integrated Service View 269 | Consumes The Consumes table lists the services the composite service is consuming. Interface Invokes The services invoked by the interface selected in the Consumes table are displayed in the Interface Invokes table. The ratio of faults to successful hits for the selected period. if you select interface S3R1 in the Consumes table and select Component Service S4I1 in the Interface Invokes table. Table 84 Interface Invokes Column Name Description The name of the service consumed by the selected interface. TIBCO ActiveMatrix Administration . 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. Table 84 describes the details about the services. The number of times the service is invoked for the selected period. Table 83 describes the details of the services. The names appear in ascending order.

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

The interfaces and operations are sorted in ascending alphabetical order.Integrated Service View 271 | Deployment Details The Deployment Details tab provides deployment details for the service. This is across all nodes the service is deployed to. You can expand or collapse the data for each interface. This is across all nodes the service is deployed to. The total number of requests for the selected operation for the selected time period. TIBCO ActiveMatrix Administration . It also provides performance details by interface and operation across all nodes. Average The average request response time for the selected operation. The ratio of the number of failed hits to the number of successful hits for the selected period. Average The average message size for the selected operation. Table 87 Interfaces and Operations Column Name Description The interface and operation names. Maximum The maximum request response time for the selected operation. Maximum The maximum message size for the selected operation. 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. Number of requests per minute for the selected time period across all nodes the service is deployed to. The operations are grouped under interfaces. Interfaces & Operations The Interfaces & Operations table lists all the operations defined in services deployed on nodes. including the 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.

Install Failed Node installation has failed. Running The node process is running. The status can be: • • • • Defined The node definition is added but the node is not installed or has been uninstalled after installation. Start Failed Node startup failed. TIBCO ActiveMatrix Administration . 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. there are three transient states that can be displayed: Installing. The status of the node on which service is running. Link to the Service Instance view on the specified node as described in Service Instance View. Table 88 describes the details of the service. Starting. Unknown The state of the node cannot be determined.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. This state occurs after the node has been installed but before it has been started or after it has been started and then stopped. an error icon is displayed next to the message. Installed Node configuration files have been successfully generated on the machine. • • • • In addition. and Stopping. Stop Failed The node stop routine has failed to stop the node process. Same status as Uninstalled. Number of times the service is used. but whether the node process is running or stopped is not known. If there is a problem. page 278. Table 88 Nodes Column Node Name Status Description The names of the nodes on which the service is deployed. Installed/Stopped The node has been installed on the machine but the node is currently not running.

4. Permission to publish to a business was not granted to the user. click Sync or Unpublish. See UDDI Servers on page 274. UDDI Publishing Reference Figure 21 on page 274 shows the UDDI Publishing tab for the service JavaSOAPService. • • To sync or unpublish a service: 1.Integrated Service View 273 | UDDI Publishing UDDI Publishing tab allows you to publish. Optionally add metadata. 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 . The system crashed during a publish and the service was not published across all UDDI servers. click Publish. unpublish. 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. You can publish a composite service to any number of UDDI servers. In the Action column. 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. you may have deployed the service to a new node after you initially published to the UDDI server. Select a UDDI server. Select a business. The service is published to one UDDI server. See Business on page 275. 2. and sync the publish state of a service. Only UDDI servers added to the enterprise and enabled for the environment are available. Select a UDDI server. See Metadata on page 276. 3. For example. In the Action column. 2.

See Enabling Non-Administrator Users to Publish to the ActiveMatrix Registry on page 374. Publish URL The publish URL of the UDDI server. you must first transfer ownership of a specific tModel to a non-admin user. 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. TIBCO ActiveMatrix Administration . UDDI Servers Table 89 UDDI Servers Column Name Description The name of the UDDI server.

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

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

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. 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. However. Therefore. only one of those service instances is chosen to be published to the UDDI server. you must manually edit the service instance endpoint and replace it with the URL of the load balancer. TIBCO ActiveMatrix Administration . The node on which the service instance is deployed. To use the load balance URL. The UUID (Universally Unique Identifier) for the service instance.

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

After you click Name.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. Name is a link that you can click to see the details about the service unit. The version of the service unit. The columns in the table specify the properties of each bundled service unit in the service assembly. For example.matrix.container. 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 .container.runtime. The name of the container type.tibco. com.tibco. The names of the nodes on which the service unit is deployed. The current status of the service unit. Whether the service assembly has been configured for deployment. Status Version Type Nodes Mapped Service Unit View The details about a service unit are displayed in the Service Unit view. Description The current status of the service assembly.runtime or com.javase.matrix. Table 99 Service Units Metric Name Description The name of the service unit. the service unit details are displayed as described in Service Unit View on page 286.soapbinding. You can click a node name to view its details as described in the Node View on page 254. The data displayed in the table is updated every minute.

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

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

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

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

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

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

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

log service. You specify the destination to which nodes TIBCO ActiveMatrix Administration . An ActiveMatrix logging environment is depicted in Figure 22. ActiveMatrix supports the following destination types: console. database. Events logged to log services can be stored to a database. or forwarded for further processing. file. Log events are sent to destinations by log event generators and log services. • Event generator An ActiveMatrix runtime object (node or object running on a node) that generates log events. analyzed using the Log Viewer.294 | Chapter 10 Managing Logging Overview ActiveMatrix supports a flexible logging architecture that enables runtime objects to log events to a variety of destinations. 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.

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

See Logging Configurations on page 308. 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 . 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. See Working with Log Services on page 300. Importing Log Files into a Log Service Database If you want to view the log events in a log file in the Log Viewer. The LogServiceConfiguration element contains the following subelements: • • ImportLogFile The fully-qualified path to the CBE format log file. The following sections contain example build file task definition and data file elements.. 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. See Exporting Log Events to a File on page 325. 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). Build File <AMXAdminTask . When an ActiveMatrix logging configuration appender is set to a file.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.

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.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. TIBCO ActiveMatrix Administration . see Help > Help Contents > Monitoring and profiling applications. For information on how to use the profiling and analysis tools. 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. To import the exported log file and display the profiling and analysis perspective: 1. Log Viewer allows more complex and sophisticated query capability than the log viewer available in TIBCO Business Studio.

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

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

. 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 . Build File <AMXAdminTask ..Working with Log Services 307 | The following sections contain example build file task definition and data file elements.

service assemblies. Table 106 shows how to navigate to the screen where you configure the logging configuration for each type of parent-child set. You configure how objects log in a logging configuration. 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. 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.308 | Chapter 10 Managing Logging Working with Logging Configurations ActiveMatrix objects (nodes. and service units) can send log events to the console. TIBCO ActiveMatrix Administration . or a log service. If you do not specify a logging configuration for a child object. containers. 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. Logging Configurations A logging configuration specifies the type of events an ActiveMatrix object logs and the destination for log events. a file.

2. Click the XXX Logging button above the Logging Configurations table. 3. Click the Edit button above the Logging Configurations table. 4. Check the checkboxes next to the child objects you want to log. click a configuration. The Choose XXX to Log dialog appears. 5. Navigate to a screen containing a logging configuration according to Table 106 on page 308. 4. Click the Apply button. 3. where XXX can be either Container or Service Unit. Edit the parameters of the logging configuration following the descriptions in Table 107 on page 314. Click the Logging Configurations link. 6. Adding Child Logging Configurations To add child logging configurations: 1.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. TIBCO ActiveMatrix Administration . 2. Navigate to a screen containing a logging configuration according to Table 106 on page 308. 5. In the Logging Configurations table. Click Save. Click Logging Configurations.

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

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

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

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.tibco.tibco. </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.TibjmsInitialContextFactory as the default value.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.commonlogging" additivity="false"> <level value="INFO"/> <appender-ref ref="JMSAppender"/> </logger> .tibco. <appender class="com.tibjms. If the parameter isn't declared.tibco.Working with Logging Configurations 313 | . The properties for SSL support include: • ssl Set as true to support SSL connections. serverUrl Must be declared as tibjmsnaming://address:port instead of tcp://address:port to support JNDI lookup.appender.tibjms.TibjmsInitialContextFactory or some other context factories.tibco.naming..tibjms. providerContextFactory Should be declared as com.naming.cert.pem"/> <param name="sslVendor" value="entrust61"/> <param name="sslPassword" value="#!aMzD1eOJOkGgLfKujKD8NeXN7npa+7rBwqDjfJgUDCk="/> </appender> <logger name="com.. TIBCO ActiveMatrix Administration .commonlogging. JMSAppender will use com..

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. sslPassword Private key or password for the Enterprise Message Service server’s certificate. • • sslVerifyHost Specifies whether the appender should verify the Enterprise Message Service server’s certificate.conf.conf. TIBCO ActiveMatrix Administration . • • sslVendor The vendor name of the SSL implementation that the appender uses. sslTrustedCertificates The name of certificate keystores containing the issuer certificates of Enterprise Message Service server certificates.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.conf. the expected name is the hostname of the server. 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. If this parameter is not set. Object Logging Configuration Reference Table 107 Object Logging Configuration Reference Column objectName Description The object for which you are configuring logging. 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. sslExpectedHostName The name the appender expects in the CN field of the Enterprise Message Service server’s certificate.

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

You can also view log events by clicking the View Logs button that appears in various screens in the Monitor & Manage perspective. The Log Viewer will display. TIBCO ActiveMatrix Administration . see Monitoring Infrastructure and Services on page 239. For information on log services.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. The Log link in the Monitor & Manage heading does not display until you configure at least one log service with a database destination. 2. see Working with Log Services on page 300. Select Monitor & Manage from the Perspective drop-down list. For further information. Click the Log link in the Monitor & Manage heading. Displaying the Log Viewer To display the Log Viewer: 1.

Log Displays the log events that satisfy the query parameters. 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. Log Detail Displays the details of a log event selected in the Log area.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. Select the log service whose events you want to view from the Log Service drop-down list.

Model Contains an event model selector and a tree of the attributes available for each type of event model. click the Maximize button. Building. Maximizing and Minimizing the Query Builder The Log Viewer allows you to control the screen real estate used by the query builder. Toolbar Contains actions for displaying the query builder. Minimizing the query builder provides more real estate for viewing log events.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. To maximize the query builder. See Building Queries on page 321 and Saving and Deleting Queries on page 322. and deleting queries. TIBCO ActiveMatrix Administration . Filter Contains a canvas displaying the active filters. See Running Queries on page 322. but you can only view saved queries. saving. To minimize the query builder. Maximizing the query builder gives you full access to all query builder functions. Displaying query result hints and running queries. and clearing the filter area. selecting and running queries. click the Minimize button in the toolbar.

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). Only attributes from the currently selected model are displayed in the attribute tree. When you change the model selection. including BEF itself are listed in the model selection control. TIBCO ActiveMatrix Administration . Figure 27 Model Selection Control Setting the Model To set the model. As shown in Figure 27 on page 319. all extensions to the BEF model.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. all the filters displayed in the filter area are cleared. select the model from the Model drop-down list.

Figure 28 shows the filter area with the creation time filter and two optional filters: ActiveMatrix Logical Component ID and EEF Severity. 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. TIBCO ActiveMatrix Administration . click the Relative radio button and select a time from the drop-down list. For example. See Building Queries on page 321 for information on how to add and remove filters. The creation time filter is always present in the Filter area. To set an absolute creation time. 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. You can set the creation time filter as a relative or absolute time. click the Absolute radio button and specify From and To date and times using the respective date and time pickers. Filter Operators Some filters allow you to provide an attribute value against which the attribute in log event is compared. the filter in Figure 28 shows the = operator selected for the EEF Severity filter.320 | Chapter 10 Filter Area Managing Logging You create new queries by adding filters to the filter area. To set a relative creation time.

Right-click a cell in the Log and select Add filter with cell value. Available only for EEF Severity and EEF Priority. matches the following Context ID values: MyContext. Double-click the attributes from the model attributes tree. For example. TIBCO ActiveMatrix Administration . 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. The attribute value you provide contains a substring of the attribute value in the log event. The attribute value you provide is less than or equal to the attribute value in the log event. This operation appends the selected cell value to the filter area. 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. Select a row and then drag and drop a cell from the Log to the filter area. the value MyContext for a Context ID attribute. MyContextXXX.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. Click the Clear Filters button. Available only for EEF Severity and EEF Priority.

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

2. The queries are identified by the time that you ran the query. 2. 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. Running a Modified Query To run a modified query: 1. Select a query from the Saved Queries drop-down list. Click the Run Query button. 2. After running a query. Select a query from the Prev Queries drop-down list. Click the Run Query button. Running a Saved Query To run a saved query: 1. To run an existing query: 1. 2. When you change perspective or restart ActiveMatrix Administrator. 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. select a row in the Log. Build a new query using the query builder. TIBCO ActiveMatrix Administration . all the queries in the Prev Queries list are removed. Click the Run Query button. — 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. The filters specified in the query are displayed in the query builder.

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

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

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

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.

Contains a scheme field and fields defined by the scheme. Contains a scheme field and up to eight fields defined by the scheme. The ActiveMatrix scheme identifier is amx. The ID is: amx#service assembly name#service unit name#service name#operation name. A generic physical component identifier. Physical component identifier category. The ID is: amx#environment name#machine name#node name#container name. The time the log event was created. An ActiveMatrix physical component identifier. Contains a scheme field and up to eight fields defined by the scheme. An identifier of the parent of the context with which the log event is associated. AMX Physical Component ID Logical Component ID Generic Logical Component ID AMX Logical Component ID TIBCO ActiveMatrix Administration . The ActiveMatrix scheme identifier is amx. A physical address that corresponds to the location of a component. Used to search for log events that don't have a scheme or whose scheme is not supported by the Log Viewer. Subcategories are either generic or identified by a scheme. 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. An ActiveMatrix logical component identifier.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. Logical component identifier category. Subcategories are either generic or identified by a scheme. An identifier of the context with which the log event is associated. an application could specify a Generic Physical Component ID with field1 named cluster_name and field2 called machine_name. A generic logical component identifier. For example.

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

Deals with the situations that identify the completion status of a request. Deals with the situations documenting when a component creates an entity. about to create. Existing messages include words such as: port number ID. Any changes that a component makes to its configuration or that describe current configuration state should be logged using this category. such as heartbeat or performance information. RequestSituation ConfigureSituation AvailableSituation ReportSituation CreateSituation DestroySituation TIBCO ActiveMatrix Administration . connection failed. and now exists. Existing messages include words such as: configuration synchronization started and backup procedure complete. Deals with component operational state and availability. 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. Deals with the situations reported from the component. Existing messages include words such as: connection reset. and offline. Messages indicate a document was created or a file was created. Existing message include words such as: was created. Deals with components identifying their configuration. and failed to get a connection. or that a connection was ended. Messages indicate that a connection failed.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. that a connection was created. Deals with the situations documenting when a component removes or destroys an entity. online. and number of threads is. and process ID. operational and ready to process functional requests. Messages indicate that a document was destroyed or a file was deleted. Existing messages include words such as: was created. about to create. address ID. and now exists. 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. or operational and ready or not ready to process management requests. buffer size is. Existing messages include words such as: ready to take requests. Existing messages include words such as: utilization value is.

Message indicate services being available and services or features being unavailable. or that the expected version of a component was not found. Messages indicate a resource was not found. currently available. Existing messages include words such as: now available. Deals with the situations in which components cannot find some component or feature that they require.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. and transport is listening on port 123. Provides support for product-specific situations other than the predefined categories. that an application or subsystem that was unavailable. DependencySituation OtherSituation TIBCO ActiveMatrix Administration .

BusinessWorks tracking identifier. Warn Potentially harmful events. BusinessWorks job ID. BusinessWorks engine name. Fatal Very severe errors that will cause the process to abort. The ID of the operating system process hosting the engine. BusinessWorks project name. The importance of the event: Low. or High. 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. BusinessWorks process starter name. BusinessWorks process name.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. The thread ID of the component or subcomponent that generated the event. Error Application errors that allow the application to continue running. Medium. BusinessWorks activity name. TIBCO ActiveMatrix Administration . The name of the class that implements the engine.

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 .

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

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

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

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

property.338 | Appendix A Securing TIBCO ActiveMatrix Communication Channels Keystores This section describes how to configure TIBCO ActiveMatrix component keystores. TIBCO ActiveMatrix Administration .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.2/bin/ cluster_server. Obtain a server certificate from a CA using the CSR. 2.bat -uploadconfig. Import the server certificate into the servercerts keystore: keytool -keystore -file AMX_ADMIN_HOME/data/cluster/server/config/servercerts -import servercert -storepass pramati 4. 3.net. Restart the ActiveMatrix Administrator server from the command line: AMX_ADMIN_HOME/2.javax. add the following property to the ActiveMatrix Administrator server TRA file (see ActiveMatrix Administrator Server on page 352): java. 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. To use a commercial certificate: 1. 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.trustStorePassword.ssl. Generate a key and a CSR in the servercerts keystore.

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. Changing Keystore Passwords The default password for the servercerts and trustedcacerts keystores is pramati. type help change_trusted_store_password and follow the instructions. follow the procedure described in Installing a Server Certificate on page 338.args and remove the command line argument -noshell true 3. Locate the string application. Open the ActiveMatrix Administrator TRA file (see ActiveMatrix Administrator Server on page 352). 6. To change the password of the server or trusted certificate keystore: 1. Open a terminal window and run AMX_ADMIN_HOME/data/cluster/server/bin/cluster_server. 5. At the command prompt j2eeadmin@admin> type secsh. 2. 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. TIBCO ActiveMatrix Administration . To change the trusted certificate password. 4.exe. To change the server keystore password type help change_server_store_password and follow the instructions.

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

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

Restart the ActiveMatrix Administrator server from the command line: AMX_ADMIN_HOME/2. Install an ActiveMatrix Administrator server certificate into the ActiveMatrix Administrator server keystore following the procedure in Installing a Server Certificate on page 339. The ActiveMatrix Administrator server is a web application deployed and run inside a web server. 4. 3. 2. Enabling HTTPS for ActiveMatrix Administrator servers involves three steps: 1. To protect communication between a browser and an ActiveMatrix Administrator server.2/bin/ cluster_server. Open the file AMX_ADMIN_HOME/data/cluster/server/config/web-config.xml by the property https-port.bat -uploadconfig. By default the web server starts an HTTP listener. Enable HTTPS in the ActiveMatrix Administrator configuration file.xml. Enable HTTPS in ActiveMatrix Administrator server clients. 2. Search for the element ssl-enabled and set the value to true. TIBCO ActiveMatrix Administration . 3. To disable the HTTP port. 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. 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 in ActiveMatrix Administrator Server To enable HTTPS in an ActiveMatrix Administrator server: 1. you enable the HTTPS listener.

Enabling HTTPS in Management Daemon Management Daemon communicates with ActiveMatrix Administrator server on HTTPS. 4. TIBCO ActiveMatrix Administration . Import the issuer certificate of the ActiveMatrix Administrator server into the trusted certificate store of the node. 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. Change the value of the two instances of scheme property from http to https. Therefore. Enabling HTTPS in ActiveMatrix Nodes To enable HTTPS in ActiveMatrix nodes: 1.xml. Restart the node from the command line using the following command: AMX_HOME/data/environment/node/environment_node. Edit the file AMX_HOME/data/environment/node/config/security-config. Management Daemon.exe -uploadconfig. 2. 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. 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. 3. Change the URL in the Ant build file to use the https protocol instead of http. then configure each of these components to access ActiveMatrix Administrator on HTTPS. If the ActiveMatrix Administrator server is enabled with HTTPS. and the ActiveMatrix Administrator command-line tool all communicate with ActiveMatrix Administrator server on HTTP as clients. 2.Enabling HTTPS for ActiveMatrix Administrator Servers 343 | Enabling HTTPS in ActiveMatrix Administrator Clients ActiveMatrix nodes.

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

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

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

add the following properties and values prepending each property name with com. Required. select Shared Resource Definitions. Select New > JNDI.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. In the ActiveMatrix Administrator UI Configure Enterprise Assets Perspective.tibjms. 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.naming. entrust61 is the only supported vendor. Required. Required. TIBCO ActiveMatrix Administration . 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. Configuring Messaging Server To configure messaging server to use SSL: 1. In the Application Properties area.tibco. 2. 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.

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

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

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

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

2/bin/admincmdline.2/bin/createadminserver.tra AMX_ADMIN_HOME/2.0/bin/managementdaemon.tra AMX_HOME/data/environment/node/environment_node.tra TIBCO ActiveMatrix Administration .2/server/bin/server.tra ENV_HOME/managementdaemon/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.tra AMX_ADMIN_HOME/2.tra AMX_ADMIN_HOME/2.tra or AMX_HOME/2.2/bin/deleteadminserver.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.

page 354 Messages In AMX Binding Queue. Guaranteed message delivery incurs overhead. You enable guaranteed message delivery by configuring the Messaging Bus' quality of service as At Least Once (see Quality of Service on page 174).| 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. because messages are persisted in TIBCO Enterprise Message Service server and message delivery is transacted. page 355 Messages in JMS Container Queue. 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.4 is the minimum required version for guaranteed message delivery. TIBCO Enterprise Message Service 4. Topics • • • Race Condition Between Consumer and Provider. page 357 TIBCO ActiveMatrix Administration .

To mitigate message loss.messaging.tibco.targetendpoint. TIBCO ActiveMatrix Administration . so by default retry is not enabled.matrix.tibco.amxframework.messaging. restart the node.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. com. 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.retrycount com. The default value for these properties are 0 and 1 second.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. After modifying the properties.targetendpoint.amxframework.matrix.tra.

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

The message will be removed from the queue. TIBCO ActiveMatrix Administration .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. A provider should throw an exception for message to be delivered again.

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

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

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

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

TIBCO ActiveMatrix Administration . If maxpoolsize is less than sessioncount then the sessioncount is made equal to maxpoolsize. 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). Stop The sessions and thread pool are removed when the service is stopped. maxpoolsize Life Cycle Start The sessions and thread pool are created when the service is started. The thread pool does orderly shutdown by finishing all running threads.Overview 361 | Session Count and Max Pool Size Normalization must be greater than or equal to sessioncount. Additional threads may be created as required until pool size reaches maximum count. The thread pool may contain minimum number of threads during its creation.

362 | Appendix C Usage Session and Thread Pools The session and thread pool are intertwined when it comes to message processing. TIBCO ActiveMatrix Administration . 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. The thread pool may serve as sandbox available to every service for concurrent message processing. In case of distributed message processing. The session pool may serve as throttling mechanism to limit the delivery of messages from the Enterprise Message Service server. the JMS provider tries to get a session object from the session pool to deliver the messages. It avoids any interference or contention for threads by other services running in the node. The session object in turn tries to get a thread from the thread pool thus providing thread of control to invoke message listeners.

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

TIBCO ActiveMatrix Administration . The rationale being the system resource (that is.g. By increasing the sessioncount and maxpoolsize for a service enables the messaging bus to dramatically increase concurrent message delivery and processing. 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. average response time. The maxpoolsize property is applicable for both local and distributed service invocation. 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. In case of local invocation. Local Invocations It must be noted that the sessioncount property is only applicable for messages exchanged in a distributed environment i. 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. 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. For example.e. It is best to control message flow limit via sessioncount property so that message delivery is blocked until a session is available.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. 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. This is especially useful in case of services whose average response time is very small or services whose throughput must be high. 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. one of the available threads from thread pool is utilized to initiate the provider processing. That results in more reliable message delivery since the messages continue to be persisted in Enterprise Message Service server.

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

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

page 372 TIBCO ActiveMatrix Administration . page 369 ActiveMatrix Administrator Server Configuration. Topics • • • Overview.| 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. page 368 JVM Configuration.

The factors discussed in the ActiveMatrix Administrator Server section are applicable only to the ActiveMatrix Administrator server.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. 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. In production environments load can be high and faster response time is more important. The factors discussed in the following sections can be managed according to the use case. In non-production environments the load is minimal and the memory footprint is expected to be low. TIBCO ActiveMatrix Administration .

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

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

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

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

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

Custom keys can be accepted by the ActiveMatrix Registry either if they are being used by the admin user. Click Add tModel. 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.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. To transfer ownership of a tModel to a non-administrator user. 3. 2. 5. Click Create account. In the Publish area. Click Create Account 5. 4. Edit the required fields. For details on the Administration Console see the ActiveMatrix Registry product documentation. enter a name for the tModel. 3. 4. 6. Click the PUBLISH tab. Click Account management. start and log in to the ActiveMatrix Registry Administration Console and follow the tasks listed below. In the tModel key field. Click Custody transfer. Click MANAGE. Task E Create the Transfer Token 1. 2. Log in to the ActiveMatrix Registry Administration Console as the admin user. Task C Add a Non-Administrator User 1. Task D Add a tModel 1. click Add tModel. enter uddi:amx:keyGenerator. Click Request transfer token. 2. TIBCO ActiveMatrix Administration . or by a non-administrator user who has ownership of a tModel in the UDDI server named uddi:custom-key-generator:keyGenerator. In the name field.

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

Click MANAGE. 7. 8. Click Add selected groups. Check the system#everyone checkbox. Select allowed in all the drop-down lists. 12. Click the group radio button. Click the business. 6. 10. Click Edit. 2. 3. 5. Click the Permissions tab. Click Search. 9. 11. Click the edit icon in the system#everyone row.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. Click Save changes. TIBCO ActiveMatrix Administration . 4. Click Find business.

| 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. machine. 49. 296. 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. 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. 94 building queries 321 BW Engine Event Format Attribute reference 332 TIBCO ActiveMatrix Administration . 306. 45.

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. 296. 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. 45.xml 39. 108. 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. 50 default connector reference 199 default runtime node configuration 59 definitions 360 .378 | Index C change the reporting and polling intervals 21 changing a user password 141 changing keystore passwords 339. 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. 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.

283 environments overview 170 environments reference 170 TIBCO ActiveMatrix Administration .Index 379 | deleting a group or groups 144 deleting a keystore 158 deleting a log service 303 deleting a shared resource definition 117. 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. 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.

270 interface invokes 268. 94.380 | Index event detail 326 event formats 327 event models 295 Example 45 example 21. 269 interfaces & operations 271. 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 . 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. 306 existing ActiveMatrix Administrator server 42 exporting log events to a file 325 external endpoint 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. 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.

groups. and permissions 137 manual recovery 45 mapped nodes reference 233 mapping service units to nodes 231 mapping shared resource profiles to shared resources 220. in JDBC shared resources 123 JNDI connection type. 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. 340. 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 .Index 381 | J JDBC connection type. 341 managing UDDI servers 154 managing users in the database authentication realm 139 managing users. 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. 340. 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. 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.

HTTP shared resources 120 model area 319 monitor & manage 71 monitoring configuration 161 monitoring configuration reference 242 multiple objects 150.382 | Index minimum and maximum threads. 249. 281 performing actions 74 permanent generation size 371 permission types 147 TIBCO ActiveMatrix Administration . 252. 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. 147. 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. 288 number of web-worker threads 372 Q quality of service 174 O object formats 82 object logging configuration reference 314 objects 78.

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. 60 starting and stopping the TIBCO Common Logging Plug-in 299 starting installed nodes 8 starting nodes 193 TIBCO ActiveMatrix Administration .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. SQL Server. 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. 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.

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. discovery. 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 .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. 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. then install 8 two-step deployment first configure. 280 TRA file locations 352 two-step configuration first define.

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 . 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. 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. 237.Index 385 | V view logs 251.

386 | Index TIBCO ActiveMatrix Administration .

Sign up to vote on this title
UsefulNot useful