Administrative properties for
Scripting administration utilizes several Java property files. Property files can be used to control the system configurations. Before any property file is specified on the command line, three levels of default property files are loaded. These property files include an installation default file, a user default file, and a properties file.
The first level represents an installation default, located in the profile_root/properties directory for each application server profile called wsadmin.properties. The second level represents a user default, and is located in the Java user.home property. This properties file is also called wsadmin.properties. The third level is a properties file that is pointed to by the WSADMIN_PROPERTIES environment variable. This environment variable is defined in the environment where wsadmin.sh starts.
If one or more of these property files is present, they are interpreted before any properties file that is present on the command line. The three levels of property files load in the order that they are specified. The properties file that is loaded last overrides the ones loaded earlier.
The following Java properties are used by scripting:
com.ibm.ws.scripting.appendTrace
Determines if the trace file appends to the end of the existing log file. The default setting, false, overrides the log file on each invocation.
com.ibm.ws.scripting.classpath
Searches for classes and resources, and is appended to the list of paths.
com.ibm.ws.scripting.connectionType
Determines the connector to use. This value can either be SOAP, JSR160RMI, RMI, IPC, or NONE. The wsadmin.properties file specifies SOAP as the connector.
com.ibm.ws.scripting.crossDocumentValidationEnabled
Determines whether the validation mechanism examines other documents when changes are made to one document.
Possible values are true and false. The default value is true.
com.ibm.ws.scripting.defaultLang
Indicates the language to use when running scripts. The wsadmin.properties file specifies Jacl as the scripting language.
The supported scripting languages are Jacl and Jython.
com.ibm.ws.scripting.echoparams
Determines if the parameters or arguments output to STDOUT or to a wsadmin log file. The default setting, true, outputs the parameters or arguments to a log file.
com.ibm.ws.scripting.emitWarningForCustomSecurityPolicy
Controls whether the WASX7207W message is emitted when custom permissions are found.
The possible values are true and false. The default value is true.
com.ibm.ws.scripting.exceptionPropagationThrown
Set this property to report the correct exception when a WAS built-in scripting object throws an exception, which is caught and handled in the script, and later a second non WebSphere Application Server exception is thrown and uncaught. On exit, wsadmin will erroneously report the first exception as the cause for exiting.
com.ibm.ws.scripting.host
Determines the host to use when attempting a connection. If not specified, the default is the local machine.
com.ibm.ws.scripting.ipchost
The ipchost property determines the host that the system uses to connect to the IPC connector. Use the host name or IP address of the loopback adapter that the IPC connector listens to, such as localhost, 127.0.0.1, or ::1. The default value is localhost.
com.ibm.ws.scripting.port
Port to use when attempting a connection. The wsadmin.properties file specifies 8879 as the SOAP port for a single server installation.
com.ibm.ws.scripting.profiles
List of profile scripts to run automatically before running user commands, scripts, or an interactive shell.
The wsadmin.properties file specifies securityProcs.jacl and LTPA_LDAPSecurityProcs.jacl as the values of this property. If Jython is specified with the wsadmin -lang option, wsadmin.sh performs a conversion to change the profile script names specified in this property to use the file extension that matches the language specified. Use the provided script procedures with the default settings to make security configuration easier.
com.ibm.ws.scripting.traceFile
Determines where trace and log output is directed. The wsadmin.properties file specifies the wsadmin.traceout file located in the profile_root/logs directory of each application server profile as the value of this property.
If multiple users work with wsadmin.sh simultaneously, set different traceFile properties in the user properties files. If the file name contains double-byte character set (DBCS) characters, use a unicode format, such as \uxxxx, where xxxx is a number.
com.ibm.ws.scripting.traceString
Turns on tracing for the scripting process. The default has tracing turned off.
com.ibm.ws.scripting.tempdir
Determines the directory to use for temporary files when installing applications.
The JVM API uses java.io.temp as the default value.
com.ibm.ws.scripting.validationLevel
Determines the level of validation to use when configuration changes are made from the scripting interface.
Possible values are: NONE, LOW, MEDIUM, HIGH, HIGHEST. The default is HIGHEST.
com.ibm.ws.scripting.validationOutput
Determines where the validation reports are directed. The default file is wsadmin.valout which is located in the profile_root/logs directory of each application server profile.
If multiple users work with wsadmin.sh simultaneously, set different validationOutput properties in the user properties files. If the file name contains double-byte character set (DBCS) characters, use unicode format, such as \uxxxx, where xxxx is a number.
Related tasks
Scripting and command line reference material Reference topic