Problem:
VisiBroker 8.0 client hang when invoking a server process controlled by the Object Activation Daemon (OAD).
Resolution:
VisiBroker 8.0 introduces ORB componentization and the OAD functionality is moved into the DSUser library. For details about componentization in VisiBroker 8.0, please refer the article below:
http://community.microfocus.com/microfocus/corba/visibroker_-_world_class_middleware/w/knowledge_base/15852.visibroker-for-c-8-x-shared-library-repackaging.aspx
http://community.microfocus.com/microfocus/corba/visibroker_-_world_class_middleware/w/knowledge_base/15852.visibroker-for-c-8-x-shared-library-repackaging.aspx
VisiBroker server ORB uses "vbroker.agent.enableLocator" property to load the dsuser library dynamically.
false - dsuser library is not loaded
true - dsuser library is loaded
However, at times, the application wants to enable the OAD functionality w/o enabling the the server ORB to look for osagent. The "vbroker.orb.loadDSUser" is introduced in VisiBroker 8.0 SP 2 to support this requirement. The default value is false.
false - dsuser library is loaded when vbroker.agent.enableLocator=true
true - dsuser library is loaded regardless of the value set for vbroker.agent.enableLocator
#OAD
#Security
#VisiBroker
#componentization
#loadDSUser
#enableLocator
#DSUser