xi3-1 update en

8/6/2019 Xi3-1 Update En

1/42

BusinessObjects XI 3.1 Update

Installation and Deployment Guide

BusinessObjects XI 3.1


2/42

2008 Business Objects, an SAP company. All rights reserved. Business Objects

owns the following U.S. patents, which may cover products that are offered and

Copyright

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

its logos, 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 and its logos , 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. SAP is the trademark or registered

trademark of SAP AG in Germany and in several other countries. All other names

mentioned herein may be trademarks of their respective owners.

Business Objects products in this release may contain redistributions of software

licensed from third-party contributors. Some of these individual components may

Third-party

Contributors

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-10-14


3/42

ContentsOverview 5Chapter 1

Prerequisites 7Chapter 2

Installable packages ...................................................................................9

Upgrading multi-language systems...........................................................10

Recommended minimum disk space values ............................................10

Uninstalling update packages....................................................................11

Installation scenarios 13Chapter 3

Installation on a single machine................................................................14

Installation in a distributed environment ...................................................14

Installation of the update packages on Windows 17Chapter 4

To install the update packages on Windows .............................................18

To uninstall the update package on Windows ..........................................19

Silent Installation on Windows...................................................................20

Response files......................................................................................23

Manual deployment of web application files..............................................28

Installation of Update packages on UNIX 29Chapter 5

Configuration backup and restore ............................................................30

To install the update on UNIX....................................................................30

To uninstall the update on UNIX ...............................................................31

Silent Installation on UNIX.........................................................................31

Response files......................................................................................32

BusinessObjects XI 3.1 Update Installation and Deployment Guide 3


4/42

Manual deployment of web application server components - UNIX .........36

Get More Help 37Appendix A

Index 41

4 BusinessObjects XI 3.1 Update Installation and Deployment Guide

Contents


5/42

Overview

1


6/42

This guide provides you with information and procedures for installing and

deploying the BusinessObjects Enterprise XI Update Packages. This guide

is intended for the system administrator or IT professional who is responsible

for the installation, deployment, and maintenance of BusinessObjectsEnterprise. Familiarity with your overall network environment, port usage,

database environment, and web application server software is beneficial.

Please refer to this additional documentation available on the Business

Objects Customer Support site at http://support.businessobjects.com/docu

mentation/product_guides/default.asp.

Also please refer to the BusinessObjects XI Updater Release Notes.


Overview

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


7/42

Prerequisites

2


8/42

Update packages and Fix Packs are released on a regular schedule. You

can upgrade from the latest main release, Update package, or Fix Pack

directly to the most recently released update (i.e. without installing any of

the intermediate fix packs).You can upgrade to 3.1 directly from any fix pack level (e.g. from 3.0 Fix

Pack X to 3.1), but if your current fix pack was released on a date after the

availability of 3.1, some of the upgrades you currently enjoy may not have

been incorporated. Therefore, we recommend that after upgrading to 3.1,

you also immediately apply the latest available 3.1 Fix Pack.

Note:

Please ensure that all components of your BusinessObjects Enterprise

deployment, including any client tools and Crystal Reports components on

user's machines, are at the same patch level before you start using the

system. If the components are at different patch levels this may prevent them

from communicating properly.

Note:

It is strongly recommended that you follow your normal procedures for backing

up your deployment, prior to installing any patch. Even though the update

package has gone through extensive testing, the update should be applied

to a test system and verified before deploying on your production system.

Note:

If you install a new BusinessObjects product or component to your systemafter the Update package in installed, you must apply the update to the

machine where you installed the new product or component to ensure that

all BusinessObjects products and components are at the same version level.

Note:

Query as a Web Service and Universe Builder require the Microsoft .NET

2.0 Framework.

Updates and Fix Packs must be uninstalled in the reverse order to which

they were installed (e.g. if you installed Fix Pack 1, then the 3.1 Update, you

must uninstall the Update, then the fix pack). Because of this, when you view

the list of available programs on the uninstall interface, the BusinessObjects

XI heading will have only one subheading, for the most recently installed fix

or service pack. Once the uninstall is complete the next service or fix pack

in the sequence will be displayed (if applicable).


Prerequisites

2 Installable packages


9/42

Installable packages

For BusinessObjects XI 3.1 there is an individual Update Package for each

BusinessObjects product. This is a change from the Service Pack scheme

in previous releases which offered a single, suite-wide update for all

BusinessObjects products.

The introduction of individual Update Packages for BusinessObjects products

is intended to provide customers with smaller packages that are easier to

deploy.

Upate packages are available for the following products.

BusinessObjects Enterprise XI

BusinessObjects Enterprise XI Client ToolsNote:

If you installed client tools using the Client Tools option from the full

BusinessObjects Enterprise XI installer, you will need to use the

BusinessObjects XI Update Package to update those tools. The Client

Tools Update Package will only work if the tools were installed by

BusinessObjects Enterprise XI Client Tools installer.

Live Office XI

Crystal Reports 2008

Process Tracker XI SAP Integration for BusinessObjects XI

PeopleSoft Ingetration for BusinessObjects XI

Table 2-1: Packages available by operating system

HP-PA RISCLinuxAIXSolarisWin

dowsService Pack

YYYYYEnterprise XI

YClient Tools XI

YLive Office XI

YCrystal Reports 2008


2Prerequisites

Installable packages


10/42


11/42

Uninstalling update packages

Updates and fix packs must be uninstalled in the reverse order to which they

were installed (e.g. if you installed Fix Pack 1, then the 3.1 Update package,

you must uninstall the service pack, then the fix pack). Because of this, when

you view the list of available programs on the Windows uninstall interface,

the BusinessObjects XI heading will have only one subheading, for the most

recently installed fix or service pack. Once the uninstall is complete the next

service or fix pack in the sequence will be displayed (if applicable).


2Prerequisites

Uninstalling update packages


12/42


Prerequisites

2 Uninstalling update packages


13/42

Installation scenarios

3


14/42

Installation on a single machine

If all of your BusinessObjects components have been installed on a singlemachine, then you will need to apply all the required Update packages to

that machine.

For instance, to apply the service pack to a machine that has BusinessObjects

Enterpirse XI and Crystal Reports installed, you will need to install the update

packages for the following products:

1. BusinessObjects Enterprise XI

2. Crystal Reports

Installation in a distributed environmentSome BusinessObjects components reside on servers but others reside on

individual client machines. The corresponding update packages must be

applied on each machine that contains a BusinessObjects component.

Note:

If you used the BusinessObjects Enterprise Installer to install any client

components, you must also use the Enterprise update package. Only client

components installed using the Client Tools Installer can be upgraded by

the Client Tools update package.

Example: Sample deployment

Table 3-1: Sample Deployment

BusinessObjects ComponentsMachine

Crystal Reports

Client

Business Objects Client Tools

BusinessObjects EnterpriseBusinessObjects server

Tomcat web application serverWeb Application server



3 Installation on a single machine


15/42

The deployment illustrated in Table 1 would require the following upgrade

packages.

1. The client machines would require the BusinessObjects Enterprise Client

Tools and Crystal Reports 2008 update packages.2. The BusinessObjects server would require the BusinessObjects Enterprise

update package.

3. The web application serverwould also require theBusinessObjectsEntperise

update package.


3Installation scenarios

Installation in a distributed environment


16/42



3 Installation in a distributed environment


17/42

Installation of the updatepackages on Windows

4


18/42

Use the following instructions to install the update packages on Windows

machines.

It is recommended that you stop all the BusinessObjects Enterprise servers

except the Central Management Server before running the update package.

To install the update packages onWindows

The following steps are applicable to these update packages for the following

products:

BusinessObjects Enterprise

BusinessObjects Enterprise Client Tools

Live Office XI

Crystal Reports

Process Tracker XI

SAP Integration for BusinessObjects XI

Note:

You may encounter the following Windows system message if you are

installing one of the larger packages: Error 1718. File was rejected by

digital signature policy. If this occurs, exit the BuisinessObjects installwizard and go to the Microsoft support site. Search the Knowledgebase

for article 925336 and install the Windows patch referenced in the article.

Restart the BusinessObjects install wizard and proceed with these

instructions.

When installing the Business Objects Enterprise update, after clicking

Setup.exe, you may experience a delay of roughly 30 minutes before

the installation wizard starts. (The delay will vary depending on machine

specifications; forminimum systemrequirements pleasesee the "Products

Availability Report") Please do not restart your machine and allow the

installation program to start the process.

1. Launch the installation by running setup.exe.

2. On the "Welcome" dialog box, click Next.

3. On the "License Agreement" dialog box, review the content of the End

User License Agreement and click Next to proceed if you agree to the

terms.


Installation of the update packages on Windows

4 To install the update packages on Windows


19/42

4. Provide your CMS name and login credentials, and click Next.

Note:

If you are installing the upgrade on clustered backend servers, the name

and credentials for the first CMS you upgraded in the cluster must alsobe used when upgrading the other servers in that cluster.

5. On the "Start Installation" dialog box, click Next to begin the installation.

The "Installation Progress" dialog box appears.

6. After the installation is complete, check to see if any BusinessObjects

Enterprise servers are still stopped. If any servers have not restarted,

start them manually through the Central Management Console (CMC),

or the Central Configuration Manager (CCM).

Note:

To review details of the installation, you can view the contents of theinstallation log file located in the default installation path: C:\Program

Files\Business Objects\BusinessObjects Enterprise 12.0\Logging.

If the installation directory was modified at the time of the original installation,

the log files are written to that directory.

To uninstall the update package onWindows

Uninstalling the update package will revert your system to a fully functional

XI 3.0 installation.

We recommend that you uninstall the update package from the Add or

Remove Programs interface on the Windows Control Panel.

If you have applied more than one update package, they must also be

removed in the reverse order to which they were installed.

To remove an update package from Windows:

1. Go to Start > Settings > Control Panel and double-click Add or RemovePrograms.

2. Select BusinessObjects Enterprise XI 3.1 Update and click Remove.

The "Add or Remove Programs" dialog box prompts you to confirm that

you want to remove the update from your computer.

3. Click Yes.


4Installation of the update packages on Windows

To uninstall the update package on Windows


20/42

4. When the appropriate files are removed and the necessary configuration

is carried out, click Finish.

BusinessObjects XI update has been uninstalled and you are returned to

the "Add/Remove Program Properties" dialog box.Note:

After the uninstallation of upgrade package, the .war files located under

C:\Program Files\Business Objects\BusinessObjects Enterprise

12.0\java\applications are notautomatically redeployed by theupdate

package uninstaller. Therefore you need to manually redeploy the .war

files.

Update packages may also be uninstalled silently. See the section Silent

Installation on Windows on page 20 for more information.

Silent Installation on Windows

A silent installation is one that you run from the command line to automatically

install software on any machine in your system, without the installation

program prompting for information during the installation. The silent

installation is particularly useful when you need to perform multiple

installations and do not want to interrupt people who are working on machines

in your system.

You can also use the silent installation command in your own scripts. Forexample, if your organization uses scripts to install software on machines,

you can add the silent update package command to your scripts to run the

update package silently.

You also have the option of running a silent install from a Response File. A

response file is simply a file that contains the configuration information that

would normally be entered in the setup Wizard. See the Response File

section for more details.

Under Windows, running the silent installation without a Response File

consists of the command setup, followed by one of several options listed in

the following table. To use an option, place it on the command line after the

setup command. For example, type setup CLIENTLANGUAGE=EN /qn if

you want to run setup.exe in silent mode without displaying any installation

dialogs while automatically deploying web application server components

and restarting BusinessObjects Enterprise services.



4 Silent Installation on Windows


21/42

The following table describes the command line options available for a silent

installation. To use an option, place it on the command line after the setup

command.

This example runs the setup program without any prompting, including theprompt for install language and shows the progress bar through completion.

setup.exe CLIENTLANGUAGE=EN /qn /qb

Table 4-1: Service Pack 1 Silent Install Command Line Parameters

DescriptionParameter

When set to 1 (i.e. AUTODE-

PLOY_WARFILES=1), the option in-

structs the update package to automat-ically deploy web application server

components (.war files) on the Tomcat

web application server.

If not specified or set to 0, the .war

files must be manually deployed after

the install is complete. This is an op-

tional parameter.

AUTODEPLOY_WARFILES





22/42


Use this to specify the Language ver-

sion code for the installation. For English, enter EN.

For French, enter FR.

For German, enter DE.

For Spanish, enter ES.

For Japanese enter JP.

For Simplified Chinese, enter CHS.

For Traditional Chinese, enter CHT.

For Korean, enter KO.

For Dutch, enter NL.

For Swedish, enter SV.

For Italian, enter IT.

For Portuguese, enter PT.

For Russian, enter RU.

Note:

If you do not enter this parameter, the

regular language selection screen ap-

pears at the beginning of your install,

even if you specified the parameters

for a no prompt installation.

CLIENTLANGUAGE

Use this option so the user is not

prompted during the install, or when

the installation is complete. To prompt

when the installation is complete,

specify /qn+.

/qn

Use this option to display a progress

indicator during the installation. To

prompt when the installation is com-

plete, specify /qb+.

/qb

This will configure the install using pa-

rameters set up in a pre-defined .ini

file.

-r .ini





23/42

Response files

A response file is a test file that can be used to record responses to thedifferent screens of the install wizard. This allows you to easily run identical

silent installs on multiple of machines while only going through the install

wizard steps once.

To run a silent installation using a response file (Windows)

To run a silent installation using a response file you must first create a .ini

file using the BusinessObjects setup program. Once you have created the

.ini file, you can run a silent installation by running the setup.exe commandand specifying the path to the .ini file.

1. Create an installation .ini file (a response file).

a. Open a command line console.

b. From the directory that contains the BusinessObjects setup.exe file,

run the setup.exe command with the write option (-w) specified:

setup.exe -w responsefilepath\filename.ini

where responsefilepath is the location where you want the file

created and filename.ini is the name you have given to theresponse file.

c. Press Enterto launch the installation setup program.

d. Follow the on screen instructions to enter your preferred installation

settings until you reach the Start installation dialog of the setup

program.

e. Click Cancel to abort the installation setup.

All parameters from the installation setup program, both user defined

and default, are recorded in the .ini file which is saved to the directory

you specified.2. You can now run a response file installation using the .ini file by issuing

setup.exe command with the read option specified (-r):

setup.exe -r





24/42

where is the path to the .ini file you

created.

Note:

You can specify the -l option when running a response file installation tocreate an installation log file in the specified file path. If a file path is not

specified, the log file is created in the folder that contains the setup files.

-l

Silent installation parameters (Windows)

The following table lists parameters that are used for response file silent

installation on Windows. It is recommended that you create response filesusing the BusinessObjects setup program (setup.exe).


Specifies a silent installation./qa

Specifies not to prompt during the installation.

Note:

You must also enter the CLIENTLANGUAGE parameteras part of your silent install string or the language selection

screen will appear at the beginning of your installation.

/qn

Specifies to prompt when the installation is complete.

Note:

You must also enter the CLIENTLANGUAGE parameter

as part of your silent install string or the language selection

screen will appear at the beginning of your installation.

/qn+





25/42


Specifies that an administrator credential must be passed

to access the web application server. This setting only validfor WebSphere 6 and Oracle.

AS_ADMIN_IS_SECURE="true"

AS_AD

MIN_IS_SE

CURE

Password used by the administrator account to access the


AS_ADMIN_PASSWORD="pass"

AS_AD

MIN_PASS

WORD

Administration port of the application server.Mandatory for NetWeaver, Oracle Application Server, and

WebLogic.

For WebSphere, the SOAP port. If not set, the default

SOAP port will be used.

For Oracle Application Server (oas1013): wdeploy ex-

pects the request port of the ele-

ment in the [opmn.xml] file.

AS_AD

MIN_PORT

Specifies the account name used by the administrator toaccess the web application server.

AS_ADMIN_USERNAME="admin"

AS_AD

MIN_USER

NAME

Specifies the installation directory for the web application

server.

AS_DIR="/Tomcat55"

AS_DIR

Specifies the name of the current web application serverinstance.

AS_INSTANCE="localhost"

AS_INSTANCE





26/42


Web application type used in installation. the following op-

tions are available: Use tomcat55 for Tomcat

Use oas1013 for Oracle Application Server 10g R3

Use weblogic9 for WebLogic 9


Use websphere6 for WebSphere 6.1

AS_SERVER="tomcat55"

AS_SERVER

Specifies the name of the Windows service if the application

server will be installed as a service on Windows.

AS_SERVICE_NAME="BOE120Tomcat"

AS_SERVICE

NAME

Specifies virtual host to which the application must be

bound.

AS_VIRTUAL_HOST="hostname"

AS_VIRTU

AL_HOST

Specifies if a log file will be created for the installation.

ENABLELOGFILE="1"

ENABLELOG

FILE

Specifies if the web application (.war) files are to be auto-

matically deployed by the installer.

To have the installer automatically deploy .war files enter

AUTODEPLOY_WAR_FILES=1.

To deploy .war files manually after the installer runs, enter

AUTODEPLOY_WAR_FILES=0

AUTODE

PLOY_WAR_FILES

Specifies the directory where you want to install Busines-

sObjects.

INSTALLDIR="C:\Program Files\Business Objects\"

INSTALLDIR





27/42


Specifies the name of the BusinessObjects Centeral Man-

agment Server (CMS) the service pack will be applied to.

NAMESERVER

Specifies the port used to communicate with the CMS

specified in NAMESERVER.

NSPORT

Specifies the user name the installer will use to access the

CMS specified in NAMESERVER. Please use your Admin-

istrator account.

CMSUSER

NAME

The password for the user account specified under CMSUSERNAME.

CMSPASS

WORD

Specifies the authentication type used to log in to the

BusinessObjects Centeral Management Server.

"Enterprise"

"WindowsNT"

"LDAP"/

CMSAUTHEN

TICATION

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

Parameter name

ADDLOCAL

ADDSOURCE

ADVERTISE

REINSTALL





28/42

Parameter name

REMOVE

SKIP_DEPLOYMENT

WDEPLOY_LATER

Manual deployment of web applicationfiles

For instructions on deploying web application (.war) files manually, pleasethe the Web Application Deployment Guide for Windows, available at

http://support.businessobjects.com.



4 Manual deployment of web application files
http://support.businessobjects.com/http://support.businessobjects.com/


29/42

Installation of Updatepackages on UNIX

5


30/42

The in-place upgrade of the installation involves backing up the affected

BusinessObjects XI components and installing the corresponding 3.1

components.

It is recommended to stop BusinessObjects servers, except for the CentralManagement Server (CMS), prior to installing any update packages.

Note:

After shutting down BusinessObjectsEnterprise processes with the command

stopservers, check with the command ps to see if any processes still remain.

Manually stop these processes (except the CMS) in this case.

Configuration backup and restore

The update package uninstall scripts for UNIX will not reverse configuration

changes that are made when the update is installed. Some of these changes

may cause residual effects that may negatively affect your environment.

Therefore, it is recommended that you create a backup copy of/setup/boconfig.cfg before installing the update and restore

these settings after uninstalling the update package.

Note:

When uninstalling an update on a system where multiple updates have been

applied, be sure to resotre the backup copy ofboconfig.cfg thatcorresponds to the udpate you are reverting to.

To install the update on UNIX

Installation of the update package using the Installation Wizard is described

below:

1. Launch the installation by inputting the following in a command line where

your installation package is located: ./install.sh

2. Review the content of the License agreement and select Y to proceed if

you agree to the terms.

3. Press Enterto proceed.

You are prompted to confirm that the installation can begin.

4. Press Enterto proceed.


Installation of Update packages on UNIX

5 Configuration backup and restore


31/42

The progress indicator displays the status of the installation.

Note:

A backup of all the files being modified by the udpate is created in the

INSTALL DIR/setup/backup directory.

5. Press Enterto complete the installation.

Note:

To review details of the installation, view the contents of the installation

log file located in /setup/logs, where is

the name of the installed product.

To uninstall the update on UNIXThe servers that were added from the Central Management Console (CMC)

after installing the update package do not stop automatically during

uninstallation which in turn results in the deletion of the added servers after

rebooting. To avoid this, manually stop all servers before uninstalling the

update.

To uninstall Service Pack 1, execute the following command from the /bobje directory: ./AddorRemoveProducts.sh

Note:

After the uninstallation of the update, the .war files located under/enterprise120/java/applications are not automatically

re-deployed by the uninstaller, you will need to manually deploy the .war

files.

Silent Installation on UNIX

A silent installation is one that you run from the command line to automatically

install software on any machine in your system, without the installationprogram prompting for information.

You can also create a response file to run your silent install. A response file

records the configuration information that you would normally enter during

the installation process. See the Response File section later in this chapter

for more details.


5Installation of Update packages on UNIX

To uninstall the update on UNIX


32/42

You can launch the installation of the update package in silent mode by

inputting the following in a command line:

./install.sh INSTALLMODE=silent,install [CMSNAME

SERVER=] [CMSPORTNUMBER=] [CMSPASSWORD=]

Response files

A response file is a test file that can be used to record responses to the

different screens of the install wizard. This allows you to easily run identical

silent installs on multiple of machines while only going through the install

wizard steps once.

To run a silent installation using a response file (UNIX)

To run a silent installation using a response file you must first create a

response file.

The following steps describe how to create a response file using the

BusinessObjects installation program. Once you have created the response

file, you can run a silent installation by running the ./install.sh command

and specifying the path to the response file.

1. Create a response file.

a. From the FixPack installation source file location, run the .install.sh

command with the write option (-w) specified:

./install.sh -writeresponsepath response_file_path/response_file_name

where response_file_path/response_file_name is the path

and file name for the response file you are creating.

b. Press Enterto launch the installation setup program.

c. Follow the on screen instructions to enter your preferred installation

settings until you reach the Start installation dialog of the setup

program.

The settings are recorded in the response file.

d. Press [Ctrl -X] to abort the installation setup.



5 Silent Installation on UNIX


33/42

The parameters from the installation setup program, both user defined

and default, are recorded in the response file which is saved to the

directory you specified.

2. You can now run a response file installation by issuing ./install.shcommand with the -r option specified:

./install.sh -readresponsepath

3. Press Enterto launch the installation.

Response file installation parameters (UNIX)

The following table lists parameters that are commonly used for responsefile silent installation on UNIX. It is recommended that you create a response

files using ./install.sh and the -writeresponsepath parameter.


Runs an interactive install and saves the settings to a re-

sponse file at the specified location

WRITEREPONSEPATH="c:/install/path/response.ini"

WRITERE

SPONSEPA

TH

Runs an install silently using the information from the spec-ified responsefile.

READRESPONSEPATH="c:/install/path/resonse.ini"

READRESPON

SEPATH

Specifies the path of the application server directory if the

server is being installed.

The path is automatically set using the installation directory.

AS_DIR=/bobje/tomcat/

AS_DIR





34/42


Specifies the name of the application server being installed.

Use tomcat55 for Tomcat Use oas1013 for Oracle Application Server 10g R3



Use websphere6 for WebSphere 6.1

AS_SERVER=tomcat55

AS_SERVER

Specifies the name of the current web application server

instance.

AS_INSTANCE="localhost"

AS_IN

STANCE

Specifies virtual host to which the application must be bound.

AS_VIRTUAL_HOST="hostname"

AS_VIRTU

AL_HOST

Administration port of the application server.

Mandatory for NetWeaver, Oracle Application Server, and

WebLogic. For WebSphere, the SOAP port. If not set, the default

SOAP port (8880) will be used.

For Oracle Application Server (oas1013): wdeploy ex-

pects the request port of the element

in the [opmn.xml] file.

AS_AD

MIN_PORT

Specifies the account name used by the

administrator to access the web application server.

AS_ADMIN_USERNAME="admin"

AS_AD

MIN_USER

NAME



5 Silent Installation on UNIX


35/42


Password used by the administrator account to access the


AS_ADMIN_PASSWORD="pass"

AS_AD

MIN_PASS

WORD

Specifies is administrator credential must be passed to ac-

cess the web application server. This setting only valid for

WebSphere 6 and Oracle.

AS_ADMIN_IS_SECURE="true"

AS_AD

MIN_IS_SE

CURE

AS_APSERV

ER_ID

AS_GROUP_ID

The following parameters are automatically generated parameters that should

not be modified in the response file.

Parameter name

AUTODEPLOY_WAR_FILES

BOBJDIR

CDDIR

CMSNAMESERVER

CMSPORTNUMBER

CMSPASSWORD

FUNCTION

INSTALLLEVEL

LANGPACKS_TO_INSTALL

LICENSEDIR

LOCALNAMESERVER

MACHINENAME





36/42

Parameter name

PRODUCTID_NAME

PRODUCTID_VER

ProductVersion

VERSION_IN_RANGE

If you want to deploy .war files as part of a UNIX silent install, you will need

to definesome parameters for thedeployment.Theexact parameters required

will vary depening on the type of server used.

Manual deployment of web applicationserver components - UNIX

If the web application server components (.war files) were not re-deployed

automatically after the installation of the Service Pack, you need to do this

manually.

For instructions on redeploying .war files, please refer to the Deploying with

wdeploychapter of the BusinessObjects Enterprise Deployment guide for

UNIX.



5 Manual deployment of web application server components - UNIX


37/42

Get More Help

A


38/42

Online documentation library

Business Objects offers a full documentation set covering all products and

their deployment. The online documentation library has the most up-to-dateversion of the Business Objects product documentation. You can browse

the library contents, do full-text searches, read guides on line, and download

PDF versions. The library is updated regularly with new content as it becomes

available.

To access the online documentation library, visit http://help.sap.com/and

click Business Objects at the top of the page.

Additional developer resources

https://boc.sdn.sap.com/developer/library/

Online customer support

The Business Objects Customer Support web site contains information about

Customer Support programs and services. It also has links to a wide range

of technical information including knowledgebase articles, downloads, and

support forums.

http://www.businessobjects.com/support/

Looking for the best deployment solution for your company?

Business Objects consultants can accompany you from the initial analysis

stage to the delivery of your deployment project. Expertise is available in

relational and multidimensional databases, in connectivities, database design

tools, customized embedding technology, and more.

For more information, contact your local sales office, or contact us at:

http://www.businessobjects.com/services/consulting/

Looking for training options?

From traditional classroom learning to targeted e-learning seminars, we can

offer a training package to suit your learning needs and preferred learning

style. Find more information on the Business Objects Education web site:

http://www.businessobjects.com/services/training


Get More Help

A
http://help.sap.com/https://boc.sdn.sap.com/developer/library/http://www.businessobjects.com/support/http://www.businessobjects.com/services/consulting/http://www.businessobjects.com/services/traininghttp://www.businessobjects.com/services/traininghttp://www.businessobjects.com/services/consulting/http://www.businessobjects.com/support/https://boc.sdn.sap.com/developer/library/http://help.sap.com/


39/42

Send us your feedback

Do you have a suggestion on how we can improve our documentation? Is

there something you particularly like or have found useful? Drop us a line,

and we will do our best to ensure that your suggestion is included in the nextrelease of our documentation:

[email protected]

Note:

If your issue concerns a Business Objects product and not the documentation,

please contact our Customer Support experts. For information about

Customer Support visit: http://www.businessobjects.com/support/.

Business Objects product information

For information about the full range of Business Objects products, visit:

http://www.businessobjects.com.


AGet More Help
mailto:[email protected]://www.businessobjects.com/support/http://www.businessobjects.com/http://www.businessobjects.com/http://www.businessobjects.com/support/mailto:[email protected]


40/42


Get More Help

A


41/42

Index

B

BusinessObjects Software Inventory Tool 9

I

installing

on UNIX

silent install 31

uninstalling 31

on Windows

silent installation 20

uninstalling 19

installing Service Pack 1

distributed environments 14

Windows 18

M

minimum disk space 10multi-language systems

upgrading 10

P

prerequisites 8

R

response file 23, 32

parameters

UNIX 33

Windows 24

S

silent installation

response file

Windows 23

UNIX

response file 32

Software Inventory Tool 9

U

uninstalling 11

W

web applications

manual deployment

on UNIX 36



42/42

Index

xi3-1 update en

Documents