Common definition settings file (configuration management functionality)

Format

To Page Top

Parameters by type

Required parameters:

None

Custom parameters:

• JBSRT_DISTRIB_VERSION

• JBSROUTE_COM_TIMEOUT

To Page Top

File name

Any

jbsrt_setup.conf.model (Model file for the common definition settings file (configuration management functionality))

To Page Top

Storage destination directory

The model file for the common definition settings file (configuration management functionality) is stored in the directories listed below. Create a common definition settings file with a file name of your choice by copying the model file.

In Windows:

installation-folder\conf\route\

shared-folder\jp1base\conf\route\ (in a cluster system)

In UNIX:

/etc/opt/jp1base/conf/route/

shared-directory/jp1base/conf/route/ (in a cluster system)

To Page Top

Description

This file is used to set the specified information on the configuration management functionality to the common definition information. If you newly installed JP1/Base, JBSRT_DISTRIB_VERSION is set to 1 (differential distribution method). If you installed JP1/Base by overwriting a JP1/Base version earlier than 11-10, JBSRT_DISTRIB_VERSION is not defined (in which case, the batch distribution method will be used).

For details about the differential distribution functionality, see 2.6.3 Managing the system's hierarchical configuration by using commands.

To Page Top

Application of settings

When the jbssetcnf command is executed, the information in the common definition settings file (configuration management functionality) is added to the common definition information. The value set for JBSRT_DISTRIB_VERSION in the common definition takes effect when the jbsrt_distrib command is executed. The value of common definition JBSROUTE_COM_TIMEOUT is applied when the jbs_spmd_reload command is executed or JP1/Base is restarted. For details about the jbssetcnf command and the jbsrt_distrib command, see jbssetcnf and jbsrt_distrib in 15. Commands.

To Page Top

Definition details

The following rules apply to the common definition settings file (configuration management functionality):

• Do not use a space or tab before or after an equal sign (=) or at the beginning or end of a line. If a space or tab is used in these locations, an error occurs when the jbssetcnf command is executed.

• Lines containing only a linefeed character are ignored.

[JP1_DEFAULT\JP1BASE\JBS_ROUTE]

This section specifies the configuration management functionality settings. If you set up a logical host, use JP1_DEFAULT as the logical host name.

"JBSRT_DISTRIB_VERSION"=dword:{00000000 | 00000001}

Specify whether to use the batch distribution method or the differential distribution method to distribute configuration definition information. To use the batch distribution method, specify dword:00000000. To use the differential distribution method, specify dword:00000001. If the specified value is not a value that can be specified in the common definition information or no value is specified, dword:00000000 is assumed.

"JBSROUTE_COM_TIMEOUT"=dword:hexa-decimal-number

Specify a communication timeout value (in seconds) in a hexadecimal number for the execution of configuration distribution or configuration synchronization. The permissible range is from 00000001 (1 second) through 00015180 (86,400 seconds). If any invalid value is specified, the initial value 00000258 (600 seconds) for a starting up case or, for a reloading case, a previously effective value before reloading is assumed. If no value is specified, the initial value 00000258 (600 seconds) is assumed.

To Page Top

Notes

If you specify a large value for communication timeout (JBSROUTE_COM_TIMEOUT), it may take too much time to execute the jbsrt_distrib or jbsrt_sync command for configuration management functionality or to set system hierarchical configuration (IM configuration) using IM configuration management. We recommend that you use the initial value of 600 seconds as it is.

Reconsider the communication timeout value if timeout occurs in such a case explained in 2.6.3 (5) Reviewing the communication timeout value.

To Page Top