Express (Distributed operating systems), v8.0 > Secure applications and their environment > Authenticate users > Select a registry or repository > Manage realms in a federated repository > Virtual member manager > Configure virtual member manager
Configure in a shared environment
When virtual member manager is used in a shared environment, where multiple applications are sharing the same virtual member manager instance, administering configuration becomes a critical task.
When one application has configured virtual member manager and then another application wants to share the same instance of virtual member manager, there needs to be some constraints and limitations to make sure that both applications can share virtual member manager without conflict.
Depending on how changes to a configuration parameter affect virtual member manager critical functionality, configuration parameters are categorized as :
Shared
- Critical – if these properties are modified they might have serious adverse effects
- Not critical – shared but if these properties are modified, they do not affect the critical functionality of other applications. However, there might be some impact to the other applications.
Not shared
These properties are not shared by the applications. Not-shared or shared but not critical parameters can be modified by applications or their administrators by calling the virtual member manager configuration API without any intervention by the virtual member manager administrator. When a critical shared configuration parameter is modified, the virtual member manager administrator makes the modifications. The virtual member manager administrator is responsible for determining whether a shared critical configuration parameter can be modified.
Parent topic: Configure virtual member manager