Sunteți pe pagina 1din 88

BMC Reporting Foundation

Installation Guide

Supporting
BMC Reporting Foundation 3.0
February 2008

www.bmc.com

Contacting BMC Software


You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information about the company, its products, corporate offices, special events, and career opportunities.

United States and Canada


Address BMC SOFTWARE INC 2101 CITYWEST BLVD HOUSTON TX 77042-2827 USA Telephone 713 918 8800 or 800 841 2031 Fax 713 918 8000

Outside United States and Canada


Telephone (01) 713 918 8800 Fax (01) 713 918 8000

Copyright 2008 BMC Software, Inc. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. Oracle is a registered trademark of Oracle Corporation. UNIX is the registered trademark of The Open Group in the US and other countries. Java, Solaris, and Sun are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries. BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation.

Restricted rights legend


U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address.

Customer support
You can obtain technical support by using the BMC Software Customer Support website or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, see Before contacting BMC.

Support website
You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this website, you can
I I I I I I I I

read overviews about support services and programs that BMC offers find the most current information about BMC products search a database for issues similar to yours and possible solutions order or download product documentation download products and maintenance report an issue or ask a question subscribe to receive proactive e-mail alerts when new product notices are released find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers

Support by telephone or e-mail


In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or send an e-mail message to customer_support@bmc.com. (In the subject line, enter SupID:<yourSupportContractID>, such as SupID:12345). Outside the United States and Canada, contact your local support center for assistance.

Before contacting BMC


Have the following information available so that Customer Support can begin working on your issue immediately:
I

product information product name product version (release number) license number and password (trial or permanent)

operating system and environment information machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or maintenance level

I I I

sequence of events leading to the issue commands and options that you used messages received (and the time and date that you received them) product error messages messages from the operating system, such as file system full messages from related software

License key and password information


If you have questions about your license key or password, contact BMC as follows:
I

(USA or Canada) Contact the Order Services Password Team at 800 841 2031, or send an e-mail message to ContractsPasswordAdministration@bmc.com. (Europe, the Middle East, and Africa) Fax your questions to EMEA Contracts Administration at +31 20 354 8702, or send an e-mail message to password@bmc.com. (Asia-Pacific) Contact your BMC sales representative or your local BMC office.

BMC Reporting Foundation Installation Guide

Contents
Chapter 1 BMC Reporting Foundation components 9 Introducing BMC Reporting Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Reporting components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Reporting server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Report portal (InfoView) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 BMC Reporting Foundation Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Import Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Central Management Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Auditing database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Publishing Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Universes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 User groups and users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Databases and data collection tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Reports and report templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Java report panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Chapter 2 Preparing to install BMC Reporting Foundation 17 18 18 19 19 19 20 20 23 26 27 27 27 28 33 33 34 37 39

Installation introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Computer roles - what goes where . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communication protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Oracle Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation prerequisites for the BMC Reporting Foundation Database . . . . . . . . . . Considerations for new installations on Windows computers. . . . . . . . . . . . . . . . Considerations for new installations on Solaris computers . . . . . . . . . . . . . . . . . . Other Requirements for Foundation Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compatibility with other products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installable images and the Distribution Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for the Reporting Server computer . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for the Report Viewer computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for the Client Tools computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for the Foundation Database host computer . . . . . . . . . . . . . . . . . . Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 3 Installing BMC Reporting Foundation on Windows computers

Installing BMC Reporting Foundation on Windows computers overview . . . . . . . . 39


Contents 5

Verifying installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Installing the BMC Reporting Foundation Database . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Installing BMC Reporting Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Installing all BMC Reporting Foundation components on one computer . . . . . . 43 Installing Client Tools only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 About web servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Uninstalling BMC Reporting Foundation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Uninstalling BMC Reporting Foundation on Windows. . . . . . . . . . . . . . . . . . . . . . 48 Chapter 4 Installing BMC Reporting Foundation on Solaris 51

Installing BMC Reporting Foundation on UNIX computers overview . . . . . . . . . . . . 51 Verifying installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Using an xterm to Install BMC Reporting Foundation . . . . . . . . . . . . . . . . . . . . . . 52 Mounting a CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Installing BMC Reporting Foundation Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Installing BMC Reporting Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Uninstalling BMC Reporting Foundation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Uninstalling BMC Reporting Foundation on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . 60 Chapter 5 Using the report portal 61

Report portal overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Starting the report server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Verifying the report server is started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Stopping the report server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Starting the report portal (InfoView). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Set the time out for the input and output file repository servers . . . . . . . . . . . . . . . . . 66 Set the Connection time out for the Web_IntelligenceReportServer service server . . 67 Chapter 6 BMC Reporting Foundation Database administration 69

BMC Reporting Foundation Database administration overview . . . . . . . . . . . . . . . . . 69 Starting and stopping the BMC Reporting Foundation Database . . . . . . . . . . . . . 69 Changing the BMCREPO password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Appendix A Frequently Asked Questions 71

Verifying whether the CMS is running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Accessing Infoview and Central Management Console . . . . . . . . . . . . . . . . . . . . . . . . . 72 Enabling drilling mode and creating new reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Starting the BusinessObjects Enterprise servers manually . . . . . . . . . . . . . . . . . . . . . . 73 Changing passwords using the Central Management Console. . . . . . . . . . . . . . . . . . . 73 Enabling audit actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Starting and stopping the BMC Reporting Foundation servers . . . . . . . . . . . . . . . . . . 75 Processes and services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Index 79

BMC Reporting Foundation Installation Guide

Tables
Tables with computer role requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware and Software required for the Reporting Server on Windows . . . . . . . . . Hardware Required for the Reporting Server on Solaris . . . . . . . . . . . . . . . . . . . . . . . Software Required for the Reporting Server on Solaris . . . . . . . . . . . . . . . . . . . . . . . . Software requirements for Report Viewer computer . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for Client Tools computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware required for BMC Reporting Foundation Database host computer . . . . . Software required for BMC Reporting Foundation Database host computer on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for BMC Reporting Foundation Database host computer on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software and Settings Required for BMC Reporting Foundation Database host computer on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC Reporting Foundation Installation Procedures for Windows . . . . . . . . . . . . . . 28 29 30 31 33 34 34 35 35 36 42

Tables

BMC Reporting Foundation Installation Guide

Chapter

BMC Reporting Foundation components


1

This chapter provides basic information on BMC Reporting Foundation. It presents the following topics: Introducing BMC Reporting Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Reporting components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Reporting server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Report portal (InfoView) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 BMC Reporting Foundation Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Import Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Central Management Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Auditing database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Publishing Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 User groups and users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Databases and data collection tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Reports and report templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Java report panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Introducing BMC Reporting Foundation


BMC Reporting Foundation provides the base on which BMC Software reporting systems and solutions are built. It is prerequisite for all BMC Reporting solution sets. Reporting Foundation uses Business Objects, a third party business intelligence system, as the reporting engine that administers and publishes the reports. Reporting Foundation does not include the database that contains the data used in the reports.

Chapter 1

BMC Reporting Foundation components

Reporting components

By itself, BMC Reporting Foundation cannot create or display any reports. Reporting Foundation works with reporting solution sets that provide the data and the reporting formats for the solution set reports. For example, BMC Performance Manager Reporting includes the PATROL Aggregate Database and a set of preconfigured templates to provide reports about parameter data from PATROL Agents. BMC Reporting Foundation is included as a component in each of the BMC reporting solutions sets. BMC Reporting Foundation also allows you to create new reports using any of the BMC reporting solution sets you have installed.

Reporting components
BMC Reporting Foundation contains the following components:
I

Reporting Foundation Server I Reporting server I Central Management Server I Help BMC Foundation Database server I Oracle I BMC Performance Manager Foundation database Client Tools I The Publishing Wizard I The Import Wizard I The Data Source Migration Wizard I The Business View Manager I Desktop Intelligence I Universe builder I Report Conversion Tool

The reporting solution sets provide the additional components required to have a complete reporting solution. Each solution set will contain some or all of the following:
I I I I I I I

Universe database data collection tools predefined reports report templates predefined users and user groups additional categories

10

BMC Reporting Foundation Installation Guide

Reporting server

Reporting server
The reporting server is the web server that manages all reporting activity. It uses either Apache or IIS as the server software.

Report portal (InfoView)


The report portal is a browser-based interface you use to connect to the report server to view and administer reports. The portal, also called InfoView, is the single point of contact for report viewing, for searching for a particular report, for determining what reports have already been produced, and for saving reports. You can use the report portal to create categories for reports. Because it is browser-based, you can access the reports from any location that has access to the Reporting server. Each Business Objects tool contains context sensitive help. In addition, the report portal provides Help for BMC Reporting Foundation, and any solution set that you have installed. Depending on the solution set, each report may also have context sensitive help. You can access the Report Portal (Infoview) from http://hostname:8080/businessobjects/enterprise115/desktoplaunch/InfoView/ logon/logon.object

BMC Reporting Foundation Database


The BMC Reporting Foundation Database (also referred to as the Foundation Database or BMCREPO) is an Oracle database that stores information about the system and its users. The primary database, which is maintained by the Central Management Server (CMS), is known as the CMS database. You can use the BMCREPO database instance with the BusinessObjects Enterprise Auditor.

WARNING
If you reinstall Reporting Foundation, and you repopulate the Foundation Database, you will lose all the customizations you have made to the Foundation Database.

Chapter 1

BMC Reporting Foundation components

11

Import Wizard

Import Wizard
You can use Import Wizard to import users, groups, and reports from an existing BusinessObjects Enterprise installation. The Import Wizard runs on Windows and you can use it to import information into a new BusinessObjects Enterprise system running on Windows or on UNIX. The Import Wizard allows you to import the Business Intelligence Application Resource (BIAR) file that contains the solution reports, users and universe.

Central Management Server


The CMS is responsible for maintaining a database of information about your BusinessObjects Enterprise system, which other components can access as required. The data stored by the CMS includes information about users and groups, security levels, BusinessObjects Enterprise content, and servers. The CMS also maintains the BusinessObjects Enterprise Repository and information about user actions. This data allows the CMS to perform its four main tasks:
I I I I

maintaining security managing servers managing auditing managing objects

You can access the Central Management Console from: http://hostname:8080/businessobjects/enterprise115/admin/en/admin.cwr

12

BMC Reporting Foundation Installation Guide

Auditing database

Auditing database
Auditor is a product that allows you to audit your BusinessObjects Enterprise deployment. The Auditor has the following key features:
I

I I

It monitors and records key facts that you want audited in your deployment of BusinessObjects Enterprise. It contains many predefined reports designed to answer many of the questions you may have about your deployment of BusinessObjects Enterprise. It includes the universe on which these reports are built so you can customize the reports that are included or create your own reports. Auditor consists of a universe and a set of reports. The Central Management Server (CMS) acts as the system auditor, while each BusinessObjects Enterprise server that controls actions that you can monitor is an auditee. As the auditee, the BusinessObjects Enterprise server records these audit actions in a local log file. As the auditor, the CMS controls the overall audit process. Each server writes audit records to a log file local to the server. At regular intervals the CMS communicates with the auditee servers to request copies of records from the auditee's local log files. When the CMS receives these records it writes data from the log files to the central auditing database.

WARNING
When you migrate the auditing BIAR file, error messages related to the crystal reports are generated. Please ignore these error messages as Crystal Reports is not supported by BMC Reporting Foundation.

For more information about auditor, see the BusinessObjects Enterprise XI Release 2 Administrators Guide and BusinessObjects Enterprise XI Release 2 Auditors Guide. For information about enabling audit actions, see Enabling audit actions on page 74.

Publishing Wizard
The Publishing Wizard is a locally installed Windows application that enables you to add reports to BusinessObjects Enterprise. By assigning object rights to BusinessObjects Enterprise folders, you can control access for publishing reports. The Publishing Wizard publishes reports from a Windows computer to BusinessObjects Enterprise servers running on Windows or on UNIX.

Chapter 1

BMC Reporting Foundation components

13

Universe

Universe
The universe is a description of the database or a part of the database. It describes the database objects in everyday language so that you can create reports without knowing SQL. The universe is a collection of objects used as building blocks for the reports. The objects provide a map between the reports and the schema of the data source that contains the data to be used in the reports. The universe uses the mapping information to generate the SQL structures for retrieving the data for each report. The universe is provided by the specific reporting solution sets you are using. Consult the user documentation for the report solution set for specific information about its universe.

Categories
Categories are a way of organizing documents. They are like a filing system because you can group like reports into the same category. However, you are not limited to one category per report. A report can be assigned to more than one category. The reporting solution sets may add more categories, and you can add categories.

User groups and users


BMC Reporting Foundation provides the highest level user, Administrator. The reporting solution sets may add more user groups and users, and you can add or delete user groups and users.

Databases and data collection tools


Each reporting solution set either provides a database for storing report data and tools to collect the data as needed, or it uses a database and collection tools provided by another solution set. For example, Base Reporting for PATROL contains the Foundation database and the Aggregator for retrieving parameter data from managed computers.

14

BMC Reporting Foundation Installation Guide

Reports and report templates

Reports and report templates


Solution sets may contain predefined reports, also called solution reports. These reports are already defined and scheduled so that you can immediately begin using them. Solution sets may also contain report templates that allow you to quickly configure reports containing the data you need.

Java report panel


The Java report panel provides an easy-to-use drag-and-drop interface for creating new reports. It also contains state-of-the-art graphs and charts and sophisticated filtering tools. You can use the Java report panel to create reports that clearly present the information you want to review.

Chapter 1

BMC Reporting Foundation components

15

Java report panel

16

BMC Reporting Foundation Installation Guide

Chapter

Preparing to install BMC Reporting Foundation


2

This chapter provides the information that you need to prepare to install BMC Reporting Foundation on Windows and UNIX computers. For installation instructions, see Chapter 3, Installing BMC Reporting Foundation on Windows computers and Chapter 4, Installing BMC Reporting Foundation on Solaris. For additional information about the PATROL installation process, see the PATROL Installation Reference Manual. This chapter presents the following topics: Installation introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Computer roles - what goes where . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communication protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation prerequisites for the BMC Reporting Foundation Database . . . . . . . . . . Considerations for new installations on Windows computers. . . . . . . . . . . . . . . . Considerations for new installations on Solaris computers . . . . . . . . . . . . . . . . . . Other Requirements for Foundation Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compatibility with other products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installable images and the Distribution Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for the Reporting Server computer . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for the Client Tools computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for the Foundation Database host computer . . . . . . . . . . . . . . . . . . Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 18 19 19 20 20 23 26 27 27 27 28 33 34 37

Chapter 2

Preparing to install BMC Reporting Foundation

17

Installation introduction

Installation introduction
The BMC Reporting Foundation installation is only part of the installation of a BMC reporting solution set. See Reporting components on page 10 for a description of the components that are part of BMC Reporting Foundation. After BMC Reporting Foundation has been installed, you must install additional components from the reporting solution set using the product CDs from the reporting solution set.

NOTE
Review the instructions in the user documentation for the reporting solution set before installing BMC Reporting Foundation.

Computer roles - what goes where


There are four distinct computer roles that BMC Reporting Foundation requires. In addition, the reporting solution sets require additional roles. See the documentation for your reporting solution set for more information about the roles for that solution set, and how the different roles relate to each other. When planning to install the BMC Reporting Foundation, note that you will need computers to fulfill the roles described in the following table:
Role CMS Server Description The CMS is responsible for maintaining a database of information about the BusinessObjects Enterprise system, which other components can access as required. The Import Wizard component must be installed a Microsoft Windows computer. If the Reporting Server is a Solaris computer, install the Client Tools on a Windows computer. The Foundation Database host computer can be a Solaris or Windows computer. It requires an Oracle server. You can either use an existing Oracle server or install an Oracle server using the BMC DataStore 2.5.10 CD. Any computer where users view reports. It requires a web browser.

Import Wizard

Foundation Database host server

Report Viewer

A computer may fulfill more than one of the required roles. This chapter contains more information about which BMC Reporting Foundation components must be installed for each role, and the system requirements for the installations.

18

BMC Reporting Foundation Installation Guide

Communication protocols

Communication protocols
Communication between Oracle and BMC Reporting Foundation is based on the TCP/IP protocol. BMC Reporting Foundation uses Hyper Text Transfer Protocol (HTTP) for client communication.

Oracle Requirements
For Oracle-related operations and installing BMC Performance Manager Reporting, you must be a:
I I

Member of the Administrator group Member of the ORA_DBA group (If Oracle server is installed and configured on the same computer hosting BMC Reporting Foundation)

User accounts
The user account you use when installing or running BMC Reporting Foundation on a Windows computer and the computer hosting the Aggregator must be a member of the Administrators group. It must also have the following privileges:
I I I I I I I

Act as part of the operating system Increase quotas Log on as a service Replace a process-level token Log on locally Profile system performance Debug programs

For Solaris, BMC Software recommends you use a local logon and local groups for the installation. If these permissions are not set, BMC Reporting Foundation may not be able to run as a service.

Chapter 2

Preparing to install BMC Reporting Foundation

19

Installation prerequisites for the BMC Reporting Foundation Database

Installation prerequisites for the BMC Reporting Foundation Database


The BMC DataStore Installer is used to create the Reporting Foundation Database instance. Ensure that the target computers for the BMC DataStore meets or exceed the system requirements listed in the BMC DataStore Installation Guide and the following sections.

Considerations for new installations on Windows computers


A BMC DataStore installation on a Windows computer has the following requirements:
I

The user running the installation program must have administrator rights and permissions on the target computer and be a member of its Administrators group. The target computer must have a static IP address. If the target computer uses Windows Dynamic Host Configuration Protocol (DHCP) to assign an IP address dynamically, you must install the Microsoft Loopback Adapter before you install the BMC DataStore. See Installing a loopback adapter on page 23. The installation directory name cannot contain spaces. The DataStore cannot be installed on a shared drive on a remote Windows computer. It must be installed on a local drive. The target computer cannot have an existing Oracle installation unless the installation is part of an existing Portal installation.

WARNING
The installation program stops if it detects an ORACLE_* environment defined on your user system. Common examples of these environment variables include
I I I I I

ORACLE_BASE ORACLE_HOME ORACLE_USER ORACLE_GROUP ORACLE_SID

20

BMC Reporting Foundation Installation Guide

Considerations for new installations on Windows computers

Before installing the DataStore, you must disable firewall protection programs, such as McAfee Host Intrusion Prevention Service (HIPS), on the target computer and leave them disabled after the DataStore is installed. HIPS can block access to ports that are used by the installation program during installation and by the Portal at runtime. You must reboot the computer after you disable the service.

Configuring DEP for a DataStore installation on computers with Windows Server 2003 SP1
Before installing the BMC DataStore on a Windows Server 2003 SP1 computer, you must configure the data execution prevention (DEP) feature to recognize the installation program. If the DEP is not configured to recognize the installation program, the DEP can block the installation program from continuing and an error message might appear stating that DEP is blocking the installation program. This problem is caused by an enhanced DEP feature that Microsoft included in SP1.

To configure a Windows Server 2003 SP1 computer to recognize the BMC DataStore installation program 1 Insert the BMC Reporting Foundation installation DVD or BMC DataStore
installation CD1 in the CD-ROM tray.

2 From the Windows Desktop, right-click the My Computer icon. 3 Select Properties. 4 Select the Advanced tab. 5 Under the Performance heading, select Settings. 6 Select the Data Execution Prevention (DEP) tab. 7 Select Turn on DEP for programs and services except those I select. 8 Click Add. 9 On the DVD or CD drive, select setup.exe (in the BMCDatastore\disk 1 directory on
the DVD).

10 Click Open. 11 Click Apply. 12 Click OK. 13 Click OK to close the System Properties window.

Chapter 2

Preparing to install BMC Reporting Foundation

21

Considerations for new installations on Windows computers

14 Perform one of the following actions:


I I

If you are not using Windows Terminal Services, reboot the computer. If you are using Windows Terminal Services, proceed to Configuring computers running Terminal Services on page 22 before rebooting the computer.

NOTE
If you are installing the Portal application server and web server on the same target computer as the DataStore, configure DEP to recognize the BMC Reporting Foundation installation program also before you reboot the computer. For instructions on configuring DEP for the BMC Reporting Foundation installation program, see the Configuring DEP for a DataStore installation on computers with Windows Server 2003 SP1 on page 21.

Configuring computers running Terminal Services


Terminal Services creates a temp directory for each user account, and the installation program creates log files in this directory. At the end of the session, Terminal Services deletes the temp directory and any files that it contains, including the installation log files. To circumvent this behavior, perform the following procedure.

To configure Terminal Services for BMC DataStore installation 1 Using the Terminal Services configuration tool, start the Terminal Services
Configuration MMC snap-in.

2 Select the Server Setting folder. 3 In the Server Setting folder, double-click Permission Compatibility, select either Full
security or Administrator, and click OK.

4 In the Delete temporary folders on exit text box, change the default setting to No and
click OK.

5 In the Use temporary folder per session text box, change the default setting to No and
click OK.

6 Navigate to the following registry key:


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server

7 Verify that the registry key has the following temporary folder settings:
I

Value: PerSessionTempDir Type: REG_DWORD Data value: 0 (enabled, the default setting)

22

BMC Reporting Foundation Installation Guide

Considerations for new installations on Solaris computers

Value: DeleteTempDirsOnExit Type: REG_DWORD Data value: 0 (enabled, the default setting) Value: FlatTempDir Type: REG_SZ Data value: 1 (enabled, the default setting)

NOTE
This registry value exists only if flat temporary folders are enabled. If flat temporary folders are disabled, the FlatTempDir value is not present.

8 Reboot the computer. NOTE


You must reboot the computer before you start the installation program; otherwise, the installation fails.

Installing a loopback adapter


If the Windows Dynamic Host Configuration Protocol (DHCP) service is used on the target computer to dynamically assign an IP address, you must install and configure a loopback adapter. If a loopback adapter is not installed, the BMC DataStore installation might fail or the BMC Reporting Foundation might lose connectivity to the datastore after the installation is complete. For instructions for installing a loopback adapter on Windows 2000 and Windows Server 2003 32-bit platforms, see the Oracle Database Installation Guide 10g Release 2 (10.2) for Microsoft Windows (32-Bit). For instructions for installing a loopback adapter on Windows Server 2003 64-bit platforms, see the Oracle Database Installation Guide 10g Release 2 (10.2) for Microsoft Windows (x64). You can access both the documents on the Oracle website at the following URL: http://www.oracle.com/technology/documentation/database10gr2.html

Considerations for new installations on Solaris computers


A BMC DataStore installation on a Solaris computer has the following requirements:
I

On the target computer, log on as root (or run su - root to switch to root) to run the installation program.
Chapter 2 Preparing to install BMC Reporting Foundation 23

Considerations for new installations on Solaris computers

The target computer must have a static IP address. The umask must be set to 022 (for example, umask 022). Other umask settings cause the datastore installation to fail. The DISPLAY environment variable must be set correctly. X Windows access control must be disabled. The nobody user account must exist on the target computer. Oracle on Solaris requires a unique user account, oracle, to handle various database functions. Additionally, Oracle requires a unique group, and this group must be the primary group for the oracle user account. The root account must be in this same group. Before starting the installation program, perform the following tasks to accomplish these requirements: 1. Create a group called dba. 2. Make the root account a member of the dba group. 3. Create the oracle user account and make the dba group the primary group for this account.

WARNING
I I

Do not use the root account as your Oracle account. Do not use the root accounts UID for the Oracle account.

The oracle user account must execute /etc/profile automatically when the user logs on. The installation program creates the /etc/bmc.profile and adds it to the /etc/profile script. If the oracle user account logon does not execute these scripts, the product fails to install properly. Enable the oracle user so that it can run in a noninteractive mode. The product routinely logs on to the account in noninteractive mode and cannot function properly if a user response is required at logon. Ensure that a noninteractive logon to the user account does not prompt for user input before it gets to a command shell or result in any output, such as messages of the day (MOTD) or error messages that are generated by executing account logon scripts. Error messages and output could interfere with the installation. Ensure that the oracle user has a home directory specified in /etc/passwd and that it has full permissions to read, write, and execute files in the home directory.

24

BMC Reporting Foundation Installation Guide

Considerations for new installations on Solaris computers

The installation program checks for specific memory requirements for the Oracle database before it creates the database. If the program finds that the existing memory parameters do not satisfy the database requirements, the installation terminates. If the target computer is a Solaris 8 or Solaris 9 computer, before restarting the installation program, perform one of the following actions to assign the minimum settings listed in Figure 1 to /etc/system, and reboot the computer. Run the setSolarisSettings.sh script from the BMC DataStore installation CD 1 (in the utility/scripts directory). Manually edit /etc/system by appending the lines listed in Figure 1 to the file. Figure 1
set set set set set set set set set set

Minimum memory parameter settings for Solaris 8 and 9 databases

shmsys:shminfo_shmmax=4294967295 shmsys:shminfo_shmmin=1 shmsys:shminfo_shmmni=100 shmsys:shminfo_shmseg=100 semsys:seminfo_semmni=100 semsys:seminfo_semmsl=256 semsys:seminfo_semmns=1024 semsys:seminfo_semopm=100 semsys:seminfo_semvmx=32767 semsys:seminfo_semume=30

In addition, see the section on configuring kernel parameters in the Oracle Database Installation Guide 10g Release 2 (10.2) for Solaris Operating System (SPARC 64-bit) at the following URL for instructions on setting these parameters: http://www.oracle.com/technology/documentation/database10gr2.html
I

If you do not use the default installation directory, ensure that the specified directory is not deeper than two directory levels in the directory structure.

Chapter 2

Preparing to install BMC Reporting Foundation

25

Other Requirements for Foundation Database

The target computer cannot have an existing Oracle installation unless the installation is part of an existing Portal installation.

WARNING
The installation program stops if it detects an ORACLE_* environment variables in your user account or in the oracle account. Examples of these environment variables include
I I I I I

ORACLE_BASE ORACLE_HOME ORACLE_USER ORACLE_GROUP ORACLE_SID

Ensure that the oracle user profile does not define these environment variables.

If you are installing the BMC DataStore into a nonglobal (local) zone on a Solaris 10 computer, when you create the zone, you must configure the file system, allocate disk space, verify that the /usr/local directory exists on the target computer, and set kernel parameters. For Oracle to operate efficiently on Solaris systems, it must bypass the file system buffering and perform direct I/O. The default file system mount options on Solaris do not enable this option, but you can enable direct I/O. This task should be performed after the database has been created.

Other Requirements for Foundation Database


BMC Reporting Foundation uses the Oracle relational database management system. Note the following requirements and considerations prior to installing the Foundation Database and the Oracle software.
I

You must install the Oracle database server included in the BMC DataStore 2.5.10 CD. If you plan on installing the Foundation Database on a different system than the Reporting Server, then you must also install the Oracle client software on the Reporting Server computer. See also Requirements for the Reporting Server computer on page 28.

26

BMC Reporting Foundation Installation Guide

Compatibility with other products

If you are installing the Foundation Database on a Solaris computer, create an oracle user on the target Solaris computer prior to starting the installation program, and assign the user to the oracle group. The oracle user account requires the same level of permission as the root account. The oracle user account must execute /etc/profile during logon. The installation program creates the bmc.profile and adds . /etc/bmc.profile to the /etc/profile script. If the logon does not execute these scripts, the product will fail to install properly. Enable the oracle user so that it can run in a non-interactive mode. The product routinely logs on the account and cannot function properly if a user response is required at logon.

Ensure that the PATH environment variable does not exceed the maximum length of 1023 characters, otherwise the Oracle database install program will fail.

Compatibility with other products


If BMC Reporting Foundation is installed on a computer where the PATROL Central Web Server is already installed, the web browser on that computer will not be able to connect to that web console. Browsers on other computers are not affected and can connect to that web console. If the PATROL Central Web Server is installed after BMC Reporting Foundation, there is no problem.

Installable images and the Distribution Server


The installation program does not create a valid installable image for BMC Reporting Foundation components. You cannot install BMC Reporting Foundation components with the Distribution Server.

Installation requirements
This section describes the hardware and software requirements for installing BMC Reporting Foundation. There are additional requirements for the particular reporting solution set that you are installing. See the user documentation for the solution set for more information. The BMC Reporting Foundation server components and Foundation Database can be installed on either Windows or Solaris computers. However, the Client Tools, a required administrative component, can only be installed on a Windows computer.

Chapter 2

Preparing to install BMC Reporting Foundation

27

Requirements for the Reporting Server computer

If you install more than one component on a particular computer, be sure the computer meets the requirements for all the components on that computer. Table 1 shows which table contains information for each type of installation. Table 1
Role BMC Reporting Server

Tables with computer role requirements


Operating System Windows Solaris Type of Requirement Hardware Software Hardware Software Requirements Table Table 2 on page 29 Table 2 on page 29 Table 3 on page 30 Table 4 on page 31 Table 5 on page 33

Report Viewer Client Tools BMC Foundation Database host

Windows and Software Solaris Windows Windows Solaris

Hardware and Table 6 on page 34 Software Hardware Software Hardware Software Table 7 on page 34 Table 8 on page 35 Table 9 on page 35 Table 10 on page 36

Verify that the target computer meets the installation requirements listed in the appropriate table or tables.

Requirements for the Reporting Server computer


The Reporting Server can be on a Solaris or Windows computer. Most of the Business Objects software is installed here. If this computer is a different system than the computer hosting the Foundation Database host server, you need to install the Oracle client software on the computer for connecting to the Foundation Database. You can download the Oracle client installer from http://www.oracle.com/technology/software/tech/oci/instantclient/htdocs/wins oft.html.

Windows
Table 2 contains hardware and software requirements for installing required components for the Reporting Server on Windows computers.

28

BMC Reporting Foundation Installation Guide

Requirements for the Reporting Server computer

Table 2
Resource operating systems

Hardware and Software required for the Reporting Server on Windows


Requirement One of the following:
I I I

Comments The server cannot be configured as either a PDC (Primary Domain Controller) or a BDC (Backup Domain Controller). Windows support is limited to the 32-bit versions of Windows operating systems on either 32 or 64-bit (x86) AMD/Intel chipsets. Recommended

Windows 2000 Server Service Pack 4 Windows 2000 Advanced Server Service Pack 4 Windows Server 2003 Server

browser

One of the following:


I I I

Internet Explorer 7.0 Internet Explorer 6.0 Service Pack 1/ Service Pack 2 Mozilla Firefox 2.0 Intel Pentium3 700 MHz or higher Intel Pentium4 2.4 GHz or higher

CPU RAM

I I

4 GB or higher

disk space used 5 GB hard disk space for BusinessObjects after installation Enterprise and additional 1.5 GB for Performance Management Application Servers ports
I

Microsoft Internet Information Server 6.0 (only if you want to use IIS with BMC Reporting Foundation) Business Objects needs a series of 11 ports for its use, which must not be in use by any other process. The Apache and Tomcat software must have unique port numbers for their use which are not in use by any other processes.
I

Port 8005 is a default port used by PATROL Central Operator - Web Edition. and the default port used by Apache. If you have PATROL Central Operator - Web Edition installed on the computer where you want to install BMC Reporting Foundation, you must change the default port for either PATROL Central Operator Web Edition or Apache.

Document viewer

Adobe Acrobat v 5.0 or later

Business Objects documentation is installed with the reporting server.

Chapter 2

Preparing to install BMC Reporting Foundation

29

Requirements for the Reporting Server computer

Solaris
Table 3 and Table 4 contain hardware and software requirements for installing required components for the Reporting Server on Solaris computers. Table 3
Resource CPU disk space used after installation RAM

Hardware Required for the Reporting Server on Solaris


Requirement SPARC v8 plus 5 GB

4 GB or higher

30

BMC Reporting Foundation Installation Guide

Requirements for the Reporting Server computer

Table 4
Resource operating systems

Software Required for the Reporting Server on Solaris (part 1 of 3)


Requirement One of the following:
I

Comments

Please consult SunTM support for the latest Solaris version 8 minimum install and the following packages versions of these patches. and patch clusters:
I I I I I I I I I I I I I I I I I I I I I I I I

108993-32 (thread, c and other library patch) 109778-13 (Misc loc having errors in CTYPE and lv colln monetary) 112668-01 (gzip patch) 112611-02 (libz patch) 110951-04 (tar patch) 108528-24 (kernel patch) 108434-13 (Shared library patch for C++ runtime SunOS 8) 109147-26 (linker patch) 109324-05 (/bin/sh family patch) 114059-02 (en_US.UTF-8 locale patch) SUNWscpu (Source compatibility) SUNWuiu8 (Iconv modules for UTF-8 Locale) SUNWxwfnt (W Window System required fonts) SUNWxwplt (X Window System platform software) SUNWgzip (The GNU Zip (gzip) compression utility) SUNWzlib (The Zip compression library) SUNWbash (GNU Bourne-Again shell (bash)) SUNWbcp (SunOS 4.x Binary Compatibility) SUNWlibC (Sun Workshop Compilers Bundled libC) SUNWeuluf (UTF-8 L10N For Language Environment User Files) SUNWulcf (UTF-8 Locale Environment Common Files) SUNWxcu4 (XCU4 Utilities) SUNWmfrun (Motif RunTime Kit) SUNWxwice (ICE package)

To check the OS version, use the following command: uname -a To check the patch level, use the following command: showrev -p | egrep "108528|108827|1 08434"

Chapter 2

Preparing to install BMC Reporting Foundation

31

Requirements for the Reporting Server computer

Table 4
Resource

Software Required for the Reporting Server on Solaris (part 2 of 3)


Requirement
I

Comments

Solaris version 9 minimum install and the following packages and patch clusters:
I I I I I I I I I I I I I I I I I I I I I

SUNWscpu (Source compatibility) SUNWxwfnt (W Window System required fonts) SUNWxwplt (X Window System platform software) SUNWgzip (The GNU Zip (gzip) compression utility) SUNWzlib (The Zip compression library) SUNWbash (GNU Bourne-Again shell (bash)) SUNWbcp (SunOS 4.x Binary Compatibility) SUNWxcu4 (XCU4 Utilities) SUNWlibC (Sun Workshop Compilers Bundled libC) SUNWeu8os (American English/UTF-8 L10N For OS Environment User Files) SUNWeuluf (UTF-8 L10N For Language Environment User Files) SUNWuiu8 (Iconv modules for UTF-8 Locale) SUNWulcf (UTF-8 Locale Environment Common Files) SUNWmfrun (Motif RunTime Kit) SUNWxwice (X Window System Inter-Client Exchange (ICE) Components) 112233-11 (kernel patch) 112874-16 (libc) 111711-06 (C++ run-time) 112963-17 (linker patch) 115754-02 (zlib patch) SUNWgzip, SUNWzlib, SUNWscpu

Solaris version 10 minimum install and the following packages:


I I I I I I I I I I I

SUNWgzip (The GNU Zip compression utility), SUNWzlib (The Zip compression library) SUNWscpu (Source compatibility), SUNWbash (GNU Bourne-Again shell (bash)) SUNWbcp (SunOS 4.x Binary Compatibility), SUNWxcu4 (XCU4 Utilities) SUNWxwfnt (W Window System required fonts),SUNWxwplt (X Window System platform software) SUNWlibC (Sun Workshop Compilers Bundled libC), SUNWeu8os (American English/UTF-8 L10N For OS Environment User Files) SUNWeuluf (UTF-8 L10N For Language Environment User Files) SUNWuiu8 (Iconv modules for UTF-8 Locale) SUNWulcf (UTF-8 Locale Environment Common Files) SUNWmfrun (Motif RunTime Kit) SUNWxwice (X Window System Inter-Client Exchange (ICE) Components)

32

BMC Reporting Foundation Installation Guide

Requirements for the Report Viewer computer

Table 4
Resource Document viewer

Software Required for the Reporting Server on Solaris (part 3 of 3)


Requirement
I

Comments Business Objects documentation is installed with the reporting server. The Client Tools are required to use BMC Reporting Foundation and must be installed on a Windows computer.

Adobe Acrobat v 5.0 or later

other

Business Objects Client Tools

Requirements for the Report Viewer computer


Windows or Solaris
Table 5 contains software requirements for the computer used to view reports. Table 5
Resource JVM browser

Software requirements for Report Viewer computer


Requirement
I

Java 1.4.2.08 or later

One of the following:


I I I

Internet Explorer 7.0 Internet Explorer 6.0 Service Pack 1/ Service Pack 2 Mozilla Firefox 2.0

Requirements for the Client Tools computer


Table 6 contains hardware and software requirements for installing required components for the Client Tools on Windows computers.

Chapter 2

Preparing to install BMC Reporting Foundation

33

Requirements for the Foundation Database host computer

Table 6
Resource CPU operating systems

Requirements for Client Tools computer


Requirements
I

Comments

Intel x86

One of the following:


I I I I I

Windows 2000 Server, Service Pack 2 Windows 2000 Advanced Server, Service Pack 2 Windows 2000 Professional, Service Pack 2 Windows 2003 Server Windows 2003 Enterprise Server Recommended

browser

One of the following:


I I I

Internet Explorer 7.0 Internet Explorer 6.0 Service Pack 1/ Service Pack 2 Mozilla Firefox 2.0

disk space used 600 MB after installation RAM 2 GB or higher Required for the Oracle client if Client Tools is on a different computer from the Foundation Database and Oracle. Business Objects documentation is installed with the Client Tools.

Document viewer

Adobe Acrobat v 5.0 or later

Requirements for the Foundation Database host computer


Windows
Table 7 and Table 8 contain hardware and software requirements for installing required components for a Foundation Database host on Windows computers. Table 7
Resource RAM disk space required for installation

Hardware required for BMC Reporting Foundation Database host computer


Requirement 4 GB 15 GB including installation of Oracle Comments

34

BMC Reporting Foundation Installation Guide

Requirements for the Foundation Database host computer

Table 8
Resource operating systems

Software required for BMC Reporting Foundation Database host computer on Windows
Requirement One of the following:
I I I

Comments

Windows 2000 Server, Service Pack 2 Windows 2000 Advanced Server, Service Pack 2 Windows 2003 Server, Service Pack 1 Recommended

browser

One of the following:


I I I

Internet Explorer 7.0, Internet Explorer 6.0 Service Pack 1, Service Pack 2 Mozilla Firefox 2.0 Oracle documentation is installed with the Oracle server.

Document viewer

Adobe Acrobat v 5.0 or later

Solaris
Table 9 and Table 10 contain the requirements for installing required components for the Foundation Database host on Solaris computers. Table 9
Resource CPU

Requirements for BMC Reporting Foundation Database host computer on Solaris


Requirement One of the following:
I I

Comments

SPARC 32 bit SPARC 64 bit

RAM Swap Space disk space required for installation

4 GB 0.75 times of RAM or higher 15 GB including installation of Oracle

Chapter 2

Preparing to install BMC Reporting Foundation

35

Requirements for the Foundation Database host computer

Table 10
Resource operating systems

Software and Settings Required for BMC Reporting Foundation Database host computer on Solaris
Requirement One of the following:
I I I

Comments

Sun Solaris 8 Sun Solaris 9 Sun Solaris 10 Internet Explorer 7.0 Internet Explorer 6.0 Service Pack 1/ Service Pack 2 Mozilla Firefox 2.0 shmsys:shminfo_shmmax=4294967295 shmsys:shminfo_shmmin=1 shmsys:shminfo_shmmni=100 shmsys:shminfo_shmseg=100 semsys:seminfo_semmni=100 semsys:seminfo_semmsl=2050 semsys:seminfo_semmns=4050 semsys:seminfo_semopm=100 semsys:seminfo_semvmx=32767 semsys:seminfo_semume=30 Recommended

browser

I I I

Semaphore and shared memory settings

I I I I I I I I I I

The installation program checks for specific memory requirements for the Oracle database before it creates the database. If the program finds that the memory parameters do not satisfy the database requirements, the installation terminates. Before restarting the installation program, assign the minimum settings by editing /etc/system so that the values reflect the settings in the requirement column, and reboot the computer. Note that these are minimum requirements. Your system may require different values for optimal performance.

packages and programs

I I I I I I

SUNWarc SUNWhea SUNWlibm SUNWbtool SUNWlibms SUNWsprot Oracle Install user group

The programs make, nm, ld, and ar must be available. (They come with the packages mentioned here.)

User group

This must be a local group. Create it before beginning any install that includes the Foundation Database. This must be the primary group for the user that runs the installation program. Oracle and the root user should have the same group ID.

ports

The following port must be available, if the default options are selected:
I

1521

36

BMC Reporting Foundation Installation Guide

Installation Overview

Installation Overview
In general, you will follow a three-stage process.
I

Install BMC DataStore. Determine whether specific instructions exist with regard to the installation of BMC Reporting Foundation, and follow those specific instructions. Install BMC Performance Manager Reporting.

You have many choices to help you accomplish the installation of BMC Reporting Foundation. As described in Computer roles - what goes where on page 18, there are four computer roles that are needed for BMC Reporting Foundation to work. The major steps for installing BMC Reporting Foundation are listed below. Each step, along with some of its variations, is discussed in chapters 3 and 4.
Task Review installation requirements Install BMC Foundation Database instance using the BMC DataStore installer Install the BMC Reporting Foundation components Install the Client Tools Install and configure your reporting solution Refer to page 27 page 40 for a Windows computer, or page 55 for a Solaris computer page 42 for a Windows computer or page 57 for a Solaris computer page 46 for a Client tools only installation see BMC Performance Manager Getting Started.

Chapter 2

Preparing to install BMC Reporting Foundation

37

Installation Overview

38

BMC Reporting Foundation Installation Guide

Chapter

3
39 40 40 42 43 46 47 47 48

Installing BMC Reporting Foundation on Windows computers


3

This chapter provides the information that you need to install BMC Reporting Foundation on Windows computers. This chapter presents the following topics: Installing BMC Reporting Foundation on Windows computers overview . . . . . . . . Verifying installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the BMC Reporting Foundation Database . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing BMC Reporting Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing all BMC Reporting Foundation components on one computer . . . . . . Installing Client Tools only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About web servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling BMC Reporting Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling BMC Reporting Foundation on Windows . . . . . . . . . . . . . . . . . . . . .

Installing BMC Reporting Foundation on Windows computers overview


BMC Reporting Foundation consists of three sets of components:
I

Reporting server components, including the report server and report portal. The report server components can be installed on either a Windows or a Solaris computer. BMC Reporting Foundation Database components. The BMC Reporting Foundation Database components include the BMC Reporting Foundation Database and Oracle 10g. They can be installed on either a Windows or a Solaris computer.

Chapter 3

Installing BMC Reporting Foundation on Windows computers

39

Verifying installation requirements

The Client Tools components must be installed on a Windows computer.

These components can be installed on the same computer, or they can be installed on different computers. All three components must be installed on a network where they can communicate with each other.

Verifying installation requirements


Before you install BMC Reporting Foundation, verify that the target computers meet the installation requirements listed in Installation requirements on page 27 and the installation requirements listed in the BMC DataStore Installation Guide.

NOTE
Review the instructions in the user documentation for the reporting solution set before installing BMC Reporting Foundation.

Installing the BMC Reporting Foundation Database


The BMC Reporting Foundation Database is the Oracle database that stores
information about the BusinessObjects Enterprise system and its users.

Complete the following procedures to install BMC Reporting Foundation Database, including the Oracle software, on one computer.

Before you begin


I

If you plan on installing the BMC Reporting Foundation Database on a different system than the Reporting Server, then you must also install the Oracle client software on the Reporting Server computer. See Requirements for the Reporting Server computer on page 28. You must have administrator rights and permissions on the target computer and be a member of its Administrators group. The target computer must have a static IP address. The name of the installation directory should not contain spaces.

40

BMC Reporting Foundation Installation Guide

Installing the BMC Reporting Foundation Database

The DataStore cannot be installed on a shared drive on a remote Windows computer. It must be installed on a local drive. You will need the BMC DataStore 2.5.10 CD to install the DataStore.

To install the BMC Reporting Foundation Database from the CD


To install the BMC Reporting Foundation Database component (BMC Datastore 2.5.10), perform the following steps

1 From the BMC DataStore 2.5.10 CD, start the installation utility by running
setupWin32.exe at the root.

2 On the welcome screen, click Next. 3 On the license agreement page, review the license, select I accept to the terms of the
License Agreement, and click Next.

4 On the instance selection page, you are prompted to select the instance you want to
install and click Next.
Option Install Reporting Aggregate Database Instance Description Creates the BMC Performance Manager Reporting database instance. The default instance name is BMCREPT (If BMC Portal is not installed on the same computer, BMC recommends creating the instance name as BMCPDS). Select this option. Install Reporting Business Objects Database Instance Creates the BMC Reporting Foundation database instance, BMCREPO. This is the Oracle database that stores information about the BusinessObjects Enterprise system and its users. Select this option.

5 On the Reporting Aggregate Database Instance Information page, type the host
name in the Fully qualified Database Host Name box.

6 Use default values for the Database Instance options and click Next. 7 Select the appropriate size of the Reporting Aggregate Database Instance and click
Next.

8 On the Reporting Business Objects Database Instance Information page, type the
host name in the Fully qualified Database Host Name box.

Chapter 3

Installing BMC Reporting Foundation on Windows computers

41

Installing BMC Reporting Foundation

9 Use default values for the Database Instance options and click Next. 10 Specify the top installation directory for the database instance, and click Next.
Accept the default location for the top-level directory. In the text box, type the preferred top-level installation directory. Click Browse to select a location.

11 Review the options you have selected on the installation summary page and then
click Next. The installation process begins.

NOTE
Do not specify a path that contains spaces. The installation program creates the following subdirectories under the specified directory:
I I I

_jvm _uninst datastore

12 Restart the system after installing the database instance and Oracle server.

Installing BMC Reporting Foundation


Use Table 11 to find the procedure for the type of installation you want to perform. Table 11
Procedure Installing all BMC Reporting Foundation components on one computer Installing Client Tools only

BMC Reporting Foundation Installation Procedures for Windows


Page 43 46

42

BMC Reporting Foundation Installation Guide

Installing all BMC Reporting Foundation components on one computer

Installing all BMC Reporting Foundation components on one computer


Use the following procedure to install all the BMC Reporting Foundation components on one computer.

Before you begin


I

Ensure that you have the BMC Reporting Foundation 3.0 Windows DVD. The computer must meet the system requirements. See Installation requirements on page 27 for more information. The account that will run BMC Reporting Foundation as a service must already exist. The account must be a member of the Administrators group. You must be logged on as a member of the account that will run BMC Reporting Foundation as a service. The ORACLE_HOME variable must be defined. For example, ORACLE_HOME=install_directory/Datastore/ora10g/db_1 You can not install BMC Reporting Foundation on a domain controller or on a computer where the Windows default security settings given to the local Administrators group have been modified. If you prefer to use IIS as the web server for the Reporting server, IIS must already be installed before you install BMC Reporting Foundation. If you prefer to use Apache, there is no prerequisite action because Apache is installed at the same time as BMC Reporting Foundation. See About web servers on page 47 for more information. Do not specify a path that contains spaces.

To install BMC Reporting Foundation 1 Insert the BMC Reporting Foundation 3.0 Windows DVD into the DVD drive and
run setup.exe at the root.

2 Select the Setup Language. 3 Click OK. 4 On the welcome page, click Next to continue.
Chapter 3 Installing BMC Reporting Foundation on Windows computers 43

Installing all BMC Reporting Foundation components on one computer

5 On the license agreement page, revie the license agreement. Choose the I accept to
the terms of the License Agreement option and click Next.

6 On the installation choice page, select Perform Server Installation, and click Next. 7 On the User Information page, type your Name and Organization details. 8 Type C620W-2SXYK2G-ZC08Z0A-ZX5N in the Product Keycode box, and click Next. 9 On the Select Directory page, type the path or browse to the location where the
product will be installed, and click Next.

NOTE
The path you select for installation of BMC Reporting Foundation 3.0 may not include spaces or the % or $ characters.

10 On the Install Type page, select New, and select Use an existing database Server.
Type BMCREPO in the Server box, bmcbodba in the Username box and zohreh in the Password box.

11 Click Next to continue. 12 On the CMS Database Information page, select Oracle and click Next. 13 On the Choose Web Component Adapter Type page, select Java application server
or IIS ASP.NET, and click Next.

NOTE
If you want to use an IIS server, select the default web site for the IIS Server from the Choose website box. To use an IIS server, the IIS server must already be installed on your system.

If you have chosen to install Tomcat application server, the Configure Tomcat page is displayed.

14 On the Configure Tomcat page, verify the installation directory and ports for
Tomcat application server and click Next.

NOTE
BMC recommends that you use the default values for the Tomcat application server ports.

44

BMC Reporting Foundation Installation Guide

Installing all BMC Reporting Foundation components on one computer

15 On the Start Installation page, click Next.


At this point, the installation program checks the system requirements, based on the information you provided on the previous screens. If there is a problem, the program provides an error message and instructs you to go back and correct the issue before proceeding with the installation. The following components are installed:
I

Apache, Tomcat, and JDK (if needed). Business Objects is installed. On Solaris, the Business Objects files are extracted from their ZIP files. On Windows, the Business Objects install program is run, using the files in the install directory.

NOTE
If the installation fails, the install software rolls back the system to the pre-installed state, while displaying this activity in the progress window.

16 When installation has completed successfully, the Business Objects Registration


Wizard page is displayed. Click Next.

NOTE
If the Registration Wizard takes more than 30 minutes, please ignore the registration and log on to the Report Server by navigating to Start => All Programs => BusinessObjects XI Release 2 => BusinessObjects XI Enterprise => BusinessObjects Enterprise Java Administration Launchpad => Central Management Console

17 On the CMS Log On page, type Administrator in the User Name box and leave the
Password box empty. Click Log on >.

18 Click Finish to close the installation utility. NOTE


After the installation is complete, ensure that Reporting server is running. See Verifying whether the CMS is running on page 71.

Chapter 3

Installing BMC Reporting Foundation on Windows computers

45

Installing Client Tools only

Installing Client Tools only


Use the following procedure to install only the Client tool components on a computer. The BusinessObjects Client installation contains the following components:
I I I I I I

The Publishing Wizard The Import Wizard The Business View Manager Desktop Intelligence Report Conversion Tool Universe builder

Before you begin


I

The computer must meet the system requirements. See Installation requirements on page 27 for more information. You must be logged on as a member of the Administrators group. Do not specify a path that contains spaces.

To install the Client Tools components 1 Insert the BMC Reporting Foundation 3.0 Windows DVD into the DVD drive and
run setup.exe at the root.

2 Select the Setup Language. 3 Click OK. 4 On the welcome page, click Next to continue. 5 On the license agreement page, read the license agreement. If you agree, choose the
I accept the License Agreement option and click Next.

6 On the installation choice page, select Perform Client Installation, and click Next. 7 On the Select Directory page, type the path or browse to the location where the
product is to be installed, and click Next. The Start Installation page is displayed.

8 Click Next.

46

BMC Reporting Foundation Installation Guide

About web servers

At this point, the installation program checks the system requirements, based on the information you provided on the previous screens. If there is a problem, the program provides an error message and instructs you to go back and correct the issue before proceeding with the install.

9 When the installation has completed (successfully or not), the final summary
window is displayed. Click Finish to close the installation utility.

About web servers


The Reporting server relies on a third party web server as its web application infrastructure. The web server for a Windows installation can be either Apache or Microsoft Internet Information Services (IIS). You choose the web server you want to use during the installation process. If you prefer to use IIS as the web server for the Reporting server, IIS must already be installed before you install BMC Reporting Foundation. A standard configuration is acceptable. BMC Reporting Foundation adds the user, Administrator. If you have installed on a Microsoft Windows 2003 system and choose IIS, you must also have the ASP and ASP.NET components of IIS installed and enabled as well. If you prefer to use Apache, there is no prerequisite action because Apache is installed at the same time as BMC Reporting Foundation.

Uninstalling BMC Reporting Foundation


To uninstall BMC Reporting Foundation use Microsoft Windows uninstall utility, described in the following section.

Before you begin


I

Uninstall all reporting solution sets before you uninstall BMC Reporting Foundation. Stop all Business Objects processes and the web server. Stop all Oracle processes. If you want to save the reports and system information, make a copy of the root directories used by the Input and Output File Repository Servers and backup the CMS database.

Chapter 3

Installing BMC Reporting Foundation on Windows computers

47

Uninstalling BMC Reporting Foundation on Windows

Uninstalling BMC Reporting Foundation on Windows


Complete the following steps to uninstall BMC Reporting Foundation on Microsoft Windows.

To uninstall BMC Reporting Foundation 1 Use the Central Management Console (CMC) to select all of the BMC Reporting
Foundation servers, right-click the selected servers and select Stop.

2 Select the Start => Control Panel => Add or Remove Programs option. 3 On the Add or Remove programs window, select the Change or Remove
Programs button, and then select BusinessObjects Enterprise.

4 Click the Change/Remove button to launch the installation utility in uninstall


mode. The Welcome window is displayed. Click Next.

5 Select the product or products that you want to uninstall, and click Next. 6 Review your selections and click Next. 7 After the uninstallation is complete, a summary window is displayed that tells you
whether the uninstallation was successful. Click Finish to exit the program.

8 Delete the install_directory manually. To uninstall BMC Reporting Foundation Database 1 Select the Start => Control Panel => Add or Remove Programs option. 2 On the Add or Remove programs window, select the Change or Remove
Programs button on the left pane of the window button, and then select Datastore.

3 Click the Change/Remove button to launch the installation utility in uninstall


mode. The Welcome window is displayed. Click Next.

4 Select the BMC Reporting Foundation Database instance, and optionally the
Datastore server components (if you also want to uninstall Oracle), and click Next.

48

BMC Reporting Foundation Installation Guide

Uninstalling BMC Reporting Foundation on Windows

5 Review the summary information selections to ensure that they reflect the
components that you want to remove. If they do not, click the Back button and amend your selections. Otherwise, click Next to proceed with the installation.

6 Review the information in the results window and click Next. 7 After the uninstallation is complete, a summary window is displayed that tells you
whether the uninstallation was successful. Click Finish to exit the program.

Chapter 3

Installing BMC Reporting Foundation on Windows computers

49

Uninstalling BMC Reporting Foundation on Windows

50

BMC Reporting Foundation Installation Guide

Chapter

4
51 52 52 53 55 57 59 60

Installing BMC Reporting Foundation on Solaris


4

This chapter provides the information that you need to install BMC Reporting Foundation on Solaris computers. This chapter presents the following topics: Installing BMC Reporting Foundation on UNIX computers overview . . . . . . . . . . . . Verifying installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using an xterm to Install BMC Reporting Foundation . . . . . . . . . . . . . . . . . . . . . . Mounting a CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing BMC Reporting Foundation Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing BMC Reporting Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling BMC Reporting Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling BMC Reporting Foundation on UNIX. . . . . . . . . . . . . . . . . . . . . . . . .

Installing BMC Reporting Foundation on UNIX computers overview


BMC Reporting Foundation consists of three sets of components:
I

Report server components, including the report server and report portal. The report server components can be installed on either a Windows or a Solaris computer. DataStore components. The BMC Reporting Foundation Database components include the DataStore and Oracle 10g. They can be installed on either a Windows or a Solaris computer. If the Client Tools components are installed on a different computer than the Foundation Database, you need an Oracle client to connect to the Foundation Database.

Chapter 4

Installing BMC Reporting Foundation on Solaris

51

Verifying installation requirements

In a Solaris environment, the Reporting server and the BMC Reporting Foundation Database can be installed on the same computer, or they can be installed on different computers. They must be in an environment where they can communicate with each other and with Client Tools. The Client Tools for BusinessObjects must be installed on a Windows computer. For information about installing Client tools, see Installing Client Tools only on page 46.

Verifying installation requirements


Before you install Reporting Foundation, verify that the target computer or computers meet the installation requirements listed in Installation requirements on page 27.

NOTE
Review the instructions in the user documentation for the reporting solution set before installing BMC Reporting Foundation.

Using an xterm to Install BMC Reporting Foundation


The installation requires a valid initialized X session. X-Windows must be installed on the system where the installer is run. Use any Sunsupported X-Windows server that supports Motif, such as dtwm, twm, and olwm. If you use an xterm to install Reporting Foundation, you must initialize the display using another X Windows application such as xclock prior to starting the install. The locale must be set to en_US using LC_CTYPE. For csh, at the command prompt, type setenv LC_CTYPE en_US For ksh or sh, at the command prompt, type LC_CTYPE=en_US export LC_CTYPE

52

BMC Reporting Foundation Installation Guide

Mounting a CD

Mounting a CD
The following sections provide information about the mount commands you must use to mount the PATROL product CDs on your UNIX system.

Mounting the CD drive


NOTE
In this procedure, the root directory for the CD drive is called /cdrom. This directory might be different for your computer, depending on how your system administrator has configured the device. If you have a question about the location or setup of your CD drive, please contact your system administrator.

1 Log on as root, or su to root. 2 Insert the CD into the CD drive. 3 Use the mount command appropriate to your platform to mount the CD.
Platform Solaris Mount Command Volume Manager (/usr/sbin/vold) automatically mounts. Otherwise, mount -r -F hsfs /dev/sr0 /cdrom

If a problem occurs, consult your system administrator or read the man page for mount.

4 Log off.

Chapter 4

Installing BMC Reporting Foundation on Solaris

53

Mounting a CD

Mounting the CD drive for an NFS client


Before you can mount the CD on an Network File System (NFS) device, you must export the CD file system so that it can be mounted by NFS clients. Most platforms use the exportfs command to export a local file system, including a CD file system. However, Solaris platforms use the share command. To mount the CD on an NFS client, follow these steps:

1 Log on as root. 2 Create a directory on your local computer (for example, /mnt/cdrom or
/mnt/cdrom/cdrom0 for Solaris) as the mount point for the CD on the remote host

computer.

3 Use the mount command appropriate to your platform to mount the CD.
Platform Solaris Mount Command mount host:/cdrom/cdrom0 /mnt/cdrom/cdrom0

If a problem occurs, consult your system administrator or read the man page for mount.

4 Log off.

54

BMC Reporting Foundation Installation Guide

Installing BMC Reporting Foundation Database

Installing BMC Reporting Foundation Database


The BMC Reporting Foundation database is the Oracle database used by the Central Management Server. Complete the following procedures to install BMC Reporting Foundation Database, including the Oracle database, on one computer.

Before you begin


I

Review the installation requirements listed in the BMC DataStore Installation Guide. Before starting the installation program, create an oracle user on the target Solaris computer, and assign it to the oracle group. The oracle user account requires the same level of permission as the root account. The oracle user account must execute /etc/profile during logon. The installation program creates the bmc.profile and adds . /etc/bmc.profile to the /etc/profile script. If the logon does not execute these scripts, the product will fail to install properly. Enable the oracle user so that it can run in a non-interactive mode. The product routinely logs on the account and cannot function properly if a user response is required at logon.

If you plan on installing DataStore on a different system than the Reporting Server, then you must also install the Oracle client software on the Reporting Server computer. See Requirements for the Reporting Server computer on page 28.

To Install the BMC Reporting Foundation Database from the DataStore CD


You will need the BMC DataStore 2.5.10 CD to install the BMC Reporting Foundation Database.

To install the BMC Reporting Foundation Database component 1 Log on as root to run the installation program, or log on with any user account that
has the permissions of the root account.

2 Change to a different directory (such as /tmp); then start the installation program,
using the fully qualified path (for example, /cdrom/cdrom0/install.bin).

3 On the welcome screen, click Next.

Chapter 4

Installing BMC Reporting Foundation on Solaris

55

Installing BMC Reporting Foundation Database

4 On the license agreement page, review the license, select I accept to the terms of the
License Agreement, and click Next.

5 On the instance selection page, you are prompted to select the instance you want to
install and click Next.
Option Install Reporting Aggregate Database Instance Description Creates BMCPDS, BMC Performance Manager Reporting database instance. Select this option. Install Reporting Business Objects Database Instance Creates BMCREPO, BMC Reporting Foundation database instance. This is the Oracle database that stores reports and universes for the reporting solution sets as well as administrative and security information for the report users. Select this option.

6 On the Reporting Aggregate Database Instance Information page, type the host
name in the Fully qualified Database Host Name box.

7 Use default values for the Database Instance options and click Next. 8 Select the appropriate size of the Reporting Aggregate Database Instance and click
Next.

9 On the Reporting Business Objects Database Instance Information page, type the
host name in the Fully qualified Database Host Name box.

10 Use default values for the Database Instance options and click Next. 11 Specify the top installation directory for the database instance, and click Next.
Accept the default location for the top-level directory. In the text box, type the preferred top-level installation directory. Click Browse to select a location.

NOTE
Do not specify a path that contains spaces. The installation program creates the following subdirectories under the specified directory: _jvm _uninst datastore

12 Review the options you have selected on the installation summary page and then
click Next. The installation process begins.

56

BMC Reporting Foundation Installation Guide

Installing BMC Reporting Foundation

After completing the installation, log off and then log on again. This process ensures that the Oracle path and SID is set properly.

Installing BMC Reporting Foundation


Use the following procedure to install the Reporting Server (BusinessObjects Enterprise XI Release 2) on a Solaris computer.

Before you begin


I

Ensure that you have the BMC Reporting Foundation 3.0 - Solaris DVD. The computer must meet the system requirements. See Installation requirements on page 27 for more information. The account that will run BMC Reporting Foundation as a process must already exist. Before installing BMC Reporting Foundation, verify that the following variables are set appropriately:
I I I

ORACLE_HOME= Oracle_install_directory/Datastore/ora10g/db_1 LC_ALL=en_US.UTF-8 LD_LIBRARY_PATH=ORACLE_HOME/lib32

WARNING
IF the LD_LIBRARY_PATH is not set, BMC Reporting Foundation does not create tables in the BMCREPO database instance.

Ensure that the BMC Reporting Foundation Database and the Oracle server have been installed on the Foundation Database host. See Installing BMC Reporting Foundation Database on page 55. You must install the BusinessObjects Client Tools on a Windows computer. For more information on installing client tools, see Installing Client Tools only on page 46. Do not specify a path that contains spaces.

Chapter 4

Installing BMC Reporting Foundation on Solaris

57

Installing BMC Reporting Foundation

To Install BMC Reporting Foundation Server Components 1 Insert the BMC Reporting Foundation 3.0 Solaris DVD into the DVD drive and
mount it. See Mounting the CD drive on page 53 or Mounting the CD drive for an NFS client on page 54 for more information.

2 Log on as a user account. 3 Change to a different directory (such as /tmp); then start the installation program,
using the fully qualified path (for example, /cdrom/cdrom0/install.sh).

4 The script prompts you to select whether to perform a system installation or a user
installation. Use the arrow keys to select system installation and press Enter.

5 The script prompts you for the product keycode. Type C620W-2SXYK2G-ZC08Z0AZX5N and press Enter.

6 The script prompts you to select the installation type. Use the arrow keys to select
New (Install a new Enterprise System) and press Enter.

7 The script prompts for using an existing CMS database or installing MySQL as the
default CMS repository for Business Objects. Use the arrow keys to select Use an
existing database and press Enter.

8 The script prompts for the type of the CMS database. Use the arrow keys to select
Oracle and press Enter.

9 The script prompts for information pertaining to the CMS database. Provide the
Oracle TNSName as BMCREPO, User ID as bmcbodba, password as zohreh, and the local name server and press Enter.

10 The script prompts you to re-initialize the BusinessObjects Enterprise database.


Use the arrow keys to select Yes and press Enter.

11 The script prompts for using an existing Java application server or installing
Tomcat. Use the arrow keys to select Tomcat and press Enter.

12 The script prompts for the port numbers for the Tomcat server. Use the default
values and press Enter.

58

BMC Reporting Foundation Installation Guide

Uninstalling BMC Reporting Foundation

13 The script displays the installation confirmation window.


At this point, the installation script checks the system requirements, based on the information you provided on the previous screens. If there is a problem, the program provides an error message and instructs you to go back and correct the issue before proceeding with the install. The following components are installed:
I

Apache, Tomcat, and JDK (if needed). Business Objects.

NOTE
If the installation fails, the install software rolls back the system to the pre-installed state, while displaying this activity in the progress window.

14 To verify that the CMS Server is running, enter the following command:
ps -aef|grep boe

Uninstalling BMC Reporting Foundation


To uninstall BMC Reporting Foundation you must use the same version of the installation utility that you used to install the product. Run the installation utility in uninstall mode to uninstall BMC Reporting Foundation from your system.

WARNING
If you use a different version of the installation program to uninstall, you might remove files needed to perform uninstallation of other BMC Software products.

Before you begin


I

Uninstall all reporting solution sets before you uninstall BMC Reporting Foundation. Stop all Business Objects processes. Stop all Oracle processes.

Chapter 4

Installing BMC Reporting Foundation on Solaris

59

Uninstalling BMC Reporting Foundation on UNIX

Uninstalling BMC Reporting Foundation on UNIX


To uninstall BMC Reporting Foundation on UNIX, run the uninstallBOBJE.sh script located in install_directory/bobje directory. This script stops all BusinessObjects Enterprise servers and processes, and deletes the files copied from the product CD during installation.

NOTE
The installation program creates a number of additional files on your computer. The uninstallBOBJE.sh script does not remove the files created during the installation process, or files created by the system or by users after installation. To remove all BusinessObjects Enterprise files, perform an rm -rf command on the bobje directory.

60

BMC Reporting Foundation Installation Guide

Chapter

5
61 61 62 64 65 66 67

Using the report portal


This chapter presents the following topics: Report portal overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the report server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying the report server is started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping the report server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the report portal (InfoView) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set the time out for the input and output file repository servers . . . . . . . . . . . . . . . . . Set the Connection time out for the Web_IntelligenceReportServer service server. .

Report portal overview


All reports are presented through the Business Objects report portal (InfoView). You can use any browser with access to the report server to display the portal and view reports.

Starting the report server


Before you begin
BMC Reporting Foundation must be installed on the computer.

To start the BMC Reporting Foundation servers on Windows 1 Navigate to Control Panel => Administrative Tools => Services. 2 Start the Apache Tomcat 5.0.27 service.

Chapter 5

Using the report portal

61

Verifying the report server is started

3 Navigate to Start => Programs => BusinessObjects XI Release 2 => BusinessObjects XI


Enterprise => Central Configuration Manager.

4 Select all the listed services. 5 Click Start on the menu to start all the services. To start the BMC Reporting Foundation servers on Solaris 1 Navigate to the install_directory/bobje directory. 2 Enter the following commands:
LC_CTYPE=en_US export LC_CTYPE ORACLE_HOME= Oracle_install_directory/Datastore/ora10g/db_1 export ORACLE_HOME LC_ALL=en_US.UTF-8 (If UTF-8 is not supported, please use en_US) export LC_ALL LD_LIBRARY_PATH=$ORACLE_HOME/lib32 export LD_LIBRARY_PATH $bobje/tomcatstartup.sh $bobje/startservers $bobje/ccm.sh start cms (Ignore message server of this name already exist).

3 Check if all BusinessObjects processes are enabled.


ps -aef|grep boe|grep -v "grep boe". There should be around 20 BusinessObjects processes running.

Verifying the report server is started


To verify that the BMC Reporting Foundation servers are started on Windows 1 On the computer where the server is installed, select Start=>Settings=>Control
Panel.

2 In the Control Panel, select Administrative Tools. 3 In the Administrative Tools panel, select Services.

62

BMC Reporting Foundation Installation Guide

Verifying the report server is started

4 Verify that these services are started.


I I I I I I I I I I I

I I I I I I

Central Management Server Connection Server Crystal Reports Cache Server Crystal Reports Job Server Crystal Reports Page Server Desktop Intelligence Cache Server Desktop Intelligence Report Server Destination Job Server Event Server Input File Repository Server Apache Tomcat web server or World Wide Web Publishing Service (IIS) List of Values Job Server Output File Repository Server Program Job Server Report Application Server Web Intelligence Job Server Web Intelligence Report Server

To verify that the BMC Reporting Foundation servers are started on Solaris 1 On the computer where the server is installed, at the command prompt, type the
following command $ ps -aef|grep boe

Chapter 5

Using the report portal

63

Stopping the report server

The computer should show the following processes:


I I I I I I I I I I I I I I I I I I I I

oe_filesd -name hostname boe_jobsd -lib procreport boe_crystalras -name hostname boe_crystalrasd boe_jobsd -lib proclov -jsT boe_pagesd -name hostname boe_crystalrasd.bin -na boe_jobsd -lib pp_procFC -j boe_pagesd.bin -name hostname boe_fccached -name hostname boe_eventsd -name hostname boe_jobsd -lib procdest -js boe_jobsd -lib procprogram boe_cachesd -name hostname boe_jobsd -lib procwebi -js boe_filesd -name hostname boe_pagesd.bin -name hostname boe -name hostname boe_fcprocd -name hostname boe_fcprocd -name hostname

Stopping the report server


Use the following procedures to stop the BMC Reporting Foundation servers.

To stop the BMC Reporting Foundation servers on Solaris 1 Navigate to the install_directory/bobje directory. 2 Enter the following commands:
LC_CTYPE=en_US export LC_CTYPE ORACLE_HOME= Oracle_install_directory/Datastore/ora10g/db_1 export ORACLE_HOME LC_ALL=en_US.UTF-8 (If UTF-8 is not supported, please use en_US) export LC_ALL LD_LIBRARY_PATH=$ORACLE_HOME/lib32 export LD_LIBRARY_PATH

64

BMC Reporting Foundation Installation Guide

Starting the report portal (InfoView)

bobje/ stopservers $bobje/ tomcatshutdown.sh $bobje/ccm.sh stop cms

3 Check if all BusinessObjects processes are stopped.


ps -aef|grep boe|grep -v "grep boe". There should be no BusinessObjects processes running.

To stop the BMC Reporting Foundation servers on Windows 1 Navigate to Start => Programs => BusinessObjects XI Release 2 => BusinessObjects XI
Enterprise => Central Configuration Manager.

2 Select all the listed services. 3 Click Stop on the menu to stop all the services. 4 Navigate to Control Panel => Administrative Tools => Services. 5 Stop the Apache Tomcat 5.0.27 service.

Starting the report portal (InfoView)


Before you begin
I

BMC Reporting Foundation must be installed and the report server must be running. You must know the name and password of at least one user who has with permission to use InfoView. Typically, one or more users are defined during the installation of a reporting solution set.

To start the report portal 1 Open a web browser. 2 If the report server is using Apache as the web server, type the following in the
Address box, where hostname is the name of the server where Business Objects is installed. The default port number is 8080.

You can access the Report Portal from

Chapter 5

Using the report portal

65

Set the time out for the input and output file repository servers

http://hostname:8080/businessobjects/enterprise115/desktoplaunch/InfoView/ logon/logon.object

3 On the Welcome to InfoView page, click Login and type the name and password of
a user with permission to use InfoView. The BMC Reporting home page is displayed.

Set the time out for the input and output file repository servers
1 Log on to the Central Management Console as Administrator, leave the password
blank and specify the hostname: port number for the BMC Reporting Foundation server.

2 Click Servers on the Organize menu. 3 Click Input.hostname service on the Home => Servers page. 4 Type 7200 in the Maximum Idle Time box. 5 Click Apply.
A confirmation message is displayed.

6 Click OK. 7 Type the operating system Administrator user name (used for installing BMC
Reporting Foundation 3.0) in the Domain Name\Logon Name box and the corresponding password in the Password box.

8 Click OK. 9 Repeat Step 4 through Step 7 for the Output.hostname service.

66

BMC Reporting Foundation Installation Guide

Set the Connection time out for the Web_IntelligenceReportServer service server

Set the Connection time out for the Web_IntelligenceReportServer service server
1 Log on to the Central Management Console as Administrator, leave the password
blank, and specify the hostname: port number for the BMC Reporting Foundation server.

2 Click Servers on the Organize menu. 3 Click Web_IntelligenceReportServer service on the Home => Servers page. 4 Type 300 in Connection Time Out (minutes) box. 5 Click Apply.
A confirmation message is displayed.

6 Click OK. 7 Type the operating system Administrator user name (used for installing
BMCReporting Foundation 3.0) in the Domain Name\Logon Name box and the corresponding password in the Password box.

8 Click OK.

Chapter 5

Using the report portal

67

Set the Connection time out for the Web_IntelligenceReportServer service server

68

BMC Reporting Foundation Installation Guide

Chapter

BMC Reporting Foundation Database administration


6

This chapter presents the following topics: BMC Reporting Foundation Database administration overview . . . . . . . . . . . . . . . . . 69 Starting and stopping the BMC Reporting Foundation Database . . . . . . . . . . . . . 69 Changing the BMCREPO password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

BMC Reporting Foundation Database administration overview


BMC Software provides products that you can use for monitoring and managing the BMC Reporting Foundation Database, or you can use scripts for these activities that are included with Reporting Foundation.

Starting and stopping the BMC Reporting Foundation Database


The database administration scripts are installed at the same time as the BMC Reporting Foundation Database components. They can be used for the BMC Reporting Foundation Database (Oracle SID BMCREPO). For Windows, the installation program places the scripts in the %ORACLE_HOME%\utilities directory. The scripts can be run by any user who is a member of the Administrators group. For Solaris, the installation program places the scripts in the $ORACLE_HOME/utilities directory.
Chapter 6 BMC Reporting Foundation Database administration 69

Changing the BMCREPO password

For starting and stopping the databases, use the DatastoreMaintainanceTool.bat script on Windows and DatastoreMaintainanceTool.sh script on UNIX.

Changing the BMCREPO password


The BMCREPO user is used in more than one component of BMC Reporting Foundation and the reporting solution sets. It serves several important roles behind the scenes. The password must remain in sync for each of its roles. BMC Software recommends that you do not change the password for any of these users. However, if your sites security procedures require that the passwords be changed, follow these procedures.

NOTE
Before using the procedures in this guide, review the user documentation for your reporting solution set. If the instructions there are different, they supersede these procedures.

70

BMC Reporting Foundation Installation Guide

Appendix

A
71 72 72 73 73 74 75 77

Frequently Asked Questions


This appendix describes frequently asked questions about BMC Reporting Foundation.In addition, the processes and services related to BMC Reporting Foundation are listed. Verifying whether the CMS is running. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing Infoview and Central Management Console. . . . . . . . . . . . . . . . . . . . . . . . . Enabling drilling mode and creating new reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the BusinessObjects Enterprise servers manually . . . . . . . . . . . . . . . . . . . . . . Changing passwords using the Central Management Console . . . . . . . . . . . . . . . . . . Enabling audit actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting and stopping the BMC Reporting Foundation servers . . . . . . . . . . . . . . . . . . Processes and services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Verifying whether the CMS is running


Type the following command to verify whether the CMS is running on a Solaris computer:
ps -aef|grep boe

On Windows, verify that the CMS services are running from the Central Configuration Manager Tool. For a list of CMS services, see Processes and services on page A-77.

Appendix A

Frequently Asked Questions

71

Accessing Infoview and Central Management Console

Accessing Infoview and Central Management Console


You can access Infoview from: http://hostname:8080/businessobjects/enterprise115/desktoplaunch/InfoView/lo gon/logon.object You can access the Central Management Console from: http://hostname:8080/businessobjects/enterprise115/admin/en/admin.cwr

Enabling drilling mode and creating new reports


You can grant the right for enabling drilling and creating new reports for BusinessObjects users from the Central Management Server.

To enable drilling and creating new reports 1 Log on to the Central Management Console as administrator, leave the password
blank, and specify the hostname: port number for the BMC Reporting Foundation server.

2 Navigate to Home > BusinessObjects Enterprise Applications > Web Intelligence. 3 Select the advanced mode for all the rights displayed for the Everyone group. 4 Grant the right to Enable Drill Mode and Create document. 5 Click Apply.

72

BMC Reporting Foundation Installation Guide

Starting the BusinessObjects Enterprise servers manually

Starting the BusinessObjects Enterprise servers manually


The ccm.sh script provides you with a command-line interface to the various BusinessObjects Enterprise server components. In BusinessObjects Enterprise XI, the install setup program starts and enables servers automatically.

To manually start and enable the servers 1 Navigate to the bobje directory that was created by the installation. 2 Start all of the BusinessObjects Enterprise servers as daemons:
./ccm.sh -start all

3 Enable all of the BusinessObjects Enterprise servers. A If you are using the default ports for the CMS, use the following command to
start:
./ccm.sh -enable all

B If you are using a different port number for the CMS, type the following
command:
./ccm.sh -enable all -cms servername: portnumber

The daemons are now listening on the appropriate ports.

Changing passwords using the Central Management Console


This section lists the steps to be followed for changing the password of a BusinessObjects Enterprise user.

To change the password 1 Log on to the Central Management Console as Administrator, type the password
(default is an empty password), and specify the hostname: port number for the BMC Reporting Foundation server.

2 Select users from the Organize menu.


Appendix A Frequently Asked Questions 73

Enabling audit actions

A list of all BusinessObjects users is displayed.

3 Select the account name for which you want to change the password. 4 Type the new password in the Password box and type the password again in the
Confirm box.

5 Click Update.

Enabling audit actions


You can enable the Central Management Server to act as a system auditor.

NOTE
Add C8200-7B3SJ28-ZC0705S-8CP3 as the auditing license key from the License Keys page of the Central Management Console. Enable the BusinessObjects servers after adding the auditing license key.

To enable audit actions 1 Log on to the Central Management Console. 1 Go to the organize Servers menu of the Central Management Console. 2 Select the server that controls the action that you want to audit. 3 Click the Auditing tab. 4 Select the Auditing is enabled check box. 5 Select the audit actions that you want to record. NOTE
Ensure that your audit log file is located on a hard drive that has sufficient space to store the log files.

6 Click Update.

74

BMC Reporting Foundation Installation Guide

Starting and stopping the BMC Reporting Foundation servers

To audit every failure of a scheduled report, a scheduled program, or a scheduled List of Values, enable auditing of "A job has failed to run" on the Job Server, and "Communication with a running instance is lost." on the Central Management Server. Auditing is enabled independently on each server. If you want to audit all actions of a given type, enable identical audit actions on every server that supports those actions. Otherwise your audit record will be incomplete. For example, if you want to track the total number of concurrent logons to your BusinessObjects Enterprise system, you must enable logging of concurrent logons on every Central Management Server in your system.

Starting and stopping the BMC Reporting Foundation servers


You can start and stop the CMS servers on Solaris computers by using the startservers and stopservers scripts. On Windows computers, you can start and stop the CMS servers by using the Central Configuration Manager Tool.

To start the CMS servers on Solaris 1 Navigate to the install_directory/bobje directory. 2 Enter the following commands:
LC_CTYPE=en_US export LC_CTYPE ORACLE_HOME= Oracle_install_directory/Datastore/ora10g/db_1 export ORACLE_HOME LC_ALL=en_US.UTF-8 (If UTF-8 is not supported, please use en_US) export LC_ALL LD_LIBRARY_PATH=$ORACLE_HOME/lib32 export LD_LIBRARY_PATH $bobje/tomcatstartup.sh $bobje/startservers $bobje/ccm.sh start cms (Ignore message server of this name already exist).

3 Check if all BusinessObjects processes are enabled.


ps -aef|grep boe|grep -v "grep boe". There should be around 20 BusinessObjects processes running.

Appendix A

Frequently Asked Questions

75

Starting and stopping the BMC Reporting Foundation servers

To stop the CMS servers on Solaris 1 Navigate to the install_directory/bobje directory. 2 Enter the following commands:
LC_CTYPE=en_US export LC_CTYPE ORACLE_HOME= Oracle_install_directory/Datastore/ora10g/db_1 export ORACLE_HOME LC_ALL=en_US.UTF-8 (If UTF-8 is not supported, please use en_US) export LC_ALL LD_LIBRARY_PATH=$ORACLE_HOME/lib32 export LD_LIBRARY_PATH bobje/ stopservers $bobje/ tomcatshutdown.sh $bobje/ccm.sh stop cms

3 Check if all BusinessObjects processes are stopped.


ps -aef|grep boe|grep -v "grep boe". There should be no BusinessObjects processes running.

To start the CMS servers on Windows 1 Navigate to Control Panel => Administrative Tools => Services. 2 Start the Apache Tomcat 5.0.27 service. 3 Navigate to Start=>Programs=>BusinessObjects XI Release 2=>BusinessObjects XI
Enterprise=>Central Configuration Manager.

4 Select all the listed services. 5 Click Start on the menu to start all the services. To stop the CMS servers on Windows 1 Navigate to Start=>Programs=>BusinessObjects XI Release 2=>BusinessObjects XI
Enterprise=>Central Configuration Manager.

2 Select all the listed services. 3 Click Stop on the menu to stop all the services. 4 Navigate to Control Panel => Administrative Tools => Services.

76

BMC Reporting Foundation Installation Guide

Processes and services

5 Stop the Apache Tomcat 5.0.27 service.

Processes and services


This section lists processes and services that are specific to BMC Reporting Foundation.

BMC Reporting Foundation services on Windows


I I I I I I I I I I I

I I I I I I

Central Management Server Connection Server Crystal Reports Cache Server Crystal Reports Job Server Crystal Reports Page Server Desktop Intelligence Cache Server Desktop Intelligence Report Server Destination Job Server Event Server Input File Repository Server Apache Tomcat web server or World Wide Web Publishing Service (IIS) List of Values Job Server Output File Repository Server Program Job Server Report Application Server Web Intelligence Job Server Web Intelligence Report Server

Appendix A

Frequently Asked Questions

77

Processes and services

BMC Reporting Foundation processes on Solaris


I I I I I I I I I I I I I I I I I I I I

oe_filesd -name hostname boe_jobsd -lib procreport boe_crystalras -name hostname boe_crystalrasd boe_jobsd -lib proclov -jsT boe_pagesd -name hostname boe_crystalrasd.bin -na boe_jobsd -lib pp_procFC -j boe_pagesd.bin -name hostname boe_fccached -name hostname boe_eventsd -name hostname boe_jobsd -lib procdest -js boe_jobsd -lib procprogram boe_cachesd -name hostname boe_jobsd -lib procwebi -js boe_filesd -name hostname boe_pagesd.bin -name hostname boe -name hostname boe_fcprocd -name hostname boe_fcprocd -name hostname

78

BMC Reporting Foundation Installation Guide

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Index
A
about using IIS as web server 47 administering the BMC Reporting Foundation database 69 DEP. See Data Execution Prevention Distribution Server restriction 27

B
BMC Datastore assigning memory settings for installation on Solaris 25 installing Microsoft Loopback Adapter 23 Solaris installation considerations 23 Windows installation considerations 20 BMC Reporting Foundation before you install 57 components 10 overview 9 BMC Reporting Foundation database administration overview 69 installation requirements 34 overview 11 requirements 26 BMC Software, contacting 2

E
exportfs command 54

F
Foundation database administration 69 description 18 installation requirements 34 Oracle requirements 26 Oracle user account requirement 55 overview 11

H
hardware and software requirements for installing Reporting Foundation 27

C
categories overview 14 CD, mounting 53 Central Management Server 12 overview 12 changing passwords 70 Client Tools description 18 compatibility with other products 27 computer roles, what gets installed 18 customer support 3

I
IIS web server requirements 47 Import Wizard 12 installable images 27 installation before you begin 57 introduction 18 overview of required tasks 37 requirements 27 system requirements 2736, 40, 52 verifying requirements 27, 40, 52 installation list of requirements 27 installation planning configuring Terminal Services 22 configuring Windows data execution prevention feature 21 directory requirement 25 installation prerequisites installing Windows loopback adapter for datastore 23

D
data collection tools 14 Data Execution Prevention (DEP), configuring for installation on Windows computers 21 databases overview 14

Index

79

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Solaris datastore installation 23 Windows datastore installation 20 installing components separately 46 Oracle remotely 26 installing BMC Reporting Foundation 37 installing on Solaris overview 51 xterm 52 installing on Windows overview 39 IP address installation requirement Solaris installation 24 Windows installation 20 starting 65 prerequisites for installing the datastore installing Windows loopback adapter 23 processes 77 product support 3 products uninstalling in Windows environments 48 Publishing Wizard 13 overview 13

R
report 15 report portal overview 11, 61 requirements 33 starting 65 report server description 18 overview 11 requirements 28 starting 61 stopping 64 verifying it is started 62 on Solaris 63 verifying startup 62 web server requirements 47 report templates 15 report viewer software requirements 33 reporting components 10 reporting portal description 18 overview 11 reporting solutions sets 10 required privileges for user accounts 19 requirements for IIS as the web server 47 for the Reporting Server computer 28 for Windows Computers 28, 34, 37 overview 27, 40, 52 privileges 53, 54 system 2736, 40, 52 root permissions on Solaris 23

L
loopback adapter, installing 23

M
memory requirements for the Oracle database 36 memory settings, assigning for datastore installation on Solaris 25 mounting a CD overview 53

N
NFS Mount a CD-ROM 54

O
Oracle remote installation 26 Oracle Install user group 36 Oracle prerequisites Solaris installations 26 Windows installations 20 Oracle requirement for reporting server 28 Oracle requirements for Foundation database 26 Oracle user account requirement for Foundation database install 55 oracle user, creating for datastore installation 24 overview of installation tasks 37

S
Semaphore and shared memory settings 36 services 77 setSolarisSettings.sh script, using to set memory parameters for Solaris installations 25 share command 54 software requirements for the report viewer 33 Solaris installation creating oracle user for datastore 24

P
passwords changing 70 portal, report overview 61

80

BMC Reporting Foundation Installation Guide

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
prerequisites for BMC Datastore 23 root permissions 23 static IP address requirement 24 solution reports introduction 15 starting the report server 61 stopping the report server 64 support, customer 3 system requirements 2736, 40, 52

T
technical support 3 templates, report 15 Terminal Services configuring for installation 22

U
UMASK on Solaris computers 24 uninstalling on Solaris 60 uninstalling on Windows 48 uninstalling products in Windows environments 48 universe described 14 user accounts requirements 19 user groups and users described 14

V
verifying the report server is started on Solaris 63 on Windows 62

W
Web servers important information 47 Windows installation configuring data execution prevention feature 21 configuring Terminal Services 22 installing loopback adapter for the datastore 23 prerequisites for BMC Datastore 20 static IP address requirement 20

Index

81

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

82

BMC Reporting Foundation Installation Guide

Third-Party Product Terms


The following terms apply to third-party products that are included with or in a BMC Software product as described in the BMC Software, Inc., License Agreement that is applicable to the product.

The Apache Software License, Version 1.1


This product includes the Apache software product found at www.apache.org and the Apache software product is distributed to us pursuant to the following terms and conditions: Copyright (c) 2000 The Apache Software Foundation. All rights reserved. 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The end-user documentation included with the redistribution if any, must include the following acknowledgement: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowlegement may appear in the software itself, if and wherever such third-party acknowlegements normally appear. 4. The names "Apache", and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org. 5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name without prior written permission of the Apache Group. THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS 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.

Apache Software License, Version 2.0


This product includes the Apache software product found at http://apache.org , and the Apache software product is distributed to us pursuant to the following terms and conditions: Copyright (c) 2000-2004 The Apache Software Foundation. All rights reserved. TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, nonexclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent

litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: A. You must give any other recipients of the Work or Derivative Works a copy of this License; and B. You must cause any modified files to carry prominent notices stating that You changed the files; and C. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and D. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

The Artistic License


Various media for this product contain miniperl v.5.8.7 ("Library"), which is licensed under the terms of the Artistic License. The Library is Copyright (C) Copyright 1987-2001, Larry Wall THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Sun Microsystems, Inc. Binary Code License Agreement


1. LICENSE TO USE. Sun grants you a non-exclusive and non-transferable license for the internal use only of the accompanying software and documentation and any error corrections provided by Sun (collectively "Software"), by the number of users and the class of computer hardware for which the corresponding fee has been paid. 2. RESTRICTIONS. Software is confidential and copyrighted. Title to Software and all associated intellectual property rights is retained by Sun and/or its licensors. Except as specifically authorized in any Supplemental License Terms, you may not make copies of Software, other than a single copy of Software for archival purposes. Unless enforcement is prohibited by applicable law, you may not modify, decompile, or reverse engineer Software. Licensee acknowledges that Licensed Software is not designed or intended for use in the design, construction, operation or maintenance of any nuclear facility. Sun Microsystems, Inc. disclaims any express or implied warranty of fitness for such uses. No right, title or interest in or to any trademark, service mark, logo or trade name of Sun or its licensors is granted under this Agreement. 3. LIMITED WARRANTY. Sun warrants to you that for a period of ninety (90) days from the date of purchase, as evidenced by a copy of the receipt, the media on which Software is furnished (if any) will be free of defects in materials and workmanship under normal use. Except for the foregoing, Software is provided "AS IS". Your exclusive remedy and Sun's entire liability under this limited warranty will be at Sun's option to replace Software media or refund the fee paid for Software. 4. DISCLAIMER OF WARRANTY. UNLESS SPECIFIED IN THIS AGREEMENT, ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. 5. LIMITATION OF LIABILITY. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no event will Sun's liability to you, whether in contract, tort (including negligence), or otherwise, exceed the amount paid by you for Software under this Agreement. The foregoing limitations will apply even if the above stated warranty fails of its essential purpose.

6. Termination. This Agreement is effective until terminated. You may terminate this Agreement at any time by destroying all copies of Software. This Agreement will terminate immediately without notice from Sun if you fail to comply with any provision of this Agreement. Upon Termination, you must destroy all copies of Software. 7. Export Regulations. All Software and technical data delivered under this Agreement are subject to US export control laws and may be subject to export or import regulations in other countries. You agree to comply strictly with all such laws and regulations and acknowledge that you have the responsibility to obtain such licenses to export, re-export, or import as may be required after delivery to you. 8. U.S. Government Restricted Rights. If Software is being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), then the Government's rights in Software and accompanying documentation will be only as set forth in this Agreement; this is in accordance with 48 CFR 227.7201 through 227.7202-4 (for Department of Defense (DOD) acquisitions) and with 48 CFR 2.101 and 12.212 (for non-DOD acquisitions). 9. Governing Law. Any action related to this Agreement will be governed by California law and controlling U.S. federal law. No choice of law rules of any jurisdiction will apply. 10. Severability. If any provision of this Agreement is held to be unenforceable, this Agreement will remain in effect with the provision omitted, unless omission would frustrate the intent of the parties, in which case this Agreement will immediately terminate. 11. Integration. This Agreement is the entire agreement between you and Sun relating to its subject matter. It supersedes all prior or contemporaneous oral or written communications, proposals, representations and warranties and prevails over any conflicting or additional terms of any quote, order, acknowledgment, or other communication between the parties relating to its subject matter during the term of this Agreement. No modification of this Agreement will be binding, unless in writing and signed by an authorized representative of each party. JAVA(TM) INTERFACE CLASSES JAVA API FOR XML-BASED RPC API CLASS FILES, VERSION 1.1 SUPPLEMENTAL LICENSE TERMS These supplemental license terms ("Supplemental Terms") add to or modify the terms of the Binary Code License Agreement (collectively, the "Agreement"). Capitalized terms not defined in these Supplemental Terms shall have the same meanings ascribed to them in the Agreement. These Supplemental Terms shall supersede any inconsistent or conflicting terms in the Agreement, or in any license contained within the Software. 1. Software Internal Use and Development License Grant. Subject to the terms and conditions of this Agreement, including, but not limited to Section 3 (Java(TM) Technology Restrictions) of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable, limited license to reproduce internally and use internally the binary form of the Software, complete and unmodified, for the sole purpose of designing, developing and testing your Java applets and applications ("Programs"). 2. License to Distribute Software. In addition to the license granted in Section 1 (Software Internal Use and Development License Grant) of these Supplemental Terms, subject to the terms and conditions of this Agreement, including but not limited to Section 3 (Java Technology Restrictions), Sun grants you a non-exclusive, non-transferable, limited license to reproduce and distribute the Software in binary form only, provided that you (i) distribute the Software complete and unmodified and only bundled as part of your Programs, (ii) do not distribute additional software intended to replace any component(s) of the Software, (iii) do not remove or alter any proprietary legends or notices contained in the Software, (iv) only distribute the Software subject to a license agreement that protects Sun's interests consistent with the terms contained in this Agreement, and (v) agree to defend and indemnify Sun and its licensors from and against any damages, costs, liabilities, settlement amounts and/or expenses 3. Java Technology Restrictions. You may not modify the Java Platform Interface ("JPI", identified as classes contained within the "java" package or any subpackages of the "java" package), by creating additional classes within the JPI or otherwise causing the addition to or modification of the classes in the JPI. In the event that you create an additional class and associated API(s) which (i) extends the functionality of the Java Platform, and (ii) is exposed to third party software developers for the purpose of developing additional software which invokes such additional API, you must promptly publish broadly an accurate specification for such API for free use by all developers. You may not create, or authorize your licensees to create additional classes, interfaces, or subpackages that are in any way identified as "java", "javax", "sun" or similar convention as specified by Sun in any naming convention designation. 4. Trademarks and Logos. You acknowledge and agree as between you and Sun that Sun owns the SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET trademarks and all SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET-related trademarks, service marks, logos and other brand designations ("Sun Marks"), and you agree to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.sun.com/policies/trademarks. Any use you make of the Sun Marks inures to Sun's benefit. 5. Source Code. Software may contain source code that is provided solely for reference purposes pursuant to the terms of this Agreement. Source code may not be redistributed unless expressly provided for in this Agreement. 6. Termination for Infringement. Either party may terminate this Agreement immediately should any Software become, or in either party's opinion be likely to become, the subject of a claim of infringement of any intellectual property right. For inquiries please contact: Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, California 95054 (LFI# 136499/Form ID# 011801)

Notes

*85158* *85158* *85158* *85158*


*85158*

S-ar putea să vă placă și