2.4.1 Add JP1/Base monitoring settings
Function
This service template performs the basic setup and monitoring configuration for JP1/Base.
A monitoring system that monitors the following content is assumed:
- The system uses JP1/Base of the monitor server to conduct event log monitoring (Windows only) and application log trapping, and transfers the monitoring results to the JP1/IM - Manager server.
- The system does not execute automatic actions from the JP1/IM - Manager server.
This service template requires the following server:
- Monitor server
This server performs event log monitoring and application log monitoring, and transfers the JP1 events that occur to JP1/IM - Manager.
Perform the following setup procedure, which is necessary after a monitor server is added to the above monitoring system.
(1) For Windows, configure the startup order definition file (JP1SVPRM.DAT). For UNIX, configure the automatic startup and automatic stop scripts.
(2) Register the following JP1/Base process to the Windows Firewall.
Skip this step if registration of JP1/Base programs of later than version 8.0# in Windows Firewall failed.
- jbssessionmgr
- jbsroute
- jcocmd
- jcocmdapi
- jevservice
- jbsplugind
- jbscomd_snd(#)
- jbscomd_rcv(#)
(3) Set the common definition information.
Use the jbssetcnf command to set the JP1/Base common definition information.
Transfer, to the monitor server for usage as the file specified for the p1base.targetCommonDefInfoPath property, the file in the JP1/AO server specified in the jp1base.commonDefInfoPathLocal property in the arguments of the jbssetcnf command.
Make this setting when both the jp1base.targetCommonDefInfoPath property and the jp1base.commonDefInfoPathLocal property are specified.
(4) Set the transfer settings file (forward).
(5) Set the definition file for event-log trap operations (ntevent.conf), the definition file for log-file trap operations (user-selected file name), the definition file for log-file trapping startup (jevlog_start.conf), and the log information definition file (jevlogd.conf).
You can specify more than one monitor servers where the JP1/AO settings will be made. To specify more than one monitor server, specify the host names of the monitor servers in the common.targetHostList property by separating them with commas. You can specify up to 99 servers.
Prerequisites
For the latest support information about [Required product in the System]/[Prerequisite products in the system executing the service template]/[Prerequisite product OS running in the system executing the service template], see the release notes.
[Required product in the System]
JP1/Automatic Operation 12-00 or later
[Prerequisite products in the system executing the service template]
(1) The following version of Job Management Partner 1/Base is running on the servers to be monitored:
Job Management Partner 1/Base 09-00 or later, or
JP1/Base 11-00 or later
[Prerequisite product OS running in the system executing the service template]
(1) Windows Server 2008 R2 Standard/Enterprise/Datacenter
(2) Windows Server 2012 Standard/Datacenter, Windows Server 2012 R2 Standard/Datacenter
(3) Windows Server 2016 Standard/Datacenter
(4) Windows Server 2019 Standard/Datacenter
(5) Red Hat Enterprise Linux Server 6 (32-bit x86), Red Hat Enterprise Linux Server 6 (64-bit x86_64)
(6) Red Hat Enterprise Linux Server 7 (64-bit x86_64)
(7) Red Hat Enterprise Linux Server 8 (64-bit x86_64)
(8) AIX V6
(9) AIX V7
[Usage conditions of prerequisite products in the system executing the service template]
(1) Prepare various definition files according to the monitor server environment (OS and JP1/Base version), and create services corresponding to these files.
(2) When making the startup order definition (JP1/Base for Windows only) and event transfer settings
Store the following files to be transferred to the monitor server in the JP1/AO server, and specify the paths of these files in the respective properties.
- Startup-order definition file (jp1svprm.dat) (Windows version only) (optional)
- Transfer-settings file (forward) (required)
(3) When configuring event log trapping (JP1/Base for Windows only)
In addition to the files shown in (2), store the following file to be transferred to the monitor server in the JP1/AO server, and specify the path of this file in the respective properties.
- Event log trap operation definition file (ntevent.conf) (Windows version only) (optional)
(4) When configuring log file trapping
In addition to the files shown in (2), store the following files to be transferred to the monitor server in the JP1/AO server, and specify the paths of these files in the respective properties.
- Definition file for log-file trap operations (jevlog.conf) (optional)
- Definition file for log-file trap startup (jevlog_start.conf) (optional)
- Log information definition file (jevlogd.conf) (optional)
(5) When configuring the common definition file
In addition to the files shown in (2), store the following file to be set to the monitor server in the JP1/AO server, and specify the path of this file in the respective properties.
- Common definition settings file (optional)
Create the common definition settings file by using the model files or the setting formats provided in the JP1/Base manual.
In JP1/Base, multiple model files are provided for each function, but you must create the file by combining these files into a single file.
(6) When making all settings
Store the files shown in (2) to (5) in the JP1/AO server, and specify the paths of these files in the respective properties.
(7) If properties are not specified for any file above that is indicated as optional, the corresponding file is not transferred. Also, if a file is not found at the path specified in the property, the task terminates abnormally.
(8) When using JP1/Base in a cluster configuration, specify the physical host or logical host of the execution system server in the common.targetHostList property.
Cautions
(1) To apply the content that is set in this service, after executing this service, reboot the monitor server.
(2) If the version of JP1/Base of the operation target is 09-00 or earlier, the definition file for log-file trap startup (jevlog_start.conf) cannot be set.
If necessary, refer to the JP1/Base manual, and make the automatic startup settings for the log file trap.
(3) When setting the common definition information, the task might terminate normally even if the statements in the common definition settings file are invalid. Carefully check that there are no mistakes in the common definition settings file.
When invalid common definition information is set, or if unnecessary settings remain even after the correct common definition information is set, make the corrections manually.
(4) If you use JP1/Base in a cluster configuration, execution of services is possible only to the execution system environment. The JP1/Base process is not registered in the Windows Firewall of the standby system. Make the settings manually.
(5) If you use JP1/Base in a cluster configuration, execution of services for the common definition information settings is possible only to the execution system environment. The common definition information of the standby system is not set. Make the settings manually.
(6) If you use JP1/Base in a cluster configuration, execution of services is possible only to the environment matching the logical host specified in the common definition settings file. If the service is executed to an environment that does not match the logical host, the task terminates normally, but the monitor server does not operate correctly.
(7) If this service is executed for a UNIX environment, do not use multi-byte characters for the properties.
(8) If the monitor server OS is Windows and multi-byte characters are specified, specify the file path by using a maximum of 255 bytes. Specify the conf folder path by using a maximum of 231 bytes.
(9) If a file or folder name specified remotely already exists, the remote file or folder is overwritten. For this reason, carefully check that there are no mistakes in the specified file or folder name.
Version
03.01.01
Tags
Configure JP1,Base
Property list
The following shows the list of the property groups set in the property:
|
Property group |
Description |
Initial display |
|---|---|---|
|
Monitor server information |
Specifies the environment information of the monitor server to be added. |
Y |
|
JP1/Base definition information |
Specifies the various definition files that are transferred from the JP1/AO server to JP1/Base. |
Y |
The following shows the list of the properties to be displayed in the "Service Definition" window:
- (Legend)
-
R: The property must be specified.
O: The property can be omitted. However, the property might be mandatory depending on what is specified for other properties. See the Description of each property.
|
Property key |
Property name |
Description |
I/O type |
Shared |
Required |
Property group |
|---|---|---|---|---|---|---|
|
jp1base.jp1svprmPathLocal |
JP1/Base start sequence definition file path (local) |
Specify the full path of the JP1/Base start sequence definition file (jp1svprm.dat) to be transferred from the JP1/AO server. |
Input |
Disabled |
O |
JP1/Base definition information |
|
jp1base.forwardPathLocal |
JP1/Base forwarding settings file path (local) |
Specify the full path of the JP1/Base forwarding settings file (forward) to be transferred from the JP1/AO server. |
Input |
Disabled |
R |
JP1/Base definition information |
|
jp1base.nteventPathLocal |
JP1/Base event log trapping definition file path (local) |
Specify the full path of the JP1/Base event log trapping definition file (ntevent.conf) to be transferred from the JP1/AO server. If you omit this property, no file will be transferred. |
Input |
Disabled |
O |
JP1/Base definition information |
|
jp1base.jevlogPathLocal |
JP1/Base log file trapping definition file path (local) |
Specify the full path of the JP1/Base log file trapping definition file (jevlog.conf) to be transferred from the JP1/AO server. If you omit this property, no file will be transferred. |
Input |
Disabled |
O |
JP1/Base definition information |
|
jp1base.jevlogstartLocal |
JP1/Base log file trapping startup definition file path (local) |
Specify the full path of the JP1/Base log file trapping startup definition file (jevlog_start.conf) to be transferred from the JP1/AO server. If you omit this property, no file will be transferred. |
Input |
Disabled |
O |
JP1/Base definition information |
|
jp1base.jevlogdLocal |
JP1/Base log information definition file path (local) |
Specify the full path of the JP1/Base log information definition file (jevlogd.conf) to be transferred from the JP1/AO server. If you omit this property, no file will be transferred. |
Input |
Disabled |
O |
JP1/Base definition information |
|
jp1base.commonDefInfoPathLocal |
Path of the JP1/Base common definition settings file (local) |
Specifies, as a full path, the path of the JP1/Base common definition settings file that is transferred (set) from the JP1/AO server. If a full path is not specified, the transfer does not execute. |
Input |
Disabled |
O |
JP1/Base definition information |
|
jp1base.targetBasePath_Windows |
JP1/Base installation path (Windows) |
Specify the installation folder of JP1/Base (Windows) on the monitor server. This property is mandatory for Windows-based monitor server. |
Input |
Disabled |
O |
Monitor server information |
|
jp1base.targetForwardPath_Windows |
Path to JP1/Base (Windows) forwarding file |
Specify the location of the JP1/Base forwarding settings file (forward) on the monitor server (Windows). This property is mandatory for Windows-based monitor server. |
Input |
Disabled |
O |
Monitor server information |
|
jp1base.targetConfPath_Windows |
Path to JP1/Base (Windows) configuration folder |
Specify the location of the JP1/Base configuration folder on the monitor server (Windows). This property is mandatory for Windows-based monitor server. |
Input |
Disabled |
O |
Monitor server information |
|
jp1base.targetForwardPath_Linux |
Path of forwarding file in JP1/Base (UNIX) |
Specify the full path of the forwarding settings file (forward) of JP1/Base on the monitor server (UNIX). This property is mandatory for UNIX-based monitor server. |
Input |
Disabled |
O |
Monitor server information |
|
jp1base.targetConfPath_Linux |
Path of configuration directory in JP1/Base (UNIX) |
Specify the full path of the JP1/Base configuration directory on the monitor server (UNIX). This property is mandatory for UNIX-based monitor server. |
Input |
Disabled |
O |
Monitor server information |
|
jp1base.targetCommonDefInfoPath |
The path of JP1/Base common definition settings file |
Specifies, as a full path, the path of the destination file when the JP1/Base common definition settings file is transferred to a monitor server. Always set this value when configuring the JP1/Base common definition settings. |
Input |
Disabled |
O |
Monitor server information |
The following shows the list of the properties to be displayed on the "Service Definition" window and the "Submit Service" window:
|
Property key |
Property name |
Description |
I/O type |
Shared |
Required |
Property group |
|---|---|---|---|---|---|---|
|
common.targetHostList |
List of host names for monitor server |
Specify the host names of monitor server on which to configure JP1/Base. Separate multiple host names with commas. The maximum number of host names is 99.Specify the physical host name of primary server or the logical host name of JP1/Base. |
Input |
Disabled |
R |
Monitor server information |
The following shows the list of the properties to be displayed in the "Task Details" window only:
|
Property key |
Property name |
Description |
I/O type |
Shared |
|---|---|---|---|---|
|
common.taskResult |
Results of repeating tasks |
This property contains the results of each task (as "true" or "false"), in a comma-delimited format. |
Output |
Disabled |
The following shows the restrictions on inputs to the properties displayed in the "Service Definition" window:
|
Property key |
Characters that can be input |
|---|---|
|
jp1base.jp1svprmPathLocal |
A character string of no more than 255 characters can be entered. It cannot include <, >, |, ;, &, *, ?, ", %, or a trailing \ or /. |
|
jp1base.forwardPathLocal |
A character string of no more than 255 characters can be entered. It cannot include <, >, |, ;, &, *, ?, ", %, or a trailing \ or /. |
|
jp1base.nteventPathLocal |
A character string of no more than 255 characters can be entered. It cannot include <, >, |, ;, &, *, ?, ", %, or a trailing \ or /. |
|
jp1base.jevlogPathLocal |
A character string of no more than 255 characters can be entered. It cannot include <, >, |, ;, &, *, ?, ", %, or a trailing \ or /. |
|
jp1base.jevlogstartLocal |
A character string of no more than 255 characters can be entered. It cannot include <, >, |, ;, &, *, ?, ", %, or a trailing \ or /. |
|
jp1base.jevlogdLocal |
A character string of no more than 255 characters can be entered. It cannot include <, >, |, ;, &, *, ?, ", %, or a trailing \ or /. |
|
jp1base.commonDefInfoPathLocal |
A character string of no more than 255 characters can be entered. It cannot include <, >, |, ;, &, *, ?, ", %, or a trailing \ or /. |
|
jp1base.targetBasePath_Windows |
A character string of no more than 232 characters can be entered. It cannot include <, >, |, ;, &, *, ?, ", %, /, or a trailing \. |
|
jp1base.targetForwardPath_Windows |
A character string of no more than 255 characters can be entered. It cannot include <, >, |, ;, &, *, ?, ", %, /, or a trailing \. |
|
jp1base.targetConfPath_Windows |
A character string of no more than 231 characters can be entered. It cannot include <, >, |, ;, &, *, ?, ", %, /, or a trailing \. |
|
jp1base.targetForwardPath_Linux |
A character string of no more than 255 characters can be entered. It cannot include <, >, |, ;, &, *, ?, ", %, `, or a trailing \ or /. |
|
jp1base.targetConfPath_Linux |
A character string of no more than 255 characters can be entered. It cannot include <, >, |, ;, &, *, ?, ", %, `, or a trailing \ or /. |
|
jp1base.targetCommonDefInfoPath |
A character string of no more than 255 characters can be entered. It cannot include <, >, |, ;, &, *, ?, ", %, `, or a trailing \ or /. |
The following shows the restrictions on inputs to the property displayed on the "Service Definition" window and the "Submit Service" window:
|
Property key |
Characters that can be input |
|---|---|
|
common.targetHostList |
A maximum of 1024 characters can be entered. Characters that can be used include alphanumeric characters, as well as . , - and , . |
Flow specification details
The following table shows the detailed specification of the flow:
|
Hierarchy |
Display name |
Plug-in |
||
|---|---|---|---|---|
|
Plug-in name |
Description |
Error recovery method |
||
|
1 |
setupJP1BaseLoop |
JP1/Base setup |
Repeatedly performs JP1/Base setup and adds monitoring settings for the specified host names. |
Remove the cause of the error, and then run the service again. |