Network Deployment (Distributed operating systems), v8.0 > Scripting the application serving environment (wsadmin) > Use the wsadmin scripting AdminConfig object for scripted administration
Saving configuration changes with wsadmin.sh
Use wsadmin.sh and scripting to save configuration changes to the master configuration repository.
The wsadmin tool uses the workspace to hold configuration changes. We must save 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:
### Jacl
$AdminConfig save
### Jython
AdminConfig.save()
If you are using interactive mode with wsadmin.sh, you will be prompted to save changes before they are discarded.
If you are using the -c option with wsadmin.sh, changes are automatically saved.
(AIX) 
(Solaris) 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.
We can use the reset command of the AdminConfig object to undo changes that you made to the configuration since your last save.
Use the wsadmin scripting AdminConfig object for scripted administration
Related
Commands for the AdminConfig object using wsadmin.sh