|
|
The Change Center allows for team collaboration when services and metadata are being configured in ALSB. Each user works in a sandbox session until the user is ready to check in the working configuration to the core configuration of the bus. The change center provides multiple levels of undo, and visibility into conflicts, as multiple users work on the configuration.
Most of the Change Center pages display different information based on whether you are in a session (that is, you have clicked Create or Edit in the Change Center) or outside a session. For example, in a session, the View Configuration Changes page lists all the changes you have made in that session; outside a session, the page lists all session activations.
Table 2-1 displays Change Center tasks and related session information.
The Change Center module is the starting point for using the ALSB Console to make changes to your configuration. To make configuration changes using the console, you must use the Change Center to start a session.
Click Discard under Change Center, at any time during the session, to discard the changes you have made so far in the current session.
Creating a session and discarding a session proceed regardless of other activity in the system. However, if another session is in the process of being activated, the Activate Session page displays an error indicating the user that has the pending WebLogic Server changes. For information on resolving conflicts between changes made in your session and other activated sessions, see Viewing and Resolving Conflicts.
You will not be able to activate the session until you have viewed all conflicts. If new conflicts arise while you view the existing conflicts, before you activate, a message pops up informing you of the new conflicts.
| Note: | When you attempt to activate a session with a JMS endpoint URI on another server (a single server other than the one on which you are working, or a Managed Server in a cluster), ensure that the destination server is available. |
| Note: | ALSB does not allow registration of proxy services with JMS transport if the JMS endpoint URL specifies a destination that is unreachable. In other words, for JMS services, ALSB checks if the specified connection factory exists; if it does not, a session activation error occurs. |
Click Exit under Change Center at any time to exit the session. However, the session does not end.
You can click Edit under Change Center to return to the session and continue making changes. This behavior also applies if you click Logout to log out of the console or close your browser. The session and all changes that you have made in the session persist even if you log out of the console or the server is restarted.
The session ends only after it has been activated. See Activating Sessions.
This page displays different information based on whether you are in a session (that is, you have clicked Create or Edit in the Change Center) or outside a session.
A description of the task that was implemented. The task is a link to the Task Details page. See Viewing Task Details.
|
|
|
As a result of undoing a task, the object of the task reverts to the state it was in before the task in question was performed. Note, however, that any tasks that were performed on the same object after the task that you undo are also undone. See Undoing Tasks.
|
A description of the session that was activated. The task is a link to the Task Details page, which displays the operations that were performed in the session. See Viewing Task Details.
|
|
|
Partially Activated—displayed during session activation if one or more servers in a cluster are inaccessible, thus preventing activation of the session on those servers. When the servers become accessible, any unactivated changes will then be activated on them.
Undone—the previously activated session was undone and all the operations performed in the session were discarded.
|
|
Click the
 Undo icon to reverse the session activation and the operations performed in that session. You can undo session activations in any order.
Click the
 Undo into Session icon to create a new session pre-populated with the tasks needed to undo the changes activated in the session. See Undoing Into a Session.
|
You can purge sessions activated over a specific period, delimited by start and end dates. This action can only be performed outside a session.
| WARNING: | Purging session activation history involves deleting data that enables multiple levels of undo. In other words, if you purge session activation history for a specific period, you will not be able to undo sessions activated during that period. |
MM/DD/YYYY.The session activation history for all sessions between the dates specified will be deleted from ALSB.
Use the View Configuration Changes page to undo tasks that you have performed in your ALSB configuration during your current session, and to undo session activations outside a session. ALSB lets you undo multiple levels of session activation, constrained only by your system resources. For more information, see Order of Undoing Tasks.
| Note: | If you upgrade from ALSB version 2.1 to version 2.5, you will not be able to undo sessions activated before the upgrade. Sessions activated after the upgrade will be available in the session activation history, for undo. |
Undo icon. You can undo any change in the current session. However after that, if you change your mind, you can undo the undo, or if you again change your mind, you can undo the undo that undid a previous undo, and so on.
Undo icon. The session activation is undone. Undo into Session icon. A new session is created pre-populated with the tasks needed to undo the changes activated in the session. For more information, see Undoing Into a Session.You can undo tasks in any order (provided that individual undo actions result in valid data). The undo operation sets the value of a resource to the value it had before the change to that resource.
In the case that the task that is being undone was one that created an object, there is no previous state to which an object can be returned—in other words, no object existed before this task was performed. Effectively, the undo operation deletes the new object from the session. In this case, errors occur for the objects that reference the one being deleted. You can view such errors on the View Conflicts page in the Change Center.
When you are not working in a session, you can access the View Configuration Changes page to see the sessions that were previously activated. You can undo these sessions. The system does not allow you to undo a session that was previously activated if an error in the run time configuration would result from the undo action. For example, if you attempt to undo a session activation that results in the removal of an object that is being referenced by another object, that undo action is disallowed.
It is possible to undo an undo action. In the Options column of the Undo of [task], click the Undo icon. ALSB supports unlimited undo. This means you can undo the undo that undid a previous undo, and so on.
If semantic errors result from undoing a session activation, you are prevented from doing the undo. However there is an alternative in this case. You can undo the session activation and have the changes put into a new session. You can then fix the semantic errors and activate the session. You can also use this capability of undoing into a session to explore the ramifications of a session activation undo. You can examine all the changes that result, and decide if you really want to do the undo. If you decide that you really want to, you can activate the session.
Use this page to view details of a specific change you made in the current session if you are in the session, and view details of specific changes you made in sessions that have been activated if you are outside a session.
Use this page to view all existing sessions within the ALSB Console. You can view these sessions if you are currently in a session or outside a session.
You can view all sessions only if you are using the Administrator role. For more information, see Configuring Administrative Security in the AquaLogic Service Bus Security Guide.
| Note: | The same user logged in with multiple browsers is not supported. It causes unpredictable behavior in the console. |
Use this page to view diagnostic messages about errors in your configuration, and to view and resolve conflicts between changes made in your session and other activated sessions. The view conflicts link also displays the number of live conflicts in the session.
Error icon denotes non-committable, critical conflicts)—inform you of critical conflicts within your configuration. You cannot commit your changes without resolving the conflicts. See Table 2-6 and Resolving Conflicts.
Warning icon denotes committable, non-critical conflicts)—warn you about incompatible changes with other activated sessions. See Table 2-7. Warning icon denotes committable, non-critical conflicts)—inform you of any non-critical conflicts within your configuration.
A description of the conflict. To resolve the conflict, see Resolving Conflicts.
|
If the object to which you make changes in a session has changed in the run time since you began the edit of the current session, the View Conflicts page displays the information shown in Table 2-7.
To resolve a conflict, use the information provided in the Messages column (as described in Table 2-6) to understand the problem, and then edit the object that is causing the conflict to fix the problem.
For the scenario in which you have a concurrent update conflict—that is, a conflict that occurs if a resource is modified in the current session that has already been modified and activated by another session (as described in Table 2-7), you can resolve the conflict in one of two ways:
Synchronize icon in the Synchronize column of the table (as described in Table 2-7). This action restores this object, in this session, to the state in which it was saved in the run time.
|