ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzamy_5.4.0.1/50/admin/qsh.htm

126 lines
8.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>Qshell scripts</title>
</head>
<BODY>
<!-- Java sync-link -->
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
<h3><a name="qsh"></a>Qshell scripts</h3>
<p>WebSphere Application Server - Express provides several scripts that you can use to administer your application server environment. These topics provide more information about the administrative Qshell scripts and how to run them.</p>
<blockquote>
<p><strong><a href="qshadm.htm">Configure Qshell to run WebSphere Application Server - Express scripts</a></strong>
<br>Most of the WebSphere Application Server - Express scripts are located in the /QIBM/ProdData/WebASE/ASE5/bin directory. This topic describes the different methods that you can use to invoke the Qshell scripts.</p>
<p><strong><a href="qshenvvar.htm">Qshell environment variables</a></strong>
<br>This topic describes how to set environment variables that affect Qshell scripts.</p>
<p><strong><a href="qshsecurity.htm">Security and Qshell scripts</a></strong>
<br>In a secured environment, you must provide authentication information for some scripts. This topic describes different ways to provide authentication information.</p>
<p><strong><a href="qshsetauth.htm">Set explicit authorities for the startServer and stopServer scripts</a></strong>
<br>You can grant explicit authorities so that user profiles that do not have *ALLOBJ authority can run the startServer and stopServer scripts. This topic provides information on granting the required authorities.</p>
</blockquote>
<p><strong>Note:</strong> Parameter values that specify a server name, a node name or a cell name are case sensitive. For example, if you want to start the application server myAppServer for the instance test, invoke startServer myAppServer -instance test. If you specify myappserver for the server name, the startServer script fails.</p>
<p>Instance names and iSeries host names are not case sensitive.</p>
<ul>
<li><a href="#server">Application server scripts</a></li>
<li><a href="#app">Application scripts</a></li>
<li><a href="#config">Configuration scripts</a></li>
<li><a href="#log">Logging and tracing scripts</a></li>
<li><a href="#svc">Serviceability tools</a></li>
<li><a href="#appdev">Application development scripts</a></li>
<li><a href="#ws">Web services scripts</a></li>
<li><a href="#sec">Security scripts</a></li>
</ul>
<p><strong><a name="server"></a>Application server scripts</strong></p>
<p>Use these scripts to manage instances of WebSphere Application Server - Express:</p>
<ul>
<li><a href="qshcrtplugininst.htm">The crtplugininst script</a> script creates an HTTP server instance on a machine that is not running WebSphere Application Server - Express. Your application server connects to this HTTP server to receive client requests.</li>
<li><a href="qshcrtinst.htm">The crtwasinst script</a> script creates a new instance of WebSphere Application Server - Express.</li>
<li><a href="qshdltinst.htm">The dltwasinst script</a> script deletes an instance of WebSphere Application Server - Express.</li>
<li><a href="qshdspinst.htm">The dspwasinst script</a> script displays information about an instance.</li>
<li><a href="qshstrsvr.htm">The startServer script</a> script starts an application server.</li>
<li><a href="qshstopsvr.htm">The stopServer script</a> script stops an application server.</li>
<li><a href="qshsvrstat.htm">The serverStatus script</a> script displays the status of an application server.</li>
<li><a href="qshchgsvr.htm">The chgwassvr script</a> script changes properties of an application server.</li>
<li><a href="qshgrtauth.htm">The grtwasaut script</a> grants users authority to an instance.</li>
<li><a href="qshrvkauth.htm">The rvkwasaut script</a> revokes a user's authority to an instance.</li>
</ul>
<p><strong><a name="app"></a>Application scripts</strong></p>
<p>Use this script to manage applications:</p>
<ul>
<li><a href="qshearexp.htm">The EARExpander script</a> script expands EAR files into a directory and collapses directories of application files into EAR files.</li>
</ul>
<p><strong><a name="config"></a>Configuration scripts</strong></p>
<p>Use these scripts to manage your server's configuration:</p>
<ul>
<li><a href="qshbkupcfg.htm">The backupConfig script</a> script backs up the configuration of a node into a ZIP file.</li>
<li><a href="qshrestcfg.htm">The restoreConfig script</a> script restores a configuration of a node.</li>
<li><a href="qshgenplgcfg.htm">The GenPluginCfg script</a> script regenerates the configuration file for the HTTP server plugin.</li>
</ul>
<p><strong><a name="log"></a>Logging and tracing scripts</strong></p>
<p>These scripts provide logging and tracing information:</p>
<ul>
<li><a href="qshgenver.htm">Product version report scripts</a> generate version reports on the WebSphere Application Server - Express product.</li>
<li><a href="qshgenhist.htm">Product history report scripts</a> generate history reports of the WebSphere Application Server - Express product.</li>
<li><a href="../trb/qshcollect.htm">The collector script</a> script gathers information about your WebSphere Application Server - Express installation and packages it in a JAR file.</li>
<li><a href="../trb/qshshowlog.htm">The showlog script</a> script displays the contents of the IBM Service log for your WebSphere Application Server - Express installation.</li>
</ul>
<p><strong><a name="svc"></a>Serviceability tools</strong></p>
<ul>
<li><a href="../trb/qshchkprq.htm">The checkprereqs script</a> invokes the prerequisite validator.</li>
<li><a href="../trb/qshsvctools.htm">The servicetools script</a> invokes serviceability tools that you can use to help troubleshoot WebSphere Application Server - Express.</li>
<li><a href="../trb/qshportval.htm">The port validator</a> verifies your WebSphere Application Server - Express configuration to ensure that you do not have port conflicts between WebSphere Application Server - Express instances and products.</li>
<li><a href="../trb/qshprereq.htm">The prerequisite validator</a> verifies your WebSphere Application Server installation and determines whether or not the prerequisite software is installed.</li>
</ul>
<p><strong><a name="appdev"></a>Application development scripts</strong></p>
<p>You can use these scripts when you develop applications:</p>
<ul>
<li><a href="../program/jndinsdu.htm">The dumpNameSpace script</a> dumps the contents of the name space accessed through a name server.</li>
<li><a href="../program/jspbatch.htm">The JspBatchCompiler script</a> compiles JSP files as a batch.</li>
</ul>
<p><strong><a name="ws"></a>Web services scripts</strong></p>
<ul>
<li><a href="../webserv/qshjava2wsdl.htm">The Java2WSDL script</a></li> uses the Java API for XML-based remote procedure call (JAX-RPC) specification to map a Java class to a Web Services Description Language (WSDL) file.
<li><a href="../webserv/qshsetwsclt.htm">The setupWebServiceClientEnv script</a> sets up a Java environment for Web Services J2SE clients to use and sets the classpath variable for Web Services clients.</li>
<li><a href="../webserv/qshwsdeploy.htm">The wsdeploy script</a> adds Websphere Application Server - Express product-specific Web services deployment classes to a Web services enterprise archive (EAR) file or an application client Java archive (JAR) file.</li>
<li><a href="../webserv/qshwsdl2java.htm">The WSDL2Java script</a> uses the Java API for XML-based remote procedure call (JAX-RPC) specification to create Java classes and deployment descriptor templates from a Web Services Description Language (WSDL) file.</li>
</ul>
<p><strong><a name="sec"></a>Security scripts</strong></p>
<ul>
<li><a href="qshpropenc.htm">The PropFilePasswordEncoder script</a> encodes passwords in a properties file.</li>
<li><a href="qshencdata.htm">The EncAuthDataFile script</a> generates a text file that contains user IDs and passwords for a client that does not pass a user ID and password on a getConnection call.</li>
</ul>
</body>
</html>