You are on page 1of 246

BusinessObjects Enterprise XI 3.

0
Installation and Configuration Guide
for UNIX

BusinessObjects Enterprise XI 3.0

unix

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

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-06-02

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

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX 3

Contents

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

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

4 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

.................................86 Finishing a system installation .......63 To enter Server Intelligence Agent information..............96 To perform a web tier installation ......................................................................................62 To perform a new installation...........................................................................................................103 BusinessObjects Enterprise XI 3....................................................102 Finishing a system installation ......76 To perform a Custom or Expand installation...................................................................................................................................................................................................................................................................................................73 Chapter 5 Custom or Expand Installation 75 Performing a custom installation..........................................93 Chapter 6 Web Applications Installation 95 Performing web tier installations.................................67 To start the installation .......................................98 To configure your existing web application server..97 To select a web application server configuration option..................................96 To cluster web tier features to a CMS..................................................................62 To configure the new CMS ...............................Contents Chapter 4 New Installation 61 Performing a new installation........80 Installing only the Web Tier Components........................................................................................................79 To install only the server components.......................................98 To configure the Tomcat installation..............................................................0 Installation and Configuration Guide for UNIX 5 .................................99 To start the installation .................72 Finishing a system installation ..76 Features available in a custom installation..............................67 To select a web application server configuration option.....63 To specify a system database option............................

...............134 To install language packs ...117 Chapter 8 After Installing BusinessObjects Enterprise 125 Using ccm.106 Performing a scripted installation.................................................................128 Troubleshooting starting performance management...................................................................................................................................107 To run a scripted installation....135 To uninstall language packs ................................................................................................................................................................132 Selecting a language ................126 To manually start and enable servers.................132 English language fall-back .128 Chapter 9 Language Packs on UNIX 131 About language packs .................................................................................................................127 To set up performance management...............................................................................0 Installation and Configuration Guide for UNIX ......................108 Performing a silent installation..........................................132 Product locale changes ..............................................................................136 6 BusinessObjects Enterprise XI 3......................................134 Installing language packs across a BusinessObjects Enterprise deployment ........................................................................................................................................106 To create a response file...........................133 Locating language packs ...........................................................................107 Scripted installation parameters......................................................................126 Post install component deployment...........................................................133 Installing language packs on UNIX systems ..126 Setup for performance management .........................sh to start the BusinessObjects Enterprise servers................................................................................................................................................................132 Installing language and complex deployments ..Contents Chapter 7 Silent Installation 105 Overview.........................

.....151 Options for using wdeploy..............................................................................141 To add performance management.........................208 BusinessObjects Enterprise XI 3......................................................................................156 Deploying to web application servers with wdeploy....................................................193 Chapter 12 Deployment Scenarios 207 Overview of deployment scenarios.......149 Overview for using wdeploy..................185 WAR file context roots..................................................................149 Deploying with wdeploy...............................................150 How to use wdeploy.........................................141 The installation log file .........187 To manually deploy web applications.................................................................................................188 To prepare for manual deployment on a remote machine.........189 After deploying web applications...0 Installation and Configuration Guide for UNIX 7 ...................................................................................................................Contents Chapter 10 Maintaining your Installation 139 Uninstalling BusinessObjects Enterprise from UNIX...........................................................................................................................................149 Prerequisites for using wdeploy..........140 To uninstall BusinessObjects Enterprise.....................................148 Before you deploy web applications.....140 Adding performance management to your installation..........................................182 Manually deploying to a web application server.......................................................................................................................................155 After deploying web applications.................186 Guidelines for deploying WAR files.................................156 To deploy web applications on a remote machine .....................................................................185 BusinessObjects Enterprise WAR files...............146 Chapter 11 Post Installation Web Application Deployment 147 Overview of post install deployment............192 Deploying with the Administration console...................................................

....................................................................................................208 Desktop client to server overview .......................................................................................226 N-tier scenario overview...............226 Summary of required tasks.208 Summary of required tasks..............227 Deploying the basic N-tier scenario...............................................................................0 Installation and Configuration Guide for UNIX ......................209 Deploying the client to server scenario............................................................Contents Desktop client to server scenario....................227 Appendix A Get More Help 239 Index 243 8 BusinessObjects Enterprise XI 3..........................................................................................210 Basic N-tier scenario.

Getting Started 1 .

determining your organization's needs. and preparing for the installation. port usage. your database environment.0 Installation and Configuration Guide for UNIX .0 on UNIX. including detailed instructions for the different installation modes available. 10 BusinessObjects Enterprise XI 3. Language Pack installation and for modifying. This guide includes an overview of the architec- ture. and your web server software would be beneficial. or removing BusinessObjects Enterprise. There are UNIX and Windows versions of this guide available.0 on UNIX operating systems. BusinessObjects Enterprise In. In addition this documentation provides instructions for Standalone Client Tools installation. Who should read this documentation This documentation is intended for the system administrator or IT professional who needs to install BusinessObjects Enterprise XI 3.Leads you through the steps required to stallation and Configuration run the setup program and complete your Guide installation of BusinessObjects Enterprise. Guide Description BusinessObjects Enterprise This guide covers the key concepts you Deployment Planning Guide should consider before you begin deploy- ing BusinessObjects Enterprise. BusinessObjects Enterprise guides The following table provides a list of BusinessObjects Enterprise guides and their contents. Familiarity with your overall network environment.1 Getting Started About this documentation About this documentation This documentation provides you with information and procedures for installing BusinessObjects Enterprise XI 3. tips for assessing your existing envi- ronment.

publishing web in- telligence documents. The server administration topics includes server con- figuration. and Voyager workspaces. Web Intelli- gence. managing users. objects.Details content migration from legacy gration Guide Business Objects software. The content administration topics include working with the CMC. BusinessObjects Enterprise In. and measuring system performance.com/documentation/product_guides/de fault. BusinessObjects Enterprise Information for upgrades from BusinessOb- Upgrade Guide jects Enterprise XI to BusinessObjects Enterprise XI 3. managing authentication. such as Clas- sic or Enterprise 5 or 6. con- figuring firewalls. publishing desktop intelligence documents. working with publications. discussions.Provides an overview of InfoView and foView User's Guide working with Crystal Reports. and publishing security.0. Getting Started BusinessObjects Enterprise guides 1 Guide Description BusinessObjects Enterprise Provides content for server administration Administrator's Guide and content administration. configuring rights and access levels. For a complete list of all of our product documentation please visit our support site: http://support. pub- lishing Crystal reports. BusinessObjects Enterprise Provides an overview of the publishing Publisher's Guide process. encyclopedia.0 Installation and Configuration Guide for UNIX 11 .businessobjects.0.asp BusinessObjects Enterprise XI 3. BusinessObjects Enterprise Mi. and working with Busi- ness Objects applications and objects. to BusinessOb- jects Enterprise XI 3.

or integrating critical information into corporate portals. Scripted Installation You can store all of your installation settings in a log file. scalable.1 Getting Started What is BusinessObjects Enterprise? What is BusinessObjects Enterprise? BusinessObjects Enterprise XI 3. which you can use to run silent or scripted installations. extranet. providing customers with personalized service offerings. As an integrated suite for reporting. This feature is particularly useful for automating custom installations. Whether it is used for distributing weekly sales reports.0 Installation and Configuration Guide is the first release to include information on the following features: Feature Description Language Packs in.Web applications can now be deployed directly using the cations BusinessObjects Enterprise installer. Internet or corporate portal. BusinessObjects Enterprise delivers tangible benefits that extend across and beyond the organization. Deploying web appli. or after installation using either the wdeploy tool or the web application serv- er's administration console. Web-tier installation Web applications can be installed and deployed to sup- ported web application servers using a dedicated installa- tion method. and information delivery. and reliable solution for delivering powerful. What's new in the BusinessObjects Enterprise Installation and Configuration guide? BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX . analysis. BusinessObjects Enterprise provides a solution for increasing end-user productivity and reducing administrative efforts. interactive reports to end users via any web application—intranet. Procedures for several deploy- ment scenarios are considered and thoroughly document- ed in this guide.0 is a flexible. 12 BusinessObjects Enterprise XI 3.New languages can be added to your installation using stallation the standalone Language Pack installer.

0 Installation and Configuration Guide for UNIX 13 . The website is refreshed with up-to-date content as it becomes available between releases.busi nessobjects. Go to http://support.com/documentation/ BusinessObjects Enterprise XI 3. Getting Started What's new in the BusinessObjects Enterprise Installation and Configuration guide? 1 All product documentation (including error message explanations) is available in all supported languages in an HTML-based documentation library. This system enables full-text search and other customizable features to make it easy to find the information you need. You can also access or download the PDF guides from the same website.

0 Installation and Configuration Guide for UNIX .1 Getting Started What's new in the BusinessObjects Enterprise Installation and Configuration guide? 14 BusinessObjects Enterprise XI 3.

Preparing to Install BusinessObjects Enterprise 2 .

and operating systems. • Decide which BusinessObjects Enterprise XI 3.com/documentation/sup ported_platforms/. • Review your physical system to ensure that it meets the basic requirements for a BusinessObjects Enterprise installation. • Decide which installation method to use. and the installation methods that you can use when you install BusinessObjects Enterprise.0 provides an open and flexible architecture that supports a multitude of deployment and configuration scenarios.2 Preparing to Install BusinessObjects Enterprise Installation overview Installation overview BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX .0 deployment can communicate properly with one another. At the start of the next chapter. Before you install BusinessObjects Enterprise you should: • Consult the BusinessObjects Enterprise XI 3. • Ensure that all machines that will be part of your BusinessObjects Enterprise XI 3. the following components must be preinstalled and configured correctly before you can install BusinessObjects Enterprise XI 3. it is also strongly recommended that you consult the BusinessObjects Enterprise XI 3.0 Deployment Planning Guide .0 components to install and which of your own components to integrate. web browsers. You can use this checklist to help ensure you are prepared before you begin your installation.businessobjects. you will find an installation checklist. For additional important information that may pertain to your deployment. This file includes specific version and patch-level requirements for web application servers. The following sections list the core software requirements. • Consider how you should prepare your infrastructure and set up your environment including server locations. Generally. consult the Platforms Availability Report (PAR) file available on the Business Objects support site http://support.0 Deployment and Planning Guide.0: 16 BusinessObjects Enterprise XI 3. the choices available to you within the core requirements. System requirements For a detailed list of supported environments and hardware requirements. • Determine where the components should be installed.

UNIX permissions To perform either a user or system installation on UNIX. the user account under which the install is run must have read. This script. write.sh. Network Access to all machines via TCP/IP . and execute permissions to the directory where BusinessObjects Enterprise will be installed. you will be unsuccessful However. you do require root authority to run the system-level initialization script. write. The following table summarizes all the required permissions for installing BusinessObjects Enterprise. or a slash.0 Installation and Configuration Guide for UNIX 17 . Note: BusinessObjects Enterprise requires a database to store information about the system and its users. if you run a system installation. ensure your machine name does not include any of the following characters: an underscore. and stops the servers when a machine is shut down. This script creates entries into the run control scripts for the operating system that start up the BusinessObjects Enterprise servers when the UNIX server is brought up. Root access if performing a system installation. which is called setupinit. Caution: If you attempt an installation with root privileges.all specified ports must be available BusinessObjects Enterprise XI 3. is run after the installation completes. Tip: If you are installing on VMWare. Preparing to Install BusinessObjects Enterprise Installation overview 2 • Web application server (unless you want to install Tomcat as part of your installation of BusinessObjects Enterprise) • Database software that is compatible with the CMS system and the Audit databases (unless you want to install MySQL as part of your installation of BusinessObjects Enterprise). and execute permissions to the directory where System BusinessObjects Enterprise will be installed . Root privileges are not required to perform either a user or system install of BusinessObjects Enterprise. Category Required permissions Operating Read. a period.

and edit table rows Minimum rights for deploying web applications Tip: We recommend that you use the same user account for installing BusinessObjects Enterprise and your web application server. write and execute files in $as_dir/$as_sid/$as_instance/j2ee/deploy ing 18 BusinessObjects Enterprise XI 3. you must ensure that the BusinessObjects Enterprise user account has the privileges listed in the following table. write and execute files in $as_dir/server/$as_instance/deploy Oracle • rights to read and execute files in $as_dir/j2ee/home • rights to read and execute files in $as_dir/opmn/lib • rights to read. plus rights to read.sar/jsf- libs directory • rights to read. write and execute files in $as_dir/server/$as_instance/lib • rights to read. Web application server Minimum required permissions JBoss • rights to read.0 Installation and Configuration Guide for UNIX . To deploy web applications using a user account different from the one used to install the web application server. write and execute files in $as_dir/bin • rights to remove the $as_dir/server/${as_in stance}/deploy/jbossweb-tomcat55. write and execute files in $as_dir/opmn/conf SAP Web Application Server • rights to read and execute files in $as_dir/$as_sid/$as_instance/j2ee • rights to read.2 Preparing to Install BusinessObjects Enterprise Installation overview Category Required permissions Database Rights to add and drop tables to/from database. write.

and execute files in $as_dir/properties • Right to read. Preparing to Install BusinessObjects Enterprise Installation overview 2 Web application server Minimum required permissions Tomcat • rights to read. write and execute files under $as_dir/conf and its subdirectories WebLogic • right to read files under $WL_HOME/server/lib • right to read and write files under $as_dir/bin/ • right to read and execute files under $WL_HOME/ jdk150_06/ (or your WebLogic JDK directory) • right to read files under $WL_HOME /wlserv- er_10.which is the domain root WebSphere • Right to read and execute $as_dir/bin/wsadmin. write. write and execute files under $ad_sir/webapps and its subdirectories • rights to read. write. write and execute files in $as_dir/bin • rights to read. the right to execute is also required on the parent directory. and execute files in $as_dir/profiles Note: In addition to the right to execute files or folders mentioned in the above table.sh • Right to read and execute $as_dir/bin/GenPlug inCfg.jacl • Right to read $as_dir/bin/LTPA_LDAPSecuri tyProcs.0 Installation and Configuration Guide for UNIX 19 .0/common/bin • right to read and execute files under $WL_HOME /modules/ Note: WL_HOME is the weblogic installation dir and not as_dir -.sh • Right to read $as_dir/bin/securityProcs.jacl • Right to read and execute files in$as_dir/plugins • Right to read and execute files in $as_dir/java • Right to read and execute files in $as_dir/deploy tool • Right to read. write and execute files in $as_dir/shared/lib • rights to read. BusinessObjects Enterprise XI 3.

login file). Checking for required commands and utilities In order for the install setup program to run correctly.businessobjects.com/documentation/supported_plat forms/. Tip: Type locale to check that all of the related locale environment variables (such as LC_MONETARY.2 Preparing to Install BusinessObjects Enterprise Installation overview Setting up your UNIX system BusinessObjects Enterprise integrates with your existing database and web server software components. LC_NUMERIC. set these environment variables in the . Setting the locale Before you install BusinessObjects Enterprise. to ensure that your operating system uses the correct locale whenever BusinessObjects Enterprise runs.) were properly set by LC_ALL. However. etc. so the installation script needs to collect certain information about your current system. set your operating system to use one of the locales that BusinessObjects Enterprise supports for your version of UNIX. the following commands and utilities must be installed on your UNIX system: 20 BusinessObjects Enterprise XI 3. Note: You should also ensure that the character set translation on your terminal is set to UTF-8. (For example. if you are using a C shell. set the LC_ALL and LANG environment variables to your preferred locale in your login environment. the following sections detail the key tasks that you must perform prior to installing BusinessObjects Enterprise. For a detailed list of supported UNIX environments see the Product Availability Report PDF available from the following Business Objects support site:http://support. See the section on International Deployments in the BusinessObjects Enterprise Administrator's Guide for information on deploying BusinessObjects Enterprise for a multilingual. Because UNIX systems can vary significantly from site to site. you can select your locale directly from the logon screen when you log on with the account from which you will install BusinessObjects Enterprise. world-wide audience. If you are working through the console of a UNIX machine.0 Installation and Configuration Guide for UNIX .

a home directory. Neither the installation scripts nor BusinessObjects Enterprise itself needs to run as root. However. these commands and utilities must be accessible in the PATH environment variable of the user account that you use when installing BusinessObjects Enterprise.0 Installation and Configuration Guide for UNIX 21 . see Creating an account. if for any reason one of them is not available on your system. It is recommended that you obtain any required files from your UNIX vendor. the account itself does not require root privileges. and a login environment Create a specific user account and group under which the BusinessObjects Enterprise background processes can run. download and install a version appropriate to your UNIX system. Creating an account. BusinessObjects Enterprise XI 3. and a login environment on page 21. Preparing to Install BusinessObjects Enterprise Installation overview 2 /bin/sh pwd read touch uname expr hostname sed awk chown grep tail tar id dirname gzip stty ulimit which These relatively standard commands and utilities should be available on most UNIX distributions. You will log on as this user in order to perform the remainder of the installation procedures. For details. Additionally. Although you will require root privileges to set up this account. a home directory. Use your usual administrative procedures to perform these recommended tasks.

write. Create a new group or use an existing group. that is. You must have root privileges to set or modify this information on your system. the installation will use your current directory as its base directory for the install. You can override this default. and execute permissions on the new installation directory. In particular. 22 BusinessObjects Enterprise XI 3.2 Preparing to Install BusinessObjects Enterprise Installation overview To set up an account for installing BusinessObjects Enterprise 1. consult your UNIX system documentation. Assign a secure password to the new user account. with the directory of your choice at install time. Create the directory where you want to install BusinessObjects Enterprise. You will see the directory that you specify for the installation directory referred to as INSTALLDIR throughout this document. Create a new user account. • The user's login environment must set up the database environment such that the install setup program can access your database client software.sh. If you are unfamiliar with these procedures. 3. and create or modify the appropriate login script(s) for the user account. make sure that the login script(s) set up a default login environment that meets these requirements: • All of the commands and utilities required by the install setup program must be accessible in the PATH environment variable. Related Topics • Checking for required commands and utilities on page 20 • Providing and verifying connectivity to the CMS database on page 43 • Setting the locale on page 20 Meeting the host name and network requirements Your UNIX server must have a fixed host name before you run the installation script. Assign the new user a default login shell. and set this user's primary group to the new group. 4. • The user's login environment must set up a default locale that is supported by your UNIX system and BusinessObjects Enterprise. 2. the directory where you run install.0 Installation and Configuration Guide for UNIX . By default. Ensure that the account you created has read.

Note: To perform a system installation. See the "Working with Firewalls" section of the BusinessObjects Enterprise Deployment and Configuration Guide. This script creates entries into the run control scripts for the operating system that start up the BusinessObjects Enterprise servers when the UNIX server is brought up and stops the BusinessObjects Enterprise servers when a machine is shut down. all the required components are installed. Note: If you are installing BusinessObjects Enterprise in a firewall environment.0 Installation and Configuration Guide for UNIX 23 . to run the system-level initiation script root-level authority is required. You can also choose to install a database server (MySQL) and a Web application server (Apache Tomcat 5. • When you choose a user installation. on UNIX.5) during your installation of BusinessObjects Enterprise. Difference between user and system installation When you perform a new installation. Preparing to Install BusinessObjects Enterprise Installation overview 2 When installing BusinessObjects Enterprise on multiple machines. You must ensure that all BusinessObjects Enterprise machines can communicate properly with one another: • Each BusinessObjects Enterprise machine must be able to communicate over TCP/IP with the machine that runs your Central Management BusinessObjects Enterprise XI 3. However. you do not require root-level authority. • When you choose a system installation. Setting up server communication BusinessObjects Enterprise requires a database server and web application server software to be installed and configured if you want to use an existing database or web application server. you will need additional configuration details. all the required components are installed. ensure that each target machine is able to communicate over TCP/IP with the machine that is running as your Central Management Server (CMS). In addition. the installation creates a system-level initiation script. you can choose between a user and a system installation.

you may have to reconfigure your servers after installation. 24 BusinessObjects Enterprise XI 3. and servers. • Ensure that your database client and server are set up to use Unicode character encoding(such as UTF-8). For more information on how to reconfigure to bind to routable NICs see the “Managing and Configuring Servers” chapter in the BusinessObjects Enterprise Administrator’s Guide. This communication is enabled by the BusinessObjects Enterprise Software Development Kit (SDK). The CMS is responsible for maintaining a database of information about your BusinessObjects Enterprise system. For more information about the CMS. The data stored by the CMS includes information about users and groups. consult your UNIX system documentation. the CMS may automatically bind to a primary NIC. • If you are installing BusinessObjects Enterprise in a firewall environment.2 Preparing to Install BusinessObjects Enterprise Installation overview Server(CMS). you do not require root privileges to perform a user installation of BusinessObjects Enterprise . or a slash. which other components can access as required.0 Installation and Configuration Guide for UNIX . you will need to install it. you will need additional configuration details. security levels. However. you could make the primary NIC routable before installing BusinessObjects Enterprise. Consult your database documentation to determine the settings required for a Unicode configuration. see the “Managing and Configuring Servers” chapter in the BusinessObjects Enterprise Administrator’s Guide. • If the host machine has more than one network interface card (NIC). Note: Please ensure that the host name you use does not include any of the following characters: an underscore. See the “Working with Firewalls” section of the BusinessObjects Enterprise Administrator’s Guide. the web application server must be able to communicate with all BusinessObjects Enterprise machines. Alternatively. which is installed as part of the Web Tier Components. a period. You must have root privileges to set or modify a fixed host name on your system. If the primary NIC is not routable. • UNIX servers that run BusinessObjects Enterprise must have a fixed host name. BusinessObjects Enterprise content. 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. • If you connect BusinessObjects Enterprise to a web application server. If you are unfamiliar with these procedures.

Your Crystal Reports Page Server. ensure each machine that runs a CMS process experiences the same latency to the system database. Job Servers. Desktop Intelligence Report Server. The CMS can also maintain a separate audit database of information about user actions. Consult the “Managing and Configuring Servers” section of the BusinessObjects Enterprise Administrator's Guide for information on other factors that you may want to consider in planning your BusinessObjects Enterprise installation. Preparing to Install BusinessObjects Enterprise Installation Scenarios 2 Choosing a server location When planning your BusinessObjects Enterprise installation. If your BusinessObjects Enterprise installation is distributed over a wide geographic region. If you are deploying more than one CMS. and servers in the CMS database. on the same subnet). place your processing servers close to your database servers (ideally. use server groups to create groups of nearby servers to process reports. place your CMS on the same LAN as the database servers that host your CMS database and the BusinessObjects Enterprise audit database. consider which of these is your intended scenario: • New installation • Custom installation • Web Tier installation • Client Tools installation • Silent or Scripted installation • Side-by-Side installation BusinessObjects Enterprise XI 3. published objects.0. To optimize CMS performance. The Central Management Server (CMS) stores data about users and groups. and Report Application Server communicate frequently with the database servers containing the data in your published reports. Connection Server. The CMS can be clustered. To optimize data retrieval and minimize network traffic. Installation Scenarios Before you install BusinessObjects Enterprise XI 3. Web Intelligence Report Server.0 Installation and Configuration Guide for UNIX 25 . you should also consider where you will place your deployment’s servers. security levels.

26 BusinessObjects Enterprise XI 3. If you perform a custom install without being familiar with specific BusinessObjects Enterprise components and their roles. New installation Performing a new installation is the simplest way to deploy BusinessObjects Enterprise because all the required and optional components are installed by default onto one machine.0 components are installed. It may be that you have an existing web application server that resides on a different machine than the one that has your BusinessObjects Enterprise core components. You may want to perform a Custom or Expand installation if you plan to use BusinessObjects Enterprise in a distributed environment. It is recommended that you run this type of installation only when you are familiar with specific BusinessObjects Enterprise components and their roles. or install only a limited set of components. you may inadvertently fail to install a required component. Alternately.0 Installation and Configuration Guide for UNIX . you may want to perform a Custom or Expand installation when you want to exclude some components installed by default with the new installation. These components include the following: • Web Tier Components • Server Components • Database Access • Export Support • Samples • Help Files Custom or Expand installation The Custom or Expand installation allows you to specify which BusinessObjects Enterprise XI 3.2 Preparing to Install BusinessObjects Enterprise Installation Scenarios • Distributed Deployments For an installation upgrade see the BusinessObjects Enterprise Upgrade Guide. You may want to choose a this installation method if: • You are already familiar with the BusinessObjects Enterprise installation program.

Preparing to Install BusinessObjects Enterprise Installation Scenarios 2 • Your deployment of BusinessObjects Enterprise servers will be distributed over multiple computers. InfoView. Web tier installation The Web Tier installation provides you with all of the components that are used by the web application server to run BusinessObjects web applications. • You have an existing web application server and would like to dedicate to work with BusinessObjects Enterprise web applications.0 Installation and Configuration Guide for UNIX 27 . • You want to cluster either BusinessObjects Enterprises servers or Server Intelligence Agent Nodes. • You completed your initial installation of BusinessObjects Enterprise.which includes Business Process BI Service. BusinessObjects Enterprise XI 3. • You have customized some of your own applications and you don't want the installation to overwrite them. • You know exactly what components you require. • Tomcat . • You have disk space constraints. Perhaps your web application server will be on one machine but other BusinessObjects Enterprise components are elsewhere.0 applications including Central Management Console. • BusinessObjects Enterprise Web Services .a web application server you can install You may want to choose a web tier installation if: • If you want to install the web applications separately from the server components. Performance Management.used to run BusinessObjects XI 3. and Voyager. These components include the following: • BI Platform Web Components . and you want to configure an additional web application server on a separate machine. • You are already familiar with the BusinessObjects Enterprise installation program.

However. or migrating system data.which include: • BusinessObjects Enterprise Java SDK • BusinessObjects Enterprise Web Services SDK • Translation Manager Note: The client applications can only be installed on Windows. Desktop Intelligence does require that a key entered in the CMC after the install completes to enable the content type. Although most end users interact with BusinessObjects Enterprise over the web. These client tools are not needed by users who access InfoView or the Central Management Console (CMC) administrative web applications.0 Installation and Configuration Guide for UNIX . developing applications. Note: The client installation does not generally require a product activation keycode. Some of these tools are used for migration of existing documents from earlier product versions or creating new documents. Install these applications for particular users who are responsible for managing BusinessObjects Enterprise content. Silent installation You can run a silent installation to install BusinessObjects Enterprise from the command line using a response file containing installation setup 28 BusinessObjects Enterprise XI 3.2 Preparing to Install BusinessObjects Enterprise Installation Scenarios Client Tools installation This scenario allows you to perform an installation that installs only the Client Tools on the local machine. the Client Tools are also provided as stand-alone Windows applications: • Desktop Intelligence • Web Intelligence Rich Client • Data Source Migration Wizard • Business View Manager • Report Conversion Tool • Import Wizard • Publishing Wizard • Query as a Web Service • Universe Designer • Developer Components .

0 in a separate directory from your existing BusinessObjects Enterprise installation. If your install source files are on multiple CDs. This method is particularly useful when you need to perform multiple installations or you do not want to interrupt people who are working on machines in your system.0 Setup program. This is called a side-by-side installation and both versions may run simultaneously.0 Installation and Configuration Guide for UNIX 29 . BusinessObjects Enterprise XI 3. You may want to choose a silent installation if: • You are already familiar with the BusinessObjects Enterprise installation program. you must first copy the contents from all the CDs to a central location. Side-by-side installation If you have an existing installation of BusinessObjects Enterprise XI. • You need an automated method for performing similar installations on several machines. Note: BusinessObjects Enterprise does not support silent installations when the install contents are on multiple CDs. if your organization uses scripts to install software on machines. When you perform a side-by-side installation you need to ensure that your BusinessObjects Enterprise XI 3. You should install BusinessObjects Enterprise XI 3. You cannot add servers to a CMS cluster used by a different version of BusinessObjects Enterprise. Custom or Expand. and XI 3.0 installation. • You do not want to run the BusinessObjects Enterprise XI 3. XI Release 2.0 installation will not clash with your preexisting BusinessObjects Enterprise version by : • Specifying a unique CMS cluster name for the BusinessObjects Enterprise XI 3. and then run the silent install from the location that contains the content from all the CDs. or Web Application installation of BusinessObjects Enterprise XI 3. you can add the silent BusinessObjects Enterprise installation command to those scripts. For example. such as a hard-drive. You can also incorporate the silent installation command into your own build scripts.0 on the same machine.0 you may perform a New. Preparing to Install BusinessObjects Enterprise Installation Scenarios 2 parameters.

refer to the “Databases in BusinessObjects Enterprise” section in the BusinessObjects Enterprise Deployment Planning Guide. Using a supported database server The CMS supports a number of third-party database servers. If you do not have a database installed on your machine you choose to install and configure MySQL as your CMS database through the BusinessObjects Enterprise installation setup program. The one requirement that applies. is that your relational database be set up to use Unicode character encoding (such as UTF-8).0 installation.2 Preparing to Install BusinessObjects Enterprise CMS System and Auditing Database Requirements Note: You cannot add servers to a CMS cluster used by a different version of BusinessObjects Enterprise. For more information on database requirements. 30 BusinessObjects Enterprise XI 3. consider the following sections that detail what settings are required when the relational database is created and what settings you should test before beginning your BusinessObjects Enterprise install. regardless of your database type.0 Installation and Configuration Guide for UNIX . • Specifying unique port numbers for the BusinessObjects Enterprise XI 3. CMS System and Auditing Database Requirements Database requirements Before you create the relational database that you want to integrate with BusinessObjects Enterprise. so you can connect BusinessObjects Enterprise to your existing database infrastructure. For a detailed list of supported database servers see the Product Availability Report PDF available from the Business Objects support site.

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

the installation program creates the CMS database using your existing database. Setting up an empty database for the CMS BusinessObjects Enterprise requires a relational database to store information about the system and its users. (dot operator) Bourne shell (sh) no yes Korn shell (ksh) no yes Bourne Again Shell yes yes (bash) C shell (csh) yes no Turbo C shell (tcsh) yes no Using MySQL MySQL database server is an open-source database that provides local data storage. you specify what database server you will use and enter the required parameters for authentication. During the installation of BusinessObjects Enterprise. The setup program can configure MySQL along with your BusinessObjects Enterprise components.2 Preparing to Install BusinessObjects Enterprise CMS System and Auditing Database Requirements Shell name source . or you can use an existing database. If you want to create a new MySQL database during the installation. You can install a MySQL database during the installation. this section does not apply to you.0 Installation and Configuration Guide for UNIX . 32 BusinessObjects Enterprise XI 3. If you already have MySQL installed.

txt file included with your product distribution for a complete list of supported database software and version requirements. and after you have completed your installation. consult these section for details on database setup requirements before you create your database: • DB2 database setup requirements on page 38 • Oracle database setup requirements on page 40 • Sybase database setup requirements on page 42 • MySQL database setup requirements on page 38 If you plan on integrating your own database with BusinessObjects Enterprise. If you plan on integrating your own database with BusinessObjects Enterprise. you will to prepare it before your installation. and create a new user account named bobje. you will destroy any existing data. BusinessObjects Enterprise XI 3. Tip: You may want to name the new database bobjecms. however. If you use a database from a previous release. Note: If you have a previous release of BusinessObjects Enterprise you cannot use your database from a previous release for BusinessObjects Enterprise XI Release 2. You must create a new database for this release. Create a new database instead.0 Installation and Configuration Guide for UNIX 33 . Preparing to Install BusinessObjects Enterprise CMS System and Auditing Database Requirements 2 If you want to use an existing database. you or your database administrator must create a new database on your database server before you install BusinessObjects Enterprise. this naming convention is not required. We strongly recommend that this database be used only for BusinessObjects Enterprise. and not contain other tables. you can migrate your old content to the new current version's database. The following database servers are supported on UNIX: • Oracle • DB2 • Sybase • MySQL Note: See the Platforms. rather than installing MySQL with your installation. Here is a summary of the steps that will be part of your preparation: • Creating a new database.

you need to set up a database account. • Recording the name of the database. and the password when you run the BusinessObjects Enterprise installation script. • Ensuring that this new account has permission to create. You must choose to reinitialize the database to proceed with the install. For database servers such as Oracle and Sybase. In either case. the user account. modify. If you plan to 34 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX . during installation you need to configure the server to use Unicode encoding for the character data types. During the installation process. Consult your database documentation to determine the settings required for a Unicode configuration. choosing this option causes the install script to create BusinessObjects Enterprise tables in the default schema of the user whose name you provided during the install. (In Oracle. you can create the CMS database with Unicode settings on your existing database server. and delete tables and create procedures so that BusinessObjects Enterprise can modify the database as required. Setting up a database account for BusinessObjects Enterprise To administer the CMS database. If you choose to install MySQL when you install BusinessObjects Enterprise.) Note: During a reinstall of BusinessObjects Enterprise. such as DB2. destroying any existing data. reinitializing the database does not affect any other tables in that database or schema. • Ensure that your database server is set up to use Unicode character encoding (such as UTF-8). • Consult your database server documentation and/or your database administrator if you are unsure of the procedure for creating a new database. Choosing to do so causes the install script to create new tables in the database to store BusinessObjects Enterprise data. you will be prompted during installation to set up this account. the install script asks you if you want to reinitialize the database.2 Preparing to Install BusinessObjects Enterprise CMS System and Auditing Database Requirements • Creating a new user account and password for this database that will be used by BusinessObjects Enterprise. choosing this option causes the install script to reinitialize the tables containing BusinessObjects Enterprise data. For other databases.

2. Preparing to Install BusinessObjects Enterprise Preparing your CMS System Database server 2 use your own database. BusinessObjects Enterprise XI 3. Create or select a user account that provides BusinessObjects Enterprise with the appropriate privileges to your database server. Verify that you can log on to your database and carry out administrative tasks using the account you set up for use by the CMS. Related Topics • System requirements on page 16 Preparing your CMS System Database server Prerequisites for database preparation Before you prepare your database. Related Topics • MySQL database setup requirements on page 38 • DB2 database setup requirements on page 38 • Sybase database setup requirements on page 42 • Oracle database setup requirements on page 40 Preparing your existing database server After you have created your database. To set up a database account for BusinessObjects Enterprise 1. you or your database administrator need to prepare your own database server so the CMS can connect to it.0 Installation and Configuration Guide for UNIX 35 . please complete these steps before you install BusinessObjects Enterprise. you must have already created it. and before you install BusinessObjects Enterprise. Ensure you have created the database with the required settings for your existing database server.

2. Database type Information required at install time MySQL Port number Sybase Sybase Server Name DB2 DB2 database alias Oracle tnsnames connect identifier Note: On UNIX deployments the Sybase Server Name is a combination of the server name and the port number which is set by your database administrator in the interfaces file. Ensure that the new account has permission to create. modify. you will be asked for details about your database. If you specify that you will you use an existing database. Create a new. This table summarizes the information you will be required to enter to identify your database during the installation if your are using SQL Server. Create a new user and assign it a secure password. empty relational database on your database server. The database the installation connects to is the default database for the user profile. This default database is to is set by the DBA in the profile of the account from which you will install and run BusinessObjects Enterprise. 36 BusinessObjects Enterprise XI 3. 3.2 Preparing to Install BusinessObjects Enterprise Preparing your CMS System Database server During your installation. delete tables and create procedures so that BusinessObjects Enterprise can modify the database as required. Oracle. you will be asked whether you want to install MySQL or use an existing database. you will not be asked to provide your database name unless you are using an existing version of MySQL. To prepare your database 1.0 Installation and Configuration Guide for UNIX . Sybase. or DB2. Although you are required to provide the details about your database during the installation.

BusinessObjects Enterprise XI 3. Tip: You may want to record the required details on the Installation Checklist at the end of this chapter so the information is available when you install. or DB2.0 Installation and Configuration Guide for UNIX 37 . If you are using MySQL. For information on how to create a new relational database. For information on how to migrate your initial CMS database to another supported database server later. Oracle. ensure the following are set up before you begin your installation: Database type Ensure this has been configured MySQL MySQL port number Sybase Sybase Server Name Oracle tnsnames connect identifier DB2 DB2 database alias During the install. or your DB2 database alias. 4. you will need to have permissions to perform the necessary operations. consult your database server documentation or your database administrator. • The user account and the password authorized to the database. your Sybase Server Name. Sybase. Record the these details as they will be required during your install: • The name of your database. see the BusinessObjects Enterprise Deployment Planning Guide. you will be asked for information regarding your database. 5. your Oracle tnsnames connect identifier. Preparing to Install BusinessObjects Enterprise Preparing your CMS System Database server 2 Note: If you are not the owner of the database.

you will need to prepare the server for the BusinessObjects Enterprise installation. Consult the documentation for MySQL for information on how to configure the MySQL. there are specific settings you need to select when the relational database is created. If you choose install and configure MySQL as part of your BusinessObjects Enterprise installation setup. you will not have to provide any special configuration information.0 Installation and Configuration Guide for UNIX . When you create the relational database you will use with BusinessObjects Enterprise: • Ensure the CMS database is not partitioned. It is not sufficient to modify these settings after the relational database has been created. DB2 database setup requirements If you are using a DB2 relational database with your BusinessObjects Enterprise deployment.0: MYSQL_HOME If this variable is not set up. the installation will not proceed and you will receive an error message. By default. and you have specified that you are using an existing MySQL database. other than the setting of UTF-8. If you want to use an existing MySQL database server. 38 BusinessObjects Enterprise XI 3. a MySQL database will be created with the default settings for the CMS database and the Audit database.2 Preparing to Install BusinessObjects Enterprise Preparing your CMS System Database server MySQL database setup requirements For a MySQL database there are no specific parameters that are crucial for BusinessObjects Enterprise to work. ensure the following variable is set up for the user who will install BusinessObjects Enterprise XI 3. Related Topics • Preparing your existing database server on page 35 Testing MySQL environment variables If you are using an existing MySQL database.

the users and usergroup objects may not sort properly in the Central Management Console. For details. Note: This requirement does not apply to the Audit database. before you begin the install of BusinessObjects Enterprise. Preparing to Install BusinessObjects Enterprise Preparing your CMS System Database server 2 If your DB2 CMS database is partitioned. see Preparing your existing database server on page 35 . • Create the relational database with the specific settings. Note: If you are using DB2 8. the installation searches the current shell for the DB2INSTANCE environment variable. you will have problems creating the CMS database.0 Installation and Configuration Guide for UNIX 39 . you need to source your database client. you must ensure the DB2 environment variables are set up correctly. BusinessObjects Enterprise XI 3. Please consult the DB2 documentation for details on how to configure the C compiler for SQL stored procedures. SQL stored procedures are used in BusinessObjects Enterprise when users are added to groups in the CMS. This standard DB2 environment variable must be set in order for the install script to utilize the DB2 client software. and for determining what version of the C compiler is supported on your platform. you can use a partitioned DB2 database for the Audit database. DB2 8. For details. Consult your DB2 documentation for specifics. Replace XX with the code that is appropriate to your code set and codepage for your location. see Testing DB2 environment variables on page 39. If you want. Collating Sequence = "Identity" Codeset = "UTF-8" Territory = "XX" If your DB2 database does not have the correct collating sequence setting.1. After you create your database you will need to prepare it for the BusinessObjects Enterprise install. In addition. you require a C compiler that is installed and configured to build SQL stored procedures. Testing DB2 environment variables If you choose to connect to DB2 through a native connection. If you are using an existing database.2 does not have this requirement.

sh. Consult your database documentation for the name of its environment script. This method can be done anytime. However. These steps will test whether the required environment variables are set: Related Topics • Sourcing the script that identifies the database environment variables on page 31 Oracle database setup requirements For an Oracle database there are no specific parameters. Note: Instead of sourcing the script that identifies the database environment variables. This method will source the database for all users. This script can be found at the following location: <install dir>/bobje/init/setupint.0 Installation and Configuration Guide for UNIX . an entry would be made in the user profile to source the environment script used by DB2 (db2profile). you must ensure the Oracle environment variables are set up correctly.2 Preparing to Install BusinessObjects Enterprise Preparing your CMS System Database server Sourcing the script that identifies the database environment variables can be done in one of two ways: • The user who performs a system installation can modify the BusinessObjects Enterprise script setupint. if you manually set the environment variables. • Each person with a user installation can modify their profile and add the command to source their database environment. you can manually set the environment variables required by your database. However. 40 BusinessObjects Enterprise XI 3. However. or if you are unable to connect successfully to the database.sh to add the command to source your database client. if an DB2 database was required. before you begin the install of BusinessObjects Enterprise. root access is required to execute this script. for information. For example. that are required for BusinessObjects Enterprise to work. you will need to set them again if the system is restarted. other than the setting of UTF-8. Consult your database documentation and/or your database administrator if the account shell environment from which you will install BusinessObjects Enterprise has not yet been set up for your database client software.

the installation searches the current shell for the ORACLE_HOME environment variable.sh where XX is replaced with the version number).sh.0 Installation and Configuration Guide for UNIX 41 . if you manually set the environment variables. For example. However. or if you are unable to connect successfully to the database. This standard Oracle environment variable must be set in order for the install script to utilize the Oracle client software. root access is required to execute this script. This method will source the database for all users. an entry would be made in the user profile to source the environment script used by Oracle (oraXXenv. • Consult your database documentation and/or your database administrator if the account shell environment from which you will install BusinessObjects Enterprise has not yet been set up for your database client software.csh or oraXXenv. Sourcing your database client can be done in one of two ways: • The user who performs a system installation can modify the BusinessObjects Enterprise script setupint. Note: • Instead of sourcing the script that identifies the database environment variables. you need to source your database client. you can manually set the environment variables required by your database. if an Oracle database was required.sh to add the command to source your database client. This script can be found at the following location: <install dir>/bobje/init/setupint. This method can be done anytime. • Each person with a user installation can modify their profile and add the command to source their database environment. BusinessObjects Enterprise XI 3. If you are using an existing database. However. you will need to set them again if the system is restarted. Preparing to Install BusinessObjects Enterprise Preparing your CMS System Database server 2 Related Topics • Testing Oracle environment variables on page 41 Testing Oracle environment variables If you choose to connect to Oracle through a native connection. Consult your database documentation for the name of its environment script.

Before you begin the install of BusinessObjects Enterprise. the page size must be 8KB. These standard Sybase environment variables must be set in order for the install script to utilize the Sybase client software. ensure the page size is set to 8 KB. Sourcing the script that identifies the database environment variables can be done in one of two ways: • The user who performs a system installation can modify the BusinessObjects Enterprise script setupint.2 Preparing to Install BusinessObjects Enterprise Preparing your CMS System Database server Related Topics • Sourcing the script that identifies the database environment variables on page 31 Sybase database setup requirements If you are using Sybase. root access is required to execute this script. when you create your database for the CMS. the installation searches the current shell for the SYBASE and SYBASE_OCS environment variables. However. you must ensure the Sybase environment variables are set up correctly. After you create your database you will need to prepare it for the BusinessObjects Enterprise install.0 Installation and Configuration Guide for UNIX . For CMS to run optimally. Related Topics • Preparing your existing database server on page 35 • Testing Sybase environment variables on page 42 Testing Sybase environment variables If you choose to connect to Sybase through a native connection. The page size is set up during the database creation and it cannot be changed after the database is set up. This script can be found at the following location: <install 42 BusinessObjects Enterprise XI 3.sh to add the command to source your database client. If you are using an existing database. you need to source the script that identifies the database environment variables. Note: The Sybase database default page size is 2KB which is too small for CMS.

BusinessObjects Enterprise XI 3. an entry would be made in the user profile to source the environment script used by Sybase (SYBASE. Only then can the installation setup program access the CMS database using your database client software. if a Sybase database was required. These steps will test whether the required environment variables are set: Related Topics • Sourcing the script that identifies the database environment variables on page 31 Providing and verifying connectivity to the CMS database To create tables and write data to your new CMS database. For example. Consult your database documentation for the name of its environment script. • Each person with a user installation can modify their profile and add the command to source their database environment. you will need to set them again if the system is restarted.0 Installation and Configuration Guide for UNIX 43 . the default shell environment must include the appropriate database environment variables and/or initialization files. or if you are unable to connect successfully to the database.csh). This method can be done anytime. • Consult your database documentation and/or your database administrator if the account shell environment from which you will install BusinessObjects Enterprise has not yet been set up for your database client software. the installation scripts need to establish a connection to the database server.sh or SYBASE. Preparing to Install BusinessObjects Enterprise Providing and verifying connectivity to the CMS database 2 dir>/bobje/init/setupint. That is. This method will source the database for all users. Note: • Instead of sourcing the script that identifies the database environment variables. you can manually set the environment variables required by your database. when you log on to UNIX with the user name from which you will perform the installation. if you manually set the environment variables. However.sh.

See Creating an account. Echo the following environment variables and ensure that their values correspond to your database client software installation. test the shell environment of the account from which you will install BusinessObjects Enterprise to verify database connectivity and privileges. Note: This account should already be set up. and a login environment on page 21for more information on setting up a UNIX account to use when you install BusinessObjects Enterprise. 2. Before running the installation script. a home directory. Log on to the UNIX server with the user account and password which you will use to do your install.2 Preparing to Install BusinessObjects Enterprise Providing and verifying connectivity to the CMS database The environment variables and/or files required by the installation scripts depend upon the type of database server you are running: Additional database environment variables must be set in order for the installation script to use the database client software properly. Variable Value This variable contains the path to the root directory of your Sybase SYBASE client installation (one level above the SYBASE_OCS version directo- ry).0 Installation and Configuration Guide for UNIX . • Testing Sybase environment variables on page 42 • Testing Oracle environment variables on page 41 • Testing DB2 environment variables on page 39 To verify Sybase native connectivity through a server name 1. 44 BusinessObjects Enterprise XI 3. See the procedure that corresponds to your database.

password.0 $ echo $SYBASE_OCS OCS-12_O $ echo $LD_LIBRARY_PATH /export/home/sybase/12.0/OCS- 12_0/bin 3. BusinessObjects Enterprise XI 3. Issue the following command to run the Sybase SQL tool and connect to the database server: isql -U user -P password -S servername Replace user. LIBPATH on AIX. This example checks the required variables. you are connected to Sybase. Preparing to Install BusinessObjects Enterprise Providing and verifying connectivity to the CMS database 2 Variable Value This variable contains the name of the Sybase version directory (one SYBASE_OCS level above the Sybase bin and lib directories).0/OCS-12_0/lib $ echo $PATH /usr/bin:/usr/ucb:/etc:. and servername with the appropriate values. The search path must include the PATH bin directory of your Sybase client installation. and shows sample output values: $ echo $SYBASE /opt/sybase/12. and SHLIB_PATH library path on HPUX) must include the lib di- rectory of your Sybase client instal- lation.:/export/home/sybase/12.0 Installation and Configuration Guide for UNIX 45 . The library search path (LD_LI BRARY_PATH on Solaris and Linux. If the shell environment has been configured correctly.

and a login environment on page 21 for more information on setting up a UNIX account to use when you install BusinessObjects Enterprise. Issue the following command to ensure that the account has permission to delete tables: drop table sampletable go sp_help sampletable go 6. a home directory. Issue the following command to ensure that the account has permission to create tables: use aps go create table sampletable (def_field char(10)) go sp_help sampletable go 5.2 Preparing to Install BusinessObjects Enterprise Providing and verifying connectivity to the CMS database 4. Type quit To verify Oracle native connectivity through a TNS 1.0 Installation and Configuration Guide for UNIX . Note: This account should already be set up. 46 BusinessObjects Enterprise XI 3. Log on to the UNIX server with the user account and password which you will use to do your install. Variable Value This variable contains the path to the root directory of your Oracle ORACLE_HOME client installation (one level above the Oracle bin and lib directories). See Creating an account. Echo the following environment variables and ensure that their values correspond to your database client software installation. 2.

5.0 Installation and Configuration Guide for UNIX 47 .0. Preparing to Install BusinessObjects Enterprise Providing and verifying connectivity to the CMS database 2 Variable Value The library search path (LD_LI BRARY_PATH on Solaris and Linux. LIBPATH on AIX.1. 4.0.1. Issue the following command to ensure that account has permission to create tables: create table sampletable (field1 char(10)). you are connected to Oracle.0. and SHLIB_PATH library path on HPUX) must include the lib32 directory of your Oracle client instal- lation.1. The search path must include the PATH bin directory of your Oracle client installation. If the shell environment has been configured correctly.password and tnsname with the appropriate values. This example checks the required variables and shows sample output values. Issue the following command to run the Oracle SQL tool and connect to the appropriate service name: sqlplus accountname/password@tnsname Replace accountname. Issue the following command to ensure that the account has permission to delete tables: drop table sampletable.3/lib32 $ echo $PATH /usr/local/bin:/home/dbclient/oracle/10. BusinessObjects Enterprise XI 3.3 $ echo $LD_LIBRARY_PATH /home/dbclient/oracle/10. $ echo $ORACLE_HOME /home/dbclient/oracle/10.3/bin 3.

2 Preparing to Install BusinessObjects Enterprise Providing and verifying connectivity to the CMS database 6.0 Installation and Configuration Guide for UNIX . END. 7. Log on to the UNIX server with the user account and password which you will use to do your install. 2. Variable Value This variable defines the current DB2INSTANCE DB2 database instance. Echo the following environment variables and ensure that their values correspond to your database client software installation. Issue the following command to ensure that the account has permission to create procedures: CREATE PROCEDURE test_proc (foo_in VARCHAR. See Creating an account. and a login environment on page 21 for more information on setting up a UNIX account to use when you install BusinessObjects Enterprise. Issue the following command to ensure that the account has permission to drop procedures: DROP PROCEDURE TEST_PROC. 8. This variable contains the path to INSTHOME the root directory of your DB2 client installation 48 BusinessObjects Enterprise XI 3. bar_in). bar_in VARCHAR) IS BEGIN INSERT INTO test_table (foo. Note: This account should already be set up. bar) VALUES (foo_in. Type exit To verify DB2 native connectivity through a database alias 1. a home directory.

and SHLIB_PATH library path on HPUX) must include the lib di- rectory of your DB2 client installa- tion. Preparing to Install BusinessObjects Enterprise Providing and verifying connectivity to the CMS database 2 Variable Value This variable contains the path to the root directory of your DB2 instal- DB2DIR lation (one level above the DB2 bin and lib directories). This example checks the required variables and shows sample output values. If the shell environment has been configured correctly.1 $ echo $LD_LIBRARY_PATH /export/home/db2inst1/sqllib/lib $ echo $PATH /usr/bin:/usr/ucb:/etc:. $ echo $DB2INSTANCE db2inst1 $ echo $DB2DIR /opt/IBMdb2/V7. you are connected to DB2. LIBPATH on AIX.0 Installation and Configuration Guide for UNIX 49 . Issue the following command to connect to the desired database alias: connect to db_alias user accountname using password Replace db_alias and password with the appropriate values. Issue the following command to run the DB2 SQL tool: db2 4.:/export/home/db2inst1/sqllib/adm:/ex port/home/db2inst1/sqllib/misc 3. The library search path (LD_LI BRARY_PATH on Solaris and Linux. The search path must include the PATH bin directory of your DB2 client in- stallation. BusinessObjects Enterprise XI 3.

0 Installation and Configuration Guide for UNIX .2 Preparing to Install BusinessObjects Enterprise Before you deploy web applications 5. Before you begin the deployment process. in addition to any other requirements specified by other software installed on the machine. Issue the following command to ensure that the account has permission to delete tables: drop table sampletable 7. and <PORT> with the port number used for HTTP. 50 BusinessObjects Enterprise XI 3. your web application server should have at least 1. Consult your web application server documentation for installation instructions. To deploy and run the CMC and InfoView applications. 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. It is recommended that you change the heapsize and maximum perm size settings of your JVM to -Xmx1024m -XX:MaxPermSize=256m. Issue the following command to ensure that the account has permission to create tables: create table sampletable (col_fld char(10) not null) 6. Type terminate Before you deploy web applications Your web application server must be installed and working before you attempt to install BusinessObjects Enterprise. If using Tomcat for example. Consult your web application server documentation for installation instructions. ensure that the web application server is correctly installed and verify that the application server is running correctly by launching its administrative console at: • http://<WAS_HOSTNAME>:<PORT> Replace <WAS_HOSTNAME> with the host name or IP address of your web application server.2 GB of free disk space.

Beginning the Installation of BusinessObjects Enterprise 3 .

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

the various core server components run as background processes. However. When you install the BusinessObjects Enterprise server components on a UNIX machine. The installation can place the necessary run control scripts in the relevant directories for automated startup (requires root privileges). a period. After you finish the installation and setup procedures. these client applications must be installed on Windows. or a slash? • Have you sourced your database client so that all the required environment variables are set up properly? • If you are using DB2 or Sybase. is your web application server already installed and configured? • Do the BusinessObjects Enterprise system requirements match your UNIX setup? • If you are installing on VMWare.0 Installation and Configuration Guide for UNIX 53 . have you verified that your database was created with the correct settings? (Some settings can't be modified after the database has been created. Note: Before you run the interactive installation setup program (. You can then deploy the BusinessObjects Enterprise web applications. BusinessObjects Enterprise XI 3. or you can confine the installation to a particular directory. you can connect remotely to BusinessObjects Enterprise with the Publishing Wizard and the Import Wizard. Users then connect to BusinessObjects Enterprise over the Web with a supported web browser. Beginning the Installation of BusinessObjects Enterprise Installation overview 3 • If you are not using Tomcat. it is strongly recommended that you read through the details and procedures provided in the previous chapter Setting up product distribution This section shows how to distribute BusinessObjects Enterprise so that you can perform an installation./install).) Installation overview BusinessObjects Enterprise allows you to run all server components on a UNIX server. have you ensured your machine name does not include any of the following characters: an underscore.

as its base directory for the install.sh from. and then run install. • When you run .sh. you will be prompted to specify a temporary location for the install.sh from that location.sh without copying the files to a temporary location.sh from. you will not be prompted for a temporary location to put the files. the installation will use your current directory. that is. or locally through a terminal window.0 Installation and Configuration Guide for UNIX .sh. Before following this procedure. as its base directory for the install./install. 54 BusinessObjects Enterprise XI 3. the installation will use your current directory. that is. you can specify the temporary location to place the installation distribution. Copying the product distribution to your machine By default. There are two ways you can set up the product distribution: • Before you run .sh from there. this will happen: • The installation files will be copied to that temporary location.sh. you can copy the installation files to a temporary location. After you specify the temporary location. be sure to set your terminal settings to VT100 before beginning the installation. the directory you run install. If you will connect remotely to install BusinessObjects Enterprise. The advantage of this option is that when you run in stall. You may want to copy the product distribution to directory on your machine and run in stall. Related Topics • Setting up your UNIX system on page 20 Running the product distribution directly from a CD By default. You are then required to go to the temporary location you specified./install.3 Beginning the Installation of BusinessObjects Enterprise Setting up product distribution You can perform this installation remotely through a telnet session. ensure that you have set up your UNIX system appropriately. • The installation program will exit. the directory you run install. If you run in stall.

a home directory. 3. Proceed to Beginning your installation on page 55.0 Installation and Configuration Guide for UNIX 55 . Log on to your UNIX system under the new account designated for installing BusinessObjects Enterprise. Related Topics • Creating an account. Repeat this process for each DISK contained in the product distribution. Copy the installation files from the product distribution to a temporary directory with this command where /mnt/cd is mapped to the CD drive and tmp is a temporary directory where you want to store the installation files: /mnt/cd/install -t /tmp/ . Beginning the Installation of BusinessObjects Enterprise Beginning your installation 3 To copy the product distribution to your machine 1. Run install. • Agree to the license terms. and a login environment on page 21 Beginning your installation The following instructions lead you through the initial steps of installing BusinessObjects Enterprise on UNIX. • Select which language packs to install. • Enter the product key codes. • Select an install type. • Choose between a user and system install.sh from the first CD. 2. In this stage you will do the following: • Choose the language for the installation. • Select where to install BusinessObjects Enterprise. BusinessObjects Enterprise XI 3. 4.

sh without copying the files to a temporary location. The installation setup program is launched and you are prompted to select a language for the installation. This section is followed by a detailed description of each screen in the installation setup program.3 Beginning the Installation of BusinessObjects Enterprise Beginning your installation To begin your installation The installation procedure below is a quick overview of the initial steps required to install BusinessObjects Enterprise on UNIX. Type . Note: If you run install./install. you will be prompted to specify a temporary location for the install. Select a language for the installation and press Enter.sh in the command line and press Enter. 1. Mount the device that contains the installation files. You can select from one of the following languages: • German • English • Spanish • French • Italian • Japanese • Korean • Dutch • Portuguese • Swedish • Simplified Chinese • Traditional Chinese The "Business Objects License Agreement" is displayed.0 Installation and Configuration Guide for UNIX . Related Topics • Running the product distribution directly from a CD on page 54 56 BusinessObjects Enterprise XI 3. 2. 3.

1. Type your code in Product Keycode. The keycode contains 26 characters and you can find it in the CD liner notes or the CD sleeve. Entering Product Keycode You must provide a valid BusinessObjects Enterprise product activation keycode to continue with the installation setup program. Read the software license agreement. 1. 2. 2. Press Enter to validate the keycode. you must accept the Business Objects License Agreement. you must specify an installation directory. To create your own directory. The "Enter Product Keycode" screen is displayed. 2. BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX 57 . use the Backspace key to remove the current directory and replace it with your own path to the desired installation directory and press Enter. Type y to agree to the terms and continue with the setup program. To accept the default installation directory press Enter. Specifying the installation directory After your product keycode is validated. 1. You are prompted to select which language packs to install. Installing language packs You can choose to install language packs when running the installation setup program on UNIX. Beginning the Installation of BusinessObjects Enterprise Beginning your installation 3 To accept the license agreement To install Business Objects Enterprise on UNIX. The setup program validates the keycode before the "Installation Directory" screen is displayed.

Press Enter . You are prompted to select either a user or system installation. Note: You can add language packs after installing Business Objects Enterprise on UNIX. However. • User • System Note: To perform a System installation. Related Topics • To install language packs on page 134 To select user or system installation 1.3 Beginning the Installation of BusinessObjects Enterprise Beginning your installation 1. 2. After you perform a System installation. 58 BusinessObjects Enterprise XI 3. you do not require root-level authority. 2.0 Installation and Configuration Guide for UNIX . Press Enter. to run the system-level initiation script root-level authority is required. The "Installation Type" screen is displayed. there are a few additional steps you must perform. Select any additional language packs you want to install. Select the type of installation you want to perform. The following languages are available: • French • Japanese • German • Spanish • Italian • Korean • Dutch • Portuguese • Swedish • Simplified Chinese • Traditional Chinese Note: English is a required language and cannot be deselected.

Recommended for advanced users. To perform a new System installation. all the required components are installed. This option installs the Web BusinessObjects Enterprise XI 3. • When you choose a User installation. You may want to perform a custom installation if you plan to use BusinessObjects Enterprise in a distributed environment. however. all the required components are also installed. the installation creates a system-level initiation script. you require root-level authority • Custom or Expand The custom installation allows you to choose which components are installed.0 Installation and Configuration Guide for UNIX 59 . Beginning the Installation of BusinessObjects Enterprise Beginning your installation 3 Difference between user and system installation There are two possible options for new Business Objects Enterprise installations on UNIX. Select the installation type. 1. • When you choose a System installation. Related Topics • Finishing a system installation on page 103 Selecting an installation type You can select from one of the following three installation types: New. • New Performing a new installation is the simplest way to deploy BusinessObjects Enterprise because all the required components are installed by default onto one machine. This script creates entries into the run levels for the Operating System that starts the BusinessObjects Enterprise servers when the UNIX server is brought up and stops the BusinessObjects Enterprise servers when a machine is shut down. or Web Tier. Custom. • Install Web Tier features Choose to perform a web applications installation if you want to install web application server components. in addition.

stopping.3 Beginning the Installation of BusinessObjects Enterprise Beginning your installation application components only. Press Enter. disabling and enabling servers.0 Installation and Configuration Guide for UNIX . Related Topics • Performing a new installation on page 62 • Performing a custom installation on page 76 • To perform a web tier installation on page 96 60 BusinessObjects Enterprise XI 3. refer to the BusinessObjects Enterprise Administrator's Guide. 2. For more information on starting. • You may select Disable servers after installation to automatically stop all servers. This will prevent communication between the Central Management Server (CMS) and other servers after the installation is complete. This is particularly useful for a distributed deployment.

New Installation 4 .

1. Confirming the installation directory. Scroll down and use the spacebar to deselect the field.0 Installation and Configuration Guide for UNIX . To perform a new installation The "Installation Type" screen in the following procedure is displayed after you have completed the initial set up of the BusinessObjects Enterprise installation. 3. The "Enter the information for your new CMS" screen is displayed. 1. 2. Select or deselect Enable servers after installation. Related Topics • Beginning your installation on page 55 62 BusinessObjects Enterprise XI 3. Configuring the Server Intelligence Agent (SIA). Setting up the web application server. The setup of a new installation of BusinessObjects Enterprise requires the following input. You can choose to either install and configure MySQL or configure your existing database. 4. Select New and press Enter. You can choose to either install and configure Tomcat or configure your existing web application server. 5. 2. Providing information on the system administrator for the new installation. Setting up the system and auditing database.4 New Installation Performing a new installation Performing a new installation Performing a new installation is the simplest way to deploy BusinessObjects Enterprise because all the required and optional components are installed on one machine. This option is selected by default.

New Installation Performing a new installation 4 To configure the new CMS Use the "Enter the information for your new CMS" screen to specify the Central Management Server (CMS) port number and password for the BusinessObjects Enterprise Administrator.6400. 2. Choose one of the following options: • Use an existing database (Oracle/DB2/Sybase/MySQL) • Install MySQL 2. Your password must be at least six characters long and should contain two of the following options • upper case character • lower case character • number • punctuation To specify a system database option You must select a system database option. Press Enter. 1. Depending on your selection you will either select and configure your existing database. or configure your MySQL installation. 1. Type a valid port number in CMS Port Number or accept the default number . Type the same password under Administrator Password and Confirm Password and press Enter. You can either choose to install MySQL or specify to use your current database.0 Installation and Configuration Guide for UNIX 63 . Note: You can also leave the passwords fields blank and configure the password at a later time. Related Topics • To configure your existing database on page 64 • To install a new MySQL Database on page 66 BusinessObjects Enterprise XI 3.

Select your database type. You can choose from the following • MySQL • Oracle • DB2 • Sybase A new screen displays containing fields for configuring your database.0 Installation and Configuration Guide for UNIX . You will then have to configure the database.4 New Installation Performing a new installation To configure your existing database If you specified to use an existing database for the CMS. 1. Provide information about your database and press Enter. 2. use the "Select the database type for your new CMS" screen to select your existing database type. Database type Information required Host Name User ID for CMS database MySQL Password for CMS database MySQL port number Database name for CMS TNS name User ID for CMS database Oracle Password for CMS database CMS port number 64 BusinessObjects Enterprise XI 3. The table below lists the information required for each database type.

Decide if you want to reinitialize the database and press Enter. type an x in the field provided. Note: Reinitialization of the BusinessObjects Enterprise database will erase all previous content in that particular database. New Installation Performing a new installation 4 Database type Information required Alias name User ID for CMS database DB2 Password for CMS database CMS port number Sybase Service name User ID for CMS database Sybase Password for CMS database CMS port number 3. Provide information about your new auditing database. Database type Information required Auditing database name Auditing database port number Auditing User ID Password 4. type an x in the field provided. To enable an auditing database. If you want to enable an auditing database. BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX 65 .

If you are using an existing database. Provide the following information for your new MySQL database and press Enter.0 Installation and Configuration Guide for UNIX . Press Enter to continue with the installation setup. • MySQL Port Number • Database administrator password The second MySQL configuration screen is displayed. • Password for user account 3. . This method must be done by each user. 2. The setup program provides two screens to configure the new database. • Each user can modify their own profile and add the command to source their database environment. you are prompted for information on the Server Intelligence agent. you need to source your database environment variable so the CMS can access it after a system reboot. • MySQL CMS Database Name • MySQL Audit Database Name • User ID Note: This is the BusinessObjects Enterprise user account. This method will source the database environment variable for all users. Related Topics • Database requirements on page 30 To install a new MySQL Database You need to provide configuration details for the new MySQL database. 1. This can be done one of two ways • Someone with root access can modify the BusinessObjects Enterprise script BobjEnterprise120 and add the command to source your database environment.4 New Installation Performing a new installation After configuring your CMS and auditing database. This script can be found at the following location: <INSTALLDIR>/bobje/init/BobjEnterprise120. 66 BusinessObjects Enterprise XI 3. Provide the following information for your new MySQL database and press Enter.

Use the installer to specify to install Tomcat as your application server. or choose to work with your existing web application server.0 Installation and Configuration Guide for UNIX 67 . Deployment option When to use Install Tomcat. To select a web application server configuration option As part of the installation setup. • Select one of the options listed below and press Enter. do not deploy web plication server and you want to manually applications deploy the web applications. New Installation Performing a new installation 4 The "Enter Server Intelligence Agent information" screen is displayed. Use existing Java application If you have an existing supported web ap- server. you need to provide information on the web application server that will work with your BusinessObjects applications such as InfoView and the Central Management Console (CMC). .0.plication server and you want to automati- tions cally deploy the web applications. 1. dashes or periods in the node Name. The SIA is automatically created during installation of BusinessObjects Enterprise XI 3. This node name serves as an identifier for the SIA. deploy web If you do not have an existing web applica- applications tion server. 2. Type a valid port number under Server Intelligence Agent Port or accept the default port number -6410. Use existing Java application If you have an existing supported web ap- server. Do not use spaces. To enter Server Intelligence Agent information The Server Intelligence Agent (SIA) simplifies the deployment and management of the BusinessObjects Enterprise servers. Use the installation setup program to configure the SIA. BusinessObjects Enterprise XI 3. deploy web applica. Type a name in Server Intelligence Agent Node. and press Enter.

You can either choose to accept the default port numbers or provide new values for the following: Required port numbers Receive HTTP requests Redirect jsp requests Shutdown hook 2. If you have selected the third option you can start the installation process.0 Installation and Configuration Guide for UNIX . the "Please enter port numbers for the Tomcat installation screen" is displayed. Press Enter. Related Topics • To start the installation on page 102 To configure your existing web application server You must select the Use existing Java application server. deploy web applications option to view the "Select a Web Application Server to deploy to" screen. Select the server type before configuring your web application server. 1. the Central Management Console and other web application servers. You must configure the server to use InfoView. Related Topics • To start the installation on page 102 • To configure your existing web application server on page 99 • To configure the Tomcat installation on page 98 To configure the Tomcat installation If you chose to install the Tomcat application server.4 New Installation Performing a new installation If you have selected either the first or second option. You can now start the installation process. 68 BusinessObjects Enterprise XI 3. you will now have to configure the web application server.

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

• Application server Installation directory: The directory where the web application server is installed (for example /bea/weblog ic10/user_projects/domains/base_domain).manda- tory for Weblogic (for example “7001”).mandatory for Weblogic. • Admin login: Password for account with administration rights to the application server .mandatory for Weblogic.0 Installation and Configuration Guide for UNIX . • Application server Installation directory: The directory where the web application server is installed (e.mandatory for Weblogic. Note: For WebLogic the directory is the domain root. • Instance to install to: Name of the current web application server instance (for example “ mserver1”).g /bea/user_projects/do mains/base_domain). WebLogic 9 • Admin port: Administration port of the application server .manda- tory for Weblogic (for example “7001”).mandatory for Weblogic. • Admin login: User name with administration rights to the application server . • Admin login: User name with administration rights to the application server . • Admin password: Password for account with administration rights to the application server .4 New Installation Performing a new installation Web application Information required for installation setup server WebLogic 10 • Admin port: Administration port of the application server . • Instance to install to: Name of the current web application server instance (for example “ mserver1”). Note: For WebLogic the directory is the domain root. 70 BusinessObjects Enterprise XI 3.

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

3/OracleAS_1). • Admin login: User name with administration rights to the application server .manda- Server 10g R3 tory for Oracle 10g R3 (for example “6003”) .1. Note: To modify the directory you would need to press [Ctrl-B] several times until you reach the screen where you specify the installation directory. Related Topics • To start the installation on page 102 To start the installation You are now ready to start the installation. • Server Name: Name of the target application server (for example "myserver. . • Admin is secure (y/n): Select this option only if you want Secure Sockets Layer (SSL) as part of the deployment. Note: If Admin is secure is not selected.0 Installation and Configuration Guide for UNIX .xml file. 72 BusinessObjects Enterprise XI 3. you will still have to specify the username and password to access the server.4 New Installation Performing a new installation Web application Information required for installation setup server Oracle Application • Admin port: Administration port of the application server . • Group Id: Name of the server group to which the target application belongs (for example "Default_group"). Review the installation directory specified on the screen.mandatory for Oracle 10g R3.domain.mandatory for Oracle 10g R3. • Application server Installation directory: The directory where the web application server is installed (for example /prod uct/10.com"). 1. • Admin password: Password for account with administration rights to the application server .This should be the Re- quest port of the <notifi-cation-server> element in the opmn. • Instance to install to: Name of the current web application server instance (for example “ home”).

To control the servers manually. BusinessObjects Enterprise XI 3. Related Topics • Using ccm.sh script. New Installation Finishing a system installation 4 2. these run control scripts start/stop the BusinessObjects Enterprise servers on system startup/shutdown. you must have root privileges to run the se tupinit. however. use the ccm.sh to start the BusinessObjects Enterprise servers on page 126 Finishing a system installation If you chose to perform a system installation. you must log on using a normal account. The BobjEnter prise120 script copies the run control scripts to your /sbin/rc# directories.0 Installation and Configuration Guide for UNIX 73 . When the new installation is finished.sh script. Press Enter to start the installation. The installation program will validate your system and install BusinessObjects Enterprise in the specified directory. the setup program script prompts you to run the BobjEnterprise120 script after it is finished. After installation. Note: To run the system installation. This script copies the BobjEnterprise120 to the /sbin/rc# directory. the setup program starts the servers as daemons and then enables each server that is registered with the CMS. When implemented.

0 Installation and Configuration Guide for UNIX .4 New Installation Finishing a system installation 74 BusinessObjects Enterprise XI 3.

Custom or Expand Installation 5 .

You customize the installation in the setup program Features screen. • [ ] means the feature will not be installed. For example. To select a feature or subfeature. select its corresponding marker and type X.5 Custom or Expand Installation Performing a custom installation Performing a custom installation The Custom or Expand installation option allows you to selectively install specific features. your existing web application server resides on a different machine than the one hosting the BusinessObjects Enterprise core components.0 Installation and Configuration Guide for UNIX . The Features screen contains a tree of features divided into the following top-level features: • Client Components • Web Tier Components • Server Components • Database Access • Export Support • Samples • Help Files The markers in the tree indicate whether or not the feature and its subfeatures will be installed: • [X] means that the feature and all its subfeatures will be installed. 76 BusinessObjects Enterprise XI 3. Features available in a custom installation Client Components This feature contains the Developer Components which has two subfeatures: • BusinessObjects Enterprise Java SDK: This is the development kit for Java applications. • [~] means that the feature and some of its subfeatures will be installed. You may want to perform a custom installation if you plan to use BusinessObjects Enterprise in a distributed environment.

• Tomcat: If you do not have an existing web application server. InfoView.0. Web Tier Components This feature contains the following subfeatures: • BI Platform Web Components: This includes all components used to run BusinessObjects XI 3. Dashboard and Analytics. It is composed of an implementation of web services that can be deployed with BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX 77 . Server Components contains the following subfeatures: • Central Management Server Contains the following subfeatures: • Auditor • MySQL • Event Server • Input File Repository Server • Output File Repository Server • Crystal Reports Cache Server • Crystal Reports Processing Server • Report Application Server • Multi-Dimensional Analysis Services Server • Crystal Reports Job Server • Destination Job Server • List of Values Job Server • Program Job Server • Adaptive Job Server BusinessObjects Enterprise XI 3. Custom or Expand Installation Performing a custom installation 5 • BusinessObjects Enterprise Web Services SDK: This is the development kit for web services. you can choose to install Apache Tomcat 5.5. and Voyager. please consult the “BusinessObjects Enterprise Architecture” chapter of the BusinessObjects Enterprise Administrator's Guide. Server Components For a detailed explanation of what the listed servers do. • BusinessObjects Enterprise Web Services: This is a component of Business Objects Enterprise built for developers.0 applications including Central Management Console.

It contains the following subfeatures: • Data Fedrator • MySQL • Generic ODBC • NETEZZA • ALL IBM Database Drivers contains the following subfeatures: • IBM DB2 • Informix • Progress OpenEdge • Oracle • Sybase • NCR Teradata Export Support This feature contains drivers and files to enable export to a variety of industry standard file formats.0 Installation and Configuration Guide for UNIX .5 Custom or Expand Installation Performing a custom installation • Adaptive Processing Server • Web Intelligence Report Server • Desktop Intelligence Servers • Dashboards and Analytics Servers • Auditing Reports and Universes Database Access This feature installs the necessary drivers and files to provide access to a broad range of data sources. It includes the following subfeatures: • Character Separated • Disk File • Rich Text Format • Word for Windows • Acrobat PDF • Text • Excel Format • Crystal Reports • XML Format • Legacy XML Format 78 BusinessObjects Enterprise XI 3.

After selecting what components you want to install press Enter. Deselect the Tomcat subfeature under Web Tier Components if you want to use your existing web application server. Deselect any features you do not want to install. Scroll down and use the spacebar to deselect the field.businessobjects. Select Custom or Expand and press Enter. Expand any displayed features to drill down to display available sub features. Only English samples will be installed. Consult the BusinessObjects Enterprise Administrator's Guide for information about scaling your deployment across multiple machines. a BIAR file that includes Web Intelligence reports as well as the universe used to create these reports. The "Features" screen is displayed with seven top level features. This option is selected by default. BusinessObjects Enterprise XI 3. Sample reports are located in the Report Samples folder. Custom or Expand Installation To perform a Custom or Expand installation 5 Samples Included are samples for Crystal Reports. Select or deselect Enable servers after installation.com/. 1. 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. Deselect Auditor under Server Components if you do not want to configure an auditing database. b. To perform a Custom or Expand installation The Installation Type screen in the following procedure appears after you have completed the initial set up of the BusinessObjects Enterprise installation.0 Installation and Configuration Guide for UNIX 79 . a. Samples in other languages can be downloaded from http://support. c. 2. 3. 4. Deselect MySQL under Server Components if you want to use your existing database server.

The Installation Type screen in the following procedure appears after you have completed the initial setup of the BusinessObjects Enterprise installation. the default user and group accounts are created.0 Installation and Configuration Guide for UNIX . 6. If you chose to Install MySQL. Deselect Auditor under Central Management Server if you do not want to configure and auditing database. the server components are installed. 2. 3. choose Custom or Expand. 5. the servers are automatically started. If you deselected the Central Management Server (CMS) feature. you must configure your new database. Select the Server top level feature under BusinessObjects Enterprise. Press Enter to submit your selections. When the installation is complete. When you perform this installation scenario. Deselect the Client Components and Web Tier Component features. Note: Ensure that the markers for the deselected features appear as [ ]. 1. 4. Related Topics • Beginning your installation on page 55 • To cluster servers to an existing CMS on page 85 • To specify CMS clustering information on page 82 • To configure MySQL in a custom or expand installation on page 81 80 BusinessObjects Enterprise XI 3. If you only deselected MySQL you must specify CMS clustering information. and the sample reports are published to the system. On the Installation Type screen. Deselect MySQL under Central Management Server if you plant to use an existing database server.5 Custom or Expand Installation To perform a Custom or Expand installation Related Topics • Beginning your installation on page 55 • Installing only the Web Tier Components on page 86 • To install only the server components on page 80 To install only the server components You would typically only install the server components onto a machine that you have set aside for use by BusinessObjects Enterprise. you must cluster the installed servers to an existing CMS.

BusinessObjects Enterprise XI 3. 3. The setup program provides two screens to configure the MySQL database.0 Installation and Configuration Guide for UNIX 81 . 2. 4. Provide the following information for your new MySQL database and press Enter.6400. • MySQL CMS Database Name • MySQL Audit Database Name • User ID Note: This is the BusinessObjects Enterprise user account. Provide the following information for your new MySQL database and press Enter. Type the same password under Administrator Password and Confirm Password and press Enter. 1. Note: You can also leave the passwords fields blank and configure the password at a later time. The "Enter Server Intelligence Agent information" screen is displayed. • MySQL Port Number • Database administrator password The second MySQL configuration screen is displayed. Your password must be at least six characters long and should contain three of the following options • upper case character • lower case character • number • punctuation You need to provide configuration details for the new MySQL database. Press Enter to continue with the installation setup. • Password for user account 5. Custom or Expand Installation To perform a Custom or Expand installation 5 To configure MySQL in a custom or expand installation The "Enter the information for your new CMS" is displayed because you chose to install MySQL in the "Feature" screen. Type a valid port number in CMS Port Number or accept the default value .

but want to install an Central Management Server (CMS). • Yes . b. b. 82 BusinessObjects Enterprise XI 3. • No .5 Custom or Expand Installation To perform a Custom or Expand installation Related Topics • To enter Server Intelligence Agent information on page 85 To specify CMS clustering information If you deselected MySQL in the "Features" screen. If you selected Yes in step 1: a. Note: You can also leave the passwords fields blank and configure the password at a later time.Cluster this CMS with an existing CMS Note: If you select this option you must provide information on the existing CMS on which you are going to cluster the servers. You need to specify a valid unused port for the new CMS in New CMS Port. you need to provide more information on CMS clustering on your deployment 1.This is the first CMS in this deployment Note: If you select this option you must provide information on your new CMS. Your password must be at least six characters long and should contain two of the following options • upper case character • lower case character • number • punctuation c. Type the system name of the CMS to which you are clustering in Existing CMS Hostname. 3. 2.6400.0 Installation and Configuration Guide for UNIX . If you selected No in step 1: a. Type a valid port number in CMS Port Number or accept the default number . Skip to step 4. Type the same password under Administrator Password and Confirm Password and press Enter. Select on of the following options and press Enter. You must now select and configure your database server.

Provide information about your database and press Enter. 4. 5. Custom or Expand Installation To perform a Custom or Expand installation 5 c.0 Installation and Configuration Guide for UNIX 83 . Accept the default value -6400. You can choose from the following • MySQL • Oracle • DB2 • Sybase A new screen displays containing fields for configuring your database. The table below lists the information required for each database type. Database type Information required Host Name User ID for CMS database MySQL Password for CMS database MySQL port number Database name for CMS TNS name User ID for CMS database Oracle Password for CMS database CMS port number BusinessObjects Enterprise XI 3. d. You must now select and configure your existing database server.or else type the port number in Existing CMS Port. Select your database type. Type the password or leave Existing CMS Administrator Password blank and press Enter.

0 Installation and Configuration Guide for UNIX . Decide if you want to reinitialize the database and press Enter. If you deselected Auditor in the "Features" screen skip to step 7.5 Custom or Expand Installation To perform a Custom or Expand installation Database type Information required Alias name User ID for CMS database DB2 Password for CMS database CMS port number Sybase Service name User ID for CMS database Sybase Password for CMS database CMS port number 6. Otherwise you must provide the following information about your new auditing database: Database type Information required Auditing database name Auditing database port number Auditing User ID Password 7. 84 BusinessObjects Enterprise XI 3. Note: Reinitialization of the BusinessObjects Enterprise database will erase all previous content in that particular database.

This node name serves as an identifier for the SIA. Type a valid port number under Server Intelligence Agent Port or accept the default port number -6410. Type a name in Server Intelligence Agent Node.Provide the password by the CMS Administrator. you will be prompted to cluster the servers you are installing to an existing CMS. To enter Server Intelligence Agent information The Server Intelligence Agent (SIA) simplifies the deployment and management of the BusinessObjects Enterprise servers. . BusinessObjects Enterprise XI 3. Use the installation setup program to configure the SIA. 1.or else type the port number used by the CMS.0 Installation and Configuration Guide for UNIX 85 .0. you are prompted for information on the Server Intelligence agent. Port Accept the default value -6400. Press Enter. You now have to configure a Server Intelligence Agent for your installation. Custom or Expand Installation To perform a Custom or Expand installation 5 After configuring your CMS and auditing database. The SIA is automatically created during installation of BusinessObjects Enterprise XI 3. 2. Provide the following information on the CMS to which you are clustering: Field Information required CMS Hostname The system name of the machine on which the CMS is installed. Existing CMS Adminis. Related Topics • To enter Server Intelligence Agent information on page 85 To cluster servers to an existing CMS If you deselected the Central Management Server feature. and press Enter. 1. dashes or periods in the node Name. Do not use spaces. trator Password 2.

1. 86 BusinessObjects Enterprise XI 3.sh script.5 Custom or Expand Installation To perform a Custom or Expand installation To start the installation You are now ready to start the installation. Note: To modify the directory you would need to press [Ctrl-B] several times until you reach the screen where you specify the installation directory.0 Installation and Configuration Guide for UNIX . the setup program starts the servers as daemons and then enables each server that is registered with the CMS. use the ccm. To control the servers manually. Review the installation directory specified on the screen. Tip: If you only want to only install Web Tier components.sh to start the BusinessObjects Enterprise servers on page 126 Installing only the Web Tier Components You can chose to only install the Web Tier components while running a Custom or Expand installation. to save time and avoid installing unnecessary components run a Web Applications installation. Related Topics • Using ccm. The installation program will validate your system and install BusinessObjects Enterprise in the specified directory. Press Enter to start the installation. You would typically only install the Web Tier components on the machine running your web application server. 2. Related Topics • To perform a web tier installation on page 96 To install only the Web Tier Components The Installation Type screen in the following procedure appears after you have completed the initial set up of the BusinessObjects Enterprise installation. When the new installation is finished.

Note: If no password is required. 3. The Features screen is displayed 2. leave the field empty. or choose to work with your existing web application server. Depending on your selection in the "Features" screen. Specify the password required for Administrator access to the CMS in Existing CMS Administrator Password. 4. 2. 3. On the Installation Type screen. or specify a deployment option. Press Enter. Related Topics • Beginning your installation on page 55 • To cluster web tier features to a CMS on page 97 To cluster web tier features to a CMS You need to be able to connect to a running Central Management Server (CMS). you need to provide information on the web application server that will work with your BusinessObjects applications such as InfoView and the Central Management Console (CMC). Use the installer to specify to install Tomcat as your application server. Specify the machine name where the CMS is installed in CMS Hostname. 1.0 Installation and Configuration Guide for UNIX 87 . Modify the value if your CMS is using another port. After selecting what web tier features to install. Accept 6400 as the Port if that is number used by the CMS. Custom or Expand Installation To perform a Custom or Expand installation 5 1. Select the Web Tier Components option under BusinessObjects Enterprise. You will be prompted to cluster your selected web tier components to an existing Central Management Server. you will now either configure the Tomcat applications server. Deselect all the other top-level features by typing X in all the corresponding markers. Ensure that all the markers for the other top level features appear as []. BusinessObjects Enterprise XI 3. choose Custom or Expand. To select a web application server configuration option As part of the installation setup. Deselect the Tomcat subfeature if you want to use your existing web application server and press Enter. you need to provide information on the CMS to which the feature will be clustered.

0 Installation and Configuration Guide for UNIX .5 Custom or Expand Installation To perform a Custom or Expand installation • Select one of the options listed below and press Enter. 1. Use existing Java application If you have an existing supported web ap- server. the Central Management Console and other web application servers. Related Topics • To start the installation on page 102 • To configure your existing web application server on page 99 • To configure the Tomcat installation on page 98 To configure the Tomcat installation If you chose to install the Tomcat application server. deploy web If you do not have an existing web applica- applications tion server.plication server and you want to automati- tions cally deploy the web applications. 88 BusinessObjects Enterprise XI 3. do not deploy web plication server and you want to manually applications deploy the web applications. You must configure the server to use InfoView. You can now start the installation process. Deployment option When to use Install Tomcat. Press Enter. Use existing Java application If you have an existing supported web ap- server. deploy web applica. You can either choose to accept the default port numbers or provide new values for the following: Required port numbers Receive HTTP requests Redirect jsp requests Shutdown hook 2. If you have selected the third option you can start the installation process. If you have selected either the first or second option. the "Please enter port numbers for the Tomcat installation screen" is displayed. you will now have to configure the web application server.

Custom or Expand Installation To perform a Custom or Expand installation 5 Related Topics • To start the installation on page 102 To configure your existing web application server You must select the Use existing Java application server. Provide the requested configuration details for your web application server and press Enter. If you selected one of the supported servers.0 Installation and Configuration Guide for UNIX 89 . you can begin the installation. select Other. you can now configure the server on a separate screen. Select your existing web application server from one of the following options and press Enter.0 or JBoss 4. 1. deploy web applications option to view the "Select a Web Application Server to deploy to" screen. BusinessObjects Enterprise XI 3.5 • Instance to install to: Name of the current web application server instance (for example “localhost”).1 • Oracle Application Server 10g R3 • Other If your existing web application server is SAP Application Server 7.04. If you select Other. Select the server type before configuring your web application server. • Application server Installation directory: The directory where the web application server is installed (for example <INSTALLDIR>/wde ploy/appserver/Tomcat5520).5 • WebLogic 10 • WebLogic 9 • WebSphere 6. 2. Web application Information required for installation setup server Apache Tomcat 5. The table below summarizes the information required for each supported web application server. • Tomcat 5.

• Instance to install to: Name of the current web application server instance (for example “ mserver1”). • Application server Installation directory: The directory where the web application server is installed (for example /bea/weblog ic10/user_projects/domains/base_domain).mandatory for Weblogic.5 Custom or Expand Installation To perform a Custom or Expand installation Web application Information required for installation setup server WebLogic 10 • Admin port: Administration port of the application server . • Application server Installation directory: The directory where the web application server is installed (e. • Admin login: Password for account with administration rights to the application server . 90 BusinessObjects Enterprise XI 3.mandatory for Weblogic.0 Installation and Configuration Guide for UNIX .g /bea/user_projects/do mains/base_domain).mandatory for Weblogic. • Admin password: Password for account with administration rights to the application server .manda- tory for Weblogic (for example “7001”). • Admin login: User name with administration rights to the application server . Note: For WebLogic the directory is the domain root. WebLogic 9 • Admin port: Administration port of the application server .manda- tory for Weblogic (for example “7001”). Note: For WebLogic the directory is the domain root.mandatory for Weblogic. • Instance to install to: Name of the current web application server instance (for example “ mserver1”). • Admin login: User name with administration rights to the application server .

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

5 Custom or Expand Installation To perform a Custom or Expand installation Web application Information required for installation setup server Oracle Application • Admin port: Administration port of the application server .manda- Server 10g R3 tory for Oracle 10g R3 (for example “6003”) .0 Installation and Configuration Guide for UNIX .mandatory for Oracle 10g R3.This should be the Re- quest port of the <notifi-cation-server> element in the opmn.3/OracleAS_1). • Group Id: Name of the server group to which the target application belongs (for example "Default_group").1. . • Admin password: Password for account with administration rights to the application server . • Admin login: User name with administration rights to the application server . • Admin is secure (y/n): Select this option only if you want Secure Sockets Layer (SSL) as part of the deployment. Review the installation directory specified on the screen. • Server Name: Name of the target application server (for example "myserver.mandatory for Oracle 10g R3.com"). • Instance to install to: Name of the current web application server instance (for example “ home”). Note: If Admin is secure is not selected. Note: To modify the directory you would need to press [Ctrl-B] several times until you reach the screen where you specify the installation directory. Press Enter to start the installation. you will still have to specify the username and password to access the server. • Application server Installation directory: The directory where the web application server is installed (for example /prod uct/10.domain.xml file. Related Topics • To start the installation on page 102 To start the installation You are now ready to start the installation. 2. 92 BusinessObjects Enterprise XI 3. 1.

Related Topics • Using ccm. When the new installation is finished. When implemented. however. To control the servers manually.sh to start the BusinessObjects Enterprise servers on page 126 Finishing a system installation If you chose to perform a system installation. After installation. the setup program script prompts you to run the BobjEnterprise120 script after it is finished. Note: To run the system installation.sh script. you must log on using a normal account. use the ccm. This script copies the BobjEnterprise120 to the /sbin/rc# directory. BusinessObjects Enterprise XI 3. you must have root privileges to run the se tupinit. these run control scripts start/stop the BusinessObjects Enterprise servers on system startup/shutdown. The BobjEnter prise120 script copies the run control scripts to your /sbin/rc# directories.sh script. the setup program starts the servers as daemons and then enables each server that is registered with the CMS.0 Installation and Configuration Guide for UNIX 93 . Custom or Expand Installation Finishing a system installation 5 The installation program will validate your system and install BusinessObjects Enterprise in the specified directory.

5 Custom or Expand Installation Finishing a system installation 94 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX .

Web Applications Installation 6 .

5 is installed by default when you install the Web Tier Components. facilitates OLAP view requests and manages session state information for users. The "Features" screen is displayed. translates cached files to DHTML.6 Web Applications Installation Performing web tier installations Performing web tier installations The web tier installation type installs the appropriate web tier components on the machine running your web application server. The web application server processes scripts.0 setup program. The first step is done on the machine where the BusinessObjects Enterprise components will reside.0 Installation and Configuration Guide for UNIX . Note: • It is best practice to install the server and client components to verify connectivity. 2. Tip: Deselect the Tomcat subfeature if you want to use your existing web application server. You will need user account and port information to configure your web application server through the BusinessObjects Enterprise 3. Scroll down and use the spacebar to deselect the field. Expand Web Tier Components to specify which features to install. 3. 4. Select or deselect Enable servers after installation. 1. A distributed installation has two stages. Press Enter to submit your selection. The second step is to install the Web Tier Components on the machine where the web server is installed. This option is selected by default. To perform a web tier installation The Installation Type screen in the following procedure appears after you have completed the initial set up of the BusinessObjects Enterprise installation. 96 BusinessObjects Enterprise XI 3. Select Install Web Tier features and press Enter. communicates with report and cache servers. • Java SDK 1.

leave the field empty. or specify a deployment option. 1.0 Installation and Configuration Guide for UNIX 97 . you will now either configure the Tomcat applications server. After selecting what web tier features to install. BusinessObjects Enterprise XI 3.0 applications including Central Management Console. • Tomcat: If you do not have an existing web application server. Dashboard and Analytics. Specify the machine name where the CMS is installed in CMS Hostname. you need to provide information on the CMS to which the feature will be clustered. It is composed of an implementation of web services that can be deployed with BusinessObjects Enterprise XI 3. you can choose to install Apache Tomcat 5.5. Press Enter. Related Topics • Beginning your installation on page 55 Features available in a web tier installation • BI Platform Web Components: This includes all components used to run BusinessObjects XI 3.0. Specify the password required for Administrator access to the CMS in Existing CMS Administrator Password. Web Applications Installation Performing web tier installations 6 You must now cluster the selected components to an existing Central Management Server (CMS). To cluster web tier features to a CMS You need to be able to connect to a running Central Management Server (CMS). Modify the value if your CMS is using another port. • BusinessObjects Enterprise Web Services: This is a component of Business Objects Enterprise built for developers. and Voyager. Accept 6400 as the Port if that is number used by the CMS. 3. Note: If no password is required. Depending on your selection in the "Features" screen. This web service implementation provides an API/WSDL which simplifies the process of developing applications. Infoview. 2.

Deployment option When to use Install Tomcat. Use the installer to specify to install Tomcat as your application server. Related Topics • To start the installation on page 102 • To configure your existing web application server on page 99 • To configure the Tomcat installation on page 98 To configure the Tomcat installation If you chose to install the Tomcat application server. or choose to work with your existing web application server. deploy web applica. If you have selected the third option you can start the installation process. Use existing Java application If you have an existing supported web ap- server. you will now have to configure the web application server. Use existing Java application If you have an existing supported web ap- server. the "Please enter port numbers for the Tomcat installation screen" is displayed. do not deploy web plication server and you want to manually applications deploy the web applications. • Select one of the options listed below and press Enter.0 Installation and Configuration Guide for UNIX . 98 BusinessObjects Enterprise XI 3. you need to provide information on the web application server that will work with your BusinessObjects applications such as InfoView and the Central Management Console (CMC).plication server and you want to automati- tions cally deploy the web applications. the Central Management Console and other web application servers. If you have selected either the first or second option.6 Web Applications Installation Performing web tier installations To select a web application server configuration option As part of the installation setup. deploy web If you do not have an existing web applica- applications tion server. You must configure the server to use InfoView.

04.0 Installation and Configuration Guide for UNIX 99 . Related Topics • To start the installation on page 102 To configure your existing web application server You must select the Use existing Java application server. select Other. • Tomcat 5. BusinessObjects Enterprise XI 3. you can now configure the server on a separate screen. You can now start the installation process. If you selected one of the supported servers. Select the server type before configuring your web application server.1 • Oracle Application Server 10g R3 • Other If your existing web application server is SAP Application Server 7.5 • WebLogic 10 • WebLogic 9 • WebSphere 6. You can either choose to accept the default port numbers or provide new values for the following: Required port numbers Receive HTTP requests Redirect jsp requests Shutdown hook 2. Web Applications Installation Performing web tier installations 6 1. Press Enter. 1. deploy web applications option to view the "Select a Web Application Server to deploy to" screen. you can begin the installation.0 or JBoss 4. 2. If you select Other. Provide the requested configuration details for your web application server and press Enter. Select your existing web application server from one of the following options and press Enter.

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

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

6 Web Applications Installation Performing web tier installations Web application Information required for installation setup server Oracle Application • Admin port: Administration port of the application server . Review the installation directory specified on the screen. 102 BusinessObjects Enterprise XI 3. you will still have to specify the username and password to access the server. .1.0 Installation and Configuration Guide for UNIX .domain. • Instance to install to: Name of the current web application server instance (for example “ home”). • Application server Installation directory: The directory where the web application server is installed (for example /prod uct/10. 1.xml file. • Group Id: Name of the server group to which the target application belongs (for example "Default_group"). Related Topics • To start the installation on page 102 To start the installation You are now ready to start the installation.mandatory for Oracle 10g R3. • Server Name: Name of the target application server (for example "myserver. • Admin is secure (y/n): Select this option only if you want Secure Sockets Layer (SSL) as part of the deployment. • Admin login: User name with administration rights to the application server .manda- Server 10g R3 tory for Oracle 10g R3 (for example “6003”) . • Admin password: Password for account with administration rights to the application server .com").mandatory for Oracle 10g R3. Note: If Admin is secure is not selected.3/OracleAS_1).This should be the Re- quest port of the <notifi-cation-server> element in the opmn. Note: To modify the directory you would need to press [Ctrl-B] several times until you reach the screen where you specify the installation directory.

Press Enter to start the installation. however. use the ccm. the setup program script prompts you to run the BobjEnterprise120 script after it is finished. BusinessObjects Enterprise XI 3.sh script. The BobjEnter prise120 script copies the run control scripts to your /sbin/rc# directories. you must have root privileges to run the se tupinit. When the new installation is finished. these run control scripts start/stop the BusinessObjects Enterprise servers on system startup/shutdown. Related Topics • Using ccm. To control the servers manually. you must log on using a normal account. The installation program will validate your system and install BusinessObjects Enterprise in the specified directory.sh script. After installation. Web Applications Installation Performing web tier installations 6 2. the setup program starts the servers as daemons and then enables each server that is registered with the CMS.0 Installation and Configuration Guide for UNIX 103 .sh to start the BusinessObjects Enterprise servers on page 126 Finishing a system installation If you chose to perform a system installation. This script copies the BobjEnterprise120 to the /sbin/rc# directory. Note: To run the system installation. When implemented.

6 Web Applications Installation Performing web tier installations 104 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX .

Silent Installation 7 .

The file is generated once the installation setup program is ready to start the installation.0 Installation and Configuration Guide for UNIX .7 Silent Installation Overview Overview There are two methods for running BusinessObjects Enterprise installations for UNIX directly from the command line: • Silent installation using a response file . This method does not allow for the same level of customization provided when using a response file.sh command. The silent installation allows you to specify parameters for running the . You can also integrate the scripts and commands into your own installation scripts. These installation types are particularly useful when you need to perform multiple installations. you can write installation settings to a specified response file. Related Topics • Performing a scripted installation on page 106 • Performing a silent installation on page 117 Performing a scripted installation While setting up an installation process on UNIX. as you can save time and avoid being prompted for information by the installation setup program./install. The scripted installation requires you to specify a response file.referred to as a scripted installation in this guide • Silent installation specifying parameters directly on the command line Both methods can be used to automate installations across multiple machines. The response file supports all three BusinessObjects Enterprise installation types available for UNIX: • New • Custom or Expand • Web Tier 106 BusinessObjects Enterprise XI 3. Note: The silent installation without the response file is not recommended for custom installations.

Mount the device that contains the installation files. In the command line type . If the parameter is not specified. 1. BusinessObjects Enterprise XI 3. Press Enter to launch the installation setup program. Related Topics • Running the product distribution directly from a CD on page 54 To run a scripted installation You need to have a response residing in a known directory. Note: If you run the installation script without copying the files to a temporary location. These settings are recorded in the response file. Follow the onscreen instructions to enter your preferred installation settings until you reach the final screen of the setup program. 5. 2.sh -w responseFilePath Note: When specifying responseFilePath make sure you include the name of the file you want to generate./install.sh. Press [Ctrl-X] to abort the installation setup once you reach the final screen in the installation setup program./install. the local server name will be used by default. 3. Select Ctrl-X to abort the installation setup once you reach the final screen in the installation setup program. . To create a response file 1. Mount the device that contains the installation files. The MACHINE NAME parameter must be specified in the response file if you are replicating an installation. You can access the response file from the directory you specified in step 2.0 Installation and Configuration Guide for UNIX 107 . -w and the file path the response file you want to generate. you will be prompted to specify a temporary location for the installation. Silent Installation Performing a scripted installation 7 Tip: You do not start the installation process to generate the response file. 4.

sh -r response. The source directory must point to the location of DISK_1 in the installation CD.7 Silent Installation Performing a scripted installation Note: If you run the install script without copying the files to a temporary location. 2.0 Installation and Configuration Guide for UNIX . the CD directory setting in the response file will be used. In the command-line type the following information: install. The setting overrides MACHINENAME the local server name. Related Topics • Copying the product distribution to your machine on page 54 Scripted installation parameters The table below lists the most common parameters used in BusinessObjects Enterprise installation scripts. If not specified.sh and the -w parameter. To change the listed parameters. Press Enter to launch the installation./install. Parameter Description Name of the machine on which to run the scripted installation. • -s <SOURCEDIR> This optional command specifies the location of the cd directory. it is recommended that you create a new response file using . • -I <INSTALLDIR> Specifies the installation directory for the scripted installation. 3. the local machine name is used.ini -I /installDirectory/ -s /cd/setup/DISK_1/ • -r <filename> Specifies the name of the response file you want the installation setup to read for installation parameters. If not specified. MACHINENAME="mymachine" 108 BusinessObjects Enterprise XI 3. These parameters are saved in a file which is used to run scripted installations of BusinessObjects Enterprise on UNIX. you will be prompted to specify a temporary location for the install.

• en=English • chs=Simplified Chinese • cht=Traditional Chinese • de=German • es=Spanish • ko=Korean BOBJELANG • nl=Dutch • jp=Japanese • pt=Portuguese • sv=Swedish • ru=Russian • fr=French BOBJELANG="en" Specifies the product activation keycode for the product to be installed. LICENSEDIR LICENSEDIR="<INSTALLDIR>/<LI CENSEDIR/" The language setting used for the instal- lation setup.0 Installation and Configuration Guide for UNIX 109 . Silent Installation Performing a scripted installation 7 Parameter Description Path of the bobje directory automatically BOBJEDIR setup in the installation directory. BOBJELICENSEKEY BOBJELICENSEKEY=XXXXX-XXXXXXX- XXXXXXX BusinessObjects Enterprise XI 3. CDDIR="<CD>/BusinessOb jects/DISK_1" Path to the directory containing the prod- uct license. BOBJEDIR="<INSTALLDIR>/bobje/" Path to the DISK_1 directory on the distri- bution CD. This path defaults to the CD CDDIR directory.

This parameter supports the follow- ing options: • new INSTALLTYPE • custom • webtier INSTALLTYPE="new" Specifies a comma-delimited list for the BusinessObjects Enterprise installer op- erating modes. This parameter supports the following options: • install INSTALLMODE • modify • remove • integrated • interactive INSTALLMODE=interactive. BOBJEINSTALLLOCAL=“user” 110 BusinessObjects Enterprise XI 3.install Specifies the name of the local server LOCALNAMESERVER LOCALNAMESERVER=“myservername” Specifies to perform either a user or sys- BOBJEINSTALLLOCAL tem installation.7 Silent Installation Performing a scripted installation Parameter Description The product id key .same as the BOB PIDKEY JELICENSEKEY PIDKEY =XXXXX-XXXXXXX-XXXXXXX Specifies the type of installation to per- form.0 Installation and Configuration Guide for UNIX .

BOBJEUSERNAME=“username” Specifies to either install or not to install INSTALLTOMCAT Tomcat. INSTALLTOMCAT=“yes” Specifies the connection port for the CONNECTORPORT Tomcat server.0 Installation and Configuration Guide for UNIX 111 . REDIRECTPORT=“15034” Specifies the shutdown port for the Tom- SHUTDOWNPORT cat server. CONNECTORPORT=“15037” Specifies the redirection port for the REDIRECTPORT Tomcat server. Silent Installation Performing a scripted installation 7 Parameter Description Specifies the language packs to install. • en=English • zh_CN=Simplified Chinese • zh_TW=Traditional Chinese • de=German • es=Spanish LANGPACKS_TO_INSTALL • ko=Korean • nl=Dutch • jp=Japanese • pt=Portuguese • sv=Swedish • ru=Russian • fr=French LANGPACKS_TO_INSTALL=“en fr” Specifies the Business Objects Enterprise BOBJEUSERNAME username. Each language pack is specified in the short format and is separated by a space. SHUTDOWNPORT=“15024” BusinessObjects Enterprise XI 3.

AS_ADMIN_USERNAME="admin" 112 BusinessObjects Enterprise XI 3. AS_ADMIN_PORT="8080" Specifies the account name used by the administrator to access the web applica- AS_ADMIN_USERNAME tion server. • Use tomcat55 for Tomcat • Use oas1013 for Oracle Application Server 10g R3 AS_SERVER • Use weblogic9 for WebLogic 9 • Use weblogic10 for WebLogic 10 • Use websphere6 for WebSphere 6.7 Silent Installation Performing a scripted installation Parameter Description Specifies the path of the application server directory if the server is being in- stalled. The path is automatically set us- AS_DIR ing the installation directory.0 Installation and Configuration Guide for UNIX .1 AS_SERVER=“tomcat55” Specifies the name of the current web AS_INSTANCE application server instance. AS_DIR=“<INSTALLDIR>/bobje/tom cat/” Specifies the name of the application server being installed. AS_VIRTUAL_HOST="hostname" Specifies the port used by the web appli- AS_ADMIN_PORT cation server. AS_INSTANCE="localhost" Specifies virtual host to which the applica- AS_VIRTUAL_HOST tion must be bound.

AS_ADMIN_PASSWORD="pass" Specifies is administrator credential must be passed to access the web application AS_ADMIN_IS_SECURE server. specifies the name CLUSTER_NAMESERVER of the CMS .0 Installation and Configuration Guide for UNIX 113 . AS_ADMIN_IS_SECURE="true" Specifies the action to perform on the application server. CMSCLUSTER=“no” If clustering to a CMS. specifies the port CLUSTERPORTNUMBER number used by the CMS. CLUSTER_NAMESERVER=“name” If clustering to a CMS. CLUSTERPORTNUMBER=“6400” BusinessObjects Enterprise XI 3. This setting only valid for Web- Sphere 6 and Oracle. Silent Installation Performing a scripted installation 7 Parameter Description Password used by the administrator ac- count to access the web application AS_ADMIN_PASSWORD server. The available options are: • deploy WDEPLOYACTION • predeploy • none WDEPLOYACTION=“deploy” Specifies whether or not to cluster to an CMSCLUSTER existing CMS.

0 Installation and Configuration Guide for UNIX . CMSPORTNUMBER=“14000” Specifies the password used to connect CMSPASSWORD to the CMS. CMSNAMESERVER CMSNAMESERVER=“servername” Specifies the port number used to com- CMSPORTNUMBER municate with the CMS.7 Silent Installation Performing a scripted installation Parameter Description Specifies the type of database used by the CMS. SIANODENAME=“name” 114 BusinessObjects Enterprise XI 3. CMSPASSWORD=“password” Specifies the node name for the Server SIANODENAME Intelligence Agent (SIA). SERVICENAME SERVICENAME=“BOE953” Specifies the username used to connect- DATABASEUID ed to the database. DATABASEUID=“username” Specifies the password used to connect- DATABASEPWD ed to the database. DATABASEPWD=“password” Specifies the name of the CMS server. The available options are: • MySQL • DB2 DBTYPE • Oracle • Sybase DBTYPE=“MySQL” Specifies the service name for the CMS.

Silent Installation
Performing a scripted installation 7
Parameter Description

Specifies the port used by the Server In-
SIAPORTNUMBER telligence Agent.
SIAPORTNUMBER=“14090”

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

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

Specifies the port number used to com-
SERVICEPORT municate with the MySQL database.
SERVICEPORT=“15036”

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

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

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

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

Specifies the port number used to com-
SERVICEPORT_AUDIT municate with the auditing database.
SERVICEPORT_AUDIT=“12133”

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX 115

7 Silent Installation
Performing a scripted installation

Parameter Description

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

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

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

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

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

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

116 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Silent Installation
Performing a silent installation 7
Parameter name
PRODUCTID_NAME
BOBJEVERSION
PRODUCTID_VER
FUNCTION
LANGUAGES_TO_INSTALL
EXPANDSERVERS

Related Topics
• To create a response file on page 107

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

This type of installation is particularly useful when you need to perform
multiple installations. You can also use the silent installation script in your
own scripts. For example, if your organization uses scripts to install software
on machines, you can add the silent BusinessObjects Enterprise installation
command to your scripts.

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

The following example would perform an English new user installation with
the following configuration:
• BusinessObjects Enterprise
• Tomcat
• MySQL
• Auditor

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX 117

7 Silent Installation
Performing a silent installation

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

-DBTYPE MySQL -SERVICENAME boe -INSTALLMYSQL yes -DATABASEUID

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

Note: The example uses the most common parameters. You can choose
any number of valid parameters, but it is good practice to keep the silent
installation as simple as possible.
Note that when you run a silent installation, you need to run the command
once for each CD, but you only need to provide the full list of options for the
first CD. For example, if the CDs are on different drives, the commands could
look like the following:
./install.sh -s /mnt/cd1 -INSTALLDIR /mymachine/
BOBJ/Enterprise120 -BOBJELICENSEKEY 00000-0000000-0000000-0000

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

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

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

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

Note: Parameter values are case-sensitive.

118 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Silent Installation Performing a silent installation 7 Installation parameter Description The location of the CD used to run the installation. -s /mnt/CD1/ Specifies the directory where you want to install the new BusinessObjects Enterprise components. For example. -INSTALLDIR /BOBJE/En terprise120. The options are “yes” and “no”. the default setting is “no”. -INSTALLDIR filepath Replace filepath with the full path for the installation directory. 0000000-0000 Enables you to install Dashboard and Analytics servers without a keycode.0 Installation and Configuration Guide for UNIX 119 . Replace languagecode with a language code for one of the supported languages: • en=English • zh_CN=Simplified Chinese • zh_TW=Traditional Chinese -clanguage code • de=German • es=Spanish • ko=Korean • nl=Dutch • jp=Japanese • ru=Russian • fr=French Specifies the Server Intelligence Agent (SIA) node -SIANODENAME name to use for the installation. BusinessObjects Enterprise XI 3. -BOBJELICENSEKEY Required to activate the product license for your 00000-0000000- product. This option determines the language for the instal- lation. -DASENABLED Note: The Dashboard and Analytics servers will be disabled until you enter an appropriate keycode through the Central Management Console (CMC). Replace filepath with the full path for the CD drive -sfilepath or other installation source directory. For example.

See the mymenu. If not specified. Specifies the type of installation. Specifies the name of an existing CMS to use for -CMSNAMESERVER either a custom or web tier installation. Each product must be separated by a comma. Note that this cannot -f be used in combination with the -x option. Specifies whether to perform a user or a system -BOBJEINSTALLLOCAL installation. user is the default.7 Silent Installation Performing a silent installation Installation parameter Description -SIAPORTNUMBER Specifies the port used by the SIA.xml tion with the -f option. See the mymenu. 120 BusinessObjects Enterprise XI 3. Specifies which specific products to manually en- able. -ENABLEMP For a custom installation this setting is used to en- able those products typically not installed in a new installation.0 Installation and Configuration Guide for UNIX .xml file in the setup directory on DISK_1 for a full list of features. the default is 6400. Specifies the administrator password for an existing -CMSPASSWORD CMS to use in either a custom or web tier installa- tion. Note that this cannot be used in combina- -xmymenu. Specifies the port number for the Central Manage- -CMSPORTNUMBER ment Server.xml file in the setup directory on DISK_1 for a full list of features. The possible val- ues are: -INSTALLTYPE • new • custom • webtier This parameter is followed by a comma-separated values (CSV) string of features that you do not want to install. The options are user or system. This parameter is followed by CSV string of fea- tures that you want to install.

you need to specify the type of database you want to use. it defaults to no. When the -IN- -MYSQLROOTPWD STALLMYSQL option is set to yes. you must also specify the -MYSQLROOTPWD option. Specifies the name of the machine hosting the -MYSQLHOSTNAME MySQL server. Specifies the service name used to connect to the -SERVICENAME Central Management Server database.0 Installation and Configuration Guide for UNIX 121 . If this option is not speci- fied. This option cannot -DATABASEUID be set to root if the -INSTALLMYSQL option is set to yes. Specifies if the an auditing database will be config- ured the during your installation setup. Silent Installation Performing a silent installation 7 Installation parameter Description When installing a Central Management Server. The two -AUDITINGENABLED options are yes and no. BusinessObjects Enterprise XI 3. Specifies the password used to connect to the -DATABASEPWD Central Management Server database. If this option is not specified. Specifies the user ID used to connect to the Central Management Server database. This is re- quired only for MySQL databases. The options are yes or no. no is the default. it defaults to blank. Specifies the password used for the root account when setting up the database. you can specify whether or not to install and configure -INSTALLMYSQL a new MySQL database. Specifies the port number used to connect to the -SERVICEPORT Central Management Server database. Possible values include: -DBTYPE • Oracle • DB2 • Sybase • MySQL When installing a Central Management Server.

Specifies whether or not to cluster the Central Management Server with an existing CMS.7 Silent Installation Performing a silent installation Installation parameter Description Modifies the name of the MySQL auditing -SERVICENAME_AUDIT database. 122 BusinessObjects Enterprise XI 3. Specifies the password for the auditing database -DATABASEPWD_AUDIT server. Specifies an existing auditing database type from one of the following options: • Oracle -DBTYPE_AUDIT • DB2 • Sybase • MySQL Specifies the port for the MySQL auditing database -SERVICEPORT_AUDIT server.yes is the default. the default name of BOE120_Audit will be used Use this parameter to pass the user ID for the au- -DATABASEUID_AUDIT diting database. Specifies whether to reinitialize the Central Man- -REINIT agement Server database. Specifies the host name for the MySQL server for -MYSQLHOSTNAME_AUDIT your auditing database. Specifies the port number used by the Sybase au- -SYBASEPORT_AUDIT diting database. Note: This option is used for a custom installation. Specifies the name of the machine hosting the -SYBASEHOSTNAME_AUDIT Sybase auditing database.0 Installation and Configuration Guide for UNIX . otherwise. no is the default. The options are yes or no. The -CLUSTERCMS options are yes or no.

-TOMCATSHUTDOWNPORT The default is 8005. then you need to specify the port number of the CMS you want to cluster with. The port number that Tomcat uses to shut down. The port number that Tomcat uses to redirect.0 Installation and Configuration Guide for UNIX 123 . For a -CLUSTER_NAMESERVER custom installation. The default is 6400. Specifies the port number of the Central Manage- ment Server for the system you are expanding. Specifies if Tomcat is to be installed as the web -INSTALLTOMCAT applications server. The -TOMCATCONNECTORPORT default is 8080. BusinessObjects Enterprise XI 3. For a custom installation. if -CLUSTERPORTNUMBER the -CLUSTERCMS option is set to yes. if the -CLUSTERCMS option is set to yes. The default value is no. The default is 6400. The -TOMCATREDIRECTPORT default is 8443. The port number that Tomcat uses to connect. then you need to specify the name of the CMS you want to cluster with. Silent Installation Performing a silent installation 7 Installation parameter Description Specifies the name of the Central Management Server for the system you are expanding.

7 Silent Installation Performing a silent installation 124 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX .

After Installing BusinessObjects Enterprise 8 .

Select Start Server. Start the Server Intelligence Agent (SIA) by typing the following command: . BusinessObjects Enterprise web applications (e. CMC) and the BusinessObjects Enterprise SDK are installed. Select the server you want to start. see the BusinessObjects Enterprise Administrator's Guide. The following information is included only as a reference. 7.g. Go to the bobje directory that was created by the installation: cd <INSTALLDIR>/bobje 2. For example http://<SERVERNAME>:<PORTNUMBER>/CmcApp 4. and deployed for you.sh to start the BusinessObjects Enterprise servers The ccm.sh to start the BusinessObjects Enterprise servers Using ccm.sh script provides you with a command-line interface to the various BusinessObjects Enterprise server components. Log on to the CMC by providing your BusinessObjects Administrator credentials.8 After Installing BusinessObjects Enterprise Using ccm. Navigate to the "Servers" page. To manually start and enable servers 1. configured. For more information about this script and others that are installed on your system. 6.sh -start sia 3. Post install component deployment When you install Tomcat as part of your BusinessObjects Enterprise installation. 126 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX . InfoView./ccm. The server should now start. the installation setup program starts and enables servers automatically. 5. In BusinessObjects Enterprise. Open a web browser to the URL of your Central Management Console (CMC) deployment on your web application server.

and adding users and groups. you must perform additional system configuration. You can either deploy the components manually or use the wdeploy tool. and keep track of published reports.0 Installation and Configuration Guide for UNIX 127 . in your BusinessObjects Enterprise Administrator's Guide. and calendars that users leverage for their performance management analysis. sets. you need to do the following: • Create the performance management repository – this repository stores the metrics. . starting servers. Related Topics • BusinessObjects Enterprise WAR files on page 185 • How to use wdeploy on page 151 • To manually deploy web applications on page 188 Setup for performance management Before users in your organization can start working with performance management. Note: If you have a firewall between the machine running your web application server and your other BusinessObjects Enterprise servers. See the section on how to configure firewalls. BusinessObjects Enterprise XI 3. schedule. see the architecture chapter of the BusinessObjects Enterprise Administrator's Guide. • Define system users – this enables the performance management application engines. The BusinessObjects Enterprise SDKs are used by many BusinessObjects Enterprise components and are also used to simplify the development of custom BusinessObjects Enterprise applications. goals. For more information about the system architecture of an installation of BusinessObjects Enterprise. If you do not install Tomcat when you install BusinessObjects Enterprise. The Central Management Console (CMC) allows you to perform user and server management tasks such as setting up authentication. • Define connections to the metrics universes and push those universes to the performance management repository – this makes the metadata for measures and dimensions available to users for metric creation. After Installing BusinessObjects Enterprise Setup for performance management 8 InfoView is a web-based interface that end users access to view. these components must configured and deployed before you use them.

and the InitConfig. On your performance management server. To verify performance management servers 1.properties file. A drop-down list is displayed. Troubleshooting starting performance management If. Make sure that all servers are enabled. and then click Enable. and then click Start. and then click Servers.0 Installation and Configuration Guide for UNIX . you receive an error message saying that you cannot connect to performance management. If a server is not running. 3. then click Open.8 After Installing BusinessObjects Enterprise Setup for performance management To set up performance management 1. 3.prop erties file and verify that the Initialization user name and password match those in the CMS. To verify the Initialization User 1. 2. this may mean one of the following: • Some of the performance management servers are stopped or disabled. select the check box next to the server name. Verify that all the performance management servers are started. InfoView. Select Dashboard & Analytics Setup. 4. Log into InfoView. select the check box next to the server name. • The Initialization User that creates the performance management server proxies may be defined inconsistently in the CMS. The Dashboard & Analytics Setup page is displayed. when you launch performance management. Follow the on-screen instructions. 128 BusinessObjects Enterprise XI 3. 2. open the InitConfig. Log into the Central Management Console (CMC). If a server is not enabled.

7. BusinessObjects Enterprise XI 3. Log into the Log into the Central Management Console (CMC). You need to restart the performance management servers. it is recommended that you do not provide a real user ID for the initialization user. After Installing BusinessObjects Enterprise Setup for performance management 8 This file is at: <INSTALLDIR>/bobje/performance_management_120 The strings to search for are: • initialization. 5. 6. click Servers > Start Servers to restart all servers. and then check the name of the initialization logon user in the Change initialization logon user section is the same as the user name specified in the InitConfig.properties is listed among the users. If you are using performance management from a client machine . and then click Users. click Settings > Rights and check that the initialization user has the appropriate rights. Click the Performance Management tab. 3. From the CMC home page.different from the machine hosting the performance manager server .Password= 2. The default user ID is PMUser.User= • initialization.prop erties file. Check that the user defined in the InitConfig. and then click the Preferences button on the InfoView toolbar.0 Installation and Configuration Guide for UNIX 129 .you need to restart your computer. From the CMC home page. Note: For security reasons. 4. Log into InfoView.

0 Installation and Configuration Guide for UNIX .8 After Installing BusinessObjects Enterprise Setup for performance management 130 BusinessObjects Enterprise XI 3.

Language Packs on UNIX 9 .

If a language pack corresponding to the locale of the operating system is not found.0 Installation and Configuration Guide for UNIX . You can install as many different language packs as you want. reports. 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. BusinessObjects Enterprise products fall back to using the default English language. English. and help. it must be restarted in order for the change to take effect. English language fall-back In the event of a localization error. if the Business Intelligence Modeler is running at the time of the change. The default language pack. Product locale changes Product Locale changes are immediately reflected in the current product's interface. An individual language is known as a locale. 132 BusinessObjects Enterprise XI 3. Selecting a language Once installed. BusinessObjects Enterprise defaults to using the locale of the installed operating system. or uninstalled language pack. setting the Crystal Report Designer product locale to Japanese will cause the Business Intelligence Modeler client to also display in Japanese. the default English is used. For example. If a preferred language has not been set in the Product Locale drop-down. BusinessObjects Enterprise products detect the existence of the language pack. Command-line utilities use the LANG environment variable to determine which language to use. or under the Options dialog box on the toolbar or application menu in other BusinessObjects Enterprise products. corrupted. such as a missing. However. Where multiple client applications are installed.9 Language Packs on UNIX About language packs About language packs A language pack is a resource package that gives a BusinessObjects Enterprise system the ability to interact with users in a specific language. is always installed. the selected Product Locale is only displayed when client is next started.

Because of this fall-back system. Note: An error message will be displayed if a language pack detects that it is incompatible with a previously installed version of BusinessObjects Enterprise. Installing language packs on UNIX systems Language packs can be installed either during the initial installation of BusinessObjects Enterprise. regardless of which language is in use. Ctrl+S is always mapped to the Save command. rather than as German in English or Allemand in French. For example.businessobjects. In the event of an operational problem with a language pack. Additional languages can also be installed onto an existing system by downloading the appropriate language pack from the Business Objects support web site at http://technicalsupport. BusinessObjects Enterprise will default back to English localization. rather than the currently employed language. or post-install using a dedicated language pack installer. English is the default option during the installation of BusinessObjects Enterprise. regardless of the localized name for the Save function. Language Packs on UNIX Installing language and complex deployments 9 Each language listed in the Product Locale drop-down is displayed in its native localization. BusinessObjects Enterprise XI 3. English cannot be deselected as an installable option during the installation of BusinessObjects Enterprise. Installing language and complex deployments If your organization uses a BusinessObjects Enterprise deployment with more than one server.0 Installation and Configuration Guide for UNIX 133 . you will need to deploy language packs to each server individually. For example. the German language pack is always displayed as Deutsch. Note: Application shortcut keys are language neutral and do not change. The installer is a script that adds the localized language resources to your Business Objects software deployment.com. but administrators can opt to install any or all of the other available languages.

your BusinessObjects Enterprise server must be running and patched to the required revision level. Note: Language packs do not require a keycode. Replace LANGUAGE with the ISO code of the language you are installing.businessobjects. Press Enter after you have confirmed the location of the BusinessObjects Enterprise install directory. Locate the language pack to install under BUSINESS_OBJECTS_DIS TRIBUTION_CD_DIR/langs/LANGUAGE/DISK_1.com/documentation/supported_platforms. 5.com. 1. Once the installation is complete. Enter the CMS hostname.businessobjects. 2. 134 BusinessObjects Enterprise XI 3. Alternatively. and administrator password into the labeled fields and press Enter. language packs can be downloaded from the Business Objects technical support site at http://technicalsupport. Press y to accept the license agreement.sh script with the first argument set to the location of the BusinessObjects Enterprise installation directory. You will be asked for CMS administrator credentials. 6. To install language packs Before installing a language pack. you will be able to choose the installed language from the Options dialog window in BusinessObjects Enterprise applications. Run the install. 3. If any part of your BusinessObjects Enterprise deployment is not patched to the required software version. the language pack installation will abort and must be reapplied after the system has been patched to the correct level.sh /opt/bobj 4.9 Language Packs on UNIX Locating language packs Locating language packs Language packs can be found in the langs folder of the BusinessObjects Enterprise for UNIX distribution package. For example: install. Open the Central Management Console (CMC) and ensure that the server processes are running. Please review the requirements for language packs at the Business Objects customer support site: http://sup port. port number.0 Installation and Configuration Guide for UNIX .

Language Packs on UNIX Installing language packs across a BusinessObjects Enterprise deployment 9 Note: • All fix packs or other updates to BusinessObjects Enterprise released on a date after the language pack release date must be re-applied to ensure that updated functionality is maintained. BER CMS CMSPASSWORD CMS admin pass.sh BUSINESS_OBJECTS_HOME_DIR INSTALLMODE=silent CMSNAMESERVER=CMS_HOSTNAME CMSPORTNUMBER=PORT_NUMBER CMSPASSWORD=CMS_PASSWORD Replace BUSINESS_OBJECTS_HOME_DIR with the full path of your BusinessObjects Enterprise installation. Parameter Expected argu. The following table details each of the parameters used by install_langpack. word BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX 135 .sh. The password for your CMS server. This is referred to as a silent installation. Installing language packs across a BusinessObjects Enterprise deployment You can install language packs with one command by specifying parameters on the command-line. The command-line syntax for a silent install is as follows: install_langpack. Description ment INSTALLMODE silent Switch to enable silent install mode CMSNAMESERV CMS Hostname Enter the name of your CMS ma- ER chine. CMSPORTNUM Port number for CMS port number. • Language packs must be re-installed after you have added or removed a component from your BusinessObjects Enterprise deployment. When parameters are supplied on the command-line the installation will not prompt for information.

/install_langpack. Run the uninstall_langpack.9 Language Packs on UNIX To uninstall language packs For example: $ .sh weblogic10 -Das_dir=/opt/bea/user_projects/domains/base_domain -Das_admin_port=7001 -Das_instance=AdminServer -Das_admin_username=weblogic -Das_admin_password=weblogic undeployall Followed by: wdeploy. You will find the uninstall_lang pack.sh /opt/bobj 136 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX .sh weblogic10 -Das_dir=/opt/bea/user_projects/domains/base_domain -Das_admin_port=7001 -Das_instance=AdminServer -Das_admin_username=weblogic -Das_admin_password=weblogic deployall For more information on using wdeploy. the following command runs undeployall for a WebLogic 10 server: wdeploy.sh script with the first argument set to the location of the BusinessObjects Enterprise installation directory. Related Topics • How to use wdeploy on page 151 To uninstall language packs 1. Open the Central Management Console (CMS) and ensure that all servers are running 2. use the wdeploy undeployall command to remove all web applications.sh /opt/bobje INSTALLMODE=silent CMSNAMESERVER=myserver1 CMSPORTNUMBER=6400 CMSPASSWORD=mypassword To uninstall language packs. see How to use wdeploy. Locate the language pack to uninstall.sh script in the setup folder of the language pack. then wdeploy deployall to re-deploy web applications without the language packs. For example: uninstall_langpack. For example. 3.

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX 137

9 Language Packs on UNIX
To uninstall language packs

138 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Maintaining your Installation

10

10 Maintaining your Installation
Uninstalling BusinessObjects Enterprise from UNIX

Uninstalling BusinessObjects Enterprise
from UNIX
Before you can remove BusinessObjects Enterprise from your UNIX machine,
you must run the AddOrRemovePrograms.sh script. The script is installed to
the directory of your installation and is used to add or remove
BusinessObjects Enterprise products or components.

This script stops all BusinessObjects Enterprise servers and processes. It
then deletes the files copied from the product CD during your original
installation of BusinessObjects Enterprise.

A BusinessObjects Enterprise installation creates a number of additional
files on your system. When you uninstall BusinessObjects Enterprise these
additional files and any files created by the system or by users after
installation will not be removed. The files that remain include log files created
by BusinessObjects Enterprise. These log files can be useful for diagnosing
problems with previous installations.

To uninstall BusinessObjects Enterprise

Before removing BusinessObjects Enterprise XI 3.0 from your UNIX system,
you should uninstall all language packs used by the installation.

To uninstall BusinessObjects Enterprise:
1. From the installation directory run ./AddOrRemovePrograms.sh.
The "Add or Remove Programs" screen is displayed.
2. Select BusinessObjects Enterprise XI 3.0 and press Enter.
The "Add Features or Uninstall Current Product"screen is displayed.
3. Select Uninstall Product and press Enter.
A confirmation screen is displayed.
4. Select Yes and press Enter.
The uninstallation process begins.

To completely remove all BusinessObjects Enterprise files, perform an rm
-Rf command on the bobje directory.

140 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

0 Installation and Configuration Guide for UNIX 141 . Select BusinessObjects Enterprise XI 3. You must run the AddOrRemovePrograms.0 and press Enter.sh. Run the following procedure if your current BusinessObjects Enterprise installation does not have the required performance management resources. you must have BusinessObjects Enterprise installed on a UNIX machine.sh script to add the performance management resources. 2. From the installation directory run . The "Add or Remove Programs" screen is displayed. To add performance management To add performance management resources. Specify the following information: Field name Description CMS Hostname The system name for the CMS host machine BusinessObjects Enterprise XI 3. The "Add Features or Uninstall Current Product" screen is displayed. 4. 1. Maintaining your Installation Adding performance management to your installation 10 If you performed a system installation./AddOrRemovePrograms. You are prompted to enter Central Management Server (CMS) connection details. Related Topics • To uninstall language packs on page 136 Adding performance management to your installation You can add performance management servers and binaries to your BusinessObjects Enterprise installation. Select Add Dashboards and Analytics Servers and press Enter. you must also delete the run control scripts from the appropriate /etc/rc# directories. The script is installed to the directory of your installation. 3.

10 Maintaining your Installation Adding performance management to your installation Field name Description CMS Port Port used by the CMS Existing CMS Administrator Pass. you will be prompted to provide the web application server configuration details. 6. Otherwise. You options are the following: • Tomcat 5.g.1 • Oracle Application Server 10g R3 • Other A configuration screen for your selected web application server is displayed. Web Application Information required for installation setup Server Apache Tomcat 5.5 • WebLogic 10 • WebLogic 9 • WebSphere 6. Provide the requested configuration details for your web application server. 5.0 Installation and Configuration Guide for UNIX . “localhost”). 142 BusinessObjects Enterprise XI 3.5 • Instance to install to: Name of the current web application server instance (e. skip to step 8.Administrator password used to access word the CMS If your previous installation was not configured to deploy web applications to a specific web application server. The table below summarizes the information required for each supported web application server. • Application server Installation directory: The directory where the web application server is installed (e. <INSTALLDIR>/wde ploy/appserver/Tomcat5520).g. Select your existing web application server and press Enter.

• Admin login: User name with administration rights to the application server .g. BusinessObjects Enterprise XI 3. Note: For WebLogic the directory is the domain root.g.g /bea/user_projects/do mains/base_domain). “ mserver1”). • Admin login: Password for account with administration rights to the application server .mandatory for Weblogic. “7001”). • Instance to install to: Name of the current web application server instance (e. • Instance to install to: Name of the current web application server instance (e.manda- tory for Weblogic (e.g. • Admin login: User name with administration rights to the application server . • Application server Installation directory: The directory where the web application server is installed (e. Maintaining your Installation Adding performance management to your installation 10 Web Application Information required for installation setup Server WebLogic 10 • Admin port: Administration port of the application server . WebLogic 9 • Admin port: Administration port of the application server .mandatory for Weblogic. “ mserver1”). “7001”). Note: For WebLogic the directory is the domain root.g. • Admin password: Password for account with administration rights to the application server . • Application server Installation directory: The directory where the web application server is installed (e.0 Installation and Configuration Guide for UNIX 143 .g.manda- tory for Weblogic (e.mandatory for Weblogic.mandatory for Weblogic. /bea/weblogic10/us er_projects/domains/base_domain).

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

If you have been provided with a new product keycode to activate performance management. • Server Name: Name of the target application server (e.mandatory for Oracle 10g R3. 8. “ home”). Maintaining your Installation Adding performance management to your installation 10 Web Application Information required for installation setup Server Oracle Application • Admin port: Administration port of the application server .g.3/Ora cleAS_1). • Admin login: User name with administration rights to the application server . • Group Id: Name of the server group to which the target application belongs (e. "Default_group"). 9. you will still have to specify the username and password to access the server. • Application server Installation directory: The directory where the web application server is installed (e. BusinessObjects Enterprise XI 3.g. /product/10. Once the verification is complete.g. Select Yes and press Enter. “6003”) .mandatory for Oracle 10g R3.1. The installation setup verifies the configuration details.g. 7. you can start the installation process. Press Enter to submit your configuration details.0 Installation and Configuration Guide for UNIX 145 .com").manda- Server 10g R3 tory for Oracle 10g R3 (e. you will have to provide the code to start the new servers. Note: If Admin is secure is not selected.This should be the Request port of the <notifi-cation-server> element in the opmn. • Admin is secure (y/n): Select this option only if you want Secure Sockets Layer (SSL) as part of the deployment. Specify the directory where the BusinessObjects Enterprise installation media is located.xml file. • Admin password: Password for account with administration rights to the application server . The Dashboard and Analytics resources are added to your installation. "myserv- er.g. • Instance to install to: Name of the current web application server instance (e. .domain.

0.10 Maintaining your Installation The installation log file Before users in your organization can start working with performance management.0 Installation and Configuration Guide for UNIX . • Define connections between the metrics used for performance management and the performance management repository.log. For more detailed information please consult the Performance Management Setup Online Help. Both files are saved under the following directory: <INSTALLDIR>/setup/logs/. • Specify which users can access performance management resources.12. and calendars used for performance management analysis. The log files can be used as a reference or to troubleshoot installation errors. 146 BusinessObjects Enterprise XI 3.0. The installation log file The installation log files contains information on all the parameter settings used in a BusinessObjects Enterprise installation. The name of the initial log files are BusinessObjects.log and BusinessOb jects.0.log file contains detailed information on installation and deployment.12. sets. you need to do the following: • Create a performance management repository – this repository stores the metrics. The BusinessObjects. goals.12. you need to do the following: After adding performance management to the installation.summary.

Post Installation Web Application Deployment 11 .

You can choose either of the following methods.04 X X 148 BusinessObjects Enterprise XI 3. The following table lists which deployment method is available for supported Web application server.0 installations by running all three supported installation types. 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.0 Oracle Application X X X Server 10G R3 JBoss 4.0 Installation and Configuration Guide for UNIX . The installation setup program guides you through an automated process for deploying the web applications and their required components only if you specify and configure your web application server during the installation setup. Installation setup Manual deploy- wdeploy program ment WebSphere 6. 1. Use the wdeploy program to automatically deploy the required components to the applications server.1 X X X WebSphere Com- X munity Edition 2.0 WebLogic 10 X X X WebLogic 9. You can also configure your web application servers and deploy web application components after installing BusinessObjects Enterprise.11 Post Installation Web Application Deployment Overview of post install deployment Overview of post install deployment You can deploy web applications for BusinessObjects Enterprise XI 3.2 X X X Tomcat 5.5 X X X SAP Application X X Server 7.

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

For detailed information on wdeploy see Deploying BusinessObjects Enterprise Web Applications using wdeploy. Related Topics • To deploy web applications on a remote machine on page 182 • Minimum rights for deploying web applications on page 18 Overview for using wdeploy The wdeploy command-line tool is included with BusinessObjects Enterprise to assist you in the command-line deployment of WAR files to your web application server. Prerequisites for using wdeploy To deploy BusinessObjects Enterprise web applications to a web application server. or to separate dynamic and static content for deployment onto de-paired web and web application servers (distributed mode). Note: If you have a firewall between the machine running your Java application server and your other BusinessObjects Enterprise servers. If the target web application server is hosted on a remote machine you will have to follow specific steps for preparing the wdeploy environment. see the “Architecture” chapter of the BusinessObjects Enterprise Deployment Planning Guide. including all required WAR files. This document is available at http://support.11 Post Installation Web Application Deployment Deploying with wdeploy Note: The wdeploy tool is also available as a stand-alone package on the product distribution media under the following directory: Collater als/Tools/wdeploy. you must perform additional system configuration. If the target web application server is on the same machine on which BusinessObjects Enterprise is installed you can proceed to run the wdeploy script.com. 150 BusinessObjects Enterprise XI 3. For more information about the system architecture of an installation of BusinessObjects Enterprise.businessobjects. See the section on how to configure firewalls in the BusinessObjects Enterprise Deployment Planning Guide. You can choose to deploy all web application resources together on a single web application server (standalone mode).0 Installation and Configuration Guide for UNIX . you must have BusinessObjects Enterprise installed.

Note: Parameters specified on the command-line override parameters in the wdeploy configuration file. It is recommended that you use the same user account for installing BusinessObjects Enterprise and your web application server. the specific configuration file for your web application server must be properly configured.2 is config. For example. Ensure that you have the minimum user rights for the web application server.weblog ic9. BusinessObjects Enterprise XI 3. The following table lists the required wdeploy configuration file details that must be specified for each supported web application server. This file is located in <INSTALLDIR>/deploy ment/.0 Installation and Configuration Guide for UNIX 151 . Post Installation Web Application Deployment Deploying with wdeploy 11 How to use wdeploy To use wdeploy. the configuration file for weblogic 9.

Note: Values for as_admin_username and as_admin_password must be set when as_admin_is_secure is true"). • as_admin_password: WebSphere administrator account password (for example "password"). • as_dir: WebSphere installation directory (for example “/opt/IBM/WebSphere/AppServer”).11 Post Installation Web Application Deployment Deploying with wdeploy Web application Required Configuration details server WebSphere 6. 152 BusinessObjects Enterprise XI 3. • as_admin_is_secure: Instructs wdeploy that WebSphere security is enabled (for example "false"). • as_instance: The name of your WebSphere application server in- stance (for example "server1"). • ws_instance: The name of the web server where the application is installed.535 files ("True" by default). Note: If as_admin_is_secure is false. • as_admin_username: WebSphere administrator account username (for example "administrator"). Note: If as_admin_is_secure is false. • enforce_file_limit: Indicates to wdeploy whether or not the web application server may encounter issues loading applications that contain more than 65.1 • as_admin_port: The SOAP Connector Port of the application server (for example “8880”).0 Installation and Configuration Guide for UNIX . in distributed mode (for example "server1"). • as_virtual_host: The virtual host to which the application must be bound (for example "default_host"). a value for as_admin_pass word does not need to be specified. a value for as_admin_user name does not need to be specified.

WebLogic 9. • as_service_key_value: Tomcat's Java parameters. • as_instance: The name of your WebLogic application server in- stance (for example "AdminServer"). • as_dir : Installation directory of the web application server (for ex- ample "/opt/tomcat). • as_admin_username: WebLogic administrator account username (for example "weblogic"). BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX 153 . • as_admin_password: WebLogic administrator account password (for example "weblogic").2 • as_admin_port: Administration port of the application server (for example "7001"). and the value of the registry key as_server_key. Tomcat 5. • as_admin_username: WebLogic administrator account username (for example "weblogic"). • as_dir: Weblogic domain directory (for example "/opt/bea/weblog ic10/user_projects/domains/base_domain").5 • as_instance : Name of the web application server instance currently used (for example "localhost"). • as_instance: The name of your WebLogic application server in- stance (for example "AdminServer"). • as_admin_password: WebLogic administrator account password (for example "weblogic"). • as_dir: Weblogic domain directory (for example "<IN STALLDIR>/bea/user_projects/domains/base_domain"). Post Installation Web Application Deployment Deploying with wdeploy 11 Web application Required Configuration details server WebLogic 10 • as_admin_port: Administration port of the application server (for example "7001").

0 STALLDIR>/SAP").xml (for example "6003"). • as_admin_username: the administrator username (for example "Administrator"). you will still have to specify the username and password to access the server. • as_instance: The name of your application server instance (for ex- ample "JC01"). • as_group_id: Name of the server group to which the target applica- tion belongs (for example "Default_group").1.11 Post Installation Web Application Deployment Deploying with wdeploy Web application Required Configuration details server SAP Application Serv.• as_dir: The location of your application server (for example "<IN- er 7.com"). • as_admin_is_secure: Instructs wdeploy that Oracle Application Server SSL security is enabled (for example "false"). Oracle Application • as_admin_port: Administration port of the application server. (for example "AS2").0 Installation and Configuration Guide for UNIX . • as_dir: Oracle Application Server installation directory (for example "/opt/product/10.3/OracleAS_1"). • as_sid: the SAP system id of the target instance. • as_admin port: the port number used by the server (for example "50104"). 154 BusinessObjects Enterprise XI 3. found in the <notifi cation-server> section of configuration file opmn. This Server 10g R3 is the request port of the notification server. • as_admin_password: Oracle Application Server administrator ac- count password (for example "oracle10g"). • as_admin_username: Oracle Application Server administrator ac- count username (for example "ocjadmin"). Note: If as_admin_is_secure is not enabled.domain. • as_admin_password: the administrator password (for example "password"). • as_appserver_name: Name of the target application server (for example "myserver. • as_instance: The name of your Oracle Application Server application server instance (for example "home").

log For example: wdeploy. For more detailed information on wdeploy see Deploying BusinessObjects Enterprise Web Applications using wdeploy. BusinessObjects Enterprise XI 3.sh weblogic9 deployall >> <INSTALLDIR>/mylog.0 Installation and Configuration Guide for UNIX 155 .0. only web applications deployed through the installer or wdeploy will be undeployed.sh <appserver> deployall >> <logfilename>.log Note: The <appserver> must be same as the web application server used in the configuration filename. • deploy/deployall: Predeploy then deploy web applications. Options for using wdeploy There are several actions that can be performed the wdeploy tool to control the web application deployment process: • predeploy/predeployall: Predeploy web applications. • undeploy/undeployall: Undeploy web applications.4.GA"). Run the wdeploy. • as_instance: The name of the JBoss application server instance (for example "default").sh script by opening command line console and typing the following: <INSTALLDIR>/deployment/wdeploy. Note: If you use the undeploy and undeployall commands. Tip: You can drop the deployable war files to non-default location by passing the parameter -Dwork_dir=your target location as part of the wdeploy command. Post Installation Web Application Deployment Deploying with wdeploy 11 Web application Required Configuration details server JBoss 4 • as_dir: The location of the JBoss application server (for example "opt/jboss-4. • deployonly/depolyonlyall: Deploy web applications.

Deploying to web application servers with wdeploy Deploying to WebSphere with wdeploy Using predeploy and predeployall The predeploy command creates resources and configuration files for a specific web application. For information on all options available for wdeploy see Deploying BusinessObjects Enterprise Web Applications using wdeploy. but does not deploy the web application to the web application server.11 Post Installation Web Application Deployment Deploying with wdeploy All other web applications can only be manually removed using the web application server's administrative console. then copies the WAR application to <IN STALLDIR>/deployment/workdir/WS_VERSION. The predeployall command performs the predeploy command for all web applications. Note: The wdeploy command does not create a log file.0 Installation and Configuration Guide for UNIX . 156 BusinessObjects Enterprise XI 3. and PORT with the port number used for either HTTP or HTTPS communication. To persist the output generated by wdeploy. the default context used for the CMC is CmcApp. For example: • http://WAS_HOSTNAME:PORT/INFOVIEW_CONTEXT • http://WAS_HOSTNAME:PORT/CMC_CONTEXT Replace WAS_HOSTNAME with the hostname or IP address of your web application server. After deploying web applications To verify the web application server configuration. redirect its output to a file using the greater-than redirect operator (>). make sure that InfoView and the Central Management Console can be launched in a web browser. The default root context used for InfoView is In foViewApp.

Example 1: using wdeploy deployonly to deploy a predeployed InfoView to WebSphere. wdeploy. wdeploy. wdeploy.sh websphere6 -Das_dir=/opt/ibm/WebSphere/AppServer -Das_instance=server1 -Das_virtual_host=default_host -Das_admin_port=8880 deployonlyall BusinessObjects Enterprise XI 3.sh websphere6 -Das_dir=/opt/ibm/WebSphere/AppServer -Das_instance=server1 -Das_virtual_host=default_host -Das_admin_port=8880 -DAPP=InfoViewApp predeploy Example 2: using wdeploy predeployall to predeploy all web applications to WebSphere.sh websphere6 -Das_dir=/opt/ibm/WebSphere/AppServer -Das_instance=server1 -Das_virtual_host=default_host -Das_admin_port=8880 predeployall Using deployonly and deployonlyall The deployonly command deploys a web application that is specifically configured for the target web application server.sh websphere6 -Das_dir=/opt/ibm/WebSphere/AppServer -Das_instance=server1 -Das_virtual_host=default_host -Das_admin_port=8880 -DAPP=InfoViewApp deployonly Example 2: using wdeploy deployonlyall to deploy all predeployed web applications to WebSphere.0 Installation and Configuration Guide for UNIX 157 . wdeploy. Post Installation Web Application Deployment Deploying with wdeploy 11 Example 1: using wdeploy predeploy to predeploy InfoView to WebSphere. The deployonlyall command performs the deployonly command for all web applications.

all web applications to WebSphere. Running deploy is equivalent to running a predeploy command followed by a deployonly command. then deploy. wdeploy. The undeployall command performs the undeploy command for all web applications. wdeploy. The deployall command performs the deploy command for all web applications.sh websphere6 -Das_dir=/opt/ibm/WebSphere/AppServer -Das_instance=server1 -Das_virtual_host=default_host -Das_admin_port=8880 -DAPP=InfoViewApp undeploy 158 BusinessObjects Enterprise XI 3. which is then deployed to the web application server. wdeploy. Example 1: using wdeploy deploy to predeploy.sh websphere6 -Das_dir=/opt/ibm/WebSphere/AppServer -Das_instance=server1 -Das_virtual_host=default_host -Das_admin_port=8880 -DAPP=InfoViewApp deploy Example 2: using wdeploy deployall to predeploy.11 Post Installation Web Application Deployment Deploying with wdeploy Using deploy and deployall The deploy command creates resources and configuration files for a specific web application.sh websphere6 -Das_dir=/opt/ibm/WebSphere/AppServer -Das_instance=server1 -Das_virtual_host=default_host -Das_admin_port=8880 deployall Using undeploy and undeployall The undeploy command uninstalls a previously deployed web application from the web application server. InfoView to WebSphere. Example 1: using wdeploy undeploy to undeploy InfoView from WebSphere.0 Installation and Configuration Guide for UNIX . Running deployall is equivalent to running a predeployall command followed by a deployonlyall command. then deploy.

0 Installation and Configuration Guide for UNIX 159 . dedicated. it may be using its own version of the Java Server Faces (JSF) library. you must manually reconfigure WebSphere for each web application that uses JSF: CmcApp. 5. CmcAppActions. The WebSphere administration console's default port number is 9060. Cached values are now displayed correctly. Restart the web application. so its settings can be modified.war Replace YOUR_WEB_APPLICATION in the example above with the name of your web application. All static content will be served by the web server. Post Installation Web Application Deployment Deploying with wdeploy 11 Example 2: using wdeploy undeployall to undeploy all web applications from WebSphere. wdeploy. you can set up a separate. To disable the JSF implementation supplied with WebSphere. Reload pages that display cached values. Select Classes loaded with application class loader first from the combo box. rather than the JSF implementation supplied with BusinessObjects Enterprise. 1. 3. Log in to the "WebSphere Application Server Administration" console using the following URL: http://WAS_HOSTNAME:PORT/admin. Stop the web application. To deploy to separate IHS web and WebSphere web application servers To reduce the load on a web application server. while dynamic content will be served by the web application server. BusinessObjects Enterprise XI 3. Repeat these steps for all other web applications that use JSF. follow the instructions below.sh websphere6 -Das_dir=/opt/ibm/WebSphere/AppServer -Das_instance=server1 -Das_virtual_host=default_host -Das_admin_port=8880 undeployall Disable WebSphere JSF implementation If pages rendered by WebSphere do not show cached values correctly. and PlatformServices. 4. To correct this problem. web server to serve static content. Browse to YOUR_WEB_APPLICATION > Manage Modules > YOUR_WEB_APPLICATION. 2.

Ensure that your WebSphere web application server is working correctly.11 Post Installation Web Application Deployment Deploying with wdeploy Note: This configuration requires that you use the wdeploy command to split web application resources into static and dynamic content that can be deployed to separate web and web application servers. and a port number. visit the URL: http://mywebserver. Open a web browser and enter the IP address or hostname of the web application server. If the web application server runs on a different machine. you must copy the wdeploy command and environment to the web application server. For example: http://mywebserver. 6. and a port number if the server is not listening on port 80.mycompany.mycompa ny. 3. such as the IHS default test page. 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. Run the web server plug-in installation wizard to install the plug-in that bridges WebSphere with IHS. Load a web page. Follow the plug-in configuration instructions on the WebSphere web site for configuring the bridge between IHS and WebSphere.0 Installation and Configuration Guide for UNIX .mycompany. and follow the directions to enter information about your IHS web server. 5.com:80/snoop/. Open a web browser and enter the IP address or hostname of the web server. For example: http://myappserver. Set up an IBM HTTP Server (IHS) web server and ensure that it is working correctly. Configure wdeploy environment to separate content between the web server and the web application server.com:9080.com:80. they must be undeployed before continuing. If the web application server is installed on the same machine as BusinessObjects Enterprise. For example. See To deploy web applications on a remote machine. 7. 1. 160 BusinessObjects Enterprise XI 3. Requests for dynamic resources are now forwarded to WebSphere when received by IHS. Note: If you have any existing BusinessObjects Enterprise web applications running on the server. run wdeploy locally on that machine. 2. to verify that the web server is serving content correctly. 4. This is known as "distributed" mode.

0 Installation and Configuration Guide for UNIX 161 .apache. 9. Run wdeploy deployonlyall command to deploy the dynamic content to WebSphere application server and static content to IHS.log Note: If your dynamic and static content are in a custom location. If IHS and WebSphere are on the same machine.log The dynamic content of web applications is located in: <INSTALLDIR>/de ployment/workdir/websphere6/application. ./wdeploy. The static content is located in: <INSTALLDIR>/deployment/workdir/web sphere6/resources. • Edit config.sh websphere6 -Das_mode=distributed -Dws_type=apache predeployall >> wdeploy. For example: • Run the following command to extract static content for the IHS web server.websphere6.sh websphere6 -Das_mode=distributed -Dws_type=apache deployonlyall >> wdeploy. For example: #Business Objects Configuration Utility ws_dir=/opt/apache connector_type=websphere6 deployment_dir=/opt/apache/htdocs • Edit config./wdeploy. For example: #Business Objects Configuration Utility as_admin_port=8880 as_admin_username=admin as_admin_password=password as_dir=/opt/websphere/appserver as_instance=server1 as_virtual_host=default_host as_admin_is_secure=false enforce_file_limit=true 8. BusinessObjects Enterprise XI 3. use the -Dwork_dir parameter. static and dynamic content will be automatically deployed to servers by the following command: . Post Installation Web Application Deployment Deploying with wdeploy 11 The wdeploy configuration files for IHS and WebSphere are located in <INSTALLDIR>/deployment. Use wdeploy predeploy in distributed mode to split source web applications into separate static and dynamic resources.

xml from the <pro file_root>/con fig/cells/<cell_name>/nodes/node_name/servers/<Web_serv er_name> directory on the WebSphere web application server to the <plugins_root>/config/<Web_server_name> directory on the IHS web server. Propagate the plugin-cfg.mycompany.0 Installation and Configuration Guide for UNIX . • Copy the bobj. Copy static content to the htdocs directory on the web server: • Extract the zip files on the web application server under <IN STALLDIR>/deployment/workdir/websphere6/resources. For example. Select the web server. Ensure that both static and dynamic content are correctly configured by trying to access a web application through the web server. Select the web server. For example. . use the -Dwork_dir parameter. click Servers > Web server. you must include an entry in httpd.sh websphere6 -Das_mode=distributed -deployonlyall >> wdeploy. • Copy these folders from the WebSphere web application server to the IHS <WS_DIR>/htdocs folder on the IHS server.11 Post Installation Web Application Deployment Deploying with wdeploy If IHS and WebSphere are on different machines. 162 BusinessObjects Enterprise XI 3. to include AnalyticalReporting. copy plugin-cfg.conf 10. For each web application. then click Propagate Plug-in.xml file from the application server to the web server using the administrative console.AnalyticalReporting.<application>.log Note: If your dynamic and static content are in a custom location. • For IHS.conf under <WS_DIR>/conf with the application config files. Web servers other than IHS require manual propagation. then click Propagate Plug-in. 11. • For all other web servers.conf files from the WebSphere web application server to the IHS <WS_DIR>/conf folder on the IHS server. 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. dynamic content will be automatically deployed to WebSphere by the following command. In this example./wdeploy. you would enter: Include conf/bobj. • Update IHS httpd. Static content must be manually deployed to the remote IHS machine afterwards.conf. Click Servers > Web server.com:80/CmcApp/.

Post Installation Web Application Deployment
Deploying with wdeploy 11
mywebserver.mycompany.com:80 is the web server, and /CmcApp/ is a
deployed web application.
Static content is now served by a dedicated web server, and dynamic content
is served by a dedicated web application server.

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

Deploying to WebLogic with wdeploy

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

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

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX 163

11 Post Installation Web Application Deployment
Deploying with wdeploy

Using deployonly and deployonlyall
The deployonly command deploys a web application that is specifically
configured for the target web application server. The deployonlyall
command performs the deployonly command for all web applications.

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

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

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

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

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

164 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment
Deploying with wdeploy 11
-DAPP=InfoViewApp
deploy

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

Using undeploy and undeployall
The undeploy command uninstalls a previously deployed web application
from the web application server. The undeployall command performs the
undeploy command for all web applications.

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

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

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX 165

11 Post Installation Web Application Deployment
Deploying with wdeploy

Note: This configuration requires that you use the wdeploy command to
split web application resources into static and dynamic content that can be
deployed to separate web and web application servers.
1. Set up the Apache web server and ensure that it is working correctly.
Load a web page, such as Apache's default test page, to verify that the
web server is serving content correctly.
Open a web browser and enter the IP address or hostname of the web
server, and a port number if the server is not listening on port 80. For
example: http://mywebserver.mycompany.com:80.
2. Ensure that your WebLogic web application server is working correctly.
Open a web browser and enter the IP address or hostname of the web
application server, and a port number. For example:
http://myappserver.mycompany.com:7001.

Note: If you have any existing BusinessObjects Enterprise web
applications running on the server, they must be undeployed before
continuing.

3. Download the WebLogic Apache HTTP Server Plug-In from the BEA web
site. The plug-in allows you to connect an Apache web server with a
WebLogic web application server, so Apache can forward requests for
dynamic resources to WebLogic.
4. Follow the plug-in configuration instructions on the BEA web site for
configuring the bridge between Apache web server and WebLogic.
Requests for dynamic resources are now forwarded to WebLogic when
received by Apache.
5. Ensure that the bridge between the web server and web application server
is working by pointing a browser to the web server and verifying that
dynamic content from the web application server is served correctly.
For example, visit the URL: http://mywebserver.mycompa
ny.com:80/jsp-examples/.

6. If the web application server is installed on the same machine as
BusinessObjects Enterprise, run wdeploy locally on that machine. If the
web application server runs on a different machine, you must copy the
wdeploy command and environment to the web application server. See
To deploy web applications on a remote machine.
7. Configure wdeploy environment to separate content between the web
server and the web application server. This is known as "distributed"
mode.

166 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

/wdeploy.0 Installation and Configuration Guide for UNIX 167 . static and dynamic content will be automatically deployed to the servers by the following command: . Use wdeploy predeploy in distributed mode to split source web applications into separate static and dynamic resources. . For example: #Business Objects Configuration Utility as_admin_port=7001 as_admin_username=weblogic as_admin_password=weblogic as_instance=AdminServer as_dir=/usr/bea/user_projects/domains/base_domain • Edit config. Post Installation Web Application Deployment Deploying with wdeploy 11 The wdeploy configuration files for Apache and WebLogic are located in <INSTALLDIR>/deployment.log The dynamic content in: <INSTALLDIR>/deployment/workdir/weblog ic9/application. Static content is located in: <INSTALLDIR>/deploy ment/workdir/weblogic9/resources. dynamic content will be automatically deployed to WebLogic by the following command. • Edit config. use the -Dwork_dir parameter. For example: • Run the following command to extract static content for the Apache web server and dynamic content for Weblogic application server. For example: #Business Objects Configuration Utility ws_dir=/opt/apache224/ connector_type=weblogic9 deployment_dir=/opt/apache224/htdocs 8.weblogic9 or config.weblogic10. If Apache and WebLogic are on different machines.log Note: If your dynamic and static content are in a custom location. If Apache and WebLogic are on the same machine.sh weblogic9 -Das_mode=distributed -Dws_type=apache predeployall >> wdeploy. Static BusinessObjects Enterprise XI 3. 9.apache./wdeploy. Run wdeploy deployonlyall command to deploy the dynamic content to WebLogic application server and static content to Apache.sh weblogic9 -Das_mode=distributed -Dws_type=apache deployonlyall >> wdeploy.

Related Topics • How to use wdeploy on page 151 • To deploy web applications on a remote machine on page 182 Deploying to Tomcat with wdeploy Using predeploy and predeployall The predeploy command creates resources and configuration files for a specific web application. 168 BusinessObjects Enterprise XI 3. and dynamic content is served by a dedicated web application server. • Update Apache httpd. but does not deploy the web application to the web application server. • Copy these folders from the WebLogic web application server to the Apache <WS_DIR>/htdocs folder on the Apache server.conf under <WS_DIR>/conf with the application config files. use the -Dwork_dir parameter. to include AnalyticalReporting.log Note: If your dynamic and static content are in a custom location.conf Static content is now served by a dedicated web server. you would enter: Include conf/bobj. you must include an entry in httpd. Copy static content to the htdocs directory on the web server: • Extract the zip files on the web application server under <IN STALLDIR>/deployment/workdir/WebLogic6/resources. • Copy the bobj. then copies the WAR application to <IN STALLDIR>/deployment/workdir/tomcat55.AnalyticalReporting.11 Post Installation Web Application Deployment Deploying with wdeploy content must be manually deployed to the remote Apache machine afterwards. The predeployall command performs the predeploy command for all web applications.<application>. For example.sh weblogic9 -Das_mode=distributed -deployonlyall >> wdeploy.0 Installation and Configuration Guide for UNIX ./wdeploy. .conf files from the WebLogic web application server to the Apache <WS_DIR>/conf folder on the Apache server.conf. For each web application.

Post Installation Web Application Deployment
Deploying with wdeploy 11
Example 1: using wdeploy predeploy to predeploy InfoViewApp to Tomcat.
wdeploy.sh tomcat55
-Das_dir=/opt/tomcat
-Das_instance=localhost
-DAPP=InfoViewApp
predeploy

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

Using deployonly and deployonlyall
The deployonly command deploys a web application that is specifically
configured for the target web application server. The deployonlyall
command performs the deployonly command for all web applications.

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

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

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

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX 169

11 Post Installation Web Application Deployment
Deploying with wdeploy

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

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

Using undeploy and undeployall
The undeploy command uninstalls a previously deployed web application
from the web application server. The undeployall command performs the
undeploy command for all web applications.

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

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

Related Topics
• After deploying web applications on page 192
• After deploying web applications on page 192
To deploy to separate Apache web and Tomcat web application servers
To reduce the load on a web application server, you can set up a separate,
dedicated, web server to serve static content. All static content will be served

170 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

Post Installation Web Application Deployment
Deploying with wdeploy 11
by the web server, while dynamic content will be served by the web
application server.
Note: This configuration requires that you use the wdeploy command to
split web application resources into static and dynamic content that can be
deployed to separate web and web application servers.
1. Set up the Apache web server and ensure that it is working correctly.
Load a web page, such as Apache's default test page, to verify that the
web server is serving content correctly.
Open a web browser and enter the IP address or hostname of the web
server, and a port number if the server is not listening on port 80. For
example: http://mywebserver.mycompany.com:80.
2. Ensure that your Tomcat web application server is working correctly.
Open a web browser and enter the IP address or hostname of the web
application server, and a port number. For example:
http://myappserver.mycompany.com:8080.

Note: If you have any existing BusinessObjects Enterprise web
applications running on the server, they must be undeployed before
continuing.

3. Download the Apache Tomcat connector from the Tomcat web site. The
Apache Tomcat connector allows you to connect an Apache web server
with a Tomcat web application server, so Apache can forward requests
for dynamic resources to Tomcat.
4. Follow the plug-in configuration instructions on the Apache web site for
configuring the bridge between Apache web server and Tomcat web
application server.
Requests for dynamic resources are now forwarded to Tomcat when
received by Apache.
5. Ensure that the bridge between the web server and web application server
is working by pointing a browser to the web server and verifying that
dynamic content from the web application server is served correctly.
For example, visit the URL: http://mywebserver.mycompa
ny.com:80/jsp-examples/.

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

BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX 171

11 Post Installation Web Application Deployment
Deploying with wdeploy

wdeploy command and environment to the web application server. See
To deploy web applications on a remote machine.
7. Configure wdeploy environment to separate content between the web
server and the web application server. This is known as "distributed"
mode.
The wdeploy configuration files for Apache and Tomcat are located in
<INSTALLDIR>/deployment.
• Edit config.tomcat55. For example:
#Business Objects Configuration Utility
as_dir=/opt/Tomcat5520
as_instance=localhost
as_service_name=Tomcat5

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

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

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

Note: If your dynamic and static content are in a custom location, use
the -Dwork_dir parameter.
If Apache and Tomcat are on different machines, dynamic content will
be automatically deployed to Tomcat by the following command. Static

172 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX

/wdeploy. The predeployall command performs the predeploy command for all web applications. Related Topics • How to use wdeploy on page 151 • To deploy web applications on a remote machine on page 182 Deploying to Oracle with wdeploy Using predeploy and predeployall The predeploy command creates resources and configuration files for a specific web application. you must include an entry in httpd. • Copy these folders from the Tomcat web application server to the Apache <WS_DIR>/htdocs folder on the Apache server. but does not deploy the web application to the web application server. Copy static content to the htdocs directory on the web server: • Extract the zip files on the web application server under <IN STALLDIR>/deployment/workdir/Tomcat55/resources.AnalyticalReporting. Post Installation Web Application Deployment Deploying with wdeploy 11 content must be manually deployed to the remote Apache machine afterwards. • Update Apache httpd.conf. use the -Dwork_dir parameter. to include AnalyticalReporting.sh tomcat55 -Das_mode=distributed -deployonlyall >> wdeploy. For example.conf Static content is now served by a dedicated web server.log Note: If your dynamic and static content are in a custom location. and dynamic content is served by a dedicated web application server. .conf files from the Tomcat web application server to the Apache <WS_DIR>/conf folder on the Apache server. • Copy the bobj. For each web application. BusinessObjects Enterprise XI 3.<application>.0 Installation and Configuration Guide for UNIX 173 .conf under <WS_DIR>/conf with the application config files. then copies the WAR application to <IN STALLDIR>/deployment/workdir/oas1013. you would enter: Include conf\bobj.

wdeploy. wdeploy.11 Post Installation Web Application Deployment Deploying with wdeploy Example 1: using wdeploy predeploy to predeploy InfoView to Oracle Application Server.sh oas1013 -Das_dir=/opt/oracle10gasr3/oracleas_1 -Das_instance=home -Das_appserver_name=oc4j_inst1 -Das_group_id=default_group -Das_admin_port=6013 -Das_admin_username=oc4jadmin -Das_admin_password=oracle12 predeployall Using deployonly and deployonlyall The deployonly command deploys a web application that is specifically configured for the target web application server. The deployonlyall command performs the deployonly command for all web applications.sh oas1013 -Das_dir=/opt/oracle10gasr3/oracleas_1 -Das_instance=home -Das_appserver_name=oc4j_inst1 -Das_group_id=default_group -Das_admin_port=6013 -Das_admin_username=oc4jadmin -Das_admin_password=oracle12 -DAPP=InfoViewApp deployonly 174 BusinessObjects Enterprise XI 3. Example 1: using wdeploy deployonly to deploy a predeployed InfoView to Oracle Application Server.0 Installation and Configuration Guide for UNIX . wdeploy.sh oas1013 -Das_dir=/opt/oracle10gasr3/oracleas_1 -Das_instance=home -Das_appserver_name=oc4j_inst1 -Das_group_id=default_group -Das_admin_port=6013 -Das_admin_username=oc4jadmin -Das_admin_password=oracle12 -DAPP=InfoViewApp predeploy Example 2: using wdeploy predeployall to predeploy all web applications to Oracle Application Server.

Running deployall is equivalent to running a predeployall command followed by a deployonlyall command. all web applications to Oracle Application Server.0 Installation and Configuration Guide for UNIX 175 . Running deploy is equivalent to running a predeploy command followed by a deployonly command. wdeploy.sh oas1013 -Das_dir=/opt/oracle10gasr3/oracleas_1 -Das_instance=home -Das_appserver_name=oc4j_inst1 -Das_group_id=default_group -Das_admin_port=6013 -Das_admin_username=oc4jadmin -Das_admin_password=oracle12 -DAPP=InfoViewApp deploy Example 2: using wdeploy deployall to predeploy. Example 1: using wdeploy deploy to predeploy. then deploy. InfoView to Oracle Application Server. which is then deployed to the web application server.sh oas1013 -Das_dir=/opt/oracle10gasr3/oracleas_1 -Das_instance=home -Das_appserver_name=oc4j_inst1 -Das_group_id=default_group -Das_admin_port=6013 -Das_admin_username=oc4jadmin -Das_admin_password=oracle12 deployonlyall Using deploy and deployall The deploy command creates resources and configuration files for a specific web application. wdeploy.sh oas1013 -Das_dir=/opt/oracle10gasr3/oracleas_1 -Das_instance=home -Das_appserver_name=oc4j_inst1 -Das_group_id=default_group -Das_admin_port=6013 -Das_admin_username=oc4jadmin BusinessObjects Enterprise XI 3. then deploy. wdeploy. Post Installation Web Application Deployment Deploying with wdeploy 11 Example 2: using wdeploy deployonlyall to deploy all predeployed web applications to Oracle Application Server. The deployall command performs the deploy command for all web applications.

wdeploy. wdeploy.0 Installation and Configuration Guide for UNIX . Example 1: using wdeploy undeploy to undeploy InfoView from Oracle Application Server. The undeployall command performs the undeploy command for all web applications. then copies the WAR application to <IN 176 BusinessObjects Enterprise XI 3.11 Post Installation Web Application Deployment Deploying with wdeploy -Das_admin_password=oracle12 deployall Using undeploy and undeployall The undeploy command uninstalls a previously deployed web application from the web application server.sh oas1013 -Das_dir=/opt/oracle10gasr3/oracleas_1 -Das_instance=home -Das_appserver_name=oc4j_inst1 -Das_group_id=default_group -Das_admin_port=6013 -Das_admin_username=oc4jadmin -Das_admin_password=oracle12 -DAPP=InfoViewApp undeploy Example 2: using wdeploy undeployall to undeploy all web applications from Oracle Application Server.sh oas1013 -Das_dir=/opt/oracle10gasr3/oracleas_1 -Das_instance=home -Das_appserver_name=oc4j_inst1 -Das_group_id=default_group -Das_admin_port=6013 -Das_admin_username=oc4jadmin -Das_admin_password=oracle12 undeployall Related Topics • After deploying web applications on page 192 Deploying to SAP Application Server with wdeploy Using predeploy and predeployall The predeploy command creates resources and configuration files for a specific web application.

sh nw2004 -Das_dir=/opt/sap -Das_instance=server1 -Das_sid=AS2 -Das_admin_username=Administrator -Das_admin_password=password1 -Das_admin_port=50000 -DAPP=InfoViewApp deployonly BusinessObjects Enterprise XI 3.sh nw2004 -Das_dir=/opt/sap -Das_instance=server1 -Das_sid=AS2 -Das_admin_username=Administrator -Das_admin_password=password1 -Das_admin_port=50000 predeployall Using deployonly and deployonlyall The deployonly command deploys a web application that is specifically configured for the target web application server. wdeploy. The deployonlyall command performs the deployonly command for all web applications.sh nw2004 -Das_dir=/opt/sap -Das_instance=server1 -Das_sid=AS2 -Das_admin_username=Administrator -Das_admin_password=password1 -Das_admin_port=50000 -DAPP=InfoViewApp predeploy Example 2: using wdeploy predeployall to predeploy all web applications to SAP Application Server. wdeploy. but does not deploy the web application to the web application server. wdeploy.0 Installation and Configuration Guide for UNIX 177 . Example 1: using wdeploy deployonly to deploy a predeployed InfoView to SAP Application Server. The predeployall command performs the predeploy command for all web applications. Post Installation Web Application Deployment Deploying with wdeploy 11 STALLDIR>/deployment/workdir/nw2004. Example 1: using wdeploy predeploy to predeploy InfoView to SAP Application Server.

Running deployall is equivalent to running a predeployall command followed by a deployonlyall command. Example 1: using wdeploy deploy to predeploy. then deploy. The deployall command performs the deploy command for all web applications.sh nw2004 -Das_dir=/opt/sap -Das_instance=server1 -Das_sid=AS2 -Das_admin_username=Administrator -Das_admin_password=password1 -Das_admin_port=50000 deployonlyall Using deploy and deployall The deploy command creates resources and configuration files for a specific web application. wdeploy.sh nw2004 -Das_dir=/opt/sap -Das_instance=server1 -Das_sid=AS2 -Das_admin_username=Administrator -Das_admin_password=password1 -Das_admin_port=50000 -DAPP=InfoViewApp deploy Example 2: using wdeploy deployall to predeploy. all web applications to SAP Application Server.0 Installation and Configuration Guide for UNIX . Running deploy is equivalent to running a predeploy command followed by a deployonly command. InfoView to SAP Application Server.11 Post Installation Web Application Deployment Deploying with wdeploy Example 2: using wdeploy deployonlyall to deploy all predeployed web applications to SAP Application Server. which is then deployed to the web application server.sh nw2004 -Das_dir=/opt/sap -Das_instance=server1 -Das_sid=AS2 -Das_admin_username=Administrator -Das_admin_password=password1 -Das_admin_port=50000 deployall 178 BusinessObjects Enterprise XI 3. wdeploy. then deploy. wdeploy.

The undeployall command performs the undeploy command for all web applications.sar/jsf- libs • JBOSS_HOME/server/default/tmp BusinessObjects Enterprise XI 3. wdeploy.sh nw2004 -Das_dir=/opt/sap -Das_instance=server1 -Das_sid=AS2 -Das_admin_username=Administrator -Das_admin_password=password1 -Das_admin_port=50000 -DAPP=InfoViewApp undeploy Example 2: using wdeploy undeployall to undeploy all web applications from SAP Application Server. Example 1: using wdeploy undeploy to undeploy InfoView from SAP Application Server. wdeploy. Post Installation Web Application Deployment Deploying with wdeploy 11 Using undeploy and undeployall The undeploy command uninstalls a previously deployed web application from the web application server. the following directories must be removed and JBoss restarted: • JBOSS_HOME/server/default/deploy/jbossweb-tomcat55.sh nw2004 -Das_dir=/opt/sap -Das_instance=server1 -Das_sid=AS2 -Das_admin_username=Administrator -Das_admin_password=password1 -Das_admin_port=50000 undeployall Related Topics • After deploying web applications on page 192 Deploying to JBoss with wdeploy The Java Server Faces (JSF) bundled with the JBoss web application servers must be disabled for the Central Management Console (CMC) and InfoView web clients to work correctly.0 Installation and Configuration Guide for UNIX 179 . To disable JSF.

wdeploy. refer to section 10.sh jboss404 -Das_dir=/opt/jboss-4.0 Installation and Configuration Guide for UNIX . wdeploy. then copies the WAR application to <IN STALLDIR>/deployment/workdir/jboss404.11 Post Installation Web Application Deployment Deploying with wdeploy • JBOSS_HOME/server/default/work Note: To use the Javalog4j logging included with BusinessObjects Enterprise XI 3.0.jboss.class loader scoping in the JBoss Development Process Guide: http://docs. Example 1: using wdeploy predeploy to predeploy InfoView to JBoss. The deployonlyall command performs the deployonly command for all web applications.properties file . Using predeploy and predeployall The predeploy command creates resources and configuration files for a specific web application. but does not deploy the web application to the web application server.4.4. wdeploy.GA -Das_instance=default predeployall Using deployonly and deployonlyall The deployonly command deploys a web application that is specifically configured for the target web application server.0.sh jboss404 -Das_dir=/opt/jboss-4.org/process-guide/en/html/logging.sh jboss404 -Das_dir=/opt/jboss-4.3. Example 1: InfoView using wdeploy deployonly to deploy a predeployed InfoView to JBoss.4.0.html#d0e3341.GA -Das_instance=default -DAPP=InfoViewApp deployonly 180 BusinessObjects Enterprise XI 3.7 Using your own log4j.GA -Das_instance=default -DAPP=InfoViewApp predeploy Example 2: using wdeploy predeployall to predeploy all web applications to JBoss. The predeployall command performs the predeploy command for all web applications.0.

Running deployall is equivalent to running a predeployall command followed by a deployonlyall command.0 Installation and Configuration Guide for UNIX 181 .sh jboss404 -Das_dir=/opt/jboss-4. InfoView to JBoss. wdeploy.0.0. The undeployall command performs the undeploy command for all web applications. wdeploy.4. Example 1: using wdeploy deploy to predeploy.GA -Das_instance=default BusinessObjects Enterprise XI 3.GA -Das_instance=default deployall Using undeploy and undeployall The undeploy command uninstalls a previously deployed web application from the web application server.0.4.sh jboss404 -Das_dir=/opt/jboss-4.4. all web applications to JBoss.GA -Das_instance=default -DAPP=InfoViewApp deploy Example 2: using wdeploy deployall to predeploy. Running deploy is equivalent to running a predeploy command followed by a deployonly command.sh jboss404 -Das_dir=/opt/jboss-4.GA -Das_instance=default deployonlyall Using deploy and deployall The deploy command creates resources and configuration files for a specific web application. wdeploy.4. then deploy. The deployall command performs the deploy command for all web applications. wdeploy. which is then deployed to the web application server. Example 1: using wdeploy undeploy to undeploy InfoView from JBoss.0.sh jboss404 -Das_dir=/opt/jboss-4. then deploy. Post Installation Web Application Deployment Deploying with wdeploy 11 Example 2: using wdeploy deployonlyall to deploy all predeployed web applications to JBoss.

Create on Box 2 the following directories. and Box 2 is the remote machine on which no BusinessObjects Enterprise resources are currently installed. • <INSTALLDIR>/deployment/. it is recommended that you maintain files within the same folder structure or hierarchy in Box 2 as in Box 1.GA -Das_instance=default undeployall Related Topics • After deploying web applications on page 192 To deploy web applications on a remote machine Use the procedure below to deploy web applications to a remote machine. Tip: Although you can customize the folder structure to meet your specific requirements. 2. wdeploy.4. 1. In this procedure Box 1 refers to the machine hosting your BusinessObjects Enterprise installation. • <INSTALLDIR>/bobje/enterprise120/java/applications/ • <INSTALLDIR>/Performance_Management_120/ • <INSTALLDIR>/caf/ These directories reflect the default directory structure installed on Box 1.sh jboss404 -Das_dir=/opt/jboss-4.11 Post Installation Web Application Deployment Deploying with wdeploy -DAPP=InfoViewApp undeploy Example 2: using wdeploy undeployall to undeploy all web applications from JBoss.0 Installation and Configuration Guide for UNIX . The deployment folder contains the wdeploy scripts and configuration files. • Copy all the contents under <INSTALLDIR>/bobje/deployment/ Note: This content is also available on the product distribution media under the following directory: Collaterals/Tools/wdeploy 182 BusinessObjects Enterprise XI 3.0. Copy the following files from Box 1 to Box 2.

war c. If you keep all the WAR files in the same folder.0 Installation and Configuration Guide for UNIX 183 . For example. You must provide all the required information to enable wdeploy to deploy the web application. 5. Open the properties file under <INSTALLDIR>/deployment/apps and modify the properties file for each web application (e. Enter the following parameter in a new line: war_dir The value of the parameter is the WAR file path name.properties. Modify the wdeploy configuration file for your web application server. Post Installation Web Application Deployment Deploying with wdeploy 11 Tip: Remove the contents under <INSTALLDIR>/bobje/deploy ment/workdir after the file copy if that folder is not empty. • Copy all the contents under <INSTALLDIR>/bobje/enterprise120/ja va/applications/. you would modify the file to: as_dir=/bea92/user_projects/domains/base_domain as_instance=AdminServer as_admin_port=7001 as_admin_username=weblogic as_admin_password=weblogic The configuration file is located in the following directory:<INSTALLDIR>/de ployment/config.g CrystalRe ports. b.war. Configure the WAR file directory for each web application. a.properties to war_dir=/home/bobje/enterprise120/java/ applications/CrystalReports.properties).<appserver> . Set the JAVA_HOME environment variable to JDK 1. If you are going to deploy CrystalReports. Repeat steps a-b for all the web applications you want to deploy to your web application server. BusinessObjects Enterprise XI 3. skip to step 5. • From <INSTALLDIR>/Performance_Management_120/ copy InitCon fig. • Copy the contents of <INSTALLDIR>/caf/. 3. you would set the value of war_dir in <INSTALLDIR>/deployment/apps/ CrystalReports. 4. to modify the configuration file for WebLogic 9. you don't need to configure the WAR file directory for each web application.5 directory.

log You can pass the -Dwar_dir (with the path to the WAR files) in the command line to specify the location from which wdeploy accesses non customized WAR files. Related Topics • How to use wdeploy on page 151 • Prerequisites for using wdeploy on page 149 184 BusinessObjects Enterprise XI 3. If the Performance Management 12.0 Installation and Configuration Guide for UNIX .11 Post Installation Web Application Deployment Deploying with wdeploy 6. Repackage the PerformanceManagement.0 files you copied in step 2 are not located under the same folder structure as Box 1.configdir parameter in theweb.xml file to the location of the InitConfig. The modified file should look like the example below.configdir</param-name> <param-value>/home/Performance_Management_120</param- value> </context-param> c. 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.sh <appserver> deployall -Dwar_dir=<INSTALLDIR>/bobje/ enterprise120/java/applications/ >> <logfilename>. <context-param> <param-name>af. Set the af.xml file is located in: /PerformanceManagement/WEB-INF . Extract PerformanceManagement.properties file. 7. to deploy Performance Management you must do the following: a.war from the following directory: <INSTALLDIR>/bobje/enterprise120/java/applications/ b.war. Run the wdeploy script from its location in Box 2 by opening command line console and entering the following: <INSTALLDIR>/deployment/wdeploy. Theweb.

Post Installation Web Application Deployment Manually deploying to a web application server 11 Manually deploying to a web application server BusinessObjects Enterprise WAR files BusinessObjects Enterprise separates web application functionality into several Web ARchive (WAR) files. InfoView PMC_Help Performance Management BusinessObjects Enterprise XI 3. Desktop Intelligence. CMC.0 Installation and Configuration Guide for UNIX 185 . CMC. WAR file Used by AdminTools Query Builder AnalyticalReport Web Intelligence. InfoView dswsbobje Web services components InfoViewApp InfoView (entry point) InfoViewAppActions InfoView OpenDocument Open Document PerformanceManage Performance Management. making it easier to deploy only the web applications required by your organization. CMC. Once you have installed BusinessObjects Enterprise the source files are available in the following directory: <INSTALLDIR>/bobje/enterprise120/ja va/applications/ The following table summarizes the relationship between the WAR files and specific web applications in a BusinessObjects Enterprise deployment. InfoView ment PlatformServices CMC. InfoView ing BusinessProcessBI Web services components CmcApp CMC (entry point) CmcAppActions CMC CrystalReports Crystal Reports.

11 Post Installation Web Application Deployment Manually deploying to a web application server WAR file Used by VoyagerClient CMC. unless otherwise noted.war.0 Installation and Configuration Guide for UNIX . with the exception of InfoViewApp and CmcApp. can be deployed to fix context root locations on your web application server. InfoView XCelsius Xcelsius data presentation XCTemplateUploader Xcelsius data presentation WAR file context roots All WAR files. a root context of /MyOrgCmc requires the WAR file to be named MyOrgCmc. CmcAp /CmcAppActions pActions CrystalRe /CrystalReports ports dswsbobje /dswsbobje 186 BusinessObjects Enterprise XI 3. For example. WAR file WAS context path (default) AdminTools /AdminTools Analytical /AnalyticalReporting Reporting BusinessPro /BusinessProcessBI cessBI CmcApp /CmcApp Note: You may use a different root context for CmcApp as long as the root context matches the name of the WAR file. The following table lists the context roots that must be used.

Post Installation Web Application Deployment Manually deploying to a web application server 11 WAR file WAS context path (default) InfoViewApp /InfoViewApp Note: You may use a different root context for InfoViewApp as long as the root context matches the name of the WAR file. a root context of/MyOrgInfo requires the WAR file to be named MyOrgInfo. if your deployment environment involves reverse proxy. there is a specific order you must follow. The order in which you deploy the WAR files for your web applications does not matter. InfoViewAp /InfoViewAppActions pActions OpenDocu /OpenDocument ment Performance /PerformanceManagement Management PlatformSer /PlatformServices vices PMC_Help /PMC_Help Voyager /VoyagerClient Client XCelsius /XCelsius XCTemplateU /XCTemplateUploader ploader Guidelines for deploying WAR files To successfully deploy the WAR files and to ensure your BusinessObjects web applications run properly. For example. Your web application server must be installed and running before you deploy any WAR file. For more information see “Modifying Default Security Behavior ” in the BusinessObjects Enterprise Administrator's Guide.war. 2. BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX 187 . However. 1. you should use the following guidelines.

Example 1: using wdeploy predeploy to prepare InfoViewApp for deployment to Tomcat.default parameter in the web.war and CmcAppActions. <context-param> <param-name>appservice. follow the steps in To prepare a manual deployment on a remote machine. you must update the appservice. The following steps will deploy a web application on a web application server using the application server's administrative console.xml file located in the WEB-INF directory of the CmcApp.11 Post Installation Web Application Deployment Manually deploying to a web application server 3.jsp</param-value> </context-param> To manually deploy web applications Ensure that your web application server and CMS are both running. to the new application name. or wdeploy predeployall to prepare all web applications. The wdeploy tool must be used to generate deployable WAR files before they can be deployed to your web application server. each WAR file must reside within the same level of the context path. When deploying a web application with functionality shared between multiple WAR files.url.url. Note: • Only two web applications can be renamed: InfoViewApp and CmcApp. 1. • To rename CmcApp. As a general rule.sh tomcat55 -Das_dir=/opt/usr/tomcat -Das_instance=localhost -Das_service_name=Tomcat55 -DAPP=InfoViewApp predeploy 188 BusinessObjects Enterprise XI 3.war. wdeploy. Change CmcApp in the <param-value> tag shown below. To rename InfoViewApp you can rename the application using the web application server administration console. 4. If the application server is located on a machine other than your BusinessObjects Enterprise machine. Run the wdeploy predeploy command to prepare a single web application.0 Installation and Configuration Guide for UNIX .default</param-name> <param-value>/NewCMC/App/appService. do not rename the WAR files.

In this procedure Box 1 refers to the machine hosting your BusinessObjects Enterprise installation. 2. The wdeploy command creates WAR or EAR files in <INSTALLDIR>/de ployment/workdir/<appserver>/application unless you specify the -Dwork_dir parameter. Create on Box 2 the following directories. and Box 2 is the remote machine on which no BusinessObjects Enterprise resources are currently installed. Related Topics • Where to find wdeploy on page 149 • How to use wdeploy on page 151 • To deploy web applications on a remote machine on page 182 • To prepare for manual deployment on a remote machine on page 189 • Minimum rights for deploying web applications on page 18 To prepare for manual deployment on a remote machine Use the procedure below to manually deploy web applications to a remote machine. Repeat these steps for any other web applications that need to be installed. Post Installation Web Application Deployment Manually deploying to a web application server 11 Example 2: using wdeploy predeployall to prepare all web applications for deployment to Tomcat. 1. BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX 189 .sh tomcat55 -Das_dir=/opt/usr/tomcat -Das_instance=localhost -Das_service_name=Tomcat55 predeployall The wdeploy command will prepare the web application files for deployment on the web application server. Your web applications can now be manually deployed on your web application server. Follow the manual deployment procedure specific to your web application server. wdeploy.

• <INSTALLDIR>/bobje/enterprise120/java/applications/ • <INSTALLDIR>/Performance_Management_120/ • <INSTALLDIR>/caf/ These directories reflect the default directory structure installed on Box 1. Set the JAVA_HOME environment variable to JDK 1. Open the properties file under <INSTALLDIR>/deployment/apps and modify the properties file for each web application (e.properties.g CrystalRe ports. Tip: Although you can customize the folder structure to meet your specific requirements. Configure the WAR file directory for each web application. 2. 4. 3. • Copy the contents of <INSTALLDIR>/caf/. • Copy all the contents under <INSTALLDIR>/bobje/enterprise120/ja va/applications/.properties). The deployment folder contains the wdeploy scripts and configuration files.11 Post Installation Web Application Deployment Manually deploying to a web application server • <INSTALLDIR>/deployment/.5 directory. it is recommended that you maintain files within the same folder structure or hierarchy in Box 2 as in Box 1. you don't need to configure the WAR file directory for each web application. a. • From <INSTALLDIR>/Performance_Management_120/ copy InitCon fig. 190 BusinessObjects Enterprise XI 3. Enter the following parameter in a new line: war_dir The value of the parameter is the WAR file path name. If you keep all the WAR files in the same folder. • Copy all the contents under <INSTALLDIR>/bobje/deployment/ Note: This content is also available on the product distribution media under the following directory: Collaterals/Tools/wdeploy Tip: Remove the contents under <INSTALLDIR>/bobje/deploy ment/workdir after the file copy if that folder is not empty. skip to step 5. b. Copy the following files from Box 1 to Box 2.0 Installation and Configuration Guide for UNIX .

configdir parameter in the web. Repeat steps a-b for all the web applications you want to deploy to your web application server.0 files you copied in step 2 are not located under the same folder structure as Box 1.war. you would modify the file to: as_dir=/bea92/user_projects/domains/base_domain as_instance=AdminServer as_admin_port=7001 as_admin_username=weblogic as_admin_password=weblogic The configuration file is located in the following directory:<INSTALLDIR>/de ployment/config.<appserver> .war from the following directory: <INSTALLDIR>/bobje/enterprise120/java/applications/ b. The modified file should look like the example below. <context-param> <param-name>af. 5. If the Performance Management 12. Extract PerformanceManagement. You must provide all the required information to enable wdeploy to prepare the WAR file for manual deployment. to deploy Performance Management you must do the following: a. 6. Set the af. Repackage the PerformanceManagement. The web. Post Installation Web Application Deployment Manually deploying to a web application server 11 If you are going to deploy CrystalReports. to modify the configuration file for WebLogic 9.properties to war_dir=/home/bobje/enterprise120/java/ applications/CrystalReports.configdir</param-name> <param-value>/home/Performance_Management_120</param- value> </context-param> c. For example.war. BusinessObjects Enterprise XI 3.war c.0 Installation and Configuration Guide for UNIX 191 .xml file to the location of the InitConfig.xml file is located in: /PerformanceManagement/WEB-INF. you would set the value of war_dir in <INSTALLDIR>/deployment/apps/ CrystalReports. Modify the wdeploy configuration file for your web application server.properties file.

the default context used for the CMC is CmcApp.0 Installation and Configuration Guide for UNIX . 8. make sure that InfoView and the Central Management Console can be launched in a web browser. Run the wdeploy script from its location in Box 2 by opening command line console and entering the following: <INSTALLDIR>/deployment/wdeploy. For example: • http://WAS_HOSTNAME:PORT/INFOVIEW_CONTEXT • http://WAS_HOSTNAME:PORT/CMC_CONTEXT Replace WAS_HOSTNAME with the hostname or IP address of your web application server. Related Topics • How to use wdeploy on page 151 • Prerequisites for using wdeploy on page 149 After deploying web applications To verify the web application server configuration.sh <appserver> predeployall -Dwar_dir=<INSTALLDIR>/bobje/ enterprise120/java/applications/ >> <logfilename>.log You can pass the -Dwar_dir (with the path to the WAR files) in the command line to specify the location from which wdeploy accesses non customized WAR files. The default root context used for InfoView is In foViewApp. You are now prepared to manually deploy web applications on Box 2. 192 BusinessObjects Enterprise XI 3. and PORT with the port number used for either HTTP or HTTPS communication. The wdeploy command creates WAR or EAR files in <INSTALLDIR>/de ployment/workdir/<appserver>/application unless you specify the -Dwork_dir parameter.11 Post Installation Web Application Deployment Manually deploying to a web application server 7. Follow the manual deployment steps for your 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.

Click the Install button and navigate to the location of the WAR file to deploy. 3. click Enterprise Applications on the left navigational pane. 2. Proceed to "Step 4".g. 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. Select the virtual host you created (or default_host if you didn't create your own) from the Virtual Host drop-down list. 5. Under the Applications heading of the console navigation menu. Verify that the WAR file was deployed. Click the Save link. configured. 8. Log in to the "WebSphere Application Server Administration" console using the following URL: http://WAS_HOSTNAME:PORT/admin The WebSphere admininstration console's default port number is 9060. 4. then click the Start button. Post Installation Web Application Deployment Manually deploying to a web application server 11 Deploying with the Administration console Deploying with the WebSphere administrative console Ensure that your WebSphere web application server is installed. give a unique name for your web application and proceed to "Step 2". 1. Under the Applications heading of the console navigation menu. click Enterprise Applications on the left navigational pane. Click Save to Master Configuration. 7. Review the summary page. 6. 11. Proceed to "Step 3". Enter a context root for the WAR file (e. followed by Continue.0 Installation and Configuration Guide for UNIX 193 . In "Step 1". and press Finish when done. then the Save button. CmcApp/ for CmcApp. 9. 10. and running before deploying WAR files. Related Topics • After deploying web applications on page 192 BusinessObjects Enterprise XI 3. Repeat steps 1-11 for each WAR file to deploy.war) and press the Next button.

2.11 Post Installation Web Application Deployment Manually deploying to a web application server Disable WebSphere JSF implementation If pages rendered by WebSphere do not show cached values correctly. you can use the WebSphere Integrated Solutions Console to separately deploy these applications to the cluster. rather than the JSF implementation supplied with BusinessObjects Enterprise. and PlatformServices. 194 BusinessObjects Enterprise XI 3. The WebSphere administration console's default port number is 9060. Once all the required web applications have been installed. Log in to the "WebSphere Application Server Administration" console using the following URL: http://WAS_HOSTNAME:PORT/admin. Stop the web application. you need to deploy the web applications to the machine hosting the WebSphere Deployment Manager. To correct this problem. To configure the load balancer and cluster setup please consult your WebSphere documentation. it may be using its own version of the Java Server Faces (JSF) library. 3. 5. Select Classes loaded with application class loader first from the combo box.0 Installation and Configuration Guide for UNIX . CmcAppActions. 1. follow the instructions below.war Replace YOUR_WEB_APPLICATION in the example above with the name of your web application. Restart the web application. To deploy to a WebSphere cluster To manually deploy BusinessObjects Enterprise web applications to a WebSphere web application cluster distributed over multiple machines. Tip: It is recommended that you install and configure a hardware or software load balancer if running BusinessObjects Enterprise web applications on a WebSphere web application cluster. Reload pages that display cached values. Cached values are now displayed correctly. Browse to YOUR_WEB_APPLICATION > Manage Modules > YOUR_WEB_APPLICATION. 4. Repeat these steps for all other web applications that use JSF. so its settings can be modified. you must manually reconfigure WebSphere for each web application that uses JSF: CmcApp. To disable the JSF implementation supplied with WebSphere.

Go to Applications > Enterprise Applications to separately install each web application you want to deploy from the following directory: <INSTALLDIR>/deployment/workdir/websphere6/application/ Note: All web applications are stored as EAR modules. BusinessObjects Enterprise XI 3.properties is matches the value specified for af. as_dir=<INSTALLDIR>/IBM/WebSphere/AppServer as_admin_port=8779 as_virtual_host=default_host as_admin_is_secure=false enforce_file_limit=true 3.war to the WebSphere cluster. you must first copy the wdeploy tool and environment to the machine hosting the WebSphere administration server.properties from <INSTALLDIR>/Per formance_Management_120 to each managed server and ensure the file path of InitConfig. Open a command-line console and run the following command: <INSTALLDIR>/deployment> wdeploy. you must copy InitConfig.sh websphere6 predeployall 4. Post Installation Web Application Deployment Manually deploying to a web application server 11 To deploy your web applications to a WebSphere cluster use the following general workflow: 1. If BusinessObjects Enterprise is installed to the same machine hosting the WebSphere Deployment Manager. Modify the config. If you plan to deploy PerformanceManagement. If BusinessObjects Enterprise and the WebSphere Deployment Manager run on different machines.0 Installation and Configuration Guide for UNIX 195 .xml in PerformanceManagement. 2.properties file should be located in C:\Program Files\BusniessObjects\Performance Management 12.configdir param in web. skip to step 3. You need to specify information for the server administrating the cluster as shown in the following example.0 on each machine hosting a managed WebSphere server.websphere6 file located in the following directory: <INSTALLDIR>/deployment/. 5.war as shown below: <context-param> <param-name>af.configdir</param-name> <param-value> /home/Performance_Management_120 </param-value> <context-param> Note: The InitConfig. Open the WebSphere Integrated Solutions Console.

See To deploy dswsbobje. 9. 1. The "WebLogic Server Administration Console" web page is displayed. Repeat steps 4-6 for each EAR file you want to install. 7. You must also have created a WebLogic domain in which to run BusinessObjects Enterprise. Related Topics • To deploy web applications on a remote machine on page 182 Deploying with the WebLogic administrative console Ensure that your WebLogic web application server is installed. In the left-hand navigation pane. Click Synchronize.0 Installation and Configuration Guide for UNIX . See your WebLogic documentation for information about creating a new domain. Open the "WebLogic Administrative Console" with a web browser at a http://WAS_HOSTNAME:PORT/console where WAS_HOSTNAME is the name of your WebLogic server and PORT_NUMBER is the port number on which the server listens. Follow the Install new application steps in the console to install the web application Note: In "Map modules to servers". Note: • Deployable web applications for WebLogic are in the following format in the wdeploy workdir folder: • WebServices (ProcessBI and dswsbobje) are folders • AnalyticalReporting and PerformanceManagement are EAR files • Rest of WebApps are WAR files • WebLogic deployments must use an extracted dswsbobje. click base_domain > Deployments . configured.war to WebLogic on page 199. Go to Applications > Enterprise Applications to start the application you just installed. Go to System administration > Nodes and select the nodes in the cluster that are not indicated as synchronized 10.war. 11. 8. and running before deploying WAR files. make sure that you highlight the target cluster and select the module to install before clicking Apply. click Save. 196 BusinessObjects Enterprise XI 3. After installing the application.11 Post Installation Web Application Deployment Manually deploying to a web application server 6. 2.

Post Installation Web Application Deployment Manually deploying to a web application server 11 The "Summary of Deployments" page is displayed. you must press the Start button to initiate its execution. When you've selected the file and specified any other parameters in the wizard. Your changes are saved. you need to create a WebLogic XML registry using the following default settings and target it to all managed servers as shown below: Property Value Name Registry name BusinessObjects Enterprise XI 3. click the Finish button to deploy the file. 5. To deploy to a WebLogic cluster use the following general workflow: 1. To configure the load balancer and cluster setup please consult your WebLogic documentation. The domain is locked for editing. Press the Activate Changes button to apply you're the changes to the web application server. 3. 6. The web application you deployed will now start. Press the Install button and navigate to the WAR file you wish to deploy. When your WAR file has been deployed. you can use the WebLogic administration console to deploy these applications to the cluster. After installing and setting up the WebLogic cluster. 4. The WAR file is deployed to the WebLogic server. you need to deploy the web applications to the machine hosting the WebLogic administration server. Once all the required web applications have been installed. Tip: It is recommended that you install and configure a hardware or software load balancer if running BusinessObjects Enterprise web applications on a WebLogic web application cluster. Click the Lock and Edit button in the left-hand pane.0 Installation and Configuration Guide for UNIX 197 . Related Topics • After deploying web applications on page 192 To deploy to a WebLogic cluster To manually deploy BusinessObjects Enterprise web applications to a WebLogic cluster distributed over multiple machines.

weblogic.jaxp.xml in PerformanceManagement. you must first copy the wdeploy tool and environment to the machine hosting the WebLogic administration server.Transformer FactoryImpl 2. as_dir=/bea/user_projects/domains/base_domain as_instance=AdminServer as_admin_port=7001 as_admin_username=weblogic as_admin_password=password 4. You need to specify information for the server administrating the cluster as shown in the following example.configdir param in web. skip to step 6.jaxp. you must copy InitConfig. The modifiedweblogic.configdir</param-name> <param-value>/home/Performance_Management_120 </param-value> <context-param> 3. Modify the config.apache.0 Installation and Configuration Guide for UNIX . If BusinessObjects Enterprise is installed to the same machine hosting the WebLogic administration server.properties is matches the value specified for af.xerces.weblogic10 or the config.war to the WebLogic cluster. If BusinessObjects Enterprise and the WebLogic administration server run on different machines.xml file located in the following directory: <INSTALLDIR>/deployment/templates/weblogic.war as shown below: <context-param> <param-name>af.apache. Modify the PersistentStoreType setting in the weblogic.SAXParserFacto ryImpl Transformer Factory weblogic.11 Post Installation Web Application Deployment Manually deploying to a web application server Property Value Document Builder Facto.xml.apache. If you plan to deploy PerformanceManagement.DocumentBuilder ry FactoryImpl SAX Parser Factory weblogic.weblogic9 located in the following directory: <INSTALLDIR>/deployment/.xerces.xalan.xml settings will look like the example below: <weblogic-web-app> <session-descriptor> 198 BusinessObjects Enterprise XI 3.processor.properties from <INSTALLDIR>/Per formance_Management_120 to each managed server and ensure the file path of InitConfig.

To deploy dswsbobje.0 Installation and Configuration Guide for UNIX 199 . Go to Domain Structure > Deployments and click Install. The list of web applications contains the dswsbobje web application. 8. Click Lock & Edit. 6. After the"Select deployment targets" workflow is complete. 9.war to a directory on the WebLogic web application server. 4. Post Installation Web Application Deployment Manually deploying to a web application server 11 <session-param> <param-name>PersistentStoreType</param-name> <param-value>replicated</param-value> </session-param> </session-descriptor> 5.war web application has been successfully deployed. Use the WebLogic administration console to separately install each web application you want to deploy from the following directory: <INSTALLDIR>/deployment/workdir/weblogic10/application/. 7. BusinessObjects Enterprise XI 3. 8. Log on to the "WebLogic Administration Console". A message will be displayed when the dswsbobje. Browse to the extracted dswsbobje. 1. 3. web services applications may display the error message “An XSD Exception occurred”. Select the directory and click Next.sh weblogic10 predeployall 6.war directory. select all the installed applications and go to Start > Servicing all requests. In the "Select deployment targets"workflow select the cluster name and All servers in the cluster. Click Activate Changes. the user must extract dswsbobje.war.war to WebLogic Before deploying web services WAR file on a WebLogic application server. 5. Select the dswsbobje web application and click Start. 2. Verify the settings and click Finish. 10. If the WAR file is not extracted and redeployed. 7. Select Install this deployment as an application and click Next. Open a command-line console and run the following command: <INSTALLDIR>/deployment> wdeploy. Extract dswsbobje.

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. Log on to the "Tomcat Manager Console". Related Topics • After deploying web applications on page 192 Deploying with the Tomcat administrative console Ensure that your Tomcat web application server is installed. Press OK to confirm the changes. The context path must be the name of the WAR file. you need to deploy the web applications on to each Tomcat instance. Set the Context Path for the web application to be deployed. Enter the full path to the WAR file and press the Deploy button The WAR file you chose is deployed. 2. Select the dswsbobje web application and click Start. For example.war. configured. 12. and running before deploying WAR files. 13. but without its extension. to deploy a web application packaged as MyWebApplica tion. Related Topics • After deploying web applications on page 192 Special considerations for deploying on Tomcat clusters To manually deploy web applications to a Tomcat web application cluster distributed over multiple machines. Open the web application in a web browser to confirm that it now runs. • http://WAS_HOSTNAME:PORT/manager/html 1. the context path must be MyWebApplication. Set the XML Configuration File setting to be an XML file that contains the context path and document base. The dswsbobje web application is started.war" path="<context_path>" crossContext="false" debug="0" reloadable="false" trust ed="false"/> 3.11 Post Installation Web Application Deployment Manually deploying to a web application server 11.0 Installation and Configuration Guide for UNIX . 200 BusinessObjects Enterprise XI 3. For example: <Context docBase="<M>/WEB_APPLICATION.

The home group is displayed under the Groups heading. and PORT with the port number used for HTTP. Press the Next button to advance to the next step in the WAR deployment wizard. configured.0 Installation and Configuration Guide for UNIX 201 . 7. The Deploy: Select Archive window is displayed. By default. to the WAR file in the Archive Location field. in which case select Archive is already present on the server where Application Server Control is running. Enter the application name and context root of the file you wish to deploy. The default port for Oracle Application Server is 7777. In the home OC4J container. Click on the home OC4J container. or browse. Ensure that the Archive is present on local host option is selected. To configure the load balancer and cluster setup please consult your Tomcat documentation. 5. Replace WAS_HOSTNAME with the hostname or IP address of your web application server. BusinessObjects Enterprise XI 3. and running before deploying WAR files. click on the Applications tab. Deploy: Application Attributes is displayed. 2. the context root will contain the application name. 8. 3. 4. 6. 1. Deploying with the Oracle Application Server administrative console Ensure that your Oracle Application Server web application server is installed. Enter the full path. Open the Oracle Application Server Enterprise Manager server page at http://WAS_HOSTNAME:PORT/em. Click on the Deploy button. You must also have created an Oracle container for Java (OC4J) container in which to run BusinessObjects Enterprise. The Oracle Application Server Control page is displayed. Step 2 of 3. Post Installation Web Application Deployment Manually deploying to a web application server 11 Tip: It is recommended that you install and configure a hardware or software load balancer if running BusinessObjects Enterprise web applications on a Tomcat web application cluster. For example. unless the web application is already running on the server. Currently deployed web applications are displayed.

click on Configure Class Loading from the Deployment Tasks section. If your application requires any class libraries. The following deployment paths are based upon the different levels of service: 202 BusinessObjects Enterprise XI 3. and running before deploying WAR files. The Java Server Faces (JSF) bundled with the JBoss web application servers must be disabled for the Central Management Console (CMC) and InfoView web clients to work correctly. 9.11 Post Installation Web Application Deployment Manually deploying to a web application server for InfoView.0. To disable JSF. specify the location of JAR file containing the libraries.war.properties file . Related Topics • After deploying web applications on page 192 Deploying with the JBoss administrative console Ensure that your JBoss web application server is installed.sar/jsf- libs • JBOSS_HOME/server/default/tmp • JBOSS_HOME/server/default/work Note: To use the Javalog4j logging included with BusinessObjects Enterprise XI 3. 11.jboss. When ready.7 Using your own log4j. Click on the Deploy button to complete the deployment.0 Installation and Configuration Guide for UNIX . Deploy: Deployment Settings page is displayed. 10. Check the output of the Progress Messages log field that web application has been deployed. configured. the application name will be InfoView. refer to section 10.org/process-guide/en/html/logging.3.html#d0e3341. The Step 3 of 3. Select the class loading options you want enabled for the WAR file and press Next to proceed.class loader scoping in the JBoss Development Process Guide: http://docs. In the Configure Web Module Class Loaders field. the following directories must be removed and JBoss restarted: • JBOSS_HOME/server/default/deploy/jbossweb-tomcat55. press Next to proceed.

0 Installation and Configuration Guide for UNIX 203 . [ReportSourceBridge] Servlet viewrpt started. Check the JBoss server log. In the "Deploy Dialog" window.906 INFO. Copy your WAR files to the appropriate context root sub-directory under one of the above paths.. 2. and you should see a message similar to the one shown below to confirm that the WAR deployment succeeded. Click OK when done. 1. configured. select the EAR file archive you created earlier. based upon the level of service provided by JBoss for your deployment. The web application will now be deployed. Click Deploy & Start in the Runtime tab of the right-hand pane.. In the "Visual Administrator". Related Topics • After deploying web applications on page 192 Deploying with the SAP Application Server console Ensure that your SAP Application Server web application server is installed. Press OK to deploy.. 06:23:08.. verify the root context and display name properties. First. Connect to your J2EE engine using the Administrator account. select the Cluster tab and expand the Server > Services > Deploy node within the J2EE tree. The web application will be automatically deployed by JBoss when the file is copied to the appropriate directory. 3.war/ 06:23:09. In the "Deploy & Start" dialog window that appears. warUrl=./BusinessObjects Enterprise 12.562 INFO. Start the "Visual Administrator" tool by running go from <SAP_HOME>/sap/CTB/JC00/j2ee/admin. click the Deploy button instead. 5. archive your web application server.TomcatDeployer deploy. 4. Post Installation Web Application Deployment Manually deploying to a web application server 11 • JBOSS_HOME/server/all/deploy • JBOSS_HOME/server/default/deploy • JBOSS_HOME/server/minimal/deploy 1. and running before deploying WAR files. If you would like to start the web application manually later. ctxPath=./tmp/deploy/tmp38470admin-exp.0/adminlaunch. BusinessObjects Enterprise XI 3. 2.

businessobjects</sys:groupId> <sys:artifactId>CmcApp</sys:artifactId> <sys:version>2. use the directory that contains the web application code directly: <INSTALLDIR>/bobje/enterprise120/java/applications/ Log in to the WebSphere"Application Server Community Edition Administrative Console" using the following URL: http://WAS_HOST NAME:PORT/console The WebSphere Community Edition admin console's default port number is 8880. 2. Ensure the myfaces-deployer system module is turned off. You can only deploy web applications using the WebSphere Community Edition administrative console.apache.org/xml/ns/deployment-1.2"> <sys:environment> <sys:moduleId> <sys:groupId>com.0 Installation and Configuration Guide for UNIX . Here is a standard geronimo-web. Then click on the Expert User check box located at the top. and running before deploying web applications.1</sys:version> 204 BusinessObjects Enterprise XI 3.apache. Scroll down to find org. configured. 1. The myfaces-deployer module is turned off. To deploy BusinessObjects Enterprise web applications with the administrative console.0.xml file for use with CmcApp: <web-app xmlns="http://geronimo. Note: The wdeploy command-line deployment tool currently does not support deployment to WebSphere Community Edition.0.1/car and click on the Stop link. Add a geronimo-web.configs/myfaces-deployer/2.org/xml/ns/security-1.2" xmlns:sec="http://geronimo.11 Post Installation Web Application Deployment Manually deploying to a web application server Related Topics • After deploying web applications on page 192 Deploying with the WebSphere Community Edition administrative console Ensure that your WebSphere Community Edition web application server is installed.org/xml/ns/j2ee/web- 1. Click on the System Modules link on the Console Navigation bar.apache.0.apache.geronimo.apache.xml file to the WEB-INF directory of each web application file.2" xmlns:sys="http://geronimo.org/xml/ns/naming-1.2" xmlns:nam="http://geronimo.

Click Install to install the web application. use <sys:artifac tId>InfoViewApp</sys:artifactId> and <context-root>/In foViewApp</context-root>.xml to InfoViewApp. 7. After the web application is deployed. For example. Verify that the web application was deployed. Click the archive Browse button and navigate to the location of the directory that contains the web application to deploy. Post Installation Web Application Deployment Manually deploying to a web application server 11 <sys:type>war</sys:type> </sys:moduleId> <sys:dependencies/> <sys:hidden-classes> <sys:filter>com. 5. 3. 8.sun. Click the Install New button to view the "Install New Applications" screen. a list of installed web applications is displayed. <INSTALLDIR>/bobje/enterprise120/java/applications/ 6. such as Start app after install or Redeploy application. click Deploy New in the left navigational pane. 4.faces</sys:filter> <sys:filter>javax. Select any other options you want to use. Related Topics • After deploying web applications on page 192 BusinessObjects Enterprise XI 3. Repeat steps 2-5 for each application to deploy.faces</sys:filter> </sys:hidden-classes> <sys:non-overridable-classes/> </sys:environment> <context-root>/CmcApp</context-root> </web-app> Note: The sys:artifactId and context-root elements must be updated with the name of the web application being deployed. to add geronimo-web.0 Installation and Configuration Guide for UNIX 205 . Under the Applications heading of the console navigation menu.

11 Post Installation Web Application Deployment Manually deploying to a web application server 206 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX .

Deployment Scenarios 12 .

connecting to the BusinessObjects Enterprise back-end server behind a firewall. • Only the ports required for the communication between the desktop client and the server tier are open on the firewall. key tasks. Installation platform for BusinessObjects Enterprise Solaris 10 Database for Central Management Server (CMS) Oracle 10g R2 (10. • Server Tier: one machine for hosting the framework servers and another for all other BusinessObjects servers. Configuration details • A firewall exists between client and server tiers.12 Deployment Scenarios Overview of deployment scenarios Overview of deployment scenarios To improve your experience in installing and deploying BusinessObjects Enterprise this section provides two sample scenarios. key configuration details. functional requirements and pre-conditions. • Client Tier: one machine for installing and running Desktop Intelligence. • BusinessObjects servers are distributed over two machines. Each example includes a deployment diagram.Desktop Intelligence .0 Installation and Configuration Guide for UNIX . The scenarios focus on two deployment characteristics: • Desktop client to server • Basic n-tier Desktop client to server scenario Desktop client to server overview This scenario illustrates a simple client to server scenario which involves a desktop client application .2) 208 BusinessObjects Enterprise XI 3. These examples are for illustrative purposes. System layers • Data Tier: one machine with existing database server. • The firewall uses NAT (Network Address Translation).

Setting up the server tier. 4. Setting up the firewall. Setting up the client tier. 3. 1. 2. Deployment Scenarios Desktop client to server scenario 12 Web application server Not relevant Firewall Linux iptables Desktop client to server diagram The following diagram illustrates the system overview for the scenario once it is implemented. Setting up the data tier.0 Installation and Configuration Guide for UNIX 209 . BusinessObjects Enterprise XI 3. Summary of required tasks The desktop client to server deployment scenario involves the following tasks in the order listed below.

as well as auditing or Performance Management databases if required.12 Deployment Scenarios Desktop client to server scenario Deploying the client to server scenario To set up the data tier The following steps require that you have already installed a version of Sun Solaris 10 that meets the installation requirements for Oracle 10g R2. ensure that you have a working network connection between the machines. Note: In addition to databases for CMS. This is the database that hosts your organization's data. Install Oracle 10g R2. Setting Example Name of database server DBSERVER1_ora Administrator account name system Administrator account password password Database character set encoding UTF-8 An Oracle database is now installed and ready to be used by BusinessObjects Enterprise. Advanced administrative knowledge of Oracle Database and Sun Solaris 10 products is assumed. Additional database will be created for auditing or performance management if required. 2. 1. auditing. If your CMS and database servers are installed on separate computers. Create or import a new tablespace for the CMS. Record the settings used for creating of the CMS database. 210 BusinessObjects Enterprise XI 3. You will need these settings when you come to install BusinessObjects Enterprise servers and clients.0 Installation and Configuration Guide for UNIX . or performance management. against which BusinessObjects Enterprise applications run. This database will be used to hold CMS data. Make note of the following settings you use during the installation. you also require access to your existing corporate reporting database.

Deployment Scenarios Desktop client to server scenario 12 CMS database setting Example CMS tablespace name mycompany Username for CMS ta. Record the settings used for creating of the auditing tablespace. if required.0 Installation and Configuration Guide for UNIX 211 . Create or import a new tablespace for the Performance Management tablespace. create session. create session. Auditing database setting Example Auditing tablespace name bobjaudit Username for auditing tablespace audituser access Password for auditing tablespace auditpassword access System privileges for user access create table. 3. Create or import a new tablespace for the auditing database. create procedure An auditing database is now available for use. create procedure access A CMS tablespace is now available for use. Performance Management Example database setting Performance Management bobjpm database name Username for PM database ac. mycompanyuser blespace access Password for CMS ta. if required. mypassword blespace access System privileges for user create table. Record the settings used for creating of the Performance Management tablespace. 4.pmuser cess BusinessObjects Enterprise XI 3.

12 Deployment Scenarios Desktop client to server scenario Performance Management Example database setting Password for PM database ac./install. You have also installed a file repository server network-shared directory. Note: This scenario includes a network firewall between the CMS and database servers. as required. Extract the FRS template file (e. Create a network-shared directory on the database server's local file system to contain shared files for the file repository server (FRS). 5. The default listener port number used by Oracle is 1521.sh in the command line and press Enter. write. auditing. Verify the connectivity between your CMS and database machines by attempting to connect to your database(s) from the CMS server(s). create table. Mount the device that contains the installation files.pmpassword cess System privileges for user ac. 1.0 Installation and Configuration Guide for UNIX . Ensure that this firewall is configured appropriately. on which you will install a second set of server components. SERVER 2. 2. To set up the server tier You need to install and setup Solaris 10 on the two machines that will host the BusinessObjects Enterprise server components. The database port number must be entered during the BusinessObjects Enterprise installation. Note: The network permissions for FRS directory must included read. You have set up CMS. Remember: The ability to connect to your database server from your CMS server may require a change to the Solaris firewall settings on both machines. Designate a machine as SERVER 1 on which you will install framework servers. and execute permissions for the networked users. Type . create proce- cess dure A Performance Management tablespace is now available for use. 212 BusinessObjects Enterprise XI 3. create session.g. 6. Designate second machine. and performance management databases. FileStore_02-22-2008.zip) within the FRS directory you created in the last step.

3. The "Features" screen is displayed. Deselect the following top level features by typing X in all the corresponding markers. You are prompted to select either a user or system installation. Under Central Management Server deselect the following: BusinessObjects Enterprise XI 3. Type y to agree to the terms. 9. 7. 11.0 Installation and Configuration Guide for UNIX 213 . Select a language for the installation and press Enter. 8. Specify the installation directory for your BusinessObjects Enterprise installation. 4. Select user and press Enter. Deployment Scenarios Desktop client to server scenario 12 The installation setup program is launched. Items to deselect Client Components Server Components Ensure that the deselected features appear as [ ] before continuing. Enter your BusinessObjects Enterprise product activation keycode in the Business Objects Enterprise Product Keycode field and press Enter. 6. 10. The "Installation Type" screen is displayed. Select the language pack you want to install and press Enter. Expand Server Components and select the following: Items to select Central Management Server Event Server Input File Repository Server Output File Repository Server a. 5. The software license agreement is displayed. Select Custom from the list of options on the Installation Type screen and press Enter.

12 Deployment Scenarios Desktop client to server scenario Items to deselect Auditor MySQL b. 17. Press Enter. Select the Install Tomcat. 14. 16. The "Enter Server Intelligence Agent information screen" is displayed. A screen is displayed to provide configuration details for the oracle database server. Select Yes and press Enter. The "Enter the information for your new CMS" screen is displayed. 19. 15.0 Installation and Configuration Guide for UNIX . The "Please enter port numbers for the Tomcat installation screen" is displayed. the "Select Web Application Server" screen is displayed. Select Yes. Type the following details and press Enter. Press Enter to accept the default values in the Enter the information for your new CMS and leave the password fields blank. deploy web applications and press Enter. Press Enter to accept the default values. Type SIA_1 in Server Intelligence Agent Node and press Enter. You are prompted to select a system database option. Select Oracle and press Enter. 18. A screen is displayed with your specified installation directory. 214 BusinessObjects Enterprise XI 3. 13. You are prompted if this is the first CMS cluster in your deployment 12. Field Type the following Oracle TNSNAME DBSERVER1_ora User ID mycompanyuser Password mypassword A new screen prompts you about reinitializing the database.

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

You need to assign static port values to the following servers: Server name SIA_1. 15. Press Enter to start the installation. Press Enter to submit your custom installation sections. 14.CentralManagementServer SIA_1. 216 BusinessObjects Enterprise XI 3. The installation program validates your system before installing BusinessObjects Enterprise in the specified directory.OutputFileRepository 1. A screen is displayed with your specified installation directory. To assign static port values to servers Access the Central Management Console (CMC) on the machine named SERVER1. Type the following configuration information and click Log On. You are prompted to enter the name and port number of an existing CMS. Press Enter The "Enter Server Intelligence Agent information" screen is displayed.0 Installation and Configuration Guide for UNIX . 12.InputFileRepository SAI_1. 13. Type SIA_2 in Choose a name for the Server Intelligence Agent Node and Press Enter. and open a browser and type in the following URL: http://SERVER1:8080/Cm cApp/App/. Use the machine you designated to run the client tier.12 Deployment Scenarios Desktop client to server scenario Items to deselect Central Management Server Event Server Input File Repository Server Output File Repository Server Note: Ensure that the markers appear as [ ] before continuing. Type Server1 in CMS Hostname. leave Port and Existing CMS Administrator Password blank.

6404. Double-click the SIA_1. Click Servers under the "Organize" column. 4. such as the internet.OutputFileRepository 6406 You will need to pass the port numbers . The SIA_1. Repeat steps 3-5 for the following servers: Server name Port number to specify SIA_1. One network card (interface eth0) is connected to an internal secure network.CentralManagementServer entry. Click Save & Close. 3. Deselect Auto assign and type 6402 in Request Port under "Common Settings". 2.when configuring the firewall. BusinessObjects Enterprise XI 3. The list of available servers is displayed again. To configure the firewall The iptables firewall is running on a supported Red Hat Linux operating system with two network interface cards (NIC).0 Installation and Configuration Guide for UNIX 217 . the other (interface eth1) is connected to an external unsecured network. Note: Advanced administrative knowledge of Red Hat Linux products is required for these steps. 5.6402.CentralManagementServer properties are displayed. A list of all available servers is displayed in a new screen. and 6406 . 6.InputFileRepository 6404 SIA_1. Deployment Scenarios Desktop client to server scenario 12 Field Required configuration information System SERVER1 User Name Administrator Password BOBJ_admin Authentication Type Enterprise The CMC Home page is displayed.

open the Central Management Console (CMC) and go to Servers > Central Management Server > your server and note the number for Request Port and Name Server Port. 3. by becoming a member of the admin group. Determine the network IP address. Log in to your Red Hat Linux server. 2. • Output FRS port 6406. Note: As iptables is configured from the command-line. firewalled network (interface eth0). the sever named CMS Server uses two port numbers to communicate with clients. 218 BusinessObjects Enterprise XI 3. Note: This must be done for each port used by every server you want accessible from outside your network.12 Deployment Scenarios Desktop client to server scenario The following steps illustrate how to forward requests from clients on an unsecured external (interface eth1) network to the server tier running on a secure. Tip: The command ifconfig -a will display network interface information. Clients on an unsecured network outside the firewall can now access the server tier through the firewall. and media access card (MAC) information for each NIC in your system. This can be achieved with the su or sudo commands.0 Installation and Configuration Guide for UNIX . For example. Tip: To determine which ports are used by servers. Desktop Intelligence. You must forward both ports on the firewall's external NIC to the CMS server connected to the internal NIC. 1. you need root privileges. • CMS Request port: 6402. and the Connection Server. four ports must be forwarded to the server tier from external clients on the external network (eth1): • CMS Name Server port: 6400. Add exceptions to the iptables firewall rules that forward incoming client requests to the server tier on the appropriate ports. • Input File Repository Server (FRS) port: 6404. interface. Typical servers used by external clients include the CMS. Record the network information in a safe place. In this scenario. or by logging in as the root user.

Run setup. Deployment Scenarios Desktop client to server scenario 12 To set up the client tier Windows Server 2003 SP2 Enterprise Edition has to be installed and running on the machine on which you will install Desktop Intelligence. Click Install to launch the installation setup program. Follow the steps below to Desktop Intelligence and 1.exe from the root directory of your product distribution. 2. Select the language for the installation setup from the pull-down list provided and click OK. BusinessObjects Enterprise XI 3. "Please Choose Setup Language" is displayed.0 Installation and Configuration Guide for UNIX 219 . 3.

4.12 Deployment Scenarios Desktop client to server scenario The "Welcome to the BusinessObjects Enterprise XI 3. The "License Agreement" screen is displayed.0 Installation and Configuration Guide for UNIX .0 Installation Wizard" is displayed after you specify a language for the installation setup. Click Next to proceed with the installation setup. 220 BusinessObjects Enterprise XI 3.

The "Choose Language Packs" screen is displayed. Select I accept the License Agreement and click Next. The "Directory Selection" screen is displayed. BusinessObjects Enterprise XI 3. Deployment Scenarios Desktop client to server scenario 12 5. Select the language packs and click Next. 6.0 Installation and Configuration Guide for UNIX 221 .

Expand Client Components and left. 222 BusinessObjects Enterprise XI 3. 8. The "Select Features" screen is displayed. Left-click on the icon beside Client Components and select Entire feature will be unavailable.click on Desktop Intelligence. The Client Components icon changes to 9. Accept the default directory by clicking "Next".12 Deployment Scenarios Desktop client to server scenario 7.0 Installation and Configuration Guide for UNIX .

Click Next to start the installation.0 Installation and Configuration Guide for UNIX 223 . Deployment Scenarios Desktop client to server scenario 12 10. The installation process begins and is completed once "BusinessObjects Enterprise XI 3. 11. The "Start Installation" screen is displayed. Select Entire feature will be installed on local hard drive and click Next.0 Client Tool has been successfully installed" is displayed. BusinessObjects Enterprise XI 3.

Type SERVER1 for System. c. 224 BusinessObjects Enterprise XI 3. 14. The Desktop Intelligence is now installed on your machine.0 Installation and Configuration Guide for UNIX .0 > BusinessObjects Enterprise Client Tools > Desktop Intelligence The "User Identification" dialog is displayed. b. Click Finish.12 Deployment Scenarios Desktop client to server scenario 12. Go to Programs > BusinessObjects XI 3. Provide the following information: a. 13. Type Administrator for User Name. Type password for Password.

Deployment Scenarios Desktop client to server scenario 12 The "New Report Wizard" is displayed. 15. BusinessObjects Enterprise XI 3. Select Generate a standard report and click Begin.0 Installation and Configuration Guide for UNIX 225 .

226 BusinessObjects Enterprise XI 3.5 Firewall Linux iptables Basic n-tier diagram The following diagram illustrates the system overview for the scenario once it is implemented. • Web Tier: One machine in hosting the web application server. Configuration details Installation platform for BusinessObjects Enterprise Solaris 10 Database for Central Management Server (CMS) MySQL Web application server Tomcat 5. processing and performance management (PMC) servers.12 Deployment Scenarios Basic N-tier scenario Basic N-tier scenario N-tier scenario overview This section describes how to setup a scenario in which a web browser accesses BusinessObjects Enterprise system through web applications. System layers • Data Tier: One machine used to host the database server.0 Installation and Configuration Guide for UNIX . • Server Tier: Three machines hosting the framework. • Client Tier: One machine running the Live Office application.

Setting up the client tier Deploying the basic N-tier scenario To set up the data tier The following steps require that you have already installed a version of Sun Solaris 10 that meets the installation requirements for MySQL. Setting up the web tier 4. BusinessObjects Enterprise XI 3. Setting up the firewall 5.0 Installation and Configuration Guide for UNIX 227 . Setting up the server tier 3. Setting up the data tier 2. Deployment Scenarios Basic N-tier scenario 12 Summary of required tasks The basic n-tier deployment scenario involves the following tasks in the order listed below. 1. Advanced administrative knowledge of MySQL and Sun Solaris 10 products is assumed.

Note: In addition to databases for CMS. Additional database will be created for auditing or performance management if required. if required. you also require access to your existing corporate reporting database. Make note of the following settings you use during the installation. Create or import a new tablespace for the auditing database. 228 BusinessObjects Enterprise XI 3. You will need these settings when you come to install BusinessObjects Enterprise servers and clients. as well as auditing or Performance Management databases if required. Setting Example Name of database server DBSERVER1_mysql Administrator account name system Administrator account password password Database character set encoding UTF-8 A database is now installed and ready to be used by BusinessObjects Enterprise. ensure that you have a working network connection between the machines. Install MySQL. Record the settings used for creating of the CMS database. Create or import a new tablespace for the CMS. against which BusinessObjects Enterprise applications run. 1. CMS database setting Example CMS tablespace name mycompany Username for CMS tablespace access mycompanyuser Password for CMS tablespace access mypassword A CMS tablespace is now available for use. If your CMS and database servers are installed on separate computers. This is the database that hosts your organization's data. auditing.0 Installation and Configuration Guide for UNIX . or performance management. Record the settings used for creating of the auditing tablespace.12 Deployment Scenarios Basic N-tier scenario This database will be used to hold CMS data. 3. 2.

The database port number must be entered during the BusinessObjects Enterprise installation. 5. Create a network-shared directory on the database server's local file system to contain shared files for the file repository server (FRS).g. 4. The default listener port number used by MySQL is 3306. FileStore_02-22-2008. auditing. write. You have set up CMS. and execute permissions for the networked users. 6.zip) within the FRS directory you created in the last step. if required. as required. Note: The network permissions for FRS directory must included read. Performance Management database setting Example Performance Management database name bobjpm Username for PM database access pmuser Password for PM database access pmpassword A Performance Management tablespace is now available for use. Record the settings used for creating of the Performance Management tablespace. Ensure that this firewall is configured appropriately. Verify the connectivity between your CMS and database machines by attempting to connect to your database(s) from the CMS server(s). Note: This scenario includes a network firewall between the CMS and database servers. Create or import a new tablespace for the Performance Management tablespace. and performance management databases. Deployment Scenarios Basic N-tier scenario 12 Auditing database setting Example Auditing tablespace name bobjaudit Username for auditing tablespace access audituser Password for auditing tablespace access auditpassword An auditing database is now available for use.0 Installation and Configuration Guide for UNIX 229 . You have also installed a file repository server network-shared directory. Extract the FRS template file (e. BusinessObjects Enterprise XI 3.

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

You are prompted to provide information on the CMS you are about to install. Type the following information for the MySQL database and press Enter to submit the database configuration details. Press Enter to submit your custom installation selections. Field Enter the following DBSERVER1_mysql Host Name system User ID for CMS database BusinessObjects Enterprise XI 3. The MySQL configuration screen is displayed. 15.0 Installation and Configuration Guide for UNIX 231 . Expand Central Management Server and deselect MySQL and Auditor. 13. 14. You are prompted in a new screen to specify if this is your first CMS in your deployment. Deployment Scenarios Basic N-tier scenario 12 Items to deselect Server Components Note: Ensure that the markers appear as [ ] before continuing. Expand Server Components and select the following servers: Items to select Central Management Server Event Server Input File Repository Server Output File Repository Server 12. Press Enter to accept the default CMS settings. 16. 11. Select Yes . 17.this is the first CMS in this deployment. Select MySQL. You are prompted to select a database type for the CMS.

7. To add processing servers to the server tier You need to install the framework servers on SERVER 1 before you can add any servers to the server tier. Press Enter to start the installation. The installation program validates your system before installing BusinessObjects Enterprise in the specified directory. 1. The installation setup program is launched. 6. Type y to agree to the terms. The software license agreement is displayed. 3. A screen is displayed with your specified installation directory. The "Enter Server Intelligence Agent Information screen" is displayed./install. 2. Mount the device that contains the installation files. 4.0 Installation and Configuration Guide for UNIX . Type SIA_1 in Choose a name for the Server Intelligence Agent Node and Press Enter. Specify the installation directory for your BusinessObjects Enterprise installation. 19. Select a language for the installation and press Enter. 5. 232 BusinessObjects Enterprise XI 3. Select Yes press Enter. Select the language pack you want to install and press Enter. Type . Use the following instructions to add BusinessObjects Enterprise servers to the CMS cluster you have installed on SERVER 1. 18.sh in the command line and press Enter. 20.12 Deployment Scenarios Basic N-tier scenario Field Enter the following password Password for CMS database 3306 MySQL port number mycompany Database name for CMS A new screen prompts you about reinitializing the database. Enter your BusinessObjects Enterprise product activation keycode in the Business Objects Enterprise Product Keycode field and press Enter.

Scroll down the "Features" screen to access Dashboard and Analytics Servers. The "Installation Type" screen is displayed. The "Features" screen is displayed. Type SIA_2 in Choose a name for the Server Intelligence Agent Node and Press Enter. 12. The "Enter Server Intelligence Agent information" screen is displayed. leave Port and Existing CMS Administrator Password blank. Select user and press Enter.0 Installation and Configuration Guide for UNIX 233 . 14. Press Enter to submit your custom installation sections. Choose Custom or Expand in the "Installation Type" screen. 11. Deployment Scenarios Basic N-tier scenario 12 You are prompted to select either a user or system installation. Expand Server Components and deselect the following items: Items to deselect Central Management Server Event Server Input File Repository Server Output File Repository Server Dashboard and Analytics Servers Note: Ensure that the markers appear as [ ] before continuing. Deselect all the following top-level features by typing X in all the corresponding markers: Items to deselect Client Components Web Tier Components Note: Ensure that the markers appear as [ ] before continuing. 8. 10. 9. Press Enter. Type SERVER1 in CMS Hostname. 13. You are prompted to enter the name and port number of an existing CMS. BusinessObjects Enterprise XI 3.

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

The installation setup program is launched. Follow the procedure to install Tomcat 5. Expand Server Components and select Dashboard and Analytics Servers. leave Port and Existing CMS Administrator Password blank. 3. 1. Type . Type SERVER1 in CMS Hostname. Press Enter The "Enter Server Intelligence Agent information" screen is displayed. Type SIA_3 in Choose a name for the Server Intelligence Agent Node and Press Enter. 5. Select a language for the installation and press Enter. BusinessObjects Enterprise XI 3. Note: Scroll down the "Features" screen to access Dashboard and Analytics Servers. To set up the web tier Sun Solaris 10 has to be installed and running on the machine that will host the web tier. Deployment Scenarios Basic N-tier scenario 12 Note: Ensure that the markers appear as [ ] before continuing. 12. Enter your BusinessObjects Enterprise product activation keycode in the Business Objects Enterprise Product Keycode field and press Enter.0 Installation and Configuration Guide for UNIX 235 . 2. Press Enter to submit your custom installation sections./install. Type y to agree to the terms. 13. 14. You are prompted to enter the name and port number of an existing CMS. A screen is displayed with your specified installation directory. Press Enter to start the installation. Mount the device that contains the installation files. Specify the installation directory for your BusinessObjects Enterprise installation. 4.sh in the command line and press Enter.5 and deploy the BusinessObjects Enterprise web applications. The installation program validates your system before installing BusinessObjects Enterprise servers in the specified directory. 6. 11. 15. The software license agreement is displayed.

To configure the firewall The iptables firewall is running on a supported Red Hat Linux operating system with two network interface cards (NIC). Press Enter to accept the default settings. You need provide the default port settings for the Tomcat Server to setup the firewall. Select user and press Enter. Type SERVER1 in the CMS Hostname and press Enter to accept default values for the other settings. 12. Select Install Web Tier features in the "Installation Type" screen. The following steps illustrate how to forward requests from clients on an unsecured external (interface eth1) network to port 8080 on for a Oracle Application Server 10g R3 web application server running on a secure. The "Installation Type" screen is displayed. 14. A screen is displayed with your specified installation directory. 9. 8. One network card (interface eth0) is connected to an internal secure network. firewalled network (interface eth0). the other (interface eth1) is connected to an external unsecured network. You are prompted to select what kind of Java application server to install. Select the language pack you want to install and press Enter. Select Install Tomcat. 236 BusinessObjects Enterprise XI 3. Press Enter to accept default port numbers for the Tomcat server. The installation program validates your system before starting the installation.12 Deployment Scenarios Basic N-tier scenario 7. 13. You are prompted to specify an existing CMS for the web tier features. 11. Press Enter to start the installation. The Tomcat configuration screen is displayed.0 Installation and Configuration Guide for UNIX . You are prompted to select either a user or system installation. deploy web applications. such as the internet. 10. The "Features" screen is displayed. Note: Advanced administrative knowledge of Red Hat Linux products is required for these steps.

Deployment Scenarios Basic N-tier scenario 12 1. 1. 5.0 CD into your computer CD-ROM drive. Record the network information in a safe place. or by logging in as the root user. 6. Insert the BusinessObjects Live Office XI 3. 2. 3. Click Start > Programs > Microsoft Office. you need root privileges.0 Installation and Configuration Guide for UNIX 237 . The Live Office Installation Wizard is displayed. When the Options dialog box appears. Clients on an unsecured network outside the firewall can now access the web application server through the firewall on port 8080. 4. Follow the on-screen instructions in the Live Office Installation Wizard to complete the installation procedure. interface. and select Microsoft Excel. To set up the client tier You need to install Microsoft Office 2003 on the machine on which you run the client tier. Word. This can be achieved with the su or sudo commands. enter your BusinessObjects Enterprise credential in the following fields: • User name • Password BusinessObjects Enterprise XI 3. by becoming a member of the admin group. 3. Tip: The command ifconfig -a will display network interface information. or PowerPoint to launch the application. Choose your preferred language for the installation setup from the list on the left and click Install. Add an exception to the iptables firewall rules that forwards incoming client requests on port 8080 to port 8080 on the web application server. 2. Note: As iptables is configured from the command-line. Determine the network IP address. Log in to your Red Hat Linux server. and media access card (MAC) information for each NIC in your system. Click LiveOffice > Options > Enterprise.

click Log On and then click OK. 8.12 Deployment Scenarios Basic N-tier scenario 7. Enter http://WEBSERVER1:8080/dswsbobje/services/session in the Web Service URL and System fields. 238 BusinessObjects Enterprise XI 3. Select the Enterprise authentication method from the drop-down list.0 Installation and Configuration Guide for UNIX .

Get More Help A .

The online documentation library has the most up-to-date version of the Business Objects product documentation.businessobjects. customized embedding technology. and support forums. in connectivities. Expertise is available in relational and multidimensional databases. The library is updated regularly with new content as it becomes available. Find more information on the Business Objects Education web site: http://www. For more information.com/documentation/product_guides/ Additional developer resources http://devlibrary. You can browse the library contents.A Get More Help Online documentation library Business Objects offers a full documentation set covering all products and their deployment. http://support.com Online customer support The Business Objects Customer Support web site contains information about Customer Support programs and services.com/support/ Looking for the best deployment solution for your company? Business Objects consultants can accompany you from the initial analysis stage to the delivery of your deployment project. database design tools. and download PDF versions. It also has links to a wide range of technical information including knowledgebase articles.businessobjects. read guides on line.com/services/training 240 BusinessObjects Enterprise XI 3. we can offer a training package to suit your learning needs and preferred learning style. downloads.businessobjects.businessobjects.businessobjects. contact your local sales office. or contact us at: http://www. and more.com/services/consulting/ Looking for training options? From traditional classroom learning to targeted e-learning seminars.0 Installation and Configuration Guide for UNIX . do full-text searches. http://www.

com. 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.businessobjects.0 Installation and Configuration Guide for UNIX 241 . visit: http://www.com/support/. BusinessObjects Enterprise XI 3. please contact our Customer Support experts. and we will do our best to ensure that your suggestion is included in the next release of our documentation: mailto:documentation@businessobjects.businessobjects. For information about Customer Support visit: http://www.com Note: If your issue concerns a Business Objects product and not the documentation. Business Objects product information For information about the full range of Business Objects products.

A Get More Help 242 BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for UNIX .

0 Installation and Configuration Guide for UNIX 243 .Index A D adding performance management 141 database AddOrRemovePrograms. 192 WebLogic 196 C WebLogic clusters 197 WebSphere 193 ccm. complex custom or expand installation 76 installing language packs 133 available features 76 BusinessObjects Enterprise XI 3. 98 client tools. installing 28 select supported web application 67. 103 preparing your existing 35 database server options MySQL 32 B tested database servers 30 basic web tier scenario database server preparations 35 configuration details 226 database setup 36 diagram 226 database. 87. 87. 103 documentation 10 BusinessObjects Enterprise JBoss 202 documentation 10 Oracle Application Server 201 new features 12 SAP Application Server 203 uninstalling 140 Tomcat 200 uninstalling from UNIX 140 Tomcat clusters 200 verifying 156. 43 system layers 226 deployment BobjEnterprise120 73. CMS 32 overview 226 DB2 32. 93. 93. CMS database 98 on UNIX 43 deployment scenarios setting up on UNIX 32 desktop client to server 208 copying the product distribution 54 general overview 208 custom installation 26 deployments. 87. 98 checklist for installation 52 manual deployment 67.sh 140 permissions 36 automated startup on UNIX 73.sh 126 WebSphere cluster 194 CD 54 WebSphere Community Edition 204 copying to your machine 54 deployment options running the install from 54 install Tomcat 67.

85 firewall specifying CMS clustering 82 iptables configuration 217 specifying CMS port 63 firewalls 22 starting the installation 72. 97 distributed installation 76 CMS administrator password 63 dswsbobje.sh 53. 99 configuring MySQL installation 66 configuring Tomcat 68. 98 Server Intelligence Agent 67. 92.war configuring existing database 64 WebLogic deployment 199 configuring existing server 68.Index distributed install installation setup (continued) BusinessObjects Enterprise 76 clustering to a CMS 87. 102 use existing database 63 I installation type user vs system 23 Import Wizard 28 web tier 96 install types 25 installation types 27 client tools 28 web tier 27 custom installation 26 installing 28 install. 86. 41 selecting new 62 Sybase 42 selecting setup language 56 selecting user or system 58 selecting web application server option 67. 43 installation directory 57 environment variables installing language packs 57 DB2 39 mounting files 56 MySQL 38 selecting installation type 59 Oracle 38.sh 126 entering product keycode 57 environment install MySQL 63 database 32. F 87. 98 E enable servers 62 enabling servers. 88. 55 client tools 28 installation on UNIX 53. 55 running scripted 107 iptables 217 web application server 50.0 Installation and Configuration Guide for UNIX . 89. 149 installation checklist 52 installation log file 146 J installation on UNIX JBoss system vs user 59 manual deployment 202 installation overview 16 installation setup accepting license agreement 57 clustering servers 85 244 BusinessObjects Enterprise XI 3. with ccm.

sh 141 setup 127 Testing MySQL database environment variables post install deployments 126 38 preparing for installation 52 Tomcat preparing your database server 35 manual deployment 200 Publishing Wizard 28. 103 P system requirements 16 performance management adding to installation 141 T AddOrRemovePrograms. 85 servers assigning static ports 216 O servers starting with ccm. Index L R language packs response file definition 132 parameter list 108 English fallback 132 fallback to English 132 installation on UNIX 133 S installing 134 SAP Application Server locale 132 manual deployment 203 locating 134 scripted installation manual deployment 133 parameter list 108 Product Locale 132 running 107 selecting locale 132 scripted installation on UNIX 106 silent mode 135 server uninstalling 136 choosing location 25 log file server communication installation 146 multiple NIC hosts 23 set up 23 M Server Intelligence Agent specifying node name 67. 98 Tomcat clusters manual deployment 200 BusinessObjects Enterprise XI 3. 93. 88. starting with ccm. 43 servers. 73.sh 126 Oracle Application Server side-by-side installation 29 manual deployment 201 silent installation on UNIX 106.0 Installation and Configuration Guide for UNIX 245 .sh 126 Oracle 32. 53 specifying port numbers 68. 85 MySQL 32 specifying port 67. 117 Sybase 32. 43 system installation on UNIX 59.

98 host name requirements 22 Web application server network requirements 22 initial installation 50. 89. 88. 98 user rights WebLogic deploying web applications 18 manual deployment 196 WebLogic clusters manual deployment 197 W WebSphere WAR file JSF implementation 159. 149 required commands and utilities 20 web services 185 setting the locale 20 web tier 27 setting up your system 20 web tier installation user vs system installation 23 available features 97 UNIX permissions 17 clustering to a CMS 87. 192 manual deployment 193 war files WebSphere cluster configuring 182 deployment 194 deploying to remote server 182 WebSphere Community Edition WAR files manual deployment 204 context roots 186 Windows deployment guidelines 187 BusinessObjects Enterprise war services 185 client tools installation 28 wdeploy Import Wizard 28 functionality 150 Publishing Wizard 28 log file 155 scripted 106 options 155 silent installation 106 prerequisites 149 246 BusinessObjects Enterprise XI 3. 194 verifying deployment 156. 99 environment 20 configuring Tomcat 68.sh with SAP Application Server 176 running 140 with WebLogic 163 procedure 140 with WebSphere 156 uninstalling from UNIX 140 web application deployment UNIX 20 on remote machines 182 character set translation 20 web application server creating login environment 21 configuring existing server 68.Index U wdeploy (continued) Tomcat 168 Unicode 32 with JBoss 179 uninstalling with Oracle 173 AddOrRemovePrograms.0 Installation and Configuration Guide for UNIX . 87. 97 user installation on UNIX 59 selecting deployment option 67.