BusinessObjects Enterprise XI 3.

0 Installation and Configuration Guide for UNIX

BusinessObjects Enterprise XI 3.0 unix

Copyright

© 2008 Business Objects. All rights reserved. Business Objects owns the following U.S. patents, which may cover products that are offered and licensed by Business Objects: 5,295,243; 5,339,390; 5,555,403; 5,590,250; 5,619,632; 5,632,009; 5,857,205; 5,880,742; 5,883,635; 6,085,202; 6,108,698; 6,247,008; 6,289,352; 6,300,957; 6,377,259; 6,490,593; 6,578,027; 6,581,068; 6,628,312; 6,654,761; 6,768,986; 6,772,409; 6,831,668; 6,882,998; 6,892,189; 6,901,555; 7,089,238; 7,107,266; 7,139,766; 7,178,099; 7,181,435; 7,181,440; 7,194,465; 7,222,130; 7,299,419; 7,320,122 and 7,356,779. Business Objects and the Business Objects logo, BusinessObjects, Business Objects Crystal Vision, Business Process On Demand, BusinessQuery, Cartesis, Crystal Analysis, Crystal Applications, Crystal Decisions, Crystal Enterprise, Crystal Insider, Crystal Reports, Crystal Vision, Desktop Intelligence, Inxight, 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 or registered trademarks in the United States and/or other countries of Business Objects and/or affiliated companies. Business Objects is an SAP company. SAP is the trademark or registered trademark of SAP AG in Germany and in several other countries. All other names mentioned herein may be trademarks of their respective owners. Business Objects products in this release may contain redistributions of software licensed from third-party contributors. Some of these individual components may also be available under alternative licenses. A partial listing of third-party contributors that have requested or permitted acknowledgments, as well as required notices, can be found at: http://www.businessobjects.com/thirdparty 2008-06-02

Third-party Contributors

Contents
Chapter 1 Getting Started 9 About this documentation..........................................................................10 Who should read this documentation .......................................................10 BusinessObjects Enterprise guides...........................................................10 What is BusinessObjects Enterprise?.......................................................12 What's new in the BusinessObjects Enterprise Installation and Configuration guide? .......................................................................................................12 Chapter 2 Preparing to Install BusinessObjects Enterprise 15

Installation overview..................................................................................16 System requirements ..........................................................................16 UNIX permissions.................................................................................17 Setting up your UNIX system...............................................................20 Setting up server communication.........................................................23 Installation Scenarios.................................................................................25 New installation....................................................................................26 Custom or Expand installation .............................................................26 Web tier installation .............................................................................27 Client Tools installation ........................................................................28 Silent installation .................................................................................28 Side-by-side installation.......................................................................29 CMS System and Auditing Database Requirements.................................30 Database requirements........................................................................30 Using a supported database server.....................................................30 Using MySQL.......................................................................................32 Setting up an empty database for the CMS.........................................32

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

3

Contents

Setting up a database account for BusinessObjects Enterprise .........34 Preparing your CMS System Database server..........................................35 Prerequisites for database preparation................................................35 Preparing your existing database server..............................................35 MySQL database setup requirements..................................................38 DB2 database setup requirements.......................................................38 Oracle database setup requirements...................................................40 Sybase database setup requirements..................................................42 Providing and verifying connectivity to the CMS database........................43 To verify Sybase native connectivity through a server name...............44 To verify Oracle native connectivity through a TNS.............................46 To verify DB2 native connectivity through a database alias.................48 Before you deploy web applications..........................................................50 Chapter 3 Beginning the Installation of BusinessObjects Enterprise 51

Installation checklist...................................................................................52 Installation overview..................................................................................53 Setting up product distribution...................................................................53 Running the product distribution directly from a CD.............................54 Copying the product distribution to your machine................................54 Beginning your installation.........................................................................55 To begin your installation......................................................................56 To accept the license agreement.........................................................57 Entering Product Keycode....................................................................57 Specifying the installation directory......................................................57 Installing language packs.....................................................................57 To select user or system installation....................................................58 Selecting an installation type................................................................59

4

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Contents

Chapter 4

New Installation

61

Performing a new installation.....................................................................62 To perform a new installation................................................................62 To configure the new CMS ..................................................................63 To specify a system database option...................................................63 To enter Server Intelligence Agent information....................................67 To select a web application server configuration option.......................67 To start the installation .........................................................................72 Finishing a system installation ..................................................................73 Chapter 5 Custom or Expand Installation 75

Performing a custom installation...............................................................76 Features available in a custom installation..........................................76 To perform a Custom or Expand installation..............................................79 To install only the server components..................................................80 Installing only the Web Tier Components.............................................86 Finishing a system installation ..................................................................93 Chapter 6 Web Applications Installation 95

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

5

Contents

Chapter 7

Silent Installation

105

Overview..................................................................................................106 Performing a scripted installation............................................................106 To create a response file....................................................................107 To run a scripted installation...............................................................107 Scripted installation parameters.........................................................108 Performing a silent installation.................................................................117 Chapter 8 After Installing BusinessObjects Enterprise 125

Using ccm.sh to start the BusinessObjects Enterprise servers...............126 To manually start and enable servers................................................126 Post install component deployment.........................................................126 Setup for performance management ......................................................127 To set up performance management.................................................128 Troubleshooting starting performance management..........................128 Chapter 9 Language Packs on UNIX 131

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

6

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Contents

Chapter 10

Maintaining your Installation

139

Uninstalling BusinessObjects Enterprise from UNIX...............................140 To uninstall BusinessObjects Enterprise............................................140 Adding performance management to your installation............................141 To add performance management.....................................................141 The installation log file ............................................................................146 Chapter 11 Post Installation Web Application Deployment 147

Overview of post install deployment........................................................148 Before you deploy web applications........................................................149 Deploying with wdeploy...........................................................................149 Prerequisites for using wdeploy.........................................................149 Overview for using wdeploy...............................................................150 How to use wdeploy...........................................................................151 Options for using wdeploy..................................................................155 After deploying web applications........................................................156 Deploying to web application servers with wdeploy...........................156 To deploy web applications on a remote machine ............................182 Manually deploying to a web application server......................................185 BusinessObjects Enterprise WAR files..............................................185 WAR file context roots........................................................................186 Guidelines for deploying WAR files....................................................187 To manually deploy web applications.................................................188 To prepare for manual deployment on a remote machine..................189 After deploying web applications........................................................192 Deploying with the Administration console.........................................193 Chapter 12 Deployment Scenarios 207

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

7

Contents

Desktop client to server scenario............................................................208 Desktop client to server overview .....................................................208 Summary of required tasks................................................................209 Deploying the client to server scenario..............................................210 Basic N-tier scenario................................................................................226 N-tier scenario overview.....................................................................226 Summary of required tasks................................................................227 Deploying the basic N-tier scenario...................................................227 Appendix A Get More Help 239

Index

243

8

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Getting Started

1

1

Getting Started About this documentation

About this documentation
This documentation provides you with information and procedures for installing BusinessObjects Enterprise XI 3.0 on UNIX, including detailed instructions for the different installation modes available. In addition this documentation provides instructions for Standalone Client Tools installation, Language Pack installation and for modifying, or removing BusinessObjects Enterprise.

Who should read this documentation
This documentation is intended for the system administrator or IT professional who needs to install BusinessObjects Enterprise XI 3.0 on UNIX operating systems. Familiarity with your overall network environment, port usage, your database environment, and your web server software would be beneficial.

BusinessObjects Enterprise guides
The following table provides a list of BusinessObjects Enterprise guides and their contents. Guide BusinessObjects Enterprise Deployment Planning Guide Description This guide covers the key concepts you should consider before you begin deploying BusinessObjects Enterprise. This guide includes an overview of the architecture, tips for assessing your existing environment, determining your organization's needs, and preparing for the installation.

BusinessObjects Enterprise In- Leads you through the steps required to stallation and Configuration run the setup program and complete your Guide installation of BusinessObjects Enterprise. There are UNIX and Windows versions of this guide available.

10

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Getting Started BusinessObjects Enterprise guides

1

Guide BusinessObjects Enterprise Administrator's Guide

Description Provides content for server administration and content administration. The server administration topics includes server configuration, managing authentication, configuring firewalls, and measuring system performance. The content administration topics include working with the CMC, configuring rights and access levels, managing users, and working with Business Objects applications and objects. Provides an overview of the publishing process, working with publications, publishing Crystal reports, publishing web intelligence documents, publishing desktop intelligence documents, and publishing security.

BusinessObjects Enterprise Publisher's Guide

BusinessObjects Enterprise Mi- Details content migration from legacy gration Guide Business Objects software, such as Classic or Enterprise 5 or 6, to BusinessObjects Enterprise XI 3.0. BusinessObjects Enterprise Upgrade Guide Information for upgrades from BusinessObjects Enterprise XI to BusinessObjects Enterprise XI 3.0.

BusinessObjects Enterprise In- Provides an overview of InfoView and foView User's Guide working with Crystal Reports, Web Intelligence, objects, discussions, encyclopedia, and Voyager workspaces.

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

11

1

Getting Started What is BusinessObjects Enterprise?

What is BusinessObjects Enterprise?
BusinessObjects Enterprise XI 3.0 is a flexible, scalable, and reliable solution for delivering powerful, interactive reports to end users via any web application—intranet, extranet, Internet or corporate portal. Whether it is used for distributing weekly sales reports, providing customers with personalized service offerings, or integrating critical information into corporate portals, BusinessObjects Enterprise delivers tangible benefits that extend across and beyond the organization. As an integrated suite for reporting, analysis, and information delivery, BusinessObjects Enterprise provides a solution for increasing end-user productivity and reducing administrative efforts.

What's new in the BusinessObjects Enterprise Installation and Configuration guide?
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide is the first release to include information on the following features:
Feature Description

Language Packs in- New languages can be added to your installation using stallation the standalone Language Pack installer. Deploying web appli- Web applications can now be deployed directly using the cations BusinessObjects Enterprise installer, or after installation using either the wdeploy tool or the web application server's administration console. Procedures for several deployment scenarios are considered and thoroughly documented in this guide. Scripted Installation 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 custom installations. Web-tier installation Web applications can be installed and deployed to supported web application servers using a dedicated installation method.

12

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

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

1

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

13

1

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

14

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Preparing to Install BusinessObjects Enterprise

2

2

Preparing to Install BusinessObjects Enterprise Installation overview

Installation overview
BusinessObjects Enterprise XI 3.0 provides an open and flexible architecture that supports a multitude of deployment and configuration scenarios. Before you install BusinessObjects Enterprise you should: • • • • • • • Consult the BusinessObjects Enterprise XI 3.0 Deployment and Planning Guide. Review your physical system to ensure that it meets the basic requirements for a BusinessObjects Enterprise installation. Ensure that all machines that will be part of your BusinessObjects Enterprise XI 3.0 deployment can communicate properly with one another. Decide which BusinessObjects Enterprise XI 3.0 components to install and which of your own components to integrate. Determine where the components should be installed. Decide which installation method to use. Consider how you should prepare your infrastructure and set up your environment including server locations.

The following sections list the core software requirements, the choices available to you within the core requirements, and the installation methods that you can use when you install BusinessObjects Enterprise. At the start of the next chapter, you will find an installation checklist. You can use this checklist to help ensure you are prepared before you begin your installation.

System requirements
For a detailed list of supported environments and hardware requirements, consult the Platforms Availability Report (PAR) file available on the Business Objects support site http://support.businessobjects.com/documentation/sup ported_platforms/. This file includes specific version and patch-level requirements for web application servers, web browsers, and operating systems. For additional important information that may pertain to your deployment, it is also strongly recommended that you consult the BusinessObjects Enterprise XI 3.0 Deployment Planning Guide . Generally, the following components must be preinstalled and configured correctly before you can install BusinessObjects Enterprise XI 3.0:

16

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Preparing to Install BusinessObjects Enterprise Installation overview

2

• •

Web application server (unless you want to install Tomcat as part of your installation of BusinessObjects Enterprise) Database software that is compatible with the CMS system and the Audit databases (unless you want to install MySQL as part of your installation of BusinessObjects Enterprise).

Note: BusinessObjects Enterprise requires a database to store information

about the system and its users.
Tip: If you are installing on VMWare, ensure your machine name does not

include any of the following characters: an underscore, a period, or a slash.

UNIX permissions
To perform either a user or system installation on UNIX, the user account under which the install is run must have read, write, and execute permissions to the directory where BusinessObjects Enterprise will be installed. Root privileges are not required to perform either a user or system install of BusinessObjects Enterprise.
Caution: If you attempt an installation with root privileges, you will be

unsuccessful However, if you run a system installation, you do require root authority to run the system-level initialization script. This script, which is called setupinit.sh, is run after the installation completes. This script creates entries into the run control scripts for the operating system that start up the BusinessObjects Enterprise servers when the UNIX server is brought up, and stops the servers when a machine is shut down. The following table summarizes all the required permissions for installing BusinessObjects Enterprise.
Category Operating System Network Required permissions Read, write, and execute permissions to the directory where BusinessObjects Enterprise will be installed . Root access if performing a system installation. Access to all machines via TCP/IP - all specified ports must be available

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

17

2

Preparing to Install BusinessObjects Enterprise Installation overview

Category Database

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

Minimum rights for deploying web applications
Tip: We recommend that you use the same user account for installing

BusinessObjects Enterprise and your web application server. To deploy web applications using a user account different from the one used to install the web application server, you must ensure that the BusinessObjects Enterprise user account has the privileges listed in the following table.
Web application server JBoss Minimum required permissions • • rights to read, write and execute files in $as_dir/bin rights to remove the $as_dir/server/${as_in
stance}/deploy/jbossweb-tomcat55.sar/jsflibs directory

• • Oracle

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

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

• • •

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

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

SAP Web Application Server

• •

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

rights to read, write and execute files in
$as_dir/$as_sid/$as_instance/j2ee/deploy ing

18

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Preparing to Install BusinessObjects Enterprise Installation overview

2

Web application server Tomcat

Minimum required permissions • • • • rights to read, write and execute files in $as_dir/bin rights to read, write and execute files in
$as_dir/shared/lib

rights to read, write and execute files under $ad_sir/webapps and its subdirectories rights to read, write and execute files under $as_dir/conf and its subdirectories right to read files under $WL_HOME/server/lib

WebLogic

• • • • •

right to read and write files under $as_dir/bin/ right to read and execute files under $WL_HOME/ jdk150_06/ (or your WebLogic JDK directory) right to read files under $WL_HOME /wlserver_10.0/common/bin

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

Note: WL_HOME is the weblogic installation dir and not as_dir -- which is the domain root WebSphere • • • • • • • • • Right to read and execute $as_dir/bin/wsadmin.sh Right to read and execute $as_dir/bin/GenPlug
inCfg.sh

Right to read $as_dir/bin/securityProcs.jacl Right to read $as_dir/bin/LTPA_LDAPSecuri
tyProcs.jacl

Right to read and execute files in$as_dir/plugins Right to read and execute files in $as_dir/java Right to read and execute files in $as_dir/deploy
tool

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

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

Note: In addition to the right to execute files or folders mentioned in the

above table, the right to execute is also required on the parent directory.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

19

2

Preparing to Install BusinessObjects Enterprise Installation overview

Setting up your UNIX system
BusinessObjects Enterprise integrates with your existing database and web server software components, so the installation script needs to collect certain information about your current system. Because UNIX systems can vary significantly from site to site, the following sections detail the key tasks that you must perform prior to installing BusinessObjects Enterprise.

Setting the locale
Before you install BusinessObjects Enterprise, set your operating system to use one of the locales that BusinessObjects Enterprise supports for your version of UNIX. For a detailed list of supported UNIX environments see the Product Availability Report PDF available from the following Business Objects support site:http://support.businessobjects.com/documentation/supported_plat forms/.
Note: You should also ensure that the character set translation on your

terminal is set to UTF-8. If you are working through the console of a UNIX machine, you can select your locale directly from the logon screen when you log on with the account from which you will install BusinessObjects Enterprise. However, to ensure that your operating system uses the correct locale whenever BusinessObjects Enterprise runs, set the LC_ALL and LANG environment variables to your preferred locale in your login environment. (For example, if you are using a C shell, set these environment variables in the .login file).
Tip: Type locale to check that all of the related locale environment variables

(such as LC_MONETARY, LC_NUMERIC, etc.) were properly set by LC_ALL. See the section on International Deployments in the BusinessObjects Enterprise Administrator's Guide for information on deploying BusinessObjects Enterprise for a multilingual, world-wide audience.

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

20

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Preparing to Install BusinessObjects Enterprise Installation overview

2

/bin/sh

pwd

read

touch

uname

expr

hostname

sed

awk

chown

grep

tail

tar

id

dirname

gzip

stty

ulimit

which

These relatively standard commands and utilities should be available on most UNIX distributions. However, if for any reason one of them is not available on your system, download and install a version appropriate to your UNIX system. It is recommended that you obtain any required files from your UNIX vendor. Additionally, these commands and utilities must be accessible in the PATH environment variable of the user account that you use when installing BusinessObjects Enterprise. For details, see Creating an account, a home directory, and a login environment on page 21.

Creating an account, a home directory, and a login environment
Create a specific user account and group under which the BusinessObjects Enterprise background processes can run. You will log on as this user in order to perform the remainder of the installation procedures. Although you will require root privileges to set up this account, the account itself does not require root privileges. Neither the installation scripts nor BusinessObjects Enterprise itself needs to run as root. Use your usual administrative procedures to perform these recommended tasks.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

21

2

Preparing to Install BusinessObjects Enterprise Installation overview

To set up an account for installing BusinessObjects Enterprise 1. Create a new group or use an existing group. Create a new user account, and set this user's primary group to the new group. Assign a secure password to the new user account. 2. Create the directory where you want to install BusinessObjects Enterprise.
By default, the installation will use your current directory as its base directory for the install, that is, the directory where you run install.sh. You can override this default, with the directory of your choice at install time. You will see the directory that you specify for the installation directory referred to as INSTALLDIR throughout this document. 3. Ensure that the account you created has read, write, and execute permissions on the new installation directory. 4. Assign the new user a default login shell, and create or modify the appropriate login script(s) for the user account. In particular, make sure that the login script(s) set up a default login environment that meets these requirements: • All of the commands and utilities required by the install setup program must be accessible in the PATH environment variable. • The user's login environment must set up the database environment such that the install setup program can access your database client software. • The user's login environment must set up a default locale that is supported by your UNIX system and BusinessObjects Enterprise.
Related Topics

• • •

Checking for required commands and utilities on page 20 Providing and verifying connectivity to the CMS database on page 43 Setting the locale on page 20

Meeting the host name and network requirements
Your UNIX server must have a fixed host name before you run the installation script. You must have root privileges to set or modify this information on your system. If you are unfamiliar with these procedures, consult your UNIX system documentation.

22

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Preparing to Install BusinessObjects Enterprise Installation overview

2

When installing BusinessObjects Enterprise on multiple machines, ensure that each target machine is able to communicate over TCP/IP with the machine that is running as your Central Management Server (CMS).
Note: If you are installing BusinessObjects Enterprise in a firewall

environment, you will need additional configuration details. See the "Working with Firewalls" section of the BusinessObjects Enterprise Deployment and Configuration Guide.

Difference between user and system installation
When you perform a new installation, on UNIX, you can choose between a user and a system installation. • • When you choose a user installation, all the required components are installed. When you choose a system installation, all the required components are installed, In addition, the installation creates a system-level initiation script. This script creates entries into the run control scripts for the operating system that start up the BusinessObjects Enterprise servers when the UNIX server is brought up and stops the BusinessObjects Enterprise servers when a machine is shut down.
Note: To perform a system installation, you do not require root-level

authority. However, to run the system-level initiation script root-level authority is required.

Setting up server communication
BusinessObjects Enterprise requires a database server and web application server software to be installed and configured if you want to use an existing database or web application server. You can also choose to install a database server (MySQL) and a Web application server (Apache Tomcat 5.5) during your installation of BusinessObjects Enterprise. You must ensure that all BusinessObjects Enterprise machines can communicate properly with one another: • Each BusinessObjects Enterprise machine must be able to communicate over TCP/IP with the machine that runs your Central Management

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

23

2

Preparing to Install BusinessObjects Enterprise Installation overview

Server(CMS). The CMS is responsible for maintaining a database of information about your BusinessObjects Enterprise system, which other components can access as required. The data stored by the CMS includes information about users and groups, security levels, BusinessObjects Enterprise content, and servers. For more information about the CMS, see the “Managing and Configuring Servers” chapter in the BusinessObjects Enterprise Administrator’s Guide. If the host machine has more than one network interface card (NIC), the CMS may automatically bind to a primary NIC. If the primary NIC is not routable, you may have to reconfigure your servers after installation. Alternatively, you could make the primary NIC routable before installing BusinessObjects Enterprise. For more information on how to reconfigure to bind to routable NICs see the “Managing and Configuring Servers” chapter in the BusinessObjects Enterprise Administrator’s Guide. UNIX servers that run BusinessObjects Enterprise must have a fixed host name. You must have root privileges to set or modify a fixed host name on your system. However, you do not require root privileges to perform a user installation of BusinessObjects Enterprise . If you are unfamiliar with these procedures, consult your UNIX system documentation.
Note: Please ensure that the host name you use does not include any

of the following characters: an underscore, a period, or a slash. • Ensure that your database client and server are set up to use Unicode character encoding(such as UTF-8). Consult your database documentation to 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 all BusinessObjects Enterprise machines. This communication is enabled by the BusinessObjects Enterprise Software Development Kit (SDK), which is installed as part of the Web Tier Components. If you plan to use a Java application server and your existing application server does not include a version of the Java Development Kit (JDK) supported by BusinessObjects 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 with Firewalls” section of the BusinessObjects Enterprise Administrator’s Guide.

24

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Preparing to Install BusinessObjects Enterprise Installation Scenarios

2

Choosing a server location
When planning your BusinessObjects Enterprise installation, you should also consider 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 Report Application Server communicate frequently with the database servers containing the data in your published reports. To optimize data retrieval and minimize network traffic, place your processing servers close to your database servers (ideally, on the same subnet). If your BusinessObjects Enterprise installation is distributed over a wide geographic region, use server groups to create groups of nearby servers to process reports. The Central Management Server (CMS) stores data about users and groups, security levels, published objects, and servers in the CMS database. The CMS can also maintain a separate audit database of information about user actions. To optimize CMS performance, place your CMS on the same LAN as the database servers that host your CMS database and the BusinessObjects Enterprise audit database. The CMS can be clustered. If you are deploying more than one CMS, ensure each machine that runs a CMS process experiences the same latency to the system database. Consult the “Managing and Configuring Servers” section of the BusinessObjects Enterprise Administrator's Guide for information on other factors that you may want to consider in planning your BusinessObjects Enterprise installation.

Installation Scenarios
Before you install BusinessObjects Enterprise XI 3.0, consider which of these is your intended scenario: • New installation • Custom installation • Web Tier installation • Client Tools installation • Silent or Scripted installation • Side-by-Side installation

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

25

2

Preparing to Install BusinessObjects Enterprise Installation Scenarios

Distributed Deployments

For an installation upgrade see the BusinessObjects Enterprise Upgrade Guide.

New installation
Performing a new installation is the simplest way to deploy BusinessObjects Enterprise because all the required and optional components are installed by default onto one machine. These components include the following: • • • • • • Web Tier Components Server Components Database Access Export Support Samples Help Files

Custom or Expand installation
The Custom or Expand installation allows you to specify which BusinessObjects Enterprise XI 3.0 components are installed. You may want to perform a Custom or Expand installation if you plan to use BusinessObjects Enterprise in a distributed environment. It may be that you have an existing web application server that resides on a different machine than the one that has your BusinessObjects Enterprise core components. Alternately, you may want to perform a Custom or Expand installation when you want to exclude some components installed by default with the new installation, or install only a limited set of components. It is recommended that you run this type of installation only when you are familiar with specific BusinessObjects Enterprise components and their roles. If you perform a custom install without being familiar with specific BusinessObjects Enterprise components and their roles, you may inadvertently fail to install a required component. You may want to choose a this installation method if: • You are already familiar with the BusinessObjects Enterprise installation program.

26

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Preparing to Install BusinessObjects Enterprise Installation Scenarios

2

Your deployment of BusinessObjects Enterprise servers will be distributed over multiple computers. Perhaps your web application server will be on one machine but other BusinessObjects Enterprise components are elsewhere. You know exactly what components you require. You want to cluster either BusinessObjects Enterprises servers or Server Intelligence Agent Nodes. You have disk space constraints. You have customized some of your own applications and you don't want the installation to overwrite them.

• • • •

Web tier installation
The Web Tier installation provides you with all of the components that are used 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 Business Process 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 server components. You are already familiar with the BusinessObjects Enterprise installation program. You have an existing web application server and would like to dedicate to work with BusinessObjects Enterprise web applications. You completed your initial installation of BusinessObjects Enterprise, and you want to configure an additional web application server on a separate machine.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

27

2

Preparing to Install BusinessObjects Enterprise Installation Scenarios

Client Tools installation
This scenario allows you to perform an installation that installs only the Client Tools on the local machine. Although most end users interact with BusinessObjects Enterprise over the web, the Client Tools are also provided as stand-alone Windows applications: • • • • • • • • • • Desktop Intelligence Web Intelligence Rich Client Data Source Migration Wizard Business View Manager Report Conversion Tool Import Wizard Publishing Wizard Query as a Web Service Universe Designer Developer Components - which include: • BusinessObjects Enterprise Java SDK • BusinessObjects Enterprise Web Services SDK Translation Manager

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

Install these applications for particular users who are responsible for managing BusinessObjects Enterprise content, developing applications, or migrating system data. These client tools are not needed by users who access InfoView or the Central Management Console (CMC) administrative web applications. Some of these tools are used for migration of existing documents from earlier product versions or creating new documents.
Note: The client installation does not generally require a product activation

keycode. However, Desktop Intelligence does require that a key entered in the CMC after the install completes to enable the content type.

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

28

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Preparing to Install BusinessObjects Enterprise Installation Scenarios

2

parameters. This method is particularly useful when you need to perform multiple installations or you do not want to interrupt people who are working on machines in your system. You can also incorporate the silent installation command into your own build scripts. For example, if your organization uses scripts to install software on machines, you can add the silent BusinessObjects Enterprise installation command to those scripts. You may want to choose a silent installation if: • • • You are already familiar with the BusinessObjects Enterprise installation program. You need an automated method for performing similar installations on several machines. You do not want to run the BusinessObjects Enterprise XI 3.0 Setup program.

Note: BusinessObjects Enterprise does not support silent installations when

the install contents are on multiple CDs. If your install source files are on multiple CDs, you must first copy the contents from all the CDs to a central location, such as a hard-drive, and then run the silent install from the location that contains the content from all the CDs.

Side-by-side installation
If you have an existing installation of BusinessObjects Enterprise XI, XI Release 2, and XI 3.0 you may perform a New, Custom or Expand, or Web Application installation of BusinessObjects Enterprise XI 3.0 on the same machine. This is called a side-by-side installation and both versions may run simultaneously. You should install BusinessObjects Enterprise XI 3.0 in a separate directory from your existing BusinessObjects Enterprise installation. You cannot add servers to a CMS cluster used by a different version of BusinessObjects Enterprise. When you perform a side-by-side installation you need to ensure that your BusinessObjects Enterprise XI 3.0 installation will not clash with your preexisting BusinessObjects Enterprise version by : • Specifying a unique CMS cluster name for the BusinessObjects Enterprise XI 3.0 installation.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

29

2

Preparing to Install BusinessObjects Enterprise CMS System and Auditing Database Requirements

Note: You cannot add servers to a CMS cluster used by a different version

of BusinessObjects Enterprise. • Specifying unique port numbers for the BusinessObjects Enterprise XI 3.0 installation.

CMS System and Auditing Database Requirements
Database requirements
Before you create the relational database that you want to integrate with BusinessObjects Enterprise, consider the following sections that detail what settings are required when the relational database is created and what settings you should test before beginning your BusinessObjects Enterprise install. The one requirement that applies, regardless of your database type, is that your relational database be set up to use Unicode character encoding (such as UTF-8). For more information on database requirements, refer to the “Databases in BusinessObjects Enterprise” section in the BusinessObjects Enterprise Deployment Planning Guide.

Using a supported database server
The CMS supports a number of third-party database servers, so you can connect BusinessObjects Enterprise to your existing database infrastructure. For a detailed list of supported database servers see the Product Availability Report PDF available from the Business Objects support site. If you do not have a database installed on your machine you choose to install and configure MySQL as your CMS database through the BusinessObjects Enterprise installation setup program.

30

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Preparing to Install BusinessObjects Enterprise CMS System and Auditing Database Requirements

2

Sourcing the script that identifies the database environment variables
If you are using an existing database, you need a method to connect to it from within BusinessObjects Enterprise. This is done through your database client. In this document, the terminology used for this operation is to source the script that identifies the database environment variables. If you are integrating BusinessObjects Enterprise with a different web application server than the version of Tomcat that can be configured with your installation, you may need to source the environment script. This will set up the required variables for BusinessObjects Enterprise. Technically, sourcing your environment script involves running a script in your current environment. When your database client is sourced from within BusinessObjects Enterprise, all the required environment variables for your database are set up and exported. Your database client or the BusinessObjects Enterprise environment script can be sourced from the command line, entered into a profile, or entered into another script. • To source your database client from the command line, you would execute the script that sets up the variables required by your database client to access your database. For example, in the bash shell, you could type this: source ora10env.sh • To source the BusinessObjects Enterprise environment script, you would execute the script that sets up the variables required. For example, you could add this to the Tomcat setenv.sh or the WebSphere startup script: source "<INSTALLDIR>/bobje/setup/env.sh" Note that the syntax used to source a script varies based on the type of shell you are using. Some UNIX shells use source as the syntax for this operation; some UNIX shells use the .(dot operator). Please consult the documentation for your shell to determine the appropriate syntax.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

31

2

Preparing to Install BusinessObjects Enterprise CMS System and Auditing Database Requirements

Shell name

source

. (dot operator)

Bourne shell (sh) Korn shell (ksh) Bourne Again Shell (bash) C shell (csh) Turbo C shell (tcsh)

no no

yes yes

yes

yes

yes yes

no no

Using MySQL
MySQL database server is an open-source database that provides local data storage. The setup program can configure MySQL along with your BusinessObjects Enterprise components. If you already have MySQL installed, the installation program creates the CMS database using your existing database. During the installation of BusinessObjects Enterprise, you specify what database server you will use and enter the required parameters for authentication.

Setting up an empty database for the CMS
BusinessObjects Enterprise requires a relational database to store information about the system and its users. You can install a MySQL database during the installation, or you can use an existing database. If you want to create a new MySQL database during the installation, this section does not apply to you.

32

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Preparing to Install BusinessObjects Enterprise CMS System and Auditing Database Requirements

2

If you want to use an existing database, you or your database administrator must create a new database on your database server before you install BusinessObjects Enterprise. We strongly recommend that this database be used only for BusinessObjects Enterprise, and not contain other tables. The following database servers are supported on UNIX: • • • • Oracle DB2 Sybase MySQL

Note: See the Platforms.txt file included with your product distribution

for a complete list of supported database software and version requirements. If you plan on integrating your own database with BusinessObjects Enterprise, rather than installing MySQL with your installation, consult these section for details on database setup requirements before you create your database: • • • • DB2 database setup requirements on page 38 Oracle database setup requirements on page 40 Sybase database setup requirements on page 42 MySQL database setup requirements on page 38

If you plan on integrating your own database with BusinessObjects Enterprise, you will to prepare it before your installation. Here is a summary of the steps that will be part of your preparation: • Creating a new database.
Tip: You may want to name the new database bobjecms, and create a

new user account named bobje, however, this naming convention is not required.
Note: If you have a previous release of BusinessObjects Enterprise you

cannot use your database from a previous release for BusinessObjects Enterprise XI Release 2; You must create a new database for this release. If you use a database from a previous release, you will destroy any existing data. Create a new database instead, and after you have completed your installation, you can migrate your old content to the new current version's database.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

33

2

Preparing to Install BusinessObjects Enterprise CMS System and Auditing Database Requirements

• •

Creating a new user account and password for this database that will be used by BusinessObjects Enterprise. Ensuring that this new account has permission to create, modify, and delete tables and create procedures so that BusinessObjects Enterprise can modify the database as required. Recording the name of the database, the user account, and the password when you run the BusinessObjects Enterprise installation script.

During the installation process, the install script asks you if you want to reinitialize the database. Choosing to do so causes the install script to create new tables in the database to store BusinessObjects Enterprise data. (In Oracle, choosing this option causes the install script to create BusinessObjects Enterprise tables in the default schema of the user whose name you provided during the install.)
Note: During a reinstall of BusinessObjects Enterprise, choosing this option

causes the install script to reinitialize the tables containing BusinessObjects Enterprise data, destroying any existing data. You must choose to reinitialize the database to proceed with the install. In either case, reinitializing the database does not affect any other tables in that database or schema. • Consult your database server documentation and/or your database administrator if you are unsure of the procedure for creating a new database. Ensure that your database server is set up to use Unicode character encoding (such as UTF-8). Consult your database documentation to determine the settings required for a Unicode configuration. For database servers such as Oracle and Sybase, during installation you need to configure the server to use Unicode encoding for the character data types. For other databases, such as DB2, you can create the CMS database with Unicode settings on your existing database server.

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

34

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Preparing to Install BusinessObjects Enterprise Preparing your CMS System Database server

2

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

To set up a database account for 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 the account you set up for use by the CMS.
Related Topics

System requirements on page 16

Preparing your CMS System Database server
Prerequisites for database preparation
Before you prepare your database, you must have already created it. Ensure you have created the database with the required settings for your existing database server.
Related Topics

• • • •

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

Preparing your existing database server
After you have created your database, and before you install BusinessObjects Enterprise, you or your database administrator need to prepare your own database server so the CMS can connect to it.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

35

2

Preparing to Install BusinessObjects Enterprise Preparing your CMS System Database server

During your installation, you will be asked whether you want to install MySQL or use an existing database. If you specify that you will you use an existing database, you will be asked for details about your database. Although you are required to provide the details about your database during the installation, you will not be asked to provide your database name unless you are using an existing version of MySQL. This table summarizes the information you will be required to enter to identify your database during the installation if your are using SQL Server, Sybase, Oracle, or DB2. Database type Information required at install time

MySQL Sybase DB2 Oracle

Port number Sybase Server Name DB2 database alias tnsnames connect identifier

Note: On UNIX deployments the Sybase Server Name is a combination of

the server name and the port number which is set by your database administrator in the interfaces file. The database the installation connects to is the default database for the user profile. This default database is to is set by the DBA in the profile of the account from which you will install and run BusinessObjects Enterprise.

To prepare your database
1. Create a new, empty relational database on your database server. 2. Create a new user and assign it a secure password. 3. Ensure that the new account has permission to create, modify, delete tables and create procedures so that BusinessObjects Enterprise can modify the database as required.

36

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Preparing to Install BusinessObjects Enterprise Preparing your CMS System Database server

2

Note: If you are not the owner of the database, you will need to have

permissions to perform the necessary operations. 4. If you are using MySQL, Sybase, Oracle, or DB2, ensure the following are set up before you begin your installation: Database type Ensure this has been configured

MySQL Sybase Oracle DB2

MySQL port number Sybase Server Name tnsnames connect identifier DB2 database alias

During the install, you will be asked for information regarding your database. 5. Record the these details as they will be required during your install: • The name of your database, your Sybase Server Name, your Oracle tnsnames connect identifier, or your DB2 database alias. • The user account and the password authorized to the database.

Tip: You may want to record the required details on the Installation

Checklist at the end of this chapter so the information is available when you install. For information on how to create a new relational database, consult your database server documentation or your database administrator. For information on how to migrate your initial CMS database to another supported database server later, see the BusinessObjects Enterprise Deployment Planning Guide.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

37

2

Preparing to Install BusinessObjects Enterprise Preparing your CMS System Database server

MySQL database setup requirements
For a MySQL database there are no specific parameters that are crucial for BusinessObjects Enterprise to work, other than the setting of UTF-8. If you choose install and configure MySQL as part of your BusinessObjects Enterprise installation setup, you will not have to provide any special configuration information. By default, a MySQL database will be created with the default settings for the CMS database and the Audit database. If you want to use an existing MySQL database server, you will need to prepare the server for the BusinessObjects Enterprise installation.
Related Topics

Preparing your existing database server on page 35

Testing MySQL environment variables
If you are using an existing MySQL database, ensure the following variable is set up for the user who will install BusinessObjects Enterprise XI 3.0: MYSQL_HOME If this variable is not set up, and you have specified that you are using an existing MySQL database, the installation will not proceed and you will receive an error message. Consult the documentation for MySQL for information on how to configure the MySQL.

DB2 database setup requirements
If you are using a DB2 relational database with your BusinessObjects Enterprise deployment, there are specific settings you need to select when the relational database is created. It is not sufficient to modify these settings after the relational database has been created. When you create the relational database you will use with BusinessObjects Enterprise: • Ensure the CMS database is not partitioned.

38

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Preparing to Install BusinessObjects Enterprise Preparing your CMS System Database server

2

If your DB2 CMS database is partitioned, you will have problems creating the CMS database.
Note: This requirement does not apply to the Audit database. If you want,

you can use a partitioned DB2 database for the Audit database. • Create the relational database with the specific settings.
Collating Sequence = "Identity" Codeset = "UTF-8" Territory = "XX"

If your DB2 database does not have the correct collating sequence setting, the users and usergroup objects may not sort properly in the Central Management Console. Replace XX with the code that is appropriate to your code set and codepage for your location. Consult your DB2 documentation for specifics.
Note: If you are using DB2 8.1, you require a C compiler that is installed

and configured to build SQL stored procedures. DB2 8.2 does not have this requirement. SQL stored procedures are used in BusinessObjects Enterprise when users are added to groups in the CMS. Please consult the DB2 documentation for details on how to configure the C compiler for SQL stored procedures, and for determining what version of the C compiler is supported on your platform. After you create your database you will need to prepare it for the BusinessObjects Enterprise install. For details, see Preparing your existing database server on page 35 . In addition, before you begin the install of BusinessObjects Enterprise, you must ensure the DB2 environment variables are set up correctly. For details, see Testing DB2 environment variables on page 39.

Testing DB2 environment variables
If you choose to connect to DB2 through a native connection, the installation searches the current shell for the DB2INSTANCE environment variable. This standard DB2 environment variable must be set in order for the install script to utilize the DB2 client software. If you are using an existing database, you need to source your database client.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

39

2

Preparing to Install BusinessObjects Enterprise Preparing your CMS System Database server

Sourcing the script that identifies the database environment variables can be done in one of two ways: • The user who performs a system installation can modify the BusinessObjects Enterprise script setupint.sh to add the command to source your database client. However, root access is required to execute this script. This script can be found at the following location: <install dir>/bobje/init/setupint.sh. This method will source the database for all users. for information. Each person with a user installation can modify their profile and add the command to source their database environment. This method can be done anytime. For example, if an DB2 database was required, an entry would be made in the user profile to source the environment script used by DB2 (db2profile). Consult your database documentation for the name of its environment script.
Note: Instead of sourcing the script that identifies the database environment

variables, you can manually set the environment variables required by your database. However, if you manually set the environment variables, you will need to set them again if the system is restarted. Consult your database documentation and/or your database administrator if the account shell environment from which you will install BusinessObjects Enterprise has not yet been set up for your database client software, or if you are unable to connect successfully to the database. These steps will test whether the required environment variables are set:
Related Topics

Sourcing the script that identifies the database environment variables on page 31

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

40

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Preparing to Install BusinessObjects Enterprise Preparing your CMS System Database server

2

Related Topics

Testing Oracle environment variables on page 41

Testing Oracle environment variables
If you choose to connect to Oracle through a native connection, the installation searches the current shell for the ORACLE_HOME environment variable. This standard Oracle environment variable must be set in order for the install script to utilize the Oracle client software. If you are using an existing database, you need to source your database client. Sourcing your database client can be done in one of two ways: • The user who performs a system installation can modify the BusinessObjects Enterprise script setupint.sh to add the command to source your database client. However, root access is required to execute this script. This script can be found at the following location: <install dir>/bobje/init/setupint.sh. This method will source the database for all users. Each person with a user installation can modify their profile and add the command to source their database environment. This method can be done anytime. For example, if an Oracle database was required, an entry would be made in the user profile to source the environment script used by Oracle (oraXXenv.csh or oraXXenv.sh where XX is replaced with the version number). Consult your database documentation for the name of its environment script.
Note:

Instead of sourcing the script that identifies the database environment variables, you can manually set the environment variables required by your database. However, if you manually set the environment variables, you will need to set them again if the system is restarted. Consult your database documentation and/or your database administrator if the account shell environment from which you will install BusinessObjects Enterprise has not yet been set up for your database client software, or if you are unable to connect successfully to the database.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

41

2

Preparing to Install BusinessObjects Enterprise Preparing your CMS System Database server

Related Topics

Sourcing the script that identifies the database environment variables on page 31

Sybase database setup requirements
If you are using Sybase, when you create your database for the CMS, ensure the page size is set to 8 KB.
Note: The Sybase database default page size is 2KB which is too small for

CMS. For CMS to run optimally, the page size must be 8KB. The page size is set up during the database creation and it cannot be changed after the database is set up. After you create your database you will need to prepare it for the BusinessObjects Enterprise install. Before you begin the install of BusinessObjects Enterprise, you must ensure the Sybase environment variables are set up correctly.
Related Topics

• •

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

Testing Sybase environment variables
If you choose to connect to Sybase through a native connection, the installation searches the current shell for the SYBASE and SYBASE_OCS environment variables. These standard Sybase environment variables must be set in order for the install script to utilize the Sybase client software. If you are using an existing database, you need to source the script that identifies the database environment variables. Sourcing the script that identifies the database environment variables can be done in one of two ways: • The user who performs a system installation can modify the BusinessObjects Enterprise script setupint.sh to add the command to source your database client. However, root access is required to execute this script. This script can be found at the following location: <install

42

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

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

2

dir>/bobje/init/setupint.sh. This method will source the database for all users. • Each person with a user installation can modify their profile and add the command to source their database environment. This method can be done anytime. For example, if a Sybase database was required, an entry would be made in the user profile to source the environment script used by Sybase (SYBASE.sh or SYBASE.csh). Consult your database documentation for the name of its environment script.
Note:

Instead of sourcing the script that identifies the database environment variables, you can manually set the environment variables required by your database. However, if you manually set the environment variables, you will need to set them again if the system is restarted. Consult your database documentation and/or your database administrator if the account shell environment from which you will install BusinessObjects Enterprise has not yet been set up for your database client software, or if you are unable to connect successfully to the database.

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

Sourcing the script that identifies the database environment variables on page 31

Providing and verifying connectivity to the CMS database
To create tables and write data to your new CMS database, the installation scripts need to establish a connection to the database server. That is, when you log on to UNIX with the user name from which you will perform the installation, the default shell environment must include the appropriate database environment variables and/or initialization files. Only then can the installation setup program access the CMS database using your database client software.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

43

2

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

The environment variables and/or files required by the installation scripts depend upon the type of database server you are running: Additional database environment variables must be set in order for the installation script to use the database client software properly. Before running the installation script, test the shell environment of the account from which you will install BusinessObjects Enterprise to verify database connectivity and privileges. See the procedure that corresponds to your database. • • • Testing Sybase environment variables on page 42 Testing Oracle environment variables on page 41 Testing DB2 environment variables on page 39

To verify Sybase native connectivity through a server name
1. Log on to the UNIX server with the user account and password which you will use to do your install.
Note: This account should already be set up. See Creating an account,

a home directory, and a login environment on page 21for more information on setting up a UNIX account to use when you install BusinessObjects Enterprise. 2. Echo the following environment variables and ensure that their values correspond to your database client software installation. Variable Value

SYBASE

This variable contains the path to the root directory of your Sybase client installation (one level above the SYBASE_OCS version directory).

44

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

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

2

Variable

Value

SYBASE_OCS

This variable contains the name of the Sybase version directory (one level above the Sybase bin and lib directories). The library search path (LD_LI BRARY_PATH on Solaris and Linux, LIBPATH on AIX, and SHLIB_PATH on HPUX) must include the lib directory of your Sybase client installation. The search path must include the bin directory of your Sybase client installation.

library path

PATH

This example checks the required variables, and shows sample output values:
$ echo $SYBASE /opt/sybase/12.0 $ echo $SYBASE_OCS OCS-12_O $ echo $LD_LIBRARY_PATH /export/home/sybase/12.0/OCS-12_0/lib $ echo $PATH /usr/bin:/usr/ucb:/etc:.:/export/home/sybase/12.0/OCS12_0/bin

3. Issue the following command to run the Sybase SQL tool and connect to the database server:
isql -U user -P password -S servername

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

45

2

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

4. Issue the following command to ensure that the account has permission to create tables:
use aps go create table sampletable (def_field char(10)) go sp_help sampletable go

5. Issue the following command to ensure that the account has permission to delete tables:
drop table sampletable go sp_help sampletable go

6. Type quit

To verify Oracle native connectivity through a TNS
1. Log on to the UNIX server with the user account and password which you will use to do your install.
Note: This account should already be set up. See Creating an account,

a home directory, and a login environment on page 21 for more information on setting up a UNIX account to use when you install BusinessObjects Enterprise. 2. Echo the following environment variables and ensure that their values correspond to your database client software installation. Variable Value

ORACLE_HOME

This variable contains the path to the root directory of your Oracle client installation (one level above the Oracle bin and lib directories).

46

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

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

2

Variable

Value

library path

The library search path (LD_LI BRARY_PATH on Solaris and Linux, LIBPATH on AIX, and SHLIB_PATH on HPUX) must include the lib32 directory of your Oracle client installation. The search path must include the bin directory of your Oracle client installation.

PATH

This example checks the required variables and shows sample output values.
$ echo $ORACLE_HOME /home/dbclient/oracle/10.1.0.3 $ echo $LD_LIBRARY_PATH /home/dbclient/oracle/10.1.0.3/lib32 $ echo $PATH /usr/local/bin:/home/dbclient/oracle/10.1.0.3/bin

3. Issue the following command to run the Oracle SQL tool and connect to the appropriate service name:
sqlplus accountname/password@tnsname

Replace accountname,password and tnsname with the appropriate values. If the shell environment has been configured correctly, you are connected to Oracle. 4. Issue the following command to ensure that account has permission to create tables:
create table sampletable (field1 char(10));

5. Issue the following command to ensure that the account has permission to delete tables:
drop table sampletable;

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

47

2

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

6. Issue the following command to ensure that the account has permission to create procedures:
CREATE PROCEDURE test_proc (foo_in VARCHAR, bar_in VARCHAR) IS BEGIN INSERT INTO test_table (foo, bar) VALUES (foo_in, bar_in); END;

7. Issue the following command to ensure that the account has permission to drop procedures:
DROP PROCEDURE TEST_PROC;

8. Type exit

To verify DB2 native connectivity through a database alias
1. Log on to the UNIX server with the user account and password which you will use to do your install.
Note: This account should already be set up. See Creating an account,

a home directory, and a login environment on page 21 for more information on setting up a UNIX account to use when you install BusinessObjects Enterprise. 2. Echo the following environment variables and ensure that their values correspond to your database client software installation. Variable Value

DB2INSTANCE

This variable defines the current DB2 database instance. This variable contains the path to the root directory of your DB2 client installation

INSTHOME

48

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

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

2

Variable

Value

DB2DIR

This variable contains the path to the root directory of your DB2 installation (one level above the DB2 bin and lib directories). The library search path (LD_LI BRARY_PATH on Solaris and Linux, LIBPATH on AIX, and SHLIB_PATH on HPUX) must include the lib directory of your DB2 client installation. The search path must include the bin directory of your DB2 client installation.

library path

PATH

This example checks the required variables and shows sample output values.
$ echo $DB2INSTANCE db2inst1 $ echo $DB2DIR /opt/IBMdb2/V7.1 $ echo $LD_LIBRARY_PATH /export/home/db2inst1/sqllib/lib $ echo $PATH /usr/bin:/usr/ucb:/etc:.:/export/home/db2inst1/sqllib/adm:/ex port/home/db2inst1/sqllib/misc

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

4. Issue the following command to connect to the desired database alias:
connect to db_alias user accountname using password

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

49

2

Preparing to Install BusinessObjects Enterprise Before you deploy web applications

5. Issue the following command to ensure that the account has permission to create tables:
create table sampletable (col_fld char(10) not null)

6. Issue the following command to ensure that the account has permission to delete tables:
drop table sampletable

7. Type terminate

Before you deploy web applications
Your web application server must be installed and working before you attempt to install BusinessObjects Enterprise. Consult your web application server documentation for installation instructions. To deploy and run the CMC and InfoView applications, your web application server should have at least 1.2 GB of free disk space, in addition to any other requirements specified by other software installed on the machine. It is recommended that you change the heapsize and maximum perm size settings of your JVM to -Xmx1024m -XX:MaxPermSize=256m. If using Tomcat 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 your Java memory settings. Before you begin the deployment process, ensure that the web application server is correctly installed and verify that the application server is running correctly by launching its administrative console at: • http://<WAS_HOSTNAME>:<PORT> Replace <WAS_HOSTNAME> with the host name or IP address of your web application server, and <PORT> with the port number used for HTTP. Consult your web application server documentation for installation instructions.

50

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Beginning the Installation of BusinessObjects Enterprise

3

3

Beginning the Installation of BusinessObjects Enterprise Installation checklist

Installation checklist
Prior to installing BusinessObjects Enterprise XI 3.0, please review the checklist below. • • Have you tested that all machines that will run BusinessObjects Enterprise can communicate properly? Have you tested the database connection between the machine that will host your CMS database and the machine on which the Central Management Server will be installed? Have you decided which database to use with BusinessObjects Enterprise? If you are using your own database server, have you created a database for the CMS? If you plan to connect remotely to install, have you ensured your terminal setting is set to VT100 before beginning the installation? If you are using your own database server and plan to use Auditor, have you created an auditing database? If you are using your own database server, have you created a user ID and password with access to your existing database (if you are integrating your existing database server software), so that the installation can access your database to configure the CMS database? If you are using your own database server, have you made sure you can log on to the database with the ID and setup tables? Have you ensured that any existing database you will connecting to has been configured correctly? Have you verified you are using a supported locale? Have you decided whether or not you will develop custom applications? Have you decided what web application server to use? If you plan to use your existing database, has the database client software been properly configured.? If you are not using Tomcat, have you made sure your existing web application server has the JDK installed?

• • • • •

• • • • • • •

52

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Beginning the Installation of BusinessObjects Enterprise Installation overview

3

• • •

If you are not using Tomcat, is your web application server already installed and configured? Do the BusinessObjects Enterprise system requirements match your UNIX setup? If you are installing on VMWare, have you ensured your machine name does 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 environment variables are set up properly? If you are using DB2 or Sybase, have you verified that your database was created with the correct settings? (Some settings can't be modified after the database has been created.)

• •

Installation overview
BusinessObjects Enterprise allows you to run all server components on a UNIX server. Users then connect to BusinessObjects Enterprise over the Web with a supported web browser. The installation can place the necessary run control scripts in the relevant directories for automated startup (requires root privileges), or you can confine the installation to a particular directory. After you finish the installation and setup procedures, the various core server components run as background processes. You can then deploy the BusinessObjects Enterprise web applications. When you install the BusinessObjects Enterprise server components on a UNIX machine, you can connect remotely to BusinessObjects Enterprise with the Publishing Wizard and the Import Wizard. However, these client applications must be installed on Windows.
Note: Before you run the interactive installation setup program (./install),

it is strongly recommended that you read through the details and procedures provided in the previous chapter

Setting up product distribution
This section shows how to distribute BusinessObjects Enterprise so that you can perform an installation.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

53

3

Beginning the Installation of BusinessObjects Enterprise Setting up product distribution

You can perform this installation remotely through a telnet session, or locally through a terminal window. If you will connect remotely to install BusinessObjects Enterprise, be sure to set your terminal settings to VT100 before beginning the installation. There are two ways you can set up the product distribution: • • Before you run ./install.sh, you can copy the installation files to a temporary location. When you run ./install.sh, you can specify the temporary location to place the installation distribution.

Before following this procedure, ensure that you have set up your UNIX system appropriately.
Related Topics

Setting up your UNIX system on page 20

Running the product distribution directly from a CD
By default, the installation will use your current directory, that is, the directory you run install.sh from, as its base directory for the install. If you run in stall.sh without copying the files to a temporary location, you will be prompted to specify a temporary location for the install. After you specify the temporary location, this will happen: • • The installation files will be copied to that temporary location. The installation program will exit.

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

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

54

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Beginning the Installation of BusinessObjects Enterprise Beginning your installation

3

To copy the product distribution to your machine
1. Log on to your UNIX system under the new account designated for installing BusinessObjects Enterprise. 2. Copy the installation files from the product distribution to a temporary directory with this command where /mnt/cd is mapped to the CD drive and tmp is a temporary directory where you want to store the installation files: /mnt/cd/install -t /tmp/ . Repeat this process for each DISK contained in the product distribution. 3. Proceed to Beginning your installation on page 55. 4. Run install.sh from the first CD.
Related Topics

Creating an account, a home directory, and a login environment on page 21

Beginning your installation
The following instructions lead you through the initial steps of installing BusinessObjects Enterprise on UNIX. In this stage you will do the following: • • • • • • • Choose the language for the installation. Agree to the license terms. Enter the product key codes. Select where to install BusinessObjects Enterprise. Select which language packs to install. Choose between a user and system install. Select an install type.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

55

3

Beginning the Installation of BusinessObjects Enterprise Beginning your installation

To begin your installation
The installation procedure below is a quick overview of the initial steps required to install BusinessObjects Enterprise on UNIX. This section is followed by a detailed description of each screen in the installation setup program. 1. Mount the device that contains the installation files. 2. Type ./install.sh in the command line and press Enter.
Note: If you run install.sh without copying the files to a temporary

location, you will be prompted to specify a temporary location for the install. The installation setup program is launched and you are prompted to select a language for the installation. 3. Select a language for the installation and press Enter. You can select from one of the following languages: • German • English • Spanish • French • Italian • Japanese • Korean • Dutch • Portuguese • Swedish • Simplified Chinese • Traditional Chinese The "Business Objects License Agreement" is displayed.
Related Topics

Running the product distribution directly from a CD on page 54

56

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Beginning the Installation of BusinessObjects Enterprise Beginning your installation

3

To accept the license agreement
To install Business Objects Enterprise on UNIX, you must accept the Business Objects License Agreement. 1. Read the software license agreement. 2. Type y to agree to the terms and continue with the setup program. The "Enter Product Keycode" screen is displayed.

Entering Product Keycode
You must provide a valid BusinessObjects Enterprise product activation keycode to continue with the installation setup program. The keycode contains 26 characters and you can find it in the CD liner notes or the CD sleeve. 1. Type your code in Product Keycode. 2. Press Enter to validate the keycode. The setup program validates the keycode before the "Installation Directory" screen is displayed.

Specifying the installation directory
After your product keycode is validated, you must specify an installation directory. 1. To accept the default installation directory press Enter. 2. To create your own directory, use the Backspace key to remove the current directory and replace it with your own path to the desired installation directory and press Enter. You are prompted to select which language packs to install.

Installing language packs
You can choose to install language packs when running the installation setup program on UNIX.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

57

3

Beginning the Installation of BusinessObjects Enterprise Beginning your installation

1. Select any additional language packs you want to install. The following languages are available: • • • • • • • • • • • French Japanese German Spanish Italian Korean Dutch Portuguese Swedish Simplified Chinese Traditional Chinese
Note: English is a required language and cannot be deselected.

2. Press Enter .
Note: You can add language packs after installing Business Objects

Enterprise on UNIX. You are prompted to select either a user or system installation.
Related Topics

To install language packs on page 134

To select user or system installation
1. Select the type of installation you want to perform. • User • System
Note: To perform a System installation, you do not require root-level

authority. However, to run the system-level initiation script root-level authority is required. After you perform a System installation, there are a few additional steps you must perform. 2. Press Enter. The "Installation Type" screen is displayed.

58

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Beginning the Installation of BusinessObjects Enterprise Beginning your installation

3

Difference between user and system installation
There are two possible options for new Business Objects Enterprise installations on UNIX. • • When you choose a User installation, all the required components are installed. When you choose a System installation, all the required components are also installed, however, in addition, the installation creates a system-level initiation script. This script creates entries into the run levels for the Operating System that starts the BusinessObjects Enterprise servers when the UNIX server is brought up and stops the BusinessObjects Enterprise servers when a machine is shut down.

Related Topics

Finishing a system installation on page 103

Selecting an installation type
You can select from one of the following three installation types: New, Custom, or Web Tier. 1. Select the installation type. • New Performing a new installation is the simplest way to deploy BusinessObjects Enterprise because all the required components are installed by default onto one machine. To perform a new System installation, you require root-level authority • Custom or Expand The custom installation allows you to choose which components are installed. You may want to perform a custom installation if you plan to use BusinessObjects Enterprise in a distributed environment. Recommended for advanced users. • Install Web Tier features Choose to perform a web applications installation if you want to install web application server components. This option installs the Web

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

59

3

Beginning the Installation of BusinessObjects Enterprise Beginning your installation

application components only. This is particularly useful for a distributed deployment. • You may select Disable servers after installation to automatically stop all servers. This will prevent communication between the Central Management Server (CMS) and other servers after the installation is complete. For more information on starting, stopping, disabling and enabling servers, refer to the BusinessObjects Enterprise Administrator's Guide.

2. Press Enter.
Related Topics

• • •

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

60

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

New Installation

4

4

New Installation Performing a new installation

Performing a new installation
Performing a new installation is the simplest way to deploy BusinessObjects Enterprise because all the required and optional components are installed on one machine. The setup of a new installation of BusinessObjects Enterprise requires the following input. 1. Providing information on the system administrator for the new installation. 2. Setting up the system and auditing database. You can choose to either install and configure MySQL or configure your existing database. 3. Configuring the Server Intelligence Agent (SIA). 4. Setting up the web application server. You can choose to either install and configure Tomcat or configure your existing web application server. 5. Confirming the installation directory.

To perform a new installation
The "Installation Type" screen in the following procedure is displayed after you have completed the initial set up of the BusinessObjects Enterprise installation. 1. Select or deselect Enable servers after installation. This option is selected by default. Scroll down and use the spacebar to deselect the field. 2. Select New and press Enter. The "Enter the information for your new CMS" screen is displayed.
Related Topics

Beginning your installation on page 55

62

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

New Installation Performing a new installation

4

To configure the new CMS
Use the "Enter the information for your new CMS" screen to specify the Central Management Server (CMS) port number and password for the BusinessObjects Enterprise Administrator. 1. Type a valid port number in CMS Port Number or accept the default number - 6400. 2. Type the same password under Administrator Password and Confirm Password and press Enter.
Note: You can also leave the passwords fields blank and configure the

password at a later time. Your password must be at least six characters long and should contain two of the following options • • • • upper case character lower case character number punctuation

To specify a system database option
You must select a system database option. You can either choose to install MySQL or specify to use your current database. 1. Choose one of the following options: • Use an existing database (Oracle/DB2/Sybase/MySQL) • Install MySQL 2. Press Enter. Depending on your selection you will either select and configure your existing database, or configure your MySQL installation.
Related Topics

• •

To configure your existing database on page 64 To install a new MySQL Database on page 66

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

63

4

New Installation Performing a new installation

To configure your existing database
If you specified to use an existing database for the CMS, use the "Select the database type for your new CMS" screen to select your existing database type. You will then have to configure the database. 1. Select your database type. You can choose from the following • MySQL • Oracle • DB2 • Sybase A new screen displays containing fields for configuring your database. 2. Provide information about your database and press Enter. The table below lists the information required for each database type. Database type Information required

Host Name User ID for CMS database MySQL Password for CMS database MySQL port number Database name for CMS TNS name User ID for CMS database Oracle Password for CMS database CMS port number

64

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

New Installation Performing a new installation

4

Database type

Information required

Alias name User ID for CMS database DB2 Password for CMS database CMS port number Sybase Service name User ID for CMS database Sybase Password for CMS database CMS port number

3. To enable an auditing database, type an x in the field provided. If you want to enable an auditing database, type an x in the field provided. Provide information about your new auditing database. Database type Information required

Auditing database name Auditing database port number Auditing User ID Password

4. Decide if you want to reinitialize the database and press Enter.
Note: Reinitialization of the BusinessObjects Enterprise database will

erase all previous content in that particular database.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

65

4

New Installation Performing a new installation

After configuring your CMS and auditing database, you are prompted for information on the Server Intelligence agent. If you are using an existing database, you need to source your database environment variable so the CMS can access it after a system reboot. This can be done one of two ways • Someone with root access can modify the BusinessObjects Enterprise script BobjEnterprise120 and add the command to source your database environment. This script can be found at the following location: <INSTALLDIR>/bobje/init/BobjEnterprise120. This method will source the database environment variable for all users. Each user can modify their own profile and add the command to source their database environment. This method must be done by each user.

• .

Related Topics

Database requirements on page 30

To install a new MySQL Database
You need to provide configuration details for the new MySQL database. The setup program provides two screens to configure the new database. 1. Provide the following information for your new MySQL database and press Enter. • MySQL Port Number • Database administrator password The second MySQL configuration screen is displayed. 2. Provide the following information for your new MySQL database and press Enter. • MySQL CMS Database Name • MySQL Audit Database Name • User ID
Note: This is the BusinessObjects Enterprise user account.

Password for user account

3. Press Enter to continue with the installation setup.

66

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

New Installation Performing a new installation

4

The "Enter Server Intelligence Agent information" screen is displayed.

To enter Server Intelligence Agent information
The Server Intelligence Agent (SIA) simplifies the deployment and management of the BusinessObjects Enterprise servers. The SIA is automatically created during installation of BusinessObjects Enterprise XI 3.0. Use the installation setup program to configure the SIA. 1. Type a name in Server Intelligence Agent Node. Do not use spaces, dashes or periods in the node Name. This node name serves as an identifier for the SIA. 2. Type a valid port number under Server Intelligence Agent Port or accept the default port number -6410, and press Enter. .

To select a web application server configuration option
As part of the installation setup, you need to provide information on the web application server that will work with your BusinessObjects applications such as InfoView and the Central Management Console (CMC). Use the installer to specify to install Tomcat as your application server, or choose to work with your existing web application server. • Select one of the options listed below and press Enter.
Deployment option Install Tomcat, deploy web applications When to use If you do not have an existing web application server.

Use existing Java application If you have an existing supported web apserver, deploy web applica- plication server and you want to automatitions cally deploy the web applications. Use existing Java application If you have an existing supported web apserver, do not deploy web plication server and you want to manually applications deploy the web applications.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

67

4

New Installation Performing a new installation

If you have selected either the first or second option, you will now have to configure the web application server. If you have selected the third option you can start the installation process.
Related Topics

• • •

To start the installation on page 102 To configure your existing web application server on page 99 To configure the Tomcat installation on page 98

To configure the Tomcat installation
If you chose to install the Tomcat application server, the "Please enter port numbers for the Tomcat installation screen" is displayed. You must configure the server to use InfoView, the Central Management Console and other web application servers. 1. You can either choose to accept the default port numbers or provide new values for the following:
Required port numbers Receive HTTP requests Redirect jsp requests Shutdown hook

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

To start the installation on page 102

To configure your existing web application server
You must select the Use existing Java application server, deploy web applications option to view the "Select a Web Application Server to deploy to" screen. Select the server type before configuring your web application server.

68

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

New Installation Performing a new installation

4

1. Select your existing web application server from one of the following options and press Enter. • Tomcat 5.5 • WebLogic 10 • WebLogic 9 • WebSphere 6.1 • Oracle Application Server 10g R3 • Other If your existing web application server is SAP Application Server 7.0 or JBoss 4.04, select Other. If you select Other, you can begin the installation. If you selected one of the supported servers, you can now configure the server on a separate screen. 2. Provide the requested configuration details for your web application server and press Enter. The table below summarizes the information required for each supported web application server.
Web application server Apache Tomcat 5.5 Information required for installation setup • • Instance to install to: Name of the current web application server instance (for example “localhost”). Application server Installation directory: The directory where the web application server is installed (for example <INSTALLDIR>/wde ploy/appserver/Tomcat5520).

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

69

4

New Installation Performing a new installation

Web application server WebLogic 10

Information required for installation setup • • • • • Admin port: Administration port of the application server - mandatory for Weblogic (for example “7001”). Admin login: User name with administration rights to the application server - mandatory for Weblogic. Admin password: Password for account with administration rights to the application server - mandatory for Weblogic. Instance to install to: Name of the current web application server instance (for example “ mserver1”). Application server Installation directory: The directory where the web application server is installed (for example /bea/weblog ic10/user_projects/domains/base_domain). Note: For WebLogic the directory is the domain root.

WebLogic 9

• • • • •

Admin port: Administration port of the application server - mandatory for Weblogic (for example “7001”). Admin login: User name with administration rights to the application server - mandatory for Weblogic. Admin login: Password for account with administration rights to the application server - mandatory for Weblogic. Instance to install to: Name of the current web application server instance (for example “ mserver1”). Application server Installation directory: The directory where the web application server is installed (e.g /bea/user_projects/do mains/base_domain). Note: For WebLogic the directory is the domain root.

70

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

New Installation Performing a new installation

4

Web application server WebSphere 6.1

Information required for installation setup • • • • • • Admin port: The SOAP Connector Port of the application server (for example “8880”). Admin login: User name with administration rights to the WebSphere application server. Admin password: Password for account with administration rights to the application server. Instance to install to: Name of the current web application server instance (for example “ server1”). Virtual host: The virtual host to which the application must be bound. Admin is secure (y/n): Select this option to enable security requiring administrative access credentials to the application. Note: If Admin is secure is not selected you do not need to specify a username or a password. • Application Server Installation Directory: The directory where the web application server is installed (for example/IBM/Web Sphere/AppServer).

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

71

4

New Installation Performing a new installation

Web application server Oracle Application Server 10g R3

Information required for installation setup • Admin 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 the opmn.xml file. Admin login: User name with administration rights to the application server - mandatory for Oracle 10g R3. Admin password: Password for account with administration rights to the application server - mandatory for Oracle 10g R3. Admin is secure (y/n): Select this option only if you want Secure Sockets Layer (SSL) as part of the deployment. Note: If Admin is secure is not selected, you will still have to specify the username and password to access the server. • • Instance to install to: Name of the current web application server instance (for example “ home”). Application server Installation directory: The directory where the web application server is installed (for example /prod uct/10.1.3/OracleAS_1). Server Name: Name of the target application server (for example "myserver.domain.com"). Group Id: Name of the server group to which the target application belongs (for example "Default_group").

• • •

• • .

Related Topics

To start the installation on page 102

To start the installation
You are now ready to start the installation. 1. Review the installation directory specified on the screen.
Note: To modify the directory you would need to press [Ctrl-B] several

times until you reach the screen where you specify the installation directory.

72

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

New Installation Finishing a system installation

4

2. Press Enter to start the installation. The installation program will validate your system and install BusinessObjects Enterprise in the specified directory. When the new installation is finished, the setup program starts the servers as daemons and then enables each server that is registered with the CMS. To control the servers manually, use the ccm.sh script.
Related Topics

Using ccm.sh to start the BusinessObjects Enterprise servers on page 126

Finishing a system installation
If you chose to perform a system installation, the setup program script prompts you to run the BobjEnterprise120 script after it is finished. The BobjEnter prise120 script copies the run control scripts to your /sbin/rc# directories. When implemented, these run control scripts start/stop the BusinessObjects Enterprise servers on system startup/shutdown.
Note: To run the system installation, you must log on using a normal account.

After installation, however, you must have root privileges to run the se tupinit.sh script. This script copies the BobjEnterprise120 to the /sbin/rc# directory.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

73

4

New Installation Finishing a system installation

74

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Custom or Expand Installation

5

5

Custom or Expand Installation Performing a custom installation

Performing a custom installation
The Custom or Expand installation option allows you to selectively install specific features. You may want to perform a custom installation if you plan to use BusinessObjects Enterprise in a distributed environment. For example, your existing web application server resides on a different machine than the one hosting the BusinessObjects Enterprise core components. You customize the installation in the setup program Features screen. The Features screen contains a tree of features divided into the following top-level features: • • • • • • • Client Components Web Tier Components Server Components Database Access Export Support Samples Help Files

The markers in the tree indicate whether or not the feature and its subfeatures will be installed: • • • [X] means that the feature and all its subfeatures will be installed. [~] means that the feature and some of its subfeatures will be installed. [ ] means the feature will not be installed.

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

Features available in a custom installation
Client Components

This feature contains the Developer Components which has two subfeatures: • BusinessObjects Enterprise Java SDK: This is the development kit for Java applications.

76

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Custom or Expand Installation Performing a custom installation

5

BusinessObjects Enterprise Web Services SDK: This is the development kit for web services.

Web Tier Components

This feature contains the following subfeatures: • BI Platform Web Components: This includes all components used to run BusinessObjects XI 3.0 applications including Central Management Console, InfoView, Dashboard and Analytics, and Voyager. BusinessObjects Enterprise Web Services: This is a component of Business Objects Enterprise built for developers. It is composed of an implementation of web services that can be deployed with BusinessObjects Enterprise XI 3.0. Tomcat: If you do not have an existing web application server, you can choose to install Apache Tomcat 5.5.

Server Components

For a detailed explanation of what the listed servers do, please consult the “BusinessObjects Enterprise Architecture” chapter of the BusinessObjects Enterprise Administrator's Guide. Server Components contains the following subfeatures: • Central Management Server Contains the following subfeatures: • Auditor • MySQL Event Server Input File Repository Server Output File Repository Server Crystal Reports Cache Server Crystal Reports Processing Server Report Application Server Multi-Dimensional Analysis Services Server Crystal Reports Job Server Destination Job Server List of Values Job Server Program Job Server Adaptive Job Server

• • • • • • • • • • • •

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

77

5

Custom or Expand Installation Performing a custom installation

• • • • •

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

Database Access

This feature installs the necessary drivers and files to provide access to a broad range of data sources. It contains the following subfeatures: • • • • • Data Fedrator MySQL Generic ODBC NETEZZA ALL IBM Database Drivers contains the following subfeatures: • IBM DB2 • Informix Progress OpenEdge Oracle Sybase NCR Teradata

• • • •

Export Support

This feature contains drivers and files to enable export to a variety of industry standard file formats. It includes the following subfeatures: • • • • • • • • • • Character Separated Disk File Rich Text Format Word for Windows Acrobat PDF Text Excel Format Crystal Reports XML Format Legacy XML Format

78

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Custom or Expand Installation To perform a Custom or Expand installation

5

Samples

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

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

To perform a Custom or Expand installation
The Installation Type screen in the following procedure appears after you have completed the initial set up of the BusinessObjects Enterprise installation. 1. Select or deselect Enable servers after installation. This option is selected by default. Scroll down and use the spacebar to deselect the field. 2. Select Custom or Expand and press Enter. The "Features" screen is displayed with seven top level features. Expand any displayed features to drill down to display available sub features. 3. Deselect any features you do not want to install. a. Deselect the Tomcat subfeature under Web Tier Components if you want to use your existing web application server. b. Deselect Auditor under Server Components if you do not want to configure an auditing database. c. Deselect MySQL under Server Components if you want to use your existing database server. 4. After selecting what components you want to install press Enter. Consult the BusinessObjects Enterprise Administrator's Guide for information about scaling your deployment across multiple machines.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

79

5

Custom or Expand Installation To perform a Custom or Expand installation

Related Topics

• • •

Beginning your installation on page 55 Installing only the Web Tier Components on page 86 To install only the server components on page 80

To install only the server components
You would typically only install the server components onto a machine that you have set aside for use by BusinessObjects Enterprise. When you perform this installation scenario, the server components are installed, the default user and group accounts are created, and the sample reports are published to the system. When the installation is complete, the servers are automatically started. The Installation Type screen in the following procedure appears after you have completed the initial setup of the BusinessObjects Enterprise installation. 1. On the Installation Type screen, choose Custom or Expand. 2. Select the Server top level feature under BusinessObjects Enterprise. 3. Deselect the Client Components and Web Tier Component features.
Note: Ensure that the markers for the deselected features appear as [

]. 4. Deselect MySQL under Central Management Server if you plant to use an existing database server. 5. Deselect Auditor under Central Management Server if you do not want to configure and auditing database. 6. Press Enter to submit your selections. If you deselected the Central Management Server (CMS) feature, you must cluster the installed servers to an existing CMS. If you only deselected MySQL you must specify CMS clustering information. If you chose to Install MySQL, you must configure your new database.
Related Topics

• • • •

Beginning your installation on page 55 To cluster servers to an existing CMS on page 85 To specify CMS clustering information on page 82 To configure MySQL in a custom or expand installation on page 81

80

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Custom or Expand Installation To perform a Custom or Expand installation

5

To configure MySQL in a custom or expand installation
The "Enter the information for your new CMS" is displayed because you chose to install MySQL in the "Feature" screen. 1. Type a valid port number in CMS Port Number or accept the default value - 6400. 2. Type the same password under Administrator Password and Confirm Password and press Enter.
Note: You can also leave the passwords fields blank and configure the

password at a later time. Your password must be at least six characters long and should contain three of the following options • upper case character • lower case character • number • punctuation You need to provide configuration details for the new MySQL database. The setup program provides two screens to configure the MySQL database. 3. Provide the following information for your new MySQL database and press Enter. • MySQL Port Number • Database administrator password The second MySQL configuration screen is displayed. 4. Provide the following information for your new MySQL database and press Enter. • MySQL CMS Database Name • MySQL Audit Database Name • User ID
Note: This is the BusinessObjects Enterprise user account.

Password for user account

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

81

5

Custom or Expand Installation To perform a Custom or Expand installation

Related Topics

To enter Server Intelligence Agent information on page 85

To specify CMS clustering information
If you deselected MySQL in the "Features" screen, but want to install an Central Management Server (CMS), you need to provide more information on CMS clustering on your deployment 1. Select on of the following options and press Enter. • Yes - This is the first CMS in this deployment
Note: If you select this option you must provide information on your

new CMS. • No - Cluster this CMS with an existing CMS
Note: If you select this option you must provide information on the

existing CMS on which you are going to cluster the servers. 2. If you selected Yes in step 1: a. Type a valid port number in CMS Port Number or accept the default number - 6400. b. Type the same password under Administrator Password and Confirm Password and press Enter.
Note: You can also leave the passwords fields blank and configure

the password at a later time. Your password must be at least six characters long and should contain two of the following options • • • • upper case character lower case character number punctuation

c. You must now select and configure your database server. Skip to step 4. 3. If you selected No in step 1: a. You need to specify a valid unused port for the new CMS in New CMS Port. b. Type the system name of the CMS to which you are clustering in Existing CMS Hostname.

82

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Custom or Expand Installation To perform a Custom or Expand installation

5

c. Accept the default value -6400- or else type the port number in Existing CMS Port. d. Type the password or leave Existing CMS Administrator Password blank and press Enter. You must now select and configure your existing database server. 4. Select your database type. You can choose from the following • MySQL • Oracle • DB2 • Sybase A new screen displays containing fields for configuring your database. 5. Provide information about your database and press Enter. The table below lists the information required for each database type. Database type Information required

Host Name User ID for CMS database MySQL Password for CMS database MySQL port number Database name for CMS TNS name User ID for CMS database Oracle Password for CMS database CMS port number

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

83

5

Custom or Expand Installation To perform a Custom or Expand installation

Database type

Information required

Alias name User ID for CMS database DB2 Password for CMS database CMS port number Sybase Service name User ID for CMS database Sybase Password for CMS database CMS port number

6. If you deselected Auditor in the "Features" screen skip to step 7. Otherwise you must provide the following information about your new auditing database: Database type Information required

Auditing database name Auditing database port number Auditing User ID Password

7. Decide if you want to reinitialize the database and press Enter.
Note: Reinitialization of the BusinessObjects Enterprise database will

erase all previous content in that particular database.

84

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Custom or Expand Installation To perform a Custom or Expand installation

5

After configuring your CMS and auditing database, you are prompted for information on the Server Intelligence agent.
Related Topics

To enter Server Intelligence Agent information on page 85

To cluster servers to an existing CMS
If you deselected the Central Management Server feature, you will be prompted to cluster the servers you are installing to an existing CMS. 1. Provide the following information on the CMS to which you are clustering:
Field CMS Hostname Port Information required The system name of the machine on which the CMS is installed. Accept the default value -6400- or else type the port number used by the CMS.

Existing CMS Adminis- Provide the password by the CMS Administrator. trator Password

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

To enter Server Intelligence Agent information
The Server Intelligence Agent (SIA) simplifies the deployment and management of the BusinessObjects Enterprise servers. The SIA is automatically created during installation of BusinessObjects Enterprise XI 3.0. Use the installation setup program to configure the SIA. 1. Type a name in Server Intelligence Agent Node. Do not use spaces, dashes or periods in the node Name. This node name serves as an identifier for the SIA. 2. Type a valid port number under Server Intelligence Agent Port or accept the default port number -6410, and press Enter. .

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

85

5

Custom or Expand Installation To perform a Custom or Expand installation

To start the installation
You are now ready to start the installation. 1. Review the installation directory specified on the screen.
Note: To modify the directory you would need to press [Ctrl-B] several

times until you reach the screen where you specify the installation directory. 2. Press Enter to start the installation. The installation program will validate your system and install BusinessObjects Enterprise in the specified directory. When the new installation is finished, the setup program starts the servers as daemons and then enables each server that is registered with the CMS. To control the servers manually, use the ccm.sh script.
Related Topics

Using ccm.sh to start the BusinessObjects Enterprise servers on page 126

Installing only the Web Tier Components
You can chose to only install the Web Tier components while running a Custom or Expand installation. You would typically only install the Web Tier components on the machine running your web application server.
Tip: If you only want to only install Web Tier components, to save time and

avoid installing unnecessary components run a Web Applications installation.
Related Topics

To perform a web tier installation on page 96

To install only the Web Tier Components
The Installation Type screen in the following procedure appears after you have completed the initial set up of the BusinessObjects Enterprise installation.

86

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Custom or Expand Installation To perform a Custom or Expand installation

5

1. On the Installation Type screen, choose Custom or Expand. The Features screen is displayed 2. Select the Web Tier Components option under BusinessObjects Enterprise. 3. Deselect all the other top-level features by typing X in all the corresponding markers. Ensure that all the markers for the other top level features appear as []. 4. Deselect the Tomcat subfeature if you want to use your existing web application server and press Enter. You will be prompted to cluster your selected web tier components to an existing Central Management Server.
Related Topics

• •

Beginning your installation on page 55 To cluster web tier features to a CMS on page 97

To cluster web tier features to a CMS
You need to be able to connect to a running Central Management Server (CMS). After selecting what web tier features to install, you need to provide information on the CMS to which the feature will be clustered. 1. Specify the machine name where the CMS is installed in CMS Hostname. 2. Accept 6400 as the Port if that is number used by the CMS. Modify the value if your CMS is using another port. 3. Specify the password required for Administrator access to the CMS in Existing CMS Administrator Password. Press Enter.
Note: If no password is required, leave the field empty.

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

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

87

5

Custom or Expand Installation To perform a Custom or Expand installation

Select one of the options listed below and press Enter.
Deployment option Install Tomcat, deploy web applications When to use If you do not have an existing web application server.

Use existing Java application If you have an existing supported web apserver, deploy web applica- plication server and you want to automatitions cally deploy the web applications. Use existing Java application If you have an existing supported web apserver, do not deploy web plication server and you want to manually applications deploy the web applications.

If you have selected either the first or second option, you will now have to configure the web application server. If you have selected the third option you can start the installation process.
Related Topics

• • •

To start the installation on page 102 To configure your existing web application server on page 99 To configure the Tomcat installation on page 98

To configure the Tomcat installation
If you chose to install the Tomcat application server, the "Please enter port numbers for the Tomcat installation screen" is displayed. You must configure the server to use InfoView, the Central Management Console and other web application servers. 1. You can either choose to accept the default port numbers or provide new values for the following:
Required port numbers Receive HTTP requests Redirect jsp requests Shutdown hook

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

88

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Custom or Expand Installation To perform a Custom or Expand installation

5

Related Topics

To start the installation on page 102

To configure your existing web application server
You must select the Use existing Java application server, deploy web applications option to view the "Select a Web Application Server to deploy to" screen. Select the server type before configuring your web application server. 1. Select your existing web application server from one of the following options and press Enter. • Tomcat 5.5 • WebLogic 10 • WebLogic 9 • WebSphere 6.1 • Oracle Application Server 10g R3 • Other If your existing web application server is SAP Application Server 7.0 or JBoss 4.04, select Other. If you select Other, you can begin the installation. If you selected one of the supported servers, you can now configure the server on a separate screen. 2. Provide the requested configuration details for your web application server and press Enter. The table below summarizes the information required for each supported web application server.
Web application server Apache Tomcat 5.5 Information required for installation setup • • Instance to install to: Name of the current web application server instance (for example “localhost”). Application server Installation directory: The directory where the web application server is installed (for example <INSTALLDIR>/wde ploy/appserver/Tomcat5520).

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

89

5

Custom or Expand Installation To perform a Custom or Expand installation

Web application server WebLogic 10

Information required for installation setup • • • • • Admin port: Administration port of the application server - mandatory for Weblogic (for example “7001”). Admin login: User name with administration rights to the application server - mandatory for Weblogic. Admin password: Password for account with administration rights to the application server - mandatory for Weblogic. Instance to install to: Name of the current web application server instance (for example “ mserver1”). Application server Installation directory: The directory where the web application server is installed (for example /bea/weblog ic10/user_projects/domains/base_domain). Note: For WebLogic the directory is the domain root.

WebLogic 9

• • • • •

Admin port: Administration port of the application server - mandatory for Weblogic (for example “7001”). Admin login: User name with administration rights to the application server - mandatory for Weblogic. Admin login: Password for account with administration rights to the application server - mandatory for Weblogic. Instance to install to: Name of the current web application server instance (for example “ mserver1”). Application server Installation directory: The directory where the web application server is installed (e.g /bea/user_projects/do mains/base_domain). Note: For WebLogic the directory is the domain root.

90

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Custom or Expand Installation To perform a Custom or Expand installation

5

Web application server WebSphere 6.1

Information required for installation setup • • • • • • Admin port: The SOAP Connector Port of the application server (for example “8880”). Admin login: User name with administration rights to the WebSphere application server. Admin password: Password for account with administration rights to the application server. Instance to install to: Name of the current web application server instance (for example “ server1”). Virtual host: The virtual host to which the application must be bound. Admin is secure (y/n): Select this option to enable security requiring administrative access credentials to the application. Note: If Admin is secure is not selected you do not need to specify a username or a password. • Application Server Installation Directory: The directory where the web application server is installed (for example/IBM/Web Sphere/AppServer).

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

91

5

Custom or Expand Installation To perform a Custom or Expand installation

Web application server Oracle Application Server 10g R3

Information required for installation setup • Admin 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 the opmn.xml file. Admin login: User name with administration rights to the application server - mandatory for Oracle 10g R3. Admin password: Password for account with administration rights to the application server - mandatory for Oracle 10g R3. Admin is secure (y/n): Select this option only if you want Secure Sockets Layer (SSL) as part of the deployment. Note: If Admin is secure is not selected, you will still have to specify the username and password to access the server. • • Instance to install to: Name of the current web application server instance (for example “ home”). Application server Installation directory: The directory where the web application server is installed (for example /prod uct/10.1.3/OracleAS_1). Server Name: Name of the target application server (for example "myserver.domain.com"). Group Id: Name of the server group to which the target application belongs (for example "Default_group").

• • •

• • .

Related Topics

To start the installation on page 102

To start the installation
You are now ready to start the installation. 1. Review the installation directory specified on the screen.
Note: To modify the directory you would need to press [Ctrl-B] several

times until you reach the screen where you specify the installation directory. 2. Press Enter to start the installation.

92

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Custom or Expand Installation Finishing a system installation

5

The installation program will validate your system and install BusinessObjects Enterprise in the specified directory. When the new installation is finished, the setup program starts the servers as daemons and then enables each server that is registered with the CMS. To control the servers manually, use the ccm.sh script.
Related Topics

Using ccm.sh to start the BusinessObjects Enterprise servers on page 126

Finishing a system installation
If you chose to perform a system installation, the setup program script prompts you to run the BobjEnterprise120 script after it is finished. The BobjEnter prise120 script copies the run control scripts to your /sbin/rc# directories. When implemented, these run control scripts start/stop the BusinessObjects Enterprise servers on system startup/shutdown.
Note: To run the system installation, you must log on using a normal account.

After installation, however, you must have root privileges to run the se tupinit.sh script. This script copies the BobjEnterprise120 to the /sbin/rc# directory.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

93

5

Custom or Expand Installation Finishing a system installation

94

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Web Applications Installation

6

6

Web Applications Installation Performing web tier installations

Performing web tier installations
The web tier installation type installs the appropriate web tier components on the machine running your web application server. You will need user account and port information to configure your web application server through the BusinessObjects Enterprise 3.0 setup program. The web application server processes scripts, communicates with report and cache servers, translates cached files to DHTML, facilitates OLAP view requests and manages session state information for users. A distributed installation has two stages. The first step is done on the machine where the BusinessObjects Enterprise components will reside. The second step is to install the Web Tier Components on the machine where the web server is installed.
Note:

• •

It is best practice to install the server and client components to verify connectivity. Java SDK 1.5 is installed by default when you install the Web Tier Components.

To perform a web tier installation
The Installation Type screen in the following procedure appears after you have completed the initial set up of the BusinessObjects Enterprise installation. 1. Select or deselect Enable servers after installation. This option is selected by default. Scroll down and use the spacebar to deselect the field. 2. Select Install Web Tier features and press Enter. The "Features" screen is displayed. 3. Expand Web Tier Components to specify which features to install.
Tip: Deselect the Tomcat subfeature if you want to use your existing

web application server. 4. Press Enter to submit your selection.

96

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Web Applications Installation Performing web tier installations

6

You must now cluster the selected components to an existing Central Management Server (CMS).
Related Topics

Beginning your installation on page 55

Features available in a web tier installation
• BI Platform Web Components: This includes all components used to run BusinessObjects XI 3.0 applications including Central Management Console, Infoview, Dashboard and Analytics, and Voyager. BusinessObjects Enterprise Web Services: This is a component of Business Objects Enterprise built for developers. It is composed of an implementation of web services that can be deployed with BusinessObjects Enterprise XI 3.0. This web service implementation provides an API/WSDL which simplifies the process of developing applications. Tomcat: If you do not have an existing web application server, you can choose to install Apache Tomcat 5.5.

To cluster web tier features to a CMS
You need to be able to connect to a running Central Management Server (CMS). After selecting what web tier features to install, you need to provide information on the CMS to which the feature will be clustered. 1. Specify the machine name where the CMS is installed in CMS Hostname. 2. Accept 6400 as the Port if that is number used by the CMS. Modify the value if your CMS is using another port. 3. Specify the password required for Administrator access to the CMS in Existing CMS Administrator Password. Press Enter.
Note: If no password is required, leave the field empty.

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

97

6

Web Applications Installation Performing web tier installations

To select a web application server configuration option
As part of the installation setup, you need to provide information on the web application server that will work with your BusinessObjects applications such as InfoView and the Central Management Console (CMC). Use the installer to specify to install Tomcat as your application server, or choose to work with your existing web application server. • Select one of the options listed below and press Enter.
Deployment option Install Tomcat, deploy web applications When to use If you do not have an existing web application server.

Use existing Java application If you have an existing supported web apserver, deploy web applica- plication server and you want to automatitions cally deploy the web applications. Use existing Java application If you have an existing supported web apserver, do not deploy web plication server and you want to manually applications deploy the web applications.

If you have selected either the first or second option, you will now have to configure the web application server. If you have selected the third option you can start the installation process.
Related Topics

• • •

To start the installation on page 102 To configure your existing web application server on page 99 To configure the Tomcat installation on page 98

To configure the Tomcat installation
If you chose to install the Tomcat application server, the "Please enter port numbers for the Tomcat installation screen" is displayed. You must configure the server to use InfoView, the Central Management Console and other web application servers.

98

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Web Applications Installation Performing web tier installations

6

1. You can either choose to accept the default port numbers or provide new values for the following:
Required port numbers Receive HTTP requests Redirect jsp requests Shutdown hook

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

To start the installation on page 102

To configure your existing web application server
You must select the Use existing Java application server, deploy web applications option to view the "Select a Web Application Server to deploy to" screen. Select the server type before configuring your web application server. 1. Select your existing web application server from one of the following options and press Enter. • Tomcat 5.5 • WebLogic 10 • WebLogic 9 • WebSphere 6.1 • Oracle Application Server 10g R3 • Other If your existing web application server is SAP Application Server 7.0 or JBoss 4.04, select Other. If you select Other, you can begin the installation. If you selected one of the supported servers, you can now configure the server on a separate screen. 2. Provide the requested configuration details for your web application server and press Enter.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

99

6

Web Applications Installation Performing web tier installations

The table below summarizes the information required for each supported web application server.
Web application server Apache Tomcat 5.5 Information required for installation setup • • Instance to install to: Name of the current web application server instance (for example “localhost”). Application server Installation directory: The directory where the web application server is installed (for example <INSTALLDIR>/wde ploy/appserver/Tomcat5520). Admin port: Administration port of the application server - mandatory for Weblogic (for example “7001”). Admin login: User name with administration rights to the application server - mandatory for Weblogic. Admin password: Password for account with administration rights to the application server - mandatory for Weblogic. Instance to install to: Name of the current web application server instance (for example “ mserver1”). Application server Installation directory: The directory where the web application server is installed (for example /bea/weblog ic10/user_projects/domains/base_domain). Note: For WebLogic the directory is the domain root. WebLogic 9 • • • • • Admin port: Administration port of the application server - mandatory for Weblogic (for example “7001”). Admin login: User name with administration rights to the application server - mandatory for Weblogic. Admin login: Password for account with administration rights to the application server - mandatory for Weblogic. Instance to install to: Name of the current web application server instance (for example “ mserver1”). Application server Installation directory: The directory where the web application server is installed (e.g /bea/user_projects/do mains/base_domain). Note: For WebLogic the directory is the domain root.

WebLogic 10

• • • • •

100

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Web Applications Installation Performing web tier installations

6

Web application server WebSphere 6.1

Information required for installation setup • • • • • • Admin port: The SOAP Connector Port of the application server (for example “8880”). Admin login: User name with administration rights to the WebSphere application server. Admin password: Password for account with administration rights to the application server. Instance to install to: Name of the current web application server instance (for example “ server1”). Virtual host: The virtual host to which the application must be bound. Admin is secure (y/n): Select this option to enable security requiring administrative access credentials to the application. Note: If Admin is secure is not selected you do not need to specify a username or a password. • Application Server Installation Directory: The directory where the web application server is installed (for example/IBM/Web Sphere/AppServer).

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

101

6

Web Applications Installation Performing web tier installations

Web application server Oracle Application Server 10g R3

Information required for installation setup • Admin 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 the opmn.xml file. Admin login: User name with administration rights to the application server - mandatory for Oracle 10g R3. Admin password: Password for account with administration rights to the application server - mandatory for Oracle 10g R3. Admin is secure (y/n): Select this option only if you want Secure Sockets Layer (SSL) as part of the deployment. Note: If Admin is secure is not selected, you will still have to specify the username and password to access the server. • • Instance to install to: Name of the current web application server instance (for example “ home”). Application server Installation directory: The directory where the web application server is installed (for example /prod uct/10.1.3/OracleAS_1). Server Name: Name of the target application server (for example "myserver.domain.com"). Group Id: Name of the server group to which the target application belongs (for example "Default_group").

• • •

• • .

Related Topics

To start the installation on page 102

To start the installation
You are now ready to start the installation. 1. Review the installation directory specified on the screen.
Note: To modify the directory you would need to press [Ctrl-B] several

times until you reach the screen where you specify the installation directory.

102

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Web Applications Installation Performing web tier installations

6

2. Press Enter to start the installation. The installation program will validate your system and install BusinessObjects Enterprise in the specified directory. When the new installation is finished, the setup program starts the servers as daemons and then enables each server that is registered with the CMS. To control the servers manually, use the ccm.sh script.
Related Topics

Using ccm.sh to start the BusinessObjects Enterprise servers on page 126

Finishing a system installation
If you chose to perform a system installation, the setup program script prompts you to run the BobjEnterprise120 script after it is finished. The BobjEnter prise120 script copies the run control scripts to your /sbin/rc# directories. When implemented, these run control scripts start/stop the BusinessObjects Enterprise servers on system startup/shutdown.
Note: To run the system installation, you must log on using a normal account.

After installation, however, you must have root privileges to run the se tupinit.sh script. This script copies the BobjEnterprise120 to the /sbin/rc# directory.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

103

6

Web Applications Installation Performing web tier installations

104

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Silent Installation

7

7

Silent Installation Overview

Overview
There are two methods for running BusinessObjects Enterprise installations for UNIX directly from the command line: • • Silent installation using a response file - referred to as a scripted installation in this guide Silent installation specifying parameters directly on the command line

Both methods can be used to automate installations across multiple machines. The scripted installation requires you to specify a response file. The silent installation allows you to specify parameters for running the ./install.sh command.
Note: The silent installation without the response file is not recommended

for custom installations. This method does not allow for the same level of customization provided when using a response file. These installation types are particularly useful when you need to perform multiple installations, as you can save time and avoid being prompted for information by the installation setup program. You can also integrate the scripts and commands into your own installation scripts.
Related Topics

• •

Performing a scripted installation on page 106 Performing a silent installation on page 117

Performing a scripted installation
While setting up an installation process on UNIX, you can write installation settings to a specified response file. The file is generated once the installation setup program is ready to start the installation. The response file supports all three BusinessObjects Enterprise installation types available for UNIX: • New • Custom or Expand • Web Tier

106

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Silent Installation Performing a scripted installation

7

Tip: You do not start the installation process to generate the response file.

Select Ctrl-X to abort the installation setup once you reach the final screen in the installation setup program.

To create a response file
1. Mount the device that contains the installation files.
Note: If you run the installation script without copying the files to a

temporary location, you will be prompted to specify a temporary location for the installation. 2. In the command line type ./install.sh, -w and the file path the response file you want to generate.
./install.sh -w responseFilePath

Note: When specifying responseFilePath make sure you include the

name of the file you want to generate. 3. Press Enter to launch the installation setup program. 4. Follow the onscreen instructions to enter your preferred installation settings until you reach the final screen of the setup program. These settings are recorded in the response file. 5. Press [Ctrl-X] to abort the installation setup once you reach the final screen in the installation setup program. You can access the response file from the directory you specified in step 2.
Related Topics

Running the product distribution directly from a CD on page 54

To run a scripted installation
You need to have a response residing in a known directory. The MACHINE NAME parameter must be specified in the response file if you are replicating an installation. If the parameter is not specified, the local server name will be used by default. 1. Mount the device that contains the installation files.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

107

7

Silent Installation Performing a scripted installation

Note: If you run the install script without copying the files to a temporary

location, you will be prompted to specify a temporary location for the install. 2. In the command-line type the following information:
install.sh -r response.ini -I /installDirectory/ -s /cd/setup/DISK_1/

• • •

-r <filename> Specifies the name of the response file you want the

installation setup to read for installation parameters. -I <INSTALLDIR> Specifies the installation directory for the scripted installation. -s <SOURCEDIR> This optional command specifies the location of the cd directory. The source directory must point to the location of DISK_1 in the installation CD. If not specified, the CD directory setting in the response file will be used.

3. Press Enter to launch the installation.
Related Topics

Copying the product distribution to your machine on page 54

Scripted installation parameters
The table below lists the most common parameters used in BusinessObjects Enterprise installation scripts. These parameters are saved in a file which is used to run scripted installations of BusinessObjects Enterprise on UNIX. To change the listed parameters, it is recommended that you create a new response file using ./install.sh and the -w parameter.
Parameter Description Name of the machine on which to run the scripted installation. The setting overrides the local server name. If not specified, the local machine name is used.
MACHINENAME="mymachine"

MACHINENAME

108

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Silent Installation Performing a scripted installation

7

Parameter

Description Path of the bobje directory automatically setup in the installation directory.
BOBJEDIR="<INSTALLDIR>/bobje/"

BOBJEDIR

CDDIR

Path to the DISK_1 directory on the distribution CD. This path defaults to the CD directory.
CDDIR="<CD>/BusinessOb jects/DISK_1"

Path to the directory containing the product license. LICENSEDIR
LICENSEDIR="<INSTALLDIR>/<LI CENSEDIR/"

BOBJELANG

The language setting used for the installation setup. • en=English • chs=Simplified Chinese • cht=Traditional Chinese • de=German • es=Spanish • ko=Korean • nl=Dutch • jp=Japanese • pt=Portuguese • sv=Swedish • ru=Russian • fr=French
BOBJELANG="en"

Specifies the product activation keycode for the product to be installed. BOBJELICENSEKEY
BOBJELICENSEKEY=XXXXX-XXXXXXXXXXXXXX

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

109

7

Silent Installation Performing a scripted installation

Parameter

Description The product id key - same as the BOB

PIDKEY

JELICENSEKEY PIDKEY =XXXXX-XXXXXXX-XXXXXXX

INSTALLTYPE

Specifies the type of installation to perform. This parameter supports the following options: • new • custom • webtier
INSTALLTYPE="new"

INSTALLMODE

Specifies a comma-delimited list for the BusinessObjects Enterprise installer operating modes. This parameter supports the following options: • install • modify • remove • integrated • interactive
INSTALLMODE=interactive,install

Specifies the name of the local server LOCALNAMESERVER
LOCALNAMESERVER=“myservername”

BOBJEINSTALLLOCAL

Specifies to perform either a user or system installation.
BOBJEINSTALLLOCAL=“user”

110

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Silent Installation Performing a scripted installation

7

Parameter

Description Specifies the language packs to install. Each language pack is specified in the short format and is separated by a space. • en=English • zh_CN=Simplified Chinese • zh_TW=Traditional Chinese • de=German • es=Spanish • ko=Korean • nl=Dutch • jp=Japanese • pt=Portuguese • sv=Swedish • ru=Russian • fr=French
LANGPACKS_TO_INSTALL=“en fr”

LANGPACKS_TO_INSTALL

BOBJEUSERNAME

Specifies the Business Objects Enterprise username.
BOBJEUSERNAME=“username”

INSTALLTOMCAT

Specifies to either install or not to install Tomcat.
INSTALLTOMCAT=“yes”

CONNECTORPORT

Specifies the connection port for the Tomcat server.
CONNECTORPORT=“15037”

REDIRECTPORT

Specifies the redirection port for the Tomcat server.
REDIRECTPORT=“15034”

SHUTDOWNPORT

Specifies the shutdown port for the Tomcat server.
SHUTDOWNPORT=“15024”

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

111

7

Silent Installation Performing a scripted installation

Parameter

Description Specifies the path of the application server directory if the server is being installed. The path is automatically set using the installation directory.
AS_DIR=“<INSTALLDIR>/bobje/tom cat/”

AS_DIR

AS_SERVER

Specifies the name of the application server being installed. • Use tomcat55 for Tomcat • Use oas1013 for Oracle Application Server 10g R3 • Use weblogic9 for WebLogic 9 • Use weblogic10 for WebLogic 10 • Use websphere6 for WebSphere 6.1
AS_SERVER=“tomcat55”

AS_INSTANCE

Specifies the name of the current web application server instance.
AS_INSTANCE="localhost"

AS_VIRTUAL_HOST

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

AS_ADMIN_PORT

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

AS_ADMIN_USERNAME

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

112

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Silent Installation Performing a scripted installation

7

Parameter

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

AS_ADMIN_PASSWORD

AS_ADMIN_IS_SECURE

Specifies is administrator credential must be passed to access the web application server. This setting only valid for WebSphere 6 and Oracle.
AS_ADMIN_IS_SECURE="true"

WDEPLOYACTION

Specifies the action to perform on the application server. The available options are: • deploy • predeploy • none
WDEPLOYACTION=“deploy”

CMSCLUSTER

Specifies whether or not to cluster to an existing CMS.
CMSCLUSTER=“no”

CLUSTER_NAMESERVER

If clustering to a CMS, specifies the name of the CMS .
CLUSTER_NAMESERVER=“name”

CLUSTERPORTNUMBER

If clustering to a CMS, specifies the port number used by the CMS.
CLUSTERPORTNUMBER=“6400”

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

113

7

Silent Installation Performing a scripted installation

Parameter

Description Specifies the type of database used by the CMS. The available options are: • MySQL • DB2 • Oracle • Sybase
DBTYPE=“MySQL”

DBTYPE

Specifies the service name for the CMS. SERVICENAME
SERVICENAME=“BOE953”

DATABASEUID

Specifies the username used to connected to the database.
DATABASEUID=“username”

DATABASEPWD

Specifies the password used to connected to the database.
DATABASEPWD=“password”

Specifies the name of the CMS server. CMSNAMESERVER
CMSNAMESERVER=“servername”

CMSPORTNUMBER

Specifies the port number used to communicate with the CMS.
CMSPORTNUMBER=“14000”

CMSPASSWORD

Specifies the password used to connect to the CMS.
CMSPASSWORD=“password”

SIANODENAME

Specifies the node name for the Server Intelligence Agent (SIA).
SIANODENAME=“name”

114

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Silent Installation Performing a scripted installation

7

Parameter

Description Specifies the port used by the Server Intelligence Agent.
SIAPORTNUMBER=“14090”

SIAPORTNUMBER

REINIT

Specifies to or not to reinitialize the database.
REINIT=“yes”

INSTALLMYSQL

Specifies to or not to install MySQL as the system database.
INSTALLMYSQL“yes”

SERVICEPORT

Specifies the port number used to communicate with the MySQL database.
SERVICEPORT=“15036”

MYSQLYHOSTNAME

Specifies the name of the server hosting the MySQL database.
MYSQLYHOSTNAME=“servername”

MYSQLROOTPWD

Specifies the root password for the MySQL database.
MYSQLROOTPWD=“password”

AUDITINGENABLED

Specifies if auditing is or is not enabled for the CMS.
AUDITINGENABLED=“yes”

SERVICENAME_AUDIT

Specifies the service audit name used by the CMS.
SERVICENAME_AUDIT=“servicename”

SERVICEPORT_AUDIT

Specifies the port number used to communicate with the auditing database.
SERVICEPORT_AUDIT=“12133”

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

115

7

Silent Installation Performing a scripted installation

Parameter

Description Specifies the name of the server hosting the MySQL auditing database.
MYSQLHOSTNAME_AUDIT=“servername”

MYSQLHOSTNAME_AUDIT

DATABASEUID_AUDIT

Specifies the user name used to connect to the auditing database.
DATABASEUID_AUDIT=“username”

DATABASEPWD_AUDIT

Specifies the password used to connect to the auditing database.
DATABASEPWD_AUDIT=“password”

-ENABLEMP

Specifies which specific products to manually enable. Each product must be separated by a comma. For a custom installation this setting is used to enable those products typically not installed in a new installation.
ENABLEMP=BusinessObjects.WebTier Components,

-DISABLEMP

Specifies which specific products to manually disable. Each product must be separated by a comma. For a custom in stallation this setting is used to disable those products typically not installed in a new installation.
DISABLEMP=ENABLEMP=BusinessOb jects.WebTierComponents,

Other automatically generated parameters

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

116

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Silent Installation Performing a silent installation

7

Parameter name PRODUCTID_NAME BOBJEVERSION PRODUCTID_VER FUNCTION LANGUAGES_TO_INSTALL EXPANDSERVERS Related Topics

To create a response file on page 107

Performing a silent installation
You can run a silent installation from the command line to automatically install BusinessObjects Enterprise on any machine in your system, without the installation program prompting for information during the installation. To install silently, run the ./install.sh script, adding parameters that provide information for installation settings and directory paths. This type of installation is particularly useful when you need to perform multiple installations. You can also use the silent installation script in your own scripts. For example, if your organization uses scripts to install software on machines, you can add the silent BusinessObjects Enterprise installation command to your scripts. The silent installation command consists of the ./install.sh script, followed by the location of the installation executable file, and a number of parameters that provide information about the installation. For example: The following example would perform an English new user installation with the following configuration: • • • • BusinessObjects Enterprise Tomcat MySQL Auditor

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

117

7

Silent Installation Performing a silent installation

Database reinitialized

./install.sh -c en -INSTALLDIR /program/business/ boe_120 -BOBJELICENSEKEY00000-1111111-2222222-0000 -BOBJEINSTALLLOCAL user -INSTALLTYPE new -CMSPORTNUMBER 13888 -DBTYPE MySQL -SERVICENAME boe -INSTALLMYSQL yes -DATABASEUID username -DATABASEPWD sa -REINIT yes -MYSQLROOTPWD sa -SERVICENAME_AUDIT audit -DATABASEUID_AUDIT hsmith -DATABASEPWD_AUDIT sa123 -INSTALLTOMCAT yes -TOMCATCONNECTORPORT 13890 -TOMCATREDIRECTPORT 13889 -TOMCATSHUTDOWNPORT 13891 -AUDITINGENABLED yes -DASENABLED yes

Note: The example uses the most common parameters. You can choose

any number of valid parameters, but it is good practice to keep the silent installation as simple as possible. Note that when you run a silent installation, you need to run the command once for each CD, but you only need to provide the full list of options for the first CD. For example, if the CDs are on different drives, the commands could look like the following:
./install.sh -s /mnt/cd1 -INSTALLDIR /mymachine/ BOBJ/Enterprise120 -BOBJELICENSEKEY 00000-0000000-0000000-0000 -INSTALLTYPE new -BOBJEINSTALLLOCAL user -CMSPORTNUMBER 6401 -DBTYPE Oracle -SERVICENAME tnsname -DATABASEUID userid -DATABASEPWD password -REINIT yes -INSTALLTOMCAT yes -TOMCATCONNECTORPORT 8080 -TOMCATREDIRECTPORT 8443 -TOMCATSHUTDOWNPORT 8005 ./install.sh -s /mnt/cd2 -INSTALLDIR /mymachine/BOBJ/ Enterprise120 ./install -s /mnt/cd3 -INSTALLDIR /mymachine/BOBJ/Enterprise120

The following table lists the most common parameters used in a silent installation. To use a parameter, place it on the command line after the ./install.sh command and the path for the installation files.
Note: Parameter values are case-sensitive.

118

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Silent Installation Performing a silent installation

7

Installation parameter

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

-sfilepath

-INSTALLDIR filepath

Specifies the directory where you want to install the new BusinessObjects Enterprise components. Replace filepath with the full path for the installation directory. For example, -INSTALLDIR /BOBJE/En terprise120. Required to activate the product license for your product. Enables you to install Dashboard and Analytics servers without a keycode. The options are “yes” and “no”; the default setting is “no”.

-BOBJELICENSEKEY 00000-00000000000000-0000

-DASENABLED

Note: The Dashboard and Analytics servers will be disabled until you enter an appropriate keycode through the Central Management Console (CMC). This option determines the language for the installation. Replace languagecode with a language code for one of the supported languages: • en=English • zh_CN=Simplified Chinese • zh_TW=Traditional Chinese • de=German • es=Spanish • ko=Korean • nl=Dutch • jp=Japanese • ru=Russian • fr=French Specifies the Server Intelligence Agent (SIA) node name to use for the installation.

-clanguage code

-SIANODENAME

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

119

7

Silent Installation Performing a silent installation

Installation parameter
-SIAPORTNUMBER

Description Specifies the port used by the SIA. Specifies the type of installation. The possible values are: • new • custom • webtier This parameter is followed by a comma-separated values (CSV) string of features that you do not want to install. Note that this cannot be used in combination with the -f option. See the mymenu.xml file in the setup directory on DISK_1 for a full list of features. This parameter is followed by CSV string of features that you want to install. Note that this cannot be used in combination with the -x option. See the mymenu.xml file in the setup directory on DISK_1 for a full list of features. Specifies which specific products to manually enable. Each product must be separated by a comma. For a custom installation this setting is used to enable those products typically not installed in a new installation. Specifies whether to perform a user or a system installation. The options are user or system; user is the default. Specifies the name of an existing CMS to use for either a custom or web tier installation. Specifies the port number for the Central Management Server. If not specified, the default is 6400. Specifies the administrator password for an existing CMS to use in either a custom or web tier installation.

-INSTALLTYPE

-xmymenu.xml

-f

-ENABLEMP

-BOBJEINSTALLLOCAL

-CMSNAMESERVER

-CMSPORTNUMBER

-CMSPASSWORD

120

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Silent Installation Performing a silent installation

7

Installation parameter

Description When installing a Central Management Server, you need to specify the type of database you want to use. Possible values include: • Oracle • DB2 • Sybase • MySQL When installing a Central Management Server, you can specify whether or not to install and configure a new MySQL database. The options are yes or no; no is the default. Specifies the name of the machine hosting the MySQL server. Specifies the service name used to connect to the Central Management Server database. Specifies the port number used to connect to the Central Management Server database. This is required only for MySQL databases. Specifies the user ID used to connect to the Central Management Server database. This option cannot be set to root if the -INSTALLMYSQL option is set to yes. Specifies the password used to connect to the Central Management Server database. If this option is not specified, it defaults to blank. Specifies the password used for the root account when setting up the database. When the -INSTALLMYSQL option is set to yes, you must also specify the -MYSQLROOTPWD option. Specifies if the an auditing database will be configured the during your installation setup. The two options are yes and no. If this option is not specified, it defaults to no.

-DBTYPE

-INSTALLMYSQL

-MYSQLHOSTNAME

-SERVICENAME

-SERVICEPORT

-DATABASEUID

-DATABASEPWD

-MYSQLROOTPWD

-AUDITINGENABLED

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

121

7

Silent Installation Performing a silent installation

Installation parameter

Description Modifies the name of the MySQL auditing database, otherwise, the default name of BOE120_Audit will be used Use this parameter to pass the user ID for the auditing database. Specifies the password for the auditing database server. Specifies the host name for the MySQL server for your auditing database. Specifies an existing auditing database type from one of the following options: • Oracle • DB2 • Sybase • MySQL Specifies the port for the MySQL auditing database server. Specifies the name of the machine hosting the Sybase auditing database. Specifies the port number used by the Sybase auditing database. Specifies whether to reinitialize the Central Management Server database. The options are yes or no;yes is the default. Specifies whether or not to cluster the Central Management Server with an existing CMS. The options are yes or no; no is the default. Note: This option is used for a custom installation.

-SERVICENAME_AUDIT

-DATABASEUID_AUDIT

-DATABASEPWD_AUDIT

-MYSQLHOSTNAME_AUDIT

-DBTYPE_AUDIT

-SERVICEPORT_AUDIT

-SYBASEHOSTNAME_AUDIT

-SYBASEPORT_AUDIT

-REINIT

-CLUSTERCMS

122

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Silent Installation Performing a silent installation

7

Installation parameter

Description Specifies the name of the Central Management Server for the system you are expanding. For a custom installation, if the -CLUSTERCMS option is set to yes, then you need to specify the name of the CMS you want to cluster with. Specifies the port number of the Central Management Server for the system you are expanding. The default is 6400. For a custom installation, if the -CLUSTERCMS option is set to yes, then you need to specify the port number of the CMS you want to cluster with. The default is 6400. Specifies if Tomcat is to be installed as the web applications server. The default value is no. The port number that Tomcat uses to connect. The default is 8080. The port number that Tomcat uses to redirect. The default is 8443. The port number that Tomcat uses to shut down. The default is 8005.

-CLUSTER_NAMESERVER

-CLUSTERPORTNUMBER

-INSTALLTOMCAT

-TOMCATCONNECTORPORT

-TOMCATREDIRECTPORT

-TOMCATSHUTDOWNPORT

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

123

7

Silent Installation Performing a silent installation

124

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

After Installing BusinessObjects Enterprise

8

8

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

Using ccm.sh to start the BusinessObjects Enterprise servers
The ccm.sh script provides you with a command-line interface to the various BusinessObjects Enterprise server components. For more information about this script and others that are installed on your system, see the BusinessObjects Enterprise Administrator's Guide. In BusinessObjects Enterprise, the installation setup program starts and enables servers automatically. The following information is included only as a reference.

To manually start and enable servers
1. Go to the bobje directory that was created by the installation:
cd <INSTALLDIR>/bobje

2. Start the Server Intelligence Agent (SIA) by typing the following command:
./ccm.sh -start sia

3. Open a web browser to the URL of your Central Management Console (CMC) deployment on your web application server. For example
http://<SERVERNAME>:<PORTNUMBER>/CmcApp

4. Log on to the CMC by providing your BusinessObjects Administrator credentials. 5. Navigate to the "Servers" page. 6. Select the server you want to start. 7. Select Start Server. The server should now start.

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

126

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

After Installing BusinessObjects Enterprise Setup for performance management

8

InfoView is a web-based interface that end users access to view, schedule, and keep track of published reports. The Central Management Console (CMC) allows you to perform user and server management tasks such as setting up authentication, starting servers, and adding users and groups. The BusinessObjects Enterprise SDKs are used by many BusinessObjects Enterprise components and are also used to simplify the development of custom BusinessObjects Enterprise applications. If you do not install Tomcat when you install BusinessObjects Enterprise, these components must configured and deployed before you use them. You can either deploy the components manually or use the wdeploy tool. For more information about the system architecture of an installation of BusinessObjects Enterprise, see the architecture chapter of the BusinessObjects Enterprise Administrator's Guide.
Note: If you have a firewall between the machine running your web

application server and your other BusinessObjects Enterprise servers, you must perform additional system configuration. See the section on how to configure firewalls, in your BusinessObjects Enterprise Administrator's Guide.
Related Topics

• • •

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

Setup for performance management
Before users in your organization can start working with performance management, you need to do the following: • Create the performance management repository – this repository stores the metrics, goals, sets, and calendars that users leverage for their performance management analysis. Define system users – this enables the performance management application engines. Define connections to the metrics universes and push those universes to the performance management repository – this makes the metadata for measures and dimensions available to users for metric creation.

• •

.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

127

8

After Installing BusinessObjects Enterprise Setup for performance management

To set up performance management
1. Log into InfoView, then click Open. A drop-down list is displayed. 2. Select Dashboard & Analytics Setup. The Dashboard & Analytics Setup page is displayed. 3. Follow the on-screen instructions.

Troubleshooting starting performance management
If, when you launch performance management, you receive an error message saying that you cannot connect to performance management, this may mean one of the following: • • Some of the performance management servers are stopped or disabled. The Initialization User that creates the performance management server proxies may be defined inconsistently in the CMS, InfoView, and the InitConfig.properties file.

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

To verify the Initialization User
1. On your performance management server, open the InitConfig.prop erties file and verify that the Initialization user name and password match those in the CMS.

128

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

After Installing BusinessObjects Enterprise Setup for performance management

8

This file is at: <INSTALLDIR>/bobje/performance_management_120 The strings to search for are: • •
initialization.User= initialization.Password=

2. Log into InfoView, and then click the Preferences button on the InfoView toolbar. 3. Click the Performance Management tab, and then check the name of the initialization logon user in the Change initialization logon user section is the same as the user name specified in the InitConfig.prop erties file. 4. Log into the Log into the Central Management Console (CMC), and then click Users. 5. Check that the user defined in the InitConfig.properties is listed among the users. 6. From the CMC home page, click Settings > Rights and check that the initialization user has the appropriate rights.
Note: For security reasons, it is recommended that you do not provide

a real user ID for the initialization user. The default user ID is PMUser. You need to restart the performance management servers. 7. From the CMC home page, click Servers > Start Servers to restart all servers. If you are using performance management from a client machine - different from the machine hosting the performance manager server - you need to restart your computer.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

129

8

After Installing BusinessObjects Enterprise Setup for performance management

130

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Language Packs on UNIX

9

9

Language Packs on UNIX About language packs

About language packs
A language pack is a resource package that gives a BusinessObjects Enterprise system the ability to interact with users in a specific language. An individual language is known as a locale. You can install as many different language packs as you want. The default language pack, English, is always installed.

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

Product locale changes
Product Locale changes are immediately reflected in the current product's interface, 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 Japanese will cause the Business Intelligence Modeler client to also display in Japanese. However, if the Business Intelligence Modeler is running at the time of the change, it must be restarted in order for the change to take effect.

Selecting a language
Once installed, BusinessObjects Enterprise products detect the existence of the language pack, and users can choose a language from a list of installed languages found in the Product Locale drop-down list of the CMC Preferences section of the CMC Preferences, or under the Options dialog box on the toolbar or application menu in other BusinessObjects Enterprise products. Command-line utilities use the LANG environment variable to determine which language to use.

132

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Language Packs on UNIX Installing language and complex deployments

9

Each language listed in the Product Locale drop-down is displayed in its native localization, rather than the currently employed language. For example, the German language pack is always displayed as Deutsch, rather than as German 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 mapped to the Save command, regardless of the localized name for the Save function.

Installing language and complex deployments
If your organization uses a BusinessObjects Enterprise deployment with more than one server, you will need to deploy language packs to each server individually.

Installing language packs on UNIX systems
Language packs can be installed either during the initial installation of BusinessObjects Enterprise, or post-install using a dedicated language pack installer. The installer is a script that adds the localized language resources to your Business Objects software deployment. English is the default option during the installation of BusinessObjects Enterprise, but administrators can opt to install any or all of the other available languages. Additional languages can also be installed onto an existing system by downloading the appropriate language pack from the Business Objects support web site at http://technicalsupport.businessobjects.com. In the event of an operational problem with a language pack, BusinessObjects Enterprise will default back to English localization. Because of this fall-back system, English cannot be deselected as an installable option during the installation of BusinessObjects Enterprise.
Note: An error message will be displayed if a language pack detects that it

is incompatible with a previously installed version of BusinessObjects Enterprise.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

133

9

Language Packs on UNIX Locating language packs

Locating language packs
Language packs can be found in the langs folder of the BusinessObjects Enterprise for UNIX distribution package. Alternatively, language packs can be downloaded from the Business Objects technical support site at http://technicalsupport.businessobjects.com.

To install language packs
Before installing a language pack, your BusinessObjects Enterprise server must be running and patched to the required revision level. You will be asked for CMS administrator credentials. If any part of your BusinessObjects Enterprise deployment is not patched to the required software version, the language pack installation will abort and must be reapplied after the system has been patched to the correct level. Please review the requirements for language packs at the Business Objects customer support site: http://sup port.businessobjects.com/documentation/supported_platforms.
Note: Language packs do not require a keycode.

1. Open the Central Management Console (CMC) and ensure that the server processes are running. 2. Locate the language pack to install under BUSINESS_OBJECTS_DIS TRIBUTION_CD_DIR/langs/LANGUAGE/DISK_1. Replace LANGUAGE with the ISO code of the language you are installing. 3. Run the install.sh script with the first argument set to the location of the BusinessObjects Enterprise installation directory. For example: install.sh /opt/bobj 4. Press y to accept the license agreement. 5. Enter the CMS hostname, port number, and administrator password into the labeled fields and press Enter. 6. Press Enter after you have confirmed the location of the BusinessObjects Enterprise install directory. Once the installation is complete, you will be able to choose the installed language from the Options dialog window in BusinessObjects Enterprise applications.

134

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

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

9

Note:

All fix packs or other updates to BusinessObjects Enterprise released on a date after the language pack release date must be re-applied to ensure that updated functionality is maintained. Language packs must be re-installed after you have added or removed a component from your BusinessObjects Enterprise deployment.

Installing language packs across a BusinessObjects Enterprise deployment
You can install language packs with one command by specifying parameters on the command-line. This is referred to as a silent installation. When parameters are supplied on the command-line the installation will not prompt for information. The command-line syntax for a silent install is as follows:
install_langpack.sh BUSINESS_OBJECTS_HOME_DIR INSTALLMODE=silent CMSNAMESERVER=CMS_HOSTNAME CMSPORTNUMBER=PORT_NUMBER CMSPASSWORD=CMS_PASSWORD

Replace BUSINESS_OBJECTS_HOME_DIR with the full path of your BusinessObjects Enterprise installation. The following table details each of the parameters used by install_langpack.sh.
Parameter INSTALLMODE CMSNAMESERV ER CMSPORTNUM BER Expected argument silent CMS Hostname Port number for CMS Description Switch to enable silent install mode Enter the name of your CMS machine. CMS port number. The password for your CMS server.

CMSPASSWORD CMS admin password

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

135

9

Language Packs on UNIX To uninstall language packs

For example:
$ ./install_langpack.sh /opt/bobje INSTALLMODE=silent CMSNAMESERVER=myserver1 CMSPORTNUMBER=6400 CMSPASSWORD=mypassword

To uninstall language packs, use the wdeploy undeployall command to remove all web applications, then wdeploy deployall to re-deploy web applications without the language packs. For example, the following command runs undeployall for a WebLogic 10 server:
wdeploy.sh weblogic10 -Das_dir=/opt/bea/user_projects/domains/base_domain -Das_admin_port=7001 -Das_instance=AdminServer -Das_admin_username=weblogic -Das_admin_password=weblogic undeployall

Followed by:
wdeploy.sh weblogic10 -Das_dir=/opt/bea/user_projects/domains/base_domain -Das_admin_port=7001 -Das_instance=AdminServer -Das_admin_username=weblogic -Das_admin_password=weblogic deployall

For more information on using wdeploy, see How to use wdeploy.
Related Topics

How to use wdeploy on page 151

To uninstall language packs
1. Open the Central Management Console (CMS) and ensure that all servers are running 2. Locate the language pack to uninstall. You will find the uninstall_lang pack.sh script in the setup folder of the language pack. 3. Run the uninstall_langpack.sh script with the first argument set to the location of the BusinessObjects Enterprise installation directory. For example: uninstall_langpack.sh /opt/bobj

136

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Language Packs on UNIX To uninstall language packs

9

4. Press y to confirm the removal of the language pack. 5. Enter the CMS hostname, port number, and administrator password and press Enter. 6. Press Enter after you have confirmed the location of the BusinessObjects Enterprise installation directory.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

137

9

Language Packs on UNIX To uninstall language packs

138

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Maintaining your Installation

10

10

Maintaining your Installation Uninstalling BusinessObjects Enterprise from UNIX

Uninstalling BusinessObjects Enterprise from UNIX
Before you can remove BusinessObjects Enterprise from your UNIX machine, you must run the AddOrRemovePrograms.sh script. The script is installed to the directory of your installation and is used to add or remove BusinessObjects Enterprise products or components. This script stops all BusinessObjects Enterprise servers and processes. It then deletes the files copied from the product CD during your original installation of BusinessObjects Enterprise. A BusinessObjects Enterprise installation creates a number of additional files on your system. When you uninstall BusinessObjects Enterprise these additional files and any files created by the system or by users after installation will not be removed. The files that remain include log files created by BusinessObjects Enterprise. These log files can be useful for diagnosing problems with previous installations.

To uninstall BusinessObjects Enterprise
Before removing BusinessObjects Enterprise XI 3.0 from your UNIX system, you should uninstall all language packs used by the installation. To uninstall BusinessObjects Enterprise: 1. From the installation directory run ./AddOrRemovePrograms.sh. The "Add or Remove Programs" screen is displayed. 2. Select BusinessObjects Enterprise XI 3.0 and press Enter. The "Add Features or Uninstall Current Product"screen is displayed. 3. Select Uninstall Product and press Enter. A confirmation screen is displayed. 4. Select Yes and press Enter. The uninstallation process begins. To completely remove all BusinessObjects Enterprise files, perform an rm -Rf command on the bobje directory.

140

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Maintaining your Installation Adding performance management to your installation

10

If you performed a system installation, you must also delete the run control scripts from the appropriate /etc/rc# directories.
Related Topics

To uninstall language packs on page 136

Adding performance management to your installation
You can add performance management servers and binaries to your BusinessObjects Enterprise installation. You must run the AddOrRemovePrograms.sh script to add the performance management resources. The script is installed to the directory of your installation.

To add performance management
To add performance management resources, you must have BusinessObjects Enterprise installed on a UNIX machine. Run the following procedure if your current BusinessObjects Enterprise installation does not have the required performance management resources. 1. From the installation directory run ./AddOrRemovePrograms.sh. The "Add or Remove Programs" screen is displayed. 2. Select BusinessObjects Enterprise XI 3.0 and press Enter. The "Add Features or Uninstall Current Product" screen is displayed. 3. Select Add Dashboards and Analytics Servers and press Enter. You are prompted to enter Central Management Server (CMS) connection details. 4. Specify the following information:
Field name CMS Hostname Description The system name for the CMS host machine

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

141

10

Maintaining your Installation Adding performance management to your installation

Field name CMS Port

Description Port used by the CMS

Existing CMS Administrator Pass- Administrator password used to access word the CMS

If your previous installation was not configured to deploy web applications to a specific web application server, skip to step 8. Otherwise, you will be prompted to provide the web application server configuration details. 5. Select your existing web application server and press Enter. You options are the following: • Tomcat 5.5 • WebLogic 10 • WebLogic 9 • WebSphere 6.1 • Oracle Application Server 10g R3 • Other A configuration screen for your selected web application server is displayed. 6. Provide the requested configuration details for your web application server. The table below summarizes the information required for each supported web application server.
Web Application Server Apache Tomcat 5.5 Information required for installation setup • • Instance to install to: Name of the current web application server instance (e.g. “localhost”). Application server Installation directory: The directory where the web application server is installed (e.g. <INSTALLDIR>/wde ploy/appserver/Tomcat5520).

142

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Maintaining your Installation Adding performance management to your installation

10

Web Application Server WebLogic 10

Information required for installation setup • • • • • Admin port: Administration port of the application server - mandatory for Weblogic (e.g. “7001”). Admin login: User name with administration rights to the application server - mandatory for Weblogic. Admin password: Password for account with administration rights to the application server - mandatory for Weblogic. Instance to install to: Name of the current web application server instance (e.g. “ mserver1”). Application server Installation directory: The directory where the web application server is installed (e.g. /bea/weblogic10/us er_projects/domains/base_domain). Note: For WebLogic the directory is the domain root.

WebLogic 9

• • • • •

Admin port: Administration port of the application server - mandatory for Weblogic (e.g. “7001”). Admin login: User name with administration rights to the application server - mandatory for Weblogic. Admin login: Password for account with administration rights to the application server - mandatory for Weblogic. Instance to install to: Name of the current web application server instance (e.g. “ mserver1”). Application server Installation directory: The directory where the web application server is installed (e.g /bea/user_projects/do mains/base_domain). Note: For WebLogic the directory is the domain root.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

143

10

Maintaining your Installation Adding performance management to your installation

Web Application Server WebSphere 6.1

Information required for installation setup • • • • • • Admin port: Administration port of the WebSphere application server - the SOAP port. Admin login: User name with administration rights to the WebSphere application server. Admin password: Password for account with administration rights to the application server. Instance to install to: Name of the current web application server instance (e.g. “ server1”). Virtual host: The virtual host to which the application must be bound. Admin is secure (y/n): Select this option to enable security requiring administrative access credentials to the application. Note: If Admin is secure is not selected you do not need to specify a username or a password. • Application Server Installation Directory: The directory where the web application server is installed (e.g./IBM/WebSphere/AppServ er).

144

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Maintaining your Installation Adding performance management to your installation

10

Web Application Server Oracle Application Server 10g R3

Information required for installation setup • Admin port: Administration port of the application server - mandatory for Oracle 10g R3 (e.g. “6003”) .This should be the Request port of the <notifi-cation-server> element in the opmn.xml file. Admin login: User name with administration rights to the application server - mandatory for Oracle 10g R3. Admin password: Password for account with administration rights to the application server - mandatory for Oracle 10g R3. Admin is secure (y/n): Select this option only if you want Secure Sockets Layer (SSL) as part of the deployment. Note: If Admin is secure is not selected, you will still have to specify the username and password to access the server. • • Instance to install to: Name of the current web application server instance (e.g. “ home”). Application server Installation directory: The directory where the web application server is installed (e.g. /product/10.1.3/Ora cleAS_1). Server Name: Name of the target application server (e.g. "myserver.domain.com"). Group Id: Name of the server group to which the target application belongs (e.g. "Default_group").

• • •

• • .

7. Press Enter to submit your configuration details. The installation setup verifies the configuration details. Once the verification is complete, you can start the installation process. 8. Specify the directory where the BusinessObjects Enterprise installation media is located. 9. Select Yes and press Enter. The Dashboard and Analytics resources are added to your installation. If you have been provided with a new product keycode to activate performance management, you will have to provide the code to start the new servers.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

145

10

Maintaining your Installation The installation log file

Before users in your organization can start working with performance management, you need to do the following: After adding performance management to the installation, you need to do the following: • Create a performance management repository – this repository stores the metrics, goals, sets, and calendars used for performance management analysis. Specify which users can access performance management resources. Define connections between the metrics used for performance management and the performance management repository.

• •

For more detailed information please consult the Performance Management Setup Online Help.

The installation log file
The installation log files contains information on all the parameter settings used in a BusinessObjects Enterprise installation. The log files can be used as a reference or to troubleshoot installation errors. The name of the initial log files are BusinessObjects.12.0.log and BusinessOb jects.12.0.log.summary. The BusinessObjects.12.0.log file contains detailed information on installation and deployment. Both files are saved under the following directory: <INSTALLDIR>/setup/logs/.

146

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment

11

11

Post Installation Web Application Deployment Overview of post install deployment

Overview of post install deployment
You can deploy web applications for BusinessObjects Enterprise XI 3.0 installations by running all three supported installation types. The installation setup program guides you through an automated process for deploying the web applications and their required components only if you specify and configure your web application server during the installation setup. You can also configure your web application servers and deploy web application components after installing BusinessObjects Enterprise. You can choose either of the following methods. 1. Use the wdeploy program to automatically deploy the required components to the applications server. For detailed information on wdeploy see Deploying BusinessObjects Enterprise Web Applications using wdeploy. 2. Manually configure and deploy the required components to the applications server. The following table lists which deployment method is available for supported Web application server.
Installation setup wdeploy program WebSphere 6.1 WebSphere Community Edition 2.0 WebLogic 10 WebLogic 9.2 Tomcat 5.5 SAP Application Server 7.0 Oracle Application Server 10G R3 JBoss 4.04 X X X X X X X X X X Manual deployment X X X X X X

X X

X X

148

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Before you deploy web applications

11

Before you deploy web applications
Your web application server must be installed and working before you attempt to install BusinessObjects Enterprise. Consult your web application server documentation for installation instructions. To deploy and run the CMC and InfoView applications, your web application server should have at least 1.2 GB of free disk space, in addition to any other requirements specified by other software installed on the machine. It is recommended that you change the heapsize and maximum perm size settings of your JVM to -Xmx1024m -XX:MaxPermSize=256m. If using Tomcat 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 your Java memory settings. Before you begin the deployment process, ensure that the web application server is correctly installed and verify that the application server is running correctly by launching its administrative console at: • http://<WAS_HOSTNAME>:<PORT> Replace <WAS_HOSTNAME> with the host name or IP address of your web application server, and <PORT> with the port number used for HTTP. Consult your 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 BusinessObjects Enterprise installation to assist you in the command-line deployment of web applications to your web application server. It is located in the following directory: <INSTALLDIR>/deployment/. In addition to the wdeploy.sh the folder contains all the required configuration files for running the tool.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

149

11

Post Installation Web Application Deployment Deploying with wdeploy

Note: The wdeploy tool is also available as a stand-alone package on the

product distribution media under the following directory: Collater als/Tools/wdeploy.

Prerequisites for using wdeploy

To deploy BusinessObjects Enterprise web applications to a web application server, you must have BusinessObjects Enterprise installed, including all required WAR files. If the target web application server is on the same machine on which BusinessObjects Enterprise is installed you can proceed to run the wdeploy script. If the target web application server is hosted on a remote machine you will have to follow specific steps for preparing the wdeploy environment.
Related Topics

• •

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

Overview for using wdeploy
The wdeploy command-line tool is included with BusinessObjects Enterprise to assist you in the command-line deployment of WAR files to your web application server. You can choose to deploy all web application resources together on a single web application server (standalone mode), or to separate dynamic and static content for deployment onto de-paired web and web application servers (distributed mode). For detailed information on wdeploy see Deploying BusinessObjects Enterprise Web Applications using wdeploy. This document is available at http://support.businessobjects.com. For more information about the system architecture of an installation of BusinessObjects Enterprise, see the “Architecture” chapter of the BusinessObjects Enterprise Deployment Planning Guide.
Note: If you have a firewall between the machine running your Java

application server and your other BusinessObjects Enterprise servers, you must perform additional system configuration. See the section on how to configure firewalls in the BusinessObjects Enterprise Deployment Planning Guide.

150

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Deploying with wdeploy

11

How to use wdeploy
To use wdeploy, the specific configuration file for your web application server must be properly configured. This file is located in <INSTALLDIR>/deploy ment/. For example, the configuration file for weblogic 9.2 is config.weblog ic9. It is recommended that you use the same user account for installing BusinessObjects Enterprise and your web application server. Ensure that you have the minimum user rights for the web application server. The following table lists the required wdeploy configuration file details that must be specified for each supported web application server.
Note: Parameters specified on the command-line override parameters in

the wdeploy configuration file.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

151

11

Post Installation Web Application Deployment Deploying with wdeploy

Web application server WebSphere 6.1

Required Configuration details

• •

as_admin_port: The SOAP Connector Port of the application server (for example “8880”). as_admin_username: WebSphere administrator account username (for example "administrator"). Note: If as_admin_is_secure is false, a value for as_admin_user name does not need to be specified.

as_admin_password: WebSphere administrator account password (for example "password"). Note: If as_admin_is_secure is false, a value for as_admin_pass word does not need to be specified.

• • •

as_instance: The name of your WebSphere application server instance (for example "server1"). as_virtual_host: The virtual host to which the application must be bound (for example "default_host"). as_admin_is_secure: Instructs wdeploy that WebSphere 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 “/opt/IBM/WebSphere/AppServer”). ws_instance: The name of the web server where the application is installed, in distributed mode (for example "server1"). enforce_file_limit: Indicates to wdeploy whether or not the web application server may encounter issues loading applications that contain more than 65,535 files ("True" by default).

152

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Deploying with wdeploy

11

Web application server WebLogic 10

Required Configuration details

• • • • •

as_admin_port: Administration port of the application server (for example "7001"). as_admin_username: WebLogic administrator account username (for example "weblogic"). as_admin_password: WebLogic administrator account password (for example "weblogic"). as_instance: The name of your WebLogic application server instance (for example "AdminServer"). as_dir: Weblogic domain directory (for example "/opt/bea/weblog ic10/user_projects/domains/base_domain"). as_admin_port: Administration port of the application server (for example "7001"). as_admin_username: WebLogic administrator account username (for example "weblogic"). as_admin_password: WebLogic administrator account password (for example "weblogic"). as_instance: The name of your WebLogic application server instance (for example "AdminServer"). as_dir: Weblogic domain directory (for example "<IN STALLDIR>/bea/user_projects/domains/base_domain"). as_instance : Name of the web application server instance currently used (for example "localhost"). as_dir : Installation directory of the web application server (for example "/opt/tomcat). as_service_key_value: Tomcat's Java parameters, and the value of the registry key as_server_key.

WebLogic 9.2

• • • • •

Tomcat 5.5

• • •

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

153

11

Post Installation Web Application Deployment Deploying with wdeploy

Web application server

Required Configuration details

SAP Application Serv- • er 7.0 • • • • •

as_dir: The location of your application server (for example "<INSTALLDIR>/SAP"). as_sid: the SAP system id of the target instance. (for example "AS2"). as_instance: The name of your application server instance (for example "JC01"). as_admin port: the port number used by the server (for example "50104"). as_admin_username: the administrator username (for example "Administrator"). as_admin_password: the administrator password (for example "password"). as_admin_port: Administration port of the application server. This is the request port of the notification server, found in the <notifi cation-server> section of configuration file opmn.xml (for example "6003"). as_admin_username: Oracle Application Server administrator account username (for example "ocjadmin"). as_admin_password: Oracle Application Server administrator account password (for example "oracle10g"). as_instance: The name of your Oracle Application Server application server instance (for example "home"). as_admin_is_secure: Instructs wdeploy that Oracle Application Server SSL security is enabled (for example "false"). Note: If as_admin_is_secure is not enabled, you will still have to specify the username and password to access the server.

Oracle Application Server 10g R3

• • • •

• • •

as_dir: Oracle Application Server installation directory (for example "/opt/product/10.1.3/OracleAS_1"). as_appserver_name: Name of the target application server (for example "myserver.domain.com"). as_group_id: Name of the server group to which the target application belongs (for example "Default_group").

154

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Deploying with wdeploy

11

Web application server JBoss 4

Required Configuration details

• •

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

Run the wdeploy.sh script by opening command line console and typing the following:
<INSTALLDIR>/deployment/wdeploy.sh <appserver> deployall >> <logfilename>.log

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

Note: The <appserver> must be same as the web application server used

in the configuration filename.
Tip: You can drop the deployable war files to non-default location by passing

the parameter -Dwork_dir=your target location as part of the wdeploy command. For more detailed information on wdeploy see Deploying BusinessObjects Enterprise Web Applications using wdeploy.

Options for using wdeploy
There are several actions that can be performed the wdeploy tool to control the 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 web

applications deployed through the installer or wdeploy will be undeployed.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

155

11

Post Installation Web Application Deployment Deploying with wdeploy

All other web applications can only be manually removed using the web application server's administrative console. For information on all options available for wdeploy see Deploying BusinessObjects Enterprise Web Applications using wdeploy.
Note: The wdeploy command does not create a log file. To persist the output

generated 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 InfoView and 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 web application server, and PORT with the port number used for either HTTP or HTTPS communication. The default root context used for InfoView is In foViewApp; 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 a specific web application, then copies the WAR application to <IN STALLDIR>/deployment/workdir/WS_VERSION, but does not deploy the web application to the web application server. The predeployall command performs the predeploy command for all web applications.

156

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Deploying with wdeploy

11

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

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

Using deployonly and deployonlyall

The deployonly command deploys a web application that is specifically configured 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 InfoView to WebSphere.
wdeploy.sh websphere6 -Das_dir=/opt/ibm/WebSphere/AppServer -Das_instance=server1 -Das_virtual_host=default_host -Das_admin_port=8880 -DAPP=InfoViewApp deployonly

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

157

11

Post Installation Web Application Deployment Deploying with wdeploy

Using deploy and deployall

The deploy command creates resources and configuration files for a specific web application, which is then deployed to the web application server. The deployall command performs the deploy command for all web applications. Running deploy is equivalent to running a predeploy command followed by a deployonly command. Running deployall is equivalent to running a predeployall command followed by a deployonlyall command. Example 1: using wdeploy deploy to predeploy, then deploy, InfoView to WebSphere.
wdeploy.sh websphere6 -Das_dir=/opt/ibm/WebSphere/AppServer -Das_instance=server1 -Das_virtual_host=default_host -Das_admin_port=8880 -DAPP=InfoViewApp deploy

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

Using undeploy and undeployall

The undeploy command uninstalls a previously deployed web application from the web application server. The undeployall command performs the undeploy command for all web applications. Example 1: using wdeploy undeploy to undeploy InfoView from WebSphere.
wdeploy.sh websphere6 -Das_dir=/opt/ibm/WebSphere/AppServer -Das_instance=server1 -Das_virtual_host=default_host -Das_admin_port=8880 -DAPP=InfoViewApp undeploy

158

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Deploying with wdeploy

11

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

Disable WebSphere JSF implementation
If pages rendered by WebSphere do not show cached values correctly, it may be using its own version of the Java Server Faces (JSF) library, rather than the JSF implementation supplied with BusinessObjects Enterprise. To correct this problem, you must manually reconfigure WebSphere for each web application that uses JSF: CmcApp, CmcAppActions, and PlatformServices. To disable the JSF implementation supplied with WebSphere, follow the instructions below. 1. Log in to the "WebSphere Application Server Administration" console using the following URL: http://WAS_HOSTNAME:PORT/admin. The WebSphere administration console's default port number is 9060. 2. Browse to YOUR_WEB_APPLICATION > Manage Modules > YOUR_WEB_APPLICATION.war Replace YOUR_WEB_APPLICATION in the example above with the name 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 displayed correctly.

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

159

11

Post Installation Web Application Deployment Deploying with wdeploy

Note: This configuration requires that you use the wdeploy command to

split web application resources into static and dynamic content that can be deployed to separate web and web application servers. 1. Set up an IBM HTTP Server (IHS) web server and ensure that it is working correctly. Load a web page, such as the IHS default test page, to verify that the web server is serving content correctly. Open a web browser and enter the IP address or hostname of the web server, and a port number if the server is not listening on port 80. For example: 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 web application server, and a port number. For example: http://myappserver.mycompany.com:9080.
Note: If you have any existing BusinessObjects Enterprise web

applications running on the server, they must be undeployed before continuing. 3. Run the web server plug-in installation wizard to install the plug-in that bridges WebSphere with IHS, and follow the directions to enter information about your IHS web server. 4. Follow the plug-in configuration instructions on the WebSphere web site for configuring the bridge between IHS and WebSphere. Requests for dynamic resources are now forwarded to WebSphere when received by IHS. 5. Ensure that the bridge between the web server and web application server is working by pointing a browser to the web server and verifying that dynamic content from the web application server is served correctly. For example, visit the URL: http://mywebserver.mycompa ny.com:80/snoop/. 6. If the web application server is installed on the same machine as BusinessObjects Enterprise, run wdeploy locally on that machine. If the web application server runs on a different machine, you must copy the wdeploy command and environment to the web application server. See To deploy web applications on a remote machine. 7. Configure wdeploy environment to separate content between the web server and the web application server. This is known as "distributed" mode.

160

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Deploying with wdeploy

11

The wdeploy configuration files for IHS and WebSphere are located in <INSTALLDIR>/deployment. • Edit config.apache. For example:
#Business Objects Configuration Utility ws_dir=/opt/apache connector_type=websphere6 deployment_dir=/opt/apache/htdocs

Edit config.websphere6. For example:
#Business Objects Configuration Utility as_admin_port=8880 as_admin_username=admin as_admin_password=password as_dir=/opt/websphere/appserver as_instance=server1 as_virtual_host=default_host as_admin_is_secure=false enforce_file_limit=true

8. Use wdeploy predeploy in distributed mode to split source web applications into separate static and dynamic resources. For example: • Run the following command to extract static content for the IHS web server.
./wdeploy.sh websphere6 -Das_mode=distributed -Dws_type=apache predeployall >> wdeploy.log

The dynamic content of web applications is located in: <INSTALLDIR>/de ployment/workdir/websphere6/application. The static content is located in: <INSTALLDIR>/deployment/workdir/web sphere6/resources. 9. Run wdeploy deployonlyall command to deploy the dynamic content to WebSphere application server and static content to IHS. If IHS and WebSphere are on the same machine, static and dynamic content will be automatically deployed to servers by the following command:
./wdeploy.sh websphere6 -Das_mode=distributed -Dws_type=apache deployonlyall >> wdeploy.log

Note: If your dynamic and static content are in a custom location, use

the -Dwork_dir parameter.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

161

11

Post Installation Web Application Deployment Deploying with wdeploy

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

Note: If your dynamic and static content are in a custom location, use

the -Dwork_dir parameter. 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 in httpd.conf. For example, to include AnalyticalReporting, you would enter:
Include conf/bobj.AnalyticalReporting.conf

10. Propagate the plugin-cfg.xml file from the application server to the web server using the administrative console. Click Servers > Web server. Select the web server, then click Propagate Plug-in. Web servers other than 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>/con fig/cells/<cell_name>/nodes/node_name/servers/<Web_serv er_name> directory on the WebSphere web application server to the <plugins_root>/config/<Web_server_name> directory on the IHS

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

162

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Deploying with wdeploy

11

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

deployed web application. Static content is now served by a dedicated web server, and dynamic content is served by a dedicated web application server.
Related Topics

• •

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

Deploying to WebLogic with wdeploy
Using predeploy and predeployall

The predeploy command creates resources and configuration files for a specific web application, then copies the WAR application to <IN STALLDIR>/deployment/workdir/WS_VERSION, but does not deploy 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.sh weblogic9 -Das_dir=/opt/bea/user_projects/domains/base_domain -Das_admin_port=7001 -Das_instance=AdminServer -Das_admin_username=weblogic -Das_admin_password=weblogic -DAPP=InfoViewApp predeploy

Example 2: using wdeploy predeployall to predeploy all web applications to WebLogic.
wdeploy.sh weblogic10 -Das_dir=/opt/bea/user_projects/domains/base_domain -Das_admin_port=7001 -Das_instance=AdminServer -Das_admin_username=weblogic -Das_admin_password=weblogic predeployall

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

163

11

Post Installation Web Application Deployment Deploying with wdeploy

Using deployonly and deployonlyall

The deployonly command deploys a web application that is specifically configured 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 InfoView to WebLogic.
wdeploy.sh weblogic9 -Das_dir=/opt/bea/user_projects/domains/base_domain -Das_admin_port=7001 -Das_instance=AdminServer -Das_admin_username=weblogic -Das_admin_password=weblogic -DAPP=InfoViewApp deployonly

Example 2: using wdeploy deployonlyall to deploy all predeployed web applications to WebLogic.
wdeploy.sh weblogic10 -Das_dir=/opt/bea/user_projects/domains/base_domain -Das_admin_port=7001 -Das_instance=AdminServer -Das_admin_username=weblogic -Das_admin_password=weblogic deployonlyall

Using deploy and deployall

The deploy command creates resources and configuration files for a specific web application, which is then deployed to the web application server. The deployall command performs the deploy command for all web applications. Running deploy is equivalent to running a predeploy command followed by a deployonly command. Running deployall is equivalent to running a predeployall command followed by a deployonlyall command. Example 1: using wdeploy deploy to predeploy, then deploy, InfoView to WebLogic.
wdeploy.sh weblogic9 -Das_dir=/opt/bea/user_projects/domains/base_domain -Das_admin_port=7001 -Das_instance=AdminServer -Das_admin_username=weblogic -Das_admin_password=weblogic

164

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Deploying with wdeploy

11

-DAPP=InfoViewApp deploy

Example 2: using wdeploy deployall to predeploy, then deploy, all web applications to WebLogic.
wdeploy.sh weblogic10 -Das_dir=/opt/bea/user_projects/domains/base_domain -Das_admin_port=7001 -Das_instance=AdminServer -Das_admin_username=weblogic -Das_admin_password=weblogic deployall

Using undeploy and undeployall

The undeploy command uninstalls a previously deployed web application from the web application server. The undeployall command performs the undeploy command for all web applications. Example 1: using wdeploy undeploy to undeploy InfoView from WebLogic.
wdeploy.sh weblogic9 -Das_dir=/opt/bea/user_projects/domains/base_domain -Das_admin_port=7001 -Das_instance=AdminServer -Das_admin_username=weblogic -Das_admin_password=weblogic -DAPP=InfoViewApp undeploy

Example 2: using wdeploy undeployall to undeploy all web applications from WebLogic.
wdeploy.sh weblogic10 -Das_dir=/opt/bea/user_projects/domains/base_domain -Das_admin_port=7001 -Das_instance=AdminServer -Das_admin_username=weblogic -Das_admin_password=weblogic undeployall

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

165

11

Post Installation Web Application Deployment Deploying with wdeploy

Note: This configuration requires that you use the wdeploy command to

split web application resources into static and dynamic content that can be deployed to separate web and web application servers. 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 the web server is serving content correctly. Open a web browser and enter the IP address or hostname of the web server, and a port number if the server is not listening on port 80. For example: 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 web application server, and a port number. For example: http://myappserver.mycompany.com:7001.
Note: If you have any existing BusinessObjects Enterprise web

applications running on the server, they must be undeployed before continuing. 3. Download the WebLogic Apache HTTP Server Plug-In from the BEA web site. The plug-in allows you to connect an Apache web server with a WebLogic web application server, so Apache can forward requests for dynamic resources to WebLogic. 4. Follow the plug-in configuration instructions on the BEA web site for configuring the bridge between Apache web server and WebLogic. Requests for dynamic resources are now forwarded to WebLogic when received by Apache. 5. Ensure that the bridge between the web server and web application server is working by pointing a browser to the web server and verifying that dynamic content from the web application server is served correctly. For example, visit the URL: http://mywebserver.mycompa ny.com:80/jsp-examples/. 6. If the web application server is installed on the same machine as BusinessObjects Enterprise, run wdeploy locally on that machine. If the web application server runs on a different machine, you must copy the wdeploy command and environment to the web application server. See To deploy web applications on a remote machine. 7. Configure wdeploy environment to separate content between the web server and the web application server. This is known as "distributed" mode.

166

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Deploying with wdeploy

11

The wdeploy configuration files for Apache and WebLogic are located in <INSTALLDIR>/deployment. • Edit config.weblogic9 or config.weblogic10. For example:
#Business Objects Configuration Utility as_admin_port=7001 as_admin_username=weblogic as_admin_password=weblogic as_instance=AdminServer as_dir=/usr/bea/user_projects/domains/base_domain

Edit config.apache. For example:
#Business Objects Configuration Utility ws_dir=/opt/apache224/ connector_type=weblogic9 deployment_dir=/opt/apache224/htdocs

8. Use wdeploy predeploy in distributed mode to split source web applications into separate static and dynamic resources. For example: • Run the following command to extract static content for the Apache web server and dynamic content for Weblogic application server.
./wdeploy.sh weblogic9 -Das_mode=distributed -Dws_type=apache predeployall >> wdeploy.log

The dynamic content in: <INSTALLDIR>/deployment/workdir/weblog ic9/application. Static content is located in: <INSTALLDIR>/deploy ment/workdir/weblogic9/resources. 9. Run wdeploy deployonlyall command to deploy the dynamic content to WebLogic application server and static content to Apache. If Apache and WebLogic are on the same machine, static and dynamic content will be automatically deployed to the servers by the following command:
./wdeploy.sh weblogic9 -Das_mode=distributed -Dws_type=apache deployonlyall >> wdeploy.log

Note: If your dynamic and static content are in a custom location, use

the -Dwork_dir parameter. If Apache and WebLogic are on different machines, dynamic content will be automatically deployed to WebLogic by the following command. Static

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

167

11

Post Installation Web Application Deployment Deploying with wdeploy

content must be manually deployed to the remote Apache machine afterwards.
./wdeploy.sh weblogic9 -Das_mode=distributed -deployonlyall >> wdeploy.log

Note: If your dynamic and static content are in a custom location, use

the -Dwork_dir parameter. 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/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 Apache server. Update Apache httpd.conf under <WS_DIR>/conf with the application config files. For each web application, you must include an entry in httpd.conf. For example, to include AnalyticalReporting, you would enter:
Include conf/bobj.AnalyticalReporting.conf

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

• •

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

Deploying to Tomcat with wdeploy
Using predeploy and predeployall

The predeploy command creates resources and configuration files for a specific web application, then copies the WAR application to <IN STALLDIR>/deployment/workdir/tomcat55, but does not deploy the web application to the web application server. The predeployall command performs the predeploy command for all web applications.

168

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Deploying with wdeploy

11

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

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

Using deployonly and deployonlyall

The deployonly command deploys a web application that is specifically configured 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 InfoView to Tomcat.
wdeploy.sh tomcat55 -Das_dir=/opt/tomcat -Das_instance=localhost -DAPP=InfoViewApp deployonly

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

Using deploy and deployall

The deploy command creates resources and configuration files for a specific web application, which is then deployed to the web application server. The deployall command performs the deploy command for all web applications. Running deploy is equivalent to running a predeploy command followed by a deployonly command. Running deployall is equivalent to running a predeployall command followed by a deployonlyall command.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

169

11

Post Installation Web Application Deployment Deploying with wdeploy

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

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

Using undeploy and undeployall

The undeploy command uninstalls a previously deployed web application from the web application server. The undeployall command performs the undeploy command for all web applications. Example 1: using wdeploy undeploy to undeploy InfoView from Tomcat.
wdeploy.sh tomcat55 -Das_dir=/opt/tomcat -Das_instance=localhost -DAPP=InfoViewApp undeploy

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

Related Topics

• •

After deploying web applications on page 192 After deploying web applications on page 192

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

170

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Deploying with wdeploy

11

by the web server, while dynamic content will be served by the web application server.
Note: This configuration requires that you use the wdeploy command to

split web application resources into static and dynamic content that can be deployed to separate web and web application servers. 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 the web server is serving content correctly. Open a web browser and enter the IP address or hostname of the web server, and a port number if the server is not listening on port 80. For example: 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 web application server, and a port number. For example: http://myappserver.mycompany.com:8080.
Note: If you have any existing BusinessObjects Enterprise web

applications running on the server, they must be undeployed before continuing. 3. Download the Apache Tomcat connector from the Tomcat web site. The Apache Tomcat connector allows you to connect an Apache web server with a Tomcat web application server, so Apache can forward requests for dynamic resources to Tomcat. 4. Follow the plug-in configuration instructions on the Apache web site for configuring the bridge between Apache web server and Tomcat web application server. Requests for dynamic resources are now forwarded to Tomcat when received by Apache. 5. Ensure that the bridge between the web server and web application server is working by pointing a browser to the web server and verifying that dynamic content from the web application server is served correctly. For example, visit the URL: http://mywebserver.mycompa ny.com:80/jsp-examples/. 6. If the web application server is installed on the same machine as BusinessObjects Enterprise, run wdeploy locally on that machine. If the web application server runs on a different machine, you must copy the

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

171

11

Post Installation Web Application Deployment Deploying with wdeploy

wdeploy command and environment to the web application server. See To deploy web applications on a remote machine. 7. Configure wdeploy environment to separate content between the web server 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 Utility as_dir=/opt/Tomcat5520 as_instance=localhost as_service_name=Tomcat5

Edit config.apache. For example:
#Business Objects Configuration Utility ws_dir=/opt/apache224 connector_type=tomcat55 deployment_dir=/opt/apache224/htdocs

8. Use wdeploy predeploy in distributed mode to split source web applications into separate static and dynamic resources. For example: • Run the following command to extract static content for the Apache web server.
./wdeploy.sh tomcat55 -Das_mode=distributed -Dws_type=apache predeployall >> wdeploy.log

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

Note: If your dynamic and static content are in a custom location, use

the -Dwork_dir parameter. If Apache and Tomcat are on different machines, dynamic content will be automatically deployed to Tomcat by the following command. Static

172

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Deploying with wdeploy

11

content must be manually deployed to the remote Apache machine afterwards.
./wdeploy.sh tomcat55 -Das_mode=distributed -deployonlyall >> wdeploy.log

Note: If your dynamic and static content are in a custom location, use

the -Dwork_dir parameter. 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/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 Apache server. Update Apache httpd.conf under <WS_DIR>/conf with the application config files. For each web application, you must include an entry in httpd.conf. For example, to include AnalyticalReporting, you would enter:
Include conf\bobj.AnalyticalReporting.conf

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

• •

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

Deploying to Oracle with wdeploy
Using predeploy and predeployall

The predeploy command creates resources and configuration files for a specific web application, then copies the WAR application to <IN STALLDIR>/deployment/workdir/oas1013, but does not deploy the web application to the web application server. The predeployall command performs the predeploy command for all web applications.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

173

11

Post Installation Web Application Deployment Deploying with wdeploy

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

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

Using deployonly and deployonlyall

The deployonly command deploys a web application that is specifically configured 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 InfoView to Oracle Application Server.
wdeploy.sh oas1013 -Das_dir=/opt/oracle10gasr3/oracleas_1 -Das_instance=home -Das_appserver_name=oc4j_inst1 -Das_group_id=default_group -Das_admin_port=6013 -Das_admin_username=oc4jadmin -Das_admin_password=oracle12 -DAPP=InfoViewApp deployonly

174

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Deploying with wdeploy

11

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

Using deploy and deployall

The deploy command creates resources and configuration files for a specific web application, which is then deployed to the web application server. The deployall command performs the deploy command for all web applications. Running deploy is equivalent to running a predeploy command followed by a deployonly command. Running deployall is equivalent to running a predeployall command followed by a deployonlyall command. Example 1: using wdeploy deploy to predeploy, then deploy, InfoView to Oracle Application Server.
wdeploy.sh oas1013 -Das_dir=/opt/oracle10gasr3/oracleas_1 -Das_instance=home -Das_appserver_name=oc4j_inst1 -Das_group_id=default_group -Das_admin_port=6013 -Das_admin_username=oc4jadmin -Das_admin_password=oracle12 -DAPP=InfoViewApp deploy

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

175

11

Post Installation Web Application Deployment Deploying with wdeploy

-Das_admin_password=oracle12 deployall

Using undeploy and undeployall

The undeploy command uninstalls a previously deployed web application from the web application server. The undeployall command performs the undeploy command for all web applications. Example 1: using wdeploy undeploy to undeploy InfoView from Oracle Application Server.
wdeploy.sh oas1013 -Das_dir=/opt/oracle10gasr3/oracleas_1 -Das_instance=home -Das_appserver_name=oc4j_inst1 -Das_group_id=default_group -Das_admin_port=6013 -Das_admin_username=oc4jadmin -Das_admin_password=oracle12 -DAPP=InfoViewApp undeploy

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

Related Topics

After deploying web applications on page 192

Deploying to SAP Application Server with wdeploy
Using predeploy and predeployall

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

176

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Deploying with wdeploy

11

STALLDIR>/deployment/workdir/nw2004, but does not deploy 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 SAP Application Server.
wdeploy.sh nw2004 -Das_dir=/opt/sap -Das_instance=server1 -Das_sid=AS2 -Das_admin_username=Administrator -Das_admin_password=password1 -Das_admin_port=50000 -DAPP=InfoViewApp predeploy

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

Using deployonly and deployonlyall

The deployonly command deploys a web application that is specifically configured 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 InfoView to SAP Application Server.
wdeploy.sh nw2004 -Das_dir=/opt/sap -Das_instance=server1 -Das_sid=AS2 -Das_admin_username=Administrator -Das_admin_password=password1 -Das_admin_port=50000 -DAPP=InfoViewApp deployonly

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

177

11

Post Installation Web Application Deployment Deploying with wdeploy

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

Using deploy and deployall

The deploy command creates resources and configuration files for a specific web application, which is then deployed to the web application server. The deployall command performs the deploy command for all web applications. Running deploy is equivalent to running a predeploy command followed by a deployonly command. Running deployall is equivalent to running a predeployall command followed by a deployonlyall command. Example 1: using wdeploy deploy to predeploy, then deploy, InfoView to SAP Application Server.
wdeploy.sh nw2004 -Das_dir=/opt/sap -Das_instance=server1 -Das_sid=AS2 -Das_admin_username=Administrator -Das_admin_password=password1 -Das_admin_port=50000 -DAPP=InfoViewApp deploy

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

178

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Deploying with wdeploy

11

Using undeploy and undeployall

The undeploy command uninstalls a previously deployed web application from the web application server. The undeployall command performs the undeploy command for all web applications. Example 1: using wdeploy undeploy to undeploy InfoView from SAP Application Server.
wdeploy.sh nw2004 -Das_dir=/opt/sap -Das_instance=server1 -Das_sid=AS2 -Das_admin_username=Administrator -Das_admin_password=password1 -Das_admin_port=50000 -DAPP=InfoViewApp undeploy

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

Related Topics

After deploying web applications on page 192

Deploying to JBoss with wdeploy
The Java Server Faces (JSF) bundled with the JBoss web application servers must be disabled for the Central Management Console (CMC) and InfoView web clients to work correctly. To disable JSF, the following directories must be removed and JBoss restarted: • JBOSS_HOME/server/default/deploy/jbossweb-tomcat55.sar/jsf•
libs JBOSS_HOME/server/default/tmp

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

179

11

Post Installation Web Application Deployment Deploying with wdeploy

JBOSS_HOME/server/default/work

Note: To use the Javalog4j logging included with BusinessObjects

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

Using predeploy and predeployall

The predeploy command creates resources and configuration files for a specific web application, then copies the WAR application to <IN STALLDIR>/deployment/workdir/jboss404, but does not deploy 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 JBoss.
wdeploy.sh jboss404 -Das_dir=/opt/jboss-4.0.4.GA -Das_instance=default -DAPP=InfoViewApp predeploy

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

Using deployonly and deployonlyall

The deployonly command deploys a web application that is specifically configured for the target web application server. The deployonlyall command performs the deployonly command for all web applications. Example 1: InfoView using wdeploy deployonly to deploy a predeployed InfoView to JBoss.
wdeploy.sh jboss404 -Das_dir=/opt/jboss-4.0.4.GA -Das_instance=default -DAPP=InfoViewApp deployonly

180

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Deploying with wdeploy

11

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

Using deploy and deployall

The deploy command creates resources and configuration files for a specific web application, which is then deployed to the web application server. The deployall command performs the deploy command for all web applications. Running deploy is equivalent to running a predeploy command followed by a deployonly command. Running deployall is equivalent to running a predeployall command followed by a deployonlyall command. Example 1: using wdeploy deploy to predeploy, then deploy, InfoView to JBoss.
wdeploy.sh jboss404 -Das_dir=/opt/jboss-4.0.4.GA -Das_instance=default -DAPP=InfoViewApp deploy

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

Using undeploy and undeployall

The undeploy command uninstalls a previously deployed web application from the web application server. The undeployall command performs the undeploy command for all web applications. Example 1: using wdeploy undeploy to undeploy InfoView from JBoss.
wdeploy.sh jboss404 -Das_dir=/opt/jboss-4.0.4.GA -Das_instance=default

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

181

11

Post Installation Web Application Deployment Deploying with wdeploy

-DAPP=InfoViewApp undeploy

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

Related Topics

After deploying web applications on page 192

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 BusinessObjects Enterprise installation, and Box 2 is the remote machine on which no BusinessObjects Enterprise resources are currently installed. 1. Create on Box 2 the following directories. • <INSTALLDIR>/deployment/. The deployment folder contains the wdeploy scripts and configuration files. • <INSTALLDIR>/bobje/enterprise120/java/applications/ • <INSTALLDIR>/Performance_Management_120/ • <INSTALLDIR>/caf/ These directories reflect the default directory structure installed on Box 1.
Tip: Although you can customize the folder structure to meet your specific

requirements, it is recommended that you maintain files within the same folder structure or hierarchy in Box 2 as in Box 1. 2. Copy the following files from Box 1 to Box 2. • Copy all the contents under <INSTALLDIR>/bobje/deployment/
Note: This content is also available on the product distribution media

under the following directory:
Collaterals/Tools/wdeploy

182

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment Deploying with wdeploy

11

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

• • •

Copy all the contents under <INSTALLDIR>/bobje/enterprise120/ja va/applications/. From <INSTALLDIR>/Performance_Management_120/ copy InitCon fig.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 file directory for each web application, skip to step 5. a. Open the properties file under <INSTALLDIR>/deployment/apps and modify the properties file for each web application (e.g CrystalRe ports.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 value of war_dir in <INSTALLDIR>/deployment/apps/ CrystalReports.properties to
war_dir=/home/bobje/enterprise120/java/ applications/CrystalReports.war

c. Repeat steps a-b for all the web applications you want to deploy to your web application server. 5. Modify the wdeploy configuration file for your web application server. You must provide all the required information to enable wdeploy to deploy the web application. For example, to modify the configuration file for WebLogic 9, you would modify the file to:
as_dir=/bea92/user_projects/domains/base_domain as_instance=AdminServer as_admin_port=7001 as_admin_username=weblogic as_admin_password=weblogic

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

183

11

Post Installation Web Application Deployment Deploying with wdeploy

6. If the Performance Management 12.0 files you copied in step 2 are not located under the same folder structure as Box 1, to deploy Performance Management you must do the following: a. Extract PerformanceManagement.war from the following directory:
<INSTALLDIR>/bobje/enterprise120/java/applications/

b. Set the af.configdir parameter in theweb.xml file to the location of the InitConfig.properties file. Theweb.xml file is located in: /PerformanceManagement/WEB-INF . The modified file should look like the example below.
<context-param> <param-name>af.configdir</param-name> <param-value>/home/Performance_Management_120</paramvalue> </context-param>

c. Repackage the PerformanceManagement.war. 7. Run the wdeploy script from its location in Box 2 by opening command line console and entering the following:
<INSTALLDIR>/deployment/wdeploy.sh <appserver> deployall -Dwar_dir=<INSTALLDIR>/bobje/ enterprise120/java/applications/ >> <logfilename>.log

You can pass the -Dwar_dir (with the path to the WAR files) in the command line to specify the location from which wdeploy accesses non customized WAR files.
Tip: You can drop the deployable war files to non-default location by

passing the parameter -Dwork_dir=your desired location as part of the wdeploy command.
Related Topics

• •

How to use wdeploy on page 151 Prerequisites for using wdeploy on page 149

184

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

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

11

Manually deploying to a web application server
BusinessObjects Enterprise WAR files
BusinessObjects Enterprise separates web application functionality into several Web ARchive (WAR) files, making it easier to deploy only the web applications required by your organization. Once you have installed BusinessObjects Enterprise the source files are available in the following directory: <INSTALLDIR>/bobje/enterprise120/ja
va/applications/

The following table summarizes the relationship between the WAR files and specific web applications in a BusinessObjects Enterprise deployment.
WAR file
AdminTools AnalyticalReport ing

Used by Query Builder Web Intelligence, Desktop Intelligence, CMC, InfoView

BusinessProcessBI Web services components CmcApp CmcAppActions CrystalReports dswsbobje InfoViewApp

CMC (entry point) CMC Crystal Reports, CMC, InfoView Web services components InfoView (entry point)

InfoViewAppActions InfoView OpenDocument

Open Document

PerformanceManage Performance Management, CMC, InfoView ment PlatformServices PMC_Help

CMC, InfoView Performance Management

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

185

11

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

WAR file
VoyagerClient XCelsius

Used by CMC, InfoView Xcelsius data presentation

XCTemplateUploader Xcelsius data presentation

WAR file context roots
All WAR files, with the exception of InfoViewApp and CmcApp, can be deployed to fix context root locations on your web application server. The following table lists the context roots that must be used, unless otherwise noted.
WAR file
AdminTools Analytical Reporting

WAS context path (default)
/AdminTools /AnalyticalReporting

BusinessPro /BusinessProcessBI cessBI CmcApp /CmcApp

Note: You may use a different root context for CmcApp as long as the root context matches the name of the WAR file. For example, a root context of /MyOrgCmc requires the WAR file to be named MyOrgCmc.war.
CmcAp pActions CrystalRe ports dswsbobje /CmcAppActions /CrystalReports /dswsbobje

186

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

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

11

WAR file

WAS context path (default)

InfoViewApp /InfoViewApp

Note: You may use a different root context for InfoViewApp as long as the root context matches the name of the WAR file. For example, a root context of/MyOrgInfo requires the WAR file to be named MyOrgInfo.war.
InfoViewAp pActions OpenDocu ment /InfoViewAppActions /OpenDocument

Performance /PerformanceManagement Management PlatformSer /PlatformServices vices PMC_Help Voyager Client XCelsius /PMC_Help /VoyagerClient /XCelsius

XCTemplateU /XCTemplateUploader ploader

Guidelines for deploying WAR files
To successfully deploy the WAR files and to ensure your BusinessObjects web applications run properly, you should use the following guidelines. 1. Your web application server must be installed and running before you deploy any WAR file. 2. The order in which you deploy the WAR files for your web applications does not matter. However, if your deployment environment involves reverse proxy, there is a specific order you must follow. For more information see “Modifying Default Security Behavior ” in the BusinessObjects Enterprise Administrator's Guide.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

187

11

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

3. When deploying a web application with functionality shared between multiple WAR files, each WAR file must reside within the same level of the 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 the web application server administration console. To rename CmcApp, you must update the appservice.url.default parameter in the web.xml file located in the WEB-INF directory of the CmcApp.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 server using the application server's administrative console. If the application server is 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 before they can be deployed to your web application server. 1. Run the wdeploy predeploy command to prepare a single web application, or wdeploy predeployall to prepare all web applications. Example 1: using wdeploy predeploy to prepare InfoViewApp for deployment to Tomcat.
wdeploy.sh tomcat55 -Das_dir=/opt/usr/tomcat -Das_instance=localhost -Das_service_name=Tomcat55 -DAPP=InfoViewApp predeploy

188

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

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

11

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

The wdeploy command will prepare the web application files for deployment on the web application server. The wdeploy command creates WAR or EAR files in <INSTALLDIR>/de ployment/workdir/<appserver>/application unless you specify the -Dwork_dir parameter. 2. Follow the manual deployment procedure specific to your web application server. Your web applications can now be manually deployed on your web application server. Repeat these steps for any other web applications that need to be installed.
Related Topics

• • • • •

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

To prepare for manual deployment on a remote machine
Use the procedure below to manually deploy web applications to a remote machine. In this procedure Box 1 refers to the machine hosting your BusinessObjects Enterprise installation, and Box 2 is the remote machine on which no BusinessObjects Enterprise resources are currently installed. 1. Create on Box 2 the following directories.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

189

11

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

• • • •

<INSTALLDIR>/deployment/. The deployment folder contains the

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

These directories reflect the default directory structure installed on Box 1.
Tip: Although you can customize the folder structure to meet your specific

requirements, it is recommended that you maintain files within the same folder structure or hierarchy in Box 2 as in Box 1. 2. Copy the following files from Box 1 to Box 2. • Copy all the contents under <INSTALLDIR>/bobje/deployment/
Note: This content is also available on the product distribution media

under the following directory:
Collaterals/Tools/wdeploy

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

• • •

Copy all the contents under <INSTALLDIR>/bobje/enterprise120/ja va/applications/. From <INSTALLDIR>/Performance_Management_120/ copy InitCon fig.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 file directory for each web application, skip to step 5. a. Open the properties file under <INSTALLDIR>/deployment/apps and modify the properties file for each web application (e.g CrystalRe ports.properties). b. Enter the following parameter in a new line: war_dir The value of the parameter is the WAR file path name.

190

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

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

11

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

c. Repeat steps a-b for all the web applications you want to deploy to your web application server. 5. Modify the wdeploy configuration file for your web application server. You must provide all the required information to enable wdeploy to prepare the WAR file for manual deployment. For example, to modify the configuration file for WebLogic 9, you would modify the file to:
as_dir=/bea92/user_projects/domains/base_domain as_instance=AdminServer as_admin_port=7001 as_admin_username=weblogic as_admin_password=weblogic

The configuration file is located in the following directory:<INSTALLDIR>/de ployment/config.<appserver> . 6. If the Performance Management 12.0 files you copied in step 2 are not located under the same folder structure as Box 1, to deploy Performance Management you must do the following: a. Extract PerformanceManagement.war from the following directory:
<INSTALLDIR>/bobje/enterprise120/java/applications/

b. Set the af.configdir parameter in the web.xml file to the location of the InitConfig.properties file. The web.xml file is located in: /PerformanceManagement/WEB-INF. The modified file should look like the example below.
<context-param> <param-name>af.configdir</param-name> <param-value>/home/Performance_Management_120</paramvalue> </context-param>

c. Repackage the PerformanceManagement.war.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

191

11

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

7. Run the wdeploy script from its location in Box 2 by opening command line console and entering the following:
<INSTALLDIR>/deployment/wdeploy.sh <appserver> predeployall -Dwar_dir=<INSTALLDIR>/bobje/ enterprise120/java/applications/ >> <logfilename>.log

You can pass the -Dwar_dir (with the path to the WAR files) in the command line to specify the location from which wdeploy accesses non customized WAR files.
Tip: You can drop the deployable war files to non-default location by

passing the parameter -Dwork_dir=your desired location as part of the wdeploy command. 8. The wdeploy command creates WAR or EAR files in <INSTALLDIR>/de ployment/workdir/<appserver>/application unless you specify the -Dwork_dir parameter. Follow the manual deployment steps for your web application server. You are now prepared to manually deploy web applications on Box 2.
Related Topics

• •

How to use wdeploy on page 151 Prerequisites for using wdeploy on page 149

After deploying web applications
To verify the web application server configuration, make sure that InfoView and 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 web application server, and PORT with the port number used for either HTTP or HTTPS communication. The default root context used for InfoView is In foViewApp; the default context used for the CMC is CmcApp.

192

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

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

11

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 using the following URL: http://WAS_HOSTNAME:PORT/admin The WebSphere admininstration console's default port number is 9060. 1. Under the Applications heading of the console navigation menu, click Enterprise Applications on the left navigational pane. 2. Click the Install button and navigate to the location of the WAR file to deploy. 3. Enter a context root for the WAR file (e.g. CmcApp/ for CmcApp.war) and press 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 create your own) from the Clusters and Servers and enable the Select checkbox. Proceed to "Step 3". 6. Select the virtual host you created (or default_host if you didn't create your 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.
Related Topics

After deploying web applications on page 192

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

193

11

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

Disable WebSphere JSF implementation
If pages rendered by WebSphere do not show cached values correctly, it may be using its own version of the Java Server Faces (JSF) library, rather than the JSF implementation supplied with BusinessObjects Enterprise. To correct this problem, you must manually reconfigure WebSphere for each web application that uses JSF: CmcApp, CmcAppActions, and PlatformServices. To disable the JSF implementation supplied with WebSphere, follow the instructions below. 1. Log in to the "WebSphere Application Server Administration" console using the following URL: http://WAS_HOSTNAME:PORT/admin. The WebSphere administration console's default port number is 9060. 2. Browse to YOUR_WEB_APPLICATION > Manage Modules > YOUR_WEB_APPLICATION.war Replace YOUR_WEB_APPLICATION in the example above with the name 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 displayed correctly.

To deploy to a WebSphere cluster
To manually deploy BusinessObjects Enterprise web applications to a WebSphere web application cluster distributed over multiple machines, you need to deploy the web applications to the machine hosting the WebSphere Deployment Manager. Once all the required web applications have been installed, you can use the WebSphere Integrated Solutions Console to separately deploy these applications to the cluster.
Tip: It is recommended that you install and configure a hardware or software

load balancer if running BusinessObjects Enterprise web applications on a WebSphere web application cluster. To configure the load balancer and cluster setup please consult your WebSphere documentation.

194

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

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

11

To deploy your web applications to a WebSphere cluster use the following general workflow: 1. If BusinessObjects Enterprise is installed to the same machine hosting the WebSphere Deployment Manager, skip to step 3. If BusinessObjects Enterprise and the WebSphere Deployment Manager run on different machines, you must first copy the wdeploy tool and environment to the machine hosting the WebSphere administration server. If you plan to deploy PerformanceManagement.war to the WebSphere cluster, you must copy InitConfig.properties from <INSTALLDIR>/Per formance_Management_120 to each managed server and ensure the file path of InitConfig.properties is matches the value specified for af.configdir param in web.xml in PerformanceManagement.war as shown below:
<context-param> <param-name>af.configdir</param-name> <param-value> /home/Performance_Management_120 </param-value> <context-param>

Note: The InitConfig.properties file should be located in C:\Program
Files\BusniessObjects\Performance Management 12.0 on each

machine hosting a managed WebSphere server. 2. Modify the config.websphere6 file located in the following directory: <INSTALLDIR>/deployment/. You need to specify information for the server administrating the cluster as shown in the following example.
as_dir=<INSTALLDIR>/IBM/WebSphere/AppServer as_admin_port=8779 as_virtual_host=default_host as_admin_is_secure=false enforce_file_limit=true

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

4. Open the WebSphere Integrated Solutions Console. 5. Go to Applications > Enterprise Applications to separately install each web application you want to deploy from the following directory:
<INSTALLDIR>/deployment/workdir/websphere6/application/

Note: All web applications are stored as EAR modules.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

195

11

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

6. Follow the Install new application steps in the console to install the web application
Note: In "Map modules to servers", make sure that you highlight the

target cluster and select the module to install before clicking Apply. 7. After installing the application, click Save. 8. Repeat steps 4-6 for each EAR file you want to install. 9. Go to System administration > Nodes and select the nodes in the cluster that are not indicated as synchronized 10. Click Synchronize. 11. Go to Applications > Enterprise Applications to start the application you just installed.
Related Topics

To deploy web applications on a remote machine on page 182

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

Deployable web applications for WebLogic are in the following format in the 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 To deploy dswsbobje.war to WebLogic on page 199.

1. Open the "WebLogic Administrative Console" with a web browser at a http://WAS_HOSTNAME:PORT/console where WAS_HOSTNAME is the name of your WebLogic server and PORT_NUMBER is the port number on which the server listens. The "WebLogic Server Administration Console" web page is displayed. 2. In the left-hand navigation pane, click base_domain > Deployments .

196

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

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

11

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 the wizard, 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 the web application server. Your changes are saved. 6. When your WAR file has been deployed, you must press the Start button to initiate its execution. The web application you deployed will now start.
Related Topics

After deploying web applications on page 192

To deploy to a WebLogic cluster
To manually deploy BusinessObjects Enterprise web applications to a WebLogic cluster distributed over multiple machines, you need to deploy the web applications to the machine hosting the WebLogic administration server. Once all the required web applications have been installed, you can use the WebLogic administration console to deploy these applications to the cluster.
Tip: It is recommended that you install and configure a hardware or software

load balancer if running BusinessObjects Enterprise web applications on a WebLogic web application cluster. To configure the load balancer and cluster setup 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 create a WebLogic XML registry using the following default settings and target it to all managed servers as shown below:
Property Name Value Registry name

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

197

11

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

Property

Value

Document Builder Facto- weblogic.apache.xerces.jaxp.DocumentBuilder ry FactoryImpl SAX Parser Factory Transformer Factory weblogic.apache.xerces.jaxp.SAXParserFacto ryImpl weblogic.apache.xalan.processor.Transformer FactoryImpl

2. If BusinessObjects Enterprise is installed to the same machine hosting the WebLogic administration server, skip to step 6. If BusinessObjects Enterprise and the WebLogic administration server run on different machines, you must first copy the wdeploy tool and environment to the machine hosting the WebLogic administration server. If you plan to deploy PerformanceManagement.war to the WebLogic cluster, you must copy InitConfig.properties from <INSTALLDIR>/Per formance_Management_120 to each managed server and ensure the file path of InitConfig.properties is matches the value specified for af.configdir param in web.xml in PerformanceManagement.war as shown below:
<context-param> <param-name>af.configdir</param-name> <param-value>/home/Performance_Management_120 </param-value> <context-param>

3. Modify the config.weblogic10 or the config.weblogic9 located in the following directory: <INSTALLDIR>/deployment/. You need to specify information for the server administrating the cluster as shown in the following example.
as_dir=/bea/user_projects/domains/base_domain as_instance=AdminServer as_admin_port=7001 as_admin_username=weblogic as_admin_password=password

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

198

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

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

11

<session-param> <param-name>PersistentStoreType</param-name> <param-value>replicated</param-value> </session-param> </session-descriptor>

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

6. Use the WebLogic administration console to separately install each web application you want to deploy from the following directory: <INSTALLDIR>/deployment/workdir/weblogic10/application/. 7. In the "Select deployment targets"workflow select the cluster name and All servers in the cluster. 8. After the"Select deployment targets" workflow is complete, select all the installed applications and go to Start > Servicing all requests.

To deploy dswsbobje.war to WebLogic
Before deploying web services WAR file on a WebLogic application server, the user must extract dswsbobje.war. If the WAR file is not extracted and redeployed, web services applications may display the error message “An XSD Exception occurred”. 1. Extract dswsbobje.war to a directory on the WebLogic web application server. 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 application has been successfully deployed. The list of web applications contains the dswsbobje web application. 9. Select the dswsbobje web application and click Start. 10. Click Activate Changes.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

199

11

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

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.
Related Topics

After deploying web applications on page 192

Deploying with the Tomcat administrative console
Ensure that your Tomcat web application server is installed, configured, and running before deploying WAR files. Log on to the "Tomcat Manager Console". • http://WAS_HOSTNAME:PORT/manager/html 1. Set the Context Path for the web application to be deployed. The context path must be the name of the WAR file, but without its extension. For example, to deploy a web application packaged as MyWebApplica tion.war, the context path must be MyWebApplication. 2. Set the XML Configuration File setting to be an XML file that contains the context path and document base. For example: <Context
docBase="<M>/WEB_APPLICATION.war" path="<context_path>" crossContext="false" debug="0" reloadable="false" trust ed="false"/>

3. Enter the full path to the WAR file and press the Deploy button The WAR file you chose is deployed.
Related Topics

After deploying web applications on page 192

Special considerations for deploying on Tomcat clusters
To manually deploy web applications to a Tomcat web application cluster distributed over multiple machines, you need to deploy the web applications on to each Tomcat instance. You can use the administrative console to deploy the BusinessObjects Enterprise web applications to the webapps subfolder in the Tomcat home directory for each server instance.

200

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

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

11

Tip: It is recommended that you install and configure a hardware or software

load balancer if running BusinessObjects Enterprise web applications on a Tomcat web application cluster. To configure the load balancer and cluster setup please consult your Tomcat documentation.

Deploying with the Oracle Application Server administrative console
Ensure that your Oracle Application Server web application server is installed, configured, and running before deploying WAR files. You must also have created an Oracle container for Java (OC4J) container in which to run BusinessObjects Enterprise. 1. Open the Oracle Application Server Enterprise Manager server page at http://WAS_HOSTNAME:PORT/em. Replace WAS_HOSTNAME with the hostname or IP address of your web application server, and PORT with the port number used for HTTP. The default port for Oracle Application Server 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 case select Archive is already present on the server where Application Server Control is running. 6. Enter the full path, or browse, to the WAR file in the Archive Location field. 7. Press the Next button to advance to the next step in the WAR deployment wizard. 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,

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

201

11

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

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 and press Next to proceed. If your application requires any class libraries, click on Configure Class Loading from the Deployment Tasks section. 10. In the Configure Web Module Class Loaders field, specify the location of 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 application has been deployed.
Related Topics

After deploying web applications on page 192

Deploying with the JBoss administrative console
Ensure that your JBoss web application server is installed, configured, and running before deploying WAR files. The Java Server Faces (JSF) bundled with the JBoss web application servers must be disabled for the Central Management Console (CMC) and InfoView web clients to work correctly. To disable JSF, the following directories must be removed and JBoss restarted: • JBOSS_HOME/server/default/deploy/jbossweb-tomcat55.sar/jsflibs

• •

JBOSS_HOME/server/default/tmp JBOSS_HOME/server/default/work

Note: To use the Javalog4j logging included with BusinessObjects

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

202

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

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

11

• • •

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 under one of the above paths, based upon the level of service provided by JBoss for your deployment. The web application will be automatically deployed by JBoss when the file is copied to the appropriate directory. 2. Check the JBoss server log, and you should see a message similar to the 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 viewrpt started.

Related Topics

After deploying web applications on page 192

Deploying with the SAP Application Server console
Ensure that your SAP Application Server web application server is installed, configured, and running before deploying WAR files. First, archive your web application server. 1. Start the "Visual Administrator" tool by running go from <SAP_HOME>/sap/CTB/JC00/j2ee/admin. Connect to your J2EE engine using the Administrator account. 2. In the "Visual Administrator", select the Cluster tab and expand the Server > Services > Deploy node within the J2EE tree. 3. Click Deploy & Start in the Runtime tab of the right-hand pane. If you would like to start the web application manually later, click the Deploy button instead. 4. In the "Deploy & Start" dialog window that appears, select the EAR file archive you created earlier. Click OK when done. 5. In the "Deploy Dialog" window, verify the root context and display name properties. Press OK to deploy. The web application will now be deployed.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

203

11

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

Related Topics

After deploying web applications on page 192

Deploying with the WebSphere Community Edition administrative console
Ensure that your WebSphere Community Edition web application server is installed, configured, and running before deploying web applications.
Note: The wdeploy command-line deployment tool currently does not support

deployment to WebSphere Community Edition. You can only deploy web applications using the WebSphere Community Edition administrative console. To deploy BusinessObjects Enterprise web applications with the administrative console, use the directory that contains the web application code directly:
<INSTALLDIR>/bobje/enterprise120/java/applications/

Log in to the WebSphere"Application Server Community Edition Administrative Console" using the following URL: http://WAS_HOST NAME:PORT/console The WebSphere Community Edition admin console's default port number is 8880. 1. Ensure the myfaces-deployer system module is turned off. Click on the System Modules link on the Console Navigation bar. Then click on the Expert User check box located at the top. Scroll down to find org.apache.geronimo.configs/myfaces-deployer/2.0.1/car and click 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 web application file. Here is a standard geronimo-web.xml file for use with CmcApp:
<web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web1.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>

204

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

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

11

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

updated with the name of the web application being deployed. For example, to add geronimo-web.xml to InfoViewApp, use <sys:artifac tId>InfoViewApp</sys:artifactId> and <context-root>/In foViewApp</context-root>. 3. Under the Applications heading of the console navigation menu, click Deploy New in the left navigational pane. 4. Click the Install New button to view the "Install New Applications" screen. 5. Click the archive Browse button and navigate to the location of the directory that contains the web application to deploy.
<INSTALLDIR>/bobje/enterprise120/java/applications/

6. Select any other options you want to use, such as Start app after install or Redeploy application. 7. Click Install to install the web application. After the web application is deployed, a list of installed web applications is displayed. 8. Verify that the web application was deployed. Repeat steps 2-5 for each application to deploy.
Related Topics

After deploying web applications on page 192

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

205

11

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

206

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Deployment Scenarios

12

12

Deployment Scenarios Overview of deployment scenarios

Overview of deployment scenarios
To improve your experience in installing and deploying BusinessObjects Enterprise this section provides two sample scenarios. These examples are for illustrative purposes. Each example includes a deployment diagram, key tasks, key configuration details, functional requirements and pre-conditions. The scenarios focus on two deployment characteristics: • • Desktop client to server Basic n-tier

Desktop client to server scenario
Desktop client to server overview
This scenario illustrates a simple client to server scenario which involves a desktop client application - Desktop Intelligence - connecting to the BusinessObjects Enterprise back-end server behind a firewall.
System layers

• • •

Data Tier: one machine with existing database server. Server Tier: one machine for hosting the framework servers and another for all other BusinessObjects servers. Client Tier: one machine for installing and running Desktop Intelligence.

Configuration details

• • • •

A firewall exists between client and server tiers. The firewall uses NAT (Network Address Translation). Only the ports required for the communication between the desktop client and the server tier are open on the firewall. BusinessObjects servers are distributed over two machines.
Solaris 10 Oracle 10g R2 (10.2)

Installation platform for BusinessObjects Enterprise Database for Central Management Server (CMS)

208

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Deployment Scenarios Desktop client to server scenario

12

Web application server Firewall

Not relevant Linux iptables

Desktop client to server diagram

The following diagram illustrates the system overview for the scenario once it is implemented.

Summary of required tasks
The desktop client to server deployment scenario involves the following tasks in the order listed below. 1. 2. 3. 4. Setting up the data tier. Setting up the server tier. Setting up the client tier. Setting up the firewall.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

209

12

Deployment Scenarios Desktop client to server scenario

Deploying the client to server scenario
To set up the data tier
The following steps require that you have already installed a version of Sun Solaris 10 that meets the installation requirements for Oracle 10g R2. Advanced administrative knowledge of Oracle Database and Sun Solaris 10 products is assumed. This database will be used to hold CMS data. Additional database will be created 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 performance

management, you also require access to your existing corporate reporting database. This is the database that hosts your organization's data, against which BusinessObjects Enterprise applications run. 1. Install Oracle 10g R2. Make note of the following settings you use during the installation. You will need these settings when you come to install BusinessObjects Enterprise servers and clients.
Setting Name of database server Administrator account name Administrator account password Database character set encoding Example DBSERVER1_ora system password UTF-8

An Oracle database is now installed and ready to be used by BusinessObjects Enterprise. 2. Create or import a new tablespace for the CMS, as well as auditing or Performance Management databases if required. Record the settings used for creating of the CMS database.

210

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Deployment Scenarios Desktop client to server scenario

12

CMS database setting CMS tablespace name Username for CMS tablespace access Password for CMS tablespace access System privileges for user access

Example mycompany mycompanyuser mypassword create table, create session, create procedure

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.
Auditing database setting Auditing tablespace name Example bobjaudit

Username for auditing tablespace audituser access Password for auditing tablespace auditpassword access System privileges for user access create table, create session, create procedure

An auditing database is now available for use. 4. Create or import a new tablespace for the Performance Management tablespace, if required. Record the settings used for creating of the Performance Management tablespace.
Performance Management database setting Performance Management database name Example bobjpm

Username for PM database ac- pmuser cess

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

211

12

Deployment Scenarios Desktop client to server scenario

Performance Management database setting

Example

Password for PM database ac- pmpassword cess System privileges for user access create table, create session, create procedure

A Performance Management tablespace is now available for use. 5. Create a network-shared directory on the database server's local file system to contain shared files for the file repository server (FRS).
Note: The network permissions for FRS directory must included read,

write, and execute permissions for the networked users. 6. Extract the FRS template file (e.g. FileStore_02-22-2008.zip) within the FRS directory you created in the last step. You have set up CMS, auditing, and performance management databases, as required. You have also installed a file repository server network-shared directory. The default listener port number used by Oracle is 1521. The database port number must be entered during the BusinessObjects Enterprise installation. Verify the connectivity between your CMS and database machines by attempting to connect to your database(s) from the CMS server(s).
Note: This scenario includes a network firewall between the CMS and

database servers. Ensure that this firewall is configured appropriately.
Remember: The ability to connect to your database server from your CMS

server may require a change to the Solaris firewall settings on both machines.

To set up the server tier
You need to install and setup Solaris 10 on the two machines that will host the BusinessObjects Enterprise server components. Designate a machine as SERVER 1 on which you will install framework servers. Designate second machine, SERVER 2, on which you will install a second set of server components. 1. Mount the device that contains the installation files. 2. Type ./install.sh in the command line and press Enter.

212

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Deployment Scenarios Desktop client to server scenario

12

The installation setup program is launched. 3. Select a language for the installation and press Enter. The software license agreement is displayed. 4. Type y to agree to the terms. 5. Enter your BusinessObjects Enterprise product activation keycode in the Business Objects Enterprise Product Keycode field and press Enter. 6. Specify the installation directory for your BusinessObjects Enterprise installation. 7. Select the language pack you want to install and press Enter. You are prompted to select either a user or system installation. 8. Select user and press Enter. The "Installation Type" screen is displayed. 9. Select Custom from the list of options on the Installation Type screen and press Enter. The "Features" screen is displayed. 10. Deselect the following top level features by typing X in all the corresponding markers.
Items to deselect Client Components Server Components

Ensure that the deselected features appear as [ ] before continuing. 11. Expand Server Components and select the following:
Items to select Central Management Server Event Server Input File Repository Server Output File Repository Server

a. Under Central Management Server deselect the following:

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

213

12

Deployment Scenarios Desktop client to server scenario

Items to deselect Auditor MySQL

b. Press Enter. You are prompted if this is the first CMS cluster in your deployment 12. Select Yes and press Enter. The "Enter the information for your new CMS" screen is displayed. 13. Press Enter to accept the default values in the Enter the information for your new CMS and leave the password fields blank. You are prompted to select a system database option. 14. Select Oracle and press Enter. A screen is displayed to provide configuration details for the oracle database server. 15. Type the following details and press Enter.
Field Oracle TNSNAME User ID Password Type the following DBSERVER1_ora mycompanyuser mypassword

A new screen prompts you about reinitializing the database. 16. Select Yes. The "Enter Server Intelligence Agent information screen" is displayed. 17. Type SIA_1 in Server Intelligence Agent Node and press Enter. the "Select Web Application Server" screen is displayed. 18. Select the Install Tomcat, deploy web applications and press Enter. The "Please enter port numbers for the Tomcat installation screen" is displayed. 19. Press Enter to accept the default values. A screen is displayed with your specified installation directory.

214

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Deployment Scenarios Desktop client to server scenario

12

20. Press Enter to start the installation. The installation program validates your system before installing BusinessObjects Enterprise in the specified directory.

To add servers to the server tier
You need to install the framework servers on SERVER 1 before you can add any servers to the server tier. Use the following instructions to add BusinessObjects Enterprise servers to the CMS cluster you have installed on SERVER 1. 1. Mount the device that contains the installation files . 2. Type ./install.sh in the command line and press Enter. The installation setup program is launched. 3. Select a language for the installation and press Enter . The software license agreement is displayed. 4. Type y to agree to the terms. 5. Enter your BusinessObjects Enterprise product activation keycode in the Business Objects Enterprise Product Keycode field and press Enter. 6. Specify the installation directory for your BusinessObjects Enterprise installation. 7. Select the language pack you want to install and press Enter. You are prompted to select either a user or system installation. 8. Select user and press Enter. The "Installation Type" screen is displayed. 9. Choose Custom or Expand. in the "Installation Type" screen. 10. Deselect all the following top-level features by typing X in all the corresponding markers:
Items to deselect Client Components Web Tier Components Note: Ensure that the markers appear as [ ] before continuing.

11. Expand Server Components and deselect the following items:

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

215

12

Deployment Scenarios Desktop client to server scenario

Items to deselect Central Management Server Event Server Input File Repository Server Output File Repository Server Note: Ensure that the markers appear as [ ] before continuing.

12. Press Enter to submit your custom installation sections. You are prompted to enter the name and port number of an existing CMS. 13. Type Server1 in CMS Hostname; leave Port and Existing CMS Administrator Password blank. Press Enter The "Enter Server Intelligence Agent information" screen is displayed. 14. Type SIA_2 in Choose a name for the Server Intelligence Agent Node and Press Enter. A screen is displayed with your specified installation directory. 15. Press Enter to start the installation. The installation program validates your system before installing BusinessObjects Enterprise in the specified directory.

To assign static port values to servers
Access the Central Management Console (CMC) on the machine named SERVER1. Use the machine you designated to run the client tier, and open a browser and type in the following URL: http://SERVER1:8080/Cm cApp/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.

216

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Deployment Scenarios Desktop client to server scenario

12

Field System User Name Password Authentication Type

Required configuration information SERVER1 Administrator BOBJ_admin Enterprise

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 "Common Settings". 5. Click Save & Close. The list of available servers is displayed again. 6. Repeat steps 3-5 for the following servers:
Server name SIA_1.InputFileRepository SIA_1.OutputFileRepository Port number to specify 6404 6406

You will need to pass the port numbers - 6402, 6404, and 6406 - when configuring the firewall.

To configure the firewall
The iptables firewall is running on a supported Red Hat Linux operating system with two network interface cards (NIC). One network card (interface eth0) is connected to an internal secure network, the other (interface eth1) is connected to an external unsecured network, such as the internet.
Note: Advanced administrative knowledge of Red Hat Linux products is

required for these steps.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

217

12

Deployment Scenarios Desktop client to server scenario

The following steps illustrate how to forward requests from clients on an unsecured external (interface eth1) network to the server tier running on a secure, firewalled network (interface eth0). 1. Log in to your Red Hat Linux server.
Note: As iptables is configured from the command-line, you need root

privileges. This can be achieved with the su or sudo commands, by becoming a member of the admin group, or by logging in as the root user. 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 interface

information. Record the network information in a safe place. 3. Add exceptions to the iptables firewall rules that forward incoming client requests to the server tier on the appropriate ports. For example, the sever named CMS Server uses two port numbers to communicate with clients. You must forward both ports on the firewall's external NIC to the CMS server connected to the internal NIC.
Note: This must be done for each port used by every server you want

accessible from outside your network. Typical servers used by external clients include the CMS, Desktop Intelligence, and the Connection Server. In this scenario, four ports must be forwarded to the server tier from external 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 Central

Management Console (CMC) and go to Servers > Central Management Server > your server and note the number for Request Port and Name Server Port. Clients on an unsecured network outside the firewall can now access the server tier through the firewall.

218

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Deployment Scenarios Desktop client to server scenario

12

To set up the client tier
Windows Server 2003 SP2 Enterprise Edition has to be installed and running on 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 list provided and click OK.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

219

12

Deployment Scenarios Desktop client to server scenario

The "Welcome to the BusinessObjects Enterprise XI 3.0 Installation Wizard" 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.

220

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Deployment Scenarios Desktop client to server scenario

12

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.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

221

12

Deployment Scenarios Desktop client to server scenario

7. Accept the default directory by clicking "Next". The "Select Features" screen is displayed. 8. Left-click on the icon beside Client Components and select Entire feature will be unavailable. The Client Components icon changes to 9. Expand Client Components and left- click on Desktop Intelligence.

222

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Deployment Scenarios Desktop client to server scenario

12

10. Select Entire feature will be installed on local hard drive and click Next. The "Start Installation" screen is displayed. 11. Click Next to start the installation. The installation process begins and is completed once "BusinessObjects Enterprise XI 3.0 Client Tool has been successfully installed" is displayed.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

223

12

Deployment Scenarios Desktop client to server scenario

12. Click Finish. The Desktop Intelligence is now installed on your machine. 13. Go to Programs > BusinessObjects XI 3.0 > BusinessObjects Enterprise Client Tools > Desktop Intelligence The "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.

224

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Deployment Scenarios Desktop client to server scenario

12

The "New Report Wizard" is displayed.

15. Select Generate a standard report and click Begin.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

225

12

Deployment Scenarios Basic N-tier scenario

Basic N-tier scenario
N-tier scenario overview
This section describes how to setup a scenario in which a web browser accesses 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 Installation platform for BusinessObjects Enterprise Database for Central Management Server (CMS) Web application server Firewall Solaris 10 MySQL Tomcat 5.5 Linux iptables

Basic n-tier diagram

The following diagram illustrates the system overview for the scenario once it is implemented.

226

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Deployment Scenarios Basic N-tier scenario

12

Summary of required tasks
The basic n-tier deployment scenario involves the following tasks in the order listed below. 1. 2. 3. 4. 5. Setting up the data tier Setting up the server tier Setting up the web tier Setting up the firewall Setting up the client tier

Deploying the basic N-tier scenario
To set up the data tier
The following steps require that you have already installed a version of Sun Solaris 10 that meets the installation requirements for MySQL. Advanced administrative knowledge of MySQL and Sun Solaris 10 products is assumed.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

227

12

Deployment Scenarios Basic N-tier scenario

This database will be used to hold CMS data. Additional database will be created 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 performance

management, you also require access to your existing corporate reporting database. This is the database that hosts your organization's data, against which BusinessObjects Enterprise applications run. 1. Install MySQL. Make note of the following settings you use during the installation. You will need these settings when you come to install BusinessObjects Enterprise servers and clients.
Setting Name of database server Administrator account name Administrator account password Database character set encoding Example DBSERVER1_mysql system password UTF-8

A database is now installed and ready to be used by BusinessObjects Enterprise. 2. Create or import a new tablespace for the CMS, as well as auditing or Performance Management databases if required. Record the settings used for creating of the CMS database.
CMS database setting CMS tablespace name Username for CMS tablespace access Password for CMS tablespace access Example mycompany mycompanyuser mypassword

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.

228

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Deployment Scenarios Basic N-tier scenario

12

Auditing database setting Auditing tablespace name Username for auditing tablespace access Password for auditing tablespace access

Example bobjaudit audituser auditpassword

An auditing database is now available for use. 4. Create or import a new tablespace for the Performance Management tablespace, if required. Record the settings used for creating of the Performance Management tablespace.
Performance Management database setting Performance Management database name Username for PM database access Password for PM database access Example bobjpm pmuser pmpassword

A Performance Management tablespace is now available for use. 5. Create a network-shared directory on the database server's local file system to contain shared files for the file repository server (FRS).
Note: The network permissions for FRS directory must included read,

write, and execute permissions for the networked users. 6. Extract the FRS template file (e.g. FileStore_02-22-2008.zip) within the FRS directory you created in the last step. You have set up CMS, auditing, and performance management databases, as required. You have also installed a file repository server network-shared directory. The default listener port number used by MySQL is 3306. The database port number must be entered during the BusinessObjects Enterprise installation. Verify the connectivity between your CMS and database machines by attempting to connect to your database(s) from the CMS server(s).
Note: This scenario includes a network firewall between the CMS and

database servers. Ensure that this firewall is configured appropriately.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

229

12

Deployment Scenarios Basic N-tier scenario

Remember: The ability to connect to your database server from your CMS

server may require a change to the firewall settings on both machines.

To set up the server tier - framework servers
Sun Solaris 10 has to be installed and running on the three machines running the server tier. Designate the machines SERVER1, SERVER2, and SERV ER3. For information on installing and configuring Solaris 10, consult your Solaris 10 documentation. Use the following instructions to create BusinessObjects Enterprise your CMS cluster on SERVER 1. 1. Mount the device that contains the installation files. 2. Type ./install.sh in the command line and press Enter. The installation setup program is launched. 3. Select a language for the installation and press Enter . The software license agreement is displayed. 4. Type y to agree to the terms. 5. Enter your BusinessObjects Enterprise product activation keycode in the BusinessObjects Enterprise Product Keycode field and press Enter. 6. Specify the installation directory for your BusinessObjects Enterprise installation. 7. Select the language pack you want to install and press Enter. You are prompted to select either a user or system installation. 8. Select user and press Enter. The "Installation Type" screen is displayed. 9. Choose Custom or Expand. in the "Installation Type" screen. The "Features" screen is displayed. 10. Deselect the following top-level features by typing X in the corresponding markers:
Items to deselect Client Components Web Tier Components

230

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Deployment Scenarios Basic N-tier scenario

12

Items to deselect Server Components Note: Ensure that the markers appear as [ ] before continuing.

11. Expand Server Components and select the following servers:
Items to select Central Management Server Event Server Input File Repository Server Output File Repository Server

12. Expand Central Management Server and deselect MySQL and Auditor. 13. Press Enter to submit your custom installation selections. You are prompted in a new screen to specify if this is your first CMS in your deployment. 14. Select Yes - this is the first CMS in this deployment. You are prompted to provide information on the CMS you are about to install. 15. Press Enter to accept the default CMS settings. You are prompted to select a database type for the CMS. 16. Select MySQL. The MySQL configuration screen is displayed. 17. Type the following information for the MySQL database and press Enter to submit the database configuration details.
Field Enter the following DBSERVER1_mysql system

Host Name User ID for CMS database

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

231

12

Deployment Scenarios Basic N-tier scenario

Field

Enter the following password 3306 mycompany

Password for CMS database MySQL port number Database name for CMS

A new screen prompts you about reinitializing the database. 18. Select Yes press Enter. The "Enter Server Intelligence Agent Information screen" is displayed. 19. Type SIA_1 in Choose a name for the Server Intelligence Agent Node and Press Enter. A screen is displayed with your specified installation directory. 20. Press Enter to start the installation. The installation program validates your system before installing BusinessObjects Enterprise in the specified directory.

To add processing servers to the server tier
You need to install the framework servers on SERVER 1 before you can add any servers to the server tier. Use the following instructions to add BusinessObjects Enterprise servers to the CMS cluster you have installed on SERVER 1. 1. Mount the device that contains the installation files. 2. Type ./install.sh in the command line and press Enter. The installation setup program is launched. 3. Select a language for the installation and press Enter. The software license agreement is displayed. 4. Type y to agree to the terms. 5. Enter your BusinessObjects Enterprise product activation keycode in the Business Objects Enterprise Product Keycode field and press Enter. 6. Specify the installation directory for your BusinessObjects Enterprise installation. 7. Select the language pack you want to install and press Enter.

232

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Deployment Scenarios Basic N-tier scenario

12

You are prompted to select either a user or system installation. 8. Select user and press Enter. The "Installation Type" screen is displayed. 9. Choose Custom or Expand in the "Installation Type" screen. The "Features" screen is displayed. 10. Deselect all the following top-level features by typing X in all the corresponding markers:
Items to deselect Client Components Web Tier Components Note: Ensure that the markers appear as [ ] before continuing.

11. Expand Server Components and deselect the following items:
Items to deselect Central Management Server Event Server Input File Repository Server Output File Repository Server Dashboard and Analytics Servers Note: Ensure that the markers appear as [ ] before continuing. Scroll

down the "Features" screen to access Dashboard and Analytics Servers. 12. Press Enter to submit your custom installation sections. You are prompted to enter the name and port number of an existing CMS. 13. Type SERVER1 in CMS Hostname; leave Port and Existing CMS Administrator Password blank. Press Enter. The "Enter Server Intelligence Agent information" screen is displayed. 14. Type SIA_2 in Choose a name for the Server Intelligence Agent Node and Press Enter.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

233

12

Deployment Scenarios Basic N-tier scenario

A screen is displayed with your specified installation directory. 15. Press Enter to start the installation. The installation program validates your system before installing BusinessObjects Enterprise servers in the specified directory.

To add performance management servers to the server tier
You need to install the framework servers on SERVER 1 before you can add any servers to the server tier. Use the following instructions to add BusinessObjects Enterprise servers to the CMS cluster you have installed on SERVER 1. 1. Mount the device that contains the installation files. 2. Type ./install.sh in the command line and press Enter. The installation setup program is launched. 3. Select a language for the installation and press Enter. The software license agreement is displayed. 4. Type y to agree to the terms. 5. Enter your BusinessObjects Enterprise product activation keycode in the Business Objects Enterprise Product Keycode field and press Enter. 6. Specify the installation directory for your BusinessObjects Enterprise installation. 7. Select the language pack you want to install and press Enter. You are prompted to select either a user or system installation. 8. Select user and press Enter. The "Installation Type" screen is displayed. 9. Choose Custom or Expand in the "Installation Type" screen. The "Features" screen is displayed. 10. Deselect all the following top-level features by typing X in all the corresponding markers:
Items to deselect Client Components Web Tier Components Server Components

234

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Deployment Scenarios Basic N-tier scenario

12

Note: Ensure that the markers appear as [ ] before continuing.

11. Expand Server Components and select Dashboard and Analytics Servers.
Note: Scroll down the "Features" screen to access Dashboard and

Analytics Servers. 12. Press Enter to submit your custom installation sections. You are prompted to enter the name and port number of an existing CMS. 13. Type SERVER1 in CMS Hostname; leave Port and Existing CMS Administrator Password blank. Press Enter The "Enter Server Intelligence Agent information" screen is displayed. 14. Type SIA_3 in Choose a name for the Server Intelligence Agent Node and Press Enter. A screen is displayed with your specified installation directory. 15. Press Enter to start the installation. The installation program validates your system before installing BusinessObjects Enterprise servers in the specified directory.

To set up the web tier
Sun Solaris 10 has to be installed and running on the machine that will host the web tier. Follow the procedure to install Tomcat 5.5 and deploy the BusinessObjects Enterprise web applications. 1. Mount the device that contains the installation files. 2. Type ./install.sh in the command line and press Enter. The installation setup program is launched. 3. Select a language for the installation and press Enter. The software license agreement is displayed. 4. Type y to agree to the terms. 5. Enter your BusinessObjects Enterprise product activation keycode in the Business Objects Enterprise Product Keycode field and press Enter. 6. Specify the installation directory for your BusinessObjects Enterprise installation.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

235

12

Deployment Scenarios Basic N-tier scenario

7. Select the language pack you want to install and press Enter. You are prompted to select either a user or system installation. 8. Select user and press Enter. The "Installation Type" screen is displayed. 9. Select Install Web Tier features in the "Installation Type" screen. The "Features" screen is displayed. 10. Press Enter to accept the default settings. You are prompted to specify an existing CMS for the web tier features. 11. Type SERVER1 in the CMS Hostname and press Enter to accept default values for the other settings. You are prompted to select what kind of Java application server to install. 12. Select Install Tomcat, deploy web applications. The Tomcat configuration screen is displayed. 13. Press Enter to accept default port numbers for the Tomcat server. A screen is displayed with your specified installation directory. 14. Press Enter to start the installation. The installation program validates your system before starting the installation. You need provide the default port settings for the Tomcat Server to setup the firewall.

To configure the firewall
The iptables firewall is running on a supported Red Hat Linux operating system with two network interface cards (NIC). One network card (interface eth0) is connected to an internal secure network, the other (interface eth1) is connected to an external unsecured network, such as the internet.
Note: Advanced administrative knowledge of Red Hat Linux products is

required for these steps. The following steps illustrate how to forward requests from clients on an unsecured external (interface eth1) network to port 8080 on for a Oracle Application Server 10g R3 web application server running on a secure, firewalled network (interface eth0).

236

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Deployment Scenarios Basic N-tier scenario

12

1. Log in to your Red Hat Linux server.
Note: As iptables is configured from the command-line, you need root

privileges. This can be achieved with the su or sudo commands, by becoming a member of the admin group, or by logging in as the root user. 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 interface

information. Record the network information in a safe place. 3. Add an exception to the iptables firewall rules that forwards incoming client requests on port 8080 to port 8080 on the web application server. Clients on an unsecured network outside the firewall can now access the web 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 run the client tier. 1. Insert the BusinessObjects Live Office XI 3.0 CD into your computer CD-ROM drive. 2. Choose your preferred language for the installation setup from the list on the left and click Install. The Live Office Installation Wizard is displayed. 3. Follow the on-screen instructions in the Live Office Installation Wizard to complete 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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

237

12

Deployment Scenarios Basic N-tier scenario

7. Enter http://WEBSERVER1:8080/dswsbobje/services/session in the Web Service URL and System fields. 8. Select the Enterprise authentication method from the drop-down list, click Log On and then click OK.

238

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Get More Help

A

A

Get More Help

Online documentation library

Business Objects offers a full documentation set covering all products and their deployment. The online documentation library has the most up-to-date version of the Business Objects product documentation. You can browse the library contents, do full-text searches, read guides on line, and download PDF versions. The library is updated regularly with new content as it becomes available. 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 about Customer Support programs and services. It also has links to a wide range of technical information including knowledgebase articles, downloads, and support forums. http://www.businessobjects.com/support/
Looking for the best deployment solution for your company?

Business Objects consultants can accompany you from the initial analysis stage to the delivery of your deployment project. Expertise is available in relational and multidimensional databases, in connectivities, database design tools, customized embedding technology, and more. For more information, contact your local sales office, or contact us at: http://www.businessobjects.com/services/consulting/
Looking for training options?

From traditional classroom learning to targeted e-learning seminars, we can offer a training package to suit your learning needs and preferred learning style. Find more information on the Business Objects Education web site: http://www.businessobjects.com/services/training

240

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Get More Help

A

Send us your feedback

Do you have a suggestion on how we can improve our documentation? Is there something you particularly like or have found useful? Drop us a line, and we will do our best to ensure that your suggestion is included in the next release of our documentation: mailto:documentation@businessobjects.com
Note: If your issue concerns a Business Objects product and not the

documentation, please contact our Customer Support experts. For information about Customer Support visit: http://www.businessobjects.com/support/.

Business Objects product information

For information about the full range of Business Objects products, visit: http://www.businessobjects.com.

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

241

A

Get More Help

242

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Index
A
adding performance management 141 AddOrRemovePrograms.sh 140 automated startup on UNIX 73, 93, 103

D
database permissions 36 preparing your existing 35 database server options MySQL 32 tested database servers 30 database server preparations 35 database setup 36 database, CMS 32 DB2 32, 43 deployment documentation 10 JBoss 202 Oracle Application Server 201 SAP Application Server 203 Tomcat 200 Tomcat clusters 200 verifying 156, 192 WebLogic 196 WebLogic clusters 197 WebSphere 193 WebSphere cluster 194 WebSphere Community Edition 204 deployment options install Tomcat 67, 87, 98 manual deployment 67, 87, 98 select supported web application 67, 87, 98 deployment scenarios desktop client to server 208 general overview 208 deployments, complex installing language packs 133

B
basic web tier scenario configuration details 226 diagram 226 overview 226 system layers 226 BobjEnterprise120 73, 93, 103 BusinessObjects Enterprise documentation 10 new features 12 uninstalling 140 uninstalling from UNIX 140

C
ccm.sh 126 CD 54 copying to your machine 54 running the install from 54 checklist for installation 52 client tools, installing 28 CMS database on UNIX 43 setting up on UNIX 32 copying the product distribution 54 custom installation 26 custom or expand installation 76 available features 76

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

243

Index

distributed install BusinessObjects Enterprise 76 distributed installation 76 dswsbobje.war WebLogic deployment 199

E
enabling servers, with ccm.sh 126 environment database 32, 43 environment variables DB2 39 MySQL 38 Oracle 38, 41 Sybase 42

F
firewall iptables configuration 217 firewalls 22

I
Import Wizard 28 install types 25 client tools 28 custom installation 26 install.sh 53, 55 installation running scripted 107 web application server 50, 149 installation checklist 52 installation log file 146 installation on UNIX system vs user 59 installation overview 16 installation setup accepting license agreement 57 clustering servers 85

installation setup (continued) clustering to a CMS 87, 97 CMS administrator password 63 configuring existing database 64 configuring existing server 68, 89, 99 configuring MySQL installation 66 configuring Tomcat 68, 88, 98 enable servers 62 entering product keycode 57 install MySQL 63 installation directory 57 installing language packs 57 mounting files 56 selecting installation type 59 selecting new 62 selecting setup language 56 selecting user or system 58 selecting web application server option 67, 87, 98 Server Intelligence Agent 67, 85 specifying CMS clustering 82 specifying CMS port 63 starting the installation 72, 86, 92, 102 use existing database 63 installation type user vs system 23 web tier 96 installation types 27 web tier 27 installing 28 client tools 28 on UNIX 53, 55 iptables 217

J
JBoss manual deployment 202

244

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Index

L
language packs definition 132 English fallback 132 fallback to English 132 installation on UNIX 133 installing 134 locale 132 locating 134 manual deployment 133 Product Locale 132 selecting locale 132 silent mode 135 uninstalling 136 log file installation 146

R
response file parameter list 108

S
SAP Application Server manual deployment 203 scripted installation parameter list 108 running 107 scripted installation on UNIX 106 server choosing location 25 server communication multiple NIC hosts 23 set up 23 Server Intelligence Agent specifying node name 67, 85 specifying port 67, 85 servers assigning static ports 216 servers starting with ccm.sh 126 servers, starting with ccm.sh 126 side-by-side installation 29 silent installation on UNIX 106, 117 Sybase 32, 43 system installation on UNIX 59, 73, 93, 103 system requirements 16

M
MySQL 32

O
Oracle 32, 43 Oracle Application Server manual deployment 201

P
performance management adding to installation 141 AddOrRemovePrograms.sh 141 setup 127 post install deployments 126 preparing for installation 52 preparing your database server 35 Publishing Wizard 28, 53

T
Testing MySQL database environment variables 38 Tomcat manual deployment 200 specifying port numbers 68, 88, 98 Tomcat clusters manual deployment 200

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

245

Index

U
Unicode 32 uninstalling AddOrRemovePrograms.sh running 140 procedure 140 uninstalling from UNIX 140 UNIX 20 character set translation 20 creating login environment 21 environment 20 host name requirements 22 network requirements 22 required commands and utilities 20 setting the locale 20 setting up your system 20 user vs system installation 23 UNIX permissions 17 user installation on UNIX 59 user rights deploying web applications 18

W
WAR file verifying deployment 156, 192 war files configuring 182 deploying to remote server 182 WAR files context roots 186 deployment guidelines 187 war services 185 wdeploy functionality 150 log file 155 options 155 prerequisites 149

wdeploy (continued) Tomcat 168 with JBoss 179 with Oracle 173 with SAP Application Server 176 with WebLogic 163 with WebSphere 156 web application deployment on remote machines 182 web application server configuring existing server 68, 89, 99 configuring Tomcat 68, 88, 98 Web application server initial installation 50, 149 web services 185 web tier 27 web tier installation available features 97 clustering to a CMS 87, 97 selecting deployment option 67, 87, 98 WebLogic manual deployment 196 WebLogic clusters manual deployment 197 WebSphere JSF implementation 159, 194 manual deployment 193 WebSphere cluster deployment 194 WebSphere Community Edition manual deployment 204 Windows BusinessObjects Enterprise client tools installation 28 Import Wizard 28 Publishing Wizard 28 scripted 106 silent installation 106

246

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Sign up to vote on this title
UsefulNot useful