It is assumed here that the current directory is $ {ILSHOME}/demo/network1. Of course, you can start the object server from any other directory provided that you specify the correct path.

Before executing the object server, you must start the logical mapper, tcpd, from the host where the server process will be running. The logical mapper is provided with the Rogue Wave® Server standard distribution.

For example, to start the logical mapper on a Solaris system, type:

Once the logical mapper is running, you can start the Network object server by typing the following command:

For details about the -ilsn option, see Executing the Server Main Loop.

A message appears to indicate that the Network server is ready.

Once the object server is running, you can launch the Rogue Wave Server Studio environment to dynamically define views. Chapter 8 explains step-by-step how to define views at runtime.

You might also want to load predefined views while starting the object server. In this case, you must start the Network object server with the following command:

For details about the -ilsr option, see Executing the Server Main Loop.

The file network.ls is a resource file that contains .ilv files. These files are parsed during the initialization phase. The environment variable ILSPATH is used by the server to locate these files.

Starting the Network server that way, you can open existing views from swcomp, a predefined application component supplied with Rogue Wave Server. See Running the swcomp Demonstration for details.