WAS configuration model using wsadmin.sh
Understanding the relationship between the different configuration objects is essential when creating wsadmin scripts that perform configuration function.
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, and port numbers the server will use. Other configuration files define Java EE resources to which the server connects in order to obtain data 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, and cache settings, are stored in files under the root directory of each application. When viewing the XML data in the configuration files, we can discern relationship between the configuration objects.
For more information on the WebSphere Application Server configuration objects view the HTML tables in the app_server_root/web/configDocs directory. There 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:
Use wsadmin scripting with Jacl (deprecated) Use wsadmin scripting with Jython wsadmin objects Get started with wsadmin scripting Start the wsadmin scripting client