|
Problem |
WebSphere Application Server will not start. |
|
Cause |
In WebSphere® Application Server 4.0, you create a new
repository, then use the XMLConfig -import command to populate the
repository. The XMLConfig file has a node name in a different case than
the hostname, such as host1 versus Host1.
After creating the new repository and running XMLConfig -import there are
two nodes, host1 and Host1, with the same name, but
different case. |
|
Solution |
Since this problem typically occurs when using XMLConfig
to repopulate a new repository from an existing XMLConfig file (created
from an XMLConfig -export prior to dropping the original
repository), you can use the following process to recreate the
configuration with only one node name:
- Drop and recreate repository .
- Start WebSphere Application Server.
- Compare node name in WebSphere (using the WebSphere Application Server
Administrative Console) with contents of the XMLConfig file that will be
used for import.
- Change the node name to match the case listed in the Administrative
Console.
- Use XMLConfig -import to repopulate repository.
A more comprehensive recovery process is documented in the technote:
How
to prevent/recover from corrupted repository - WebSphere:
http://www.ibm.com/support/docview.wss?rs=180&context=SSEQTP&uid=swg21052797
Hints and Tips
- DB2® commands used to create a repository are listed in
the createdb2.scr file in WebSphere's bin directory.
- When recreating a repository, you must create tables: Edit
admin.config to set these lines as follows:
line.com.ibm.ejs.sm.adminServer.initializeDb=true
com.ibm.ejs.sm.adminServer.createTables=true
- Do not recreate the default server automatically because
it must be part of the XMLConfig file you are importing: Edit admin.config
to set install.initial.config=false.
- For more details on modifying the node name, see technote:
WASWLM:
WebSphere 4.0.x: How to change the Node Name:
http://www.ibm.com/support/docview.wss?rs=180&context=SSEQTP&uid=swg21052549
|
|
|
|
|
|
|