Contents

• Notices

• Summary of amendments

• Preface

• 1. Installing and Setting Up JP1/IM

  • 1.1 Preparation before installation

  • 1.2 Configuration procedures

    • 1.2.1 Overview of a basic configuration system

    • 1.2.2 Installation and setup procedures

    • 1.2.3 Meaning of "Administrator permissions" in descriptions of installation and setup

    • 1.2.4 Replacement characters such as "View-path" and "Manager-path" used in procedures

  • 1.3 Installation and setup (for Windows)

    • 1.3.1 Installing the prerequisite product (for Windows)

    • 1.3.2 Setting up the prerequisite product (for Windows)

    • 1.3.3 Installing JP1/IM (for Windows)

    • 1.3.4 Setting up JP1/IM - Manager (for Windows)

    • 1.3.5 Setting up JP1/IM - View (Windows only)

    • 1.3.6 Starting JP1/IM - Manager (for Windows)

  • 1.4 Installation and setup (for Linux)

    • 1.4.1 Installing the prerequisite product (for Linux)

    • 1.4.2 Setting up the prerequisite product (for Linux)

    • 1.4.3 Installing JP1/IM (for Linux)

    • 1.4.4 Setting up JP1/IM - Manager (for Linux)

    • 1.4.5 Starting JP1/IM - Manager (for Linux)

  • 1.5 Logging in to JP1/IM - Manager from JP1/IM - View

• 2. Setting Up a System

  • 2.1 Setting up a basic system

    • 2.1.1 Procedure for setting up a system by using IM Configuration Management

    • 2.1.2 Verifying that the system has been correctly set up by IM Configuration Management

  • 2.2 Settings for executing commands on monitored hosts from JP1/IM - View

    • 2.2.1 Using the user mapping feature to map a JP1 user account to an OS user account

    • 2.2.2 Verifying that you can execute a command

  • 2.3 Customizing events to be monitored

    • 2.3.1 Using IM Configuration Management to set a forwarding filter in IM Configuration Management

    • 2.3.2 Verifying that the forwarding filter has been correctly set

  • 2.4 Using event conversion to monitor log files

    • 2.4.1 Procedure for starting log file monitoring in JP1/IM

    • 2.4.2 Verifying that records can be converted to events by the log file trap

  • 2.5 Using event conversion to monitor Windows event logs

    • 2.5.1 Monitoring Windows event logs in JP1/IM

    • 2.5.2 Verifying that Windows event log data can be converted to events

• 3. Monitoring a System

  • 3.1 Filtering the events that are displayed

    • 3.1.1 Using the view filter to specify conditions of events to be displayed

    • 3.1.2 Verifying that the events that match the view filter conditions are displayed

  • 3.2 Changing the severity level of events to better match your operations

    • 3.2.1 Using the severity changing function to change the severity level of events

    • 3.2.2 Verifying that the severity level was changed

  • 3.3 Removing hosts undergoing maintenance from being monitored

    • 3.3.1 Using common exclusion conditions in a filter to temporarily stop hosts from being monitored

    • 3.3.2 Verifying that events from unmonitored hosts are not displayed

  • 3.4 Specifying not to display unnecessary events in the list

    • 3.4.1 Using additional common exclusion conditions for a filter to prevent display of unnecessary events

    • 3.4.2 Checking whether unnecessary events are displayed

  • 3.5 Identifying important events among a large number of issued events

    • 3.5.1 Consolidating a large number of events by using the repeated event monitoring suppression function

    • 3.5.2 Verifying that a large number of events are consolidated

• 4. Detecting System Errors

  • 4.1 Handling multiple events as a single event

    • 4.1.1 Settings of the correlation event generation definition file to be created

    • 4.1.2 Associating events with correlation events

    • 4.1.3 Verifying that the correlation event is generated

  • 4.2 Automatically executing a command when a specific event is generated

    • 4.2.1 Using the automated action function to execute a command

    • 4.2.2 Verifying that a command specified as an automated action was executed

  • 4.3 Preventing an action that was already executed once from being executed again during a set period of time

    • 4.3.1 Using automated action suppression to prevent an action from being executed

    • 4.3.2 Verifying that the same action is not executed repeatedly

• 5. Troubleshooting System Errors

  • 5.1 Checking the status of previously-issued events

    • 5.1.1 Using the event display start-time specification function to display events based on a specified time

    • 5.1.2 Verifying that events are displayed from the specified display time

  • 5.2 Searching for events

    • 5.2.1 Using the search events function to search for events that match a specified condition

    • 5.2.2 Verifying that events were found

  • 5.3 Registering corrective action to be used as a guide for known errors

    • 5.3.1 Settings in the event guide information file to be created

    • 5.3.2 Using the event guide function to register the corrective action to be taken

    • 5.3.3 Verifying that the corrective action is registered

• Appendixes

  • A. Settings for Using the Email Notification Function (Windows only)

    • A.1 Setting up the email notification function (Windows only)

    • A.2 Verifying that the email notification function has been set up correctly (Windows only)

    • A.3 Example definition for an automated action when using the email notification function

  • B. Visual Monitoring to Ascertain the Extent of Impact of a System Error

    • B.1 Procedure for configuring visual monitoring

    • B.2 Verifying that you can monitor the extent of impact of events in map format and tree format

  • C. Monitoring Systems on a Business Group Basis

    • C.1 Procedure for creating business groups

    • C.2 Verifying that the business group settings are specified correctly

  • D. Port Numbers

    • D.1 JP1/IM port numbers

    • D.2 JP1/Base port numbers

    • D.3 Direction of communication through a firewall

  • E. List of Services (Windows only)

  • F. Advanced Use

  • G. Reference Material for this Manual

  • H. Glossary

To Page Top