[Erlang Systems]

1 Installing Orber

1.1 Introduction

The Orber application is an Erlang implementation of the OMG CORBA 2.0 environment. The parts which are implemneted are compliant to 2.0.

1.2 Installation

Before you can install Orber you must have created a mnesia schema for the erlang nodes where you want to run Orber.

This can be done with mnesia:create_schema(NodeList). where NodeList is a list with the names of the erlang nodes.

Next step is to install Orber itself, which will create som new mnesia tables and load some of them with data. The installation behaves a bit different depending on if mnesia is running in the erlang node or not.

Functions to choose from are:

Example of a one node installation where mnesia is not running:

      1> mnesia:create_schema([]).
      2> orber:install([]).
    

Example of a multi node installation (see chapter below regarding multi node installations) where mnesia already is running:

      1> orber:install([a@machine1, b@machine2]).
    

1.2.1 Multi node installation

There are one extra step when a multi node domain is installed. You must start mnesia on the other erlang nodes after the schema is created but before Orber's installation function is run on the first node.

1.2.2 Running java clients agianst Orber.

If you intend to run java clients, <OTP_INSTALLPATH>/lib/orber-<current-version>/priv must be added to your CLASSPATH variable to get the orber support for initial references.

1.3 Configuration

The following configurations are possible:

IIOP communication is just used between to Orber instances if they are in different domains so if one want to have IIOP communication between Orber installations the domain name must be set to different values.

IIOP communication is just used between to Orber instances if they are in different domains so if one want to have IIOP communication between Orber installations the domain name must be set to different values.

Theses settings can be changed with a configuration file, see config(4), which can be given to the erl command with the -config flag. One can also send the values separately as options to the erlang node when it is started, see erl(1).

1.4 Contents of the Orber application

The orber release contains the following parts:

1.4.1 Orb kernel and IIOP support

There is an ORB kernel with IIOP support which allows creating persistent server objects in erlang and access them from erlang and java. For the moment one need a java enabled Orb to generate java from idl and use java server objects (we have tested with OrbixWeb).

1.4.2 Interface Repository

The IFR is an interface repository built on the Mnesia application. Orber is using the IFR for some typechecking when coding/decoding IIOP. The IFR is capable of storing all interfaces and declarations of OMG IDL.

1.4.3 CosNaming Service

Orber contains a CosNaming compliant service.

1.4.4 CosEvent Service

Orber contains an Event Service taht is compliant with the untyped part of the CosEvent service.

1.4.5 Resolving initial reference from Java

A class with just one method which returns an IOR on the external string format to the INIT object (see "Interoperable Naming Service" specification).

1.4.6 Resolving initial reference from C++

A class (and header file) with just one method which returns an IOR on the external string format to the INIT object (see "Interoperable Naming Service" specification).

1.4.7 A small example

A small programming example is contributed which shows how Orber can be used. It is an implementation of a Stack service which shows how erlang services can be accessed from both erlang and java.


Copyright © 1991-98 Ericsson Telecom AB