Weblogic 12C Features - Named Concurrent Edit Sessions

Weblogic 12C Features – Named Concurrent Edit Sessions

In 12.2.1 there is no longer a single global Edit lock on the administrative changes being executed in a domain. With Named Concurrent Edit Sessions, multiple administrators can now have concurrent edit sessions. This is especially useful in a multitenant scenario where different partitions are managed by different administrators.

This describes how to manage concurrent named edit sessions in WebLogic Server Multitenant (MT). You can use either Fusion Middleware Control (FMWC), the WLS Administration Console, or WLST to manage edit sessions.

In previous releases, WebLogic Server configuration edit sessions supported only one active edit session at a time. The system administrator got a global edit lock, made changes, and then activated them. Other administrators could not make changes at the same time. In this release, there are situations in which more than one administrator may need to make configuration changes. A multitenant WLS domain contains multiple partitions each with its own administrator. Partition administrators must be able to make configuration changes to the partition configuration and resources deployed in the partition without affecting other partition administrators or the WLS system administrator. Therefore, WLS has enabled multiple, concurrent edit sessions which support one or more configuration edit sessions per partition plus global configuration edit sessions.

With this feature, an administrator creates a named edit session, makes changes, and then activates the changes. Another administrator also creates a named edit session in parallel. If there are conflicts between the edit session from the first administrator and the changes made by a second administrator, the second administrator will receive an error when activating their changes.


Managing Named Concurrent Edit Sessions: Main Steps

  1. Administrators create (and destroy) named edit sessions. :

You use the ConfigurationManagerMBean API to start an edit session, activate changes, show changes, undo changes, and so forth. Each edit session has its own configuration files and ConfigurationManagerMBean instance.

  1. Changed configuration files are persisted to an edit-session-specific directory:
  • Global named edit session changes are persisted to a sub-directory of a new edit directory at the domain level: <domain-directory>/edit/<edit-session-name>, where edit-session-name is a version of the edit session name specified at create-edit-session time.
  • Partition-specific named edit session changes are persisted to a sub-directory of the partition directory: <partition-directory>/edit/<edit-session-name>, where edit-session-name is a version of the edit session name specified at create-edit-session time.
  1. Conflicts may occur between parallel edit sessions when changes are activated. If any conflicts occur during activation, then the activate operation will fail and you must resolve the conflicts manually.

To resolve conflicts, administrators can use these informational messages:

  • Each conflict contains a description including the identification of MBeans and/or properties in conflict.
  • Each conflict also contains a message describing the resolve operation for this conflict.

Resolve log messages contain short descriptions of each resolve and merge step. Administrators can use the resolve log message to identify what was modified and how it was modified in the current edit session

Related Posts:


Weblogic 12C Features

Multitenancy Support

Continuous Availability

Elasticity for Dynamic Clusters

RESTful Management Services