Creating a Runtime Configuration File for the Remote Server Component

Because at least some application logic executes on the server, you may want to create a runtime configuration file for the remote server component of your application. If you create this file, you will install it on the server machine along with the remote application component. This file defines how the remote application should behave at run time.

To tell AcuConnect where to find this file in a distributed processing environment, you must specify its full path using the ACUCONNECT_RUNTIME_FLAGS variable in the client configuration file, client.cfg.

Because the remote application is run using an ACUCOBOL-GT runtime, you can use any runtime configuration file variable described in the ACUCOBOL-GT User's Guide. The following variables are significant for the distributed processing environment:

Runtime configuration files have a similar function in a thin client environment. The file is stored on the server along with the application, and its name is specified in a server alias file that you establish when first setting up the system. See Creating a Server Alias File in Thin Client for more information.

In addition to the variables in the previous table, the following variables are important for a thin client environment: