IBM WebSphere V5.0 Security - CGISecurity

The JACL language that is used in scripts allows you to create procedures.
Procedures may be grouped into a profile files that can be passed to wsadmin in
a command line to create a custom environment for wsadmin execution. These
procedures can then be used as normal JACL commands. For more information
about how to create profiles, please refer to the WebSphere Application Server
info center.
Preparing and testing the wsadmin client
The wsadmin scripting tool can run with a command prompt where the user can
feed the commands to the interpreter and execute them from a console; or
wsadmin can run in silent mode where users can pass a script file as a
parameter to the tool and execute a whole sequence of commands.
The scripts provided below can be saved in files and you can feed then to the
wsadmin tool or you can start wsadmin as a command line interpreter and run
the commands line by line from the scripts.
Since the wsadmin tool is basically a Java application accessing the WebSphere
Application Server, when global security is enabled, the application has to
provide the right user name and password to be able to run the scripts.
You can pass the username and password in the command line or by modifying
the sas.client.props file.
Running the script with command line parameters
Issue the wsadmin command with the following parameters:
►
►
-username
-password
For example:
wsadmin -username cn=wasadmin,o=itso -password password myscript.jacl
Editing the sas.client.props file
Follow these steps to provide the user name and password in the properties file
for the client.
1. Open the sas.client.props file in your text file editor. The file is located in the
/properties directory.
2. Go to the section Authentication Configuration and find the # JMX SOAP
connector identity.
Appendix D. Using wsadmin scripting for security configuration 515