|
Problem(Abstract) |
When using the WebSphere® Test Environment that ships with
the WebSphere Studio tooling, it can be difficult to locate logs and trace
files. This technote will help you find these files. It will also help you
locate files that must be customized to run the .bat files that ship as
part of the WebSphere test environment V5 Application Server. |
|
|
|
Resolving the
problem |
Locating log and trace files
When using the WebSphere test environment that is built into development
tools such as WebSphere Studio, it is useful to look at the logs and trace
files produced for a particular application server. However, it is not
obvious from the online help where these files are found.
The default log directory is ${LOG_ROOT}/serverName
The diagnostic trace file is ${SERVER_LOG_ROOT}/trace.log
However, SERVER_LOG_ROOT does not appear under the WebSphere environment
variables. Apparently, it is created automatically when a server is
defined with a value equal to ${LOG_ROOT}/serverName. LOG_ROOT is defined
as an environment variable equal to ${SERVER_TEMP_DIR_PATH_MAP}/logs, but
it is unclear how this value is set.
To see values constructed by WebSphere Studio for use as environment
variables for a WebSphere test environment server, see:
workspace\.metadata\.plugins\com.ibm.etools.server.core\<tmpN>\pathmap.properties
where:
- workspace is the location of the WebSphere Studio
workspace (for example: C:\Program Files\IBM\WebSphere
Studio\workspace)
- <tmpN> is a directory for each WebSphere test
environment that is defined to your workspace. For example, tmp0, tmp1 and
so on. To see which tmpN directory corresponds to each WebSphere technical
environment, see the temp-data.xml file in the com.ibm.etools.server.core
directory.
By default, SystemOut and SystemErr messages are written to the console,
but WebSphere test environment server activity, ffdc logs, and trace files
are written to:
workspace\.metadata\.plugins\com.ibm.etools.server.core\logs\<tmpN>\<serverName>\
You can locate the WebSphere Application Server XML configuration files
(for example, variables.xml and resources.xml) in the
workspace\Servers\<Name>.wsc\cells\ directory:
Running WebSphere Application Server .bat files
WebSphere Application Server ships with .bat files to perform various
functions in the WebSphere\AppServer\bin directory. The equivalent
directory in WebSphere Studio is the
<WSAD_install_dir>\runtimes\<server version>\bin.
The .bat files all call the setupCmdLine.bat file to set up the
environment. However, a number of these variables are set to the
installation path of the WebSphere Application Server product, which does
not exist if only WebSphere Studio is installed. To resolve this problem,
follow the instructions in the setupCmdLine.bat file (copied here for
convenience):
"REM To override the previous values, create your own batch file to
override the values and then"
"REM set the WAS_USER_SCRIPT environment variable to point to your batch
file"
Running dumpNameSpace.bat
In addition to customizing the setupCmdLine.bat file, you must also edit
the following file:
<WSAD_install_dir>\runtimes\<server
verson>\properties\sas.client.props
to correct the values specified for the following variables to match the
WebSphere Studio installation path:
com.ibm.ssl.keystore=
com.ibm.ssl.truststore= |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Software Development |
WebSphere Studio Application Developer |
Not Applicable |
Windows |
5.0 |
|
Software Development |
WebSphere Studio Site Developer |
Not Applicable |
Windows |
5.0 |
|
Business Integration |
WebSphere Studio Application Developer Integration Edition |
General |
Windows |
5.0 |
Edition Independent |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|