Use the AdminConfig object for scripted administration



Search Tips   |   Advanced Search



AdminConfig is used to...

Updates to the configuration through a scripting client are kept in a temporary workspace and are not copied to the master configuration repository until you run a save command.

The workspace is located under...


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 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 appserver, the AdminConfig commands will not be available because the configuration for these server processes are copies of the master configuration residings 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.

General steps...

  1. Identify the configuration type and attributes.
  2. Query an existing object and obtain a configuration ID.
  3. Modify or create object.
  4. Save the config.



Commands for the AdminConfig object
Create configuration objects using wsadmin
Interpreting the output of the AdminConfig attributes command using scripting
Specifying configuration objects using wsadmin
Listing attributes of configuration objects using wsadmin
Modify configuration objects with wsadmin
Remove configuration objects with wsadmin
Remove the trust association interceptor class using scripting
Change the appserver configuration using wsadmin
Modify nested attributes with wsadmin
Saving configuration changes with wsadmin