Pco Web Edition

PATROL Central Operator Web Edition Getting Started
Version 7.1.10
December 31, 2003
Copyright 2004 BMC Software, Inc., as an unpublished work. All rights reserved. BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc. All other registered trademarks or trademarks belong to their respective companies. PATROL technology holds U.S. Patent Number 5655081. THE USE AND CONTENTS OF THIS DOCUMENTATION ARE GOVERNED BY THE SOFTWARE LICENSE AGREEMENT ENCLOSED AT THE BACK OF THIS DOCUMENTATION.
Restricted Rights Legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101 CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to this address.
Contacting BMC Software

You can access the BMC Software Web site at http://www.bmc.com. From this Web site, you can obtain information about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada

Address BMC Software, Inc. 2101 CityWest Blvd. Houston TX 77042-2827 713 918 8800 or 800 841 2031 713 918 8000
Outside United States and Canada

Telephone Fax (01) 713 918 8800 (01) 713 918 8000
Telephone Fax
Customer Support
You can obtain technical support by using the Support page on the BMC Software Web site or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, please see Before Contacting BMC Software.
Support Web Site

You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support.html. From this Web site, you can read overviews about support services and programs that BMC Software offers find the most current information about BMC Software products search a database for problems similar to yours and possible solutions order or download product documentation report a problem or ask a question subscribe to receive e-mail notices when new product versions are released find worldwide BMC Software support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers
Support by Telephone or E-mail

In the United States and Canada, if you need technical support and do not have access to the Web, call 800 537 1813. Outside the United States and Canada, please contact your local support center for assistance. To find telephone and e-mail contact information for the BMC Software support center that services your location, refer to the Contact Customer Support section of the Support page on the BMC Software Web site at www.bmc.com/support.html.
Before Contacting BMC Software

Before you contact BMC Software, have the following information available so that Customer Support can begin working on your problem immediately: product information product name product version (release number) license number and password (trial or permanent)
operating system and environment information machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or maintenance level
BMC Software, Inc., Confidential and Proprietary Information
iii
sequence of events leading to the problem commands and options that you used messages received (and the time and date that you received them) product error messages messages from the operating system, such as file system full messages from related software
iv
Contents
Contents
Chapter 1 Product Components and Capabilities
PATROL Central Operator Features . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 How PATROL Central Operator Fits into PATROL Central . . . . . . . 1-3 How PATROL Central Operator Fits into PATROL . . . . . . . . . . . . . 1-4 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Accessing Books and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Chapter 2 Installing PATROL Central Operator
Implementation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 The PATROL 7.x Environment . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Considerations for Determining Which Web Server to Use . . . . 2-3 Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 Preparing to Install PATROL Central Operator . . . . . . . . . . . . . . . . . 2-8 Workflow for Installing PATROL Central Operator . . . . . . . . . . 2-8 Installable Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 Choosing a Typical or Custom Installation . . . . . . . . . . . . . . . . . 2-14 Required Information for a Typical Installation . . . . . . . . . . . . . 2-15 Required Information for a Custom Installation . . . . . . . . . . . . . 2-22 Installation Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24 Upgrading Versus First-Time Installation . . . . . . . . . . . . . . . . . 2-29 Installing PATROL Central Operator on Windows . . . . . . . . . . . 2-32 Installing PATROL Central Operator on Unix . . . . . . . . . . . . . . 2-46 Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62 Backing Up and Restoring PATROL Central and Console Modules . 2-63 Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64
Contents
Chapter 3
Monitoring and Managing Your Enterprise with PATROL Central Operator
Web Browser Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2 Solaris OS Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3 About the Java Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3 About Installing or Accepting the Certificate . . . . . . . . . . . . . . .3-6 Using Internet Explorer Version 6 on Windows 2003 . . . . . . . . .3-6 Setting Up Your Monitoring Environment . . . . . . . . . . . . . . . . . . . . .3-7 Accessing PATROL Central . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8 The PATROL Central Console Infrastructure . . . . . . . . . . . . . . .3-9 Accessing PATROL Central Operator . . . . . . . . . . . . . . . . . . . . .3-11 About Your Management Profile . . . . . . . . . . . . . . . . . . . . . . . . .3-12 Connecting to a PATROL Console Server and Selecting a Management Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14 Adding Managed Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-18 Loading PATROL KMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21 Where to Go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-24
Chapter 4 Administering Users of PATROL Central Operator
About Accounts and Groups in the PATROL Environment . . . . . . . .4-2 Setting Up User Accounts and Groups . . . . . . . . . . . . . . . . . . . . . . .4-4 User Accounts and Groups on PATROL Central Web Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-4 User Accounts and Groups on the PATROL Console Server . . . .4-4 User Accounts on Managed Systems . . . . . . . . . . . . . . . . . . . . .4-6 General Guidelines for Setting Up User Accounts and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-6 Administering Aliases and Impersonation . . . . . . . . . . . . . . . . . . . . .4-8 About the User Authentication Process . . . . . . . . . . . . . . . . . . . .4-9 Example Scenario for A Single Account for All Managed Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-10 Example Scenario for Different Accounts According to Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-11 Example Scenario for A Single Account for All Managed Systems But One . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-12 Administering Privileges and Rights . . . . . . . . . . . . . . . . . . . . . . . . .4-14 About Assigning Privileges and Rights . . . . . . . . . . . . . . . . . . . .4-14 Predefined Groups on the PATROL Console Server . . . . . . . . . .4-15 Privileges Used in PATROL Central Operator . . . . . . . . . . . . . .4-15 Rights Used in PATROL Central Operator . . . . . . . . . . . . . . . . .4-17
vi
How Predefined Privileges and Rights Determine Group Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18 Using the Predefined Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19 Special Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20 Example Scenario for Granting Privileges . . . . . . . . . . . . . . . . . 4-20 Example Scenario for Adding Rights for Management Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23 About PATROL Central Administration . . . . . . . . . . . . . . . . . . . . . . 4-27 Starting PATROL Central Administration . . . . . . . . . . . . . . . . . 4-28
Chapter 5 Configuring the PATROL Central Console Environment
Starting and Stopping Related Programs . . . . . . . . . . . . . . . . . . . . . . 5-2 Starting and Stopping the RTserver . . . . . . . . . . . . . . . . . . . . . . 5-3 Starting and Stopping the PATROL Agent . . . . . . . . . . . . . . . . . 5-5 Starting and Stopping the PATROL Console Server . . . . . . . . . . 5-7 Managing Services on Windows . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 Starting and Stopping PATROL Central Operator Web Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 Starting and Stopping PATROL Central Operator Web Edition on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12 Starting and Stopping PATROL Central Operator Web Edition on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 Verifying the Installation and Execution of the Web Server and Related Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15 Changing Web Server Ports after Installation . . . . . . . . . . . . . . . . . . 5-16 Changing Tomcat Standalone Web Server Ports . . . . . . . . . . . . 5-16 Changing Apache Web Server Ports . . . . . . . . . . . . . . . . . . . . . . 5-20 Changing IIS Web Server Ports . . . . . . . . . . . . . . . . . . . . . . . . . 5-25 Changing the Java Plug-in Version after Installation . . . . . . . . . . . . 5-30 Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Chapter 6 Using the PATROL 3.x and PATROL 7.x Consoles
Compatibility and Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 PATROL Agent Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 KM Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Developer Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Differences Between PATROL Console for Windows or PATROL Console for Unix and PATROL Central Operator . . . . . . . . . . . . . 6-3 Communications with Managed Systems . . . . . . . . . . . . . . . . . . 6-4 Session and Desktop Files Versus Management Profiles . . . . . . 6-4
Contents
vii
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5 User Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5 User Names and Passwords for Managed Systems . . . . . . . . . . .6-6 Computer Name and Port Number Versus Managed System Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-6 Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-7 Customizations Versus Overrides . . . . . . . . . . . . . . . . . . . . . . . .6-7 State Change Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-7 KM Version Arbitration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-8 Chart History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-8 Location of Task Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9 KMs in the PATROL Object Namespace . . . . . . . . . . . . . . . . . .6-9 Running Menu Commands and InfoBox Commands . . . . . . . . .6-10 Migrating Console Information from PATROL Console for Windows or PATROL Console for Unix . . . . . . . . . . . . . . . . . . . . .6-10
Chapter 7 Troubleshooting PATROL Central Operator
Common Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2 Installation Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3 Web Server Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-5 Problems that May Occur While Using PATROL Central Operator Web Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-8 Gathering Troubleshooting Information . . . . . . . . . . . . . . . . . . . . . .7-25 Installation Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-25 Web Server Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-25 Client Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-29 Checking Which PATROL Central Ports Are In Use on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-30 Obtaining Version, System and Contact Information . . . . . . . . .7-31 Dealing with Web Server Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-32
Appendix A Enhancing Web Server Security
About the Keystore Password and Self-signed Certificate for the Apache Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Keystore Password and the Apache Policy File . . . . Replacing the Self-signed Certificate . . . . . . . . . . . . . . . . . . . . About Attended and Unattended Modes for the Apache Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-2 A-2 A-3 A-3
viii
Appendix B
Modifying Initialization Settings After Installation
The Startup Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2 About Modifying the Startup Configuration File . . . . . . . . . . . .B-2 What You May Modify in the Startup.cfg file . . . . . . . . . . . . . .B-3
Appendix C Index Environment Variables
Contents
ix
Product Components and Capabilities
This chapter provides an overview of the PATROL Central Operator Web Edition product for users and administrators of PATROL Central Operator. This product is also called PATROL Central Operator. PATROL Central Operator Features . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 How PATROL Central Operator Fits into PATROL Central . . . . . . . 1-3 How PATROL Central Operator Fits into PATROL . . . . . . . . . . . . . 1-4 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Accessing Books and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
1-1
PATROL Central Operator Features

The Web Edition of PATROL Central Operator is a cross-platform, Web-based console for use with the PATROL 7.x architecture. You can use it to monitor and manage an entire enterprise-wide information system or a collection of workstations, server computers, and single computers.
PATROL 7.x Architecture
PATROL Central Operator is part of the PATROL 7.x architecture. It communicates with PATROL Agents through the Real Time server (RTserver) and the PATROL Console Server. The PATROL Console Server acts as a centralized repository for storing PATROL Central Operator data in management profiles and serves as a mid-level tier to deliver data from managed systems to PATROL Central Operator, thereby reducing network traffic. For more information about PATROL Console Server and RTserver, see the PATROL Console Server and RTserver Getting Started.
System Monitoring and Managing
From PATROL Central Operator, you can view the state of resources, such as managed systems, applications, and parameters that are managed by PATROL. You can also perform basic PATROL operator console functions on those objects, such as parameter customizations, event management, managed system queries, and KM commands.
Note
PATROL developer functionality is not supported by PATROL Central Operator. For development functionality, use the PATROL Console for Windows or PATROL Console for Unix in developer mode.
1-2
Custom Views
You can create custom views in your management profile. A custom view is a single window that can display multiple objects. For example, you can create a custom view to display the charts of several parameters together.
How PATROL Central Operator Fits into PATROL Central

PATROL Central Operator is a console module that leverages the PATROL Central console infrastructure. The Web Edition of PATROL Central provides an integrated Web-based interface for its console modules. Both the console infrastructure and console modules are installed on the Web server.
1-3
How PATROL Central Operator Fits into PATROL

Like other PATROL consoles, PATROL Central Operator provides a window into your PATROL environment. PATROL Central Operator works with the PATROL 7.x architecture. Figure 1-1 shows the relationship between the Web Edition of PATROL Central Operator and other PATROL programs. Almost all of the information that you view in PATROL Central Operator ultimately comes from the individual managed systems. However, all communication between PATROL Central Operator and the managed systems is facilitated by the PATROL Console Server and Real-Time Server (RTserver) cloud.
Note
For a more complete understanding of PATROL architecture, see the PATROL Fundamentals online Help.
1-4
Figure 1-1
PATROL Architecture for the Web Edition of PATROL Central Operator
Console Systems
Web browser
Common Services
PATROL Central Web Edition PATROL Central Operator Web Edition Other console modules RTserver Cloud
PATROL Console Server
Managed Systems
PATROL Agent (version 3.5) Install PATROL solutions (KMs) for resources on each system.
PATROL products and solutions may require additional files installed throughout the infrastructure.
1-5
Related Documentation
PATROL Central Operator is supported by the following documents: PATROL Central Web Edition online Help PATROL Central Operator Web Edition online Help PATROL Central Administration Web Edition online Help PATROL Fundamentals online Help PATROL Central Operator Web Edition Getting Started PATROL Central Operator Web Edition Release Notes PATROL Console Server and RTserver Getting Started PATROL Installation Reference Manual PATROL Security User Guide PATROL Infrastructure Planning Guide
1-6
Accessing Online Help

Online Help provides detailed instructions on how to use PATROL Central Operator, the PATROL Central console infrastructure, and other console modules. It also provides reference information on Knowledge Modules (KMs). The following table describes a variety of methods for accessing Help.
For Help on
individual console modules, such as PATROL Central Operator or PATROL Central Administration
Do This
In the upper-right corner of the PATROL Central interface, click the Help icon and choose PATROL Central Help.
PATROL Central and console module pages, including fields PATROL Knowledge Modules
In the toolbar area, click the page help icon.
In the upper-right corner of the PATROL Central interface, click the Help icon and choose PATROL KM Help.
application instances and classes parameters
In the tree view area, right-click the application instance or class and choose Help. In the tree view area, right-click the parameter and choose Help.
1-7
Accessing Books and Release Notes

A set of PATROL manuals is provided on the documentation CD included with the kit. You can view manuals in electronic format or order additional printed copies from the Web at http://www.bmc.com/support.html. For the latest updates to product information, refer to the release notes, which are available at http://www.bmc.com/support.html.
Where to Go from Here

For information about...
installing PATROL Central Operator monitoring and managing with PATROL Central Operator setting up account and groups, administrating aliases, impersonations, privileges, and rights. configuring other PATROL programs and computers to work with PATROL Central Operator and running the Web server using both PATROL 3.x console and PATROL Central Operator, or moving from a PATROL 3.x console provides troubleshooting information related to installing and configuring PATROL Central Operator.
See...
Chapter 2, Installing PATROL Central Operator and the PATROL Installation Reference Manual Chapter 3, Monitoring and Managing Your Enterprise with PATROL Central Operator Chapter 4, Administering Users of PATROL Central Operator
Chapter 5, Configuring the PATROL Central Console Environment
Chapter 6, Using the PATROL 3.x and PATROL 7.x Consoles
Chapter 7, Troubleshooting PATROL Central Operator
1-8
Installing PATROL Central Operator 2

This chapter provides information for PATROL administrators about installing the Web Edition of PATROL Central Operator. For more information on how to run the installation program and the differences between types of installations, see the PATROL Installation Reference Manual. This chapter discusses the following topics: Implementation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 The PATROL 7.x Environment . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Considerations for Determining Which Web Server to Use . . . . 2-3 Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 Preparing to Install PATROL Central Operator . . . . . . . . . . . . . . . . . 2-8 Workflow for Installing PATROL Central Operator . . . . . . . . . . 2-8 Installable Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 Choosing a Typical or Custom Installation . . . . . . . . . . . . . . . . . 2-14 Required Information for a Typical Installation . . . . . . . . . . . . . 2-15 Required Information for a Custom Installation . . . . . . . . . . . . . 2-22 Installation Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24 Upgrading Versus First-Time Installation . . . . . . . . . . . . . . . . . 2-29 Installing PATROL Central Operator on Windows . . . . . . . . . . . 2-32 Installing PATROL Central Operator on Unix . . . . . . . . . . . . . . 2-46 Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62 Backing Up and Restoring PATROL Central and Console Modules . 2-63 Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64
Installing PATROL Central Operator
2-1
Implementation Considerations
This section provides an overview of things to consider when implementing PATROL Central Operator and the PATROL 7.x architecture. For more information about implementation, see the PATROL Infrastructure Planning Guide and run the PATROL Infrastructure Planner.
The PATROL 7.x Environment

PATROL Central Operator requires a PATROL 7.x environment, which includes the following components: PATROL Agent v3.5 or later installed on managed systems RTserver v6.2 or later PATROL Console Server v7.2.30 or later PATROL KMs
The size of your environment and number of concurrent users determines the number of PATROL Console Servers and RTservers you need. For detailed explanations and guidance, see the PATROL Infrastructure Planning Guide. For more information about installing PATROL Console Server and RTserver, see the PATROL Console Server and RTserver Getting Started. For more information about installing PATROL Agent and PATROL KMs, see the getting started guide for the product or solution you are installing.
Note
You must enable the PATROL Agent 3.5 to communicate with the RTserver before you can use PATROL Central Operator to monitor that managed system. For more information, see the PATROL Console Server and RTserver Getting Started.
2-2
Considerations for Determining Which Web Server to Use

The PATROL Central console infrastructure requires a Web server.
Platform
Windows
Available Web Servers

IIS (version 4.0 for Windows NT, version 5.0 for Windows 2000, or version 6.0 for Windows 2003) with Tomcat servlet container Tomcat version 4.1.29 standalone (not recommended for production environments) Apache version 1.3.29 with Tomcat servlet container Tomcat version 4.1.29 standalone (not recommended for production environments)
Unix
About the Tomcat Servlet Container
The Tomcat servlet container is installed and used with PATROL Central, regardless of the Web server that you choose. This servlet container runs Java code for PATROL Central.
IIS Web Server with Tomcat Servlet Container (Windows)
If you choose to integrate with Microsoft Internet Information Services (IIS), IIS must already be installed on the computer on which you want to install PATROL Central. The Tomcat servlet container will be installed and used when you install PATROL Central. The installation will add a virtual directory and an ISAPI filter, both named PATROLCentralWebEdition, to the selected IIS Web Site instance. The ISAPI filter redirects execution of Java pages to the Tomcat servlet container. IIS must be configured to support HTTPS. For specific instructions, consult your IIS documentation. As part of the process, you configure IIS with either a self-signed or a trusted root certificate from a certificate authority. The certificate is required to enable Secure Sockets Layer (SSL) for the Web server. See About Certificates on page 2-6. For more information about obtaining and installing a certificate, see Certificate Information (IIS Only) on page 2-18.
2-3
Apache Web Server with Tomcat Servlet Container (Unix)
If you choose to integrate with Apache version 1.3.29, both Apache and the Tomcat servlet container will be installed and used with PATROL Central. A new instance of Apache will be installed, even if there already is an instance of Apache on the computer. If there will be multiple Web servers on the computer, you must make certain that they do not use conflicting ports. For more information, see Web Server HTTP and HTTPS Ports (Apache and Tomcat Only) on page 2-23. A self-signed certificate is created for you, using information that you enter during the install. However, this certificate is not signed by a trusted root. You might want to replace it with a certificate from a certificate authority. For more information about the information you must provide for the certificate, see Certificate Information (Apache and Tomcat Only) on page 2-20.
Tip
For more information about Apache, see the Apache HTTP Server Web site at http://httpd.apache.org or the Apache documentation installed with Apache at http://hostname:port/manual, where hostname is the name of the server, and port is its HTTP port.
2-4
Tomcat Standalone Web Server (Windows or Unix)
If you choose to use the Tomcat standalone Web server, then Tomcat, including the Tomcat servlet container, will be installed and used with PATROL Central. A new instance of Tomcat will be installed, even if there already is an instance of Tomcat on the computer. If there will be multiple Web servers on the computer, you must make certain that they do not use conflicting ports. For more information, see Web Server HTTP and HTTPS Ports (Apache and Tomcat Only) on page 2-23. A self-signed certificate is created for you, using information that you enter during the install. This certificate is sufficient for use in a test environment. For more information about the information you must provide for the certificate, see Certificate Information (Apache and Tomcat Only) on page 2-20.
Note
Good practice recommends that the Tomcat standalone Web server not be used in production environments. The Tomcat standalone Web server is more commonly used as a development server.
Tip
For more information about Tomcat, see the Jakarta Project Web site at http://jakarta.apache.org/tomcat or the Tomcat documentation installed with Tomcat at http://hostname:port/tomcat-docs, where hostname is the name of the server, and port is its HTTP port.
2-5
About Certificates
A Web server requires a digital certificate, which identifies the source of online transactions. This certificate is contained in a keystore for the Web server. Which Web server you use and the level of security you want determine the type of certificate you use. A certificate can be self-signed or provided by a certificate authority. A self-signed certificate provides encryption, which assures the confidentiality of the data across the network, but a certificate provided by a certificate authority provides the browser user with more confidence that the server delivering the certificate is authentic. A certificate authority, also referred to as the certificate signing authority, is a trusted public or private organization that signs certificates using a private key unique to their organization. A certificate is validated by a hierarchy of certificate authorities that approve the certificate. This process is called a chain of trust. The final certificate authority in the chain is called the trusted root certificate authority or trusted root. Web browsers maintain a list of trusted certificate authorities. Not all certificate authorities are listed in a web browser. The list of trusted certificate authorities can differ between browsers and browser versions. Certificates also contain the name of the Web site to ensure that they are not arbitrarily moved. The Web browser will notify the user if the Web site in the certificate does not match the URL being viewed.
2-6
Firewalls
How you deal with a firewall depends on where it is located. If a firewall separates the Web server from Web browser clients, configure the firewall to allow HTTP and HTTPS communications. If a firewall separates the Web server from the computer with PATROL Console Server, install an RTserver on at least one computer on each side of the firewall. The RTservers communicate across the firewall as a single RTserver cloud. The Web server communicates with the part of the RTserver cloud on its side of the firewall. The RTserver cloud is responsible for carrying messages across the firewall.
Note
For information about configuring the RTserver cloud to work with firewalls, see the PATROL Console Server and RTserver Getting Started.
2-7
Preparing to Install PATROL Central Operator

This section describes installing PATROL Central Operator, including all of its installable components.
Workflow for Installing PATROL Central Operator
Review system requirements and implementation considerations.
Select a computer and a Web server type.
Review required information for an installation starting on page 2-15.
Complete the installation worksheets starting on page 2-24.
5 If needed, create
accounts as indicated in the installation information.
Install PATROL Central Operator.
2-8
Installable Components
The following table lists components that can be installed as part of PATROL Central Operator.
Component
PATROL Central Operator PATROL Central Administration
Comments
This is the primary component of PATROL Central Operator. It is a console module for PATROL Central. This component provides administration of user access to PATROL. It is a console module for PATROL Central. For more information, see About PATROL Central Administration on page 4-27. This component provides the console infrastructure for console modules, such as PATROL Central Operator and PATROL Central Administration. It is automatically installed when you install a console module. Do not install PATROL Central by itself, unless you also install a different product that instructs you to do so.
PATROL Central
Before installing any of these components, ensure that the system requirements have been met (see System Requirements on page 2-10) and that you know all of the required information (see Required Information for a Typical Installation on page 2-15 and Required Information for a Custom Installation on page 2-22).
2-9
System Requirements
This section lists the system requirements for the installable components listed under Installable Components on page 2-9. You do not need to install any PATROL Central Operator components on client computers. For requirements for client computers, see Web Browser Requirements on page 3-2. Minimum Requirements
One of the following operating systems: Red Hat Linux 7.1 Red Hat Linux 7.2 Red Hat Linux 7.3 Red Hat Enterprise Linux AS 2.1 Solaris 7 (32, 64 bit) Solaris 8 (32, 64 bit) Solaris 9 (32, 64 bit) Windows NT 4 Enterprise Edition Windows NT 4 Server Windows 2000 Server Windows 2000 Datacenter Server Windows 2000 Advanced Server Windows 2003 Standard Server Windows 2003 Enterprise Server Windows 2003 Datacenter Server Windows 2003 Web Server See Solaris OS Patches on page 2-11.
Comments
For security purposes, if you use a Windows system, you must use an NTFS system. FAT volumes are not supported.
350 MB disk space (approximately) processor and memory
You need less disk space if you do not install all of the components. The processor and memory required depends on the size of your environment. See Processor and Memory Requirements on page 2-11. See Considerations for Determining Which Web Server to Use on page 2-3 for more information.
One of the following Web servers IIS v4.0 (Windows NT) IIS v5.0 (Windows 2000) IIS v6.0 (Windows 2003) Apache v1.3.29 (Unix, installed with PATROL Central) Tomcat v4.1.29 standalone (Windows or Unix, installed with PATROL Central)
2-10
Minimum Requirements
PATROL environment 100 mbps network speed
Comments
See The PATROL 7.x Environment on page 2-2.
Solaris OS Patches
BMC Software recommends you install the latest patches for Solaris, including the J2SE patch cluster for your version of Solaris. These patches can be retrieved from the Solaris maintenance Web site at http://sunsolve.sun.com.
Warning
The patches are necessary to address multiple problems that can range from subtle usage problems to crashes.
Processor and Memory Requirements
The processor and memory requirements vary, depending on the size of your environment. Each Web browser client is considered one console. Small environments have less than 100 managed systems and three to five consoles. Medium environments have less than 500 managed systems and five to ten consoles. Large environments have more than 500 managed systems and ten or more consoles. A typical large environment might include 1000 managed systems across multiple sites.
The following table lists processor and memory requirements for small, medium, and large environments. Minimum and recommended requirements are listed; use the recommended requirements for better performance or to support a number of console users greater than those listed in the definitions above.
2-11
Resource
Processora
Minimum Requirements
Recommended Requirements
Small environment
Single processor, Intel Pentium III at 800 Mhz (Linux and Windows) Single processor, SUN Ultra 10 at 300 MHz or Netra X1 at 400 MHz (Solaris) 512 MB Dual processor, Intel Pentium III at 800 Mhz (Linux and Windows) Dual processor, Solaris UltraSPARC 220R at 450 MHz (Solaris) 1 GB
Server memory
Medium environment
Processora Dual processor, Intel Pentium III at 800 Mhz (Linux and Windows) Dual processor, SUN Ultra 220R at 450 MHz (Solaris) 1 GB Dual processor, Intel Pentium III at 1400 MHz (Linux and Windows) Dual processor, SUN Ultra 280R at 750 MHz (Solaris) 2 GB
Server memory
Large environment
Processora Dual processor, Intel Pentium IV 1000 Mhz (Linux and Windows) Dual processor, SUN Ultra 280R at 750 MHz (Solaris) 2 GB Three- or four-processor, Intel Pentium IV 1000 Mhz (Linux and Windows) Dual processor, Solaris UltraSPARC 280R at 750 MHz (Solaris) 3 GB
Server memory
a
Specific processors are listed as examples only. You can use an equivalent processor.
2-12
Scalability Guidelines
Use the following guidelines to determine how many PATROL Central Web servers to use. Implement one PATROL Central Web server for each location. Implement PATROL Central Web server for approximately every 25 Web browser clients. This number varies, depending on what the Web browser clients are used for, and the performance burden being placed on the Web server.
Tip
For best performance, especially in a large environment, install PATROL Central and its console modules on a dedicated computer. For information on scalability considerations, see the PATROL Infrastructure Planning Guide.
2-13
Choosing a Typical or Custom Installation

The installation utility provides both Typical and Custom installations. The Typical installation allows you to install all components at the same time. You will be asked for only mandatory configuration information. The defaults will be used for all optional configuration information. The Custom installation allows you to install individual components. You will be asked for both mandatory and optional configuration information.
You must use a Custom installation in the following cases: You want to use a security level greater than basic security. You want to install only some of the components. For example, you want to install only one console module, or you want to install KM help for only some KMs. You want to use specific ports other than the defaults. For example, you have another instance of Apache on the same computer that already uses the default ports. You want to use a specific IIS Web site instance, other than the default.
2-14
Required Information for a Typical Installation

You need to know the information in this section before installing the components listed under Installable Components on page 2-9 using the Typical path.
Installation Directory
The base installation directory is the location where you will install all products that you select. Additional directories will be created under the base installation directory. The default for this directory on Windows is C:\Program Files\BMC Software. The default on Unix is /opt/bmc. This directory is stored as the $BMC_ROOT or %BMC_ROOT% environment variable depending whether the operating system is Unix or Windows respectively.
Note
All BMC Software products installed on the same computer must share the same installation directory because the products share the BMC_ROOT environment variable.
Note
The installation program creates a sub-directory for PATROL Central under the base installation directory. On Windows, the sub-directory is WebCentral. On Unix, the sub-directory is webcentral.
Web Server
You must select which Web server to use. For more information, see Considerations for Determining Which Web Server to Use on page 2-3.
2-15
Root Login and Password (Unix only)
On Unix, you must specify the Root login name and password.
Both the PATROL Central console infrastructure and individual console modules use PATROL Console Servers. A PATROL Console Server can serve different purposes for PATROL Central and each console module. PATROL Central uses a PATROL Console Server as a security server to authenticate users. Only users who have accounts known to that PATROL Console Server can use PATROL Central or any of its console modules. Individual console modules can use the same PATROL Console Server as PATROL Central or additional PATROL Console Servers, depending on the console module. For example, in PATROL Central Operator, users can open management profiles on the PATROL Console Server used by PATROL Central or other PATROL Console Servers.
You specify the PATROL Console Server for PATROL Central during the install of PATROL Central. For information about changing this PATROL Console Server after installation, see Appendix B, Modifying Initialization Settings After Installation.
Tip
You identify a PATROL Console Server by name. By default, this name is the host name of the PATROL Console Server; however, a different name can be specified when starting the PATROL Console Server. Do not use the IP address. You can use additional PATROL Console Servers with individual console modules by including them in the RTserver cloud. For more information, see the PATROL Console Server and RTserver Getting Started.
2-16
For more information about setting up user accounts on PATROL Console Servers, see Setting Up User Accounts and Groups on page 4-4. For more information about the role of the PATROL Console Server, see the PATROL Console Server and RTserver Getting Started.
Web Server User Name and Group (Apache and Tomcat Only)
Before you install PATROL Central, you must create an operating system account for the Web server. If you have already installed BMC Software products and created a base installation directory, BMC Software recommends you use the same account to install PATROL Central Web Edition. The installation will ask you for the user name for the account. You must ensure that the account used for installation has write permissions in the base installation directory. On Unix, you must also be logged on as this account when you run the install. On Unix, you must also create an operating system group for the Web server account, and the account should belong to only this Web server group for security purposes. The installation will also ask you for the group name. Additionally, the installation will ask you for the HTTPD user name and group. These are used to run the HTTPD child daemons and to protect the files. The HTTPD user name and group must be the same as the user name and group you are using to install PATROL Central Operator Web Edition.
Note
If you need to install multiple BMC Software products under different accounts, please call your BMC Software Support representative for instructions.
2-17
Certificate Information (IIS Only)
If you choose to integrate with IIS, you must have a self-signed certificate or a trusted root certificate from a certificate authority. The certificate is required to enable Secure Sockets Layer (SSL) for the Web server. See About Certificates on page 2-6. The general process for obtaining and installing a certificate from a certificate authority for IIS is as follows. For detailed instructions about using IIS, refer to the documentation for that product. 1. Use Admin Tools => Internet Services Manager to create a Certificate Signing Request (CSR).
Note
When creating the CSR, you must specify a bit length of 1024. This will make the certificate more secure. IIS creates a CSR in the format filename.txt, and stores it on your system in the specified directory. A typical CSR is shown below:
-----BEGIN NEW CERTIFICATE REQUEST-----MIIBpTCCAQ4CAQAwZTefgAkGA1UEBhMCVVMxCzAJBg NVBAgTAlRYMRAwDgYDVQQHEwdIb3VzdG9uMRUwEwYDVQQKEwxCTUMg U29mdHdhcmUxEjAQBgNVBAsTCXRlY2ggcHViczEMMAoGA1UEAxMDZG 9jMabcMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCyEsLg33WKokpN A4W+4eeZDxR0F/e6kr3FkdDU54JKZ0nDeXqCHKz+rVM27ahiFksUJv obnZDiZIWpearlizdfHsI37dzTxCCkfNxyzOkd/xfMIFnREq6ktYRt 3pg39LDXSC15LiJsDCgA4SG5sTBsDQv5HjITFtS8OzWpf8lQIDAQAB oAAwDQYJKoZgeorgeEBQADgYEAV/sb0tY37LvAg2XYLgLz5uKtqLWm kRJJI14pJGCrl+UVBxH/WM9VOVef2TE6lItJX24HWABb0hijsjan25 jSH5y0J0z9ZGWDJESE+3lmnopy60DkQkpcQT6v/q+7fzqRn/GziAPj Vx6huc/Sw+XMN4sVMZ6uKbrunLQQ0Vcks=-----END NEW CERTIFICATE REQUEST-----
2-18
2. Send the CSR text to the certificate authority. Several certificate authority vendors allow you to copy and paste the CSR text to their Web sites. The certificate authority typically generates a signed certificate in the format filename.cer. 3. Obtain the signed certificate from the certificate authority vendor. Several certificate authority vendors allow you to download the signed certificate from their Web sites. 4. Use Internet Services Manager to install the signed certificate.
2-19
Certificate Information (Apache and Tomcat Only)
You must provide the following information for the self-signed certificate created during the installation.
Note
Commas in any of the fields will be converted to spaces. Commas are used internally as delimiters by the certificate generation tool.
Field
keystore password
Description
This is the password used to protect the keystore and the certificate. It must be at least eight characters for the Apache Web server or six characters for the Tomcat standalone Web server. This is the name of the Web server, as it will be specified in the URL for accessing the PATROL Central Web site. The Web browser will compare the server domain name in the certificate to the URL used to access the Web server. If they differ, a warning will be displayed by the browser. These fields identify your organization. These fields identify the location of your organization.
server domain name
organization name and organizational unit name city, state, and country
2-20
Note
If you choose the Tomcat standalone Web server, due to limitations of the Web server implementation, the keystore password is stored unencrypted in the Tomcat server.xml file. Although this file can be read by only the Web server account, it is vulnerable if that account is compromised. Although BMC Software is not aware of such a vulnerability at present, we recommend that a non-sensitive password be used. BMC Software also recommends that you do not add sensitive certificates to the Tomcat keystore in the event that the password is discovered. The site-specific, self-signed certificate deployed during the product installation is usually sufficient.
RTserver
You must specify which RTserver to use. The format is protocol:hostname:port. The default is tcp:localhost:2059. You can use this default only if PATROL Central will use an RTserver on the local computer with the default port. For more information, see PATROL Console Server and RTserver Getting Started. For information about changing this value after installation, see Appendix B, Modifying Initialization Settings After Installation.
2-21
Required Information for a Custom Installation

If you select a Custom installation, you need to know all of the information for a Typical installation, plus the information in this section.
PATROL Security Information
You must set the level of security that you want to use. For more information, see the PATROL Security User Guide.
Note
The security level must match the security level of other PATROL components that you will be communicating with.
Tomcat Shutdown Port
The Tomcat servlet container listens for termination messages on the shutdown port. The port does not need to be visible outside the Web server; however, no other applications can use this port. The default port is 8005. For information about changing this value after installation, see Changing Web Server Ports after Installation on page 5-16 and Appendix B, Modifying Initialization Settings After Installation.
Apache-Jakarta Protocol Version 13 Port (IIS and Apache Only)
The Apache-Jakarta Protocol version 13 port is used by the IIS and Apache Web servers to communicate with the Tomcat servlet container. The port does not need to be visible outside the Web server; however, no other applications can use this port. The default port is 8009. For information about changing this value after installation, see Changing Web Server Ports after Installation on page 5-16 and Appendix B, Modifying Initialization Settings After Installation.
2-22
IIS HTTPS Ports (IIS Only)
This is the port that IIS is configured to use for secure communications. The default HTTPS port is 443. For information about changing this value after installation, see Changing Web Server Ports after Installation on page 5-16 and Appendix B, Modifying Initialization Settings After Installation.
Web Server HTTP and HTTPS Ports (Apache and Tomcat Only)
The Web server uses these ports for unsecure (HTTP) and secure (HTTPS) communications. If there will be multiple Web servers on the computer, make sure that each Web server uses a different set of ports. If a port is already in use when you run the install, the install will prompt you to specify a different port. The default HTTP port is 80. The default HTTPS port is 443. If you do not use the default HTTP port, users will have to include the port number in the URL for accessing the PATROL Central Web site. For example, if the Web server myserver is using port 8080, view the URL http://myserver:8080. For information about changing the HTTPS port after installation, see Changing Web Server Ports after Installation on page 5-16 and Appendix B, Modifying Initialization Settings After Installation.
IIS Web Site Instance (IIS Only)
IIS can support multiple Web site instances. The install retrieves the list of Web site instances from the IIS metabase. Each Web site instance is identified by both its name and its instance number. You must select which instance you want to use with PATROL Central. The default is the default Web site.
2-23
Trimming Apache Web Server Log Files (Apache Only)
The Apache Web server log files can grow considerably over the course of time. For example, each image load request is logged. The installation installs a utility that truncates the log files for the Apache Web server while the Web server is running, so that they do not grow without limit. This utility can be run periodically as a job in the root crontab. You can choose the maximum log file size. The same maximum size is applied to each log file. The default value is 20MB. You can choose whether the installer automatically adds the job to the root crontab. If you chose to not add the job to the root crontab, you can add the job manually and adjust the job schedule. For more information, see Apache Web Server Logs on page 7-26.
Installation Worksheets
Use these worksheets to record information for your installation.
Complete both the general worksheet and the worksheet for your Web
server.
Worksheet
General Worksheet Worksheet for IIS Web Server Worksheet for Apache Web Server Worksheet for Tomcat Standalone Web Server
Page
2-25 2-26 2-27 2-28
Tip
You can use the completed worksheets to determine if you need to use a Custom installation. For more information, see Choosing a Typical or Custom Installation on page 2-14.
2-24
General Worksheet Computer Name:

Which console modules do you want to install? Which Web Server do you want to use? PATROL Central Operator PATROL Central Administration IIS (Windows) Apache (Unix) Tomcat standalone (Windows or Unix)
Directories
Where do you want to install BMC Software products? The default is C:\Program Files\BMC Software (Windows) or /opt/bmc (Unix).
Security Information
What security level do you want to use? The default is basic.a basic level 1 level 2 level 3 level 4

What is the name of the PATROL Console Server to use to authenticate users for PATROL Central? (Typically, the name of the PATROL Console Server is the hostname of the computer where the PATROL Console Server is installed.)
Tomcat Servlet Container Information

Shutdown port for the Tomcat servlet container The default is 8005. a
RTserver Information
What is the name of the RTserver computer to use? The default is localhost. What is the port number for the RTserver to use? The default is 2059.
a
If you do not use the default, you must use a custom install.
2-25
Worksheet for IIS Web Server IIS Web Server

Do you have a certificate? (required) IIS Web Site Instance
IIS Ports
AJP 13 port The default is 8009.a HTTPS port The default is 443.a
a
2-26
Worksheet for Apache Web Server Apache Ports

HTTP port The default is 80. HTTPS port The default is 443. AJP 13 port The default is 8009.a
Apache User Name and Group

You will need the root login name and password. Apache HTTPD User Name **** The HTTPD user name and group must be the same as the user name and group you are using to install PATROL Central Operator Web Edition.
Apache HTTPD Group
Apache Log Maintenance

Maximum size for log files. The default is 20 MB.a Automatically add job to crontab? The default is yes.a yes / no
Apache Certificate Information

keystore password server domain name organization name organizational unit name city state country
a
****
2-27
Worksheet for Tomcat Standalone Web Server Tomcat User Name and Group
You will need the root login name and password (Unix only). Tomcat user name **** The Tomcat user name and group must be the same as the user name and group you are using to install PATROL Central Operator Web Edition.
Tomcat user group (Unix only)
Tomcat Ports
HTTP port The default is 80.a HTTPS port The default is 443.a
Tomcat Certificate Information

keystore password server domain name organization name organizational unit name city state country
a
****
2-28
Upgrading Versus First-Time Installation

When upgrading from a previous version of PATROL Central Web Edition to version 7.2.10, the installation utility will automatically detect a previous install of PWC and migrate the following files. Startup.cfg Internal datastore
When upgrading PATROL Central Operator Web Edition to version 7.2.10, the following user preferences are migrated to the new version. Additionally, if you choose a Custom installation, you have the opportunity to change port numbers and names used for the PATROL Console Server, RTserver, and Web servers.
Location of Information
My Home => Preferences
Information Migrated
First Name Last Name E-mail Initial Tab Applet Style Default Initial Tab Default Refresh Interval Default Message Timeout Max Number of Sessions
My Home => Admin Options => General
My Home => Admin Options => Console Server My Home => Admin Options => Managed system Query
Default Console Server Default Management Profile Maximum Number of Rows Allowed Query Results Lifespan
2-29
Migrating a Customized PATROL Central Sub-directory
When you installed PATROL Central Operator Web Edition version 7.1.0x, the installation allowed you to customize the name of the PATROL Central sub-directory. When you upgrade to PATROL Central Operator Web Edition version 7.1.10, the installation will prompt you for the name of the customized PATROL Central sub-directory. PATROL Central Operator will create a backup of this directory and migrate the data to the version 7.1.10 directory name. For PATROL Central Operator Web Edition version 7.1.10, the PATROL Central sub-directory name is WebCentral on Windows, and webcentral on Unix. You cannot customize the PATROL Central sub-directory name in version 7.1.10.
To Upgrade PATROL Central Web Edition to Version 7.2.10 Step 1 Step 2
Ensure that all users are logged off of PATROL Central Web Edition. Shut down the Web server by stopping the PATROL Central Web Edition service. For more information, see Starting and Stopping PATROL Central Operator Web Edition on page 5-11.
Step 3
If the Web server, PATROL Console Server, and RTserver are installed in the same %BMC_ROOT% or $BMC_ROOT directory, you must shutdown the Console Server and RTserver. For more information, see Starting and Stopping the RTserver on page 5-3, and Starting and Stopping the PATROL Console Server on page 5-7.
Step 4
Run the installation program.
2-30
For more information see, Installing PATROL Central Operator on Windows on page 2-32, or Installing PATROL Central Operator on Unix on page 2-46.
Note
During installation of PATROL Central Operator, you may see references to aborted packages or components in the installation utility status screen and the log files. This happens when the installation utility encounters components that have already been installed on the target computer. The message does not indicate a problem with the product installation. Entries in the log files will indicate that the package or component was skipped because it was already installed.
2-31
Installing PATROL Central Operator on Windows Summary:

This task describes how to install PATROL Central Operator, including all the components listed under Installable Components on page 2-9 on Windows. If you install only some of the components, you might be asked for less configuration information. If you install other programs from the same CD at the same time, you will be asked for additional configuration information for those programs. For more information on how to run the installation program, see the PATROL Installation Reference Manual. This task applies to both a Typical and Custom installation; however, the screen captures reflect the Typical installation. If you choose a Custom installation, the screens will vary slightly.
Before You Begin
The following requirements must be met before you can run the installation: The computer must meet the requirements stated in System Requirements on page 2-10. If a PATROL Console Server, RTserver, or PATROL Agent are on the computer, they are stopped. For more information, see Starting and Stopping Related Programs on page 5-2. You are logged on using an account in the Administrators group so that you can install software and modify user rights. All of the ports to be used by the Web server are available.
BMC Software recommends having PATROL Console Server and RTserver installed in your environment (not necessarily the same computer) before installing PATROL Central Operator.
2-32
The installation procedures for the IIS and Tomcat Web servers are slightly different.
Procedure
To Install PATROL Central Operator on Windows with IIS To Install PATROL Central Operator on Windows with the Tomcat Standalone Web Server
Page
2-33 2-43
To Install PATROL Central Operator on Windows with IIS Step 1
Insert the product CD into the CD drive and run setup.exe. Then click Next to start the installation program. Review the license agreement. If you accept it, choose Accept. Then click Next.
Step 2
2-33
Step 3
On the Select Installation Option page, choose Install products on this computer now. Then click Next. For more information about creating an installable image, see the PATROL Installation Reference Manual.
2-34
Step 4
On the Select Type of Installation page, choose Typical or Custom as the installation type. Then click Next. For more information about the installation type, see Choosing a Typical or Custom Installation on page 2-14.
2-35
Step 5
On the Specify Installation Directory page, specify the location where you want to install BMC products. Then click Next. For more information about the installation directory, see Installation Directory on page 2-15.
2-36
Step 6
On the Select System Roles page, select Common Services as the system role. Then click Next. If you do not select a role or if you select all roles, all products will be displayed on the Select Products and Components to Install page.
2-37
Step 7
On the Select Products and Components to Install page, expand the PATROL Central - Web Edition folder and then select PATROL Central Console for Web and all Console Modules. If you chose the Custom installation, you can select individual components instead. For more information, see Installable Components on page 2-9.
Step 8
If you chose the Custom installation, on the Select Level of Security screen, select the level of security that you want to use. Then click Next. For more information, see PATROL Security Information on page 2-22.
2-38
Step 9
If you chose the Custom installation and selected Advanced security options, complete the security information. Then click Next. For more information, see PATROL Security Information on page 2-22.
Step 10
On the Select Web Server for Windows Platforms page, select Microsoft IIS. Then click Next.
Step 11
If you are upgrading from PATROL Central Operator Web Edition version 7.1.0x, and you customized the name of the PATROL Central sub-directory when you installed 7.1.0x, the installation will prompt you for the name of the sub-directory. Enter the name of the PATROL Central sub-directory and click Next. For more information, see Migrating a Customized PATROL Central Sub-directory on page 2-30.
2-39
Step 12
On the Configure PATROL Central - Web Edition page, specify the name of the PATROL Console Server to be used as the security server. For more information, see the PATROL Console Server on page 2-16. Then click Next.
2-40
Step 13
If you chose the Custom installation, specify the shutdown port number of the Tomcat servlet container. Also select whether you want to start the Tomcat servlet container as a service (listed as a Windows service named PATROL Central-WebEdition) after the installation. Then click Next.
Warning
If you do not select to start the Tomcat servlet container as a service, the PATROL Central-WebEdition service will not appear in the list of services located in the Windows Services dialog.
Note
The Tomcat servlet container is installed and used with PATROL Central, regardless of the Web server that you choose. This servlet container runs Java code for PATROL Central. For more information about the shutdown port number, see Tomcat Shutdown Port on page 2-22.
Step 14
If you chose the Custom installation, specify the AJP 13 port and the port that is used by Microsoft IIS for HTTPS connections. Then choose the the Web site instance to use. Then click Next. For more information, see Apache-Jakarta Protocol Version 13 Port (IIS and Apache Only) on page 2-22, IIS HTTPS Ports (IIS Only) on page 2-23, and IIS Web Site Instance (IIS Only) on page 2-23.
2-41
Step 15
On the RTSERVERS Variable Properties page, specify the RTserver to use. For more information, see RTserver on page 2-21.
Step 16
On the Review Selections and Install screen, review your product selections and configuration information. Click Back to make changes or click Start Install to complete the installation. Watch the Installation Status page to verify that the installation process completes successfully. When the installation is complete, click Next. On the SUCCESS page, if you want to review the installation log file, click View Log File. When you are done, click Finish.
Step 17
Step 18
2-42
To Install PATROL Central Operator on Windows with the Tomcat Standalone Web Server Note
Step 1
Complete Step 1 through Step 9 of To Install PATROL Central Operator on Windows with IIS on page 2-33. On the Select Web Server for Windows Platforms page, select Jakarta Tomcat v4.1.29. Then click Next.
Step 2
Step 3
Continue with Step 11 on page 2-39 of To Install PATROL Central Operator on Unix with Apache through Step 13 on page 2-41.
2-43
Step 4
On the Configure PATROL Central - Web Edition for Tomcat Standalone page, specify the Tomcat user name. If you chose the Custom installation, also specify the port numbers for HTTP and HTTPS connections. Then click Next. The Tomcat user name be the same as the user name you are using to install PATROL Central Operator Web Edition. For more information, see Web Server User Name and Group (Apache and Tomcat Only) on page 2-17 and Web Server HTTP and HTTPS Ports (Apache and Tomcat Only) on page 2-23.
2-44
Step 5
On the Configure PATROL Central - Web Edition Tomcat Certificate page, specify the self-signed certificate information. Then click Next. For more information, see Certificate Information (Apache and Tomcat Only) on page 2-20.
Step 6
Continue with Step 15 on page 2-42 of To Install PATROL Central Operator on Windows with IIS to the end of that procedure.
2-45
Installing PATROL Central Operator on Unix Summary:

This task describes how to install PATROL Central Operator, including all the components listed under Installable Components on page 2-9 on Unix. This task assumes that you are installing all components listed under Installable Components on page 2-9. If you install only some of the components, you might be asked for less configuration information. If you install other programs from the same CD at the same time, you will be asked for additional configuration information for those programs. For more information on how to run the installation program, see the PATROL Installation Reference Manual. This task applies to both a Typical and Custom installation; however, the screen captures reflect the Typical installation. If you choose a Custom installation, the screens will vary slightly.
Before You Begin
The following requirements must be met before you can run the installation: The computer must meet the requirements stated in System Requirements on page 2-10. You are logged on using the Web server account. For more information, see Web Server User Name and Group (Apache and Tomcat Only) on page 2-17. All of the ports to be used by the Web server are available. If a PATROL Console Server, RTserver, or PATROL Agent are on the computer, they are stopped. For more information, see Starting and Stopping Related Programs on page 5-2.
2-46
BMC Software recommends having PATROL Console Server and RTserver installed in your environment (not necessarily the same computer) before installing PATROL Central Operator. The installation procedures for the Apache and Tomcat Web servers are slightly different.
Procedure
To Install PATROL Central Operator on Unix with Apache To Install PATROL Central Operator on Unix with the Tomcat Standalone Web Server
Page
2-47 2-59
To Install PATROL Central Operator on Unix with Apache Step 1
Insert the product CD into the CD drive, mount to the CD drive, and run setup.sh. Then click Next to start the installation program. Review the license agreement. If you accept it, choose Accept. Then click Next.
Step 2
2-47
Step 3
On the Select Installation Option page, choose Install products on this computer now. Then click Next. For more information about creating an installable image, see the PATROL Installation Reference Manual.
2-48
Step 4
On the Select Type of Installation page, choose Typical or Custom as the installation type. Then click Next. For more information about the different types, see Choosing a Typical or Custom Installation on page 2-14.
2-49
Step 5
On the Specify Installation Directory page, specify the location where you want to install BMC Software products. Then click Next. For more information about the installation directory, see Installation Directory on page 2-15.
2-50
Step 6
On the Select System Roles page, select Common Services as the system role. Then click Next. If you do not select a role or if you select all roles, all products will be displayed on the Select Products and Components to Install page.
2-51
Step 7
On the Select Products and Components to Install page, expand the PATROL Central - Web Edition folder and then select PATROL Central Console for Web and all Console Modules. If you chose the Custom installation, you can select individual components instead. For more information, see Installable Components on page 2-9.
Step 8
If you chose the Custom installation, on the Select Level of Security screen, select the level of security that you want to use. Then click Next. For more information, see PATROL Security Information on page 2-22.
Step 9
If you chose the Custom installation and selected Advanced security options, complete the security information. Then click Next. For more information, see PATROL Security Information on page 2-22.
2-52
Step 10
If you are upgrading from PATROL Central Operator Web Edition version 7.1.0x, and you customized the name of the PATROL Central sub-directory when you installed 7.1.0x, the installation will prompt you for the name of the sub-directory. Enter the name of the PATROL Central sub-directory and click Next. For more information, see Migrating a Customized PATROL Central Sub-directory on page 2-30.
Step 11
On the Select Web Server for Unix Platforms page, choose Apache v1.3.29 as the Web server. Then click Next.
2-53
Step 12
On the Provide the System Root Account Properties page, type the Root login name and password. Then click Next.
Note
If you chose the Custom installation, the pages for the Root login name and the PATROL Console Server are reversed. For more information, see Root Login and Password (Unix only) on page 2-16.
2-54
Step 13
On the Configure PATROL Central - Web Edition page, specify the name of the PATROL Console Server to be used as the security server. Then click Next. For more information about the installation directory, see PATROL Console Server on page 2-16.
Step 14
If you chose the Custom installation, specify the shutdown port number on which the Tomcat servlet container will listen for termination messages. For more information, see Tomcat Shutdown Port on page 2-22.
2-55
Step 15
On the Apache HTTP Server Parameters page, specify the port numbers for HTTP and HTTPS connections, and the Apache user name and group. Then click Next. The HTTPD user name and group are used to run the HTTPD child daemons and to protect the files. The HTTPD user name and group must be the same as the user name and group you are using to install PATROL Central Operator Web Edition. For more information, see Web Server User Name and Group (Apache and Tomcat Only) on page 2-17 and Web Server HTTP and HTTPS Ports (Apache and Tomcat Only) on page 2-23.
Step 16
If you chose the Custom installation, specify if you want to automatically trim Apache log files and the maximum log file size. Then click Next. For more information, see Trimming Apache Web Server Log Files (Apache Only) on page 2-24.
2-56
Step 17
If you chose the Custom installation, specify the AJP 13 port. Then click Next. For more information, see Apache-Jakarta Protocol Version 13 Port (IIS and Apache Only) on page 2-22.
Step 18
On the Configure Apache Certificate page, specify the self-signed certificate information. Then click Next. For more information, see Certificate Information (Apache and Tomcat Only) on page 2-20.
2-57
Step 19
On the RTSERVERS Variable Properties page, specify the RTserver to use. Then click Next. For more information, see RTserver on page 2-21.
Step 20
On the Review Selections and Install page, review your product selections and configuration information. Click Back to make changes or click Start Install to complete the installation. Watch the Installation Status page to verify that the installation process completes successfully. When the installation is complete, click Next. On the SUCCESS page, if you want to review the installation log file, click View Log File. When you are done, click Finish.
Step 21
Step 22
2-58
To Install PATROL Central Operator on Unix with the Tomcat Standalone Web Server Note
Step 1
Complete Step 1 through Step 10 of To Install PATROL Central Operator on Unix with Apache on page 2-47. On the Select Web Server for Unix Platforms page, choose Jakarta Tomcat v4.1.29. Then click Next.
Step 2
Step 3
Continue with Step 12 on page 2-54 of To Install PATROL Central Operator on Unix with Apache through Step 14 on page 2-55.
2-59
Step 4
On the Configure PATROL Central - Web Edition for Tomcat Standalone page, specify the Tomcat user name and group. If you chose the Custom installation, also specify the port numbers for HTTP and HTTPS connections. Then click Next. The Tomcat user name and group must be the same as the user name and group you are using to install PATROL Central Operator Web Edition. For more information, see Web Server User Name and Group (Apache and Tomcat Only) on page 2-17 and Web Server HTTP and HTTPS Ports (Apache and Tomcat Only) on page 2-23.
2-60
Step 5
On the Configure PATROL Central - Web Edition Tomcat Certificate page, specify the self-signed certificate information. Then click Next. For more information, see Certificate Information (Apache and Tomcat Only) on page 2-20.
Step 6
Continue with Step 19 on page 2-58 of To Install PATROL Central Operator on Unix with Apache to the end of that procedure.
2-61
Directory Structure
The following table describes the directories used by PATROL Central.
Directory
$BMC_ROOT
Description
This directory is where BMC Software products are installed. The $BMC_ROOT environment variable is shared by all PATROL Central components that are installed on the same computer. This directory contains common components that are shared by multiple PATROL 7.x products, such as security files. This directory contains information about which components and products are installed. This directory contains files for uninstalling components and products. This directory is where PATROL Central is installed. This directory is where the Tomcat servlet container (and Tomcat Web server) are installed. This directory contains binary files. This directory contains Tomcat log files. This directory contains configuration files. This directory contains configuration files. This directory contains PATROL Central Web Edition log files.
$BMC_ROOT\common
$BMC_ROOT\Install $BMC_ROOT\Uninstall $BMC_ROOT\WebCentral $BMC_ROOT\WebCentral\jakarta-tomcat $BMC_ROOT\WebCentral\jakarta-tomcat\bin $BMC_ROOT\WebCentral\jakarta-tomcat\logs $BMC_ROOT\WebCentral\jakarta-tomcat\ webapps\patrol\WEB-INF $BMC_ROOT\WebCentral\jakarta-tomcat\conf $BMC_ROOT\WebCentral\jakarta-tomcat\ webapps\patrol\WEB-INF\log
Note
These directories refer to the webcentral sub-directory of $BMC_ROOT. This directory is WebCentral on Windows, and webcentral on Unix. For more information see, Installation Directory on page 2-15.
2-62
Backing Up and Restoring PATROL Central and Console Modules

PATROL Central and the PATROL Central Operator and PATROL Central Administration console modules maintain preferences and administrative settings in a datastore. To backup the datastore, back up the following files in the
$BMC_ROOT/webcentral/jakarta-tomcat/webapps/patrol/WEB-INF
directory:
wc.backup wc.data wc.properties wc.script
The PATROL Central Operator and PATROL Central Administration console modules also store data on the PATROL Console Server. For information about the PATROL Console Server, see the PATROL Console Server and RTserver Getting Started.
2-63
To restore PATROL Central and the PATROL Central Operator and PATROL Central Administration console modules, reinstall them, and replace the backed-up versions of the datastore files.
Warning
When restoring PATROL Central and the PATROL Central Operator and PATROL Central Administration console modules, reinstall all of the console modules that were originally installed, and only those console modules. If you reinstall a different set of console modules, and then restore the datastore files, the PATROL Central Web page will not display the correct tabs. You can install or uninstall console modules after restoring the datastore files.
Tip
To make reinstalling easier, record the answers to installation questions on the installation worksheets. See Installation Worksheets on page 2-24. Also record any changes made to the startup configuration file. See Appendix B, Modifying Initialization Settings After Installation.

Before you can monitor and manage with PATROL Central Operator, other PATROL programs, computers, and the Web server must be running and configured to work with PATROL Central Operator. For more information, see Chapter 5, Configuring the PATROL Central Console Environment.
2-64
This chapter contains information for monitoring and managing your enterprise with Web Edition of PATROL Central Operator. This chapter contains information for both users and administrators of PATROL Central Operator. This chapter discusses the following topics: Web Browser Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Solaris OS Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 About the Java Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 About Installing or Accepting the Certificate . . . . . . . . . . . . . . . 3-6 Using Internet Explorer Version 6 on Windows 2003 . . . . . . . . 3-6 Setting Up Your Monitoring Environment . . . . . . . . . . . . . . . . . . . . 3-7 Accessing PATROL Central . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 The PATROL Central Console Infrastructure . . . . . . . . . . . . . . . 3-9 Accessing PATROL Central Operator . . . . . . . . . . . . . . . . . . . . . 3-11 About Your Management Profile . . . . . . . . . . . . . . . . . . . . . . . . 3-12 Connecting to a PATROL Console Server and Selecting a Management Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14 Adding Managed Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18 Loading PATROL KMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21 Where to Go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
3-1
Web Browser Requirements

You do not need to install any PATROL components on client computers. Users access PATROL Central and its console modules through a Web browser on the client computer. The following table lists the required Web browsers.
Platform
Red Hat Linux 7.1 Red Hat Linux 7.2 Red Hat Linux 7.3 Red Hat Enterprise Linux AS 2.1 Solaris 7 Solaris 8 Solaris 9 Windows NT 4 Enterprise Edition Windows NT 4 Server Windows 2000 Server Windows 2000 Advanced Server Windows 2000 Datacenter Server Windows 2000 Professional Windows 2000 XP Windows 2003 Standard Server Windows 2003 Enterprise Server Windows 2003 Datacenter Server Windows 2003 Web Server
Web Browser
Netscape 7.0 PATROL Central Operator was certified using Netscape 7.02 and JRE 1.4.1_02. Netscape 7.0 PATROL Central Operator was certified using Netscape 7.0 and JRE 1.4.1_02. Internet Explorer 5.5, 6.0 Netscape 7.0, 7.1 PATROL Central Operator was certified using JRE 1.4.1_02.
Internet Explorer 6.0 PATROL Central Operator was certified using JRE 1.4.1_02.
The Web browser also must have at least Java Plugin (JRE) version 1.4.1_02 installed on the client computer. PATROL Central Operator was certified using JRE version 1.4.1_02. See About the Java Plugin on page 3-3 for more information. Using versions other than those listed in the Web Browser Requirements table, may cause problems in PATROL Central Operator.
3-2
Solaris OS Patches
The latest patches for Solaris must also be installed, including the J2SE patch cluster for your version of Solaris. These patches can be retrieved from the Solaris maintenance Web site at http://sunsolve.sun.com.
Warning
The patches are necessary to address multiple problems that can range from subtle usage problems to crashes.
About the Java Plugin

PATROL Central requires at least Java Plugin (JRE) version 1.4.1_02 installed on the client computer. You can change the JRE version, but using versions other than those listed in the Web Browser Requirements table on page 3-2 may cause problems in PATROL Central Operator. The Java Plugin is used to implement dynamic client-side features such as live state updates and charts.
About Installing the Java Plugin
The Java Plugin must be installed on the client computer in order to use PATROL Central. On Internet Explorer, if the Java Plugin is not already installed on the client computer when you first access the PATROL Central Web site, PATROL Central will attempt to automatically download JRE version 1.4.1_02 from the Web server and install it. If it cannot be automatically downloaded, a page with a link for downloading it from the Web server is displayed.
3-3
On Unix, if the Java Plugin is not installed, a page with a link for downloading JRE version 1.4.1_02 from the Web server is displayed.
Tip
If you must manually install the Java Plugin, click the link to download the Java Plugin and follow the instructions on the screen to ensure that you install the appropriate version for PATROL Central.
Avoiding Conflicts with Other Desktop Applications
Some of your desktop applications might use a different version of the Java Plugin from the version used by PATROL Central, which can cause problems if each application does not use its corresponding version of the Java Plugin. For example, if an existing application uses an older version of the Java Plugin, you might experience problems with that application after you install the Java Plugin for PATROL Central. Similarly, if you later install an application that uses a different version of the Java Plugin from PATROL Central, you might experience problems with PATROL Central.
Avoiding Conflicts When Using Internet Explorer
To avoid these problems when using Internet Explorer, perform the following steps:
Step 1 Step 2 Step 3 Step 4 Step 5
From the Internet Explorer menu, choose Tools => Internet Options. Click the Advanced tab. Scroll to the Java (Sun) section. Clear the Use Java 2 v1.4.1_02 for <applet> (requires restart) check box. Click OK.
3-4
Avoiding Display Problems When Using Netscape
To avoid these problems when using Netscape, perform the following steps:
To fix the problem on Windows: Step 1 Step 2
Close all browser windows. Open the Windows Control Panel by selecting Start => Settings = > Control Panel. Double-click the Java Plug-in icon to open the Java Control Panel. From the Advanced tab, add the following line to the list of Java Runtime Parameters:
-Dsun.java2.ddoffscreen=false
Step 3 Step 4
Step 5 Step 6
Select Apply, and Close the Java Console. Restart the Netscape browser.
To fix the problem on Unix:
Step 1 Step 2
Change to the JRE_HOME/bin directory. Type the following command to load the Java Plugin control panel.
./ControlPanel
Step 3
From the Advanced tab, add the following line to the list of Java Runtime Parameters:
-Dsun.java2.ddoffscreen=false
Step 4 Step 5
Select Apply, and Close the Java Console. Restart the Netscape browser.
3-5
About Installing or Accepting the Certificate

Internet Explorer and Netscape contain a list of prominent certificate authorities. If the certificate on the Web server is not signed by one of these certificate authorities, or another certificate authority known to the Web browser on the client computer, the Web browser will notify you when you access the PATROL Central Web page. For example, if the Web server uses the default self-signed certificate on Apache, the Web browser will notify you. You must accept the certificate in order to use PATROL Central. You can accept the certificate for all sessions by installing the certificate or you can choose to accept it for just the current session. If you install the certificate, you will not be prompted to accept the certificate again. How you accept or install the certificate depends on the Web browser.
Using Internet Explorer Version 6 on Windows 2003

If you are using IE 6 on a Windows 2003 machine, after you enter the PATROL Central Operator URL, IE will display a blank web page. This is caused by Windows 2003 applying a high security level by default. For more information, see The PATROL Central Web Page is Blank on Internet Explorer on page 7-18.
3-6
Setting Up Your Monitoring Environment

To begin monitoring your environment with PATROL Central Operator, you must complete the following process: 1. Start and log on to the PATROL Central console infrastructure. 2. Connect to the PATROL Console Server and select or create a management profile. 3. Add the managed systems that you want to monitor. 4. Load the PATROL KMs that you want to monitor.
Tip
If you currently use the PATROL Console for Windows or the PATROL Console for Unix, see Chapter 6, Using the PATROL 3.x and PATROL 7.x Consoles for a list of differences between the classic consoles and PATROL Central Operator.
3-7
Accessing PATROL Central Summary:

This task describes how to access PATROL Central by using your Web browser.
To Access PATROL Central Step 1 Step 2
Start your Web browser application. In the Address or Location field, enter the following URL, where hostname is typically the name of the computer on which the Web server for PATROL Central is running.
http://hostname/patrol
If the Web server is not using the default port for HTTP, include the port number in the URL. For example, if the Web server myserver is using port 8080, view the URL http://myserver:8080/patrol. If the Java Plugin is not installed on the client computer, see About the Java Plugin on page 3-3 for more information. If the Web browser notifies you that it does not recognize the certificate for the Web server, see About Installing or Accepting the Certificate on page 3-6 for more information. You are prompted to log on to your security server.
Step 3
Type your user name and password for the security server and click OK. The home page for PATROL Central is displayed. See Figure 3-1 on page 3-10.
3-8
The PATROL Central Console Infrastructure

The interface provided by the Web Edition of the PATROL Central is composed of the major areas in the following table:
Area
navigation area
Description
The navigation area is located at the top of the PATROL Central interface. The navigation area is composed of the console module tabs, subtabs, and toolbar items. For each console module installed, one or more tabs, representing an area of functionality, are added to the navigation area. The list or tree view area is located on the left side of the PATROL Central interface. This area may display a list or tree view of objects. The results area is typically located on the right side of the PATROL Central interface. The results area displays information as you browse the tabs or select objects from the list or tree view area. The status area is located on the lower right corner of the PATROL Central interface. The status area provides information about your connection to PATROL Console Servers, RTservers, and system messages from PATROL Central Operator, as well as other console modules.
list or tree view area
results area
status area
3-9
Figure 3-1 shows the default home page for PATROL Central.
Figure 3-1 The PATROL Central Home Page
Navigation Area
Results Area
List or Tree View Area
Status Area
3-10
Accessing PATROL Central Operator Summary:

Before You Begin
This task describes how to access PATROL Central Operator.
You must have accessed PATROL Central and logged on to your security server. See page 3-8.
To Access PATROL Central Operator
In the navigation area, click the Operator tab.

The PATROL Central Operator General Tasks page is displayed.
Figure 3-2 The PATROL Central Operator General Tasks Page
3-11
If this is the first time that you have accessed PATROL Central Operator, the Open Management Profile wizard is displayed. The wizard will help you to connect to a PATROL Console Server, and to choose an existing or set up a new management profile. See Connecting to a PATROL Console Server and Selecting a Management Profile on page 3-14. The next time you access PATROL Central Operator, your last management profile will automatically be opened. At any time, you can navigate from within PATROL Central Operator back to the General Tasks page by clicking the General Tasks icon in the navigation area.
About Your Management Profile

PATROL Central Operator stores the following information in your management profile: the managed systems you have added the PATROL KMs you have loaded your arrangement of objects in the hierarchy event filters managed system queries user-created objects (folders, charts, custom views, shortcuts to objects)
PATROL Central Operator automatically saves changes to your management profile as you make them. You do not need to manually save changes to your management profile.
3-12
Because management profiles are stored on the PATROL Console Server, you can access your management profile from any computer running PATROL Central Operator by connecting to the same PATROL Console Server.
Note
If you use the PATROL Console for Windows, the PATROL Console for Unix, or both, a management profile contains information similar to a desktop file. For more information, see Chapter 6, Using the PATROL 3.x and PATROL 7.x Consoles.
3-13
Connecting to a PATROL Console Server and Selecting a Management Profile Summary:

This task describes how to run the Open Management Profile wizard to connect to a PATROL Console Server and select a management profile. The first time that you access PATROL Central Operator, the Open Management Profile wizard is displayed for you to specify which PATROL Console Server and management profile you want to use. The next time that you start PATROL Central Operator, it will automatically connect to the last PATROL Console Server and management profile that you used. You can also change PATROL Console Servers or management profiles at any time.
Before You Begin
You must have performed the following tasks. 1. Accessed PATROL Central. See page 3-8. 2. Accessed the PATROL Central Operator General Tasks page. See page 3-11.
3-14
To Run the Open Management Profile Wizard Step 1
On the PATROL Central Operator General Tasks page, click Open Management Profile. The Console Server Service Name page of the Open Management Profile wizard is displayed.
3-15
Step 2
From the Service Name drop-down list, choose the PATROL Console Server to use. Then click Next. The Management Profile Name page of the Open Management Profile wizard is displayed.
Step 3
3-16
Step 4
Perform one of the following actions: Type a name for a new management profile and click Next. Select an existing management profile and click Next.
Note
If you select an existing management profile that is currently opened by another user in read-write mode, you can choose to open it as read-only. If you open it as read-only, you will not be able to make any changes, such as adding managed systems or loading KMs. For more information about read-only management profiles, see the PATROL Central Operator Web Edition online Help.
Step 5
Click Finish. PATROL Central Operator connects to the PATROL Console Server and opens the management profile.
3-17
Adding Managed Systems Summary:

This task describes how to add managed systems for monitoring by using the Add Managed Systems wizard. After you connect to a PATROL Console Server, you must specify which managed systems (computers running the PATROL Agent software) you want to monitor. You can also add new managed systems at any time.
Before You Begin
You must have performed the following tasks. 1. Accessed PATROL Central. See page 3-8. 2. Accessed the PATROL Central Operator General Tasks page. See page 3-11. 3. Connected to the PATROL Console Server and select a management profile. See page 3-14.
3-18
To Add Managed Systems Step 1
On the PATROL Central Operator General Tasks page, click Add Managed Systems. The Selecting Managed Systems page of the Add Managed Systems wizard is displayed.
Tip
To select multiple managed systems, hold down the Ctrl key, and click each item you want to select. To select a range of managed systems, click the first one, then hold down the Shift key as you click the last one in the range. To select all managed systems, press Ctrl+a.
3-19
Step 2
From the list of discovered systems, choose the systems that you want to monitor. Then click Next.
Note
Depending on how user accounts are set up on the PATROL Console Server and the individual managed systems, you might be prompted for a username and password for some managed systems. For more information, see Setting Up User Accounts and Groups on page 4-4. A confirmation page is displayed.
Step 3
Click Finish to close the wizard.
The managed systems are displayed in the tree view and added to your management profile.
3-20
Loading PATROL KMs Summary:

This task describes how to load PATROL KMs by using the Load Knowledge Module(s) wizard. After you add managed systems, you must specify which PATROL KMs you want to load for those managed systems. You can also load additional PATROL KMs at any time.
Before You Begin
You must have performed the following tasks. 1. Accessed PATROL Central. See page 3-8. 2. Accessed the PATROL Central Operator General Tasks page. See page 3-11. 3. Connected to the PATROL Console Server and select a management profile. See page 3-14. 4. Added the managed systems that you want to monitor. See page 3-18.
3-21
To Load KM(s) Step 1
On the PATROL Central Operator General Tasks page, click Load Knowledge Modules. The Selecting Managed Systems page of the Loading Knowledge Modules wizard is displayed.
Step 2
From the list of available managed systems, select the managed systems on which to load PATROL KMs. Then click Next.
3-22
Step 3
The list of available KMs is displayed.
Step 4
Select the PATROL KMs that you want to load. Then click Next. A confirmation message is displayed.
Step 5
Click Finish to close the wizard. Any PATROL KMs that were not already loaded on their respective managed systems are loaded. The PATROL KMs are displayed in the tree view area and added to your management profile.
3-23
Where to Go From Here

monitoring with PATROL Central Operator using the PATROL Central console infrastructure administering users how PATROL works using both PATROL 3.x and PATROL Central Operator, or moving from a PATROL 3.x console
See...
PATROL Central Operator Web Edition online Help PATROL Central Web Edition online Help PATROL Central Administration Web Edition online Help PATROL Fundamentals online Help Chapter 6, Using the PATROL 3.x and PATROL 7.x Consoles
3-24
Administering Users of PATROL Central Operator
The PATROL 7.x architecture requires that you set up operating system user accounts and groups for the PATROL Console Server and managed systems. This chapter contains the following topics: About Accounts and Groups in the PATROL Environment . . . . . . . 4-2 Setting Up User Accounts and Groups . . . . . . . . . . . . . . . . . . . . . . . 4-4 User Accounts and Groups on PATROL Central Web Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 User Accounts and Groups on the PATROL Console Server . . . 4-4 User Accounts on Managed Systems . . . . . . . . . . . . . . . . . . . . . 4-6 General Guidelines for Setting Up User Accounts and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 Administering Aliases and Impersonation . . . . . . . . . . . . . . . . . . . . 4-8 About the User Authentication Process . . . . . . . . . . . . . . . . . . . 4-9 Example Scenario for A Single Account for All Managed Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 Example Scenario for Different Accounts According to Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 Example Scenario for A Single Account for All Managed Systems But One . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 Administering Privileges and Rights . . . . . . . . . . . . . . . . . . . . . . . . . 4-14 About Assigning Privileges and Rights . . . . . . . . . . . . . . . . . . . 4-14 Predefined Groups on the PATROL Console Server . . . . . . . . . . 4-15 Privileges Used in PATROL Central Operator . . . . . . . . . . . . . . 4-15
4-1
Rights Used in PATROL Central Operator . . . . . . . . . . . . . . . . .4-17 How Predefined Privileges and Rights Determine Group Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-18 Using the Predefined Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-19 Special Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-20 Example Scenario for Granting Privileges . . . . . . . . . . . . . . . . .4-20 Example Scenario for Adding Rights for Management Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-23 About PATROL Central Administration . . . . . . . . . . . . . . . . . . . . . .4-27 Starting PATROL Central Administration . . . . . . . . . . . . . . . . . .4-28
About Accounts and Groups in the PATROL Environment

The PATROL 7.x architecture uses operating system groups and users on the PATROL Console Server and managed systems for the following: establishing user's identity throughout PATROL (authentication and impersonation) For more information, see Administering Aliases and Impersonation on page 4-8. controlling which functionality users can access (privileges) and which objects users can access (rights) For more information, see Administering Privileges and Rights on page 4-14.
4-2
The following table shows how user accounts and groups are used on different computers.
Component
PATROL Central Web Edition
User Accounts
User accounts on a specified PATROL Console Server are used to control who can log on to PATROL Central - Web Edition and who can perform administration functions. User accounts on the PATROL Console Server are used to control privileges and rights and to identify users. User accounts on managed systems are used to identify users.
Groups
Groups on a specified PATROL Console Server are used to control who can log on to PATROL Central Web Edition and who can perform administration functions. Groups on the PATROL Console Server are used to control privileges and rights.
Managed System
not used
4-3
Setting Up User Accounts and Groups

The PATROL 7.x architecture requires that user accounts and groups be set up for the PATROL Console Servers and managed systems.
User Accounts and Groups on PATROL Central Web Edition

PATROL Central Web Edition uses a PATROL Console Server as a security server to authenticate users during the initial log in. The name of this server is assigned during installation. Only users who have accounts known to that PATROL Console Server can use PATROL Central Web Edition or any of its console modules. Users inherit the privileges and rights of the groups to which they belong, including nested groups. For example, to log on to PATROL Central Web Edition, users must be a member of a group that includes the Log on privilege. Additionally, to administer PATROL Central Web Edition with access to the Admin Options tab, users must be a member of a group that includes the Administer PATROL Central Web Edition privilege. For more information, see Privileges Used in PATROL Central Operator on page 4-15
User Accounts and Groups on the PATROL Console Server

The PATROL 7.x architecture uses operating system user accounts and groups on the PATROL Console Server to control privileges and rights for PATROL. Accounts can be local accounts or domain accounts. A privilege allows a user to access specific console functionality. A right allows a user to access specific PATROL objects. A PATROL user cannot access functionality or objects without the appropriate privileges and rights.
4-4
Users inherit the privileges and rights of the groups to which they belong, including nested groups. Usually it is easier to add users to the appropriate groups in the operating system than to administer privileges and rights for users directly. The following table lists the groups with predefined privileges and rights. If these groups do not already exist, they are created when you install the PATROL Console Server.
Group
patop patpop patwatch patadm patscadm
Description
standard PATROL operators power operators operators who can only watch console objects standard PATROL administrators PATROL administrators who can configure security
Step 1
Add the account for each user of PATROL Central to the appropriate group on the default PATROL Console Server computer. If you are using additional PATROL Console Servers with PATROL Central Operator, also add the account for each user to the appropriate group on those PATROL Console Servers.
Tip
Step 2
Only the privileges and rights on the relevant PATROL Console Server are used. For example, a user who is a member of the patscadm group on only one PATROL Console Server can configure security on only that PATROL Console Server. When a user connects to the PATROL Console Server from a console, the user logs on with an operating system account. The PATROL Console Server uses the operating system account to identify the user, the groups that the user belongs to, and the PATROL privileges and rights that the user has. You set up user accounts and groups in the operating system for the PATROL Console Server. You change privileges and rights of groups or individual users by using PATROL Central Administration. For more information, see About PATROL Central Administration on page 4-27.
4-5
User Accounts on Managed Systems

The PATROL 7.x architecture uses operating system accounts on each managed system and uses an impersonation table in the PATROL Console Server to control access to each managed system. Users can access a managed system only in the following situations: The user logs on to the PATROL Console Server with a domain account that is also known to the managed system. The user logs on to the PATROL Console Server with a local account, and the managed system has an account with an identical user name and password. The impersonation table in the PATROL Console Server is set up to provide an alias for the user to a user account on the managed system. The user has an account on the managed system and enters the username and password when adding the managed system.
You set up user accounts in the operating system for each computer. You set up the impersonation table in the PATROL Console Server with PATROL Central Administration. For more information, see About PATROL Central Administration on page 4-27.
General Guidelines for Setting Up User Accounts and Groups

You can use various strategies for setting up user accounts and groups on the PATROL Console Server and managed systems. Use the following questions as guidelines for setting up user accounts and groups: Do you want to use local accounts or domain accounts? If you use domain accounts that are known to both the PATROL Console Server and managed systems, you do not have to use the impersonation table. If you use local accounts for managed systems, you might have to create aliases to those accounts in the impersonation table in the PATROL Console Server.
4-6
Do you want to create multiple accounts in the operating system for each managed system? If you want multiple users to share the same account on a managed system, you can create aliases to that account in the impersonation table in the PATROL Console Server.
Do you want users to be able to access managed systems that they do not have accounts on? If so, you will have to set up user accounts on the managed systems and then create aliases to them in the impersonation table in the PATROL Console Server.
The following process describes one method of setting up user accounts and groups: 1. In the operating system of the PATROL Console Server, create an account for each user and add each account to the appropriate group or groups listed in the table under Administering Privileges and Rights on page 4-14. This user account can be a local account or a domain account. 2. In the operating system of each managed system, create one or more operating system accounts for use by PATROL. 3. (Optional) In PATROL Central Administration, set up the impersonation table to provide alias accounts on the PATROL Console Server to accounts on the managed systems.
4-7
If you do not set up the impersonation table, you will have to manually enter a username and password for each managed system as you add it and each time you log back in and reconnect.
Tip
If you use multiple PATROL Console Servers, set up the impersonation table on each PATROL Console Server separately. Only the impersonation table on the corresponding PATROL Console Server is used. For example, suppose a user logs on to PATROL Central with an account on the PATROL Console Server used by PATROL Central, then, in PATROL Central Operator, opens a management profile on a different PATROL Console Server. When the user tries to access a managed system in the management profile, the impersonation table on only the second PATROL Console Server is used.
Administering Aliases and Impersonation

The PATROL 7.x architecture uses operating system accounts on each managed system and an impersonation table in the PATROL Console Server to control access to each managed system. Accounts can be local accounts or domain accounts. Users can access a managed system only in the following situations: The user logs on to the PATROL Console Server with a domain account that is also known to the managed system. The user logs on to the PATROL Console Server with a local account, and the managed system has an account with an identical user name and password. The impersonation table in the PATROL Console Server is set up to provide an alias for the user to a user account on the managed system. The user has an account on the managed system and enters the username and password when connecting to the managed system.
4-8
You set up user accounts in the operating system for the managed system. You set up user accounts and groups in the operating system for the PATROL Console Server. You set up the impersonation table in the PATROL Console Server with PATROL Central Administration. For more information, see the PATROL Central Administration online Help.
About the User Authentication Process

The process of establishing a user's identity to PATROL is called authentication. Each PATROL program that you access in PATROL's layered architecture must authenticate your identity. For example, when you use PATROL Central Operator, both the PATROL Console Server and the PATROL Agent must authenticate your identity. A PATROL program, such as PATROL Console Server or PATROL Agent, can only authenticate users with valid operating system user accounts that it recognizes. In order to allow a user to access PATROL Agents that do not recognize the user's account, the PATROL Console Server provides PATROL Agents with account information on behalf of the user. If a PATROL Agent does not recognize the original account of the user, the PATROL Console Server consults an impersonation table that maps users to alias accounts that are recognized by PATROL Agents. The PATROL Console Server then provides the PATROL Agent with the alias account that is configured for the user. For example, the authentication process for a user of PATROL Central Operator is as follows: 1. First, the user logs on to the PATROL Console Server, providing an account known to the PATROL Console Server. The PATROL Console Server authenticates this account. This account is the console account. 2. The PATROL Console Server provides the PATROL Agent with the user's account. If the PATROL Agent recognizes the user's account, the authentication process is successfully completed.
4-9
3. If the PATROL Agent does not recognize the console account, the PATROL Console Server consults its impersonation table for an alias account. 4. If there is an alias account, the PATROL Console Server provides it to the PATROL Agent. If the PATROL Agent recognizes the alias account, the authentication process is successfully completed. 5. If there is no alias account, or if the PATROL Agent does not recognize the alias account, the user is prompted for an account to use. 6. If the PATROL Agent recognizes the account the user enters, the authentication process is successfully completed. Otherwise, the user cannot access the PATROL Agent.
Example Scenario for A Single Account for All Managed Systems

This example describes a solution to granting all PATROL users access to all managed systems, when those managed systems use the same username and password.
Note
This example scenario provides the general tasks. For step instructions for a specific task, see the PATROL Central Administration online Help.
Scenario
You have several managed systems that all have a local account with the same username and password. You want all users to be able to access all of the managed systems.
4-10
Solution
1. Create a single alias for the local account.

Alias
patrol_all
Username
patrol
Password
****
2. Add a single row in the impersonation table, using wildcards for the user and the service name.
User
*
Service Type
Managed System
Service Name
*
Alias
patrol_all
Note
You can still control which users and groups can access specific managed systems by setting rights for those managed system.
Example Scenario for Different Accounts According to Location

This example describes a solution to granting all PATROL users access to all managed systems, when different managed systems have different usernames and passwords, according to location.
Note
Scenario
You have several managed systems in two locations. You name the managed systems according to a naming convention that identifies the location of the managed system.
4-11
All of the managed systems have a local account with the same user name. However, each location uses a different password. You want all users to be able to access all of the managed systems.
Solution
1. Create an alias for each username and password combination.

Alias
patrol_location_1 patrol_location_2
Username
patrol patrol
Password
**** ****
2. Add a row in the impersonation table for each location, using pattern matching on the service name.
User
* *
Service Type
Managed System Managed System
Service Name
*loc1* *loc2*
Alias
patrol_location_1 patrol_location_2
Note
You can still control which users and groups can access specific managed systems by setting rights for those managed system.
Example Scenario for A Single Account for All Managed Systems But One
This example describes a solution to granting all PATROL users access to all managed systems, when all managed systems have the same username and password, except one.
Note
4-12
Scenario
You have several managed systems. All of the managed systems have a local account with the same user name and password, except for one special system. You want only one special user to be able to access the special system. You want all users, including the special user, to be able to access all of the other managed systems.
Solution
1. Create two aliases: one for the account on the special system, and another for the shared username and password.
Alias
patrol_special patrol_regular
Username
patrolspecial patrol
Password
**** ****
2. Add two rows to the impersonation table: one for the special managed system, and another for all the other managed systems.
User
SpecialUser *
Service Type
Managed System Managed System
Service Name
SpecialAgent *
Alias
patrol_special patrol_regular
Make sure that the row for the special user is before the row for all users. Otherwise, the PATROL Console Server will find the alias patrol_regular, and never use the patrol_special alias.
Note
Instead of controlling access to the special managed system in the impersonation table, you can apply the alias to all users and control which users and groups can access the special managed system by setting rights for it.
4-13
Administering Privileges and Rights

The PATROL 7.x architecture uses operating system user accounts and groups on the PATROL Console Server to control privileges and rights for PATROL. A privilege allows a user to access specific console functionality. A right allows a user to access specific PATROL objects. It is the combination of privileges and rights that determine what any user can accomplish or access in the PATROL world. A PATROL user cannot access functionality or objects without both the appropriate privileges and rights.
About Assigning Privileges and Rights

There are three basic methods of assigning privileges and rights to a user: In the operating system for the PATROL Console Server, put the user into an existing group that already has the desired privileges and rights. This method is usually the easiest method. The existing group can be one of the predefined groups (see Predefined Groups on the PATROL Console Server on page 4-15) or a group that has been previously assigned specific privileges and rights. Use PATROL Central Administration to assign the desired privileges and rights to a new or existing group. Then, in the operating system for the PATROL Console Server, put the user into that group. Use PATROL Central Administration to assign the user the desired privileges and rights directly.
Note
Accounts can be local accounts or domain accounts. Users inherit the privileges and rights of the groups to which they belong, including nested groups.
4-14
For more information about using PATROL Central Administration, see the PATROL Central Administration online Help.
Predefined Groups on the PATROL Console Server

The PATROL Console Server installation process includes the creation of the operating system groups listed in the table below. These predefined groups are initially assigned PATROL privileges and rights according to a typical set of roles that apply to PATROL users. These groups are created as a convenience for PATROL security administrators.
Table 4-1 Default PATROL Groups on the PATROL Console Server
Group
patop patpop patwatch patadm patscadm
Description
standard PATROL operators power operators operators who can only watch console objects standard PATROL administrators PATROL administrators who can configure security
Privileges Used in PATROL Central Operator

Privileges are used to protect console functionality. The following table lists the privileges relating to PATROL Central Operator that are assigned to the predefined PATROL groups during installation of the PATROL Console Server. Note that other privileges that do not relate to PATROL Central Operator might also be assigned to the PATROL groups.
4-15
Assigned Privilege
Acknowledge event Add, delete, connect and disconnect managed systems Administer PATROL Central - Web Edition Clear parameter history Close event Create and destroy management profile Create, modify and delete state-change actions Create, modify and destroy event filters Create, modify and destroy managed system query filters Create, modify and destroy user-defined objects Delete event Display event manager window Display managed system query window Execute admin KM commands Execute commands in system output window Execute KM commands Force closing management profile that is in use Load and unload KM packages Log on Override attributes of KM objects Read contents of system output window Shutdowna Update, suspend and resume parameter executions
a
x x x x x x x x x x x x x x x x x x x x x x x
x x
x x
x x x x x x x x x x x x x x x x x x
x x x x x x x x x x x x x
This privilege applies to version 7.2.30 of PATROL Console Server, but not to version 7.2.00.
4-16
patscadm
patwatch
patadm
patpop
patop
Rights Used in PATROL Central Operator

Rights are used to control access to objects. PATROL security administrators allow or deny rights in access control lists (ACLs) for objects. By default, there is only one ACL created at installation of the PATROL Console Server. This ACL is used to restrict access to management profiles used in PATROL Central Operator. It exists on the PATROL\Management Profiles folder, as seen in PATROL Central Administration. The following table lists how rights are assigned in this ACL.
Rights Group
patadm patpop patop patwatch patscadm Allow
Read
Allow Allow
Write
Allow
4-17
How Predefined Privileges and Rights Determine Group Roles

The predefined rights and privileges affect the default abilities of the members of the predefined PATROL groups in the following ways.
Group
patadm
Access to Management Profiles

Members of this group can create, view, modify, and delete management profiles created by any user. When choosing a management profile in PATROL Central Operator, a patadm member can see all the management profiles stored on the PATROL Console Server.
Comments
Users in this group are the PATROL administrators. These users have privileges to do everything, from executing admin KM commands to shutting down the PATROL Console Server. However, these users cannot use PATROL Central Administration unless they are also members of patscadm or are the default PATROL user (See Special Users on page 4-20). Users in this group are capable of doing almost as much as a PATROL administrator. In general, anyone who needs to manage all management profiles or solve problems that do not require shutting down the PATROL Console Server or running admin KM commands belongs in this group. For example, a DBA who not only needs to monitor databases, but also would like to run commands from the system output window and set up appropriate state change actions should be placed in this group. Users in this group are ordinary operators with no administrative abilities. They can create and use their own management profiles, event filters, and managed system queries. However, they cannot modify parameter execution, close events, modify state change actions, or execute commands in the system output window.
patpop
Members of this group can create, view, modify, and delete their own management profiles. They can also open, in read only mode, management profiles created by other users. When choosing a management profile in PATROL Central Operator, a patpop member can see all the management profiles stored on the PATROL Console Server.
patop
Members of this group can create, view, modify, and delete their own management profiles. However, they cannot access management profiles created by other users. When choosing a management profile in PATROL Central Operator, a patop member can see only the management profiles that he or she created.
4-18
Group
patwatch
Access to Management Profiles

Members of this group cannot create, open, modify, or delete any management profiles. When prompted to choose a management profile in PATROL Central Operator, a patwatch member will not see any management profiles on the PATROL Console Server, except those for which access has been specifically granted.
Comments
Users in this group are highly restricted. They cannot even open a management profile until specifically granted access by a PATROL security administrator using PATROL Central Administration. Once they do have access to a management profile, they can only view objects and events. For example, suppose a member of patadm sets up a management profile for a patwatch member to view. A member of patscadm would have to use PATROL Central Administration to create an ACL on the management profile that grants read access to the patwatch group. Users in the patscadm group have only the rights and privileges to use PATROL Central Administration. Although users could assign the group additional rights and privileges, it is better practices to add the users to other groups, such as patadm, instead.
patscadm
Members of this group cannot create, modify, or delete any management profiles. However, they can open, in read only mode, any management profile created by any user. When choosing a management profile in PATROL Central Operator, a patadm member can see all the management profiles stored on the PATROL Console Server.
Using the Predefined Groups

If the roles set up by the predefined groups are sufficient for the PATROL security administrators, they can simply add the operating system users to the predefined groups. In this scenario, users can belong to multiple PATROL groups; however, they must belong to at least one of the predefined groups to use PATROL.
4-19
If the roles set up by the predefined groups are not sufficient for the PATROL security administrators, they can modify or delete the privileges and rights associated with these groups as they see fit. They can also assign privileges and rights to other operating system groups or users as needed. Individuals must still have the appropriate privileges and rights to use PATROL, either by belonging to a group with the privileges and rights, or by having the privileges and rights directly. For more information on assigning privileges and rights, see the PATROL Central Administration Help.
Special Users
There are two exceptions that the PATROL Console Server makes when determining who has what privileges and rights. The user who creates an object, such as a management profile, is considered the owner of the object and always has full rights to it, regardless of any ACLs that indicate differently. (However, the owner of an object still needs the appropriate privileges to perform a specific action on the object.) The PATROL default account, which is specified when the PATROL Console Server is installed, always has all privileges and rights. Even if this account is removed from all groups and all privileges and rights are revoked from it in PATROL Central Administration, it still has full access.
Example Scenario for Granting Privileges

This example describes several different solutions to granting additional privileges to users.
Note
4-20
Scenario
Most of the PATROL operators are in the patop group, since the predefined privilege and rights for that group are the closest match for what they need to do. However, they also need to have full control over PATROL events, but members of patop cannot close or delete events by default.
Solution 1: Modifying the patop Group
The PATROL security administrator uses PATROL Central Administration to grant the required extra privileges to the patop group.
Solution 2: Granting Privileges Individually
The PATROL security administrator uses PATROL Central Administration to grant the required extra privileges to each individual user that needs them. This method is not recommended in organizations with many users or high turnover. If any users are added to or removed from patop in the future, the PATROL security administrator will also have to modify the privileges individually.
Solution 3: Replacing the patop Group
1. The PATROL security administrator creates a new group in the operating system, such as pateventops. 2. Then the PATROL security administrator uses PATROL Central Administration to assign this new group the same privileges and rights as the patop group, plus the additional event privileges. 3. Finally, the PATROL security administrator moves the users from the patop group to the new pateventops group in the operating system. 4. Since the patop group is no longer used, it can be removed.
4-21
Solution 4: Adding a New Group (Variation 1)
1. The PATROL security administrator creates a new group in the operating system, such as patevents. 2. Then the PATROL security administrator uses PATROL Central Administration to assign this new group only the additional event privileges. 3. Finally, the PATROL security administrator adds the users from the patop group to the new patevents group in the operating system, so that they are members of both groups. Because the users are members of both groups, they have all the necessary privileges. The privileges from both groups are additive. Note that users should not be members of only the patevents group, or they will not have the other necessary privileges and rights to use PATROL.
Solution 5: Adding a New Group (Variation 2)
1. The PATROL security administrator creates a new group in the operating system, such as pateventsops, and makes it a nested member of the patop group. 2. Then the PATROL security administrator uses PATROL Central Administration to assign this new group only the additional event privileges. 3. Finally, the PATROL security administrator moves the users from the patop group to the new pateventsops group in the operating system. Because the pateventsops group is a nested member of the patop group, its members have all the privileges and rights the patop group, as well as the additional event privileges. Users can be members of the pateventops group, without being members of the patop group directly. However, because the patop group is still used, it should not be removed.
4-22
Example Scenario for Adding Rights for Management Profiles

This example describes a solution to sharing different management profiles with different users.
Note
Scenario
An organization needs to monitor four computers. Two of them are database servers (DB1 and DB2), and two are mail servers (Mail1 and Mail2). There are a total of five users to monitor these systems:
User
John
Role for Database Servers

PATROL administrator & administrator for database servers Johns backup operator for database servers none none
Role for Mail Servers

PATROL administrator
Jill Jim Jane Jack
administrator for mail servers none operator for mail servers intern for mail servers
Adding Users to the Predefined Groups
After installation of the PATROL Console Server is complete, John decides that the predefined groups fit the roles for his users. He places the users in the predefined groups in the operating system as follows, based on their roles:
User
John Jill Jim
Groups
patadm, patscadm patpop, patscadm patop
4-23
User
Jane Jack
Groups
patop patwatch
Setting up and Sharing a Management Profile for the Database Servers
As the administrator for the database servers, John wants to set up a management profile for monitoring the database servers. As a member of patadm, John has the privileges and rights to set up a management profile. He uses PATROL Central Operator to create a management profile called Databases for the database servers. He adds the database servers (DB1 and DB2), loads the appropriate PATROL Knowledge Modules (KMs), and creates some custom views, event filters, and managed system queries. By default, the ACL on the PATROL/Management Profiles folder controls who has access to the Databases management profile, because the management profile does not have its own ACL. The management profile inherits the ACL of the PATROL/Management Profiles folder. According to that ACL, members of patpop and patscadm, such as Jill, can open the management profile in read-only mode. Members of patadm, and the owner John, have full access to it. No-one else has access to the management profile. John wants Jim to be able to open the management profile in read-only mode. (Although Jim could create his own management profile, John wants him to use the same one as everyone else.) John wants everyone else to maintain the same access that they currently have. In order to change the access to the management profile, John uses PATROL Central Administration to create an ACL for the Databases management profile. Creating an ACL for the Databases management profile means that the ACL on the PATROL/Management Profiles folder is no longer inherited. So, all rights for the Databases management profile must be specified in the ACL for the Databases management profile.
4-24
In the ACL for the Databases management profile, John duplicates the rights in the ACL on the PATROL/Management Profiles folder. Then John also allows Jim to have read access to the Databases management profile in the ACL. The following screen captures show the entries in the ACL for the group patadm and the user Jim. The following table summarizes who has access to the management profile and why.
User / Group
John (user) Jill (user) Jim (user) patadm (group) patpop (group) patscadm (group)
Access
full (read and write) read read full (read and write) read read
Reason
owner & membership in patadm membership in patpop group allowed in ACL allowed in ACL allowed in ACL allowed in ACL
Setting up and Sharing a Management Profile for the Mail Servers
As the administrator for the mail servers, Jill wants to set up a management profile for monitoring the mail servers. As a member of patpop, Jill has the privileges and rights to set up a management profile. She uses PATROL Central Operator to create a management profile called Mail for the mail servers. She adds the mail servers (Mail1 and Mail2), loads the appropriate PATROL Knowledge Modules (KMs), and creates some custom views, event filters, and managed system queries. As with the Databases management profile, by default, the Mail management profile inherits the ACL on the PATROL/Management Profiles folder. According to that ACL, members of patpop and patscadm can open the management profile in read-only mode. Members of patadm (such as John), and the owner Jill, have full access to it. No-one else has access to the management profile.
4-25
Jill wants Jane and the interns, such as Jack, in the patwatch group to be able to open the management profile in read-only mode. (Although Jane could create her own management profile, Jill wants her to use the same one as everyone else.) Jill wants everyone else to maintain the same access that they currently have. As John created an ACL for the Databases management profile, Jill uses PATROL Central Administration to create an ACL for the Mail management profile. In the ACL for the Mail management profile, Jill duplicates the rights in the ACL on the PATROL/Management Profiles folder. Then Jill also allows Jane and the patwatch group to have read access to the Mail management profile in the ACL. The following table summarizes who has access to the management profile and why.
User / Group
John (user) Jill (user) Jane (user) Jack (user) patadm (group) patpop (group) patwatch (group) patscadm (group)
Access
full (read and write) full (read and write) read read full (read and write) read read read
Reason
membership in patadm owner and membership in patpop group allowed in ACL membership in patwatch group allowed in ACL allowed in ACL allowed in ACL allowed in ACL
4-26
About PATROL Central Administration

PATROL Central Administration is a console module that works within the PATROL Central console infrastructure to control user access to PATROL. You use PATROL Central Administration in the following cases: You want to set up impersonation tables so that users do not have to enter account information for managed systems. You want to control privileges using groups other than the default groups, or the default privileges for those groups do not fit your needs. You want to change the access rights to individual PATROL objects. For example, you want to make a management profile available to more users, or you want to prevent users from accessing a specific
For more information, see the PATROL Central Administration online Help.
4-27
Starting PATROL Central Administration Summary:

This task describes how to start the Web Edition of PATROL Central Administration.
Before Your Begin
You must be a member of the patscadm group on the PATROL Console Server.
To Start PATROL Central Administration Step 1
If you have not yet started the PATROL Central console infrastructure, start it. See Starting and Stopping Related Programs on page 5-2.
Step 2
Click the Administration tab in the PATROL Central Web Edition banner area.
4-28
Configuring the PATROL Central Console Environment
This chapter provides information for PATROL administrators about configuring the PATROL environment for PATROL Central Operator and starting programs, including the Web server. This chapter discusses the following topics: Starting and Stopping Related Programs . . . . . . . . . . . . . . . . . . . . . . 5-2 Starting and Stopping the RTserver . . . . . . . . . . . . . . . . . . . . . . 5-3 Starting and Stopping the PATROL Agent . . . . . . . . . . . . . . . . . 5-5 Starting and Stopping the PATROL Console Server . . . . . . . . . . 5-7 Managing Services on Windows . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 Starting and Stopping PATROL Central Operator Web Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 Starting and Stopping PATROL Central Operator Web Edition on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12 Starting and Stopping PATROL Central Operator Web Edition on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 Verifying the Installation and Execution of the Web Server and Related Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15 Changing Web Server Ports after Installation . . . . . . . . . . . . . . . . . . 5-16 Changing Tomcat Standalone Web Server Ports . . . . . . . . . . . . 5-16 Changing Apache Web Server Ports . . . . . . . . . . . . . . . . . . . . . . 5-20 Changing IIS Web Server Ports . . . . . . . . . . . . . . . . . . . . . . . . . 5-25 Changing the Java Plug-in Version after Installation . . . . . . . . . . . . 5-30 Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
5-1
Starting and Stopping Related Programs

This section contains the basic steps for starting stopping the following related programs in the PATROL 7.x architecture and verifying that they are running: RTserver PATROL Agent PATROL Console Server
5-2
Starting and Stopping the RTserver Summary:

By default, the RTserver is started automatically as a service when you install it. However, you can start it manually. This task describes how to start the RTserver on both Windows and Unix and verify that it is running.
Note
For more information on starting the RTserver, see the PATROL Console Server and RTserver Getting Started.
Execution of RTserver on Windows
Start, stop, or verify the execution of the SmartSockets RTserver service.

For more information, see Managing Services on Windows on page 5-9.
To Manually Start the RTserver on Unix Step 1 Step 2
Change to the $BMC_ROOT/common/smartsockets directory. Enter the following command:

./start_rtserver.sh
To Verify That RTserver Is Running on Unix Step 1
Enter the following command:

ps -ef | grep rtserver
Step 2
Look for the rtserver process.
5-3
To Stop RTserver on Unix Step 1 Step 2
Change to the $BMC_ROOT/common/smartsockets directory. Enter the following command:

./stop_rtserver.sh
5-4
Starting and Stopping the PATROL Agent Summary:

By default, the PATROL Agent is started automatically as a service when you install it. However, you can start it manually. This task describes how to start the PATROL Agent on both Windows and Unix and verify that it is running.
Note
For more information on starting the PATROL Agent, see the PATROL Agent Reference Manual. You must enable the PATROL Agent 3.5 to communicate with the RTserver before you can use PATROL Central Operator to monitor it. For more information, see PATROL Console Server and RTserver Getting Started.
Execution of the PATROL Agent on Windows
Start, stop, or verify the execution of the PatrolAgent service.

For more information, see Managing Services on Windows on page 5-9.
To Manually Start the PATROL Agent on Unix Step 1 Step 2
Change to the $BMC_ROOT/patrol3 directory. Enter the following command:

./PatrolAgent -p port_number -rtServer protocol:hostname:port
5-5
To Verify That PATROL Agent Is Running on Unix Step 1
Enter the following command:

ps -ef | grep PatrolAgent
Step 2
Look for the PatrolAgent process.
To Stop the PATROL Agent on Unix Step 1
Type the following at the command line:

ps -ef | grep PatrolAgent
Step 2
Identify the process ID number of the PATROL Agent that you would like to shut down from the list. Type the following command, where process_ID_number is the process ID number of the PATROL Agent.
kill process_ID_number
Step 3
5-6
Starting and Stopping the PATROL Console Server Summary:

By default, the PATROL Console Server is started automatically as a service when you install it. However, you can start it manually. This task describes how to start PATROL Console Server on both Windows and Unix and verify that it is running.
Note
For more information on starting PATROL Console Server, see the PATROL Console Server and RTserver Getting Started.
Execution of the PATROL Console Server on Windows
Start, stop, or verify the execution of the PATROL Console Server

service. For more information, see Managing Services on Windows on page 5-9.
To Manually Start the PATROL Console Server on Unix Step 1 Step 2
Change to the $PATROL_ROOT directory. Enter the following command:

./start_cserver.sh
To Verify That PATROL Console Server Is Running on Unix Step 1
Enter the following:

ps -ef | grep cserver
Step 2
Look for the cserver process.
5-7
To Stop the PATROL Console Server on Unix Step 1 Step 2
Change to the $PATROL_ROOT directory. Enter the following command:

./stop_cserver.sh
5-8
Managing Services on Windows Summary:

On Windows, you use the Services dialog box to start, stop, and verify the execution of services.
To Open the Services Dialog Box on Windows NT Step 1 Step 2
For Windows NT, choose Start => Settings => Control Panel. Double-click the Services icon.
To Open the Services Dialog Box on Windows 2000 Step 1
For Windows 2000, choose Start => Settings => Control Panel => Administrative Tools. Double-click the Services icon.
Step 2
To Open the Services Dialog Box on Windows 2003 Step 1
For Windows 2003, choose Start => Control Panel => Administrative Tools. Double-click the Services icon.
Step 2 To Start a Service Step 1 Step 2 Step 3
Open the Services dialog box. Select the name of the service. For Windows NT, click Start. For Windows 2000 and Windows 2003, choose Action => Properties, then click Start.
5-9
To Verify that a Service is Running Step 1 Step 2 To Stop a Service Step 1 Step 2 Step 3
Open the Services dialog box. Look at the status of the service.
Open the Services dialog box. Select the name of the service. For Windows NT, click Stop. For Windows 2000 and Windows 2003, choose Action => Properties, then click Stop.
5-10
Starting and Stopping PATROL Central Operator Web Edition

This section contains the basic steps for starting, stopping, and verifying the execution of PATROL Central Operator Web Edition, the Web servers, and the Tomcat servlet container. The procedure to start and stop PATROL Central Operator Web Edition will depend on the following choices: the operating system on the computer where PATROL Central Operator Web Edition resides the web server with which you integrate PATROL Central Operator Web Edition if you are using Windows, whether you elected during installation to start the Tomcat servlet container as a service
Note
These procedures refer to the webcentral sub-directory of $BMC_ROOT. This directory is WebCentral on Windows, and webcentral on Unix. For more information see, Installation Directory on page 2-15.
5-11
Starting and Stopping PATROL Central Operator Web Edition on Windows

This task describes how to start PATROL Central Operator Web Edition on Windows when installed with the IIS or Tomcat standalone Web servers. When installing PATROL Central Operator Web Edition on Windows, you can elect to either start the Tomcat servlet container as a service, or to start it manually. When starting PATROL Central Web Edition, the Web server and the Tomcat servlet container are also started.
Starting and Stopping PATROL Central Operator Web Edition when Installed with IIS
This task describes how to start PATROL Central Operator Web Edition and the Tomcat servlet container. You must start the Tomcat servlet container and IIS separately.
To Start PATROL Central Operator if You Installed it as a Service
When you installed PATROL Central Operator, if you did not elect to start the Tomcat servlet container as a service, the PATROLCentral-WebEdition service will not appear in the list of services located in the Windows Services dialog. If the PATROLCentral-WebEdition service does not appear in the list of services, you can manually start the Tomcat servlet container.
Start, stop, or verify the execution of the PATROLCentral-WebEdition

5-12
To Manually Start PATROL Central Operator if You Installed it as a Command Line Application
Run %BMC_ROOT%\WebCentral\jakarta-tomcat\bin\pwcstart.bat.
To Start IIS
For information on starting, stopping, and verifying the execution of IIS,

see the documentation for that product.
Starting and Stopping PATROL Central Operator Web Edition when Installed with Tomcat Standalone on Windows
This task describes how to start PATROL Central Operator Web Edition, the Tomcat standalone Web server, and the Tomcat servlet container on Windows. You run the Tomcat standalone Web server and Tomcat servlet container together.
To Start PATROL Central Operator if You Installed it as a Service
When you installed PATROL Central Operator Web Edition, if you did not elect to start the Tomcat servlet container as a service, the PATROLCentral-WebEdition service will not appear in the list of services located in the Windows Services dialog. If the PATROLCentral-WebEdition service does not appear in the list of services, you can manually start the Tomcat servlet container.
Start, stop, or verify the execution of the PATROLCentral-WebEdition

To Manually Start PATROL Central Operator if You Installed it as a Command Line Application
Run %BMC_ROOT%\WebCentral\jakarta-tomcat\bin\pwcstart.bat.
5-13
Starting and Stopping PATROL Central Operator Web Edition on Unix

This task describes how to start PATROL Central Operator Web Edition on Unix when installed with the Apache or Tomcat standalone Web servers. Starting PATROL Central Operator Web Edition will also start the Web server, and the Tomcat servlet container.
Starting and Stopping PATROL Central Operator Web Edition when Installed with Apache or Tomcat Standalone
You control the execution of PATROL Central Operator Web Edition, the Apache or Tomcat standalone Web servers, and the Tomcat servlet container together. This task describes how to start and stop them.
To Start or Stop PATROL Central Operator on Unix
1. Change to the root user. 2. Change to the $BMC_ROOT/webcentral/bin directory. 3. Enter the ./pwcctl command, followed by the appropriate command line option from the table below.
Option
start stop status
Description
This option starts the Web server. This option stops the Web server. This option checks the status of the ports used by the Web server.
5-14
Verifying the Installation and Execution of the Web Server and Related Components
You can verify that the Web Server, Tomcat servlet container, RTserver, and PATROL Console Server are running by viewing the URLs in the table below. In the URL to view, hostname is the name of the Web site. Typically, this is the name of the computer on which the Web server for PATROL Central is running. If the Web server is not using the default port for HTTP, include the port number in the URL. For example, if the Web server myserver is using port 8080, view the URL http://myserver:8080.
What to Verify
Is the Web server running? Is HTTPS active for the Web server? Is the Tomcat servlet container running? Are the RTserver and PATROL Console Server available?
URL to View
http://hostname https://hostname http://hostname/patrol
Comments
If the default page for the Web server is displayed, the Web server is running. If the default page for the Web server is displayed, HTTPS is active. If the PATROL Central page is displayed, the Tomcat servlet container is running. Check the RTserver and PATROL Console Server status by clicking the expand button on the login dialog.
5-15
Changing Web Server Ports after Installation

There are many reasons why you may want to change the default port numbers after installation. You may want to change the Web server port numbers because of possible firewall restrictions or an existing web server may use the PATROL Central Operator default Web server ports. This section provides instructions to change the IIS, Apache and Tomcat standalone Web server port numbers after installation of PATROL Central Operator Web Edition. In all cases, the Tomcat servlet container is installed and used with the Web servers. For more information about the default Web server ports that are used by PATROL Central Operator Web Edition, see Required Information for a Custom Installation on page 2-22.
Before you Begin
Ensure all users all logged off of PATROL Central Web Edition Shut down PATROL Central Web Edition. For more information, see Starting and Stopping PATROL Central Operator Web Edition on page 5-11.
Changing Tomcat Standalone Web Server Ports

If you are using the Tomcat standalone Web server, then Tomcat, including the Tomcat servlet container, are installed and used with PATROL Central Operator Web Edition. For more information about running PATROL Central Operator with Tomcat standalone, see Considerations for Determining Which Web Server to Use on page 2-3. You must complete the following steps and change port numbers in the following files: shut down PATROL Central change the pwcctl file
5-16
change the server.xml file change the startup.cfg file restart PATROL Central
To Shut Down PATROL Central Web Edition
For instructions, see Starting and Stopping PATROL Central Operator

Web Edition on page 5-11.
To Change the pwcctl File
You must be logged in as the user who installed PATROL Central Web Edition. If you change the port number values in this file, make sure you change the value to match it in the other files listed in this procedure.
Step 1
Backup the pwcctl file, which is located in the following directory:

$BMC_ROOT/webcentral/jakarta-tomcat/bin/pwcctl
Step 2 Step 3
Open the pwcctl file. Change the HTTP_PORT value from the default port number value (shown as 80 using bold text in the following example) to the new port number. Change the HTTPS_PORT value (shown as 443 using bold text in the following example) to the new port number. Change the SHUTDOWN_PORT value (shown as 8005 using bold text in the following example) to the new port number.
Step 4
Step 5
HTTP_PORT=80 HTTPS_PORT=443 SHUTDOWN_PORT=8005
5-17
To Change the server.xml File
If you change the port number values in this file, make sure you change the value to match it in the other files listed in this procedure.
Step 1
Backup the server.xml file located in the following directory: $BMC_ROOT/webcentral/jakarta-tomcat/conf/server.xml
Step 2 Step 3
Open the server.xml file. Change the Shutdown value (shown as 8005 using bold text in the following example) from the default to the new port number.
<Server port="8005" shutdown="SHUTDOWN" debug="0"> ... ...
Step 4
Change the non-SSL HTTP Connector value (shown as 80 using bold text in the following example) to the new port number. Change the redirect port value (shown as 443 using bold text in the following example) from the default to the new port number.
Step 5
 <Connector className="org.apache.coyote.tomcat4.Coyote Connector" port="80" minProcessors="5" maxProcessors="75" enableLookups="true" redirectPort="443" acceptCount="100" debug="0" connectionTimeout="20000" useURIValidationHack="false" disableUploadTimeout="true"/>
5-18
Step 6
Change the SSL HTTP Connector value (shown as 443 using bold text in the following example) to the new port number.
 <Connector className="org.apache.coyote.tomcat4.Coyote Connector" port="443" minProcessors="5" maxProcessors="75" enableLookups="true" acceptCount="100" debug="0" scheme="https" secure="true" useURIValidationHack="false" disableUploadTimeout="true">
To Change the startup.cfg File
Step 1
Backup the startup.cfg file located in the following directory:

$BMC_ROOT/webcentral/jakarta-tomcat/webapps/patrol/WEB-INF/ startup.cfg
Step 2 Step 3
Open the startup.cfg file. Change the httpsPort value from the default port number value (shown as 443 using bold text in the following example) to the new port number.
# # # # # # #
HTTPS Port This is the port used for HTTPS by the web server, whether it be IIS, Apache, Tomcat standalone, or another server. The port is communicated to the browser so that it can use HTTPS for secure communication.
httpsPort=443
For more information about the startup.cfg file, see Modifying Initialization Settings After Installation on page B-1.
5-19
To Restart PATROL Central Web Edition

Changing Apache Web Server Ports

If you using the Apache Web server, both Apache and the Tomcat servlet container are installed and used with PATROL Central Operator Web Edition. For more information about running PATROL Central Operator with Apache, see Considerations for Determining Which Web Server to Use on page 2-3. You must complete the following steps and change port numbers in the following files: shut down PATROL Central change the pwcctl.sh file change the workers.properties file change the server.xml file change the startup.cfg file change the httpd.conf file restart PATROL Central

5-20
To Change the pwcctl File
You must be logged in as the user who installed PATROL Central Web Edition. If you change the port number values in this file, make sure you change the value to match it in the other files listed in this procedure.
Step 1
Backup the pwcctl file located in the following directory: $BMC_ROOT/webcentral/bin/pwcctl.sh
Step 2 Step 3
Open the pwcctl file. Change the HTTP_PORT value from the default port number value (shown as 80 using bold text in the following example) to the new port number. Change the HTTPS_PORT value (shown as 443 using bold text in the following example) to the new port number. Change the AJP13_PORT value (shown as 8009 using bold text in the following example) to the new port number. Change the SHUTDOWN_PORT value (shown as 8005 using bold text in the following example) to the new port number.
Step 4
Step 5
Step 6
HTTP_PORT=80 HTTPS_PORT=443 AJP13_PORT=8009 SHUTDOWN_PORT=8005
5-21
To Change the workers.properties File
Step 1
Backup the workers.properties file located in the following directory:

$BMC_ROOT/webcentral/jakarta-tomcat/conf/workers.properties
Step 2 Step 3
Open the workers.properties file. Change the worker.ajp13.port value (shown as 8009 using bold text in the following example) to the new port number.
# Defining a worker named ajp13 and of type ajp13 # Note that the name and the type do not have to # match. # worker.ajp13.port=8009
Step 1
Step 2 Step 3
5-22
Step 4
Change the AJP Connector value (shown using 8009 bold text in the following example) to the new port number.
 <Connector className="org.apache.ajp.tomcat4.Ajp13Conn ector" port="8009" minProcessors="5" maxProcessors="75" acceptCount="10" debug="0"/>
Step 1

$BMC_ROOT/webcentral/jakarta-tomcat/webapps/patrol/WEB-INF/ startup.cfg
Step 2 Step 3
# # # # # # #
httpsPort=443
5-23
To Change the httpd.conf File
Step 1
Backup the httpd.conf file located in the following directory:

$BMC_ROOT/common/apache/httpd/OS/conf/httpd.conf
Step 2 Step 3
Open the httpd.conf file. Change the HTTPD value (shown as 80 using bold text in the following example) from the default to the new port number.
# Port: The port to which the standalone server # listens. For ports < 1023, you will need httpd to # be run as root initially. # Port 80
Step 4
Change the SSL HTTP value (shown as 80 using bold text in the following example) to the new port number. Change the SSL HTTPS value (shown as 443 using bold text in the following example) to the new port number.
Step 5
## ## ## ##
SSL Support When we also provide SSL we have to listen to the standard HTTP port (see above) and to the HTTPS port
<IfDefine SSL> Listen 80 Listen 443 </IfDefine>
5-24
Step 6
Change the SSL VirtualHost _default value (shown as 443 using bold text in the following example) to the new port number.
## SSL Virtual Host Context <VirtualHost _default_:443>

Changing IIS Web Server Ports

If you using the IIS Web server, both IIS and the Tomcat servlet container are installed and used with PATROL Central Operator Web Edition. For more information about running PATROL Central Operator with IIS, see Considerations for Determining Which Web Server to Use on page 2-3. Use Internet Services Manager to change the port values in IIS. For information about changing the default web server ports in IIS, see the documentation for that product. You must complete the following steps and change port numbers in the following files: shut down PATROL Central change port numbers in IIS change the workers.properties file change the server.xml file change the startup.cfg file restart PATROL Central
5-25

To Change Port Numbers in IIS
Use Internet Services Manager to change the port values in IIS. For
information about changing the default web server ports in IIS, see the documentation for that product.
To Change the workers.properties File
Step 1
Backup the workers.properties file located in the following directory:

$BMC_ROOT/webcentral/jakarta-tomcat/conf/workers.properties
Step 2 Step 3
Open the workers.properties file. Change the worker.ajp13.port value (shown as 8009 using bold text in the following example) to the new port number.
# Defining a worker named ajp13 and of type ajp13 # Note that the name and the type do not have to # match. # worker.ajp13.port=8009
5-26
Step 1
Step 2 Step 3
Step 4
Change the non-SSL HTTP Connector value (shown as 80 using bold text in the following example) to the new port number. Change the redirect port value (shown as 443 using bold text in the following example) from the default to the new port number.
Step 5
 <Connector className="org.apache.coyote.tomcat4.Coyote Connector" port="80" minProcessors="5" maxProcessors="75" enableLookups="true" redirectPort="443" acceptCount="100" debug="0" connectionTimeout="20000" useURIValidationHack="false" disableUploadTimeout="true"/>
5-27
Step 6
Change the SSL HTTP Connector value (shown as 443 using bold text in the following example) to the new port number.
 <Connector className="org.apache.coyote.tomcat4.Coyote Connector" port="443" minProcessors="5" maxProcessors="75" enableLookups="true" acceptCount="100" debug="0" scheme="https" secure="true" useURIValidationHack="false" disableUploadTimeout="true">
Step 7
Change the AJP Connector value (shown using 8009 bold text in the following example) to the new port number.
 <Connector className="org.apache.ajp.tomcat4.Ajp13Conn ector" port="8009" minProcessors="5" maxProcessors="75" acceptCount="10" debug="0"/>
5-28
Step 1
$BMC_ROOT/webcentral/jakarta-tomcat/webapps/patrol/WEB-INF/ startup.cfg Step 2 Step 3
# # # # # # #
httpsPort=443

5-29
Changing the Java Plug-in Version after Installation

PATROL Central Operator Web Edition version 7.1.10 is installed and certified with JRE version 1.4.1_02, but is capable of supporting JRE 1.4.x. Multiple versions of the JRE can coexist on the same client computer. This task describes how to change the JRE on the client computer after installation. For more information, see About the Java Plugin on page 3-3.
Note
Using versions other than those listed in the Web Browser Requirements table on page 3-2, may cause problems in PATROL Central Operator.
Warning
You can change the JRE version on the client computer only. Do not change the JRE version on the computer where you have installed PATROL Central Web Edition.
To Change Java Plug-in Version on Windows Step 1
Download the desired version of the JRE from the following URL:
http://java.sun.com/j2se
Step 2
Download and follow the instructions provided on the JRE download page to install the new JRE. Close all browser windows. Open the Windows Control Panel by selecting Start => Settings = > Control Panel. Double-click the Java Plug-in icon to open the Java Control Panel. From the Advanced tab, select the desired JRE version from the Java Runtime Environment drop down list.
Step 3 Step 4
Step 5 Step 6
5-30
The default is the last JRE version installed.

Step 7
Select Apply, and Close the Java Console.
To Change Java Plug-in Version on RedHat Linux Step 1
Step 2
Download and follow the instructions provided on the JRE download page to install the new JRE. Execute the following commands.
chmod +x j2re-<version>-linux-i586.bin ./j2re-<version>-linux-i586.bin
Step 3
Step 4 Step 5 Step 6
Close all browser windows. Login as root and change the directory to NETSCAPE_HOME/plugins Check for either a link to the libjavaplugin_oji.so library or whether the library file exists in the plugins directory.
6.A
If a link to the libjavaplugin_oji.so library already exists in the directory, remove the link using the following command:
rm libjavaplugin_oji.so
6.A
If the libjavaplugin_oji.so library file resides in the plugins directory, back up the library using the following command:
MV libjavaplugin_oji.so bak_libjavaplugin_oji.so
Step 7
Create a soft link to the new plug-in using the following command:
ln -s <JRE>/plugin/i386/ns610-gcc32/libjavaplugin_oji.so libjavaplugin_oji.so
5-31
To Change Java Plug-in Version on Unix Step 1
Step 2
Download and follow the instructions provided on the JRE download page to install the new JRE. Execute the following commands:
chmod +x j2re-<version>-solaris*.sh ./j2re-<version>-solaris*.sh
Step 3
Close all browser windows. Login as root and change the directory to NETSCAPE_HOME/plugins Check for either a link to the libjavaplugin_oji.so library or whether the library file exists in the plugins directory.
6.A
If a link to the libjavaplugin_oji.so library already exists in the directory, remove the link using the following command:
rm libjavaplugin_oji.so
6.A
If the libjavaplugin_oji.so library file resides in the plugins directory, back up the library using the following command:
MV libjavaplugin_oji.so bak_libjavaplugin_oji.so
Step 7
Create a soft link to the new plug-in using the following command:
ln -s <JRE>/plugin/sparc/ns610/libjavaplugin_oji.so libjavaplugin_oji.so
5-32

monitoring and managing with PATROL Central Operator using both PATROL 3.x console and PATROL Central Operator, or moving from a PATROL 3.x console
See...
Chapter 3, Monitoring and Managing Your Enterprise with PATROL Central Operator Chapter 6, Using the PATROL 3.x and PATROL 7.x Consoles
5-33
5-34
Using the PATROL 3.x and PATROL 7.x Consoles 6

PATROL Central Operator is a console for the PATROL 7.x architecture. Consoles for the PATROL 3.x architecture include the PATROL Console for Windows and the PATROL Console for Unix. This chapter contains information for PATROL Central Operator users who are familiar with or will also use a PATROL 3.x console and discusses the following topics: Compatibility and Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 PATROL Agent Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 KM Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Developer Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Differences Between PATROL Console for Windows or PATROL Console for Unix and PATROL Central Operator . . . . . . . . . . . . . 6-3 Communications with Managed Systems . . . . . . . . . . . . . . . . . . 6-4 Session and Desktop Files Versus Management Profiles . . . . . . 6-4 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 User Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 User Names and Passwords for Managed Systems . . . . . . . . . . 6-6 Computer Name and Port Number Versus Managed System Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6 Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7 Customizations Versus Overrides . . . . . . . . . . . . . . . . . . . . . . . . 6-7 State Change Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7 KM Version Arbitration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8 Chart History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8 Location of Task Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9 KMs in the PATROL Object Namespace . . . . . . . . . . . . . . . . . . 6-9
Using the PATROL 3.x and PATROL 7.x Consoles
6-1
Running Menu Commands and InfoBox Commands . . . . . . . . .6-10 Migrating Console Information from PATROL Console for Windows or PATROL Console for Unix . . . . . . . . . . . . . . . . . . . . .6-10
Compatibility and Functionality

This section describes important facts that you need to know before moving from PATROL Console for Windows or PATROL Console for Unix (PATROL 3.x architecture), to PATROL Central Operator.
Tip
You can use both PATROL 3.x consoles and PATROL 7.x consoles in your PATROL environment.
PATROL Agent Compatibility

To use PATROL Central Operator, you must use the PATROL 7.x architecture, which requires PATROL Agent version 3.5 or later. PATROL Central Operator will not work with a PATROL Agent earlier than version 3.5.
KM Compatibility
A PATROL 7.x console is compatible with currently supported KMs. You can continue to use the same KMs that you used with a PATROL 3.x console. However, if a KM requires files (such as Help, icons or executables) on the PATROL Console Server or the console, features that use those files will not work until the files are installed in the appropriate locations. Local menu commands also are disabled in the Web Edition of PATROL Central Operator, unlike in Windows Edition.
6-2
Developer Functionality
The PATROL 7.x architecture currently has no console with KM developer functionality. In order to develop new KMs or change existing ones, you should continue using PATROL Console for Windows or PATROL Console for Unix.
Differences Between PATROL Console for Windows or PATROL Console for Unix and PATROL Central Operator
This section describes the primary differences between PATROL Console for Windows or PATROL Console for Unix (PATROL 3.x architecture) and PATROL Central Operator (PATROL 7.x architecture). Many of the differences come from differences between the PATROL 3.x and the PATROL 7.x architectures. For a description of the PATROL architecture, see the PATROL Fundamentals online Help.
Difference
Communications with Managed Systems Session and Desktop Files Versus Management Profiles Terminology User Administration User Names and Passwords for Managed Systems Computer Name and Port Number Versus Managed System Name Event Types Customizations Versus Overrides State Change Actions KM Version Arbitration Chart History Location of Task Icons
Page
6-4 6-4 6-5 6-5 6-6 6-6 6-7 6-7 6-7 6-8 6-8 6-9
6-3
Difference
KMs in the PATROL Object Namespace Running Menu Commands and InfoBox Commands
Page
6-9 6-10
Communications with Managed Systems

PATROL Console for Windows and PATROL Console for Unix communicate directly with managed systems. PATROL Central Operator uses an RTserver cloud and PATROL Console Server to communicate with managed systems.
Session and Desktop Files Versus Management Profiles

PATROL Console for Windows and PATROL Console for Unix store console information, such as which managed systems and KMs are loaded, in session and desktop files. These files are stored on the console computer and can be accessed from only that computer. PATROL Central Operator stores console information in a management profile on the PATROL Console Server. A management profile can be accessed from any installation of PATROL Central Operator with access to that PATROL Console Server. Also, changes to your management profile are saved automatically as you make them. You can use the Windows Edition of PATROL Central Operator to migrate a desktop file to a management profile. That management profile, in turn, can then be used with the Web Edition of PATROL Central Operator. For more information about migrating desktop files, see the PATROL Central Operator- Microsoft Windows Edition Getting Started.
6-4
Terminology
The following table lists terms that are different in PATROL 3.x and PATROL 7.x consoles.
PATROL Console for Windows and PATROL Console for Unix Term
agent, host
PATROL Central Operator Term

managed system
Comments
A managed system is a computer that is running the PATROL Agent software. This change corresponds to the change from agent to managed system. The alarm state in the PATROL 3.x architecture is the critical state in the PATROL 7.x architecture. However, the term alarm is still used when referring to undesirable situations without indicating a specific object state, as in alarm ranges, snoozing an alarm, or responding to an alarm.
agent query
managed system query
alarm (state)
critical (state)
User Administration
For PATROL Console for Windows and PATROL Console for Unix, a users access to functionality is controlled by the patrol.conf and ptrlroles.txt files and by the ptrldev and patroldev groups, as well as by the mode of the console (developer or operator). For PATROL Central Operator, a users access to functionality is controlled by privileges and rights set for groups and users in PATROL Central Administration.
6-5
User Names and Passwords for Managed Systems

For PATROL Console for Windows and PATROL Console for Unix, user names and passwords for managed systems are stored on the console computer in the desktop and session files. After you enter the account information once, you do not have to enter it again when you open that desktop or session. However, if you use a different console, you must re-enter the account information. For PATROL Central Operator, user names and passwords for managed systems are not stored in the management profile (the corresponding item for a desktop or session file). If you enter account information in PATROL Central Operator, it is not remembered the next time you open the management profile. However, an administrator can set up aliases and impersonations on the PATROL Console Server by using PATROL Central Administration. If the aliases and impersonations are set up correctly, you can open any management profile without being prompted for account information.
Computer Name and Port Number Versus Managed System Name

When specifying a managed system (computer) in PATROL Console for Windows and PATROL Console for Unix, you provide both a computer name and a port number separately. When specifying a managed system in PATROL Central Operator, you provide the managed system name, which is a combination of the computer name and the port number that the PATROL Agent uses. For example, if the computer name is starfish and the PATROL Agent is running on the default port of 3181, then the name of the managed system is starfish_3181. When adding a managed system to your management profile, you must specify the complete name of the managed system, including the computer name and the port number.
6-6
Event Types
The following table lists the event types in PATROL Console for Windows and PATROL Console for Unix and the equivalent event types in PATROL Central Operator.
PATROL Console for Windows and PATROL Console for Unix Event Type
info state change error warning alarm
PATROL Central Operator Event Type

info
warning critical
Customizations Versus Overrides

In PATROL Console for Windows and PATROL Console for Unix, changes that you make to an object, such as changes to the alarm ranges of a parameter, are called overrides. In PATROL Central Operator, these changes are called customizations. For more information, see the PATROL Agent Reference Manual.
State Change Actions

A state change action is a set of commands that are executed on the console (or PATROL Console Server) computer when an object changes state. In PATROL 3.x architecture, a state change action is stored as part of a KM and is executed on only the console computer. State change actions can be defined globally and locally at the managed system and application instance levels.
6-7
In PATROL 7.x architecture, state change actions are stored in the management profile. You must use the Windows Edition of PATROL Central Operator to define state change actions. When a management profile is open in the Web Edition of PATROL Central Operator, only state change actions that are defined to execute on the PATROL Console Server are executed. State change actions that are defined to execute on the console computer are ignored. For more information about state change actions, see the PATROL Central Operator Microsoft Windows Edition online Help.
KM Version Arbitration
In PATROL 3.x architecture, KMs are stored on both the managed system running the PATROL Agent and on the console computer. How the PATROL Agent and PATROL Console reconcile different versions of a single KM is called KM version arbitration. For specific information on KM version arbitration, see PATROL Console for Unix User Guide or PATROL Console for Microsoft Windows User Guide, Volume 1. In PATROL 7.x architecture, KM related files that are installed on the console computer are not versioned. Therefore, PATROL Central Operator does not take part in KM version arbitration.
Chart History
In PATROL Console for Windows and PATROL Console for Unix, history is shown in a separate window from the main chart. In PATROL Central Operator, history is shown in the same window as the chart. You do not have to open a separate window to view historical data. The title of the chart displays the current history range.
6-8
Location of Task Icons

In PATROL Console for Windows and PATROL Console for Unix, icons for tasks are shown at the same level of the hierarchy as the object from which the task was run. In PATROL Central Operator, icons for tasks are all shown under the Tasks folder.
KMs in the PATROL Object Namespace

In PATROL 3.x architecture, the PATROL object namespace includes three levels: application class, application instance, and parameter. In PATROL 7.x architecture, the PATROL object namespace now includes a level for the KM. This level is above the application class level in the hierarchy. For PATROL Agent version 3.5, the KM level is automatically created for each loaded application class. The name of the KM is the same as the name of the corresponding application class. For example, in the runtime path of the Windows Operating System object, rt/NT_OS/NT_OS/NT_OS, the first NT_OS refers to the KM, the second NT_OS refers to the application class, and the third NT_OS refers to the application instance. This KM level is displayed in InfoBoxes (the runtime path item) and Event Manager (the event origin attribute). It is used in managed system queries and event filters. However, it is not displayed in the navigation pane and is not supported in PSL statements. When referring to a PATROL object in PSL commands, you must continue to use its PATROL 3.x path without the KM level.
6-9
Running Menu Commands and InfoBox Commands

In PATROL 3.x architecture, menu commands and InfoBox commands are stored in the KM on the console computer. When the user selects a menu command or opens an InfoBox, the console prompts the user for the value of any console macros, and determines where the command should be runon the console or on the PATROL Agent. Then the console either sends the command to the PATROL Agent for execution or executes the command itself. The PATROL Agent does not use the menu commands or InfoBox commands in its own copy of the KM. In PATROL 7.x architecture, menu commands and InfoBox commands are still stored in the KM. However, since the KM no longer exists on the console, the menu commands and InfoBox commands in the PATROL Agent are used. Also, local menu commands are disabled in the Web Edition of PATROL Central Operator. When the user selects a menu command or opens an InfoBox, the PATROL Agent tells the console to prompt the user for the value of any console macros and determines where the command should be run. Then the PATROL Agent executes the command.
Migrating Console Information from PATROL Console for Windows or PATROL Console for Unix
You can migrate console information from PATROL Console for Windows and PATROL Console for Unix to a management profile for PATROL Central Operator. After you migrate the console information to a management profile, you can then use the management profile with the Web Edition of PATROL Central Operator. See the PATROL Console Migration Tool Release Notes for more information about how to migrate console information.
6-10
Troubleshooting PATROL Central Operator
This appendix provides troubleshooting information on installing and configuring PATROL Central Operator. For more troubleshooting information, see the PATROL Central Operator Web Edition online Help, PATROL Console Server and RTserver Getting Started, and PATROL Installation Reference Manual. This appendix discusses the following topics: Common Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Installation Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 Web Server Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Problems that May Occur While Using PATROL Central Operator Web Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8 Gathering Troubleshooting Information . . . . . . . . . . . . . . . . . . . . . . 7-25 Installation Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25 Web Server Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25 Client Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29 Checking Which PATROL Central Ports Are In Use on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30 Obtaining Version, System and Contact Information . . . . . . . . . 7-31 Dealing with Web Server Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32
7-1
Common Problems
This section contains troubleshooting information for the following common problems.
Problem Type
Installation Problems Web Server Problems Problems that May Occur While Using PATROL Central Operator Web Edition
Page
7-3 7-5 7-8
7-2
Installation Problems
This section describes known issues and workarounds for issues that can occur when installing PATROL products.
References to aborted packages or components during installation
During installation of PATROL Central Operator, you may see references to aborted packages or components in the installation utility status screen and the log files. This happens when the installation utility encounters components that have already been installed on the target computer. The message does not indicate a problem with the product installation. Entries in the log files will indicate that the package or component was skipped because it was already installed.
Installing additional console module on Solaris and Linux
If you install additional console modules after you have installed the Web server and the installation utility detects port conflicts during the installation, you must stop the Web server and the servlet container to complete the installation.
Exiting applications and stopping processes on Windows
Before installing or uninstalling PATROL Central on Windows, exit all applications, and ensure that the following processes are not running: any Java processes (Java.exe and Javaw.exe) the Service Control Manager the Internet Services Manager (if you choose to integrate with IIS)
7-3
Uninstalling products on Windows platforms
Problem:
When you uninstall all PATROL products, the installation utility does not remove all product files. You must perform an additional task using specific control files after you uninstall all products to remove the remaining product files. For more information, see the PATROL Installation Reference Manual.
Solution:
Uninstalling products on Unix platforms
Problem:
On Unix, uninstalling PATROL Central does not remove the $BMC_ROOT/webcentral/bin directory. Manually remove the directory and files after the uninstall completes or stop the Web server before uninstalling.
Solution:
Uninstalling PATROL KM Help files or console module
If you uninstall a console module or PATROL KM Help files, you must restart the Web server and the servlet container after the uninstall.
7-4
Web Server Problems

This section contains troubleshooting information for the following problems.
Web server crashes on Linux platforms
Problem:
On Red Hat Linux 7.1 and 7.2 platforms, the Tomcat Web server crashes with a JVM error when the console server and RTserver are installed on separate computers from the Web server and PATROL Central Operator is connected to more than 100 agents. Install and run the console server, RTserver, and Web server on the same computer.
Solution:
Web server may not release all ports after PATROL Central is stopped on Unix platforms
Problem:
Using the ./pwcctl stop command to shut down PATROL Central may not release all the ports for the Tomcat or Apache processes. Perform the following steps as root: 1. Wait approximately 30 seconds then enter the following command to see if the ports have been released:
./pwcctl status
Solution:
2. If the ports have not been released, enter the following commands to get the process ids for the processes associated with the open ports:
ps -elf | grep jre1.4.x ps -elf | grep httpd
7-5
3. Terminate the processes found in step 2 by entering the following command:

kill process id
Saving user preferences on Windows Web servers
Problem:
User preferences are saved using the current user account. In PATROL Central, the account name is case sensitive, so the same Windows account may have multiple preferences defined, depending on the case of the account name that you used to log on to PATROL Central. Enter the account name the same way each time you log on to PATROL Central.
Solution:
The Web Server Will Not Start
Problem:
Some of the required ports are not available. For example, if you have just stopped the Web server, it might not have released the ports yet. Make sure that no processes are using the ports. See Checking Which PATROL Central Ports Are In Use on Unix on page 7-30. If you just stopped the Web server, wait for it to release the ports.
Solution:
7-6
Problem:
The Tomcat servlet container or Tomcat Web server was terminated incorrectly or ran out of disk space, causing the wc.* files in the WEB-INF directory to be set to zero length. Copy the files from the
$BMC_ROOT/webcentral/jakarta-tomcat/webapps/patrol/WEB-INF/ backup directory to the $BMC_ROOT/webcentral/jakarta-tomcat/webapps/patrol/WEB-INF
Solution:
directory.
On Solaris, the Web Server Dies at Startup
Problem: Solution:
The latest Solaris patches are not applied. Apply the latest patches for Solaris. See the PATROL Central Operator Web Edition Release Notes for information about Solaris patches.
7-7
Problems that May Occur While Using PATROL Central Operator Web Edition
This section contains troubleshooting information for the following problems.
Dragging a user-defined chart or folder to a gauge, text, or stoplight parameter
Problem:
If you drag a user-defined chart or folder to a gauge, text, or stoplight parameter, the chart or folder disappears. You cannot recover the user-defined chart or folder. Do not drag a user-defined chart or folder to a gauge, text, or stoplight parameter.
Solution:
Suspending parameter through attribute setting in Customizations dialog box
Problem:
If you suspend a parameter by selecting the Suspend attribute in the Customizations dialog box, you cannot use the Task => Resume menu command to resume the parameter. Suspend and resume the parameter by right-clicking it and choosing Task => Suspend or Resume.
Solution:
7-8
Event Manager default filter does not work properly if Event Manager taskpad is open
Problem:
If you specify an event filter as the default filter, then load a different filter and close the Event Manager while the Event Manager taskpad is displayed, the Event Manager will access events from the current filter instead of the default filter. Ensure that the Event Manager taskpad page is not displayed before you access the default event filter.
Solution:
Event Filter Properties dialog box text entry field does not work properly
Problem:
On the Event Filter Properties dialog box, the Limit number of events displayed per Managed System text entry field does not work properly. If you type a new value into the field, the new value is not accepted. Instead, the default value is retained. Use the spin control to specify a new value.
Solution:
Parameters for multi-line charts do not displayed properly in custom views
Problem:
If you create a multi-line chart outside of a custom view, and you add the chart object to a custom view, the chart parameter list does not display correctly. Viewing the chart after it is created displays the parameters correctly. To see the correct parameter list for the multi-line chart, add the parameters to the chart within the Custom View wizard.
Solution:
7-9
Dragging and dropping parameters into custom view objects within the tree view
Problem:
You cannot drag and drop a parameter into a custom view object within a tree view. The symbol is not displayed when you attempt to perform this action. Do not drag and drop parameters into the custom view object within the tree view. Instead, in the tree view area, right-click the custom view object and choose Edit to add parameters to the custom view.
Solution:
Creating custom views with similar multi-line charts
Problem:
If you create a custom view with multi-line charts and two cells within the view have the same parameter names, the second cell will not display any data. Change the default title of the multi-line chart in one of the cells so that the names are unique for each cell.
Solution:
Graphs autoscale within a custom view
Problem:
If you create a custom view and add a graph to the view, the Y axis will autoscale based on the minimum and maximum values for the data displayed in the graph but no data is lost. No workaround
Solution:
7-10
Selection of rows is not persistent for managed system query
Problem:
When you execute a managed system query and the query returns more than one page of results, if you select objects on one page, then click Next or Back, the objects will no longer be selected. Perform one of the following actions: Set the default number of lines per page so that the results are displayed on one page. For each page in the results pane, add the results to a folder or chart.
Solution:
For more information, see the PATROL Central Operator Web Edition Help.
Exporting charts and graphs is not supported
Problem:
You cannot export charts and graphs as images or copy them to the clipboard to use in other applications. Double click the title of the chart or graph to open it in a separate window and create a screen capture of the window; for example, on Windows platforms, use Alt + Print Scrn. You can then paste the image into a document or image editor.
Solution:
7-11
Incorrect profile name is displayed in the Open Management Profile wizard
Problem:
When you use the Open Management Profile wizard to change to a new management profile, the previous profile name is still displayed on the Finish page of the wizard. Click Back then Next to display the new profile name.
Solution:
After initial connection to a management profile or on start-up of PATROL Central Operator, text parameters and gauges are not immediately displayed in custom views
Problem:
If you create a custom view and add a text parameter or gauge, when you open a management profile or log off and log back on to PATROL Central Operator and open the custom view, the items are not immediately displayed. No workaround
Solution:
Shortcuts to parameters cannot be added to custom views
Problem:
A shortcut to a parameter will not be visible while creating a custom view in the Create Custom View wizard. Add the parameter itself to the custom view, instead of the shortcut.
Solution:
7-12
Adding a disconnected managed system to a folder
Problem:
You cannot add a disconnected managed system to a folder from the Query results page. Make sure that the managed system is connected before adding it to the folder or move the specified managed system from the tree view to the folder.
Solution:
Changes to a managed system query are not recognized immediately
Problem:
When you edit a query from the Managed System Query Results page, you must load the query again to view the changes. If you attempt to edit the query again before reloading it, your changes will not be present. Reload the query after making changes.
Solution:
Multiple objects with the same name
Problem:
You can have multiple objects (shortcuts, folders, custom views, and charts) with the same name at the same level of the hierarchy in a management profile. For example, if two managed systems have the same parameter, you can create shortcuts to each instance of the parameter, then move the shortcuts to the same folder. You can copy an item of the same name to another level of the hierarchy. The copied item will not overwrite or be prepended or appended to the existing item. Each item is unique. No workaround
Solution:
7-13
Adding objects from the managed system query results page to a folder or chart
Problem:
You cannot add objects from the Managed System Query Results page to a user-defined folder or chart that is not directly under the PATROL Main Map. User-defined folders and charts that are not directly under the PATROL Main Map are not displayed in the list of existing folders and charts. Move the folder or chart directly under the PATROL Main Map, add the object to the folder or chart, then move the folder or chart back to its original location. You can also drag a single object in the tree view area to the folder or chart.
Solution:
Output for a task being redirected to the system output window
Problem:
Normally the output from a task, such as a task started from a KM command or a user initiated PSL or OS task, is displayed in the window for the task. However, if two tasks are running and you delete the first task, any future output for the second task is redirected to the system output window. This issue is most visible when the task takes a long time to execute, the task is interactive, or you repeat the task. If the output for a task is missing from its task window, look in the system output window. You can also avoid this issue by waiting for all tasks to complete before deleting any of them.
Solution:
7-14
PATROL Infrastructure KM not displayed under PATROL Main Map
Problem:
The PATROL Infrastructure KM is designed to display the PATROL7 application class directly under the PATROL Main Map. However, unless the PATROL7.kml is preloaded, the PATROL7 application class is displayed under the managed system on which the KM is loaded. Preload the PATROL7.kml on the managed system. Then close and reopen the management profile used to view the KM, or disconnect from and reconnect to the managed system.
Solution:
Granting write access to management profiles
Problem:
If you use PATROL Central Administration to grant the write right for a management profile to a group or user that does not have the Create and destroy management profile privilege, those users cannot open that management profile for read/write (versus read-only). If those users attempt to open the management profile for read/write, all users become locked out of the management profile until the PATROL Console Server is restarted. By default, only the patadm, patpop, and patop groups have the Create and destroy management profile privilege.
Solution:
If you use PATROL Central Administration to allow the write right for a management profile to a group or user, also make sure that the group or user has the Create and destroy management profile privilege. If users are locked out of a management profile due to this issue, restart the PATROL Console Server to unlock it.
7-15
Deleting aliases in impersonation tables
Problem:
You can delete an alias even though it has been added to an impersonation table. The impersonation connected to that alias will not work. Recreate the alias or remove the entry from the impersonation table.
Solution:
Multiple sessions of PATROL Central Administration
Problem:
PATROL Central Administration retrieves its data from the PATROL Console Server. If there are multiple sessions of PATROL Central Administration connected to the same PATROL Console Server, changes made in one session are not automatically reflected in the other sessions. To see changes made in other sessions, reload the page.
Solution:
Shortcut keys and function keys are not supported
Problem:
Browser-defined shortcut keys and function keys are not supported in this release. Do not use shortcut or function keys.
Solution:
7-16
The PATROL Central Web Page Is Not Available
Problem: Solution:
The Web server is not running. Start the Web server (IIS, Apache, or Tomcat standalone). For IIS, you must also start the Tomcat servlet container separately. For more information see Starting and Stopping PATROL Central Operator Web Edition on page 5-11.
Problem: Solution:
The Web server is using a different port from the default. Inform users to include the port number in the URL. For example, if the Web server myserver is using port 8080, view the URL http://myserver:8080.
Problem: Solution:
On IIS, the security certificate is not properly installed or it has expired. Install a valid security certificate. For more information, see Certificate Information (IIS Only) on page 2-18.
7-17
The PATROL Central Web Page is Blank on Internet Explorer
Problem:
If you are using IE 6 on a Windows 2003 machine, after you enter the PATROL Central Operator URL, IE may display a blank web page. This is caused by Windows 2003 applying a high security level by default. You can the solve this problem using two different methods:
Solution:
To add the PATROL Central Operator URL to the Trusted Sites list in IE
From the IE Tools menu, select Internet Options => Security. Select Trusted Sites and click Add Add the PATROL Central Operator URL to the list of trusted sites and click OK.
To set the security level for Trusted Sites
From the IE Tools menu, select Internet Options => Security. Select Trusted Sites and move the slider down for a lower level of security
The RTserver or PATROL Console Server Is Not Responding
Problem: Solution:
The RTserver or PATROL Console Server is not running. Make sure that the RTserver and PATROL Console Server are running. For more information, see the PATROL Console Server and RTserver Getting Started. If you must start the RTserver, wait for PATROL Central to recognize that the RTserver has been started.
7-18
Problem:
PATROL Central might not be using the correct RTserver or PATROL Console Server. Make sure that PATROL Central is using the correct RTserver and PATROL Console Server and that their names are type correctly. Note that the name of the PATROL Console Server might not match the host name. For more information, see the AppendixB, Modifying Initialization Settings After Installation.
Solution:
Problem:
PATROL Central might be using a different RTserver from the PATROL Console Server. Make sure that PATROL Central and PATROL Console Server are using the same RTserver. For more information, see AppendixB, Modifying Initialization Settings After Installation and PATROL Console Server and RTserver Getting Started.
Solution:
Problem: Solution:
The PATROL Console Server might not be available on the network. To determine if the PATROL Console Server computer is available on the network, ping the host name of the computer. Note that the name of the PATROL Console Server is its host name by default; however, a different name can be specified when starting the PATROL Console Server. Also ensure that the RTserver computer and the PATROL Console Server computer can both reach each other on the network.
Problem: Solution:
The RTserver might not be available on the network. To determine if the RTserver is available on the network, telnet to the RTserver on the appropriate port. Also ensure that the RTserver computer and the Web server computer can both reach each other on the network.
7-19
Users Cannot Log on
Problem: Solution:
HTTPS is not active. Make sure that HTTPS is active by trying to access https://hostname:port, where hostname is the name of the server, and port is its HTTPS port. If you are using IIS, make sure that PATROL Central is using the correct HTTPS port for IIS. For more information about setting the HTTPS port, see the AppendixB, Modifying Initialization Settings After Installation.
Problem: Solution:
The user did not accept the certificate for the Web server. Inform the user to restart the Web browser and accept the certificate when accessing the PATROL Central Web site.
Problem:
The PATROL Console Server is too busy processing requests from other computers to process your log on request. (You get the Failed to log on to Console Server. Operation Timed Out error message.) Inform users to try to log on again.
Solution:
Problem: Solution:
The user might be using an incorrect user name or password. Inform the user to use a user name and password for an operating system or domain account on the PATROL Console Server.
7-20
Problem: Solution:
The user might not have the necessary privileges. Grant the necessary privileges to the user by placing the user account in the appropriate group on the PATROL Console Server.
Users Cannot Add a Managed System
Problem:
The PATROL Agent software on the managed system might not be running, or it might not be using the correct RTserver. Make sure the PATROL Agent software is running on the managed system and using the correct host name and port number for the RTserver. For more information, see the PATROL Agent Reference Manual and PATROL Console Server and RTserver Getting Started.
Solution:
Problem:
The PATROL Agent software on the managed system might be a version previous to version 3.5. Make sure the PATROL Agent software is at least version 3.5. For more information, see the PATROL Agent Reference Manual.
Solution:
Problem: Solution:
The management profile might be read-only. Inform the user to use a management profile that is not read-only.
7-21
Problem: Solution:
The user might not have the necessary privileges. Grant the necessary privileges to the user by placing the user account in the appropriate group on the PATROL Console Server.
Users are Prompted to Log on to a Managed System
Problem: Solution:
The managed system does not recognize the user as a valid user. Set up the impersonation table for the user in PATROL Central Administration. The user can also log on to the managed system with an account on that system.
No Online Help Exists for a Specific KM
Problem:
The online Help for that KM is not installed with PATROL Central Operator. If you are running a PATROL Console Server prior to version 7.2.36, make sure you install the appropriate online Help with the PATROL Central Operator whenever you install a new KM on a managed system.
Solution:
Problem: Solution:
There is no online Help for that KM. No action required.
7-22
PATROL Central Does Not Prompt for Password in Attended Mode
Problem:
On Unix, at security level 4, attended mode, PATROL Central does not prompt for the keystore location or password when it is started. The startup script uses 'su -' to pass the Tomcat user's environment to the Tomcat process. This includes the X11 variables necessary to display a dialog box. Set your default shell, as specified in etc/passwd, to /bin/sh. If you use a different shell, such as ksh or bash, the environment is not passed so X11 is not available to the Tomcat process.
Solution:
Users Are Told to Accept the Certificate, But Are Never Allowed To Do So
Problem:
On Netscape, after a user permanently accepted the certificate for the Web site in a previous session, you re-installed the certificate on the Web server or installed a new certificate. Inform the user to delete the certificate from the browser, then reconnect to the PATROL Central Web site.
Solution:
7-23
Interface Display Problems when Using Netscape
Problem: Solution:
Intermittent display problems may occur when using Netscape. Adding "-Dsun.java2.ddoffscreen=false" to the list of Java Runtime Parameters will fix some display problem that you may encounter on Netscape. For more information, see Avoiding Conflicts with Other Desktop Applications on page 3-4.
7-24
Gathering Troubleshooting Information

This section contains information on locating installation logs and Web server logs.
Installation Logs
One log file is created each time the installer is run. The name of the log file is a combination of the computer name and a time stamp. The location of the file depends on the operating system. On Windows 2000, the log file is saved to the
Document and Settings\username\Application Data\BMCINSTALL\
directory. On Windows NT, the log file is saved to the

Winnt\Profiles\username\Application Data\BMCINSTALL\ directory.
On Unix, the log file is saved to the home_directory/BMCINSTALL/ directory.
For example, the log file for user auser on a Windows NT computer ACOMPUTER could be
C:\WINNT\Profiles\auser\Application Data\BMCinstall\ACOMPUTER_11005340189.log.
Web Server Logs

Which Web server logs you have depends on the Web server. All Web servers will have Tomcat servlet container logs.
Note
This section refers to the webcentral sub-directory of $BMC_ROOT. This directory is WebCentral on Windows, and webcentral on Unix. For more information see, Installation Directory on page 2-15.
7-25
IIS Web Server Logs
The IIS Web server maintains log files and also places messages in the Windows Event log. The logs for IIS are located in the system_dir\LogFiles\w3svcl\ directory. These logs are most useful for monitoring HTTP requests.
Apache Web Server Logs
The Apache Web server maintains the log files in the $BMC_ROOT/common/apache/httpd/OS/logs/ directory. The error_log file contains information about port conflicts and startup problems. The Apache Web server log files can grow considerably over the course of time. For example, each image load request is logged. The installation installs a utility to truncate the log files for the Apache Web server while the Web server is running, so that they do not grow without limit. The utility consists of the following files: the /etc/patrol.d/apache/bmctrimlog executable utility the /etc/patrol.d/apache/bmctrimlog.conf text configuration file
This utility can be run periodically as a job in the root crontab. If you chose to automatically add the job to the root crontab in the installation, the following line is added, which runs the utility every hour on the half-hour.
30 * * * * /etc/patrol.d/apache/bmctrimlog
If you chose to not add the job to the root crontab, you can add the job manually and adjust the job schedule. For more information about cron and crontab, see the man pages for them for your system. To fine-tune the log file management edit the bmctrimlog.conf file. For example, you can set different maximum sizes for each log file. See the comments in the configuration file for more information.
7-26
Tomcat Web Server and Servlet Container Logs
The following logs in the $BMC_ROOT/webcentral/jakarta-tomcat/logs directory reflect the state of the Tomcat servlet container and its integration with the Web server.
Web Server
all all all IIS Apache Apache and Tomcat standalone (Unix) IIS and Tomcat Standalone (Windows) IIS and Tomcat Standalone (Windows)
a
File
localhost_log.year-month -date.txta localhost_examples_log. year-month-date.txta localhost_access_log.ye ar-month-date.txta isapi.log mod_jk.log jvm.stdout
Description
standard output log file for Tomcat Web server example Web applications log file access log file for Tomcat Web server This file contains messages created by the Apache Jakarta Protocol 13 (AJP13) ISAPI filter. This file contains messages created by the Apache Jakarta Protocol 13 (AJP13) Apache module. This file contains the standard output of the Tomcat java process. It is usually the most useful log to look at initially. This file contains the Tomcat java process standard output messages when Tomcat is run as a service. If Tomcat is run from a command window, all output is sent to that window. This file contains the Tomcat java process standard error output messages when Tomcat is run as a service. If Tomcat is run from a command window, all output is sent to that window.
stdout.log
stderr.log
The level of verbosity in these logs is controlled by settings in the $BMC_ROOT/webcentral/jakarta-tomcat/conf/server.xml file
7-27
The following logs in the

$BMC_ROOT/webcentral/jakarta-tomcat/webapps/patrol/WEB-INF/log/
directory contain information for the Tomcat servlet container.

File
jcosjni.log pwc1.loga pwc2.log pwc3.log pwc4.log pwc5.log
a a
Description
log file for jcosjni These files are error log files for PATROL Central. The log pwc1.log is always the most recent.
The level of verbosity in these logs is controlled by the $BMC_ROOT/webcentral/jakarta-tomcat/webapps/patrol/WEB-INF/ globalDebug.cfg file.
On Windows, if you run the Tomcat Web server as a service, it also places messages into the Windows Event log.
7-28
Client Logs
The location of client logs depends on the platform of the client.
Windows Client Logs
On Windows, the Java Plugin also has its own error messages and trace file. To view error messages related to the Java Plugin, double-click the java console icon in the system tray. The location of the Java Plugin trace file depends on the operating system. On Windows 2000, the Java Plugin trace file is saved to the Document and Settings\username\plugin141_02.trace file. On Windows NT, the Java Plugin log file is saved to the
Winnt\Profiles\username\plugin141_02.trace file. Unix Client Logs
On Unix, the Java Plugin trace log contains trace output from the plugin. It is contained in the home directory of the user. The typical file name is plugin141_02.trace.
7-29
Checking Which PATROL Central Ports Are In Use on Unix Summary:

This task describes how to check whether the ports used by the PATROL Central Web server are in use on Unix.
To Check Which Ports are In Use on Unix
Step 1 Step 2
Change to the root user. In a command window, change to the $BMC_ROOT/webcentral/bin directory. Enter the following command:
./pwcctl status
Step 3
7-30
Obtaining Version, System and Contact Information Summary:

This task describes how to obtain version, system, and contact information for PATROL Central.
To Obtain Version, System and Contact Information
Start your Web browser and log on to PATROL Central. In the navigation area, click the Home tab, then the About sub-tab. Click one of the following links in the list area: Version Information System Information Contact Information
7-31
Dealing with Web Server Issues

For assistance with Web server issues, see the documentation for your Web server.
Web Server
IIS Apache
Documentation
See the IIS documentation. See the following: the Apache documentation installed with Apache at http://hostname:port/manual, where hostname is the name of the server, and port is its HTTP port. the Apache HTTP Server Web site at http://httpd.apache.org. See the following the Tomcat documentation installed with Tomcat at http://hostname:port/tomcat-docs, where hostname is the name of the server, and port is its HTTP port. the Jakarta Project Web site at http://jakarta.apache.org/tomcat.
Tomcat standalone
Note
The documentation for the Web server and the documentation for PATROL Central differ in some areas. For example, in how you start the Web server. In these cases, follow the documentation for PATROL Central.
7-32
Enhancing Web Server Security
Historically, Web servers have been vulnerable to back-door attacks. Unusual URLs, combined with weaknesses in the handling of them, may allow unauthorized users to execute commands on behalf of the Web server account. This section discusses optional tasks that you can do to minimize potential damage. About the Keystore Password and Self-signed Certificate for the Apache Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 About the Keystore Password and the Apache Policy File . . . . A-2 Replacing the Self-signed Certificate . . . . . . . . . . . . . . . . . . . . A-3 About Attended and Unattended Modes for the Apache Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
A-1
About the Keystore Password and Self-signed Certificate for the Apache Web Server
This section discusses how the keystore password is saved and the implications of this implementation.
About the Keystore Password and the Apache Policy File

Apache needs the password for the keystore when it starts up so that it can access its keystore containing its private key. This private key is used together with the corresponding certificate to perform encrypted communications. You specify the keystore password in the installation. By default, this password is stored encrypted in the /etc/patrol.d/security_policy/Apache.plc policy file. Apache is configured to automatically retrieve the password from this policy file.
Note
Apache operates outside the PATROL Security context. The Apache.plc policy file is used only to store and retrieve the keystore password. Other information stored in the file is not used. For more information about policy files, see the PATROL Security User Guide. If you obtain a new certificate from a certificate authority, you might also have to generate a new private key and keystore. If the new keystore is protected by a different password from the one specified in the installation, you must also update the Apache policy file.
A-2
Replacing the Self-signed Certificate Summary:

This task describes how to replace the self-signed certificate created at installation with a certificate from a certificate authority. Obtain the certificate from a certificate authority. Installing the new certificate. See your certificate authority for detailed instructions.
Step 3
Step 1 Step 2
If the certificate uses a private key with a different password from the previous keystore password, use the plc_password utility to update the password for the Apache.plc policy file to the new password.
Note
The plc_password utility is documented in the PATROL Security User Guide.

Step 4
Restart the Apache Web server.
About Attended and Unattended Modes for the Apache Web Server
By default, Apache runs in unattended mode. It automatically retrieves the keystore password from the Apache policy file. However you can configure it for attended mode. In attended mode, an administrator must manually enter to the keystore password when starting Apache, and the Apache policy file is no longer used. The keystore password for starting Apache is specified in the installation. It is not the default password specified in the PATROL Security User Guide.
A-3
To convert Apache to attended mode, use the SSLPassPhraseDialog directive in the httpd.conf file. For more information, see the SSL documentation included with the Apache documentation at http://hostname:port/manual/mod/mod_ssl, where hostname is the name of the server, and port is its HTTP port. Do not use the plc_password utility that is documented in the PATROL Security User Guide to switch Apache to unattended or attended mode. That method does not apply to starting the Apache Web server.
A-4
Modifying Initialization Settings After Installation B

You configure initialization settings during the installation of PATROL Central Operator. However, you can change some of those settings after installation by editing the startup configuration file. This appendix discusses the following topics: The Startup Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2 About Modifying the Startup Configuration File . . . . . . . . . . . .B-2 What You May Modify in the Startup.cfg file . . . . . . . . . . . . . .B-3
B-1
The Startup Configuration File

The startup configuration file, startup.cfg, resides in
$BMC_ROOT/webcentral/jakarta-tomcat/webapps/patrol/WEB-INF. Note
This path refers to the webcentral sub-directory of $BMC_ROOT. This directory is WebCentral on Windows, and webcentral on Unix. For more information see, Installation Directory on page 2-15.
About Modifying the Startup Configuration File

The startup configuration file is a flat text file. When you modify the file, observe the following rules: Place each assignment statement alone on a single line. Each assignment statement must be of the format token = value with no commas, semi-colons, or other special characters Precede any comments with a # in the first position of the line.
Note
You must restart the Tomcat servlet container for any changes to the startup configuration file to take effect. For the Apache and Tomcat standalone servers, this also involves restarting the Web server.
B-2
What You May Modify in the Startup.cfg file

The following table lists the entries in the in the startup configuration file that you may modify.
Entry
RTServer securityService
Description
This entry specifies the RTserver to use. For more information, see RTserver on page 2-21. This entry specifies the PATROL Console Server that is used as a security server for PATROL Central. For more information, see PATROL Console Server on page 2-16. This entry specifies the HTTPS port for the Web server. For more information, see Web Server HTTP and HTTPS Ports (Apache and Tomcat Only) on page 2-23 or IIS HTTPS Ports (IIS Only) on page 2-23. This entry is used to cache users login credentials as the default login credentials. If you set the caching flag in the startup.cfg file, the next time you login to a PATROL Console Server using PATROL Central Operator Web Edition, your login credentials are cached as the default. This means, when you login to PATROL Central Operator, your user name and password credentials are saved. If you try to open a management profile on a different PATROL Console Server, and if your credentials are valid for the new console server, PATROL Central Operator will not prompt you to enter your login user name and password. To cache login credentials, stop the PATROL Central Operator Web Edition process, open the statup.cfg file and remove the comment character from the first position in the cacheLoginCredentials line. You must be running the PATROL Console version 7.2.30 or above to use this functionality.
httpsPort
cacheLoginCredentials
B-3
Tip
If you used the installation worksheets (See Installation Worksheets on page 2-24), record any changes to these entries on the worksheets.
Warning
Do not modify any other settings in the startup configuration file. They are for use by BMC Software technical support only.
B-4
Environment Variables
This appendix lists the environment variables used by PATROL Central Operator. The values of these variables are assigned at installation.
Environment Variable
BMC_ROOT
How Variable Is Used

points to the location where BMC Software products are installed. This directory is stored as the $BMC_ROOT or %BMC_ROOT% environment variable depending whether the operating system is Unix or Windows respectively. points to the location where PATROL 7.x components, including PATROL Central Operator, are installed. This directory is stored as the $PATROL_ROOT or %PATROL_ROOT% environment variable depending whether the operating system is Unix or Windows respectively.
PATROL_ROOT
The BMC_ROOT environment variable is shared by all PATROL Central components that are installed on the same computer.
Environment Variables
C-1
C-2
Index
Index
Symbols
$BMC_ROOT 2-15, C-1 $PATROL_ROOT C-1 %BMC_ROOT% 2-15, C-1 %PATROL_ROOT% C-1
C
caching login credentials B-3 certificate about 2-6 accepting or installing in Web browser 3-6 considerations for Apache Web server 2-4 considerations for IIS Web server 2-3 considerations for Tomcat standalone Web server 2-5 obtaining for IIS Web server 2-18 specifying info for Apache Web server 2-20 specifying info for Tomcat standalone Web servers 2-20 chart history 6-8 compatibility KMs and PATROL Central Operator 6-2 PATROL Agent 6-2 console migrating to new version 2-29 migration from 3.x versions 6-10 console information, migrating 6-10 console infrastructure 1-3 console module 1-3 consoles 6-1
Index 1
A
accounts web server 2-17 agent query 6-5 AJP v13 port 2-22 alarm ranges 6-7 alarm state, vs. critical state 6-5 aliases 4-6, 4-8 Apache Web server considerations 2-4 execution of 5-14 installation worksheet 2-27 logs 7-26 port 2-23 user name and group 2-17
critical state vs. alarm state 6-5 custom installation 2-14 custom views 1-3 customizations, vs. overrides 6-7
setting up on for PATROL Console Server 4-4 Tomcat standalone Web server group 2-17, 2-44, 2-60 groups and user accounts 4-1, 4-2
D
developer functionality 6-3 diagram, PATROL architecture 1-5 directory structure 2-62 documentation manuals, availability 1-8 related 1-6 release notes, availability 1-8
H
Help accessing 1-7 HTTP and HTTPS (Apache and Tomcat standalone Web servers) ports 2-23 HTTP port specifying for Apache Web server 2-23 specifying for Tomcat standalone Web server 2-23 HTTPD 2-17, 2-56 HTTPS port changing B-3 specifying for Apache Web server 2-23 specifying for IIS Web server 2-23 specifying for Tomcat standalone Web server 2-23
E
environment variables $BMC_ROOT C-1 $PATROL_ROOT C-1 %BMC_ROOT% C-1 %PATROL_ROOT% C-1
F
features of PATROL Central Operator 1-2 firewalls 2-7
I
IIS Web server considerations 2-3 installation worksheet 2-26 logs 7-26 port 2-23 Web site instance 2-23 impersonation 4-6, 4-8 InfoBox commands 6-10 installation 2-1 about custom path 2-14 about typical path 2-14 components 2-9 directory 2-15
G
groups 2-17 Apache Web server group 2-17 general guidelines for PATROL Console Server 4-6 PATROL Console Server and managed systems 4-4
logs 7-25 procedure for Unix 2-46 procedure for Windows 2-32 required information for custom path 2-22 required information for typical path 2-15 troubleshooting 7-3 upgrading to new version 2-29 verifying 5-15 worksheets 2-24 internal datastore 2-29
management profiles about 3-12 selecting 3-14 vs. desktop files 6-4 manuals, availability 1-8 menu commands 6-10 migrating to new version 2-29 monitoring with PATROL Central Operator 3-1
O
operating systems supported versions 2-10 overrides vs. customizations 6-7
J
Java Plugin 3-3
K
KMs console compatibility 6-2 loading 3-21
P
passwords, caching B-3 patadm 4-15 patadm group 4-5 patop 4-15 patop group 4-5 patpop 4-15 patpop group 4-5 PATROL 7.x environment 2-2 PATROL Agent execution on Windows 5-5 managed system vs. 6-5 starting on Unix 5-5 stopping on Unix 5-6 supported version 2-2 verifying execution on Unix 5-6 PATROL architecture, diagram of 1-5 PATROL Central accessing 3-8 interface 3-9 main window 3-10 PATROL Central Operator vs. 1-3
L
login credentials, caching B-3
M
managed system query 6-5 managed systems adding 3-18 aliases and impersonation 4-6, 4-8 architecture 1-4 name 6-6 term 6-5 user accounts 4-6, 4-8
Index
troubleshooting 7-8 PATROL Central Administration about 4-27 starting 4-28 troubleshooting 7-8 when to use 4-27 PATROL Central Operator accessing 3-11 architecture diagram 1-5 configuring environment for 5-1 features 1-2 installing 2-1 management profile 3-12 monitoring with 3-1 PATROL and 1-4 PATROL Central vs. 1-3 system requirements 2-10 troubleshooting 7-1, 7-8 PATROL Central sub-directory 2-15 PATROL Console Server about 2-16 architecture 1-4 changing PATROL Central security server B-3 connecting to 3-14 execution on Windows 5-7 impersonation table 4-6, 4-8 PATROL Central security server 2-16 starting on Unix 5-7 stopping on Unix 5-8 supported version 2-2 user accounts and groups 4-4, 4-14 verifying execution on Unix 5-7 verifying installation 5-15 PATROL security information 2-22 patscadm 4-15 patscadm group 4-5 patwatch 4-15 patwatch group 4-5 ports
AJP v13 2-22 changing after installation 5-16 checking use of 7-30 HTTP and HTTPS (Apache and Tomcat standalone Web servers) 2-23 HTTPS (IIS Web server) port 2-23 managed systems 6-6 Tomcat shutdown 2-22 privileges and rights 4-4, 4-14 problems, common 7-2
R
release notes, availability 1-8 RTserver architecture 1-4 changing B-3 execution on Windows 5-3 specifying 2-21 starting on Unix 5-3 stopping on Unix 5-4 supported version 2-2 verifying execution on Unix 5-3 verifying installation 5-15
S
security enhancing for Web server A-1 Web server A-1 services starting 5-9 stopping 5-9 startup configuration file B-2 modifying B-2 startup.cfg 2-29, B-2 modifying B-2 state change actions 6-7 system requirements 2-10
T
terminology 6-5 test URLs 5-15 Tomcat port 2-23 Tomcat servlet container execution on Windows 5-12 logs 7-27 verifying installation 5-15 Tomcat shutdown port 2-22 Tomcat standalone Web server considerations 2-5 installation worksheet 2-28 logs 7-27 Web server user name and group 2-17 Tomcat standalone Web server group 2-44, 2-60 Tomcat Web server execution of 5-13 starting 5-13 stopping 5-13 troubleshooting 7-1 installation 7-3 PATROL Central 7-8 web server 7-5 typical installation 2-14
Tomcat standalone Web server account 2-17 user accounts and groups setting up 4-1, 4-2
W
Web browser logs 7-29 requirements 3-2 Web server 2-17 account 2-17 Apache 2-4 choices 2-3 IIS 2-3 log files 7-25 starting 5-11 stopping 5-11 supported versions 2-10 Tomcat standalone 2-5 verifying execution of 5-15 verifying installation 5-15 web server troubleshooting 7-5 Web server security enhancing A-1 Web server user name and group 2-17 webcentral directory 2-15 worksheets Apache Web server 2-27 general 2-25 IIS Web server 2-26 installation 2-24 Tomcat standalone Web server 2-28
U
upgrading to new version 2-29 URLs test 5-15 user accounts Apache Web server account 2-17 general guidelines for PATROL Console Server and managed systems 4-6 setting up on for PATROL Console Server and managed systems 4-4
Index
END USER LICENSE AGREEMENT NOTICE

BY OPENING THE PACKAGE, INSTALLING, PRESSING "AGREE" OR "YES" OR USING THE PRODUCT, THE ENTITY OR INDIVIDUAL ENTERING INTO THIS AGREEMENT AGREES TO BE BOUND BY THE FOLLOWING TERMS. IF YOU DO NOT AGREE WITH ANY OF THESE TERMS, DO NOT INSTALL OR USE THE PRODUCT, PROMPTLY RETURN THE PRODUCT TO BMC OR YOUR BMC RESELLER, AND IF YOU ACQUIRED THE LICENSE WITHIN 30 DAYS OF THE DATE OF YOUR ORDER CONTACT BMC OR YOUR BMC RESELLER FOR A REFUND OF LICENSE FEES PAID. IF YOU REJECT THIS AGREEMENT, YOU WILL NOT ACQUIRE ANY LICENSE TO USE THE PRODUCT. This Agreement ("Agreement") is between the entity or individual entering into this Agreement ("You") and BMC Software Distribution, Inc., a Delaware corporation located at 2101 CityWest Blvd., Houston, Texas, 77042, USA or its affiliated local licensing entity ("BMC"). "You" includes you and your Affiliates. "Affiliate" is defined as an entity which controls, is controlled by or shares common control with a party. THIS AGREEMENT WILL APPLY TO THE PRODUCT, UNLESS (1) YOU AGREED TO A WEB BASED LICENSE AGREEMENT WITH BMC WHEN ORDERING THE PRODUCT, IN WHICH CASE THAT WEB BASED LICENSE AGREEMENT GOVERNS THE USE OF THE PRODUCT, OR (2) IF YOU DID NOT AGREE TO A WEB BASED LICENSE AGREEMENT WITH BMC WHEN ORDERING THE PRODUCT AND YOU HAVE A WRITTEN LICENSE AGREEMENT WITH BMC, THEN THAT WRITTEN AGREEMENT GOVERNS THE USE OF THE PRODUCT. THE ELECTRONIC AGREEMENT PROVIDED WITH THE PRODUCT AS PART OF THE INSTALLATION OF THE PRODUCT WILL NOT APPLY. In addition to the restrictions imposed under this Agreement, any other usage restrictions contained in the Product installation instructions or release notes shall apply to Your use of the Product. PRODUCT AND CAPACITY. "Software" means the object code version of the computer programs provided, via delivery or electronic transmission, to You. Software includes computer files, enhancements, maintenance modifications, upgrades, updates, bug fixes, and error corrections. "Documentation" means all written or graphical material provided by BMC in any medium, including any technical specifications, relating to the functionality or operation of the Software. "Product" means the Software and Documentation. "License Capacity" means the licensed capacity for the Software with the pricing and other license defining terms, including capacity restrictions, such as tier limit, total allowed users, gigabyte limit, quantity of Software, and/or other capacity limitations regarding the Software. For licenses based on the power of a computer, You agree to use BMCs current computer classification scheme, which is available at http://www.bmc.com or can be provided to You upon request. ACCEPTANCE. The Product is deemed accepted by You, on the date that You received the Product from BMC. LICENSE. Subject to the terms of this Agreement, as well as Your payment of applicable fees, BMC grants You a non-exclusive, non-transferable, perpetual (unless a term license is provided on an order) license for each copy of the Software, up to the License Capacity, to do the following: (a) install the Software on Your owned or leased hardware located at a facility owned or controlled by You in the country where You acquired the license; (b) operate the Software solely for processing Your own data in Your business operations; and (c) make one copy of the Software for backup and archival purposes only (collectively a "License"). If the Software is designed by BMC to permit you to modify such Software, then you agree to only use such modifications or new software programs for Your internal purposes or otherwise consistent with the License. BMC grants You a license to use the Documentation solely for Your internal use in Your operations. LICENSE UPGRADES. You may expand the scope of the License Capacity only pursuant to a separate agreement with BMC for such expanded usage and Your payment of applicable fees. There is no additional warranty period or free support period for license upgrades. RESTRICTIONS: You agree to NOT: (a) disassemble, reverse engineer, decompile or otherwise attempt to derive any Software from executable code; (b) distribute or provide the Software to any third party (including without limitation, use in a service bureau, outsourcing environment, or processing the data of third parties, or for rental, lease, or sublicense); or (c) provide a third party with the results of any functional evaluation or benchmarking or performance tests, without BMCs prior written approval, unless prohibited by local law.
TRIAL LICENSE. If, as part of the ordering process, the Product is provided on a trial basis, then these terms apply: (i) this license consists solely of a non-exclusive, non-transferable evaluation license to operate the Software for the period of time specified from BMC or, if not specified, a 30 day time period ("Trial Period") only for evaluating whether You desire to acquire a capacity-based license to the Product for a fee; and (ii) Your use of the Product is on an AS IS basis without any warranty, and BMC, ITS AFFILIATES AND RESELLERS, AND LICENSORS DISCLAIM ANY AND ALL WARRANTIES (INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT) AND HAVE NO LIABILITY WHATSOEVER RESULTING FROM THE USE OF THIS PRODUCT UNDER THIS TRIAL LICENSE ("Trial License"). BMC may terminate for its convenience a Trial License upon notice to You. When the Trial Period ends, Your right to use this Product automatically expires. If You want to continue Your use of the Product beyond the Trial Period, contact BMC to acquire a capacity-based license to the Product for a fee. TERMINATION. This Agreement shall immediately terminate if You breach any of its terms. Upon termination, for any reason, You must uninstall the Software, and either certify the destruction of the Product or return it to BMC. OWNERSHIP OF THE PRODUCT. BMC or its Affiliates or licensors retain all right, title and interest to and in the BMC Product and all intellectual property, informational, industrial property and proprietary rights therein. BMC neither grants nor otherwise transfers any rights of ownership in the BMC Product to You. BMC Products are protected by applicable copyright, trade secret, and industrial and intellectual property laws. BMC reserves any rights not expressly granted to You herein. CONFIDENTIAL AND PROPRIETARY INFORMATION. The BMC Products are and contain valuable confidential information of BMC ("Confidential Information"). Confidential Information means non-public technical and non-technical information relating to the BMC Products and Support, including, without limitation, trade secret and proprietary information, and the structure and organization of the Software. You may not disclose the Confidential Information to third parties. You agree to use all reasonable efforts to prevent the unauthorized use, copying, publication or dissemination of the Product. WARRANTY. Except for a Trial License, BMC warrants that the Software will perform in substantial accordance with the Documentation for a period of one year from the date of the order. This warranty shall not apply to any problems caused by software or hardware not supplied by BMC or to any misuse of the Software. EXCLUSIVE REMEDY. BMCs entire liability, and Your exclusive remedy, for any defect in the Software during the warranty period or breach of the warranty above shall be limited to the following: BMC shall use reasonable efforts to remedy defects covered by the warranty or replace the defective Software within a reasonable period of time, or if BMC cannot remedy or replace such defective copy of the Software, then BMC shall refund the amount paid by You for the License for that Software. BMCs obligations in this section are conditioned upon Your providing BMC prompt access to the affected Software and full cooperation in resolving the claim. DISCLAIMER. EXCEPT FOR THE EXPRESS WARRANTIES ABOVE, THE PRODUCT IS PROVIDED "AS IS." BMC, ITS AFFILIATES AND LICENSORS SPECIFICALLY DISCLAIM ALL OTHER WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. BMC DOES NOT WARRANT THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR FREE, OR THAT ALL DEFECTS CAN BE CORRECTED. DISCLAIMER OF DAMAGES. IN NO EVENT IS BMC, ITS AFFILIATES OR LICENSORS LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL, PUNITIVE OR CONSEQUENTIAL DAMAGES RELATING TO OR ARISING OUT OF THIS AGREEMENT, SUPPORT, AND/OR THE PRODUCT (INCLUDING, WITHOUT LIMITATION, LOST PROFITS, LOST COMPUTER USAGE TIME, AND DAMAGE OR LOSS OF USE OF DATA), EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND IRRESPECTIVE OF ANY NEGLIGENCE OF BMC OR WHETHER SUCH DAMAGES RESULT FROM A CLAIM ARISING UNDER TORT OR CONTRACT LAW. LIMITS ON LIABILITY. BMCS AGGREGATE LIABILITY FOR DAMAGES IS LIMITED TO THE AMOUNT PAID BY YOU FOR THE LICENSE TO THE PRODUCT. SUPPORT. If Your order includes support for the Software, then BMC agrees to provide support (24 hours a day/7 days a week) ("Support"). You will be automatically re-enrolled in Support on an annual basis unless BMC receives notice of termination from You as provided below. There is a free support period during the one year warranty period. (a) Support Terms. BMC agrees to make commercially reasonable efforts to provide the following Support: (i) For malfunctions of supported versions of the Software, BMC provides bug fixes, patches or workarounds in order to cause that copy of the Software to operate in substantial conformity with its then-current operating specifications; and (ii) BMC provides new releases or versions, so long as such new releases or versions are furnished by BMC to all other enrolled Support customers without additional charge. BMC may refuse to provide Support for any versions or releases of the Software other than the most recent version or release of such Software made available by BMC. Either party may terminate Your enrollment in Support upon providing notice to the other at least 30 days prior to the next applicable Support anniversary date. If You re-enroll in Support, BMC may charge You a reinstatement fee of 1.5 times what You would have paid if You were enrolled in Support during that time period. (b) Fees. The annual fee for Support is 20% of the Softwares list price less the applicable discount or a flat capacity based annual fee. BMC may change its prices for the Software and/or Support upon at least 30 days notice prior to Your support anniversary date.
VERIFICATION. If requested by BMC, You agree to deliver to BMC periodic written reports, whether generated manually or electronically, detailing Your use of the Software in accordance with this Agreement, including, without limitation, the License Capacity. BMC may, at its expense, audit Your use of the Software to confirm Your compliance with the Agreement. If an audit reveals that You have underpaid fees, You agree to pay such underpaid fees. If the underpaid fees exceed 5% of the fees paid, then You agree to also pay BMCs reasonable costs of conducting the audit. EXPORT CONTROLS. You agree not to import, export, re-export, or transfer, directly or indirectly, any part of the Product or any underlying information or technology except in full compliance with all United States, foreign and other applicable laws and regulations. GOVERNING LAW. This Agreement is governed by the substantive laws in force, without regard to conflict of laws principles: (a) in the State of New York, if you acquired the License in the United States, Puerto Rico, or any country in Central or South America; (b) in the Province of Ontario, if you acquired the License in Canada (subsections (a) and (b) collectively referred to as the "Americas Region"); (c) in Singapore, if you acquired the License in Japan, South Korea, Peoples Republic of China, Special Administrative Region of Hong Kong, Republic of China, Philippines, Indonesia, Malaysia, Singapore, India, Australia, New Zealand, or Thailand (collectively, "Asia Pacific Region"); or (d) in the Netherlands, if you acquired the License in any other country not described above. The United Nations Convention on Contracts for the International Sale of Goods is specifically disclaimed in its entirety. ARBITRATION. ANY DISPUTE BETWEEN YOU AND BMC ARISING OUT OF THIS AGREEMENT OR THE BREACH OR ALLEGED BREACH, SHALL BE DETERMINED BY BINDING ARBITRATION CONDUCTED IN ENGLISH. IF THE DISPUTE IS INITIATED IN THE AMERICAS REGION, THE ARBITRATION SHALL BE HELD IN NEW YORK, U.S.A., UNDER THE CURRENT COMMERCIAL OR INTERNATIONAL, AS APPLICABLE, RULES OF THE AMERICAN ARBITRATION ASSOCIATION. IF THE DISPUTE IS INITIATED IN A COUNTRY IN THE ASIA PACIFIC REGION, THE ARBITRATION SHALL BE HELD IN SINGAPORE, SINGAPORE UNDER THE CURRENT UNCITRAL ARBITRATION RULES. IF THE DISPUTE IS INITIATED IN A COUNTRY OUTSIDE OF THE AMERICAS REGION OR ASIA PACIFIC REGION, THE ARBITRATION SHALL BE HELD IN AMSTERDAM, NETHERLANDS UNDER THE CURRENT UNCITRAL ARBITRATION RULES. THE COSTS OF THE ARBITRATION SHALL BE BORNE EQUALLY PENDING THE ARBITRATORS AWARD. THE AWARD RENDERED SHALL BE FINAL AND BINDING UPON THE PARTIES AND SHALL NOT BE SUBJECT TO APPEAL TO ANY COURT, AND MAY BE ENFORCED IN ANY COURT OF COMPETENT JURISDICTION. NOTHING IN THIS AGREEMENT SHALL BE DEEMED AS PREVENTING EITHER PARTY FROM SEEKING INJUNCTIVE RELIEF FROM ANY COURT HAVING JURISDICTION OVER THE PARTIES AND THE SUBJECT MATTER OF THE DISPUTE AS NECESSARY TO PROTECT EITHER PARTYS CONFIDENTIAL INFORMATION, OWNERSHIP, OR ANY OTHER PROPRIETARY RIGHTS. ALL ARBITRATION PROCEEDINGS SHALL BE CONDUCTED IN CONFIDENCE, AND THE PARTY PREVAILING IN ARBITRATION SHALL BE ENTITLED TO RECOVER ITS REASONABLE ATTORNEYS FEES AND NECESSARY COSTS INCURRED RELATED THERETO FROM THE OTHER PARTY. U.S. GOVERNMENT RESTRICTED RIGHTS. The Software under this Agreement is "commercial computer software" as that term is described in 48 C.F.R. 252.227-7014(a)(1). If acquired by or on behalf of a civilian agency, the U.S. Government acquires this commercial computer software and/or commercial computer software documentation subject to the terms of this Agreement as specified in 48 C.F.R. 12.212 (Computer Software) and 12.211 (Technical Data) of the Federal Acquisition Regulations ("FAR") and its successors. If acquired by or on behalf of any agency within the Department of Defense ("DOD"), the U.S. Government acquires this commercial computer software and/or commercial computer software documentation subject to the terms of this Agreement as specified in 48 C.F.R. 227.7202 of the DOD FAR Supplement and its successors. MISCELLANEOUS TERMS. You agree to pay BMC all amounts owed no later than 30 days from the date of the applicable invoice, unless otherwise provided on the order for the License to the Products. You will pay, or reimburse BMC, for taxes of any kind, including sales, use, duty, tariffs, customs, withholding, property, value-added (VAT), and other similar federal, state or local taxes (other than taxes based on BMCs net income) imposed in connection with the Product and/or the Support. This Agreement constitutes the entire agreement between You and BMC and supersedes any prior or contemporaneous negotiations or agreements, whether oral, written or displayed electronically, concerning the Product and related subject matter. No modification or waiver of any provision hereof will be effective unless made in a writing signed by both BMC and You. You may not assign or transfer this Agreement or a License to a third party without BMCs prior written consent. Should any provision of this Agreement be invalid or unenforceable, the remainder of the provisions will remain in effect. The parties have agreed that this Agreement and the documents related thereto be drawn up in the English language. Les parties exigent que la prsente convention ainsi que les documents qui sy rattachent soient rdigs en anglais.
SW EULA Int 030102
Notes
*42890* *42890* *42890* *42890*

*42890*

Pco Web Edition

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Pco Web Edition

Загружено:

Авторское право:

Доступные форматы

PATROL Central Operator Web Edition Getting Started

December 31, 2003

Restricted Rights Legend

Contacting BMC Software

United States and Canada

Outside United States and Canada

Support Web Site

Support by Telephone or E-mail

Before Contacting BMC Software

BMC Software, Inc., Confidential and Proprietary Information

BMC Software, Inc., Confidential and Proprietary Information

PATROL Central Operator Web Edition Getting Started

Monitoring and Managing Your Enterprise with PATROL Central Operator

PATROL Central Operator Web Edition Getting Started

A-2 A-2 A-3 A-3

BMC Software, Inc., Confidential and Proprietary Information

PATROL Central Operator Web Edition Getting Started

Modifying Initialization Settings After Installation

BMC Software, Inc., Confidential and Proprietary Information

BMC Software, Inc., Confidential and Proprietary Information

PATROL Central Operator Web Edition Getting Started

Product Components and Capabilities

BMC Software, Inc., Confidential and Proprietary Information

Product Components and Capabilities

PATROL Central Operator Features

BMC Software, Inc., Confidential and Proprietary Information

PATROL Central Operator Web Edition Getting Started

How PATROL Central Operator Fits into PATROL Central

BMC Software, Inc., Confidential and Proprietary Information

Product Components and Capabilities

How PATROL Central Operator Fits into PATROL

BMC Software, Inc., Confidential and Proprietary Information

PATROL Central Operator Web Edition Getting Started

PATROL Architecture for the Web Edition of PATROL Central Operator

PATROL Console Server

BMC Software, Inc., Confidential and Proprietary Information

Product Components and Capabilities

BMC Software, Inc., Confidential and Proprietary Information

PATROL Central Operator Web Edition Getting Started

Accessing Online Help

In the toolbar area, click the page help icon.

application instances and classes parameters

BMC Software, Inc., Confidential and Proprietary Information

Product Components and Capabilities

Accessing Books and Release Notes

Where to Go from Here

Chapter 5, Configuring the PATROL Central Console Environment

Chapter 6, Using the PATROL 3.x and PATROL 7.x Consoles

Chapter 7, Troubleshooting PATROL Central Operator

BMC Software, Inc., Confidential and Proprietary Information

PATROL Central Operator Web Edition Getting Started

Installing PATROL Central Operator 2

BMC Software, Inc., Confidential and Proprietary Information

Installing PATROL Central Operator

The PATROL 7.x Environment

BMC Software, Inc., Confidential and Proprietary Information

PATROL Central Operator Web Edition Getting Started

Considerations for Determining Which Web Server to Use

Available Web Servers

About the Tomcat Servlet Container

Installing PATROL Central Operator

Apache Web Server with Tomcat Servlet Container (Unix)

BMC Software, Inc., Confidential and Proprietary Information