VISUAL Message Center Smartconsole User Guide

SmartConsole User Guide

8.0 VMC-Mxx VISUAL Message Center SmartConsole - User Guide The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement.

Document date: May 2014

Document version: 1.8

Product version: 8.0

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, electronic mechani- cal, magnetic, optical, chemical, manual, or otherwise, without the prior written permission of Tango/04.

Trademarks Any references to trademarked product names are owned by their respective companies.

Technical Support For technical support visit our web site at www.tango04.com.

Tango/04 Computing Group S.L. Avda. Meridiana 358, 5 A-B Barcelona, 08027 Spain

Tel: +34 93 274 0051 Table of Contents

Table of Contents

Table of Contents...... iii How to Use this Guide...... xiii

Chapter 1

Introduction ...... 1

1.1. What is VISUAL Message Center?...... 2 1.2. How Does VISUAL Message Center Work?...... 2 1.2.1. Collection Layer ...... 3 1.2.2. Correlation Layer...... 3 1.2.3. Presentation Layer...... 3 1.2.4. Middleware Components ...... 3 1.3. SmartConsole Features ...... 3 1.3.1. Preprocessing ...... 3 1.3.2. Business Views and Enterprise Views ...... 4 1.3.3. Automation...... 5 1.3.4. Filters ...... 6 1.3.5. Resilient and Non Resilient Mode...... 7 1.3.6. Multiple Console Usability...... 7 1.3.7. In-Memory Database Deletion System ...... 8 1.4. Security ...... 8 1.5. How does SmartConsole work?...... 8 1.6. Terms and Definitions ...... 8

Chapter 2

Starting VISUAL Message Center SmartConsole...... 11

Chapter 3

VISUAL Message Center SmartConsole ...... 14

3.1. Toolbar ...... 15 3.1.1. Select Connections ...... 15 3.1.2. View Current Connections ...... 15 3.1.3. Remove Connections...... 16 3.1.4. Refresh...... 16 3.1.5. Capture with VISUAL Message Center iSeries Support Agent...... 16 3.1.6. Debug with VISUAL Message Center Debugging Agent ...... 16 3.1.7. Open Chat...... 16 3.1.8. System Explorer...... 17 3.1.9. Source Member Explorer ...... 17 3.1.10. Alarms ...... 17 3.1.11. Action Sets ...... 17 3.1.12. Show Alarm Log...... 17 3.1.13. Filters in this Business View...... 17 3.1.14. Colors in this Business View...... 17 3.1.15. Zoom In/ Zoom Out...... 19 3.1.16. Print...... 19 3.1.17. Adjust List...... 20 3.1.18. AccessServer...... 20 3.1.19. Exit ...... 20 3.2. Hotkeys ...... 20 3.3. Menu Bar ...... 20 3.3.1. File Menu ...... 20 3.3.2. Change Menu...... 21 3.3.3. Connections Menu ...... 22 3.3.4. View Menu ...... 22 3.3.5. List Menu...... 23 3.3.6. Window Menu ...... 25 3.3.7. Options Menu...... 25 3.3.8. Tools Menu ...... 30 3.4. Status Bar ...... 35 3.5. System Tray Icons ...... 35 3.6. Message Types...... 36

Chapter 4

Security ...... 38

4.1. AccessServer...... 38 4.2. AccessServer Management...... 39 4.2.1. Log Out ...... 39 4.2.2. Manage Roles...... 39 4.2.3. Manage Security ...... 39 4.3. Auditing Using AccessServer...... 44

Chapter 5

Calendars...... 46

5.1. Range Sets ...... 47 5.2. Exclusion Ranges ...... 50 5.3. Creating Calendars ...... 50 5.4. Example ...... 51 5.5. Importing Calendar Settings ...... 53 5.6. Activity Calendars ...... 53 5.7. Using Calendars in Reports ...... 55 5.8. Using Calendars in Goals ...... 57

Chapter 6

Business Network ...... 59

6.1. What is a Business View?...... 60 6.1.1. Business View Substates...... 60 6.1.2. Substate Criticalness Views...... 62 6.2. What is a Folder?...... 62 6.2.1. Types of Folder ...... 62 6.2.2. Basic Service Control Point...... 63 6.3. Folder Criticalness Management ...... 63 6.3.1. Substate Criticalness Propagation Configuration...... 64 6.3.2. Global Criticalness Calculation Configuration...... 69 6.4. Criticalness Alarms for Folders ...... 71 6.5. Business Network Pane...... 71 6.5.1. Rename ...... 72 6.5.2. New...... 72 6.5.3. Copy...... 72 6.5.4. Paste...... 72 6.5.5. Paste (Business Views as links) ...... 73 6.5.6. Paste as Link ...... 73 6.5.7. Multiple Copy...... 73 6.5.8. Delete ...... 74 6.5.9. Add Shortcut ...... 74 6.5.10. Type of Folder...... 74 6.5.11. Criticalness Management...... 74 6.5.12. Edit Filters ...... 76 6.5.13. Edit Colors...... 77 6.5.14. Set Icon...... 77 6.5.15. Collapse/Expand...... 78 6.5.16. Business Value ...... 78 6.5.17. Import & Export ...... 78 6.5.18. Refresh...... 81 6.5.19. Information ...... 81

6.6. Business Shortcuts Pane...... 82 6.6.1. Rename...... 82 6.6.2. New...... 82 6.6.3. Copy...... 83 6.6.4. Delete...... 83 6.6.5. Edit Filters ...... 83 6.6.6. Edit Colors...... 84 6.6.7. Sort Chronologically...... 85 6.6.8. Large/Small Icons ...... 85 6.6.9. Export To ...... 85 6.6.10. Import From ...... 85 6.6.11. Reset Criticalness ...... 86 6.6.12. Refresh...... 86 6.7. Message Grid...... 86 6.7.1. Event Tab...... 87 6.7.2. Variables Tab...... 87 6.7.3. User Defined Variables Tab...... 88 6.7.4. Global Variables Tab...... 88 6.7.5. Hide Selected Messages ...... 89 6.7.6. Unhide Messages ...... 89 6.7.7. Select All ...... 89 6.7.8. Message Text ...... 89 6.7.9. System Properties...... 89 6.7.10. Capture with iSeries Support Agent ...... 89 6.7.11. Debug with VISUAL Message Center Debugging Agent ...... 89 6.7.12. Open Chat ...... 90 6.7.13. Execute Actions Set ...... 90 6.7.14. Adjust List ...... 90 6.7.15. Columns...... 90 6.7.16. User Columns ...... 91 6.7.17. Show Groups ...... 93 6.7.18. Show Grid ...... 94 6.7.19. Hide Speed Filters...... 94 6.7.20. Save to HTML ...... 95 6.7.21. Save to XML...... 95 6.7.22. Save to XLS ...... 96 6.7.23. Save Business View Style ...... 96 6.7.24. Load Business View Style...... 97 6.7.25. Sort Chronologically ...... 97 6.7.26. Print...... 97 6.8. Analysis Pane ...... 97 6.8.1. Problem Root Causes Pane...... 98 6.8.2. Real-Time Impact Analysis Pane...... 99

Chapter 7

Enterprise Network...... 102

7.1. Enterprise Views Panel...... 104 7.1.1. Customizing How Enterprise Views are Displayed ...... 104

7.1.2. Opening an Enterprise View ...... 104 7.1.3. Creating an Enterprise View ...... 105 7.1.4. Customizing an Enterprise View ...... 105 7.1.5. Customizing the Enterprise View Icons...... 105 7.1.6. Adding and Removing Icons to an Enterprise View...... 106 7.1.7. Renaming Enterprise View Icons...... 107 7.1.8. Creating Links to other Enterprise Views...... 108 7.1.9. Creating Links to Web Sites...... 109 7.1.10. Open, Rename and Delete Enterprise Views ...... 110 7.1.11. Creating an Enterprise View Using Multiple Copy ...... 110 7.1.12. Importing & Exporting Enterprise Views...... 115 7.1.13. Using Enterprise Views...... 116 7.2. Filter Panel...... 117 7.2.1. Filter Search Button ...... 118 7.3. Categories...... 118 7.3.1. Creating Categories ...... 118 7.3.2. Assigning a Category to an Enterprise View...... 118 7.3.3. Giving Permission for a Category ...... 119 7.3.4. Using Categories...... 121 7.3.5. Viewing which Categories are Assigned to Enterprise Views ...... 122 7.3.6. Managing Categories...... 123 7.4. Message Storage...... 123

Chapter 8

Working with Console Filters...... 124

8.1. Speed Filters...... 125 8.2. Groups ...... 125 8.3. Column Filters...... 125 8.4. Filter by Date...... 126 8.5. Quickly Executing Action Sets ...... 126 8.6. Agent Subscriptions ...... 126 8.7. Color Coding Messages...... 126 8.8. Filters in this Business View ...... 127 8.8.1. Hyperhashing...... 128 8.8.2. General Tab ...... 130 8.8.3. System i Tab ...... 136 8.8.4. ThinkServer Tab...... 138 8.8.5. Console Tab...... 140 8.9. How to Configure a Filter ...... 141 8.10. Storing Business View Filters ...... 143 8.10.1. Importing and Exporting Business View Configurations ...... 143 8.10.2. Saving Business View Contents to HTML, XML, and XLS ...... 144 8.11. Saving Business Network and Alarms Hierarchies...... 144

Chapter 9

Preprocessing ...... 146

9.1. Preprocess Filter List Window ...... 146 9.1.1. Preprocess List Hierarchy...... 147 9.2. Creating Preprocesses ...... 147 9.2.1. Filters ...... 147 9.2.2. Expression List...... 147 9.2.3. Advanced ALEV Filter Editor...... 148

Chapter 10

Alarms...... 150

10.1. Why Configure Alarms? ...... 150 10.1.1. Protecting Your Alarms ...... 151 10.2. Setting an Alarm Filter ...... 151 10.3. Setting Alarm Actions ...... 153 10.3.1. E-mail Action ...... 154 10.3.2. Audible Alarm – Sound ...... 158 10.3.3. Execute a PC Program ...... 158 10.3.4. Annotate in the Windows Event Log ...... 159 10.3.5. Show a Window – Visual...... 161 10.3.6. Execute a SNMP Trap ...... 162 10.3.7. Execute a DLL Function ...... 162 10.3.8. Execute an OS/400 Command Sequence ...... 163 10.3.9. Reply to Message ...... 166 10.3.10. Sending and Replying to Messages via SMS or E-mail with Notifier 167 10.3.11. Send a Remote Message (Net Send Function) ...... 168 10.3.12. Send a Message to an Escalation List ...... 169 10.3.13. Setting Action Sets...... 170 10.3.14. Creating Dependencies...... 172 10.3.15. Pre-Actions...... 173 10.3.16. Post-Actions...... 174 10.3.17. Repetitions ...... 174 10.4. Activating and De-Activating Alarms...... 175 10.5. Alarm Log ...... 176 10.6. Saving or Exporting your Alarm Configuration...... 177 10.6.1. Exporting or Importing the Entire Configuration...... 177 10.6.2. Exporting or Importing Individual Alarms, Calendars, Actions Sets, Special Days, Address Books, or SMTP Server Lists ...... 178 10.7. Getting the Most Out of Your Alarms ...... 179 10.8. Alarms Summary ...... 180

Chapter 11

Business Services Management (BSM)...... 181

11.1. Business Process Modeling...... 182 11.2. Problem Root Cause ...... 183 11.3. Impact Analysis...... 183 11.4. Service Control Point ...... 183 11.5. Business Values ...... 184 11.5.1. How to add a Business Value ...... 184 11.5.2. Using Business Values ...... 185 11.5.3. Using Formulas for Business Value...... 187 11.6. Cause/Effect Criticalness Management...... 187 11.7. BSM Engine ...... 188 11.8. BSM Reporting...... 188 11.8.1. Service Control Point Listing...... 189 11.8.2. Service Control Point Overview ...... 189 11.8.3. Service Control Point Detail ...... 190 11.9. BSM License...... 191 11.9.1. Importing & Exporting with BSM Active...... 192

Chapter 12

User-Defined Variables...... 193

12.1. Creating and Defining Per Message Variables ...... 194 12.2. Creating and Defining Global Variables...... 195 12.2.1. Persistent Variables ...... 196 12.3. Tips for Using Pre-processing and User-Defined Variables ...... 196 12.3.1. Example 1: Using Per Message Variables...... 196 12.3.2. Example 2: Clean Up Windows Server using Global Variables and Post Actions...... 197 12.4. User Defined Functions ...... 197

Chapter 13

Getting the Most Out of SmartConsole...... 200

13.1. Using SmartConsole with iSeries Support Agent ...... 200 13.2. Using SmartConsole with Performance Agent...... 202 13.2.1. Real Time Performance Monitoring ...... 202 13.2.2. Detailed Performance Information ...... 202 13.2.3. Response Times ...... 202 13.2.4. Customizable Alerts ...... 203 13.3. Using SmartConsole for Problem Diagnosis...... 203 13.3.1. Serious System Conditions...... 203

13.3.2. Job Details ...... 204 13.4. Using VISUAL Message Center for Automating Operations...... 205 13.4.1. Automated Operations Examples ...... 205 13.4.2. Automation Tips ...... 205 13.5. Using VISUAL Message Center for Security Alerts ...... 205 13.6. Integrate SMS and E-mail Message Support into Your System Applications ...... 206

Chapter 14

SmartConsole High Availability Options ...... 207

14.1. Installing SmartConsole as a Service in Windows NT / 2000 ...... 207 14.1.1. Minimum Knowledge of Services...... 207 14.1.2. VISUAL Message Center as a Service ...... 207 14.2. Smart Reconnect ...... 208 14.3. Connection Time-out...... 208 14.4. Monitor Checking ...... 209 14.5. Console Mode...... 209 14.5.1. What Happens in Resilient Mode?...... 210 14.6. Options for Sending Alerts ...... 210 14.7. Clustering...... 211

Chapter 15

SmartConsole Web Client...... 212

Appendices

Appendix A: Automating the Export of SmartConsole Configuration Files213 A.1. Scheduling Backups ...... 213 A.2. Directories to Backup ...... 215

Appendix B: ALEV Logical Expression eValuator...... 216 B.1. ALEV Functions Specific to SmartConsole ...... 216 B.1.1. Set Icon...... 216 B.1.2. Retrieve Criticalness...... 216 B.1.3. Changing Criticalness...... 217 B.1.4. Adding a Reason to the Criticalness Change ...... 218 B.1.5. Add a Business View Filter to an Alarm ...... 218 B.1.6. Including an Event ID in a Business View Filter ...... 218 B.1.7. Verify Calendar Date ...... 218 B.1.8. Execute an Action Set ...... 219 B.1.9. Retrieve an LDAP Attribute...... 219

B.1.10. Export a Business View...... 219 B.1.11. Export Business Views to XLS, XML, or HTML Format...... 219 B.1.12. Convert SID to an Account Name...... 219 B.1.13. Activate or Deactivate an Alarm Folder ...... 219 B.1.14. Retrieve an Array with All Calendar Names ...... 220 B.2. Advanced Service Functions ...... 220 B.2.1. Retrieve the Internal ID from a Business View ...... 220 B.2.2. Retrieve an Array with All Names from a Business View Defined in the Business Tree...... 220 B.2.3. Retrieve an Array with All the Service Control Points and Basic Service Control Points on which a Business View is Impacting...... 220 B.2.4. Retrieve the Message from the Last Change of State from a Business View...... 221 B.2.5. Retrieve the Business Value for a Service Control Point...... 221 B.2.6. Retrieve the Total Business Value from the Impacted Service Control Point ...... 221 B.2.7. Set a Business Value for a Service Control Point...... 221 B.3. Business Tree Modification Functions...... 221 B.3.1. Check if a Folder Exists in the Business Tree ...... 221 B.3.2. Check if a Business View Exists in the Business Tree...... 221 B.3.3. Move a Folder to a New Destination in the Business Tree...... 221 B.3.4. Move a Business View to a New Destination in the Business Tree...... 222 B.3.5. Make a Multiple Copy of a Folder in the Business Tree ...... 222 B.3.6. Make a Multiple Copy of a Business View in the Business Tree...... 222 B.3.7. Delete a Folder from the Business Tree...... 223 B.3.8. Delete a Business View from the Business Tree...... 223 B.4. Using UNIX/Linux Messages at the SmartConsole ...... 223 B.4.1. Example 1: New User Creation ...... 223 B.4.2. Example 2: Security Alert ...... 224

Appendix C: Increasing Windows Registry Size...... 225

Appendix D: Disk-Usage & Message-Processing Tests...... 226 D.1. Performance Tests ...... 226 D.1.1. Host Configuration...... 226 D.1.2. Virtual Machine Configuration ...... 226 D.2. Software Architecture ...... 227 D.3. Results ...... 227 D.3.1. Database Disk Usage...... 227 D.3.2. Message Processing ...... 228

Appendix E: Hotkeys ...... 229 E.1. Business Tree Hotkeys...... 229 E.2. Business List ...... 229 E.3. Messages List...... 230 E.4. Enterprise View ...... 230 E.5. Alarms ...... 231

Appendix F: Contacting Tango/04...... 232

Glossary...... 234 Index...... 252 List of Figures...... 259 About Tango/04 Computing Group ...... 269 Legal Notice...... 270

How to Use this Guide

This chapter explains how to use Tango/04 User Guides and understand the typographical conventions used in all Tango/04 documentation.

Typographical Conventions The following conventional terms, text formats, and symbols are used throughout Tango/04 printed documentation:

Convention Description

Boldface Commands, on-screen buttons and menu options.

Blue Italic References and links to other sections in the manual or further documentation containing relevant information.

Italic Text displayed on screen, or variables where the user must substitute their own details.

Monospace Input commands such as System i commands or code, or text that users must type in. Keyboard keys, such as CTRL for the Control key and F5 for the UPPERCASE function key that is labeled F5.

Notes and useful additional information.

Tips and hints that will improve the users experience of working with this product.

Important additional information that the user is strongly advised to note.

Warning information. Failure to take note of this information could potentially lead to serious problems.

Chapter 1 1 Introduction

VISUAL Message Center SmartConsole provides an organization with visibility based on the alignment of IT infrastructure with business processes. It filters, categorizes and manipulates data so that personnel can respond to the most business-relevant problems first. SmartConsole´s automated features save time, and configurable features give users powerful control. Plus, it is compatible with most industry standard hardware and software.

Applications and services are essential to business processes, and organizations typically have several dozen to monitor. SmartConsole allows the business to have complete, powerful visibility over its business-critical applications and services, even in complex multiplatform environments. The following figure demonstrates the role and the monitoring potential of SmartConsole.

Figure 1 – SmartConsole allows you to stay in control of your business processes and IT applications on a wide variety of platforms

There are currently two distinct SmartConsole options, each with their own features and limitations:

• SmartConsole Kernel (Windows based engine)

• SmartConsole Web Client (Includes SmartConsole Kernel)

For more information on SmartConsole Web Client, see the SmartConsole Web Client User Guide.

VISUAL Message Center is a multiplatform client-server software system that monitors applications, databases, business services and processes and more, thus avoiding the need for system operators or programmers to manually monitor every component of a company's infrastructure. VISUAL Message Center centralizes all the operating health information coming from multiple sources and identifies and reacts to situations that can impact on critical business processes.

VISUAL Message Center continuously monitors your systems to find and resolve events that may be problematic such as bottlenecks in the IT infrastructure underlying your business processes. With VISUAL Message Center, it is no longer necessary to rely on end-users to report application errors, and you can be sure critical events will not go unnoticed. You can receive an alert or even monitor a situation in real time to ensure problems are dealt with before they even occur, and importantly before any damage is done, saving you time, and improving the agility of your business.

All events detected by VISUAL Message Center are retrieved by ThinkServer and stored in a centralized database, and being completely configurable it only retrieves the events that need to be seen. Events are then accessed by other VISUAL Message Center products to provide complete error message information in a variety of formats to suit you, such as historical reports, real-time dashboards or alerts by SMS or e-mail.

As many VISUAL Message Center products are Web-based accessing centralized data, many people can work with VISUAL Message Center at the same time, wherever they are. 1.2 How Does VISUAL Message Center Work?

VISUAL Message Center is set up in four layers, or groups, of products, based on their function and relationship to other products. The flow of events is taken through a recollection stage, where events are gathered from the various sources connected via ThinkServer. Events then get passed through to the correlation layer (wherein lies SmartConsole) for filtering and acting upon. Finally, events get delivered to different products in the presentation layer, where visualization tools allow for easy viewing.

Figure 2 – VISUAL Message Center overview; SmartConsole is a Correlation Layer product.

1.2.1 Collection Layer

Monitors are created to collect events via ThinkServer and various ThinAgents from a wide range of platforms, databases and hardware. The events are then stored in databases to be accessed by other VISUAL Message Center products.

Tango/04 Collection Layer products: Orchestrator, Applications Agent, Performance Agent. 1.2.2 Correlation Layer

In the Correlation Layer, actions are applied to the stored and collected events to organize and send them onwards for viewing or reporting.

Tango/04 Correlation Layer products: Goals and SmartConsole. 1.2.3 Presentation Layer

The gathered information is finally presented via Reports or Dashboards through Web interfaces. Both historical and real-time information is visualized in graphs, reports and gauges. Information can be pulled directly from the Collection Layer or from the filtered results in the Correlation Layer.

Tango/04 Presentation Layer products: Reports, Dashboards, and SmartConsole Web Client. 1.2.4 Middleware Components

The three layers are supported by a few applications to handle security, shared objects and shared databases. Proprietary middleware is used to connect to the various systems that the information is retrieved from. Finally, nearly one thousand ThinAgents are available supporting most major operating systems, network devices and hardware.

Tango/04 middleware products: AccessServer, SharedObjects, NiceLink, PMDB, various ThinAgents, and Database Settings Administrator. 1.3 SmartConsole Features

Organizations that use SmartConsole know the business impact of issues in real time. SmartConsole is a centralized solution to an organization with fragmented IT systems. Automated tasks and alarms help to streamline organizational processes. Multiuser, multi-console capable SmartConsole is cloud-ready and tablet-enabled, so your organization can keep pace with modern technology. 1.3.1 Preprocessing

User-defined preprocesses act on events before they proceed into further SmartConsole filters. Used in combination with Arithmetic-Logic Expression eValuator (ALEV) scripts, preprocessing makes changes to an event, for example, adding an identifier so that it appears in one of your Business Views. Preprocessing is a potent feature that allows users to configure a wide range of customized automations. The process is illustrated as follows.

Figure 3 – Preprocessing within the SmartConsole allows for powerful automated dependency mapping 1.3.2 Business Views and Enterprise Views

In SmartConsole, a Business View is a powerful visualization tool that shows the impact of IT infrastructure and business processes on your organization in terms of real value. When a problematic event is discovered by SmartConsole, your Business View reflects a change in health status by turning red, and you can drill-down to see not only what the root-cause of the problem is, but its actual impact on the business in a weighted point system. IT personnel can focus on the most business-relevant issues first, adding value to the organization. The following figure shows the appearance of Business Views.

Figure 4 – Manipulation of your Business Tree is almost instantaneous, no matter the number of components

An Enterprise View is a conglomerate of Business Components, and provides a different, non- hierarchichal view. Easy to create, an Enterprise View keeps you informed as to the impact of the health of your individual Business Views on your Enterprise View as a whole. For example, an Enterprise View could change status if an qualifying event occurs in a Business View for printing, credit card transactions, total policies, or even an unforeseen problem of a nontechnical nature, for example, a broken transportation line or a depleted inventory. The appearance of Enterprise Views is shown in the following figure.

Figure 5 – Enterprise Views in SmartConsole 1.3.3 Automation SmartConsole has many autonomic computing properties and is designed to:

• reduce the number of common tasks performed manually

• alert users only to significant issues and potential problems

• manipulate data so that it takes on a specifically desired flow

Pre-actions and post-actions Just as soon as an event is picked up by the alarm filters, SmartConsole can perform a pre-action. After the alarm is triggered (and the corresponding actions and action sets called), SmartConsole performs a post-action.

Alarms and action sets: SmartConsole reduces costs and increases efficiency by centralizing the multitude of operating health messages your organization is faced with. Users are not only notified of issues, but they are informed by SmartConsole as to their diagnoses, and even aided by SmartConsole in solving them.

SmartConsole screens every event for user-defined alarm parameters. If an event passes through this alarm filter, the user is immediately alarmed on the console; alarms can be sent as e-mails and SMS messages. Alarms are also compared against user-defined action set parameters. If a user wants an immediate and automatic response to an alarm without manually interfering, the user can assign an alarm action or action set for SmartConsole to take automatically. The alarms system process is illustrated as follows:

Figure 6 – SmartConsole alarm processes

Alert escalation list SmartConsole features two-way alerting. In case of an alarm, SmartConsole will notify the first person on the escalation list. If it receives no reply within a user-defined period of time, it will continue to notify the people on the list, in order, until someone responds.

Repetition suppression For those events that occur too frequently, for example, a positive Ping event, SmartConsole can be configured to not display the event in the console.

Event anticipation SmartConsole has the ability to recognize that an expected event did not occur, in which case action sets can be run. For example, if a critical batch process is not completed on time, SmartConsole can notify operators immediately instead of after the fact. 1.3.4 Filters

Filters in SmartConsole are designed to limit the number and type of events processed and displayed in the console. Because they are user-made, you can create filters that are especially useful to your organization. SmartConsole filters incoming events to determine actions related to:

• Alarms, action sets, preprocesses and criticalness

• Business Views

• ThinkServer

The following illustration depicts the SmartConsole filtering system:

Figure 7 – Events are screened through several filters, and can affect many SmartConsole features.

Pattern matching The SmartConsole engine features pattern matching, which increases processing speed, enabling the engine to process millions of events per day.

Hyperhashing This Tango/04 technology supercharges SmartConsole´s event processing speed. This is especially useful in complex, multi-platform environments with enormous quantities of data. When properly configured, Hyperhashing rapidly performs actions on events as they enter Business View and/or alarm filters.

Advanced ALEV Filter Editor This feature of SmartConsole allows users to create actions on filtered events before they reach the console. Expressions are constructed using both out-of-the-box and user-defined variables and functions. ALEV scripts can be used in conjunction with Alarms, Preprocesses, and Business Views. 1.3.5 Resilient and Non Resilient Mode

SmartConsole can collect and process events even when powered off: resilient mode is a safeguard against losing data and events during downtime. Non resilient mode cuts down on latency and gives the user the flexibility to start and stop event flow. 1.3.6 Multiple Console Usability

Many SmartConsole Kernels can exist, and users can have a customized view of relevant machines. For example, install consoles and configure user-specific Business Views for:

• IT: Application architects can test developments while systems operators and security officers can stay informed of issues within IT Infrastructure.

• Accounting: to receive events based on an accounting code criteria and can monitor financial applications.

• Operations: ensure that Service Level Analytics (SLAs) fall within organizational standards, and monitor enterprise applications.

• Customer Relations: to monitor CRM applications.

• External consultants or service providers: to work securely and efficiently on your important projects.

1.3.7 In-Memory Database Deletion System

SmartConsole governs its own disk usage by clearing the oldest events to make space for new ones. This protects your database from data overload problems, and it is user-adjustable, so you have even more control over historical events. 1.4 Security

Not only does SmartConsole provide visibility, it is also a solution for security. The engine´s pattern matching intelligence along with user-defined security parameters of filters police the event log and ensure the safety of your applications and business processes that undermine your company. Create a SmartConsole connection for your security manager, who can be notified instantly of any security related events. 1.5 How does SmartConsole work?

SmartConsole receives events from either iSeries servers or ThinkServer through NiceLink. Events are screened by preprocess filters, where they may be modified. Then, events flow through alarm filters, where, provided they meet alarm criteria, they are sent to the console for visualization, or as an e-mail or SMS alert. If alarms aren´t tripped, the events can still be modified, and are sent to the criticalness management engine, where they are compared against criticalness values. Next, events are processed for Business View and Enterprise View updates. If your SmartConsole includes a Business Services Management (BSM) engine, events appear in the console to reflect Business Values. Finally, events flow to the in-memory database deletion system. There, events are stored or deleted according to user configurations. The following diagram shows event flow in SmartConsole.

Figure 8 – Event flow in SmartConsole 1.6 Terms and Definitions

AccessServer AccessServer is Tango/04’s security solution. It provides security-related services to other Tango/04 applications providing a central database for authentication and authorization services. It is fully incorporated in SmartConsole.

Database Settings Administrator

This Tango/04 middleware permits the configuration of database connection settings for each VISUAL Message Center product. Scheduled maintenance tasks to be performed by the Tango/04 Maintenance Service component are configured here as well.

Health There are five possible health values that represent the current monitor status: monitoring error, critical, warning, minor and success. The user can define monitor health conditions with the Health and Actions Wizard. When defining the health condition assignment you can use any of the variables available in the

monitor. Every time the data source state is refreshed the configured health scripts are executed to assign the new monitor health.

Monitor Any instance of a ThinAgent. For example, to monitor the availability of two different computers on the network you should create two different monitors of the Ping monitor class (i.e. ThinAgent); one for each IP address.

NiceLink NiceLink is a network protocol created by Tango/04 to manage different communication protocols, such as TCP/IP, APPC and SNA Server, allowing VISUAL Message Center SmartConsole (and other Tango/ 04 products) to communicate with servers running different operating systems and different network protocols.

Python Python is a dynamic object-oriented programming language that can be used for many kinds of software development. It offers strong support for integration with other languages and tools, comes with extensive standard libraries, and can be learned in a few days. Many Python programmers report substantial productivity gains and feel the language encourages the development of higher quality, more maintainable code.

Reports The Reports module provides powerful methods of creating reports based on historical data using other VISUAL Message Center solutions. As it is web-based it provides a very flexible interface in a platform independent solution. It connects to the VISUAL Message Center databases and uses the selected data to view reports on performance, users, security, auditing and much more. Please see the VISUAL Message Center Reports User Guide for further information on the available functions and reports.

SharedObjects

This Tango/04 middleware is a central repository for data that Tango/04 products share in common, for example, configurations, thus preventing repetitive entries and negating inconsistencies from product to product.

System i Also known as AS/400 or iSeries. A type of computer developed by IBM. It has an integrated DB2 database and is capable of supporting multiple instances of: AIX, Linux, Windows 2000 and Windows 2003.

SmartConsole SmartConsole is the VISUAL Message Center client´s event correlation console. It is a powerful tool that enables you to control your infrastructure and business processes. SmartConsole receives events via NiceLink and can perform actions on the messages (according to filters), simply display them in the console, or manage them to show the status of your business.

ThinAgent Classes of monitors installed in the ThinkServer, the ThinAgents available in VISUAL Message Center ThinkServer will differ depending on what libraries you have on your server at the time of installation. A few examples are the Port, Ping and SMTP Connect.

ThinkServer The server component of VISUAL Message Center ThinkServer. The ThinkServer contains all the reusable logic and stores the configuration the user sets in the ThinkServer Configurator. Therefore the ThinkServer can run independently from the Configurator. The ThinkServer usually runs as a Windows Service on the machine.

ThinkServer Configurator The graphical client component of VISUAL Message Center ThinkServer. Here you can configure monitors, connect to one or more ThinkServers on your system, and view messages received from the ThinkServer. Note a ThinkServer Configurator can be connected to more than one ThinkServer, and one ThinkServer may be connected to more than one ThinkServer Configurator.

Chapter 2 2 Starting VISUAL Message Center SmartConsole

To start VISUAL Message Center SmartConsole: Step 1. Click the Windows Start menu and select All Programs > Tango04 > VISUAL Message Center SmartConsole > SmartConsole.

Step 2. When the VISUAL Message Center splash screen appears you will be asked to define your systems in the NiceLink Configurator. Click OK to start the NiceLink Configurator.

Note If a system was previously configured, NiceLink Configurator setup will not be required. In such a case steps 2-4 will be skipped.

Step 3. Select the system(s) that you would like to monitor with SmartConsole by double- clicking them or dragging them to the Selected Systems area.

Figure 9 – Selecting systems to monitor from NiceLink

Important When two or more ThinkServers share a database, you only need to select one of them here. Do not select both (or all) of the ThinkServers: this will cause a duplication of events sent to SmartConsole.

Figure 10 – Select any one of the ThinkServers if they share a database

However, when the ThinkServers have separate databases, it is necessary to select both ThinkServers here (or all, as the case may be).

Figure 11 – Selecting two ThinkServers to monitor when setting up SmartConsole, because the ThinkServers each have their own separate database

Step 4. Click OK once you have added all required systems to your VISUAL Message Center sessions. The AccessServer login screen appears.

Step 5. Enter the user and password details for AccessServer and click Sign-On.

Note When you attempt to connect to VISUAL Message Center on an iSeries with a user profile different than the one used when installing the product, you may receive an error saying that the user is not authorized to use the product on the selected system. To solve this problem, add this user profile on the iSeries side of the product (see the VISUAL Message Center (iSeries Modules) User Guide for instructions on adding a user).

Chapter 3 3 VISUAL Message Center SmartConsole

The VISUAL Message Center SmartConsole opens with the Business Network view. You can switch between the Business Network view and the Enterprise Network view by clicking on the respective tabs located just under the toolbar.

The Business Network view is made up of 4 panes:

• the Business Shortcuts pane on the left

• the Business Network column located center-left

• the Message Grid at the top-right, and

• the Analysis pane at the bottom right

Figure 12 – SmartConsole’s main message console – Business Network view

The icons in the two panes on the left of the Business Network view help you to instantly check if important events have been received in a specific Business View, as the color of the icon and folder will change from green to blue, yellow, or red according to the criticalness of the message received.

Select the Business View in either of these two panes to view its messages in the message grid and see what impact the problem has on your business processes in the real-time impact analysis pane. The messages help you locate the problem and drill down for event details to help solve the problem. The analysis pane helps determine the importance of the error to the business and helps the managers allocate resources where it really matters.

For details about working with the Business Network and Enterprise Network views Chapter 4 - Business Network on page 38 and Chapter 5 - Enterprise Network on page 74.

A wide range of functions is available in the SmartConsole. Some functionality is available from the menus at the top of the SmartConsole. The most frequently used functions are available from the toolbar just beneath the menus. More functionality that is specific to a particular area of the SmartConsole (for example the message grid) is available by right clicking anywhere in the particular area. 3.1 Toolbar

The buttons on the toolbar represent the functions you will use most frequently in VISUAL Message Center SmartConsole.

Figure 13 – SmartConsole Toolbar is located at the top of the Window

More functionality specific to a particular area of the SmartConsole (for example the message grid) is available by right clicking anywhere in the particular area. These functions are described in Chapter 4 - Business Network on page 38.

Other functions are available from the menus at the top of the SmartConsole. These functions will be discussed in a later section. 3.1.1 Select Connections

Click this button to open NiceLink Configurator. Here, you can select the system connections to collect messages from. Double-click the desired system in the top-right pane to select the system. The system will appear in the Selected Systems pane at the bottom of the NiceLink Configurator window.

Once you have selected all the connections you are interested in, click OK. You will be asked for your user ID and passwords for the different systems, where required. 3.1.2 View Current Connections

Click this button to open the View Current Connections dialog box, where you can see the status of the connections. If there are inactive connections, you will be able to reconnect them here. You can also see the status of the monitor jobs on the iSeries (BD_MONITOR and KRNSUP).

Figure 14 – Viewing your current connections

To check and/or restart any of the monitors, use the drop-down menu. It may take a moment before the information is refreshed. If an attempt to start a monitor fails for any reason, you will see a message in the Cause column.

Note Interactive and Batch monitor correspond to the BD_MONITOR, which is the job that monitors interactive and batch messages on your iSeries.

3.1.3 Remove Connections

Click this button to view the connections status and remove the connections you do not want to work with. 3.1.4 Refresh

Click this button to execute a manual refresh of the message grid. You can also press the function key F5. This button also contains a drop-down menu in which you can quickly choose the date filter, using the last 24 hours, the last 48 hours, the last week, or all dates. Custom calendars and time lapses can also be set. These date filters apply to the selected Business View only. 3.1.5 Capture with VISUAL Message Center iSeries Support Agent

If you have VISUAL Message Center iSeries Support Agent installed on your PC you will be able to capture jobs that produce errors by clicking this button. Otherwise this function is disabled. For more information about iSeries Support Agent, please see the VISUAL Message Center iSeries Support Agent User Guide. 3.1.6 Debug with VISUAL Message Center Debugging Agent

If you have VISUAL Message Center Debugging Agent installed on your PC, click this button to capture and debug jobs that produce errors. Otherwise this function is disabled. For more information about Debugging Agent, please see the VISUAL Message Center Debugging Agent User Guide. 3.1.7 Open Chat

If you have iSeries Support Agent or Debugging Agent installed, you will be able to open a chat session with the user of the job that produced the error message. Otherwise this function is disabled. Consult the VISUAL Message Center iSeries Support Agent or Debugging Agent User Guides for details on how to use this function.

3.1.8 System Explorer

If you have iSeries Support Agent or Debugging Agent installed, you will be able to explore system objects by clicking this button. Otherwise this function is disabled. Consult the VISUAL Message Center iSeries Support Agent or Debugging Agent User Guides for details on how to use this function. 3.1.9 Source Member Explorer

If you have iSeries Support Agent or Debugging Agent installed, you will be able to explore source members by clicking this button. Otherwise this function is disabled. Consult the VISUAL Message Center iSeries Support Agent or Debugging Agent User Guides for details on how to use this function. 3.1.10 Alarms

Click this button to configure the Alarms. For further details on how to use alarms Chapter 9 - Alarms on page 119. 3.1.11 Action Sets

Select this button to configure the action sets associated with alarms. For further details on how to use action sets section 9.3.13 - Setting Action Sets on page 142. 3.1.12 Show Alarm Log

Click this button to show the alarm log. The alarm log appears in a new window. The alarm log shows information about the execution of the alarms. If any problems occurred while executing an alarm, the information will be displayed here.

Figure 15 – Example of an alarm log 3.1.13 Filters in this Business View

Click this button to open the Display Filters window where you can configure the Display Filter for the selected Business View. For details section 7.9 - Filters in this Business View on page 98. 3.1.14 Colors in this Business View

All messages displayed in the console can be color coded for easy identification. You can change the displayed background and the foreground colors of a message.

Use Colors in this Business View to color-code particular sets of messages.

Example of using colors in a Business View

Mark all console messages with a red background and a white foreground so that the operator can easily pick out problems from the list in the message grid. The colored console messages will appear between the other messages in the message grid, but will be easy to pick out as they are displayed as a bright red bar with the message in white letters.

Click this button to configure the Color Filter List for the selected Business View. The following window appears.

Figure 16 – Configure a color filter for a Business View to distinguish important messages at a glance.

To create a color code for the selected Business View: Step 1. Create a filter to use as selection criteria for the color code

Step 2. Click the New Color Filter button at the top left of the menu bar to open the Filter Configuration window.

Step 3. Add your conditions for the filter and click OK to confirm.

Note If you do not configure a filter, but do change the color settings here, all the messages for the selected Business View will appear according to the colors you selected.

In the Color Filter List window you can now configure the colors for the filter as follows:

• To change the foreground color, that is the color in which the text will appear in, click the desired block of color. The letters FG will appear in the block of color you selected.

• To change the background color, that is the color in which the row background will appear, right-click the desired block of color. The letters BG will appear in the block of color you selected.

Note If you have selected both the foreground and the background color to be the same the selected block of color will contain the letters FB.

In our example we selected a red background and a white foreground. As you can see in Figure 16 on page 18, the red block of color has the letters BG to indicate this is the background color and the white block of color has the letters FG to show this is the foreground color. The section below the blocks of color displays how the messages for this filter will appear in the message grid.

Click OK to accept your changes.

Figure 17 – Example of a Business View with a color filter

Example of how to color code messages pending a response.

Select a Business View and click the Colors in this Business View button to open the Color Filter List and create a new include filter. Open the System i tab and select message type. Deselect all the options except for Answer Pending. Then select the colors that you want to apply to your answer pending messages.

Color filters are applied to messages in the order that they appear in the Color Filter List. To change the order and thus the priority of a filter, select the filter you want to move and use the up and down buttons to move the filter. You can also drag a filter to the required place in the list. 3.1.15 Zoom In/ Zoom Out

Click these zoom buttons to increase or decrease the message text size. The zoom does not affect the text size of the Business Network Columns and the Shortcuts pane. 3.1.16 Print

Click this button to print the grid with the current message data in it. This uses the screen display configuration that you are using, so you will see the headings and order that you have selected.

3.1.17 Adjust List

Click this button to regroup all columns shown on the screen. Adjust list resizes all of the columns in the message grid in one go, so that all columns fit in the current window size. If you resize the window you may want to repeat this operation. 3.1.18 AccessServer

Click this button to log out of AccessServer. Once clicked, the AccessServer Windows User Authentication window will appear allowing another user to log in. 3.1.19 Exit

Click this button to exit SmartConsole. 3.2 Hotkeys

Many of the most common functions in VISUAL Message Center can also be activated using hotkeys (special key combinations). For a list of available hotkeys Appendix E: Hotkeys on page 229. 3.3 Menu Bar

Most functionality is available from the Menu Bar at the top of the SmartConsole and will be discussed in this section.

Figure 18 – Menu Bar

For details of functionality available from the toolbar section 3.1 - Toolbar on page 15.

More functionality specific to a particular area of the SmartConsole (for example the message grid) is available by right clicking anywhere in the particular area. These functions are included in the descriptions of the different areas in Chapter 6 - Business Network on page 59. 3.3.1 File Menu

Figure 19 – The File Menu includes the functions Export Configuration File, Import Configuration file, Print and Exit

Export Configuration File Use Export Configuration File to save your entire VISUAL Message Center Configuration to an external file. Enter a file name and click OK. The file extension of the configuration file is .scc.

Import Configuration File To import an entire configuration of VISUAL Message Center select Import Configuration File and select the desired .scc or .vmc file. The SmartConsole will be shut down and restarted to update the changes.

Print allows you to print the messages in the message grid to a printer.

Exit Select Exit to end this session. You can also click the exit button from the toolbar, or close the application with the Windows Close button (the X at the top right of the Window). 3.3.2 Change Menu

Figure 20 – The Change menu

Fonts

Click Fonts to change the font size and appearance in the SmartConsole. The default font is Tahoma Regular 8, but you can change it to any other font.

Note Font changes affect the entire panel not just the Message Grid, as is the case with the Zoom In/ Zoom Out function from the toolbar. For details section 3.1.15 - Zoom In/ Zoom Out on page 19.

Alarms

Select this menu option to configure the Alarms. For details on how to use alarms Chapter 9 - Alarms on page 119.

Action Sets

Select this menu option to configure the action sets associated with alarms. For details on how to use action sets section 9.3.13 - Setting Action Sets on page 142.

Preprocess List

Use Preprocess list to configure actions to take before processing an alarm or filter. For details Chapter 8 - Preprocessing on page 115.

User Message Variables

User Defined – Per Message variables are message variables defined by the user and can be used in alarms, filters and other scripts in SmartConsole. The user message variables range from USERVAR1 to USERVAR99.

Please see section 12.1 - Creating and Defining Per Message Variables on page 194 for information on creating user message variables.

Global Variables Global variables are ALEV variables that the user can define. These variables can be used in any scripts in the SmartConsole.

Please see section 12.2 - Creating and Defining Global Variables on page 195 for information on creating global variables. 3.3.3 Connections Menu

Figure 21 – The Connections Menu

The options available from the Connections menu are also available from the toolbar. For details section 3.1.1 - Select Connections on page 15. 3.3.4 View Menu

Figure 22 – The View Menu

Toolbar By default the Toolbar is displayed in the SmartConsole. To hide the Toolbar click Toolbar. The check mark next to the Toolbar option will disappear and the Toolbar will be removed from the SmartConsole.

To show the toolbar select Toolbar. The check mark will appear next to the option Toolbar and the toolbar will appear in the SmartConsole.

It is also possible to hide or show the toolbar by pressing the function key F9 directly from the SmartConsole.

Business Shortcuts By default the Business Shortcuts pane is displayed in the SmartConsole. To hide the Business Shortcuts pane click Business Shortcuts. The check mark next to the Business Shortcuts option will disappear and the Business Shortcuts pane will be removed from the SmartConsole.

To show the Business Shortcuts pane select Business Shortcuts. The check mark will appear next to the option Business Shortcuts and the Business Shortcuts pane will appear in the SmartConsole.

For details regarding hiding and displaying the Business Shortcuts pane directly from the SmartConsole see section 4.4 - Business Shortcuts Pane on page 54.

Business Network By default the Business Network column is displayed in the SmartConsole. To hide the Business Network column click Business Network. The check mark next to the Business Network option will disappear and the Business Network column will be removed from the SmartConsole.

To show the Business Network column select Business Network. The check mark will appear next to the option Business Network and the Business Network column will appear in the SmartConsole.

For details regarding hiding and displaying the Business Shortcuts pane directly from the SmartConsole see section 4.3 - Business Network Column on page 44.

Zoom in/Zoom out Use the zoom function to enlarge or reduce the size of the font of the Message grid only. If you would like to enlarge or reduce all text in the SmartConsole use the function Fonts, available from the Change menu. For details section 3.3.2 - Change Menu on page 21.

Alarm Log To view the alarm log in a new window select the option Alarm Log. The alarm log is also available from the toolbar. For a description of the alarm log section 3.1.12 - Show Alarm Log on page 17. 3.3.5 List Menu

Figure 23 – The List Menu

Message Text Message text opens the details of a message in the Message Grid.

To open the message details: Step 1. First select a message in the Message Grid

Step 2. Then click List in the menu bar, and select Message Text from the menu that appears. The message details will open in a new window.

Message Text is also available from the message grid, simply right-click the desired message and select Message Text.

System Properties System Properties opens the system properties of a particular message in a new window.

To open the system properties: Step 1. First select a message in the Message Grid

Step 2. Then click List from the menu bar and select System Properties from the menu that appears. A new window will open with the System Properties.

System Properties are also available from the message grid: Simply right-click the desired message and select System Properties.

Capture with VISUAL Message Center iSeries Support Agent If you have iSeries Support Agent installed on your PC you will be able to capture jobs that produce errors by clicking this button. Otherwise the option is not available. For more information about iSeries Support Agent, please see the VISUAL Message Center iSeries Support Agent User Guide.

Debug with VISUAL Message Center Debugging Agent If you have this product installed on your PC, click this button to capture and debug jobs that produce errors. Otherwise the option is not available. For more information about Debugging Agent, please see the VISUAL Message Center Debugging Agent user guide.

Open Chat If you have iSeries Support Agent and / or Debugging Agent installed, you will be able to open a chat session with the user of the job that produced the error message. Otherwise the option is not available. For more information about this function consult the VISUAL Message Center iSeries Support Agent or Debugging Agent User Guide.

System Explorer If you have iSeries Support Agent or Debugging Agent installed, you will be able to explore system objects by clicking this button. Otherwise the option is not available. For more information about this function consult the VISUAL Message Center iSeries Support Agent or Debugging Agent User Guide.

Source Member Explorer If you have iSeries Support Agent or Debugging Agent installed, you will be able to explore source members by clicking this button. Otherwise the option is not available. For more information about this function consult the VISUAL Message Center iSeries Support Agent or Debugging Agent User Guide..

Columns You can adjust the information presented in the message grid by working with the columns. The columns display information such as System, Subsystem, Error type, Job name, User name, Job number, Time and Date, and Inquiry text.

For details on how to arrange columns section 4.5.16 - Columns on page 62.

Adjust List Adjust list resizes all of the columns in the message grid in one go, so that all columns fit in the current window size. If you resize the window you may want to repeat this operation. This function is also available from the Toolbar.

3.3.6 Window Menu

Figure 24 – The Window Menu

Refresh Select Refresh for a manual update of the message grid. You can also press the function key F5. By default refresh retrieves all messages received by the SmartConsole since it was started. Please see section 3.1.4 - Refresh on page 16. 3.3.7 Options Menu

Figure 25 – The Options Menu

Select Options from the menu bar at the top of the screen and click Options. A new window will appear with tabs for various SmartConsole options.

Figure 26 – Options window: Options for SmartConsole

Server Tab Here you can configure the time interval in seconds for a server time out.

In addition you can enable Smart Reconnect. Smart Reconnect tries to re-establish any dropped connection, and will continue to re-establish the connection until it is successful. Use the slide bar to set the time interval to use for trying to re-establish the connection.

Note You can reconnect manually using the NiceLink Configurator at any time, section 3.1.1 - Select Connections on page 15 for details.

The section Message Recollection is used to define the SmartConsole’s In-Memory database. The data is removed from memory every time the SmartConsole is shut down.

Data from previous sessions (historical data) or messages that occurred while the SmartConsole was shut down (only when operating in resilient mode - see Console Mode tab later in this section) can be retrieved the next time you start the SmartConsole.

Normally the database fills with new events. Historical data is always stored in the database as a result of a manual retrieve.

• Use Message List Refresh Time (Sec.) to indicate how often to refresh the message list. By default this is set to 30 seconds.

• Determine the maximum number of messages to store in memory. This number indicates the total number of new and historical events that can be stored in the database. This is useful to avoid databases growing too big. The default setting is 15.000 messages.

• Number of messages reserved for historical requests: When you manually retrieve historical records the database will store as many historical records as you specify in this field. This is important for viewing historical data and finding the root-events that triggered an alarm. By default this variable is set to 10.000 messages.

Warning When you retrieve historical data the 10.000 oldest new messages (or number of messages equivalent to the number you specify in this field) will be removed from the database to make way for the historical messages being retrieved.

BSM Tab The BSM tab is used to enable The Business Services Management (BSM) Engine.

Figure 27 – Options Menu - BSM Tab

As BSM uses the same DSN as the general configuration defining DSN database information is not required.

Finally the BSM tab shows BSM License information. It displays the number of Service Control Points available according to your license and how many Service Control Points are currently in use. You can also enter a new license key. Simply press the Enter Key… button and add the BSM license key in the field that appears.

Alarms Tab In general we recommend you execute alarms for all messages, regardless of when they arrive. However sometimes notification from an alarm is delayed, for example after a network black out. If you do not want to execute alarms for old messages, you can define here what messages you will process.

Figure 28 – Options menu - Alarms tab

When you open the alarms tab you will see that the Execute alarms for all messages check box is selected by default. However, when you deselect this option you can enter a threshold for the age of the message you will execute alarms for. For example Do not execute alarms for messages older than 2 hours.

Precycle/Postcycle Tab This tab allows an action set to be executed before or after every message retrieval cycle. You can enable either precycle or postcycle and select a predefined action set to run. Please note that action sets have to be defined in order to be selected in this tab. For further information on action sets see section 10.3.13 - Setting Action Sets on page 170.

Figure 29 – Options menu - Precycle/Postcycle tab

Monitors Tab You can check whether Batch, Interactive and Kernel Supervisor monitors are running. Here you can indicate what monitors you want to check, and what action, if any, you want to take if they are not running.

Figure 30 – Options menu - Monitors tab

Trace Tab In the Trace tab you can configure the Trace Details. First select a trace level from the drop down list. The available options are:

• Don’t Trace Anything

• Only Trace errors (default)

• Trace Everything

In the Advanced section you can select the file to use for storing trace information. Either enter the file name directly or click the button at the right to select an existing file.

Furthermore you can limit the trace file size. Enter the maximum trace size in MB desired.

Figure 31 – Options Menu - Trace tab

Language Tab Here you can change the language that SmartConsole is currently showing.

Figure 32 – Changing the current SmartConsole language

To set a new language, click the Languages tab and select a language. SmartConsole will reappear in the language you set. 3.3.8 Tools Menu

Figure 33 – Tools Menu

Calendars You may want to include or exclude events depending on when they were created in your infrastructure. With calendars, you have the power to do this. Please see Chapter 5 - Calendars on page 46 for more information.

SMTP Server List SMTP server list contains the SMTP Server configuration required for sending e-mail messages from the SmartConsole. For more information about sending messages via email see the SMTP Server List section on page 126.

Figure 34 – SMTP server configuration window

Address Book Here you can create lists of e-mail addresses to use in configuration of alarms and actions. Use e-mail lists to escalate events if they cannot be attended right away.

To create an address book: Step 1. Click Tools from the menu bar and select Address Book.

Step 2. In the window that appears click Options and select New.

Step 3. Enter the e-mail address you want to use. You can enter more than one e-mail address separating the e-mail addresses with a comma or a semi-colon. You can also add mobile phone numbers to the address list.

Step 4. Click OK. The new address book will appear as alias1 in the Address Book window.

Step 5. Change the name of the entry and click OK.

Now you can use the address books in your SmartConsole scripts.

LDAP Configuration LDAP uses your network directory to translate all the names in the mail fields into e-mail addresses. VISUAL Message Center uses the Windows configuration to access the directory, so in most cases all you need to do is activate LDAP by selecting the Translate names using LDAP in all mail fields check box.

There is a new ALEV function that uses the LDAP configuration to retrieve any user attribute for use in scripts. The ALEV function is defined as:

GET_LDAP_ATTRIBUTE(USER_NAME: STRING, ATTRIBUTE_NAME: STRING).

For example: GET_LDAP_ATTRIBUTE("John Smith", "mail").

For details on using ALEV in your filters, alarms and actions see the ALEV reference manual.

Click Tools from the menu bar, and select LDAP Configuration… to open the LDAP Configuration window. The following figure shows the LDAP Configuration window. In most cases you will not need to make any changes here as VISUAL Message Center uses your Windows configuration to access the directory.

Of course, if you want to use a different directory than the default directory, or if there is no default configured, you can enter the settings here. Once you have completed the LDAP configuration, you can test to make sure it is working correctly.

Figure 35 – LDAP configuration window

Configuring LDAP: Server: Enter the DNS name or IP address of the directory service server.

Port: Enter the port of the connection.

Server uses secure connection (SSL): Select this option if the server uses a secure connection.

UserName: Enter the User Name or, if you use Active Directory with domain, select DOMAIN\UserName.

Password: Enter the password for the domain.

Base Object: Enter the full name (for example CN=MY_ENTERPRISE) of the directory node where all the searches will start.

LDAP User Field Name: Enter the name of the User Name field you want to use. In most cases you can use cn (NetAdmin). If you are using Domino you should use uid.

Translate names using LDAP in all mail fields: Select this option to activate the LDAP configuration. It translates user names into e-mail addresses using LDAP. The translation will be done if the user name is found in the directory or left as is if the name is not found in the directory.

To test if the configuration is working correctly, enter a directory user name in the field User Name and click the Search button. If the configuration is correct the user’s e-mail address will appear in the Mail field. An error message will appear if the directory is not accessible or the name is not found.

Templates VISUAL Message Center comes with a pre-configured default and short template, which can be used in sending e-mail alarms, entries in the NT Event Log and for visual alarms (pop-up windows). Click Tools from the menu bar and select Templates to open the default template.

You can create your own templates to use in sending e-mail alarms, entries in the NT Event Log and for visual alarms. For details on how to configure templates see the Templates section on page 128.

Add/Delete DLL Actions Add and Delete DLL Actions allow you to add DLL actions to alarms and actions. Enter the identifier of the DLL and the DLL path. You can browse the system to find the DLL action path.

Retrieve Messages from Servers Retrieve Messages from Servers is similar to a manual refresh. This option will refresh the SmartConsole according to the selection in the pull down menu of the refresh button in the Toolbar. The default is “All Events Since Console Started”. However if you have selected “Last 2 Hours” for example, the SmartConsole will retrieve and display only the messages that arrived in the last two hours.

Configure Agent Subscriptions Click Tools from the menu bar and select Configure Agent Subscriptions… to open the Agents Subscription window. You will find a list of all the agents you have installed on your monitored systems, here you can select which agents you wish to receive messages from.

Figure 36 – Agents Subscription window

By default they are all active, but if you do not wish to receive messages from, for example the Interactive Agent, simply deselect the check box.

Whenever a new agent is added to your systems, it automatically appears here as activated.

By default all agents are in resilient mode. When an agent is resilient, all events for this agent are saved while the console is shut down or offline. You can change its status to non-resilient so you have control over what information is saved and when.

For example, if the JAM (Job Activity Monitor) agent has events that occur every two minutes and you do not need to see them when the console comes back online; you can make this agent non-resilient so it does not collect unwanted events.

To change the status of agents: Step 1. Right-click any agent and choose Set as Non-Resilient or Set as Resilient, depending on its current status. The agent’s icon changes to indicate whether it is resilient.

Step 2. Click Options from the menu bar, select Options and click the Console Mode tab. Select either the Non-resilient or Resilient check box.

Configure Criticalness Criticalness represents a severity level. There are four criticalness levels, as you can see in the following image:

Figure 37 – Configuring Criticalness

Each event has a severity level that is determined by the system. Here you configure what severity levels you consider Harmless, Minor, Warning or Critical.

For example, in the configuration above, if an event with severity 60 is received, the icon of all Business Views where this message is shown will turn yellow.

Note To reset the Business View to green, click the right mouse button in the view and then select Reset Criticalness.

Sign-Off Click Tools from the menu bar and select Sign-Off to log out of the AccessServer. This can also be done using the respective icon in the toolbar.

Manage Roles To configure roles of users in the AccessServer click Tools from the menu bar and select the Manage Roles ... item. This will bring up the SmartConsole Role Management window where users, groups and roles can be defined.

Figure 38 – Tools: Manage Roles window

Manage Security To further configure security settings in AccessServer click Tools from the menu bar and select Manage Security. Several options are available:

• General

• Connections

• Tools

• Message Retrieval

• Business Tree

• Enterprise View 3.4 Status Bar

At the bottom of the main window, you will find the Status bar.

Figure 39 – Status bar in play mode - click the pause button to pause the console.

The console opens in Play mode by default. In Play mode messages are automatically refreshed in the display grid. The interval is specified in Options from the main menu. In Pause mode messages are not automatically refreshed in the display grid. You must manually refresh clicking Refresh or pressing the F5 function key.

To pause the console, click the Pause button on the left. The button will change to a Play button. Click the Play button to resume the console.

When you begin to retrieve messages from a system, the console tells you how many messages are in the list and how many have been retrieved so far. Clicking the Stop button, you can stop retrieval midstream if there are too many messages in the queue and you only want to collect some of them. This may generate a NiceLink error, but this can be ignored and no events will be lost. VISUAL Message Center will always start collecting the oldest messages from the server. 3.5 System Tray Icons

If you are working with another application on your PC the following icon will appear in your system tray when SmartConsole receives a message

Figure 40 – System tray icon as displayed in system tray

Interactive Messages

Indicates that the message is an inquiry message.

Indicates that the message is a reply.

Indicates that the message is informational.

Queue Messages

Completion Message

Diagnostic Message

Escape Message

Informational Message

Inquiry Message

Notify Message

Reply Message

Request Message

Other Messages

Windows Messages

Audit Error Message

Audit Success Message

Error Message

Warning Message

Information Message

Console Messages

Error Message

Warning Message

Information Message

Chapter 4 4 Security

Security in VISUAL Message Center SmartConsole is handled by Tango/04’s AccessServer. In this chapter you will find introductory information on AccessServer and the available tools to configure AccessServer in SmartConsole. 4.1 AccessServer

The Tango/04 AccessServer software is a middleware product that provides security-related services to other Tango/04 applications:

• Authentication Services: seamlessly integrating Tango/04 applications with user provider systems already available in your company (only Windows-based user provider systems at the moment, but others can be supported if required). AccessServer allows you to configure an application’s security based on the current user profiles available in your systems, negating the need to manage new user systems just for our products.

• Authorization Services: allows you to define and fine-tune an applications security privileges based on application roles, system users and system groups.

• Auditing Services: provides the basis for common and flexible auditing requirements.

Figure 41 – AccessServer integration with Tango/04 applications.

AccessServer is used specifically with SmartConsole to:

• manage which users have access to SmartConsole,

• specify which users can edit Business Trees and Enterprise Views,

• specify whether they can simply view or edit its alarms, user and global variables, options, preprocesses,

• specify whether they can edit and export configuration settings,

• specify whether they can close the application,

• auditing user and change history,

• and more. 4.2 AccessServer Management

Management of AccessServer roles, users and groups is done through the Tools menu in SmartConsole. There are several options for configuring access as detailed below.

The name of the user currently logged in is always displayed in the upper right corner of SmartConsole’s window.

Note Only users with administration rights have access to the AccessServer Management options.

4.2.1 Log Out

Click Tools from the menu bar and select Log out to log out of the AccessServer. This can also be done using the respective icon in the toolbar. Once you log out of AccessServer the Windows User Authentication window will appear allowing you to login again. 4.2.2 Manage Roles

SmartConsole Role Management allows you to define AccessServer roles within the application. Roles define the different rights of a user in SmartConsole. By default there are three roles defined:

• Administrator: can create and edit roles and assign users and groups to each role

• Creator: can create and edit alarms, Business Views, Enterprise Views, etc.

• Viewer: can view Business Views and Enterprise Views, but can not edit them

Note Users must be created in Windows before roles can be assigned. Users can be created using the User Accounts Control Panel in Windows.

4.2.3 Manage Security

Several options are available when defining user and group access to SmartConsole. As custom roles can be created they can be configured in detail using the options below.

General General options of security management allow an administrator to assign general permissions to roles, users or groups. Here permissions to edit alarms, user and global variables, options and preprocesses can be set. Furthermore permissions for exporting and shutting down the application can be assigned.

Figure 42 – Manage Security: General options

To edit general permissions click Tools from the menu bar, select Manage Security and then General.

Connections Connections options of security management allow an administrator to assign permissions regarding connections. Here permissions for editing, removing or granting connections can be set.

Figure 43 – Manage Security: Connections options

To edit connections permissions click Tools from the menu bar, select Manage Security and then Connections.

Tools The tools options of security management allow an administrator to assign permissions regarding several tools. Here permissions for editing the Address Book, Agent subscriptions, calendars, DLL Actions, SMTP servers, severity of criticalness configuration and special days can be set.

Figure 44 – Manage Security: Tools options

To edit tool permissions click Tools from the menu bar, select Manage Security and then Tools.

Message Retrieval The message retrieval options of security management allow an administrator to assign permissions regarding messages. Here permissions for auto refresh, historical message retrieval and starting/ stopping message retrieval can be set.

To edit message retrieval permissions click Tools from the menu bar, select Manage Security and then Message Retrieval.

Figure 45 – Manage Security: Message Retrieval options

Business Tree The Business Tree options of security management allow an administrator to assign permissions regarding changes to Business Views. Here permissions for changing, copying, creating and deleting trees can be set. Furthermore editing permissions of color filters, criticalness options, filters, folder type and speed filters can be assigned. Finally, permissions for importing and exporting trees are set here.

Figure 46 – Manage Security: Business Tree options

To edit Business Tree permissions click Tools from the menu bar, select Manage Security and then Business Tree.

Enterprise Views The Enterprise Views options of security management allow an administrator to assign permissions regarding changes to Enterprise Views. Here permissions for viewing, modifying and deleting Enterprise Views can be set.

Figure 47 – Manage Security: Enterprise Views options

To edit Enterprise View permissions click Tools from the menu bar, select Manage Security and then Enterprise Views.

Enterprise View categories

You have security controls over the categories you use to organize your Enterprise Views. Here, you can grant users permission for a category containing relevant Enterprise Views, while you can prevent the same user from seeing other Enterprise Views because they are in a sensitive category.

Example

An Enterpise View category called ‘Branch1’ is used by two people:

• Technician, who sees EV1, etc.

• Manager, who can also see EV1, etc.

An Enterprise View category called ‘Branch Security’ is used by two people:

• Technician, who can only see EV1

• Security Officer, who can see EV1, EV2...

Although Manager has permission to view EV1, he only has permission in the ‘Branch1’ category and therefore cannot see EV1 (or any other Enterprise Views) in ‘Branch Security.’

A user must have permission for both an Enterprise View and its category (or categories) in order to view the Enterprise View. By default, every user has permission to see newly created Enterprise View categories.

Figure 48 – Manage Security: Enterprise View category options. Notice these are the default settings for all categories

To edit Enterprise View category permissions click the Enterprise Network tab at the left of your screen, right-click a category, and select Manage Security. For more information, please refer to section 7.3.3 - Giving Permission for a Category on page 119. 4.3 Auditing Using AccessServer

Auditing is an important part of AccessServer integration in SmartConsole. Administrators can view audit logs using the Windows Event Viewer found in Start > Control Panel > Administrative Tools > Event Viewer. With this tool administrators can view actions made by users in the SmartConsole. For example, if a Business View is accidentally deleted an administrator can see which user did so and at what time. This can be useful if unwelcome changes have to be tracked or user permissions need to be reviewed.

Figure 49 – The Event Viewer window displays audited events

Chapter 5 5 Calendars

Your SmartConsole Business Views can filter for events according to the calendars you create here. You can have them process or ignore events depending on when they were generated. You can also configure alarms to be enabled or disabled according to calendars as well as any given time of day, day of the week, or special days of the year. Calendars are configured online via the VISUAL Message Center SharedObjects calendars service

In SmartConsole, calendars can be used in:

• Business View filters (see section 8.8 - Filters in this Business View on page 127)

• Alarm filters (see section 10.2 - Setting an Alarm Filter on page 151).

Tip Calendars you create here can be used in VISUAL Message Center Reports and VISUAL Message Center Goals. See section 5.7 - Using Calendars in Reports and section 5.8 - Using Calendars in Goals, respectively.

To open the calendars service: Click Tools from the menu bar and select Calendars. The following Web page opens:

Figure 50 – Creating calendars in SmartConsole is done online via VISUAL Message Center SharedObjects. The list of calendars appears in the upper right of the browser its own toolbar

SharedObjects stores the calendars in the PMDB Engine and can provide access to them for Reports and Goals. This means that typical calendars, such as those with normal weekday working hours, summer timetables, or details of specific time shifts only need to be defined once and can then be reused many times by the other two Tango/04 applications.

Calendars help filter the days and even hours to include in Business View and alarm calculations. For example, a business hours calendar which includes business hours for normal working days and excludes the Christmas holiday will help if you want to exclude the non-working hours and holidays from the calculations used to determine the health of a Business View and the triggering of alarms.

Figure 51 – Business hours calendar with Christmas holiday details. The upper Range Set indicates that there are no business hours on the 25th of December and the 1st of January, as defined by the values */12/25, */01/01 entered in the Mask field. Normal weekday hours are defined in the lower Range Set

System calendars work with Range Sets and Exclusion Ranges to define the calendars. Before you can create a calendar, you must first define the range sets and exclusion ranges to be included in the calendar. 5.1 Range Sets

Range sets are presented by weekdays and on a 24 hour scale. Here, you can enter the weekdays and hours to include in your calendar.

To create a range set: Step 1. Click the New button at the top of the Range Sets list to create a new range set.

Step 2. Click the Edit button and enter a name for the new range set and click OK.

Step 3. Click Save.

Important If you click away from the new range set before saving (for example, to open a calendar or another range set), all your edits will be lost.

To add a range: Step 1. Click a box to select the starting point of the range.

Step 2. Next click the box that represents the last day and time in the range.

Step 3. Click Add to the calendar to accept the range.

Example of how to add a range

To create a calendar for working days from Monday 09:00 to Friday 17:00:

Step 1. Click once in the box that intersects Monday and 09; note that the box turns orange.

Step 2. Next click once in the box that intersects Friday and 16. Note that the whole area between the starting and ending box becomes orange to indicate the selected range.

Step 3. Click Add to the calendar to accept the range. The accepted range is shown in blue.

Figure 52 – Add hours to a calendar

To remove certain days and hours from the range: Select the range you want to remove as described in the steps above, but now click Remove from the calendar.

Example of how to remove a section from a range

To remove the hours 15:00-17:00 on Wednesday from the calendar we created above:

Step 1. Click the box that intersects Wednesday and 15.

Step 2. Next click the box that intersects Wednesday and 16. The range corresponding to 15:00 and 17:00 on Wednesday is highlighted in orange.

Step 3. Click Remove from the calendar and this time slot will be removed from the range.

Figure 53 – To remove the time slot 15:00 to 17:00, select the range 15 to 16 and click Remove from the calendar

You can also specify calendar ranges down to the minute.

To configure minutes: Step 1. Click Configure minutes. The Minutes bar opens.

Step 2. Click a box to select the starting point of the range.

Step 3. Next click the box that represents the last minute in the range.

Step 4. Click Add minutes to save the selection.

Step 5. Click Apply to apply the selected minutes to the calendar.

Example of how to configure minutes

The business day starts at 09:30.

Step 1. Select the desired date range as described in the examples above.

Step 2. Click Configure minutes to open the Minutes bar.

Step 3. Click minute 30 and then minute 59 to select the second half of the hour.

Step 4. Click Add minutes to save the selection.

Step 5. Click Apply. Notice that the calendar now shows only half the 9-10 block in blue.

Figure 54 – Configuring minutes for a time slot. In this example, from 09:30 to 09:59. Once the selection is applied, the time slot for Monday will appear as for Monday in the image with only half the 09 time marked in blue

Once you save the range set, it appears in the Range Sets list in the side bar for use in other calendars.

Figure 55 – Range Sets

Note Once a range set has been included in a calendar you will not have the option to delete it from the Range Sets list. Only unused range sets can be deleted using the delete button.

You can create more than one range set for each calendar. The original range set will serve as the base set. For example, your base range set could represent regular business hours. Additional range sets could function as alternative business hours, for example, summer business hours or business hours during holidays.

When you create a second range set you will notice that the new range set appears above the original range set. You will also notice the new Masks field is available at the top of the new range set. The mask is where you define what days the new range set applies to. You can enter individual dates (yyyy/mm/ dd) separated by commas, wild cards are also allowed, for example: */07/*

Exclusion ranges are those time periods that are disregarded by SmartConsole analysis. Use exclusion ranges for unexpected events like power outages and office closures. If you want to exclude the analysis of data already collected by SmartConsole, create an exclusion range to specify the date and time of the unexpected event.

To add an exclusion range: Step 1. Click Add on the Exclusion Ranges toolbar.

Step 2. Fill in the New Description field by clicking on the Edit button and naming the unexpected event.

Step 3. Enter the beginning and ending dates and times you want to exclude in the From and To fields, respectively, and click Save.

Figure 56 – Exclusion range for power outage on September 1, 2011 between 14:00 and 16:00

Note You can enter the date manually or select a date from the calendar.

To add a specific time you will need to enter the time manually in the To and From fields.

The new exclusion range appears in the Exclusion Ranges list in the side bar for use in calendars.

Figure 57 – Exclusion Ranges list

To add an exclusion range to a calendar, click the Add Exclusion Set button at the top of the calendar. 5.3 Creating Calendars

To create a calendar: Step 1. Click the New button on the toolbar above the calendars list. A calendar appears at the left of your browser.

Figure 58 – Creating a calendar in SmartConsole

Step 2. Click the edit button to the right of (the default) Calendar Name. A renaming field opens over the name. Enter a name for your calendar.

Step 3. Next you can choose to add existing range sets or exclusion ranges or create new ones here. You can add multiple range sets and exclusion ranges until you have the calendar to your liking.

Click Save to store the calendar. The calendar will appear in the calendars drop-down list box used in Business View and alarm configurations. 5.4 Example

Example of how to create a calendar.

Let’s say we want to create a calendar that includes all the business hours for the whole year for our company:

• Regular business hours are Monday to Saturday from 09:00 to 17:00, with an hour for lunch between 12:30 and 13:30.

• Summer hours apply from June to August and are from 08:00 to 15:00, Monday to Friday.

• Business is closed on Christmas day and New years day.

First we create our new calendar and call it Business Hours. We will add our range sets to this calendar. Remember to save the calendar before you start creating the range sets.

Next, we create a range set for the regular business hours called Weekdays. Open the Business Hours calendar and click Add Range Set and select the Weekdays range set to add this range set to the calendar.

Figure 59 – Initial range set: Business Hours

Then we create a range set for the summer hours called Summer Hours and add this range set to the calendar. In the Mask field for the Summer Hours range set, we enter */06/*,*/07/*,*/08/* to represent June, July, and August (note that each value is separated by a comma)

Mask

Second Range Set with Mask

Original Range Set

Figure 60 – Notice that the second range set for summer hours appears above the original business hours range set. Also notice the field Mask at the top right of the new range set

Finally, we create and add another range set called Holidays, which is essentially a blank range set with no hours selected to indicate the business is closed on these days. In the mask field we enter ? */ 12/25,*/01/01 to represent Christmas day and New Years day.

Third Range Set with holiday mask

Second Range Set with summer mask

Original Range Set, no mask

5.5 Importing Calendar Settings

The calendar settings used by SmartConsole coincide with those Calendar settings configured in the SharedObjects Calendar Service. You can import all VISUAL Message Center calendars.

To import a calendar from SharedObjects: Step 1. Click the Management tab, then select the Configure the Calendars subtab. Click the Import tab above the calendars list.

Step 2. Enter the Host name, User, Password and Owner of the machine in which SharedObjects is installed

Step 3. Click Calendar Lists and select the calendar which you want to import from the drop- down list box. The imported calendar appears in the calendars list. 5.6 Activity Calendars

You can assign an Activity Calendar to any component on the Service Model. A clock icon is shown on a component outside of Activity, but this will not affect the component’s criticalness propagation.

Activity Calendars are typically used to represent those times of day when you really want to monitor a component. For example, you would assign a normal business hours Calendar to a folder that represents a server that is turned on at 9:00 and is turned off at 5:00, because monitoring events outside of that Activity are not relevant.

Note Some components created from within Orchestrator (Business Folders and Views) might use this calendar to not propagate the criticalness upwards when the component is outside of Activity (depending on the template assigned).

Figure 61 – Components outside of an Activity Calendar show a “waiting” clock on their icon

To assign an Activity Calendar, Step 1. Right-click a Business Component and select Activity Calendar.

Figure 62 – About to assign an Activity Calendar to a folder

The following window appears:

Figure 63 – Selecting an Activity Calendar

Step 2. Select a Calendar from the drop-down list box. Click OK. 5.7 Using Calendars in Reports

In VISUAL Message Center Reports, you can define a calendar as a report template parameter. Plus, before you launch an instance of the report, you can change this specific parameter, using a more specific calendar for the report instance without changing the template at all.

Calendars that you create in SmartConsole will automatically appear in Reports.

Figure 64 – Accessing calendars in SmartConsole

Figure 65 – Creating the calendar ‘Security audit’ online (in SmartConsole) via SharedObjects

Figure 66 – Selecting the calendar in Reports as a parameter for a report template

Remember, if you want to launch a report using a different calendar than the one you have defined in the report’s template, click Run... to change the calendar right before you run the report.

Figure 67 – About to run the (SmartConsole) Component Brief Overview report using another calendar than what is defined for the report template

In VISUAL Message Center Goals, goal calculations can be based on calendars—even those you create in SmartConsole.

Figure 68 – Accessing calendars in SmartConsole

Figure 69 – Creating a ‘Test Calendar’ (in SmartConsole) online via SharedObjects

Specifically, calendars are used in creating (and editing) goal templates.

Figure 70 – The ‘Test Calendar’ appears in Goals, and we can select it when creating a goal template

In Goals, if a calendar is too broad of a timespan for your specific goal, you can further refine the goal by using excluded periods, which exclude periods of time from the calendar defined in the template used to create your goal. See the VISUAL Message Center Goals User Guide for more information on working with your specific goals.

Chapter 6 6 Business Network

The Business Network is the starting point for all views in the SmartConsole. The Business Network view is a model representing the complete structure of your company. With the business network you can create a model of your company starting from the smallest infrastructure element through to your business processes, applications, services, and more.

The Business Network Tree is a very simple yet powerful system for gaining insight into the status of your company.

The Business Network view is made up of 4 panes:

• The Business Shortcuts pane on the left - see section 6.6 - Business Shortcuts Pane on page 82

• The Business Network column located center-left - see section 6.5 - Business Network Pane on page 71

• The Message grid at the top-right - see section 6.7 - Message Grid on page 86

• The Analysis pane at the bottom right - see section 6.8 - Analysis Pane on page 97

The icons in the two left hand panes of the Business Network view help you to instantly check if important events have been received in a specific Business View, as the color of the icon and folder will change from green to blue, yellow, or red according to the criticalness of the message received.

Note Business Views can also be wine red in color. This means that they are in a “Monitoring Error” criticalness state. The “monitoring error” criticalness state falls between “critical” and “warning.” A Business View is assigned a “monitoring error” criticalness when a ThinkServer event lacking information is sent to it.

Select the Business View in either of these two panes to view its messages in the message grid and to see what impact the problem has on your business processes or the rot cause of a problem in the analysis pane. The messages help you locate the problem and drill down for event details to help solve the problem. The Analysis pane helps determine the importance of the error to the business and helps the managers allocate resources where it really matters.

Each pane will be described in detail in the following sections.

Figure 71 – Business Network view of VISUAL Message Center’s main message console 6.1 What is a Business View?

Business Views represent elements of your business and offer at-a-glance insight into the health of the element they represent. Business Views group messages that are relevant to a given business process such as security status, performance, availability and related business metrics. That Business View then indicates the status of that business process, and takes action accordingly. Key performance indicators (KPI) can also be included to better reflect the status of a business process.

Business views use filters to include only those messages that are relevant to the element, whether it is a logical element, physical element, originates from one or multiple systems. Each Business View has its own configuration, so you can organize all your messages per system, business area, or any other criteria.

For details on how to work with Business Views see section 6.5 - Business Network Pane on page 71. 6.1.1 Business View Substates

Business Views created in Orchestrator can have different substates, which are labels that you can give your Business Views to better classify them. If a Business View is not created in Orchestrator, its substate will always be Availability. Possible substates include:

• Availability

• Performance

• Scheduling

• Security

• Response Time

• Activity

• Errors

Note By default, all new Business Views that are created are given the substate of Availability. Also, when installing SmartConsole 8 Service Pack 4 (where substate criticalness first appears) all of your existing Business Views will be assigned the substate of Availability.

Note BSM data is only stored for the Availability substate.

When you click on a Business View, its business substate is given in the upper right of the browser panel.

Figure 72 – The selected Business View is of substate type Failures

6.1.2 Substate Criticalness Views

When you click on a Business Folder you see all the substates of all of the folder’s components. The substates are color-coded according to which criticalness they are in.

Figure 73 – All of the existing substates within a folder are shown when the folder is selected. In this example, we can tell that our “Security” folder has child components of four different substates

A given substate represents all of the underlying components of that substate.

If not created in Orchestrator, the component will not have any substates but Availability. 6.2 What is a Folder?

A folder represents a group of business network elements and may include Business Views and other folders. This super-component can represent anything form a single server to an entire business process or an application. Folders are represented in the Business Network Tree by the default folder icon. However you can change the icon to one that better reflects the folders purpose. After changing a folder icon you will still be able to distinguish folders form other Business Views as the icon shows a little folder in the bottom right corner of the icon.

Figure 74 – Left, a Business View icon; Right, a Folder icon

For details on how to work with folders see section 6.5 - Business Network Pane on page 71. 6.2.1 Types of Folder

There are three types of folder available in SmartConsole; the differences between them are explained in the table below:

Criticalness Impact BSM Business BSM Folder Type Management Analysis Reports Values License

F o l d e r Basic no no no no

Criticalness Impact BSM Business BSM Folder Type Management Analysis Reports Values License

Basic Service Control P o i n t Basic yes no no no

S e r v i c e C o n t r o l P o i n t Basic + Cause/ yes yes yes yes Effect

For quick and easy recognition, folder icons differ in the SmartConsole depending on their type:

Figure 75 – Left, folder icon; center, Basic Service Control Point icon, right, Service Control Point icon

Important You do not require any additional license to use Folders and Basic Service Control Points; however to define a Service Control Point you need an additional BSM license.

6.2.2 Basic Service Control Point

Basic Service Control Points allow you to draw extra real-time information. To improve clarity of the Real-Time Impact Analysis pane of the Business Network, only Service Control Points (including Basic Service Control Points) appear in the pane.

To create a Basic Service Control Point: Step 1. Create a folder.

Step 2. Right-click the folder, select Type of Folder, and click Basic Service Control Point. Notice that the folder icon changes to show a small grey triangle in the bottom-right corner.

You can change the Basic Service Control Point back to a folder at any time. Right-click the folder, select Type of Folder and click Folder.

Important Service Control Points offer advanced functionality over the Basic Service Control Points. Only Service Control Points can be used in conjunction with Business Values, Cause and Effect criticalness management and BSM Reports. For details regarding BSM licenses and advanced BSM features see Chapter 11 - Business Services Management (BSM) on page 181.

6.3 Folder Criticalness Management

A Business Folder has as many criticalnesses as its children components have business substates. Each substate criticalness depends on the children components of the folder and is calculated depending on the criticalness propagation configuration.

Folders have a global criticalness, which is calculated depending on the criticalness of its substates.

Figure 76 – A selected Business Folder’s criticalness setting is given at the upper right of the browser panel. In this example, the folder is assigned a Global Criticalness type (Priority on Availability substate) 6.3.1 Substate Criticalness Propagation Configuration

Each folder substate has its own criticalness which depends on the components of that substate that it has.

The Availability criticalness substate is calculated depending on the Availabiltiy Critiicalness Propagation Configuration. For the other substates the criticalness is always calculated by the most critical child component rule.

Availability Criticalness Propagation Configuration This type of criticalness only takes the Availability substate into account. Criticalness Propagation management is available from the folder menu. Right-click the folder, select Criticalness Management and click Criticalness Propagation Configuration. Here you will find five options for determining the criticalness of the folder:

• Most Critical Child Component: set criticalness of the folder according to the component with the most critical status.

• Least Critical Child Component: set criticalness of the folder according to the component with the least critical status.

• Simple Redundancy: set criticalness of the folder to the component with the least critical status. Only when all the components are “critical” is the criticalness of the folder set to “critical.” If 50% of the components are critical the folder is set to “warning.”

• Cause / Effect: uses the same method for setting criticalness as used by the Most Critical option, but allows you to define a child component (for example a synthetic transaction) as an effect. A component marked as effect will only appear as a cause of the resulting Business View state if there is no other child component causing the state to change.

• Custom Rules: allows for managing more complex situations.

Figure 77 – Criticalness propagation according to different Criticalness Evaluation options. In the example above, the Firewalls and switches in each of the offices in Barcelona have failed. However each folder shows a different state due to criticalness propagation rules: 01. Paseo de Gracia is red because it is set to Most Critical Child Component; 02. Diagonal is yellow because it is set to Simple Redundancy (more than 50% of the child components are critical); 03. Gran Via is blue because a custom rule is applied; 04. Meridiana is green because the Criticalness Propagation is set to Least Critical Child Component

Most critical, Least critical and Simple Redundancy The first three options are illustrated above in Figure :

• The 01. Paseo de Gracia folder is critical, as it sets the folder state according to the Most critical Business View.

• The 04. Meridiana folder is harmless, as it sets the folder state according to the Least critical Business View.

• The 02. Diagonal folder is warning, as it uses the Simple redundancy option and 50% of the Business Views are critical. If less than 50% of the Business Views are Critical the folder is set to harmless. It would be set to critical only if all the Business Views were critical.

A good comparison of Simple Redundancy criticalness management results can be seen in Figure 78.

Figure 78 – Simple Redundancy criticalness management. The folder setting depends on the percentage of critical Business Views.

Cause/Effect Cause and Effect criticalness management is only available with a BSM License. For more details see section 11.6 - Cause/Effect Criticalness Management on page 187.

Custom Rules

In the event that the previous options for Criticalness Propagation do not fully satisfy your needs, you can create a number of Custom Rules using pull-down menus.

The rules are evaluated in order of appearance in the list. The first rule that matches a component is used to set the criticalness of the folder. If no rule matches the criticalness of the components the folder is set to harmless.

Figure 79 – Custom Rules

What does Continue and Stop evaluating causes mean? The continue and stop evaluating causes tell SmartConsole whether to continue evaluating rules that have been set up or not, based on the criticalness of the component’s children. Component criticalness will always be set by the first rule of which conditions are met. Once a rule is evaluated and conditions satisfied a value decided by the rule is assigned to the folder’s criticalness (Set to column in Figure 80) and any components affected by the rule are added to the folder-criticalness causes list. As evaluation continues, if conditions of any further rules are met, only the folder-criticalness causes list is updated – the component criticalness will not be changed or reset from what was set by the first satisfied rule.

Figure 80 – A set of custom rules

If the Continue and Stop evaluating causes column is set to Stop, the evaluation is completed and no more causes are added to the list.

If the Continue and Stop evaluating causes column is set to Continue, consecutive rules are evaluated until either of these conditions occur:

• The currently evaluated rule has the Set to column set to a different criticalness than the first matched rule (the one that set the folder criticalness). In this case the current rule, and any subsequent rule(s), will not be evaluated.

• The currently evaluated rule has the Continue and Stop evaluating causes column set to Stop. In this case the current rule, and any subsequent rule(s), will be not evaluated.

In effect Continue and Stop allow you to group a set of rules for the same criticalness allowing for even more complex configurations of custom rules. Sometimes setting one custom rule does not cover all your business rules. In these cases you can create a group of rules as follows:

• Create two, or more, custom rules with the same Set to criticalness level.

• Define one part of the business rule in the first rule and select Continue. This tells the Business View to continue looking for causes in the next rule in the list with the same Set to criticalness level.

• In the subsequent rule(s) add the remaining logic of your business rule. Select Stop in the last rule for this Set to criticalness level (or group). The Business View will add the causes from rules 1 and 2 (or more), and not continue to evaluate any more rules.

Let’s look at an example to further explain the function of Continue and Stop using an example tree and rules.

Example

Imagine we have a simple tree as seen in Figure 81.

Figure 81 – Example tree

For the Parent folder we have set up custom rules to determine criticalness, as seen in Figure 82.

Figure 82 – example of Custom Rules used

It would seem logical that the parent folder’s criticalness would be set to harmless instead of minor due to rule number 5. However, this is not the case. To see why let’s evaluate each rule.

Figure 83 – Case 1

Example (continued) Rule 1

The first rule’s condition is not met so the rule is ignored. Even though the rule is set to stop evaluating causes this is not taken into account since the entire rule is ignored. The system therefore proceeds to evaluate rule number two.

Rule 2 Since the parent folder includes a child that has criticalness of warning the conditions of the second rule are met and the criticalness of the parent is set to minor. Furthermore, child B is added to the root causes of the parent. As the rule stipulates evaluation continues on to rule number three.

Rule 3 As rule number three has the same Set to value as the previous rule it gets evaluated. However, the parent does not include any child that has criticalness of harmless so no action is taken.

Rule 4 Rule number four still maintains the same Set to value as rule number three and is therefore evaluated. The rule’s conditions are met but notice how only child A is included. Since child A is a folder its criticalness is set by its children. The root causes of A therefore get added to the list of root causes of the Parent folder.

Rules 5 and 6 In rule five the Set to value is different from the previous rules and the process stops. Whether or not the rule’s conditions are met doesn’t matter. Further evaluation is not done so rule six is left unevaluated.

Now let’s change rule number two so that it is set to Stop rather than Continue as in Figure 84.

Figure 84 – Case 2

Rule number one is still ignored since the condition is not met. Rule two meets the set conditions but instead of continuing as above it is set to stop. No further rules are evaluated. The final criticalness of Parent will therefore be minor. While in the former case both B and the root causes of A are added to the root causes of Parent’s criticalness, in the second case only B is added as a root cause.

Modify Resulting Criticalness At the bottom of the Criticalness Evaluation Configuration window, you will find the option Modify Resulting Criticalness. This option allows you to increase or decrease the criticalness by up to two levels. In effect you are increasing or decreasing the importance of a Business View with regards to criticalness.

This feature can be useful for example when two different processes use the same underlying Business Views, where:

• in one case the “critical” Business View signals a serious problem in process 1.

• in the second case the same “critical” Business View signals a minor problem in process 2.

For process 1 you would leave the option set to the default none. For process 2 you would set the option to decrease 1 or 2 levels. With this configuration, the Service Control Point for process 1 would be adequately notified that there is a serious problem, without unnecessarily alarming the Service Control Point for process 2.

Note If resulting criticalness is “Monitoring Error,” it cannot be modified. (For example, an “Monitoring Error” criticalness decreased two levels is still “Monitoring Error.”)

Non-Availability Criticalness Propagation Configuration

For non-Availability folder substates, criticalness is always set using the Most Critical Child Component rule, which sets the criticalness of the substate’s folder according to the component with the most critical status. This section only applies if you have components created in Orchestrator.

Figure 85 – In this example the Performance substate is “minor” because the worst Performance Business View is “minor.” The Business substate is “critical” because the worst Business Business View is in “critical” 6.3.2 Global Criticalness Calculation Configuration

Global criticalness depends on the substate criticalness of the folder.

By default a folder that is not created in Orchestrator is set to the Only critical when availability is down rule and cannot be changed. Components created in Orchestrator can have these two options:

• Most Critical Substate: set criticalness of the folder based on the most critical component’s substate.

• Only critical when availability is down: criticalness will only turn “critical” when the Availability substate is critical. For non-Availability substates, if they turn “critical,” the most critical value of the folder will be “warning.”

Note The configuration of the global criticalness calculation is assigned depending on the template used in Orchestrator. They can’t be changed from SmartConsole. By default globabl criticalness calculation is set to the second option.

Most Critical Substate A Business Folder can have as many criticalnesses as its children components have business substates. With this type of criticalness, the Business Folder acquires the most severe criticalness out of all of its substate criticalnesses, no matter which business substates they are.

Figure 86 – The folder selected at left displays the criticalnesses of its children components, which include four substates. The folder is “critical” because one of its components (of substate Performance) is “critical”

Priority to Availability Substate With this type, a folder will only turn “critical” if its Availability substate is “critical.” If its Availability substate is not “critical” but another substate is, then the folder’s criticalness will be “warning.”

Figure 87 – In this example, folder criticalness is not “critical” because priority has been given to the Availability substate, which is not “critical”. The Business Folder has acquired a criticalness of “warning” because one of its components (the Failures substate component) is “critical,” and one level of criticalness down from “critical” is “warning”

The actual rule is: we take the most critical non-Availability component’s criticalness, and if its criticalness is “critical” (if it is “critical”) then we change it to “warning.” 6.4 Criticalness Alarms for Folders

You can execute an action (or action set) anytime the Business Views in any one of your Business Folders change criticalness. For example, you can send an e-mail when any of your Availability Business Views turn to “warning.” .

Note You can only create these types of alarms in Orchestrator.

Please see the Business Applications configuration guide for more information. 6.5 Business Network Pane

The Business Network pane shows you all the currently configured Business Views, and allows you to organize them into folders for easier navigation. You can then use these icons and folders in your Enterprise Views, but remember that a Business View must be configured in the Business Network before it will appear in your Enterprise Views.

Note Folders are for navigation purposes only, and do not affect the way that Business Views are saved. This makes newer versions of VISUAL Message Center backward-compatible with older versions, but as a result you cannot give the same name to two different Business Views, even if you have them organized in different folders.

To hide the Business Network pane click the Close button at the top right of the pane. To retrieve or unhide the Business Network pane drag the left margin of the message grid to the right until you can see the Business View pane again. You can resize all sections to suit your needs.

If you right-click anywhere in the Business Network pane a menu will appear where you can carry out several related functions, which are described here.

Figure 88 – Business Network menu 6.5.1 Rename

Click Rename to change the name of an existing Business View or Folder. 6.5.2 New

Use New to create a new Folder or Business View. Right-click the folder or Business View where you want to add a new item, then click New and select the item you would like to create. The new folder or Business View appears in Business Network column, ready to be renamed. You can change the name now or use Rename to change the name of the item at a later point in time. 6.5.3 Copy

To copy a Business View or Folder right-click the Business View or Folder you would like to copy. Then select Copy from the menu that appears. 6.5.4 Paste

There are three ways to paste a copied Business View or Folder:

• Paste

• Paste (Business Views as links)

• Paste as a link

Paste creates a new Business View or Folder with the same configuration of the original you copied. This function saves you work when you want to have two separate Business Views or Folders based on the same filters but where one is further refined than the other. For example start by copying and pasting one Business View. Then add additional configuration to further refine the second Business View.

Note You cannot have more than one Business View with the same name. Therefore, when you paste a copy, the new Business View is called copy of (original business view name). If you paste another copy of the same Business View it will be called copy of (original business view name) 2.

6.5.5 Paste (Business Views as links)

Paste (Business Views as links) is only available when you try to paste a folder containing Business Views. When you use this option the folder is duplicated but the contained Business Views are pasted as links only. These links appear in the new folder with the same name as the original Business Views they refer to.

This paste option is useful if you have a folder with many Business Views to link to while also adding additional Business Views that the original folder did not include. 6.5.6 Paste as Link

Paste as Link is only available when you paste a Business View, a Service Control Point or a folder as a link in a different folder from the original, you cannot Paste as Link in the same folder as the original.

When you Paste as Link you create a link to the original Business View or folder in a different folder. This link appears in the new folder with the same name as the original Business View. Links can not be renamed but if the original is renamed any attached links will inherit the new name.

When you paste a Business Folder or a Service Control Point as a link, only a link to the original folder or Service Control Point is created. The link acts as a representation of the original and completely mirrors the original. Editing the link is not possible, but instead double clicking it brings the focus back to the folder or Service Control Point.

Note Any changes you make to the original Business View will also apply to the link. Likewise any changes you make to the filters in the link will also apply to the original Business View. It is one and the same.

Paste as link is useful when one component affects an entire business area and you want all operators in this business area to see a particular Business View but do not want them to have access to other information the other operators can see. 6.5.7 Multiple Copy...

Multiple Copy will create a new copy of the selected Business View or Folder and allows the user to automatically change the items. For example, say you have an existing Server BCN and you have added two new servers NYC and SFC.

To add the new servers to your configuration: Step 1. Copy BCN using multiple copy

Step 2. Enter BCN in the Search Text

Step 3. Enter NYC and SFC in the Replace Text List

SmartConsole will create two copies of BCN: one called NYC and the other called SFC.

Tip You can add as many search and replace strings as you wish by filling up the available columns. If all columns are filled SmartConsole will automatically add more.

Figure 89 – Multiple Copy: Search and Replace window

Import / Export Multiple Copy It is possible to import and export your Multiple Copy configurations. Click the Export button to save the Multiple Copy configuration which can be used with other Business Views or Enterprise Views. 6.5.8 Delete

To remove a Business View or folder from the Business Network Column, right-click the item you would like to remove. From the menu that appears select Delete and confirm the action. 6.5.9 Add Shortcut

Add Shortcut allows you to add a shortcut to the Business Shortcut pane on the left. Right-click the Business View for which you would like to add a shortcut and select Add Shortcut from the menu that appears. 6.5.10 Type of Folder

Use the Type of Folder option to define Service Control Points. You can change folder types at any time. Options are:

• Basic Service Control Point

• Service Control Point

• Folder

Note Please see section 6.2.1 - Types of Folder on page 62 for explanations of the types of folders available.

6.5.11 Criticalness Management

Criticalness Management includes the following four menu options:

• Reset Criticalness

• Reset and refresh Criticalness Since

• Set Criticalness of all Descendants / Criticalness Configuration

• Criticalness Propagation Configuration

Note The Set Criticalness of all Descendants and Criticalness Configuration options, appear in the menu depending on whether you right-click on a folder or an individual Business View. Both options open the same window, however changing the Criticalness Configuration for a folder will affect all Business Views in that folder.

The first three options are described below. Criticalness Propagation Configuration is discussed in section 6.3 - Folder Criticalness Management on page 63.

Reset Criticalness Once an event has been resolved you may want to change the icon back to harmless to reflect the current state of the Business View. To do so right-click the icon you want to reset and select Criticalness Management and click Reset Criticalness. The criticalness will be changed to harmless until a new event arrives changing the criticalness to one of the other states.

Reset and Refresh Criticalness Since Reset and Refresh Criticalness Since allows you to customize the date from when to refresh.

Reset and Refresh Criticalness Since is only available after you select Inquiry/Reply from the Criticalness Configuration options described below. Once Inquiry/Reply has been selected, click Criticalness Management and select Refresh Criticalness Since to open the Select Reset and Refresh Date window. Select from what date forward you want to see all answer pending messages in the Business View.

Figure 90 – Select the date from when you want to refresh criticalness

To change back to the default click the triangle next to the Refresh button on the toolbar and select All Events Since Console Started.

Note The Reset and Refresh date also changes the function of the Refresh button from the toolbar. The default function of the Refresh button is to update all messages from the moment you start the SmartConsole. However, after you select a Reset and Refresh Date, the refresh button will refresh the messages from that date onward instead of from when the console started.

Set Criticalness of all Descendants / Criticalness Configuration

Criticalness Configuration options allow you to configure how the criticalness of a Business View is updated.

By default the criticalness of the Business View (color of the icon) changes according to the most critical message received in the Business View since starting VISUAL Message Center or the last time the Business View criticalness was reset.

Figure 91 – Criticalness Configuration options

Select the required update method. You can choose from:

• Default: use the most critical event received since the last criticalness reset

• Constant: Ignore criticalness of messages. The criticalness of the Business View will always be harmless (i.e. green)

• Last Event: Set the criticalness according to the last message received in the Business View

• Time Dependent: Make the criticalness of the Business View depend on the most critical message received during the time period you specify here

• Inquiry/Reply: Change the criticalness to harmless if there are no answer-pending messages for this Business View or to critical if there are any answer-pending messages. Select this option if you wish to manually set the Reset and Refresh Criticalness Since date.

• Programmatic: When this criticalness type is selected SmartConsole will ignore the criticalness of the message included in the selected Business View. Criticalness is set up through ALEV scripting using SET_CRITICALNESS. Please see Appendix B: ALEV Logical Expression eValuator on page 216 for further information on ALEV. 6.5.12 Edit Filters

Edit Filters opens the Display Filter Configuration window where you can create filters for your Business View. For configuration details see section 8.8 - Filters in this Business View on page 127. 6.5.13 Edit Colors

Edit Colors opens the Color Filter List where you can configure colors of the messages in the message grid. For details on how to configure message colors see section 3.1.13 - Filters in this Business View on page 17. 6.5.14 Set Icon

Set Icons allows you to choose an icon that best reflects the type of events you are monitoring with a Business View. The default icon is round with an arrow, but you can change this for example to round with an emergency vehicle for a security event.

Figure 92 – Set icon: example of the default icon (round with arrow) and a security icon (round with emergency vehicle)

Note The icon changes in both the Business Network Column and the Business Shortcuts pane.

To change an icon: Step 1. Right-click on the Business View or folder that you want to change

Step 2. Select Set Icon from the context menu that appears. The Select Icon window appears with all the available icons.

Step 3. Select the desired icon by double clicking the icon.

You can customize the view of the icons in the select icon window using the View menu. Here you can change the size of the icons displayed, or view the icons as a list. You can also arrange the icons by name or by ID.

Figure 93 – Set Icon 6.5.15 Collapse/Expand

Use Collapse and Expand to close and open a folder and its subfolders. 6.5.16 Business Value

Business Values can only be applied to Service Control Points and therefore require a BSM license. For more details regarding Business Values see section 11.5 - Business Values on page 184. 6.5.17 Import & Export

Menu option Import & Export contains the following menu options:

• Export to

• Import (overlapping) from

• Import (as sub-tree) from

• Print Structure

• Copy Structure to Clipboard

• Save Ordered Structure to RTF file

• Save Structure to RTF File

• Transfer Structure to Enterprise Views

Each option is discussed individually below.

Export to Use this option to copy the configuration of a Business View to an external file.

To copy the configuration of a Business View to an external file: Step 1. Right-click the Business View you want to export, select Import & Export and click Export To...

Step 2. In the new window that appears click the Arrow buttons to select or deselect the Business Views should be exported. Those appearing in the left hand pane will be included in the exported file. When you are happy with the selection click OK. The configuration is stored in a file with extension.bvl.

Figure 94 – Export to: Selection window for exporting a Business View. A similar window opens when you import a Business View.

Import (overlapping) from

To import a Business View configuration: Step 1. Select the desired option (overlapping or as sub-tree) from the menu

Step 2. Browse your system to find the appropriate.bvl file to import.

Step 3. In the new window that appears click the Right Arrow button to select the required Business View(s) and click OK.

When you use the option Import (overlapping) from the imported configuration overwrites the current folder from where you started the import.

Import (as sub-tree) from When you use this option the imported configuration is placed as a sub-tree in the folder where you started the import.

Figure 95 – Results of different import methods

The left hand image in Figure 95 shows the results of Import (as a sub-tree) from. A new folder – Bonanova – is created inside the original containing the imported Business Views. The right hand image shows the results of Import (overlapping) from. The Business Views are appended to the folder where the import was carried out.

If the name of the Business View you are importing already exists in your Business Network Tree the following screen appears, where you can indicate what to do:

Figure 96 – Indicate what action to take if a Business View with this name already exists.

Several importing conflict options are available if an attempt is to import a Business View whose name already exists:

• Rename imported Business View: the Business View is imported with a new name

• Rename existing Business View: the Business View is imported with the original name but the existing one is renamed

• Don’t import Business View: cancels the import of the Business View causing the conflict but goes ahead with any non-conflicting ones

• Delete existing Business View: removes the existing Business View from the tree

• Import it and set the existing Business View(s) as a link to it: the Business View is imported but the existing one is set as a link to the new one

• Import as a link to the existing Business View: the Business View is imported as a link to the existing one

• Overwrite the existing Business View with the imported one (maintaining the ID of the existing one): the existing Business View is deleted while the Business View is imported with the ID of the existing one

Figure 95 shows the results of selecting Rename imported Business View: the imported Business Views are renamed to:

• FW_Oficina_barcelona_bonanova - Ping 1

• Router_Oficina_barcelona_bonanova - Ping 2, and

• SW_Oficina_barcelona_bonanova - Ping 2.

Print Structure Print Structure allows you to print a list of all the Business Views, their location in the Business Network structure, and their configuration details to a printer.

Copy Structure to Clipboard Copy Structure to Clipboard copies the full Business Network Structure to the clipboard so that you can use it in other Service Control Points.

Save Ordered Structure to RTF File Save Ordered Structure to RTF File saves a list of all the Business Views in alphabetical and ascending order in a Rich Text Format file. In addition to the name and location of the Business View in the Business Network structure, the list contains the configuration details of each Business View.

Save Structure to RTF File Save Structure to RTF File saves a list of all the Business Views, their location in the Business Network structure, and their configuration details in a Rich Text Format file.

Transfer Structure to Enterprise View Transfer Structure to Enterprise View creates an Enterprise View for every folder of the Business Network structure. Each Enterprise View created here contains icons for all the Business Views included in the corresponding folder in the Business Network Structure. Now all you need to do to finish the Enterprise Views is select the background image and organize the icons. For details on working with Enterprise Views see Chapter 7 - Enterprise Network on page 102. 6.5.18 Refresh

Click Refresh for a manual update of the message grid. You can also press the function key F5. By default refresh retrieves all messages received by the SmartConsole since it was started. However you can easily apply a date filter for example for last few hours, last two days, last week, and many more. Furthermore you can create your own custom time lapse for a more specific refresh rate. For example, with custom time lapse the refresh rate can be set to 1 day, 2 hours, 37 minutes and 10 seconds. 6.5.19 Information

Click Information... for a window showing information on the selected Business View or folder. You can also use the hotkey combination CTRL+I. Previously the information was displayed as a tool tip when hovering over a Business View or folder. The new Information Window is capable of displaying more details with a cleaner interface. 6.6 Business Shortcuts Pane

When you first open VISUAL Message Center the Business Shortcuts pane will be empty. You can decide which icons appear in the Business Shortcuts pane by dragging and dropping them from the Business Network column. You can display as many Business View shortcuts as you wish.

To change the order in which the shortcuts appear in the Business Shortcuts pane simply drag a shortcut to the desired position in the list.

To hide the Business Shortcuts pane click the Close button at the top right of the pane. To retrieve or unhide the Business Shortcuts pane drag the left margin of the Business Network Column to the right until you can see the Business View pane again. You can resize all sections to suit your needs.

Figure 97 – Business Shortcuts Pane

If you right-click anywhere in the Business Shortcuts pane a menu will appear where you can carry out several related functions, which are described here. 6.6.1 Rename

Select Rename to change the name of an existing Business View Shortcut. 6.6.2 New

Choose New to add a Business View shortcut to the pane. The Shortcut Property window appears. Here you can enter a name for the shortcut and select what Business View the shortcut will link to. All Business Views are available for selection from the drop down list in the Business View field.

Figure 98 – The Shortcut Properties window appears when you select New from the menu 6.6.3 Copy

You can also Copy a Business View Shortcut from the right-click menu. Right-click the shortcut you would like to copy and select Copy from the menu that appears.

The new shortcut appears at the bottom of the list of shortcuts with the name copy of (name of original shortcut). You can change the name right away or use Rename to change the name at a later point in time.

Note If a shortcut with the name Copy of (name of original shortcut) already exists, the new shortcut will appear with the name Copy of Copy of (name of original shortcut).

Figure 99 – 1st and 2nd copies of the same shortcut (Delivery UK) in the Business Shortcuts pane 6.6.4 Delete

To delete a shortcut right-click the shortcut you want to remove from the Business Shortcuts pane. Select Delete from the menu that appears and click Yes to confirm the action. 6.6.5 Edit Filters

Edit Filters opens the Display Filter Configuration window. Note that changes you make here will affect the messages of the Business view as displayed in the message grid. For configuration details see section 8.8 - Filters in this Business View on page 127. 6.6.6 Edit Colors

Edit Colors opens the Color Filter List where you can configure colors of the messages in the message grid. Just as for Edit Filters, changes you make here will affect the messages of the Business View as displayed in the message grid. For details on how to configure message colors see section 3.1.14 - Colors in this Business View on page 17.

6.6.7 Sort Chronologically

If you have been using the Speed filters (or any other console filters) to sort messages in the message grid you may find that the messages no longer appear in chronological order within your selections. In order to arrange the messages in chronological order within your selections use Sort Chronologically. 6.6.8 Large/Small Icons

By default the icons in the Business Shortcuts pane appears as Large Icons. If you have many shortcuts you may want to change the size of the icons to small icons. To do this right-click anywhere in the Business Shortcuts pane and select Small Icons from the menu that appears. Small Icons is a toggle key, so the next time you open the menu you will find the option Large Icons instead.

Figure 100 – Large and Small Icons in Business Shortcuts 6.6.9 Export To

To copy the configuration of a Business View to an external file: Step 1. Right-click the Business View you want to export. Click Import & Export from the options menu that appears.

Step 2. Select Export To and save the file.

Step 3. In the new window that appears use the Right Arrow button to select the Business View and click OK. The configuration is stored in a file with extension.bvl. 6.6.10 Import From

To import a Business View configuration: Step 1. Right-click the Business View you want to import. Click Import & Export from the options menu that appears.

Figure 101 – Importing a Business View and its configurations

Step 2. Select Import From and browse your system to find the appropriate.bvl file.

Step 3. In the new window that appears use the Right Arrow button to select the Business View and click OK. The imported Business View will appear in the SmartConsole. 6.6.11 Reset Criticalness

Once an event has been resolved you may want to change the criticalness of the Business View back to harmless to reflect the current state. To do so right-click the icon you want to reset and select Reset Criticalness from the menu that appears. The criticalness will be changed to harmless until a new event arrives changing the criticalness to one of the other states. 6.6.12 Refresh

Click Refresh for a manual update of the message grid. You can also press the function key F5. By default refresh retrieves all messages received by the SmartConsole since it was started. However you can easily apply a date filter for example for last few hours, last two days, last week, a custom time lapse and many more. For details regarding the refresh function see the Reset and Refresh Criticalness Since section on page 75. 6.7 Message Grid

The message grid displays the messages received in a Business View. These messages can be further evaluated to give you more information about each message. Double-click the message in the grid to open the messages window, which gives you full message details. There are four tabs in the message window:

• Event

• Variables

• User Defined Variables

• Global Variables

In each window you will find the following buttons:

• Click Previous to move to an earlier message in the list

• Click Next to move to a later message in the list.

• Print allows you to print the full message details to a printer.

• Click Copy to copy the message details to the clipboard. 6.7.1 Event Tab

The Event tab displays details about the event that triggered the message and the full message description.

Figure 102 – Event tab in the Message window. 6.7.2 Variables Tab

The Variables tab shows all the variables that form part of this message and their values. You can use these messages in your filter and action configurations.

Figure 103 – Variables tab in the Message window.

6.7.3 User Defined Variables Tab

In the User Defined Variables tab you will find all the user defined variables that form part of the message and their values. You can use these variables in filter and actions configurations. For more information see the Custom Logical Condition section on page 134.

Figure 104 – User Defines Variables tab in Message window 6.7.4 Global Variables Tab

The Global Variables tab displays all of the Global values that form part of this message and their values. You can use these variables in filter and actions configurations. For more information see the Custom Logical Condition section on page 134.

Figure 105 – Global variables in the Message window

When you right-click anywhere in the message grid the context menu shown on the following page appears. Note that some functions require that you select one or more messages before opening the menu.

6.7.5 Hide Selected Messages

Sometimes it is useful to temporarily hide a number of messages to improve the operator’s view of the situation. Select the messages you would like to hide and right-click the selection. Click Hide Selected Messages and the messages will disappear from the message grid. 6.7.6 Unhide Messages

Right-click anywhere in the message grid and select Unhide Messages to display the messages you hid, as described in the previous section. 6.7.7 Select All

Use Select All to select all the messages in the message grid. This can be useful for example if you want to temporarily clear the message grid: select all messages and then hide the selection. You will only see new messages appear. You can retrieve the hidden messages at any time using unhide messages, as explained earlier. 6.7.8 Message Text

Right-click on a message and select Message Text, the message window will appear displaying the full message details. You can also open the message window by double-clicking a message. 6.7.9 System Properties

Right-click on a message and select System Properties to see details regarding the system, on which, the event occurred.

Figure 106 – System properties of the system where the event took place. 6.7.10 Capture with iSeries Support Agent

The option Capture with iSeries Support Agent is only available when you have selected an iSeries event. Furthermore you must have iSeries Support Agent installed. For further information see the VISUAL Message Center iSeries Support Agent User Guide. 6.7.11 Debug with VISUAL Message Center Debugging Agent

Likewise Debug with Debugging Agent is only available if you have selected an iSeries event. Furthermore you need to have Debugging Agent installed. For further information see the VISUAL Message Center Debugging Agent User Guide for more information.

6.7.12 Open Chat

Open Chat is a function of iSeries Support Agent and Debugging Agent. It is only available when you have selected an iSeries event. Furthermore you need VISUAL Message Center iSeries Support Agent or Debugging Agent installed to enable this function. 6.7.13 Execute Actions Set

This menu option allows you to manually execute any action set you have configured in SmartConsole. For details regarding the configuration of actions sets see section 10.3.13 - Setting Action Sets on page 170. 6.7.14 Adjust List

Adjust list resizes all of the columns in the message grid in one go, so that all columns fit in the current window size. If you resize the window you may want to repeat this operation. 6.7.15 Columns

You can adjust the information presented in the message grid by working with the columns. The columns display information such as System, Subsystem, Error type, Job name, User name, Job number, Time and Date, and Inquiry text.

Using Column Filters You can filter messages in the Message grid using Columns Filters located in the column headings. The messages can also be sorted in ascending or descending order by clicking the column heading itself.

Figure 107 – Column filters

To filter messages using a Column Filter:

Step 1. Click the Down Arrow next to the column header

Step 2. Choose a selection criterion to filter by.

Example of how to filter messages by system

Click the down arrow next to the column header called System and select the required system from the drop-down list that appears. Only the messages from the selected system will appear in the message grid. Click the arrow again and select (All) to undo the filter.

To further organize the messages in this view you could for example sort the messages by Message ID. Click the column header Message Id to sort the messages in ascending order according to message ID.

Adding and Removing Columns

To add a column to the message grid: Step 1. Click the right mouse button anywhere in the message grid and select Columns

Step 2. The Customization window will appear

Step 3. Drag a column heading from the Column window to the desired place in the message grid.

To remove a column from the message grid drag the column heading from the message grid to the Column window.

You can also change the order of the columns in the message grid by dragging the column heading to the desired position.

This customization will apply only to the current Business View, so you can see the fields relevant to the kind of events you are monitoring in that view.

Figure 108 – Available columns 6.7.16 User Columns

In addition to the default columns provided, you can create a column and associate it with any variable (such as an ALEV variable). This is particularly useful if there is a specific variable that is important to you within a message and you want to easily monitor its behavior from the console.

To create a User Column to associate with any variable: Step 1. Right-click anywhere in the message grid and select User Columns from the menu that appears. The Configure User Column List window appears.

Figure 109 – Configure User Column List

Step 2. Click Options / New. The Column Properties window appears.

Figure 110 – Column Properties window

Step 3. Click the Browse Variable button to display the Data Dictionary.

Figure 111 – Data Dictionary

Step 4. Select the category of variable you would like to browse and double-click the desired variable to select. Click OK and the new column is listed in the Configure User Column List window.

Step 5. Assign a descriptive name to the column, and click OK to return to the console. The new column is displayed as the last column in the message grid.

You can select user-defined columns from any other Business View for use in the current Business View. Each Business View has its own set of columns, so you can import as many columns as you wish.

If you want to use a user-defined column from another Business View, Right-click in the Configure User Column List window and click Select Columns… from the menu that appears. You can also click Options and then click Select Columns. The Select Columns window opens, displaying all of the available columns for use.

Figure 112 – Select Columns

Step 6. Select the column you want to use and click Select, and then click OK in the Configure User Column List window. 6.7.17 Show Groups

To group messages: Step 1. Right-click in the message grid and select Show Groups.

Step 2. A gray area will appear at the top of the message grid

Step 3. Drag-and-drop column headings to this area, all messages will be automatically grouped according to the selected column header.

Tip If a field that you would like to group the messages by is not available in the message grid add the column to the message grid (see above).

Figure 113 – Messages grouped by severity: Here messages for Severity less than 50 are collapsed and the others are expanded. Note that the column heading by which you grouped the messages is located in the gray area at the top of the message grid

You will also be able to define multiple grouping criteria.

Figure 114 – Message grid with multiple grouping criteria: in this example grouped first by severity and then by system date. Note both column headings are located in the gray area above the message grid and the line to indicate the relationship between the two columns

To ungroup messages, drag the column heading back to its original position in the message grid.

Note If you drag the column from the group area but not back to the message grid, you will delete this column from the Message grid, see also section 8.2 - Groups on page 125.

6.7.18 Show Grid

Select Show Grid to add light gray lines between the messages in the message grid, making it easier to read the messages.

Once you have selected Show grid, the option in the menu will change to Hide Grid.

Select Hide Grid to remove the thin gray lines from the message grid. 6.7.19 Hide Speed Filters

Select Hide Speed Filters to remove the speed filters from the top of the message grid.

Once you have selected Hide Speed Filters, the option in the menu will change to Show Speed Filters.

Select Show Speed Filters to display the speed filters at the top of the message grid.

Working with Speed Filters Speed Filters are located at the top of the message grid. They allow you to quickly filter messages according to

• Message Type

• System

• Subsystem/Domain

• Users

• Queues

Figure 115 – Speed filters as displayed above the Message Grid

To filter messages with a speed filter:

Step 1. Click the Down Arrow button next to the filter you want to use

Step 2. Select the desired filter option. The messages in the grid will show only the messages that match your selection criterion, in ascending order.

Step 3. To see all the messages select All.

Example of how to display only Answer Pending messages

Click the arrow next to message type (the first speed filter that by default displays All Messages) and select Answer Pending. Only the answer pending messages will appear in the message grid.

To see all messages again, click the Down Arrow button next to the message type and select (All messages). All messages will be displayed again. 6.7.20 Save to HTML

Use Save to HTML to save the list of messages in the message grid to an HTML-file.

Figure 116 – Example of resulting HTML file 6.7.21 Save to XML

Use Save to XML to save the list of messages in the message grid to an XML-file.

Figure 117 – Example of resulting XML file 6.7.22 Save to XLS

Use save to XLS to save the list of messages in the message grid to an excel spreadsheet (XLS-file).

Figure 118 – Example of resulting Excel file 6.7.23 Save Business View Style

Business View style is your configuration of how to display messages in the message grid for a particular Business View. It includes your settings for what columns to display, size of the columns, groups, message order, speed filters and user columns.

Click Save Business View Style to save your Business View configuration to an external file. For example it is useful as a backup copy of your settings, or for copying the settings to another machine.

6.7.24 Load Business View Style

Use Load Business View Style to apply a Business view style from an external file. This will import the settings of the message grid that you have stored in the file to your current Business View. 6.7.25 Sort Chronologically

Use Sort Chronologically if you have been using the filters to sort messages in the message grid and would like to rearrange the messages in chronological order. This will arrange the messages of this Business View in the order that they arrived in the SmartConsole. 6.7.26 Print

Select Print to print a list of the messages in the message grid of this Business View. This prints list according to the screen display configuration that you are using, so you will see the headings and order that you have selected. 6.8 Analysis Pane

The Analysis pane is located under the Message Grid at the bottom right of the Business Network view. The Analysis pane will change from the Problem Root Causes pane to the Real Time Impact Analysis pane depending on whether you select a Business View or a folder:

• Problem Root Causes pane: appears when you select a folder or Service Control Point

• Real-Time Impact Analysis pane: appears when you select a Business View

The user can resize the Analysis pane to show more items if necessary. Simply drag the divider between the message grid and the Analysis pane to the desired position.

You can also fix the contents of the Analysis pane temporarily by clicking the thumbtack symbol at the top right of the Analysis Pane. While the pane is fixed, the contents will not change to show root causes for other folders or Business Views you are browsing. This is useful for maintaining an overview of the root causes while exploring the different elements that caused the problem. Once you have completed your investigation release the Analysis pane by clicking the thumbtack symbol at the top right of the Analysis pane.

The user can sort the information in the Analysis pane in ascending or descending order. Simply click a column heading to order by that column. A small triangle appears in the column heading to indicate whether the column is sorted in ascending or descending order and mark according to which column the date has been sorted.

To organize the columns in a different order: Step 1. Click the column heading of the column you want to move

Step 2. Holding down the left mouse button, drag the column to the desired position.

Step 3. Release the mouse button and the column will be moved to the new position

Click and drag the left border of the column heading to resize the column width as desired. In addition you can resize each column to fit the width of the contents. Simply double-click the left border of the column heading and the column resizes to the width of the column contents.

6.8.1 Problem Root Causes Pane

The Problem Root Causes pane appears when you position on a folder or Service Control Point. The Problem Root Causes pane is intended to be used with Service Control Points but is also available for folders.

The Problem Root Causes pane shows all the Business Views based on which the Service Control Point or folder state was set. As seen in Figure 119, the pane’s header includes the Business Value of the Service Control Point.

Figure 119 – Problem Root Causes pane

Column headings The first column – Component Name – shows the name of the Business View and its current state.

Total Impact Cost is the combined Business Values for the Service Control Points that the Business View is impacting on. This functionality is only available for Service Control Points. For more information on Business Values see section 11.5 - Business Values on page 184.

The column Impact Type indicates the impact of the Business View on the Service Control Point. There are three impact types:

• Potential (low): The state of the Business View is normal (harmless) and it currently does not affect the operation of the Service Control Point.

• Potential (moderate): The current state of the Business View does not stop the Service Control Points from functioning; however the state of the Business View is not as it should be.

• Real: The Business View directly affects the state of the Service Control Point and may be causing problems to its normal operation. To determine when a Business View will affect a Service Control Point see section 6.3 - Folder Criticalness Management on page 63.

Last State Change indicates the date and time of the last state change of the Business View.

Problem Duration indicates the amount of time that has passed since the last state change of the Business View.

Impacting Since shows the date and time at which the Business View started to affect the Service Control Point.

Note Impacting Since only appears when the impact type is Real.

Impact Time is the amount of time that the Business View has had an affect on the Service Control Point (i.e. the time that the Business view has had Impact Type Real).

Full Path indicates the full file path of the problem root.

Show All (including potential problems) When a Service Control Point includes a large number of Business Views it may be hard to maintain a good overview of the current problem causes. Therefore, by default, only Business Views that have a real impact on the Service Control Point are displayed in the Problem Root Causes pane. To view the Business Views that have potential impact on the Service Control Point select the option Show All at the top right of the Problem Root Causes pane. To hide the potential problems again, simply deselect the show all option.

Figure 120 – The Show All and Show low potential problems check boxes are located in the top right corner of the Problem Root Causes Pane

Double-click the Business View to show the related messages in the Message pane and change the Problem Root Causes pane to the Real-Time Impact Analysis pane.

Show low potential problems When Show All (Including potential problems) is selected you can choose not to display low potential impacts. To omit those, select the Show low potential impacts option at the top right of the Real-Time Impact Analysis pane. This can be useful to focus on potentially high impact problems. Deselecting this options displays all Service Control Points affected by the Business View. 6.8.2 Real-Time Impact Analysis Pane

The Real-Time Impact Analysis pane shows the Service Control Points that are being affected by the current status of the Business View. As seen in Figure 121, the pane’s header will show the Total Impact Cost (sum of all the Business Values of affected Service Control Points) of the selected Business View.

Figure 121 – Real-Time Impact Analysis Pane. In the example above we can see that the router problems in the London - Picadilly Circus branch have been impacting on three Service Control Points.

Note If no Service Control Points (including Basic Service Control Points) are defined in the Business Network, then you will not see anything in the Real-Time Impact Analysis pane.

Column headings SCP Name shows the name of the affected Service Control Point and its current state.

Business Value is the value assigned to Service Control Points to indicate the level of impact the service or application has on the business. For more information on Business Values see section 11.5 - Business Values on page 184.

Note The Business Value column only appears in the Real-Time Impact Analysis Pane, replacing the Total Impact Cost column from the Problem Root Causes Pane.

Impact Type indicates whether the impact is real or potential. Three types of impact are possible:

• Real: The Business View directly affects the state of the Service Control Point and may be causing problems to its normal operation. See the section 6.3 - Folder Criticalness Management on page 63 to determine when a Business View will affect a Service Control Point.

• Potential (Moderate): The Business View does not affect the Service Control Point directly but may need some attention as it is not in a healthy state

• Potential (Low): The Business View is does not affect the Service Control Point directly and is in a healthy state.

Last State Change indicates the date and time of the last state change of the Service Control Point.

Problem Duration indicates the amount of time that has passed since the last state change of the Service Control Point.

Impacting Since shows the date and time at which the Impact Type changed to Real. Note that values for Impacting Since only appear when the impact type is Real.

Impact Time – The amount of time that the Service Control Point is affected (i.e. that the Service Control Point has Impact Type Real).

Full Path indicates the full file path of the problem root.

Show All (including potential problems) When a Business View impacts a large number of Service Control Points it may be hard to maintain a good overview of the current problems caused. Therefore, by default, only Service Control Points that are really affected by a Business View are displayed in the Real-Time Impact Analysis pane. To view the Service Control Points that are potentially affected by the Business View, select the Show All option at the top right of the Real-Time Impact Analysis pane. To hide the potential problems again, simply deselect the Show All option.

Double-click the Service Control Point to see all Business Views related to that Service Control Point and Change the Real-Time Impact Analysis pane to the Problem Root Causes pane.

Show low potential problems When Show All (Including potential problems) is selected you can choose not to display low potential impacts. To omit those, select the Show low potential impacts option at the top right of the Real-Time Impact Analysis pane. This can be useful to focus on potentially high impact problems. Deselecting this option displays all Service Control Points affected by the Business View.

Chapter 7 7 Enterprise Network

Once you have successfully completed the configuration of all your Business Views, you can create customized Enterprise Views to monitor your entire business from one unique global window.

Enterprise Views offer an alternative view of the Business Network Tree. You can create as many Enterprise Views as you need, making different consoles tailored to specific groups of users and using the information available in the Business Network Tree.

Different users need different views of the information stored in the SmartConsole. Management is typically interested in high level views of core business processes, whereas, an IT operator needs to see what underlying IT components are causing problems. For example the CEO simply wants to see that customer service and billing are functioning smoothly. The Security Officer wants to see that the databases with customer and billing information are secure. The IT operator needs to know the status of a specific database’s availability and performance.

Enterprise Views are very flexible and powerful tools which make sure that all users get exactly the information they need to manage their jobs successfully, no matter at what level they operate.

Enterprise Views are constructed using different elements from the Business Network. You can add Business Views, Business Folders and Service Control Points to your Enterprise Views. You can create custom backgrounds and place the selected elements exactly where you need to. You can even create links to other Enterprise Views or URLs offering quick access to important information.

The Enterprise Network tab in the SmartConsole consists of two panels:

• The Enterprise Views panel: contains the available Enterprise Views.

• The Filter panel: contains Enterprise View filtering tools. These tools are explained in more detail in section 7.2 - Filter Panel on page 117.

Figure 122 – Enterprise Views. In the first Enterprise View the icon for the 08.Branches folder is red (critical), indicating a problem. We can also see that while the UK and France folders are green (harmless), the overall folder for Spain is red, suggesting the branches problem is emanating from Spain. Clicking on the Spain folder opens an Enterprise View showing the whole of Spain, where we can see the problem is in Barcelona, a link to a new Enterprise View for Barcelona further narrows down the problem to a specific branch and finally we can see the cause of the problem is a router within this branch.

Figure 123 – SmartConsole - Enterprise Network tab

This is the main panel where all your Enterprise Views are displayed. The Enterprise Views that appear here will depend on the filters (if any), that have been applied using the filter tools in the Filter panel, for more information see section 7.2 - Filter Panel on page 117.

The Enterprise View panel can be customized by accessing the Enterprise View panel context menu. To open the context menu right-click anywhere in the Enterprise Views panel.

From the context menu select:

New or key Ctrl+N to create a new Enterprise View

Open to open the selected Enterprise Views

Rename or use F2 to rename the selected Enterprise Views

Delete or use Del to delete the selected Enterprise Views

Select All or use Ctrl+A to select all Enterprise Views

Categories to assign categories to the selected Enterprise Views (see section 7.3 - Categories on page 118)

View / Icons size to change how the Enterprise Views are displayed (see section 7.1.1 - Customizing How Enterprise Views are Displayed on page 104)

Multiple Copy to create a duplicate Enterprise View (see section 7.1.11 - Creating an Enterprise View Using Multiple Copy on page 110)

Import & Export to import or export Enterprise Views (see section 7.1.12 - Importing & Exporting Enterprise Views on page 115)

Tip Some options from the context menu will not be available if an Enterprise view is not selected. It is also possible to select more than one Enterprise View at a time by clicking and dragging the mouse cursor over the views, or by holding down the CTRL or SHIFT keys while clicking on the Enterprise Views. Some options in the context menu will apply to all the Enterprise Views that are selected.

7.1.1 Customizing How Enterprise Views are Displayed

By default Enterprise Views are displayed in a list; however you can change this view to display Enterprise Views as icons instead. From the context menu, select View and click as Icons. To change back to the list view, from the context menu select View and click as List.

You can further personalize the Enterprise Views panel by changing the size of the icons. From the context menu select Icon Size and click the desired size from the submenu that appears. Available sizes are Large, Medium, Small, and Very Small. 7.1.2 Opening an Enterprise View

To open an Enterprise View, double-click it’s icon in the Enterprise View panel, or right-click on it and select Open from the context menu.

7.1.3 Creating an Enterprise View

To create an Enterprise View, right-click anywhere in the Enterprise View panel and select New. You can also create a new Enterprise View by typing CTRL+N in the Enterprise View panel.

The new Enterprise View will appear in a window with the default world map. 7.1.4 Customizing an Enterprise View

You can customize the Enterprise View using the Properties and Options menus in the Enterprise View window.

To change the background image of the Enterprise View: Step 1. Click Properties from the menu bar

Step 2. Select Load Background from file… then browse your system to find the required image.

The SmartConsole comes with a series of maps; however you can use any .bmp file as a background.

Figure 124 – Enterprise View - Properties menu

To resize the window to the size of the background image click Properties and select Resize to Background Image Size. You can always manually resize the window by dragging the edge of the window to the desired size. 7.1.5 Customizing the Enterprise View Icons

There are two sizes of icons: large and small. To change the size of the Enterprise View icons displayed in the Enterprise View click Options from the menu bar and select Large Icons. Note that once you have selected Large Icons the option changes to Small Icons.

Figure 125 – Enterprise View - Options menu

You can choose whether or not to display the captions of the Enterprise View icons. The default setting is to display the captions. Click Options and select Hide Captions to remove the captions from the Enterprise View.

Note By default, an icon in an Enterprise View will be added with the same name as the corresponding Business View. This default name will be displayed as the caption if the icon name has not been changed.

For more details see section 7.1.7 - Renaming Enterprise View Icons on page 107.

Once you have selected Hide Captions, the option changes to Show Captions.

From the Enterprise View window you can change the Font and the Background color used in the labels.

Figure 126 – Customizing the icon label Font and Background

The default font is MS Sans Serif, size 8pt, and color black. Click the drop-down menus to select a different font, size, or color for the labels.

By default the labels have a clear background. To change the background color of the label, select Label Background. Then use the pull down menu to find the desired color for the background. 7.1.6 Adding and Removing Icons to an Enterprise View

To add icons for Business Views, folders or Service Control Points to an Enterprise View: Step 1. From menu bar click Properties and select Add icons

Step 2. In the window that appears select the elements from the list that you want to add to the Enterprise View. You can browse for the desired icons using the Business Tree tab, or use the Business List to select the icons from a list.

Step 3. Click the Right Arrow button to add each Business View or folder individually. Click the Double Right Arrow button to add all the Business Views and folders contained within a folder.

Figure 127 – Select elements to add to the Enterprise View from the Business Tree

Tip The Business List allows you to use filters to narrow your search, or to select only Business Views if desired. By default the Business List shows only the available Business Views. To display folders and Service Control Points select the Folders check box and click Search.

Figure 128 – Select elements using the Business List

Step 4. Once you have selected all the elements you want to add, click OK. The selected icons will appear at the top of the Enterprise View.

Step 5. Drag the icons to the desired positions in the Enterprise View. You can also right-click the icon and select the option Set position to indicate the exact position of an icon.

Tip You can also add a new icon to an Enterprise View by simply dragging it from the Business Network and dropping it on top of any open Enterprise View.

From the Enterprise View it is possible to remove icons one by one or all at once.

To remove a single icon from the Enterprise View: Step 1. Right-click the desired icon and select Remove Icon.

To remove all the icons from the Enterprise View: Step 1. Click Properties and select Remove All Icons

Once you have cleared the icons from the Enterprise View you can follow the steps above to add and position the icons again. 7.1.7 Renaming Enterprise View Icons

By default the name of an icon in the Enterprise View is the same as the Business View or Folder it represents; when icons are added to an Enterprise View, they are added with a name (caption).

The names of icons can be edited individually or as a whole by accessing the Enterprise View context menu. To change all icons, right-click in the Enterprise View to access the context menu and select:

• Set all icon names to default: to add the default name of the Business View to each icon. These will then be displayed as a caption

• Delete all icon names: to remove all names

Warning The option Set all icon names to default, will rename every icon in the Enterprise View, including any customized names. It is recommended that you rename each icon individually if you have manually renamed any icons in the Enterprise View.

Figure 129 – Enterprise View icons are added by default, with names (and therefore with captions). Right-click in the Enterprise View to open the context menu.

You can change the name of an individual icon, right-click the Enterprise View icon you want to change and select:

• Rename icon: to open a new window where you can rename the Enterprise View Icon.

• Set icon name to default to restore the default name of an Enterprise View icon

• Delete icon name: to remove the name from an Enterprise View icon 7.1.8 Creating Links to other Enterprise Views

You can use the Enterprise View icons to create links to other Enterprise Views.

To create a link from an icon to another Enterprise View: Step 1. Right-click the icon and select Create Link

Step 2. Select the desired Enterprise View to link the icon to.

When an Enterprise View icon is linked to another Enterprise View, the icon will changed to indicate that the link exists.

Double-clicking an icon with a link to an Enterprise View will open the linked Enterprise View.

Figure 130 – Right-click an icon and select Create Link to link to another Enterprise View available from the list 7.1.9 Creating Links to Web Sites

You can also use Enterprise View icons to link to a URL.

To create a link from an icon to a URL: Step 1. Right-click the icon and select Create URL

Step 2. Enter the desired Web address to link the icon to in the window that appears.

When an Enterprise View icon is linked to a URL, the icon will changed to indicate that the link exists.

Double-clicking an icon with a link to a URL will open the linked web page in your browser.

Tip Double-clicking an Enterprise View icon can result in different actions depending on the icon:

When an icon is not linked to another Enterprise view or URL, you can double-click the icon to access the Events window.

When an icon is linked to another Enterprise View, you can double-click the icon to open the Enterprise View.

When an icon is linked to a URL, you can double-click the icon to open the URL.

When an icon has a link to both an Enterprise View and a URL, double-clicking the icon will open the Enterprise View, not the Events window or the URL. In this case, right-click the icon and select View Events to access the Events window, or select open URL to open the linked web page.

Other functions available when you right-click a linked icon include, Open the link in a new window, Rename icon, Remove icon, Reset criticalness, and more.

Figure 131 – Right-click an Enterprise View icon to open the context menu. You can create, open and edit links from this menu to other Enterprise Views or web pages 7.1.10 Open, Rename and Delete Enterprise Views

Once you have created an Enterprise View click Enterprise View from the menu bar of the Enterprise View window to access further options.

From the Enterprise View menu select:

New or key Ctrl+N to create a new Enterprise View

Open to open an existing Enterprise View

Open in New Window to open an existing Enterprise View in a new window

Rename or use F2 to rename an existing Enterprise View

Delete or use Del to delete an Enterprise View

Delete All or key Ctrl+Del to delete all Enterprise Views

Close or key Ctrl+X to close the current Enterprise View 7.1.11 Creating an Enterprise View Using Multiple Copy

Multiple Copy is an extremely useful way of creating two or more Enterprise Views that display similar information. After creating the first Enterprise View you can use Multiple Copy to duplicate it and replace the Enterprise View icons in the new Enterprise View that differ from the first.

To create an Enterprise View using Multiple Copy: Step 1. Right-click on the Enterprise View you wish to duplicate and select Multiple Copy

Step 2. In the Search and Replace window, enter the text you wish to replace in the new Enterprise View in the Search Texts field.

Step 3. Enter the replacement text in the Replace Texts List field, and click OK.

Note You can select more than one Enterprise View at once to duplicate using Multiple Copy. Searching and replacing different text strings is easy using the automatically created columns in the Multiple Copy: Search and Replace dialog.

You can enter as many texts as you wish to be replaced. The texts are replaced column by column.

Multiple Copy looks for instances of the specified text (to be replaced in the Enterprise View) in the following places:

• Name of the Enterprise View

• All the links (to other Enterprise Views, or URLs)

• All the icons − If the icon represents a Business View, then it will search for a Business View that matches the new name with the replaced text. − If the icon represents a folder (a Service Control Point or Basic Service Control Point), then it will search for a folder that matches the new full path with the replaced text. − Note that if the Business View / folder is not found then the icon will not be created.

The new Enterprise View appears in the Enterprise View panel where you can rename it and arrange the icons as required.

Example of using Multiple Copy to create Enterprise Views

Creating Enterprise Views for a large number of branches within a multinational organization could be an extremely time consuming exercise if we had to create each Enterprise View individually. Multiple Copy will allow us to create unique Enterprise Views based on just one single Enterprise View by simply changing the name of each branch.

In our example we have several branches all monitoring network activity and we want to create an Enterprise View for each branch. In the Business Network we have several folders representing branches which each contain the same type of Business Views to monitor network activity in each of the branches:

• a router (01. Router_name of office)

• a firewall (02. Firewall_name of office)

• a switch (03. Switch_name of office)

Figure 132 – Each folder contains three Business Views following the same naming convention

Make sure that the Business Views you create in the Business Network follow a controlled naming convention, so that each Business View for each process differs only in the name of the branch it is monitoring. It is important when creating Business Views that naming conventions are considered in order to simplify the process of reproducing Business Views and Network Views utilizing Multiple Copy.

Next, we create the first Enterprise View for the first branch, in this case Paseo de Gracia and add the Enterprise View icons.

Figure 133 – Create the first Enterprise View and add the Enterprise View icons

The Enterprise View is renamed to include the name of the branch as it appears in the name of the Business Views (Comms - Barcelona - Paseo de Gracia) to ensure that each new instance of the Enterprise View will be renamed accordingly. In the Enterprise Network pane right-click on the new Enterprise View for Paseo de Gracia and select Multiple Copy.

Figure 134 – Right-click the Enterprise View and select Multiple Copy to open the Search and Replace window

In the Search and Replace window the name of the branch as it appears in the Business View is entered in the first Search Texts column (Paseo de Gracia).

The names of each of the branches which we wish to create duplicate Enterprise Views for are then entered in the first Replace Texts List columns (Diagonal, Gran Via, Meridiana).

Figure 135 – Enter the text to be replaced in the duplicated Enterprise Views

Multiple Copy creates an Enterprise View for each branch, changing the names of the Enterprise Views and replacing the Business Views contained within to those that are relevant to each branch.

Figure 136 – The new Enterprise Views in the Enterprise Views window

Figure 137 – Three new Enterprise Views have been created for the branches in: Diagonal; Gran Via; and Meridiana. The Enterprise View icons for monitoring the firewall, router and switches in Paseo de Gracia have been replaced by Enterprise View icons for monitoring the firewall, router and switches in Diagonal, Gran Via and Meridiana.

Once you have created your Enterprise Views you can export them to file as a backup or for others to import to their Enterprise Network.

Exporting Enterprise Views

To Export an Enterprise View: Step 1. Right-click anywhere in the Enterprise Views panel to open the context menu, select Import & Export and click Export to …

Step 2. Enter a name for the exported file, select a destination and click Save to open the Export Enterprise Views window.

Figure 138 – Export Enterprise Views Options window. In the example above, Communications has been selected from the list of categories and all Enterprise Views in the Communications category appear in the column below.

Step 3. Select the Enterprise Views to export. You can use the filter tools to easily find just the Enterprise Views you need:

• Filter Search: Enter a search term in the field and click the Search button. • Categories filter: Select the categories from the drop-down list you wish to filter by. You can filter by more than one category at a time. Step 4. Use the arrow buttons to add or remove Enterprise Views to be exported. Click OK when you have made your selection.

Note The background images (.bmp files) are also exported.

Importing Enterprise Views

To import Enterprise Views: Step 1. Right-click anywhere in the Enterprise Views panel to open the context menu

Step 2. Select Import & Export and click either: Import from..., or Multiple Import from... Each of these options is explained below.

Import from... Use this option to import Enterprise Views into the SmartConsole when you simply want to add or replace views.

Navigate to the file you wish to import and click Open to open the Import Enterprise Views window. This window is the same as the Export Enterprise Views window and is used in the same way to select the views to import, see Figure 138 above. After making your selection click OK to import the views.

If you are importing Enterprise Views with the same name as existing views, the Importing Conflict window will appear where you can select the appropriate action to perform.

Figure 139 – Importing Conflict options

Multiple Import from... Use this option to import Enterprise Views into the SmartConsole when you want to add duplicate views using the Multiple Copy tool.

The process is the same as the Import from... process above, however after importing you have the option to replace text use the Multiple Copy tool. For more details on using Multiple Copy see section 7.1.11 - Creating an Enterprise View Using Multiple Copy on page 110. 7.1.13 Using Enterprise Views

The icons in the Enterprise Views work exactly as the icons in the corresponding Business Views; they will automatically change color according to the criticalness of the received messages. This allows you to monitor your entire IT system with one unique and easy-to-use window, while keeping total control over individual events.

You can investigate the events of a Business View at any time by simply double-clicking the icon to open the SmartConsole Events window.

Note If the icon has a link you must right-click the icon and select Event View to open the Events window.

You can also quickly view useful link information by resting the mouse on an icon.

Figure 140 – Business View information displayed in an Enterprise View. Rest on an icon and a context menu appears displaying link information.

Once you have completed your investigation right-click the icon and select Reset Criticalness to reset the color of the icon.

When there is a lot of traffic it can be helpful to filter the icons to improve the overview of the situation. You can filter the icons according to criticalness at the bottom of the Enterprise View window, simply select or deselect the criticalness levels that an icon must have to be displayed in the Enterprise View.

Figure 141 – Criticalness filter

You can hide an individual icon at any time by right-clicking the icon and selecting Remove Icon. It is also easy to add new Business View or Business Folder icons if required: simply right-click in the Enterprise View window, and select the icon from the appropriate Add Icon option.

Finally, use the previous and next buttons located under the main toolbar in the Enterprise View window to scroll through your most recently viewed Enterprise Views. 7.2 Filter Panel

Enterprise Views are a very powerful way to monitor every aspect of the business of a company due to their fully customizable nature. It is therefore very probable that you will create many Enterprise Views to ensure that the entire business is monitored as efficiently as possible. There is no limit to the number of Enterprise Views you can create, however the more you create the harder it becomes to manage them all. The Filter panel makes it easy to display only the Enterprise Views you need to see at any time, at the click of a button.

The Filter panel contains two distinct methods for filtering the Enterprise Views that are displayed in the Enterprise View panel:

• Filter Search button. Filter Enterprise Views using a simple search term.

• Categories. List of categories assigned to Enterprise Views to enable quick filtering and logical grouping of the views. 7.2.1 Filter Search Button

To filter Enterprise Views using the Filter Search button, simply enter a term in the Search field to filter by and click the Filter Search button. This filter searches in the title of the Enterprise View returning all Enterprise Views that contain the search term in the title.

Figure 142 – Filter Search button

Tip Giving your Enterprise Views meaningful names, will enable much more powerful filtering when using the Filter Search button.

The Filter Search button can be used in combination with Category filtering. Entering a search term and selecting a category will return only the Enterprise Views that match both criteria (see the Categories section below for more information).

7.3 Categories

Categories are used in the Enterprise Network to manage Enterprise Views. They make it easier to view only the Enterprise Views you need to see, but also provide a potent tool for grouping Enterprise Views together for ease of use. And, becuase they have permissions, you can create confidential categories in the sense that some users won’t be able to see the Enterprise Views in said categories. 7.3.1 Creating Categories

To add a category to the categories list: Step 1. Right-click anywhere in the Categories panel and select New Category.

Step 2. Enter a name for the category in the Create a new category window that appears and click OK.

The new category is added to the list and can be assigned to any Enterprise View. 7.3.2 Assigning a Category to an Enterprise View

To assign a category to an Enterprise View: • Drag and drop the Enterprise View onto a category in the Categories panel, or

• Right-click on the Enterprise View and select Categories from the context menu and click the desired categories from the list, or

• Open the Enterprise View and click Properties form the menu bar and select Categories to open the Enterprise View Categories window. Select the check boxes for the categories you wish to assign to the Enterprise View.

Figure 143 – Enterprise View Categories window. Select the check boxes to assign categories to an Enterprise View.

Note You can assign as many categories as needed to an Enterprise View.

7.3.3 Giving Permission for a Category

Once you give a new user General Enterprise View permission, you still have to give him permission for a category for him to be able to see any Enterprise Views.

Note By default, every user with General Enterprise View permission has permission to see newly created Enterprise View categories. In other words, make sure to deny permission to users if you create a sensitive category.

To control user access to an Enterprise View category: Step 1. Right-click on a category and select Manage Security, then click

• Default: for your settings to apply to all categories, or • Selected: for your settings to apply only to the selected Enterprise View

Figure 144 – Enterprise View category security; Note that you can control the default security for all categories or just the security for the selected category

Step 2. The Enterprise View category security window appears. Here you can see that all SmartConsole users have full permission by default:

Figure 145 – You can deny permission to users that don’t need to see any of the Enterprise Views in a whole specific category

To deny permission to a user or group, select the user, group or role in the Object field and click the Deny check box(es) in the Permission field. Click OK.

7.3.4 Using Categories

Categories are used to filter the Enterprise Views that are seen at any time in the Enterprise Network. Filtering using categories ensures that you can easily locate and view only the Enterprise Views that you need.

Figure 146 – Using Categories. In the example above, we are filtering on the Communications and UK categories; therefore only the Enterprise Views that have been assigned to both categories are visible in the Enterprise Views panel.

To filter Enterprise Views by Category: In the Category panel, click the Category check box for the category you wish to filter the Enterprise Views by. When you select a Category check box, then only the Enterprise Views that have been assigned to that category will appear in the Enterprise Views panel. Selecting another category will result in further filtering of the Enterprise Views, so that you only see the Enterprise Views that belong to all the categories selected.

Example of using categories

Imagine you want to monitor all iSeries systems in branches based in Spain, of a multinational company with branches throughout Europe. You will have many Enterprise Views for monitoring the IT infrastructure of every branch in each country.

Create a category called iSeries and assign all the Enterprise Views to this category that contain information relating to the iSeries systems installed. Next, create another category called Branches and add all the Enterprise Views that are relevant to branches. Finally create a third category for Spain and add all the Enterprise Views relating to Spain.

Selecting the iSeries check box in the Categories panel will display all the Enterprise Views that have been assigned to that category. Now, if you also select the Branches and Spain check boxes, you will only see Enterprise Views that meet all three criteria i.e. an Enterprise View containing information regarding iSeries systems in branches only based in Spain.

Use the Check Box buttons at the foot of the Category panel to quickly activate all the category filters; or deactivate all the category filters.

7.3.5 Viewing which Categories are Assigned to Enterprise Views

It can be useful to be able to see which filters have been applied to a customized Enterprise View panel, or indeed which categories an Enterprise View belongs to before applying filters. This information is particularly useful when you want to export a selection of Enterprise Views. The various methods for accessing this information are described below.

Category Information bar At the foot of the Enterprise Views panel an information bar displays which categories are selected, for example, Categories: (Commercial) AND (Spain). If no categories are selected then the information bar will display Categories: <*ALL>, indicating that all the categories are being displayed.

Category context information You can rest on an Enterprise View to see which categories it has been assigned to. Similarly if you rest on a Category you can see which Enterprise Views have been assigned to that category.

Figure 147 – Category context information. Rest on an Enterprise View (left hand image) or a category (right hand image) to see category assignments. In the example above we can see that there are five Enterprise Views assigned to the Branches category. The Branches - Spain Enterprise View is one of these.

Right-Click on an Enterprise View or Selection of Enterprise Views Right-click on an Enterprise view and select Categories from the context menu to view the categories assigned to the view (indicated by a tick in the list).

When several Enterprise Views are selected in the Enterprise Views panel, right-clicking on the selection and selecting Categories will indicate the categories that apply to each of the selected views.

Figure 148 – Category information for several selected Enterprise Views. In this example we can see that the selected views belong to both the Branches and Countries categories. 7.3.6 Managing Categories

Further options for managing categories can be accessed by right-clicking on a Category in the Category panel to open the Category context menu.

From the context menu select:

New Category … to create a new category

Rename to rename the selected category

Delete to delete the selected category

Remove from all Enterprise Views to remove the assignment of the selected category from all Enterprise Views

7.4 Message Storage

When the VISUAL Message Center console connects to the iSeries, it will retrieve only the specific subset of messages corresponding to the configuration in the Business View filters. This allows for a quick and efficient way to retrieve messages because only the important messages will be retrieved and viewed, thus limiting network traffic and ensuring an easier view of all activity occurring on that system. All messages shown in SmartConsole are stored in the iSeries database in a unique repository for easy retrieval.

Chapter 8 8 Working with Console Filters

VISUAL Message Center SmartConsole aims to alert you to vital error messages immediately, so you can react. But you need to be able to select those messages - there may be some error messages that do not interest you, and there may be some critical error messages (maybe waiting for a reply) that you need to see immediately. SmartConsole comes with a complete filter system to help you get just the very important messages.

SmartConsole uses filters for different product functions: one to select messages to include in your Current grid, another for the History grid, another for customizing the color coding of messages, and filters that act as selection criteria for alarms. For more information about alarms see Chapter 10 - Alarms on page 150.

You can easily filter out all of the messages that don’t interest you or select important messages using the following parameters:

• System

• Subsystem

• Message ID

• Message type

• Severity

• Job name

• User name

• Date/Time

• Message queue

• Message text

• Any other customer parameter, as defined in Advanced Filters

You can use generic names in filters, and you can use both include and exclude functions.

SmartConsole also utilizes Hyperhashing technology to provide high speed event processing, reducing processing time by up to 99%. For more information on Hyperhashing, see section 8.8.1 - Hyperhashing on page 128.

Quickly filter out unwanted messages using the speed filters above the message grid. There are speed filters for Message Type, System, Subsystem, User and Queue. see section 6.7 - Message Grid on page 86.

Figure 149 – Speed filters 8.2 Groups

Use Groups to group messages in the message grid according to the values of a particular field. For example group the messages according to their severity. When you group messages by severity the groups appear as a collapsed tree in the message grid. You can expand the tree to display the messages for each group.

You can also create subgroups, further organizing the messages in the message grid.

The Groups area appears at the top of the message grid, between the Speed Filters and the Column Filters.

Figure 150 – Message Grid with multiple grouping criteria: in this example grouped first by Severity and then by Server Date. Note both fields by which the messages are grouped are located in the dark gray area above the message grid and the line to indicate the relationship between them.

For details on how to configure groups see section 6.7.17 - Show Groups on page 93. 8.3 Column Filters

Apart from the speed filters each column header has its own filter function, so that you can filter messages according to any field you have selected in your view. For details see section 6.7.15 - Columns on page 90.

Figure 151 – Column filters

To quickly filter the messages by date you can use the drop-down filter, which is accessed by clicking the arrow to the right of the Refresh button in the Toolbar. You can use it to filter messages from the last 24 hours, 48 hours, and more. For details see the Reset and Refresh Criticalness Since section on page 75. 8.5 Quickly Executing Action Sets

From the Message Grid, you can quickly execute an action set on any message by right-clicking the message and selecting Execute Action Set. You must have configured your action sets before executing them; for more information see section 10.3.13 - Setting Action Sets on page 170. 8.6 Agent Subscriptions

Another way to filter is to use Agent Subscriptions. By subscribing or unsubscribing to an agent you choose whether you will receive messages from that agent or not, reducing the number of messages received in the SmartConsole.

By default all agents are subscribed and any new agent that is added to your system is automatically activated. However it is easy to unsubscribe an Agent and deactivating an unwanted message collection may significantly improve communications performance.

You can further customize the agents to control what information is stored when by changing an agent’s resilient mode. When an agent is resilient, all events for this agent are saved while the console is shut down or offline. You can change its status to non-resilient so you have control over what information is saved and when.

For details regarding the configuration of Agent Subscriptions see the Configure Agent Subscriptions section on page 33. 8.7 Color Coding Messages

In addition to organizing and excluding messages from the message grid as described in earlier sections, you can also apply colors to specific messages to help make them more visible in the message grid.

Start by configuring a filter that will act as the selection criteria for your color-coding. For example, if you want to customize the color of all messages from system X, you must Include system X in your filter. Once you have done that, you need to specify the colors.

To color code messages pending a response: Step 1. From the Color Filter List, create a new filter.

Step 2. In the System i tab, select Message Type and deselect all checkboxes except for Answer Pending.

Step 3. Select the color you want Answer-pending messages to appear in.

For configuration details see section 3.1.14 - Colors in this Business View on page 17.

With Display Filters, you can filter out all of the messages that are not of interest, using any parameter such as system, subsystem, message ID, message type, severity, job name, user name, date, message queue, or message text. You can use generic names in filters, and you can use both include and exclude functions.

To access the Display Filter configuration, click the Filters in this Business View button in the toolbar or right-click the Business View you wish to configure and select Edit Filter. The Display Filter window appears.

Figure 152 – Display Filter

Click the Create Inclusion Condition button to add an inclusion condition (i.e. all messages which come from system NUMBER1) or the Create Exclusion Condition button to add an exclusion condition (i.e. all messages from any system except system NUMBER1).

Once you have decided the inclusion or exclusion condition, the Filter configuration window appears. In this window, you can set any condition you wish for customizing your current view.

In the Options sections select what system you want to set a filter for:

• System i

• ThinkServer

• Console messages

• Any System

Note The tabs available in the bottom half of the window, change according to your selection.

There are four tabs in the Filter Configuration window:

• General

• System i

• ThinkServer

• Console 8.8.1 Hyperhashing

When a new event is received by SmartConsole, it is normally processed by each Business View to test if it matches its filters. Processing events can be a time-consuming operation which can impact the overall performance of SmartConsole depending on the volume of events received.

Hyperhashing technology provides great improvements to overall performance by reducing the time taken to process Business View Filters.

Hyperhashing is only used for some of the filters, and only under specific configurations. But when these requirements are met, the filtering operation can be performed much faster than with standard filters.

Example

The power of Hyperhashing means that SmartConsole 7.5 takes less than two seconds to process 1000 events in a 10,000 Business View system!

You can easily recognize Hyperhashing-capable filters because they are displayed in bold text on the Business View Filter's dialog, (see Figure 153 below), and include:

• System

• Agent Code

• Message ID

• Event ID

• Computer Name

• Category

Tip The more Hyperhashing filters you use, the greater your performance will be!

Figure 153 – Hyperhashing Filters

To use Hyperhashing technology: Step 1. Create or edit a Business View Filter (For more information on configuring filters, see see section 8.9 - How to Configure a Filter on page 141.)

Step 2. Select the type of filter from the following selections:

• System i • ThinkServer, or • Console Messages Step 3. Enter no more than one constant value for every Hyperhashing filter. A constant value is a literal value, without any wildcard characters (* or ?).

Step 4. Click OK to finish

Important Hyperhashing will not work effectively if:

• If the Any System option is selected

• more than one value is selected

• wildcard characters are used

Figure 154 – Entering the Constant Value “SADAMS” 8.8.2 General Tab

This tab allows the configuration of filters that may apply to both ThinkServer and System i systems, such as system name, agent code, date/time, and more.

Note Several filters appear in bold. It is highly recommended that these filters be set to improve the filtering process.

Figure 155 – Filters - General tab

System

Enter here all the systems that you would like to include or exclude in your filter. Click *All to clear the filter. Use the drop-down menu when entering to include or exclude systems that you are already working with.

Agent Code Specify here the Tango/04 agent code that you would like to include or exclude in your filter. Click *All to clear the filter. Use the drop–down menu when including or excluding systems that you are already working with. Following is a description of each agent code:

• API: T4WAPI messages. T4WAPI is a utility installed with Windows Server Agent. It writes a new record to the Tango/04 Windows Server Agent Database.

• AUD: VISUAL Message Center iSeries Security Agent – iSeries Audit Journal monitoring. See the VISUAL Message Center iSeries Security Agent User Guide for more detailed information.

• BCH: VISUAL Message Center Batch Jobs Agent – included in the iSeries Base Agent. Messages can be sent to any queue. See the VISUAL Message Center (iSeries Modules) User Guide for more information.

• CIT: Citrix Agent. For details see the Citrix Operations Agent User Guide.

• CNS: VISUAL Message Center Console messages (these messages are generated when the console loses the connection with target systems), see section 8.8.5 - Console Tab on page 140 for more information.

• CPR: VISUAL Message Center Crash Preventer Agent enables freezing of end-users sessions in case of error and allows you to reply to the interactive error message remotely from the console. See the VISUAL Message Center (iSeries Modules) User Guide for more information.

• DBA: Data Adapter ThinAgent – ThinkServer ThinAgent that queries an ODBC DSN. See the VISUAL Message Center ThinkServer User Guide for more information.

• DVM: Device Activity Monitor Agent is included in the iSeries Base Agent. See the VISUAL Message Center (iSeries Modules) User Guide for more information.

• EXC: Microsoft Exchange ThinAgents. For details see the Exchange Server Operations Agent (2003) or the Exchange Server Operations Agent (2007 - 2010) User Guides.

• FIL: Windows File System ThinAgents. For details see the Universal File Reader Agent - User Guide.

• HST: History queue agent (*QHST) – included in the iSeries Base Agent. See the VISUAL Message Center (iSeries Modules) User Guide for more information.

• INT: VISUAL Message Center Interactive Messages Agent – monitors all errors in any running interactive job for any user. See the VISUAL Message Center (iSeries Modules) User Guide for more information.

• JAM: Job Activity Monitor agent – included in the iSeries Base Agent – monitors the activity of iSeries jobs. See the VISUAL Message Center (iSeries Modules) User Guide for more information.

• JBM: Job Status Monitor agent – included in the iSeries Base Agent – monitors the status of iSeries jobs. See the VISUAL Message Center (iSeries Modules) User Guide for more information.

• JDM: Job Duration Monitor – included in the iSeries Base Agent – monitors the duration of iSeries Jobs. See the VISUAL Message Center (iSeries Modules) User Guide for more information.

• JMX: JMX Generic – messages from the generic JMX monitor in ThinkServer. See the JMX Generic Agent - User Guide for more information.

• JQM: Queue Status Agent – included in the iSeries Base Agent – monitors the status of iSeries queues. See the VISUAL Message Center (iSeries Modules) User Guide for more information.

• MSQ: SQL Server Security ThinAgents – ThinkServer ThinAgents that monitor SQL Server Security. See the VISUAL Message Center ThinkServer User Guide for more information.

• NT: Windows Server Agent – monitors the Windows Server Event Logs - See the VISUAL Message Center (iSeries Modules) User Guide for more information.

• ORA: Oracle Operations and Security ThinAgents – ThinkServer ThinAgents that monitor Oracle server operations and security. See the VISUAL Message Center ThinkServer User Guide for more information.

• OS4: iSeries Agentless ThinAgents – monitor iSeries Agentless Operations from ThinkServer. See the iSeries Agentless Operations and the iSeries Agentless Security - User Guides for more information.

• PCS: PCSACC

• PYG: Generic Python – messages from generic Python monitors in ThinkServer. See the Python Generic Agent User Guide for more information.

• RST: Restricted State Monitor – monitors systems in restricted state. For details see the VISUAL Message Center iSeries Restricted State Monitor User Guide.

• SPF: Spool Files Size – included in the iSeries Base Agent – See the VISUAL Message Center (iSeries Modules) User Guide for more information.

• SPJ: Spool Files by Job – included in the iSeries Base Agent – See the VISUAL Message Center (iSeries Modules) User Guide for more information.

• SPQ: Spool Files by Output Queue– included in the iSeries Base Agent – see the VISUAL Message Center (iSeries Modules) User Guide for more information.

• SQI: SQL Interactive Monitor – monitors SQL Interactive statements. See the VISUAL Message Center iSeries SQL Agent User Guide for more information.

• SQL: SQL Monitor – monitors SQL statements. See the VISUAL Message Center iSeries SQL Agent User Guide for more information.

• SQP: SQL Server Operations ThinAgents – ThinkServer agents that monitor SQL server operations. See the VISUAL Message Center ThinkServer User Guide for more information.

• TCP: Network Monitors - ThinkServer agents that monitor mail, ping, pop3, and other network services. See the VISUAL Message Center ThinkServer User Guide for more information.

• TES: Test Monitor – ThinkServer ThinAgent used to send test messages. See the VISUAL Message Center ThinkServer User Guide for more information.

• TS: ThinkServer monitor – Monitors ThinkServer application messages, for example, environment messages or program internal errors.

• UIN: User Inactivity Agent – included in VISUAL Message Center iSeries Base. See the VISUAL Message Center iSeries SQL Agent User Guide for more information.

• VSM: VISUAL Service Manager

• WAS: WebSphere Application Agent Performance ThinAgents. See the WebSphere Application Server Operations Agent (Version 5.x) and the WebSphere Application Server Operations Agent (Version 5.x) User Guides for more information.

• WAT: Universal Transactions ThinAgent – monitors Universal Transactions using ThinkServer. See the Universal Transaction Agent User Guide for more information.

• WEB: Web Availability and Response Time Agents. For details, see the Web Availability and Response Time Agent User Guide.

• WHE: Windows Health ThinAgents – ThinkServer ThinAgents that monitor key indicators of Windows health. See the VISUAL Message Center ThinkServer User Guide for more information.

• WIN: Windows Lightweight ThinAgents – ThinkServer ThinAgents that monitor Windows machines and operating system health. See the VISUAL Message Center ThinkServer User Guide for more information.

• WLG: Windows event log.

• WPR: Windows Processes ThinAgents – ThinkServer ThinAgents that monitor Windows processes. See the VISUAL Message Center ThinkServer User Guide for more information.

• WSV: Windows (Extended) Services ThinAgents – ThinkServer ThinAgents that monitor Windows Services

• WTX: Web Transaction Response Time ThinAgent. See the Web Availability and Response Time Agent User Guide for more information.

• XHE: Linux /Unix Operations Agent. See the Linux & FreeBSD Operations Agent and the UNIX Operations Agent User Guides for more information.

• XLG: Linux/Unix Security Agent (Syslog). See the Linux & FreeBSD Security Agent and the UNIX Security Agent User Guides for more information.

• XML: XML ThinAgent. See the XML Generic Agent User Guide for more information.

• XPR: UNIX Process Agent.

Note Depending on the version of VISUAL Message Center you are using, some of these agents may be unavailable. Also, some of these agents are licensed separately. Ask your Tango/04 Business Partner for more information.

When You can either set the filter for anytime, or you can use a calendar to specify the exact dates and times that you would the filter to include or exclude. For more information on working with calendars see Chapter 5 - Calendars on page 46.

User Name Enter here all the iSeries user names that you would like to include or exclude in your filter. Click *All to clear the filter. Use the drop-down menu to include or exclude user names that you are already working with.

Search in the Message Text VISUAL Message Center allows you to search for text strings in the message, so that you can include or exclude messages with a certain text string. This is a useful way to search for messages according to the nature of the message without the need to select by Message ID.

Custom Logical Condition VISUAL Message Center allows you to build advanced filters, using:

• Message variables: − Particular message details, such as the Message ID, job name, system date etc., − System variables and User-Defined or Global Variables that have been included in the message, i.e. &VAR01.

• Complex expressions: include expressions such as AND, OR, NOT, XOR etc., using the ALEV Logical Expression eValuator. For complete information about variables and expressions of this guide see Appendix B: ALEV Logical Expression eValuator on page 216.

To create a custom filter: Step 1. Click the Custom Logical Conditions button to open the Advanced ALEV Filter Editor

Figure 156 – Advanced ALEV Filter Editor

Step 2. Enter your statement directly into the window.

• If you want to see the available user defined variables use the buttons at the top of the window. • To see the message variables and complex expressions available press CTRL+SPACE. You will see a number of wizards displayed at the top of the list. • Select the Variables Wizard to see a list of all variables and constants per category. Double-click a variable or constant to select it in your filter. • Likewise there are wizards for ALEV functions, LIKE and MATCH function. In this way you can create advanced message filters that evaluate various message properties, for example:

((&SYSTEM = 'PRODAS') AND (&JOBNAME = 'QINTER')) OR (&SUBSYSTEM = 'QBATCH')

In this example, we will receive all messages from QBATCH in any system, as well as just those messages from QINTER in system PRODAS. To check the expression, click the check mark button.

Below is a more complex example:

Message ID CPA3394 needs to be analyzed. The message text contains the name of a printer. We want to make an alarm for all printers starting with PRT. When the first level text contains the name 'PRT' then it should do something like call a program. But not when the text contains ‘PRTABC’ because the ABC printer needs special attention.

First of all you have to see the structure of the message you are going to monitor, in this case CPA3394:

Enter DSPMSGD CPA3394 (option 1)

Figure 157 – Display Formatted Message Text screen

The variable number 5 will contain the name of the printer device. To see the variable type use option 2:

Figure 158 – Display Field Data screen

Now you can see that the variable is a character string 10 bytes long.

At this point you're ready to prepare the alarm. In this case you need two alarms: the first must be triggered when the device name starts with PRT but the full name is not PRTABC. The second one must only be executed when the device name is PRTABC.

Advanced filters solve the problem. There are two kinds of variables within VISUAL Message Center:

• The first set contains attributes, for example, about the job that issued the message, the system name or the message ID, among others.

• The second set, whose names start with &VAR, contains the variables in the text of the message itself.

As the correspondence is one to one, meaning that field &1 of DSPMSGD option 2 will be named &VAR01, and so on. In our example, we will need to use &VAR05, because field &5 of the message will contain the device name.

When working on a string, the sub string is a very useful function to use because it allows you to perform your check on just a portion of the variable.

The resulting expression for the first alarm will be as follows:

(&MESSAGEID='CPA3394') AND (SUBS(&VAR05,1,3) = 'PRT') AND (&VAR05<>'PRTABC')

This means: trigger the alarm when message ID is CPA3394 AND the first three characters of the device name are 'PRT' AND the complete name of the device is NOT 'PRTABC'.

The second alarm will be:

(&MESSAGEID='CPA3394') AND (&VAR05= 'PRTABC')

This example gives you an idea of how the Advanced Filter can be used. If you have specific questions or would like help then do not hesitate to contact your Tango/04 Business Partner.

Severity Range Enter here the severity that you would like your filter to look for, severity 99 being the highest (most severe).

Criticalness Range Enter here the criticalness that you would like your filter to look for. To learn how to customize criticalness ranges, see the Configure Criticalness section on page 33. 8.8.3 System i Tab

This tab allows the configuration of filters, which apply only to System i systems, such as Message ID, queue, and subsystem.

Figure 159 – Filters - System i Tab

Message ID Here, enter the message IDs that you would like to include or exclude in your filter. Click *All to clear the filter. Use the drop-down menu when entering to include or exclude message IDs that you are already working with.

Job Name

Enter here all the System i job names that you would like to include or exclude in your filter. Click *All to clear the filter. Use the drop-down menu when entering to include or exclude job names that you are already working with.

Queue You can select any message queue. Just specify the message queue and its library, or click *All to select all message queues from a certain library, which is useful with many third-party products that create many message queues.

Search in the Second Level Messages have two levels of message texts. SmartConsole will allow you to search for text strings in the second message level. For details how to search text in the first level see the Search in the Message Text section on page 133.

Subsystem Enter here all the System i subsystems that you would like to include or exclude in your filter. Click *All to clear the filter. Use the drop-down menu when entering to include or exclude subsystems that you have already received messages from.

Message Type

You can select messages by their message type by checking the option boxes for the required messages.

Tip If you are connected to more than one System i and you choose to include the subsystem QINTER for example, you will include messages received from that subsystem on all iSeries that you have included in your system filter. If you would like to configure a more complex filter, then use the Advanced Filter options discussed in the section - Custom Logical Condition on page 134.

Figure 160 – System i Filters - Message Type

Accounting Code

You can select messages according to the accounting code. 8.8.4 ThinkServer Tab

Similar to the previous tab, in the ThinkServer tab you can configure filters that apply only to ThinkServer events, such as Domain and Category.

In this tab you can configure filters for messages received from ThinkServer, such as computer name, domain, event log type, and more.

Figure 161 – Filters - ThinkServer Tab

Event ID

Here, enter the Event IDs that you would like to include or exclude in your filter. Click *All to clear the filter. Use the drop-down menu when entering to include or exclude Event IDs that you are already working with.

Computer Name Here, enter the Computer Names that you would like to include or exclude in your filter. Click *All to clear the filter. Use the drop-down menu when entering to include or exclude computer names that you are already working with.

Source Name

Here, enter the Source name that you would like to include or exclude in your filter. Click *All to clear the filter. Use the drop-down menu when entering to include or exclude Source Names that you are already working with.

Category

Here, enter the categories that you would like to include or exclude in your filter. Click *All to clear the filter. Use the drop-down menu when entering to include or exclude Categories that you are already working with.

User Domain Here, enter the User Domains that you would like to include or exclude in your filter. Click *All to clear the filter. Use the drop-down menu when entering to include or exclude User Domains that you are already working with.

Windows Message Type There are five Windows Message Types

• Error

• Warning

• Information

• Success audit

• Failure audit

Click the Windows Message Type button to open a window where you can select the message types that you would like to include or exclude in your filter. By default all message types are selected.

Event Log Type

Here, enter the Event Log Type that you would like to include or exclude in your filter. Click *All to clear the filter. Use the drop-down menu when entering to include or exclude Event Log Types that you are already working with. 8.8.5 Console Tab

Normally, the agents installed in the server systems generate messages and events received by the VISUAL Message Center console. However, there are some events that are generated directly by the console, such as disconnections from monitored systems. In this tab you will be able to filter such events.

The console tab is useful for setting fully customizable alarm conditions when the connection with the target server is lost.

Figure 162 – Filters - Console Tab

Console Message ID There are three local messages.

• CONS001: The system has not been able to start the connection.

• CONS002: The system was started and the connection has been lost.

• CONS003: The system has started the connection.

Console Category At this time there is only one console category: communications.

Console Message Type There are three Console Message Types:

• Error

• Warning

• Information

Click the Console Message Type button to open the Message Type window, where you can select what message types you want to filter. By default all message types are selected. 8.9 How to Configure a Filter

Let’s say that you wish to set the current view in order to see only events in system MUNDAKA generated in any subsystem but T4NICELINK.

Therefore, an inclusion and an exclusion condition must be created.

To configure a filter with an inclusion condition: Step 1. Open the Business View where you want to create the filter

Step 2. Click the Create Inclusion Condition button

Step 3. In Options select System i

Step 4. In the General Tab click the System button and make sure that the Included check box is selected.

Figure 163 – System(s) to include

Step 5. Select MUNDAKA from the drop-down menu and click OK.

Note The text next to the System button in the General tab of the Filter window, has changed from <*All> to and is marked in blue.

To add an exclusion condition to the same filter: Step 1. Click the System i Tab

Step 2. Click the Subsystem button and make sure the Excluded check box is selected.

Figure 164 – Subsystem(s) to include

Step 3. Choose T4NICELINK from the drop-down menu and click OK.

Note The text next to the Subsystem button in the System i tab of the Filter window, has changed from <*All> to and is marked in blue.

Step 4. Click OK to close the filter configuration window

Step 5. The new filter appears in the inclusion condition section of the screen. You can rename the condition if you wish. In our example we’ve renamed the filter Mundaka.

Step 6. Make sure the filter you want to use is selected; or it will not work.

Step 7. Click OK to exit the filter configuration

Note The filter is applied immediately and that the Message Grid now only contains messages that come from Mundaka and that there are no messages from T4NICELINK.

To remove the filter simply click the Filter button and deselect the filter. You can also delete the filter entirely if you like.

Figure 165 – Display Filter window - deselect the filter 8.10 Storing Business View Filters

Whatever filters you apply to your Business Views you will want to make sure you save your configurations, whether as a back-up, or for using them in other Business Views.

The following tools can help you achieve this. 8.10.1 Importing and Exporting Business View Configurations

To import / export Business View configurations: Step 1. Right-click a Business View to display the context menu.

Step 2. Click Import & Export from the menu to reveal further options:

Figure 166 – Import & Export menu options

For a detailed explanation of these menu options see section 6.5.17 - Import & Export on page 78.

The Import & Export options allow you to import or export filter configurations. You will be asked to specify which Business Views you wish to import/export and the target directory on your PC from where you want to export/import your filter configurations. This is particularly useful if you want to share your filter configurations with other users.

It is advisable to maintain a copy of your filter configurations; you can export your configuration to save a backup copy in a safe location.

The *ALL options resets the filter configuration to *ALL for all options, i.e. all messages received will pass through the filter. 8.10.2 Saving Business View Contents to HTML, XML, and XLS

To save a table of a Business View’s existing messages in HTML, XML or XLS format: Step 1. Right-click the message list of any Business View to open the context menu

Figure 167 – Saving Business View messages to HTML, XML, or XLS

Step 2. Click one of the following menu options, depending on the desired output format of the table:

• Save To HTML... • Save To XML... • Save To XLS... The saved table can then be used to generate status reports, make historical analyses, etc., based on the filter criteria of the Business View.

See also sections Save to HTML, Save to XML and Save to XLS on page 95 and page 96. 8.11 Saving Business Network and Alarms Hierarchies

You can save visual representations of your Business Network and alarm hierarchies to RTF files or as bitmap images (BMPs), so that you can replicate them in another document as they appear in the console.

To do so, simply right-click the Business Network or alarm Tree; if you want to export the structure to RTF, select Save Structure to RTF and name the file.

To save the Business Network structure as it appears in the console: Step 1. Right-click the Business Network and select Copy Structure to Clipboard.

Step 2. Open a new Word document

Step 3. Click Edit from the menu bar and Select Paste Special

Step 4. Select Bitmap image in the window that appears.

You will then have a graphical copy of the hierarchy in your Word document.

See also sections Copy Structure to Clipboard , Save Ordered Structure to RTF File and Save Structure to RTF File , on page 81.

Chapter 9 9 Preprocessing

Preprocessing allows you to filter messages and make changes to them before they reach the console. You can reorganize the information contained within a message, or add information to messages so that you can process them more efficiently later.

For example, you can add an identifying variable to a series of diverse messages to make it easier to group them into one Business View, or add a line of text to the beginning of particular messages to make them more understandable.

Preprocessing uses the same filters as alarms, in combination with the ALEV Expression eValuator. This provides greater granularity for detecting incoming messages and gives you the power to adjust them and adapt them according to your IT environment’s needs.

Effectively, through preprocessing you create a primary screening and organization process for messages before they reach the alarms, actions, and Business View configurations of the main VISUAL Message Center SmartConsole. 9.1 Preprocess Filter List Window

To open the Preprocess Filter List window: Step 1. From the menu bar click Change and select Preprocess List.

Figure 168 – Preprocess Filter List

Step 2. The Preprocess Filter List window opens. Using the icons on the toolbar, you can create new preprocesses, edit the filters or expressions of existing preprocesses, and copy, delete, import, or export preprocesses. 9.1.1 Preprocess List Hierarchy

Once you have configured several preprocesses, they will appear on the left in the Preprocess Filter List window. Select a preprocess to see its properties on the right.

The list represents the hierarchical order in which preprocesses are executed on each message before it arrives at the console. To save processing power and time, you have the option of stopping messages from continuing down the list once it has triggered a preprocess. This is useful if you have some preprocesses that are more important than others, and can help you filter your messages more efficiently by organizing your preprocesses in order of importance.

To do this, right-click any preprocess. You will see that, apart from the other options available in the main screen, you can also Continue processing after filter success or Stop processing on filter success. If you want SmartConsole to stop processing a message once it has met the selected preprocess filter, choose Stop processing on filter success as shown below.

The default setting is Continue processing after filter success.

Note Deactivating a preprocess using the check box does NOT deactivate the entire list below it. All active preprocesses below will be carried out as usual.

When you right click a preprocess you can move it up or down in the list according to its importance. 9.2 Creating Preprocesses

To create a preprocess, you must first configure the filters and then define the expressions. 9.2.1 Filters

By clicking New on the toolbar or double-clicking in the left hand column, you access the Filters configuration window. For more information on configuring filters see Chapter 8 - Working with Console Filters on page 124.

Once you have configured your filters, close the Filter window by clicking OK. The Expression List window appears. 9.2.2 Expression List

The Expression List window is where you create, edit, copy, delete and activate/deactivate the expressions for your preprocesses. You can also rename expressions by right-clicking them, giving them more descriptive titles. By default they appear with the ALEV expression that they activate.

Figure 169 – Expression List window

When you select New Expression or double-click on the window, the Advanced ALEV Filter Editor appears. 9.2.3 Advanced ALEV Filter Editor

In this window, you create the logical expressions for actions you want to carry out on filtered messages before they reach the console. It is similar to the Custom Logical Condition function in Chapter 8 - Working with Console Filters on page 124, the difference is that here, instead of simply configuring a condition that a message must meet, you are configuring an action to be taken on the message.

This uses the Arithmetic-Logic Expression eValuator v1.2 to generate a wide range of customizable logical conditions. For more information see Appendix B: ALEV Logical Expression eValuator on page 216, or see the ALEV Expression Evaluator section found in the Reference document available in Windows Start menu > Programs > VISUAL Message Center SmartConsole folder.

When the Advanced ALEV Filter Editor appears, there is already an example expression in the window. Delete this example before creating your own expressions.

Figure 170 – Advanced ALEV Filter Editor

Expressions can be used to perform a huge range of functions on messages and message variables. For example, you can change the criticalness of a specific incoming message. If a message with Message ID CPI1133 arrives with a severity of 40, your criticalness configuration may class this as a

Warning, whereas you know that it is harmless. You can set a preprocess filter to detect messages with this ID. Then, in the Advanced ALEV Filter Editor, you enter the following expression:

&CRITICALNESS:= 0

This will change the criticalness of the message to 0 before it arrives at the console.

Once you have created an expression, check the syntax with the Expression checker to make sure that it is correct.

To see the message variables and complex expressions available press CTRL+SPACE. You will see a number of wizards displayed at the top of the list.

• Variables: The Variables section contains a broad range of common variables for creating conditions, organized into easily identifiable groups. Double-click any of the variables to add them to the expression.

• Functions: The Functions icon displays a pop-up guide detailing the different ALEV operations available to you. Again, double-click a function to add it to the expression.

Remember that the possibilities open to you through preprocessing are extremely far-reaching, especially when you use user-defined variables. For more information on these variables and how they can be used in Preprocessing, see section 6.7.3 - User Defined Variables Tab on page 88.

Chapter 10 10 Alarms

10.1 Why Configure Alarms?

Alarms save you from having to manually monitor all messages and events (Windows, iSeries, Unix/ Linux), and just alert you to those that require operator intervention.

If you fail to notice an important message on your system, it could delay all your processes. By receiving an alert and taking action immediately, you can avoid all types of operational problems, including database corruption, delays in batch processes, or a halt in data replication. The consequences and costs of these issues may vary but will always be significant. Investing time and energy into configuring and maintaining alarms correctly is important, and will maximize your return on investment in the long run.

You can configure as many alarms as you need to perform a wide variety of actions such as:

• Send alerts to operators so that they can respond to important messages. You can send alerts by SMS, e-mail or display them directly on the console. You can also alert operators to an important message by playing a sound.

• Use two-way messaging (SMS) to allow operators to reply to messages remotely, from anywhere in the world.

• Configure responses to specific messages, such as running an iSeries command

• Retrieve information required to diagnose and even solve problems

• Reply automatically to messages

• Integrate with other applications or systems management frameworks

• Advise and help operators in response to specific messages received

As you can see from these examples alarms help to ensure that no important events go unnoticed. They allow operators to focus on resolving potentially threatening situations that require operator intervention as less important events are filtered out and actions that can be automated are attended to by SmartConsole.

10.1.1 Protecting Your Alarms

You can define which users and roles can create or edit alarms. Please see section 4.1 - AccessServer on page 38 for instructions on how to configure access to alarms in SmartConsole. 10.2 Setting an Alarm Filter

To access the alarms, click the Alarms button on the toolbar. The alarm configuration dialog box appears.

Figure 171 – Alarm Configuration dialog box

This dialog box shows all the alarms that have been configured, with a brief summary of each alarm in the Description area. The most frequently used functions are available from the toolbar in the alarms window and include buttons for Add, Delete, Copy, Paste, Print, Export and Import alarms, in addition to buttons for Edit Alarm Filters and Actions for each alarm. In the Options menu you will find functions including Save Alarm to RTF File, Copy Structure to Clipboard, Change Passwords and Enable All Actions and Reset All Repetition Counters.

When you configure alarms you start by indicating what events the alarm must apply to using the alarm filter configuration. The alarm filter configuration is nearly identical to the display filter configuration discussed in the previous chapter except for the addition of the Advanced tab. You can start to configure your alarm filter by following the filter instructions in the previous chapter.

The Advanced tab, which is only available to the alarm filter configuration, allows you to configure the execution of an alarm when a particular message is not received within a given period of time.

Figure 172 – Filters - Advanced Tab (alarms only)

An event passes this filter means the actions configured for this alarm will be executed for each event that matches the alarm filter.

No event passes this filter in the specified calendar means the actions configured for this alarm will be carried out if no events match the alarm filter during the time period set in the calendar.

Note You can use the calendar to include days (i.e. event passes filter in these days) or to exclude days (i.e. the event passes the filter not in these days).

To select a calendar click the Specified Calendar button .

A window appears where you can select an existing calendar, create a new calendar, or edit an existing calendar. For details regarding calendar configuration see Chapter 5 - Calendars on page 46.

Finally indicate whether the days in the calendar are to be included or excluded for this alarm.

No event passes this filter during a period of XX minutes after activation of this alarm is used to make sure a particular process ends within a certain time of starting. For example make sure an event is received for the end of a backup procedure backup process.

There are two options for this check:

• Once off: after the event is received or the time has run out, do not check for the event again. Used for cases, where not receiving the signals, is a problem that needs attention from the operator.

• Continuous: starting to check for the event again after one is received or after the specified time intervals run out. Used for cases where a process that should terminate within a certain period did not, but it is possible and acceptable that the process takes longer. In these cases the operator simply wants to be notified when the event has completed. It can also be used for checking on repetitive processes.

Once you have completed all your filter options, click OK. The Alarm Actions dialog box now appears, where you select the types of alarms that you would like to activate.

Note The alarm configuration functions independently of Business Views.

10.3 Setting Alarm Actions

Once you have completed configuring the alarm filter, the Alarm Actions window appears where you can configure many different actions to take if an alarm is triggered.

Figure 173 – Alarm action configuration

Note You can reopen this window by right-clicking an alarm and selecting Edit Actions.

To enable different types of alarm actions, you must select the corresponding check box in the Actions window, shown above. When you select a particular option a new tab will appear allowing you to configure details for that alarm action.

Some functions may be grayed out – that is because you do not have support for those functions on your PC, or you have not installed the necessary service. Contact your Tango/04 Business Partner for more information.

The actions you select here will be carried out when an event is received that matches the alarm filters.

Remember that you can use ALEV variables throughout these actions to configure complex alarm actions. For more information see Appendix B: ALEV Logical Expression eValuator on page 216. You can also reference the ALEV Documentation included in this installation.

The following sections describe the different actions and their configuration. 10.3.1 E-mail Action

The e-mail action can be used to send normal e-mail text messages to any mail recipient. Of course, most telephone companies will also allow you to send e-mails to pagers and mobile phones. Therefore, the application can alert you via mobile phone of any application error on your system, no matter where you are, so you can be notified immediately whenever critical events are produced.

Select the Send an E-mail check box in the Actions tab and click the Email tab that appears.

Figure 174 – Configuring e-mail support in an alarm

If you are not using the SMTP List (see SMTP Server List below) configure the SMTP details directly in the e-mail tab:

STMP Server: Enter the IP address of your SMTP server, or the name of the host if you are using DNS with your SMTP server. If you are not sure, contact your network administrator for more information. It is most convenient to configure an SMTP server in the SMTP server list – for more information, see the SMTP Server List section below.

SMTP Port: The port used by the SMTP server is usually 25. If you are not sure, contact your network administrator for more information.

Tip You may be able to see the port used by checking your own e-mail settings in your e-mail software.

E-mail User ID: The SMTP server user name. It is usually not necessary to change this, but some SMTP servers require this. If you are not sure, contact your network administrator for more information.

Mail From: This is the address that will appear as the sender of alarm e-mails. This must be configured in the format [email protected]. Without the @ symbol, the e-mail will not be sent successfully.

Password: enter the password required for connecting to the SMTP server. The password field is grayed out if the SMTP Server requires authentication check box is left unchecked.

SMTP Server requires authentication: Check this box if the SMTP server requires a password. The Password field above it will be activated so that the user can enter the required password.

Send mail to: You can introduce more than one e-mail address by separating the addresses with commas (,) or semi-colons (;). It is best to use the Address Book in order to configure many e-mail addresses at one time, reusing them in different alarms. For more information see the Address Book section on page 156.

E-mail Subject Format: The default subject line is VISUAL Message Center. You can customize the subject by selecting the Customized check box and entering a subject template. You can either select an existing template or create a new template.

E-mail Message Format: As described above, an e-mail message can be sent as a normal e-mail (Full message format), or to a mobile phone or pager device (short message format). The short message format only includes the basic error message details, i.e. message ID, job, user, first level text etc. The long default message format includes the second level error message text.

You can also configure a message template to introduce your own customized message information. This could include emergency contact details, such as an operator’s mobile telephone number. For more information about configuring templates see the Templates section on page 157.

Add Reply Code: If you select the Add code to reply when it is an inquiry message check box, the recipient will be able to reply by e-mail to the inquiry message directly from the iSeries.

Send Mail Test: Once you have configured your e-mail details you can send test e-mail by clicking the Mail icon by the side of the e-mail address dialog. If everything has been correctly configured you will receive the following message:

Figure 175 – Sending test e-mail

SMTP Server List An SMTP Server List can be configured if you want to send the message via various SMTP servers, which is useful if one of the SMTP servers becomes unavailable. SmartConsole will attempt to send the message through the first server in the list. If it fails, it will try the next, and so on.

Figure 176 – SMTP server list

To access the SMTP Server List, click the SMTP Server List button from the e-mail action configuration dialog box. You can also access the SMTP Server List from the Tools menu in the menu bar of the SmartConsole.

When an alarm is activated to send e-mail with the SMTP server list configured, SmartConsole will try to send that e-mail message using the SMTP servers listed in sequence, starting with the first. It is useful to configure a back-up SMTP server – after all, the message that SmartConsole is trying to send could be a notification that the SMTP server is down! SmartConsole will keep trying until one of the servers sends the mail successfully.

To add a new SMTP Server in the SMTP Server List Configuration window, click Options and select New. Add the SMTP server details as described in section 10.3.1 - E-mail Action on page 154.

When you have introduced all SMTP servers, you can change their priority using the Up and Down buttons.

For information about exporting or importing configured SMTP server lists, see section 10.6.2 - Exporting or Importing Individual Alarms, Calendars, Actions Sets, Special Days, Address Books, or SMTP Server Lists on page 178.

Address Book The address book can be used to store e-mail addresses for use in various e-mail alarms. It saves you from having to enter e-mail addresses every time you configure an alarm.

Figure 177 – E-mail address book window

To add new addresses: Step 1. Click Options from the menu bar and select New.

Step 2. Enter all the e-mail addresses that you wish to use, separating addresses with a comma (,) or semi-colon (;). It is also possible to enter a single mobile phone number to send the message to.

For information about exporting or importing configured Address Books, see section 10.6.2 - Exporting or Importing Individual Alarms, Calendars, Actions Sets, Special Days, Address Books, or SMTP Server Lists on page 178.

Templates With SmartConsole you can configure templates to use for sending e-mail alarms, entries in a Windows event log, or in visual alarms (pop-up windows).

When configuring templates, you can insert any text you wish, such as emergency contact information, specific instructions for operators, and so on. You can create as many templates as you wish, so you may chose to create templates for different types of error message – for example, you may want messages associated with a particular application, to include additional contact information, specific to those people responsible for managing that application on your system.

To configure templates, click the Edit Templates button from the Email, Visual, or Windows Event Log configuration tabs. Templates are also available from the Tools menu in the menu bar of SmartConsole. The default message template appears.

Figure 178 – Default message template in the Template configuration window

To create a new template, click the File menu and select New. You can insert any text that you wish, and can insert variables by clicking Variables from the File menu in the template configuration window. The Data Dictionary that appears shows a list of all available variables, including system variables such as &VAR01. This gives you great freedom to customize your alarm messages.

To add a variable, position your cursor where you want to add it, then click the File menu and select Variables. From the Data Dictionary that appears double-click the desired variable to add it to your template. 10.3.2 Audible Alarm – Sound

You can get VISUAL Message Center to respond to an alarm by playing any sound file. You can use a typical alarm sound, or alternatively you can pre-record voice instructions for operators.

To configure an alarm to play a sound: Step 1. In the Alarm Actions window click the Actions tab

Step 2. Select the Play a Sound check box

Step 3. Click the Sound tab that appears in the same window.

Step 4. Browse for sound files on your PC or your network using the Looking Glass button.

If you leave the sound field blank the default system sound will be used. Use the Play button to test the selected sound. 10.3.3 Execute a PC Program

SmartConsole can run any PC program or file attached to a PC program, such as a Word document or an.AVI video. You can configure the PC program alarm to give operators instructions when error messages are produced.

For example, if you have a company knowledge base with standard procedures to follow in specific situations, you can link SmartConsole alarms to documents in your knowledge base, so operators are able to respond quickly to important messages.

There are several tools included in SmartConsole. Please refer to the Tools document included in this installation for more information. This document can be accessed by clicking the Windows Start button > All Programs > Tango04 > VISUAL Message Center SmartConsole > Reference. Navigate to Tools & Tips and open the Tools document.

Of course you can select many other programs to execute.

Important About the CommandSender tool, which can be used to send a command to be executed on your remote Java iSeries Server:

For ThinkServer versions lower than V1.6 SP03 HF05, the CommandSender tool is based on Apache’s Axis1 technology. However, beginning with ThinkServer V1.6 SP03 HF05, the CommandSender tool is based on Axis2 technology, and therefore another CommandSender tool must be used: it can be found in the folder v2.

Figure 179 – Working with PC program alarms

To configure an alarm to execute a PC Program: Step 1. In the Alarm Actions window click the Actions tab

Step 2. Select the Execute a PC Program check box

Step 3. Click the PCProgram tab that appears in the same window.

Step 4. Enter the PC command in the Command field – you can browse for programs or files by clicking the Find button.

If you wish to pass parameters from the message received to your PC program, include them in the Parameters field. To include a parameter position your cursor in the parameters field and double-click the desired parameter in the variable list.

For example in Figure 128 you see the configuration required to run Norton Antivirus on the system where the message was produced. The Command field contains the location of the executable. The Parameters field includes the system and name of the computer that produced the message so that Norton knows what computers to check in response to the alarm. 10.3.4 Annotate in the Windows Event Log

SmartConsole can be used to send messages to any Windows event log. You may already be using products that monitor your Windows event logs. You can use SmartConsole to add iSeries functionality to your Windows event log-monitoring framework.

This option will be grayed out if the PC you are working with does not use a Windows operating system.

Figure 180 – Working with Windows event log annotations

To configure an alarm to send messages to any Windows event log: Step 1. In the Alarm Actions window click the Actions tab

Step 2. Select the Annotate in the Windows Event Log check box

Step 3. Click the Windows Event Log tab that appears in the same window.

Step 4. The configuration dialog box for sending alarms to a Windows event log opens. Enter the IP address or the name of the target Windows server in the Server Name field.

Step 5. You must also register the event ID in the target machine using: RegEventLog.Exe. This program is usually found in the product path:

C:\Program Files\TANGO04\SmartConsole

If you do not register the event ID in the target machine, the event will still be sent when the alarm is produced but the Event Viewer will add the entry The Event ID (X) is not found...

The default values are Event ID = 4096, Event Category = 1, and Event Type = Information.

If you change the event ID value, the event will be sent when the alarm is produced, but the Event Viewer will add the entry The Event ID (X) is not found... You can change the other values as you wish.

You can customize the message format by using a template, see the Templates section on page 157, or by selecting the short or full message format.

10.3.5 Show a Window – Visual

The simplest type of alarm is a pop-up window, which displays all the message information that you need on-screen. If you are working with another application on your PC then you will be interrupted by the alarm – the pop-up window will appear in front of the work that you are doing to alert you.

To configure a visual alarm: Step 1. In the Alarm Actions window click the Actions tab

Step 2. Select the Show a Window check box

Step 3. Click the Visual tab that appears in the same window.

Step 4. There a number of options with the Visual alarm. You can configure the window to close automatically after a period of time set by the user. If you would prefer the window to stay open until an operator manually closes it, select the Do not automatically close the message window check box.

You can also configure the message format – short, full, or use a customized template. By using a template you can add your own information to the message text, such as emergency contact details, or standard procedures that an operator should follow. For more information see the Templates section on page 157.

Figure 181 – Working with visual alarms

10.3.6 Execute a SNMP Trap

SNMP (Standard Network Management Protocol) is a standard protocol used to manage networked hardware and software devices. SNMP uses an administrator to manage messages, and agents which are installed on each device being monitored.

As SNMP is a standard protocol that many systems management frameworks, such as HP Open View, Tivoli’s systems management products, and CA Unicenter support.

VISUAL Message Center can be integrated with these system management frameworks through the use of SNMP traps – packets of information that an agent sends to an SNMP administrator. VISUAL Message Center acts as an iSeries agent, sending iSeries specific information to those system management frameworks. If your organization uses products such as these to monitor your NT, UNIX, or Mainframe systems, you may want to investigate the use of VISUAL Message Center with SNMP traps to add iSeries functionality to those existing frameworks.

For SmartConsole to offer SNMP support, you must first install the SNMP Agent and Service support. If SNMP Support is not active on your system you will find this action grayed out.

For complete information on installing and configuring SNMP support, see the Alarm Support with SNMP Traps document which you can find in the Reference page located in the SmartConsole program menu on your PC.

To configure an alarm to execute a SNMP trap: Step 1. In the Alarm Actions window click the Actions tab

Step 2. Select the Execute a SNMP Trap check box

Step 3. Click the SNMP tab that appears in the same window.

Note Tango/04’s OpenView Connector is available to connect VISUAL Message Center’s iSeries monitoring capability to HP Open View. For more information, please contact your local Tango/04 Business Partner.

10.3.7 Execute a DLL Function

SmartConsole can use DLLs to send information and communicate with external applications or databases. For example, you could create a DLL that introduces information from SmartConsole into your Help Desk database.

In the SmartConsole directory on your PC, there is a directory called DLL Example, which contains a Visual C++ example for creating a DLL, and the necessary types to be able to exchange data between SmartConsole and the DLL.

The example is quite specific and contains all the data necessary to create a DLL. Fill in the functions that you require the DLL to perform wherever you see the text Put your code here.

Once the DLL has been created with the necessary code, add the DLL to SmartConsole.

To add the DLL to VISUAL Message Center: Step 1. From the SmartConsole click the Tools menu and select Add DLL Action.

Step 2. In the window that appears add an identifier and the directory where the DLL is located.

From then on, the new DLL will be registered by the product and can be used like any other action offered by the product.

To configure an alarm to execute a DLL function: Step 1. In the Alarm Actions window click the Actions tab

Step 2. Select the Execute a DLL Function check box

Step 3. Click the DLL Functions tab that appears in the same window.

Step 4. This tab shows a list of available DLL actions. Select the DLL actions you want to execute when this alarm is triggered. 10.3.8 Execute an OS/400 Command Sequence

In many situations, you may wish to run a command in response to a message. This can help you automate some of your operations by performing standard message responses automatically. For example, in a communication line failure, you may want to run a CL command to vary off and vary back on the line.

Note Commands run from the PC console are managed on the iSeries server side by NiceLink’s command execution manager (CEM) and executed by command execution program jobs (CE^P). Those jobs are configured and started during the install process.

To configure an alarm to execute an OS/400 command sequence: Step 1. In the Alarm Actions window click the Actions tab

Step 2. Select the Execute an OS/400 Command Sequence check box

Step 3. Click the AS/400 Commands tab that appears in the same window.

Figure 182 – Working with iSeries command actions

To enter a new command, click the New button in the OS/400 Commands tab. The Edit AS/400 Command dialog box appears:

Figure 183 – Editing iSeries command actions

Select the system to run the command on. You can enter your command directly in the command text area of the Edit AS/400 Command window and add any variables you want to use by double-clicking the desired variable. You can also prompt for commands using F4 or the button at the top of the edit AS/400 Command window as described in the next section.

Command Prompting In the edit AS/400 command window you can enter any iSeries command and use any variables from the message (such as the message number, job number, or even message variables). You can prompt any command from the interface by pressing F4 to see all command parameters as you would from your iSeries command line. Here is an example of a command prompt for the Display Job command:

Figure 184 – Using command prompting and entering variables in iSeries commands

The command entry utility includes drop-down menus to include parameter options from the AS/400, as well as convenient PC-style graphical calendars to choose dates and so on.

Add Message Variables to Commands – Data Dictionary To include variables from the message that produces the alarm, position your cursor in the appropriate command variable space and press F2 to open the data dictionary window, which includes a list of all variables available from the message. To select a variable from the data dictionary double-click the desired variable and it will be entered as a command parameter. You can also enter the variables

manually for example Job name is &JOBNAME and so on. Once you have finished building your command click OK until you return back to the AS400Commands tab.

Having built your AS/400 Commands, select whether to execute them simultaneously or sequentially. If you select to execute them sequentially the commands are executed in the order that they appear in the list. Use the Up and Down buttons to change the order of the commands.

You can instruct VISUAL Message Center what to do if a command fails:

• Temporarily disable the action for a system

• Execute a different action

Retrieving Spool File Output from an iSeries Command You can retrieve spool files after you have run a command from SmartConsole. For example, you may wish to configure a Display Job command in response to a message in order to get more information for diagnosing the problem that produced the message. The output from the DSPJOB command will go to a spool file, which SmartConsole will retrieve.

From the OS/400 Command tab you can tell SmartConsole to retrieve the spool file so you can see it from your PC. All spool files can be viewed from the alarm log. For more information see section 10.5 - Alarm Log on page 176.

Figure 185 – Retrieving spool file output from an iSeries command

Sending Spool File Output by E-mail You can also tell SmartConsole to send the spool file by e-mail (as a .ZIP file). Just enter the e-mail addresses in the space provided, or use your Address Book. This is especially useful if you want to provide as much information as possible to operators or consultants when sending error messages.

Example of sending a spool file output by e-mail

Typically when performance related messages are produced, the first thing that a system analyst would do is run WRKACTJOB or DSPJOB to check the status of active jobs on the system.

With SmartConsole, this can be performed automatically and instantly for the analyst. Just set your filters to select the important performance related messages. Configure the Alarms to notify the systems analyst by sending e-mail with all the message information. Add an iSeries command action to run the WRKACTJOB command, perhaps also adding a DSPJOB command specifying the particular job that produced the alarm, and send the spool file output by e-mail to the analyst. Hopefully, the analyst will then have all the information needed to react immediately to correct the situation.

10.3.9 Reply to Message

Some messages have a standard reply, so why waste time replying to them? By selecting Reply to message, you can automatically reply to specified messages with Cancel (C), Ignore (I), Retry (R), Go on Processing (G), Reply by Default (*DFT), or Reply by Text.

Figure 186 – Automatically reply to a message

For example, you may have a message stating that a file size limit has been reached. In this case you could automatically reply to such messages to increase the size limit of the file. Reply by text allows you to create custom replies to messages.

Note The message reply function will work for messages collected by the batch message agent (BCH), and those collected by the crash preventer agent (CPR). The interactive message agent (INT) does not offer the capability to reply to messages.

10.3.10 Sending and Replying to Messages via SMS or E-mail with Notifier

SmartConsole is integrated with Tango/04’s Notifier product, allowing you to send and reply to SmartConsole messages remotely via SMS or e-mail. This enables operators to receive and reply to critical system messages anywhere in the world.

The option Send an SMS is only available in SmartConsole if you have previously installed Notifier. If you want to suspend sending SMS messages at any time you can do so using the icon in your Windows system tray. For more information on Notifier, see the Notifier Configuration Guide.

Figure 187 – SMS alarm configuration

When configuring an SMS message alarm, you must first specify the phone numbers to send them to. Phone numbers can be configured in the address book. For more information see the Address Book section on page 156. Alternatively, you can retrieve the phone number to send to from the message variable. Simply right-click the Mobile Phone number field in the above dialog box to display the Data Dictionary and enter the relevant message variable.

You can also introduce SMS messaging support into your RPG and COBOL programs – using monitored iSeries system message queues – and SmartConsole with Notifier.

You can customize the format of the SMS message to be sent. By default a short message will be sent. If the message within the SmartConsole can be replied to, you will be able to do so having received the SMS message at your mobile phone or other device.

If it is possible to reply to a message (for example in the case of an inquiry message from the BCH agent, or a message from the CPR agent), the SMS message will begin with a code, normally of two characters (e.g. 5G). In order to reply to the message from your mobile phone, enter Reply on the phone, and then enter the reply code, followed by your reply text (e.g. 5G R). The message will be received by the server phone attached to the VISUAL Message Center console and will be processed by SmartConsole.

For more information on using SmartConsole with Notifier, see the VISUAL Message Center Notifier Configuration Guide.

Note Notifier, introduced in VISUAL Message Center version 4.5, replaces DirectSMS (valid only until version 4.1).

10.3.11 Send a Remote Message (Net Send Function)

The Net Send function allows you to send a graphical message to any or all computers on your Windows network. Target computers must be working on workstations with Windows NT 4.0 or higher.

In the Computers field, choose available computer names using the Looking Glass icon. You can select multiple computers by holding down CTRL on your keyboard and selecting computers with your mouse. The dialog also shows you which Windows versions those computers are running. You can also write the computer names manually if you prefer, separating each with semicolon (;). You can also write IP addresses if you wish.

Figure 188 – Configuring Net Send function

Select the message format by choosing to send a Short message (includes just the main message info, i.e. job name, message ID, time, system etc.), a Full message (includes all message text), or use a template where you can create a Customized message. For more information about working with templates see the Templates section on page 157.

Once a message is produced, SmartConsole will send a message to the computers you have specified, as shown below:

Figure 189 – Receiving a Net Send message

Click OK to close the message. 10.3.12 Send a Message to an Escalation List

You can define a list of recipients for your SMS and e-mail messages, the order in which they should receive messages and the time-out before passing to the next recipient, using the escalation list. These messages can be inquiry messages (requiring a reply) or informational messages.

When escalating, a message reply can either be a real reply to a message (e.g. R for Retry with iSeries messages), or it can be an acknowledgement of receipt of the message.

The message is sent to the first recipient on the list, and is escalated to the next recipient if a response is not received after the pre-determined time-out period. Escalation stops when a message has been replied to or receipt has been acknowledged.

Messages received at a mobile phone can be manually escalated: reply using the reply code and the command E, for ‘Escalate’. Notifier will automatically send the message according to the escalation rules of that list.

For more information on escalation lists, see the VISUAL Message Center Notifier Configuration Guide.

To configure an escalation list for an alarm: Step 1. In the Alarm Actions window click the Actions tab

Step 2. Select the Send a message to an escalation list check box

Step 3. Click the Escalation List tab that appears in the same window

Step 4. Click the button next to the escalation list field to select an existing escalation list. To create a new escalation list click the Add button from the right of the escalation list window.

Step 5. Indicate if this escalation list will use e-mail or mobile phone.

Step 6. Enter a recipient mail address or mobile phone number or click the Find button to select an address book.

Step 7. Enter the time-out interval in minutes. If you want to use the list as a broadcast list – i.e. to send an SMS to many people simultaneously – enter a time-out of 0.

Step 8. Finally indicate what escalation list options should apply to this list. Click OK to return to the escalation list window. Your escalation list will be displayed here.

You can change the name of your escalation list if you like.

Once you have selected your escalation list configure the message details.

Indicate whether to use the default message template or use a custom template for your SMS messages and mail subject lines. Also select whether to use the full message details, the short message details or a custom template for the mail message. For details regarding custom message templates see the Templates section on page 157. 10.3.13 Setting Action Sets

An action set can be used to group commonly used actions together. Action sets are externalized and are available for use by any alarm that you configure, so you can reuse them in many alarms. In that sense they are more powerful than setting actions individually in each alarm. We recommend that you group common actions into action sets as much as possible to save you time and make SmartConsole work better for you.

Example of setting action sets

If you usually want to have a pop-up window, run a DLL action, and send e-mail to various operators, it would be wise to configure that as an action set. That way, each time you configure an alarm that uses those actions, you just select that action set.

To create a new action set: Step 1. In the Alarm Actions window click the Action Sets tab. The action set configuration is also available from the Change menu in the menu bar of the SmartConsole.

Figure 190 – Configuring action sets

Step 2. Click the New button and select Action.

Step 3. Select the actions that you want to run together in your action set, following the instructions above for each type of alarm action, i.e. send e-mail, Windows event log, etc.

Step 4. Once you have finished you can give the action set a name that will allow you to identify it easily. You can also see a summary of the action set characteristics in the Description area. Click OK to return to the Alarm configuration window.

In your Alarm configuration window, you can select your action set from the drop-down menu, and add or delete it by clicking Add and Delete. You can add more than one action set to each alarm. The action sets will be run in order, starting with the first in the list. To change the order, first select an action set, then use the Up and Down buttons to move the action set to the desired position in the list.

Figure 191 – Adding action sets to alarm configuration

Remember that action set names can be used as variables in the ALEV Logical Expression eValuator for creating complex conditions and actions. For more information see Appendix B: ALEV Logical Expression eValuator on page 216, or see the Expression Evaluator document available in Windows Start menu. You can also see some examples on using variables in ALEV in Chapter 9 - Preprocessing on page 146.

Also remember that action sets can be set to run before and after every message retrieval cycle. This option is set up in the Precycle/Postcycle tab of SmartConsole’s Options.

For information about exporting or importing configured action sets see section 10.6.2 - Exporting or Importing Individual Alarms, Calendars, Actions Sets, Special Days, Address Books, or SMTP Server Lists on page 178. 10.3.14 Creating Dependencies

In the Dependencies tab of the Alarm configuration you can link several alarms to the alarm you are configuring. For example, if you receive a message stating that the backup job has started, you can configure an action for this first message to activate a new alarm, which will check if the backup completion message is received within a specific time.

You can also deactivate alarms here. For example if one alarm normally would lead to a second alarm being triggered, you can indicate that you do not want to trigger this second alarm in response to the alarm configured here.

To activate or deactivate an alarm drag it from the list of available alarms to the Activate or Deactivate lists. You can also select an alarm and use the arrow keys to transfer the alarm to the appropriate list.

10.3.15 Pre-Actions

These are actions that can be taken before an alarm action is triggered (not just before it is executed). Using pre-actions, you can test an incoming message to see if it will trigger the alarm, and then carry out any necessary preparatory actions before the alarm is triggered.

To configure a pre-action: Step 1. Click the Pre-Actions tab of the Alarm configuration window

Step 2. Click New from the toolbar.

Step 3. In the Advanced ALEV Filter Editor that appears, you can create the logical expression for the actions you want to carry out using the ALEV Logical Expression eValuator.

For more information on configuring logical expressions in ALEV see section 9.2.3 - Advanced ALEV Filter Editor on page 148 and additional ALEV documentation included in this installation.

Figure 192 – Advanced ALEV Filter Editor

Example of creating a pre-action

Imagine you want to send e-mail to a user who generates a message with Message ID CPC1194. After configuring the alarm filter for this message ID, you would configure a pre-action in the Alarm configuration window.

From the Pre-Actions tab of the Alarm configuration window, click New from the toolbar, then the Edit Global User Variables button and from the Options menu select New to create a new global variable, &USERVAR1, with no default value. For more information on global variables see the Global Variables section on page 22.

Then, in the Advanced ALEV Filter Editor, configure the logical condition so that this variable equals the &USERNAME in the message:

&USERVAR1:= &USERNAME

If you use this Username as an alias in your address book and associate the user’s e-mail address to it, you can then use it to define the recipient’s address when you configure the e-mail action. Simply right-click in the Send Mail To field, select User Defined - Global Variables and then &USERVAR1.

Next time a message with Message ID CPC1194 arrives in SmartConsole, the pre-action will enter the user’s e-mail address before the e-mail is sent.

10.3.16 Post-Actions

Post-Actions are similar to pre-actions, but you can set them to be executed after an alarm’s action has been executed. You will find a good example of using post-actions in section 12.3 - Tips for Using Pre- processing and User-Defined Variables on page 196.

Setting post-actions is the same process as for Pre-Actions discussed in the previous section.

Tip Actions can also be set to run before or after every message retrieval cycle. These options can be enabled in the Precycle/Postcycle tab of SmartConsole’s options.

10.3.17 Repetitions

The Repetitions tab includes more options for alarm configuration.

Figure 193 – Advanced alarm options

For example, you can specify different actions depending on a message’s frequency – you may want to disable an alarm if a message occurs very often, but is of little importance. Using the Data Dictionary, you can define which message variables to look for, define their frequency and what the action will be: disable all actions, disable the actions specifically related to these message variables, execute an action set, or reset the counter.

Click Reset Now to quickly and easily reset the counters.

Resilient Mode When the console is in Resilient mode, the Disable these actions for X minutes option is saved while the console is shut down or offline.

Example of using repetition alarm options

If you are receiving many incorrect user sign-on messages, it may be that somebody is trying to break into your system. You don’t want your administrator to receive alerts for every single invalid sign on attempt, but you do when the messages are produced frequently!

Selecting the Reset the repetition counter to zero check box, will make the alarm restart counting from zero every time it is triggered. This means that if our incorrect sign on messages keep appearing, SmartConsole will keep activating the alarm every time the frequency that we have defined is reached (in the image above, this is set to 2 times in 1 minute). If you do not select the Reset the repetition counter to zero check box, SmartConsole will trigger an alarm in response to every message received after the threshold has been reached in any given interval.

Additionally, if you have the Repetitions tab set up to identify when an action repeats 20 times in 30 minutes, and the console goes offline at minute 25 and comes back online at minute 30, the Resilient mode console will start counting again as soon as it comes back online and will always monitor the last 30 minutes.

For more information on Resilient mode see section 14.5.1 - What Happens in Resilient Mode? on page 210.

Note Even though you specify in the Repetitions tab that an action set should be run if the alarm is produced more than x times in y seconds, other actions configured for the same events will be executed anyway. For example, if you create an alarm that always sends you an e-mail, and you also specify that it will run an action set if the alarm is produced more than x times in y seconds, you will send the e-mail every time the alarm is produced, and you will execute the action set only once the alarm has been produced more than x times in y seconds.

Enable if the OS/400 Command Action Fails If you have configured an alarm to run an iSeries command in response to a system message or event, you should have a contingency plan in case the iSeries command fails. For example, your command action may attempt to vary on a failed communications line. If your action fails, you should either configure an alternative command to run, or you may want to send this information by e-mail to an operator for further action. In that case, create an action set and select it in the Execute the action set field.

Alternatively, if your iSeries command has failed, you may also want to disable the action in that system – so if you are receiving repeated messages or events, you are probably wasting time by trying to run that iSeries command repeatedly. In that case, select disable the actions for and indicate the number of minutes to disable the alarm for.

For more information see also section 10.3.8 - Execute an OS/400 Command Sequence on page 163. 10.4 Activating and De-Activating Alarms

Once you have configured your alarms, you can see them all listed in the Alarm dialog box. You can quickly activate or deactivate individual alarms using the check boxes. You can also edit their names to help you easily identify them. Furthermore, the Features window gives you a summary of the characteristics of your alarm.

Figure 194 – Working with configured alarms

All alarms that satisfy the filter condition are executed. 10.5 Alarm Log

To open the alarm log click the Alarm Log button in the toolbar of the SmartConsole. A new window opens displaying a log of all the alarms that have been run by SmartConsole during your current session.

Figure 195 – The alarm log displays all alarms executed during current session

Right-click an alarm action in the list, to see the alarm definition that produced the alarm, or to see the message that generated the alarm. Also, if the alarm is an iSeries command that has created a spool file, you can right-click to see the spool file.

Spool files retrieved by SmartConsole are stored on the PC in a directory named Spool Files in C:\Program Files\TANGO04\SmartConsole. The name of the spool file reflects the job from which the spool file output was retrieved, for example NIRVANATCPIP QPJOBLOG 1 CEPJOBD SIMON 184872.txt is a spool file containing the job log retrieved from the system NIRVANA, for the job CEPJOBD, user SIMON, job number 184872.

Spool files are stored as .TXT documents. If you want to delete those files from your PC you must do so manually. Any alarm command that fails will show a red icon to display the error, with full error information.

Figure 196 – alarm log options

To save the alarm log to an external plaintext file: Step 1. Click the File menu in the Alarm Log window and select Options

Step 2. Designate a destination file for the log.

Step 3. Select the Clear the file at Startup check box to replace the existing file each time the alarm log is recorded.

If you do not select this option the logs will be compiled consecutively until they reach the maximum number of messages allowed in the alarm log, then the log will be cleared and they will start to compile again. 10.6 Saving or Exporting your Alarm Configuration

Your alarm configuration is highly valuable, and it takes time and effort to configure. It is therefore advisable, that you keep a backup copy of your alarm configuration.

You may also want to share you alarm configuration with another user, working with a different console. 10.6.1 Exporting or Importing the Entire Configuration

To export the entire SmartConsole configuration, including your alarm configuration, from your console PC click the File menu from the menu bar in the SmartConsole and select Export Configuration File.

The exported file is saved with the extension .SCC. In order to import a configuration from an exported .SCC file, two options are available.

To import using double click:

Step 1. Double-click the exported configuration file in .SCC format. The Importer/Exporter display will appear.

Step 2. Choose the import option most suitable and click OK.

To import/export using contextual menu:

Step 1. Right-click the exported configuration file in .SCC format to bring up a contextual menu.

Step 2. From the contextual menu select and click the import option most suitable.

Important When BSM is active it is recommended that you avoid doing a full import of configuration files, which could potentially corrupt the BSM data in the database. To maintain BSM compatibility, we recommend that you import Business Views, Enterprise Views or alarms instead of doing a full import.

Note Any previous SmartConsole configuration will be removed.

10.6.2 Exporting or Importing Individual Alarms, Calendars, Actions Sets, Special Days, Address Books, or SMTP Server Lists

SmartConsole’s export and import function lets you export and import many of the variables that you configure within SmartConsole:

• Alarms

• Calendars

• Action sets

• Special days

• Address books

• SMTP server lists

From the dialog box for any of the functions listed above, choose the Options or File menu, and then choose Export to … or Import from … The example below shows the Alarm dialog box, but the same applies to any other function.

Figure 197 – Exporting or importing alarms

To export, first enter a name for the file that you are exporting to with the file extension .ALM. Once you have created the file, you are presented with a dialog box allowing you to select the individual alarms (or calendars, actions sets, etc.) that you would like to export.

Figure 198 – Select alarms to export

Use the arrow buttons to select or deselect alarms (or calendars, actions sets, etc.) from those you have configured. Click OK to save those alarms.

To import, simply specify the file location where you are importing from, and then select each individual alarm in the same way. Once you click OK, those alarms will be imported into your alarm configuration.

If you have any questions about working with the SmartConsole configuration, please do not hesitate to contact your Tango/04 Business Partner. 10.7 Getting the Most Out of Your Alarms

When configuring alarms, it is important to think carefully about the situations that could cause the alarm to be activated. As described in the previous chapter, alarms use filters. It is important to ensure that you alarm action will be activated only by the conditions that you are anticipating. So for example, if you set an alarm action for a specific message ID, you must be sure that the particular message ID will only be received because of the condition that you are anticipating. To make your alarms more specific, it is a good idea to use multiple selection criteria, such as message ID, user profile, message variables, and system.

It is also very important to ensure that no alarms cause conflicts. When configuring alarms, ask yourself if the alarm you are configuring is more or less generic to any previously configured alarms. Only one alarm should be activated for any given message or event.

Finally, we strongly recommend that you configure action sets and use them widely. By working with action sets you will save yourself time and make your SmartConsole more logical and adaptable to your environment. Action sets allow you to externalize all actions, and reuse them between different alarms. If you need to change the configuration of an action, and if it is defined in an action set, simply modify the action set and the change is then applied to all alarms that use that action.

Alarms can be configured to respond to any expected or unexpected events. You should spend time creating and maintaining your alarms. Our main objective with alarms is to:

• Give operators all the information that they need to solve problems as soon as they occur.

• Automate responses to certain events to free operators from those tasks.

• Integrate the iSeries and windows information that SmartConsole offers with other systems or application management frameworks that you have working in your company.

Chapter 11 11 Business Services Management (BSM)

Business Services Management (BSM) is an IT approach that looks at the whole business rather than a collection of inter-related technology components. Instead of focusing on the status of servers, printers, the network, or other technical components, the focus is on the health of online order processing, production lines, or the payroll application.

A traditional IT management system tells you that a production job has failed. A BSM system tells you that one of your offices has lost all network connections and that this problem has been caused by the failure of a router at the office in question. BSM also indicates the implications of the downtime and the impact on the business it will have compared to other events. By assigning Business Values based on the number of customers at a particular branch for example, prioritizing incident handling is simple.

Figure 199 – This image portrays the example explained above: The Barcelona - Paseo de Gracia branch has lost network connections, due to a problem with the branch router. The problem occurred at 9:00:05 AM and internet connections for this branch have been down for 4 minutes and 12 seconds so far. Meanwhile the Picadilly Circus branch in London has been experiencing similar problems for the last 1 minute and 25 seconds. By examining the Total Impact Cost column, an operator can instantly see that the network problems in London pose a greater threat to the business than those in Barcelona and can therefore prioritize further actions to ensure the Paris problem is resolved first.

The difference is not subtle. In the first case, the IT systems problems are isolated from the business context. In the second, IT systems are aligned to business processes, so it is easy to determine the business impact of a problem. This ultimately reduces downtime and improves service levels, since IT personnel can focus on the high-priority, business-relevant issues first.

In a broader definition of BSM, everything that impacts the service is also included. This may include real-time alerts on key business performance indicators (KPIs), such as lower transaction rates, number of users connected to a system, or plain business metrics such as sales in the last hour and factory quality deviations in a critical product line.

BSM systems improve communications across the corporation. Through modeling tools, it makes evident the relationship between revenue-generating services and the underlying IT infrastructure, so it helps upper management to understand and value the work of the IT department. It also helps IT operators to prioritize their work, by assessing the business impact of the failing components.

Example of the benefits of BSM

Suppose that your inventories for a critical manufacturing process are low. Your ERP system can tell your production manager about this. Now suppose that the software managing your warehouse slows down: IT hears about that one. But both situations are impacting the same business process. BSM brings those elements together in one management package, providing visibility of all aspects of a business process.

With BSM, the line manager knows the operating status of the business processes he or she has responsibility for, and the IT department knows the exact business impact of any problem and which problems need prioritizing.

11.1 Business Process Modeling

SmartConsole can define IT and business elements as Business Views and include them in the corresponding business services (Service Control Points). Grouping a set of elements in logical hierarchies is a matter of point and click, and an element can be reused as many times as needed (an element can be present in more than one Service Control Point) without any need to redefine it. Service status can be automatically inherited from the lower-level elements, or custom policies can be applied to reflect complex business situations.

Policies, SLAs, SLOs and filters can be added and maintained with ease, too, so rules can be changed rapidly to reflect changes in the real world.

For details regarding modeling please consult Chapter 6 - Business Network on page 59.

Figure 200 – Business service modeling capabilities enable the creation of custom Business Views for purposes such as demonstrating regulatory compliance. The figure shows a Sarbanes-Oxley compliance console implemented at an American manufacturing company’s iSeries. 11.2 Problem Root Cause

Management can use the model to see which business services are not running correctly and which element is causing the problem, using the Problem Root Cause pane. The Problem Root Cause pane displays all business elements that have real and potential impact on the business service and information regarding the duration of any real problems. Please consult see section 6.8.1 - Problem Root Causes Pane on page 98 for details. 11.3 Impact Analysis

The Real-Time Impact Analysis pane gives you a bottom up view of the business services. It shows what element is under performing and what business services are affected by it. Besides real impact it also shows potential impact allowing the operator to take action before the anomaly affects the business process. The operator can drill down to message detail level to help determine and solve the problem as soon as possible.

Impact analysis helps your IT department focus on problems that have a real effect on your core business services and helps them to take proactive action where it counts. For details see section 6.8 - Analysis Pane on page 97. 11.4 Service Control Point

A Service Control Point is a special type of folder that is used in Business Services Management (BSM) projects. Service Control Point is a BSM concept and represents any critical element of our business, such as an application, a service, a business process, and more.

Service Control Points are:

• Required for use with Business Values (see below)

• Used in BSM reports (see section 11.8 - BSM Reporting on page 188)

To create a Service Control Point you need to change the folder properties. Right-click the Basic Service Control Point or folder, select Type of Folder, and click Service Control Point. Notice that the folder icon changes to show a small yellow triangle in the bottom-right corner.

Important Service Control Points offer advanced functionality over the Basic Service Control Points. To define a Service Control Point you need an additional BSM license. For details regarding the differences between Service Control Points, Basic Service Control Points and folders see section 6.2 - What is a Folder? on page 62.

You can change the Service Control Point back to a folder or Basic Service Control Point at any time. 11.5 Business Values

Business Values enable you to put a numeric weight on the business impact of each service or application you monitor in SmartConsole. A Business Value can be any metric, such as money lost per minute of downtime, or number of customers affected, or simply a number that reflects the priority of the service. The important thing is to use a value that will help you determine the impact that a problem in a particular service has on the organization, compared to other services.

SmartConsole will show the event, the impact, and the numerical value, making it possible to instantly recognize the most important or urgent event that needs attention according to business needs, and therefore prioritize incident handling.

If an event impacts on more than one service, the SmartConsole will automatically sum up all the Business Values of the impacted services and display it on screen, labeled as Total Impact Cost. So if an element impacts on an application that has a value of 1000 and another that has a value of 500, it will show that the event has a business impact value of 1500.

Business Values ensure that no potentially serious event goes unnoticed and is dealt with before it has a disastrous effect on your business.

Figure 201 – Total Impact Cost. In this example, events in the Problem Root Causes pane have been ordered by Total Impact Cost so that the highest value appears at the top of the list. We can see that the router problem in Barcelona is not as serious as that in Paris which will need to be prioritized. This is because the Paris branch has been given a higher Business Value than Barcelona because it is a larger branch with more customers. 11.5.1 How to add a Business Value

Business values can only be added to Service Control Points. To add a Business Value, right-click on a Service Control Point and select Business Value... form the context menu. The Business Value window appears.

Figure 202 – Add a Business Value to a Service Control Point

Enter an integer value that reflects the Business Value for the Service Control Point in the Business Value field and click OK.

Tip If you change a Service Control Point to a Basic Service Control Point or normal folder you will not be able to use the Business Value; however if you then change the folder back to a Service Control Point, SmartConsole will remember the Business Value you previously assigned to it. Note also that you can change the Business Value at any time.

11.5.2 Using Business Values

Business Values appear in both the Problem Root Causes pane and the Real-Time Impact Analysis pane; however they are used differently by each pane:

• In the Problem Root Causes pane they appear in the Total Impact Value column, which displays the combined Business Values that have been assigned to each of the Service Control Points that the event impacts on.

• In the Real-Time Impact Analysis pane they appear in the Business Value column, which displays only the singular Business Value assigned to each of the Service Control Points being impacted on.

Figure 203 – Problem Root Causes pane

In Figure 203 above, we can see that when we select a Service Control Point (03. Business) in the Business Network pane, we are presented with the Problem Root Causes pane which displays the Business Views and their Business Values that are impacting on this Service Control Point:

• 03. Switch_New York: 700

• 01. Router_Picadilly Circus: 550

• 01. Router_Paseo de Gracia: 500

The three Business Views have Total Impact Costs ranging from 500 to 700 which means we can see instantly that the firewall issue in Times Square is the priority problem affecting the business.

Figure 204 – Real-Time Impact Analysis pane - 03. Switch_New York

In Figure 204, we can see that when we select a Business View (03. Switch_New York) in the Business Network pane, we are presented with the Real-Time Impact Analysis pane which displays the Service Control Points that are impacted on by the Business View. The Business Values of the Service Control Points affected are:

• 02. USA: 300

• 03. Business: 250

• 01. East Coast: 150

The combined Business Values equal 700, which is the Total Impact Value of the 03. Switch_New York Business View, as shown in Figure 203. The Total Impact Cost is also displayed in the header of the Real-Time Impact Analysis pane.

Figure 205 – Real-Time Impact Analysis pane - 01. Router_Picadilly Circus

If we examine the Real-Time Impact Analysis pane for a different Business View (01. Router_Picadilly Circus) as shown in Figure 205 above, we can see why the problem in New York is given a higher Total Impact Cost: Issues in the USA (300) are given a higher Business Value compared to Europe (200) reflecting the increased value to the business of the market in the USA; while branches in the East Coast of USA also have a higher Business Value than those in the UK suggesting larger branches with more customers and further increasing the Business Value.

You can use the Total Impact Value to see which Business Views have the highest impact on the business at any moment. Business Views can be ordered in Problem Root Causes pane by the Total Impact Value field, promoting the most serious events to the top of the list, by simply clicking on the Total Impact Value column header. The values can be arranged in the list ascending or descending, click the column again to toggle between the two options.

Note The Business Value only appears in the Total Impact Value column when the Impact Type of an event is Real.

Figure 206 – Only when the Impact Type is Real is a Business Value displayed

Tip It is recommended that you reflect a higher impact with a higher number. If you are not able to determine a precise Business Value of a service failure, use 1000 for the most critical applications, 100 for the least critical, and intermediate values for the moderately critical applications.

11.5.3 Using Formulas for Business Value

You can further control how Business Values can work for you, using a simple or complex formula to alter the Business Value by using pre-action scripts.

For instance, you can make the Business Value increase exponentially for the longest downtime the service experiences during the day or current month, or to reflect a penalty you may incur if a service agreement is violated. Use the ALEV function SET_SCP_VALUE(‘Service Control Point name’, value) to programmatically modify the Business Value.

Tip The Total Impact Value of an event can also be shown in messages and exported to Help Desk applications. This value should be calculated with an ALEV function, and will require a preprocess to set the value to an ALEV variable.

11.6 Cause/Effect Criticalness Management

Cause and Effect provides advanced criticalness management of folders in the SmartConsole and is only available with a BSM License.

Criticalness management is available from the folder menu. Right-click the folder, select Criticalness Management and click Criticalness Propagation Configuration. Here you will find the Cause/Effect option for determining the criticalness of the folder.

For details of other Criticalness management options see section 6.3 - Folder Criticalness Management on page 63.

Cause and Effect uses the same method to set element criticalness as used by the Most Critical Child Component option. However, this option allows you to define a child component (for example a synthetic transaction) as an effect. The component marked as effect will only appear as the cause of a resulting state, if there is no other child component causing the state to change.

Example of using Cause and Effect

For example, say an insurance company makes heavy use of its b2b application for writing policies for its nationwide network of agents. This company may define its Service Control Point to contain a number of Business Views representing the underlying components and a separate folder for the transaction. The transaction folder is defined as effect.

Now assume that the Service Control Point reaches the critical state and the company investigates the problem. There are three scenarios:

• One of the underlying components is showing problems but the transaction is able to run. Only the component with a problem appears in the Root Causes pane. The operator investigates and corrects the problem with the underlying component.

• The transaction is not able to run, but the underlying components are functioning as required. The root causes pane shows only the transaction as a cause. The operator investigates and corrects the problem with the transaction.

• Both an underlying element and the transaction are showing a problem. Because the transaction was defined as effect, only the underlying elements will appear in the Root Cause pane. The operator investigates and corrects the problem with the underlying element.

In the event that there was also a problem with the transaction, the transaction will appear in the Root Causes pane once the problem with the underlying component has been corrected.

When the operator opens the Service Control Point he will notice that there is a problem with both child elements and may decide to investigate both routes at the same time.

11.7 BSM Engine

BSM Engine requires a separate license (for details see section 11.9 - BSM License on page 191). Once you activate BSM Engine all data relevant to BSM is stored in the general configuration database. This information includes:

• any status changes to the Business View (given that its substate is Availability)

• any status changes to the Service Control Points

• Impact of the Business View on the Service Control Points (given that its substate is Availability)

This information is used to create real-time and historical reports regarding your business services.

For details on how to enable BSM functionality and the configuration of the BSM database see the BSM Tab section on page 26. 11.8 BSM Reporting

VISUAL Message Center Reports uses information stored in the BSM Database for creating BSM Reports. BSM Reports offer you information regarding the availability of your applications and components over time. In addition you can find out for each Service Control Point what components are causing problems and reveal the underlying component errors.

Special parameters in the BSM reports allow you to select which components or Service Control Points to include in the report. You can define your SLAs in the report and use the reports to monitor

compliance with your SLAs. In addition, use calendars and predefined time slots, such as last hour, last 30 minutes, last month, etc. to refine your reports.

BSM Reports can be scheduled to run automatically and used to feed Web pages so that you can keep up to date with the state of your business processes at all times, wherever you are.

A description of a number of BSM Report follows here. For details regarding how to use BSM Reports, consult the VISUAL Message Center Reports User Guide, included in your installation. 11.8.1 Service Control Point Listing

The Service Control Point listing report provides you with a list of selected Service Control Points or simply all Service Control Points showing the availability of each Service Control Point for the period selected and the most problematic component

Fields available in this report are listed in the following table:

Field Description

Service Control Name of the Service Control Point Point

Amount of time that the Service Control Point was available % Avail as a percentage of the time period of the report

# Failures Total number of times the Service Control Point failed

Total amount of time the Service Control Point was not avail- Unavailable Time able

Longest period of time that a Service Control Point was Longest Failure unavailable

MTBF Mean time between failures

MTTR Mean time to repair

Component causing the Service Control Point to fail for the Worst Component longest time.

Total amount of time the worst component caused the Service Impact Time Control Point to fail.

Impact time of the worst component as a percentage of the % Impact Unavailable Time of the Service Control Point.

Most Common Message text of the Worst Component Reason

11.8.2 Service Control Point Overview

The Service Control Point Overview report shows the most important indicators of a Service Control Point over time. Availability for each time slot is displayed in graphs (bar charts) and the report includes a ranking of the 10 worst components. The user can choose to rank the components according to highest:

• Total Impact Time

• Number of failures

• MTTR

• MTBF

• % Impact

These fields are discussed in the previous section. 11.8.3 Service Control Point Detail

The Service Control Point detail report first shows summary information of the Service Control Point. The Service Control Point summary is followed by the individual Service Control Point failures that took place during the time period specified in the report.

Each Service Control Point failure record shows data regarding impact on Service Control Point (i.e. start and end time of the Service Control Point failure, total duration of the failure in time and as a percentage of total failure time), before listing the components that caused the failure and their details (i.e. component name, time the component failed, duration of the failure, cause of the failure). Note that a failure maybe caused by more than one component, therefore you may find details of several components for each Service Control Point failure.

Figure 207 – BSM report 11.9 BSM License

To use the advanced BSM features in SmartConsole you need a separate BSM Engine license key. Advanced BSM features offer:

• A BSM database which stores status changes to Business Views and Service Control Points for reporting purposes.

• The Criticalness Evaluation option Cause/Effect.

• The option to create Service Control Points

• The option to add Business Values to Service Control Points

The basic BSM Engine license allows you to define a limited number of Service Control Points. Licenses are available for additional Service Control Points.

If you try to create more Service Control Points than your License allows, the following message will appear.

Figure 208 – BSM Key Management

You may continue to create the Service Control Point, however it will not be considered by the BSM Engine. It will be converted to a Basic Service Control Point.

You can decide at anytime to upgrade your license to allow you more Service Control Points. Alternatively you can swap an existing Service Control Point for a Basic Service Control point (for details see section 6.2.2 - Basic Service Control Point on page 63).

Important When you convert a Service Control Point to a Basic Service Control Point the BSM Engine will no longer store changes for this folder in the BSM database and this information will no longer be available for reporting purposes.

Warning If the key is incorrect or has expired, all Service Control Points will revert to Basic Control points. Also, if you had defined Criticalness Evaluation option Cause/Effect for the Service Control Point, the Basic Service Control Point will now be evaluated using the Most Critical option.

11.9.1 Importing & Exporting with BSM Active

When BSM is active it is recommended that you avoid doing a full import of configuration files, which could potentially corrupt the BSM data in the database.

To maintain BSM compatibility, we recommend that you import Business Views, Enterprise Views or alarms instead of doing a full import.

Chapter 12 12 User-Defined Variables

SmartConsole lets you define your own variables and use them in ALEV expressions to carry out a broad range of functions. You can either create variables that apply to specific messages (per message), or variables that apply to all messages (global). Through ALEV, user-defined variables can be used to:

• Change the values of variables in incoming messages to adapt them to the console configuration (e.g. name, user, severity, etc.)

• Group messages before they arrive at the console

• Add information to messages (e.g. text)

• Rearrange message information

• Correlate events (e.g. by creating an event counter on incoming messages)

Through user-defined variables, you can make your Business Views, alarms, Actions, and Message Grouping more generic, ensuring that network-wide changes are easier to implement.

For example, imagine you have an operator with user name JOHN who has a certain number of authorities. His profile will appear as included or excluded in many filters and Business Views throughout your console configuration.

Now imagine JOHN leaves and is replaced by an operator with user name LAURA. You would have to go through all the filters and alarms to change the user name — unless you use per message variables.

First you would set a preprocess filter to detect all incoming messages with REALUSER name JOHN. Then you would create a logical expression to change this into "TEMP":

&REALUSER:= "TEMP"

You would then use TEMP rather than JOHN in all your filter, alarm, and Business View configurations at the console. When JOHN leaves and LAURA arrives, you can make the update quickly and simply by modifying the filter for this preprocess to select messages with REALUSER name LAURA.

User-defined variables are also useful for creating alarms. For more information see Chapter 10 - Alarms on page 150.

To open the User Defined - Per Message Variables window: Step 1. From the SmartConsole menu bar, click Change and select User Message Variables,

or From the Advanced ALEV Filter window click the icon.

Figure 209 – User Defined Per Message Variables window

Step 2. Click Options, select New, and give a value and description to your new variable.

Figure 210 – Configuring a user-defined variable

Step 3. Once you click OK, you will be able to name the new variable.

Figure 211 – Naming a user-defined variable

This variable will then be available from the Advanced ALEV Filter Editor in the user defined – per message variable button.

Note The Variable, Default Value and Description fields are fields that the user configures, whereas the Current Value field is provided by your system. Current Value is not automatically refreshed the user must open the variable to refresh the Current Value data.

12.2 Creating and Defining Global Variables

To open the User Defined - Global Variables window: Step 1. From the SmartConsole menu bar, click Change and select Global Variables, or

From the Advanced ALEV Filter window click the icon.

Figure 212 – User Defined - Global Variables window

Step 2. Click Options, select New

Step 3. Assign a value and description to your new variable.

Figure 213 – Configuring a global user-defined variable

For an example on creating and using global variables see section 12.3.2 - Example 2: Clean Up Windows Server using Global Variables and Post Actions on page 197.

Once you click OK, you will be able to name the new variable.

This variable will then appear in the User Defined - Global Variables button available from the Advanced ALEV Filter Editor.

12.2.1 Persistent Variables

Persistent variables are maintained when the SmartConsole is shut down and are recovered when the console is restarted. Only global variables can be set as persistent. Once set as persistent, these variables will always maintain that status regardless of whether Resilient or Non-Resilient is selected in the Console Mode tab in the Options menu.

To set a variable as persistent: Step 1. Click Change from the SmartConsole menu bar and select Global Variables. The User Defined – Global Variables window appears.

Step 2. Double-click the variable you want to set as persistent.

Figure 214 – Configuring a persistent global user-defined variable

Step 3. Select Persistent at the bottom of the window and then click OK. The icon next to the variable changes to indicate it is now persistent.

Figure 215 – Persistent variables indicated by a different icon 12.3 Tips for Using Pre-processing and User-Defined Variables

Pre-processing and user-defined variables have enormous possibilities, and can as a result seem a little daunting at first. Below are two examples to give you an idea of the possibilities and to take you through the configuration process. 12.3.1 Example 1: Using Per Message Variables

This example shows you how pre-processing can be used to alter message variables and extrapolate extra, useful information from messages.

Imagine you have configured two different types of SNMP Traps in your TCP/IP Agent: Generic Traps (to warn you of device problems) and Enterprise Traps (to warn you of application problems). Both arrive

with Message ID 256 and Message Category SNMP Trap. The only place where you can distinguish between the two different traps in is &VAR03, where the information arrives as either:

• SNMP Generic Trap received

• SNMP Enterprise Trap received

Using preprocessing and ALEV, you can extrapolate this information and change the Message Category so that you know whether the message is a Generic or Enterprise Trap, and arrange them accordingly in your Business Views.

To do this, you would first configure the pre-processing filters to detect Windows messages with Message ID 256. Then you would create a logical expression to change the Message Category so that it states whether the message is a Generic Trap or an Enterprise Trap, using the following expression:

&VAR03 MATCH “SNMP%&MSGCATEGORY% Trap received”

Using this expression changes the Message Category of the message before it arrives at the console, so you can either filter these messages into different Business Views, or organize them by Category within one Business View.

Note Preprocessing only changes messages on the client-side: it never makes any changes on the server-side or to server lists.

Bear in mind that if you change the message variables by which you filter on the server side, you may accidentally exclude these messages from your Business Views.

12.3.2 Example 2: Clean Up Windows Server using Global Variables and Post Actions

Imagine you want to know if the Windows message database on system MERCURY becomes saturated. You can set a limit of 10,000 messages from Console Startup, after which you automatically trigger a DLL action to clean up the server. To do this, you can use a combination of global variables and post actions. For more information on post actions see Chapter 10 - Alarms on page 150.

First of all, create a global variable WINMESSAGES with a default value of 0. Then set an alarm filter to detect each time a Windows message arrives from MERCURY, with a post action that increases the variable WINMESSAGES by 1 every time the alarm is triggered. In this case the expression would be:

&WINMESSAGES:= &WINMESSAGES+1

Next create a second alarm with a custom logical condition that checks the value of WINMESSAGES and runs a DLL function to cleanup the server if it exceeds 10,000:

&WINMESSAGES > 10000

Finally, create a post action for this alarm to reset the WINMESSAGES variable to zero once the server has been cleaned:

&WINMESSAGES:= 0

This way you can automatically ensure that your Windows message database never gets saturated. 12.4 User Defined Functions

An advanced option available to programmers is to define user functions with ALEV. You can see an example, built in C, in the following directory:

C:\Program Files\TANGO04\SmartConsole\Alev user function example

You can create as many functions as you wish using the following format:

// This is an example function that accepts one string parameter

// If the parameter is equal to 'Value' the function returns "Good Parameter"

// Otherwise it returns "Bad Parameter"

long int OneFunction( TArgumentList *TheArguments, void **TheResult)

{if (TheArguments!= NULL)

{if (TheArguments->fArgCount == 1)

{if (TheArguments->fFirst!= NULL)

{if (TheArguments->fFirst->Value->Kind == typeString)

{gValue.Kind = typeString;

if (gValue.Data.AsString!= NULL)

{free(gValue.Data.AsString);

gValue.Data.AsString = NULL;}

if (strcmp(TheArguments->fFirst->Value->Data.AsString, "Value") = 0)

{gValue.Data.AsString = (char *) malloc(strlen("Good Parameter")+1);

strcpy(gValue.Data.AsString, "Good Parameter");}

else

{gValue.Data.AsString = (char *) malloc(strlen("Bad Parameter")+1);

strcpy(gValue.Data.AsString, "Bad Parameter");}

*TheResult = &gValue;

return (0);}

else

{return (-4);}}

else

{return (-3);}}

else

{return (-2);}}

else

{return (-1);}}

In order to load all of the functions, you will then need to create a function with the name:

int WINAPI FUNCSTARTUP ()

{HMODULE lModule;

TDefineFunctionC lDefineFunctionC;

//Here we do the functions load.

gValue.Data.AsString = NULL;

lModule =LoadLibrary ("ALEV.dll");

if (lModule!= 0)

{lDefineFunctionC = (TDefineFunctionC) GetProcAddress(lModule,"DefineFunctionC");

if (lDefineFunctionC!= NULL)

{lDefineFunctionC ("FUNCTION OneFunction (S STRING): STRING", &OneFunction);}

return (0);

// FreeLibrary (lModule);}

else

{return (-1);}}

Once you have defined these functions, you need to declare them so that they can be used by the application in a file named Functions.ini with the following format:

[General]

dll0 = C:\Program Files\Alev Functions dll\AlevFunc\Debug\AlevFunc.dll

dll1 = C:\Program Files\Alev Functions dll\AlevFunc\Debug\OtherFunctions.dll

This states the location of your functions to be used in the application.

Chapter 13 13 Getting the Most Out of SmartConsole

It is worth investing time in configuring SmartConsole to adapt it to your environment. You should aim to automate as many processes as possible using the auto-reply functions (running commands, replying to messages).

You should also aim to configure SmartConsole to collect as much problem diagnosis information as possible when unexpected errors occur, and to ensure that the right people are alerted.

You should aim to take advantage of the two-way messaging functionality provided by Notifier to allow operators to control your systems and solve problems wherever they are in the world.

Finally, you should aim to configure SmartConsole to provide operators with as much as additional information required to solve problems when they occur.

In summary, it is very important to make a keen analysis of the current environment and needs, in order to maximize the benefits of SmartConsole. 13.1 Using SmartConsole with iSeries Support Agent

SmartConsole was designed to integrate with other Tango/04 operational problem-solving products.

VISUAL Message Center iSeries Support Agent is a unique and integrated tool for diagnosing and solving problems on your iSeries. It shows you a list of all active jobs on your system, and allows you to drill down to inspect internal information for any chosen job. For interactive jobs it shows you any user’s screen, and it gives you access to any job’s library list, LDA, objects in QTEMP, or the call stack and offers more general job and system information. You can even drill down to browse the source code, see and edit program variables, and graphically identify the statement in execution.

Figure 216 – Capturing another job with iSeries Support Agent

VISUAL Message Center iSeries Support Agent can be used in this way to diagnose the cause of many software or operational problems. It is also invaluable for giving end user support.

However, it also allows you to solve problems using the command prompt and execution function. This allows you to run any command on any active job, even if it is waiting for a message reply.

There are many uses of this function, for example:

• Change a job’s run priority, timeslice, and other run time details, with CHGJOB

• Add a library to a job’s library list

• Edit the LDA, contents of QTEMP

• Sign off absent users when doing upgrades, changes, PTFs

• You can even take control of end-user’s keyboards with the remote control function when giving technical support or training.

In many cases, serious application problems are quickly diagnosed and solved with iSeries Support Agent, ensuring high quality end-user service and maximum application availability.

If you receive a message in SmartConsole and you want to inspect the job that produced the message, you can use iSeries Support Agent just by selecting the message and clicking Capture with iSeries Support Agent. All of iSeries Support Agent’s functions will be available to you directly from the SmartConsole.

The VISUAL Message Center Performance Agent module allows real time graphical performance monitoring. Multiple systems can be monitored simultaneously from the same console, and performance data can be cross-graphed. The system view can be manually refreshed at any time. The display offers hundreds of performance parameters, and can be easily customized – drilling down to graphs offers greater detail, and multiple windows can be opened and tiled. Any graph can be saved or printed at any time.

Figure 217 – VISUAL Message Center Performance Agent – real time iSeries performance monitoring 13.2.2 Detailed Performance Information

By moving the cursor over on-screen performance info, more detailed information can be seen. For example, the CPU user list can be further analyzed by moving the cursor over each job, or memory pool info such as number of active jobs, & CPU% active jobs can be revealed. 13.2.3 Response Times

Performance Agent offers very advanced response time information, grouping interactions by response time intervals, for example, revealing that 80% of interactions had a response of less than one second.

Figure 218 – VISUAL Message Center Performance Agent displays response time information 13.2.4 Customizable Alerts

Hundreds of performance parameters can be used for real time alerts, similar to those used with messages in SmartConsole. Alerts can be sent to operators when CPU is persistently high, or response times are low, or page faulting is too frequent and so on. Automatic responses to key conditions can also be programmed to increase automation.

The two products are integrated so SmartConsole and Performance Agent can be used together to monitor all aspects of iSeries system operation and performance. 13.3 Using SmartConsole for Problem Diagnosis

One of the key benefits that SmartConsole can offer is the ability to capture a “snapshot” of an application or system at the time that an important message is produced. That information can be stored or distributed and used to diagnose the cause of problems, at the time they occurred, reducing troubleshooting time and allowing tough problems to be solved faster.

This can be done through the use of the iSeries command alarm, and the retrieval of spool files. Following are some examples: 13.3.1 Serious System Conditions

When diagnosing system events the output from commands such as WRKACTJOB or WRKSYSSTS are vital for quickly diagnosing the cause and extent of the problem.

For example, a CPF0907 message indicates that a serious storage condition may exist. Without a Work with System Status command WRKSYSSTS, an operator cannot determine the nature of the problem.

VISUAL Message Center can greatly accelerate this process. Just configure an alarm that monitors for iSeries message ID CPF0907. For your action you should configure VISUAL Message Center to run a WRKSYSSTS command on the system that produced the error *SAME, as shown in the figure below.

Figure 219 – A WRKSYSSTS command can be used to collect diagnostic information

The spool file output is sent by e-mail to all those recipients indicated in the Send Script Results… field.

Without SmartConsole, operators would only find out that the system was in critical condition by manually scanning the message queues, and would then have to get to an emulation screen (even if they are traveling) and enter the necessary commands to find out the system status: but it may even be too late by then.

Now with SmartConsole, an operator will simply receive an e-mail seconds after the message is produced, wherever they are, with the required complete current system information attached to the e- mail. They are ready to solve the problem immediately. 13.3.2 Job Details

When error messages occur, critical application jobs, programmers, and developers need to have access to specific environment information to help them to diagnose the cause of the problem and solve it. Time spent recreating problems in testing are costly and often unnecessary.

With SmartConsole, you can configure alarms to run and distribute the output from Display Job or similar commands to facilitate problem diagnosis. The spool file produced by the message is stored with the PC console and can be distributed by e-mail so you get a “snapshot” of the job or the system at the moment the error is produced.

There are many more examples of ways that you can use SmartConsole to help you to diagnose problem, and of course, you can use it together with iSeries Support Agent to offer you even more detailed job information.

One of the prime benefits offered by SmartConsole is the ability to operate your operations, performing tedious manual tasks automatically and allowing you and your operations team to dedicate energies to more productive tasks.

When working with SmartConsole you should be conscious to put as much of your intelligence and knowledge of your operating environment into the product. There are so many tasks that you may do automatically which can be automated – so you should constantly think about what can be automated and how best to do it.

You will get a constant return from automating your operations – in time savings, productivity improvements, service level improvements, and more. We will help you with any training or consultancy work that you require to help you configure SmartConsole to work for you. 13.4.1 Automated Operations Examples

There are two main automation areas – replying to messages automatically, and configuring commands to run in response to messages. As you start working with SmartConsole you will soon discover which messages are most common, and which areas can best be automated.

There are many obvious tasks that can be automated – many people will configure an automatic message reply to a file full message CPA5305 to increment file size by 1. But you could also configure SmartConsole to alert you if that message is produced very frequently – more than x times per minute – using advanced options in the Alarms dialog box.

Now that you have seen an example of replying to a message as a form of automation, you will see an example of using a command to automate operations.

You may receive an error message telling you that a certain critical process has ended with an error. As the error message will contain variables, you can program a command to run as an action, which will restart the process. For examples on how to configure such commands see section 10.3.8 - Execute an OS/400 Command Sequence on page 163.

Some of our customers use this feature to automatically restart a data-replication process if it ends in error. Rather than having to wait for operator intervention for this critical action to be performed, it is now done automatically as soon as the message is received. The command is customized according to the replication process in error: the details of the process are included in the message and are used as an input in the command. This way, any kind of processes can be successfully monitored and automatically fixed when errors arise. 13.4.2 Automation Tips

We recommend that you study your History message grid once every week or two. Look to see which messages are most common. Which messages can be replied to automatically? Which messages could have been dealt with by automatically running a command?

If you dedicate your efforts to automating the most common messages you’ll get the best return on your investment, and you’ll free yourself from tedious tasks that can be automated by SmartConsole. 13.5 Using VISUAL Message Center for Security Alerts

Whatever the size of your IT department, security should be an important issue for you. SmartConsole can be used to send you an alert every time a user attempts too many invalid sign-on attempts. For example, a CPF1397 message means that a device has been varied off for too many invalid sign-on

attempts. If that is a user who has a problem, they need immediate help. If it is a hacker, you need to be able to monitor your system immediately for any abnormal user behavior. You can set an alarm to alert you by e-mail or pager every time this occurs. 13.6 Integrate SMS and E-mail Message Support into Your System Applications

Notifier allows you to send and reply to messages via SMS (the industry standard mobile text messaging service) or e-mail. This function is invaluable for allowing operators to control your system when they are out of the office.

Furthermore, the architecture of SmartConsole lets you take advantage of this technology to introduce SMS and e-mail support into your own iSeries applications.

Applications can be modified to send messages informing operators when critical processes have been finalized correctly (or not). Also, Notifier can be used to give operators control over the behavior of an application. For example:

• When a process is completed, the application can ask an operator via SMS or e-mail whether a save should be performed or not;

• Notify delivery personnel of changes in delivery routes to their mobile phone;

• Send sales personnel updated information of product pricing and availability.

Figure 220 – Sending and replying to messages via SMS or e-mail

As SmartConsole monitors any message queue on your iSeries, you can create a specific message queue for managing SMS or e-mail messages. Then you could adapt your RPG or Cobol programs to send messages to that message queue so that SmartConsole sends them to an operator via SMS. The message can be replied to at the message queue via SmartConsole, so this can also be used by your applications.

Chapter 14 14 SmartConsole High Availability Options

SmartConsole is used to monitor and manage applications and systems that are critical to your enterprise. It is important to ensure that SmartConsole is set up in a way that guarantees that all- important messages are received and managed correctly. This chapter contains information that you can use to ensure that SmartConsole is always working – protecting it against network failures, operating system crashes, or other unexpected events. 14.1 Installing SmartConsole as a Service in Windows NT / 2000

You can install SmartConsole to run as a service on Windows NT/2000. That means that it will run in the background without the graphical user interface. It will perform all of its functions as normal, including running pop-up window alarms.

Obviously you must have SmartConsole correctly configured for it to run in the background without any operator intervention.

Please refer to the VISUAL Message Center SmartConsole Installation Guide for information on how to install SmartConsole in service mode. 14.1.1 Minimum Knowledge of Services

Services start as soon as your PC or server is started without the need to log onto your system. They can be started and stopped from the Service Administrator in Windows NT/2000.

Service needs a user profile to start with; by default it is LOCALSYSTEM, which is the system user and is the only user who can see the graphical interface of the service application. 14.1.2 VISUAL Message Center as a Service

Bear in mind that it is the user who saves user names and passwords used in the system configuration of NiceLink, so if the user ADMINISTRATOR saves any passwords, they cannot be seen by user STEVE. This is very important as the service will start by default using the user LOCALSYSTEM, so all users and passwords defined by other users will not be seen by LOCALSYSTEM.

When SmartConsole as a service is started by LOCALSYSTEM, you will have to re-enter any user names and passwords.

So that the service works automatically with the user LOCALSYSTEM, configure all users and passwords starting SmartConsole as a service with the graphical interface. If you want to start SmartConsole as a

service without the graphical interface, you should leave some iSeries pre-selected to start automatically.

Note If no user or password is configured, SmartConsole will not connect to any system, and will not alert you to that fact. You must configure the connection and user profiles previously using the graphical interface.

14.2 Smart Reconnect

What happens when your connection to the monitored systems goes down? We all know that telecom connections are prone to failure - Smart Reconnect is the answer. Click Options from the menu bar, select Options and click the Server tab. Here, you can enable Smart Reconnect and specify the time to reconnect. SmartConsole will attempt to reconnect as soon as there is a break in communications and you will never lose vital error information. This is also true for IPLs – SmartConsole will simply reconnect after any IPL.

Figure 221 – Smart Reconnect configuration 14.3 Connection Time-out

If your connection to the monitored server from your NT server console fails for any reason, you need to be alerted – it could create a communication problem with for example the iSeries, or the NT, or a network failure. Click Options from the menu bar, select Options, and select the Server tab.

SmartConsole will send you an alert whenever the connection is interrupted so you can take action. Of course, you can configure more than one SMTP server in case the problems are related to your network.

For more information see the SMTP server list contains the SMTP Server configuration required for sending e-mail messages from the SmartConsole. For more information about sending messages via email see the SMTP Server List section on page 126. section on page 30.

Tip You can also check the connection of the console with iSeries or Windows servers by configuring alarms for the console messages.

14.4 Monitor Checking

SmartConsole can be configured to check the activity of the monitor jobs on your iSeries. Click Options from the menu bar, select Options and click the Monitors tab.

Figure 222 – Configure alerts in case the message monitors fail

You can configure an alarm when any of the monitors are inactive. Just select the check boxes to enable the function, and click the alarm icon to configure your alarm action – such as an e-mail alert, or even run an iSeries command: i.e. B_DETECTOR/STRBDMON. 14.5 Console Mode

SmartConsole can give you another level of security in case Windows or the console is rebooted, if there is a power outage, or if any situation occurs where the console loses contact with the currently connected systems. There are two possible modes to run SmartConsole in:

• Resilient Mode: The safer of the two modes. When you restart the console, it will attempt to retrieve all events from all connected systems that occurred since it was shut down. Business View states, Repetition Counters, any enabled or disabled alarms, and more will be set to values they had at console shutdown when the SmartConsole is back online.

• Non-resilient Mode: The faster of the two modes. When you restart the console, it starts from scratch and processes only new events. This mode is recommended when console has been down for a long time.

Figure 223 – Console mode

The default mode is Non-resilient. To change the current mode, click Options from the menu bar, select Options and click the Console Mode tab, choose the desired mode, and then click OK. 14.5.1 What Happens in Resilient Mode?

The two main areas that are saved in Resilient Mode are Business Views and alarms.

Each time you make a change to a Business View it is automatically saved and displayed when you restart the console.

Example of how alarms interact with Resilient Mode

In the Advanced tab of the Alarm Filter window, the No event passes this filter in the specified calendar option is selected. The calendar’s times are from 3am to 5am and 6am to 8am, Monday to Friday. If the console goes offline at 4am and the event occurs at 5:30am (outside the selected time range), the console will only check the previous time range (3 to 5 AM). If the event occurs at 7am, the console will only check the second time range because it has already started.

14.6 Options for Sending Alerts

SmartConsole offers various alarm actions for sending critical alerts to operators. In a high-availability environment, it is advisable to have more than one option programmed. For example, if an e-mail server fails, you cannot send an alert by e-mail. Therefore, it is advisable to use SMS messaging for sending those critical messages. However, in case SMS coverage is affected, e-mail can be used as a backup for sending that alert.

Companies should examine combinations of alert procedures and ensure that a contingency plan is always available – it could even be as primitive as an audio file that will alert nearby operators that the system is not functioning as expected with some visual information providing instructions on who to contact, and how to contact them.

A High Availability System that supports Microsoft Clustering has been added to VISUAL Message Center to guarantee rock-solid availability. Setting up the new High Availability feature is simple, as it uses native Windows Clustering Technologies. Please see the Clustering VISUAL Message Center SmartConsole and ThinkServer with Microsoft Cluster Services (MSCS) guide for further details.

Chapter 15 15 SmartConsole Web Client

SmartConsole Web Client gives you access to information from Business Views and Events from anywhere you have an Internet connection. It is continuously updated allowing you to monitor crucial information in real-time across the globe.

From the Web you can see Business Views, Folders and Service Control Points reflect the current status at all times and you can view related Events to identify problems as they occur.

In the Web Client you can create users and roles to ensure operators have the information they need to do their jobs while restricting access to sensitive information.

SmartConsole Web Client is easy to install and configure enabling you to extend your monitoring capabilities and manage crucial systems worldwide.

For more information please consult the VISUAL Message Center SmartConsole Web Client Installation Guide and User Guide included in the product installation.

Figure 224 – VISUAL Message Center SmartConsole Web Client

Appendix A Appendix A: Automating the Export of SmartConsole Configuration Files

It is highly recommended to make periodic backups of SmartConsole configuration files. As has been covered earlier in this manual this can be done from within SmartConsole using the export function. Should the configuration files be needed later they can easily be imported again. However, to make periodic backups easy it is best to automate the task. This can be done easily using the Scheduled Tasks option in Windows along with the SmartConsoleImporterExporter.exe tool included with the SmartConsole installation. A.1 Scheduling Backups

Before setting up the scheduled task a batch file containing the necessary command needs to be created.

Step 1. Create a new plain text document (in Notepad for example).

Step 2. Enter the following command to the text document “C:\Program Files\SmartConsole\Tango04\SmartConsoleImporterExporter.exe” -E -F “C:\Backups\backup.scc”

Figure 225 – Add the necessary command in the text file

Note If automatic export is being setup for service mode, -S needs to be added to the command.

Step 3. Save the file as a batch or command file, .bat and .cmd respectively, in a location of your choosing.

How to set up a Scheduled Task for automatic import/export of configuration files? Step 1. Click the Windows Start button, go to Control Panel.

Step 2. Open the Scheduled Tasks control panel.

Step 3. Double click the Add Scheduled Task Wizard. Click Next in the Scheduled Tasks Wizard Welcome window.

Figure 226 – Add Scheduled Task Wizard

Step 4. Click Browse to navigate to the previously created batch file and select the file. Click Next.

Figure 227 – Select the batch file to run

Step 5. Name the task and select the frequency for the task to be performed. As there are various combinations of frequency possible the following screen may differ according to your setup. In Figure 228 we have chosen to have a monthly backup at 17:15, the first day of the month. Click Next.

Figure 228 – Scheduled Task frequency

Step 6. Enter the authentication details to make sure the scheduled task will run when required.

Figure 229 – Scheduled Task authentication

Step 7. Click Finish.

Tip Once a scheduled task has been created, further options can be configured further for better control. To access advanced settings, right-click the scheduled task and select Properties. Then select the Settings tab.

A.2 Directories to Backup

The following directories should be backed up:

C:\Program Files\Tango04\SmartConsole\Config

C:\Program Files\Tango04\SmartConsole\Templates

C:\Program Files\Tango04\SmartConsole\Messenger\config

C:\Program Files\Tango04\SmartConsole\Publisher\config

C:\Program Files\Tango04\SharedObjects\calendars\

Appendix B Appendix B: ALEV Logical Expression eValuator

The power of the ALEV Logical Expression eValuator enhances SmartConsole’s compatibility with UNIX and Linux systems. In combination with the Windows Server Agent, you can monitor and make effective use of UNIX/Linux messages in the SmartConsole. Using ALEV you can break down UNIX/Linux messages into many different variables that can then form the basis of your Business View and alarm configurations, extending the functionality of SmartConsole to all your UNIX and Linux systems. B.1 ALEV Functions Specific to SmartConsole B.1.1 Set Icon

This procedure allows you to set the icon used for a Business View. The change to the new icon is permanent.

PROCEDURE SET_ICON(BV_NAME STRING, ICON INDEX INTEGER)

You can find the icon value (icon index integer) from the folder BV Icons in the installation path of SmartConsole. B.1.2 Retrieve Criticalness

You can retrieve criticalness of a Business View or of a folder.

To retrieve the criticalness of a Business View use:

FUNCTION GET_CRITICALNESS( BV_NAME STRING): INTEGER

This function returns an integer of 0 through 3 representing the criticalness values:

• 0:Unknown

• 0: Harmless

• 1: Minor

• 2: Warning

• 3: Critical

• 0: Monitoring error

To retrieve the criticalness of a folder use:

FUNCTION GET_CRITICALNESS_BY_FOLDER( FOLDER_NAME STRING): INTEGER

Where:

• If the folder name is unique it is sufficient to enter only the folder name. However if the folder name is not unique you must enter the full path of the folder.

• This function returns an integer of 0 through 3 as described above.

A second function exists to be able to recover the values of the criticalness states unknown and monitoring error:

FUNCTION GET_CRITICALNESS_EX( BV_NAME STRING): INTEGER

This function returns an integer of 0 through 5 representing the criticalness values:

• 5:Unknown

• 0: Harmless

• 1: Minor

• 2: Warning

• 3: Critical

• 4: Monitoring error

To retrieve the criticalness of a folder use:

FUNCTION GET_CRITICALNESS_BY_FOLDER_EX( FOLDER_NAME STRING): INTEGER B.1.3 Changing Criticalness

The following procedures allow you to change the criticalness of any Business View or folder.

To set the criticalness of a Business View use:

PROCEDURE SET_CRITICALNESS(BV_NAME STRING, CRITICALNESS INTEGER)

The supported criticalness values are:

• 5:Unknown

• 0: Harmless

• 1: Minor

• 2: Warning

• 3: Critical

• 4: Monitoring error

To set the criticalness of a folder use:

PROCEDURE SET_CRITICALNESS_BY_FOLDER(FOLDER_NAME STRING, CRITICALNESS INTEGER)

Where:

• If the folder name is unique it is sufficient to enter only the folder name. However if the folder name is not unique you must enter the full path of the folder.

• The supported criticalness values are the same as above.

Important When you change the criticalness of this folder it will also change the criticalness of all of its subfolders.

B.1.4 Adding a Reason to the Criticalness Change

Two more procedures are available for setting criticalness. They work the same as the procedures mentioned above, but allow you to add an explanation to the event. This explanation or reason can later be used in BSM reports.

To set the criticalness of a Business View and add an explanation use

PROCEDURE SET_CRITICALNESS_EX( BV_NAME STRING, CRITICALNESS INTEGER, REASON STRING)

Where:

• The supported criticalness values are the same as above.

To set the criticalness of a folder and add an explanation use

PROCEDURE SET_CRITICALNESS_BY_FOLDER( FOLDER_NAME STRING, CRITICALNESS INTEGER, REASON STRING)

Where:

• If the folder name is unique it is sufficient to enter only the folder name. However if the folder name is not unique you must enter the full path of the folder.

• The supported criticalness values are the same as above. B.1.5 Add a Business View Filter to an Alarm

This function allows you to use an existing Business View filter in an alarm, for example. The alarm then checks if the message matches the specified Business View filter and depending on the result executes an alarm.

To add a Business View filter in an alarm use:

FUNCTION IS_EVENT_CONTAINED( BV_NAME STRING): BOOLEAN B.1.6 Including an Event ID in a Business View Filter

There is a quick way to exclude messages with a particular Event ID from a Business View in the message grid. This procedure does the opposite. It allows you to include messages with a specific Event ID in a Business View.

To include messages with a specific Event ID in a Business View use:

PROCEDURE ADD_EVENT_ ID_TO_BV _FILTER( BV_NAME STRING) B.1.7 Verify Calendar Date

You can now check a date in a specific calendar by using the following function:

FUNCTION IS_DATE_IN_CALENDAR( CALENDAR_NAME STRING, THEDATE DATETIME): BOOLEAN

B.1.8 Execute an Action Set

Launch an action set using the following ALEV procedure:

PROCEDURE EXECUTE_ACTION_SET( ACTION_SET_NAME STRING) B.1.9 Retrieve an LDAP Attribute

You can use this ALEV function to retrieve an e-mail address, for example.

To retrieve an LDAP attribute use:

FUNCTION GET_LDAP_ATTRIBUTE( USER_NAME STRING, ATTRIBUTE_NAME STRING): STRING

For example to retrieve an e-mail address, enter:

FUNCTION GET_LDAP_ATTRIBUTE( ‘INFO’, ‘MAIL’)

The result of the ALEV function is: [email protected] B.1.10 Export a Business View

This ALEV function automatically exports a Business View to XLS, XML, or HTML. The function format is:

PROCEDURE EXPORT_BUSINESS_VIEW( EXPORT_TYPE STRING, BUSINESS_VIEW_NAME STRING, DATE_TIME_FROM DATETIME, DATE_TIME_TO DATETIME, FILE_NAME STRING)

However, to specify these ranges you can use other functions such as NOW() or NOW() - 7, where you can specify whatever parameter you like. B.1.11 Export Business Views to XLS, XML, or HTML Format

The ALEV function below allows you to automatically export all descendent Business Views from a folder into XLS, XML, or HTML. The function format is:

PROCEDURE EXPORT_FOLDER( EXPORT_TYPE STRING,

FOLDER_NAME STRING,

DATE_TIME_FROM DATETIME,

DATE_TIME_TO DATETIME,

FILE_NAME STRING)

If FOLDER_NAME is equal to '' then you will export all Business Views. B.1.12 Convert SID to an Account Name

This ALEV function allows you to convert an SID to an account name. The function format is:

FUNCTION GET_ACCOUNT_NAME( SERVER_NAME STRING, SID STRING): STRING B.1.13 Activate or Deactivate an Alarm Folder

This ALEV functions allows you to activate or deactivate a folder on the Alarms tree. The function does not allow you to activate or deactivate the whole Alarm tree. The functions’ format are as follows:

• activation:

PROCEDURE DEACTIVATE_ALARMS_SUB_TREE(FOLDER_PATH:STRING);

• deactivation

PROCEDURE ACTIVATE_ALARMS_SUB_TREE(FOLDER_PATH:STRING);

Example

Our root Alarms folder is called Alarms but we want to deactivate the Alarms located in the subfolder Email here: Alarms\Tango04\Email. We would enter the following ALEV function:

PROCEDURE DEACTIVATE_ALARMS_SUB_TREE('Tango04\Email')

B.1.14 Retrieve an Array with All Calendar Names

This ALEV function allows you to retrieve an array with all existing Calendar names. The function format is:

FUNCTION GET_CALENDAR_NAMES():ARRAY

There are two possible arrays returned:

• []: this means that no Calendars exist

• [A, B...], where A and B are the names of your existing Calendars B.2 Advanced Service Functions B.2.1 Retrieve the Internal ID from a Business View

This ALEV function allows you to retrieve the internal ID from a Business View. The function format is:

FUNCTION GET_BV_ID ( BV_NAME STRING): INTEGER

If the value returned is positive then this is the correct ID. B.2.2 Retrieve an Array with All Names from a Business View Defined in the Business Tree.

This ALEV function allows you to retrieve an array with all names from a Business View defined in the Business Tree. The function format is:

FUNCTION GET_BV_LIST ( ): ARRAY

Returns the following values:

• [ ]: No Business View exists

• [A,B...]: Where A and B are the names of the Business Views in the array B.2.3 Retrieve an Array with All the Service Control Points and Basic Service Control Points on which a Business View is Impacting.

This ALEV function allows you to retrieve an array with all the Service Control Points and Basic Service Control Points that a Business View is impacting on. The function format is:

FUNCTION GET_IMPACT_LIST ( BV_NAME STRING): ARRAY

Returns the following values:

• [ ]: Business View name exists but is not impacting on the SCPs and BSCPs

• [A,B...]: Where A and B are the names of the Business Views that are impacting on the SCPs and BSCPs

B.2.4 Retrieve the Message from the Last Change of State from a Business View.

This ALEV function allows you to retrieve the message from the last change of state from a Business View. The function format is:

FUNCTION GET_LAST_STATE_CHANGE_MSG ( BV_NAME STRING): STRING B.2.5 Retrieve the Business Value for a Service Control Point

This ALEV function allows you to retrieve the value of a Service Control Point. The function format is:

FUNCTION GET_SCP_VALUE ( SCP_NAME STRING): INTEGER

If the value returned is positive then this is the correct Business Value. B.2.6 Retrieve the Total Business Value from the Impacted Service Control Point

This ALEV function allows you to retrieve the actual Business Value cost of a Service Control Point (the sum of the values of the SCP impacted by the Business Value). The function format is:

FUNCTION GET_BV_COST ( BV_NAME STRING): INTEGER

If the value returned is positive then this is the correct total Business Value. B.2.7 Set a Business Value for a Service Control Point

This ALEV function allows you to set a Business value for a Service Control Point. The function format is:

PROCEDURE SET_SCP_VALUE ( SCP_NAME STRING, VALUE INTEGER) B.3 Business Tree Modification Functions B.3.1 Check if a Folder Exists in the Business Tree

With this function you will know if a certain folder exists in the Business Tree. The function format is:

FUNCTION EXISTS_FOLDER(FOLDER_FULL_PATH STRING): BOOLEAN

FOLDER_FULL_PATH: String containing the folder full path without the root name (example: Servers\Cluster 001\Server XS1054)

Return Value: True if the folder is found in the tree, false otherwise B.3.2 Check if a Business View Exists in the Business Tree

With this function you will know if a certain Business View exists in the Business Tree as a child of the specified folder. The function format is:

FUNCTION EXISTS_BV(BV_NAME STRING, PARENT_FOLDER_FULL_PATH STRING): BOOLEAN

BV_NAME: String containing the name of the BV (example: Server XS1054 Ping)

PARENT_FOLDER_FULL_PATH: String containing the parent folder full path without the root name

Return Value: True if the BV exists in the specified folder, false if not, error if the specified parent folder does not exist B.3.3 Move a Folder to a New Destination in the Business Tree

This function moves a folder to a new destination parent folder. The function format is:

FUNCTION MOVE_FOLDER(FOLDER_FULL_PATH STRING, DESTINATION_PATH STRING): STRING

FOLDER_FULL_PATH: String containing the folder full path without the root name (example: Servers\Cluster 001\Server XS1054)

DESTINATION_PATH: String containing the destination folder full path without the root name (example: Servers\Cluster 002)

Return Value: A string containing the new folder full path or script error if the folder or destination are not found (example: Servers\Cluster 002\Server XS1054) B.3.4 Move a Business View to a New Destination in the Business Tree

This function moves a BV to a new destination parent folder. The function format is:

PROCEDURE MOVE_BV(BV_NAME STRING, PARENT_FOLDER_FULL_PATH STRING, DESTINATION_PATH STRING)

BV_NAME: String containing the name of the BV (example: Server XS1054 Ping)

PARENT_FOLDER_FULL_PATH: String containing the parent folder full path without the root name (example: Servers\Cluster 001\Server XS1054)

DESTINATION_PATH: String containing the destination folder full path without the root name (example: Servers\Cluster 002\Server XS1054) B.3.5 Make a Multiple Copy of a Folder in the Business Tree

This function makes a Multiple Copy of a folder. The function format is:

FUNCTION MULTIPLE_COPY_FOLDER(FOLDER_FULL_PATH STRING, SEARCH_TEXTS ARRAY, REPLACE_TEXTS ARRAY): STRING

FOLDER_FULL_PATH: String containing the folder full path without the root name (example: Servers\Cluster 001\Server XS1054)

SEARCH_TEXTS: Array containing the strings to search (example: [Server XS1054])

REPLACE_TEXTS: Array containing the strings to replace by (example: [Server XS1055])

Return Value: The new folder full path created after the multiple copy or raises a script error if any element is not found (example: Servers\Cluster 001\Server XS1055) B.3.6 Make a Multiple Copy of a Business View in the Business Tree

This function makes a Multiple Copy of a Business View. The function format is:

PROCEDURE MULTIPLE_COPY_BV(BV_NAME STRING, PARENT_FOLDER_FULL_PATH STRING, SEARCH_TEXTS ARRAY, REPLACE_TEXTS ARRAY)

BV_NAME: String containing the name of the BV (example: Server XS1054 Ping)

PARENT_FOLDER_FULL_PATH: String containing the parent folder full path without the root name (example: Servers\Cluster 001\Server XS1054)

SEARCH_TEXTS: Array containing the strings to search (example: [Server XS1054])

REPLACE_TEXTS: Array containing the strings to replace by (example: [Server XS1055])

B.3.7 Delete a Folder from the Business Tree

This ALEV function deletes a specified folder or raises a script error if the folder is not found. The function format is:

PROCEDURE DELETE_FOLDER(FOLDER_FULL_PATH STRING)

FOLDER_FULL_PATH: String containing the folder full path without the root name (example: Servers\Cluster 001\Server XS1054) B.3.8 Delete a Business View from the Business Tree

This ALEV function deletes a specified Business View or raises a script error if the folder is not found. The function format is:

PROCEDURE DELETE_BV(BV_NAME STRING, PARENT_FOLDER_FULL_PATH STRING)

BV_NAME: String containing the name of the BV (example: Server XS1054 Ping) B.4 Using UNIX/Linux Messages at the SmartConsole

Once your UNIX or Linux messages have been forwarded to the SmartConsole, the messages will arrive in single text format. Thanks to the ALEV Logical Expression evaluator, you can break these single texts down into meaningful, useful values that can then be used in your Business View and alarm configuration. For more information, see the ALEV Reference Manual. B.4.1 Example 1: New User Creation

Imagine you have a UNIX message that arrives at VISUAL Message Center from a UNIX machine with &FIRSTLEVEL text:

UNIXSERVER useradd[19771]: new user: name=raul, uid=500, gid=0, home=/ home/raul, shell=/bin/bash

In its current state, it takes a bit of interpreting to know what has happened. Using ALEV, however, you can preprocess this message text to break it down into useful, understandable components. To divide this single text message into seven different variables, you could use an expression such as:

&FIRSTLEVEL MATCH ‘&SERVERNAME useradd[&NUMBER]: new user: name=&NEWUSER, uid=&UID, gid=&GID, home=&HOME, shell=&SHELL’

This means that when the message arrives at the console, it will have variables with the following contents:

&SERVERNAME = ‘UNIXSERVER’

&NUMBER = 19771

&NEWUSER = ‘raul’

&UID = 500

&GID = 0

&HOME = ‘/home/raul’

&SHELL = ‘/bin/bash’

You can also add another logical condition to the preprocess to turn the UNIX message into plain English:

User &NEWUSER has been created in &SERVERNAME

This would mean that in the final message that appears in the console, there would be a simple phrase:

User raul has been created in UNIXSERVER. B.4.2 Example 2: Security Alert

Let us assume that a UNIX message arrives with &FIRSTLEVEL text of:

UNIXSERVER in.telnetd[4749]: connect from 204.21.0.3

A preprocess condition could extract the telnet IP in the message so that it could then be compared to a list of authorized IPs to see if it is a possible security threat. First you would extract the IP address from the UNIX message:

&FIRSTLEVEL MATCH ‘&SERVER in.telnetd[&NUMBER]: connect from &IPADDRESS

From the resulting message, you could compare the IP address against a series of known or authorized IPs. If it is not included in the list, you can deduce that it is an unauthorized attempt to access the network from the outside using telnet. To create a warning of this, you could set a post action to send the following message:

There is a Telnet connection from &IPADDRESS currently active. &IPADDRESS is not from the LAN nor a know IP address.

In this case, it would arrive at the SmartConsole as follows:

There is a Telnet connection from 204.21.0.3 currently active. 204.21.0.3 is not from the LAN nor a know IP address.

Then, using the IP as a variable, you can abort the process using a console alarm.

Appendix C Appendix C: Increasing Windows Registry Size

If you are creating an unusually high number of alarms in SmartConsole, you may reach the maximum registry size (this does not occur in Windows XP or 2003 Server).

To increase the registry size: Step 1. Choose Windows Start Menu > Settings > Control Panel > System.

Step 2. Select the Advanced tab.

Step 3. Click Performance Options. The following dialog box appears:

Step 4. Click Change…. The Virtual Memory dialog box appears, where you can also set the registry maximum size:

Note Windows will automatically prompt you to increase the Paging File size so it is large enough to handle the new registry size.

After you increase the maximum registry size, click OK to accept the changes. The changes will be available on next system restart.

Appendix D Appendix D: Disk-Usage & Message-Processing Tests

The following tests were performed on SmartConsole v8.0 Service Pack 03. D.1 Performance Tests

These tests were performed in order to benchmark the processing capabilities of SmartConsole 8.0.

Note Performance test results may vary depending on: hardware used; network connections and use of databases; SmartConsole configuration (the number of Business Views, Service Control Points, affectations, etc.).

D.1.1 Host Configuration

The following tests were performed on the following hardware (where SmartConsole was installed):

• Intel i5-750 2.8Ghz 4-core processor

• Intel H55 Chipset

• 8GB RAM 1333Mhz DDR3 memory module

• 500 GB Western Digital Caviar Blue 16MB Cache, 7200 RPM hard drive; host OS installed

The OS installed on the host machine was Windows Server 2008 R2 Standard. D.1.2 Virtual Machine Configuration

The tests were performed on a virtual machine whose configuration was:

• Intel Core i5 CPU-750 processor using 2 cores at 2.8Ghz

• 4 GB of allotted RAM

• Hard drives: − 320GB Seagate 16MB Cache 7200 RPM drive used to install the virtual OS − 320GB Seagate 16MB Cache 7200 RPM drive used as the SmartConsole database

The virtual machine was created using (Oracle's) VirtualBox, and a Windows Server 2008 R2 x64 OS was installed to be used for all the tests. Before we began our tests, our SmartConsole database already had 40,000,000 stored messages in it.

The following software was installed on the different servers affected during the tests:

• On the virtual host (described in section D.1.2 - Virtual Machine Configuration): − Windows Server 2008 R2 x64 − SQL Server 2012 used for the SmartConsole database DSN − VISUAL Message Center SmartConsole Kernel v8.0 − VISUAL Message Center SmartConsole Messenger − VISUAL Message Center SmartConsole Publisher

• On the database server (a physical server): − SQL Server 2008 used to store ThinkServer's messages

• On the secondary virtual host (hosted on another physical server): − VISUAL Message Center ThinkServer − VISUAL Message Center SmartConsole Web Client v8.0 − VISUAL Message Center SharedObjects − VISUAL Message Center AccessServer D.3 Results D.3.1 Database Disk Usage

Disk usage per message Each message stored in the database uses approximately 3 KB of disk space (without any BSM data). According to this, and depending on how many messages your SmartConsole receives per day, you will need to configure database maintenance using VISUAL Message Database Settings Administrator (see its user guide for instructions). Please take into account that if you are saving historical data, the same space is also required for each message in the historical db.

Number of messages Disk space

1,000,000 3,000 MB

5,000,000 15,000 MB

30,000,000 90 GB

BSM disk usage Database disk usage depends on where the SCPs are located in a particular SmartConsole configuration, and also how many messages change the health states of the different Business Views and Folders. For our results we used a configuration with 10,000 components, each showing 2 health- state changes per day.

Each change of state takes about 1 KB of storage, which translates to 20 MB per day. After 1 month you would need about an extra 620 MB of your database disk space (apart from the space required to store the messages).

D.3.2 Message Processing

During our tests we measured how many messages SmartConsole was capable of processing, when receiving up to 1,000 messages per second. Message-processing speed is affected not only by hardware/network, but also depends on SmartConsole configuration.

Note The SmartConsole database used for these tests already had more than 40,000,000 stored messages.

Scenario (1,000 events per Average number of messages processed per second) second

BSM not active, the onrush of events having the same health ~1,000 state

BSM not active, all incoming ~600 events with different health states

BSM active, all incoming events ~300 with different health states

Appendix E Appendix E: Hotkeys

E.1 Business Tree Hotkeys

The Hotkeys available from the Business Tree are detailed in the following table.

Hotkeys Function

CTRL.+F New Folder

CTRL.+B New Business View

CTRL.+C Copy

CTRL.+V Paste

CTRL.+W Paste as Link

Del Delete

CTRL.+R Reset Criticalness

CTRL.+O Advanced Criticalness Options

F2 Rename

CTLR.+I Information Window E.2 Business List

When you select a Folder in your Business Network List the Business list appears in the panel to the right. The Hotkeys available from the Business list are mentioned in the following table.

Hotkeys Function

CTRL.+F New Folder

CTRL.+B New Business View

CTRL.+C Copy

Hotkeys Function

CTRL.+V Paste

CTRL.+W Paste as Link

Del Delete

CTRL.+R Reset Criticalness

CTRL.+I Information Window E.3 Messages List

When you select a Business View in your Business Network List the Messages list appears in the panel to the right. The Hotkeys available from the Messages list are mentioned in the following table.

Hotkeys Function

CTRL.+A Select all

CTRL.+C Cancel reply message

CTRL.+I Ignore reply message

CTRL.+R Retry reply message

CTRL.+G Go On Processing reply message

CTRL.+D Reply by Default

CTRL.+T Reply by Text

Note The functions for reply messages are only available when you have selected AS400 messages that are pending reply. Otherwise these menu options and hotkeys will not be available.

E.4 Enterprise View

The Hotkeys available from the Enterprise Network are mentioned in the following table.

Hotkeys Function

CTRL+N New Enterprise View

F2 Rename Enterprise View

Del Delete Enterprise View

CTRL+Del Delete All Enterprise Views

CTRL+X Close Enterprise Views

The following table lists the hotkeys that are available in the Alarms and Action Sets configuration.

Hotkey Function

Ctrl+F Create Folder

Ctrl+A Create Alarm/Action Set

F2 Rename Folder or Alarm/Action Set

Del Delete Folder or Alarm/Action Set

Ctrl+C Copy Folder or Alarm/Action Set

Ctrl+V Paste Folder or Alarm/Action Set

Appendix F Appendix F: Contacting Tango/04

EMEA (European, Middle-Eastern & African) Latin American Headquarters Headquarters Barcelona/04 Computing Group SRL Tango/04 Computing Group S.L. Avda. Federico Lacroze 2252, Piso 6 Avda. Meridiana 358, 12 B-C 1426 Buenos Aires Capital Federal 08027 Barcelona Argentina Spain Phone: +54 11 4774-0112 Phone: +34 93 274 0051 Fax: +54 11 4773-9163 Fax: +34 93 345 1329 [email protected] [email protected] www.barcelona04.com www.tango04.com

North America (USA & Canada) Sales Office in Brazil

Tango/04 Computing Group USA Tango/04 Computing Group Brasil PO Box 3301 Rua Turiassú, 591 - 5º Andar Peterborough, NH 03458 Perdizes USA Cep: 05005-001 São Paulo

Brasil Phone: 1-800-304-6872 Fax: 858-428-2864 Phone: +55 (11) 3675 6228 [email protected] Fax: +51 1 211-2526 www.tango04.com [email protected] www.tango04.com.br

Sales Office in Chile Sales Office in Columbia

Barcelona/04 Computing Group Chile Barcelona/04 Computing Group Colombia Guardia Vieja 255, Of. 1601 Calle 125 nº 19-89, Piso 5º Providencia Bogotá, D.C. Santiago Colombia Chile Phone: + 57(1) 658 2664 Phone: +56 2 234 0898 Fax: +51 1 211-2526 Fax: +56 2 234 0865 [email protected] [email protected] www.barcelona04.com www.barcelona04.com

Tango/04 France Tango/04 Computing Group Italy La Grande Arche Viale Garibaldi 51 Paroi Nord 15ème étage 13100 Vercelli VC 92044 Paris La Défense Italy France Phone: +39 0161 56922 Phone: +33 01 40 90 34 49 Fax: +39 0161 259277 Fax: +33 01 40 90 31 01 [email protected] [email protected] www.tango04.it www.tango04.fr Sales Office in Peru Sales Office in Switzerland

Barcelona/04 Computing Group Perú Tango/04 Computing Group Switzerland Calle Isaac Albeniz 555, Dpto 201 Urb 18, Avenue Louis Casaï Las Magnolias CH-1209 Genève San Borja Switzerland L 27 Lima Perú Phone: +41 (0)22 747 7866 Fax: +41 (0)22 747 7999 Phone: +51 1 640-9168 [email protected] Fax: +51 1 211-2526 www.tango04.fr [email protected] www.barcelona04.com

Glossary

A AccessServer Tango/04’s security application. It provides authentication and authorization services (like User Management and single sign-on) to all Tango/04 apps. Part of the Monitoring Engine (Submodel-Mxx).

Action A task that SmartConsole performs automatically when an Alarm is triggered. Actions include: writing to the Event Log, Executing an OS/400 command, Sending an e-mail, and more.

Action Set A set of Actions that SmartConsole performs automatically when an Alarm is triggered.

Actor An Actor, who plays an Application Role in Tango/04 apps, can be any Windows user or group, or another Application Role.

Advanced Assistance Services A credit-based help system for Tango/04 Customers who need occasional help with their Monitoring Solution.

Agent Code (SmartConsole) A ThinAgent’s three-letter identification code. Each event arriving to SmartConsole from ThinkServer has this unique identification code, so you can: tell which ThinAgent the event came from; filter for events coming from a specific ThinAgent.

Agent Code (ThinkServer) Represented by the variable VSMAgentID, this is a ThinAgent’s three-letter identification code.

Agentless Agents installed in ThinkServer—not in the target machine—are considered agentless because they do not involve installing on/consuming client resources.

Alarm A SmartConsole filter that enables the user to be notified of certain events, perform actions, etc. An alarm may or may not include audible/visible alerts.

ALEV iSeries Agents use a scripting language that allows the user to perform advanced operations or change the information contained in a message. This powerful yet simple scripting language is called ALEV and is explained in the Arithmetic-Logic Expression eValuator (ALEV)1.5 - Reference Manual. Part of the Monitoring Engine (Submodel-Mxx).

Analysis Panel The bottom panel of SmartConsole (Web Client) wherein the user can see the components being affected by a selected component experiencing a non-harmless health state. In the SmartConsole desktop client this panel is known as the Problem Root Cause panel.

Application Role An Application Role is a user’s level of importance in a Tango/04 application. By default, three Application Roles exist: Viewer, Creator, and Administrator. New roles can also be created.

Applications Agent A Legacy Monitoring Engine-standard product. Reads any real-time text file (from servers, applications etc.).

Auto-Enterprise View The default way that SmartConsole Web Client displays the inner componenets of a selected Business Folder. It is for the sake of organization, as the user can see any subfolders and all the corresponding Business Views placed in their actual folders. An Auto-Enterprise View is not an Enterprise View.

B Batch Queues Monitor Included with VISUAL Message Center iSeries Base and the VISUAL Message Center Suite for Operations. Allows the monitoring of messages from any iSeries message queues. Not sold separately.

BEA WebLogic Operations Agent A group of ThinAgents that monitor WebLogic Servers for bandwidth events and JMS messages exchanged between applications. Comes standard with the Monitoring Engine’s ThinkServer.

Browser Panel The SmartConsole panel (at upper right) showing the components included in a selected Service Model Business Folder. As long as a folder is selected on the Service Model, Auto-Enterprise Views appear in this panel in SmartConsole Web Client.

BSM See Business Services Management.

Business Category A user-defined label for any SmartConsole Business Component. This property can be reused in VISUAL Message Center Reports and VISUAL Message Center Goals.

Business Folder A folder anywhere on the SmartConsole Service Model. It can contain other Business Folders, Business Views, and SCPs. Business Folders are usually identifiable by a folder icon.

Business Network The entire “Service Model” (or “Tree”) in the desktop SmartConsole interface.

Business Services Management (BSM) A Monitoring Engine add-on that includes: nonstandard SLA Analytics and Reporting ThinAgents in ThinkServer; the ability to have SCPs and Total Impact Cost in SmartConsole; nonstandard BSM reports in Reports; special dashboards in Dashboards.

Business Value A numeric weight given to a SmartConsole SCP, it represents the cost to your business that an event has on a monitored service or application. It is a user-defined number that should reflect lost profits, lost customers, or the like.

Business View In VISUAL Message Center SmartConsole, a Business View represents an IT element of a business service or process. Business Views are the ends of the branches in the Service Model (tree). They group relevant incoming events and change Health status accordingly.

Business View Message Panel In SmartConsole, the Browser panel becomes the Business View Message Panel when the user drills down, on the Service Model, to a Business View. The events (messages) corresponding to the Business View are listed in the panel.

C Calendar Created online via SharedObjects, a Calendar can be used across the range of Tango/04 apps to have an application consider only those days and hours set forth in the Calendar when handling events.

Child Reports The number of reports that have been launched from a report template.

Cisco PIX/ASA Security Agent These ThinAgents monitor your Cisco PIX and ASA firewall devices. This Agent does not come standard with the Monitoring Engine. Product code Submodel-TSN.

Citrix Operations Agent A sold-standard group of standard.ThinAgents that monitor Citrix farms and MetaFrame servers for processes, sessions, bandwidths, performance, datastore availability, users, and application load level, among other things.

Commander The ThinkServer DOS-command line tool that enables users to quickly and easily list, start and stop monitors, and view events.

Connector Determines where data used by Goals will come from. Connectors can be of type SmartConsole or ThinkServer.

Contact A third party that is involved with a particular SLA (or goal) in VISUAL Message Center Goals. Contacts usually include: the name of the company, a primary contact person, and e-mail and phone details.

Contract The binding SLA between you (your IT department or your organization) and another party, entered in VISUAL Message Center Goals. Contracts include: contact details for both parties, start and end dates, etc.

Crash Preventer A product for the iSeries platform that is included with both the VISUAL Message Center Suite for Operations and VISUAL Message Center iSeries Base.

Criticalness The health-state of a Business Component in SmartConsole: Harmless, Minor, Warning, Critical or Unknown.

Criticalness Propagation The way by which a Business Component in a Harmless, Minor, Warning or Critical state affects a parent component. User-defined, can be set to: Cause/Effect, Simple Redundancy, Custom Rules, etc.

Custom Command Agent This ThinAgent group lets you execute single or multiple commands and scripts on remote Windows and Linux/UNIX systems, controlling the output returned. It has a wide range of use. A standard Agent.

D Dashboards VISUAL Message Center Dashboards is Tango/04’s real-time dashboard application. Including many predefined dashboards, it lets users view everything from system performance to business trends. The dashboards include charts, tables, gauges, and can handle SmartConsole branches, and can be shared across installations. Product code Submodel-DSB.

DashboardServer A legacy product, it was replaced by VISUAL Message Center Dashboards.

Data Adapter Agent This ThinAgent group allows you to collect a wide variety of events for ThinkServer using SQL queries via ODBC connections. Pre- and post- queries are also used to modify these events to your liking. Monitoring Engine-standard.

Data Collector for Goals A group of ThinAgents acting in ThinkServer to collect the data that Goals needs. This Agent is sold and used by Tango/04 Customers without a Monitoring Engine (a Customer having just Goals, for example). It has product code Submodel-TOG.

Data Monitor for iSeries Available for both Reads (DMI-REA) and Changes (DMI-BAS), and in an Express version as well (DMI- EXP), these products monitor IBM DB2 UDB databases, and comes with best-practices that are useful in security auditing. It is installed on the server you wish to monitor.

Database Settings Administrator Tango/04’s database management program for all Tango/04 apps. It lets you create each application’s database, manage event signatures, variables, and define retention policies. Part of the Monitoring Engine (Submodel-Mxx).

Debugging Agent (powered by VDW) VISUAL Message Center Debugging Agent is an iSeries debugging product that enables a user to monitor and control Jobs, applications, Security, system information. It displays problematic source code and lets the user run commands and modify variables. Formerly known as VISUAL Debugger for WIndows. Product code VDW.

Dependencies A relationship between one SmartConsole alarm and another. Specifically, if the first alarm is triggered, then the second one is automatically triggered as well.

Device Monitor A product for the iSeries platform that is included with both the VISUAL Message Center Suite for Operations and VISUAL Message Center iSeries Base. It notifies the user of the statuses of drivers, devices, and communication lines.

E Element ID Used in ThinkServer—in Data Collection for Dashboards—it is a user-defined text variable that appears with an event (to distinguish it from others) when a monitor is producing multiple events per recollection.

Enterprise Problem Solver A Legacy product, code EPS.

Enterprise View Provides a top-down, high-level view in SmartConsole. Constructed using Service Model elements, you can add Business Views, Business Folders and SCPs to an Enterprise View, create custom backgrounds and place the selected elements exactly where you need to. You can even create links to other Enterprise Views or URLs, offering quick access to important information.

Escalation List A list of e-mails/mobile phone numbers (for SMS) by which SmartConsole tries to contact operators when an alarm in triggered. SmartConsole tries first to contact the operator at the bottom of the list, and

if no reply is received (or receipt of message delivered) within a certain amount of time, it moves up the list, attempting to contact the next operator, until an answer or appropriate response is received. The Escalation List is editable in Notifier, which handles the sending of the e-mails and SMS (text) messages for SmartConsole.

Events Integrity Agent This Monitoring Engine-standard Agent (one ThinAgent, in this case) provides security to the T4EventLob table. It verifies the digital signatures of events and detects unauthorized modifications or deletions.

Exchange Server Operations Agent There are two of these Agents: one for Exchange 2003, and the other for Exchange 2007-2010. They both include several ThinAgents that monitor the performance of the Exchange mail system itself as well as the relevant databases, services, DAGs, mailboxes, etc. Product code Submodel-TOE.

Exclusion Range A period of time in a Calendar that is not considered by a Tango/04 application in which the Calendar is used.

F Filters Used widely by VISUAL Message Center products to facilitate the easy retrieval of specific data.

Folder See Business Folder.

G Global Variables ALEV variables that the user can define in SmartConsole, for use in scripts.

Goals VISUAL Message Center Goals is a Tango/04 product that provides real-time calculation for SLAs and goals making sure you reach important service goals and avoid failures that can impact on your clients or can come from your suppliers.

H Health There are five possible health values that represent the current monitor status: unknown, critical, warning, minor, and success. The user can define monitor health conditions with the Health and Actions Wizard. When defining the health condition assignment you can use any of the variables available in the monitor. Every time the data source state is refreshed the configured health scripts are executed to assign the new monitor health.

Health Action (ThinkServer) A Python script that a ThinkServer monitor runs when an event is found to match the conditions of a Health state.

HP Systems Insight Manager Agent A group of ThinAgents that capture, from your current HP Systems Insight Manager software, the statuses and performances of your HP logical disks and controllers, memory modules, hardware fans and temperature, network interface adapters, physical disks and controllers, power supplies and consumptions, processors and CPUs. Standard with Monitoring Engine.

Hyperhashing Tango/04 technology that boosts the efficiency of SmartConsole filters so that incoming events are processed up to 99% faster.

I IBM Director SNMP Agent This Agent is made up of one ThinAgent that lets you incorporate the physical and virtual IBM infrastructure currently monitored by IBM Director. Processing, disks and memory, configuration, and device-health events appear in ThinkServer. Comes standard with the Monitoring Engine; not sold separately.

Impact Analysis SmartConsole’s way of showing a user how one component is affecting another (how a Business View is affecting SCPs, for example).

Indicator In VISUAL Message Center Goals, an Indicator performs the calculation (and/or Python expression) for each inflowing variable instance. An Indicator’s output is compared against the conditions of a corresponding goal; this determines the goal’s status.

Interactive Agent A product for the iSeries platform that is only available as part of the VISUAL Message Center Suite for Operations and VISUAL Message Center iSeries Base. It monitors for any interactive error in the system and allows for automatic freezing of the user session. Not sold separately.

iSeries Agentless Security Only available as part of the VISUAL Security Suite - Security Package (VSS) and the Submodel iSeries Security Agent, these ThinAgents are partly agentless and return Security events based on job inactivity, system and network attributes, etc. Not sold separately.

iSeries Audit Journal Available as part of either the Submodel iSeries Security Agent or the VISUAL Security Suite - Security Package (VSS). Spawns events based on the iSeries Audit Journal. Not sold separately.

iSeries Operations ThinAgents Included (exclusively) with both the VISUAL Message Center Suite for Operations and VISUAL Message Center iSeries Base, these ThinAgents are partly agentless and return Operations events based on queues, jobs, OUTFILE output, etc. Not sold separately.

iSeries Performance Agent VISUAL Message Center iSeries Performance Agent also known as VCW, is included in the VISUAL Message Center Suite for Operations as well as VISUAL Control Center. Available as a standalone product. It monitors the performance of iSeries systems. Product code VCW-ISE.

iSeries Performance Manager VISUAL Message Center iSeries Performance Manager is included in VISUAL Control Center, and is made up of two products: VISUAL Control for Jobs and VISUAL Control for Pools. It boosts system response time and automates job control and optimizes memory for pools. Product code Submodel-VJP.

iSeries Security Agent VISUAL Message Center iSeries Security Agent is also available as a standalone product, this Agent comes as part of the VISUAL Security Suite - Security Package (VSS). It is particularly useful for Security auditing and automated protection. Product code Submodel-SEC.

iSeries SQL Agent VISUAL Message Center iSeries SQL Agent includes the iSeries SQL Interactive Monitor and the iSeries SQL Monitor. It is useful in securing iSeries SQL databases and increasing application availability. Product code Submodel-SQL.

iSeries Support Agent VISUAL Message Center iSeries Support Agent also known as VISUAL Support, is included in the VISUAL Message Center Suite for Operations as well as VISUAL Control Center. It has a Remote Control functionality and is especially beneficial to programmers/technicians in situations where applications are undergoing big changes. Product code Submodel-RST

iSeries Restricted State Monitor VISUAL Message Center iSeries Restricted State Monitor requires either the Monitoring Engine or VISUAL Message Center iSeries Base. It delivers informational events when an iSeries system goes into a restricted state. Product code VSP.

J JBoss Operations Agent A ThinAgent group that comes standard with the Monitoring Engine (not sold apart). They monitor JBoss Application Servers and produce events related to memory pools, threads, CPU, and message queues.

JMX Generic Agent This (single) ThinAgent is shipped with the Monitoring Engine, and is not sold individually. It monitors target MBeans and their attributes for Java application resource usage, response times and server performance.

Job Activity Monitor Included (exclusively) with both the VISUAL Message Center Suite for Operations and VISUAL Message Center iSeries Base, this ThinAgent is useful in reporting unfinished or prematurely finished iSeries jobs. Not sold separately.

Job Duration Monitor Included (exclusively) with both the VISUAL Message Center Suite for Operations and VISUAL Message Center iSeries Base, this ThinAgent produces events when an iSeries job exceeds predefined times. Not sold separately.

Job Status Monitor Included (exclusively) with both the VISUAL Message Center Suite for Operations and VISUAL Message Center iSeries Base, this ThinAgent produces events if an active job has spent too long in a given abnormal state, such as MSGW or INEL. Not sold separately.

Job Que Status Monitor Included (exclusively) with both the VISUAL Message Center Suite for Operations and VISUAL Message Center iSeries Base, this ThinAgent monitors job queues for the presence of problems such as full or blocked queues, jobs in excessive HLD or RLS, etc. Not sold separately.

K KeyInfo An XML file that you create with NiceLink Configurator. It contains the serial number and MAC address of a system for which you need a product activation key.

L Label A user-defined piece of text that appears on a dashboard.

Launch To run a report based on a template in VISUAL Message Center Reports.

Link Generator A VISUAL Message Center Dashboards dashboard sharing tool. A dashboard shared this way can be used—with full functionality, if desired—by another Dashboards user..

Linux Operations Agent A nonstandard ThinAgent group for Linux and FreeBSD Operations. They spawn events related to physical and virtual memory, CPU, processes, file systems, etc. Product code Submodel-TOL.

Linux Security Agent A non-standard ThinAgent group for Linux and FreeBSD Security. They monitor, via SSH or Syslog, user and group activity, file systems, audit logs, etc. Product code Submodel-TSL.

M Managed Administration Services A service offered by Tango/04 whereby a Customer’s Monitoring Solution is managed remotely.

Middleware Programs essential to the VISUAL Message Center product suite that do not demand a high level of user-interface interaction: AccessServer, ALEV, Database Settings Administrator, NiceLink, Scheduler, SharedObjects.

Message Panel Also known as the Message Grid, this is the upper panel in SmartConsole that shows the events filtering in to a Business View.

Monitor Any instance of a ThinAgent. For example, to monitor the Availability of two different computers on your network you create two different monitors from the Network Basic Agent’s Ping ThinAgent—one for each IP address.

Monitoring Engine Tango/04’s standard monitoring solution. It is composed of ThinkServer (with its various standard ThinAgents), SmartConsole (and its Web Client), Reports, and also the following middleware: AccessServer, Database Settings Administrator, Notifier, NiceLink, SharedObjects, and Scheduler. It also includes two Web Portal Users. Product code Submodel-Mxx.

Multiple Copy An action on any part or parts of the SmartConsole Service Model or Enterprise Views, it involves the duplication of the copied component(s) while renaming the pasted component(s). You can save a Multiple Copy for use later, by exporting it (this is only possible in the desktop console).

N Narrow Table The type of table in VISUAL Message Center Dashboards that typically includes one host, several variables (aligned vertically).

Network Basic Agent A Monitoring Engine-standard ThinAgent group that monitors ports, POP3, SMTP, and performs pings to check network devices.

Network Operations Agent This ThinAgent group does not come standard with the Monitoring Engine. It monitors Cisco Operations (memory, processors, temperature, interfaces, top flows). Product code Submodel-TON.

Network Syslog Agent A non-standard ThinAgent that captures events from the Syslog Daemon for use in ThinkServer (and thus, all other VISUAL Message Center apps). Product code Submodel-TNW.

NiceLink A network protocol created by Tango/04 to manage different communication protocols, such as TCP/IP, PPC and SNA Server, allowing VISUAL Message Center SmartConsole (and other Tango/04 products) to communicate with servers running different operating systems and different network protocols. Part of the Monitoring Engine (Submodel-Mxx).

Non Resilient Mode A SmartConsole operation mode that disregards events sent to the console at times when it is off. Faster than the resilient mode, especially in cases where the console has been down a long time.

Notifier Notifier allows VISUAL Message Center SmartConsole (as an Alarm Action, for instance) to send SMS messages or e-mail from a mobile phone connected to a PC (the “server” phone) or an SMTP mail server to another mobile device (the “receiver” phone) or e-mail address, and reply to a message from any device via the server phone or via e-mail.

O Operations Knowledge Module for IBM i This product can be added on to: the Monitoring Engine with the VISUAL Message Center Suite for Operations, or the Monitoring Engine with VISUAL Message Center iSeries Base. System i features and functions in ThinkServer, SmartConsole, Reports and Dashboards. Product code Submodel-KIO.

Oracle Operations Agent Includes a wealth of ThinAgents; for Availability, Performance, and Alert Log, to name a few. Product code Submodel-TOO.

Oracle Security Agent ThinAgents that return Profile-, Role-, Login- and User-Manipulation events. Product code Submodel- CSO.

P Paste as Link An action in SmartConsole whereby you are able to paste any Service Model component(s) onto another as a link. A pasted Business Folder icon appears with an arrow on it to indicate that is it a link, whereas the icon of a pasted Business View does not.

Player A SmartConsole Web Client feature. Show a rolling, live presentation of desired Enterprise Views. Can be shared.

PMDB Used by VISUAL Message Center to manage data source configuration and retention policies.

Policy Compliance for Windows An Agent including several ThinAgents. They notify you when Windows Policies are changed, etc. Useful in Auditing for Regulatory Compliance. Product code Submodel-TWP.

Portal User A Tango/04 Portal User is an AccessServer-registered user for all desktop and Web applications. Two Tango/04 Portal Users are included with the Monitoring Engine. Extra Portal Users are sold in packages of Users under product code Submodel-USE.

Post Event Group Action An action that a ThinkServer monitor performs for an event group after Health rules are applied.

Post Health Check Action An action that a ThinkServer monitor performs for each incoming event after Health rules are applied.

Pre Event Group Action An action that a ThinkServer monitor performs for an event group before Health rules are applied.

Pre Health Check Action An action that a ThinkServer monitor performs for each incoming event before Health rules are applied.

Preprocess A combination of a filter that screens events and an ALEV expression that modifies them as soon as they reach SmartConsole (before appearing in the console).

Problem Root Cause Panel In SmartConsole (the desktop client), this is the panel at bottom-right when any Business Folder is selected. It shows all the Business Views contained in the folder, their Total Impact, etc.

Python Generic Agent Included with the Monitoring Engine, this ThinAgent can run any user-defined Python script at a specified time interval. Does not recollect data (used for scripting).

R Range Set A group of weekdays with desired hours (from a 24-hour scale) that you add to a Calendar. The days and hours set forth in a range set are the beginnings of a Calendar: the range set sets the days and hours that events will be considered.

Repetitions SmartConsole alarm controls that determine if an alarm will repeat (or not), etc., if it has recently triggered.

ReportingSystem A legacy product, replaced by VISUAL Message Center Reports.

Reports A VISUAL Message Center module that allows you to create a variety of reports in real time or report on historical data. It uses ODBC to connect to data stored in the VISUAL Message Center databases and creates reports that allow you to view historical message information, Security, Auditing policies, User Usage/Accounting data, Performance Data, SLAs and more. This Web-based application is shipped with the Monitoring Engine.

Resilient Mode

An operation mode that allows SmartConsole to recuperate events that have occurred while the console was off or disconnected.

Restricted State Monitor Included (exclusively) with both the VISUAL Message Center Suite for Operations and VISUAL Message Center iSeries Base, it produces events based on (QSYSOPR) messages when the iSeries system is in a restricted state. Not sold separately.

Role See Application Role.

S Scheduler A piece of middleware that enables the execution of Tasks that you schedule in Dashboards and Reports.

Scorecard A page within VISUAL Message Center Goals where the user sees the statuses of all goals. Goals has real-time, historical, and summary scorecards. Each are filterable (they can show specific goals if desired).

SCP See Service Control Point.

Security Model The product-specific security configuration stored by AccessServer for each Tango/04 product. A Security Model is important because it holds all the user permissions you have configured in a product.

Selector A selection field in dashboards whereby the user chooses which data he wants the dashboard to show when he clicks the Show Dashboard button.

Service Level Agreement (SLA) An agreement between an organization and a service provider, including those services provided by IT within the organization. In VISUAL Message Center SLAs are monitored by SLA Analytics ThinAgents in ThinkServer. In Goals: any goal. In SmartConsole: an SLA can be represented by an SCP on the Service Model. In Reports, BSM Reporting based on SCPs in SmartConsole is essentially SLA Reporting.

Service Control Point (SCP) A type of folder that is used in Business Services Management (BSM) projects in VISUAL Message Center SmartConsole. Service Control Point (SCP) is a BSM concept and represents any critical element of a business, such as an application, a service, a business process, and more. SCPs have Business Values.

Severity SmartConsole determines the Severity of each event coming in from ThinkServer. Severity then translates into Criticalness via the rules the user sets forth (in SmartConsole) for the four states (of Criticalness): Harmless, Minor, Warning and Critical.

SharedObjects A repository for common data used by several VISUAL Message Center products (like calendars). It includes the PMDB statistical database which provides multidimensional statistical data, centralized access to BSM databases and forecasting functions.

SLA See Service Level Agreement.

SLA Analytics A group of ThinAgents that enable historical and real-time SLA events and reporting based on your SLAs. Sold separately. Product code Submodel-MSL.

SmartConsole VISUAL Message Center’s client console. It has a desktop interface as well as a Web interface (SmartConsole Web Client). SmartConsole correlates events from ThinkServer via NiceLink and can perform actions on them (according to filters), simply display them in the console, or manage them to show the status of your business in corresponding locations on the Service Model.

SmartConsole Branch A group of SmartConsole components shown in a dashboard exactly as they appear in a SmartConsole Service Model. In Dashboards the user can assign a display title, hyperlinks, and more for it.

SmartConsole Component Any item on the SmartConsole Service Model (a.k.a. tree). The types of components are: Basic Service Control Point, Service Control Point, Business Folder, Business View.

SmartConsole Web Client The Web-based client for VISUAL Message Center SmartConsole.

SNMP Agent A group of ThinAgents for Network and Printer health, TCP Connections, and more. Shipped with the Monitoring Engine.

Spool Files by Job Monitor Included (exclusively) with both the VISUAL Message Center Suite for Operations and VISUAL Message Center iSeries Base, it produces events when an iSeries job is using more spool files than allowed. Not sold separately.

Spool Files by Output Queue Monitor Included (exclusively) with both the VISUAL Message Center Suite for Operations and VISUAL Message Center iSeries Base, it produces events when there are more spool files per output queue than allowed. Not sold separately.

Spool Files by Size Monitor Included (exclusively) with both the VISUAL Message Center Suite for Operations and VISUAL Message Center iSeries Base, it produces events when it detects larger spool files than allowed. Not sold separately.

SQL Server Operations Agent Has ThinAgents for Availability (like the Logical Disks Usage ThinAgents) and Performance (like the CPU Abuse ThinAgents). Not included with the standard Monitoring Engine, this Product code Submodel-TOS.

T Tag A categorization of a report in Reports . . . like Security, ThinkServer, or BSM. Reports can have several tags at once. You can search for reports by clicking on tags.

Task A scheduled macro with a defined trigger(s) in Dashboards and Reports. Tasks appear in the Scheduled Items list.

ThinAgent Classes of monitors installed on ThinkServer. Many ThinAgents come standard with VISUAL Message Center ThinkServer, and many are available as will differ depending on what libraries you have on your server at the time of installation. A few examples are the Port, Ping, and SMTP Connect.

ThinkServer The server component of VISUAL Message Center ThinkServer. ThinkServer contains all the reusable logic and stores the configuration the user sets in the ThinkServer Configurator. Therefore the ThinkServer can run independently from the Configurator. The ThinkServer usually runs as a Windows Service on your machine.

ThinkServer Configurator The graphical client component of VISUAL Message Center ThinkServer. Here you can configure monitors, connect to one or more ThinkServers on your system, and view messages received from the ThinkServer. Note: a ThinkServer Configurator can be connected to more than one ThinkServer, and one ThinkServer may be connected to more than one ThinkServer Configurator.

Total Impact Cost The sum of the Business Values of affected SmartConsole components. Shows operators which problems are affecting the business most negatively.

Trigger A user-defined time-based definition that tells Dashboards or Reports when to run a macro. A component of Scheduler.

U Universal File Reader Agent Includes ThinAgents for Files and Folders. Reads logs. Comes standard with the Monitoring Engine.

Universal Transaction Agent For SAP, Citrix, ActiveX control-using browser apps, and more. Available as a Monitoring Engine add- on. Includes a script runner (on monitored system). Product code Submodel-TUC.

UNIX Operations Agent ThinAgents for AIX, HP-UX and Solaris file systems, processes, and system health. Sold separately. Product code Submodel-TSU.

UNIX Security Agent A group of ThinAgents sold to complement the Monitoring Engine. They supply ThinkServer with events based on User Activity and Management, Files Systems etc. Product code Submodel-TSU.

User Activity Monitor Included with all iSeries suites (not sold separately). Generates events if user inactivity breaches a threshold of time.

User Message Variables User-defined SmartConsole variables. They are per-message variables (they can have different values depending on the event). These variables can be used with ALEV.

V Variable Instance A VISUAL Message Center Goals concept. A single occasion whereby a desired variable (and its value, at that particular time) is passed to a Connector.

VISUAL Control Center Includes Submodel iSeries Performance Manager, the Submodel iSeries Performance Agent (a.k.a. VCW), VISUAL Support Pro, and VISUAL Control Performance Planner. No Monitoring Engine required. Product code VCC.

VISUAL Control for Jobs A single product. No Monitoring Engine required. Product code VCJ.

VISUAL Control for Pools A single product. No Monitoring Engine required. Product code VCP.

VISUAL Control LPAR Tuner Legacy product, code LPT.

VISUAL Control Performance Planner - All LPAR E. A single product. No Monitoring Engine required. However, either the Submodel iSeries Performance Agent or the VISUAL Message Center Suite for Operations is required. This product is also known as Performance Navigator. Product code VPP-IFL.

VISUAL Debugger 5250 A source-level interactive debugger that serves as support for batch and remote iSeries jobs. Product code VD.

VISUAL Message Center for iSeries/IBM i The VISUAL Message Center Monitoring Engine for iSeries. Product code Submodel-Mxx.

VISUAL Message Center iSeries Base Includes several iSeries agents. A Monitoring Engine add-on. Product code Submodel-BAS.

VISUAL Message Center Suite for Operations An iSeries Monitoring Suite. Includes VISUAL Message Center iSeries Base, the Submodel iSeries Performance Agent (a.k.a. VCW), VISUAL Support Pro, and Submodel iSeries Restricted State Monitor. Product code SUI-OPE.

VISUAL Remote Control Requires VISUAL Support Pro, but not the Monitoring Engine. Product code VSP-VRC.

VISUAL Security Suite - Security Package (VSS) Includes the Submodel iSeries Security Agent, Data Monitor for iSeries Express, and the Submodel iSeries SQL Agent. Product code SUI-SEC.

VISUAL Support Pro Available only with the VISUAL Message Center Suite for Operations. Inspects details of iSeries jobs. Product code VSP.

VMware Operations Agent A Monitoring Engine add-on, it has ThinAgents for Role Management, VMs, Hosts, Datastores, Logons/ Logoffs etc. Product code Submodel-TSV.

VMware Security Agent Sold separately. ThinAgents for Role Management, VMs, Hosts, Datastores, Logons/Logoffs etc. Product code Submodel-TSV.

W Web Availability and Response Time Agent Monitors that tell you how long Web transactions are taking on Consumer sites, their Availabilities and Contents, etc. Web 2.0-friendly. An End-User Experience Agent. Product code Submodel-TWS.

Web SmartConsole A Legacy product. The former Web interface for VISUAL Message Center SmartConsole (SmartConsole Web Client being the current one).

WebSphere Application Server Operations Agent

Agents for both Version 5.x and Version 6.x.The Agents includes ThinAgents for Thread pools, sessions, Enterprise Beans, and the J2C Connection Pool, etc. It is not shipped standard with the Monitoring Engine. Product code Submodel-TOW.

WebSphere MQ Operations Agent Safeguards Web applications. Includes several ThinAgents that create events about MQ Channels, the Queue Manager, and message traffic, among others. Product code Submodel-TOQ.

Wide Table The type of table in VISUAL Message Center Dashboards that typically includes several hosts (aligned vertically, and several variables (aligned horizontally).

Windows Operations Agent Allowing deep insight into Windows Server Operations (Availability, Performance, Compliance etc.), this large collection of ThinAgents, which is sold apart from the Monitoring Engine, also delivers events about Services, Terminal Services, and File Systems. Product code Submodel-WAD.

Windows Performance Agent VISUAL Message Center Windows Performance Agent is a standalone product with code VCW-WIN. Does not require Monitoring Engine.

Windows Security Agent A collection of ThinAgents, this Agent provides events based on Security: User/Computer, File, Domain Policy/Trust, Active Directory, and Event Log events appear in SmartConsole Business Views and predefined reports can be generated in Reports.

WMI Generic Agent A ThinkServer staple, the ThinAgent runs WMI queries against as many local/remote Windows systems as you desire and returns provides disk, service, process, system configuration and Event Log events.

X XML Generic Agent Included with the Monitoring Engine, this ThinAgent reads any XML log/file anywhere to deliver events concerning service applications.

Index

Alarm Log ...... 176 A Show ...... 17 Alarms AccessServer ...... 38 Activating and de-activating ...... 175 Action Sets Creating dependencies ...... 172 Execute for all messages ...... 27 Executing ...... 90, 126 Exporting or Importing ...... 177 Exporting or Importing ...... 178 Filters ...... 151 Setting ...... 170 Getting the most out of them ...... 179 Toolbar button ...... 17 Hotkeys ...... 231 Add a business view filter to an alarm, ALEV Overview ...... 150 function ...... 218 Post-Actions ...... 174 Adding a reason to the criticalness change, Pre-Actions ...... 173 ALEV function ...... 217 Protecting with passwords ...... 151 Address Book ...... 31, 156 Repetitions ...... 174 Saving or exporting configurations ...... 177 Exporting or Importing ...... 178 Toolbar button ...... 17 Adjust List Alarms tab, options ...... 27 Toolbar button ...... 20, 24, 90 Alerts Advanced ALEV Filter Editor ...... 148 Customized for Performance Agent ...... 203 Advanced Service Functions ...... 220 Sending options ...... 210 Agent Code, filtering by ...... 131 ALEV Filter Editor, Advanced ...... 148 Agent Subscriptions ...... 126 ALEV functions ...... 31 Agents Specific to SmartConsole ...... 216 Changing status ...... 33 ALEV Logical Expression eValuator ...... 216 Alarm Actions Analysis Pane, overview ...... 97 Annotate in the Windows Event Log ...... 159 Annotate in the Windows Event Log, alarm action Audible Alarm - sound ...... 158 ...... 159 E-mail Action ...... 154 Arrays, retrieving using an ALEV function ...... 220 Execute a DLL function ...... 162 Execute a PC Program ...... 158 Audible Alarm - sound, alarm action ...... 158 Execute a SNMP Trap ...... 162 Automating operations ...... 205 Execute an OS/400 Command sequence ...... 163 Reply to message ...... 166 Send a message to an Escalation List ....169 Send a Remote Message (Net Send B Function) ...... 168 Setting ...... 153 Background images, of an Enterprise View ...105 Show a window, Visual ...... 161 SMS ...... 167 Basic Service Control Points ...... 62 BSM Engine ...... 188

Business List hotkeys ...... 229 Views ...... 122 Business Network Category, filtering by ...... 139 Saving structure to RTF ...... 82 Cause and Effect ...... 187 Business Network Column ...... 72 Change Menu ...... 21 Overview ...... 72 Changing Criticalness, ALEV function ...... 217 Show / Hide ...... 23 Chat, open ...... 16, 24, 90 Business Process Modeling ...... 182 Colors Business Services Management Editing ...... 77 Business Values ...... 184 How to color code pending messages ...... 19 Cause and Effect ...... 187 In the Business View, toolbar button ...... 17 Impact Analysis ...... 183 Columns License ...... 191 Adding and removing ...... 90 Overview ...... 181 Adjusting ...... 24, 90 Problem Root Cause ...... 183 Filters ...... 90, 125 Reporting ...... 188 User columns ...... 91 Service Control Point ...... 183 Command Prompting ...... 164 Business Shortcuts Pane ...... 82 Component, Problem Root Causes Pane ...... 98 Show / Hide ...... 22 Computer Name, filtering by ...... 139 Business Tree hotkeys ...... 229 Configuration Files Business Values ...... 184 Exporting ...... 20 Adding ...... 184 Importing ...... 20 Formulas ...... 187 Real-Time Impact Analysis Pane ...... 99 Connection time-out ...... 25, 208 Retrieving for a Service Control Point using Connections an ALEV function ...... 220 Menu ...... 22 Retrieving from the impacted Service Remove ...... 16 Control Point using an ALEV function ...220 Select ...... 15 Using ...... 185 View Current ...... 15 Business Views Console Category, filtering by ...... 141 Colors ...... 17 Console Message ID, filtering by ...... 141 Creating ...... 73 Definition ...... 59 Console Message Type, filtering by ...... 141 Exporting ...... 79, 85 Console Mode ...... 209 Filters ...... 17 Convert SID to an Account Name, ALEV function Importing ...... 79, 85 ...... 219 Pasting ...... 73 Criticalness Problem Root Causes Pane ...... 98 Style, saving and loading ...... 96 Management ...... 62, 75 Transfer structure to Enterprise View ...... 82 Management, Business Service Management ...... 187 Propagation configuration ...... 62 Reset ...... 86 Criticalness Range, filtering by ...... 136 C Custom Logical Condition, filtering by ...... 134 Custom Rules, criticalness of folder ...... 64 Calendars Exporting or Importing ...... 178 calendars ...... 50 create ...... 50 D import ...... 53 range sets ...... 47 Data Dictionary ...... 92 Capture with VISUAL Message Center iSeries Support Agent ...... 16, 24 Using to add message variables to commands ...... 164 Capture with VMC iSeries Support Agent ...... 89 Data from previous sessions ...... 25 Categories Date Filters ...... 126 In Enterprise Views ...... 118 Managing ...... 123 Debug with VISUAL Message Center Debugging Using to filter Enterprise Views ...... 121 Agent ...... 16, 24, 89 Viewing which are assigned to Enterprise Debugging Agent ...... 16, 24

Dependencies, creating for alarms ...... 172 Enterprise Views ...... 115 DLL Actions ...... 33 Documentation, using ...... xiii F

E File menu ...... 20 Filter Configuration ...... 127 E-mail Action, alarm action ...... 154 Console tab E-mail Alarms Console Category ...... 141 Console Message ID ...... 141 Templates ...... 157 Console Message Type ...... 141 E-mail Message Support, integrating into system General tab ...... 130 applications ...... 206 Agent Code ...... 131 Enterprise Network Criticalness Range ...... 136 Overview ...... 102 Custom Logical Condition ...... 134 Search in the Message Text ...... 133 Enterprise View Severity Range ...... 136 Hotkeys ...... 230 System ...... 130 Enterprise Views User Name ...... 133 When ...... 133 Adding and removing icons ...... 106 System i tab ...... 136 Categories ...... 118 Queue ...... 137 Creating ...... 105 Search in the Second Level ...... 137 Criticalness filtering ...... 116 ThinkServer tab Customizing ...... 105 Category ...... 139 Customizing how they are displayed ...... 104 Computer Name ...... 139 Filter Panel ...... 117 Event ID ...... 139 Icons ...... 106, 109 Event Log Type ...... 140 Importing and Exporting ...... 115 Source Name ...... 139 Links ...... 108 User Domain ...... 139 Multiple Copy ...... 110 Windows Message Type ...... 140 Opening ...... 104, 110 Renaming ...... 107 Filter Panel, Enterprise Views ...... 117 Using ...... 116 Filter Search button, Enterprise Views ...... 118 Enterprise Views panel ...... 104 Filters Escalation Lists ...... 169 Agent Subscriptions ...... 126 Event ID, filtering by ...... 139 Column Filters ...... 125 Column filters ...... 90 Event Log Type, filtering by ...... 140 Custom ...... 134 Event tab, messages ...... 87 Date ...... 126 Exclusion conditions Display Filters ...... 127 Creating ...... 127 Editing ...... 77 Groups ...... 125 exclusion range How to configure ...... 141 add exclusion range ...... 50 Overview ...... 124 Execute a DLL Function, alarm function ...... 162 Speed Filters ...... 94, 125 Execute a PC program, alarm action ...... 158 Filters for Alarms ...... 151 Execute a SNMP Trap, alarm action ...... 162 Filters in this Business View ...... 127 Execute an action set, ALEV function ...... 218 Toolbar button ...... 17 Execute an OS/400 Command Sequence, alarm Folders action ...... 163 Creating ...... 73 Exit Criticalness ...... 62 Toolbar button ...... 20 Defining the type of ...... 75 Definition ...... 61 Export a Business View, ALEV function ...... 218 Pasting ...... 73 Export Business Views to XLS, XML, or HTML Fonts Format, ALEV function ...... 219 Changing in an Enterprise View ...... 105 Exporting Changing in SmartConsole ...... 21 Business Views ...... 79, 85 Formulas for Business Values ...... 187 Configuration Files ...... 20

Global Variables Creating and defining ...... 195 K Example of ...... 197 Global Variables tab, messages ...... 88 Kernel Supervisor Monitor ...... 28 Grid, show ...... 94 Group filters ...... 125 L

H Last State Change, Problem Root Causes Pane . 98 Hide Speed Filters ...... 94 Last State Change, Real-Time Impact Analysis Pane ...... 100 Hotkeys ...... 229 LDAP Configuration ...... 31 HTML, saving to ...... 95 Least critical Child Component, criticalness of folder ...... 62 Linking Enterprise Views ...... 108 I Links to websites from Enterprise Views ...... 109 List menu ...... 23

Icons Adding and removing in an Enterprise View . 106 Change size ...... 85 M Changing in an Enterprise View ...... 105 Renaming in an Enterprise View ...... 107 Menu bar, overview ...... 20 Setting ...... 78 Menus Impact Type, Problem Root Causes Pane ...... 98 Change ...... 21

Impact Type, Real-Time Impact Analysis Pane Connections ...... 22 ...... 100 File ...... 20 Impacting Since, Problem Root Causes Pane .98 List ...... 23 Impacting Since, Real-Time Impact Analysis Tools ...... 30 Pane ...... 100 View ...... 22 Window ...... 25 Importing Message Grid ...... 86 Business Views ...... 79, 85 Configuration Files ...... 20 Adjusting ...... 20, 24, 90 Enterprise Views ...... 116 Printing ...... 19 Refresh ...... 16, 25, 82 Including an Event ID in a Business View filter, ALEV function ...... 218 Message List Inclusion conditions Refresh time ...... 25 Creating ...... 127 Message Recollection ...... 25 Interactive and Batch monitors ...... 28 Message Text Internal IDs, retrieving using an ALEV function Viewing messages ...... 23, 89 ...... 220 Message Variables, user defined ...... 21 iSeries Support Agent Messages Capturing with ...... 16, 24, 89 Color coding ...... 126 Using SmartConsole with ...... 200 Event tab ...... 87 Execute alarms for all ...... 27 Global Variables tab ...... 88 Groups ...... 93 Hide ...... 89 J Maximum number stored in memory ...... 25 Printing ...... 97 Jobs Retrieving from Server ...... 33

Retrieving from the last change of state from Performance Agent

a Business View using an ALEV function Using SmartConsole with ...... 202 ...... 220 Persistent Variables ...... 196 Select all ...... 89 Sort in chronological order ...... 97 Play button ...... 35 Storage ...... 123 Post Actions System Properties ...... 89 Example of ...... 197 System properties ...... 23 Text size ...... 19, 23 Post-Actions Unhide ...... 89 For alarms ...... 174 User Defined Variables tab ...... 88 Potential Impact, Problem Root Causes Pane .98 Variables tab ...... 87 Potential Impact, Real-Time Impact Analysis Viewing ...... 23, 89 Pane ...... 100 Messages List Pre-Actions Hotkeys ...... 230 For alarms ...... 173 Modify resulting criticalness ...... 67 Preprocess Filter List Window ...... 146 Monitors Preprocess List Checking ...... 209 Hierarchy ...... 147 Types of ...... 28 Menu option ...... 21 Monitors tab, options ...... 28 Preprocesses Most critical Child Component, criticalness of Creating ...... 147 folder ...... 62 Expression List ...... 147 Multiple Copy ...... 74 Filters ...... 147 Importing and Exporting ...... 115 Preprocessing Using to create Enterprise Views ...... 110 Overview ...... 146 Pre-processing Tips ...... 196 Print Business Network structure ...... 82 N messages ...... 97 Toolbar button ...... 19 Net Send Function ...... 168 Problem diagnosis, using VISUAL Message New User Creation, using UNIX/Linux ...... 223 Center for ...... 203 Non-resilient mode ...... 209 Problem Duration, Problem Root Causes Pane ... 98 Notifier ...... 167 Problem Duration, Real-Time Impact Analysis Pane ...... 100 Problem Root Causes Pane ...... 98 O Using with Business Values ...... 185

Options Alarms Tab ...... 27 Q Monitors Tab ...... 28 Server tab ...... 25 Trace Tab ...... 29 Queue, filtering by ...... 137 Options menu ...... 25 R P range set Passwords create ...... 47 Changing ...... 34 minutes ...... 48 remove time periods ...... 48 Pause the console ...... 35 Real Impact, Real-Time Impact Analysis Pane Per Message Variables ...... 100 Creating and defining ...... 194 Real-Time Impact Analysis Pane ...... 99 Example of ...... 196

Using with Business Values ...... 185 Show All in the Real-Time Impact Analysis Pane Real-Time Performance Monitoring ...... 202 ...... 99, 101 Refresh Message Grid ...... 16, 25, 82 Simple Redundancy, criticalness of folder ...... 62 Remote Message, alarm action ...... 168 Smart Reconnect ...... 25, 208 Remove Connections ...... 16 SmartConsole Repetitions, alarms ...... 174 Starting ...... 11 Reply to Message, alarm action ...... 166 SMS Reports ...... 188 alarm actions ...... 167 Alerts, sending options ...... 210 Resilient mode ...... 209 Define lists of recipients for ...... 169 Alarm repetitions ...... 174 SMS and E-mail Message support, integrating Response times, Performance Agent ...... 202 into System applications ...... 206 Retrieve an LDAP Attribute, ALEV function ...218 SMTP server Retrieve Criticalness, ALEV function ...... 216 Configuring for e-mail alarms ...... 154 Retrieve Messages from Servers ...... 33 SMTP Server Lists Retrieving using ALEV functions ...... 220 Exporting or Importing ...... 178 Sort messages in chronological order ...... 97 Source Member Explorer ...... 17, 24 Source Name, filtering by ...... 139 S Special Days Exporting or Importing ...... 178 Saving Speed Filters ...... 94, 125 Alarm configurations ...... 177 Spool File Output To various formats ...... 95 Retrieving from an iSeries command ...... 165 SCP Name, Real-Time Impact Analysis Pane ..... Sending by e-mail ...... 166 100 Starting VMC SmartConsole ...... 11 Search in the Message Text, filtering by ...... 133 Stop button ...... 35 Security ...... 38 System Explorer ...... 17, 24 AccessServer ...... 38 System i Command action fails ...... 175 Security Alerts System Properties Using UNIX/Linux ...... 223 Of messages ...... 23 Security alerts system Properties Using VISUAL Message Center for ...... 205 Of messages ...... 89 Select Connections ...... 15 System, filtering by ...... 130 Send a Message to an Escalation List, alarm action ...... 169 Send a Remote Message, alarm action ...... 168 Server tab, options ...... 25 T Service Control Point Detail ...... 190 Folder type ...... 183 Tango/04 Listing ...... 189 contacting ...... 232 Overview ...... 189 Templates Service Control Points, in the Problem Root For e-mail alarms ...... 157 Causes Pane ...... 98 Text Messages See SMS Service Control Points, in the Real-Time Impact Thumbtack symbol ...... 97 Analysis Pane ...... 100 Toolbar Set a Business Value for a Service Control Point, ALEV function ...... 221 Definitions ...... 15 Show / Hide ...... 22 Set Criticalness ...... 76 Tools menu ...... 30 Set Icon, ALEV function ...... 216 Total Impact Value, Problem Root Causes Pane Severity Range, filtering by ...... 136 ...... 98 Shortcut, adding to Business Shortcuts Pane ..75 Trace ...... 29 Show All in the Problem Root Causes Pane ....99 Trace tab, options ...... 29

Transfer structure to Enterprise View ...... 82 Typographical conventions ...... xiii Z

Zoom U Toolbar button ...... 19, 23

User Columns ...... 91 User Defined Functions ...... 197 User Defined Variables Tips ...... 196 User Defined Variables tab, messages ...... 88 User Domain, filtering by ...... 139 User Name, filtering by ...... 133 Using UNIX/Linux Messages at the SmartConsole ...... 223

Variables User defined message variables ...... 21 User defined, tips ...... 196 Variables tab, messages ...... 87 Verify Calendar Date, ALEV function ...... 218 View Current Connections ...... 15 View menu ...... 22 VISUAL Message Center Definition ...... 2 How it works ...... 2 VISUAL Message Center as a Service ...... 207

Web SmartConsole ...... 212 Websites, links from Enterprise Views ...... 109 When, filtering by ...... 133 Window Menu ...... 25 Windows Message Type, filtering by ...... 140 Windows NT / 2000 ...... 207 Windows Registry Size, increasing ...... 225

XLS, saving to ...... 96 XML, saving to ...... 95

List of Figures

Chapter 1. Introduction

Figure 1 – SmartConsole allows you to stay in control of your business processes and IT applications on a wide variety of platforms ...... 1

Figure 2 – VISUAL Message Center overview; SmartConsole is a Correlation Layer product...... 2

Figure 3 – Preprocessing within the SmartConsole allows for powerful automated dependency mapping ...... 4

Figure 4 – Manipulation of your Business Tree is almost instantaneous, no matter the number of components ...... 4

Figure 5 – Enterprise Views in SmartConsole ...... 5

Figure 6 – SmartConsole alarm processes...... 6

Figure 7 – Events are screened through several filters, and can affect many SmartConsole features...... 7

Figure 8 – Event flow in SmartConsole...... 8

Chapter 2. Starting VISUAL Message Center SmartConsole

Figure 9 – Selecting systems to monitor from NiceLink ...... 11

Figure 10 – Select any one of the ThinkServers if they share a database...... 12

Figure 11 – Selecting two ThinkServers to monitor when setting up SmartConsole, because the ThinkServers each have their own separate database...... 12

Chapter 3. VISUAL Message Center SmartConsole

Figure 12 – SmartConsole’s main message console – Business Network view...... 14

Figure 13 – SmartConsole Toolbar is located at the top of the Window ...... 15

Figure 14 – Viewing your current connections ...... 16

Figure 15 – Example of an alarm log ...... 17

Figure 16 – Configure a color filter for a Business View to distinguish important messages at a glance ...... 18

Figure 17 – Example of a Business View with a color filter...... 19

Figure 18 – Menu Bar ...... 20

Figure 19 – The File Menu includes the functions Export Configuration File, Import Configuration file, Print and Exit...... 20

Figure 20 – The Change menu ...... 21

Figure 21 – The Connections Menu...... 22

Figure 22 – The View Menu ...... 22

Figure 23 – The List Menu ...... 23

Figure 24 – The Window Menu ...... 25

Figure 25 – The Options Menu ...... 25

Figure 26 – Options window: Options for SmartConsole ...... 25

Figure 27 – Options Menu - BSM Tab ...... 26

Figure 28 – Options menu - Alarms tab ...... 27

Figure 29 – Options menu - Precycle/Postcycle tab ...... 28

Figure 30 – Options menu - Monitors tab ...... 28

Figure 31 – Options Menu - Trace tab ...... 29

Figure 32 – Changing the current SmartConsole language...... 30

Figure 33 – Tools Menu ...... 30

Figure 34 – SMTP server configuration window ...... 31

Figure 35 – LDAP configuration window ...... 32

Figure 36 – Agents Subscription window ...... 33

Figure 37 – Configuring Criticalness ...... 34

Figure 38 – Tools: Manage Roles window ...... 34

Figure 39 – Status bar in play mode - click the pause button to pause the console...... 35

Figure 40 – System tray icon as displayed in system tray ...... 35

Chapter 4. Security

Figure 41 – AccessServer integration with Tango/04 applications...... 38

Figure 42 – Manage Security: General options...... 40

Figure 43 – Manage Security: Connections options ...... 40

Figure 44 – Manage Security: Tools options...... 41

Figure 45 – Manage Security: Message Retrieval options...... 42

Figure 46 – Manage Security: Business Tree options ...... 42

Figure 47 – Manage Security: Enterprise Views options ...... 43

Figure 48 – Manage Security: Enterprise View category options. Notice these are the default settings for all categories...... 44

Figure 49 – The Event Viewer window displays audited events ...... 45

Chapter 5. Calendars

Figure 50 – Creating calendars in SmartConsole is done online via VISUAL Message Center SharedObjects. The list of calendars appears in the upper right of the browser its own toolbar ...... 46

Figure 52 – Add hours to a calendar...... 48

Figure 53 – To remove the time slot 15:00 to 17:00, select the range 15 to 16 and click Remove from the calendar ...... 48

Figure 55 – Range Sets ...... 49

Figure 56 – Exclusion range for power outage on September 1, 2011 between 14:00 and 16:00 ...... 50

Figure 57 – Exclusion Ranges list...... 50

Figure 58 – Creating a calendar in SmartConsole ...... 51

Figure 59 – Initial range set: Business Hours ...... 52

Figure 60 – Notice that the second range set for summer hours appears above the original business hours range set. Also notice the field Mask at the top right of the new range set...... 52

Figure 61 – Components outside of an Activity Calendar show a “waiting” clock on their icon ...... 54

Figure 62 – About to assign an Activity Calendar to a folder ...... 54

Figure 63 – Selecting an Activity Calendar ...... 54

Figure 64 – Accessing calendars in SmartConsole ...... 55

Figure 65 – Creating the calendar ‘Security audit’ online (in SmartConsole) via SharedObjects ...... 55

Figure 66 – Selecting the calendar in Reports as a parameter for a report template ...... 55

Figure 67 – About to run the (SmartConsole) Component Brief Overview report using another calendar than what is defined for the report template...... 56

Figure 68 – Accessing calendars in SmartConsole ...... 56

Figure 69 – Creating a ‘Test Calendar’ (in SmartConsole) online via SharedObjects ...... 57

Figure 70 – The ‘Test Calendar’ appears in Goals, and we can select it when creating a goal template ...... 57

Chapter 6. Business Network

Figure 71 – Business Network view of VISUAL Message Center’s main message console ...... 59

Figure 72 – The selected Business View is of substate type Failures ...... 60

Figure 73 – Assigning a business substate to a Business View ...... 60

Figure 74 – All of the existing substates within a folder are shown when the folder is selected. In this example, we can tell that our “Security” folder has child components of four different substates...... 61

Figure 75 – Left, a Business View icon; Right, a Folder icon...... 61

Figure 76 – Left, folder icon; center, Basic Service Control Point icon, right, Service Control Point icon ...... 62

Figure 77 – A selected Business Folder’s criticalness setting is given at the upper right of the browser panel. In this example, the folder is assigned a Global Criticalness type (Priority on Availability substate) ...... 63

Figure 78 – Criticalness propagation according to different Criticalness Evaluation options. In the example above, the Firewalls and switches in each of the offices in Barcelona have failed. However each folder shows a different state due to criticalness propagation rules: 01. Paseo de Gracia is red because it is set to Most Critical Child Component; 02. Diagonal is yellow because it is set to Simple Redundancy (more than 50% of the child components are critical); 03. Gran Via is blue because a custom rule is applied; 04. Meridiana is green because the Criticalness Propagation is set to Least Critical Child Component ...... 64

Figure 79 – Simple Redundancy criticalness management. The folder setting depends on the percentage of critical Business Views...... 64

Figure 80 – Custom Rules ...... 65

Figure 81 – A set of custom rules ...... 65

Figure 82 – Example tree...... 66

Figure 83 – example of Custom Rules used ...... 66

Figure 84 – Case 1...... 66

Figure 85 – Case 2...... 67

Figure 86 – In this example the Performance substate is “minor” because the worst Performance Business View is “minor.” The Business substate is “critical” because the worst Business Business View is in “critical”...... 68

Figure 87 – The Global Criticalness Calculation Configuration window...... 69

Figure 88 – The folder selected at left displays the criticalnesses of its children components, which include four substates. The folder is “critical” because one of its components (of substate Performance) is “critical” ...... 69

Figure 89 – In this example, folder criticalness is not “critical” because priority has been given to the Availability substate, which is not “critical”. The Business Folder has acquired a criticalness of “warning” because one of its components (the Failures substate component) is “critical,” and one level of criticalness down from “critical” is “warning”...... 70

Figure 90 – This type of alarm lets you define which substates SmartConsole takes into account when a folder’s components start to change criticalness ...... 71

Figure 91 – Business Network menu ...... 72

Figure 92 – Multiple Copy: Search and Replace window...... 74

Figure 93 – Select the date from when you want to refresh criticalness...... 76

Figure 94 – Criticalness Configuration options ...... 77

Figure 95 – Set icon: example of the default icon (round with arrow) and a security icon (round with emergency vehicle)...... 78

Figure 96 – Set Icon...... 78

Figure 97 – Export to: Selection window for exporting a Business View. A similar window opens when you import a Business View...... 80

Figure 98 – Results of different import methods ...... 80

Figure 99 – Indicate what action to take if a Business View with this name already exists...... 81

Figure 100 – Business Shortcuts Pane...... 83

Figure 101 – The Shortcut Properties window appears when you select New from the menu...... 83

Figure 102 – 1st and 2nd copies of the same shortcut (Delivery UK) in the Business Shortcuts pane ..84

Figure 103 – Large and Small Icons in Business Shortcuts...... 85

Figure 104 – Importing a Business View and its configurations...... 86

Figure 105 – Event tab in the Message window...... 87

Figure 106 – Variables tab in the Message window...... 87

Figure 107 – User Defines Variables tab in Message window...... 88

Figure 108 – Global variables in the Message window...... 88

Figure 109 – System properties of the system where the event took place...... 89

Figure 110 – Column filters ...... 90

Figure 111 – Available columns ...... 91

Figure 112 – Configure User Column List...... 91

Figure 113 – Column Properties window ...... 92

Figure 114 – Data Dictionary ...... 92

Figure 115 – Select Columns...... 93

Figure 116 – Messages grouped by severity: Here messages for Severity less than 50 are collapsed and the others are expanded. Note that the column heading by which you grouped the messages is located in the gray area at the top of the message grid ...... 93

Figure 117 – Message grid with multiple grouping criteria: in this example grouped first by severity and then by system date. Note both column headings are located in the gray area above the message grid and the line to indicate the relationship between the two columns ...... 94

Figure 118 – Speed filters as displayed above the Message Grid...... 95

Figure 119 – Example of resulting HTML file ...... 95

Figure 120 – Example of resulting XML file ...... 96

Figure 121 – Example of resulting Excel file ...... 96

Figure 122 – Problem Root Causes pane...... 98

Figure 123 – The Show All and Show low potential problems check boxes are located in the top right corner of the Problem Root Causes Pane ...... 99

Figure 124 –Real-Time Impact Analysis Pane. In the example above we can see that the router problems in the London - Picadilly Circus branch have been impacting on three Service Control Points...... 100

Chapter 7. Enterprise Network

Figure 125 – Enterprise Views. In the first Enterprise View the icon for the 08.Branches folder is red (critical), indicating a problem. We can also see that while the UK and France folders are green (harmless), the overall folder for Spain is red, suggesting the branches problem is emanating from Spain. Clicking on the Spain folder opens an Enterprise View showing the whole of Spain, where we can see the problem is in Barcelona, a link to a new Enterprise View for Barcelona further narrows down the problem to a specific branch and finally we can see the cause of the problem is a router within this branch...... 103

Figure 126 – SmartConsole - Enterprise Network tab ...... 103

Figure 127 – Enterprise View - Properties menu ...... 105

Figure 128 – Enterprise View - Options menu ...... 105

Figure 129 – Customizing the icon label Font and Background...... 106

Figure 130 – Select elements to add to the Enterprise View from the Business Tree ...... 106

Figure 131 – Select elements using the Business List...... 107

Figure 132 – Enterprise View icons are added by default, with names (and therefore with captions). Right-click in the Enterprise View to open the context menu...... 108

Figure 133 – Right-click an icon and select Create Link to link to another Enterprise View available from the list...... 109

Figure 134 – Right-click an Enterprise View icon to open the context menu. You can create, open and edit links from this menu to other Enterprise Views or web pages ...... 110

Figure 135 – Each folder contains three Business Views following the same naming convention ...... 112

Figure 136 – Create the first Enterprise View and add the Enterprise View icons...... 112

Figure 137 – Right-click the Enterprise View and select Multiple Copy to open the Search and Replace window ...... 113

Figure 138 – Enter the text to be replaced in the duplicated Enterprise Views...... 113

Figure 139 – The new Enterprise Views in the Enterprise Views window ...... 114

Figure 140 – Three new Enterprise Views have been created for the branches in: Diagonal; Gran Via; and Meridiana. The Enterprise View icons for monitoring the firewall, router and switches in Paseo de Gracia have been replaced by Enterprise View icons for monitoring the firewall, router and switches in Diagonal, Gran Via and Meridiana...... 114

Figure 141 –Export Enterprise Views Options window. In the example above, Communications has been selected from the list of categories and all Enterprise Views in the Communications category appear in the column below...... 115

Figure 142 – Importing Conflict options ...... 116

Figure 143 – Business View information displayed in an Enterprise View. Rest on an icon and a context menu appears displaying link information...... 117

Figure 144 – Criticalness filter...... 117

Figure 145 – Filter Search button...... 118

Figure 146 – Enterprise View Categories window. Select the check boxes to assign categories to an Enterprise View...... 119

Figure 147 – Enterprise View category security; Note that you can control the default security for all categories or just the security for the selected category...... 120

Figure 148 – You can deny permission to users that don’t need to see any of the Enterprise Views in a whole specific category...... 120

Figure 149 – Using Categories. In the example above, we are filtering on the Communications and UK categories; therefore only the Enterprise Views that have been assigned to both categories are visible in the Enterprise Views panel...... 121

Figure 150 – Category context information. Rest on an Enterprise View (left hand image) or a category (right hand image) to see category assignments. In the example above we can see that there are five Enterprise Views assigned to the Branches category. The Branches - Spain Enterprise View is one of these...... 122

Figure 151 – Category information for several selected Enterprise Views. In this example we can see that the selected views belong to both the Branches and Countries categories...... 123

Chapter 8. Working with Console Filters

Figure 152 – Speed filters ...... 125

Figure 153 – Message Grid with multiple grouping criteria: in this example grouped first by Severity and then by Server Date. Note both fields by which the messages are grouped are located in the dark gray area above the message grid and the line to indicate the relationship between them...... 125

Figure 154 – Column filters ...... 125

Figure 155 – Display Filter ...... 127

Figure 156 – Hyperhashing Filters ...... 129

Figure 157 – Entering the Constant Value “SADAMS” ...... 130

Figure 158 – Filters - General tab ...... 130

Figure 159 – Advanced ALEV Filter Editor ...... 134

Figure 160 – Display Formatted Message Text screen ...... 135

Figure 161 – Display Field Data screen ...... 135

Figure 162 – Filters - System i Tab ...... 137

Figure 163 – System i Filters - Message Type...... 138

Figure 164 – Filters - ThinkServer Tab ...... 139

Figure 165 – Filters - Console Tab...... 140

Figure 166 – System(s) to include ...... 141

Figure 167 – Subsystem(s) to include...... 142

Figure 168 – Display Filter window - deselect the filter...... 143

Figure 169 – Import & Export menu options ...... 143

Figure 170 – Saving Business View messages to HTML, XML, or XLS ...... 144

Chapter 9. Preprocessing

Figure 171 – Preprocess Filter List ...... 146

Figure 172 – Expression List window...... 148

Figure 173 – Advanced ALEV Filter Editor ...... 148

Chapter 10. Alarms

Figure 174 – Alarm Configuration dialog box...... 151

Figure 175 – Filters - Advanced Tab (alarms only) ...... 152

Figure 176 – Alarm action configuration ...... 153

Figure 177 – Configuring e-mail support in an alarm ...... 154

Figure 178 – Sending test e-mail ...... 155

Figure 179 – SMTP server list...... 156

Figure 180 – E-mail address book window ...... 157

Figure 181 – Default message template in the Template configuration window...... 157

Figure 182 – Working with PC program alarms ...... 159

Figure 183 – Working with Windows event log annotations...... 160

Figure 184 – Working with visual alarms ...... 161

Figure 185 – Working with iSeries command actions ...... 163

Figure 186 – Editing iSeries command actions...... 164

Figure 187 – Using command prompting and entering variables in iSeries commands ...... 164

Figure 188 – Retrieving spool file output from an iSeries command...... 165

Figure 189 – Automatically reply to a message ...... 166

Figure 190 – SMS alarm configuration...... 167

Figure 191 – Configuring Net Send function ...... 168

Figure 192 – Receiving a Net Send message...... 169

Figure 193 – Configuring action sets ...... 171

Figure 194 – Adding action sets to alarm configuration ...... 172

Figure 195 – Advanced ALEV Filter Editor ...... 173

Figure 196 – Advanced alarm options ...... 174

Figure 197 – Working with configured alarms...... 176

Figure 198 – The alarm log displays all alarms executed during current session...... 176

Figure 199 – alarm log options...... 177

Figure 200 – Exporting or importing alarms ...... 178

Figure 201 – Select alarms to export ...... 179

Chapter 11. Business Services Management (BSM)

Figure 202 –This image portrays the example explained above: The Barcelona - Paseo de Gracia branch has lost network connections, due to a problem with the branch router. The problem occurred at 9:00:05 AM and internet connections for this branch have been down for 4 minutes and 12 seconds so far. Meanwhile the Picadilly Circus branch in London has been experiencing similar problems for the last 1 minute and 25 seconds. By examining the Total Impact Cost column, an operator can instantly see that the network problems in London pose a greater threat to the business than those in Barcelona and can therefore prioritize further actions to ensure the Paris problem is resolved first...... 181

Figure 203 – Business service modeling capabilities enable the creation of custom Business Views for purposes such as demonstrating regulatory compliance. The figure shows a Sarbanes- Oxley compliance console implemented at an American manufacturing company’s iSeries...... 183

Figure 204 – Total Impact Cost. In this example, events in the Problem Root Causes pane have been ordered by Total Impact Cost so that the highest value appears at the top of the list. We can see that the router problem in Barcelona is not as serious as that in Paris which will need to be prioritized. This is because the Paris branch has been given a higher Business Value than Barcelona because it is a larger branch with more customers...... 184

Figure 205 – Add a Business Value to a Service Control Point ...... 185

Figure 206 – Problem Root Causes pane...... 185

Figure 207 – Real-Time Impact Analysis pane - 03. Switch_New York...... 186

Figure 208 – Real-Time Impact Analysis pane - 01. Router_Picadilly Circus...... 186

Figure 209 – Only when the Impact Type is Real is a Business Value displayed...... 187

Figure 210 – BSM report...... 191

Figure 211 – BSM Key Management ...... 192

Chapter 12. User-Defined Variables

Figure 212 – User Defined Per Message Variables window...... 194

Figure 213 – Configuring a user-defined variable ...... 194

Figure 214 – Naming a user-defined variable ...... 194

Figure 215 – User Defined - Global Variables window ...... 195

Figure 216 – Configuring a global user-defined variable ...... 195

Figure 217 – Configuring a persistent global user-defined variable...... 196

Figure 218 – Persistent variables indicated by a different icon...... 196

Chapter 13. Getting the Most Out of SmartConsole

Figure 219 – Capturing another job with iSeries Support Agent ...... 201

Figure 220 – VISUAL Message Center Performance Agent – real time iSeries performance monitoring ...... 202

Figure 221 – VISUAL Message Center Performance Agent displays response time information ...... 203

Figure 222 – A WRKSYSSTS command can be used to collect diagnostic information ...... 204

Figure 223 – Sending and replying to messages via SMS or e-mail ...... 206

Chapter 14. SmartConsole High Availability Options

Figure 224 – Smart Reconnect configuration...... 208

Figure 225 – Configure alerts in case the message monitors fail ...... 209

Figure 226 – Console mode...... 210

Chapter 15. SmartConsole Web Client

Figure 227 – VISUAL Message Center SmartConsole Web Client ...... 212

Appendix A: Automating the Export of SmartConsole Configuration Files

Figure 228 – Add the necessary command in the text file ...... 213

Figure 229 – Add Scheduled Task Wizard...... 214

Figure 230 – Select the batch file to run ...... 214

Figure 231 – Scheduled Task frequency ...... 214

Figure 232 – Scheduled Task authentication...... 215

Appendix B: ALEV Logical Expression eValuator

Appendix C: Increasing Windows Registry Size

Appendix D: Disk-Usage & Message-Processing Tests

Appendix E: Hotkeys

Appendix F: Contacting Tango/04

Tango/04 Computing Group is one of the leading developers of systems management and automation software. Tango/04 software helps companies maintain the operating health of all their business processes, improve service levels, increase productivity, and reduce costs through intelligent management of their IT infrastructure.

Founded in 1991 in Barcelona, Spain, Tango/04 is an IBM Business Partner and a key member of IBM's Autonomic Computing initiative. Tango/04 has more than a thousand customers who are served by over 35 authorized Business Partners around the world.

Alliances

Partnerships IBM Business Partner IBM Autonomic Computing Business Partner IBM PartnerWorld for Developers Advanced Membership IBM ISV Advantage Agreement IBM Early code release IBM Direct Technical Liaison Microsoft Developer Network Microsoft Early Code Release

Awards

Legal Notice

The information in this document was created using certain specific equipment and environments, and it is limited in application to those specific hardware and software products and version and releases levels.

Any references in this document regarding Tango/04 Computing Group products, software or services do not mean that Tango/04 Computing Group intends to make these available in all countries in which Tango/04 Computing Group operates. Any reference to a Tango/04 Computing Group product, software, or service may be used. Any functionally equivalent product that does not infringe any of Tango/04 Computing Group's intellectual property rights may be used instead of the Tango/04 Computing Group product, software or service

Tango/04 Computing Group may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents.

The information contained in this document has not been submitted to any formal Tango/04 Computing Group test and is distributed AS IS. The use of this information or the implementation of any of these techniques is a customer responsibility, and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. Despite the fact that Tango/04 Computing Group could have reviewed each item for accurateness in a specific situation, there is no guarantee that the same or similar results will be obtained somewhere else. Customers attempting to adapt these techniques to their own environments do so at their own risk. Tango/04 Computing Group shall not be liable for any damages arising out of your use of the techniques depicted on this document, even if they have been advised of the possibility of such damages. This document could contain technical inaccuracies or typographical errors.

Any pointers in this publication to external web sites are provided for your convenience only and do not, in any manner, serve as an endorsement of these web sites.

The following terms are trademarks of the International Business Machines Corporation in the United States and/or other countries: iSeries, iSeriese, iSeries, i5, DB2, e (logo)®Server IBM ®, Operating System/400, OS/400, i5/OS.

Microsoft, SQL Server, Windows, Windows NT, Windows XP and the Windows logo are trademarks of Microsoft Corporation in the United States and/or other countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and/or other countries. UNIX is a registered trademark in the United States and other countries licensed exclusively through The Open Group. Oracle is a registered trade mark of Oracle Corporation.

Other company, product, and service names may be trademarks or service marks of other companies.