Security and Qshell scripts

If security is enabled for your application server, provide authentication information to the scripts. If security is enabled and you do not provide authentication information, the scripts receive an AccessDenied exception. You can provide authentication data in any of these ways:

• Most command line tools support a -username and -password option for providing basic authentication data. The userid and password that you specify should be an administrative user. For example, you can use a member of the administrative console users with operator or administrator privileges, or the administrative userid configured in the user registry. This example demonstrates the stopNode script which specifies command line parameters:

  stopNode -username adminuser -password adminpw

• You can place the authentication data in a properties file that the command line tools read.

  • If you use the SOAP connector, the default file for this data is the soap.client.props.
  • If you use the RMI connector, use the sas.client.props file.

  The script uses the properties files in this directory:

  • WebSphere Application Server: /QIBM/UserData/WebAS5/Base/instance/properties
  • WebSphere Application Server Network Deployment: /QIBM/UserData/WebAS5/ND/instance/properties

  where instance is the instance name specified by the -instance parameter for the command, or default if you do not specify the -instance parameter.