xi3 bip install windows en

BusinessObjects Enterprise XI 3.0Installation and Configuration Guidefor Windows

BusinessObjects Enterprise XI 3.0

Windows

© 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 ..........................................................................16Network requirements .........................................................................17User permissions for installing BusinessObjects Enterprise................18Installing on a non-system drive...........................................................20Setting up server communication.........................................................21

Installation Scenarios ................................................................................23New installation ...................................................................................23Custom and Expand installation ..........................................................24Web Tier installation ............................................................................25Client Tools installation ........................................................................26Silent installation .................................................................................28Side-by-side installation ......................................................................29Distributed deployment.........................................................................29

CMS Database requirements and preparation..........................................30Installing MySQL as the system database...........................................30To setup a database account for BusinessObjects Enterprise ............31

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 3

Setting up an empty database for the CMS.........................................31DB2 database setup requirements ......................................................32Oracle database setup requirements...................................................33Sybase database setup requirements..................................................34MySQL database setup requirements..................................................34Microsoft SQL Server database setup requirements ..........................35

Preparing your existing database server...................................................35To prepare your database....................................................................36

Before you deploy web applications..........................................................37

Beginning the Installation of BusinessObjects Enterprise 39Chapter 3

Installation checklist...................................................................................40Beginning your installation.........................................................................41

To accept the license agreement.........................................................41Entering user information and a product keycode................................42To install Language Packs ...................................................................43To select an installation type................................................................44

New Installation of BusinessObjects Enterprise 47Chapter 4

Performing a new installation.....................................................................48To perform a new BusinessObjects Enterprise installation..................48To enter information on your new CMS................................................50To specify Server Intelligence Agent information.................................51CMS database configuration................................................................52To select a web application server configuration option.......................56To start the installation..........................................................................62

Custom or Expand Installations 63Chapter 5

Performing a Custom or Expand installation.............................................64To select or deselect features...............................................................64

4 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows

Contents

BusinessObjects Enterprise Client Components.................................65BusinessObjects Enterprise Web Tier Components............................67BusinessObjects Server Components.................................................67Database Access ................................................................................69Export Support.....................................................................................69Samples...............................................................................................70Help Files ............................................................................................70

To perform a custom or expand installation...............................................70To only install the Client Components..................................................71To only install the Server Components.................................................71To only install the Web Tier Components.............................................80

Web Applications Installation 89Chapter 6

Performing a Web Tier installation.............................................................90BusinessObjects Enterprise Web Tier Components............................90To perform a Web Tier installation........................................................91To select and deselect web tier components.......................................91To specify an existing CMS for web tier components...........................92To select a web application server configuration option.......................93To start the installation........................................................................100

Silent Installation 101Chapter 7

Overview of silent installation..................................................................102Specific ini file parameters for setup.exe ................................................103To create an installation .ini file................................................................103Sample .ini script file................................................................................104Silent and scripted installation parameters..............................................107

After Installing BusinessObjects Enterprise 115Chapter 8

Launching the Central Management Console (CMC)..............................116


Contents

To log on to the CMC..........................................................................116Troubleshooting CMC logon issues...................................................117

Register your installed product................................................................117Diagnostic Tool........................................................................................118

Deployment Diagnostic tool................................................................118To run diagnostic tests in Windows....................................................119Diagnostic options..............................................................................122

Language Packs on Windows 125Chapter 9

About language packs ............................................................................126English language fall-back ......................................................................126Product locale changes ..........................................................................126Selecting a language ..............................................................................126Installing language packs and complex deployments ............................127Installing language packs on Windows systems ....................................127Locating language packs ........................................................................128

To install language packs ..................................................................128Installing language packs across a BusinessObjects Enterprise deployment.................................................................................................................129To uninstall language packs ...................................................................131

Client Tools Installation 133Chapter 10

Overview of Client Tools installation........................................................134BusinessObjects Enterprise Client Components.....................................134To perform a client tools installation........................................................135Client Tools silent installations ................................................................142

Sample client tools ini file...................................................................143

Maintaining your Installation 145Chapter 11

BusinessObjects Enterprise maintenance operations.............................146


Contents

To enter maintenance mode...............................................................146Uninstalling BusinessObjects Enterprise from Windows.........................147

Silent uninstallation............................................................................148Software Inventory Tool...........................................................................148

Introduction.........................................................................................148How does the BusinessObjects Software Inventory Tool work?........149

The installation log file.............................................................................153

Post Installation Web Application Deployment 155Chapter 12

Overview of post install deployment........................................................156Before you deploy web applications........................................................157Deploying with wdeploy...........................................................................157

Prerequisites for using wdeploy.........................................................157Overview for using wdeploy...............................................................158How to use wdeploy...........................................................................159Options for using wdeploy..................................................................164After deploying web applications........................................................165Deploying to web application servers with wdeploy...........................165To deploy web applications on a remote machine.............................194

Manually deploying to a web application server......................................197BusinessObjects Enterprise WAR files..............................................197WAR file context roots........................................................................198Guidelines for deploying WAR files....................................................199To manually deploy web applications.................................................200To prepare for manual deployment on a remote machine..................201After deploying web applications........................................................204Deploying with the Administration console.........................................205

Deployment Scenarios 219Chapter 13

Overview of deployment scenarios..........................................................220


Contents

Desktop client to server scenario............................................................220Desktop client to server overview......................................................220Summary of required tasks................................................................221Deploying the desktop client to server scenario.................................222

Basic N-tier scenario................................................................................240N-tier scenario overview.....................................................................240Summary of required tasks................................................................241Deploying the N-tier scenario.............................................................241

Complex deployment scenario................................................................256Complex deployment overview..........................................................256Summary of required tasks................................................................257Deploying the complex deployment scenario.....................................258

Get More Help 281Appendix A

Index 285


Contents

Getting Started

1

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

In addition this documentation provides instructions for installing standaloneclient tools, language packs and for modifying, repairing or removingBusinessObjects Enterprise XI 3.0.

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

If you are installing BusinessObjects Enterprise XI 3.0 on UNIX or Linuxoperating systems, please read the BusinessObjects Enterprise XI 3.0Installation and Configuration Guide for UNIX.

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


Getting Started1 About this documentation

DescriptionGuide

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

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


1Getting StartedBusinessObjects Enterprise guides

DescriptionGuide

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

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


Getting Started1 What is BusinessObjects Enterprise?

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

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

DescriptionFeature

Web applications can now be deployed directly usingthe BusinessObjects Enterprise installer, or after instal-lation using either the wdeploy tool or the web applica-tion server's administration console. Procedures forseveral deployment scenarios are considered andthoroughly documented 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 tosupported web application servers using a dedicatedinstallation method.

Web-tier installation

You can now validate your deployments through theDeployment Diagnostic Tool.

Deployment Diagnos-tic Tool

BusinessObjects Enterprise client tools can now be in-stalled using the standalone Client Tools installer.

Stand-alone ClientTools installation

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/



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:

• Ensure that that your system meets the basic requirements for aBusinessObjects Enterprise XI 3.0 installation.

• Consult the BusinessObjects Enterprise XI 3.0 Deployment PlanningGuide.

• Consider how you should prepare your infrastructure and set up yourenvironment including server locations.

• Verify that all machines that will be part of your BusinessObjects Enterprisedeployment 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.• Choose an installation method.

The following sections list the core software and system requirements, thechoices available to you within the core requirements, and the install methodsavailable to you for installing BusinessObjects Enterprise XI 3.0.

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

Related Topics• Installation checklist on page 40• System requirements on page 16• Preparing your existing database server on page 35

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 your


Preparing to Install BusinessObjects Enterprise2 Installation overview

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

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

deployment, 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:

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

Network requirements

When installing BusinessObjects Enterprise on multiple machines, you mustensure that each target machine can communicate over TCP/IP with themachine running the Central Management Server (CMS). Also ensure thatthe target machines can communicate over TCP/IP with each other. Inparticular, your web server must be able to communicate with the machinethat is running the web application server. All web desktop clients must alsobe able to access the web server. For more information on the communicationbetween components please refer to the “Architecture” chapter in theBusinessObjects Enterprise Deployment Planning Guide.

Note: If you are installing BusinessObjects Enterprise in a firewallenvironment, you will require additional configuration details. See the“Working with Firewalls” chapter of the BusinessObjects EnterpriseAdministrator's Guide.


2Preparing to Install BusinessObjects EnterpriseInstallation overview

User permissions for installing BusinessObjectsEnterprise

To successfully install BusinessObjects Enterprise XI 3.0 on Windows, theuser running the setup program must have the permissions listed in the tablebelow:

Required permissionsCategory

Administrative privileges on the local machine.Operating Sys-tem

Access to all machines via TCP/IP - all specified ports mustbe available.

Network

Rights to add and drop tables to/from database, plus rightsto read, write, and edit table rows.

Database

It is recommended that you use the same user account forinstalling BusinessObjects Enterprise and your web applicationserver.

Web applicationserver

Note:

The following scenarios are not supported:

• Installing on a domain controller.

• Installing on a machine where the Windows default security settings givento the local Administrators group have been modified.

Minimum user rights for deploying web applications

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, create, and modify 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, create, and modify files in$as_dir\server\$as_instance\lib

• rights to read, create, and modify files in the$as_dir\server\$as_instance\deploy directory

JBoss

• rights to read, create, and modify files in$as_dir\opmn\conf

• rights to read and modify files in$as_dir\j2ee\home\

• rights to read and modify files in $as_dir\opmn\lib

Oracle

• rights to read, create, and modify files in$as_dir\$as_sid\$as_instance\j2ee\deploying

• rights to read and modify files in$as_dir\$as_sid\$as_instance\j2ee

SAP Web Application Server

• rights to read, create, and modify files in $as_dir\bin• rights to read, create, and modify files in

$as_dir\shared\lib• right to create and modify files under $ad_sir\we

bapps and its subdirectories• rights to create and modify files under $as_dir\conf

and its subdirectories• rights to call $as_dir\bin\tomcat55.exe• rights to modify service startup parameters in the

registry

Tomcat



Minimum required permissionsWeb application server

• 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 di-rectory)

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

• Right to read and execute $as_dir\bin\GenPluginCfg.bat

• Right to read $as_dir\bin\securityProcs.jacl• Right to read $as_dir\bin\LTPA_LDAPSecuri

tyProcs.jacl• Right to read and execute files under $as_dir\plu

gins• Right to read and execute files under $as_dir\java• Right to read and execute files under $as_dir\de

ploytool• Right to read, write, and execute files under

$as_dir\properties• Right to read, write, and execute files under

$as_dir\profiles

WebSphere

Installing on a non-system drive

You can install BusinessObjects Enterprise on any drive on your machine.The installation program targets the folder or directory that you specify.



There is one exception to this rule. If you previously installed anotherBusiness Objects product of the same version, the BusinessObjectsEnterprise XI 3.0 Setup program automatically uses the existing commondirectory to add any shared Business Objects product files. If this commondirectory is on the system drive - the drive containing your operating systemfiles - BusinessObjects Enterprise automatically installs its shared files there.

Note: If the previously installed product is the same version as the one youare about to install, maintenance mode is evoked.

To install several Business Objects products on a non-system drive, youmust first install BusinessObjects Enterprise. All Business Objects productsthat you subsequently install will use the same non-system drive for sharedfiles.

Setting up server communication

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

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

• Servers that run BusinessObjects Enterprise must have a fixed host name.You must have administrative privileges to set or modify a fixed host nameon your system. You can use fully qualified domain names to specify thelocation of the CMS.

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.

• If you are clustering multiple file repository servers on separate machines,ensure that each server has read and write permissions to the folder usedto store data.

Choosing a server location

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

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

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



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

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

Installation 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• Distributed Deployments

For an installation upgrade see the BusinessObjects Enterprise UpgradeGuide.

New installation

Performing a new installation is the easiest way to deploy BusinessObjectsEnterprise because all of the required client, server, and optional componentsare installed by default onto one machine.

Note: After the installation you can easily disable any components you donot require.

You may want to choose a new installation if:

• You have not installed BusinessObjects Enterprise before.• You want to install all the components on the same machine.• You do not have stringent disk space limitations.• You do not need to specify which particular components to install.


2Preparing to Install BusinessObjects EnterpriseInstallation Scenarios

Related Topics• Performing a new installation on page 48

Custom and Expand installation

The Custom or Expand installation scenario allows you to select whichcomponents to install. You may want to perform a custom installation whenyou want to exclude some components, or install only a limited set ofcomponents. It is recommended that you run this type of installation onlyafter you are familiar with specific BusinessObjects Enterprise componentsand their roles, otherwise you may inadvertently fail to install a requiredcomponent.

You may want to perform a Custom and Expand installation if you plan touse BusinessObjects Enterprise in a distributed environment. For example,in a distributed environment you can install the BusinessObjects EnterpriseDesktop Intelligence server components on one machine, and use anotherto host Crystal Reports server components.

After you install BusinessObjects Enterprise on one machine, you can runa Custom and Expand installation to add server components, create a CMScluster, increase available resources, and distribute the processing workload.

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

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

Tip: Consult the “Scaling Your System” section of the BusinessObjectsEnterprise Administrator's Guide for information on planning how to bestexpand your installation to meet the needs of your organization.

You may want to choose a Custom and Expand installation if:


Preparing to Install BusinessObjects Enterprise2 Installation Scenarios

• You are already familiar with the BusinessObjects Enterprise installationprogram.

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

• Your deployment of BusinessObjects Enterprise servers will be distributedover multiple computers.

• You want to add additional BusinessObjects Enterprise servers.• You know exactly what components you require.• You have resource limitations and need to consider disk space constraints.• You want to improve system performance.• You require fault tolerance.• If you wish to install the web or client components separately from the

server components.

Related Topics• Performing a Custom or Expand installation on page 64

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.

Related Topics• Performing a Web Tier installation on page 90

Client Tools installation

You can install the BusinessObjects Client Tools by either using a distributedstandalone installer or the Custom or Expand installation. The available clienttools are listed below:

Short descriptionComponent

An integrated query, reporting and analysis so-lution for business professionals that allows youto access data in your corporate databases di-rectly from your desktop and present and ana-lyze this information in a Desktop Intelligencedocument.

Desktop Intelligence

Provides business users an easy to use interac-tive and flexible user interface for building andanalyzing reports on corporate data over theweb, on secured intranets and extranets.

Web Intelligence Rich Client

Allows you to migrate reports that are based onCrystal queries, dictionaries, and InfoViews toa BusinessObjects Enterprise deployment.

Data Source Migration Wizard

Enables you to design relational views of infor-mation that provides a wide range of capabilitiesfor creating and modifying Data Connections,Dynamic Data Connections, Data Foundations,Business Elements, and Business Views.

Business View Manager

Converts Desktop Intelligence XI R2 reports toWeb Intelligence XI R2 format and publishesthe converted reports to the CMS. The level ofconversion depends on the features in theoriginal report.

Report Conversion Tool




Allows you to import and export content fromprevious and current versions of BusinessOb-jects Enterprise.

Import Wizard

Enables users to add reports to BusinessOb-jects Enterprise

Publishing Wizard

Allows you create custom web services forspecific queries using Business Objects WebServices.

Query as a Web Service

Allows you to create universes for Web Intelli-gence and Desktop Intelligence users.

Universe Designer

Contains the following subfeatures:

BusinessObjects Enterprise Java SDK: allowsyou to build web applications that interfacedirectly with your BusinessObjects Enterprisesystem.

BusinessObjects Enterprise Web ServicesSDK: implementation of web services thatcan be deployed with BusinessObjects Enter-prise.

Developer Components

An application that defines the multilingualdocument and performs translation of docu-ments and prompts. It supports Universe De-signer universes and Web Intelligence docu-ments.

Translation Manager

Note: The client applications must 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.



If you install the BusinessObjects Enterprise servers on a UNIX machine,you can connect remotely to BusinessObjects Enterprise with the client tools.However, the client applications must be installed on Windows.

Note: The BusinessObjects Enterprise Client Tool Setup program does notgenerally require a license key to activate the product. However, DesktopIntelligence does require that a license key be entered in the CMC after theinstallation.

Related Topics• To perform a client tools installation on page 135

Silent installation

You can run a silent installation to install BusinessObjects Enterprise fromthe command line using a response file containing installation setupparameters. 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

You can perform a New, Custom and Expand, or Web Tier installation onmachines containing the following:

• BusinessObjects Enterprise XI• BusinessObjects Enterprise XI Release 2

This scenario is called a side-by-side installation in which bothBusinessObjects Enterprise versions can run simultaneously.

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

For more information on migrating content and working with side-by-sideinstallations see the BusinessObjects Enterprise XI 3.0 Upgrade Guide.

Distributed deployment

Once BusinessObjects Enterprise XI 3.0 is installed and running on onemachine, you can add server components, create a CMS cluster, increaseavailable resources, and distribute the processing workload.

For example, if you plan to use BusinessObjects Enterprise with an existingweb application server that resides on a different machine than whereBusinessObjects Enterprise is currently installed, you will need to install theclient and server components separately from the web tier components. Thistype of installation allows you to integrate BusinessObjects Enterprise withyour existing web application server—without installing the coreBusinessObjects Enterprise components on the web application server itself.



This type of distributed installation also allows you to scale your deploymentof BusinessObjects Enterprise by installing additional servers to meet thedemands of your enterprise. How you choose to expand your system dependslargely upon your current configuration and your reporting requirements.

A distributed deployment installation is accomplished by selecting the Customand Expand installation and choosing the components you wish to install oneach machine.

Before you create a distributed deployment it is strongly recommended thatyou consult the BusinessObjects Enterprise Planning and Deployment Guidefor general scalability considerations, for sample configurations, and forinformation about CMS clustering.

CMS Database requirements andpreparation

BusinessObjects Enterprise requires a database to store information aboutthe system and its users. The following sections detail required settings andhow to test settings for:

• DB2• MySQL• Microsoft SQL• Oracle• SybaseBefore installing BusinessObjects Enterprise you should review thisinformation in order to properly prepare your CMS system and auditingdatabase. For more information on database requirements, refer to the“Databases in BusinessObjects Enterprise” section in the BusinessObjectsEnterprise Deployment Planning Guide.

Note: Regardless of database type, your database must be setup to useUnicode character encoding, such as UTF-8.

Installing MySQL as the system database

MySQL database server is an open-source database that provides local datastorage. The BusinessObjects Enterprise XI 3.0 Setup program can install


Preparing to Install BusinessObjects Enterprise2 CMS Database requirements and preparation

and configure MySQL as the database server for a BusinessObjectsEnterprise installation. If you already have MySQL installed, the installationprogram is used to configure the CMS database using your existing databaseengine. During the installation of BusinessObjects Enterprise, you specifywhat database server you will use and enter the required parameters forauthentication.

To setup a database account for BusinessObjectsEnterprise

To administer the CMS database, you need to set up a database account.If you choose to install MySQL as part of your BusinessObjects Enterpriseinstallation, you will be prompted during installation to set up this account. Ifyou plan to use your own database, you should complete the steps listedbelow before installing BusinessObjects Enterprise.1. Create or select a user account that provides BusinessObjects Enterprise

with the appropriate privileges to your database server.2. Verify that you can log on to your database and carry out administrative

tasks using this account.

Setting up an empty database for the CMS

If you want to use an existing database server, you must create a newdatabase on your database server before you installing BusinessObjectsEnterprise.

The following database servers are supported for the CMS system and auditdatabases:

• Oracle• DB2• Sybase• MySQL• Microsoft SQL Server (ODBC)

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


2Preparing to Install BusinessObjects EnterpriseCMS Database requirements and preparation


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

• Create a new database

• Create a new user account and password for the database - to be usedby BusinessObjects Enterprise

• Specify that the new user account has required permissions to create,modify, and delete tables and create procedures so that database canbe modified as required.

• Record the name of the database, the user account, and the passwordwhen you run the BusinessObjects Enterprise installation setup program

During the installation setup, you can choose to reinitialize the existingdatabase. This will cause new tables to be created in your existing databaseto store BusinessObjects Enterprise data. Consult your specific databaseserver documentation if you are unsure of the procedure for creating a newdatabase. Ensure that your database server is set up to use Unicodecharacter encoding (such as UTF-8).

Note: If you have a previous release of BusinessObjects Enterprise youcannot use your database from a previous release for BusinessObjectsEnterprise XI Release 3. 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.

Related Topics• DB2 database setup requirements on page 32• Oracle database setup requirements on page 33• Sybase database setup requirements on page 34• Microsoft SQL Server database setup requirements on page 35• MySQL database setup requirements on page 34

DB2 database setup requirements

If you are using a DB2 database with your BusinessObjects Enterprisedeployment, there are specific settings you need to select when the database



is created. It is not sufficient to modify these settings after the database hasbeen created.

When you create the database you will use with BusinessObjects Enterprise:

• Ensure the CMS database is not partitioned.

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

Note: The requirement above does not apply to the Audit database. Youcan use a partitioned DB2 database for the Audit database.

• Create the database with the following 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 (CMC). Replace XXwith the code that is appropriateto your 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 through version 9.1do not have this requirement. SQL stored procedures are used inBusinessObjects Enterprise when users are added to groups in the CMS.Please consult the DB2 documentation for details on how to configure theC compiler for SQL stored procedures, and for determining what version ofthe C compiler is supported on your platform.

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

Related Topics• To prepare your database on page 36

Oracle database setup requirements

For an Oracle database there are no specific parameters, other than thesetting of UTF-8, that are crucial for BusinessObjects Enterprise to work.


2Preparing to Install BusinessObjects EnterpriseCMS Database requirements and preparation



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 forthe CMS system database. For the CMS to run optimally, the page size mustbe 8KB. The page size is set up during the database creation and it cannotbe changed after the database is set up.



MySQL database setup requirements

For an existing MySQL database there are no specific parameters that arecrucial for BusinessObjects Enterprise to work, other than the setting ofUTF-8. If you select the option to install and configure MySQL that is suppliedwith your installation, the installation creates a MySQL database with thedefault settings for the CMS database and the Audit database.





Microsoft SQL Server database setup requirements

For an Microsoft SQL Server database there are no specific parameters,other than the setting of UTF-8 that are crucial for BusinessObjects Enterpriseto work.



Preparing your existing database serverAfter you have created your database, setup the database client, and beforeyou install BusinessObjects Enterprise, you need to prepare the databaseserver so the CMS can connect to it.

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.

The table below summarizes the information required for configuring yourexisting database during the installation setup.

Information required at install timeDatabase type

• Database: MySQL database name• Server: MySQL server name• Port: default port is 3306• Login credentials used to access

database

MySQL


2Preparing to Install BusinessObjects EnterprisePreparing your existing database server


• Server: Sybase Server Name• Login credentials used to access

database

Note: The Sybase server name is acombination of the host name and theport number which is set by yourdatabase administrator in the filesql.ini.

Sybase

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

databaseDB2

• Server: tnsnames connect identifier• Login credentials used to access

databaseOracle

• ODBC DSNMicrosoft SQL Server

To prepare your database

1. If you are using an existing database ensure the following are set upbefore you begin your installation:

Ensure that the following has beenconfiguredDatabase type

MySQL server nameMySQL

Sybase server nameSybase

DB2 aliasDB2

tnsname nameOracle

ODBC DSNMicrosoft SQL Server


Preparing to Install BusinessObjects Enterprise2 Preparing your existing database server

2. Create a new, empty database on your database server.

For information on how to create a new database, consult your databaseserver documentation or your database administrator.

3. Create a new user account and assign it a secure password.4. Ensure that the new account has permission to create, modify, delete

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

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

Related Topics• DB2 database setup requirements on page 32• Oracle database setup requirements on page 33• Sybase database setup requirements on page 34• Microsoft SQL Server database setup requirements on page 35• MySQL database setup requirements on page 34

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.


2Preparing to Install BusinessObjects EnterpriseBefore you deploy web applications

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 ensured that all machines running BusinessObjects Enterprisecomponents can communicate properly?

• Have you tested the database connection between the machine hostingyour CMS database and the machine on which the Central ManagementServer 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 are using your own database server and plan to use auditing, 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 onto the database with your logon ID and password?

• 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 going to install Tomcat, have you ensured that your existingweb application server has the required JDK installed?

• If using an existing web application server, has the server already beeninstalled and configured?

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


Beginning the Installation of BusinessObjects Enterprise3 Installation checklist

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

Beginning your installationThe following instructions lead you through the initial steps of setting up yourBusinessObjects Enterprise XI 3.0 installation on Windows. In this stage youwill do the following:

• Choose the language for the installation setup

• Agree to the license terms

• Enter the product key codes

• Select where to install BusinessObjects Enterprise

• Select which language packs to install

• Select an installation type

When you perform the following installation setup, all the componentsassociated with your product key are installed on the local machine. Defaultuser and group accounts are created, and sample reports are published tothe system.

To accept the license agreement

Use the "License Agreement" screen to review and accept the licenseagreement for BusinessObjects Enterprise XI 3.0. You must accept the


3Beginning the Installation of BusinessObjects EnterpriseBeginning your installation

agreement to continue with the installation setup.

1. Review the License Agreement.2. Select I accept the License Agreement and click Next.

The "User Information" screen is displayed.

Entering user information and a product keycode

Use the "User Information" screen to enter user information and provide akeycode for your BusinessObjects Enterprise XI 3.0 product.


Beginning the Installation of BusinessObjects Enterprise3 Beginning your installation

1. Provide your user credentials in the Full Name and Organization fields.This information personalizes your installation and is recorded in theregistry.

2. Enter a valid code in the Product Keycode field and click Next.The "Chose Language Packs" screen is displayed.

To install Language Packs

You can choose to install specific or all available language packs whenrunning the BusinessObjects Enterprise installation setup.

1. Select the Language Packs you want to install.The language packs currently available for installation include:• French• Japanese• German• Spanish• Italian



• Chinese Simplified• Chinese Traditional• Korean• Dutch• Swedish• Portuguese (Brazil)

Note: English is a required language and cannot be deselected. You canalso add language packs after installing BusinessObjects Enterprise.

2. Click Next.The "Install Type" screen is displayed.

Related Topics• Installing language packs on Windows systems on page 127

To select an installation type

The "Install Type" screen is used to select an installation method and tospecify an installation directory.



1. Select one of the following installation type options:• New

This option installs all the required BusinessObjects Enterprise serverand client components.

• Custom or Expand Install

This option enables experienced users to pick and choose whichBusinessObjects Enterprise client and server components to install.

• Web Tier

This option only installs the Web application server components.

2. Specify where to install the BusinessObjects Enterprise components inthe Destination Folder field.

If you have BusinessObjects products installed on your machine, theDestination Folder field is disabled and path to the existingBusinessObjects folder is displayed.

3. Click Next to continue with the installation setup.



Depending on your installation type selection, either the "ServerComponents Configuration" or "Select Features" screen is displayed.

Related Topics• Installing on a non-system drive on page 20• Distributed deployment on page 29• Performing a Web Tier installation on page 90• Performing a Custom or Expand installation on page 64• To perform a new BusinessObjects Enterprise installation on page 48



New Installation ofBusinessObjects Enterprise

4

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

The setup of a new installation of BusinessObjects Enterprise XI 3.0 requiresthe following inputs.

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

2. Configuring up the system database. You can choose to either install andconfigure MySQL or configure your existing database.

3. Providing information on the Server Intelligence Agent (SIA).

4. Configuring the Java application server. You can choose to either installand configure Tomcat or configure your existing Java application server.

Related Topics• To perform a new BusinessObjects Enterprise installation on page 48• Beginning your installation on page 41

To perform a new BusinessObjects Enterpriseinstallation

The "Install Type" screen is displayed once you complete the initial set upof the BusinessObjects Enterprise installation.


New Installation of BusinessObjects Enterprise4 Performing a new installation

1. Choose New in the "Install Type" screen.2. Select one of the following options:

• Install MySQLDatabase Server if you do not have a system databaseserver.

• Use an existing database server if you want to user your currentdatabase server.

Depending on your selection, you will configure the database server insubsequent screens.

3. Select the Enable servers upon installation box if you want toautomatically launch the BusinessObjects Enterprise once the installationprocess is finished.

4. Specify where to install the BusinessObjects Enterprise components inthe Destination Folder field.

5. Click Next to continue with the installation setup.The Server Components Configuration screen is displayed.

Related Topics• To select an installation type on page 44• Beginning your installation on page 41


4New Installation of BusinessObjects EnterprisePerforming a new installation

To enter information on your new CMS

The "Server Components Configuration" screen is used to specify the portnumber and an administrator password for the new Central ManagementServer (CMS). The Central Management Server's (CMS) role is tocommunicate with the other Enterprise servers and services and managethe system and audit databases.

1. Specify a port number in the CMS port field.The default CMS port number is 6400.The CMS will communicate with other BusinessObjects Enterprise serversthrough the specified port.

2. Specify a password for the CMS administrator account in the Passwordand Confirm password fields.

Tip: You can opt to skip this step - select the Configure theBusinessObjects Enterprise Administrator password at a later timebox.




The "Server Intelligence Agent" screen is displayed.

Note: If the port you specified in step 1 is unavailable, you will berequested to specify another port number.

To specify Server Intelligence Agent information

The Server Intelligence Agent (SIA) is automatically created during installationof BusinessObjects Enterprise XI 3.0. For more information on ServerIntelligence and the Server Intelligence Agent, refer to the BusinessObjectsEnterprise Administrator's Guide. The "Server Intelligence Agent" screen isused to name and designate a port address for the SIA for the currentinstallation.

1. Provide a name to identify the SIA node in the Node Name field.2. Specify a port number for the SIA in the Port field.

This port will be used by the SIA to communicate with the CentralManagement Server (CMS).




Once the SIA information is entered, the port number will be validatedbefore you can proceed to configure the CMS database for yourinstallation. A warning will display if the port you specified is not available.

Related Topics• To configure your MySQL database server on page 75• To configure an existing database server on page 76

CMS database configuration

To configure your MySQL database server

The "MySQL Database Server Configuration" screen appears if you choseto install MySQL as part of the BusinessObjects Enterprise installation.

1. Specify the port number for the MySQL database server in the MySQLPort Number field.The default port number is 3306. Use this number unless this port isunavailable.



2. Specify and confirm a password for the MySQL root user account in theMySQL root User Account pane.

3. Select the Enable remote root access box to activate remote root accessto the database server.

4. Specify and confirm a password for the MySQL BusinessObjects useraccount in the MySQL BusinessObjects User Account pane and clickNext.The "Select Web Application Server" screen is displayed.

Related Topics• To perform a new BusinessObjects Enterprise installation on page 48• To select a web application server configuration option on page 93

To configure an existing database server

The "CMS Database Information" screen appears if you chose to use anexisting database server as your CMS for the new BusinessObjects Enterpriseinstallation. Use this screen to configure the database server.

1. Select a database type from the Select existing CMS databasedrop-down list in the CMS Database pane.Depending on your database server selection, corresponding input fieldsare displayed in the CMS Database pane.

2. Provide all the required information for the database in the fields providedin the CMS Database pane.

The table below summarizes all the information required for each databasetype:


• Database: MySQL databasename

• Server: MySQL server name• Port: default port is 3306• Login credentials used to access

database

MySQL




• Server: Sybase Server Name• Login credentials used to access

database

Note: The Sybase server name is acombination of the host name andthe port number which is set by yourdatabase administrator in the filesql.ini.

Sybase

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

databaseDB2

• Server: tnsnames connect identifi-er

• Login credentials used to accessdatabase

Oracle

• ODBC DSNMicrosoft SQL Server

a. To provide an ODBC DSN for a Microsoft SQL Server, click theBrowse button in the CMS Database pane.



The "SQL Server Logon" screen is displayed.

b. Use the "SQL Server Logon" screen to select a data source, database,and to provide user credentials.

c. Click OK to submit your settings.The "SQL Server Logon" screen is closed and an ODBC DSN entryis displayed in the CMS Database pane.

If you do not want to specify an auditing database for your new installationskip to step 6.

3. Select the Auditing Database box to specify an auditing database foryour new installation.The input fields under the Auditing Database box are activated.

4. Select a database type from the Select existing Auditing databasedrop-down list in the Auditing Database pane.Depending on your database server selection, corresponding input fieldsare displayed in the Auditing Database pane.

5. Provide all the required information for the database in the fields providedin the Auditing Database pane.

6. Select the Reset existing database box to delete all current tables andentries in the existing database.



7. Click Next to continue with the installation setup.The "Select Web Application Server" screen is displayed. This screenonly displays if a connection is established with the database configurationyou provided.

Related Topics• To select a web application server configuration option on page 93

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, the Central Management Console or your custom applications.Use the "Select Web Application Server" screen to either install Tomcat asyour application server, or to work with your existing web application server.

To configure your web application server for BusinessObjects Enterpriseyou will need account information along with port information.



1. Select one of the following options:• Use a pre-installed Web Application Server• Install Tomcat application server

2. To use your current Web application server you can:• Specify your server from the drop-down list provided.

Tip: You can configure the server during the current installation setup.You will need to provide access information for this server in asubsequent screen.

Note: Select Other if your existing web application server is SAPApplication Server 7.0 or JBoss 4.04. If you select this option you willhave to manually deploy the web applications.

• Choose to manually configure your server at a later time

3. Click Next.Depending on your selection, you can now proceed to either configureyour web application server, or start the installation process.

To configure your Tomcat application server

The "Configure Tomcat" screen displays during installation setup if youchoose to install Tomcat as the Web application server for yourBusinessObjects Enterprise installation. Use this screen to configure Tomcatand the Java SDK.



1. Accept the default values or specify new port numbers for Connectionport, Shutdown port, and Redirect port.


Note: If the port numbers you specified are in use, a warning messageis displayed. To continue you will have to specify unused and valid portnumbers.

The "Start Installation" screen is displayed.

To configure your existing Web application server

The "Configure Web Application Server" screen displays during installationsetup after you specify an existing server in the "Select Web ApplicationServer" screen. To properly install web components on your web applicationserver, you must provide specific configuration information about your existingweb application server.1. Specify the required configuration information for your existing web

application server.



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

Information required for installation setupWeb applicationserver

• Server Instance: Name of the current web appli-cation server instance (for example “localhost”).

• Service Name: Name of the Windows service ifthe application server will be installed as a win-dows service (for example “Tomcat5”).

• Application Server Installation Directory: Thedirectory where the web application server is in-stalled (for example C:\wdeploy\appserver\Tomcat5520).

Apache Tomcat 5.5

• Port: Administration port of the application server- mandatory for Weblogic (for example “7001”).

• Username: User name with administration rightsto the application server - mandatory for Weblogic.

• Password: Password for account with administra-tion rights to the application server - mandatoryfor Weblogic.

• Server Instance: Name of the current web appli-cation server instance (for example “ mserver1”).

• Application Server Installation Directory: Thedirectory where the web application server is in-stalled (for example C:\bea\weblogic10\user_projects\domains\base_domain).

Note: For WebLogic the directory is the domainroot.

WebLogic 10








• Application Server Installation Directory: Thedirectory where the web application server is in-stalled (for example C:\bea\user_projects\domains\base_domain).


WebLogic 9

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

• Username: User name with administration rightsto the WebSphere application server.

Note: If Admin is Secure is not selected you donot need to specify a username or a password.

• Password: Password for account with administra-tion rights to the application server.

• Server Instance: Name of the current web appli-cation server instance (for example “ server1”).

• Virtual Host: The virtual host to which the applica-tion must be bound.

• Admin is Secure: Select this option to enablesecurity requiring administrative access credentialsto the application.

• Application Server Installation Directory: Thedirectory where the web application server is in-stalled (for example C:\ProgramFiles\IBM\WebSphere\AppServer).

WebSphere 6.1




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

• Username: User name with administration rightsto the application server - mandatory for Oracle10g R3.

• Password: Password for account with administra-tion rights to the application server - mandatoryfor Oracle 10g R3.

• Server Instance: Name of the current web appli-cation server instance (for example “ myserver.do-main.com”).

• Admin is Secure: Select this option only if youwant Secure Sockets Layer (SSL) as part of thedeployment.

Note: If Admin is Secure is not selected, you willstill have to specify the username and passwordto access the server.

• Application Server Installation Directory: Thedirectory where the web application server is in-stalled (for example C:\product\10.1.3\OracleAS_1).

• Group Id: Name of the server group to which thetarget application belongs (for example "De-fault_group").

.

Oracle ApplicationServer 10g R3

2. Click Next to continue with the installation setup.The "Start Installation" screen is displayed.

Remember your credentials for the web application server as they may berequired to install BusinessObjects add-ons such as ProcessTracker oradditional language packs.



To start the installation

The" Start Installation" screen is the final screen in the installation setup.

• Click the Next button to start the installation process.

Note: If you are running the setup.exe program from the command line,and have the -w [filename] parameter switch enabled, this is the point atwhich you canCancel the installation process to have the .ini file writtenwith all the installation parameter information. This .ini file can then beused in silent and scripted installations.

Related Topics• Silent installation on page 28



Custom or ExpandInstallations

5

Performing a Custom or Expandinstallation

The Custom or Expand installation type allows you to install specific featuresand check the amount of disk space required by each feature. You may wantto perform a Custom or Expand installation when you want to exclude somecomponents, 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, otherwise you mayinadvertently fail to install a required component.

You can select or deselect features for your installation through a featuretree. The tree contains the following top-level features:

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

The following sections outline the features available for a Custom or Expandinstallation.

To select or deselect features

Use the "Select Features" screen to select and deselect BusinessObjectscomponents when running a Custom and Expand installation. All the availablefeatures are listed in the feature tree under theBusinessObjects Enterprisesnode. Each feature and subfeature has a corresponding icon.

1. Click the icon for a feature you want to select or deselect.You can do any of the following:• Specify that the selected feature will be installed on the local hard

drive.• Specify that the selected feature and its subfeatures will be installed

on the local hard drive.• Specify that a selected feature and its subfeatures will not be installed.


Custom or Expand Installations5 Performing a Custom or Expand installation

MeaningIcon associatedwith feature

The feature and only the subfeatures you select will beinstalled on the local hard drive you specified in theSetup program.

The feature and all its subfeatures will be installed onthe local hard drive you specified earlier .

The feature or subfeature is either unavailable or will notbe installed.

a. Click Disk Cost to calculate if sufficient disk space is available foryour selected features.A separate screen is displayed indicating storage space available onthe local machine and mapped network drives. Drives that do not haveenough disk space for the currently selected features are highlighted.Click OK to close to return to the "Select Features" screen.

b. Click Reset to revert to the original configuration of the feature list.

2. Click Next.

BusinessObjects Enterprise Client Components

The following BusinessObjects Enterprise XI 3.0 client components areavailable for installation:







5Custom or Expand InstallationsPerforming a Custom or Expand installation









Import Wizard


Publishing Wizard




Universe Designer









Translation Manager

BusinessObjects Enterprise Web Tier Components

The following Web Tier components are available when installingBusinessObjects Enterprise XI 3.0:


Includes all components used to run BusinessObjectsXI 3.0 applications including Central ManagementConsole, Infoview, Performance Management, andVoyager.

BI Platform Web Com-ponents

A component of Business Objects Enterprise built fordevelopers. It is composed of an implementation ofweb services that can be deployed with BusinessOb-jects Enterprise. This web service implementationprovides an API/WSDL which simplifies the processof developing applications. To further ease implemen-tation, the Web Services consumer API is provided forboth Java and .NET with a full set of documentationand samples.

BusinessObjects Enter-prise Web Services

If you do not have an existing web application server,you can choose to install Apache Tomcat 5.5.

Tomcat

BusinessObjects Server Components

The following BusinessObjects Enterprise XI 3.0 Server Components canbe installed by running a Custom or Expand installation. For furtherexplanation of what these servers do, please consult the “BusinessObjects



Enterprise Architecture” chapter of the BusinessObjects Enterprise 3.0Administrator's Guide.

• Central Configuration Manager

This is the application that can be used to start and stop services suchas Apache Tomcat supplied with the installation as well as the ServerIntelligence Agent.

When you select the Manage Servers icon on the toolbar you may alsostart, stop, restart, disable, enable and force termination of the Enterpriseservers. This tool is also used after installation to change which datasource is used for either the CMS or the auditing database, and to updateobjects after a migration.

• Mapping Support

Installs the necessary components for building interactive geographicmaps in Crystal Reports.

• Enterprise Servers• Central Management Server

• MySQL Database Server• Auditor

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



Database Access

The Database access feature installs the necessary drivers and files toprovide access to the following data sources:

• Data Federator• HP Neoview• MySQL• Generic ODBC• Salesforce.com Driver• Netezza• Microsoft• IBM

• IBM DB2• Informix (includes Redbrick)

• Progress OpenEdge• Oracle• Sybase• NCR Teradata

Export Support

The Export Support feature provides drivers and files to enable export to avariety of industry standard file formats.

• Character Separated Format (CSV)• Disk File Destination• Rich Text Format (RTF)• Word for Windows Format• Acrobat PDF Format• Text Format• Excel Format• Crystal Reports Format• XML Format• Legacy XML Format



Samples

Select theSamples feature to include sample reports in your BusinessObjectsEnterprise installation. These reports are found in the Report Samples folder.Included are sample reports for Crystal Reports, a BIAR file that includesWeb Intelligence reports as well as the Universe for those sample reports.

Note: Only English samples will be installed. Samples in other languagescan be downloaded from 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. These guides can be accessed after installation from Start >BusinessObjects XI 3.0 >BusinessObjects Enterprise >Documentation.

Note: The specific help related to an individual component is bundled withthe component. For example, if you install the Publishing Wizard or the ImportWizard you will get the appropriate .chm help.

To perform a custom or expandinstallation


1. Choose Custom or Expand in the "Install Type" screen.2. Specify where to install the BusinessObjects Enterprise components in

the Destination Folder field.3. Click Next.

The "Select Features" screen is displayed.

Related Topics• To select an installation type on page 44


Custom or Expand Installations5 To perform a custom or expand installation

http://support.businessobjects.com

• To select or deselect features on page 64• To only install the Server Components on page 71• Beginning your installation on page 41

To only install the Client Components

Use the procedure below when running a Custom or Expand installation toonly install the BusinessObjects Enterprise Client Components.

1. Left-click on the icon beside BusinessObjects Enterprise in the "SelectFeatures" screen.

2. Select Entire feature will be unavailable.

All the icons under BusinessObjects Enterprise will change to .

3. Left-click on the Client Components icon.4. Select Entire feature will be installed on local hard drive.

The Client Components icon will display as .

5. Click Next to continue with the installation setup.The installation setup program displays the following error message:You are installing one or more features without anyDatabase Access drivers. Without these, installedfeatures maynot function properly. Do you wish to continue?

6. Click Yes.The "Start Installation" screen is displayed.

7. Click Next to start the installation.

To only install the Server Components

Use the procedure below to only install the BusinessObjects EnterpriseServer Components. When you perform this installation, the servercomponents are installed, the default user and group accounts are created,and the sample reports are published to the system. When the installationis complete, the servers are started as services on the local machine.

1. Left-click on the icon besideClient Components in the "Select Features"screen and select Entire feature will be unavailable.


5Custom or Expand InstallationsTo perform a custom or expand installation

The Client Components icon changes to

2. Left-click on the icon beside Web Tier Components and select Entirefeature will be unavailable.

3. If you want to install MySQL skip to step 4. Expand Server Componentsif you do not want to install MySQL as your database server

Note: Do not install MySQL if you want to use an existing databaseserver. Do not install MySQL if you want to add server components to anexisting CMS cluster.

a. Expand Central Management Server.b. Left-click on the icon beside MySQL and select Entire Feature will

be unavailable.c. Left-click on the icon beside Auditor and select Entire Feature will

be unavailable.

4. Click Next to continue with the installation setup.If you chose to install MySQL you need specify information on your newCMS. If you chose not to install MySQL you need to specify whether ornot this is your first CMS cluster.

Related Topics• To specify CMS clustering information on page 72

To specify CMS clustering information

If you chose not to install MySQL, and are installing server componentsthrough a Custom or Expand installation, you need to provide information inthe "CMS Clustering" screen.

1. If this installation is the first CMS in your deployment, select Yes, enterthe information for the new CMS. You can now do one of the following.• In the fields provided enter information on the CMS port and the

password used by the CMS administrator.• Select theConfigure theBusinessObjects EnterpriseAdministrator

password at a later time box.

2. Select If no..if this server installation is not the first CMS in yourdeployment.a. Specify a port number for your new CMS installation.



b. Provide the CMS hostname, port number, and password for the clusterto which you want to add the CMS of your installation.

Before proceeding to the next screen, the installation setup program willtest connectivity to your existing CMS cluster based on the informationyou provided.

3. Click Next to continue with the installation setup.The "Server Intelligence Agent" screen is displayed.

Related Topics• To specify Server Intelligence Agent information on page 74

To enter information on your new CMS

The "Server Components Configuration" screen is used to specify the portnumber and an administrator password for the new Central ManagementServer (CMS). The Central Management Server's (CMS) role is tocommunicate with the other Enterprise servers and services and managethe system and audit databases.

1. Specify a port number in the CMS port field.



The default CMS port number is 6400.The CMS will communicate with other BusinessObjects Enterprise serversthrough the specified port.

2. Specify a password for the CMS administrator account in the Passwordand Confirm password fields.

Tip: You can opt to skip this step - select the Configure theBusinessObjects Enterprise Administrator password at a later timebox.

3. Click Next to continue with the installation setup.The "Server Intelligence Agent" screen is displayed.

Note: If the port you specified in step 1 is unavailable, you will berequested to specify another port number.

To specify Server Intelligence Agent information

The Server Intelligence Agent (SIA) is automatically created during installationof BusinessObjects Enterprise XI 3.0. For more information on ServerIntelligence and the Server Intelligence Agent, refer to the BusinessObjectsEnterprise Administrator's Guide. The "Server Intelligence Agent" screen isused to name and designate a port address for the SIA for the currentinstallation.



1. Provide a name to identify the SIA node in the Node Name field.2. Specify a port number for the SIA in the Port field.

This port will be used by the SIA to communicate with the CentralManagement Server (CMS).

3. Click Next to continue with the installation setup.Once the SIA information is entered, the port number will be validatedbefore you can proceed to configure the CMS database for yourinstallation. A warning will display if the port you specified is not available.

Related Topics• To configure your MySQL database server on page 75• To configure an existing database server on page 76

To configure your MySQL database server

The "MySQL Database Server Configuration" screen appears if you choseto install MySQL as the database server for your Custom or Expandinstallation.



1. Specify the port number for the MySQL database server in the MySQLPort Number field.The default port number is 3306. Use this number unless this port isunavailable.

2. Specify and confirm a password for the MySQL root user account in theMySQL root User Account pane.

3. Select the Enable remote root access box to activate remote root accessto the database server.

4. Specify and confirm a password for the MySQL BusinessObjects useraccount in the MySQL BusinessObjects User Account pane.

5. Click Next to continue the installation setup.The "Start Installation" screen is displayed.

To configure an existing database server

The "CMS Database Information" screen appears if you chose to use anexisting database server as your CMS for your Custom or Expand installation.



1. Select a database type from the Select existing CMS databasedrop-down list in "CMS Database".Depending on your database server selection, corresponding input fieldsare displayed in "CMS Database".

2. Provide all the required information for the database in the fields providedin "CMS Database".

The table below summarizes all the information required for each databasetype.

Information required for installa-tion setupDatabase type

Data Source NameSQL Server

Sybase Server NameSybase

DB2 database aliasDB2

tnsnames connect identifierOracle


a. To provide an ODBC DSN for a Microsoft SQL Server, click theBrowse button in "CMS Database".The "SQL Server Logon" screen is displayed.



Note: If you are running the installation on a Windows 64-bit machinean additional check box - Consume DSN created under WOW64 -is displayed.

b. Use the "SQL Server Logon" screen to select a data source, database,and to provide user credentials.

c. Click OK to submit your settings.The "SQL Server Logon" screen is closed and an ODBC DSN entryis displayed in"CMS Database".

If you do not want to specify an auditing database for your new installationskip to step 6.

3. Select the Auditing Database box to specify an auditing database foryour new installation.The input fields under the Auditing Database box are activated.

4. Select a database type from the Select existing Auditing databasedrop-down list in "Auditing Database"Depending on your database server selection, corresponding input fieldsare displayed in "Auditing Database".

5. Provide all the required information for the database in the fields providedin "Auditing Database".



The table below summarizes all the information required for each databasetype.

Information required for installa-tion setupDatabase type

Data Source NameSQL Server

Sybase Server NameSybase

DB2 database aliasDB2

tnsnames connect identifierOracle


6. Select the Reset existing database box to delete all current tables andentries in the existing database.

7. Click Next to continue with the installation setup.The "Start Installation" screen is displayed. This screen only displays ifa connection is established with the database configuration you provided.








To only install the Web Tier Components

Use the procedure below when running a Custom or Expand installation typeto only install the BusinessObjects Enterprise Web Tier Components.

1. Left-click on the icon beside BusinessObjects Enterprise in the "SelectFeatures" screen.

2. Select Entire feature will be unavailable.

All the icons under BusinessObjects Enterprise will change to .



3. Left-click on the Web Tier Components icon.4. Select Will be installed on local hard drive.

The Web Tier Components icon will display as .

5. If you want to install Apache Tomcat as your web application server skipto step 6. Expand Web Tier components if you want to use your existingweb application server.a. Left-click on the icon beside Tomcat.b. Select Entire Feature will be unavailable.

6. Click Next to continue with the installation setup.The "CMS Clustering" screen is displayed.

To specify CMS cluster information

When you only install Web Tier components as part of a custom or expandinstallation, you need to specify an existing CMS. Use the "CMS Clustering"screen to provide information on CMS to which you want to cluster your webtier components.1. Enter information on your existing CMS in the fields provided.

• Existing CMS Hostname• Existing CMS Port• CMS Administrator Password

Note: The CMS Hostname defaults to your local computer name.

2. Click Next to continue.The installation setup program will attempt to communicate with yourexisting CMS cluster using the information you provided.

You now need to configure your web application server.

To select a web application server configuration option




To configure your Tomcat application serverThe "Configure Tomcat" screen displays during installation setup if youchoose to install Tomcat as the Web application server for yourBusinessObjects Enterprise installation. Use this screen to configure Tomcatand the Java SDK.





To configure your existing Web application serverThe "Configure Web Application Server" screen displays during installationsetup after you specify an existing server in the "Select Web ApplicationServer" screen. To properly install web components on your web applicationserver, you must provide specific configuration information about your existingweb application server.



1. Specify the required configuration information for your existing webapplication server.






Apache Tomcat 5.5







WebLogic 10










WebLogic 9









WebSphere 6.1












.






Web ApplicationsInstallation

6

Performing a Web Tier installationThe 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 Java SDK 1.5 is installed by default with a web tier installation.

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.

Tip: If you have not yet installed the server components in your deployment,you will not be able to verify the connectivity for the web applications. It isbest practice to install the server and client components to verify connectivity.

BusinessObjects Enterprise Web Tier Components

The following Web Tier components are available when installingBusinessObjects Enterprise XI 3.0:


Includes all components used to run BusinessObjectsXI 3.0 applications including Central ManagementConsole, Infoview, Performance Management, andVoyager.

BI Platform Web Com-ponents

A component of Business Objects Enterprise built fordevelopers. It is composed of an implementation ofweb services that can be deployed with BusinessOb-jects Enterprise. This web service implementationprovides an API/WSDL which simplifies the processof developing applications. To further ease implemen-tation, the Web Services consumer API is provided forboth Java and .NET with a full set of documentationand samples.

BusinessObjects Enter-prise Web Services

If you do not have an existing web application server,you can choose to install Apache Tomcat 5.5.

Tomcat


Web Applications Installation6 Performing a Web Tier installation

To perform a Web Tier installation


1. Choose Web Tier in the "Install Type" screen.2. Specify where to install the BusinessObjects Enterprise components in

the Destination Folder field.3. Click Next to continue with the installation setup.

The "Select Features" screen is displayed.

Related Topics• To select an installation type on page 44• Beginning your installation on page 41

To select and deselect web tier components

Use the "Select Features" screen to select and deselect web tier componentswhen running a Web Tier installation. All the available web tier componentsare listed in the feature tree under the BusinessObjects Enterprises node.Each feature and subfeature has a corresponding icon.

1. Click the icon for a feature you want to select or deselect.You can do any of the following:• Specify that the selected feature will be installed on the local hard






6Web Applications InstallationPerforming a Web Tier installation




a. Click Disk Cost to calculate if sufficient disk space is available foryour selected features.A separate screen is displayed indicating storage space available onthe local machine and mapped network drives. Drives that do not haveenough disk space for the currently selected features are highlighted.Click OK to close to return to the "Select Features" page.

b. Click Reset to revert to the original configuration of the feature list.

2. Click Next to continue with the installation setup.The "CMS Clustering" screen is displayed.

To specify an existing CMS for web tier components

The web tier components need to be associated with an existing CentralManagement Server. Use the "CMS Clustering" screen to provide informationon the CMS that will manage the web tier components you are installing.



1. Specify the host name for the CMS in the Existing CMS Hostname field.2. Specify the port number used to communicate with the CMS in the

Existing CMS Port field.The default port number used by the CMS is 6400.

3. Specify the password used by CMS Administrator in the CMSAdministrator Password field.

4. Click Next to continue with the installation setup.The information on the CMS is verified. Once the verification is complete,the "Select Web Application Server" screen is displayed.

To select a web application server configurationoption




To configure your Tomcat application server

The "Configure Tomcat" screen displays during installation setup if youchoose to install Tomcat as the Web application server for yourBusinessObjects Enterprise installation. Use this screen to configure Tomcatand the Java SDK.







To configure your existing Web application server

The "Configure Web Application Server" screen displays during installationsetup after you specify an existing server in the "Select Web ApplicationServer" screen. To properly install web components on your web applicationserver, you must provide specific configuration information about your existingweb application server.1. Specify the required configuration information for your existing web

application server.






Apache Tomcat 5.5










WebLogic 10







WebLogic 9












WebSphere 6.1












.






Silent Installation

7

Overview of silent installationThere are two methods for running BusinessObjects Enterprise installationsfor Windows 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 method requires that you to specify an.ini file. The silent installation allows you to specify parameters for runningsetup.exe.

The same parameters are used for both methods. It is recommended thatyou use the scripted installation method to run custom installations, so thatyou avoid having to pass a large number of parameter settings directlythrough the command line.

Note: If you pass a parameter directly in the command line, the setting willoverride any setting specified in the .ini file.

These installation methods are particularly useful when you need to quicklyperform multiple installations. You can also integrate the scripts andcommands into your own installation scripts.

Silent installations include a series of parameters including installation settingsand directory paths to system resources. You can also specify settings thatcontrol the level of prompts during an installation.

Note: BusinessObjects Enterprise does not support silent installations whenthe install contents are on multiple CDs. If your install is on multiple CDs,you must first copy the contents from all the CDs to a central location, suchas the local hard-drive, and then run the silent install from the location thatcontains the content from all the CDs.

Related Topics• Specific ini file parameters for setup.exe on page 103• Silent and scripted installation parameters on page 107


Silent Installation7 Overview of silent installation

Specific ini file parameters for setup.exeThere are 3 parameters used in conjunction with the .ini file than can beused when running setup.exe on the command line.

DescriptionParameter

Writes all the installation settings to an .ini file to thespecified filepath. If a filepath is not specified, the file isstored in the system default %TEMP% folder.

-w<filepath/filename.ini>

Reads the specified.ini file and passes the settings tothe installer as settings.

Note: If you pass a parameter directly in the commandline, the setting will override any setting specified in the.ini file.

-r <filepath/filename.ini>

Creates an installation log file in the specified filepath. Ifa filepath is not specified, the system default %TEMP%folder is used. This parameter can only be used if -r isalso specified.

-l <filepath/filename.ini>

Related Topics• Silent and scripted installation parameters on page 107

To create an installation .ini fileYou need to access the directory containing the setup.exe file.

1. Open a command line console.2. CD to directory containing the BusinessObjects Enterprise setup.exe.3. In the command-line type the following:

setup.exe -w filename.ini responsefilepath

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

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

until you reach the final screen of the setup program.


7Silent InstallationSpecific ini file parameters for setup.exe

.These settings are recorded in the response file.

6. Click Cancel to abort the installation setup.

All the parameters - user-defined and default - from installation setup arepassed to the .ini file which is stored in the directory specified in step 3.

Note: If a filepath is not specified, the file is stored in the system default%TEMP% folder.

Related Topics• Specific ini file parameters for setup.exe on page 103• Silent and scripted installation parameters on page 107

Sample .ini script fileThe following installation script was generated for a new BusinessObjectsEnterprise installation in which MySQL and Tomcat were installed. TheGerman language pack was added to the default English language pack.[OTHER]QUIET=/qa[INSTALL] ALLUSERS="1"


Silent Installation7 Sample .ini script file

AS_ADMIN_IS_SECURE=""AS_ADMIN_PASSWORD=""AS_ADMIN_PORT="8080"AS_ADMIN_USERNAME="admin"AS_DIR="../Tomcat55"AS_INSTANCE="localhost"AS_SERVER="tomcat55"AS_SERVICE_NAME="BOE120Tomcat"AS_VIRTUAL_HOST=""ApplicationUsers="AllUsers"CADNODE="VANW11AKAHAN"CADPORT="6410"CLIENTAUDITINGPORT="6420"CLIENTLANGUAGE="EN"CLUSTERCMS="False"CMSPASSWORD=""COMPANYNAME="Business Objects"DATABASEAUDITDRIVER="MySQLDatabaseSubSystem"DATABASECONNECT=""DATABASEDB="BOE120"DATABASEDB_AUDIT="BOE120_AUDIT"DATABASEDRIVER="MySQLDatabaseSubSystem"DATABASEDSN="Business Objects CMS"DATABASEDSN_AUDIT="Business Objects Audit Server"DATABASENWLAYER_AUDIT="ODBC"DATABASEPWD="sa"DATABASEPWD_AUDIT="sa"DATABASEPWD_MYSQLROOT="sa"DATABASERDMS_AUDIT="MySQL 5"DATABASESERVER_AUDIT="localhost"DATABASEUID="sa"DATABASEUID_AUDIT="sa"DATABASE_AUDIT_CONNSVR="connsvr"ENABLELOGFILE="1"ENABLESERVERS="1"INSTALL.LP.DE.SELECTED="1"INSTALL.LP.EN.SELECTED="1"INSTALL.LP.JA.SELECTED="1"INSTALLDBTYPE="SQL"INSTALLDIR="C:\Program Files\Business Objects\"INSTALLLEVEL="6"INSTALLMODE="New"INSTALLSWITCH="Server"INSTALL_DB_TYPE="InstallMySQL"MYSQLPORT="3306"MYSQL_REMOTE_ACCESS="1"NEWCMSPASSWORD=""NSPORT="6400"PIDKEY="C901B-CUZ6S76-000500J-G9M3"Privileged="1"SINGLESERVER=""SKIP_DEPLOYMENT=""TOMCAT_CONNECTION_PORT="8080"


7Silent InstallationSample .ini script file

TOMCAT_REDIRECT_PORT="8443"TOMCAT_SHUTDOWN_PORT="8005"USERNAME="Licensed User"WCADOTNETINSTALL=""WCAJAVAINSTALL="True"WCATOMCATINSTALL="True"WDEPLOY_LANGUAGES="en,fr,ja,de,es,it,ko,nl,sv,pt,zh_CN,zh_TW"

WDEPLOY_LATER=""WEBSITE_METABASE_NUMBER="1"WEBSITE_PORT="80"[FEATURES]REMOVE=""ADDLOCAL="Tomcat,Universe,Complete,BIPWebComp,Designer,AlwaysInstall,BeforeInstall,VBA62,Reporter,Clients,WRC,DataSourceMigrationWizard,CrystalBVM,MetaDataDesigner,ConversionTool,ImportWizard,PubWiz,qaaws,JavaRASSDK,BOEJavaSDK,JavaViewersSDK,RebeanSDK,DevelopersFiles,WebServicesSDK,UnivTransMgr,wdeploy,WebTierComp,BOEWebServices,CCM,ServerComponents,Mapping,Repository,CRPE,MetaData,CMS,Auditor,MySQL,EventServer,InputFRS,OutputFRS,CacheServer,PageServer,PublicationServer,DotNETOnly,ReportAppServer,MDASS,CRJobServer,DestJobServer,LOVJobServer,DeskIJobServer,ProgramJobServer,WebIJobServer,AdaptiveJobServer,PublishingService,AdaptiveProcessingServer,SearchingService,CrystalReportDataProvider,AuditProxyService,Webi,RAS21,DAS,AuditRptUnvEN,DADataFederator,DataAccess,HPNeoview,WebActivityLog,OLAP,MyCube,SOFA,DAMySQL,DAGenericODBC,SFORCE,XML,BDE,dBase,FileSystem,DANETEZZA,DAMicrosoft,DAIBMDB2,IBM,Redbrick,DAIBMInformix,OLE_DB_Data,DAProgressOpenEdge,DAOracle,SybaseAnywhere,DASybase,SybaseASE,SybaseIQ,SymantecACT,DANCRTeradata,TextDA,Btrieve,CharacterSeparated,ExportSupport,ExpDiskFile,ExpRichTextFormat,ExpWordforWindows,PDF,ExpText,ExpExcel,ExpCrystalReports,XMLExport,LegacyXMLExport,SamplesEN,UserHelp,LanguagePackCostingFeatureen,LanguagePackCostingFeature"ADDSOURCE=""ADVERTISE=""

This script can now be used for future silent installations by including the filename and path in the command line as shown below:setup.exe -r FILEPATH


Silent Installation7 Sample .ini script file

Silent and scripted installationparameters

The following table lists common parameters that are used for both silentand scripted installations of BusinessObjects Enterprise on Windows.

Caution: If you pass a parameter directly in the command line, the settingwill override any setting specified in the .ini file.


Specifies not to prompt during or after the installation.

Note: You must also enter the CLIENTLANGUAGE param-eter as part of your silent install string or the language selec-tion screen will appear at the beginning of your install.

/qn

Specifies to prompt when the installation is complete.

Note: You must also enter the CLIENTLANGUAGE param-eter as part of your silent install string or the language selec-tion screen will appear at the beginning of your install.

/qn+

Specifies is administrator credential must be passed to accessthe web application server. This setting only valid for Web-Sphere 6 and Oracle.AS_ADMIN_IS_SECURE="true"

AS_ADMIN_IS_SECURE

Password used by the administrator account to access theweb application server.AS_ADMIN_PASSWORD="pass"

AS_ADMIN_PASSWORD

Specifies the port used by the web application server.AS_ADMIN_PORT="8080"

AS_ADMIN_PORT

Specifies the account name used by the administrator to ac-cess the web application server.AS_ADMIN_USERNAME="admin"

AS_ADMIN_USERNAME


7Silent InstallationSilent and scripted installation parameters


Specifies the installation directory for the web applicationserver.AS_DIR="<INSTALLDIR>/Tomcat55"

AS_DIR

Specifies the name of the current web application server in-stance.AS_INSTANCE="localhost"

AS_INSTANCE

Web application type used in installation. the following optionsare available:• 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 Windows service if the applicationserver will be installed as a service on Windows.AS_SERVICE_NAME="BOE120Tomcat"

AS_SERVICE_NAME

Specifies virtual host to which the application must be bound.AS_VIRTUAL_HOST="hostname"

AS_VIRTUAL_HOST

Specifies the node name for the Server Intelligence Agent.CADNODE="SIA1"

CADNODE

Specifies the port used by Server Intelligence Agent.CADPORT="6410"

CADPORT


Silent Installation7 Silent and scripted installation parameters


Specifies the language used by the installer:• EN=English• ZH_CN=Simplified Chinese• ZH_TW=Traditional Chinese• DE=German• ES=Spanish• KO=Korean• NL=Dutch• JA=Japanese• PT=Portuguese• SV=Swedish• RU=Russian• FR=French

Note: If this parameter not specified, you will be promptedto select a language when the installation setup begins.CLIENTLANGUAGE="EN"

CLIENTLANGUAGE

Specifies if you are adding servers to an existing CMS. Tochange this setting, it is recommended that you create a new.ini file.CLUSTERCMS="False"

CLUSTERCMS

Specifies the administrator password for an existing CMS touse in either a custom or web tier installation.CMSPASSWORD="password"

CMSPASSWORD

The company name specified when setting user credentialsin the installation setup.COMPANYNAME="MyCompanyName"

COMPANYNAME

Specifies which driver to use for the auditing database. Tochange this setting, it is recommended that you create a newini file.DATABASEAUDITDRIVER="MySQLDatabaseSubSystem"

DATABASEAUDITINGDRIVER

Name of the CMS database on the database server.DATABASEDB="BOE120"

DATABASEDB




Name of the auditing database on the database server.DATABASEDB_AUDIT="BOE120_AUDIT"

DATABASEDB_AUDIT

Specifies which driver to use for the CMS database.To changethis setting, it is recommended that you create a new ini file.DATABASEDRIVER="MySQLDatabaseSubSystem"

DATABASEDRIVER

Specifies the ODBC connection to connect to the CMSdatabase.DATABASEDSN="Business Objects CMS"

DATABASEDSN

Specifies the ODBC connection to connect to the auditingdatabase.DATABASEDSN_AUDIT="Business Objects Audit Server"

DATABASEDSN_AUDIT

Specifies auditing database type. To change this setting, itis recommended that you create a new ini file.DATABASENWLAYER_AUDIT="ODBC"

DATABASENWLAYER_AUDIT

Specifies the password used to access the database server.DATABASEPWD="password"

DATABASEPWD

Specifies the password used to access the auditing databaseserver.DATABASEPWD_AUDIT="password"

DATABASEPWD_AUDIT

The password used by the root account to access if you areinstalling the MySQL database server.DATABASEPWD_MYSQLROOT="password"

DATABASEPWD_MYSQLROOT

Specifies the auditing database type. To change this setting,it is recommended that you create a new ini file.DATABASERDMS_AUDIT="MySQL 5"

DATABASERDMS_AUDIT

Specifies the CMS database server name.DATABASESERVER="localhost"

DATABASESERVER




Specifies the auditing database server name.DATABASESERVER_AUDIT="localhost"

DATABASESERVER_AUDIT

Specifies the username used to access the CMS database.DATABASEUID="servername"

DATABASEUID

Specifies the username used to access the auditing database.DATABASEUID_AUDIT="auditname"

DATABASEUID_AUDIT

Specifies if a log file will be created for the installation.ENABLELOGFILE="1"

ENABLELOGFILE

Specifies if servers should be enabled once the installationis complete.ENABLESERVERS="1"

ENABLESERVERS

Specifies which language pack to install. The following optionsare available :• EN=English• ZH_CN=Simplified Chinese• ZH_TW=Traditional Chinese• DE=German• ES=Spanish• KO=Korean• NL=Dutch• JA=Japanese• PT=Portuguese• SV=Swedish• RU=Russian• FR=French

Note: The English language pack is always selected by de-fault.INSTALL.LP.EN.SELECTED="1"INSTALL.LP.JA.SELECTED="1"

INSTALL.LP.<>.SELECTED




Specifies the directory where you want to install the Busines-sObjects Enterprise components.INSTALLDIR="C:\Program Files\Business Objects\"

INSTALLDIR

Specifies the installation method from one of the followingoptions:• New• Custom• WebTierINSTALLMODE="New"

INSTALLMODE

Specifies the port if you are installing the MySQL databaseserver.MYSQLPORT="3306"

MYSQLPORT

Specifies to enable remote access if you are installing theMySQL database server.MYSQL_REMOTE_ACCESS="1"

MYSQL_REMOTE_ACCESS

Specifies the port used by the CMS.NSPORT="6400"

NSPORT

Specifies your product license key code.PIDKEY="xxxxx-xxxxxx-xxxxxx-xxxx"

PIDKEY

Specifies the port number that Tomcat uses to connect.TOMCAT_CONNECTION_PORT="8080"

TOMCAT_CONNECTION_PORT

Specifies the port number that Tomcat uses to redirect.TOMCAT_REDIRECT_PORT="8443"

TOMCAT_REDIRECT_PORT

Specifies the port number that Tomcat uses to shut downTOMCAT_SHUTDOWN_PORT="8005"

TOMCAT_SHUTDOWN_PORT




The username specified in the installation setup when provid-ing the license key code .USERNAME="Licensed User"

USERNAME

Specifies not to automatically deploy the web application onthe target web application server. This is an automaticallygenerated parameter that should not be modified.WDEPLOY_LATER="1"

WDEPLOY_LATER

Specifies which client, server, web tier, and other Busines-sObjects Enterprise components will not be installed. Tochange this setting, it is recommended that you create a newini file.REMOVE="Tomcat,BIPWebComp,Designer,Reporter,Clients,WRC,

DataSourceMigrationWizard,MetaDataDesigner,ConversionTool,ImportWizard,

PubWiz,qaaws,BOEJavaSDK,DevelopersFiles,WebServicesSDK,UnivTransMgr,

WebTierComp,BOEWebServices"

REMOVE

Specifies which client, server, web tier, and other Busines-sObjects Enterprise components will be installed. To changethis setting, it is recommended that you create a new ini file.ADDLOCAL="Tomcat,Universe,Complete,BIPWebComp,Designer,AlwaysInstall,

BeforeInstall,VBA62,Reporter,Clients,WRC,DataSourceMigrationWizard,

CrystalBVM,MetaDataDesigner,ConversionTool,ImportWizard,PubWiz,qaaws,

JavaRASSDK,BOEJavaSDK,JavaViewersSDK,RebeanSDK,DevelopersFiles,

WebServicesSDK,UnivTransMgr,wdeploy,WebTierComp,BOEWebServices,

CCM,ServerComponents,Mapping,Repository,CRPE,MetaData,CMS,Auditor"

ADDLOCAL

Other automatically generated parameters

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



Parameter name

DATABASECONNECT

DATABASE_AUDIT_CONNSVR

INSTALLDBTYPE

INSTALL_DB_TYPE

INSTALLLEVEL

INSTALLSWITCH

NEWCMSPASSWORD

Privileged

SINGLESERVER

SKIP_DEPLOYMENT

WCADOTNETINSTALL

WCAJAVAINSTALL

WCATOMCATINSTALL

WDEPLOY_LANGUAGES

WEBSITE_METABASE_NUMBER

WEBSITE_PORT

ADDSOURCE

ADVERTISE

Related Topics• Specific ini file parameters for setup.exe on page 103



After InstallingBusinessObjects Enterprise

8

Launching the Central ManagementConsole (CMC)

The BusinessObjects Enterprise Central Management Console (CMC) Logonscreen appears if you selected the Launch BusinessObjectsAdministration Console option on the last screen of the installation setupprogram.

You can also launch the CMC by going to:Start > Programs >BusinessObjects XI 3.0 >BusinessObjects Enterprise >BusinessObjectsEnterprise Central Management Console.

It is recommended that you verify your installation by logging into the CMC.Once you access the CMC you can create users and groups, set up securitypolicies, and define rights. For more information on using the CMC, see theBusinessObjects Enterprise Administrator's Guide.

To log on to the CMC

1. Type the name of your Central Management Server (CMS) in theSystemfield.

2. Type your User Name and Password.

If you are using LDAP or Windows NT authentication, you can log onusing an account that has been mapped to the BusinessObjectsEnterpriseAdministrators group.

Note: If this is the first time an administrator from your organization isaccessing the CMC, type “Administrator” as the User Name. ThisEnterprise account by default does not have a password unless youspecified one during installation setup.

3. Select Enterprise in the Authentication Type list.

Windows AD, Windows NT, and LDAP authentication also appear in thelist; however, third-party user accounts and groups must be mapped toBusinessObjects Enterprise before you can use these types ofauthentication.

4. Click Log On.The CMC Home page is displayed.


After Installing BusinessObjects Enterprise8 Launching the Central Management Console (CMC)

Troubleshooting CMC logon issues

If you are unable to log on to the CMC, consider the following solutions:

1. Did you provide the correct name for the Central Management Server inthe System field?

2. Did you provide the correct user credentials in the User Name andPassword fields?

3. Is the correct method specified in the Authentication field?4. Check if the Server Intelligence Agent (SIA) is running. Go to Start >

BusinessObjects XI 3.0 > BusinessObjects Enterprise > CentralConfiguration Manager. If the SIA is not running, start or enable it.

5. If you did not install MySQL as part of your installation, use the databaseclient to connect to the database server. See your database documentationfor more information.

6. Are you attempting to connect to a CMS cluster using the @<clustername>format? If this is your first attempt to connect to this cluster, the CMC willnot know which CMS servers belong to the cluster. In this case, you needto specify a list of CMS servers in the web.xml which is found in the WEB-INF folder of the CMC web application war file. Follow the instructions inthe cms.clusters section of the web.xml file for more details. It is alsopossible to specify CMS cluster information for the InfoView by modifyingits corresponding web.xml file.

7. Go to Start > BusinessObjects XI 3.0 > BusinessObjects Enterprise> Diagnostic Tool. Run the tool to verify your deployment.

If none of these solutions work, consider repairing or reinstallingBusinessObjects Enterprise.

Related Topics• To run diagnostic tests in Windows on page 119

Register your installed productAfter installing BusinessObjects Enterprise, you can register your product.Your installation on Windows includes the Business Objects RegistrationWizard, a tool designed to ease the process of obtaining registrationcredentials.


8After Installing BusinessObjects EnterpriseRegister your installed product

Once registered, you can access Business Objects support programs andservices. The Registration Wizard also provides links for resources to helpyou evaluate or purchase Business Objects products.

To access the wizard, go toStart > Programs > BusinessObjects XI 3.0 >Registration Wizard.

Diagnostic Tool

Deployment Diagnostic tool

The Deployment Diagnostic Tool is a Java-based application designed toverify basic operating functionality of a BusinessObjects Enterprise XI 3.0installation. It is an open-framework utility that allows for the developmentof additional test drivers through the use of various SDKs provided byBusiness Objects.

Note: This tool is intended only for deployment validation purposes; anyother uses are not supported by Business Objects.

The following software is required to use the Diagnostic Tool:

• JDK 1.5 (included with your BusinessObjects Enterprise installation)• Business Objects Enterprise XI 3.0 installation

Tests you can perform

Currently, the Deployment Diagnostic Tool includes the following test drivers:

• Log On/Off - tests logging on and off BusinessObjects Enterprise.

• InfoView Test - test logging on and logging off through InfoView.

• Web Intelligence Tier - tests creating, viewing, and scheduling a simpleWeb Intelligence document.

• Crystal Reports Tier - tests creating and scheduling a simple CrystalReports document.

• Start/Stop Servers - connects to a CMS and queries for all availableservers associated with it, then proceeds to stop and start each one.


After Installing BusinessObjects Enterprise8 Diagnostic Tool

Tests you can perform

Currently, the Deployment Diagnostic Tool includes the following test drivers:

• Log On/Off - tests logging on and off BusinessObjects Enterprise.

• InfoView Test - test logging on and logging off through InfoView.

• Web Intelligence Tier - tests creating, viewing, and scheduling a simpleWeb Intelligence document.

• Crystal Reports Tier - tests creating and scheduling a simple CrystalReports document.

• Start/Stop Servers - connects to a CMS and queries for all availableservers associated with it, then proceeds to stop and start each one.

To run diagnostic tests in Windows

1. From the Start menu, clickPrograms > BusinessObjects XI 3.0 >BusinessObjects Enterprise > Diagnostic Tool.

The user logon screen appears.

2. In the System field, enter the hostname for the machine you want toconnect to.Information for the local machine will appear by default.

3. Enter your user name and password and select the appropriateauthentication type, then click Logon.

If you are authenticated, the main application is screen appears.

The top pane of the tool contains a list of the test drivers that have beenloaded into memory. This list is determined by the contents of theconfiguration file.

The bottom pane is the console output and provides status updates whilethe tests are running. These updates remain on the display after the testsare complete.

4. To initiate a diagnostic, select Run All Tests from the Test menu.


8After Installing BusinessObjects EnterpriseDiagnostic Tool

The diagnostic is performed in the sequence that it appears in the testdrivers pane, and a status update is provided in the console pane.

Note: Some tests may take several minutes.

Upon completion of the diagnostic, the console reads 'Finished Testing' andprovides a file path to the results log file. All test drivers will either concludewith a 'pass' or a 'fail' status. Double-click the result to view further details.These details are also recorded in the log file.

To view the log file, either go to the location specified in the console pane,or select the View menu and then select Log File.

To run Diagnostic Test from Command Line

1. Open your command line interface.

The following list explains the different parameters that you can enter intothe command line:

• gui - Runs the application in graphical mode

• console - Runs the application in console mode

• run - (Optional) This launches and runs the test drivers immediately.Default behavior is to have the user manually initiate the tests.

• configfile - (Optional) Specify the absolute or relative path to theconfiguration xml file which tells the tool what test drivers to run.

• logfile - (Optional) Specify the absolute or relative path to the resultsxml log file.

• user - Required if the tool is run in console mode. This is theBusinessObjects Enterprise user name that the tool uses to log in andit should have administrative rights.

• password - Required if the tool is run in console mode. This is theBusinessObjects Enterprise user password.

• system - Required if the tool is run in console mode. This is the CMSthe tool will attempt to connect to.

• authtype - Required if the tool is run in console mode. This is theauthentication method used to connect the tool will connect to BOE.Possible values (Enterprise, LDAP, WinAD, WindowsNT)



2. Enter the following command:java -jar

diagnosticTool.jar -[mode] -run-configfile [config file]-logfile [log file] -user [username]-password [password]-system [system name] -authtype[authentication type]

The Diagnostic Tool launches.

Example: Launching in CONSOLE mode

The following command launches the tool, opens a login dialog box, opensthe tool interface in a window, and overrides the default config file and logfile with the ones presented.

'java -jar diagnosticTool.jar -gui-configfile 'c:\temp\config.xml' -logfile'c:\log\log.xml'

Note: If you want to bypass the login screen, you can uncomment the xml tagsin the config file and fill in the necessary authentication tags, as shown below.

<authentication><user>administrator</user><password> </password><system>TestBOESystem</system><authtype>Enterprise</authtype></authentication>

The following command launches the tool, automatically logs in with thecredentials supplied, uses the default config file and log file, andautomatically runs the test case.'java -jar

-diagnosticTool.jar -console-user Administrator -password 'Password'-system TestBOESystem -authtype Enterprise'

.



Diagnostic options

The following section describes some of the option settings for the diagnostictool.

Configuration files

Configuration files are used to determine which tests to run, the order inwhich to run them, and any parameters for those tests.

To set configuration files1. Select Set Config File from the Test menu.

A file dialog box used to select the configuration XML is displayed. Thedefault XML name is 'TestClasses.xml'.

2. Navigate to the XML file you want to set and select it.3. Click Open, then click OK.

This will set the configuration XML for the tool.

Log files

Log files provide a permanent record of the results of the tests run by thediagnostic tool. The following procedure shows you how to set the locationfor a log file.

To set a custom log file location1. Choose Set Log File from the Test menu.

The "Set Log File" window appears.

2. Browse to the location where you want to store the log file.3. Type a name for the log file, and click Open.

Log files for tests will now appear in the directory you selected.

To set configuration files

1. Select Set Config File from the Test menu.



A file dialog box used to select the configuration XML is displayed. Thedefault XML name is 'TestClasses.xml'.

2. Navigate to the XML file you want to set and select it.3. Click Open, then click OK.

This will set the configuration XML for the tool.

To set a custom log file location

1. Choose Set Log File from the Test menu.The "Set Log File" window appears.

2. Browse to the location where you want to store the log file.3. Type a name for the log file, and click Open.

Log files for tests will now appear in the directory you selected.



Language Packs onWindows

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 Windows9 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 packs 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 Windowssystems

Language packs can be installed either during the initial installation ofBusinessObjects Enterprise, or post-install using a dedicated language packinstaller. The installer is a single executable that adds the localized languageresources to your Business Objects software deployment.

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

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

Note: An error message will be displayed if a language pack detects that itis incompatible with a previously installed version of BusinessObjectsEnterprise.


9Language Packs on WindowsInstalling language packs and complex deployments

http://technicalsupport.businessobjects.com

Locating language packsLanguage packs can be found in the langs folder of the BusinessObjectsEnterprise for Windows distribution package.

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

To install language packs

Before installing a language pack, your BusinessObjects Enterprise servermust be running and patched to the required revision level. You will be askedfor CMS administrator credentials. If any part of your BusinessObjectsEnterprise deployment is not patched to the required software version, thelanguage pack installation will abort and must be reapplied after the systemhas been patched to the correct level. Please review the requirements 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_INSTALL_CD_DIR\langs\LANGUAGE\.

3. Run the setup.exe installer.Replace LANGUAGEwith the ISO code of the language you are installing.The Microsoft Windows installer will search for all installed BusinessObjects applications.

4. Click Next.5. Check I accept the License Agreement, and then click Next.6. Enter values for the CMS, CMS Port, User Name, Password, and

Authentication fields. Click Next.7. Enter values for the Port, Username, Password, Server Instance, and

Virtual Host, and Application Server Installation Directory fields. Ifyour web application server uses a password for the administrator account,select the Admin is Secure check-box. Click Next.

8. Click Next to begin the installation.


Language Packs on Windows9 Locating language packs

http://technicalsupport.businessobjects.com

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

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

The language pack will now begin the installation process.

Once the installation is complete, you will be able to choose the installedlanguage from the Options dialog window in BusinessObjects Enterpriseapplications.

Note:

• All fix packs or other updates to BusinessObjects Enterprise released ona date after the language pack release date must be re-applied to ensurethat updated functionality is maintained.

• Language packs must be re-installed after you have added or removeda component from your BusinessObjects Enterprise deployment.

Installing language packs across 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:

setup.exe BUSINESS_OBJECTS_HOME_DIRINSTALLMODE=silentCMSNAMESERVER=CMS_HOSTNAMECMSPORTNUMBER=PORT_NUMBERCMSPASSWORD=CMS_PASSWORD

BUSINESS_OBJECTS_HOME_DIRwith the full path of your BusinessObjectsEnterprise installation. The following table details each of the otherparameters used by setup.exe.

DescriptionExpected argu-ment

Parameter

Switch to enable silent install modesilentINSTALLMODE

Enter the name of your CMS ma-chine.

CMS HostnameCMSNAMESERVER


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

DescriptionExpected argu-ment

Parameter

CMS port number.Port number forCMS

CMSPORTNUMBER

The password for your CMS server.CMS admin pass-word

CMSPASSWORD

For example:setup.exe

"C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0"

INSTALLMODE=silentCMSNAMESERVER=myserver1CMSPORTNUMBER=6400CMSPASSWORD=mypassword

To uninstall language packs in silent mode, use the wdeploy undeployall

command to remove all web applications, then wdeploy deployall tore-deploy web applications without the language packs.

For example, the following command runs undeployall for a WebLogic 10server:wdeploy.bat weblogic10-Das_dir=C:\bea\user_projects\domains\base_domain-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_username=weblogic-Das_admin_password=weblogicundeployall

Followed by:wdeploy.bat weblogic10-Das_dir=C:\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 159


Language Packs on Windows9 Installing language packs across a BusinessObjects Enterprise deployment

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

are running.2. In Windows, click Start, point to Settings, and then selectControl Panel.3. Double-click Add/Remove Programs.4. Select the BusinessObjects Enterprise XI 3.0 Language Pack to

remove and click Remove.The "Add/Remove Programs" prompts you to confirm that you want toremove the language pack from your computer.

5. Click Yes.The appropriate files are removed and the necessary configuration iscompleted.

6. Click Finish.

The language pack has been uninstalled and you are returned to the"Add/Remove Programs" list.


9Language Packs on WindowsTo uninstall language packs


Language Packs on Windows9 To uninstall language packs

Client Tools Installation

10

Overview of Client Tools installationBusinessObjects Enterprise client applications are available for installationthrough a separate installation program. You can use this stand alone installerto add client tools and their related components to an existing installation.

The Client Tools installation program enables you to select which client toolsto install and to assess disk space costs.

Note: You can also install client tools by selecting the BusinessObjectsEnterprise Custom or Expand install option.

BusinessObjects Enterprise ClientComponents

The following BusinessObjects Enterprise XI 3.0 client components areavailable for installation:











Client Tools Installation10 Overview of Client Tools installation





Import Wizard


Publishing Wizard




Universe Designer






Translation Manager

To perform a client tools installationA product distribution CD/DVD for the BusinessObjects Enterprise ClientTools Installation.


10Client Tools InstallationTo perform a client tools installation

1. Run setup.exe from the root directory of your product distribution.2. Click Install to launch the installation setup program.

Note: If you are installing from a CD and if the Autoplay is enabled foryour CD-ROM drive, the Autorun program will start automatically. "PleaseChoose Setup Language" is displayed.

3. Select the language for the installation setup from the pull-down listprovided.You have a choice of the following languages for setup:• English• French• Japanese• German• Spanish• Italian• Chinese Simplified• Chinese Traditional• Korean• Dutch• Swedish• Portuguese (Brazil)

4. Check the Create log file during installation box if you want to createan installation log file.The log file is saved under the following directory: <INSTALLDIR>\BusinessObjects Enterprise 12.0\Logging.

5. Click OK.

The "Welcome to the BusinessObjects Enterprise XI 3.0 InstallationWizard" is displayed after you specify a language for the installation setup.


Client Tools Installation10 To perform a client tools installation

6. Click Next to proceed with the installation setup.

Note: Click Cancel to abort the installation setup

If you are installing BusinessObjects Enterprise XI 3.0 on Windows XPService Pack2 or higher, is message is displayed. Click OK to continuewith the installation setup.The "License Agreement" screen is displayed



7. Select I accept the License Agreement and click Next.The "Choose Language Packs" screen is displayed.

8. Select the Language Packs you want to install with the client tools clickNext.The language packs currently available for installation include:• English• French• Japanese• German• Spanish• Italian• Chinese Simplified• Chinese Traditional• Korean• Dutch• Swedish• Portuguese (Brazil)

Note: English is a required language and is automatically selected.



Tip: Select the All Languages box to select all the available languagepacks.

The "Directory Selection" screen is displayed.

9. Type the installation directory for the client tools in Destination Folderor accept the default selection and click Next.The "Select Features" screen is displayed.



10. Click the icon for a feature you want to select or deselect under the"BusinessObjects Enterprise Client Tools" node. When you have finishedmaking your selections click Next.You can do any of the following:• Specify that the selected feature will be installed on the local hard









a. Click Disk Cost to calculate if sufficient disk space is available foryour selected features.A separate screen is displayed indicating storage space available onthe local machine and mapped network drives. Drives that do not haveenough disk space for the currently selected features are highlighted.Click OK to close to return to the "Select Features" screen.

b. Click Reset to revert to the original configuration of the feature list.The "Start Installation" screen is displayed.

11. Click Next.The installation process begins and is complete when the following screenis displayed:



12. Click Finish to exit the installation.

Client Tools silent installationsThere are two methods for running BusinessObjects Enterprise Client Toolsinstallations directly from the command line:

• Scripted installations• Silent installations

Both methods can be used to automate installations across multiplemachines. The scripted installation method requires that you to specify an.ini file. The silent installation allows you to specify parameters for runningsetup.exe. The same parameters are used for both methods. It isrecommended that you use the scripted installation method to run custominstallations, so that you avoid having to pass a large number of parametersettings directly through the command line. These installation methods areparticularly useful when you need to quickly perform multiple installations.You can also integrate the scripts and commands into your own installationscripts.


Client Tools Installation10 Client Tools silent installations

Note: If you pass a parameter directly in the command line, the setting willoverride any setting specified in the .ini file.

Related Topics• Specific ini file parameters for setup.exe on page 103• To create an installation .ini file on page 103

Sample client tools ini file

The following installation script was generated for a BusinessObjectsEnterprise Client Tools installation. The Dutch language pack was added tothe default English language pack.[OTHER]QUIET=/qa[INSTALL]CLIENTLANGUAGE="EN"DATABASEAUDITDRIVER="MySQLDatabaseSubSystem"DATABASEDRIVER="MySQLDatabaseSubSystem"ENABLELOGFILE="1"INSTALL.LP.EN.SELECTED="1"INSTALL.LP.NL.SELECTED="1"INSTALLDIR="C:\Program Files\Business Objects\"INSTALLLEVEL="4"WDEPLOY_LANGUAGES="en,nl"[FEATURES]REMOVE="UnivTransMgr"ADDLOCAL="Complete,AlwaysInstall,BeforeInstall,VBA62,Reporter,Clients,WRC,DataSourceMigrationWizard,CrystalBVM,MetaDataDesigner,ConversionTool,ImportWizard,PubWiz,qaaws,Designer,JavaRASSDK,BOEJavaSDK,JavaViewersSDK,RebeanSDK,DevelopersFiles,WebServicesSDK,DADataFederator,DataAccess,HPNeoview,WebActivityLog,OLAP,MyCube,SOFA,DAMySQL,DAGenericODBC,SFORCE,XML,Universe,BDE,dBase,FileSystem,DANETEZZA,DAMicrosoft,DAIBMDB2,IBM,Redbrick,DAIBMInformix,OLE_DB_Data,DAProgressOpenEdge,DAOracle,SybaseAnywhere,DASybase,SybaseASE,SybaseIQ,SymantecACT,DANCRTeradata,TextDA,Btrieve,CharacterSeparated,ExportSupport,ExpDiskFile,ExpRichTextFormat,ExpWordforWindows,PDF,ExpText,ExpExcel,ExpCrystalReports,XMLExport,LegacyXMLExport,SamplesEN,UserHelp,LanguagePackCostingFeatureen,LanguagePackCostingFeature,


10Client Tools InstallationClient Tools silent installations

LanguagePackCostingFeaturenl"ADDSOURCE=""ADVERTISE=""

This script can now be used for future silent installations by including the filename and path in the command line as shown below:setup.exe -r FILEPATH


Client Tools Installation10 Client Tools silent installations

Maintaining your Installation

11

BusinessObjects Enterprisemaintenanceoperations

You can perform three maintenance operations on your installation ofBusinessObjects Enterprise:

• Modify: this operation will identify the current components installed onyour system. Using the "Select Feature" screen you can add or removecomponents from your current installation.

• Repair: this operation replaces missing or corrupt files, registry keys, andshortcuts. Preferences in the registry are restored to default values.

• Remove: this operation uninstalls BusinessObjects Enterprise. Alllanguage packs and patches will also be removed.

To enter maintenance mode

There are two methods for evoking maintenance mode for BusinessObjectsEnterprise on Windows:

1. Go to Start > Settings > Control Panel > Add or Remove Programs.a. Select BusinessObjects Enterprise XI 3.0.b. Click Change.

The "Application Maintenance" screen is displayed.


Maintaining your Installation11 BusinessObjects Enterprise maintenance operations

2. Alternatively, you can run the setup.exe program you originally used toinstall your current BusinessObjects Enterprise product.

Uninstalling BusinessObjects EnterprisefromWindows

It is recommended that you back up reports, documents and systeminformation before uninstalling BusinessObjects Enterprise. For moreinformation on backing up your system see “Managing and ConfiguringServers” in the BusinessObjects Enterprise Administrator's Guide.

To uninstall BusinessObjects Enterprise from your system:

1. Go to Start > Programs > BusinessObjects XI 3.0 > BusinessObjectsEnterprise > Central Configuration Manager.The CCM console is displayed.

2. Right-click to highlight all listed servers and select Stop.For more information on stopping servers see “Managing and ConfiguringServers” in the BusinessObjects Enterprise Administrator's Guide. .


11Maintaining your InstallationUninstalling BusinessObjects Enterprise from Windows

3. Go to Start > Settings > Control Panel > Add or Remove Programs.4. Select BusinessObjects Enterprise XI 3.0.5. Click Remove.

The "Add or Remove Programs" dialog prompts to confirm that you wantto remove BusinessObjects Enterprise XI 3.0.

6. Click Yes.

Please wait while files are removed and your system is reconfigured. Youare prompted once the configuration process is complete.

7. Click Finish.

Your BusinessObjects Enterprise installation may have included an installationof the Apache Tomcat java application server. By default, Tomcat installs toC:\Program Files\BusinessObjects\Tomcat\. When BusinessObjectsEnterprise is uninstalled; the contents of the Tomcat subfolder are removed.

Note: Only web applications deployed on a Tomcat server installed throughthe BusinessObjects Enterprise installer are automatically removed. You willmanually have to remove web applications deployed on other servers.

The installer removes only the files that it originally installed. Folders or filescreated after the installation, for example log or report files, are not uninstalledby the uninstallation process.

Silent uninstallation

If the installation source is available, you can use the command-line consoleto unistall BusinessObjects Enterprise. In the command-line specify thefollowing method:setup.exe REMOVE=ALL

Software Inventory Tool

Introduction

The BusinessObjects Enterprise Software Inventory Tool is a Java-basedmaintenance tool available to administrators of BusinessObjects Enterprise.


Maintaining your Installation11 Software Inventory Tool

The tool creates and maintains an inventory of all changes made to BusinessObjects software via Business Objects installers and allows users to viewthese changes.

What does the BusinessObjects Software Inventory Tool do?

The Business Objects Software Inventory Tool collects and displaysinformation on your BusinessObjects installations.

The tool monitors BusinessObjects Enterprise after it is installed and logsupdates such as critical hot fixes and service packs. The logged informationis presented chronologically using various formats and views. The inventorylist can then be queried for specific files, features, and patches.

Installation

The BusinessObjects Software Inventory Tool is automatically bundledtogether with your BusinessObjects XI 3.0 installation. It is available for allWindows platforms supported by BusinessObjects XI 3.0. See the ProductsAvailability Report PDF which can be accessed at http://support.businessobjects.com/documentation/supported_platforms/default.asp.

The SoftwareInventory.bat and SoftwareInventory.jar.files are bydefault installed to the following directory C:\Program Files\BusinessObjects\common\4.0\java\lib. Once the program is launched, the inventory.xml and log.txt files are created in the same folder.

How does the BusinessObjects Software InventoryTool work?

When a Business Objects installer is run, the tool is automatically evoked.Information on what is being installed is added to the inventory.xml file.The inventory contains the following information:

• A record of all Business Objects installations including original productand service packs, and critical hot fixes.

• Records of all the fixes that were installed on the system.


11Maintaining your InstallationSoftware Inventory Tool

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

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

• Records of the files that are associated with each Business Objectsinstallation such as WAR files and DLLs.

Launching the BusinessObjects Software Inventory Tool

The BusinessObjects Software Inventory Tool is installed by default into theC:\Program Files\Business Objects\common\4.0\java\lib folder.

• To launch the tool, either:Go to Start/Programs/BusinessObjects XI 3.0/BusinessObjects/Enterpriseand double-click the Software Inventory Tool icon.ORDouble-click the SoftwareInventory.bat file which is located by default inthe C:\Program Files\Business Objects\common\4.0\java\libfolder. This launches a Windows Command window and starts the Javaprogram.

OR

1. From the Start\Run command line - type cmd and click OK. Thislaunches a Windows Command window.

2. Navigate to the folder in which the tool is installed (the default isC:\Program Files\Business Objects\common\4.0\java\lib).

3. At the prompt type:"C:\Program Files\Business Objects\javasdk\bin\java" -Djava.library.path=.\external -Xmx256M -jar "C:\ProgramFiles\BusinessObjects\common\4.0\java\lib\softwareInventory.jar" gui

This command uses the Java implementation installed withBusinessObjects Enterprise and provides Java configurationinformation.

Note: Closing the Windows Command window will terminate the Javaprogram.

Using the BusinessObjects Software Inventory Tool

Once the BusinessObjects Software Inventory Tool is launched it displaysthree separate panes for information on :



• Viewing Format

• History View

• Search

The Viewing Format AreaThe Viewing format pane provides three options for what to display.

• Install/Patch name

This option displays all the available information logged by the tool inchronological order.

• ADAPT number

This option only displays the ADAPT numbers for modifications loggedby the tool.

Note: ADAPT numbers are only displayed if critical hot fixes have beeninstalled. ADAPT is the system used internally by Business Objects totrack technical problems and feature enhancements.

• File

This option only displays files that have been installed and recorded bythe tool.

History ViewThe History View is divided into two parts:

• History Tree• Node Details

History Tree and the Node Details

The History Tree is the main pane used to navigate the inventory. Thehistory of installations and changes is listed chronologically; each entry canbe expanded to display further details in the Node Details pane.

Note: To view more specific information you can use the Search function.


11Maintaining your InstallationSoftware Inventory Tool

The type of information displayed in Node Details includes :

• Name of the product• Version or Build number• Date and time of installation• Path locations

The following table summarizes the detail displayed in the History View areadepending on the selected Viewing Format:

History View DetailViewing Format

Build number

Install/Patch Name of the product

Installation or Removal timestamp

List of all features installed

List of all files installed

Installed or Removed

List of all ADAPT records (not for Ser-vice Packs)

ADAPT number /ID

ADAPT NumberProblem Summary

Fix description

List of updated files

Name of the file

File

Full path location of the file

Version (if available)

Build

History of changes to the file



The Search paneThe Search pane of the BusinessObjects Software Inventory Tool allowsyou to refine the information displayed in History View. It is divided intothree parts:• Enter search string: use this field to enter a string. A new tree is

generated based on the search result and the current view being used.• Search History: lists all the search parameters.• Clear search history: click to clear the Search History.

The Software Inventory log fileThe tool creates a log file for recording each time the tool is launched.

The log.txt file is saved in the default installation folder together with theinventory.xml file: C:\Program Files\BusinessObjects\common\4.0\java\lib

The installation log fileThe installation log file contains information on all the parameter settingsused in a BusinessObjects Enterprise installation. The log file can be usedas a reference or to troubleshoot installation errors. The name of the initiallog file is BOEInstall_0.log and it is saved under the following directory:<INSTALLDIR>\BusinessObjects Enterprise 12.0\Logging. Each timeyou run the BusinessObjects Enterprise installer, a new log file is generated.For example after the initial installation you choose run the “Modify”maintenance operation. Once the process is completed, BOEInstall_1.logis stored in the Logging directory.

Information specific to web application deployment is also included in thelog file.


11Maintaining your InstallationThe installation log file


Maintaining your Installation11 The installation log file

Post Installation WebApplication Deployment

12

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 Deployment12 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.bat thefolder contains all the required configuration files for running the tool.


12Post 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 allthe required 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• Minimum user rights for deploying web applications on page 18• To deploy web applications on a remote machine on page 194

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 Deployment12 Deploying with wdeploy

http://support.businessobjects.com

How to use wdeploy

To use wdeploy , the specific configuration file for your web applicationserver must 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.


12Post Installation Web Application DeploymentDeploying with wdeploy

Required Configuration detailsWeb applicationserver

• as_admin_port: The SOAP Connector Port of the ap-plication server (for example "8880").

• as_admin_username: WebSphere administrator ac-count username (for example "administrator").

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

• as_admin_password: WebSphere administrator ac-count password (for example "password").

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

• as_instance: The name of your WebSphere applicationserver instance (for example "server1").

• as_virtual_host: The virtual host to which the applica-tion must be bound (for example "default_host").

• as_admin_is_secure: Instructs wdeploy that Web-Sphere security is enabled (for example "false").

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

• as_dir: WebSphere installation directory (for example"C:\Program Files\IBM\WebSphere\AppServer").

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

• enforce_file_limit: Indicates to wdeploy whether ornot the web application server may encounter issuesloading applications that contain more than 65 535 files("True" by default).

WebSphere 6.1




• as_admin_port: Administration port of the applicationserver (for example "7001").

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

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

• as_instance: The name of your WebLogic applicationserver instance (for example "AdminServer").

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

WebLogic 10

• as_admin_port: Administration port of the applicationserver (for example "7001").

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

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

• as_instance: The name of your WebLogic applicationserver instance (for example "AdminServer").

• as_dir: Weblogic domain directory (for example"C:\bea\user_projects\domains\base_domain").

WebLogic 9.2




• as_instance : Name of the web application server in-stance currently used (for example "localhost").

• as_service_name : The name of the Windows service(when the application server is installed as a Windowsservice) (for example "Tomcat5").

• as_dir : Installation directory of the web applicationserver (for example "C:\wdeploy\appserver\Tom-cat5520").

• as_service_key: Name of the Windows registry keyused by Tomcat to specify Java parameters (for exam-ple "HKLM\SOFTWARE\Apache Software Founda-tion\Procrun 2.0\$as_service_name\Parameters\Java").

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

Tomcat 5.5

• as_dir: The location of your application server (for ex-ample "C:\Program Files\SAP").

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

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

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

• as_admin_username: the administrator username (forexample "Administrator").

• as_admin_password: the administrator password (forexample "password").

SAP ApplicationServer 7.0




• as_admin_port: Administration port of the applicationserver. This is the request port of the notification server,found in the <notification-server> section ofconfiguration file opmn.xml (for example "6003").

• as_admin_username: Oracle Application Server ad-ministrator account username (for example "ocjadmin").

• as_admin_password: Oracle Application Server ad-ministrator account password (for example "oracle10g").

• as_instance: The name of your Oracle ApplicationServer application server instance (for example "home").

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

Note: If as_admin_is_secure is not enabled, you willstill have to specify the username and password to ac-cess the server.

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

• as_appserver_name: Name of the target applicationserver (for example "oracle10g.BO-AMIT.product.busi-nessobjects.com").

• as_group_id: Name of the server group to which thetarget application belongs (for example "De-fault_group").

Oracle ApplicationServer 10 G R3

• as_dir: The location of the JBoss application server(for example "C:\Program Files\jboss-4.0.4.GA").

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

JBoss 4

Note:



Run the wdeploy script by opening command line console and typing thefollowing:<INSTALLDIR>\deployment\wdeploy.bat

<appserver> deployall >> <logfilename>.log

For example:wdeploy.bat weblogic9 deployall >> C:\mylog.log

Note: The <appserver> must be same as the web application server usedin the configuration filename (for example, config.weblogic9).

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

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

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

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 web application to <INSTALLDIR>\deployment\workdir\WebAppServer_VERSION, 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 WebSphere.wdeploy.bat websphere6-Das_dir=C:\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.bat websphere6-Das_dir=C:\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.bat websphere6-Das_dir=C:\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.bat websphere6-Das_dir=C:\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.bat websphere6-Das_dir=C:\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.bat websphere6-Das_dir=C:\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.bat websphere6-Das_dir=C:\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.bat websphere6-Das_dir=C:\IBM\WebSphere\AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_admin_port=8880undeployall



Related Topics• After deploying web applications on page 204

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=C:\Program Files\Apache Software Foundation\Apache2.2connector_type=websphere6deployment_dir=C:\Program Files\Apache Software Foundation\Apache 2.2\htdocs

• Edit config.websphere6. For example:#Business Objects Configuration Utilityas_admin_port=8880as_admin_username=adminas_admin_password=passwordas_dir=C:\Program Files\IBM\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.bat 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.bat 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.bat 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 159• To deploy web applications on a remote machine on page 194

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\WebAppServer_VERSION, but does notdeploy the web application to the web application server. The predeployall

command performs the predeploy command for all web applications.

Example 1: using wdeploy predeploy to predeploy InfoView to WebLogic.wdeploy.bat weblogic9-Das_dir=C:\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.bat weblogic10-Das_dir=C:\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.bat weblogic9-Das_dir=C:\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.bat weblogic10-Das_dir=C:\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.bat weblogic9-Das_dir=C:\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.bat weblogic10-Das_dir=C:\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.bat weblogic9-Das_dir=C:\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.bat weblogic10-Das_dir=C:\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 the



web 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=C:\bea\user_projects\domains\base_domain

• Edit config.apache. For example:#Business Objects Configuration Utilityws_dir=C:\Webserver\Apache224connector_type=weblogic9deployment_dir=C:\Webserver\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.bat 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.bat weblogic9 -Das_mode=distributed





If Apache and WebLogic are on different machines, dynamic content willbe automatically deployed to WebLogic by the following command. Staticcontent must be manually deployed to the remote Apache machineafterwards.wdeploy.bat weblogic9 -Das_mode=distributed

-predeployall >> wdeploy.log



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



STALLDIR>\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 InfoView to Tomcat.wdeploy.bat tomcat55-Das_dir=C:\Tomcat5-Das_instance=localhost-Das_service_name=Tomcat5-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto Tomcat.wdeploy.bat tomcat55-Das_dir=C:\Tomcat5-Das_instance=localhost-Das_service_name=Tomcat5predeployall




Example 1: using wdeploy deployonly to deploy a InfoView to Tomcat.wdeploy.bat tomcat55-Das_dir=C:\Tomcat5-Das_instance=localhost-Das_service_name=Tomcat5-DAPP=InfoViewAppdeployonly

Example 2: using wdeploy deployonlyall to deploy all predeployed webapplications to Tomcat.wdeploy.bat tomcat55-Das_dir=C:\Tomcat5-Das_instance=localhost-Das_service_name=Tomcat5deployonlyall






Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toTomcat.wdeploy.bat tomcat55-Das_dir=C:\Tomcat5-Das_instance=localhost-Das_service_name=Tomcat5-DAPP=InfoViewAppdeploy

Example 2: using wdeploy deployall to predeploy, then deploy, all webapplications to Tomcat.wdeploy.bat tomcat55-Das_dir=C:\Tomcat5-Das_instance=localhost-Das_service_name=Tomcat5deployall



Example 1: using wdeploy undeploy to undeploy InfoView from Tomcat.wdeploy.bat tomcat55-Das_dir=C:\Tomcat5-Das_instance=localhost-DAPP=InfoViewApp-Das_service_name=Tomcat5undeploy



Example 2: using wdeploy undeployall to undeploy all web applicationsfrom Tomcat.wdeploy.bat tomcat55-Das_dir=C:\Tomcat5-Das_instance=localhost-Das_service_name=Tomcat5undeployall


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 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 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 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 Tomcat are located in<INSTALLDIR>\deployment.• Edit config.tomcat55. For example:

#Business Objects Configuration Utilityas_dir=C:\Appserver\Tomcat5520as_instance=localhostas_service_name=Tomcat5as_service_key=HKLM\SOFTWARE\Apache Software Foundation\

Procrun 2.0\Tomcat5\Parameters\Javaas_service_key_value=Options

• Edit config.apache. For example:#Business Objects Configuration Utilityws_dir=C:\Webserver\Apache224connector_type=tomcat55deployment_dir=C:\Webserver\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 Apacheweb server.wdeploy.bat 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.bat tomcat55 -Das_mode=distributed



If Apache and Tomcat are on different machines, dynamic content willbe automatically deployed to Tomcat by the following command. Staticcontent must be manually deployed to the remote Apache machineafterwards.wdeploy.bat tomcat55 -Das_mode=distributed

-deployonlyall >> wdeploy.log



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.bat oas1013-Das_dir=C:\Oracle10gASR3\OracleAS_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6003-Das_admin_username=oc4jadmin-Das_admin_password=oracle12-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto Oracle Application Server.wdeploy.bat oas1013-Das_dir=C:\Oracle10gASR3\OracleAS_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6003-Das_admin_username=oc4jadmin-Das_admin_password=oracle12predeployall






Example 1: using wdeploy deployonly to deploy a predeployed InfoViewto Oracle Application Server.wdeploy.bat oas1013-Das_dir=C:\Oracle10gASR3\OracleAS_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6003-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.bat oas1013-Das_dir=C:\Oracle10gASR3\OracleAS_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6003-Das_admin_username=oc4jadmin-Das_admin_password=oracle12deployonlyall




Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toOracle Application Server.wdeploy.bat oas1013-Das_dir=C:\Oracle10gASR3\OracleAS_1



-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6003-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.bat oas1013-Das_dir=C:\Oracle10gASR3\OracleAS_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6003-Das_admin_username=oc4jadmin-Das_admin_password=oracle12deployall



Example 1: using wdeploy undeploy to undeploy InfoView from OracleApplication Server.wdeploy.bat oas1013-Das_dir=C:\Oracle10gASR3\OracleAS_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6003-Das_admin_username=oc4jadmin-Das_admin_password=oracle12-DAPP=InfoViewAppundeploy

Example 2: using wdeploy undeployall to undeploy all web applicationsfrom Oracle Application Server.wdeploy.bat oas1013-Das_dir=C:\Oracle10gASR3\OracleAS_1-Das_instance=home-Das_appserver_name=oc4j_inst1



-Das_group_id=default_group-Das_admin_port=6003-Das_admin_username=oc4jadmin-Das_admin_password=oracle12undeployall


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 <INSTALLDIR>\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.bat nw2004-Das_dir=C:\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.bat nw2004-Das_dir=C:\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.bat nw2004-Das_dir=C:\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.bat nw2004-Das_dir=C:\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.bat nw2004-Das_dir=C:\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.bat nw2004-Das_dir=C:\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.bat nw2004-Das_dir=C:\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.bat nw2004-Das_dir=C:\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.bat jboss404-Das_dir=C:\jboss-4.0.4.GA-Das_instance=default-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto JBoss.wdeploy.bat jboss404-Das_dir=C:\jboss-4.0.4.GA



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

-Das_instance=defaultpredeployall




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

Example 2: using wdeploy deployonlyall to deploy all predeployed webapplications to JBoss.wdeploy.bat jboss404-Das_dir=C:\jboss-4.0.4.GA-Das_instance=defaultdeployonlyall




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



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



Example 1: using wdeploy undeploy to undeploy InfoView from JBoss.wdeploy.bat jboss404-Das_dir=C:\jboss-4.0.4.GA-Das_instance=default-DAPP=InfoViewAppundeploy

Example 2: using wdeploy undeployall to undeploy all web applicationsfrom JBoss.wdeploy.bat jboss404-Das_dir=C:\jboss-4.0.4.GA-Das_instance=defaultundeployall


Deploying to WebSphere Community Edition with wdeploy


The predeploy command creates resources and configuration files for aspecific web application, then copies the WAR application to <INSTALLDIR>\deployment\workdir\wasce20, 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 WebSphereCommunity Edition.wdeploy.bat wasce20-Das_dir=C:\Program Files\ibm\WebSphere\AppServerCommunityEdi

tion-Das_instance=server1-Das_admin_port=1099-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto WebSphere Community Edition.wdeploy.bat wasce20-Das_dir=C:\Program Files\ibm\WebSphere\AppServerCommunityEdi

tion-Das_instance=server1-Das_admin_port=1099predeployall




Example 1: using wdeploy deployonly to deploy a predeployed InfoViewto WebSphere Community Edition.wdeploy.bat wasce20-Das_dir=C:\Program Files\ibm\WebSphere\AppServerCommunityEdi

tion-Das_instance=server1-Das_admin_port=1099-DAPP=InfoViewAppdeployonly

Example 2: using wdeploy deployonlyall to deploy all predeployed webapplications to WebSphere Community Edition.wdeploy.bat wasce20-Das_dir=C:\Program Files\ibm\WebSphere\AppServerCommunityEdi

tion-Das_instance=server1-Das_admin_port=1099deployonlyall






Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toWebSphere Community Edition.wdeploy.bat wasce20-Das_dir=C:\Program Files\ibm\WebSphere\AppServerCommunityEdi

tion-Das_instance=server1-Das_admin_port=1099-DAPP=InfoViewAppdeploy

Example 2: using wdeploy deployall to predeploy, then deploy, all webapplications to WebSphere Community Edition.wdeploy.bat wasce20-Das_dir=C:\Program Files\ibm\WebSphere\AppServerCommunityEdi

tion-Das_instance=server1-Das_admin_port=1099deployall



Example 1: using wdeploy undeploy to undeploy InfoView from WebSphereCommunity Edition.wdeploy.bat wasce20-Das_dir=C:\Program Files\ibm\WebSphere\AppServerCommunityEdi

tion-Das_instance=server1-Das_admin_port=1099-DAPP=InfoViewAppundeploy



Example 2: using wdeploy undeployall to undeploy all web applicationsfrom WebSphere Community Edition.wdeploy.bat wasce20-Das_dir=C:\Program Files\ibm\WebSphere\AppServerCommunityEdi

tion-Das_instance=server1-Das_admin_port=1099undeployall


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 wdeploy folder will contain the

wdeploy scripts and configuration files.• <INSTALLDIR>\BusinessObjects Enterprise

12.0\java\applications\

• <INSTALLDIR>\Performance Management 12.0\

• <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>\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>\BusinessObjectsEnterprise 12.0\java\applications

• From <INSTALLDIR>\Performance Management 12.0\ 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 war filedirectory 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=C:\Program Files\Business Objects\BusinessObjects Enterprise12.0\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=C:\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>\BusinessObjects Enterprise12.0\java\applications\

b. Set the af.configdir parameter in theweb.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>C:\Performance Management 12.0</param-value>

</context-param>

c. Repackage PerformanceManagement.war.

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

<appserver> deployall -Dwar_dir=“<INSTALLDIR>\BusinessObjects Enterprise 12.0\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 159• Prerequisites for using wdeploy on page 157



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


12Post 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 Deployment12 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.bat tomcat55-Das_dir=C:\Tomcat5520-Das_instance=localhost-Das_service_name=Tomcat55-DAPP=InfoViewApppredeploy



Example 2: using wdeploy predeployall to prepare all web applicationsfor deployment to Tomcat.wdeploy.bat tomcat55-Das_dir=C:\Tomcat5520-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 157• How to use wdeploy on page 159• Minimum user rights for deploying web applications on page 18• To prepare for manual deployment on a remote machine on page 201• Minimum user 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 wdeploy folder will contain thewdeploy scripts and configuration files.

•

• <INSTALLDIR>\BusinessObjects Enterprise12.0\java\applications\

• <INSTALLDIR>\Performance Management 12.0\

• <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>\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>\BusinessObjectsEnterprise 12.0\java\applications

• From <INSTALLDIR>\Performance Management 12.0\ 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 war filedirectory 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=C:\Program Files\Business Objects\BusinessObjects Enterprise12.0\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=C:\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>\BusinessObjects Enterprise12.0\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>C:\Performance Management 12.0</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.bat

<appserver> predeployall -Dwar_dir=“<INSTALLDIR>\BusinessObjects Enterprise 12.0\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 159• Prerequisites for using wdeploy on page 157

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, click

Enterprise 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 runs 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 12.0\ to each managedserver and ensure the file path of InitConfig.properties is matches thevalue specified for af.configdir param in web.xml in PerformanceManagement.war as shown below:<context-param>

<param-name>af.configdir</param-name><param-value>C:\Program Files\BusniessObjects\Per

formance Management 12.0</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=C:\Program Files\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:C:\Program Files\Business Objects\deployment>wdeploy.bat 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 5-7 for each EAR file you want to install.9. Go toSystem 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 194

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

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 12.0\ to each managedserver and ensure the file path of InitConfig.properties is matches thevalue specified for af.configdir param in web.xml in PerformanceManagement.war as shown below:<context-param>

<param-name>af.configdir</param-name><param-value>C:\Program Files\BusniessObjects\Per

formance Management 12.0</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=c:\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:C:\Program Files\Business Objects\deployment>wdeploy.bat 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" is complete, select all the installedapplications and go to Start > Servicing all requests.

Example:

“Deploying the complex deployment scenario” in this manual includes astep-by-step description of how to deploy web applications to a WebLogic10 cluster.

Related Topics• To deploy the WAR files to WebLogic 10 on page 272• To prepare the WAR files for deployment on page 271

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 theContext 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 theNext 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:• 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.



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

1. Start the "Visual Administrator" tool by running go.bat from<SAP_HOME>\sap\J2E\JC01\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 J2E 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.


Deployingwith theWebSphereCommunity Edition administrativeconsole

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

Note: Thewdeploy 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:

<INSTALLDIR>\BusinessObjects Enterprise 12.0\java\applications

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 find



org.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>\BusinessObjects Enterprise 12.0\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

13

Overview of deployment scenariosTo improve your experience in installing and deploying BusinessObjectsEnterprise this section provides three sample scenarios. These examplesare for illustrative purposes. Each example includes a deployment diagram,key tasks, key configuration details, functional requirements andpre-conditions. The three scenarios focus on three deployment characteristics:

• Desktop client to server• Basic n-tier• Complex deployment

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

Windows Server 2003 SP2 EnterpriseEdition

Installation platform for BusinessObjects Enterprise


Deployment Scenarios13 Overview of deployment scenarios

Microsoft SQL Server 2005Database for Central Management Server (CMS)

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.


13Deployment ScenariosDesktop client to server scenario

Deploying the desktop client to server scenario

To set up the data tier

This scenario calls for Microsoft SQL Server 2005 running on a supportedMicrosoft Windows operating system. Advanced administrative knowledgeof Microsoft SQL Server 2005 and Microsoft Windows products is assumed.

Install a version of Microsoft Windows with the appropriate service packsand updates required by Microsoft SQL Server 2005. If your CMS anddatabase servers are installed on separate computers, ensure that you havea working network connection between the machines.1. Install Microsoft SQL Server 2005.

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_sqlName of database server instance

saAdministrator account name

passwordAdministrator account password

UTF-8Database character set encoding

Microsoft SQL Server 2005 is now installed and ready to be used byBusinessObjects Enterprise.

2. Create or import a new database 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

BOE120CMS database name

bobjuserUsername for CMS database access

mypasswordPassword for CMS database access


Deployment Scenarios13 Desktop client to server scenario

A CMS database is now available for use.

3. Set up a DSN database connection on the machine hosting the CMS.On each system that needs to access the database, create a SystemDSN entry in the Microsoft Windows"ODBC Data Source Administrator"Control Panel tool. Enter the settings you used when you created thedatabase above. Use Control Panel > Administrative Tools > DataSources (ODBC) > System DSN > Add....The server hosting the CMS is now able to communicate with the newlycreated Microsoft SQL Server 2005 database.

You have set up the machine running the CMS with a database connection.The default listener port number used by SQL Server is 1433. The databaseport number must be entered during the BusinessObjects Enterpriseinstallation.

Verify the network connectivity between the server hosting the CMS and thedatabase server by attempting to connect to the database from the serverhosting the CMS. This can be done from the Control Panel in MicrosoftWindows under Control Panel > Administrative Tools > Data Sources(ODBC) > System DSN > BOE120 > Configure > Next > Next.

Note: This scenario does not include a network firewall between the CMSand database servers.

Remember: The ability to connect to your database server may require achange to the Windows Firewall settings on both machines.

To set up the server tier - framework servers

Windows Server 2003 SP2 Enterprise Edition has to be installed and running.You need administrative privileges on both machines that will host theBusinessObjects Enterprise server components. Designate a machine asSERVER 1 on which you will install framework servers. Designate secondmachine, SERVER 2, on which you will install all other server components.

Follow the instructions below to install the framework servers.1. Run setup.exe from the root directory of your product distribution.

The "Please Choose Setup Language" dialog is displayed.

2. Select your 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.

3. Click Next.The "License Agreement" screen is displayed.

4. Select I accept the License Agreement and click Next.The "User Information" screen is displayed.

5. Enter the requested information for Full Name, Organization, andProduct Keycode. Click Next.The "Choose Language Packs" screen is displayed.

6. Select any Language Packs you want to install. Click Next.


The "Install Type" screen is displayed

7. Left-click on the icon beside Server Components and select Entirefeature will be unavailable.

8. Choose Custom or Expand install.The "Select Features" screen is displayed.

9. Left-click on the icon beside Web Tier Components and select Entirefeature will be installed on local hard drive.

10. Left-click on the icon beside Client Components and select Entirefeature will be unavailable.

The Client Components icon changes to .

11. Expand Server Components.a. Left-click on the icon beside Central Configuration Manager and

select Entire feature will be installed on local hard drive.b. Left-click on the icon beside Central Management Server and select

Will be installed on local hard drive.The Central Management Server option will be installed but not thetwo subfeatures listed under the item: MySQL and Auditing.

c. Left-click on the icon beside Event Server and select Entire featurewill be installed on local hard drive.

d. Left-click on the icon beside Input File Repository Server and selectEntire feature will be installed on local hard drive.

e. Left-click on the icon beside Output File Repository Server andselect Entire feature will be installed on local hard drive.



f. Click Next.The "CMS Clustering" screen is displayed.

12. Select Yes, enter information for the new CMSFields are provided for you to enter and confirm a password for the CMSAdministrator.

13. Enter BOBJ_admin in bothCMSAdministrator Password andConfirmPassword.

14. Click Next.The "Server Intelligence Agent" screen is displayed.

15. Enter SIA_1 in the Node Name field and click Next.The "CMS Database Information" screen is displayed.

16. Select SQL Server (ODBC) from the Select existing CMS databasedrop-down list and click Browse.The "SQL Server Logon" screen is displayed.

17.18. Enter the following SQL Server user information and then click Next.



Select my company database as the data source.a.b. Enter bobjuser as your Login ID and password as your Password.c. Select BOE120 from the Database drop-down list.

d. Click OK.You are returned to the "CMS Database Information" screen.

19. Click Next.The "Start Installation" screen is displayed.

20. Click Next to start the installation.



Click Finish once the following screen is displayed.

Click Finish once the following screen is displayed.

You must now install all remaining BusinessObjects Enterprise servercomponents on SERVER 2.

To add servers to the server tier

You 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. Run setup.exe from the root directory of your product distribution.


Note: If you are installing from a CD and if the Autoplay is enabled foryour CD-ROM drive, the Autorun program will start automatically.







5. Enter the requested information for Full Name, Organization, andProduct Keycode. Click Next.The "Chose Language Packs" screen is displayed.

6. Select any Language Packs you want to install. Click Next.


The "Install Type" screen is displayed






select Entire feature will be unavailable .b. Left-click on the icon beside Central Management Server and select

Entire feature will be unavailable.c. Left-click on the icon beside Event Server and select Entire feature

will be unavailable.d. Left-click on the icon beside Input File Repository Server and select

select Entire feature will be unavailable.e. Left-click on the icon beside Output File Repository Server and

select Entire feature will be unavailable.



After implementing the selections, the "Select Features" screen shouldappear as shown in the following image.

11. Click Next.The "CMS Clustering" screen is displayed.

12. Enter SERVER1 for CMS Host Name, and password in both CMSAdministrator Password and Confirm password.


14. Enter SIA_2 in the Node Name field and click Next.The "Start Installation" screen is displayed.

15. Click Next to start the installation.16. Click Finish once the following screen is displayed.



To assign static port values to servers

Access 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 unsecure 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 anunsecure 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 rootpriviliges. 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.


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



Oracle 10g R2Database for Central Management Server (CMS)

Oracle 10g R3Web application server

Linux iptablesFirewall

Basic n-tier diagram



Deployment Scenarios13 Basic N-tier scenario


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 N-tier scenario


The following steps require that you have already installed a version ofMicrosoft Windows that meets the installation requirements for Oracle 10gR2. Advanced administrative knowledge of Oracle and Microsoft Windowsproducts is assumed.


13Deployment 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 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

BOE120Name of database server

bobjuserAdministrator account name



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.


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

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

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. Install the Oracle database drivers onto all CMS servers, and any clientsthat need direct database access.Your CMS server machines are now able to communicate with your newlycreated Oracle 10g R2 databases.

You have set up CMS, auditing, and performance management databases,as required. You have also installed a file repository server network-shared



directory. 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 the database from the CMS machine(s).

Note: This scenario includes a network firewall between the client browserand web application server. Ensure that this firewall is configuredappropriately.

Remember: The ability to connect to your database server from your CMSserver may require a change to the Windows Firewall settings on bothmachines.

To set up the server tier

Windows Server 2003 SP2 Enterprise Edition has to be installed and runningon the three machines running the server tier. You need administrativeprivileges on the three machines that will host the BusinessObjects Enterpriseservers. Designate the machines SERVER1, SERVER2, and SERVER3.

Follow the instructions below to install all the servers on SERVER1.1. Run setup.exe from the root directory of your product distribution.







6. Select any Language Packs you want to install. Click Next.The "Install Type" screen is displayed



7. Select New and Use an existing database server in the "Install Type"screen. Click Next.The Server Components Configuration screen is displayed.

8. Enter password in both Password and Confirm password. Click Next..The "Server Intelligence Agent" screen is displayed.

9. Enter SIA_1 in Node Name and click Next.The "CMS Database Information" screen is displayed.

10. Select Oracle from the CMS database drop-down list.The "SQL Server Logon" screen is displayed.

11. In the fields provided provide the following configuration for your Oracledatabase:

valueSetting

DBSERVER1_oraServer

mycompanyuserUsername

mypasswordPassword

12. Select Auditing Database and repeat steps 10-11.13. Select the Install Tomcat application server option and click Next.

The "Configure Tomcat" screen is displayed

14. Do not modify any of the values in the input fields and click Next.The "Start Installation" screen is displayed.

15. Click Next to start the installation.The installation process begins and is completed when "BusinessObjectsEnterprise XI 3.0 has been successfully installed" is displayed.

16. Select Launch BusinessObjects Administration Console and clickFinish to exit.A new browser window opens and within a few seconds you are promptedto log into the Central Management Console (CMC).

17. Verify the connectivity between the BusinessObjects CMS and your MSSQL server by logging onto the CMC.a. Type SERVER1 in System.b. Type Administrator in User name .



c. Type password in Password.d. Click Log On to access the CMC.

Accessing the CCM home page, verifies that the BusinessObjectsEnterprise CMS is communicating with the Microsoft SQL Server 2005database server.

You must now install another set of BusinessObjects Enterprise servers onthe machine designated SERVER2.

To add processing servers to clusterYou need to install the framework servers on SERVER 1 before you can addany servers on SERVER2.

Use the following instructions to install BusinessObjects Enterprise serversto SERVER2.1. Run setup.exe from the root directory of your product distribution.



3. Click Next in the "Welcome to the BusinessObjects Enterprise XI 3.0Installation Wizard".The "License Agreement" screen is displayed.











select Entire feature will be unavailable .b. Left-click on the icon beside Event Server and select Entire feature

will be unavailable.c. Left-click on the icon beside Input File Repository Server and select

select Entire feature will be unavailable.d. Left-click on the icon beside Output File Repository Server and

select Entire feature will be unavailable.e. Left-clickDashboard andAnalytics Servers and selectEntire feature

will be unavailable.f. Left-clickCentral Management Server and select Entire feature will

be unavailable. .After implementing the selections, the "Select Features" screen shouldappear as shown in the following image.


12. Enter SERVER1 for CMS Host Name, 6400 for Existing CMS Port, andpassword for CMS Administrator Password.




14. Enter SIA_2 in the Node Name field and click Next.The "Start Installation" screen is displayed.

15. Click Next to start the installation.16. Click Finish once the following screen is displayed.

To add PMC servers to the clusterYou 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 toSERVER3.1. Run setup.exe from the root directory of your product distribution.



3. Click Next in the "Welcome to the BusinessObjects Enterprise XI 3.0Installation Wizard".



The "License Agreement" screen is displayed.








10. Left-click on the icon beside Server Components and select Entirefeature will be unavailable.

11. Expand Server Components. Left-click Dashboard and AnalyticsServers and select Entire feature will be installed on local hard drive.


13. Enter SERVER1 for CMS Host Name, 6400 for Existing CMS Port, andpassword for CMS Administrator Password.


15. Enter SIA_3 in the Node Name field and click Next.16. Select Oracle from the CMS database drop-down list.

The "SQL Server Logon" screen is displayed.

17. Select Auditing Database and repeat steps 10-11.18. Click Next to start the installation.19. Click Finish once the following screen is displayed.



To set up the web tier

You need to install and configure Oracle Application Server 10g R3 on amachine running Windows Server 2003 SP2 Enterprise Edition. To configurethe application use the following setup parameters.

valueSetup parameter

8080Port

adminUsername

oraclePassword

WEBSERVER1Server Instance

c:\product\10.1.3\Oracle_AS1Installation Directory

Use the following steps to install the web applications to the“managedserver1” machine.



1. Run setup.exe from the root directory of your product distribution.The "Please Choose Setup Language" dialog is displayed.



3. Click Next in the "Welcome to the BusinessObjects Enterprise XI 3.0Installation Wizard".The "License Agreement" screen is displayed.




7. Choose Web Tier and click Next .The "Select Features" screen is displayed.

8. Expand Web Tier Components.9. Left-click on the icon beside Tomcat and select Entire Feature will be

unavailable. Click Next.The "CMS Clustering" screen is displayed.

10. Type SERVER1 for Existing CMS Hostname, 6400 for Existing CMSPort, and password for CMS Administrator Password. Click Next.



The "Select Web Application Server" screen is displayed.

11. Choose Oracle Application Server 10g R3 from list of supported webapplication servers and click Next.



The "Configure Web Application Server" screen is displayed.

12. Type 8080 for Port, admin for Username, password for Password, andWEBSERVER1 for Server Instance.



13. Click Next twice to start the installation.The installation process begins and is completed when "BusinessObjectsEnterprise XI 3.0 has been successfully installed" is displayed.

14. Click Finish to exit.


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 unsecure network, such as the internet.


The following steps illustrate how to forward requests from clients on anunsecure 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.





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 theWebService URL and System fields.

8. Select the Enterprise authentication method from the drop-down list,click Log On and then click OK.

Complex deployment scenario

Complex deployment overview

The following scenario illustrates an end to end scenario which combinessplit web and server tiers. The web tier contains a load balancer and clusteredweb applications clustered on two separate machines. The server tiercomprises clustered Central Management (CMS) and File Repository servers,and multiple instances of the remaining servers clustered on two separatemachines..

System layers

• Data Tier: contains databases used by the CMS and File Repositoryservers.

• Server Tier: all BusinessObjects Enterprise servers installed on twomachine running as a cluster.

• Web Tier: two web application servers installed on separate machinesrunning as a cluster with fail- over support through load balancer.

• Client Tier: a browser used to log into Central Management Console(CMC).

Configuration details



Microsoft SQL Server 2005Database for Central Management Server (CMS)

WebLogic 10Web application server

Cisco CSS 11500 series load bal-ancer

Load balancer


Deployment Scenarios13 Complex deployment scenario

Linux iptables running on Red HatLinux with two network interface cards(NIC)

Firewall

Complex deployment diagram



The complex 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. Configuring the load balancer5. Setting up the firewall6. Setting up the client tier


13Deployment ScenariosComplex deployment scenario

Deploying the complex deployment scenario


This scenario calls for Microsoft SQL Server 2005 running on a supportedMicrosoft Windows operating system. In the examples below, this databasesystem is named DBSERVER1.

Install a version of Microsoft Windows with the appropriate service packsand updates required by Microsoft SQL Server 2005. If your CMS anddatabase servers are installed on separate computers, ensure that you havea working network connection between the machines.1. Install Microsoft SQL Server 2005.

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_sqlName of database server instance

saAdministrator account name



Microsoft SQL Server 2005 is now installed and ready to be used byBusinessObjects Enterprise.

2. Create or import a new database for the CMS, as well as auditing orPerformance Management databases if required.Record the settings used for creating of the CMS database.


BOE120CMS database name

bobjuserUsername for CMS database access

mypasswordPassword for CMS database access



A CMS database is now available for use.

3. Create or import a new database for auditing database, if required.Record the settings used for creating of the auditing database.

ExampleAuditing database setting

bobjauditAuditing database name

audituserUsername for auditing database access

auditpasswordPassword for auditing database access

An auditing database is now available for use.

4. Create or import a new database for Performance Management database,if required.Record the settings used for creating of the Performance Managementdatabase.

ExamplePerformance Management database setting

bobjpmPerformance Management database name

pmuserUsername for PM database access

pmpasswordPassword for PM database access

A Performance Management database is now available for use.

5. Set up a DSN database connection on the BusinessObjects EnterpriseCMS and any clients that need direct database access.On each system that needs to access the database, create a SystemDSN entry in the Microsoft "ODBC Data Source Administrator" ControlPanel tool. Enter the settings you used when you created the database(s)above.Your CMS server are now able to communicate with your newly createdMicrosoft SQL Server 2005 databases.

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 SQL Server is 1433. 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) afterinstalling BusinessObjects Enterprise.

Note: This scenario does not include a network firewall between the CMSand database servers.

Remember: The ability to connect to your database server from your CMSserver may require a change to the Windows Firewall settings on bothmachines.

To set up the server tier

Windows Server 2003 SP2 Enterprise Edition has to be installed and running.You need administrative privileges on both machines that will host theBusinessObjects Enterprise servers. Designate one machine SERVER1 andthe other SERVER2.

Follow the instructions below to install all the servers on SERVER1.1. Run setup.exe from the root directory of your product distribution.








7. Select New and Use an existing database server in the "Install Type"screen. Click Next.The Server Components Configuration screen is displayed.



8. Enter password in both Password and Confirm password. Click Next..The "Server Intelligence Agent" screen is displayed.

9. Enter SIA_1 in Node Name and click Next.The "CMS Database Information" screen is displayed.

10. Select SQL Server (ODBC) from the CMS database drop-down list andclick Browse.The "SQL Server Logon" screen is displayed.

11. Input your Microsoft SQL Server user credentials through thepreconfigured ODBC DSN.a. Selectmy company database from the list underData Source Name.b. Enter bobjuser and paword in the Login ID and Password fields.c. Select BOE120 from the list under Database.

d. Click OK to validate and save your user credential information.The "CMS Database Information" screen is once again displayed.

12. Select Auditing Database and repeat steps 10-11 to configure usercredentials through the ODBC DSN for the auditing database. WhenODBC DSN is displayed in the "CMS Database Information" screen clickNext.




13. Select the Install Tomcat application server option and click Next.The "Configure Tomcat" screen is displayed

14. Do not modify any of the values in the input fields and click Next.The "Start Installation" screen is displayed.


16. Select Launch BusinessObjects Administration Console and clickFinish to exit.A new browser window opens and within a few seconds you are promptedto log into the Central Management Console (CMC).

17. Verify the connectivity between the BusinessObjects CMS and your MSSQL Server by logging onto the CMC.a. Type SERVER1 in System.b. Type Administrator in User name .c. Type password in Password.d. Click Log On to access the CMC.

Accessing the CCM home page, verifies that the BusinessObjectsEnterprise CMS is communicating with the Microsoft SQL Server 2005database server.

You must now install another set of BusinessObjects Enterprise servers onthe machine designated SERVER2.

To set up a CMS clusterWindows Server 2003 SP2 Enterprise Edition has to be installed and running.You need administrative privileges on the SERVER2 machine.

Follow the instructions below to install BusinessObjects Enterprise servercomponents which will be clustered to the CMS you installed on SERVER1.










7. Choose Custom or Expand and click Next.The "Select Features" screen is displayed.

8. Configure the screen as follows:a. Left-click on the icon beside Client Components and select Entire

feature will be unavailable.b. Left-click on the icon besideWeb Tier Components and select Entire

feature will be unavailable.c. Expand Server Components > Central Management Server.d. Left-click on the icon beside MySQL and select Entire Feature will

be unavailable.e. Left-click on the icon beside Auditor and select Entire Feature will

be unavailable.f. Click Next.

The "CMS Cluster" screen is displayed.

9. Select the If No...option and provide the following configuration detailsa. Type 6401 in New CMS Port.b. Type SERVER1 in Existing CMS Hostname.c. Type 6400 in Existing CMS Port.d. Type password in CMS Administrator Password and click Next.



The "Server Intelligence Agent" screen is displayed.

10. Type SIA_2 in Node Name and 6415 in Port. Click Next.The "CMS Database Information" screen is displayed.

11. Select SQL Server (ODBC) from the CMS database drop-down list andclick Browse.The "SQL Server Logon" screen is displayed.

12. Input your Microsoft SQL Server user credentials through thepreconfigured ODBC DSN.a. Selectmy company database from the list underData Source Name.b. Enter bobjuser and paword in the Login ID and Password fields.c. Select BOE120 from the list under Database.



d. Click OK to validate and save your user credential information.The "CMS Database Information" screen is once again displayed.

13. Select Auditing Database and repeat steps 10-11 to setup configureuser credentials through the ODBC DSN for the auditing database. WhenODBC DSN is displayed in the "CMS Database Information" screen clickNext.The "Start Installation" screen is displayed.



To cluster File Repository serversYou need to create a Filestore folder on SERVER1 in the followingdirectory: C:\Program Files\Business Objects\BusinessObjectsEnterprise 12.0\FileRep. This folder will store data for the File Repositoryservers installed on SERVER1 and SERVER2. The folder must contain twosubfolders: Input and Output. You have to enable sharing for the Filestorefolder and set Full, Change, and Read permissions for Everyone. Name



the shared folder FileRep. You must be logged into the Central ManagementConsole on SERVER1 for the procedure below.

To complete the server tier setup, you must cluster all the File Repositoryservers.


2. Double-click the SIA_1.InputFileRepository entry.The SIA_1.InputFileRepository properties are displayed.

3. Replace the current value in the FileStore Directory field by typingC:\Program Files\Business Objects\BusinessObjects Enterprise12.0\FileRep\Input\ .

4. Click Save.5. Repeat steps 2-3 for the servers listed in the following table and provide

the specific configuration for each server.

FileStore Directory settingServer name

\\Server1\FileRep\Input\SIA_2.InputFil-eRepository

C:\Program Files\Business Objects\BusinessObjectsEnterprise 12.0\FileRep\Output\

SIA_1.OutputFil-eRepository

\\Server1\FileRep\Output\SIA_2.OutputFil-eRepository

The server tier setup is now complete. You should now set up the web tier.

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



Server name

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.


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 prepare your web application servers

Before setting up the BusinessObjects Enterprise web tier you need to installand prepare your web application servers. For this scenario you require twomachines running on Windows Server 2003 SP2 Enterprise Edition.Designate one machine managedserver1 and the other managedserver2.1. Install WebLogic 10 on both managedserver1 and managedserver2 .

For more information consult your WebLogic 10 documentation.

2. Configure the WebLogic 10 server names on each machine according tothe machine name.The server on managedserver1 is called “managedserver1”, and theserver on managedserver2 is called “managedserver2”.

3. Create a cluster on the machine running “managedserver1” with thefollowing settings

ValueSetting

cluster1Cluster name

AdminServerAdministration server

managedserver1

managedserver2

Managed servers

8001AdminServer listen port

7001managedserver1 listen port

7001managedserver2 listen port

weblogicUsername for AdminServer

passwordPassword for AdminServer

For more information on how to create a cluster on WebLogic see yourWebLogic 10 documentation.

4. Create a WebLogic XML Registry for each server using the followingentries:



ValueProperty

BusinessObjectsName

weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl

DocumentBuilder Facto-ry

weblogic.apache.xerces.jaxp.SAXParserFactoryImpl

SAX Parser Factory

weblogic.apache.xalan.processor.TransformerFactoryImpl

Transformer Factory

For more information on WebLogic XML registries see your WebLogic10 documentation.

You can now proceed to install the web applications and setup theBusinessObjects Enterprise web tier.

To install the web applicationsUse the following steps to install the web applications to the“managedserver1” machine.




3. Click Next in the "Welcome to the BusinessObjects Enterprise XI 3.0Installation Wizard" . .The "License Agreement" screen is displayed.






7. Choose Web Tier and click Next .The "Select Features" screen is displayed.

8. Expand Web Tier Components.9. Left-click on the icon beside Tomcat and select Entire Feature will be

unavailable. Click Next.The "CMS Clustering" screen is displayed.

10. Enter the requested information for the CMS on SERVER1 in the fieldsprovided and click Next.

Type SERVER1, 6400, and password. C


11. Choose WebLogic 10 from list of supported web application servers.



12. Select I will manually deploy web components at a later time and clickNext.The "Start Installation" screen is displayed.



The WAR files used to deploy the web applications have to be preparedbefore you can deploy them to your WebLogic 10 cluster.

To prepare the WAR files for deploymentYou need to prepare the WAR files in the BusinessObjects Enterpriseinstallation onmanagedserver1 so that they can be deployed on WebLogic.1. Open the weblogic.xml file which is located in the following directory:

C:\Program Files\Business Objects\deployment\templates\

2. Type in the following information after the <weblogic-web-app> tag:<session-descriptor>

<session-param>



<param-name>PersistentStoreType</param-name><param-value>replicated</param-value>

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

3. Save and close the weblogic.xml file.4. Open the config.weblogic10 file which is located in:

C:\Program Files\Business Objects\deployment\.

5. Modify the file to read as follows:as_dir=c:\bea\user_projects\domains\base_domainas_instance=AdminServeras_admin_port=8001as_admin_username=weblogicas_admin_password=password

6. Save and close the config.weblogic10 file.7. Open a command-line console and run the following command:

C:\Program Files\Business Objects\deployment>wdeploy.bat weblogic10 predeployall

The WAR file have been prepared for deployment and are located in thefollowing directory:

C:\Program Files\BusinessObjects\deployment\workdir\weblogic10\application\.

You can now deploy the WAR files using the WebLogic AdministrationConsole.

To deploy the WAR files to WebLogic 10You need to log on to the WebLogic Server Administration console.

Once the WAR files have been prepared for deployment, you can use theWebLogic 10 Administration console to deploy the web applications.

1. Click Deployments under "Domain Structure".The "Summary of Deployments" is displayed on the right.

2. Click Install under the Control tab.The "Install Application Assistant" is displayed.

3. Click Lock & Edit under "Change Center".4. In the Location area navigate to the following folder:



C:\Program Files\BusinessObjects\deployment\workdir\weblogic10\application\.

5. Select InfoViewApp.war and click Next.6. ClickNext in the screen that displays to accept the selected default setting

Install this deployment as an application."Select deployment targets" is displayed.

7. Under "Clusters" select cluster1 and All servers in the cluster. ClickNext."Optional settings" is displayed.

8. Click Finish to accept all the defaults settings.The "Install Application Assistant" is closed.

9. Click Activate Changes under "Change Center".10. Repeat steps 1-8 for all the files in the C:\Program Files\Business

Objects\deployment\workdir\weblogic10\application\ directory.All the files to be deployed are listed in "Summary of Deployments "underthe Control tab.

11. Select all the files under the Control tab.12. ClickStart > Servicing all requests.

The files are deployed and ready to run.

To set up the hardware load balancer

This section illustrates the configuration of a Cisco CSS 11500 series loadbalancer for use with two clustered WebLogic web application servers.Advanced administrative knowledge of Cisco load balancer products isrequired. The load balancer must be configured to use persistent (sticky)sessions.

The load balancer provides content switching for incoming external clientrequests to the web application servers in the web tier.1. Create a VLAN circuit IP address. This will allow administrators to connect

to the load balancer remotely.Below, a VLAN circuit named VLAN189 is created with an IP address of10.50.96.78.CSS11503#configCSS11503(config)#circuit VLAN189



CSS11503(config−circuit[VLAN189])#ip address 10.50.96.78255.255.252.0CSS11503(config−circuit−ip[VLAN189−10.50.96.78])#exitCSS11503(config−circuit[VLAN189])#exitCSS11503(config)# exitCSS11503#

2. Configure the IP address and the port number to be used for incomingweb requests. Web clients will sent web requests to load balancer at thisaddress and port number.Below, a virtual, load balanced server named arrowpoint-weblogic at10.50.96.79 port 7001 is created. To a web client, arrowpoint-weblogicwill appear to be a single WebLogic server.CSS11503# configureCSS11503(config)# owner transCreate owner <trans>, [y/n]:yCSS11503(config-owner[trans])# content arrowpoint-weblogicCreate content <arrowpoint-weblogic>, [y/n]:yCSS11503(config-owner-content[trans-arrowpoint-weblogic])#vip address 10.50.96.79CSS11503(config-owner-content[trans-arrowpoint-weblogic])#protocol tcpCSS11503(config-owner-content[trans-arrowpoint-weblogic])#port 7001

3. Create a service for each WebLogic server in the cluster, entering theservice name, IP address, and other connection information. The loadbalancer will distribute requests received from web clients among theseservers.Below, services are created for each WebLogic server:LB01-ARROWPOINT at 10.50.96.76, and LB02-ARROWPOINT at10.50.96.77.CSS11503# configureCSS11503(config)# service <LB01-ARROWPOINT>Create service LB01-ARROWPOINT, [y/n]:yCSS11503(config-service[LB01-ARROWPOINT])# ip address10.50.96.76CSS11503(config-service[LB01-ARROWPOINT])# string LB01CSS11503(config-service[LB01-ARROWPOINT])# keepalive typetcpCSS11503(config-service[LB01-ARROWPOINT])# keepalive port7001CSS11503(config-service[LB01-ARROWPOINT])# activeCSS11503(config-service[LB01-ARROWPOINT])# exitCSS11503(config)# exitCSS11503#

CSS11503# configure



CSS11503(config)# service <LB02-ARROWPOINT>Create service LB02-ARROWPOINT, [y/n]:yCSS11503(config-service[LB02-ARROWPOINT])# ip address10.50.96.77CSS11503(config-service[LB02-ARROWPOINT])# string LB02CSS11503(config-service[LB02-ARROWPOINT])# keepalive typetcpCSS11503(config-service[LB02-ARROWPOINT])# keepalive port7001CSS11503(config-service[LB02-ARROWPOINT])# activeCSS11503(config-service[LB02-ARROWPOINT])# exitCSS11503(config)# exitCSS11503#

4. Add each of the WebLogic services to the load balancer. Requestsreceived by the load balancer will then be distributed between each ofthe services.Below, LB01-ARROWPOINT and LB02-ARROWPOINT are added to theload balancer as services.CSS11503(config-owner-content[trans-arrowpoint-weblogic])#add service LB01-ARROWPOINTCSS11503(config-owner-content[trans-arrowpoint-weblogic])#add service LB02-ARROWPOINT

5. Configure session persistence, so that requests can be managed by allWebLogic servers in the cluster.Below, session persistence is activated.CSS11503(config-owner-content[trans-arrowpoint-weblogic])#advanced-balance arrowpoint-cookieCSS11503(config-owner-content[trans-arrowpoint-weblogic])#activeCSS11503(config-owner-content[trans-arrowpoint-weblogic])#exitCSS11503(config-owner[trans])# exitCSS11503(config)#

The load balancer is now configured to accept requests from web clients asvirtual server arrowpoint-weblogic at 10.50.96.79 port 7001. Thearrowpoint-weblogic virtual server distributes the requests between WebLogicservers configured as services LB01-ARROWPOINT at 10.50.96.76 port7001 and LB02-ARROWPOINT at 10.50.96.77 port 7001.!Generated on 10/02/2007 13:09:44!Active version: sg0730005

configure



!*************************** GLOBAL **************************

ip route 0.0.0.0 0.0.0.0 10.50.96.1 1!************************* INTERFACE *************************interface e9trunkvlan 189

!************************** CIRCUIT **************************circuit VLAN189ip address 10.50.96.78 255.255.252.0

!************************** SERVICE **************************service LB01-ARROWPOINTip address 10.50.96.76string LB01keepalive type tcpkeepalive port 7001active

service LB02-ARROWPOINTip address 10.50.96.77string LB02keepalive type tcpkeepalive port 7001active

!*************************** OWNER ***************************owner trans

content arrowpoint-weblogicvip address 10.50.96.79advanced-balance arrowpoint-cookieprotocol tcpport 7001add service LB01-ARROWPOINTadd service LB02-ARROWPOINTactive

!*************************** GROUP ***************************group transadd destination service LB01-ARROWPOINTadd destination service LB02-ARROWPOINTvip address 10.50.96.79active




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 with a hardware loadbalancer , the other (interface eth1) is connected to an external unsecurenetwork, such as the internet.


The following steps illustrate how to forward requests from clients on anunsecure external (interface eth1) network to port 7001 on a hardware loadbalancer running on a secure, firewalled network (interface eth0).1. Log in to your Red Hat Linux server.





3. Add an exception to the iptables firewall rules that forwards incomingclient requests on port 7001 to port 7001 on the Cisco CSS 11500 serieshardware load balancer.

Clients on an unsecured network outside the firewall can now access theclustered WebLogic web application servers tier through the firewall on port7001.

To set up a client tier

To set up the client tier in this scenario all you need is a machine running onWindows Server 2003 SP2 Enterprise Edition and a web browser.

1. Open your web browser



2. Access the cluster by entering the followingURL:http://10.50.96.79:7001/InfoViewApp/The "Log On to InfoView" page appears.

3. Type SERVER1 for System; Administrator forUser name; and passwordfor Password.

4. Click Log On.The "InfoView" home page is displayed.



You have successfully completed the scenario.



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

IndexAApache Tomcat 5.5

configuration details 58, 83, 96

Bbasic web tier scenario

configuration details 240diagram 240overview 240system layers 240

BusinessObjects Enterpriseavailable diagnostic tests 118, 119client 277client components 65, 134Deployment diagnostic tool

configuring 122running from command line 120running from Windows 119

documentation 10network requirements 17new features 12non-system drive installation 20silent 148uninstalling 147

BusinessObjects Enterprise client toolsscripted 142silent installation 142

Cchecklist for installation 40client

set up 277

client components 65, 134client tools 26client tools installation 134

procedure 135sample ini file 143scripted 142silent 142

clusteringFile Repository Servers 265

clustersWebLogic configuration 268

CMClogging into 116

CMC logon issues 117CMS clustering 72CMS database

setting up on Windows 31components, selecting individually on Windows

64configuring

Tomcat 57, 83, 95configuring existing database 76custom and expand 24custom and expand installation

deselecting features 64selecting features 64

custom or expand installationclient components 71Windows 64

Ddatabase 36

configuring existing 76installing MySQL 30


database (continued)permissions 36preparing your existing 35

database configuration detailsDB2 53MySQL 53oracle 53SQL sever 53sybase 53

database requirementscharacter encoding 30CMS overview 30

database server preparations 35database, CMS 31DB2 31deployment

documentation 10JBoss 214Oracle Application Server 213SAP Application Server 215Tomcat 212Tomcat clusters 213verifying 165, 204WebLogic 208WebLogic clusters 209WebSphere 205WebSphere cluster 206WebSphere Community Edition 216

Deployment diagnostic tool 118available tests 118, 119

deployment scenariocomplex 256diagram 256

deployment scenariosdesktop client to server 220general overview 220

deployments, complexinstalling language packs 127

distributed deploymentsoverview 29

domain namesCMS location 21

domain names (continued)fully qualified 21

dswsbobje.warWebLogic deployment 211

Eenvironment

database 31

IInfoView

logging into 116installation

only server components 71web application server 37, 157web tier 90

installation .ini fileparameters 103

installation checklist 40, 67, 90installation ini file

creating 103installation log file 153installation overview 16installation scenarios

on Windows 23installation script

sample .ini file 104installation setup

accepting license agreement 41configuring existing database server 53configuring MySQL 52entering user information 42product keycode specification 42select web application option 56, 81, 93selecting language packs 43SIA node specification 51, 74SIA port specification 51, 74specifying CMS information 50, 73

installation types 23, 24, 25, 26client tools 26


Index

installation types (continued)custom and expand 24new 23web tier 25

Installing MySQLconfiguring 52

inventory.xml 149

JJBoss

manual deployment 214

Llanguage packs

definition 126English fallback 126fallback to English 126installation on Windows 127installing 128locale 126locating 128manual deployment 127Product Locale 126selecting locale 126silent mode 129specifying through installer 43uninstalling 131

load balancer 273log file

installation 153logging

to the CMC 116

Mmaintenance mode

modify 146remove 146repair 146

modify installation 146evoking maintenance mode 146

MySQLinstalling as database 30

Nnetwork requirements

firewalls 17new 23

OOracle 31Oracle Application Server

manual deployment 213Oracle Application Server 10g R3

configuration details 58, 83, 96

Ppreparing your database server 35product registration 117

Rregistration wizard 117remove installation 146

evoking maintenance mode 146repair installation 146

evoking maintenance mode 146

SSAP Application Server

manual deployment 215scripted installation

common parameters 107scripted installation on Windows 102server

choosing location 22


Index

server communicationfixed host names 21multiple NIC hosts 21set up 21

serversassigning static ports 230, 266clustering File Repository servers 265

setup.exe parameters-w 103additional parameters 103

side-by-side installation 29silent installation

common parameters 107silent installation on Windows 102Software Inventory Tool

functionality 149history view 151installation files 149introduction 148inventory.xml 149, 153log.txt 149, 153search 153SoftwareInventory.bat 149SoftwareInventory.jar 149user interface 150viewing format

ADAPT number 151file 151install/patch name 151

Sybase 31system requirements 16

TTomcat

configuring 57, 83, 95manual deployment 212

Tomcat clustersmanual deployment 213

troubleshooting CMC logon 117

UUnicode 31uninstalling 146, 147

silent 148

WWAR file

verifying deployment 165, 204war files

configuring 194deploying to remote server 194preparing for WebLogic 271

WAR filescontext roots 198deploying to WebLogic 10 272deployment guidelines 199web services 197

wdeployfunctionality 158log file 164options 164prerequisites 157Tomcat 177with JBoss 189with Oracle 183with SAP Application Server 186with WebLogic 172with WebSphere 165with WebSphere Community Edition 191

web application deploymenton remote machines 194

web application serverconfiguration details 58, 83, 96minimum required rights 18

Web application serverinitial installation 37, 157

web services 197web tier 25web tier components

features 67, 90


Index

web tier components (continued)specifying a CMS 92Tomcat installation option 67, 90web applications 67, 90web services 67, 90

web tier installationdeselecting features 91selecting features 91

WebLogicdeploying with wdeploy 172manual deployment 208preparing cluster 268

WebLogic 10configuration details 58, 83, 96

WebLogic 9configuration details 58, 83, 96

WebLogic administration consoledeploying WAR files 272

WebLogic clustersmanual deployment 209

WebSphereJSF implementation 168, 206manual deployment 205

WebSphere 6.1configuration details 58, 83, 96

WebSphere clusterdeploying to 206

WebSphere Community Editionmanual deployment 216

WebSphere Community Edition 2.0configuration details 58, 83, 96

Windows 23BusinessObjects Enterprise

custom or expand installation 64scripted 102silent installation 102

installation scenarios overview 23


Index


Index

xi3 bip install windows en

Documents