Contents

• Notices

• Summary of amendments

• Preface

• Part 1: Administration

  • 1. JP1/IM System Maintenance

    • 1.1 Managing the configuration information

      • 1.1.1 JP1/IM - Manager backups and recoveries

      • 1.1.2 Backing Up and Recovering of JP1/IM - Agent

    • 1.2 Managing the databases

      • 1.2.1 Database reorganization

      • 1.2.2 Database backup and recovery

      • 1.2.3 Re-creating a database and changing its settings

    • 1.3 Managing the disk capacity

      • 1.3.1 Managing the IM database capacity

      • 1.3.2 Managing the log file size

      • 1.3.3 Managing dump files

    • 1.4 Using historical reports

      • 1.4.1 Outputting events to a CSV file

      • 1.4.2 Correlation event generation history

      • 1.4.3 Exclusion history and definition history of common exclusion conditions

    • 1.5 Migrating the configuration information and databases

      • 1.5.1 Configuration information and databases to be migrated

    • 1.6 Managing certificates for the communication encryption function

      • 1.6.1 Managing the effective duration of the server certificate

      • 1.6.2 Managing keystores

  • 2. Changing the Configuration of JP1/IM

    • 2.1 Changing the JP1/IM settings information

      • 2.1.1 Changing the JP1/IM-Agent settings with integrated agent host

      • 2.1.2 Changing the Integration Manager Host JP1/IM-Agent settings

    • 2.2 Tasks necessary when a host name is changed

      • 2.2.1 When you are using JP1/IM-Agent as agent

      • 2.2.2 When you are using JP1/Base as agent

      • 2.2.3 Tasks to be performed when the host name of a mail server is changed

      • 2.2.4 Tasks to be performed before a logical host name is changed in a cluster system

    • 2.3 Tasks necessary when an IP address is changed

      • 2.3.1 When JP1/IM-Agent is used as agent

      • 2.3.2 When JP1/IM-Base is used as agent

      • 2.3.3 Tasks to be performed when the IP address of a mail server is changed

    • 2.4 Tasks necessary when the date of a manager or agent is changed

      • 2.4.1 Resetting the date/time of a manager or agent to a past date/time

      • 2.4.2 Advancing the system time

    • 2.5 Required steps to change integrated agent host system date and time

      • 2.5.1 Changing integrated agent host system date and time

      • 2.5.2 Changing the system date and time on a cluster system

      • 2.5.3 Changing the system date and time in a container

    • 2.6 Tasks necessary when the date of a monitored host in a remote monitoring configuration is changed

      • 2.6.1 Resetting the date/time of a monitored host in a remote monitoring configuration to a past date/time

      • 2.6.2 Advancing the date/time of a monitored host in a remote monitoring configuration

    • 2.7 Tasks necessary when the passwords of a monitored host in a remote monitoring configuration are changed

    • 2.8 Notes on changing the monitoring configuration from remote to agent

      • 2.8.1 Notes on JP1/Base log file traps

      • 2.8.2 Notes on JP1/Base event log traps

    • 2.9 Tasks necessary when an Port number is changed

    • 2.10 Tasks to be performed when changing the locale of integrated agent host

      • 2.10.1 Changing the locale of integrated agent host

      • 2.10.2 Changing the locale on a cluster system

      • 2.10.3 Changing the locale in a container

    • 2.11 Duplicate an integrated agent host

      • 2.11.1 Replicating physical hosts

      • 2.11.2 Duplicate AWS/EC2 instance after operation starts

• Part 2: Operation

  • 3. Starting and Stopping JP1/IM - Manager

    • 3.1 Starting JP1/IM - Manager

      • 3.1.1 In Windows

      • 3.1.2 In UNIX

      • 3.1.3 Operations in a cluster system

      • 3.1.4 Operating a logical host in a non-cluster system

    • 3.2 Stopping JP1/IM - Manager

      • 3.2.1 In Windows

      • 3.2.2 In UNIX

      • 3.2.3 Operations in a cluster system

      • 3.2.4 Operating a logical host in a non-cluster system

    • 3.3 Automatic startup and automatic stop setting examples when a logical host operates in a non-cluster system

      • 3.3.1 Setting up automatic startup and automatic stop when a logical host operates in a non-cluster system (for Windows)

      • 3.3.2 Setting up automatic startup and automatic stop when a logical host operates in a non-cluster system (for Linux)

      • 3.3.3 Setting up automatic startup and automatic stop on both the physical host and the logical host

    • 3.4 Notes on starting and stopping

  • 4. JP1/IM - Manager Login and Logout

    • 4.1 Logging in to JP1/IM - Manager

      • 4.1.1 Using a Web browser to log in to JP1/IM - Manager (Intelligent Integrated Management Base)

      • 4.1.2 Using the GUI to log in to JP1/IM - Manager

      • 4.1.3 Using a command to log in to JP1/IM - Manager

    • 4.2 Logging out of JP1/IM - Manager

  • 5. System Monitoring from the Intelligent Integrated Management Base

    • 5.1 Viewing the system status

      • 5.1.1 What Intelligent Integrated Management Base can monitor

      • 5.1.2 Items displayed in the sunburst chart or the tree chart

    • 5.2  Viewing JP1 events (Events window)

      • 5.2.1 Items displayed in the events list

      • 5.2.2 Displaying Repeated event list window

      • 5.2.3 Displaying detailed JP1 event information

    • 5.3 Add metric for Trend Viewing and Alerting

    • 5.4 How to look at the dashboard

      • 5.4.1 For viewing dashboards

      • 5.4.2 IM management node status monitoring

      • 5.4.3 Monitoring with alert information

      • 5.4.4 Checking various IT resouces

      • 5.4.5 Flow of Problem Investigation and Response Based on Dashboard

      • 5.4.6 Notes

    • 5.5 Viewing links with other products

      • 5.5.1 Using signs to avoid failures (link with JP1/AJS)

      • 5.5.2 Understanding how extensive a problem that occurred during operation of a job is and handling it (link with JP1/AJS)

      • 5.5.3 Understanding in advance which root jobnets are affected before the definition or content of a job is changed (link with JP1/AJS)

      • 5.5.4 Checking performance data and handling the problem (link with JP1/PFM)

      • 5.5.5 Handling errors by viewing suggestions

      • 5.5.6 Logging in to the system with single sign-on through linkage with external products using OIDC authentication

      • 5.5.7 Sharing information using a direct access URL

    • 5.6 Notes on operating the Intelligent Integrated Management Base

      • 5.6.1 Notes on when there is a link with JP1/AJS

      • 5.6.2 Notes on using event receiver filters

  • 6. System Monitoring from Central Console

    • 6.1 Viewing JP1 events

      • 6.1.1 Items displayed in the events list

      • 6.1.2 Events displayed in the events list in the Event Console window

      • 6.1.3 Applying a filter

    • 6.2 Displaying detailed JP1 event information

      • 6.2.1 Editing JP1 memo entries

    • 6.3 Setting JP1 event response statuses

      • 6.3.1 Settings for JP1 event response statuses

      • 6.3.2 Setting a response status for JP1 events from the events list

      • 6.3.3 Deleting severe events from the Severe Events page

    • 6.4 Operating JP1 events from the Related Events window

      • 6.4.1 Checking detailed information about repeated events and changing the response status

      • 6.4.2 Checking detailed information about a correlation event and changing the response status

    • 6.5 Applying a JP1/IM filter

      • 6.5.1 Enabling a view filter to display only certain JP1 events

      • 6.5.2 Displaying only severe events

      • 6.5.3 Switching the event acquisition filter to be applied

      • 6.5.4 Setting an additional common exclusion-condition to exclude a JP1 event from the monitoring target or action execution

    • 6.6 Displaying an event by specifying an event display start-time

    • 6.7 Narrowing the JP1 events to be displayed by specifying a time period

    • 6.8 Searching for JP1 events

      • 6.8.1 Search method

      • 6.8.2 Displaying the search results

    • 6.9 Customizing JP1 event information by operation

      • 6.9.1 Displaying program-specific extended attributes of JP1 events (displaying program-specific extended attributes)

      • 6.9.2 Displaying extended attributes of JP1 events (mapping of event information)

      • 6.9.3 Adding a user-defined extended attribute to JP1 events that match a condition

      • 6.9.4 Changing the severity level of JP1 events

      • 6.9.5 Changing the message displayed for a JP1 event

    • 6.10 Taking actions for the generation of a large number of events

      • 6.10.1 General procedures and preparation for handling occurrence a large number of events

      • 6.10.2 Preparing to suppress event forwarding from an agent

      • 6.10.3 Handling the occurrence of a large number of events by suppressing event forwarding from an agent

      • 6.10.4 Handling the occurrence of a large number of events by consolidating them on the manager

      • 6.10.5 Setting a threshold for automatically suppressing event forwarding on an agent

      • 6.10.6 Specifying repeated event conditions

      • 6.10.7 Stopping, on the manager, a log file trap that issues a large numbers of events

      • 6.10.8 Consolidated display when events with the same attributes occur consecutively

    • 6.11 Handling JP1 events by linking with other products

      • 6.11.1 Registering JP1 events as incidents in JP1/IM - Service Support (linking with JP1/IM - Service Support)

      • 6.11.2 Displaying operating procedures for JP1 events (linking with JP1/Navigation Platform)

      • 6.11.3 Opening a monitor window of the application that issued JP1 events

      • 6.11.4 Displaying performance reports for JP1 events when linking with JP1/PFM

    • 6.12 Notes for Central Console

    • 6.13 Notes on using the Central Console - View

  • 7. System Monitoring from Central Scope

    • 7.1 Monitoring from the Monitoring Tree window

      • 7.1.1 Changing the status of monitoring nodes

      • 7.1.2 Changing the monitoring status of monitoring nodes

      • 7.1.3 Searching for monitoring nodes

      • 7.1.4 Searching for status-change events

      • 7.1.5 Displaying the attributes of monitoring nodes

      • 7.1.6 Displaying guide information

      • 7.1.7 Opening the Visual Monitoring window

      • 7.1.8 Displaying a login user list

      • 7.1.9 Saving the information in the Monitoring Tree window on the local host

    • 7.2 Monitoring from the Visual Monitoring window

      • 7.2.1 Opening the Monitoring Tree window from the Visual Monitoring window

      • 7.2.2 Changing the status of monitoring nodes

      • 7.2.3 Changing the monitoring status of monitoring nodes

      • 7.2.4 Searching for monitoring nodes

      • 7.2.5 Searching for status-change events

      • 7.2.6 Displaying the attributes of monitoring nodes

      • 7.2.7 Displaying guide information

    • 7.3 Cautions on integrated scope

  • 8. System Operation Using JP1/IM

    • 8.1 Executing a command

      • 8.1.1 Executing a command by using Command Execution

      • 8.1.2 Executing a command by using the Command button

      • 8.1.3 User that executes commands

      • 8.1.4 Checking command execution status and deleting a command

    • 8.2 Executing automated actions and taking necessary steps

      • 8.2.1 Checking the execution status of an automated action

      • 8.2.2 Checking the execution results of automated actions

      • 8.2.3 Checking the operating status of the automated action function

    • 8.3 Opening other application windows from the Tool Launcher

      • 8.3.1 Operations in the Tool Launcher window

      • 8.3.2 Functions that can be operated from the Tool Launcher window

  • 9. Managing the System Hierarchy Using IM Configuration Management

    • 9.1 Managing hosts

    • 9.2 Managing the system hierarchy

    • 9.3 Managing the configuration of a virtual system

      • 9.3.1 Registering a virtual system host

      • 9.3.2 Displaying host information in a virtual system

      • 9.3.3 Applying the management information to the Central Scope monitoring tree

    • 9.4 Managing business groups

    • 9.5 Managing profiles

    • 9.6 Managing service operation status

      • 9.6.1 Collecting service operation information

      • 9.6.2 Service operation information display

    • 9.7 Exporting and importing management information of IM Configuration Management

      • 9.7.1 Exporting management information of IM Configuration Management

      • 9.7.2 Importing management information of IM Configuration Management

      • 9.7.3 Applying the imported management information of IM Configuration Management to a system

    • 9.8 Cautions on the IM configuration

  • 10. Starting and Stopping JP1/IM - Agent

    • 10.1 Service of JP1/IM - Agent

    • 10.2 Starting the Service

    • 10.3 Stopping the service

    • 10.4 When operating in a cluster system

      • 10.4.1 Starting the Service

      • 10.4.2 Stopping the service

      • 10.4.3 Settings of auto start

      • 10.4.4 Auto-Stop at OS Shutdown

• Part 3: Linking with Other Products

  • 11. Linking with BJEX or JP1/AS

    • 11.1 Overview of BJEX and JP1/AS linkage

      • 11.1.1 System configuration when linking JP1/IM with a batch job execution system

    • 11.2 JP1/IM functionality for BJEX and JP1/AS linkage

      • 11.2.1 Handling response-waiting events in JP1/IM

      • 11.2.2 Monitoring response-waiting events

      • 11.2.3 Accumulation of response-waiting events

      • 11.2.4 Responding to response-waiting events

      • 11.2.5 Canceling response-waiting events

    • 11.3 Configuring JP1/IM to link with BJEX and JP1/AS

      • 11.3.1 Configuring JP1/IM - Manager

      • 11.3.2 Configuring JP1/IM - View

      • 11.3.3 Configuring JP1/Base

      • 11.3.4 Communication settings between BJEX or JP1/AS and JP1/IM - Manager

      • 11.3.5 Configuring BJEX or JP1/AS

    • 11.4 Working with response-waiting events

      • 11.4.1 Flow of tasks for responding to response-waiting events

      • 11.4.2 Responding to response-waiting events

      • 11.4.3 Manually releasing response-waiting events from the hold-and-accumulate state

      • 11.4.4 Resuming monitoring of events in the hold-and-accumulate state

    • 11.5 Command usage when linking with BJEX or JP1/AS

      • 11.5.1 jcoimdef

      • 11.5.2 jim_log.bat (Windows only)

      • 11.5.3 jim_log.sh (UNIX only)

• Part 4: Troubleshooting

  • 12. Troubleshooting

    • 12.1 Troubleshooting procedure

    • 12.2 Log information types

      • 12.2.1 JP1/IM - Manager log information

      • 12.2.2 JP1/IM - Agent log information

    • 12.3 Data that needs to be collected when a problem occurs

      • 12.3.1 Information about JP1/IM - Manager

      • 12.3.2 Data about JP1/IM - Agent

    • 12.4 Collecting data

      • 12.4.1 How to collect JP1/IM - Manager data

      • 12.4.2 How to collect JP1/IM - Agent data

    • 12.5 Troubleshooting

      • 12.5.1 How to isolate faults

      • 12.5.2 What happens and how to recover from major input errors

      • 12.5.3 Dealing with common problems

• Part 5: IM Exporter

  • 13. Using IM Exporter

    • 13.1 Starting and stopping JP1/IM - Agent services defined by IM Exporter add-on programs

      • 13.1.1 Windows environment

      • 13.1.2 Linux environment

    • 13.2 Changing the IM Exporter configuration

      • 13.2.1 Procedure required to change a monitored host name or IP address

      • 13.2.2 Procedure required to change the Exporter listening port

      • 13.2.3 Procedure required to change the listening port for scraping used by the log metrics feature

      • 13.2.4 Procedure required to add, change, and delete targets for monitoring

    • 13.3 IM Exporter troubleshooting

      • 13.3.1 Isolating failures

      • 13.3.2 Results of major input errors and how to recover from them

      • 13.3.3 Major issues and countermeasures

• Index

To Page Top