Saving configuration changes with the wsadmin tool

 

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

 

Overview

The wsadmin tool uses the workspace to hold configuration changes. You must save your changes to transfer the updates to the master configuration repository. If a scripting process ends and you have not saved your changes, the changes are discarded.

 

Procedure

Use the following commands to save the configuration changes:

1. Use Jacl:

   $AdminConfig save
   

2. Use Jython:

   AdminConfig.save()
   

where:

$	Jacl operator for substituting a variable name with its value
AdminConfig	object representing the WebSphere Application Server configuration
save	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.

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 the configuration since your last save.

---

Use the AdminConfig object for scripted administration

 

Related Reference

Commands for the AdminConfig object