153 lines
7.1 KiB
HTML
153 lines
7.1 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<html>
|
|
<head>
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
|
|
|
<title>Namespace dump utility</title>
|
|
</head>
|
|
|
|
<BODY>
|
|
<!-- Java sync-link -->
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
|
|
|
<h6><a name="jndinsdu"></a>Namespace dump utility</h6>
|
|
|
|
<p>The namespace stored by a given name server can be dumped with the name space dump utility that is shipped with WebSphere Application Server - Express. You can invoke this utility from the command line or from a Java program. The naming service for the WebSphere Application Server - Express host must be active when this utility is invoked.</p>
|
|
|
|
<p>You can invoke the namespace dump utility in these ways:</p>
|
|
|
|
<p>
|
|
<ul>
|
|
<li>Invoke the name space dump utility by adding the following code to your Java program:
|
|
<pre>
|
|
import com.ibm.websphere.naming.DumpNameSpace;
|
|
java.io.PrintStream filePrintStream = ...
|
|
Context ctx = new InitialContext();
|
|
Context ctx = (Context) ctx.lookup("<em><starting_context></em>");
|
|
// Starting context for dump
|
|
DumpNameSpace dumpUtil = new DumpNameSpace(filePrintStream, DumpNameSpace.LONG);
|
|
dumpUtil.generateReport(ctx);
|
|
</pre>
|
|
|
|
<p>where <em><starting_context></em> is the starting context for the dump.</p>
|
|
|
|
<p>For more information, see <a href="jndiimpl.htm">JNDI implementation</a> for the API documentation.</p>
|
|
|
|
</li>
|
|
<li>Invoke the namespace dump utility on your iSeries server:
|
|
<p>
|
|
<ul>
|
|
<li>Enter the Start Qshell (STRQSH) command on an CL command line.</li>
|
|
<li>At the Qshell command prompt, enter the following command:
|
|
<pre>cd /QIBM/ProdData/WebASE/ASE5/bin
|
|
</pre>
|
|
</li>
|
|
<li>Run the dumpNameSpace script. The syntax is as follows:
|
|
<pre>dumpNameSpace -host myhost.mycompany.com -port <em><port_number></em>
|
|
</pre>
|
|
<p>where <em><port_number></em> is the name service port which, if not specified, defaults to 2809. In this case, assume that the port number is 2809.</p>
|
|
</li>
|
|
</ul>
|
|
</p>
|
|
</li>
|
|
</ul>
|
|
</p>
|
|
|
|
<p>The keywords and associated values for the dumpNameSpace utility are:</p>
|
|
<table border="1" title="Keywords and associated values for the dumpNameSpace utility" width="680">
|
|
<tr>
|
|
<th width="73" align="left" valign="top"><strong>Keyword</strong></th>
|
|
<th width="307" align="left" valign="top"><strong>Values</strong></th>
|
|
<th width="300" align="left" valign="top"><strong>Description</strong></th>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td width="73" align="left" valign="top">-host</td>
|
|
<td width="307" align="left" valign="top">Example: <em>myhost.myserver.mycompany.com</em></td>
|
|
<td width="300" align="left" valign="top">Represents the bootstrap host or the WebSphere Application Server - Express host whose name space you want to dump. The value defaults to <tt>localhost</tt>.</td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td width="73" align="left" valign="top">-port</td>
|
|
<td width="307" align="left" valign="top">Example: <em>nnn</em></td>
|
|
<td width="300" align="left" valign="top">Represents the bootstrap port which, if not specified, defaults to <tt>2809</tt>.</td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td width="73" align="left" valign="top">-factory</td>
|
|
<td width="307" align="left" valign="top">Example: <em>com.ibm.websphere.naming.
|
|
<br>WsnInitialContextFactory</em></td>
|
|
<td width="300" align="left" valign="top">Indicates the initial context factory to be used to get the JNDI initial context. The value defaults to com.ibm.websphere.naming.
|
|
<br>WsnInitialContextFactory. You typically do not need to change the default value.</td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td width="73" align="left" valign="top">-root</td>
|
|
<td width="307" align="left" valign="top"><p>cell</p><br>
|
|
<p>server</p>
|
|
<p>node</p>
|
|
<p>legacy</p><br>
|
|
<p>host</p><br><br>
|
|
<p>tree</p><br><br>
|
|
<p>default</p></td>
|
|
<td width="300" align="left" valign="top">
|
|
<ul>
|
|
<li>The cell option dumps the tree starting at the cell root context and is the default value.</li>
|
|
<li>The server option dumps the tree starting at the server root context.</li>
|
|
<li>The node option dumps the tree starting at the node root context.</li>
|
|
<li>In earlier versions of WebSphere Application Server, the legacy option dumps the tree starting at the legacy root context and is the default value.</li>
|
|
<li>In earlier versions of WebSphere Application Server, the host option dumps the tree starting at the bootstrap host root context.</li>
|
|
<li>In earlier versions of WebSphere Application Server, the tree option dumps the tree starting at the tree root context.</li>
|
|
<li>The default option dumps the tree starting at the initial context that JNDI returns by default for that server type.</li>
|
|
</ul>
|
|
</td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td width="73" align="left" valign="top">-url</td>
|
|
<td width="307" align="left" valign="top">Example: some_url</td>
|
|
<td width="300" align="left" valign="top">Represents the value for the java.naming.provider.url property, which is used to get the initial JNDI context.</td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td width="73" align="left" valign="top">-startAt</td>
|
|
<td width="307" align="left" valign="top">Example: <em>some/subcontext/in/the/tree</em></td>
|
|
<td width="300" align="left" valign="top">Indicates the path from the bootstrap host's root context to the top level context where the dump should begin. The utility recursively dumps subcontexts below this point. It defaults to an empty string, which represents context of the bootstrap host root.</td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td width="73" align="left" valign="top">-format</td>
|
|
<td width="307" align="left" valign="top"><p>jndi</p>
|
|
<p>ins</p></td>
|
|
<td width="300" align="left" valign="top"><p>Displays name components as atomic strings. (Note: This is the default value.)</p>
|
|
<p>Displays name components parsed per INS rules (id.kind).</p></td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td width="73" align="left" valign="top">-report</td>
|
|
<td width="307" align="left" valign="top"><p>short</p><br>
|
|
<p>long</p></td>
|
|
<td width="300" align="left" valign="top"><p>Dumps the binding name and bound object type. This output is also provided by JNDI Context.list(). (Note: This is the default value.)</p>
|
|
<p>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).</p></td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td width="73" align="left" valign="top">-traceString</td>
|
|
<td width="307" align="left" valign="top">Example: "<em>some.package.name.to.trace.*=all=enabled</em>"</td>
|
|
<td width="300" align="left" valign="top">Represents the trace string with the same format as that generated by the servers. The output is sent to the file DumpNameSpaceTrace.out in the current working directory.</td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td width="73" align="left" valign="top">-help</td>
|
|
<td width="307" align="left" valign="top"> </td>
|
|
<td width="300" align="left" valign="top">Provides a description of Name Space Dump utility and command line usage.</td>
|
|
</tr>
|
|
</table>
|
|
|
|
<p>See <a href="jndinsdx.htm">Example: Output from the namespace dump utility</a> for sample output.</p>
|
|
|
|
|
|
</body>
|
|
</html>
|