wsinstance problems for all releases and editions of
V5.0 and V5.1
If you have already contacted support, continue on to the
component-specific MustGather information. Otherwise, click: MustGather:
Read First for all WebSphere Application Server Products.
The wsinstance command creates multiple configuration instances of one
initial installation of the product.
Each WebSphere Application Server configuration instance is a stand-alone
instance with a unique name and its own set of configuration files and
user data folders. Configuration folders include config, etc and
properties. User data folders include installedApps, installableApps,
temp, logs, tranlog and wstemp. Each configuration instance also has the
administrative console application to manage the configuration instance.
Each configuration instance shares all run-time scripts, libraries, the
Software Development Kit, and other files with the initial Application
Server.
Collect the following information's, if the wsinstance fails to create or
delete the config instance.
- Enable tracing in wsadmin:
Modify the wsadmin.properties file located in the following directory:
install_root/bin/wsinstance/propdefaults
Uncomment the following line:
com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled
- Run the wsinstance with debug option as follows.
On windows :
wsinstance.bat -name instanceName -path instanceLocation -host hostName
-create|-delete -debug > captureFileName.txt
On Unix :
./wsinstance.sh -name instanceName -path instanceLocation -host hostName
-create|-delete -debug > captureFileName.txt 2>&1
- Copy the command prompt output of the wsinstance command
and paste the output of
the command to a text file and save it as wsinstanceoutput.txt.
For a listing of all technotes, downloads, and educational materials
specific to the componentName component, search the WebSphere
Application Server support site
|