istrobe install

8/18/2019 Istrobe Install

1/84

iStrobeInstallation Guide

Release 5.1


2/84

2 iStrobe Installation Guide

Please direct questions about iStrobe

or comments on this document to:

iStrobe Customer Support

http://go.compuware.com

This document and the product referenced in it are subject to the following legends:

Copyright 2014 Compuware Corporation. All rights reserved. Unpublished rights reserved under theCopyright Laws of the United States.

U.S. GOVERNMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject torestrictions as set forth in Compuware Corporation license agreement and as provided in DFARS227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995),FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. Compuware Corporation.

This product contains confidential information and trade secrets of Compuware Corporation. Use,disclosure, or reproduction is prohibited without the prior express written permission of CompuwareCorporation. Access is limited to authorized users. Use of this product is subject to the terms andconditions of the user’s License Agreement with Compuware Corporation.

iStrobe, AutoStrobe, and Strobe, are trademarks or registered trademarks of Compuware Corporation.

AD/Cycle, BookManager, CICS, DB2, IBM, IMS/ESA, Language Environment, MQSeries, VisualGen, andVTAM are trademarks of International Business Machines Corporation. Microsoft is a registered trademarkof Microsoft Corporation. Windows, Windows NT, and Windows 98 are trademarks of MicrosoftCorporation.

Adobe® Reader® is a trademark of Adobe Systems Incorporated in the United States and/or othercountries.

All other company and product names are trademarks or registered trademarks of their respective owners.

Doc. CWISDX5E

September 23, 2014

http://go.compuware.com/http://go.compuware.com/http://go.compuware.com/


3/84

3

Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7How This Guide is Organized. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7How to Use This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8iStrobe Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8iStrobe 3rd Party Licensing Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Compuware iStrobe Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Compuware Go Customer Support Website . . . . . . . . . . . . . . . . . . . . . . . . . 8Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Corporate Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 1. Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11iStrobe System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installing iStrobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Server Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Server Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Web Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12File Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Database Server Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Individuals to Participate in the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Installation Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Web Container Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Database Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Security Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 2. Upgrading iStrobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Security Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Migrating from Supported Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 3. Installing or upgrading iStrobe on Windows with Tomcat . . . . . . . . . . 17Before Beginning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Installing or upgrading iStrobe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Starting and Stopping the iStrobe Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Starting the iStrobe Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Stopping the iStrobe Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Starting and Stopping the iStrobe SMF Manager . . . . . . . . . . . . . . . . . . . . . . . . 22Starting the iStrobe SMF Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Stopping the iStrobe SMF Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Using the iStrobe Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 4. Installing or upgrading iStrobe on Linux with Tomcat . . . . . . . . . . . . . 23Before Beginning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Installing or upgrading iStrobe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Starting and Stopping the iStrobe Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Installing and Starting the iStrobe Manager Daemon . . . . . . . . . . . . . . . . 27Stopping the iStrobe Manager Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Restarting the iStrobe Manager Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . 28


4/84


Stopping and Uninstalling the iStrobe Manager Daemon . . . . . . . . . . . . . 28Starting and Stopping the iStrobe SMF Manager . . . . . . . . . . . . . . . . . . . . . . . . 28

Installing and Starting the iStrobe SMF Manager Daemon. . . . . . . . . . . . . 28Stopping the iStrobe SMF Manager Daemon . . . . . . . . . . . . . . . . . . . . . . . 28Restarting the iStrobe SMF Manager Daemon. . . . . . . . . . . . . . . . . . . . . . . 28Stopping and Uninstalling the iStrobe SMF Manager Daemon . . . . . . . . . 28

Using the iStrobe Web Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 5. Installing or upgrading iStrobe on Linux with WebSphere . . . . . . . . . 31Before Beginning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Installing or upgrading iStrobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Continuing install using JCL and the IBM WSADMIN tool . . . . . . . . 34Continuing install using WebSphere’s Integrated Solutions

Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Starting and Stopping the iStrobe Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Installing and Starting the iStrobe Manager Daemon. . . . . . . . . . . . . . . . . 39Stopping the iStrobe Manager Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Restarting the iStrobe Manager Daemon. . . . . . . . . . . . . . . . . . . . . . . . . . . 39Stopping and Uninstalling the iStrobe Manager Daemon . . . . . . . . . . . . . 39

Starting and Stopping the iStrobe SMF Manager . . . . . . . . . . . . . . . . . . . . . . . . 40

Installing and Starting the iStrobe SMF Manager Daemon. . . . . . . . . . . . . 40Stopping the iStrobe SMF Manager Daemon . . . . . . . . . . . . . . . . . . . . . . . 40Restarting the iStrobe SMF Manager Daemon. . . . . . . . . . . . . . . . . . . . . . . 40Stopping and Uninstalling the iStrobe Manager Daemon . . . . . . . . . . . . . 40


Chapter 6. Installing or upgrading iStrobe on z/OS System Serviceswith Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Before Beginning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Installing or upgrading iStrobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Running the iStrobe Manager and the iStrobe SMF Manager using JZOS . . . . . 47

Executing the iStrobe Jobs as Started Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 49iStrobe Manager as a started task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

iStrobe SMF Manager as a started task . . . . . . . . . . . . . . . . . . . . . . . . . 49Changing the Time Zone for iStrobe Manager . . . . . . . . . . . . . . . . . . . . . . 50Modifying Java Heap Size for iStrobe Manager . . . . . . . . . . . . . . . . . . . . . . 50


Chapter 7. Installing or upgrading iStrobe on z/OS System Serviceswith WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Before Beginning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Installing or upgrading iStrobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Continuing install using JCL and the IBM WSADMIN tool . . . . . . . . 54Continuing install using WebSphere’s Integrated Solutions

Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Running the iStrobe Manager and the iStrobe SMF Manager using JZOS . . . . . 59

Executing the iStrobe Jobs as Started Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 61iStrobe Manager as a started task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61iStrobe SMF Manager as a started task . . . . . . . . . . . . . . . . . . . . . . . . . 62

Changing the Time Zone for iStrobe Manager . . . . . . . . . . . . . . . . . . . . . . 62Modifying Java Heap Size for iStrobe Manager . . . . . . . . . . . . . . . . . . . . . . 62


Chapter 8. Configuring iStrobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Apache Derby Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Microsoft SQL Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67


5/84

5

IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67DB2 for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67DB2 for Linux, Unix, and Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Security Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Enable security using LDAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Enable security using X.509 (Smart Card) . . . . . . . . . . . . . . . . . . . . . . . . . 70Enable security using X.509 with LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Enable security using Kerberos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Disable security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Other Configuration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Chapter 9. Customizing iStrobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Changing the Location of the iStrobe Log File . . . . . . . . . . . . . . . . . . . . . . . . . 73

Modifying the log4j.xml file to Change the Location of the iStrobeLog File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Passing a JVM Parameter to Change the Location of the iStrobe L og File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Installing the Compuware Workbench Web-Based Plug-In for iStrobe . . . . . . 74

Chapter 10. iStrobe Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

iStrobe Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75How to Use the API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Requesting WSDL URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Web Service Request to iStrobe Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Descriptions of Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76connectTest Web Service Request to iStrobe Server - Detail . . . . . . . . 77

Java Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Using SSL with the Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Apache Tomcat Server Configuration for SSL. . . . . . . . . . . . . . . . . . . . . . . 78Web Service Java Client Using SSL Connection . . . . . . . . . . . . . . . . . . . . . 79

Chapter 11. Uninstalling iStrobe 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Uninstalling iStrobe on Windows with Tomcat . . . . . . . . . . . . . . . . . . . . . . . . 81

Uninstalling iStrobe on Linux with Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Uninstalling iStrobe on Linux with WebSphere . . . . . . . . . . . . . . . . . . . . . . . . 81Uninstalling iStrobe on z/OS USS with Tomcat. . . . . . . . . . . . . . . . . . . . . . . . . 82Uninstalling iStrobe on z/OS USS with WebSphere. . . . . . . . . . . . . . . . . . . . . . 82

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83


6/84



7/84

7

Introduction Intro

This guide provides instructions on how to install iStrobe. iStrobe is an applicationperformance analysis product designed to be used on workstations with the Strobe MVSApplication Performance Measurement System. iStrobe uses a Web browser that enablesyou to create a custom view of Strobe MVS measurement data.

After installing iStrobe, you will be able to view the sample Performance Profile datapackaged with it.

To create and analyze new Strobe measurement data using iStrobe, do the following:

1. Set up Strobe to communicate with iStrobe, as described in the Strobe Installation andCustomization Guide.

2. Use Strobe to measure an application’s performance, create an iStrobe PerformanceProfile data file, and store it in a directory where iStrobe users can access it, as

described in the Strobe User Guide.

Intended Audience

This installation guide is intended for the database administrator or individual(s)installing iStrobe. You should be familiar with administering the operating system, yournetwork security policies, and your web server (Tomcat or WebSphere). If you areunfamiliar with any of the prerequisite software, contact your administrator for help.

How This Guide is Organized

This guide contains the following chapters.

Chapter 1, “Installation Overview”

Chapter 2, “Upgrading iStrobe”

Chapter 3, “Installing or upgrading iStrobe on Windows with Tomcat”

Chapter 4, “Installing or upgrading iStrobe on Linux with Tomcat”

Chapter 5, “Installing or upgrading iStrobe on Linux with WebSphere”

Chapter 6, “Installing or upgrading iStrobe on z/OS System Services with Tomcat”

Chapter 7, “Installing or upgrading iStrobe on z/OS System Services with WebSphere”Chapter 8, “Configuring iStrobe”

Chapter 9, “Customizing iStrobe”

Chapter 10, “iStrobe Web Service”

Chapter 11, “Uninstalling iStrobe 5.1”


8/84


How to Use This Guide

If you are installing iStrobe for the first time, you should read the following chapters:

• “Installation Overview”

• The appropriate chapter for your operating system:

– Chapter 3, “Installing or upgrading iStrobe on Windows with Tomcat”

– Chapter 4, “Installing or upgrading iStrobe on Linux with Tomcat”

– Chapter 5, “Installing or upgrading iStrobe on Linux with WebSphere”

– Chapter 6, “Installing or upgrading iStrobe on z/OS System Services withTomcat”

– Chapter 7, “Installing or upgrading iStrobe on z/OS System Services withWebSphere”

• Chapter 8, “Configuring iStrobe”

If you want to customize iStrobe, read Chapter 9, “Customizing iStrobe”.

If you are upgrading your iStrobe installation, read Chapter 2, “Upgrading iStrobe”.

iStrobe Publications

To learn more about using iStrobe:

• See the iStrobe online help within the product.

• Visit Compuware’s FrontLine at http://frontline.compuware.com and selectiStrobe, for the latest technical information on iStrobe.

iStrobe 3rd Party Licensing DocumentationTo view iStrobe 3rd party licensing documentation, refer to the legal subdirectory that isincluded as part of the iStrobe installation.

Compuware iStrobe Customer Support

Compuware provides a variety of support resources to make it easy for you to find theinformation you need.

Compuware Go Customer Support Website

You can access online information for Compuware products via our Compuware Gocustomer support website at http://go.compuware.com.

Compuware Go provides access to critical information about your Compuware products.You can review frequently asked questions, read or download documentation, accessproduct fixes, or e-mail your questions or comments. The first time you accessCompuware Go, you are required to register and obtain a password. Registration is free.

Compuware now offers User Communities, online forums to collaborate, network, andexchange best practices with other Compuware solution users worldwide. To join, go tohttp://groups.compuware.com.

http://http//frontline.compuware.comhttp://go.compuware.com/http://groups.compuware.com/http://groups.compuware.com/http://go.compuware.com/http://http//frontline.compuware.com


9/84

Introduction 9

Contacting Customer Support

Phone

• USA and Canada: 1-800-538-7822 or 1-313-227-5444.• All other countries: Contact your local Compuware office. Contact information is

available at http://go.compuware.com.

Web

You can report issues via the Quick Link Create & View Support Cases on theCompuware Go home page.

Note: Please report all high-priority issues by telephone.

Mail

Compuware Customer Support Compuware Corporation One Campus Martius Detroit, MI 48226-5099

Corporate Website

To access Compuware’s site on the Web, go to http://www.compuware.com .

The Compuware site provides a variety of product and support information.

http://go.compuware.com/http://www.compuware.com/http://www.compuware.com/http://go.compuware.com/


10/84



11/84

11

Chapter 1.

1Installation Overview Chap 1

This chapter provides an overview of the different hardware and software componentsneeded to install iStrobe. It also identifies those individuals who will participate in theiStrobe installation.

Note: When iStrobe is installed on a standalone workstation, it supports a single user.To support more than one user, iStrobe must be installed on a server.

iStrobe System Overview

The diagram below is an overview of the components and data flow in iStrobe. iStrobe

5.1 is backward compatible with iStrobe. You may install iStrobe components on thesame or separate servers. Refer to the operating systems-specific installation chapters forsetup and security considerations.

Figure 1-1. iStrobe Components and Data Flow


12/84


Starting at the bottom of the diagram, Strobe collects performance statistics for your z/OSapplications. Strobe 4.1 and newer versions transfer the performance metrics directly tothe iStrobe Manager. The iStrobe Manager then stores the Profiles on your file server aswell as loading them into a database. The Manager listens for transfer requests fromStrobe, processes update requests from the Web server, and optionally watches for newprofiles transferred from Strobe and prepares them for viewing.

The iStrobe web application can authenticate all users against your corporate

authentication server, so you may secure performance measurements and iStrobefunctionality. In addition, user preferences and state information are stored in thedatabase instead of browser cookies. The individual performance reports use the xml filesfor input; the Strobe Insight reports use the database. The end user runs iStrobe using abrowser.

Requirements

Installing iStrobe

If your site intends to use both Strobe and iStrobe, Compuware recommends that you

install the latest version of iStrobe before installing the latest version of Strobe in orderto utilize any new measurement functionality in iStrobe.

Server Software Requirements

For complete server software requirements, refer to the details described in the iStrobe Release Notes for this version.

Server Hardware Requirements

Web Server Requirements

Ensure that the Web server where you will be installing iStrobe meets the followinghardware requirements:

• Minimum of 1 GB available disk space

• Minimum 2 GB of RAM

• Minimum 2 GHz processor

Note: These are the minimum requirements for a server dedicated to iStrobe with lessthan 20 users. If you experience performance problems, you may need toincrease memory or processor speed.

File Server Requirements

The following are the minimum hardware and software requirements for the file serverwhere iStrobe Performance Profiles are stored:

• 1 GB RAM

• Each Performance Profile requires 0.2-50 MB of disk space, depending on themeasured application and the Strobe measurement parameters. Your spacerequirements may vary widely depending on the number of users and how manyprofiles they keep.


13/84

Installation Overview 13

Database Server Requirements

iStrobe supports Microsoft SQL Server, Oracle, and IBM DB2. Refer to your databasesystem documentation for the minimum hardware requirements. iStrobe data storagerequirements vary from 300k to 50MB per profile, depending on the measurement taken.Processor usage also varies, depending on the number of users and their use of StrobeInsight reports.

Individuals to Participate in the Installation

This section identifies individuals who should participate in the installation and theinformation needed to complete the installation.

Installation Environment

The installation environment requires the following:

• An administrator familiar with either the Windows, USS or z/OS, or zLinux,environment, as is appropriate for your site. The user performing the installation

needs to have the appropriate authorizations in the selected environment.

Web Container Environment

The web container environment requires the following:

• An administrator familiar with either Tomcat services or WebSphere ApplicationServer.

Database Environment

If you are going to use Strobe Insight with iStrobe, you must install a DBMS whenprompted during the install.

The database environment requires the following:

• A database administrator (DBA) to create the database used in your environment.

– Microsoft SQL Server– Oracle Database– IBM DB2 for z/OS– IBM DB2 for Linux, Unix, and Windows.

Complete requirements for installing a database are detailed in Chapter 8, “ConfiguringiStrobe”.

Security Environment

The security features in iStrobe can utilize LDAP security servers for user authentication.To implement LDAP, the iStrobe server post-installation configuration requires a securityadministrator with knowledge of LDAP security settings.


14/84



15/84

15

Chapter 2.

2Upgrading iStrobe Chap 2

The iStrobe 5.1 installation wizard includes an option to upgrade from either iStrobe 4.3or iStrobe 4.4.

When prompted by the wizard for the installation location, enter the location of yourcurrent installation. During this process, the existing database is upgraded.

After the database upgrade is complete, you are prompted to synchronize your profiles.Any changes to customized or canned reports are lost.

CAUTION: If you are upgrading using USS, you must shut down the iStrobe Managerservice before beginning the upgrade.

If you are using Tomcat, you must restart the Tomcat server after completingthe upgrade installation.

Security Considerations

If you want to enable security in iStrobe 5.1, you will need to configure that in theiStrobe interface after the upgrade.

Any browsers that remained open during the upgrade should be closed and reopened toreflect the new security configuration.

IMPORTANT NOTE WHEN UPGRADING FROM 4.4.0:

If you are upgrading from iStrobe 4.4.0 to iStrobe 5.1.0, and you want the upgrade tomaintain the security settings (LDAP or X.509) set in Strobe 4.4.0, you must copy thefollowing two files identified in the table below before beginning the upgrade. If youdo not copy these files, but want to enable security in iStrobe 5.1.0, you mustreconfigure security in the iStrobe interface after completing the upgrade.

For additional security installation details, refer to “Security Configuration” on page 69.

Migrating from Supported Releases

When upgrading from either iStrobe 4.3 or 4.4 to iStrobe 5.1, be aware of the followingmigration considerations:

• Existing iStrobe repository connection information will be used in the upgrade.

• Profiles which may have been contained in multiple sub-directories in the supportedrelease will be moved to a single profile directory in the upgraded release.

From To

/WEB-INF/security.properties

/manager/cfg/security.properties.old

/WEB-INF/ldapControl.properties

/manager/cfg/ldapControl.properties.old


16/84



17/84

17

Chapter 3.

3Installing or upgrading iStrobe on Windows with

TomcatChap 3

A Windows Server Administrator should install or upgrade iStrobe for departmental orcorporate use.

End-users with administration authority on their workstation can do a standaloneworkstation install for their own use.

Before you begin the iStrobe install for Windows determine where you will store yourPerformance Profiles.

When Performance Profiles are stored on the machine where you install iStrobe then youmay use the “local/system” for both the Tomcat service and the iStrobe Manager service.

This is usually the case for a standalone workstation install.

When Performance Profiles are stored on a file server, you need domain IDs for bothTomcat and iStrobe Manager services. The IDs need authority to run a service. The ProfileDirectory permissions for the iStrobe Manager must include both update and create. Andthe Tomcat service ID must have read access to the Profile directory.

Before Beginning

Before beginning the installation, you should have the following for your iStrobeManager and Server:

• Ensure that JAVA_HOME is defined as an environment variable and set to the fullpath of the JDK directory.

• The ID and password for the iStrobe Manager service.

• The ID and password for the Tomcat service.

• A port number for the iStrobe Manager to listen on (the default is 24354, whichshould not conflict with most systems).

• A port number for the iStrobe SMF Manager to listen on (the default is 24355).


If you are upgrading from iStrobe 4.4.0 to iStrobe 5.1.0, and you want the upgrade tomaintain the security settings (LDAP or X.509) set in Strobe 4.4.0, you must copy thefollowing two files identified in the table below before beginning the upgrade. If you

do not copy these files, but want to enable security in iStrobe 5.1.0, you mustreconfigure security in the iStrobe interface after completing the upgrade.

From To






18/84


The installation does the following:

• Installs the iStrobe Manager as a service.

• Installs the iStrobe SMF Manager as a service. You must manually start the iStrobeSMF Manager.

• Optionally installs Tomcat if it was initiated by the user during the installation setup.

• Deploys the iStrobe web application in Tomcat.

Installing or upgrading iStrobe

1. Insert the product CD (or FTP image). If you have Internet Explorer, the CD browseropens; if it does not, run setup.exe from the root folder of the CD.

Note: If installing from an FTP image, run setup.exe from the root of that image.

2. Click Install iStrobe for Windows on the CD browser.

The Introduction dialog box appears.

3. Click Next. The License agreement dialog box appears.

4. Read the license agreement, click the I accept the terms. . . radio button, and clickNext. The Application server dialog box appears.

5. Select Tomcat then click Next. The Supported platforms for Tomcat dialog boxappears.

6. Read the supported platform information to ensure that you plan to use a supportedoperating system, then click Next. A dialog box appears asking if you are going tostore your performance profiles on this server.

7. Select Yes or No to answer the question of whether or not you intend to store yourperformance profiles on this server. Click Next. The Install folder dialog boxappears.

8. Accept the default path or enter the path to the location where you want to installiStrobe and click Next. The iStrobe Manager dialog box appears.

– If you are performing an upgrade of a previous version of iStrobe, you are notifiedthat a previous version of iStrobe exists. Click OK.

Note: At the completion of an upgrade installation, you must migrate profiles for thoseprofiles existing from iStrobe version 4.1.

9. From the iStrobe Manager dialog box, enter the following, and then click Next:

– For a new installation• Manager Host• Manager Port

• Service Name• SMF Manager Port– For an upgrade installation

• Service Name• SMF Manager Port

The Tomcat Installation dialog box appears.

Note: If you are not storing your performance profiles on this server, you areprompted to enter the Domain\User ID and Password for the iStrobeManager service before continuing to the Tomcat installation. The User IDmust have read/write permission to the directory where Performance Profilesare stored.


19/84

Installing or upgrading iStrobe on Windows with Tomcat 19

10. The Tomcat installation requires that Tomcat already exists on this machine or thatyou now install it.

– If Tomcat is not installed on this machine, select Install to install Tomcat duringthe iStrobe installation, and then click Next. The Web Application Name dialogbox appears.

– If Tomcat is already installed on this machine, select Locate to locate where

Tomcat is currently installed, and then click Next. The Tomcat Folder dialog boxappears. Choose the folder where Tomcat is installed and click Next. The WebApplication Name dialog box appears.

11. If you want to rename the iStrobe web application, enter a new name. This name isused in the URL to access iStrobe. Click Next.

– If you are doing a new installation, the iStrobe Repository dialog box appears.

Note: The webserver ID needs update permissions to this folder.

– If you are doing an upgrade of an existing installation, the Pre-installationsummary dialog box appears. Continue with step 13 on page 20.

12. Select a database to use—either the default repository or a DBMS.

Note: When you choose the default repository (Derby) instead of a DBMS, you willnot be able to use the iStrobe SMF Manager.

If you choose the default repository:

– Default repository (Derby):Enter the following as prompted, and then click Next:

• Location of the repository folder (where to place Derby). Accept the default path, or type an absolute path, for storing profile data andreport definitions.


• Port number

If you choose a DBMS repository:

– Microsoft SQL Server :Enter the following as prompted, and then click Next:

• Database User ID• Password for the database user ID• Schema• Database Server• Port• Database Name• Instance Name—if you select an instance name other than the default, the

port value is ignored.

– Oracle:Enter the following as prompted, and then click Next:

• Database User ID• Password for the Database User ID• Schema• Read and accept the license agreement• Database Server• Port• Database Name


20/84


– IBM DB2 for LUW:Enter the following as prompted, and then click Next:

• Database User ID• Password for the Database User ID• Schema• Database Server• Port

• Database Name• Folder for the IBM JDBC driver (db2jcc.jar) location

– IBM DB2 for z/OS:Enter the following as prompted, and then click Next:

• Database User ID (the database ID must have at least the minimum privilegesas specified in “DB2 for z/OS” on page 67)

• Password for the Database User ID• Schema• Database Server (DNS name)• Port• Location Name• Database.Tablespace Name• Folder for the IBM JDBC driver (db2jcc.jar) location

The Pre-installation summary panel appears.

13. Review the installation information in the Pre-installation summary dialog box. Ifit is correct, click Install to start the iStrobe installation. Otherwise, click Previous and revise the installation settings as necessary. The Installation complete dialogbox appears. Click Done to exit the installer.

14. If you are using a DBMS other than the default (Derby) repository, you mayoptionally start the iStrobe SMF Manager by referring to “Starting and Stopping theiStrobe Manager” on page 21.

Notes:

– After starting the iStrobe SMF Manager, be sure to return to this step andcontinue the installation as detailed below.

– You may need to restart Tomcat before opening the iStrobe interface. If you needhelp deploying either the istrobe.war file or the iStrobe application, refer toApache’s website for the Tomcat Manager App How-To in the Tomcat User’s Guide for your version of Tomcat.

15. The iStrobe software installation is complete.

16. Open iStrobe by pointing your web browser to:

:/

where:

– host address is the name of the server where you just installed iStrobe.

– application server port number is the port Tomcat is listening on, which is 8080 bydefault. This is optional if you have IIS installed. If you are not sure of the porton which Tomcat is listening, you can find it in the catalina log file.

– iStrobe application name is the name you entered in step 11 on page 19.

Ex. http://myserver:8080/istrobe

Note: The recommended Tomcat memory settings are as follows:

• Initial memory pool field is set to 1024 MB or greaterEx. (-Xms1024m)


21/84

Installing or upgrading iStrobe on Windows with Tomcat 21

• Maximum memory pool field is set to 1536 MB or greaterEx. (-Xmx1536m)

• Java HEAP storage memory is set to 512 MB or greater

Ex. (Perm size -XX:PermSize=512m -XX:MaxPermSize=512m).

When running as a Windows service:

• Add the following two lines to the JAVA Options section:

-XX:PermSize=256m -XX:MaxPermSize=1024m

• Change the initial memory pool to 1024 MB.

• Change the maximum memory pool to 1536 MB.

When running as a Windows process:

• Modify catalina.bat to set JAVA_OPTS as follows:

set JAVA_OPTS=-Djava.awt.headless=true

-Dfile.encoding=UTF-8 ^

-server -Xms1024m -Xmx1536m ^-XX:PermSize=256m -XX:MaxPermSize=512m ^

Note: You may alternatively define memory settings from the commandline. Refer to Apache’s website for the Tomcat Windows Service How-To in the Tomcat User’s Guide for your version of Tomcat.

Ex.

\bin\tomcat.exe //US// --JvmMs=1024

\bin\tomcat.exe //US// --JvmMx=1500

\bin\tomcat.exe //US//++JvmOptions=-XX:MaxpermSize=1024m

17. Refer to Chapter 8, “Configuring iStrobe” for complete configuration considerations.

Starting and Stopping the iStrobe Manager

The iStrobe Manager is installed as a service and by default comes up with a Startup typeof Automatic.

Starting the iStrobe Manager

Bring up the Services application (Administrative Tools). To start the iStrobe Manager,select the Compuware iStrobe Manager service and click Start the service.

If you do not want the iStrobe Manager to start every time the Windows machine isstarted, select the Compuware iStrobe Manager service and change the Startup type toManual. The next time Windows starts up, the service will not start.

Stopping the iStrobe Manager

Bring up the Services application (Administrative Tools). To shut down the iStrobeManager, select the Compuware iStrobe Manager service and click Stop the service.


22/84


Starting and Stopping the iStrobe SMF Manager

By default, the iStrobe SMF Manager does not come up, but a service is created. It iscreated with a Startup type of Manual.

Starting the iStrobe SMF ManagerBring up the Services application (Administrative Tools). To start up the iStrobe SMFManager, select the Compuware iStrobe Manager SMF service and click Start the service.

To have the iStrobe SMF Manager start every time the Windows machine is started, findthe Compuware iStrobe Manager SMF service. If the Startup type is Manual, change it toAutomatic. The next time Windows starts up, the service will start.

Stopping the iStrobe SMF Manager

Bring up the Services application (Administrative Tools). To shut down the iStrobe SMFManager, select the Compuware iStrobe Manager SMF service and click Stop the service.

Using the iStrobe Web Application

Before using the iStrobe web application, ensure the iStrobe Manager is running.

Open iStrobe by pointing your web browser to:

:/

where:


– application server port number is the port Tomcat is listening on, which is 8080 by

default. This is optional if you have IIS installed. If you are not sure of the porton which Tomcat is listening, you can find it in the catalina log file.

– iStrobe application name is the name you entered in step 11 on page 19.



23/84

23

Chapter 4.

4Installing or upgrading iStrobe on Linux with Tomcat Chap 4

A server administrator should install or upgrade iStrobe in a Linux environment.

Before you begin the iStrobe installation, determine where you will store yourPerformance Profiles and how many ways they are transferred from z/OS to the directorywhere they are stored for iStrobe.

If you are only running Strobe version 4.X, all profiles are transmitted directly to theiStrobe Manager daemon. Therefore, the ID used to run the daemon is always the ownerand is the only ID that needs write access to the profiles and quarantine directories.

Before Beginning

Before beginning the installation, you should have the following for your iStrobeManager and Server:

• A supported version of Java installed and configured.

• A supported version of Tomcat installed and configured.

• The ID and password for the iStrobe Manager daemon with full-control-access to theHFS/ZFS directories you plan to use for the performance profiles.

• A port number for the iStrobe Manager to listen on (the default is 24354, whichshould not conflict with most systems).

• A port number for the iStrobe SMF Manager to listen on (the default is 24355).



The iStrobe installation may require up to 250 MB of temporary space during theinstallation. When the installation is complete, the temporary installation files areremoved.

By default, the /tmp directory is used for temporary disk space during the install. If analternate location for temporary disk space is needed, the following parameter can beused:

From To






24/84


-Dlax.nl.env.IATEMPDIR

For example, the following commands may be entered either individually at thecommand prompt or in a shell script:

export TMPDIR=/sample directory/tmp

export JAVA_HOME=/usr/lpp/java/J6.0

export PATH=$JAVA_HOME/bin:$PATH

export LIBPATH=$JAVA_HOME/lib:$LIBPATH:.

cd /iStrobe-install-dir/Linux/Disk1/InstData/NoVM

./install.bin -Dlax.nl.env.IATEMPDIR=$TMPDIR


• Installs the iStrobe Manager and sets it up as a daemon by putting script in the/etc/init.d directory. The daemon is enabled for run-levels 3 and 5 so that, during areboot of the system, the Manager starts without manual intervention.

• Creates a shell script to install the iStrobe SMF Manager and sets it up as a daemon by

putting script in the /etc/init.d directory. The daemon is enabled for run-levels 3 and5 so that, during a reboot of the system, the Manager starts without manualintervention.

• Deploys the iStrobe Web application under Tomcat.


1. Be sure that you have a supported version of Tomcat installed on the machine ontowhich you are installing or upgrading iStrobe.

2. Transfer the contents of the following folder from the product CD (or FTP image) toyour system:

:\cpwr\Linux

3. Log on to your system, navigate to where you have transferred the files, and locatethe directory where install.bin is stored.

4. Issue the following commands individually or in a shell script:

export JAVA_HOME=


./install.bin -i console

Note: Be sure to execute the commands in the directory where install.bin is located.

You must be logged in as a super user (root) to allow the daemon installation andyou must have execute permission on install.bin. You may need to have the /sbinand /usr/sbin directories in your path.

The Introduction panel appears.

5. After reading the panel, press Enter . The License agreement panel appears.

6. Read the license agreement, pressing Enter until you have scrolled through and readthe entire agreement.

7. Type Y and press Enter to accept the terms of the license agreement. TheApplication server panel appears.


25/84

Installing or upgrading iStrobe on Linux with Tomcat 25

8. Select Tomcat and press Enter . The Supported platforms for Tomcat panel appears.

9. Read the supported platform information to ensure that you plan to use a supportedoperating system, then press Enter . The Install folder panel appears.

10. Enter the path to the location where you want to install or upgrade iStrobe.

– For a new installation, accept the default path or type an absolute path and pressEnter . Confirm the path and press Enter . You must have permission to install to

the directory you choose. The iStrobe Manager panel appears.

– For an upgrade of an existing installation, enter the path to the existinginstallation. Press Enter to confirm the decision to upgrade and continue. TheiStrobe SMF Manager panel appears.

Note: If you choose an alternate installation directory instead of the default, thedirectory (and parent directories) will be created with privileges of 755. Forexample, if this directory structure exists:

/u/sb/abcdef1

and you enter: /u/sb/abcdef1/dirA/dirB/dirC

then directories dirA, dirB, and dirC will be created and iStrobe will beinstalled into dirC.

11. As prompted, enter the Manager Host, Manager Port, Daemon Name, and SMFManager Port for the iStrobe SMF Manager and press Enter after each.

12. Enter the user ID needed to install and run the iStrobe Manager Daemon and pressEnter .

CAUTION: If you do not specify the correct user ID, file permissions for both the iStrobeinstallation and repository directories will be incorrect. An incorrect user ID willrequire the installer to execute the chown Linux command to set the ownershipof these directories to the user ID associated with the iStrobe Manager.

13. Enter the location of the Tomcat home folder and press Enter .14. If you want to rename the iStrobe web application, type a new name and press Enter .

This name is used in the URL to access iStrobe. The iStrobe repository panel appears.

15. From the iStrobe repository panel, select a database to use—either the defaultrepository or a DBMS.



– Default repository (Derby):Enter the following as prompted and press Enter when complete:

• Location of the repository folder (where to place Derby).

Accept the default path, or type an absolute path, for storing profile data andreport definitions.


• Port number


– IBM DB2 for z/OS:Enter the following as prompted and press Enter when complete:


26/84




– IBM DB2 for LUW:Enter the following as prompted and press Enter when complete:

• Database User ID• Password for the Database User ID• Schema• Database Server• Port• Database Name• Folder for the IBM JDBC driver (db2jcc.jar) location

– Microsoft SQL Server :Enter the following as prompted and press Enter when complete:



– Oracle:Enter the following as prompted and press Enter when complete:

• Database User ID• Password for the Database User ID

• Schema• Read and accept the license agreement• Database Server• Port• Database Name

16. Select the version of Tomcat to be installed and press Enter .

Note: This prompt appears only if the install cannot determine the version ofTomcat.


17. Review the installation information on the Pre-installation summary panel. If it iscorrect, press Enter to start the iStrobe installation. Otherwise, type Back and revisethe installation settings as necessary. The Installation complete panel appears.

18. Press Enter to exit the installer. The iStrobe software installation is complete.

19. If you are using a DBMS other than the default (Derby) repository, you mayoptionally set up and start the iStrobe SMF Manager by referring to “Starting andStopping the iStrobe Manager” on page 27.

Notes:

– After starting the iStrobe SMF Manager, be sure to return to this step andcontinue the installation as detailed below.


27/84


– You may need to restart Tomcat before opening the iStrobe interface. If you needhelp deploying either the istrobe.war file or the iStrobe application, refer toApache’s website for the Tomcat Manager App How-To in the Tomcat User’s Guide for your version of Tomcat.


:/

where:


– application server port number is the port Tomcat is listening on, which is 8080 bydefault. If you are not sure of the port on which Tomcat is listening, you can findit in the catalina log file.

– iStrobe application name is the name you entered in step 14.


Note: The recommended Tomcat memory settings are as follows:

• Initial memory pool field is set to 1024 MB or greater

Ex. (-Xms1024m)

• Maximum memory pool field is set to 1536 MB or greaterEx. (-Xmx1536m)

• Java HEAP storage memory is set to 512 MB or greater Ex. (Perm size -XX:PermSize=512m -XX:MaxPermSize=512m).

When running as a Unix process:

• Modify catalina.sh to set JAVA_OPTS as follows:

JAVA_OPTS="-Djava.awt.headless=true -Dfile.encoding=UTF-8 "

JAVA_OPTS="$JAVA_OPTS -server -Xms1024m -Xmx1536m

-XX:PermSize=256m -XX:MaxPermSize=512m "

21. Refer to Chapter 8, “Configuring iStrobe”for complete configuration considerations.


By default, the iStrobe Manager is installed as a daemon.

Installing and Starting the iStrobe Manager Daemon

To install and start the iStrobe Manager daemon, issue the following command:

istrobemanager_service.sh -install

Note: After the iStrobe Manager daemon has been installed, you may wish to edit theumask command in the /etc/in it.d/execistrobe.h file. By default, the umaskcommand is set to 027. This setting does not allow users in a different group toread profiles. If the iStrobe Manager user ID and the Tomcat user ID are indifferent groups, 022 would be a more appropriate setting for the umaskcommand.


28/84


Stopping the iStrobe Manager Daemon

To stop the iStrobe Manager daemon, issue the following command:

mgrcmd.sh stop

If you are having difficulty stopping the iStrobe Manager daemon, you may issue thefollowing command:

mgrcmd.sh kill

Restarting the iStrobe Manager Daemon

To restart the iStrobe Manager daemon, issue the following command:

istrobemanager_service.sh -start

Stopping and Uninstalling the iStrobe Manager Daemon

To stop and uninstall the iStrobe Manager daemon, issue the following command:

istrobemanager_service.sh -remove


By default, the iStrobe SMF Manager is not installed as a daemon.

Installing and Starting the iStrobe SMF Manager Daemon

To install and start the iStrobe SMF Manager daemon, issue the following command:

istrobeSmfManager_service.sh -install

Stopping the iStrobe SMF Manager Daemon

To stop the iStrobe SMF Manager daemon, issue the following command:

smfmgrcmd.sh SHUTDOWN


smfmgrcmd.sh kill

Restarting the iStrobe SMF Manager Daemon

To restart the iStrobe SMF Manager daemon, issue the following command:istrobeSmfManager_service.sh -start

Stopping and Uninstalling the iStrobe SMF Manager Daemon

To stop and uninstall the iStrobe SMF Manager daemon, issue the following command:

istrobeSmfManager_service.sh -remove


29/84





:/

where:


– application server port number is the port Tomcat is listening on, which is 8080 bydefault. If you are not sure of the port on which Tomcat is listening, you can findit in the catalina log file.

– iStrobe application name is the name you entered in step 14.



30/84



31/84

31

Chapter 5.

5Installing or upgrading iStrobe on Linux with

WebSphereChap 5

A server administrator should install or upgrade iStrobe in a Linux environment and aWebSphere system administrator should deploy the iStrobe web application.

Before you begin the iStrobe installation, determine where you will store yourPerformance Profiles and how many ways profiles are transferred from z/OS to thedirectory where they are stored for iStrobe.

If you are only running Strobe version 4.X, all profiles are transmitted directly to theiStrobe Manager daemon. Therefore, the ID used to run the daemon is always the ownerand is the only ID that needs write access to the profiles and quarantine directories.

Before Beginning

Before beginning the installation, you should have the following:

• For your iStrobe Manager and Server:

– A supported version of Java installed and configured.

– A supported version of WebSphere installed and configured.

– The ID and password for the iStrobe Manager daemon with full-control-access tothe HFS/ZFS directories you plan to use for the performance profiles.

– A port number for the iStrobe Manager to listen on (the default is 24354, which

should not conflict with most systems).

– A port number for the iStrobe SMF Manager to listen on (the default is 24355).

IMPORTANT NOTE WHEN UPGRADING FROM 4.4.0: If you are upgrading from iStrobe 4.4.0 to iStrobe 5.1.0, and you want the upgrade tomaintain the security settings (LDAP or X.509) set in Strobe 4.4.0, you must copy thefollowing two files identified in the table below before beginning the upgrade. If youdo not copy these files, but want to enable security in iStrobe 5.1.0, you mustreconfigure security in the iStrobe interface after completing the upgrade.

Notes:

– A custom property must be set on the web container so the WebSphereApplication Server will function with the filters that decide to commit a responseinstead of passing responsibility along to the next filter in the chain.

From To






32/84


– Contact your WebSphere administrator to have the following property set on theWebSphere Application Server where iStrobe will be installed:

com.ibm.ws.webcontainer.invokefilterscompatibility = true

– Use WAS fixpack 6.1.0.11 or higher.

• For the iStrobe database:

– have a supported DBMS installed and configured (see “Database Configuration”on page 65 for details)

– have a database application ID and password

• If you want to use the Web Service interface for requesting a Strobe measurement,contact your Strobe administrator to get the following Host Communications (HCI):

– HCI Host– HCI Port– default Strobe signature

If you decide later to use the Web Service interface, you may setup the HCIconnection information in the Configuration section of Administration.

• If you are installing using the IBM-provided WSADMIN tool, you need the:

– path where the WebSphere Deployment Manager resides

– host name where the WebSphere Deployment Manager is listening

– type of connection (SOAP or RMI) for the WebSphere Deployment Manager

– port number (SOAP or RMI) for the WebSphere Deployment Manager

– WebSphere administration user name and password

– name of the WebSphere application server to which either the istrobe.war oristrobe.ear file will be deployed

– WebSphere node name where the WebSphere application server resides

– path to the repository setup folder.


By default, the /tmp directory is used for temporary disk space during the install. If analternate location for temporary disk space is needed, the following parameter can beused:

-Dlax.nl.env.IATEMPDIR

For example, the following commands may be entered either individually at thecommand prompt or in a shell script:

export TMPDIR=/sample directory/tmp

export JAVA_HOME=/usr/lpp/java/J6.0


export LIBPATH=$JAVA_HOME/lib:$LIBPATH:.

cd /iStrobe-install-dir/Linux/Disk1/InstData/NoVM

./install.bin -Dlax.nl.env.IATEMPDIR=$TMPDIR



33/84

Installing or upgrading iStrobe on Linux with WebSphere 33

• Installs the iStrobe Manager and sets it up as daemon by putting a runtime script inthe /etc/init.d directory. The daemon is enabled for run-levels 3 and 5 so that, duringa reboot of the system, the Manager starts without manual intervention.

• Creates a shell script to install the iStrobe SMF Manager and sets it up as a daemon byputting script in the /etc/init.d directory. The daemon is enabled for run-levels 3 and5 so that, during a reboot of the system, the Manager starts without manualintervention.

• Copies the iStrobe .war or .ear file to the software directory for the WebSphere systemadministrator.

When the installation is finished, the WebSphere system administrator must install theiStrobe Web application. This chapter contains instructions for using either theIntegrated Solutions Console or a shell script with the IBM WSADMIN tool.


1. Transfer the contents of the following folder from the product CD (or FTP image) toyour system:

– :\cpwr\Linux

2. Log on to your system as a super user (root), navigate to where you transferred thefiles, and locate the directory where install.bin is stored.

3. Issue the following commands individually or in a shell script:

export JAVA_HOME=


./install.bin

Note: Be sure to execute the commands in the directory where install.bin is located.You must have execute permission on install.bin. You may need to have the

/sbin and /usr/sbin directories in your path.


Note: You can cancel the installation at any time by typing quit.




7. Select the WebSphere Application Server and press Enter . The Supported platforms

for IBM WebSphere panel appears.8. Read the supported platform information to ensure that you plan to use a supported

operating system, then press Enter . The Install folder panel appears.


– For a new installation, accept the default path or type an absolute path and pressEnter . Confirm the path and press Enter . You must have permission to install tothe directory you choose. The iStrobe Manager panel appears.

– For an upgrade of an existing installation, enter the path to the existinginstallation. Press Enter to confirm the decision to upgrade and continue. TheiStrobe SMF Manager panel appears.


34/84


Note: If you choose an alternate installation directory instead of the default, thedirectory (and parent directories) will be created with privileges of 755. Forexample, if this directory structure exists:

/u/sb/abcdef1

and you enter:

/u/sb/abcdef1/dirA/dirB/dirC


10. As prompted, enter the Manager Host, Manager Port, Daemon Name, and SMFManager Port for the iStrobe SMF Manager, and press Enter after each.

11. Enter the user ID needed to install and run the iStrobe Manager daemon and pressEnter .

CAUTION: If you do not specify the correct user ID, file permissions for both the iStrobeinstallation and repository directories will be incorrect. An incorrect user ID willrequire the installer to execute the chown Linux command to set the ownershipof these directories to the user ID associated with the iStrobe Manager.

The WebSphere version panel appears.

12. Select the version of WebSphere that will run iStrobe and press Enter . The WebApplication name panel appears.

13. From the Web Application Name panel, enter the name to be used as the iStrobeapplication name in the URL used to access iStrobe and press Enter .

Note: If you will deploy using IBM’s Integrated Solutions Console, be sure that thename used as the Web Application Name matches exactly that of the contextroot.

The WebSphere setup panel appears.

14. Select that a .war or a .ear file be created to deploy iStrobe on your WebSphereapplication server and press Enter .

The Scripting panel appears.

15. Select whether or not to use the automatic scripting tool or the Integrated SolutionsConsole to install the iStrobe server, and press Enter .

– To select automatic scripting, type 1 and proceed to “Continuing install using JCL and the IBM WSADMIN tool” on page 34 to install iStrobe using a shellscript.

– To select IBM’s Integrated Solutions Console, type 2. Either the istrobe.war fileor the istrobe.ear file is placed into the installation directory you selected.Proceed to “Continuing install using WebSphere’s Integrated Solutions Console”on page 37 to continue installing iStrobe and start the application.

Continuing install using JCL and the IBM WSADMIN tool

The following panels gather information that is used to generate the shell script to installthe iStrobe.war file.

1. On the WebSphere folder panel, enter the path where the WebSphere deploymentmanager resides, and press Enter . The Deployment Manager host address panelappears.

2. Enter the host name where the WebSphere Deployment Manager is listening andpress Enter . The Connection type panel appears.


35/84


3. Select a connection type—either a SOAP connection or RMI connection—and pressEnter . The Port panel appears.

4. Enter the SOAP or RMI port number and press Enter . The WebSphereadministration ID panel appears.

5. Enter the WAS administration user name and press Enter . The WebSphereadministration password panel appears.

6. Enter the password for the WAS administration user name and press Enter . TheWebSphere application server panel appears.

7. Enter the name of the WebSphere application server and press Enter . The WebSpherenode panel appears.

8. Enter the WebSphere node (where the WebSphere application server above resides)and press Enter . The Synchronize nodes panel appears.

9. Select whether or not to synchronize the WebSphere nodes and press Enter . TheiStrobe repository setup panel appears.

10. Enter the path to the repository folder and press Enter . Enter the Port number andpress Enter . The Start application panel appears.

11. Select whether or not to start the iStrobe web application after the installation has

completed and press Enter .

– If you are doing a new installation, the iStrobe Repository panel appears.


– If you are doing an upgrade of an existing installation, the Pre-installationsummary panel appears. Continue with step 13 on page 36.







• Port number






36/84



• Database User ID• Password for the Database User ID• Schema• Database Server• Port

• Database Name• Folder for the IBM JDBC driver (db2jcc.jar) location







13. Review the installation information on the Pre-installation summary panel. If it iscorrect, press Enter to start the iStrobe installation. Otherwise, type Back and revise

the installation settings as necessary. The Installation complete panel appears.14. Review the installation location in the Ready to Install panel. If it is incorrect, type

Back and revise the installation location as necessary. If it is correct, press Enter tostart the iStrobe installation.

Notes:

– If you are using a 3270 device, you will need to press PF8 to check the status ofthe installation.

– When the Pre-deployment installation complete panel appears, the shell scripthas been generated to invoke the IBM-provided WSADMIN tool allowing theistrobe.war or istrobe.ear file to be deployed under WebSphere. The generatedshell script (iStrobe_Unix_install.ksh) is created in ASCII format and is located inthe utilities directory in the installation directory you specified in step 9 on page

33.

15. Press Enter to exit the installer.


Note: After setting up and starting the iStrobe SMF Manager, be sure to return tothis step and continue the installation as detailed below.

17. Review the created shell script and modify it if necessary.

18. Run the following command:


37/84


./iStrobe_Unix_install.ksh

The shell script output message “Application installedsuccessfully” indicates that the web application has been deployed under the selectedWebSphere application server.

19. If you chose not to synchronize nodes earlier in the installation process, you mayneed to do so now.

20. Using IBM’s Integrated Solutions Console (ISC), ensure that the “Class loader order ”for the iStrobe application is set to Classes loaded with local class loader first(parent last).

21. If you chose not to start iStrobe earlier in the installation, use the IntegratedSolutions Console (ISC) to start it now.

22. The iStrobe software installation is complete.


:/

where:


– application server port number is the port on which WebSphere is listening.

– iStrobe context root is the name you entered in step 13 on page 34.



Continuing install using WebSphere’s Integrated Solutions Console

1. If you are doing an upgrade of an existing installation, continue with the Pre-Installation Summary panel in step 3 on page 38. If you are doing a newinstallation, continue with step 2.







• Port number




• Password for the Database User ID• Schema• Database Server (DNS name)


38/84


• Port• Location Name• Database.Tablespace Name• Folder for the IBM JDBC driver (db2jcc.jar) location


• Database User ID• Password for the Database User ID• Schema• Database Server• Port• Database Name• Folder for the IBM JDBC driver (db2jcc.jar) location


• Database User ID• Password for the database user ID• Schema• Database Server

• Port• Database Name• Instance Name—if you select an instance name other than the default, the





3. Review the installation information in the Pre-installation summary panel. If youneed to modify the settings, type Back and revise the installation settings asnecessary. Otherwise, press Enter . The Ready to Install panel appears.

4. To start the iStrobe installation, press Enter . The iStrobe installation begins. When itis complete, the Pre-deployment installation complete panel appears.

5. Press Enter to exit the installer.


Note: After starting the iStrobe SMF Manager, be sure to return to this step andcontinue the installation as detailed below.

7. Use WebSphere’s Integrated Solutions Console to continue the installation:

– Deploy the istrobe.war file by entering the name you used in step 13 on page 34 as the iStrobe application name. The context root applies only to .war files. Thisfile is located in the install directory.

– After deploying the istrobe.war file, you must complete a full re-synchronizationof nodes.

– Ensure that the “Class loader order ” for the iStrobe application is set to Classesloaded with local class loader first (parent last) .


39/84


– Start the iStrobe application.

The iStrobe software installation is complete.


:/

where:







By default, the iStrobe Manager is installed as a daemon.

Installing and Starting the iStrobe Manager Daemon

To install and start the iStrobe Manager daemon, issue the following command:

istrobemanager_service.sh -install

Note: After the iStrobe Manager daemon has been installed, you may wish to edit theumask command in the /etc/in it.d/execistrobe.h file. By default, the umaskcommand is set to 027. This setting does not allow users in a different group toread profiles. If the iStrobe Manager user ID and the WebSphere user ID are indifferent groups, 022 would be a more appropriate setting for the umaskcommand.

Stopping the iStrobe Manager Daemon

To stop the iStrobe Manager daemon, issue the following command:

mgrcmd.sh stop


mgrcmd.sh kill

Restarting the iStrobe Manager Daemon

To restart the iStrobe Manager daemon, issue the following command:

istrobemanager_service.sh -start





40/84



By default, the iStrobe SMF Manager is not installed as a daemon.

Installing and Starting the iStrobe SMF Manager Daemon

To install and start the iStrobe SMF Manager daemon, issue the following command:

istrobeSmfManager_service.sh -install

Stopping the iStrobe SMF Manager Daemon

To stop the iStrobe SMF Manager daemon, issue the following command:

smfmgrcmd.sh SHUTDOWN

Restarting the iStrobe SMF Manager Daemon

To restart the iStrobe SMF Manager daemon, issue the following command:

istrobeSmfManager_service.sh -start







:/

where:






41/84

41

Chapter 6.

6Installing or upgrading iStrobe on z/OS System

Services with TomcatChap 6

A USS System Administrator should install or upgrade iStrobe.

Depending on your site standards, you may need an MVS systems programmer to set upthe iStrobe Manager on JZOS.

Before you begin the iStrobe installation, determine where you will store yourPerformance Profiles and how many ways they are transferred from z/OS to the directorywhere they are stored for iStrobe.

If you are only running Strobe version 4.X, all profiles are transmitted directly to theiStrobe Manager running on JZOS. Therefore the ID used to run the Manager job is

always the owner and is the only ID that needs write access to the profiles andquarantine directories.

Before Beginning

Before you begin the installation, you should have the following:

• Ensure that the iStrobe 5.1 installation is done with a Java version 1.6.0 at SR9 FP2 orhigher.

To verify the version of Java:

Under z/OS UNIX System Services, go to the bin directory for Java and issue the“java –version” command:

cd /path/to/java/bin java –version

Sample Output:

java version "1.6.0" Java(TM) SE Runtime Environment (build pmz3160sr9fp2-20110625_01(SR9FP2)) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 z/OS s390-31 jvmmz3160sr9-20110624_85526 (JIT enabled, AOT enabled) J9VM -20110624_085526 JIT -r9_20101028_17488ifx17 GC - 20101027_AA)

JCL - 20110530_01

• Shut down the iStrobe Manager service before beginning an upgrade.

• For your iStrobe Manager and Server:

– A supported version of Java installed and configured.

– A supported version of Tomcat installed and configured.

Note: Tomcat parameters should contain the argument:

-Dfile.encoding=ISO8859-1’


42/84


This provides support to read the iStrobe ASCII-based distribution files.

– The ID and password for the iStrobe Manager JZOS job. The system authority forthe JOB or TASK that executes the Manager must be set on the z/OS system sothat full-control access is enabled for the HFS/ZFS directories designated forstoring the performance profiles.

– A port number for the iStrobe Manager to listen on (the default is 24354, which

should not conflict with most systems).– A port number for the iStrobe SMF Manager to listen on (the default is 24355).



• If you want to use the Web Service interface for requesting a Strobe measurement,contact your Strobe administrator to get the following Host Communications (HCI):

– HCI Host– HCI Port– default Strobe signature.

If you decide later to use the Web Service interface, you may setup the HCI

connection information in the Configuration section of Administration.

• The iStrobe installation may require up to 250 MB of temporary space during theinstallation. When the installation is complete, the temporary installation files areremoved.


• Creates the JCL to run the iStrobe Manager on JZOS

• Places the iStrobe.war file into the web apps directory of your Tomcat installation

• Installs the iStrobe SMF Manager as a service.

Note: If autodeployment is enabled, the applications will be automatically

deployed. If autodeployment is not enabled, you will have to manuallydeploy the WAR files.


1. Transfer both the install.jar and the install.sh files from the product CD (orFTP image) (:\cpwr\USS) to the mainframe as binary.

From To

/WEB-INF/security.properties /manager/cfg/security.properties.old




43/84

Installing or upgrading iStrobe on z/OS System Services with Tomcat 43

Note: If you are performing an upgrade, you must also transfer theUpdateConfig.jar file and the UpdateConfig2Props.sh file as binary tothe same directory as the install.jar file.

2. Log on to the mainframe and navigate to an OMVS command prompt. Change thedirectory to the location where the install.jar and the install.sh files weretransferred.

3. Edit the install.sh file:

Change: export JAVA_HOME=

Change: cd


By default, the /tmp directory is used for temporary disk space during the install. Ifan alternate location for temporary disk space is needed, the following changesshould be made:

Add: export TMPDIR=/sample directory/tmp

Change: java -Xmx512m -Xnoargsconversion-Dlax.nl.env.IATEMPDIR=$TMPDIR -Dfile.encoding=ISO8859-1-jar install.jar -i console

4. Be sure the install.sh file has execute authority and execute it.


Note: You can cancel the installation at any time by typing quit.




8. Select Tomcat and press Enter . The Supported platforms for Tomcat panel appears.

9. Read the supported platform information to ensure that you plan to use a supportedoperating system, then press Enter . The Install folder panel appears.


– For a new installation, accept the default path or type an absolute path and pressEnter . Confirm the path and press Enter . You must have permission to install tothe directory you choose. The iStrobe Manager panel appears.

– For an upgrade of an existing installation, enter the path to the existinginstallation. Press Enter to confirm the decision to upgrade, and continue withthe iStrobe SMF Manager panel in step 12.

Note: If you choose an alternate installation directory instead of the default, thedirectory (and parent directories) will be created with privileges of 755. Forexample, if this directory structure exists: /u/sb/abcdef1

and you enter: /u/sb/abcdef1/dirA/dirB/dirC



44/84


11. Enter the Manager Host and Manager Port for the iStrobe Manager, and press Enter .

12. Enter the iStro

istrobe install

Documents