|
Problem |
Follow these steps to change the node name after
installation of any release of WebSphere® Application Server V4.0. |
|
Solution |
During installation of V4.0 releases, the host machine
name is determined and used as the node name. If you want to change the
node name after installation, follow these steps.
- Perform an XML Export of the current configuration from the command
line. This serves as a backup of your repository.
xmlconfig -export filename.xml -adminNodeName nodename
- Stop WebSphere® Application Server Services.
- Create a new WebSphere Application Server repository.
- Edit the admin.config file in the $WAS_HOME\bin directory to include
the following changes:
Install.initial.config=true
com.ibm.ejs.sm.adminServer.initializeDb=true
com.ibm.ejs.sm.adminServer.createTables=true
com.ibm.ejs.sm.adminServer.nodeName=<new_node_name>
If you do not want the new repository to contain the default
configuration, such as the Default Application, then leave the
install.initial configuration set to false as follows:
install.initial.config=false
By setting "initializeDb=true" the adminserver process creates
all required database tables and exit.
- Save the changes to the admin.config file.
- Is WebSphere security turned on? If so then from the
$WAS_HOME\properties directory edit the sas.server.props file to include
the new node name:
com.ibm.CORBA.principalName=<new_node_name>/
- Save the changes to the sas.server.props file.
- Start the WebSphere Application Server services (adminserver).
- From the $WAS_HOME\logs directory, check the tracefile for
"Server__adminServer open for e-business" to ensure that the
Administrative Server has started.
- In the WebSphere Application repository check the NODE_TABLE for the
new node name.
- The admin.config file should now reflect the following:
install.initial.config=false
com.ibm.ejs.sm.adminServer.initializeDb=false
com.ibm.ejs.sm.adminServer.createTables=false
com.ibm.ejs.sm.adminServer.nodeName=<new_node_name>
If the three lines didn't change from true to false, you can manually edit
them to match the above and save the file.
- Start the WebSphere Application Server services (adminserver).
- Edit your XML Export file created in step 1 and change all references
to the old node name.
- From a command line, import the XMLConfig (step 1 above).
xmlconfig -import filename.xml -adminNodeName newnodename
- Start the Administrative Console. The new node name is now listed in
the topology.
|
|
|
|
|
|
|