Configuration Settings |
Virtual Machine |
Several configuration settings can be used for PROIV. These configurations can, in general, be divided into three groups:
Kernel options - There are many kernel options, due to the large number of environments and options the kernel supports.
PROISAM File System options - These options are set using the PROIV Task Manager GUI tool. They typically are never changed, unless you are running with a large number of users under the NT Server kernel (more than 64), or require more than 200 PROISAM files open simultaneously.
GUI Client options - These are all typically set using the Client menu options.
The kernel options can be divided into several groups:
- General Environment settings, which you define in the [Environment] section of the INI file.
- File system settings, which you define in the [Environment] or [database DEFAULT] sections of the INI file.
- Database settings, which you define in the [database SQLDEFAULT] or [database <area name>] sections of the INI file.
- Printer mapping assignments, which you define in the [Print Font,LP0] through [Print Font,LP9] sections. Typically set by using the PROIV Task Manager GUI tool.
- Product Licensing information, which you define [Serial – 4.0] and [Serial Info – 4.0] sections. Typically set by using the PROIV Licensing tool (normally run automatically at installation).
The GUI Client options can also be further split into:
- General settings
- Printer mapping assignments
In general, options may be set globally (using the same value for all the PROIV environments on a machine), or may be set on a per-connection basis. Therefore, for the kernel, there is a Global INI file and one or more Local INI files. Similarly, for the Client there is a Global INI file, and one or more Local PIV files. The kernel/Client looks in the local INI/PIV file first for an option, and if it is not found there, it looks in the global INI file.
For some settings, this may be further refined. For example, the SQL database settings have options global to all SQL databases, as well as per-database-area options. Both of these are definable in both of the above kernel INI files, giving a total of four locations the kernel searches for a database option.
Topic ID: 750008