Oncommand Insight 6.4 Data Warehouse Administration Guide

OnCommand® Insight 6.4 Data Warehouse Administration Guide

NetApp, Inc. Telephone: +1(408) 822-6000 Part number: 215-07588_A0 495 East Java Drive Fax: +1(408) 822-4501 March 2013 Sunnyvale, CA 94089 Support telephone: +1(888) 4-NETAPP U.S. Web: www.netapp.com Feedback: [email protected]

Table of Contents | 3

Contents

Welcome to OnCommand Insight Data Warehouse ...... 6 Data Warehouse features ...... 6 Data Warehouse components ...... 6 OnCommand Insight Data Warehouse Portal ...... 6 OnCommand Insight Reporting Portal ...... 8 Report authoring tools ...... 8 Data Warehouse software components ...... 8 Data Warehouse processes ...... 9 How Data Warehouse extracts data ...... 9 ETL frequency and date data ...... 10 Historical data retention in Data Warehouse ...... 11 Data retention, ETL, and time periods ...... 12 OnCommand Insight product portfolio ...... 13 Where to find more information about OnCommand Insight ...... 14 Videos for OnCommand Insight ...... 14 OnCommand Insight product documentation ...... 15 Displaying Cognos or OnCommand Insight documentation ...... 16 Getting started with Data Warehouse ...... 18 Accessing the Data Warehouse Portal ...... 19 Accessing MySQL using the command line interface ...... 20 Connecting Data Warehouse to OnCommand Insight servers ...... 21 Data Warehouse database build from history overview ...... 22 Forcing an update of annotations for Data Warehouse ...... 23 Adding a job that builds from history ...... 24 Canceling a build from history job ...... 26 Scheduling daily builds ...... 26 Backing up the Data Warehouse database ...... 28 Backing up custom reports and reporting artifacts ...... 29 Restoring the Data Warehouse database ...... 30 Managing Data Warehouse and Reporting user accounts ...... 31 Accessing the Data Warehouse and Reporting ...... 31 Reporting user roles ...... 31 4 | OnCommand Insight Data Warehouse Administration Guide

Adding a Reporting user ...... 33 Managing user accounts ...... 34 Configuring Reporting LDAP ...... 34 Setting up multiple tenancy in reporting ...... 36 Configuring user accounts ...... 37 Assigning users to business entities ...... 37 Troubleshooting setup issues ...... 39 Why I cannot see my annotations ...... 39 What to do with failing historical build points ...... 43 Troubleshooting incorrect report numbers ...... 43 Data Warehouse Administration ...... 44 Accessing the Data Warehouse Portal ...... 45 Connecting Data Warehouse to OnCommand Insight servers ...... 46 Managing jobs ...... 48 Scheduling daily builds ...... 49 Annotations ...... 50 Preparing annotations in OnCommand Insight ...... 51 Importing user-defined annotations into Data Warehouse ...... 51 Viewing the Annotations job in the Jobs list ...... 53 Updating annotations in OnCommand Insight reporting ...... 53 Using annotations in a Query Studio report ...... 55 Seeing the annotation changes in the database schema ...... 55 Setting email notifications ...... 57 Accessing the Reporting Portal ...... 57 Viewing the Data Warehouse documentation ...... 58 Viewing the Data Warehouse database schema ...... 59 Editing the site name and viewing system information ...... 60 Viewing the Data Warehouse version and upgrade history ...... 60 Advanced options ...... 61 Data Warehouse database build from history overview ...... 61 Skipping failed builds ...... 65 Resetting the Data Warehouse database or Reporting server ...... 67 Backing up the Data Warehouse database ...... 67 Backing up custom reports and reporting artifacts ...... 69 Restoring the Data Warehouse database ...... 69 Table of Contents | 5

Restoring and upgrading reports after upgrading from OnCommand Insight versions before 6.3 ...... 70 Troubleshooting Data Warehouse ...... 71 OnCommand Insight Data Warehouse user interface reference ...... 84 Annotations Page ...... 84 Connectors Page ...... 85 Jobs Page ...... 86 Schedule Page ...... 86 Email Notification Page ...... 87 Copyright information ...... 88 Trademark information ...... 89 How to send your comments ...... 90 Index ...... 91 6 | OnCommand Insight Data Warehouse Administration Guide

Welcome to OnCommand Insight Data Warehouse

The OnCommand Insight Data Warehouse is a centralized repository that stores data from multiple OnCommand Insight servers and transforms data into a common, multidimensional data model for querying and analysis. The OnCommand Insight Data Warehouse enables access to an open database consisting of several data marts that let you generate custom capacity and performance reports such as chargeback reports, trending reports with historical data, consumption analyses, and forecasting reports.

Data Warehouse features The OnCommand Insight Data Warehouse is an independent database made up of several data marts. Data Warehouse includes the following features: • Current and historical configuration and inventory data that enables you to create trending reports useful for forecasting and planning. • Several multi-dimensional historical data marts and an additional current-only inventory data mart. • An optimized database for predefined queries or user-defined queries. • A platform for integration with third-party reporting and business intelligence engines, including: • Configuration management databases • Financial accounting systems • Asset management systems

Data Warehouse components Data Warehouse contains several components. • Data Warehouse Portal • OnCommand Insight Reporting Portal • Report authoring tools

OnCommand Insight Data Warehouse Portal The Data Warehouse Portal is a web-based user interface that you use to configure options and set up fixed schedules to retrieve data. From the Data Warehouse Portal, you can also access the OnCommand Insight reporting portal. Using Data Warehouse, you can do the following: Welcome to OnCommand Insight Data Warehouse | 7

• Access the OnCommand Insight reporting portal to view predesigned reports or create custom reports using report authoring tools such as Business Insight Advanced, Query Studio, and Report Studio. • Consolidate multiple OnCommand Insight databases. • Manage connections to OnCommand Insight servers . • Check the status on current jobs or queries that are running. • Schedule Data Warehouse builds. • Edit the site name using the System Information. • View Data Warehouse version and upgrade history including specific information such as module versions, sites and licenses. • Import annotations. • Configure a build from history. • View Data Warehouse documentation and database schema. • Reset the Data Warehouse database. • Back up and restore the Data Warehouse database. • Troubleshoot Data Warehouse issues. • Manage user accounts. For instructions about using Data Warehouse administrative features, see the OnCommand Insight Data Warehouse User Guide.

Related concepts Data Warehouse database build from history overview on page 22

Related tasks Connecting Data Warehouse to OnCommand Insight servers on page 21 Managing jobs on page 48 Scheduling daily builds on page 26 Editing the site name and viewing system information on page 60 Viewing the Data Warehouse version and upgrade history on page 60 Importing user-defined annotations into Data Warehouse on page 41 Viewing the Data Warehouse database schema on page 59 Viewing the Data Warehouse documentation on page 58 Resetting the Data Warehouse database or Reporting server on page 67 Backing up the Data Warehouse database on page 28 Managing user accounts on page 34 8 | OnCommand Insight Data Warehouse Administration Guide

OnCommand Insight Reporting Portal You can use the OnCommand Insight Reporting Portal and the OnCommand Insight data model to run or create custom reports. You can generate reports in various formats, including HTML, PDF, CSV, and Excel. OnCommand Insight Data Warehouse accommodates multiple tenancy in reporting by allowing you to associate users with business units. With this feature, administrators can separate data or reports according to the attributes of a user or his affiliation. To see reports and dashboards that can be configured through the OnCommand Insight Reporting user interface, see the OnCommand Reporting Guide.

Report authoring tools The OnCommand Insight enterprise reporting data models provide data elements and interactive relationships among data elements that yield business views of the data. Using the data elements and relationships, you can create reports using Query Studio, Report Studio, Business Insight or Business Insight Advanced, which are report generation tools. You can use the following report authoring tools to create reports with OnCommand Insight data models: • With Query Studio, you drag and drop data elements to create customized ad hoc reports that address your business needs. Note: Although the OnCommand Insight documentation provides basic information about creating reports using Query Studio, for details about Query Studio format options, see the Cognos documentation. • With Report Studio, you can create more complex reports with complex filters, prompts, and conditions. You can create very complex reports using the Report Studio tool and OnCommand Insight data. Report Studio is a powerful tool, and its use is beyond the scope of this guide. • With Business Insight, you can create and assemble dashboards and create interactive reports. • With Business Insight Advanced, you can create rich, interactive reports with a tool that has all the functionality of Query Studio, Report Studio Express, and Analysis Studio. Note: For details about using Business Insight Advanced to create a report, see the video on the NetApp Community site: Creating an Adhoc Report video.

Some authoring tools are hidden for use only with advanced views. See information about switching between simple and advanced reporting views.

Data Warehouse software components OnCommand Insight Data Warehouse includes several software components. • MySQL database - backend repository for data mart tables • IBM Cognos - reporting engine for OnCommand Insight Welcome to OnCommand Insight Data Warehouse | 9

• Apache Derby Database - used for storing Cognos configuration and content • JBoss - Java Enterprise application server that hosts OnCommand Insight components • Apache Web Server/Tomcat - web front end and servlet engine for Cognos web interface

Data Warehouse processes Data Warehouse performs many types of processes.

ETL process The Extract Transform and Load (ETL) process retrieves data from multiple OnCommand Insight databases, transforms the data, and saves it into the data mart. The Data Warehouse build process is an ETL process. Jobs Data Warehouse performs and reports on jobs such as these: inventory, dimensions, capacity, port capacity, VM capacity, file system utilization, performance, capacity efficiency, licenses, history build, dynamic annotations, connector removal, skipped build, AutoSupport (ASUP) option, and maintenance jobs. Consolidation Data Warehouse supports the consolidation of multiple OnCommand Insight process servers into the same Data Warehouse database. In many configurations it may happen that the same object is reported from multiple connectors (that is, the same switch exists in two OnCommand Insight instances). In that case, Data Warehouse consolidates the multiple objects into one (a primary connector is chosen and the object’s data is taken from that connector only). Requests sent to By using OnCommand Insight Plan in the OnCommand Insight Client or by Data Warehouse using the Request Portal, storage administrators can initiate requests (for capacity and ports) and reservations (for volumes, capacity, and ports). Note: Only requests for capacity and ports are received from the OnCommand Insight Server and are sent to the Data Warehouse during the ETL process.

The Storage Capacity Planning Report includes a projection of capacity usage which is calculated from capacity requests.

How Data Warehouse extracts data The Extract, Transform, and Load (ETL) process retrieves data from multiple OnCommand Insight databases, transforms the data, and saves it into the data model. OnCommand Insight connectors invoke a series of batch jobs to extract data from multiple OnCommand Insight mySQL databases and publish the data in various data marts, as shown in the following diagram.

10 | OnCommand Insight Data Warehouse Administration Guide

The ETL process includes these individual processes:

Extract Takes data from multiple OnCommand Insight databases, transforms the data, and saves it into the data model. The process is performed against each OnCommand Insight instance at the same time. To ensure that data cleansing and deduplication is performed, it is not possible to split the ETL process into multiple scheduled ETL operations. Transform Applies business logic rules or functions to extract the data from the OnCommand Insight database. Load Loads the transformed data into public data models

ETL frequency and date data You should run the Extract, Transform, and Load (ETL) process only once per day. Two date data elements in the Date dimension are related to the daily ETL process. By default, the Cognos reporting engine treats all capacity and performance facts as additive. As a result, there is a risk of double counting capacity data if the ETL process is run multiple times per day without the proper time filters. The Date dimension, which is used in several data models, includes the following data elements that are affected by the ETL:

Is Day The "Is Day Representative" data element is set to a value of 1 (true) during the Representative first ETL process run during any given day. If the first ETL process is run at 1:00 a.m., Is Day Representative is set to 1 for all of the data loaded during the 1:00 a.m. ETL process. If a second ETL is scheduled later (for example, 1:00 p.m.), Is Day Representative is set to 0 (false) for the data loaded during that ETL process. Is Latest The "Is Latest" member is set to a value of 1 (true) after each ETL process completes. If the first ETL process is run at 1:00 a.m., Is Latest is set to 1 for all of the data loaded during the 1:00 a.m. ETL process. If another ETL process is scheduled later (for example, 1:00 p.m.), Is Latest is set to 1 for data loaded Welcome to OnCommand Insight Data Warehouse | 11

during the 1 p.m. ETL process. The ETL process also sets the 1:00 a.m. ETL load's Is Latest entry to 0 (false).

Historical data retention in Data Warehouse Data is maintained in Data Warehouse according to a schedule. Data Warehouse retains historical data based on the data marts and granularity of the data, as shown in the following summary:

Data mart Measured object Granularity Retention period Performance marts Volumes and Internal Hourly 14 days Volumes Performance marts Volumes and Internal Daily 13 months Volumes Performance marts Application Hourly 13 months Performance marts Host Hourly 13 months Performance marts Switch Performance 5 weeks for port Performance marts Switch Performance 13 months for host, storage and tape Capacity marts All (except individual Daily 13 months volumes) Capacity marts All (except individual Monthly representative 14 months and beyond volumes) Inventory mart Individual volumes Current state 1 day (or until next ETL)

In more detail, for capacity, performance, and resource data in the following tables, after 13 months Data Warehouse retains only one record per month instead of one record per day: • Application fact table (dwh_sa.sa_application_fact) • Capacity Efficiency fact table (dwh_capacity_efficiency.efficiency_fact) • Capacity fact table (dwh_capacity.capacity_fact) • Chargeback fact table (dwh_capacity.chargeback_fact) • File System Utilization fact table (dwh_fs_util.fs_util_fact) • Host fact table (dwh_sa.sa_host_fact) • Internal Volume Capacity fact table (dwh_capacity.internal_volume_capacity_fact) 12 | OnCommand Insight Data Warehouse Administration Guide

• Ports fact table (dwh_ports.ports_fact) • Qtree Capacity fact table (dwh_capacity.qtree_capacity_fact) • Storage and Storage Pool Capacity fact table (dwh_capacity.storage_and_storage_pool_capacity_fact) • Volume capacity fact table (dwh_capacity.vm_capacity_fact)

Data retention, ETL, and time periods OnCommand Insight Data Warehouse retains data obtained from the Extract, Transform, and Load (ETL) process for different time periods based on the different data marts and time granularity of the data.

Performance Marts and hourly granularity for volumes and internal volumes The OnCommand Insight Data Warehouse records the hourly averages, hourly maximums and access bit for each hour of the day (twenty-four data points) for 14 days. The access bit is a Boolean value that is true if the volume was accessed or false if the volume was not accessed during the hourly interval. All 24 data points for the preceding day are obtained during the first ETL process of the day. You do not need to run one ETL per hour to gather the hourly data points. Running additional ETLs during the day does not obtain any performance information from the OnCommand Insight Servers.

Performance Marts and daily granularity for volumes and internal volumes Each day when the ETL is processed, the daily averages for the preceding day are calculated and populated within the Data Warehouse. The daily average is a summary of the 24 data points for the previous day. The performance data marts retain daily summaries for volumes and internal volumes for 13 months.

Capacity marts and daily granularity The Capacity marts provide daily measurements for various capacity facts on a daily basis for a period of 13 months. The capacity facts in Data Warehouse are current as of the last data source acquisition for the device prior to the ETL.

Capacity marts and monthly granularity Data Warehouse retains daily capacity data for 13 months. After the 13-month threshold is reached, the capacity data is summarized on a monthly basis. The monthly data is based on the values reflected by the date that is the month representative date. The following table shows which monthly data is included in the monthly summary.

Date Is Month Representative Allocated capacity value Jan 1 1 (True) 50 TB Welcome to OnCommand Insight Data Warehouse | 13

Date Is Month Representative Allocated capacity value Jan 2 0 (False) 52 TB ...... Jan 31 0 (False) 65 TB Feb 1 1 (True) 65 TB

Based on the table, a monthly report would show 50 TB allocated for January and 65 TB allocated for February. All of the other capacity values for January would not be included in the monthly summary.

Inventory mart The Inventory data mart is not historical. Each time an ETL is run, the Inventory mart is erased and rebuilt from scratch. So, any reports generated out of the Inventory mart do not reflect historical inventory configuration.

OnCommand Insight product portfolio OnCommand Insight is a suite of products that boost the quality and efficiency of your storage environment by providing near real-time visibility, multi-vendor and multi-protocol support, and end-to-end service-level views of your application storage path. The OnCommand Insight portfolio provides the tools for you to manage your environment. You can do the following: • Optimize the assets that you have on the floor, according to space, performance, and usage criteria. • Optimize the business activities, such as application or storage service, on your assets. The OnCommand Insight portfolio includes the following products:

14 | OnCommand Insight Data Warehouse Administration Guide

OnCommand Helps administrators focus on maintaining storage service on their storage Insight Assure resources. Lets administrators establish global, application, host, or path-based service policies and manage the effects of change, risk, and service-level violations of those policies on availability and performance. OnCommand Helps administrators focus on their storage resources. Collects and maintains Insight Perform service performance information to help administrators reclaim under-utilized storage resources, manage tiers, analyze storage virtualization efficiency, improve load balancing, troubleshoot congestion and contention, and improve resource utilization to optimize services. OnCommand Helps administrators focus on both storage resources and the services on those Insight Plan assets. Provides administrators with an end-to-end view of resource order, the storage allocation process, and trend usage so that they can manage resource reservations and forecast consumption and resource needs. Administrators can report on costs for storage services by business entity or tier and use this information for chargebacks on storage usage. Business level roll-up reporting helps storage administrators improve capacity planning and optimize consumption by application and tier.

OnCommand Insight Assure, OnCommand Insight Perform, and OnCommand Insight Plan use the same integrated discovery component. This discovery component provides visibility into storage availability, resource inventory, and host-to-storage access paths. Administrators can also gain visibility into the path from virtual machines to arrays for organizations deploying VMware ESX technology combined with VMware vCenter (VirtualCenter) technology. The Inventory features are the foundation features for the OnCommand Insight suite and are used in OnCommand Insight Assure, OnCommand Insight Perform, and OnCommand Insight Plan. OnCommand Insight Assure, OnCommand Insight Perform, and OnCommand Insight Plan also use the same report authoring tools and the same Data Warehouse platform.

Where to find more information about OnCommand Insight You can find more information about OnCommand Insight on the NetApp Support Site and in other OnCommand Insight documentation.

Videos for OnCommand Insight You can access how-to videos that show you how to perform some actions in OnCommand Insight. The videos are located on the OnCommand Insight Customer Community, a forum for customers. Many individual topics in the OnCommand Insight documentation include links to specific videos. Note: To see OnCommand Insight videos, use your web browser to access the Customer Community at the following link: https://communities.netapp.com/community/ Welcome to OnCommand Insight Data Warehouse | 15

products_and_solutions/storage_management_software/oncommand-insight/oncommand-insight- videos/content

You need a user name and password for some features of this community. To obtain them, click the Join Now link. The following video topics and more are included in the Community: • How to tell OnCommand Insight about your tiering • How to identify over utilized disks in OnCommand Insight • How to view orphaned storage • How to set thresholds for storage efficiency • How to identify candidates for tiering • How to identify candidates for host virtualization • How to group violations • How to set business entity annotations

OnCommand Insight product documentation The OnCommand Insight products are accompanied by a set of guides. You can access the following documents from the NetApp Support Site at support.netapp.com/ documentation/productsatoz/index.html.

OnCommand Insight Helps new OnCommand Insight users set up and customize their installed Getting Started Guide system and begin using it for improved efficiency. Note: Information about OnCommand Insight is available from the OnCommand Insight Client Help menu and from the OnCommand Insight Administration portal.

OnCommand Report Provides an overview of suite architecture with instructions to get the Installation and system up and running, discover the logical and physical storage resources Administration Guide in your storage environment, and perform administrative tasks. Describes the configuration parameters and some installation procedures for data sources used by OnCommand Insight. Provides recommended methods of discovering your storage environment for the OnCommand Insight deployment.

OnCommand Insight Provides information about the tools and features to help you gain visibility Inventory User Guide into your SAN or NAS inventory environment. The Inventory features are the foundation used by all other products in the OnCommand Insight suite. After looking at the OnCommand Insight Getting Started Guide, use this guide to learn about basic features common across all OnCommand Insight modules. 16 | OnCommand Insight Data Warehouse Administration Guide

OnCommand Insight Provides an overview of how to use OnCommand Insight to analyze and Assurance User validate your storage network environment and to automate monitoring of Guide operations, as well as procedures for making safe changes without disrupting availability. OnCommand Insight Provides an overview of how to use OnCommand Insight to reclaim under- Performance User utilized resources, manage tiers, identify multipath risks, and troubleshoot Guide ongoing performance bottlenecks. OnCommand Insight Provides an overview of how to use OnCommand Insight to enable Planning User Guide educated capacity management decisions by managing the end-to-end resource order and allocation process. Describes how system administrators can communicate storage capacity requirements to SAN managers using OnCommand Insight Connect Applications web access instead of the full OnCommand Insight feature set.

OnCommand Describes reports from the centralized reports portal that support viewing Reporting Guide critical inventory and capacity-related information from the data warehouse. Describes the metadata model upon which OnCommand Insight reports are based. Information in this guide is also available from the OnCommand Insight Data Warehouse portal and in the OnCommand Insight Reporting Connection. Note: This guide differs from the OnCommand Report User Guide, which describes how to use OnCommand Report.

OnCommand Insight Describes a data warehouse repository that consolidates multiple Data Warehouse OnCommand Insight operational databases in an easy-to-query format. Administration Guide OnCommand Insight Provides an overview of how to use the API interface to enable integration Connect API with other applications, such as reporting and monitoring systems. Helps Reference customers and Independent Software Vendors (ISVs) to develop applications using the OnCommand Insight API interface.

Displaying Cognos or OnCommand Insight documentation You can find information about OnCommand Insight Data Warehouse in the Reporting portal. However, to find details about Cognos features, such as how to configure SMTP services, refer to the Cognos documentation.

Steps

1. From the Data Warehouse Main Menu, select OnCommand Insight Reporting Portal. Welcome to OnCommand Insight Data Warehouse | 17

2. Enter your user name and password and click OK.

3. To open the OnCommand Insight Reporting Portal, select Insight Reporting Content.

4. To access Cognos documentation, click the question mark (?). 5. To access Data Warehouse and Reporting documentation, from the Launch menu, select a Help option. 18 | OnCommand Insight Data Warehouse Administration Guide

Getting started with Data Warehouse

OnCommand Insight Data Warehouse enables you to configure options needed before generating reports that include your data. Data Warehouse contains many features; however, you need to use only a few of them to get started. To set up Data Warehouse, you use options in the Data Warehouse Portal.

About this task To set up OnCommand Insight Data Warehouse, a storage administrator should complete the following procedures: • Accessing the Data Warehouse portal • Connecting Data Warehouse to OnCommand Insight servers • Building the database from history • Setting up backup and restore processes Additionally, a storage administrator might want to complete the following procedures. • Accessing MySQL using the command line interface • Scheduling daily builds • Setting up multiple tenancy in reporting • Troubleshooting setup issues • Why can't I see my annotations? • What should I do with failing historical build points? If this is the first time you are using the Data Warehouse Portal, you must set up Data Warehouse before any information can appear on the Jobs page. You also need to repeat this setup process after resetting the Data Warehouse database.

Related concepts Data Warehouse database build from history overview on page 22 Setting up multiple tenancy in reporting on page 36 Why I cannot see my annotations on page 39 What to do with failing historical build points on page 43

Related tasks Accessing the Data Warehouse Portal on page 19 Accessing MySQL using the command line interface on page 20 Connecting Data Warehouse to OnCommand Insight servers on page 21 Scheduling daily builds on page 26 Getting started with Data Warehouse | 19

Backing up the Data Warehouse database on page 28 Restoring the Data Warehouse database on page 30

Accessing the Data Warehouse Portal The OnCommand Insight Data Warehouse Portal is a web-based user interface that you can use to update connector information, view job queues, access documentation and schema diagrams, perform backups, and update builds.

About this task The following is the default user name and password. It is a good idea to change these defaults after installation. • Username: admin • Password: admin123

Steps

1. Open a web browser and enter the following URL: http:///dwh 2. Enter your username and password. 3. Click OK. The Data Warehouse Portal opens.

20 | OnCommand Insight Data Warehouse Administration Guide

Accessing MySQL using the command line interface In addition to accessing Data Warehouse data elements through the report authoring tools (such as Query Studio and Report Studio), you can obtain access to Data Warehouse data elements directly by connecting as a MySQL user. You might want to connect as a MySQL user to use the data elements in your own applications.

About this task There are many ways to connect. The following shows one way. When accessing MySQL, consider the following issues: • Connect to the MySQL database on the machine where Data Warehouse is installed. • The MySQL port is “3306” by default; however, you can change it during installation. • The username and password is: dwhuser/netapp123

Steps

1. On the machine where Data Warehouse is installed, open a command line window. 2. Access the MySQL directory in the OnCommand Insight directory. 3. Type the following user name and password: mysql -udwhuser -pnetapp123 The following is displayed, depending on where Data Warehouse is installed:

c:\Program Files\OnCommand Insight\mysql\bin> mysql -udwhuser -pnetapp123

Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 882 Server version: 5.1.28-rc-community MySQL Community Server (GPL)

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

4. To show the Data Warehouse databases, type the following: show databases The following is displayed:

| dwh_ports | +------+

Connecting Data Warehouse to OnCommand Insight servers Connectors establish connections from the OnCommand Insight Data Warehouse to the OnCommand Insight servers. You can connect Data Warehouse with one or more OnCommand Insight servers. You can add or remove connections to or from OnCommand Insight databases.

About this task Data Warehouse assigns a global unique ID to the connector that is used in conjunction with the connector name. After adding a connector, Data Warehouse queries the OnCommand Insight database for the OnCommand Insight site name and version. You can choose to connect to a data source with or without SSL. Choosing the secure data source forces the connection to use SSL when communicating with the OnCommand Insight remote database. Data Warehouse can provide a consolidated view of data from multiple OnCommand Insight installations. This consolidated database provides the following information: • Globally Unique Identifiers: Each object is assigned a globally unique ID that is independent of the IDs used by individual sites, to avoid conflicting IDs and enable duplicate detection. These IDs are shared between all the data marts. This ID is the Globally Unique ID (GUID) in the Comment column of the Inventory data mart tables. • No duplication: Entities that exist in multiple OnCommand Insight databases are registered only once in the consolidated database. • Current record: The data in the consolidated database (Inventory data mart) is always the most up-to-date possible. When you add or edit a connection, you can also test the connection. The test does the following: • Verifies the host IP address, user name, and password and ensures that a connection can be established. Invalid connections appear in red. • Compares the OnCommand Insight version to the Data Warehouse version. If the versions are not compatible, an error message appears. • Verifies that the OnCommand Insight database has not been changed or restored to a different database as seen by the last Data Warehouse processing. If there has been a change, an error message appears.

Steps 1. From the Data Warehouse Main Menu, select Connectors. The Connectors table appears blank at first and shows connector information after you add a connector. 2. Click New to add a new connector. 22 | OnCommand Insight Data Warehouse Administration Guide

3. Enter the following:

Encryption To enable Data Warehouse requests to be made using SSL encryption, select Enabled. Name A connector name that will identify the connector on the Connectors view. Host Host IP address User name "inventory" Note: Using this user name and password, you can log into the remote OnCommand Insight database and perform queries on the data. You should change the default user name and password as soon as possible.

Password "sanscreen"

4. To specify the port to use for TCP connections to the host, click Advanced and enter the TCP port number. 5. To specify the port (other than the default port) to use for HTTPS connections to the host, click Advanced and enter the port number. 6. Click Test. Data Warehouse tests the connection. 7. Click Save. If you enter multiple connections for multiple installations, Data Warehouse invokes independent build processes, one for each database from which data should be extracted. Each such build process extracts data from an OnCommand Insight database and loads it into the consolidated database.

Data Warehouse database build from history overview You can build the Data Warehouse database using historical data in your OnCommand Insight server. Data Warehouse extracts data from the OnCommand Insight servers and builds the Data Warehouse data marts according to the build from history schedule. This option does not require a special license and inventory data is included in the build. However, to build capacity information, the OnCommand Insight Plan and OnCommand Insight Perform licenses are required. If any build (from history or current) has already been performed, the build cannot be done on dates before the last job. This means if you perform a current build, you cannot build from history. More specifically, if you performed builds from history that ended on Jan 1, 2012, you cannot perform any build on the year 2011. If the history build does not include a day or two of any unsuccessful ETL processes, do not try building history for just these few days. Historical data is for longer periods and a day or two is not Getting started with Data Warehouse | 23

going to change trending significantly. If you do want to rebuild from history, rebuild the entire history. The Build from History view displays all build jobs from all connectors. For example, the view might display an inventory job for every connector, a port capacity job for every build run, and an annotations job. Before you configure the Build from History, the following must occur: • Connectors must be configured. • At least one of the connectors must have history information. • Annotations should be entered in OnCommand Insight and updated (from the OnCommand Insight Main Menu, Troubleshooting > Force Update of Annotations for DWH).

Forcing an update of annotations for Data Warehouse You can initiate an update of annotations from OnCommand Insight to Data Warehouse.

About this task You can update annotations using one of two options: • Including deleted objects: This includes data about devices that no longer exist such as hosts, storage arrays, or switches that were removed. This is needed if you want to build Data Warehouse data with historical data points. • Not including deleted objects: Choose this option if you want to exclude deleted objects.

Steps

1. Access the OnCommand Insight Administration web-based portal.

24 | OnCommand Insight Data Warehouse Administration Guide

2. From the OnCommand Insight Main Menu, select Troubleshooting > Force Update of Annotations for DWH (include deleted objects).

Adding a job that builds from history You can build the Data Warehouse database using historical data that is kept in your OnCommand Insight server.

Before you begin Before you build from history, you should update annotations in the OnCommand Insight Client and then force an update of annotation information for Data Warehouse.

Steps

1. Access the Data Warehouse Portal at http:///dwh. 2. From the Advanced section of the DWH Main Menu, select Build from History.

Getting started with Data Warehouse | 25

3. Click Configure.

4. Enter the start and end times. To display a calendar from which you can select a date, click the down arrow near the month. 26 | OnCommand Insight Data Warehouse Administration Guide

The time format depends upon the locale of the Data Warehouse server. The start and end times must be within the range of history contained in all the OnCommand Insight servers to which Data Warehouse is connected, as set in the Data Warehouse portal Connectors option. The default start and end times reflect the maximum valid period. Note: Configuring a non-realistic schedule such as “Daily for 4 years” results in 1460 build cycles, which could take 10 days to complete.

5. Choose the time at which you want the job to run. This ensures that the Data Warehouse build job runs automatically at the time you specify. 6. Choose the interval. 7. Choose the date during the month or day of the week when the build from history will take place. If you select a monthly or weekly interval, the Day field appears. If you selected monthly, then Day is a date. If you selected weekly, Day is Sunday through Saturday. 8. Choose the hour when the build will take place. 9. Optionally, to return the options to default settings, click Reset. 10. Click Save. 11. From the Build from History page, to perform a build outside of the automatic schedule build, click Run. The Target Time column displays the time that this entry was built. The Status column displays whether the build was completed or failed.

Canceling a build from history job You can cancel all planned jobs. The job status becomes "Aborted."

Steps

1. Access the Data Warehouse Portal. 2. From the Advanced section of the Data Warehouse Main Menu, select Build from History. 3. Click Cancel.

Scheduling daily builds You can set the frequency and the time of the build process, building each Data Warehouse data mart. Data Warehouse performs a build job for each connector and for each data mart. For example, Getting started with Data Warehouse | 27

Data Warehouse performs an inventory job for each connector, then performs a capacity job for each connector.

About this task Whenever the Data Warehouse is being built, it performs an inventory job for every connector. After the inventory jobs are complete, Data Warehouse performs jobs for dimensions, capacity, and the remaining data marts.

Steps

1. From the Data Warehouse Main Menu, select Schedule.

2. Click Edit to add a new schedule.

3. Choose the frequency, for example, daily or weekly. 28 | OnCommand Insight Data Warehouse Administration Guide

4. Choose the time at which you want the job to run. This ensures that the build job runs automatically. 5. To enable the schedule, check Enabled. Note: If you do not check this, the schedule build does not occur.

6. Click Save. 7. From the Schedule page, to build Data Warehouse outside of the automatic scheduled build, click Build Now.

Backing up the Data Warehouse database You can back up the Data Warehouse (DWH) database to a file and later restore it using the Data Warehouse portal. This feature not only backs up your data, but also enables you to migrate to a different Data Warehouse machine or upgrade to a new Data Warehouse version.

About this task Data Warehouse backs up the following information: • LDAP configuration • Data sources • Import and export tasks that imported or exported reports • Reporting security roles, groups, and namespaces • User accounts • Any modified Reporting Connection reports Note: If you want to modify a predesigned report, we recommend that you save the predesigned report with a different name first and modify the copied version so that you do not lose your modifed version when you upgrade or restore the system. • Custom reports, regardless of where they are stored, even the My folders directory. Note: You should save custom reports in one of the OnCommand Insight shipped folders, such as Custom Reports or Custom Dashboards.

In addition to a manual backup that you can perform at any time, Data Warehouse creates a daily backup (generated each day to a file called DailyBackup.zip) that includes the report definitions. The daily backup includes the top folders and packages shipped with the product. The My Folders directory and directories that you create outside the product's top folders are not included in the Cognos backup.

Steps

1. To access the Data Warehouse portal, open a Web browser and enter the URL for the OnCommand Insight Data Warehouse:

http:///dwh

2. From the Advanced section of the Data Warehouse Main Menu, select Backup/Restore. 3. Do one of the following: • To back up only inventory data and not performance, capacity, port or other data, select Inventory Datamart only. To back up your historical capacity data as well, do not check this option. • To back up all data except performance data, which might require more time and space, select All Datamarts except Performance Datamart. • To back up all data including performance data, select All Datamarts Including Performance Datamart. 4. Click Backup. This operation can take awhile (possibly 30 minutes or more). Data Warehouse creates a backup file and displays its name. 5. Right-click on the backup file and save it to a location you want. Recommendation: You might not want to change the file name; however, you should store the file outside the Data Warehouse installation path.

Backing up custom reports and reporting artifacts If you created custom reports or you made changes to the reports in your current version of the Reporting Connection and you want to upgrade to a newer version, you need to back up your reports and reporting artifacts and restore them after the upgrade installation.

• CustomerDashboards - Use this to store your dashboards. • CustomerReports - Use this to store your reports. If you have reports in the My Folders area, you should copy them to the CustomerReports folders so that they are not lost. In addition to a manual backup that you can perform at any time, Data Warehouse creates a daily backup (generated each day to a file called DailyBackup.zip) that includes the report definitions. The daily backup includes the top folders, CustomerReports folders, and packages that were shipped with the product. The My Folders directory and directories that you create outside the product's top folders are not included in the Cognos backup.

Restoring the Data Warehouse database When you back up the Data Warehouse database, Data Warehouse creates a .gz file that you can later use to restore that same database.

About this task When you restore the Data Warehouse database, you have the option to restore user account information from the backup as well. User management tables are used by the Data Warehouse report engine in a Data Warehouse only installation.

Steps

1. From the Advanced section of the Data Warehouse Main Menu, select Backup/Restore. 2. In the Restore section, in the Select File to Restore option, click Browse and locate the .gz file that holds the Data Warehouse backup. 3. If you want to restore reports or user account data also, check one or both of the following: • Restore database: Includes Data Warehouse settings, data marts, connections, schedules, and user account information. • Restore reports: Includes custom reports, predesigned reports, changes to predesigned reports that you made, and reporting settings you made in the Reporting Connection. 4. Click Restore. After the restore process completes, a message appears just below the Restore button. If the restore process is successful, the message indicates success. If the restore process fails, the message indicates the specific exception that occurred to cause the failure. If an exception occurs and the restore fails, the original database is automatically reset.

Related tasks Resetting the Data Warehouse database or Reporting server on page 67 Getting started with Data Warehouse | 31

Managing Data Warehouse and Reporting user accounts User accounts, user authentication, and user authorization for the OnCommand Insight reporting tools are defined and managed from the Data Warehouse (DWH). Based on these configurations, users and administrators gain access to some or all of the available OnCommand Insight reports. Access to the User Management in the Data Warehouse requires an account with System Administrator privileges. This includes: • Full administrative capabilities for the Data Warehouse. • Configuration and maintenance of all user accounts. • Read access to the database. • Capability to set up connectors in the ETL, schedule Data Warehouse jobs, reset the database, assign or change roles, and add and remove user accounts. • Capability to run SQL queries.

Accessing the Data Warehouse and Reporting The Data Warehouse portal provides access to administration options. From the Data Warehouse portal, you can also access the Reporting Connection portal.

Steps

1. To open the Data Warehouse portal, enter this URL:

http:///dwh

2. Log in as an administrator. The Data Warehouse portal resembles the OnCommand Insight Administration portal with a Main Menu and Advanced features listed in the left pane. 3. To access the reporting features, in the Main Menu, click Reporting Portal.

Reporting user roles Each user account is assigned a role with a set of permissions. The number of users is limited by the number of Reporting licenses attached to each role. Each role can perform the following actions:

Recipient Views OnCommand Insight Reporting portal dashboards and reports and sets personal preferences such as those for languages and time zones. Note: Recipients cannot create reports, run reports, schedule reports, export reports, nor perform administrative tasks. 32 | OnCommand Insight Data Warehouse Administration Guide

Business Runs reports in Business Insight (in standard mode) and runs reports Consumer interactively in addition to performing all Recipient options. Business Author Views scheduled reports, runs reports interactively, and creates some reports in addition to performing all Business Consumer options. Pro Author Creates reports in addition to performing all Business Author options and has advanced reporting tool options that are available also with Report Studio. Administrator Performs reporting administrative tasks such as the import and export of report definitions, configuration of reports, configuration of data sources, and the shutdown and restart of reporting tasks.

The following table shows the privileges and the maximum number of users allowed for each role:

Feature Recipient Business Business Pro Author Admin Consumer Author (Insight Plan (Insight only) Plan only) View reports (in Yes Yes Yes Yes Yes Detailed Reports tab, Public Folder tab, My Folders) Run reports No Yes Yes Yes Yes Schedule reports No Yes Yes Yes Yes Create reports in No No Yes Yes No Query Studio Create reports in No Yes Yes Yes No Business Insight (Standard) Create reports in No No Yes Yes No Business Insight (Advanced) Create reports in No No No Yes No Report Studio Perform No No No No Yes administrative tasks Number of users Number of 20 2 1 1 OnCommand Insight users Getting started with Data Warehouse | 33

When you add a new Data Warehouse and Reporting user, if you exceed the limit in a role, the user is added as "deactivated," and you need to deactivate or remove another user with that role to give a new user membership. Note: Report authoring capabilities require Insight Plan license.

These reporting user roles do not affect direct database access. These reporting user roles do not impact your ability to create SQL queries using the data marts.

Adding a Reporting user Add a new user account for each person who requires access to the Reporting portal. Having a different user account for each person provides a way of controlling the access rights, individual preferences, and accountability.

Before you begin Before adding a Reporting user: • Allocate a unique user name. • Determine what password to use. • Verify the correct user role or roles. These roles are specialized in the Reporting portal. See "Reporting user roles" for details.

Steps

1. Log in as the administrator to the DWH management portal. 2. On the lower left in the Advanced menu, click User Management. 3. In the User Management window, click Add New User. 4. Enter the following information for the new Reporting user:

User Name Name assigned to the new user (alphanumeric, including a-z, A-Z, and 0-9). This name is used to log in and is case-sensitive. E-mail Address User e-mail address and required if the user subscribes to any reports. Password Password used to log in to OnCommand Insight under this user account (typically selected by the user) and confirmed in the next field. OnCommand Roles available to the user with appropriate permissions. Insight role Note: The options for the OnCommand Insight role are shown only if OnCommand Insight has been is installed on the same machine as the reporting facilities, which is not typical.

Reporting roles Select the Reporting role for this user. For example, select Reporting Author. The Reporting Administrator role is unique and requires a separate license. This role can be added to any user. 34 | OnCommand Insight Data Warehouse Administration Guide

No Access Selected by default. It indicates that the user should not have access to the OnCommand Insight Reporting portal.

5. Click Add.

Managing user accounts You can configure user accounts, user authentication, and user authorization from the Data Warehouse Portal. Each user account is assigned a role with one of the following permission levels. The number of users is limited by the number of Reporting licenses attached to each role.

Steps

1. On the lower left in the Advanced section of the Data Warehouse Main Menu, select User Management.

2. Do one of the following: • To edit an existing user, select the row for the user and click Edit. • To change a user's password, select the row for the user and click Change password. • To delete a user, select the row for the user and click Delete 3. To activate or deactivate a user, select the row for the user and click Activate or Deactivate.

Configuring Reporting LDAP From the Data Warehouse portal, the Administrator can configure LDAP usage for Data Warehouse and Reporting.

Steps

1. Log in as the administrator to the Data Warehouse portal. 2. On the lower left in the Advanced menu, click User Management. 3. Click LDAP Configuration. 4. Mark the Enable LDAP box to start the LDAP user authentication and authorization process. Getting started with Data Warehouse | 35

5. In the LDAP Configuration window, the majority of the fields contain default values. The default settings are valid for the Active Directory. Note: If you make any changes in this window, you must fill in the Directory lookup user and Directory lookup user password fields at the bottom. If you do not, the changes you make in the LDAP configuration will not be saved.

User principal Attribute that identifies each user in the LDAP server (defaults to name attribute userPrincipalName, which is globally unique). OnCommand Insight attempts to match the contents of this attribute with the username that has been supplied. Role attribute LDAP attribute that identifies the user role (defaults to memberOf ). Mail attribute LDAP attribute that identifies the user email address (defaults to mail). This is useful if you want to subscribe to the OnCommand Insight reports available from the OnCommand Insight portal. Note: OnCommand Insight picks up the user email address the first time each user logs in and does not look for it after that. If the email address changes on the LDAP server, make sure to change it manually in the OnCommand Insight database.

Distinguished name LDAP attribute that identifies the user distinguished name (defaults to attribute distinguishedName ). Referral Indication of whether to follow the path to other domains if there are multiple domains in the enterprise. Always use the default (follow ). Timeout (ms) Length of time to wait for a response from the LDAP server before timing out, in milliseconds (defaults to 2 seconds, which is adequate in all cases and should not be modified). LDAP servers (use IP address or DNS name to identify the LDAP server, typically provided comma to delimit) in this format:

ldap:// :port

or, to use the default port:

ldap://

Note: To import the LDAP certificates, click Import Certificates and automatically import or manually locate the certificate files.

Domain LDAP node where OnCommand Insight should start looking for the LDAP user (typically the top-level domain for the organization). For example: DC=,DC=com 36 | OnCommand Insight Data Warehouse Administration Guide

OnCommand Value of the Role Attribute that identifies the user as having Server Insight server Administrator privileges (defaults to sanscreen.server.admin ). administrators group OnCommand Value of the Role Attribute that identifies the user as having Insight Administrator privileges (defaults to sanscreen.admin). administrators group OnCommand Value of the Role Attribute that identifies the user as having User Insight users group privileges (defaults to sanscreen.users ). OnCommand Value of the Role Attribute that identifies the user as having Guest Insight guests privileges (defaults to sanscreen.guests ). group Reporting Value of the Role Attribute that identifies the user as having Reporting administrators administrator privileges (defaults to sanscreenreport.admins). See group Reporting user roles for more information. Reporting pro Value of the Role Attribute that identifies the user as having Reporting authors group pro author privileges (defaults to sanscreenreport.proauthors). Reporting authors Value of the Role Attribute that identifies the user as having Reporting group author privileges (defaults to sanscreenreport.authors). Reporting Value of the Role Attribute that identifies the user as having Reporting consumers group consumer privileges (defaults to sanscreenreport.consumers).

6. If you changed any of the previous fields, enter Directory lookup values. Confirm the password and click Validate Password to check it on the server. 7. Click Update to save the changes.

Setting up multiple tenancy in reporting OnCommand Insight Data Warehouse accommodates multiple tenancy (often abbreviated "multi- tenancy") in reporting by allowing you to associate users with one or more business entities. With this feature, administrators can separate data or reports according to user attributes or user affiliation. Business entities use a hierarchy for the purposes of capacity chargeback using the following values: • Tenant: Primarily used by service providers to associate resources with a customer, for example, NetApp. • Line of Business (LOB): A line of business within a company, for example "Hardware" or "Software." • Business Unit: A traditional business unit such as "Sales" or "Marketing." • Project: A project to which you might want to assign capacity chargeback. Getting started with Data Warehouse | 37

The process of configuring multiple tenancy involves the following major steps: • Configure a Data Warehouse user account. • Create a group in Reporting Connection. • Assign users to one or more groups, which represent business entities. • Assign users to one or more business entities. For example, users associated with "NetApp" obtain access to all business entities that have “NetApp” as a tenant. • Test that users can see only those reports that they should see. The following points summarize how users access reporting data: • A user, not assigned to any group, gets access to all the data. • A user, assigned to any group, will not be able to get access to records without business entity. For example, you might have the following departments and need to separate reports for users within these departments.

User Engineering Support Finance Legal User1 X X User2 X X User3 X

Configuring user accounts You must complete several steps to configure user accounts.

Steps

1. Access the Data Warehouse Portal. 2. From the Data Warehouse Main Menu, select User Management. 3. Configure each user account.

Assigning users to business entities You must complete a series of steps to assign users to business entities.

Steps

1. Log onto OnCommand Insight Data Warehouse as a super user. 2. From the Data Warehouse Main Menu, select Reporting Portal. 3. Enter your user name and password and click OK.

38 | OnCommand Insight Data Warehouse Administration Guide

4. Select Insight Reporting Content to open the OnCommand Insight Reporting Portal.

5. From the Launch menu in the upper right, select Insight Report Administration.

6. From the OnCommand Insight Reporting Administration view, select the Security tab.

7. In the Directory, select System. 8. Create a new directory/folder inside System called "BEs" for business entities. 9. Open the BEs directory. 10. Click the New Group icon to add groups that correspond to different permission levels. These permission levels can be either the full name of the business entity (for example, NetApp.N/A) or a prefix (for example, NetApp.N/A.Finance). Either of these formats enables access to all projects within the business entity (NetApp.N/A.Finance).

Getting started with Data Warehouse | 39

11. Click Next and then Finish.

12. Check a business entity and click More. 13. Click Set members. 14. Click Add. 15. Select the SANscreen directory. 16. From the list of users, check each user that you want to include in the Business Entity and add the user to the Selected Entries box. 17. Click OK. 18. Repeat the process of adding members to each of the business entity groups.

Troubleshooting setup issues There are several common issues with annotations, builds, and reports that you may face during setup. You can troubleshoot these issues by following the steps outlined.

Why I cannot see my annotations If you cannot see annotations in Data Warehouse, you might need to force an update of annotations and then initiate a Data Warehouse build. Missing annotations affect the way data is imported into Data Warehouse and is displayed in the reports. For example, if the annotation “Tier” is not available, you will not be able to group storage systems by tier in Data Warehouse reports. 40 | OnCommand Insight Data Warehouse Administration Guide

Related concepts Annotations on page 50

Forcing an update of annotations for Data Warehouse You can initiate an update of annotations from OnCommand Insight to Data Warehouse.

Steps

1. Access the OnCommand Insight Administration web-based portal.

2. From the OnCommand Insight Main Menu, select Troubleshooting > Force Update of Annotations for DWH (include deleted objects). Getting started with Data Warehouse | 41

Generating a manual Data Warehouse build After forcing an annotations update (running transient data) in OnCommand Insight, you need to initiate a Data Warehouse build. You can wait until the next scheduled build or initiate a build now.

Steps 1. Access the Data Warehouse portal. 2. From the Data Warehouse Main Menu, select Schedule. 3. Click Build Now.

Importing user-defined annotations into Data Warehouse After forcing an annotation update in OnCommand Insight, you need to select the annotations you want in Data Warehouse and initiate a Data Warehouse build. You can wait until the next scheduled build or initiate a build now.

Steps 1. From the Data Warehouse Main menu, select Annotations. View a list of annotations. The list displays a row for every annotation type and a target object to which the annotation can be assigned. A check mark in the Published column indicates that the annotation was already selected for the particular target object and is already available through the Data Warehouse data marts.

42 | OnCommand Insight Data Warehouse Administration Guide

2. Click Edit to edit how annotations will be imported from OnCommand Insight.

3. To edit the annotation process, do the following: • Published. Check this to add annotations retrieved from OnCommand Insight into the Data Warehouse database. Click All to select all annotations on all objects. Click None to deselect all options. Note: Uncheck this option to remove the annotation column from the specific object's inventory table and associated data marts. If any custom-designed reports use annotation data, the reports do not run successfully. • Init with Current. Check this to initialize historical data in Data Warehouse dimension tables with the current annotation value. Click All to select all annotations on all objects. Click None to deselect all options. This checkbox is disabled once an annotation has been published; the checkbox is enabled for annotations that have not been published. For example, if a host is annotated with annotation type "floor" and gets the value "1", and there are 3 rows for that host in the host_dimension table, then selecting "Init with current" associates the value "1" in the 'floor" column for all 3 rows in the host_dimension table. If "init with current" is not selected, then only the latest row for that host will have the value "1" in the floor column. 4. Click Save. Getting started with Data Warehouse | 43

A warning message appears indicating that this will cause changes to the structure of the data or data loss, if you are removing annotations. 5. To continue, click Yes. Data Warehouse initiates an asynchronous Annotations job that applies the requested changes. You can see the job in the Jobs page. You can also see the changes in the Data Warehouse database schema.

What to do with failing historical build points You can build from history, but skip any failed builds by enabling an option to Skip Failed Builds. If you do this, the build from history continues. If a build fails and this option is enabled, Data Warehouse continues building and ignores any failed builds. In such cases, there will not be a data point in the historical data for any skipped builds. If you do not enable this option and the build fails, all subsequent jobs are aborted.

Related tasks Skipping failed builds on page 65

Troubleshooting incorrect report numbers A report might show data that you did not expect. To help troubleshoot this, you can run a utility that shows the possible issues.

Steps

1. Access the Data Warehouse Portal. 2. From the Data Warehouse Main Menu, select Troubleshooting. 3. Scroll down and click Sanity Tests. 4. In the Sanity Tests view, to filter what tests and results you see, do any of the following and click Filter: • Select the type of test. • Select whether you want to see all states of errors. • Select whether you want to see all root causes or a specific one. 5. Optionally, enter a prefix for the DWH schema, such as “inventory” or “performance.” 6. Click Start. Data Warehouse retrieves test information and shows you possible issues with your data. 44 | OnCommand Insight Data Warehouse Administration Guide

Data Warehouse Administration

OnCommand Insight Data Warehouse (DWH) is a web-based user interface that enables users to configure and troubleshoot data in OnCommand Insight Data Warehouse and set up schedules to retrieve data from OnCommand Insight. Using the Data Warehouse Portal, you can do the following tasks: • Manage connections. • Check the status on current jobs or queries that are running. • Schedule builds. • Manage annotations. • Configure email notifications. • Access and create custom reports. • Review Data Warehouse documentation and database schema. • Use the System Information option to do the following: • Edit the site name. • Identifying the Data Warehouse version and upgrade history. • Use the Advanced option to do the following: • Build the Data Warehouse data from history. • Reset the Data Warehouse database. • Back up and restore the Data Warehouse database. • Troubleshoot Data Warehouse issues and look at OnCommand Insight logs. • Manage user accounts.

Related concepts Annotations on page 50 Data Warehouse database build from history overview on page 22 Troubleshooting Data Warehouse on page 71

Related tasks Connecting Data Warehouse to OnCommand Insight servers on page 21 Managing jobs on page 48 Scheduling daily builds on page 26 Setting email notifications on page 57 Accessing the Reporting Portal on page 57 Viewing the Data Warehouse database schema on page 59 Viewing the Data Warehouse documentation on page 58 Data Warehouse Administration | 45

Editing the site name and viewing system information on page 60 Viewing the Data Warehouse version and upgrade history on page 60 Resetting the Data Warehouse database or Reporting server on page 67 Backing up the Data Warehouse database on page 28 Restoring the Data Warehouse database on page 30 Managing user accounts on page 34

About this task The following is the default user name and password. It is a good idea to change these defaults after installation. • Username: admin • Password: admin123

Steps

1. Open a web browser and enter the following URL: http:///dwh 2. Enter your username and password. 3. Click OK. The Data Warehouse Portal opens.

46 | OnCommand Insight Data Warehouse Administration Guide

When you add or edit a connection, you can also test the connection. The test does the following: • Verifies the host IP address, user name, and password and ensures that a connection can be established. Invalid connections appear in red. • Compares the OnCommand Insight version to the Data Warehouse version. If the versions are not compatible, an error message appears. • Verifies that the OnCommand Insight database has not been changed or restored to a different database as seen by the last Data Warehouse processing. If there has been a change, an error message appears.

Steps

1. From the Data Warehouse Main Menu, select Connectors. The Connectors table appears blank at first and shows connector information after you add a connector. 2. Click New to add a new connector. 3. Enter the following:

Password "sanscreen"

Managing jobs You can see a list of current jobs and their status. The first job in a build cycle is in bold type. The build that Data Warehouse performs for each connector and for each data mart is considered a job.

About this task You can cancel any pending job you have scheduled or begun. You can also clear the history of previously executed jobs. You can clear history of jobs that are not pending, running, or in the process of aborting. You can clear all history or all history except the previous 24 hours to remove all but the last day's entries. You can see information about the following types of jobs: inventory, dimensions, capacity, port capacity, VM capacity, file system utilization, capacity efficiency, history build, dynamic annotations, connector removal, skipped build, Phone Home activities, and maintenance jobs. A maintenance job runs weekly and uses mysql tools to optimize the database.

Steps

1. From the Data Warehouse Main menu, select Jobs.

Data Warehouse Administration | 49

2. If a Pending status appears, a cancel link appears. To cancel a pending job, click cancel. 3. To remove history, click All or All but last 24h. No additional message appears.

Steps

1. From the Data Warehouse Main Menu, select Schedule.

2. Click Edit to add a new schedule.

50 | OnCommand Insight Data Warehouse Administration Guide

3. Choose the frequency, for example, daily or weekly. 4. Choose the time at which you want the job to run. This ensures that the build job runs automatically. 5. To enable the schedule, check Enabled. Note: If you do not check this, the schedule build does not occur. 6. Click Save. 7. From the Schedule page, to build Data Warehouse outside of the automatic scheduled build, click Build Now.

Annotations The annotation feature lets you define information that relates to objects in your environment and then track the objects based on the annotation. For example, you could add building or floor number annotations to devices in your environment. Additionally, you might want to look at all devices in a specific data center or business entity and determine which business entity is using the most tier 1 storage. To do this, you assign a data center, business entity or tier annotation to the device using the OnCommand Insight Client. Then, you can bring selected user-defined annotations from OnCommand Insight into Data Warehouse. You want to do this to see the annotation values assigned to objects appear in your custom reports. For details about creating annotations in OnCommand Insight, see the OnCommand Insight Inventory User Guide. You can specify which user-defined annotations propagate to Data Warehouse. Annotations are added as additional columns to the object table in the inventory, and to the relevant dimension table in the data marts. When you update the annotations on resources using the OnCommand Insight user interface and initiate or wait for the next Data Warehouse build, you will see the results in the following tables: • dwh_inventory.annotation_value • dwh_inventory.object_to_annotation Data Warehouse Administration | 51

Ensuring annotations entered in OnCommand Insight are included in Data Warehouse requires the following major processes, each explained in this section: • Before you import annotations into Data Warehouse, ensure that they are prepared in OnCommand Insight. To do this, you can manually run the Troubleshooting > Force Update of Annotations for Data Warehouse option or wait until the next scheduled transient data run process. When you force the update of annotations, you force the OnCommand Insight server to calculate and place the transient data (such as annotation values) into database tables so that the Data Warehouse ETL process can read the data. The update of annotations data occurs every four hours automatically, but you can force it to happen more frequently. • Import annotations into Data Warehouse by using Data Warehouse Annotations option. • If you want to include annotations in reports that you create by using the OnCommand Insight Reporting Portal (Query Studio or Report Studio), you need to update the OnCommand Insight reporting metadata model. When you upgrade Data Warehouse, the annotations job runs automatically during the database restore process. The annotations job runs automatically also when JBoss starts up. Note: JBoss is an application server where the OnCommand Insight Java code runs and is needed for both for the OnCommand Insight server and for Data Warehouse.

Preparing annotations in OnCommand Insight Annotations must be prepared in OnCommand Insight before they can be imported into Data Warehouse.

Steps

1. Access the OnCommand Insight web-based Administration portal. 2. From the OnCommand Insight Main Menu, select Troubleshooting > Force Update of Annotations for Data Warehouse.

Steps

1. From the Data Warehouse Main menu, select Annotations. View a list of annotations. The list displays a row for every annotation type and a target object to which the annotation can be assigned. A check mark in the Published column indicates that the annotation was already selected for the particular target object and is already available through the Data Warehouse data marts.

52 | OnCommand Insight Data Warehouse Administration Guide

2. Click Edit to edit how annotations will be imported from OnCommand Insight.

3. To edit the annotation process, do the following: Data Warehouse Administration | 53

• Published. Check this to add annotations retrieved from OnCommand Insight into the Data Warehouse database. Click All to select all annotations on all objects. Click None to deselect all options. Note: Uncheck this option to remove the annotation column from the specific object's inventory table and associated data marts. If any custom-designed reports use annotation data, the reports do not run successfully. • Init with Current. Check this to initialize historical data in Data Warehouse dimension tables with the current annotation value. Click All to select all annotations on all objects. Click None to deselect all options. This checkbox is disabled once an annotation has been published; the checkbox is enabled for annotations that have not been published. For example, if a host is annotated with annotation type "floor" and gets the value "1", and there are 3 rows for that host in the host_dimension table, then selecting "Init with current" associates the value "1" in the 'floor" column for all 3 rows in the host_dimension table. If "init with current" is not selected, then only the latest row for that host will have the value "1" in the floor column. 4. Click Save. A warning message appears indicating that this will cause changes to the structure of the data or data loss, if you are removing annotations. 5. To continue, click Yes. Data Warehouse initiates an asynchronous Annotations job that applies the requested changes. You can see the job in the Jobs page. You can also see the changes in the Data Warehouse database schema.

Viewing the Annotations job in the Jobs list You can view the Annotations job in the Jobs list and apply the annotation changes to Data Warehouse data marts.

Steps

1. Access the Data Warehouse Portal. 2. From the Data Warehouse Main Menu, select Jobs.

Updating annotations in OnCommand Insight reporting To include annotations in reports that you create by using the OnCommand Insight Reporting Portal (Query Studio or Report Studio), you need to update the OnCommand Insight reporting metadata model.

Steps

1. Unzip \cognos\10_64\deployment\Models XX.zip (where “XX” is the current version) to a temporary directory. 54 | OnCommand Insight Data Warehouse Administration Guide

2. Open Framework Manager (Start menu > All Programs> IBM Cognos version > Framework Manager). 3. Click on the Open a Project link. 4. In the File Open dialog, navigate to the temporary directory where you unzipped the Models xx.zip file and open the .cpf file for the datamart to which you want to add the annotation.

For example, open \My Projects\Storage Capacity\Storage Capacity.cpf. 5. Expand the directory. For example, expand Storage Capacity > dwh_capacity 6. If you are looking at packages other than the Inventory package, do the following: a) Expand the directory by double-clicking the dimension table (for example, storage_dimension) corresponding to the target resource you assigned the annotation type to in the OnCommand Insight Client. b) Click OK to refresh the dimension table. c) Expand Advanced Datamart. The annotation entry appears under the dimension table on the left side. 7. If you are looking at the Inventory package, do the following: a) Expand these directories Inventory [version] > dwh_inventory > Database layer > storage Update the table (for example, Storage) to include the annotation column. b) Expand these directories Inventory [version] > dwh_inventory > Presentation layer > storage Update the table (for example, Storage) to include the annotation column. c) Expand these directories Inventory [version] > dwh_inventory > Group containing the annotation object (for example, Storage Assets) > annotated object (for example, storage) Update the table (for example, Storage) to include the annotation column. 8. Right-click on the query subject corresponding to the dimension table you updated (for example, Storage Dimension) and click Edit Definition. 9. Double-click each new annotation entry under the raw “x_dimension” table to the “Available Model Objects” list to add it to the query subject. Reorder and rename as desired. 10. Expand Packages. 11. Right-click on the package, select Publish Packages and click through the dialogs to finish. 12. In the toolbar, click the Save icon. Data Warehouse Administration | 55

Using annotations in a Query Studio report You can use annotations in a Query Studio report.

Steps

1. Return to the OnCommand Insight Reporting Portal. 2. Open or create reports. Drag and drop the new annotation columns onto the report.

Seeing the annotation changes in the database schema The DB schema reflects the changes in the specific table.

About this task For example, if the annotation was added to a storage array Enter the tasks the user should do after finishing this task (optional). or switch in OnCommand Insight, after Data Warehouse receives the annotation values, they appear in the storage or switch table in the inventory or other data marts. If you update the annotations on resources using the OnCommand Insight user interface and initiate or wait for the next Data Warehouse build, you see a new column added or removed in the corresponding object in inventory (dwh_inventory) and in the corresponding dimension table as well (in the appropriate data mart). You see the results in the following tables: • dwh_inventory.annotation_value • dwh_inventory.object_to_annotation This example shows changes made to the dwh_inventory switch and dwh_capacity table.

Steps

1. From the Data Warehouse Main Menu, select Documentation > Database Schema. 2. In the Databases pane, click dwh_inventory. 3. In the Tables pane, click the switch table.

56 | OnCommand Insight Data Warehouse Administration Guide

The dwh_inventory.switch table reflects the changes. 4. As another example, in the Databases pane, click dwh_capacity. 5. In the Tables pane, click storage_dimensions.

The dataCenter annotation column appears in the storage_dimensions table. Data Warehouse Administration | 57

Setting email notifications You can have Data Warehouse send email to a specific email address when Data Warehouse jobs do not complete successfully.

Steps

1. From the Data Warehouse Main Menu, select Email Notification. 2. In the Configuration view, enter the following: • SMTP server address: Server that is acting as the SMTP server in your organization, identified using either a hostname or an IP address (nnn.nnn.nnn.nnn format). If you specify a host name, make sure the name can be resolved through DNS. • SMTP server username and password: User name to access the email server, required only if your SMTP server is protected by a user login. This is the same user name you use to log in to the application and access your email. • Notifications enabled: Check Yes. • Sender's Email: E-mail account to be identified as the sender of the notification emails. This account must be a valid email account within your organization. • Recipient's Email: Email address of the person who will always receive the email. This account must be a valid email account within your organization. • Email signature: Information that will appear at the bottom of the email, for example, the department name.

Accessing the Reporting Portal From the Data Warehouse Portal, you can access the Reporting Portal, where you can create custom reports using report authoring tools such as Business Insight Advanced, Query Studio, and Reports Studio.

About this task

Steps

1. From the Data Warehouse Main Menu, select Reporting Portal. 2. Another browser page appears where you must log in. Enter your user name and password and click OK.

58 | OnCommand Insight Data Warehouse Administration Guide

3. Click Insight Reporting content. The Reporting Portal opens, from which you can select a data model and open the report authoring tool.

Viewing the Data Warehouse documentation You can review Data Warehouse documentation, including this Data Warehouse User Guide, and database schema information.

Steps

1. Access the Data Warehouse Portal. 2. From Data Warehouse Main menu, select Documentation.

Data Warehouse Administration | 59

Viewing the Data Warehouse database schema You might want to view the database schema to understand how to use the data in another API or to develop SQL queries. The schema option lists all databases, tables, and columns in the schema. You can also review the database schema diagrams showing the table relationships.

Steps

1. From Data Warehouse Main menu, select Documentation. 2. From the Data Warehouse Documentation page, select Database Schema. 3. For example, in the Databases pane, click dwh_inventory. 4. In the Tables pane, click the annotation_value table.

60 | OnCommand Insight Data Warehouse Administration Guide

The dwh_inventory.annotation table appears.

Editing the site name and viewing system information You can edit the site name, which displays on reports. You can also view information about licenses, installed versions, and installation dates for modules.

Steps 1. From the Data Warehouse Main Menu, select System Information. 2. On the System tab, review system information. 3. To edit the site name, click Edit Site Name 4. Enter the new site name and click Save. 5. To see application information and versions, click the Application Info tab. 6. To see license information, click the Licenses tab.

Viewing the Data Warehouse version and upgrade history You can view the Data Warehouse version, and view a list of previous upgrades. You can also view the list of modules that indicates the module version and date. You can look at the module version and date to determine whether a particular upgrade was applied.

Steps 1. From the Data Warehouse Main Menu, select System Information. 2. To see application information and versions, click the Application Info tab. Data Warehouse Administration | 61

3. To see upgrade information, click the Upgrade History tab.

Advanced options Data Warehouse includes various advanced options.

Related concepts Data Warehouse database build from history overview on page 22 Troubleshooting Data Warehouse on page 71

Related tasks Skipping failed builds on page 65 Resetting the Data Warehouse database or Reporting server on page 67 Backing up the Data Warehouse database on page 28 Restoring the Data Warehouse database on page 30 Managing user accounts on page 34

Forcing an update of annotations for Data Warehouse You can initiate an update of annotations from OnCommand Insight to Data Warehouse.

Steps

1. Access the OnCommand Insight Administration web-based portal.

Data Warehouse Administration | 63

2. From the OnCommand Insight Main Menu, select Troubleshooting > Force Update of Annotations for DWH (include deleted objects).

Adding a job that builds from history You can build the Data Warehouse database using historical data that is kept in your OnCommand Insight server.

Before you begin Before you build from history, you should update annotations in the OnCommand Insight Client and then force an update of annotation information for Data Warehouse.

Steps

1. Access the Data Warehouse Portal at http:///dwh. 2. From the Advanced section of the DWH Main Menu, select Build from History.

64 | OnCommand Insight Data Warehouse Administration Guide

3. Click Configure.

4. Enter the start and end times. To display a calendar from which you can select a date, click the down arrow near the month. Data Warehouse Administration | 65

Canceling a build from history job You can cancel all planned jobs. The job status becomes "Aborted."

Steps

1. Access the Data Warehouse Portal. 2. From the Advanced section of the Data Warehouse Main Menu, select Build from History. 3. Click Cancel.

Skipping failed builds After your first build, sometimes you might encounter an unsuccessful build. To ensure that all the jobs after an unsuccessful build complete successfully, you can enable an option to skip build failures.

About this task If a build fails and the Skip Failed Builds option is enabled, Data Warehouse continues building and ignores any failed builds. If this occurs, there will not be a data point in the historical data for any skipped builds. 66 | OnCommand Insight Data Warehouse Administration Guide

Use this option only if the build is not successful. If a build fails in Build from History and the Skip Failed Builds checkbox is disabled (not checked), all subsequent jobs are aborted.

Steps

1. Access the Data Warehouse Portal. 2. From the Advanced section of the Data Warehouse Main Menu, select Build from History.

3. Click Configure. 4. Configure the build. 5. Click Save. 6. From the Build from History page, to skip failed builds, check Skip Failed Builds. You can see this checkbox only if the Run button is enabled. Data Warehouse Administration | 67

7. From the Build from History page, to perform a build outside of the automatic scheduled build, click Run.

Resetting the Data Warehouse database or Reporting server You can delete the contents of the Data Warehouse data marts and delete all configured connectors. You might want to do this if an installation or upgrade did not complete successfully and it left the Data Warehouse database in an intermediate state. You can also delete only the Inventory data model or the Cognos Reporting data model.

Steps

1. From the Advanced section of the Data Warehouse Main menu, select Reset DWH database. 2. Click one of the options. • Reset DWH Database: Deletes the contents of all Data Warehouse data marts and all configured connectors. This places the Data Warehouse to the default installed state without any custom configurations. You might choose this option, for example, if you changed your connected servers, but restored a different Data Warehouse database accidentally on your server and need to return to a default installed state. Using the Reset DWH Database option does not delete custom reports. (Custom reports are saved in the Cognos Content Store.) • Reset Inventory Only: Deletes the contents of the Inventory data model only. This does not delete any historical data. • Reset Cognos Server Only: Deletes the default Reporting data models, reports, custom reports, and any changed settings (for example, import or export tasks or data sources). This option returns the Reporting Server to Cognos "factory settings." A warning message appears. 3. To continue deleting, click Yes.

Note: If you want to modify a predesigned report, we recommend that you save the predesigned report with a different name first and modify the copied version so that you do not lose your modifed version when you upgrade or restore the system. • Custom reports, regardless of where they are stored, even the My folders directory. Note: You should save custom reports in one of the OnCommand Insight shipped folders, such as Custom Reports or Custom Dashboards.

The following items are not backed up: • Cognos system configuration parameters, such as SMTP server settings • Cognos custom memory settings In this manual backup, Data Warehouse creates a zip file that contains these files: • A daily backup zip file, which contains Cognos report definitions • A reports backup zip file, which contains all the reports in Cognos (including those in the My Folders directory) • A Data Warehouse database backup file In addition to a manual backup that you can perform at any time, Data Warehouse creates a daily backup (generated each day to a file called DailyBackup.zip) that includes the report definitions. The daily backup includes the top folders and packages shipped with the product. The My Folders directory and directories that you create outside the product's top folders are not included in the Cognos backup.

Steps

1. To access the Data Warehouse portal, open a Web browser and enter the URL for the OnCommand Insight Data Warehouse:

http:///dwh

5. Right-click on the backup file and save it to a location you want. Recommendation: You might not want to change the file name; however, you should store the file outside the Data Warehouse installation path.

About this task If you made changes to the predesigned reports, the best practice is to create your own copy in a separate folder from the predesigned ones. That way, when you update the predesigned artifacts, you will not overwrite your changes. Two folders exist under each package: • CustomerDashboards - Use this to store your dashboards. • CustomerReports - Use this to store your reports. If you have reports in the My Folders area, you should copy them to the CustomerReports folders so that they are not lost. In addition to a manual backup that you can perform at any time, Data Warehouse creates a daily backup (generated each day to a file called DailyBackup.zip) that includes the report definitions. The daily backup includes the top folders, CustomerReports folders, and packages that were shipped with the product. The My Folders directory and directories that you create outside the product's top folders are not included in the Cognos backup.

Restoring the Data Warehouse database When you back up the Data Warehouse database, Data Warehouse creates a .gz file that you can later use to restore that same database.

Steps

• Restore database: Includes Data Warehouse settings, data marts, connections, schedules, and user account information. • Restore reports: Includes custom reports, predesigned reports, changes to predesigned reports that you made, and reporting settings you made in the Reporting Connection. 4. Click Restore. After the restore process completes, a message appears just below the Restore button. If the restore process is successful, the message indicates success. If the restore process fails, the message indicates the specific exception that occurred to cause the failure. If an exception occurs and the restore fails, the original database is automatically reset.

Related tasks Resetting the Data Warehouse database or Reporting server on page 67

Restoring and upgrading reports after upgrading from OnCommand Insight versions before 6.3 After performing the backup procedure in your OnCommand Insight version prior to 6.3, install the new version and then execute the following steps to restore your reporting artifacts.

Steps

1. To start to restore old Reporting artifacts, copy the Export Backup.zip file you created when you executed the steps in the "Backing up report artifacts" to the \cognos \c10_64\deployment directory. 2. Open a browser and go to http://:/reporting for the server and port you used during installation, for example http://localhost:8080/reporting.

3. Log in using the user name admin and the password admin123. Click Home. 4. On the Home portal page, a Launch link appears in the toolbar in the header. Click Launch > Reporting Administration. 5. Click the Configuration tab. Due to changes in the data model, the reports in the old packages may not run and need to be upgraded. 6. Click Content Administration. 7. Click the New Import button. 8. Make sure that archive you copied to the deployment directory is selected (for example, backup6.0.zip ) and click Next. 9. If you entered a password to protect the archive, enter the password and click OK.

10. Change the name Export... to Import Backup and click Next. Data Warehouse Administration | 71

11. Click on the pencil icon next to each package name and enter a new target name if necessary. For example, add a _original suffix to the existing name. Then click OK. 12. After you rename the target package names for all packages, select all blue folders and click Next to continue. 13. Accept all default values until you reach the Finish button. 14. Click Finish. Click Run. 15. Check the View the details of this import after closing this dialog checkbox. Click OK. 16. Click the Refresh link in the top right of the page until the Status text indicates that the job is complete. 17. Click Close. When completed, two sets of packages appear in the Public Folders tab. For example, one with a 6.x suffix (for the newer version) and one with a _original (or whatever you entered during the backup/restore procedure) suffix which will contain your old reports. Due to changes in the data model, the reports in the old packages may not run and will have to be upgraded. Your portal tabs now point to the 6.x version of the portal pages.

Troubleshooting Data Warehouse You can do various tasks related to troubleshooting Data Warehouse. • Use OnCommand Insight AutoSupport (ASUP). • View OnCommand Insight logs. • Resolve issues related to upgrades and business entities. • Resolve issues related to the consolidation of multiple OnCommand Insight servers. You can consolidate multiple OnCommand Insight servers into the same Data Warehouse database. Many configurations may report the same object from multiple connectors (that is, the same switch exists in two OnCommand Insight instances). In such cases, Data Warehouse consolidates the multiple objects into one (a primary connector is chosen and the object's data will be taken from that connector only). The storage administrator can use the Troubleshooting page to solve problems related to consolidation issues.

Related concepts Issue resolution with AutoSupport (ASUP) on page 72

Related tasks Viewing OnCommand Insight logs on page 76 Migrating business entities on page 77 Resolving multiple server annotation consolidation issues on page 83 72 | OnCommand Insight Data Warehouse Administration Guide

Issue resolution with AutoSupport (ASUP) You can send ASUP logs to NetApp Technical Support for assistance in troubleshooting. ASUP is configured to run automatically using OnCommand Insight options. In the Data Warehouse Portal, you can initiate a transmittal to ASUP and you can also disable the automatic send process. ASUP does not send a backup of the OnCommand Insight database to NetApp Technical Support. The information is forwarded to NetApp via FTP, HTTPS, or email, according to your choice. It contains minimal sensitive data. For example, sent files do not contain clear text passwords. Instead, the backup includes the hashed representation of user passwords, and encrypted device passwords. Data Warehouse sends the logs to the OnCommand Insight Server that is the first connector as listed in the Data Warehouse portal > Connector option. The automatic process sends the following files: • Data Warehouse logs • boot.log (including backups) • dwh.log (including backups such as dwh.log.1) • dwh_upgrade.log (including backups) • jboss.log (including backups) • ldap.log (including backups) • SQL dump of the Data Warehouse management database • mysql: my.cnf, .err and slow query logs • full innodb status • Sanity tests • Cognos logs • cognos-manager.zip: Contains the reporting data models. These are shipped in the \cognos\c10\deployment directory as a zip file in a file called Models 6.0.zip. To make changes to the data model (such as to add annotations), unzip the Models 6.0.zip file into the \cognos\c10 directory. This creates a My Projects directory in the \cognos\c10 directory, which OnCommand Insight zips. For 64-bit installations, the directory path is \cognos\10_64. • cognos-logs.zip: Contains the Cognos log files from the \cognos\c10\logs directory. Contains the logs generated by Cognos as well as our OnCommand InsightAP.log file that contains all logging from users logging in and out of OnCommand Insight reporting. • apache-logs.zip: Contains all of the Apache log files generated by the Apache server, on which Cognos runs. • DailyFullBackup.zip: Contains the backup of the reporting artifacts in the Public Folders. The contents of My Folders is not included in this. You can generate a troubleshooting report manually. The Troubleshooting Report zip file contains the following Data Warehouse information: • boot.log (including backups) Data Warehouse Administration | 73

• dwh.log (including backups such as dwh.log.1) • dwh_upgrade.log (including backups) • jboss.log (including backups) • ldap.log (including backups) • dump files in c:\Program Files\OnCommand Insight\jboss\server\onaro\log\dwh\ • SQL dump of the Data Warehouse management database • mysql: my.cnf, .err and slow query logs • full innodb status • Sanity tests

Configuring OnCommand Insight ASUP If ASUP is enabled, but no connection is configured, Data Warehouse indicates this in the OnCommand Insight ASUP view.

Steps

1. Access the OnCommand Insight Administration portal.

2. From the Advanced section of the OnCommand Insight Administration portal Main Menu, select Troubleshooting. 3. From the Troubleshooting menu, select Insight ASUP.

74 | OnCommand Insight Data Warehouse Administration Guide

4. Database: Select the database containing the data that you want to upload to ASUP: “No database backup,” "OnCommand Insight,” or OnCommand Insight and Application Insight. Depending on your selection, one or more of the following selections will be activated: • OnCommand Insight data: Choose whether you want "All" OnCommand Insight data or one of the "Current" options including 60 days, 90 days, 180 days, or the year of data. • Application Insight data: Choose whether you want "All" Application Insight data or only the "Last x days." Note: Application Insight will include all performance data, which could generate a huge *.gz file. • Application Insight packages: Check the appropriate box to include the specific Performance data to upload. Choices include: “Switch,” “Array,” or Host Virtualization.” Note: If all boxes are checked, Application Insight will include all performance data, which could generate a huge *.gz file. 5. Logs: Select whether you want “No logs,” “Base logs,” or the “Extended Logs,” which also contain a Data Source recording. 6. Send Method: Select which Send Method you want to use to upload data to ASUP (FTP, HTTP, HTTPS, email). Email is the default. If you select “email,” you must configure the email server to Data Warehouse Administration | 75

use from the OnCommand Insight Web Portal -> Mail. The preferred method of uploading the data is in order: FTP, HTTPS, or email. • Size Limit. Set the size limit of the data sample to be sent. The recommended data sample size is 100 MB and the recommended split file size is 1 MB. • Split files if bigger than: Indicate the cutoff point for file size. • ProxyHost, Port, User/Password: If you selected the HTTP or HTTPS protocol for ASUP data transmission and your company does not allow that type of data to be sent directly to the OnCommand Insight site, identify the proxy server it should use. Enter the proxy port and user credentials for ASUP data transmission. 7. Other • Sending Frequency: Choose how often you want to upload the data to ASUP. Enter the number of days. • Customer Name: Enter your customer name. • Site name: Enter your site name. If you have more than one instance of a OnCommand Insight installation, please make sure that the site name is unique. • Site serial number: Enter your serial number. 8. To send the report, click Update and Send Now.

Sending OnCommand Insight logs to ASUP When you request an ASUP report, the report request appears as a job in the Jobs page.

About this task The job is managed by the job queue similar to the processing of other jobs. If an ASUP job is in a Pending or Running state already, an error message appears indicating that the ASUP report request cannot be added to the job request, since the job queue contains pending or running requests.

Steps

1. From the Advanced section of the Data Warehouse Main menu, select Troubleshooting. 2. From the Troubleshooting menu, select Insight ASUP.

76 | OnCommand Insight Data Warehouse Administration Guide

3. In the OnCommand Insight ASUP section, to retrieve the Troubleshooting Report, click Download DWH Troubleshooting Report. 4. To send the troubleshooting information to the OnCommand Insight Server listed as the first connection, click Send Now. 5. To disable automatic ASUP transmissions, click disable.

Viewing OnCommand Insight logs You can view various Data Warehouse and Cognos logs in OnCommand Insight.

About this task You can view the following logs: • Data Warehouse logs • server.log: Lists the status of Server jobs. • jboss.log: Provides information about the Jboss application server. • ldap.log: Logs messages related to LDAP authentication. Data Warehouse Administration | 77

• dwh.log: Lists the status of Data Warehouse jobs. • boot.log: Provides information about the start-up process, the server home directory, the Java version, OS, and server. • dwh_upgrade.log: Provides information about the upgrade on Data Warehouse. • Cognos logs • tomcat.log: Lists the status of the reporting tool. • OnCommand Insightap.log: Provides information about the connection to the server, authentication and access to the Cognos repository, and information about other processes.

Steps 1. From the Advanced section of the Data Warehouse Main menu, select Troubleshooting. 2. In the Troubleshooting page, click Log Files.

3. Click the log file that you want to view.

Migrating business entities When you upgrade, you might need assistance migrating business entities from the previous version to the current version.

About this task After you upgrade to 6.2 and begin to change business entity information, Data Warehouse will include history that points to the older business entities (the ones that are upgraded automatically 78 | OnCommand Insight Data Warehouse Administration Guide

during the installation) and the current data that points to the new business entities. This results in incorrect trend data for two different business entities. To resolve this, use the business entities utility to migrate business entities. Note: This action changes the data in the database. Use this option under the direction of NetApp Technical Support. Use this utility only once after upgrading.

Business entities have a four-part format: ... For example, you might have these items: • NetApp.Data Storage.Legal.patents • NetApp.Data Storage.Marketing.sales events This tool enables you to replace only the business entities with the format of “N/A.N/A.some- business_units.N/A”. The replacement can be done only once per business entity. Only the business entities that are not currently assigned in OnCommand Insight to any object can be replaced.

Steps

1. Back up the Data Warehouse database before starting this process. 2. From the Advanced section of the Data Warehouse Main Menu, select Troubleshooting. 3. In the Troubleshooting view, select Business Entity Migration.

This view displays only the business entities that you can change. 4. For each business entity, from the New Business Entity drop-down, select the new format. 5. For each business entity that you change, click Update. 6. For the message that appears indicating that this action could cause irreversible data change and asking whether you want to continue. To continue with each update, click OK. 7. Repeat the process for each entry. Data Warehouse Administration | 79

Multiple server chassis consolidation issues You can view the connectors that report on hosts and adapters and SAN switches and storage arrays. You can also see the various connectors that report on an object and identify the primary connector, which is the connector that was chosen for the object.

Viewing hosts and adapters consolidation issues The reported data for hosts and their associated adapters is derived from the Inventory data mart.

Steps

1. From the Advanced section of the Data Warehouse Main Menu, select Troubleshooting. 2. Under the Chassis Consolidation section, click Hosts and Adapters.

For all hosts and adapters there is a row for each connector that reports on them, as well as the Primary Connector from which the host and adapter are taken. For hosts and adapters only, a host that is reported by one connector may have its adapters reported by a different connector. You can also see the OnCommand Insight change time of a host/adapter for each connector. Using this parameter, you can discover when an update has occurred in OnCommand Insight for the host/adapter and when the same host/adapter has been updated in other OnCommand Insight servers. 80 | OnCommand Insight Data Warehouse Administration Guide

3. Optionally, filter data in this view by typing a portion of the text and clicking Filter. To clear the filter, clear the Filter box and click Filter. You can filter by host name, host IP, adapter WWN, or OnCommand Insight object ID. The filter is case sensitive. 4. Review the following data:

Host GUID Global Unique Identifier for this type of consolidated device: Host. Host Name Name of the consolidated host as it appears in the data warehouse. Host IP IP address of the consolidated host. Adapter GUID Global Unique identifier for the host adapter. Adapter WWN WWN of the host adapter. Principal Connector Name of the OnCommand Insight connector that was the actual source of the data. Available Connectors All OnCommand Insight connectors where the consolidated host / adapter reside. Insight ID OnCommand Insight ID of the consolidated host/adapter for the relevant reporting connector. Insight Change Time When an update has occurred in OnCommand Insight for the host/ adapter and when the same host/adapter has been updated in other OnCommand Insight servers.

5. To obtain detail about the connector, click on the connector.

You can see the following: Data Warehouse Administration | 81

• Host name • The last time a Data Warehouse job was run on that connector • The last time a change was received from that connector • The version of the OnCommand Insight server pointed to by that connector

Viewing storage arrays consolidation issues The reported data for storage arrays is derived from the Inventory data mart. For all storage arrays, there is a row for each connector that reports on them, as well as the Primary Connector from which each array is taken.

Steps

1. From the Advanced section of the Data Warehouse Main menu, select Troubleshooting. 2. Under Chassis Consolidation, click SAN Storage Arrays. 3. Optionally, filter data in this view by typing a portion of the text and clicking Filter. To clear the filter, clear the Filter box and click Filter. You can filter by storage name, storage IP, vendor model, or OnCommand Insight object ID. The filter is case sensitive. 4. Review the following data

GUID Global Unique Identifier for this type of consolidated device: Storage array. Name Name of the consolidated storage array as it appears in the data warehouse. IP IP address of the consolidated storage array. Vendor and Model Name of the vendor who sells the consolidated storage array and the manufacturer's model number. Principal Connector Name of the OnCommand Insight connector that was the actual source of the data. Available All OnCommand Insight connectors where the consolidated storage Connectors array resides. Insight ID ID of the consolidated storage array on the OnCommand Insight chassis where the Principal Connector resides. Insight Change When an update has occurred in OnCommand Insight for the storage Time array and when the same storage array has been updated in other OnCommand Insight servers. 82 | OnCommand Insight Data Warehouse Administration Guide

Viewing switches consolidation issues The reported data for switches is derived from the Inventory data mart. For all switches, there is a row for each connector that reports on them, as well as the Primary Connector from which each switch is taken.

Steps

1. From the Advanced section of the Data Warehouse Main menu, select Troubleshooting. 2. Under Chassis Consolidation, click SAN Switches. 3. Optionally, filter data in this view by typing a portion of the text and clicking Filter. To clear the filter, clear the Filter box and click Filter. You can filter by switch name, switch IP, vendor model, or OnCommand Insight object ID. The filter is case sensitive. 4. Review the following data:

GUID Global Unique Identifier for this type of consolidated device: Storage array. Name Name of the consolidated storage array as it appears in the data warehouse. IP IP address of the consolidated storage array. Vendor and Model Name of the vendor who sells the consolidated storage array and the manufacturer's model number. WWN WWN for the consolidation switch. Principal Connector Name of the OnCommand Insight connector that was the actual source of the data. Available All OnCommand Insight connectors where the consolidated storage Connectors array resides. Insight ID ID of the consolidated storage array on the OnCommand Insight chassis where the Principal Connector resides. Insight Change When an update has occurred in OnCommand Insight for the storage Time array and when the same storage array has been updated in other OnCommand Insight servers. Data Warehouse Administration | 83

Resolving multiple server annotation consolidation issues The Annotation Consolidation view in the Data Warehouse Troubleshooting view displays a table that contains all the available Annotation Types and the Object Types to which they can be applied.

About this task The consolidation of annotation values is based on the value of the Annotation Type. A storage array could have two different tier values, each coming from a different connector. Thus, if in one connector there is a tier defined by the name gold and in a second connector a tier is defined with the name goldy, this information appears in Data Warehouse as two separate tiers. Because some Annotation Types allow assignment of multiple annotation values to the same object, Data Warehouse allows objects (for example, “host”) to have multiple annotation values assigned to them (for example, “data center 1” and “data center 2" could be assigned to the same host). Tier annotation on volumes functions somewhat differently from the general annotation tables. Potentially, there could be a very large number of volumes in the environment and displaying all of them in the Data Warehouse would affect the usability of the information. Therefore, the Annotations Consolidation view displays only the volumes that have multiple tier values assigned to them, and the storage containing each such volume.

Steps

1. From the Advanced section of the Data Warehouse Main menu, select Troubleshooting. 2. In the Annotation Consolidation section, in the row for the object, click Show. The following shows an example of the annotations for data center.

84 | OnCommand Insight Data Warehouse Administration Guide

OnCommand Insight Data Warehouse user interface reference

OnCommand Insight Data Warehouse includes several main views.

Annotations Page The Annotations page allows you to define information related to objects in your environment. For example, the building and floor of a storage unit can be added as an annotation. Then you can track objects based on their annotations.

Navigation Select Main Menu > Annotations.

Content

Annotation A specific, user-defined piece of information about an object in your environment. Column Name Name of the annotation column that appears in the data mart tables. Target Object Target object to which the annotation can be assigned. Published A check mark in this field indicates that the annotation was already selected for the particular target object and is already available through Data Warehouse data marts.

Options

Edit Allows you to access the Edit Annotations page where you can modify current annotations. Check the Published field to add annotations retrieved from OnCommand Insight into the Data Warehouse database. Click All to select all annotations on all objects. Click None to deselect all options. Check the Init With Current field to initialize historical data in Data Warehouse dimension tables with the current annotation value. Click All to select all annotations on all objects. Click None to deselect all options. This checkbox is disabled once an annotation has been published; the checkbox is enabled for annotations that have not been published.

Related concepts Annotations on page 50 OnCommand Insight Data Warehouse user interface reference | 85

Related tasks Preparing annotations in OnCommand Insight on page 51 Importing user-defined annotations into Data Warehouse on page 41 Viewing the Annotations job in the Jobs list on page 53 Updating annotations in OnCommand Insight reporting on page 53 Using annotations in a Query Studio report on page 55 Seeing the annotation changes in the database schema on page 55

Connectors Page The Connectors page contains information on current connections between OnCommand Insight servers and the Insight Data Warehouse. From this page, you can add connections to or remove connections from OnCommand Insight databases.

Navigation Select Main Menu > Connectors.

Content

Name Name chosen at setup to identify the connector in the Connector view. Host Host IP address. Last Run Last time the connection was accessed. Last Change Last update made to the connection. Site The OnCommand Insight site name. Views Version Server Version The version of the OnCommand Insight server connecting to Data Warehouse. State Indicates if the connection was successfully completed.

Options

New Allows you to input information to set up a new connection or to edit a current connection. Export Allows you to export connector information to an XML file. Import Allows you to import connector information from an existing file.

Related tasks Connecting Data Warehouse to OnCommand Insight servers on page 21 86 | OnCommand Insight Data Warehouse Administration Guide

Jobs Page The build that Data Warehouse performs for each connector and for each data mart is considered a job. The Jobs page displays a list of recently executed jobs and their status.

Navigation Select Main Menu > Jobs.

Content

# Job Number Name Name of the Job Status The status of the job can be listed as complete, skipped, failed, or pending. If a pending status appears, a cancel link also appears that enables you to cancel the job. Start time The date and time the job started to run End time The date and time the job ended

Options

Clear You can clear the history of previously executed jobs. You can clear all history or all History history except the previous 24 hours to remove all but the last day's entries. You cannot clear history of jobs that are pending, running, or in the process of aborting.

Related tasks Managing jobs on page 48

Schedule Page The Schedule page allows you to set the frequency and the time of the build process and enable builds to run as defined.

Navigation Select Main Menu > Schedule.

Content

Enabled Click Edit to select the frequency and time of your build and to enable your job. If you do not enable your job, the build will not occur. OnCommand Insight Data Warehouse user interface reference | 87

Options

Build Now You can use this option to run all scheduled jobs now. Manual Build You can use this option to manually select a specific job to run now.

Related tasks Scheduling daily builds on page 26

Email Notification Page This page enables you set up email notifications to a specific email address when Data Warehouse jobs do not complete successfully.

Navigation Select Main Menu > Email Notifications.

Content You will need to enter the following to set email notification.

SMTP server Server that is acting as the SMTP server in your organization, identified address using either a hostname or an IP address (nnn.nnn.nnn.nnn format). If you specify a host name, make sure the name can be resolved through DNS. SMTP server User name to access the email server, required only if your SMTP server is username and protected by a user login. This is the same user name you use to log in to the password application and accesses your email. Notifications Check Yes. enabled Sender's Email Email account to be identified as the sender on the notification emails. This account must be a valid email account within your organization. Recipient's Email Email address of the person who will always receive the email. This account must be a valid email account within your organization. Email signature Information that will appear at the bottom of the email, for example, the department name.

Related tasks Setting email notifications on page 57 88 | OnCommand Insight Data Warehouse Administration Guide

Copyright © 1994–2013 NetApp, Inc. All rights reserved. Printed in the U.S. No part of this document covered by copyright may be reproduced in any form or by any means— graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. Software derived from copyrighted NetApp material is subject to the following license and disclaimer: THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. NetApp reserves the right to change any products described herein at any time, and without notice. NetApp assumes no responsibility or liability arising from the use of products described herein, except as expressly agreed to in writing by NetApp. The use or purchase of this product does not convey a license under any patent rights, trademark rights, or any other intellectual property rights of NetApp. The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987). 89

Trademark information

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo, Akorri, ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePoint Predictor, Bycast, Campaign Express, ComplianceClock, Cryptainer, CryptoShred, Data ONTAP, DataFabric, DataFort, Decru, Decru DataFort, DenseStak, Engenio, Engenio logo, E-Stack, FAServer, FastStak, FilerView, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol, FPolicy, GetSuccessful, gFiler, Go further, faster, Imagine Virtually Anything, Lifetime Key Management, LockVault, Manage ONTAP, MetroCluster, MultiStore, NearStore, NetCache, NOW (NetApp on the Web), Onaro, OnCommand, ONTAPI, OpenKey, PerformanceStak, RAID-DP, ReplicatorX, SANscreen, SANshare, SANtricity, SecureAdmin, SecureShare, Select, Service Builder, Shadow Tape, Simplicity, Simulate ONTAP, SnapCopy, SnapDirector, SnapDrive, SnapFilter, SnapIntegrator, SnapLock, SnapManager, SnapMigrator, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot, SnapSuite, SnapValidator, SnapVault, StorageGRID, StoreVault, the StoreVault logo, SyncMirror, Tech OnTap, The evolution of storage, Topio, vFiler, VFM, Virtual File Manager, VPolicy, WAFL, Web Filer, and XBB are trademarks or registered trademarks of NetApp, Inc. in the United States, other countries, or both. IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. A complete and current list of other IBM trademarks is available on the web at www.ibm.com/legal/copytrade.shtml. Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the United States and/or other countries. Microsoft is a registered trademark and Windows Media is a trademark of Microsoft Corporation in the United States and/or other countries. RealAudio, RealNetworks, RealPlayer, RealSystem, RealText, and RealVideo are registered trademarks and RealMedia, RealProxy, and SureStream are trademarks of RealNetworks, Inc. in the United States and/or other countries. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such. NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks. NetApp, Inc. NetCache is certified RealSystem compatible. 90 | OnCommand Insight Data Warehouse Administration Guide

How to send your comments

You can help us to improve the quality of our documentation by sending us your feedback. Your feedback is important in helping us to provide the most accurate and high-quality information. If you have suggestions for improving this document, send us your comments by email to [email protected]. To help us direct your comments to the correct division, include in the subject line the product name, version, and operating system. You can also contact us in the following ways: • NetApp, Inc., 495 East Java Drive, Sunnyvale, CA 94089 U.S. • Telephone: +1 (408) 822-6000 • Fax: +1 (408) 822-4501 • Support telephone: +1 (888) 463-8277 Index | 91 Index

A C accessing Cognos documentation 16 Data Warehouse Portal 19, 45 connectors 85 MySQL 20 consolidation issues Reporting Portal 57 hosts and adapters 79 advanced options multiple servers 83 backing up the Data Warehouse database 28, 67 storage arrays 81 building the database from history 22, 61 switches 82 migrating business entities 77 resetting the database 67 restoring the database 30, 69 D skipping failed builds 65 data capacity fact maintenance 11 troubleshooting 71 data models user management 34 updating annotations 53 annotations data retention 12 displaying in database schema 55 Data Warehouse forcing an update 23, 40, 62 accessing data as MySQL user 20 importing 41, 50, 51 administration 31 troubleshooting 39, 83 backing up database 28, 67 updating the data model 53 building database from history 22, 61 viewing in Jobs list 53 components 6 Assure connecting to OnCommand Insight servers 21, 46 features 13 database AutoSupport (ASUP) resetting 67 configuring 73 restoring 30, 69 troubleshooting 72 database schemas 59 documentation 58 B Extract, Transform, Load (ETL) process 9 features 6 backing up 28, 67 getting started 18 backups login and password 19, 45 report artifacts 29, 69 managing jobs 48 best practices opening management portal 31 saving custom reports 29, 69 overview 6 building database from history processes data 22, 61 consolidation 9 builds ETL 9 adding from history 24, 63 jobs 9 cancelling 26, 65 requests to DWH 9 scheduling 26, 49 scheduling builds 26, 49 skipping failed 65 software components 8 business entities troubleshooting 71 migrating in Data Warehouse 77 version and upgrade history 60 Data Warehouse database 28, 67 Data Warehouse Portal 92 | OnCommand Insight Data Warehouse Administration Guide

accessing 19, 45 annotations 50 database schema 59 user-defined annotation 41, 51 documentation 58 installation login and password 19, 45 viewing component versions 60 resetting the DWH database 67 viewing license information 60 restoring the DWH database 30, 69 database schemas Data Warehouse 59 J seeing annotations 55 jobs 86 databases jobs management 48 backing up Data Warehouse 28, 67 documentation Cognos 16 L Data Warehouse 58 LDAP list of 15 configuring for Reporting 34 OnCommand Insight 16 licenses videos 14 Reporting roles 31 viewing installed 60 E logins and passwords 19, 45 email setting up notifications 87 M email notifications, setting 57 managing extracting data from OnCommand Insight into Data jobs in DWH 48 Warehouse user accounts 34 data retention 12 MySQL, accessing data in Data Warehouse 20 frequency 10

F N notifications, email 57 failed builds, skipping 65 features, Data Warehouse 6 O G OnCommand Insight connecting DWH with servers 21, 46 getting started documentation 16 accessing the Data Warehouse Portal 19, 45 extracting data from 9 setting up connections 21, 46 product portfolio 13 setting up daily builds 26, 49 Reporting Portal 8 setting up historical database build 22, 61 setting up multiple tenancy 36 P H Perform features 13 historical data retention 11 Plan features 13 I reporting user roles 31 processes importing consolidation 9 Index | 93

data capacity fact maintenance 11 user access 20 ETL 9 system information 60 Jobs 9 requests to DWH 9 product documentation T list of 15 troubleshooting annotations 39 R AutoSupport (ASUP) 72 consolidation of servers 83 Reporting Data Warehouse 71 adding users 33 report numbers 43 administration 31 configuring LDAP 34 open the portal 31 U user roles 31 upgrading Reporting Portal, accessing 57 backing up the database prior to 28, 67 reports reports 70 authoring tools 8 user accounts backing up artifacts 29, 69 assigning to business entities 37 upgrading 70 configuring 37 resetting the DWH database 67 managing 34 restoring the DWH database 30, 69 number of users per role 34 roles users Reporting 31 Reporting roles 31, 33

S V schedules 86 version and upgrade history 60 scheduling, daily builds 26, 49 videos schemas and schema diagrams display 59 Community portal 14 site name, editing 60 skipping failed builds 65 software components 8 SQL queries