Interoperability

• To bootstrap to a remote object which may run on a different vendor's ORB.
• To disable VisiBrokers osagent directory service.
• Use the -DORBInitRef property and the URL-style addressing as defines in chapter 3 of the Interoperable Naming Service specification.

• Bank.idl

IDL interface for the Bank.

• Server.java

Bank server. Creates a POA named MyPOA, creates an instance of the AccountManager servant and activates that servant on the MyPOA. Then associates a name with the AccountManager IOR in the root
context of the Naming Service. It then starts waiting for client requests.
• AccountImpl.java

Account servant implementation. Implements the balance() method.
• AccountManagerImpl.java

Account Manager servant Implementation. Implements open() method. Checks in a table to see if there is already an Account for the specified user. If not, creates an account with random balance. Returns the created account.
• Client.java

This is the Bank client. Obtains the IOR of the AccountManager by resolving with the name associated with it in the root context of the Naming Service. Then  invokes open() to open a bank account. It then invokes balance() on the Account object reference obtained to query the balance.
• Makefile Used to build all the test targets.

Building this example

• Server.class
• Client.class

Running the examples

Starting the NameService

vbroker.agent.enableLocator=false This property tells the ORB to skip looking for an osagent, thus improving startup time when no osagent is listening on the given port.

vbroker.se.default=iiop_tp We set the threading model to ThreadPool.

vbroker.se.iiop_tp.scm.iiop_tp.listener.port=9999 We want the ThreadPool server engine to listen on port 9999.

The Naming Service needs to be activated first. It can be done with the following command:

    prompt> nameserv -VBJprop ORBpropStorage=ns.properties >ns.ior &

This will startup the NameService with the default backing store InMemory and the default name "NameService". The IOR will be captured in the file ns.ior for later use.

Alternatively, you can start any other NameService, e.g. the tnameserv executable that comes with JDK 1.2. Please note that you can use corbaploc and corbaname scheme only with a NameService that fully implements the INS specification (orbos/98-10-11 or newer)!
You would start the jdk 1.2 NameService as follows. It will print out its IOR, which you will have to copy in a file named ns.ior

    prompt> tnameserv -ORBInitialPort 9999 &
 

Starting the Server

Then start the bank server using the command:

prompt> vbj -Dvbroker.agent.enableLocator=false -DORBInitRef=NameService=corbaloc::localhost:9999/NameService Server& 

Starting a client

The server started so far behave from the client point of view like CORBA objects implemented on top of other vendor's ORB, in particular, we cannot use the XXXHelper.bind() call to locate an object. Instead, we will use resolve_initial_references in conjunction with -DORBInitRef to point the client to the NameService, which contains all other objects.

The first example will specify the location of the NameService by passing in an IOR.

prompt> vbj -DORBInitRef=NameService=`cat ns.ior` Client

The second example will specify the location of the NameService by pointing to the host and port number, on which the NameService is listening. Please note that the object key "NameService" has to be used regardless of which name we give the NameService instance on the commandline.

prompt> vbj -DORBInitRef=NameService=corbaloc::localhost:9999/NameService Client

The third example will specify the location of the NameService by pointing to the host and port number, on which the NameService is listening and a stringified name with which the object is registered. Since the server registered on the root context, this name is only the slash.

prompt> vbj -DORBInitRef=NameService=corbaname::localhost:9999/ Client

All previous protocols (IOR, corbaloc, corbaname) are mandatory, according to the INS specification. VisiBroker also implements the optional protocols "file://", "http:", and "ftp:", to obtain an IOR. Their use is presented in the following three examples.

The first example will specify the location of the NameService by pointing to a file containing an IOR.

prompt> vbj -DORBInitRef=NameService=file:ns.ior Client

The second example will specify the location of the NameService by pointing to a file on a webserver containing an IOR. You will have to copy the ns.ior file to a webserver to try this example.

prompt> vbj -DORBInitRef=NameService=http://<your location>/ns.ior Client

The third example will specify the location of the NameService by pointing to a file on a ftp server containing an IOR.  You will have to copy the ns.ior file to the ftp server to try this example.

prompt> vbj -DORBInitRef=NameService=ftp://<your location>/ns.ior Client

---