Server Reference Guide > Server Reference Guide > D. OpenROAD Server Pooler Event Log > OpenROAD Server Configuration Management
Was this helpful?
OpenROAD Server Configuration Management
The OpenROAD Server Pooler uses the SPO Configurator component to access its configuration information. The configuration information is stored in the following locations:
Platform
Storage Location
Windows
%II_SYSTEM%\ingres\files\orserver.json
Linux and UNIX
$II_SYSTEM/ingres/files/orserver.json
The Server Manager is used to enter or modify this information. (The configuration information for the OpenROAD Server is created when the OpenROAD Server is initially installed.)
IMPORTANT!  We strongly recommend that no tool other than the Server Manager be used modify the OpenROAD server configuration repository. The following sections describe this information from this utility's perspective.
The Server Manager will look for a file named VASA.ini when it first initializes. It looks for this file in the following locations:
Platform
Storage Location
Windows
%II_SYSTEM%\ingres\files
Linux and UNIX
$II_SYSTEM/ingres/files
The typical contents of this file are as follows:
[Nameserver 1]
Location=\\machine-name
The contents of the [Nameserver 1] section tells the Server Manager that it should connect to the OpenROAD Name Server at \\machine-name. You can add additional sections to this list. The section number is incremented and the location shows a different machine name.
The OpenROAD Name Server is an OpenROAD Server application that runs in a dedicated ASO slave that an ASO client application uses to access OpenROAD application signature information. There is only one Name Server instance per machine.
Last modified date: 12/20/2023