Activating Sessions

  1. Click Activate in the Change Center. The Activate Session page shows the session name, user name, and a description field.
  2. 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.

  3. If there are validation errors, an error message is displayed, indicating that your session has validation errors. View and fix configuration conflicts before you proceed. For information on fixing conflicts, see Viewing and Resolving Conflicts.
  4. 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.

  5. Enter a description in the Description field. This description is displayed in the Description column when you click View Changes under Change Center to display configuration changes caused by session activations.
  6. To activate the session, click Submit. If no new conflicts have arisen in the interim, the session ends and the configuration is deployed to the run time.
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.