Solstice Enterprise Manager 4.1 Developing CORBA Applications | ![]() ![]() ![]() ![]() ![]() |
Interoperating SEM CORBA Gateway
The SEM CORBA Gateway consists of a set of CORBA objects built as per the JIDM standards. These objects can be built and deployed to meet your requirements depending on the ORB that you have installed. It is also possible to implement these objects on one ORB and develop the client applications on another ORB and communicate with Solstice Enterprise Manager (Solstice EM) in a seamless way. This chapter describes the issues of interoperability.
This chapter describes the following topics:
- Section 8.1 Background on Interoperability
- Section 8.2 ORBs for Developing Client/Manager Applications
- Section 8.3 Implementing Client Applications on Other ORBs
8.1 Background on Interoperability
Interoperability in terms of CORBA standards is defined as "the ability of a client on ORB A to invoke an OMG IDL-defined operation on an object on ORB B, where ORB A and ORB B have been independently developed by the same vendor or by different vendors."
Interoperability as applicable to SEM CORBA Gateway is defined as "the ability of a manager application developed on any SEM CORBA ToolKit supported ORB to be able to interact with SEM CORBA Gateway interfaces developed on any SEM CORBA ToolKit supported ORB and carry out all the Solstice EM supported functions on any of the managed objects transparently."
Interoperability to a large extent is ensured by IIOP, which is a mandatory OMG requirement for all ORB vendors. All products that are compliant with CORBA 2.0 standards must implement IIOP as a standard communication protocol.
Some of the ORBs that are commercially available for developing client applications are listed in the following sections. Steps to follow when developing manager applications are also discussed.
8.2 ORBs for Developing Client/Manager Applications
The SEM CORBA ToolKit currently supports the following ORBs:
- VisiBroker 4.5
- Orbacus 4.0.5
- Orbix 2000 1.2.1
Any of these ORBs can be used for developing client/manager applications.
8.3 Implementing Client Applications on Other ORBs
If you wish to develop and implement client applications using other ORBs, which are not supported by the SEM CORBA ToolKit, perform the following steps1:
1. Create a template file for the ORB.
- For example, if you are building applications for HP Orb Plus, you can create a template file hp.tmpl. The template file defines the various parameters and flags required for IDL to CPP/Java compilation.
- The .tmpl file already exists for the ORB chosen at the time of SEM CORBA ToolKit installation. You can use this .tmpl file as reference while creating the .tmpl file for the current ORB.
2. Create Makefiles for the ORB in the following IDL directories:
- jidm
- auth_proxy
- jidm_ext
- event_gw
- metadata_gw
- cos
- The Makefile already exists for the ORB chosen at the time of SEM CORBA ToolKit installation. You can use this Makefile as reference while creating the Makefile file for the current ORB.
- While creating Makefiles, make sure that the header files, source files and the libraries are installed in the required directories.
Note The template file created in Step1 is included in the Makefile created in Step2.
3. Execute the Makefiles individually in the directories mentioned in Step2 by using the following command:
dmake <makefile-name-for-the-orb> install1 It is assumed here that the client applications are to be written using C++.
- This step will create the C++ and header files; build the libraries and install them in the required directories.
- After creation and installation of the header files (.hh) and shared libraries; include the header files in your client applications; compile and link the header files to the shared libraries to build applications.
Sun Microsystems, Inc. Copyright information. All rights reserved. |
Doc Set | Contents | Previous | Next | Index |