6. Managing and Monitoring the OpenROAD Server : How You Can Set Up an Initialization File for the Server Manager
 
Share this page                  
How You Can Set Up an Initialization File for the Server Manager
To start the Server Manager, you must maintain a local initialization file with one entry for each Name Server net address. This file might be called the vasa.ini, although you may name the file whatever you want. The default vasa.ini file is found in %II_SYSTEM%\ingres\files. This file is necessary because:
The Server Manager gets its data from one or more Name Server processes
Each OpenROAD Server installation has one Name Server process
The Server Manager attempts to connect to the Name Server on each of the net addresses listed in the initialization file. Alternatively, you can set the environment variable VASA_FILE to hold the full pathname and file name of an initialization file alternative to the default vasa.ini. If this variable is set, the referenced file will be read when the Server Manager starts. For more information on the VASA_FILE environment variable, see the Workbench User Guide.
Note:  If DCOM has not been configured correctly locally or on a target machine, a COM error number is displayed, which must be decoded manually.
Make changes to the initialization file by doing one of the following:
Edit it with a regular text editor.
In the Server Manager, right-click the Server Neighborhood node and select Register from the context menu (to insert network addresses).
Remove network address changes by clicking the node to be removed and selecting Unregister.
A sample initialization file is shown in the following example: