Network Deployment (Distributed operating systems), v8.0 > Scripting the application serving environment (wsadmin)
Use the wsadmin scripting AdminConfig object for scripted administration
Use the AdminConfig object to manage the configuration information stored in the repository.
This object communicates with the WAS configuration service component to make configuration inquires and changes. You can use it to query existing configuration objects, create configuration objects, modify existing objects, remove configuration objects, and obtain help.
Updates to the configuration through a scripting client are kept in a private temporary area called a workspace and are not copied to the master configuration repository until you run a save command. The workspace is a temporary repository of configuration information that administrative clients including the admin console use. The workspace is kept in the wstemp subdirectory of your WAS installation.
The use of the workspace allows multiple clients to access the master configuration. If the same update is made by more than one client, it is possible that updates made by a scripting client will not save because there is a conflict. If this occurs, the updates will not be saved in the configuration unless you change the default save policy with the setSaveMode command.
The AdminConfig commands are available in both connected and local modes. If a server is currently running, it is not recommended that you run the scripting client in local mode because the configuration changes made in the local mode is not reflected in the running server configuration and vice versa. In connected mode, the availability of the AdminConfig commands depend on the type of server to which a scripting client is connected in a WAS ND installation.
The AdminConfig commands are available only if a scripting client is connected to a dmgr. When connected to a node agent or an application server, the AdminConfig commands will not be available because the configuration for these server processes are copies of the master configuration that resides in the dmgr. The copies are created in a node machine when configuration synchronization occurs between the dmgr and the node agent. You should make configuration changes to the server processes by connecting a scripting client to a dmgr. For this reason, to change a configuration, do not run a scripting client in local mode on a node machine. It is not a supported configuration.
Procedure
- Query and update a configuration object.
- Identify the configuration type and the corresponding attributes.
- Query an existing configuration object to obtain a configuration ID to use.
- Modify the existing configuration object or create a one.
- Save the configuration.
- See the Commands for the AdminConfig object:
### Jacl $AdminConfig help ### Jython print AdminConfig.help()
Related
Create configuration objects using wsadmin.sh
Interpreting the output of the AdminConfig attributes command using wsadmin.sh
Specify configuration objects using wsadmin.sh
List attributes of configuration objects using wsadmin.sh
Modify configuration objects using wsadmin.sh
Remove configuration objects with wsadmin.sh
Remove the trust association interceptor class using scripting
Change the application server configuration using wsadmin
Modify nested attributes using wsadmin.sh
Saving configuration changes with wsadmin.sh
Related
Commands for the AdminConfig object using wsadmin.sh