You register the application with the Name Server using the Server Manager.

First, copy the OpenROAD Server application image to all target machines where the image is to be run. It should be put in your standard application images directory on each machine (for example, II_W4GLAPPS_DIR, II_W4GLAPPS_SYS or %II_SYSTEM%\ingres\w4glapps).

Now use the Server Manager to create one or more local Name Server registrations on each target machine. If you require automatic connection balancing to be attempted between machines, you should also set up one or more remote Name Server registrations on each target machine.

Use the Server Manager to connect, ping, bong, and view the metadata interface of your OpenROAD Server application. If the Server Manager can connect successfully, other clients with the same DCOM security authentication will also be able to connect.

For more information about using the Server Manager, see Managing and Monitoring the OpenROAD Server. For more information about DCOM configuration, see Configuring the OpenROAD Server.