5.1 Capabilities, Limitations, and Requirements

During server application initialization, application factories need to be registered with the NameManager. Clients can then be provided with the object reference of a FactoryFinder to allow them to retrieve a factory object reference based on associated names that were created when the factory was registered.

The following functional capabilities, limitations, and requirements apply to this release:

• The FactoryFinder interface is in compliance with the CosLifeCycle::FactoryFinder interface.
• Server applications can register and unregister application factories with the CORBAservices Naming Service.
• Clients can access objects using a single point of entry—the FactoryFinder.
• Clients can construct names for objects using a simplified Oracle scheme made possible by Oracle Tuxedo extensions to the CORBAservices interface or the more general CORBA scheme.
• Multiple FactoryFinders and NameManagers can be used to increase availability and reliability in the event that one FactoryFinder or NameManager should fail.
• Support for multiple domains. Factories in one domain can be configured to be visible in another domain under administrative control.
• Two NameManager services, at a minimum, must be configured, preferably on different machines, to maintain the factory-to-object reference mapping across process failures. If both NameManagers fail, the master NameManager, which has been keeping a persistent journal of the registered factories, recovers the previous state by processing the journal so as to re-establish its internal state.
• One NameManager must be designated as the Master and the Master NameManager must be started before the Slave. If the master NameManager is started after one or more Slaves, the Master assumes that it is in recovery mode instead of in initializing mode.