Configuration definition file (jbs_route.conf)
- Organization of this page
Format
[manager-host-1]
managed-host
managed-host
:
[manager-host-2]
managed-host
:
File
jbs_route.conf (configuration definition file)
jbs_route.conf.model (model file for the configuration definition file)
Storage directory
- In Windows
-
- For a physical host:
-
Base-path\conf\route\
- For a logical host:
-
shared-folder\jp1base\conf\route\
- In UNIX
-
- For a physical host:
-
/etc/opt/jp1base/conf/route/
- For a logical host:
-
shared-directory/jp1base/conf/route/
Description
This file defines the system hierarchy that is to be managed by JP1/IM.
JP1/IM operates under a hierarchical system configuration that consists of managers that manage the system and agents. There can be a hierarchy under each manager, which enables JP1/IM to manage systems of various sizes.
The system hierarchy is managed by JP1/Base, which is the prerequisite product that provides the core functionality of JP1/IM.
Based on the hierarchy information that is defined in this file, the JP1/IM functions operate as follows:
-
JP1 event forwarding
Important JP1 events are forwarded from lower-level hosts to higher-level hosts, as defined in the configuration definition information (when the default settings are used).
-
Automated actions and command execution
Automated action and command execution requests can be issued to hosts specified in the configuration definition information.
You must enter a linefeed on the last line of the file.
When the definitions are applied
The specified configuration definition information takes effect when the following commands are executed for applying the definitions:
-
jbsrt_distrib (distributes definition information)
-
jbsrt_sync (synchronizes definition information at the highest manager)
-
jbsrt_del (deletes definition information)
Information that is specified
- [manager-host]
-
Specifies the host name of a manager.
Express the host name using from 1 to 255 alphanumeric characters, the hyphen (-), and the period (.).
If you divide the system configuration definition, place an asterisk (*) immediately before the host name that is duplicated in (continued to) another configuration definition file.
The manager is the host where JP1/IM - Manager is installed.
- managed-host
-
-
Specifies the name of a host that is managed by the specified manager.
-
Express the host name using from 1 to 255 alphanumeric characters, the hyphen (-) and the period (.).
-
If you divide the system configuration definition, place an asterisk (*) immediately before the host name that is duplicated in (continued from) another configuration definition file.
-
JP1/Base must be installed on a managed host. A managed host cannot be defined under more than one manager.
-
Specify a host name that is registered in the hosts file or on the DNS server, or a host name that is defined in jp1hosts or jp1hosts2.
-
If you specify an asterisk (*) as part of the host name, which is not permitted, the jbsrt_distrib command will not delete the configuration definition information that follows that host name.
-
If you use alias names for hosts, do not specify in the definition file more than one alias for a host. If multiple aliases are specified for the same host, each alias is treated as the name of a different host.
-
If you use the automated action function or the command execution function, specify for a managed host the same host name that is specified in the command execution or automated action function. If the host is a physical host, specify the host name that is returned by the hostname command or an alias of that host name. Do not specify an alias name for a host running on Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP Professional, or Windows 2000. (The restrictions that apply to the use of alias names are the same as the restrictions that apply to the managers.)
-
Example definition
The following describes examples of configuration definition files for a JP1/IM system based on the system hierarchy shown in the table below. The first example is of a batch definition; the second example is of divided definitions.
|
Integrated manager |
Site manager |
Agents |
|---|---|---|
|
jp1sv1 |
jp1sv2 |
jp1ag1, jp1ag2 |
|
jp1sv3 |
jp1ag3, jp1ag4, jp1ag5 |
- Example of a batch definition:
-
To create a batch definition, edit the configuration definition file at the integrated manager as follows (there is no need to edit the files at the site managers or agents):
- Configuration definition file for integrated manager jp1sv1:
[jp1sv1] jp1sv2 jp1sv3 [jp1sv2] jp1ag1 jp1ag2 [jp1sv3] jp1ag3 jp1ag4 jp1ag5
- Example of divided definitions:
-
To create divided definitions, edit a configuration definition file at the integrated manager and at each site manager as follows (there is no need to edit files at the agents):
- Configuration definition file for integrated manager jp1sv1:
[jp1sv1] *jp1sv2 *jp1sv3
- Configuration definition file for site manager jp1sv2:
[*jp1sv2] jp1ag1 jp1ag2
- Configuration definition file for site manager jp1sv3:
[*jp1sv3] jp1ag3 jp1ag4 jp1ag5