Qshell scripts

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.

Configure Qshell to run WebSphere Application Server - Express scripts
Most of the WebSphere Application Server - Express scripts are located in the /QIBM/ProdData/WebASE51/ASE/bin directory. This topic describes the different methods that you can use to invoke the Qshell scripts.

Qshell environment variables
This topic describes how to set environment variables that affect Qshell scripts.

Security and Qshell scripts
In a secured environment, you must provide authentication information for some scripts. This topic describes different ways to provide authentication information.

Set explicit authorities for the startServer and stopServer scripts
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.

Note: 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.

Instance names and iSeries host names are not case sensitive.

• Application server scripts
• Application scripts
• Configuration scripts
• Logging and tracing scripts
• Serviceability tools
• Application development scripts
• Web services scripts
• Security scripts

Application server scripts

Use these scripts to manage instances of WebSphere Application Server - Express:

• The crtplugininst 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.
• The crtwasinst script creates a new instance of WebSphere Application Server - Express.
• The dltwasinst script deletes an instance of WebSphere Application Server - Express.
• The dspwasinst script displays information about an instance.
• The startServer script starts an application server.
• The stopServer script stops an application server.
• The serverStatus script displays the status of an application server.
• The chgwassvr script changes properties of an application server.
• The grtwasaut script grants users authority to an instance.
• The rvkwasaut script revokes a user's authority to an instance.
• The enbprfwas script enables a profile to run an application server instance.
• The lstwasinst script displays a list of instances based on specified parameters.
• The updwashost script updates an instance if the host name of the server is changed.
• The enableAdmin script enables the administrative console application for an application server.

Application scripts

Use this script to manage applications:

• The EARExpander script expands EAR files into a directory and collapses directories of application files into EAR files.

Configuration scripts

Use these scripts to manage your server's configuration:

• The backupConfig script backs up the configuration of a node into a ZIP file.
• The restoreConfig script restores a configuration of a node.
• The GenPluginCfg script regenerates the configuration file for the HTTP server plugin.

Logging and tracing scripts

These scripts provide logging and tracing information:

• Product version report scripts generate version reports on the WebSphere Application Server - Express product.
• Product history report scripts generate history reports of the WebSphere Application Server - Express product.
• The collector script gathers information about your WebSphere Application Server - Express installation and packages it in a JAR file.
• The showlog script displays the contents of the IBM Service log for your WebSphere Application Server - Express installation.

Serviceability tools

• The checkprereqs script invokes the prerequisite validator.
• The servicetools script invokes serviceability tools that you can use to help troubleshoot WebSphere Application Server - Express.
• The port validator verifies your WebSphere Application Server - Express configuration to ensure that you do not have port conflicts between WebSphere Application Server - Express instances and products.
• The prerequisite validator verifies your WebSphere Application Server installation and determines whether or not the prerequisite software is installed.

Application development scripts

You can use these scripts when you develop applications:

• The dumpNameSpace script dumps the contents of the name space accessed through a name server.
• The JspBatchCompiler script compiles JSP files as a batch.

Web services scripts

• The Java2WSDL script 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.
• The setupWebServiceClientEnv script sets up a Java environment for Web Services J2SE clients to use and sets the classpath variable for Web Services clients.
• The wsdeploy script 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.
• The WSDL2Java script 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.

Security scripts

• The PropFilePasswordEncoder script encodes passwords in a properties file.
• The EncAuthDataFile script 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.