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. We 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 administrative console use. The workspace is kept in the wstemp subdirectory of the 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 Network Deployment installation.

The AdminConfig commands are available only if a scripting client is connected to a deployment manager. 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 deployment manager. The copies are created in a node machine when configuration synchronization occurs between the deployment manager and the node agent. You should make configuration changes to the server processes by connecting a scripting client to a deployment manager. 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.

• Query and update a configuration object.

  1. Identify the configuration type and the corresponding attributes.

  2. Query an existing configuration object to obtain a configuration ID to use.

  3. Modify the existing configuration object or create a one.

  4. Save the configuration.

• See the Commands for the AdminConfig object topic. We can also use the help command, for example:

  Jacl:

  $AdminConfig help

  Using Jython:

  print AdminConfig.help()

Subtopics

• Create configuration objects using wsdmin.sh
  We can use scripting and wsadmin.sh to create configuration objects.

• Interpreting the output of the AdminConfig attributes command
  Use scripting to interpret the output of the AdminConfig attributes command.

• Specify configuration objects using wsdmin.sh
  Specify configuration objects and wsadmin.sh.

• Listing attributes of configuration objects using wsdmin.sh
  We can use scripting to generate a list of attributes of configuration objects.

• Modify configuration objects using wsdmin.sh
  Modify configuration objects and wsadmin.sh.

• Remove configuration objects with wsadmin.sh
  Use this task to delete a configuration object from the configuration repository. This action only affects the configuration.

• Remove the trust association interceptor class
  Use wsadmin.sh to remove the trust association interceptor class.

• Change the application server configuration
  We can use the wsadmin AdminConfig and AdminApp objects to make changes to the application server configuration.

• Modify nested attributes using wsdmin.sh
  We can modify nested attributes for a configuration object and wsadmin.sh.

• Saving configuration changes with wsadmin.sh
  Use wsadmin.sh and scripting to save configuration changes to the master configuration repository.

Commands for the AdminConfig object