Kriu for Crisis Management v 1.1

Introduction

Kriu for Crisis Management enables you to manage “crisis” due to natural disasters, such as earthquakes, floods from rainfall and overflows, as well as potentially dangerous situations caused by riots, insurrections and terrorist acts.

When a potential danger notification arrives a “pre-crisis” event is automatically opened. This allows an operator to analyze the event in order to understand it and as needed register it, and indicate the area of interest on a map, with the ability to view at any time the potentially impacted assets.

If the pre-crisis operator finds the event in question actually dangerous, he will associate it with an actual crisis event, triggering a series of activities that can involve managers with various roles to effectively contribute to the resolution of the crisis.

Table of Contents

1       Introduction. 3

2       Architectural Overview and Technical Specifications. 4

2.1        High Level Architecture. 4

2.2        Technical Specifications and Minimum Hardware and Software Requirements. 5

3       Login. 6

3.1        Login. 6

4       Pre-crisis Events. 7

4.1        Console. 7

4.2        Event Aggregation. 7

4.3        Mappings. 8

4.4        Opening a Crisis Event 14

5       Crisis Events. 16

5.1        Console. 16

5.2        Crisis Level 16

5.3        Managing Crisis. 17

5.3.1 Actions 18

5.3.2 Documentation. 19

5.4        Group Notification. 20

5.4.1 Integration with Lync. 21

5.5        Closing Crisis. 24

5.6        Manually Opening an Event 25

6       Reporting. 27

Fill out the form and download the free manual

Operations Manual for IBM Tivoli Monitoring 6.2.2.1 in ProductionSample

Introduction

This document describes the monitoring solution implemented by IBM in ProductionSample based on Tivoli Suite products. The second chapter provides a description of the resulting architecture, with indications of the products that make up the solution. The third chapter provides the information necessary for the management of the installed environment, with indications of the activation procedures for the monitors and of the visualization of the alarms.

The document is not intended as a substitute for the official Tivoli documentation to which will occasionally refer the user for more detailed explanations.

The complete official documentation for Tivoli products is available at

boulder.ibm.com

Table of Contents

1        Introduction. 3

2        The Implemented Solution. 4

2.1         IBM Tivoli Monitoring. 4

3        Customizing the ProductionSample Environment 6

3.1         Installation of an Agent 6

3.2         Source code. 6

3.3         Installation of an Agent (OS, Oracle, DB2 and Universal) on UNIX.. 6

3.4         Configuring the OS Linux Agent 7

3.5         Start/stop of the OS Agent for Linux. 8

3.6         Configuration of the Oracle Agent on UNIX.. 8

3.7         Additional Configuration Steps for the Oracle Agent. 12

3.8         Start/stop of the Agent for Oracle. 13

3.9         Installation of the Custom Solution for Monitoring MySQL. 13

3.10           Configuring the Universal Agent for Monitoring MySQL. 15

3.11           Start/stop of the Universal Agent 15

3.12           Installation of the Agent Builder on UNIX.. 15

3.13           Creation of the Tivoli Agent for SNMP Monitoring of Windows Server 2000 Professional 15

3.14           Installation of SNMP Monitoring Agent 22

3.15           Configuration of the SNMP Monitoring Agent 23

3.16           Start/stop of SNMP Monitoring Agent 24

3.17           Configuration of DB2 Monitoring Agent 24

3.18           Start/stop of the DB2 Monitoring Agent 24

4        Procedure for Deploying Agents Remotely. 25

4.1         Procedure for Installing and Enabling Support Files for Agents. 26

Fill out the form and download the free manual

© 2016 OMNINECS. All rights reserved.

Click Me