Reporting and IntegrationReporting and Integration

Jonathan Whiteman Microsoft Europe, Middle East and Africajonwhite@microsoft.com

Jonathan Whiteman Microsoft Europe, Middle East and Africajonwhite@microsoft.com

AgendaAgenda

MOM 2005 Reporting Overview Pre-requisites SQL Server 2000 Reporting Services Best practices in creating MOM Reports How to create your own reports

Extending MOM 2005 Microsoft Connector Framework Microsoft Product Connectors

MOM Reporting ConsoleMOM Reporting Console Utilizes SQL Server Reporting Services

Dedicated Reporting Database for long term storage Automatic DTS transfer Fully customizable reports Per report security available Dynamic reports Exporting data to other formats Publish to Web site Schedule generation offline

Multiple perspectives available out of the box Operations Reports Management Pack Reports Capacity and Usage Reports Performance and Load Reports Security Reports Reliability and Availability Reports (December) Configuration and Inventory Reports

MOM 2005 Built-in ReportsMOM 2005 Built-in ReportsManagement Pack Reports Released

Exchange 2000 & 2003 Server 34 RTM

Internet Information Services 6 WEB

MOM 2005 33 RTM

Security (MBSA) 2 RTM

SMS 2003 44 RTM

SQL Server 2000 12 RTM

Terminal Server 4 WEB

Virtual Server 2005 4 WEB

Web Services 6 WEB

Windows Active Directory 14 RTM

Windows Server Cluster 2 RTM

Windows DNS 3 RTM

Windows Server (2000, 2003, NT4)

27 RTM

TOTALTOTAL 193193

Reporting Pre-requisitesReporting Pre-requisites Win2000 with SP4, all editions Windows 2003, all editions, XP ASP.NET 1.1, IIS 5.0 or later installed and configured, MDAC 2.6 or

higher. SQL Server 2000 SP3a. For Windows 2003, the computer must be

configured as an application server. For Windows 2003 to use the network service account to run the ReportServer service, you need SQL Server QFE 859. To download the QFE, go to Microsoft Support Report ManagerWeb

Install Visual Studio 2003 (one of the Visual Studio .Net Standalones) Install SQL 2000 Reporting Services according to your SQL Version Install the System Center Data Warehouse Default website accessible through http://<servername>/Reportserver System Center Data Warehouse Reports through

http://<servername>/reports

SQL Server CatalogSQL Server Catalog

Report ServerReport Server

XML Web Service InterfaceXML Web Service Interface

Report ProcessingReport Processing

DeliveryDelivery

Delivery Targets(E-mail, SharePoint,

Custom)

RenderingRendering

Output Formats (HTML, Excel, PDF, Custom)

Data ProcessingData Processing

Data Sources(SQL, OLE DB, XML/A, ODBC, Oracle, Custom)

SecuritySecurity

Security Services(NT, Passport,

Custom)

Office Custom ApplicationBrowser

SQL Server 2000 Reporting Services ArchitectureSQL Server 2000 Reporting Services Architecture

Step 1: What to think about planning ReportsStep 1: What to think about planning Reports

Using Parameters to handle large data volumesReport header allow to chose ParametersParameter types are Filtering

A filter is a field where to whole results are impacted Sorting

Allow to sort the columns in a Report Grouping

Allows to display data in groups and reduce the amount of data presented.

Data collectionData should be collected by MOM that you can Report on. If not already done you to create the logic to collect the data

Step 2: What you should not doStep 2: What you should not do

Don’t do a simple 100 pages long list Base on a scenario E.G. : “Show me what Server has which Version

of ASP .NET installed” The faster you get to your result the better

Details can be on a linked Report

Step 3: What Reports should look likeStep 3: What Reports should look likeThis logo can be replaced globally for all Reports in the Images folder of the Reporting Server Called “2Inchlogo.png”

Print the parameters selected - this helps to understand an exported report

This is a groupheader. Sorting works

best on this topmost level. Collapsed you

only see the groupheaders

The next groupheader is only visible

after expanding.Do not hide

important Informations

on a lower level

Underlined Information is linked to a Detailreport. Data which is related, but not needed on this page

Set and follow StandardsSet and follow Standards

Use a Reports folder outside of “Microsoft Operations Manager Reporting” to not have your Reports overwritten

Do not overload Reports with too much data - choose Portrait or Landscape (Letter or A4) as a Standard

If you use a single graph don’t let the User scroll – fit it on one page

If you are using multiple graphs keep the same height

Building a simple reportBuilding a simple report

Building a simple report is easy using the reporting wizard

The reporting wizard allows you to select all of the required options for your report including: Data source SQL Query Report look and feel Fields to show on your report

Creating more complex reportsCreating more complex reports

Use the Microsoft reports as a starting point when creating more complex reports

Save an existing report to RDL and open in SQL Reporting Services

Modify the look and feel as required Edit the report to show the data you would

like to see

MOM 2005 Reporting TemplatesMOM 2005 Reporting Templates

Five Templates for easing your work Basic Settings for an international Report

are previewed Link:

http://www.microsoft.com/technet/prodtechnol/mom/mom2005/maintain/devguide/mpdg_8_reporting_6.mspx

Deployment of reportsDeployment of reports

Command line tool: RptUtil.exe creates .xml file which can be imported using the AdminconsoleThe XML file can contain 1-n Reports

/action: Action - import or export./file: Full path to the import or export file./url: Url of the report server./reportpath: Path to the report or report folder to be exported./fromdsref: Name of the "from" datasource reference to fixup./todsref: Name of the "to" datasource reference to fixup./datasource:Name of the datasource to fixup./dwserver: Name of the datawarehouse server used to fixup the datasource. /dwdb: Name of the datawarehouse database used to fixup the datasource.

cd "E:\Program Files\Microsoft System Center Reporting\Reporting"rptutil.exe /file:e:\myalertlatency.xml /nowarn /reportpath:"/custom reports/alert logging latency"

Example for a Batch file to export a Report to xml:

Reporting SummaryReporting Summary

Built in reports may suit Modify existing to create your own Report to support your business

Try it – custom Reporting is possible now

Extending MOM 2005Extending MOM 2005

Management Packs (MP) Intelligent monitoring of server applications

MOM Connector Framework (MCF) Interoperability with other management systems

Extensible API and configuration Development of custom solutions

MOM Connector FrameworkMOM Connector Framework

Interoperability Existing management system Trouble-ticketing system Consistency for integration with different products

Expose MOM and MP intelligence Forwarding MOM alerts Collecting alerts from other systems Tracking which alerts have been forwarded Synchronizing alerts Exposing discovery data

Expose an easy way for data to flow into MOM Show alerts and state for servers and systems not

managed by mom directly

Microsoft Product ConnectorsMicrosoft Product Connectors

3 microsoft supported product connectors MOM to Tivoli TEC MOM to HP OVO MOM to HP NNM

Partner solutions There are a number of partners in this space

Build your own

Microsoft Product connectors featuresMicrosoft Product connectors features Can be installed on MOM management server,

the other system server or separate dedicated server

Runs as a service and service account needs to be part of the mom service group

Contain management packs to Manage the product connector service and events Automatically mark an alert for that product connector

Utilize the recommended integration mechanism provided by the other product

MOM to Tivoli Enterprise Console (Tivoli TEC)

MOM to Tivoli Enterprise Console (Tivoli TEC)

Available in MOM Resource kit Forwards new alerts from MOM to Tivoli

TEC and keeps them in sync Uses Tivoli Endpoint and Tivoli tasks Supports the following versions

Tivoli Framework 3.7.1, 4.1 Tivoli Enterprise Console Adapter

Configuration Facility (ACF) 3.7.1, 3.8, 3.9 Tivoli Enterprise Console (TEC) 3.7.1, 3.8, 3.9

MOM to Tivoli TEC CaveatsMOM to Tivoli TEC Caveats

Does not support Tivoli framework 4.1.1 Was not tested with it and there is a known

framework issue around tasks

MOM to HP Openview OperationsMOM to HP Openview Operations

Available in MOM Resource kit Forwards new alerts from MOM to HP

OVO and keeps them in sync Uses HP OVI Supports the following versions

HP OpenView Operations for Windows (OVO/W) – Version: 7.x

Requires HP OpenView Interconnect (OVI) – Version: 3.0

MOM to HP OVO CaveatsMOM to HP OVO Caveats

If customer is using HP OVO on Unix then there could be contention issues with the ServiceName field This field is used by MOM to store the mom

alert id Definitely an issue if customer is using HP

Service Desk

MOM to HP Network Node Manager (NNM)MOM to HP Network Node Manager (NNM) Available in MOM Resource kit Forwards new alerts from MOM to HP NNM

By sending SNMP traps from MOM to HP NNM Supports the following versions

HP Network Node Manager 6.2 or 6.41

MOM to HP NNM CaveatsMOM to HP NNM Caveats

Is not a 2 way product connector Data only flows from MOM to HP NNM Changes to the alert in MOM do not

update HP NNM

Microsoft Product Connector SupportMicrosoft Product Connector Support Microsoft Product connectors posted on

MOM resource kit site Premier customers can get support through

Premier Support Services (PSS) Caveat:

This may not be the case yet in some areas Other product connectors are supported

by their creators

SummarySummary

Reporting Built in reports may suit Modify existing to create your own Report to support your business

Extending MOM Connectors available for many products Microsoft supplies 3

Tivoli TEC HP OpenView Operations HP NNM

Can build your own

© 2003-2004 Microsoft Corporation. All rights reserved.This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

MCF Partners – For Reference Only

MCF Partners – For Reference Only

Aprisma Dirigo/Engyro eXc Software Maranti Networks Metilinx Micromuse Opalis Seamless (BMC) Skywire Software Smarts More every day

Product Connector References – For Reference Only

Product Connector References – For Reference Only

HP Openview

MSFT Skywire Software Engyro

Network Node Manager MSFT Skywire Software eXc software

Product Connector References – For Reference Only

Product Connector References – For Reference Only

BMC Service Impact Manager

Seamless Technologies (BMC Partner) Patrol Enterprise Manager

eXc software Engyro Seamless Technologies

Remedy Skywire Software Opalis Seamless Technologies – planning Remedy in ‘05

Product Connector References (cont) – For Reference Only

Product Connector References (cont) – For Reference Only

Tivoli TEC MSFT Skywire Software eXc software Engyro

Computer Associates CA has one but it doesn’t use MCF and they are working on a

new one Skywire Software eXc software

Product Connector References (cont) – For Reference Only

Product Connector References (cont) – For Reference Only

Peregrine Skywire Software Working with Peregrine directly but no firm plans yet

Micromuse Working with Micromuse – beta Jan 05 Skywire software eXc software

MCF Resources – For Reference Only

MCF Resources – For Reference Only

MOM Product Infohttp://www.microsoft.com/mom/

Management Packshttp://www.microsoft.com/mom/downloads/managementpacks/

MOM Connector Framework (MCF)http://www.microsoft.com/mom/evaluation/mcf/

SDKhttp://www.microsoft.com/mom/downloads/sdk/

Communityhttp://www.microsoft.com/mom/community/

MOM Partnerhttp://www.microsoft.com/management/mma