Installation Guide
Release 5.1
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
17
17
18
21
21
21
22
22
22
22
23
23
24
27
27
28
28
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
73
73
75
75
75
75
75
76
77
78
78
78
79
81
81
81
81
82
82
73
73
74
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Introduction
Intro
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.
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.
Introduction
Web
You can report issues via the Quick Link Create & View Support Cases on the
Compuware Go home page.
Note:
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.
Installation Overview
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:
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.
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.
Installation Overview
13
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.
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.
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
For additional security installation details, refer to Security Configuration on page 69.
16
17
Chapter 3.
Installing or upgrading iStrobe on Windows with
Tomcat
Chap 3
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).
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
18
If installing from an FTP image, run setup.exe from the root of that image.
For
a new installation
Manager Host
Manager Port
Service Name
SMF Manager Port
an upgrade installation
Service Name
SMF Manager Port
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.
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:
When you choose the default repository (Derby) instead of a DBMS, you will
not be able to use the iStrobe SMF Manager.
Port number
If you choose a DBMS repository:
Microsoft SQL Server:
Enter the following as prompted, and then click Next:
Database User ID
Password for the database user ID
Schema
Database Server
Port
Database Name
Instance Nameif you select an instance name other than the default, the
port value is ignored.
Oracle:
Enter the following as prompted, and then click Next:
Database User ID
Password for the Database User ID
Schema
Read and accept the license agreement
Database Server
Port
Database Name
20
Database User ID
Password for the Database User ID
Schema
Database Server
Port
Database Name
Folder for the IBM JDBC driver (db2jcc.jar) location
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:
21
-Xmx1536m ^
-XX:PermSize=256m -XX:MaxPermSize=512m ^
Note:
22
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
23
Chapter 4.
Installing or upgrading iStrobe on Linux with Tomcat
Chap 4
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.
A port number for the iStrobe Manager to listen on (the default is 24354, which
should not conflict with most systems).
A port number for the iStrobe SMF Manager to listen on (the default is 24355).
IMPORTANT NOTE WHEN UPGRADING FROM 4.4.0:
If you are upgrading from iStrobe 4.4.0 to iStrobe 5.1.0, and you want the upgrade 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
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
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>
export PATH=$JAVA_HOME/bin:$PATH
./install.bin -i console
Note:
25
8. Select Tomcat and press Enter. The Supported platforms for Tomcat panel appears.
9. Read the supported platform information to ensure that you plan to use a supported
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:
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:
When you choose the default repository (Derby) instead of a DBMS, you will
not be able to use the iStrobe SMF Manager.
Port number
If you choose a DBMS repository:
IBM DB2 for z/OS:
Enter the following as prompted and press Enter when complete:
26
Database User ID (the database ID must have at least the minimum privileges
as specified in DB2 for z/OS on page 67)
Password for the Database User ID
Schema
Database Server (DNS name)
Port
Location Name
Database.Tablespace Name
Folder for the IBM JDBC driver (db2jcc.jar) location
IBM DB2 for LUW:
Enter the following as prompted and press Enter when complete:
Database User ID
Password for the Database User ID
Schema
Database Server
Port
Database Name
Folder for the IBM JDBC driver (db2jcc.jar) location
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:
Enter the following as prompted and press Enter when complete:
Database User ID
Password for the Database User ID
Schema
Read and accept the license agreement
Database Server
Port
Database Name
This prompt appears only if the install cannot determine the version of
Tomcat.
27
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.
20. 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. 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.
Ex. http://myserver:8080/istrobe
Note:
-Xms1024m
-Xmx1536m
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
If you are having difficulty stopping the iStrobe Manager daemon, you may issue the
following command:
mgrcmd.sh kill
If you are having difficulty stopping the iStrobe Manager daemon, you may issue the
following command:
smfmgrcmd.sh kill
29
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. 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.
Ex. http://myserver:8080/istrobe
30
31
Chapter 5.
Installing or upgrading iStrobe on Linux with
WebSphere
Chap 5
Before Beginning
Before beginning the installation, you should have the following:
For your iStrobe Manager and Server:
A supported version of Java installed and configured.
A supported version of WebSphere installed and configured.
The ID and password for the iStrobe Manager daemon with full-control-access to
the HFS/ZFS directories you plan to use for the performance profiles.
A port number for the iStrobe Manager to listen on (the default is 24354, which
should not conflict with most systems).
A port number for the iStrobe SMF Manager to listen on (the default is 24355).
IMPORTANT NOTE WHEN UPGRADING FROM 4.4.0:
If you are upgrading from iStrobe 4.4.0 to iStrobe 5.1.0, and you want the upgrade 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
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
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
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.
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.
The Introduction panel appears.
Note:
4. After reading the panel, press Enter. The License agreement panel appears.
5. Read the license agreement, pressing Enter until you have scrolled through and read
the entire agreement.
6. Type Y and press Enter to accept the terms of the license agreement. The
Application server panel appears.
7. Select the WebSphere Application Server and press Enter. The Supported platforms
for IBM WebSphere panel appears.
8. Read the supported platform information to ensure that you plan to use a supported
operating system, then press Enter. The Install folder panel appears.
9. 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.
34
Note:
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:
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.
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.
35
When you choose the default repository (Derby) instead of a DBMS, you will
not be able to use the iStrobe SMF Manager.
Port number
If you choose a DBMS repository:
IBM DB2 for z/OS:
Enter the following as prompted and press Enter when complete:
Database User ID (the database ID must have at least the minimum privileges
as specified in DB2 for z/OS on page 67)
Password for the Database User ID
Schema
Database Server (DNS name)
Port
Location Name
Database.Tablespace Name
Folder for the IBM JDBC driver (db2jcc.jar) location
36
Database User ID
Password for the Database User ID
Schema
Database Server
Port
Database Name
Folder for the IBM JDBC driver (db2jcc.jar) location
Database User ID
Password for the database user ID
Schema
Database Server
Port
Database Name
Instance Nameif you select an instance name other than the default, the
port value is ignored.
Oracle:
Enter the following as prompted and press Enter when complete:
Database User ID
Password for the Database User ID
Schema
Read and accept the license agreement
Database Server
Port
Database Name
After setting up and starting the iStrobe SMF Manager, be sure to return to
this step and continue the installation as detailed below.
37
./iStrobe_Unix_install.ksh
where:
host address is the name of the server where you just installed iStrobe.
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.
Ex. http://myserver:8080/istrobe
When you choose the default repository (Derby) instead of a DBMS, you will
not be able to use the iStrobe SMF Manager.
Port number
If you choose a DBMS repository:
IBM DB2 for z/OS:
Enter the following as prompted and press Enter when complete:
Database User ID (the database ID must have at least the minimum privileges
as specified in DB2 for z/OS on page 67)
Password for the Database User ID
Schema
Database Server (DNS name)
38
Port
Location Name
Database.Tablespace Name
Folder for the IBM JDBC driver (db2jcc.jar) location
Database User ID
Password for the Database User ID
Schema
Database Server
Port
Database Name
Folder for the IBM JDBC driver (db2jcc.jar) location
Database User ID
Password for the database user ID
Schema
Database Server
Port
Database Name
Instance Nameif you select an instance name other than the default, the
port value is ignored.
Oracle:
Enter the following as prompted and press Enter when complete:
Database User ID
Password for the Database User ID
Schema
Read and accept the license agreement
Database Server
Port
Database Name
After starting the iStrobe SMF Manager, be sure to return to this step and
continue the installation as detailed below.
39
where:
host address is the name of the server where you just installed iStrobe.
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.
Ex. http://myserver:8080/istrobe
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.
If you are having difficulty stopping the iStrobe Manager daemon, you may issue the
following command:
mgrcmd.sh kill
40
where:
host address is the name of the server where you just installed iStrobe.
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.
Ex. http://myserver:8080/istrobe
41
Chapter 6.
Installing or upgrading iStrobe on z/OS System
Services with Tomcat
Chap 6
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
-Dfile.encoding=ISO8859-1
42
From
To
If you want to use the Web Service interface for requesting a Strobe measurement,
contact your Strobe administrator to get the following Host Communications (HCI):
HCI Host
HCI Port
default Strobe signature.
If you decide later to use the Web Service interface, you may setup the HCI
connection information in the Configuration section of Administration.
The iStrobe installation may require up to 250 MB of temporary space during the
installation. When the installation is complete, the temporary installation files are
removed.
The installation does the following:
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:
Note:
43
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>
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 changes
should be made:
Add:
4. Be sure the install.sh file has execute authority and execute it.
The Introduction panel appears.
Note:
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.
8. Select Tomcat and press Enter. The Supported platforms for Tomcat panel appears.
9. Read the supported platform information to ensure that you plan to use a supported
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 with
the iStrobe SMF Manager panel in step 12.
Note:
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:
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 Unix command to set the ownership
of these directories to the user ID associated with the iStrobe Manager.
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.
17. From the iStrobe repository panel, 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.
Port number
If you choose a DBMS repository:
IBM DB2 for z/OS:
Enter the following as prompted and press Enter when complete:
Database User ID (the database ID must have at least the minimum privileges
as specified in DB2 for z/OS on page 67)
Password for the Database User ID
Schema
Database Server (DNS name)
Port
Location Name
Database.Tablespace Name
Folder for the IBM JDBC driver (db2jcc.jar) location
IBM DB2 for LUW:
Enter the following as prompted and press Enter when complete:
Database User ID
Password for the Database User ID
Schema
Database Server
Port
Database Name
Folder for the IBM JDBC driver (db2jcc.jar) location
45
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:
Enter the following as prompted and press Enter when complete:
Database User ID
Password for the Database User ID
Schema
Read and accept the license agreement
Database Server
Port
If you are using a 3270 device, you will need to press PF8 to check the status of
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.
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.
20. Open iStrobe by pointing your web browser to:
<host address>:<application server port number>/<iStrobe context root>
where:
host address is the name of the server where you just installed iStrobe.
application server port number is the port on which Tomcat is listening.
iStrobe context root is the name you entered in step 15 on page 44.
Ex. http://myserver:8080/istrobe
Note:
46
47
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 sysid on JOBPARM card to the target z/OS system name.
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
//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)
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)
49
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
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
50
where:
host address is the name of the server where you just installed iStrobe.
application server port number is the port on which Tomcat is listening.
iStrobe context root is the name you entered in step 15 on page 44.
Ex. http://myserver:8080/istrobe
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.
Before you begin the iStrobe installation, determine where you will store your
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
52
From
To
53
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>
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 changes
should be made:
Add:
4. Be sure the install.sh file has execute authority and execute it.
The Introduction panel appears.
Note:
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.
8. Select the WebSphere Application Server and press Enter. The Supported platforms
for IBM WebSphere panel appears.
9. Read the supported platform information to ensure that you plan to use a supported
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
54
11. Enter the Manager host and press Enter. Enter the Manager port and press Enter. The
iStrobe SMF Manager panel appears.
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:
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 Unix command to set the ownership
of these directories to the user ID associated with the iStrobe Manager.
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.
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:
When you choose the default repository (Derby) instead of a DBMS, you will
not be able to use the iStrobe SMF Manager.
Port number
If you choose a DBMS repository:
IBM DB2 for z/OS:
Enter the following as prompted and press Enter when complete:
Database User ID (the database ID must have at least the minimum privileges
as specified in DB2 for z/OS on page 67)
Password for the Database User ID
Schema
Database Server (DNS name)
Port
Location Name
56
Database.Tablespace Name
Folder for the IBM JDBC driver (db2jcc.jar) location
IBM DB2 for LUW:
Enter the following as prompted and press Enter when complete:
Database User ID
Password for the Database User ID
Schema
Database Server
Port
Database Name
Folder for the IBM JDBC driver (db2jcc.jar) location
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:
Enter the following as prompted and press Enter when complete:
Database User ID
Password for the Database User ID
Schema
Read and accept the license agreement
Database Server
Port
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.
57
where:
host address is the name of the server where you just installed iStrobe.
application server port number is the port on which WebSphere is listening.
iStrobe context root is the name you entered in step 14 on page 54.
Ex. http://myserver:8080/istrobe
When you choose the default repository (Derby) instead of a DBMS, you will
not be able to use the iStrobe SMF Manager.
58
Port number
If you choose a DBMS repository:
IBM DB2 for z/OS:
Enter the following as prompted and press Enter when complete:
Database User ID (the database ID must have at least the minimum privileges
as specified in DB2 for z/OS on page 67)
Password for the Database User ID
Schema
Database Server (DNS name)
Port
Location Name
Database.Tablespace Name
Folder for the IBM JDBC driver (db2jcc.jar) location
IBM DB2 for LUW:
Enter the following as prompted and press Enter when complete:
Database User ID
Password for the Database User ID
Schema
Database Server
Port
Database Name
Folder for the IBM JDBC driver (db2jcc.jar) location
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:
Enter the following as prompted and press Enter when complete:
Database User ID
Password for the Database User ID
Schema
Read and accept the license agreement
Database Server
Port
If you are using a 3270 device, you will need to press PF8 to check the status of
the installation.
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
SMF Managerbe sure to return to this step and continue the installation as
detailed below.
where:
host address is the name of the server where you just installed iStrobe.
application server port number is the port on which WebSphere is listening.
iStrobe context root is the name you entered in step 14 on page 54.
Ex. http://myserver:8080/istrobe
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 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 sysid on JOBPARM card to the target z/OS system name.
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',
//
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:
61
// JCLLIB ORDER=(<USER>.ISTROBE.CNTL)
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)
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
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
where:
host address is the name of the server where you just installed iStrobe.
application server port number is the port on which WebSphere is listening.
iStrobe context root is the name you entered in step 14 on page 54.
Ex. http://myserver:8080/istrobe
63
64
65
Chapter 8.
Configuring iStrobe
Chap 8
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:
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.
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.
Before installing iStrobe:
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:
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.
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.
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.
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.
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 X.509 with LDAP security mode:
4. Enter the required information in each of the fields:
Configuring iStrobe
71
Password for DN
Search base
Search filter
X.509 mask
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.
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 for LDAP or their smart
card PIN.
Disable security
Start iStrobe in your browser and click the Administration button. The Administration
window appears.
1. Click Security. The Security window appears.
2. Select the None radio button.
3. Click Apply.
You must restart your web application for the security settings to become effective. When
logging on, users are no longer prompted for their user ID and password, and all content
and profiles are available to all users.
72
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.
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.
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 name of the argument and the path are case sensitive.
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.
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
<!-- Copyright (c) 2010 Compuware Corporation. All rights reserved. -->
<AddActiveRequest xmlns="http://istrobe.compuware.com/ws/Measurement" >
<reqType>addActive</reqType> <!-- addQueue for Add Queued request -->
<logonid>mainframe-userid</logonid>
<password>mainframe-password</password><!-- sample java code will ask this value at runtime
->
<jobname>YOURJOB0</jobname>
<system>yourSystem</system>
<!-- Optional -->
<tags>list of tags</tags>
<profileName>profile name to be created</profileName>
<emailto>email-id to notify</emailto><!-- iStrobe should be configured to use email
notification -->
<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.
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>
<!-- below is the iStrobe reporter url when the returnCode is less than 5 -->
<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.
78
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.
79
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
<!-- Define a SSL HTTP/1.1 Connector on port 8443 -->
<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
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)
82
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.
5. Delete any additional files or folders that the uninstall did not delete.
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.
5. Delete any additional files or folders that the uninstall did not delete.
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