Queued Update 

Use

A queued update represents a sequence of configuration changes that are carried out as a whole. The use of a queued update is beneficial if several related or interdependent configuration objects need to be processed.

An administrator can use a queued update to create, duplicate, delete, or update several configuration objects. As soon as the administrator starts the queued update, all changes made are stored temporarily and all changed or newly created configuration objects are locked to other users. The changes take effect and the affected configuration objects are unlocked only when the administrator confirms the queued update.

 

Features

When you start the queued update, a map of the current system configuration is created in the memory. All changes that you now carry out are stored in this map. When you confirm the changes, they are written to the map in the system configuration. However, you can also discard these changes. If you do so, the map is deleted and the system configuration remains unchanged.

Each user can have one queued update. This means that the queued update is user-dependent.

Locks on configuration objects are normally maintained for ten hours. The locks are then lifted automatically.

 

Constraints

If several administrators start and execute a queued update in the system at short intervals from one another, the changes made in the last queued update to be made are adopted. Changes made in the previous queued updates are overwritten.

 

Known behavior:

You are editing an existing configuration object or creating a new one. You confirm the change using the Apply pushbutton. You leave the page and do not choose Save or Cancel. You finish the queued update by confirming or discarding the changes. However, the configuration object remains locked. This behavior occurs if you are editing a configuration object and leave the page. The lock continues to be active after the queued update has finished. The lock remains even if you close the browser window.

 

To resolve this restriction, choose Pending Locks from the lower area of the Configuration iView, and remove the lock manually.

 

Activities

To start a queued update, choose Actions ® Update Queuing from the lower area of the Configuration iView. Choose Queued Update. A small flag shows that the queued update has been activated.

Make the required configuration changes.

If you have finished making changes to the configuration, and now want to apply these changes, choose Actions ® Update Queuing ® Apply Queued Updates. To discard the changes to the configuration, choose Actions ® Update Queuing ® Discard Queued Updates.

In both cases, you then receive an overview of the collective changes. When you have completed the queued update, the flag is no longer displayed.

 

Example

You want to create a repository manager with a cache.

...

       1.      Start the queued update.

       2.      Create a cache.

       3.      Create a repository manager and select the cache that you just created from its configuration.

       4.      Accept the collected changes and end the queued update.

The two new configuration objects are now registered in the configuration in one step.