40.4 Starting IceBox

Incorporating everything we discussed in the previous sections, we can now configure and start IceBox servers.

40.4.1 Starting the C++ Server

The configuration file for our example C++ service is shown below:

IceBox.Service.Hello=HelloService:create
Hello.Endpoints=tcp ‑p 10001

Notice that we define an endpoint for the object adapter created by the Hello service.

Assuming these properties reside in a configuration file named config, we can start the C++ IceBox server as follows:

$ icebox ‑‑Ice.Config=config

Additional command line options are supported, including those that allow the server to run as a Windows service or Unix daemon. See Section 8.3.2 for more information.

40.4.2 Starting the Java Server

Our Java configuration is nearly identical to the C++ version, except for the entry point specification:

IceBox.Service.Hello=HelloServiceI
Hello.Endpoints=tcp ‑p 10001

Notice that we define an endpoint for the object adapter created by the Hello service.

Assuming these properties reside in a configuration file named config, we can start the Java IceBox server as follows:

$ java IceBox.Server ‑‑Ice.Config=config

40.4.3 Starting the C# Server

The configuration file for our example C# service is shown below:

IceBox.Service.Hello=helloservice.dll:HelloService
Hello.Endpoints=tcp ‑p 10001

Notice that we define an endpoint for the object adapter created by the Hello service.

Assuming these properties reside in a configuration file named config, we can start the C# IceBox server as follows:

$ iceboxnet ‑‑Ice.Config=config

40.4.4 Initialization Failure

At startup, an IceBox server inspects its configuration for all properties having the prefix IceBox.Service. and initializes each service. If initialization fails for a service, the IceBox server invokes the stop operation on any initialized services, reports an error, and terminates.