12.4.2 How to collect JP1/IM - Agent data

(a) Integrated agent host

1. Log in to integrated agent host.

2. Execute the jima_log command (data collection tool).

   When you execute the jima_log command, a jp1default folder is created under the document storage directory specified by -f option. The collected document is stored there.

   For details about the jima_log command, see jima_log (in Chapter 1. Commands) in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

3. Manually collect the following files:

   Data to be collected	Collection object
   Product information	If you have already set up the log extraction command for SAP system, collect the following files manually: Environment parameter configuration file (any name.ini) Log files of SAP system log extract commands Trace files for SAP system log extract commands The following files-stored in the path set in WORKDIR of configuration file environment parameter - Log file of SAP system log extract command (any name) - SAP system log extract command trace file (command name.log, command name.dat) - Trace file (dev_rfc*) output by RFC library installation-location-of-the-SAP-system-log-extract-command\agtm folder If sensitive information such as passwords is included, delete the corresponding definition from the definition file after collection.
   	When JP1/AJS3 is linked by the job monitoring function, you can manually collect the files that are output by JP1/AJS3 linkage command (ajseventmetrics). If -d option or -l option is not specified as an argument of the linkage command (ajseventmetrics) set to Script exporter configuration file, the data is collected using JP1/AJS3 data collection tool. If -d option or -l option is specified as an argument of the linkage command (ajseventmetrics) set in Script exporter configuration file, you can collect the directory specified by the option manually.

(b) Integrated agent host on Cluster System

1. Log in to the integrated agent host of active server.

2. Execute the jima_log command (collection tool) with the -l option specified.

   When the jima_log command is executed, the logical host name folder is created under the document storage directory specified by -f option. The collected materials are stored in the folder.

   For details about the jima_log command, see jima_log (in Chapter 1. Commands) in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

3. Log in to integrated agent host of the standby system.

4. To collect only information about the physical host, execute the jima_log command (data collection tool) without the -l option.

   When the jima_log command is executed, the logical host name folder is stored in the document storage directory specified by -f option. The collected data is stored in the folder.

   For details about the jima_log command, see jima_log (in Chapter 1. Commands) in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

5. Manually collect the following files:

   Data to be collected	Collection object
   Product information	If you have already set up the log extraction command for SAP system, collect the following files manually: Environment parameter configuration file (any-name.ini) Log files of SAP system log extract commands Trace files for SAP system log extract commands The following files-stored in the path set in WORKDIR of configuration file environment parameter - Log file of SAP system log extract command (any-name) - SAP system log extract command trace file (command name.log, command name.dat) - Trace file (dev_rfc*) output by RFC library installation-location-of-the-SAP-system-log-extract-command\agtm folder If sensitive information such as passwords is included, delete the corresponding definition from the definition file after collection.
   	When JP1/AJS3 is linked by the job monitoring function, you can manually collect the files that are output by JP1/AJS3 linkage command (ajseventmetrics). If -d option or -l option is not specified as an argument of the linkage command (ajseventmetrics) set to Script exporter configuration file, the data is collected using JP1/AJS3 data collection tool. If -d option or -l option is specified as an argument of the linkage command (ajseventmetrics) set in Script exporter configuration file, you can collect the directory specified by the option manually.

(c) Integrated agent host in Containers

Same as 12.4.2(1)(a) Integrated agent host.

(d) Integration Manager Host

Collect the data related to JP1/IM agent management base (imbase, imbaseproxy) with the data collection tool (jim_log.bat).

For the file to be collected, see the file folder list in Appendix A.4 (1) Integrated Manager host (Windows) in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

(e) Integration Manager Host on Cluster Systems

Same as 12.4.2(1)(d) Integration Manager Host.

(f) Monitored AIX hosts (When Node exporter for AIX is deployed)

1. Log in to the monitored AIX host.

2. Execute the jima_log_aix command (data collection tool).

   When the jima_log_aix command is executed, the compressed file "jima_log_aix.tar.gz" of the collected document is stored in the document storage directory specified by -f option.

   For details about the jima_log_aix command, see jima_log_aix (in Chapter 1. Commands) in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference, API Reference.

(a) Integrated agent host

1. Log in to integrated agent host.

2. Execute the jima_log command (data collection tool).

   When the jima_log command is executed, the compressed file "jima_log.tar.gz" of the collected material is stored in the document storage directory specified by -f option.

   For details about the jima_log command, see jima_log (in Chapter 1. Commands) in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference, API Reference.

3. Manually collect the following files:

   Data to be collected	Collection object
   Product information	If you have already set up the SAP system log extract command, collect the following files manually: Environment parameter configuration file (any name.ini) Log files of SAP system log extract commands Trace files for SAP system log extract commands The following files-stored in the path set in WORKDIR of configuration file environment parameter - Log file of SAP system log extract command (any name) - SAP system log extract command trace file (command name.log, command name.dat) - Trace file (dev_rfc*) output by RFC library If the directory where the above files are stored is changed in the environment parameter configuration file or the argument when the SAP system log extract command is executed, the changed directory must also be collected. /opt/jp1pc/agtm directory If sensitive information such as passwords is included, delete the corresponding definition from the definition file after collection.
   	When JP1/AJS3 is linked by the job monitoring function, you can manually collect the files that are output by JP1/AJS3 linkage command (ajseventmetrics). If -d option or -l option is not specified as an argument of the linkage command (ajseventmetrics) set to Script exporter configuration file, the data is collected using JP1/AJS3 data collection tool. If -d option or -l option is specified as an argument of the linkage command (ajseventmetrics) set in Script exporter configuration file, you can collect the directory specified by the option manually.

(b) Integrated agent host on Cluster System

1. Log in to the integrated agent host of active system.

2. Execute the jima_log command (data collection tool) with the -l option specified.

   When the jima_log command is executed, the compressed file "logical-hostname.tar.gz" of the collected document is stored in the document storage directory specified by -f option.

   For details about the jima_log command, see jima_log (in Chapter 1. Commands) in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference, API Reference.

3. Manually collect the necessary files.

4. To collect only information about the physical host, execute the jima_log command (data collection tool) without the -l option.

   When the jima_log command is executed, the compressed file "logical-hostname.tar.gz" of the collected document is stored in the document storage directory specified by -f option.

   For details about the jima_log command, see jima_log (in Chapter 1. Commands) in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference, API Reference.

5. Manually collect the following files:

   Data to be collected	Objects to be collected
   Product information	If you have already set up the log extraction command for SAP system, collect the following files manually: Environment parameter configuration file (any name.ini) RFC library allocated when the SAP system log extract command was built CRT library allocated when the SAP system log extract command was built The following files-stored in the path set in WORKDIR of configuration file environment parameter - Log file of SAP system log extract command (any name) - SAP system log extract command trace file (command name.log, command name.dat) - Trace file (dev_rfc*) output by RFC library If the directory where the above files are stored is changed in the environment parameter configuration file or the argument when the SAP system log extract command is executed, the changed directory must also be collected. /opt/jp1pc/agtm directory If sensitive information such as passwords is included, delete the corresponding definition from the definition file after collection.
   	When JP1/AJS3 is linked by the job monitoring function, you can manually collect the files that are output by JP1/AJS3 linkage command (ajseventmetrics). If -d option or -l option is not specified as an argument of the linkage command (ajseventmetrics) set to Script exporter configuration file, the data is collected using JP1/AJS3 data collection tool. If -d option or -l option is specified as an argument of the linkage command (ajseventmetrics) set in Script exporter configuration file, you can collect the directory specified by the option manually.

(c) Integrated agent host in Containers

Same as 12.4.2(2)(a) Integrated agent host.

(d) Integrated Manager Host

Collect the data related to JP1/IM agent management base (imbase, imbaseproxy) with the data collection tool (jim_log.sh).

For the file to be collected, see the file and directory list in Appendix A.4 (2) Integrated Manager host (Linux) in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

(e) Integrated Manager Host on Cluster Systems

Same as 12.4.2(2)(d) Integrated Manager Host.

(f) Monitored AIX hosts (When Node exporter for AIX is deployed)

Same as 12.4.2(1)(f) Monitored AIX hosts (When Node exporter for AIX is deployed).