TIBEMAdvisor Usr

TIBCO Enterprise Management Advisor Users Guide
Software Release 2.1 May 2006
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE TIBCO ENTERPRISE MANAGEMENT ADVISOR USERS GUIDE). 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, Information Bus, The Power of Now, TIBCO Adapter, TIBCO BusinessWorks, TIBCO Administrator are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries. EJB, J2EE, JMS and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only. This software may be available on multiple operating systems. However, not all operating system platforms for a specific software version are released at the same time. Please see the readme.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. Copyright 2004-2006 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information
| iii
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi How to Contact TIBCO Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Chapter 2 Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Required TIBCO Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Installation Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Pre-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Installing TIBCO EM Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Uninstalling TIBCO EM Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Post Uninstallation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Additional Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Configuring TIBCO Hawk Microagent Plugin RvdServiceMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Administering TIBCO EMS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Setup for Fault Tolerance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Chapter 3 TIBCO Enterprise Management Advisor Components . . . . . . . . . . . . . . . . . . . . . . . 29

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 EMA Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Representation of Managed Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dependency Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating with TIBCO BusinessWorks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 31 32 34
EM Advisor Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Navigating Through the Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
iv
| Contents
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Invoking TIBCO Hawk Microagent Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 All Alerts Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 EMA ConfigUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Service Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Service Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining and Deleting Dependencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding and Deleting an External Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using TIBCO EM Advisor with External EM Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External EM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Available Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 57 57 57 60 62 62 63 65 67
Chapter 4 Trace Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Trace Message List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Appendix A Sample Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

default_config.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Sample custom_config.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Appendix B Icons Used By EM Advisor Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

EM Advisor Console Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
|v
Preface
This users guide explains how to use TIBCO Enterprise Management Advisor (TIBCO EM Advisor). TIBCO EM Advisor provides an automated application service-centric view of managed entities within the TIBCO Administrator environment. TIBCO EM Advisor also works with Enterprise Management platforms such as HP OpenView to give administrators and business managers complete bidirectional insight into network, application, and process data. By doing so, TIBCO EM Advisor gives them the ability to identify problems as they arise, analyze them within the context of the impact they are likely to have across the organization, and address them before they impact customers. This manual assumes you are familiar with TIBCO Rendezvous, TIBCO Enterprise Messaging Service (TIBCO EMS), TIBCO Administrator, and TIBCO Hawk.
Topics
Related Documentation, page vi How to Contact TIBCO Customer Support, page vii
vi
| Related Documentation
Related Documentation
This section lists documentation resources you may find useful.
TIBCO Product Documentation

The following documents form the Product documentation set: TIBCO Enterprise Management Advisor Users Guide: Read this manual to gain an understanding of installing and using TIBCO Enterprise Management Advisor. TIBCO Enterprise Management Advisor Release Notes: Read this manual for information on the current release of TIBCO Enterprise Management Advisor.
Other TIBCO Product Documentation

You may find it useful to read the documentation for the following TIBCO products: TIBCO Hawk software. This application provides network monitoring. TIBCO Administrator software. TIBCO administrator is the monitoring and managing interface for new-generation TIBCO products. TIBCO Runtime Agent software. The TIBCO Runtime Agent (TRA) is a bundle of TIBCO software and third-party software that is needed to run many TIBCO applications such as TIBCO BusinessWorks and TIBCO Adapters.
Preface vii
How to Contact TIBCO Customer Support

For comments or problems with this manual or the software it addresses, please contact TIBCO Support Services as follows. For an overview of TIBCO Support Services, and information about getting started with TIBCO Product Support, visit this site: http://www.tibco.com/services/support/default.jsp If you already have a valid maintenance or support contract, visit this site: http://support.tibco.com Entry to this site requires a username and password. If you do not have a username, you can request one.
viii
| How to Contact TIBCO Customer Support
|1
Chapter 1
Introduction
TIBCO Enterprise Management Advisor (TIBCO EM Advisor) provides an automated application service-centric view of managed entities within the TIBCO Administrator environment. TIBCO EM Advisor also works with Enterprise Management platforms such as HP OpenView to give administrators and business managers complete insight into system, network, application, and process data and status. This chapter introduces TIBCO Enterprise Management Advisor.
Topics
Overview, page 2 Architecture, page 4
| Chapter 1
Introduction
Overview
Companies today use a number of hardware and software systems to support their business processes. These business processes depend on a complex infrastructure of resources such as networks, servers, applications, storage devices, and security tools. Enterprise Management (EM) platforms monitor and administer such heterogeneous software and hardware systems in a centralized fashion. EM platforms are often aided by a central monitoring console which displays the status of the resources being monitored. Todays competitive environment demands that your companys business processes are up and running at all times and at the same time are able to change course to avert potential problems. This results in complex business processes which are increasingly getting automated and are supported by a complex array of IT components. EM platforms, typically, monitor and manage just the IT infrastructure resources and ensure their optimum performance. For example, they make sure the network is not congested or the disks are not full. What is not known is how a particular infrastructure problem is likely to impact a key business process. Being cognizant of the relationship between business processes and the resources that support them is crucial in ensuring optimum business performance. For example, it is not sufficient to know which disk is running low on space. You need to know which processes depend on this disk and of the business impact if the disk was rendered unusable. TIBCO EM Advisor can operate stand alone or work in partnership with EM platforms to give administrators and business managers complete insight into system, network, application, and process data. By doing so, TIBCO EM Advisor gives them the ability to identify problems as they arise, analyze them within the context of the business service impact they are likely to have across the organization, and address them before they impact customers.
Overview 3
Benefits Provides visibility into the mapping of business processes to IT infrastructure, providing business context to monitoring events from the supporting IT infrastructure. Enables ability to respond to problems and opportunities by modifying the underlying infrastructure that supports business processes. Reduces risk of critical business processes failing as a result of infrastructure problems by enabling people to pinpoint problem sources and initiate a rapid response. Improves effectiveness of IT departments by enabling staff to focus on handling situations that are most crucial to business success. Improves ability to manage service level agreements (SLAs) by providing metrics on both business process and infrastructure. Figure 1 Overview
CRM Order Management System Business Activity Monitoring Project Integration
TIBCO Enterprise Management Advisor
Enterprise Management System
| Chapter 1
Introduction
Architecture
TIBCO Enterprise Management Advisors environment consists of software components, external services such as databases, and the machines on which these components are running. Software components typically consist of databases, messaging components, and TIBCO software components manageable by TIBCO Hawk. TIBCO EM Advisor keeps track of all these managed objects which belong to its environment. The following figure shows the components of TIBCO EM Advisor and other parts of the TIBCO environment.
TIBCO EM Advisor Console TIBCO Administrator TIBCO Hawk
TIBCO Messaging
TIBCO Enterprise Management Advisor EMA Agent EMA ConfigUI
TIBCO BusinessWorks
TIBCO Adapter for SAP TIBCO Adapter for Files
Data Storage
EMA Agent EMA Agent is the runtime component of TIBCO EM Advisor and is responsible for discovering the managed objects, their relationships. and sharing this information with the EM platform. Managed objects are discovered either through interaction with the TIBCO Administrator application deployment environment or via network discovery from TIBCO Hawk Agents. Once the TIBCO environment has been discovered, EMA Agent forwards all alerts generated by TIBCO Hawk to the EM platform. TIBCO software components managed by TIBCO Hawk are configured with rules which provide instruction on what to monitor and the action to take when problems are encountered. When EMA Agent receives such alerts, it uses the configuration information of that
Architecture 5
service instance when relaying the alert information to the EM platform. An alert is the text message posted as a consequence of processing a TIBCO Hawk rule. TIBCO EM Advisor also provides metric data and facilitates interactive invocation of TIBCO Hawk methods. When the EM platform notices a decline in the performance based on the metrics and events reported by EMA Agent or by co-relating events from the supporting IT infrastructure that it is monitoring, it may choose to dictate options to correct the failing performance with minimal business impact. External EM Events are events sent by the EM platform to EMA Agent. EMA Agent, on receiving an External EM event makes it available to the entire domain using the configured TIBCO Messaging component or invokes a state control method within the BusinessWorks process engine utilizing the affected infrastructure. A software component managing business logic could use the information contained in this event message to modify business processes to counter the declining performance. EMA Agent acts as a bi-directional bridge between the EM platform and TIBCO applications. The managed objects belonging to TIBCO EM Advisors environment are organized into Domains. The primary domain, referred to as the Enterprise Domain, is the TIBCO Administrator domain where TIBCO EM Advisor is deployed. Any additional TIBCO Hawk domains that are monitored by TIBCO EM Advisor are referred to as Discovered Domains. EM Advisor Console EM Advisor Console helps visualize the managed objects and their relationships within the domain. This component is accessed via TIBCO Administrator. EMA ConfigUI EMA ConfigUI is the tool used to edit configuration information for the managed objects discovered in the additional TIBCO Hawk domains (referred to as Discovered domains) that you may be monitoring. Additionally, EMA ConfigUI is used to add managed objects such as disk drives and databases to the domain. Integration Protocols TIBCO EM Advisor enables a two-way exchange of data between EM platforms such as HP OpenView and the TIBCO environment using standard management interfaces. This version of TIBCO EM Advisor supports Web Services Management Framework (WSMF) v1.20.13. and Web Services Distributed Management (WSDM) 1.0 specifications.
| Chapter 1
Introduction
The WSMF specification is a management framework that provides a consistent and secure mechanism based on Web services for managing various types of resources. The WSDM standard specifies how the manageability of a resource is made available to the consumers using Web services. It provides a framework that enables management technologies to access and receive notifications of the resources. TIBCO Software Components TIBCO EM Advisor depends on the following TIBCO software components: TIBCO Administrator A server and browser application that work together to provide security and administration, as well as monitoring and management of processes and machines. TIBCO Runtime Agent (TRA) A process running on each machine that executes scripts, sends alerts, and performs recovery as specified.
An instance of TIBCO Administrator in the domain and a local TIBCO Runtime Agent must be installed and configured before installing TIBCO EM Advisor.
|7
Chapter 2
Installation and Configuration
This chapter describes how to install and configure TIBCO EM Advisor.
Topics
Installation Prerequisites, page 8 Installing TIBCO EM Advisor, page 11 Uninstalling TIBCO EM Advisor, page 12 Configuration, page 13 Configuring TIBCO Hawk Microagent Plugin RvdServiceMA, page 20 Administering TIBCO EMS Servers, page 23 Deployment, page 26 Setup for Fault Tolerance, page 27
| Chapter 2
Installation Prerequisites
Before starting the installation procedure, review the topics in this section to determine that your system has the basic requirements and that you have the prerequisite software installed.
System Requirements
The following table lists the supported platforms and the system prerequisites for installing TIBCO EM Advisor. Table 1 Supported Platforms and Required Disk Space OS
Microsoft Windows 2000 Server with Service Pack 2 and later HP-UX 11i and later HP-UX 11.2 and later Solaris 2.8 and later Linux 2.4.21 and later AIX 5.3
Hardware
x86
Disk Space (MB)

45
PA-RISC IA64 (Itanium) Sun SPARC Intel x86 Power
45 45 45 45 45
To access EM Advisor Console via TIBCO Administrator, your browser must be either Mozilla Firefox 1.0 or later or Microsoft Internet Explorer 6.x or later with the Java plug-in enabled (using JDK 1.4.2_05 or later).
Installation Prerequisites 9
Required TIBCO Products

The following table describes the required TIBCO products and their function. Table 2 Required TIBCO products Component
TIBCO Administrator 5.3
Purpose
TIBCO Administrator includes the following modules: User Management. Management of authentication, roles and users, that is, connecting roles (groups) and users to access control lists (ACLs). This includes security for deployed applications at runtime. Resource Management. Monitoring of machines and of all running applications in a TIBCO administration domain. Alerts can be created, for example, to notify an administrator if the number of processes or disk usage exceed a certain number. Application Management. Uploading of Enterprise Archive (EAR) files, creation, configuration, deployment, and monitoring of applications. This console is also used to start and stop applications.
An instance of TIBCO Administrator in the domain must be installed and configured before TIBCO Enterprise Management Advisor is installed. TIBCO Runtime Agent 5.3 TIBCO Runtime Agent supplies a number of TIBCO and third-party libraries used by TIBCO Enterprise Management Advisor and other TIBCO products at runtime. This includes, for example, TIBCO Rendezvous software. Make sure your operating system meets the minimum patch requirements as recommended by TIBCO Runtime Agent. See the documentation for TIBCO Runtime Agent for more information.
Each machine hosting TIBCO software components within the TIBCO EM Advisor domain must either run TIBCO Runtime Agent or TIBCO Hawk. Machines running TIBCO Hawk agents and TIBCO Rendezvous daemon (rvd or rvrd) processes that need to be monitored are required to have a static IP address.
10
| Chapter 2
Installation Packages
The following table lists the installation packages for the supported platforms. Table 3 Installation Packages OS
Microsoft Windows 2000 Service Pack 2 and later HP-UX 11i and later HP-UX 11.2 and later Solaris 2.8 and later Linux 2.4.21 and later AIX 5.3
Package Name
TIB_ema-simple_2.1.0_w32.exe
TIB_ema-simple_2.1.0_h7_110.bin TIB_ema-simple_2.1.0_h7_ia64.bin TIB_ema-simple_2.1.0_s4_57.bin TIB_ema-simple_2.1.0_lnx86_24.bin TIB_ema-simple_2.1.0_rs_51.bin
Pre-Installation Tasks
Follow these steps If upgrading from a previous version of TIBCO EM Advisor: 1. Backup the following files if you have updated them: custom_config.xml and default_config.xml 2. Un-install the current TIBCO EM Advisor installation. 3. Remove the following plugins using TIBCO Administrator EMAdvisor-Console EMAdmin HawkConsole You can now install TIBCO EM Advisor 2.1.0.
Installing TIBCO EM Advisor 11
Installing TIBCO EM Advisor

This section describes the steps involved in installing TIBCO EM Advisor. 1. Verify that TIBCO Runtime Agent and TIBCO Administrator have been installed and are running. 2. Navigate to the directory appropriate for your platform on the installation CD. 3. Invoke the installer. On Microsoft Windows, double-click on the executable
TIB_ema_simple_2.1.0_w32.exe
On UNIX, invoke the installation package for your platform. See Table 3 on page 10 for the list of package names. For example, for the Solaris 2.8 platform, type the command:
./TIB_ema_simple_2.1.0_s4_57.bin
4. Review and accept the license agreement. 5. By default, TIBCO EM Advisor is installed under the directory specified by the variable TIBCO_HOME. This variable is set by the first TIBCO product installed on the machine. 6. Select between a typical install and a custom install. A typical install has minimal prompts and installs standard components in default locations. A custom install allows you to choose the components from the product suite to install and installs only those components
On HP-UX platforms, the environment variable SHLIB_PATH must contain $TIBCO_HOME/jre/1.4.1/hotspot:$TIBCO_HOME/jre/1.4.1 before starting any TIBCO application. When using TIBCO Enterprise Message Service (TIBCO EMS), in the .tra file used by TIBCO Administrator the jar files used by TIBCO EMS (tibrvjms.jar, tibjms.jar, and jms.jar) should be placed before tibrvj.jar.
12
| Chapter 2
Uninstalling TIBCO EM Advisor

This section describes how you can uninstall TIBCO EM Advisor.
Microsoft Windows
Use one of the following options to uninstall TIBCO EM Advisor: Click Start>Programs>TIBCO>TIBCO Enterprise Management Advisor 2.1>Uninstall Navigate to the _uninst directory located in the TIBCO EM Advisor home directory and invoke the Tibuninstall.exe program.
UNIX
Navigate to the _uninst directory located in the TIBCO EM Advisor home directory and invoke the Tibuninstall.exe program.
Post Uninstallation Tasks

After the uninstallation process is complete, you will have to manually remove the plugins used by TIBCO EM Advisor. To do this: 1. Log into your TIBCO Administrator domain. 2. Click All Service Instances>TIBCO Administrator>Plug-Ins>Remove and remove the following plugins:
EMAdvisor-Console HawkConsole
3. Click Application Management>EMAdvisor>Configuration>Undeploy to undeploy EMAdvisor. 4. Select EMAdvisor from the Application Management console and click Delete. 5. Make sure all instances of TIBCO EM Advisor within the domain are uninstalled. 6. Click All Service Instances>TIBCO Administrator>Plug-Ins>Remove and remove the EMAAdmin plugin.
Configuration 13
Configuration
This section describes the configuration tasks of the Configuration Console. To access the configuration console of TIBCO EM Advisor, from the left pane of TIBCO Administrator click Application Management> EMAdvisor>Configuration. Within this pane, click emaagent.sar. The following tabs are available: General This tab contains the following fields: General Name Service name. Description Service description. Additional Required Components Any other components required to run this service. You cannot enable the service unless this field is empty. Enable Service Only enabled services are deployed. Disabling a service, effectively undeploys just that service while allowing all other services in the application run as normal. This can be useful, for example when you wish to deploy an application that includes a service for which you don't have the required software. General EMA Agent External Web Services
Target Machines Remove from Selected Machines Click to remove this service configuration from the selected machine(s). Add to Additional Machines Adding services to additional machines is useful for fault tolerance. As a rule, it therefore does not make sense to run the same service on the same machine twice. Service Instance Service instance from the selected machine. The service instance name includes the machine name. Software The software required by this service instance.
14
| Chapter 2
Deployment Status Deployment status, as shown in the Configuration Builder. FT Weight The fault tolerance status and weight of the service instance. Appears only if Run Fault Tolerant is selected.
FT Group Settings Appears only if the EMA Agent is assigned to additional machines. Run Fault Tolerant If selected, the selected service instances will run in fault tolerant mode. Heartbeat Interval (ms) The master engine of a fault-tolerant group broadcasts heartbeat messages to inform the other group members that it is still active. The heartbeat interval determines the time (in milliseconds) between heartbeat messages. In the event if one process engine fails, another engine detects the stop in the masters heartbeat and resumes operation in place of the other engine. All process starters are restarted on the secondary, and services are restarted to the state of their last checkpoint. Activation Interval (ms) A standard TIBCO Rendezvous fault tolerant parameter, documented in the TIBCO Rendezvous Concepts chapter 15, Developing Fault Tolerant Programs. Secondary process engines track heartbeat messages sent from the master engine. This field specifies the amount of time to expire since the last heartbeat from the master before the secondary restarts the process starters and process engines. The Heartbeat Interval should be smaller than the Preparation Interval, which should be smaller than the Activation interval. It is recommended that Activation Interval be slightly over 2 heartbeats. Preparation Interval (ms) A standard TIBCO Rendezvous fault tolerant parameter, documented in the TIBCO Rendezvous Concepts chapter 15 Developing Fault Tolerant Programs). When a master engine resumes operation, the secondary engine shuts down and returns to standby mode. For some situations, it may be necessary to ensure that the secondary engine has completely shut down before the master engine resumes operation. This field is used to specify a delay before the master engine restarts. When the time since the last heartbeat from an active member exceeds this value, the ranking inactive member will receive a "hint" so that it can prepare for activation. The Heartbeat Interval should be smaller than the Preparation Interval, which should be smaller than the Activation interval.
Configuration 15
EMA Agent Tab This tab contains of the following panes: Agent Running Modes This pane has the following fields: Enable Enterprise Mode Select this checkbox to read deployment data stored by TIBCO Administrator for applications deployed in your TIBCO Administrator domain. Enable Discovery Mode Select this checkbox to discover applications that were not deployed through TIBCO Administrator and to discover managed objects from your other TIBCO Hawk Domains.
Hawk Domains This pane lists the Hawk domains that are monitored by this instance of EMA. To add additional domains, click the Add button and choose the configured Hawk domains listed in the Add Additional Hawk Domains pane. To configure additional Hawk domains, see Configuring Multiple Hawk Domains, page 15. To delete a domain, choose any of the listed Hawk Domain names and click Delete. Deleting a Hawk domain will delete the domain from the monitoring configuration of this EMA instance. Configuring Multiple Hawk Domains To configure additional Hawk domains for use by EMA, click Monitoring Management>Hawk Configuration. After an additional Hawk domain is configured, TIBCO EM Advisor should be re-deployed and the EMA Agent re-started for the changes to take effect. Click Add to configure a Hawk domain. The following table lists the parameters that need to be specified Hawk Domain Transport Network transport used by the TIBCO Hawk domain. Possible choices are RV Transport or EMS Transport.
If you choose RV Transport, values for the following fields should be specified: Hawk Domain Name Name of the TIBCO Hawk domain. RV Service, RV Network, and RV Daemon These attributes together configure the TIBCO Rendezvous parameters for communicating with TIBCO Hawk agent.
16
| Chapter 2
Hawk Security Impl (Optional) The name of the class implementing the security policy.
If you choose EMS Transport, values for the following fields should be specified: EMS Server URL The location of the EMS server. EMS User and EMS Password The login credentials to access the EMS server. Hawk Security Impl (Optional) The name of the class implementing the security policy. Use SSL Select this checkbox if using SSL to connect to the EMS server. If this checkbox is selected, the Configure SSL button is displayed. Click the Configure SSL button to configure the SSL parameters.
The following SSL parameters should be specified: Vendor The name of the SSL implementation. Ciphers When specifying this option to specify the cipher suites that can be used, use the ^ qualifier instead of a - qualifier. For more information on specifying cipher suites, refer to the TIBCO Enterprise Message Service documentation.
Settings for Hawk components to verify EMS server Authenticate EMS server Select this checkbox if the Hawk components should verify the EMS server. Server Name Trusted The option specifies the file name of the server certificates.
Settings for EMS server to verify Hawk components Identity The digital certificate of the TIBCO Hawk components. Private Key The private key of the TIBCO Hawk component. Password The password to decrypt the identity file of the Hawk component.
When using TIBCO Enterprise Message Service (TIBCO EMS), in the .tra file used by TIBCO Administrator the jar files used by TIBCO EMS (tibrvjms.jar, tibjms.jar, and jms.jar) should be placed before tibrvj.jar.
To delete a TIBCO Hawk domain, select a domain from the displayed list and click the Delete button.
Configuration 17
External Web Services Customize this tab only when using TIBCO EM Advisor with an EM platform. In all other cases, the Disable External Web Service Interfaces checkbox should selected. If the Disable
External Web Service Interfaces checkbox is not selected, the Web Services Parameters
pane is displayed.
Web Services Parameters This pane has the following fields: External Interface Choose between WSDM and WSMF. If WSMF is chosen, an additional pane External EM Events is displayed. HTTP Port The HTTP port used by the internal HTTP server of EMA Agent. Use HTTPS If this checkbox is selected, the Config SSL button is displayed. Click Config SSL to specify the SSL information for TIBCO EM Advisor.
EMA SSL Information Specify the Secondary HTTP Port. EMA Server SSL Parameters Specify the Identity Type Choose between Identity_File and
Certificate_PrivateKey.
If you choose Identity_File, specify the following parameters: Identity File The full path name for the identity file. Identity File Type Choose between Entrust, JCEKS, JKS, PKCS12. Identity Password The password for the identity file. Click the change.. button to change the password. If you choose Certificate_PrivateKey, specify the following parameters: Certificate The full path name for the certificate file. Private Key The private key for the certificate. Private Key Password The password for the private key. Click change.. to change the password. If the Require Client Trusted Certificate.
Authentication
checkbox is selected, specify the
18
| Chapter 2
Alerts Alert Filter Threshold Choose between high, medium, or low. This controls the lowest level of the alerts that will be forwarded to the EM platform. External EM Events This pane is displayed when WSMF is the chosen External Interface. Root WDSL URL This elements points to the top-level node of the managed object hierarchy of the EM platform. HTTP Client Port Used by the External EM event client to receive External EM events from the EM platform. Publish EMS Messages If this checkbox is selected, the following fields are displayed and values for these should be specified: EMS Server URL The protocol and the address of the running instance of the JMS server. EMS Topic The topic name used for publishing JMS messages for the received External EM events. EMS User, EMS Password The login credentials to access the EMS server. Publish RV Messages If this checkbox is selected, the following fields are displayed and the values for these should be specified. RV Service RV Network RV Daemon These attributes together configure the TIBCO Rendezvous transport for publishing the parsed External EM event messages. Config Retry Parameters If this checkbox is selected, the following fields are displayed and values for these should be specified. Retry Interval Retry Total
Any change made to the configuration information after TIBCO EM Advisor is deployed requires that you re-deploy TIBCO EM Advisor for the changes to take effect.
Configuration 19
Additional Configuration
EMA Agent uses a configuration file default_config.xml that contains parameters which aid in discovering TIBCO applications within the domain and in collecting metrics for the discovered applications. This configuration file is located in the following directory:
<TIBCO_HOME>\ema\2.1\config
where <TIBCO_HOME> is the TIBCO installation directory. The configuration file located in the directory mentioned above is a template and each time TIBCO EM Advisor is deployed a copy of this file is used for that specific deployment. It is not recommended that you change the template or the deployment specific configuration file unless instructed by TIBCO Support for troubleshooting purposes. For details on the contents of this file and how this file is used by EMA Agent, see default_config.xml on page 88. If you have custom applications deployed, specify rules for discovering those applications in the custom_config.xml configuration file. This configuration file is located in the same directory as default_config.xml. Sample Configuration Files on page 87 lists a sample custom_config.xml file.
20
| Chapter 2
Configuring TIBCO Hawk Microagent Plugin RvdServiceMA

RvdServiceMA is a TIBCO Hawk microagent which aids in the discovery of TIBCO Rendezvous daemons in the additional Hawk domains, referred to as Discovered domains, monitored by TIBCO EMA. Additionally, RvdServiceMA helps monitor the status of the discovered TIBCO Rendezvous daemons and provide metrics. If RvdServiceMA is not installed, all TIBCO Rendezvous daemons in the Discovered domains will have a status of UNKNOWN and the capability to invoke TIBCO Hawk methods for the microagent will not be available through EM Advisor Console. You need to configure one instance of RvdServiceMA per Discovered domain per subnet. To install the TIBCO Hawk microagent RvdServiceMA: 1. Copy the files used by RvdServiceMA. Users of TIBCO Hawk: Copy the hma directory and its contents from the machine where TIBCO EM Advisor is installed to the directory used for TIBCO Hawk plugin configuration files on the machine running the rvrd process. If RvdServiceMA is the first plugin used by TIBCO Hawk, create a directory to hold the plugin configuration files. The contents of the hma directory are:
RvdServiceMA.jar RvdServiceMA.hma
Users of TIBCO Runtime Agent: Copy the contents of the hma directory to the <TIBCO_HOME>\tra\domain\<domain-name>\plugin directory of TIBCO Runtime Agent, where domain-name> is your TIBCO Administrator domain. The following files are copied:
RvdServiceMA.jar RvdServiceMA.hma
2. Update the MicroAgent Plugins option (Users of TIBCO Hawk on the Microsoft Windows platform only)
Configuring TIBCO Hawk Microagent Plugin RvdServiceMA 21
On the Microsoft Windows platform, users use the Update the MicroAgent Plugins option using TIBCO Hawk Configuration Utility. To use the Configuration Utility: Select Start>Programs>TIBCO>TIBCO Hawk>Hawk Configuration. Navigate to the Agent
Configuration
tab.
Update the Plugins option to specify the directory that will be searched when loading the microagent plugins. For more information, see TIBCO Hawk Installation and Configuration. Skip step 3 and proceed to step 4. 3. Update the hawkagent.cfg file Users of TIBCO Hawk on UNIX: the hawkagent.cfg file is located in
<TIBCO Hawk installation directory>/bin
Users of TIBCO Runtime Agent: the location of the hawkagent.cfg file is pointed by the value of the command line argument applications.args contained in the file: On Microsoft Windows: <TIBCO
TRA installation directory>\domain\< TIBCO Administrator domain name>\hawkagent_< TIBCO Administrator domain name>.tra
On UNIX: <TIBCO
TRA installation directory>/domain/< TIBCO
Administrator domain name>/hawkagent_< TIBCO Administrator domain name>.tra
For example, if your TIBCO Administrator domain name is MyDomain and your TIBCO Runtime Agent installation directory on Microsoft Windows is c:\tibco\tra then the location of the hawkagent.cfg file is contained in the file
c:\tibco\tra\domain\MyDomain\hawkagent_MYDomain.tra
Within the hawkagent.cfg file, update the -hma_plugin_dir option. This option specifies the directory that will be searched when loading the microagent plugins. For more information, see TIBCO Hawk Installation and Configuration.
hawkagent.cfg
If RvdServiceMA is not the first plugin used by TIBCO Hawk, no changes to are necessary.
4. Update the arguments section of the RvdServiceMA.hma file with the appropriate TIBCO Rendezvous parameters. Replicate the <arg> element with appropriate values to discover multiple TIBCO Rendezvous daemons within that subnet. 5. Re-start the TIBCO Hawk agent.
22
| Chapter 2
To use TIBCO Hawk microagent RvdServiceMA, you need to run JRE 1.4.x and TIBCO Hawk version 4.1.0 or later on the host computer where RvdServiceMA is installed. It will not work with JRE 1.3.x.
Administering TIBCO EMS Servers 23
Administering TIBCO EMS Servers

To monitor and manage TIBCO EMS servers in your domain, you need to load the provided HawkController class into the TIBCO Hawk agent. Once the classes are loaded, methods for managing the EMS server are available. Make sure you have added the EMS server to your Enterprise domain using TIBCO Domain Utility. For more information refer to TIBCO Runtime Agent Domain Utility Users Guide. To load the HawkController class: 1. Copy the required files. Users of TIBCO Hawk: Copy the tibemsadmin.hma file from the TIBCO Enterprise Message Service installation directory under the samples\admin\hawk subdirectory and copy it into your TIBCO Hawk plugins directory, which is typically <TIBCO_HOME>\hawk\plugins. If this directory does not exist, create it. Also, locate tibjmsadmin.jar, jms.jar, and tibjms.jar in the clients\java subdirectory and copy these files into the TIBCO Hawk plugins directory. Users of TIBCO Runtime Agent: Copy the tibemsadmin.hma file from the TIBCO Enterprise Message Service installation directory under the samples\admin\hawk subdirectory and copy it into your the plugin directory of TIBCO Runtime Agent, which is typically <TIBCO_HOME>\tra\domain\<domain-name>\plugin, where domain-name> is your TIBCO Administrator domain. Also, locate tibjmsadmin.jar, jms.jar, and tibjms.jar in the clients\java subdirectory and copy these files into the plugin directory of TIBCO Runtime Agent. 2. Update the MicroAgent Plugins option (Users of TIBCO Hawk on the Microsoft Windows platform only)
24
| Chapter 2
On the Microsoft Windows platform, users use the Update the MicroAgent Plugins option using TIBCO Hawk Configuration Utility. To use the Configuration Utility: Select Start>Programs>TIBCO>TIBCO Hawk>Hawk Configuration. Navigate to the Agent
Configuration
tab.
Update the Plugins option to specify the directory that will be searched when loading the microagent plugins. For more information, see TIBCO Hawk Installation and Configuration. Skip step 3 and proceed to step 4. 3. Update the hawkagent.cfg file Users of TIBCO Hawk on UNIX: the hawkagent.cfg file is located in
<TIBCO Hawk installation directory>/bin
Users of TIBCO Runtime Agent: the location of the hawkagent.cfg file is pointed by the value of the command line argument applications.args contained in the file: On Microsoft Windows: <TIBCO
TRA installation directory>\domain\< TIBCO Administrator domain name>\hawkagent_< TIBCO Administrator domain name>.tra
On UNIX: <TIBCO
TRA installation directory>/domain/< TIBCO
Administrator domain name>/hawkagent_< TIBCO Administrator domain name>.tra
For example, if your TIBCO Administrator domain name is MyDomain and your TIBCO Runtime Agent installation directory on Microsoft Windows is c:\tibco\tra then the location of the hawkagent.cfg file is contained in the file
c:\tibco\tra\domain\MyDomain\hawkagent_MyDomain.tra
Within the hawkagent.cfg file, update the -hma_plugin_dir option. This option specifies the directory that will be searched when loading the microagent plugins. For more information, see TIBCO Hawk Installation and Configuration.
hawkagent.cfg
If this is not the first plugin used by TIBCO Hawk, no changes to are necessary.
4. Navigate to the plugins directory and open the tibemsadmin.hma file for editing. 5. Specify HawkController in the <classname> element.
Administering TIBCO EMS Servers 25
6. Update the <arg> element and specify the username, password, and server URL to use to connect to the TIBCO EMS server. Make sure that the specified user has Administrator privileges. For example:
<arguments> <arg>-user</arg> <arg>admin</arg> <arg>-password</arg> <arg>admin_pass</arg> <arg>-server</arg> <arg>tcp://server1.yourcompany.com:7222</arg> <arg>-timeout</arg> <arg>5</arg> </arguments>
You should use specify the predefined admin user or a user that is a member of the $admin group.
26
| Chapter 2
Deployment
After completing configuration, TIBCO EM Advisor can be deployed. 1. From the TIBCO Administrator left pane, select Application Management> EMAdvisor>Configuration.
2. Choose the General tab. 3. From the Target Machines pane, select a machine where TIBCO EM Advisor will be deployed. Click Add to Additional Machines. 4. Click Save to save the configuration information. 5. TIBCO Administrator returns to the Configuration console, here click Deploy. 6. Enter a description for this deployment. Click OK. 7. TIBCO Administrator returns to the Configuration console and updates the panel with information in the Deployed Configuration pane.
Setup for Fault Tolerance 27
Setup for Fault Tolerance

TIBCO EM Advisor offers fault tolerance by allowing multiple EMA Agents to connect to the EM platform. In the simplest scenario, there will be two EMA Agents deployed on different machines, one of which be the designated primary and the other the secondary. You can deploy more than one EMA Agent to function as the secondary. Primary and Secondary EMA Agents The primary and secondary EMA Agents will function in the active-warm standby mode. During normal operation both EMA Agents will be running using the same configuration data and will connect to the same TIBCO Administrator instance and will manage the same set of managed objects. Failover Process When the primary fails, the secondary EMA Agent will take over using the same data model of the managed objects as the primary. Managed objects for applications deployed after the secondary takes over will not be added to the data model. After the secondary takes over only alerts, clears and status change notifications will be forwarded to the EM platform. In case of a failover, when the secondary EMA Agent takes over, the EM platform will be required to re-discover all managed objects using the secondary EMA Agent and re-send subscription requests for each managed objects. If integration with TIBCO BusinessWorks is enabled, in case of a failover, the secondary EMA Agent will update the TIBCO BusinessWorks processes with the alert status. Deployment In order to setup the fault tolerant system, you should have TIBCO EM Advisor installed on the two machines that will constitute your fault tolerant system. These machines should be part of your Enterprise domain. 1. Configure EMA Agent and add it to your target machines. The following figure shows the machines pprasad-nb and wilder added to the EMA Agent.
28
| Chapter 2
2. Specify the FT Weight, which is the fault tolerant status and weight for each EMA Agent. The FT Weight column appears only if Run Fault Tolerant is selected. 3. Update the following settings from the FT Group Settings pane as required: Heartbeat Interval (ms) The heartbeat interval determines the time (in milliseconds) between heartbeat messages. Activation Interval (ms) A standard TIBCO Rendezvous fault tolerant parameter. The Heartbeat Interval should be smaller than the Preparation Interval, which should be smaller than the Activation interval. It is recommended that Activation Interval be slightly over 2 heartbeats. Preparation Interval (ms) A standard TIBCO Rendezvous fault tolerant parameter 4. Click Save. You are now ready to deploy TIBCO EM Advisor in a fault-tolerant setting.
| 29
Chapter 3
TIBCO Enterprise Management Advisor Components
Topics
Overview, page 30 EMA Agent, page 31 EM Advisor Console, page 35 All Alerts Console, page 52 EMA ConfigUI, page 55 Using TIBCO EM Advisor with External EM Platforms, page 62
30
| Chapter 3
Overview
This chapter describes the functional components of TIBCO EM Advisor. EMA Agent EMA Agent discovers the managed objects in the TIBCO EM Advisor domain and determines the dependencies and relationships for applications deployed by TIBCO Administrator. The dependencies and relationships between managed objects is determined by analyzing the deployment data stored within TIBCO Administrator. EM Advisor Console This component graphically represents the dependency model generated by EMA Agent within the TIBCO Administrator browser interface. You can navigate the dependency model, inspect the managed objects and view the impact of alerts occurring anywhere within the domain. EMA ConfigUI EMAConfigUI is used to create additional configuration information, such as defining dependencies between managed object. EMA ConfigUI uses information made available by EMA Agent and organizes it into the Enterprise Domain and Discovered Domains tabs. Using TIBCO EM Advisor with External EM Platforms This section describes the use of TIBCO EM Advisor with external EM Platforms, the metrics that are provided, the methods that are exposed to interact with the managed objects and the handling of events and notifications.
The sections in this chapter use a sample deployment which consists of EMA-domain1 as the Enterprise domain and mmdomain1 and the additional TIBCO Hawk domain being monitored. TIBCO EM Advisor has been deployed in the EMA-domain1 domain. Also deployed in this domain is an application
FileAdapter-Simple
EMA Agent 31
EMA Agent
The TIBCO EM Advisor domain consists of managed objects contained in the Enterprise Domain, which is your TIBCO Administrator domain, and any additional TIBCO Hawk domains, referred to as Discovered Domains, that you may wish to monitor.
Representation of Managed Objects

EMA Agent automatically determines the managed object dependencies and relationships for applications deployed by TIBCO Administrator by analyzing the deployment data stored within TIBCO Administrator. The deployment data includes the defined relationships and dependencies between managed objects, deployment configuration information, and any external services created by the applications. The dependency information for a business process or an adapter configuration is determined during the design process. However, the binding of the business process or the adapter configuration to a specific component instance or external service is specified during the deployment process where the global variables are set and the configurations are bound to physical engine or adapter instances. Service groups for load balancing and fault tolerance are also determined at the time of deployment. Any custom applications not deployed by TIBCO Administrator are discovered by EMA Agent uses the microagent name patterns described in the <microagentDiscoveryRuleList> element of default_config.xml. For more information, see microagentDiscoveryRuleList on page 90. The managed objects in the Discovered domain are discovered by EMA Agent using the defined microagent discovery rules. Dependencies between managed objects in the Discovered domain and any external services used have to be created manually using EMA ConfigUI. For more details on EMA ConfigUI, see EMA ConfigUI on page 55. EMA Agent creates a hierarchical tree of the managed objects in the TIBCO EM Advisor domain. This tree can be perused using the EM Advisor Console component. For details, see EM Advisor Console on page 35.
If a new application is deployed after you start EMA Agent, you need to re-start EMA Agent for that application to be discovered. For applications deployed by TIBCO Administrator, runtime dependencies are not analyzed.
32
| Chapter 3
Dependency Model
During model generation the configuration information contained in the Enterprise Archive (EAR) file is combined with the deployment binding information in order to build the dependency relationships. The dependency model will be re-generated when EMA Agent starts if EMA Agent detects that any change has happened to the deployment since the last time the model was built. TIBCO Servers The TIBCOServers folder is populated with all deployed applications that are members of the TIBCO Servers application group. These applications are part of the TIBCO infrastructure and are typically shared by all user-defined applications. Application instances that are included in this group include the following: TIBCO Administration server TIBCO EMS server TIBCO Workflow server TIBCO Rendezvous daemon
The TIBCO Rendezvous daemons are grouped according to UDP service port number in order to provide a single folder that represents the virtual communication service provided by all daemons participating in group.
Adapter Services The deployment of an adapter configuration results in an adapter instance on the deployed node. Each adapter instance along with the system to which the adapter is connected is responsible for providing a service. This is reflected by the creation of an Adapter Service to represent the service being provided. The adapter service will be dependent upon the adapter instance as well as the system to which the adapter is connected. Furthermore, the adapter service may also be dependent upon infrastructure components that the adapter or connected system depends. Adapter Service Groups are created to represent the deployment of an adapter configuration on multiple nodes. This scenario may be for fault-tolerance or load-balancing purposes. The adapter service is made dependent on the service group instead of the service instance in order to reflect that there is more than one adapter instance providing the necessary service.
EMA Agent 33
Business Processes The deployment of a process archive results in a TIBCO BusinessWorks engine instance on the deployed node. The process archive is responsible for providing a business service. This is reflected by the creation of a Business Process Service to represent the service being provided. The business process service is dependent upon the TIBCO BusinessWorks engine on which it is deployed. Each business process consists of several distinct activities. Each activity may depend upon some adapter service, external system, or service to be available in order to function. Furthermore, the activity may also depend on some messaging component for communication with the adapter service. The business process may also call other business processes. Circular dependencies (i.e. recursive process calls) are detected and eliminated so that the resulting dependency graph has no cycles. Business Process Service Groups are created to represent the deployment of a process archive on multiple nodes. This scenario may be for fault-tolerance or load-balancing purposes. The process archive is made dependent on the service group instead of the service instance in order to reflect that there is more than one adapter instance providing the necessary service. Shared Resources Shared resources represent common connection information for various systems and services used by business process activities and adapter configurations. The shared resources are mapped to internal services under the TIBCOServers folder or external services under the External Services folder. The following shared connection types are mapped to the TIBCOServers folder: Rendezvous transport EMS
The following shared connection types are mapped to the External Services folder: EJB FTP HTTP TCP JDBC Workflow IM Engine
34
| Chapter 3
JNDI
Integrating with TIBCO BusinessWorks

As mentioned in the earlier section, the managed objects within TIBCO EM Advisors domain also include TIBCO BusinessWorks processes. While generating the dependency model, EMA Agent shares information with TIBCO BusinessWorks about the resources (managed objects) that the process definitions of these business processes depend on. TIBCO EM Advisor sends notifications about the status of these managed objects to TIBCO BusinessWorks. The status of the managed object is based on the Hawk alert generated by the TIBCO Hawk agent associated with the managed object. When any managed object generates a high alert, TIBCO BusinessWorks suspends (blocks) execution of the processes that depend on that managed object. The process is re-started after the alert status of the managed object is cleared. If the TIBCO BusinessWorks process has multiple paths, the process will be blocked (in case of an high alert) if all paths in the process are impacted. This integration between TIBCO EM Advisor and TIBCO BusinessWorks simplifies exception handling in process definitions. To enable TIBCO EM Advisor integration with TIBCO BusinessWorks, the following customized properties must be set to true:
bw.engine.emaEnabled Hawk.enabled.
and
Additionally, ensure that EMA Agent is running before the TIBCO BusinessWorks applications are deployed.
EM Advisor Console 35
EM Advisor Console
EMA Agent creates a dependency model of the managed objects in the TIBCO EM Advisor domain. This model is represented by a hierarchical tree that describes the relationships and dependencies between the managed objects in the domain. EM Advisor Console is the tool is used to navigate through the domain, inspect the managed objects and view the impact of alerts occurring anywhere within the domain. This console is accessed by clicking Monitoring Management>EM Advisor Console from the left-hand pane of TIBCO Administrator. The following figure shows an EM Advisor Console screen for the sample application. The Enterprise domain is EMA-domain1 and mmdomain1 is the additional Hawk domain being monitored.
When using EM Advisor Console or All Alerts console, your TIBCO Administrator session will never timeout. You need to explicitly log out of your session.
36
| Chapter 3
Navigating Through the Domain

The EM Advisor Console screen is divided into the navigational panel on the left and the graphical panel on the right. The root node of the hierarchical tree is TIBCORoot. Contained within this node is a folder for the Enterprise Domain and each Discovered Domain. The Enterprise Domain is your TIBCO Administrator domain. Within these folders the managed objects are organized into the following sub-folders: Machines All Applications This folder contains the following: TIBCOServers: contains the TIBCO infrastructure components including the messaging components of the domain. External Services: contains any external services used by the domain. Discovered Services: contains any managed objects corresponding to custom applications that are discovered by EMA Agent. Applications deployed in this domain. There is a separate folder for each application. The folder for an application contains the services instances, any Adapter services used, and the business processes belonging to the application. The graphical panel and the navigational panel are always synchronized. Any selections made to one panel are reflected in the other. In the hierarchical tree, the solid lines connect managed objects to denote containment and the dashed-lines denote dependencies. EM Advisor Console represents each managed object type is represented by a different icon. For a list of the managed objects types and their icons, see Appendix B on page 101.
Navigational Panel The navigational panel shows relations between managed objects. Both containment and dependency relations between managed objects are shown. Dependency relations are shown in italics. The following figure shows a the navigational panel of EM Advisor Console for our sample application.
The following figure shows the information contained in the navigational panel for a managed object.
Managed object status Alert status of the corresponding TIBCO Hawk agent. Managed object name. If this name is underlined, you can drilldown from this managed object. Managed object type
Expand and collapse option.
38
| Chapter 3
Graphical Panel The graphical panel shows managed objects along with their containment and dependency information, and any TIBCO Hawk alerts generated within the domain. In the following figure, the emaagent managed object (type: EMAdvisor) is contained within the EMAdvisor managed object (type: Deployment) and is dependant on the pprasad-nb managed object (type:Machine).
Viewing the tooltip Moving the mouse over a managed object in the graphical panel displays the tooltip for that managed object. The following figure shows the tooltip for the managed object Spot-schalla-lt.
The following figure shows the information contained within a managed object icon in the graphical panel.
To select a managed object, click anywhere within this rectangular area. Managed object type Managed object status The border color signifies the highest alert level of the this managed objects dependencies.
Alert status of the corresponding TIBCO Hawk agent. Managed object name. If this name is underlined, you can drilldown from this managed object.
Expand and collapse option.
Expanding and collapsing the tree You can expand or collapse the hierarchical tree by clicking the small + or - icons which are located below the managed object. In the navigational panel the + and icons precede the managed object name.
40
| Chapter 3
Highlighting the relevance of a managed object Click on a managed object in the graphical panel to highlight the relevance of that managed object. Also highlighted is the impact path up to the root node as well as its containment and dependencies links. You can select more than one managed object to view the combined relevance of the selected nodes. From the navigational panel, you select the checkbox located next to the managed object. The following figure shows the containment and dependency links of the FileAdapterPublisher managed object belonging to the FileAdapterApp application.
Controls for the graphical panel The following controls located at the bottom of the graphical panel:
Zoom out. Click this icon to display more of the view of the hierarchical tree. Pan. Click this button to move the graphical view to a different location. Zoom in. Click this icon to magnify the view of the hierarchical tree. Sets the root of the hierarchical tree to the chosen node. This control is enabled only when one node is chosen. Select a node and click this button to expand the entire tree.
Resets the root of the hierarchical tree to Re-sizes the tree TIBCORoot. This control to fit the size of is enabled only after the the graphical Set Root control has been panel. previously used.
Click this button to ensure that siblings are displayed at the same . level when the tree is rendered.
Additional controls The following controls are located on the top-right corner of the graphical panel:
Click this button to access the online help for EM Advisor Console.
Click this button to tear-off the EM Advisor Console and view it in a separate window.
Click this button to access the security dialog for EM Advisor Console.
42
| Chapter 3
Alerts Any alert generated by the TIBCO Hawk agent corresponding to the managed object is displayed. The color of the managed object icon reflects that of the alert. The colors are either yellow, amber, or red representing low, medium, or high alerts respectively. Within the managed object icon, alerts are additionally represented by a series of alert icons. The color of these icons reflect the color of the managed object. Table 4 Alert Icons Icon Description
There are no alerts generated.
Low alert.
Medium alert.
High alert.
Unable to communicate with the TIBCO Hawk Agent.
Also, the impact of the alert is traced up to the root of the tree. The color of the impact path too reflects the color of the alert. When there are multiple alerts, the impact path takes the color of the highest alert occurring along that path.
The following figure shows alerts generated with the EMA-domain1 and mmdomain1 of the sample application being traced up to the root.
To view all the alerts generated within the TIBCO EM Advisor domain, from the TIBCO Administrator left pane select Monitoring Management>All Alerts. For more details see, All Alerts Console on page 52.
44
| Chapter 3
Status of a managed object Table 5 lists the icons that represent the status of a managed object in EM Advisor Console. Unlike alerts, the status of the managed object is not propagated along the impact path. Table 5 Icons Representing Status of a Managed Object Icon Description
Ok.
Starting
Stopping
Stopped
Error
Down
Unknown
Invoking TIBCO Hawk methods for a managed object From either navigational or graphical panel, clicking on a managed object directs you to the panel from where you can invoke TIBCO Hawk methods. For more information, see Invoking TIBCO Hawk Microagent Methods on page 49.
Managed objects such as Folders, External Services do not have corresponding TIBCO Hawk agents. You can only drill down from objects that have their names underlined as a link. Viewing the Process Diagram You can view the BusinessWorks process diagram for managed objects that represent business processes. To do this, first click on the managed object represented by the icon and then choose the Process Diagram tab. The following figure shows a sample process diagram.
The following controls are located at the bottom of the pane that displays the process diagram:
Zoom out. Click this icon to display more of the view of the hierarchical tree. Pan. Click this button to move the graphical view to a different location. Zoom in. Click this icon to magnify the view of the hierarchical tree.
Re-sizes the tree to fit the size of the graphical panel.
46
| Chapter 3
Security
Security access determines whether a user can perform an operation on a managed object in your domain.TIBCO Administrator users that have Administrator access can access all managed objects and also drill down and invoke microagent methods on them. Table 6 on page 46 lists the TIBCO Administrator access required for the EM Advisor Console functionality. Table 6 TIBCO Administrator Access for EM Advisor Console Functionality User Access Machines
Does not have any access permissions. Cannot access EM Advisor Console and consequently cannot access or invoke methods. User can drill down from EM Advisor Console but the list of microagents will be empty. User can drill down from EM Advisor Console and access microagent methods. Cannot access EM Advisor Console and consequently cannot access or invoke methods. User can drill down from EM Advisor Console but the list of microagents will be empty. User can drill down from EM Advisor Console and access microagent methods.
Enterprise Domain
Discovered Domain(s)
Read or Read-Administer
ReadWrite or Read-Write-Administer
Service Instances and TIBCO Servers managed by TIBCO Administrator

Does not have any access permissions. Cannot access EM Advisor Console and consequently cannot access or invoke methods. User can drill down from EM Advisor Console but the list of microagent methods for the specific service instance or TIBCO Server will be empty. User can drill down from EM Advisor Console and access and invoke microagent methods for the specific service instance or TIBCO Server. N/A
Read or Read-Administer
N/A
ReadWrite or Read-Write-Administer
N/A
Table 6 TIBCO Administrator Access for EM Advisor Console Functionality User Access Enterprise Domain Discovered Domain(s)
Discovered Services and TIBCO Servers not managed by TIBCO Administrator

Does not have any access to EM Advisor Console. EM Advisor is not listed under Application Management and cannot be accessed. User can drill down from EM Advisor Console but cannot invoke or access microagent methods. User can drill down from EM Advisor Console and access and invoke microagent methods. EM Advisor is not listed under Application Management and cannot be accessed. User can drill down from EM Advisor Console but cannot invoke or access microagent methods. User can drill down from EM Advisor Console and access microagent methods.
Read or Read-Administer for EM Advisor Console.
ReadWrite or Read-Write-Administer for EM Advisor Console.
It is strongly recommended that only administrators have access to the All Alerts console and EM Advisor Console.
Security between TIBCO Administrator and TIBCO Runtime Agent. Security is enabled between TIBCO Administrator and TIBCO Runtime Agent by specifying a Java class that implements your security policy. For the Enterprise domain this security policy is specified by the -security_policy option in the hawkagent.cfg configuration file. This configuration file is located in: For TIBCO Hawk users this file is located in <TIBCO Hawk installation directory>/bin For TIBCO Runtime Agent users the location of the hawkagent.cfg file is pointed by the value of the command line argument applications.args contained in the file:
<TIBCO TRA installation directory>\domain\< TIBCO Administrator domain name>\hawkagent_< TIBCO Administrator domain name>.tra
For other TIBCO Hawk domains, the security policy is specified by the field Hawk Security Impl when you specify parameters to access the additional domains. See Hawk Domains on page 15 for details.
48
| Chapter 3
When invoking or subscribing to TIBCO Hawk microagent methods, the security that is enforced is based on the user that started the TIBCO Administrator server and not the user accessing TIBCO Hawk microagent methods. For more information on TIBCO Hawk security see TIBCO Hawk Installation and Configuration Guide.
Invoking TIBCO Hawk Microagent Methods

To invoke microagent methods, click on a managed object from either the graphical or navigational panel of EM Advisor Console. The names of the managed objects on which you can invoke microagent methods are underlined. For managed objects of type machine, the Agent tab lists the available microagents. Click on a microagent to view the list of available microagent methods. For more information, see Agent Tab on page 49. For managed objects corresponding to instances of TIBCO Software components, the microagent methods are listed in the Methods tab of the service instance. For more information, see Hawk microagent methods on page 49. See Security on page 46 for the access permissions required to able to drill-down and access micoragents and microagent methods. Agent Tab This dialog lists the available microagent and the rulebases defined for the agent. Microagents Displays the available microagents. Name Name of the microagent. Instance Number to identify the running instance Description Description of the microagent.
Click on a microagent name for the list of associated microagent methods. Rulebases A list of the loaded rulebases is displayed. Rulebases The name of the rulebase. Click on this field to sort the rulebase names. Click on a rulebase name to view details of the rulebase. Hawk microagent methods This dialog lists the available microagent methods. You can choose to display only those microagent methods that match a search criteria. You can use the * character as a wildcard.
50
| Chapter 3
Methods The following fields are displayed for the microagent methods: Name Name of the microagent methods. Description Description of the microagent method.
To invoke a microagent method click on the method name. See Invoke microagent methods for details. Invoke microagent methods This dialog displays information about the microagent method and provides fields you can specify input parameters when either invoking or subscribing to the method. Method Displays general information about the microagent method: Name The name of the microagent method. Description Description of the microagent method. Type Type of the microagent method, either Synchronous or Asynchronous. Impact The function performed by the method and can be one of the following types:
IMPACT_INFO
returns information. performs an action on the TIBCO Hawk system. both returns information and performs an action
IMPACT_ACTION
IMPACT_ACTION_INFO
based on it. Time Out The method invocation timeout value in milliseconds.
Invocation Parameters Displays the following elements for the parameters: Name Name of the input argument. Value Value of the input argument. Type Data type of the argument. Description Description of the argument.
Subscribe Available for methods of type IMPACT_INFO and IMPACT_ACTION_INFO. You cannot subscribe to methods of type IMPACT_ACTION. Information is returned by the method either synchronously or asynchronously. If the Subscribe checkbox is selected, the following fields are displayed along with the default values: Data Interval The time interval for collection data points. Available when subscribing to synchronous methods. History The number of data points you want to see for historical data set. Even though a method may return data asynchronously, the result will not be updated until the page is refreshed.
52
| Chapter 3
All Alerts Console

You can view all TIBCO Hawk alerts generated in your TIBCO EM Advisor domain in this console. Here you can specify search conditions to filter the alerts that are displayed. This console is accessed by clicking Monitoring Management>All Alerts from the left-hand pane of TIBCO Administrator.
To access the All Alerts console, you must have read access for it.
Alerts Domain Choose from the All,Custom, or a domain that belongs to the TIBCO EM Advisor environment. State Choose either Any, Active, Cleared, or Custom. Add Search Condition The following options are available: Date/Time Specify the date and time before or after which you want to filter the alerts. Level Lowest level of the alert. Possible choices are High, Medium, Low, Notification or Custom. This level indicates the lowest alert level that you want to search for. For example, if you choose medium, both medium and high alerts will be displayed and if you choose low, all alerts will be displayed. Agent Name of the agent. Rulebase Name of the rulebase that generated the alert. Deployment Name of the deployment. Component Instance Name of the component.
When more than one selection condition can be specified, one of the following options must also be chosen: Show entries where ALL conditions are true Show entries where ANY conditions are true
Search Click this button to apply the chosen search conditions to the list of generated alerts.
All Alerts Console 53
Purge Cleared Alerts Used to purged alerts that have been cleared.
Alerts that are cleared will stay in the list for 30 minutes if user does not click the purge alert button.
List of Alerts For each alert, the following information is displayed: Date/ Time Date and Time of the alert. Domain The domain where this alert orginated. Cleared Whether this alert has been cleared. If the alert is cleared a X is displayed in this column. Alert Level Level of the alert represented by the alert icons. Table 4, Alert Icons, on page 42 list the alert icons. Text Text belonging to the alert. detail Click on this field to view details about the generated alert. Alert Details This dialog lists details of the chosen alert. Details Date/ Time Date and Time of the alert. Alert Level Level of the alert represented by the alert icons. Table 4, Alert Icons, on page 42 list the alert icons. Text Text belonging to the alert. Properties Domain The domain where this alert orginated. Agent The TIBCO Hawk Agent which generated this alert. Rulebase The TIBCO Hawk rulebase which generated this alert. DataIndex If the alert was generated from a rule with composite data sources, this value is _. If the alert was generated from a rule with a tabular data source, this value is _<indexField>:<indexValue>. Where <indexField> and indexValue> refer to values in the tabular data source.
54
| Chapter 3
Action The number corresponding to its position in the action list for the test as defined in the rulebase. Rule The rule which uses the specified datasource to test for certain conditions. DataSource The datasource for the rulebase. Test The test performed on the datasource. The following properties are displayed if a rulebase is configured for a service instance through TIBCO Administrator. Action.Deployment The deployment name of the service instance. Action.ComponentInstance The name of the service instance. Action.ComponentInstanceID The ID of the service instance. Suspend Reason The reason for suspending the alert. Suspend Interval The duration in seconds for which the alert should be suspended. Suspend Click this button to suspend the alert. For more information on suspending alerts, refer to TIBCO Hawk Administrators Guide.
Only users with write access can suspend alerts. Users with read access can only view alerts.
EMA ConfigUI 55
EMA ConfigUI
EMAConfigUI is used to create additional configuration information, such as defining dependencies between managed object. EMA ConfigUI uses information made available by EMA Agent and organizes it into the Enterprise Domain and Discovered Domains tabs. The following figure shows the Enterprise domain tab of EMA ConfigUI for the sample application. The root of the tree structure is EMA-domain1 which is the TIBCO Administrator domain of the sample application.
Starting EMA ConfigUI You can start the EMA ConfigUI by invoking the following command: Microsoft Windows Invoke from the command-line or double-click the file:
<TIBCO_HOME>\tra\domain\<domain_name>\application\<EM Advisor deployment name>\EMAdvisor_emaconfigui.cmd
56
| Chapter 3
Where, <TIBCO_HOME> is your TIBCO installation directory, <domain_name> is the name of the TIBCO Administrator domain where you have TIBCO EM Advisor deployed, and <EM Advisor deployment name> is the name specified for this TIBCO EM Advisor deployment and is EMAdvisor by default. UNIX
<TIBCO_HOME>/tra/domain/<domain_name>/application/<EM Advisor deployment name>/EMAdvisor_emaconfigui.cmd
Where, <TIBCO_HOME> is your TIBCO installation directory, <domain_name> is the name of the TIBCO Administrator domain where you have TIBCO EM Advisor deployed, and <EM Advisor deployment name> is the name specified for this TIBCO EM Advisor deployment and is EMAdvisor by default. The following sections describe the steps involved in: Configuring Service Instances, page 57 Deleting Service Instances, page 57 Defining and Deleting Dependencies, page 57 Adding and Deleting an External Service, page 60
With the exception deleting a service instance that is discovered in the Enterprise domain, all operations are performed on managed objects in the Discovered domains.
EMA ConfigUI 57
Configuring Service Instances

Service instances are instances of managed objects in the domain. To update the configuration data for service instances in the Discovered domain: 1. Expand the folders belonging to the discovered domain to display the specific instances of the managed objects. 2. Click on the service instance to display the configuration information. 3. Update the data displayed on the right-hand panel 4. Click Apply Changes.
Deleting Service Instances

To delete any service instance from any domain, right click on the service instance and choose Delete. Of the service instances in the Enterprise domain, you can only delete services corresponding to customs applications that are discovered by EMA Agent. If you delete a service instance for say, a RVD process, from your Discovered domain, this service instance will be re-discovered when you re-start EMA Agent. If you do not want to re-discover that service instance, either stop the process or in the case of custom applications, edit the microagent discovery rules such that the application is not discovered.
Defining and Deleting Dependencies

The Dependency Details sub-panel describes the dependencies between the selected instance of a managed object and other managed object instances. Defining Dependencies To define a new dependency for a service instance: 1. Select the service instance.
58
| Chapter 3
2. Click Add, to define a new dependency. The following pop-up window displays:
This window displays the available instances of managed objects for defining dependencies. 3. Select a service instance. 4. Click OK.
EMA ConfigUI 59
The Dependency Details sub-panel now displays the updated dependency information.
Deleting a Dependency To delete a dependency, select the dependency in the Dependency details sub-panel and click the Delete button. The dependency is now deleted from your deployment.
60
| Chapter 3
Adding and Deleting an External Service

Typically, an external service is a non-TIBCO software component such as a database or R/3 SAP system. Such an external service is not discovered by the EMA Agent and needs to be added manually. Adding an External Service To add an external service to the TIBCO EM Advisor domain: 1. Select Edit>Add External Service. 2. Type Name, Version, description, Host Name and Connection URL for the new service. The Connection URL field is used by the EM platform to access the external service components. For example, if the external service is a directory on the local machine, the Connection URL could be logdir=c:\Logs In this example, hk-win06 is the Host Name and will be used.
c:\Logs is the directory that
3. Click OK. A new external service is now created and added to the tree-view of the domain on the left-hand panel. You can use this service when defining dependencies.
EMA ConfigUI 61
When adding External Services, ensure that you do not have multiple instances of managed objects with the same name in one deployment. Deleting an External Service To delete a ExternalService, select the service by clicking on it, then right-click and select Delete. The selected ExternalService is now deleted from the deployment.
62
| Chapter 3
Using TIBCO EM Advisor with External EM Platforms

EMA Agent is the software component that bridges the gap between EM applications and the TIBCO environment. EMA Agent presents a complete and detailed representation of all TIBCO software components to the EM world. This includes describing the managed objects, their relationships and dependencies and the non-TIBCO managed objects. Knowing the dependencies between managed objects is beneficial because they tell us which other managed objects are likely to be impacted in case any one managed object fails.
Metrics
Gathering performance metrics of the business processes and the resources that support them are crucial in determining whether SLAs have been met. These metrics provide the factual data required to support SLAs. Performance metrics define the overall state of the domain. This state can be broken down into the states of individual resources, which in the context of TIBCO EM Advisor are its managed objects. The EM platform utilizes these metrics to perform analysis such as, observing how resources are performing, where changes are likely required, or which resources are getting overloaded and could potentially be a single point of failure. Each installed TIBCO software component exposes methods which provide its performance metrics. Using the <metricConfigurationList> element defined in the default_config.xml file you can specify the metrics belonging to which TIBCO software component you want to collect. Additionally, you can also specify the type of the metric. The metric types supported are accumulated, delta, snapshot, and rate. For more information, see metricConfigurationList on page 95. If you have custom applications deployed in your domain and have specified rules to discover them in the custom_config.xml file, any metrics that you wish to collect for those applications must be defined in custom_config.xml using the <metricConfigurationList> element. If the <metricConfigurationList> element has not been defined, the only metrics made available are the TIBCO Rendezvous metrics. The following data values are collected: Messages Sent Messages Received Bytes Sent Bytes Received
Using TIBCO EM Advisor with External EM Platforms 63
Packets Sent Packets Received Retransmitted Packets Missed Packets Messages Sent Rate Messages Received Rate Bytes Sent Rate Bytes Received Rate Packets Sent Rate Packets Received Rate Percent Retransmitted Packets Percent Missed Packets
The TIBCO Rendezvous metrics are accumulated from the time the TIBCO Rendezvous daemon (rvd) process was first started. The data collection interval is specified by the parameter <rvDeamonStatisticsCollectionInterval> in the custom_config.xml configuration file. Appendix A, Sample Configuration Files, on page 87 lists a sample custom_config.xml file. The TIBCO Hawk microagent RvdServiceMa helps provide metrics for TIBCO Rendezvous. See Configuring TIBCO Hawk Microagent Plugin RvdServiceMA on page 20 for instructions on installing this microagent. To collect metrics for TIBCO EMS servers, additional classes need to be loaded into the TIBCO Hawk agent. See Administering TIBCO EMS Servers on page 23 for more information.
External EM Events
Typically, business processes are dependant on resources spread over multiple systems. TIBCO EM Advisor enables you to build relationships between resources and the business processes they support. It is crucial for business processes to act either proactively or with minimal impact on productivity to any slide in the performance of the involved resources. As a result, aiding communication between all resources managed and monitored by the EM platform becomes important.
64
| Chapter 3
Within the context of TIBCO Enterprise Management Advisor, External EM events are events received from the EM platform. External EM events facilitate communication between managed objects belonging to the TIBCO EM Advisor domain and managed objects external to the TIBCO EM Advisor domain. External EM events map to the Service Effect Analysis (SEA) events of HP OpenView. External EM events are made available to your TIBCO EM Advisor domain using either JMS or TIBCO Rendezvous. For more information see External Web Services, page 17. The following sample scenario further describes External EM Events. Sample Scenario EMA Agent makes available to the EM platform the performance metrics of the managed objects in its domain. The EM platform notices that the performance of a resource is degrading or deviating from the standard, such as a disk running low on diskspace or certain operations timing-out frequently. This information is relayed in the form of an External EM event. EMA Agent parses such a message and publishes it using a pre-defined subject. A message published on that subject could be used by applications within the TIBCO EM Advisor domain to either initiate execution of specific tasks or modify the sequence of activities to proactively address performance issues. External EM Event Message Format Following is part of a sample External EM event message received by EMA Agent:
<wsev:NotificationList> <wsev:Notification Id="urn:event-0000000000000000003"> <wsev:Source>http://hpdemo1.tibco.com:8090/wsmf/services/AIA_DEF AULT?wsdl</wsev:Source> <wsev:Type>http://hpdemo1.tibco.com:8090/wsmf/services/AIA_DEFAU LT?wsdl/AIA_DEFAULT/testCPU</wsev:Type> <wsev:CreatedOn>2005-01-02T21:45:24Z</wsev:CreatedOn> <wsev:ExpiresOn>2005-01-02T21:45:24Z</wsev:ExpiresOn> <aia:AIANotification xmlns:aia="http://schemas.hp.com/wsmf/2003/03/Events#Extension#AIA Notification"> <aia:Severity>CRITICAL</aia:Severity> <aia:Message>Testing</aia:Message> <aia:NodeName>hpdemo1.tibco.com</aia:NodeName> <aia:CorrectiveMessage /> <aia:Application>OSSPI</aia:Application> <aia:Object>CPU</aia:Object> <aia:ImpactPathList /> </aia:AIANotification> </wsev:Notification>
Notifications
EMA Agent notifies the EM platform any changes in the state of its managed objects. The types of notifications are: Alerts Alerts are messages sent by TIBCO Hawk agents when a specific condition occurs. Any alert generated within TIBCO Enterprise Management Advisors domain is sent to the EM platform. You can filter alerts using the <alertFilterThreshold> element of the default_config.xml. The following is a sample alert notification sent by EMA Agent:
<wsev:Notification wsev:Id="ZHILI-NB:none:2438"> <wsev:Source>http://ZHILI-NB.na.tibco.com:8888/?wsdl:objid=tib ema%3A%2F%2Fwww.tibco.com%2Fema%2F2005%2F01%2Fmo%2Fidentity%2FMach ine%2FZHILI-NB%2FZHILI-NB </wsev:Source> <wsev:Type>http://www.tibco.com/ema/2005/01/event/alert</wsev: Type> <wsev:CreatedOn>2005-01-25T17:02:50.012Z</wsev:CreatedOn> <wsev:ExpiresOn>2006-01-25T17:02:50.012Z</wsev:ExpiresOn> <mgmt:ManagementNotification> <mgmt:Severity>Warning</mgmt:Severity> <mgmt:Message> 54786485 = 54786485 </mgmt:Message> <mgmt:CorrectiveMessage/> <mgmt:ResourceHostName>zhili-nb.na.tibco.com</mgmt:ResourceHos tName> <mgmt:ApplicationName>COM.TIBCO.hawk.microagent.Self:0</mgmt:A pplicationName> </mgmt:ManagementNotification> </wsev:Notification>
RelationshipsChanged A relationship is defined in terms of the dependencies between managed objects and is configured using EMA ConfigUI. Any change to the relationship of a managed object with the other managed objects in the domain, such as adding or deleting dependencies, is communicated to the EM platform. The following is a sample RelationShipsChanged notification sent by EMA Agent:
<wsev:Notification> <wsev:Source>http://zhili-nb.tibco.com:8888/?wsdl:objid=tibema% 3A%2F%2Fwww.tibco.com%2Fema%2F2005%2F01%2Fmo%2Fidentity%2FDeployme nt%2Fmmdomain1%2FExternal_Services</wsev:Source> <wsev:Type>http://schemas.hp.com/wsmf/2003/03/Foundation/Event/ RelationshipsChanged</wsev:Type> <wsev:CreatedOn>2005-02-14T23:39:30.221Z</wsev:CreatedOn> <wsev:ExpiresOn>2006-02-14T23:39:30.221Z</wsev:ExpiresOn> <mgmt:ManagementRelationNotification> <mgmt:RelationType>RelationCreate</mgmt:RelationType>
66
| Chapter 3
<core:RelationshipList><core:Relationship> <core:HowRelated>http://schemas.hp.com/wsmf/2003/03/Relations/ Contains</core:HowRelated> <core:RelatedObject>http://zhili-nb.tibco.com:8888/?wsdl:objid =tibema%3A%2F%2Fwww.tibco.com%2Fema%2F2005%2F01%2Fmo%2Fidentity%2F ExternalService%2Fmmdomain1%2Fjdbc%3Amysql%3A%2F%2Flocalhost%3A330 6%2Ftest</core:RelatedObject> </core:Relationship> <core:Relationship><core:HowRelated>http://schemas.hp.com/wsmf /2003/03/Relations/Contains</core:HowRelated> <core:RelatedObject>http://zhili-nb.tibco.com:8888/?wsdl:objid=tib ema%3A%2F%2Fwww.tibco.com%2Fema%2F2005%2F01%2Fmo%2Fidentity%2FExte rnalService%2Fmmdomain1%2Fjdbc%3Amysql%3A%2F%2Flocalhost%3A3306%2F test</core:RelatedObject> </core:Relationship> </core:RelationshipList> </mgmt:ManagementRelationNotification> </wsev:Notification>
StatusChange Any change in the status of an managed object is captured and sent as an StatusChange notification. The severity level of the status notification is CRITICAL when the status changes from UP to DOWN and NORMAL when the status changes from DOWN to UP. The following is a sample Statuschange notification sent by EMA Agent:
<wsev:Notification> <wsev:Id="tibema://www.tibco.com/ema/2005/01/mo/identity/Service Instance/ZHILI-NB/Discovered_Services/Spot-ZHILI-NB"> <wsev:Source>http://zhili-nb.na.tibco.com:8888/?wsdl:objid=tibema% 3A%2F%2Fwww.tibco.com%2Fema%2F2005%2F01%2Fmo%2Fidentity%2FServiceI nstance%2FZHILI-NB%2FDiscovered_Services%2FSpot-ZHILI-NB</wsev:Sou rce> <wsev:Type>http://www.tibco.com/ema/2005/01/event/StatusChange</ wsev:Type> <wsev:CreatedOn>2005-01-28T21:25:04.085Z</wsev:CreatedOn> <wsev:ExpiresOn>2006-01-28T21:25:04.085Z</wsev:ExpiresOn> <mgmt:ManagementNotification> <mgmt:Severity>Critical</mgmt:Severity>
Available Methods
EMA Agent exposes the following methods for interacting with the managed objects in its domain. In addition, methods standard to the EM vendor specification are also available. Table 7 TIBCO Enterprise Management Advisor Methods (Sheet 1 of 4) Managed Object Type
All managed objects GetType GetName Returns the type of this managed object. Returns the name assigned to the managed object. Returns the version number associated with this managed object. Returns the management WSDL URL for this managed object. Returns a strings describing this managed object. Returns the owner of this managed object. Returns the vendor of this managed object. Returns the resource version of the underlying resource. Returns the version number of this managed object. Returns the date on which this managed object was created. Returns the current status of this managed object. Returns the list of relationships that are currently active for this managed object. Returns the list of relationships supported for this managed object.
Method Name
Description
GetVersion
GetManagementWsdlUrl
GetDescription
GetOwner GetVendor GetResourceVersion
GetManagedObjectVersion
GetCreatedOn
GetStatus
GetRelationships
GetSupportedRelationhips
68
| Chapter 3
Table 7 TIBCO Enterprise Management Advisor Methods (Sheet 2 of 4) Managed Object Type Method Name
GetSpecificRelationships
Description
Returns the list of relationships having a specific relationship with another managed object. Returns the list of events supported for this managed object. This operation provides a way to register a desire to receive a callback when any of a list of event types occur. This operation indicates the desire to stop receiving callbacks for previously registered subscriptions. Returns the fully qualified host name on which this managed object is running. Returns the host name for this managed object.
GetSupportedEventTypes
PushSubscribe
CancelSubscription
GetResourceHostName
GetManagedObjectHostName
On machines having multiple interfaces, the methods GetResourceHostName and GetManagedObjectHostName may not return the fully qualified host name.
Host getPlatform Returns the name of the operating system platform.
Table 7 TIBCO Enterprise Management Advisor Methods (Sheet 3 of 4) Managed Object Type
JMS Server getResourceIP Returns the IP address of the host on which this managed object is running. Return all metric definitions of this managed object. Return all metric values for this managed object. Return a list of metric categories. Return a particular metric definition. Return all metric values for the given category. Return a particular metric value Return all metric values for the given category
Method Name
Description
GetMetricDefinitions
GetMetricValues
GetMetricDefinitionCategories GetMetricDefinitionByName GetMetricDefinitionByCategory
GetMetricValueByName GetMetricValuesByCategory
RVD and RVRD getResourceIP Returns the IP address of the host on which this managed object is running. Returns the service port for this managed object. Return all metric definitions of this managed object. Return all metric values for this managed object. Return a list of metric categories. Return a particular metric definition. Return all metric values for the given category. Return a particular metric value
getServicePort
GetMetricDefinitions
GetMetricValues
GetMetricDefinitionCategories GetMetricDefinitionByName GetMetricDefinitionByCategory
GetMetricValueByName
70
| Chapter 3
Table 7 TIBCO Enterprise Management Advisor Methods (Sheet 4 of 4) Managed Object Type
RVD and RVRD (Contd) TIBCO software components
Method Name
GetMetricValuesByCategory
Description
Return all metric values for the given category
Refer to the documentation for the specific TIBCO software component for a list of available methods. Additionally, the following methods are available for accessing metric data. GetMetricDefinitions Return all metric definitions of this managed object. Return all metric values for this managed object. Return all meric definition values for the given managed object. Return a particular metric definition. Return a list of metric categories. Return a particular metric value Return all metric values for the given category
GetMetricValues
GetMetricDefinitionCategories
GetMetricDefinitionByName GetMetricDefinitionByCategory GetMetricValueByName GetMetricValuesByCategory
External Component getResourceIdentifier Returns the unique identifier assigned to this managed object.
| 71
Chapter 4
Trace Messages
Topics
Introduction, page 72 Trace Message List, page 73
72
| Chapter 4
Trace Messages
Introduction
Trace messages provide an efficient way to track down the cause of a problem. Trace messages are standardized to a particular format. Each message is divided into a number of fields, which are explained in the next table: Table 8 Trace Message Handling Fields Field Name MessageCode Explanation Unique code for the message. For example:
EMI-10022
Description Category Role
Informative text message explaining the trace message. Name of the component which generated the message. Role of the trace message: Error Unrecoverable errors. If an error of this type is not addressed, the component may continue with the next operation or may stop altogether. Warning An abnormal condition was found, but it does not prevent processing to be performed. Special attention from an administrator is recommended. Information A significant processing step was reached and it has been logged for tracking or auditing purposes.
Resolution
Suggested solution to resolve the problem.
Location of the log files The log file created by EMA Agent, EMAdvisor-emaagent.log is created in the following location:
<TIBCO_HOME>\tra\domain\<domain_name>\application\logs
Where, <TIBCO_HOME> is your TIBCO installation directory and <domain_name> is the name of the TIBCO Administrator domain where you have TIBCO EM Advisor deployed.
Trace Message List 73
Trace Message List

EMI-10010=Starting TIBCO Enterprise Management Advisor Monitoring Service Role: Info Category: TIBCO Enterprise Management Advisor core
EMI-10011=TIBCO Enterprise Management Advisor Monitoring Service is ready Role: Info Category: TIBCO Enterprise Management Advisor core
EMI-10012=Stopping TIBCO Enterprise Management Advisor Monitoring Service Role: Info Category: TIBCO Enterprise Management Advisor core
EMI-10013=Initialize TIBCO Hawk Console with RV paramters '%1' domain %2 security implementation %3 Role: Info Category: TIBCO Enterprise Management Advisor core
EMI-10021=Internal Error: %1 Role: Error Category: TIBCO Enterprise Management Advisor core Resolution: Internal Error. Contact TIBCO Support for assistance.
EMI-10022=Internal Error: %1 Role: Error Category: TIBCO Enterprise Management Advisor core
74
| Chapter 4
Trace Messages
Resolution: Internal Error. Contact TIBCO Support for assistance.
EMI-10031=Error in Configuration for element <element name>: Invalid value <element value> Role: Error Category: TIBCO Enterprise Management Advisor core Resolution: An invalid value <element value> was specified for <element name>. If the resolution is not obvious from the error description contact TIBCO Support for assistance.
EMI-10032=Error in Configuration for element <element name>: Invalid managed object type <managed object type> Role: Error Category: TIBCO Enterprise Management Advisor core Resolution: An invalid managed object type was specified. For a list of valid managed object types see Valid Managed Object Types, page 93.
EMI-10033=Error in Configuration for element <element name>: Invalid metric definition type <metric definition type value> Role: Error Category: TIBCO Enterprise Management Advisor core Resolution: An invalid metric definition type <metric definition type value> was specified. Valid values are: accumulated, delta, snapshot, and rate.
EMI-10034=Error in configuration for element <element > name <element name>: The <sub-element> element for <element-2 > can not be null. Role: Error Category: TIBCO Enterprise Management Advisor core Resolution: Check your default_config.xml file and make sure sub-elements of <element-2> have values specified.
EMI-10035=Error in configuration for element <element > name <element name>: The <sub-element> element for <element-2 > <element-3 >can not be null. Role: Error Category: TIBCO Enterprise Management Advisor core Resolution: Check your default_config.xml file and make sure sub-elements of <element-2> and <element-3> have values specified.
EMI-10041=Unable to get TIBCO Hawk method description for ManagedObject <managed object>microagent <microagent> method <method> on machine <host name>, the metric category configuration <metric category> is ignored Role: Error Category: TIBCO Enterprise Management Advisor core Resolution: Check the method name <method> that is used.
EMI-10042=Failed to listen on RV HOST STATUS messages with parameters '%1' because of %2 Role: Error Category: TIBCO Enterprise Management Advisor core Resolution: Check your TIBCO Rendezvous configuration parameters.
EMI-10043=Failed to subscribe TIBCO EMA Proxy methods on machine <host 1> because of <host 2> Role: Error Category: TIBCO Enterprise Management Advisor core Resolution: Use TIBCO Hawk Display to check the status of the machine host-1 and host-2. Also check the EMA Agent log file for help in resolving the error.
EMI-10044=EMA admindomain %1 %2 Role: Error Category: TIBCO Enterprise Management Advisor core
76
| Chapter 4
Trace Messages
Resolution:
EMI-10101=AGENT_ALIVE : agent={agent-name= <agent name>, dns= <dns>, host-name= <host name>, host-ip= <host IP address>, cluster= <cluster>} Role: Info Category: TIBCO Enterprise Management Advisor core
EMI-10102=AGENT_EXPIRED : agent={agent-name= <agent name>, dns= <dns>, host-name= <host name>, host-ip= <host IP address>, cluster= <cluster>} Role: Warning Category: TIBCO Enterprise Management Advisor core Resolution: Restart the agent <agent name>. You may also need to reboot the host name <host name>.
EMI-20000=EMA Agent version <version number> Role: Info Category: TIBCO Enterprise Management Advisor EMA Agent
EMI-20001=EMA Agent is starting up Role: Info Category: TIBCO Enterprise Management Advisor EMA Agent
EMI-20002=EMA Agent started successfully Role: Info Category: TIBCO Enterprise Management Advisor EMA Agent
EMI-20003=EMA Agent is loading Managed Object Provider: '%1' Role: Info

Category: TIBCO Enterprise Management Advisor EMA Agent
EMI-20004=EMA Agent loaded Managed Object Provider: '%1' successfully Role: Info Category: TIBCO Enterprise Management Advisor EMA Agent
EMI-20005=Plugin to be used does not match any of the Managed Object Providers defined. EMA Agent exits Role: Error Category: TIBCO Enterprise Management Advisor EMA Agent Resolution: Contact TIBCO Support for assistance.
EMI-20006=No Managed Object Provider defined. EMA Agent exits Role: Error Category: TIBCO Enterprise Management Advisor EMA Agent
EMI-20007=Try to use a non-supported web service management specification. EMA Agent exits. Role: Error Category: TIBCO Enterprise Management Advisor EMA Agent
EMI-20009=EMA Agent terminated Role: Info Category: TIBCO Enterprise Management Advisor EMA Agent
EMI-20011=EMA Agent started as '%1' fault-tolerance mode Role: Info Category: TIBCO Enterprise Management Advisor EMA Agent
78
| Chapter 4
Trace Messages
EMI-20012=Enterprise mode is turned on Role: Info Category: TIBCO Enterprise Management Advisor EMA Agent
EMI-20013=Sniffer mode is turned on Role: Info Category: TIBCO Enterprise Management Advisor EMA Agent
EMI-20014=Dependency Model is out of date. Rebuilding... Role: Info Category: TIBCO Enterprise Management Advisor EMA Agent
EMI-20015=Dependency Model is up to date. Role: Info Category: TIBCO Enterprise Management Advisor EMA Agent
EMI-30001=EMA Agent is starting '%1' soap driver on port '%2' Role: Info Category: TIBCO Enterprise Management Advisor web services
EMI-30002=EMA Agent started '%1' soap driver on port <port number> successfully Role: Info Category: TIBCO Enterprise Management Advisor web services
EMI-30003=EMA Agent is listening on '%1' Role: Info Category: TIBCO Enterprise Management Advisor web services
EMI-30004=HTTP (or HTTPS) server tries to run on an already used port. EMA Agent exits. Role: Error Category: TIBCO Enterprise Management Advisor web services Resolution: Try to use an unused port to run the HTTP (or HTTPS) server.
EMI-30211=Invoke operation <operation name> on <managed object> Role: Info Category: TIBCO Enterprise Management Advisor web services
EMI-30222=Invoke TIBCO Hawk AMI method <method name>on <Hawk microagent name> Role: Info Category: TIBCO Enterprise Management Advisor web services
EMI-35011=Initializing Web Services environment for WSMF Role: Info Category: TIBCO Enterprise Management Advisor web services
EMI-35012=Initialized Web Services environment for WSMF successfully Role: Info Category: TIBCO Enterprise Management Advisor web services
EMI-35013=Root Managed Object is available at '%1' Role: Info

80
| Chapter 4
Trace Messages
Category: TIBCO Enterprise Management Advisor web services
EMI-35311=EMA Agent connection to <HTTP server> refused. Role: Warning Category: TIBCO Enterprise Management Advisor web services Resolution: Check the connection to the HTTP server receiving events. You may need to re-subscribe to the lost events.
EMI-35312=Notify Listener <listener name> about event <event name> Role: Info Category: TIBCO Enterprise Management Advisor web services
EMI-35411=The status of Managed Object <managed object name> changed from '<old status> to <new status> Role: Info Category: TIBCO Enterprise Management Advisor web services
EMI-35511=Relationship changed to Managed Object <managed object name>. Type: %2, HowRelated: %3 Role: Info Category: TIBCO Enterprise Management Advisor web services
EMI-40000=%1 Role: Error Category: External EM Event Notification Resolution: Contact TIBCO Support
EMI-40001=External EM Event Thread started listening on port : <port number>. Role: Info Category: External EM Event Notification
EMI-40002=Invoking GetSupportedEvent Events on MO : <managed object name>. Role: Info Category: External EM Event Notification
EMI-40003=Sending PushSubscribe for event: %1 : MO URL : %2 Role: Info Category: External EM Event Notification
EMI-40004=No events supported for MO : <managed object name>. Role: Info Category: External EM Event Notification
EMI-40005=Location for PushSubscribe is : %1 Role: Info Category: External EM Event Notification
EMI-40006=Response back for PushSubscribe for event : <event> : is : <response>. Role: Info Category: External EM Event Notification
EMI-40007=No Subscription response for event : <event>. Role: Info Category: External EM Event Notification
82
| Chapter 4
Trace Messages
EMI-40008=External EM Event Sent on JMS topic. Role: Info Category: External EM Event Notification
EMI-40009=External EM Event Sent on RV Subject. Role: Info Category: External EM Event Notification
EMI-41001=Failed to open Tibrv in native implementation. Role: Error Category: External EM Event Notification Resolution: Contact TIBCO Support for assistance.
EMI-41002=Failed to create TibrvRvdTransport. Role: Error Category: External EM Event Notification Resolution: Check the RV transport parameters.
EMI-41003=Client port :%1: specified in config.xml is not a valid number. Role: Error Category: External EM Event Notification Resolution: Make sure the client port specified is a valid integer.
EMI-41004=External EM Event Thread was interrupted. Role: Error Category: External EM Event Notification
Resolution: Contact TIBCO Support for assistance.
EMI-41005=IO Exception for listening on clientport Role: Error Category: External EM Event Notification Resolution: Contact TIBCO Support for assistance.
EMI-41006=Exception dispatching RV default queue. Role: Error Category: External EM Event Notification Resolution: Contact TIBCO Support for assistance.
EMI-41007=Failed to initialized WSDL: <root wsdl>: External EM Events receiving functionality non-operative. Role: Error Category: External EM Event Notification Resolution: Make sure the URL specified for the root WSDL is valid.
EMI-41008=Unknown host exception for InetAddress.getLocalHost(): %1. Role: Error Category: External EM Event Notification Resolution: Contact TIBCO Support for assistance.
EMI-41009=Events from HP OpenView will not be received. Role: Error Category: External EM Event Notification Resolution: Contact TIBCO Support for assistance.
84
| Chapter 4
Trace Messages
EMI-41010=IOException wring to file: <file name>. Role: Error Category: External EM Event Notification Resolution: Unable to create a temporary file in the directory <TIBCO_HOME>\ema\2.1\bin. Check the permissions for this directory.
EMI-41011=Error Closing RV connection. Role: Error Category: External EM Event Notification Resolution: Contact TIBCO Support for assistance.
EMI-41012=Error Closing JMS connection. Role: Error Category: External EM Event Notification Resolution: Contact TIBCO Support for assistance.
EMI-41013=Exception Creating JMS connection. Role: Error Category: External EM Event Notification Resolution: Check your JMS paramters and make sure the JMS server is accepting connections.
EMI-41014=IO Exception Publishing Message. Role: Error Category: External EM Event Notification Resolution: Contact TIBCO Support for assistance.
EMI-41015=Exception Publishing Message on RV. Role: Error Category: External EM Event Notification Resolution: Contact TIBCO Support for assistance.
EMI-41016=Exception Publishing Message on JMS topic. Role: Error Category: External EM Event Notification Resolution: Contact TIBCO Support for assistance.
EMI-50000=EMI Sniffer %1 %2 Role: Info Category: EMA Agent
EMI-52000=EMI Sniffer %1 %2 Role: Error Category: EMA Agent Resolution: If resolution is not obvious from the error description contact TIBCO Support for assistance.
86
| Chapter 4
Trace Messages
| 87
Appendix A
Sample Configuration Files
Topics
default_config.xml, page 88 Sample custom_config.xml, page 100
88
| Appendix A
default_config.xml
The following sections describe the configuration file default_config.xml to give an understanding of how the file is used by EMA Agent. Please note that if you change any parameter values in default_config.xml, you will need to re-deploy EMA Agent in order for those values to be picked up. The following table describes the top-level <emi> element described in the default_config.xml configuration file. Subsequent tables describe the elements contained within the <emi> element. emi Element Name: emi
emi defaultVendor The default vendor of the product. Default value is TIBCO Software. defaultOwner The default owner of the product. Default value is TIBCO Software. noAlertClearAfterAgentExpired This element specifies whether the TIBCO Hawk alert clear events will be sent after the agent expires. If this element is set to TRUE, alert clear events will be not sent after the agent expired event until the agent becomes alive again. emiagentStartupDelay The time in milliseconds for which EMA Agent waits before announcing its availability to the EM platform. useShortURI If this parameter is set to true, the URI assigned for each managed object is shorter in length. Default value is false.
The following sections describe the elements contained within the top-level <emi> element. microagentDiscoveryRuleList, page 90 methodFilterList, page 94
default_config.xml 89
metricConfigurationList, page 95 logger, page 98
90
| Appendix A
microagentDiscoveryRuleList The <microagentDiscoveryRuleList> element contains rules used in discovering TIBCO Hawk for the TIBCO applications that are not deployed using TIBCO Administrator. To discover the multiple TIBCO applications, the <microagentDiscoveryRule> element has to be replicated with appropriate values. If a microagent is not listed, it will not be discovered and will not be exposed to the EM Platform. The string described by the <maNamePattern> element is used to match with the microagent display name of the deployed TIBCO applications. The sequence of the <microagentDiscoveryRule> elements is important because rules defined earlier take precedence over subsequent rule definitions. Rules that use a precise <maNamePattern> pattern should be at the beginning of the list with the more generic patterns appearing later in the list. If you have customs applications deployed in your domain, rules to discover those applications must be specified in the custom_config.xml configuration file. This configuration file is located in the following directory:
<TIBCO_HOME>\ema\config
where <TIBCO_HOME> is the TIBCO installation directory. Element Name: microagentDiscoveryRuleList

microagentDiscoveryRuleList microagentDiscoveryRule The <microagentDiscoveryRule> element contains the following elements: maNamePattern String used to match with the microagent display name. EMA Agent uses the string substituted by {0} to form the name of the managed object. The strings at the locations indicated by curly brackets denote the following: {0} - instance name {1} - component type {2} - deployment name {3} - domain name See Using the maNamePattern Element on page 91 for more details. managedObjectType Type of managed object. componentType Component type of the managed object.
Element Name: microagentDiscoveryRuleList

stopMethod Name of the TIBCO Hawk method used to stop the managed object. Example: stopApplicationInstance startScript The name of the start script. This element can be updated using EMA ConfigUI. stopScript The name of the stop script. This element can be updated using EMA ConfigUI. instanceName In Example 2, the <maNamePattern> element does not contain an instance name, indicated by the absence of the {0} wildcard. In this case, defining a <instanceName> element is required in order to give the microagent a specific name. In Example 3, the <maNamePattern> element does contain an instance name as denoted by the presence of the wildcard {0}, but the <instanceName> element is used to give the microagent a different name. The <instanceName> element overrides the <maNamePattern> element. When using the <instanceName> element to override the name specified by <maNamePattern> the wildcard {0} has to be a part of the <instanceName> definition. Use of the <instanceName> element in this example is optional. versionMethod The name of the TIBCO Hawk method that returns information related to the application instance. versionColumn The name of the column in the data returned by the <versionMethod> defined above that contains the version number of the application instance. The <stopMethod> element will be used for microagents that expose a stop method. If it is specified, you will not be able to update the <stopScript> element using EMA ConfigUI. If a stop method is not exposed, use the <stopScript> element instead.
Using the maNamePattern Element When the maNamePattern is defined as COM.TIBCO.ADAPTER.{1}.{2}.{0} and EMA Agent discovers an adapter with the name
COM.TIBCO.ADAPTER.adpsft8.psa_test.PeopleSoftAdapterConfiguration.
EMA Agent maps the name of the discovered adapter to the maNamePattern to define the name of the component type of this managed object to be adpsft8 as denoted by the location {1}
92
| Appendix A
the deployment name to be psa_test as denoted by the location {2}, and the instance name to be PeopleSoftAdapterConfiguration as denoted by the location of {0}
Example
<microagentDiscoveryRuleList> <microagentDiscoveryRule>   <maNamePattern>COM.TIBCO.ADAPTER.bwengine.{3}.{2}.{0}</maNamePa ttern> <managedObjectType>BWEngine</managedObjectType> <stopMethod>stopApplicationInstance</stopMethod> <startScript></startScript> <stopScript></stopScript> </microagentDiscoveryRule> <microagentDiscoveryRule>  <maNamePattern>COM.TIBCO.ADAPTER.SAP.{1}.{2}.{0}</maNamePattern> <managedObjectType>Adapter</managedObjectType> <componentType>bw</componentType> <stopMethod></stopMethod> <startScript></startScript> <stopScript></stopScript> </microagentDiscoveryRule>   <microagentDiscoveryRule> <maNamePattern>Spot</maNamePattern> <managedObjectType>Custom</managedObjectType> <componentType>custom</componentType> <stopMethod /> <startScript /> <stopScript /> <instanceName>Spot</instanceName> </microagentDiscoveryRule>    <microagentDiscoveryRule> <maNamePattern>MessageBroker.{0}</maNamePattern> <managedObjectType>MB</managedObjectType> <componentType>mb</componentType> <stopMethod>shutdown</stopMethod> <startScript /> <stopScript /> <instanceName>MB {0}</instanceName> </microagentDiscoveryRule> </microagentDiscoveryRuleList>
Valid Managed Object Types The following table lists the valid managed object types that you can specify in the default_config.xml file. Table 9 Valid Managed Object Types Used in Configuration Files Managed Object Type
Custom
Corresponding TIBCO Software Component

Any application instrumented using TIBCO Hawk AMI API. TIBCO Adapter TIBCO BusinessWorks engine TIBCO Integration Manager TIBCO MessageBroker TIBCO InConcert Server TIBCO BusinessConnect TIBCO Administrator TIBCO Enterprise Management Advisor TIBCO Rendezvous daemon TIBCO Rendezvous routing daemon TIBCO EMS TIBCO DataExchange TIBCO DataExchange
Adapter BWEngine IM MB ICServer BC REPO EMI RVD RVRD JMSServer DXServer ETLTask
94
| Appendix A
methodFilterList This element is used to define which TIBCO Hawk methods belonging to the managed objects within the domain are exposed. Element Name: methodfilterList
methodFilterList methodFilter The <methodFilter> element contains the following elements: managedObjectType Type of the managed object for which you want to define method filters. If a managedObjectType is listed in the <microagentDiscoveryRule> element, but not listed in the <methodFilterList>, all methods for the managedObjectType will be exposed See Valid Managed Object Types Used in Configuration Files on page 93 for the list of valid values. componentType Optional. The specific component type of the managed objects for which method filters are defined. Typically, instances of a specific managed object type have a common set of methods. Additionally, there could be another set of methods common only to a particular component type of some managed objects. Using componentType you can make available those methods that are common to the managed object type and component type combination. method The name of the method exposed to the EM platform.
Example
<methodFilterList> <methodFilter>  <managedObjectType>Adapter</managedObjectType> <method>getStatus</method> <method>getConfig</method> <method>getAdapterServiceInformation</method> <method>getHostInformation</method> <method>getComponents</method> <method>getRvConfig</method> <method>reviewLedger</method> <method>preRegisterListener</method> <method>unRegisterListener</method> </methodFilter> </methodFilterList>
metricConfigurationList The <metricConfigurationList> is used to define the metrics that you want TIBCO EM Advisor to provide. If this element is not defined, only the default TIBCO Rendezvous daemon metrics will be available. Element Name: metricConfigurationList
metricConfigurationList metricConfiguration The <metricConfiguration> element contains the following elements: managedObjectType Type of the managed object for which you want to define metrics. ComponentType Optional. When this element is not defined the <metricConfiguration> element is applied to all instances of the specified managed object type. category This element defines the metrics for the specified managed object and component type for a specific TIBCO Hawk method. name The metric category name exposed to the EM platform. This is the name by which the method defined in the following <method> element is known to the EM platform. description The description of this category. method The name of the TIBCO Hawk method that will provide the metrics for the managed object. Asynchronous TIBCO Hawk methods cannot be used for collecting metric
data.
inputParameters This element is a container for the <parameter> element which specifies the input parameters for the TIBCO Hawk methods returning the data for metrics.
96
| Appendix A
Element Name: metricConfigurationList

parameter name The name of the input parameter. value The value to use for the input parameter. rowindex This element uses the name and value combination defined by the <parameter> elements to select a unique row. More than one <parameter> element may be needed to select a unique row. parameter name The name of the output parameter. value The value of the output parameter for the selected row. metricDefinition name The name of the metric definition. By default, it is the same as the <outputParameterName> element. outputParameterName This is the name of the output parameter of the method that returns metric values. unit The unit of measurement. metrictype Valid values are: accumulated, delta, snapshot, and rate.
When invoking the GetMetricDefinitionByName method from the EM platform, you have to use the combination of the category name and the metric definition name as defined in the default_config.xml to uniquely identify the metric definitions for the managed object. This is because multiple TIBCO Hawk methods providing metric data could have columns with the same name. Using the example given below for an managed object of type Adapter and component type adsbl, use getAdapterStatisticsByService-MeasurementInterval as the input parameter when invoking the GetMetricDefinitionByName method.
Example
<metricConfigurationList> <metricConfiguration>    <managedObjectType>Adapter</managedObjectType> <componentType>adsbl</componentType> <category> <name>getAdapterServiceInformation</name> <description>Get adapter activity statictics </description> <method>getAdapterStatisticsByService</method> <metricDefinition> <name>MeasurementInterval </name> <outputParameterName>MeasurementInterval</outputParameterName> <unit>seconds</unit> <metricType>Accumulated</metricType> </metricDefinition> </category> </metricConfiguration>  <metricConfiguration> <managedObjectType>Adapter</managedObjectType> <category> <name>getAdapterServiceInformation</name> <description>Get adapter service information</description> <method>getAdapterServiceInformation</method> <metricDefinition> <name>Number of Messages</name> <outputParameterName>Number of Messages</outputParameterName> <unit>messages</unit> <metricType>Accumulated</metricType> </metricDefinition> </category> </metricConfiguration> <metricConfigurationList>
98
| Appendix A
logger
You can tailor the contents of the log files generated by EMA Agent using the <logger> element. Element Name: logger
logger file The <file> element contains the following elements: maxsize The maximum size in bytes a log file is allowed to reach before it is closed and renamed, and a new log file with the same name is created. maxnum The maximum number of log files created before log entries roll over to reuse the oldest log file. append If TRUE, append to the current log file if a file with the specified name exists. If FALSE, delete the existing file and create a new file. enabledRoles role Role of the trace message:
errorRole warnRole
- Unrecoverable errors were encountered.
- An abnormal condition was found, but it does not prevent further processing. - A significant processing step was reached which is being logged.
infoRole
debugRole - Processing steps of the EMA Agent when used in the debug mode are logged for problem resolution purposes.
Example
<logger> <file>  <maxsize>1024000</maxsize>  <maxnum>5</maxnum>  <append>false</append> </file> <enabledRoles> 
<role>errorRole</role> <role>warnRole</role> </enabledRoles> </logger>
100
| Appendix A
Sample custom_config.xml
<?xml version = "1.0" encoding = "UTF-8"?>  <emi>  <microagentDiscoveryRuleList>  <microagentDiscoveryRule> <maNamePattern>Spot</maNamePattern> <managedObjectType>Custom</managedObjectType> <componentType>custom</componentType> <stopMethod></stopMethod> <startScript></startScript> <stopScript></stopScript> <instanceName>Spot</instanceName> </microagentDiscoveryRule> </microagentDiscoveryRuleList>  <rvDeamonStatisticsCollectionInterval>360</rvDeamonStatisticsColle ctionInterval> </emi>
| 101
Appendix B
Icons Used By EM Advisor Console
Topics
EM Advisor Console Icons, page 102
102
| Appendix B
EM Advisor Console Icons

The following table lists the icons used by EM Advisor Console.
Table 10 Icons used by EM Advisor Console Icon Managed Object Type

TIBCORoot
Domain
Deployment folder
Machine
Service group. For example, a fault tolerant group.
TIBCO Adapter service
TIBCO BusinessWorks business process with no starter.
EM Advisor Console Icons 103

TIBCO BusinessWorks business process with starters.
Custom application TIBCO MessageBroker TIBCO BusinessConnect TIBCO Rendezvous daemon TIBCO Rendezvous routing daemon TIBCO Adapter
TIBCO BusinessWorks engine
TIBCO Integration Manager
TIBCO EM Advisor
TIBCO EMS
TIBCO Administrator
104
| Appendix B

TIBCO BusinessWorks WorkFlow
TIBCO Software Inc. End User License Agreement
| 105

READ THIS END USER LICENSE AGREEMENT CAREFULLY. BY DOWNLOADING OR INSTALLING THE SOFTWARE, YOU AGREE TO BE BOUND BY THIS AGREEMENT. IF YOU DO NOT AGREE TO THESE TERMS, DO NOT DOWNLOAD OR INSTALL THE SOFTWARE AND RETURN IT TO THE VENDOR FROM WHICH IT WAS PURCHASED. Upon your acceptance as indicated above, the following shall govern your use of the Software except to the extent all or any portion of the Software (a) is subject to a separate written agreement, or (b) is provided by a third party under the terms set forth in an Addenda at the end of this Agreement, in which case the terms of such addenda shall control over inconsistent terms with regard to such portion(s). License Grant. The Software is the property of TIBCO or its licensors and is protected by copyright and other laws. While TIBCO continues to own the Software, TIBCO hereby grants to Customer a limited, non-transferable, non-exclusive, license to use the number of Permitted Instances set forth in the Ordering Document, in machine-readable, object code form and solely for Customer's internal business use. Restrictions. Customer agrees not to (a) make more copies than the number of Permitted Instances plus a reasonable number of backups; (b) provide access to the Software to anyone other than employees, contractors, or consultants of Customer; (c) sublicense, transfer, assign, distribute to any third party, pledge, lease, rent, or commercially share the Software or any of Customer's rights under this Agreement (for the purposes of the foregoing a change in control of Licensee is deemed to be an assignment); (d) use the Software for purposes of providing a service bureau, including, without limitation, providing third-party hosting, or third-party application integration or application service provider-type services, or any similar services; (e) use the Software in connection with ultrahazardous activities, or any activity for which failure of the Software might result in death or serious bodily injury to Customer or a third party; or (f) directly or indirectly, in whole or in part, modify, translate, reverse engineer, decrypt, decompile, disassemble, make error corrections to, create derivative works based on, or otherwise attempt to discover the source code or underlying ideas or algorithms of the Software. Beta and Evaluation Licenses. Notwithstanding the foregoing, if the Software is being provided for demonstration, beta testing, or evaluation purposes, then Customer agrees (a) to use the Software solely for such purposes, (b) that the Software will not be used or deployed in a production environment, and (c) that such use shall automatically terminate upon the earlier of thirty days from the date Customer receives the right to install the Software, or Customer's receipt of notice of termination from TIBCO. Technical Support. Provided Customer has paid applicable support fees (not included with Software fees unless separately listed), TIBCO shall provide support for generally available TIBCO Software on an annual basis commencing on the Purchase Date, as follows ("Support"): Customer shall designate at TIBCO's support website https://support.tibco.com/eSupport/newuser.html, the number of technical support contacts permitted under the level of Support purchased (contacts are changeable upon 48-hours prior written notice to TIBCO). Each contact may contact TIBCO for problem resolution during TIBCO's published support hours corresponding to the level of Support fees paid. Upon notice from a contact of a Software problem which can be reproduced at a TIBCO support facility or via remote access to Customer's facility, TIBCO shall use reasonable efforts to correct or circumvent the problem according to its published support objectives. TIBCO reserves the right to make changes only to the most currently available version. TIBCO will use reasonable efforts to support the previously released version of the Software for a maximum of six months. TIBCO shall have no obligation to support the Software (i) for use on any computer system running other than the operating system software for which the Software is approved (as set forth in the Software documentation) and licensed hereunder, or (ii) if Customer has modified or authorized a third party to modify the Software. TIBCO shall have no obligation to modify any version of the Software to run with any new versions of any operating system, or any other third party software or hardware. If Customer purchases Support for any Software, Customer must purchase the same level of Support for all copies of the Software for which it is licensed. Support may be extended for one-year periods on the anniversary of each Purchase Date at the standard amounts set forth in its price list, for as long as TIBCO offers Support. Customer may reinstate lapsed support for any then currently supported Software by paying all Support fees in arrears and any applicable reinstatement fee. Upgrades, patches, enhancements, bug fixes, new versions and/or new releases of the Software provided from time to time under Support shall be used only as replacements to existing Permitted Instances, and shall not be deemed to increase that number, and use thereof shall be governed by the terms of this Agreement, except for the first paragraph of the Limited Warranty and any right of return or refund. Consulting Services. Customer may request additional services ("Services") either in an Ordering Document, or by a separate mutually executed work order, statement of work or other work-request document incorporating this Agreement (each, a "Work Order"). Unless otherwise expressly agreed to in a Work Order, all Services and any work product therefrom shall be (a) performed on a time and materials basis, plus meals, lodging, travel, and other expenses reasonably incurred in connection therewith, (b) deemed accepted upon delivery, and (c) exclusively owned by TIBCO (except for confidential information of Customer identified to TIBCO in the Ordering Document), including all right, title and intellectual property or other right or interest therein. Each Work Order is intended to constitute an independent and distinct agreement of the parties, notwithstanding that each shall be construed to incorporate all applicable provisions of this Agreement. Specific to TIBCO training services, additional information regarding courses, registration, restrictions or limitation can be found at TIBCO's website at http://www.tibco.com/services/education under Education Programs. Fees for Services shall be due and payable in United States dollars net 30 from the date of TIBCO's invoice. Limited Warranty. If Customer obtained the Software directly from TIBCO, then TIBCO warrants that for a period of thirty (30) days from the Purchase Date: (i) the media on which the Software is furnished will be free of defects in materials and workmanship under normal use; and (ii) the Software will substantially conform to its published specifications. This limited warranty extends only to the original Customer hereunder. Customer's sole and exclusive remedy and the entire liability of TIBCO and its licensors under this limited warranty will be, at TIBCO's option, repair, replacement, or refund of the Software and applicable Support fees, in which event this Agreement shall terminate upon payment thereof.
106
| TIBCO Software Inc. End User License Agreement

This warranty does not apply to any Software which (a) is licensed for beta, evaluation, testing or demonstration purposes for which TIBCO does not receive a license fee, (b) has been altered or modified, except by TIBCO, (c) has not been installed, operated, repaired, or maintained in accordance with instructions supplied by TIBCO, (d) has been subjected to abnormal physical or electrical stress, misuse, negligence, or accident, or (e) is used in violation of any other term of this Agreement. Customer agrees to pay TIBCO for any Support or Services provided by TIBCO related to a breach of the foregoing on a time, materials, travel, lodging and other reasonable expenses basis. If Customer obtained the Software from a TIBCO reseller or distributor, the terms of any warranty shall be as provided by such reseller or distributor, and TIBCO provides Customer no warranty with respect to such Software. EXCEPT AS SPECIFIED IN THIS LIMITED WARRANTY, THE SOFTWARE, SUPPORT AND SERVICES ARE PROVIDED "AS IS", ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS, AND WARRANTIES INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTY OR CONDITION OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, SATISFACTORY QUALITY OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE, ARE HEREBY EXCLUDED TO THE EXTENT ALLOWED BY APPLICABLE LAW. NO WARRANTY IS MADE REGARDING THE RESULTS OF ANY SOFTWARE, SUPPORT OR SERVICES OR THAT THE SOFTWARE WILL OPERATE WITHOUT ERRORS, PROBLEMS OR INTERRUPTIONS, OR THAT ERRORS OR BUGS IN THE SOFTWARE WILL BE CORRECTED, OR THAT THE SOFTWARE'S FUNCTIONALITY OR SERVICES WILL MEET CUSTOMER'S REQUIREMENTS. NO TIBCO DEALER, DISTRIBUTOR, AGENT OR EMPLOYEE IS AUTHORIZED TO MAKE ANY MODIFICATIONS, EXTENSIONS OR ADDITIONS TO THIS WARRANTY. Indemnity. If Customer obtained the Software from TIBCO directly, then TIBCO shall indemnify Licensee from and against any final judgment by a court of competent jurisdiction, including reasonable attorneys' fees, that the unmodified TIBCO Software infringes any patent issued by the United States, Canada, Australia, Japan, or any member of the European Union, or any copyright, or any trade secret of a third party; provided that TIBCO is promptly notified in writing of such claim, TIBCO has the exclusive right to control such defense and/or settlement, and Licensee shall provide reasonable assistance (at TIBCO's expense) in the defense thereof. In no event shall Licensee settle any claim, action or proceeding without TIBCO's prior written approval. In the event of any such claim, litigation or threat thereof, TIBCO, at its sole option and expense, shall (a) procure for Licensee the right to continue to use the TIBCO Software or (b) replace or modify the TIBCO Software with functionally equivalent software. If such settlement or modification is not commercially reasonable (in the reasonable opinion of TIBCO), TIBCO may cancel this Agreement upon sixty days prior written notice to Licensee, and refund to Licensee the unamortized portion of the license fees paid to TIBCO by Licensee based on a five-year straight-line depreciation. This Section states the entire liability of TIBCO with respect to the infringement of any Intellectual Property rights, and Licensee hereby expressly waives any other liabilities or obligations of TIBCO with respect thereto. The foregoing indemnity shall not apply to the extent any infringement could have been avoided by use of the then-current release. Limitation of Liability. EXCEPT AS PROVIDED UNDER INDEMNITY OR RESULTING FROM A BREACH OF CONFIDENTIALITY (THE "EXCLUDED MATTERS"), IN NO EVENT WILL EITHER PARTY OR TIBCO'S LICENSORS BE LIABLE FOR ANY LOST DATA, LOST REVENUE, LOST PROFITS, DAMAGE TO REPUTATION, BUSINESS INTERRUPTION, OR ANY OTHER INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, PUNITIVE, EXEMPLARY OR ANY SIMILAR TYPE DAMAGES ARISING OUT OF THIS AGREEMENT, THE USE OR THE INABILITY TO USE THE SOFTWARE, OR THE PROVISION OF ANY SUPPORT OR SERVICES, EVEN IF A PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. EXCEPT FOR THE EXCLUDED MATTERS, IN NO EVENT SHALL A PARTY BE LIABLE TO THE OTHER, WHETHER IN CONTRACT, TORT (INCLUDING ACTIVE OR PASSIVE NEGLIGENCE), BREACH OF WARRANTY, CLAIMS BY THIRD PARTIES OR OTHERWISE, EXCEED THE PRICE PAID BY CUSTOMER UNDER THE APPLICABLE ORDERING DOCUMENT. THE FOREGOING LIMITATIONS SHALL APPLY EVEN IF THE ABOVE-STATED REMEDY OR LIMITED WARRANTY FAILS OF ITS ESSENTIAL PURPOSE. BECAUSE SOME STATES OR JURISDICTIONS DO NOT ALLOW LIMITATION OR EXCLUSION OF CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO CUSTOMER. Confidentiality. "Confidential Information" means the terms of this Agreement; all information marked by the disclosing party as proprietary or confidential; any provided software, related documentation or related performance test results derived by Licensee; and any methods, concepts or processes utilized in provided software or related documentation. Confidential Information shall remain the sole property of the disclosing party and shall not be disclosed to any non-Authorized User without the prior written consent of the disclosing party. If Confidential Information is communicated orally, such communication shall be confirmed as "Confidential" in writing within thirty days of such disclosure. The parties agree to protect the Confidential Information of the other in the same manner it protects the confidentiality of similar information and data of its own (and at all times exercising at least a reasonable degree of care). Except with respect to the Software, items will not be deemed Confidential Information if (i) available to the public other than by a breach of an agreement with TIBCO, (ii) rightfully received from a third party not in breach of any obligation of confidentiality, (iii) independently developed by one party without use of the Confidential Information of the other; (iv) known to the recipient at the time of disclosure (other than under a separate confidentiality obligation); or (v) produced in compliance with applicable law or court order, provided the other party is given reasonable notice of the same. Both parties agree to indemnify the other for any damages the other may sustain resulting from their unauthorized use and/or disclosure of the other's Confidential Information. Such damages shall include reasonable expenses incurred in seeking both legal and equitable remedies. To the extent required by law, at Customer's request, TIBCO shall provide Customer with the interface information needed to achieve interoperability between the Software and another independently created program, on payment of TIBCO's applicable fee. Customer agrees to observe obligations of confidentiality with respect to such information. Export. Software, including technical data, is subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Customer agrees to comply strictly with all such regulations and agrees to obtain all necessary licenses to export, re-export, or import Software. Government Use. If the Customer is an agency, department, or other entity of the United States Government ("Government"), the use, duplication, reproduction, release, modification, disclosure or transfer of the Software, or any related documentation of any kind, including technical data or manuals, is restricted in accordance with Federal Acquisition Regulation ("FAR") 12.212 for civilian agencies and
| 107
Defense Federal Acquisition Regulation Supplement ("DFARS") 227.7202 for military agencies. The Software is commercial computer software and commercial computer software documentation. Use of the Software and related documentation by the Government is further restricted in accordance with the terms of this Agreement, and any modification thereto. Orders. An Ordering Document shall be deemed accepted only by issuance of a TIBCO invoice and solely for purposes of administrative convenience. None of the terms of the Ordering Document (other than the Software product name, number of Permitted Instances, level of Support, description of Services, and fees due in connection therewith) shall apply for any reason or purpose whatsoever, regardless of any statement on any Ordering Document to the contrary, unless countersigned by an officer of TIBCO. This Agreement constitutes the entire agreement between the parties with respect to the use of the Software, Support and Services, and supersedes all proposals, oral or written, and all other representations, statements, negotiations and undertakings relating to the subject matter hereof. All orders of Software, Support or Services by Customer from TIBCO shall be deemed to occur under the terms of this Agreement (with or without reference to this Agreement), unless expressly superseded by a signed written Agreement between the parties. Software shall be delivered electronically (unless physical shipment is specifically set forth in an Ordering Document), and such delivery shall occur when the TIBCO Software is made available for download by Customer. Physical deliveries (if applicable) of Software and documentation which typically accompanies the Software on delivery shall be on CD-ROM, FOB Palo Alto and/or FOB Swindon, and delivery shall occur by depositing the CD-ROM with TIBCO's overnight carrier (at no charge to Customer). Term and Termination. Support or Services may be terminated: (a) by either party upon a default of the other, such default remaining uncured for fifteen days from written notice from the non-defaulting party; (b) upon the filing for bankruptcy or insolvency of the other party, (c) by either party upon prior written notice at least sixty days prior to the end of any annual Maintenance period; or (d) by Licensee (for Services), upon ten days prior written notice. Termination of Support or Services shall not terminate this Agreement. Customer may terminate this Agreement in its entirety at any time by destroying all copies of the Software. Upon termination of this Agreement in its entirety, for any reason, Customer must cease using and return or destroy all copies of the Software. Customer's obligation to pay accrued charges and any fees due as of the date of termination, as well as the sections entitled "Confidentiality", "Limited Warranty" and "Limitation of Liability" shall survive any such termination. Authority. You hereby represent and warrant that you have full power and authority to accept the terms of this Agreement on behalf of Customer, and that Customer agrees to be bound by this Agreement. General. Fees on the Ordering Document (all to be paid on the latter of thirty days from Invoice by TIBCO or the date set forth in the Ordering Document) do not include sales, use, withholding, value-added or similar taxes, and Customer agrees to pay the same, excluding therefrom taxes related to TIBCO's income and corporate franchise tax. Customer agree to pay all reasonable costs incurred (including reasonable attorneys' fees) in collecting past due amounts under this Agreement. Except as set forth in the Section entitled Limited "Warranty" all fees paid under or in connection with this Agreement are non-refundable and no right of set-off exists. All payments of fees due shall be made in U.S. dollars, net 30 from Purchase Date, or, for any other amounts coming due hereafter, net 30 from TIBCO's invoice. A service charge of one and one-half percent per month will be applied to all invoices that are not paid on time. Licensee agrees to pay all sales, use, value-added, withholding,
excise and any other similar taxes or government charges, exclusive of TIBCO's income taxes. No delay in the performance of any obligation by either party, excepting all obligations to make payment, shall constitute a breach of this Agreement to the extent caused by force majeure. Customer hereby grants TIBCO and its independent auditors the right to audit Customer's compliance with this Agreement. If any portion of this Agreement is found to be void or unenforceable, the remaining provisions shall remain in full force and effect. This Agreement shall be governed by and construed in accordance with the laws of the State of California, United States of America, as if performed wholly within the state and without giving effect to the principles of conflict of law. The state and/or federal courts in San Francisco, California, shall have exclusive jurisdiction of any action arising out of or relating to this Agreement. The United Nations Convention on Contracts for the International Sale of Goods is excluded from application hereto. If any portion hereof is found to be void or unenforceable, the remaining provisions of this Agreement shall remain in full force and effect. Definitions. In connection with this Agreement, the following capitalized terms shall have the following meaning: "Agreement" means this End User License Agreement; "Case Start" means the initiation of a single instance of a defined business process; "Connection" for the TIBCO Software product TIBCO Enterprise Message Service - Full Edition means a TIBCO Enterprise Message Service client connection to the TIBCO Enterprise Message Service server for the purpose of sending or receiving messages and for the purposes of the TIBCO Software products TIBCO SmartSockets and TIBCO SmartMQ software products, a Connection means any network protocol link established with such TIBCO Software (directly or indirectly) to any other entity, including but not limited to software, firmware or hardware; "Customer" means the original purchaser or licensee of the Software and any permitted successors and assigns; "Developer" means one user/developer of a TIBCO Software product for use in Development; "Development" means used for software development purposes only; "Enterprise" means an unlimited number of Permitted Instances for a period of one year from the Purchase Date (unless otherwise set forth in the Ordering Document), at which time existing licenses convert to perpetual and Customer may not thereafter deploy additional Permitted Instances, and in any event, shall (during the one-year unlimited deployment period) exclude any entity which acquires, is acquired by, merged into, or otherwise combined with Customer. Customer hereby agrees to provide TIBCO with notice of the number of Permitted Instances deployed at the end of such one-year period within thirty days thereafter; "Fab" means unlimited use for shop-floor manufacturing applications at a Site; "Workstation" shall mean a single end-user computer that is generally intended to be accessed by one person at a time; "Ordering Document" means any purchase order or similar document or agreement requesting Software, Support or Services; "Permitted Instance(s)" means the number of copies of Software running on a Server Instance, Workstation, User, or Development basis, on a designated Platform, as set forth in an Ordering Document, including, without limitation, Enterprise, Site and Fab licensing; "Platform" means the operating system set forth in an Ordering Document; "Purchase Date" means the date of the Ordering Document is accepted by TIBCO; "Server Instance" means a computer with 1 CPU (unless otherwise set forth in the Ordering Document) performing common services for multiple machines; "Site" means an unlimited number of Permitted Instances at a specific physical address set forth in the Ordering Document (or, in the absence of any address, at Customer's corporate headquarters); "Software" means the software products listed in an Ordering Document (except as provided in the second paragraph hereof), in whole and in part, along with their associated documentation; "TIBCO" means TIBCO Software Inc.; and "Named User" means the number of named users with access to the Software.
108
| TIBCO Software Inc. End User License Agreement

Special Product Provisions. TIBCO/BusinessPartner: Customer may sublicense to third parties ("Partners") up to the total Number of Copies of TIBCO/BusinessPartner, provided that for every such sublicense, the Number of Copies Customer is licensed to use shall be reduced by the same number, and provided further that prior to delivery of TIBCO/BusinessPartner to a Partner, such Partner agrees in writing (a) to be bound by terms and conditions at least as protective of TIBCO as the terms of this Agreement, (b) that TIBCO/BusinessPartner be used solely to communicate with Customer's implementation of TIBCO/BusinessConnect, and (c) for such Partner to direct all technical support and Maintenance questions directly to Customer. Customer agrees to keep records of the Partners to which it distributes TIBCO/BusinessPartner, and to provide TIBCO the names thereof (with an address and contact name) within sixty days of the end of each quarter. Third Party Software: Use of any other third-party software identified by its company and/or product name or otherwise designated in Licensee's Ordering Document (collectively "Third Party Software") is subject solely to the terms and conditions of the click-wrap or shrink-wrap license agreement included with the Third Party Software products, and for which TIBCO shall be an intended third-party beneficiary of same. TIBCO shall have no obligation whatsoever in connection with the Third Party Software (including, without limitation, any obligation to provide maintenance or support) and the provision of Third Party Software is accomplished solely as an accommodation and in lieu of Customer purchasing a license to Third Party Software directly from the third party vendor. Embedded/Bundled Products. Some TIBCO Software embeds or bundles other TIBCO Software (e.g., TIBCO/InConcert bundles TIBCO/Rendezvous). Use of such embedded or bundled TIBCO Software is solely to enable the functionality of the TIBCO Software licensed on the Cover Page, and may not be used or accessed by any other TIBCO Software, or for any other purpose. Open Source Software: If Licensee uses Open Source software in conjunction with the TIBCO Software, Licensee must ensure that its use does not: (i) create, or purport to create, obligations of use with respect to the TIBCO Software; or (ii) grant, or purport to grant, to any third party any rights to or immunities under TIBCO's intellectual property or proprietary rights in the TIBCO Software. You also may not combine the TIBCO Software with programs licensed under the GNU General Public License ("GPL") in any manner that could cause, or could be interpreted or asserted to cause, the TIBCO Software or any modifications thereto to become subject to the terms of the GPL. Version 5.0, 8/04 Copyright 1994-2005 TIBCO Software Inc. ALL RIGHTS RESERVED.
Third Party Software Notices

W3C SOFTWARE NOTICE This product includes software licensed from the W3C, copyright 1994-2000 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/ ADDENDA: Third Party License Agreements
Third Party Software License Agreements
| 109
Third Party Software License Agreements

W3C SOFTWARE NOTICE AND LICENSE Appendix B SOAP 1.1 Schemas Copyright 1994-2001 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/ This W3C work (including software, documents, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions: Permission to use, copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including modifications, that you make: 1.The full text of this NOTICE in a location viewable to users of the redistributed or derivative work. 2.Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, a short notice of the following form (hypertext is preferred, text is permitted) should be used within the body of any redistributed or derivative code: "Copyright [$date-of-software] World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/" 3.Notice of any changes or modifications to the W3C files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.) THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION. The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders. HSQLDB 1.7.3 ORIGINAL LICENSE (a.k.a. "hypersonic_lic.txt") THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE For content, code, and products originally developed by Thomas Mueller and the Hypersonic SQL Group: Copyright (c) 1995-2000, The Hypersonic SQL Group. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the Hypersonic SQL Group nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE HYPERSONIC SQL GROUP, OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This software consists of voluntary contributions made by many individuals on behalf of the Hypersonic SQL Group. For work added by the HSQL Development Group: Copyright (c) 2001-2004, The HSQL Development Group All rights reserved. Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the HSQL Development Group nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
110
| Third Party Software License Agreements

IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL HSQL DEVELOPMENT GROUP, HSQLDB.ORG, OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
| 111
Index
A
Administering TIBCO EMS Servers 23 All Alerts alert details 53 viewing alerts 52
EMA ConfigUI adding and deleting an external service 56 configuring service instances 56 defining and deleting dependencies 56 deleting service instances 56 starting 55
C
configuration element emi 88 logger 98 methodFilterList 94 metricConfigurationList 95 microagentDiscoveryRuleList 90 Configuring TIBCO Hawk Microagent Plugin RvdServiceMA 20 customer support vii
S
support, contacting vii system requirements 8
T
technical support vii TIBCO EM Advisor additional configuration 19 configuration 13 fault tolerance setup 27 installation packages 10 installation pre-requisites 8 installing 11 pre-installation tasks 10 required TIBCO products 9 supported platforms 8 uninstalling 12 Trace message 73
E
EM Advisor Console alerts 42 invoking TIBCO Hawk methods 44 managed object status 44 navigating the domain 36 viewing process diagram 45 EMA Agent 31 dependency model 32 integration with TIBCO BusinessWorks 34 representing managed objects 31
112
| Index
U
using TIBCO EM Advisor with EM Platforms available methods 67 external EM events 63 metrics 62 notifications 65

TIBEMAdvisor Usr

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

TIBEMAdvisor Usr

Hochgeladen von

Copyright:

Verfügbare Formate

TIBCO Enterprise Management Advisor Users Guide

Software Release 2.1 May 2006

Chapter 2 Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 3 TIBCO Enterprise Management Advisor Components . . . . . . . . . . . . . . . . . . . . . . . 29

TIBCO Enterprise Management Advisor Users Guide

Chapter 4 Trace Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Appendix A Sample Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Appendix B Icons Used By EM Advisor Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

TIBCO Enterprise Management Advisor Users Guide

TIBCO Enterprise Management Advisor Users Guide

TIBCO Product Documentation

Other TIBCO Product Documentation

TIBCO Enterprise Management Advisor Users Guide

How to Contact TIBCO Customer Support

TIBCO Enterprise Management Advisor Users Guide

| How to Contact TIBCO Customer Support

TIBCO Enterprise Management Advisor Users Guide

TIBCO Enterprise Management Advisor Users Guide

TIBCO Enterprise Management Advisor Users Guide

TIBCO Enterprise Management Advisor

Enterprise Management System

TIBCO Enterprise Management Advisor Users Guide

TIBCO EM Advisor Console TIBCO Administrator TIBCO Hawk

TIBCO Enterprise Management Advisor EMA Agent EMA ConfigUI

TIBCO Adapter for SAP TIBCO Adapter for Files

TIBCO Enterprise Management Advisor Users Guide

TIBCO Enterprise Management Advisor Users Guide

Installation and Configuration

This chapter describes how to install and configure TIBCO EM Advisor.

TIBCO Enterprise Management Advisor Users Guide

Installation and Configuration

Disk Space (MB)

PA-RISC IA64 (Itanium) Sun SPARC Intel x86 Power

TIBCO Enterprise Management Advisor Users Guide

Required TIBCO Products

TIBCO Enterprise Management Advisor Users Guide

Installation and Configuration

TIB_ema-simple_2.1.0_h7_110.bin TIB_ema-simple_2.1.0_h7_ia64.bin TIB_ema-simple_2.1.0_s4_57.bin TIB_ema-simple_2.1.0_lnx86_24.bin TIB_ema-simple_2.1.0_rs_51.bin

TIBCO Enterprise Management Advisor Users Guide

Installing TIBCO EM Advisor 11

Installing TIBCO EM Advisor

TIBCO Enterprise Management Advisor Users Guide

Installation and Configuration

Uninstalling TIBCO EM Advisor

Post Uninstallation Tasks

TIBCO Enterprise Management Advisor Users Guide

TIBCO Enterprise Management Advisor Users Guide

Installation and Configuration

TIBCO Enterprise Management Advisor Users Guide

Installation and Configuration

TIBCO Enterprise Management Advisor Users Guide

checkbox is selected, specify the

TIBCO Enterprise Management Advisor Users Guide

Installation and Configuration

TIBCO Enterprise Management Advisor Users Guide

TIBCO Enterprise Management Advisor Users Guide

Installation and Configuration

Configuring TIBCO Hawk Microagent Plugin RvdServiceMA

TIBCO Enterprise Management Advisor Users Guide

Configuring TIBCO Hawk Microagent Plugin RvdServiceMA 21

TRA installation directory>/domain/< TIBCO

Administrator domain name>/hawkagent_< TIBCO Administrator domain name>.tra