11.14.2 Files required for the function for centrally managing client definitions

(1) Client definition file used by the function for centrally managing client definitions

The client definition file used by the function for centrally managing client definitions specifies the values for the operands in the client definition that you want to apply to the authorization identifier managed by this function. The applicable authorization identifier connects to the HADB server, according to the definitions in the client definition file used by the function for centrally managing client definitions.

The template of the client definition file used by the function for centrally managing client definitions (client.def) is stored in the server directory $ADBDIR/sample/conf. Copy the template, and in the new file, specify the individual operands for the client definition. The specification rules for the client definition are the same as ones for the server definition. For details about the specification rules for the server definition, see 7.3 Syntax rules for the server definition.

Note

• For details about individual operands in the client definition, see Contents of operands in the client definition in the HADB Application Development Guide.

• You do not have to specify the operands in the client definitions that are not applied to the function for centrally managing client definitions. For details about individual operands in the client definitions that are not applied to this function, see Notes about using the function for centrally managing client definitions in the HADB Application Development Guide.

Important

The default values are assumed for the omitted operands in client definitions. Therefore, if you want to apply the definitions in the client definition file managed by an HADB client, specify the same definitions also in the client definition file used by the function for centrally managing client definitions.

After creating the client definition file to be used by the function for centrally managing client definitions, store the file in the server directory $ADBDIR/conf. You can rename the client definition file from the name of the template (client.def).

If you want to apply the definitions in different client definition files to multiple authorization identifiers, create as many client definition files as needed that are used by the function for centrally managing client definitions.

To Page Top

(2) Client management definition file

In the client management definition file, the adbclientmang operand in the client-managing definition is specified. For the adbclientmang operand, specify the following two items to associate them.

Items specified for the adbclientmang operand in the client-managing definition:

• Name of the client definition file used by the function for centrally managing client definitions

• Authorization identifier of the HADB user for which you want to apply the definitions in the client definition file

The template of the client management definition file (adbclientdefmang.def) is stored in the server directory $ADBDIR/sample/conf. Copy the template, and in the new file, specify the adbclientmang operand in the client-managing definition.

After creating the client management definition file, store the file in the server directory $ADBDIR/conf. Keep the file name the same as the template (adbclientdefmang.def).

In the following cases, the function for centrally managing client definitions is not applied:

• Nothing is specified in the client management definition file. (The file is an empty file.)

• All definitions in the client management definition file are commented out.

In these cases, the definitions specified in the client definition file managed by the HADB client are applied.

{{
  [adbclientmang
     -f client-definition-file-used-by-the-function-for-centrally-managing-client-definitions
     -i authorization-identifier[,authorization-identifier]...]
}}

To Page Top

(3) Client definition files managed by HADB clients

Even when you use the function for centrally managing client definitions, you need to create the client definition files that are managed by individual HADB clients.

Note

For details about how to create the client definition file managed by an HADB client, see How to create a client definition in the HADB Application Development Guide.

For the client definition file managed by an HADB client, specify the operands in the client definition to which the function for centrally managing client definitions is not applied. Such operands include the host name and port number of the connection-target HADB server. For details about individual operands in the client definitions that are not applied to the function for centrally managing client definitions, see Notes about using the function for centrally managing client definitions in the HADB Application Development Guide.

For the client definition file managed by an HADB client, you do not have to specify the operands in the client definition to which the function for centrally managing client definitions is applied.

Specify the operands in the client definitions to which the function for centrally managing client definitions is applied, in the client definition file used by the function for centrally managing client definitions. If an operand is omitted, the default value is assumed.

To Page Top