You can use the dumpNameSpace tool to dump the contents of a name space accessed through a name server. The dumpNameSpace tool is based on Java Naming and Directory Interface (JNDI).
When you run the dumpNameSpace tool, the naming service must be active. The dumpNameSpace tool cannot dump name spaces local to the server process, such as those with java: and local: URL schemes. The local: name space contains references to enterprise beans with local interfaces. Use the name space dump utility for java:, local: and server name spaces to dump java: and local: name spaces.
The tool dumps the server root context for the server at the specified host and port unless you specify a non-default starting context which precludes it. The tool does not dump the server root contexts for other servers.
Running dumpNameSpace
You can run the tool from a command line or using its program interface. This article describes command-line invocations. To access the dumpNameSpace tool through its program interface, refer to the class com.ibm.websphere.naming.DumpNameSpace in the WebSphere Application Server API documentation. Example: Invoking the name space dump tool illustrates running the tool from a command line or using its program interface.
To run the tool from a command line, enter the following command from the WebSphere/AppServer/bin directory:
Platform | Command |
---|---|
UNIX | dumpNameSpace.sh [[-keyword value]...] |
Windows NT or later | dumpNameSpace [[-keyword value]...] |
If you run the dumpNameSpace tool with security enabled, a login prompt is displayed. If you cancel the login prompt, the dumpNameSpace tool continues outbound with an "UNAUTHENTICATED" credential. Thus, by default, an "UNAUTHENTICATED" credential is used that is equivalent to the "Everyone" access authorization policy. You can modify this default setting by changing the value for the com.ibm.CSI.performClientAuthenticationRequired property to true in the install_dir/properties/sas.client.props file. If you change this property to true, rerun the dumpNameSpace tool and cancel the login prompt; the authorization fails and the command does not continue outbound.
Parameters
The keywords and associated values for the dumpNameSpace tool follow:
myhost.company.com
dumpNameSpace -host myhost.mycompany.comto display the name space of the server running on myhost.mycompany.com.
nnn
{ cell | server | node | host | legacy | tree | default }
cell | DumpNameSpace default. Dumps the tree starting at the cell root context. |
server | Dumps the tree starting at the server root context. |
node | Dumps the tree starting at the node root context. The node value is synonymous with host. |
For WebSphere Application Servers Version 4.0 or later:
legacy | DumpNameSpace default. Dumps the tree starting at the legacy root context. |
host | Dumps the tree starting at the bootstrap host root context. The host value is synonymous with node. |
tree | Dumps the tree starting at the tree root context. |
For all WebSphere Application Servers and other name servers:
default | Dumps the tree starting at the initial context which JNDI returns by default for that server type. This is the only -root choice that is compatible with WebSphere Application Servers prior to Version 4.0 and with non-WebSphere Application Server name servers. |
some_provider_URL
com.ibm.websphere.naming.WsnInitialContextFactory
some/subcontext/in/the/tree
{ jndi | ins }
jndi | The default. Displays name components as atomic strings. |
ins | Shows name components parsed using Interoperable Naming Service (INS) rules (id.kind). |
{ short | long }
short | The default. Dumps the binding name and bound object type. This output is also provided by JNDI Context.list(). |
long | Dumps the binding name, bound object type, local object type, and string representation of the local object (that is, the IORs, string values,
and other values that are printed).
For objects of user-defined classes to display correctly with the long report option, you might need to add their containing directories to the list of directories searched. Set the environment variable WAS_USER_DIRS as shown in the following platform-specific commands. The value can include one or more directories.
All .zip, .jar, and .class files in the specified directories can then be resolved by the class loader when running the dumpNameSpace tool. |
"some.package.name.to.trace.*=all=enabled"
Related tasks
Troubleshooting name space problems
Related reference
Example: Invoking the name space dump tool
Name space dump utility for java:, local: and server name spaces
Example: Invoking the name space dump utility for java: and local: name spaces
Name space dump sample output