|
Problem(Abstract) |
The IBM® WebSphere® Application Server for z/OS® Portable
Collector is included in the IBM Support Assistant version 3 Fix Pack 1
(ISA V3.01) to assist with the data collection activities for WebSphere
Application Server versions 5.0, 5.1, 6.0, and 6.1 on the z/OS operating
system. Navigate to the data collector embeddeed in the IBM Support
Assistant by selecting Services and then clicking the
Collect link of the tool. |
|
|
|
Resolving the
problem |
Background
Install IBM Support Assistant:
Start by installing IBM Support
Assistant version 3 Fix Pack 1 (ISA V3.01)
Information collected by the WebSphere Application Server for z/OS
Portable Collector:
The output of the data collection is a Java™ Archive file (JAR file)
containing:
- The system information gathered from running the following
commands:
- netstat -anps -ef
- java -fullversion
- uname -a
- df
- The configuration files located in the WebSphere
Application Server config directory EXCLUDING security
information such as that found in the security.xml file and in
key store files.
- Any job logs that are available
- Any WebSphere Application Server log files
Resources required during a data collection:
Running the collector is equivalent to running the commands listed in
section A, item 1 and a Java Archive (JAR) command.
Performing a data collection
The WebSphere Application Server for z/OS Portable Collector is run
under the UNIX® System Services (USS) sub system using the FTP and Telnet
protocols.
- FTP the zPortableCollector.jar file to the remote z/OS USS sub-system
- ftp z/OS_host_name
- $ login: user_name
- $ password: password
- $ bin
- $ cd /tmp
- $ ftp zPortableCollector.jar
- Telnet to the remote system and deploy the WebSphere Application
Server for z/OS Portable Collector:
- telnet z/OS_host_name
- $ login: user_name
- $ password:
- cd /tmp
- mkdir collector
- mv zPortableCollector.jar collector
- cd collector
- jar xvf zPortableCollector.jar
- chmod 755 *
- ./zcollector.sh
The WebSphere for z/OS data collector is capable of collecting one
deployment manager and one node in a single session. The naming convention
used by the WebSphere for z/OS data collector keeps the naming unique
between a node and deployment manager, only. If multiple nodes or
deployment managers need to be collected, then;
- Rename the collected jar files to some unique name
example: WASHOST-BASE-WASenv.jar ->
WASHOST_1-BASE-WASenv.jar
- Perform another collection by entering the command
./zcollector.sh at the command prompt as in
step 2 j, above.
Note: By renaming the collected jars, they will not be overwritten by
subsequent collections.
- type "exit" and press Enter to end the Telnet
session
- Use FTP to retrieve all of the collected information from the z/OS
system
Steps (if the session from 1 is still active, jump to step f.):
- ftp z/OS_host_name
- $ login: user_name
- $ password: password
- $ bin
- $ cd /tmp
- cd collector
- get
<xxxx>,<bbb>,<ccc>.<yyy>.<yyy>.jar
The actual file name is the name you during the IBM Support Assistant
activity to configure the collection.
- Type "y" and press Enter for each collected file
- Type "bye" and press Enter to end the FTP session
- Transfer the collected file to IBM support ECuRep server
This section is an excerpt from the technote Submitting
diagnostic information to IBM Technical Support for problem
determination
|
|
|
|