Presentation is loading. Please wait.

Presentation is loading. Please wait.

Reporting and Integration Jonathan Whiteman Microsoft Europe, Middle East and Africa Jonathan Whiteman Microsoft Europe, Middle.

Similar presentations


Presentation on theme: "Reporting and Integration Jonathan Whiteman Microsoft Europe, Middle East and Africa Jonathan Whiteman Microsoft Europe, Middle."— Presentation transcript:

1 Reporting and Integration Jonathan Whiteman Microsoft Europe, Middle East and Africa jonwhite@microsoft.com Jonathan Whiteman Microsoft Europe, Middle East and Africa jonwhite@microsoft.com

2 Agenda 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

3 MOM 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

4 MOM 2005 Built-in Reports Management PackReportsReleased Exchange 2000 & 2003 Server34RTM Internet Information Services6WEB MOM 200533RTM Security (MBSA)2RTM SMS 200344RTM SQL Server 200012RTM Terminal Server4WEB Virtual Server 20054WEB Web Services6WEB Windows Active Directory14RTM Windows Server Cluster2RTM Windows DNS3RTM Windows Server (2000, 2003, NT4) 27RTM TOTAL193

5 Reporting 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:// /Reportserver System Center Data Warehouse Reports through http:// /reports

6 SQL Server Catalog Report Server XML Web Service Interface Report Processing Delivery Delivery Targets (E-mail, SharePoint, Custom) Rendering Output Formats (HTML, Excel, PDF, Custom) Data Processing Data Sources (SQL, OLE DB, XML/A, ODBC, Oracle, Custom)Security Security Services (NT, Passport, Custom) Office Custom Application Browser SQL Server 2000 Reporting Services Architecture

7 Step 1: What to think about planning Reports Using Parameters to handle large data volumes Report header allow to chose Parameters Parameter 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 collection Data should be collected by MOM that you can Report on. If not already done you to create the logic to collect the data

8 Step 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

9 Step 3: What Reports should look like

10 Set 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

11 Building 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

12 Creating 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

13 MOM 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_r eporting_6.mspx

14 Deployment of reports Command line tool: RptUtil.exe creates.xml file which can be imported using the Adminconsole The 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:

15 Reporting Summary Built in reports may suit Modify existing to create your own Report to support your business Try it – custom Reporting is possible now

16 Extending 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

17 MOM 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

18 Microsoft 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

19 Microsoft 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

20 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

21

22

23 MOM 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

24 MOM 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

25

26

27 MOM 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

28 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

29 MOM 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

30 Microsoft 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

31

32 Summary 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

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

34 MCF Partners – For Reference Only Aprisma Dirigo/Engyro eXc Software Maranti Networks Metilinx Micromuse Opalis Seamless (BMC) Skywire Software Smarts More every day

35 Product Connector References – For Reference Only HP  Openview  MSFT  Skywire Software  Engyro  Network Node Manager  MSFT  Skywire Software  eXc software

36 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

37 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

38 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

39 MCF Resources – For Reference Only MOM Product Info http://www.microsoft.com/mom/ Management Packs http://www.microsoft.com/mom/downloads/managementpacks/ MOM Connector Framework (MCF) http://www.microsoft.com/mom/evaluation/mcf/ SDK http://www.microsoft.com/mom/downloads/sdk/ Community http://www.microsoft.com/mom/community/ MOM Partner http://www.microsoft.com/management/mma


Download ppt "Reporting and Integration Jonathan Whiteman Microsoft Europe, Middle East and Africa Jonathan Whiteman Microsoft Europe, Middle."

Similar presentations


Ads by Google