If num is set to a value larger than zero, each service inherits the configuration properties of the IceBox server’s communicator.
Specifies an alternate identity category for the IceBox service manager object. If defined, the identity of the object becomes
name/ServiceManager. If not specified, the default identity category is
IceBox.
Determines the order in which services are loaded. The service manager loads the services in the order they appear in
names, where each service name is separated by a comma or white space. Any services not mentioned in
names are loaded afterward, in an undefined order.
If this property is set to a value greater than zero, the service manager prints “
token ready” on standard output once initialization of all the services is complete. This is useful for scripts that wish to wait until all services are ready to be used.
In C++, entry_point has the form
basename[,version]:symbol. The
basename and optional
version components are used to construct the name of a DLL or shared library. If no version is supplied, the version is the empty string. The
symbol component is the name of a function with C linkage. For example, the entry point
IceStormService,32:createIceStorm implies a shared library name of
libIceStormService.so.32 on Unix and
IceStormService32.dll on Windows. Furthermore, if IceBox is built on Windows with debugging, a
d is automatically appended to the version (e.g.,
IceStormService32d.dll).
In Java, entry_point is the name of the service implementation class.
IceBox uses the adapter name IceBox.ServiceManager for its object adapter. Therefore, all the adapter properties detailed in
Section C.4 can be used to configure the IceBox object adapter.
If num is set to a value larger than zero, the service manager supplies the service with the
name of a communicator that might be shared by other services.
