TIBCO Hawk™ Installation and Configuration

Software Release 4.2.1 April 2004

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 HAWK ADMINISTRATOR’S 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 Hawk, TIBCO Designer, TIBCO Rendezvous, TIBCO ActiveEnterprise and TIBCO Repository 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 © 1999-2004 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information

| iii

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TIBCO Hawk Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Third Party Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv xiv xv xv

How to Contact TIBCO Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Chapter 1 Overview of the TIBCO Hawk System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Components of the TIBCO Hawk System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2 Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Installer Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Installing TIBCO Hawk over Previous Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Uninstalling TIBCO Hawk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Product Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Uninstallation Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Installation Registry and History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microsoft Windows Platform Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UNIX Platform Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying the JRE Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6 6 6 7

Chapter 3 Installing on Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disk Space and Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 12 12 13 14

Installing TIBCO Hawk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

TIBCO Hawk Installation and Configuration

iv

| Contents
Typical and Custom Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Installation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reboot the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Disk Counters (Windows 2000 and Windows XP Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Windows Services Logon Account (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 18 18 18 19

Chapter 4 Installing on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Operating Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installer Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disk Space and Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default File Descriptor Setting (Solaris 2.6 and 2.7 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reconfigure Two-Button Mouse Devices (Solaris Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Environment Variable (Compaq Tru64 UNIX Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing TIBCO Hawk on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical and Custom Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 24 25 25 26 28 28 28 29 29 30 30

Installing the TAR File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Starting TIBCO Hawk Components Automatically at System Boot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solaris Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP-UX Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AIX Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRU64 Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LINUX Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 35 36 36 37 37

Chapter 5 Installing on OS/400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Supported Operating Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Installing TIBCO Hawk on OS/400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Starting TIBCO Hawk Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 6 Configuring TIBCO Hawk Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Startup Scripts and Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 TIBCO Hawk Display Configuration File (hawkdisplay.cfg) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
TIBCO Hawk Installation and Configuration

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -M Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 TIBCO Hawk Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 AMI Rendezvous Session Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Creating a TIBCO Rendezvous Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 MicroAgent Plugins. . . . .cfg) . . . . . . . . . . . . . . . . . . . . . . 84 Chapter 7 Using the Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .cfg) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Setting up a TIBCO Rendezvous Daemon Session . . . . . . . . 64 TIBCO Hawk Event Service Configuration File (hawkevent. . Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 General Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Logfile Microagent . . . . . . . . . . Character Encoding . . . . . .cfg) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -M LogService . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Default Session Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Configuration Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Configuration . . . . . . . . . . . . . -M TIBProtocolAdapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 AMI . . . . . . . . . . . 67 Creating a TIBCO Hawk Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 54 56 60 61 62 63 63 TIBCO Hawk HMA Configuration File (hawkhma. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration File Options . -M Self . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -M LogfileMicroAgent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Configuration Utility Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Configuring the Event Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 TIBCO Hawk Agent Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -M AMIService . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Display . . . . . . . . . . Rendezvous Session . . . . . . . . . . . . . . . . . . . . . . . . . 103 Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Java Virtual Machine Command Line Options . . . -M RuleBaseEngine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Heartbeat . . . Domain Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HMA Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Java Runtime Configuration . . . . . . . . . . . . . . . . . . 89 90 90 91 92 93 94 95 95 95 95 TIBCO Hawk Display Configuration . . . . . . . . . . .Contents v | TIBCO Hawk Agent Configuration File (hawkagent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TIBCO Hawk AMI Java API Sample Application . . . . . . . . . . . . . 113 Agents and the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging . . . . . . . . . . . . . . . . . . . . . . . . 135 Trusted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 127 128 129 130 Chapter 10 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Event Service in Windows XP and 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Setting Up Network Communication in Windows . . . . . . . . . . . . . . . . . . . 125 The Sample AMI API Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Routing Daemon Configuration for UNIX . . . . 144 TIBCO Rendezvous DataSecurity . . . . 118 118 118 118 Using the TIBCO Hawk Display over a Dial-up Network Connection . . . . . . . . . . . . . . . . . . . . . Command-Line Executable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TIBCO Hawk AMI C API Sample Applications. . . . . . . . 124 Using the TIBCO Hawk Sample Applications . . . . . . . . . . . . . . . . Installing a Routing Daemon as a Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Establishing a Dial-up Connection in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 107 108 108 109 Chapter 8 Using TIBCO Hawk Across Nets or Subnets . . . . . . . . . . . . . . . . . . . . . . . . 140 Certified Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TIBCO Hawk AMI C++ API Sample Application . . . . . . . . . . . . . . . . . . 145 Architecture . . 135 Access Control File . . . . . . . . . 123 Using the Sample TIBCO Hawk Rulebases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Configuring Hawk Rendezvous Subjects . . . . . . . . . . . . . . . . . . Using the Sample Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 TIBCO Hawk Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using both Trusted and TrustedWithDomain . . . . . . . . . Disabling and Enabling the Event Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making TIBCO Hawk Services Depend on the Routing Daemon Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . .vi | Contents TIBCO Hawk Event Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .txt and TrustedWithDomain File Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Chapter 9 TIBCO Hawk Sample Rulebases and Applications . . . . . . . . . . . . . . . 133 133 133 134 To Use the Trusted Model . . . . . . . . . . . . . . . . . . . . . . . . . 114 Configuring for Network Communication . . . . . . . . 132 Trusted Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Setting up Network Communication on UNIX . . . . . . . . . . . . . . 121 Establishing a Dial-up Connection in UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Routing Daemon Service Automatically in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Converting Commands from Previous Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Certificate Authorities. . . . . . . . . . . . 162 General Errors . . . . . . . . . . . . . 150 Running with a localhost rvd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Appendix C TIBCO Hawk Directories and Files . . . . . . . . . . 155 Migration Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Appendix D Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Appendix A Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Configuring access control in rvacld for the Certificate Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 TIBCO Hawk Directory Structure. . . . . . 147 Secure AMI Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Re-Linking C and C++ Applications to Libraries. . . . . . . . 185 TIBCO Hawk Installation and Configuration . . . . . . . . . . . . . . . .Contents vii | Access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 String Variable Error . . 176 Appendix E Code Page Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Packet Fragmentation Errors with Multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 156 156 156 156 157 157 Appendix B Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 UNIX Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .x Agents Together. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Code Page Identifiers . . . . . . . . . . . . . . . . . 175 Example Certificate File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Index . . . . . . . . . . . . . . . . . . . . . . . Migrating Rulebase Map from Previous JRE Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Codepage Setting . . . . .x and 4. . . . . . . . . . . . . . . . . . . 153 Third-Party Certificate Authorities. 160 Windows Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

viii | Contents TIBCO Hawk Installation and Configuration .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Rulebase Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Adding the rvrd Service Value to the Windows Registry . . . . . . . . 115 The TIBCO Hawk Services in the Windows Registry Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Agent Configuration Tab . . . . . . . . . . . . . . 89 Advanced Configuration . . . . . . . . . . . . 105 TIBCO Hawk Event Service Dialog . . . . . . . . . 150 TIBCO Hawk Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 AMI Rendezvous Session Configuration . . . . . . . . . 94 Display Configuration . . . . . . . . . 105 Add AMI Rendezvous Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| ix Figures Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 General Configuration . . . . . . . . . . . . . . . . . . 146 AMI Communication Architecture . . . . . . . . . . . . 120 Certified Model Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Sample Routing Daemon Configuration for TIBCO Hawk Messaging . . . . . . . . . . . . .

x | Figures TIBCO Hawk Installation and Configuration .

. . . . . . . . . . . . . . . . . . .cfg Functions and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Supported Windows Platforms . . Startup Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 JRE Search Location on HP-UX . . . . . . . . . . . . . . . . . . . 178 TIBCO Hawk Installation and Configuration . . . . . . . . . . . . . . . 54 -M RuleBaseEngine Options . . . . . . . . . . . . . 63 hawkhma. . . . . . . . . . . . . . 67 Access Control File Settings . . . . . . . . . . . . . . . . . . . . . . . 26 Recommended JRE Versions and Download Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 TIBCO Hawk Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 hawkevent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 -M Self Options . . . . . . . . . . . . . . . . .cfg Functions and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 -M LogfileMicroAgent Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 JRE Search Location on Solaris . . . . . . . . . . . . . . . . . . 9 JRE Search Location on Linux . . . . . . . .cfg Options . . . . . 168 Code Page Identifiers. . . and Configuration Files . . . . . . . . . . . . . . . 48 hawkagent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 hawkdisplay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| xi Tables Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Table 22 JRE Search Location on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 TIBCO Hawk Files and Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Supported UNIX Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .cfg Modules and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 UNIX Installation tar Package Filenames. . . . . . . . . . . . . . . 24 Required Disk Space in the Temp and Installation Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 -M TIBProtocolAdapter Options . . . . . . . . . . . . . . . . . . . . 8 JRE Search Location on AIX . . . . . .

xii | Tables TIBCO Hawk Installation and Configuration .

txt file for the availability of this software version on a specific operating system platform. page xiv How to Contact TIBCO Customer Support. Microsoft Windows XP. and OS/400. not all operating system platforms for a specific software version are released at the same time. This manual covers the installation of the TIBCO Hawk™ software on Microsoft Windows 2000. HP-UX. Solaris. page xvi TIBCO Hawk Installation and Configuration . This manual assumes you are familiar with TIBCO Rendezvous architecture and the concepts of system monitoring.| xiii Preface This software may be available on multiple operating systems. Linux. Custom configuration is also covered in this manual. However. Please see the readme. Compaq TRU64 UNIX. Topics • • Related Documentation. AIX.

instructions for using TIBCO Hawk Display. An installation FAQ is included. TIBCO Hawk Documentation The following documents form the TIBCO Hawk documentation set: • TIBCO Hawk Release Notes Contains late-breaking news and information. It covers the AMI protocol. AMI messages. and a glossary. a set of Java interfaces that allow you to manage and interact with TIBCO Hawk agents and monitor alerts generated by these agents. Programmers should then refer to the appropriate language reference for the AMI API. and open and closed issues. All books in the documentation set refer to features explained in this book. It contains step-by-step instructions for installing TIBCO Hawk software on various operating system platforms. • • • • • • • • • TIBCO Hawk Installation and Configuration . once it is installed. migration paths. TIBCO Hawk Console API Reference Contains detailed descriptions of each class and method in the TIBCO Hawk Console API. TIBCO Hawk Administrator’s Guide This manual includes basic descriptions of TIBCO Hawk concepts. TIBCO Hawk Installation and Configuration Read this book first. and the TIBCO Hawk security framework and its classes. The TIBCO Hawk Application Management Interface (AMI) exposes internal application methods to TIBCO Hawk. TIBCO Hawk AMI C++ Reference Contains detailed descriptions of each datatype and function in the TIBCO Hawk C++ AMI API. TIBCO Hawk Configuration Object API Reference Contains detailed descriptions of each class and method in the TIBCO Hawk Configuration Object API. a comprehensive FAQ. as well as descriptions of new features. the AMI Workbench development tool. TIBCO Hawk AMI Java Reference Contains detailed descriptions of each class and method in the TIBCO Hawk Java AMI API. It also describes how to configure the software for specific applications. TIBCO Hawk Methods Reference A reference to the microagents and methods used by a TIBCO Hawk Agent for system and application monitoring.xiv | Related Documentation Related Documentation This section lists documentation resources you may find useful. monitoring strategies with examples. TIBCO Hawk AMI C Reference Contains detailed descriptions of each datatype and function in the TIBCO Hawk C AMI API. TIBCO Hawk Programmer’s Guide All programmers should read this manual.

Joy. TIBCO Adapter SDK™ software. and Steele TIBCO Hawk Installation and Configuration . • The Java Language Specification by Gosling.Preface xv | Other TIBCO Product Documentation You may find it useful to read the documentation for the following TIBCO products: • • TIBCO Rendezvous™ software: This is TIBCO’s real-time transport layer that is used by TIBCO Hawk. Third Party Documentation You may find the following third-party documentation useful. including TIBCO AdapterAdministrator™ and TIBCO Repository™: These related products are used to manage TIBCO ActiveEnterprise data and metadata.

If you do not have a username. you can request one. TIBCO Hawk Installation and Configuration . and information about getting started with TIBCO Product Support. visit this site: http://support.xvi | How to Contact TIBCO Customer Support 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.jsp • If you already have a valid maintenance or support contract. • For an overview of TIBCO Support Services. visit this site: http://www.com/services/support/default.tibco.tibco.com Entry to this site requires a username and password.

as well as how to configure the software for specific applications after installation. Not all components run on all platforms. its components. This book provides instructions for installing the TIBCO Hawk software on each software platform. so determine what is supported on your system before beginning installation and configuration. Topics • Components of the TIBCO Hawk System.|1 Chapter 1 Overview of the TIBCO Hawk System This chapter gives a basic overview of the TIBCO Hawk monitoring system. page 2 TIBCO Hawk Installation and Configuration . and the components supported on the various platforms.

2

| Chapter 1

Overview of the TIBCO Hawk System

Components of the TIBCO Hawk System
The TIBCO Hawk monitoring system consists of the following main software components. TIBCO Hawk Agent A TIBCO Hawk agent is an autonomous process that resides on each computer and monitors systems and applications on that computer. Agents run independently of the TIBCO Hawk Display. Agents operate autonomously and are active whenever the operating system they monitor is active. Agents use sets of rules, called rulebases, to configure system management, status, and automation tasks. A TIBCO Hawk agent must be installed on each computer you wish to monitor. TIBCO Hawk Microagent A TIBCO Hawk Microagent (HMA) is a partner process to the TIBCO Hawk agent and provides the local agent with methods for monitoring the host operating system. Like the agent, a TIBCO Hawk Microagent is generally installed on each computer you wish to monitor. TIBCO Hawk Display Program The TIBCO Hawk Display program is used by system administrators to view network health and to create rulebases (sets of rules that automate monitoring activities). A TIBCO Hawk Display should be installed on any computers you wish to use for monitoring the network or for building rulebases. TIBCO Hawk Event Service The TIBCO Hawk Event Service is a process that records TIBCO Hawk alerts and changes in agent status. When communication with an agent is lost, the Event Service can invoke a user-provided script. Alerts and notifications can be recorded to log files or a database. Typically, the TIBCO Hawk Event Service is installed on a minimal number of computers in the network.

TIBCO Hawk Installation and Configuration

|3
Chapter 2

Installation Overview

This chapter provides an overview of the installer program. Appendix C, TIBCO Hawk Directories and Files, contains a complete list of the files and folders installed for the various platforms. Installing TIBCO Hawk on Windows updates the system path to include TIBCO Rendezvous 7.2. If you have TIBCO applications installed that use Java, and if those applications are using the TIBCO Rendezvous bundled in TRA 5.1.x (instead of a separately installed TIBCO Rendezvous), the applications will not be able to start the TIBCO Rendezvous daemon, rvd.exe, after you install TIBCO Hawk. To allow the previous TIBCO applications to start rvd.exe again, remove the TIBCO Rendezvous 7.2 directory from the system path (for example, c:\tibco\tibrv\bin). This will not affect the operation of TIBCO Hawk. TIBCO applications that use Java include TIBCO Adapter 4.x, TIBCO Designer 4.x, TIBCO BusinessWorks 5.x, TIBCO BusinessWorks 5.x, and others.

Topics
• • • Installer Overview, page 4 Uninstalling TIBCO Hawk, page 5 Installation Registry and History, page 6

TIBCO Hawk Installation and Configuration

4

| Chapter 2

Installation Overview

Installer Overview

Installation Directory
If this is the first TIBCO software product you are installing on the system, you can specify the installation directory where TIBCO Hawk will be installed. On Microsoft Windows, the default installation directory is C:\tibco\hawk. On UNIX, the default installation directory is /opt/tibco. If you already have a TIBCO 5.x product on your machine and you install TIBCO Hawk, the installer will automatically select the TIBCO 5.x product installation directory. You cannot choose a different location. If you wish to install TIBCO Hawk in a different location, you must first completely uninstall all TIBCO 5.x products from the machine. install-path The directory into which you install TIBCO Hawk is referred to in this documentation as install-path. For example, if you accept the default installation path on Windows, install-path is
C:\Tibco\hawk.

Installing TIBCO Hawk over Previous Releases
You do not need to uninstall the previous or current version of TIBCO Hawk on the system before installing the new version. If the installer detects an existing TIBCO Hawk version, it will ask you if you want to overwrite it or cancel the installation. All files originally installed by TIBCO Hawk are replaced with the new versions. Files that you created are not removed or modified, even if they are in the same directories as the original TIBCO Hawk files. If any TIBCO Hawk files are locked (for example, if they are open or in use) when you install the new version, the installer places them in a temporary location and performs the actual overwrite the next time you reboot. See Uninstalling TIBCO Hawk on page 5.

TIBCO Hawk Installation and Configuration

Uninstalling TIBCO Hawk 5

|

Uninstalling TIBCO Hawk
The uninstaller removes all files that were installed as a part of TIBCO Hawk installation, even if those files were modified by the user or the application. Files that were created by the user are not deleted or modified. Make sure you have a backup of user-modified files before proceeding with the uninstallation.

Product Dependencies
TIBCO Designer and TIBCO Runtime Agent (TRA) are dependent on TIBCO Hawk being present on the machine. If you have TIBCO Designer or TRA installed on your machine, you will need to uninstall them before uninstalling TIBCO Hawk, in the following order: 1. Uninstall TIBCO Runtime Agent (tra-install-path\version\uninst) and any of its product dependencies. 2. Uninstall TIBCO Hawk (hawk-install-path\hawk\uninst). If you do not have TIBCO Designer or TRA installed on your machine, you can uninstall TIBCO Hawk without prerequisite.

Uninstallation Instructions
Microsoft Windows Uninstall the product(s) in the order shown above, using one of the following methods: • • • Click Start>Programs>TIBCO>TIBCO Runtime Agent>Uninstall. Use Add/Remove Programs from the Control Panel. Navigate to the _uninst directory located in each of the folders listed above and invoke the Tibuninstall.exe program.

UNIX Systems Uninstall the product(s) in the order shown above, by navigating to the _uninst directory located in each directory shown and invoke the Tibuninstall.bin program.

TIBCO Hawk Installation and Configuration

Each time an installation or uninstallation is performed. or delete any of the registry vpd files. TIBCO Hawk Installation and Configuration .properties SystemDrive:\WINNT\vpd. The installer uses the registry file during subsequent installations.properties. The location of the registry varies by platform.systemName If installation is performed by a regular user (non-root).tibco.tibco.systemName • Linux: in the /root directory: /root/vpd.properties User_Home_Directory/vpd.properties /usr/lib/objrepos/vpd.6 | Chapter 2 Installation Overview Installation Registry and History The installer maintains an installation registry consisting of two files with the prefix vpd.properties. the installation registry is maintained in the following files in the user's home directory: User_Home_Directory/vpd. Microsoft Windows Platform Registry On Microsoft Windows. Do not edit. move.tibco. the installation registry consists of the following files: SystemDrive:\WINNT\vpd.properties.tibco.properties.systemName UNIX Platform Registry If installation is performed by super-user (root).systemName • AIX: in the /usr/lib/objrepos directory: /usr/lib/objrepos/vpd. This section explains where the registry files are located on each platform.tibco.properties User_Home_Directory/vpd.properties. which stands for Vital Product Database. rename.properties /root/vpd. entries are appended to the file.xml.systemName Installation History The installer creates a file called TIBCOInstallationHistory. modify. the installation registry is maintained in the following locations: • Solaris and HP-UX: in the root user’s home directory: User_Home_Directory/vpd.

1 in a set of standard locations by default. When you start installation.3.1. the installer loads and completes more quickly and the product uses less disk space (because it doesn’t need to extract and save its own JRE). you can run the uninstaller using -is:javahome to point to a different JRE location. then add a JAVA_HOME variable and set its value. • Include the command line option installer. If the JRE is removed at any time. The installer is Java-based.3. If the installer can use a JRE 1. For example: — Windows suite installer: <exe> — Other installers: <exe_or_bin> -is:javahome when launching the -a -is:javahome C:\java\JRE\1.1 on your system. If it doesn’t find one.3. it extracts its own JRE into a temporary space and uses that JRE to launch itself.3. JAVA_HOME export — Unix C-shell: setenv JAVA_HOME /opt/jre1.1 already on the system.1.1 — Microsoft Windows (setting JAVA_HOME in a command prompt will not work): Choose Start-> Settings-> Control Panel-> System-> Environment-> System Variables or User Variables. It uses that same existing JRE for uninstallation.3.3. It then copies the JRE into install-dir for use at uninstallation.3. How the Installer Searches for JRE The installer searches for JRE 1.3.Installation Registry and History 7 | The installation history file is created in the same directory as the installation registry. These standard locations are platform-specific and are listed in JRE Search Locations on page 8. Specifying the JRE Location This section explains how the installer uses JRE and how you can speed up installation and reduce disk space requirements by using an existing JRE 1. It is bundled with JRE 1.1 TIBCO Hawk Installation and Configuration . but you can speed it up further by using one of the following actions to specify the JAVA_HOME location before you launch the installer: • Set the environment variable JAVA_HOME or JDKHOME to the JRE home directory.1 on the target system.1 -is:javahome /opt/jre1. The JRE search is very quick.3. For example: — Unix Bourne or Korn shell: JAVA_HOME=/opt/jre1. the installer looks for an existing JRE 1.

3.1 Directory JRE Search Location on Solaris Table 2 JRE Search Location on Solaris Location Environment Path Description JAVA_HOME JDKHOME /usr/jre1.8 | Chapter 2 Installation Overview JRE Search Locations The following tables list the search locations for the various supported platforms.3\JavaHome \HKEY_LOCAL_MACHINE\SOFTWARE\ JavaSoft\ Java DevelopmentKit\1.1 JRE Search Location on HP-UX Table 3 JRE Search Location on HP-UX Location Environment Path Description JAVA_HOME JDKHOME /opt/java1. JRE Search Location on Windows Table 1 JRE Search Location on Windows Location Environment (set in ControlPanel.3 /opt/java1.1 /usr/jdk1.3.3.1 \JavaSoft\JRE\1.3.3.3.3/jre TIBCO Hawk Installation and Configuration .3.3.1 /opt/jre1.1 \Java\JRE\1.3. The installer searches for and uses only JRE 1. It will not use a different version even if the other version exists on the system or is specified using an environment variable or command-line option.1.3.3\JavaHome \Program Files\JavaSoft\JRE\1.1 /opt/jdk1.1 /opt/java1. not in command prompt) Registry Description JAVA_HOME JDKHOME \HKEY_LOCAL_MACHINE\SOFTWARE\ JavaSoft\Java Runtime Environment\ 1.1 /usr/java1.

3.3 /opt/jre1.3 /opt/j2re1.1 TIBCO Hawk Installation and Configuration .3 /usr/local/jre1.Installation Registry and History 9 | JRE Search Location on AIX Table 4 JRE Search Location on AIX Location Environment Path Description JAVA_HOME JDKHOME /usr/jdk_base /usr/jdk_base /usr/java131 /usr/java131 JRE Search Location on LINUX Table 5 JRE Search Location on Linux Location Environment Path Description JAVA_HOME JDKHOME /usr/jre1.

10 | Chapter 2 Installation Overview TIBCO Hawk Installation and Configuration .

page 12 Installing TIBCO Hawk. page 15 Post-Installation Tasks.| 11 Chapter 3 Installing on Microsoft Windows This chapter explains how to install and uninstall TIBCO Hawk on computers running the Microsoft Windows 2000 or XP operating system. Information in this chapter applies to all three platforms unless otherwise noted. page 18 TIBCO Hawk Installation and Configuration . Topics • • • Installation Prerequisites.

If you do not. TIBCO Hawk Installation and Configuration . it is recommended that the server be in Install mode and that you have administrator privileges.12 | Chapter 3 Installing on Microsoft Windows Installation Prerequisites Read this section before you start installation. the installer will exit. which allows users to run applications. Installing on a Windows 2000 Terminal Server A Windows 2000 terminal server has two modes: Execute and Install. or consult Microsoft Windows online help. If not. To install TIBCO Hawk. Installing to a Networked Drive If you intend to install the product onto a networked drive. Supported Operating Systems The following tables lists the supported Windows platforms: Table 6 Supported Windows Platforms OS Microsoft Windows 2000 with Service Pack 3 (build 2195) Microsoft Windows XP (build 2600) Microsoft Windows 2003 Server Hardware Intel Pentium Intel Pentium Intel Pentium User Privileges You must have administrator privileges to install TIBCO Hawk. You must then log out of the system and log in as a user with administrator privileges. go to the machine so you can install locally. you must have permissions to write to that drive. The default mode is Execute. some Windows 2000 Terminal Server features will not be available for TIBCO Hawk. If you do not know how to do this.

the entire package is extracted into a temporary directory. see Specifying the JRE Location on page 7. To reduce this amount. the installation registry is maintained in your user home folder. If some of the required disk space is taken by another process during installation. see Specifying the JRE Location on page 7. To reduce this amount. Temp Directory At least 152MB free space is required in the temp directory. TIBCO Hawk Installation and Configuration . The installer will proceed only if sufficient free disk space is available in the installation directory. typically one of the following: • • • SystemDrive:\Temp SystemDrive:\Documents Settings\user_name\Local Settings\Temp Before actually installing the files. the installer calculates the disk space that the selected components will require in the installation directory. the installer may fail and display a failure message. During installation. the installation registry is maintained in the SystemDrive:\WINNT\ folder. If you install in the Install mode. RAM All platforms require at least 256 MB RAM.Installation Prerequisites 13 | If you install in Execute mode. Installation Directory At least 35MB free space is required in the TIBCO Hawk installation directory. Check your server mode by typing the following command: C:\> change user /query You can change the server mode to Install by typing the following command: C:\> change user /install Disk Space and Memory This section lists the minimum free disk space and memory required for each platform.

3.2.3. The TIBCO Hawk installation package includes TIBCO Rendezvous 7.1.1_01. The installer asks you during installation to verify that JRE is on the system.3. If a new version of JRE is installed after installing TIBCO Hawk software.3. install JRE.4. In this case.1. TIBCO Software TIBCO Rendezvous 6.tkt file for that machine.1_02. TIBCO Hawk Installation and Configuration . or 1. you must manually set the Java Home Directory value using the Advanced Settings options of the TIBCO Hawk Configuration Utility. you will not need additional TIBCO Rendezvous licenses unless you will be running TIBCO Rendezvous Routing Daemon (RVRD) processes on a particular machine.9 or higher is required. 1. If it is not. with any available patches. See Java Runtime Configuration on page 95 for more information. JRE TIBCO Hawk requires Java Runtime Environment (JRE) version 1.14 | Chapter 3 Installing on Microsoft Windows Software The following software is required as indicated on the target machine. 1. then start TIBCO Hawk installation again. If you have already installed TIBCO Rendezvous software on a network-wide basis. on the target machine.1_03. you need a valid RVRD license in the tibrv. you must exit the installer. TIBCO Hawk does not support Java 1. with any available patches.

Installing TIBCO Hawk 15

|

Installing TIBCO Hawk
Before you begin installation, close all open programs. If any errors appear during installation, consult Appendix B, Troubleshooting, page 159, for possible solutions.

Installation Media
You can either download the TIBCO Hawk installation package or install the components from a CD.

Typical and Custom Installation
During installation, you can choose a typical installation or a custom installation. • • A typical install has minimal prompts and installs standard components in default locations. A custom install prompts you to choose which components of the product suite to install and installs only those components.

The following sections discuss the different modes of installing TIBCO Hawk.

Installation Modes
The installer allows you to install in different modes. Each mode is supported on all platforms. • •
GUI mode allows you to select which components to install, where to install them, and so on. GUI mode is the installer’s default mode. Console mode allows you to run the installer from the command line and allows you to select which components to install. You can create a response file or template file using console mode. Silent mode installs in console mode without prompting you for input. It

installs using either the default settings or a response file that was saved during an earlier installation. You can use any of the following options to install TIBCO Hawk: • • • Install Using GUI, page 31 Install Using Console, page 31 Install in Silent Mode, page 31

TIBCO Hawk Installation and Configuration

16

| Chapter 3

Installing on Microsoft Windows

• • •

Install and Generate a Response File, page 31 Install and Generate a Template File, page 32 Install Using a Response File, page 32

These options and the instructions for installing TIBCO Hawk are provided in the following sections. Install Using GUI GUI mode performs the installation in an interactive graphical interface. The installer prompts you for values specific to your environment. To install, doubleclick the icon named TIB_hawk-suite_4.2.1_w32.exe. Install Using Console Console mode allows you to install the software from a Windows command window. The installer prompts you for values. When installing in console mode you move through the installation process as shown: • • • • Enter moves forward in the installer. 2 returns to the previous screen. 3 cancels the installer and exits the installation or uninstallation. 4 redisplays the current screen.

To install from a Windows command window, type:
TIB_hawk-suite_4.2.1_w32.exe -is:javaconsole -console

Install in Silent Mode This mode installs TIBCO Hawk in a Windows command window without prompting you for any information during installation. It installs TIBCO Hawk using default values. To install from a Windows command window, type:
TIB_hawk-suite_4.2.1_w32.exe -silent

Install and Generate a Response File This installation is performed in a Windows command window. The installer prompts you for information during installation and saves your answers in a response file. The response file can be used during subsequent installations to create another instance using the same values as the original installation, either with or without prompting for changes.

TIBCO Hawk Installation and Configuration

Installing TIBCO Hawk 17

|

Instructions for using the response file during subsequent installations are given in Install Using a Response File, below. To install from a Windows command window, type the following (note there is no space between -options and -record):
TIB_hawk-suite_4.2.1_w32.exe -is:javaconsole -console -options-record responseFilepath

Install and Generate a Template File This installation is performed in a Windows command window. The installer generates a template file, similar to the response file described above except that the values you enter during installation are not saved in the file. You can use a text editor to add those values later, resulting in a response file that can be used in subsequent installations. To install from a Windows command window, type the following (note there is no space between -options and -template):
TIB_hawk-suite_4.2.1_w32.exe -options-template

templateFilepath

Install Using a Response File This installation is performed in a Windows command window using a response file or an edited template file. Instructions for creating a response file and a template file are given above. The response file can be used in silent mode or interactive mode.
Silent Mode

In silent mode, you are not prompted during installation. TIBCO Hawk is installed using the values in the response file. To install from a Windows command window, type:
TIB_hawk-suite_4.2.1_w32.exe -silent -options

responseFilepath

Interactive Mode

In interactive mode, you are prompted for values during installation. The values in the response file are presented as suggested defaults. • To install from a Windows command window, type:
TIB_hawk-suite_4.2.1_w32.exe -options

responseFilepath

TIBCO Hawk Installation and Configuration

18

| Chapter 3

Installing on Microsoft Windows

Post-Installation Tasks
After the installation program has finished, it automatically starts the TIBCO Hawk configuration utility, described in Chapter 7, Using the Configuration Utility. Before using the configuration utility, perform the following post-installation tasks as noted.

Reboot the System
If you upgraded to TIBCO Rendezvous 7.2.0 during installation, reboot the system now.

Verify the Installation
To verify the installation, check that all directories and files have been added correctly. For details, see Appendix C, TIBCO Hawk Directories and Files, page 167.

Set Disk Counters (Windows 2000 and Windows XP Only)
In Windows 2000, the default is Physical Disk object turned on and the Logical Disk object turned off. In addition, the logical disk information is in the MMC under the storage section instead of in performance. As a result, the LogicalDisk method is not available on Windows 2000 under the HMA performance microagent. However, the default Windows 2000 hawk rulebase has a rule that monitors System Events, and a System Event is posted when the disk gets low. To obtain this performance counter data for logical drives or storage volumes in Windows 2000: 1. Type diskperf 2. Press Enter. 3. Reboot the system. For complete details, see Microsoft article Q253251.
-yv

at a command prompt.

TIBCO Hawk Installation and Configuration

(Refer to the Windows documentation for help on the fields required by the New User dialog. skip to step 3. The selected user account appears in the Add Names list in the lower half of the dialog. The user account is now in the Members list.Post-Installation Tasks 19 | Configure Windows Services Logon Account (Optional) The TIBCO Hawk software components (TIBCO Hawk agent. do the following. the installation program configures the TIBCO Hawk Windows services to use the built-in system account. Task A Set up the Administrator User Account You can use an existing user account or create a new one under which to run the TIBCO Hawk services. 2. If you are creating a new user to be the administrator. 1. and TIBCO Hawk Event Service) are installed as Windows services. This is the account used by the majority of Windows services. under which the service can log on and run. Choose Start>Programs>Administrative Tools>User Manager. Click Add to access the Add Users and Groups dialog. require a Windows user account. TIBCO Hawk Installation and Configuration . In the lower half of the User Manager window. Complete the New User dialog and click OK to return to the User Manager window. Set up the Administrator User Account. b.) 3. If you want to use an existing account that doesn’t already have administrator privileges. If you are adding administrator privileges to an existing account. Change the Logon Account for TIBCO Hawk Windows Services. Select the desired user account and click Add. you must do the following: a. double-click the Administrators group. 6. To set up the administrator account. These instructions follow. 4. therefore. Windows services run independently of any logged-on user and. Give the Administrative User the "Log On as Service" Privilege. If you don’t want to use the system account. you must assign administrative privileges to it. Choose the User>New User menu item. proceed as follows: a. Click OK to return to the User Manager window. 7. By default. b. Click OK to add the user to the group and return to the Group Properties dialog. You see the New User dialog. You see the Local Group Properties dialog. c. 5. HMA.

select your machine name. Repeat from step 2 for each TIBCO Hawk Windows service in the services list. The Local Group Members box appears. choose the line Log on as a service. From the drop-down list labeled Right. 5. In the List Names From list box. In the Names box. In the User Rights Policy dialog do the following: a. then choose User>Exit to leave this window. 1. 4. choose the menu item Policies>User Rights. You see the Services dialog. Click OK to return to the User Manager window. 5. b.20 | Chapter 3 Installing on Microsoft Windows Task B Give the Administrative User the "Log On as Service" Privilege If your administrator user account doesn’t already have the "Log on as a service" right. You see the User Rights Policy dialog. c. Task C Change the Logon Account for TIBCO Hawk Windows Services Now you must change the logon account for the TIBCO Hawk Windows services to the selected administrative user account. 3. In the User Manager window. Click OK to grant the selected user the "Log on as a service" right and return to the User Rights Policy dialog. Select the desired user account and click Add. 3. b. select the Administrators group and click Members. Navigate to the desired user name and select it. 2. 4. You see the Service dialog. In the Log On As panel. Click the Show Advanced User Rights check box. Select the desired TIBCO Hawk service from the list and click Startup. Click OK to save your action and return to the Services dialog. Choose Start>Settings>Control Panel and double-click on the Services icon. The Add Users and Groups dialog appears. Click Add. 1. as follows. c. click This Account and enter the desired user account and password. give it this right as follows. The user account you selected now appears in the Grant To box. TIBCO Hawk Installation and Configuration . The desired user account appears in the Add Names box at the bottom of the Add Users and Groups dialog. as follows: a. 2. if it is not selected.

Select the TIBCO Hawk Agent service from the list and click Startup. TIBCO Hawk Installation and Configuration . c. You see the Service dialog. Click OK to save your action and return to the Services dialog. In the Log On As panel. You can now configure processes started by the TIBCO Hawk agent to run in the foreground. This is optional. click System Account and Allow Service to Interact with Desktop enter the desired user account and password. Click Close to exit the Services dialog. You must reboot the machine for the TIBCO Hawk service configuration changes to take effect. if you don’t want to do this. b. skip to step 7. then close the Control Panel window. 7.Post-Installation Tasks 21 | 6. a.

22 | Chapter 3 Installing on Microsoft Windows TIBCO Hawk Installation and Configuration .

page 29 Installing the TAR File. page 34 Starting TIBCO Hawk Components Automatically at System Boot. page 33 Post-Installation Tasks. page 24 Installing TIBCO Hawk on UNIX.| 23 Chapter 4 Installing on UNIX This chapter explains how to install and uninstall the TIBCO Hawk monitoring system on computers running the UNIX operating system. page 35 TIBCO Hawk Installation and Configuration . Topics • • • • • Installation Prerequisites.

6 Solaris 2.2. Supported Operating Systems The following platforms are supported.2 IBM RS/6000 Intel x86 None required for TIBCO Hawk.2 IA64 (Itanium) None required for TIBCO Hawk.1 AIX 5.1 or later. Apply 5.4 xlC libraries as indicated by APAR IY14529 AIX 4.x HPPA Hardware Sun SPARC Sun SPARC (32. HP-UX 11. with patches required as listed. TIBCO Hawk Installation and Configuration . Table 7 Supported UNIX Platforms (Sheet 1 of 2) OS Solaris 2. ARPA patch PHNE_20436 (PHNE_17662).2 LINUX 2. Requires kernel 2.7 or later and glibc 2.14 or later and glibc 2.9 HP-UX 11. None required for TIBCO Hawk. Requires kernel 2. LINUX 2.4 LINUX AS 2.and 64-bit) Intel (32-bit) Patches None required for TIBCO Hawk.7 Solaris 2.4.2.0 Intel x86 None required for TIBCO Hawk.00 64 bit systems. For HP-UX 11.4 or later. HP-UX kernel patch PHKL_27282 is required.24 | Chapter 4 Installing on UNIX Installation Prerequisites Read this section before you start installation.1 LINUX AS 3.0. If using TIBCO Rendezvous: PHNE_26250. Make sure that all patches required by other TIBCO products or third-party software (such as the JRE) are installed before installing TIBCO Hawk. and streams patch PHNE_20008 (PHNE_17794) are required.3 AIX 5.0.8 Solaris 2.

change the permissions and ownership of the tibhawkhma binary to root after installation.0 TRU64 UNIX 5. or stop processes. as shown: #> chmod 4555 tibhawkhma #> chown root:bin tibhawkhma Different users can install the same product at different locations. creates setuid permissions with root ownership for the TIBCO Hawk HMA binary. If a non-root user installs TIBCO Hawk.x (including 5. TIBCO Hawk Installation and Configuration . See Installation Registry and History on page 6 for more information. accordingly. Before actually installing the files. TIBCO Hawk HMA Process Runs as root The TIBCO Hawk HMA process must run as user root to operate correctly. Installer Privileges TIBCO Hawk can be installed by a regular (non-root) user or super-user (root). If some of the required disk space is taken by another process during installation. If the required JRE version is already on your system. It cannot manipulate. The HMA only reads system information and cannot perform any actions. The installer will proceed only if sufficient free disk space is available in the installation directory. Disk Space and Memory During installation. the installer may fail and display a failure message.1A) Hardware HP Alpha Patches (Cont’d) None required for TIBCO Hawk.Installation Prerequisites 25 | Table 7 Supported UNIX Platforms (Sheet 2 of 2) OS TRU64 UNIX 4. the installer calculates the disk space that the selected components will require in the installation directory. significantly less disk space is required in the temp directory. Product dependencies at install time are resolved at user level through the installation registry maintained at user's home directory. modify. The installation program. Note: CXXLIB631 Compaq C++ Run-Time Library (libcxx) is required. See Specifying the JRE Location on page 7. the entire package is extracted into a temporary directory.

bin -is:tempdir /new_tmp Table 8 Required Disk Space in the Temp and Installation Directories Temp Directory Free Space 15 MB in /var/tmp 85 MB in /var/tmp 20 MB in /tmp 15 MB in /tmp 65 MB in user’s home directory Installation Directory Free Space 177 MB 635 MB 186 MB 177 MB 177 MB Operating System Solaris (Sun SPARC and Intel) HP-UX AIX LINUX TRU64 UNIX Home Directory The user's home directory must at least have 500 KB of free disk space for the installation registry.9 or higher is required. See Installation Registry and History on page 6. the command is: TRA. RAM All platforms require at least 256 MB RAM.0-suite_s4_58. where /new_tmp has sufficient free disk space: -is:tempdir /new_tmp For example. TIBCO Hawk Installation and Configuration .0.5. you can use a different temp directory by including the following option when starting the installer. Software The following software is required as indicated.26 | Chapter 4 Installing on UNIX If your system does not have sufficient free disk space in the temp directory listed in the table below. TIBCO Software TIBCO Rendezvous 6. with any available patches. on SUN SPARC Solaris.

1. The following table lists web sites where you can download the recommended versions.6 and 2. a GUI environment such as CDE (X Windows) is required. you will not need additional TIBCO Rendezvous licenses unless you will be running TIBCO Rendezvous Routing Daemon (RVRD) processes on a particular machine.1 to avoid conflicts. In this case. with any available patches.compaq. Table 9 Recommended JRE Versions and Download Sites Platform Solarisa (Sun SPARC) Solaris (Intel) HP-UX AIX LINUX TRU64 UNIX Recommended JRE Version 1. GUI Environment (optional) If you are running the installer in GUI mode. or 1.1_02 1.com/j2se/ http://www.3.1_01. TIBCO Hawk does not support Java 1.7. JRE is not included with the TIBCO Hawk installation package.3.6 (respectively) be removed before you install JRE 1. TIBCO Hawk Installation and Configuration .3.3.1.sun. On Solaris 2.Installation Prerequisites 27 | If you have already installed TIBCO Rendezvous software on a network-wide basis.3.3. It is not required for a console or silent installation. JRE TIBCO Hawk requires Java Runtime Environment (JRE) version 1.com/j2se/ http://java. run pkgrm SUNWjvjit and pkgrm SUNWjvjrt.com/j2se/ http://www.tkt file for that machine.3.com/java/download/index. on the target machine.3.com/products1/unix/java/ http://www.1.3.1_02 1. you need a valid RVRD license in the tibrv.1.1.3.sun.1_02 plus JIT 1.3 or 1.3.1_03.html a. it is strongly recommended that the factory-installed JDK 1.4. Also see DISPLAY Variable Error on page 160. 1.1_02 JRE Download Site http://java.1_02 1. To remove the JDK.hp.com/java/jdk/aix/supported/118ga/ http://java.1_02 1.ibm.sun.1_02.

Run ulimit .7 Only) Solaris 2. in PS/2 3. Before you start TIBCO Hawk installation. which allows efficient use of threads within the TIBCO Hawk agent.8 comes with a default file descriptor setting of 1024. Set Environment Variable (Compaq Tru64 UNIX Only) Installation on Compaq Tru64 UNIX requires a POSIX-compliant Bourne Shell.8: 1. enter kdmconfig and select Built [3 button mouse]. Configure the two-button mouse as follows: 1. previous releases of Solaris have a default file descriptor setting of 64.28 | Chapter 4 Installing on UNIX Default File Descriptor Setting (Solaris 2. and ideally to 1024.n 256 (or whatever number is desired) to increase the setting. From the command-line prompt. This should be increased to at least 256. However.6 and 2. To increase the default file descriptor in Solaris releases prior to 2. set the BIN_SH environment variable as follows: BIN_SH=xpg4. Reboot the system. Reconfigure Two-Button Mouse Devices (Solaris Only) Solaris systems using a two-button mouse must be configured with the three-button mouse setting. TIBCO Hawk Installation and Configuration . navigate to /usr/bin/sh. As the root user. 2. the TIBCO Hawk installer will abort with the following error: ^D@AA: is not an identifier. 2. Log in as superuser (root). export BIN_SH // Bourne shell setenv BIN_SH xpg4 // C-shell If BIN_SH is not set properly.

stop all TIBCO Rendezvous processes before installing TIBCO Hawk.tar TRU64 UNIX 5. HP-UX 11i HP-UX IA64 AIX 4.2 TIB_hawk-suite_4. If any errors appear during installation.0.tar TIB_hawk-suite_4. Troubleshooting.1_lnx86_20.tar TIBCO Hawk Installation and Configuration .3 TIB_hawk-suite_4.tar tar Package Filename TIB_hawk-suite_4.2.1_s4_58.7 (Sun SPARC) Solaris 2.0. Installation Packages The following table lists the platform-specific installation packages.tar TIB_hawk-suite_4.9 (Sun SPARC) Solaris 2.0 TIB_hawk-suite_4.2.tar TIB_hawk-suite_4.2.1A) LINUX 2.2.2.1_h7_110.1_i86_57.1_rs_43.2 TRU64 UNIX 4.2. Table 10 UNIX Installation tar Package Filenames OS Solaris 2.tar AIX 5.6 (Sun SPARC) Solaris 2.1_s4_56.2. if you are upgrading to TIBCO Rendezvous 7.1 AIX 5.1_s4_57. for possible solutions.2.1_alpha_40. close all open applications.tar TIB_hawk-suite_4.7 (Intel) HP-UX 11. On HP-UX.1_s4_58.2. Copy the appropriate tar file from the download site or the CD and unpack it on your system.1_h7_ia64.Installing TIBCO Hawk on UNIX 29 | Installing TIBCO Hawk on UNIX Before you begin installation.tar TIB_hawk-suite_4.x (including 5. consult Appendix B.2.2.8 (Sun SPARC) Solaris 2.tar TIB_hawk-suite_4.

page 31 Install in Silent Mode. page 32 Install Using a Response File.tar Typical and Custom Installation During installation. Console mode allows you to run the installer from the command line and allows you to select which components to install.1 LINUX Advanced Server 3. page 32 TIBCO Hawk Installation and Configuration . page 31 Install Using Console.2. It • installs using either the default settings or a response file that was saved during an earlier installation. The following sections discuss the different modes of installing TIBCO Hawk. where to install them. and so on.4 LINUX Advanced Server 2. • • GUI mode allows you to select which components to install. • • A typical install has minimal prompts and installs standard components in default locations. A custom install prompts you to choose which components of the product suite to install and installs only those components. GUI mode is the installer’s default mode.30 | Chapter 4 Installing on UNIX Table 10 UNIX Installation tar Package Filenames OS LINUX 2. page 31 Install and Generate a Response File. Each mode is supported on all platforms. You can create a response file or template file using console mode.1_lnx86_24. Silent mode installs in console mode without prompting you for input. page 31 Install and Generate a Template File. You can use any of the following options to install TIBCO Hawk: • • • • • • Install Using GUI. you can choose a typical installation or a custom installation.0 tar Package Filename TIB_hawk-suite_4. Installation Modes The installer allows you to install in different modes.

Instructions for using the response file during subsequent installations are given in Install Using a Response File. TIBCO Hawk Installation and Configuration .1_s4_56. below.6.Installing TIBCO Hawk on UNIX 31 | These options and the instructions for installing TIBCO Hawk are provided in the following sections.1_s4_56. To install from a UNIX terminal window. The installer prompts you for values specific to your environment. The installer prompts you for values. To install from a UNIX terminal window. The following examples use the installation package for SUN SPARC Solaris 2. either with or without prompting for changes. type: TIB_hawk-simple_4. The installer prompts you for information during installation and saves your answers in a response file. 3 cancels the installer and exits the installation or uninstallation. 4 redisplays the current screen.2.bin -is:javaconsole -console Install in Silent Mode This mode installs TIBCO Hawk in a UNIX terminal window without prompting you for any information during installation. Install Using Console Console mode allows you to install the software from a UNIX terminal window. The response file can be used during subsequent installations to create another instance using the same values as the original installation. To install.1_s4_56.bin -silent Install and Generate a Response File This installation is performed in a UNIX terminal window. type: TIB_hawk-simple_4.bin. doubleclick the icon TIB_hawk-simple_4. It installs TIBCO Hawk using default values. Install Using GUI GUI mode performs the installation in an interactive graphical interface.2.2. 2 returns to the previous screen. When installing in console mode you move through the installation process as shown: • • • • Enter moves forward in the installer.

bin -options-record responseFilepath Install and Generate a Template File This installation is performed in a UNIX terminal window.bin -options responseFilepath TIBCO Hawk Installation and Configuration . TIBCO Hawk is installed using the values in the response file.bin -options-template templateFilepath Install Using a Response File This installation is performed in a UNIX terminal window using a response file or an edited template file. You can use a text editor to add those values later.1_s4_56.bin -silent -options responseFilepath Interactive Mode In interactive mode. type the following (note there is no space between -options and -template): TIB_hawk-simple_4.32 | Chapter 4 Installing on UNIX To install from a UNIX terminal window. type: TIB_hawk-simple_4.1_s4_56. similar to the response file described above except that the values you enter during installation are not saved in the file.2.2. The values in the response file are presented as suggested defaults.2. you are prompted for values during installation.1_s4_56. type: TIB_hawk-simple_4. To install from a UNIX terminal window. To install from a UNIX terminal window.2.1_s4_56. The installer generates a template file. Instructions for creating a response file and a template file are given above. The response file can be used in silent mode or interactive mode. To install from a UNIX terminal window. Silent Mode In silent mode. resulting in a response file that can be used in subsequent installations. you are not prompted during installation. type the following (note there is no space between -options and -record): TIB_hawk-simple_4.

1. product documentation is not installed on the system. 2.x) that depend on Hawk 4.tar 3. cd to hawkroot/bin and check that the tibhawkhma binary is setuid and is owned by the root user. When TIBCO Hawk is installed using this method. use the following commands to modify it: #> chmod 4555 tibhawkhma #> chown root:bin tibhawkhma TIBCO Hawk Installation and Configuration . To successfully install these TIBCO products on this machine. This installation should only be performed by advanced users. the following command unpacks the tar image for SUN SPARC Solaris 2. For example.0. The tar image is placed on your system when you unpack the tar file on your system as described in Installation Packages on page 29.1 will not be able to recognize or locate this TIBCO Hawk installation.2.2. navigate to the directory that will be HAWK_ROOT.1 Lite product (agent only) included with TRA 5.1_s4_56.6: #> tar -xvf download_directory/TIB_hawk_4. You can view the documentation on the product CDROM in the doc folder at root level or obtain it from the product download site. The following procedure describes how to install TIBCO Hawk using the tar image.1. As root user.2. Subsequent TIBCO product installations will detect the presence of TIBCO Hawk Lite and will complete successfully. After installation. you must install the TIBCO Hawk 4. as shown: #> ls -l tibhawkhma #> -r-sr-xr-x 1 root bin 263320 Oct 30 17:03 tibhawkhma If it is not. Other TIBCO products (such as TIBCO Runtime Agent 5. 1. When you install TIBCO Hawk using this method.Installing the TAR File 33 | Installing the TAR File A tar image is provided as an alternative method of installing TIBCO Hawk on UNIX platforms. an entry for it is not placed in the installation registry.0 when you install TRA 5. and installation of those products may fail.x and TIBCO Administrator 5. Unpack the tar file in that directory.

execute the following command before starting any TIBCO Hawk component: ln -s <RV_HOME>/libtibrvj. see TIBCO Hawk Directories and Files. Task A Verify the Installation Check that all directories and files have been added correctly. page 167. For details. TIBCO Hawk Installation and Configuration . the root user must perform the following post-installation tasks as noted.so Where <RV_HOME> is your TIBCO Rendezvous installation directory.34 | Chapter 4 Installing on UNIX Post-Installation Tasks After installing TIBCO Hawk on UNIX. Task B Modify Permission for tibhawkhma Modify the permissions of the TIBCO Hawk HMA (tibhawkhma) as shown: cd $TIBCO_HAWK_HOME/bin/tibhawkhma chown root tibhawkhma chmod g+s tibhawkhma On the TRU64 UNIX platform.so <RV_HOME>/libtibrvj64.

You can modify this script for your environment. 2. The following sections list the steps involved in starting TIBCO Hawk components automatically at system boot. is provided in the $HAWK_ROOT/samples/etc directory. Open the file $HAWK_ROOT/samples/etc/hawk2 in an editor and make the following changes. Copy the hawk2 file as follows: cp $HAWK_ROOT/samples/etc/hawk2 /etc/init. Edit the line JRE_ROOT=usr/tibco/java to reflect your Java installation directory. It can be used on all supported UNIX platforms. 1. Hawk2. Create a link as follows: ln -s /etc/init. Edit the line: HAWK_ROOT=/usr/tibco/hawk to reflect your TIBCO Hawk installation directory.d/hawk2 /etc/rc2.Starting TIBCO Hawk Components Automatically at System Boot 35 | Starting TIBCO Hawk Components Automatically at System Boot The TIBCO Hawk agent and TIBCO Hawk HMA components can be configured to start automatically during the system boot cycle. Edit the line: RV_ROOT=/usr/tibco/tibrv to reflect your TIBCO Rendezvous installation directory.d/hawk2 3. Refer to the correct section for your operating system. It invokes the starthma and startagent scripts during the boot cycle.d/S99hawk TIBCO Hawk Installation and Configuration . • • • • • Solaris Instructions on page 35 HP-UX Instructions on page 36 AIX Instructions on page 36 TRU64 Instructions on page 37 LINUX Instructions on page 37 Solaris Instructions This section describes how to start TIBCO Hawk components automatically at system boot on a SUN SPARC Solaris or Intel Solaris operating system. A sample autostart script.

AIX Instructions This section describes how to start TIBCO Hawk components automatically at system boot on an IBM operating system. Edit the line JRE_ROOT= directory. Edit the line: HAWK_ROOT=/usr/tibco/hawk to reflect your TIBCO Hawk installation directory. Edit the line: RV_ROOT=/usr/tibco/tibrv to reflect your TIBCO Rendezvous installation directory.d/hawk2 3. Edit the line: HAWK_ROOT=/usr/tibco/hawk to reflect your TIBCO Hawk installation directory. 1. 1. dependent upon your system startup parameters. JRE_ROOT= /usr/tibco/java to reflect your Java installation 2. Open the file $HAWK_ROOT/samples/etc/hawk2 in an editor and make the following changes. Open the file $HAWK_ROOT/samples/etc/hawk2 in an editor and make the following changes.d/hawk2 /etc/rc2.d/Sxxxhawk where xxx is an integer. Add an entry to the /etc/inittab file as follows: # hawk:2:once:<HAWK_ROOT>/samples/etc/hawk2 -start >/dev/console 2>&1 TIBCO Hawk Installation and Configuration . Copy the hawk2 file as follows: cp $HAWK_ROOT/samples/etc/hawk2 /etc/init. Edit the line: RV_ROOT=/usr/tibco/tibrv to reflect your TIBCO Rendezvous installation directory. Edit the line directory. usr/tibco/java to reflect your Java installation 2. Create a link as follows: ln -s /etc/init.36 | Chapter 4 Installing on UNIX HP-UX Instructions This section describes how to start TIBCO Hawk components automatically at system boot on an HP operating system.

to reflect your TIBCO Rendezvous installation directory. Create a link as follows: ln -s /sbin/init. Edit the line: HAWK_ROOT=/usr/tibco/hawk to reflect your TIBCO Hawk installation directory.d/hawk2 3.d/S98hawk TIBCO Hawk Installation and Configuration . Edit the line: RV_ROOT=/usr/tibco/tibrv to reflect your TIBCO Rendezvous installation directory. Copy the hawk2 file as follows: cp $HAWK_ROOT/samples/etc/hawk2 /etc/init. Edit the line: HAWK_ROOT=/usr/tibco/hawk to reflect your TIBCO Hawk installation directory. Open the file $HAWK_ROOT/samples/etc/hawk2 in an editor and make the following changes. 1.d/Sxxhawk where xx is an integer. Copy the hawk2 file as follows: cp $HAWK_ROOT/samples/etc/hawk2 /sbin/init.d/hawk2 /etc/rc2. usr/tibco/java to reflect your Java installation 2. Edit the line: RV_ROOT=/usr/rv. Edit the line JRE_ROOT= to reflect your Java installation directory. 1. Create a link as follows: ln -s /etc/init. Edit the line JRE_ROOT= directory. dependent upon your system startup parameters LINUX Instructions This section describes how to start TIBCO Hawk components automatically at system boot on a LINUX operating system. 2. Open the file $HAWK_ROOT/samples/etc/hawk2 in an editor and make the following changes.Starting TIBCO Hawk Components Automatically at System Boot 37 | TRU64 Instructions This section describes how to start TIBCO Hawk components automatically at system boot on a TRU64 operating system.d/hawk2 /sbin/rc2.d/hawk2 3.

38 | Chapter 4 Installing on UNIX TIBCO Hawk Installation and Configuration .

Topics • • • • Installation Prerequisites. page 40 Installing TIBCO Hawk on OS/400. page 43 TIBCO Hawk Installation and Configuration .| 39 Chapter 5 Installing on OS/400 This chapter explains how to install the TIBCO Hawk monitoring system on computers running the OS/400 operating system. page 41 Post-Installation Tasks. page 42 Starting TIBCO Hawk Components.

1_02. Supported Operating Systems TIBCO Hawk supports OS/400 version V5R1M0 or higher Software The following software is required as indicated.1. 1.tkt file for that machine. on the target machine.40 | Chapter 5 Installing on OS/400 Installation Prerequisites Read this section before you start installation. TIBCO Hawk Installation and Configuration . or 1. TIBCO Software TIBCO Rendezvous 6.3.1.3. In this case. JRE is not included with the TIBCO Hawk installation package.4. you will not need additional TIBCO Rendezvous licenses unless you will be running TIBCO Rendezvous Routing Daemon (RVRD) processes on a particular machine.3. you need a valid RVRD license in the tibrv.3. TIBCO Hawk does not support Java 1.9 or higher is required. 1. If you have already installed TIBCO Rendezvous software on a network-wide basis. JRE TIBCO Hawk requires Java Runtime Environment (JRE) version 1.1_03. with any available patches.1_01. with any available patches.

follow these steps: 1. Login as QSCECOFR. TIBCO Hawk Installation and Configuration . CRTLIB TIBHAWK CRTLIB <libname> 3. 6. Create SAVE files TIBHAWKSF and TIBHAWKSFL within the library <libname>. Unzip the distribution archive on a Microsoft Windows system. CRTDIR ('/usr/tibco/hawk') b. Use the command CRTSAVF to do this.Installing TIBCO Hawk on OS/400 41 | Installing TIBCO Hawk on OS/400 To install the software. Restore the file containing the java files and the IFS file structure RST DEV('/qsys. 4. a. Create a library TIBHAWK and another library in which you will store the installation SAVE files. 2. 5. Create a directory for TIBCO Hawk in /usr (if it doesn't exist already). After RSTOBJ is complete.file') OBJ(('/usr/tibco/hawk/*')) This command restores TIBCO Hawk components to the directory /usr/tibco/hawk in the Integrated File System. perform the following steps. Copy the TIBHAWKSF and TIBHAWKSFL files from the Microsoft Windows system to the SAVE files you created in step 2 on your OS/400 system. You can use FTP or other mechanisms to do so. Perform the installation using the command RSTOBJ as follows: RSTOBJ OBJ(*ALL) SAVLIB(TIBHAWK) DEV(*SAVF) SAVF(<libname>/TIBHAWKSF) Where <libname> is the library where you created the SAVE files in step 2. 7.lib/TIBHAWKSFL.lib/<libname>.

If you do not set this variable. choose from one of these options: — To run the components as jobs. you must turn on multi-threading.42 | Chapter 5 Installing on OS/400 Post-Installation Tasks After installing TIBCO Hawk on OS/400. To use TIBCO Hawk components. make sure that the ALWMLTTHD parameter is set to (*YES) TIBCO Hawk Installation and Configuration . it persists until you log out. 2. you can create a CL program that is run when a user logs in. 1. enable the job descriptions for multiple threads. that sets the environment variable QIBM_MULTI_THREADED. the user must perform the following post-installation tasks as noted. by setting INLPGM parameter in the user profile. For example: PGM /* start it */ ADDENVVAR ENVVAR(QIBM_MULTI_THREADED) VALUE(Y) ENDPGM If you do this manually when you log in. — To set the variable permanently. the TIBCO Hawk components will not run reliably. To turn on multi-threading. — To use qsh to run Hawk components you set the environment variable QIBM_MULTI_THREADED to Y before you start qsh. When submitting jobs using SBMJOB.

to change the code page to Cp500. This script is located in the $HAWK_ROOT/bin directory. the sample program will not start. • TIBCO Hawk Agent You can start TIBCO Hawk Agent in the following ways: — Start TIBCO Hawk Agent from the native system using the following command: call tibhawk/tibhawktmp — Execute the startagent script from qshell. You can override this default value by This default can be overrided by specifying the codepage in the Java property customMA. TIBCO Hawk Installation and Configuration . For example.Starting TIBCO Hawk Components 43 | Starting TIBCO Hawk Components • TIBCO Hawk Microagent To start the TIBCO Hawk Microagent (HMA) from the command prompt use the SBMJOB command.codepage. Without multi-thread support set in the job description. The default codepage use for reading output from the TIBCO Hawk methods Custom::ExecuteForString and Custom::ExecuteForNumber is Cp037. For example. to start the TIBCO Hawk Microagent submit the job as follows: SBMJOB CMD(CALL PGM(TIBHAWK/TIBHKHMA) PARM('-rvd_session' '7474' '' 'tcp:7474')) JOBQ(QUSRNOMAX) MSGQ(*USRPRF) ALWMLTTHD(*YES) If you are uncertain whether your job description has multi-threading enabled set ALWMLTHTHD to *YES.codepage="Cp500" before specifying the classpath in the startagent script. add the following line -DcustomMA.

44 | Chapter 5 Installing on OS/400 TIBCO Hawk Installation and Configuration .

and Event Service components. and create a TIBCO Rendezvous session. page 84 TIBCO Hawk Installation and Configuration . page 67 Creating a TIBCO Hawk Domain. page 83 Creating a TIBCO Rendezvous Session. On Microsoft Windows platforms. Using the Configuration Utility.cfg).cfg). page 52 TIBCO Hawk HMA Configuration File (hawkhma. Topics • • • • • • • Startup Scripts and Configuration Files.cfg). It also describes how to use the startup scripts. page 46 TIBCO Hawk Display Configuration File (hawkdisplay.cfg). Display.| 45 Chapter 6 Configuring TIBCO Hawk Software This chapter describes how to edit the configuration files for the TIBCO Hawk Display. This is described in Chapter 7. Agent. HMA and Event Service components on Microsoft Windows and UNIX platforms. you can alternatively use a GUI interface to configure TIBCO Hawk General. Agent. page 64 TIBCO Hawk Event Service Configuration File (hawkevent. create a TIBCO Hawk domain. page 48 TIBCO Hawk Agent Configuration File (hawkagent.

cfg This ensures that the scripts will work as shipped. For example. if the startagent script is run using arguments for a predefined file. followed by the filename of the absolute path to the .cfg hawkevent. modelling them on the default supplied.cfg hawkagent.cfg Described on Page 48 52 64 67 Startup scripts and configuration files are located in <TIBCO Hawk installation directory>/bin. the file has the following default value: -M LogService -log_dir . You can create and name your own configuration files.cfg file.46 | Chapter 6 Configuring TIBCO Hawk Software Startup Scripts and Configuration Files Please read this chapter and determine your system’s particular configuration and setup requirements before changing any values. If no command line options are specified. Special characters must be escaped with a backslash ( \ ). This chapter describes the command line options you can use in the configuration files. Replacing Relative Paths with Absolute Paths As shipped. A startup script and default configuration file are supplied for each component. Startup Scripts. The startup scripts take a single command line option of -file.cfg hawkhma. The configuration files and options are described in the next sections. the configuration files use relative paths./log TIBCO Hawk Installation and Configuration . where <TIBCO Hawk installation directory> is the starting point (also known as the reference directory). A set of startup scripts and configuration files is provided with the TIBCO Hawk software. the startup scripts use the supplied default values in the configuration files (as shipped) by default. On UNIX. hawkagent. the script does not recognize special characters such as quotation marks ( " ). and Configuration Files Component TIBCO Hawk Display TIBCO Hawk Agent TIBCO Hawk HMA TIBCO Hawk Event Service Startup Script startdisplay startagent starthma startevent Configuration File hawkdisplay. Table 11 TIBCO Hawk Components.

cfg file for your environment. After installation. as shown here: startagent -file . you must customize the configuration files to specify the absolute path to the . when executing the scripts to start either the agent. TIBCO Hawk Display or the HMA./hawkagent./log expands to <TIBCO Hawk installation directory>/log. . In other words.Startup Scripts and Configuration Files 47 | This instructs the system to create the log directory under <TIBCO Hawk installation directory>.cfg TIBCO Hawk Installation and Configuration .

page 83. The default is to monitor an entire network as one group.cfg Functions and Options Function TIBCO Hawk Domain TIBCO Rendezvous (RVD) Session Character Encoding Logging Information Options -hawk_domain <TIBCO Hawk domain name> -rvd_session <service> <network> <daemon> -character_encoding <character encoding string> -logdir <directory for display logs> size of single display log> -logmaxsize <maximum -logmaxnum <maximum number of display logs> -log_format <Hawk or ActiveEnterprise format> <directory for display files> implementing security> property file> Display File Security Policy Variables -display_file -security_policy <class -variables <External variables TIBCO Hawk Domain -hawk_domain <TIBCO Hawk domain name> Separate domains create independent TIBCO Hawk systems. Table 12 hawkdisplay. TIBCO Rendezvous (RVD) Session -rvd_session <service> <network> <daemon> TIBCO Hawk Installation and Configuration .cfg) The options in the hawkdisplay. To use the default. omit the -hawk_domain option.cfg configuration file are used to configure the following functions related to TIBCO Hawk Display. The functions and options are described in the next sections. Agents and the display must share the same Hawk Domain name in order to communicate.48 | Chapter 6 Configuring TIBCO Hawk Software TIBCO Hawk Display Configuration File (hawkdisplay. for more details. See Creating a TIBCO Hawk Domain.

To use the default TIBCO Hawk session parameters. for example: -rvd_session 7474 "" tcp:7474 See Creating a TIBCO Rendezvous Session. You can enter at minimum 5 and at maximum 999 as a value for -logmaxnum. If you use this option. omit the -rvd_session command-line options. The log thus retains the latest log information and discards the oldest. thus maintaining a total of five rollover files. it must connect to a TIBCO Rendezvous daemon by creating a session. By default. use the TIBCO Rendezvous daemon session default values. for example. and a new log file with the same name is started. When the number of log files exceeds the number set in the -logmaxsize option. log files roll over until there are five files (named file1. Character Encoding -character_encoding <character encoding string> Specifies the character encoding to be used for strings sent over all TIBCO Rendezvous transports. TIBCO Hawk Installation and Configuration . file2… file5). or use an empty string. all three parameters must be present and separated by white space.) to indicate a null value.cfg) 49 | Because the TIBCO Hawk software uses the functionality of the TIBCO Rendezvous system. page 84.TIBCO Hawk Display Configuration File (hawkdisplay. When one file has reached the size specified in the -logmaxsize option. 10M specifies ten megabytes. the unit of measure for -logmaxsize is kilobytes and the default size is 1024. you have configured a maximum of five log files. Note that the maximum log file size is 2097151 kilobytes. for more details. Logging Information -logdir <directory for display logs> size of single display log> -logmaxsize <maximum -logmaxnum <maximum number of display logs> <Hawk or ActiveEnterprise format> -log_format The TIBCO Hawk system creates rolling log files for display events (display. If TIBCO Rendezvous is only used on one network and no special TIBCO Rendezvous sessions are needed. use the suffix m or M. Use a semicolon (. log entries roll over to reuse the oldest log file. If. At this point. To specify a value in megabytes.log) in the directory named in the -log_dir option. it is closed and renamed. For example. the next rollover eliminates file5 and renames file4 to file5.

security. use: COM. Do not enter the file extension. on each machine where you want to use the policy. Either the existing Hawk format or the ActiveEnterprise format can be specified.TIBCO. For more information on creating a security policy class. • • If you are not using a security policy.hawk. Security Policy -security_policy <class implementing security> Because security needs vary greatly. you must write a Java class that implements a security policy specific to your needs. For more information on the Trusted and Certified security policies that come with TIBCO Hawk software. To use the default. specify the name of the security policy class. The variables file can pass data to define external variables to be used in either host or tool menu commands. see the TIBCO Hawk Programmer’s Guide. To use a specific security policy.hawk.TIBCO.trusted.security. the TIBCO Hawk system provides a mechanism by which you can develop your own security policy plug-in.hawk. omit this option. omit this option.TIBCO. complete the -security_policy option as follows.certified.class you would specify ASecurityPolicy. use: COM. Display File -display_file <display file path and name> Specify the location of a display file to be loaded automatically. TIBCO Hawk Installation and Configuration .security.TrustedWithDomain • To use the TIBCO Hawk Certified Security Policy. To use the TIBCO Hawk Trusted Security Policy.Certified Variables -variables <External variables property file> Use the Variables option to specify a variables file. Depending on your security needs.trusted. see Chapter 10 on page 131. To create a security policy. For example.50 | Chapter 6 Configuring TIBCO Hawk Software The -log_format option allow you to select the format of log file entries.Trusted • or COM. if your Java class file is named ASecurityPolicy.

TIBCO Hawk Display Configuration File (hawkdisplay. However. Variables and variable names cannot include spaces or any of the following characters: equals sign (=). period (. or forward slash(\). you would specify in the file: HAWK_ROOT=c:\\tibco\\hawk. HAWK_ROOT=c:/tibco/hawk will also work properly on the Windows platform.cfg) 51 | On UNIX systems. the following restrictions apply to external variables: • • • The variables file to support External variables in the agent must conform to the Java properties file format. the env command outputs environment values in the correct format. to use a variable for c:\tibco\hawk. Also. in Windows. For example.). due to the Java file path separator format. TIBCO Hawk Installation and Configuration . Any special characters must be escaped to be evaluated properly.

The agent command line options are organized in a modular fashion.52 | Chapter 6 Configuring TIBCO Hawk Software TIBCO Hawk Agent Configuration File (hawkagent.. such as -M Self. Within each modular section are command line options relating to the function of the module. The command line options within each module of the TIBCO Hawk agent configuration file are described in the next sections.cfg Modules and Options Options -cluster <cluster Module Name -M Self Page name> name> domain name> 54 -agent_name <agent -agent_domain <agent -hawk_domain <TIBCO Hawk domain name> -rvd_session <service> <network> <daemon> -character_encoding <character encoding string> -hma_plugin_dir <directory> -file <configuration file> -M RuleBaseEngine -rulebases <rulebase> <rulebase> -config_path <list . Table 13 hawkagent. Each section of the file begins with -M followed by the module name..cfg) The options in the hawkagent.cfg configuration file relate to agent functionality. 56 of directories to use as configuration sources> to autoload rulebases at startup> -auto_config_dir <directory -repository_path <list of repositories to use as configuration sources> -repository_cache_dir <repository cache -variables <property -M AMIService directory> file> -ami_rvd_session <service> <network> <daemon> -ami_rvds_session <service> <network> <daemon> 60 TIBCO Hawk Installation and Configuration .

cfg Modules and Options Options -log_dir <directory to Module Name (Cont’d) -M LogService Page store TIBCO Hawk logs> size of one TIBCO Hawk log> 61 -log_max_size <maximum -log_max_num <maximum -log_format -M TIBProtocolAdapter number of TIBCO Hawk logs> <Hawk or ActiveEnterprise format> interval in seconds> that implements security> name> -interval <heartbeat 62 -security_policy <class -M Repository -repository_name <repository 63 -repository_dir <repository directory> -M LogfileMicroAgent -scan_rate <rate in seconds> -block_size < size in kilobytes> -eval_rate <rate in seconds> 63 TIBCO Hawk Installation and Configuration .TIBCO Hawk Agent Configuration File (hawkagent.cfg) 53 | Table 13 hawkagent.

54

| Chapter 6
-M Self

Configuring TIBCO Hawk Software

This module of the agent configuration file deals with the following command line options which relate to the agent itself: Table 14 -M Self Options Option
-cluster <cluster

Description
name>

The name of the container in which this agent will appear in the display by default. The display will create the container if it does not already exist. Allows for grouping of multiple agents. The default name for the container is the IP subnet address. The cluster name must be enclosed within quotes, if the name contains spaces.

-agent_name <agent

name>

The agent name as it appears in the TIBCO Hawk Display. The default name for the TIBCO Hawk agent is the host name of the computer on which it is installed. Each agent being managed must have a unique combination of agent_name, agent_domain, and hawk_domain values. To use the host name as the agent name, omit this option. To use a different name, specify a name as desired.

-agent_domain <agent

domain

name>

Sets the agent domain name. The default value is "none". Each agent being managed must have a unique combination of agent_name, agent_domain, and hawk_domain values. An agent domain must be specified when two computers within the same TIBCO Hawk domain have the same name but reside in different network domains. For example, you might specify this option as: -agent_domain pa.tibco.com.

-hawk_domain <TIBCO

Hawk

domain name>

Sets the hawk domain name. The agents and the display must have the same hawk domain value in order to communicate. Each agent being managed must have a unique combination of agent_name, agent_domain, and hawk_domain values. Separate domains create independent TIBCO Hawk systems. Agents and the display must share the same Hawk Domain name in order to communicate. The default is to monitor an entire network as one group. To use the default, omit the -hawk_domain option. See Creating a TIBCO Hawk Domain, page 83, for more details.

TIBCO Hawk Installation and Configuration

TIBCO Hawk Agent Configuration File (hawkagent.cfg) 55

|

Table 14 -M Self Options (Cont’d) Option (Cont’d)
-rvd_session <service> <network> <daemon>

Description (Cont’d) Specifies the primary TIBCO Rendezvous transport used by the agent. Because the TIBCO Hawk software uses the functionality of the TIBCO Rendezvous system, it must connect to a TIBCO Rendezvous daemon by creating a session. If TIBCO Rendezvous is only used on one network and no special TIBCO Rendezvous sessions are needed, use the TIBCO Rendezvous daemon session default values. To use the default TIBCO Hawk session parameters, omit the -rvd_session command-line options. If you use this option, all three parameters must be present and separated by white space. Use an empty string to indicate a null value, for example:
-rvd _session 7474 "" tcp:7474

See Creating a TIBCO Rendezvous Session, page 84, for more details. -character_encoding <character encoding string> -hma_plugin_dir <directory> -file <configuration file> Specifies the character encoding to be used for strings sent over all TIBCO Rendezvous transports. Specifies the directory the TIBCO Hawk Agent should search when loading microagent plug-ins. Read more command line arguments from a config file. The contents of the file have the same syntax and semantics as command lines. Multiple lines are permitted. All characters from # to the end of a line are treated as a comment. This option is not allowed in a config file. You may supply no more than one -file parameter.

TIBCO Hawk Installation and Configuration

56

| Chapter 6

Configuring TIBCO Hawk Software

-M RuleBaseEngine
This module of the agent configuration file deals with the following command line options which relate to the rulebases used by this agent. If you are using the rulebase map, you usually do not need to list any rulebases in the -rulebases option. Using both a rulebase map and the -rulebases option increases the complexity of managing your monitoring configuration. The -rulebases option is provided to maintain backward compatibility with previous versions of TIBCO Hawk that do not contain the rulebase map feature. Three mutually-exclusive configuration modes are available for determining which configuration objects to use. Combining these options to implement each configuration mode is discussed in the following sections: • • • Automatic Configuration Mode on page 57 Manual Configuration Mode on page 58 Repository Configuration Mode on page 59

Table 15 -M RuleBaseEngine Options Option
-rulebases <rulebase> <rulebase>

Description Typically used only if rulebase map is not being used If manual or repository configuration mode is used, specify a list of rulebases to be loaded at startup. If -rulebases option is used, you must omit the -auto_config_dir option and use either manual configuration mode or repository configuration mode options. ...

-config_path <list of directories to use as configuration sources>

If manual configuration mode is used, specify the path to be searched for configuration objects. The delimiter for path entries is a colon (:). The default used if this option is omitted is the current working directory. If -config_path is used, omit the -auto_config_dir, -repository_path, and -repository_cache_dir options.

TIBCO Hawk Installation and Configuration

TIBCO Hawk Agent Configuration File (hawkagent.cfg) 57

|

Table 15 -M RuleBaseEngine Options (Cont’d) Option (Cont’d)
-auto_config_dir <directory to

Description (Cont’d) If this option is present, the agent will run in automatic configuration mode. Specify the directory from which rulebase and schedule configuration objects will be loaded at startup. The default directory, <TIBCO Hawk installation directory>/autoconfig, is used if a value is omitted. If you use automatic configuration, omit the following options:
-config_path, -repository_path, -repository_cache_dir, -rulebases

autoload rulebases

at startup>

-repository_path <list of

repositories to use as configuration sources>

If repository configuration mode is used, specify the path to be searched for repositories. The delimiter for path entries is a colon (:). The default used if this option is omitted is the current working directory. If -repository_path is used, omit the -auto_config_dir and -config_path options.

-repository_cache_dir <repository cache

directory>

If repository configuration mode is used, all configuration objects loaded from the repository may be cached in a local directory, specified in this option. This cache is used in the event of a repository failure, and also to minimize network traffic. If -repository_cache_dir is used, omit the -auto_config_dir and -config_path options.

-variables <property file>

Use this option to specify a variables file. The variables file can pass data to define external variables to be passed to rules for use in rulebase configurations.

Automatic Configuration Mode This section explains how you use the -M RuleBaseEngine options to implement an Automatic Configuration mode. This is one of three mutually-exclusive modes available for determining which configuration objects to use. The other two modes are Manual Configuration and Repository Information, both of which are types of manual configuration mode. To use Automatic configuration, specify the -auto_config_dir option. When Automatic Configuration mode is used, all load-by-reference rulebase loading mechanisms are disabled. Therefore, you will omit the following options:
-rulebases

TIBCO Hawk Installation and Configuration

However. Manual Configuration Mode This section explains how you use the -M RuleBaseEngine options to implement a Manual Configuration mode. To use manual configuration.58 | Chapter 6 Configuring TIBCO Hawk Software -config_path -repository_path -repository_cache_dir In addition. Use of the methods RuleBaseEngine:loadRuleBaseFromFile() and RuleBaseEngine:unloadRuleBase() do not affect the autoconfiguration directory. When a rulebase is removed from an agent via the Display. the RuleBaseInclude feature. the microagent method RuleBaseEngine:loadRuleBaseFromFile() is allowed. or by using SendTo from the Display. and the RuleBaseEngine:loadRuleBase() microagent method are not used. However. if no RuleBase Map is supplied by the repository. When a rulebase is sent to an agent via SendTo or Apply Changes from the Display. Use of -rulebases is optional. rulebase maps. the agent will load the Schedule configuration file and all rulebase configuration files from the automatic configuration directory at startup. the rulebase is stored in the autoconfiguration directory. The only other mechanism by which an agent can load a rulebase after this point is through invocation of RuleBaseEngine:loadRuleBaseFromFile() using fully qualified filenames. Manual Configuration and Repository Information are both types of manual configuration mode. the use of -rulebases is recommended. specify a configuration path and a list of rulebases. the rulebase is also removed from the autoconfiguration directory. When Manual Configuration mode is used. The other two modes are Automatic Configuration and Repository Information. This is one of three mutually exclusive modes available for determining which configuration objects to use. See the TIBCO Hawk Administrator’s Guide and the TIBCO Hawk Methods Reference for more on these features and microagent methods. omit the following options: -auto_config_dir -repository_path -repository_cache_dir TIBCO Hawk Installation and Configuration . With automatic configuration. using the -rulebases and -config_path options.

Instead of a configuration path. However. omit the following options: -config_path -auto_config_dir Repository mode is also a type of manual configuration mode and operates in a similar way to Manual Configuration mode. Repositories are kept on the network and can be accessed by multiple agents. and rulebases in any contained RuleBaseIncludes. Note that any rulebases loaded by the agent are not written to a local cache. The agent communicates with a list of repositories in this path to obtain all configuration objects (rulebases. using the -rulebases option. those listed in the Rulebases dialog. After evaluating the rulebase map. The other two modes are Automatic Configuration and Manual Configuration. specify a repository path and a repository cache directory. if no RuleBase Map is supplied by the repository. the agent has a list of rulebase names. Note that the loaded startup rulebases may have RuleBaseInclude lists that will trigger further searches of the manual configuration path for additional rulebases. using the -repository_path and -repository_cache_dir options. Manual Configuration and Repository Information are both types of manual configuration mode. Also at startup. TIBCO Hawk Installation and Configuration . and a list of rulebases. To use repository configuration. schedules. the use of -rulebases is recommended. Repository Configuration Mode This section explains how you use the -M RuleBaseEngine options to implement a Repository Configuration mode.cfg) 59 | When manual configuration is selected. and rulebase maps). When Repository Configuration mode is used. you specify a repository path.TIBCO Hawk Agent Configuration File (hawkagent. This is one of three mutually-exclusive modes available for determining which configuration objects to use. See the TIBCO Hawk Administrator’s Guide for an explanation of repositories. Note that manual configuration mode is also known as Configuration Path mode. The only rulebases an agent may load at startup are those specified by the rulebase map. the agent searches the Manual Configuration Path for the Schedule file and the rulebase map file at startup. the agent searches the path for any rulebases specified in the Rulebases dialog and loads them. See the TIBCO Hawk Administrator’s Guide for more on these features. It searches for these using the Manual Configuration Path. Use of -rulebases is optional. There is no notion of an autoconfiguration directory.

-M AMIService This module of the agent configuration file deals with the following command line options which relate to monitoring an AMI-instrumented application. for example: -ami_rvd _session 7474 "" tcp:7474 You can specify any number of additional TIBCO Rendezvous sessions for a TIBCO Hawk agent to monitor. To monitor AMI-instrumented applications that use different session parameters than those used in the TIBCO Hawk configuration. Agents can determine if a configuration object in their cache is identical to the one in the repository and will load it directly from the cache or update it from the Repository as appropriate. To monitor an AMI-instrumented application that uses the same session parameters as those used in the Self section of the agent configuration file (the primary session). This cache is used in the event of a repository failure. TIBCO Hawk agents can use rulebases that refer to the applications. -ami_rvd_session <service> <network> <daemon> -ami_rvds_session <service> <network> <daemon> Applications instrumented with AMI must create and use a TIBCO Rendezvous session to connect with a TIBCO Rendezvous daemon (rvd). If you use these options.60 | Chapter 6 Configuring TIBCO Hawk Software Unlike Manual Configuration Mode. You can specify a secure Rendezvous session that uses Rendezvous DataSecurity along with digital certificates to guarantee the integrity and authenticity of the messages sent to applications instrumented with AMI. Applications using these sessions appear as primary sessions in the TIBCO Hawk Display in the same list as managed applications (and microagents). page 84. with Repository mode all configuration objects loaded from the Repository may be cached in a local directory. and also to minimize network traffic. Use an empty string to indicate a null value. See Creating a TIBCO Rendezvous Session. use the -ami_rvds_session option. all three parameters must be present and separated by white space. for more on defining sessions. omit the AMIService options. TIBCO Hawk Installation and Configuration . you must create additional AMI sessions. as long as those applications are running. To do this. specified in the -repository_cache_dir option.

the next rollover eliminates file5 and renames file4 to file5. for example. log files roll over until there are five files (named file1.TIBCO Hawk Agent Configuration File (hawkagent. The -log_format option allows you to select the format of log file entries. you have configured a maximum of five log files. TIBCO Hawk Installation and Configuration . file2… file5). Either the existing Hawk format or the Active Enterprise format can be specified. use the suffix m or M. log entries roll over to reuse the oldest log file. 10M specifies ten megabytes. it is closed and renamed. For example. the unit of measure for -logmaxsize is kilobytes and the default size is 1024.cfg) 61 | -M LogService This module of the agent configuration file deals with the following command line options which relate to log files used by this agent. When the number of log files exceeds the number set in the -log_max_size option. -log_dir <directory to store TIBCO Hawk logs> size of one TIBCO Hawk log> -log_max_size <maximum -log_max_num <maximum -log_format number of TIBCO Hawk logs> <Hawk or ActiveEnterprise format> The TIBCO Hawk system creates rolling log files for agent events (Hawk. To specify a value in megabytes. and a new log file with the same name is started. If.log) in the directory named in the -log_dir option. thus maintaining a total of five rollover files. At this point. When one file has reached the size specified in the -log_max_size option. By default. The log thus retains the latest log information and discards the oldest.

if you used the Java "package" directive in your code).) Depending on your security needs. For example.TIBCO.trusted.hawk.Certified To use a specific security policy. complete this option as follows: • • If you are not using a security policy.security. see the TIBCO Hawk Programmer’s Guide. if your fully qualified class name is com.trusted. To use the TIBCO Hawk Trusted Security Policy.mycorp.hawk. To create a security policy.security. For more information on the Trusted and Certified security policies. enter a number of seconds.class you would specify ASecurityPolicy. see Chapter 10 on page 131.hawk.certified. you will need to create the appropriate directory structure beneath <TIBCO Hawk installation directory>/Java that corresponds to your package name and place your class file in the appropriate location. Table 16 -M TIBProtocolAdapter Options Option -interval <heartbeat Description interval in seconds> The TIBCO Hawk agent heartbeat interval can be set on each computer where an agent is installed.62 | Chapter 6 Configuring TIBCO Hawk Software -M TIBProtocolAdapter This module of the agent configuration file deals with the following command line options which relate to agent heartbeat and security used by this agent. if your Java class file is named ASecurityPolicy.TrustedWithDomain • To use the TIBCO Hawk Certified Security Policy. specify the name of the security policy class on each machine where you want to use the policy.TIBCO. (For more information on creating a security policy class. as desired. omit this option. The TIBCO Hawk Display uses this value to determine when to mark an agent dead. For example.security.MySecurity. Note: If your security policy class is not part of the default package (for example. To use a different value.TIBCO. Ensure that this class file is placed in <TIBCO Hawk installation directory>/Java. you must write a Java class that implements a security policy specific to your needs.Trusted or COM. TIBCO Hawk Installation and Configuration . specify: COM. To use the default value of 30 seconds. specify: COM. -security_policy <class that implements security> TIBCO Hawk provides a mechanism by which you can develop your own security policy plug-in. omit this option.class in <TIBCO Hawk installation directory>/Java/com/mycorp. you will place MySecurity. Do not enter the file extension.

To use a different value. The TIBCO Hawk agent eval rate is the rate at which all the logfiles being monitored are re-evaluated. omit these options. To use the default value of 300 seconds.cfg) 63 | -M Repository This module of the agent configuration file deals with the following command line options which relate only to agents used as repositories for the TIBCO Hawk system. To use the default value of 16 kilobytes. -M LogfileMicroAgent This module of the agent configuration file deals with the following command line options which relate to agent heartbeat and security used by this agent. enter a number of seconds. The default scan rate is 10 seconds. Table 17 -M LogfileMicroAgent Options Option -scan_rate <rate in seconds> Description The TIBCO Hawk agent scan rate is the rate at which logfiles are scanned. omit this option. The default value is 16 kilobytes. -repository_name <repository name> -repository_dir <repository directory> If a TIBCO Hawk agent is to act as a repository for the TIBCO Hawk system. If this is not the case. To use a different value. as desired. The default eval rate is 300 seconds. enter a number of seconds. enter a number of seconds. omit this option. omit this option. To use a different value. To use the default value of 10 seconds.TIBCO Hawk Agent Configuration File (hawkagent. The default is <TIBCO Hawk installation directory>/repository. enter a name (with no spaces or periods) for the repository and a path for storage of the configuration object files. as desired. The TIBCO Hawk agent block size is the maximum number of kilobytes to read on each scan. as desired. -block_size < size in kilobytes> -eval_rate <rate in seconds> TIBCO Hawk Installation and Configuration .

cfg Functions and Options Function TIBCO Rendezvous (RVD) Session Logging Information Options -rvd_session <service> <network> <daemon> -logdir <directory to store HMA logs> size of one HMA log> logs> -logmaxsize <maximum -logmaxnum <maximum number of HMA -log_format <Hawk or ActiveEnterprise format> Timeout Trace Level UNIX Signal Handling -timeout <milliseconds> <desired trace level> -tracelevel -ignore_sigint -ignore_sigterm -ignore_sigabrt TIBCO Rendezvous (RVD) Session -rvd_session <service> <network> <daemon> Because the TIBCO Hawk software uses the functionality of the TIBCO Rendezvous system. If you use this option. it must connect to a TIBCO Rendezvous daemon by creating a session. Use an empty string to indicate a null value. use the TIBCO Rendezvous daemon session default values. To use the default session parameters (specified in the Self module of the agent configuration file).cfg) The options in the hawkhma. TIBCO Hawk Installation and Configuration . for more details. omit the -rvd_session command-line options.cfg configuration file are used to configure microagent-related functions: Table 18 hawkhma. all three parameters must be present and separated by white space. If TIBCO Rendezvous is only used on one network and no special TIBCO Rendezvous sessions are needed.64 | Chapter 6 Configuring TIBCO Hawk Software TIBCO Hawk HMA Configuration File (hawkhma. for example: -rvd _session 7474 "" tcp:7474 See Creating a TIBCO Rendezvous Session. page 84.

use the suffix m or M. Either the existing Hawk format or the Active Enterprise format can be specified. 10M specifies ten megabytes. At this point. file2… file5). the next rollover eliminates file5 and renames file4 to file5. for example. If.cfg) 65 | Logging Information -logdir <directory to store HMA logs> size of one HMA log> -logmaxsize <maximum -logmaxnum <maximum -log_format number of HMA logs> <Hawk or ActiveEnterprise format> The TIBCO Hawk system creates rolling log files for microagent events in the directory named in the -logdir option. When one file has reached the size specified in the -logmaxsize option. Normally there is no need to change this value. it is closed and renamed. For example. and a new log file with the same name is started. hawk_performance. however.log. log entries roll over to reuse the oldest log file.TIBCO Hawk HMA Configuration File (hawkhma. By default. for example. The -log_format option allow you to select the format of log file entries. log files roll over until there are five files (named file1. The default is 10000 milliseconds. the unit of measure for -logmaxsize is kilobytes and the default size is 1024. When the number of log files exceeds the number set in the -logmaxsize option. this new option allows the timeout value to be increased Trace Level -tracelevel <desired trace level> TIBCO Hawk Installation and Configuration . on machines under extreme stress where method invocations are timing out. The log thus retains the latest log information and discards the oldest. To specify a value in megabytes. The HMA produces a log file for each of its microagents and names them using the format hawk_<microagentname>.log. Timeout -timeout <milliseconds> Specifies the amount of time the Hawk Agent should wait for HMA method invocations to complete before timing them out. thus maintaining a total of five rollover files. you have configured a maximum of five log files.

the HMA installs a signal handler for these signals that performs a graceful shutdown of the HMA in response to one of these signals. and SIGABRT signals. By default. These options will cause the HMA to set the disposition of the corresponding signal to SIG_IGN. SIGTERM. warning and error).66 | Chapter 6 Configuring TIBCO Hawk Software Specifies the level of diagnostic trace output. For example. the HMA can be started as a background process from a UNIX console with -ignore_sigint so that the HMA will not be shutdown if Ctrl-C is entered from the console. UNIX Signal Handling -ignore_sigint -ignore_sigterm -ignore_sigabrt These options specify that the TIBCO Hawk HMA should ignore the SIGINT. 0 to enable no tracing. or 1+2+4 (information. or calculate a desired trace level by adding together values from the following table: Value 1 2 4 8 16 32 Purpose enables information level trace messages enables warning level trace messages enables error level trace messages enables debug level trace messages enables AMI level trace messages adds source filename and line numbers to all trace messages The default value for tracing is 7. TIBCO Hawk Installation and Configuration . respectively. For most circumstances. These options can be used to configure the HMA not to shutdown or terminate in response to any of these signals. You can choose -1 to enable all tracing. this is the desired behavior and these options would not be specified.

Multiple instances can be run on separate systems for fault tolerance. The Event.cfg) 67 | TIBCO Hawk Event Service Configuration File (hawkevent.log file is discussed in the TIBCO Hawk Administrator’s Guide. and to detect and respond to agent termination.log data files contain the data produced by the Event Service. Configuring the Event Service The Event Service is configured through a command-line interface. or to take some other automated action. This facility could be used to send an e-mail or page. Be careful not to confuse TIBCO Hawk Event Service data files (Event.dat) with Event Service log files (Event. as well as changes in an agent’s alert level (as would be shown by a color in the TIBCO Hawk Display) all instances of agent activation and expiration • The event service also can call a script (using the -script option in the Event Service configuration file) when the heartbeat of a TIBCO Hawk agent is lost (not received for a specified length of time). You will normally run the TIBCO Hawk Event Service on a single system in a TIBCO Hawk managed network.log). TIBCO Hawk Installation and Configuration .TIBCO Hawk Event Service Configuration File (hawkevent.cfg) The TIBCO Hawk Event Service has two main purposes: to record the activity of TIBCO Hawk agents. This usually means that the agent process has terminated or that network communication has been interrupted.cfg Options Option -hawk_root Description The TIBCO Hawk root installation directory. The event service records: • all alerts raised and cleared by TIBCO Hawk agents across the network.dat Event. The options are described below. • • Event. log files record the state of the Event Service itself. Table 19 hawkevent.

-character_encoding Specifies the character encoding to be used for strings sent over all TIBCO Rendezvous transports. For example: -rvd _session 7474 "" tcp:7474 The default session uses null values. -rvd_session Specifies the TIBCO Rendezvous session used by TIBCO Hawk Event Service.dat) for the event service. all three parameters must be present and separated by whitespace but any of them may be an empty string to indicate a null value. To use the default. The default is 5. If you use this option. Default is <install-path>/data. omit this option. If TIBCO Rendezvous is only used on one network and no special TIBCO Rendezvous sessions are needed. -datadir -datamaxnum TIBCO Hawk Installation and Configuration . The directory in which TIBCO Hawk will create rolling data files (event. and the default is used instead. The maximum number of rolling data files to keep. The default is to monitor an entire network as one group. Those values are specified in the Self module of the agent configuration file. Separate domains create independent TIBCO Hawk systems. -ami_rvd_session Specifies the TIBCO Rendezvous rvd session used by the TIBCO Hawk Event Service for AMI communications.cfg Options (Cont’d) Option (Cont’d) -hawk_domain Description (Cont’d) Sets the hawk domain name. The default ami_rvd_session uses rvd_session values. See the TIBCO Hawk Installation and Configuration Guide for more details. The agents and the event service must have the same hawk domain value in order to communicate.68 | Chapter 6 Configuring TIBCO Hawk Software Table 19 hawkevent. the following three parameters must be present and separated by white space: -rvd_session <service> <network> <daemon> Use an empty string to indicate a null value. Values lower than the default number are ignored. If this options is used. See the TIBCO Hawk Installation and Configuration Guide for more details. you can omit this parameter to use the default TIBCO Rendezvous daemon session values.

By default. User-defined. -JDBCdriverClassName -JDBCpassword -JDBCurl -JDBCuserName -log_format -logdir TIBCO Hawk Installation and Configuration . comma-separated alert action property fields of type VARCHAR(256) to be created as additional columns in the HawkAlertClearInfo table.microsoft. and a new data file with the original name is started.SQLServerDriver. use the suffix m or M. z creates three additional columns (x. DB2.log files generated by TIBCO Hawk Event Service. -ft -JDBCalertTableFields Fault Tolerant weight for TibrvFtMember. For example. Class name for the vendor's JDBC driver. the unit of measure for -datamaxsize is kilobytes and the default size is 1024. the command -JDBCalertTableFields x.TIBCO Hawk Event Service Configuration File (hawkevent. Default is no fault tolerance. To specify a value in megabytes. When the event service receives an "onAlert" event that contains the specified properties. and the default is used instead.cfg Options (Cont’d) Option (Cont’d) -datamaxsize Description (Cont’d) When one rolling data file has reached this size. it is closed and renamed. Valid values are default (Hawk format) or ae4 (Active Enterprise format).cfg) 69 | Table 19 hawkevent. The format of log file entries. The directory in which to store Event. -JDBCdbType Database vendor name. To print all log messages to the screen. INFORMIX and SYBASE. y and z) of type VARCHAR(256) in the HawkAlertClearInfo table. For example. com. User password to connect to the database. ORACLE. For example. Supported values are SQLSERVER. the corresponding values are inserted into the database.jdbc. You can. User name to connect to the database. 10M specifies ten megabytes. however. Values lower than the default size are ignored. y. omit this option. URL that identifies the database connection.sqlserver. enter a value greater than the default.

The default ami_rvd_session uses rvd_session values. If you use this option. For example: -rvd _session 7474 "" tcp:7474 The default session uses null values. the following three parameters must be present and separated by white space: -rvd_session <service> <network> <daemon> Use an empty string to indicate a null value. The agents and the event service must have the same hawk domain value in order to communicate. all three parameters must be present and separated by whitespace but any of them may be an empty string to indicate a null value.dat) for the event service. The maximum number of rolling data files to keep. -character_encoding Specifies the character encoding to be used for strings sent over all TIBCO Rendezvous transports. The default is to monitor an entire network as one group. If this options is used. The default is 5. omit this option. -rvd_session Specifies the TIBCO Rendezvous session used by TIBCO Hawk Event Service.70 | Chapter 6 Configuring TIBCO Hawk Software Table 19 hawkevent. To use the default. you can omit this parameter to use the default TIBCO Rendezvous daemon session values. -ami_rvd_session Specifies the TIBCO Rendezvous rvd session used by the TIBCO Hawk Event Service for AMI communications. See the TIBCO Hawk Installation and Configuration Guide for more details. Values lower than the default number are ignored. Separate domains create independent TIBCO Hawk systems. Those values are specified in the Self module of the agent configuration file. -datadir -datamaxnum TIBCO Hawk Installation and Configuration . Default is <install-path>/data. If TIBCO Rendezvous is only used on one network and no special TIBCO Rendezvous sessions are needed. The directory in which TIBCO Hawk will create rolling data files (event. See the TIBCO Hawk Installation and Configuration Guide for more details. and the default is used instead.cfg Options (Cont’d) Option (Cont’d) -hawk_domain Description (Cont’d) Sets the hawk domain name.

and a new data file with the original name is started. To print all log messages to the screen. You can.cfg) 71 | Table 19 hawkevent. Valid values are default (Hawk format) or ae4 (Active Enterprise format). For example. y and z) of type VARCHAR(256) in the HawkAlertClearInfo table. ORACLE. 10M specifies ten megabytes. For example.sqlserver. To specify a value in megabytes. enter a value greater than the default. y. it is closed and renamed. Values lower than the default size are ignored. User password to connect to the database. com. -JDBCdbType Database vendor name. The directory in which to store Event.SQLServerDriver. URL that identifies the database connection.microsoft. The format of log file entries. -JDBCdriverClassName -JDBCpassword -JDBCurl -JDBCuserName -log_format -logdir TIBCO Hawk Installation and Configuration . User name to connect to the database. omit this option. the unit of measure for -datamaxsize is kilobytes and the default size is 1024. By default. Supported values are SQLSERVER. Default is no fault tolerance. INFORMIX and SYBASE.cfg Options (Cont’d) Option (Cont’d) -datamaxsize Description (Cont’d) When one rolling data file has reached this size. comma-separated alert action property fields of type VARCHAR(256) to be created as additional columns in the HawkAlertClearInfo table.log files generated by TIBCO Hawk Event Service.TIBCO Hawk Event Service Configuration File (hawkevent. Class name for the vendor's JDBC driver. When the event service receives an "onAlert" event that contains the specified properties. use the suffix m or M. however. -ft -JDBCalertTableFields Fault Tolerant weight for TibrvFtMember. DB2. User-defined. and the default is used instead. For example.jdbc. z creates three additional columns (x. the corresponding values are inserted into the database. the command -JDBCalertTableFields x.

and the default is used instead. If TIBCO Rendezvous is only used on one network and no special TIBCO Rendezvous sessions are needed.cfg Options (Cont’d) Option (Cont’d) -hawk_domain Description (Cont’d) Sets the hawk domain name. omit this option. you can omit this parameter to use the default TIBCO Rendezvous daemon session values. -datadir -datamaxnum TIBCO Hawk Installation and Configuration . To use the default. See the TIBCO Hawk Installation and Configuration Guide for more details. The directory in which TIBCO Hawk will create rolling data files (event. all three parameters must be present and separated by whitespace but any of them may be an empty string to indicate a null value. -character_encoding Specifies the character encoding to be used for strings sent over all TIBCO Rendezvous transports. Those values are specified in the Self module of the agent configuration file. -ami_rvd_session Specifies the TIBCO Rendezvous rvd session used by the TIBCO Hawk Event Service for AMI communications. If this options is used. the following three parameters must be present and separated by white space: -rvd_session <service> <network> <daemon> Use an empty string to indicate a null value. The agents and the event service must have the same hawk domain value in order to communicate. Default is <install-path>/data. For example: -rvd _session 7474 "" tcp:7474 The default session uses null values.dat) for the event service. -rvd_session Specifies the TIBCO Rendezvous session used by TIBCO Hawk Event Service. If you use this option. Values lower than the default number are ignored. The maximum number of rolling data files to keep. Separate domains create independent TIBCO Hawk systems. The default is 5. The default is to monitor an entire network as one group. The default ami_rvd_session uses rvd_session values. See the TIBCO Hawk Installation and Configuration Guide for more details.72 | Chapter 6 Configuring TIBCO Hawk Software Table 19 hawkevent.

Default is no fault tolerance.TIBCO Hawk Event Service Configuration File (hawkevent. omit this option. -JDBCdriverClassName -JDBCpassword -JDBCurl -JDBCuserName -log_format -logdir TIBCO Hawk Installation and Configuration . To print all log messages to the screen. Values lower than the default size are ignored. INFORMIX and SYBASE. comma-separated alert action property fields of type VARCHAR(256) to be created as additional columns in the HawkAlertClearInfo table. DB2. The directory in which to store Event. 10M specifies ten megabytes.log files generated by TIBCO Hawk Event Service. URL that identifies the database connection. enter a value greater than the default. You can. When the event service receives an "onAlert" event that contains the specified properties. User name to connect to the database. To specify a value in megabytes. however. Valid values are default (Hawk format) or ae4 (Active Enterprise format).cfg) 73 | Table 19 hawkevent. For example. -JDBCdbType Database vendor name. By default. com. Supported values are SQLSERVER. the command -JDBCalertTableFields x. y. the unit of measure for -datamaxsize is kilobytes and the default size is 1024. use the suffix m or M. it is closed and renamed. ORACLE. and the default is used instead.jdbc. The format of log file entries. the corresponding values are inserted into the database. For example. For example.sqlserver.microsoft. -ft -JDBCalertTableFields Fault Tolerant weight for TibrvFtMember. y and z) of type VARCHAR(256) in the HawkAlertClearInfo table. and a new data file with the original name is started.cfg Options (Cont’d) Option (Cont’d) -datamaxsize Description (Cont’d) When one rolling data file has reached this size.SQLServerDriver. z creates three additional columns (x. User-defined. User password to connect to the database. Class name for the vendor's JDBC driver.

The directory in which TIBCO Hawk will create rolling data files (event. Default is <install-path>/data. If you use this option. To use the default. If this options is used. The default is 5. -ami_rvd_session Specifies the TIBCO Rendezvous rvd session used by the TIBCO Hawk Event Service for AMI communications. Separate domains create independent TIBCO Hawk systems. Values lower than the default number are ignored. -character_encoding Specifies the character encoding to be used for strings sent over all TIBCO Rendezvous transports. See the TIBCO Hawk Installation and Configuration Guide for more details. If TIBCO Rendezvous is only used on one network and no special TIBCO Rendezvous sessions are needed. The default ami_rvd_session uses rvd_session values. all three parameters must be present and separated by whitespace but any of them may be an empty string to indicate a null value. Those values are specified in the Self module of the agent configuration file.dat) for the event service. the following three parameters must be present and separated by white space: -rvd_session <service> <network> <daemon> Use an empty string to indicate a null value. you can omit this parameter to use the default TIBCO Rendezvous daemon session values. and the default is used instead. The agents and the event service must have the same hawk domain value in order to communicate. See the TIBCO Hawk Installation and Configuration Guide for more details.74 | Chapter 6 Configuring TIBCO Hawk Software Table 19 hawkevent. For example: -rvd _session 7474 "" tcp:7474 The default session uses null values. The maximum number of rolling data files to keep. omit this option. -datadir -datamaxnum TIBCO Hawk Installation and Configuration . The default is to monitor an entire network as one group.cfg Options (Cont’d) Option (Cont’d) -hawk_domain Description (Cont’d) Sets the hawk domain name. -rvd_session Specifies the TIBCO Rendezvous session used by TIBCO Hawk Event Service.

z creates three additional columns (x. the corresponding values are inserted into the database.microsoft. URL that identifies the database connection. You can. For example. User password to connect to the database. -ft -JDBCalertTableFields Fault Tolerant weight for TibrvFtMember. y and z) of type VARCHAR(256) in the HawkAlertClearInfo table. it is closed and renamed. To print all log messages to the screen.jdbc. the unit of measure for -datamaxsize is kilobytes and the default size is 1024.SQLServerDriver. -JDBCdbType Database vendor name. com. y. Values lower than the default size are ignored. User name to connect to the database.cfg Options (Cont’d) Option (Cont’d) -datamaxsize Description (Cont’d) When one rolling data file has reached this size. User-defined. For example.TIBCO Hawk Event Service Configuration File (hawkevent. comma-separated alert action property fields of type VARCHAR(256) to be created as additional columns in the HawkAlertClearInfo table. Class name for the vendor's JDBC driver. Default is no fault tolerance. enter a value greater than the default. By default. INFORMIX and SYBASE. however. To specify a value in megabytes.log files generated by TIBCO Hawk Event Service. use the suffix m or M. Valid values are default (Hawk format) or ae4 (Active Enterprise format). -JDBCdriverClassName -JDBCpassword -JDBCurl -JDBCuserName -log_format -logdir TIBCO Hawk Installation and Configuration . ORACLE.cfg) 75 | Table 19 hawkevent.sqlserver. the command -JDBCalertTableFields x. 10M specifies ten megabytes. The format of log file entries. omit this option. and a new data file with the original name is started. When the event service receives an "onAlert" event that contains the specified properties. For example. DB2. and the default is used instead. The directory in which to store Event. Supported values are SQLSERVER.

Separate domains create independent TIBCO Hawk systems. -rvd_session Specifies the TIBCO Rendezvous session used by TIBCO Hawk Event Service. Those values are specified in the Self module of the agent configuration file. The agents and the event service must have the same hawk domain value in order to communicate. The default is to monitor an entire network as one group. See the TIBCO Hawk Installation and Configuration Guide for more details. The default ami_rvd_session uses rvd_session values.dat) for the event service. and the default is used instead. If you use this option. -ami_rvd_session Specifies the TIBCO Rendezvous rvd session used by the TIBCO Hawk Event Service for AMI communications. The maximum number of rolling data files to keep. you can omit this parameter to use the default TIBCO Rendezvous daemon session values. The directory in which TIBCO Hawk will create rolling data files (event. To use the default. If this options is used. omit this option.76 | Chapter 6 Configuring TIBCO Hawk Software Table 19 hawkevent. all three parameters must be present and separated by whitespace but any of them may be an empty string to indicate a null value.cfg Options (Cont’d) Option (Cont’d) -hawk_domain Description (Cont’d) Sets the hawk domain name. See the TIBCO Hawk Installation and Configuration Guide for more details. If TIBCO Rendezvous is only used on one network and no special TIBCO Rendezvous sessions are needed. Default is <install-path>/data. -datadir -datamaxnum TIBCO Hawk Installation and Configuration . the following three parameters must be present and separated by white space: -rvd_session <service> <network> <daemon> Use an empty string to indicate a null value. For example: -rvd _session 7474 "" tcp:7474 The default session uses null values. -character_encoding Specifies the character encoding to be used for strings sent over all TIBCO Rendezvous transports. Values lower than the default number are ignored. The default is 5.

omit this option. and the default is used instead. For example. To print all log messages to the screen.log files generated by TIBCO Hawk Event Service. The directory in which to store Event.sqlserver. z creates three additional columns (x. Supported values are SQLSERVER. DB2.microsoft. the corresponding values are inserted into the database. For example. To specify a value in megabytes. User password to connect to the database. Values lower than the default size are ignored. User-defined. -ft -JDBCalertTableFields Fault Tolerant weight for TibrvFtMember. -JDBCdriverClassName -JDBCpassword -JDBCurl -JDBCuserName -log_format -logdir TIBCO Hawk Installation and Configuration . the command -JDBCalertTableFields x. For example.cfg Options (Cont’d) Option (Cont’d) -datamaxsize Description (Cont’d) When one rolling data file has reached this size. ORACLE. 10M specifies ten megabytes. enter a value greater than the default. however. You can. and a new data file with the original name is started. The format of log file entries. y and z) of type VARCHAR(256) in the HawkAlertClearInfo table. com. -JDBCdbType Database vendor name. Class name for the vendor's JDBC driver. When the event service receives an "onAlert" event that contains the specified properties. User name to connect to the database. Default is no fault tolerance. URL that identifies the database connection. it is closed and renamed. y. By default. Valid values are default (Hawk format) or ae4 (Active Enterprise format). INFORMIX and SYBASE.TIBCO Hawk Event Service Configuration File (hawkevent. the unit of measure for -datamaxsize is kilobytes and the default size is 1024.cfg) 77 | Table 19 hawkevent.jdbc. comma-separated alert action property fields of type VARCHAR(256) to be created as additional columns in the HawkAlertClearInfo table. use the suffix m or M.SQLServerDriver.

For example: -rvd _session 7474 "" tcp:7474 The default session uses null values. -rvd_session Specifies the TIBCO Rendezvous session used by TIBCO Hawk Event Service. Those values are specified in the Self module of the agent configuration file. the following three parameters must be present and separated by white space: -rvd_session <service> <network> <daemon> Use an empty string to indicate a null value. If you use this option. The agents and the event service must have the same hawk domain value in order to communicate. If this options is used. Values lower than the default number are ignored. omit this option. Separate domains create independent TIBCO Hawk systems.78 | Chapter 6 Configuring TIBCO Hawk Software Table 19 hawkevent. The default is 5. The directory in which TIBCO Hawk will create rolling data files (event. all three parameters must be present and separated by whitespace but any of them may be an empty string to indicate a null value.dat) for the event service. To use the default. -ami_rvd_session Specifies the TIBCO Rendezvous rvd session used by the TIBCO Hawk Event Service for AMI communications. and the default is used instead. -datadir -datamaxnum TIBCO Hawk Installation and Configuration . See the TIBCO Hawk Installation and Configuration Guide for more details. you can omit this parameter to use the default TIBCO Rendezvous daemon session values. Default is <install-path>/data.cfg Options (Cont’d) Option (Cont’d) -hawk_domain Description (Cont’d) Sets the hawk domain name. The maximum number of rolling data files to keep. The default is to monitor an entire network as one group. -character_encoding Specifies the character encoding to be used for strings sent over all TIBCO Rendezvous transports. If TIBCO Rendezvous is only used on one network and no special TIBCO Rendezvous sessions are needed. See the TIBCO Hawk Installation and Configuration Guide for more details. The default ami_rvd_session uses rvd_session values.

-ft -JDBCalertTableFields Fault Tolerant weight for TibrvFtMember. DB2. INFORMIX and SYBASE. For example.cfg Options (Cont’d) Option (Cont’d) -datamaxsize Description (Cont’d) When one rolling data file has reached this size. enter a value greater than the default. For example. however. comma-separated alert action property fields of type VARCHAR(256) to be created as additional columns in the HawkAlertClearInfo table. To specify a value in megabytes.jdbc. URL that identifies the database connection. The format of log file entries. y and z) of type VARCHAR(256) in the HawkAlertClearInfo table. Values lower than the default size are ignored. The directory in which to store Event.microsoft. User name to connect to the database. Valid values are default (Hawk format) or ae4 (Active Enterprise format). For example. omit this option. the unit of measure for -datamaxsize is kilobytes and the default size is 1024. 10M specifies ten megabytes. By default. User password to connect to the database. it is closed and renamed. User-defined. Supported values are SQLSERVER. com. the command -JDBCalertTableFields x. -JDBCdbType Database vendor name. You can. z creates three additional columns (x.log files generated by TIBCO Hawk Event Service. the corresponding values are inserted into the database.cfg) 79 | Table 19 hawkevent. and the default is used instead. Class name for the vendor's JDBC driver. Default is no fault tolerance.sqlserver. use the suffix m or M. ORACLE. To print all log messages to the screen.SQLServerDriver. and a new data file with the original name is started. -JDBCdriverClassName -JDBCpassword -JDBCurl -JDBCuserName -log_format -logdir TIBCO Hawk Installation and Configuration . y.TIBCO Hawk Event Service Configuration File (hawkevent. When the event service receives an "onAlert" event that contains the specified properties.

The directory in which TIBCO Hawk will create rolling data files (event. If TIBCO Rendezvous is only used on one network and no special TIBCO Rendezvous sessions are needed. you can omit this parameter to use the default TIBCO Rendezvous daemon session values. omit this option. Default is <install-path>/data. and the default is used instead. -ami_rvd_session Specifies the TIBCO Rendezvous rvd session used by the TIBCO Hawk Event Service for AMI communications. The default ami_rvd_session uses rvd_session values. Those values are specified in the Self module of the agent configuration file. the following three parameters must be present and separated by white space: -rvd_session <service> <network> <daemon> Use an empty string to indicate a null value. The default is to monitor an entire network as one group.cfg Options (Cont’d) Option (Cont’d) -hawk_domain Description (Cont’d) Sets the hawk domain name.80 | Chapter 6 Configuring TIBCO Hawk Software Table 19 hawkevent. The maximum number of rolling data files to keep. The default is 5. all three parameters must be present and separated by whitespace but any of them may be an empty string to indicate a null value. See the TIBCO Hawk Installation and Configuration Guide for more details. -character_encoding Specifies the character encoding to be used for strings sent over all TIBCO Rendezvous transports. Separate domains create independent TIBCO Hawk systems. To use the default. If this options is used. Values lower than the default number are ignored. See the TIBCO Hawk Installation and Configuration Guide for more details. The agents and the event service must have the same hawk domain value in order to communicate. If you use this option. -rvd_session Specifies the TIBCO Rendezvous session used by TIBCO Hawk Event Service. -datadir -datamaxnum TIBCO Hawk Installation and Configuration . For example: -rvd _session 7474 "" tcp:7474 The default session uses null values.dat) for the event service.

TIBCO Hawk Event Service Configuration File (hawkevent.cfg) 81

|

Table 19 hawkevent.cfg Options (Cont’d) Option (Cont’d)
-datamaxsize

Description (Cont’d) When one rolling data file has reached this size, it is closed and renamed, and a new data file with the original name is started. By default, the unit of measure for -datamaxsize is kilobytes and the default size is 1024. To specify a value in megabytes, use the suffix m or M. For example, 10M specifies ten megabytes. Values lower than the default size are ignored, and the default is used instead. You can, however, enter a value greater than the default.

-ft -JDBCalertTableFields

Fault Tolerant weight for TibrvFtMember. Default is no fault tolerance. User-defined, comma-separated alert action property fields of type VARCHAR(256) to be created as additional columns in the HawkAlertClearInfo table. When the event service receives an "onAlert" event that contains the specified properties, the corresponding values are inserted into the database. For example, the command
-JDBCalertTableFields x, y, z

creates three additional columns (x, y and z) of type VARCHAR(256) in the HawkAlertClearInfo table.
-JDBCdbType

Database vendor name. Supported values are SQLSERVER, ORACLE, DB2, INFORMIX and SYBASE. Class name for the vendor's JDBC driver. For example, com.microsoft.jdbc.sqlserver.SQLServerDriver. User password to connect to the database. URL that identifies the database connection. User name to connect to the database. The format of log file entries. Valid values are default (Hawk format) or ae4 (Active Enterprise format). The directory in which to store Event.log files generated by TIBCO Hawk Event Service. To print all log messages to the screen, omit this option.

-JDBCdriverClassName

-JDBCpassword -JDBCurl -JDBCuserName -log_format

-logdir

TIBCO Hawk Installation and Configuration

82

| Chapter 6

Configuring TIBCO Hawk Software

Table 19 hawkevent.cfg Options (Cont’d) Option (Cont’d)
-logmaxnum

Description (Cont’d) The maximum number of rolling log files to keep. When the number of rolling log files exceeds this number, log entries roll over to reuse the oldest log file. The default is 4. Values lower than the default number are ignored, and the default is used instead. When one rolling log file has reached this size, it is closed and renamed, and a new log file with the original name is started. By default, the unit of measure for -logmaxsize is kilobytes and the default size is 1024. To specify a value in megabytes, use the suffix m or M. For example, 10M specifies ten megabytes.

-logmaxsize

-script

The script to execute on lost agent heartbeat. Hawk passes the agent hostname and IP address to the script to identify which agent died. Reads more command line arguments from this file. The file has exactly the same syntax and semantics as if it were a continuation of the command line. If you supply -file, it must be the last parameter on the command line. You may supply no more than one -file parameter. Prints a help message.

-file

-help

TIBCO Hawk Installation and Configuration

Creating a TIBCO Hawk Domain 83

|

Creating a TIBCO Hawk Domain
Create a TIBCO Hawk domain if you wish to isolate groups of TIBCO Hawk agents into independent monitoring sets. Remember that each TIBCO Hawk agent can belong to only one TIBCO Hawk domain and cannot communicate with the TIBCO Hawk Display program on other domains. The default is to monitor an entire network as one group. To use the default, omit the -hawk_domain option. Testing a Domain To test the domain option, temporarily set the TIBCO Hawk domain on a single system to a name such as test, then start (or restart) the TIBCO Hawk Display. If you entered a unique domain name, you only one discovered host should appear in the TIBCO Hawk Display main window. This shows that only the local agent and the local TIBCO Hawk Display are using the test domain. If the domain is as desired, you can now install it on the network systems where you want to assign specific computers to that domain. All systems assigned to that TIBCO Hawk domain appear on the Display as part of that domain. When finished with testing, change back to the default domain and restart the TIBCO Hawk Display to verify that it was correctly restored.

TIBCO Hawk Installation and Configuration

84

| Chapter 6

Configuring TIBCO Hawk Software

Creating a TIBCO Rendezvous Session
A TIBCO Rendezvous session is a direct conduit through which an application and a TIBCO Rendezvous daemon communicate. The following processes in the TIBCO Hawk system communicate with a TIBCO Rendezvous daemon through sessions: • • • • TIBCO Hawk Agent TIBCO Hawk HMA TIBCO Hawk Display TIBCO Hawk Event Service

Default Session Values
If TIBCO Rendezvous is only used on one network and no special TIBCO Rendezvous sessions are needed, use the TIBCO Rendezvous daemon session default values. To use the default TIBCO Hawk session parameters with port 7474, omit the -rvd_session command-line options. If you use this option, all three parameters must be present and separated by white space. Use an empty string to indicate a null value, for example:
-rvd _session 7474 "" tcp:7474

Setting up a TIBCO Rendezvous Daemon Session
This section provides a brief overview of session parameters used to set up a TIBCO Rendezvous Daemon (RVD) session for TIBCO Hawk monitoring. For more information on interacting with TIBCO Rendezvous daemons and sessions, refer to the books TIBCO Rendezvous Concepts and the TIBCO Rendezvous Administrator’s Guide. • The Service parameter specifies which User Datagram Protocol (UDP) service group the TIBCO Rendezvous daemon should use for session communications. The default configuration uses the service port number 7474. A service can be specified either by its name or its port number. The Network parameter specifies what network to use for outbound session communications when a computer is connected to more than one network. A network can be specified by its name or by its IP address. This parameter is also used to specify the multicast groups to use for communication.

TIBCO Hawk Installation and Configuration

g. 7474). A local daemon is specified by the communications type (always tcp) and a socket number (e. The default configuration uses the local daemon with the TCP socket number 7474. for example: tcp:remote_computer:7800 TIBCO Hawk Installation and Configuration .Creating a TIBCO Rendezvous Session 85 | • The Daemon parameter specifies which TIBCO Rendezvous daemon is to handle communication for the session.. tcp Specify a remote daemon by inserting its host name or IP address between the entry and the port number of the daemon parameter.

86 | Chapter 6 Configuring TIBCO Hawk Software TIBCO Hawk Installation and Configuration .

page 98 TIBCO Hawk Event Service Configuration. page 88 General Configuration. all TIBCO Hawk configuration is done through the command line. This is discussed in Chapter 6. Configuring TIBCO Hawk Software.| 87 Chapter 7 Using the Configuration Utility This chapter explains how to configure TIBCO Hawk using the Configuration Utility GUI. The Configuration Utility GUI interface is available only on Windows platforms. page 89 TIBCO Hawk Display Configuration. page 107 TIBCO Hawk Installation and Configuration . page 97 TIBCO Hawk Agent Configuration. For UNIX. Topics • • • • • Configuration Utility Overview.

The tabs in the configuration utility correspond to the four configuration files described in Chapter 6. TIBCO Hawk Installation and Configuration . it automatically starts the TIBCO Hawk configuration utility. The configuration utility can also be run at any time by selecting Start > Programs > TIBCO Hawk Software > Hawk Configuration. Configuring TIBCO Hawk Software.88 | Chapter 7 Using the Configuration Utility Configuration Utility Overview When the TIBCO Hawk installation program is finished on Microsoft Windows.

When you start TIBCO Hawk. Figure 1 General Configuration TIBCO Hawk Installation and Configuration . you do not need to change those values.General Configuration 89 | General Configuration The General tab contains basic TIBCO Hawk configuration items common to all TIBCO Hawk components. In most cases. the fields in these dialogs are populated with values appropriate for your configuration.

• The Service parameter specifies which User Datagram Protocol (UDP) service group the TIBCO Rendezvous daemon should use for session TIBCO Hawk Installation and Configuration . when you configure them on the systems where they are installed. Rendezvous Session Use this section to configure the TIBCO Rendezvous session. Sessions A TIBCO Rendezvous session is a direct conduit through which an application and a TIBCO Rendezvous daemon communicate. Each TIBCO Hawk agent can belong to only one TIBCO Hawk domain and cannot communicate with TIBCO Hawk Display programs monitoring on other domains. refer to the books TIBCO Rendezvous Concepts and the TIBCO Rendezvous Administrator’s Guide. enter the desired name in the Hawk Domain field. For more information on interacting with TIBCO Rendezvous daemons and sessions. To give the agent a domain name.90 | Chapter 7 Using the Configuration Utility Domain Information Separate domains create independent TIBCO Hawk systems. Give this same name to all agents that you want to include in the domain. it must connect to a TIBCO Rendezvous daemon by creating a session. The domain you enter here is used for both the TIBCO Hawk agent and for any instance of the TIBCO Hawk Display program running on that system. Because the TIBCO Hawk software uses the functionality of the TIBCO Rendezvous system. Use TIBCO Hawk domains if you want to isolate groups of TIBCO Hawk agents into independent monitoring sets. The following processes in the TIBCO Hawk system communicate with a TIBCO Rendezvous daemon through sessions: • • • • TIBCO Hawk Agent TIBCO Hawk HMA TIBCO Hawk Display TIBCO Hawk Event Service Setting up a TIBCO Rendezvous Daemon Session This section provides a brief overview of session parameters used to set up a TIBCO Rendezvous Daemon (RVD) session for TIBCO Hawk monitoring. Leave the Hawk Domain field blank to use the default domain.

security.security. the TIBCO Hawk system provides a mechanism by which you can develop your own security policy plug-in.trusted. tcp • Specify a remote daemon by inserting its host name or IP address between the entry and the port number of the daemon parameter. The Daemon parameter specifies which TIBCO Rendezvous daemon is to handle communication for the session. see the TIBCO Hawk Programmer’s Guide. This parameter is also used to specify the multicast groups to use for communication.. A service can be specified either by its name or its port number. Security Because security needs vary greatly.hawk. • The Network parameter specifies what network to use for outbound session communications when a computer is connected to more than one network.security. For more information on creating a security policy class. Do not enter the file TIBCO Hawk Installation and Configuration .General Configuration 91 | communications. enter: COM. For more information on the Trusted and Certified security policies that come with TIBCO Hawk software. on each machine where you want to use the policy. The default configuration uses the service port number 7474. To use the TIBCO Hawk Trusted Security Policy. enter the name of the security policy class.TrustedWithDomain • • To use the TIBCO Hawk Certified Security Policy.Certified To use a specific security policy. 7474). Depending on your security needs. A network can be specified by its name or by its IP address.certified.hawk. A local daemon is specified by the communications type (always tcp) and a socket number (e. you must write a Java class that implements a security policy specific to your needs. complete the Security Policy field as follows.g. enter: COM.Trusted or COM.hawk.TIBCO. • • If you are not using a security policy. Ensure that this class file is placed in <TIBCO Hawk installation directory>\Java. The default configuration uses the local daemon with the TCP socket number 7474. leave the Security Policy Class field blank. for example: tcp:remote_computer:7800. To create a security policy.trusted. see Chapter 10 on page 131.TIBCO.TIBCO.

if your fully qualified class name is com.class you would enter ASecurityPolicy. The TIBCO Hawk system creates rolling log files for each component. Log to Windows Event Log Enable this setting to log TIBCO Hawk events in the Application section of the Windows Event Log. For example. if your Java class file is named ASecurityPolicy.92 | Chapter 7 Using the Configuration Utility extension. Logging The TIBCO Hawk system logs specific events as they occur.MySecurity. When the number of log files exceeds the number set in the Maximum Number of Log Files TIBCO Hawk Installation and Configuration . The TIBCO Hawk Display (Display. select Start>Programs>Administrative Tools>Event Viewer. and a new log file with the same name is started. the TIBCO Hawk agent) under the Source column. The events are categorized as errors.log). it is closed and renamed. If your security policy class is not part of the default package (for example.log). The settings configured in the Logging panel control logging of the following components: • • • The TIBCO Hawk agent (Hawk.class in <TIBCO Hawk installation directory>\Java\com\mycorp. To access the viewer. you will place MySecurity. you will need to create the appropriate directory structure beneath <TIBCO Hawk installation directory>\Java that corresponds to your package name and place your class file in the appropriate location. The logs provide a detailed picture of the status and health of each of the TIBCO Hawk components to aid in diagnosing problems. or informational events. For example. Log to Hawk Log Files Enable this setting to log TIBCO Hawk events using a set of log files in the directory you specify in the Log Files Directory field. Events logged by the TIBCO Hawk system contain the component name (for example. when one file has reached the size specified in the Maximum Size of Log Files field. These events can be viewed using the Windows Event Viewer. then select Log>Application from the Event Viewer menu to view Application events.log). The TIBCO Hawk Event Service (Event. if you used the Java "package" directive in your code).mycorp. warnings.

for example. The default value is 5. enter the maximum log file size. You can enter at minimum 5 and at maximum 999. Log Message Format This field allow you to select the format of log file entries. The only reason to change this value is for compatibility with other TIBCO Rendezvous applications not using UTF-8. At this point. The default is 1024. The default value is <TIBCO Hawk installation directory>\Log. you have configured a maximum of five log files. Normally there is no need to change this value. Enter only digits. This value is specified using Microsoft Windows code page values. thus maintaining a total of five rollover files. Codepage The Codepage configuration option indicates the desired character encoding to be used by the HMA when converting multi-byte characters (MBCS) to UNICODE.General Configuration 93 | field. Note that the maximum log file size is 2097151 kilobytes. log files roll over until there are five files (named file1. HMA Configuration AMI Timeout Specifies the amount of time the Hawk Agent should wait for HMA method invocations to complete before timing them out. • Maximum Number of Files Enter the maximum number of rolling log files to create. The default is 10000 milliseconds. • Maximum Size of Log File In this edit field. on machines under extreme stress where method invocations are timing out. as listed at the following URL: TIBCO Hawk Installation and Configuration . If. which is the Microsoft Windows ID for UTF-8. The log thus retains the latest log information and discards the oldest. the next rollover eliminates file5 and renames file4 to file5. • Log Files Directory Enter the name of the directory where the TIBCO Hawk system should place its log files. Either the existing Hawk format (Default) or the ActiveEnterprise format (ae4) can be specified. log entries roll over to reuse the oldest log file. The default codepage identifier is 65001. file2… file5). this option allows the timeout value to be increased. however. in kilobytes. and which will work for all locales.

if you want to specify Latin-1 locales (such as French). click the Advanced button to access the Advanced Configuration dialog.com/library/default. Advanced Configuration On the General configuration tab. See Code Page Identifiers on page 177 for the list of code page identifiers.asp If you change the Codepage value. Figure 2 Advanced Configuration TIBCO Hawk Installation and Configuration . For example.asp?url=/library/en-u s/intl/unicode_81rn.microsoft. you must also change the value of the Character Encoding.94 | Chapter 7 Using the Configuration Utility http://msdn. page 95. the Codepage value must be 1252 and the Character Encoding value must be ISO-8859-1.

in which case it is automatically updated. Java Virtual Machine Command Line Options This section allows you to set the Java Virtual Machine command line options for use by the TIBCO Hawk Display.cfg). Character Encoding The Character Encoding configuration option indicates the desired character encoding to be used by the Agent. which sets the character encoding for the TIBCO Hawk HMA. This is also the encoding used for the character data that TIBCO Hawk transmits over TIBCO Rendezvous. Type in the new JRE path or set it to blank. you must also change the Codepage value. if an option in the configuration file you select is blank but a custom value is specified for that option in the configuration utility. TIBCO Hawk will use the default (blank) value for that option. For example. If you change this value. and Event Service. add the -Xrs option to the agent's JVM command line (JRE 1. Prevent an Agent from Exiting For example. such as a need for more memory. Configuration File Options This section allows you to specify configuration files (such as hawkagent. the values in that file override the corresponding values entered into the configuration utility. you must update the Java field. on your system. and Event Service.1 only).General Configuration 95 | Java Runtime Configuration The Java Runtime Configuration section of the window allows you to select a specific JRE file to use and to specify the JVM executable. The only reason to change this setting is for compatibility with other TIBCO Rendezvous applications. The default setting of UTF-8 will work for all locales. When you specify a configuration file. If you have specific applications that require a nonstandard configuration. Home Directory If you install a new JRE after installing TIBCO Hawk. use the Command Line Options fields to custom-configure the Java environment. This is useful if there are several JRE installations with different version levels. To prevent the agent from exiting. Display. TIBCO Hawk Installation and Configuration . an agent can exit when a user logs off the desktop.3. Agent.

TIBCO Hawk Installation and Configuration .96 | Chapter 7 Using the Configuration Utility Possible Character Encoding values are listed in Table 22. Code Page Identifiers. on page 178.

TIBCO Hawk Display Configuration 97 | TIBCO Hawk Display Configuration The Display tab allows you to specify a previously created layout to be loaded automatically at startup and to specify a variables file.Properties. There is one line per variable where each line has the format variablename=value. The variables file can pass data to define external variables to be used in either host or tool menu commands. The format of the file is that used by the standard Java class java.util. Variables Use the Variables option to specify a variables file. TIBCO Hawk Installation and Configuration . Figure 3 Display Configuration Display Use the Display option to specify the previously created layout you want loaded automatically at startup.

The default name for the TIBCO Hawk agent is the host name of the computer on which it is installed.98 | Chapter 7 Using the Configuration Utility TIBCO Hawk Agent Configuration The Agent tab allows you to configure options specific to the TIBCO Hawk agent. Figure 4 Agent Configuration Tab Identification Agent Name The agent name appears in the TIBCO Hawk Display. TIBCO Hawk Installation and Configuration .

com. To specify an agent domain for a TIBCO Hawk agent.) or specify another directory. ). Cluster Enter the container name in which this agent is to appear in the TIBCO Hawk Display. TIBCO Hawk Installation and Configuration . When the radio button for one of these modes is selected. You can either use the default auto configuration directory (<TIBCO Hawk installation directory>\AutoConfig. Manual. enter the desired domain in the Agent Domain field. you usually do not need to list any rulebases in the rulebase list dialog. and Repository configuration modes are mutually exclusive.tibco. The cluster name must be enclosed within quotes. Automatic Configuration Mode To use Automatic configuration. leave the Agent Name field blank. Using both a rulebase map and the rulebase list dialog increases the complexity of managing your monitoring configuration. The default is to use Automatic configuration. for example. To use a different name. enable the Auto radio button. The rulebase list dialog (which corresponds to the UNIX or file config option -rulebases) is provided to maintain backward compatibility with previous versions of TIBCO Hawk that do not contain the rulebase map feature. the other options are disabled. Configuration Modes Use the options in this panel to set up what mode the agent is to use when it searches for configuration objects.TIBCO Hawk Agent Configuration 99 | To use the host name as the agent name. if the name contains spaces. pa. If you are using the rulebase map. Automatic. enter a name as desired. The delimiter for path entries is a semicolon ( . Agent Domain An agent domain must be specified when two computers within the same TIBCO Hawk domain have the same name but reside in different network domains. The default name for the container is the IP subnet address.

the agent will load the Schedules configuration file and all rulebase configuration files from the automatic configuration directory at startup. Any rulebases loaded by the agent are not written to a local cache. It searches for these using the Manual Configuration Path. The only rulebases an agent may load at startup are the ones: • • • specified by the rulebase map. the agent searches the Manual Configuration Path for the Schedule file and the rulebase map file. With automatic configuration. and the RuleBaseEngine:loadRuleBase() microagent method are not used. all load-by-reference rulebase loading mechanisms are disabled. the Manual Configuration Path. In addition. Use of the methods RuleBaseEngine:loadRuleBaseFromFile() and RuleBaseEngine:unloadRuleBase() do not affect the autoconfiguration directory. the rulebase is stored in the autoconfiguration directory. There is no notion of an autoconfiguration directory. Manual Configuration Mode When manual configuration is selected. However. See the TIBCO Hawk Administrator’s Guide and the TIBCO Hawk Methods Reference for more on these features and microagent methods. TIBCO Hawk Installation and Configuration . The only other mechanism by which an agent can load a rulebase after this point is through invocation of RuleBaseEngine:loadRuleBaseFromFile() or via SendTo from the Display. Repository Cache Directory. contained in any RuleBaseIncludes. Repository Path. Note that the loaded startup rulebases may have RuleBaseInclude lists that will trigger further searches of the manual configuration path for additional rulebases. the rulebase is also removed from the autoconfiguration directory. When a rulebase is removed from an agent via the Display. listed in the Rulebases dialog. See the TIBCO Hawk Console API Reference for information on configuring microagent plug-ins. the RuleBaseInclude feature. Also at startup. See the TIBCO Hawk Administrator’s Guide for more on these features. the agent searches the path for any rulebases specified in the Rulebases dialog and loads them. Note that manual configuration mode is also known as Configuration Path mode. When a rulebase is sent to an agent via SendTo or Apply Changes from the Display. the agent has a list of rulebase names. After evaluating the rulebase map. Therefore. rulebase maps.100 | Chapter 7 Using the Configuration Utility When Automatic Configuration mode is enabled. using fully qualified filenames. at startup. the microagent method RuleBaseEngine:loadRuleBaseFromFile() is allowed. and the Rulebases button are not enabled.

The default directory is <TIBCO Hawk installation directory>\Config. Do not use a file extension when entering rulebase names. then click OK: — To add a rulebase to the list. Click Rulebases to bring up the Rulebase Configuration dialog Figure 5 Rulebase Configuration Dialog 4. enter a a rulebase filename. as follows.hrb extensions are only used for rulebase files. The . 3. select it and click Delete. 1. click Add. and click OK. See RuleBaseEngine:loadRuleBase() and RuleBaseEngine:loadRuleBaseFromFile() for more information. you specify a configuration path to use. and a list of rulebases. specify a list of directories to be searched by separating directory entries with semicolons. In the Manual Configuration Path field. 2. — To remove a rulebase from the list. TIBCO Hawk Installation and Configuration .TIBCO Hawk Agent Configuration 101 | To set up manual configuration. Do either of the following until your list is as desired. Select the Manual radio button.

you specify a repository path. However. and click OK. then click OK: — To add a rulebase to the list. specified in the Repository Cache Directory field. In the Repository Path field. Repository If a TIBCO Hawk agent is to act as a repository for the TIBCO Hawk system. Instead of a configuration path. TIBCO Hawk Installation and Configuration . See the TIBCO Hawk Administrator’s Guide for an explanation of repositories. You can also specify a list of rule bases. this step is recommended. specify a path for the repository and a repository cache to use in case the repository is off-line. specify the list of repositories to be searched.). The default is <TIBCO Hawk installation directory>\Repository. 3. This cache is used in the event of a repository failure. Select the Repository radio button. select it and click Delete. and rulebase maps). Click Rulebases to bring up the Rulebase Configuration dialog (Figure 5). as follows. and a list of rulebases. 1. Do either of the following until your list is as desired. if no rulebase map is supplied by the repository. Agents can determine if a configuration object in their cache is identical to the one in the repository and will load it directly from the cache or update it from the Repository as appropriate. enter a a rulebase filename. enter a name (with no spaces or periods) for the repository and a path for storage of the configuration object files. To use repository mode.102 | Chapter 7 Using the Configuration Utility Repository Configuration Mode Repository mode is also a type of manual configuration mode and operates in a similar way to Manual Configuration mode. specify a repository cache directory. 2. 4. The list should consist of the repository names separated by semicolons (. The agent communicates with a list of repositories in this path to obtain all configuration objects (rulebases. Step 4 is optional. schedules. The default is <TIBCO Hawk installation directory>\cache. with Repository mode all configuration objects loaded from the Repository may be cached in a local directory. click Add. In the Repository Cache Directory field. — To remove a rulebase from the list. and also to minimize network traffic. Repositories are kept on the network and can be accessed by multiple agents. Unlike Manual Configuration Mode.

The default is 10 seconds. To use a different value. Block Size (KB) The size of the block that is read from the log file each time it is scanned. Evaluation Rate (secs) The rate at which all the logfiles being monitored by the agent are evaluated. Heartbeat The TIBCO Hawk agent heartbeat interval can be set on each computer where an agent is installed. AMI Applications instrumented with AMI must create and use a TIBCO Rendezvous session to connect with a TIBCO Rendezvous daemon (rvd). Logfile Microagent Scan Rate (secs) The rate at which the log file that is being monitored is scanned for new entries. The default is 300 seconds.TIBCO Hawk Agent Configuration 103 | MicroAgent Plugins Use the Plugins Directory option to specify the directory that the TIBCO Hawk Agent should search when loading microagent plugins. as desired. The variables file can pass data to define external variables to be passed to rules for use in rulebase configurations. The TIBCO Hawk Display uses this value to determine when to mark an agent dead. The default heartbeat interval is 30 seconds. leave the value in the Interval field set to 30. The default is 16 KB. To use the default value of 30 seconds. Variables Use the Variables option to specify a variables file. TIBCO Hawk Installation and Configuration . enter a number of seconds.

no additional action is required. See the next section for details. you must create additional AMI sessions. See Chapter 10 on page 131 for details. TIBCO Hawk Installation and Configuration . It lists any AMI Rendezvous sessions already created. You can specify any number of additional TIBCO Rendezvous sessions for a TIBCO Hawk agent to monitor. near the bottom of the Agent tab of the TIBCO Hawk Configuration Utility. The next section describes how to add a session. as long as those applications are running.104 | Chapter 7 Using the Configuration Utility To monitor an AMI-instrumented application that uses the same session parameters as those used in the TIBCO Hawk configuration. To Create an AMI Session 1. You can specify a secure Rendezvous session that uses Rendezvous DataSecurity along with digital certificates to guarantee the integrity and authenticity of the messages sent to applications instrumented with AMI. You can add. You see the AMI Rendezvous Session Configuration Dialog. specify RVDS in the AMI Rendezvous Session dialog (Figure 7). you must create additional AMI sessions as required. edit. and delete sessions using the AMI Rendezvous Session Configuration dialog. To monitor AMI-instrumented applications that use different session parameters than those used in the TIBCO Hawk configuration. TIBCO Hawk agents can use rulebases that refer to the applications. To do this. All sessions in the list will be accessible to the TIBCO Hawk agent. Click AMI Sessions. Applications using these sessions appear as primary sessions in the TIBCO Hawk Display in the same list as managed applications (and microagents). AMI Rendezvous Session Configuration To monitor AMI-instrumented applications that use different session parameters than those used in the TIBCO Hawk configuration.

Change the Session Name and other values as required (see next steps). You see the Add AMI Rendezvous Session dialog. highlight the desired session and click Derive. Enter a Session Name and select a Session Type for the AMI session. Do one of the following: — To create a new session click Add. Figure 7 Add AMI Rendezvous Session 3. — To create a new session based on an existing one. showing the values for the session you selected.) TIBCO Hawk Installation and Configuration .TIBCO Hawk Agent Configuration 105 | Figure 6 AMI Rendezvous Session Configuration 2. Select RVDS to specify a secure Rendezvous session that uses Rendezvous DataSecurity along with digital certificates to guarantee the integrity and authenticity of the messages sent to applications instrumented with AMI. You see the Add AMI Rendezvous Session dialog (Figure 7). (See Chapter 10 on page 131 for details.

TIBCO Hawk Installation and Configuration . Click OK to close the AMI Session window and add the AMI session to the list of sessions. the arguments are the same and the resulting sessions are similar. Use the same values as those used by the application to initialize its TIBCO Rendezvous daemon session. with session parameters specified as — Service: 7474 — Network: . In the Session Parameters panel.106 | Chapter 7 Using the Configuration Utility 4.) The default values for an AMI session are RVD. enter values for Service. (Although AMI session parameters are named differently from their non-AMI counterparts. Network. and Daemon. — Daemon: TCP: 7474 5. check the application’s configuration files or documentation. To determine these values.

log). host-ip=160.dat log file.26. Allows persistence of TIBCO Hawk Events using JDBC. TIBCO Hawk Installation and Configuration . The Event. Be careful not to confuse TIBCO Hawk Event Service data files (Event. at Sat Dec 18 11:40:23 EST 1999 RULEBASE_ADDED : AgentID={ host-name=asture. Provides Event Service fault tolerance.101.101.26.dat) with Event Service log files (Event.0 }. The event service AMI methods are described in the TIBCO Hawk Methods Reference. dns=none.dat log file service entries are shown below.dat Event. network-ip=160. Detects and responds to agent termination using a user-supplied command line executable. These functions are described in the TIBCO Hawk Administrator's Guide.0 }.108.TIBCO Hawk Event Service Configuration 107 | TIBCO Hawk Event Service Configuration The Event Service tab allows you to configure options specific to the TIBCO Hawk Event Service.log data files contain the data produced by the Event Service. The TIBCO Hawk Event Service is a separate process that collects information about TIBCO Hawk Agents.108.log file is discussed in the TIBCO Hawk Administrator’s Guide.26. Uses AMI instrumentation to asynchronously notify users of events on a particular Hawk domain. alert-state=0. log files record the state of the Event Service itself. dns=none. Logging File The event service records the following items: • All alerts raised and cleared by TIBCO Hawk agents across the network. network-ip=160. AGENT_ALIVE : agent={ host-name=asture. as well as changes in an agent’s alert level (as would be shown by a color in the TIBCO Hawk Display) All instances of agent activation and expiration • Some example event.101.101. It performs the following functions: • • • • • Logs the activity of TIBCO Hawk agents in the event. • • Event.26. host-ip=160.

network-ip=160. host-ip=160. You must manually enable it. host-ip=160.hawk.microagent. at Sat Dec 18 11:48:18 EST 1999 RULEBASE_REMOVE : AgentID={ host-name=ultrahawk1.246.246. alert-id=950.com. dns=none.0 }. TIBCO Hawk Installation and Configuration .hawk.246. dns=none.246. dns=none. network-ip=160. at Sat Dec 18 11:50:36 EST 1999 Command-Line Executable The Event Service can call a command-line script or executable when the heartbeat of a TIBCO Hawk agent is lost (not received for a specified length of time). alert-state=50. MicroAgentID=COM. host-ip=160.110.com. at Sat Dec 18 11:50:05 EST 1999 AGENT_REINITIALIZED : agent={ host-name=lexus.101. state=0.101. This usually means that the agent process has terminated or that network communication has been interrupted. Disabling and Enabling the Event Service The Event Service is not enabled by default. host-ip=160..0 }.microagent. at Sat Dec 18 11:50:05 EST 1999 MICROAGENT_REMOVE : AgentID={ host-name=ultrahawk1.110. time-received=Sat Dec 18 11:51:20 EST 1999 }. dns=nytek. host-ip=160. This facility could be used to send an e-mail or page.101.26.101.101.246. at Sat Dec 18 11:40:23 EST 1999 MICROAGENT_ADDED : AgentID={ host-name=asture.SysInfo.101.108 | Chapter 7 Using the Configuration Utility rulebase=HawkServices-WinNT. alert-state=50.101.16. network-ip=160. dns=none. reason=test evaluated to FALSE. network-ip=160. network-ip=160.101.TIBCO. host-ip=160.101. network-ip=160.26. host-ip=160.TIBCO. rulebase=Solaris2x.18. at Sat Dec 18 11:51:20 EST 1999 ALERT_CLEARED : agent={ host-name=boxter.101.0 }.101.16.246.16. dns=none.110. or to take some other automated action.SysInfo.101.110. network-ip=160.0 }.246.0 }.101. rulebase=Filesystem.110. at Sat Dec 18 11:40:23 EST 1999 AGENT_EXPIRED : agent={ host-name=ultrahawk1. alert-text=Disk space on /opt running low.101. MicroAgentID=COM.0 }. dns=nytek. at Sat Dec 18 11:50:05 EST 1999 ALERT_RECEIVED : alert={ agent={ host-name=puck.0 } alert-id=589.246.169.108.

click the Automatic radio button. After entering the appropriate data in this dialog. Select TIBHawk Event in the list of services and click Startup. then click OK. The status in the list is blank. click OK to save the changes.TIBCO Hawk Event Service Configuration 109 | Enabling the Event Service To enable the TIBCO Hawk Event Service. 4. Choose Start>Settings>Control Panel. indicating the service is stopped. The service is shown in the list as Automatic. then double-click on the Services icon. Select TIBHawk Event in the list of services and click Startup. If the service is already running. 2. disable the TIBCO Hawk Event Service in the Windows Services control panel as follows: 1. you configure how dead agents are handled and how Event Service data files are managed. The service is shown in the list as Started. 1. 4. TIBCO Hawk Installation and Configuration . Disabling the Event Service To disable the TIBCO Hawk Event Service. 2. Click Start to start the Event Service. then double-click on the Services icon. Choose Start>Settings>Control Panel. Configuring the Event Service in Windows XP and 2000 On the Event Service tab of the TIBCO Hawk Configuration Utility (Figure 8). In the Service window. 3. The service is shown in the list as disabled. click the Disabled radio button. then click OK. In the Service window. 3. click Stop to stop it. The new settings are immediately applied to the instance.

The IP address of the computer on which the agent is installed.110 | Chapter 7 Using the Configuration Utility Figure 8 TIBCO Hawk Event Service Dialog Agent Dead Handling You can write a script to be called when an agent does not respond for a specified length of time. in this order: 1. identical to the name of the computer on which the agent is installed). In the Script File field. By default. TIBCO Hawk Installation and Configuration . 2. The name of the agent (by default. Two command-line arguments are sent to the script. specify the name of this script file. this field is blank and no script is called when the agent does not respond.

Database Connection: URL that identifies the database connection. The default maximum is 1024 kilobytes.microsoft.jdbc. The default is five. As with TIBCO Hawk log files. Database Type: The database vendor. page 92). Password: User password to connect to the database. When this feature is enabled. Select the appropriate vendor from the dropdown menu. you can set the following options: • • • The directory in which to store data files. Separate instances of TIBCO Hawk must be running on at least two machines in order to use fault tolerance. Fault tolerance must be enabled on each instance. The maximum number of data files to keep. For example. fill in the following fields: • • • • • User Name: User name to connect to the database. The TIBCO Hawk Event Service writes to rolling data files in the same way that the standard TIBCO Hawk logging system writes to rolling log files (see Logging. The maximum size of a data file.SQLServerDriver. TIBCO Hawk Installation and Configuration . The default data file directory is <TIBCO Hawk installation directory>\Data. com. You can leave a parameter field empty (blank) to indicate a null value. AMI Rendezvous Session Check Enable Dedicated AMI Session if your Event Service process needs to use a dedicated Rendezvous session for AMI transport. specify the following values. see Rendezvous Session on page 90. Database Configuration Check the Enable Event Persistence box to enable event persistence.sqlserver. • • • • Service number Network TCP daemon For more information on these.TIBCO Hawk Event Service Configuration 111 | Event Data Check the Enable Event Service Data Files box to enable logging. JDBC Driver Class Name: Class name for the vendor's JDBC driver. When the session is enabled.

When an instance fails. The highest weight is 1. Defaults This button clears all fields and returns them to their default values. the next-highest instance is activated. TIBCO Hawk Installation and Configuration . The weights do not need to be consecutive. If two or more TIBCO Hawk Event Services have the same weight. meaning the instance outranks all others. starting with 1.112 | Chapter 7 Using the Configuration Utility Fault Tolerance Check the Enable Fault Tolerance box to enable fault tolerance on this instance. This instance joins a fault tolerant group named HawkEventService:hawkdomain. Weight Assign the weight of this instance using a positive integer. Each service should have a unique weight. Note the following considerations: • • • • • Each TIBCO Hawk Event Service instance in the fault tolerance group must be assigned a weight. Each weight must be a positive whole number. Rendezvous fault tolerance software assigns a rank to them but does not update the Weight field in this dialog with the new value. where hawkdomain is the value specified in the General tab.

page 115 Setting up Network Communication on UNIX. page 121 TIBCO Hawk Installation and Configuration . Topics • • • • • Agents and the Network. page 117 Setting Up Network Communication in Windows. page 114 Configuring for Network Communication. It also explains how to access TIBCO Hawk monitoring through a dial-up connection.| 113 Chapter 8 Using TIBCO Hawk Across Nets or Subnets This chapter explains how to configure TIBCO Hawk monitoring for use across networks or subnets. page 118 Using the TIBCO Hawk Display over a Dial-up Network Connection.

Network traffic for these protocols is not generally routed openly between subnets or networks. TIBCO Rendezvous software uses a process known as a routing daemon (rvrd) to allow TIBCO Rendezvous messages to transcend multiple networks. but if the TIBCO Hawk agents are installed on computers in different subnets or networks. If all TIBCO Hawk agents are installed on computers within one subnet. you must change their configuration to allow them to communicate using the routing daemon. rvrd. IP Multicast traffic can be passed through configuration of the network routers. no configuration changes are necessary. but IP Broadcast must use other means to reach other subnets.114 | Chapter 8 Using TIBCO Hawk Across Nets or Subnets Agents and the Network The TIBCO Rendezvous messaging software that TIBCO Hawk uses operates within either IP Broadcast or IP Multicast protocols. TIBCO Hawk Installation and Configuration .

TIBCO Hawk Installation and Configuration . Figure 9 Sample Routing Daemon Configuration for TIBCO Hawk Messaging Subnet 1 Subnet 2 Subnet 3 Router host A host B (hub) host C neighbor connection Router Configuring Hawk Rendezvous Subjects When creating Rendezvous routing daemon (rvrd) routes between networks. For details on using the Browser Administration Interface and creating Rendezvous routes. and there is only one TIBCO Hawk domain.Configuring for Network Communication 115 | Configuring for Network Communication Figure 9 shows a sample routing daemon implementation where all TIBCO Hawk messages are available throughout the network. the routed subjects can be used to control which agents can be discovered by TIBCO Hawk Console instances located on different parts of the network. For TIBCO Hawk networks. On these machines. as applicable. However. All other rvd processes in each subnet will obtain information from the other subnets through rvrd processes on host A. Host B acts as the hub. you must specify the Rendezvous message subject names that can be passed between the networks. in addition to its routing functions. These are configured using the routing daemon's Browser Configuration Interface. the rvrd process would replace the regular rvd process. see TIBCO Rendezvous Administration. B or C. the rvrd will support the local applications just as rvd would.

agent.pa.*.repository. with references to Figure 9: On the spoke networks (Hosts A and C): Import: "_HAWK. anywhere on the network. as shown: Import and Export: "_HAWK.nl. However.nl.console.*.agent4.>" Isolated Spokes and DMZ networks In many large enterprises. a central hub network can be used to view all agents for the purposes of Hawk alert management. In this case.>" If a Hawk Repository is used.pa.nl.*.pa. * . is the Hawk Domain parameter. but not on networks outside their control.*.agent4. application groups may be allowed to discover Hawk agents on their own networks.116 | Chapter 8 Using TIBCO Hawk Across Nets or Subnets Full Visibility The simplest TIBCO Hawk routing configuration is full visibility of all agents from any TIBCO Hawk Console.p1.*.p1.>" Import: "_HAWK.nl.*. In this case.nl.*.p1. This is configured as shown. add the following to both sides: Import and Export: "_HAWK.p1.pa. and so on. this subject configuration will prevent any of the "inside" agents being discovered in the event a Hawk Console is launched from the "outside.p1.>" Export: "_HAWK.agent.p1. centralized rulebase administration.>" Export: "_HAWK.console.nl. the routing daemons running on the spoke networks are configured to allow traffic in only from the central hub network consoles.>" The second subject segment.>" Import: "_HAWK.>" On the central hub network (Host B): Export: "_HAWK." TIBCO Hawk Installation and Configuration .pa. the subject configuration of the Rendezvous routing daemons is identical across all routing daemons.pa.nl. When used on DMZ networks.

Move or rename the rvd binary from the rv_install_dir/bin directory. Routing Daemon Configuration for UNIX When any Rendezvous application starts. rvrd reads this file when the process starts. 3. see TIBCO Rendezvous Administration.Setting up Network Communication on UNIX 117 | Setting up Network Communication on UNIX When starting the rvrd process. they will find the rvrd wrapper script instead of the rvd process itself. For details on the routing daemon command line parameters. the libraries will cause a Rendezvous daemon (rvd) process to start if one is not already running. Once the rvd process is running. This can cause coordination issues in starting the rvrd prior to any applications. TIBCO Hawk Installation and Configuration . and becomes a problem if the rvrd dies during run time and an rvd is restarted in its place. For details on using the Browser Administration Interface. 2. and writes this file each time you change the configuration using the browser administration interface. Create a shell script named rvd that starts the rvrd process with the desired command line arguments. To set up the script: 1. a Rendezvous routing daemon (rvrd) process cannot be started with the same transport parameters. When the Rendezvous libraries search the PATH for an executable named rvd. You can avoid these problems by creating a simple wrapper script to always start the rvrd process in lieu of an rvd process. Place the rvd script in the rv_install_dir/bin directory of each machine where an rvrd process is required to run. see TIBCO Rendezvous Administration. This will always ensure that the rvrd process is started or restarted properly. to store the parameters that configure rvrd. which is specific to TIBCO Rendezvous. A TIBCO Rendezvous license file is required to use TIBCO Hawk with rvrd. use the -store <file name> argument.

Choose Start > Settings > Control Panel > Services. 1. Click Startup. Log on with administrative privileges. TIBCO Hawk Installation and Configuration . Making TIBCO Hawk Services Depend on the Routing Daemon Windows Service Once the rvrd service has been installed. 3. 2. Select the service in the list of services. causing an rvd to launch and preventing the rvrd from running. Starting the Routing Daemon Service Automatically in Windows Once you have configured the rvrd process as a Windows service. Click OK. set it up to start automatically when the operating system starts. you must install the TIBCO Rendezvous routing daemon as a Windows service and configure the TIBCO Hawk services to depend on it. and TIBHawkEvent). 5. as shown in the following steps. b. enter regedt32 in the Open drop-down list box and click OK. use the TIBCO Rendezvous Services Configuration Program. see TIBCO Rendezvous Administration. 2. Select Start > Run. as follows: a. To configure the appropriate command line parameters for the rvrd process and install it as a Windows service. regedt32. as shown in the following steps: 1. TIBHawkHMA. For further details on this program and routing daemon command line parameters. In the Run dialog that appears. If this is not done.exe. Run the Windows registry editor. Click the Automatic radio button. 4. the TIBCO Hawk services may start first.118 | Chapter 8 Using TIBCO Hawk Across Nets or Subnets Setting Up Network Communication in Windows Installing a Routing Daemon as a Windows Service Because TIBCO Hawk processes are installed as Windows services. rv_install_dir\bin\rvntscfg. add a DependOnService parameter in the service registry to each of the installed TIBCO Hawk services (TIBHawkAgent.

. navigate through the hierarchy to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TIBHawkAgent as shown in Figure 10. Figure 10 The TIBCO Hawk Services in the Windows Registry Editor 4.Setting Up Network Communication in Windows 119 | 3. Add the DependOnService value to the Windows Registry. Choose Edit > Add Value. 5. In the registry editor. TIBCO Hawk Installation and Configuration .

Select a Data Type of REG_MULTI_SZ. Figure 11 Adding the rvrd Service Value to the Windows Registry 10. TIBCO Hawk Installation and Configuration . 12. 8. 7. 9. Exit regedt32. enter DependOnService in the Value Name edit box. In the Add Value window that appears.120 | Chapter 8 Using TIBCO Hawk Across Nets or Subnets 6. Reboot your system. Click OK. In the Multi-String Editor window that appears (as shown in Figure 11). Repeat from step 3 for TIBHawkHma and TIBHawkEvent (if installed). enter rvrd in the Data edit box and click OK. 11.

123.12:7474 When the dial-up connection is established. You cannot spawn a remote daemon. From the offsite system. Enter the remote computer’s name as part of the Daemon parameter. The remote host must already be running a correctly configured TIBCO Rendezvous daemon.123 tcp:123.123 tcp:office_computer:7474 or startdisplay -rvd_session 7474 123. or event service). you can monitor your network remotely. restart the TIBCO Hawk Display. Establishing a Dial-up Connection in Windows By setting the TIBCO Hawk daemon parameter to point to a TIBCO Rendezvous daemon on your network. 2. The easiest way to achieve a dial-up connection is to choose a machine that already has a properly configured TIBCO Hawk agent or TIBCO Hawk Display running.123. Establishing a Dial-up Connection in UNIX To establish a dial-up connection using UNIX. enter the Windows TIBCO Hawk Configuration program. supply the command-line option -rvd_session to the startdisplay script: startdisplay -rvd_session <service> <network> tcp:<internal rvd host>:<port> For example: startdisplay -rvd_session 7474 123. If you are using a machine that has dial-in access to your network.Using the TIBCO Hawk Display over a Dial-up Network Connection 121 | Using the TIBCO Hawk Display over a Dial-up Network Connection The TIBCO Hawk system supports remote monitoring. This procedure can also be used for remote networks without an rvrd. as follows: tcp:<internal rvd host>:<port> TIBCO Hawk Installation and Configuration .123. and no other TIBCO Hawk services (such as HMA. 1. and should only run the TIBCO Hawk Display. Standard connection techniques such as PPP and a simple configuration change are all that are required. agent.123. you effectively make your TIBCO Hawk Display appear to be located on that system. The dial-in computer must have an IP address on the network.

TIBCO Hawk Installation and Configuration .123.12:7474 3. restart the TIBCO Hawk Display. For example: tcp:office_computer:7474 or tcp:123.123.122 | Chapter 8 Using TIBCO Hawk Across Nets or Subnets where <internal rvd host> is any computer on the internal network which a TIBCO Rendezvous daemon process is running. When the dial-up connection is established.

page 127 TIBCO Hawk Installation and Configuration . page 124 Using the TIBCO Hawk Sample Applications.| 123 Chapter 9 TIBCO Hawk Sample Rulebases and Applications If. For example. page 125 The Sample AMI API Applications. the TIBCO Hawk software is installed in any location other than the default path of /usr/tibco/hawk. Topics • • • Using the Sample TIBCO Hawk Rulebases. on UNIX. you must update all rules using the logfile:onNewLine data source in the sample rulebases. HawkAgent-Unix (in the directory $HAWK_ROOT/samples) must be updated to reflect the correct path to $HAWK_ROOT/log.

it is added to the Rulebase List. The Open dialog displays. click Apply Changes to Agent. Choose File>Load From File. 3. follow the instructions below: 1. — If a rulebase with this name is loaded on the agent. Navigate to the desired rulebase file and click Open. You cannot edit those rules. On UNIX. In the TIBCO Hawk Display. If you are using Automatic Configuration mode. or Cancel to leave the dialog. you must update all rules using the logfile:onNewLine data source in the sample rulebases. The Rulebase List for Agent dialog displays. HawkAgent-Unix (in the directory $HAWK_ROOT/samples) must be updated to reflect the correct path to $HAWK_ROOT/log.124 | Chapter 9 TIBCO Hawk Sample Rulebases and Applications Using the Sample TIBCO Hawk Rulebases The TIBCO Hawk sample rulebases are installed in the directory $HAWK_ROOT/samples/rulebases. if the TIBCO Hawk software is not installed in the default location (/usr/tibco/hawk). 2. the loaded rulebase is copied to your auto-configuration directory and will be loaded at startup. To save changes to memory. For example. a dialog displays your options. TIBCO Hawk Installation and Configuration . — If a rulebase with this name is not already loaded. 4. To use any of these rulebases. NoDataSource errors can result if any rules in the rulebase use data sources that are unavailable on the agent where the rulebase is loaded. Click OK to overwrite the existing rulebase. right-click on the desired agent and select Get Configuration>Rulebases from the menu.

Use of the TIBCO Hawk AMI APIs is recommended because they handle all the TIBCO Rendezvous and AMI details for you. refer to Using TIBCO Hawk Across Nets or Subnets. The TIBCO Rendezvous session parameters are hard-wired into the code of these sample applications. like all AMI applications. AMI is used to instrument applications so that TIBCO Hawk agents can directly monitor them. You can use the TIBCO Rendezvous APIs to directly implement the AMI protocol or you can use the TIBCO Hawk AMI APIs which implement the AMI protocol for you. TIBCO Hawk Installation and Configuration . For information on configuring primary and AMI session parameters for a TIBCO Hawk agent on the Windows platform. Use of the APIs also ensures that your applications will be compatible with future releases of TIBCO Hawk and AMI. page 113. have both a display name and an internal name. Configuring TIBCO Rendezvous Session Parameters All the sample applications require TIBCO Rendezvous session parameters in order for those applications to establish a TIBCO Rendezvous session with the local TIBCO Hawk agent. Sample AMI Application Names These samples. Please refer to the TIBCO Hawk Programmer's Guide for a complete description of AMI. To change the session parameters you must edit the files and change the values of the TIBCO Rendezvous session constant. The internal name is the name by which the TIBCO Hawk system uniquely identifies this AMI application and distinguishes it from other AMI applications. refer to Chapter 6. making programming AMI simpler and more foolproof. Configuring TIBCO Hawk Software. The display name is a user-friendly name that is used in the TIBCO Hawk Display.Using the TIBCO Hawk Sample Applications 125 | Using the TIBCO Hawk Sample Applications The TIBCO Hawk software distribution includes source code for sample applications that demonstrate the use of the TIBCO Hawk Application Management Interface (AMI). AMI is a specification of TIBCO Rendezvous messages that define the interactions that take place between a TIBCO Hawk agent and an AMI application. For UNIX. These session parameters must match the primary session parameters configured for the TIBCO Hawk agent or one of the AMI sessions configured for the TIBCO Hawk agent. Using AMI Protocol Versus the AMI APIs There are two ways to write an AMI application.

which are character strings that encode licensing information. License tickets are stored in files such as tibrv. This license only allows the AMI instrumented application to use TIBCO Rendezvous in support of the AMI communication with the TIBCO Hawk agent.126 | Chapter 9 TIBCO Hawk Sample Rulebases and Applications • • To see the list of AMI application internal names for a particular TIBCO Hawk agent. TIBCO Hawk employs an embedded TIBCO Rendezvous license that allows the TIBCO Hawk software to use the TIBCO Rendezvous solely in support of the TIBCO Hawk product. and Arguments dialog appears. The MicroAgents. To view the display name. invoke its Self:getMicroAgentInfo method. and select GetMicroAgents from the menu. Methods. A TIBCO Rendezvous license ticket is not required to run the TIBCO Hawk product with the TIBCO Rendezvous daemon (rvd). however. Any other use of TIBCO Rendezvous by the AMI application would require a valid TIBCO Rendezvous license ticket. When the sample applications are successfully executed you should see their names appear on the associated TIBCO Hawk agent. The use of TIBCO Hawk with the TIBCO Rendezvous routing daemon (rvrd). The AMI APIs allow applications to be AMI instrumented so that they use the same embedded TIBCO Rendezvous license as the TIBCO Hawk product. right-click on the desired agent in TIBCO Hawk Display.tkt (for the TIBCO Rendezvous daemon and routing daemon). TIBCO Hawk Installation and Configuration . TIBCO Rendezvous License Tickets and AMI TIBCO Rendezvous software is licensed using license tickets. still requires a valid TIBCO Rendezvous license ticket.

TIBCO. This method limits the number of dispatching threads to one thread. The users application is responsible for synchronizing access to user application data in the multi-threaded case. with the numbers 1-4 substituted for the x: TIBCO Hawk AMI C API sample x: — Filename: ami_samplex. The AMI API does all the Rendezvous work under the covers.c. The users application would be responsible for thread safety regarding any of its own data structures. If the users application is to be multi-threaded then the code in this sample would run on a dedicated thread. the users application can be single threaded. These applications are discussed in the following sections. which is also located in the sample directory. This method can be used with only a Hawk license. As a result. This is the only thread which will call the user applications AMI API callback functions.c This sample shows how to AMI instrument a Rendezvous application. The users application is free to be single or multiple threaded. TIBCO Hawk Installation and Configuration . • ami_sample1. TIBCO Hawk AMI C API Sample Applications The TIBCO Hawk AMI C API sample directory contains four sample applications. They have the following filenames and AMI application names. and Java TIBCO Hawk AMI APIs.c This sample shows how to AMI instrument a non-Rendezvous application. • ami_sample2. C++.hawk. respectively.ami_samplex The four sample applications can be built by following the instructions in the Makefile.c — Display name: ami_samplex — Internal name: COM.sample file. and java that contain sample applications for the C. cpp.ami_api. The users application creates a Rendezvous transport and queue and is responsible for dispatching that queue.The Sample AMI API Applications 127 | The Sample AMI API Applications The TIBCO Hawk AMI API sample applications can be found in the directory: $HAWK_ROOT/samples/ami_api directory This directory contains three sub-directories c.

use the following command line: ami_samplex Using Sample Applications on OS/400 The names of the TIBCO Hawk AMI C API sample programs have been truncated to fit the OS/400 name limit. and the results returned at that rate or another rate. the sample programs have the following names. Executing Sample Programs • To execute.c This sample is identical to ami_sample1. To submit a job.c This sample shows how to create an asynchronous AMI method for a synchronous data source. with the numbers 1-4 substituted for the x: ami_samplx. This sample CL program is included with the HAWKAMI library in QCSRC.c except that it demonstrates how to create methods that return tabular data. On OS/400. ami_samplex program. The sample CL program assumes the source for the sample programs is present in TIBHAWK/QCSRC. • ami_sample4. possibly calculations performed on the data across samples.c A sample CL program is provided to compile the sample programs. execute the following command: CALL TIBHAWK/AMICMP AMI_SAMPL1 You can execute the TIBCO HAWK AMI C sample programs as a job or from qsh. execute the following command: SBMJOB CMD(CALL PGM(TIBHAWK/AMI_SAMPL1)) JOBQ(QUSRNOMAX) MSGQ(*USRPRF) ALWMLTTHD(*YES) TIBCO Hawk AMI C++ API Sample Application The TIBCO Hawk AMI C++ API sample directory contains one sample application.cpp TIBCO Hawk Installation and Configuration . This technique is used when synchronous data needs to be polled at a certain rate.128 | Chapter 9 TIBCO Hawk Sample Rulebases and Applications • ami_sample3. which has the following filename and AMI application names: • AmiSample1. To compile the sample programs. for example. This technique makes use of the auto-invoke feature of the AMI C API.

java has the following AMI application names: • • Display name: Spot Internal name: COM. also located in the sample directory.sample file. Executing the Sample Program • To execute AmiSample1 program. a simple GUI application using TIBCO Hawk AMI API for Java. The sample application can be built by following the instructions in the Makefile.Spot Executing the Sample Program In order to compile and execute this sample.java: SpotAmi. the following must be in your Java CLASSPATH: TIBCO Hawk Installation and Configuration . — return data asynchronously.AmiSample1 This sample creates an AMI session to support methods that demonstrate how to: — pass data to an instrumented application. AMI Java API instrumentation for the Spot application. can be instrumented with the AMI Java API. Spot. use the following command line: AmiSample1 TIBCO Hawk AMI Java API Sample Application The TIBCO Hawk AMI Java API sample directory contains the following files: • • • AmiSample. Spot.ami_api.java.Java:a sample application designed to illustrate how to instrument a Java application using the TIBCO Hawk AMI API for Java.The Sample AMI API Applications 129 | Filename: AmiSample1. and — shutdown an application. — receive data from an instrumented application.TIBCO.TIBCO.hawk. The AMI sample spot.cpp.cpp Display name: AmiSample1 Internal name: COM.ami_api. — return tabular data.java: This sample demonstrates how an existing application.hawk.java.

To Compile the Program Samples See the TIBCO Hawk AMI C Reference and TIBCO Hawk AMI C++ Reference books for information about compiling the program samples.jar.jar and utilities. To run this pre-built version do the following: 1. Do not use any class libraries (such as MFC) in your build. TIBCO Hawk Installation and Configuration . The Spot application is executed with the following command: jre Spot -rvd_session <service> <network> <daemon> Executing the Prebuilt Sample Program A pre-built version of the Spot sample program. Run the appropriate start script in the directory: <TIBCO Hawk installation directory>/samples/scripts using the -rvd_session option: run_spot -rvd_session <service> <network> <daemon>) For example: run_spot -rvd_session 7474 123.130 | Chapter 9 TIBCO Hawk Sample Rulebases and Applications • • ami. Compile and link them using your C/C++ development environment.3.jar from the TIBCO Hawk java directory from the TIBCO Rendezvous java directory tibrvj. On the command line. Start scripts are provided in the directory <TIBCO Hawk installation directory>/samples/scripts. spot.123 tcp:7474 Using the Sample Programs Each sample program represents a separate application.jar It is recommended that you use Java 1. is supplied in the directory <TIBCO Hawk installation directory>/lib. set the following environment variables as appropriate for your environment: — — — HAWK_ROOT RV_ROOT JRE_ROOT 2.1_02 or higher. make the application a console application only.123.

page 150 Certificate Authorities.| 131 Chapter 10 Security This chapter discusses the two security models supplied with the TIBCO Hawk system. page 132 Trusted Model. page 153 TIBCO Hawk Installation and Configuration . page 144 Secure AMI Communication. refer to the TIBCO Hawk Programmer’s Guide. page 135 Certified Model. page 133 To Use the Trusted Model. For details on creating a custom security model. Topics • • • • • • Overview.

The ability to authorize a request requires two pieces of information: the identity of the user and the nature of the request. etc.g. or develop a custom security model (as explained in the TIBCO Hawk Programmer's Guide). person.132 | Chapter 10 Security Overview The TIBCO Hawk product supports a security mechanism which enables all method invocation requests made of a TIBCO Hawk agent to be verified for authenticity and integrity and then authorized (or not) based on the identity of the user making the request. The definitions of security terms used in this manual are as follows: Authentication Authentication is the practice of determining that an entity (e. Privacy Privacy is the ability to guarantee that the content of a message that is sent from one party to another is hidden from other parties. Integrity Data integrity is the ability to guarantee that the content of a message that is sent from one party to another is received just as it was sent. integrity and privacy. authentication.) is who they say they are. The system can then determine if the user has sufficient privileges for the request. process. Authorization Authorization is the practice of granting and denying privileges to users of a service or resource. You can use one of the security models provided with the TIBCO Hawk product (Trusted or Certified). TIBCO Hawk Installation and Configuration . The security implementation you choose will depend on your security requirements for authorization.

for more details. This has the benefit of being easily distributed to all nodes. The current log file is named Trusted. See below. A scan of the ASCII file for information about the user determines if the request will be granted. Authorization: the Trusted security model guarantees that only authorized users can perform restricted actions. and a new Trusted. See Access Control File.Trusted Model 133 | Trusted Model The Trusted model provides a simple yet effective mechanism for addressing authorization concerns.log. Privacy: the Trusted security model does not address the privacy of the request. Users are explicitly granted or denied access through the access control file. Integrity: the Trusted security model does not guarantee the integrity of the request.log. Authorization The Trusted model uses an ASCII file as a simple yet effective entitlement server. All requests are sent using plain text. Logging All trusted requests (both Trusted and TrustedWithDomain) can be logged to rolling log files in a directory of your choice. add the following line to the access control file: <LogService> -log_dir <logDir> -log_max_size <size> -log_max_num <n> TIBCO Hawk Installation and Configuration . To activate logging. making it a very scalable mechanism. page 135. Access control information is in a plain ASCII file located in <TIBCO Hawk installation directory>/security. When the number of logs exceeds the maximum (n). It addresses security issues as follows: • • • • Authentication: the Trusted security model does not guarantee the authenticity of the request. log entries roll over to reuse the oldest log file. it is closed and renamed Trusted1. When it reaches the maximum size (size). A user who is not in this file is not allowed to perform any operations on the TIBCO Hawk system.log is started.

Make sure this directory exists before you activate logging.txt should include the domain of the user who actually starts Hawk Display. • TIBCO Hawk Installation and Configuration . node=hawkuser-DT:none:default.microagent.hawk. microagent= COM. This is an example of an entry for an unauthorized request: Tue Dec 31 11:19:54 EST 2002: Trusted operation: userID= HAWK-TRUSTDMN\hawkuser. method= getRBMap permission denied. size The maximum size of the rolling log file in KB.txt or TrustedWithDomain.txt should not include the domain of the user who actually starts Hawk Display (or the Console API application).SysInfo.TIBCO. node=hawkuser-DT:none:default. microagent=COM. n Example Log File Entries This is an example log entry for an authorized request: Tue Dec 31 11:14:13 EST 2002: Trusted operation: userID=HAWK-TRUSTDMN\hawkuser. • To allow access to a user who starts Hawk Display (or the Console API application) in Trusted security mode.Repository.txt or TrustedWithDomain. Using both Trusted and TrustedWithDomain An agent using the Trusted or TrustedWithDomain security model allows users with either Trusted or TrustedWithDomain to access the agent. The suffix m or M can be used for indicating MB.microagent.134 | Chapter 10 Security where: Option logDir Description The directory where the log file is saved. the entry for <user> specified in the agent’s Trusted. To allow access to a user who starts Hawk Display in TrustedWithDomain security mode. the entry for <user> specified in the agent’s Trusted.hawk. The maximum number of rolling log files. method= getOperatingSystem.TIBCO.

trusted. Two sample access control files are included with TIBCO Hawk: Trusted. Modify the appropriate sample access control file. 3.txt. enter one of the following in the Security Policy Class dialog of the Windows Configuration Utility: COM. and is used when the command line specifies TrustedWithDomain. TIBCO Hawk Installation and Configuration . 4. Trusted. according to the requirements of your system.trusted. Access Control File To store access control information. Save the modified file in the directory you created.txt is for use on Windows only.security. without changing the filename.txt can be used on UNIX or Windows. the Trusted model uses an ASCII file.Trusted — On Windows.hawk. in the directory <TIBCO Hawk installation directory>/samples/security/.To Use the Trusted Model 135 | To Use the Trusted Model Two sample access control files are included with TIBCO Hawk. The access control files. Sample access control files are shipped with the TIBCO Hawk software. Trusted. Start the TIBCO Hawk agent and Display as follows: — On UNIX. To use the Trusted model: 1.txt.TIBCO.security. Create a directory called <TIBCO Hawk installation directory>/security/. TrustedWithDomain.TIBCO.hawk. 2.TrustedWithDomain The Trusted model is now in effect.TIBCO.hawk.txt or TrustedWithDomain.txt and TrustedWithDomain.Trusted or COM.txt. • • Trusted. It is used when the command line specifies Trusted.security. are described in the next section. The security policy will stay in force as long as the process is running.trusted.txt and TrustedWithDomain. The program automatically searches for the access control file in this directory. specify the following in the agent configuration file: COM.

TrustedWithDomain.trusted. microagent. See the TIBCO Hawk Administrator’s Guide for more details. or XP. The defined classes are nodes. Explicit restriction for a particular resource implicitly allows access to all other resources in the same class.security.TIBCO.hawk.txt This file can only be used with Windows 2000 or XP. • • • • Use + in node access to allow access to group operations. Use + in method access to allow access to all INFO and ACTION methods.TrustedWithDomain. The user for authorization is the login ID of the TIBCO Hawk Display owner. and methods. Access Control File Conventions The access control file uses the following conventions to grant or deny access. page 137. The defined classes are nodes. microagents. the user is <domainX>\user1. The user is the login ID and the domain where the user is logged on. for user1 in domainX. Wildcard characters + and * affect permissions on group operations and point-to-point invocations as shown in Access Control File Settings. and only when specified in the command used to start TIBCO Hawk agent and Display. and methods. Use * in method access to allow access. Group Operations A group operation effectively performs a method invocation simultaneously on all of the specified target microagents. It is useful for affecting a group of microagents in a single operation. as in -security_policy COM.136 | Chapter 10 Security Trusted. provided they have been explicitly granted. • Explicit access for a particular resource implicitly denies access to all other resources in the same class. There are two kinds of group operation: network query and network action. Use * in node access to allow access to point-to-point invocations. For example.txt This access control file can be used with UNIX or with Windows 2000. • • TIBCO Hawk Installation and Configuration . Permissions always default to the most restrictive case.

<user> <node> <user> * <user> + !<user> User <user> Node Microagent Method TIBCO Hawk Installation and Configuration . page 140. Node Access: All Nodes Grants point-to-point invocation access to all methods on all microagents. Individual node. For example. you can give a user access to all methods on a node in one line. Each individual setting is represented by one line in the access control file. restrict that user’s access to one of those methods.txt and TrustedWithDomain File Examples. Table 20 Access Control File Settings Effect Full Access Grants full access to all methods on all microagents on all nodes. You can add several lines for one user to provide access to a set of nodes. See Trusted.To Use the Trusted Model 137 | File Settings for the Trusted Model This table presents how individual restrictions and permissions are defined for nodes. Node Access: Named node Grants invocation access to all methods on all microagents on the named node. including group operations Node Access: All Nodes Grants point-to-point and group operation invocation access to all methods on all microagents. Complex permissions and restrictions can be defined using sets of related lines. and method names can be specified. Full Restriction Denies access to all methods on all microagents on all nodes. as shown in the table. for further details. microagent. In addition. Permissions are granted to a user using the user name. microagents. and methods. Restrictions are defined by prefixing a bang (!) character to the user name. including group operations. wildcard characters can be used as shown in the table. Does not grant group operation invocation access. then in the following line.

See Node Restriction above. Wildcard characters can be used in the Node and Microagent columns. Wildcard characters can be used in place of a specific node name. Microagent Restriction Denies access to all methods on the specified microagent. Microagent Access Grants access to all methods on the specified microagent. <user> <node> <microagent> + !<user> <node> <microagent> <user> <node> <microagent> !<user> <node> !<user> + User !<user> Node * Microagent Method TIBCO Hawk Installation and Configuration . (Does not deny point-to-point operation invocations.138 | Chapter 10 Security Table 20 Access Control File Settings (Cont’d) Effect (Cont’d) Node Restriction: All Nodes Denies point-to-point and group operation invocation access to all methods on all microagents. You can add several lines for one user to provide access to a set of nodes. See Node Access above.) Node Restriction: Named node Denies invocation access to all methods on all microagents on the named node. Wildcard characters can be used in the Node columns. Method Access Grants access to all ACTION and INFO methods on the specified microagent (but not ACTIONINFO methods). Node Restriction: All Nodes Denies group operation invocation access to all methods on all microagents.

Wildcard characters can be used in the Node and Microagent columns. Method Restriction Denies access to all ACTION and ACTION_INFO methods on the specified microagent. Wildcard characters can be used in the Node and Microagent columns. !<user> <node> <microagent> <method> !<user> <node> <microagent> + !<user> <node> <microagent> * <user> <node> <microagent> <method> User <user> Node <node> Microagent <microagent> Method * TIBCO Hawk Installation and Configuration . Method Restriction Denies access to the specified method on the specified microagent. Method Access Grants access to the specified method on the specified microagent. Wildcard characters can be used in the Node and Microagent columns.To Use the Trusted Model 139 | Table 20 Access Control File Settings (Cont’d) Effect (Cont’d) Method Access Grants access to all INFO methods on the specified microagent (but not ACTION or ACTIONINFO methods). Method Restriction Denies access to all methods on the specified microagent. Wildcard characters can be used in the Node and Microagent columns. Wildcard characters can be used in the Node and Microagent columns.

• • Grant user4 full access to all methods on all microagents on nodeB. Trusted.TIBCO.hawk. The permissions and restrictions defined in this file are explained in the previous section. EXCEPT . . Explanation of Settings The settings in the example files below provide access to the following users as shown here: • Grant user1 point-to-point access to all methods on all microagents. — The specified methods on the RuleBaseEngine microagent on nodeA. except: — group operation invocation access to all ACTION methods on the RuleBase microagent.trusted.the specified methods on the RuleBaseEngine microagent on "nodeA". except: — All ACTION methods on the Custom microagent on all nodes.the specified methods on the Repository microagent on all nodes.security. — All ACTION methods on the RuleBase microagent on all nodes.txt access control file might be constructed.txt Example File # # # # # # # # # # # This file is used by agent running with COM.Trusted security model. — The specified methods on the Repository microagent on all nodes. .all ACTION methods on the Custom microagent on all nodes. except: — All ACTION methods on the Custom microagent on all nodes. • Grant user3 point-to-point and group operation invocation access to all methods on all microagents on all nodes.140 | Chapter 10 Security Trusted. TIBCO Hawk Installation and Configuration . Grant user5 point-to-point access to all INFO methods on all microagents on all nodes. • Grant user2 point-to-point and group operation invocation access to all methods on all microagents. Explanation of Settings: Grant "user1" point-to-point access to all methods on all Microagents. — All ACTION methods on the Repository microagent on all nodes.txt and TrustedWithDomain.txt and TrustedWithDomain File Examples The following example files demonstrates how a Trusted.

# .TIBCO.microagent.microagent.hawk.Repository COM.Custom + !user1 * COM.To Use the Trusted Model 141 | # # Grant "user2" point-to-point and network access to all methods on all # Microagents. # # Grant "user4" full access to all methods on all microagents on nodeB.network access to all ACTION methods on the RuleBase microagent.hawk. EXCEPT # .TIBCO.Repository setRBMap !user1 nodeA COM.microagent.Repository addRuleBase !user1 * COM.microagent.TIBCO.TIBCO.microagent.Use * in node access for allowing access to point-to-point invocations.TIBCO.hawk.RuleBaseEngine + TIBCO Hawk Installation and Configuration .TIBCO.hawk.TIBCO.RuleBaseEngine setSchedules !user1 nodeA COM.Custom COM.TIBCO.Repository deleteRuleBase !user1 * COM.TIBCO.TIBCO.TIBCO. # # # Wildcard characters + and * usage: # # .microagent.hawk.hawk.RuleBaseEngine deleteRuleBase !user1 nodeA COM.RuleBaseEngine updateRuleBase !user1 nodeA COM.hawk.hawk.microagent. # .TIBCO.RuleBaseEngine loadRuleBaseFromFile !user1 nodeA COM.hawk. EXCEPT # .microagent.microagent.hawk.hawk.hawk.all ACTION methods on the RuleBase microagent on all nodes. # .microagent.microagent.hawk.Repository updateRuleBase !user1 * COM.Repository setSchedules !user1 * COM.hawk.microagent. # # Grant "user5" point-to-point access to all INFO methods on all microagents # on all nodes.microagent.RuleBaseEngine addRuleBase !user1 nodeA COM.microagent.RuleBaseEngine + + + + + nodeB COM.TIBCO.Use + in node access for allowing access to group operations.microagent.all ACTION methods on the Custom microagent on all nodes.RuleBaseEngine setRBMap user2 !user2 !user2 !user2 user3 !user3 user4 + * * * * COM. # # Grant "user3" point-to-point and network access to all methods on all # Microagents on all nodes.TIBCO.microagent.TIBCO.hawk. # # # File format: # # user node microagent method # access access access # & & & # restrictions restrictions restrictions # user1 * !user1 * COM.RuleBaseEngine unloadRuleBase !user1 nodeA COM.hawk.microagent.microagent.Use + in method access for allowing access to all INFO and ACTION methods.hawk.TIBCO.Use * in method access for allowing access to all INFO methods only. # .TIBCO.all ACTION methods on the Repository microagent on all nodes.hawk.TIBCO.RuleBaseEngine loadRuleBase !user1 nodeA COM. # .

security. the domain should not be # included in the user.Trusted security model # to access this agent.TIBCO. for user1 in domainX. the user # specified should include the domain of the user. #.TrustedWithDomain security model. # A suffix m or M can be used for indicating MB .security.hawk.trusted. # # To allow a user running with COM. # n is the maximum number of rotating log files. # . #.all ACTION methods on the Custom microagent on all nodes.network access to all ACTION methods on the RuleBase microagent.trusted.TIBCO. EXCEPT #. EXCEPT #.trusted. # For example.all ACTION methods on the Repository microagent on all nodes. EXCEPT #. # . # # Grant "user5" point-to-point access to all INFO methods on all microagents # on all nodes. TrustedWithDomain. # # Grant "user4" full access to all methods on all microagents on nodeB. # # TIBCO Hawk Installation and Configuration . # # # Explanation of Settings: # # Grant "user1" point-to-point access to all methods on all Microagents. # # Grant "user3" point-to-point and network access to all methods on all # Microagents on all nodes. uncomment the following: # <LogService> -log_dir logDir -log_max_size size -log_max_num n # # where: logDir is the directory where the log file will be stored # size is the maximum size of a rotating log file in KB. # # Note that agents using the TrustedWithDomain security model also allow # users running with COM.the specified methods on the Repository microagent on all nodes.hawk.all ACTION methods on the Custom microagent on all nodes.security.142 | Chapter 10 user5 Security * * * # # To activate logging.hawk.all ACTION methods on the RuleBase microagent on all nodes.the specified methods on the RuleBaseEngine microagent on "nodeA".TIBCO.txt Example File # # This file is used by agent running with # COM. the user should be specified as # "domainX\user1". For these users. # # Grant "user2" point-to-point and network access to all methods on all # Microagents.TrustedWithDomain # security model on Windows platform to access this agent.

TIBCO.Use + in method access for allowing access to all INFO and ACTION methods.hawk.microagent.microagent.Custom + !user1 * COM.Repository updateRuleBase !user1 * COM. TIBCO Hawk Installation and Configuration .hawk.TIBCO.hawk.hawk.Use * in node access for allowing access to point-to-point invocations.RuleBaseEngine loadRuleBase !user1 nodeA COM.hawk.Repository COM.RuleBaseEngine updateRuleBase !user1 nodeA COM.Repository addRuleBase !user1 * COM. # .hawk.To Use the Trusted Model 143 | # Wildcard characters + and * usage: # # .TIBCO.TIBCO.RuleBaseEngine + * * # # To activate logging.microagent. uncomment the following: # <LogService> -log_dir logDir -log_max_size size -log_max_num n # # where: logDir is the directory where the log file will be stored # size is the maximum size of a rotating log file in KB.microagent.microagent.TIBCO.TIBCO.RuleBaseEngine + + + + + nodeB * COM.TIBCO.hawk.TIBCO.Use + in node access for allowing access to group operations.TIBCO.microagent.microagent.hawk.TIBCO.TIBCO.microagent.microagent.TIBCO.hawk.hawk.Custom COM.microagent.RuleBaseEngine deleteRuleBase !user1 nodeA COM.microagent. # .RuleBaseEngine setSchedules !user1 nodeA COM.microagent.Repository setSchedules !user1 * COM.TIBCO.RuleBaseEngine loadRuleBaseFromFile !user1 nodeA COM. # # # File format: # # user node microagent method # access access access # & & & # restrictions restrictions restrictions # user1 * !user1 * COM. # n is the maximum number of rotating log files.hawk.RuleBaseEngine unloadRuleBase !user1 nodeA COM.TIBCO.microagent.microagent. # .microagent.TIBCO.TIBCO.Use * in method access for allowing access to all INFO methods only.hawk.hawk.Repository setRBMap !user1 nodeA COM.microagent.RuleBaseEngine setRBMap user2 !user2 !user2 !user2 user3 !user3 user4 user5 + * * * * COM.TIBCO.Repository deleteRuleBase !user1 * COM.hawk.hawk.microagent.hawk. # A suffix m or M can be used for indicating MB .hawk.RuleBaseEngine addRuleBase !user1 nodeA COM.TIBCO.hawk.microagent.

available at www.txt file is not allowed to perform any operations on the TIBCO Hawk system.txt properties file must be formatted according to specifications for J2SE 1. enables the holder of the corresponding certificate to verify the integrity of the message. which then functions as the entitlement server.javasoft. The Certified. Authentication Authentication can be done via shared secret (e. Entitlements are handled by configuring the rvacld daemon. TIBCO Hawk Installation and Configuration .3/docs/api/java/util/Properties. Integrity Digital signature techniques can be used to apply a one-way hash algorithm on the message and encrypt the hash value using a private key.txt properties file to store information about the TIBCO Rendezvous Access Control Daemon (rvacld) and Hawk users and agents. A user or agent that is not specified in the rvacld configuration referred to in the Certified. The use of the one-way hash algorithm is a powerful tool for determining if a document has been tampered with.html. known as signing. The Certified model uses the decryption capability provided by TIBCO Rendezvous DataSecurity to decrypt a file on disk containing the private key of the principal after prompting the user for a password. The sender will use the certificate that accompanied the message to calculate the one-way hash value.g.4 and above.144 | Chapter 10 Security Certified Model The certified model provides a high degree of security for the TIBCO Hawk system. Authorization The Certified model uses the Certified.. password) or via certificates and digital signatures. This process. Certificates The Certified model can use either login/password authentication (default) or certificates with corresponding private keys for each user of the TIBCO Hawk system. Comparing with the signature can verify the integrity of all messages.com/j2se/1. It then uses the certificate that was sent along with the message to verify the signature and identify the sender enabling a decision to be reached regarding the processing of the request.

The procedure for importing an external root certificate and a list of Certificate Authorities trusted by the TIBCO Hawk software are provided in the section Certificate Authorities. Otherwise. The system will look for this file in the user’s system and use it as the user’s certificate. and the user will be prompted. It is also possible for you to act as a trusted Certificate Authority by importing an external root certificate. page 153.jar to your CLASSPATH.0 or higher for addressing authentication and integrity concerns. As part of DataSecurity installation. in a file called username. There are several well-known third party Certificate Authorities from which you can choose. It is your responsibility to obtain and install the Rendezvous DataSecurity package prior to using the Certified security model. managing. TIBCO Hawk Installation and Configuration . you will be prompted to add tibrvdsj. the system will assume that the user is authenticated by password only.Certified Model 145 | The encrypted certificate and private key must be in a X509 encoded PEM formatted file in a directory called . maintaining. TIBCO Rendezvous DataSecurity The Certificate model employs TIBCO Rendezvous DataSecurity Version 2. and distributing certificates and private keys.hawk in the home directory of the owner of the TIBCO Hawk Display process.key. It is important that you perform a complete and successful installation of the DataSecurity software before attempting to use the product with TIBCO Hawk. Note: You are responsible for obtaining.

Figure 12 Certified Model Architecture TIBCO Hawk Agent AMI Application Rendezvous DataSecurity CA Root Certificate Encrypted Certificate File TIBCO Rendezvous DataSecurity RVDS Key Holder RVDS Context Embedded Certificate TIBCO Rendezvous Transport Access control To set access control using the Certified model you must first ensure that you have a valid Certified.passwd = somepassword TIBCO Hawk Installation and Configuration .txt properties file must contain the following information: • • • • certificates and/or passwords. or pointers to files containing the same rvacld parameters indicating the rv service.key. daemon.txt properties file. for the password: agent. and acld certification the Hawk agent the user(s) Passwords and/or certificates may be included directly in the file. or may be put in a separate file.146 | Chapter 10 Security Architecture The architecture supporting the certified model is shown in Figure 12. network. then configure the rvacld.txt file The Certified.. as follows. Creating the Certified.

key.pem Include information about the rvacld parameters as in the following sample: rv. Configuring access control in rvacld for the Certificate Model To configure the rvacld..name = HawkACL #acld. If the console cannot prompt the user (for example.pem agent.pass.. then the ~/.key. then it is searched for a file named username.key.daemon =<rvdeamonname> acld.hawk directory is checked for a file named username.key = -----BEGIN CERTIFICATE-----\n \ #<certificate PEM text> #(see Certificates. and this is used as the user's certificate. and he/she is prompted for this. if the security code is being used in DAEMON mode)..key = . If absent.user = hawkAgent Specify the certificate that identified the agent: #agent.passwd = somepassword Or.cert if used> Include information about the agent as follows: The agent's user name: agent. agent..network =<networkname> rv.file = agent. the default value of anonymous is used.service =<servicename> rv.<certificate text. acld.key. Otherwise it is assumed that the user is identified by a password only.cert. if the agent is only identified by a password.or agent.Certified Model 147 | . If the user has a directory named .file = agent.key. each user has to be identified.passwd = apassword #agent. you will need to perform the following tasks: TIBCO Hawk Installation and Configuration . comment out the agent.pass In addition to the above.file = acld.* lines and use on of these: #agent.name.passwd. The username is taken from the system property named user.file = mypasswordfile and for the certificate: agent. page 175) -or#agent.hawk in their home directory.file = agent. and the content of this file is used as the user's password.. but that doesn't happen here.cert = ..passwd.key.

Repository Creating Users Create a user entry in the rvacld for each Hawk user that will be permissioned.microagent.ACTION_INFO. page 145. the Repository microagent would require the following tags: hawk. So for instance. page 144. page 153.Repository hawk.hawk. which you must create.) Assign user permissions Each user that can perform an action should be given "rw" permission on the corresponding tag. TIBCO Hawk Installation and Configuration . Install TIBCO Rendezvous DataSecurity software.<type>. Create a user for each agent. See Certificates. Assign agent permissions Each agent that can receive an action should be given "r" permission on the corresponding tag.ACTION.txt. See TIBCO Rendezvous DataSecurity. To Use the Certified Model In order to use the Certified model.TIBCO.COM.INFO. and place it in the <TIBCO Hawk installation directory>/security/ directory. and Certificate Authorities. or set of agents that will be controlled.hawk.Repository hawk.148 | Chapter 10 Security • • • • create tag names create users and agent-users assign user permissions assign agent permissions Creating tag names Each microagent that will be invoked needs a corresponding set of tags with names of the following form "hawk.COM. The TIBCO RVDS manuals give information about how to create users. or assign a different "user" for each agent. certified.microagent.TIBCO. (You can have all of your agents log in as the same "user" if you want.TIBCO.COM. Define the properties file. you must first do the following: • • • Obtain the required certificates.hawk.microagent. for details. and give them certificates if desired.<microagent name>".

enter the following in the Security Policy Class dialog of the Windows Configuration Utility: COM.TIBCO. Once the access control file has been configured.security.certified.certified. specify the following in the agent configuration file: -security_policy COM. you use the Certified model by starting the TIBCO Hawk agent and Display as follows: • • On UNIX.security. Note that you must create this directory manually. TIBCO Hawk Installation and Configuration . The security policy will stay in force as long as the process is running.Certified The program will automatically search for the access control file in the <TIBCO Hawk installation directory>/security directory.Certified Model 149 | • Configure the acld daemon.Certified On Windows.hawk.hawk.TIBCO.

The procedure for importing an external root certificate and a list of Certificate Authorities trusted by the TIBCO Hawk software are provided in the section Certificate Authorities. This permits a single TIBCO Hawk agent and HMA to be shipped regardless of security concerns. TIBCO Hawk Installation and Configuration . page 153. The TIBCO Hawk agent and HMA support an option to specify the use of TIBCO Rendezvous DataSecurity for communicating with AMI applications (-ami_rvds_session). It is necessary for the TIBCO Hawk agent. even messages that are signed but NOT encrypted. and AMI applications to distinguish between secure and non-secure communication because TIBCO Rendezvous DataSecurity requires decryption of all messages. There are several well-known third party Certificate Authorities from which you can choose. managing.150 | Chapter 10 Security Secure AMI Communication The TIBCO Hawk agent supports secure AMI communication using TIBCO Rendezvous DataSecurity. The architecture supporting secure AMI communication is shown in Figure 13. It is also possible for you to act as a trusted Certificate Authority by importing an external root certificate. Figure 13 AMI Communication Architecture TIBCO Hawk Display TIBCO Hawk Agent Certificate agent Encrypted Certificate File Certificate console Trusted Users File RVDS Key Holder CA Root Certificate RVDS Context Embedded Certificate TIBCO Rendezvous Transport You are responsible for obtaining. maintaining. This enables the AMI applications to verify the authenticity and integrity of all requests. HMA. and distributing certificates and private keys.

Since the private key used to pack AMI messages is provided to the TIBCO Hawk agent at run-time. Use the following parameters: TIBCO Hawk Installation and Configuration .exe. in the -rvd_session parameter. The TIBCO Hawk agent will pack all AMI messages using the private key. AMI applications will be required to specify localhost as part of the TIBCO Rendezvous daemon parameter in order to prevent remote connections to its rvd daemon. specify the following: tcp:127. The procedure is similar to that given in Setting Up Network Communication in Windows. Running with a localhost rvd As a further precaution.0. Modify hawkagent. it is also necessary to provide the corresponding certificate to any AMI applications wishing to perform authorization.cfg and hawkhma. page 118.ami. This contains the password needed by the TIBCO Rendezvous DataSecurity decryption facility to decrypt the file on disk containing the certificate and private key. for details. Applications should look in the following location: <TIBCO Hawk installation directory>/security/ certificate.1:<daemon> 2.exe to install a localhost rvd as a Windows service.1:<daemon> Windows Procedure Use rvntsreg. An AMI application will use the certificate that accompanies the message to verify the authenticity and integrity of the message.0. See that section for a fuller description. The TIBCO Hawk agent will look for the following file: <TIBCO Hawk installation directory>/security/ password. Instructions to do this for UNIX and Windows platforms are given below.ami.cfg and.Secure AMI Communication 151 | The TIBCO Hawk agent supports a mechanism by which the TIBCO Hawk administrator can import a certificate and private key for use by TIBCO Rendezvous DataSecurity for AMI communication. page 118. Create an rvd service using rvntsreg.0. Only requests that have been signed using the private key associated with this certificate will be considered authorized. See Installing a Routing Daemon as a Windows Service. UNIX Procedure 1. 1.0.ami. The encrypted certificate and private key must be in a X509 encoded DER formatted file in the following location: <TIBCO Hawk installation directory>/security/certificate. as follows: rvd -listen tcp:127. Add a command to start the localhost rvd prior to starting any TIBCO Hawk processes.

modify the daemon parameter to the following: tcp:127. for details. page 118.152 | Chapter 10 Security -listen tcp:127.0.0.0.1:<daemon> 2. In the Configuration Utility. See Making TIBCO Hawk Services Depend on the Routing Daemon Windows Service.1:<daemon> TIBCO Hawk Installation and Configuration .0. 3. Make all TIBCO Hawk services dependent upon this new rvd service.

Certificate Authorities 153 | Certificate Authorities Certificates issued by the third-party Certificate Authorities listed below are trusted by the TIBCO Hawk agent and the Certified security model. in a file with the suffix . • • • • • • • • • • • • • • • GTECyberTrustGlobalRoot GTECyberTrustRoot KeyWitnessGlobal2048Root MicrosoftRootAuthority MicrosoftRootSGCAuthority ThawtePersonalBasicCA ThawtePersonalFreemailCA ThawtePersonalPremiumCA ThawtePremiumServerCA ThawteServerCA ThawteTimestampingCA VeriSignClass1PrimaryCA20180518 VeriSignClass1PrimaryCA20200107 VeriSignClass2PrimaryCA20040107 VeriSignClass2PrimaryCA20180518 TIBCO Hawk Installation and Configuration .root. as explained next. Third-Party Certificate Authorities The list below gives sources for User certificates that are trusted by the Certified model. To import an external Root certificate. Once the Root certificate is imported by the model. or if you want to act as your own certificate authority. You can also use an external Root certificate. it will trust the certificate authority associated with the certificate. place the certificate in the <TIBCO Hawk installation directory>/security directory. then you must provide them appropriate Root certificate for import into the model. Importing an External Root Certificate If you wish to obtain User certificates from a third-party not on the list below.

154 | Chapter 10 Security • • • • • • VeriSignClass3PrimaryCA20040107 VeriSignClass3PrimaryCA20180518 VeriSignClass4PrimaryCA VeriSignCommercialSoftwarePublishersCA20040107 VeriSignIndividualSoftwarePublishersCA20040107 VeriSignTimeStampingCA TIBCO Hawk Installation and Configuration .

page 157 TIBCO Hawk Installation and Configuration . page 157 Converting Commands from Previous Releases. page 156 Using the Scheduler. page 156 Migrating Rulebase Map from Previous JRE Environments. page 156 Using 3. page 156 Changing the Codepage Setting.x and 4.| 155 Appendix A Migration This appendix discusses issues related to migration. Topics • • • • • • Re-Linking C and C++ Applications to Libraries.x Agents Together.

2.x and 4. Re-Linking C and C++ Applications to Libraries The AMI C and C++ libraries were renamed to eliminate a naming conflict with OS libraries. Changing the Codepage Setting (Windows only) The TIBCO Hawk installation program automatically retains your previous configuration. all AMI C or C++ applications must be re-linked against the renamed libraries. UTF-8 is now the default for all TIBCO Hawk components. If the previous version of TIBCO Hawk specified a codepage setting for the HMA other than 65001 (Windows identifier for UTF-8). if you load the same rulebase on each agent.x Agents Together You can include TIBCO Hawk 4.x and 3.x Agents in the same environment. However. TIBCO Hawk Installation and Configuration . the OS name returned is ’Solaris’ and is ’SunOS’ when using JRE 1.156 | Appendix A Migration Migration Issues The following considerations apply when migrating from a previous version of TIBCO Hawk. you will need to manually change the codepage setting to 65001 after installing this version. Migrating Rulebase Map from Previous JRE Environments The OS name returned by the SysInfo::getOperatingSystem() depends on the version of JRE being used. After installing TIBCO Hawk. any rulebase intended for all Solaris machines should be added to both the ++Solaris group and the ++SunOS group in the map. TIBCO Hawk Display will show the rulebases as being different versions.2. This can become a problem when using rulebase maps in a mixed environment of both JRE 1.2.1.1 and 1. Therefore. Using 3. When using JRE 1.

1 schedules that are send to a 4. • • If an agent command in a previous release has Append Agent Name checked. the variable ${Internal. • TIBCO Hawk Installation and Configuration .0. as were used in 4. If an agent command in a previous release has Append Agent IP Address checked.0.0 will automatically be converted when executed using the current release. Agent IP Address} will be appended to the command. Likewise.Agent Name} will be appended to the command. TIBCO Hawk 4.x. the variable ${Internal.x agents using schedules that are sent to 4. Converting Commands from Previous Releases Commands created prior to the TIBCO Hawk 4.Migration Issues 157 | Using the Scheduler The Scheduler in TIBCO Hawk 4.1 will be converted to minutes instead of the 15-minute interval. TIBCO Hawk 4.x agent will have the minute converted to the nearest 15-minute interval.0.1.1 uses 1-minute intervals instead of 15-minute intervals.

158 | Appendix A Migration TIBCO Hawk Installation and Configuration .

page 160 Windows Errors. Topics • • • UNIX Errors. page 163 TIBCO Hawk Installation and Configuration . page 162 General Errors.| 159 Appendix B Troubleshooting This appendix presents some common problems and error conditions encountered during TIBCO Hawk installation and describes how to resolve them.

If the environment variable is not set..0 # C-shell setenv DISPLAY <ip_address>:0.............. So you decide to telnet to itaska from alaska.. Before doing so.... consider a scenario where you install TIBCO Hawk on a remote HP-UX machine (named itaska).2...... generally for graphics.... .. alaska> xhost + # give permission for all to its share monitor alaska> telnet itaska Welcome to HPUX itaska 11... which can be :0. you can run an X-window application on it. The DISPLAY variable must be set to the IP address or name of the computer (on which the installer graphics window are to be displayed)..160 | Appendix B Troubleshooting UNIX Errors This section lists possible installation errors on UNIX along with solutions............. For example: # Bourne shell DISPLAY=<ip_address>:0.... It uses the DISPLAY environment variable to tell it on which computer to open the window. That is why you must set the DISPLAY variable.. which instructs the X-server to redirect all windows to the computer set in the variable. the computer (specified in the DISPLAY variable) must give permissions to share its monitor.0... export DISPLAY # Korn shell export DISPLAY=<ip_address>:0....1_s4_56... .. Because you have a Solaris machine (named alaska) with a video card and monitor. Preparing Java(tm) Virtual Machine....0.bin TIBCO Hawk Installation and Configuration .. DISPLAY Variable Error (Only when installing in a GUI environment) The installer on UNIX must open an additional window.....0 For example. followed by a screen address. the installer will either wait or abort after displaying the following message: InstallShield Wizard Initializing InstallShield Wizard... you will not get access to itaska's monitor and will be unable to display an X-window application..... .....00 User: Password: itaska> export DISPLAY=alaska:0..... When you telnet to itaska...0 # set display on alaska itaska> TIB_hawk-simple_4..

0. file softobj.c. you may get the following error: Assertion failed: so->so_hard_contents. It does not happen on an HP-UX 11. SIGABRT Error (AIX 4. Pid nnn was killed due to failure in writing the signal context.11 (or 11. This happens after the Finish button is clicked at the end of installation or if the installation is aborted. the TIBCO Hawk installer may produce the following error message and create a core file. Assertion Failed Error (HP-UX Only) When installing as root user on HP-UX. OK. To avoid getting this error message during installation.. Writing stack trace to .a. The installation however. line 363 If this happens.0.00 64 bit systems. reinstall TIBCO Hawk as non-root user. SIGABRT received at d0103df4 in /usr/lib/libpthreads.UNIX Errors 161 | PID Error (HP-UX 11.4 xlC libraries as indicated by APAR IY14529 and proceed with the installation. completes successfully.00 64 bit system may crash with the following error message: Pid nnn killed due to trashed stack.00 32 bit system or an HP-UX 11.3 Only) On the AIX 4. Installation on a HP-UX 11. apply 5.3 system.i) system.00 64 bit Platform Only) The following error can occur only on HP-UX 11. install HP-UX kernel patch PHKL_27282 and then install TIBCO Hawk.. TIBCO Hawk Installation and Configuration . If this error occurs.

you must reinstall Hawk with a shorter installation path. a command line has a limit of 1024 characters. Packet Fragmentation Errors with Multicast You may encounter packet fragmentation errors when using multicast on Windows XP or Windows 2000. Information about obtaining the fix is in Microsoft Knowledge Base Article Q319627. The startup command for TIBCO Hawk (which includes the installation path and a large number of required jar files) may be longer than 1024 characters if TIBCO Hawk was installed into a directory with a long installation pathname. Error 401 In this case. the following error message appears when you try to start TIBCO Hawk: String variable is not large enough for string. This is due to a known issue in Microsoft Windows. If the startup command is too long. Check the string declarations. TIBCO Hawk Installation and Configuration .162 | Appendix B Troubleshooting Windows Errors This section lists possible installation errors on Windows along with solutions. You may need to apply a Microsoft hot fix (this fix is not included in Windows 2000 SP3). String Variable Error In Windows.

TIBCO Hawk Installation and Configuration . Error code is 1057 Event Service Failed to Install. uninstall the TIBCO Hawk software. select Start>Programs>TIBCO Hawk Software>UnInstall. This is usually caused by missing files in the CLASSPATH. No Administrator Privilege During TIBCO Hawk installation on Windows. you will not be able to change the account used to start the services (the services will not appear in the list of services in your Services control panel).You must have administrator privilege to install Hawk Services. TIBCO Hawk Service Failed to Install (Error 1057) Either form of the following error message can be generated by the Windows Service Manager: Hawk agent service failed to install. To resolve the situation.General Errors 163 | General Errors This section lists installation errors that can occur on both UNIX and Windows.jar in your CLASSPATH. Status is 1057 This means that the user account specified for starting the TIBCO Hawk services does not have sufficient privileges to start the services. Because this error occurs during installation. Cannot Initialize Display TIBCO Hawk Display stops after the Initializing subscriptions screen and displays the message Unable to Initialize TIBCO Hawk Display. then install the software again giving a valid account.jar Specify only tibrvj. You need to log back into the machine as a user with local administrator privileges to correctly install TIBCO Hawk software. if you encounter the following message: Severe . To uninstall the software. Check your CLASSPATH environment variable and make sure it includes the file: <TIBCO Rendezvous installation directory>/lib/tibrvj.

• See Installing on Microsoft Windows. TIBCO Hawk Services Fail to Start After Installation After you have completed TIBCO Hawk installation on Windows." This error indicates one of the following situations: • • • An invalid account was specified.164 | Appendix B Troubleshooting Installation Problems (Error 1073) If you encounter any of the following messages.. (After each new installation or re-installation of TIBCO Rendezvous or TIBCO Hawk software on Windows. you must reboot the machine before using the software. use the Event Viewer to check for error messages related to the TIBCO Hawk services in the Application Log. for more information on these settings. Make sure the account has the correct privileges. make sure that TIBCO Rendezvous is correctly installed. The wrong password was given for the account on which the TIBCO Hawk services are being run. TIBCO Hawk Installation and Configuration . If any messages contain the text ". could not be spawned". you need to re-install TIBCO Hawk: • • • HMA Service failed to install.. The account on which the TIBCO Hawk services are being run does not have "Log on as a service" privileges.. Error code is 1073 Error code is 1073 Hawk Agent Service failed to install. Status is 1073 Service Not Started (Error 1069) The system displays the following message: Could not start the TIBCO Hawk service . if none of the TIBCO Hawk services will start. Event Service failed to install. and that you rebooted the machine after both the TIBCO Rendezvous and TIBCO Hawk installations.) Internal Error 2140 The system displays the following message: Error 2140: An internal Windows error occurred. The account on which the TIBCO Hawk services are being run does not have administrative privileges. page 11. Error 1069: The service did not start due to a logon failure..

Change the text in the edit box labeled Value. Choose Start>Settings>Control Panel. Select the variable in the System Variables list. In System Variables. If this corrects the error. If you have checked all of these possibilities. You can also determine your CLASSPATH and PATH settings by opening a DOS command-line window and typing echo %CLASSPATH% or echo %PATH%. after the TIBCO Rendezvous file. Reboot and try the services again. before contacting TIBCO Hawk technical support. 2. check that your CLASSPATH variable includes the file <TIBCO Rendezvous installation directory>\lib\tibrvj. To view and change environment variables: 1. 3. after checking these variables. 3. TIBCO Hawk Installation and Configuration . is set incorrectly. you still get the error. To change an environment variable: 1. double-click the System icon. try removing all other files from your CLASSPATH. Usually this is because one of two environment variables. and click the Environment tab. re-add other files to the CLASSPATH one at a time. If. verify that the Windows Service Pack 4 was reinstalled after any recent major changes were made. Because TIBCO Hawk is a Windows service. 2. so that it includes only the tibrvj. In System Variables. to make sure none are omitted on re-installation). check that your PATH environment variable includes the directory <TIBCO Rendezvous installation directory>\bin.jar.General Errors 165 | This message probably means the services cannot find crucial TIBCO Rendezvous files. all changes made to the environment and registry require that the Windows machine be rebooted for the changes to propagate to the Windows Service. Click Set. CLASSPATH or PATH.jar file (writing down the names of the removed files is recommended. and you still get Error 2140.

166 | Appendix B Troubleshooting TIBCO Hawk Installation and Configuration .

| 167 Appendix C TIBCO Hawk Directories and Files This appendix lists the files installed with TIBCO Hawk on Windows and UNIX platforms. page 168 TIBCO Hawk Installation and Configuration . Topics • TIBCO Hawk Directory Structure.

Linux. and files are placed in it only when the event service is started. .hrb autoconfig bin hawkagent. and OS/400 tibhawkhma startagent startdisplay startevent starthma TIBCO Hawk Installation and Configuration .txt <platform>.168 | Appendix C TIBCO Hawk Directories and Files TIBCO Hawk Directory Structure Table 21 explains the directory structure and general placement of files in the TIBCO Hawk software installation subdirectories.cfg hawkhma. Table 21 TIBCO Hawk Files and Directories Directory <TIBCO Hawk installation directory> Description The directory in which TIBCO Hawk software is installed. Used to store rulebase files that will be loaded by the TIBCO Hawk agent automatically at startup.cfg hawkdisplay.txt license.cfg Additional files for UNIX. The data directory is created only if the TIBCO Hawk event service is installed. Contains TIBCO Hawk executable files and starting scripts.cfg hawkevent. Contents readme.

Contains TIBCO Hawk event service data files. TIBCO Hawk Installation and Configuration .exe HawkRandomAccessFile.dat .dll tibhawkmsg.dat Event1.dll tibhawkconfig.dll config Used to store rulebase files if using manual rulebase configuration.exe tibhawkhma. TibRendezvous.TIBCO Hawk Directory Structure 169 | Table 21 TIBCO Hawk Files and Directories (Cont’d) Directory bin Cont’d Description Contents Additional files for Windows EventLogClass.exe tibhawkagentnt.dll tibhawkregistry.exe tibhawkeventnt.dll tibhawkservice.dll Uninst. .dll killproc. .dll psapi.hrb data Event. Files are placed in this directory only when the event service is started.dll HawkTrustedUserID.dll pdh.exe mfc42.exe tibhawkdisplay.dll tibhawkami.

jar crimson.h AmiSession.h AmiParameterListIn.jar TIBCO Hawk Installation and Configuration .h AmiSyncMethod.h AmiParameterListOut.jar mail.jar workbench.jar security.h AmiStatus.h AmiParameterIn.h AmiList.jar console. activation.h AmiParameter.jar utilities.jar ami.jar config.jar rvutils.jar jkitgo.h lib Contains TIBCO Hawk Java class.jar display.jar files.h AmiParameterList.jar talon.jar jcchart.jar perltools.h AmiParameterOut.jar publisher.h AmiSubscription.jar util.jar agent.h amicpp.jar event.170 | Appendix C TIBCO Hawk Directories and Files Table 21 TIBCO Hawk Files and Directories (Cont’d) Directory include Description Contains all header files required for sample programs Contents ami.h AmiMethod.jar spot.h AmiAsyncMethod.

sample java Spot.sample cpp AmiAsample1. Contains sample applications with AMI interfaces.java DM2_Dynamic. Contents Hawk.java DM1.c ami_sample2.java DM1_Dynamic.cpp Makefile.properties samples ami_api c ami_sample1.log Event. sample rulebases.log Display. scripts.Java TestConsole.java ma_plugin DemoMicroagent.java GroupOpSample.TIBCO Hawk Directory Structure 171 | Table 21 TIBCO Hawk Files and Directories (Cont’d) Directory Log Description Contains log files written by TIBCO Hawk agents and TIBCO Hawk Display. and other files.log HMA.log resource Contains files used by TIBCO Hawk Display.c ami_sample3.c MakeFile.Java console_api ConsoleApp.java DM2.java TIBCO Hawk Installation and Configuration .java SpotAmi. HawkGui.

hrb HawkAgent-Unix.hrb Tru64UNIX.java RBMapGetandSet.java RBMapSampleConstant.hrb HP-UX.hrb Win2000.hrb HawkWindowsEventLog.hrb Spot.java ScheduleGetandSet.hsf schedule_api ScheduleCreateAndSave.hrb Sleep.java TIBCO Hawk Installation and Configuration .172 | Appendix C TIBCO Hawk Directories and Files Table 21 TIBCO Hawk Files and Directories (Cont’d) Directory samples Cont’d Description Contains sample applications with AMI interfaces.hrb WinNT.hrb WinXP.hrb Linux2x.java RBMapSampleConsole.java rulebases AIX.java ScheduleSampleConstant.hrb TibRendezvous.hrb WinNT_Server. and other files.hrb rbmap.java ScheduleSampleConsole.java ScheduleWithPeriodGroup.hrm schedules.hrb Solaris2x. sample rulebases. scripts. Contents rbmap_api RBMapCreateandSave.

txt TrustedWithDomain.c ami_sample2.java Trusted.bat Additional files on UNIX etc hawk2 scripts run_spot amiworkbench Files on OS/400 ami_api c ami_sample1.bat amiworkbench.java TestOperation.java TIBCO Hawk Installation and Configuration .txt Test.c java AmiSample.txt Additional files on Windows scripts run_spot.TIBCO Hawk Directory Structure 173 | Table 21 TIBCO Hawk Files and Directories (Cont’d) Directory samples Cont’d Description Contents scripts amiworkbench run_spot security Certified.

174 | Appendix C TIBCO Hawk Directories and Files TIBCO Hawk Installation and Configuration .

| 175 Appendix D Certificates This appendix describes certificates. Topics • Example Certificate File. page 176 TIBCO Hawk Installation and Configuration .

ENCRYPTED\n \ #DEK-Info: DES-EDE3-CBC.key = -----BEGIN CERTIFICATE-----\n \ #MIIDGDCCAoGgAwIBAgIBAjANBgkqhkiG9w0BAQQFADBgMQswCQYDVQQGEwJVUzET\n #MBEGA1UECBMKTmV3IEZvb2JhcjEhMB8GA1UEChMYSW50ZXJuZXQgV2lkZ2l0cyBQ\n #dHkgTHRkMRkwFwYDVQQDExBDQSBBZG1pbmlzdHJhdG9yMB4XDTAxMDcwMzE3MzQ0\n #NloXDTAyMDcwMzE3MzQ0NlowWjELMAkGA1UEBhMCVVMxEzARBgNVBAgTClNvbWUt\n #U3RhdGUxITAfBgNVBAoTGEludGVybmV0IFdpZGdpdHMgUHR5IEx0ZDETMBEGA1UE\n #AxMKSGF3ayBBZ2VudDCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAsi0mvVAq\n #Ak/S6HN97GXU0ztJLxEmBkZuxde99H7cUJjAJyoENpgWb6ZIhbDSQSL6yMWY/B+Z\n #9SnLHs+f9n6qrAOn1Xlrvlne8UhnuBSZ3HL5OUWCjaHYijRmnK1FkFMsBJ1X23T5\n #kL2plTrEABQzQHX67lAmkbZ8tyanPP5teIkCAwEAAaOB5zCB5DAJBgNVHRMEAjAA\n #MCwGCWCGSAGG+EIBDQQfFh1PcGVuU1NMIEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAd\n #BgNVHQ4EFgQU1oO0yNN8Tpicz+4CaROknQV9Cj0wgYkGA1UdIwSBgTB/gBS6Jwjz\n #PR4x4/WgY/OV2+WmXLBQmqFkpGIwYDELMAkGA1UEBhMCVVMxEzARBgNVBAgTCk5l\n #dyBGb29iYXIxITAfBgNVBAoTGEludGVybmV0IFdpZGdpdHMgUHR5IEx0ZDEZMBcG\n #A1UEAxMQQ0EgQWRtaW5pc3RyYXRvcoIBADANBgkqhkiG9w0BAQQFAAOBgQCd56Y6\n #eEgRuz1KfWBq25/MRhGxtWVJscuraOUUPFlcYeUlSpdRsxKBq9VgdHcAQgut5ZgJ\n #DM0oyg2lHcZAWAt9dIWtFqCg2p8mdIxMzi2pLC+eZEgx7t7NUwtQL6oRfZHSl7vD\n #uWfn6w4gFepY/ynaSiPDIlCr3Zbzjy7hNLZNag==\n \ #-----END CERTIFICATE-----\n \ #-----BEGIN RSA PRIVATE KEY-----\n \ #Proc-Type: 4. Remove the # at the beginning of each line to uncomment the line.txt file. PEM encoding is always used for certificates. #agent. so they look like text. as in the following example.176 | Appendix D Certificates Example Certificate File The certificate and private key for an agent can be included in the Certified. or a pointer can be provided to a separate file containing this information.118CDC345C0DAB35\n \ # \n \ #QgGaqKReWk7xS9mEdDLjBQLXHI5MeSjtFMLtjp1xKlA8xdGsb44j4gY00UbFBTiO\n #fkGTutY6syjHiBxgF6svaPMgI793V7CZmkDNlDgvMUL4ZwEoL1fxtdWQ4S+OG9JV\n #WorTCMmIfeObrV8M2lArbBsDmYUEwBud4gSip4d3YxRqf0LiPAKTOjheVnPTolJ+\n #ogkcJTeE0WglsQJedHyL6cqrKMmMqlwrlRjjCnRy71KnvVafHGviLc41VkCX6maM\n #DdPeke+xTqMoXWIciil1R4UhupaRSQCs0UKa0szeX0mxThy/G28slDD1A6nha17I\n #Qwt925u6lEuCzwQSM3abjgI3EFjSZu5iYe51iMWJnWzn1cm+hVvb8hP6VDRyDNbY\n #iZHQjAsMvxXWj2oVf5+jRx33HUROB5JO2Elp8eeeU75yGC/1NIIIlUAqVWE8GyNh\n #yx9dRPOoJY5Q6ycS4iQvG3zn4WjIYSg/ZENW9AeWtDWsTAJAHdwYGdmQsO1q0uhk\n #XW/MGeOmDbumOJM2PO/85XNAhCkITkNOgH7OVTjJjfqucIybCUWUdBEXBeOelTXw\n #I+O1IYTM997d+ncH3fXqCDDBkfyXrzkveOxRZpu/Bgyd/tXQB41ARAqUZQjmxyOs\n #FgKryrqHmrShqvFntDH9Sqko5dRujJhftq6/QYsYlc+OgejNg/F4N4a+GkgW+wgg\n #WRk+WjPI365WrVlEW9ar/lhqqgHsk7bPKHk+SR+t+sbbMeFUKQd8ejg8wyPmjFO/\n #Ba8awLurCGq1VgrlqmlVlAKJpv38E597ahPcWA1qS5W/Llkpo8SsCg==\n \ #-----END RSA PRIVATE KEY-----\n \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ TIBCO Hawk Installation and Configuration .

page 178 TIBCO Hawk Installation and Configuration .| 177 Appendix E Code Page Identifiers This appendix lists code page identifiers that can be specified to indicate the locale of the machine running the HMA. Topics • Code Page Identifiers.

Arabic TIBCO Hawk Installation and Configuration .Greek (formerly 437G) OEM .Turkish OEM .Hebrew OEM .International Arabic .U.Transparent ASMO OEM .178 | Appendix E Code Page Identifiers Code Page Identifiers Code page identifiers are specified as a value in the Codepage field.United States IBM EBCDIC .Latin II OEM .Canadian-French OEM . BCON V4 Arabic .Multilingual Latin I OEM .Icelandic OEM .Cyrillic (primarily Russian) OEM .Multilingual Latin I + Euro symbol OEM ./Canada OEM .ASMO 449+.S.Baltic OEM . See Codepage on page 93 for details.Transparent Arabic Arabic . Table 22 Code Page Identifiers Identifier 037 437 500 708 709 710 720 737 775 850 852 855 857 858 860 861 862 863 864 Name IBM EBCDIC .Portuguese OEM .ASMO 708 Arabic .

Japanese.Code Page Identifiers 179 | Table 22 Code Page Identifiers (Cont’d) Identifier 865 866 869 870 874 875 932 936 949 950 1026 1047 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1200 Name (Cont’d) OEM .United Kingdom (20285 + Euro symbol) IBM EBCDIC .Latin America/Spain (20284 + Euro symbol) IBM EBCDIC . ISO 8859-15) IBM EBCDIC .Finland/Sweden (20278 + Euro symbol) IBM EBCDIC .Simplified Chinese (PRC.Thai (same as 28605.Russian OEM .Modern Greek ANSI/OEM . Singapore) ANSI/OEM ./Canada (037 + Euro symbol) IBM EBCDIC .Germany (20273 + Euro symbol) IBM EBCDIC .Nordic OEM .Icelandic (20871 + Euro symbol) Unicode UCS-2 Little-Endian (BMP of ISO 10646) TIBCO Hawk Installation and Configuration .Modern Greek IBM EBCDIC .France (20297 + Euro symbol) IBM EBCDIC . Shift-JIS ANSI/OEM .Denmark/Norway (20277 + Euro symbol) IBM EBCDIC .International (500 + Euro symbol) IBM EBCDIC .Multilingual/ROECE (Latin-2) ANSI/OEM .Traditional Chinese (Taiwan. Hong Kong SAR.Korean (Unified Hangeul Code) ANSI/OEM .U.Latin 1/Open System IBM EBCDIC .Turkish (Latin-5) IBM EBCDIC .S. PRC) IBM EBCDIC .Italy (20280 + Euro symbol) IBM EBCDIC .

Cyrillic MAC .Turkish ANSI .Hebrew MAC .Japanese MAC .Simplified Chinese (GB 2312) MAC .Thai TIBCO Hawk Installation and Configuration .Latin I ANSI .Romania MAC .180 | Appendix E Code Page Identifiers Table 22 Code Page Identifiers (Cont’d) Identifier 1201 1250 1251 1252 1253 1254 1255 1256 1257 1258 1361 10000 10001 10002 10003 10004 10005 10006 10007 10008 10010 10017 10021 Name (Cont’d) Unicode UCS-2 Big-Endian ANSI .Arabic MAC .Ukraine MAC .Arabic ANSI .Cyrillic ANSI .Roman MAC .Traditional Chinese (Big5) MAC .Baltic ANSI/OEM .Central European ANSI .Hebrew ANSI .Greek I MAC .Korean MAC .Vietnamese Korean (Johab) MAC .Greek ANSI .

61 ISO 6937 Non-Spacing Accent IBM EBCDIC .Italy TIBCO Hawk Installation and Configuration .Taiwan Wang .Taiwan Eten .Taiwan IA5 IRV International Alphabet No.Taiwan IBM5550 .Turkish MAC .Croatia Unicode UCS-4 Little-Endian Unicode UCS-4 Big-Endian CNS .Code Page Identifiers 181 | Table 22 Code Page Identifiers (Cont’d) Identifier 10029 10079 10081 10082 12000 12001 20000 20001 20002 20003 20004 20005 20105 20106 20107 20108 20127 20261 20269 20273 20277 20278 20280 Name (Cont’d) MAC .Denmark/Norway IBM EBCDIC .Finland/Sweden IBM EBCDIC .Taiwan TeleText . 5 (7-bit) IA5 German (7-bit) IA5 Swedish (7-bit) IA5 Norwegian (7-bit) US-ASCII (7-bit) T.Icelandic MAC .Germany IBM EBCDIC .Taiwan TCA .Latin II MAC .

France IBM EBCDIC .Icelandic IBM EBCDIC .Japanese Katakana Extended IBM EBCDIC .United Kingdom IBM EBCDIC .182 | Appendix E Code Page Identifiers Table 22 Code Page Identifiers (Cont’d) Identifier 20284 20285 20290 20297 20420 20423 20424 20833 20838 20866 20871 20880 20905 20924 20932 20936 21025 21027 21866 28591 28592 28593 28594 Name (Cont’d) IBM EBCDIC .Hebrew IBM EBCDIC .Arabic IBM EBCDIC . Bulgarian) Extended Alpha Lowercase Ukrainian (KOI8-U) ISO 8859-1 Latin I ISO 8859-2 Central Europe ISO 8859-3 Latin 3 ISO 8859-4 Baltic TIBCO Hawk Installation and Configuration .Cyrillic (Serbian.Latin America/Spain IBM EBCDIC .Thai Russian .Korean Extended IBM EBCDIC .KOI8-R IBM EBCDIC .Turkish IBM EBCDIC .Greek IBM EBCDIC .Cyrillic (Russian) IBM EBCDIC .Latin-1/Open System (1047 + Euro symbol) JIS X 0208-1990 & 0121-1990 Simplified Chinese (GB2312) IBM EBCDIC .

Code Page Identifiers 183 | Table 22 Code Page Identifiers (Cont’d) Identifier 28595 28596 28597 28598 28599 28605 29001 38598 50220 50221 50222 50225 50227 50229 50930 50931 50933 50935 50936 50937 50939 51932 51936 Name (Cont’d) ISO 8859-5 Cyrillic ISO 8859-6 Arabic ISO 8859-7 Greek ISO 8859-8 Hebrew ISO 8859-9 Latin 5 ISO 8859-15 Latin 9 Europa 3 ISO 8859-8 Hebrew ISO 2022 Japanese with no halfwidth Katakana ISO 2022 Japanese with halfwidth Katakana ISO 2022 Japanese JIS X 0201-1989 ISO 2022 Korean ISO 2022 Simplified Chinese ISO 2022 Traditional Chinese Japanese (Katakana) Extended US/Canada and Japanese Korean Extended and Korean Simplified Chinese Extended and Simplified Chinese Simplified Chinese US/Canada and Traditional Chinese Japanese (Latin) Extended and Japanese EUC .Japanese EUC .Simplified Chinese TIBCO Hawk Installation and Configuration .

Korean EUC .184 | Appendix E Code Page Identifiers Table 22 Code Page Identifiers (Cont’d) Identifier 51949 51950 52936 54936 57002 57003 57004 57005 57006 57007 57008 57009 57010 57011 65000 65001 Name (Cont’d) EUC .Traditional Chinese HZ-GB2312 Simplified Chinese Windows XP: GB18030 Simplified Chinese (4 Byte) ISCII Devanagari ISCII Bengali ISCII Tamil ISCII Telugu ISCII Assamese ISCII Oriya ISCII Kannada ISCII Malayalam ISCII Gujarati ISCII Punjabi Unicode UTF-7 Unicode UTF-8 TIBCO Hawk Installation and Configuration .

121 default TIBCO Hawk agent name (-host). 30 Interactive Mode 17. Planning TIBCO Hawk 88 Csh users 35 customer support xvi H heartbeat interval Setting 117. 121 dial-up network connection. 121 How the Installer Searches for JRE 7 D daemon configuration for TIBCO Hawk messaging. 32 TIBCO Hawk Installation and Configuration . 25. 29 Installation Options 15. Overriding I Install and Generate a Response File 16. 121 -ami_rva_session 103 -ami_rvd_session 103 automatically.| 185 Index A Adding AMI sessions 103 Adding the rvrd service value to the Windows registry 120 agent heartbeat interval Setting 117. Making TIBCO Hawk services depend on the routing 118 default container for the TIBCO Hawk Display 117. 121 Disk Space and Memory 13. 31 Install and Generate a Template File 17. 121 configuration on Unix. 121 agent name 117. Setting up the routing 121 daemon service automatically. Making TIBCO Hawk services 118 Designating a security policy 117. 121 -host 117. 32 Install Using Console 16. 32 Install in Silent Mode 16. Using the TIBCO Hawk Display over a 117. Starting the routing 118 daemon service. Starting the routing daemon service 118 the 117. 31 Install Using GUI 16. Setting up the routing daemon 121 configuration. 31 Install Using a Response File 17. 40 E Example TIBCO Rendezvous routing daemon configuration for TIBCO Hawk messaging 115 C -cluster 117. Example TIBCO Rendezvous routing 115 daemon configuration on Unix. 31 Installation Directories 4 Installation Directory 13 Installation Media 15. 121 depend on the routing daemon service.

121 saging. TIBCO Hawk services in Windows 119 registry. 121 security_policy 117. 32 Software 14. 26. 40 Specifying the JRE Location 7 Starting the routing daemon service automatically 118 support. 121 service. Example TIBCO Rendezvous 115 routing daemon configuration on Unix. contacting xvi O over a dial-up network connection. 121 setting the TIBCO Hawk agent heartbeat interval 121 Setting up a TIBCO Rendezvous session 103 Setting up the routing daemon configuration on Unix 121 Silent Mode 17. Making TIBCO Hawk services depend on the 118 -rva_session 103 -rvd_session 103 rvrd service value to the Windows registry. 121 Overriding the default TIBCO Hawk agent name 117. TIBCO Hawk 119 Setting the TIBCO Hawk agent heartbeat interval 117. Adding the rvrd service value to Windows 120 routing daemon configuration for TIBCO Hawk mesTIBCO Hawk Installation and Configuration T technical support xvi Temp Directory 13 TIBCO Hawk agent heartbeat interval (-interval). 26 registry editor. 121 TIBCO Hawk agent name (-host). Using the TIBCO Hawk Display over a dial-up 117.186 | Index -interval 117. 121 security policy. Starting the 118 routing daemon service. Adding the 120 J JRE Search Locations 8 L license tickets 126 S N network connection. Making TIBCO Hawk 118 services in the Windows registry editor. designating 117. Making TIBCO Hawk services depend on the routing daemon 118 services depend on the routing daemon service. Setting up the 121 routing daemon service automatically. Setting 117. Using the TIBCO Hawk Display 117. Overriding the . 121 P Planning TIBCO Hawk configuration 88 R RAM 13.

Index 187 | default 117. Planning 88 TIBCO Hawk Display over a dial-up network connection. Using the 117. Example 115 TIBCO Software 14. 40 Trace level 65 tracing 66 U UNIX installation 23 User Privileges 12. 40 Using the TIBCO Hawk Display over a dial-up network connection 117. 121 TIBCO Hawk configuration. TIBCO Hawk services in Windows 119 Windows registry. 24. 26. Adding the rvrd service value to the registry 120 TIBCO Hawk Installation and Configuration . 121 TIBCO Hawk services in the Windows registry editor 119 TIBCO Rendezvous routing daemon configuration for TIBCO Hawk messaging. 121 W Windows registry editor.

188 | Index TIBCO Hawk Installation and Configuration .

Sign up to vote on this title
UsefulNot useful