WAS configuration model
Configuration data is stored in several different XML files which the server run time reads when it starts and responds to the component settings stored there. The configuration data includes the settings for the run time, such as...
- JVM options
- thread pool sizes
- container settings
- port numbers
Other configuration files define J2EE resources to which the server connects in order to obtain data that is needed by the application logic. Security settings are stored in a separate document from the server and resource configuration. Application-specific configuration, such as...
- deployment target lists
- session configuration
- cache settings
...are stored in files under the root directory of each application. When viewing the XML data in the configuration files, you can discern relationship between the configuration objects.
For more information on the WAS configuration objects view the HTML tables in...
installroot/web/configDocsThere are several subdirectories, one for each configuration package in the model. The index.html file ties all of the individual configuration packages together in a top-level navigation tree. Each configuration package lists the supported configuration classes and the configuration class lists all of the supported properties. The properties with names that end with the at (@) character imply that property is a reference to a different configuration object within the configuration data. The properties with names that end with an asterisk (*) character imply that the property is a list of other configuration objects.
Related concepts
Jacl
Jython
Related tasks
Use the wsadmin scripting objects
Getting started with scripting
Start the wsadmin scripting client