Properties used by wsadmin.sh
There are three levels of default property files that load before any property file specified on the command line:
- Installation default, located in the WAS properties directory called wsadmin.properties.
- User default, located in the Java user.home property. This properties file is also called wsadmin.properties.
- Properties file 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 present on the command line. The properties file loaded last, overrides the ones loaded earlier.
The following Java properties are used by scripting...
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, RMI, or NONE. The wsadmin.properties file specifies SOAP as the connector.
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.port Specifies the 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.defaultLang Indicates the language to use when executing scripts. The wsadmin.properties file specifies Jacl as the scripting language. The supported scripting languages are Jacl and Jython. Other scripting languages that the Bean Scripting Framework (BSF) supports might work, but have not been tested.
com.ibm.ws.scripting.traceString Turns on tracing for the scripting process. Tracing turned off is the default.
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 WebSphere Application Server properties directory 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 unicode format, such as \uxxxx, where xxxx is a number.
com.ibm.ws.scripting.validationOutput Determines where the validation reports are directed. The default file is wsadmin.valout located in the WebSphere Application Server logs directory. 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.
com.ibm.ws.scripting.emitWarningForCustomSecurityPolicy Controls whether message WASX7207W is emitted when custom permissions are found. The possible values are true and false. The default value is true.
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.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.profiles Specifies a list of profiles 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 will perform conversion to change the profile names specified in this property to use file extension that matches the language specified. Use the default to make security configuration easier.