Troubleshooting WebSphere Studio for Application Developer

This section describes problems you may encounter when launching WebSphere Studio for Application Developer (WSAD). The following problems are addressed:

WSAD will not open

Problem

WSAD will not open.

Solution

One of the initialization of plugins may have failed in a critical way. To verify, look at the log file in <your WSAS workspace>/.metadata/log.

Note:
The WSAD workspace is typically located at <your WSAD install directory>/workspace unless overridded by one of the command line arguments.
If the log file does not indicate any problem, you can launch WSAD with the following command line option:

-consoleLog

Note 1:
The second "L" in "consoleLog" must be capitalized.
Note 2:
You can supply the command line by editing the shortcut that launches WSAD. This will bring up a console window from which you can watch the initialization process.
Note 3:
WSAD is a large application and may take several minutes to launch.

Cannot locate System Manager perspective from WSAD

Problem

WSAD opens, but the System Manager perspective cannot be found.

Solution

The System Manager plugin is probably not loaded properly, or one or more of the components it needs is missing. The following steps describe how to fix this problem:

  1. Make sure you have unzipped all of the plugins from the WebSphereBI\plugins directory.
  2. Look at the WSAD log file, as explained in the "WSAD will not open" section.

How to change WSAD workspace directory

Problem

The WSAD workspace directory needs to be changed.

Solution

Change the following text in the startcsm.bat file:

-data your_workspace_location

Example: -data C:\myworkspace

Copyright IBM Corp. 1997, 2004