Cross Product Reporting

Transcription

1 Cross Product Reporting User Guide Latest Revision: November 3, 2008 iii

2

3 Legal Notice This publication is based on current information and resource allocations as of its date of publication and is subject to change or withdrawal by CA at any time without notice. The information in this publication could include typographical errors or technical inaccuracies. CA may make modifications to any CA product, software program, method or procedure described in this publication at any time without notice. Any reference in this publication to non-ca products and non-ca websites are provided for convenience only and shall not serve as CA s endorsement of such products or websites. Your use of such products, websites, and any information regarding such products or any materials provided with such products or at such websites shall be at your own risk. Notwithstanding anything in this publication to the contrary, this publication shall not (i) constitute product documentation or specifications under any existing or future written license agreement or services agreement relating to any CA software product, or be subject to any warranty set forth in any such written agreement; (ii) serve to affect the rights and/or obligations of CA or its licensees under any existing or future written license agreement or services agreement relating to any CA software product; or (iii) serve to amend any product documentation or specifications for any CA software product. The development, release and timing of any features or functionality described in this publication remain at CA s sole discretion. The information in this publication is based upon CA s experiences with the referenced software products in a variety of development and customer environments. Past performance of the software products in such development and customer environments is not indicative of the future performance of such software products in identical, similar or different environments. CA does not warrant that the software products will operate as specifically set forth in this publication. CA will support only the referenced products in accordance with (i) the documentation and specifications provided with the referenced product, and (ii) CA s then-current maintenance and support policy for the referenced product. Certain information in this publication may outline CA s general product direction. All information in this publication is for your informational purposes only and may not be incorporated into any contract. CA assumes no responsibility for the accuracy or completeness of the information. To the extent permitted by applicable law, CA provides this document AS IS without warranty of any kind, including, without limitation, any implied warranties of merchantability, fitness for a particular purpose, or non-infringement. In no event will CA be liable for any loss or damage, direct or indirect, from the use of this document, including, without limitation, lost profits, lost investment, business interruption, goodwill or lost data, even if CA is expressly advised of the possibility of such damages. Copyright License and Notice This publication may contain sample application programming code and/or language which illustrate programming techniques on various operating systems. Notwithstanding anything to the contrary contained in this publication, such sample code does not constitute licensed products or software under any CA license or services agreement. You may copy, modify and use this sample code for the purposes of performing the installation methods and routines described in this document. These samples have not been tested. CA does not make, and you may not rely on, any promise, express or implied, of reliability, serviceability or function of the sample code. Copyright 2008 CA. All rights reserved. All trademarks, trade names, service marks and logos referenced herein belong to their respective companies.

4

5 CA Product References This document may reference the following CA components and products: CA SPECTRUM CA Network and Systems Management (CA NSM) CA Service Desk CA CMDB CA Systems Management Pack Assistant (including the Asset Migration Utility) Change History November 3, 2008 Initial version of document created

6

7 Contents Chapter 1: Introduction Commonly Used Terms... 2 High Level Overview... 2 Chapter 2: Installation Before you Begin... 5 Hardware Prerequisites... 5 Software Prerequisites... 5 Configuration Requirements... 5 MDR Mappings... 6 Access to CMDB and Source Application Databases... 6 Security Considerations... 7 Database Installer User ID... 7 Database Admin User ID... 7 Database Reader Authorization... 8 Installing Cross Product Reporting... 8 Chapter 3: Data Refresh Process Data Refresh Basics Command Line Interface List Valid Source Types (/v) List Defined Sources (/s) List Linked Server Logins (/l) Add, Replace or Update Source (/a) Change Access Credentials for an Existing Source (/c) Delete Source (/d) Refresh Data (/r) Output Activities to Log File (/f) Data Refresh Process Scheduling Chapter 4: The Reports Overview iii

8 Change History Accessing Cross Products Reporting in InfoView CMDB/Source Services Report Overview CMDB Services Report CMDB Services Report Hierarchy Examples / Use cases Source Services Report Source Services Report Hierarchy Examples / Use cases CMDB/Source Service Content Report CMDB Service Content Report CMDB Service Content Report Hierarchy Examples / Use cases Source Service Content Report CMDB Service Content Report Hierarchy Examples / Use cases CIs/Source Object Exceptions Reports CI Exceptions Report CI Exceptions Report Hierarchy Examples / Use cases Source Object Exceptions Report Source Object Exceptions Report Hierarchy Examples / Use cases Chapter 5: Frequently Asked Questions Chapter 6: References and Links CA Links and Documents External Links Appendix A: Advanced Data Refresh Topics Identify Sources Establishing the Connection Drivers and Configuration Microsoft SQL Server MySQL Credentials CMDB Source Database Privileges NSM Source Database Privileges Spectrum Source Database Privileges iv

9 Change History MySQL Credentials Data to Retrieve and Merge Refresh Process Scheduling Appendix B: Data Gathered and Exposed by the Reporting Database v

10

11 Chapter 1: Introduction One of the fundamental purposes of implementing a CMDB is to minimize operational risks by managing the relationships between key configuration items (CIs) that support the business. Much of the power of the CA CMDB lies in its ability to aggregate data from IT silos across the infrastructure and to integrate that data into a single logical entity. In short, the CA CMDB enables you to view federated information from nearly any managed data source through a simple mouse-click. Cross Product Reporting takes this one step further by utilizing and correlating information between the CA CMDB and the integrated Management Data Repositories (MDRs) that provide the CI source data, such as CA SPECTRUM and CA Network and Systems Management (NSM). The CA Cross Product Reporting Solution is built upon the following key components: Reporting database containing key data from source CA application databases (i.e., CA NSM, CA SPECTRUM) Data collection process that connects to defined source CA application databases to populate and refresh the reporting database Reporting application to present and support analysis of the data populated to the reporting database Unifying the essential data generated from multiple sources together in a single repository and simplifying the analysis of the information by providing out of the box reports allows you to easily spot potential issues and identify opportunities to improve the overall health of the Enterprise. Through the provided CI exceptions reports you can: Easily identify the CI s source application(s) and instances that manage the CMDB Business Services you care about as well as the status of this alignment Understand how various Business Services are managed through reports on the associated CIs and how these are managed by the various source applications Quickly find CIs that are inactivated in the CMDB but are still managed by it source application, as well as those CIs that are active in the CMDB but no longer are being managed by CA NSM and/or CA SPECTRUM. These are just a few examples of how Cross Product Reporting correlates information from the CMDB and its associated MDRs to quickly provide an overview of how critical Business Services and their associated CIs are managed. 1

12 Commonly Used Terms Commonly Used Terms Following is a list of terms that are commonly used in this document. Term Configuration Item (CI) Management Data Repository (MDR) Linked Server Linked Server Login Stored Procedure Definition CMDB entity that represents an infrastructure component that is required to provide the services, systems and applications to support an agreed-upon service to the IT customer. Identifies an instance of the source application and source application identifier for the entity that generated the CMDB configuration item. Configuration entry that enables Microsoft SQL Server to execute commands against OLE DB data sources on remote servers. Configuration entry that maps a local database user login to a remote linked server database user and password. Precompiled executable object that contains one or more SQL statements. High Level Overview Cross Products Reporting provides three basic types of reports that focus on the following: CMDB/Source Services Report This type of report analyzes all Services and identifies how they are aligned with services in other MDRs. This enables you to quickly pinpoint where and how important Business Services are being managed and, even more importantly, where they are not being managed. CMDB/Source Services Content Report This type of report analyzes the Services and the CIs which comprise those Services. You can drill into a specific service and analyze the CIs associated with this service, based on how they are aligned with the designated service in its counterpart (CMDB/source application). This simplifies the process of ensuring that all assets in the key business services are being properly managed (as outlined in the CA CMDB) CI Alignment with CMDB and MDR Assets This type of report analyzes how each CI is aligned with assets in the CA CMDB and other MDRs. This enables you to quickly identify exceptions across all CIs and all MDRs. 2

13 High Level Overview Furthermore, each of these reports can be looked at from either the CMDB or source application perspective. The result is the following six primary reports: CMDB Oriented Reports which include: CMDB Services Report CMDB Service Content Report CI Exceptions Report Source Application Oriented Reports which include: Source Services Report Source Service Content Report Source Object Exceptions Report Further details on these reports are provided on page 25 in the The Reports chapter. Note: The Cross Product Reports in this package were designed using Crystal Reports XI and to use these as a base for custom reports you need to have a separate license for Crystal Reports Developer XI. However, custom reports based on this BusinessObjects universe can be created with Web Intelligence that is licensed with the CA bundled version of BusinessObjects. 3

14

15 Chapter 2: Installation This chapter provides information on how to install Cross Product Reporting including security considerations. Before you Begin In order to use this solution, the following prerequisites must be met. Hardware Prerequisites Cross Product Reporting requires a minimum of 1 GB of free disk space. Note: As noted below, CA Business Intelligence is a prerequisite. Therefore, you should refer to the BusinessObjects documentation and scaling guidelines for additional hardware requirements for BusinessObjects XI. Software Prerequisites The Cross Product Reporting solution requires the following software to be installed before the Cross Product Reporting Package is installed: CA Business Intelligence MS SQL Server 2005 Since this solution produces reports on discrepancies between the CA Service Desk/CMDB and CA SPECTRUM and/or CA NSM, these solutions need to be accessible in the infrastructure: CA Service Desk r11.x / CMDB r11.x (Integrated and installed on the same server / MDB) CA SPECTRUM r8.x (optional) CA NSM r11.x (optional) Appropriate ODBC drivers to access databases for these products (see Appendix A for more details) Configuration Requirements The following additional configuration changes are required to support this solution: 5

16 Before you Begin Ensure Managed Data Repositories (MDRs) are defined for the CIs and Services you are concerned about Ensure appropriate access is provided to CA CMDB and defined MDRs Details are provided in the next sections. MDR Mappings In order to identify the relationship between assets and services in the CA CMDB with the corresponding objects in their source applications you need to ensure that the necessary MDRs have been mapped. This can be done manually, by defining Federated CI Mapping in the CMDB, or through utilities such as the Modeling Gateway Toolkit or the CA Asset Migration Utility. For manual definition, each mapping will require a CI, an MDR and the related Federated Asset IDs that identifies the aligned object in the Source Application. If a CI is managed in multiple data sources this step has to be done for each of them. Details on how to do this are provided in the CA CMDB Implementation Guide ( f&type=pdf) If you have a large number of CIs/objects that have not yet been aligned, manual definition is obviously not feasible. To accommodate these types of situations, CA has developed toolkits that assist with bulk loading of a selected subset of objects into the CMDB, including the associated Federated Asset IDs. One of the tools that can be used to bulk import and align CA NSM assets into the CMDB is the CA Asset Migration Utility, which is a part of CA Systems Management Pack Assistant (SMPA). CA SMPA can be obtained through a CA Services engagement and details on how to use it can be found in the Getting Started Guide that is provided with the utility. The corresponding utility for CA SPECTRUM is the Modeling Gateway Toolkit. For more information about this toolkit refer to the Modeling gatewaytoolkit Guide [5069] which can be found at the following link: pdf Access to CMDB and Source Application Databases In order to successfully collect the required information from the various data sources it is important to ensure that the database user(s) have sufficient privileges to those databases. Please see Appendix A for details on these requirements. 6

17 Security Considerations Security Considerations Security for the cross product reporting database has been designed to be simple and easy to manage. Roles have been predefined and granted the privileges to carry out typical activities. Granting user access is as easy as adding a Microsoft SQL Server login, trusted Windows user or group to an appropriate database role. Database Installer User ID The database, required objects and default database owner login are created during installation. You will be prompted to provide credentials that are authorized to perform the following tasks on the specified database server: Create a database Create a new login Grant server privileges to the new login Change the owner of the database Add a job and job schedule to be executed by the Microsoft SQL Server Agent It is recommended that the credentials provided be those of a system administrator (i.e., member of the Microsoft SQL Server built-in sysadmin server role). Consult the Microsoft SQL Server documentation for specifics on assigning the required privileges to a login that is not a sysadmin member. Database Admin User ID Along with the database, the installation process also creates a Microsoft SQL Server login, cacomrpt_admin, and assigns the owner of the reporting database (dbo) to that login. As the database owner, cacomrpt_admin has privileges to access, alter and delete any and all objects in the cross product reporting database. The login will also be granted two additional server privileges: ALTER ANY LINKED SERVER ALTER ANY LOGIN These privileges are required to successfully define the linked server and linked server login records that will be used to access remote sources to collect data that will be added to the reporting database. 7

18 Installing Cross Product Reporting Database Reader Authorization Users or groups requiring access to read data and view reports can simply be added to the ca_datareader database role. Role members are granted select privileges on all database objects and execute privileges on scalar functions that dynamically generate values for calculated fields exposed in the reports. Role members cannot add, alter or delete data or objects from the database. Installing Cross Product Reporting To install Cross Product Reporting, do the following: Note: Note that the user ID you use to perform the install must have administrator level credentials. Additional details are provided in the previous section. 1. Launch the install by double-clicking setup.exe Once the InstallShield Wizard initializes, it checks the system to ensure that all prerequisites have been met. 2. The Welcome dialog appears once the prerequisites have been confirmed. Click Next to continue. 3. Review the License Agreement and click I Agree to proceed. 8

19 Installing Cross Product Reporting 4. Provide a User Name, Company Name and select usage conditions restricting to all one user or open to all users on this computer and click Next to proceed. 5. Select the features to install. 9

20 Installing Cross Product Reporting There is only 1 feature that can be selected - Local Install. This install will not run remotely and needs to be run on the BOXI machine. Click Next to proceed. 6. You will be prompted to identify the installation folder for Cross Product Reporting. 10

21 Installing Cross Product Reporting Accept the default location or click Browse to select a new location. Then, click Next to proceed. Note: A warning message will be issued if the installation folder does not have sufficient space available. 7. Once the system environment has been checked and validated you will be prompted to provide details regarding connection to the master database: Provide the following details: SQL Server name Instance name (if SQL is configured to use an instance) Listen Port (default 1433) SQL Administrator user (default sa) and corresponding password for that user Click Next to proceed. 8. Provide the user ID, password and authentication method that will be used to connect to the Business Objects Central Management Server. 11

22 Installing Cross Product Reporting Note: The ID you provide must have administrator level credentials. Click Next to proceed. 9. Specify a password for the cacomrpt_admin and re-enter that password to confirm it. Note: The cacomrpt_admin user ID is created during the installation. For more information refer to the Database Admin User ID section earlier. 12

23 Installing Cross Product Reporting Click Next to proceed. 10. Review your install selections and click Install to proceed with the installation. 11. When the installation is completed, you will be prompted to view the Readme file. This is recommended. 12. Click Finish to complete the installation. 13

24

25 Chapter 3: Data Refresh Process The CA Cross Product Reporting Solution data refresh process relies on Microsoft SQL Server support for linked servers and linked server logins configurations to connect directly to defined source application databases, execute stored procedures that extract, process and insert the required data into the reporting database tables. Since connection information for the configurations is stored in system tables, the information is protected and access is managed by Microsoft SQL Server. You are encouraged to review the following data refresh basics in order to understand the requirements for successful processing. Detailed steps are not provided for creating and managing the required configurations using Microsoft SQL server tools directly. Instead, for convenience, a command line interface is provided to add, delete or update entries that control the behavior of the refresh process. For more in depth details consult Appendix A: Advanced Data Refresh Topics. Data Refresh Basics Understanding the basics of the process is important to ensure successful data collection and will help pinpoint root cause should an error occur. Following are several basic concepts that are used. Concept Source Linked Server Comments Sources are application databases that contain data needed to populate the reporting database. Each source defined to the reporting database must have an associated linked server and linked server login defined. Linked servers are similar to an ODBC Data Source Name (DSN) except that the properties are stored in and accessible to Microsoft SQL Server processes. Once a linked server is defined, the data in a remote database can be accessed nearly as easily as data in a local database. Note that non-default instance names and ports may not be recognized. When necessary, use the Microsoft SQL Server Configuration Manager to define an alias. 15

26 Command Line Interface cacprcli Concept Linked Server Login Comments Once a linked server is defined the next step to establishing near transparent connectivity to a remote database is to define a linked server login. Simply put, a linked server login entry maps a local login to credentials (i.e., login and password) needed to access data on a remote server. When a source is defined to the reporting database, a unique linked server name for that source is generated and stored with the source record in the reporting database. A linked server entry is also defined to Microsoft SQL Server for the unique linked server name generated. For each linked server entry generated, a linked server login record is added, mapping the reporting database admin login to credentials needed to login into the remote linked server and access the required data. Command Line Interface cacprcli You can use the cacprcli command line interface to manage entries that control the behavior of the collection process. This utility can be run on any system on which the Microsoft SQL Server sqlcmd utility is installed and in the default path. Brief usage instructions are displayed when the utility is invoked without a switch or if the switch specified is not recognized. Since configuration information is stored in the reporting database, when the utility is invoked using a supported switch, you will always be prompted for access information and credentials. Prompt Reporting Database Name (Default cacomrpt) Reporting Database Server (Default localhost) Comments Name of the reporting database. If left blank the default cacomrpt will be assumed Name, IP address or alias of the database server hosting the reporting database. If left blank the default localhost will be assumed. Note that non-default instance names and ports may not be recognized. When necessary define use the Microsoft SQL Server Configuration Manager to define an alias. 16

27 Command Line Interface cacprcli Prompt Reporting Database Admin (Default Trusted) Reporting Database Password Comments Database user with administrative privileges defined for the reporting database. If left blank the logged on Windows user will be assumed to be a trusted user with the required privileges. Password for the database user specified, if other then trusted logged on Windows user is specified. Appropriate console messages will be generated if you fail to provide a required entry or if the specified entry is identified as invalid. Once connected to the reporting database you will be prompted for additional information required dependent upon the switch specified. The activities and results of the last ten sessions are retained in the log sub-directory in files named cacprcli*.log. List Valid Source Types (/v) Executing cacprcli /v will produce a table of currently supported source and associated parameters. Parameter Application Name Version Content Type Database Provider Comments Names of supported source applications. Supported version(s) of the source application. Most source applications require only one source entry be defined to gather all data that should be extracted and merged into the reporting database (type All ). Certain source applications may require separate source entries for types of data exposed by the application to align the merged data properly (for example, the application Spectrum exposes data for both Devices and Services ). Name of supported DBMS provider(s) for the source application. 17

28 Command Line Interface cacprcli List Defined Sources (/s) To generate a list of defined sources and related properties simply execute cacprcli /s. The results will be output to the console and to a file ( source.dat ). Property Source App Name Version Content Type DB Provider DB Server DB Name Linked Server ID MDR Class MDR Name Comments Names of supported source applications. Supported version of the source applications. Most source applications require only one source entry be defined to gather all data that should be extracted and merged into the reporting database (type All ). Certain source applications may require separate source entries for type of data exposed by the application to align the merged data properly (for example, the application Spectrum exposes data for both Devices and Services ). Name of supported DBMS provider(s) for the source application. Name, IP address or alias of the DBMS hosting the source application database. Name of the source application database. Unique name generated to identify the source linked server in Microsoft SQL system tables. Class associated with unique management data repository (MDR) record defined to the CMDB for the source application instance. Name associated with unique management data repository (MDR) record defined to the CMDB for the source application instance. List Linked Server Logins (/l) Executing cacprcli /l generates a table containing information to help identify linked server login mappings. The results will be output to the console and to a file ( login.dat ). 18

29 Command Line Interface cacprcli Property Linked Server Local DB Login Remote DB Login Source App Name Content Type DB Provider DB Server DB Name MDR Class MDR Name Comments Unique name for linked sever associated with a source application entry. Local reporting database login that has been mapped to a remote linked server login. Login defined to remote linked server able to access the required data associated with the local database login. Names of supported source application. Most source applications require only one source entry be defined to gather all data that should be extracted and merged into the reporting database (type All ). Certain source application may require separate source entries for type of data exposed by the application to align the merged data properly (for example, the application Spectrum exposes data for both Devices and Services ). Name of supported DBMS provider(s) for the source application. Name, IP address or alias of the DBMS hosting the source application database. Name of the source application database. Class associated with unique management data repository (MDR) record defined to the CMDB for the source application instance. Name associated with unique management data repository (MDR) record defined to the CMDB for the source application instance. Add, Replace or Update Source (/a) In order to collect and merge data from a supported source application instance into the reporting database, a source record must be added. Successful addition of a source will also create the required linked server and linked server login records needed to connect to the source database. To start the process execute cacprcli /a and respond to the prompts requesting information needed to connect to the reporting database. Note that the user specified for this connection must have equivalent to database admin or higher privileges. 19

30 Command Line Interface cacprcli Once connected prompts for the following parameters will be generated: Property Source Application Name Source Application Version Source Application Content Type Source Application Database Provider Source Application Database Server Source Application Database Name Source Application Database User Source Application Database Password Comments Names of supported source application. Version of the source application supported. Most source applications require only one source entry be defined to gather all data that should be extracted and merged into the reporting database (type All ). Certain source application may require separate source entries for type of data exposed by the application to align the merged data properly (for example, the application Spectrum exposes data for both Devices and Services ). Name of supported DBMS provider(s) for the source application. Name or IP address for the DBMS hosting the source application database (see Named Instance for specifying a non-default instance of Microsoft SQL Server). Name of the source application database. User ID to use to connect to the source application database during the collection process. Password for user specified to connect to source application database during the collection process. When the source application specified is other than CMDB two additional prompts will be generated: Property CMDB MDR Class Related to Source CMDB MDR Name Related to Source Comments Class associated with unique management data repository (MDR) record defined to the CMDB for the source application instance. Name associated with unique management data repository (MDR) record defined to the CMDB for the source application instance. 20

31 Command Line Interface cacprcli After you respond to all prompts, the utility will first confirm that required parameters have been specified and match entries for supported applications. Appropriate messages will be generated if any exceptions are detected. Next, a search is made to determine if a source matching the parameters specified already exists. If an existing source is found you will be informed and prompted to confirm replacement of the existing source information based on the parameters entered. Important: Each reporting database may have only one source CMDB. An Existing source record found and prompt to confirm replacement of the existing source will be generated whenever a user attempts to add a second CMDB source. Should the user respond Y the existing CMDB source record and all related data will be purged from the reporting database. Important: Sources for applications other than CMDB must have a unique application name, content type and database server as well as unique MDR class and name. Should a user attempt to add a source with the same application name, content type and database server or MDR class and name an Existing source record found and prompt to confirm replacement of the existing source will always be generated. Should the user respond Y the existing CMDB source record and all related data will be purged from the reporting database. Note that, if the existing source entry is replaced, all data associated with that source will be purged. Data will be repopulated during the next refresh cycle. Respond Y to replace the previously defined source or N to cancel the update. Change Access Credentials for an Existing Source (/c) To update access credentials (i.e., user name, password) for the linked server login associated with a defined source execute cacprcli /c and respond to the prompts requesting information needed to connect to the reporting database. Note that the user specified for this connection must have equivalent to database admin or higher privileges. Once connected to the reporting database, you will be prompted for the following: Parameter Source Application Name Source Application Database Provider Source Application Database Server Comments Names of supported source application. Name of supported DBMS provider(s) for the source application. Name or IP address for the DBMS hosting the source application database. 21

32 Command Line Interface cacprcli Parameter MDR Class MDR Name Source Application Database User Source Application Database Password Comments Class associated with unique management data repository (MDR) record defined to the CMDB for the source application instance. Name associated with unique management data repository (MDR) record defined to the CMDB for the source application instance. User ID to use to connect to the source application database during the collection process. Password for user specified to connect to source application database during the collection process. Once the required parameters are entered and the associated source record is located in the reporting database, you will be prompted to confirm the change. Enter Y to confirm or N to cancel the access credentials change. Delete Source (/d) Deleting a source entry will also purge all data related to the source from the reporting database. To delete the source and related data run cacprcli /d and respond to the prompts requesting information needed to connect to the reporting database. Note that the user specified for this connection must have equivalent to database admin or higher privileges. After connecting to the reporting database respond to the following prompts: Property Source Application Name Source Application Content Type Comments Names of supported source application. Most source applications require only one source entry be defined to gather all data that should be extracted and merged into the reporting database (type All ). Certain source application may require separate source entries for type of data exposed by the application to align the merged data properly (for example, the application Spectrum exposes data for both Devices and Services ). 22

33 Data Refresh Process Scheduling Property Source Application Database Server CMDB MDR Class Related to Source CMDB MDR Name Related to Source Comments Name, IP address or alias of the DBMS hosting the source application database. Class associated with unique management data repository (MDR) record defined to the CMDB for the source application instance. Name associated with unique management data repository (MDR) record defined to the CMDB for the source application instance. You will be prompted to confirm that the source and related data should be deleted from the reporting database. Respond Y to delete the data or N to cancel the request. Refresh Data (/r) After defining sources to the reporting database you can execute cacprcli /r to initiate a refresh cycle on demand to collect and merge data from all defined sources. You will prompted to supply connection information for the reporting database. Note that the reporting database admin login and password are required to successfully connect to the remote sources. Upon successfully connection to the reporting database, the refresh process will begin. Note that the refresh process can take a significant amount of time. Exiting prior to completion can leave the database in unpredictable state and that, in turn, will produce incorrect results or errors when you attempt to view reports. Output Activities to Log File (/f) Events recorded during the refresh cycle are stored in a table in the reporting database. To limit the size of the table, events that are over tens days old are automatically purged at the start of each cycle. For convenience, the contents of the table can be written to file activity.log in the log sub-directory by running cacprcli /f. The log can then be viewed using a simple text editor ( WordPad is recommended). Data Refresh Process Scheduling The CA Cross Product Reporting solution package does not include a scheduling service of its own. Instead, a job is added to the Microsoft SQL Server Agent queue during the installation process to invoke the data refresh process daily at 03:00 AM local server time. You can modify that schedule through the Microsoft SQL Server Management Server user interface (see Microsoft SQL Server Books Online for details). 23

34

35 Chapter 4: The Reports This chapter describes how to generate the reports provided with Cross Product Reporting, and how the information they provide can help you identify discrepancies between CIs defined in the CA CMDB and active CIs managed by the source MDRs. Overview As previously noted, Cross Product Reporting basically consists of three types of reports that are delivered out of the box: CMDB/Source Services Report CMDB/Source Service Content Report CIs/Source Objects Exceptions Reports Each type consists of two reports so that you can navigate from either of the following perspectives: From CMDB point of view to see aligned Source service and\or assets From Source Application point of view to see aligned CMDB Services and CIs Important: It is critical to understand that these reports will only work if the necessary relationships between the CMDB and the corresponding objects in the Source Application are defined through MDRs within the CMDB. For more information on this see Configuration Requirements on page 5. 25

36 Accessing Cross Products Reporting in InfoView Accessing Cross Products Reporting in InfoView The Cross Product Reports are located in the path Public Folders / CA Reports / CA Cross Product Reports and can be accessed through the BusinessObjects XI InfoView component. Details on how to find them can be found below: 1. Launch InfoView. The default URL is the following: 2. Login to InfoView using credentials which have access to the Cross Product Reporting Reports. 3. Navigate to Public Folders / CA Reports / CA Cross Product Reports 26

37 Accessing Cross Products Reporting in InfoView 4. Open the report you would like to access by clicking on its Title/Name in the right hand pane. The result will be similar to the following: The report options that are displayed will depend on what access rights you have and whether any reports have been scheduled to run. The options displayed in the example above reflect the view for the out-of-the box Administrator user. To view the report, click the report title (for example, CI Exceptions Report ). You can also initiate other actions by clicking on the desired action link. Options include: View Latest Instance: Click this link to quickly access the latest available pre-processed report. This link is only visible for reports that have been pre-processed through a scheduled job. History: Click this link to view a list of all pre-processed reports. This allows you to go back and see how the results have changed over time. Schedule: Click this link to schedule when and how this specific report should be executed. This will make it available in the History and as the Latest Instance. Properties: Click this link to view a list of basic properties of the report. Modify: Click this link to modify the report. Note, however, that Crystal Reports requires a separate license for developing and modifying reports. More detailed explanations are available in the BusinessObjects XI InfoView product documentation. The following sections provide information about the individual reports. 27

38 CMDB/Source Services Report Overview CMDB/Source Services Report Overview The CMDB Services Report and the Source Services Report allow you to easily locate services with a specific exception status based on alignment between the CMDB Services and Source Application Services. These reports are organized so that you can see increasingly more specific subsets of services by drilling into reports and looking at the Service s status from different points of views. For example you can determine the following: If the Services are Active or Not Active If they are correctly Mapped with an MDR or Not If the Services are Found or Not in the corresponding data source Each summary report also lets you optionally select further analysis of the expected/good state or analyze the exceptions. Typically, you can reach the exception by following a Service with a negating status such as NOT Active or NOT mapped. When looking at an exception or at the most granular expected/good state you can also drill down further and view the service from the perspective of a specific source application, such as CA NSM or CA SPECTRUM. In addition, each summary report allows you to drill into detailed reports of all services aligned with the current exception/status. The detailed reports list all services (both CMDB and their aligned Source Application) that have the selected status. When applicable, the detailed report also lists details about the connection, such as Source Application Name and Version, MDR Class and Name and Source Database Server. CMDB Services Report The CMDB Service Report follows a basic troubleshooting tree approach, drilling down into the report by answering questions such as: Is the CMDB Service active or NOT? In most cases, Services that are tagged as inactive in the CMDB should no longer be monitored by various Source Applications. This exception report helps you to find services that either are incorrectly tagged as inactive or that you should consider removing or marking as inactive in the Source Application as well. 28

39 CMDB/Source Services Report Overview Is the Mapping to the Source Service Found or NOT? If a Service is defined AND active in CMDB it is likely that it should be monitored by all types of Source Applications that are service-aware (from this point of view both NSM and SPECTRUM are considered to be serviceaware). The exception report for mapping to Source Service NOT found lists all CMDB services where at least one instance of a managed, service-aware source application does not have an aligned Service. This might or might not be expected. Is the actual Source Service Found or NOT? Finally, you can drill down to see a summary report of source services, indicating which have been successfully found in the source application and which have not. This allows you to easily find exceptions where services that previously existed and had been mapped from the CMDB but which now no longer exist in the source application. As noted earlier, when you have reached the most granular state based on status, you can also analyze the exception based on if the aligned source application is NSM or SPECTRUM. Finally, depending on the data collected, each of the summary reports can link to one or more detailed reports that list the CMDB services and applicable details regarding the aligned source services. CMDB Services Report Hierarchy Following is the complete hierarchy of the summary reports contained within the CMDB Service report: CMDB Service Active CMDB service active, mapping to source service found CMDB service active, mapped and source service found o o NSM SPECTRUM CMDB service active, mapped but source service NOT found o o NSM SPECTRUM CMDB service active, mapping to source service NOT found NSM SPECTRUM 29

40 CMDB/Source Services Report Overview CMDB Service NOT Active CMDB service NOT active - source service found NSM SPECTRUM CMDB service NOT active - source service NOT found NSM SPECTRUM Examples / Use cases Following are several examples of how this report can be used. Identify Non-Active CMDB Services still are managed by SPECTRUM 1. Launch InfoView and select the CMDB Service Report 2. Click the CMDB service NOT active link in the Status area or on the corresponding portion of the pie chart. This will drill down into the list of Inactive CMDB services to identify how many of those have a found source. 30

41 CMDB/Source Services Report Overview 3. Click the CMDB service NOT active source service found link in the table or on the corresponding portion of the pie chart to identify the how many of those services were defined in NSM and how many in SPECTRUM. 31

42 CMDB/Source Services Report Overview 4. To view a detailed report for each source application, click the count value in the appropriate row (e.g., NSM or SPECTRUM). For example, click the number 1 in the third row above to view detailed information regarding CA SPECTRUM, The result would be similar to the following: Identify Active CMDB Services Which Do Not Map to a Source Application 1. Launch InfoView and select the CMDB Service Report 2. Click the CMDB service active link in the Status area or on the corresponding portion of the pie chart. This will drill down into the list of active CMDB services to identify how many of those have a found source. 3. To view a detailed list of active CMDB service for which a source service has not been found, click the count value to the left of the CMDB service active, mapping to source service NOT found row. In the above example, you would click the 2. The results would be similar to the following: 32

43 CMDB/Source Services Report Overview This detailed report shows that the CMDB Service SAP is not managed by any of the integrated NSM or SPECTRUM instances. This would suggest that additional analysis is needed. For example, you might choose to take the following steps: After looking closer at this realize that one of the NSM instances should manage this. Add the related service definition into Systems Management Pack (or a ordinary Business Service) Align this new NSM Service to the CMDB Service SAP by creating a new Federated CI mapping within the CA CMDB. See the CA CMDB Implementation Guide for details on how to do this. After this is correctly mapped and the Reporting database has been updated the report should now only list SPECTRUM in this report. 33

44 CMDB/Source Services Report Overview Source Services Report The Source Services Report follows a similar troubleshooting tree, progressing through the following questions: Is the Source Service mapped to the CMDB or NOT? Typically services that are defined in source applications, such as NSM and SPECTRUM, should be managed and aligned with services in the CMDB. This report allows you easily locate those Services that are defined in various instances of the source application but which, for some reason have not been mapped to a service within the CMDB. A few possible reasons for this can be: This is a rogue service that the CMDB is not aware of A corresponding service has been defined in the CMDB but the corresponding Federated CI Mapping is not defined. There has been an active decision that this service shouldn t be managed by the CMDB Is the aligned CMDB Service Found or NOT? If the CMDB service is mapped, the next step would be to make sure that the CMDB service is actually found in the CMDB. This sub-report should typically not have any exceptions. Any services with the status Source service mapped to CMDB service but CMDB service NOT found is unexpected and requires a thorough technical analysis. Is the aligned CMDB Service Active or NOT? Finally, it is important to find out if there are services which have been defined and managed in source applications but which have been tagged as inactive in the CMDB. This typically indicates that the CMDB service is incorrectly tagged as inactive or that the service no longer needs to be managed by the source application. These services require further analysis to determine the true root cause. As noted earlier, when you have reached the most granular state based on status, you can also analyze the exception based on if the aligned source application is NSM or SPECTRUM. Finally, depending on the data collected, each of the summary reports can link to one or more detailed reports that list the service as defined in the source application and applicable details regarding the aligned CMDB services. 34

45 CMDB/Source Services Report Overview Source Services Report Hierarchy Following is the complete hierarchy of the summary reports contained within the CMDB Service report: Source service mapped to CMDB service Source service mapped to CMDB service and CMDB service found Source service mapped to CMDB service, CMDB service found and active NSM SPECTRUM Source service mapped to CMDB service, CMDB service found but NOT active NSM SPECTRUM Source service mapped to CMDB service but CMDB service NOT found NSM SPECTRUM Source service NOT mapped to CMDB service NSM SPECTRUM 35

46 CMDB/Source Services Report Overview Examples / Use cases Following are several examples on how this report can be used: Service in CA NSM NOT mapped to a CMDB Service 1. Launch InfoView and select the Source Services Report 2. Click the Source service NOT mapped to CMDB service link in the Status area or on the corresponding portion of the pie chart. 36

47 CMDB/Source Services Report Overview 3. Click the count value that corresponds to the source application you wish to view details for (for example, select 18 for NSM in the above example). Service in SPECTRUM mapped to a inactive service in the CMDB 1. Launch InfoView and select the Source Services Report 2. Click the Source service mapped to CMDB service link in the Status area or on the corresponding portion of the pie chart. 37

48 CMDB/Source Services Report Overview 3. Click the Source service mapped to CMDB service and CMDB service found link or the corresponding portion of the pie chart. 4. Click the Source service mapped to CMDB service, CMDB service found but NOT active link or the corresponding portion of the pie chart. 38

49 CMDB/Source Service Content Report 5. Click the count value that corresponds to the appropriate source application (in the above example, click 2 for SPECTRUM). CMDB/Source Service Content Report The CMDB Service Content Report and the Source Service Content Reports allow you to drill into a specific service to analyze the CIs associated with that service, in order to see how they are aligned with the CIs in its counterparts (CMDB/source application) corresponding service. These reports are organized so that you first see a list of all services that are associated with its counterpart (CMDB service/source Application Service) together with some basic information, such as name of both the CMDB as well as the aligned Source Application Service, the number of CIs and what MDR is used to align them. You can then select a service and the source application type that you want to analyze further. This will display pie chart indicating the status of the CIs/source objects that belong to this service, based on how they are aligned with the CIs/source objects in the counterpart (CMDB/Source Application) corresponding service. Finally you can drill into a detailed report listing all CIs or all CIs with a specific status. The detailed reports list the CMDB CI Class, CMDB CI Name, Source Object Class, Source Object Name and status for each CI. CMDB Service Content Report The basic flow of the CMDB Service Content Report is as follows: Select the CMDB Service to be analyzed This first view lists all CMDB Services that have at least one associated Source Application Service. To simplify the selection process the CMDB Service Class and the number of CIs in each service are also displayed. 39

50 CMDB/Source Service Content Report Select the aligned Source Service to be analyzed The next view lists all Source Services that are aligned with the selected CMDB Service, grouped by application type. To simplify selection of the correct view, the Source Application Service, Source Application service Class, Numbers of managed CIs, Source Application Version, MDR Class & Name and the Source Application database server are also listed. View/Analyze the distribution of the CIs status This pie-chart display indicates the distribution of the CIs status based on how the CIs in the CMDB service are aligned to the managed objects in the corresponding source application service. Potential statuses include: Source object related to CMDB service child CI found and is included in source service related to CMDB service Source object related to CMDB service child CI found but NOT included in source service related to CMDB service Source object related to CMDB service child CI NOT found Drill down to a detailed list of CIs with a specific status Finally, select a status that you would like to analyze further and click on the number in the column CI Count. This will open a detailed report listing all CIs with this specific status. To simplify the analysis the name and class for both the CMDB CI as well as the source objects are listed when applicable. CMDB Service Content Report Hierarchy Following is the complete hierarchy of the summary reports within the CMDB Service report: All CMDB Services with at least one aligned Source Service Corresponding Source Services grouped by application name Pie-chart showing distribution of associated CIs status Detailed report of all CIs Detailed report of CIs with status Source object related to CMDB service child CI found and is included in source service related to CMDB service Detailed report of CIs with status Source object related to CMDB service child CI found but NOT included in source service related to CMDB service Detailed report of CIs with status Source object related to CMDB service child CI NOT found 40

51 CMDB/Source Service Content Report Examples / Use cases Following are a few examples of how this report can be used: Locate source objects that are managed in a NSM Instance, aligned to a CMDB CI and a member of a CMDB Service, but which are not included in the corresponding NSM service 1. Launch InfoView and select the CMDB Service Content Report 2. Click on the CMDB service you are analyzing. In our example this is Payment Processing 3. Select and click on the corresponding Source Service in the NSM section. In our example it is called Payment Processing in NSM as well. 41

52 CMDB/Source Service Content Report 4. Locate the status Source object related to CMDB service child CI found but NOT included in source service related to CMDB service in the table. This number indicates how many source objects have this status. These objects need to be analyzed further since it is very likely that they should be managed by the existing NSM service. 5. Click on the number behind that status. 42

53 CMDB/Source Service Content Report Review a CMDB service that is aligned to a service in a SPECTRUM Instance, and list all related CMDB CIs that aren t aligned with any objects in the SPECTRUM instance. 1. Launch InfoView and select the CMDB Service Content Report 2. Click on the CMDB service you are analyzing. In our example this is Payment Processing 3. Select and click on the corresponding Source Service in the SPECTRUM section. In our example the service is called Payment Processing in SPECTRUM as well. 4. Locate the status Source object related to CMDB service child CI NOT found in the table. This number indicates how many source objects have this status. These objects should be analyzed further to determine if they should be managed by this SPECTRUM Instance and, if so, added to its service. 5. Click on the number behind the status we just located to open a detailed report listing all these objects. Source Service Content Report The basic flow of the Source Service Content Report is as follows: Select the Source Service to be analyzed This first view lists all Source Services that have at least one associated CMDB Service. Services are grouped by the Source Application. To simplify the selection process, the Source Service Name & Class, CMDB service name & class, Source Application & Version, Source Application Database server, MDR Class & name and the number of child objects in the managed service are also displayed. 43

54 CMDB/Source Service Content Report View/Analyze the distribution of the CIs status This pie-chart displays the distribution of the Source Objects status based on how the objects in the source service are aligned to the CIs in the corresponding CMDB service. Potential statuses include: CMDB CI related to source service child object found, active and included in CMDB service related to source service CMDB CI related to source service child object found, active but NOT included in CMDB service related to source service CMDB CI related to source service child object found but NOT active CMDB CI related to source service child object NOT found Detailed list of source objects with a specific status Finally, select a status that you would like to analyze further and click on the number in the column Child Item Count. This will open a detailed report listing all source objects with this specific status. To simplify the analysis the name and class for both the source objects as well as the CMDB CIs are listed when applicable. CMDB Service Content Report Hierarchy Following is the complete hierarchy of the summary reports within the CMDB Service report:. All Source Services that are aligned to a CMDB Source Service Pie-chart showing distribution of the associated source objects status Detailed report of all source objects Detailed report of CIs with status CMDB CI related to source service child object found, active and included in CMDB service related to source service Detailed report of CIs with status CMDB CI related to source service child object found, active but NOT included in CMDB service related to source service Detailed report of CIs with status CMDB CI related to source service child object found but NOT active Detailed report of CIs with status CMDB CI related to source service child object NOT found 44

55 CMDB/Source Service Content Report Examples / Use cases Following are several examples of how these reports can be used: Identify source objects that are managed by a NSM service but which do not have an aligned CI in the CMDB 1. Launch InfoView and select the Source Service Content Report 2. Click on the NSM service you are analyzing. In our example this is General Ledger 45

56 CMDB/Source Service Content Report 3. Locate the status CMDB CI related to source service child object NOT found in the table below the pie-chart. This number indicate how many source objects have this status. These objects should be analyzed further to determine if they should be defined as individual CIs in the CMDB. 4. Click on the number behind the status we just located to open a detailed report listing all these objects. Identify source objects that are managed by a SPECTRUM service but whose aligned CMDB CI is inactive. 1. Launch InfoView and select the Source Service Content Report 2. Click on the SPECTRUM service you are analyzing. In our example this is General Ledger 3. Locate the status CMDB CI related to source service child object found but NOT active in the table. 46

57 CIs/Source Object Exceptions Reports This number indicates the number of source objects managed in the SPECTRUM service with an aligned CMDB CI that is inactive. These objects should be analyzed further since it is likely that they are incorrectly inactivated or should no longer be managed in the source application. 4. Click on the number behind the status we just located to open a detailed report listing all these objects. CIs/Source Object Exceptions Reports The CI Exceptions Report and Source Object Exceptions Report allow you to easily and quickly find all CIs with a specific status based on how the CIs and source object are aligned to each other. These reports are organized so that you first see a pie-chart that provides a visual break-down of the status of the alignment between all CIs and their aligned source objects. From this you can drill down into a specific status and analyze it further, based on source application, and then even further based on a specific instance (MDR) of the source application. In addition, each summary report allows you to drill into detailed reports of all CIs/source objects aligned with a specific exception/status, source application and even individual instances. The detailed reports list all CIs/source objects that match the current summary report. When applicable, the detailed report lists information such as CMDB CI name & Class, Source Objects name, class & type, Source Application Name & Version, MDR Class & Name, Source Database Server and count of CIs/objects matching this fingerprint. CI Exceptions Report Following is the basic flow of the CI Exceptions Report: Select the CI status that should be analyzed This first view displays a pie-chart visualizing the distribution of the CIs statuses based on how they are aligned with the corresponding source objects. Potential statuses include: CI NOT active CI active but MDR provider NOT found CI active, MDR provider found but MDR to source mapping NOT found CI active, MDR provider found, MDR to source mapping found but source object NOT found CI active, MDR provider found, MDR to source mapping found and source object found 47

58 CIs/Source Object Exceptions Reports From this view you can either drill into a detail report by clicking on the numbers in the Count of CIs column, or drill into more detailed summary reports by clicking on either the corresponding part of the pie-chart or the corresponding status text in the table. Select the source application type to be analyzed The next graph displays a bar chart representing each source application that has at least one CI with this status. If no source application is mapped the bar will instead be tagged with Source Mapping Not Found. If the user clicks on one of the numbers in the column Count of CIs a detailed report will be displayed. The other option is to drill further into the summary report by clicking on one of the bars or the Source Application Name in the table. This will open a summary report as described in the bullet below. View/Analyze in what instances (MDRs) these object are located. This view displays all CI s of the selected status, grouped by the instance of the selected source application on which they have corresponding source objects. Each instance is represented by a bar named by its MDR (to be unique a combination of the MDR Class and MDR Name is used). Just as with all other summary reports, the corresponding detailed reports can be reached by clicking on the numbers in the Count of CIs column. CI Exceptions Report Hierarchy Following is the complete hierarchy of the summary reports within the CI Exceptions Report: CIs with status CI NOT active NSM List of all matching MDRs (MDR Class & MDR Name tuple) SPECTRUM List of all matching MDRs (MDR Class & MDR Name tuple) Source Mapping Not Found CIs with status CI active but MDR provider NOT found Source Mapping Not Found CIs with status CI active, MDR provider found but MDR to source mapping NOT found Source Mapping Not Found CIs with status CI active, MDR provider found, MDR to source mapping found but source object NOT found NSM 48

59 CIs/Source Object Exceptions Reports List of all matching MDRs (MDR Class & MDR Name tuple) SPECTRUM List of all matching MDRs (MDR Class & MDR Name tuple) CIs with status CI active, MDR provider found, MDR to source mapping found and source object found NSM List of all matching MDRs (MDR Class & MDR Name tuple) SPECTRUM List of all matching MDRs (MDR Class & MDR Name tuple) Examples / Use cases Following are several examples of how this report can be used: Identify inactive CIs that still are managed by source applications 1. Launch InfoView and select the CI Exceptions Report 49

60 CIs/Source Object Exceptions Reports 2. Click on the pie-chart representing CI NOT active or, to directly go to a detailed report, click on the number behind this status in the column Count of CIs 3. Click on the number in the column Count of CIs corresponding to the Source Application you are interested in or click after the CI NOT active This displays a list of all Source Objects that are aligned with CMDB CIs that are tagged as inactive. These objects require additional analysis since this is an indication that either the CI is incorrectly marked as inactive or that the source object maybe shouldn t be managed. 50

61 CIs/Source Object Exceptions Reports Identify CIs that have a valid mapping to a source objects but whose corresponding asset is no longer managed by the source application. 1. Launch InfoView and select the CI Exceptions Report 2. Click on the Pie-chart representing CI active, MDR provider found, MDR to source mapping found but source object NOT found 3. Click on the Number in the column Count of CIs corresponding to the Source Application you are interested in - or click after the CI active, MDR provider found, MDR to source mapping found but source object NOT found This displays a list of all CIs that are mapped to a source object that is no longer managed by the source application. These CIs require additional analysis to determine what is broken. The object should either still be managed or the change order responsible for removing the object should also include removal of the alignment from the CMDB. 51

62 CIs/Source Object Exceptions Reports Source Object Exceptions Report Following is the basic flow of the Source Object Exceptions Report: Select the Source object status that should be analyzed This first view displays a pie-chart visualizing the distribution of the Source Objects statuses, based on how they are aligned with the corresponding CMDB CIs. Potential statuses include: MDR provider mapping to CI NOT found MDR provider mapping to CI found but CI NOT found MDR provider mapping to CI found, CI found but NOT active MDR provider mapping to CI found, CI found and active From this view you can either drill into a detail report by clicking on one of the numbers in the table or drill into more detailed summary reports by clicking on either the corresponding part of the pie-chart or the corresponding status text in the table. Select the source application type to be analyzed The next graph displays a bar chart that represents each source application that has at least one Source Object with the selected status. If you clicks on one of the numbers in the column Count of Source Objects a detailed report will be displayed. Alternatively, you can drill further into the summary report by clicking on one of the bars or the Source Application Name in the table. This will open a summary report as described in the next item. View/Analyze the instances in which these source objects are located This view displays all source objects of the selected status, grouped by the instance of the source application they are managed by. Each instance is visualized with a bar named by its MDR (to be unique a combination of the MDR Class and MDR Name is used). Just as with all other summary reports, the corresponding detailed reports can be reached by clicking on the numbers in the Count of Source Objects column. 52

63 CIs/Source Object Exceptions Reports Source Object Exceptions Report Hierarchy Following is the complete hierarchy of the summary reports within the Source Object Exceptions Report: Source Objects with status MDR provider mapping to CI NOT found NSM List of all matching MDRs (MDR Class & MDR Name tuple) SPECTRUM List of all matching MDRs (MDR Class & MDR Name tuple) Source Objects with status MDR provider mapping to CI found but CI NOT found NSM List of all matching MDRs (MDR Class & MDR Name tuple) SPECTRUM List of all matching MDRs (MDR Class & MDR Name tuple) Source Objects with status MDR provider mapping to CI found, CI found but NOT active NSM List of all matching MDRs (MDR Class & MDR Name tuple) SPECTRUM List of all matching MDRs (MDR Class & MDR Name tuple) Source Objects with status MDR provider mapping to CI found, CI found and active NSM List of all matching MDRs (MDR Class & MDR Name tuple) SPECTRUM List of all matching MDRs (MDR Class & MDR Name tuple) 53

64 CIs/Source Object Exceptions Reports Examples / Use cases Following are several examples of how this report can be used: Find all source objects not aligned to a CMDB CI 1. Launch InfoView and select the Source Object Exceptions Report 2. Click on the pie-chart representing MDR provider mapping to CI NOT found or, to directly go to a detailed report, click on the number behind this status in the column Count of Source Objects 54

65 CIs/Source Object Exceptions Reports 3. Click on the Number in the column Count of Source Objects corresponding to the Source Application you are interested in or click after the row MDR provider mapping to CI NOT found This displays a list of all Source Objects that do not have an aligned CI. Note: Typically, this represents a normal state since not all managed objects should also be managed in the CMDB. Find all managed objects in SPECTRUM that are mapped to an inactive CMDB CI. 1. Launch InfoView and select the Source Object Exceptions Report 2. Click on the Pie-chart representing MDR provider mapping to CI found, CI found but NOT active 55

66 CIs/Source Object Exceptions Reports 3. Click on the bar-chart representing SPECTRUM or, to directly go to a detailed report, click the number behind SPECTRUM in the column Count of Source Objects 4. Click on the number in the column Count of Source Objects after SPECTRUM or, after a specific instance (MDR Class/ Name) if you would like to analyze an individual SPECTRUM instance. This displays a list of all source objects that are mapped to an inactive CI. These objects may require additional analysis since this may indicate that either the CI is incorrectly marked as inactive or the source object may be shouldn t be managed. 56