1.18.3 Specifying settings for handling JP1/IM - Manager failures (for Windows)

(1) Preparations for collecting data in the event of a failure

JP1/IM - Manager provides a batch file (jim_log.bat) as a tool for collecting data in the event of a problem. This tool enables you to collect data needed for resolving problems in batch mode.

The data collection tool of JP1/IM - Manager can collect troubleshooting data for JP1/IM - Manager, JP1/Base, and JP1/IM - View (on the same host). For details about the data that can be collected, see 11.3 Data that needs to be collected when a problem occurs in the JP1/Integrated Management 2 - Manager Administration Guide.

About the data collection tool

• About jim_log.bat

  See jim_log.bat (Windows only) in Chapter 1. Commands in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

In the event of a problem, you might need to obtain a memory dump and a crash dump. (This data can also be collected by using the data collection tool.) For details about how to configure output settings for memory dump and crash dump, see the release notes.

Important

• The size of a memory dump depends on the size of the real memory. If the installed physical memory is large, the size of a memory dump will also be large. Take care to allocate sufficient disk space for collecting a memory dump. For details, see the Windows Help topic Stop error.

• In addition to JP1 information, error information for other application programs is also output to the crash dump. For this reason, output of a crash dump requires a fair amount of disk space. If you specify the setting to output crash dumps, take care that sufficient disk space is available.

• Settings for immediately obtaining a problem investigation report in case of abnormal termination By setting the following registry before starting JP1/IM - Manager, you can immediately obtain a user mode process dump for a problem investigation report when JavaVM terminates abnormally:Take sufficient care when setting registry values, because registry values influence the entire system.

  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps

  Set the following registry value for the registry key above:

  DumpFolder: REG_EXPAND_SZ <folder-name-of-dump-destination>

  (The folder requires access authorization.)

  DumpCount: REG_DWORD <number-of-dumps-saved>

  DumpType: REG_DWORD 2

To Page Top

(2) Restart settings in the event of abnormal process termination

To specify restart settings in the event of abnormal process termination:

1. Define process restart.

   Edit the following extended startup process definition file (jp1co_service.conf) so that process restart is enabled:

   Console-path\conf\jp1co_service.conf

   The restart parameter is the third value separated by the vertical bars (|). Set either 0 (do not restart (default)) or 1 (restart). Do not change the first value separated by the vertical bars (|).

2. Apply the definition information.

   If JP1/IM - Manager is running, execute JP1/IM - Manager's reload command so that the process restart setting is enabled:

   jco_spmd_reload

About process restart definition

• About the extended startup process definition file (jp1co_service.conf)

  See Extended startup process definition file (jp1co_service.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

Note:

In a cluster system, do not enable process restart in the event of abnormal process termination. If JP1/IM - Manager fails, the process restart function might also be affected. If you want to restart processes in the event of abnormal process termination in a cluster system, use the cluster software (not JP1/IM - Manager) to control the restart.

To Page Top

(3) Setting JP1 event issuance in the event of abnormal process termination

To set JP1 event issuance in the event of abnormal process termination:

1. Set JP1 event issuance.

   Edit the following IM parameter definition file (jp1co_param_V7.conf):

   Console-path\conf\jp1co_param_V7.conf

   In this file, SEND_PROCESS_TERMINATED_ABNORMALLY_EVENT and SEND_PROCESS_RESTART_EVENT are the JP1 event issuance setting parameters. To issue JP1 events, change the value to dword:1.

2. Execute the jbssetcnf command to apply the definition information.

   jbssetcnf Console-path\conf\jp1co_param_V7.conf

3. Restart JP1/Base and the products that require JP1/Base.

   The specified settings take effect after the restart.

About JP1 event issuance settings

• About the IM parameter definition file (jp1co_param_V7.conf)

  See IM parameter definition file (jp1co_param_V7.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

To Page Top

(4) Setting the health check function

To set the health check function in order to detect JP1/IM - Manager process hang-ups:

1. Open the health check definition file (jcohc.conf) and specify parameters.

   To enable the health check function, specify ENABLE=true.

   Specify EVENT=true to issue a JP1 event and COMMAND=command-to-be-executed to execute a notification command when a hang-up is detected.

2. Use the jco_spmd_reload command to reload JP1/IM - Manager, or restart JP1/IM - Manager.

3. If you specified a notification command, execute the jcohctest command to check the notification command's execution validity.

   Execute the jcohctest command to determine whether the command specified in COMMAND executes correctly. If the operation is not valid, check and, if necessary, revise the specification.

   Important

   In Windows (x64), if you execute a command in the %WINDIR%\System32 folder, the redirection function of WOW64 redirects the command as a command in the %WINDIR%\SysWow64 folder. If the command does not exist at the redirection destination, the command execution might fail. Be careful when you specify a command in the %WINDIR%\System32 folder as the execution command.

About the health check function settings

• About the health check definition file (jcohc.conf)

  See Health check definition file (jcohc.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

• About the jcohctest command

  See jcohctest in Chapter 1. Commands in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

To Page Top

(5) Automatic backup and recovery settings for a monitoring object database

You specify these settings when you will be using the functions of Central Scope.

If the OS shuts down while the monitoring tree is being updated, or a failover occurs during cluster operation, the monitoring object database might be corrupted. Therefore, you must set the monitoring object database to be backed up and recovered automatically when the monitoring tree is being updated.

These settings are enabled when you have performed a new installation, and they are disabled if the settings were disabled in the previous version of JP1/IM - Manager. Change the settings as appropriate to your operation.

1. Terminate JP1/IM - Manager.

2. Execute the jbssetcnf command using the following file for the parameters:

   To enable the automatic backup and recovery functions for the monitoring object database: auto_dbbackup_on.conf

   To disable the automatic backup and recovery functions for the monitoring object database: auto_dbbackup_off.conf

   When you execute the jbssetcnf command, the settings are applied to the JP1 common definition information.

   For details about the jbssetcnf command, see the JP1/Base User's Guide.

   About the settings in the file

   For details about the settings in the file, see Automatic backup and recovery settings file for the monitoring object database (auto_dbbackup_xxx.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

3. Start JP1/IM - Manager.

To Page Top