xi3 bip install unix en

BusinessObjects Enterprise XI 3.0Installation and Configuration Guidefor UNIX

BusinessObjects Enterprise XI 3.0

unix

© 2008 Business Objects. All rights reserved. Business Objects owns the followingU.S. patents, which may cover products that are offered and licensed by Business

Copyright

Objects: 5,295,243; 5,339,390; 5,555,403; 5,590,250; 5,619,632; 5,632,009;5,857,205; 5,880,742; 5,883,635; 6,085,202; 6,108,698; 6,247,008; 6,289,352;6,300,957; 6,377,259; 6,490,593; 6,578,027; 6,581,068; 6,628,312; 6,654,761;6,768,986; 6,772,409; 6,831,668; 6,882,998; 6,892,189; 6,901,555; 7,089,238;7,107,266; 7,139,766; 7,178,099; 7,181,435; 7,181,440; 7,194,465; 7,222,130;7,299,419; 7,320,122 and 7,356,779. Business Objects and the Business Objectslogo, BusinessObjects, Business Objects Crystal Vision, Business Process OnDemand, BusinessQuery, Cartesis, Crystal Analysis, Crystal Applications, CrystalDecisions, Crystal Enterprise, Crystal Insider, Crystal Reports, Crystal Vision,Desktop Intelligence, Inxight, the Inxight Logo, LinguistX, Star Tree, Table Lens,ThingFinder, Timewall, Let There Be Light, Metify, NSite, Rapid Marts, RapidMarts,the Spectrum Design, Web Intelligence, Workmail and Xcelsius are trademarks orregistered trademarks in the United States and/or other countries of BusinessObjects and/or affiliated companies. Business Objects is an SAP company. SAPis the trademark or registered trademark of SAP AG in Germany and in severalother countries. All other names mentioned herein may be trademarks of theirrespective owners.

Business Objects products in this release may contain redistributions of softwarelicensed from third-party contributors. Some of these individual components may

Third-partyContributors

also be available under alternative licenses. A partial listing of third-partycontributors that have requested or permitted acknowledgments, as well as requirednotices, can be found at: http://www.businessobjects.com/thirdparty

2008-06-02

ContentsGetting Started 9Chapter 1

About this documentation..........................................................................10Who should read this documentation .......................................................10BusinessObjects Enterprise guides...........................................................10What is BusinessObjects Enterprise?.......................................................12What's new in the BusinessObjects Enterprise Installation and Configurationguide? .......................................................................................................12

Preparing to Install BusinessObjects Enterprise 15Chapter 2

Installation overview..................................................................................16System requirements ..........................................................................16UNIX permissions.................................................................................17Setting up your UNIX system...............................................................20Setting up server communication.........................................................23

Installation Scenarios.................................................................................25New installation....................................................................................26Custom or Expand installation .............................................................26Web tier installation .............................................................................27Client Tools installation ........................................................................28Silent installation .................................................................................28Side-by-side installation.......................................................................29

CMS System and Auditing Database Requirements.................................30Database requirements........................................................................30Using a supported database server.....................................................30Using MySQL.......................................................................................32Setting up an empty database for the CMS.........................................32

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX 3

Setting up a database account for BusinessObjects Enterprise .........34Preparing your CMS System Database server..........................................35

Prerequisites for database preparation................................................35Preparing your existing database server..............................................35MySQL database setup requirements..................................................38DB2 database setup requirements.......................................................38Oracle database setup requirements...................................................40Sybase database setup requirements..................................................42

Providing and verifying connectivity to the CMS database........................43To verify Sybase native connectivity through a server name...............44To verify Oracle native connectivity through a TNS.............................46To verify DB2 native connectivity through a database alias.................48

Before you deploy web applications..........................................................50

Beginning the Installation of BusinessObjects Enterprise 51Chapter 3

Installation checklist...................................................................................52Installation overview..................................................................................53Setting up product distribution...................................................................53

Running the product distribution directly from a CD.............................54Copying the product distribution to your machine................................54

Beginning your installation.........................................................................55To begin your installation......................................................................56To accept the license agreement.........................................................57Entering Product Keycode....................................................................57Specifying the installation directory......................................................57Installing language packs.....................................................................57To select user or system installation....................................................58Selecting an installation type................................................................59

4 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Contents

New Installation 61Chapter 4

Performing a new installation.....................................................................62To perform a new installation................................................................62To configure the new CMS ..................................................................63To specify a system database option...................................................63To enter Server Intelligence Agent information....................................67To select a web application server configuration option.......................67To start the installation .........................................................................72

Finishing a system installation ..................................................................73

Custom or Expand Installation 75Chapter 5

Performing a custom installation...............................................................76Features available in a custom installation..........................................76

To perform a Custom or Expand installation..............................................79To install only the server components..................................................80Installing only the Web Tier Components.............................................86

Finishing a system installation ..................................................................93

Web Applications Installation 95Chapter 6

Performing web tier installations................................................................96To perform a web tier installation .........................................................96To cluster web tier features to a CMS..................................................97To select a web application server configuration option.......................98To configure the Tomcat installation.....................................................98To configure your existing web application server................................99To start the installation .......................................................................102Finishing a system installation ...........................................................103


Contents

Silent Installation 105Chapter 7

Overview..................................................................................................106Performing a scripted installation............................................................106

To create a response file....................................................................107To run a scripted installation...............................................................107Scripted installation parameters.........................................................108

Performing a silent installation.................................................................117

After Installing BusinessObjects Enterprise 125Chapter 8

Using ccm.sh to start the BusinessObjects Enterprise servers...............126To manually start and enable servers................................................126

Post install component deployment.........................................................126Setup for performance management ......................................................127

To set up performance management.................................................128Troubleshooting starting performance management..........................128

Language Packs on UNIX 131Chapter 9

About language packs ............................................................................132English language fall-back ......................................................................132Product locale changes ..........................................................................132Selecting a language ..............................................................................132Installing language and complex deployments .......................................133Installing language packs on UNIX systems ..........................................133Locating language packs ........................................................................134To install language packs ........................................................................134Installing language packs across a BusinessObjects Enterprise deployment.................................................................................................................135To uninstall language packs ...................................................................136


Contents

Maintaining your Installation 139Chapter 10

Uninstalling BusinessObjects Enterprise from UNIX...............................140To uninstall BusinessObjects Enterprise............................................140

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

The installation log file ............................................................................146

Post Installation Web Application Deployment 147Chapter 11

Overview of post install deployment........................................................148Before you deploy web applications........................................................149Deploying with wdeploy...........................................................................149

Prerequisites for using wdeploy.........................................................149Overview for using wdeploy...............................................................150How to use wdeploy...........................................................................151Options for using wdeploy..................................................................155After deploying web applications........................................................156Deploying to web application servers with wdeploy...........................156To deploy web applications on a remote machine ............................182

Manually deploying to a web application server......................................185BusinessObjects Enterprise WAR files..............................................185WAR file context roots........................................................................186Guidelines for deploying WAR files....................................................187To manually deploy web applications.................................................188To prepare for manual deployment on a remote machine..................189After deploying web applications........................................................192Deploying with the Administration console.........................................193

Deployment Scenarios 207Chapter 12

Overview of deployment scenarios..........................................................208


Contents

Desktop client to server scenario............................................................208Desktop client to server overview .....................................................208Summary of required tasks................................................................209Deploying the client to server scenario..............................................210

Basic N-tier scenario................................................................................226N-tier scenario overview.....................................................................226Summary of required tasks................................................................227Deploying the basic N-tier scenario...................................................227

Get More Help 239Appendix A

Index 243


Contents

Getting Started

1

About this documentationThis documentation provides you with information and procedures forinstalling BusinessObjects Enterprise XI 3.0 on UNIX, including detailedinstructions for the different installation modes available.

In addition this documentation provides instructions for Standalone ClientTools installation, Language Pack installation and for modifying, or removingBusinessObjects Enterprise.

Who should read this documentationThis documentation is intended for the system administrator or IT professionalwho needs to install BusinessObjects Enterprise XI 3.0 on UNIX operatingsystems. Familiarity with your overall network environment, port usage, yourdatabase environment, and your web server software would be beneficial.

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

DescriptionGuide

This guide covers the key concepts youshould consider before you begin deploy-ing BusinessObjects Enterprise. Thisguide includes an overview of the architec-ture, tips for assessing your existing envi-ronment, determining your organization'sneeds, and preparing for the installation.

BusinessObjects EnterpriseDeployment Planning 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 Enterprise In-stallation and ConfigurationGuide


Getting Started1 About this documentation

DescriptionGuide

Provides content for server administrationand content administration. The serveradministration topics includes server con-figuration, managing authentication, con-figuring firewalls, and measuring systemperformance. The content administrationtopics include working with the CMC,configuring rights and access levels,managing users, and working with Busi-ness Objects applications and objects.

BusinessObjects EnterpriseAdministrator's Guide

Provides an overview of the publishingprocess, working with publications, pub-lishing Crystal reports, publishing web in-telligence documents, publishing desktopintelligence documents, and publishingsecurity.

BusinessObjects EnterprisePublisher's Guide

Details content migration from legacyBusiness Objects software, such as Clas-sic or Enterprise 5 or 6, to BusinessOb-jects Enterprise XI 3.0.

BusinessObjects Enterprise Mi-gration Guide

Information for upgrades from BusinessOb-jects Enterprise XI to BusinessObjectsEnterprise XI 3.0.

BusinessObjects EnterpriseUpgrade Guide

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

BusinessObjects Enterprise In-foView User's Guide

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


1Getting StartedBusinessObjects Enterprise guides

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

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

What is BusinessObjects Enterprise?BusinessObjects Enterprise XI 3.0 is a flexible, scalable, and reliable solutionfor delivering powerful, interactive reports to end users via any webapplication—intranet, extranet, Internet or corporate portal. Whether it isused for distributing weekly sales reports, providing customers withpersonalized service offerings, or integrating critical information into corporateportals, BusinessObjects Enterprise delivers tangible benefits that extendacross and beyond the organization.

As an integrated suite for reporting, analysis, and information delivery,BusinessObjects Enterprise provides a solution for increasing end-userproductivity and reducing administrative efforts.

What's new in the BusinessObjectsEnterprise Installation andConfigurationguide?

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide isthe first release to include information on the following features:

DescriptionFeature

New languages can be added to your installation usingthe standalone Language Pack installer.

Language Packs in-stallation

Web applications can now be deployed directly using theBusinessObjects Enterprise installer, or after installationusing either the wdeploy tool or the web application serv-er's administration console. Procedures for several deploy-ment scenarios are considered and thoroughly document-ed in this guide.

Deploying web appli-cations

You can store all of your installation settings in a log file,which you can use to run silent or scripted installations.This feature is particularly useful for automating custominstallations.

Scripted Installation

Web applications can be installed and deployed to sup-ported web application servers using a dedicated installa-tion method.

Web-tier installation


Getting Started1 What is BusinessObjects Enterprise?

All product documentation (including error message explanations) is availablein all supported languages in an HTML-based documentation library. Thissystem enables full-text search and other customizable features to make iteasy to find the information you need. You can also access or download thePDF guides from the same website. The website is refreshed with up-to-datecontent as it becomes available between releases. Go to http://support.businessobjects.com/documentation/


1Getting StartedWhat's new in the BusinessObjects Enterprise Installation and Configuration guide?

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

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


Getting Started1 What's new in the BusinessObjects Enterprise Installation and Configuration guide?

Preparing to InstallBusinessObjects Enterprise

2

Installation overviewBusinessObjects Enterprise XI 3.0 provides an open and flexible architecturethat supports a multitude of deployment and configuration scenarios. Beforeyou install BusinessObjects Enterprise you should:

• Consult the BusinessObjects Enterprise XI 3.0 Deployment and PlanningGuide.

• Review your physical system to ensure that it meets the basicrequirements for a BusinessObjects Enterprise installation.

• Ensure that all machines that will be part of your BusinessObjectsEnterprise XI 3.0 deployment can communicate properly with one another.

• Decide which BusinessObjects Enterprise XI 3.0 components to installand which of your own components to integrate.

• Determine where the components should be installed.• Decide which installation method to use.• Consider how you should prepare your infrastructure and set up your

environment including server locations.

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.

At the start of the next chapter, you will find an installation checklist. You canuse this checklist to help ensure you are prepared before you begin yourinstallation.

System requirements

For a detailed list of supported environments and hardware requirements,consult the Platforms Availability Report (PAR) file available on the BusinessObjects support site http://support.businessobjects.com/documentation/supported_platforms/. This file includes specific version and patch-levelrequirements for web application servers, web browsers, and operatingsystems. For additional important information that may pertain to yourdeployment, it is also strongly recommended that you consult theBusinessObjects Enterprise XI 3.0 Deployment Planning Guide .

Generally, the following components must be preinstalled and configuredcorrectly before you can install BusinessObjects Enterprise XI 3.0:


Preparing to Install BusinessObjects Enterprise2 Installation overview

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


• Web application server (unless you want to install Tomcat as part of yourinstallation of BusinessObjects Enterprise)

• Database software that is compatible with the CMS system and the Auditdatabases (unless you want to install MySQL as part of your installationof BusinessObjects Enterprise).

Note: BusinessObjects Enterprise requires a database to store informationabout the system and its users.

Tip: If you are installing on VMWare, ensure your machine name does notinclude any of the following characters: an underscore, a period, or a slash.

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. Rootprivileges are not required to perform either a user or system install ofBusinessObjects Enterprise.

Caution: If you attempt an installation with root privileges, you will beunsuccessful

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 BusinessObjectsEnterprise 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


2Preparing to Install BusinessObjects EnterpriseInstallation overview

Required permissionsCategory

Rights to add and drop tables to/from database, plus rights toread, write, and edit table rows

Database

Minimum rights for deploying web applications

Tip: We recommend that you use the same user account for installingBusinessObjects Enterprise and your web application server.

To deploy web applications using a user account different from the one usedto install the web application server, you must ensure that theBusinessObjects Enterprise user account has the privileges listed in thefollowing table.

Minimum required permissionsWeb application server

• rights to read, write and execute files in $as_dir/bin• rights to remove the $as_dir/server/${as_in

stance}/deploy/jbossweb-tomcat55.sar/jsf-libs directory

• rights to read, write and execute files in$as_dir/server/$as_instance/lib

• rights to read, write and execute files in$as_dir/server/$as_instance/deploy

JBoss

• rights to read and execute files in$as_dir/j2ee/home

• rights to read and execute files in $as_dir/opmn/lib• rights to read, write and execute files in

$as_dir/opmn/conf

Oracle

• rights to read and execute files in$as_dir/$as_sid/$as_instance/j2ee

• rights to read, write and execute files in$as_dir/$as_sid/$as_instance/j2ee/deploying

SAP Web Application Server



Minimum required permissionsWeb application server

• rights to read, write and execute files in $as_dir/bin• rights to read, write and execute files in

$as_dir/shared/lib• rights to read, write and execute files under

$ad_sir/webapps and its subdirectories• rights to read, write and execute files under

$as_dir/conf and its subdirectories

Tomcat

• right to read files under $WL_HOME/server/lib• right to read and write files under $as_dir/bin/

• right to read and execute files under $WL_HOME/jdk150_06/ (or your WebLogic JDK directory)

• right to read files under $WL_HOME /wlserv-er_10.0/common/bin

• right to read and execute files under $WL_HOME/modules/

Note: WL_HOME is the weblogic installation dir and notas_dir -- which is the domain root

WebLogic

• Right to read and execute $as_dir/bin/wsadmin.sh• Right to read and execute $as_dir/bin/GenPlug

inCfg.sh• Right to read $as_dir/bin/securityProcs.jacl• Right to read $as_dir/bin/LTPA_LDAPSecuri

tyProcs.jacl• Right to read and execute files in$as_dir/plugins• Right to read and execute files in $as_dir/java• Right to read and execute files in $as_dir/deploy

tool• Right to read, write, and execute files in

$as_dir/properties• Right to read, write, and execute files in

$as_dir/profiles

WebSphere

Note: In addition to the right to execute files or folders mentioned in theabove table, the right to execute is also required on the parent directory.



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 PDF 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 yourterminal is 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 on page 21.

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 environment

such 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 20• Providing and verifying connectivity to the CMS database on page 43• Setting the locale on page 20

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 firewallenvironment, you will need additional configuration details. See the "Workingwith Firewalls" section of the BusinessObjects Enterprise Deployment andConfiguration Guide.

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 theUNIX 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-levelauthority. However, to run the system-level initiation script root-levelauthority is required.

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 ofinformation about your BusinessObjects Enterprise system, which othercomponents can access as required. The data stored by the CMS includesinformation about users and groups, security levels, BusinessObjectsEnterprise content, and servers. For more information about the CMS,see the “Managing and Configuring Servers” chapter in theBusinessObjects Enterprise 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 anyof the following 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 database documentationto determine the settings required for a Unicode configuration.

• 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 machinethat 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 ScenariosBefore you install BusinessObjects Enterprise XI 3.0, consider which of theseis your intended scenario:• New installation• Custom installation• Web Tier installation• Client Tools installation• Silent or Scripted installation• Side-by-Side installation


2Preparing to Install BusinessObjects EnterpriseInstallation Scenarios

• Distributed Deployments

For an installation upgrade see the BusinessObjects Enterprise UpgradeGuide.

New installation

Performing a new installation is the simplest way to deploy BusinessObjectsEnterprise because all the required and optional components are installedby default onto one machine. These components include the following:

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

Custom or Expand installation

The Custom or Expand installation allows you to specify whichBusinessObjects Enterprise XI 3.0 components are installed. You may wantto perform a Custom or Expand installation if you plan to use BusinessObjectsEnterprise in a distributed environment. It may be that you have an existingweb application server that resides on a different machine than the one thathas your BusinessObjects Enterprise core components.

Alternately, you may want to perform a Custom or Expand installation whenyou want to exclude some components installed by default with the newinstallation, or install only a limited set of components. It is recommendedthat you run this type of installation only when you are familiar with specificBusinessObjects Enterprise components and their roles. If you perform acustom install without being familiar with specific BusinessObjects Enterprisecomponents and their roles, you may inadvertently fail to install a requiredcomponent.

You may want to choose a this installation method if:

• You are already familiar with the BusinessObjects Enterprise installationprogram.


Preparing to Install BusinessObjects Enterprise2 Installation Scenarios

• Your deployment of BusinessObjects Enterprise servers will be distributedover multiple computers. Perhaps your web application server will be onone machine but other BusinessObjects Enterprise components areelsewhere.

• You know exactly what components you require.

• You want to cluster either BusinessObjects Enterprises servers or ServerIntelligence Agent Nodes.

• You have disk space constraints.

• You have customized some of your own applications and you don't wantthe installation to overwrite them.

Web tier installation

The Web Tier installation provides you with all of the components that areused by the web application server to run BusinessObjects web applications.

These components include the following:• BI Platform Web Components - used to run BusinessObjects XI 3.0

applications including Central Management Console, InfoView,Performance Management, and Voyager.

• BusinessObjects Enterprise Web Services - which includes BusinessProcess BI Service.

• Tomcat - a web application server you can install

You may want to choose a web tier installation if:

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


• You have an existing web application server and would like to dedicateto work with BusinessObjects Enterprise web applications.

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



Client Tools installation

This scenario allows you to perform an installation that installs only the ClientTools on the local machine. Although most end users interact withBusinessObjects Enterprise over the web, the Client Tools are also providedas stand-alone Windows applications:

• Desktop Intelligence• Web Intelligence Rich Client• Data Source Migration Wizard• Business View Manager• Report Conversion Tool• Import Wizard• Publishing Wizard• Query as a Web Service• Universe Designer• Developer Components - which include:

• BusinessObjects Enterprise Java SDK• BusinessObjects Enterprise Web Services SDK

• Translation Manager

Note: The client applications can only be installed on Windows.

Install these applications for particular users who are responsible formanaging BusinessObjects Enterprise content, developing applications, ormigrating system data. These client tools are not needed by users whoaccess InfoView or the Central Management Console (CMC) administrativeweb applications. Some of these tools are used for migration of existingdocuments from earlier product versions or creating new documents.

Note: The client installation does not generally require a product activationkeycode. However, Desktop Intelligence does require that a key entered inthe CMC after the install completes to enable the content type.

Silent installation

You can run a silent installation to install BusinessObjects Enterprise fromthe command line using a response file containing installation setup


Preparing to Install BusinessObjects Enterprise2 Installation Scenarios

parameters. This method is particularly useful when you need to performmultiple installations or you do not want to interrupt people who are workingon machines in your system.

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 similar installations onseveral machines.

• You do not want to run the BusinessObjects Enterprise XI 3.0 Setupprogram.

Note: BusinessObjects Enterprise does not support silent installations whenthe install contents are on multiple CDs. If your install source files are onmultiple CDs, you must first copy the contents from all the CDs to a centrallocation, such as a hard-drive, and then run the silent install from the locationthat contains the content from all the CDs.

Side-by-side installation

If you have an existing installation of BusinessObjects Enterprise XI, XIRelease 2, and XI 3.0 you may perform a New, Custom or Expand, or WebApplication installation of BusinessObjects Enterprise XI 3.0 on the samemachine. This is called a side-by-side installation and both versions may runsimultaneously.

You should install BusinessObjects Enterprise XI 3.0 in a separate directoryfrom your existing BusinessObjects Enterprise installation. You cannot addservers to a CMS cluster used by a different version of BusinessObjectsEnterprise.

When you perform a side-by-side installation you need to ensure that yourBusinessObjects Enterprise XI 3.0 installation will not clash with yourpreexisting BusinessObjects Enterprise version by :

• Specifying a unique CMS cluster name for the BusinessObjects EnterpriseXI 3.0 installation.



Note: You cannot add servers to a CMS cluster used by a different versionof BusinessObjects Enterprise.

• Specifying unique port numbers for the BusinessObjects Enterprise XI3.0 installation.

CMS System and Auditing DatabaseRequirements

Database requirements

Before you create the relational database that you want to integrate withBusinessObjects Enterprise, consider the following sections that detail whatsettings are required when the relational database is created and whatsettings you should test before beginning your BusinessObjects Enterpriseinstall.

The one requirement that applies, regardless of your database type, is thatyour relational database be set up to use Unicode character encoding (suchas UTF-8). For more information on database requirements, refer to the“Databases in BusinessObjects Enterprise” section in the BusinessObjectsEnterprise Deployment Planning Guide.

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.


Preparing to Install BusinessObjects Enterprise2 CMS System and Auditing Database Requirements

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 databaseclient. 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.


2Preparing to Install BusinessObjects EnterpriseCMS System and Auditing Database Requirements

. (dot operator)sourceShell name

yesnoBourne shell (sh)

yesnoKorn shell (ksh)

yesyesBourne Again Shell(bash)

noyesC shell (csh)

noyesTurbo C shell (tcsh)

Using MySQL

MySQL database server is an open-source database that provides local datastorage. The setup program can configure MySQL along with yourBusinessObjects Enterprise components. If you already have MySQLinstalled, the installation program creates the CMS database using yourexisting database. During the installation of BusinessObjects Enterprise, youspecify what database server you will use and enter the required parametersfor authentication.

Setting up an empty database for the CMS

BusinessObjects Enterprise requires a relational database to store informationabout the system and its users. You can install a MySQL database duringthe installation, or you can use an existing database. If you want to create anew MySQL database during the installation, this section does not apply toyou.



If you want to use an existing database, you or your database administratormust create a new database on your database server before you installBusinessObjects Enterprise. We strongly recommend that this database beused only for BusinessObjects Enterprise, and not contain other tables.

The following database servers are supported on UNIX:

• Oracle

• DB2

• Sybase

• MySQL

Note: See the Platforms.txt file included with your product distributionfor a complete list of supported database software and version requirements.

If you plan on integrating your own database with BusinessObjects Enterprise,rather than installing MySQL with your installation, consult these section fordetails on database setup requirements before you create your database:

• DB2 database setup requirements on page 38

• Oracle database setup requirements on page 40

• Sybase database setup requirements on page 42

• MySQL database setup requirements on page 38

If you plan on integrating your own database with BusinessObjects Enterprise,you will to prepare it before your installation. Here is a summary of the stepsthat will be part of your preparation:

• Creating a new database.

Tip: You may want to name the new database bobjecms, and create anew user account named bobje, however, this naming convention is notrequired.

Note: If you have a previous release of BusinessObjects Enterprise youcannot use your database from a previous release for BusinessObjectsEnterprise XI Release 2; You must create a new database for this release.If you use a database from a previous release, you will destroy any existingdata. Create a new database instead, and after you have completed yourinstallation, you can migrate your old content to the new current version'sdatabase.


2Preparing to Install BusinessObjects EnterpriseCMS System and Auditing Database Requirements

• Creating a new user account and password for this database that will beused by BusinessObjects Enterprise.

• Ensuring that this new account has permission to create, modify, anddelete tables and create procedures so that BusinessObjects Enterprisecan modify the database as required.

• Recording the name of the database, the user account, and the passwordwhen you run the BusinessObjects Enterprise installation script.

During the installation process, the install script asks you if you want toreinitialize the database. Choosing to do so causes the install script to createnew tables in the database to store BusinessObjects Enterprise data. (InOracle, choosing this option causes the install script to createBusinessObjects Enterprise tables in the default schema of the user whosename you provided during the install.)

Note: During a reinstall of BusinessObjects Enterprise, choosing this optioncauses the install script to reinitialize the tables containing BusinessObjectsEnterprise data, destroying any existing data. You must choose to reinitializethe database to proceed with the install. In either case, reinitializing thedatabase does not affect any other tables in that database or schema.

• Consult your database server documentation and/or your databaseadministrator if you are unsure of the procedure for creating a newdatabase.

• Ensure that your database server is set up to use Unicode characterencoding (such as UTF-8). Consult your database documentation todetermine the settings required for a Unicode configuration. For databaseservers such as Oracle and Sybase, during installation you need toconfigure the server to use Unicode encoding for the character data types.For other databases, such as DB2, you can create the CMS databasewith Unicode settings on your existing database server.

Setting up a database account for BusinessObjectsEnterprise

To administer the CMS database, you need to set up a database account.If you choose to install MySQL when you install BusinessObjects Enterprise,you will be prompted during installation to set up this account. If you plan to



use your own database, please complete these steps before you installBusinessObjects Enterprise.

To set up a database account for BusinessObjects Enterprise

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 carry out administrativetasks using the account you set up for use by the CMS.

Related Topics• System requirements on page 16

Preparing your CMS System Databaseserver

Prerequisites for database preparation

Before you prepare your database, you must have already created it. Ensureyou have created the database with the required settings for your existingdatabase server.

Related Topics• MySQL database setup requirements on page 38• DB2 database setup requirements on page 38• Sybase database setup requirements on page 42• Oracle database setup requirements on page 40

Preparing your existing database server

After you have created your database, and before you install BusinessObjectsEnterprise, you or your database administrator need to prepare your owndatabase server so the CMS can connect to it.


2Preparing to Install BusinessObjects EnterprisePreparing your CMS System Database server

During your installation, you will be asked whether you want to install MySQLor use an existing database. If you specify that you will you use an existingdatabase, you will be asked for details about your database.

Although you are required to provide the details about your database duringthe installation, you will not be asked to provide your database name unlessyou are using an existing version of MySQL. This table summarizes theinformation you will be required to enter to identify your database during theinstallation if your are using SQL Server, Sybase, Oracle, or DB2.

Information required at install timeDatabase type

Port numberMySQL

Sybase Server NameSybase

DB2 database aliasDB2

tnsnames connect identifierOracle

Note: On UNIX deployments the Sybase Server Name is a combination ofthe server name and the port number which is set by your databaseadministrator in the interfaces file. The database the installation connects tois the default database for the user profile. This default database is to is setby the DBA in the profile of the account from which you will install and runBusinessObjects Enterprise.

To prepare your database

1. Create a new, empty relational database on your database server.2. Create a new user and assign it a secure password.3. Ensure that the new account has permission to create, modify, delete

tables and create procedures so that BusinessObjects Enterprise canmodify the database as required.


Preparing to Install BusinessObjects Enterprise2 Preparing your CMS System Database server

Note: If you are not the owner of the database, you will need to havepermissions to perform the necessary operations.

4. If you are using MySQL, Sybase, Oracle, or DB2, ensure the followingare set up before you begin your installation:

Ensure this has been configuredDatabase type

MySQL port numberMySQL

Sybase Server NameSybase

tnsnames connect identifierOracle

DB2 database aliasDB2

During the install, you will be asked for information regarding yourdatabase.

5. Record the these details as they will be required during your install:• The name of your database, your Sybase Server Name, your Oracle

tnsnames connect identifier, or your DB2 database alias.

• The user account and the password authorized to the database.

Tip: You may want to record the required details on the InstallationChecklist at the end of this chapter so the information is available whenyou install.

For information on how to create a new relational database, consult yourdatabase server documentation or your database administrator. Forinformation on how to migrate your initial CMS database to another supporteddatabase server later, see the BusinessObjects Enterprise DeploymentPlanning Guide.



MySQL database setup requirements

For a MySQL database there are no specific parameters that are crucial forBusinessObjects Enterprise to work, other than the setting of UTF-8. If youchoose install and configure MySQL as part of your BusinessObjectsEnterprise installation setup, you will not have to provide any specialconfiguration information. By default, a MySQL database will be created withthe default settings for the CMS database and the Audit database.

If you want to use an existing MySQL database server, you will need toprepare the server for the BusinessObjects Enterprise installation.

Related Topics• Preparing your existing database server on page 35

Testing MySQL environment variables

If you are using an existing MySQL database, ensure the following variableis set up for the user who will install BusinessObjects Enterprise XI 3.0:

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.

DB2 database setup requirements

If you are using a DB2 relational database with your BusinessObjectsEnterprise deployment, there are specific settings you need to select whenthe relational database is created. It is not sufficient to modify these settingsafter the relational database has been created.

When you create the relational database you will use with BusinessObjectsEnterprise:

• Ensure the CMS database is not partitioned.



If your DB2 CMS database is partitioned, you will have problems creatingthe CMS database.

Note: This requirement does not apply to the Audit database. If you want,you can use a partitioned DB2 database for the Audit database.

• Create the relational database with the specific settings.Collating Sequence = "Identity"Codeset = "UTF-8"Territory = "XX"

If your DB2 database does not have the correct collating sequence setting,the users and usergroup objects may not sort properly in the CentralManagement Console. Replace XX with the code that is appropriate toyour code set and codepage for your location. Consult your DB2documentation for specifics.

Note: If you are using DB2 8.1, you require a C compiler that is installedand configured to build SQL stored procedures. DB2 8.2 does not have thisrequirement. SQL stored procedures are used in BusinessObjects Enterprisewhen users are added to groups in the CMS. Please consult the DB2documentation for details on how to configure the C compiler for SQL storedprocedures, and for determining what version of the C compiler is supportedon your platform.

After you create your database you will need to prepare it for theBusinessObjects Enterprise install. For details, see Preparing your existingdatabase server on page 35 . In addition, before you begin the install ofBusinessObjects Enterprise, you must ensure the DB2 environment variablesare set up correctly. For details, see Testing DB2 environment variables onpage 39.

Testing DB2 environment variables

If 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.

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

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

page 31

Oracle database setup requirements

For an Oracle database there are no specific parameters, other than thesetting of UTF-8, that are required for BusinessObjects Enterprise to work.However, before you begin the install of BusinessObjects Enterprise, youmust ensure the Oracle environment variables are set up correctly.



Related Topics• Testing Oracle environment variables on page 41

Testing Oracle environment variables

If 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: <installdir>/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 31

Sybase database setup requirements

If you are using Sybase, when you create your database for the CMS, ensurethe page size is set to 8 KB.

Note: The Sybase database default page size is 2KB which is too small forCMS. For CMS to run optimally, the page size must be 8KB. The page sizeis set up during the database creation and it cannot be changed after thedatabase is set up.

After you create your database you will need to prepare it for theBusinessObjects Enterprise install. Before you begin the install ofBusinessObjects Enterprise, you must ensure the Sybase environmentvariables are set up correctly.

Related Topics• Preparing your existing database server on page 35• Testing Sybase environment variables on page 42

Testing Sybase environment variables

If 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: <install



dir>/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 installBusinessObjects 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 31

Providing and verifying connectivity tothe CMS database

To create tables and write data to your new CMS database, the installationscripts need to establish a connection to the database server. That is, whenyou log on to UNIX with the user name from which you will perform theinstallation, the default shell environment must include the appropriatedatabase environment variables and/or initialization files. Only then can theinstallation setup program access the CMS database using your databaseclient software.


2Preparing to Install BusinessObjects EnterpriseProviding and verifying connectivity to the CMS database

The environment variables and/or files required by the installation scriptsdepend upon the type of database server you are running:

Additional database environment variables must be set in order for theinstallation script to use the database client software properly. Before runningthe installation script, test the shell environment of the account from whichyou will install BusinessObjects Enterprise to verify database connectivityand privileges. See the procedure that corresponds to your database.

• Testing Sybase environment variables on page 42

• Testing Oracle environment variables on page 41

• Testing DB2 environment variables on page 39

To verify Sybase native connectivity through a servername

1. Log on to the UNIX server with the user account and password whichyou will use to do your install.

Note: This account should already be set up. See Creating an account,a home directory, and a login environment on page 21for more informationon setting up a UNIX account to use when you install BusinessObjectsEnterprise.

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

ValueVariable

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

SYBASE


Preparing to Install BusinessObjects Enterprise2 Providing and verifying connectivity to the CMS database

ValueVariable

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

SYBASE_OCS

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

5. Issue the following command to ensure that the account has permissionto delete tables:drop table sampletablegosp_help sampletablego

6. Type quit

To verify Oracle native connectivity through a TNS


Note: This account should already be set up. See Creating an account,a home directory, and a login environment on page 21 for moreinformation on setting up a UNIX account to use when you installBusinessObjects Enterprise.


ValueVariable

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

ORACLE_HOME



ValueVariable

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

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 appropriate values.If the shell environment has been configured correctly, you are connectedto Oracle.

4. Issue the following command to ensure that account has permission tocreate tables:create table sampletable (field1 char(10));

5. Issue the following command to ensure that the account has permissionto delete tables: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

To verifyDB2native connectivity through a databasealias


Note: This account should already be set up. See Creating an account,a home directory, and a login environment on page 21 for moreinformation on setting up a UNIX account to use when you installBusinessObjects Enterprise.


ValueVariable

This variable defines the currentDB2 database instance.DB2INSTANCE

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

INSTHOME



ValueVariable

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

DB2DIR

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

Before you deploy web applicationsYour web application server must be installed and working before you attemptto install BusinessObjects Enterprise. Consult your web application serverdocumentation for installation instructions.

To deploy and run the CMC and InfoView applications, your web applicationserver should have at least 1.2 GB of free disk space, in addition to any otherrequirements specified by other software installed on the machine.

It is recommended that you change the heapsize and maximum perm sizesettings of your JVM to -Xmx1024m -XX:MaxPermSize=256m. If usingTomcat for example, your modified settings would look like:

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 correctly installed and verify that the application server is runningcorrectly by launching its administrative console at:• http://<WAS_HOSTNAME>:<PORT>

Replace <WAS_HOSTNAME> with the host name or IP address of your webapplication server, and <PORT> with the port number used for HTTP. Consultyour web application server documentation for installation instructions.


Preparing to Install BusinessObjects Enterprise2 Before you deploy web applications

Beginning the Installation ofBusinessObjects Enterprise

3

Installation checklistPrior to installing BusinessObjects Enterprise XI 3.0, please review thechecklist below.

• Have you tested that all machines that will run BusinessObjects Enterprisecan communicate properly?

• Have you tested the database connection between the machine that willhost your CMS database and the machine on which the CentralManagement Server will 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 user IDand 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 connecting to hasbeen 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 plan to use your existing database, has the database client softwarebeen properly configured.?

• If you are not using Tomcat, have you made sure your existing webapplication server has the JDK installed?


Beginning the Installation of BusinessObjects Enterprise3 Installation checklist

• If you are not using Tomcat, is your web application server alreadyinstalled and configured?

• Do the BusinessObjects Enterprise system requirements match yourUNIX setup?

• If you are installing on VMWare, have you ensured your machine namedoes not include any of the following characters: an underscore, a period,or a slash?

• 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 is strongly 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.


3Beginning the Installation of BusinessObjects EnterpriseInstallation overview

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.

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 20

Running the product distributiondirectly fromaCD

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 CD 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 on page 55.4. Run install.sh from the first CD.

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

page 21

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 temporarylocation, you will be prompted to specify a temporary location for theinstall.

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:• German• English• Spanish• French• Italian• Japanese• Korean• Dutch• Portuguese• Swedish• Simplified Chinese• Traditional ChineseThe "Business Objects License Agreement" is displayed.

Related Topics• Running the product distribution directly from a CD on page 54


Beginning the Installation of BusinessObjects Enterprise3 Beginning your installation

To accept the license agreement

To install Business Objects 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.

Entering 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 CD liner notes or the CD 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.

Specifying the installation directory

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

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.

Installing 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:

• French• Japanese• German• Spanish• Italian• Korean• Dutch• Portuguese• Swedish• Simplified Chinese• Traditional Chinese

Note: English is a required language and cannot be deselected.

2. Press Enter .

Note: You can add language packs after installing Business ObjectsEnterprise on UNIX.

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

Related Topics• To install language packs on page 134

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-levelauthority. However, to run the system-level initiation script root-levelauthority is required. After you perform a System installation, there are afew additional steps you must perform.

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



Difference between user and system installation

There are two possible options for new Business Objects Enterpriseinstallations on UNIX.

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

• When you choose a System installation, all the required components arealso installed, however, in addition, the installation creates a system-levelinitiation script. This script creates entries into the run levels for theOperating System that starts the BusinessObjects Enterprise serverswhen the UNIX server is brought up and stops the BusinessObjectsEnterprise servers when a machine is shut down.

Related Topics• Finishing a system installation on page 103

Selecting 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. To perform a new Systeminstallation, you require root-level authority

• 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 may select Disable servers after installation to automaticallystop all servers. This will prevent communication between the CentralManagement Server (CMS) and other servers after the installation iscomplete. For more information on starting, stopping, disabling andenabling servers, refer to the BusinessObjects EnterpriseAdministrator's Guide.

2. Press Enter.

Related Topics• Performing a new installation on page 62• Performing a custom installation on page 76• To perform a web tier installation on page 96



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.

To perform 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 55


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 thepassword at a later time. Your password must be at least six characterslong and should 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 64• To install a new MySQL Database on page 66


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



CMS port number

Oracle




Alias name



CMS port number

DB2

Sybase Service name



CMS port number

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

Auditing database port number

User ID

Password

Auditing

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

Note: Reinitialization of the BusinessObjects Enterprise database willerase all previous 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• Database requirements on page 30

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 XI3.0. Use the installation setup program to configure the SIA.

1. Type a name in Server Intelligence Agent Node.Do not use spaces, dashes or periods in the 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 installerto specify to install Tomcat as your application server, or choose to work withyour existing web application server.

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

When to useDeployment option

If you do not have an existing web applica-tion server.

Install Tomcat, deploy webapplications

If you have an existing supported web ap-plication server and you want to automati-cally deploy the web applications.

Use existing Java applicationserver, deploy web applica-tions

If you have an existing supported web ap-plication server and you want to manuallydeploy the web applications.

Use existing Java applicationserver, do not deploy webapplications



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 102• To configure your existing web application server on page 99• To configure the Tomcat installation on page 98

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 102

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 followingoptions and press Enter.• Tomcat 5.5• WebLogic 10• WebLogic 9• WebSphere 6.1• Oracle Application Server 10g R3• OtherIf your existing web application server is SAP Application Server 7.0 orJBoss 4.04, select Other.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 Installation directory: The directory where theweb application server is installed (for example /bea/weblogic10/user_projects/domains/base_domain).

Note: For WebLogic the directory is the domain root.

WebLogic 10



• Admin login: Password for account with administration rights to theapplication server - mandatory for Weblogic.


• Application server Installation directory: The directory where theweb application server is installed (e.g /bea/user_projects/domains/base_domain).


WebLogic 9




• Admin port: The SOAP Connector Port of the application server(for example “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 (y/n): Select this option to enable security requiring

administrative access credentials to the application.

Note: If Admin is secure is not selected you do not need to specifya username or a password.

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

WebSphere 6.1




• 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 tospecify the username 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").

.

Oracle ApplicationServer 10g R3


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] severaltimes until you reach the screen where you specify the installationdirectory.



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 126

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.After installation, however, you must have root privileges to run the setupinit.sh script. 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 installationThe 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 environment. For example,your existing web application server resides on a different machine than theone 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.

Features available in a custom installation

Client Components

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

Java applications.


Custom or Expand Installation5 Performing a custom installation

• BusinessObjects Enterprise Web Services SDK: This is thedevelopment kit for web services.

Web Tier Components

This feature contains the following subfeatures:

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

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

• 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• Report Application Server• Multi-Dimensional Analysis Services Server• Crystal Reports Job Server• Destination Job Server• List of Values Job Server• Program Job Server• Adaptive Job Server


5Custom or Expand InstallationPerforming a custom installation

• Adaptive Processing Server• Web Intelligence Report Server• Desktop Intelligence Servers• Dashboards and Analytics Servers• Auditing Reports and Universes

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 Fedrator• MySQL• Generic ODBC• NETEZZA• ALL IBM Database Drivers contains the following subfeatures:

• IBM DB2• Informix

• Progress OpenEdge• Oracle• Sybase• NCR Teradata

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 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. Deselect Auditor under Server Components if you do not want to

configure an auditing database.c. Deselect MySQL under Server Components 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 55• Installing only the Web Tier Components on page 86• To install only the server components on page 80

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.

Note: Ensure that the markers for the deselected features appear as [].

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 55• To cluster servers to an existing CMS on page 85• To specify CMS clustering information on page 82• To configure MySQL in a custom or expand installation on page 81


Custom or Expand Installation5 To perform a Custom or Expand installation

To configure MySQL in a custom or expand installation

The "Enter the information for your new CMS" is displayed because youchose to install MySQL in the "Feature" screen.

1. Type a valid port number in CMS Port Number or accept the defaultvalue - 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 thepassword at a later time. Your password must be at least six characterslong and should contain three of the following options

• upper case character• lower case character• number• punctuationYou need to provide configuration details for the new MySQL database.The setup program provides two screens to configure the MySQLdatabase.

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

4. 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

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



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

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 yournew CMS.

• No - Cluster this CMS with an existing CMS

Note: If you select this option you must provide information on theexisting CMS 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 configurethe password at a later time. Your password must be at least sixcharacters long and should contain two of the following options

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

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 inExisting CMS Port.

d. Type the password or leave Existing CMS Administrator Passwordblank 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



CMS port number

Oracle




Alias name



CMS port number

DB2

Sybase Service name



CMS port number

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

Auditing database port number

User ID

Password

Auditing

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

Note: Reinitialization of the BusinessObjects Enterprise database willerase all previous 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 85

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 Adminis-trator Password

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 XI3.0. Use the installation setup program to configure the SIA.

1. Type a name in Server Intelligence Agent Node.Do not use spaces, dashes or periods in the 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..










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 andavoid installing unnecessary components run a Web Applications installation.

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

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 55• To cluster web tier features to a CMS on page 97

To cluster web tier features to a CMSYou need to be able to connect 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 in CMS Hostname.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 applications 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 installerto specify to install Tomcat as your application server, or choose to work withyour 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





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.

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• WebSphere 6.1• Oracle Application Server 10g R3• OtherIf your existing web application server is SAP Application Server 7.0 orJBoss 4.04, select Other.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.






Apache Tomcat 5.5










WebLogic 10







WebLogic 9












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.



5Custom or Expand InstallationFinishing a system installation


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 3.0 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.

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 existingweb application server.

4. Press Enter to submit your selection.


Web Applications Installation6 Performing web tier installations

You must now cluster the selected components to an existing CentralManagement Server (CMS).

Related Topics• Beginning your installation on page 55

Features available in a web tier installation

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

• BusinessObjects Enterprise Web Services: This is a component ofBusiness Objects Enterprise built for developers. It is composed of animplementation of web services that can be deployed withBusinessObjects Enterprise XI 3.0. This web service implementationprovides an API/WSDL which simplifies the process of developingapplications.

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

To cluster web tier features to a CMS

You need to be able to connect 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 in CMS Hostname.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 applications server, or specify a deployment option.


6Web Applications InstallationPerforming web tier installations

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 installerto specify to install Tomcat as your application server, or choose to work withyour 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



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• WebSphere 6.1• Oracle Application Server 10g R3• OtherIf your existing web application server is SAP Application Server 7.0 orJBoss 4.04, select Other.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.








Apache Tomcat 5.5







WebLogic 10







WebLogic 9












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 recommendedfor custom installations. This method does not allow for the same level ofcustomization provided 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• Performing a scripted installation on page 106• Performing a silent installation on page 117

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.Select Ctrl-X to abort the installation setup once you reach the final screenin the installation 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 atemporary location, you will be prompted to specify a temporary locationfor the installation.

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 thename of 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• Running the product distribution directly from a CD on page 54

To run a scripted installation

You need to have a response residing in a known directory. The MACHINENAME parameter must be specified in the response file if you are replicatingan installation. If the parameter is not specified, the local server name willbe used by default.1. Mount the device that contains the installation files.


7Silent InstallationPerforming a scripted installation

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

2. In the command-line type the following information:install.sh -r response.ini -I /installDirectory/ -s/cd/setup/DISK_1/

• -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 CD. If not specified, the CD directory setting in theresponse file will be used.

3. Press Enter to launch the installation.

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

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


Silent Installation7 Performing a scripted installation


Path of the bobje directory automaticallysetup in the installation directory.BOBJEDIR="<INSTALLDIR>/bobje/"

BOBJEDIR

Path to the DISK_1 directory on the distri-bution CD. This path defaults to the CDdirectory.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=FrenchBOBJELANG="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-XXXXXXXPIDKEY

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

INSTALLTYPE

Specifies a comma-delimited list for theBusinessObjects Enterprise installer op-erating modes. This parameter supportsthe following options:• install• modify• remove• integrated• interactiveINSTALLMODE=interactive,install

INSTALLMODE

Specifies the name of the local serverLOCALNAMESERVER=“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=FrenchLANGPACKS_TO_INSTALL=“en fr”

LANGPACKS_TO_INSTALL

Specifies the Business Objects 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• Use weblogic10 for WebLogic 10• Use websphere6 for WebSphere 6.1AS_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 is administrator credential mustbe passed to access the web applicationserver. This setting only valid for Web-Sphere 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• noneWDEPLOYACTION=“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• SybaseDBTYPE=“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”

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 107

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


7Silent InstallationPerforming 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 -INSTALLTOMCAT yes-TOMCATCONNECTORPORT 13890 -TOMCATREDIRECTPORT 13889-TOMCATSHUTDOWNPORT 13891 -AUDITINGENABLED yes-DASENABLED yes

Note: The example uses the most common parameters. You can chooseany number 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 CD, but you only need to provide the full list of options for thefirst CD. For example, if the CDs are on different drives, the commands couldlook 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 -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.


Silent Installation7 Performing a silent installation

DescriptionInstallation parameter

The location of the CD used to run the installation.Replace filepath with the full path for the CD driveor other installation source directory. For example,-s /mnt/CD1/

-sfilepath

Specifies the directory where you want to installthe new BusinessObjects Enterprise components.Replace filepath with the full path for the installationdirectory. 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 willbe disabled until you enter an appropriate keycodethrough the Central Management Console (CMC).

-DASENABLED

This option determines the language for the instal-lation. Replace languagecodewith a language codefor 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

-clanguage code

Specifies the Server Intelligence Agent (SIA) nodename to use for the installation.-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 webapplications 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 manually start and enable servers

1. 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 examplehttp://<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.7. Select Start Server.

The server should now start.

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.


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

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 configured and deployed before you use them. Youcan either deploy the components manually or use the wdeploy tool.

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

Note: If you have a firewall between the machine running your webapplication server and your other BusinessObjects Enterprise servers, youmust perform additional system configuration. See the section on how toconfigure firewalls, in your BusinessObjects Enterprise Administrator's Guide.

Related Topics• BusinessObjects Enterprise WAR files on page 185• How to use wdeploy on page 151• To manually deploy web applications on page 188

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.

.


8After Installing BusinessObjects EnterpriseSetup for performance management

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:

• 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.


After Installing BusinessObjects Enterprise8 Setup for performance management

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.

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 providea real user 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.


8After Installing BusinessObjects EnterpriseSetup for performance management


After Installing BusinessObjects Enterprise8 Setup for performance management

Language Packs on UNIX

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-backIn 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 changesProduct 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.

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.


Language Packs on UNIX9 About language packs

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.

Note: Application shortcut keys are language neutral and do not change,regardless of which language is in use. For example, Ctrl+S is always mappedto the Save command, regardless of the localized name for the Save function.

Installing language and complexdeployments

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

Installing language packs on UNIXsystems

Language packs can be installed either during the initial installation ofBusinessObjects Enterprise, or post-install using a dedicated language packinstaller. The installer is a script that adds the localized language resourcesto 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 itis incompatible with a previously installed version of BusinessObjectsEnterprise.


9Language Packs on UNIXInstalling language and complex deployments

http://technicalsupport.businessobjects.com

Locating language packsLanguage 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 packsBefore 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 forlanguage 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 LANGUAGEwith 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.


Language Packs on UNIX9 Locating language packs

http://technicalsupport.businessobjects.com

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

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

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 aBusinessObjects Enterprise 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.

The command-line syntax for a silent install is as follows:

install_langpack.sh BUSINESS_OBJECTS_HOME_DIRINSTALLMODE=silentCMSNAMESERVER=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_langpack.sh.

DescriptionExpected argu-ment

Parameter

Switch to enable silent install modesilentINSTALLMODE

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


9Language Packs on UNIXInstalling language packs across a BusinessObjects Enterprise deployment

For example:$ ./install_langpack.sh /opt/bobjeINSTALLMODE=silentCMSNAMESERVER=myserver1CMSPORTNUMBER=6400CMSPASSWORD=mypassword

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 How to use wdeploy.

Related Topics• How to use wdeploy on page 151

To uninstall language packs1. Open the Central Management Console (CMS) and ensure that all servers

are running2. Locate the language pack to uninstall. You will find the uninstall_lang

pack.sh script in the setup folder of the language pack.3. Run the uninstall_langpack.sh script with the first argument set to the

location of the BusinessObjects Enterprise installation directory.For example: uninstall_langpack.sh /opt/bobj


Language Packs on UNIX9 To uninstall language packs

4. Press y to confirm the removal of the language pack.5. Enter the CMS hostname, port number, and administrator password and

press Enter.6. Press Enter after you have confirmed the location of the BusinessObjects

Enterprise installation directory.


9Language Packs on UNIXTo uninstall language packs


Language Packs on UNIX9 To uninstall language packs

Maintaining your Installation

10

Uninstalling BusinessObjects Enterprisefrom UNIX

Before you can remove BusinessObjects Enterprise from your UNIX machine,you must run the AddOrRemovePrograms.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 CD during your originalinstallation of BusinessObjects Enterprise.

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 XI 3.0 from your UNIX system,you should uninstall all language packs used by the installation.

To uninstall BusinessObjects Enterprise:

1. From the installation directory run ./AddOrRemovePrograms.sh.The "Add or Remove Programs" screen is displayed.

2. Select BusinessObjects Enterprise XI 3.0 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.


Maintaining your Installation10 Uninstalling BusinessObjects Enterprise from UNIX

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 136

Addingperformancemanagement to yourinstallation

You can add performance management servers and binaries to yourBusinessObjects Enterprise installation.

You must run the AddOrRemovePrograms.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 ./AddOrRemovePrograms.sh.The "Add or Remove Programs" screen is displayed.

2. Select BusinessObjects Enterprise XI 3.0 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:

DescriptionField name

The system name for the CMS hostmachine

CMS Hostname


10Maintaining your InstallationAdding performance management to your installation

DescriptionField name

Port used by the CMSCMS Port

Administrator password used to accessthe 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• WebSphere 6.1• Oracle Application Server 10g R3• OtherA configuration screen for your selected web application server isdisplayed.

6. Provide the requested configuration details for your web application server.


Information required for installation setupWeb 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


Maintaining your Installation10 Adding performance management to your installation


• 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 Installation directory: The directory where theweb application server is installed (e.g. /bea/weblogic10/user_projects/domains/base_domain).


WebLogic 10

• 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”).



WebLogic 9




• 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”).




• Application Server Installation Directory: The directory where theweb application server is installed (e.g./IBM/WebSphere/AppServer).

WebSphere 6.1


Maintaining your Installation10 Adding 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 setup verifies the configuration details. Once theverification is complete, 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 Performance ManagementSetup 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.0.log and BusinessObjects.12.0.log.summary. The BusinessObjects.12.0.log file containsdetailed information on installation and deployment. Both files are savedunder the following directory: <INSTALLDIR>/setup/logs/.


Maintaining your Installation10 The installation log file

Post Installation WebApplication Deployment

11

Overview of post install deploymentYou can deploy web applications for BusinessObjects Enterprise XI 3.0installations by running all three supported installation types. The installationsetup program guides you through an automated process for deploying theweb applications and their required components only if you specify andconfigure your web application server during the installation setup.

You can also configure your web application servers and deploy webapplication components after installing BusinessObjects Enterprise. You canchoose either of the following methods.

1. Use the wdeploy program to automatically deploy the required componentsto the applications server. For detailed information on wdeploy seeDeploying BusinessObjects Enterprise Web Applications using wdeploy.

2. Manually configure and deploy the required components to the applicationsserver.

The following table lists which deployment method is available for supportedWeb application server.

Manual deploy-mentwdeployInstallation setup

program

XXXWebSphere 6.1

XWebSphere Com-munity Edition 2.0

XXXWebLogic 10

XXXWebLogic 9.2

XXXTomcat 5.5

XXSAP ApplicationServer 7.0

XXXOracle ApplicationServer 10G R3

XXJBoss 4.04


Post Installation Web Application Deployment11 Overview of post install deployment

Before you deploy web applicationsYour web application server must be installed and working before you attemptto install BusinessObjects Enterprise. Consult your web application serverdocumentation for installation instructions.

To deploy and run the CMC and InfoView applications, your web applicationserver should have at least 1.2 GB of free disk space, in addition to any otherrequirements specified by other software installed on the machine.

It is recommended that you change the heapsize and maximum perm sizesettings of your JVM to -Xmx1024m -XX:MaxPermSize=256m. If usingTomcat for example, your modified settings would look like:

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 correctly installed and verify that the application server is runningcorrectly by launching its administrative console at:• http://<WAS_HOSTNAME>:<PORT>

Replace <WAS_HOSTNAME> with the host name or IP address of your webapplication server, and <PORT> with the port number used for HTTP. Consultyour web application server documentation for installation instructions.

Deploying with wdeploy

Prerequisites for using wdeploy

Where to find wdeploy

The wdeploy command-line tool is included with your BusinessObjectsEnterprise installation to assist you in the command-line deployment of webapplications to your web application server. It is located in the followingdirectory: <INSTALLDIR>/deployment/. In addition to the wdeploy.sh thefolder contains all the required configuration files for running the tool.


11Post Installation Web Application DeploymentBefore you deploy web applications

Note: The wdeploy tool is also available as a stand-alone package on theproduct distribution media under the following directory: Collaterals/Tools/wdeploy.

Prerequisites for using wdeploy

To deploy BusinessObjects Enterprise web applications to a web applicationserver, you must have BusinessObjects Enterprise installed, including allrequired WAR files. If the target web application server is on the samemachine on which BusinessObjects Enterprise is installed you can proceedto run the wdeploy script.

If the target web application server is hosted on a remote machine you willhave to follow specific steps for preparing the wdeploy environment.

Related Topics• To deploy web applications on a remote machine on page 182• Minimum rights for deploying web applications on page 18

Overview for using wdeploy

The wdeploy command-line tool is included with BusinessObjects Enterpriseto assist you in the command-line deployment of WAR files to your webapplication server. You can choose to deploy all web application resourcestogether on a single web application server (standalone mode), or to separatedynamic and static content for deployment onto de-paired web and webapplication servers (distributed mode). For detailed information on wdeploysee Deploying BusinessObjects EnterpriseWeb Applications using wdeploy.This document is available at http://support.businessobjects.com.

For more information about the system architecture of an installation ofBusinessObjects Enterprise, see the “Architecture” chapter of theBusinessObjects Enterprise Deployment Planning Guide.

Note: If you have a firewall between the machine running your Javaapplication server and your other BusinessObjects Enterprise servers, youmust perform additional system configuration. See the section on how toconfigure firewalls in the BusinessObjects Enterprise Deployment PlanningGuide.


Post Installation Web Application Deployment11 Deploying with wdeploy

http://support.businessobjects.com

How to use wdeploy

To use wdeploy, the specific configuration file for your web application servermust be properly configured. This file is located in <INSTALLDIR>/deployment/. For example, the configuration file for weblogic 9.2 is config.weblogic9.

It is recommended that you use the same user account for installingBusinessObjects Enterprise and your web application server. Ensure thatyou have the minimum user rights for the web application server.

The following table lists the required wdeploy configuration file details thatmust be specified for each supported web application server.

Note: Parameters specified on the command-line override parameters inthe wdeploy configuration file.


11Post Installation Web Application DeploymentDeploying with wdeploy

Required Configuration detailsWeb applicationserver

• as_admin_port: The SOAP Connector Port of the application server(for example “8880”).

• as_admin_username: WebSphere administrator account username(for example "administrator").

Note: If as_admin_is_secure is false, a value for as_admin_username does not need to be specified.

• as_admin_password: WebSphere administrator account password(for example "password").

Note: If as_admin_is_secure is false, a value for as_admin_password does not need to be specified.

• as_instance: The name of your WebSphere application server in-stance (for example "server1").

• as_virtual_host: The virtual host to which the application must bebound (for example "default_host").

• as_admin_is_secure: Instructs wdeploy that WebSphere securityis enabled (for example "false").

Note: Values for as_admin_username and as_admin_passwordmust be set when as_admin_is_secure is true").

• as_dir: WebSphere installation directory (for example“/opt/IBM/WebSphere/AppServer”).

• ws_instance: The name of the web server where the application isinstalled, in distributed mode (for example "server1").

• enforce_file_limit: Indicates to wdeploy whether or not the webapplication server may encounter issues loading applications thatcontain more than 65,535 files ("True" by default).

WebSphere 6.1




• as_admin_port: Administration port of the application server (forexample "7001").

• as_admin_username: WebLogic administrator account username(for example "weblogic").

• as_admin_password: WebLogic administrator account password(for example "weblogic").

• as_instance: The name of your WebLogic application server in-stance (for example "AdminServer").

• as_dir: Weblogic domain directory (for example "/opt/bea/weblogic10/user_projects/domains/base_domain").

WebLogic 10

• as_admin_port: Administration port of the application server (forexample "7001").

• as_admin_username: WebLogic administrator account username(for example "weblogic").

• as_admin_password: WebLogic administrator account password(for example "weblogic").

• as_instance: The name of your WebLogic application server in-stance (for example "AdminServer").

• as_dir: Weblogic domain directory (for example "<INSTALLDIR>/bea/user_projects/domains/base_domain").

WebLogic 9.2

• as_instance : Name of the web application server instance currentlyused (for example "localhost").

• as_dir : Installation directory of the web application server (for ex-ample "/opt/tomcat).

• as_service_key_value: Tomcat's Java parameters, and the valueof the registry key as_server_key.

Tomcat 5.5




• as_dir: The location of your application server (for example "<IN-STALLDIR>/SAP").

• as_sid: the SAP system id of the target instance. (for example"AS2").

• as_instance: The name of your application server instance (for ex-ample "JC01").

• as_admin port: the port number used by the server (for example"50104").

• as_admin_username: the administrator username (for example"Administrator").

• as_admin_password: the administrator password (for example"password").

SAP Application Serv-er 7.0

• as_admin_port: Administration port of the application server. Thisis the request port of the notification server, found in the <notification-server> section of configuration file opmn.xml (for example"6003").

• as_admin_username: Oracle Application Server administrator ac-count username (for example "ocjadmin").

• as_admin_password: Oracle Application Server administrator ac-count password (for example "oracle10g").

• as_instance: The name of your Oracle Application Server applicationserver instance (for example "home").

• as_admin_is_secure: Instructs wdeploy that Oracle ApplicationServer SSL security is enabled (for example "false").

Note: If as_admin_is_secure is not enabled, you will still have tospecify the username and password to access the server.

• as_dir: Oracle Application Server installation directory (for example"/opt/product/10.1.3/OracleAS_1").

• as_appserver_name: Name of the target application server (forexample "myserver.domain.com").

• as_group_id: Name of the server group to which the target applica-tion belongs (for example "Default_group").





• as_dir: The location of the JBoss application server (for example"opt/jboss-4.0.4.GA").

• as_instance: The name of the JBoss application server instance(for example "default").

JBoss 4

Run the wdeploy.sh script by opening command line console and typingthe following:<INSTALLDIR>/deployment/wdeploy.sh

<appserver> deployall >> <logfilename>.log

For example:wdeploy.sh weblogic9 deployall >> <INSTALLDIR>/mylog.log

Note: The <appserver> must be same as the web application server usedin the configuration filename.

Tip: You can drop the deployable war files to non-default location by passingthe parameter -Dwork_dir=your target location as part of the wdeploycommand.

For more detailed information on wdeploy see Deploying BusinessObjectsEnterprise Web Applications using wdeploy.

Options for using wdeploy

There are several actions that can be performed the wdeploy tool to controlthe web application deployment process:• predeploy/predeployall: Predeploy web applications.• deployonly/depolyonlyall: Deploy web applications.• deploy/deployall: Predeploy then deploy web applications.• undeploy/undeployall: Undeploy web applications.

Note: If you use the undeploy and undeployall commands, only webapplications deployed through the installer or wdeploy will be undeployed.



All other web applications can only be manually removed using the webapplication server's administrative console.

For information on all options available for wdeploy see DeployingBusinessObjects Enterprise Web Applications using wdeploy.

Note: The wdeploy command does not create a log file. To persist the outputgenerated by wdeploy, redirect its output to a file using the greater-than

redirect operator (>).

After deploying web applications

To verify the web application server configuration, make sure that InfoViewand the Central Management Console can be launched in a web browser.For example:• http://WAS_HOSTNAME:PORT/INFOVIEW_CONTEXT

• http://WAS_HOSTNAME:PORT/CMC_CONTEXT

Replace WAS_HOSTNAME with the hostname or IP address of your webapplication server, and PORT with the port number used for either HTTP orHTTPS communication. The default root context used for InfoView is InfoViewApp; the default context used for the CMC is CmcApp.

Deploying to web application servers with wdeploy

Deploying to WebSphere with wdeploy

Using predeploy and predeployall

The predeploy command creates resources and configuration files for aspecific web application, then copies the WAR application to <INSTALLDIR>/deployment/workdir/WS_VERSION, but does not deploy theweb application to the web application server. The predeployall commandperforms the predeploy command for all web applications.



Example 1: using wdeploy predeploy to predeploy InfoView to WebSphere.wdeploy.sh websphere6-Das_dir=/opt/ibm/WebSphere/AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_admin_port=8880-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto WebSphere.wdeploy.sh websphere6-Das_dir=/opt/ibm/WebSphere/AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_admin_port=8880predeployall

Using deployonly and deployonlyall

The deployonly command deploys a web application that is specificallyconfigured for the target web application server. The deployonlyall

command performs the deployonly command for all web applications.

Example 1: using wdeploy deployonly to deploy a predeployed InfoViewto WebSphere.wdeploy.sh websphere6-Das_dir=/opt/ibm/WebSphere/AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_admin_port=8880-DAPP=InfoViewAppdeployonly

Example 2: using wdeploy deployonlyall to deploy all predeployed webapplications to WebSphere.wdeploy.sh websphere6-Das_dir=/opt/ibm/WebSphere/AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_admin_port=8880deployonlyall



Using deploy and deployall

The deploy command creates resources and configuration files for a specificweb application, which is then deployed to the web application server. Thedeployall command performs the deploy command for all web applications.

Running deploy is equivalent to running a predeploy command followedby a deployonly command. Running deployall is equivalent to running apredeployall command followed by a deployonlyall command.

Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toWebSphere.wdeploy.sh websphere6-Das_dir=/opt/ibm/WebSphere/AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_admin_port=8880-DAPP=InfoViewAppdeploy

Example 2: using wdeploy deployall to predeploy, then deploy, all webapplications to WebSphere.wdeploy.sh websphere6-Das_dir=/opt/ibm/WebSphere/AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_admin_port=8880deployall

Using undeploy and undeployall

The undeploy command uninstalls a previously deployed web applicationfrom the web application server. The undeployall command performs theundeploy command for all web applications.

Example 1: using wdeploy undeploy to undeploy InfoView from WebSphere.wdeploy.sh websphere6-Das_dir=/opt/ibm/WebSphere/AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_admin_port=8880-DAPP=InfoViewAppundeploy



Example 2: using wdeploy undeployall to undeploy all web applicationsfrom WebSphere.wdeploy.sh websphere6-Das_dir=/opt/ibm/WebSphere/AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_admin_port=8880undeployall

Disable WebSphere JSF implementationIf pages rendered by WebSphere do not show cached values correctly, itmay be using its own version of the Java Server Faces (JSF) library, ratherthan the JSF implementation supplied with BusinessObjects Enterprise. Tocorrect this problem, you must manually reconfigure WebSphere for eachweb application that uses JSF: CmcApp, CmcAppActions, andPlatformServices.

To disable the JSF implementation supplied with WebSphere, follow theinstructions below.

1. Log in to the "WebSphere Application Server Administration" consoleusing the following URL: http://WAS_HOSTNAME:PORT/admin. TheWebSphere administration console's default port number is 9060.

2. Browse to YOUR_WEB_APPLICATION > Manage Modules >YOUR_WEB_APPLICATION.warReplace YOUR_WEB_APPLICATION in the example above with thename of your web application.

3. Stop the web application, so its settings can be modified.4. Select Classes loaded with application class loader first from the

combo box.Restart the web application.

5. Repeat these steps for all other web applications that use JSF.

Reload pages that display cached values. Cached values are now displayedcorrectly.

To deploy to separate IHS web and WebSphere web application serversTo reduce the load on a web application server, you can set up a separate,dedicated, web server to serve static content. All static content will be servedby the web server, while dynamic content will be served by the webapplication server.



Note: This configuration requires that you use the wdeploy command tosplit web application resources into static and dynamic content that can bedeployed to separate web and web application servers.

1. Set up an IBM HTTP Server (IHS) web server and ensure that it is workingcorrectly. Load a web page, such as the IHS default test page, to verifythat the web server is serving content correctly.Open a web browser and enter the IP address or hostname of the webserver, and a port number if the server is not listening on port 80. Forexample: http://mywebserver.mycompany.com:80.

2. Ensure that your WebSphere web application server is working correctly.Open a web browser and enter the IP address or hostname of the webapplication server, and a port number. For example:http://myappserver.mycompany.com:9080.

Note: If you have any existing BusinessObjects Enterprise webapplications running on the server, they must be undeployed beforecontinuing.

3. Run the web server plug-in installation wizard to install the plug-in thatbridges WebSphere with IHS, and follow the directions to enter informationabout your IHS web server.

4. Follow the plug-in configuration instructions on the WebSphere web sitefor configuring the bridge between IHS and WebSphere.Requests for dynamic resources are now forwarded to WebSphere whenreceived by IHS.

5. Ensure that the bridge between the web server and web application serveris working by pointing a browser to the web server and verifying thatdynamic content from the web application server is served correctly.For example, visit the URL: http://mywebserver.mycompany.com:80/snoop/.

6. If the web application server is installed on the same machine asBusinessObjects Enterprise, run wdeploy locally on that machine. If theweb application server runs on a different machine, you must copy thewdeploy command and environment to the web application server. SeeTo deploy web applications on a remote machine.

7. Configure wdeploy environment to separate content between the webserver and the web application server. This is known as "distributed"mode.



The wdeploy configuration files for IHS and WebSphere are located in<INSTALLDIR>/deployment.• Edit config.apache. For example:

#Business Objects Configuration Utilityws_dir=/opt/apacheconnector_type=websphere6deployment_dir=/opt/apache/htdocs

• Edit config.websphere6. For example:#Business Objects Configuration Utilityas_admin_port=8880as_admin_username=adminas_admin_password=passwordas_dir=/opt/websphere/appserveras_instance=server1as_virtual_host=default_hostas_admin_is_secure=falseenforce_file_limit=true

8. Use wdeploy predeploy in distributed mode to split source web applicationsinto separate static and dynamic resources.For example:• Run the following command to extract static content for the IHS web

server../wdeploy.sh websphere6 -Das_mode=distributed

-Dws_type=apache predeployall >> wdeploy.log

The dynamic content of web applications is located in: <INSTALLDIR>/deployment/workdir/websphere6/application.

The static content is located in: <INSTALLDIR>/deployment/workdir/websphere6/resources.

9. Run wdeploy deployonlyall command to deploy the dynamic content toWebSphere application server and static content to IHS.If IHS and WebSphere are on the same machine, static and dynamiccontent will be automatically deployed to servers by the followingcommand:./wdeploy.sh websphere6 -Das_mode=distributed

-Dws_type=apache deployonlyall >> wdeploy.log

Note: If your dynamic and static content are in a custom location, usethe -Dwork_dir parameter.



If IHS and WebSphere are on different machines, dynamic content willbe automatically deployed to WebSphere by the following command.Static content must be manually deployed to the remote IHS machineafterwards../wdeploy.sh websphere6 -Das_mode=distributed

-deployonlyall >> wdeploy.log


Copy static content to the htdocs directory on the web server:• Extract the zip files on the web application server under <IN

STALLDIR>/deployment/workdir/websphere6/resources.• Copy these folders from the WebSphere web application server to the

IHS <WS_DIR>/htdocs folder on the IHS server.• Copy the bobj.<application>.conf files from the WebSphere web

application server to the IHS <WS_DIR>/conf folder on the IHS server.• Update IHS httpd.conf under <WS_DIR>/conf with the application

config files. For each web application, you must include an entry inhttpd.conf. For example, to include AnalyticalReporting, you wouldenter:Include conf/bobj.AnalyticalReporting.conf

10. Propagate the plugin-cfg.xml file from the application server to theweb server using the administrative console. Click Servers > Web server.Select the web server, then click Propagate Plug-in. Web servers otherthan IHS require manual propagation.• For IHS, click Servers > Web server. Select the web server, then

click Propagate Plug-in.• For all other web servers, copy plugin-cfg.xml from the <pro

file_root>/config/cells/<cell_name>/nodes/node_name/servers/<Web_server_name> directory on the WebSphere web application server to the<plugins_root>/config/<Web_server_name> directory on the IHSweb server.

11. Ensure that both static and dynamic content are correctly configured bytrying to access a web application through the web server. For example,create a URL that includes the address of the web server with the rootcontext of a web application deployed to the web application server:http://mywebserver.mycompany.com:80/CmcApp/. In this example,



mywebserver.mycompany.com:80 is the web server, and /CmcApp/ is adeployed web application.

Static content is now served by a dedicated web server, and dynamic contentis served by a dedicated web application server.

Related Topics• How to use wdeploy on page 151• To deploy web applications on a remote machine on page 182

Deploying to WebLogic with wdeploy


The predeploy command creates resources and configuration files for aspecific web application, then copies the WAR application to <INSTALLDIR>/deployment/workdir/WS_VERSION, but does not deploy theweb application to the web application server. The predeployall commandperforms the predeploy command for all web applications.

Example 1: using wdeploy predeploy to predeploy InfoView to WebLogic.wdeploy.sh weblogic9-Das_dir=/opt/bea/user_projects/domains/base_domain-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_username=weblogic-Das_admin_password=weblogic-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto WebLogic.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=weblogicpredeployall






Example 1: using wdeploy deployonly to deploy a predeployed InfoViewto WebLogic.wdeploy.sh weblogic9-Das_dir=/opt/bea/user_projects/domains/base_domain-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_username=weblogic-Das_admin_password=weblogic-DAPP=InfoViewAppdeployonly

Example 2: using wdeploy deployonlyall to deploy all predeployed webapplications to WebLogic.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=weblogicdeployonlyall




Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toWebLogic.wdeploy.sh weblogic9-Das_dir=/opt/bea/user_projects/domains/base_domain-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_username=weblogic-Das_admin_password=weblogic



-DAPP=InfoViewAppdeploy

Example 2: using wdeploy deployall to predeploy, then deploy, all webapplications to WebLogic.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



Example 1: using wdeploy undeploy to undeploy InfoView from WebLogic.wdeploy.sh weblogic9-Das_dir=/opt/bea/user_projects/domains/base_domain-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_username=weblogic-Das_admin_password=weblogic-DAPP=InfoViewAppundeploy

Example 2: using wdeploy undeployall to undeploy all web applicationsfrom WebLogic.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

To deploy to separate Apache web and WebLogic web application serversTo reduce the load on a web application server, you can set up a separate,dedicated, web server to serve static content. All static content will be servedby the web server, while dynamic content will be served by the webapplication server.




1. Set up the Apache web server and ensure that it is working correctly.Load a web page, such as Apache's default test page, to verify that theweb server is serving content correctly.Open a web browser and enter the IP address or hostname of the webserver, and a port number if the server is not listening on port 80. Forexample: http://mywebserver.mycompany.com:80.

2. Ensure that your WebLogic web application server is working correctly.Open a web browser and enter the IP address or hostname of the webapplication server, and a port number. For example:http://myappserver.mycompany.com:7001.


3. Download the WebLogic Apache HTTP Server Plug-In from the BEA website. The plug-in allows you to connect an Apache web server with aWebLogic web application server, so Apache can forward requests fordynamic resources to WebLogic.

4. Follow the plug-in configuration instructions on the BEA web site forconfiguring the bridge between Apache web server and WebLogic.Requests for dynamic resources are now forwarded to WebLogic whenreceived by Apache.

5. Ensure that the bridge between the web server and web application serveris working by pointing a browser to the web server and verifying thatdynamic content from the web application server is served correctly.For example, visit the URL: http://mywebserver.mycompany.com:80/jsp-examples/.

6. If the web application server is installed on the same machine asBusinessObjects Enterprise, run wdeploy locally on that machine. If theweb application server runs on a different machine, you must copy thewdeploy command and environment to the web application server. SeeTo deploy web applications on a remote machine.

7. Configure wdeploy environment to separate content between the webserver and the web application server. This is known as "distributed"mode.



The wdeploy configuration files for Apache and WebLogic are located in<INSTALLDIR>/deployment.• Edit config.weblogic9 or config.weblogic10. For example:

#Business Objects Configuration Utilityas_admin_port=7001as_admin_username=weblogicas_admin_password=weblogicas_instance=AdminServeras_dir=/usr/bea/user_projects/domains/base_domain

• Edit config.apache. For example:#Business Objects Configuration Utilityws_dir=/opt/apache224/connector_type=weblogic9deployment_dir=/opt/apache224/htdocs

8. Use wdeploy predeploy in distributed mode to split source web applicationsinto separate static and dynamic resources.For example:• Run the following command to extract static content for the Apache

web server and dynamic content for Weblogic application server../wdeploy.sh weblogic9 -Das_mode=distributed


The dynamic content in: <INSTALLDIR>/deployment/workdir/weblogic9/application. Static content is located in: <INSTALLDIR>/deployment/workdir/weblogic9/resources.

9. Run wdeploy deployonlyall command to deploy the dynamic content toWebLogic application server and static content to Apache.If Apache and WebLogic are on the same machine, static and dynamiccontent will be automatically deployed to the servers by the followingcommand:./wdeploy.sh weblogic9 -Das_mode=distributed



If Apache and WebLogic are on different machines, dynamic content willbe automatically deployed to WebLogic by the following command. Static



content must be manually deployed to the remote Apache machineafterwards../wdeploy.sh weblogic9 -Das_mode=distributed




STALLDIR>/deployment/workdir/WebLogic6/resources.• Copy these folders from the WebLogic web application server to the

Apache <WS_DIR>/htdocs folder on the Apache server.• Copy the bobj.<application>.conf files from the WebLogic web

application server to the Apache <WS_DIR>/conf folder on the Apacheserver.

• Update Apache httpd.conf under <WS_DIR>/confwith the applicationconfig files. For each web application, you must include an entry inhttpd.conf. For example, to include AnalyticalReporting, you wouldenter:Include conf/bobj.AnalyticalReporting.conf



Deploying to Tomcat with wdeploy


The predeploy command creates resources and configuration files for aspecific web application, then copies the WAR application to <INSTALLDIR>/deployment/workdir/tomcat55, but does not deploy the webapplication to the web application server. The predeployall commandperforms the predeploy command for all web applications.



Example 1: using wdeploy predeploy to predeploy InfoViewApp to Tomcat.wdeploy.sh tomcat55-Das_dir=/opt/tomcat-Das_instance=localhost-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto Tomcat.wdeploy.sh tomcat55-Das_dir=/opt/tomcat-Das_instance=localhostpredeployall




Example 1: using wdeploy deployonly to deploy a InfoView to Tomcat.wdeploy.sh tomcat55-Das_dir=/opt/tomcat-Das_instance=localhost-DAPP=InfoViewAppdeployonly

Example 2: using wdeploy deployonlyall to deploy all predeployed webapplications to Tomcat.wdeploy.sh tomcat55-Das_dir=/opt/tomcat-Das_instance=localhostdeployonlyall






Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toTomcat.wdeploy.sh tomcat55-Das_dir=/opt/tomcat-Das_instance=localhost-DAPP=InfoViewAppdeploy

Example 2: using wdeploy deployall to predeploy, then deploy, all webapplications to Tomcat.wdeploy.sh tomcat55-Das_dir=/opt/tomcat-Das_instance=localhostdeployall



Example 1: using wdeploy undeploy to undeploy InfoView from Tomcat.wdeploy.sh tomcat55-Das_dir=/opt/tomcat-Das_instance=localhost-DAPP=InfoViewAppundeploy

Example 2: using wdeploy undeployall to undeploy all web applicationsfrom Tomcat.wdeploy.sh tomcat55-Das_dir=/opt/tomcat-Das_instance=localhostundeployall

Related Topics• After deploying web applications on page 192• After deploying web applications on page 192

To deploy to separate Apache web and Tomcat web application serversTo reduce the load on a web application server, you can set up a separate,dedicated, web server to serve static content. All static content will be served



by the web server, while dynamic content will be served by the webapplication server.


1. Set up the Apache web server and ensure that it is working correctly.Load a web page, such as Apache's default test page, to verify that theweb server is serving content correctly.Open a web browser and enter the IP address or hostname of the webserver, and a port number if the server is not listening on port 80. Forexample: http://mywebserver.mycompany.com:80.

2. Ensure that your Tomcat web application server is working correctly.Open a web browser and enter the IP address or hostname of the webapplication server, and a port number. For example:http://myappserver.mycompany.com:8080.


3. Download the Apache Tomcat connector from the Tomcat web site. TheApache Tomcat connector allows you to connect an Apache web serverwith a Tomcat web application server, so Apache can forward requestsfor dynamic resources to Tomcat.

4. Follow the plug-in configuration instructions on the Apache web site forconfiguring the bridge between Apache web server and Tomcat webapplication server.Requests for dynamic resources are now forwarded to Tomcat whenreceived by Apache.

5. Ensure that the bridge between the web server and web application serveris working by pointing a browser to the web server and verifying thatdynamic content from the web application server is served correctly.For example, visit the URL: http://mywebserver.mycompany.com:80/jsp-examples/.

6. If the web application server is installed on the same machine asBusinessObjects Enterprise, run wdeploy locally on that machine. If theweb application server runs on a different machine, you must copy the



wdeploy command and environment to the web application server. SeeTo deploy web applications on a remote machine.

7. Configure wdeploy environment to separate content between the webserver and the web application server. This is known as "distributed"mode.The wdeploy configuration files for Apache and Tomcat are located in<INSTALLDIR>/deployment.• Edit config.tomcat55. For example:

#Business Objects Configuration Utilityas_dir=/opt/Tomcat5520as_instance=localhostas_service_name=Tomcat5

• Edit config.apache. For example:#Business Objects Configuration Utilityws_dir=/opt/apache224connector_type=tomcat55deployment_dir=/opt/apache224/htdocs

8. Use wdeploy predeploy in distributed mode to split source web applicationsinto separate static and dynamic resources.For example:• Run the following command to extract static content for the Apache

web server../wdeploy.sh tomcat55 -Das_mode=distributed


9. Run wdeploy deployonlyall command to deploy the dynamic content toTomcat application server and static content to Apache.If Apache and Tomcat are on the same machine, static and dynamiccontent will be automatically deployed to servers by the followingcommand:./wdeploy.sh tomcat55 -Das_mode=distributed



If Apache and Tomcat are on different machines, dynamic content willbe automatically deployed to Tomcat by the following command. Static



content must be manually deployed to the remote Apache machineafterwards../wdeploy.sh tomcat55 -Das_mode=distributed




STALLDIR>/deployment/workdir/Tomcat55/resources.• Copy these folders from the Tomcat web application server to the

Apache <WS_DIR>/htdocs folder on the Apache server.• Copy the bobj.<application>.conf files from the Tomcat web

application server to the Apache <WS_DIR>/conf folder on the Apacheserver.

• Update Apache httpd.conf under <WS_DIR>/confwith the applicationconfig files. For each web application, you must include an entry inhttpd.conf. For example, to include AnalyticalReporting, you wouldenter:Include conf\bobj.AnalyticalReporting.conf



Deploying to Oracle with wdeploy


The predeploy command creates resources and configuration files for aspecific web application, then copies the WAR application to <INSTALLDIR>/deployment/workdir/oas1013, but does not deploy the webapplication to the web application server. The predeployall commandperforms the predeploy command for all web applications.



Example 1: using wdeploy predeploy to predeploy InfoView to OracleApplication Server.wdeploy.sh oas1013-Das_dir=/opt/oracle10gasr3/oracleas_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6013-Das_admin_username=oc4jadmin-Das_admin_password=oracle12-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto Oracle Application Server.wdeploy.sh oas1013-Das_dir=/opt/oracle10gasr3/oracleas_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6013-Das_admin_username=oc4jadmin-Das_admin_password=oracle12predeployall




Example 1: using wdeploy deployonly to deploy a predeployed InfoViewto Oracle Application Server.wdeploy.sh oas1013-Das_dir=/opt/oracle10gasr3/oracleas_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6013-Das_admin_username=oc4jadmin-Das_admin_password=oracle12-DAPP=InfoViewAppdeployonly



Example 2: using wdeploy deployonlyall to deploy all predeployed webapplications to Oracle Application Server.wdeploy.sh oas1013-Das_dir=/opt/oracle10gasr3/oracleas_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6013-Das_admin_username=oc4jadmin-Das_admin_password=oracle12deployonlyall




Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toOracle Application Server.wdeploy.sh oas1013-Das_dir=/opt/oracle10gasr3/oracleas_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6013-Das_admin_username=oc4jadmin-Das_admin_password=oracle12-DAPP=InfoViewAppdeploy

Example 2: using wdeploy deployall to predeploy, then deploy, all webapplications to Oracle Application Server.wdeploy.sh oas1013-Das_dir=/opt/oracle10gasr3/oracleas_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6013-Das_admin_username=oc4jadmin



-Das_admin_password=oracle12deployall



Example 1: using wdeploy undeploy to undeploy InfoView from OracleApplication Server.wdeploy.sh oas1013-Das_dir=/opt/oracle10gasr3/oracleas_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6013-Das_admin_username=oc4jadmin-Das_admin_password=oracle12-DAPP=InfoViewAppundeploy

Example 2: using wdeploy undeployall to undeploy all web applicationsfrom Oracle Application Server.wdeploy.sh oas1013-Das_dir=/opt/oracle10gasr3/oracleas_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6013-Das_admin_username=oc4jadmin-Das_admin_password=oracle12undeployall

Related Topics• After deploying web applications on page 192

Deploying to SAP Application Server with wdeploy


The predeploy command creates resources and configuration files for aspecific web application, then copies the WAR application to <IN



STALLDIR>/deployment/workdir/nw2004, but does not deploy the webapplication to the web application server. The predeployall commandperforms the predeploy command for all web applications.

Example 1: using wdeploy predeploy to predeploy InfoView to SAPApplication Server.wdeploy.sh nw2004-Das_dir=/opt/sap-Das_instance=server1-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50000-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto SAP Application Server.wdeploy.sh nw2004-Das_dir=/opt/sap-Das_instance=server1-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50000predeployall




Example 1: using wdeploy deployonly to deploy a predeployed InfoViewto SAP Application Server.wdeploy.sh nw2004-Das_dir=/opt/sap-Das_instance=server1-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50000-DAPP=InfoViewAppdeployonly



Example 2: using wdeploy deployonlyall to deploy all predeployed webapplications to SAP Application Server.wdeploy.sh nw2004-Das_dir=/opt/sap-Das_instance=server1-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50000deployonlyall




Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toSAP Application Server.wdeploy.sh nw2004-Das_dir=/opt/sap-Das_instance=server1-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50000-DAPP=InfoViewAppdeploy

Example 2: using wdeploy deployall to predeploy, then deploy, all webapplications to SAP Application Server.wdeploy.sh nw2004-Das_dir=/opt/sap-Das_instance=server1-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50000deployall





Example 1: using wdeploy undeploy to undeploy InfoView from SAPApplication Server.wdeploy.sh nw2004-Das_dir=/opt/sap-Das_instance=server1-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50000-DAPP=InfoViewAppundeploy

Example 2: using wdeploy undeployall to undeploy all web applicationsfrom SAP Application Server.wdeploy.sh nw2004-Das_dir=/opt/sap-Das_instance=server1-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50000undeployall


Deploying to JBoss with wdeploy

The Java Server Faces (JSF) bundled with the JBoss web application serversmust be disabled for the Central Management Console (CMC) and InfoViewweb clients to work correctly.

To disable JSF, the following directories must be removed and JBossrestarted:• JBOSS_HOME/server/default/deploy/jbossweb-tomcat55.sar/jsf-

libs

• JBOSS_HOME/server/default/tmp



• JBOSS_HOME/server/default/work

Note: To use the Javalog4j logging included with BusinessObjectsEnterprise XI 3.0, refer to section 10.3.7 Using your own log4j.properties file- class loader scoping in the JBoss Development Process Guide:http://docs.jboss.org/process-guide/en/html/logging.html#d0e3341.


The predeploy command creates resources and configuration files for aspecific web application, then copies the WAR application to <INSTALLDIR>/deployment/workdir/jboss404, but does not deploy the webapplication to the web application server. The predeployall commandperforms the predeploy command for all web applications.

Example 1: using wdeploy predeploy to predeploy InfoView to JBoss.wdeploy.sh jboss404-Das_dir=/opt/jboss-4.0.4.GA-Das_instance=default-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto JBoss.wdeploy.sh jboss404-Das_dir=/opt/jboss-4.0.4.GA-Das_instance=defaultpredeployall




Example 1: InfoView using wdeploy deployonly to deploy a predeployedInfoView to JBoss.wdeploy.sh jboss404-Das_dir=/opt/jboss-4.0.4.GA-Das_instance=default-DAPP=InfoViewAppdeployonly



http://docs.jboss.org/process-guide/en/html/logging.html#d0e3341

Example 2: using wdeploy deployonlyall to deploy all predeployed webapplications to JBoss.wdeploy.sh jboss404-Das_dir=/opt/jboss-4.0.4.GA-Das_instance=defaultdeployonlyall




Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toJBoss.wdeploy.sh jboss404-Das_dir=/opt/jboss-4.0.4.GA-Das_instance=default-DAPP=InfoViewAppdeploy

Example 2: using wdeploy deployall to predeploy, then deploy, all webapplications to JBoss.wdeploy.sh jboss404-Das_dir=/opt/jboss-4.0.4.GA-Das_instance=defaultdeployall



Example 1: using wdeploy undeploy to undeploy InfoView from JBoss.wdeploy.sh jboss404-Das_dir=/opt/jboss-4.0.4.GA-Das_instance=default



-DAPP=InfoViewAppundeploy

Example 2: using wdeploy undeployall to undeploy all web applicationsfrom JBoss.wdeploy.sh jboss404-Das_dir=/opt/jboss-4.0.4.GA-Das_instance=defaultundeployall


To deploy web applications on a remote machine

Use the procedure below to deploy web applications to a remote machine.In this procedure Box 1 refers to the machine hosting your BusinessObjectsEnterprise installation, and Box 2 is the remote machine on which noBusinessObjects Enterprise resources are currently installed.

1. Create on Box 2 the following directories.• <INSTALLDIR>/deployment/. The deployment folder contains the

wdeploy scripts and configuration files.• <INSTALLDIR>/bobje/enterprise120/java/applications/

• <INSTALLDIR>/Performance_Management_120/

• <INSTALLDIR>/caf/

These directories reflect the default directory structure installed on Box1.

Tip: Although you can customize the folder structure to meet your specificrequirements, it is recommended that you maintain files within the samefolder structure or hierarchy in Box 2 as in Box 1.

2. Copy the following files from Box 1 to Box 2.• Copy all the contents under <INSTALLDIR>/bobje/deployment/

Note: This content is also available on the product distribution mediaunder the following directory:

Collaterals/Tools/wdeploy



Tip: Remove the contents under <INSTALLDIR>/bobje/deployment/workdir after the file copy if that folder is not empty.

• Copy all the contents under <INSTALLDIR>/bobje/enterprise120/java/applications/.

• From <INSTALLDIR>/Performance_Management_120/ copy InitConfig.properties.

• Copy the contents of <INSTALLDIR>/caf/.

3. Set the JAVA_HOME environment variable to JDK 1.5 directory.4. Configure the WAR file directory for each web application. If you keep all

the WAR files in the same folder, you don't need to configure the WARfile directory for each web application, skip to step 5.a. Open the properties file under <INSTALLDIR>/deployment/apps and

modify the properties file for each web application (e.g CrystalReports.properties).

b. Enter the following parameter in a new line:war_dir The value of the parameter is the WAR file path name.If you are going to deploy CrystalReports.war, you would set the valueof war_dir in <INSTALLDIR>/deployment/apps/CrystalReports.properties towar_dir=/home/bobje/enterprise120/java/applications/CrystalReports.war

c. Repeat steps a-b for all the web applications you want to deploy toyour web application server.

5. Modify the wdeploy configuration file for your web application server. Youmust provide all the required information to enable wdeploy to deploy theweb application.For example, to modify the configuration file for WebLogic 9, you wouldmodify the file to:as_dir=/bea92/user_projects/domains/base_domainas_instance=AdminServeras_admin_port=7001as_admin_username=weblogicas_admin_password=weblogic

The configuration file is located in the following directory:<INSTALLDIR>/deployment/config.<appserver> .



6. If the Performance Management 12.0 files you copied in step 2 are notlocated under the same folder structure as Box 1, to deploy PerformanceManagement you must do the following:a. Extract PerformanceManagement.war from the following directory:

<INSTALLDIR>/bobje/enterprise120/java/applications/

b. Set the af.configdir parameter in theweb.xml file to the location ofthe InitConfig.properties file.Theweb.xml file is located in: /PerformanceManagement/WEB-INF .The modified file should look like the example below.

<context-param><param-name>af.configdir</param-name><param-value>/home/Performance_Management_120</param-value></context-param>

c. Repackage the PerformanceManagement.war.

7. Run the wdeploy script from its location in Box 2 by opening commandline console and entering the following:<INSTALLDIR>/deployment/wdeploy.sh

<appserver> deployall -Dwar_dir=<INSTALLDIR>/bobje/enterprise120/java/applications/ >> <logfilename>.log

You can pass the -Dwar_dir (with the path to the WAR files) in thecommand line to specify the location from which wdeploy accesses noncustomized WAR files.

Tip: You can drop the deployable war files to non-default location bypassing the parameter -Dwork_dir=your desired location as part of thewdeploy command.

Related Topics• How to use wdeploy on page 151• Prerequisites for using wdeploy on page 149



Manually deploying to aweb applicationserver

BusinessObjects Enterprise WAR files

BusinessObjects Enterprise separates web application functionality intoseveral Web ARchive (WAR) files, making it easier to deploy only the webapplications required by your organization.

Once you have installed BusinessObjects Enterprise the source files areavailable in the following directory: <INSTALLDIR>/bobje/enterprise120/java/applications/

The following table summarizes the relationship between the WAR files andspecific web applications in a BusinessObjects Enterprise deployment.

Used byWAR file

Query BuilderAdminTools

Web Intelligence, Desktop Intelligence, CMC, InfoViewAnalyticalReporting

Web services componentsBusinessProcessBI

CMC (entry point)CmcApp

CMCCmcAppActions

Crystal Reports, CMC, InfoViewCrystalReports

Web services componentsdswsbobje

InfoView (entry point)InfoViewApp

InfoViewInfoViewAppActions

Open DocumentOpenDocument

Performance Management, CMC, InfoViewPerformanceManagement

CMC, InfoViewPlatformServices

Performance ManagementPMC_Help


11Post Installation Web Application DeploymentManually deploying to a web application server

Used byWAR file

CMC, InfoViewVoyagerClient

Xcelsius data presentationXCelsius

Xcelsius data presentationXCTemplateUploader

WAR file context roots

All WAR files, with the exception of InfoViewApp and CmcApp, can bedeployed to fix context root locations on your web application server. Thefollowing table lists the context roots that must be used, unless otherwisenoted.

WAS context path (default)WAR file

/AdminToolsAdminTools

/AnalyticalReportingAnalyticalReporting

/BusinessProcessBIBusinessProcessBI

/CmcApp

Note: You may use a different root context for CmcApp aslong as the root context matches the name of the WAR file. Forexample, a root context of /MyOrgCmc requires the WAR fileto be named MyOrgCmc.war.

CmcApp

/CmcAppActionsCmcAppActions

/CrystalReportsCrystalReports

/dswsbobjedswsbobje


Post Installation Web Application Deployment11 Manually deploying to a web application server

WAS context path (default)WAR file

/InfoViewApp

Note: You may use a different root context for InfoViewAppas long as the root context matches the name of the WAR file.For example, a root context of/MyOrgInfo requires the WARfile to be named MyOrgInfo.war.

InfoViewApp

/InfoViewAppActionsInfoViewAppActions

/OpenDocumentOpenDocument

/PerformanceManagementPerformanceManagement

/PlatformServicesPlatformServices

/PMC_HelpPMC_Help

/VoyagerClientVoyagerClient

/XCelsiusXCelsius

/XCTemplateUploaderXCTemplateUploader

Guidelines for deploying WAR files

To successfully deploy the WAR files and to ensure your BusinessObjectsweb applications run properly, you should use the following guidelines.

1. Your web application server must be installed and running before youdeploy any WAR file.

2. The order in which you deploy the WAR files for your web applicationsdoes not matter. However, if your deployment environment involvesreverse proxy, there is a specific order you must follow. For moreinformation see “Modifying Default Security Behavior ” in theBusinessObjects Enterprise Administrator's Guide.



3. When deploying a web application with functionality shared betweenmultiple WAR files, each WAR file must reside within the same level ofthe context path.

4. As a general rule, do not rename the WAR files.

Note:

• Only two web applications can be renamed: InfoViewApp and CmcApp.To rename InfoViewApp you can rename the application using theweb application server administration console.

• To rename CmcApp, you must update the appservice.url.defaultparameter in the web.xml file located in the WEB-INF directory of theCmcApp.war and CmcAppActions.war. Change CmcApp in the<param-value> tag shown below, to the new application name.<context-param><param-name>appservice.url.default</param-name><param-value>/NewCMC/App/appService.jsp</param-value></context-param>

To manually deploy web applications

Ensure that your web application server and CMS are both running.

The following steps will deploy a web application on a web application serverusing the application server's administrative console. If the application serveris located on a machine other than your BusinessObjects Enterprise machine,follow the steps in To prepare a manual deployment on a remote machine.

The wdeploy tool must be used to generate deployable WAR files beforethey can be deployed to your web application server.

1. Run the wdeploy predeploy command to prepare a single webapplication, or wdeploy predeployall to prepare all web applications.

Example 1: using wdeploy predeploy to prepare InfoViewApp fordeployment to Tomcat.wdeploy.sh tomcat55-Das_dir=/opt/usr/tomcat-Das_instance=localhost-Das_service_name=Tomcat55-DAPP=InfoViewApppredeploy



Example 2: using wdeploy predeployall to prepare all web applicationsfor deployment to Tomcat.wdeploy.sh tomcat55-Das_dir=/opt/usr/tomcat-Das_instance=localhost-Das_service_name=Tomcat55predeployall

The wdeploy command will prepare the web application files fordeployment on the web application server.

The wdeploy command creates WAR or EAR files in <INSTALLDIR>/deployment/workdir/<appserver>/application unless you specify the-Dwork_dir parameter.

2. Follow the manual deployment procedure specific to your web applicationserver.

Your web applications can now be manually deployed on your web applicationserver.

Repeat these steps for any other web applications that need to be installed.

Related Topics• Where to find wdeploy on page 149• How to use wdeploy on page 151• To deploy web applications on a remote machine on page 182• To prepare for manual deployment on a remote machine on page 189• Minimum rights for deploying web applications on page 18

To prepare for manual deployment on a remotemachine

Use the procedure below to manually deploy web applications to a remotemachine.

In this procedure Box 1 refers to the machine hosting your BusinessObjectsEnterprise installation, and Box 2 is the remote machine on which noBusinessObjects Enterprise resources are currently installed.1. Create on Box 2 the following directories.



<INSTALLDIR>/deployment/. The deployment folder contains thewdeploy scripts and configuration files.

•

• <INSTALLDIR>/bobje/enterprise120/java/applications/

• <INSTALLDIR>/Performance_Management_120/

• <INSTALLDIR>/caf/

These directories reflect the default directory structure installed on Box1.

Tip: Although you can customize the folder structure to meet your specificrequirements, it is recommended that you maintain files within the samefolder structure or hierarchy in Box 2 as in Box 1.

2. Copy the following files from Box 1 to Box 2.• Copy all the contents under <INSTALLDIR>/bobje/deployment/

Note: This content is also available on the product distribution mediaunder the following directory:

Collaterals/Tools/wdeploy

Tip: Remove the contents under <INSTALLDIR>/bobje/deployment/workdir after the file copy if that folder is not empty.

• Copy all the contents under <INSTALLDIR>/bobje/enterprise120/java/applications/.

• From <INSTALLDIR>/Performance_Management_120/ copy InitConfig.properties.

• Copy the contents of <INSTALLDIR>/caf/.

3. Set the JAVA_HOME environment variable to JDK 1.5 directory.4. Configure the WAR file directory for each web application. If you keep all

the WAR files in the same folder, you don't need to configure the WARfile directory for each web application, skip to step 5.a. Open the properties file under <INSTALLDIR>/deployment/apps and

modify the properties file for each web application (e.g CrystalReports.properties).

b. Enter the following parameter in a new line:war_dir The value of the parameter is the WAR file path name.



If you are going to deploy CrystalReports.war, you would set the valueof war_dir in <INSTALLDIR>/deployment/apps/CrystalReports.properties towar_dir=/home/bobje/enterprise120/java/applications/CrystalReports.war

c. Repeat steps a-b for all the web applications you want to deploy toyour web application server.

5. Modify the wdeploy configuration file for your web application server. Youmust provide all the required information to enable wdeploy to preparethe WAR file for manual deployment.For example, to modify the configuration file for WebLogic 9, you wouldmodify the file to:as_dir=/bea92/user_projects/domains/base_domainas_instance=AdminServeras_admin_port=7001as_admin_username=weblogicas_admin_password=weblogic

The configuration file is located in the following directory:<INSTALLDIR>/deployment/config.<appserver> .

6. If the Performance Management 12.0 files you copied in step 2 are notlocated under the same folder structure as Box 1, to deploy PerformanceManagement you must do the following:a. Extract PerformanceManagement.war from the following directory:


b. Set the af.configdir parameter in the web.xml file to the location ofthe InitConfig.properties file.The web.xml file is located in: /PerformanceManagement/WEB-INF.The modified file should look like the example below.

<context-param><param-name>af.configdir</param-name><param-value>/home/Performance_Management_120</param-value></context-param>

c. Repackage the PerformanceManagement.war.



7. Run the wdeploy script from its location in Box 2 by opening commandline console and entering the following:<INSTALLDIR>/deployment/wdeploy.sh

<appserver> predeployall -Dwar_dir=<INSTALLDIR>/bobje/enterprise120/java/applications/ >> <logfilename>.log

You can pass the -Dwar_dir (with the path to the WAR files) in thecommand line to specify the location from which wdeploy accesses noncustomized WAR files.

Tip: You can drop the deployable war files to non-default location bypassing the parameter -Dwork_dir=your desired location as part of thewdeploy command.

8. The wdeploy command creates WAR or EAR files in <INSTALLDIR>/deployment/workdir/<appserver>/application unless you specify the-Dwork_dir parameter. Follow the manual deployment steps for yourweb application server.

You are now prepared to manually deploy web applications on Box 2.

Related Topics• How to use wdeploy on page 151• Prerequisites for using wdeploy on page 149

After deploying web applications

To verify the web application server configuration, make sure that InfoViewand the Central Management Console can be launched in a web browser.For example:• http://WAS_HOSTNAME:PORT/INFOVIEW_CONTEXT

• http://WAS_HOSTNAME:PORT/CMC_CONTEXT

Replace WAS_HOSTNAME with the hostname or IP address of your webapplication server, and PORT with the port number used for either HTTP orHTTPS communication. The default root context used for InfoView is InfoViewApp; the default context used for the CMC is CmcApp.



Deploying with the Administration console

Deploying with the WebSphere administrative console

Ensure that your WebSphere web application server is installed, configured,and running before deploying WAR files.

Log in to the "WebSphere Application Server Administration" console usingthe following URL: http://WAS_HOSTNAME:PORT/admin The WebSphereadmininstration console's default port number is 9060.

1. Under the Applications heading of the console navigation menu, clickEnterprise Applications on the left navigational pane.

2. Click the Install button and navigate to the location of the WAR file todeploy.

3. Enter a context root for the WAR file (e.g. CmcApp/ for CmcApp.war) andpress the Next button, followed by Continue.

4. In "Step 1", give a unique name for your web application and proceed to"Step 2".

5. Highlight the server you created (or highlight server1 if you didn't createyour own) from the Clusters and Servers and enable the Selectcheckbox. Proceed to "Step 3".

6. Select the virtual host you created (or default_host if you didn't createyour own) from the Virtual Host drop-down list. Proceed to "Step 4".

7. Review the summary page, and press Finish when done.8. Click Save to Master Configuration.9. Click the Save link, then the Save button.

10. Under the Applications heading of the console navigation menu, clickEnterprise Applications on the left navigational pane.

11. Verify that the WAR file was deployed, then click the Start button.Repeat steps 1-11 for each WAR file to deploy.




Disable WebSphere JSF implementationIf pages rendered by WebSphere do not show cached values correctly, itmay be using its own version of the Java Server Faces (JSF) library, ratherthan the JSF implementation supplied with BusinessObjects Enterprise. Tocorrect this problem, you must manually reconfigure WebSphere for eachweb application that uses JSF: CmcApp, CmcAppActions, andPlatformServices.

To disable the JSF implementation supplied with WebSphere, follow theinstructions below.

1. Log in to the "WebSphere Application Server Administration" consoleusing the following URL: http://WAS_HOSTNAME:PORT/admin. TheWebSphere administration console's default port number is 9060.

2. Browse to YOUR_WEB_APPLICATION > Manage Modules >YOUR_WEB_APPLICATION.warReplace YOUR_WEB_APPLICATION in the example above with thename of your web application.

3. Stop the web application, so its settings can be modified.4. Select Classes loaded with application class loader first from the

combo box.Restart the web application.

5. Repeat these steps for all other web applications that use JSF.

Reload pages that display cached values. Cached values are now displayedcorrectly.

To deploy to a WebSphere clusterTo manually deploy BusinessObjects Enterprise web applications to aWebSphere web application cluster distributed over multiple machines, youneed to deploy the web applications to the machine hosting the WebSphereDeployment Manager. Once all the required web applications have beeninstalled, you can use the WebSphere Integrated Solutions Console toseparately deploy these applications to the cluster.

Tip: It is recommended that you install and configure a hardware or softwareload balancer if running BusinessObjects Enterprise web applications on aWebSphere web application cluster. To configure the load balancer andcluster setup please consult your WebSphere documentation.



To deploy your web applications to a WebSphere cluster use the followinggeneral workflow:

1. If BusinessObjects Enterprise is installed to the same machine hostingthe WebSphere Deployment Manager, skip to step 3. If BusinessObjectsEnterprise and the WebSphere Deployment Manager run on differentmachines, you must first copy the wdeploy tool and environment to themachine hosting the WebSphere administration server.

If you plan to deploy PerformanceManagement.war to the WebSpherecluster, you must copy InitConfig.properties from <INSTALLDIR>/Performance_Management_120 to each managed server and ensure the filepath of InitConfig.properties is matches the value specified for af.configdirparam in web.xml in PerformanceManagement.war as shown below:<context-param>

<param-name>af.configdir</param-name><param-value> /home/Performance_Management_120

</param-value><context-param>

Note: The InitConfig.properties file should be located in C:\ProgramFiles\BusniessObjects\Performance Management 12.0 on eachmachine hosting a managed WebSphere server.

2. Modify the config.websphere6 file located in the following directory:<INSTALLDIR>/deployment/. You need to specify information for theserver administrating the cluster as shown in the following example.as_dir=<INSTALLDIR>/IBM/WebSphere/AppServeras_admin_port=8779as_virtual_host=default_hostas_admin_is_secure=falseenforce_file_limit=true

3. Open a command-line console and run the following command:<INSTALLDIR>/deployment>wdeploy.sh websphere6 predeployall

4. Open the WebSphere Integrated Solutions Console.5. Go to Applications > Enterprise Applications to separately install each

web application you want to deploy from the following directory:<INSTALLDIR>/deployment/workdir/websphere6/application/

Note: All web applications are stored as EAR modules.



6. Follow the Install new application steps in the console to install the webapplication

Note: In "Map modules to servers", make sure that you highlight thetarget cluster and select the module to install before clicking Apply.

7. After installing the application, click Save.8. Repeat steps 4-6 for each EAR file you want to install.9. Go to System administration > Nodes and select the nodes in the cluster

that are not indicated as synchronized10. Click Synchronize.11. Go to Applications > Enterprise Applications to start the application

you just installed.

Related Topics• To deploy web applications on a remote machine on page 182

Deploying with the WebLogic administrative console

Ensure that your WebLogic web application server is installed, configured,and running before deploying WAR files. You must also have created aWebLogic domain in which to run BusinessObjects Enterprise. See yourWebLogic documentation for information about creating a new domain.

Note:

• Deployable web applications for WebLogic are in the following format inthe wdeploy workdir folder:• WebServices (ProcessBI and dswsbobje) are folders• AnalyticalReporting and PerformanceManagement are EAR files• Rest of WebApps are WAR files

• WebLogic deployments must use an extracted dswsbobje.war. See Todeploy dswsbobje.war to WebLogic on page 199.

1. Open the "WebLogic Administrative Console" with a web browser at ahttp://WAS_HOSTNAME:PORT/console where WAS_HOSTNAME is thename of your WebLogic server and PORT_NUMBER is the port numberon which the server listens.The "WebLogic Server Administration Console" web page is displayed.

2. In the left-hand navigation pane, click base_domain > Deployments .



The "Summary of Deployments" page is displayed.

3. Click the Lock and Edit button in the left-hand pane.The domain is locked for editing.

4. Press the Install button and navigate to the WAR file you wish to deploy.When you've selected the file and specified any other parameters in thewizard, click the Finish button to deploy the file.The WAR file is deployed to the WebLogic server.

5. Press the Activate Changes button to apply you're the changes to theweb application server.Your changes are saved.

6. When your WAR file has been deployed, you must press the Start buttonto initiate its execution.The web application you deployed will now start.


To deploy to a WebLogic clusterTo manually deploy BusinessObjects Enterprise web applications to aWebLogic cluster distributed over multiple machines, you need to deploy theweb applications to the machine hosting the WebLogic administration server.Once all the required web applications have been installed, you can use theWebLogic administration console to deploy these applications to the cluster.

Tip: It is recommended that you install and configure a hardware or softwareload balancer if running BusinessObjects Enterprise web applications on aWebLogic web application cluster. To configure the load balancer and clustersetup please consult your WebLogic documentation.

To deploy to a WebLogic cluster use the following general workflow:

1. After installing and setting up the WebLogic cluster, you need to createa WebLogic XML registry using the following default settings and targetit to all managed servers as shown below:

ValueProperty

Registry nameName



ValueProperty

weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl

Document Builder Facto-ry

weblogic.apache.xerces.jaxp.SAXParserFactoryImpl

SAX Parser Factory

weblogic.apache.xalan.processor.TransformerFactoryImpl

Transformer Factory

2. If BusinessObjects Enterprise is installed to the same machine hostingthe WebLogic administration server, skip to step 6. If BusinessObjectsEnterprise and the WebLogic administration server run on differentmachines, you must first copy the wdeploy tool and environment to themachine hosting the WebLogic administration server.

If you plan to deploy PerformanceManagement.war to the WebLogiccluster, you must copy InitConfig.properties from <INSTALLDIR>/Performance_Management_120 to each managed server and ensure the filepath of InitConfig.properties is matches the value specified for af.configdirparam in web.xml in PerformanceManagement.war as shown below:<context-param>

<param-name>af.configdir</param-name><param-value>/home/Performance_Management_120

</param-value><context-param>

3. Modify the config.weblogic10 or the config.weblogic9 located in thefollowing directory:<INSTALLDIR>/deployment/. You need to specify information for theserver administrating the cluster as shown in the following example.as_dir=/bea/user_projects/domains/base_domainas_instance=AdminServeras_admin_port=7001as_admin_username=weblogicas_admin_password=password

4. Modify the PersistentStoreType setting in the weblogic.xml file locatedin the following directory:<INSTALLDIR>/deployment/templates/weblogic.xml. Themodifiedweblogic.xml settings will look like the example below:<weblogic-web-app>

<session-descriptor>



<session-param><param-name>PersistentStoreType</param-name>

<param-value>replicated</param-value>

</session-param></session-descriptor>

5. Open a command-line console and run the following command:<INSTALLDIR>/deployment>wdeploy.sh weblogic10 predeployall

6. Use the WebLogic administration console to separately install each webapplication you want to deploy from the following directory:<INSTALLDIR>/deployment/workdir/weblogic10/application/.

7. In the "Select deployment targets"workflow select the cluster name andAll servers in the cluster.

8. After the"Select deployment targets" workflow is complete, select all theinstalled applications and go to Start > Servicing all requests.

To deploy dswsbobje.war to WebLogicBefore deploying web services WAR file on a WebLogic application server,the user must extract dswsbobje.war. If the WAR file is not extracted andredeployed, web services applications may display the error message “AnXSD Exception occurred”.

1. Extract dswsbobje.war to a directory on the WebLogic web applicationserver.

2. Log on to the "WebLogic Administration Console".3. Click Lock & Edit.4. Go to Domain Structure > Deployments and click Install.5. Browse to the extracted dswsbobje.war directory.6. Select the directory and click Next.7. Select Install this deployment as an application and click Next.8. Verify the settings and click Finish.

A message will be displayed when the dswsbobje.war web applicationhas been successfully deployed. The list of web applications contains thedswsbobje web application.

9. Select the dswsbobje web application and click Start.10. Click Activate Changes.



11. Select the dswsbobje web application and click Start.12. Press OK to confirm the changes.

The dswsbobje web application is started.

13. Open the web application in a web browser to confirm that it now runs.


Deploying with the Tomcat administrative console

Ensure that your Tomcat web application server is installed, configured, andrunning before deploying WAR files.

Log on to the "Tomcat Manager Console".• http://WAS_HOSTNAME:PORT/manager/html

1. Set the Context Path for the web application to be deployed. The contextpath must be the name of the WAR file, but without its extension. Forexample, to deploy a web application packaged as MyWebApplication.war, the context path must be MyWebApplication.

2. Set the XML Configuration File setting to be an XML file that containsthe context path and document base. For example: <ContextdocBase="<M>/WEB_APPLICATION.war" path="<context_path>"crossContext="false" debug="0" reloadable="false" trusted="false"/>

3. Enter the full path to the WAR file and press the Deploy buttonThe WAR file you chose is deployed.


Special considerations for deploying on Tomcat clustersTo manually deploy web applications to a Tomcat web application clusterdistributed over multiple machines, you need to deploy the web applicationson to each Tomcat instance. You can use the administrative console todeploy the BusinessObjects Enterprise web applications to the webappssubfolder in the Tomcat home directory for each server instance.



Tip: It is recommended that you install and configure a hardware or softwareload balancer if running BusinessObjects Enterprise web applications on aTomcat web application cluster. To configure the load balancer and clustersetup please consult your Tomcat documentation.

Deploying with the Oracle Application Server administrativeconsole

Ensure that your Oracle Application Server web application server is installed,configured, and running before deploying WAR files. You must also havecreated an Oracle container for Java (OC4J) container in which to runBusinessObjects Enterprise.

1. Open the Oracle Application Server Enterprise Manager server page athttp://WAS_HOSTNAME:PORT/em. Replace WAS_HOSTNAME with thehostname or IP address of your web application server, and PORT withthe port number used for HTTP. The default port for Oracle ApplicationServer is 7777.The Oracle Application Server Control page is displayed.

2. Click on the home OC4J container.The home group is displayed under the Groups heading.

3. In the home OC4J container, click on the Applications tab.Currently deployed web applications are displayed.

4. Click on the Deploy button.The Deploy: Select Archive window is displayed.

5. Ensure that the Archive is present on local host option is selected,unless the web application is already running on the server, in which caseselect Archive is already present on the server where ApplicationServer Control is running.

6. Enter the full path, or browse, to the WAR file in the Archive Locationfield.

7. Press the Next button to advance to the next step in the WAR deploymentwizard.Step 2 of 3, Deploy: Application Attributes is displayed.

8. Enter the application name and context root of the file you wish to deploy.By default, the context root will contain the application name. For example,



for InfoView.war, the application name will be InfoView. When ready,press Next to proceed.The Step 3 of 3, Deploy: Deployment Settings page is displayed.

9. Select the class loading options you want enabled for the WAR file andpress Next to proceed.If your application requires any class libraries, click on Configure ClassLoading from the Deployment Tasks section.

10. In the Configure Web Module Class Loaders field, specify the locationof JAR file containing the libraries.

11. Click on the Deploy button to complete the deployment.Check the output of the Progress Messages log field that web applicationhas been deployed.


Deploying with the JBoss administrative console

Ensure that your JBoss web application server is installed, configured, andrunning before deploying WAR files.

The Java Server Faces (JSF) bundled with the JBoss web application serversmust be disabled for the Central Management Console (CMC) and InfoViewweb clients to work correctly.

To disable JSF, the following directories must be removed and JBossrestarted:• JBOSS_HOME/server/default/deploy/jbossweb-tomcat55.sar/jsf-

libs

• JBOSS_HOME/server/default/tmp

• JBOSS_HOME/server/default/work

Note: To use the Javalog4j logging included with BusinessObjectsEnterprise XI 3.0, refer to section 10.3.7 Using your own log4j.properties file- class loader scoping in the JBoss Development Process Guide:http://docs.jboss.org/process-guide/en/html/logging.html#d0e3341.

The following deployment paths are based upon the different levels of service:



http://docs.jboss.org/process-guide/en/html/logging.html#d0e3341

• JBOSS_HOME/server/all/deploy

• JBOSS_HOME/server/default/deploy

• JBOSS_HOME/server/minimal/deploy

1. Copy your WAR files to the appropriate context root sub-directory underone of the above paths, based upon the level of service provided by JBossfor your deployment.The web application will be automatically deployed by JBoss when thefile is copied to the appropriate directory.

2. Check the JBoss server log, and you should see a message similar tothe one shown below to confirm that the WAR deployment succeeded.06:23:08,906 INFO;TomcatDeployer deploy,ctxPath=.../BusinessObjects Enterprise 12.0/adminlaunch,warUrl=.../tmp/deploy/tmp38470admin-exp.war/06:23:09,562 INFO; [ReportSourceBridge] Servlet viewrptstarted.


Deploying with the SAP Application Server console

Ensure that your SAP Application Server web application server is installed,configured, and running before deploying WAR files.

First, archive your web application server.

1. Start the "Visual Administrator" tool by running go from<SAP_HOME>/sap/CTB/JC00/j2ee/admin. Connect to your J2EE engineusing the Administrator account.

2. In the "Visual Administrator", select the Cluster tab and expand theServer > Services > Deploy node within the J2EE tree.

3. Click Deploy & Start in the Runtime tab of the right-hand pane. If youwould like to start the web application manually later, click the Deploybutton instead.

4. In the "Deploy & Start" dialog window that appears, select the EAR filearchive you created earlier. Click OK when done.

5. In the "Deploy Dialog" window, verify the root context and display nameproperties. Press OK to deploy.The web application will now be deployed.




Deploying with the WebSphere Community Edition administrativeconsole

Ensure that your WebSphere Community Edition web application server isinstalled, configured, and running before deploying web applications.

Note: The wdeploy command-line deployment tool currently does not supportdeployment to WebSphere Community Edition. You can only deploy webapplications using the WebSphere Community Edition administrative console.To deploy BusinessObjects Enterprise web applications with theadministrative console, use the directory that contains the web applicationcode directly:


Log in to the WebSphere"Application Server Community EditionAdministrative Console" using the following URL: http://WAS_HOSTNAME:PORT/console The WebSphere Community Edition admin console'sdefault port number is 8880.

1. Ensure the myfaces-deployer system module is turned off. Click on theSystem Modules link on the Console Navigation bar. Then click on theExpert User check box located at the top. Scroll down to findorg.apache.geronimo.configs/myfaces-deployer/2.0.1/car andclick on the Stop link.The myfaces-deployer module is turned off.

2. Add a geronimo-web.xml file to the WEB-INF directory of each webapplication file.Here is a standard geronimo-web.xml file for use with CmcApp:<web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.2"xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2"xmlns:sec="http://geronimo.apache.org/xml/ns/security-1.2"xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.2">

<sys:environment><sys:moduleId><sys:groupId>com.businessobjects</sys:groupId><sys:artifactId>CmcApp</sys:artifactId><sys:version>2.0.0.1</sys:version>



<sys:type>war</sys:type></sys:moduleId><sys:dependencies/><sys:hidden-classes><sys:filter>com.sun.faces</sys:filter><sys:filter>javax.faces</sys:filter></sys:hidden-classes><sys:non-overridable-classes/></sys:environment><context-root>/CmcApp</context-root></web-app>

Note: The sys:artifactId and context-root elements must beupdated with the name of the web application being deployed. Forexample, to add geronimo-web.xml to InfoViewApp, use <sys:artifactId>InfoViewApp</sys:artifactId> and <context-root>/InfoViewApp</context-root>.

3. Under the Applications heading of the console navigation menu, clickDeploy New in the left navigational pane.

4. Click the Install New button to view the "Install New Applications" screen.5. Click the archive Browse button and navigate to the location of the

directory that contains the web application to deploy.<INSTALLDIR>/bobje/enterprise120/java/applications/

6. Select any other options you want to use, such as Start app after installor Redeploy application.

7. Click Install to install the web application.After the web application is deployed, a list of installed web applicationsis displayed.

8. Verify that the web application was deployed. Repeat steps 2-5 for eachapplication to deploy.




Deployment Scenarios

12

Overview of deployment scenariosTo improve your experience in installing and deploying BusinessObjectsEnterprise this section provides two sample scenarios. These examples arefor illustrative purposes. Each example includes a deployment diagram, keytasks, key configuration details, functional requirements and pre-conditions.The scenarios focus on two deployment characteristics:

• Desktop client to server• Basic n-tier

Desktop client to server scenario

Desktop client to server overview

This scenario illustrates a simple client to server scenario which involves adesktop client application - Desktop Intelligence - connecting to theBusinessObjects Enterprise back-end server behind a firewall.

System layers

• Data Tier: one machine with existing database server.• Server Tier: one machine for hosting the framework servers and another

for all other BusinessObjects servers.• Client Tier: one machine for installing and running Desktop Intelligence.

Configuration details• A firewall exists between client and server tiers.• The firewall uses NAT (Network Address Translation).• Only the ports required for the communication between the desktop client

and the server tier are open on the firewall.• BusinessObjects servers are distributed over two machines.

Solaris 10Installation platform for BusinessObjects Enterprise

Oracle 10g R2 (10.2)Database for Central Management Server (CMS)


Deployment Scenarios12 Overview of deployment scenarios

Not relevantWeb application server

Linux iptablesFirewall

Desktop client to server diagram

The following diagram illustrates the system overview for the scenario onceit is implemented.

Summary of required tasks

The desktop client to server deployment scenario involves the following tasksin the order listed below.

1. Setting up the data tier.2. Setting up the server tier.3. Setting up the client tier.4. Setting up the firewall.


12Deployment ScenariosDesktop client to server scenario

Deploying the client to server scenario

To set up the data tier

The following steps require that you have already installed a version of SunSolaris 10 that meets the installation requirements for Oracle 10g R2.Advanced administrative knowledge of Oracle Database and Sun Solaris 10products is assumed.

This database will be used to hold CMS data. Additional database will becreated for auditing or performance management if required.

If your CMS and database servers are installed on separate computers,ensure that you have a working network connection between the machines.

Note: In addition to databases for CMS, auditing, or performancemanagement, you also require access to your existing corporate reportingdatabase. This is the database that hosts your organization's data, againstwhich BusinessObjects Enterprise applications run.

1. Install Oracle 10g R2.Make note of the following settings you use during the installation. Youwill need these settings when you come to install BusinessObjectsEnterprise servers and clients.

ExampleSetting

DBSERVER1_oraName of database server

systemAdministrator account name

passwordAdministrator account password

UTF-8Database character set encoding

An Oracle database is now installed and ready to be used byBusinessObjects Enterprise.

2. Create or import a new tablespace for the CMS, as well as auditing orPerformance Management databases if required.Record the settings used for creating of the CMS database.


Deployment Scenarios12 Desktop client to server scenario

ExampleCMS database setting

mycompanyCMS tablespace name

mycompanyuserUsername for CMS ta-blespace access

mypasswordPassword for CMS ta-blespace access

create table, create session, create procedureSystem privileges for useraccess

A CMS tablespace is now available for use.

3. Create or import a new tablespace for the auditing database, if required.Record the settings used for creating of the auditing tablespace.

ExampleAuditing database setting

bobjauditAuditing tablespace name

audituserUsername for auditing tablespaceaccess

auditpasswordPassword for auditing tablespaceaccess

create table, create session, createprocedure

System privileges for user access

An auditing database is now available for use.

4. Create or import a new tablespace for the Performance Managementtablespace, if required.Record the settings used for creating of the Performance Managementtablespace.

ExamplePerformance Managementdatabase setting

bobjpmPerformance Managementdatabase name

pmuserUsername for PM database ac-cess



ExamplePerformance Managementdatabase setting

pmpasswordPassword for PM database ac-cess

create table, create session, create proce-dure

System privileges for user ac-cess

A Performance Management tablespace is now available for use.

5. Create a network-shared directory on the database server's local filesystem to contain shared files for the file repository server (FRS).

Note: The network permissions for FRS directory must included read,write, and execute permissions for the networked users.

6. Extract the FRS template file (e.g. FileStore_02-22-2008.zip) withinthe FRS directory you created in the last step.

You have set up CMS, auditing, and performance management databases,as required. You have also installed a file repository server network-shareddirectory. The default listener port number used by Oracle is 1521. Thedatabase port number must be entered during the BusinessObjects Enterpriseinstallation.

Verify the connectivity between your CMS and database machines byattempting to connect to your database(s) from the CMS server(s).

Note: This scenario includes a network firewall between the CMS anddatabase servers. Ensure that this firewall is configured appropriately.

Remember: The ability to connect to your database server from your CMSserver may require a change to the Solaris firewall settings on both machines.

To set up the server tier

You need to install and setup Solaris 10 on the two machines that will hostthe BusinessObjects Enterprise server components. Designate a machineas SERVER 1 on which you will install framework servers. Designate secondmachine, SERVER 2, on which you will install a second set of servercomponents.1. Mount the device that contains the installation files.2. Type ./install.sh in the command line and press Enter.



The installation setup program is launched.

3. Select a language for the installation and press Enter.The software license agreement is displayed.

4. Type y to agree to the terms.5. Enter your BusinessObjects Enterprise product activation keycode in the

Business Objects Enterprise Product Keycode field and press Enter.6. Specify the installation directory for your BusinessObjects Enterprise

installation.7. Select the language pack you want to install and press Enter.


8. Select user and press Enter.The "Installation Type" screen is displayed.

9. Select Custom from the list of options on the Installation Type screenand press Enter.The "Features" screen is displayed.

10. Deselect the following top level features by typing X in all thecorresponding markers.

Items to deselect

Client Components

Server Components

Ensure that the deselected features appear as [ ] before continuing.

11. Expand Server Components and select the following:

Items to select

Central Management Server

Event Server

Input File Repository Server

Output File Repository Server

a. Under Central Management Server deselect the following:



Items to deselect

Auditor

MySQL

b. Press Enter.You are prompted if this is the first CMS cluster in your deployment

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

13. Press Enter to accept the default values in the Enter the informationfor your new CMS and leave the password fields blank.You are prompted to select a system database option.

14. Select Oracle and press Enter.A screen is displayed to provide configuration details for the oracledatabase server.

15. Type the following details and press Enter.

Type the followingField

DBSERVER1_oraOracle TNSNAME

mycompanyuserUser ID

mypasswordPassword

A new screen prompts you about reinitializing the database.

16. Select Yes.The "Enter Server Intelligence Agent information screen" is displayed.

17. Type SIA_1 in Server Intelligence Agent Node and press Enter.the "Select Web Application Server" screen is displayed.

18. Select the Install Tomcat, deploy web applications and press Enter.The "Please enter port numbers for the Tomcat installation screen" isdisplayed.

19. Press Enter to accept the default values.A screen is displayed with your specified installation directory.



20. Press Enter to start the installation.The installation program validates your system before installingBusinessObjects Enterprise in the specified directory.

To add servers to the server tierYou need to install the framework servers on SERVER 1 before you can addany servers to the server tier.

Use the following instructions to add BusinessObjects Enterprise servers tothe CMS cluster you have installed on SERVER 1.1. Mount the device that contains the installation files .2. Type ./install.sh in the command line and press Enter.


3. Select a language for the installation and press Enter .The software license agreement is displayed.






9. Choose Custom or Expand. in the "Installation Type" screen.10. Deselect all the following top-level features by typing X in all the

corresponding markers:

Items to deselect

Client Components

Web Tier Components

Note: Ensure that the markers appear as [ ] before continuing.

11. Expand Server Components and deselect the following items:



Items to deselect


Event Server




12. Press Enter to submit your custom installation sections.You are prompted to enter the name and port number of an existing CMS.

13. Type Server1 in CMS Hostname; leave Port and Existing CMSAdministrator Password blank. Press EnterThe "Enter Server Intelligence Agent information" screen is displayed.

14. Type SIA_2 in Choose a name for the Server Intelligence Agent Nodeand Press Enter.A screen is displayed with your specified installation directory.


To assign static port values to serversAccess the Central Management Console (CMC) on the machine namedSERVER1. Use the machine you designated to run the client tier, and opena browser and type in the following URL: http://SERVER1:8080/CmcApp/App/.

You need to assign static port values to the following servers:

Server name

SIA_1.CentralManagementServer

SIA_1.InputFileRepository

SAI_1.OutputFileRepository

1. Type the following configuration information and click Log On.



Required configuration informationField

SERVER1System

AdministratorUser Name

BOBJ_adminPassword

EnterpriseAuthentication Type

The CMC Home page is displayed.

2. Click Servers under the "Organize" column.A list of all available servers is displayed in a new screen.

3. Double-click the SIA_1.CentralManagementServer entry.The SIA_1.CentralManagementServer properties are displayed.

4. Deselect Auto assign and type 6402 in Request Port under "CommonSettings".

5. Click Save & Close.The list of available servers is displayed again.

6. Repeat steps 3-5 for the following servers:

Port number to specifyServer name

6404SIA_1.InputFileRepository

6406SIA_1.OutputFileRepository

You will need to pass the port numbers - 6402, 6404, and 6406 - whenconfiguring the firewall.

To configure the firewall

The iptables firewall is running on a supported Red Hat Linux operatingsystem with two network interface cards (NIC). One network card (interfaceeth0) is connected to an internal secure network, the other (interface eth1)is connected to an external unsecured network, such as the internet.

Note: Advanced administrative knowledge of Red Hat Linux products isrequired for these steps.



The following steps illustrate how to forward requests from clients on anunsecured external (interface eth1) network to the server tier running on asecure, firewalled network (interface eth0).

1. Log in to your Red Hat Linux server.

Note: As iptables is configured from the command-line, you need rootprivileges. This can be achieved with the su or sudo commands, bybecoming a member of the admin group, or by logging in as the rootuser.

2. Determine the network IP address, interface, and media access card(MAC) information for each NIC in your system.

Tip: The command ifconfig -a will display network interfaceinformation.

Record the network information in a safe place.

3. Add exceptions to the iptables firewall rules that forward incoming clientrequests to the server tier on the appropriate ports.

For example, the sever named CMS Server uses two port numbers tocommunicate with clients. You must forward both ports on the firewall'sexternal NIC to the CMS server connected to the internal NIC.

Note: This must be done for each port used by every server you wantaccessible from outside your network. Typical servers used by externalclients include the CMS, Desktop Intelligence, and the Connection Server.

In this scenario, four ports must be forwarded to the server tier fromexternal clients on the external network (eth1):• CMS Name Server port: 6400.• CMS Request port: 6402.• Input File Repository Server (FRS) port: 6404.• Output FRS port 6406.

Tip: To determine which ports are used by servers, open the CentralManagement Console (CMC) and go to Servers > Central ManagementServer > your server and note the number for Request Port and NameServer Port.

Clients on an unsecured network outside the firewall can now access theserver tier through the firewall.



To set up the client tier

Windows Server 2003 SP2 Enterprise Edition has to be installed and runningon the machine on which you will install Desktop Intelligence.

Follow the steps below to Desktop Intelligence and

1. Run setup.exe from the root directory of your product distribution.2. Click Install to launch the installation setup program.

"Please Choose Setup Language" is displayed.

3. Select the language for the installation setup from the pull-down listprovided and click OK.



The "Welcome to the BusinessObjects Enterprise XI 3.0 InstallationWizard" is displayed after you specify a language for the installation setup.

4. Click Next to proceed with the installation setup.The "License Agreement" screen is displayed.



5. Select I accept the License Agreement and click Next.The "Choose Language Packs" screen is displayed.

6. Select the language packs and click Next.The "Directory Selection" screen is displayed.



7. Accept the default directory by clicking "Next".The "Select Features" screen is displayed.

8. Left-click on the icon beside Client Components and select Entirefeature will be unavailable.

The Client Components icon changes to

9. Expand Client Components and left- click on Desktop Intelligence.



10. Select Entire feature will be installed on local hard drive and clickNext.The "Start Installation" screen is displayed.

11. Click Next to start the installation.The installation process begins and is completed once "BusinessObjectsEnterprise XI 3.0 Client Tool has been successfully installed" is displayed.



12. Click Finish.The Desktop Intelligence is now installed on your machine.

13. Go to Programs > BusinessObjects XI 3.0 > BusinessObjectsEnterprise Client Tools > Desktop IntelligenceThe "User Identification" dialog is displayed.

14. Provide the following information:a. Type SERVER1 for System.b. Type Administrator for User Name.c. Type password for Password.



The "New Report Wizard" is displayed.

15. Select Generate a standard report and click Begin.



Basic N-tier scenario

N-tier scenario overview

This section describes how to setup a scenario in which a web browseraccesses BusinessObjects Enterprise system through web applications.

System layers

• Data Tier: One machine used to host the database server.• Server Tier: Three machines hosting the framework, processing and

performance management (PMC) servers.• Web Tier: One machine in hosting the web application server.• Client Tier: One machine running the Live Office application.

Configuration details

Solaris 10Installation platform for BusinessObjects Enterprise

MySQLDatabase for Central Management Server (CMS)

Tomcat 5.5Web application server

Linux iptablesFirewall

Basic n-tier diagram

The following diagram illustrates the system overview for the scenario onceit is implemented.


Deployment Scenarios12 Basic N-tier scenario

Summary of required tasks

The basic n-tier deployment scenario involves the following tasks in the orderlisted below.

1. Setting up the data tier2. Setting up the server tier3. Setting up the web tier4. Setting up the firewall5. Setting up the client tier

Deploying the basic N-tier scenario

To set up the data tier

The following steps require that you have already installed a version of SunSolaris 10 that meets the installation requirements for MySQL. Advancedadministrative knowledge of MySQL and Sun Solaris 10 products is assumed.


12Deployment ScenariosBasic N-tier scenario

This database will be used to hold CMS data. Additional database will becreated for auditing or performance management if required.

If your CMS and database servers are installed on separate computers,ensure that you have a working network connection between the machines.

Note: In addition to databases for CMS, auditing, or performancemanagement, you also require access to your existing corporate reportingdatabase. This is the database that hosts your organization's data, againstwhich BusinessObjects Enterprise applications run.

1. Install MySQL.Make note of the following settings you use during the installation. Youwill need these settings when you come to install BusinessObjectsEnterprise servers and clients.

ExampleSetting

DBSERVER1_mysqlName of database server

systemAdministrator account name

passwordAdministrator account password

UTF-8Database character set encoding

A database is now installed and ready to be used by BusinessObjectsEnterprise.

2. Create or import a new tablespace for the CMS, as well as auditing orPerformance Management databases if required.Record the settings used for creating of the CMS database.

ExampleCMS database setting

mycompanyCMS tablespace name

mycompanyuserUsername for CMS tablespace access

mypasswordPassword for CMS tablespace access

A CMS tablespace is now available for use.

3. Create or import a new tablespace for the auditing database, if required.Record the settings used for creating of the auditing tablespace.



ExampleAuditing database setting

bobjauditAuditing tablespace name

audituserUsername for auditing tablespace access

auditpasswordPassword for auditing tablespace access

An auditing database is now available for use.

4. Create or import a new tablespace for the Performance Managementtablespace, if required.Record the settings used for creating of the Performance Managementtablespace.

ExamplePerformance Management database setting

bobjpmPerformance Management database name

pmuserUsername for PM database access

pmpasswordPassword for PM database access

A Performance Management tablespace is now available for use.

5. Create a network-shared directory on the database server's local filesystem to contain shared files for the file repository server (FRS).

Note: The network permissions for FRS directory must included read,write, and execute permissions for the networked users.

6. Extract the FRS template file (e.g. FileStore_02-22-2008.zip) withinthe FRS directory you created in the last step.

You have set up CMS, auditing, and performance management databases,as required. You have also installed a file repository server network-shareddirectory. The default listener port number used by MySQL is 3306. Thedatabase port number must be entered during the BusinessObjects Enterpriseinstallation.

Verify the connectivity between your CMS and database machines byattempting to connect to your database(s) from the CMS server(s).

Note: This scenario includes a network firewall between the CMS anddatabase servers. Ensure that this firewall is configured appropriately.



Remember: The ability to connect to your database server from your CMSserver may require a change to the firewall settings on both machines.

To set up the server tier - framework servers

Sun Solaris 10 has to be installed and running on the three machines runningthe server tier. Designate the machines SERVER1, SERVER2, and SERVER3. For information on installing and configuring Solaris 10, consult yourSolaris 10 documentation.

Use the following instructions to create BusinessObjects Enterprise yourCMS cluster on SERVER 1.1. Mount the device that contains the installation files.2. Type ./install.sh in the command line and press Enter.


3. Select a language for the installation and press Enter .The software license agreement is displayed.


BusinessObjects Enterprise Product Keycode field and press Enter.6. Specify the installation directory for your BusinessObjects Enterprise




9. Choose Custom or Expand. in the "Installation Type" screen.The "Features" screen is displayed.

10. Deselect the following top-level features by typing X in the correspondingmarkers:

Items to deselect

Client Components

Web Tier Components



Items to deselect

Server Components


11. Expand Server Components and select the following servers:

Items to select


Event Server



12. Expand Central Management Server and deselect MySQL and Auditor.13. Press Enter to submit your custom installation selections.

You are prompted in a new screen to specify if this is your first CMS inyour deployment.

14. Select Yes - this is the first CMS in this deployment.You are prompted to provide information on the CMS you are about toinstall.

15. Press Enter to accept the default CMS settings.You are prompted to select a database type for the CMS.

16. Select MySQL.The MySQL configuration screen is displayed.

17. Type the following information for the MySQL database and press Enterto submit the database configuration details.

Enter the followingField

DBSERVER1_mysqlHost Name

systemUser ID for CMS database



Enter the followingField

passwordPassword for CMS database

3306MySQL port number

mycompanyDatabase name for CMS

A new screen prompts you about reinitializing the database.

18. Select Yes press Enter.The "Enter Server Intelligence Agent Information screen" is displayed.



To add processing servers to the server tierYou need to install the framework servers on SERVER 1 before you can addany servers to the server tier.

Use the following instructions to add BusinessObjects Enterprise servers tothe CMS cluster you have installed on SERVER 1.1. Mount the device that contains the installation files.2. Type ./install.sh in the command line and press Enter.










9. Choose Custom or Expand in the "Installation Type" screen.The "Features" screen is displayed.

10. Deselect all the following top-level features by typing X in all thecorresponding markers:

Items to deselect

Client Components

Web Tier Components


11. Expand Server Components and deselect the following items:

Items to deselect


Event Server



Dashboard and Analytics Servers

Note: Ensure that the markers appear as [ ] before continuing. Scrolldown the "Features" screen to access Dashboard and AnalyticsServers.


13. Type SERVER1 in CMS Hostname; leave Port and Existing CMSAdministrator Password blank. Press Enter.The "Enter Server Intelligence Agent information" screen is displayed.

14. Type SIA_2 in Choose a name for the Server Intelligence Agent Nodeand Press Enter.



A screen is displayed with your specified installation directory.

15. Press Enter to start the installation.The installation program validates your system before installingBusinessObjects Enterprise servers in the specified directory.

To add performance management servers to the server tierYou need to install the framework servers on SERVER 1 before you can addany servers to the server tier.

Use the following instructions to add BusinessObjects Enterprise servers tothe CMS cluster you have installed on SERVER 1.1. Mount the device that contains the installation files.2. Type ./install.sh in the command line and press Enter.








9. Choose Custom or Expand in the "Installation Type" screen.The "Features" screen is displayed.

10. Deselect all the following top-level features by typing X in all thecorresponding markers:

Items to deselect

Client Components

Web Tier Components

Server Components




11. Expand Server Components and select Dashboard and AnalyticsServers.

Note: Scroll down the "Features" screen to access Dashboard andAnalytics Servers.


13. Type SERVER1 in CMS Hostname; leave Port and Existing CMSAdministrator Password blank. Press EnterThe "Enter Server Intelligence Agent information" screen is displayed.


15. Press Enter to start the installation.The installation program validates your system before installingBusinessObjects Enterprise servers in the specified directory.

To set up the web tier

Sun Solaris 10 has to be installed and running on the machine that will hostthe web tier.

Follow the procedure to install Tomcat 5.5 and deploy the BusinessObjectsEnterprise web applications.1. Mount the device that contains the installation files.2. Type ./install.sh in the command line and press Enter.





installation.



7. Select the language pack you want to install and press Enter.You are prompted to select either a user or system installation.


9. Select Install Web Tier features in the "Installation Type" screen.The "Features" screen is displayed.

10. Press Enter to accept the default settings.You are prompted to specify an existing CMS for the web tier features.

11. Type SERVER1 in the CMS Hostname and press Enter to accept defaultvalues for the other settings.You are prompted to select what kind of Java application server to install.

12. Select Install Tomcat, deploy web applications.The Tomcat configuration screen is displayed.

13. Press Enter to accept default port numbers for the Tomcat server.A screen is displayed with your specified installation directory.

14. Press Enter to start the installation.The installation program validates your system before starting theinstallation.

You need provide the default port settings for the Tomcat Server to setupthe firewall.

To configure the firewall

The iptables firewall is running on a supported Red Hat Linux operatingsystem with two network interface cards (NIC). One network card (interfaceeth0) is connected to an internal secure network, the other (interface eth1)is connected to an external unsecured network, such as the internet.

Note: Advanced administrative knowledge of Red Hat Linux products isrequired for these steps.

The following steps illustrate how to forward requests from clients on anunsecured external (interface eth1) network to port 8080 on for a OracleApplication Server 10g R3 web application server running on a secure,firewalled network (interface eth0).



1. Log in to your Red Hat Linux server.

Note: As iptables is configured from the command-line, you need rootprivileges. This can be achieved with the su or sudo commands, bybecoming a member of the admin group, or by logging in as the rootuser.

2. Determine the network IP address, interface, and media access card(MAC) information for each NIC in your system.

Tip: The command ifconfig -a will display network interfaceinformation.

Record the network information in a safe place.

3. Add an exception to the iptables firewall rules that forwards incomingclient requests on port 8080 to port 8080 on the web application server.

Clients on an unsecured network outside the firewall can now access theweb application server through the firewall on port 8080.

To set up the client tier

You need to install Microsoft Office 2003 on the machine on which you runthe client tier.

1. Insert the BusinessObjects Live Office XI 3.0 CD into your computerCD-ROM drive.

2. Choose your preferred language for the installation setup from the list onthe left and click Install.The Live Office Installation Wizard is displayed.

3. Follow the on-screen instructions in the Live Office Installation Wizard tocomplete the installation procedure.

4. Click Start > Programs > Microsoft Office, and select Microsoft Excel,Word, or PowerPoint to launch the application.

5. Click LiveOffice > Options > Enterprise.6. When the Options dialog box appears, enter your BusinessObjects

Enterprise credential in the following fields:• User name

• Password



7. Enter http://WEBSERVER1:8080/dswsbobje/services/session in the WebService URL and System fields.

8. Select the Enterprise authentication method from the drop-down list,click Log On and then click OK.



Get More Help

A

Online documentation library

Business Objects offers a full documentation set covering all products andtheir deployment. The online documentation library has the most up-to-dateversion of the Business Objects product documentation. You can browsethe library contents, do full-text searches, read guides on line, and downloadPDF versions. The library is updated regularly with new content as it becomesavailable.

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

Additional developer resources

http://devlibrary.businessobjects.com

Online customer support

The Business Objects Customer Support web site contains information aboutCustomer Support programs and services. It also has links to a wide rangeof technical information including knowledgebase articles, downloads, andsupport forums.

http://www.businessobjects.com/support/

Looking for the best deployment solution for your company?

Business Objects consultants can accompany you from the initial analysisstage to the delivery of your deployment project. Expertise is available inrelational and multidimensional databases, in connectivities, database designtools, customized embedding technology, and more.

For more information, contact your local sales office, or contact us at:

http://www.businessobjects.com/services/consulting/

Looking for training options?

From traditional classroom learning to targeted e-learning seminars, we canoffer a training package to suit your learning needs and preferred learningstyle. Find more information on the Business Objects Education web site:

http://www.businessobjects.com/services/training


Get More HelpA

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

http://devlibrary.businessobjects.com


http://www.businessobjects.com/services/consulting/

http://www.businessobjects.com/services/training

Send us your feedback

Do you have a suggestion on how we can improve our documentation? Isthere something you particularly like or have found useful? Drop us a line,and we will do our best to ensure that your suggestion is included in the nextrelease of our documentation:

mailto:[email protected]

Note: If your issue concerns a Business Objects product and not thedocumentation, please contact our Customer Support experts. For informationabout Customer Support visit: http://www.businessobjects.com/support/.

Business Objects product information

For information about the full range of Business Objects products, visit:http://www.businessobjects.com.


AGet More Help

mailto:[email protected]


http://www.businessobjects.com


Get More HelpA

IndexAadding performance management 141AddOrRemovePrograms.sh 140automated startup on UNIX 73, 93, 103

Bbasic web tier scenario

configuration details 226diagram 226overview 226system layers 226

BobjEnterprise120 73, 93, 103BusinessObjects Enterprise

documentation 10new features 12uninstalling 140uninstalling from UNIX 140

Cccm.sh 126CD 54

copying to your machine 54running the install from 54

checklist for installation 52client tools, installing 28CMS database

on UNIX 43setting up on UNIX 32

copying the product distribution 54custom installation 26custom or expand installation 76

available features 76

Ddatabase

permissions 36preparing your existing 35

database server optionsMySQL 32tested database servers 30

database server preparations 35database setup 36database, CMS 32DB2 32, 43deployment

documentation 10JBoss 202Oracle Application Server 201SAP Application Server 203Tomcat 200Tomcat clusters 200verifying 156, 192WebLogic 196WebLogic clusters 197WebSphere 193WebSphere cluster 194WebSphere Community Edition 204

deployment optionsinstall Tomcat 67, 87, 98manual deployment 67, 87, 98select supported web application 67, 87,

98deployment scenarios

desktop client to server 208general overview 208

deployments, complexinstalling language packs 133


distributed installBusinessObjects Enterprise 76

distributed installation 76dswsbobje.war

WebLogic deployment 199

Eenabling servers, with ccm.sh 126environment

database 32, 43environment variables

DB2 39MySQL 38Oracle 38, 41Sybase 42

Ffirewall

iptables configuration 217firewalls 22

IImport Wizard 28install types 25

client tools 28custom installation 26

install.sh 53, 55installation

running scripted 107web application server 50, 149

installation checklist 52installation log file 146installation on UNIX

system vs user 59installation overview 16installation setup

accepting license agreement 57clustering servers 85

installation setup (continued)clustering to a CMS 87, 97CMS administrator password 63configuring existing database 64configuring existing server 68, 89, 99configuring MySQL installation 66configuring Tomcat 68, 88, 98enable servers 62entering product keycode 57install MySQL 63installation directory 57installing language packs 57mounting files 56selecting installation type 59selecting new 62selecting setup language 56selecting user or system 58selecting web application server option 67,

87, 98Server Intelligence Agent 67, 85specifying CMS clustering 82specifying CMS port 63starting the installation 72, 86, 92, 102use existing database 63

installation typeuser vs system 23web tier 96

installation types 27web tier 27

installing 28client tools 28on UNIX 53, 55

iptables 217

JJBoss

manual deployment 202


Index

Llanguage packs

definition 132English fallback 132fallback to English 132installation on UNIX 133installing 134locale 132locating 134manual deployment 133Product Locale 132selecting locale 132silent mode 135uninstalling 136

log fileinstallation 146

MMySQL 32

OOracle 32, 43Oracle Application Server

manual deployment 201

Pperformance management

adding to installation 141AddOrRemovePrograms.sh 141setup 127

post install deployments 126preparing for installation 52preparing your database server 35Publishing Wizard 28, 53

Rresponse file

parameter list 108

SSAP Application Server

manual deployment 203scripted installation

parameter list 108running 107

scripted installation on UNIX 106server

choosing location 25server communication

multiple NIC hosts 23set up 23

Server Intelligence Agentspecifying node name 67, 85specifying port 67, 85

serversassigning static ports 216

servers starting with ccm.sh 126servers, starting with ccm.sh 126side-by-side installation 29silent installation on UNIX 106, 117Sybase 32, 43system installation on UNIX 59, 73, 93, 103system requirements 16

TTesting MySQL database environment variables

38Tomcat

manual deployment 200specifying port numbers 68, 88, 98

Tomcat clustersmanual deployment 200


Index

UUnicode 32uninstalling

AddOrRemovePrograms.shrunning 140

procedure 140uninstalling from UNIX 140UNIX 20

character set translation 20creating login environment 21environment 20host name requirements 22network requirements 22required commands and utilities 20setting the locale 20setting up your system 20user vs system installation 23

UNIX permissions 17user installation on UNIX 59user rights

deploying web applications 18

WWAR file

verifying deployment 156, 192war files

configuring 182deploying to remote server 182

WAR filescontext roots 186deployment guidelines 187war services 185

wdeployfunctionality 150log file 155options 155prerequisites 149

wdeploy (continued)Tomcat 168with JBoss 179with Oracle 173with SAP Application Server 176with WebLogic 163with WebSphere 156

web application deploymenton remote machines 182

web application serverconfiguring existing server 68, 89, 99configuring Tomcat 68, 88, 98

Web application serverinitial installation 50, 149

web services 185web tier 27web tier installation

available features 97clustering to a CMS 87, 97selecting deployment option 67, 87, 98

WebLogicmanual deployment 196

WebLogic clustersmanual deployment 197

WebSphereJSF implementation 159, 194manual deployment 193

WebSphere clusterdeployment 194

WebSphere Community Editionmanual deployment 204

WindowsBusinessObjects Enterprise

client tools installation 28Import Wizard 28Publishing Wizard 28scripted 106silent installation 106


Index

xi3 bip install unix en

Documents