| Resolution |
All optional ORB plugins for an Orbix application are listed Inside the domain configuration .
You can obtain the domain configuration by running the command:
itadmin config dump
From the configuration, the variable orb_plugins specifies the plug-ins that the ORB should load during application initialization. Each plugin has a corresponding class name (Java) or shared library\\DLL (C ). These are defined in the configuration file as below:
C
plugins:<<plugin name>>:<<shared library>>;
Java
plugins:<<plugin name>>:ClassName=<<class name>>;
As referenced in the administrators guide, each variable is valid only inside it's scope, and can be redefined in subscopes.
Loading a plugin guarantees it will be instantiated, but does not guarantee that it will be used. Some plugins, for example giop_snoop, must be placed in a binding list to ensure that it is used. The possible binding variables are binding:server_binding_list, binding:client_binding_list, and binding:servlet_binding_list.
The command
itadmin variable show [-scope <scoped name>] orb_plugins
will show the orb_plugins defined at a specific scope.
Please reference the CORBA plugins chapter of the Orbix Configuration Reference for a description of each plugin. Inside the Configuration Reference chapter on Core Namespaces, the section binding defines the binding lists.
It is also possible to use the IT_SHLIB_VERBOSE variable to view which C libraries are loaded when running Orbix.
“Related KB Article(s):”
000029386, "How view which C libraries are loaded when running Orbix"
References to other documentation:
Orbix Configuration Reference, “Core Namespaces”
|
|---|
