InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.0: About user assistance >
6.6.0.2: Command line administration >
6.6.0.2.1: XMLConfig command line interface for XML configuration >
6.6.0.2.1.5: Troubleshooting XMLConfig
6.6.0.2.1.5: Troubleshooting XMLConfig
This article describes what to do if XMLConfig fails and displays the
following message at its command line.
Unable to create Initial Context. Please check name service settings:
org.omg.CORBA.COMM_FAILURE: minor code: 3 completed: No
java com.ibm.websphere.xmlconfig.XMLConfig
{ ( -import <xml data file> ) ||
[ ( -export <xml output file> [-partial <xml data file>] ) }
-adminNodeName <primary node name>
[ -nameServiceHost <host name> [ -nameServicePort <port number> ]]
[-traceString <trace spec> [-traceFile <file name>]]
[-substitute <"key1=value1[;key2=value2[...]]">]}
In input xml file, the key(s) should appear as $key$ for substitution.
One or more of the following conditions is likely to have caused the problem:
To resolve the problem:
- Check whether the administrative server started successfully, as described
in the documentation for starting the administrative server.
- If the XMLConfig tool is being run remotely with respect to the machine on which
the IBM Websphere administrative server is running, ensure that the
-nameServiceHost (as well as the -adminNodeName) parameter are set to the
host name of the remote machine.
- If the naming service port has been changed from the default 900 on the machine
on which the administrative server is running, look in the
administrative server configuration file for the parameter:
com.ibm.ejs.sm.adminServer.bootstrapPort
Set the XMLConfig -nameServicePort parameter to this port value.
- If you use the -nameServicePort parameter, you must also use the
-nameServiceHost parameter even if you are running XMLConfig on the same machine as
the administrative server.
- Modify the -adminNodeName parameter to use the node name, which
can be found as your hostname in your TCP/IP networking configuration
and also in the Websphere administrative console under
"Websphere Administrative Domain."
|
|