When you encounter the problems with OSGi applications running in the IBM WebSphere Application Server such as the deployment issue. You may start to collect the following information to help you understand the problem and save time analyzing the data. The procedures below is based on IBM WAS v.8.5.
1. Backup and clear all Application Server logs.
The log files are located in the following directory:
Note: If you have configured to write Application Server log files into a different location, then clear that location accordingly.
2. Enable and collect Application Server traces with the following trace string:
3. Run the collector tool. On ND, run the collector tool on the DMGR node so that the configuration for the entire cell is collected. If you run it from a server node, only the configuration from the servers on that node is collected.
- Log on to the system as root or a member of the administrator group on a Windows platform.
- - Verify that Java is available in the path.
The collector program requires Java code to run. It also collects data about the IBM Developer Kit, Java Technology Edition in which it runs.If there are multiple Developer Kits on the system, verify that the one that the WebSphere Application Server product uses is the one in the path for the collector program. If the Developer Kit being used by the WebSphere Application Server is not available, put another Developer Kit in the path for the collector program so that you can collect everything except data about the Developer Kit that WebSphere Application Server Express is using.
- - Verify that all necessary information is in the path that is being used by the collector program and that you are not running the program from within the WebSphere Application Server product installation root directory.
- Verify that the path contains the following system directories:
- - Make a working directory where you can start the collector program.
- - Make the working directory the current directory.
- - Run the collector program by entering the fully qualified command from the command line of the working directory.
- Or use the command with no additional parameter to gather one copy of the profile data and data from each server in the node, and to store the data in a single JAR output file.
app_server_root/bin/collector.sh -profileName profile_name
4. Review the collector tool output
You can view the files contained in the JAR file without extracting the files from the JAR file. However, it is easier to extract all files and view the contents of each file individually. To extract the files, use one of the following commands:
- jar -xvf WASenv.jar
- unzip WASenv.jar
Wasenv.jar stands for the name of the JAR file that the collector tool creates.
The JAR file contains:
- A collector tool log file, collector.log
- Copies of stored WebSphere Application Server files and their full paths that are located under directory root in the JAR file
- Operating system information in a directory named OS
- Java information in a directory named Java
- WebSphere Application Server information in a directory named WAS
- Collector shell script (or batch file ) execution information in a directory named debug
- MQ information in a directory named MQ, if you installed WebSphere MQ or the embedded messaging feature
- A JAR file manifest