Explore topic-wise InterviewSolutions in .

To get all the Orbix configuration for a domain, run the following command:

• it ADMIN config DUMP
• This will WORK in both CFR and file based domains.

The output will look SOMETHING LIKE:

• plugins:it_arm_interceptors:shlib_name = "it_arm_interceptors"
• plugins:itrp:shlib_name = "it_itrp"
• plugins:itrp:live_time = "2"
• plugins:it_mbean_monitoring:shlib_name = "it_mbean_monitoring"
• plugins:it_mbean_monitoring:ClassName = "com.iona.management.logging.mbean_monitoring.MBeanMonitoringPlugIn"
• plugins:basic_codeset:shlib_name = "it_basic_codeset"
• plugins:basic_codeset:ClassName = "com.iona.corba.codeset.BasicCodeSetPlugIn"
• plugins:iiop_tls:ClassName = "com.iona.corba.iiop.tls.IIOPTLSPlugIn"
• plugins:iiop_tls:shlib_name = "it_iiop_tls"

To get all the Orbix configuration for a domain, run the following command:

The output will look something like:

Orbix 5 and Orbix 6 is designed to write multi-threaded (and single threaded) application from the ground up.

However, the FOLLOWING describes in more details about Orbix thread safety:

• All Orbix library public APIs are thread safe.
• Per CORBA specification, add_ref/remove_ref OPERATIONS in the idl generated CODE is thread safe.
• Regarding the REST of the generated code, Orbix IDL -> C++ code generator generates mappings for user-defined IDL types, as well as client-side proxy invocation code (-base SWITCH) and server-side servant dispatch code (-poa switch). The client-side invocation code and server-side dispatch code are thread-safe. The mappings generated for user-defined IDL types are not thread safe for concurrent modification but are thread-safe for concurrent reads.

Orbix 5 and Orbix 6 is designed to write multi-threaded (and single threaded) application from the ground up.

However, the following describes in more details about Orbix thread safety:

Yes, the port of the Orbix Notification service can be changed easily during the Orbix domain DEPLOYMENT process. Running itconfigure in expert mode allows you to change the IIOP port of the Orbix Notification Service. For further information please see the CHAPTER "CREATING a Domain in Expert Mode" in the Orbix Deployment Guide and the chapter "MANAGING the Notification Service" in the Enterprise MESSAGING Guide.

Yes, the port of the Orbix Notification service can be changed easily during the Orbix domain deployment process. Running itconfigure in expert mode allows you to change the IIOP port of the Orbix Notification Service. For further information please see the chapter "Creating a Domain in Expert Mode" in the Orbix Deployment Guide and the chapter "Managing the Notification Service" in the Enterprise Messaging Guide.

OAccessing the local address on the client-side, e.g. in an interceptor can be ACHIEVED by using the following CODE:

CORBA::Object_var obj = orb->resolve_initial_references("IT_IPTransport");
if (CORBA::is_nil(obj))
{
self_addr = (const char*) 0;
RETURN;
}
IT_ATLI2_IP::IPTransport_ptr ip_transport = IT_ATLI2_IP::IPTransport::_narrow(obj);
if (CORBA::is_nil(ip_transport))
{
self_addr = (const char*) 0;
return;
}
CORBA::String_var HOSTNAME = ip_transport->local_node_name();
IT_ATLI2_IP::IPAddressSeq_var ip_addresses =
ip_transport->name_to_addresses(
hostname,
0,
IT_ATLI2_IP::PROTOCOL_TCP,
IT_UtcT::NEVER()
);
IT_ATLI2_IP::IPAddress_var ip_address = ip_addresses[0];
self_addr = ip_address->node_literal();

OAccessing the local address on the client-side, e.g. in an interceptor can be achieved by using the following code:

CORBA::Object_var obj = orb->resolve_initial_references("IT_IPTransport");
if (CORBA::is_nil(obj))
{
self_addr = (const char*) 0;
return;
}
IT_ATLI2_IP::IPTransport_ptr ip_transport = IT_ATLI2_IP::IPTransport::_narrow(obj);
if (CORBA::is_nil(ip_transport))
{
self_addr = (const char*) 0;
return;
}
CORBA::String_var hostname = ip_transport->local_node_name();
IT_ATLI2_IP::IPAddressSeq_var ip_addresses =
ip_transport->name_to_addresses(
hostname,
0,
IT_ATLI2_IP::PROTOCOL_TCP,
IT_UtcT::never()
);
IT_ATLI2_IP::IPAddress_var ip_address = ip_addresses[0];
self_addr = ip_address->node_literal();

As SUN's ORB RUNTIME cannot be used with Orbix APPLICATIONS, configure the JDK to use the Orbix ORB runtime instead by setting system properties org.omg.CORBA.ORBClass and org.omg.CORBA.ORBSingletonClass to the APPROPRIATE values.

As SUN's ORB runtime cannot be used with Orbix applications, configure the JDK to use the Orbix ORB runtime instead by setting system properties org.omg.CORBA.ORBClass and org.omg.CORBA.ORBSingletonClass to the appropriate values.

As SUN's ORB runtime cannot be USED with ORBIX applications, CONFIGURE the JDK to use the Orbix ORB runtime instead by setting system properties org.omg.CORBA.ORBClass and org.omg.CORBA.ORBSingletonClass to the appropriate values.

As SUN's ORB runtime cannot be used with Orbix applications, configure the JDK to use the Orbix ORB runtime instead by setting system properties org.omg.CORBA.ORBClass and org.omg.CORBA.ORBSingletonClass to the appropriate values.

The ORB properties can be SET in ONE of the FOLLOWING ways:

1. Using the iona.properties FILE
2. Using Java interpreter arguments

The ORB properties can be set in one of the following ways:

Clients can locate CORBA OBJECTS through the OrbixNames, which is Orbix's IMPLEMENTATION of the CORBA Naming SERVICE. 

"OrbixNames allows you to set up groups of objects that can provide particular services to a client. When a client requests an object from a group, OrbixNames selects an object using a RANDOM or a round-robin load-balancing algorithm. You choose the algorithm associated with each group".

Clients can locate CORBA objects through the OrbixNames, which is Orbix's implementation of the CORBA Naming Service. 

"OrbixNames allows you to set up groups of objects that can provide particular services to a client. When a client requests an object from a group, OrbixNames selects an object using a random or a round-robin load-balancing algorithm. You choose the algorithm associated with each group".

ORBIX 6.3 has not been TESTED to run with JAVA APPLETS and is unsupported.

Orbix 6.3 has not been tested to run with Java Applets and is unsupported.

Orbix 3 and LATER versions of Orbix (such as Orbix 6) have "on the wire" COMPATIBILITY. Orbix 3 uses IIOP (Internet Inter-Orb Protocol) as it's default protocol. Hence an Orbix 3 CLIENT can speak to an Orbix 6 server and vice-versa.

Orbix 3 and later versions of Orbix (such as Orbix 6) have "on the wire" compatibility. Orbix 3 uses IIOP (Internet Inter-Orb Protocol) as it's default protocol. Hence an Orbix 3 client can speak to an Orbix 6 server and vice-versa.

By default IORs will contain the hostname of a MACHINE. Using such an IOR will succeed without any problems SINCE a hostname lookup will return the new IP address.

Ensure IORs of the CFR, Locator, etc. contain hostnames rather then IP addresses. Use the iordump TOOL shipped with Orbix in order to inspect the hostname/port contained in the IOR.

By default IORs will contain the hostname of a machine. Using such an IOR will succeed without any problems since a hostname lookup will return the new IP address.

Ensure IORs of the CFR, Locator, etc. contain hostnames rather then IP addresses. Use the iordump tool shipped with Orbix in order to inspect the hostname/port contained in the IOR.

These SETTINGS apply to each Orbix process for which these settings have been CONFIGURED and not to the sum of Orbix processes running in an Orbix domain.

If these settings have been configured in the GLOBAL CONFIGURATION scope then these settings will apply to each process started in your Orbix domain.

These settings apply to each Orbix process for which these settings have been configured and not to the sum of Orbix processes running in an Orbix domain.

If these settings have been configured in the global configuration scope then these settings will apply to each process started in your Orbix domain.

It is not possible to CAPTURE SSL HANDSHAKING errors programatically in Orbix as this is HANDLED by the SSL toolkit and will fail before the connection is established and Orbix begins to pass the request through the interceptors in the binding list.

It is not possible to capture SSL handshaking errors programatically in Orbix as this is handled by the SSL toolkit and will fail before the connection is established and Orbix begins to pass the request through the interceptors in the binding list.

CURRENTLY ORBIX 3 (release 3.3.10) is not SUPPORTED on any virtualization PLATFORMS.

Currently Orbix 3 (release 3.3.10) is not supported on any virtualization platforms.

Orbix 6.3.6 is the FIRST Service Pack of Orbix to include SUPPORT for Java 7. Support for Java 7 is provided for Orbix 3.3.12 in Q2 2013.

Orbix 6.3.6 is the first Service Pack of Orbix to include support for Java 7. Support for Java 7 is provided for Orbix 3.3.12 in Q2 2013.

Because Orbix 6 has no equivalent to the Orbix 3 I/O Callback FUNCTIONALITY, you MUST migrate any CODE that USES it. Orbix 6 does not allow access to TCP/IP sockets or transport-level INFORMATION, this is not compatible with the Orbix 6 architecture.

Because Orbix 6 has no equivalent to the Orbix 3 I/O Callback functionality, you must migrate any code that uses it. Orbix 6 does not allow access to TCP/IP sockets or transport-level information, this is not compatible with the Orbix 6 architecture.

Orbix does not provide any tools to remove empty or surplus empty lines from an Orbix CONFIGURATION file.

Using a text EDITOR for example Notepad++ (http://notepad-plus-plus.org/) with the TextFX PLUGIN installed (Plugins->Plugin MANAGER->Show Plugin Manager and install TextFX plugin), you can simply load the configuration file, mark all text (Ctrl+A), then select menu TextFX->TextFX EDIT->Delete Surplus Blank Lines.

This removes all surplus empty lines.

Orbix does not provide any tools to remove empty or surplus empty lines from an Orbix configuration file.

Using a text editor for example Notepad++ (http://notepad-plus-plus.org/) with the TextFX plugin installed (Plugins->Plugin Manager->Show Plugin Manager and install TextFX plugin), you can simply load the configuration file, mark all text (Ctrl+A), then select menu TextFX->TextFX Edit->Delete Surplus Blank Lines.

This removes all surplus empty lines.

Orbix does not impose a SIZE limit on the MESSAGES sent from Client to Server. The size of the MESSAGE is influenced by how the application has defined the message in the Interface Definition LANGUAGE (IDL) used by the server and client.

Orbix does not impose a size limit on the messages sent from Client to Server. The size of the message is influenced by how the application has defined the message in the Interface Definition Language (IDL) used by the server and client.

An EVENT service SUPPLIER PROGRAM performs the following actions:

1. Instantiates suppliers using the appropriate INTERFACE in module CosEventComm
2. Connects suppliers to the event channel
3. Sends event messages to the event channe
4. Disconnects from the event channel

An event service supplier program performs the following actions:

Orbix WEB SERVICES does not INCLUDE locator functionality for web services ENDPOINTS.

Orbix Web Services does not include locator functionality for web services endpoints.

Any VERSIONS of ORBIX do not SUPPORT ORACLE JRockit Java Virtual Machine.

Any versions of Orbix do not support Oracle JRockit Java Virtual Machine.

Product downloads are AVAILABLE through the Micro FOCUS EPD (Electronic Product DELIVERY) portal.

Product downloads are available through the Micro Focus EPD (Electronic Product Delivery) portal.

The VARIABLE that SETS the TIMEOUT ORBIX CONFIG is:

relative_roundtrip_timeout

The variable that sets the timeout Orbix config is:

relative_roundtrip_timeout

Orbix 3 clients do not automatically close the CONNECTION to the Orbix daemon. These connections need to be closed EXPLICITLY.

Orbix 3 JAVA provides the IT_KEEP_ALIVE_FORWARDER_CONNECTION configuration variable which can be set to FALSE in order to close the connection to the Orbix daemon.

Orbix 3 clients do not automatically close the connection to the Orbix daemon. These connections need to be closed explicitly.

Orbix 3 Java provides the IT_KEEP_ALIVE_FORWARDER_CONNECTION configuration variable which can be set to false in order to close the connection to the Orbix daemon.

Orbix can be instructed to publish corbaloc style references INSTEAD of IORs for the Orbix SERVICES through the "-corbalocs TRUE" switch to the itconfigure command line TOOL when configuring an Orbix domain.

When using the itconfigure GUI ensure to check the "Use Corbalocs" check-box in the itconfigure GUI. This setting is only available in the "Domain Details" step when running the itconfigure GUI tool in EXPERT mode (File->New->Expert).

Orbix can be instructed to publish corbaloc style references instead of IORs for the Orbix services through the "-corbalocs true" switch to the itconfigure command line tool when configuring an Orbix domain.

When using the itconfigure GUI ensure to check the "Use Corbalocs" check-box in the itconfigure GUI. This setting is only available in the "Domain Details" step when running the itconfigure GUI tool in expert mode (File->New->Expert).

When running itconfigure and CREATING the Orbix domain in non-GUI mode use the "-hostnamePolicy" PARAMETER to specify the address mode POLICY for IORs.

The hostnamePolicy value can be one of the following:

ip (IP addresses)
localhost ('localhost'),
localhost_ip ('127.0.0.1'),
long (fully qualified hostname),
short (unqualified hostname-the default).

When running itconfigure and creating the Orbix domain in GUI mode use the "Address Mode Policy for Object References" setting in the first step (Domain Defaults) of itconfigure one of the above values can be selected.

Use the hostnamePolicy "long" for GENERATING fully qualified hostnames in IORs.

When running itconfigure and creating the Orbix domain in non-GUI mode use the "-hostnamePolicy" parameter to specify the address mode policy for IORs.

The hostnamePolicy value can be one of the following:

ip (IP addresses)
localhost ('localhost'),
localhost_ip ('127.0.0.1'),
long (fully qualified hostname),
short (unqualified hostname-the default).

When running itconfigure and creating the Orbix domain in GUI mode use the "Address Mode Policy for Object References" setting in the first step (Domain Defaults) of itconfigure one of the above values can be selected.

Use the hostnamePolicy "long" for generating fully qualified hostnames in IORs.

When configuring the ORBIX domain provide the "-multihome" switch to itconfigure command FOLLOWED by the DNS NETWORK alias of the hostname,

e.g:

it configure -multihome <network alias hostname&GT;

The IORs generated for the Orbix services configured in the Orbix domain will contain the "network alias hostname" rather than the physical hostname.

When configuring the Orbix domain provide the "-multihome" switch to itconfigure command followed by the DNS network alias of the hostname,

e.g:

it configure -multihome <network alias hostname>

The IORs generated for the Orbix services configured in the Orbix domain will contain the "network alias hostname" rather than the physical hostname.

ORBIX 3.3 uses a license code, not a license file. 

There are three product sets for Orbix 3.3, each with it's own license code: Java, C++, or OTS. 

The licenses codes have the form: 00000000-11111111-22222222-33333333-44444444

When PROMPTED, provide the codes to the installer. 

If licensed Orbix commands like idl or orbixd fail to RUN, the license MAY have been entered incorrectly. 

To reinstall a license code after the initial installation is completed, run:

UNIX: Install_license <app> <license code>

WINDOWS: License.exe <app> <license code>

Orbix 3.3 uses a license code, not a license file. 

There are three product sets for Orbix 3.3, each with it's own license code: Java, C++, or OTS. 

The licenses codes have the form: 00000000-11111111-22222222-33333333-44444444

When prompted, provide the codes to the installer. 

If licensed Orbix commands like idl or orbixd fail to run, the license may have been entered incorrectly. 

To reinstall a license code after the initial installation is completed, run:

UNIX: Install_license <app> <license code>

Windows: License.exe <app> <license code>

Orbix logging is configured through the event_log filters. These sequences of variables set the logging level for each of Orbix's subsystem. For example, the following configures the IT_POA subsystem to display only error MESSAGES:

event_log:filters = ["IT_POA=ERROR"];

Similarly, the following SETS the IT_POA subsystem to display only error messages and also the IT_PSS_DB subsystem to display only warning, error and FATAL messages:

event_log:filters = ["IT_POA=ERROR", "IT_PSS_DB=WARN+ERROR+FATAL"];

An asterisk can be used as a WILDCARD character, either to SPECIFY all subsystems, or all message levels. For example, the following configures the IT_POA subsystem to display all messages:

event_log:filters = ["IT_POA=*"];

Similarly, the following configures all subsystems to display all messages:

event_log:filters = ["*=*"];

If unconfigured, a subsystem will display no messages.

Orbix logging is configured through the event_log filters. These sequences of variables set the logging level for each of Orbix's subsystem. For example, the following configures the IT_POA subsystem to display only error messages:

event_log:filters = ["IT_POA=ERROR"];

Similarly, the following sets the IT_POA subsystem to display only error messages and also the IT_PSS_DB subsystem to display only warning, error and fatal messages:

event_log:filters = ["IT_POA=ERROR", "IT_PSS_DB=WARN+ERROR+FATAL"];

An asterisk can be used as a wildcard character, either to specify all subsystems, or all message levels. For example, the following configures the IT_POA subsystem to display all messages:

event_log:filters = ["IT_POA=*"];

Similarly, the following configures all subsystems to display all messages:

event_log:filters = ["*=*"];

If unconfigured, a subsystem will display no messages.

The itconfigure utility uses Log4J logging. This is configured in the properties file:

<ORBIX_INSTALL_DIR>asp6.3 emplatesetclog4jlog4j.properties.

To configure DEBUG logging level, change the first LINE of the properties file from:

log4j.rootLogger=ERROR, A1
to
log4j.rootLogger=DEBUG, A1

The above change writes debug logging to the console. The logging OUTPUT can be redirected to a file by adding the following lines to the log4j.properties file:

logDir = C:/temp
log4j.appender.A1.File=${logDir}/itconfigure.log

The itconfigure utility uses Log4J logging. This is configured in the properties file:

<ORBIX_INSTALL_DIR>asp6.3 emplatesetclog4jlog4j.properties.

To configure debug logging level, change the first line of the properties file from:

log4j.rootLogger=ERROR, A1
to
log4j.rootLogger=DEBUG, A1

The above change writes debug logging to the console. The logging output can be redirected to a file by adding the following lines to the log4j.properties file:

logDir = C:/temp
log4j.appender.A1.File=${logDir}/itconfigure.log

ORBIX provides the following configuration SETTINGS to limit the number of connections to and from a service:

• PLUGINS:IIOP:incoming_connections:soft_limit
• plugins:iiop:incoming_connections:hard_limit
• plugins:iiop:outgoing_connections:soft_limit
• plugins:iiop:outgoing_connections:hard_limit

Orbix provides the following configuration settings to limit the number of connections to and from a service:

The Orbix Connect RESOURCE adapter is packaged as a standard J2EE Connector Architecture resource adapter archive (RAR) file, corbaconn.rar. The corbaconn.rar file contains all the CLASSES and resources that Orbix Connect needs to manage the connections between J2EE APPLICATIONS and CORBA systems. CORBA capabilities are embedded within this RAR file and include a fully functional, pre-configured standalone client instance of Orbix, IONA's market-leading ORB.

The Orbix Connect resource adapter is packaged as a standard J2EE Connector Architecture resource adapter archive (RAR) file, corbaconn.rar. The corbaconn.rar file contains all the classes and resources that Orbix Connect needs to manage the connections between J2EE applications and CORBA systems. CORBA capabilities are embedded within this RAR file and include a fully functional, pre-configured standalone client instance of Orbix, IONA's market-leading ORB.

Orbix is a CORBA ORB (Object RESOURCE Broker) - a commercial software product which helps programmers build DISTRIBUTED APPLICATIONS. Orbix is an implementation of the OMG's (Object Management Group) CORBA SPECIFICATION.

Orbix is a CORBA ORB (Object Resource Broker) - a commercial software product which helps programmers build distributed applications. Orbix is an implementation of the OMG's (Object Management Group) CORBA Specification.