Istrobe Install

iStrobe
Installation Guide
Release 5.1
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 the
Copyright Laws of the United States.
U.S. GOVERNMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject to
restrictions as set forth in Compuware Corporation license agreement and as provided in DFARS
227.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 Compuware
Corporation. Access is limited to authorized users. Use of this product is subject to the terms and
conditions of the users 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, and
VTAM are trademarks of International Business Machines Corporation. Microsoft is a registered trademark
of Microsoft Corporation. Windows, Windows NT, and Windows 98 are trademarks of Microsoft
Corporation.
Adobe Reader is a trademark of Adobe Systems Incorporated in the United States and/or other
countries.
All other company and product names are trademarks or registered trademarks of their respective owners.
Doc. CWISDX5E
September 23, 2014
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How This Guide is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Use This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iStrobe Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iStrobe 3rd Party Licensing Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compuware iStrobe Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compuware Go Customer Support Website . . . . . . . . . . . . . . . . . . . . . . . . .
Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Corporate Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 1. Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iStrobe System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing iStrobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Server Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Server Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Web Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database Server Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Individuals to Participate in the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Web Container Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
7
7
8
8
8
8
8
9
9
9
9
9
11
11
12
12
12
12
12
12
13
13
13
13
13
13
Chapter 2. Upgrading iStrobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Security Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Migrating from Supported Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Chapter 3. Installing or upgrading iStrobe on Windows with Tomcat . . . . . . . . . .
Before Beginning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing or upgrading iStrobe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting and Stopping the iStrobe Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting the iStrobe Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stopping the iStrobe Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting and Stopping the iStrobe SMF Manager . . . . . . . . . . . . . . . . . . . . . . . .
Starting the iStrobe SMF Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stopping the iStrobe SMF Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the iStrobe Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
17
18
21
21
21
22
22
22
22
Chapter 4. Installing or upgrading iStrobe on Linux with Tomcat . . . . . . . . . . . . .

Before Beginning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing or upgrading iStrobe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting and Stopping the iStrobe Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing and Starting the iStrobe Manager Daemon . . . . . . . . . . . . . . . .
Stopping the iStrobe Manager Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restarting the iStrobe Manager Daemon . . . . . . . . . . . . . . . . . . . . . . . . . .
23
23
24
27
27
28
28
Stopping and Uninstalling the iStrobe Manager Daemon . . . . . . . . . . . . . 28

Starting and Stopping the iStrobe SMF Manager . . . . . . . . . . . . . . . . . . . . . . . . 28
Installing and Starting the iStrobe SMF Manager Daemon. . . . . . . . . . . . . 28
Stopping the iStrobe SMF Manager Daemon . . . . . . . . . . . . . . . . . . . . . . . 28
Restarting the iStrobe SMF Manager Daemon. . . . . . . . . . . . . . . . . . . . . . . 28
Stopping and Uninstalling the iStrobe SMF Manager Daemon . . . . . . . . . 28
Using the iStrobe Web Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Chapter 5. Installing or upgrading iStrobe on Linux with WebSphere . . . . . . . . . 31
Before Beginning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Installing or upgrading iStrobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Continuing install using JCL and the IBM WSADMIN tool . . . . . . . . 34
Continuing install using WebSpheres Integrated Solutions
Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Starting and Stopping the iStrobe Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Installing and Starting the iStrobe Manager Daemon. . . . . . . . . . . . . . . . . 39
Stopping the iStrobe Manager Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Restarting the iStrobe Manager Daemon. . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Starting and Stopping the iStrobe SMF Manager . . . . . . . . . . . . . . . . . . . . . . . . 40
Installing and Starting the iStrobe SMF Manager Daemon. . . . . . . . . . . . . 40
Stopping the iStrobe SMF Manager Daemon . . . . . . . . . . . . . . . . . . . . . . . 40
Restarting the iStrobe SMF Manager Daemon. . . . . . . . . . . . . . . . . . . . . . . 40
Chapter 6. Installing or upgrading iStrobe on z/OS System Services
with Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Running the iStrobe Manager and the iStrobe SMF Manager using JZOS . . . . . 47
Executing the iStrobe Jobs as Started Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 49
iStrobe Manager as a started task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
iStrobe SMF Manager as a started task . . . . . . . . . . . . . . . . . . . . . . . . . 49
Changing the Time Zone for iStrobe Manager . . . . . . . . . . . . . . . . . . . . . . 50
Modifying Java Heap Size for iStrobe Manager . . . . . . . . . . . . . . . . . . . . . . 50
Chapter 7. Installing or upgrading iStrobe on z/OS System Services
with WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Continuing install using JCL and the IBM WSADMIN tool . . . . . . . . 54
Continuing install using WebSpheres Integrated Solutions
Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Running the iStrobe Manager and the iStrobe SMF Manager using JZOS . . . . . 59
Executing the iStrobe Jobs as Started Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 61
iStrobe Manager as a started task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
iStrobe SMF Manager as a started task . . . . . . . . . . . . . . . . . . . . . . . . . 62
Changing the Time Zone for iStrobe Manager . . . . . . . . . . . . . . . . . . . . . . 62
Modifying Java Heap Size for iStrobe Manager . . . . . . . . . . . . . . . . . . . . . . 62
Chapter 8. Configuring iStrobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Apache Derby Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Microsoft SQL Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DB2 for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DB2 for Linux, Unix, and Windows . . . . . . . . . . . . . . . . . . . . . . . . . .
Security Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enable security using LDAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enable security using X.509 (Smart Card) . . . . . . . . . . . . . . . . . . . . . . . . .
Enable security using X.509 with LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enable security using Kerberos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disable security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other Configuration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
67
67
68
69
69
70
70
71
71
72
Chapter 9. Customizing iStrobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Changing the Location of the iStrobe Log File . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying the log4j.xml file to Change the Location of the iStrobe
Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Passing a JVM Parameter to Change the Location of the iStrobe L
og File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Compuware Workbench Web-Based Plug-In for iStrobe . . . . . .
73
73
Chapter 10. iStrobe Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

iStrobe Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Use the API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Requesting WSDL URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Web Service Request to iStrobe Server . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Descriptions of Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
connectTest Web Service Request to iStrobe Server - Detail . . . . . . . .
Java Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using SSL with the Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Apache Tomcat Server Configuration for SSL . . . . . . . . . . . . . . . . . . . . . . .
Web Service Java Client Using SSL Connection . . . . . . . . . . . . . . . . . . . . .
75
75
75
75
75
76
77
78
78
78
79
Chapter 11. Uninstalling iStrobe 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Uninstalling iStrobe on Windows with Tomcat . . . . . . . . . . . . . . . . . . . . . . . .
Uninstalling iStrobe on Linux with Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uninstalling iStrobe on Linux with WebSphere . . . . . . . . . . . . . . . . . . . . . . . .
Uninstalling iStrobe on z/OS USS with Tomcat . . . . . . . . . . . . . . . . . . . . . . . . .
Uninstalling iStrobe on z/OS USS with WebSphere . . . . . . . . . . . . . . . . . . . . . .
81
81
81
81
82
82
73
73
74
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Introduction
Intro
This guide provides instructions on how to install iStrobe. iStrobe is an application

performance analysis product designed to be used on workstations with the Strobe MVS
Application Performance Measurement System. iStrobe uses a Web browser that enables
you to create a custom view of Strobe MVS measurement data.
After installing iStrobe, you will be able to view the sample Performance Profile data
packaged 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 and
Customization Guide.
2. Use Strobe to measure an applications performance, create an iStrobe Performance
Profile 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, your
network security policies, and your web server (Tomcat or WebSphere). If you are
unfamiliar 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
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 with
Tomcat
Chapter 7, Installing or upgrading iStrobe on z/OS System Services with
WebSphere
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 Compuwares FrontLine at http://frontline.compuware.com and select
iStrobe, for the latest technical information on iStrobe.
iStrobe 3rd Party Licensing Documentation

To view iStrobe 3rd party licensing documentation, refer to the legal subdirectory that is
included 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 the
information you need.
Compuware Go Customer Support Website

You can access online information for Compuware products via our Compuware Go
customer 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, access
product fixes, or e-mail your questions or comments. The first time you access
Compuware Go, you are required to register and obtain a password. Registration is free.
Compuware now offers User Communities, online forums to collaborate, network, and
exchange best practices with other Compuware solution users worldwide. To join, go to
http://groups.compuware.com.
Introduction
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 the
Compuware 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 Compuwares site on the Web, go to http://www.compuware.com.
The Compuware site provides a variety of product and support information.
10
11
Chapter 1.
Chap 1
This chapter provides an overview of the different hardware and software components
needed to install iStrobe. It also identifies those individuals who will participate in the
iStrobe 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 the
same or separate servers. Refer to the operating systems-specific installation chapters for
setup and security considerations.
Figure 1-1. iStrobe Components and Data Flow
12
Starting at the bottom of the diagram, Strobe collects performance statistics for your z/OS
applications. Strobe 4.1 and newer versions transfer the performance metrics directly to
the iStrobe Manager. The iStrobe Manager then stores the Profiles on your file server as
well as loading them into a database. The Manager listens for transfer requests from
Strobe, processes update requests from the Web server, and optionally watches for new
profiles 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 iStrobe
functionality. In addition, user preferences and state information are stored in the
database instead of browser cookies. The individual performance reports use the xml files
for input; the Strobe Insight reports use the database. The end user runs iStrobe using a
browser.
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 order
to 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 following
hardware 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 less
than 20 users. If you experience performance problems, you may need to
increase memory or processor speed.
File Server Requirements

The following are the minimum hardware and software requirements for the file server
where iStrobe Performance Profiles are stored:
1 GB RAM
Each Performance Profile requires 0.2-50 MB of disk space, depending on the
measured application and the Strobe measurement parameters. Your space
requirements may vary widely depending on the number of users and how many
profiles they keep.
13
Database Server Requirements

iStrobe supports Microsoft SQL Server, Oracle, and IBM DB2. Refer to your database
system documentation for the minimum hardware requirements. iStrobe data storage
requirements 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 Strobe
Insight reports.
Individuals to Participate in the Installation

This section identifies individuals who should participate in the installation and the
information 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 Application
Server.
Database Environment
If you are going to use Strobe Insight with iStrobe, you must install a DBMS when
prompted 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, Configuring

iStrobe.
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 security
administrator with knowledge of LDAP security settings.
14
15
Chapter 2.
Upgrading iStrobe
Chap 2
The iStrobe 5.1 installation wizard includes an option to upgrade from either iStrobe 4.3
or iStrobe 4.4.
When prompted by the wizard for the installation location, enter the location of your
current 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 Manager
service before beginning the upgrade.
If you are using Tomcat, you must restart the Tomcat server after completing
the upgrade installation.
Security Considerations
If you want to enable security in iStrobe 5.1, you will need to configure that in the
iStrobe interface after the upgrade.
Any browsers that remained open during the upgrade should be closed and reopened to
reflect 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 to
maintain the security settings (LDAP or X.509) set in Strobe 4.4.0, you must copy the
following 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 must
reconfigure security in the iStrobe interface after completing the upgrade.
From
To
<iStrobe Web Application Root>/WEBINF/security.properties
<iStrobe Manager installed

Directory>/manager/cfg/security.proper
ties.old
<iStrobe Web Application Root>/WEBINF/ldapControl.properties

Directory>/manager/cfg/ldapControl.pro
perties.old
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 following
migration considerations:
Existing iStrobe repository connection information will be used in the upgrade.
Profiles which may have been contained in multiple sub-directories in the supported
release will be moved to a single profile directory in the upgraded release.
16
17
Chapter 3.
Installing or upgrading iStrobe on Windows with
Tomcat
Chap 3
A Windows Server Administrator should install or upgrade iStrobe for departmental or

corporate use.
End-users with administration authority on their workstation can do a standalone
workstation install for their own use.
Before you begin the iStrobe install for Windows determine where you will store your
Performance Profiles.
When Performance Profiles are stored on the machine where you install iStrobe then you
may 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 both
Tomcat and iStrobe Manager services. The IDs need authority to run a service. The Profile
Directory permissions for the iStrobe Manager must include both update and create. And
the Tomcat service ID must have read access to the Profile directory.
Before Beginning
Before beginning the installation, you should have the following for your iStrobe
Manager and Server:
Ensure that JAVA_HOME is defined as an environment variable and set to the full
path 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, which
should not conflict with most systems).
A port number for the iStrobe SMF Manager to listen on (the default is 24355).
From
To

ties.old

perties.old
18
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 iStrobe
SMF 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 browser
opens; 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 click
Next. The Application server dialog box appears.
5. Select Tomcat then click Next. The Supported platforms for Tomcat dialog box
appears.
6. Read the supported platform information to ensure that you plan to use a supported
operating system, then click Next. A dialog box appears asking if you are going to
store your performance profiles on this server.
7. Select Yes or No to answer the question of whether or not you intend to store your
performance profiles on this server. Click Next. The Install folder dialog box
appears.
8. Accept the default path or enter the path to the location where you want to install
iStrobe and click Next. The iStrobe Manager dialog box appears.
If you are performing an upgrade of a previous version of iStrobe, you are notified
that a previous version of iStrobe exists. Click OK.
Note: At the completion of an upgrade installation, you must migrate profiles for those
profiles existing from iStrobe version 4.1.
9. From the iStrobe Manager dialog box, enter the following, and then click Next:
For
For
a new installation
Manager Host
Manager Port
Service Name
SMF Manager Port
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 are
prompted to enter the Domain\User ID and Password for the iStrobe
Manager service before continuing to the Tomcat installation. The User ID
must have read/write permission to the directory where Performance Profiles
are stored.
Installing or upgrading iStrobe on Windows with Tomcat
19
10. The Tomcat installation requires that Tomcat already exists on this machine or that
you now install it.
If Tomcat is not installed on this machine, select Install to install Tomcat during
the iStrobe installation, and then click Next. The Web Application Name dialog
box 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 box
appears. Choose the folder where Tomcat is installed and click Next. The Web
Application Name dialog box appears.
11. If you want to rename the iStrobe web application, enter a new name. This name is
used 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-installation

summary dialog box appears. Continue with step 13 on page 20.
12. Select a database to useeither the default repository or a DBMS.
Note:
When you choose the default repository (Derby) instead of a DBMS, you will
not 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 and
report definitions.
Note:
Port number
If you choose a DBMS repository:
Microsoft SQL Server:
Database User ID
Password for the database user ID
Schema
Database Server
Port
Database Name
Instance Nameif you select an instance name other than the default, the
port value is ignored.
Oracle:
Database User ID
Password for the Database User ID
Schema
Read and accept the license agreement
Database Server
Port
Database Name
20
IBM DB2 for LUW:

Database User ID
Schema
Database Server
Port
Database Name
Folder for the IBM JDBC driver (db2jcc.jar) location
IBM DB2 for z/OS:

Database User ID (the database ID must have at least the minimum privileges
as specified in DB2 for z/OS on page 67)
Schema
Database Server (DNS name)
Port
Location Name
Database.Tablespace Name
The Pre-installation summary panel appears.
13. Review the installation information in the Pre-installation summary dialog box. If
it is correct, click Install to start the iStrobe installation. Otherwise, click Previous
and revise the installation settings as necessary. The Installation complete dialog
box appears. Click Done to exit the installer.
14. If you are using a DBMS other than the default (Derby) repository, you may
optionally start the iStrobe SMF Manager by referring to Starting and Stopping the
iStrobe Manager on page 21.
Notes:
After starting the iStrobe SMF Manager, be sure to return to this step and
continue the installation as detailed below.
You may need to restart Tomcat before opening the iStrobe interface. If you need
help deploying either the istrobe.war file or the iStrobe application, refer to
Apaches website for the Tomcat Manager App How-To in the Tomcat Users Guide
for your version of Tomcat.
15. The iStrobe software installation is complete.
16. Open iStrobe by pointing your web browser to:
<host address>:<application server port number>/<iStrobe application name>
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 by
default. This is optional if you have IIS installed. If you are not sure of the port
on 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 greater
Ex. (-Xms1024m)
Installing or upgrading iStrobe on Windows with Tomcat
21
Maximum memory pool field is set to 1536 MB or greater

Ex. (-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 command

line. Refer to Apaches website for the Tomcat Windows Service HowTo in the Tomcat Users Guide for your version of Tomcat.
Ex.
<tomcat>\bin\tomcat<N>.exe //US//<service name> --JvmMs=1024
<tomcat>\bin\tomcat<N>.exe //US//<service name> --JvmMx=1500
<tomcat>\bin\tomcat<N>.exe //US//<service name>
++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 type
of 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 is
started, select the Compuware iStrobe Manager service and change the Startup type to
Manual. 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 iStrobe
Manager, select the Compuware iStrobe Manager service and click Stop the service.
22
Starting and Stopping the iStrobe SMF Manager

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

Bring up the Services application (Administrative Tools). To start up the iStrobe SMF
Manager, 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, find
the Compuware iStrobe Manager SMF service. If the Startup type is Manual, change it to
Automatic. 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 SMF
Manager, 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:
default. This is optional if you have IIS installed. If you are not sure of the port
on 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
Chapter 4.
Installing 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 your
Performance Profiles and how many ways they are transferred from z/OS to the directory
where they are stored for iStrobe.
If you are only running Strobe version 4.X, all profiles are transmitted directly to the
iStrobe Manager daemon. Therefore, the ID used to run the daemon is always the owner
and 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 Tomcat installed and configured.
The ID and password for the iStrobe Manager daemon with full-control-access to the
HFS/ZFS directories you plan to use for the performance profiles.
From
To

ties.old

perties.old
The iStrobe installation may require up to 250 MB of temporary space during the
installation. When the installation is complete, the temporary installation files are
removed.
By default, the /tmp directory is used for temporary disk space during the install. If an
alternate location for temporary disk space is needed, the following parameter can be
used:
24
-Dlax.nl.env.IATEMPDIR
For example, the following commands may be entered either individually at the
command 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 a
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 by
putting script in the /etc/init.d directory. The daemon is enabled for run-levels 3 and
5 so that, during a reboot of the system, the Manager starts without manual
intervention.
Deploys the iStrobe Web application under Tomcat.

1. Be sure that you have a supported version of Tomcat installed on the machine onto
which you are installing or upgrading iStrobe.
2. Transfer the contents of the following folder from the product CD (or FTP image) to
your system:
<CDROM drive>:\cpwr\Linux
3. Log on to your system, navigate to where you have transferred the files, and locate
the directory where install.bin is stored.
4. Issue the following commands individually or in a shell script:
export JAVA_HOME=<directory location for Java>
./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 and
you must have execute permission on install.bin. You may need to have the /sbin
and /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 read
the entire agreement.
7. Type Y and press Enter to accept the terms of the license agreement. The
Application server panel appears.
25
8. Select Tomcat and press Enter. The Supported platforms for Tomcat panel appears.
operating 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 press
Enter. 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 existing
installation. Press Enter to confirm the decision to upgrade and continue. The
iStrobe SMF Manager panel appears.
Note:
If you choose an alternate installation directory instead of the default, the

directory (and parent directories) will be created with privileges of 755. For
example, 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 be
installed into dirC.
11. As prompted, enter the Manager Host, Manager Port, Daemon Name, and SMF
Manager 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 press
Enter.
CAUTION:
If you do not specify the correct user ID, file permissions for both the iStrobe
installation and repository directories will be incorrect. An incorrect user ID will
require the installer to execute the chown Linux command to set the ownership
of 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 useeither the default
repository or a DBMS.
Note:

Enter the following as prompted and press Enter when complete:
report definitions.
Note:
Port number
IBM DB2 for z/OS:
26
Schema
Port
Location Name
IBM DB2 for LUW:
Database User ID
Schema
Database Server
Port
Database Name

Database User ID
Schema
Database Server
Port
Database Name
Oracle:
Database User ID
Schema
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 of
Tomcat.

17. Review the installation information on the Pre-installation summary panel. If it is
correct, press Enter to start the iStrobe installation. Otherwise, type Back and revise
the installation settings as necessary. The Installation complete panel appears.
18. Press Enter to exit the installer. The iStrobe software installation is complete.
optionally set up and start the iStrobe SMF Manager by referring to Starting and
Stopping the iStrobe Manager on page 27.
Notes:
27
where:
default. If you are not sure of the port on which Tomcat is listening, you can find
it in the catalina log file.
iStrobe application name is the name you entered in step 14.
Note:

Ex. (-Xms1024m)

Ex. (-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 iStrobefor 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 the
umask command in the /etc/init.d/execistrobe.h file. By default, the umask
command is set to 027. This setting does not allow users in a different group to
read profiles. If the iStrobe Manager user ID and the Tomcat user ID are in
different groups, 022 would be a more appropriate setting for the umask
command.
28
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 the
following 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
following command:
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

where:
default. If you are not sure of the port on which Tomcat is listening, you can find
it in the catalina log file.
iStrobe application name is the name you entered in step 14.
30
31
Chapter 5.
Installing or upgrading iStrobe on Linux with
WebSphere
Chap 5
A server administrator should install or upgrade iStrobe in a Linux environment and a

WebSphere system administrator should deploy the iStrobe web application.
Performance Profiles and how many ways profiles are transferred from z/OS to the
directory where they are stored for iStrobe.
iStrobe Manager daemon. Therefore, the ID used to run the daemon is always the owner
and 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 WebSphere installed and configured.
The ID and password for the iStrobe Manager daemon with full-control-access to
the HFS/ZFS directories you plan to use for the performance profiles.
From
To

ties.old

perties.old
Notes:
A custom property must be set on the web container so the WebSphere
Application Server will function with the filters that decide to commit a response
instead of passing responsibility along to the next filter in the chain.
32
Contact your WebSphere administrator to have the following property set on the
WebSphere 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 HCI
connection 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 or
istrobe.ear file will be deployed
WebSphere node name where the WebSphere application server resides
path to the repository setup folder.
removed.
By default, the /tmp directory is used for temporary disk space during the install. If an
alternate location for temporary disk space is needed, the following parameter can be
used:
-Dlax.nl.env.IATEMPDIR
For example, the following commands may be entered either individually at the
command prompt or in a shell script:
export JAVA_HOME=/usr/lpp/java/J6.0
cd /iStrobe-install-dir/Linux/Disk1/InstData/NoVM
./install.bin -Dlax.nl.env.IATEMPDIR=$TMPDIR
Installing or upgrading iStrobe on Linux with WebSphere
33
Installs the iStrobe Manager and sets it up as daemon by putting a runtime script in
the /etc/init.d directory. The daemon is enabled for run-levels 3 and 5 so that, during
a 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 by
putting script in the /etc/init.d directory. The daemon is enabled for run-levels 3 and
5 so that, during a reboot of the system, the Manager starts without manual
intervention.
Copies the iStrobe .war or .ear file to the software directory for the WebSphere system
administrator.
When the installation is finished, the WebSphere system administrator must install the
iStrobe Web application. This chapter contains instructions for using either the
Integrated 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) to
your system:
<CDROM drive>:\cpwr\Linux
2. Log on to your system as a super user (root), navigate to where you transferred the
files, and locate the directory where install.bin is stored.
./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.
installation. Press Enter to confirm the decision to upgrade and continue. The
34
Note:

/u/sb/abcdef1
and you enter:
10. As prompted, enter the Manager Host, Manager Port, Daemon Name, and SMF
Manager 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 press
Enter.
CAUTION:
require the installer to execute the chown Linux command to set the ownership
The WebSphere version panel appears.

12. Select the version of WebSphere that will run iStrobe and press Enter. The Web
Application name panel appears.
13. From the Web Application Name panel, enter the name to be used as the iStrobe
application name in the URL used to access iStrobe and press Enter.
Note:
If you will deploy using IBMs Integrated Solutions Console, be sure that the
name used as the Web Application Name matches exactly that of the context
root.
The WebSphere setup panel appears.

14. Select that a .war or a .ear file be created to deploy iStrobe on your WebSphere
application server and press Enter.
The Scripting panel appears.
15. Select whether or not to use the automatic scripting tool or the Integrated Solutions
Console 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 shell
script.
To select IBMs Integrated Solutions Console, type 2. Either the istrobe.war file
or the istrobe.ear file is placed into the installation directory you selected.
Proceed to Continuing install using WebSpheres 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 install
the iStrobe.war file.
1. On the WebSphere folder panel, enter the path where the WebSphere deployment
manager resides, and press Enter. The Deployment Manager host address panel
appears.
2. Enter the host name where the WebSphere Deployment Manager is listening and
press Enter. The Connection type panel appears.
35
3. Select a connection typeeither a SOAP connection or RMI connectionand press

Enter. The Port panel appears.
4. Enter the SOAP or RMI port number and press Enter. The WebSphere
administration ID panel appears.
5. Enter the WAS administration user name and press Enter. The WebSphere
administration password panel appears.
6. Enter the password for the WAS administration user name and press Enter. The
WebSphere application server panel appears.
7. Enter the name of the WebSphere application server and press Enter. The WebSphere
node 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. The
iStrobe repository setup panel appears.
10. Enter the path to the repository folder and press Enter. Enter the Port number and
press 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.
Note:

summary panel appears. Continue with step 13 on page 36.
Note:

report definitions.
Note:
Port number
IBM DB2 for z/OS:
Schema
Port
Location Name
36
IBM DB2 for LUW:

Database User ID
Schema
Database Server
Port
Database Name

Database User ID
Schema
Database Server
Port
Database Name
Oracle:
Database User ID
Schema
Database Server
Port
Database Name

correct, 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 to
start the iStrobe installation.
Notes:
If you are using a 3270 device, you will need to press PF8 to check the status of
the installation.
When the Pre-deployment installation complete panel appears, the shell script
has been generated to invoke the IBM-provided WSADMIN tool allowing the
istrobe.war or istrobe.ear file to be deployed under WebSphere. The generated
shell script (iStrobe_Unix_install.ksh) is created in ASCII format and is located in
the 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 to
this 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
./iStrobe_Unix_install.ksh
The shell script output message Application <application name> installed

successfully indicates that the web application has been deployed under the selected
WebSphere application server.
19. If you chose not to synchronize nodes earlier in the installation process, you may
need to do so now.
20. Using IBMs 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 Integrated
Solutions Console (ISC) to start it now.
22. The iStrobe software installation is complete.
<host address>:<application server port number>/<iStrobe context root>
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 WebSpheres Integrated Solutions Console

1. If you are doing an upgrade of an existing installation, continue with the PreInstallation Summary panel in step 3 on page 38. If you are doing a new
installation, continue with step 2.
Note:

report definitions.
Note:
Port number
IBM DB2 for z/OS:
Schema
38
Port
Location Name
IBM DB2 for LUW:

Database User ID
Schema
Database Server
Port
Database Name

Database User ID
Schema
Database Server
Port
Database Name
Oracle:
Database User ID
Schema
Database Server
Port
Database Name

3. Review the installation information in the Pre-installation summary panel. If you
need to modify the settings, type Back and revise the installation settings as
necessary. Otherwise, press Enter. The Ready to Install panel appears.
4. To start the iStrobe installation, press Enter. The iStrobe installation begins. When it
is complete, the Pre-deployment installation complete panel appears.
Note:
7. Use WebSpheres 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. This
file is located in the install directory.
After deploying the istrobe.war file, you must complete a full re-synchronization
of nodes.
Ensure that the Class loader order for the iStrobe application is set to Classes
loaded with local class loader first (parent last).
39
Start the iStrobe application.

The iStrobe software installation is complete.
<host address>:<application server port number>/<context root>
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 the
umask command in the /etc/init.d/execistrobe.h file. By default, the umask
command is set to 027. This setting does not allow users in a different group to
read profiles. If the iStrobe Manager user ID and the WebSphere user ID are in
different groups, 022 would be a more appropriate setting for the umask
command.
Stopping the iStrobe Manager Daemon

To stop the iStrobe Manager daemon, issue the following command:
mgrcmd.sh stop
following command:
mgrcmd.sh kill
Restarting the iStrobe Manager Daemon

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

40

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


<host address>:<application server port number>/<context root>
where:
41
Chapter 6.
Installing or upgrading iStrobe on z/OS System
Services with Tomcat
Chap 6
A USS System Administrator should install or upgrade iStrobe.

Depending on your site standards, you may need an MVS systems programmer to set up
the iStrobe Manager on JZOS.
Performance Profiles and how many ways they are transferred from z/OS to the directory
where they are stored for iStrobe.
iStrobe 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 and
quarantine 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 or
higher.
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(SR9
FP2))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 z/OS s390-31 jvmmz3160sr920110624_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.

A supported version of Tomcat installed and configured.
Note:
Tomcat parameters should contain the argument:
-Dfile.encoding=ISO8859-1
42
This provides support to read the iStrobe ASCII-based distribution files.

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

ties.old

perties.old
HCI Host
HCI Port
default Strobe signature.
removed.
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 manually
deploy the WAR files.

1. Transfer both the install.jar and the install.sh files from the product CD (or
FTP image) (<CDROM drive>:\cpwr\USS) to the mainframe as binary.
Installing or upgrading iStrobe on z/OS System Services with Tomcat
Note:
43
If you are performing an upgrade, you must also transfer the

UpdateConfig.jar file and the UpdateConfig2Props.sh file as binary to
the same directory as the install.jar file.
2. Log on to the mainframe and navigate to an OMVS command prompt. Change the
directory to the location where the install.jar and the install.sh files were
transferred.
3. Edit the install.sh file:
Change: export JAVA_HOME=<directory location for Java>
Change: cd <directory location for install.jar, e.g. /u/sb/userid>
removed.
By default, the /tmp directory is used for temporary disk space during the install. If
an alternate location for temporary disk space is needed, the following changes
should be made:
Add:
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:
8. Select Tomcat and press Enter. The Supported platforms for Tomcat panel appears.
installation. Press Enter to confirm the decision to upgrade, and continue with
the iStrobe SMF Manager panel in step 12.
Note:

/u/sb/abcdef1
and you enter:
44
11. Enter the Manager Host and Manager Port for the iStrobe Manager, and press Enter.
12. Enter the iStrobe SMF Manager Port and press Enter.
13. Enter the user ID needed to install and run the iStrobe Manager Daemon and
press Enter.
CAUTION:
require the installer to execute the chown Unix command to set the ownership
14. Enter the location of the Tomcat home folder and press Enter.
15. 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.
16. Enter the version of Tomcat to be installed and press Enter.
Note:
This prompt appears only if the install cannot determine the version of
Tomcat.
Note:

report definitions.
Note:
Port number
IBM DB2 for z/OS:
Schema
Port
Location Name
IBM DB2 for LUW:
Database User ID
Schema
Database Server
Port
Database Name
45

Database User ID
Schema
Database Server
Port
Database Name
Oracle:
Database User ID
Schema
Database Server
Port

18. Review the installation information. If it is incorrect, type Back and revise the
installation settings as necessary. If it is correct, press Enter to start the iStrobe
installation. The Installation complete panel appears.
Note:
the installation.
19. Set up and start the iStrobe Manager by referring to Running the iStrobe Manager
and the iStrobe SMF Manager using JZOS on page 47. If you are using a DBMS other
than the default (Derby) repository, you may also optionally set up and start the
iStrobe SMF Manager using the instructions in that same section.
Notes:
After setting up and starting the iStrobe Managerand, if applicable, the iStrobe
SMF Managerbe sure to return to this step and continue the installation as
detailed below.
where:
application server port number is the port on which Tomcat is listening.
Note:

Ex. (-Xms1024m)

Ex. (-Xmx1536m)
46
47
Running the iStrobe Manager and the iStrobe SMF

Manager using JZOS
1. Create a data set for the iStrobe Manager runtime files. A partitioned data set (PDS)
will lend itself better to updating and customizing the JCL prior to submission. The
job shown in step 2 illustrates creation of a new PDS for this FTP transfer.
2. FTP the following files from the /Manager directory in the installation directory in
USS to MVS:
PARMLIB.ISMGRADS
PARMLIB.ISMGRAMN
PARMLIB.ISMGRASP
PARMLIB.ISMGREMN
SAMPLE.JCL
JZOSPROC.JCL
PARMLIB.SMFMGRIN
PARMLIB.SMFMGRSH
PARMLIB.SMFMGRST
SMFSAMP.JCL
The names must be shortened to the eight-character member name limit. The files
that start with PARMLIB are input parameter files used to start the appropriate
iStrobe Manager service. These can be shortened to ISMGRxxx member names. The
files that are qualified as JCL are the PROC and JOB samples for executing on the
z/OS system; these can be shortened by removing the .JCL qualifier.
Refer to the SAMPLE_FTP.JCL in the Manager directory and edit it as follows:
Modify the job card
Change sysid on JOBPARM card to the target z/OS system name.
Change userid to your z/OS user ID throughout the JCL.
In the INPUT DD, make the following changes:
Change password to the password associated with the z/OS user id to the
FTP server.
Change the cd directory to your iStrobe installation location.
Add the extra get command that appears at the bottom of the job before the
quit command.
Submit the job.
3. After the FTP process is complete, modify the JCL members in the data set you
created in as needed:
JZOSPROC - Change the data set name for DDNAME STDENV and MAINARGS to
a system data set where you store the PARMLIB.ISMGRxxx members. The PROC is
shipped by default to use &QUAL.PARMLIB where QUAL defaults to SYSA. This
PROC should be put into a system PROCLIB to be referenced automatically when
the job for the iStrobe Manager is submitted. You can rename the PROC to follow
your system standards (e.g. ISMANAGR).
VERSION - Set the VERSION variable to the level of Java installed on the
system. The VERSION variable is used within the JZOSPROC to invoke the
proper version of the Java Batch Launcher. The default is set to 50 to invoke
Java 5. Use 60 to invoke Java 6.
REGSIZE - The REGSIZE variable specifies a specific region memory
allocation. The default is 0, which sets the region memory size based on the
system defaults defined within the JES2 sub-system.
48
LEPARM - The LEPARM variable is the mechanism used by the JZOS to

establish settings for the z/OS language environment. The initialization of
Java is performed by LE as part of the z/OS operating system. By default, the
setting assigns the UMASK to files created in the HFS file system. Note that
UMASK is a compliment to the permission assignment. The default value is
022, which will give new files a permission setting of 644 for files and 755 for
directories. Refer to Unix Systems Services documentation for valid values
and other information.
MANAGER - Change the job card to match your system requirements.
ARGS=ISMGRAMN is set by default to start the iStrobe Manager.
000001
000002
000003
000004
000005
000006
000007
000008
000009
000010
000011
//ISTROBEM JOB
('ACCOUNT',78,1,1),'ISTROBE MANAGER',
//
CLASS=L,MSGCLASS=R,NOTIFY=&SYSUID,REGION=0M
//*
optional JCLLIB ORDER=(<USERID>.ISTROBE.CNTL)
//***************************************************
//*
Use ISMGREMN for the ENV member for all uses
//*
Use ARGS=ISMGRAMN to run the iStrobe Manager
//*
Use ARGS=ISMGRASP to stop the iStrobe Manager
//*
Use ARGS=ISMGRADS to test activity in the iStrobe Manager
//***************************************************
//ISMANAGR EXEC JZOSPROC Defaults are ENV=ISMGREMN,ARGS=ISMGRAMN
//*
As shown in the JCL above, you can insert a JCLLIB statement if you want to
invoke the JZOSPROC from the ISTROBE.CNTL data set.
For example:
// JCLLIB ORDER=(<USER>.ISTROBE.CNTL)
Use ARGS=ISMGRASP to stop the iStrobe Manager cleanly.

Note: Your JOBNAME must be different from the JOBNAME that is running
the iStrobe Manager in order for the stop request to execute.
Use ARGS=ISMGRADS to get a current status of active tasks in the iStrobe
Manager. This is useful to confirm that the iStrobe Manager is
communicating normally.
ISSMFMGR - Change the job card to match your system requirements.
ARGS=SMFMGRST is set by default to start the iStrobe SMF Manager.
000001
000002
000003
000004
000005
000006
000007
000008
000009
000010
000011
//ISTROBES JOB ('ACCOUNT'),'ISTROBE SMF MANAGER',

//
//* optional JCLLIB ORDER=(<USERID>.ISTROBE.CNTL)
//********************************************************************
//*
//*
Use ARGS="SMFMGRST" to start the iStrobe SMF Manager
//*
Use ARGS="SMFMGRSH" to shutdown the iStrobe SMF Manager
//*
Use ARGS="SMFMGRIN" to get current status of iStrobe SMF Manager
//********************************************************************
//ISSMFMGR EXEC JZOSPROC,ENV=ISMGREMN,ARGS=SMFMGRST
//*
For example:
Use ARGS=SMFMGRSH to shutdown the iStrobe SMF Manager cleanly.

the iStrobe SMF Manager in order for the stop request to execute.
49
Use ARGS=SMFMGRIN to get a current status of active tasks in the iStrobe

SMF Manager. This is useful to confirm that the iStrobe SMF Manager is
4. Submit the JCL from member MANAGER, or start the system task (described below),
to start the iStrobe Manager.
5. You may optionally submit the JCL from member ISSMFMGR, or start the system task
(described below) to start the iStrobe SMF Manager.
Executing the iStrobe Jobs as Started Tasks

You can, optionally, set up the iStrobe Manager to execute as a started procedure on your
z/OS system by adding the start command to the SYS1.PARMLIB(COMMNDxx) member.
Your installation may require special security authorizations for the started task to
actually execute.
iStrobe Manager as a started task

You can rename the PROC at your discretion (for example ISMANAGR) so that the longrunning task is identifiable as the iStrobe Manager or to match your systems standards.
In this setup, you would only have to start the iStrobe Manager the first time with a z/OS
console command:
START JZOSPROC
or
START ISMANGR
For stopping the iStrobe Manager, you can create a copy of the PROC (like ISMGRSTP)
and set the ARGS value to ISMGRASP. The iStrobe Manager normally should not have to
be stopped but, if necessary for operational reasons, the console command:
START JZOSPROC,ARGS=ISMGRASP
or
START ISMGRSTP
will notify the iStrobe Manager to cleanly terminate.
iStrobe SMF Manager as a started task

For starting the iStrobe SMF Manager, you can optionally create a copy of the PROC (like
ISSMFM) and set the ARGS value to SMFMGRST. Use the console command:
START JZOSPROC,ARGS=SMFMGRST
or
START ISSMFM
For stopping the iStrobe SMF Manager, you can create a copy of the PROC (like ISSMFS)
and set the ARGS value to SMFMGRSH. The iStrobe SMF Manager normally should not
have to be stopped but, if necessary for operational reasons, the console command:
START JZOSPROC,ARGS=SMFMGRSH
or
START ISSMFS
will notify the iStrobe SMF Manager to cleanly terminate.
50
Changing the Time Zone for iStrobe Manager

The member name ISMGREMN defines the Time Zone variable.
For example:
TZ = EST5EDT
EST is Eastern Standard Time

Standard Time is 5 hours west of the universal reference time
EDT is Eastern Daylight Savings Time
For more information on setting time zones in iStrobe, refer to IBMs z/OS Information
Center on the Web.
Modifying Java Heap Size for iStrobe Manager

The member name ISMGREMN defines the startup options. The iStrobe Manager is
configured with an initial heap size of 256 MB (java option = '-Xms256M') and a
maximum heap size of 1024 MB (java option = '-Xmx1024m').
To modify these parameters:
1. Stop the iStrobe Manager.
2. Locate the following two lines in member ISMGREMN.
# INSTALLER:
Sets java heap allocation if more becomes necessary
DEFS="-Xms256M -Xmx1024m "
3. Make the appropriate changes to the heap sizes.

4. Restart the iStrobe Manager.

where:
application server port number is the port on which Tomcat is listening.
51
Chapter 7.
Installing or upgrading iStrobe on z/OS System
Services with WebSphere
Chap 7
A USS system administrator should install or upgrade iStrobe and a WebSphere system
administrator should deploy the iStrobe web application.
Depending on your site standards you may need an MVS systems programmer to set up
the iStrobe Manager on JZOS. You may also need a security administrator.
Performance Profiles. If you are only running Strobe version 4.X, all profiles are
transmitted directly to the iStrobe Manager running on JZOS. Therefore the ID used to
run the iStrobe Manager job is always the owner and is the only ID that needs write
access to the profiles and quarantine directories. The user ID under which WebSphere is
running needs read access to the profile directories.
Before Beginning
Before you begin the installation, you should:
Ensure the WebSphere Application Server environment into which you are installing
iStrobe has only one application servant. WebSphere Application Servers on z/OS
with multiple application servants are not supported.
Ensure that the iStrobe 5.1 installation is done with a Java version 1.6.0 at SR9 FP2 or
higher.
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(SR9
FP2))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 z/OS s390-31 jvmmz3160sr920110624_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.

have a supported version of Java installed and configured.
have a supported version of WebSphere installed and configured.
have the ID and password for the iStrobe Manager JZOS job. The system
authority for the JOB or TASK that executes the Manager must be set on the z/OS
52
system so that full-control access is enabled for the HFS/ZFS directories

designated for storing the performance profiles.
have a port number for the iStrobe Manager to listen on (the default is 24354,
which should not conflict with most systems).
have a port number for the iStrobe SMF Manager to listen on (the default is
24355).
From
To

ties.old

perties.old
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.
HCI Host
HCI Port
default Strobe signature.
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 or
istrobe.ear file will be deployed
WebSphere node name where the WebSphere application server resides
path to the repository setup folder.
removed.
The installation:
Creates the JCL to run the iStrobe Manager on JZOS
Installing or upgrading iStrobe on z/OS System Services with WebSphere
53
Installs the iStrobe SMF Manager as a service.

Places the istrobe.war or istrobe.ear file into the iStrobe installation directory.
When the installation is finished, the WebSphere system administrator must install the
iStrobe Web application. This chapter contains instructions for using either the
Integrated Solutions Console or a shell script with the IBM WSADMIN tool.

1. Transfer both the install.jar and the install.sh files from the product CD (or
FTP image) (<CDROM drive>:\cpwr\USS) to the mainframe as binary.
Note:
If you are performing an upgrade, you must also transfer the

UpdateConfig.jar file and the UpdateConfig2Props.sh file as binary to
the same directory as the install.jar file.
2. Log on to the mainframe and navigate to an OMVS command prompt. Change the
directory to the location where the install.jar and the install.sh files were
transferred.
3. Edit the install.sh file:
Change: export JAVA_HOME=<directory location for Java>
Change: cd <directory location for install.jar, e.g. /u/sb/userid>
removed.
By default, the /tmp directory is used for temporary disk space during the install. If
an alternate location for temporary disk space is needed, the following changes
should be made:
Add:
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:
8. Select the WebSphere Application Server and press Enter. The Supported platforms
for IBM WebSphere panel appears.
54

installation. Press Enter to confirm the decision to upgrade, and continue with
the iStrobe SMF Manager panel in step 12 on page 54.
Note:

/u/sb/abcdef1
and you enter:
11. Enter the Manager host and press Enter. Enter the Manager port and press Enter. The
12. Enter the SMF Manager port and press Enter. The iStrobe Manager panel appears.
13. Enter the user ID for the iStrobe Manager and press Enter.
CAUTION:
require the installer to execute the chown Unix command to set the ownership
The Application name panel appears.

14. From the Application name panel, enter the name to be used as the iStrobe
application name in the URL used to access iStrobe and press Enter.
Note:
If you will deploy using IBMs Integrated Solutions Console, be sure that the
name used as the Application Name matches exactly that of the context root.
The WebSphere setup panel appears.

15. Select that a .war or a .ear file be created to deploy iStrobe on your WebSphere
application server and press Enter.
The Scripting panel appears.
16. Select whether or not to use the automatic scripting tool or the Integrated Solutions
Console 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 54 to install iStrobe using a shell
script.
To select IBMs Integrated Solutions Console, type 2. Either the istrobe.war file
or the istrobe.ear file is placed into the installation directory you selected.
Proceed to Continuing install using WebSpheres Integrated Solutions Console
on page 57 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 JCL to install the
istrobe.war file.
1. On the WebSphere folder panel, enter the path where the WebSphere deployment
manager resides, and press Enter. The Deployment Manager host address panel
appears.
55
2. Enter the host name where the WebSphere Deployment Manager is listening and
press Enter. The Connection type panel appears.
3. Select a connection typeeither a SOAP connection or RMI connectionand press
Enter. The Port panel appears.
4. Enter the SOAP or RMI port number and press Enter. The WebSphere
administration ID panel appears.
5. Enter the WAS administration user name and press Enter. The WebSphere
administration password panel appears.
6. Enter the password for the WAS administration user name and press Enter. The
WebSphere application server panel appears.
7. Enter the name of the WebSphere application server and press Enter. The WebSphere
node 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. The
iStrobe repository setup panel appears.
10. Enter the path to the repository folder and press Enter. Enter the Port number and
press Enter. The Start application panel appears.
11. Select whether or not to start iStrobe after the installation has completed and press
Enter.
If you are doing a new installation, the iStrobe Repository panel appears.
Note:

summary panel appears. Continue with step 13 on page 56.
Note:

report definitions.
Note:
Port number
IBM DB2 for z/OS:
Schema
Port
Location Name
56
IBM DB2 for LUW:
Database User ID
Schema
Database Server
Port
Database Name

Database User ID
Schema
Database Server
Port
Database Name
Oracle:
Database User ID
Schema
Database Server
Port

incorrect, type Back and revise the installation settings as necessary. If it is correct,
press Enter. The Ready to install 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 to
start the iStrobe installation.
Notes:
the installation.
When the Pre-deployment installation complete panel appears, the JCL has been
generated to invoke the IBM-provided WSADMIN tool allowing the istrobe.war
or istrobe.ear file to be deployed under WebSphere. The generated JCL
(WASADMIN.JCL) is created in ASCII format and is located in the utilities
directory in the installation directory you specified in step 10 on page 53.
and the iStrobe SMF Manager using JZOS on page 59. Be sure that the get command
in the WASADMIN.JCL is put before the quit command in the JCL. If you are using a
DBMS other than the default (Derby) repository, you may also optionally set up and
start the iStrobe SMF Manager using the instructions in that same section.
Note:
After setting up and starting the iStrobe Managerand if applicable, the iStrobe
detailed below.
57
17. Review the WASADMIN.JCL:

Modify the job card to conform to your sites standards if necessary.
Ensure that the PROC symbolic ISTRLOC points to the directory where the
iStrobe installation utilities are located. The generated JCL sets ISTRLOC to the
directory where WASADMIN.JCL was generated.
Ensure that STDIN (standard input), STDOUT (standard output), and STDERR
(standard error) point to the correct location.
Ensure that the environment variables are correctly set for STDENV. Refer to the
JCL for environment variable definitions.
18. Submit the job defined by WASADMIN.JCL for execution. The job output message
Application <application name> installed successfully indicates that the istrobe.war
or istrobe.ear file has been deployed under the selected WebSphere application
server.
19. If you chose not to synchronize nodes earlier in the installation process, you may
need to do so now.
20. Using IBMs 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 Integrated
Solutions Console (ISC) to start it now.
where:
Continuing install using WebSpheres Integrated Solutions Console

1. If you are doing an upgrade of an existing installation, continue with the PreInstallation Summary panel in step 3 on page 58. If you are doing a new
installation, continue with step 2.
Note:

report definitions.
Note:
58
Port number
IBM DB2 for z/OS:
Schema
Port
Location Name
IBM DB2 for LUW:
Database User ID
Schema
Database Server
Port
Database Name

Database User ID
Schema
Database Server
Port
Database Name
Oracle:
Database User ID
Schema
Database Server
Port

3. Review the installation information in the Pre-installation summary panel. If it is
incorrect, type Back and revise the installation settings as necessary. If it is correct,
press Enter. The Ready to Install panel appears.
4. To start the iStrobe installation, press Enter. The iStrobe installation begins. When it
is complete, the Pre-deployment installation complete panel appears.
Note:
the installation.

and the iStrobe SMF Manager using JZOS on page 59. If you are using a DBMS other
59
than the default (Derby) repository, you may also optionally set up and start the
iStrobe SMF Manager using the instructions in that same section.
Note:
After setting up and starting the iStrobe Managerand, if applicable, the iStrobe
detailed below.
7. Use WebSpheres Integrated Solutions Console to continue the installation:

Deploy either the istrobe.war file or the istrobe.ear file by entering the
name you used in step 14 on page 54 as the iStrobe application name. The
context root applies only to .war files. This file is located in the install directory.
After deploying the istrobe.war file, you must complete a full resynchronization of nodes.
Ensure that the Class loader order for the iStrobe application is set to Classes
loaded with local class loader first (parent last).
Start the iStrobe application.
where:
Running the iStrobe Manager and the iStrobe SMF

Manager using JZOS
1. Create a data set for the iStrobe Manager runtime files. A partitioned data set (PDS)
will lend itself better to updating and customizing the JCL prior to submission. The
job shown in step 2 illustrates creation of a new PDS for this FTP transfer.
2. FTP the following files from the /Manager directory in the installation directory in
USS to MVS:
PARMLIB.ISMGRADS
PARMLIB.ISMGRAMN
PARMLIB.ISMGRASP
PARMLIB.ISMGREMN
SAMPLE.JCL
JZOSPROC.JCL
WASADMIN.JCL (only present for WebSphere installs)
PARMLIB.SMFMGRIN
PARMLIB.SMFMGRSH
PARMLIB.SMFMGRST
SMFSAMP.JCL
The names must be shortened to the eight-character member name limit. The files
that start with PARMLIB are input parameter files used to start the appropriate
iStrobe Manager service. These can be shortened to ISMGRxxx member names. The
60
files that are qualified as JCL are the PROC and JOB samples for executing on the
z/OS system; these can be shortened by removing the .JCL qualifier.
Refer to the SAMPLE_FTP.JCL in the Manager directory and edit it as follows:
Modify the job card
Change userid to your z/OS user ID throughout the JCL.
In the INPUT DD, make the following changes:
Change password to the password associated with the z/OS user id to the
FTP server.
Change the cd directory to your iStrobe installation location.
Add the extra get command that appears at the bottom of the job before the
quit command.
Submit the job.
3. After the FTP process is complete, modify the JCL members in the data set you
created in as needed:
JZOSPROC - Change the data set name for DDNAME STDENV and MAINARGS to
a system data set where you store the PARMLIB.ISMGRxxx members. The PROC is
shipped by default to use &QUAL.PARMLIB where QUAL defaults to SYSA. This
PROC should be put into a system PROCLIB to be referenced automatically when
the job for the iStrobe Manager is submitted. You can rename the PROC to follow
your system standards (e.g. ISMANAGR).
VERSION - Set the VERSION variable to the level of Java installed on the
system. The VERSION variable is used within the JZOSPROC to invoke the
proper version of the Java Batch Launcher. The default is set to 50 to invoke
Java 5. Use 60 to invoke Java 6.
REGSIZE - The REGSIZE variable specifies a specific region memory
allocation. The default is 0, which sets the region memory size based on the
system defaults defined within the JES2 sub-system.
LEPARM - The LEPARM variable is the mechanism used by the JZOS to
establish settings for the z/OS language environment. The initialization of
Java is performed by LE as part of the z/OS operating system. By default, the
setting assigns the UMASK to files created in the HFS file system. Note that
UMASK is a compliment to the permission assignment. The default value is
022, which will give new files a permission setting of 644 for files and 755 for
directories. Refer to Unix Systems Services documentation for valid values
and other information.
MANAGER - Change the job card to match your system requirements.
ARGS=ISMGRAMN is set by default to start the iStrobe Manager.
000001
000002
000003
000004
000005
000006
000007
000008
000009
000010
000011
//ISTROBEM JOB
('ACCOUNT',78,1,1),'ISTROBE MANAGER',
//
//*
optional JCLLIB ORDER=(<USERID>.ISTROBE.CNTL)
//***************************************************
//*
//*
Use ARGS=ISMGRAMN to run the iStrobe Manager
//*
Use ARGS=ISMGRASP to stop the iStrobe Manager
//*
Use ARGS=ISMGRADS to test activity in the iStrobe Manager
//***************************************************
//ISMANAGR EXEC JZOSPROC Defaults are ENV=ISMGREMN,ARGS=ISMGRAMN
//*
For example:
61
Use ARGS=ISMGRASP to stop the iStrobe Manager cleanly.

the iStrobe Manager in order for the stop request to execute.
Use ARGS=ISMGRADS to get a current status of active tasks in the iStrobe
Manager. This is useful to confirm that the iStrobe Manager is
ISSMFMGR - Change the job card to match your system requirements.
ARGS=SMFMGRST is set by default to start the iStrobe SMF Manager.
000001
000002
000003
000004
000005
000006
000007
000008
000009
000010
000011
//ISTROBES JOB ('ACCOUNT'),'ISTROBE SMF MANAGER',

//
//* optional JCLLIB ORDER=(<USERID>.ISTROBE.CNTL)
//********************************************************************
//*
//*
Use ARGS="SMFMGRST" to start the iStrobe SMF Manager
//*
Use ARGS="SMFMGRSH" to shutdown the iStrobe SMF Manager
//*
Use ARGS="SMFMGRIN" to get current status of iStrobe SMF Manager
//********************************************************************
//ISSMFMGR EXEC JZOSPROC,ENV=ISMGREMN,ARGS=SMFMGRST
//*
For example:
Use ARGS=SMFMGRSH to shutdown the iStrobe SMF Manager cleanly.

the iStrobe SMF Manager in order for the stop request to execute.
Use ARGS=SMFMGRIN to get a current status of active tasks in the iStrobe
SMF Manager. This is useful to confirm that the iStrobe SMF Manager is
4. Submit the JCL from member MANAGER, or start the system task (described below),
to start the iStrobe Manager.
5. You may optionally submit the JCL from member ISSMFMGR, or start the system task
(described below) to start the iStrobe SMF Manager.
Executing the iStrobe Jobs as Started Tasks

You can, optionally, set up the iStrobe Manager to execute as a started procedure on your
z/OS system by adding the start command to the SYS1.PARMLIB(COMMNDxx) member.
Your installation may require special security authorizations for the started task to
actually execute.
iStrobe Manager as a started task

You can rename the PROC at your discretion (for example ISMANAGR) so that the longrunning task is identifiable as the iStrobe Manager or to match your systems standards.
In this setup, you would only have to start the iStrobe Manager the first time with a z/OS
console command:
START JZOSPROC
or
62
START ISMANGR
For stopping the iStrobe Manager, you can create a copy of the PROC (like ISMGRSTP)
and set the ARGS value to ISMGRASP. The iStrobe Manager normally should not have to
be stopped but, if necessary for operational reasons, the console command:
START JZOSPROC,ARGS=ISMGRASP
or
START ISMGRSTP
will notify the iStrobe Manager to cleanly terminate.
iStrobe SMF Manager as a started task

For starting the iStrobe SMF Manager, you can optionally create a copy of the PROC (like
ISSMFM) and set the ARGS value to SMFMGRST. Use the console command:
START JZOSPROC,ARGS=SMFMGRST
or
START ISSMFM
For stopping the iStrobe SMF Manager, you can create a copy of the PROC (like ISSMFS)
and set the ARGS value to SMFMGRSH. The iStrobe SMF Manager normally should not
have to be stopped but, if necessary for operational reasons, the console command:
START JZOSPROC,ARGS=SMFMGRSH
or
START ISSMFS
will notify the iStrobe SMF Manager to cleanly terminate.
Changing the Time Zone for iStrobe Manager

The member name ISMGREMN defines the Time Zone variable.
For example:
TZ = EST5EDT
EST is Eastern Standard Time
Standard Time is 5 hours west of the universal reference time
EDT is Eastern Daylight Savings Time
For more information on setting time zones in iStrobe, refer to IBMs z/OS Information
Center on the Web.
Modifying Java Heap Size for iStrobe Manager

The member name ISMGREMN defines the startup options. The iStrobe Manager is
configured with an initial heap size of 256 MB (java option = '-Xms256M') and a
maximum heap size of 1024 MB (java option = '-Xmx1024m').
To modify these parameters:
1. Stop the iStrobe Manager.
2. Locate the following two lines in member ISMGREMN.
# INSTALLER:
Sets java heap allocation if more becomes necessary
DEFS="-Xms256M -Xmx1024m
3. Make the appropriate changes to the heap sizes.

4. Restart the iStrobe Manager.

where:
63
64
65
Chapter 8.
Configuring iStrobe
Chap 8
This chapter identifies two important configuration options available to administrators

in iStrobe:
Configuring a Database for iStrobe
Configuring Security for iStrobe
Before using iStrobe, you may want to configure these two options. They are accessed
through the Administration section within iStrobe.
Other configuration options are also available. Within the iStrobe interface you can
configure:
Web service hosts (HCI)
Database archives
Profile archives
Users and Roles.
Database Configuration
iStrobe profiles are stored in a database management system (DBMS) to support advanced
reporting. Other application informationsuch as configuration, security, and user
preferencesget stored in this DBMS.
By default, iStrobe installs with the Apache Derby database. You can use this database or
you can configure another database.
iStrobe supports these databases:
Apache Derby (default)

Microsoft SQL Server
Oracle Database
IBM DB2 for z/OS
IBM DB2 for Linux, Unix, and Windows.
The iStrobe database should use a case-sensitive collation.

iStrobe requires a database user ID for installation and data access.
iStrobe can store extended characters, if the chosen database supports Unicode data.
Microsoft SQL Server and Oracle Database implement a Unicode data type solution using
national character data types. IBM DB2 uses a Unicode database solution, if the database
is created with a Unicode encoding.
For Oracle and IBM DB2, you must create the database and schema before installing
iStrobe. For Microsoft SQL Server only, the iStrobe installation creates the database and
schema.
For each DBMS, the iStrobe installation creates the schema objects, such as tables, foreign
keys, and indexes.
66
iStrobe requires one database user ID with data definition (DDL) and data manipulation
(DML) privileges for the database and schema. You are prompted for this ID and password
during the installation.
After the installation, the iStrobe Manager creates database entries for initial users and
security. Migration of profiles from the previous version of iStrobe is done with a separate
utility provided with iStrobe.
Apache Derby Database

By default, the iStrobe application will install an Apache Derby database.
Before installing iStrobe:
Be prepared to specify a repository folder. This is where the database will be stored on
the file system of the manager. The installer must have authorization to create this
folder.
Be sure to select a listening port that is not being used.
Note: To access the Derby database by default, the user ID is istrobe and the password is
istrobe.
Microsoft SQL Server Database

For Microsoft SQL Server, iStrobe uses national character datatypes.
By default, iStrobe uses case-sensitive collations with Microsoft SQL Server, causing filters
to be case-sensitive.
iStrobe redistributes and uses the jTDS JDBC drivers for Microsoft SQL Server.
Microsoft SQL Server must be installed and an instance must be running on a server.
You must know either the DNS name or the IP address of the server on which
Microsoft SQL Server is installed.
You must know either the statically assigned port number or the instance name
(dynamically assigned port) for the Microsoft SQL Server instance.
For the instance name option, the Microsoft SQL Server Browser Service must be
running on that server.
Select a name for the database.
Limit this name to alphabetic, numeric and underscore (_) characters.
Strobe does not support delimited identifiers.
You must have a logon name and password defined on the Microsoft SQL Server
instance.
The password should conform to your organization's standards.
The logon name should have these server roles:
sysadmin
dbcreator
public
Note:
Since iStrobe connects through JDBC, Microsoft SQL Server authentication

must be used.
Identify or create a schema name to be used.

Microsoft recommends that you back up the master database before creating a new
database.
Configuring iStrobe
67
Oracle Database
For Oracle Database, iStrobe uses national character datatypes. Using a database with a
Unicode character set is recommended, but not required.
iStrobe redistributes the Oracle Database JDBC drivers. You will be prompted to accept
their Oracle license during installation.
You must create an Oracle database before the iStrobe installation.
iStrobe uses the JDBC Thin (type 4) driver with Thin-style server name syntax for its
database URLs. You must know your database's service name for this syntax.
You must create a database user ID and password before the iStrobe installation for
database authentication. The Oracle CREATE USER command automatically creates a
schema with the same name. iStrobe will create all of its objects in this schema.
An Oracle Database instance must be installed and running on a server.
You must know either the DNS name or the IP address of the server on which the
Oracle database is installed.
You must know the port on which Oracle is listening.
You need a database for iStrobe and you must know its service name.
We recommend a Unicode character set.
You need a user ID and password within that database for use by the iStrobe
application. with at least the following privileges:
CREATE SESSION system privilege.

CREATE TABLE or CREATE ANY TABLE system privilege.
CREATE VIEW or CREATE ANY VIEW system privilege.
Space quota on the database table spaces or the UNLIMITED TABLESPACE system
privilege.
Your Oracle DBA must change the default value of the open_cursors parameter to at
least 400 to avoid the Maximum open cursors exceeded error message.
IBM DB2
iStrobe supports both DB2 for z/OS and DB2 for Linux, UNIX, and Windows.
iStrobe uses the type 4 driver in the IBM Data Server DB2 Driver for JDBC and SQLJ.
iStrobe does not redistribute this driver. It is available with your DB2 installation. Be sure
this driver has been installed. You will supply the directory containing the driver
(db2jcc.jar) and license file (db2jcc_license_cu.jar or db2jcc_license_cisuz.jar) during the
iStrobe installation. This directory and its driver files must be readable by the iStrobe
installation program. If necessary, you may copy them to a directory where they will be
readable.
DB2 for z/OS

iStrobe needs to access a database that you will create in one of your DB2 subsystems.
Choose any single, non-destructive subsystem in which to create this database.
DB2 for z/OS JDBC URLs use a location name instead of a database name. You will need
to know both names during iStrobe installation.
IBM DB2 for z/OS must be installed and running on a host.
68
The IBM Data Server DB2 Driver for JDBC and SQLJ must be installed for that DB2
subsystem.
You must know the DNS name or IP address of your DB2 host.
You must know the DB2 location name and port on which DB2 is listening.
Create a database and table space in your DB2 for z/OS location. iStrobe will create its
tables in this table space during installation.
The table space associated with the database must be created in a 32K
BUFFERPOOL.
The table space must be a segmented table space (SEGSIZE > 0).
The iStrobe database contains LOB data. For the iStrobe database, you may wish
to have a CREATE LOB TABLESPACE for iStrobe. Otherwise, the iStrobe LOB data
will go into the default LOB TABLESPACE.
Compuware requires specifying Unicode CCSID on the Create Database
statement to handle any extended characters.
You must have an application ID (user ID) and password for use by the iStrobe
application. This application ID will be used as the table and index creator.
The application ID must have at least the following minimum privileges:
DBADM privilege for the database.
USE privilege for the storage group.
USE privilege for the default buffer pool for user LOB data.
Be sure the Data Server DB2 Driver for JDBC and SQLJ files can be read by the iStrobe
installation program running on UNIX System Services.
DB2 for Linux, Unix, and Windows

You must create a database before iStrobe installation. Compuware requires a Unicode
code page. iStrobe will create the schema to ensure its name matches the database user ID
for Strobe Insight.
DB2 for Linux, UNIX and Windows JDBC URLs use the database name. There is no
location.
IBM DB2 for Linux, UNIX and Windows must be installed and running an instance
on a server.
The IBM Data Server DB2 Driver for JDBC and SQLJ must be installed for that DB2
instance.
You must know the DNS name or IP address of your DB2 server.
You must know the port on which the DB2 instance is listening.
Create a database for iStrobe.
The table space associated with the database must be created in a 32K
BUFFERPOOL.
You need an authorization ID and password for use by the iStrobe application.
This authorization ID needs one of the following sets of privileges:
CREATETAB authority for the database; USE privilege for its table spaces.
DBADM authority for the database.
SYSADM authority.
Be sure the Data Server DB2 Driver for JDBC and SQLJ files can be read by the iStrobe
installation program from the server on which it will run.
Configuring iStrobe
69
Security Configuration
The security features in iStrobe are optional and can utilize either your existing LDAP
security servers or X.509 certificates from a smart card for user authentication. iStrobe
does not store passwords, but does store user IDs. By requiring a user ID and either a
password or PIN to access iStrobe, you are able to provide role-based content and give
users access to specific functionality.
By default, iStrobe security is disabled upon first installing iStrobe and all content is
available to all users.
As an administrator, you may configure and enable iStrobe security after installing
iStrobe. The first time you click the button to the administration section, you are
prompted to provide the administration password. The default password is
isadministration. Having been provided the password, you are able to act as the
administrator and enable security. You also have the ability to change the administrator
password. Do this by clicking the Security button within the Administration section.
Note:
Although you are not required to secure content, you should consult with the
network security group at your site to determine whether or not to enable
security for iStrobe. You always have the ability to disable security that has been
enabled.
With security configured, users must present credentials for authentication and access to
iStrobe. When security is enabled with an LDAP authentication server, users are
prompted for both a user ID and password. When security is enabled with an X.509
certificate from a smart card, users are prompted for a PIN only.
Enable security using LDAP

To configure and enable LDAP security, the security administrator must provide the
following:
iStrobe administrator(s) ID. Do not include the domain name in this field.
Binding URL for binding the URL to the LDAP server
Distinguished Name (DN) of a service account used to search LDAP for the
service account
Password of an account that can be used to bind to the LDAP server
Search base and filter to use to locate the users ID
When logging on, users are prompted for their user ID and password.
1. Start iStrobe in your browser and click the Administration button. The
Administration window appears.
2. Click Security. The Security window appears.
3. Select the LDAP security mode:
4. Enter the required information in each of the fields:
LDAP server URL

LDAP server port number
Bind with
Distinguished name (DN)
Password for DN
Search base
Search filter
iStrobe administrator(s)
5. Click LDAP server connection test. If an LDAP server connection is available, you
will be able to apply this security configuration.
6. Click Apply.
70
You must restart your web application for the security settings to become effective. When
logging on, users will be prompted for their user ID and password.
Enable security using X.509 (Smart Card)

With security configured for X.509 (Smart Card), users must first have their smart card
plugged into the reader. They must also have a valid X.509 certificate. And they must log
on using the https:// protocol as the first element in the URL.
To configure and enable X.509 (Smart Card) security, the security administrator must
provide the following:
iStrobe administrator(s) ID
X.509 mask. This is needed to extract the user ID from the smart card
certificate.
When logging on, users are prompted for their smart card PIN. Those users without both
the smart card and PIN for that card are denied access to iStrobe.
3. Select the X.509 (Smart Card) security mode:
X.509 mask
5. Click Apply.
logging on, users will be prompted for their smart card PIN.
Enable security using X.509 with LDAP

With security configured for X.509 with LDAP, users can log on with a smart card and
PIN using the https:// protocol or with LDAP using the http:// protocol.
To configure and enable X.509 with LDAP security, the security administrator must
provide the following:
LDAP server URL

Password for DN
Search base
Search filter
iStrobe Administrator
X.509 mask. This is needed to extract the user ID from the smart card
certificate.
3. Select the X.509 with LDAP security mode:
LDAP server URL

Bind with
Configuring iStrobe
71
Password for DN
Search base
Search filter
X.509 mask
5. Click LDAP server connection test. If an LDAP server connection is available, you
will be able to apply this security configuration.
6. Click Apply.
logging on, users will be prompted for their user ID and password for LDAP or their smart
card PIN.
Enable security using Kerberos

With security configured for Kerberos, users are automatically signed on using their user
ID.
To configure and enable Kerberos, the security administrator must provide the following:
Service principal
Keytab location
iStrobe administrator(s).
3. Select the Kerberos security mode:
Service principal
Keytab location
5. Click Kerberos login test. If you are able to log in, you will be able to apply this
security configuration.
6. Click Apply.
logging on, users are not prompted.
Important:
Only administrators can add or remove users and manage access to specific functionality.
This function appears in the list of functions on the administration tab in the
Application Controls panel. See Other Configuration Considerations on page 72.
Disable security
Start iStrobe in your browser and click the Administration button. The Administration
window appears.
2. Select the None radio button.
3. Click Apply.
logging on, users are no longer prompted for their user ID and password, and all content
and profiles are available to all users.
72
Other Configuration Considerations

Start iStrobe in your browser and click the Administration button. The Administration
window appears.
The install sets up much of the configuration. Compuware recommends reviewing all the
configuration parameters when you do the initial install. Refer to the online help for
detailed instructions on updating each page.
1. Click General Configuration. The General Configuration window appears.
Note:
If the iStrobe Manager Connection Error dialog box appears instead of the
iStrobe Configuration page, review your installation for errors and resolve
them. If you still have problems, refer to Frontline for additional
information on connection problems.
In the Email box, enter the Email server name and Sender address to allow you to use
the email notification option when new profiles are downloaded from Strobe.
In the iStrobe manager communications box, do not change the values for the host
or port fields unless there is an error. You may want to change the location of the
Quarantine directory. The iStrobe Manager service or daemon ID must have update
access to this directory.
2. Navigate back to the Administration window.
3. Click Users and Roles. The Users and Roles window appears in the display pane.
If you want to restrict access to iStrobe content other than administration use the
Roles page to create roles to assign to users. The install creates three roles:
USER - Has access to all content except Administration and defining new Strobe
Insight Reports.
ADMINISTRATOR - This is not listed in the Role page to prevent accidental
deletion. You can give others access to Administration by going to the user page
and adding ROLE_ADMIN.
Super - Has access to all content.
Since users are created automatically when iStrobe is accessed, you would not need to
visit this window at this time except to create another iStrobe administrator.
4. Navigate back to the Administration window.
5. Click Host Connections. The Host Connections window appears. Host Connections
is used to define configuration connections to the Host Communications Interface
(HCI) component to support measurement requests from the iStrobe Web Service.
The Compuware HCI can be configured to support multiple Strobe instances within a
network. This tab allows you to enter specifications for multiple HCI instances. Refer
to the Strobe/HCI Configuration documentation for more information on details to
support multiple Strobe instances. If you wish to use this web service, contact
Compuware Technical Support for full documentation.
73
Chapter 9.
Customizing iStrobe
Chap 9
This chapter describes the following ways to customize your iStrobe installation:
Changing the Location of the iStrobe Log File on page 73.
Installing the iStrobe plug-in to Eclipse on page 74.
Changing the Location of the iStrobe Log File

The iStrobe log file (istrobe.log) captures error and informational messages used by
Compuware Customer Support.
By default, the iStrobe installation program places the istrobe.log in the istrobe/logs
directory. iStrobe archives the log file on a monthly basis and appends a date to the
name. For example, an iStrobe log file archived in January 2007 would be named
istrobe.log.2007-01.
To change the location of the iStrobe log file, use one of the following procedures:
Modify the log4j.xml file on page 73.
Pass a parameter to the Java Virtual Machine (JVM), in Tomcat or WebSphere, on
page 73.
Modifying the log4j.xml file to Change the Location of the iStrobe Log
File
The easiest way to change the location of the iStrobe log file is to edit the log4j.xml file,
located in the istrobe/WEB-INF directory.
To change the location of the log file, change the following line of code in the log4j.xml
file. Replace ${istrobe#.#.log.home} with the path of an existing directory:
<param name="File" value="${istrobe#.#.log.home}/istrobe.log"/>
For example, to place the istrobe.log in the C:/ istrobe23/logs directory, you would
change the code as follows:
<param name="File" value="C:/istrobe23/logs/istrobe.log"/>
Passing a JVM Parameter to Change the Location of the iStrobe Log File
If your site will not allow you to edit the log4j.xml file, you can pass a parameter to the
JVM in Tomcat or WebSphere with the new location of the iStrobe log file.
Passing a JVM Parameter in Tomcat

You can pass a parameter with the new location of the iStrobe log file to the JVM each
time Tomcat starts.
Replace the # symbols with the iStrobe version number:
-Distrobe#.#.log.home=C:\istrobe\logs
74
Note: There is no period between the Distrobe and the version number. Placing a period
between them prevents the log file from being created.
A version subdirectory is created within the specified path.
C:\istrobe\logs\#.#\istrobe_server.log
To illustrate the above, assume you are customizing iStrobe 5.1. The parameter and value
is set as such:
-Distrobe5.1.log.home=C:\istrobe\logs
The log file is created in the following directory:

C:\istrobe\logs\5.1\istrobe_server.log
Passing a JVM Parameter in WebSphere

To pass a parameter with the new location of the iStrobe log file to the JVM, choose the
WebSphere procedure that is appropriate for your iStrobe installation:
Passing a JVM Parameter for WebSphere 7.0

1. Log on to the WebSphere Administrative Console.
2. In the left-hand navigation pane, click Servers > Application Servers.
3. Click the server where iStrobe is deployed.
4. Expand Java and Process Management under Server Infrastructure.
5. Click Process Definition > Java Virtual Machine.
6. Type the istrobe#.#.log.home argument in the Generic JVM Arguments field.
For example, to specify the location istrobe23/logs for the iStrobe log file, the
parameter should appear as follows:
-Distrobe#.#.log.home=/istrobe23/logs
Note:
The name of the argument and the path are case sensitive.
7. Click Apply > OK.

Note: Because the iStrobe log file uses the ASCII character set, you must transfer the log
file using binary settings from z/OS to a Windows operating system to be able to
read it.
Installing the Compuware Workbench Web-Based PlugIn for iStrobe

iStrobe can be launched from within the Compuware Workbench or installed into an
Eclipse or RDz instance. To use iStrobe within the Compuware Workbench, refer to the
Mainframe Modernization Components Installation Guide for installation instructions.
75
Chapter 10.
iStrobe Web Service
Chap 10
iStrobe 5.1 accepts an HTTP request to initiate a Strobe measurement of an active z/OS
process. You can use this feature with a performance monitor to start a Strobe
measurement when you notice performance problems on the mainframe and would like
a deep dive analysis.
iStrobe Configuration
To configure iStrobe you need to specify Host Name or IP address, Port number, and
Strobe signature for each System you want to use with the Web Service. The z/OS systems
programmer who set up Strobe and the HCI will have this information. Go to the
Administration tab and select Web Services Hosts in the Application Controls pane.
You may configure as many HCIs as needed to connect to your Strobe Release 4.2 and
above installations. The connection for an individual measurement is specified in the
Web Service request. Refer to the iStrobe online help Manage HCIs page for more details
about the individual fields.
How to Use the API

Measurement requests are sent to the iStrobe Web Server as a Web Service request via
HTTP or HTTPS. You should consider using an HTTPS connection, because the z/OS ID
and password are included in the request. The z/OS ID only needs permission to start a
Strobe measurement. It does not need access to TSO.
Requesting WSDL URL

The Web Services Description Language (WSDL) of this Web Service can be retrieved
using this URL:
Figure 10-1. URL to Retrieve WSDL
HTTP://istrobeHost:port/iStrobeWebApplicationName/ws/Measurement/measurement.wsdl
Web Service Request to iStrobe Server

The SOAP body expected by the iStrobe Web Service is described below. The requester will
receive the return value formatted as a SOAP response. See below for the available request
types.
Figure 10-2. URL Format of the Web Service Request to the iStrobe Server
HTTP://istrobeHost:port/iStrobeWebApplicationName/ws/Measurement
76
When the message for an addActive request is sent to the iStrobe Web Service, a
response will be returned. If the request is successfully processed, the response will
include the URL for the iStrobe measurement report.
Figure 10-3. Example Web Service Request SOAP Body Format

<AddActiveRequest xmlns="http://istrobe.compuware.com/ws/Measurement" >
<reqType>addActive</reqType> 
<logonid>mainframe-userid</logonid>
<password>mainframe-password</password>
<tags>list of tags</tags>
<profileName>profile name to be created</profileName>
<emailto>email-id to notify</emailto>
<duration>minimum measurement time</duration>
<samples>number of samples</samples>
<limit>number of smaple dataset to be created</limit>
<finalAction>quit|stop|continue</finalAction>
<hlq>MY.GROUP</hlq>
<tranid>transaction id mask</tranid>
</AddActiveRequest>
Descriptions of Elements
reqType
addActive. Adds a request for measurement of an active job.
logonid
Required. z/OS logon ID.
password
Required. z/OS password. An SSL connection should be used to prevent exposing the
password to the network.
jobname
Required. Jobname to be measured.
system
Required. Host Connection name defined by the iStrobe HostConnections
configuration screen.
tags
Optional. Tags to be assigned to profile.
profileName
Optional. Name of the profile. The default is the jobname.
emailto
Optional. SMTP e-mail address to notify when the measurement is complete and the
profile is ready to view.
duration
Optional. Estimated minimum measurement time in minutes. See the Strobe User
Guide for details.
samples
Optional. The target number of samples to take during the measurement session. See
the Strobe User Guide for details.
iStrobe Web Service
77
limit
Optional. Suspends sampling when the target number of samples is reached. See the
Strobe User Guide for details.
finalAction
Optional. Controls the measurement session when the final dataset has been
completed. Value can be one of the following: {QUIT | STOP | CONTINUE}. See the
Strobe User Guide for details.
hlq
Optional. High Level Qualifier. DSNAME High level qualifier - Temporary dataset
prefix.
tranid
Optional. May occur up to 5 times. Used for transaction profiling, the tranids are
transaction ID masks used to specify the transactions to be measured.
Figure 10-4. Example of Returns: SOAP Body Format
<?xml version="1.0" encoding="UTF-8"?>
<ns2:AddActiveResponse xmlns:ns2="http://istrobe.compuware.com/ws/Measurement">
<ns2:reqType>addQueue</ns2:reqType>

<ns2:returnCode>0</ns2:returnCode>

<ns2:reportUrl>http://iStrobe.server:8080/iStrobe43/iStrobe.html?js=on&auto=on&
amp;report=MSD&profile=D%3A%5Ceclipse%5C... Sample11</ns2:reportUrl>
<ns2:messageList>
<ns2:message>STR6300I Input = ADD SBHCI,STEP=*ALL,GOMIN=0002,SAMPLES=009999,
NONOTIFY,LIMIT=(01,QUIT),ISPFFLAG=0000,RJCLFILE=(_YES_)</ns2:message>
<ns2:message>STR6261I 0581 JOBNAME1 QUEUED STEP=*ALL CREATED=(09:29:53
06/23/2011) GOMIN=2 SAMPLES=9999 LIMIT=(1,QUIT)</ns2:message>
<ns2:message>STR6261I EXPIRATION=(06/30/2011) NONOTIFY</ns2:message>
<ns2:message>STR6130I ADD operation completed</ns2:message>
</ns2:messageList>
<ns2:statusList>
<ns2:status number="581" state="QUEUED"/>

</ns2:statusList>
</ns2:AddActiveResponse>
If there is an error in the addActive request, the return code will be non-zero with an
appropriate message.
connectTest Web Service Request to iStrobe Server - Detail

This request is used to test the z/OS connection information to confirm that it is correct
and available.
Figure 10-5. URL Format of connectTest Web Service Request
HTTP://istrobeHost:port/iStrobeWebApplicationName/ws/Measurement
See below for the available request types.
78
Figure 10-6. Web Service Request SOAP Body Format

<ConnectTestRequest xmlns="http://istrobe.compuware.com/ws/Measurement"/>
Figure 10-7. Returns (Response): Soap Body Format

<?xml version="1.0" encoding="UTF-8"?>
<ConnectTestResponse>
<returnCode>nnnn</returnCode>
<message>message_string</message>
</ConnectTestResponse>
If there is an error in the connectTest request, the return code will be non-zero with an
appropriate message. If the request is successful, the return code will be 0, and the
message will include the available system list.
Java Example
An example of using the Web service with a Java program was installed with the iStrobe
manager in the utilities\web-service\clientsample sub-directory. See the readme.txt
file for detailed instructions about using this sample.
Using SSL with the Web Service

You may want to secure the communications between the Web server and the Web
service client by using Secure Sockets Layer (SSL/HTTPS). In order to request an Add
Active via the SSL, the Web server and the Web service client should be configured for the
SSL. The protocol is controlled by the Web server so that no special coding is needed in
the iStrobe Web Service.
The settings for the Web server configuration for SSL and the client should be
documented by the Web server provider. Here is an example of how to set up the SSL
configuration for the Apache Tomcat and the Web service client using JSSE (Java Secure
Socket Extension).
Apache Tomcat Server Configuration for SSL

The JKS format which is being used in this example is Javas standard Java KeyStore
format, and is the format created by the keytool command-line utility. This tool is
included in the JDK. For more information, refer to the HOW-TO guide which can be
found on the Apache Tomcat Web site
(http://tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html or
http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html).
1. Generate the key for the Tomcat server using the keytool command as follows:
Enter the keytool command:
keytool -genkey -alias tomcat -keyalg RSA -keystore server.keystore
Enter password: changeit

Provide inputs when prompted.
Provide the same password, changeit, when prompted.
The key file server.keystore will be created under the current directory.
2. Generate the key for the web service client using the keytool command as follows:
iStrobe Web Service
79
Enter the keytool command:

keytool -genkey -alias client -keyalg RSA -keystore client.keystore
Enter password: changeit

Provide inputs when prompted.
Provide the same password, changeit, when prompted.
The key file client.keystore will be created under the current directory.
3. Export the self certificate for the Tomcat server using the following keytool
command:
keytool -selfcert -export -alias tomcat -storepass changeit -file server.cer keystore server.keystore.
The certificate server.cer will be created under the current directory.

4. Export the self certificate for the web service client using the following keytool
command:
keytool -selfcert -export -alias client-storepass changeit -file client.cer keystore client.keystore.
The certificate client.cer will be created under the current directory.

5. Import the server certificate into client.keystore using the keytool command as
follows. This file will be used by the SSL client or web service client.
keytool -import -v -trustcacerts -alias tomcat -file server.cer keystore client.keystore -keypass changeit -storepass changeit
6. Find the file server.keystore under the current directory and copy it to the
$CATALINA_HOME directory.
7. Uncomment the SSL HTTP/1.1 Connector entry in
CATALINA_HOME/conf/server.xml (Figure 10-8) and make any necessary revisions.
Figure 10-8. Example SSL HTTP/1.1 Connector Entry

<Connector acceptCount="100" disableUploadTimeout="true"
enableLookups="false" maxHttpHeaderSize="8192"
maxSpareThreads="75" maxThreads="150" minSpareThreads="25"
port="8443" scheme="https" secure="true" sslProtocol="TLS"
clientAuth="false"
keystoreFile="${catalina.home}/server.keystore" />
8. Restart Tomcat as you normally would, and you will be able to access iStrobe via SSL
(HTTPS) using the following URL:
HTTPS://istrobeHost:8443/iStrobeWebApplicationName/iStrobe51.html
Web Service Java Client Using SSL Connection

To access iStrobe web service via SSL based on the Tomcat configuration in the previous
section, use following JVM parameter:
-Djavax.net.ssl.trustStore=client.keystore
Or, you can set the following parameter in your web service client Java program:
System.setProperty("javax.net.ssl.trustStore", "<proper-path>/client.keystore");
The file client.keystore is the same file generated in the previous section.
80
The URL for the web service will be similar to the following:
HTTPS://istrobeHost:8443/iStrobeWebApplicationName/ws/Measurement
81
Chapter 11.
Uninstalling iStrobe 5.1
Chap 11
Follow the procedures in this chapter to uninstall iStrobe. If you are uninstalling in order
to move the iStrobe application to a different server, and would like to retain the existing
configuration, reports, preferences, etc., be certain to:
Export your User-defined Help (see Help for User-defined Help)
Uninstalling iStrobe on Windows with Tomcat

1. Log on to your system as a user with administrator authority.
2. Use the Windows Add or Remove Programs dialog box to remove the iStrobe
application.
3. Choose whether or not to remove the iStrobe database.
4. Delete any additional files or folders that the uninstall did not delete.
Uninstalling iStrobe on Linux with Tomcat

1. Log on to your system as superuser (root).
2. Use the Tomcat Manager to undeploy the iStrobe application.
3. Navigate to <iStrobe_install_directory>/uninstall.
4. Execute the command:
./uninstall

Uninstalling iStrobe on Linux with WebSphere

1. Log on to your system as superuser (root).
2. Use WebSpheres Integrated Solutions Console to uninstall the iStrobe application.
3. Navigate to <iStrobe_install_directory>/uninstall.
4. Execute the command:
./uninstall

82
Uninstalling iStrobe on z/OS USS with Tomcat

1. Log on to your system.
2. Use the Tomcat Manager to undeploy the iStrobe application.
3. Stop the iStrobe Manager. Instructions for stopping and starting the iStrobe Manager
are found in the installation chapter applicable to your platform.
export IBM_JAVA_ENABLE_ASCII_FILETAG=true
java -Xnoargsconversion -Dfile.encoding=ISO8859-1 -jar/
<istrobe_install_directory>/uninstall/uninstaller.jar -i console 2>
/dev/null
Notes:
There is a sample shell script named uninstall.sh located in
<CDROM>:\cpwr\USS that you can use as a template.
If you are executing the shell script, be sure to place it outside the directory
where iStrobe is installed.
Uninstalling iStrobe on z/OS USS with WebSphere

1. Have your WebSphere Administrator uninstall the iStrobe application.
2. Log on to the mainframe and navigate to an OMVS command prompt.
3. Stop the iStrobe Manager. Instructions for stopping and starting the iStrobe Manager
are found in the installation chapter applicable to your platform.
export IBM_JAVA_ENABLE_ASCII_FILETAG=true
java -Xnoargsconversion -Dfile.encoding=ISO8859-1 -jar/
<istrobe_install_directory>/uninstall/uninstaller.jar -i console 2>
/dev/null
Notes:
There is a sample shell script named uninstall.sh located in
<CDROM>:\cpwr\USS that you can use as a template.
If you are executing the shell script, be sure to place it outside the directory
where iStrobe is installed.
83
Index
E
Event Processor
who to involve in installation, 13
I
install
Windows, 18
integrated solutions console, 37
iStrobe Manager, 48, 6061
started task, 49, 61
J
JZOS, 47, 59
L
Linux, 31
Tomcat, 23
S
server requirements
hardware, 12
software requirements
server, 12
system overview, 11
T
Tomcat
Linux, 23
Windows
Windows
Tomcat, 17
U
USS system administrator, 41, 51
W
Web Container Environment, 13
WebSphere, 31
integrated solutions console, 37, 57
Windows installation, 18
WSADMIN tool, 34, 54
Z
z/OS UNIX
system services, 41, 51
84

Istrobe Install

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Istrobe Install

Uploaded by

Copyright:

Available Formats

iStrobe

iStrobe Installation Guide

Please direct questions about iStrobe

Chapter 2. Upgrading iStrobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 4. Installing or upgrading iStrobe on Linux with Tomcat . . . . . . . . . . . . .

iStrobe Installation Guide

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

Chapter 9. Customizing iStrobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

Chapter 11. Uninstalling iStrobe 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

iStrobe Installation Guide

This guide provides instructions on how to install iStrobe. iStrobe is an application

How This Guide is Organized

iStrobe Installation Guide

How to Use This Guide

iStrobe 3rd Party Licensing Documentation

Compuware iStrobe Customer Support

Compuware Go Customer Support Website

Contacting Customer Support

Please report all high-priority issues by telephone.

iStrobe Installation Guide

When iStrobe is installed on a standalone workstation, it supports a single user.

iStrobe System Overview

iStrobe Installation Guide

Server Software Requirements

Server Hardware Requirements

File Server Requirements

Database Server Requirements

Individuals to Participate in the Installation

Web Container Environment

Microsoft SQL Server

Complete requirements for installing a database are detailed in Chapter 8, Configuring

iStrobe Installation Guide

<iStrobe Web Application Root>/WEBINF/security.properties

<iStrobe Manager installed

<iStrobe Web Application Root>/WEBINF/ldapControl.properties

<iStrobe Manager installed

Migrating from Supported Releases

iStrobe Installation Guide

A Windows Server Administrator should install or upgrade iStrobe for departmental or

<iStrobe Web Application Root>/WEBINF/security.properties

<iStrobe Manager installed

<iStrobe Web Application Root>/WEBINF/ldapControl.properties

<iStrobe Manager installed

iStrobe Installation Guide

The installation does the following:

Installing or upgrading iStrobe

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

The Tomcat Installation dialog box appears.

Installing or upgrading iStrobe on Windows with Tomcat

The webserver ID needs update permissions to this folder.

If you are doing an upgrade of an existing installation, the Pre-installation

If you choose the default repository:

The webserver ID needs update permissions to this folder.

iStrobe Installation Guide

IBM DB2 for LUW:

IBM DB2 for z/OS:

The recommended Tomcat memory settings are as follows:

Installing or upgrading iStrobe on Windows with Tomcat

Maximum memory pool field is set to 1536 MB or greater

Java HEAP storage memory is set to 512 MB or greater

When running as a Windows service:

Change the initial memory pool to 1024 MB.

When running as a Windows process: