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 ina command line to create a custom environment for wsadmin execution. Theseprocedures can then be used as normal JACL commands. For more informationabout how to create profiles, please refer to the WebSphere Application Serverinfo center.Preparing and testing the wsadmin clientThe wsadmin scripting tool can run with a command prompt where the user canfeed the commands to the interpreter and execute them from a console; orwsadmin can run in silent mode where users can pass a script file as aparameter 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 thewsadmin tool or you can start wsadmin as a command line interpreter and runthe commands line by line from the scripts.Since the wsadmin tool is basically a Java application accessing the WebSphereApplication Server, when global security is enabled, the application has toprovide 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 modifyingthe sas.client.props file.Running the script with command line parametersIssue the wsadmin command with the following parameters:►►-username -password For example:wsadmin -username cn=wasadmin,o=itso -password password myscript.jaclEditing the sas.client.props fileFollow these steps to provide the user name and password in the properties filefor 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 SOAPconnector identity.Appendix D. Using wsadmin scripting for security configuration 515