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


Configuration files

The main configuration file is called wimconfig.xml. This file stores the virtual member manager settings at the global (admin) level or at the domain level in a multiple security domain environment.

When virtual member manager is started, during initialization, the virtual member manager core component retrieves configuration data using the virtual member manager Configuration API. Some of the configuration data is passed to the various adapters for their own initialization. This file contains the following information:

The wimdomain.xsd file contains the “data model” of virtual member manager. It consists of the definitions of the entity types that virtual member manager supports out-of-the-box. The wimdomain.xsd is the detailed XML Schema representation of the virtual member manager common data model. The properties for the entity types are defined at the virtual member manager level and need to be mapped to actual repository-specific property definitions in other configuration files.

The wimdatagraph.xsd file defines the options that can be specified when the virtual member manager API is invoked.

If extend the virtual member manager domain model to add more entity types or properties for the out-of-the-box entity types, use a separate XSD file (for example, wimextension.xsd) or a separate XML file (for example wimxmlextension.xml).


Virtual member manager configuration files in a multiple security domain environment

When you create a security domain in WAS 8.0, all virtual member manager configuration files are created for that domain, regardless of whether virtual member manager is configured as the active user registry.

WAS provides an option to create a domain by copying a selected domain from a domain collection. Based on the options you specify while creating a domain, virtual member manager files are copied from the selected domain, the admin security domain, or default profile template location. This might also include copying the file repository if it exists in the source domain.

The domain-specific virtual member manager files are located under the WAS_HOME/profiles/profile_name/config/waspolicies/$PolicyName/securitydomains/$DomainName directory.

The files related to virtual member manager configuration and data model schema are listed in the following table.

The following directory conventions are used in the table:

Virtual member manager configuration files

Description Level Directory File name
Virtual member manager configuration schema file One global copy for the whole system WAS_HOME/etc/wim/schema/config wimconfig.xsd
Virtual member manager configuration file Global level cell_vmm_root/config wimconfig.xml
Domain level
domain_vmm_root/config
Argus files Global level cell_vmm_root/config/authz  
Domain level
domain_vmm_root/config/authz
File registry that contains users and groups for the out-of-the-box file repository Global level PROFILE_ROOT/config/cells/$CellName fileRegistry.xml

The fileRegistry.xml file is copied for a new domain only if the source domain contains this file.


Domain level PROFILE_ROOT/config/waspolicies/$PolicyName/securitydomains/$DomainName
Virtual member manager out-of-the-box data model schema files. One global copy for the whole system WAS_HOME/etc/wim/schema/model

The same files are also copied to cell_vmm_root/model as they are required for migration purposes.

wimdatagraph.xsd
wimdomain.xsd
wimschema.xsd
xml.xsd
Virtual member manager data model extension files Global level cell_vmm_root/model wimxmlextension.xml
custom xsd
Domain level domain_vmm_root/model
wimxmlextension.xml
custom xsd

Parent topic: Configure virtual member manager
Extend virtual member manager functionality in the application


+

Search Tips   |   Advanced Search