Xi3-1 Bip Install Unix En

Installation Guide for UNIX

BusinessObjects Enterprise XI 3.1

unix

© 2009 SAP® BusinessObjects™. All rights reserved. SAP BusinessObjects andits logos, BusinessObjects, Crystal Reports®, SAP BusinessObjects Rapid Mart™,

Copyright

SAP BusinessObjects Data Insight™, SAP BusinessObjects Desktop Intelligence™,SAP BusinessObjects Rapid Marts®, SAP BusinessObjects Watchlist Security™,SAP BusinessObjects Web Intelligence®, and Xcelsius® are trademarks orregistered trademarks of Business Objects, an SAP company and/or affiliatedcompanies in the United States and/or other countries. SAP® is a registeredtrademark of SAP AG in Germany and/or other countries. All other namesmentioned herein may be trademarks of their respective owners.

2009-05-19

ContentsGetting Started 7Chapter 1

About this documentation............................................................................8Who should read this documentation .........................................................8BusinessObjects Enterprise guides.............................................................8What is BusinessObjects Enterprise?.......................................................10What's new in the BusinessObjects Enterprise Installation Guide? .........11

Preparing to Install BusinessObjects Enterprise 13Chapter 2

Installation overview..................................................................................14System requirements ..........................................................................15Network requirements .........................................................................16UNIX permissions.................................................................................16Setting up your UNIX system...............................................................17Setting up server communication.........................................................21

Installation types........................................................................................23New installation ...................................................................................23Custom or Expand installation .............................................................24Web Tier installation ............................................................................25

Installation modes......................................................................................26Silent installation .................................................................................26

Installing client tools only ..........................................................................26CMS Database requirements and preparation..........................................28

Using a supported database server.....................................................29Setting up an empty database for the CMS.........................................32

Preparing an existing database server......................................................45Before you deploy web applications..........................................................46

Installation Guide for UNIX 3

Before deploying to a Java web application server..............................46

Beginning the Installation of BusinessObjects Enterprise 47Chapter 3

Installation checklist...................................................................................48Installation overview..................................................................................49Setting up product distribution...................................................................49

Running the product distribution directly from a DVD..........................50Copying the product distribution to your machine................................50

Beginning your installation.........................................................................51To begin your installation......................................................................52To accept the license agreement.........................................................53To enter a product keycode..................................................................53To specify the installation directory.......................................................53To install language packs.....................................................................54To select user or system installation....................................................55To select an installation type................................................................55

New Installation 57Chapter 4

Performing a new installation.....................................................................58Selecting a new installation..................................................................58To configure the new CMS ..................................................................59To specify a system database option...................................................59To enter Server Intelligence Agent information....................................63To select a web application server configuration option.......................63To start the installation .........................................................................68

Finishing a system installation ..................................................................69

Custom or Expand Installation 71Chapter 5

Performing a custom or expand installation..............................................72To perform a Custom or Expand installation..............................................75

4 Installation Guide for UNIX

Contents

To install only the server components..................................................76Installing only the Web Tier Components.............................................82

Finishing a system installation ..................................................................90

Web Applications Installation 91Chapter 6

Performing web tier installations................................................................92Features available in a web tier installation ........................................92To perform a web tier installation .........................................................93To cluster web tier features to a CMS..................................................93To select a web application server configuration option.......................94To start the installation .........................................................................99Finishing a system installation ...........................................................100

Silent Installation 101Chapter 7

Overview..................................................................................................102Performing a scripted installation............................................................102

To create a response file....................................................................103Sample response file..........................................................................104To run a scripted installation...............................................................109Scripted installation parameters.........................................................110

Performing a silent installation.................................................................120

After Installing BusinessObjects Enterprise 129Chapter 8

Using ccm.sh to start the BusinessObjects Enterprise servers...............130To view additional help on ccm.sh......................................................130

To manually start and enable servers......................................................130To check if the CMS is running................................................................131Post install component deployment.........................................................131Setup for performance management ......................................................132

To set up performance management.................................................132


Contents

Troubleshooting starting performance management..........................132

Language Packs 135Chapter 9

About language packs ............................................................................136English language fall-back ................................................................136Product locale changes .....................................................................136Installing language with complex deployments .................................136

Installing language packs........................................................................137Locating language packs ...................................................................137To install language packs ..................................................................137Installing language packs across a BusinessObjects Enterprisedeployment ........................................................................................138

Selecting a language ..............................................................................140To uninstall language packs ...................................................................141

Maintaining your Installation 143Chapter 10

Adding performance management to your installation............................144To add performance management.....................................................144

The installation log file ............................................................................149Uninstalling BusinessObjects Enterprise from UNIX...............................149

To uninstall BusinessObjects Enterprise............................................150

More Information 151Appendix A

Index 155


Contents

Getting Started

1

About this documentationThis documentation provides information, procedures, and options forinstalling, removing, and repairing BusinessObjects Enterprise, client tools,and language packs. Two versions of this guide exist:• BusinessObjects Enterprise Installation Guide for Windows: for use with

Microsoft Windows operating systems.• BusinessObjects Enterprise Installation Guide for UNIX: for use with UNIX

and Linux operating systems.

Note:Information related to the post-installation deployment of WAR files to a Javaweb application server is now covered by the BusinessObjects EnterpriseWeb Application Deployment Guide.

Who should read this documentationThis documentation is intended for the system administrator who needs toinstall BusinessObjects Enterprise on a UNIX or Linux operating system.Familiarity with your overall network environment, port usage conventions,database environment, and web server software is essential.

Note:If you are installing BusinessObjects Enterprise on a Microsoft Windowsoperating system, please read the BusinessObjects Enterprise InstallationGuide for Windows.

BusinessObjects Enterprise guidesThe following table provides a list of BusinessObjects Enterprise guides andtheir contents.


Getting Started1 About this documentation

DescriptionGuide

Covers the key concepts you should con-sider before you begin deploying Busines-sObjects Enterprise. This guide includesan overview of the architecture, tips for as-sessing your existing environment, deter-mining your organization's needs, andpreparing for the installation.

BusinessObjects EnterprisePlanning Guide

Leads you through the steps required torun the setup program and complete yourinstallation of BusinessObjects Enterprise.There are UNIX and Windows versions ofthis guide available.

BusinessObjects EnterpriseInstallation Guide

Covers topics related to the deployment ofweb applications to web application serverswith BusinessObjects Enterprise. There areUNIX and Windows versions of this guideavailable.

BusinessObjects EnterpriseWeb Application DeploymentGuide

Provides content for server and contentadministration. The server administrationtopics includes server configuration, man-aging authentication, configuring firewalls,and measuring system performance. Thecontent administration topics include work-ing with the CMC, configuring rights andaccess levels, managing users, and work-ing with Business Objects applications andobjects.

BusinessObjects EnterpriseAdministrator's Guide


1Getting StartedBusinessObjects Enterprise guides

DescriptionGuide

Provides an overview of the publishingprocess, working with publications, publish-ing Crystal reports, publishing Web Intelli-gence documents, publishing Desktop In-telligence documents, and publishing secu-rity.

BusinessObjects EnterprisePublisher's Guide

Details content migration from legacyBusiness Objects software, such as Classicor Enterprise 5 or 6, to BusinessObjectsEnterprise XI 3.1.

BusinessObjects 5/6 to XI 3.1Migration Guide

Information for upgrades from BusinessOb-jects Enterprise XI to BusinessObjects En-terprise XI 3.1.

BusinessObjects EnterpriseUpgrade Guide

Provides an overview of InfoView andworking with Crystal Reports, Web Intelli-gence, objects, discussions, encyclopedia,and Voyager workspaces.

BusinessObjects EnterpriseInfoView User's Guide

For a complete list of all of our product documentation please visit:http://support.businessobjects.com/documentation/product_guides/default.asp

What is BusinessObjects Enterprise?BusinessObjects Enterprise is a flexible, scalable, and reliable businessintelligence reporting system that can be tightly integrated into yourinformation technology infrastructure. Support for many industry-standarddatabase systems makes it easier to access your organization's data foranalysis. The use of common industry standards for security allow you touse your existing authentication systems to control access to BusinessObjectsEnterprise. And broad platform support allows you to install BusinessObjectsEnterprise on the operating systems and hardware architecture that youprefer.


Getting Started1 What is BusinessObjects Enterprise?

http://support.businessobjects.com/documentation/product_guides/default.asp

As a system administrator, you will be faced with many choices when installingBusinessObjects Enterprise. This documentation helps you to make the rightdecisions to create a reliable and powerful business intelligence reportingsystem for your organization.

What's new in the BusinessObjectsEnterprise Installation Guide?

The installation and deployment documentation from previous releases ofBusinessObjects Enterprise has been split into separate installation and webapplication deployment guides:• For information related to the installation of BusinessObjects Enterprise,

see the BusinessObjects Enterprise Installation Guide (this guide).• For information related to the post-installation deployment of web

applications, see the BusinessObjects Enterprise Web ApplicationDeployment Guide.

This document is the first to include information on the following features forBusinessObjects Enterprise:

DescriptionFeature

The use of the Microsoft Internet Information Services (IIS)web application server version 6 or 7 is now supported onWindows-based BusinessObjects Enterprise servers.

IIS support

The deployment of ASP.NET web applications is now sup-ported on Microsoft operating systems running the IIS webapplication server. The BusinessObjects Enterprise setupprogram can automatically deploy .NET support and a .NETversion of InfoView during installation.

.NET support

A new Web Application Container Server (WACS) allowsyou to run the Central Management Console (CMC) onWindows machines without the need to install Java.

WACS

IP version 6 (IPv6) addresses can now be used anywherein BusinessObjects Enterprise.

IPv6 support

The response file information has been updated.Response files


1Getting StartedWhat's new in the BusinessObjects Enterprise Installation Guide?

DescriptionFeature

A new .NET-based version of the InfoView application isnow supported.

.NET InfoView

The wdeploy tool now supports the deployment of web ap-plications to:• JBoss• WebSphere Community Edition• Sun Java One (UNIX only)

Web applicationservers

BusinessObjects Enterprise is now supported on the follow-ing operating systems:• HP-UX IA-64• Redhat 5

Operating systems

Business Objects product documentation is available in supported languagesfrom the support web site, and is refreshed with up-to-date content as itbecomes available between releases. For the most recent productdocumentation, visit http://support.businessobjects.com/documentation/.


Getting Started1 What's new in the BusinessObjects Enterprise Installation Guide?

http://support.businessobjects.com/documentation/

Preparing to InstallBusinessObjects Enterprise

2

Installation overviewBefore you install BusinessObjects Enterprise, you should:

• Consult the BusinessObjects Enterprise Planning Guide to gain a generalunderstanding of the installation process and the different optionsavailable.

• Review your systems to ensure that it meets the basic requirements fora BusinessObjects Enterprise installation. See System requirements.

• Ensure that all machines that will be part of your BusinessObjectsEnterprise deployment can communicate with one another across yournetwork. See Network requirements.

• Decide which BusinessObjects Enterprise components to install, andwhich of your own components to integrate. For more information ondetermining your needs and planning requirements, consult theBusinessObjects Enterprise Planning Guide.

Note:If you are upgrading from an earlier version of BusinessObjects Enterprise,ensure that all components are at the same patch level before startingthe system. If the components are at different patch levels, somecomponents may encounter communication problems.

• Determine the location of the components to be installed. This includesthe specific subnet, machine, database, security, or cluster systems thatwill be used to run your system.

• Decide which installation method to use.

The following sections list the core software requirements, the choicesavailable to you within the core requirements, and the installation methodsthat you can use when you install BusinessObjects Enterprise.

An installation checklist is provided to help ensure you are prepared beforeyou begin your installation of BusinessObjects Enterprise.

Related Topics• Installation checklist on page 48• Installation overview on page 14• System requirements on page 15• Network requirements on page 16


Preparing to Install BusinessObjects Enterprise2 Installation overview

System requirements

For a detailed list of supported environments and hardware requirements,consult the Products Availability Report (PAR) document available on theBusiness Objects support site http://support.businessobjects.com/documentation/supported_platforms. This document includes specific version andpatch-level requirements for web application servers, web browsers, andoperating systems. For information related to the planning of aBusinessObjects Enterprise deployment, consult the BusinessObjectsEnterprise Planning Guide.

BusinessObjects Enterprise ships with the Tomcat web application serverand MySQL database server. If you are planning to use a different webapplication or database server, it must be installed and configured beforeBusinessObjects Enterprise.

Related Topics• CMS Database requirements and preparation on page 28

Installing BusinessObjects Enterprise on a HPUX 64-bit system

If you are installing BusinessObjects Enterprise on a HPUX Itanium 64-bitoperating system, you must use a Tomcat 5.5 as the application server. Noother web application servers are supported.

Tomcat 5.5 is provided with the BusinessObjects Enterprise installationpackage. You can install Tomcat when you install BusinessObjects Enterprise,or you can specify an existing Tomcat server during the installation process.

The BusinessObjects Enterprise Java components require the HP 64-bitrelease of the JDK/JRE. To run the Java Virtual Machine in 64-bit mode, youmust use the -d64 option. For more information, seehttp://docs.hp.com/en/JAVAPROGUIDE/hotspot.html#-d64

Note:

If you encounter difficulty in installing BusinessObjects Enterprise on HPUX64-bit systems, see SAPNote 1311735 - Install problem on HP-UX IA64 at:https://bcp.wdf.sap.corp/sap/sapnotes/display/1311735.


2Preparing to Install BusinessObjects EnterpriseInstallation overview

http://support.businessobjects.com/documentation/supported_platforms/


http://docs.hp.com/en/JAVAPROGUIDE/hotspot.html#-d64

https://bcp.wdf.sap.corp/sap/sapnotes/display/1311735

The following BusinessObjects Enterprise products and components will notrun on an HPUX Itanium 64-bit system platform:• Business View Manager• Polestar• Desktop Intelligence• Predictive Analysis• Multi-Dimensional Analysis Services

Network requirements

When installing BusinessObjects Enterprise on multiple machines, ensurethat each machine can communicate over TCP/IP with the machine runningthe Central Management Server (CMS), and all other machines in thedeployment. A dedicated web server must be able to communicate with theweb application server. All web desktop clients must be able to access theweb server. For more information on the communication between componentsplease refer to the Architecture chapter in the BusinessObjects EnterprisePlanning Guide.

Note:

• If you are installing BusinessObjects Enterprise in a firewalledenvironment, see the Working with Firewalls chapter of theBusinessObjects Enterprise Administrator's Guide.

• If you are installing on a VMware virtual machine, ensure the machinename does not include underscore (_), period (.), or slash (/ or \)characters.

UNIX permissions

To perform either a user or system installation on UNIX, the user accountunder which the install is run must have read, write, and execute permissionsto the directory where BusinessObjects Enterprise will be installed.

However, if you run a system installation, you do require root authority to runthe system-level initialization script. This script, which is called setupinit.sh,is run after the installation completes. This script creates entries into the runcontrol scripts for the operating system that start up the BusinessObjects



Enterprise servers when the UNIX server is brought up, and stops the serverswhen a machine is shut down.

The following table summarizes all the required permissions for installingBusinessObjects Enterprise.

Required permissionsCategory

Read, write, and execute permissions to the directory whereBusinessObjects Enterprise will be installed. Root access ifperforming a system installation.

OperatingSystem

Access to all machines via TCP/IP - all specified ports must beavailable.

Network

Rights to add and drop tables to or from the database, plusrights to read, write, and edit table rows.

Database

Setting up your UNIX system

BusinessObjects Enterprise integrates with your existing database and webserver software components, so the installation script needs to collect certaininformation about your current system. Because UNIX systems can varysignificantly from site to site, the following sections detail the key tasks thatyou must perform prior to installing BusinessObjects Enterprise.

Setting the locale

Before you install BusinessObjects Enterprise, set your operating system touse one of the locales that BusinessObjects Enterprise supports for yourversion of UNIX. For a detailed list of supported UNIX environments see theProduct Availability Report available from the following Business Objectssupport site: http://support.businessobjects.com/documentation/supported_platforms/.

Note:You should also ensure that the character set translation on your terminalis set to UTF-8.





If you are working through the console of a UNIX machine, you can selectyour locale directly from the logon screen when you log on with the accountfrom which you will install BusinessObjects Enterprise. However, to ensurethat your operating system uses the correct locale whenever BusinessObjectsEnterprise runs, set the LC_ALL and LANG environment variables to yourpreferred locale in your login environment. (For example, if you are using aC shell, set these environment variables in the .login file).

Tip:Type locale to check that all of the related locale environment variables(such as LC_MONETARY, LC_NUMERIC, etc.) were properly set by LC_ALL.

See the section on International Deployments in the BusinessObjectsEnterprise Administrator's Guide for information on deploying BusinessObjectsEnterprise for a multilingual, world-wide audience.

Checking for required commands and utilities

In order for the install setup program to run correctly, the followingcommands and utilities must be installed on your UNIX system:

touchreadpwd/bin/sh

sedhostnameexpruname

tailgrepchownawk

gzipdirnameidtar

whichulimitstty

These relatively standard commands and utilities should be available onmost UNIX distributions. However, if for any reason one of them is notavailable on your system, download and install a version appropriate to yourUNIX system. It is recommended that you obtain any required files from yourUNIX vendor.



Additionally, these commands and utilities must be accessible in the PATHenvironment variable of the user account that you use when installingBusinessObjects Enterprise. For details, see Creating an account, a homedirectory, and a login environment.

Related Topics• Creating an account, a home directory, and a login environment on

page 19

Creating an account, a home directory, and a login environment

Create a specific user account and group under which the BusinessObjectsEnterprise background processes can run. You will log on as this user inorder to perform the remainder of the installation procedures. Although youwill require root privileges to set up this account, the account itself does notrequire root privileges. Neither the installation scripts nor BusinessObjectsEnterprise itself needs to run as root.

Use your usual administrative procedures to perform these recommendedtasks.

To set up an account for installing BusinessObjects Enterprise1. Create a new group or use an existing group. Create a new user account,

and set this user's primary group to the new group. Assign a securepassword to the new user account.

2. Create the directory where you want to install BusinessObjects Enterprise.

By default, the installation will use your current directory as its basedirectory for the install, that is, the directory where you run install.sh. Youcan override this default, with the directory of your choice at install time.You will see the directory that you specify for the installation directoryreferred to as INSTALLDIR throughout this document.

3. Ensure that the account you created has read, write, and executepermissions on the new installation directory.

4. Assign the new user a default login shell, and create or modify theappropriate login script(s) for the user account. In particular, make surethat the login script(s) set up a default login environment that meets theserequirements:• All of the commands and utilities required by the install setup

program must be accessible in the PATH environment variable.



• The user's login environment must set up the database environmentsuch that the install setup program can access your database clientsoftware.

• The user's login environment must set up a default locale that issupported by your UNIX system and BusinessObjects Enterprise.

Related Topics• Checking for required commands and utilities on page 18• Setting the locale on page 17

Meeting the host name and network requirements

Your UNIX server must have a fixed host name before you run the installationscript. You must have root privileges to set or modify this information on yoursystem. If you are unfamiliar with these procedures, consult your UNIX systemdocumentation.

When installing BusinessObjects Enterprise on multiple machines, ensurethat each target machine is able to communicate over TCP/IP with themachine that is running as your Central Management Server (CMS).

Note:If you are installing BusinessObjects Enterprise in a firewall environment,you will need additional configuration details. See the "Working with Firewalls"section of the BusinessObjects Enterprise Web Application DeploymentGuide.

Difference between user and system installation

When you perform a new installation, on UNIX, you can choose between auser and a system installation.

• When you choose a user installation, all the required components areinstalled.

• When you choose a system installation, all the required components areinstalled, In addition, the installation creates a system-level initiation script.This script creates entries into the run control scripts for the operatingsystem that start up the BusinessObjects Enterprise servers when the



UNIX server is brought up and stops the BusinessObjects Enterpriseservers when a machine is shut down.

Note:To perform a system installation, you do not require root-level authority.However, to run the system-level initiation script root-level authority isrequired.

Setting up server communication

BusinessObjects Enterprise requires a database server and web applicationserver software to be installed and configured if you want to use an existingdatabase or web application server. You can also choose to install a databaseserver (MySQL) and a Web application server (Apache Tomcat 5.5) duringyour installation of BusinessObjects Enterprise.

You must ensure that all BusinessObjects Enterprise machines cancommunicate properly with one another:

• Each BusinessObjects Enterprise machine must be able to communicateover TCP/IP with the machine that runs your Central Management Server(CMS). The CMS is responsible for maintaining a database of informationabout your BusinessObjects Enterprise system, which other componentscan access as required. The data stored by the CMS includes informationabout users and groups, security levels, BusinessObjects Enterprisecontent, and servers. For more information about the CMS, see the“Managing and Configuring Servers” chapter in the BusinessObjectsEnterprise Administrator’s Guide.

• If the host machine has more than one network interface card (NIC), theCMS may automatically bind to a primary NIC. If the primary NIC is notroutable, you may have to reconfigure your servers after installation.Alternatively, you could make the primary NIC routable before installingBusinessObjects Enterprise. For more information on how to reconfigureto bind to routable NICs see the “Managing and Configuring Servers”chapter in the BusinessObjects Enterprise Administrator’s Guide.

• UNIX servers that run BusinessObjects Enterprise must have a fixed hostname. You must have root privileges to set or modify a fixed host nameon your system. However, you do not require root privileges to performa user installation of BusinessObjects Enterprise. If you are unfamiliarwith these procedures, consult your UNIX system documentation.



Note:Please ensure that the host name you use does not include any of thefollowing characters: an underscore, a period, or a slash.

• Ensure that your database client and server are set up to use Unicodecharacter encoding (such as UTF-8). Consult your databasedocumentation to determine the settings required for a Unicodeconfiguration.

• If you connect BusinessObjects Enterprise to a web application server,the web application server must be able to communicate with allBusinessObjects Enterprise machines. This communication is enabledby the BusinessObjects Enterprise Software Development Kit (SDK),which is installed as part of the Web Tier Components. If you plan to usea Java application server and your existing application server does notinclude a version of the Java Development Kit (JDK) supported byBusinessObjects Enterprise, you will need to install it.

• If you are installing BusinessObjects Enterprise in a firewall environment,you will need additional configuration details. See the “Working withFirewalls” section of the BusinessObjects Enterprise Administrator’sGuide.

Choosing a server location

When planning your BusinessObjects Enterprise installation, you should alsoconsider where you will place your deployment’s servers.

Your Crystal Reports Page Server, Desktop Intelligence Report Server,Connection Server, Web Intelligence Report Server, Job Servers, and ReportApplication Server communicate frequently with the database serverscontaining the data in your published reports. To optimize data retrieval andminimize network traffic, place your processing servers close to your databaseservers (ideally, on the same subnet).

If your BusinessObjects Enterprise installation is distributed over a widegeographic region, use server groups to create groups of nearby servers toprocess reports. The Central Management Server (CMS) stores data aboutusers and groups, security levels, published objects, and servers in the CMSdatabase. The CMS can also maintain a separate audit database ofinformation about user actions. To optimize CMS performance, place yourCMS on the same LAN as the database servers that host your CMS databaseand the BusinessObjects Enterprise audit database. The CMS can beclustered. If you are deploying more than one CMS, ensure each machine



that runs a CMS process experiences the same latency to the systemdatabase.

Consult the “Managing and Configuring Servers” section of theBusinessObjects Enterprise Administrator's Guide for information on otherfactors that you may want to consider in planning your BusinessObjectsEnterprise installation.

Installation typesWhen you install BusinessObjects Enterprise, you can choose one of thefollowing installation types. Consider which of these types is your best suitedfor your intended deployment:• "New": Installs all components on one machine.

Select this installation type to quickly set up a complete deployment, withall server and client components on a single machine.

• "Custom or Expand": Installs the components that you select on themachine.

Select this installation type to specify which components to install whenperforming a distributed deployment, or when adding servers to an existingdeployment.

• "Web Tier": Installs only the used by a web application server to run webapplications.

Select this installation type to set up Java or .NET web applicationcomponents when performing a distributed deployment.

For information on performing installation upgrades, see the BusinessObjectsEnterprise Upgrade Guide.

"New" installation

Installing a "New" installation puts all of the required client, server, andoptional components onto one machine. This configuration can be useful forsmall, trial, or tested installations. Components can be disabled after theinstallation if they are not required.


2Preparing to Install BusinessObjects EnterpriseInstallation types

You may want to choose a "New" installation if:

• This is the first time that you've installed BusinessObjects Enterprise, andyou are unsure of which components to install.

• You want to install all the components on the same machine.

"Custom or Expand" installation

The "Custom or Expand" installation option allows you to select individualcomponents. It is recommended that you run this type of installation onlyafter you are familiar with specific BusinessObjects Enterprise componentsand their roles, otherwise you may inadvertently fail to install a requiredcomponent.

You should perform a "Custom or Expand" installation if you plan to useBusinessObjects Enterprise in a distributed environment. For example, in adistributed deployment you can install the BusinessObjects EnterpriseDesktop Intelligence server components on one machine, and use anothermachine to host Crystal Reports server components.

After setting up one BusinessObjects Enterprise server, you can run a"Custom or Expand" installation on a second machine to add servercomponents, create a CMS cluster, increase available resources, anddistribute the processing workload over both machines.

The "Custom or Expand" install features consist of:• Client Components• Web Tier Components• Server Components• Database Access• Export Support• Samples• Help Files

You may choose to install all, some, or parts of the above components.

Tip:Consult the “Scaling Your System” section of the BusinessObjects EnterpriseAdministrator's Guide for information on planning how to best expand yourinstallation to meet the needs of your organization. In addition, consult the


Preparing to Install BusinessObjects Enterprise2 Installation types

BusinessObjects Enterprise Planning Guide for general scalabilityconsiderations, sample configurations, and information about CMS clustering.

You may want to choose a "Custom or Expand" installation if:

• You have already completed your initial installation of BusinessObjectsEnterprise and would like to deploy additional components to anothermachine.

• Your deployment of BusinessObjects Enterprise will be distributed acrossmultiple computers.

• You have resource limitations and need to consider disk space constraints.

"Web Tier" installation

The "Web Tier" option installs all of components used by the web applicationserver to run BusinessObjects Enterprise web applications. Thesecomponents include:

DescriptionComponent

Used to run BusinessObjects Enterprise applications,including the Central Management Console (CMC),InfoView, and Dashboard and Analytics.

BI Platform Web Compo-nents

An implementation of web services that provides anAPI/WSDL to simplify the process of developing webapplications.

BusinessObjects Enter-prise Web Services

An open-source, standards-based, Java web applica-tion server. If you do not have an existing web appli-cation server, you can choose to install ApacheTomcat 5.5.

Tomcat

You may want to choose a "Web Tier" installation if:

• If you want to install the web applications separately from the servercomponents.

• You completed your initial installation of BusinessObjects Enterprise, andyou want to configure an additional web application server on a separatemachine.


2Preparing to Install BusinessObjects EnterpriseInstallation types

Installation modesThere are two methods that you can use to install BusinessObjects Enterprise:• Running the installation setup program.

The installation set up program provides a number of screens that allowto select an installation type, specify the details for your CMS database,and to deploy web applications to a supported application server.

• Running a silent or scripted installation.

A silent or scripted installation uses configuration information that hasbeen stored in a .ini response file during a previous command-lineinstallation of BusinessObjects Enterprise. This method is useful whenyou need to perform multiple installations, or you want to install withoutthe setup program prompting for configuration information.

Silent installation

A silent installation uses configuration information that has been stored in a.ini response file during a previous command-line installation ofBusinessObjects Enterprise. This method is useful when you need to performmultiple installations, or you want to install without the setup programprompting for configuration information.

You can also incorporate the silent installation command into your own buildscripts. For example, if your organization uses scripts to install software onmachines, you can add the silent BusinessObjects Enterprise installationcommand to those scripts.

You may want to choose a silent installation if:

• You need an automated method for performing identical or similarinstallations on several machines.

• You do not want to run the BusinessObjects Enterprise setup program.

Installing client tools onlyThe client tools are applications that can only be installed on Windows, withthe Windows Client Tools installation package.


Preparing to Install BusinessObjects Enterprise2 Installation modes

If you install the BusinessObjects Enterprise servers on a UNIX machine,you can connect remotely to BusinessObjects Enterprise with the client toolsinstalled on a Windows machine.

The available tools are:

DescriptionClient tool

An integrated query, reporting, and analysis toolto access your organization's data for presenta-tion and analysis in a Desktop Intelligencedocument.

Desktop Intelligence

Provides business users an interactive andflexible interface for building and analyzing re-ports from your organization's data over theweb, through a secured intra- or extranet.

Web Intelligence Rich Client

Migrates reports based on Crystal queries, dic-tionaries, or InfoViews to BusinessObjects En-terprise.

Data Source Migration Wizard

Provides relational views of information forcreating and modifying Data Connections, Dy-namic Data Connections, Data Foundations,Business Elements, or Business Views.

Business View Manager

Converts Desktop Intelligence reports (.repfiles) to Web Intelligence (.wid) format. Con-verted files can then be published to the CentralManagement Server (CMS).

Report Conversion Tool

Imports user, group, object, or folder contentfrom previous and current Crystal or Busines-sObjects Enterprise deployments.

Import Wizard

Publishes and sets properties for multiple re-ports in BusinessObjects Enterprise.

Publishing Wizard

Creates custom web services for specificqueries using Business Objects Web Services.

Query as a Web Service


2Preparing to Install BusinessObjects EnterpriseInstalling client tools only

DescriptionClient tool

Creates universe connections for Web Intelli-gence and Desktop Intelligence documents.

Universe Designer

Software Development Kits (SDK) with wizardsand templates for integrating BusinessObjectsEnterprise functionality into your interactive webapplications:• BusinessObjects Enterprise .NET SDK.• BusinessObjects Enterprise Java SDK.• BusinessObjects Enterprise Web Services

SDK.

Developer Components

Defines translations for multilingual documentsand prompts. Supports Universe Designer uni-verses and Web Intelligence documents.

Translation Manager

Install these applications for users responsible for managing BusinessObjectsEnterprise content, developing applications, or importing system data. Clienttools are not needed by users who access InfoView or the CMC administrativeweb applications.

Note:The BusinessObjects Enterprise Client Tool Setup program does not generallyrequire a license key to activate the product. However, Desktop Intelligencedoes require that a license key be entered in the CMC after the installation.

CMS Database requirements andpreparation

BusinessObjects Enterprise requires a database to store Central ManagementServer (CMS) information about the system and its users. This database isreferred to as the CMS, or system, database.

The following sections detail required settings and how to test settings for:

• DB2

• MySQL

•


Preparing to Install BusinessObjects Enterprise2 CMS Database requirements and preparation

• Oracle

• Sybase

Before installing BusinessObjects Enterprise, review this information in orderto properly prepare your CMS system and auditing database. For moreinformation on database requirements, refer to the “Databases inBusinessObjects Enterprise” section in the BusinessObjects EnterprisePlanning Guide.

Note:Regardless of database type, the database must be setup to use Unicodecharacter encoding, such as UTF-8.

Using a supported database server

The CMS supports a number of third-party database servers, so you canconnect BusinessObjects Enterprise to your existing database infrastructure.For a detailed list of supported database servers see the Product AvailabilityReport PDF available from the Business Objects support site. If you do nothave a database installed on your machine you choose to install and configureMySQL as your CMS database through the BusinessObjects Enterpriseinstallation setup program.

UsingMySQL as the Central Management Server (CMS) database

MySQL is an open-source database included with BusinessObjects Enterprisethat can be automatically installed and configured for use as the CentralManagement Server (CMS), or system, database.

If you want to use an existing supported database server, you can enterconnection and authentication parameters during the BusinessObjectsEnterprise installation process.

Sourcing the script that identifies the database environmentvariables

If you are using an existing database, you need a method to connect to itfrom within BusinessObjects Enterprise. This is done through your database


2Preparing to Install BusinessObjects EnterpriseCMS Database requirements and preparation

client. In this document, the terminology used for this operation is to sourcethe script that identifies the database environment variables.

If you are integrating BusinessObjects Enterprise with a different webapplication server than the version of Tomcat that can be configured withyour installation, you may need to source the environment script. This willset up the required variables for BusinessObjects Enterprise.

Technically, sourcing your environment script involves running a script inyour current environment. When your database client is sourced from withinBusinessObjects Enterprise, all the required environment variables for yourdatabase are set up and exported.

Your database client or the BusinessObjects Enterprise environment scriptcan be sourced from the command line, entered into a profile, or enteredinto another script.

• To source your database client from the command line, you would executethe script that sets up the variables required by your database client toaccess your database. For example, in the bash shell, you could typethis:

source ora10env.sh

• To source the BusinessObjects Enterprise environment script, you wouldexecute the script that sets up the variables required. For example, youcould add this to the Tomcat setenv.sh or the WebSphere startup script:

source "<INSTALLDIR>/bobje/setup/env.sh"

Note that the syntax used to source a script varies based on the type of shellyou are using. Some UNIX shells use source as the syntax for this operation;some UNIX shells use the .(dot operator). Please consult thedocumentation for your shell to determine the appropriate syntax.

. (dot operator)sourceShell name

yesnoBourne shell (sh)

yesnoKorn shell (ksh)



. (dot operator)sourceShell name

yesyesBourne Again Shell(bash)

noyesC shell (csh)

noyesTurbo C shell (tcsh)

To setup a database account for BusinessObjects Enterprise

The Central Management Server (CMS) uses a database to store systeminformation. If you choose to install MySQL as part of your BusinessObjectsEnterprise installation, a MySQL CMS database will be created for you. Ifyou plan to use your own database, you should complete the steps listedbelow before installing BusinessObjects Enterprise.

To create tables and write data to your new CMS database, the installationprogram needs to establish a connection to the database server. When youlog on to the account being used to install BusinessObjects Enterprise, theenvironment must include the appropriate variables and database drivers toaccess your chosen database. Only then can the installation program accessthe CMS database using your database client software.

1. Create or select a user account that provides BusinessObjects Enterprisewith the appropriate privileges to your database server.

2. Verify that you can log on to your database and that you have rights toadd or remove database tables and to add, delete, or edit table rows withthe user account.



Setting up an empty database for the CMS

If you want to use an existing database server as the Central ManagementServer (CMS) or auditing database, you must create a new tablespace ordatabase before installing BusinessObjects Enterprise.

The installer will prompt for the connection and authentication details if youchoose to use your own database during the installation of BusinessObjectsEnterprise. The following database servers are supported for the CMS systemand audit databases:

•• Oracle

• DB2

• MySQL

• Sybase

Note:Review the online BusinessObjects Enterprise supported platforms documentfor information related to supported database software and versionrequirements:http://support.businessobjects.com/documentation/.

To integrate your existing database with BusinessObjects Enterprise, youneed to prepare it. Here is a summary of the steps to prepare your database:

• Create a new tablespace, schema, or database (the exact terminologywill depend on the database platform you're using) to act as the CMSdatabase. Create a second for the auditing database, if you plan to enableauditing.

• Create a new user account and password to be used by BusinessObjectsEnterprise to access the CMS database. Create a second username andpassword 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 canbe modified as required.

• Record the name of the database(s), the user account(s), and thepassword(s) you created, so you can enter the details when you run theBusinessObjects Enterprise installer.



http://support.businessobjects.com/documentation/

During the installation, you can choose to reinitialize the existing database.This will cause new tables to be created in your existing database. Consultyour specific database server documentation if you are unsure of theprocedure for creating a new tablespace, schema, or database. Ensure thatyour database server is set up to use Unicode character encoding (such asUTF-8).

Note:If you have a previous release of BusinessObjects Enterprise you cannotuse your database from a previous release for BusinessObjects Enterprise.You must create a new database, or existing data from the previous releasewill be destroyed. To migrate from an previous release, create a newdatabase migrate your old content to the new current version's databaseafter the installation is complete.

DB2 database requirements

If you are using DB2 for the Central Management Console (CMC) or auditingdatabase:• Ensure that the CMS database is not partitioned.

Note: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 Sequencesetting, the user and usergroup objects may not sort properly in the CMC.

Replace XX with the code that is appropriate for your location. Consultyour DB2 documentation for more information.

• If you are using DB2 8.1, you require a C compiler that is installed andconfigured to build SQL stored procedures. DB2 8.2 through version 9.1do not have this requirement. Stored procedures are used byBusinessObjects Enterprise when users are added to groups. Pleaseconsult the DB2 documentation for details on how to configure the Ccompiler for SQL stored procedures.



Once the database is created, you will need to prepare it for theBusinessObjects Enterprise installation.

Related Topics• Preparing an existing database server on page 45

Testing DB2 environment variablesIf you choose to connect to DB2 through a native connection, the installationsearches the current shell for the DB2INSTANCE environment variable. Thisstandard DB2 environment variable must be set in order for the installscript to utilize the DB2 client software.

If you are using an existing database, you need to source your databaseclient.

Sourcing the script that identifies the database environment variables canbe done in one of two ways:

• The user who performs a system installation can modify theBusinessObjects Enterprise script setupint.sh to add the command tosource your database client. However, root access is required to executethis script. This script can be found at the following location: <installdir>/bobje/init/setupint.sh. This method will source the database for allusers. for information.

• Each person with a user installation can modify their profile and add thecommand to source their database environment. This method can bedone anytime.

For example, if an DB2 database was required, an entry would be madein the user profile to source the environment script used by DB2(db2profile). Consult your database documentation for the name of itsenvironment script.

Note:Instead of sourcing the script that identifies the database environmentvariables, you can manually set the environment variables required by yourdatabase. However, if you manually set the environment variables, you willneed to set them again if the system is restarted.

Consult your database documentation and/or your database administratorif the account shell environment from which you will install BusinessObjectsEnterprise has not yet been set up for your database client software, or ifyou are unable to connect successfully to the database.



The following steps will test whether the required environment variables areset.

Related Topics• Sourcing the script that identifies the database environment variables on

page 29

To verify DB2 native connectivity through a database alias1. Log on to the UNIX server with the user account and password which

you will use to do your install.

Note:This account should already be set up. See Creating an account, a homedirectory, and a login environment for more information on setting up aUNIX account to use when you install BusinessObjects Enterprise.

2. Echo the following environment variables and ensure that their valuescorrespond to your database client software installation.

ValueVariable

This variable defines the currentDB2 database instance.DB2INSTANCE

This variable contains the path tothe root directory of your DB2 clientinstallation

INSTHOME

This variable contains the path tothe root directory of your DB2 instal-lation (one level above the DB2 binand lib directories).

DB2DIR



ValueVariable

The library search path (LD_LIBRARY_PATH on Solaris and Linux,LIBPATH on AIX, and SHLIB_PATHon HPUX) must include the lib di-rectory of your DB2 client installa-tion.

library path

The search path must include thebin directory of your DB2 client in-stallation.

PATH

This example checks the required variables and shows sample outputvalues.

$ echo $DB2INSTANCEdb2inst1$ echo $DB2DIR/opt/IBMdb2/V7.1$ echo $LD_LIBRARY_PATH/export/home/db2inst1/sqllib/lib$ echo $PATH/usr/bin:/usr/ucb:/etc:.:/export/home/db2inst1/sqllib/adm:/export/home/db2inst1/sqllib/misc

3. Issue the following command to run the DB2 SQL tool:

db2

4. Issue the following command to connect to the desired database alias:

connect to db_alias user accountname using password

Replace db_alias and password with the appropriate values. If the shellenvironment has been configured correctly, you are connected to DB2.



5. Issue the following command to ensure that the account has permissionto create tables:

create table sampletable (col_fld char(10) not null)

6. Issue the following command to ensure that the account has permissionto delete tables:

drop table sampletable

7. Type terminate


page 19

Oracle database requirements

If you are using Oracle for the CMS or auditing database:• Use a Unicode character set, such as UTF-8.



Testing Oracle environment variablesIf you choose to connect to Oracle through a native connection, the installationsearches the current shell for the ORACLE_HOME environment variable. Thisstandard Oracle environment variable must be set in order for the installscript to utilize the Oracle client software.

If you are using an existing database, you need to source your databaseclient.

Sourcing your database client can be done in one of two ways:

• The user who performs a system installation can modify theBusinessObjects Enterprise script setupint.sh to add the command tosource your database client. However, root access is required to executethis script. This script can be found at the following location: <install



dir>/bobje/init/setupint.sh. This method will source the database for allusers.


For example, if an Oracle database was required, an entry would be madein the user profile to source the environment script used by Oracle(oraXXenv.csh or oraXXenv.sh where XX is replaced with the versionnumber). Consult your database documentation for the name of itsenvironment script.

Note:

• Instead of sourcing the script that identifies the database environmentvariables, you can manually set the environment variables required byyour database. However, if you manually set the environment variables,you will need to set them again if the system is restarted.

• Consult your database documentation and/or your database administratorif the account shell environment from which you will installBusinessObjects Enterprise has not yet been set up for your databaseclient software, or if you are unable to connect successfully to thedatabase.


page 29

To verify Oracle native connectivity through a TNS1. Log on to the UNIX server with the user account and password which






ValueVariable

This variable contains the path tothe root directory of your Oracleclient installation (one level abovethe Oracle bin and lib directories).

ORACLE_HOME

The library search path (LD_LIBRARY_PATH on Solaris and Linux,LIBPATH on AIX, and SHLIB_PATHon HPUX(PA-RISC)) must includethe lib32 directory of your Oracleclient installation.

On HPUX(IA-64), the library searchpath must include the lib directoryof your 64-bit Oracle client installa-tion.

library path

The search path must include thebin directory of your Oracle clientinstallation.

PATH

This example checks the required variables and shows sample outputvalues.

$ echo $ORACLE_HOME/home/dbclient/oracle/10.1.0.3$ echo $LD_LIBRARY_PATH/home/dbclient/oracle/10.1.0.3/lib32$ echo $PATH/usr/local/bin:/home/dbclient/oracle/10.1.0.3/bin

3. Issue the following command to run the Oracle SQL tool and connect tothe appropriate service name:

sqlplus accountname/password@tnsname



Replace accountname, password and tnsname with the appropriatevalues. If the shell environment has been configured correctly, you areconnected to Oracle.

4. Issue the following command to ensure that account has permission tocreate tables:

create table sampletable (field1 char(10));


drop table sampletable;

6. Issue the following command to ensure that the account has permissionto create procedures:

CREATE PROCEDURE test_proc (foo_in VARCHAR, bar_in VARCHAR)ISBEGININSERT INTO test_table (foo, bar) VALUES (foo_in, bar_in);END;

7. Issue the following command to ensure that the account has permissionto drop procedures:

DROP PROCEDURE TEST_PROC;

8. Type exit


page 19

Sybase database requirements

If you are using Sybase for the CMS or auditing database:• Create a database with a page size of 8 KB. The Sybase database default

page size is 2KB, which is too small for the CMS system database to runefficiently. The page size is set up during the database creation andcannot be changed after the database is created.



• Use a Unicode character set, such as UTF-8.

Once the database is created, you must prepare it for the BusinessObjectsEnterprise installation.


Testing Sybase environment variablesIf you choose to connect to Sybase through a native connection, theinstallation searches the current shell for the SYBASE and SYBASE_OCSenvironment variables. These standard Sybase environment variables mustbe set in order for the install script to utilize the Sybase client software.

If you are using an existing database, you need to source the script thatidentifies the database environment variables.

Sourcing the script that identifies the database environment variables canbe done in one of two ways:

• The user who performs a system installation can modify theBusinessObjects Enterprise script setupint.sh to add the command tosource your database client. However, root access is required to executethis script. This script can be found at the following location: <installdir>/bobje/init/setupint.sh. This method will source the database for allusers.


For example, if a Sybase database was required, an entry would be madein the user profile to source the environment script used by Sybase(SYBASE.sh or SYBASE.csh). Consult your database documentation forthe name of its environment script.

Note:

• Instead of sourcing the script that identifies the database environmentvariables, you can manually set the environment variables required byyour database. However, if you manually set the environment variables,you will need to set them again if the system is restarted.

• Consult your database documentation and/or your database administratorif the account shell environment from which you will install



BusinessObjects Enterprise has not yet been set up for your databaseclient software, or if you are unable to connect successfully to thedatabase.

These steps will test whether the required environment variables are set:


page 29

To verify Sybase native connectivity through a server name1. Log on to the UNIX server with the user account and password which




ValueVariable

This variable contains the path tothe root directory of your Sybaseclient installation (one level abovethe SYBASE_OCS version directo-ry).

SYBASE

This variable contains the name ofthe Sybase version directory (onelevel above the Sybase bin and libdirectories).

SYBASE_OCS



ValueVariable

The library search path (LD_LIBRARY_PATH on Solaris and Linux,LIBPATH on AIX, and SHLIB_PATHon HPUX) must include the lib di-rectory of your Sybase client instal-lation.

library path

The search path must include thebin directory of your Sybase clientinstallation.

PATH

This example checks the required variables, and shows sample outputvalues:

$ echo $SYBASE/opt/sybase/12.0$ echo $SYBASE_OCSOCS-12_O$ echo $LD_LIBRARY_PATH/export/home/sybase/12.0/OCS-12_0/lib$ echo $PATH/usr/bin:/usr/ucb:/etc:.:/export/home/sybase/12.0/OCS-12_0/bin

3. Issue the following command to run the Sybase SQL tool and connect tothe database server:

isql -U user -P password -S servername

Replace user, password, and servername with the appropriate values. Ifthe shell environment has been configured correctly, you are connectedto Sybase.

4. Issue the following command to ensure that the account has permissionto create tables:

use apsgocreate table sampletable (def_field char(10))



gosp_help sampletablego


drop table sampletablegosp_help sampletablego

6. Type quit


page 19

MySQL database requirements

If you are using your own MySQL installation for the CMS or auditingdatabase:• Use a Unicode character set, such as UTF-8.



Testing MySQL environment variablesIf you are using an existing MySQL database, ensure the following variableis set up for the user who will install BusinessObjects Enterprise:

MYSQL_HOME

If this variable is not set up, and you have specified that you are using anexisting MySQL database, the installation will not proceed and you will receivean error message. Consult the documentation for MySQL for information onhow to configure the MySQL.



Preparing an existing database serverAfter you have created your database, setup the database client, and beforeyou install BusinessObjects Enterprise, ensure that the Central ManagementServer (CMS) can connect to it.

During your installation, you will be asked whether you want to install MySQLor use an existing database. If you opt to use an existing database, you willbe asked for the connection and authentication details by the BusinessObjectsEnterprise installer:

Information required by installerExistingdatabase

• Database name• Server name• Port number (default is 3306)• Login credentials used to access database

MySQL

• Server name• Login credentials used to access database

Note:

• The Sybase server name is a combination of the host nameand the port number which is set by your database administratorin the file sql.ini interfaces file.

• BusinessObjects Enterprise will connect to the default databasefor the user you specify. This default is set by the databaseadministrator.

Sybase

• Server: DB2 database alias• Login credentials used to access databaseDB2

• Server: TNSNAMES connect identifier• Login credentials used to access databaseOracle


2Preparing to Install BusinessObjects EnterprisePreparing an existing database server

Before you deploy web applicationsYour web application server must be installed and working before you attemptto install BusinessObjects Enterprise.

To deploy and run the Central Management Console (CMC) and InfoViewweb applications, your web application server should have at least 2 GB offree disk space, in addition to any other requirements for other softwareinstalled on the machine.

Before deploying to a Java web application server

It is recommended that you change the heapsize and maximum perm sizesettings of your Java Virtual Machine (JVM) to -Xmx1024m-XX:MaxPermSize=256m. For example, Tomcat uses the JAVA_OPTSenvironment variable to configure its JVM:

JAVA_OPTS="$JAVA_OPTS -Xmx1024m -XX:MaxPermSize=256m"

Consult your JVM documentation for more information about changing yourJava memory settings.

Before you begin the deployment process, ensure that the web applicationserver is running correctly by launching its administrative console at:• http://<WAS_HOSTNAME>:<PORT>

Replace <WAS_HOSTNAME> with the hostname or IP address of your webapplication server, and <PORT> with the port number, if required.


Preparing to Install BusinessObjects Enterprise2 Before you deploy web applications

Beginning the Installation ofBusinessObjects Enterprise

3

Installation checklistPrior to installing BusinessObjects Enterprise, review the checklist below.• Have you tested that all machines that will run BusinessObjects Enterprise

can communicate properly?• Have you tested the database connection between the machine where

your CMS database will reside and where the Central Management Serverwill be installed?

• Have you decided which database to use with BusinessObjectsEnterprise?

• If you are using your own database server, have you created a databasefor the CMS?

• If you plan to connect remotely to install, have you ensured your terminalsetting is set to VT100 before beginning the installation?

• If you are using your own database server and plan to use Auditor, haveyou created an auditing database?

• If you are using your own database server, have you created a useridand password with access to your existing database (if you are integratingyour existing database server software), so that the installation can accessyour database to configure the CMS database?

• If you are using your own database server, have you made sure you canlog on to the database with the ID and setup tables?

• Have you ensured that any existing database you will be connecting tohas been configured correctly?

• Have you verified you are using a supported locale?• Have you decided whether or not you will develop custom applications?• Have you decided what web application server to use?• If you are not using Tomcat, have you made sure your existing web

application server has the JDK installed?• If you are not using Tomcat, is your web application server already

installed and configured?• Do the BusinessObjects Enterprise system requirements match your

UNIX setup?• If you are installing on a VMware virtual machine, ensure the machine

name does not include underscore (_), period(.), or slash (/ or \)characters.


Beginning the Installation of BusinessObjects Enterprise3 Installation checklist

• Does the UNIX user account under which the install is run have read,write, and execute permissions to the directory where BusinessObjectsEnterprise will be installed?

• Have you sourced your database client so that all the required environmentvariables are set up properly?

• If you are using DB2 or Sybase, have you verified that your databasewas created with the correct settings? (Some settings can't be modifiedafter the database has been created.)

Installation overviewBusinessObjects Enterprise allows you to run all server components on aUNIX server. Users then connect to BusinessObjects Enterprise over theWeb with a supported web browser. The installation can place the necessaryrun control scripts in the relevant directories for automated startup (requiresroot privileges), or you can confine the installation to a particular directory.

After you finish the installation and setup procedures, the various core servercomponents run as background processes. You can then deploy theBusinessObjects Enterprise web applications.

When you install the BusinessObjects Enterprise server components on aUNIX machine, you can connect remotely to BusinessObjects Enterprisewith the Publishing Wizard and the Import Wizard. However, these clientapplications must be installed on Windows.

Note:Before you run the interactive installation setup program (./install), it isstrongly recommended that you read through the details and proceduresprovided in the previous chapter

Setting up product distributionThis section shows how to distribute BusinessObjects Enterprise so that youcan perform an installation.

You can perform this installation remotely through a telnet session, or locallythrough a terminal window. If you will connect remotely to installBusinessObjects Enterprise, be sure to set your terminal settings to VT100before beginning the installation.


3Beginning the Installation of BusinessObjects EnterpriseInstallation overview

There are two ways you can set up the product distribution:

• Before you run ./install.sh, you can copy the installation files to atemporary location.

• When you run ./install.sh, you can specify the temporary location toplace the installation distribution.

Before following this procedure, ensure that you have set up your UNIXsystem appropriately.

Related Topics• Setting up your UNIX system on page 17

Running the product distribution directly from aDVD

By default, the installation will use your current directory, that is, the directoryyou run install.sh from, as its base directory for the install. If you run install.sh without copying the files to a temporary location, you will beprompted to specify a temporary location for the install. After you specify thetemporary location, this will happen:

• The installation files will be copied to that temporary location.

• The installation program will exit.

You are then required to go to the temporary location you specified, and thenrun install.sh from that location.

Copying the product distribution to your machine

By default, the installation will use your current directory, that is, the directoryyou run install.sh from, as its base directory for the install. You may wantto copy the product distribution to directory on your machine and run install.sh from there. The advantage of this option is that when you run install.sh, you will not be prompted for a temporary location to put the files.


Beginning the Installation of BusinessObjects Enterprise3 Setting up product distribution

To copy the product distribution to your machine

1. Log on to your UNIX system under the new account designated forinstalling BusinessObjects Enterprise.

2. Copy the installation files from the product distribution to a temporarydirectory with this command where /mnt/cd is mapped to the DVD driveand tmp is a temporary directory where you want to store the installationfiles:

/mnt/cd/install -t /tmp/

. Repeat this process for each DISK contained in the product distribution.

3. Proceed to Beginning your installation.4. Run install.sh from the first DVD.


page 19• Beginning your installation on page 51

Beginning your installationThe following instructions lead you through the initial steps of installingBusinessObjects Enterprise on UNIX. In this stage you will do the following:

• Choose the language for the installation.

• Agree to the license terms.

• Enter the product key codes.

• Select where to install BusinessObjects Enterprise.

• Select which language packs to install.

• Choose between a user and system install.

• Select an install type.


3Beginning the Installation of BusinessObjects EnterpriseBeginning your installation

To begin your installation

The installation procedure below is a quick overview of the initial stepsrequired to install BusinessObjects Enterprise on UNIX. This section isfollowed by a detailed description of each screen in the installation setupprogram.

1. Mount the device that contains the installation files.2. Type ./install.sh in the command line and press Enter.

Note:If you run install.sh without copying the files to a temporary location,you will be prompted to specify a temporary location for the install.

The installation setup program is launched and you are prompted to selecta language for the installation.

3. Select a language for the installation and press Enter.You can select from one of the following languages:• Chinese Simplified• Chinese Traditional• Danish• Dutch• English• French• German• Italian• Japanese• Korean• Norwegian• Polish• Portuguese (Brazil)• Russian• Spanish• Swedish• ThaiThe "Business Objects License Agreement" is displayed.


Beginning the Installation of BusinessObjects Enterprise3 Beginning your installation

Related Topics• Running the product distribution directly from a DVD on page 50

To accept the license agreement

To install BusinessObjects Enterprise on UNIX, you must accept the BusinessObjects License Agreement.

1. Read the software license agreement.2. Type y to agree to the terms and continue with the setup program.

The "Enter Product Keycode" screen is displayed.

To enter a product keycode

You must provide a valid BusinessObjects Enterprise product activationkeycode to continue with the installation setup program. The keycode contains26 characters and you can find it in the DVD liner notes or the DVD sleeve.

1. Type your code in Product Keycode.2. Press Enter to validate the keycode.

The setup program validates the keycode before the "Installation Directory"screen is displayed.

To specify the installation directory

After your product keycode is validated, you must specify an installationdirectory.

Note:If you are installing BusinessObjects Enterprise on a machine that has anearlier version of BusinessObjects Enterprise installed, you must specify adifferent directory for the new installation.

1. To accept the default installation directory press Enter.2. To create your own directory, use the Backspace key to remove the

current directory and replace it with your own path to the desiredinstallation directory and press Enter.



You are prompted to select which language packs to install.

To install language packs

You can choose to install language packs when running the installation setupprogram on UNIX.

1. Select any additional language packs you want to install.

The following languages are available:

• Chinese Simplified• Chinese Traditional• Danish• Dutch• English• French• German• Italian• Japanese• Korean• Norwegian• Polish• Portuguese (Brazil)• Russian• Spanish• Swedish• Thai

2. Press Enter .

Note:You can also add language packs after installing BusinessObjectsEnterprise on UNIX.

You are prompted to select either a user or system installation.

Related Topics• Installing language packs on page 137



To select user or system installation

1. Select the type of installation you want to perform.• User• System

Note:To perform a System installation, you do not require root-level authority.However, to run the system-level initiation script root-level authority isrequired. After you perform a System installation, there are a few additionalsteps you must perform.

2. Press Enter.The "Installation Type" screen is displayed.

Related Topics• Difference between user and system installation on page 20

To select an installation type

You can select from one of the following three installation types: New,Custom, or Web Tier.

1. Select the installation type.• New

Performing a new installation is the simplest way to deployBusinessObjects Enterprise because all the required components areinstalled by default onto one machine.

• Custom or Expand

The custom installation allows you to choose which components areinstalled. You may want to perform a custom installation if you planto use BusinessObjects Enterprise in a distributed environment.Recommended for advanced users.

• Install Web Tier features

Choose to perform a web applications installation if you want to installweb application server components. This option installs the Web



application components only. This is particularly useful for a distributeddeployment.

• You can deselect Enable servers after installation. This preventscommunication between the Central Management Server (CMS) andother servers after the installation is complete. For more informationon starting, stopping, disabling and enabling servers, refer to theBusinessObjects Enterprise Administrator's Guide.

2. Press Enter.

Related Topics• Performing a new installation on page 58• Performing a custom or expand installation on page 72• To perform a web tier installation on page 93



New Installation

4

Performing a new installationPerforming a new installation is the simplest way to deploy BusinessObjectsEnterprise because all the required and optional components are installedon one machine.

The setup of a new installation of BusinessObjects Enterprise requires thefollowing input.

1. Providing information on the system administrator for the new installation.

2. Setting up the system and auditing database. You can choose to eitherinstall and configure MySQL or configure your existing database.

3. Configuring the Server Intelligence Agent (SIA).

4. Setting up the web application server. You can choose to either installand configure Tomcat or configure your existing web application server.

5. Confirming the installation directory.

Selecting a new installation

The "Installation Type" screen in the following procedure is displayed afteryou have completed the initial set up of the BusinessObjects Enterpriseinstallation.

1. Select or deselect Enable servers after installation. This option isselected by default. Scroll down and use the spacebar to deselect thefield.

2. Select New and press Enter.The "Enter the information for your new CMS" screen is displayed.

Related Topics• Beginning your installation on page 51


New Installation4 Performing a new installation

To configure the new CMS

Use the "Enter the information for your new CMS" screen to specify theCentral Management Server (CMS) port number and password for theBusinessObjects Enterprise Administrator.

1. Type a valid port number in CMS Port Number or accept the defaultnumber - 6400.

2. Type the same password under Administrator Password and ConfirmPassword and press Enter.

Note:You can also leave the passwords fields blank and configure the passwordat a later time. Your password must be at least six characters long andshould contain two of the following options

• upper case character• lower case character• number• punctuation

To specify a system database option

You must select a system database option. You can either choose to installMySQL or specify to use your current database.

1. Choose one of the following options:• Use an existing database (Oracle/DB2/Sybase/MySQL)• Install MySQL

2. Press Enter.Depending on your selection you will either select and configure yourexisting database, or configure your MySQL installation.

Related Topics• To configure your existing database on page 60• To install a new MySQL Database on page 62


4New InstallationPerforming a new installation

To configure your existing database

If you specified to use an existing database for the CMS, use the "Select thedatabase type for your new CMS" screen to select your existing databasetype. You will then have to configure the database.

1. Select your database type. You can choose from the following• MySQL• Oracle• DB2• SybaseA new screen displays containing fields for configuring your database.

2. Provide information about your database and press Enter.The table below lists the information required for each database type.

Information requiredDatabase type

Host Name

User ID for CMS database

Password for CMS database

MySQL port number

Database name for CMS

MySQL

TNS name

User ID for CMS databasePassword for CMS database

CMS port number

Oracle




Alias name



DB2

Sybase Service name



Sybase

3. To enable an auditing database, type an x in the field provided.

If you want to enable an auditing database, type an x in the field provided.

Provide information about your new auditing database.


Auditing database name

User ID

Password

Note:If you are using Sybase as the au-diting database, you must also pro-vide the Auditing database portnumber.

Auditing

4. Decide if you want to reinitialize the database and press Enter.



Note:Reinitialization of the BusinessObjects Enterprise database will erase allprevious content in that particular database.

After configuring your CMS and auditing database, you are prompted forinformation on the Server Intelligence agent.

If you are using an existing database, you need to source your databaseenvironment variable so the CMS can access it after a system reboot. Thiscan be done one of two ways

• Someone with root access can modify the BusinessObjects Enterprisescript BobjEnterprise120 and add the command to source your databaseenvironment. This script can be found at the following location:<INSTALLDIR>/bobje/init/BobjEnterprise120. This method will sourcethe database environment variable for all users.

• Each user can modify their own profile and add the command to sourcetheir database environment. This method must be done by each user.

.

Related Topics• CMS Database requirements and preparation on page 28

To install a new MySQL Database

You need to provide configuration details for the new MySQL database. Thesetup program provides two screens to configure the new database.

1. Provide the following information for your new MySQL database andpress Enter.• MySQL Port Number• Database administrator passwordThe second MySQL configuration screen is displayed.

2. Provide the following information for your new MySQL database andpress Enter.• MySQL CMS Database Name• MySQL Audit Database Name• User ID



Note:This is the BusinessObjects Enterprise user account.

• Password for user account

3. Press Enter to continue with the installation setup.The "Enter Server Intelligence Agent information" screen is displayed.

To enter Server Intelligence Agent information

The Server Intelligence Agent (SIA) simplifies the deployment andmanagement of the BusinessObjects Enterprise servers. The SIA isautomatically created during installation of BusinessObjects Enterprise. Usethe installation setup program to configure the SIA.

1. Type a name in Server Intelligence Agent Node.

Note:Do not use spaces or non-alphanumeric characters in a SIA node name.

This node name serves as an identifier for the SIA.

2. Type a valid port number under Server Intelligence Agent Port or acceptthe default port number -6410, and press Enter..

To select a web application server configurationoption

As part of the installation setup, you need to provide information on the webapplication server that will work with your BusinessObjects applications suchas InfoView and the Central Management Console (CMC). Use the installationprogram to specify to install Tomcat as your application server, or chooseto work with your existing web application server.

Note:If you are installing BusinessObjects Enterprise on an HPUX Itanium 64-bitoperating system, Tomcat 5.5 is the only supported application server. Youcan either install the version of Tomcat that comes with the installationpackage, or deploy the BusinessObjects Enterprise web applications to anexisting Tomcat 5.5 application server.



• Select one of the options listed below and press Enter.

When to useDeployment option

If you do not have an existing web appli-cation server.

Install Tomcat, deploy web appli-cations

If you have an existing supported webapplication server and you want to auto-matically deploy the web applications.

Use existing Java applicationserver, deploy web applications

If you have an existing supported webapplication server and you want to manu-ally deploy the web applications.

Use existing Java applicationserver, do not deploy web appli-cations

If you have selected either the first or second option, you will now haveto configure the web application server. If you have selected the thirdoption you can start the installation process.

Related Topics• To start the installation on page 99• To configure your existing web application server on page 95• To configure the Tomcat installation on page 95

To configure the Tomcat installation

If you chose to install the Tomcat application server, the "Please enter portnumbers for the Tomcat installation screen" is displayed. You must configurethe server to use InfoView, the Central Management Console and other webapplication servers.

1. You can either choose to accept the default port numbers or provide newvalues for the following:

Required port numbers

Receive HTTP requests

Redirect jsp requests

Shutdown hook

2. Press Enter.



You can now start the installation process.

Related Topics• To start the installation on page 99

To configure your existing web application server

You must select the Use existing Java application server, deploy webapplications option to view the "Select a Web Application Server to deployto" screen.

Select the server type before configuring your web application server.1. Select your existing web application server from one of the following

options and press Enter.• Tomcat 5.5• WebLogic 10• WebLogic 9.2• WebSphere 6.1• Oracle Application Server 10g R3If your existing web application server is SAP Application Server 7.0 orJBoss 4.04, selectUse existing Java application server, do not deployweb applications.

Note:If you are installing BusinessObjects Enterprise an HPUX Itanium 64-bitoperating system, Tomcat 5.5 is the only option that is available to you.

If you select Other, you can begin the installation. If you selected one ofthe supported servers, you can now configure the server on a separatescreen.

2. Provide the requested configuration details for your web application serverand press Enter.

The table below summarizes the information required for each supportedweb application server.



Information required for installation setupWeb applicationserver

• Instance to install to: Name of the current web application serverinstance (for example “localhost”).

• Application server Installation directory: The directory where theweb application server is installed (for example <INSTALLDIR>/wdeploy/appserver/Tomcat5520).

Apache Tomcat 5.5

• Admin port: Administration port of the application server - manda-tory for WebLogic (for example “7001”).

• Admin login: User name with administration rights to the applicationserver - mandatory for WebLogic.

• Admin password: Password for account with administration rightsto the application server - mandatory for WebLogic.

• Instance to install to: Name of the current web application serverinstance (for example “mserver1”).

• Application server domain root directory: The WebLogic domainroot directory (for example /bea/user_projects/domains/base_domain).

WebLogic 9.2





• Application server domain root directory: The WebLogic domainroot directory (for example /bea/weblogic10/user_projects/domains/base_domain).

WebLogic 10

WebSphere 6.1




• SOAP port: The SOAP Connector Port of the application server (forexample “8880”).

• Admin login: User name with administration rights to the WebSphereapplication server.

• Admin password: Password for account with administration rightsto the application server.

• Instance to install to: Name of the current web application serverinstance (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 setwhen Admin is Secure is enabled.

• Application server installation directory: The directory where theweb application server is installed (for example/IBM/WebSphere/AppServer).

Oracle ApplicationServer 10g R3




• Admin port: Administration port of the application server - manda-tory for Oracle 10g R3 (for example “6003”) .This should be the Re-quest port of the <notifi-cation-server> element in theopmn.xml file.

• Admin login: User name with administration rights to the applicationserver - mandatory for Oracle 10g R3.

• Admin password: Password for account with administration rightsto the application server - mandatory for Oracle 10g R3.

• Admin is secure (y/n): Select this option only if you want SecureSockets Layer (SSL) as part of the deployment.

Note:If Admin is secure is not selected, you will still have to specify theusername and password to access the server.

• Instance to install to: Name of the current web application serverinstance (for example “home”).

• Application server Installation directory: The directory where theweb application server is installed (for example /product/10.1.3/OracleAS_1).

• Server Name: Name of the target application server (for example"myserver.domain.com").

• Group Id: Name of the server group to which the target applicationbelongs (for example "Default_group").

.


To start the installation

You are now ready to start the installation.

1. Review the installation directory specified on the screen.

Note:To modify the directory you would need to press [Ctrl + B ] several timesuntil you reach the screen where you specify the installation directory.



2. Press Enter to start the installation.The installation program will validate your system and installBusinessObjects Enterprise in the specified directory.

When the new installation is finished, the setup program starts the serversas daemons and then enables each server that is registered with the CMS.To control the servers manually, use the ccm.sh script.

Related Topics• Using ccm.sh to start the BusinessObjects Enterprise servers on page 130

Finishing a system installationIf you chose to perform a system installation, the setup program script promptsyou to run the BobjEnterprise120 script after it is finished. The BobjEnterprise120 script copies the run control scripts to your /sbin/rc# directories.When implemented, these run control scripts start/stop the BusinessObjectsEnterprise servers on system startup/shutdown.

Note:To run the system installation, you must log on using a normal account. Afterinstallation, however, you must have root privileges to run the setupinit.shscript. This script copies the BobjEnterprise120 to the /sbin/rc# directory.


4New InstallationFinishing a system installation


New Installation4 Finishing a system installation

Custom or ExpandInstallation

5

Performing a custom or expandinstallation

The Custom or Expand installation option allows you to selectively installspecific features. You may want to perform a custom installation if you planto use BusinessObjects Enterprise in a distributed (split) environment. Forexample, your existing web application server resides on a different machinethan the one hosting the BusinessObjects Enterprise core components.

You customize the installation in the setup program Features screen.

The Features screen contains a tree of features divided into the followingtop-level features:

• Client Components• Web Tier Components• Server Components• Database Access• Export Support• Samples• Help Files

The markers in the tree indicate whether or not the feature and its subfeatureswill be installed:

• [X] means that the feature and all its subfeatures will be installed.

• [~] means that the feature and some of its subfeatures will be installed.

• [ ] means the feature will not be installed.

To select a feature or subfeature, select its corresponding marker and typeX.

Client Components

This feature contains the Developer Components which has twosubfeatures:• BusinessObjects Enterprise Java SDK: This is the development kit for

Java applications.• BusinessObjects Enterprise Web Services SDK: This is the

development kit for web services.


Custom or Expand Installation5 Performing a custom or expand installation

Web Tier Components

This feature contains the following subfeatures:

• BI Platform Web Components: This includes all components used torun BusinessObjects applications including Central Management Console,InfoView, Dashboard and Analytics, and Voyager.

• BusinessObjects Enterprise Web Services: This is a component ofBusinessObjects Enterprise built for developers. It is composed of animplementation of web services that can be deployed withBusinessObjects Enterprise.

• Tomcat: If you do not have an existing web application server, you canchoose to install Apache Tomcat 5.5.

Server Components

For a detailed explanation of what the listed servers do, please consult the“BusinessObjects Enterprise Architecture” chapter of the BusinessObjectsEnterprise Administrator's Guide. Server Components contains the followingsubfeatures:

• Central Management Server Contains the following subfeatures:• Auditor• MySQL

• Event Server• Input File Repository Server• Output File Repository Server• Crystal Reports Cache Server• Crystal Reports Processing Server• Publication Job Server• Report Application Server• Crystal Reports Job Server• Destination Job Server• List of Values Job Server• Desktop Intelligence Job Server• Program Job Server• Adaptive Job Server• Adaptive Processing Server• Web Intelligence Report Server• Desktop Intelligence Servers


5Custom or Expand InstallationPerforming a custom or expand installation

• Dashboards and Analytics Servers• Auditing Reports and Universes• Multi-Dimensional Analysis Services Server

Database Access

This feature installs the necessary drivers and files to provide access to abroad range of data sources. It contains the following subfeatures:

• Data Federator• MySQL• Generic ODBC, JDBC• Salesfore.com Driver• NETEZZA• ALL IBM Database Drivers contains the following subfeatures:

• IBM DB2• Informix

• Progress OpenEdge• Oracle• Sybase• NCR Teradata• HP Neoview (For Linux only)

Export Support

This feature contains drivers and files to enable export to a variety of industrystandard file formats. It includes the following subfeatures:

• Character Separated• Disk File• Rich Text Format• Word for Windows• Acrobat PDF• Text• Excel Format• Crystal Reports• XML Format• Legacy XML Format


Custom or Expand Installation5 Performing a custom or expand installation

Samples

Included are samples for Crystal Reports, a BIAR file that includes WebIntelligence reports as well as the universe used to create these reports.Sample reports are located in the Report Samples folder. Only Englishsamples will be installed. Samples in other languages can be downloadedfrom http://support.businessobjects.com/.

Help Files

Select the Help files feature to install the HTML help for the products youare installing including as well as the BusinessObjects EnterpriseAdministrator's Guide and the BusinessObjects Enterprise InfoView User'sGuide.

To perform a Custom or Expandinstallation

The Installation Type screen in the following procedure appears after youhave completed the initial set up of the BusinessObjects Enterpriseinstallation.1. Select or deselect Enable servers after installation. This option is

selected by default. Scroll down and use the spacebar to deselect thefield.

2. Select Custom or Expand and press Enter.The "Features" screen is displayed with seven top level features. Expandany displayed features to drill down to display available sub features.

3. Deselect any features you do not want to install.a. Deselect the Tomcat subfeature under Web Tier Components if you

want to use your existing web application server.b. DeselectAuditor underServer Components >Central Management

Server if you do not want to configure an auditing database.c. DeselectMySQL underServer Components >Central Management

Server if you want to use your existing database server.

4. After selecting what components you want to install press Enter.

Consult the BusinessObjects Enterprise Administrator's Guide for informationabout scaling your deployment across multiple machines.


5Custom or Expand InstallationTo perform a Custom or Expand installation

http://support.businessobjects.com

Related Topics• Beginning your installation on page 51• Installing only the Web Tier Components on page 82• To install only the server components on page 76

To install only the server components

You would typically only install the server components onto a machine thatyou have set aside for use by BusinessObjects Enterprise. When you performthis installation scenario, the server components are installed, the defaultuser and group accounts are created, and the sample reports are publishedto the system. When the installation is complete, the servers are automaticallystarted.

The Installation Type screen in the following procedure appears after youhave completed the initial setup of the BusinessObjects Enterprise installation.

1. On the Installation Type screen, choose Custom or Expand.2. Select the Server top level feature under BusinessObjects Enterprise.3. Deselect the Client Components and Web Tier Component features.

4. Deselect MySQL under Central Management Server if you plant to usean existing database server.

5. Deselect Auditor under Central Management Server if you do not wantto configure and auditing database.

6. Press Enter to submit your selections.If you deselected the Central Management Server (CMS) feature, youmust cluster the installed servers to an existing CMS. If you onlydeselected MySQL you must specify CMS clustering information. If youchose to Install MySQL, you must configure your new database.

Related Topics• Beginning your installation on page 51• To cluster servers to an existing CMS on page 81• To specify CMS clustering information on page 78• To configure MySQL in a custom or expand installation on page 77


Custom or Expand Installation5 To perform a Custom or Expand installation

To configure the new CMS

Use the "Enter the information for your new CMS" screen to specify theCentral Management Server (CMS) port number and password for theBusinessObjects Enterprise Administrator.

1. Type a valid port number in CMS Port Number or accept the defaultnumber - 6400.

2. Type the same password under Administrator Password and ConfirmPassword and press Enter.

Note:You can also leave the passwords fields blank and configure the passwordat a later time. Your password must be at least six characters long andshould contain two of the following options


To configure MySQL in a custom or expand installation

The "Enter the information for your new MySQL Database" screens allowyou to provide configuration details for the new MySQL database.

1. On the first "Enter the information for your new MySQL Database" screen,provide the following information for your new MySQL database, andpress Enter.• MySQL Port Number• Database administrator passwordThe second MySQL configuration screen is displayed.

2. Provide the following information for your new MySQL database andpress Enter.• MySQL CMS Database Name• MySQL Audit Database Name• User ID

Note:This is the BusinessObjects Enterprise user account.



• Password for user accountThe "Enter Server Intelligence Agent information" screen is displayed.

Related Topics• To enter Server Intelligence Agent information on page 81

To specify CMS clustering information

If you deselected MySQL in the "Features" screen, but want to install anCentral Management Server (CMS), you need to provide more informationon CMS clustering on your deployment

1. Select on of the following options and press Enter.• Yes - This is the first CMS in this deployment

Note:If you select this option you must provide information on your newCMS.

• No - Cluster this CMS with an existing CMS

Note:If you select this option you must provide information on the existingCMS on which you are going to cluster the servers.

2. If you selected Yes in step 1:a. Type a valid port number in CMS Port Number or accept the default

number - 6400.b. Type the same password under Administrator Password and

Confirm Password and press Enter.

Note:You can also leave the passwords fields blank and configure thepassword at a later time. Your password must be at least six characterslong and should contain two of the following options


c. You must now select and configure your database server. Skip to step4.



3. If you selected No in step 1:a. You need to specify a valid unused port for the new CMS in New CMS

Port.b. Type the system name of the CMS to which you are clustering in

Existing CMS Hostname.c. Accept the default value -6400- or else type the port number in

Existing CMS Port.d. Type the password or leave Existing CMS Administrator Password

blank and press Enter.You must now select and configure your existing database server.

4. Select your database type. You can choose from the following• MySQL• Oracle• DB2• SybaseA new screen displays containing fields for configuring your database.

5. Provide information about your database and press Enter.The table below lists the information required for each database type.


Host Name



MySQL port number

Database name for CMS

MySQL

TNS name



Oracle




Alias name



DB2

Sybase Service name



Sybase

6. If you deselected Auditor in the "Features" screen skip to step 7.Otherwise you must provide the following information about your newauditing database:


Auditing database name

User ID

Password

Note:If you are using Sybase as the au-diting database, you must also pro-vide the Auditing database portnumber.

Auditing

7. Decide if you want to reinitialize the database and press Enter.



Note:Reinitialization of the BusinessObjects Enterprise database will erase allprevious content in that particular database.

After configuring your CMS and auditing database, you are prompted forinformation on the Server Intelligence agent.

Related Topics• To enter Server Intelligence Agent information on page 81

To cluster servers to an existing CMS

If you deselected the Central Management Server feature, you will beprompted to cluster the servers you are installing to an existing CMS.

1. Provide the following information on the CMS to which you are clustering:

Information requiredField

The system name of the machine on which the CMSis installed.

CMS Hostname

Accept the default value -6400- or else type the portnumber used by the CMS.

Port

Provide the password by the CMS Administrator.Existing CMS Ad-ministrator Pass-word

2. Press Enter.You now have to configure a Server Intelligence Agent for your installation.

To enter Server Intelligence Agent information

The Server Intelligence Agent (SIA) simplifies the deployment andmanagement of the BusinessObjects Enterprise servers. The SIA isautomatically created during installation of BusinessObjects Enterprise. Usethe installation setup program to configure the SIA.

1. Type a name in Server Intelligence Agent Node.




This node name serves as an identifier for the SIA.

2. Type a valid port number under Server Intelligence Agent Port or acceptthe default port number -6410, and press Enter..








Installing only the Web Tier Components

You can chose to only install the Web Tier components while running aCustom or Expand installation. You would typically only install the Web Tiercomponents on the machine running your web application server.

Tip:If you only want to only install Web Tier components, to save time and avoidinstalling unnecessary components run a Web Applications installation.



Related Topics• To perform a web tier installation on page 93

To install only the Web Tier Components

The Installation Type screen in the following procedure appears after youhave completed the initial set up of the BusinessObjects Enterpriseinstallation.

1. On the Installation Type screen, choose Custom or Expand.The Features screen is displayed

2. Select the Web Tier Components option under BusinessObjectsEnterprise.

3. Deselect all the other top-level features by typing X in all the correspondingmarkers. Ensure that all the markers for the other top level features appearas[ ].

4. Deselect the Tomcat subfeature if you want to use your existing webapplication server and press Enter.You will be prompted to cluster your selected web tier components to anexisting Central Management Server.

Related Topics• Beginning your installation on page 51• To cluster web tier features to a CMS on page 93

To cluster web tier features to a CMSIf you are only installing the web tier components, you need to be able toconnect to a running Central Management Server (CMS).

After selecting what web tier features to install, you need to provideinformation on the CMS to which the feature will be clustered.

1. Specify the machine name where the CMS is installed inCMSHostname.2. Accept 6400 as the Port if that is number used by the CMS. Modify the

value if your CMS is using another port.3. Specify the password required for Administrator access to the CMS in

Existing CMS Administrator Password. Press Enter.

Note:If no password is required, leave the field empty.



Depending on your selection in the "Features" screen, you will now eitherconfigure the Tomcat application server, or specify a deployment option.

To select a web application server configuration optionAs part of the installation setup, you need to provide information on the webapplication server that will work with your BusinessObjects applications suchas InfoView and the Central Management Console (CMC). Use the installationprogram to specify to install Tomcat as your application server, or chooseto work with your existing web application server.














To configure the Tomcat installationIf you chose to install the Tomcat application server, the "Please enter portnumbers for the Tomcat installation screen" is displayed. You must configurethe server to use InfoView, the Central Management Console and other webapplication servers.





Shutdown hook

2. Press Enter.You can now start the installation process.


To configure your existing web application serverYou must select the Use existing Java application server, deploy webapplications option to view the "Select a Web Application Server to deployto" screen.


options and press Enter.• Tomcat 5.5• WebLogic 10• WebLogic 9.2• WebSphere 6.1• Oracle Application Server 10g R3If your existing web application server is SAP Application Server 7.0 orJBoss 4.04, selectUse existing Java application server, do not deployweb applications.






Apache Tomcat 5.5






WebLogic 9.2






WebLogic 10

WebSphere 6.1













.


To start the installationYou are now ready to start the installation.



2. Press Enter to start the installation.



The installation program will validate your system and installBusinessObjects Enterprise in the specified directory.



Finishing a system installationIf you chose to perform a system installation, the setup program script promptsyou to run the BobjEnterprise120 script after it is finished. The BobjEnterprise120 script copies the run control scripts to your /sbin/rc# directories.When implemented, these run control scripts start/stop the BusinessObjectsEnterprise servers on system startup/shutdown.



Custom or Expand Installation5 Finishing a system installation

Web ApplicationsInstallation

6

Performing web tier installationsThe web tier installation type installs the appropriate web tier componentson the machine running your web application server. You will need useraccount and port information to configure your web application server throughthe BusinessObjects Enterprise setup program.

The web application server processes scripts, communicates with report andcache servers, translates cached files to DHTML, facilitates OLAP viewrequests and manages session state information for users.

A distributed installation has two stages. The first step is done on the machinewhere the BusinessObjects Enterprise components will reside. The secondstep is to install the Web Tier Components on the machine where the webserver is installed.

Note:

• It is best practice to install the server and client components to verifyconnectivity.

• Java SDK 1.5 is installed by default when you install the Web TierComponents.

Features available in a web tier installation

• BI Platform Web Components: This includes all components used torun BusinessObjects applications including Central Management Console,Infoview, Dashboard and Analytics, and Voyager.

• BusinessObjects Enterprise Web Services: This is a component ofBusinessObjects Enterprise built for developers. It is composed of animplementation of web services that can be deployed withBusinessObjects Enterprise. This web service implementation providesan API/WSDL which simplifies the process of developing applications.

• Tomcat: If you do not have an existing web application server, you canchoose to install Apache Tomcat 5.5.


Web Applications Installation6 Performing web tier installations

To perform a web tier installation

The Installation Type screen in the following procedure appears after youhave completed the initial set up of the BusinessObjects Enterpriseinstallation.

1. Select or deselect Enable servers after installation. This option isselected by default. Scroll down and use the spacebar to deselect thefield.

2. Select Install Web Tier features and press Enter.The "Features" screen is displayed.

3. Expand Web Tier Components to specify which features to install.

Tip:Deselect the Tomcat subfeature if you want to use your existing webapplication server.

4. Press Enter to submit your selection.You must now cluster the selected components to an existing CentralManagement Server (CMS).

Related Topics• Beginning your installation on page 51

To cluster web tier features to a CMS

If you are only installing the web tier components, you need to be able toconnect to a running Central Management Server (CMS).

After selecting what web tier features to install, you need to provideinformation on the CMS to which the feature will be clustered.

1. Specify the machine name where the CMS is installed inCMSHostname.2. Accept 6400 as the Port if that is number used by the CMS. Modify the

value if your CMS is using another port.3. Specify the password required for Administrator access to the CMS in

Existing CMS Administrator Password. Press Enter.


6Web Applications InstallationPerforming web tier installations

Note:If no password is required, leave the field empty.

Depending on your selection in the "Features" screen, you will now eitherconfigure the Tomcat application server, or specify a deployment option.

To select a web application server configurationoption

As part of the installation setup, you need to provide information on the webapplication server that will work with your BusinessObjects applications suchas InfoView and the Central Management Console (CMC). Use the installationprogram to specify to install Tomcat as your application server, or chooseto work with your existing web application server.














To configure the Tomcat installation

If you chose to install the Tomcat application server, the "Please enter portnumbers for the Tomcat installation screen" is displayed. You must configurethe server to use InfoView, the Central Management Console and other webapplication servers.





Shutdown hook

2. Press Enter.You can now start the installation process.


To configure your existing web application server

You must select the Use existing Java application server, deploy webapplications option to view the "Select a Web Application Server to deployto" screen.


options and press Enter.• Tomcat 5.5• WebLogic 10



• WebLogic 9.2• WebSphere 6.1• Oracle Application Server 10g R3If your existing web application server is SAP Application Server 7.0 orJBoss 4.04, selectUse existing Java application server, do not deployweb applications.










Apache Tomcat 5.5






WebLogic 9.2






WebLogic 10

WebSphere 6.1













.











Finishing a system installation

If you chose to perform a system installation, the setup program script promptsyou to run the BobjEnterprise120 script after it is finished. The BobjEnterprise120 script copies the run control scripts to your /sbin/rc# directories.When implemented, these run control scripts start/stop the BusinessObjectsEnterprise servers on system startup/shutdown.




Silent Installation

7

OverviewThere are two methods for running BusinessObjects Enterprise installationsfor UNIX directly from the command line:

• Silent installation using a response file - referred to as a scriptedinstallation in this guide

• Silent installation specifying parameters directly on the command line

Both methods can be used to automate installations across multiplemachines. The scripted installation requires you to specify a response file.The silent installation allows you to specify parameters for running the./install.sh command.

Note:The silent installation without the response file is not recommended for custominstallations. This method does not allow for the same level of customizationprovided when using a response file.

These installation types are particularly useful when you need to performmultiple installations, as you can save time and avoid being prompted forinformation by the installation setup program. You can also integrate thescripts and commands into your own installation scripts.

Related Topics• To create a response file on page 103• Scripted installation parameters on page 110

Performing a scripted installationWhile setting up an installation process on UNIX, you can write installationsettings to a specified response file. The file is generated once the installationsetup program is ready to start the installation.

The response file supports all three BusinessObjects Enterprise installationtypes available for UNIX:• New• Custom or Expand• Web Tier


Silent Installation7 Overview

Tip:You do not start the installation process to generate the response file. SelectCtrl + X to abort the installation setup once you reach the final screen in theinstallation setup program.

To create a response file

1. Mount the device that contains the installation files.

Note:If you run the installation script without copying the files to a temporarylocation, you will be prompted to specify a temporary location for theinstallation.

2. In the command line type ./install.sh, -w and the file path the responsefile you want to generate.

./install.sh -w responseFilePath

Note:When specifying responseFilePath make sure you include the nameof the file you want to generate.

3. Press Enter to launch the installation setup program.4. Follow the onscreen instructions to enter your preferred installation settings

until you reach the final screen of the setup program.These settings are recorded in the response file.

5. Press [Ctrl + X] to abort the installation setup once you reach the finalscreen in the installation setup program.You can access the response file from the directory you specified in step2.

Related Topics• To create a response file on page 103• Scripted installation parameters on page 110


7Silent InstallationPerforming a scripted installation

Sample response file

The following example installation response file was generated for a newBusinessObjects Enterprise installation in which MySQL and Tomcat wereselected. The French language pack was added to the English default.

# Installation Response File# ---------------------------------------------------------------------- #[Manual Settings]# The name of the local server. This feature overrides the localserver name# to the machine name specified. It must be manually set withinthe response file# or it will be defaulted to the local machine name.MACHINENAME= <mymachine>

[Paths]# The path of the bobje directory. This feature is automaticallyset by# the installation directory specified as a command line argument followed# by /bobje/.BOBJEDIR="/net/home/businessobjectsenterprise/bobje/"

# The path of the DISK_1 directory on the CD. This path defaultsto the cd directory# pertaining to the install which has created the responsefile. It may be overwritten# by specifying the cd directory as an argument on the commandline.CDDIR=/net/home/temp

# The path of the license directory.LICENSEDIR=

[Product Information]# The current language with the following exceptions:# 1) "jp" if the current language is "ja"

(Japanese)# 2) "chs" if the current language is "zh_CN"

(Chinese - China)# 3) "cht" if the current language is "zh_TW"

(Chinese - Taiwan)BOBJELANG="en"

# The name of the product being installed.PRODUCTID_NAME="BusinessObjects"


Silent Installation7 Performing a scripted installation

# The version of Business Objects Enterprise.BOBJEVERSION="12.0"

# The version of the product being installed.PRODUCTID_VER="12.0"

# The license key to install Business Objects Enterprise.BOBJELICENSEKEY=XXXXX-XXXXXXX-XXXXXXX-XXXX

# The product id key. ( The product id is usually the same asthe BOBJELICENSEKEY )PIDKEY=XXXXX-XXXXXXX-XXXXXXX-XXXX

[Installation Information]# The installation function to perform. (i.e. install)FUNCTION=install

# The type of installation. (i.e. new / custom / webtier )INSTALLTYPE="new"

# A comma-delimited list of flags that describe the operatingmode of the Installer# The following flags are supported:# install - running a new install of the product# modify - running a modify install on a previously installed product# remove - running a uninstall of on a previously installedproduct# integrated - the current install is running from within another installed (ie. integrated langpacks)# interactive - UI is enabled and can prompt for user response

INSTALLMODE=interactive,install

# The name of the local server.LOCALNAMESERVER="<servername>"

# Whether to perform a user or system install.BOBJEINSTALLLOCAL="user"

# The language packs to install.# Each language is specified using the short format and isseparated by a space.# Example: LANGPACKS_TO_INSTALL=en frLANGPACKS_TO_INSTALL=fr

# List of all languages included in the product.# Each language is specified using the short format and isseparate by a comma.# Example: LANGUAGES_TO_INSTALL=en,frLANGUAGES_TO_INSTALL=en,fr,is,ja

# The Business Objects Enterprise username.



BOBJEUSERNAME="Administrator"

# Specified servers to add.EXPANDSERVERS=

[Tomcat]# Whether or not to install Tomcat.INSTALLTOMCAT=yes

# The connection port.CONNECTORPORT="8080"

# The redirection port.REDIRECTPORT="8443"

# The shutdown port.SHUTDOWNPORT="8005"

[Application Server]# The path of the Application Server directory (If an Application Server# is being installed). This path is automatically set usingthe installation# directory.

AS_DIR=/net/home/businessobjectsenterprise/bobje/tomcat/

# The Application Server name.# Defaults to tomcat55 if Tomcat is to be installed.AS_SERVER=tomcat55

# The instance of the Application Server. (e.g. localhost)# Defaults to localhost if Tomcat is to be installed.AS_INSTANCE=localhost

# The Application Server virtual host.AS_VIRTUAL_HOST=

# The Application Server port.AS_ADMIN_PORT=

# The Application Server's Administrator Username.AS_ADMIN_USERNAME=

# The Application Server's Administrator Password.AS_ADMIN_PASSWORD=

# Whether or not the Application Server's Administrator is secure.AS_ADMIN_IS_SECURE=

# The Application Server's Name (Oracle AS only).AS_APPSERVER_ID=



# The Application Server's Group Id (Oracle AS only).AS_GROUP_ID=

# The Application Server deployment action. (i.e. deploy orpredeploy)WDEPLOYACTION=deploy

[CMS Cluster]# Whether or not to cluster the CMS.CMSCLUSTER="no"

# The CMS name to cluster to.CLUSTER_NAMESERVER=""

# The CMS port number to cluster to.CLUSTERPORTNUMBER="6400"

[CMS]# The type of database. (e.g. MySQL, DB2, Oracle)DBTYPE="MySQL"

# The service name of the CMS.SERVICENAME="BOE120"

# The username to connect to the database.DATABASEUID="Administrator"

# The password to connect to the database.DATABASEPWD=<password>

# The name of the CMS server.CMSNAMESERVER="<servername>"

# The port number used to communicate with the CMS.CMSPORTNUMBER="6400"

# The password used to connect to the CMS.CMSPASSWORD=<password>

# The server intelligence agent node name.SIANODENAME="MyNode"

# The port used to communicate with the server intelligenceagent.SIAPORTNUMBER="6410"

# Whether or not to reinitialize the database.REINIT="yes"

[MySQL]# Whether or not to install MySQLINSTALLMYSQL="yes"



# The port number used to communicate with the MySQL database.

SERVICEPORT="3306"

# The name of the server hosting the MySQL database.MYSQLHOSTNAME="<servername>"

# The root password for the MySQL database.MYSQLROOTPWD=<password>

[Audit]# Whether or not auditing is enabled.

AUDITINGENABLED=yes

# The service audit name of the CMS.SERVICENAME_AUDIT="BOE120_AUDIT"

# The port number used to communicate with the MySQL database.

SERVICEPORT_AUDIT="3306"

# The name of the server hosting the MySQL database.MYSQLHOSTNAME_AUDIT="<servername>"

# The audit username to connect to the database.DATABASEUID_AUDIT=Administrator

# The audit password to connect to the database.DATABASEPWD_AUDIT=<password>

[Marketing Products]# This feature manually enables specified marketing products.Each marketing product# specified must be seperated by a comma.# For a custom install this field is used to enable thoseproducts which are different from a default new installation.

# Example: ENABLEMP=BusinessObjects.MySQL,BusinessObjects.WebTierComponentsENABLEMP=

# This feature manually disables specified marketing products.Each marketing product# specified must be seperated by a comma.# For a custom install this field is used to disable thoseproducts which are different from a default new installation.

# Example: DISABLEMP=BusinessObjects.MySQL,BusinessObjects.WebTierComponentsDISABLEMP=



[New Settings]# All uncommented settings are added here.DBTYPE_AUDIT="MySQL"


This script can now be used for future silent installations by including the filename and path in the command line as shown below:

./install.sh -r <filename> -I /<INSTALLDIR>/ -s /<SOURCEDIR>/

To run a scripted installation

You need to have a response residing in a known directory. TheMACHINENAME parameter must be specified in the response file if you arereplicating an installation. If the parameter is not specified, the local servername will be used by default.1. Mount the device that contains the installation files.

Note:If you run the install script without copying the files to a temporary location,you will be prompted to specify a temporary location for the install.

2. In the command-line type the following information:

install.sh -r <filename> -I /<INSTALLDIR>/ -s /<SOURCEDIR>/

• -r <filename> Specifies the name of the response file you want theinstallation setup to read for installation parameters.

• -I <INSTALLDIR> Specifies the installation directory for the scriptedinstallation.

• -s <SOURCEDIR> This optional command specifies the location of thecd directory. The source directory must point to the location of DISK_1in the installation DVD. If not specified, the DVD directory setting inthe response file will be used.

3. Press Enter to launch the installation.

Related Topics• Copying the product distribution to your machine on page 50



Scripted installation parameters

The table below lists the most common parameters used in BusinessObjectsEnterprise installation scripts. These parameters are saved in a file which isused to run scripted installations of BusinessObjects Enterprise on UNIX.To change the listed parameters, it is recommended that you create a newresponse file using ./install.sh and the -w parameter.

DescriptionParameter

Name of the machine on which to run thescripted installation. The setting overridesthe local server name. If not specified,the local machine name is used.

MACHINENAME="mymachine"

MACHINENAME

Path of the bobje directory automaticallysetup in the installation directory.

BOBJEDIR="<INSTALLDIR>/bobje/"BOBJEDIR

Path to the DISK_1 directory on the distri-bution DVD. This path defaults to theDVD directory.

CDDIR="<CD>/BusinessObjects/DISK_1"

CDDIR

Path to the directory containing the prod-uct license.

LICENSEDIR="<INSTALLDIR>/<LICENSEDIR/"

LICENSEDIR




The language setting used for the instal-lation setup.• en=English• chs=Simplified Chinese• cht=Traditional Chinese• de=German• es=Spanish• ko=Korean• nl=Dutch• jp=Japanese• pt=Portuguese• sv=Swedish• ru=Russian• fr=French• it=Italian• th=Thai• pl=Polish• da=Danish• no=Norwegian• sv=Swedish• pt=Portuguese

BOBJELANG="en"

BOBJELANG

Specifies the product activation keycodefor the product to be installed.

BOBJELICENSEKEY=XXXXX-XXXXXXX-XXXXXXX

BOBJELICENSEKEY

The product id key - same as the BOBJELICENSEKEY

PIDKEY =XXXXX-XXXXXXX-XXXXXXX

PIDKEY




Specifies the type of installation to per-form. This parameter supports the follow-ing options:• new• custom• webtier

INSTALLTYPE="new"

INSTALLTYPE

Specifies a comma-delimited list for theBusinessObjects Enterprise installationprogram operating modes. This parame-ter supports the following options:• install• modify• remove• integrated• interactive

INSTALLMODE=interactive,install

INSTALLMODE

Specifies the name of the local server

LOCALNAMESERVER=“myservername”LOCALNAMESERVER

Specifies to perform either a user or sys-tem installation.

BOBJEINSTALLLOCAL=“user”BOBJEINSTALLLOCAL




Specifies the language packs to install.Each language pack is specified in theshort format and is separated by a space.• en=English• zh_CN=Simplified Chinese• zh_TW=Traditional Chinese• de=German• es=Spanish• ko=Korean• nl=Dutch• jp=Japanese• pt=Portuguese• sv=Swedish• ru=Russian• fr=French• it=Italian• th=Thai• pl=Polish• da=Danish• no=Norwegian• sv=Swedish• pt=Portuguese

LANGPACKS_TO_INSTALL=“en fr”

LANGPACKS_TO_INSTALL

Specifies the BusinessObjects Enterpriseusername.

BOBJEUSERNAME=“username”BOBJEUSERNAME

Specifies to either install or not to installTomcat.

INSTALLTOMCAT=“yes”INSTALLTOMCAT




Specifies the connection port for theTomcat server.

CONNECTORPORT=“15037”CONNECTORPORT

Specifies the redirection port for theTomcat server.

REDIRECTPORT=“15034”REDIRECTPORT

Specifies the shutdown port for the Tom-cat server.

SHUTDOWNPORT=“15024”SHUTDOWNPORT

Specifies the path of the applicationserver directory if the server is being in-stalled. The path is automatically set us-ing the installation directory.

AS_DIR=“<INSTALLDIR>/bobje/tomcat/”

AS_DIR

Specifies the name of the applicationserver being installed.• Use tomcat55 for Tomcat• Use oas1013 for Oracle Application

Server 10g R3• Use weblogic9 for WebLogic 9.2• Use weblogic10 for WebLogic 10• Use websphere6 for WebSphere 6.1

AS_SERVER=“tomcat55”

AS_SERVER

Specifies the name of the current webapplication server instance.

AS_INSTANCE="localhost"AS_INSTANCE




Specifies virtual host to which the applica-tion must be bound.

AS_VIRTUAL_HOST="hostname"AS_VIRTUAL_HOST

Specifies the port used by the web appli-cation server.

AS_ADMIN_PORT="8080"AS_ADMIN_PORT

Specifies the account name used by theadministrator to access the web applica-tion server.

AS_ADMIN_USERNAME="admin"

AS_ADMIN_USERNAME

Password used by the administrator ac-count to access the web applicationserver.

AS_ADMIN_PASSWORD="pass"

AS_ADMIN_PASSWORD

Specifies that an administrator credentialmust be passed to access the web appli-cation server. This setting only valid forWebSphere 6 and Oracle.

AS_ADMIN_IS_SECURE="true"

AS_ADMIN_IS_SECURE

Specifies the action to perform on theapplication server. The available optionsare:• deploy• predeploy• none

WDEPLOYACTION=“deploy”

WDEPLOYACTION




Specifies whether or not to cluster to anexisting CMS.

CMSCLUSTER=“no”CMSCLUSTER

If clustering to a CMS, specifies the nameof the CMS .

CLUSTER_NAMESERVER=“name”CLUSTER_NAMESERVER

If clustering to a CMS, specifies the portnumber used by the CMS.

CLUSTERPORTNUMBER=“6400”CLUSTERPORTNUMBER

Specifies the type of database used bythe CMS. The available options are:• MySQL• DB2• Oracle• Sybase

DBTYPE=“MySQL”

DBTYPE

Specifies the service name for the CMS.

SERVICENAME=“BOE953”SERVICENAME

Specifies the username used to connect-ed to the database.

DATABASEUID=“username”DATABASEUID

Specifies the password used to connect-ed to the database.

DATABASEPWD=“password”DATABASEPWD




Specifies the name of the CMS server.

CMSNAMESERVER=“servername”CMSNAMESERVER

Specifies the port number used to com-municate with the CMS.

CMSPORTNUMBER=“14000”CMSPORTNUMBER

Specifies the password used to connectto the CMS.

CMSPASSWORD=“password”CMSPASSWORD

Specifies the node name for the ServerIntelligence Agent (SIA).

SIANODENAME=“name”

Note:Do not use spaces or non-alphanumericcharacters in a SIA node name.

SIANODENAME

Specifies the port used by the Server In-telligence Agent.

SIAPORTNUMBER=“14090”SIAPORTNUMBER

Specifies to or not to reinitialize thedatabase.

REINIT=“yes”REINIT

Specifies to or not to install MySQL asthe system database.

INSTALLMYSQL=“yes”INSTALLMYSQL




Specifies the port number used to com-municate with the MySQL database.

SERVICEPORT=“15036”SERVICEPORT

Specifies the name of the server hostingthe MySQL database.

MYSQLYHOSTNAME=“servername”MYSQLYHOSTNAME

Specifies the root password for theMySQL database.

MYSQLROOTPWD=“password”MYSQLROOTPWD

Specifies if auditing is or is not enabledfor the CMS.

AUDITINGENABLED=“yes”AUDITINGENABLED

Specifies the service audit name used bythe CMS.

SERVICENAME_AUDIT=“servicename”SERVICENAME_AUDIT

Specifies the port number used to com-municate with the auditing database.

SERVICEPORT_AUDIT=“12133”SERVICEPORT_AUDIT

Specifies the name of the server hostingthe MySQL auditing database.

MYSQLHOSTNAME_AUDIT=“servername”MYSQLHOSTNAME_AUDIT




Specifies the user name used to connectto the auditing database.

DATABASEUID_AUDIT=“username”DATABASEUID_AUDIT

Specifies the password used to connectto the auditing database.

DATABASEPWD_AUDIT=“password”DATABASEPWD_AUDIT

Specifies which specific products tomanually enable. Each product must beseparated by a comma. For a custom in-stallation this setting is used to enablethose products typically not installed in anew installation.

ENABLEMP=BusinessObjects.WebTierComponents,

-ENABLEMP

Specifies which specific products tomanually disable. Each product must beseparated by a comma. For a custom installation this setting is used to disablethose products typically not installed in anew installation.

DISABLEMP=ENABLEMP=BusinessObjects.WebTierComponents,

-DISABLEMP

Other automatically generated parameters

The following parameters are automatically generated parameters that shouldnot be modified in the .ini file.



Parameter name

PRODUCTID_NAME

BOBJEVERSION

PRODUCTID_VER

FUNCTION

LANGUAGES_TO_INSTALL

EXPANDSERVERS

Related Topics• To create a response file on page 103

Performing a silent installationYou can run a silent installation from the command line to automatically installBusinessObjects Enterprise on any machine in your system, without theinstallation program prompting for information during the installation. Toinstall silently, run the ./install.sh script, adding parameters that provideinformation for installation settings and directory paths.

This type of installation is particularly useful when you need to performmultiple installations. You can also use the silent installation script in yourown scripts. For example, if your organization uses scripts to install softwareon machines, you can add the silent BusinessObjects Enterprise installationcommand to your scripts.

The silent installation command consists of the ./install.sh script, followedby the location of the installation executable file, and a number of parametersthat provide information about the installation. For example:

The following example would perform an English new user installation withthe following configuration:

• BusinessObjects Enterprise

• Tomcat

• MySQL

• Auditor


Silent Installation7 Performing a silent installation

• Database reinitialized

./install.sh -c en -INSTALLDIR /program/business/boe_120 -BOBJELICENSEKEY00000-1111111-2222222-0000-BOBJEINSTALLLOCAL user -INSTALLTYPE new -CMSPORTNUMBER 13888

-DBTYPE MySQL -SERVICENAME boe -INSTALLMYSQL yes -DATABASEUID

username -DATABASEPWD sa -REINIT yes -MYSQLROOTPWD sa-SERVICENAME_AUDIT audit -DATABASEUID_AUDIT hsmith-DATABASEPWD_AUDIT sa123 -SIANODENAME=MyNode-SIAPORTNUMBER=6410 -INSTALLTOMCAT yes-TOMCATCONNECTORPORT 13890 -TOMCATREDIRECTPORT 13889-TOMCATSHUTDOWNPORT 13891 -AUDITINGENABLED yes-DASENABLED yes

Note:The example uses the most common parameters. You can choose anynumber of valid parameters, but it is good practice to keep the silentinstallation as simple as possible.

Note that when you run a silent installation, you need to run the commandonce for each DVD, but you only need to provide the full list of options forthe first DVD. For example, if the DVDs are on different drives, the commandscould look like the following:

./install.sh -s /mnt/cd1 -INSTALLDIR /mymachine/BOBJ/Enterprise120 -BOBJELICENSEKEY 00000-0000000-0000000-0000

-INSTALLTYPE new -BOBJEINSTALLLOCAL user -CMSPORTNUMBER 6401-DBTYPE Oracle -SERVICENAME tnsname -DATABASEUID userid-DATABASEPWD password -REINIT yes -SIANODENAME=MyNode-SIAPORTNUMBER=6410 -INSTALLTOMCAT yes-TOMCATCONNECTORPORT 8080 -TOMCATREDIRECTPORT 8443-TOMCATSHUTDOWNPORT 8005

./install.sh -s /mnt/cd2 -INSTALLDIR /mymachine/BOBJ/Enterprise120

./install -s /mnt/cd3 -INSTALLDIR /mymachine/BOBJ/Enterprise120

The following table lists the most common parameters used in a silentinstallation. To use a parameter, place it on the command line after the./install.sh command and the path for the installation files.

Note:Parameter values are case-sensitive.


7Silent InstallationPerforming a silent installation

DescriptionInstallation parameter

The location of the DVD used to run the installation.Replace filepath with the full path for the DVDdrive or other installation source directory. For ex-ample, -s /mnt/CD1/

-sfilepath

Specifies the directory where you want to installthe new BusinessObjects Enterprise components.Replace filepath with the full path for the instal-lation directory. For example, -INSTALLDIR/BOBJE/Enterprise120.

-INSTALLDIR filepath

Required to activate the product license for yourproduct.

-BOBJELICENSEKEY00000-0000000-0000000-0000

Enables you to install Dashboard and Analyticsservers without a keycode. The options are “yes”and “no”; the default setting is “no”.

Note:The Dashboard and Analytics servers will be dis-abled until you enter an appropriate keycodethrough the Central Management Console (CMC).

-DASENABLED




This option determines the language for the instal-lation. Replace languagecode with a languagecode for one of the supported languages:• en=English• zh_CN=Simplified Chinese• zh_TW=Traditional Chinese• de=German• es=Spanish• ko=Korean• nl=Dutch• jp=Japanese• ru=Russian• fr=French• it=Italian• th=Thai• pl=Polish• da=Danish• no=Norwegian• sv=Swedish• pt=Portuguese

-clanguage code

Specifies the Server Intelligence Agent (SIA) nodename to use for the installation.

Note:Do not use spaces or non-alphanumeric charactersin a SIA node name.

-SIANODENAME

Specifies the port used by the SIA.-SIAPORTNUMBER

Specifies the type of installation. The possible val-ues are:• new• custom• webtier

-INSTALLTYPE




This parameter is followed by a comma-separatedvalues (CSV) string of features that you do not wantto install. Note that this cannot be used in combina-tion with the -f option. See the mymenu.xml filein the setup directory on DISK_1 for a full list offeatures.

-xmymenu.xml

This parameter is followed by CSV string of fea-tures that you want to install. Note that this cannotbe used in combination with the -x option. See themymenu.xml file in the setup directory on DISK_1for a full list of features.

-f

Specifies which specific products to manually en-able. Each product must be separated by a comma.For a custom installation this setting is used to en-able those products typically not installed in a newinstallation.

-ENABLEMP

Specifies whether to perform a user or a systeminstallation. The options are user or system; useris the default.

-BOBJEINSTALLLOCAL

Specifies the name of an existing CMS to use foreither a custom or web tier installation.-CMSNAMESERVER

Specifies the port number for the Central Manage-ment Server. If not specified, the default is 6400.-CMSPORTNUMBER

Specifies the administrator password for an existingCMS to use in either a custom or web tier installa-tion.

-CMSPASSWORD

When installing a Central Management Server, youneed to specify the type of database you want touse. Possible values include:• Oracle• DB2• Sybase• MySQL

-DBTYPE




When installing a Central Management Server, youcan specify whether or not to install and configurea new MySQL database. The options are yes orno; no is the default.

-INSTALLMYSQL

Specifies the name of the machine hosting theMySQL server.-MYSQLHOSTNAME

Specifies the service name used to connect to theCentral Management Server database.-SERVICENAME

Specifies the port number used to connect to theCentral Management Server database. This is re-quired only for MySQL databases.

-SERVICEPORT

Specifies the user ID used to connect to the CentralManagement Server database. This option cannotbe set to root if the -INSTALLMYSQL option is setto yes.

-DATABASEUID

Specifies the password used to connect to theCentral Management Server database. If this optionis not specified, it defaults to blank.

-DATABASEPWD

Specifies the password used for the root accountwhen setting up the database. When the -IN-STALLMYSQL option is set to yes, you must alsospecify the -MYSQLROOTPWD option.

-MYSQLROOTPWD

Specifies if the an auditing database will be config-ured the during your installation setup. The twooptions are yes and no. If this option is not speci-fied, it defaults to no.

-AUDITINGENABLED

Modifies the name of the MySQL auditingdatabase, otherwise, the default name ofBOE120_Audit will be used

-SERVICENAME_AUDIT

Use this parameter to pass the user ID for the au-diting database.-DATABASEUID_AUDIT




Specifies the password for the auditing databaseserver.-DATABASEPWD_AUDIT

Specifies the host name for the MySQL server foryour auditing database.-MYSQLHOSTNAME_AUDIT

Specifies an existing auditing database type fromone of the following options:• Oracle• DB2• Sybase• MySQL

-DBTYPE_AUDIT

Specifies the port for the MySQL auditing databaseserver.-SERVICEPORT_AUDIT

Specifies the name of the machine hosting theSybase auditing database.-SYBASEHOSTNAME_AUDIT

Specifies the port number used by the Sybase au-diting database.-SYBASEPORT_AUDIT

Specifies whether to reinitialize the Central Man-agement Server database. The options are yes orno;yes is the default.

-REINIT

Specifies whether or not to cluster the CentralManagement Server with an existing CMS. Theoptions are yes or no; no is the default.

Note:This option is used for a custom installation.

-CLUSTERCMS

Specifies the name of the Central ManagementServer for the system you are expanding. For acustom installation, if the -CLUSTERCMS option isset to yes, then you need to specify the name ofthe CMS you want to cluster with.

-CLUSTER_NAMESERVER




Specifies the port number of the Central Manage-ment Server for the system you are expanding.The default is 6400. For a custom installation, ifthe -CLUSTERCMS option is set to yes, then youneed to specify the port number of the CMS youwant to cluster with. The default is 6400.

-CLUSTERPORTNUMBER

Specifies if Tomcat is to be installed as the webapplication server. The default value is no.-INSTALLTOMCAT

The port number that Tomcat uses to connect. Thedefault is 8080.-TOMCATCONNECTORPORT

The port number that Tomcat uses to redirect. Thedefault is 8443.-TOMCATREDIRECTPORT

The port number that Tomcat uses to shut down.The default is 8005.-TOMCATSHUTDOWNPORT



After InstallingBusinessObjects Enterprise

8

Using ccm.sh to start the BusinessObjectsEnterprise servers

The ccm.sh script provides you with a command-line interface to the variousBusinessObjects Enterprise server components. For more information aboutthis script and others that are installed on your system, see theBusinessObjects Enterprise Administrator's Guide.

In BusinessObjects Enterprise, the installation setup program starts andenables servers automatically. The following information is included only asa reference.

To view additional help on ccm.sh

The ccm.sh script provides a detailed description of its command-line options.To see the help, issue the following command:

<INSTALLDIR>/bobje/ccm.sh -help | more

To manually start and enable servers1. Go to the bobje directory that was created by the installation:

cd <INSTALLDIR>/bobje

2. Start the Server Intelligence Agent (SIA) by typing the following command:

./ccm.sh -start sia

3. Open a web browser to the URL of your Central Management Console(CMC) deployment on your web application server. For example

http://<SERVERNAME>:<PORTNUMBER>/CmcApp

4. Log on to the CMC by providing your BusinessObjects Administratorcredentials.

5. Navigate to the "Servers" page.6. Select the server you want to start.


After Installing BusinessObjects Enterprise8 Using ccm.sh to start the BusinessObjects Enterprise servers

7. Select Start Server.

The server should now start.

To check if the CMS is runningAfter installing BusinessObjects Enterprise, you can validate if the CentralManagement Server (CMS) is running.

1. CD to the bobje directory in your installation.2. Enter ./ccm.sh -display -cms <hostname>:<port>.

Note:It is not necessary to provide the CMS hostname and port if you'vespecified the default port during installation.

A list of running servers is displayed. Make sure the CMS is running.

Post install component deploymentWhen you install Tomcat as part of your BusinessObjects Enterpriseinstallation, BusinessObjects Enterprise web applications (e.g. InfoView,CMC) and the BusinessObjects Enterprise SDK are installed, configured,and deployed for you.

InfoView is a web-based interface that end users access to view, schedule,and keep track of published reports. The Central Management Console(CMC) allows you to perform user and server management tasks such assetting up authentication, starting servers, and adding users and groups.The BusinessObjects Enterprise SDKs are used by many BusinessObjectsEnterprise components and are also used to simplify the development ofcustom BusinessObjects Enterprise applications.

If you do not install Tomcat when you install BusinessObjects Enterprise,these components must be configured and deployed before you use them.You can either deploy the components manually or use the wdeploy tool.For more information, see the BusinessObjects Enterprise Web ApplicationDeployment Guide for UNIX.

For more information about the system architecture of an installation ofBusinessObjects Enterprise, see the architecture chapter of theBusinessObjects Enterprise Administrator's Guide.


8After Installing BusinessObjects EnterpriseTo check if the CMS is running

Note:If you have a firewall between the machine running your web applicationserver and your other BusinessObjects Enterprise servers, you must performadditional system configuration. See the section on how to configure firewalls,in your BusinessObjects Enterprise Administrator's Guide.

Setup for performance managementBefore users in your organization can start working with performancemanagement, you need to do the following:

• Create the performance management repository – this repository storesthe metrics, goals, sets, and calendars that users leverage for theirperformance management analysis.

• Define system users – this enables the performance managementapplication engines.

• Define connections to the metrics universes and push those universesto the performance management repository – this makes the metadatafor measures and dimensions available to users for metric creation.

.

To set up performance management

1. Log into InfoView, then click Open.

A drop-down list is displayed.

2. Select Dashboard & Analytics Setup.The Dashboard & Analytics Setup page is displayed.

3. Follow the on-screen instructions.

Troubleshooting starting performance management

If, when you launch performance management, you receive an error messagesaying that you cannot connect to performance management, this may meanone of the following:


After Installing BusinessObjects Enterprise8 Setup for performance management

• Some of the performance management servers are stopped or disabled.

• The Initialization User that creates the performance management serverproxies may be defined inconsistently in the CMS, InfoView, and theInitConfig.properties file.

To verify performance management servers

1. Log into the Central Management Console (CMC), and then click Servers.2. Verify that all the performance management servers are started.3. If a server is not running, select the check box next to the server name,

and then click Start.4. Make sure that all servers are enabled.

If a server is not enabled, select the check box next to the server name,and then click Enable.

To verify the Initialization User

1. On your performance management server, open the InitConfig.properties file and verify that the Initialization user name and passwordmatch those in the CMS.

This file is at:

<INSTALLDIR>/bobje/performance_management_120

The strings to search for are:

• initialization.User=

• initialization.Password=

2. Log into InfoView, and then click the Preferences button on the InfoViewtoolbar.

3. Click the Performance Management tab, and then check the name ofthe initialization logon user in the Change initialization logon usersection is the same as the user name specified in the InitConfig.properties file.

4. Log into the Log into the Central Management Console (CMC), and thenclick Users.


8After Installing BusinessObjects EnterpriseSetup for performance management

5. Check that the user defined in the InitConfig.properties is listedamong the users.

6. From the CMC home page, click Settings > Rights and check that theinitialization user has the appropriate rights.

Note:For security reasons, it is recommended that you do not provide a realuser ID for the initialization user. The default user ID is PMUser.

You need to restart the performance management servers.

7. From the CMC home page, click Servers > Start Servers to restart allservers.

If you are using performance management from a client machine - differentfrom the machine hosting the performance manager server - you need torestart your computer.


After Installing BusinessObjects Enterprise8 Setup for performance management

Language Packs

9

About language packsA language pack is a resource package that gives a BusinessObjectsEnterprise system the ability to interact with users in a specific language. Anindividual language is known as a locale.

You can install as many different language packs as you want. The defaultlanguage pack, English, is always installed.

English language fall-back

In the event of a localization error, such as a missing, corrupted, or uninstalledlanguage pack, BusinessObjects Enterprise products fall back to using thedefault English language. If a preferred language has not been set in theProduct Locale drop-down, BusinessObjects Enterprise defaults to using thelocale of the installed operating system. If a language pack correspondingto the locale of the operating system is not found, the default English is used.

Product locale changes

Product Locale changes are immediately reflected in the current product'sinterface, reports, and help. Where multiple client applications are installed,the selected Product Locale is only displayed when client is next started.For example, setting the Crystal Report Designer product locale to Japanesewill cause the Business Intelligence Modeler client to also display inJapanese. However, if the Business Intelligence Modeler is running at thetime of the change, it must be restarted in order for the change to take effect.

Installing language with complex deployments

If your organization uses a BusinessObjects Enterprise deployment withmore than one server, you will need to deploy language packs to each serverindividually.


Language Packs9 About language packs

Installing language packsLanguage packs can be installed either during the initial installation ofBusinessObjects Enterprise, or post-install using a dedicated language packinstallation program. The installation program is a script that adds thelocalized language resources to your Business Objects software deployment.

English is the default option during the installation of BusinessObjectsEnterprise, but administrators can opt to install any or all of the other availablelanguages. Additional languages can also be installed onto an existing systemby downloading the appropriate language pack from the Business Objectssupport web site at http://technicalsupport.businessobjects.com.

In the event of an operational problem with a language pack, BusinessObjectsEnterprise will default back to English localization. Because of this fall-backsystem, English cannot be deselected as an installable option during theinstallation of BusinessObjects Enterprise.

Note:An error message will be displayed if a language pack detects that it isincompatible with a previously installed version of BusinessObjects Enterprise.

Locating language packs

Language packs can be found in the langs folder of the BusinessObjectsEnterprise for UNIX distribution package.

Alternatively, language packs can be downloaded from the Business Objectstechnical support site at http://technicalsupport.businessobjects.com.

To install language packs

Before installing a language pack, your BusinessObjects Enterprise servermust be running and patched to the required revision level. You will be askedfor CMS administrator credentials. If any part of your BusinessObjectsEnterprise deployment is not patched to the required software version, thelanguage pack installation will abort and must be reapplied after the systemhas been patched to the correct level. Please review the requirements for


9Language PacksInstalling language packs

http://technicalsupport.businessobjects.com

http://technicalsupport.businessobjects.com

language packs at the Business Objects customer support site: http://support.businessobjects.com/documentation/supported_platforms.

Note:Language packs do not require a keycode.

1. Open the Central Management Console (CMC) and ensure that the serverprocesses are running.

2. Locate the language pack to install under BUSINESS_OBJECTS_DISTRIBUTION_CD_DIR/langs/LANGUAGE/DISK_1.Replace LANGUAGE with the ISO code of the language you are installing.

3. Run the install.sh script with the first argument set to the location ofthe BusinessObjects Enterprise installation directory.For example: install.sh /opt/bobj

4. Press y to accept the license agreement.5. Enter the CMS hostname, port number, and administrator password into

the labeled fields and press Enter.6. Press Enter after you have confirmed the location of the BusinessObjects

Enterprise install directory.

Once the installation is complete, you will be able to choose the installedlanguage from the Options dialog window in BusinessObjects Enterpriseapplications.

Note:

• All fix packs or other updates to BusinessObjects Enterprise released ona date after the language pack release date must be re-applied to ensurethat updated functionality is maintained.

• Language packs must be re-installed after you have added or removeda component from your BusinessObjects Enterprise deployment.

Installing language packs across a BusinessObjectsEnterprise deployment

You can install language packs with one command by specifying parameterson the command-line. This is referred to as a "silent" installation. Whenparameters are supplied on the command-line the installation will not promptfor information.


Language Packs9 Installing language packs

http://support.businessobjects.com/documentation/supported_platforms

http://support.businessobjects.com/documentation/supported_platforms

The command-line syntax for a silent install is as follows:

install.sh BUSINESS_OBJECTS_HOME_DIRINSTALLMODE=silent,installCMSNAMESERVER=CMS_HOSTNAMECMSPORTNUMBER=PORT_NUMBERCMSPASSWORD=CMS_PASSWORD

Replace BUSINESS_OBJECTS_HOME_DIR with the full path of yourBusinessObjects Enterprise installation. The following table details each ofthe parameters used by install.sh.

DescriptionExpected argu-ment

Parameter

Switch to enable silent install mode"silent"INSTALLMODE

Enter the name of your CMS ma-chine.

CMS HostnameCMSNAMESERVER

CMS port number.Port number forCMS

CMSPORTNUMBER

The password for your CMS server.CMS admin pass-word

CMSPASSWORD

You must also specify parameters for your web application server. Thespecific parameters that you must use depend on the web application serverthat you use.

For example, on WebLogic 9.2:

$ ./install.sh /opt/bobjeINSTALLMODE=silent,installCMSNAMESERVER=myserver1CMSPORTNUMBER=6400CMSPASSWORD=mypasswordAS_SERVER=weblogic9AS_DIR=/opt/bea/user_projects/domains/base_domainAS_INSTANCE=AdminServerAS_ADMIN_PORT=7001AS_ADMIN_USERNAME=weblogicAS_ADMIN_PASSWORD=weblogic


9Language PacksInstalling language packs

To uninstall language packs, use the wdeploy undeployall command toremove all web applications, then wdeploy deployall to re-deploy webapplications without the language packs.

For example, the following command runs undeployall for a WebLogic 10server:

wdeploy.sh weblogic10-Das_dir=/opt/bea/user_projects/domains/base_domain-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_username=weblogic-Das_admin_password=weblogicundeployall

Followed by:

wdeploy.sh weblogic10-Das_dir=/opt/bea/user_projects/domains/base_domain-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_username=weblogic-Das_admin_password=weblogicdeployall

For more information on using wdeploy, see the BusinessObjects EnterpriseWeb Application Deployment Guide for UNIX.

Selecting a languageOnce installed, BusinessObjects Enterprise products detect the existenceof the language pack, and users can choose a language from a list of installedlanguages found in the Product Locale drop-down list of the CMCPreferences section of the CMC Preferences, or under the Options dialogbox on the toolbar or application menu in other BusinessObjects Enterpriseproducts. Command-line utilities use the LANG environment variable todetermine which language to use.

Each language listed in the Product Locale drop-down is displayed in itsnative localization, rather than the currently employed language. For example,the German language pack is always displayed as Deutsch, rather than asGerman in English or Allemand in French.


Language Packs9 Selecting a language

Note:Application shortcut keys are language neutral and do not change, regardlessof which language is in use. For example, Ctrl+S is always mapped to theSave command, regardless of the localized name for the Save function.

To uninstall language packs1. Run the ./AddOrRemoveProcducts.sh script.2. On the "Choose Product to Modify" screen, select the language pack that

you want to uninstall, and press Enter.3. On the "Enter information for existing CMS" screen, specify the CMS

Hostname, CMS Port, and Existing CMS Administrator Password, andthen press Enter.

4. Press Enter to confirm the removal of the language pack.


9Language PacksTo uninstall language packs


Language Packs9 To uninstall language packs

Maintaining your Installation

10

Addingperformancemanagement to yourinstallation

You can add performance management servers and binaries to yourBusinessObjects Enterprise installation.

You must run the AddOrRemoveProducts.sh script to add the performancemanagement resources. The script is installed to the directory of yourinstallation.

To add performance management

To add performance management resources, you must have BusinessObjectsEnterprise installed on a UNIX machine.

Run the following procedure if your current BusinessObjects Enterpriseinstallation does not have the required performance management resources.

1. From the installation directory run ./AddOrRemoveProducts.sh.The "Add or Remove Programs" screen is displayed.

2. Select BusinessObjects Enterprise XI 3.1 and press Enter.The "Add Features or Uninstall Current Product" screen is displayed.

3. Select Add Dashboards and Analytics Servers and press Enter.You are prompted to enter Central Management Server (CMS) connectiondetails.

4. Specify the following information:


Maintaining your Installation10 Adding performance management to your installation

DescriptionField name

The system name for the CMS hostmachine

CMS Hostname

Port used by the CMSCMS Port

Administrator password used to ac-cess the CMS

Existing CMS Administrator Pass-word

If your previous installation was not configured to deploy web applicationsto a specific web application server, skip to step 8. Otherwise, you willbe prompted to provide the web application server configuration details.

5. Select your existing web application server and press Enter. You optionsare the following:• Tomcat 5.5• WebLogic 10• WebLogic 9.2• WebSphere 6.1• Oracle Application Server 10g R3A configuration screen for your selected web application server isdisplayed.

6. Provide the requested configuration details for your web application server.



10Maintaining your InstallationAdding performance management to your installation

Information required for installationWeb ApplicationServer

• Instance to install to: Name of the current web application serverinstance (e.g. “localhost”).

• Application server Installation directory: The directory where theweb application server is installed (e.g. <INSTALLDIR>/wdeploy/appserver/Tomcat5520).

Apache Tomcat 5.5

• Admin port: Administration port of the application server - manda-tory for WebLogic (e.g. “7001”).


• Admin login: Password for account with administration rights to theapplication server - mandatory for WebLogic.

• Instance to install to: Name of the current web application serverinstance (e.g. “ mserver1”).

• Application server domain root directory: The WebLogic domainroot directory (e.g /bea/user_projects/domains/base_domain).

WebLogic 9.2

• Admin port: Administration port of the application server - manda-tory for WebLogic (e.g. “7001”).



• Instance to install to: Name of the current web application serverinstance (e.g. “ mserver1”).

• Application server domain root directory: The WebLogic domainroot directory (e.g. /bea/weblogic10/user_projects/domains/base_domain).

WebLogic 10

WebSphere 6.1




• Admin port: Administration port of the WebSphere applicationserver - the SOAP port.



• Instance to install to: Name of the current web application serverinstance (e.g. “ server1”).

• Virtual host: The virtual host to which the application must be bound.• Admin is secure (y/n): Select this option to enable security requiring


Note:If Admin is secure is not selected you do not need to specify ausername or a password.

• Application Server Installation Directory: The directory where theweb application server is installed (e.g./IBM/WebSphere/AppServer).



10Maintaining your InstallationAdding performance management to your installation


• Admin port: Administration port of the application server - manda-tory for Oracle 10g R3 (e.g. “6003”) .This should be the Requestport of the <notifi-cation-server> element in the opmn.xmlfile.





• Instance to install to: Name of the current web application serverinstance (e.g. “ home”).

• Application server Installation directory: The directory where theweb application server is installed (e.g. /product/10.1.3/OracleAS_1).

• Server Name: Name of the target application server (e.g. "myserv-er.domain.com").

• Group Id: Name of the server group to which the target applicationbelongs (e.g. "Default_group").

.

7. Press Enter to submit your configuration details.The installation verifies the configuration details. Once the verification iscomplete, you can start the installation process.

8. Specify the directory where the BusinessObjects Enterprise installationmedia is located.

9. Select Yes and press Enter.The Dashboard and Analytics resources are added to your installation.

If you have been provided with a new product keycode to activateperformance management, you will have to provide the code to start the newservers.



Before users in your organization can start working with performancemanagement, you need to do the following:

After adding performance management to the installation, you need to dothe following:

• Create a performance management repository – this repository storesthe metrics, goals, sets, and calendars used for performance managementanalysis.

• Specify which users can access performance management resources.

• Define connections between the metrics used for performancemanagement and the performance management repository.

For more detailed information please consult the Dashboard and AnalyticsSetup Online Help.

The installation log fileThe installation log files contains information on all the parameter settingsused in a BusinessObjects Enterprise installation. The log files can be usedas a reference or to troubleshoot installation errors. The name of the initiallog files are BusinessObjects.12.1.0.log and BusinessObjects.12.1.0.log.summary. The BusinessObjects.12.1.0.log filecontains detailed information on installation and deployment. Both files aresaved under the following directory: <INSTALLDIR>/setup/logs/.

Uninstalling BusinessObjects Enterprisefrom UNIX

Before you can remove BusinessObjects Enterprise from your UNIX machine,you must run the AddOrRemoveProducts.sh script. The script is installed tothe directory of your installation and is used to add or removeBusinessObjects Enterprise products or components.

This script stops all BusinessObjects Enterprise servers and processes. Itthen deletes the files copied from the product DVD during your originalinstallation of BusinessObjects Enterprise.


10Maintaining your InstallationThe installation log file

A BusinessObjects Enterprise installation creates a number of additionalfiles on your system. When you uninstall BusinessObjects Enterprise theseadditional files and any files created by the system or by users afterinstallation will not be removed. The files that remain include log files createdby BusinessObjects Enterprise. These log files can be useful for diagnosingproblems with previous installations.

To uninstall BusinessObjects Enterprise

Before removing BusinessObjects Enterprise from your UNIX system, youshould uninstall all language packs used by the installation.

To uninstall BusinessObjects Enterprise:

1. From the installation directory run ./AddOrRemoveProducts.sh.The "Add or Remove Programs" screen is displayed.

2. Select BusinessObjects Enterprise and press Enter.The "Add Features or Uninstall Current Product" screen is displayed.

3. Select Uninstall Product and press Enter.A confirmation screen is displayed.

4. Select Yes and press Enter.The uninstallation process begins.

To completely remove all BusinessObjects Enterprise files, perform an rm-Rf command on the bobje directory.

If you performed a system installation, you must also delete the run controlscripts from the appropriate /etc/rc# directories.

Related Topics• To uninstall language packs on page 141


Maintaining your Installation10 Uninstalling BusinessObjects Enterprise from UNIX

More Information

A

LocationInformation Resource

http://www.sap.comSAP BusinessObjects productinformation

Select http://help.sap.com > SAP BusinessObjects.

You can access the most up-to-date documentation cover-ing all SAP BusinessObjects products and their deploymentat the SAP Help Portal. You can download PDF versionsor installable HTML libraries.

Certain guides are stored on the SAP Service Marketplaceand are not available from the SAP Help Portal. Theseguides are listed on the Help Portal accompanied by a linkto the SAP Service Marketplace. Customers with a mainte-nance agreement have an authorized user ID to accessthis site. To obtain an ID, contact your customer supportrepresentative.

SAP Help Portal

http://service.sap.com/bosap-support > Documentation• Installation guides: https://service.sap.com/bosap-inst

guides• Release notes: http://service.sap.com/releasenotes

The SAP Service Marketplace stores certain installationguides, upgrade and migration guides, deployment guides,release notes and Supported Platforms documents. Cus-tomers with a maintenance agreement have an authorizeduser ID to access this site. Contact your customer supportrepresentative to obtain an ID. If you are redirected to theSAP Service Marketplace from the SAP Help Portal, usethe menu in the navigation pane on the left to locate thecategory containing the documentation you want to access.

SAP Service Marketplace

https://boc.sdn.sap.com/

https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibraryDeveloper resources


More InformationA

http://www.sap.com

http://help.sap.com/

http://service.sap.com/bosap-support

https://service.sap.com/bosap-instguides

https://service.sap.com/bosap-instguides

http://service.sap.com/releasenotes

https://boc.sdn.sap.com/

https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibrary

LocationInformation Resource

https://www.sdn.sap.com/irj/boc/businessobjects-articles

These articles were formerly known as technical papers.

SAP BusinessObjects articleson the SAP Community Net-work

https://service.sap.com/notes

These notes were formerly known as Knowledge Base ar-ticles.

Notes

https://www.sdn.sap.com/irj/scn/forumsForums on the SAP Communi-ty Network

http://www.sap.com/services/education

From traditional classroom learning to targeted e-learningseminars, we can offer a training package to suit yourlearning needs and preferred learning style.

Training


The SAP Support Portal contains information about Cus-tomer Support programs and services. It also has links toa wide range of technical information and downloads.Customers with a maintenance agreement have an autho-rized user ID to access this site. To obtain an ID, contactyour customer support representative.

Online customer support

http://www.sap.com/services/bysubject/businessobjectsconsulting

Consultants can accompany you from the initial analysisstage to the delivery of your deployment project. Expertiseis available in topics such as relational and multidimensionaldatabases, connectivity, database design tools, and customized embedding technology.

Consulting


AMore Information

https://www.sdn.sap.com/irj/boc/businessobjects-articles

https://service.sap.com/notes

https://www.sdn.sap.com/irj/scn/forums

http://www.sap.com/services/education





More InformationA

IndexAadding performance management 144AddOrRemoveProducts.sh 149after installation 131automated startup on UNIX 69, 90, 100

BBobjEnterprise120 69, 90, 100BusinessObjects Enterprise

documentation 8installation overview 14network requirements 16new features 11uninstalling 149, 150

Cccm.sh 130checking CMS 131checklist for installation 48CMS 131copying the product distribution 50custom or expand installation 24

available features 72

Ddatabase

installing MySQL 29preparing your existing 45

database requirementscharacter encoding 28CMS overview 28

database requirements (continued)DB2 33MySQL 44Oracle 37Sybase 40

database server optionstested database servers 29

database server preparations 45database, CMS 32DB2 32deployment

documentation 8deployment options

install Tomcat 63, 84, 94manual deployment 63, 84, 94select supported web application 63, 84,

94deployments, complex

installing language packs 136DVD 50

copying to your machine 50running the install from 50

Eenabling servers, with ccm.sh 130environment variables

DB2 34MySQL 44Oracle 37, 44Sybase 41

Ffirewalls 20


Iinstall.sh 49, 51installation

client tools 26modes 26running scripted 109silent 26types 23web application server 46

installation checklist 48installation log file 149installation setup

accepting license agreement 53clustering servers 81clustering to a CMS 83, 93CMS administrator password 59, 77configuring existing database 60configuring existing server 65, 85, 95configuring MySQL installation 62configuring Tomcat 64, 85, 95enable servers 58entering product keycode 53install MySQL 59installation directory 53installing language packs 54mounting files 52selecting installation type 55selecting new 58selecting setup language 52selecting user or system 55selecting web application server option 63,

84, 94Server Intelligence Agent 63, 81specifying CMS clustering 78specifying CMS port 59, 77starting the installation 68, 82, 89, 99use existing database 59

installation typeuser vs system 20web tier 93

installation types 23, 25custom or expand 24new 23web tier 25

installingon UNIX 49, 51

Llanguage packs

definition 136English fallback 136fallback to English 136installation on UNIX 137installing 137locale 136locating 137manual deployment 136Product Locale 136selecting locale 136, 140silent mode 138uninstalling 141

log fileinstallation 149

MMySQL

installing as database 29

Nnetwork requirements 16new installation 23

OOracle 32


Index

Pperformance management

adding to installation 144AddOrRemoveProducts.sh 144setup 132

post install deployments 131preparing for installation 48preparing your database server 45Publishing Wizard 49

Rresponse file

creating 103parameter list 110sample 104

Sscripted installation 102

parameter list 110running 109

server communicationmultiple NIC hosts 21set up 21

Server Intelligence Agentspecifying node name 63, 81specifying port 63, 81

servers, starting with ccm.sh 130silent installation 102, 120Sybase 32system installation on UNIX 69, 90, 100system requirements 15

TTesting MySQL database environment variables

44

to validate after installation 131Tomcat

specifying port numbers 64, 85, 95

UUnicode 32uninstalling

AddOrRemoveProducts.shrunning 150

procedure 150uninstalling from UNIX 149UNIX 17

character set translation 17creating login environment 19environment 18host name requirements 20network requirements 20permissions 16required commands and utilities 18setting the locale 17setting up your system 17user vs system installation 20

Wweb application server

configuring existing server 65, 85, 95configuring Tomcat 64, 85, 95initial installation 46

web tier 25web tier installation

available features 92clustering to a CMS 83, 93selecting deployment option 63, 84, 94

what's new 11


Index


Index

Xi3-1 Bip Install Unix En

Documents

Transcript of Xi3-1 Bip Install Unix En