A profile script is a script that runs before the main
script, or before entering interactive mode. You can use profile scripts
to set up a scripting environment that is customized for the user
or the installation.
By default, the following profile script
files might be configured for the
com.ibm.ws.scripting.profiles profiles
property in the
app_server_root/properties/wsadmin.properties file:
app_server_root/bin/securityProcs.jacl
app_server_root/bin/LTPA_LDAPSecurityProcs.jacl
By default, these files are in ASCII. If
you use the profile.encoding option to run EBCDIC encoded
profile script files, change the encoding of the files to EBCDIC.
To
run scripting commands in a profile script, run the wsadmin tool with
the -profile option, and include the commands that you want to run
into the profile script.
To customize the script environment,
specify one or more profile scripts to run.
Do not use parenthesis
in node names when creating profiles.
The following examples
run profile scripts:
where the
alprof.py file contains the following commands:
apps = AdminApp.list()
print "Applications currently installed:\n " + apps
where the
alprof.jacl file contains the following commands:
set apps [$AdminApp list]
puts "Applications currently installed:\n$apps"