Building a CORBA Server Basic Steps for Building

Building a CORBA Server

Basic Steps for Building a CORBA Server 1. Define the server's interfaces using IDL. 2. Choose an implementation approach for the server's interfaces. 3. Use the IDL compiler to generate client stubs and server skeletons for the server interfaces. 4. Implement the server interfaces. 5. Compile the server application. 6. Run the server application.

1. Defining the Server Interfaces n n n // Stock. Market. idl module Stock. Market { typedef string Stock. Symbol; typedef sequence<Stock. Symbol> Stock. Symbol. List; n n n n }; interface Stock. Server { float get. Stock. Value(in Stock. Symbol symbol); Stock. Symbol. List get. Stock. Symbols(); };

2. Choosing an Implementation Approach n Implementation by inheritance n n consists of a base class that defines the interfaces of a particular object and a separate class, inheriting from this base class, which provides the actual implementations of these interfaces Implementation by delegation n consists of a class that defines the interfaces for an object and then delegates their implementations to another class or classes.

3. Using the IDL Compiler n n Sun's Java IDL product is this: idltojava -fno-cpp -fclient -fserver Stock. Market. idl IDL Compiler generate number of files n n Helper classes Client Stub classes Server Stub classes The names of the files generated by the IDL compiler are dependent on the language mapping used and sometimes on command-line arguments passed to the IDL compiler.

Using the IDL Compiler (Cont) n For each IDL interface compiler generate a source file and header file for the client stub n a source file and header file for the server skeleton n n IDL Compiler can create separate directories for IDL module.

4. Implementing the Server Interfaces n To keep the example as simple Java is used as implementation language.

i) Using Server Skeletons n n The server skeleton, as you have learned, provides a framework upon which to build the server implementation. In Java, a server skeleton combines a set of helper classes with an interface, for providing the implementation.

n After Compilation within Stock. Market directory are a number of files containing client stub and server skeleton definitions: Stock. Symbol. Helper. java Stock. Symbol. List. Holder. java Stock. Symbol. List. Helper. java Stock. Server. Holder. java Stock. Server. Helper. java _Stock. Server. Stub. java _Stock. Server. Impl. Base. java

Stock. Server. java n n n package Stock. Market; public interface Stock. Server extends org. omg. CORBA. Object { float get. Stock. Value(String symbol); String[] get. Stock. Symbols(); }