To start the edit process, you obtain a lock to prevent other people from making changes. When you finish making changes, you save the changes. The changes do not take effect, however, until you activate them, distributing them to all server instances in the domain.
The configuration change lock does not prevent you from making conflicting configuration edits using the same administrator user account. For example, if you obtain a configuration change lock using the Administration Console, and then use the WebLogic Scripting Tool (WLST) with the same user account, you will access the same edit session that you opened in the Administration Console and you will not be locked out of making changes with the WLST.
Note: BEA Systems recommends against this because when one of the sessions activates their changes, it releases the lock and the other session will not be able to save or activate their changes.
To make any changes using the Console, you must:
This enables you to make changes using the Administration Console.
After you finish
Some changes you make in the Administration Console take place immediately when you activate them. Other changes require you to restart the server or module affected by the change. These latter changes are called non-dynamic changes. Non-dynamic changes are indicated in the Administration Console with this warning icon:
Note: If an edit is made to a non-dynamic configuration setting, no edits to dynamic configuration settings will take effect until after you restart the server.