IBM WebSphere V5.0 Security - CGISecurity

3. In the line com.ibm.SOAP.loginUserid= write your security server user ID (the
same that you entered while configuring Global Security). If you are using
LDAP distinguished names, do not put names in quotes, just type them as
they are defined in the LDAP server. For our test, we have used LDAP user
cn=wasadmin,o=itso.
4. In the line com.ibm.SOAP.loginPassword= enter the password for that user.
5. Save the file and run wsadmin client without any parameters. You should get
output similar to that shown below.
Example: D-1 Example output after successful connection from wsadmin client
C:\>wsadmin
WASX7209I: Connected to process "server1" on node mka0klfc using SOAP
connector;
The type of process is: UnManagedProcess
WASX7029I: For help, enter: "$Help help"
wsadmin>
Now you are ready to start writing scripts.
Sample scripts
This section lists some useful scripts to make the configuration more convenient
for WebSphere.
Each script will show and teach something new with the scripting language, and
at the end you will learn how to create your own scripts based on these.
Remember that you can always refer to the InfoCenter for scripting references
and more scripting samples.
Setting global security
The following script can enable or disable global security for the application
server, depending on the parameter value passed to the interpreter. For more
information on this script, check the comments in the source below.
Example: D-2 globalsecurity.jacl
# global security
# usage: wsadmin globalsecurity.jacl [enable | disable]
# store the pointer to the security object
set security_item [$AdminConfig list Security]
# store the parameter from the command line
set argv0 [lindex $argv 0]
516 IBM WebSphere V5.0 Security Handbook