Saving configuration changes with the wsadmin tool

Use the wsadmin tool and scripting to save configuration changes to the master configuration repository.

Overview

Procedure

1. Using Jacl:

   $AdminConfig save

2. Using Jython:

   AdminConfig.save()

where:

$	is a Jacl operator for substituting a variable name with its value
AdminConfig	is an object representing the WebSphere Application Server configuration
save	is an AdminConfig command

If you are using interactive mode with the wsadmin tool, you will be prompted to save your changes before they are discarded.

If you are using the -c option with the wsadmin tool, changes are automatically saved. On a Unix operating system, if you invoke a command that includes a dollar sign character ($) using the wsadmin -c option, the command line attempts to substitute a variable. To avoid this problem, escape the dollar sign character with a backslash character (\). For example: wsadmin -c "\$AdminConfig save".

If a scripting process ends and no save has been performed, any configuration changes made since the last save are discarded. If there are multiple clients (scripts or browser clients) updating the configuration at the same time, it is possible that the changes requested by a script may not be saved. If this happens, you will receive an exception and make the updates again. If the save fails, the updates will not be saved to the configuration. If it succeeds, all updates are saved. To avoid save failures, you can invoke the save command after every configuration update.

You can use the reset command of the AdminConfig object to undo changes that you made to your configuration since your last save.

Related Reference