A client configuration provides settings that define a client and how it should operate in the network. Each configuration includes settings for:
The Software AG Directory Server that should be used by the client in its attempts to work with Adabas databases.
The databases that should be included or excluded for use by the client.
Specific database access definitions for the client, including any additional access parameters that should be used.
XTS (communication service) and ADALNK trace levels used for the client.
Any user exit used for the client.
These client configuration settings are stored in an Entire Net-Work Client configuration file. When you first install Entire Net-Work Client, a default client (named "default") is already defined and can be maintained. When a client is added to the System Management Hub (SMH), a new Entire Net-Work Client configuration file is created to contain the settings for that client. When a client is deleted from SMH, its associated Entire Net-Work Client configuration file is also deleted.
By default, all client configuration files are stored in one of the following locations:
In Windows XP environments (up to XP Server 2003): Documents and
Settings\All Users\Application Data\Software AG\Entire Net-Work
Client\
In Windows Vista environments: ProgramData\Software AG\Entire
Net-Work Client\
In UNIX environments: $SAG\wcl\.
However, you can elect to store a client configuration file in a different location by specifying the location when you create the client configuration. For more information, read Adding Client Configurations. Once the configuration is created, you cannot change the path; you must delete and recreate the client configuration to do so.
Client configurations cannot be stored on a server; they can only be stored on the local machine. If you want to share a client configuration with multiple clients, define it in a directory on the local machine and then share that directory with the other clients, being sure to specify the path to the client configuration when you identify the client configuration to your application. For more information, read Identifying the Client Configuration to Your Application .
In general, the filenames of Entire Net-Work Client configuration files are the same as the name of the client you specify when you add the client in SMH. For example, a client named "TEST" will create a configuration file also named "TEST".
Note:
We do not recommend that you maintain client configuration files using
a text editor. Instead, we recommend that you use SMH to perform all
maintenance to Entire Net-Work Clients and their configuration files.
You can also use Directory Server configuration settings to define how a client should operate in the network. Directory Server configuration settings affect all clients that use the Directory Server Entire Net-Work Client configuration settings only affect the individual client. Entire Net-Work Client configurations can be very useful, therefore, if you want to test a configuration before publishing it for additional clients in the Directory Server.
For example, you might use the following procedure to test a configuration prior to publishing it in the Directory Server:
Test the Entire Net-Work Client configuration settings against a copy of an Adabas database on a local machine.
Once these first tests run correctly, you might then test the Entire Net-Work Client configuration settings against the actual Adabas database available to all users on the network. The only client affected by the Entire Net-Work Client configuration settings would be the client to which they apply.
Only after these second set of tests run correctly would you publish the Entire Net-Work Client configuration settings by defining the same settings in the Directory Server.
