You can use Windows Terminal Service to operate HiRDB. This capability enables you to operate HiRDB on machines in remote areas and on machines with no console. For details about Windows Terminal Service, see the operating system documentation.
Windows Terminal Service includes console sessions and virtual sessions.
When you operate an application using Windows Terminal Service, the initialization files (file extension: .INI) created under the directory for each user (for example, c:\windows\Documents and Settings\log-n user-name\Windows) may be used rather than the initialization files under the directory where the operating system is installed (for example, c:/windows).
In such a case, you need to copy the contents of the HiRDB.INI file located under the operating system installation directory into the HiRDB.INI file under the directory created for each user. However, to prevent HiRDB.INI files in different locations from affecting the execution environment of command prompts to execute operating commands, utilities, and client programs, you can set client environment definitions for the execution environment. For details about how to set client environment definitions, see the HiRDB Version 9 UAP Development Guide.
When Windows Terminal Server is used, even though the server console is not in login status, the client side window may still run in login status. To avoid this, you must do the following in the server or client:
When Windows Terminal Service is used, there are limitations that apply to using the system switchover facility in Windows Server 2003 (IPF). The following table lists the items supported in the Windows Server 2003 (IPF) system switchover facility when Windows Terminal Service is used.
Table 1-2 Items supported in the Windows Server 2003 (IPF) system switchover facility when Windows Terminal Service is used
Type | Support | ||
---|---|---|---|
System switchover facility | Monitor mode | Y | |
Server mode#1 | Console session | Y | |
Virtual session | --#2 |