Professional Documents
Culture Documents
0
Installation and Configuration Guide
for Windows
Windows
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,555,403; 5,857,205; 6,289,352; 6,247,008; 6,490,593; 6,578,027;
6,831,668; 6,768,986; 6,772,409; 6,882,998; 7,139,766; 7,299,419; 7,194,465;
7,222,130; 7,181,440 and 7,181,435. Business Objects and the Business Objects
logo, BusinessObjects, Business Objects Crystal Vision, Business Process On
Demand, BusinessQuery, Crystal Analysis, Crystal Applications, Crystal Decisions,
Crystal Enterprise, Crystal Insider, Crystal Reports, 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. All other names mentioned herein may be trademarks of their respective
owners.
Third-party Business Objects products in this release may contain redistributions of software
Contributors 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-02-29
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
Index 281
1
1 Getting Started
About this documentation
Guide Description
BusinessObjects Enter- This guide covers the key concepts you should
prise Deployment Plan- consider before you begin deploying BusinessOb-
ning Guide jects 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 Enter- Leads you through the steps required to run the
prise Installation and setup program and complete your installation of
Configuration Guide BusinessObjects Enterprise. There are UNIX and
Windows versions of this guide available.
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
Feature Description
Language Packs instal- New languages can be added to your installation using
lation the standalone Language Pack installer.
Deploying web applica- Web applications can now be deployed directly using
tions the BusinessObjects Enterprise installer, or after instal-
lation using either the wdeploy tool or the web applica-
tion server's administration console. Procedures for
several deployment scenarios are considered and
thoroughly documented in this guide.
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:
Ensure that that your system meets the basic requirements for a
BusinessObjects Enterprise XI 3.0 installation.
Consult the BusinessObjects Enterprise XI 3.0 Deployment Planning
Guide.
Consider how you should prepare your infrastructure and set up your
environment including server locations.
Verify that all machines that will be part of your BusinessObjects Enterprise
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.
Choose an installation method.
The following sections list the core software and system requirements, the
choices available to you within the core requirements, and the install methods
available to you for installing BusinessObjects Enterprise XI 3.0.
Related Topics
Installation checklist on page 40
System requirements on page 16
Preparing your existing database server on page 35
System requirements
Network requirements
Note:
The following scenarios are not supported:
Installing on a domain controller.
Installing on a machine where the Windows default security settings given
to the local Administrators group have been modified.
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.
SAP Web Application Server rights to read, create, and modify files in the
$as_dir\$as_sid\$as_instance\j2ee\deploy
ing directory
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 Administrators
Guide.
If you are clustering multiple file repository servers on separate machines,
ensure that each server has read and write permissions to the folder used
to store data.
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
Distributed Deployments
Related Topics
Performing a new installation on page 48
You may want to perform a Custom and Expand installation if you plan to
use BusinessObjects Enterprise in a distributed environment. For example,
in a distributed environment you can install the BusinessObjects Enterprise
Desktop Intelligence server components on one machine, and use another
to host Crystal Reports server components.
After you install BusinessObjects Enterprise on one machine, you can run
a Custom and Expand installation to add server components, create a CMS
cluster, increase available resources, and distribute the processing workload.
You may choose to install all or just some of the above components.
Tip: Consult the Scaling Your System section of the BusinessObjects
Enterprise Administrator's Guide for information on planning how to best
expand your installation to meet the needs of your organization.
Related Topics
Performing a Custom or Expand installation on page 64
The Web Tier installation provides you with all of the components that are
used by the web application server to run BusinessObjects web applications.
Related Topics
Performing a Web Tier installation on page 90
You can install the BusinessObjects Client Tools by either using a distributed
standalone installer or the Custom or Expand installation. The available client
tools are listed below:
Note: The BusinessObjects Enterprise Client Tool Setup program does not
generally require a license key to activate the product. However, Desktop
Intelligence does require that a license key be entered in the CMC after the
installation.
Related Topics
To perform a client tools installation on page 137
You can perform a New, Custom and Expand, or Web Tier installation on
machines containing the following:
BusinessObjects Enterprise XI
BusinessObjects Enterprise XI Release 2
This scenario is called a side-by-side installation in which both
BusinessObjects Enterprise versions can run simultaneously.
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
prexisting BusinessObjects Enterprise version by :
This type of distributed installation also allows you to scale your deployment
of BusinessObjects Enterprise by installing additional servers to meet the
demands of your enterprise. How you choose to expand your system depends
largely upon your current configuration and your reporting requirements.
If you want to use an existing database server, you must create a new
database on your database server before you installing BusinessObjects
Enterprise.
The following database servers are supported for the CMS system and audit
databases:
Oracle
DB2
Sybase
MySQL
Microsoft SQL Server (ODBC)
Note: Review the online BusinessObjects Enterprise supported platforms
document for information related to supported database software and version
requirements:http://support.businessobjects.com/documentation/
During the installation setup, you can choose to reinitialize the existing
database. This will cause new tables to be created in your existing database
to store BusinessObjects Enterprise data. Consult your specific database
server documentation 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).
Related Topics
DB2 database setup requirements on page 32
Oracle database setup requirements on page 33
Sybase database setup requirements on page 34
Microsoft SQL Server database setup requirements on page 35
MySQL database setup requirements on page 34
When you create the database you will use with BusinessObjects Enterprise:
Ensure the CMS database is not partitioned.
If your DB2 CMS database is partitioned, you will have problems creating
the CMS database.
Note: The requirement above does not apply to the Audit database. You
can use a partitioned DB2 database for the Audit database.
Create the database with the following specific settings.
Collating Sequence = Identity
Codeset = UTF-8
Territory = XX
If your DB2 database does not have the correct collating sequence setting,
the users and usergroup objects may not sort properly in the Central
Management Console (CMC). 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 through version 9.1
do 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.
Once the database is created, you will need to prepare it for the
BusinessObjects Enterprise installation.
Related Topics
To prepare your database on page 36
For an Oracle database there are no specific parameters, other than the
setting of UTF-8, that are crucial for BusinessObjects Enterprise to work.
Once the database is created, you will need to prepare it for the
BusinessObjects Enterprise installation.
Related Topics
To prepare your database on page 36
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
the CMS system database. For the 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.
Once the database is created, you will need to prepare it for the
BusinessObjects Enterprise installation.
Related Topics
To prepare your database on page 36
For an existing MySQL database there are no specific parameters that are
crucial for BusinessObjects Enterprise to work, other than the setting of
UTF-8. If you select the option to install and configure MySQL that is supplied
with your installation, the installation creates a MySQL database with the
default settings for the CMS database and the Audit database.
Once the database is created, you will need to prepare it for the
BusinessObjects Enterprise installation.
Related Topics
To prepare your database on page 36
Once the database is created, you will need to prepare it for the
BusinessObjects Enterprise installation.
Related Topics
To prepare your database on page 36
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.
The table below summarizes the information required for configuring your
existing database during the installation setup.
Related Topics
DB2 database setup requirements on page 32
Oracle database setup requirements on page 33
Sybase database setup requirements on page 34
Microsoft SQL Server database setup requirements on page 35
MySQL database setup requirements on page 34
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>
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 ensured that all machines running BusinessObjects Enterprise
components can communicate properly?
Have you tested the database connection between the machine hosting
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 are using your own database server and plan to use auditing, 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 onto the database with your logon ID and password?
Have you decided what web application server to use?
If you plan to use your existing database, has the database client software
been properly configured?
If you are not going to install Tomcat, have you ensured that your existing
web application server has the required JDK installed?
If using an existing web application server, has the server already been
installed and configured?
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?
When you perfrom the following installation setup, all the components
associated with your product key are installed on the local machine. Default
user and group accounts are created, and sample reports are published to
the system.
Use the "License Agreement" screen to review and accept the license
agreement for BusinessObjects Enterprise XI 3.0. You must accept the
Use the "User Information" screen to enter user information and provide a
keycode for your BusinessObjects Enterprise XI 3.0 product.
1. Provide your user credentials in the Full Name and Organization fields.
This information personalizes your installation and is recorded in the
registry.
2. Enter a valid code in the Product Keycode field and click Next.
The "Chose Language Packs" screen is displayed.
You can choose to install specific or all available language packs when
running the BusinessObjects Enterprise installation setup.
1. Select the Language Packs you want to install.
The language packs currently available for installation include:
French
Japanese
German
Spanish
Italian
Chinese Simplified
Chinese Traditional
Korean
Dutch
Swedish
Portuguese (Brazil)
Note: English is a required language and cannot be deselected. You can
also add language packs after installing BusinessObjects Enterprise.
2. Click Next.
The "Install Type" screen is displayed.
Related Topics
Installing language packs on Windows systems on page 129
Related Topics
Installing on a non-system drive on page 20
Distributed deployments overview on page 29
Performing a Web Tier installation on page 90
Performing a Custom or Expand installation on page 64
To perform a new BusinessObjects Enterprise installation on page 48
4
4 New Installation of BusinessObjects Enterprise
Performing a new installation
Related Topics
To perform a new BusinessObjects Enterprise installation on page 48
Beginning your installation on page 41
The "Install Type" screen is displayed once you complete the initial set up
of the BusinessObjects Enterprise installation.
Related Topics
To select an installation type on page 44
Beginning your installation on page 41
1. Provide a name to identify the SIA node in the Node Name field.
2. Specify a port number for the SIA in the Port field.
This port will be used by the SIA to communicate with the Central
Management Server (CMS).
3. Click Next to continue with the installation setup.
Once the SIA information is entered, the port number will be validated
before you can proceed to configure the CMS database for your
installation. A warning will display if the port you specified is not available.
Related Topics
To configure your MySQL database server on page 75
To configure an existing database server on page 76
1. Specify the port number for the MySQL database server in the MySQL
Port Number field.
The default port number is 3306. Use this number unless this port is
unavailable.
Related Topics
To perform a new BusinessObjects Enterprise installation on page 48
To select a web application server configuration option on page 93
b. Use the "SQL Server Logon" screen to select a data source, database,
and to provide user credentials.
c. Click OK to submit your settings.
The "SQL Server Logon" screen is closed and an ODBC DSN entry
is displayed in the CMS Database pane.
If you do not want to specify an auditing database for your new installation
skip to step 6.
3. Select the Auditing Database box to specify an auditing database for
your new installation.
The input fields under the Auditing Database box are activated.
4. Select a database type from the Select existing Auditing database
drop-down list in the Auditing Database pane.
Depending on your database server selection, corresponding input fields
are displayed in the Auditing Database pane.
5. Provide all the required information for the database in the fields provided
in the Auditing Database pane.
6. Select the Reset existing database box to delete all current tables and
entries in the existing database.
Related Topics
To select a web application server configuration option on page 93
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, the Central Management Console or your custom applications.
Use the "Select Web Application Server" screen to either install Tomcat as
your application server, or to work with your existing web application server.
Related Topics
Deploying with the JBoss administrative console on page 211
Deploying with the SAP Application Server console on page 212
1. Accept the default values or specify new port numbers for Connection
port, Shutdown port, and Redirect port.
2. Click Next to continue with the installation setup.
Note: If the port numbers you specified are in use, a warning message
is displayed. To continue you will have to specify unused and valid port
numbers.
The "Start Installation" screen is displayed.
Remember your credentials for the web application server as they may be
required to install BusinessObjects add-ons such as ProcessTracker or
additional language packs.
The" Start Installation" screen is the final screen in the installation setup.
Related Topics
Silent installation overview on page 28
5
5 Custom or Expand Installations
Performing a Custom or Expand installation
You can select or deselect features for your installation through a feature
tree. The tree contains the following top-level features:
Client Components
Web Tier Components
Server Components
Database Access
Export Support
Samples
Help Files
The following sections outline the features available for a Custom or Expand
installation.
When you select the Manage Servers icon on the toolbar you may also
start, stop, restart, disable, enable and force termination of the Enterprise
servers. This tool is also used after installation to change which data
source is used for either the CMS or the auditing database, and to update
objects after a migration.
Mapping Support
Installs the necessary components for building interactive geographic
maps in Crystal Reports.
Enterprise Servers
Central Management Server
MySQL Database Server
Auditor
Event Server
Input File Repository Server
Output File Repository Server
Crystal Reports Cache Server
Crystal Reports Processing Server
Publication Job Server
Web Intelligence Processing Server
Desktop Intelligence Servers
Adaptive Processing Server
Crystal Reports Job Server
Program Job Server
Destination Job Server
List of Values Job Server
Desktop Intelligence Job Server
Adaptive Job Server
Report Application Server
Multi Dimensional Analysis Services Server
Performance Management Servers
Database Access
The Database access feature installs the necessary drivers and files to
provide access to the following data sources:
Data Federator
HP Neoview
MySQL
Generic ODBC
Salesforce.com Driver
Netezza
Microsoft
IBM
IBM DB2
Informix (includes Redbrick)
Progress OpenEdge
Oracle
Sybase
NCR Teradata
Export Support
The Export Support feature provides drivers and files to enable export to a
variety of industry standard file formats.
Character Separated Format (CSV)
Disk File Destination
Rich Text Format (RTF)
Word for Windows Format
Acrobat PDF Format
Text Format
Excel Format
Crystal Reports Format
XML Format
Legacy XML Format
Samples
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. These guides can be accessed after installation from Start >
BusinessObjects XI 3.0 > BusinessObjects Enterprise > Documentation.
Related Topics
To select an installation type on page 44
Related Topics
To specify CMS clustering information on page 72
If you chose not to install MySQL, and are installing server components
through a Custom or Expand installation, you need to provide information in
the "CMS Clustering" screen.
1. If this installation is the first CMS in your deployment, select Yes, enter
the information for the new CMS. You can now do one of the following.
In the fields provided enter information on the CMS port and the
password used by the CMS administrator.
Select the Configure the BusinessObjects Enterprise Administrator
password at a later time box.
2. Select If no..if this server installation is not the first CMS in your
deployment.
a. Specify a port number for your new CMS installation.
Related Topics
To specify Server Intelligence Agent information on page 74
1. Provide a name to identify the SIA node in the Node Name field.
2. Specify a port number for the SIA in the Port field.
This port will be used by the SIA to communicate with the Central
Management Server (CMS).
3. Click Next to continue with the installation setup.
Once the SIA information is entered, the port number will be validated
before you can proceed to configure the CMS database for your
installation. A warning will display if the port you specified is not available.
Related Topics
To configure your MySQL database server on page 75
To configure an existing database server on page 76
1. Specify the port number for the MySQL database server in the MySQL
Port Number field.
The default port number is 3306. Use this number unless this port is
unavailable.
2. Specify and confirm a password for the MySQL root user account in the
MySQL root User Account pane.
3. Select the Enable remote root access box toactivate remote root access
to the database server.
4. Specify and confirm a password for the MySQL BusinessObjects user
account in the MySQL BusinessObjects User Account pane.
5. Click Next to continue the installation setup.
The "Start Installation" screen is displayed.
6. Select the Reset existing database box to delete all current tables and
entries in the existing database.
7. Click Next to continue with the installation setup.
The "Start Installation" screen is displayed. This screen only displays if
a connection is established with the database configuration you provided.
The" Start Installation" screen is the final screen in the installation setup.
Related Topics
Silent installation overview on page 28
Use the procedure below when running a Custom or Expand installation type
to only install the BusinessObjects Enterprise Web Tier Components.
1. Left-click on the icon beside BusinessObjects Enterprise in the "Select
Features" screen.
2. Select Entire feature will be unavailable.
All the icons under BusinessObjects Enterprise will change to .
When you only install Web Tier components as part of a custom or expand
installation, you need to specify an existing CMS. Use the "CMS Clustering"
screen to provide information on CMS to which you want to cluster your web
tier components.
1. Enter information on your existing CMS in the fields provided.
Existing CMS Hostname
Existing CMS Port
CMS Administrator Password
Note: The CMS Hostname defaults to your local computer name.
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, the Central Management Console or your custom applications.
Use the "Select Web Application Server" screen to either install Tomcat as
your application server, or to work with your existing web application server.
1. Accept the default values or specify new port numbers for Connection
port, Shutdown port, and Redirect port.
2. Click Next to continue with the installation setup.
Note: If the port numbers you specified are in use, a warning message
is displayed. To continue you will have to specify unused and valid port
numbers.
The "Start Installation" screen is displayed.
Remember your credentials for the web application server as they may be
required to install BusinessObjects add-ons such as ProcessTracker or
additional language packs.
The" Start Installation" screen is the final screen in the installation setup.
Related Topics
Silent installation overview on page 28
6
6 Web Applications Installation
Performing a Web Tier installation
The Java SDK 1.5 is installed by default with a web tier installation.
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.
Tip: If you have not yet installed the server components in your deployment,
you will not be able to verify the connectivity for the web applications. It is
best practice to install the server and client components to verify connectivity.
The "Install Type" screen is displayed once you complete the initial set up
of the BusinessObjects Enterprise installation.
1. Choose Web Tier in the "Install Type" screen.
2. Specify where to install the BusinessObjects Enterprise components in
the Destination Folder field.
3. Click Next to continue with the installation setup.
The "Select Features" screen is displayed.
Related Topics
To select an installation type on page 44
Beginning your installation on page 41
Use the "Select Features" screen to select and deselect web tier components
when running a Web Tier installation. All the available web tier components
are listed in the feature tree under the BusinessObjects Enterprises node.
Each feature and subfeature has a corresponding icon.
1. Click the icon for a feature you want to select or deselect.
You can do any of the following:
Specify that the selected feature will be installed on the local hard
drive.
Specify that the selected feature and its subfeatures will be installed
on the local hard drive.
Specify that a selected feature and its subfeatures will not be installed.
1. Specify the hostnam for the CMS in the Exisiting CMS Hostname field.
2. Specify the port number used to communicate with the CMS in the
Existing CMS Port field.
The default port number used by the CMS is 6400.
3. Specify the password used by CMS Administrator in the CMS
Administrator Password field.
4. Click Next to continue with the installation setup.
The information on the CMS is verified. Once the verification is complete,
the "Select Web Application Server" screen is displayed.
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, the Central Management Console or your custom applications.
Use the "Select Web Application Server" screen to either install Tomcat as
your application server, or to work with your existing web application server.
1. Accept the default values or specify new port numbers for Connection
port, Shutdown port, and Redirect port.
2. Click Next to continue with the installation setup.
Note: If the port numbers you specified are in use, a warning message
is displayed. To continue you will have to specify unused and valid port
numbers.
The "Start Installation" screen is displayed.
Remember your credentials for the web application server as they may be
required to install BusinessObjects add-ons such as ProcessTracker or
additional language packs.
The" Start Installation" screen is the final screen in the installation setup.
Related Topics
Silent installation overview on page 28
100 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Silent Installation
7
7 Silent Installation
Overview of silent installation
The same parameters are used for both methods. It is recommended that
you use the scripted installation method to run custom installations, so that
you avoid having to pass a large number of parameter settings directly
through the command line.
Note: If you pass a parameter directly in the command line, the setting will
override any setting specified in the .ini file.
These installation methods are particularly useful when you need to quickly
perform multiple installations. You can also integrate the scripts and
commands into your own installation scripts.
Related Topics
Specific ini file parameters for setup.exe on page 103
Silent and scripted installation parameters on page 107
102 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Silent Installation
Specific ini file parameters for setup.exe 7
Specific ini file parameters for setup.exe
There are 3 parameters used in conjunction with the .ini file than can be
used when running setup.exe on the command line.
Parameter Description
-w<filepath/file Writes all the installation settings to an .ini file to the
name.ini> specified filepath. If a filepath is not specified, the file is
stored in the system default %TEMP% folder.
-r <filepath/file Reads the specified.ini file and passes the settings to
name.ini> the installer as settings.
Note: If you pass a parameter directly in the command
line, the setting will override any setting specified in the
.ini file.
Related Topics
Silent and scripted installation parameters on page 107
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 103
7 Silent Installation
Sample .ini script file
.
These settings are recorded in the response file.
6. Click Cancel to abort the installation setup.
All the parameters - user-defined and default - from installation setup are
passed to the .ini file which is stored in the directory specified in step 3.
Note: If a filepath is not specified, the file is stored in the system default
%TEMP% folder.
Related Topics
Specific ini file parameters for setup.exe on page 103
Silent and scripted installation parameters on page 107
104 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Silent Installation
Sample .ini script file 7
AS_ADMIN_IS_SECURE=""
AS_ADMIN_PASSWORD=""
AS_ADMIN_PORT="8080"
AS_ADMIN_USERNAME="admin"
AS_DIR="../Tomcat55"
AS_INSTANCE="localhost"
AS_SERVER="tomcat55"
AS_SERVICE_NAME="BOE120Tomcat"
AS_VIRTUAL_HOST=""
ApplicationUsers="AllUsers"
CADNODE="VANW11AKAHAN"
CADPORT="6410"
CLIENTAUDITINGPORT="6420"
CLIENTLANGUAGE="EN"
CLUSTERCMS="False"
CMSPASSWORD=""
COMPANYNAME="Business Objects"
DATABASEAUDITDRIVER="MySQLDatabaseSubSystem"
DATABASECONNECT=""
DATABASEDB="BOE120"
DATABASEDB_AUDIT="BOE120_AUDIT"
DATABASEDRIVER="MySQLDatabaseSubSystem"
DATABASEDSN="Business Objects CMS"
DATABASEDSN_AUDIT="Business Objects Audit Server"
DATABASENWLAYER_AUDIT="ODBC"
DATABASEPWD="sa"
DATABASEPWD_AUDIT="sa"
DATABASEPWD_MYSQLROOT="sa"
DATABASERDMS_AUDIT="MySQL 5"
DATABASESERVER_AUDIT="localhost"
DATABASEUID="sa"
DATABASEUID_AUDIT="sa"
DATABASE_AUDIT_CONNSVR="connsvr"
ENABLELOGFILE="1"
ENABLESERVERS="1"
INSTALL.LP.DE.SELECTED="1"
INSTALL.LP.EN.SELECTED="1"
INSTALL.LP.JA.SELECTED="1"
INSTALLDBTYPE="SQL"
INSTALLDIR="C:\Program Files\Business Objects\"
INSTALLLEVEL="6"
INSTALLMODE="New"
INSTALLSWITCH="Server"
INSTALL_DB_TYPE="InstallMySQL"
MYSQLPORT="3306"
MYSQL_REMOTE_ACCESS="1"
NEWCMSPASSWORD=""
NSPORT="6400"
PIDKEY="C901B-CUZ6S76-000500J-G9M3"
Privileged="1"
SINGLESERVER=""
SKIP_DEPLOYMENT=""
TOMCAT_CONNECTION_PORT="8080"
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 105
7 Silent Installation
Sample .ini script file
TOMCAT_REDIRECT_PORT="8443"
TOMCAT_SHUTDOWN_PORT="8005"
USERNAME="Licensed User"
WCADOTNETINSTALL=""
WCAJAVAINSTALL="True"
WCATOMCATINSTALL="True"
WDEPLOY_LANGUAGES="en,fr,ja,de,es,it,ko,nl,sv,pt,zh_CN,zh_TW"
WDEPLOY_LATER=""
WEBSITE_METABASE_NUMBER="1"
WEBSITE_PORT="80"
[FEATURES]
REMOVE=""
ADDLOCAL="Tomcat,Universe,Complete,BIPWebComp,Designer,AlwaysIn
stall,
BeforeInstall,VBA62,Reporter,Clients,WRC,DataSourceMigrationWiz
ard,
CrystalBVM,MetaDataDesigner,ConversionTool,ImportWizard,Pub
Wiz,qaaws,
JavaRASSDK,BOEJavaSDK,JavaViewersSDK,RebeanSDK,DevelopersFiles,
WebServicesSDK,UnivTransMgr,wdeploy,WebTierComp,BOEWebServices,
CCM,ServerComponents,Mapping,Repository,CRPE,MetaData,CMS,Audi
tor,
MySQL,EventServer,InputFRS,OutputFRS,CacheServer,PageServer,
PublicationServer,DotNETOnly,ReportAppServer,MDASS,CRJobServer,
DestJobServer,LOVJobServer,DeskIJobServer,ProgramJobServer,
WebIJobServer,AdaptiveJobServer,PublishingService,AdaptivePro
cessingServer,
SearchingService,CrystalReportDataProvider,AuditProxyService,We
bi,
RAS21,DAS,AuditRptUnvEN,DADataFederator,DataAccess,HPNeoview,We
bActivityLog,
OLAP,MyCube,SOFA,DAMySQL,DAGenericOD
BC,SFORCE,XML,BDE,dBase,FileSystem,
DANETEZZA,DAMicrosoft,DAIBMDB2,IBM,Redbrick,DAIBMIn
formix,OLE_DB_
Data,DAProgressOpenEdge,DAOracle,SybaseAnywhere,DASy
base,SybaseASE,
SybaseIQ,SymantecACT,DANCRTeradata,TextDA,Btrieve,CharacterSep
arated,
ExportSupport,ExpDiskFile,ExpRichTextFormat,ExpWordforWin
dows,PDF,
ExpText,ExpExcel,ExpCrystalReports,XMLExport,LegacyXMLExport,Sam
plesEN,
UserHelp,LanguagePackCostingFeatureen,LanguagePackCostingFea
ture"
ADDSOURCE=""
ADVERTISE=""
This script can now be used for future silent installations by including the file
name and path in the command line as shown below:
setup.exe -r FILEPATH
106 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Silent Installation
Silent and scripted installation parameters 7
Silent and scripted installation
parameters
The following table lists common parameters that are used for both silent
and scripted installations of BusinessObjects Enterpriseon Windows.
Caution: If you pass a parameter directly in the command line, the setting
will override any setting specified in the .ini file.
Parameter Description
/qn Specifies not to prompt during or after the installation.
Note: You must also enter the CLIENTLANGUAGE
parameter as part of your silent install string or the
language selection screen will appear at the beginning
of your install.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 107
7 Silent Installation
Silent and scripted installation parameters
Parameter Description
AS_DIR Specifies the installation directory for the web applica-
tion server.
AS_DIR="<INSTALLDIR>/Tomcat55"
108 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Silent Installation
Silent and scripted installation parameters 7
Parameter Description
CLIENTLANGUAGE Specifies the language used by the installer:
EN=English
ZH_CN=Simplified Chinese
ZH_TW=Traditional Chinese
DE=German
ES=Spanish
KO=Korean
NL=Dutch
JA=Japanese
PT=Portuguese
SV=Swedish
RU=Russian
FR=French
Note: If this parameter not specified, you will be
prompted to select a language when the installation
setup begins.
CLIENTLANGUAGE="EN"
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 109
7 Silent Installation
Silent and scripted installation parameters
Parameter Description
DATABASEDB Name of the CMS database on the database server.
DATABASEDB="BOE120"
110 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Silent Installation
Silent and scripted installation parameters 7
Parameter Description
DATABASERDMS_AU Specifies the auditing database type. To change this
DIT setting, it is recommended that you create a new ini
file.
DATABASERDMS_AUDIT="MySQL 5"
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 111
7 Silent Installation
Silent and scripted installation parameters
Parameter Description
INSTALL.LP.< >.SE- Specifies which language pack to install. The following
LECTED options are available :
EN=English
ZH_CN=Simplified Chinese
ZH_TW=Traditional Chinese
DE=German
ES=Spanish
KO=Korean
NL=Dutch
JA=Japanese
PT=Portuguese
SV=Swedish
RU=Russian
FR=French
Note: The English language pack is always selected
by default.
INSTALL.LP.EN.SELECTED="1"
INSTALL.LP.JA.SELECTED="1"
112 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Silent Installation
Silent and scripted installation parameters 7
Parameter Description
NSPORT Specifies the port used by the CMS.
NSPORT="6400"
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 113
7 Silent Installation
Silent and scripted installation parameters
Parameter Description
ADDLOCAL Specifies which client, server, web tier, and other
BusinessObjects Enterprise components will be in-
stalled. To change this setting, it is recommended that
you create a new ini file.
ADDLOCAL="Tomcat,Universe,Complete,BIPWeb
Comp,Designer,AlwaysInstall,
BeforeInstall,VBA62,Re
porter,Clients,WRC,DataSourceMigrationWiz
ard,
CrystalBVM,MetaDataDesigner,Conversion
Tool,ImportWizard,PubWiz,qaaws,
JavaRASSDK,BOEJavaSDK,JavaViewersSDK,Re
beanSDK,DevelopersFiles,
WebServicesSDK,UnivTransMgr,wde
ploy,WebTierComp,BOEWebServices,
CCM,ServerComponents,Mapping,Reposito
ry,CRPE,MetaData,CMS,Auditor"
Parameter name
DATABASECONNECT
DATABASE_AUDIT_CONNSVR
INSTALLDBTYPE
INSTALL_DB_TYPE
INSTALLLEVEL
INSTALLSWITCH
NEWCMSPASSWORD
Privileged
SINGLESERVER
SKIP_DEPLOYMENT
WCADOTNETINSTALL
114 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Silent Installation
Silent and scripted installation parameters 7
Parameter name
WCAJAVAINSTALL
WCATOMCATINSTALL
WDEPLOY_LANGUAGES
WEBSITE_METABASE_NUMBER
WEBSITE_PORT
ADDSOURCE
ADVERTISE
Related Topics
Specific ini file parameters for setup.exe on page 103
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 115
7 Silent Installation
Silent and scripted installation parameters
116 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
After Installing
BusinessObjects Enterprise
8
8 After Installing BusinessObjects Enterprise
Launching the Central Management Console (CMC)
You can also launch the CMC by going to: Start > Programs >
BusinessObjects XI 3.0 > BusinessObjects Enterprise > BusinessObjects
Enterprise Central Management Console .
It is recommended that you verify your installation by logging into the CMC.
Once you access the CMC you can create users and groups, set up security
policies, and define rights. For more information on using the CMC, see the
BusinessObjects Enterprise Administrator's Guide.
118 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
After Installing BusinessObjects Enterprise
Register your installed product 8
If you are unable to log on to the CMC, consider the following solutions:
1. Did you provide the correct name for the Central Management Server in
the System field?
2. Did you provide the correct user credentials in the User Name and
Password fields?
3. Is the correct method specified in the Authentication field?
4. Check if the Server Intelligence Agent (SIA) is running. Go to Start >
BusinessObjects XI 3.0 > BusinessObjects Enterprise > Central
Configuration Manager. If the SIA is not running, start or enable it.
5. If you did not install MySQL as part of your installation, use the database
client to connect to the database server. See your database documentation
for more information.
6. Are you attempting to connect to a CMS cluster using the @<clustername>
format? If this is your first attempt to connect to this cluster, the CMC will
not know which CMS servers belong to the cluster. In this case, you need
to specify a list of CMS servers in the web.xml which is found in the WEB-
INF folder of the CMC web application war file. Follow the instructions in
the cms.clusters section of the web.xml file for more details. It is also
possible to specify CMS cluster information for the InfoView by modifying
its corresponding web.xml file.
7. Go to Start > BusinessObjects XI 3.0 > BusinessObjects Enterprise
> Diagnostic Tool. Run the tool to verify your deployment.
If none of these solutions work, consider repairing or reinstalling
BusinessObjects Enterprise.
Related Topics
To run diagnostic tests in Windows on page 121
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 119
8 After Installing BusinessObjects Enterprise
Diagnostic Tool
Once registered, you can access Business Objects support programs and
services. The Registration Wizard also provides links for resources to help
you evaluate or purchase Business Objects products.
To access the wizard, go toStart > Programs > BusinessObjects XI 3.0 >
Registration Wizard.
Diagnostic Tool
Currently, the Deployment Diagnostic Tool includes the following test drivers:
Log On/Off - tests logging on and off BusinessObjects Enterprise.
InfoView Test - test logging on and logging off through InfoView.
Web Intelligence Tier - tests creating, viewing, and scheduling a simple
Web Intelligence document.
Crystal Reports Tier - tests creating and scheduling a simple Crystal
Reports document.
Start/Stop Servers - connects to a CMS and queries for all available
servers associated with it, then proceeds to stop and start each one.
120 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
After Installing BusinessObjects Enterprise
Diagnostic Tool 8
Currently, the Deployment Diagnostic Tool includes the following test drivers:
Log On/Off - tests logging on and off BusinessObjects Enterprise.
InfoView Test - test logging on and logging off through InfoView.
Web Intelligence Tier - tests creating, viewing, and scheduling a simple
Web Intelligence document.
Crystal Reports Tier - tests creating and scheduling a simple Crystal
Reports document.
Start/Stop Servers - connects to a CMS and queries for all available
servers associated with it, then proceeds to stop and start each one.
2. In the System field, enter the hostname for the machine you want to
connect to.
Information for the local machine will appear by default.
3. Enter your user name and password and select the appropriate
authentication type, then click Logon.
If you are authenticated, the main application is screen appears.
The top pane of the tool contains a list of the test drivers that have been
loaded into memory. This list is determined by the contents of the
configuration file.
The bottom pane is the console output and provides status updates while
the tests are running. These updates remain on the display after the tests
are complete.
4. To initiate a diagnostic, select Run All Tests from the Test menu.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 121
8 After Installing BusinessObjects Enterprise
Diagnostic Tool
Upon completion of the diagnostic, the console reads 'Finished Testing' and
provides a file path to the results log file. All test drivers will either conclude
with a 'pass' or a 'fail' status. Double-click the result to view further details.
These details are also recorded in the log file.
To view the log file, either go to the location specified in the console pane,
or select the View menu and then select Log File.
122 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
After Installing BusinessObjects Enterprise
Diagnostic Tool 8
2. Enter the following command:
java -jar
diagnosticTool.jar -[mode] -run
-configfile [config file]
-logfile [log file] -user [username]
-password [password]
-system [system name] -authtype
[authentication type]
Note: If you want to bypass the login screen, you can uncomment the xml tags
in the config file and fill in the necessary authentication tags, as shown below.
<authentication>
<user>administrator</user>
<password> </password>
<system>TestBOESystem</system>
<authtype>Enterprise</authtype>
</authentication>
The following command launches the tool, automatically logs in with the
credentials supplied, uses the default config file and log file, and
automatically runs the test case.
'java -jar
-diagnosticTool.jar -console
-user Administrator -password 'Password'
-system TestBOESystem -authtype Enterprise'
.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 123
8 After Installing BusinessObjects Enterprise
Diagnostic Tool
Diagnostic options
The following section describes some of the option settings for the diagnostic
tool.
Configuration files
Configuration files are used to determine which tests to run, the order in
which to run them, and any parameters for those tests.
To set configuration files
1. Select Set Config File from the Test menu.
A file dialog box used to select the configuration XML is displayed. The
default XML name is 'TestClasses.xml'.
2. Navigate to the XML file you want to set and select it.
3. Click Open, then click OK.
This will set the configuration XML for the tool.
Log files
Log files provide a permanent record of the results of the tests run by the
diagnostic tool. The following procedure shows you how to set the location
for a log file.
To set a custom log file location
1. Choose Set Log File from the Test menu.
The "Set Log File" window appears.
2. Browse to the location where you want to store the log file.
3. Type a name for the log file, and click Open.
Log files for tests will now appear in the directory you selected.
124 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
After Installing BusinessObjects Enterprise
Diagnostic Tool 8
A file dialog box used to select the configuration XML is displayed. The
default XML name is 'TestClasses.xml'.
2. Navigate to the XML file you want to set and select it.
3. Click Open, then click OK.
This will set the configuration XML for the tool.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 125
8 After Installing BusinessObjects Enterprise
Diagnostic Tool
126 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Language Packs on
Windows
9
9 Language Packs on Windows
About language packs
You can install as many different language packs as you want. The default
language pack, English, is always installed.
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.
128 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Language Packs on Windows
Installing language packs 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.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 129
9 Language Packs on Windows
Locating language packs
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_IN
STALL_CD_DIR\langs\LANGUAGE\.
3. Run the setup.exe installer.
Replace LANGUAGE with the ISO code of the language you are installing.
The Microsoft Windows installer will search for all installed Business
Objects applications.
4. Click Next.
5. Check I accept the License Agreement, and then click Next.
6. Enter values for the CMS, CMS Port, User Name, Password, and
Authentication fields. Click Next.
7. Enter values for the Port, Username, Password, Server Instance, and
Virtual Host, and Application Server Installation Directory fields. If
your web application server uses a password for the administrator account,
select the Admin is Secure check-box. Click Next.
8. Click Next to begin the installation.
130 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Language Packs on Windows
Installing language packs across a BusinessObjects Enterprise deployment 9
The language pack will now begin the installation process.
Once the installation is complete, you will be able to choose the installed
language from the Options dialog window in BusinessObjects Enterprise
applications.
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.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 131
9 Language Packs on Windows
Installing language packs across a BusinessObjects Enterprise deployment
For example:
setup.exe
"C:\Program Files\Business Objects\BusinessObjects Enter
prise 12.0"
INSTALLMODE=silent
CMSNAMESERVER=myserver1
CMSPORTNUMBER=6400
CMSPASSWORD=mypassword
Related Topics
How to use wdeploy on page 161
132 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Language Packs on Windows
To uninstall language packs 9
To uninstall language packs
1. Open the Central Management Server (CMS) and ensure that all servers
are running.
2. In Windows, click Start, point to Settings, and then select Control Panel.
3. Double-click Add/Remove Programs.
4. Select the BusinessObjects Enterprise XI 3.0 Language Pack to
remove and click Remove.
The "Add/Remove Programs" prompts you to confirm that you want to
remove the language pack from your computer.
5. Click Yes.
The appropriate files are removed and the necessary configuration is
completed.
6. Click Finish.
The language pack has been uninstalled and you are returned to the
"Add/Remove Programs" list.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 133
9 Language Packs on Windows
To uninstall language packs
134 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Client Tools Installation
10
10 Client Tools Installation
Overview of Client Tools installation
136 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Client Tools Installation
To perform a client tools installation 10
Component Short description
Report Conversion Tool Converts Desktop Intelligence XI R2 reports to
Web Intelligence XI R2 format and publishes
the converted reports to the CMS. The level of
conversion depends on the features in the
original report.
Import Wizard Allows you to import and export content from
previous and current versions of BusinessOb-
jects Enterprise.
Publishing Wizard Enables users to add reports to BusinessOb-
jects Enterprise
Query as a Web Service Allows you create custom web services for
specific queries using Business Objects Web
Services.
Universe Designer Allows you to create universes for Web Intelli-
gence and Desktop Intelligence users.
Developer Components Contains the following subfeatures:
BusinessObjects Enterprise Java SDK: allows
you to build web applications that interface
directly with your BusinessObjects Enterprise
system.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 137
10 Client Tools Installation
To perform a client tools installation
3. Select the language for the installation setup from the pull-down list
provided.
You have a choice of the following languages for setup:
English
French
Japanese
German
Spanish
Italian
Chinese Simplified
Chinese Traditional
Korean
Dutch
Swedish
Portuguese (Brazil)
4. Check the Create log file during installation box if you want to create
an installation log file.
The log file is saved under the following directory:
<INSTALLDIR>\BusinessObjects Enterprise 12.0\Logging.
5. Click OK.
The "Welcome to the BusinessObjects Enterprise XI 3.0 Installation
Wizard" is displayed after you specify a language for the installation setup.
138 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Client Tools Installation
To perform a client tools installation 10
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 139
10 Client Tools Installation
To perform a client tools installation
140 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Client Tools Installation
To perform a client tools installation 10
Tip: Select the All Languages box to select all the available language
packs.
The "Directory Selection" screen is displayed.
9. Type the installation directory for the client tools in Destination Folder
or accept the default selection and click Next.
The "Select Features" screen is displayed.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 141
10 Client Tools Installation
To perform a client tools installation
10. Click the icon for a feature you want to select or deselect under the
"BusinessObjects Enterprise Client Tools" node. When you have finished
making your selections click Next.
You can do any of the following:
Specify that the selected feature will be installed on the local hard
drive.
Specify that the selected feature and its subfeatures will be installed
on the local hard drive.
Specify that a selected feature and its subfeatures will not be installed.
142 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Client Tools Installation
To perform a client tools installation 10
a. Click Disk Cost to calculate if sufficient disk space is available for
your selected features.
A separate screen is displayed indicating storage space available on
the local machine and mapped network drives. Drives that do not have
enough disk space for the currently selected features are highlighted.
Click OK to close to return to the"Select Features" screen.
b. Click Reset to revert to the original configuration of the feature list.
The "Start Installation" screen is displayed.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 143
10 Client Tools Installation
Client Tools silent installations
Scripted installations
Silent installations
144 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Client Tools Installation
Client Tools silent installations 10
Note: If you pass a parameter directly in the command line, the setting will
override any setting specified in the .ini file.
Related Topics
Specific ini file parameters for setup.exe on page 103
To create an installation .ini file on page 103
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 145
10 Client Tools Installation
Client Tools silent installations
LanguagePackCostingFeaturenl"
ADDSOURCE=""
ADVERTISE=""
This script can now be used for future silent installations by including the file
name and path in the command line as shown below:
setup.exe -r FILEPATH
146 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Maintaining your Installation
11
11 Maintaining your Installation
BusinessObjects Enterprise maintenance operations
There are two methods for evoking maintenance mode for BusinessObjects
Enterprise on Windows:
1. Go to Start > Settings > Control Panel > Add or Remove Programs.
a. Select BusinessObjects Enterprise XI 3.0.
b. Click Change.
The "Application Maintenance" screen is displayed.
148 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Maintaining your Installation
Uninstalling BusinessObjects Enterprise from Windows 11
2. Alternatively, you can run the setup.exe program you originally used to
install your current BusinessObjects Enterprise product.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 149
11 Maintaining your Installation
Software Inventory Tool
3. Go to Start > Settings > Control Panel > Add or Remove Programs.
4. Select BusinessObjects Enterprise XI 3.0.
5. Click Remove.
The "Add or Remove Programs" dialog prompts to confirm that you want
to remove BusinessObjects Enterprise XI 3.0.
6. Click Yes.
Please wait while files are removed and your system is reconfigured. You
are prompted once theconfiguration process is complete.
7. Click Finish.
Your BusinessObjects Enterprise installation may have included an installation
of the Apache Tomcat java application server. By default, Tomcat installs to
C:\Program Files\BusinessObjects\Tomcat\. When BusinessObjects
Enterprise is uninstalled, the contents of the Tomcat subfolder are removed.
Note: Only web applications deployed on a Tomcat server installed through
the BusinessObjects Enterprise installer are automatically removed. You will
manually have to remove web applications deployed on other servers.
The installer removes only the files that it originally installed. Folders or files
created after the installation, for example log or report files, are not uninstalled
by the uninstallation process.
Silent uninstallation
If the installation source is available, you can use the command-line console
to unistall BusinessObjects Enterprise. In the command-line specify the
following method:
setup.exe REMOVE=ALL
Introduction
150 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Maintaining your Installation
Software Inventory Tool 11
The tool creates and maintains an inventory of all changes made to Business
Objects software via Business Objects installers and allows users to view
these changes.
Installation
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 151
11 Maintaining your Installation
Software Inventory Tool
Records of the files that are associated with each Business Objects
installation such as WAR files and DLLs.
Note: Closing the Windows Command window will terminate the Java
program.
Viewing Format
152 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Maintaining your Installation
Software Inventory Tool 11
History View
Search
The Viewing Format Area
The Viewing format pane provides three options for what to display.
Install/Patch name
This option displays all the available information logged by the tool in
chronological order.
ADAPT number
This option only displays the ADAPT numbers for modifications logged
by the tool.
Note: ADAPT numbers are only displayed if critical hot fixes have been
installed. ADAPT is the system used internally by Business Objects to
track technical problems and feature enhancements.
File
This option only displays files that have been installed and recorded by
the tool.
History View
The History View is divided into two parts:
History Tree
Node Details
History Tree and the Node Details
The History Tree is the main pane used to navigate the inventory. The
history of installations and changes is listed chronologically; each entry can
be expanded to display further details in the Node Details pane.
Note: To view more specific information you can use the Search function.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 153
11 Maintaining your Installation
Software Inventory Tool
Build number
Installed or Removed
Problem Summary
ADAPT Number
Fix description
Build
154 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Maintaining your Installation
The installation log file 11
The Search pane
The Search pane of the BusinessObjects Software Inventory Tool allows
you to refine the information displayed in History View. It is divided into
three parts:
Enter search string: use this field to enter a string. A new tree is
generated based on the search result and the current view being used.
Search History: lists all the search parameters.
Clear search history: click to clear the Search History.
The log.txt file is saved in the default installation folder together with the
inventory.xml file: C:\Program Files\Business
Objects\common\4.0\java\lib
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 155
11 Maintaining your Installation
The installation log file
156 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web
Application Deployment
12
12 Post Installation Web Application Deployment
Overview of post install deployment
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.
WebSphere 6.1 X X X
WebSphere Com-
X
munity Edition 2.0
WebLogic 10 X X X
WebLogic 9.2 X X X
Tomcat 5.5 X X X
SAP Application
X X
Server 7.0
Oracle Application
X X X
Server 10G R3
JBoss 4.04 X X
158 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Before you deploy web applications 12
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>
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 159
12 Post Installation Web Application Deployment
Deploying with wdeploy
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
Minimum user rights for deploying web applications on page 18
To deploy web applications on a remote machine on page 192
160 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Deploying with wdeploy 12
To use wdeploy , the specific configuration file for your web application
server must be properly configured. This file is located in <INSTALLDIR>\de
ployment\. For example, the configuration file for weblogic 9.2 is config.we
blogic9.
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 Windows 161
12 Post Installation Web Application Deployment
Deploying with wdeploy
162 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Deploying with wdeploy 12
Web appli- Required Configuration details
cation
server
WebLogic as_admin_port: Administration port of the application server
10 (for example "7001").
as_admin_username: WebLogic administrator account user-
name (for example "weblogic").
as_admin_password: WebLogic administrator account pass-
word (for example "weblogic").
as_instance: The name of your WebLogic application server
instance (for example "AdminServer").
as_dir: Weblogic domain directory (for example "C:\bea\we
blogic10\user_projects\domains\base_domain").
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 163
12 Post Installation Web Application Deployment
Deploying with wdeploy
164 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Deploying with wdeploy 12
Web appli- Required Configuration details
cation
server
Oracle Ap- as_admin_port: Administration port of the application server.
plication This is the request port of the notification server, found in the
Server 10 <notification-server> section of configuration file opmn.xml (for
G R3 example "6003").
as_admin_username: Oracle Application Server administrator
account username (for example "ocjadmin").
Note: If as_admin_is_secure is false, a value for as_ad
min_username does not need to be specified.
JBoss 4 as_dir: The location of the JBoss application server (for example
"C:\Program Files\jboss-4.0.4.GA").
as_instance: The name of the JBoss application server instance
(for example "default").
Note:
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 165
12 Post Installation Web Application Deployment
Deploying with wdeploy
Run the wdeploy script by opening command line console and typing the
following:
<INSTALLDIR>\deployment\wdeploy.bat
<appserver> deployall >> <logfilename>.log
For example:
wdeploy.bat weblogic9 deployall >> C:\mylog.log
Note: The <appserver> must be same as the web application server used
in the configuration filename (for example, config.weblogic9).
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
Minimum user rights for deploying web applications on page 18
To deploy web applications on a remote machine on page 192
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.
All other web applications can only be manually removed using the web
application server's administrative console.
166 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Deploying with wdeploy 12
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 (>).
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
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 167
12 Post Installation Web Application Deployment
Deploying with wdeploy
168 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Deploying with wdeploy 12
Example 1: using wdeploy deploy to predeploy, then deploy, InfoView to
WebSphere.
wdeploy.bat websphere6
-Das_dir=C:\IBM\WebSphere\AppServer
-Das_instance=server1
-Das_virtual_host=default_host
-Das_admin_port=8880
-DAPP=InfoViewApp
deploy
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 169
12 Post Installation Web Application Deployment
Deploying with wdeploy
Related Topics
After deploying web applications on page 202
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.
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://myappserv
er.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 dymanic 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/.
170 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Deploying with wdeploy 12
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 wdepoly environment to separate content between the web
server and the web application server. This is known as "distributed"
mode.
The wdeploy configuration files for IHS and WebSphere are located in
<INSTALLDIR>\deployment.
Edit config.apache. For example:
#Business Objects Configuration Utility
ws_dir=C:\Program Files\Apache Software Foundation\Apache
2.2
connector_type=websphere6
deployment_dir=C:\Program Files\Apache Software Founda
tion\Apache 2.2\htdocs
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 171
12 Post Installation Web Application Deployment
Deploying with wdeploy
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
172 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Deploying with wdeploy 12
fig/cells/<cell_name>/nodes/node_name/servers/<Web_server_name>
directory on the WebSphere web application server to the <plug
ins_root>/config/<Web_server_name> directory on the IHS web server.
11. Ensure that both static and dymanic 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, my
webserver.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 161
To deploy web applications on a remote machine on page 192
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 173
12 Post Installation Web Application Deployment
Deploying with wdeploy
174 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Deploying with wdeploy 12
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 Windows 175
12 Post Installation Web Application Deployment
Deploying with wdeploy
-Das_admin_port=7001
-Das_instance=AdminServer
-Das_admin_username=weblogic
-Das_admin_password=weblogic
undeployall
Related Topics
After deploying web applications on page 202
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.
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://myappserv
er.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 dymanic resources are now forwarded to WebLogic when
received by Apache.
176 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Deploying with wdeploy 12
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.mycompany.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 wdepoly 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 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=C:\bea\user_projects\domains\base_domain
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 177
12 Post Installation Web Application Deployment
Deploying with wdeploy
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 161
To deploy web applications on a remote machine on page 192
178 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Deploying with wdeploy 12
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 179
12 Post Installation Web Application Deployment
Deploying with wdeploy
180 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Deploying with wdeploy 12
Example 1: using wdeploy undeploy to undeploy InfoView from Tomcat.
wdeploy.bat tomcat55
-Das_dir=C:\Tomcat5
-Das_instance=localhost
-DAPP=InfoViewApp
-Das_service_name=Tomcat5
undeploy
Related Topics
After deploying web applications on page 202
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
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://myappserv
er.mycompany.com:8080.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 181
12 Post Installation Web Application Deployment
Deploying with wdeploy
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 dymanic 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.mycompany.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 wdepoly 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=C:\Appserver\Tomcat5520
as_instance=localhost
as_service_name=Tomcat5
as_service_key=HKLM\SOFTWARE\Apache Software Foundation\
Procrun 2.0\Tomcat5\Parameters\Java
as_service_key_value=Options
182 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Deploying with wdeploy 12
connector_type=tomcat55
deployment_dir=C:\Webserver\Apache224\htdocs
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 183
12 Post Installation Web Application Deployment
Deploying with wdeploy
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 161
To deploy web applications on a remote machine on page 192
184 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Deploying with wdeploy 12
-Das_admin_port=50000
predeployall
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 185
12 Post Installation Web Application Deployment
Deploying with wdeploy
186 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Deploying with wdeploy 12
-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 202
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 187
12 Post Installation Web Application Deployment
Deploying with wdeploy
188 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Deploying with wdeploy 12
-Das_instance=home
-Das_appserver_name=oc4j_inst1
-Das_group_id=default_group
-Das_admin_port=6003
-Das_admin_username=oc4jadmin
-Das_admin_password=oracle12
-DAPP=InfoViewApp
deploy
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 189
12 Post Installation Web Application Deployment
Deploying with wdeploy
-Das_group_id=default_group
-Das_admin_port=6003
-Das_admin_username=oc4jadmin
-Das_admin_password=oracle12
undeployall
Related Topics
After deploying web applications on page 202
190 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Deploying with wdeploy 12
Example 1: InfoView using wdeploy deployonly to deploy a predeployed
InfoView to JBoss.
wdeploy.bat jboss404
-Das_dir=C:\jboss-4.0.4.GA
-Das_instance=default
-DAPP=InfoViewApp
deployonly
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 191
12 Post Installation Web Application Deployment
Deploying with wdeploy
Related Topics
After deploying web applications on page 202
192 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Deploying with wdeploy 12
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.
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.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 193
12 Post Installation Web Application Deployment
Deploying with wdeploy
For example, to modify the configuration file for WebLogic 9, you would
modify the file to:
as_dir=C:\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>\BusinessObjects Enterprise
12.0\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>C:\Performance Management 12.0</param-value>
</context-param>
194 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Manually deploying to a web application server 12
Related Topics
How to use wdeploy on page 161
Prerequisites for using wdeploy on page 159
Once you have installed BusinessObjects Enterprise the source files are
available in the following directory: <INSTALLDIR>\BusinessObjects
Enterprise 12.0\java\applications\
The following table summarizes the relationship between the WAR files and
specific web applications in a BusinessObjects Enterprise deployment.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 195
12 Post Installation Web Application Deployment
Manually deploying to a web application server
All WAR files, with the exception of InfoViewApp and CmcApp, 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.
CmcAppActions /CmcAppActions
CrystalReports /CrystalReports
dswsbobje /dswsbobje
196 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Manually deploying to a web application server 12
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.
InfoViewAppActions /InfoViewAppActions
OpenDocument /OpenDocument
PerformanceManagement /PerformanceManagement
PlatformServices /PlatformServices
PMC_Help /PMC_Help
VoyagerClient /VoyagerClient
XCelsius /XCelsius
XCTemplateUploader /XCTemplateUploader
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.
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.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 197
12 Post Installation Web Application Deployment
Manually deploying to a web application server
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>
Ensure that your web applicaton 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.bat tomcat55
-Das_dir=C:\Tomcat5520
-Das_instance=localhost
-Das_service_name=Tomcat55
-DAPP=InfoViewApp
predeploy
198 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Manually deploying to a web application server 12
-Das_instance=localhost
-Das_service_name=Tomcat55
predeployall
The wdeploy command will prepare the web applicaton 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.
Repeat these steps for any other web applications that need to be installed.
Related Topics
Where to find wdeploy on page 159
How to use wdeploy on page 161
Minimum user rights for deploying web applications on page 18
To prepare for manual deployment on a remote machine on page 199
Minimum user rights for deploying web applications on page 18
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 199
12 Post Installation Web Application Deployment
Manually deploying to a web application server
<INSTALLDIR>\caf\
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.
c. Repeat steps a-b for all the web applications you want to deploy to
your web application server.
200 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Manually deploying to a web application server 12
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=C:\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>\BusinessObjects Enterprise
12.0\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>C:\Performance Management 12.0</param-value>
</context-param>
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 201
12 Post Installation Web Application Deployment
Manually deploying to a web application server
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 161
Prerequisites for using wdeploy on page 159
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
202 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Manually deploying to a web application server 12
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 202
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.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 203
12 Post Installation Web Application Deployment
Manually deploying to a web application server
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>\Performance Management 12.0\ 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 PerformanceMan
agement.war as shown below:
<context-param>
<param-name>af.configdir</param-name>
<param-value>C:\Program Files\BusniessObjects\Per
formance Management 12.0
</param-value>
<context-param>
Note: The InitConfig.properties file should be located in C:\Program
Files\BusniessObjects\Performance Management 12.0 on each
machine hosting a managed webphere 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.
204 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Manually deploying to a web application server 12
7. After installing the application, click Save.
8. Repeat steps 5-7 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 192
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 205
12 Post Installation Web Application Deployment
Manually deploying to a web application server
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 202
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.
Property Value
Name Registry name
Document Builder Factory weblogic.apache.xerces.jaxp.Document
BuilderFactoryImpl
SAX Parser Factory weblogic.apache.xerces.jaxp.SAXParserFac
toryImpl
Transformer Factory weblogic.apache.xalan.processor.Trans
formerFactoryImpl
206 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Manually deploying to a web application server 12
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 websphere
cluster, you must copy InitConfig.properties from
<INSTALLDIR>\Performance Management 12.0\ 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 PerformanceMan
agement.war as shown below:
<context-param>
<param-name>af.configdir</param-name>
<param-value>C:\Program Files\BusniessObjects\Per
formance Management 12.0
</param-value>
<context-param>
<param-value>replicated</param-value>
</session-param>
</session-descriptor>
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 207
12 Post Installation Web Application Deployment
Manually deploying to a web application server
7. In the "Select deployment targets" workflow select the cluster name and
All servers in the cluster.
8. After the "Select deployment targets" is complete, select all the installed
applications and go to Start > Servicing all requests.
Example:
Deploying the complex deployment scenario in this manual includes a
step-by-step description of how to deploy web applications to a WebLogic
10 cluster.
Related Topics
To deploy the WAR files to WebLogic 10 on page 268
To prepare the WAR files for deployment on page 267
208 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Manually deploying to a web application server 12
10. Click Activate Changes.
11. Select the dswsbobje web application and click Start.
12. Press OK to confirm the changes.
The dswsbobje web application is started.
13. Open the web application in a web browser to confirm that it now runs.
Related Topics
After deploying web applications on page 202
Ensure that your Tomcat web application server is installed, configured, and
running before deploying WAR files.
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" trusted="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 202
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.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 209
12 Post Installation Web Application Deployment
Manually deploying to a web application server
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.
210 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Post Installation Web Application Deployment
Manually deploying to a web application server 12
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 202
Ensure that your JBoss web application server is installed, configured, and
running before deploying WAR files.
The following deployment paths are based upon the different levels of service:
JBOSS_HOME/server/all/deploy
JBOSS_HOME/server/default/deploy
JBOSS_HOME/server/minimal/deploy
1. Copy your WAR files to the appropriate context root sub-directory 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/enterprise120/adminlaunch,
warUrl=.../tmp/deploy/tmp38470admin-exp.war/
06:23:09,562 INFO; [ReportSourceBridge] Servlet viewrpt
started.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 211
12 Post Installation Web Application Deployment
Manually deploying to a web application server
Related Topics
After deploying web applications on page 202
Ensure that your SAP Application Server web application server is installed,
configured, and running before deploying WAR files.
Related Topics
After deploying web applications on page 202
212 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
13
13 Deployment Scenarios
Overview of deployment scenarios
System layers
Data Tier: one machine with existing database server
Server Tier: one machine for hosting the framework servers and another
for all other BusinessObjects servers
Client Tier: one machine for installing and running Desktop Intelligence
Configuration details
A firewall exists between client and server tiers
Only the ports required for the communication between the desktop client
and the server tier are open on the firewall
BusinessObjects servers are distributed over two machines.
Installation platform for BusinessObjects Enterprise Windows Server 2003 SP2 Enterprise
Edition
214 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Desktop client to server scenario 13
Database for Central Management Server (CMS) Microsoft SQL Server 2005
Web application server Not relevant
Firewall Linux iptables
The desktop client to server deployment scenario involves the following tasks
in the order listed below.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 215
13 Deployment Scenarios
Desktop client to server scenario
This scenario calls for Microsoft SQL Server 2005 running on a supported
Microsoft Windows operating system. Advanced administrative knowledge
of Microsoft SQL Server 2005 and Microsoft Windows products is assumed.
Install a version of Microsoft Windows with the appropriate service packs
and updates required by Microsoft SQL Server 2005. If your CMS and
database servers are installed on separate computers, ensure that you have
a working network connection between the machines.
1. Install Microsoft SQL Server 2005.
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 Example
Name of database server instance DBSERVER1_sql
Administrator account name sa
Administrator account password password
Database character set encoding UTF-8
216 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Desktop client to server scenario 13
A CMS database is now available for use.
3. Create or import a new database for auditing database, if required.
Record the settings used for creating of the auditing database.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 217
13 Deployment Scenarios
Desktop client to server scenario
Windows Server 2003 SP2 Enterprise Edition has to be installed and running.
You need administrative privileges on both 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 all other server components.
Follow the instructions below to install the framework servers.
1. Run setup.exe from the root directory of your product distribution.
The "Please Choose Setup Language" dialog is displayed.
2. Select your language for the installation setup from the pull-down list
provided and click OK.
The "Welcome to the BusinessObjects Enterprise XI 3.0 Installation
Wizard" is displayed.
3. Click Next.
The "License Agreement" screen is displayed.
4. Select I accept the License Agreement and click Next.
The "User Information" screen is displayed.
5. Enter the requested information forFull Name, Organization, and Product
Keycode. Click Next.
The "Chose Language Packs" screen is displayed.
6. Select any Language Packs you want to install. Click Next.
Note: English is a required language and is automatically selected.
The "Install Type" screen is displayed
7. Choose Custom or Expand install.
218 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Desktop client to server scenario 13
The "Select Features" screen is displayed.
8. Left-click on the icon beside Client Componentsand select Entire feature
will be unavailable.
The Client Components icon changes to .
9. Left-click on the icon beside Server Components and select Entire
feature will be unavailable.
10. Expand Server Components.
a. Left-click on the icon beside Central Configuration Manager and
select Entire feature will be installed on local hard drive.
b. Left-click on the icon beside Central Management Server and select
Will be installed on local hard drive.
The Central Management Server option will be installed but not the
two subfeatures listed under the item: MySQL and Auditing.
c. Left-click on the icon beside Event Server and selectEntire feature
will be installed on local hard drive.
d. Left-click on the icon beside Input File Repository Server and
selectEntire feature will be installed on local hard drive
e. Left-click on the icon beside Output File Repository Server and
select Entire feature will be installed on local hard drive
f. Click Next.
The "CMS Clustering" screen is displayed.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 219
13 Deployment Scenarios
Desktop client to server scenario
220 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Desktop client to server scenario 13
c. Select BOE120 from the Database drop-down list
d. Click OK.
You are returned to the "CMS Database Information" screen.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 221
13 Deployment Scenarios
Desktop client to server scenario
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. Run setup.exe from the root directory of your product distribution.
The "Please Choose Setup Language" dialog is displayed.
Note: If you are installing from a CD and if the Autoplay is enabled for
your CD-ROM drive, the Autorun program will start automatically.
2. Select your language for the installation setup from the pull-down list
provided and click OK.
222 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Desktop client to server scenario 13
The "Welcome to the BusinessObjects Enterprise XI 3.0 Installation
Wizard" is displayed.
3. Click Next.
The "License Agreement" screen is displayed.
4. Select I accept the License Agreement and click Next.
The "User Information" screen is displayed.
5. Enter the requested information for Full Name, Organization, and
Product Keycode. Click Next.
The "Chose Language Packs" screen is displayed.
6. Select any Language Packs you want to install. Click Next.
Note: English is a required language and is automatically selected.
The "Install Type" screen is displayed
7. Choose Custom or Expand install.
The "Select Features" screen is displayed.
8. Left-click on the icon beside Client Componentsand select Entire feature
will be unavailable.
The Client Components icon changes to .
9. Left-click on the icon beside Web Tier Components and select Entire
feature will be unavailable.
10. Expand Server Components.
a. Left-click on the icon beside Central Configuration Manager and
select Entire feature will be unavailable .
b. Left-click on the icon beside Central Management Server and select
Entire feature will be unavailable.
c. Left-click on the icon beside Event Server and select Entire feature
will be unavailable.
d. Left-click on the icon beside Input File Repository Server and select
select Entire feature will be unavailable.
e. Left-click on the icon beside Output File Repository Server and
select Entire feature will be unavailable.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 223
13 Deployment Scenarios
Desktop client to server scenario
224 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Desktop client to server scenario 13
Server name
SIA_1.CentralManagementServer
SIA_1.InputFileRepository
SAI_1.OutputFileRepository
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 225
13 Deployment Scenarios
Desktop client to server scenario
You will need to pass the port numbers - 6402, 6404, and 6406 - when
configuring the firewall.
226 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Desktop client to server scenario 13
The following steps illustrate how to forward requests from clients on an
unsecure 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
priviliges. 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.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 227
13 Deployment Scenarios
Desktop client to server scenario
Server > your server and note the number for Request Port and Name
Server Port.
Clients on an unsecured network outside the filewall can now access the
server tier through the firewall.
Windows Server 2003 SP2 Enterprise Edition has to be installed and running
on the machine on which you will install Desktop Intelligence.
3. Select the language for the installation setup from the pull-down list
provided and click OK.
228 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Desktop client to server scenario 13
The "Welcome to the BusinessObjects Enterprise XI 3.0 Installation
Wizard" is displayed after you specify a language for the installation setup.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 229
13 Deployment Scenarios
Desktop client to server scenario
230 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Desktop client to server scenario 13
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 231
13 Deployment Scenarios
Desktop client to server scenario
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.
232 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Desktop client to server scenario 13
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 233
13 Deployment Scenarios
Desktop client to server scenario
234 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Basic N-tier scenario 13
Basic N-tier scenario
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 Windows Server 2003 SP2 Enterprise
Edition
Database for Central Management Server (CMS) Oracle 10g R2
Web application server Oracle 10g R3
Firewall Linux iptables
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 235
13 Deployment Scenarios
Basic N-tier scenario
The basic n-tier deployment scenario involves the following tasks in the order
listed below.
The basic n-tier deployment scenario involves the following tasks in the order
listed below.
236 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Basic N-tier scenario 13
The following steps require that you have already installed a version of
Microsoft Windows that meets the installation requirements for Oracle 10g
R2. Advanced administrative knowledge of Oracle and Microsoft Windows
products is assumed.
This database will be used to hold CMS data. Additional database will be
created for auditing or performance management if required.
Setting Example
Name of database server DBSERVER1_ora
Administrator account name system
Administrator account password password
Database character set encoding UTF-8
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 237
13 Deployment Scenarios
Basic N-tier scenario
238 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Basic N-tier scenario 13
5. Install the Oracle database drivers onto all CMS servers, and any clients
that need direct database access.
Your CMS server machines are now able to communicate with your newly
created Oracle 10g R2 databases.
6. 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
and Change permissions for the Everyone group.
Windows Server 2003 SP2 Enterprise Edition has to be installed and running
on the three machines running the server tier. You need administrative
privileges on the three machines that will host the BusinessObjects Enterprise
servers. Designate the machines SERVER1, SERVER2, and SERVER3.
Follow the instructions below to install all the servers on SERVER1.
1. Run setup.exe from the root directory of your product distribution.
The "Please Choose Setup Language" dialog is displayed.
2. Select your language for the installation setup from the pull-down list
provided and click OK.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 239
13 Deployment Scenarios
Basic N-tier scenario
3. Click Next.
The "License Agreement" screen is displayed.
4. Select I accept the License Agreement and click Next.
The "User Information" screen is displayed.
5. Enter the requested information for Full Name, Organization, and
Product Keycode. Click Next.
The "Chose Language Packs" screen is displayed.
6. Select any Language Packs you want to install. Click Next.
The "Install Type" screen is displayed
7. Select New and Use an existing database server in the "Install Type"
screen. Click Next.
The Server Components Configuration screen is displayed.
8. Enter password in both Password and Confirm password. Click Next..
The "Server Intelligence Agent"screen is displayed.
9. Enter SIA_1 in Node Name and click Next.
The "CMS Database Information" screen is displayed.
10. Select Oracle from the CMS database drop-down list.
The "SQL Server Logon" screen is displayed.
11. In the fields provided provide the following configuration for your Oracle
database:
Setting value
Server DBSERVER1_ora
Username system
Password password
240 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Basic N-tier scenario 13
The "Start Installation" screen is displayed.
15. Click Next to start the installation.
The installation process begins and is completed when "BusinessObjects
Enterprise XI 3.0 has been successfuly installed" is displayed.
16. Select Launch BusinessObjects Administration Console and click
Finish to exit.
A new browser window opens and within a few seconds you are prompted
to log into the Central Management Console (CMC).
17. Verify the connectivity between the BusinessObjects CMS and your MS
SQL Server server by logging onto the the CMC.
a. Type SERVER1 in System.
b. Type Administrator in User name .
c. Type password in Password.
d. Click Log On to access the CCM.
Accessing the CCM home page, verifies that the BusinessObjects
Enterprise CMS is communicating with the Microsoft SQL Server 2005
database server.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 241
13 Deployment Scenarios
Basic N-tier scenario
242 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Basic N-tier scenario 13
After implementing the selections, the "Select Features" screen should
appear as shown in the following image.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 243
13 Deployment Scenarios
Basic N-tier scenario
244 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Basic N-tier scenario 13
6. Select any Language Packs you want to install. Click Next.
The "Install Type" screen is displayed
7. Choose Custom or Expand install.
The "Select Features" screen is displayed.
8. Left-click on the icon beside Client Componentsand select Entire feature
will be unavailable.
The Client Components icon changes to .
9. Left-click on the icon beside Web Tier Components and select Entire
feature will be unavailable.
10. Left-click on the icon beside Server Components and select Entire
feature will be unavailable.
11. Expand Server Components. Left-click Dashboard and Analytics
Servers and select Entire feature will be installed on local hard drive.
12. Click Next.
The "CMS Clustering" screen is displayed.
13. Enter SERVER1 for CMS Host Name, 6400 for Existing CMS Port, and
password for CMS Administrator Password.
14. Click Next.
The "Server Intelligence Agent"screen is displayed.
15. Enter SIA_2 in the Node Name field and click Next.
16. Select Oracle from theCMS database drop-down list.
The "SQL Server Logon" screen is displayed.
17. In the fields provided provide the following configuration for your Oracle
database:
Setting value
Server
Username
Password
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 245
13 Deployment Scenarios
Basic N-tier scenario
246 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Basic N-tier scenario 13
1. Run setup.exe from the root directory of your product distribution.
The "Please Choose Setup Language" dialog is displayed.
2. Select your language for the installation setup from the pull-down list
provided and click OK.
The "Welcome to the BusinessObjects Enterprise XI 3.0 Installation
Wizard" is displayed.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 247
13 Deployment Scenarios
Basic N-tier scenario
248 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Basic N-tier scenario 13
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 249
13 Deployment Scenarios
Basic N-tier scenario
250 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Basic N-tier scenario 13
1. Log in to your Red Hat Linux server.
Note: As iptables is configured from the command-line, you need root
priviliges. 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.
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.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 251
13 Deployment Scenarios
Complex deployment scenario
System layers
Data Tier: contains databases used by the CMS and File Repository
servers.
Server Tier: all BusinessObjects Enterprise servers installed on two
machine running as a cluster.
Web Tier: two web application servers installed on separate machines
running as a cluster with fail- over support through load balancer.
Client Tier: a browser used to log into Central Management Console
(CMC).
252 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Complex deployment scenario 13
Configuration details
Installation platform for BusinessObjects Enterprise Windows Server 2003 SP2 Enterprise
Edition
Database for Central Management Server (CMS) Microsoft SQL Server 2005
Web application server WebLogic 10
Load balancer Cisco CSS 11500 series load bal-
ancer
Firewall Linux iptables running onRed Hat
Linux with two network interface cards
(NIC)
The complex deployment scenario involves the following tasks in the order
listed below.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 253
13 Deployment Scenarios
Complex deployment scenario
This scenario calls for Microsoft SQL Server 2005 running on a supported
Microsoft Windows operating system. In the examples below, this database
system is named DBSERVER1.
Install a version of Microsoft Windows with the appropriate service packs
and updates required by Microsoft SQL Server 2005. If your CMS and
database servers are installed on separate computers, ensure that you have
a working network connection between the machines.
1. Install Microsoft SQL Server 2005.
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 Example
Name of database server instance DBSERVER1_sql
Administrator account name sa
Administrator account password password
Database character set encoding UTF-8
254 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Complex deployment scenario 13
CMS database setting Example
CMS database name mycompany
Username for CMS database access mycompanyuser
Password for CMS database access mypassword
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 255
13 Deployment Scenarios
Complex deployment scenario
Your CMS server are now able to communicate with your newly created
Microsoft SQL Server 2005 databases.
Windows Server 2003 SP2 Enterprise Edition has to be installed and running.
You need administrative privileges on both machines that will host the
BusinessObjects Enterprise servers. Designate one machine SERVER1 and
the other SERVER2.
Follow the instructions below to install all the servers on SERVER1.
1. Run setup.exe from the root directory of your product distribution.
The "Please Choose Setup Language" dialog is displayed.
2. Select your language for the installation setup from the pull-down list
provided and click OK.
The "Welcome to the BusinessObjects Enterprise XI 3.0 Installation
Wizard" is displayed.
3. Click Next.
The "License Agreement" screen is displayed.
4. Select I accept the License Agreement and click Next.
The "User Information" screen is displayed.
256 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Complex deployment scenario 13
5. Enter the requested information forFull Name, Organization, and Product
Keycode. Click Next.
The "Chose Language Packs" screen is displayed.
6. Select any Language Packs you want to install. Click Next.
The "Install Type" screen is displayed
7. Select New and Use an existing database server in the "Install Type"
screen. Click Next.
The Server Components Configuration screen is displayed.
8. Enter password in both Password and Confirm password. Click Next..
The "Server Intelligence Agent"screen is displayed.
9. Enter SIA_1 in Node Name and click Next.
The "CMS Database Information" screen is displayed.
10. Select SQL Server (ODBC) from theCMS database drop-down list and
clickBrowse.
The "SQL Server Logon" screen is displayed.
11. Input your Microsoft SQL Server user credentials through the
preconfigured ODBC DSN.
a. Select my company database afrom the list under Data Source
Name.
b. Enter bobjuser and paword in the Login ID and Password fields.
c. Select BOE120 from the list under Database.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 257
13 Deployment Scenarios
Complex deployment scenario
12. Select Auditing Database and repeat steps 10-11 to setup configure
user credentials through the ODBC DSN for the auditing database. When
ODBC DSN is displayed in the "CMS Database Information" screen click
Next.
The "Select Web Application Server" screen is displayed.
13. Select the Instal Tomcat application server option and click Next.
The "Configure Tomcat" screen is displayed
14. Do not modify any of the values in the input fields and click Next.
The "Start Installation" screen is displayed.
15. Click Next to start the installation.
The installation process begins and is completed when "BusinessObjects
Enterprise XI 3.0 has been successfuly installed" is displayed.
16. Select Launch BusinessObjects Administration Console and click
Finish to exit.
A new browser window opens and within a few seconds you are prompted
to log into the Central Management Console (CMC).
258 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Complex deployment scenario 13
17. Verify the connectivity between the BusinessObjects CMS and your MS
SQL Server server by logging onto the the CMC.
a. Type SERVER1 in System.
b. Type Administrator in User name .
c. Type password in Password.
d. Click Log On to access the CCM.
Accessing the CCM home page, verifies that the BusinessObjects
Enterprise CMS is communicating with the Microsoft SQL Server 2005
database server.
3. Click Next.
The "License Agreement" screen is displayed.
4. Select I accept the License Agreement and click Next.
The "User Information" screen is displayed.
5. Enter the requested information forFull Name, Organization, and Product
Keycode. Click Next.
The "Chose Language Packs" screen is displayed.
6. Select any Language Packs you want to install. Click Next.
The "Install Type" screen is displayed
7. Choose Custom or Expand and click Next.
The "Select Features" screen is displayed.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 259
13 Deployment Scenarios
Complex deployment scenario
260 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Complex deployment scenario 13
10. Type SIA_2 in Node Name and 6415 in Port. Click Next.
The "CMS Database Information" screen is displayed.
11. Select SQL Server (ODBC) from theCMS database drop-down list and
clickBrowse.
The "SQL Server Logon" screen is displayed.
12. Input your Microsoft SQL Server user credentials through the
preconfigured ODBC DSN.
a. Select my company database afrom the list under Data Source
Name.
b. Enter bobjuser and paword in the Login ID and Password fields.
c. Select BOE120 from the list under Database.
13. Select Auditing Database and repeat steps 10-11 to setup configure
user credentials through the ODBC DSN for the auditing database. When
ODBC DSN is displayed in the "CMS Database Information" screen click
Next.
The "Start Installation" screen is displayed.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 261
13 Deployment Scenarios
Complex deployment scenario
To complete the server tier setup, you must cluster all the File Repository
servers.
1. Click Servers under the "Organize" column.
A list of all available servers is displayed in a new screen.
2. Double-click the SIA_1.InputFileRepository entry.
The SIA_1.InputFileRepository properties are displayed.
3. Replace the current value in the FileStore Directory field by typing
C:\Program Files\Business Objects\BusinessObjects Enterprise
12.0\FileRep\Input\ .
4. Click Save.
5. Repeat steps 2-3 for the servers listed in the following table and provide
the specific configuration for each server.
The server tier setup is now complete. You should now set up the web tier.
262 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Complex deployment scenario 13
To assign static port values to servers
You need to access the Central Management Console (CMC) on SERVER1.
A browser is therefore required. Use the machine you designated to run the
client tier. This machine needs to be able to communicate with the SERVER1
host. Open a browser and type in the following URL: http://SERV
ER1:8080/CmcApp/App/
Server name
SIA_1.CentralManagementServer
SIA_1.InputFileRepository
SAI_1.OutputFileRepository
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 263
13 Deployment Scenarios
Complex deployment scenario
You will need to pass the port numbers - 6402, 6404, and 6406 - when
configuring the firewall.
Before setting up the BusinessObjects Enterprise web tier you need to install
and prepare your web application servers. For this scenario you require two
machines running on Windows Server 2003 SP2 Enterprise Edition.
Designate one machine managedserver1 and the other managedserver2.
1. Install WebLogic 10 on both managedserver1 and managedserver2 .
For more information consult your WebLogic 10 documentation.
2. Configure the WebLogic 10 server names on each machine according to
the machine name.
The server on managedserver1 is called managedserver1, and the
server on managedserver2 is called managedserver2.
3. Create a cluster on the machine running managedserver1 with the
following settings
Setting Value
Cluster name cluster1
Administration server AdminServer
Managed servers
managedserver1
managedserver2
264 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Complex deployment scenario 13
Setting Value
Password for AdminServer password
Property Value
Name BusinessObjects
Document Builder Factory weblogic.apache.xerces.jaxp.Document
BuilderFactoryImpl
SAX Parser Factory weblogic.apache.xerces.jaxp.SAXParserFac
toryImpl
Transformer Factory weblogic.apache.xalan.processor.Trans
formerFactoryImpl
You can now proceed to install the web applications and setup the
BusinessObjects Enterprise web tier.
To install the web applications
Use the following steps to install the web applications to the
managedserver1 machine.
1. Run setup.exe from the root directory of your product distribution.
The "Please Choose Setup Language" dialog is displayed.
2. Select your language for the installation setup from the pull-down list
provided and click OK.
The "Welcome to the BusinessObjects Enterprise XI 3.0 Installation
Wizard" is displayed.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 265
13 Deployment Scenarios
Complex deployment scenario
266 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Complex deployment scenario 13
The "Select Web Application Server" screen is displayed.
11. Choose WebLogic 10 from list of supported web application servers.
12. Select I will manually deploy web components at a later time and click
Next.
The "Start Installation" screen is displayed.
13. Click Next to start the installation.
The installation process begins and is completed when "BusinessObjects
Enterprise XI 3.0 has been successfully installed" is displayed.
14. Click Finish to exit.
The WAR files used to deploy the web applications have to be prepared
before you can deploy them to your WebLogic 10 cluster.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 267
13 Deployment Scenarios
Complex deployment scenario
The WAR file have been prepared for deployment and are located in the
following directory:
C:\Program Files\Business
Objects\deployment\workdir\weblogic10\application\.
You can now deploy the WAR files using the WebLogic Administration
Console.
Once the WAR files have been prepared for deployment, you can use the
WebLogic 10 Administration console to deploy the web applications.
1. Click Deployments under "Domain Structure".
The "Summary of Deployments" is displayed on the right.
2. Click Install under the Control tab.
The "Install Application Assistant" is displayed.
268 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Complex deployment scenario 13
3. Click Lock & Edit under "Change Center".
4. In the Location area navigate to the following folder:
C:\Program Files\Business
Objects\deployment\workdir\weblogic10\application\.
This section illustrates the configuration of a Cisco CSS 11500 series load
balancer for use with two clustered WebLogic web application servers.
Advanced administrative knowledge of Cisco load balancer products is
required. The load balancer must be configured to use persistent (sticky)
sessions.
The load balancer provides content switching for incoming external client
requests to the web application servers in the web tier.
1. Create a VLAN circuit IP address. This will allow administrators to connect
to the load balancer remotely.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 269
13 Deployment Scenarios
Complex deployment scenario
2. Configure the IP address and the port number to be used for incoming
web requests. Web clients will sent web requests to load balancer at this
address and port number.
Below, a virtual, load balanced server named arrowpoint-weblogic at
10.50.96.79 port 7001 is created. To a web client, arrowpoint-weblogic
will appear to be a single WebLogic server.
CSS11503# configure
CSS11503(config)# owner trans
Create owner <trans>, [y/n]:y
CSS11503(config-owner[trans])# content arrowpoint-weblogic
Create content <arrowpoint-weblogic>, [y/n]:y
CSS11503(config-owner-content[trans-arrowpoint-weblogic])#
vip address 10.50.96.79
CSS11503(config-owner-content[trans-arrowpoint-weblogic])#
protocol tcp
CSS11503(config-owner-content[trans-arrowpoint-weblogic])#
port 7001
3. Create a service for each WebLogic server in the cluster, entering the
service name, IP address, and other connection information. The load
balancer will distribute requests received from web clients among these
servers.
Below, services are created for each WebLogic server:
LB01-ARROWPOINT at 10.50.96.76, and LB02-ARROWPOINT at
10.50.96.77.
CSS11503# configure
CSS11503(config)# service <LB01-ARROWPOINT>
Create service LB01-ARROWPOINT, [y/n]:y
CSS11503(config-service[LB01-ARROWPOINT])# ip address
10.50.96.76
CSS11503(config-service[LB01-ARROWPOINT])# string LB01
CSS11503(config-service[LB01-ARROWPOINT])# keepalive type
tcp
CSS11503(config-service[LB01-ARROWPOINT])# keepalive port
7001
CSS11503(config-service[LB01-ARROWPOINT])# active
270 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Complex deployment scenario 13
CSS11503(config-service[LB01-ARROWPOINT])# exit
CSS11503(config)# exit
CSS11503#
CSS11503# configure
CSS11503(config)# service <LB02-ARROWPOINT>
Create service LB02-ARROWPOINT, [y/n]:y
CSS11503(config-service[LB02-ARROWPOINT])# ip address
10.50.96.77
CSS11503(config-service[LB02-ARROWPOINT])# string LB02
CSS11503(config-service[LB02-ARROWPOINT])# keepalive type
tcp
CSS11503(config-service[LB02-ARROWPOINT])# keepalive port
7001
CSS11503(config-service[LB02-ARROWPOINT])# active
CSS11503(config-service[LB02-ARROWPOINT])# exit
CSS11503(config)# exit
CSS11503#
The load balancer is now configured to accept requests from web clients as
virtual server arrowpoint-weblogic at 10.50.96.79 port 7001. The
arrowpoint-weblogic virtual server distributes the requests between WebLogic
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 271
13 Deployment Scenarios
Complex deployment scenario
configure
service LB02-ARROWPOINT
ip address 10.50.96.77
string LB02
keepalive type tcp
keepalive port 7001
active
content arrowpoint-weblogic
vip address 10.50.96.79
advanced-balance arrowpoint-cookie
protocol tcp
port 7001
add service LB01-ARROWPOINT
add service LB02-ARROWPOINT
active
272 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Complex deployment scenario 13
vip address 10.50.96.79
active
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 273
13 Deployment Scenarios
Complex deployment scenario
Clients on an unsecured network outside the filewall can now access the
clustered WebLogic web application servers tier through the firewall on port
7001.
To set up the client tier in this scenario all you need is a machine running on
Windows Server 2003 SP2 Enterprise Edition and a web browser.
1. Open your web browser
2. Access the cluster by entering the following
URL:http://10.50.96.79:7001/InfoViewApp/
The "Log On to InfoView" page appears.
3. Type SERVER1 for System; Administrator for User name; and password
for Password.
274 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Deployment Scenarios
Complex deployment scenario 13
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 275
13 Deployment Scenarios
Complex deployment scenario
276 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Get More Help
A
A Get More Help
http://support.businessobjects.com/documentation/product_guides/
http://www.businessobjects.com/support/
For more information, contact your local sales office, or contact us at:
http://www.businessobjects.com/services/consulting/
http://www.businessobjects.com/services/training
278 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
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/.
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 279
A Get More Help
280 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Index
A client components 65, 136
client tools 26
Apache Tomcat 5.5 client tools installation 136
configuration details 58, 84, 96 procedure 137
sample ini file 145
scripted 144
B silent 144
basic web tier scenario clustering
configuration details 235 File Repository Servers 262
diagram 235 clusters
overview 235 WebLogic configuration 264
system layers 235 CMC
BusinessObjects Enterprise logging into 118
available diagnostic tests 120, 121 CMC logon issues 119
client 274 cms clustering 72
client components 65, 136 CMS database
Deployment diagnostic tool setting up on Windows 31
configuring 124 components, selecting individually on Windows
running from command line 122 64
running from Windows 121 configuring
documentation 10 Tomcat 57, 83, 95
network requirements 17 configuring existing databse 76
new features 12 custom and expand 24
non-system drive installation 20 custom and expand installation
silent 150 deselecting features 64
uninstalling 149 selecting features 64
BusinessObjects Enterprise client tools custom or expand installation
scripted 144 client components 71
silent installation 144 Windows 64
C D
checklist for installation 40 database 36
client configuring existing 76
set up 274 installing MySQL 30
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 281
Index
282 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Index
L O
language packs Oracle 31
definition 128 Oracle Application Server
English fallback 128 manual deployment 210
fallback to English 128 Oracle Application Server 10g R3
installation on Windows 129 configuration details 58, 84, 96
installing 130
locale 128
locating 130
P
manual deployment 129 preparing your database server 35
Product Locale 128 product registration 119
selecting locale 128
silent mode 131
specifying through installer 43 R
uninstalling 133
License Agrement 41 registration wizard 119
load balancer 269 remove installation 148
log file evoking maintenance mode 148
installation 155 repair installation 148
logging evoking maintenance mode 148
to the CMC 118
S
M SAP Application Server
maintenance mode manual deployment 212
modify 148 scripted installation
remove 148 common parameters 107
repair 148 scripted installation on Windows 102
server
choosing location 22
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 283
Index
server communication U
fixed host names 21
multiple NIC hosts 21 Unicode 31
set up 21 uninstalling 148, 149
servers silent 150
assigning static ports 225, 263
clustering File Repository servers 262
setup.exe parameters
W
-w 103 WAR file
additional parameters 103 verifying deployment 167, 202
side-by-side installation 29 war files
silent installation configuring 192
common parameters 107 deploying to remote server 192
silent installation on Windows 102 preparing for WebLogic 267
Software Inventory Tool WAR files
functionality 151 context roots 196
history view 153 deploying to WebLogic 10 268
installation files 151 deployment guidelines 197
introduction 150 web services 195
inventory.xml 151, 155 wdeploy
log.txt 151, 155 functionality 160
search 155 log file 166
SoftwareInventory.bat 151 options 166
SoftwareInventory.jar 151 prerequisites 159
user interface 152 Tomcat 179
viewing format with JBoss 190
ADAPT number 153 with Oracle 187
file 153 with SAP Application Server 184
install/patch name 153 with WebLogic 173
Sybase 31 with WebSphere 167
system requirements 16 web application deployment
on remote machines 192
T web application server
configuration details 58, 84, 96
Tomcat minimum required rights 18
configuring 57, 83, 95 Web application server
manual deployment 209 initial installation 37, 159
Tomcat clusters web services 195
manual deployment 209 web tier 25
troubleshooting CMC logon 119 web tier components
features 67, 90
specifying a CMS 92
284 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows
Index
BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows 285
Index
286 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows