Features Specific to OpenFusion JacORB

PrismTech has added a number of valuable features to OpenFusion JacORB that are not available in the standard Open Source JacORB distribution. These features include:

Support for client side fault tolerance mechanisms (chapter 23 of the CORBA specification).
JacORB now implements the Endorsed Standards Override Mechanism as described in http://java.sun.com/j2se/1.5.0/docs/guide/standards/index.html.
Synchronisation and deadlock fixes.
Several enhancements have been made to improve the performance of JacORB.
Portability Stubs and Skeletons have been implemented as per 4.21.6 of IDL to Java Mapping.
JacORB is tested for interoperability with OpenFusion TAO, RTOrb and e*ORB.
QoS options have been enhanced.
Memory leak improvements have been made.
The JacORB IDL compiler has been improved to make it more specification compliant.
OpenFusion IMR
The new OpenFusion Implementation Repository (IMR) is used by OpenFusion JacORB to locate and activate CORBA object implementations. The new OpenFusion IMR was designed so that it can also be used to locate object implementations based on OpenFusion TAO or OpenFusion e*ORB. The OpenFusion IMR was designed to provde a single unifying IMR that can be used across OpenFusion ORBs. However, in this initial release of the OpenFusion IMR, support will only be provided for CORBA servers written with OpenFusion JacORB. The OpenFusion IMR provides a number of advanced features including:
- Load balancing between multiple server object instances. This feature can also be used to provide basic fail over between servers objects.
- Support is provided for fail over between IMR instances. Multiple OpenFusion IMR instances can be started, if one instance fails then any OpenFusion JacORB server object references registered with the first instance will be automatically re-registered with the second OpenFusion IMR instance and client requests will continue to be processed as normal.
- Support is provided for auto-activation of server objects. Any persistent object references registered with the OpenFusion IMR can be automatically started if they are not already running when the IMR receives a client request.
- Support for fail over between IMR instances across different network subnets. (Added JacORB 2.1.3+)
Transparent corbaloc URLs
The jacorb.properties file now includes references to allow transparent corbaloc URLs for the OpenFusion CORBA Services.
JacORB ImR and OpenFusion Name and Notification Service can be installed as a RPM (RedHat Package Manager) and integrated as Unix services.
- A RPM called openfusion installs the distribution to the /opt/openfusion directory and an associated script called openfusion to the /etc/init.d directory to ensure that the services are run as Unix services on machine boot.
- A service wrapper script called serviceWrapper.sh is installed with the RPM into the /opt/openfusion/bin directory. This script is responsible for starting the JacORB ImR and OpenFusion Services, detecting multiple start attempts, configuring a timeout and detect if a Service is already running. This script takes the following options:
  - [-t <timeout>] The timeout value that the script waits for a service to start. If not specified, it defaults to 180 seconds. The timeout value should be specified in seconds.
  - -start|-stop|-status A command to start, stop or get the status of the services.
  The -t parameter is optional. The ImR, Name and Notification Services are started and stopped sequentially by the -start or -stop option.
- So, to start the services, you need to run /etc/init.d/openfusion -start (or reboot the machine) which calls onto the serviceWrapper.sh script with the -start option.If you want to configure the timeout value, edit the openfusion script to put -t <timeout> before -start.
  The openfusion script supports chkconfig and the services are active in levels 2,3,4,5. The script executes last in the boot sequence (or first when shutting down).

Top