If virtual member manager is configured to use the dynamic model, the dynamic process of loading schema occurs when virtual member manager starts up.
When virtual member manager starts, the Configuration Manager loads the wimconfig.xml file into configuration data graph. The Schema Manager is then passed with configuration data graph.
The Schema Manager gets the name of the XSD file (wimextension.xsd) from data object, dynamicModel, and loads the schemas from this file. Because this XSD file imports all other virtual member manager built-in schema XSD files, both the custom extension schemas ( http://www.ibm.com/websphere/wim/ext ) and the virtual member manager built-in schema ( http://www.ibm.com/websphere/wim ) are loaded into memory as ECore models in the form of an EPackage. At the same time, the Schema Manager also registers these models.
If the instance of the Local Service Provider is not in the same JVM as the virtual member manager instance, an instance of Local Service Provider is created remotely, the Local Service Provider calls the virtual member manager API getEPackages to retrieve the schemas of all namespaces by passing the nsURI parameter as null.
The Schema Manager receives the API call. Because the ECore models are not serialized and cannot be passed to the remote client, the Schema Manager converts the ECore models into the form of a byte array and passes the schemas back to the Local Service Provider. The Local Service Provider converts the schemas from byte array to ECore models and registers them in the client's JVM.