Wyapm Install and Upgrade

Installation and Upgrade Guide Version 9.0

CA Wily Application Performance Management

This documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA.

Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

Copyright © 2011 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

CA Technologies Product References

This document references the following CA Technologies products:

■ CA SiteMinder®

■ CA Spectrum® Infrastructure Manager

■ CA SYSVIEW® Performance Management

■ CA Wily Extension for CA SYSVIEW®

■ CA Wily Introscope®

■ CA Wily Introscope® ErrorDetector™

■ CA Wily Introscope® ChangeDetector™

■ CA Wily Introscope® PowerPack™ for CA SiteMinder Web Access Manager

■ CA Wily Introscope® PowerPack™ for BEA Tuxedo Connectors

■ CA Wily Introscope® PowerPack™ for BEA WebLogic Integration

■ CA Wily Introscope® PowerPack™ for BEA WebLogic Server

■ CA Wily Introscope® PowerPack™ for IBM CICS Transaction Gateway

■ CA Wily Introscope® PowerPack™ for IBM WebSphere Business Integration Adapters

■ CA Wily Introscope® PowerPack™ for IBM WebSphere Application Server

■ CA Wily Introscope® PowerPack™ for IBM WebSphere MQ

■ CA Wily Introscope® PowerPack™ for IBM z/OS

■ CA Wily Introscope® PowerPack™ for Oracle Database

■ CA Wily Introscope® PowerPack™ for SharePoint Portal

■ CA Wily Introscope® PowerPack™ for Web Servers

■ CA Wily Introscope® for Microsoft .NET

■ CA Wily Introscope® for SAP NetWeaver

■ CA Wily Introscope® for SAP ABAP

■ CA Wily Introscope® Integration Pack for CA NSM

■ CA Wily Introscope® LeakHunter™

■ CA Wily Introscope® SNMP Adapter™

■ CA Wily Introscope® PowerPack™ for IBM WebSphere Application Server for Distributed Environments

Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ CA Support policies and guidelines

■ Other helpful resources appropriate for your product

Provide Feedback

If you have comments or questions about CA Technologies product documentation, you can send a message to [email protected].

If you would like to provide feedback about CA Technologies product documentation, complete our short customer survey, which is available on the CA Support website at http://ca.com/docs.

http://www.ca.com/support

mailto:[email protected]

http://www.ca.com/docs

http://www.ca.com/docs

Contents 5

Contents

Chapter 1: Introduction 13

What’s new in the CA Wily APM Installation and Upgrade Guide ....................................... 13

One installation and upgrade guide for Introscope and Wily CEM ................................... 14

Wily CEM TESS integrated with the Enterprise Manager ........................................... 14

Enterprise Manager installer includes the new APM database ...................................... 14

PowerPack files and extensions included with Introscope .......................................... 15

Additional standalone PowerPack installer ...................................................... 15

TIM is now a software appliance .............................................................. 15

Updated APM Database information for PostgreSQL and Oracle users ............................... 15

Other new information ...................................................................... 16

CA Wily APM architecture highlights ............................................................... 16

About directory and file naming conventions ........................................................ 17

Where to go for more information ................................................................ 17

Product documentation ..................................................................... 17

Chapter 2: Planning the deployment 21

Evaluating the environment ...................................................................... 21

Determining the database to use ................................................................. 22

Deciding whether to install the APM database as a separate component ................................. 23

Chapter 3: Preparing for install or upgrade 25

Enterprise Manager requirements ................................................................ 26

Enterprise Manager JVM requirements ......................................................... 26

Enterprise Manager operating system requirements .............................................. 27

Enterprise Manager memory requirements ..................................................... 27

Enterprise Manager disk space requirements .................................................... 27

SmartStor database requirements ............................................................. 28

Transaction Events database requirements ..................................................... 28

baselines database requirements ............................................................. 28

Enterprise Manager temporary directory space requirements ...................................... 28

Enterprise Manager Services requirements ..................................................... 28

Enterprise Manager Internet Protocol requirements .............................................. 29

APM database requirements ..................................................................... 29

Using PostgreSQL for the APM database ........................................................ 30

Using Oracle for the APM database ............................................................ 31

Selecting a user account to run the installer ..................................................... 34

6 Installation and Upgrade Guide

Workstation requirements ....................................................................... 34

Workstation JVM requirements ............................................................... 35

Workstation operating system requirement ..................................................... 35

Workstation disk space and memory requirements ............................................... 35

Workstation Java Web Start requirements ...................................................... 35

WebView requirements ......................................................................... 36

Wily CEM console requirements .................................................................. 36

About Wily CEM TIM requirements and recommendations ............................................ 36

TIM minimum requirements .................................................................. 37

TIM recommendations ...................................................................... 37

About security requirements ................................................................. 37

Creating the TIM DVD ....................................................................... 38

PowerPack and extension requirements ............................................................ 38

Other requirements ............................................................................ 40

JAR installer requirements ................................................................... 40

ProbeBuilder requirements .................................................................. 40

Platform support for Java 1.6 ................................................................. 40

SNMP requirements ........................................................................ 41

About upgrade requirements ..................................................................... 41

Introscope upgrade requirements ............................................................. 42

Wily CEM upgrade requirements .............................................................. 42

Upgrade paths ............................................................................. 43

About the installation files ....................................................................... 43

Introscope installers ........................................................................ 43

External component packages ................................................................ 51

Wily CEM installation files .................................................................... 51

CA Embedded Entitlements Manager installation files ............................................ 52

About installation modes ........................................................................ 52

About APM time settings ........................................................................ 53

Post-install password security .................................................................... 54

Default connection URLs ........................................................................ 55

Chapter 4: Installation checklist 57

Chapter 5: Installing Introscope in GUI or console mode 59

Launching installers in GUI mode on Windows systems ............................................... 59

Launching installers in GUI mode on UNIX systems ................................................... 60

Using GUI mode on UNIX systems with a desktop environment ..................................... 60

Using GUI mode on UNIX systems without a desktop environment .................................. 60

Launching the installer in console mode ............................................................ 61

Launching .BIN installers in console mode ...................................................... 62

Contents 7

Launching .JAR installers in console mode ...................................................... 63

Launching the console mode installer on OS/400 / IBMi ........................................... 63

Launching the console mode installer on z/OS ................................................... 64

Installing Introscope main components ............................................................ 65

Specifying the install directory, external components, and licenses .................................. 66

Specifying the Enterprise Manager ............................................................ 68

Specifying the APM database ................................................................. 70

Specifying WebView settings ................................................................. 75

Specifying ProbeBuilder advanced JVM settings .................................................. 75

Completing the installation ................................................................... 76

Copying the Introscope license after installation ................................................. 76

Verifying the Enterprise Manager installation ................................................... 76

Installing the Workstation ....................................................................... 77

Verifying the Workstation installation .......................................................... 78

Installing the Workstation using Java Web Start .................................................. 79

Uninstalling Introscope .......................................................................... 81

Removing Introscope on z/OS ................................................................ 82

Forcing an uninstall mode .................................................................... 82

Chapter 6: Installing Introscope in silent mode 85

Preparing for silent mode installation .............................................................. 85

Silent mode installation overview ............................................................. 85

Using a response file ........................................................................ 86

Downloading and editing external files ......................................................... 87

Silent mode installation settings .................................................................. 87

Main installer silent mode settings ............................................................ 88

Standalone PowerPack installer silent mode settings ............................................ 114

SAP installer silent mode settings ............................................................ 117

Launching silent mode installers ................................................................. 118

Launching silent mode installer on z/OS ....................................................... 118

Launching silent mode installer on other platforms .............................................. 119

About silent mode errors ................................................................... 119

Chapter 7: Installing Introscope PowerPacks and extensions 121

About the PowerPacks and extensions ............................................................ 122

LeakHunter installation ..................................................................... 124

ErrorDetector installation ................................................................... 124

ChangeDetector installation ................................................................. 125

SNMP Adapter installation .................................................................. 125

SYSVIEW installation ....................................................................... 125

CA Wily APM Web Services APIs .............................................................. 126


Installing a standalone PowerPack ............................................................... 127

Chapter 8: Installing Wily CEM 129

Installing and configuring a TIM .................................................................. 129

Installing the operating system for a new TIM (kickstart DVD) ..................................... 130

Configuring the TIM network management settings ............................................. 133

Installing TIM software ..................................................................... 135

Setting the time zone on a TIM .............................................................. 137

Configuring the TIM network monitor interface ................................................. 138

Wily CEM post-install configuration on the Enterprise Manager ................................... 139

Accessing the Wily CEM console and setup pages ................................................... 142

Accessing the Wily CEM console ............................................................. 142

Accessing the Wily System Setup page for the TIM .............................................. 144

Troubleshooting login to Wily CEM ........................................................... 144

Accessing the TIM from the Wily CEM console .................................................. 145

Verifying Wily CEM configurations ............................................................... 145

Verifying TIM configuration ................................................................. 146

Verifying communication between the TIM and Enterprise Manager ............................... 146

Shutting down and restarting a TIM .............................................................. 147

Uninstalling a TIM ............................................................................. 148

Chapter 9: Upgrading to CA Wily APM 9.x 149

Determining the current and target environments .................................................. 149

Determining the upgrade path ................................................................... 150

Pros and cons of upgrading products one at a time .............................................. 150

Pros and cons of upgrading products at the same time ........................................... 151

Summary of upgrade paths .................................................................. 151

Preparing for all upgrades ...................................................................... 152

Preparing for Introscope-related upgrades ......................................................... 153

Main points to be aware of when upgrading Introscope .......................................... 153

Introscope component version compatibility ................................................... 154

Introscope automatic and manual upgrade information .......................................... 155

What to do before upgrading Introscope ...................................................... 156

Preparing for Wily CEM-related upgrades ......................................................... 158

Main points to be aware of when upgrading Wily CEM ........................................... 159

What to do before upgrading Wily CEM ....................................................... 159

Upgrading from Introscope ..................................................................... 160

Upgrading a standalone Introscope: architecture overview ....................................... 162

Upgrading a clustered Introscope: architecture overview ......................................... 165

Introscope upgrade workflow................................................................ 167

Introscope upgrade workflow details ......................................................... 170

Contents 9

Adding Wily CEM to an upgraded Introscope ................................................... 172

Upgrading from CA Wily APM ................................................................... 173

Upgrading CA Wily APM: architecture overview ................................................. 173

CA Wily APM upgrade workflow ............................................................. 176

CA Wily APM upgrade workflow details ....................................................... 177

Upgrading from Wily CEM ...................................................................... 179

Upgrading Wily CEM: architecture overview.................................................... 180

Wily CEM upgrade workflow ................................................................ 182

Wily CEM upgrade workflow details .......................................................... 183

Adding Introscope to an upgraded Wily CEM ................................................... 186

Chapter 10: Upgrading Wily CEM components 187

Backing up and restoring TIM configuration data ................................................... 187

Upgrading a TIM .............................................................................. 189

Configuring the Enterprise Manager for Wily CEM post-upgrade ....................................... 190

Copying the previous Wily CEM configuration properties ......................................... 190

Copying the defect evidence files ............................................................. 191

Specifying customized CA Service Desk settings ................................................. 191

Copying plug-ins ........................................................................... 191

Unblocking ports on a former Wily CEM appliance .................................................. 192

Changing the TIM System Setup Page password .................................................... 194

Uninstalling 4.5.x TESS ......................................................................... 194

Cleaning up a 4.5.x TESS machine for re-use .................................................... 195

Chapter 11: Migrating the APM database 196

Upgrading the APM database (special cases) ....................................................... 197

Upgrading the 4.5 PostgreSQL from a Wily CEM installation (overview) ............................. 197

Upgrading the 4.5 PostgreSQL from a CA Wily APM installation, one product at a time (overview) ....... 198

Upgrading the 4.5 PostgreSQL database ....................................................... 199

Merging Introscope and Wily CEM databases during upgrade ..................................... 201

Upgrading PostgreSQL ...................................................................... 203

Exporting and restoring the APM database ........................................................ 204

Exporting an APM database on PostgreSQL .................................................... 204

Restoring an APM database from a backup file (PostgreSQL) ...................................... 206

Moving the APM database to a different machine .................................................. 209

Moving the APM database to another operating system ............................................. 210

Migrating data from a PostgreSQL database to an Oracle database .................................... 210

Customizing migration properties ............................................................ 212

Running more than one instance of the migration script .......................................... 214

Changing and verifying APM database settings ..................................................... 214

Specifying APM database settings after installation .............................................. 214


Changing the default passwords for a PostgreSQL database instance ............................... 215

Verifying the schema version of the APM database .............................................. 216

Configuring PostgreSQL on Linux or Solaris ........................................................ 216

Troubleshooting the non-root PostgreSQL installation on Solaris ...................................... 217

Uninstalling APM database software or data ....................................................... 217

Removing the APM database schema from PostgreSQL .......................................... 218

Removing the APM database schema from Oracle ............................................... 219

Uninstalling PostgreSQL .................................................................... 220

Chapter 12: Upgrading Introscope 223

Upgrading Enterprise Managers and databases (GUI or console modes) ................................ 223

Starting the installer and specifying the install set ............................................... 224

Specifying the upgrade location, external components, and licenses ................................ 225

Renaming Windows Service names ........................................................... 225

Specifying external components and license ................................................... 226

Specifying the APM database during upgrade .................................................. 226

Confirming the upgrade .................................................................... 227

About silent mode upgrades .................................................................... 228

Editing the upgrade response file ............................................................. 228

Upgrading other Introscope elements ............................................................ 230

Upgrading the Workstation ................................................................. 231

Upgrading the bytecode, agents, and platform monitors ......................................... 231

Applying agent customizations ............................................................... 232

Upgrading PowerPacks and extensions ........................................................ 232

Completing the upgrade ........................................................................ 233

Chapter 13: Upgrading security 235

About upgrading Wily CEM operators ............................................................. 235

Upgrading Wily CEM operators to CA EEM users and groups .......................................... 236

What to do before upgrading Wily CEM 4.5.x operators to CA EEM ................................. 237

Exporting Wily CEM operators to XML ......................................................... 237

Adding the exported Wily CEM operators into CA EEM ........................................... 239

Verifying Wily CEM users authorization in CA EEM .............................................. 240

Resetting passwords for Wily CEM users in CA EEM.............................................. 241

Removing Wily CEM users and groups after uninstalling Wily CEM ..................................... 241

Upgrading from Wily CEM operators to Local users ................................................. 242

Merging Wily CEM users from the usersCEM45.xml into the users.xml file (Realm Option 1) ............ 243

Creating a new Local realm for Wily CEM users and groups (Realm option 2) ......................... 244

About the Introscope security upgrade ............................................................ 244

Contents 11

Appendix A: Using the installation worksheet 245

Do you want to configure JVM settings? ........................................................... 246

What’s the location of the external component package archive file? .................................. 246

What’s the location of the CA Wily license file? ..................................................... 247

What are the Enterprise Manager ports? .......................................................... 247

Should the Enterprise Manager be part of a cluster? ................................................ 248

If the Enterprise Manager is part of a cluster, is it the MOM or a Collector? ............................. 248

How long do you store your Transaction Event data? ................................................ 249

Where do you store your Transaction Event data? .................................................. 249

Where do you store the SmartStor database? ...................................................... 249

Where do you store the APM database? .......................................................... 249

What port does the APM database use? ........................................................... 250

What is the APM database instance name, usernames, and passwords? ................................ 250

Does the Enterprise Manager run as a Windows Service? ............................................ 251

What ports and host does WebView use? ......................................................... 251

What are the TIM’s network settings? ............................................................ 252

Appendix B: Manual upgrade and upgrade change summary 253

Manually upgrading Introscope .................................................................. 253

Manual configuration file upgrade overview ................................................... 254

Manually upgrading the Enterprise Manager ................................................... 256

Manually upgrading WebView ............................................................... 257

Completing the Enterprise Manager manual upgrade ............................................ 259

About file changes during an Introscope upgrade ................................................... 260

How the upgrade handles properties files ...................................................... 261

Files and properties that Introscope upgrades .................................................. 261

Files and properties that Introscope does not upgrade ........................................... 263

Introscope files that the installer moves or copies during upgrade ................................. 265

Creating the APM database schema manually ...................................................... 267

Running individual SQL scripts to manage the APM database schema ............................... 269

Appendix C: Using the Lynx text browser on a TIM 273

Installing TIM software using the Lynx browser ..................................................... 273

Keyboard tips for the Lynx browser ........................................................... 275

Using Lynx to configure Wily CEM ................................................................ 275

Index 277


Chapter 1: Introduction

Welcome to CA Wily Application Performance Management 9.x (CA Wily APM). This release includes many new features for CA Wily APM, which includes both CA Wily Introscope 9.x and CA Wily Customer Experience Manager 5.0 (Wily CEM).

This guide describes how to install or upgrade CA Wily APM.

For information related to installing agents, see the Introscope Java Agent Guide and Introscope .NET Agent Guide. For SYSVIEW and ChangeDetector installation details, see the CA SYSVIEW Integration Pack User Guide and the CA Wily Introscope ChangeDetector User Guide.

IMPORTANT! Before installing or upgrading CA Wily APM, CA Wily Introscope, and Wily CEM, you should read the CA Wily APM Known Issues and the CA Wily APM ReadMe (or Introscope ReadMe if you have an Introscope only implementation). The ReadMe files are a part of your downloaded product archive; the Known Issues document is available only on the product download site, at the same level as your product download.

This section contains the following topics:

What’s new in the CA Wily APM Installation and Upgrade Guide (see page 13) CA Wily APM architecture highlights (see page 16) About directory and file naming conventions (see page 17) Where to go for more information (see page 17)

What’s new in the CA Wily APM Installation and Upgrade Guide

The following sections detail new or changed features in CA Wily APM 9.0 that affect installation and upgrade.


One installation and upgrade guide for Introscope and Wily CEM (see page 14) Wily CEM TESS integrated with the Enterprise Manager (see page 14) Enterprise Manager installer includes the new APM database (see page 14) PowerPack files and extensions included with Introscope (see page 15) Additional standalone PowerPack installer (see page 15) TIM is now a software appliance (see page 15) Updated APM Database information for PostgreSQL and Oracle users (see page 15) Other new information (see page 16)



One installation and upgrade guide for Introscope and Wily CEM

In prior releases, there was an Introscope Installation and Upgrade Guide and a Wily CEM Installation and Upgrade Guide. In this release, there is one installation and upgrade guide for CA Wily APM, which covers installation and upgrade for Introscope, CA Wily APM, and Wily CEM.

Wily CEM TESS integrated with the Enterprise Manager

When you install the Enterprise Manager, the Wily CEM services formerly known as Transaction Events and Statistics Server (TESS) now are installed along with the Enterprise Manager. There is no longer a TESS in Wily CEM. You access the Wily CEM console from the Enterprise Manager.

For an architecture overview, see CA Wily APM architecture highlights (see page 16).

Enterprise Manager installer includes the new APM database

In CA Wily APM 9.x, the APM database stores data for both Wily CEM and Introscope. The APM database stores business transaction and defect-related data for Wily CEM and application triage map data for Introscope.

When you install the Enterprise Manager, you can choose the type of APM database you want to use. If you select PostgreSQL, you have the option to install a new database instance and schema, connect to an existing APM database schema, or upgrade a previously installed APM database schema. If you select Oracle, you must connect to an existing Oracle database instance, but can then install a new APM database schema in that database, connect to an existing APM database schema, or upgrade a previously installed APM database schema.

Note that in addition to the APM database, Introscope continues to use other databases, such as the SmartStor, baselines, and Transaction Events databases.



PowerPack files and extensions included with Introscope

Many PowerPacks and extensions that you used to install separately have files that are automatically installed along with the Enterprise Manager. This includes extensions such as ChangeDetector, ErrorDetector, LeakHunter, SNMP Adapter, SYSVIEW, and Web Services APIs.

Although these PowerPacks and extensions have files that are automatically installed with the Enterprise Manager, the agent installers and standalone PowerPack installer provide additional files.

The PowerPacks require some post-install configuration before you can use them.

Additional standalone PowerPack installer

For PowerPacks that operate outside of or in addition to a Java or .NET agent, the standalone PowerPack installer provides additional files.

TIM is now a software appliance

For new customers, you install a Transaction Impact Monitor (TIM) as software on a machine that you provide. CA Wily provides the operating system and other files needed to run a TIM. For TIM machine requirements and recommendations, see About Wily CEM TIM requirements and recommendations.

If you are an existing customer, continue using your existing CA Wily TIM machines and upgrade them to the new TIM software version.

Updated APM Database information for PostgreSQL and Oracle users

This guide has a number of changes related to the APM database:

■ APM database using Oracle information is now integrated into this guide. Previously this information was in the CA Wily APM ReadMe.

■ CA Wily APM 9.0.6 information for the APM database using PostgreSQL, including how to upgrade to the updated version.

■ APM database section is now a separate chapter so that it's easier to find and navigate.

CA Wily APM architecture highlights


Other new information

This guide now includes information on the following:

■ Planning the deployment (see page 21)

■ About CA Wily APM time settings (see page 53)

■ Default connection URLs (see page 55)

■ Creating the TIM DVD (see page 38)

CA Wily APM architecture highlights

This section provides a brief introduction to the key architecture changes in this CA Wily APM release. For a more detailed explanation of CA Wily APM and all components, see the CA Wily APM Overview Guide.

From the point of view of component architecture, this CA Wily APM release has the following changes:

■ Introscope and Wily CEM both store information in the APM database. The APM database stores information that is required for recording and monitoring business service transactions, managing and reporting on service degradation, and tracking relationships between components in the application triage map.

■ The Transaction Events and Statistics Server (TESS) is no longer a separate component of Wily CEM. The Transaction Events and Statistics Server (TESS) functionality is now part of the Enterprise Manager.

■ The Enterprise Manager now connects to the TIMs.

■ The TIM Collection, Stats Aggregation, and Database cleanup services that are required for Wily CEM are now Enterprise Manager services that you must distribute across Collectors.

■ You access the Wily CEM console from the MOM.

■ CA Wily APM deployments require a cluster of Enterprise Managers. Running CA Wily APM with a standalone Enterprise Manager is not supported.

About directory and file naming conventions


About directory and file naming conventions

This guide uses the following conventions in file names and directory paths:

■ <Agent_Home>: The top-level directory where the Introscope agent is installed. This directory is typically named wily.

■ <EM_Home>: The top-level directory where the Enterprise Manager is installed.

■ <APM_Db_Home>: The top-level directory where the APM database is installed, when referring to Database-only installations.

■ <version>: Introscope or Wily CEM version-specific identifier included in file names or displayed in the user interface. For example, the following file name introscope<version>windows.exe represents a version-specific file name, such as introscope9.0.5.0windows.exe.

Where to go for more information

Each product comes with its own documentation and unique set of resources. This section gives you an overview of other resources available to you.

Product documentation

The following tables list the titles in the CA Wily APM documentation set. All these titles can be viewed and searched from the CA Wily APM bookshelf:

■ CA Wily APM documentation (see page 17)

■ Introscope documentation (see page 18)

■ Wily CEM documentation (see page 19)

■ Introscope PowerPack documentation (see page 19)

CA Wily APM documentation

This is the documentation unique for CA Wily APM. This documentation is pertinent to both Introscope and Wily CEM.

■ CA Wily APM ReadMe — Release summary and readme information for CA Wily APM.

■ CA Wily APM Known Issues — Important last-minute release information for CA Wily APM; available on the product download site or the Wily Community Site.

Note: This document is not in the product build.

■ CA Wily APM Glossary — Terms and concepts for CA Wily APM.



■ CA Wily APM Installation and Upgrade Guide — Installation requirements; installing CA Wily APM, including installing Introscope Enterprise Manager, APM database, Workstation, WebView, Wily CEM, TIM; upgrading from previous releases.

■ CA Wily APM Overview Guide — A broad overview of CA Wily APM components and architecture. Explains terms and concepts used in a CA Wily APM deployment.

■ CA Wily APM Security Guide — Choosing and configuring CA Wily APM, Introscope, and Wily CEM security solutions.

■ CA Wily APM Sizing and Performance Guide — Sizing, tuning, and capacity planning for your CA Wily APM deployment and components.

■ CA Wily APM Transaction Definition Guide — Transaction definition processes and procedures for CA Wily APM; describes the necessary steps to record, define, and verify customer transactions.

Introscope documentation

This is the documentation unique for Introscope. The CA Wily APM documentation is also pertinent for Introscope.

■ Introscope ReadMe — Release summary and readme information for Introscope. This is a subset of the CA Wily APM ReadMe.

■ Introscope ChangeDetector User Guide — Using Introscope ChangeDetector to monitor and report changes in application files and configuration.

■ Introscope Configuration and Administration Guide — Administering the Enterprise Manager; working with management modules and dashboards; using the command line Workstation. Includes Introscope properties reference.

■ Introscope Environment Performance Agent Guide — Implementing Environment Performance Agent (EPAgent) with Introscope to monitor system information, including process availability, disk statistics, web application server and web server logs, Solaris KStat and HTTP service availability. The guide provides instructions for installing, configuring, and using EPA.

■ Introscope Extension for CA SYSVIEW Guide — Installing, configuring, and using the SYSVIEW Agent extension, which allows you to manage application performance of distributed applications accessing mainframe back ends and trace transactions from distributed applications to mainframe CICS transactions. It also lets you monitor the health metrics of critical mainframe components.

■ Introscope Java Agent Guide — Installation, configuration, and use of the Wily Introscope Java Agent.

■ Introscope .NET Agent Guide — Installation, configuration, and use of the Wily Introscope .NET Agent.

■ Introscope SOA Performance Management Implementation Guide — Installation and configuration information for using SOA Performance Management and SOA platform extensions with Introscope.



■ Introscope WebView Guide — Using WebView to view Introscope data in dashboards and Investigator.

■ Introscope WebView Guide for SAP — This guide on how to view Introscope data in dashboards, Investigator, and Transaction Tracer, is for WebView for SAP users.

■ Introscope Workstation User Guide — Using Introscope dashboards, Investigator tree and application triage map, Transaction Tracer, and reporting. Introscope metrics overview and descriptions.

Wily CEM documentation

This is the documentation unique for Wily CEM. The CA Wily APM documentation is also pertinent for Wily CEM.

■ Wily CEM Configuration and Administration Guide — Networking, administration, and configuration information for the Wily CEM administrator.

■ Wily CEM Integration Guide — Integration of CA Wily APM and CA Technologies products (such as CA SiteMinder, CA NSM, CA Service Desk, Wily Transaction Generator, and CA CMDB) with CA Wily CEM.

■ Wily Transaction Generator Implementation Guide — Using the CA Wily Transaction Generator (WTG) to monitor the availability, health, and performance of web sites and web services from the perspective of a user attempting to access web sites. How to use the WTG Agent to generate synthetic transactions that you can monitor using Wily CEM and Introscope.

Introscope PowerPack documentation

This is the documentation for PowerPacks.

■ PowerPack for CA SiteMinder Web Access Manager Guide — Installing, configuring, and using the PowerPack for CA SiteMinder Web Access Manager.

■ PowerPack for IBM WebSphere Application Server Distributed Environments Guide — Installing, configuring and using the CA Wily PowerPack for IBM WebSphere Application Server Distributed.

■ PowerPack for Oracle Database Guide — Installing, configuring, and using the CA Wily PowerPack for Oracle Database.

■ PowerPack for SharePoint Portal Guide — Installing and configuring the PowerPack for SharePoint Portal to monitor your SharePoint Portal components during development, QA, staging, and production.

■ PowerPack for SiteMinder SNMP Collector Guide — Installing and configuring the PowerPack for CA Wily SiteMinder SNMP Collector. Understanding the associated metrics.

■ PowerPack for Web Servers Guide — Installing, configuring, and using the CA Wily PowerPack for Web Servers.



■ PowerPack for WebLogic Portal — Installing, configuring, and using the CA Wily PowerPack for WebLogic Portal.

■ PowerPack for WebLogic Server Guide — Installing, configuring, and using the Introscope PowerPack for WebLogic Server.

■ PowerPack for IBM WebSphere MQ Connectors and Messaging System Guide — Using Introscope to view metrics from IBM WebSphere MQ.

■ PowerPack for WebSphere Portal Guide — Installing, configuring, and using the CA Wily PowerPack for WebSphere Portal.

Note: Portions of this manual offer examples of commands, code, XML or other text printed in plain text. If you use the PDF version of this manual as a source from which to copy such text for use as a template or example for your implementation, you may copy extraneous characters that are invisible vestiges of the PDF conversion process. To avoid this issue, use the HTML version of this manual, contained in the Introscope Workstation Help system, as a source for plain text.


Chapter 2: Planning the deployment

Before you install or upgrade to CA Wily APM, you should do some initial planning to determine what components you need to install and where, to scope the time and resources required, and to collect the information you'll need to complete the deployment successfully. Because the performance of the Enterprise Manager and the maintenance and scalability of the APM database are keys to a successful deployment, your planning should also include an evaluation of your environment to determine the type of database best suited to your needs. This section provides information to help you with the planning process.


Evaluating the environment (see page 21) Determining the database to use (see page 22) Deciding whether to install the APM database as a separate component (see page 23)

Evaluating the environment

An important step in planning an installation or upgrade is to evaluate your existing environment and determine how and where you will deploy the components you intend to use. You should also consider what you plan to monitor and the depth and breadth of metrics you plan to collect. For example, if you are installing components to monitor application performance in a development or testing lab or in an isolated network for evaluation purposes, your requirements are different from the requirements for monitoring applications in a high-volume production environment.

From the information you collect about your environment, you can identify the system requirements appropriate for your deployment scenario and tune them as needed to suit your applications and monitoring level. This guide provides a summary of the minimum system requirements for the Enterprise Manager and other components. You should also consult the CA Wily APM Sizing and Performance Guide for examples of different deployment scenarios and configuration recommendations.

Before you install or upgrade, you should:

■ Identify the characteristics of the environment to be monitored

■ Decide on the type of database you should use

■ Review the system requirements and supported environments for the type of database you want to install

■ Review the supported upgrade and migration paths if you are upgrading from a previous release

Determining the database to use


Determining the database to use

Because CA Wily APM offers a choice of databases, one key decision you need to make in planning your deployment is the type of database you want to use. There are several factors you should consider to determine the database that best suits your needs. For example, the PostgreSQL database is easy to install and requires minimal configuration and ongoing management. The PostgreSQL database can also be installed automatically from the Enterprise Manager installer and typically does not require a separate database administrator to install or maintain data integrity and control user access. However, the PostgreSQL database does have some limitations that make it unsuitable for some deployment scenarios or organizations.

In general, you should consider whether the following apply to determine if you should use PostgreSQL or Oracle as your database platform or if you should plan to migrate from PostgreSQL to Oracle for the APM database:

■ If you don't already have a database instance installed, you can use the Enterprise Manager installer to install PostgreSQL without any preconfiguration.

■ If you want to minimize database maintenance and keep the configuration of your environment as simple as possible, using the PostgreSQL database provides an easier alternative to using an Oracle database.

■ If you are managing the APM database without the support of a database administrator group, the PostgreSQL database requires less management overhead, specialized knowledge, and database-specific skills.

■ If your organization has standardized on a specific vendor's database, you may be required to use that database platform.

■ If you have existing database administrator resources and procedures in place for a specific database platform, you may be able to best leverage those resources by using that database platform.

■ If you do not have an existing database administrator, it may be more difficult for you to install, configure, and manage Oracle than a PostgreSQL database.

■ If your organization has complex database configuration requirements, you may need more advanced configuration and management options than PostgreSQL provides.

■ If you are monitoring a high-volume production environment, you may require a more robust and scalable database than PostgreSQL provides.

Deciding whether to install the APM database as a separate component


Deciding whether to install the APM database as a separate component

You can choose to install the APM database independent of the Enterprise Manager or other components. For example, you may want to install the database schema on a separate, dedicated database server or prepare the database schema in the planning phase before you set up the Enterprise Manager connection to it. Because the APM database is often hosted on a separate server, it is common to use the Database Only installation option once, and then connect to that APM database using the existing schema option when you install other components.

If you want to install the APM database schema on its own and it is a PostgreSQL database, you can create a new database instance or use an existing database instance directly from the installer. For PostgreSQL, you can also create the database administrator account and APM database owner during the installation process.

If you want to install the APM database schema for Oracle, however, the Oracle database instance must already exist and you must have at least one Oracle database user account that you can use to connect to the database instance.


Chapter 3: Preparing for install or upgrade

This chapter lists supported environments and required resources for Application Performance Management components other than the agent.


Enterprise Manager requirements (see page 26) APM database requirements (see page 29) Workstation requirements (see page 34) WebView requirements (see page 36) Wily CEM console requirements (see page 36) About Wily CEM TIM requirements and recommendations (see page 36) PowerPack and extension requirements (see page 38) Other requirements (see page 40) About upgrade requirements (see page 41) About the installation files (see page 43) About installation modes (see page 52) About APM time settings (see page 53) Post-install password security (see page 54) Default connection URLs (see page 55)

Enterprise Manager requirements



The system requirements for the Enterprise Manager and APM database depend on several factors, including where you deploy Enterprise Manager services and data stores, the frontends you have deployed, the total number of metrics you are collecting, and the volume of transactions you can expect on the application servers you are monitoring.

When choosing where to install an Enterprise Manager and the APM database, use this section to identify computers that meet the minimum system requirements. For more detailed information about deploying components, see the CA Wily APM Sizing and Performance Guide. The CA Wily APM Sizing and Performance Guide provides examples of different configuration and workload scenarios with recommendations to assist you in optimizing performance for your environment.


Enterprise Manager JVM requirements (see page 26) Enterprise Manager operating system requirements (see page 27) Enterprise Manager memory requirements (see page 27) Enterprise Manager disk space requirements (see page 27) SmartStor database requirements (see page 28) Transaction Events database requirements (see page 28) baselines database requirements (see page 28) Enterprise Manager temporary directory space requirements (see page 28) Enterprise Manager Services requirements (see page 28) Enterprise Manager Internet Protocol requirements (see page 29)

Enterprise Manager JVM requirements

■ Windows, Solaris, and Linux (x86, x64): 1.6.0_11

■ HP-UX: Hewlett-Packard JRE 1.6.0.02 64 bit HP-UX PA-RISC

■ AIX: IBM J2RE 1.6.0 AIX build pap3260sr2-20080818_01 (SR2)

For most platforms, 1.6 JVM is bundled with and installed by the installer. If you choose to force the installer to run using an alternate JVM, you must boot the installer with a JVM version 1.5.

Also see Specifying an alternate JVM for the Enterprise Manager or WebView (see page 50).



Enterprise Manager operating system requirements

■ IBM AIX 5.2, 5.3, 6.x

■ HP-UX 11.x, 11.23

■ Red Hat Linux 4.0, 4.4, 5.0, 5.1, 5.2

■ Red Hat z/Linux 5.0

■ Linux 2.6

■ Sun Solaris 8, 9, 10

■ Novell SuSE Linux 10, 11

■ Microsoft Windows Server 2003, 2008

■ z/OS 1.8, 1.9, 1.10

■ IBM OS/400

Note: Installing in GUI mode on OS/400 is not supported, even from a Windows system that has a drive mapped to the OS/400 system.

Enterprise Manager memory requirements

■ 2 GB

Requirements might be higher, depending on:

■ number of connected agents

■ number of connected Workstations

■ metric volume

■ monitoring logic, such as Metric Groupings, Alerts, and Calculators

Enterprise Manager disk space requirements

■ 80 MB, including VM for the Enterprise Manager

■ 30 MB for command line ProbeBuilder



SmartStor database requirements

■ 10 GB minimum disk space

Assumes default aging configuration. See the discussion about configuring SmartStor Data Storage in the CA Wily APM Sizing and Performance Guide and the spreadsheet SmartStorSizing.xls for information on determining SmartStor storage space requirements.

IMPORTANT! You must configure a dedicated disk for SmartStor if Enterprise Managers are collecting agent data. If an Enterprise Manager is running Enterprise Manager Services and not collecting agent data, SmartStor does not have to be on a separate disk or partition.

Transaction Events database requirements

■ 2 GB minimum disk space

Assumes default aging configuration. Requirements vary, depending on number of transaction events captured and how long data is stored.

baselines database requirements

■ 4 GB disk space

Assumes 200K metrics

Note: Metric baselines are stored in <EM_Home>\data\baselines.db.

Enterprise Manager temporary directory space requirements

■ 200 MB disk space

Requirements vary by platform and installer type.

Enterprise Manager Services requirements

■ 32-bit systems: 2 Enterprise Managers

■ 64-bit systems: 1 Enterprise Manager

If you are running an Enterprise Manager on a 32-bit operating system, you cannot assign all Enterprise Manager Services to a single Enterprise Manager on that machine. Instead, you must install a second Enterprise Manager, either on the same machine or on a different machine.

APM database requirements


Configure both Enterprise Managers as a cluster and assign the Stats Aggregation Service to one Enterprise Manager (as the MOM) and assign the TIM Collection Service and remaining Enterprise Manager Services to the other Enterprise Manager (as the Collector).

You should assign the DB Cleanup Service to the Enterprise Manager that has the Stats Aggregation Service.

For more information about Enterprise Manager Services, see the Wily CEM Configuration and Administration Guide.

Enterprise Manager Internet Protocol requirements

■ IPv4 or IPv6

For details on configuring Introscope for use on IPv4 or IPv6 networks, see the Introscope Configuration and Administration Guide.

For details on configuring Wily CEM for use on IPv6 networks, see the Wily CEM Configuration and Administration Guide.

Note: For Enterprise Manager clustering, you can assign up to 10 Collectors per MOM (Manager of Managers).


The APM database can be installed on the same computer as the Enterprise Manager or installed remotely on a computer the Enterprise Manager can access over the network.

The system requirements for the Enterprise Manager and APM database depend on several factors, including where you deploy Enterprise Manager services and data stores, the frontends you have deployed, the total number of metrics you are collecting, and the volume of transactions you can expect on the application servers you are monitoring.

The CA Wily APM Sizing and Performance Guide provides examples of different configuration and workload scenarios with recommendations to assist you in optimizing performance for your environment.



Disk and memory requirements

■ 10 GB disk space

■ 4 GB RAM

If you are monitoring Introscope agents only (no TIMs), you may need less disk space that these requirements suggest. For more information, see the CA Wily APM Sizing and Performance Guide.

IMPORTANT! If you are running CA Wily APM, it is recommended that you put the APM database on its own disk or partition. For more information, see the CA Wily APM Sizing and Performance Guide.

Supported databases and operating systems

PostgreSQL 8.4 on the following operating systems:

■ Red Hat Enterprise Linux 4 and above,

■ Sun Solaris 10 (32-bit and 64-bit, SPARC and x86),

■ Windows 2003 or Windows 2008.

For more information about using PostgreSQL, see Using PostgreSQL for the APM database (see page 30).

Oracle 10g or Oracle 11g, Enterprise Edition with partitioning enabled, on Windows, Linux, Solaris, HP-UX, or AIX. Note that, on all platforms, you should keep the Oracle environment up-to-date with the latest patches. You can view and download patches for the Oracle database from the Oracle web site (https://updates.oracle.com). For more information about using Oracle, see Using Oracle for the APM database (see page 31).

Note: You can use the Enterprise Manager installer to create a new PostgreSQL instance on a computer. You cannot use the installer to create a new Oracle database instance. For more information about using PostgreSQL, see Using PostgreSQL for the APM database (see page 30). For more information about the recommended minimum configuration requirements for an Oracle environment, see Using Oracle for the APM database (see page 31).

Using PostgreSQL for the APM database

Support for 32-bit and 64-bit operating environments

If you install PostgreSQL on Windows, the Enterprise Manager installer installs a 32-bit PostgreSQL database, regardless of whether you are running a 32-bit or 64-bit Windows operating system. On Linux and Solaris, you can install 32-bit PostgreSQL on 32-bit systems, and 64-bit PostgreSQL on 64-bit systems, allowing you to make full use of 64-bit capabilities.

https://updates.oracle.com/



Minimum hardware requirements and recommendations for running PostgreSQL

If you are using PostgreSQL, you should follow the guidelines published on the PostgreSQL web site (http://www.postgresql.org/) to determine the minimum hardware configuration for your environment. With the recommended configuration, you should see Input/Output throughput similar to the following:

■ Block writes should be greater than or equal to 140K writes seconds.

■ Block rewrites should be greater than or equal to 70K writes per second.

■ Sequential reads should be greater than or equal to 200K per second.

Disabling enhanced security and configuring shared memory on Linux

To use PostgreSQL on Red Hat Linux, you must turn off the SELinux service. For details, see http://wiki.postgresql.org/wiki/PostgreSQL_and_SELinux.

You should also set the Kernel Shared Memory to 100 MB or more if you are using Linux and the PostgreSQL database. For information about disabling SELinux or configuring kernel parameters, see your Linux documentation.

Using Oracle for the APM database

The following additional system requirements and recommendations apply when you are using Oracle for the APM database schema. For more information about configuring the Oracle environment, see the Oracle documentation for the version of the Oracle database you have installed.

For the CA Wily APM database on Oracle, use the following guidelines:

Operating system

32-bit or 64-bit.

Memory

The recommended setting is 2.5 GB or more. On Windows 32-bit operating systems, this setting requires changes to the boot.ini file to allow processes to use a maximum of 3 GB.

Oracle PROCESSES initialization parameter

This parameter specifies the maximum number of operating system user processes that can simultaneously connect to Oracle. The recommended setting for this parameter is 200 or more.

Oracle automatic memory management

You should enable the option for automatic memory management for the Oracle database.

http://www.postgresql.org/

http://wiki.postgresql.org/wiki/PostgreSQL_and_SELinux

http://wiki.postgresql.org/wiki/PostgreSQL_and_SELinux



Oracle automatic system maintenance

You should schedule the Oracle system maintenance task Optimizer Statistics Gathering to run once a day between 8:00 PM and 12 AM in the APM database Enterprise Manager time zone.

Redo log file size

You should increase the size of the log files to 2048 MB to hold at least 20 minutes of redo information when using Oracle for the APM database.

For information about the user roles and privileges required for the APM database owner, see About the APM database schema owner for Oracle (see page 33).

Installing and configuring an Oracle instance

If you want to install the APM database as an Oracle database schema, you must first install and configure an Oracle database instance. The APM database schema does not require the Oracle database to have any specific configuration options except that its character set should be Unicode Transformation Format (UTF-8) compliant. The default character set is selected based on the locale of the operating system when the database is installed and supports only a single language. However, Oracle recommends using AL32UTF8 as the database character set even if your database only stores data in one language.

Note: Although the AL32UTF8 character set is recommended, you can install the APM database schema on Oracle if you selected a different character set. If you do not use the AL32UTF8 character set, the database will not support more than one language or multi-byte characters.

After you have created or identified the Oracle database instance you want to use, you should verify that the database server and database instance are running and available locally or over the network. The installer must be able to connect to the database to successfully install the APM database schema.

Creating or identifying an Oracle database user

In Oracle, a database schema is always associated with a specific database user. Although there are several role-based user accounts that are created automatically when you install an Oracle database, these built-in accounts are typically preconfigured with permissions to perform specific tasks. Therefore, it is generally a best practice to create a new Oracle database user account that is specifically for the APM database.

If you want to use an existing database user account for the APM database schema, you should verify that the user namespace does not have any tables, views, sequences, or other database objects defined. After you create or identify an empty Oracle namespace to use, you can use that user's credentials to connect to the Oracle database and install the APM database schema. After installing, the user you specify will be the owner of the APM database schema. For information about the roles and privileges required for this user, see About the APM database schema owner for Oracle (see page 33).



About the APM database schema owner for Oracle

The APM database schema for Oracle requires an empty Oracle user namespace to exist on the Oracle database to which you plan to connect. The Oracle database instance is identified by its system identifier (SID). Therefore, you must create or identify a user account with access to that Oracle database instance. This user account then becomes the owner of the APM database schema. As the database owner, the user account must be granted the following roles:

■ Connect

■ Resource

The user account must also be granted the following system privileges:

■ Analyze Any

■ Create Any View

■ Unlimited Tablespace

Other than these roles and privileges assigned to the user's account, the user's namespace should not have any tables, views, procedures, or other objects defined. For information about how to create database users, assign roles, and grant specific privileges, see the Oracle documentation for the version of the Oracle database you are using. For example, if the database is Oracle 11g, Enterprise Edition, you can open the Enterprise Manager Database Console, select the Server page, then click Users to add and configure a database user for the APM database schema.

Allowing segment creation in Oracle

By default, Oracle 11g Enterprise Edition, Release 2 (11.2.0.1.0) does not allocate space for non-partition tables when tables are created. Instead, the default Oracle configuration allocates space for the table when the first record is inserted. This default behavior prevents the APM database schema from being created on Oracle 11g Enterprise Edition, Release 2. To create the APM database schema, you must modify an Oracle database property to allow the immediate creation of database segments.

To allow space to be allocated to a table when the Create Table statement is executed on Oracle 11g R2, run the following SQL statement after you have created the user account for the APM database owner:

ALTER SYSTEM SET deferred_segment_creation=FALSE scope=both

After you have created the APM database schema, you can reset the APM database to defer allocating segments when tables are created by running the following SQL statement:

ALTER SYSTEM SET deferred_segment_creation=TRUE scope=both

For more information about deferred segment creation, see http://download.oracle.com/docs/cd/E14072_01/server.112/e10820/initparams069.htm.

http://download.oracle.com/docs/cd/E14072_01/server.112/e10820/initparams069.htm



Workstation requirements


Selecting a user account to run the installer

When you run the Enterprise Manager installer, you have the option to create a new Oracle or PostgreSQL database instance with the APM database schema or update an existing Oracle or PostgreSQL database.

When creating a new PostgreSQL database instance on Linux or Solaris, use one of the following kinds of user accounts to install the PostgreSQL database:

■ root

■ a non-root account named postgres

Note: If you choose to use a non-root account to install PostgreSQL on Linux or Solaris, you must name that user account postgres. Otherwise, some database operations may not work correctly.

In addition, if you plan to install the Enterprise Manager on the same computer as the APM database, you should install the APM database first using the Database Only option, then separately install the Enterprise Manager using a regular user account.

For more information about deploying the Enterprise Manager and APM database, see the CA Wily APM Sizing and Performance Guide.

If you are creating or upgrading the APM database schema in an Oracle database, you can use any user account with permission to read and write to the target directory to run the installer. Running the Enterprise Manager installer does not require root or other privileged-user permissions.

Note: If you use a non-root user account to install PostgreSQL on Linux or Solaris, there are some minor, post-installation configurations to do. For details, see Configuring PostgreSQL on Linux or Solaris (see page 216).


When choosing where to install a Workstation, be sure the machine meets the requirements listed in this section.


Workstation JVM requirements (see page 35) Workstation operating system requirement (see page 35) Workstation disk space and memory requirements (see page 35) Workstation Java Web Start requirements (see page 35)



Workstation JVM requirements

■ JVM: v1.6 or later

Java Web Start requires JVM version 1.6 or higher on the same machine as the browser. See Designating the Java version for Java Web Start (see page 80) for more information.

Workstation operating system requirement

■ Microsoft Windows 2003 Server, XP SP2, Vista, Windows 7

■ Red Hat and Novell SuSE Linux (32 & 64 bit)

Windows platform is recommended because of better performance. Some UNIX platforms require OS patches for Java 1.6 to run properly. For more information, see Other requirements (see page 40).

Workstation disk space and memory requirements

■ 80 MB disk space, including VM

■ 128 MB memory

Workstation memory requirements may be higher, depending on:

■ the number of connected agents

■ the number of connected Workstations

■ amount of metrics generated

Workstation Java Web Start requirements

Required for Web Start installation of the Workstation. Not required for regular Workstation install.

WebView requirements


WebView requirements

When choosing where to install WebView, be sure the machine meets the requirements listed below.

■ JVM requirements: same as for the Enterprise Manager

■ Operating system: Microsoft Windows 2003 Server, Windows XP, Windows 7

■ Disk space: 80 MB

■ Memory: 128 MB

■ Client browser: Internet Explorer 6.x, 7.x, 8.x

■ Silverlight: Silverlight version 2 or 3

Wily CEM console requirements ■ Client browser: Internet Explorer 6.x, 7.x, 8.x

Although web browsers other than Internet Explorer may work, Wily CEM graph displays are not guaranteed to render properly.

Browser text size should be set to medium (IE View > Text Size > Medium). Settings other than this can produce less than optimal results.

■ screen resolution of 1280 X 1024

Screen resolution must be set to 1280 x 1024. Settings other than this can produce unexpected results with lists and reports.

About Wily CEM TIM requirements and recommendations

The following requirements and recommendations apply to customers who supply their own hardware for a TIM machine. If you are supplying your own hardware, the machine must meet or exceed the requirements below.

When installing a new TIM, the kickstart DVD installs Red Hat Enterprise Linux 4 (32-bit).

For more details regarding TIM configuration requirements and recommendations, refer to the CA Wily Compatibility Guide, which is available from your CA Wily representative or CA Support.

Note: If you plan on using evidence collection in Wily CEM and have installed Enterprise Managers on Windows, be sure that Python or Perl is installed on the machines. For details, see the Wily CEM Configuration and Administration Guide.

About Wily CEM TIM requirements and recommendations


TIM minimum requirements

Your TIM machine must meet or exceed the following minimum requirements:

■ Dual or quad core 2.93 GHz processor

■ DVD-ROM

■ 4 GB RAM memory

■ 146 GB or larger hard disk

■ network adapters: 2 onboard copper 10/100/1000 network adapters (if you upgrade your network to fiber, see below for network adapter recommendations)

TIM recommendations

If you are supplying your own hardware, CA Technologies recommends the TIM machine have the following resources:

■ RAID 1 Mirroring, for redundancy

■ 16 GB RAM

■ Two available PCI-e 8x slots, for fiber network adapters or hardware security modules

■ Redundant power supplies with failover, for redundancy

■ (optional) 2 Intel Pro 1000 MF (1 GB) onboard network adapters for fiber networks

About security requirements

CA Embedded Entitlements Manager (CA EEM) allows applications to share common access policy management, authentication, and authorization services. If you use CA EEM to implement security in CA Wily APM, use CA EEM version 8.4.

Note: CA Wily APM does not support CA EEM version 8.4 in FIPS mode.

For information about Application Performance Management security and permissions, see the CA Wily APM Security Guide.

PowerPack and extension requirements


Creating the TIM DVD

If you are installing a new TIM, you need to create a bootable (kickstart) DVD from one of the download archive files. You then use this DVD to install the Red Hat Enterprise Linux software for the TIM. For details, see Installing and configuring a TIM (see page 129).

You can use any widely available third-party utility for creating bootable DVDs from ISO images. Instructions with the utility should be sufficient to allow you to create the DVD and copy the software image to it.

To use the download archive to install the TIM operating system software:

1. Locate the download archive APMRHEL<version>_BIN.iso.

2. Copy the file to a machine that has DVD creation software installed on it.

3. Create a bootable DVD with only that software image file on it.

4. Use the DVD to install the TIM.


The following table lists the operating systems supported for the individual PowerPacks and extensions. For version-specific information or other resources required by a specific PowerPack, please consult the individual PowerPack user guide. For details, see Installing Introscope PowerPacks and extensions (see page 121).

PowerPack or Extension name Supported Platforms

PowerPack for WebSphere Portal Windows, Solaris, HP-UX, AIX, Linux (Red Hat and SUSE)

PowerPack for WebLogic Portal Windows, Solaris, HP-UX, AIX, Linux (Red Hat and SUSE)

PowerPack for SharePoint Portal and SP Monitor for SharePoint Portal

Windows

SOA Extension for webMethods Integration Server

Windows, Solaris, HP-UX, AIX, Linux (Red Hat and SUSE)

SOA Extension for TIBCO BusinessWorks Windows, Solaris, HP-UX, AIX, Linux (Red Hat)

SOA Extension for Oracle Service Bus Windows, Solaris, HP-UX, AIX, Linux

SOA Extension for WebSphere Process Server / WebSphere Enterprise Bus

Windows, Solaris, HP-UX, AIX, Linux (Red Hat), z/OS



PowerPack or Extension name Supported Platforms

SOA Extension for TIBCO Enterprise Message Service

Windows, Solaris, HP-UX, AIX, Linux (Red Hat)

SOA Extension for webMethods Broker Windows, Solaris, HP-UX, AIX, Linux (Red Hat)

PowerPack for WebSphere MQ Connectors and Messaging System

Windows, Solaris, HP-UX, AIX, Linux (Red Hat), z/OS (remote monitor)

PowerPack for WebServers (and IIS) Windows, Solaris, Linux (Red Hat)

PowerPack for WebLogic Server Windows, Solaris, HP-UX, AIX, Linux (Red Hat)

PowerPack for SiteMinder Windows, Solaris, HP-UX, AIX, Linux (Red Hat)

SNMP Collector for SiteMinder Windows, Solaris, HP-UX, AIX, Linux (Red Hat)

PowerPack for Oracle DB Windows, Solaris, HP-UX, AIX, Linux (Red Hat)

PowerPack for WebSphere - Distributed Windows, Solaris, HP-UX, AIX, Linux (Red Hat)

LeakHunter Windows, Solaris, HP-UX, AIX, Linux (Red Hat and SUSE), OS/400, z/OS

ErrorDetector Windows, Solaris, HP-UX, AIX, Linux (Red Hat and SUSE), OS/400, z/OS

ChangeDetector Windows, Solaris, HP-UX, AIX, Linux (Red Hat and SUSE), OS/400, z/OS

SNMP Adapter Windows, Solaris, HP-UX, AIX, Linux (Red Hat and SUSE), OS/400, z/OS

SYSVIEW Windows, Solaris, HP-UX, AIX, Linux, OS/400, z/OS

Other requirements


Other requirements

In addition to the requirements already mentioned, there are a few additional requirements for Introscope.


JAR installer requirements (see page 40) ProbeBuilder requirements (see page 40) Platform support for Java 1.6 (see page 40) SNMP requirements (see page 41)

JAR installer requirements

Before you run a .JAR installer, verify that there is enough disk space in the target installation directory. If the target installation directory does not have enough disk space, the installer will not run successfully.

The minimum sufficient disk space is usually 2 to 3 times the size of the .JAR installer. For example, if the .JAR is 50 MB, the initial application footprint will be 100 to 150 MB, so you should choose an install directory with a minimum of 150 MB.

ProbeBuilder requirements

■ JVM: v1.6.x

■ command-line ProbeBuilder: 30 MB disk space

Platform support for Java 1.6

Some UNIX platforms require patches to run Java 1.6. Running Introscope in an unpatched environment under heavy load can result in unpredictable errors.

To ensure patches necessary to run Java 1.6 are installed, check the patch download center for your platform:

Platform Patch Download Center

AIX http://www.ibm.com/developerworks/java/jdk/aix/service.html

Solaris http://sunsolve.sun.com/show.do?target=patches/patch-access

HP UX http://www.hp.com/products1/unix/operating/index.html

http://www.ibm.com/developerworks/java/jdk/aix/service.html

http://sunsolve.sun.com/show.do?target=patches/patch-access

http://www.hp.com/products1/unix/operating/index.html

http://www.hp.com/products1/unix/operating/index.html

About upgrade requirements


SNMP requirements

These are the system and version requirements for the SNMP Adapter, an Introscope extension which is installed automatically along with the Enterprise Manager.

■ System requirements: Same as for Introscope agent.

■ SNMP Framework requirements: SNMP Manager must be SNMP V1.0 or V2.0 compliant. Only MIB v2 is supported

■ Other requirements:

■ BMC Patrol version 3.4 and higher

■ MIB to KM Wizard version 2.1 and higher

■ Mercury LoadRunner version 7.8, 8.0, and 8.1

■ Mercury Load Runner’s SNMP Monitor (same version as LoadRunner used)

SNMP Adapter required permissions

Many functions require resource-specific permissions. SNMP Adapter features require these permissions:

■ To create an SNMP Collection, a user must have write permission to a domain.

■ To publish a MIB, a user must have publish_mib permission for the server.

For information about Application Performance Management security and permissions, see the CA Wily APM Security Guide.


To upgrade to the current release, your existing installations of Introscope and Wily CEM must meet the requirements listed below.


Introscope upgrade requirements (see page 42) Wily CEM upgrade requirements (see page 42) Upgrade paths (see page 43)



Introscope upgrade requirements

Your installation must meet these requirements to upgrade to Introscope 9.0:

■ An Enterprise Manager is installed.

The installer can upgrade WebView, ProbeBuilder, and the EPAgent during an Enterprise Manager upgrade, if:

■ an Enterprise Manager is present

■ the WebView, ProbeBuilder and/or EPAgent was installed during the same installation as the Enterprise Manager

Note: For details on how to upgrade components that were not installed during the same installation as the Enterprise Manager, see Introscope automatic and manual upgrade information.

■ The Enterprise Manager is one of these versions:

■ 8.0.x.y

■ 8.1.x.y

■ 8.2.x.y

■ 9.0.x.y (any patch or Service Pack level lower than the patch or Service Pack level of your installer)

You should also read Preparing for install or upgrade (see page 13).

Wily CEM upgrade requirements

Your Wily CEM installation must be version 4.5 to 4.5.4 to upgrade to CA Wily APM 9.0.

If your installation’s version is prior to version 4.5, you must first upgrade to version 4.5 before proceeding. For example, if you need to upgrade from 4.0.x, first upgrade to 4.2.x and then to 4.5.x, using the documentation provided in those releases.

IMPORTANT! If your Wily CEM version is 4.5.5 or later, you must upgrade instead to the first service pack release after CA Wily APM 9.0.

About the installation files


Upgrade paths

This document contains some general machine and configuration recommendations for upgrade, depending on factors such as clustering, existing machine resources, and which products you are upgrading from and to.

Introscope 9.x provides many new out-of-the box features that both improve visibility into monitored applications and make it easier to quickly isolate production issues. Depending on the number of web applications that you monitor using Introscope, your Introscope configuration, and the available capacity in your MOM-Collector cluster, you may need additional Collectors to accommodate the additional 9.x performance load

The new frontend and business transaction monitoring features in Introscope 9.x also increase metric subscriptions on the MOM.

For further details, see the CA Wily APM Sizing and Performance Guide.


This section includes information about the installers and other files needed to install Introscope or Wily CEM components. When getting ready for your CA Wily APM installation or upgrade, you download the correct installers for Introscope and Wily CEM. For information about which files to download, see the CA Wily APM Release Notes.

Introscope installers

Due to Introscope’s multi-tier architecture, there are separate Introscope installers for each component to install. Introscope components run on a variety of platforms, and your deployment plan affects which components you install on which machines.

Use the Introscope installers to perform a fresh installation or to upgrade an existing installation.

During upgrade, you backup and restore customizations and other artifacts from your existing installation. For details, see Upgrading Introscope (see page 223).

Introscope installers supply default values for key configuration settings, such as the ports that components use to communicate, location and aging rules for data stores, and JVM options. You can accept default settings, or supply your own, as appropriate.

Most of the configuration settings you specify during the installation are persisted properties files, or other configuration artifacts that you can edit manually after the installation, as appropriate. Most configuration files reside in the <EM_Home>\config directory.



Several Introscope installers are available:

■ Introscope Main installer—Installs the Enterprise Manager, WebView, Environment Performance agent, ProbeBuilder, and databases (SmartStor, Transaction Event, baseline, and the APM database). Also provides files needed for PowerPacks; you must enable and configure these in order to use the PowerPacks. You can install all components, or select only desired components to install. See Selecting the correct main installer for your operating system (see page 45). For details on enabling and configuring a PowerPack, see the documentation for that PowerPack.

■ Introscope Workstation-only installer—A smaller installer, appropriate when you are installing only the Workstation on the target system. Also installs some files for ChangeDetector. For details, see Selecting the correct Workstation-only installer (see page 46).

■ Introscope Standalone PowerPack installer— This installer performs some initial Enterprise Manager configuration for specified PowerPacks and installs the PowerPack files. To fully enable a PowerPack, you must also consult the PowerPack’s user guide for instructions on post-install configuration. For details, see Selecting the correct PowerPack installer (see page 47).

■ Introscope Workstation Java Web Start—Enables on-line installation and automatic updates of the Workstation, ensuring that end-users have the version of the Workstation that matches the Enterprise Manager. See Installing the Workstation using Java Web Start.

■ Introscope SAP installer—This installer is for SAP NetWeaver users to whom Introscope components are distributed by SAP. See Selecting the correct SAP installers (see page 47).

The SAP installation is bundled with certain customized files, ports, and SAP-specific components.

For information about the agent installers, see the Introscope Java Agent Guide and Introscope .NET Agent Guide.

If you plan to configure settings other than the default port assignments or bundled JVM, determine the values you prefer before starting the installation. You can record these values on the Using the installation worksheet.



Selecting the correct main installer for your operating system

This section identifies the name of the installer and the archive that contains it for different operating systems (OS).

IMPORTANT! Some distributions of the main installer include the Introscope agent. These archives have filenames ending with install.zip or install.tar. However, the installer does not install the agent. For information and instructions on installing the agent, see the guide appropriate to your system—the Introscope Java Agent Guide or the Introscope .NET Agent Guide.

Note: If you are installing a PostgreSQL database instance for the APM database, the operating system user account that you use to install must have permission to create users. On Windows, the installer can install PostgreSQL only from a direct login or console session. You cannot install PostgreSQL by way of terminal services.

The following table lists the installer file and installer archive files available for each operating system:

OS Installer file Installer archive

Red Hat Linux introscope<version>linux.bin

introscope<version>linuxinstall.tar (with agent)

or

introscope<version>linux.tar

Windows introscope<version>windows.exe

introscope<version>windowsinstall.zip (with agent),

or

introscope<version>windows.zip

HP-UX introscope<version>hpuxParisc.bin

introscope<version>hpuxPariscinstall.tar (with agent)

or

introscope<version>hpuxParisc.tar

Solaris introscope<version>solaris.bin

introscope<version>solarisinstall.tar (with agent)

or

introscope<version>solaris.tar

AIX introscope<version>aix.bin

introscope<version>aixinstall.tar (with agent)

or

introscope<version>aix.tar




Other UNIX introscope<version>otherUnix.jar

introscope<version>otherinstall.tar (with agent)

or

introscope<version>other.tar

This installer is for use on other UNIX platforms on which the bundled JVM Linux installer is not supported, such as Linux/PPC, and SUSE. For details, see the CA Wily APM Compatibility Guide (available from CA Support).

OS/400 introscope<version>os400.jar

introscope<version>os400install.zip (with agent)

or

introscope<version>os400.zip

z/OS introscope<version>zOS.jar

introscope<version>zOSinstall.tar (with agent)

or

introscope<version>zOS.tar

Note: When installing Enterprise Manager or WebView, if the target system is running an antivirus service that continuously scans the file system, pause this service before the installation and resume it once the installation is complete. If this step is not taken, the file scanning service may lock new or temporary files as soon as the installer creates them, and installation errors may occur as a result.

Selecting the correct Workstation-only installer

The table below lists the Workstation-only installer files and installer archive files for each operating system:

Platform Installer file Installer archive

Windows IntroscopeWorkstation<version>windows.exe IntroscopeWorkstation<version>windows.zip

Linux IntroscopeWorkstation<version>linux. bin

IntroscopeWorkstation<version>linux.tar



Selecting the correct PowerPack installer

The table below lists the standalone PowerPack installer files and installer archive files for each operating system:

Platform Installer filename

Windows IntroscopeStandalonePowerPackInstaller<version>windows.zip

UNIX IntroscopeStandalonePowerPackInstaller<version>unix.tar

Selecting the correct SAP installers

The table below lists the SAP main installer files and installer archive files for each operating system:


Windows introscope<version>windowsAMD64SAP.exe

introscope<version>windowsIA64SAP.exe

introscope<version>windowsSAP.exe

Solaris introscope<version>solarisSparcSAP.bin

HP-UX introscope<version>hpuxPariscSAP.bin

introscope<version>hpuxIA64SAP.bin

AIX introscope<version>aix64SAP.bin

introscope<version>aixSAP.bin

Linux introscope<version>linuxAMD64SAP.bin

introscope<version>linuxIA64SAP.bin

introscope<version>linuxSAP.bin

OS/400 introscope<version>os400SAP.jar

runinstaller.os400.sh

Other UNIX introscope<version>otherUnixSAP.jar

Use this installer to install Introscope on other UNIX platforms that are otherwise not listed here or in the CA Wily APM Compatibility Guide (available from CA Support).



SAP main installers install Enterprise Manager components, and the following extensions are handled differently from the main installer:

■ ChangeDetector, ErrorDetector, LeakHunter, SNMP Adapter, and SYSVIEW extensions are installed but not enabled.

■ SOA Performance Management is enabled by default.

■ The following SOA extensions are installed but not enabled:

■ SOA Extension for webMethods Integration Server

■ SOA Extension for TIBCO BusinessWorks

■ SOA Extension for Oracle Service Bus

■ SOA Extension for WebSphere Process Server/WebSphere Enterprise Service Bus

■ Other PowerPacks are not installed.

■ Console mode installation is not supported for SAP end users. If you are installing Introscope on an SAP end user’s machine, use silent install mode.

■ The SAP main installer comes bundled with additional JVMs. For details, see About Introscope bundled JVMs (see page 48).

The table below lists the SAP workstation installers for each operating system:


Windows IntroscopeWorkstation<version>windowsAMD64SAP.exe

IntroscopeWorkstation<version>windowsSAP.exe

Linux IntroscopeWorkstation<version>linuxAMD64SAP.bin

IntroscopeWorkstation<version>linuxSAP.bin

About Introscope bundled JVMs

A version of the Java Virtual Machine is bundled with the Introscope installers on Sun Solaris, Windows, AIX, HP-UX, and Red Hat Linux. By default, an Introscope component runs on the JVM with which it is bundled. You can specify that an Introscope component use a different JVM during the installation process. The JVM bundled with Introscope depends on the operating system where you install the component.

Solaris bundled JVM

The JVM bundled with the Solaris installer is: Sun JRE 1.6.0_11 64bit Solaris SPARC



Windows bundled JVMs

The JVMs bundled with the Windows installers are as follows:

■ x86 processors: Sun 1.6.0_11

■ Itanium 64-bit (SAP installers only): Sun JRE 1.6.0_11 for Windows Itanium 64 bit

■ AMD processors (SAP installers only): Sun JRE 1.6.0_11 Win AMD64

AIX bundled JVMs

The JVMs bundled with the AIX installers are as follows:

■ AIX 32: IBM J2RE 1.6.0 AIX build pap3260sr2-20080818_01(SR2)

■ AIX 64 (SAP installers only): IBM J2RE 1.6.0 AIX build pap6460sr2-20080818_01 (SR2)

HP-UX bundled JVMs

The JVMs bundled with the HP-UX installers are as follows:

■ PA-RISC 32+64 : HP JRE 1.6.0.02 64bit HP-UX PA-RISC

■ Itanium (SAP installers only): HP JRE 1.6.0.04 64bit HP-UX Itanium

Linux bundled JVMs

The JVMs bundled with the Linux installers are as follows:

■ x86, (Red Hat 2, 3, 4; SUSE 8, 9): Sun JRE 1.6.0_11 Linux Intel

■ Itanium (SAP installers only): Sun JRE 1.6.0_11 for Linux Itanium 64 bit

■ AMD64 (SAP installers only): Sun JRE 1.6.0_11 for Linux AMD64

Other installer bundled JVM information

The Other UNIX, z/OS and OS/400 installers do not include bundled JVMs.

■ Other UNIX: The Other UNIX installer is for use on Linux/PPC, SUSE 10, and other platforms on which the bundled JVM Linux installer is not supported.

Use the Other UNIX installer to install Introscope on other UNIX platforms that are otherwise not listed in this guide or in the CA Wily APM Compatibility Guide (available from CA Support).

■ z/OS: The installed text files are in EBCDIC format. See Running an installer with an alternate JVM (see page 50).

■ OS/400: See Running an installer with an alternate JVM (see page 50).



Running an installer with an alternate JVM

For most platforms, 1.6 JVM is bundled with and installed by the installer. If you choose to force the installer to run using an alternate JVM, you must boot the installer with a JVM version 1.5 or later.

Note: The OS/400 installer requires a JVM version 1.6 or later.

We recommend you boot the installer with a JVM that meets the minimum requirements for the component(s) you are installing.

To run an installer with an alternate JVM:

■ Run the following command in the installer directory:

<installerName>.[exe|bin] LAX_VM <path to alternate JVM>

Specifying an alternate JVM for the Enterprise Manager or WebView

By default, Enterprise Manager and WebView use the JVM installed in <EM_Home>/JRE. You can designate Enterprise Manager WebView to use an alternate JVM to run. If you specify an alternate JVM, it must be version 1.6 or above. In particular this applies to installations on z/OS and OS/400 (IBMi), which require you to specify an existing JVM to run the installer.

■ Before a silent install, configure these properties in the response file:

■ emLaxNlCurrentVm property (for Enterprise Manager)— see Enterprise Manager Advanced JVM settings (see page 98).

■ wvLaxNlCurrentVm property (for WebView)— see WebView Advanced JVM settings (see page 110).

■ During the GUI installation, provide the installer with an alternate path to the JVM. See step 4 under the heading Specifying the install directory, external components, and licenses (see page 66).

■ After installation, by editing the .LAX files for Enterprise Manager or WebView.

Note: If you specify a 64-bit JVM, the uninstaller does not work. In this situation restore the default JVM and then uninstall.

Note: JRE and JVM are used interchangeably to refer to the same Java executable.

To designate an alternate JVM after installation:

1. Open the EnterpriseManager.lax or WebView.lax files for editing.

2. Edit the LAX.NL.CURRENT.VM property to point to a different JRE.

3. Save and close the file.

After this edit, you must restart the Enterprise Manager or WebView for the change to take effect.



External component packages

To install Introscope, you must obtain third-party external component package files:

■ eula.txt

■ osgiPackages archive:

■ osgiPackages.v2.1.windows.zip, for a Windows system

■ osgiPackages.v2.1.unix.tar, for a UNIX system

■ osgiPackages.v2.1.zos.tar, for an OS/400 or z/OS system

To download the third-party external component package files:

1. Go to http://opensrcd.ca.com/ips/osgi/.

2. Download the eula.txt file and the osgiPackages archive for your system.

Note: The installer does not validate whether you have downloaded the correct archive for your platform. Be sure you download and specify the correct archive for your platform.

3. Put the files somewhere on your network. You will provide the path to these files during the installation process.

Wily CEM installation files

After you have installed Introscope, or the Enterprise Manager portion of CA Wily APM, to complete the Wily CEM installation you install a TIM.

If installing a new TIM, you need to get the TIM software appliance DVD bundle from your CA Wily representative, which includes:

■ TIM software appliance kickstart DVD (for installing the Red Hat operating system)

■ DVDs that contain the three TIM software .IMG files:

■ APM_INSTUPD<version>.IMG

■ APMTHIRDPART<version>.IMG

■ APM_TIM<version>.IMG

If you are upgrading a TIM, you download the three .IMG files from the location provided to you by your CA Wily representative. For details, see the CA Wily APM Release Notes.

http://opensrcd.ca.com/ips/osgi/


About installation modes


CA Embedded Entitlements Manager installation files

If you are installing CA Embedded Entitlements Manager, you need to have the CA EEM installer appropriate for your operating system (OS). The table below lists the CA EEM installer files and archives for each operating system.


Red Hat Linux

EEMServer_8.4.217_linux.sh APM_EEM_<version>.tar

Windows EEMServer_8.4.217_win32.exe APM_EEM_<version>.zip

HP-UX EEMServer_8.4.217_hpux.sh APM_EEM_<version>.tar

Solaris EEMServer_8.4.217_sunos.sh APM_EEM_<version>.tar

AIX EEMServer_8.4.217_aix.sh APM_EEM_<version>.tar

About installation modes

Introscope installers can run in these modes:

■ GUI mode—a series of windows that guide you through the installation and summarize the results when complete.

■ Windows: The Introscope installer defaults to GUI mode on Windows platforms. See Launching installers in GUI mode on Windows systems (see page 59).

■ UNIX: GUI mode is supported on UNIX systems where you can launch a windowing environment. See Launching installers in GUI mode on UNIX systems (see page 60).

On operating systems that do not support GUI mode, you must force the installer to run in a different mode, either at the command line or in the script that invokes the installer.

■ Console mode—a series of text prompts that guide you through the installation and summarize the results when complete. Use Console mode to install Introscope components on machines without video cards, or Xservers. Console mode is the default mode on UNIX platforms. See Launching the installer in console mode (see page 61).

■ Silent mode—invoked from the command line, the Silent mode installer obtains input from a specified response file. The Silent mode installer eases the process of performing multiple Introscope installations. The installer runs in the background and does not provide output—you check the install log to verify the installation results. See Installing Introscope in silent mode (see page 85).

About APM time settings


The table below lists the supported installation modes for each operating system.

Platform GUI Console Silent

Windows Yes (default) No Yes

Solaris

HP-UX

Red Hat Linux

SUSE Linux

Yes Yes (default) Yes

AIX No Yes (default) Yes

OS/400 No Yes Yes

z/OS No Yes Yes

Other Yes Yes Yes

About APM time settings

Here are some important notes about time settings in CA Wily APM:

■ If installing a new TIM, the default time zone is America/New York. If upgrading an existing TIM, the time zone remains as configured. Note that the Collector Enterprise Manager running the TIM Collection Service communicates with the TIMs in GMT (Greenwich Mean Time). This makes the TIM’s time zone setting affect only the timestamp of the TIM’s log files. Enterprise Manager log files are in that EM’s time zone.

■ When you first enable a TIM from the Wily CEM console, the MOM Enterprise Manager machine synchronizes its time with that TIM machine (not affecting the TIM machine’s time zone), matching the TIM machine’s time to the MOM machine’s time. Subsequent time synchronizations to the TIM machine are initiated from the machine that hosts the Collector EM running the TIM Collection Service.

■ The machine that hosts the Collector Enterprise Manager running the TIM Collection Service synchronizes its time to all enabled TIMs when that Collector starts, and also daily at 1:05 am (Collector Enterprise Manager machine time).

Post-install password security


■ CA Wily strongly recommends that you set up your clustered systems so that machines running Enterprise Managers synchronize their system clocks with a time server such as an NTP server. If you are using a standalone Enterprise Manager or have not configured your installation to synchronize to a time server, use caution when changing the system clock on the Enterprise Manager machine. Changing the time on machine that hosts a Collector Enterprise Manager running either the TIM Collection service or Stats Aggregation Service can affect CA Wily CEM system functions including:

■ Setting the time forward might result in gaps in the aggregation statistics.

■ Setting the time backward might result in corruption and/or duplicate aggregation statistics.

■ Changing the time in the middle of an aggregation process might result in corrupted aggregation statistics.

■ The time setting that is most important in CA Wily APM is the clock on the machine that hosts the Enterprise Manager, or the MOM if there's a cluster. This is the time that all (Collectors,) agents, and TIMs should be synchronized with. When the TIM is first enabled from the Wily CEM Console, the MOM/EM machine will synchronize its time with the TIM machine. In addition, the machine that hosts the Enterprise Manager (running the TIM Collection Service) will synchronize its time with all enabled TIM machines on Enterprise Manager startup and daily at 1:05 A.M.

Post-install password security

The table below lists the user name and default passwords for each of the major CA Wily APM components and where you can find information about changing the passwords.

IMPORTANT! Be sure to change and secure all passwords from their default settings, as listed below. Your security implementation solution determines how you change user accounts for CA Wily APM, Introscope, or Wily CEM. Refer to the CA Wily APM Security Guide for additional security information.

Component Default username Default password Where to go for details on changing the password

Enterprise Manager (Workstation, WebStart, or WebView)

admin (blank)

If using CA EEM, the default password is:

admin

Introscope Workstation User Guide

TIM (operating system) root quality Red Hat Linux documentation

Default connection URLs



TIM Wily System Setup admin quality Changing the TIM System Setup Page password (see page 194)

Wily CEM console cemadmin quality CA Wily APM Security Guide

If you install a PostgreSQL database instance for the APM database, be sure to change the following database user passwords from their default settings.


PostgreSQL administrator postgres C@wilyapm90 Changing PostgreSQL database passwords (see page 215)

PostgreSQL database user admin wily Changing PostgreSQL database passwords (see page 215)

PostgreSQL operating system user account for the PostgreSQL service

postgres C@wilyapm90 Operating system documentation


Here are the default login URLs for different CA Wily APM components:

■ Java Web Start Workstation:

http://<EM_Host>:8081/workstation

■ Wily CEM Console / Enterprise Manager login:

http://<IP_Address>:8081/wily

■ Wily System Setup Page for a TIM:

http://<IP_Address>/wily/system

Chapter 4: Installation checklist 57

Chapter 4: Installation checklist

This chapter includes an overview of the tasks involved in installing a new deployment of CA Wily APM. There is also a list of passwords that need securing post-installation or post-upgrade.

Note: For overviews of the upgrade process, see Upgrading to CA Wily APM 9.x (see page 149).

To install CA Wily Application Performance Management 9.0 (an overview):

1. Plan what parts of CA Wily APM you will install and onto which machines.

For information related to architecture, sizing, and security, consult the following CA Wily APM documentation:

■ CA Wily APM Overview Guide

■ CA Wily APM Glossary

■ CA Wily APM Sizing and Performance Guide

■ CA Wily APM Security Guide

■ CA Wily APM Transaction Definition Guide

2. Familiarize yourself with CA Wily APM 9.0 and how you intend to use it once it’s installed.

Review the documentation listed in Where to go for more information (see page 17).

3. Ensure the machines meet or exceed the minimum requirements.

For more information, see Preparing for install or upgrade (see page 25).

4. Locate and select the correct installer and related files.

For more information, see About the installation files (see page 43).

5. Use the installation worksheet to note the details you’ll need to specify during the installation process.

For more information, see Using the installation worksheet (see page 245).

6. Install the Enterprise Manager, APM database, WebView workstation, and related files.

When installing the Enterprise Manager, you can either install a standalone Enterprise Manager or deploy into a clustered environment. For more information, see Installing Introscope in GUI or console mode (see page 59) or Installing Introscope in silent mode (see page 85).



7. If you plan on using extensions, install additional components and do manual configurations as needed.

For more information, see Installing Introscope PowerPacks and extensions (see page 121).

8. Install the Workstation and Java Web Start workstation.

For more information, see Installing the Workstation (see page 77).

9. Install CA Embedded Entitlements Manager (CA EEM) so that you can authenticate and authorize CA Wily APM users.

For more information, see the CA EEM documentation to install and run CA EEM, and then refer to the CA Wily APM Security Guide for instructions on implementing CA Wily APM with CA EEM security. Also see CA Embedded Entitlements Manager installation files (see page 52).

10. Verify that the Enterprise Manager and Workstation are installed correctly.

For more information, see Verifying the Enterprise Manager installation (see page 76) and Verifying the Workstation installation (see page 78).

11. Install the TIMs for use with Wily CEM.

For more information, see Installing Wily CEM (see page 129).

12. Configure the TIMs to monitor the network, if desired.

For more information, see Configuring the TIM network monitor interface (see page 138).

13. Install agents, and make sure you see agent data in the Enterprise Manager.

For more information, see the Introscope Java Agent Guide and the Introscope .NET Agent Guide.

14. After you have installed all components, you may need to modify configuration properties to suit your environment.

For more information, see the following: Introscope Configuration and Administration Guide, Wily CEM Configuration and Administration Guide, and the Wily CEM Integration Guide.


Chapter 5: Installing Introscope in GUI or console mode

This chapter contains instructions for running the full install, the standalone PowerPack installer, and the Workstation-only installer in GUI mode.

For information about the installers, and to verify that GUI mode installation is supported in your environment, see Preparing for install or upgrade (see page 25).

Note: If you are upgrading an existing Introscope installation, see Upgrading to CA Wily APM 9.x (see page 149).


Launching installers in GUI mode on Windows systems (see page 59) Launching installers in GUI mode on UNIX systems (see page 60) Launching the installer in console mode (see page 61) Installing Introscope main components (see page 65) Installing the Workstation (see page 77) Uninstalling Introscope (see page 81)

Launching installers in GUI mode on Windows systems

To launch the installer in GUI mode on Windows:

■ Start the installer using the method that corresponds to the file type for your platform, substituting the file name for Install.exe in these instructions:

■ If your installer has a .EXE file extension, you can:

■ double-click the file

or:

■ invoke the installer from the command line:

c:> .\Install.exe

Launching installers in GUI mode on UNIX systems


Launching installers in GUI mode on UNIX systems

On UNIX systems, you can run the installer in GUI mode from any shell that has a windowing environment available, both:

■ UNIX systems with a desktop environment—You launch the installer in GUI mode with a simple command.

■ UNIX systems without a desktop environment—You can still run the installer in GUI mode by starting and configuring an Xsession.

Using GUI mode on UNIX systems with a desktop environment

This applies to .BIN and .JAR installers.

To launch the installer in GUI mode on a UNIX system with a desktop environment:

1. Open a command shell.

2. If your installer has a .BIN file extension, invoke it from the command line. For example:

./install.bin -i swing

where install.bin is the installer archive appropriate for your system.

3. If your installer has a .JAR file extension, invoke it from the command line and specify the appropriate JVM (.JAR installers do not include a bundled JVM). For example:

[root:/] /usr/java/bin/java -classpath <InstallerName>.jar install -i swing

Now proceed with Installing Introscope main components (see page 65).

Using GUI mode on UNIX systems without a desktop environment

Even on a headless UNIX system with no desktop of its own, you can still run the Introscope installer in GUI mode.

To launch the installer in GUI mode on a UNIX system with no desktop environment:

1. Copy the install.bin (the installer archive appropriate for your system) to the headless system where you want to install Introscope.

2. Locate a separate system that does have an X windowing environment. For example, a Linux server, or a Windows system with Cygwin/X installed.

3. Log into the desktop of this second system.

4. Open a terminal shell.

Launching the installer in console mode


5. Type the following command to allow the headless machine to start an Xsession on your local, windowing-capable system:

xhost + <headless box hostname or IP address>

6. From the terminal shell, use SSH or telnet to connect and log in to the headless system as a properly permissioned user.

7. In the SSH or telnet session, type the following commands to set up the display:

{root@headlessbox] DISPLAY=<Xserver.box.hostname.or.IP.address>:0.0

[root@headlessbox] export DISPLAY

[root@headlessbox] echo $DISPLAY

8. In the SSH or telnet session, launch the installer in swing mode with the command:

./install.bin -i swing

The installer introduction screen opens on your local desktop.

9. Proceed normally with the installation, using the steps in Installing Introscope main components (see page 65).

10. When the installer has completed, end the SSH or telnet session.

11. Once you have disconnected your session, type this command to restore your windowing-capable system to its previous state.

xhost - <headless box hostname or IP address>


This section covers how to run Introscope installers in console mode.

For information on removing Introscope components, see Uninstalling Introscope (see page 81).

In console mode, the installer collects the same input, issues the same error messages, and presents the same installation summary information as the GUI installer, but using a terminal window.

Console mode installation is the default on UNIX platforms.

Note: Console mode installation is not supported on Windows nor for SAP end users. If you are installing Introscope on an SAP end user’s machine, use silent install mode. See Installing Introscope in silent mode (see page 85).



Note: If you are installing in console mode on UNIX, you specify the CA EULA file location instead of reviewing it in the installer. You must first review and edit the CA EULA file to indicate that you accept the terms of the agreement. Then, when running the installer in console mode, specify the file location. For details, see Editing the eula.txt and ca-eula.txt files (see page 87).

Refer to Installing Introscope main components (see page 65) to review information that the installer requests during the process.

During Console mode installation process, you can:

■ Type Back to return to the previous window.

■ Type Quit at any time to quit the installer.

Launching .BIN installers in console mode

.BIN installers are available for Solaris, HP-UX, AIX, and Red Hat Linux platforms. For details, see Introscope installers (see page 43).

To launch a .BIN installer in console mode:

■ For .BIN files, at the command line, type:

<path to installer> -i console

For example:

[root@server:/sw/downloads] ./introscope9.0.x.ysolaris.bin -i console

Note: Installing SAPExpertCenter Enterprise manager on HP-UX in console mode requires the -i console flag.

Note: If you are installing in console mode on Linux, the "-i console" is not necessary.



Launching .JAR installers in console mode

.JAR installers are available for other UNIX platforms. For OS/400 and z/OS, refer to sections below for details unique to those operating systems. For details on installer files, see Introscope installers (see page 43).

To launch a .JAR installer (without a bundled JVM) in console mode:

■ Enter the following at the command line, specifying your JVM:

[root:/] /usr/java/bin/java -classpath introscope<version>os400.jar install –i

console

You must use a flag to force console mode, because Swing mode is the default for .JAR files.

For disk space requirements related to running .JAR installers, see JAR installer requirements (see page 40).

Launching the console mode installer on OS/400 / IBMi

When installing an Introscope component on an OS/400 or IBMi machine, follow the instructions below. Be sure to specify JAVA_HOME, either at the command line or by the JAVA_HOME environment variable.

Note: When installing on OS/400 or IBMi systems, to run the installer successfully, the JVM must be version 1.6 or later; other installers require at least version 1.5.x. Running Enterprise Manager and WebView requires a 1.6 JVM. For details on installer files, see Introscope installers (see page 43).

To launch the console mode installer on OS/400:

1. Use the IBM iSeries Access for Windows or similar utility to extract the installer .ZIP archive. The installer archive contains the following files:

■ introscope<version>os400.jar

■ runinstaller.os400.sh—This script launches the installer with the -i console option.



2. Specify the JAVA_HOME variable.

Use either the environment variable or the script’s definition. If you use the environment variable, you must comment out the script’s definition.

Verify that a JAVA_HOME environment variable exists by running:

echo $JAVA_HOME

■ If JAVA_HOME is not defined, do the following:

a. Open the runinstaller.os400.sh script in a text editor.

b. Uncomment the line that sets the JAVA_HOME variable, and modify the path to specify the location of your Java installation directory for JAVA_HOME.

c. Save your changes.

3. Launch the script from Qshell:

runinstaller.os400.sh introscope<version>os400.jar

Note: If your system temp directory has insufficient space, the installer cannot run. To resolve this problem, you can use an alternate temp directory:

java -Dlax.nl.env.tmp=/my/Temp/Dir -jar install.jar

Launching the console mode installer on z/OS

When installing an Introscope component on a z/OS machine, follow the instructions below. Be sure to specify JAVA_HOME, either at the command line or by the JAVA_HOME environment variable.

To launch the console mode installer on z/OS:

1. Run the following command to extract the contents of the z/OS installer archive:

tar tvf <installerFile>.tar

2. Extract the contents of the z/OS installer file:

■ introscope<version>zOS.jar

■ runinstaller.sh—This script launches the installer with the -i console option, and checks that there is enough space in the /tmp directory.

■ tmppath—This executable determines where to put temporary files during the installation.

3. Verify that a JAVA_HOME environment variable exists by running:

echo $JAVA_HOME

Installing Introscope main components


4. If JAVA_HOME is not defined, do the following:

a. Open the runinstaller.sh script in a text editor.

b. Uncomment the line that sets the JAVA_HOME variable, and modify the path to specify the location of your Java installation directory for JAVA_HOME.

c. Save your changes.

5. Launch the installer with the following command:

runinstaller.sh introscope<version>zOS.jar

Note: If your system temp directory has insufficient space, the installer cannot run. To resolve this problem, you can use an alternate temp directory:

java -Dlax.nl.env.tmp=/my/Temp/Dir -jar install.jar


Locate the appropriate installer for your environment—see Selecting the correct main installer for your operating system (see page 45). Then:

■ If you are installing on a UNIX platform, go to Launching installers in GUI mode on UNIX systems (see page 60).

■ If you are installing on Windows, go directly to the procedure below.

Use the main installer to install an Enterprise Manager, WebView, the Introscope databases, ProbeBuilder, and the Environment Performance agent.

For more information, see Installing Introscope PowerPacks and extensions (see page 121).

To install Introscope:

1. The installer opens with the Introduction window. Click Next to begin the installation.

The installer guides you through the installation step by step. The list of navigation steps shows where you are in the process. Use the Next and Previous buttons to navigate through the installation.

2. The installer asks you to accept the terms of the CA End User License Agreement (EULA). This EULA is for CA Technologies products. Read the agreement, and then, if you accept the terms, select I accept the terms of the License Agreement. The installation will not continue until you accept the terms of the license agreement.

Next, go to Specifying the install directory, external components, and licenses (see page 66).



Specifying the install directory, external components, and licenses

These steps continue from Installing Introscope main components (see page 65).

1. In the Choose Install Set window, choose the type of installation—Complete, Minimal, Database Only, or Custom—and click Next.

Complete Installation

Installs or upgrades the Enterprise Manager, WebView, the APM database, ProbeBuilder, and the Environment Performance Agent.

Minimal

Installs or upgrades just the Enterprise Manager and the APM database.

Database Only

Installs or upgrades the APM database. For Oracle, this option validates that the Enterprise Manager can connect to an existing Oracle database using the credentials you specify or upgrades an existing APM database schema on an Oracle database instance. For PostgreSQL, this option enables you to install a database instance without any other components.

Custom

Choose the individual components to install or upgrade.

2. If you selected Custom, the Choose Product Components screen displays. Select the product components you want to install, and click Next to continue.

Note: If you do not select the APM database, you will still be prompted to specify connection information when installing the Enterprise Manager to ensure that the Enterprise Manager can connect to an existing APM database. For details, see Specifying the APM database (see page 70).

3. In the Choose Install Folder you can click Next to accept the default installation directory, or click Browse to specify a different location.

Default directories:

■ Windows: C:\Program Files\CA Wily\Introscope9.0\

■ UNIX: /root/Introscope9.0/

■ For SAP:

■ On Windows: C:\usr\sap\ccms\wilyintroscope\

■ On UNIX: /usr/sap/ccms/wilyintroscope/

WARNING: If you are installing on Linux and pasting in the path, be sure the path does not include a leading space. If the path has a leading space, the installer interprets the path as relative, not absolute.

If you are using an installer that includes a bundled JVM, the Configure JVM Settings window opens.



Note: If you are installing the Enterprise Manager and the APM database separately, do not use the same installation directory for the Enterprise Manager and the APM database. For example, use the default directory when installing the Enterprise Manager, and specify another directory, such as /home/apm as the installation directory for the APM database. Using the same directory for both the Enterprise Manager and APM database can cause the installer to overwrite uninstall data that is required to uninstall the Enterprise Manager.

4. If desired, select Yes to configure JVM settings during the installation. Select No to accept the defaults, or if you plan to configure them manually later.

If you choose Yes, a JVM Settings window opens for each Introscope component during the installation.

5. Click Next to open the Specify External Components window.

6. The installer asks for the location of the External Components Package (see External component packages (see page 51)). The installer automatically detects the External Components Package if it is in the same directory as the installer file.

Use the Browse button to select the file. You must select the file itself in the file explorer, not just its directory.

To continue, click Next.

7. The installer asks you to accept the terms of the End User License Agreement (EULA). This EULA is for third party products that Introscope and Wily CEM use. Read the agreement, and then, if you accept the terms, select I accept the terms of the License Agreement. The installation will not continue until you accept the terms of the license agreement.


8. In the Specify License window, click Browse to locate the CA Wily Introscope license file, then click Next.

During installation, the license file is copied into the <EM_Home>/license folder.

Note: If you are performing an SAP installation, this window does not appear.

If you don’t have a license, you can install it later. To install the license later, click Next, then click Skip License in the dialog box that opens. Later, when you’re ready to install the license, refer to Copying the Introscope license after installation (see page 76).

Next, go to Specifying the Enterprise Manager (see page 68).



Specifying the Enterprise Manager

These steps continue from Specifying the install directory, external components, and licenses (see page 66).

1. In the Enterprise Manager Port Settings window, click Next to accept the default port values, or change the values and then click Next.

Note: If the Enterprise Manager is behind a firewall, be sure to configure the firewall to allow access to the Enterprise Manager Connection and Web Server ports.

2. In the Enterprise Manager Clustering window, select Yes if this Enterprise Manager will be part of a cluster, or No if it will not.

Clustering enables an Enterprise Manager to manage other Enterprise Managers as a Manager of Managers. The managed Enterprise Managers are called Collectors.

If you select Yes in the Enterprise Manager Clustering window, the installer prompts you to specify whether this Enterprise Manager will be a Manager or a Collector. If you specify Manager, go to step 3.

If you select No in the Enterprise Manager Clustering window, or if you specify that this Enterprise Manager will be a Collector, the installer prompts you to specify the time to store data. Go to step 4.

3. If you selected Manager, specify the connection properties for a Collector and click Next.

The installer asks if you want to add another Collector. If you add another Collector, the installer asks for that Collector’s connection properties. You can add up to 10 Collectors per Enterprise Manager.

When you are finished adding Collectors, the installer prompts you to specify the time to store data. Go to step 4.

4. In the Enterprise Manager Transaction Storage window, specify the number of days to store Transaction Event data and click Next.

When assigning the transaction trace storage length, consider that increasing the storage time increases system overhead and disk storage requirements.

5. Specify a directory for trace data storage and click Next.

You can set a maximum allowable amount of disk space. This option is useful if space is a concern because of the number of transactions that will be stored and the length of time the data will be kept.

By default, Introscope creates the Transaction Event database in the <EM_Home>/traces directory. You can also specify a maximum of disk space, if appropriate to your storage needs.

Note: The disk space maximum specifies the point at which Introscope begins deleting historical data. The current day’s data (live data) is included in the maximum calculation. When the data cap is reached, Introscope begins deleting historical data—it does not delete live data.



6. Specify a directory for SmartStor data and click Next.

SmartStor continuously records all Introscope data in this directory, without the need for a database.

Note: You must use a separate, dedicated disk or I/O subsystem for SmartStor data to avoid affecting Enterprise Manager performance. For the recommended space allocation, see Enterprise Manager requirements (see page 26). See the CA Wily APM Sizing and Performance Guide and the spreadsheet SmartStorSizing.xls for SmartStor sizing information.

If you selected Yes in the Configure JVM Settings window (step 4), the Enterprise Manager Advanced JVM Settings window opens.

7. Specify the Java executable to use to run Introscope, and any appropriate command-line JVM arguments.

8. On Windows machines, configure whether the Enterprise Manager should run as a service.

Installing the Enterprise Manager as a Windows Service increases its availability.

If you configure the Enterprise Manager as a Windows Service, when the machine on which it runs starts, the Enterprise Manager starts automatically. It shuts down when the machine is shut down.

■ Click No to continue without configuring Enterprise Manager as a Windows Service.

■ Select Yes to configure the Enterprise Manager as a Windows Service, and:

■ Enter a unique service name for this instance of Enterprise Manager as Windows Service.

■ Accept the default display name, or enter a unique display name.

9. Click Next and review the pre-installation summary of your Enterprise Manager settings. Click Next to continue the installation, or go back to make corrections if necessary.

Next, go to Specifying the APM database (see page 70).



Specifying the APM database

These steps continue from Specifying the Enterprise Manager (see page 68).

1. When prompted to choose the APM database, select PostgreSQL or Oracle.

■ If you select PostgreSQL and you are installing an Enterprise Manager of Managers (MOM), go to step 2. If you’re installing a Collector Enterprise Manager, go to step 3.

■ If you select Oracle, go on to step 8.

Note: If you choose PostgreSQL, you can create a new database instance directly from the installer. If you choose Oracle, you must already have an Oracle database instance to which you can connect and an Oracle database user name and password that will be the APM database owner. For more information about the prerequisites for the database owner, see About the APM database schema owner for Oracle (see page 33).

2. Follow the prompts displayed to install or specify the database instance appropriate for your environment.

If you selected PostgreSQL: you have the following options:

■ Install database - Enables you to install a new PostgreSQL database instance and APM database schema - go to step 4

■ Upgrade database schema or create new database schema - Enables you to upgrade PostgreSQL and the APM database schema - go to step 5

■ Choose existing database instance and APM database schema - Enables you to connect to an existing APM database - go to step 3

■ Install database with default configurations - Enables you to install a database using default account and password information. You should only select this option if installing an environment for evaluation or testing. You should not use this option for a production environment.

If you selected Oracle, you have the following options:

■ Update schema or create new database schema - Enables you to connect to an Oracle database and update or add the APM database schema to that database - go to step 8

■ Use existing schema - Enables you to connect to an Oracle database that has the APM database schema installed - go to step 8



3. If you are setting up a Collector Enterprise Manager or selected Choose existing database, specify the connection information for the existing APM database, then click Next:

Database Host

The machine name or address that hosts the APM database.

Database Port

The port that is used by the Enterprise Managers to communicate with the APM database. The default is 5432.

Database Name

The name of the database instance. The default is cemdb.

Database Username

The database user name cannot contain special or upper-case characters. The default is admin.

Database Password

The password for the database user name.

Note: If the APM database is behind a firewall, be sure to configure the firewall to allow access to the database port.

The installer attempts to connect to the database. A warning message displays if the installer cannot connect to the database. Some situations in which this may occur are:

■ the database does not have the correct tablespace or schema or version.

■ the database is in use by another, non-clustered Enterprise Manager.

■ there is existing 4.5 TESS data in the database.

■ the user does not have create schema permissions.

Note: The installer does not prevent you from continuing. If desired, you can change the settings later by editing the properties in the tess-db-cfg.xml file. For details, see Specifying APM database settings after installation (see page 214).

If the connection to the existing database succeeds, the Database Configuration Summary window displays. Go to step 10.

If the connection to the existing database fails, click Re-enter Database Settings, or click OK to continue. If you continue without correcting the settings, you can modify them after the installer completes by editing the tess-db-cfg.xml file. (For details, see Specifying APM database settings after installation (see page 214).)



4. If you selected Install database, specify the directory name for the APM database, then click Next.

The default APM database installation directories are:

■ Windows: <EM_Home>\database

■ UNIX: /opt/database

Note: You must use a separate, dedicated disk or I/O subsystem for APM database data to avoid affecting Enterprise Manager performance. For the recommended space allocation, see Enterprise Manager requirements (see page 26). See the CA Wily APM Sizing and Performance Guide for sizing information.

WARNING: On Linux, if you change the database installation directory, do not change it to be under the /root directory. If you do so, PostgreSQL will install but fail to start. This is a PostgreSQL limitation.

5. Specify the port number and administrative account information for the PostgreSQL database instance, then click Next:

Database Connection Port

The port that is used by the Enterprise Managers to communicate with the APM database. The default is 5432.

PostgreSQL Administrator Username

The PostgreSQL administrator user account that has administrative privileges for the PostgreSQL database. The default account name is postgres.

PostgreSQL Administrator Password

The password for PostgreSQL administrator user account. The password must adhere to your organization’s password security policies.

Enter the password again in the Confirm Password field.



■ The installer creates a user account with the same name as the PostgreSQL Administration user name. Because this is also a user account, the password must adhere to your organization’s password security policies.

■ If a user account with this name already exists, the installation continues if the specified password matches the existing user account’s password. If the passwords do not match, the installation fails.

■ The installer uses the PostgreSQL Administrator user to create the operating system user account, the postgres service user account, and the PostgreSQL superuser account.

■ After the installer completes, you can change the operating system’s postgres account password and the PostgreSQL superuser password.

Note: The installer verifies the connection information at the end of the installation process. The installer cannot pre-check the password. For example, if you enter the PostgreSQL Administrator Password and it does not conform to your organization’s password security policies, the installer fails at the end of the installation. Review the installation log files for more information.

6. In the PostgreSQL Service User dialog, click OK to accept the password. If the password does not conform to your organization’s security policies, click Re-Enter Database Admin Settings to change the password.

7. Specify the following information for the APM database schema, then click Next and go to step 10:

Database Name

Type the name of the APM database schema. The default schema name is cemdb.

If you’re upgrading a database schema, use the name of the database schema you’re upgrading.

Database User

Type the database user name you want associated with the APM database schema. The database user name cannot contain upper case or special characters.

Password

Type the password for the database user associated with the APM database schema. Enter the password again in the Confirm Password field.

Note: If the existing database schema is a version that’s invalid to upgrade, the installer provides the option to create a new schema or to continue.



8. If you selected Oracle as the database type, select whether to update or create a new schema or use an existing schema.

In most cases, you should select the Upgrade Schema or Create New Schema option unless you have previously run the installer using the Database Only installation option. The default is to update or create a new schema.

If you select Use Existing Schema, you should verify that a valid APM database has been installed or will be installed by a database administrator.

9. Specify the connection information for the installer to use to connect to the Oracle database where the APM database schema should be installed.

Database Host

Specifies the host name or IP address of the computer where the Oracle database instance is installed.

Database Port

Specifies the port number for the Enterprise Manager to use to communicate with the APM database. The default port is 1521, which is also the default port for the LISTENER service in Oracle databases.

Database SID Name

Specifies the Oracle system identifier (SID) which is the unique name of the database instance. The database instance must already exist for the connection to be successful.

Database Username

Specifies the database user name that should own the APM database schema. This user must already exist as a valid database user in the database instance specified. For information about the requirements associated with this account, see About the APM database schema owner for Oracle (see page 33).

Database Password

Specifies the password for the database user that owns the APM database schema.

The installer will create the APM database schema under the database user name you specify.

Note: If you are creating a new schema, the user namespace you specify must be empty. If the installer detects any tables, views, or other database objects, it displays an error message and prompts you to enter a different user name.

10. Review your settings in the Database Configuration Summary, then click Install to continue.



Specifying WebView settings

These steps continue from Specifying the APM database (see page 70).

1. In the WebView Settings window, accept the default HTTP host and the Enterprise Manager port and host values, or enter other values and click Next.

2. On Windows machines, configure whether WebView should run as a service.

■ Click No to continue without configuring WebView as a Windows Service.

■ Select Yes to configure the WebView as a Windows Service, and:

■ enter a unique service name for this instance of WebView as Windows Service.

■ either accept the default display name, or enter a unique display name.

If you selected Yes in the Configure JVM Settings window (step 4), the WebView Advanced JVM Settings window opens.

3. Specify the Java executable to use to run WebView, and any necessary JVM command-line arguments.

4. Click Next and review the summary of your WebView settings. Click Next to continue the installation, or go back to make corrections, if necessary.

Next, go to Specifying ProbeBuilder advanced JVM settings (see page 75).

Specifying ProbeBuilder advanced JVM settings

These steps continue from Specifying WebView settings (see page 75).

If you selected Yes in the Configure JVM Settings window (step 4), the ProbeBuilder Advanced JVM Settings window opens.

1. Specify the Java executable to use to run the ProbeBuilder, and any necessary JVM command-line arguments.

2. Click Next and review the summary of your ProbeBuilder settings. Click Next to continue the installation, or go back to make corrections if necessary.

Next, go to Completing the installation (see page 76).



Completing the installation

These steps continue from Specifying ProbeBuilder advanced JVM settings (see page 75).

■ Click Install.

The installer notifies you when Introscope installation is complete.

If errors occur during the installation, the installer directs you to view the appropriate component log files. For assistance, contact CA Support.

Copying the Introscope license after installation

The Enterprise Manager requires a valid Introscope license in order to run. Usually, you install your Introscope license when installing the Enterprise Manager.

You can also install it after installing the Enterprise Manager, by copying it in to your <EM_Home>/license directory on the Enterprise Manager system.

Verifying the Enterprise Manager installation

To make sure that you installed the Enterprise Manager and related components correctly, ensure that the Enterprise Manager starts and does so without any error messages.

To verify the Enterprise Manager installation:

1. Start the Enterprise Manager. For details, see the Introscope Configuration and Administration Guide.

2. In the Enterprise Manager command console window, ensure that it starts without errors.

If you see the "Introscope Enterprise Manager started" message, this means that the Enterprise Manager installed successfully.

Installing the Workstation



This section includes instructions for installing just the workstation, in GUI mode.

In addition to installing the workstation, the Workstation installer also installs files for ChangeDetector. For details about configuring and using ChangeDetector, see the Introscope ChangeDetector User Guide.

After you install either the standalone Workstation or Java Web Start workstation, you need to install agents to see metric data. For details, see the Introscope Java Agent Guide and Introscope .NET Agent Guide.

To install the workstation:

1. Start the Workstation installer (see Selecting the correct Workstation-only installer (see page 46)).

The Introduction window opens.

2. Click Next.

3. The installer asks you to accept the terms of the CA End User License Agreement (EULA). This EULA is for CA Technologies products. Read the agreement, and then, if you accept the terms, select I accept the terms of the License Agreement. The installation will not continue until you accept the terms of the license agreement.

4. In the Choose Install Folder window you can click Next to accept the default installation directory, or click Browse to specify a different location and click Next. The Specify External Components window opens.

Note: Do not specify the installation directory with non-Roman characters, such as Japanese, when installing on a machine with an English-language locale. Although the installer accepts non-Roman characters, the Workstation cannot use the information to connect to the Enterprise Manager.

5. The installer asks for the location of the External Components Package (see External component packages (see page 51)).



6. The installer asks you to accept the terms of the End User License Agreement (EULA). Read the agreement, and then, if you accept the terms, select I accept the terms of the License Agreement. The installation will not continue until you accept the terms of the license agreement.


If you are using an installer that includes a bundled JVM, the Configure JVM Settings window opens.



7. Select Yes to configure JVM workstation settings during the installation. Select No to accept the defaults, or if you plan to configure them manually later. Click Next.

If you choose Yes, a JVM Settings window opens for each Introscope component during the installation.

8. In the Workstation Settings window, you can accept the default user, host, and port values, or type other values and click Next.

Note: An Admin user exists by default in the Enterprise Manager’s users.xml file. If you enter any other user name in this window, that user must exist in the Enterprise Manager’s users.xml file if you are using local authentication, or in the external authentication system. See the discussion about configuring Introscope security and permissions in the CA Wily APM Security Guide for information about adding new users.

If you selected No in step 7, the Configure JVM Settings window, the Pre-installation summary opens. Go to step 10.

If you selected Yes in step 7, the Configure JVM Settings window, the Workstation Advanced JVM Settings window opens.

9. Specify the Java executable to use to run Introscope, and any appropriate command-line JVM arguments, and click Next.

10. Review the summary of the Workstation settings. Click Next to continue the installation, or go back and make corrections, if necessary.

11. Click Install to install the Workstation.

Introscope installs the necessary files and displays the Install Complete window. The installer places installation log files in the <EM_Home>\install directory.

Verifying the Workstation installation

To ensure the Workstation is installed correctly, be sure that you can run both the Enterprise Manager and Workstation without errors.

To verify the Introscope Workstation installation:

1. Start the Enterprise Manager. For details, see the Introscope Configuration and Administration Guide.

2. Start the Workstation. For details, see the Introscope Workstation User Guide.

When the Workstation connects successfully to the Enterprise Manager, the Workstation opens. If you have not yet added Introscope agents, you won’t see data in the Workstation Investigator.



Installing the Workstation using Java Web Start

Installing the Workstation with Java Web Start enables on-line deployment of the Workstation, and ensures that users have the version of the Workstation that matches the Enterprise Manager.

The Java Web Start installation uses the Enterprise Manager’s embedded Web server and a Java Web Start service that starts automatically when the Enterprise Manager starts.

In a Java Web Start deployment, users launch the Workstation by opening a browser to the Java Web Start URL. The Enterprise Manager installation puts a Workstation Web Start shortcut on the Start menu on the Enterprise Manager machine, from which the Web Start can be accessed.

Each time the user opens the URL, Java Web Start checks to see if the installation is current and updates it if necessary.

After you finish installing the Workstation, be sure to install agents so that the Enterprise Manager has data to display. For details, see the Introscope Java Agent Guide and Introscope .NET Agent Guide.

To install the Workstation using Java Web Start:

1. Open a browser to:

http://<EM_Host>:8081/workstation

Note: If Java Web Start is not installed on your machine, you are prompted to download it. Close and reopen the browser after installation.

The Workstation login page opens.

Note: If more than one Enterprise Manager is running on a single machine, or if the default Web Server port of 8081 is in use by another service on the machine, it may be necessary to specify an alternate port for the Enterprise Manager Web server by setting introscope.enterprisemanager.webserver.port in the Enterprise Manager properties file. For more information, see the Introscope Configuration and Administration Guide.

2. Create a URL shortcut for the Java Web Start URL.

Drag and drop the URL to your Desktop or desired folder. If you use Internet Explorer, drag the IE icon, at the beginning of the address bar, to the desired location.



Designating the Java version for Java Web Start

Java Web Start will launch the workstation using a Java version defined by these two files:

■ <EM_Home>\product\enterprisemanager\plugins\com.wily.introscope.workstation.webstart_9.0.0\WebContent\jnlp\workstation.jsp

■ <EM_Home>\product\enterprisemanager\plugins\com.wily.introscope.workstation.webstart_9.0.0\WebContent\jnlp\ com.wily.introscope.workstation.feature_9.0.0.jsp

In both of these files, you will find a j2se node with a version attribute:

<j2se version="1.6*&1.6.0_05+" ... />

Java Web Start will use this attribute to determine the Java version that will be used to launch the Workstation.

The attribute lists Java version ranges in preferred order from first to last. Each range is separated by a single space. Java Web Start checks the client system for all version ranges in the listed order and installs the first qualifying version that it finds.

If Java Web Start does not find a pre-installed JVM that matches the listed version ranges, it downloads the newest available version permitted by all of the version ranges taken together, regardless of order.

For example: When the j2se version is set to "1.6*&1.6.0_05+" ...

■ If a valid update level of Java 1.6 is not found, Java Web Start will then check the client system for Java 1.6, update 5 or later.

1.6* = version starts with 1.6

& = and

1.6.0_05+ = version is 1.6 update 5 or later

■ If a valid update level of Java 1.6 is not found, Java Web Start will download the newest available version permitted by any of the version ranges. So, as of this writing, Java Web Start would download 1.6 update 6 at this step. As later updates of 1.6 are released, Java Web Start will download those instead. It would never download Java 1.7 since the version range does not permit it.

CA Wily has deliberately chosen 1.6.0_05 as the minimum update level because this update is the earliest to address critical security issues in Java (see http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-1185). Users can customize the ranges to allow earlier update levels at their own risk.

If you edit the version range list, be sure to edit it in both workstation.jsp and com.wily.introscope.workstation.feature_9.0.0.jsp.

http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-1185

http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-1185

Uninstalling Introscope



By default, the uninstaller runs in the mode in which the installer originally ran. If your installer did not include a bundled JVM, you can uninstall your Introscope components in a different mode than the installation was performed. For information on which installers have JVMs, see About Introscope bundled JVMs (see page 48).

If your environment supports it, and you want to run the uninstaller mode in a different mode than you used for the installation, follow the steps in Forcing an uninstall mode (see page 82) before running the uninstaller.

Note: If you previously had both the Enterprise Manager and Workstation installed, you must uninstall the Workstation before uninstalling the Enterprise Manager.

To uninstall Introscope:

1. Locate the uninstaller for your platform.

■ Windows: <EM_Home>\UninstallerData\base\Uninstall_Introscope.exe

■ UNIX: <EM_Home>/UninstallerData/base/Uninstall_Introscope

■ OS/400 and other—<EM_Home>/UninstallerData/base/uninstaller.jar

Note: For z/OS, see Removing Introscope on z/OS (see page 82).

2. Run the uninstaller, using the appropriate command for your platform.

■ For .EXE or .BIN files—run the .exe or ./<bin file>

■ For .JAR files —run this command:

java -classpath uninstaller.jar uninstall

If Introscope was installed in GUI mode, the uninstaller starts in GUI mode.

Note: Removing Introscope in Console mode prompts for the information described in the steps that follow. Silent mode removes all components, without prompting you for input.

3. If you installed the Enterprise Manager or WebView as a Windows Service during the installation, a page opens, offering the option to deregister the service.

■ Select Yes, Deregister Service to remove the Enterprise Manager or WebView instance you configured as a Windows Service during installation. This command stops the service and deregisters it. The Windows Service is deleted as part of the uninstall process.

■ Select No, Keep Service to leave it.



4. Click Next.

The Confirm Uninstallation window opens.

5. Click Continue to uninstall all Introscope components that were originally installed.

Note: Introscope tells you to manually deregister any remaining Enterprise Managers or WebView instances configured as Windows Services, just in case you changed the name of the Windows Service configured during installation, or configured a service yourself, outside of the installation process.

6. Manually delete any extra files that exist in the Introscope directory.

7. Repeat the uninstall process on other machines as necessary.

Removing Introscope on z/OS

The recommended way to uninstall Introscope 9.0 on z/OS is to delete the Introscope install directory using an rm -rf command. (The executable uninstaller will not run properly on z/OS due to a third party bug.)

Note: For an active Introscope 9.0 installation on z/OS, it is important to keep the UninstallerData folder intact. If you delete the UninstallerData folder, you will not be able to upgrade to future versions of Introscope. Do not delete the UninstallerData folder unless you have decided to uninstall the entire instance.

Forcing an uninstall mode

By default, the uninstaller runs in the mode the installer originally ran in. For example, if you installed in GUI mode, the uninstaller also runs in GUI mode. For installers with bundled JVMs, however, you can force a different uninstall mode—for example, if you installed components in silent mode, you can run the uninstall in GUI mode to uninstall selected components.

The Console mode asks for the same information as the GUI mode. The silent mode uninstaller uninstalls everything in the background with no prompts.

You force a different uninstall mode by specifying the desired uninstall mode in the uninstaller’s .LAX file.



To specify the uninstall mode in the uninstaller’s .LAX file:

1. Open the uninstaller file:

■ To uninstall the Enterprise Manager, open <EM_Home>/Uninstaller Data/base/Uninstall_Introscope.lax.

■ To uninstall the Workstation, open <EM_Home>/Uninstaller Data/ws/Uninstall_Introscope_Workstation.lax.

2. Find the property lax.command.line.args=$CMD_LINE_ARGUMENTS$ -u

3. Modify the property with the flag that forces the appropriate mode:

■ lax.command.line.args=$CMD_LINE_ARGUMENTS$ -u -i swing

■ lax.command.line.args=$CMD_LINE_ARGUMENTS$ -u -i console

■ lax.command.line.args=$CMD_LINE_ARGUMENTS$ -u -i silent

4. Save changes to the file.


Chapter 6: Installing Introscope in silent mode

This section provides instructions for installing Introscope components in console mode. For information about Introscope installation modes, see About installation modes.

If you are upgrading an existing Introscope installation, consult Preparing for Introscope-related upgrades (see page 153) to be sure that the necessary files are backed up before performing a new installation.


Preparing for silent mode installation (see page 85) Silent mode installation settings (see page 87) Launching silent mode installers (see page 118)

Preparing for silent mode installation

You can install or upgrade Introscope in silent mode. In silent mode, the installer runs from a command line and takes input from a response file. This makes multiple installations or upgrades of Introscope easy.

Silent mode is supported on all platforms.

The silent mode installer runs in the background with no feedback. See Installing Introscope in GUI or console mode (see page 59) to review the information required for installation.

After installation, you can check the results in the installer logs.

To upgrade in silent mode, see About silent mode upgrades (see page 228).

Silent mode installation overview

Here is an overview of the silent installation process:

1. Edit the response file. See Using a response file (see page 86).

2. Edit the ca-eula.txt and eula.txt files. See Downloading and editing external files (see page 87).

3. Run the installer from the command line, pointing to the response file. See Launching silent mode installers (see page 118).

Preparing for silent mode installation


Using a response file

Instead of asking the user for input during the installation process, the silent install takes input from a prepared response file.

You can use an automatically generated response file, or modify the sample response file provided with your installation.

Sample response file

You can edit a sample response file with the settings you want to use during installation, then use this file for subsequent silent mode installs. The sample response file is found in:

<EM_Home>/examples/installer/SampleResponseFile.txt

The response file can have any name, and can be located in any directory—you specify the name and location in the command line when invoking silent mode for the installer.

The properties in the response file are similar to those in the usual properties files.

Automatically generated response file

The automatically generated response file is created when Introscope is installed, and it contains the settings specified during the install process. You can use this response file for subsequent silent mode installations or upgrades.

The file, in the <EM_Home>/install/ directory, is named using the date and time information of the last installation. For example, an installation done April 30, 2010 at 7:10:00 a.m. would have a response file with this name:

<EM_Home>/install/autogenerated.responsefile.

2010.4.30.7.10.00

Response file guidelines

When specifying directory paths, follow these guidelines:

■ On Windows, escape backslash characters. For example:

C:\\Program Files\\CA Wily\\Introscope9.0d\\

■ On UNIX, append a slash to directory names. For example:

/tmp/Wily1/Introscopedirectory/

■ Uncomment properties that configure JVM settings.

■ If you specify a relative paths, it should be relative to the installer launch directory.

Silent mode installation settings


Downloading and editing external files

Before starting the installation process, you must download third-party external component package files, then edit two End User License Agreements (EULA).

IMPORTANT! The installation cannot proceed unless you follow these steps.

See External component packages (see page 51) and download the files for your system. Note the location on your network of the downloaded files. You will supply this location in the response file.

Editing the eula.txt and ca-eula.txt files

IMPORTANT! You must perform this step to signify acceptance of both End User License Agreements (EULA), or the installer does not proceed.

To edit the eula.txt file to agree to the EULA:

1. Open the eula.txt file.

2. Read the agreement.

3. If you agree to the terms and conditions of the agreement, edit the LGPL property (located at the end of the file) to:

LGPL=accept


To edit the ca-eula.txt file to agree to the EULA:

1. Open the ca-eula.txt file.

2. Read the agreement.

3. If you agree to the terms and conditions of the agreement, edit the CA-EULA property (located at the end of the file) to:

CA-EULA=accept



The following properties can be configured in the response file. Each installer uses a separate response file.


Main installer silent mode settings (see page 88) Standalone PowerPack installer silent mode settings (see page 114) SAP installer silent mode settings (see page 117)



Main installer silent mode settings

This section contains information about the properties you must specify to install CA Wily APM components silently without user interaction.


General Settings (see page 88) Upgrade Settings (see page 91) Enterprise Manager Install Settings (see page 93) Enterprise Manager Clustering Settings (see page 94) Enterprise Manager Transaction Storage Settings (see page 95) Enterprise Manager Data Storage Settings (see page 96) Enterprise Manager as Windows Service Settings (see page 97) Enterprise Manager Advanced JVM settings (see page 98) APM Database Settings (see page 99) WebView installation settings (see page 108) WebView as Windows Service Installation settings (see page 109) WebView Advanced JVM settings (see page 110) ProbeBuilder Installation settings (see page 111) ProbeBuilder Advanced JVM settings (see page 111) Workstation installer silent mode settings (see page 112) Install Anywhere settings (see page 113)

General Settings

This section describes the properties in the General Settings section of the installer response file.

USER_INSTALL_DIR

Specifies the directory where to install Introscope.

Property settings

The absolute path and directory name. On Windows, to enter a backslash, enter an extra backslash as an escape sequence. Paths must be absolute and end with a directory separator. If no directory is specified, the defaults are used. On UNIX, the directory is under the user’s home directory. On Windows, the exact drive letter and name of the Program Files directory may vary depending on the Windows configuration.



Default

UNIX: /root/Introscope9.0.0.0/

Windows: C:\\Program Files\\CA Wily\\Introscope9.0.0.0\\

Example

USER_INSTALL_DIR=C:\\IntroscopeSilentInstall\\

silentInstallChosenFeatures

A comma-separated list of the features to install.

Property settings

Enterprise Manager, WebView, ProbeBuilder, EPA, Database

Note: "Database" refers to the APM database. For more information about this database, see the Introscope Configuration and Administration Guide.

Default

silentInstallChosenFeatures=Enterprise Manager,WebView,ProbeBuilder,EPA

Example

silentInstallChosenFeatures=Enterprise Manager,WebView,ProbeBuilder,EPA,Database

externalComponentPackage

Specifies the location of the external component package (see External component packages (see page 51)).

If you are installing the Enterprise Manager or WebView, you must also specify the external component package location.

Property settings

The absolute or relative path to the external component packages. Introscope resolves the relative path based on the installer launch directory. On Windows, to enter a backslash, enter an extra backslash as an escape sequence. You can download the external component packages from http://opensrcd.ca.com/ips/osgi.





Default

There is no default setting for this property.

Example

Windows: C:\\osgiPackages.v<x.y>.windows.zip

UNIX: /osgiPackages.v<x.y>.unix.tar

where <x.y> is a valid version string.

eulaFile

The location of the external component library's End User License Agreement (EULA), a file named eula.txt. The file is usually located in the same directory as the externalComponentPackage location.

If you are installing the Enterprise Manager or WebView, you must also specify the EULA file location.

Note: In addition to specifying the location of the EULA file, you must edit the EULA file to agree to the license agreement. See Editing the eula.txt and ca-eula.txt files (see page 87).

Property settings

The absolute or relative path to the external component package’s end user license agreement (EULA) file. Introscope resolves the relative path based on the installer launch directory. On Windows, to enter a backslash, enter an extra backslash as an escape sequence.

You must acknowledge and accept the EULA in order to install the product. To acknowledge and accept the agreement, open the file in a text editor and read the terms and conditions. Edit the end of the file to indicate acceptance of the license and save your changes. Use this eulaFile property to specify the location of the edited file.

Default


Example

Windows: C:\\Documents and Settings\\eula.txt

UNIX: /home/myuser/eula.txt



ca-eulaFile

Location of the CA End User License Agreement (EULA), a file named ca-eula.txt. The file is usually located in the same location as the main and workstation installers.

Note: In addition to specifying the location of the EULA file, you must edit the EULA file to agree to the license agreement. See Editing the eula.txt and ca-eula.txt files (see page 87).

Property settings

The absolute or relative path to the CA end user license agreement (CA-EULA) file. Introscope resolves the relative path based on the installer launch directory. On Windows, to enter a backslash, enter an extra backslash as an escape sequence.

You must acknowledge and accept the CA-EULA in order to install the product. To acknowledge and accept the agreement, open the file in a text editor and read the terms and conditions. Edit the end of the file to indicate acceptance of the license and save your changes. Use this eulaFile property to specify the location of the edited file.

Default


Example

Windows: C:\\Documents and Settings\\ca-eula.txt

UNIX: /home/myuser/ca-eula.txt

Upgrade Settings

This section describes settings listed in the Upgrade Settings section of the installer response file.



shouldUpgrade

Specifies whether to upgrade an existing Introscope installation. For valid versions from which to upgrade, see About upgrade requirements (see page 41).

The upgrade procedure is not reversible. CA Technologies recommends creating a full backup of your Introscope installation before initiating an upgrade.

To do an upgrade in silent mode, specify the following other properties:

■ USER_INSTALL_DIR

■ externalComponentPackage

■ eulaFile

■ ca-eulaFile

■ (Optional) upgradedInstallDir

■ (Optional) shouldConfigEmAsService, emAsServiceName, emAsServiceDisplayName

Property settings

True or false

Default

shouldUpgrade=false

Example

shouldUpgrade=true

upgradedInstallDir

Specifies a new Introscope installation directory. If upgrading an existing Introscope installation, use this property to rename the installation directory. If you do not have permission to write to that directory, the silent upgrade fails.

Property settings

The absolute path and directory name. On Windows, to enter a backslash, enter an extra backslash as an escape sequence. Paths must be absolute and end with a directory separator. If no directory is specified, the defaults are used. On UNIX, the directory is under the user’s home directory. On Windows, the exact drive letter and name of the Program Files directory may vary depending on the Windows configuration.



Default


Example

Windows: C:\\IntroscopeSilentlyUpgradedInstall\\

UNIX: /IntroscopeSilentlyUpgradedInstall/

Enterprise Manager Install Settings

This section describes the settings in the Enterprise Manager Install Settings section of the installer response file.

wilyLicenseFile

Location of the CA Wily license file.

Property settings

The absolute path and filename of the CA Wily license file. On Windows, to enter a backslash, enter an extra backslash as an escape sequence.

Default


Example

Windows: C:\\Documents and Settings\\CAWilyLicense.txt

UNIX: /home/myuser/CAWilyLicense.txt

emPort

The port used by the Enterprise Manager to listen for incoming connections.

Property settings

A valid, available port number.

Default

5001

Example

emPort=5030



emWebPort

The port used by the Enterprise Manager to serve web applications.

Note: This is also the port used by Java Web Start. See Installing the Workstation using Java Web Start (see page 79).

Property settings


Default

8081

Example

emWebPort=8050

Enterprise Manager Clustering Settings

This section describes the properties listed in the Enterprise Manager Clustering Settings section of the installer response file.

shouldClusterEm

Specifies whether or not the Enterprise Manager is part of a cluster.

Property settings

True or false. True specifies the Enterprise Manager is in a cluster.

Default

False

Example

shouldClusterEm=true

emClusterRole

For Enterprise Managers that are part of a cluster, this property specifies whether the Enterprise Manager is a Collector or a Manager of Managers (MOM).

Property settings

Either Collector or Manager. Values are case-sensitive.



Default

This property has no default setting.

Example

emClusterRole=Collector

emCollectorHost.n and emCollectorPort.n

If installing an Enterprise Manager as a MOM, use the emCollectorHost and emCollectorPort properties to specify up to ten managed collectors that are managed by the MOM. For each Collector, specify a pair of these properties with a unique number.

If emClusterRole is Manager, specify the host and port for up to ten managed collectors. Each pair must have a unique numeral for its pair. The limit is 10 pairs.

Property settings

Specify the fully qualified hostname for emCollectorHost and a valid, available port number for emCollectorPort. Each pair of emCollectorHost and emCollectorPort must have a unique number.

Default

There are no default settings for these properties.

Example

emCollectorHost.1=myManagedEm.mydomain.com

emCollectorPort.1=5005

emCollectorHost.2=computerName.domain.com

emCollectorPort.2=5006

Enterprise Manager Transaction Storage Settings

This section describes the properties listed in the Enterprise Manager Transaction Storage Settings section of the installer response file.



emTxTraceDataShelfLife

Specifies the fixed length of time (in days) to store trace data to disk.

Default

14 (days)

Example

emTxTraceDataShelfLife=30

emTxTraceDir

Specifies a customized directory name in which to store transaction trace data. On Windows, to enter a backslash, enter an extra backslash as an escape sequence.

Default

emTxTraceDir=traces

Example

emTxTraceDir=TsxnTraces

emTxTraceDiskSpaceCap

The maximum amount of disk space reserved to store transaction trace data. This setting is optional, useful if disk space is a concern.

Default

This property does not have a default setting.

Enterprise Manager Data Storage Settings

You must use a separate, dedicated disk or I/O subsystem for SmartStor data to avoid affecting Enterprise Manager performance. For the recommended space allocation and other requirements, see Enterprise Manager requirements (see page 26). See the CA Wily APM Sizing and Performance Guide and the spreadsheet SmartStorSizing.xls for SmartStor sizing information.



emDataStoreDir

Name of the SmartStor directory. On Windows, to enter a backslash, enter an extra backslash as an escape sequence.

Default

emDataStoreDir=data

Example

emDataStoreDir=SmartStor

Enterprise Manager as Windows Service Settings

This section describes the properties listed in the Enterprise Manager as Windows Service Settings section of the installer response file.

shouldConfigEmAsService

Specifies whether to configure the Enterprise Manager as a Windows service.

Property settings

True or false.

Default

shouldConfigEmAsService=false

Example

shouldConfigEmAsService=true

emAsServiceName

If the Enterprise Manager is configured as a service, a unique name for the Service.

Property settings

A text string of 8 or fewer characters without spaces.

Default

emAsServiceName=IScopeEM

Example

emAsServiceName=EM7



emAsServiceDisplayName

If the Enterprise Manager is configured as a service, a display name for the Service. May contain spaces.

Property settings

A case-sensitive alphanumeric string.

Default

emAsServiceDisplayName=Introscope Enterprise Manager

Example

emAsServiceDisplayName=Introscope EM1

Enterprise Manager Advanced JVM settings

This section describes the properties listed in the Enterprise Manager Advanced JVM Settings section of the installer response file.

These options should only be configured by advanced users. If you are unsure of the values to enter, keep the defaults by leaving these properties commented out.

emLaxNlCurrentVm

Path to the JVM that will be used to run the Enterprise Manager.

Property settings

The path may be absolute or relative to <EM_Home>. On Windows, to enter a backslash, enter an extra backslash as an escape sequence.

Default

By default, Introscope points to the JRE folder which is created during the installation. Edit this property if you want to point to an alternate JVM.

Example

Windows: emLaxNlCurrentVM=jre\\bin\\java.exe

UNIX: emLaxNlCurrentVM=jre/bin/java



emLaxNlJavaOptionAdditional

Command line arguments to be used by the Enterprise Manager JVM.

Property settings

For 32-bit Sun JVMs, CA Technologies recommends the following settings:

-showversion -XX:+UseConcMarkSweepGC -XX:+UseParNewGC

-XX:CMSInitiatingOccupancyFraction=50

If you are using both Hot Failover and the Wily CEM Console, add this setting:

-Dosgi.clean=false

Default

This property has a default setting that is commented out.

#emLaxNlJavaOptionAdditional=-Xms512m -Xmx1024m -XX:MaxPermSize=256m

APM Database Settings

This section describes the settings used to configure the connection from an Enterprise Manager to an APM database. The specific properties you are required to set depend on the database type and whether you are installing a new PostgreSQL database instance, upgrading a database schema, or connecting to an existing database.

chosenDatabaseIsPostgres

Specifies whether you want the APM database to be a PostgreSQL database. You must set this property to true if you want to install or upgrade a PostgreSQL database instance on the computer where you run the silent installation. If you want to use an Oracle database, set this property to false.

Property settings

True or False.

Default

true

Example

chosenDatabaseIsPostgres=true



chosenDatabaseIsOracle

Specifies whether you want the APM database to be an Oracle database. You must set this property to true if you want to connect to an Oracle database instance and create or upgrade the APM database schema. Note that the Oracle database instance must be installed and running and have a database user with the proper permissions for creating the APM database schema. For more infomation about the requirements for using an Oracle database, see Using Oracle for the APM database (see page 31). If you want to use an Oracle database, set this property to true.

Property settings

True or False.

Default

false

Example

chosenDatabaseIsOracle=false

dbHost

Specifies the host name of the machine where the APM database is installed or where the APM database will be installed if you are using PostgreSQL as the database. This property is not applicable if you are using an Oracle database for the APM database schema.

Property settings

A valid IP address.

Default

The default value is the IP address for localhost, 127.0.0.1.

Example

dbHost=192.168.17.201



dbPort

Specifies the port number the Enterprise Manager uses to connect to the APM database if you are using PostgreSQL as the database. This property is not applicable if you are using an Oracle database for the APM database schema.

Property settings


Default

5432

Example

dbPort=5432

dbName

Specifies the name of the APM database schema if you are using PostgreSQL as the database. This property is not applicable if you are using an Oracle database for the APM database schema.

Property settings

A text string that does not contain special or upper-case characters.

Default

cemdb

Example

dbName=cemdb



dbUser

Specifies the name of the database user account if you are using PostgreSQL as the database. This property is not applicable if you are using an Oracle database for the APM database schema.

Property settings


Default

admin

Example

dbUser=admin

dbPassword

Specifies the password for the database user account if you are using PostgreSQL as the database. This property is not applicable if you are using an Oracle database for the APM database schema.

Property settings


Default

wily

Example

dbPassword=qtest

validateDatabase

Option to validate database information. If enabled, the installer displays an error message if any of the following situations occur:

■ the installer cannot connect

■ the database does not have the correct tablespace, schema, or version

■ the database is in use by another, non-clustered Enterprise Manager

■ there is existing 4.5 TESS data in the database

■ the user does not have create schema permissions.

Note: The installer produces a warning message and writes it to silent.install.failed.txt, but does not prevent you from continuing.



Property settings

True or false.

Default

validateDatabase=true (commented out)

upgradeSchema

Specifies whether you want to upgrade an existing APM database schema to the current version if you are using PostgreSQL as the database. This property is not applicable if you are using an Oracle database for the APM database schema.

Property settings

True or false

Default

This property set to true but commented out by default.

Example

upgradeSchema=true



databaseDir

Specifies the directory name for the APM database if you are using PostgreSQL as the database. This property is required when you are installing a new PostgreSQL database instance. This property is not applicable if you are using an Oracle database for the APM database schema.

If you are installing a new PostgreSQL database instance, use a separate, dedicated disk or I/O subsystem to avoid affecting Enterprise Manager performance. For the recommended space allocation, see Enterprise Manager requirements (see page 26). See the CA Wily APM Sizing and Performance Guide for sizing information.

Property settings

If the directory name or path contains spaces, you must use a backslash to escape the spaces or use quotes around the path.

Default

For Linux and Solaris, the default path is /opt/database. For Windows the default path is a database folder in the installation directory. For example:

C:\Program Files\CA Wily\Introscope9.0\database

Example

databaseDir=database

dbAdminUser

Specifies the PostgreSQL administrator user name if you are using PostgreSQL as the database. This property is required when you are installing or upgrading a PostgreSQL database instance.


Default

postgres

Example

dbAdminUser=postgres



dbAdminPassword

Specifies the PostgreSQL administrator account password if you are using PostgreSQL as the database. This property is required when you are installing or upgrading a PostgreSQL database instance.


Property settings

A text string that adheres to your organization’s password security policies.

Note: If the default PostgreSQL Administrator password does not comply with your organization’s password security policies, the database installation fails. Review the installation log files for more information. The installer cannot pre-check the password.

Default

C@wilyapm90

Example

dbAdminPassword=C@wilyapm90

useExistingSchemaForOracle

Specifies whether you want to use an existing APM database schema on an Oracle database. Set this property to true if you want the Enterprise Manager to connect to an existing APM database. Set this property to false if you want to create new schema on a Oracle database.This property is not applicable if you are using PostgreSQL for the APM database schema.

Property settings

True or false

Default

This property set to false by default.

Example

useExistingSchemaForOracle=false



oracleDbHost

Specifies the host name or IP address of the machine where the Oracle database instance is installed.

Property settings

A valid host name or IP address.

Default

This property has no default value.

Example

oracleDbHost=sfcedar05

oracleDbPort

Specifies the port number the Enterprise Manager uses to connect to the APM database if you are using Oracle as the database. This property is not applicable if you are using PostgreSQL for the APM database schema.

Property settings


Default

This property has no default value. However, the default port for the LISTENER process is 1521.

Example

oracleDbPort=1521



oracleDbSidName

Specifies the system identifier (SID) name of the Oracle database instance. This property is not applicable if you are using PostgreSQL for the APM database schema.

Property settings

A text string.

Default

This property has no default value. However, the default SID for the Oracle database is orcl.

Example

oracleDbSidName=cemdb

oracleDbUsername

Specifies the name of the database user account you want to associate with the APM database schema in an Oracle database. The user account you specify is the database owner of the APM schema and requires specific rights and roles. For more information about the requirements that are specific to using an Oracle database, see Using Oracle for the APM database (see page 31).

Property settings

A valid Oracle database user account.

Default


Example

oracleDbUsername=apmadmin



oracleDbPassword

Specifies the password of the database user account you want to associate with the APM database schema in an Oracle database.

Property settings

A valid password for the Oracle database user account.

Default


Example

oracleDbPassword=Apm4$

WebView installation settings

This section describes the properties listed in the WebView Install Settings section of the installer response file.

wvPort

Port on which WebView will listen for connections.

Property settings

A valid, available port.

Default

wvPort=8080

wvEMHost

Enterprise Manager host to which WebView connects.

Property settings

A valid, fully qualified domain name, or localhost.

Default

wvEMHost=localhost



wvEMPort

Enterprise Manager port on which WebView connects.

Default

wvEMPort=5001 (6001 for SAP)

WebView as Windows Service Installation settings

This section describes the properties listed in the WebView as Windows Service Settings section of the installer response file.

shouldConfigWvAsService

Specifies to configure WebView as a Windows service. During an upgrade, if this property is set to true, Introscope revises the original values to those specified in this section.

Property settings

True or false

Default

shouldConfigWvAsService=false

wvAsServiceName

If shouldConfigWvAsService =true, specify a unique name for the service. The Windows registry uses the service name.

Property settings

The service name must be 8 or fewer characters, without spaces.

Default

wvAsServiceName=IScopeWV



wvAsServiceDisplayName

If shouldConfigWvAsService =true, specify a unique display name for the service. Windows control panels and the NET START command display this name.

Property settings

The display name may contain spaces.

Default

wvAsServiceDisplayName=Introscope WebView

WebView Advanced JVM settings

This section describes the properties listed in the WebView Advanced JVM Settings section of the installer response file.

Note: These options should only be configured by advanced users. If you are unsure of the values to enter, keep the defaults by leaving these properties commented out.

wvLaxNlCurrentVm

Path to the JVM that will be used to run WebView.

Property settings


Default


Example

Windows: emLaxNlCurrentVM=jre\\bin\\java.exe

UNIX: emLaxNlCurrentVM=jre/bin/java



wvLaxNlJavaOptionAdditional

Command line arguments to be used by the WebView JVM.

Property settings

The recommended setting for the headless switch is:

■ false for Windows, AIX, HP-UX, Linux, and Solaris platforms

■ true for other UNIX and mainframe platforms

Default

wvLaxNlJavaOptionAdditional=-Xms128m -Xmx512m -Djava.awt.headless=false

ProbeBuilder Installation settings

There is nothing to set in this section.

ProbeBuilder Advanced JVM settings

This section describes the properties listed in the ProbeBuilder Advanced JVM Settings section of the installer response file.

Note: These options should only be configured by advanced users. If you are unsure of which values to enter, keep the defaults by leaving these properties commented out.

pbLaxNlCurrentVm

Path to the JVM that will be used to run the Workstation.

Property settings


Default


Example

Windows: pbLaxNlCurrentVM=jre\\bin\\java.exe

UNIX: pbLaxNlCurrentVM=jre/bin/java



pbLaxNlJavaOptionAdditional

Command line arguments to be used by the ProbeBuilder JVM.

Default

pbLaxNlJavaOptionAdditional=-Xms32m -Xmx64m (commented out)

Workstation installer silent mode settings

This section describes the properties in the Workstation installer’s response file.

For information about the properties in the General Settings section of the Workstation installer’s response file, see General Settings (see page 88).


Workstation Install settings (see page 112) Workstation Advanced JVM settings (see page 113)

Workstation Install settings

These options are applicable to the response file used with the Workstation installer.

wsUser

The workstation user account. The Introscope administrator must create this account and grant it access privileges. For more details about granting access privileges, see the CA Wily APM Security Guide.

Default

wsUser=Admin

wsHost

Enterprise Manager host to which the workstation connects.

Property settings

A fully qualified domain name or localhost.

Default

wsHost=localhost



wsPort

Enterprise Manager port on which the workstation connects.

Property settings


Default

wsPort=5001 (6001 for SAP)

Workstation Advanced JVM settings

These options should only be configured by advanced users. If you are unsure of which values to enter, keep the defaults by leaving these properties commented out.

wsLaxN1CurrentVM

Path to the JVM that will be used to run the Workstation.

Property settings


Default


Example

Windows: wsLaxNlCurrentVM=jre\\bin\\java.exe

UNIX: wsLaxNlCurrentVM=jre/bin/java

wsLaxNlJavaOptionAdditional

Command line arguments to be used by the Workstation JVM.

Default

wsLaxNlJavaOptionAdditional=-client -Xms64m -Xmx256m (commented out by default)

Install Anywhere settings

Do not edit this section.



Standalone PowerPack installer silent mode settings

These options are applicable to the response file used with the standalone PowerPack installer.


USER_INSTALL_DIR (standalone PowerPack) (see page 114) silentInstallChosenFeatures (see page 114) shouldInstallPPForOracleDB (see page 115) shouldInstallSiteMinderSNMP (see page 115) shouldInstallTibcoEMS (see page 115) shouldInstallWMBroker (see page 115) shouldInstallPPForWebSphereMQ (see page 116) shouldInstallPPForWebServers (see page 116) shouldInstallPPForWebServersIIS (see page 116) shouldInstallSPMonitor (see page 117) emHost (see page 117) emPort (see page 117)

USER_INSTALL_DIR (standalone PowerPack)

The absolute path and directory name where you install the PowerPacks.

Property settings

On Windows, to enter a backslash, enter an extra backslash as an escape sequence. Paths must be absolute and end with a directory separator. If no directory is specified, the defaults are used. On UNIX, the directory is under the user’s home directory. On Windows, the exact drive letter and name of the Program Files directory may vary depending on the Windows configuration.

Default

UNIX: /root/Introscope9.0.0.0/

Windows: C:\\Program Files\\CA Wily\\Introscope9.0.0.0\\

silentInstallChosenFeatures

Do not edit this property.



shouldInstallPPForOracleDB

Specifies whether or not to install the Introscope PowerPack for Oracle Database.

Property settings

Set this property to true to install this PowerPack. To not install this PowerPack, either leave the property blank or set it to false.

Default

shouldInstallPPForOracleDB=false

shouldInstallSiteMinderSNMP

Specifies whether or not to install the Introscope SNMP Collector for SiteMinder.

Property settings

Set this property to true to install this PowerPack item. To not install this PowerPack item, either leave the property blank or set it to false.

Default

shouldInstallSiteMinderSNMP=false

shouldInstallTibcoEMS

Specifies whether or not to install Tibco Enterprise Message Service.

Property settings

Set this property to true to install this SOA extension. To not install this PowerPack, either leave the property blank or set it to false.

Default

shouldInstallTibcoEMS=false

shouldInstallWMBroker

Specifies whether or not to install webMethods Broker.

Property settings

Set this property to true to install this SOA extension. To not install this PowerPack, either leave the property blank or set it to false.

Default

shouldInstallWMBroker=false



shouldInstallPPForWebSphereMQ

Specifies whether or not to install the PowerPack for WebSphere MQ Connectors and Messaging System.

Property settings


Default

shouldInstallPPForWebSphereMQ=false

shouldInstallPPForWebServers

Specifies whether or not to install the PowerPack for WebServers.

Property settings


(This PowerPack is not supported on HP-UX and AIX.)

Default

shouldInstallPPForWebServers=false

shouldInstallPPForWebServersIIS

Specifies whether or not to install the IIS Monitoring Components for the PowerPack for WebServers.

Property settings

If shouldInstallPPForWebServers=true, you can also specify to install the PowerPack for Web Server IIS. To do so, uncomment this property and set to true. (Windows platforms only).

Default

shouldInstallPPForWebServersIIS=false



shouldInstallSPMonitor

Specifies whether or not to install the SP Monitor for SharePoint Portal.

Property settings


(Windows Server 2003 and Windows Server 2008 only.)

Default

shouldInstallSPMonitor=false

emHost

Enterprise Manager host to which the PowerPack or SOA extension connects.

Default value

localhost

Property settings

A valid, fully qualified domain name, or localhost.

Default

emHost=localhost

emPort

The port used by the Enterprise Manager to listen for incoming connections.

Property settings


Default

5001

Example

emPort=5030

SAP installer silent mode settings

The SAP main installer and SAP workstation installer response files use the same settings that are in the regular installer. Refer to the appropriate sections for details.

Launching silent mode installers



This section contains the instructions for running the Introscope installers in silent mode.

Note: When installing on OS/400 or IBMi systems, to run the installer successfully, the JVM must be version 1.6 or later; other installers require at least version 1.5.x. Running Enterprise Manager and WebView requires a 1.6 JVM. For details on installer files, see Introscope installers (see page 43).

Launching silent mode installer on z/OS

After extracting the introscope<version>zOSinstall.tar file, you see two files:

■ runinstaller.sh: The runinstaller.sh script launches the installer, confirms that the specified response file exists, and confirms that there is at least 60 MB of space in the /tmp directory.

■ introscope<version>zOS.jar: You can use a Java command to launch the silent mode installer on z/OS—for example:

java -cp introscope9.0.x.yzOS.jar -f <absolute-path_to_responsefile>

To run the installer in silent mode on z/OS:

1. Before running the script, check that a JAVA_HOME environment variable exists by running:

echo $JAVA_HOME

2. If it exists, continue to step 3. If no such variable exists:

■ open the runinstaller.sh script in a text editor.

■ Find the line that sets the Java home.

■ Uncomment this line, and modify the path to specify your own Java home.

■ Save your changes, then launch the script.

3. Launch the script using:

runinstaller.sh introscope9.0.x.yzOS.jar -silent <absolute path to responsefile>



Launching silent mode installer on other platforms

Note: For OS/400, perform silent mode installation from Qshell.

To run the installer in silent mode:

■ For .exe or .bin files, specify the path to the installer and the absolute path to the response file:

installer.exe -f <absolute path to response file>

installer.bin -f <absolute path to response file>

For example:

[root@qaserver:/] ./introscope9.0.x.ysolaris.bin -f /tmp/myResponseFile.txt

■ For .JAR files (no bundled JVM), specify the path to the installer, the absolute path to the response file and specify the appropriate JVM:

java -classpath installer.jar install -f <absolute path to response file>

For example:

[root@qaserver:/] /usr/java/bin/java –classpath introscope9.0.x.yos400.jar

install –f /tmp/myResponseFile.txt

Note: The above path should be all one line. Ignore the line break.

About silent mode errors

If the response file specified does not exist or the path is invalid, the installer tries to run in GUI mode. However, if GUI mode is not supported on the platform, the installer fails.

Note: If the silent install or upgrade fails, you can check Introscope_9.0_InstallLog.log in the <EM_Home>/install directory, but on occasions where the install or upgrade fails before the process creates the log file, no feedback will be available.


Chapter 7: Installing Introscope PowerPacks and extensions

This chapter contains instructions for using the standalone PowerPack installer in GUI mode, and information related to the other extensions installed with Introscope.

For information about the installers, and to verify that GUI mode installation is supported in your environment, see Preparing for install or upgrade (see page 25).

Note: If you are upgrading an existing PowerPack or extension, see Upgrading PowerPacks and extensions (see page 232).


About the PowerPacks and extensions (see page 122) Installing a standalone PowerPack (see page 127)

About the PowerPacks and extensions


About the PowerPacks and extensions ■ Completely installing a PowerPack involves multiple installers. All PowerPacks have

files installed by the main installer related to the Enterprise Manager. In addition, PowerPacks have files installed by the standalone PowerPack installer and/or agent installer.

■ The main installer creates a separate directory for each PowerPack in the <EM_Home>\examples directory. Within each PowerPack’s directory are the files needed to install and configure the PowerPack. To enable and use a PowerPack, you must perform additional configurations and possible installations.

■ Introscope installs LeakHunter and ErrorDetector automatically. For details on enabling or configuring these extensions, see the Introscope Java Agent Guide and the Introscope .NET Agent Guide.

■ Introscope installs SNMP Adapter automatically. For details on enabling or configuring this extension, see the Introscope Configuration and Administration Guide and the Introscope Workstation User Guide.

■ Users need to know which operating systems are valid for the PowerPacks to install on.

■ The main installer, agent installer, and standalone PowerPack installer install the PowerPack documentation.

Note: This is not a complete list of available PowerPacks. For additional information, please contact your CA Wily account representative or call 1-800-225-5224.

The following table lists PowerPacks and extensions, where they get installed, and the documentation location.

PowerPack or extension

How/where installed Product documentation (in <EM_Home>\docs\ if not otherwise indicated)

PowerPack for WebSphere Portal

Enterprise Manager,

agent

wyisc_websphere_portal.pdf

PowerPack for WebLogic Portal

Enterprise Manager,

agent

wyisc_powerpack_for_weblogic_portal.pdf

PowerPack for SharePoint Portal

Enterprise Manager,

agent

wyisc_powerpack_for_sharepoint_portal.pdf

SP Monitor for SharePoint Portal

Enterprise Manager,

Standalone

wyisc_powerpack_for_sharepoint_portal.pdf

SOA Extension for webMethods Integration Server

Enterprise Manager,

agent

wyisc_soa_performance_management_guide.pdf





SOA Extension for TIBCO BusinessWorks

Enterprise Manager,

agent


SOA Extension for Oracle Service Bus

Enterprise Manager,

agent


SOA Extension for WebSphere Process Server / WebSphere Enterprise Bus

Enterprise Manager,

agent


SOA Extension for TIBCO Enterprise Message Service

Standalone wyisc_soa_performance_management_guide.pdf

SOA Extension for webMethods Broker

Standalone wyisc_soa_performance_management_guide.pdf

PowerPack for WebSphere MQ Connectors and Messaging System

Enterprise Manager, agent, Standalone

wyisc_ibm_websphere_mq_connectors_messaging_system.pdf

PowerPack for WebServers

Enterprise Manager,

Standalone

wyisc_powerpack_for_web_servers.pdf

PowerPack for WebLogic Server

Enterprise Manager,

agent

wyisc_powerpack_for_weblogic_server.pdf

PowerPack for SiteMinder

Enterprise Manager,

agent

wyisc_powerpack_for_siteminder.pdf

SNMP Collector for SiteMinder

Enterprise Manager,

Standalone

wyisc_powerpack_siteminder_snmp_collector.pdf

PowerPack for Oracle DB

Enterprise Manager,

Standalone

wyisc_powerpack_for_oracle_database.pdf

PowerPack for WebSphere - Distributed

Enterprise Manager,

agent

wyisc_powerpack_for_ibm_websphere_distributed.pdf

LeakHunter Enterprise Manager

agent

wyisc_java_agent_guide.pdf and wyisc_net_agent_guide.pdf

ErrorDetector Enterprise Manager wyisc_java_agent_guide.pdf and wyisc_net_agent_guide.pdf





ChangeDetector Enterprise Manager,

agent,

Workstation

wyisc_change_detector.pdf

SNMP Adapter Enterprise Manager wyisc_introscope_configuration_administration_guide.pdf and wyisc_workstation_user_guide.pdf

SYSVIEW Enterprise Manager,

agent

wyisc_sysview_integration.pdf

LeakHunter installation

When installing the Enterprise Manager, the installer automatically installs the following files for LeakHunter:

<EM_Home>\config\systempbd\LeakHunter.pbd

LeakHunter also has files that the agent installer installs. For details, see the Introscope Java Agent Guide and the Introscope .NET Agent Guide.

ErrorDetector installation

When installing the Enterprise Manager, the installer automatically installs the following files for ErrorDetector:

<EM_Home>\product\enterprisemanager\plugins\

com.wily.introscope.errordetector_9.0.0.jar

The agent installers also install additional files related to ErrorDetector. For additional information about ErrorDetector, see the Introscope Java Agent Guide and the Introscope .NET Agent Guide.



ChangeDetector installation

When installing the Enterprise Manager, the installer automatically installs the following files for ChangeDetector:

<EM_Home>\products\enterprisemanager\plugins\com.wily.cd.*.jar

<EM_Home>\config\modules\ChangeDetectorManagementModule.jar

When installing the Workstation, the installer automatically installs the following directory containing files for ChangeDetector:

<WS_Home>\tools\ChangeDetectorWizard.jar

<WS_Home>\tools\configwizard.bat

The agent installers also install additional files related to ChangeDetector. For details, see the Introscope Java Agent Guide and the Introscope .NET Agent Guide.

For additional information about ChangeDetector, see the Introscope ChangeDetector User Guide.

SNMP Adapter installation

When installing the Enterprise Manager, the installer automatically installs the following file for SNMP Adapter:

<EM_Home>\product\enterprisemanager\plugins\

com.wily.introscope.em.snmp_9.0.0.jar

For additional information about SNMP Adapter, see the Introscope Configuration and Administration Guide and Introscope Workstation User Guide.

SYSVIEW installation

When installing the Enterprise Manager, the installer automatically installs files for SYSVIEW in the <EM_Home>\examples\SYSVIEWExtension directory.

Introscope also installs SYSVIEW files in the Java Agent installer.

Introscope installs the files but does not automatically enable SYSVIEW. For additional information about installing and configuring SYSVIEW, see the CA Wily Introscope Extension for CA SYSVIEW Guide.



CA Wily APM Web Services APIs

Introscope provides the CA Wily APM Web Services APIs so you can use third-party applications to use Introscope as a source for alerts and metrics.

When installing the Enterprise Manager, the installer automatically installs the following files for CA Wily APM Web Services APIs in the <EM_Home>\product\enterprisemanager\plugins directory:

com.wily.introscope.alerts.extension_9.0.0.jar

com.wily.apm.webservices_9.0.0.jar

com.wily.apm.tess_9.0.0.jar

To learn what’s available with these web services, view the Web Services Description Language files (WSDL).

To view the web services description files:

1. Open the following WSDLs in a web browser to expose the Introscope web services:

http://host:port/introscope-web-services/services/AlertPollingService?wsdl

http://host:port/introscope-web-services/services/MetricsDataService?wsdl

http://host:port/introscope-web-services/services/MetricsListService?wsdl

http://host:port/introscope-web-services/services/EmLifecycleService?wsdl

Replace host and port with the correct machine name where you have installed the Enterprise Manager and the correct web server port for the Enterprise Manager.

2. Open the following WSDLs in a web browser to expose the Wily CEM web services (replacing host and port with the correct values):

http://host:port/wily/cem/webservices/ConfigurationDataOutService?wsdl

http://host:port/wily/cem/webservices/BizImpactDataOutService?wsdl

http://host:port/wily/cem/webservices/EventsDataOutService?wsdl

http://host:port/wily/cem/webservices/StatisticsDataOutService?wsdl

3. When you are prompted, enter the valid username and password in the authentication dialog.

If local realm authorization is used, then any administrator user or any user that belongs to a defined administrator group has access to web services. Group membership is defined in users.xml. For more details about security, see the CA Wily APM Security Guide.

If CA EEM authorization is used, any user who has the "Allow" privilege to the "WebService" resource class has access to web services. This is typically administrator users. Group membership is not relevant in CA EEM authorization. For further details, consult the CA EEM documentation.

After you are logged in, the browser displays the WSDL.

Installing a standalone PowerPack



The standalone PowerPack installer installs files needed by the following PowerPacks:

■ PowerPack for Oracle Database

■ SNMP Collector for SiteMinder

■ SOA Extension for TIBCO Enterprise Message Service

■ SOA Extension for webMethods Broker

■ PowerPack for Web Servers (with the option to install files for IIS)

■ SPMonitor for SharePoint Portal

■ PowerPack for WebSphere MQ Connectors and Messaging System

For each PowerPack, you need to do post-install configuration. For details, refer to the user guide for the specific PowerPack.

Note: The above list does not represent all available Introscope PowerPacks. Some PowerPacks are installed by the agent installers. Some PowerPacks have components installed by both the standalone PowerPack installer and the agent installer. All PowerPacks have files installed by the main, Enterprise Manager installer.

To install a standalone PowerPack:

1. Be sure that the appropriate JVM is specified in your PATH (UNIX) or CLASSPATH (Windows) environment variable. In order to run the installer, a JVM must be installed and specified in the system environment. For JVM version requirements for an installer, see Running an installer with an alternate JVM.

2. Start the standalone PowerPack installer (see Selecting the correct PowerPack installer).

The Introduction window opens.

3. Click Next.

4. In the Choose Install Set window, select the desired PowerPack(s) to install, and click Next to continue.

5. In the Choose Install Folder window, you can click Next to accept the default installation directory, or click Browse to specify a different location.

Default directories:

■ Windows: C:\Program Files\CA Wily\Introscope9.0\

■ UNIX: /root/Introscope9.0.0

6. If you selected the PowerPack for Web Servers, the PowerPack for Web Server IIS window opens. Select PowerPack for Web Server IIS if you want to install the PowerPack files for IIS. Click Next to continue.



7. In the Enterprise Manager Connection Settings window, specify the Enterprise Manager Host address and Enterprise Manager Port number. Click Next to continue.

8. In the Pre-Installation Summary window, review the summary of your PowerPack settings. Click Next to continue the installation, or go back and make corrections if necessary.


Chapter 8: Installing Wily CEM

This chapter contains information about installing a new TIM, the main monitoring component of Wily CEM.

If you are upgrading a Wily CEM installation, see Upgrading to CA Wily APM 9.x (see page 149) and Upgrading Wily CEM components (see page 187).


Installing and configuring a TIM (see page 129) Accessing the Wily CEM console and setup pages (see page 142) Verifying Wily CEM configurations (see page 145) Shutting down and restarting a TIM (see page 147) Uninstalling a TIM (see page 148)

Installing and configuring a TIM

Installing a new TIM software appliance includes installing a new operating system plus the TIM software, configuring the TIM’s network connectivity, and enabling the TIM to communicate with the Enterprise Manager. Below is an overview of the install process.

To install a new TIM software appliance (an overview):

1. Ensure that the machine has a DVD drive. For system requirements, see About Wily CEM TIM requirements and recommendations (see page 36).

2. Install the operating system from the TIM kickstart DVD. For details, see Installing the operating system for a new TIM (kickstart DVD) (see page 130).

3. Change the current time zone, if needed. For details, see Setting the time zone on a TIM (see page 137).

4. Configure and verify the TIM’s network management settings so that the TIM can access the network appropriately. For details, see Configuring the TIM network management settings (see page 133).

5. Install the TIM software. For details, see Installing TIM software (see page 135).

Note: If you do not want to install the TIM software from the network, you can do step 5 before step 4.

6. Configure the TIM network monitoring. For details, see Configuring the TIM network monitor interface (see page 138).



7. Add the TIMs to enable them on the Enterprise Manager. For details, see Adding and enabling the TIMs (see page 139).

8. Verify the TIM configuration after installation. For details, see Verifying Wily CEM configurations (see page 145).


Installing the operating system for a new TIM (kickstart DVD) (see page 130) Configuring the TIM network management settings (see page 133) Installing TIM software (see page 135) Setting the time zone on a TIM (see page 137) Configuring the TIM network monitor interface (see page 138) Wily CEM post-install configuration on the Enterprise Manager (see page 139)

Installing the operating system for a new TIM (kickstart DVD)

Use the kickstart DVD to automatically install Red Hat Enterprise Linux 4 (32-bit).

IMPORTANT! When installing a new TIM, you must use the kickstart DVD provided by CA Wily to install the operating system. Do not use other operating system installation media.



To install the operating system software required by the TIM:

1. Insert the DVD disk into the drive, and boot the machine. The machine boots from the DVD.

2. On the opening screen, press Enter to select Auto-Install.

WARNING: Installing the TIM operating system software partitions the first drive, formats it, and automatically installs Linux. Any data on the drive is deleted.



The DVD installs the operating system files and partitions the first hard disk drive automatically.

During installation, a screen displays a summary of the installation progress.

After the installation completes, the machine reboots automatically and ejects the DVD.

3. The EULA (end user license agreement) displays for Red Hat Linux. You must accept the license agreement and click Next to continue.

The installer installs and configures the TIM web server. This allows you to install the later software using a web browser.

The installer also collects basic information about the machine, such as CPU, memory, disk size, and network ports, to verify that the machine meets the minimum system requirements.

If the machine does not pass system requirement verification, the installer writes the test results to a plain text file and opens the text file in a web browser. The test results indicate what system requirement tests failed.

If the machine passes the system requirement check, the Setup Date/Time screen displays. By default, the time is set to the Eastern time zone. You can change the time zone later, if desired.

4. Change the date and time, if desired, and click Next to continue.

5. In the Setup Display screen, change the display details for the monitor, if desired. Click Next to continue.

6. In the Finish Setup screen, click Next to finish the initial machine setup.

The Red Hat Linux login screen opens. The operating system installation is complete.

7. Enter the username of "root", and password of "quality."

The Red Hat Linux desktop opens.



The desktop icons provide convenient access to common post-install configuration tasks, such as setting the time zone, configuring the IP address, and installing the TIM software. The Post-Install notes include a brief overview of the post-install tasks.

Next, configure the date, time, and time zone for the machine. Use the Date/Time shortcut to configure the date and time.

Configuring the TIM network management settings

After installing the TIM operating system software you configure the TIM’s IP address and other network settings. You need to configure the network interface for each TIM.

By default, the TIM software is configured to use DHCP assignment of IP addresses on the management port (eth0). It is possible to use dynamically assigned IP addressing in short term or testing environments. However, for production use, you must set a static IP address.

When the IP address of a TIM changes, the Enterprise Manager is not able to communicate or receive data from the TIM.

You can configure the network settings either from the Network shortcut, or by editing the system configuration’s network files. To prevent syntax errors, the Network shortcut is recommended.



Note: However, if you prefer, you can edit the system’s network configuration file:

/etc/sysconfig/network-scripts/ifcfg-eth0

Setting the hostname and domain name for each machine is an optional practice. A hostname is required for some integrations, to use SMTP and SNMP protocols, and in some security environments.

Tip: Make sure to use a fully qualified domain name for the hostname, or appropriately edit the /etc/hosts file.

To configure the TIM network management settings using the Network desktop shortcut:

1. On the Red Hat Linux desktop, double-click Network.

2. In the Network Settings screen, change the following settings:

■ hostname

■ eth0 IP address from DHCP to Static (highly recommended)

■ subnet mask

■ Default Gateway

■ DNS Server 1

■ DNS Server 2

■ domain

The eth0 is the management port that the Enterprise Manager uses to communicate with the TIM software appliance.

3. Click File > Save.

The system prompts you to restart the machine. You must restart to apply the changes to the network settings.

4. Click Actions > Log Out. Linux displays a log out verification dialog.

5. Select Restart the computer and click OK.

The machine reboots. Log in again with the username (root) and the default password (quality).

6. After you have configured the network management interface with the correct IP address, ensure that you have network connectivity to and from this IP address. The network connectivity allows you to connect remotely to the TIM machine from a web browser.

To ensure the HTTP server is running on the TIM machine, run the following command:

ps -ef|grep httpd



Installing TIM software

After you’ve installed the operating system software for the TIM software appliance, you must install three software components in the following order:

1. APM_INSTUPD<version>.img

2. APMThirdPart<version>.img

3. APM_TIM5000_<version>.img

These software images are provided to you on the DVD’s in the TIM software appliance DVD bundle. Either mount these DVDs onto your network, or navigate to the files directly from the TIM machine.

Use the Wily System Setup page (available from the desktop icon) to install the TIM software. Alternatively, connect a monitor to the TIM machine and use the Lynx browser to install the files. For Lynx information, see Using the Lynx text browser on a TIM (see page 273).

To install the TIM software image files from the Wily System Setup page:

1. Ensure the TIM is connected to the network, and the TIM’s HTTP server is running. For details, see Configuring the TIM network monitor interface (see page 138).

2. On the desktop, double-click the Wily System Setup icon to open the Wily System Setup page. Open the file either from a remote client or directly on the machine. If using a remote client, enter the IP address.

3. In the login prompt dialog, enter the following credentials and click Login:

username=admin

password=quality

The Wily System Setup Page opens.

4. Click Install New Software.

5. In the Install Software page, click Browse to navigate to and select the APM_INSTUPD<version>.img file.



6. Click Upload and Install.

The software installation log appears. If you see errors in the log, contact CA Support. Errors are displayed in red text.

7. Click Install Another Product.

8. In the Install Software page, click Browse to navigate to and select the APMThirdPart<version>.img file.


10. For the third party software, you must accept the EULA before continuing. Read the agreement, then at the bottom of the page, select the option ‘I accept the terms of the License Agreement,’ and click Next.


11. Click Install Another Product.

12. In the Install Software page, click Browse to navigate to and select the APM_TIM5000_<version>.img file.


14. For the TIM software, you must accept the EULA before continuing. Read the agreement, then at the bottom of the page, select the option ‘I accept the terms of the License Agreement,’ and click Next.


15. At the bottom of the page, click Return to Setup. The setup page should look like the following:



Setting the time zone on a TIM

When you first install a TIM, you may need to specify the time zone. The default is America/New York.

The instructions below cover how to change the time zone from the Wily System Setup Page.

Alternatively, you can use the Date & Time desktop shortcut to change the time zone, in addition to the machine date and time.

Note: Statistics and aggregation are based on the Enterprise Manager time zone. For more information, see About CA Wily APM time settings (see page 53).

IMPORTANT! You should set the time zone only once and only before gathering any transaction statistics on the Wily CEM system.

WARNING: Use caution when changing the CA Wily APM system time or time zone. Set the time zone on the TIM only when instructed to do so by CA Support. Changing the time or time zone can affect Introscope and Wily CEM system functions including:

■ The Enterprise Manager automatically reboots after a time or time zone change.

■ Setting the time forward might result in gaps in the aggregation statistics.

■ Setting the time backward might result in corruption and/or duplicate aggregation statistics.

■ The Enterprise Manager synchronizes a time change with the TIMs when you change it, and 1:05 a.m. daily.

■ The Enterprise Manager does not propagate the time zone to the TIMs.

■ Changing the time or time zone in the middle of an aggregation process might result in corrupted aggregation statistics.

To set the time zone on a TIM:

1. Review the warnings listed above before proceeding to the next step.

2. On the desktop, double-click the Wily System Setup icon to open the Wily System Setup page. Open the file either from a remote client or directly on the machine. If using a remote client, enter the IP address.

3. In the login prompt dialog, enter the following credentials and click Login:

username=admin

password=quality

The Wily System Setup Page opens.

4. Select Machine Settings.



5. Select Set Time Zone.

The current time zone setting appears, with a list of alternative time zones below it.

6. Select the time zone where you will deploy this TIM.

Configuring the TIM network monitor interface

After the TIM software is installed, you must configure the TIM so that it can monitor the network traffic and communicate with the Enterprise Manager.

The network monitor interface determines which ports TIM monitors traffic on. Use eth1 for copper. Use eth2 and/or eth3 for fiber. Do not set the monitoring port to eth0 because that is the management port. (If you have upgraded a TIM, you can disregard this section.)

To set up the TIM network monitor interface:

1. From a web browser on any network computer, access the TIM Wily System Setup page. For details, see Accessing the Wily System Setup page for the TIM (see page 144).

2. Select TIM > Configure TIM Network Interfaces.

The TIM network interfaces page appears.

3. If necessary, clear the eth0 (management port) check box, and select the (monitoring port) check box.

■ If the TIM traffic monitoring cable is connected to eth1 port (copper cable connected to a switch), check eth1.

■ If the TIM traffic monitoring cable is connected to eth2 port (fiber cable connected to a network tap), check eth2.

■ If your tap supports only half-duplex and you require dual fiber cards to achieve full-duplex, then you need to check eth2 and eth3 for the TIM traffic monitoring.

Note: Select monitoring ports only for those ports that you will be receiving a network monitoring feed on.

4. Click Set.

5. Repeat this procedure for each TIM machine.

After you finish configuring the TIMs, you are ready to perform the Wily CEM configurations on the Enterprise Manager. For details, see Wily CEM post-install configuration on the Enterprise Manager (see page 139).



Wily CEM post-install configuration on the Enterprise Manager

After you have installed the TIM, there are some configuration tasks to do on the Enterprise Manager so that the TIMs and the Enterprise Manager communicate with each other.


Adding and enabling the TIMs (see page 139) Configuring TIM monitoring (see page 140)

Adding and enabling the TIMs

You need to make sure to enable the TIMs so that the TIMs can monitor transactions. The Enterprise Manager does not receive data from disabled TIM monitors. If you have clustered Enterprise Managers, you enable the TIMs from the MOM Enterprise Manager.

These are some examples of when you need to enable TIMs:

■ When setting up a TIM and associating it with an Enterprise Manager.

■ After upgrading the TIMs and/or Enterprise Manager.

■ After a configuration is imported. (See the Wily CEM Configuration and Administration Guide.)

To add the TIM and enable TIM communication with an Enterprise Manager:

1. Open a web browser and enter address of the machine that hosts the Enterprise Manager. If using a clustered environment, specify the address of the MOM:


where <IP_Address> is the IP address or DNS name for the MOM or a standalone Enterprise Manager. For example:

http://192.168.1.54:8081/wily

http://cem.company.com:8081/wily

To use a DNS name, your DNS administrator must have configured it.

Note: The default port is 8081. It is defined in the IntroscopeEnterpriseManager.properties file as introscope.enterprisemanager.webserver.port=8081 and can be changed.

2. Enter the user name and password.

The default user name for the Wily CEM administrator is cemadmin, and the default password is quality.

The Wily CEM console appears.For information about security and logins, see the CA Wily APM Security Guide.

3. Select Setup > Monitors.



4. If the TIM does not appear in the list, to add it:

a. Click New.

b. Enter the name and IP address of the TIM, and click Save.

5. Select the check box next to each required TIM and click Enable.

Communication between the Enterprise Manager and the TIMs is then enabled. You may notice additional tabs now display in the Wily CEM Console.

Configuring TIM monitoring

After you have installed a TIM and you have multiple TIMs, you can configure each TIM to monitor specific network traffic and load balance the traffic among the TIMs. (If you have upgraded a TIM, you can disregard this section.)

Note: If you do not configure the TIMs correctly, network packets might not be monitored as needed. If you do not configure the TIM web server filters, then all IP addresses will be monitored by the TIM. If a TIM gets overloaded, recording might not work. If you have more than one TIM monitoring the same servers, transactions will be monitored twice.

Follow the steps to assign each TIM to the portion of the network that it must monitor.

To configure TIM monitoring:

1. Open the Wily CEM console. For details, see Accessing the Wily CEM console (see page 142).

2. Select Setup > Web Server Filters.



3. Click New.

4. Type a Name that describes the network portion for TIM monitoring. For example, WebFarmCorp1.

5. In the Monitor list, select the TIM that will monitor this portion of the network.

Each TIM monitors an IP address range by default. If you want to monitor via a specific MAC address instead, go to step 6.

a. From IP Address — type the IP address of the web server at the low end of the range (or the specific IP address if there is only one server to monitor).

b. To IP Address — type the IP address of the web server at the high end of the range (or the specific IP address if there is only one server to monitor).

c. Port

■ If the TIM should monitor transactions only on a specific port, type the port number.

■ If the TIM should monitor all transactions on all ports, type 0 (the default).

d. In most cases, TIMs should monitor specific servers in the network rather than overlapping. However, in special circumstances, you might want to allow overlapping IP addresses.

If you want to configure more than one monitor for an IP address or range, select the Save without checking for overlapping IP Addresses check box.

6. If you want to monitor a specific MAC address instead of by IP address range:

a. Click the Address Type of MAC Address.

b. Type the specific MAC Address of the device you want to monitor. For example: 12:eb:a0:32:51:4c.

7. Click Save to configure the TIM monitor as specified.

Accessing the Wily CEM console and setup pages



After you have completed the initial installation, you can set up and administer Wily CEM from any computer that has a web browser.

Before trying to access the Wily CEM console, ensure that the Enterprise Manager is running.

Accessing the Wily CEM console

You can set up and administer business applications, business services, and transaction definitions from any computer that has a web browser.

The Wily CEM console is the main user interface of Wily CEM. Administrators use it to set up and configure Wily CEM, including transaction recording and creating transaction definitions. Analysts use it to produce and view reports.

If you are an administrator, the Wily CEM console looks like this:

(If no TIMs are enabled, the Tools and CEM links do not appear.)

Unless otherwise indicated, this guide assumes that you are using the Wily CEM console as an administrator.



In a clustered environment, the Wily CEM console is on the Manager of Managers (MOM).

To access the Wily CEM console:

1. Open a web browser and type the address:


where <IP_Address> is the IP address or DNS name for the MOM or a standalone Enterprise Manager. For example:

http://192.168.1.54:8081/wily

http://cem.company.com:8081/wily


Note: The default port is 8081. It is defined in the IntroscopeEnterpriseManager.properties file as introscope.enterprisemanager.webserver.port=8081 and can be changed.


The default user name for the CEM administrator is cemadmin.

The Wily CEM console appears.

For information about security and logins, see the CA Wily APM Security Guide.

Note: If you are re-using a 4.5.x TESS appliance, be sure to enter the URL for CA Wily APM 9.x Wily CEM console correctly, including the port address. If you have not yet uninstalled the 4.5.x TESS software, the old 4.5.x console URL may still be available.



Accessing the Wily System Setup page for the TIM

The Wily System Setup page for the TIM provides access to various configuration and status pages. Wily CEM administrators rarely use these pages, typically to check status information or for troubleshooting.

To access the Wily System Setup page for a TIM:

1. Open a web browser and enter the address:

http://<IP_Address>/wily/system

where <IP_Address> is the TIM IP address or DNS name.

For example:

http://192.168.1.54/wily/system

http://cem.company.com/wily/system



The default user name for the Wily System Setup page is admin.

The Wily System Setup page appears.

Troubleshooting login to Wily CEM

Symptom:

If you are unable to log in to Wily CEM, verify that Active Scripting is enabled on your browser.

If Active Scripting is disabled, when you click Log In on the Wily CEM login page, you are redirected to a CEM Console / Back page. This happens even when your User Name and Password have been entered correctly.

Verifying Wily CEM configurations


Solution:

To enable Active Scripting, see the user documentation for your browser. For example, in Internet Explorer 8, the setting is under Internet Options > Security > Custom level > Scripting > Active scripting.

Accessing the TIM from the Wily CEM console

If you know the IP address and path for the TIM, you can access the TIM System Setup page from the Wily System Setup page. However, if you have the Wily CEM console open, you can access the TIM System Setup page from the console.

To access the TIM System Setup page from the Wily CEM console:

1. In the administrator console, select Setup > Monitors.

2. Click the IP address of the TIM (far right column).


The default user name for the System Setup page is admin.

The TIM System Setup page appears.


After you have installed or upgraded a TIM, it’s a good practice to verify that the TIM and the connection between the TIM and the Enterprise Manager are set up correctly.



Verifying TIM configuration

Confirm the settings on your Wily CEM system TIM. The table below lists the TIM settings and how to verify them.

This TIM Setting … Can be Verified …

TIM:

DHCP or IP Address

Subnet Mask

Default Gateway

DNS Server 1

DNS Server 2

On the TIM:

Wily System Setup > Machine Settings > Network Setup > select the interface you want to verify and click Set.

or, if your network is IPv6,

Wily System Setup > Machine Settings > Configure IPv6 > select the interface you want to verify and click Set.

Time zone

Be sure that the TIM time zone is correct.

For more information on time settings, see Setting the time zone on a TIM (see page 137) and the Wily CEM Configuration and Administration Guide.

TIM network interface to monitor

On the TIM:

Wily System Setup > TIM System Setup > Configure TIM Network Interfaces

For more information, see Configuring the TIM network monitor interface (see page 138).

Verifying communication between the TIM and Enterprise Manager

Before you can view Wily CEM reports and statistics, you must ensure that the Enterprise Manager is communicating with the TIMs.

To verify communication between the TIM and Enterprise Manager:

1. Open the Wily CEM console. For details, see Accessing the Wily CEM console (see page 142).

2. Select Setup > Monitors, and ensure that the TIMs are enabled.

3. Check for error conditions.

The Monitors page shows two columns: Domain Configuration Status and Monitor Configuration Status. Both columns should show successful states for all enabled Monitors.

If there are any communication errors, these columns will display a failure or an HTTP error code. To see details, click on the link of the monitor that failed.

Shutting down and restarting a TIM


4. If you get an error message, be sure that:

■ the Enterprise Manager is running (refresh the browser).

■ all TIMs have the correct IP addresses.

■ all TIMs are running.

■ all TIM are accessible—select System > Events and look for communications errors.

■ all cables providing physical connections between the computers are securely in place.

For more information on system events and possible communications errors between the Enterprise Manager and TIM, see the Wily CEM Configuration and Administration Guide.

Shutting down and restarting a TIM

Occasionally, you may need to shut down or restart a TIM. For example, you must shut down a TIM before upgrading it.

You may also want to shut down or restart a TIM if you want to stop monitoring a particular application that the TIM is monitoring, or if the TIM has excessive memory usage from an incorrectly written plug-in that caused some processes to make the TIM unresponsive.

To shutdown or restart a TIM:

1. On the TIM: Access the Wily System Setup page. For details, see Accessing the Wily System Setup page for the TIM (see page 144) .

2. Select Machine Settings > System Shutdown/Restart.

Uninstalling a TIM


Uninstalling a TIM

Before you uninstall the TIM software, you must first:

■ Ensure no other machine is accessing the TIM machine.

■ Disable all monitors.

■ Stop the TIM.

To uninstall the TIM software:

1. On the TIM machine, navigate to the following directory:

cd /etc/wily/cem/tim/install

2. In this directory, run the following command:

sh uninstall

3. Navigate to the following directory:

cd /etc/wily/third-party/install

4. In this directory, run the following command:

sh uninstall


Chapter 9: Upgrading to CA Wily APM 9.x

This chapter contains information related to upgrading any Introscope, Wily CEM, or CA Wily APM installations, including preparatory steps, upgrade workflows, and checklists.


Determining the current and target environments (see page 149) Determining the upgrade path (see page 150) Preparing for all upgrades (see page 152) Preparing for Introscope-related upgrades (see page 153) Preparing for Wily CEM-related upgrades (see page 158) Upgrading from Introscope (see page 160) Upgrading from CA Wily APM (see page 173) Upgrading from Wily CEM (see page 179)

Determining the current and target environments Depending on your current environment and how you have deployed Introscope or Wily CEM, the upgrade process varies. So, before reviewing the steps involved in upgrading, determine the characteristics of your current environment and upgrade goal. The table below lists the possible current and target installations.

Current installation Target installation

Introscope only Introscope only (CA Wily APM without TIMs)

Introscope only CA Wily APM

CA Wily APM Introscope and Wily CEM

(integrated)

CA Wily APM

CA Wily APM Introscope and Wily CEM (non-integrated)

CA Wily APM

Wily CEM only Wily CEM only (CA Wily APM without agents)

Wily CEM only CA Wily APM

Determining the upgrade path



This section provides key information for you to consider when determining how you plan to upgrade your existing deployment.

Review the system requirements in this guide and also consult the CA Wily APM Overview Guide, the CA Wily APM Security Guide, the CA Wily APM Sizing and Performance Guide, and the CA Wily APM Compatibility Guide (available from CA Support). Once you understand the system requirements, you can identify and plan your deployment.

Answers to the following questions are the major factors that determine the steps you follow to upgrade your environment:

■ If upgrading Introscope or CA Wily APM, will you be upgrading a standalone Enterprise Manager or a clustered environment?

■ If upgrading CA Wily APM, do you plan to upgrade one product at a time, or all products at the same time?

■ Will you need more hardware?

■ Will you continue to use the existing machines?

■ Will you upgrade on the existing machines, or move to additional machines?

■ Will you be using CA EEM security?

Once you determine the answers to the above questions, you are ready to plan your upgrade deployment.

Pros and cons of upgrading products one at a time

If you upgrade Introscope components first and then upgrade Wily CEM components, it can be easier to diagnose any conflicts or errors. This method also minimizes production down-time.

The disadvantage of using this approach is that there will be a time lag in the database, and you later must integrate two databases.

You should upgrade Enterprise Managers before upgrading agents. If you have a large number of agents, you can schedule their upgrades over time.



Pros and cons of upgrading products at the same time

Tip: CA Technologies recommends upgrading both products at the same time, to avoid potential time lag and data merge issues.

If you upgrade both products at the same time, you do not have to handle merging databases and managing the data integrity as much.

The disadvantage of upgrading both products at the same time is that it takes more time to complete the upgrade. There is also more potential for errors in more places, and you need additional time to diagnose the cause of the errors.

If you are upgrading a production system, there is also impact to have the production systems not operating for a longer amount of time.

Summary of upgrade paths

The table below lists the upgrade checklists to follow for each upgrade path. For any upgrade, first go to Preparing for all upgrades (see page 152).

Current installation Target installation Where to go


Preparing for Introscope-related upgrades (see page 153)

Upgrading from Introscope (see page 160)

Introscope only CA Wily APM Preparing for Introscope-related upgrades (see page 153)


APM (Introscope and Wily CEM integrated)

CA Wily APM Preparing for Introscope-related upgrades (see page 153)

Preparing for Wily CEM-related upgrades (see page 158)

Upgrading from CA Wily APM (see page 173)

APM Introscope and Wily CEM (non-integrated)

CA Wily APM Preparing for Introscope-related upgrades (see page 153)


Upgrading from CA Wily APM (see page 173)

or, for continued non-integration,


Upgrading from Wily CEM (see page 179)

Preparing for all upgrades


Current installation Target installation Where to go

Wily CEM only CA Wily APM Preparing for Wily CEM-related upgrades (see page 158)





Preparing for all upgrades

Before you begin an upgrade, regardless of the product you are upgrading from or to, there is some pre-work to do to ensure an upgrade that is as error-free as possible.

To prepare for any upgrade:

1. Back up all data from your current Introscope and/or Wily CEM installation, as a precaution. If at any point in the upgrade process you realize you have gone down the wrong path or performed too many tasks incorrectly, you can start over by restoring from a backup. For more information, see the Introscope Configuration and Administration Guide and the Wily CEM Configuration and Administration Guide.'

2. Before you do any upgrade-specific tasks, review and understand the upgrade process and requirements. Be sure that your environment meets or exceeds both the upgrade and system requirements.

For Introscope, be prepared that the installers will upgrade many components automatically, and there may be pieces that you must manually upgrade.

For Wily CEM, there are some post-upgrade tasks to do, such as making sure you specify plug-in configuration information correctly.

Note: After you have upgraded, you may find at some point that you need to move the APM database to another machine for scalability reasons. For details, see Moving the APM database to a different machine (see page 209).

In particular, see the following sections:

■ Preparing for Introscope-related upgrades (see page 153)

■ Preparing for Wily CEM-related upgrades (see page 158)

■ Preparing for install or upgrade (see page 25)

Preparing for Introscope-related upgrades


Preparing for Introscope-related upgrades This section pertains to those of you who are upgrading either Introscope-only installations or CA Wily APM. The table below lists the current and target installations that this section covers.




CA Wily APM Introscope and Wily CEM (integrated)

CA Wily APM


CA Wily APM

When preparing to upgrade your existing Introscope installation, whether upgrading to Introscope or all of CA Wily APM functionality, there are some details to be aware of before you begin that affect the process by which you upgrade.

This section covers the main points to be aware of, Enterprise Manager and agent version compatibility, which components may need manual upgrades, and what tasks you need to do just before you begin the upgrade.

Main points to be aware of when upgrading Introscope

The main difference between the current Introscope and previous versions is the addition of the APM database.

When you upgrade a standalone Enterprise Manager or a MOM, you install a new APM database. When you upgrade a Collector, you specify the connection details so that it connects to the new database.

Also, be aware that you may need to manually upgrade some Introscope components. For details, see Introscope automatic and manual upgrade information (see page 155) and Manually upgrading Introscope (see page 253).



Introscope component version compatibility

These rules govern version compatibility among Introscope components:

■ The Enterprise Manager and the Workstation must be the same version.

When you upgrade Enterprise Manager, you install a new Workstation of the same version. This includes upgrades to service pack or patch releases.

■ All Enterprise Managers in a cluster must be the same version. This includes the MOM and all Collector Enterprise Managers.

■ Agents, AutoProbe or ProbeBuilder, and the Platform Monitor must all be the same version. If you upgrade agents, you must also upgrade AutoProbe or ProbeBuilder, and Platform Monitors.

■ Agents can be either the same version as, or an earlier version than, the Enterprise Manager (EM). For example, the table below lists which agent versions work with which Enterprise Manager versions:

7.0 Enterprise Manager?

8.x Enterprise Manager?

9.x Enterprise Manager?

7.0 agent works with... Yes Yes Yes

7.2 agent works with... Yes Yes Yes

8.x agent works with... No Yes Yes

9.x agent works with... No No Yes

Note: There may be some loss of functionality if your agent is an earlier version than your Enterprise Manager.

Upgrading agents when you upgrade Enterprise Managers and install new Workstations is recommended, but not required. In some environments, upgrading all agents at the same time as the Enterprise Manager and Workstation is impractical because it requires restarting each application server.

You can update agents in one of two ways:

■ Continue to run the previous version of the agent until you can schedule upgrade of all agents at the same time.

■ Upgrade your agents gradually.



Introscope automatic and manual upgrade information

To upgrade to this Introscope release from an earlier version, you must upgrade each Introscope component in your environment. You can upgrade most components automatically, and some you must upgrade manually.

When using the installer to automatically upgrade Introscope, you can run the installer in GUI, console, or silent mode.

You can use the Introscope installers to automatically upgrade the following:

■ Enterprise Managers (except for some z/OS systems)

■ WebView, ProbeBuilder, and EPAgent components, if they were originally installed with the Enterprise Manager.

■ Web Start Workstations automatically upgrade to the new version when they connect to a newly upgraded Enterprise Manager.

Note: To upgrade a standalone Workstation, you install a new one.

You must manually upgrade the following:

■ Agents

■ Standalone 8.x instances of WebView, ProbeBuilder, and the EPAgent

■ Customizations (you must manually copy over any customized files)

■ If you are running Introscope versions 8.1x or later on the z/OS operating system, you must perform a manual upgrade. See Manual upgrade and upgrade change summary (see page 253).

■ If you are upgrading a 7.x agent with ChangeDetector, you should delete the ChangeDetector cache before upgrading. Otherwise, ChangeDetector fails to operate correctly.

■ If you encounter issues with tracking changes, be sure to copy over the changes.db file from the prior installation to the new version.

For details, see Manual upgrade and upgrade change summary (see page 253).

What happens during an Introscope automated upgrade

During an automated upgrade, the Introscope installer does the following:

■ Replaces all Introscope program files.

■ Leaves intact all user data and log files. The installer may rename or move some files to different locations. For details, see About file changes during an Introscope upgrade.

■ Upgrades configuration files and startup scripts so that the new instance's files include the old instance's settings.



■ Performs the same upgrade tasks as those listed in Manual upgrade and upgrade change summary (see page 253). See the information in that section for details on what happens to pre-upgrade files and settings.

■ Moves obsolete files to <EM_Home>/backup/<iscXx>, where <iscXx> is the release number of the old installation—for example, isc81P8.

■ Takes activated properties that were originally commented out and places them underneath the same property’s example.

For example, for a property that originally appears in the property file as:

# Some EM Property - optional

#commented.out.property=true

... and you had uncommented it and changed its value:

commented.out.property=false

... then the installer will retain your change and place the line under the example, to look like this:

# First EM Property - optional

#commented.out.property=true

commented.out.property=false

What to do before upgrading Introscope

This section covers what preparation tasks there are to do before you upgrade, and also what tasks you need to do just before you begin the upgrade.

To prepare for the upgrade to 9.0:

1. Understand the installation process, and how your Introscope installation is affected by it, by reading:

■ All preparation tasks; see Preparing for all upgrades (see page 152) and Preparing for Introscope-related upgrades (see page 153).

■ All upgrade tasks; see Upgrading from Introscope (see page 160).

■ All completion tasks; see Completing the upgrade (see page 233).

2. Note the location of:

■ The external components package archive and its accompanying End User License Agreement file, eula.txt. See External component packages (see page 51). If you are upgrading from a previous version of Introscope, you must obtain the current external components package archive.

■ Your CA Wily license file and CA Wily End User License Agreement file, ca-eula.txt. This is not the same as the eula.txt file.



3. Schedule your upgrade for a period that allows enough time to perform these upgrade-related tasks:

■ Prior to the upgrade, a full backup of the Enterprise Manager, or an image of the system on which the Enterprise Manager is running.

■ Perform the upgrade itself.

■ Perform post-upgrade tasks.

Immediately before you begin the upgrade

After you have planned for your upgrade, then it is time to do backups and other file-specific tasks before you begin the upgrade.

Immediately before you begin the upgrade:

1. Verify that you are logged in as a user with full Read/Write/Execute permissions on the Introscope directory, preferably as the root user.

2. Shut down your Enterprise Manager and all other Introscope components.

3. If you are upgrading from Introscope 8.0 to 9.0, back up the \traces directory of your Introscope 8.x installation before you perform the upgrade.

WARNING: It is vital that you back up this directory to avoid losing data.

4. Ensure that all folders and text files are closed. No running process should be accessing any file in your Introscope installation.

5. Perform a full backup of the Enterprise Manager, or create an image of the system on which the Enterprise Manager is running. For details about backing up SmartStor and other databases, see the Introscope Configuration and Administration Guide.

6. If the Enterprise Manager directory includes a Workstation, uninstall the Workstation now. You must upgrade the Enterprise Manager, then reinstall the Workstation as a post-upgrade step (see Completing the upgrade (see page 233)).

The uninstaller is in the directory <EM_Home>\UninstallerData\ws.

Preparing for Wily CEM-related upgrades


7. The installer will back up extensions, .JAR files, and docs from your existing Introscope instance, then remove them from the old installation directory.

For the location of the backup directory, see What happens during an Introscope automated upgrade (see page 155). If you want to delete those files, you must do so manually. For more information about upgrading Introscope extensions and PowerPacks, see Upgrading PowerPacks and extensions (see page 232) .

IMPORTANT! Refer to the CA Wily APM Sizing and Performance Guide to determine if it’s appropriate to re-use your existing 4.5 TESS machines or to move your installation and upgrade onto new machines. Re-using a TIM as a TIM is supported.

8. If you determine that it is appropriate to re-use your 4.5 TESS machine, before you install any Introscope components you must unblock the ports needed by the Enterprise Manager. For details, see Unblocking ports on a former Wily CEM appliance (see page 192).


This section pertains to those of you who are upgrading either Wily CEM installations or CA Wily APM. The table below lists the current and target installations that this section covers.



CA Wily APM


CA Wily APM



This section covers what you need to know before you upgrade your Wily CEM installation, and what you need to do before you proceed with the upgrade.



Main points to be aware of when upgrading Wily CEM

The main differentiator in upgrading Wily CEM is whether you’re upgrading on the same machines, or onto new machines. This decision affects how upgrade the PostgreSQL database.

If you are upgrading on the same machine, you do an in-place upgrade.


Otherwise, you need to create a database backup file, install a new APM database (PostgreSQL) onto the new machine, and load the backup file into the new APM database installation.

Note: If the operating system on the new machine is Windows or 64-bit Linux, you must upgrade the database before creating the database backup file.

What to do before upgrading Wily CEM

1. Prepare for the upgrade, such as backing up data and reviewing the upgrade process. For details, see Preparing for all upgrades (see page 152).

For Wily CEM installations:

■ Create a backup file of the 4.5.x Wily CEM (PostgreSQL) database from the 4.5.x Database Backup and Restore tab in the administrator console. For details, see Chapter 10 in the version 4.5 Wily CEM Administration Guide.

Note: In version 4.5.x, ad-hoc backups go into /etc/wily/cem/data/adhoc-backups, whereas scheduled backup files go into: /etc/wily/cem/data/dbbackups. If the scheduled backup ran successfully and nothing has changed since the time of that backup, you can use that backup file.

■ Backup TIM configuration data. For details, see Backing up and restoring TIM configuration data (see page 187).

IMPORTANT! The maximum number of days that defect data can be stored has been reduced to 30 days. These settings are controlled by the "Delete Defects After" option on the Setup > Incident Settings page of the Wily CEM Console. Defects older than 30 days are deleted at the first daily APM database purge after upgrade. For more information, see the Wily CEM Configuration and Administration Guide.

Upgrading from Introscope


2. Copy all Wily CEM customizations to a backup location. This includes:

■ tess-customer.properties file

■ defect evidence files

■ CA Service Desk settings

■ plug-ins

■ Introscope Transaction Trace settings (if the defaults have been customized). For more details, see the CA Wily CEM Integration Guide.

For details on where these files are located, see Configuring the Enterprise Manager for Wily CEM post-upgrade (see page 190).

3. Disable the TIMs. For details, see the version 4.5 Wily CEM Installation Guide.

4. Stop the TIMs. For details, see the version 4.5 Wily CEM Installation Guide.

5. Export the Wily CEM operators to an XML file. For details, see Upgrading security (see page 235).

6. Stop the TESS on the 4.5.x machine (M-1). For details, see the version 4.5 Wily CEM Installation Guide.

7. If you determine that it is appropriate to re-use your 4.5 TESS machine, before you install any Introscope components you must unblock the ports needed by the Enterprise Manager. For details, see Unblocking ports on a former Wily CEM appliance (see page 192).


This section pertains to those of you who are upgrading either Introscope-only installations or CA Wily APM. The table below lists the current and target installations that this section covers.





CA Wily APM


CA Wily APM



Other than the addition of the APM database, the rest of the Introscope upgrade is mostly similar to previous upgrades.

In most cases, you can automatically upgrade WebView and EPAgents along with the Enterprise Manager. If a component was not installed at the same time as the Enterprise Manager, you must manually upgrade that component.

For Workstations, you must install new ones, you cannot upgrade the prior versions.For any PowerPacks or extensions that you currently use or that you intend to use, you may have to do some manual configurations before they are ready to use.

For agents, it is recommended to upgrade them one at a time. This way you can pinpoint errors to a specific agent if something goes wrong with the upgrade and thus minimize production down time. If desired, you can wait to upgrade the agents, although you will not have access to the new functionality in this release.

Verify that the Enterprise Managers, Workstations, and Agents run without errors to be sure you configured them correctly. If your intention is to continue using only Introscope, then you’re ready to go.


Upgrading a standalone Introscope: architecture overview (see page 162) Upgrading a clustered Introscope: architecture overview (see page 165) Introscope upgrade workflow (see page 167) Introscope upgrade workflow details (see page 170) Adding Wily CEM to an upgraded Introscope (see page 172)



Upgrading a standalone Introscope: architecture overview

If your current installation uses a standalone Enterprise Manager, the following diagram illustrates the essential parts of the installation. There are one or more agents connected to a single Enterprise Manager. The Introscope Workstation connects to the Enterprise Manager, and the Enterprise Manager contains the SmartStor database.



Post-upgrade standalone Introscope architecture overview

After the upgrade, the Introscope-only, standalone Enterprise Manager deployment has an architecture that looks like what is shown in the following diagram. The main difference is the addition of the APM database, which the Enterprise Manager connects to and uses for data storage. The Wily CEM console is available as well, for use with agent recording.



Post-upgrade CA Wily APM from standalone Introscope architecture overview

If you then choose to add the rest of CA Wily APM functionality, the architecture looks like what is shown in the following diagram. There are now at least two Collector Enterprise Managers connecting to a MOM Enterprise Manager. The TIMs connect to one Collector, and the agents connect to a separate Collector. All Enterprise Managers connect to the APM database. There are some Enterprise Manager services that you distribute to Collectors. You use the Wily CEM console to view Wily CEM data by way of the MOM, and you use the Introscope Workstation to see Introscope data by way of the MOM. Each Enterprise Manager continues to have its own SmartStor database. The MOM Enterprise Manager connects to the CA Embedded Entitlements Manager, to manage user and group authentication and authorization.



Upgrading a clustered Introscope: architecture overview

If your current installation uses a cluster of Enterprise Managers, the following diagram illustrates the essential parts of the installation. There are one or more agents connected to one or more Collector Enterprise Managers. The Introscope Workstation connects to the Enterprise Manager, and each Enterprise Manager has its own SmartStor database.



Post-upgrade clustered Introscope architecture overview

After the upgrade, the Introscope-only, clustered Enterprise Manager deployment has an architecture that looks like what is shown in the following diagram. The main difference is the addition of the APM database, which each Enterprise Manager connects to and uses for data storage.



Post-upgrade clustered CA Wily APM architecture overview

The following diagram illustrates how to integrate Wily CEM with an upgraded, clustered Introscope, so that you have an integrated CA Wily APM environment. In this diagram, there are two TIMs connected to one of the Collector Enterprise Managers, and the Wily CEM Console is available from the MOM. Each Enterprise Manager has some Enterprise Manager services distributed on it. The Agents report to the other Collectors. The MOM Enterprise Manager connects to the CA Embedded Entitlements Manager, to manage user and group authentication and authorization.

Introscope upgrade workflow

The following workflow diagram illustrates the main steps involved in upgrading existing Introscope environments. There are essentially two different paths, depending on what kind of Enterprise Manager you are upgrading. When upgrading a standalone Enterprise Manager or a MOM, you also install the APM database. When upgrading a Collector, you specify the connection settings to an existing APM database, which is on the MOM.



The first diagram shows the process involved in upgrading from Introscope to Introscope.

If upgrading a clustered environment

Upgrade standalone Enterprise Manager or

MOM & Install new APM database2

Perform manual upgrade Introscope tasks

5

Prepare for upgrade1

Upgrade Collectors, connect to existing

APM database3

Redeploy PowerPack & extension files on the Enterprise Manager

Install CA EEM (optional)

4

Upgrade agents, one at a time8

Install new Workstations

7

Introscope Upgrade Workflow:

Upgrading to Introscope

6



The second diagram shows the process of upgrading from Introscope to CA Wily APM:

Introscope Upgrade Workflow:

Upgrading to CA Wily APM

If upgrading a clustered environment

Upgrade standalone Enterprise Manager or

MOM & Install new APM database2

Perform manual upgrade Introscope tasks

5

Prepare for upgrade1

Upgrade Collectors, connect to existing

APM database3

Redeploy PowerPack & extension files on the Enterprise Manager

Add Wily CEM to upgraded Introscope

Install & configure TIMs10

Redistribute services on Enterprise Managers

11

Perform post-install Wily CEM configurations

12

Decide how many TIMs to install

9

Install CA EEM4

Upgrade agents, one at a time8

Install new Workstations

7

6



Introscope upgrade workflow details

Below are the general tasks that you need to perform to upgrade your existing Introscope installation. For a graphical overview of these tasks, see Introscope upgrade workflow (see page 167).

The workflow table below lists each step in more detail.

Step Description Task Details / More Information

1 Prepare for the upgrade. For example, be sure to back up your existing environment, as a precaution.

For more information: see Preparing for all upgrades (see page 152), Preparing for Introscope-related upgrades (see page 153).

2 Run the main Introscope installer, and select the desired options to install or upgrade.

Upgrade the standalone Enterprise Manager or the MOM.

For standalone installations, continue to step 4.

When upgrading a standalone Enterprise Manager or MOM, you also install a new APM database.

If WebView or EPAgent was installed during the same installation as the Enterprise Manager, you can upgrade them with the installer.

The installer automatically upgrades the SmartStor, Transaction Event, and baselines databases.

You can run the installer in GUI, console, or silent modes.

In the main installer, choose the following options to install a new APM database:

■ Choose PostgreSQL as the database type.

■ In the Install Database or Choose Existing Database window, choose Install database.

■ In the Target Installation Directory for the Database window, specify the directory name for the APM database.

■ In the Database Administration Settings window, enter the port, PostgreSQL administrator user name and password for the new database.

■ In the Database Settings window, enter the new database name, user name, and password.

For more information: see Upgrading Enterprise Managers and databases (GUI or console modes) (see page 223), Specifying the APM database during upgrade (see page 226), and Specifying the APM database (see page 70).




3 If upgrading a Collector:

When you upgrade the Collector Enterprise Manager, specify the settings to connect to the APM database on the MOM.

When going through the installer to upgrade a Collector, choose the following options to connect to the database on the MOM:

■ Choose PostgreSQL as the database type.

■ In the Install Database or Choose Existing Database window, select the Choose an Existing Database option.

■ In the Database Settings window, enter the existing database host, port, name, user name, and password.

For more information: see Upgrading Enterprise Managers and databases (GUI or console modes) (see page 223) and Specifying the APM database (see page 70).

4 Install CA EEM. If you will be using the CA Embedded Entitlements Manager (CA EEM) to manage common access policies, authentication, and authorization, be sure to install CA EEM.

This is an optional task if you are only upgrading to Introscope.

For more information: see Upgrading security (see page 235), the CA Wily APM Security Guide, and the CA EEM installation documentation.

5 Perform manual upgrade tasks. For more information: see Completing the upgrade (see page 233).

6 Install new standalone workstations.

Prior standalone workstations are not upgraded, you install the new version instead. You can install a workstation in GUI, console, or silent modes.

For more information: see Installing the Workstation (see page 77).

7 Redeploy PowerPack and extension files on the Enterprise Manager.

Depending on which extension or PowerPack you decide to use, you may need to install additional files or do manual configurations.

For more information: see Installing Introscope PowerPacks and extensions (see page 121).

8 Upgrade agents, one at a time.

Manually upgrade agents and AutoProbe or ProbeBuilder together, and run your code through the 9.x ProbeBuilder to instrument it for the 9.x Agent.

You can use agents from prior Introscope versions, but there is a loss of functionality if you do so.

Note: If necessary, you can upgrade all components but the agents—it is possible to upgrade Enterprise Managers and Workstations without upgrading agents, AutoProbe, ProbeBuilder, and Platform Monitor.

For more information: see Introscope component version compatibility (see page 154), Upgrading the bytecode, agents, and platform monitors, and the Introscope Java Agent Guide and Introscope .NET Agent Guide.



IMPORTANT! Be sure to change all default passwords after upgrading. For more information, see Post-install password security (see page 54).

Adding Wily CEM to an upgraded Introscope

When you have upgraded and verified your Introscope installation, you can then choose to integrate the rest of CA Wily APM—namely, adding Wily CEM functionality.

Be sure your Enterprise Manager and APM database machines meet the requirements for the additional load. Follow the instructions to do a new install of a TIM software appliance. The workflow table below lists each step in more detail.


9 Decide how many TIMs to install and onto which machines. Ensure the machines meet or exceed the minimum requirements.

For more information: for information related to architecture, sizing, and security, consult the following CA Wily APM documentation:

CA Wily APM Sizing and Performance Guide

CA Wily APM Security Guide

Wily CEM Configuration and Administration Guide

10 Install and configure the TIMs for use with Wily CEM.

For more information: see Installing Wily CEM (see page 129).

11 Redistribute services on Enterprise Managers.

Access the MOM to distribute the Enterprise Managers appropriately. For details, see the Wily CEM Configuration and Administration Guide.

Note: If an Enterprise Manager is running on a machine with a 32-bit operating system, redistribute the Enterprise Manager Services so that the Stats Aggregation Service and TIM Collection Service are assigned to different Enterprise Managers. You should assign the DB Cleanup Service to the Enterprise Manager that has the Stats Aggregation Service.

12 Perform post-install Wily CEM configurations.

Consult the guides below for specific post-install tasks, such as refining security permissions, checking age-out settings, and checking database settings.

For more information: see the Introscope Configuration and Administration Guide, Wily CEM Configuration and Administration Guide, and Wily CEM Integration Guide.

Upgrading from CA Wily APM



This section pertains to those of you who are upgrading CA Wily APM, which includes both Introscope and Wily CEM. The table below lists the current and target installations that this section covers.



CA Wily APM


CA Wily APM

Because of the architecture changes in CA Wily APM 9.x, you must upgrade your existing CA Wily APM installation carefully.

■ There is no longer a separate TESS. What used to be the TESS is now included in the Introscope Enterprise Manager.

■ Both Wily CEM and Introscope now store data in the APM database schema. The APM database schema can be a PostgreSQL database schema or an Oracle database schema.

Upgrading CA Wily APM: architecture overview

If your installation currently uses both Introscope and Wily CEM integrated together, otherwise known as CA Wily APM 8.x, the following diagram illustrates the essential components of your installation.

There are one or more agents connected to one or more Collector Enterprise Managers. The Introscope Workstation connects to the Enterprise Manager, and the SmartStor database is contained with the Enterprise Manager.



If your CA Wily APM 8.x installation has Introscope integrated with Wily CEM, then the MOM (Manager of Managers) connects to the 4.5.x Wily CEM TESS. The TESS communicates with individual TIMs, and contains the APM database. The CEM console connects to the TESS.

After the upgrade, the CA Wily APM upgrade has an architecture that looks like the following diagram. The services that were associated with TESS are now distributed as Enterprise Manager Services, and all Enterprise Managers connect to the APM database to store data for business transactions and application triage maps.

It’s a best practice to have the TIMs connect to one Collector and the agents connect to one or more other Collectors.



Agents and TIMs communicate with Collectors (not the same ones). Each Enterprise Manager continues to have its own SmartStor database. You use the Wily CEM Console to administer Wily CEM by way of the MOM, and you continue to use the Introscope Workstation to see data from the agents and Collectors by way of the MOM. The MOM Enterprise Manager connects to the CA Embedded Entitlements Manager, to manage user and group authentication and authorization.



CA Wily APM upgrade workflow

The following diagram illustrates the essential steps to upgrade CA Wily APM installations:

Export Wily CEM operatorsto XML

CA Wily APMUpgrade Workflow

Upgrade the restof Introscope

Upgrade the restof Wily CEM

Upgrade to APM databaseschema

Prepare for upgrade

Install CA EEM

Import Wily CEM operatorsinto EEM

Redistribute serviceson EnterpriseManagersUpgrade TIMsComplete post-upgrade tasks

9

Complete manualpost-upgrade tasksInstall workstationsUpgrade PowerPacks& extensionsUpgrade agents, onea time

8

Upgrade EnterpriseManagers

3

2

1

6

7

4

When upgrading CA Wily APM, first upgrade the 4.5 PostgreSQL database. You then upgrade the Enterprise Managers and connect to the upgraded APM database. After the Introscope cluster is established, go ahead and export the Wily CEM operators to XML, install CA EEM and import the Wily CEM operators.

After you have upgraded to the APM database, installed the Enterprise Managers, and set up CA EEM, you’re then ready to upgrade the rest of Introscope and Wily CEM.



CA Wily APM upgrade workflow details

Below are the general tasks that you need to perform to upgrade your existing CA Wily APM installation, which includes both Introscope and Wily CEM. For a graphical overview of these tasks, see CA Wily APM upgrade workflow (see page 176).

This upgrade scenario is targeted for a clustered Introscope installation, although it also works for a standalone environment. The workflow table below lists each step in more detail.

Task Description More Information


For more information: see Preparing for all upgrades (see page 152), Preparing for Introscope-related upgrades (see page 153), and Preparing for Wily CEM-related upgrades (see page 158).

2 Upgrade the existing 4.5 PostgreSQL database to the APM database schema.

The existing PostgreSQL database was used as part of the 4.5 TESS.

Note: Refer to the CA Wily APM Sizing and Performance Guide to determine if it’s appropriate to re-use your existing 4.5 TESS machines or to move your installation and upgrade onto new machines. Re-using a TIM as a TIM is supported.

For more details about upgrading the 4.5.x PostgreSQL, whether on the same or new machines, see Upgrading the APM database (special cases) (see page 197) and Specifying the APM database during upgrade (see page 226).

Depending on your deployment, you may install Enterprise Managers at the same time as upgrading the 4.5 PostgreSQL database. For configuration and deployment guidance, see the CA Wily APM Sizing and Performance Guide.




Upgrade the existing 4.5 PostgreSQL database to the APM database schema

(continued)

Use the Introscope installer to upgrade the database schema using the following steps:

■ Select Database Only as the installation set.

■ Select a target installation directory that is not the Enterprise Manager home directory.

■ Select PostgreSQL as the APM database.

■ Select the Upgrade database schema or create new database schema option.

■ In the Database Administration Settings window, enter the port number, PostgreSQL administrator account name and password for the existing 4.5.x database.

■ In the Database Settings window, enter the existing 4.5.x database name, user name, and password.

For more information: see Specifying the APM database (see page 70).

Note: If upgrading a PostgreSQL database onto a new machine, you can upgrade the database instead by using the restore script (UNIX only), if desired. If you want to keep just the configuration data and not any defect data, you can run the database configuration scripts. For details, see Migrating the APM database (see page 196) and the Wily CEM Configuration and Administration Guide.

3 Upgrade Enterprise Managers. If upgrading a clustered environment, upgrade the MOM and then the Collectors.

If upgrading a standalone environment, upgrade the standalone Enterprise Manager to a MOM and install an additional two Collectors.

For more information: See Installing Introscope main components (see page 65). Also, refer to the CA Wily APM Sizing and Performance Guide for details as to how many Collectors to install.

4 Export Wily CEM operator data to an .XML file.

For more information: see Upgrading security (see page 235).


For more information: See Upgrading security (see page 235), the CA Wily APM Security Guide, and the CA EEM installation documentation.

Upgrading from Wily CEM



7 Import the Wily CEM operator data into CA EEM.

For details, see Upgrading security (see page 235).

8 Upgrade the rest of Introscope. For more information: See steps 5 through 8 in Introscope upgrade workflow details (see page 170).

9 Upgrade the rest of Wily CEM. For more information: See steps 7 through 9 in Wily CEM upgrade workflow details (see page 183).

Be sure to change all default passwords after upgrading. For more information, see Post-install password security (see page 54).


This section pertains to those of you who are upgrading Wily CEM. The table below lists the current and target installations that this section covers.




This section contains a brief overview of the architectural changes involved in upgrading your Wily CEM installation, and also an overview of the upgrade tasks.


Upgrading Wily CEM: architecture overview (see page 180) Wily CEM upgrade workflow (see page 182) Wily CEM upgrade workflow details (see page 183) Adding Introscope to an upgraded Wily CEM (see page 186)



Upgrading Wily CEM: architecture overview

The Wily CEM-only installation has an architecture that looks like the following diagram. There is a TESS that communicates with multiple TIMS, and the TESS contains the PostgreSQL database. The Wily CEM Console connects and communicates with the TESS.

Post-upgrade CA Wily APM from Wily CEM architecture overview

After the upgrade, the Wily CEM-only upgrade has an architecture that looks like the following diagram. What used to be the TESS is now distributed as Enterprise Manager Services, and all Enterprise Managers connect to the APM database.

It’s a best practice to have the TIMs connect to one Collector and the agents connect to one or more other Collectors.



Use the Wily CEM Console to administer Wily CEM by way of the MOM, and you use the Introscope Workstation to see data from the agents and Collectors by way of the MOM. The MOM Enterprise Manager connects to the CA Embedded Entitlements Manager, to manage user and group authentication and authorization.

Note: After you upgrade, the installation will not have Introscope agents. When you are ready, you can add agents and use the full set of CA Wily APM 9.x features.



Wily CEM upgrade workflow

The following diagram illustrates the essential steps to upgrade Wily CEM installations:

Upgrade PostgreSQL tothe APM database

schema

Wily CEM UpgradeWorkflow

Install the restof Introscope

Prepare for upgrade

Export Wily CEMoperators to XML

Install CA EEM

Load Wily CEM operatorsinto CA EEM

Redistribute services onEnterprise Managers

Upgrade TIMs

Perform post-upgradetasks

Plan for additional machinesEnsure machines meet or exceedmin. requirementsInstall additional EnterpriseManagers, WebView, or EPAgentsInstall workstationsVerify Enterprise Managers andworkstations connect correctlyInstall agents as neededPerform post-install tasks

10

Install EnterpriseManagers

1

2

3

5

6

7

8

9

4



Wily CEM upgrade workflow details

Below are the general tasks that you need to perform to upgrade your existing Wily CEM installation. For a graphical overview of these tasks, see Wily CEM upgrade workflow (see page 182). The workflow table below lists each step in more detail.



For more information: see Preparing for all upgrades (see page 152) and Preparing for Wily CEM-related upgrades (see page 158).

2 Upgrade the 4.5 PostgreSQL database to the APM database schema.

Refer to the CA Wily APM Sizing and Performance Guide to determine if it’s appropriate to re-use your existing 4.5 TESS machines or to move your installation and upgrade onto new machines. Re-using a TIM as a TIM is supported.

For more details about upgrading the 4.5.x PostgreSQL, whether on the same or new machines, see Upgrading the APM database (special cases) (see page 197).

Depending on your deployment, you may install Enterprise Managers at the same time as upgrading the 4.5 PostgreSQL database. For configuration and deployment guidance, see the CA Wily APM Sizing and Performance Guide.

For more information: see Migrating the APM database (see page 196) and Moving the APM database to a different machine (see page 209).

3

Install Enterprise Managers. In general, you should install at least 2 Collectors and a MOM.

If you didn’t install Enterprise Managers at the same time as upgrading the 4.5.x PostgreSQL database, install them now.

Run the Introscope 9.x main installer to install the Enterprise Manager. Connect to the upgraded APM database.

For details about how many Enterprise Managers to install on which machines, see the CA Wily APM Sizing and Performance Guide.

When going through the installer, choose the following options to connect to the existing database:

■ In the Install Database or Choose Existing Database window, select the Choose an Existing Database option.

■ In the Database Settings window, enter the existing database host, port, name, username, and password.

For more information: see Specifying the APM database (see page 70).




4 Export Wily CEM operator data to an .XML file.

For more information: see Upgrading security (see page 235).


For more information: see Upgrading security (see page 235), the CA Wily PM Security Guide, and the CA EEM installation documentation.

6 Load the Wily CEM operator data into CA EEM.

For details, see Upgrading security (see page 235).

7 Redistribute services on Enterprise Managers.

Access the MOM to distribute the Enterprise Managers appropriately. For details, see the Wily CEM Configuration and Administration Guide.

Note: If an Enterprise Manager is running on a machine with a 32-bit operating system: redistribute the Enterprise Manager Services so that the Stats Aggregation Service and TIM Collection Service are assigned to different Enterprise Managers. You should assign the DB Cleanup Service to the Enterprise Manager that has the Stats Aggregation Service.

8 Upgrade the TIMs. Do this by downloading the necessary files and uploading them through Wily CEM. For details, see Upgrading a TIM (see page 189).




9 Perform Wily CEM post-upgrade tasks. This includes:

■ Configuring the TIM network management settings (see page 133)

■ Configuring TIM monitoring (see page 138)

■ Re-enable plug-ins. For details, see the CEM Integration Guide.

■ Copy plug-ins from the Wily CEM 4.5 location to the new CA Wily APM installation directory. For details, see Copying plug-ins (see page 191).

■ If you used the HTTP-enabled license in Wily CEM 4.5.x, then see the CA Wily APM Security Guide for information about protecting HTTP requests and responses on defects.

■ Copying the previous Wily CEM configuration properties (see page 190)

■ Copying the defect evidence files (see page 191)

■ Specifying customized CA Service Desk settings (see page 191)

■ Ensure all TIMs are running, and verify the upgrade. For details, see Verifying Wily CEM configurations (see page 145).

■ Uninstalling 4.5.x TESS (see page 194).

If you intend to re-use the old 4.5.x TESS machine, be sure to delete any remaining directories that were used.

For details, see Cleaning up a 4.5.x TESS machine for re-use (see page 195).

IMPORTANT! Be sure to change all default passwords after upgrading. For more information, see Post-install password security (see page 54).



Adding Introscope to an upgraded Wily CEM

When adding Introscope functionality to an upgraded Wily CEM installation, first decide which machines and processes you will monitor with agents. Refer to the Introscope documentation for guidance in making these decisions. Then install Enterprise Managers, Workstations, and agents, as needed. The workflow table below lists each step in more detail.


10 Decide how many additional machines are needed, and what to install onto which machines.

For more information: For information related to architecture, sizing, and security, consult the following CA Wily APM documentation:

CA Wily APM Sizing and Performance Guide

CA Wily APM Security Guide

Wily CEM Configuration and Administration Guide

CA Wily APM Overview Guide

11 Ensure the machines meet or exceed the minimum requirements.

For more information: see Preparing for install or upgrade (see page 25).

12 Install the Enterprise Manager, WebView workstation, and related files.

You already installed at least 2 Collectors and a MOM. Install more Enterprise Managers or additional components as needed.

For more information: see Installing Introscope in GUI or console mode (see page 59).

13 If you plan on using PowerPacks or extensions, install additional components and do manual configurations as needed.

For more information: see Installing Introscope PowerPacks and extensions (see page 121).

14 Install the Workstation and Java Web Start workstation.

For more information: see Installing the Workstation (see page 77).

15 Verify that the Enterprise Manager and Workstation are installed correctly.

For more information: see Verifying the Enterprise Manager installation (see page 76) and Verifying the Workstation installation (see page 78).

16 Install agents, and make sure you see agent data in the Enterprise Manager.

For more information: see the Introscope Java Agent Guide and the Introscope .NET Agent Guide.

17 Perform post-install configurations.

For more information: see the Introscope Configuration and Administration Guide, Wily CEM Configuration and Administration Guide, and Wily CEM Integration Guide.


Chapter 10: Upgrading Wily CEM components

This chapter contains information related to upgrading a TIM and upgrading the APM database. For an overview of the upgrade process for Wily CEM, see Upgrading to CA Wily APM 9.x (see page 149).

In most cases, you’ll need to change passwords related to the APM database after the installation completes. Depending on the kind of installation you are upgrading from and to, you may have to run some batch scripts on the APM database.


Backing up and restoring TIM configuration data (see page 187) Upgrading a TIM (see page 189) Configuring the Enterprise Manager for Wily CEM post-upgrade (see page 190) Unblocking ports on a former Wily CEM appliance (see page 192) Changing the TIM System Setup Page password (see page 194) Uninstalling 4.5.x TESS (see page 194)

Backing up and restoring TIM configuration data

If you are re-using a TIM machine as a TIM, you should back up all TIM configurations before performing a fresh install of a TIM. The fresh install of TIM as a software appliance deletes all existing configurations and customizations. You can then re-use the previous configuration data on the new TIM, if desired.

This process involves the following:

■ backing up existing TIM configuration data

■ installing a fresh TIM operating system

■ restoring the saved TIM configuration data

■ installing the remaining TIM software

For additional information about whether to upgrade a TIM or do a fresh install, please contact your account representative or call 1-800-225-5224.

Backing up and restoring TIM configuration data


To back up and restore TIM configuration data:

1. Log in to the TIM machine as root using a console or ssh.

2. Save the TIM configuration to a file /tmp/timconfig.tar by running the following commands:

cd /

tar cf /tmp/timconfig.tar usr/local/wily/cem/tim/config

3. Save the /tmp/timconfig.tar file to another machine over the network. If you have a Linux or UNIX machine on your network, you can use scp to copy the file to the remote machine:

scp /tmp/timconfig.tar remote-user@remote-host:timconfig.tar

where remote-host is the machine to save the file to, and remote-user is the user name on that machine.

4. Install the TIM operating system from the kickstart DVD. For details, see Installing the operating system for a new TIM (kickstart DVD) (see page 130).

IMPORTANT! Only install the operating system at this point. You must restore the previous TIM configuration data before installing the remaining TIM software. Otherwise, the restored configuration data is lost.

5. Proceed with setting the TIM’s time zone and network configuration. For details, see Configuring the TIM network management settings (see page 133) and Setting the time zone on a TIM (see page 137).

6. Copy the saved TIM configuration data to /tmp/timconfig.tar on the TIM machine.

If you used the scp command above, the corresponding command to bring the file back is as follows:

scp remote-user@remote-host:timconfig.tar /tmp/timconfig.tar

7. Unpack the file by running the following commands:

cd /

tar xf /tmp/timconfig.tar

8. Install the remaining TIM software and other TIM installation tasks. For details, see Installing and configuring a TIM (see page 129).

Upgrading a TIM


Upgrading a TIM

Occasionally you will need to upgrade to the latest version of Wily CEM. This provides an opportunity to take advantage of the latest features Wily CEM has to offer.

IMPORTANT! It is usually recommended to back up the database before a major release upgrade. Often the Wily CEM software upgrade includes a database upgrade. Your database upgrade times are very dependent on your data. Check the Read Me for this, plus any other deployment instructions for the new release.

IMPORTANT! To minimize the amount of transaction defect information lost during an upgrade, it is a good idea to upgrade the TIMs and get them back in service as soon as possible.

Obtain the upgrade packages that you need to install on the TIM.

For example, to upgrade the TIM, you need:

■ APM_INSTUPD<version>.img

■ APMThirdPart<version>.img

■ APM_TIM5000_<version>.img

Note: These packages do not upgrade the operating system. If you are re-using a TIM as a TIM, installing a new TIM appliance on existing TIM hardware, be sure to back up all TIM configurations before doing so. For details, see Backing up and restoring TIM configuration data (see page 187).

To upgrade the TIM:

1. Perform any necessary pre-installation steps, as mentioned in Preparing for all upgrades and Preparing for Wily CEM-related upgrades.

2. Copy the TIM upgrade packages to a local directory or other easily accessible location.

3. If the 4.5x TESS is running, open the 4.5x Wily CEM administrator console and disable all TIMs (monitors). For details, see the version 4.5 Wily CEM Installation Guide.

4. On the TIM: Access the Wily System Setup page. For details, see Accessing the Wily System Setup page for the TIM (see page 144).

5. Click Install New Software.

Configuring the Enterprise Manager for Wily CEM post-upgrade


6. Browse to an installation package and then click Upload and Install.

If you are upgrading, install these packages in this order:

■ installonce-update-<version>.image

■ third-party-update-<version>.image

■ tim-complete-<version>.image

When you install third-party and TIM packages, you are presented with a license agreement page which you must accept before continuing.

Tip: It is a good idea to install one image at a time. You should let the installation complete before attempting another installation.

7. Wait for the installation results.

The final message should say that the package was successfully installed.

8. If you need to install another package on the TIM, click Install Another Product, and repeat step 6 and step 7 for the next package.

Note: The TIM restarts automatically, so unless you are specifically advised in the Read Me, it is not necessary to shut down and restart the TIM after the installation.

9. Click Return to Setup to return to the TIM’s Wily System Setup page.


After you have upgraded the TIM, there are some configuration tasks to do on the Enterprise Manager so that the TIMs and the Enterprise Manager communicate with each other.

Copying the previous Wily CEM configuration properties

If your Wily CEM 4.5 installation had customized tess-customer.properties, copy that file from the TESS machine to the new Enterprise Manager location.

old TESS 4.5 location:

/etc/wily/cem/tess/tomcat/webapps/wily/WEB-INF/classes

new Enterprise Manager location:

<EM_Home>\config



Copying the defect evidence files

If your Wily CEM 4.5 installation used customized defect evidence files, copy the .HTM files from the old 4.5 TESS location to the new Enterprise Manager location.

The defect details page can link to a custom web page that can contain additional defect information.

old 4.5 TESS location:

/var/www/html/wily/cem/tess/defects

new Enterprise Manager location:

<EM_home>\cem\tess\additionaldefectdetails\

If you are using a clustered environment, copy the files to the MOM.

For details on customizing this location, see the Wily CEM Configuration and Administration Guide.

Specifying customized CA Service Desk settings

If your Wily CEM 4.5 installation had customized settings for CA Service Desk, you must re-enable the plug-in and re-enter these settings after the upgrade. Integration with CA Service Desk provides incident management support by automatically generating service requests from Wily CEM incidents.

For details, see the Wily CEM Integration Guide.

Copying plug-ins

Copy the user-defined HTTP Analyzer plug-ins from the previous Wily CEM 4.5 location to the new CA Wily APM installation directory. Update the path to the correct location using the Wily CEM console (Setup > Plug-ins > CA Wily CEM HTTP Analyzer).

previous Wily CEM 4.5 location: /etc/wily/cem/tess/plugins

new CA Wily APM installation directory: <EM_HOME>/cem/tess/plugins

Unblocking ports on a former Wily CEM appliance



In Wily CEM 4.5, a TESS or TIM appliance was configured with a firewall to automatically block most incoming ports for security reasons. In CA Wily APM 9.x, the Enterprise Manager needs to have some ports opened for incoming communication. So, if you plan to install an Enterprise Manager on a machine that previously ran a 4.5 TESS or TIM, you must first unblock the ports you plan to use for the Enterprise Manager.

As an alternative, if you prefer to use your own firewall, you can instead disable the existing firewall.

Be sure to consult a Linux system administrator for additional questions.


The ports that the Enterprise Manager uses for incoming communication are:

■ Enterprise Manager Connection port (default is 5001)

■ Enterprise Manager Web Server port (default is 8081)

■ Enterprise Manager WebView HTTP port (default is 8080)

The procedures below provide instructions on using the configfirewall program to unblock the ports and also for disabling the firewall.

IMPORTANT! Do not use the configfirewall program if the Linux firewall files (/etc/sysconfig/iptables or /etc/sysconfig/ip6tables) have been modified in any way since Wily CEM 4.x was installed on the machine. Modifications may prevent the program from operating correctly. If the firewall files have been modified, have your system administrator unblock the ports.

Tip: Use the iptables or ip6tables command to determine if ports are open. Contact your Linux system administrator for assistance in interpreting the command’s results.

or ipv4, the command is:

"iptables -L -n"

For ipv6, the command is:

"ip6tables -L -n"



To unblock a port on a former 4.5 Wily CEM machine:

1. On the 4.5 Wily CEM machine, navigate to the following directory:

/etc/wily/machine/machine-settings/bin/

2. Run the configfirewall program, according to the following syntax and arguments:

./configfirewall port/ipver/protocol/status

Arguments:

port

Specify either a port number, or an ICMP/ICMPv6 service name

ipver

Specify either ipv4 or ipv6.

protocol

Specify the communication protocol as tcp, udp, icmp, or icmpv6.

status

Specify the status of the port. To enable a port, specify on. To disable a port, specify off.

For example:

./configfirewall 8081/ipv4/tcp/on

If you want the Enterprise Manager to communicate over the port using either IPv4 or IPv6, unblock the port for both:

./configfirewall 8081/ipv4/tcp/on 8081/ipv6/tcp/on

To disable the firewall on a former 4.5 Wily CEM machine:

1. Log in to the machine as root.

2. Run the service command to stop the firewall service during this login session, and run the chkconfig program to prevent the firewall from starting when the system reboots. The commands differ slightly for IPv4 and IPv6 configurations.

For IPv4:

/sbin/service iptables stop

/sbin/chkconfig iptables off

For IPv6:

/sbin/service ip6tables stop

/sbin/chkconfig ip6tables off

Changing the TIM System Setup Page password


Changing the TIM System Setup Page password

As part of your post-installation security tasks, you should change the default password that allows access to the Wily System Setup Page on the TIM. For more information on password security, see Post-install password security (see page 54) and the CA Wily APM Security Guide. Changing this password involves using the htpasswd command on the Linux machine.

To change the TIM System Setup Page password:

1. On the TIM machine, run the following command:

htpasswd /etc/wily/system/httpd.passwd admin

2. At the prompt, enter the new password.

Uninstalling 4.5.x TESS

WARNING: Uninstalling a 4.5.x version of TESS involves dropping the 4.5.x database and uninstalling the TESS-related software. Be sure to first back up the 4.5.x database.

Before you uninstall the 4.5.x TESS, you must first:

■ Ensure no other machine is accessing the TESS machine.

■ Disable all monitors.

■ Stop the TESS.

■ Stop the TIMs.

Uninstalling the 4.5.x TESS involves uninstalling TESS, CEM-base, and the 4.5 PostgreSQL database.

Note: If you want to uninstall TESS but leave the PostgreSQL database, disregard step 1, step 2, and step 12 in the procedure below. This is useful if you are re-using the TESS 4.5.x appliance for CA Wily APM 9.x.


To uninstall the TESS and related software:

1. On the 4.5.x TESS machine, navigate to the following directory:

cd /etc/wily/cem/tess/install/database-scripts

2. In this directory, run the following command to drop the 4.5 PostgreSQL database:

sh dropdb-postgres.sh

The following message displays:

Dropping database "cemdb"




cd /etc/wily/cem/tess/install

4. In this directory, run the following command to uninstall TESS:

sh uninstall


cd /etc/wily/third-party/install

6. In this directory, run the following command to uninstall third-party software:

sh uninstall


cd /etc/wily/cem/tess-help/install

8. In this directory, run the following command to uninstall TESS help:

sh uninstall


cd /etc/wily/cem/cem-base/install

10. In this directory, run the following command to uninstall CEM-base:

sh uninstall


cd /var/lib

12. In this directory, run the following command to uninstall PostgreSQL:

rm -rf pgsql

Cleaning up a 4.5.x TESS machine for re-use


Before you re-use the machine where you had the 4.5.x TESS installed, CA Technologies recommends that you delete any remaining directories that were used. Some of these directories may contain substantial backup data. If desired, you can move the backup files to a different machine, if you want to save the backup data.

To prepare a former 4.5.x TESS machine for re-use:

■ Delete the following directories and their contents:

Wily CEM backups directory:

/var/lib/pgsql/backups

Postgres directories:

/usr/local/wily/postgres

/var/lib/pgsql



Chapter 11: Migrating the APM database

When upgrading from previous versions of CA Wily APM or Wily CEM 4.5, how you upgrade the APM database depends on the kind of deployment you currently have, the method by which you upgrade, and your target deployment scenario. In some cases, you may need to upgrade the APM database in-place or merge two instances of the database.

If your existing deployment uses the APM database on PostgreSQL, you will also need to upgrade the PostgreSQL installation, which involves doing a backup, uninstalling PostgreSQL, installing a new database, and then restoring the backup file into the new database.

Also, your business requirements may drive the need to change your deployment architecture and move the APM database to another machine, operating system, or database platform.

This section contains instructions on performing specific operations to APM database data that you may need to perform as part of your unique upgrade path or data migration plan.

Note: The scripts covered in this section apply only to APM database data stored in PostgreSQL or Oracle; they do not affect SmartStor data.

Before you make any changes to the database, you should make sure that no one else is connected to the database. Otherwise, you may run into data integrity issues, and in some cases, you cannot run the script.

For PostgreSQL users, verify that the postgres service is running. Refer to the PostgreSQL documentation for information on starting or stopping the service.

Upgrading the APM database (special cases)


The database scripts are in the following directories; use the ones appropriate for your operating system.

■ Windows: <EM-home>\install\database-scripts\windows\

■ Linux/Solaris: <EM-home>/install/database-scripts/unix/

For PostgreSQL users, ensure that the machine on which you’re running a database script has PostgreSQL installed. If desired, you can run the script on a remote machine, as long as that remote machine also has PostgreSQL installed.


Upgrading the APM database (special cases) (see page 197) Exporting and restoring the APM database (see page 204) Moving the APM database to a different machine (see page 209) Moving the APM database to another operating system (see page 210) Migrating data from a PostgreSQL database to an Oracle database (see page 210) Changing and verifying APM database settings (see page 214) Configuring PostgreSQL on Linux or Solaris (see page 216) Troubleshooting the non-root PostgreSQL installation on Solaris (see page 217) Uninstalling APM database software or data (see page 217)


When upgrading from previous versions of CA Wily APM or Wily CEM, there may be some additional steps to upgrade the APM database, depending on your upgrade scenario.

For guidance on how many Enterprise Managers to install and onto which machines, see the CA Wily APM Sizing and Performance Guide.

Upgrading the 4.5 PostgreSQL from a Wily CEM installation (overview)

In many cases you upgrade Wily CEM onto new machines, which involves not only upgrading the PostgreSQL database to use the new APM database schema but also exporting it from the old location and restoring it to the new location.




If you intend to upgrade the 4.5 PostgreSQL database on the existing machine, use the main Introscope installer or the database script. For details, see Upgrading the 4.5 PostgreSQL database (see page 199).

To upgrade a Wily CEM 4.5 installation to CA Wily APM 9.x (overview):

1. (If upgrading to Windows or 64-bit Linux only) Upgrade the 4.5 PostgreSQL database to use the APM database schema before exporting it. For details, see Upgrading the 4.5 PostgreSQL database (see page 199).

2. Export the upgraded or existing database to a backup file. For details, see Exporting an APM database on PostgreSQL (see page 204).

3. On the target machine, install a new PostgreSQL database instance and the APM database schema with the main Introscope installer. For details, see Specifying the APM database (see page 70).

4. On the target machine, load the backup file to restore the prior database. For details, see Restoring a APM database from a backup file (PostgreSQL) (see page 206).

Note: If you are upgrading onto a 32-bit Linux machine, the restore script also upgrades the database.

Upgrading the 4.5 PostgreSQL from a CA Wily APM installation, one product at a time (overview)

If you choose to first upgrade Introscope and then upgrade Wily CEM later, there is a time lag in the APM database that you must reconcile. You can either merge the databases, or, if you haven’t used key Introscope features much, you can drop the new database and instead use the upgraded one. For more information, see Pros and cons of upgrading products one at a time (see page 150).

To upgrade a CA Wily APM installation one product at a time (overview):

1. Upgrade the Enterprise Managers and install a new PostgreSQL APM database (later referred to as DB-1). For details, see Installing Introscope main components (see page 65).

When installing the new database, specify the following:

■ In the Database Administration Settings window, enter the port number, PostgreSQL administrator user name and password for the new database.

■ In the Database Settings window, enter the new database name, user name, and password.



2. Upgrade the 4.5 PostgreSQL database (later referred to as DB-2) using the Introscope main installer or the upgrade script. For details, see Upgrading the 4.5 PostgreSQL database (see page 199).

3. Integrate the databases by one of the following methods:

■ Drop the data in the DB-1 database, and point all Enterprise Managers to the remaining database DB-2. If you have not yet used key Introscope features much, there is not much data in DB-1, so this is okay. For details, see Removing the APM database from PostgreSQL (see page 218).

■ Merge the data in the two databases, and point all Enterprise Managers to the merged database. For details, see Merging Introscope and Wily CEM databases during upgrade (see page 201).

Upgrading the 4.5 PostgreSQL database

If you are upgrading Wily CEM, at one point you will need to upgrade the database. You can either run the upgrade script, or use the installer to perform the upgrade. This section includes instructions for both options.

Note: This APM database upgrade script is not supported on Windows.

Note: If upgrading a APM database onto a new machine, you may upgrade the database instead by using the restore script, if desired. If you want to keep just the configuration data and not any defect data, you can run the database configuration scripts. For details, see Migrating the APM database (see page 196) and the Wily CEM Configuration and Administration Guide.

To upgrade the APM database with the Introscope main installer:

■ Run the Introscope installer main installer on your existing 4.5 TESS machine to upgrade the 4.5 PostgreSQL database schema.

When going through the installer, choose the following options to upgrade the existing database:

■ Database Only

■ In the Install Database or Choose Existing Database window, choose Upgrade database schema or create new database schema.

■ In the Database Administration Settings window, enter the port, PostgreSQL administrator username and password for the existing 4.5.x database.

■ In the Database Settings window, enter the existing 4.5.x database name, username, and password.

For details, see Specifying the APM database (see page 70).



To upgrade the APM database manually:

1. Navigate to the database-scripts directory for your operating system.

2. Open a command line, and run the following script for your operating system:

■ Linux: dbupgrade-postgres.sh

Note: This script is not supported on Windows.

Use the following syntax and arguments:

./dbupgrade.sh [dbinstalldir] [dbname] [dbuser] [dbpassword] [dbport]

[dbscriptVer <optional>]

Use the following arguments:

dbinstalldir

The directory location of the APM database.

If you didn’t change the defaults, then the location is as follows:

Linux: opt/database

dbname

The database instance name.

If you didn’t change the default, this is cemdb.

dbuser

The username for the database. If you didn’t change the default, this is admin.

Note: This is NOT the PostgreSQL administrator username.

dbpassword

The password for the database user specified.

dbport

The port on which the database communicates to the Enterprise Manager and other components. By default, this is 5432.

dbScriptVer

(Optional) This option is for use in the future and is not applicable at this time.



Merging Introscope and Wily CEM databases during upgrade

If you are upgrading your prior CA Wily APM installation by first upgrading Introscope and then later upgrading Wily CEM, you will need to merge the Introscope and Wily CEM databases at one point.

To combine a 9.x Introscope-only APM database with an 5.x upgraded Wily CEM-only APM database:

1. Verify that both the Wily CEM-only and Introscope-only APM databases have the correct schema.



■ Windows: StaggeredAPMUpgradeExport.bat

■ Linux: StaggeredAPMUpgradeExport.sh

Note: Run this export script on the database that has the Introscope-only data.


[StaggeredAPMUpgradeExport.bat| ./StaggeredAPMUPgradeExport.sh] [dbinstalldir]

[dbbakfile] [dbname] [dbuser] [dbpassword] [dbport <optional>]

Include the following arguments:

dbinstalldir



Linux: opt/database

Windows: <EM_Home>\database

dbbakfile

The directory location and name of the database backup file.

dbname

The database instance name. If you didn’t change the default, this is cemdb.

dbuser



dbpassword


dbport

(Optional) The port on which the database communicates to the Enterprise Manager and other components. By default, this is 5432.



When the script finishes, the database export file is in the specified location. This is the file you will import into the other Wily CEM-only database.

4. Run the following script for your operating system to import the exported Introscope-only data into the Wily CEM-only database:

■ Windows: StaggeredAPMUpgradeImport.bat

■ Linux: StaggeredAPMUpgradeImport.sh


[StaggeredAPMUpgradeImport.bat| ./StaggeredAPMUpgradeImport.sh] [dbinstalldir]

[dbbakfile] [dbname] [dbuser] [dbpassword] [dbport <optional>]


dbinstalldir



Linux: opt/database


dbbakfile


dbname


dbuser



dbpassword


dbport

(Optional) The port on which the database communicates to the Enterprise Manager and other components. By default, this is 5432.

If any table rows could not get copied over, the import script displays error messages.



Upgrading PostgreSQL

If you have your APM database on PostgreSQL, when you upgrade to CA Wily APM version 9.0.6 you need to also upgrade PostgreSQL to a newer version (8.4). This upgrade requires you uninstall the previous version of PostgreSQL before you install the new version.

To upgrade PostgreSQL to 8.4:

1. Backup your existing database. For details, see Exporting an APM database on PostgreSQL (see page 204).

2. Remove the APM database schema. For details, see Removing the APM database from PostgreSQL (see page 218).

3. Uninstall PostgreSQL. For details, see Uninstalling PostgreSQL (see page 220).

4. Run the installer to install a new database. This option includes installing the newer version of PostgreSQL. For details, see Specifying the APM database during upgrade (see page 226).

You can upgrade the Enterprise Manager at the same time, if the Enterprise Manager is on the same machine as the APM database. This is often the case if you have just Introscope installed .

5. Using the backup file, restore the database into the new installation. For details, see Restoring an APM database from a backup file (PostgreSQL) (see page 206).

Note: If you previously upgraded the PostgreSQL database on Linux from a version prior to 4.5 (Wily CEM) and you are installing PostgreSQL as a non-root user, you must manually install the ODBC files after upgrading PostgreSQL. CA Wily APM uses the ODBC files to connect to the database. For details, see Configuring PostgreSQL on Linux or Solaris (see page 216).

Exporting and restoring the APM database



A few of the upgrade scenarios involve the tasks of exporting the APM database to a backup file and later restoring the database from the backup file. Or your business needs involve changes to your deployment architecture, you may need to move the APM database to another machine or database platform.

This section includes details for exporting and restoring the APM database on PostgreSQL to and from a backup file.

Note: If you install the APM database schema as an Oracle database, however, you must use the backup and restore programs provided by Oracle for the version of the database you are using. For example, you can configure the Oracle database for automatic backups using the Database Configuration Assistant (dbca), schedule regular or ad hoc backups through the Oracle Enterprise Manager Database Control, or manage both backup and recovery operations using the Oracle Recovery Manager (RMAN) client. The backup and restore utilities described in this section only apply when the APM database is a PostgreSQL database.

Exporting an APM database on PostgreSQL

If you are upgrading Wily CEM to a new machine, at one point you will need to manually export the APM database. Exporting a database creates a database backup file. You can then move the database to a new machine by loading the backup file using a restore utility.

If the APM database is a PostgreSQL database, you can use the dbbackup-postgres and dbrestore-postgres scripts to back up and restore the APM database. For example, you can use dbbackup-postgres.bat (on Windows) or dbbackup-postgres.sh (on Linux) with the appropriate command line options to back up an existing database before moving the database to a new machine.

Note: This section applies only to PostgreSQL databases. For details on backing up and restoring an APM database on Oracle, see Exporting and restoring the APM database (see page 204).

The backup utility creates a .backup file of the APM database. You can customize the backup filename, as long as it has a .backup filename suffix. If you do not specify a filename, the script creates a backup file with the name of the database.

To create a backup file of the APM database:

1. Ensure the machine on which you’re running the database script has PostgreSQL installed. If desired, you can run the script on a remote machine, as long as that remote machine also has PostgreSQL installed.

2. Navigate to the database-scripts directory for your operating system. For details, see Migrating the APM database (see page 196).




■ Windows: dbbackup-postgres.bat

■ Linux: dbbackup-postgres.sh


dbbackup-postgres.bat|./dbbackup-postgres.sh [dbserverhostip] [dbinstalldir]

[dbname] [dbuser] [dbpassword] [dbport] [dbbackupdir] [outputfile <optional>]

dbserverhostIP

The IP address of the machine hosting the database. If you are running it on the machine directly, you can specify localhost.

dbinstalldir


On Linux, this must be the shortened version of the path if there are spaces in it. For Linux, an example is the directory /root/Introscope Enterprise Manager can be represented as /root/Introscope\ Enterprise\ Manager.


Linux: opt/database


dbname

The APM database schema name. If you didn’t change the default, this is cemdb.

dbuser

The user name for the database. If you didn’t change the default, this is admin.

Note: This is NOT the PostgreSQL administrator user name.

dbpassword

The password for the specified database user.

dbport


dbbackupdir

The directory location where you want to save the database backup file. You can specify a full or relative path to the directory. For Linux, you must escape any blank spaces in the path name. For example, if the backup directory is /root/Introscope Enterprise Manager you must specify the path as /root/Introscope\ Enterprise\ Manager.



outputfile

(Optional) The name of the database backup file. If you don’t specify this parameter, the script generates a file with named dbname.backup, with the database name supplied.

The following is an example that generates a cemdb.backup file in the /opt/database/backups directory:

sh dbbackup-postgres.sh 127.0.0.1 /opt/database cemdb admin quality 5432

./backups

4. When the backup process completes, a confirmation message displays.

If the script encounters errors, here are common explanations:

■ The database name is incorrect.

■ PostgreSQL is not installed.

■ The location of the APM database is incorrect.

Restoring an APM database from a backup file (PostgreSQL)

If you are upgrading Wily CEM to a new, parallel machine, at one point you will need to manually restore the APM database. When restoring a database, you create a new database from the backup file and the new database has the username and password that you specify when invoking the restore script.

Note: This section applies only to PostgreSQL databases. For details on backing up and restoring an APM database on Oracle, see Exporting and restoring the APM database (see page 204).

WARNING: The restore function destroys the specified database if it already exists before it creates a new database with the name specified.



Note: If the database is on a UNIX machine, the restore process also upgrades the database.

Note: The restore script is not supported on Windows if you are restoring a database version 4.5.x or earlier.

Note: The amount of time it takes to restore a database is directly related to the database size. Large databases take longer to restore, and restore times also depend on machine capacity and memory. For example, a 1 GB database could take 1 to 2 hours to restore, depending on machine resources.

Note: If you restore a PostgreSQL database on a 64-bit Linux machine, you may get an error message like the one below. The error message occurs if plpsql is already installed on the machine; you can safely ignore this error message.

pg_restore: [archiver (db)] Error while PROCESSING TOC:

pg_restore: [archiver (db)] Error from TOC entry 909; 2612 16386 PROCEDURAL LANGUAGE

plpgsql postgres

pg_restore: [archiver (db)] could not execute query: ERROR: language "plpgsql" already

exists

Command was:

CREATE PROCEDURAL LANGUAGE plpgsql;

To restore the APM database from a backup file:

1. Ensure that no users are connected to the database. You cannot restore the database if users are connected to it.


Note: If you are restoring a PostgreSQL database on Solaris, navigate to the following directory instead:

<APM_Db_Home>/postgres/8.4-community/


■ Windows: dbrestore-postgres.bat

■ Linux/Solaris: dbrestore-postgres.sh


[dbrestore-postgres.bat|./dbrestore-postgres.sh]

[dbserverhostip] [dbinstalldir] [dbserviceuser]

[dbservicepassword] [dbname] [dbuser] [dbpassword] [dbport]

[backupfile]


dbserverhostIP




dbinstalldir


This must be the shortened version of the path if there are spaces in it. An example of this is c:\progra~1\cawily~1. If you didn’t change the defaults, then the location is as follows:

Linux: opt/database


dbserviceuser

The PostgreSQL administrator username. By default, this is postgres.

dbservicepassword

The PostgreSQL administrator password.

dbname


dbuser



dbpassword

The password for the database user.

dbport


backupfile


The following is an example that restores a cemdb.backup file from the /opt/database/backups directory:

sh dbrestore-postgres.sh 127.0.0.1 /opt/database postgres C@wilyapm90 cemdb admin quality 5432 ./backups/cemdb.backup

4. When the restore process completes, a confirmation message displays.

If you encounter errors:

■ The most common error is that users are still connected to the database. You can restart the PostgreSQL server to bump off errant connections.

■ If you get an error that says that database does not exist, this is okay. This means that the script is being used to create a new database in the process.

Moving the APM database to a different machine


Moving the APM database to a different machine

You may need to move the APM database to a different machine for scalability reasons, or as part of your unique upgrade path. The overview instructions below apply to APM databases that are either newly installed or have already been upgraded.

Note: This topic applies to PostgreSQL databases only. For information about doing backup and restore operations on an Oracle database, see Exporting and restoring the APM database (see page 204).

To move the APM database to a different machine (overview):

1. Run the Introscope main installer to upgrade the APM database, if you haven’t already upgraded the 4.5 PostgreSQL database. For details, see Upgrading the 4.5 PostgreSQL database (see page 199).

2. Export the database to a database backup file. For details, see Exporting an APM database on PostgreSQL (see page 204).

3. On the new machine, run the Introscope main installer to install a new APM database using the following options:

■ For the Install Set, click Database Only.

■ Choose an installation directory that is not the Enterprise Manager home directory.

■ For the database type, select PostgreSQL.

■ Select the Install database option.

■ Specify the directory name to use for the APM database schema.

■ Enter the port number, PostgreSQL administrator user name and password for the new database instance.

■ Enter the new APM database name, a database user name, and a password.


4. Populate the new, empty APM database with the contents of the backup file you created in step 2. For details, see Restoring a APM database from a backup file (PostgreSQL) (see page 206).

5. Connect all existing Enterprise Managers to the new database location. For details, see Specifying APM database settings after installation (see page 214).

Moving the APM database to another operating system


Moving the APM database to another operating system

In some cases, you may want to move the APM database from one computer to another or from one platform to another as part of your upgrade process. For example, you may want to move the APM database from PostgreSQL on Windows or Linux to PostgreSQL on Solaris. To move the database from one platform to another, you must export the business transaction and configuration data from a source database then import the business transaction and configuration data into a the target database on the new platform. Alternatively, you can use the dbbackup-postgres and dbrestore-postgres utilities to create a complete backup of an existing PostgreSQL database and restore the database on a new computer.

For more information about exporting and importing data from a PostgreSQL database or using the dbbackup-postgres and dbrestore-postgres utilities, see the Wily CEM Configuration and Administration Guide. For information about migrating data from a PostgreSQL database to an Oracle database, see Migrate data from a PostgreSQL database to an Oracle database (see page 210).

Migrating data from a PostgreSQL database to an Oracle database

If you are upgrading from CA Wily APM 9.0, the APM database schema is a PostgreSQL database. After upgrading, you can choose to migrate the APM database to Oracle, if desired. For example, if your organization is standardized on Oracle as a database platform, you may need to migrate the APM database to Oracle to enable production-level monitoring. If you want to move your existing data from a source database in PostgreSQL to a target database in Oracle, you can use the CA Wily APM migration utility to specify the source and target databases.

To migrate from a PostgreSQL database to an Oracle database

1. Plan and prepare for the upgrade by reviewing the upgrade scenarios and upgrade paths.

2. Create a backup copy of all components.

3. Upgrade the Enterprise Manager and APM database using the interactive or silent installer.

4. Navigate to the <EM_Home>/install/migration directory.



5. Run the migration.bat or migration.sh script as appropriate for your operating environment using the following arguments:

migration -srcDatabaseName <database_name> -srcDatabaseType <database_type>

-srcHost <hostname> -srcPort <port_number> -srcUser <username> -srcPassword

<password> -tgtDatabaseName <datatargetname> -tgtDatabaseType <database_type>

-tgtHost <hostname> -tgtPort <port_number> -tgtUser <username> -tgtPassword

<password>

srcDatabaseName

Specifies the name of the source database. If you used the default settings, the database name is cemdb.

srcDatabaseType

Specifies the type of the source database. In this release, the only valid value is postgres.

srcHost

Specifies the host name or IP address of the database server for the source database.

srcPort

Specifies the port number for connecting to the source database. If you used the default settings, the port is 5432.

srcUser

Specifies the database user name for the source database. If you used the default settings, the database user name is admin.

srcPassword

Specifies the password for the database user in the source database.

tgtDatabaseName

Specifies the name or service account identifier of the target database. For an Oracle database, the name should be the unique system identifier (SID) for the target database.

tgtDatabaseType

Specifies the type of the target database. In this release, the only valid value is oracle.

tgtHost

Specifies the host name or IP address of the database server for the target database.

tgtPort

Specifies the port number for connecting to the target database. If you used the default settings, the port is 1521.



tgtUser

Specifies the database user name for the target database.

tgtPassword

Specifies the password for the database user in the target database.

Note: All arguments are case-sensitive and required to run the migration tool.

For example, to migrate data from the PostgreSQL database cemdb to an Oracle database with the SID orcl with the schema owner of apmdb on a Linux computer, the command line might be similar to the following:

./migration.sh -srcDatabaseName cemdb -srcDatabaseType postgres -srcHost nyc16

-srcPort 5432 -srcUser admin -srcPassword quality -tgtDatabaseName orcl

-tgtDatabaseType oracle -tgtHost nyc23 -tgtPort 1521 -tgtUser apmdb -tgtPassword

cent3R

6. Check the migration.log file in the logs directory to verify the schema has been migrated successfully or to troubleshoot problems with the migration. For example, navigate to the <EM_Home>/install/migration/logs directory.

Note: You can modify the location of the migration.log file by modifying the log4j.appender.logfile.File property in the <EM_Home>/install/migration/log4j-migration.properties file. For more information about customizing migration and log file properties, see Customizing migration properties (see page 212).

Customizing migration properties

If you are migrating data from PostgreSQL to Oracle, there are two properties files that can be used to customize the operation of the migration utility:

■ migration.properties

■ log4j-migration.properties



The migration.properties file provides properties you can use to control the copy and insertion of database objects during migration to optimize processing for your environment. In most cases, the default values for the properties should provide fast and efficient data migration without overloading memory. Depending on the memory constraints of your environment, however, you may need to modify the following properties to customize data migration:

migration.fetchsize

Controls the number of records retrieved from the source database and held in memory at a time. The value should be an integer greater than zero. The default value is 1000. For example:

migration.fetchsize=1000

migration.batchsize

Controls the number of records inserted into the target database in each batch. The value should be an integer greater than zero. The default value is 3000. For example:

migration.batchsize=3000

migration.queuesize

Controls the size of the queue that holds the records to be migrated in a single thread. As records are retrieved from the source database, they are placed in this queue to be read for batch insert into the target database. The value should be an integer greater than zero. The default value is 10000. For example:

migration.queuesize=10000

migration.parallel.table.number

Controls the number of parallel table migrations. Each table is migrated using a single thread. The thread retrieves the records for a table from the source database according to the value set for the migration.fetchsize property and places the records in the queue up to the value set for the migration.queuesize property. The records are read from the queue and inserted in batches defined by the value of migration.batchsize property. This property controls the number of threads in use at a time. The value should be an integer greater than 0. The default value is 5.

For example:

migration.parallel.table.number=5

The log4j-migration.properties file provides properties you can use to control the logging activities during migration. In most cases, you should use the default values for the properties unless you want to change the log file name or location, the maximum file size, or the maximum number of backup copies.

log4j.appender.logfile.File

Specifies the relative path to the log file for recording information about the operations performed during the data migration. For example:

log4j.appender.logfile.File=logs/migration.log

Changing and verifying APM database settings


log4j.appender.logfile.MaxFileSize

Specifies the maximum size of the log file in KB. For example:

log4j.appender.logfile.MaxFileSize=2048KB

log4j.appender.logfile.MaxBackupIndex

Specifies the maximum number of backup copies to save. For example:

log4j.appender.logfile.MaxBackupIndex=3

Running more than one instance of the migration script

You should not run the migration utility more than once with the same target database. If the migration fails, you can restart the program, but you should not run more than one instance of the migration for any source and target database. After starting a migration, you should ensure that any running instance of the program has completed processing before starting a new migration operation. Running more than one instance of the migration utility generates errors and may prevent the APM database from being migrated successfully.


In some cases, after you install the APM database you may need to change or verify the database settings after the installation completes. This section includes information on changing APM database connection settings and passwords post-installation, in addition to how to verify the APM database schema version.

Specifying APM database settings after installation

In most cases, you specify connection information for the APM database when you run the installer. However, if you are unable to specify this information in the installer, you can configure the connection to the APM database manually after the install completes.

For example, if a remote server hosts the APM database and becomes unavailable so that the attempt to connect fails, you can continue with the installation and configure the connection manually after completing the installation.

To configure the connection to the APM database after installation:

1. Open the tess-db-cfg.xml file for editing. The file is located in the following directory, depending on your operating system:

■ Windows: <EM_home>\config\

■ UNIX: <EM_home>/rootFiles/config/



2. For the hibernate.connection.url property, replace the current settings with the database hostname (or IP address), port, and database name.

For example:

<property

name="hibernate.connection.url">jdbc:postgresql://127.0.0.1:5432/cemdb</prope

rty>

3. For the hibernate.connection.username property, specify the database user name.

Note: This is not the PostgreSQL administrator user name.

4. For the hibernate.connection.password property, specify the database user password in plain text.

5. For the plainTextPasswords property, change the setting to true. This allows you to enter the password in plain text.

When the Enterprise Manager starts, Introscope sets the plainTextPasswords property back to false and encrypts the password.

Changing the default passwords for a PostgreSQL database instance

After you install a new APM database, particularly if you did so with default configurations, for security reasons you should change the passwords for the following:

■ PostgreSQL administrator account (PostgreSQL)

■ postgres service user account (operating system)

Refer to your operating system’s documentation for details on changing the service user account password. For additional information about PostgreSQL, consult the documentation installed along with PostgreSQL.

Tip: You can also use pgAdmin to access the PostgreSQL database, change passwords, and so forth.

For other passwords that should be changed after installation, see Post-install password security (see page 54).

To change the PostgreSQL administrator account password:

1. Connect to the database with psql:

■ On Windows, click Start > Programs > PostgreSQL 8.3 > psql to ‘postgres’.

■ On Linux: enter the following:

psql -U username -d databasename

A command line window opens, prompting for your password.

Configuring PostgreSQL on Linux or Solaris


2. Enter the PostgreSQL Administrator password that you specified during installation.

If the password is correct, a welcome message and some command information displays, and the command prompt changes to "postgres=#".

3. Enter the following:

ALTER USER postgres WITH PASSWORD ‘newpassword’;

Where newpassword is the new password. This password must comply with your organization’s password security requirements.

4. Press Enter to commit the change.

If the change is successful, ALTER ROLE displays as a confirmation message.

Verifying the schema version of the APM database

If you need to verify that an APM database has the correct schema version, run the following SQL statement using a tool such as pgAdmin or psql for PostgreSQL or isql or SQL*Plus for Oracle:

SELECT ts_db_versions FROM ts_domains

The SQL statement should return a value of 9.0.5.0 or later, depending on the version of the APM database schema you have installed. If you are using an older version of Wily CEM, such as 4.5, the return value would reflect the version of Wily CEM you have installed.

Configuring PostgreSQL on Linux or Solaris

If you have installed PostgreSQL on Linux or Solaris using a non-root user account, there are a few additional configurations that you need to have your system administrator do after you have installed PostgreSQL.

Linux system administrator tasks

1. Configure the <APM_Db_Home>/bin/postgresql-8.4.5 startup script to run automatically after reboot.

2. Copy the postgresql-8.4.5 script to the init.d folder and then run the following:

chkconfig –add postgresql-8.4.5

3. Then set levels 2,3,4,5 to on.

4. Manually install ODBC files. See below for details.

Troubleshooting the non-root PostgreSQL installation on Solaris


To manually install ODBC files on Linux for non-root installations of PostgreSQL:

1. Use the template file in <APM_Db_Home>/install/database-scripts/unix to create your <tsdnfile>.

2. Edit the file with your database settings.

3. Run the following command:

■ odbcinst -l -s -l -f <tsndfile>

If there are no error statements and the prompt appears, the command ran successfully. The odbc.ini file should also be in the /etc folder.

Solaris system administrator tasks

■ Configure the PostgreSQL startup scripts to run automatically after reboot. These scripts are:

<APM_Db_Home>/bin/postgresql.xml

<APM_Db_Home>/bin/postgresql

■ Add services using the svcadmn feature in Solaris 10.

■ If the installation failed with a shared memory error, set the shared memory value higher. For details, see Troubleshooting the non-root PostgreSQL installation on Solaris.

Troubleshooting the non-root PostgreSQL installation on Solaris

If the non-root installation of PostgreSQL on Solaris failed due to insufficient shared memory, have your Solaris system administrator run the following command:

projadd -U postgres -K "project.max-shm-memory=(priv,7000MB,deny)" user.postgres

Uninstalling APM database software or data

If you decide to remove the Enterprise Manager and the APM database from a computer, you can use the Uninstall_Introscope program appropriate for your operating environment. The Uninstall_Introscope program removes most of the files for the Enterprise Manager and the database automatically.

There are some cases when you need to separately remove the APM database schema: in some upgrade scenarios, and when uninstalling an Introscope or CA Wily APM installation that uses an APM database on Oracle.

When upgrading a CA Wily APM or Introscope 9.x installation and the APM database is on PostgreSQL, you need to first uninstall the existing PostgreSQL installation before installing the updated PostgreSQL.



Removing the APM database schema from PostgreSQL

If you are upgrading Wily CEM to a new machine, at one point you will need to manually remove the APM database. (This is also called dropping the database.)

WARNING: Dropping a database involves removing all data and schema.

To remove the APM database contents:


2. Open a command prompt, and run the following script for your operating system:

■ Windows: dropdb-postgres.bat

■ Linux: dropdb-postgres.sh


[dropdb-postgres.bat| ./dropdb-postgres.sh] [dbserverhostip] [dbinstalldir]

[dbname] [dbserviceuser] [dbservicepwd] [dbport <optional>]


dbserverhostIP


dbinstalldir



Linux: opt/database


dbname

The database instance name.

If you didn’t change the default, this is cemdb.

dbserviceuser



dbservicepassword


dbport




Removing the APM database schema from Oracle

In some cases, you may need to manually remove APM tables, views, indexes, and sequences. For example, if the APM database is an Oracle database schema, you must manually remove objects from the database after you have run the Uninstall_Introscope program. You can use the Oracle Enterprise Manager Database Control or SQL statements to manually remove tables, views, and sequences associated with the APM database schema, or use the dbdrop program to remove all of the APM objects from the Oracle database.

Note: To remove the APM database from PostgreSQL, you can use the dropdb-postgres.bat or dropb-postgres.sh program as described in WYAPM--Removing the APM database from PostgreSQL (see page 218). You can only use the dbdrop.bat or dbdrop.sh program to remove the APM database schema from an Oracle database.

To remove all APM database schema objects from an Oracle database

1. Navigate to the <EM_Home>/install/database-scripts directory for your operating system. For example:

cd /home/Introscope9.0.5.0/install/database-scripts/unix

2. Open a command or terminal window and run the dbdrop.bat on Windows or dbdrop.sh on other platforms with the following arguments:

dbDrop -databaseName <database_name> -databaseType <database_type> -host

<hostname> -password <password> -port <port_number> -releaseVersion <version>

-scriptsDir <dir> -user <user_name>

databaseName

Specifies the Oracle system identifier (SID) or service name for APM database schema.

databaseType

Specifies the type of database. You must set this argument to oracle because you can only use the dbdrop program for Oracle databases in this release.

host

Specifies the host name or IP address for the computer that hosts the Oracle database instance.

password

Specifies the password for database user associated with the APM database schema.

port

Specifies the port number for connecting to the Oracle database instance. The default port number for the Oracle Listener service is 1521.



releaseVersion

Specifies the release version information for the APM database schema to be removed, for example, 9.0.5 or 5.0.0.

scriptsDir

Specifies the directory for locating database-specific SQL scripts. For Oracle database, the default directory for the SQL scripts is <EM_Home>/install/oracle.

user

Specifies the user name for database user associated with the APM database schema.

For example, to run the dbdrop program on Linux to remove an Oracle schema, you would use a command line similar to the following:

./dbdrop.sh -databaseName arcade -databaseType oracle -host sfqa07.org -password

mypwd -port 1521 -releaseVersion 9.0.5 -scriptsDir

/apps/Introscope9.0.5.0/install/oracle -user apmdba

Uninstalling PostgreSQL

When you upgrade an APM database on PostgreSQL for CA Wily APM 9.0.6, you need to uninstall your existing PostgreSQL installation before installing the updated version of PostgreSQL.

You may also need to uninstall PostgreSQL if you have moved the APM database onto another machine and you need to remove unnecessary files from the old machine.

To uninstall PostgreSQL on Windows, use the Windows Control Panel to uninstall the program.

To uninstall PostgreSQL on Linux or Solaris:

1. If you are uninstalling PostgreSQL from a machine that has pre-9.x Introscope or Wily CEM , navigate to the following directory:

cd /etc/wily/cem/tess/install/database-scripts

If uninstalling PostgreSQL from a machine that has Introscope or APM 9.x installed, navigate to the following directory:

cd <APM_DB_Home>/install/database-scripts/unix

2. In this directory, run the following command to remove the PostgreSQL database schema:

sh dropdb-postgres.sh

The following message displays:

Dropping database "cemdb"




cd /var/lib

4. In this directory, run the following command to uninstall PostgreSQL:

rm -rf pgsql


Chapter 12: Upgrading Introscope

This chapter describes options and considerations for upgrading Introscope.

The Introscope 9.x installer upgrades Introscope versions 8.0, 8.1, and 8.2.

For Introscope versions prior to 8.0, use the 8.x installer to first upgrade to 8.x, and then upgrade to 9.x.

For upgrade assistance, please contact CA Support.

WARNING: The upgrade procedure is not reversible. CA Technologies recommends creating a full backup of your Introscope installation before initiating an upgrade.

IMPORTANT! Before installing or upgrading CA Wily APM, CA Wily Introscope, and Wily CEM, you should read the CA Wily APM Known Issues and the CA Wily APM ReadMe (or Introscope ReadMe if you have an Introscope only implementation). The ReadMe files are a part of your downloaded product archive; the Known Issues document is available only on the product download site, at the same level as your product download.


Upgrading Enterprise Managers and databases (GUI or console modes) (see page 223) About silent mode upgrades (see page 228) Upgrading other Introscope elements (see page 230) Completing the upgrade (see page 233)

Upgrading Enterprise Managers and databases (GUI or console modes)

You can upgrade Enterprise Manager cluster members as well as standalone Enterprise Managers—simply run the Enterprise Manager upgrade on each Enterprise Manager in the cluster.

Follow these instructions to automatically upgrade Introscope to the latest 9.x in GUI or console mode.

Note: If you are upgrading an APM database using PostgreSQL to 9.0.6 or later, you need to upgrade your PostgreSQL installation. For details, see Upgrading PostgreSQL (see page 203).

For details on upgrading in silent mode, see About silent mode upgrades (see page 228).



When you upgrade CA Wily APM or Introscope, you can upgrade the Enterprise Manager at the same time as the APM database if you had installed them at the same time. The installer determines if this is the case. If you installed the APM database at a different time or on a separate machine from the Enterprise Manager, run the installer to just upgrade the APM database, and run the installer separately to upgrade the Enterprise Manager.

If you are upgrading from an Introscope-only deployment to CA Wily APM, ensure that you locate the APM database on a machine separate from any Enterprise Manager Collector.

Upgrading Enterprise Managers and databases involves the following (an overview):

1. Starting the installer and specifying the install set (see page 224)

2. Specifying the installation location, external components, and licenses (see page 225)

3. Renaming Windows Service names (see page 225)

4. Specifying external components and license (see page 226)

5. Specifying the APM database during upgrade (see page 226)

6. Confirming the upgrade (see page 227)

Starting the installer and specifying the install set

1. Start the Introscope installer, and proceed through the Introduction and CA End User License Agreement windows. For details, see Installing Introscope main components (see page 65).

2. In the Choose Install Set window, choose the type of installation—Complete, Minimal, Database Only, or Custom—and click Next.

3. If you selected Custom, the Choose Product Components screen displays. Select the product components you want to install, and click Next to continue.

Next, go to Specifying the installation location, external components, and licenses (see page 225).



Specifying the upgrade location, external components, and licenses

These steps continue from Starting the installer and specifying the install set (see page 224).

Note: If you are running the installer to upgrade the database schema but not other components, you should specify the database installation directory rather than the <EM_Home> directory when you are prompted for the directory. You should only specify the existing <EM_Home> directory when you are upgrading the Enterprise Manager and other components. If you choose to upgrade the database schema without other components, you must specify valid credentials for connecting to the database. The installation directory for an APM database-only upgrade is only used to store installation-related log files and scripts. You can use any accessible directory.

Note: If you specify the existing <EM_Home> directory when you select the Database Only upgrade option, you will not be able to use the Uninstall_Introscope program to remove the Enterprise Manager and other components from the local computer.

1. When the installer prompts for an install directory, specify the directory of the Enterprise Manager to upgrade.

When you specify a directory containing an existing instance of Introscope, the installer offers to upgrade it:

Select Upgrade existing installation and click Next.

2. The installer asks if you want to rename the existing Introscope home directory.

Rename the directory, or click Browse... to choose an existing directory. The installer will create a directory if it does not exist.


Next, go to Renaming Windows Service names (see page 225).

Renaming Windows Service names

These steps continue from Specifying the installation location, external components, and licenses (see page 225).

■ On Windows platforms only, if the Enterprise Manager and/or WebView were configured to run as Windows services during the original install, the installer prompts you to rename service and display names.

You can designate new service or display names, or accept the current names. If you rename them here, the installer handles the renaming process.

Rename, or accept old names, and click Next.

Next, go to Specifying external components and license (see page 226).



Specifying external components and license

These steps continue from Renaming Windows Service names (see page 225).

1. The installer asks for the location of the External Components Package (see External component packages (see page 51)).



2. The installer asks you to accept the terms of the End User License Agreement (EULA). Click I accept the terms of the License Agreement.


Next, go to Specifying the APM database during upgrade (see page 226).

Specifying the APM database during upgrade

These steps continue from Specifying external components and license (see page 226).

The applications you upgrade and the path by which you upgrade determine your method of specifying the APM database during upgrade. The table below lists the selections to specify in the installer for each upgrade scenario.

upgrade scenario selections to make

Introscope upgrade: upgrading or installing MOM

install new APM database

Introscope upgrade: upgrading or installing a Collector

connect to an existing APM database

CA Wily APM upgrade: upgrading one application at a time


upgrade existing APM database

CA Wily APM upgrade: upgrade both applications at the same time


Wily CEM upgrade: same machines upgrade existing APM database

Wily CEM upgrade: new machines, Windows or 64-bit Linux


Wily CEM upgrade: new machines, 32-bit Linux


Introscope or CA Wily APM upgrade: from 9.x to 9.0.6 or later with APM database using PostgreSQL




upgrade scenario selections to make

Introscope or CA Wily APM upgrade: from 9.0.5 to 9.0.6 or later with APM database using Oracle


Note: If you are upgrading a 9.x APM database on PostgreSQL, be sure to first backup the database and uninstall the existing PostgreSQL. For details, see Upgrading PostgreSQL (see page 203).


Next, go to Confirming the upgrade (see page 227).

Confirming the upgrade

These steps continue from Specifying the APM database during upgrade (see page 226).

1. The installer prompts you to confirm you want to proceed with the upgrade.

Click Yes, Upgrade or Cancel & Exit.

2. Introscope displays a message dialog to ensure that Introscope is shut down, that all Introscope services are stopped, and that no Introscope files or folders are in use by any running process.

Confirm that Introscope and its related services and files are shut down and stopped, then click Introscope Is Shut Down, Upgrade Now.

The installer installs the necessary files.

3. When the upgrade installation is complete, the Install Complete window opens. Click Done to complete the installation.

Note: The installer upgrades the Enterprise Manager only in the directory you specified for the upgrade, so you must run the upgrade once for each Enterprise Manager in a cluster. For example, if you have two collectors in a cluster, run the upgrade three times—once on the MOM and once each on each collector.

After the upgrade process is complete, see Completing the upgrade (see page 233).

Note: If you use Wily CEM, be sure to verify communication between the TIMs and the upgraded Enterprise Manager(s) and enable the TIMs. For details, see Verifying communication between the TIM and Enterprise Manager (see page 146).

About silent mode upgrades



You can upgrade some Introscope components in silent mode. In this method, the installer runs from a command line and takes input from a response file. This makes multiple upgrades of Introscope easy.

Silent mode is supported on all platforms, and runs in the background with no feedback. See Installing Introscope in silent mode (see page 85) to review the information required for installation.

After installation, you can check the results in the installer logs.

For additional upgrade tasks, see Preparing for Introscope-related upgrades (see page 153).

Here is an overview of the upgrade process in silent mode:

1. Edit the response file. See Using a response file (see page 86), and Editing the upgrade response file, below (see page 228).

2. Download and edit the necessary external files. See Downloading and editing external files (see page 87).

3. Run the installer from the command line, pointing to the edited response file. See Launching silent mode installers (see page 118).

Before proceeding, review the information in Preparing for silent mode installation (see page 85).

Editing the upgrade response file

Below is a summary of the changes to make to the installer response file when upgrading in silent mode. For details on specific silent mode settings, see Silent mode installation settings (see page 87).

To edit the installer response file:

1. In the General Settings section of the response file, set the following properties:

a. USER_INSTALL_DIR to your existing Introscope 8.0x/9.x directory.

IMPORTANT! If the directory you designate does not contain an upgradable Introscope 8.x installation, the installer will perform a full installation, overwriting any files that are not eligible for the upgrade (for example, a 6.x installation or a 7.1 Workstation-only installation.) To review the upgrade requirements, see What to do before upgrading Introscope (see page 156).



b. externalComponentPackage property with the location of the current External Components Package. For details, see Downloading and editing external files.

c. eulaFile property with the location of the End User License Agreement (EULA) file, eula.txt.

IMPORTANT!: After you finish editing the response file, you edit the eula.txt file itself to affirm acceptance of the EULA; see Editing the eula.txt and ca-eula.txt files (see page 87). The upgrade will not proceed unless the eula.txt file is edited.

2. In the Upgrade Settings section of the response file, set the following properties:

a. shouldUpgrade=true

b. (Optional) uncomment the upgradedInstallDir property and specify a new value. This indicates the installer should rename the installation directory during the upgrade.

3. If the Enterprise Manager you are upgrading is a collector, in the Enterprise Manager Clustering Settings section of the response file, set the following properties:

shouldClusterEm=true

emClusterRole=Collector

the emClusterRole value is case sensitive.

4. (Optional) In the Windows Service Settings section, change Windows service names and display names, if desired, to:

a. shouldConfigEmAsService=true

b. emAsServiceName and emAsServiceDisplayName to their new values

5. (Optional) In the WebView as Windows Service Settings section, change Windows service names and display names for WebView, if desired, to:

a. shouldConfigWVAsService=true

b. wvAsServiceName and wvAsServiceDisplayName to their new values

Upgrading other Introscope elements


6. Specify database settings as appropriate:

For information on these properties and settings, see APM Database Settings (see page 99).

a. If you are using an existing database, specify the following properties:

■ dbHost

■ dbPort

■ dbName

■ dbUser

■ dbPassword

■ validateDatabase=true

■ upgradeSchema=true

b. If you installing a new database, also specify the following properties:

■ databaseDir

■ dbAdminUser

■ dbAdminPassword

7. Specify settings in the following sections as needed, depending on what components you are upgrading:

■ Enterprise Manager

■ WebView

■ ProbeBuilder

8. Save your changes to the response file and exit the editor.

After the upgrade process is complete, see Completing the upgrade (see page 233).


This section contains information on upgrading the Introscope Workstation, some general information about upgrading agents, PowerPacks, and extensions.

Note: If you have upgraded to a localized version of Introscope or CA Wily APM, be sure to copy the localized dashboards (.JAR files) from

<EM_Home>\config\modules-upgrade<version>

to

<EM_Home>\config\modules.



Upgrading the Workstation

If you use the Java Web Start Workstation installation in your environment, your Workstations automatically upgrade the first time they connect to a 9.0 Enterprise Manager.

If you use standalone Introscope Workstations, you must uninstall your Introscope 8.x Workstations and perform a fresh 9.0 Workstation installation.

Upgrading the bytecode, agents, and platform monitors

If you plan to use 9.0 agents, you must instrument your bytecode with the appropriate version 9.0 tool.

Note: This section includes general recommendations about upgrading agents. For more details, refer to the Introscope Java Agent Guide and Introscope .NET Agent Guide.

To upgrade the bytecode:

1. Shut down the managed application(s).

2. Instrument your code again, depending on your method:

■ If code was instrumented with the ProbeBuilder Wizard or the ProbeBuilder command-line interface, run the 9.0 version of the appropriate program.

■ If code was instrumented dynamically with AutoProbe, remove the previous version of ProbeBuilder.jar and any references to it on classpaths. The 9.0 ProbeBuilder.jar file is found automatically and should not be referenced on any classpath.

3. If you use JVM ProbeBuilder, generate and run a new connector, as described in the Introscope Java Agent Guide.

To upgrade to 9.0 agents and platform monitors:

1. Shut down the managed application(s).

2. Replace the Agent.jar file in each 8.x installation with the 9.0 Agent.jar file.

3. Remove the platform monitor files from the previous installation.

Platform monitor files are installed with the Introscope agent installer, in the <Appserver_Home>/wily/ext directory.



Applying agent customizations

The IntroscopeAgent.profile file from your previous installation contains settings and customizations you defined.

The 9.0 IntroscopeAgent.profile contains new settings that relate to 9.0 features and behavior.

Note: Do not copy the backup of IntroscopeAgent.profile from your previous installation over the 9.0 version. Compare the settings between the previous and 9.0 version of the file and identify the settings you customized. Copy the relevant settings from the backup you performed before the upgrade, and paste them into the Introscope 9.0 IntroscopeAgent.profile.

The IntroscopeAgent.profile is located in one of these locations:

■ in the default Introscope installation: <EM_Home>/examples

■ in an agent installation on an application server: <Appserver_Home>/wily

Upgrading PowerPacks and extensions

This section provides information related to upgrading PowerPacks and extensions.

If you are upgrading from an earlier Introscope version with a PowerPack installed, the Introscope main installer copies the existing PowerPack .JAR files, extensions, typeviews, management module(s) and calculators (if any) into the \backup folder.

However, if you want to use 9.x new features, be sure to use the new version of the files.

Upgrading a PowerPack is a manual process and is similar to a new install. For installation and configuration details, refer to the appropriate PowerPack user guide.

Note: For upgrade instructions for the following PowerPacks, refer to the CA Wily APM Release Notes:

■ PowerPack for WebSphere MQ Connectors and Messaging System

■ SOA Extension for IBM WebSphere Process Server and WESB

■ SOA Extension for Oracle Service Bus

If you are upgrading from an earlier Introscope version with LeakHunter, ErrorDetector, SNMP Adapter, or ChangeDetector extension installed, the Introscope main installer copies the existing add-on .JAR files, extensions, tab views, and calculators (if any) into the \backup folder.

Completing the upgrade


The installer leaves the existing Management Module(s) in place and does not copy them to the \backup folder. Use the current version’s Management Module(s) instead.

Upgrading an extension is a manual process. By default, the installer disables these extensions, and you must manually enable them. Consult the extension’s documentation for details, and see About the PowerPacks and extensions (see page 122).


After the upgrade finishes, you must perform some tasks before you start the 9.0 Enterprise Manager. These tasks complete the upgrade.

To manually complete the upgrade:

1. Transfer custom .JAR files that are in the Enterprise Manager or WebView classpaths.

If your previous Introscope installation included custom .JAR files on your Enterprise Manager or WebView classpath (in the Enterprise Manager or WebView .LAX or .CONF files), restore them now. Copies of the old .LAX or .CONF files are located in <EM_Home>/backup/<iscXx>, where <iscXx> is the release number of the old installation; for example, isc71P8.

Note: During an upgrade, various property files are backed up to <EM_Home>/backup/<iscXx> for your convenience during post-upgrade tasks. These files provide an easy way for you to review your previous configurations without having to locate and access the full backup you did before you started the upgrade. The backup/<iscXx> folder is organized as the Introscope root directory would be. For example, the .conf and .sh files are located in backup/<iscXx>; properties files in backup/<iscXx>/config; system ProbeBuilder directives in backup/<iscXx>/config/systempbd; and so on.

IMPORTANT! You cannot use these files to roll back an upgrade, and the files are not a substitute for making a full backup of your Enterprise Manager before upgrading.

2. Transfer property file comments.

If your old installation property files included comments that you want to retain, restore them at this time by adding them to the property files in your new installation.

3. Restore customizations to management modules.

If you added business logic to the examples/SampleManagementModule.jar file in your previous installation, the upgrade has overwritten it with the new examples/SampleManagementModule.jar file. You must manually restore your custom information from the backup file that was saved in backup/iscXx/examples.



4. For z/OS and OS/400 only: If you edited your old runem or runwv shell scripts to add or change information, you must manually edit the new scripts to update them with that information now.

5. Transfer customized system .PBD files.

If you installed ProbeBuilder with your Enterprise Manager and you customized any system .PBD files, place the customized files in the new hotdeploy directory. Agent.profile does not need to be updated. For more information, see the Introscope Java Agent Guide or Introscope .NET Agent Guide.

6. Upgrades from 8.0 only: Redo any customizations made to files in the following directory:

The installer replaces the .JAR files in all <EM_Home>/product/*/plugins/ directories. It will also replace this directory and all of its contents:

<EM_Home>/product/enterprisemanager/plugins/com.wily.introscope.workstation.w

ebstart_9.0.n

where 9.0.n is the version you upgraded from. If you edited files in this directory during the original install (to customize the version requirements for the Web Start Workstation JVM), you must manually redo the customization after the upgrade. For your reference, the installer preserves your original customizations in the backup directory in /backup/iscXx.

7. If you want a Workstation to be located in your Enterprise Manager directory, reinstall it now.

Note: The Workstation must be the same release number as the Enterprise Manager in the installation directory.

8. Restart the upgraded Enterprise Manager.


Chapter 13: Upgrading security

This chapter includes information related to upgrading Wily CEM operator data to work in the current version of CA Wily APM.


About upgrading Wily CEM operators (see page 235) Upgrading Wily CEM operators to CA EEM users and groups (see page 236) Removing Wily CEM users and groups after uninstalling Wily CEM (see page 241) Upgrading from Wily CEM operators to Local users (see page 242) About the Introscope security upgrade (see page 244)

About upgrading Wily CEM operators

In Wily CEM 4.5.x, you created and stored Wily CEM operator data in Security > Operators in the TESS UI.

In deploying CA Wily APM 9.0, your organization will choose and deploy a security solution. For Wily CEM security, your organization must deploy one of two security solutions:

■ CA Embedded Entitlements Manager (CA EEM): A CA application that allows other applications to share common access policy management, authentication, and authorization services/

■ Local XML files (Local): Local security consists of Local authentication and authorization using XML files stored in the Enterprise Manager in the <EM_Home>/config directory.

For more information about CA EEM and Local security, see the CA Wily APM Security Guide.

In CA Wily APM 9.0, Wily CEM operators are called Wily CEM users, which belong to Wily CEM security groups.

Note: The term Wily CEM security group means any group set up to be authenticated and authorized to use Wily CEM. However, in CA Wily APM and Introscope security, the terms user group and CA Wily APM user group mean any group set up to be authenticated and authorized to use Introscope or CA Wily APM. In Wily CEM, the term user group means a logical grouping of people who use a website (or web application) that Wily CEM is monitoring. For more information, see the CA Wily APM Security Guide and the CA Wily APM Glossary.

Upgrading Wily CEM operators to CA EEM users and groups


When upgrading Wily CEM, CA Wily APM provides scripts that export Wily CEM 4.5.x operators and generates Wily CEM users for the CA EEM and Local realms. In CA Wily APM 9.0, Wily CEM operator data is not stored in the APM database. Instead, Wily CEM user data is stored in either CA EEM or, for Local security, in the users.xml file.

CA Wily APM provides scripts that:

■ retrieve Wily CEM 4.5.x operators and roles from the APM database.

■ for CA EEM security, creates three Safex xml scripts to load Wily CEM 4.5.x users and groups in your CA EEM realm.

■ for Local security, creates a usersCEM45.xml file to load Wily CEM 4.5.x users and groups in your Local realm.

You can run either Windows or UNIX scripts depending on your environment. After you run the scripts appropriate to your security deployment, you perform some CA EEM or Local security-specific tasks.


Upgrading Wily CEM operators and migrating them into CA EEM users and groups involves the following tasks; these tasks are detailed in this section:

1. Ensure you have performed the prerequisite tasks. See What to do before upgrading Wily CEM 4.5.x operators to CA EEM (see page 237).

2. Export Wily CEM operators from the Wily CEM APM database to XML. See Exporting Wily CEM operators to XML (see page 237).

3. Run the generated XML scripts to add the operators into CA EEM users and groups. See Adding the exported Wily CEM operators into CA EEM (see page 239).

4. Verify the users in CA EEM are authorized to access Wily CEM. See Verifying Wily CEM users authorization in CA EEM (see page 240).

5. Reset passwords for the imported Wily CEM users and groups. See Resetting passwords for Wily CEM users in CA EEM (see page 241).



What to do before upgrading Wily CEM 4.5.x operators to CA EEM

Before upgrading Wily CEM 4.5.x operators to CA EEM users, you must:

■ On the machine where you will run the operator export script, set JAVA_HOME to point to JRE version 1.6 or higher. For instructions on using the operator export script, see Exporting Wily CEM operators to XML, below.

■ Set up the default CA Wily APM application in CA EEM by running the eem.register.app.xml Safex script provided in the CA Wily APM 9.0 <EM_Home> \examples\authentication directory.

■ Run the eem.add.globalidentities.xml file provided in the CA Wily APM 9.0 <EM_Home>\examples\authentication directory to add CA Wily APM global users and groups.

■ Ensure that no Wily CEM 4.5.x operators have invalid characters in the usernames. Valid user names are restricted to alphanumeric, hyphen, or underscore characters. During export, the script does not export invalid operators and instead displays a warning message for each invalid operator.

For more information, see the CA Wily APM Security Guide.

Exporting Wily CEM operators to XML

When migrating Wily CEM operators to CA EEM, you need to first run the operator export script that is installed with the Enterprise Manager. This operator export script exports the user and group data from the database into three CA EEM Safex script files. You can run the operator export script from the same machine that hosts the database, or a remote machine.

IMPORTANT! When you export Wily CEM operators to XML using the operator export script, users with invalid user names are not exported. Valid user names are restricted to alphanumeric, hyphen, or underscore characters. During export, a warning message indicates any invalid user that is not exported.

To export Wily CEM users and groups to XML:


■ Windows: <EM_Home>\install\database-scripts\windows

■ UNIX: <EM_Home>/install/database-scripts/unix

2. Open a command prompt, and run the following script for your operating system, according to the syntax and arguments listed below:

■ Windows: operatorexport.bat

■ Linux: operatorexport.sh

operatorexport.sh <dbhostIP> <dbport> <dbname> <dbuser> <dbpassword>

<exportType(eem/local/both)> <exportToDir>



Below are the argument descriptions.

dbHostIP

IP address of the machine where the Wily CEM 4.5.x (PostgreSQL) database is installed. If running on the machine directly, you can enter localhost.

dbport

(default is 5432) Port on which the database communicates to Wily CEM components

dbname

(default is cemdb) Database instance name for the Wily CEM 4.5.x (PostgreSQL) database

dbuser

(default is admin) 4.5 Wily CEM (PostgreSQL) database user name

dbpassword

Password for the 4.5 Wily CEM (PostgreSQL) database user

exportType

Enter eem or local or both. If exporting operators for migration into CA EEM, specify eem.

Note: Use the both variable to generate both the: * Safex scripts to transfer Wily CEM 4.5.x users into CA EEM * usersCEM45.xml file to transfer Wily CEM 4.5.x users to the Local realm

exportToDir

The directory under which the output xml files will be generated.

For example if you are on Windows and input safexfiles as the variable name, the script output will be saved in the <EM_Home>\install\database-scripts\windows\safexfiles directory.

For example:

operatorexport.sh 127.0.0.1 5432 cemdb cemadmin quality eem safexfiles



Depending on the exportType you specified, the script generates new files in the output directory. If you specified the exportType as eem, the script generates three new files:

■ eem.add.global.identities.xml is an CA EEM Safex script that adds Wily CEM 4.5.x global users to CA EEM.

IMPORTANT! The eem.add.global.identities.xml file generated by the operator export script is a different file from the initial CA EEM set up eem.add.global.identities.xml file. The former is for the Wily CEM upgrade process. The latter sets up users and groups in the default CA Wily APM application.

■ eem.add.app.groupsAndusers.xml is an CA EEM Safex script that adds Wily CEM 4.5.x application groups and users to CA EEM.

■ eem.remove.global.identities.xml is an CA EEM Safex script that removes global users if you later uninstall Wily CEM or remove CEM users and security groups from CA EEM.

Note: When you generate the Safex scripts, this process also resets all user passwords to quality.

Note: If you specified an exportType of both, the script also generates the usersCEM45.xml and users.xml files. If you specified an exportType of both or Local, see Upgrading from Wily CEM operators to Local users for details.

Adding the exported Wily CEM operators into CA EEM

IMPORTANT! Duplicate users cannot be created in CA EEM. If a Wily CEM 4.5.x operator user name already exists in CA EEM, when the upgrade script tries to load the same user name that’s been extracted from the Wily CEM 4.5.x APM database, the new duplicate name will not be loaded.

Run the new CA EEM Safex scripts to add the Wily CEM 4.5.x operators to the appropriate global and application-specific CA EEM Wily CEM user groups.

To add the exported Wily CEM operators into CA EEM:

1. On the machine that hosts CA EEM, go to the C:\Program Files\CA\Embedded IAM SDK\ directory on Windows or the /opt/CA/SharedComponents/Technology/ directory on Linux.


safex.exe -h <hostname> -u <username> -p <password> -f

eem.add.global.identities.xml


safex.exe -h hostname -u username -p password -f eem.add.app.groupsAndusers.xml



Verifying Wily CEM users authorization in CA EEM

After you have added the exported operators into CA EEM user groups, you should verify that the users are authorized to access Wily CEM in CA EEM.

To verify that the Wily CEM 4.5.x operators are Wily CEM users in CA EEM:

1. Log in to the CA Wily APM application on CA EEM:

a. At the CA EEM log-in page, choose APM from the Application: drop-down list.

b. Enter the log-in name and password.

The CA Wily APM application default log-in is EiamAdmin.

2. Navigate to Manage Identities > Users.

3. Verify that Wily CEM 4.5.x operators are now listed as users and assigned to the correct Wily CEM user groups.

For example, if Tony Dae is a Wily CEM 4.5.x user who is a member of the CEM System Administrator group, verify that Tony Dae is a user in CA EEM and belongs to the CEM System Administrator group.

4. Handle as appropriate the Wily CEM 4.5.x users that have a status of disabled.

Wily CEM 4.5.x users with a status of disabled are exported to the eem.add.global.identities.xml file with a status of suspended.

a. In the eem.add.global.identities.xml file you can search for this line to find all the Wily CEM 4.5.x users now with a status of suspended: <Suspended>yes</Suspended>

For example, the Wily CEM 4.5.x user Bruce Lee with status of disabled is listed in the eem.add.global.identities.xml file as shown in this sample snippet.

<GlobalUser name="Bruce_Lee" folder="/APM">

<UserName>Bruce_Lee</UserName>

<DisplayName>Bruce Lee</DisplayName>

<Password>quality</Password>

<FirstName>Bruce</FirstName>

<LastName>Lee</LastName>

<WorkPhoneNumber>2334082390840234</WorkPhoneNumber>

<EmailAddress>[email protected]</EmailAddress>

<Suspended>yes</Suspended>

</GlobalUser>

b. Input data into CA EEM about Wily CEM 4.5.x users with a status of suspended as appropriate to your organization’s security policies.

Removing Wily CEM users and groups after uninstalling Wily CEM


Resetting passwords for Wily CEM users in CA EEM

Upon transfer from the Wily CEM 4.5.x APM database, the operator export script resets all Wily CEM 4.5.x passwords to quality. For security reasons, these passwords need to be changed.

Do one of the following:

■ Log in to CA EEM as the CA Wily APM administrator and reset each user’s password. The CA Wily APM administrator in CA EEM is EiamAdmin.

■ Edit the Safex scripts to change the passwords in the .XML files (eem.add.global.identities.xml and eem.add.app.groupsAndusers.xml).

■ Instruct the Wily CEM users to log in to CA EEM directly and change their password themselves. When they log in to CA EEM, they can use the Change Password link on the Home page.

If you change users’ passwords, be sure to notify users of their new passwords. Consult the CA EEM documentation for instructions on resetting passwords.

Removing Wily CEM users and groups after uninstalling Wily CEM

If you uninstall Wily CEM or remove Wily CEM users and security groups from CA EEM, use the eem.remove.global.identities.xml Safex script to remove CA EEM Wily CEM global users.

When upgrading Wily CEM from version 4.5.x to CA Wily APM 9.0, the operator export script generated the eem.remove.global.identities.xml Safex script. For details, see Exporting Wily CEM operators to XML (see page 237).

To remove Wily CEM users and groups from CA EEM:

1. Run the eem.remove.global.identities.xml CA EEM Safex scripts to remove Wily CEM users and groups in CA EEM.

a. On the machine that hosts CA EEM, go to this directory: C:\Program Files\CA\Embedded IAM SDK\.

At a command prompt, run this command to remove the Wily CEM 4.5.x operators to the appropriate global and application-specific CA EEM Wily CEM user groups.

C:\Program Files\CA\Embedded IAM SDK\safex.exe -h hostname

-u username -p password -f eem.remove.global.identities.xml

For example:

bin\safex.exe -h <EEM_Server_Ipaddress> -u EiamAdmin -p 1234567

-f eem.remove.global.identities.xml

Upgrading from Wily CEM operators to Local users


2. Verify that the Wily CEM users are removed from CA EEM.

a. Log in to the CA Wily APM application on CA EEM.

b. At the CA EEM log-in page, choose APM from the Application: drop-down list.

c. Enter the log-in name and password.

The CA Wily APM application default log-in is EiamAdmin.

d. Navigate to Manage Identities > Users.

e. Verify that Wily CEM 4.5.x operators formerly listed as users are no longer listed.

For example, if Tony Dae was a Wily CEM 4.5.x user who was a member of the CEM System Administrator group, verify that Tony Dae no longer in CA EEM and does not belong to the CEM System Administrator group.


Before upgrading Wily CEM 4.5.x operators to Local users, you must:

■ On the machine where you will run the operator export script (see step 1 on page 189), set JAVA_HOME to point to JRE version 1.6 or higher.

■ Review the CA Wily APM Security Guide about configuring Local security and using multiple files for security realms.

To upgrade Wily CEM 4.5.x operators to Local users and groups:

1. Run the operator export script to export Wily CEM operators from the Wily CEM 4.5.x APM database.

For details, see Exporting Wily CEM operators to XML. When you run the script, specify the exportType as Local.

For example:

operatorexport.sh 127.0.0.1 5432 cemdb cemadmin quality local exportcemoperators

The script generates a usersCEM45.xml file in the output directory.

Note: If Wily CEM 4.5.x users have a status of disabled, then they are not transferred to usersCEM45.xml for Local security.

2. Verify that the Wily CEM 4.5.x operators are now Wily CEM users in the usersCEM45.xml file.

a. Open the usersCEM45.xml file in the output directory.

b. Verify that Wily CEM 4.5.x operators are now listed in the file and are assigned to the correct Wily CEM security user groups.

For example, if Tony Dae is a Wily CEM 4.5.x user who is a member of the CEM System Administrator group, verify that Tony Dae is listed as user in usersCEM45.xml and belongs to the CEM System Administrator group.



3. Reset the passwords for the Wily CEM 4.5.x users just loaded into the usersCEM45.xml file. To do this, edit the <password> elements in the usersCEM45.xml file.

Upon transfer from the Wily CEM 4.5.x APM database, the operator export script resets all Wily CEM 4.5.x passwords to quality.

See the instructions for configuring CA Wily APM users and groups in users.xml in the CA Wily APM Security Guide.

4. Determine if you want one or two Local realms for your organization’s Local security.

After the operator export script runs, you have two Local xml files:

■ the usersCEM45.xml file you just created. This file is in, for example, the <EM_Home>/install/database-scripts/unix/exportcemoperators directory.

■ the users.xml file currently being used for Local security to authenticate CA Wily APM users. This file is in the <EM_Home>/config directory.

You have these options to complete the transfer of Wily CEM 4.5.x operators to Local security:

■ merge the Wily CEM 4.5.x users in the usersCEM45.xml file into the users.xml file. (Realm Option 1 (see page 243))

■ create a new Local realm that uses the usersCEM45.xml file to authenticate and authorize Wily CEM 4.5.x users. (Realm Option 2 (see page 244))

Once you have determined which option is best for your organization’s security deployment, follow the steps in the appropriate section.

Merging Wily CEM users from the usersCEM45.xml into the users.xml file (Realm Option 1)

When you are creating Local realms, you have the option to merge users into the same realm. This option is useful if you do not want to maintain a new, separate realm or if you have few users.

To merge Wily CEM users from the usersCEM45.xml file into the users.xml file: (Realm Option 1)

Note: Be sure you have reset the passwords of Wily CEM 4.5.x users before merging.

1. Open the usersCEM45.xml file.

This file is in, for example, the <EM_Home>/install/database-scripts/windows/exportcemoperators directory.

2. Open the users.xml file in the <EM_Home>/config directory.

About the Introscope security upgrade


3. Copy Wily CEM 4.5.x users and passwords from the usersCEM45.xml file and paste them into the users.xml file.

4. If needed, copy Wily CEM 4.5.x security user groups from the usersCEM45.xml file and paste them into the users.xml file.

5. Add each Wily CEM 4.5.x user to the appropriate Local security group.

Creating a new Local realm for Wily CEM users and groups (Realm option 2)

When you are creating Local realms, you have the option to create a new, separate realm. This option is useful if you already have a password-encrypted users.xml file, because you cannot merge a plain-text password file with an encrypted one.

To create a new Local realm for Wily CEM users and groups: (Realm option 2)

1. Copy the CEM45users.xml file.

2. Paste the CEM45users.xml file into the <EM_Home>/config directory.

3. Open the realms.xml file in the <EM_Home>/config directory.

4. Below the Local Users and Groups Realm, add a new realm for Wily CEM 4.5 and point to the CEM45users.xml file.

For example,

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<realms xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="0.1"

xsi:noNamespaceSchemaLocation="realms0.1.xsd">

<realm descriptor="CEM 4.5 Realm" id="Local Users and Groups" active="true">

<property name="usersFile">

<value>cem45users.xml</value>

</property>

</realm>

About the Introscope security upgrade

Be aware that when you upgrade an Introscope installation, the upgrade preserves the data in the users.xml file. For more details about what files are changed or preserved during the upgrade, see About file changes during an Introscope upgrade (see page 260).

For additional Introscope security upgrade information, see the CA Wily APM Security Guide.


Appendix A: Using the installation worksheet

This worksheet can help you decide how to configure the installer settings before you begin installing CA Wily APM. You can also use it to record the information you’ll need during the installation.

The worksheet is a handy tool during installation, a useful reference for administrators after installation, and useful information to have available for CA Support, should you need to call for help in resolving a problem later.


Do you want to configure JVM settings? (see page 246) What’s the location of the external component package archive file? (see page 246) What’s the location of the CA Wily license file? (see page 247) What are the Enterprise Manager ports? (see page 247) Should the Enterprise Manager be part of a cluster? (see page 248) If the Enterprise Manager is part of a cluster, is it the MOM or a Collector? (see page 248) How long do you store your Transaction Event data? (see page 249) Where do you store your Transaction Event data? (see page 249) Where do you store the SmartStor database? (see page 249) Where do you store the APM database? (see page 249) What port does the APM database use? (see page 250) What is the APM database instance name, usernames, and passwords? (see page 250) Does the Enterprise Manager run as a Windows Service? (see page 251) What ports and host does WebView use? (see page 251) What are the TIM’s network settings? (see page 252)

Do you want to configure JVM settings?


Do you want to configure JVM settings?

If you want to use a JVM other than the one that is bundled with Introscope, or if no JVM is bundled for your platform, you can configure the settings yourself. For each Introscope component you install (Enterprise Manager, WebView, and Workstation).

The path you enter to the JVM can be relative or absolute.

■ Java Virtual Machine (for example, jre\bin\java.exe):

_____________________________________________________

■ JVM arguments (for example, -Xms64m -Xmx256m):

_____________________________________________________

What’s the location of the external component package archive file?

For more information, see External component packages (see page 51).

Component package archive file location:

____________________________________________________

What’s the location of the CA Wily license file?


What’s the location of the CA Wily license file?

License file location:

____________________________________________________

You can skip this step in the installer and install the license later, if necessary.

Note: If you are performing an SAP installation, the installer does not prompt for a license.

What are the Enterprise Manager ports?

Agents and the Workstation connect to the port you choose for the Enterprise Manager connection port. Users accessing the Workstation using an HTTP browser URL connect to the Web Server port.

You can configure additional ports manually later, and can split them by modifying the Enterprise Manager properties (see the Introscope Configuration and Administration Guide for a discussion about using communications properties). For example, you might want to create separate ports for agent and Workstation connections.

Enterprise Manager Connection Port (default is 5001; 6001 for SAP):

_____________________________________________________

Enterprise Manager Web Server Port (default is 8081):

_____________________________________________________

IMPORTANT! If the Enterprise Manager is behind a firewall, be sure to configure the firewall to allow access to the Enterprise Manager Connection and Web Server ports.

Should the Enterprise Manager be part of a cluster?


Should the Enterprise Manager be part of a cluster?

The installer prompts you to specify whether the Enterprise Manager you’re installing will be part of a cluster.

See the Introscope Configuration and Administration Guide for information about configuring Enterprise Manager clustering.

If the Enterprise Manager is part of a cluster, is it the MOM or a Collector?

If the Enterprise Manager you’re installing will be part of a cluster, you specify whether it will be a MOM (manages other Enterprise Managers) or a Collector (managed by another Enterprise Manager).

If the Enterprise Manager you’re installing is a Manager, you specify the connection properties for up to five Collectors.

Is this Enterprise Manager a MOM? Y / N

Collector host name or IP address:

____________________________________________________

Collector port:

____________________________________________________

Note: You can configure up to five Collectors during the installation. If you need more Collectors, you can configure them manually later. See the Introscope Configuration and Administration Guide for more information about configuring clusters.

How long do you store your Transaction Event data?


How long do you store your Transaction Event data?

The default is 14 days. When deciding how long to keep Transaction Event data, consider that longer storage time increases system overhead and disk storage requirements.

Where do you store your Transaction Event data?

The installer creates the Transaction Event database in the <EM_Home>/traces directory by default, but you can specify another directory during the installation.

Where do you store the SmartStor database?

You must use a dedicated disk for SmartStor data to avoid affecting Enterprise Manager performance.

For the recommended space allocation, see Enterprise Manager requirements (see page 26).

See the CA Wily APM Sizing and Performance Guide and the spreadsheet SmartStorSizing.xls for SmartStor sizing information.

Where do you store the APM database?

You must use a dedicated disk for APM database data to avoid affecting Enterprise Manager performance. For the recommended space allocation, see Enterprise Manager requirements (see page 26).

The installer creates the APM database in the <EM_Home>\database directory or /opt/database directory by default, but you can specify another directory during the installation.

Note: You can use the installer to install the APM database as a PostgreSQL database instance on Windows, Linux, or Solaris. For these operating systems, the user account that runs the installer must have permissions to create users. On Windows, you can only install the APM database if your started the installer from a direct login or a console session. You cannot install the APM database through a terminal service session.

What port does the APM database use?


What port does the APM database use?

The default port for APM database when using PostgreSQL is 5432.

The default port for APM database when using Oracle is 1521, the default LISTENER port.

Note: If the APM database is behind a firewall, be sure to configure the firewall to allow access to the database port.

What is the APM database instance name, usernames, and passwords?

By default, the installer creates the PostgreSQL database instance and APM database schema with the following settings. You can adjust these settings during the installation, if desired.

PostgreSQL Administrator Username

postgres

PostgreSQL Administrator Password

If you installed the APM database with the default database configuration, the default password is C@wilyapm90.

Note: The PostgreSQL Administrator password must adhere to your organization’s password security policies. If a user account with this name already exists, the installation fails.

Database Name

cemdb

Database User

admin

Database Password

If you installed the APM database with the default database configuration, the default password is wily.

Note: The database user name cannot contain special or upper-case characters.

Does the Enterprise Manager run as a Windows Service?


Does the Enterprise Manager run as a Windows Service?

If you configure the Enterprise Manager as a service on a Windows system, you specify the service and display names.

What ports and host does WebView use?

The WebView HTTP port is the port to which WebView users connect. The WebView Enterprise Manager host is the host where your Enterprise Manager is running. The WebView Enterprise Manager port is your Enterprise Manager listener port.

WebView HTTP Port (default is 8080):

_____________________________________________________

WebView Enterprise Manager host (defaults to the name of the machine on which you’re installing):

_____________________________________________________

WebView Enterprise Manager port (default is 5001; 6001 for SAP):

____________________________________________________

What are the TIM’s network settings?


What are the TIM’s network settings?

(If you are upgrading Wily CEM, you have already established these settings.)

■ The TIM hostname and domain name:

_____________________________________________________

■ The TIM static IP address on the eth0 port:

_____________________________________________________

■ The TIM subnet mask:

_____________________________________________________

■ The TIM default gateway:

_____________________________________________________

■ The TIM DNS Server 1: (Optional)

_____________________________________________________

■ The TIM DNS Server 2: (Optional)

_____________________________________________________

■ The default login credentials for the TIM Wily System Setup page are as follows:

username=admin

password=quality

You should change the administrator password after you’ve finished installing the TIM.

■ Decide on the network monitoring ports to be used (eth1, eth2, eth3):

_____________________________________________________

■ The default login credentials for the Wily CEM console page are as follows:

username=cemadmin

password=quality


Appendix B: Manual upgrade and upgrade change summary

This chapter contains details on manually upgrading your existing Introscope installation, and also summarizes the changes that Introscope makes during an automated upgrade.


Manually upgrading Introscope (see page 253) About file changes during an Introscope upgrade (see page 260) Creating the APM database schema manually (see page 267)

Manually upgrading Introscope

Follow the instructions in this section to manually upgrade the Enterprise Manager, WebView, ProbeBuilder, and EPAgent.

Before manually copying and adjusting your pre-9.x configurations:

■ Perform a fresh install of Introscope 9.x, using the automated installer. See Installing Introscope main components.

You will be manually copying pre-9.x properties and configurations into the directories and files created by the automated installer.

Once the automated install is complete, proceed.

Note: If you are upgrading from a version prior to 8.x, refer to the 8.x Introscope Installation and Upgrade Guide for information on upgrading to 8.x.


Manual configuration file upgrade overview (see page 254) Manually upgrading the Enterprise Manager (see page 256) Manually upgrading WebView (see page 257) Completing the Enterprise Manager manual upgrade (see page 259)



Manual configuration file upgrade overview

The table below lists the Enterprise Manager files and properties that you need to copy or move to the new 9.x files:

File and location, relative to <EM_Home> Description

config/CustomDBRecordTypes.properties Copy these files over to the new installation directory, to replace the newly installed versions.

config/agentclusters.xml Copy these files over to the new installation directory, to replace the newly installed versions.

config/alert-blackout.xml

Note: This is a 7.x file, brought over if you upgraded from 7.x to 8.x. Continue to bring it over to 9.x, even though it is not shipped in 9.x.

Copy these files over to the new installation directory, to replace the newly installed versions.

config/domains.xml Copy these files over to the new installation directory, to replace the newly installed versions.

config/em-jetty-config.xml Copy these files over to the new installation directory, to replace the newly installed versions.

config/loadbalancing.xml Copy these files over to the new installation directory, to replace the newly installed versions.

config/server.xml Copy these files over to the new installation directory, to replace the newly installed versions.

config/webview-jetty-config.xml Copy these files over to the new installation directory, to replace the newly installed versions.

config/realms.xml Copy these files over to the new installation directory, to replace the newly installed versions.

config/users.xml

Note: You may need to add Wily CEM user and groups definitions to this file to connect to Wily CEM. For details, see the CA Wily APM Security Guide.

Copy these files over to the new installation directory, to replace the newly installed versions.

config/IntroscopeEnterpriseManager.properties Copy any customized properties, except for the specified single property and any customized absolute paths.

Handle the following property specially:

introscope.enterprisemanager.webserver.dir

For details, see Upgrading EnterpriseManager.properties (see page 256).



config/shutoff/ Copy the directory to the new installation, replacing the newly installed version.

IntroscopeEnterpriseManager.lax Copy any customized properties, except for the specified list of properties. For details, see Upgrading IntroscopeEnterpriseManager.lax (see page 257).

EMService.conf

Note: This file has changed location in 9.x. It is now in <EM_home>\bin.

Copy any customized properties, except for the specified list of properties. For details, see Upgrading EMService.conf (see page 257).

product/enterprisemanager/configuration/.settings/users.prefs

Copy the file over to the new installation directory, to replace the newly installed version.

runem.sh This file is shipped only by .JAR installers (which do not bundle JVMs). During an upgrade, the file is backed up to backup/iscXx and then replaced. The old settings are not preserved.

You must customize the new file with the appropriate JAVA_HOME and any other custom settings.

The table below lists the WebView files that need to either be copied over, or have properties in them moved over to the new 9.x files:

File and location, relative to <EM_Home> Description

config/IntroscopeWebView.properties Copy any customized properties over into the newly installed file.

WVService.conf

Note: This file has changed location in 9.x. It is now in <EM_home>\bin.

Copy any customized properties, except for the specified list of properties. For details, see Upgrading WVService.conf (see page 258).

IntroscopeWebView.lax Copy any customized properties, except for the specified list of properties. For details, see Upgrading IntroscopeWebView.lax (see page 258).

IntroscopeProbeBuilderWizard.lax Copy any customized properties, except for the specified list of properties. For details, see Upgrading IntroscopeProbeBuilderWizard.lax (see page 259).

runwv.sh This file is shipped only by .JAR installers (which do not bundle JVMs). During an upgrade, the file is backed up to backup/iscXx and then replaced. The old settings are not preserved.

You must customize the new file with the appropriate JAVA_HOME and any other custom settings.



The following EPAgent file must be either copied over, or have properties in them moved over to the new 9.x file:

The table below lists the files that need to either be copied over, or have properties in them moved over to the new 9.x files:

IntroscopeEPAgent.properties

Manually upgrading the Enterprise Manager

Follow these instructions to manually upgrade the Enterprise Manager (EM). The instructions will be divided according to files/folders in your Enterprise Manager installation.


Upgrading EnterpriseManager.properties (see page 256) Upgrading EMService.conf (see page 257) Upgrading IntroscopeEnterpriseManager.lax (see page 257)

Upgrading EnterpriseManager.properties

The following properties require special handling. All other customized property values can be manually copied to the newly installed EnterpriseManager.properties file as is.

■ If the introscope.enterprisemanager.webserver.dir property is configured to a value other than webapps, then:

■ Transfer the property to the EnterpriseManager.properties file in the 9.x installation.

■ Manually copy all newly-installed 9.x web applications from <EM_Home>/webapps to the custom directory.

■ Move the existing 8.x web application help files (IntroscopeHelp_Config.war and IntroscopeHelp_Using.war) to a backup location and remove them from the original location.

■ If you renamed your Introscope directory during the upgrade, and your property files used absolute paths to reference files in the Introscope directory, then you update these paths as a manual post-upgrade task. CA Technologies recommends using relative paths to refer to any file inside the Introscope root directory.



Upgrading EMService.conf

Note: This file has changed location in 9.x. EMService.conf is now in <EM_home>\bin. In previous versions, it was in <EM_home>.

Do not transfer the following properties to the newly installed EMService.conf file. The default settings in the new installation should be used instead:

■ wrapper.java.command

■ wrapper.app.parameter.*

■ wrapper.java.classpath.*

■ wrapper.native_library.*

You can transfer all other customized property values from the old file to the newly installed version.

Upgrading IntroscopeEnterpriseManager.lax

Do not transfer the following properties to the newly installed IntroscopeEnterpriseManager.lax file:

■ lax.class.path

■ lax.version

■ lax.main.class

■ lax.command.line.args

■ lax.nl.valid.vm.list

■ lax.nl.message.vm.not.loaded


Manually upgrading WebView

Follow these instructions to manually upgrade WebView. The instructions will be divided according to files/folders in your installation.


Upgrading IntroscopeWebView.properties (see page 258) Upgrading WVService.conf (see page 258) Upgrading IntroscopeWebView.lax (see page 258) Upgrading IntroscopeProbeBuilderWizard.lax (see page 259)



Upgrading IntroscopeWebView.properties

All customized property values in the IntroscopeWebView.properties file can be transferred to the new 9.x version of the file as is.

Upgrading WVService.conf

Do not transfer the following properties to the newly installed WVService.conf file:





Upgrading IntroscopeWebView.lax

Do not transfer the following properties to the newly installed IntroscopeWebView.lax file:

■ lax.class.path

■ lax.version

■ lax.main.class







Upgrading IntroscopeProbeBuilderWizard.lax

Do not transfer the following properties to the newly installed IntroscopeProbeBuilderWizard.lax file:

■ lax.class.path

■ lax.version

■ lax.main.class





Completing the Enterprise Manager manual upgrade

To complete the manual upgrade, manually copy certain files from the old Enterprise Manager instance to the new one.

To complete the Enterprise Manager manual upgrade:

1. Manually copy these components from the old 8.x Enterprise Manager instance to the new 9.x Enterprise Manager instance:

■ all customized management modules

■ any custom extensions

■ any custom documents

2. Manually copy the data or log files you want to retain from the old Enterprise Manager instance to the new Enterprise Manager instance. The list below has suggestions for files you may want to retain.

Enterprise Manager (EM)

data/*

traces/*

perflog.txt

querylog.txt

Enterprise Manager or WebView

any custom SSL key files

logs/*.LOG

About file changes during an Introscope upgrade


ProbeBuilder

any custom .PBD files (See Completing the upgrade regarding post-upgrade tasks for .PBD files.)

any customized system .PBD files

EPAgent

any customized EPAgent files

To keep data or log files from the old Enterprise Manager instance, manually copy them to the new Enterprise Manager instance.

Note: If a data file is in a shared directory (for example, \\mySAN\data) you do not need to move the file. Instead, edit the new installation’s IntroscopeEnterpriseManager.properties file to point to the shared location.

Note: Custom extensions written for 8.x and earlier may need to be rewritten for Introscope 9.x. For more information, contact CA Support or CA Technologies Professional Services.


This section describes the files and properties that Introscope updates during the Introscope 9.x upgrade, and which are replaced.

For the following files, the upgrade keeps the previous versions and does not install new versions:

■ config/users.xml

■ config/domains.xml

■ config/alert-blackout.xml

■ config/agentclusters.xml

■ config/server.xml

■ config/shutoff/*

The upgrade migrates any customizations of these files from the old version to the new version:

■ Service.conf

■ .lax

■ config/*.properties



The upgrade removes obsolete files after backing them up:

■ Obsolete extensions, .JAR files, and docs shipped with the original installation

■ Extensions, .JAR files, documents, and other files added by the user will be left alone

The upgrade removes SDK files previously deployed as part of CA Wily Integrations.


How the upgrade handles properties files (see page 261) Files and properties that Introscope upgrades (see page 261) Files and properties that Introscope does not upgrade (see page 263) Introscope files that the installer moves or copies during upgrade (see page 265)

How the upgrade handles properties files

■ Any property name & value that existed in the previous file is carried over to the new file—unless the property has gone away or changed in the new version. See Files and properties that Introscope does not upgrade (see page 263) for specifics on how these cases are handled.

■ Any new property not in the old file will appear in the new property file with the default value.

■ User comments are not preserved.

■ If the user customized the order of properties within the file, that order will not be preserved.

Files and properties that Introscope upgrades

The Introscope upgrade automatically makes the changes listed in the section, Manually upgrading Introscope (see page 253) (which you can choose to manually upgrade, if desired).

The Introscope upgrade saves configuration options that were made to a 8.x installation. The upgrade:

■ Preserves the settings that are configured in files in your <EM_Home> directory, including:

■ .LAX files that define startup settings for the Enterprise Manager, WebView, and local Workstation installations.

■ Performance and query logs—if these logs were being written to the Introscope root directory, they have been moved to the \logs directory.

■ .CONF files that configure Enterprise Manager and WebView as Windows services.



■ Preserves the contents of SmartStor, Transaction Event, and baselines databases. Here are the default locations of these databases:

■ SmartStor database: <EM_home>\data

■ Transaction Event database: <EM_home>\traces

■ Baselines : <EM_home>\data\baselines.db

■ Upgrades the JRE, if any, that was bundled with your previous Introscope installation.

■ Preserves the contents of the files in the <EM_Home>/config directory, including:

■ XML files that define domains, users, Enterprise Manager permissions, virtual agents, and alert blackout periods.

■ Shutoff setting files in the shutoff directory.

■ Property files for the Enterprise Manager, WebView, the EPAgent, and local or LDAP authentication.

■ The values you customized in properties files are also preserved. If you edited existing properties in Introscope 7.x, the 9.x upgrade imports the changes into your upgraded installation. See About upgraded property files, below (see page 262).

■ Removes the transactionevents storage directory. This is the directory specified in the IntroscopeEnterpriseManager.properties file by the property introscope.enterprisemanager.transactionevents.storage.dir. For example, if the line in the IntroscopeEnterpriseManager.properties file reads:

introscope.enterprisemanager.transactionevents.storage.dir=traces

Then the installer removes traces/index/.

■ Renames the ext/ddtv directory—used to store user-created tab-view management module elements—to ext/xmltv.

■ Keeps any customized .JAR files in the \ext directory. The installer moves the .JAR files that shipped with the previous Introscope to the \backup directory.

■ Moves any obsolete .JAR files in the \lib directory to the \backup directory.

■ Moves the installer response files (\install\autogenerated.responseFile.*) to the \backup directory. The upgrader creates new versions of the response files that contain information on the upgrade.

About upgraded property files

Some notes about upgraded property files:

■ During an upgrade to Introscope 9.x, you receive new copies of all property files. The upgrade updates these new copies with the settings from your old property files. The upgrade thus doesn’t preserve your old property files—it preserves the old settings by transferring them to the new files.



■ After the upgrade, the location of your old settings in property files might be different than in your previous Introscope installation:

■ Old property file settings that are commented into Introscope 9.x by default appear in the same section of the new property file as in the old file.

■ Custom properties, or properties that are commented out of Introscope 9.x by default, are appended to the bottom of the new property file.

If you open a new property file and don’t see a property where it appeared in the old file, scroll to the end of the new file to find it.

■ If the name, format, or default value of a property changed from your Introscope installation version 8.x to 9.x, the upgrade automatically adjusts your installation to reflect the changes.

Files and properties that Introscope does not upgrade

This section lists the properties, scripts, and files that Introscope does not upgrade.


Non-upgraded properties (see page 263) Non-upgraded scripts (see page 264) Non-upgraded files (see page 265)

Non-upgraded properties

These properties are not upgraded in any .LAX file:

■ lax.class.path

■ lax.version

Note: If you manually added .JAR filenames to any 8.x classpath, you must manually add them to the 9.x classpath after the upgrade is complete.

In EMService.conf and WVService.conf, these properties are not upgraded:




■ wrapper.native_library.*

Note: If you manually added .JAR filenames to any 8.x .conf classpath, you must manually add them to the 9.x classpath after the upgrade is complete.



Exceptions:

■ If the introscope.enterprisemanager.dbfile property points to a file named em.db (case insensitive), em.db file itself will be renamed to baselines.db and the property value will be updated accordingly.

■ For any properties which both start with the string introscope.enterprisemanager.serversocketfactory and are set to any of these three values:

■ com.wily.isengard.postofficehub.link.net. DefaultServerSocketFactory

■ com.wily.isengard.postofficehub.link.net. ObfuscatedServerSocketFactory

■ com.wily.isengard.postofficehub.link.net. SSLServerSocketFactory

For these, the property value will be edited to read ...link.net.server... (in other words, server. will be inserted before the classname).

■ If the introscope.enterprisemanager.webserver.dir property is configured to a value other than webapps, the new 9.x webapps will be installed to that directory and also to webapps.

■ If the com.wily.introscope.documentation.dir property is present and configured to a value other than docs, the upgrader:

■ Backs up, then upgrades, the docs in the custom folder.

■ Ships any new docs to the custom folder.

■ Preserves any extra docs that the user added to the custom folder.

Non-upgraded scripts

These scripts are not upgraded:

■ runem.sh

■ runwv.sh

The upgrade saves these scripts in the directory backup/iscXx, and replaces them. If you edited your old runem or runwv shell scripts to add or change information, you must manually edit the new scripts to update them with that information after the update is complete.



Non-upgraded files

The upgrade moves all .PBD files in config/systempbd/*.pbd to the backup directory in your <EM_Home> directory and replaces them with the 9.x versions.

The installer replaces the file examples/SampleManagementModule.jar with the new Introscope 9.x examples. Any changes you made to the file in the examples directory of your previous installation are overwritten by the new version. If you made changes to that file, you must restore them from the previous version, which was saved in backup/iscXx/examples.

Tip: To try using the new sample Management Module, manually rename it—for example, TestManagementModule.jar—before you deploy the 9.x examples/SampleManagementModule.jar.

Introscope 9.x upgrades the Management Module files that are located in your config/modules deployment directory—if you have modified those files, the changes are upgraded automatically to 9.x.

The upgrade removes any CA Wily SDK/API files that were previously deployed for web services integration with other CA Technologies applications. Specifically, the upgrade removes the following files:

■ <EM_home>\webapps\introscope-web-services.war

■ <EM_home>\webapps\castylesr2.war

■ <EM_home>\ext\IscopeAlertsExt-EM.jar

Introscope files that the installer moves or copies during upgrade

If the Introscope installer moves a file to a new location, the file exists only in the new location.

If the Introscope installer copies a file to a new location, the file exists in both the old and new locations.


General Introscope files that are moved during upgrade (see page 266) Enterprise Manager files that are moved or copied during upgrade (see page 266) Environmental Performance Agent files that are moved or copied during upgrade (see page 267) ProbeBuilder files that are moved or copied during upgrade (see page 267) WebView files that are moved or copied during upgrade (see page 267)



General Introscope files that are moved during upgrade

The following table lists the files and directories that apply to multiple Introscope components and are moved during the upgrade process.

File or directory Moved to this location..

install/ backup/iscXx/install/

jre/ backup/iscXx/jre/

UninstallerData/base/ backup/iscXx/UninstallerData/base/

lax.jar install/lax.jar

Enterprise Manager files that are moved or copied during upgrade

The following table lists the Enterprise Manager files that the installer copies during upgrade.

File or directory Copied to this location..

config/CustomDBRecordTypes.properties backup/iscXx/config/ CustomDBRecordTypes.properties

config/*.xml backup/iscXx/config/*.xml

config/modules/ backup/iscXx/config/modules/

The following table lists the Enterprise Manager files that the installer moves during upgrade.

File or directory Moved to this location...

config/ IntroscopeEnterpriseManager.properties

backup/iscXx/config/ IntroscopeEnterpriseManager.properties

EMService.conf backup/iscXx/EMService.conf

IntroscopeEnterpriseManager.lax backup/iscXx/IntroscopeEnterpriseManager.lax

IntroscopeProbeBuilder.lax backup/iscXx/IntroscopeProbeBuilder.lax

runem.os400.sh (OS/400 version) backup/iscXx/runem.sh

runem.zos.sh (z/OS version) backup/iscXx/runem.sh

ext/*.jar added by user after install backup/iscXx/ext/*.jar added by user after install

Creating the APM database schema manually


Environmental Performance Agent files that are moved or copied during upgrade

During upgrade, Introscope copies the EPAgent files from the epaplugins/ directory to the backup/iscXx/epaplugins/ directory.

During upgrade, Introscope moves the config/IntroscopeEPAgent.properties EPAgent file from the config/ directory to the backup/iscXx/config/ directory.

ProbeBuilder files that are moved or copied during upgrade

The following table lists the ProbeBuilder files that the installer copies during upgrade.

File or directory Copied to this location..

config/custompbd/ backup/iscXx/config/custompbd/

config/systempbd/ backup/iscXx/config/systempbd/

No files are moved for ProbeBuilder.

WebView files that are moved or copied during upgrade

No files are copied for WebView.

The following table lists the WebView files that the installer moves during upgrade.

File or directory Moved to this location...

config/ IntroscopeWebView.properties

backup/ iscXx/config/IntroscopeWebView.properties

IntroscopeWebView.lax backup/iscXx/IntroscopeWebView.lax

WVService.conf backup/iscXx/WVService.conf

work/ backup/iscXx/work/


In some environments, it may be desirable or necessary to create the APM database schema manually. For example, your database administrator may not want to run Enterprise Manager installer interactively or using a response file, or wants to manually control the tables, views, and sequences added to the database while ensuring no other components are installed on the database server. Instead, the database administrator may choose to manually create the database schema, and can use the scripts installed by default in the <EM_Home>/install/database-scripts directory.



To create the APM database schema manually

1. Open a command or terminal window as appropriate for your operating environment.

2. Navigate to the <EM_Home>/install/database-scripts directory for your operating environment. For example, if you are creating the APM database schema on a Linux or Solaris computer, navigate to the <EM_Home>/install/database-scripts/unix directory:

cd <EM_Home>/install/database-scripts/unix

3. Run the createschema.bat or createschema.sh command appropriate for your operating environment using the following arguments:

CreateSchema -databaseName <database_name> -databaseType <database_type> -host

<host_name> -port <port_number> -releaseVersion <version> -scriptsDir

<directory> -user <user_name> -password <password>

databaseName

Specifies the database name or service identifier of the database instance. For example, if you are creating an Oracle database schema, set this parameter to the Oracle database SID.

databaseType

Specifies whether the database is an Oracle database or a PostgreSQL database. For example, if you are creating an Oracle database schema, set this parameter to oracle. The only valid values are oracle and postgres. If you are running the command on Linux or UNIX, keep in mind that this setting is case-sensitive.

host

Specifies the host name or IP address of the computer that hosts the database server.

port

Specifies the port number for communication between the Enterprise Manager and the APM database. For example, the default port for the LISTENER port on an Oracle database is 1521. The default port for the PostgreSQL database is 5432.

releaseVersion

Specifies the version of the APM database schema to create. For the current version of the APM database schema, you should set this option to 9.0.6.0.

scriptsDir

Specifies the directory for database-specific SQL scripts. For example, you should use <EM_Home>/install/oracle/database-scripts if you are creating an Oracle database schema or <EM_Home>/install/database-scripts if you are creating a PostgreSQL database.



user

Specifies the user name for connecting to the database and creating the APM database schema. If you are creating an Oracle database schema, the user name you specify is the database owner.

password

Specifies the password for the specified database user name.

For example, run a command similar to the following to manually create the APM database schema for Oracle on a Linux computer:

./createschema.sh -databaseName cemdb -databaseType oracle -host localhost -port

1521 -releaseVersion 9.0.6.0 -scriptsDir

/home/Introscope9.0.6.0/install/oracle/database-scripts -user apmadmin

-password quality

The CreateSchema program calls several individual SQL scripts to remove any existing APM database schema objects and create new APM database tables, constraints, indexes, procedures, views, and sequences. For more information about the individual SQL scripts used to drop and create the APM database schema, see Running individual SQL scripts to manage the APM database schema (see page 269).

4. Check the schematools.log file in the install directory to verify the schema has been created successfully or to troubleshoot problems with the schema creation. The directory and file are created automatically in the directory from which you started the CreateSchema command. For example, if you are creating the APM database schema on a Linux or Solaris computer, navigate to the <EM_Home>/install directory.

Running individual SQL scripts to manage the APM database schema

In most cases, you can use wrapper programs, such as the CreateSchema or dbdrop programs, to create or remove APM database schema objects in an Oracle environment. These programs call individual SQL scripts to perform specific operations, such as creating tables and views or adding constraints. You can use these individual scripts independent of the wrapper programs for greater flexibility in managing the APM database schema. For example, if you already have a repository of scripts and processes in place for managing different schemas and databases, you may want to add the scripts for managing APM database objects to your current repository and management processes.



The individual SQL scripts for managing APM database schema objects are installed by default in the <EM_Home>/install/oracle/database-scripts directory.

You can execute the individual SQL scripts in the following order to DROP an existing schema:

<EM_Home>/install/oracle/database-scripts/droptables-oracle-<VERSION>.sql

<EM_Home>/install/oracle/database-scripts/dropsequences-oracle-<VERSION>.sql

<EM_Home>/install/oracle/database-scripts/droptables-apm-oracle-<VERSION>.sql

<EM_Home>/install/oracle/database-scripts/dropsequences-apm-oracle-<VERSION>.sql

You can execute the individual SQL scripts in the following order to CREATE a new Oracle schema:

<EM_Home>/install/oracle/database-scripts/createtables-oracle-<VERSION>.sql

<EM_Home>/install/oracle/database-scripts/createsequences-oracle-<VERSION>.sql

<EM_Home>/install/oracle/database-scripts/addindexes-oracle-<VERSION>.sql

<EM_Home>/install/oracle/database-scripts/addconstraints-oracle-<VERSION>.sql

<EM_Home>/install/oracle/database-scripts/addviews-oracle-<VERSION>.sql

<EM_Home>/install/oracle/database-scripts/defaults-oracle-<VERSION>.sql

<EM_Home>/install/oracle/database-scripts/initdb-oracle-<VERSION>.sql

<EM_Home>/install/oracle/database-scripts/create-apm-tables-oracle-<VERSION>.sql

<EM_Home>/install/oracle/database-scripts/create-apm-sequences-oracle-<VERSION>.s

ql

<EM_Home>/install/oracle/database-scripts/add-apm-indexes-oracle-<VERSION>.sql

<EM_Home>/install/oracle/database-scripts/add-apm-constraints-oracle-<VERSION>.sq

l

<EM_Home>/install/oracle/database-scripts/apm-procedures-oracle-<VERSION>.sql

<EM_Home>/install/oracle/database-scripts/procedures-oracle-<VERSION>.sql

<EM_Home>/install/oracle/database-scripts/quartz-1.5.1-oracle.sql

To run the individual SQL scripts to create the APM database schema manually

1. Open a command or terminal window as appropriate for your operating environment.

2. Navigate to the <EM_Home>/install/oracle/database-scripts directory. For example:

cd <EM_Home>/install/oracle/database-scripts

3. Start SQL *Plus from the command line or using Oracle Enterprise Manager, and connect to the database instance, if needed.



4. Execute the individual SQL scripts in the following order to create a new Oracle schema for the APM database:

createtables-oracle-<VERSION>.sql

createsequences-oracle-<VERSION>.sql

addindexes-oracle-<VERSION>.sql

addconstraints-oracle-<VERSION>.sql

addviews-oracle-<VERSION>.sql

defaults-oracle-<VERSION>.sql

initdb-oracle-<VERSION>.sql

create-apm-tables-oracle-<VERSION>.sql

create-apm-sequences-oracle-<VERSION>.sql

add-apm-indexes-oracle-<VERSION>.sql

add-apm-constraints-oracle-<VERSION>.sql

apm-procedures-oracle-<VERSION>.sql

procedures-oracle-<VERSION>.sql

quartz-1.5.1-oracle.sql

For example, execute the script to create APM database schema tables:

start createtables-oracle<VERSION>.0

For more information about starting SQL *Plus or executing SQL scripts, see the Oracle documentation for the version of the Oracle database you are using.


Appendix C: Using the Lynx text browser on a TIM

The information in this section pertains to the text-based Lynx browser. If your TIM machine is not connected to the network, follow the procedures in this section instead to install the TIM software appliance and configure the TIM.

Lynx provides access to the Wily System Setup pages—without requiring the network.

To use the Lynx text browser, you need:

■ A monitor to attach to the monitoring port.

■ A keyboard to attach to keyboard port.

The monitor and keyboard must be local to the machine that you need to modify; you cannot use PuTTY or a similar tool in this case.

Alternatively, you can use a serial cable to connect from the TIM machine to a computer with a terminal emulator program (such as HyperTerminal) installed.


Installing TIM software using the Lynx browser (see page 273) Using Lynx to configure Wily CEM (see page 275)

Installing TIM software using the Lynx browser

If you prefer, you can use the Lynx text browser to install the TIM software.

You use this browser to install the Wily CEM software and to specify the machine’s IP address and other network settings.

However, if you already know the IP address of a machine after placing it on the network, then you can follow Installing TIM software instead.

Install the TIM software using the Lynx browser:

1. Turn on the TIM machine.

After the system completes the power-on self-test process, the login prompt appears:

<localhost> login:

Installing TIM software using the Lynx browser


2. Type admin and press Enter.

A message displays the last login date and time.

This prompt appears:

Enter terminal type [vt100]:

3. Press Enter to accept the default terminal type and enter the Lynx browser.

The third-party license agreements page appears. (This is the only page you can access until you have accepted the license.)

Tip: For help navigating in the Lynx browser, see Keyboard tips for the Lynx browser (see page 275).

4. Review and accept the license agreement.

Note: If you see an error, such as, "mount: No medium found or Error mounting /media/cdrom," verify that the TIM disc is in the DVD drive. If it is not, call CA Support.

5. Select the packages and select Continue. You must install each .IMAGE file in this order:

a. installonce-update-<version>.image

b. third-party-update-<version>.image

c. tim-complete-<version>.image

After the package or packages have been copied from the disk to the machine, at the bottom of the screen, an alert and then a prompt to log in to Lynx appears.

6. Log in to Lynx with username admin and password quality.

7. Review and accept the license agreement.

IMPORTANT! Do not use the right arrow key. Use the down arrow key to select Next and the Enter key to commit.

The software installation log appears. If you see errors in the log, contact CA Support.

8. Select Finish.

Using Lynx to configure Wily CEM


Keyboard tips for the Lynx browser

Use the arrow keys to navigate through the menu options:

■ up arrow — moves up in current screen

■ down arrow — moves down in current screen

■ right arrow — is the same as the Enter key. It follows the selected link (for example, to the next menu). It does not move right.

■ left arrow — goes back to previously viewed screen

The following table lists the available keys you can use to further navigate in the Lynx browser.

Action Key

Follow the selected link Enter (or right arrow)

Go to the end of a screen End

Go to the next page Spacebar

Get Lynx help ? or h

Go to the Wily System setup menu (main screen) m

Exit Lynx q or Q

Confirm (yes) y or Y


These steps are specific to Lynx text browser behavior when using the locally attached monitor and keyboard.

To modify the Wily CEM system settings using Lynx:

1. Attach the monitor to the monitoring port.

2. Attach the keyboard to a USB port.

3. Turn on and use the monitor and keyboard for the following steps.

4. Turn on the TIM machine.

After the system completes the power-on self-test process, the login prompt appears:

<localhost> login:




A message displays the last login date and time.


Enter terminal type [vt100]:

6. Press Enter.

A message appears briefly:

Alert! Access without authorization denied -- retrying

And, then this prompt appears:

Username for 'system' at server '127.0.0.1':



password:

8. Type the password for the Wily CEM system administrator and press Enter.

The Lynx version of the Wily CEM System Setup menu appears.

9. Use the down arrow key to navigate through the menu options. See Keyboard tips for the Lynx browser (see page 275).

Index 277

Index

<

<Agent_Home> • 17 <APM_Db_Home> • 17 <EM_Home> • 17 <version> • 17

6

64-bit JVM, unsupported for uninstall • 50 64-bit Linux, Wily CEM upgrade • 159

A

administrator password for PostgreSQL changing • 215 compliance with security policies • 70 default • 70 installation worksheet • 250 silent mode settings • 105

agents applying agent customizations • 232 home directory • 17 must be upgraded manually • 155 upgrade compability • 154 upgrading • 231, 232

AIX bundled JVMs • 48 CA EEM installer files • 52 Enterprise Manager JVM requirement • 26 installation modes supported • 52 Java 1.6 patches for UNIX • 40 main installer files • 45 PowerPacks and extensions supported • 38 SAP installer files • 47 silent mode installer • 119

antivirus, pausing during installation • 45 APIs

upgrading • 265 Web Services files • 126

APM database, See also PostgreSQL & Oracle architecture • 16 database name • 70 deciding where to install • 23 description • 14 determining the database to use • 22 exporting the APM database • 204

installing • 70 merging APM databases • 201 moving the APM database to a different machine

• 209 passwords • 54 removing the APM database • 218, 219 requirements • 29 restoring the APM database • 204, 206 root user • 70 scripts • 196, 199, 201, 204, 206, 209, 216, 218 silent mode settings • 99 tess-db-cfg.xml, APM database configuration •

70, 214 upgrading from 9.0 • 223 username restrictions • 102 validations • 70 verifying schema version • 216

architecture • 16

B

backup APM database • 204 before upgrading • 152, 153, 158 Enterprise Manager • 157 non-upgraded scripts • 264 obsolete files post-upgrade • 155 post-upgrade manual tasks • 233 TIMs • 187 Wily CEM • 159

baselines database default location • 68, 261 storage requirements • 28 upgrading • 263

BIN installers console mode • 62 main installer files • 45 SAP main installers • 47 silent mode installer • 119 Workstation installers • 46

browser requirements • 36

C

CA EEM about • 235 CA EEM installer files • 52


removing Wily CEM users and groups • 241 requirements • 37 Safex scripts • 239

CA EULA • See EULA CA Service Desk customizations for Wily CEM • 159,

191 CA Wily APM

architecture highlights • 16 release notes • 13 setup page for TIM • 135, 138 upgrade overview • 173 Wily CEM requirements • 36

CA Wily license • 68, 77 ChangeDetector

installing • 122, 125 PowerPacks and extensions supported • 38 requirements • 38 upgrading • 232 Workstation install • 77

clustering, See also Collectors, MOM, Enterprise Managers installation • 68 installation worksheet • 248 number of collectors per MOM • 68 silent mode settings • 94

code, copying from this manual • 17 Collectors, See also clustering, Enterprise Manager,

MOM installing • 68 number per MOM • 68 silent mode settings • 94

command line, launching installer in GUI mode from • 59

configuring Wily CEM • 138 console mode

about • 61 BIN installers • 62 forcing uninstall • 82 JAR installers • 63 OS/400 (IBMi) • 63 uninstalling • 81 upgrading • 223 z/OS • 64

console, Wily CEM • 143 copying text from this manual • 17 customizations, Wily CEM • 159

D

database, See also SmartStor, Transaction Event, APM database, PostgreSQL APM database validations • 70 APM database validations, silent mode settings •

102 name, APM database • 70 requirements • 28, 29

ddtv directory, renamed during upgrade • 261 defect evidence files in Wily CEM • 159, 191 deployment

architecture highlights • 16 directories

default installation • 66, 127 directory and filename conventions • 17 PostgreSQL default • 70

documentation • 17 domains.xml • 260

E

EMService.conf • 257 end user license agreement, See EULA • See EULA Enterprise Manager

antivirus, pausing during installation • 45 Enterprise Manager includes APM database • 14 home directory • 17 JVM settings, silent mode • 98 license file • 68 manual upgrade • 256 passwords • 54 ports • 93, 95, 247 requirements • 26 silent mode settings • 93 upgrade compatability with agents • 154 users.xml • 77 verifying the installation • 76

EnterpriseManager.properties • 257 EPAgents

manual upgrade • 254, 256, 267 upgrading • 170

ErrorDetector installing • 122, 124 PowerPacks and extensions supported • 38 requirements • 38 upgrading • 232

EULA • 66 CA products • 65, 77 console mode • 61

Index 279

editing • 87 silent mode settings • 90, 91 third-party • 66, 77 upgrading • 225

evidence collection and Python or Perl • 36 executable installer files • 62 exporting the APM database • 204 extensions

installed with Introscope • 121 requirements • 38 upgrading • 232

external component packages • 51 downloading • 51, 87 installation worksheet • 246 specifying during install • 66 upgrading • 225 Workstation install • 77

F

feedback, providing on documentation • 17 files and properties that Introscope does not

upgrade • 263 files and properties that Introscope upgrades • 261 firewall

disabling on 4.5 Wily CEM appliance • 194 Enterprise Manager configuration • 68 Enterprise Manager ports, installation worksheet

• 247, 250 PostgreSQL configuration • 70

G

groups, security • 235, 236 GUI mode

forcing uninstall mode • 82 running installer • 59, 60 upgrading • 223

H

historical data, disk space cap • 68 host

APM database • 70 Enterprise Manager • 66 silent mode settings • 95, 100, 108, 112, 117 WebView • 75 Workstation setting • 77

HP-UX bundled JVMs • 48 CA EEM installer files • 52

console mode • 62 Enterprise Manager JVM requirement • 26 installation modes supported • 52 Java 1.6 patches for UNIX • 40 main installer files • 45 PowerPacks and extensions supported • 38 SAP installer files • 47 silent mode installer • 119

I

IIS, PowerPack for WebServers • 127 image files for TIM • 135, 189 installing

alternate JVM for installer • 26 console mode • 61 default directories • 66 GUI mode on Windows • 59 GUI mode, on UNIX systems • 60 installation modes supported • 52 installation overview checklist • 57 installation, worksheet • 245 installer files • 43 main components • 65 pausing antivirus programs • 45 PowerPacks and extensions • 121 silent mode • 85, 87, 118 specifying JVM for JAR installers • 60 Wily CEM • 129 Workstation • 77

Introscope extensions and PowerPacks • 121 installer files • 43 Introscope and Wily CEM installed together • 14 license file • 76, 77 merging database with Wily CEM • 201 preparing for upgrade • 153 uninstalling Introscope • 81 upgrade overview • 160 upgrade requirements • 41

IntroscopeEnterpriseManager.lax • 257 IntroscopeProbeBuilderWizard.lax • 259 IntroscopeWebView.lax • 258 IntroscopeWebView.properties • 258 IP addresses

IPv4 or IPv6 • 29, 133, 140, 145 TIM monitoring • 140 TIMs • 133


J

JAR installers console mode • 63 requirements • 40 silent mode installer • 119 specifying the JVM • 60

Java 1.6 patches for UNIX • 40 Java Web Start

designating the Java version for Java Web Start • 80

installing the Workstation • 79 JVM • 80 upgrading • 233

JAVA_HOME operator export script • 237 OS/400 • 63 runem.sh and runwv.sh • 254 upgrading Wily CEM operators • 242 z/OS • 64, 118

JVM alternate JVM for installer • 26 command line installation • 60 configuring settings during installation • 66 Enterprise Manager settings • 68 forcing uninstall • 82 installation worksheet • 246 Java 1.6 patches for UNIX • 40 Java Web Start • 80 JVM, ProbeBuilder, upgrading • 231 OS/400 • 63 ProbeBuilder settings • 75 requirements • 26, 35, 36, 40 response file guidelines • 86 silent mode settings • 98, 110, 111, 113 specifying for console mode • 63 specifying for installer • 60 specifying ProbeBuilder arguments • 75 specifying Workstation settings • 77 uninstalling • 81 upgrading • 261 WebView settings • 75 Workstation settings • 77

K

known issues • 17

L

LDAP • 261 LeakHunter

installation • 122, 124 PowerPacks and extensions supported • 38 requirements • 38 upgrading • 232

license agreement for CA products • 66, 77 license file

installation worksheet • 247 installing • 66, 76 upgrading • 225

Linux APM database • 70 bundled JVMs • 48 Enterprise Manager JVM requirement • 26 installation path • 66 main installer files • 45 PowerPack installer file • 47 PowerPacks and extensions supported • 38 SAP installer files • 47 Workstation installer file • 46

Lynx text browser, using • 273, 275

M

MAC address, TIM monitoring • 140 main installer

about • 43 console mode • 61 main installer files • 45 silent mode • 88

main installer files • 45 manual upgrade

APM database • 199 components • 155 configuration file overview • 254 post-upgrade tasks • 233

merging APM databases • 201 modes, installer • See installation modes supported MOM

architecture highlights • 16 installation worksheet • 248 installing • 68

moving the APM database to a different machine • 209

Index 281

N

network TIM configuration for traffic monitoring • 140 TIM monitor interface (eth1, eth2, eth3) • 138 TIM network management settings • 133

O

operating system, PostgreSQL user and service • 70 operators, exporting from Wily CEM • 235 Oracle, See also APM database

determining the database to use • 22 exporting and restoring • 204 manually creating the APM database schema •

267 migrating data from PostgreSQL to Oracle • 210 removing • 219 specifying during Enterprise Manager installation

• 70 OS/400 (IBMi)

bundled JVMs • 48 console mode installation • 63 external component packages • 51 installation modes supported • 52 main installer files • 45 PowerPacks and extensions supported • 38 running an installer with alternate JVM • 50 SAP installer files • 47 silent mode installer • 119 uninstall • 81

osgi, See external component packages • See external component packages

P

passwords Enterprise Manager • 54 PostgreSQL • 70, 215, 250 security • 54 TIM • 194, 252 Wily CEM console • 54

Perl requirement for evidence collection • 36 platform monitors, upgrading • 231 plug-ins in Wily CEM, backing up before upgrading •

159 ports

disabling firewall on former Wily CEM appliance • 194

Enterprise Manager • 68, 247

eth1, eth2, eth3 • 138 firewall configuration • 68, 70 PostgreSQL • 70, 250 re-using TESS (4.5) • 143 unblocking on former Wily CEM appliance • 192 web server • 80 WebView • 75, 251 Workstation • 77

PostgreSQL configuring • 216 default directories • 70 default port • 70 determining the database to use • 22 exporting the APM database • 204 firewall ports • 70 installing or upgrading • 70 Linux limitation • 70, 249 passwords • 54, 70, 215 removing • 218 restoring the APM database • 206 terminal services unsupported on PostgreSQL •

45 troubleshooting non-root install • 217 uninstalling • 220 upgrading • 203 user and service accounts • 70 verifying schema version • 216

PowerPacks included with Introscope • 15 installing • 15, 47, 122, 127 PowerPacks and extensions supported • 38 requirements • 38 silent mode settings • 114 upgrading • 232

ProbeBuilder advanced JVM settings • 75 IntroscopeProbeBuilderWizard.lax • 259 requirements • 40 silent mode settings • 111 upgrading • 231, 256, 267

Python requirement for evidence collection • 36

R

realm, security • 235 Red Hat Linux

CA EEM installer files • 52 installation modes supported • 52 main installer files • 45


PowerPacks and extensions supported • 38 TIM network settings • 133 TIM operating system • 130 TIM requirements • 36

release notes • 13, 17 removing the APM database • 218, 219 response file

alternatives • 86 guidelines • 86 sample • 86

restarting a TIM • 147 restoring the APM database • 204, 206 running an installer with alternate JVM • 50

S

Safex scripts for CA EEM • 239 SAP

console mode install not supported for SAP end users • 59

default installation directory • 66 default port • 68, 247 Expert Center HP-UX console mode • 62 license option disabled during installation • 66 silent mode settings • 117

schema, verifying version of • 216 SDK, upgrading • 265 security

CA Wily APM • 235, 244 passwords • 54 PostgreSQL password • 70 requirements • 37 upgrading Introscope • 244 upgrading Wily CEM operators • 235 users.xml • 77

service (Windows) EMService.conf • 257 Enterprise Manager • 68 renaming during upgrade • 225 silent mode settings • 97, 109 WebView • 75 WVService.conf • 258

silent mode APM Database settings • 99 Enterprise Manager settings • 93, 94, 95, 96, 97,

98 forcing uninstall • 82 main installer settings • 88, 91, 113 PowerPack installer settings • 114

ProbeBuilder settings • 111 response file guidelines • 86 SAP installer settings • 117 uninstalling • 81 upgrade settings • 91 WebView settings • 108, 109, 110 Workstation installer settings • 112

SmartStor directory • 68, 261 requirements • 28 silent mode settings • 96, 97 sizing recommendation • 68

SNMP PowerPacks and extensions supported • 38 SNMP Adapter, installation • 122, 125 SNMP requirements • 41

SOA Performance Management installing • 122 PowerPacks and extensions supported • 38 requirements • 38

Solaris bundled JVMs • 48 CA EEM installer files • 52 Enterprise Manager JVM requirement • 26 installation modes supported • 52 Java 1.6 patches for UNIX • 40 main installer files • 45 PowerPacks and extensions supported • 38 SAP installer files • 47 silent mode installer • 119

standalone PowerPack installer • 121 SUSE

bundled JVMs • 48 installation modes supported • 52 PowerPacks and extensions supported • 38

synchronizing TIMs • 146 System Setup pages, accessing • 142 SYSVIEW

installation • 122, 125 PowerPacks and extensions supported • 38

T

terminal services, not supported for PostgreSQL • 45, 249

TESS (4.5) disabling monitors before upgrading TIM • 189 existing data • 70 re-using • 143, 159, 192, 194, 195

Index 283

uninstalling • 194 tess.customer.properties file • 159, 190 tess-db-cfg.xml, APM database configuration • 70,

214 time settings • 53, 137 TIMs

configuring monitoring • 140 configuring network management • 133, 252 configuring network monitor interface • 138 installing from Lynx text browser • 273 operating system installation • 130 requirements • 36 restarting • 147 software appliance • 15 time zone • 137 TIMs, passwords • 54, 252 uninstalling • 148 upgrading • 189 verifying communication with Enterprise

Manager • 146 verifying configuration • 146

Transaction Event database backing up settings before upgrade • 159 default location • 68, 261 location and storage duration • 68, 249 upgrading • 261

U

uninstalling forcing the mode • 82 Introscope • 81 silent or console mode • 81 TESS (4.5) • 194 TIM • 148 z/OS • 82

UNIX bundled JVMs • 48 default installation directory • 66 external component packages • 51 GUI mode installer • 60 headless installation • 60 Java 1.6 patches for UNIX • 40 main installer files • 45 passwords • 54 PostgreSQL installation directory • 70 PowerPack installer file • 47 PowerPacks and extensions supported • 38 response file guidelines • 86

SAP installation directory • 66 SAP installer files • 47 silent mode installer • 119 uninstalling • 81

upgrading agents • 231, 232 automatic or manual • 155 CA Wily APM one product at a time • 198 component compatibility • 154 defect data storage changes • 159 editing the response file • 228 files and properties not upgraded • 263 files and properties that are upgraded • 261 manual • 253 PostgreSQL from Wily CEM 4.5 • 197 preparing for • 152, 153, 158 security • 235, 244 silent mode • 91 upgrade overviews • 167, 176, 182, 197 upgrade requirements • 41

URL TIM setup page • 144, 145 Wily CEM console • 142 Workstation Java Web Start • 79

user accounts passwords • 54 upgrading Wily CEM operators • 235 username restrictions • 102

users.xml upgraded • 254 users.xml, upgrading Wily CEM to Local users •

242 Workstation installation • 77

V

verifying Enterprise Manager installation • 76 TIM communication with Enterprise Manager •

146 TIM configuration • 146 Workstation installation • 78

W

web services APIs installation • 122, 126 upgrading • 265

Web Start Workstation • 79 WebView


IntroscopeWebView.lax • 258 IntroscopeWebView.properties • 258 manual upgrade • 254, 257 requirements • 36 silent mode settings • 108, 109, 110 WebView, settings • 75, 251 Windows service • 75

Wily CEM backup customizations before upgrading • 159 configuring network management • 133, 252 configuring network monitor interface • 138 Enterprise Manager configuration • 190 evidence collection requirements • 36 Introscope and Wily CEM installed together • 14 merging database with Introscope during

upgrade • 201 passwords • 54 post-upgrade manual tasks • 233 preparing for upgrade • 158 System Setup page • 144 TIM installation • 129 TIM requirements • 36 TIM upgrade • 189 uninstalling TESS (4.5) • 194 upgrade overview • 179 upgrade requirements • 41 upgrading a TIM • 189 upgrading security • 235 Wily CEM console • 142, 143, 145, 252

Windows bundled JVMs • 48 CA EEM installer files • 52 console mode unsupported • 61 default installation directory • 66 Enterprise Manager JVM requirement • 26 Enterprise Manager service • 68, 97 external component packages • 51 installation modes supported • 52 main installer files • 45 passwords • 54 PostgreSQL installation directory • 70 PowerPack installer file • 47 PowerPacks and extensions supported • 38 response file guidelines • 86 SAP installation directory • 66 SAP installer files • 47 uninstaller • 81 WebView as a service • 75, 109 Workstation installer file • 46

worksheet, installation • 245 Workstation

designating the Java version for Java Web Start • 80

installing • 77 installing new no upgrade • 231 installing the Workstation • 79 password • 54 requirements • 34 silent mode settings • 112, 113 starting using URL • 79 verifying installation • 78 Workstation, JVM settings • 79

Workstation installer file • 46 WVService.conf • 258

Z

z/OS external component packages • 51 installation modes supported • 52 installing in console mode • 64 installing in silent mode • 118 main installer files • 45 PowerPacks and extensions supported • 38 running an installer with alternate JVM • 50 uninstalling on • 82 upgrading manually • 155