Professional Documents
Culture Documents
Copyright
2008 Business Objects, an SAP company. All rights reserved. Business Objects owns the following U.S. patents, which may cover products that are offered and licensed by Business Objects: 5,295,243; 5,339,390; 5,555,403; 5,590,250; 5,619,632; 5,632,009; 5,857,205; 5,880,742; 5,883,635; 6,085,202; 6,108,698; 6,247,008; 6,289,352; 6,300,957; 6,377,259; 6,490,593; 6,578,027; 6,581,068; 6,628,312; 6,654,761; 6,768,986; 6,772,409; 6,831,668; 6,882,998; 6,892,189; 6,901,555; 7,089,238; 7,107,266; 7,139,766; 7,178,099; 7,181,435; 7,181,440; 7,194,465; 7,222,130; 7,299,419; 7,320,122 and 7,356,779. Business Objects and its logos, BusinessObjects, Business Objects Crystal Vision, Business Process On Demand, BusinessQuery, Cartesis, Crystal Analysis, Crystal Applications, Crystal Decisions, Crystal Enterprise, Crystal Insider, Crystal Reports, Crystal Vision, Desktop Intelligence, Inxight and its logos , LinguistX, Star Tree, Table Lens, ThingFinder, Timewall, Let There Be Light, Metify, NSite, Rapid Marts, RapidMarts, the Spectrum Design, Web Intelligence, Workmail and Xcelsius are trademarks or registered trademarks in the United States and/or other countries of Business Objects and/or affiliated companies. SAP is the trademark or registered trademark of SAP AG in Germany and in several other countries. All other names mentioned herein may be trademarks of their respective owners. Business Objects products in this release may contain redistributions of software licensed from third-party contributors. Some of these individual components may also be available under alternative licenses. A partial listing of third-party contributors that have requested or permitted acknowledgments, as well as required notices, can be found at: http://www.businessobjects.com/thirdparty 2008-11-06
Third-party Contributors
Contents
Chapter 1 Welcome to the BusinessObjects Enterprise XI 3.1 Upgrade Guide 7 What's new in the BusinessObjects Enterprise...........................................8 What this guide explains..............................................................................9 What this guide does not explain...............................................................10 BusinessObjects Enterprise guides...........................................................10 Chapter 2 Getting Started 13
Upgrading from BusinessObjects Enterprise.............................................14 Simple Upgrades..................................................................................15 Complex upgrades...............................................................................16 Upgrading from Crystal Enterprise............................................................18 Upgrade and migration scenarios..............................................................18 Upgrading server and client components..................................................20 Chapter 3 Preparing for upgrades 21
System requirements ................................................................................23 User permissions for installing BusinessObjects Enterprise.....................23 Choosing a web application server............................................................24 CMS Database requirements and preparation..........................................25 Setting up a database for the auditing database..................................26 Using MySQL as the Central Management Server (CMS) database....26 To setup a database account for BusinessObjects Enterprise.............27 Setting up an empty database for the CMS.........................................27 Preparing an existing database server.................................................31
Contents
Chapter 4
33
Running the installer..................................................................................35 Entering user information and a product keycode.....................................36 To install Language Packs ........................................................................36 To select a simple upgrade........................................................................37 To specify the existing CMS database.......................................................38 To specify an installation directory ............................................................39 To enter information on your existing CMS ...............................................41 To specify Server Intelligence Information.................................................41 CMS database configuration.....................................................................42 To configure your MySQL database server .........................................42 To configure an existing database server ............................................42 To select a web application server configuration option............................46 To configure a new Tomcat web application server..............................48 To configure your existing web application server................................48 To enter a Web Application Container Server (WACS) HTTP port number.................................................................................................52 To start the installation...............................................................................52 To uninstall the previous version of BusinessObjects Enterprise..............52 Chapter 5 Performing a complex upgrade 55
Copying data to your XI 3.1 deployment...................................................57 Copying data from your existing CMS system database.....................58 Copying file repository server data ......................................................61 Updating the CMS Repository Objects................................................62 Using the Import Wizard.......................................................................63 Reconfiguring and adding servers.............................................................63 Enabling BusinessObjects Enterprise XI 3.1 Servers................................64 Adding the Search Index Program............................................................64
Contents
Uninstalling the previous version of BusinessObjects Enterprise XI.........65 To uninstall BusinessObjects Enterprise XI or XI Release 2................65 Chapter 6 Updating imported events 67
Chapter 7
71
Chapter 8
73
To set up Desktop Intelligence Release 2 and XI 3.x interconnectivity.....74 Chapter 9 Upgrading Performance Management objects to XI 3.1 77
Upgrading your Performance Management repository..............................78 To upgrade your Performance Management repository.......................79 Appendix A Get More Help 81
Index
85
Contents
Welcome to the BusinessObjects Enterprise XI 3.1 Upgrade Guide What's new in the BusinessObjects Enterprise
This guide explains how to upgrade your System Data and Business Intelligence content to BusinessObjects Enterprise XI 3.1 from BusinessObjects Enterprise XI or XI Release 2. Online documentation library A completely new interface to the full documentation set now has guides for all Business Objects products. The new online documentation library has the most up-to-date version of the Business Objects product documentation, posted upon publication and updated regularly. You can browse the library contents, run full-text searches, read guides on line, and download PDFs. http://support.businessobjects.com/documentation/product_guides/default.asp
Welcome to the BusinessObjects Enterprise XI 3.1 Upgrade Guide What this guide explains
Description The use of the Microsoft Internet Information Services (IIS) web application server version 6 or 7 is now supported on Windowsbased BusinessObjects Enterprise servers. The deployment of ASP.NET web applications is now supported on Microsoft operating systems running the IIS web application server. IP version 6 (IPv6) addresses can now be used anywhere in BusinessObjects Enterprise. A new Web Application Container Server (WACS) allows you to run the Central Management Console (CMC) on Windows machines without the need to install any Java components.
.NET support
.NET InfoView A new .NET-based version of the InfoView application is now supported.
Note:
If you are upgrading from BusinessObjects Enterprise XI Release 2, XI Release 2 MHF1 or XI Release 2 SP1, you must first upgrade to BusinessObjects Enterprise XI Release 2 SP2 or higher before you upgrade to BusinessObjects Enterprise XI 3.1. All versions of BusinessObjects Enterprise XI and XI Release 2 SP2 and higher are supported for upgrading to BusinessObjects Enterprise XI 3.1.
Welcome to the BusinessObjects Enterprise XI 3.1 Upgrade Guide What this guide does not explain
You can install most of the newest versions of BusinessObjects client components side-by-side with the previous versions of these components. When you have tested the new versions and are sure that you no longer require the previous versions of these components, you can uninstall them.
10
Welcome to the BusinessObjects Enterprise XI 3.1 Upgrade Guide BusinessObjects Enterprise guides
Description Covers the key concepts you should consider before you begin deploying BusinessObjects Enterprise. This guide includes an overview of the architecture, tips for assessing your existing environment, determining your organization's needs, and preparing for the installation. Leads you through the steps required to run the setup program and complete your installation of BusinessObjects Enterprise. There are UNIX and Windows versions of this guide available. Covers topics related to the deployment of web applications to web application servers with BusinessObjects Enterprise. There are UNIX and Windows versions of this guide available. Provides content for server and content administration. The server administration topics includes server configuration, managing authentication, configuring firewalls, and measuring system performance. The content administration topics include working with the CMC, configuring rights and access levels, managing users, and working with Business Objects applications and objects.
11
Welcome to the BusinessObjects Enterprise XI 3.1 Upgrade Guide BusinessObjects Enterprise guides
Description Provides an overview of the publishing process, working with publications, publishing Crystal reports, publishing Web Intelligence documents, publishing Desktop Intelligence documents, and publishing security.
BusinessObjects 5/6 to XI 3.1 Details content migration from legacy Migration Guide Business Objects software, such as Classic or Enterprise 5 or 6, to BusinessObjects Enterprise XI 3.1. BusinessObjects Enterprise Upgrade Guide Information for upgrades from BusinessObjects Enterprise XI to BusinessObjects Enterprise XI 3.1. Provides an overview of InfoView and working with Crystal Reports, Web Intelligence, objects, discussions, encyclopedia, and Voyager workspaces.
For a complete list of all of our product documentation please visit: http://support.businessobjects.com/documentation/product_guides/default.asp
12
Getting Started
The upgrade options that are available to you depend on your current deployment and your preferred method of updating.
Note:
Please ensure that all components of your BusinessObjects Enterprise deployment are at the same patch level before you start using the system. If the components are at different patch levels this may prevent them from communicating properly. If you are upgrading from BusinessObjects Enterprise XI Release 2, XI Release 2 MHF1 or XI Release 2 SP1, you must first upgrade to BusinessObjects Enterprise XI Release 2 SP2 or higher before you upgrade to BusinessObjects Enterprise XI 3.1. All versions of BusinessObjects Enterprise XI and XI Release 2 SP2 and higher are supported for upgrading to BusinessObjects Enterprise XI 3.1.
14
If you import events from a BusinessObjects Enterprise deployment, you must run an EventUpdater script to associate the imported events with the destination Central Management Server (CMS). If you are upgrading performance management InfoObjects from BusinessObjects Enterprise XI, you also need to upgrade the Performance Management repository. This is accomplished from the Performance Management Setup page. Although it is recommended that you upgrade all your Desktop Intelligence clients to XI 3.1, you can continue using Desktop Intelligence XI Release 2 clients against an XI 3.1 server during the upgrade phase.
Related Topics
Updating imported events on page 67 Upgrading Performance Management objects to XI 3.1 on page 77 Using Desktop Intelligence XI Release 2 with BusinessObjects Enterprise XI 3.1 on page 73
Simple Upgrades
If the BusinessObjects Enterprise XI 3.1 installation program detects a simple deployment, where an entire product line has been installed on a single computer, you can perform a simple upgrade to XI 3.1. In a simple upgrade to XI 3.1, the installation program performs the following steps: Installs BusinessObjects Enterprise XI 3.1. Points the BusinessObjects Enterprise XI 3.1 Input and Output File Repository Servers (FRS) to the location of the existing BusinessObjects Enterprise XI or XI Release 2 FRSs. Creates a new XI 3.1 CMS database, and then copies the contents of your existing CMS database to the XI 3.1 database. Updates all of the objects in the newly copied CMS database to XI 3.1 objects. Disables the existing XI or XI Release 2 system. If you perform a simple upgrade to BusinessObjects Enterprise XI 3.1, the installation program automatically disables the previous XI system. After the upgrade is complete, the BusinessObjects Enterprise XI 3.1 installation program asks you whether to uninstall the previous system. It is highly
15
recommended that you uninstall the previous version of the system as soon as you have verified that XI 3.1 has been successfully installed. If you choose to uninstall BusinessObjects Enterprise XI 3.1 later, you must ensure that the previous version's servers are not re-enabled and not re-started. In particular, enabling the older version of the CMS and File Repository Servers will conflict with the XI 3.1 system. If the installation program does not detect a simple deployment, you must perform a complex upgrade. This includes the scenario where your deployment's web and application servers are on separate computers.
Note:
This option is available only when upgrading on a Windows computer. If you are upgrading on a UNIX computer, you must perform a complex upgrade, even if you are upgrading from a deployment that has been installed on a single computer. If you are performing a simple upgrade, the installation program stops your existing XI or XI Release 2 CMS database. This means that your existing deployment will not be available during the upgrade process, and users will not be able to access BusinessObjects Enterprise.
Related Topics
Complex upgrades
If the XI 3.1 installation program does not detect a simple deployment, or if you want to install XI 3.1 across multiple servers, you must perform a complex upgrade. In complex upgrades, you install a new BusinessObjects Enterprise XI 3.1 deployment, and then copy your content and system data from your existing BusinessObjects Enterprise XI deployment to the XI 3.1 deployment. You can install BusinessObjects Enterprise XI 3.1 on the same computer as your existing XI or XI Release 2 system, or on a separate computer. If you are performing a complex upgrade, you must manually perform the following steps after you've finished installing XI 3.1:
16
Import your existing XI or XI Release 2 Business Intelligence content to your XI 3.1 deployment, either by using the Central Configuration Manager (CCM) or by using the Import Wizard.
Note:
If you chose to import content through the CCM, you must also either re-point your XI 3.1 Input and Output File Repository Servers to the location of your existing repositories, or copy the contents of your existing repositories to the XI 3.1 repositories. Reconfgure and add the BusinessObjects Enterprise XI 3.1 servers to the Central Management Server (CMS). Add the Search Index Program. Update any events that you copied to the BusinessObjects Enterprise XI 3.1 deployment from your existing BusinessObjects Enterprise deployment. Configure the XI 3.1 auditing database.
The upgrade process does not copy server and server cluster settings to your new deployment. If your existing deployment is distributed across several servers or clusters, and you want to replicate the same environment for your XI 3.1 deployment, you must manually add the servers and clusters by using the CMS. For more information, see Managing and Configuring Servers chapter of the BusinessObjects Enterprise Administrator's Guide. Your BusinessObjects Enterprise XI 3.1 system can operate at the same time as your existing XI or XI Release 2 system, whether the deployments are on the same computers or not. When you are ready to, you can uninstall the XI or XI Release 2 system.
Related Topics
Performing a complex upgrade on page 55 Adding the Search Index Program on page 64
Side-by-side deployments
When you perform a side-by-side installation, you need to ensure that your BusinessObjects XI 3.1 installation does not clash with your preexisting BusinessObjects Enterprise version by: Specifying a unique CMS cluster name for the BusinessObjects Enterprise XI 3.1 installation.
17
Specifying unique port numbers for the BusinessObjects Enterprise XI 3.1 installation.
Version
Scenario
BusinessObjects 5/6
For more information on migrating from BusinessObjects 5/6, see the BusinessObjects 5/6 to XI 3.1 Migration Guide.
18
Version
Scenario
Crystal Enterprise 9
To perform a simple upgrade from Crystal Enterprise 9, you must first upgrade to BusinessObjects Enterprise XI or XI Release 2 or higher. You can perform a complex upgrade from Crystal Enterprise 9. To perform a simple upgrade from Crystal Enterprise 10, you must first upgrade to BusinessObjects Enterprise XI or XI Release 2 or higher. You can perform a complex upgrade from Crystal Enterprise 10. You can perform a simple or complex upgrade from BusinessObjects Enterprise XI.
Crystal Enterprise 10
BusinessObjects Enterprise XI
To perform a simple upgrade from BusinessObjects XI Release 2 SP1 or lower, you BusinessObjects Enterprise XI must first upgrade to SP2 or higher.
Release 2, SP 1 or lower
You can perform a complex upgrade from BusinessObjects XI Release 2 SP1 or lower. You can perform a simple or complex upRelease 2 or higher.
19
Version
Scenario
To install the .NET components in BusinessObjects Enterprise XI 3.1, uninstall XI 3.0, and then install XI 3.0.
BusinessObjects Enterprise XI To update your deployment with the enhancements in XI 3.1, but without installing 3.0
the .NET components, apply the BOE XI3.1 Patch. For more information, see the BusinessObjects XI 3.1 Update Installation and Deployment Guide.
If some of the components in your deployment are at different product versions or patch levels, this may prevent them from communicating with a BusinessObjects Enterprise XI 3.1 Central Management Server properly. Previous versions of the following components may communicate with BusinessObjects Enterprise XI 3.1, with reduced functionality: BI Widgets Live Office Business Views Manager You can install most of the newest versions of BusinessObjects client components side-by-side with the previous versions of these components. When you have tested the new versions and are sure that you no longer require the previous versions of these components, you can uninstall them.
20
It is highly recommended that you follow your usual administrative practices before upgrading to BusinessObjects Enterprise XI 3.1. However, you should also consider the following common tasks and guidelines: Consult the What's New Documentation and the Architecture chapter in the BusinessObjects Enterprise Planning Guide for an overview of the changes in BusinessObjects Enterprise XI 3.1. Consult the Release Notes included with your product distribution for further information that may pertain to your reporting environment (re lease.pdf). Review your systems to ensure that they meet the basic requirements for a BusinessObjects Enterprise installation. Stop the web servers and/or web application servers that are configured for use with BusinessObjects Enterprise. The installation program gives you the option of creating a new MySQL database or using an existing database for your BusinessObjects Enterprise XI 3.1 deployment's Central Management Server (CMS) database. If you are using an existing database, ensure that you have the connection details about the database server that you select, and logon credential information for the account used for connecting to the database instance. The database account requires permissions to add and drop tables, as well as to insert, delete, and update data in those tables. Back up your existing repository or repositories, including the system database and Input and Output File Repository Servers. Back up any custom web applications, HTML pages, or scripts that you have added to your existing deployment. Make sure you log onto the machine as an administrator first when you install or upgrade BusinessObjects Enterprise components. If you are upgrading on a Windows computer, you must log on with an administrator account. If you are upgrading on UNIX, you must log on as the same user that installed your previous BusinessObjects Enterprise deployment. Close any other programs that are running locally before you start the BusinessObjects Enterprise setup program.
22
System requirements
For a detailed list of supported environments and hardware requirements, consult the Products Availability Report (PAR) document available on the Business Objects support site http://support.businessobjects.com/documen tation/supported_platforms. This document includes specific version and patch-level requirements for web application servers, web browsers, and operating systems. For information related to the planning of a BusinessObjects Enterprise deployment, consult the BusinessObjects Enterprise Planning Guide. BusinessObjects Enterprise ships with the Tomcat web application server and MySQL database server. If you are planning to use a different web application or database server, it must be installed and configured before BusinessObjects Enterprise.
Related Topics
23
Category
Required permissions
Operating System Administrative privileges on the local machine. Network Network connectivity to all machines in the deployment, as well access to as the appropriate ports on each of the machines. Rights to create and drop tables, plus rights to read, write, and edit rows. For more information on the database privileges required, see Databases in BusinessObjects Enterprise in the BusinessObjects Enterprise Planning Guide. Use the same user account for installing both BusinessObjects Enterprise and your web application server, to reduce the likelihood of encountering a problem with access control settings.
Database
Note:
The following scenarios are not supported: Installation on a domain controller. Installation on a Windows machine where the default local Administrator group security settings have been modified.
24
provides an easier way to deploy, configure, and maintain the CMC, and removes the need for Java application server administration skills. There are two ways that you can install WACS: If you are performing a simple upgrade, if you choose not to deploy BusinessObjects Enterprise web applications to a Java application server, the installation program automatically creates a WACS server and then adds a CMC service to the server. The CMC is ready to use after you complete the installation. If you are performing a complex upgrade on a Windows machine, and chose a Custom or Expand install, you can choose to install WACS on the "Select Features" screen by expanding Server Components and selecting Web Application Container Server For more information on installing WACS, see the BusinessObjects Enterprise Installation Guide. For more information on using WACS, see the Working with Web Application Container Servers chapter of the BusinessObjects Enterprise Administrator's Guide.
Before installing BusinessObjects Enterprise, review this information in order to properly prepare your CMS system and auditing database. For more information on database requirements, refer to the Databases in BusinessObjects Enterprise section in the BusinessObjects Enterprise Planning Guide.
25
Note:
Regardless of database type, the database must be setup to use Unicode character encoding, such as UTF-8.
26
27
Note:
Review the online BusinessObjects Enterprise supported platforms document for information related to supported database software and version requirements:http://support.businessobjects.com/documentation/. To integrate your existing database with BusinessObjects Enterprise, you need to prepare it. Here is a summary of the steps to prepare your database: Create a new tablespace, schema, or database (the exact terminology will depend on the database platform you're using) to act as the CMS database. Create a second for the auditing database, if you plan to enable auditing. Create a new user account and password to be used by BusinessObjects Enterprise to access the CMS database. Create a second username and password if you plan to enable auditing. Specify that the new user account has required permissions to create, modify, and delete tables and create procedures so that database can be modified as required. Record the name of the database(s), the user account(s), and the password(s) you created, so you can enter the details when you run the BusinessObjects Enterprise installer.
During the installation, you can choose to reinitialize the existing database. This will cause new tables to be created in your existing database. Consult your specific database server documentation if you are unsure of the procedure for creating a new tablespace, schema, or database. Ensure that your database server is set up to use Unicode character encoding (such as UTF-8).
Note:
If you have a previous release of BusinessObjects Enterprise you cannot use your database from a previous release for BusinessObjects Enterprise. You must create a new database, or existing data from the previous release will be destroyed. To migrate from an previous release, create a new database migrate your old content to the new current version's database after the installation is complete.
28
The auditing database can be partitioned. Create the database with these settings:
Collating Sequence = Identity Codeset = UTF-8 Territory = XX
If your DB2 database does not have the correct Collating Sequence setting, the user and usergroup objects may not sort properly in the CMC. Replace XX with the code that is appropriate for your location. Consult your DB2 documentation for more information. If you are using DB2 8.1, you require a C compiler that is installed and configured to build SQL stored procedures. DB2 8.2 through version 9.1 do not have this requirement. Stored procedures are used by BusinessObjects Enterprise when users are added to groups. Please consult the DB2 documentation for details on how to configure the C compiler for SQL stored procedures.
Once the database is created, you will need to prepare it for the BusinessObjects Enterprise installation.
Related Topics
29
30
Related Topics
MySQL
Note: Sybase The Sybase server name is a combination of the host name and the port number which is set by your database administrator in the file sql.ini interfaces file. BusinessObjects Enterprise will connect to the default database for the user you specify. This default is set by the database administrator. Server: DB2 database alias Login credentials used to access database Server: TNSNAMES connect identifier Login credentials used to access database
DB2
Oracle
31
Existing Information required by installer database Microsoft SQL Serv- er ODBC DSN name from the Windows System DSN.
Existing Information required by installer database Database name Server name Port number (default is 3306) Login credentials used to access database Server name Login credentials used to access database
MySQL
Note: Sybase The Sybase server name is a combination of the host name and the port number which is set by your database administrator in the file sql.ini interfaces file. BusinessObjects Enterprise will connect to the default database for the user you specify. This default is set by the database administrator. Server: DB2 database alias Login credentials used to access database Server: TNSNAMES connect identifier Login credentials used to access database
DB2
Oracle
32
You can perform a simple upgrade to BusinessObjects Enterprise XI 3.1 if the BusinessObjects Enterprise XI 3.1 installation program detects an entire XI or XI Release 2 deployment on the Windows computer that you are installing XI 3.1 on. Performing a simple upgrade to BusinessObjects Enterprise XI 3.1 requires the following inputs. Providing information on your existing XI or XI Release 2 Central Management Server (CMS) database. Providing information on the CMS for the existing deployment. This includes the port on with the CMS is running and the administrative credentials. Providing information on the Server Intelligence Agent (SIA). The Server Intelligence Agent is a component of the Central Management Console (CMC) that simplifies administrative procedures previously carried out by the Central Configuration Manager (CCM), such as the management of CMC server processes. For more information on the Server Intelligence Agent, see the Managing and Configuring Servers chapter of the BusinessObjects Enterprise Administrator's Guide. Configuring the XI 3.1 CMS database.
Note:
The installation of a MySQL database is provided with the installation package. You can use a MySQL database to create a new copy of CMS database for XI 3.1, or you can use any of the other database servers that are supported for the release. Configuring the Java application server. You can choose to either install and configure Tomcat or configure any other Java application server that is supported for the release.
The BusinessObjects Enterprise XI 3.1 installation program writes the details of your existing deployment to a log file. The name of the file is boe_up grade_output.xml; the boe_upgrade.xsl file provides formatting when you open boe_upgrade_output.xml You can use this log file as a reference when you are configuring the servers and server clusters in your XI 3.1 deployment. The default location of this log file is C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\Logging\.
34
This setting is only used by the Setup program for the duration of the installation. You select languages to be installed on your new BusinessObjects Enterprise server later. You have a choice of the following languages for setup: Chinese Simplified Chinese Traditional Danish Dutch English French German Italian Japanese Korean Norwegian Polish Portuguese (Brazil) Russian Spanish Swedish Thai 3. Deselect Create log file during installation if you don't want the installer to create a log file.
35
The log file is created as: <INSTALLDIR>\BusinessObjects Enterprise 12.0\Logging\BOEInstall_X.log. 4. Click OK. The installation wizard welcome screen is displayed. 5. Click Next to proceed with the installation. If you are installing BusinessObjects Enterprise on Windows XP Service Pack 2 or higher, an Internet Connection Firewall warning message is displayed. Click OK to continue. The "License Agreement" dialog is displayed. 6. Review the agreement. 7. Select I accept the License Agreement and click Next. The "User Information" screen is displayed.
English is mandatory because it's used as a back-up language if a problem with a language pack is detected. English cannot be deselected.
36
1. Select the language packs you want to install. The language packs currently available for installation include: Chinese Simplified Chinese Traditional Danish Dutch English French German Italian Japanese Korean Norwegian Polish Portuguese (Brazil) Russian Spanish Swedish Thai
Note:
You can also add language packs after installing BusinessObjects Enterprise. 2. Click Next. The "Install Type" screen is displayed.
37
Points the BusinessObjects Enterprise XI 3.1 Input and Output File Repository Servers (FRS) to the location of the existing BusinessObjects Enterprise XI or XI Release 2 FRSs. Creates a new XI 3.1 CMS database, and then copies the contents of your existing CMS database to the XI 3.1 database. Updates all of the objects in the newly copied CMS database to XI 3.1 objects. Disables the existing XI or XI Release 2 system.
If you want to perform a side-by-side deployment or a deployment that is distributed across multiple servers, select No, do not perform an upgrade installation. On a later screen, you will be able to choose to perform a New, Custom, or Web Tier installation.
2. Click Next to continue. The "Existing CMS Database Information for Upgrade" screen appears.
38
1. On the CMS Database list, select DB2. 2. Type the DB2 database alias in the Server field. 3. Type the credentials for the server in the Username and Password fields, and click Next . d. If you are copying data from MySQL: 1. On the CMS Database list, select MySQL. 2. Type the name of the database in the Database field. 3. Type the Host Name in the Server field. 4. Type the port that the database uses in the Port field 5. Type the credentials for the server in the Username and Password fields, and click Next . e. If you are copying data from Sybase: 1. On the CMS Database list, select Sybase. 2. Type the Sybase Server Name in the Server field. 3. Type the credentials for the server in the Username and Password fields, and click Next. The "Install Type" screen appears.
39
Note:
If you chose to perform a simple upgrade on the "BusinessObjects Enterprise Upgrade" page, you can only select a New install type. The Custom or Expand Install and Web Tier options are disabled. 1. Specify whether you want to install a MySQL database server, or if you want BusinessObjects Enterprise to use an existing database server. 2. In the Destination Folder field, specify where to install the BusinessObjects Enterprise components. You must select a different installation directory for BusinessObjects Enterprise XI 3.1 than the directory for your previous BusinessObjects Enterprise deployment. The installation program validates the directory that you specify, and prevents you from installing XI 3.1 in the same directory as your existing deployment. 3. Click Next to continue with the installation setup. The "Server Components Configuration" screen is displayed.
40
41
Once the SIA information is entered, the port number will be validated before you can proceed to configure the CMS database for your installation. A warning will display if the port you specified is not available. Depending on whether you chose to use MySQL as the CMS database or to use an existing database server, the "MySQL Database Server Configuration" screen or "CMS Database Information" screen appears.
The default port number is 3306. If the existing CMS database uses port 3306, you must specify a different port number for the XI 3.1 database. You cannot to copy content from one CMS database to the other CMS database in the event of a conflict. 2. In the MySQL root User Account pane, specify and confirm a password for the MySQL root user account. 3. In the MySQL BusinessObjects User Account pane, specify and confirm a password for the MySQL BusinessObjects user account. 4. Click Next to continue the installation setup. The "Select Web Application Server" screen is displayed.
42
If you are using an existing database, ensure that you have the connection details about the database server that you select, and logon credential information for the account used for connecting to the database instance. The database account requires permissions to add and drop tables, as well as to insert, delete, and update data in those tables. 1. Select a database type from the Select existing CMS database drop-down list in the CMS Database pane. Depending on your database server selection, corresponding input fields are displayed in the CMS Database pane. 2. Provide all the required information for the database in the fields provided in the CMS Database pane. The table below summarizes all the information required for each database type:
Database type Information required at install time MySQL Database: MySQL database name Server: MySQL server name Port: default port is 3306 Login credentials used to access database Server: Sybase Server Name Login credentials used to access database
Sybase
Note: The Sybase server name is a combination of the host name and the port number which is set by your database administrator in the file sql.ini. Server: DB2 database alias Login credentials used to access database
DB2
43
Database type
Information required at install time Server: tnsnames connect identifier Login credentials used to access database ODBC DSN
Oracle
If you do not want to specify an auditing database for your new installation skip to step 6. 3. Select the Auditing Database box to specify an auditing database for your new installation. The input fields under the Auditing Database box are activated.
Note:
If you select a BusinessObjects Enterprise XI or XI Release 2 auditing database for BusinessObjects Enterprise XI 3.1, the installation program permanently deletes any existing auditing data from that database. This means that the data will not be available after the upgrade is complete. If you want to keep auditing data from XI or XI Release 2, select a new database for XI 3.1. 4. Select a database type from the Select existing Auditing database drop-down list in the Auditing Database pane. Depending on your database server selection, corresponding input fields are displayed in the Auditing Database pane. 5. Provide all the required information for the database in the fields provided in the Auditing Database pane. The table below summarizes all the information required for each database type:
44
Database type
Information required at install time Database: MySQL database name Server: MySQL server name Port: default port is 3306 Login credentials used to access database Server: Sybase Server Name Login credentials used to access database
MySQL
Sybase
Note: The Sybase server name is a combination of the host name and the port number which is set by your database administrator in the file sql.ini. Server: DB2 database alias Login credentials used to access database Server: tnsnames connect identifier Login credentials used to access database ODBC DSN
DB2
Oracle
6. Select the Reset existing database box to delete all current tables and entries in the existing database.
Note:
This option permanently deletes all of the contents of the existing database that you select. 7. Click Next to continue with the installation setup. The "Select Web Application Server" screen is displayed. This screen only displays if a connection is established with the database configuration you provided.
45
If you are using the 64-bit version of IIS 7, you must ensure that: ASP.NET is enabled. The advanced IIS setting Enable 32-bit Applications is set to "True". The advanced IIS setting .NET Application Pool is set to "Classic" mode. If the IIS Web Application Server option is not selectable, ASP.NET v1.1 and the IIS (Control Panel > Add or Remove Programs > Windows Components > Application Server) must be installed.
46
To configure a Java web application server for BusinessObjects Enterprise you will need the web application server administrator account name and password, as well as the listener port number. 1. To use a Java web application server, select Java Web Application Server and choose one of the following options: Install Tomcat application server and deploy to it. This will automatically install and configure Tomcat. Automatically deploy to a pre-installed Web Application Server. This will prompt you to enter the configuration and authentication information on the next screen. 2. To use the IIS web application server included as part of your Windows operating system, choose IIS Web Application Server, then select the website to use for deployment from the drop-down list. 3. Click Next. Depending on your selection, you can now proceed to either configure your web application server, or start the installation process.
47
If the port numbers you specified are in use, a warning message is displayed. To continue you will have to specify unused and valid port numbers. The "Start Installation" screen is displayed.
48
Information required for installation Server Instance: Name of the current web application server instance (for example localhost). Service Name: Name of the Windows service if the application server will be installed as a windows service (for example Tomcat5). Application Server Installation Directory: The directory where the web application server is installed (for example C:\wdeploy\appserver\Tom cat5520). Port: Administration port of the application server (for example 7001). Username: User name with administration rights to the application server. Password: Password for account with administration rights to the application server. Server Instance: Name of the current web application server instance (for example mserver1). Application Server Domain Root Directory: The WebLogic domain root directory (for example
C:\bea\weblogic10\user_projects\do mains\base_domain).
WebLogic 10
WebLogic 9.2
Port: Administration port of the application server (for example 7001). Username: User name with administration rights to the application server. Password: Password for account with administration rights to the application server. Server Instance: Name of the current web application server instance (for example mserver1). Application Server Domain Root Directory: The directory where the web application server is installed (for example C:\bea\user_projects\do mains\base_domain).
WebSphere 6.1
49
Information required for installation SOAP Port: The SOAP Connector Port of the application server (for example 8880). Username: User name with administration rights to the WebSphere application server. Password: Password for account with administration rights to the application server. Server Instance: Name of the current web application server instance (for example server1). Virtual Host: The virtual host to which the application must be bound. Admin is Secure?: Select this option to enable security requiring administrative access credentials to the application. Note: Values for the username and password parameters must be set when Admin is Secure is enabled. Application Server Installation Directory: The directory where the web application server is installed (for example C:\Program Files\IBM\WebSphere\AppServer).
50
Information required for installation Admin is Secure?: Select this option to use Secure Sockets Layer (SSL) encryption for authentication. Note: If Admin is Secure? is not selected, you will still have to specify the username and password to access the server. Port: Administration port of the application server (for example 6003). This should be the request port of the <notification-server> element in the opmn.xml file. Username: User with administration rights to the application server. Password: Password for account with administration rights to the application server. Server Instance: Name of the Oracle Application Server application server instance (for example home). Server Name: Name of the target application server (for example, myserver.domain.com). Group Id: Name of the server group to which the target application belongs (for example "Default_group"). Application Server Installation Directory: The directory where the web application server is installed (for example C:\product\10.1.3\Ora cleAS_1).
The "Start Installation" screen is displayed. Remember your credentials for the web application server as they may be required to install add-ons such as ProcessTracker or additional language packs.
51
It is highly recommended that you uninstall your previous BusinessObjects Enterprise XI or XI Release 2 system as soon you have verified that XI 3.1 has been successfully installed. If you choose to uninstall BusinessObjects Enterprise XI 3.1 later, you must ensure that the previous version of servers are not re-enabled and not re-started. In particular, enabling the older version of the CMS and File Repository Servers will conflict with the XI 3.1 system.
52
1. If you want to uninstall your previous version of BusinessObjects Enterprise click Yes, and when the Windows Installer dialog box appears, click Yes again. 2. If you do not want to uninstall your previous version of BusinessObjects Enterprise, click Exit to complete the installation process. The installation program disables the previous version of BusinessObjects Enterprise. You can uninstall the previous version at a later time through Add/Remove Programs.
53
54
In a complex upgrade, you install a new deployment of BusinessObjects Enterprise XI 3.1, either on the same computer as your previous BusinessObjects Enterprise deployment or on another computer. You can copy the data from your previous deployment to the new one. After BusinessObjects Enterprise XI 3.1 is installed, both deployments can run at the same time. You can uninstall your XI or XI Release 2 deployment when you are ready to do so. After you install XI 3.1, you must perform the following steps: Copy the content from your XI or XI Release 2 deployment to your XI 3.1 deployment, either through the Central Configuration Manager or through the Import Wizard. Manually add and configure any necessary servers and server clusters. Enable your BusinessObjects Enterprise XI 3.1 services. Add the Search Indexing Program. Update any events that you copied to the BusinessObjects Enterprise XI 3.1 deployment from your existing BusinessObjects Enterprise deployment. Configure the XI 3.1 auditing database. For more information on installing BusinessObjects Enterprise XI 3.1 on a Windows computer, see the BusinessObjects Enterprise XI 3.1 Installation Guide for Windows. For more information on installing BusinessObjects Enterprise XI 3.1 on a UNIX computer, see the BusinessObjects Enterprise XI 3.1 Installation Guide for UNIX.
Note:
When you are copying content to your XI 3.1 deployment, users will still be able to access the existing XI or XI Release 2 deployment. However, any new content that is added to the existing deployment after the process of copying data has started will not be copied to the new deployment. Therefore, it is recommended that you prevent users from accessing your existing XI or XI Release 2 deployment once the process of copying your data has started. The default CMS port number is 6400. If you are installing XI 3.1 on the same machine that has an XI or XI Release 2 deployment, and you want to import content from the existing deployment to the XI 3.1 deployment,
56
you must select a different port number than the port that the existing deployment uses. If you are installing XI 3.1 on a machine that already has an existing XI or XI Release 2 deployment, you must specify a different port number for the XI 3.1 CMS database.
Related Topics
Copying data to your XI 3.1 deployment on page 57 Using the Import Wizard on page 63 Reconfiguring and adding servers on page 63 Enabling BusinessObjects Enterprise XI 3.1 Servers on page 64 Adding the Search Index Program on page 64 Updating imported events on page 67 Configuring the auditing database on page 71 Uninstalling the previous version of BusinessObjects Enterprise XI on page 65
When you use the CCM to copy the contents of a database, it re-initializes the destination database. This means that any data in the destination database is deleted. If you are copying data from a source database, and
57
want to preserve any data that already exists in the destination database, you must use the Import Wizard. If you are using the CCM to copy your content to your XI 3.1 deployment, you must perform the following steps. Use the CCM to copy the data from your existing CMS database to your XI 3.1 CMS database. Either re-point the XI 3.1 Input and Output File Repositories to the locations of the existing repositories, or copy the files in the existing file repositories to the XI 3.1 file repositories. Use the CCM to update the objects in your CMS repository. This step adds the properties to the objects copied from the CMS that XI 3.1 requires.
Note:
If you've performed a simple upgrade, the installation program automatically copies your content to your XI 3.1 deployment.
If you want to import users, groups, folders, and reports from one system database to another, without deleting the contents of the current CMS database, use the Import Wizard. For more information, click Help in the Import Wizard.
58
Note:
If you performed a simple upgrade, the installation program performs this step automatically. If you are using the Import Wizard to import content from your existing deployment, it is not necessary to perform these steps.
If you are copying a CMS database from an XI 3.1 source destination to an XI 3.1 target destination, you can change the CMS location, name, and database type. However, you cannot change the BusinessObjects Enterprise installation path, operating system, and machine name. 1. Open the Central Configuration Manager (CCM) and stop the Server Intelligence Agent (SIA). 2. Right-click the SIA and choose Properties. 3. Click the Configuration tab, and then click Specify. 4. Choose Copy, then click OK. 5. Choose the version information for the source CMS database. 6. Select the database type for the source CMS database, and then specify its database information (including host name, user name, and password). 7. Select the database type for the destination CMS database, and then specify its database information (including host name, user name, and password). 8. When the CMS database has finished copying, click OK. 9. If you are upgrading from an earlier version than XI 3.1, you will be prompted to build a Server Intelligence Agent. a. Click OK. b. Specify the administrator password, and then click OK. c. When the SIA is built, click OK. 10. Proceed to Copying file repository server data on page 61 .
59
On UNIX you can not migrate directly from a source environment that uses an ODBC connection to the CMS database. If your source CMS database uses ODBC, you must first upgrade that system to a supported native driver. 1. Stop the BusinessObjects Enterprise XI 3.1 CMS by typing the following command: ./ccm.sh -stop sia 2. Run cmsdbsetup.sh (located in <InstallDirectory>/bobje/, by default). 3. Select the copy option (option 4), then confirm your choice. 4. Select the version information for the source CMS database. 5. Select the database type for the source CMS database, then specify its database information (including host name, user name, and password). 6. Select the database type for the destination CMS database, and then specify its database information (including host name, user name, and password). The CMS database is copied to the destination machine. A message appears when the copy is complete. 7. If you are upgrading from an earlier version than XI 3.1, you will be prompted to build a Server Intelligence Agent. Specify the administrator password. A message appears when the SIA is built. 8. Proceed to Copying file repository server data on page 61 .
60
If you performed a simple upgrade, the installation program performs this step automatically. If you are using the Import Wizard to import content from your existing deployment, it is not necessary to perform these steps.
61
4. Copy the contents of the XI or XI Release 2 Input and Output folders to the XI 3.1 Input and Output folders. 5. Proceed to Updating the CMS Repository Objects on page 62
If you performed a simple upgrade, the installation program performs this step automatically. If you are using the Import Wizard to import content from your existing deployment, it is not necessary to perform these steps.
62
63
For more information on adding servers and server clusters with the CMC, see the BusinessObjects Enterprise Administrator's Guide.
If you are performing a simple upgrade to BusinessObjects Enterprise XI 3.1, the installation program performs this step automatically. 1. Log in to the Central Management Console, with an administrator username and password. 2. Go to Public Folders > Search Program, and delete the Search Indexing Program. 3. Use the Import Wizard to import the XI 3.1 Search Indexing Program.
64
The following features will not be uninstalled: The contents of your XI or XI Release 2 File Repository Servers. CMS database tables. Auditing database tables.
65
66
After you import events to a destination Central Management Server (CMS), you must run the EventUpdater script. This script updates the imported events by associating them with the BusinessObjects Enterprise XI 3.x event servers that they are to run on. If you do not run this script, you must manually re-associate the events with event servers, by navigating to every imported event and associating it with an event server. If you are importing events from more than one event server, you must run the script once for each event server that you are importing the events from. On a Windows computer, the script is called EventUpdater.bat, and is located in the c:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\scripts\ folder by default. On a UNIX computer, the script is called EventUpdater.sh, and is located in the ./bobje/ directory. The following table describes the parameters for the script.
Parameter Description
-olde The friendly name of the event server on the system that the ventserver event was exported from. -new eventserv er -cms -user -password -authenti cation The name of the event server on the XI 3.x system that you want to associate the event with. The name of any CMS on the XI 3.x destination system. The username for a BusinessObjects Enterprise administrator account. The password for the BusinessObjects Enterprise administrator account. The authentication method. The accepted values are secEnter prise, secWinAd, and secLdap.
1. Locate the appropriate script, depending on your platform. 2. Run the script with the necessary parameters.
68
On Windows, run
c:\Program Files\Business Objects\BusinessObjects Enter prise 12.0\win32_x86\scripts\eventupdater.bat" -olde ventserver <old event server friendly name> -neweventserv er <new event server name> [-cms <cms>] [-user <username>] [-password <password>] [-authentication secAuthType]
On UNIX, run
./bobje/eventupdater.sh -oldeventserver <old event server friendly name> -neweventserver <new event server name> [-cms <cms>] [-user <username>] [-password <pass word>] [-authentication secAuthType]
69
70
Using the existing BusinessObjects Enterprise XI auditing database with the BusinessObjects Enterprise XI 3.1 auditing database is not supported. When you perform an upgrade to BusinessObjects Enterprise XI 3.1, the installation program does not copy the contents of your existing auditing database. If you want to keep the contents of the previous auditing database intact, specify a new database for the XI 3.1 auditing database. You need to recreate all settings for the XI 3.1 version of the auditing database. For more information on configuring the auditing database, see the Managing Auditing chapter of the BusinessObjects Enterprise Administrator's Guide.
72
Using Desktop Intelligence XI Release 2 with BusinessObjects Enterprise XI 3.1 To set up Desktop Intelligence Release 2 and XI 3.x interconnectivity
Although it is recommended that you upgrade all your Desktop Intelligence clients to Desktop Intelligence XI 3.x, you can continue using Desktop Intelligence XI Release 2 clients against a BusinessObjects Enterprise XI 3.x server during the upgrade phase. You can continue to use Desktop Intelligence XI Release 2 clients to connect to an XI 3.xCentral Management Server (CMS), and to create, view, and edit Desktop Intelligence XI 3.x documents that use either of the following. XI Release 2 universes. XI 3.x universes that are based on XI Release 2 universe connections. You can also use Desktop Intelligence XI Release 2 and XI 3.x clients on the same computer. Desktop Intelligence XI Release 2 does not work with universes that are based on XI 3.x universe connections. Desktop Intelligence XI 3.x clients work with both XI Release 2 and XI 3.x universes and universe connections. However, you cannot use Desktop Intelligence XI 3.x to connect to an XI Release 2 CMS, or to use Desktop Intelligence documents through an XI Release 2InfoView.
Note:
It is highly recommended that you upgrade to Desktop Intelligence XI 3.0 clients. Desktop Intelligence Release 2 and BusinessObjects Enterprise XI 3.x interconnectivity should only be used to make the upgrade BusinessObjects Enterprise 3.x easier. Do not use the Central Management Console (CMC) or Designer XI 3.x to edit XI Release 2 universe connections. Using the CMC or Designer to edit an XI Release 2 universe connection will convert the universe connection to an XI 3.x format, and break compatibility. Desktop Intelligence XI Release 2 clients will not be able to use the XI 3.x universe connections.
74
Using Desktop Intelligence XI Release 2 with BusinessObjects Enterprise XI 3.1 To set up Desktop Intelligence Release 2 and XI 3.x interconnectivity
1. Before you start to upgrade to XI 3.x, ensure that the XI Release 2 deployment has the universe connections that Desktop Intelligence XI Release 2 will use. If the XI Release 2 deployment does not have the required universe connections, create the connections using Designer XI Release 2. 2. Use the Import Wizard to import Desktop Intelligence documents, universes, and universe connections to the XI 3.x CMS. The Import Wizard converts the XI Release 2 universes that you import to XI 3.x universes, but it keeps the related universe connections in XI Release 2 format.
75
Using Desktop Intelligence XI Release 2 with BusinessObjects Enterprise XI 3.1 To set up Desktop Intelligence Release 2 and XI 3.x interconnectivity
76
Upgrading Performance Management objects to XI 3.1 Upgrading your Performance Management repository
The Import Wizard and the Central Management Console (CMC) copy performance management InfoObjects from BusinessObjects Enterprise XI or XI Release 2 to BusinessObjects Enterprise XI 3.1. As in previous versions, performance management products rely on a dedicated repository that stores performance management data as well as the CMS. To copy performance management objects to BusinessObjects Enterprise XI 3.1, follow these steps: Install BusinessObjects Enterprise XI 3.1 and configure the Central Management Sever (CMS). Run the Import Wizard to copy InfoObjects from the previous version and to import connections to the connection server. For more information, see the BusinessObjects Enterprise XI 3.1 Import Wizard Guide. Upgrade the performance management repository.
Related Topics
Before you begin to copy PM metrics objects, ensure that the PMUser has all Access Rights and Privileges. You should also back up your existing Enterprise Performance Management repository.
78
Upgrading Performance Management objects to XI 3.1 Upgrading your Performance Management repository
If your performance management repository shares a database with the Central Management Server, create a connection to this database. 3. On the BusinessObjects Enterprise XI 3.1 InfoView, go to Dashboards and Analytics Setup and point the XI 3.1 deployment to the connection that you created in Designer. a. Under Open, click Dashboard and Analytics Setup. The "Setup" page is displayed. b. Click System Setup, and click the Repository tab. c. Click Change, and select the connection that you created in Designer. 4. Click Upgrade Repository to start the Repository Upgrade Wizard. 5. Open the Central Configuration Manager (CCM) and restart the Enterprise Performance Management and Web Intelligence services. 6. Logon to the InfoView and refresh your Enterprise Performance Management metrics. a. Logon to the InfoView b. Under Open, click Dashboards and Analytics. c. Click Performance Manager > Metrics. d. On the Available Metrics list, select the metric that you want to refresh, and click Refresh.
79
Upgrading Performance Management objects to XI 3.1 Upgrading your Performance Management repository
80
Business Objects offers a full documentation set covering all products and their deployment. The online documentation library has the most up-to-date version of the Business Objects product documentation. You can browse the library contents, do full-text searches, read guides on line, and download PDF versions. The library is updated regularly with new content as it becomes available. To access the online documentation library, visit http://help.sap.com/ and click Business Objects at the top of the page.
Additional developer resources
https://boc.sdn.sap.com/developer/library/
Online customer support
The Business Objects Customer Support web site contains information about Customer Support programs and services. It also has links to a wide range of technical information including knowledgebase articles, downloads, and support forums. http://www.businessobjects.com/support/
Looking for the best deployment solution for your company?
Business Objects consultants can accompany you from the initial analysis stage to the delivery of your deployment project. Expertise is available in relational and multidimensional databases, in connectivities, database design tools, customized embedding technology, and more. For more information, contact your local sales office, or contact us at: http://www.businessobjects.com/services/consulting/
Looking for training options?
From traditional classroom learning to targeted e-learning seminars, we can offer a training package to suit your learning needs and preferred learning style. Find more information on the Business Objects Education web site: http://www.businessobjects.com/services/training
82
Do you have a suggestion on how we can improve our documentation? Is there something you particularly like or have found useful? Drop us a line, and we will do our best to ensure that your suggestion is included in the next release of our documentation: documentation@businessobjects.com
Note:
If your issue concerns a Business Objects product and not the documentation, please contact our Customer Support experts. For information about Customer Support visit: http://www.businessobjects.com/support/.
For information about the full range of Business Objects products, visit: http://www.businessobjects.com.
83
84
Index
A
analytics, upgrading 79 Apache Tomcat 5.5 configuration details 48 auditing database, configuring 42, 72 database requirements character encoding 25 CMS overview 25 DB2 28 Microsoft SQL Server 30 MySQL 30 Oracle 29 Sybase 30 database server preparations 31 database, CMS 27 DB2 27 configuring 42 deployment documentation 10 user permissions 23 Desktop Intelligence 74
B
BusinessObjects Enterprise documentation 10
C
CMS repository objects, updating 62 CMS data copying 58, 60 CMS database configuring 42 setting up on Windows 27 specifying 38, 41 complex upgrades 14, 56 content copying 57
E
environment database 27 events, updating 68
F
file repositories re-pointing 61 file repository data copying 61
D
dashboards, upgrading 79 data copying 57 database installing MySQL 26 preparing your existing 31
I
Import Wizard using 63 Input File Repository 61
85
Index
installation language packs 36 running 35 Tomcat 48 user information 36 Web Application Container Server (WACS) 52 web application option 46 installation directory specifying 39
R
repository objects, updating 62
S
Search Index program adding 64 Server Intelligence Agent 41 servers reconfiguring and adding 63 simple upgrades 14, 37 SQL Server configuring 42 Sybase 27 configuring 42 system requirements 23
L
language packs installation 36
M
metrics, refreshing 79 migrating from BusinessObjects 6.x 14 from BusinessObjects Enterprise 6.x 10, 18 from WebIntelligence 10 MySQL configuring 42 installing as database 26
T
Tomcat configuring 48
U
Unicode 27 uninstalling BusinessObjects Enterprise 52, 65 upgrade scenarios 18 upgrades complex 14, 56 simple 14, 34, 37 upgrading considerations 22 from BusinessObjects Enterprise 9, 14, 18 from Crystal Enterprise 9, 18 overview 14
O
Oracle 27 configuring 42 Oracle Application Server 10g R3 configuration details 48 Output File Repository 61
P
Performance Management Repository, upgrading 78, 79 preparing your database server 31
86
Index
W
wdeploy user permissions 23 Web Application Container Server installing 24 Web Application Container Server (WACS) 52 web application server choosing 24 configuration details 48
web application server (continued) user permissions required 23 WebLogic 10 configuration details 48 WebLogic 9 configuration details 48 WebSphere 6.1 configuration details 48 WebSphere Community Edition 2.0 configuration details 48
87
Index
88