xi31 sp5 webappd win en

Web Application Deployment Guidefor Windows

SAP BusinessObjects Enterprise XI 3.1 Service Pack 5

windows

© 2011 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge,ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products

Copyright

and services mentioned herein as well as their respective logos are trademarksor registered trademarks of SAP AG in Germany and other countries.BusinessObjects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalDecisions, Web Intelligence, Xcelsius, and other Business Objects products andservices mentioned herein as well as their respective logos are trademarks orregistered trademarks of Business Objects Software Ltd. Business Objects is anSAP company.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQLAnywhere, and other Sybase products and services mentioned herein as well astheir respective logos are trademarks or registered trademarks of Sybase, Inc.Sybase is an SAP company. All other product and service names mentioned arethe trademarks of their respective companies. Data contained in this documentserves informational purposes only. National product specifications may vary.Thesematerials are subject to change without notice. These materials are provided bySAP AG and its affiliated companies ("SAP Group") for informational purposesonly, without representation or warranty of any kind, and SAP Group shall not beliable for errors or omissions with respect to the materials. The only warranties forSAP Group products and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any. Nothingherein should be construed as constituting an additional warranty.

2011-12-01

ContentsGetting Started 7Chapter 1

What's new in the SAP BusinessObjects Enterprise Web ApplicationDeployment Guide.......................................................................................8About this documentation............................................................................9Who should read this documentation........................................................10SAP BusinessObjects Enterprise guides...................................................10What is BusinessObjects Enterprise?.......................................................12

Deploying web applications after installation 15Chapter 2

Overview of post-installation deployment..................................................16Web application clustering support......................................................17

Failover and load balancing.......................................................................18

Deploying with wdeploy 19Chapter 3

Overview of wdeploy..................................................................................20Standalone mode.................................................................................20Split mode............................................................................................21

Actions for wdeploy....................................................................................23Log file creation....................................................................................23

Prerequisites for using wdeploy.................................................................24Enable 8-dot-3 filename support..........................................................24Set the JAVA_HOME............................................................................25Hardware requirements........................................................................25Before you deploy web applications.....................................................26

How to use wdeploy...................................................................................27Where to find wdeploy..........................................................................27

Web Application Deployment Guide for Windows 3

The wdeploy configuration file..............................................................27Command-line usage of wdeploy.........................................................34After deploying web applications..........................................................35

Deploying to web application servers with wdeploy..................................36JBoss 4.2.3 with wdeploy.....................................................................36Oracle Application Server 10g R3 with wdeploy..................................38SAP NetWeaver AS Java 7.0 with wdeploy.........................................42SAP NetWeaver AS Java 7.3 with wdeploy.........................................45Tomcat 5.5 with wdeploy......................................................................48Tomcat 6.0 with wdeploy......................................................................54Tomcat 7.0 with wdeploy......................................................................60WebLogic 10 or 10.3 with wdeploy.......................................................66WebLogic 10.3.3 (11gR1) with wdeploy...............................................72WebSphere 6.1 with wdeploy...............................................................79WebSphere 7.0 with wdeploy...............................................................85

To deploy web applications on a remote machine.....................................95

Manually deploying to a web application server 99Chapter 4

BusinessObjects Enterprise WAR files....................................................100WAR file context roots.............................................................................101Predeployment without access to Web Application servers....................103Guidelines for deploying WAR files.........................................................104To manually deploy web applications......................................................104Deployment with the administrative console...........................................106

JBoss..................................................................................................106Oracle Application Server...................................................................107SAP NetWeaver.................................................................................108Tomcat................................................................................................110WebLogic...........................................................................................112WebSphere........................................................................................117

4 Web Application Deployment Guide for Windows

Contents

Sample Deployment Scenarios 125Chapter 5

Overview of deployment scenarios..........................................................126Desktop client to server scenario............................................................126

Desktop client to server overview......................................................126Summary of required tasks................................................................127Deploying the desktop client to server scenario.................................128

Basic N-tier scenario................................................................................146N-tier scenario overview.....................................................................146Summary of required tasks................................................................147Deploying the N-tier scenario.............................................................147

Complex deployment scenario................................................................163Complex deployment overview..........................................................163Summary of required tasks................................................................165Deploying the complex deployment scenario.....................................165

Appendix 189Chapter 6

Reference for wdeploy.............................................................................190Configuration Information...................................................................190wdeploy parameters ..........................................................................196wdeploy actions..................................................................................204Web application updates made by wdeploy.......................................208

Troubleshooting wdeploy.........................................................................211WASX7017E: Exception deploying in WebSphere ...........................211Apache or Sun Java System Web server/Oracle 10G R3 applicationserver split deployment .....................................................................212Web application not removed from server..........................................212

Known issues...........................................................................................212Java fails to run in an IPv6 solo environment.....................................212Known web application server issues................................................213


Contents

More Information 221Appendix A

Index 225


Contents

Getting Started

1

What's new in the SAP BusinessObjectsEnterpriseWebApplicationDeploymentGuide

For a list of supported platforms, databases, web application servers, webservers, and other systems supported by this release, see the ProductsAvailability Report (Supported Platforms), available on the SAPBusinessObjects section of the SAP Support Portal at: https://service.sap.com/bosap-support. The Products Availability Report takesprecedence over any discrepancies in Web Application Deployment Guide.

The table below lists supported Java web application servers sinceBusinessObjects Enterprise XI 3.1 and what has changed in Service Pack5:

Supported inXI 3.1 SP5




Supported inXI 3.0 SP1 orXI 3.1

JavaWeb ap-plicationserver

YesYesYesYesYesTomcat 5.5

YesYesYesYesNoTomcat 6

YesNoNoNoNoTomcat 7

YesYesYesYesYesWebSphere6.1

YesYesYesYesNoWebSphere 7

NoYesYesYesYesWebLogic 9.2

YesYesYesYesYesWebLogic 10

YesYesYesYesNoWebLogic10.3


Getting Started1 What's new in the SAP BusinessObjects Enterprise Web Application Deployment Guide

https://service.sap.com/bosap-support

https://service.sap.com/bosap-support





Supported inXI 3.0 SP1 orXI 3.1

JavaWeb ap-plicationserver

YesYesNoNoNoWebLogic10.3.3(11gR1)

YesYesYesYesYesNetWeaver7.0

NoNoYesYesNoNetWeaver7.1

YesYesNoNoNoNetWeaver7.3

NoNoNoYesYesJBoss 4.0.4

YesYesYesNoNoJBoss 4.2.3

YesYesYesYesYesOracle 10g R3

NoYesYesYesYesWebSphereCommunityEdition 2.0

About this documentationThis documentation provides information, procedures, and options fordeploying web applications to your web application server after the installationof BusinessObjects Enterprise. Two versions of this guide exist:• SAP BusinessObjects Enterprise Web Application Deployment Guide for

Windows: for use with Microsoft Windows operating systems.• SAP BusinessObjects Enterprise Web Application Deployment Guide for

UNIX: for use with UNIX and Linux operating systems.


1Getting StartedAbout this documentation

Note:Instructions and information for the installation of BusinessObjects Enterpriseare documented in the SAP BusinessObjects Enterprise Installation Guide.

Who should read this documentationThis documentation is intended for the system administrator or IT professionalworking with BusinessObjects Enterprise on a Microsoft Windows operatingsystem. Familiarity with your overall network environment, port usageconventions, database environment, and web server software is essential.

Note:If you are installing BusinessObjects Enterprise on a UNIX or Linux operatingsystem, please read the SAP BusinessObjects Enterprise Installation Guidefor UNIX.

SAP BusinessObjects Enterprise guidesThe following table provides a list of SAP BusinessObjects Enterprise guidesand their contents.


Getting Started1 Who should read this documentation

DescriptionGuide

Covers the key concepts you should con-sider before you begin deploying SAPBusinessObjects Enterprise. This guideincludes an overview of the architecture,tips for assessing your existing environ-ment, determining your organization'sneeds, and preparing for the installation.

SAP BusinessObjects Enter-prise Planning Guide

Leads you through the steps required torun the setup program and complete yourinstallation of SAP BusinessObjects Enter-prise. There are UNIX and Windows ver-sions of this guide available.

SAP BusinessObjects Enter-prise Installation Guide

Covers topics related to the deploymentof web applications to web applicationservers with SAP BusinessObjects Enter-prise. There are UNIX and Windows ver-sions of this guide available.

SAP BusinessObjects Enter-prise Web Application Deploy-ment Guide

Provides content for server and contentadministration. The server administrationtopics includes server configuration,managing authentication, configuring fire-walls, and measuring system perfor-mance. The content administration topicsinclude working with the CMC, configuringrights and access levels, managing users,and working with Business Objects appli-cations and objects.

SAP BusinessObjects Enter-prise Administrator's Guide


1Getting StartedSAP BusinessObjects Enterprise guides

DescriptionGuide

Provides an overview of the publishingprocess, working with publications, pub-lishing Crystal reports, publishing WebIntelligence documents, publishing Desk-top Intelligence documents, and publishingsecurity.

SAP BusinessObjects Enter-prise Publisher's Guide

Details content migration from legacyBusiness Objects software, such as Clas-sic or Enterprise 5 or 6, to SAP Busines-sObjects Enterprise XI 3.1.

SAP BusinessObjects 5/6 to XI3.1 Migration Guide

Information for upgrades from BusinessOb-jects Enterprise XI to SAP BusinessOb-jects Enterprise XI 3.1.

SAP BusinessObjects Enter-prise Upgrade Guide

Provides an overview of InfoView andworking with Crystal Reports, Web Intelli-gence, objects, discussions, encyclopedia,and Voyager workspaces.

SAP BusinessObjects Enter-prise InfoView User's Guide

For all of our product documentation please visit: http://help.sap.com/

What is BusinessObjects Enterprise?BusinessObjects Enterprise is a flexible, scalable, and reliable businessintelligence reporting system that can be tightly integrated into yourinformation technology infrastructure. Support for many industry-standarddatabase systems makes it easier to access your organization's data foranalysis. The use of common industry standards for security allow you touse your existing authentication systems to control access to BusinessObjectsEnterprise. And broad platform support allows you to implement the operatingsystems and hardware architecture that you prefer.


Getting Started1 What is BusinessObjects Enterprise?

http://help.sap.com/

As a system administrator, you will be faced with many choices when installingBusinessObjects Enterprise. This documentation helps you to make the rightdecisions and create a reliable and powerful business intelligence reportingsystem for your organization.


1Getting StartedWhat is BusinessObjects Enterprise?


Getting Started1 What is BusinessObjects Enterprise?

Deploying web applicationsafter installation

2

Overviewofpost-installationdeploymentThe BusinessObjects Enterprise setup program can deploy web applicationsdirectly to a subset of the supported web application servers. For webapplication servers not supported by the setup program, web applicationsmust be deployed either on the command-line using the wdeploy tool, orwith the web application server's administrative console.

Web applications deployed by the administrative console must be updatedfrom their original, post-install, generic format into WAR or EAR filesdeployable to the destination web application server. The wdeploypredeploy command automates this process. For more information on thewdeploy predeploy command, see BusinessObjects Enterprise WARfiles.

The following table lists the deployment methods available for supportedweb application servers:

Administrative con-sole

wdeploy command-line

Setup programpost-installation

Web applicationserver

WebSphere 6.1

WebSphere 7.0 *

WebLogic 10

WebLogic 10.3 *

WebLogic 10.3.3(11gR1) ***

Tomcat 5.5

Tomcat 6.0 (6.0.18 ornewer) *

Tomcat 7.0 ****

SAP NetWeaver ASJava 7.0


Deploying web applications after installation2 Overview of post-installation deployment

Administrative con-sole

wdeploy command-line

Setup programpost-installation

Web applicationserver

SAP NetWeaver ASJava 7.3 ***

Oracle ApplicationServer 10g R3

JBoss 4.2.3 **

Microsoft IIS 6

Microsoft IIS 7

• * Denotes platforms newly supported in BusinessObjects Enterprise XI3.1 Service Pack 2.

• ** Denotes platforms newly supported in BusinessObjects Enterprise XI3.1 Service Pack 3.

• *** Denotes platforms newly supported in BusinessObjects Enterprise XI3.1 Service Pack 4.

• **** Denotes platforms newly supported in BusinessObjects EnterpriseXI 3.1 Service Pack 5.

Web application clustering support

The Central Management Console (CMC) and InfoView web applicationscan be used in environments with a variety of different clustered, loadbalanced, or fault tolerant configurations. The table below lists configurationsupport for CMC and InfoView web applications.


2Deploying web applications after installationOverview of post-installation deployment

Fault tol-erant

Load balanceswithout sessionaffinity

Load balancerswith sessionaffinity

Clustered webapplicationservers

Web ap-plication

YesSupportedSupportedSupportedInfoView(stateless)

NoUnsupportedSupportedSupportedCMC(stateful)

Failover and load balancingSAP BusinessObjects Enterprise supports the clustering of your webapplication server. Hardware or software load balancers can be used as theentry-point for the web application servers to ensure that the processing isevenly distributed among servers.

The following hardware load balancers are currently supported:

• Cisco Content Services Switches (CSS).• Cisco Content Switching Modules (CSM).• The F5 BIG-IP family of load balancers.

The following persistence types are currently supported:• Source IP address persistence.• Cookie persistence Insert mode (ArrowPoint Cookie).

Note:Web services applications are currently not supported with cookie persistenceand fail-over.

The Central Management Console (CMC) application does not supportsession fail-over. However, InfoView is fault-tolerant, and does supportsession fail-over, so users will not notice if a cluster node fails.


Deploying web applications after installation2 Failover and load balancing

Deploying with wdeploy

3

Overview of wdeployThe wdeploy command-line tool is included with BusinessObjects Enterpriseto aide the command-line deployment of web applications on Java-basedweb application servers.

Note:The wdeploy tool does not deploy to IIS web application servers.

You can deploy web applications to a single web application server(standalone mode deployment), or separate dynamic and static content fordeployment to separate web and web application servers (split modedeployment). For detailed information on the wdeploy tool, see Deploying toweb application servers with wdeploy.

For more information on the system architecture of BusinessObjectsEnterprise, see the Architecture chapter of the SAP BusinessObjectsEnterprise Deployment Planning Guide.

Note:If you have a firewall between your web application and BusinessObjectsEnterprise servers, you must perform additional system configuration. Seethe Firewalls section in the SAP BusinessObjects Enterprise DeploymentPlanning Guide.

Related Topics• How to use wdeploy

Standalone mode

Standalone mode deploys both static and dynamic web application contentto a single web application server. The web application server could berunning on the BusinessObjects Enterprise server, or a dedicated machine.

In the following diagram, clients connect through a firewall to a webapplication server (machine 1) that serves both static and dynamic content.Processing requests from the web application server are sent to theBusinessObjects Enterprise Central Management Server (CMS) forprocessing (machine 2).


Deploying with wdeploy3 Overview of wdeploy

This arrangement is best suited to small or mid-sized deployments with alimited number of users. The advantage of a standalone deployment is thatit is easy to deploy and maintain, but may not scale to a large number ofusers because both static and dynamic content is served by the webapplication server.

Split mode

Split mode separates static and dynamic web application content so thatstatic content can be served by a dedicated web server, and dynamic contentcan be served by a dedicated web application server. The web and webapplication servers could run on the same server, or separate servers on anetwork.

In the following diagram, clients connect through a firewall to a web server(machine 1) that serves only static content, such as images and HTML. Whendynamic content is required, the web server sends a request to the webapplication server (machine 2). Processing requests from the web applicationserver are sent to the BusinessObjects Enterprise Central ManagementServer (CMS) for processing (machine 3).

This arrangement is best suited to large or mid-sized deployments that expectthe number of users to grow. The advantage of a split deployment is that itis scalable and provides good performance.


3Deploying with wdeployOverview of wdeploy

Supported web and web application server combinations

In split deployments, wdeploy supports the following web and web applicationserver configurations:• Apache web server with Tomcat• Apache web server with WebLogic• Oracle HTTP Web Server with Oracle Application Server• IBM IHS web server with WebSphere

Note:Apache, Oracle HTTP Server, and IBM IHS web servers are both specifiedas apache in wdeploy configuration files.

Predeployment without access to Web Application servers

The wdeploy command can separate static and dynamic content fordeployment to web and web application servers.

When wdeploy is installed on a dedicated web server, the wdeploypredeploy or wdeploy predeployall commands can be used to deploystatic content directly to the web server's content directory. Some parametersare mandatory for particular web or web application servers:

Parameters required for predeploymentWeb or web appli-cation server

as_virtual_hostWebSphere Applica-tion Server

ws_dir, deployment_dir, connector_type

Note:When using Oracle HTTP Server with Oracle ApplicationServer, the following parameters must also be specified:connector_host, connector_port

Apache


Deploying with wdeploy3 Overview of wdeploy

Actions for wdeployThere are several actions that can be performed by the wdeploy tool to controlthe web application deployment process:• listapps: List all web applications installed on the system.• predeploy: Prepares a web application for deployment to a web

application server.• predeployall: Prepares all web applications for deployment to a web

application server.• deploy: Prepares and deploys a web application to a web application

server. *• deployall: Prepares and deploys all web applications to a web

application server. *• deployonly: Deploys a prepared web application to a web application

server. *• deployonlyall: Deploys all prepared web applications to a web

application server. *• listdeployedapps: Lists all web applications deployed to a web

application server. *• undeploy: Remove a web application from a web application server. *• undeployall: Remove all web applications from a web application

server. *• validateconfig: Validate the wdeploy configuration for supported web

application servers. ** These actions must be run on the web application server.

Note:If you use the undeploy and undeployall commands, only webapplications deployed through the installer or wdeploy will be undeployed.All other web applications can only be manually removed using the webapplication server's administrative console.

Log file creation

The wdeploy command appends activity information to the log file<BOE_INSTALL_DIR>BusinessObjects Enterprise12.0\deployment\workdir\wdeploy.log.


3Deploying with wdeployActions for wdeploy

Prerequisites for using wdeployTo deploy web applications to a web application server, BusinessObjectsEnterprise and the web application server must be installed and operational.

If the web application server is on the same machine as BusinessObjectsEnterprise, you can run the wdeploy script from BOE_INSTALL_DIR\deployment.

If the target web application server is on the same machine asBusinessObjects Enterprise, you can proceed to run the wdeploy script.

If the web application server is hosted on a different machine, you will haveto prepare the wdeploy on the web application server.Related Topics• To deploy web applications on a remote machine

Enable 8-dot-3 filename support

Windows 8-dot-3 filename support refers to the way in which Windows filesystems maintain two filenames for each file: one filename up to eightcharacters with a three-character extension, and the full name that can behundreds of characters long.

This feature is enabled by default on Windows operating systems, andensures backwards compatibility with legacy Microsoft operating and filesystems.

BusinessObjects Enterprise requires 8-dot-3 support to be enabled. Verifythat your Windows server has 8-dot-3 filenames enabled with the followingsteps:

1. From the Windows Start menu, select "Run...".The "Run" dialog window is displayed.

2. Type regedit into the "Open" field.The Registry Editor program runs.

3. Browse the registry tree to HKEY_LOCAL_MACHINE > SYSTEM >CurrentControlSet > Control > FileSystem


Deploying with wdeploy3 Prerequisites for using wdeploy

4. Double-click NtfsDisable8dot3NameCreation and ensure that itsvalue is set to 0.When set to 0, Windows 8-dot-3 filename support is enabled.

Windows now supports both long and short filenames.

Reboot the system for the change to take effect.

Set the JAVA_HOME

The wdeploy tool is based on the ANT (Another Neat Tool) build system,and requires Java 1.4, 1.5, or 1.6.

The wdeploy tool requires a Java Virtual Machine (JVM) to be available onthe host system. Java Development Kit (JDK) 1.5 is installed automaticallyby the SAP BusinessObjects Enterprise installation program. If you arerunning the wdeploy tool on a dedicated web application server, you mustinstall the JDK by performing a Web Tier installation on that dedicated system,manually install a supported JDK for that web application server, or use thesupported JDK if one is already installed with your web application server.

If you manually install a supported JDK, you must ensure that the followingenvironment settings have been configured:• The JAVA_HOME environment variable has been set to the directory where

Java is installed. If the JAVA_HOME variable is not set, or is invalid, thewdeploy tool attempts to use the JVM installed with SAP BusinessObjectsEnterprise.

• The user account PATH environment variable includes the bin directory:<JAVA_HOME>\bin

If no suitable JVM is found, wdeploy exits.

Hardware requirements

The deployment of web applications to a web application server using thewdeploy tool requires the following minimum hardware:• Minimum 4 GB of RAM (8 GB for SAP NetWeaver AS Java 7.3).• Minimum 15 GB of free disk space.


3Deploying with wdeployPrerequisites for using wdeploy

• Minimum 5 GB of free disk space on the drive hosting the temporaryfolder used for web application deployment (defined by the %TEMP%environment variable).

These minimum requirements are in addition to any requirements of the webapplication server and any other services installed on the host mchine.

Before you deploy web applications

Your web application server must be installed and working before you attemptto install BusinessObjects Enterprise. Consult your web application serverdocumentation for installation instructions.

To deploy and run the CMC and InfoView applications, your web applicationserver should have at least 2 GB of free disk space, in addition to any otherrequirements specified by other software installed on the machine.

It is recommended that you change the minimum and maximum heapsizeand the maximum Permanent Generation size settings of your JVM to-Xms128m -Xmx1024m -XX:MaxPermSize=256m. If using Tomcat forexample, your modified settings would look like this:

JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx1024m -XX:MaxPermSize=256m"

Note:For SAP NetWeaver AS 7.3, ensure the maximum heap size is 2048 MBand the maximum Permanent Generation size to 512 MB. For example:

JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx2048m -XX:MaxPermSize=512m"

Consult your JVM documentation for information on changing your Javamemory settings.

Before you begin the deployment process, ensure that the web applicationserver is correctly installed and verify that the application server is runningcorrectly by launching its administrative console. Consult your web applicationserver documentation for information on how to access the administrativeconsole.


Deploying with wdeploy3 Prerequisites for using wdeploy

How to use wdeployThe wdeploy tool is run from the command-line. The following sections walkyou through the initial configuration of wdeploy, then how to deploy webapplications to a web application server:1. Where to find wdeploy in the BusinessObjects Enterprise installation

directory.2. How to update the wdeploy configuration file to contain the default options

and parameters specific to your web application server.3. Using wdeploy command-line parameters.4. Ensuring that web applications were correctly deployed.

Related Topics• After deploying web applications• Reference for wdeploy

Where to find wdeploy

The wdeploy tool and its configuration files are located in the deploymentsubdirectory of the BusinessObjects Enterprise install directory INSTALL_DRIVE > BOE_INSTALL_DIR > deployment

The wdeploy tool is also available as a stand-alone package.

The wdeploy configuration file

The wdeploy configuration file is BOE_INSTALL_DIR\deployment\config.<WEB_APP_SERVER>. Substitute the <WEB_APP_SERVER> suffix forthe name of your web application server. The suffix must be the same webapplication server name used as the second parameter in the wdeploycommand-line syntax. Valid names for are:• config.jboss4 (JBoss 4.2.3)• config.oas1013 (Oracle Application Server 10g R3)• config.sapappsvr7 (SAP NetWeaver AS Java 7.0)• config.sapappsvr73 (SAP NetWeaver AS Java 7.3)


3Deploying with wdeployHow to use wdeploy

• config.tomcat55 (Tomcat 5.5.20)• config.tomcat6 (Tomcat 6.0.20)• config.tomcat7 (Tomcat 7.0)• config.weblogic10 (WebLogic 10 or 10.3)• config.weblogic11 (WebLogic 10.3.3 (11gR1))• config.websphere6 (WebSphere 6.1.0.7)• config.websphere7 (WebSphere 7.0)Valid names for web servers are:• config.apache (Apache Web Server and IBM IHS, for split web

application and web server deployments)

It is recommended that you use the same user account for installingBusinessObjects Enterprise and the web application server. This reducesthe likelihood of account permissions restricting file system access betweenBusinessObjects Enterprise and the web application server.

The following table lists the required wdeploy configuration file details thatcan be specified for each supported web application server.

Note:

• Parameters specified on the command-line override parameters in thewdeploy configuration file.

• It is recommended to pass the admin password to the web applicationserver using the as_admin_password parameter, rather than storing thepassword in the config.<WEB_APP_SERVER> configuration file.


Deploying with wdeploy3 How to use wdeploy

Required parametersWeb application server

• as_soap_port: SOAP port for application server administra-tion. If not set, the default SOAP port will be used (for exam-ple "8880").

• as_admin_username: WebSphere administrator accountusername (for example "administrator").

Note:If as_admin_is_secure is false, a value for as_admin_user-name does not need to be specified.

• as_admin_password: WebSphere administrator accountpassword (for example "password").

Note:If as_admin_is_secure is false, a value for as_admin_pass-word does not need to be specified.

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

• as_virtual_host: The virtual host to which the applicationmust be bound (for example "default_host").

• as_admin_is_secure: Instructs wdeploy that WebSpheresecurity is enabled (for example "false").

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

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

• ws_instance: Web server used to server requests when de-ployed to a distributed environment.

• enforce_file_limit: Indicates to wdeploy whether or not theweb application server may encounter issues loading appli-cations that contain more than 65 535 files ("False" by de-fault).

WebSphere 6.1 or 7.0

WebLogic 10, 10.3, or 10.3.3(11gR1)




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

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

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

• as_instance: The name of your WebLogic application serverinstance (for example "AdminServer").

• as_domain_dir: WebLogic domain directory (for example"C:\bea\weblogic\user_projects\domains\base_domain").

• as_instance : Name of the web application server instancecurrently used (for example "localhost").

• as_service_name : The name of the Windows service (whenthe application server is installed as a Windows service) (forexample "Tomcat5").

• as_dir : Installation directory of the web application server(for example "C:\wdeploy\appserver\Tomcat5520").

• as_service_key: Name of the Windows registry key used byTomcat to specify Java parameters (for example"HKLM\SOFTWARE\Apache Software Foundation\Procrun2.0\$as_service_name\Parameters\Java").

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

Tomcat 5.5, 6.0, or 7.0

SAP NetWeaver AS Java 7.0




• as_dir: The location of your application server (for example"C:\usr\sap").

• as_sid: the SAP system id of the target instance. (for example"AS1").

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

• as_admin_port: the port number used by the server (for ex-ample "50004").

• as_admin_username: the administrator username (for exam-ple "Administrator").

• as_admin_password: the administrator password (for exam-ple "password").




• as_dir: The location of your application server (for example"C:\usr\sap").

• as_sid: the SAP system id of the target instance. (for example"CE1").

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

• as_admin_port: the port number used by the server (for ex-ample "50004").

• as_admin_username: the administrator username (for exam-ple "Administrator").

• as_admin_password: the administrator password (for exam-ple "password").

• clear.temp.dirs (passed to SAP NetWeaver AS Java duringdeployment): toggles the automatic removal of temporaryfiles. Should be set to "true".

• use.deploy.controller (passed to SAP NetWeaver AS Javaduring deployment): toggles use of the SAP Deploy Controllertool. Should be set to "true".

• time.to.wait.factor (passed to SAP NetWeaver AS Java duringdeployment): wait time in seconds for the wdeploy script towait for the web application server to complete deployment(for example "1600").

SAP NetWeaver AS Java 7.3

Oracle Application Server10gR3




• as_admin_port: Administration port of the application server.This is the request port of the notification server, found inthe <notification-server> section of configurationfile opmn.xml (for example "6003").

• as_admin_username: Oracle Application Server administratoraccount username (for example "oc4jadmin").

• as_admin_password: Oracle Application Server administratoraccount password (for example "oracle10g").

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

• as_admin_is_secure: Instructs wdeploy that Oracle Appli-cation Server SSL security is enabled (for example "false").

Note:If as_admin_is_secure is not enabled, you will still have tospecify the username and password to access the server.

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

• as_appserver_name: Name of the target application server(for example "oracle10g.BO-AMIT.product.businessob-jects.com").

• as_group_id: Name of the server group to which the targetapplication belongs (for example "Default_group").

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

• as_instance: The name of the JBoss application server in-stance (for example "default").

JBoss 4.2.3

The following table lists the required wdeploy configuration file details for theApache web server, which can only be used when using a split web and webapplication server deployment.



Required Configuration detailsWeb Server

• ws_dir: The Apache web server installation directory (for example"C:\apache2").

• connector_type: The Apache connector type used to configure split mode(see the wdeployREADME file, located in the same directory as wdeploy) (for example "apache").

• deployment_dir: Directory under which wdeploy creates a subdirectoryfor static content served by the web server. This name must match theapplication name, and the name of the .zip archive that contains theapplication's static resources. wdeploy creates a virtual directory on theweb server, mapping the subdirectory to the URL (for example"C:\apache2\htdocs").

• connector_host: The ajp13 connector hostname for Oracle ApplicationServer (for example "localhost"). Only used with Oracle ApplicationServer.

• connector_port: The ajp13 connector port number for Oracle ApplicationServer (for example "8009"). Only used with Oracle Application Server.

Apache 2.2 orIBM IHS

Command-line usage of wdeploy

The wdeploy tool requires three types of parameters:

wdeploy.bat<WEB_OR_WAS>[-D<PROPERTY>]<ACTION>

Where:• <WEB_OR_WAS> is the configuration file for the web or web application

server (e.g. tomcat55).

• <PROPERTY> is a list of parameters and switches (e.g.-Das_mode=split). Parameters given here on the command-lineoverride those in the configuration file.

• <ACTION> is the name of the operation to perform (e.g. deployall).For a complete list of available actions, see the Parameters table below,or see Actions for wdeploy.



For example:

cd <BOE_INSTALL_DIR>\deployment

wdeploy.sh tomcat55-Das_mode=split-Das_dir=C:\tomcat-Das_instance=localhost-Dws_type=apache-Dws_dir=C:\apache-Dwork_dir=C:\Windows\TEMP\wdeploy-Dconnector_type=tomcat55-Ddeployment_dir=C:\apache\htdocs-DAPP=InfoViewAppdeploy

Note:Advanced users can run just the predeploy or predeployall commandsand deploy manually through the web application server administrativeconsole.

Tip:You can drop the deployable WAR files to non-default location by passingthe parameter -Dwork_dir=your_desired_location as part of thewdeploy command.

For more detailed information on wdeploy see Deploying to web applicationservers with wdeploy.Related Topics• To deploy web applications on a remote machine

After deploying web applications

After deploying your web applications on the web or web application serverusing wdeploy, restart the web application server (and web server, if used).

To verify the web application server configuration, make sure that InfoViewand the Central Management Console can be launched in a web browser.For example:• http://WAS_HOSTNAME:PORT/INFOVIEW_CONTEXT• http://WAS_HOSTNAME:PORT/CMC_CONTEXT



Replace WAS_HOSTNAME with the hostname or IP address of your web orweb application server, and PORT with the port number used for either HTTPor HTTPS communication. The default root context used for InfoView is InfoViewApp; the default context used for the CMC is CmcApp.

Deploying to web application serverswith wdeploy

JBoss 4.2.3 with wdeploy

Note:JBoss 4.2.3 is only supported in SAP BusinessObjects Enterprise XI 3.1Service Pack 3.

Using predeploy and predeployall

The predeploy command creates resources and configuration files for aspecific web application, then copies the WAR application to <BOE_INSTALL_DIR>\deployment\workdir\jboss4, but does not deploy theweb application to the web application server. The predeployall commandperforms the predeploy command for all web applications.

Example 1: using wdeploy predeploy to predeploy InfoView to JBoss.

wdeploy.bat jboss4-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto JBoss.

wdeploy.bat jboss4predeployall

Using deployonly and deployonlyall

The deployonly command deploys a web application that is specificallyconfigured for the target web application server. The deployonlyallcommand performs the deployonly command for all web applications.


Deploying with wdeploy3 Deploying to web application servers with wdeploy

Example 1: InfoView using wdeploy deployonly to deploy a predeployedInfoView to JBoss.

wdeploy.bat jboss4-Das_dir=C:\jboss-Das_instance=default-DAPP=InfoViewAppdeployonly

Example 2: using wdeploy deployonlyall to deploy all predeployedweb applications to JBoss.

wdeploy.bat jboss4-Das_dir=C:\jboss-Das_instance=defaultdeployonlyall

Using deploy and deployall

The deploy command creates resources and configuration files for a specificweb application, which is then deployed to the web application server. Thedeployall command performs the deploy command for all webapplications.

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

Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toJBoss.

wdeploy.bat jboss4-Das_dir=C:\jboss-Das_instance=default-DAPP=InfoViewAppdeploy

Example 2: using wdeploy deployall to predeploy, then deploy, all webapplications to JBoss.

wdeploy.bat jboss4-Das_dir=C:\jboss


3Deploying with wdeployDeploying to web application servers with wdeploy

-Das_instance=defaultdeployall

Using undeploy and undeployall

The undeploy command uninstalls a previously deployed web applicationfrom the web application server. The undeployall command performs theundeploy command for all web applications.

Example 1: using wdeploy undeploy to undeploy InfoView from JBoss.

wdeploy.bat jboss4-Das_dir=C:\jboss-Das_instance=default-DAPP=InfoViewAppundeploy

Example 2: using wdeploy undeployall to undeploy all web applicationsfrom JBoss.

wdeploy.bat jboss4-Das_dir=C:\jboss-Das_instance=defaultundeployall

Oracle Application Server 10g R3 with wdeploy


The predeploy command creates resources and configuration files for aspecific web application, then copies the WAR application to <BOE_INSTALL_DIR>\deployment\workdir\oas1013, but does not deploy theweb application to the web application server. The predeployall commandperforms the predeploy command for all web applications.

Example 1: using wdeploy predeploy to predeploy InfoView to OracleApplication Server.

wdeploy.bat oas1013-Das_dir=C:\Oracle10gASR3\OracleAS_1-Das_instance=home



-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6003-Das_admin_username=oc4jadmin-Das_admin_password=oracle12-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto Oracle Application Server.

wdeploy.bat oas1013-Das_dir=C:\Oracle10gASR3\OracleAS_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6003-Das_admin_username=oc4jadmin-Das_admin_password=oracle12predeployall



Example 1: using wdeploy deployonly to deploy a predeployed InfoViewto Oracle Application Server.

wdeploy.bat oas1013-Das_dir=C:\Oracle10gASR3\OracleAS_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6003-Das_admin_username=oc4jadmin-Das_admin_password=oracle12-DAPP=InfoViewAppdeployonly



Example 2: using wdeploy deployonlyall to deploy all predeployedweb applications to Oracle Application Server.

wdeploy.bat oas1013-Das_dir=C:\Oracle10gASR3\OracleAS_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6003-Das_admin_username=oc4jadmin-Das_admin_password=oracle12deployonlyall




Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toOracle Application Server.

wdeploy.bat oas1013-Das_dir=C:\Oracle10gASR3\OracleAS_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6003-Das_admin_username=oc4jadmin-Das_admin_password=oracle12-DAPP=InfoViewAppdeploy

Example 2: using wdeploy deployall to predeploy, then deploy, all webapplications to Oracle Application Server.

wdeploy.bat oas1013-Das_dir=C:\Oracle10gASR3\OracleAS_1-Das_instance=home-Das_appserver_name=oc4j_inst1



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



Example 1: using wdeploy undeploy to undeploy InfoView from OracleApplication Server.

wdeploy.bat oas1013-Das_dir=C:\Oracle10gASR3\OracleAS_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6003-Das_admin_username=oc4jadmin-Das_admin_password=oracle12-DAPP=InfoViewAppundeploy

Example 2: using wdeploy undeployall to undeploy all web applicationsfrom Oracle Application Server.

wdeploy.bat oas1013-Das_dir=C:\Oracle10gASR3\OracleAS_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6003-Das_admin_username=oc4jadmin-Das_admin_password=oracle12undeployall

Related Topics• After deploying web applications



SAP NetWeaver AS Java 7.0 with wdeploy

Note:Before deploying BusinessObjects Enterprise web applications, seePrerequisites for deployment on SAP NetWeaver.


The predeploy command creates resources and configuration files for aspecific web application, then copies the WAR application to <BOE_INSTALL_DIR>\deployment\workdir\sapappsvr7, but does not deploythe web application to the web application server. The predeployallcommand performs the predeploy command for all web applications.

Example 1: using wdeploy predeploy to predeploy InfoView to SAPNetWeaver AS Java 7.0.

wdeploy.bat sapappsvr7-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto SAP NetWeaver AS Java 7.0.

wdeploy.bat sapappsvr7predeployall



Example 1: using wdeploy deployonly to deploy a predeployed InfoViewto SAP NetWeaver AS Java 7.0.

wdeploy.bat sapappsvr7-Das_dir=C:\usr\sap-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator



-Das_admin_password=password1-Das_admin_port=50004-DAPP=InfoViewAppdeployonly

Example 2: using wdeploy deployonlyall to deploy all predeployedweb applications to SAP NetWeaver AS Java 7.0.

wdeploy.bat sapappsvr7-Das_dir=C:\usr\sap-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50004deployonlyall




Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toSAP NetWeaver AS Java 7.0.

wdeploy.bat sapappsvr7-Das_dir=C:\usr\sap-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50004-DAPP=InfoViewAppdeploy



Example 2: using wdeploy deployall to predeploy, then deploy, all webapplications to SAP NetWeaver AS Java 7.0.

wdeploy.bat sapappsvr7-Das_dir=C:\usr\sap-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50004deployall



Example 1: using wdeploy undeploy to undeploy InfoView from SAPNetWeaver AS Java 7.0.

wdeploy.bat sapappsvr7-Das_dir=C:\usr\sap-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50004-DAPP=InfoViewAppundeploy

Example 2: using wdeploy undeployall to undeploy all web applicationsfrom SAP NetWeaver AS Java 7.0.

wdeploy.bat sapappsvr7-Das_dir=C:\usr\sap-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50004undeployall




SAP NetWeaver AS Java 7.3 with wdeploy

Note:Before deploying BusinessObjects Enterprise web applications, seePrerequisites for deployment on SAP NetWeaver.


The predeploy command creates resources and configuration files for aspecific web application, then creates an EAR file in <BOE_INSTALL_DIR>\deployment\workdir\sapappsvr73, but does not deploythe web application to the web application server. The predeployallcommand performs the predeploy command for all web applications.

Example 1: using wdeploy predeploy to predeploy InfoView to SAPNetWeaver AS Java 7.3 .

wdeploy.bat sapappsvr73-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto SAP NetWeaver AS Java 7.3 .

wdeploy.bat sapappsvr73predeployall



Example 1: using wdeploy deployonly to deploy a predeployed InfoViewto SAP NetWeaver AS Java 7.3 .

wdeploy.bat sapappsvr73-Das_dir=C:\usr\sap-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator



-Das_admin_password=password1-Das_admin_port=50004-DAPP=InfoViewAppdeployonly

Example 2: using wdeploy deployonlyall to deploy all predeployedweb applications to SAP NetWeaver AS Java 7.3 .

wdeploy.bat sapappsvr73-Das_dir=C:\usr\sap-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50004deployonlyall




Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toSAP NetWeaver AS Java 7.3 .

wdeploy.bat sapappsvr73-Das_dir=C:\usr\sap-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50004-DAPP=InfoViewAppdeploy



Example 2: using wdeploy deployall to predeploy, then deploy, all webapplications to SAP NetWeaver AS Java 7.3 .

wdeploy.bat sapappsvr73-Das_dir=C:\usr\sap-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50004deployall



Example 1: using wdeploy undeploy to undeploy InfoView from SAPNetWeaver AS Java 7.3 .

wdeploy.bat sapappsvr73-Das_dir=C:\usr\sap-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50004-DAPP=InfoViewAppundeploy

Example 2: using wdeploy undeployall to undeploy all web applicationsfrom SAP NetWeaver AS Java 7.3 .

wdeploy.bat sapappsvr73-Das_dir=C:\usr\sap-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50004undeployall




Tomcat 5.5 with wdeploy


The predeploy command creates resources and configuration files for aspecific web application, then copies the WAR application to <BOE_INSTALL_DIR>\deployment\workdir\tomcat55, but does not deploy theweb application to the web application server. The predeployall commandperforms the predeploy command for all web applications.

Example 1: using wdeploy predeploy to predeploy InfoView to Tomcat5.5.

wdeploy.bat tomcat55-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto Tomcat 5.5.

wdeploy.bat tomcat55predeployall



Example 1: using wdeploy deployonly to deploy a InfoView to Tomcat5.5.

wdeploy.bat tomcat55-Das_dir=C:\Tomcat5-Das_instance=localhost-Das_service_name=Tomcat5-DAPP=InfoViewAppdeployonly



Example 2: using wdeploy deployonlyall to deploy all predeployedweb applications to Tomcat 5.5.

wdeploy.bat tomcat55-Das_dir=C:\Tomcat5-Das_instance=localhost-Das_service_name=Tomcat5deployonlyall




Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toTomcat 5.5.

wdeploy.bat tomcat55-Das_dir=C:\Tomcat5-Das_instance=localhost-Das_service_name=Tomcat5-DAPP=InfoViewAppdeploy

Example 2: using wdeploy deployall to predeploy, then deploy, all webapplications to Tomcat 5.5.

wdeploy.bat tomcat55-Das_dir=C:\Tomcat5-Das_instance=localhost-Das_service_name=Tomcat5deployall





Note:It is recommended that you stop Tomcat before using the undeploy or undeployall commands to undeploy web applications from a Tomcat server.

Example 1: using wdeploy undeploy to undeploy InfoView from Tomcat5.5.

wdeploy.bat tomcat55-Das_dir=C:\Tomcat5-Das_instance=localhost-DAPP=InfoViewApp-Das_service_name=Tomcat5undeploy

Example 2: using wdeploy undeployall to undeploy all web applicationsfrom Tomcat 5.5.

wdeploy.bat tomcat55-Das_dir=C:\Tomcat5-Das_instance=localhost-Das_service_name=Tomcat5undeployall

Note:If web applications are not undeployed from the web application server, usethe administrative console to stop all web applications and restart the server,then re-run the undeploy or undeployall command.


To deploy to separate Apache web and Tomcat 5.5 webapplication 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 webapplication server.

Note:This configuration requires that you use the wdeploy command to split webapplication resources into static and dynamic content that can be deployedto 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 theweb server is serving content correctly.Open a web browser and enter the IP address or hostname of the webserver, and a port number if the server is not listening on port 80. Forexample: http://mywebserver.mycompany.com:80.

2. Ensure that your Tomcat web application server is working correctly.Open a web browser and enter the IP address or hostname of the webapplication server, and a port number. For example:http://myappserver.mycompany.com:8080.

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

3. Download the Apache Tomcat connector from the Tomcat web site. TheApache Tomcat connector allows you to connect an Apache web serverwith a Tomcat web application server, so Apache can forward requestsfor dynamic resources to Tomcat.

4. Follow the plug-in configuration instructions on the Apache web site forconfiguring the bridge between Apache web server and Tomcat webapplication server.Requests for dynamic resources are now forwarded to Tomcat whenreceived by Apache.

5. Ensure that the bridge between the web server and web application serveris working by pointing a browser to the web server and verifying thatdynamic content from the web application server is served correctly.For example, visit the URL: http://mywebserver.mycompany.com:80/jsp-examples/.

Note:This example URL will only work if you have manually deployed the jsp-examples web application.



6. If the web application server is installed on the same machine asBusinessObjects Enterprise, run wdeploy locally on that machine. If theweb application server runs on a different machine, you must copy thewdeploy command and environment to the web application server. SeeTo deploy web applications on a remote machine.

7. Configure wdeploy environment to separate content between the webserver and the web application server. This is known as "split" mode.The wdeploy configuration files for Apache and Tomcat are located in<BOE_INSTALL_DIR>\deployment.• Edit config.tomcat55. For example:

#Business Objects Configuration Utilityas_dir=C:\Appserver\Tomcat5520as_instance=localhostas_service_name=Tomcat5as_service_key=HKLM\SOFTWARE\Apache Software Foundation\Procrun 2.0\Tomcat5\Parameters\Javaas_service_key_value=Options

• Edit config.apache. For example:

#Business Objects Configuration Utilityws_dir=C:\Webserver\Apache224connector_type=tomcat55deployment_dir=C:\Webserver\Apache224\htdocs

8. Use wdeploy predeploy in split mode to split source web applications intoseparate static and dynamic resources.For example:• Run the following command to extract static content for the Apache

web server.

wdeploy.bat tomcat55 -Das_mode=split-Dws_type=apache predeployall

9. Run wdeploy deployonlyall command to deploy the dynamic content toTomcat application server and static content to Apache.If Apache and Tomcat are on the same machine, static and dynamiccontent will be automatically deployed to servers by the followingcommand:

wdeploy.bat tomcat55 -Das_mode=split-Dws_type=apache deployonlyall



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 willbe automatically deployed to Tomcat by the following command. Staticcontent must be manually deployed to the remote Apache machineafterwards.

wdeploy.bat tomcat55 -Das_mode=splitdeployonlyall


Copy static content to the htdocs directory on the web server:• Extract the zip files on the web application server under <BOE_IN

STALL_DIR>\deployment\workdir\Tomcat55\resources.• Copy these folders from the Tomcat web application server to the

Apache <WS_DIR>\htdocs folder on the Apache server.• Copy the bobj.<application>.conf files from the Tomcat web

application server to the Apache <WS_DIR>\conf folder on theApache server.

• Update Apache httpd.conf under <WS_DIR>\conf with theapplication config files. For each web application, you must includean entry in httpd.conf. For example, to include AnalyticalReporting,you would enter:

Include conf\bobj.AnalyticalReporting.conf

Static content is now served by a dedicated web server, and dynamic contentis served by a dedicated web application server.Related Topics• The wdeploy configuration file• To deploy web applications on a remote machine





Note:Tomcat 6 is only supported when using release 6.0.18 or newer.














#Business Objects Configuration Utilityas_dir=C:\Appserver\tomcat6as_instance=localhostas_service_name=Tomcat6as_service_key=HKLM\SOFTWARE\Apache Software Foundation\Procrun 2.0\Tomcat6\Parameters\Javaas_service_key_value=Options




web server.











STALL_DIR>\deployment\workdir\tomcat6\resources.• Copy these folders from the Tomcat web application server to the










#Business Objects Configuration Utilityas_dir=C:\Appserver\tomcat7as_instance=localhostas_service_name=Tomcat7as_service_key=HKLM\SOFTWARE\Apache Software Foundation\Procrun 2.0\Tomcat7\Parameters\Javaas_service_key_value=Options




web server.











STALL_DIR>\deployment\workdir\tomcat7\resources.• Copy these folders from the Tomcat web application server to the








WebLogic 10 or 10.3 with wdeploy


The predeploy command creates resources and configuration files for aspecific web application, then copies the WAR application to <BOE_INSTALL_DIR>\deployment\workdir\WebAppServer_VERSION, butdoes not deploy the web application to the web application server. Thepredeployall command performs the predeploy command for all webapplications.

Example 1: using wdeploy predeploy to predeploy InfoView to WebLogic10 or 10.3.

wdeploy.bat weblogic10-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto WebLogic 10 or 10.3.

wdeploy.bat weblogic10predeployall



Example 1: using wdeploy deployonly to deploy a predeployed InfoViewto WebLogic 10 or 10.3.

wdeploy.bat weblogic10-Das_domain_dir=C:\bea\user_projects\domains\base_do

main-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_is_secure=true-Das_admin_username=weblogic-Das_admin_password=weblogic



-DAPP=InfoViewAppdeployonly

Example 2: using wdeploy deployonlyall to deploy all predeployedweb applications to WebLogic 10 or 10.3.


main-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_is_secure=true-Das_admin_username=weblogic-Das_admin_password=weblogicdeployonlyall




Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toWebLogic 10 or 10.3.


main-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_is_secure=true-Das_admin_username=weblogic-Das_admin_password=weblogic-DAPP=InfoViewAppdeploy



Example 2: using wdeploy deployall to predeploy, then deploy, all webapplications to WebLogic 10 or 10.3.


main-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_is_secure=true-Das_admin_username=weblogic-Das_admin_password=weblogicdeployall



Example 1: using wdeploy undeploy to undeploy InfoView from WebLogic10 or 10.3.


main-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_is_secure=true-Das_admin_username=weblogic-Das_admin_password=weblogic-DAPP=InfoViewAppundeploy

Example 2: using wdeploy undeployall to undeploy all web applicationsfrom WebLogic 10 or 10.3.


main-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_is_secure=true-Das_admin_username=weblogic



-Das_admin_password=weblogicundeployall


To deploy to separate Apache web andWebLogic 10 or 10.3 webapplication 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 servedby the web server, while dynamic content will be served by the webapplication server.



2. Ensure that your WebLogic web application server is working correctly.Open a web browser and enter the IP address or hostname of the webapplication server, and a port number. For example:http://myappserver.mycompany.com:7001.


3. Download the WebLogic Apache HTTP Server Plug-In from the BEA website. The plug-in allows you to connect an Apache web server with aWebLogic web application server, so Apache can forward requests fordynamic resources to WebLogic.

4. Follow the plug-in configuration instructions on the BEA web site forconfiguring the bridge between Apache web server and WebLogic.



Requests for dynamic resources are now forwarded to WebLogic whenreceived by Apache.




7. Configure wdeploy environment to separate content between the webserver and the web application server. This is known as "split" mode.The wdeploy configuration files for Apache and WebLogic are located in<BOE_INSTALL_DIR>\deployment.• Edit config.weblogic10. For example:

#Business Objects Configuration Utilityas_admin_port=7001as_admin_username=weblogicas_admin_password=weblogicas_instance=AdminServeras_domain_dir=C:\bea\user_projects\domains\base_domain


#Business Objects Configuration Utilityws_dir=C:\Webserver\Apache224connector_type=weblogic10deployment_dir=C:\Webserver\Apache224\htdocs

8. Use wdeploy predeploy in split mode to split source web applications intoseparate static and dynamic resources.For example:



• Run the following command to extract static content for the Apacheweb server and dynamic content for WebLogic application server.

wdeploy.bat weblogic10 -Das_mode=split-Dws_type=apache predeployall

The dynamic content is located in: <BOE_INSTALL_DIR>\deployment\workdir\weblogic10\application.

Static content is located in: <BOE_INSTALL_DIR>\deployment\workdir\weblogic10\resources.

9. Run wdeploy deployonlyall command to deploy the dynamic content toWebLogic application server and static content to Apache.If Apache and WebLogic are on the same machine, static and dynamiccontent will be automatically deployed to the servers by the followingcommand:

wdeploy.bat weblogic10 -Das_mode=split-Dws_type=apache deployonlyall


If Apache and WebLogic are on different machines, dynamic content willbe automatically deployed to WebLogic by the following command. Staticcontent must be manually deployed to the remote Apache machineafterwards.

wdeploy.bat weblogic10 -Das_mode=splitdeployonlyall

Note:If your dynamic and static content resides in a custom location, use the-Dwork_dir parameter.


STALL_DIR>\deployment\workdir\weblogic10\resources.• Copy these folders from the WebLogic web application server to the

Apache <WS_DIR>\htdocs folder on the Apache server.



• Copy the bobj.<application>.conf files from the WebLogic webapplication server to the Apache <WS_DIR>\conf folder on theApache server.




WebLogic 10.3.3 (11gR1) with wdeploy


The predeploy command creates resources and configuration files for aspecific web application, then copies the WAR application to <BOE_INSTALL_DIR>\deployment\workdir\WebAppServer_VERSION, butdoes not deploy the web application to the web application server. Thepredeployall command performs the predeploy command for all webapplications.

Example 1: using wdeploy predeploy to predeploy InfoView to WebLogic10.3.3 (11gR1) .

wdeploy.bat weblogic11-DAPP=InfoViewApppredeploy



Example 2: using wdeploy predeployall to predeploy all web applicationsto WebLogic 10.3.3 (11gR1) .

wdeploy.bat weblogic11predeployall



Example 1: using wdeploy deployonly to deploy a predeployed InfoViewto WebLogic 10.3.3 (11gR1) .


main-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_is_secure=true-Das_admin_username=weblogic-Das_admin_password=weblogic-DAPP=InfoViewAppdeployonly

Example 2: using wdeploy deployonlyall to deploy all predeployedweb applications to WebLogic 10.3.3 (11gR1) .


main-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_is_secure=true-Das_admin_username=weblogic-Das_admin_password=weblogicdeployonlyall


The deploy command creates resources and configuration files for a specificweb application, which is then deployed to the web application server. The



deployall command performs the deploy command for all webapplications.


Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toWebLogic 10.3.3 (11gR1) .


main-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_is_secure=true-Das_admin_username=weblogic-Das_admin_password=weblogic-DAPP=InfoViewAppdeploy

Example 2: using wdeploy deployall to predeploy, then deploy, all webapplications to WebLogic 10.3.3 (11gR1) .


main-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_is_secure=true-Das_admin_username=weblogic-Das_admin_password=weblogicdeployall



Example 1: using wdeploy undeploy to undeploy InfoView from WebLogic10.3.3 (11gR1) .




main-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_is_secure=true-Das_admin_username=weblogic-Das_admin_password=weblogic-DAPP=InfoViewAppundeploy

Example 2: using wdeploy undeployall to undeploy all web applicationsfrom WebLogic 10.3.3 (11gR1) .


main-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_is_secure=true-Das_admin_username=weblogic-Das_admin_password=weblogicundeployall


To deploy to separate Apache web andWebLogic 10.3.3 (11gR1)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 theweb server is serving content correctly.



Open a web browser and enter the IP address or hostname of the webserver, and a port number if the server is not listening on port 80. Forexample: http://mywebserver.mycompany.com:80.

2. Ensure that your WebLogic web application server is working correctly.Open a web browser and enter the IP address or hostname of the webapplication server, and a port number. For example:http://myappserver.mycompany.com:7001.


3. Download the WebLogic Apache HTTP Server Plug-In from the BEA website. The plug-in allows you to connect an Apache web server with aWebLogic web application server, so Apache can forward requests fordynamic resources to WebLogic.

4. Follow the plug-in configuration instructions on the BEA web site forconfiguring the bridge between Apache web server and WebLogic.Requests for dynamic resources are now forwarded to WebLogic whenreceived by Apache.




7. Configure wdeploy environment to separate content between the webserver and the web application server. This is known as "split" mode.The wdeploy configuration files for Apache and WebLogic are located in<BOE_INSTALL_DIR>\deployment.



• Edit config.weblogic11. For example:

#Business Objects Configuration Utilityas_admin_port=7001as_admin_username=weblogicas_admin_password=weblogicas_instance=AdminServeras_domain_dir=C:\bea\user_projects\domains\base_domain


#Business Objects Configuration Utilityws_dir=C:\Webserver\Apache224connector_type=weblogic11deployment_dir=C:\Webserver\Apache224\htdocs


web server and dynamic content for WebLogic application server.

wdeploy.bat weblogic11 -Das_mode=split-Dws_type=apache predeployall

The dynamic content is located in: <BOE_INSTALL_DIR>\deployment\workdir\weblogic11\application.

Static content is located in: <BOE_INSTALL_DIR>\deployment\workdir\weblogic11\resources.

9. Run wdeploy deployonlyall command to deploy the dynamic content toWebLogic application server and static content to Apache.If Apache and WebLogic are on the same machine, static and dynamiccontent will be automatically deployed to the servers by the followingcommand:

wdeploy.bat weblogic11 -Das_mode=split-Dws_type=apache deployonlyall




If Apache and WebLogic are on different machines, dynamic content willbe automatically deployed to WebLogic by the following command. Staticcontent must be manually deployed to the remote Apache machineafterwards.

wdeploy.bat weblogic11 -Das_mode=splitdeployonlyall

Note:If your dynamic and static content resides in a custom location, use the-Dwork_dir parameter.


STALL_DIR>\deployment\workdir\weblogic11\resources.• Copy these folders from the WebLogic web application server to the

Apache <WS_DIR>\htdocs folder on the Apache server.• Copy the bobj.<application>.conf files from the WebLogic web







WebSphere 6.1 with wdeploy


The predeploy command creates resources and configuration files for aspecific web application, then copies the web application to <BOE_INSTALL_DIR>\deployment\workdir\WebAppServer_VERSION, butdoes not deploy the web application to the web application server. Thepredeployall command performs the predeploy command for all webapplications.

Example 1: using wdeploy predeploy to predeploy InfoView to WebSphere6.

wdeploy.bat websphere6-Das_virtual_host=default_host-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto WebSphere 6.

wdeploy.bat websphere6-Das_virtual_host=default_hostpredeployall



Example 1: using wdeploy deployonly to deploy a predeployed InfoViewto WebSphere 6.

wdeploy.bat websphere6-Das_dir=C:\IBM\WebSphere\AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_soap_port=8880



-DAPP=InfoViewAppdeployonly

Example 2: using wdeploy deployonlyall to deploy all predeployedweb applications to WebSphere 6.

wdeploy.bat websphere6-Das_dir=C:\IBM\WebSphere\AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_soap_port=8880deployonlyall




Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toWebSphere 6.

wdeploy.bat websphere6-Das_dir=C:\IBM\WebSphere\AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_soap_port=8880-DAPP=InfoViewAppdeploy

Example 2: using wdeploy deployall to predeploy, then deploy, all webapplications to WebSphere 6.

wdeploy.bat websphere6-Das_dir=C:\IBM\WebSphere\AppServer-Das_instance=server1-Das_virtual_host=default_host



-Das_soap_port=8880deployall



Example 1: using wdeploy undeploy to undeploy InfoView fromWebSphere 6.

wdeploy.bat websphere6-Das_dir=C:\IBM\WebSphere\AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_soap_port=8880-DAPP=InfoViewAppundeploy

Example 2: using wdeploy undeployall to undeploy all web applicationsfrom WebSphere 6.

wdeploy.bat websphere6-Das_dir=C:\IBM\WebSphere\AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_soap_port=8880undeployall


To deploy to separate IHS web and WebSphere 6.1 webapplication servers





1. Set up an IBM HTTP Server (IHS) web server and ensure that it is workingcorrectly. Load a web page, such as the IHS default test page, to verifythat the web server is serving content correctly.Open a web browser and enter the IP address or hostname of the webserver, and a port number if the server is not listening on port 80. Forexample: http://mywebserver.mycompany.com:80.

2. Ensure that your WebSphere web application server is working correctly.Open a web browser and enter the IP address or hostname of the webapplication server, and a port number. For example:http://myappserver.mycompany.com:9080.


3. Run the web server plug-in installation wizard to install the plug-in thatbridges WebSphere with IHS, and follow the directions to enter informationabout your IHS web server.

4. Follow the plug-in configuration instructions on the WebSphere web sitefor configuring the bridge between IHS and WebSphere.Requests for dynamic resources are now forwarded to WebSphere whenreceived by IHS.

5. Ensure that the bridge between the web server and web application serveris working by pointing a browser to the web server and verifying thatdynamic content from the web application server is served correctly.For example, visit the URL: http://mywebserver.mycompany.com:80/snoop/.


7. Configure wdeploy environment to separate content between the webserver and the web application server. This is known as "split" mode.



The wdeploy configuration files for IHS and WebSphere are located in<BOE_INSTALL_DIR>\deployment.• Edit config.apache. For example:

#Business Objects Configuration Utilityws_dir=C:\Program Files\Apache Software Foundation\Apache 2.2connector_type=websphere6deployment_dir=C:\Program Files\Apache SoftwareFoundation\Apache 2.2\htdocs

• Edit config.websphere6. For example:

#Business Objects Configuration Utilityas_soap_port=8880#as_admin_username=admin#as_admin_password=passwordas_dir=C:\Program Files\IBM\WebSphere\AppServeras_instance=server1as_virtual_host=default_hostas_admin_is_secure=falseenforce_file_limit=truews_instance=webserver1

8. Use wdeploy predeploy in split mode to split source web applications intoseparate static and dynamic resources.For example:• Run the following command to extract static content for the IHS web

server.

wdeploy.bat websphere6 -Das_mode=split-Dws_type=apache predeployall

The dynamic content of web applications is located in: <BOE_INSTALL_DIR>\deployment\workdir\websphere6\application.

The static content is located in: <BOE_INSTALL_DIR>\deployment\workdir\websphere6\resources.

9. Run wdeploy deployonlyall command to deploy the dynamic content toWebSphere application server and static content to IHS.



If IHS and WebSphere are on the same machine, static and dynamiccontent will be automatically deployed to servers by the followingcommand:

wdeploy.bat websphere6 -Das_mode=split-Dws_type=apache deployonlyall


If IHS and WebSphere are on different machines, dynamic content willbe automatically deployed to WebSphere by the following command.Static content must be manually deployed to the remote IHS machineafterwards.

wdeploy.bat websphere6 -Das_mode=splitdeployonlyall



STALL_DIR>\deployment\workdir\websphere6\resources.• Copy these folders from the WebSphere web application server to the

IHS <WS_DIR>\htdocs folder on the IHS server.• Copy the bobj.<application>.conf files from the WebSphere

web application server to the IHS <WS_DIR>\conf folder on the IHSserver.

• Update IHS httpd.conf under <WS_DIR>\confwith the applicationconfig files. For each web application, you must include an entry inhttpd.conf. For example, to include AnalyticalReporting, you wouldenter:


10. Propagate the plugin-cfg.xml file from the application server to theweb server using the administrative console. Click Servers >Web server.Select the web server, then click Propagate Plug-in. Web servers otherthan IHS require manual propagation.



• For IHS, click Servers > Web server. Select the web server, thenclick Propagate Plug-in.

• For all other web servers, copy plugin-cfg.xml from the <profile_root>/config/cells/<cell_name>/nodes/node_name/servers/<Web_server_name> directory on the WebSphere web application server to the<plugins_root>/config/<Web_server_name> directory on theIHS web server.

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


WebSphere 7.0 with wdeploy


The predeploy command creates resources and configuration files for aspecific web application, then copies the web application to <BOE_INSTALL_DIR>\deployment\workdir\WebAppServer_VERSION, butdoes not deploy the web application to the web application server. Thepredeployall command performs the predeploy command for all webapplications.

Example 1: using wdeploy predeploy to predeploy InfoView to WebSphere7.

wdeploy.bat websphere7-Das_virtual_host=default_host



-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy all web applicationsto WebSphere 7.

wdeploy.bat websphere7-Das_virtual_host=default_hostpredeployall



Note:After deploying to WebSphere 7.0, ensure that the setting Classes loadedwith application class loader first is enabled for each deployed webapplication. For detailed instructions, see Classes loaded with applicationclass loader first.

Example 1: using wdeploy deployonly to deploy a predeployed InfoViewto WebSphere 7.

wdeploy.bat websphere7-Das_dir=C:\IBM\WebSphere\AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_soap_port=8880-DAPP=InfoViewAppdeployonly

Example 2: using wdeploy deployonlyall to deploy all predeployedweb applications to WebSphere 7.

wdeploy.bat websphere7-Das_dir=C:\IBM\WebSphere\AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_soap_port=8880deployonlyall






Note:After deploying to WebSphere 7.0, ensure that the setting Classes loadedwith application class loader first is enabled for each deployed webapplication. For detailed instructions, see Classes loaded with applicationclass loader first.

Example 1: using wdeploy deploy to predeploy, then deploy, InfoView toWebSphere 7.

wdeploy.bat websphere7-Das_dir=C:\IBM\WebSphere\AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_soap_port=8880-DAPP=InfoViewAppdeploy

Example 2: using wdeploy deployall to predeploy, then deploy, all webapplications to WebSphere 7.

wdeploy.bat websphere7-Das_dir=C:\IBM\WebSphere\AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_soap_port=8880deployall





Example 1: using wdeploy undeploy to undeploy InfoView fromWebSphere 7.

wdeploy.bat websphere7-Das_dir=C:\IBM\WebSphere\AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_soap_port=8880-DAPP=InfoViewAppundeploy

Example 2: using wdeploy undeployall to undeploy all web applicationsfrom WebSphere 7.

wdeploy.bat websphere7-Das_dir=C:\IBM\WebSphere\AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_soap_port=8880undeployall


Disable WebSphere JSF implementation

If pages rendered by WebSphere 7 do not show cached values correctly, itmay be using its own version of the Java Server Faces (JSF) library, ratherthan the JSF implementation supplied with BusinessObjects Enterprise. Tocorrect this problem, you must manually reconfigure WebSphere for eachweb application that uses JSF: CmcApp, CmcAppActions, andPlatformServices.

To disable the JSF implementation supplied with WebSphere, follow theinstructions below.

1. Log in to the "WebSphere Application Server Administration" consoleusing the following URL: http://WAS_HOSTNAME:PORT/admin. TheWebSphere administration console's default port number is 9060.

2. Browse to YOUR_WEB_APPLICATION > Manage Modules >YOUR_WEB_APPLICATION.war



Replace YOUR_WEB_APPLICATION in the example above with the nameof your web application.

3. Stop the web application, so its settings can be modified.4. SelectClasses loaded with application class loader first (parent last)

from the combo box.Restart the web application.

5. Repeat these steps for all other web applications that use JSF.

Reload pages that display cached values. Cached values are now displayedcorrectly.

To deploy to separate IHS web and WebSphere 7.0 webapplication servers



1. Set up an IBM HTTP Server (IHS) web server and ensure that it is workingcorrectly. Load a web page, such as the IHS default test page, to verifythat the web server is serving content correctly.Open a web browser and enter the IP address or hostname of the webserver, and a port number if the server is not listening on port 80. Forexample: http://mywebserver.mycompany.com:80.

2. Ensure that your WebSphere web application server is working correctly.Open a web browser and enter the IP address or hostname of the webapplication server, and a port number. For example:http://myappserver.mycompany.com:9080.




3. Run the web server plug-in installation wizard to install the plug-in thatbridges WebSphere with IHS, and follow the directions to enter informationabout your IHS web server.

4. Follow the plug-in configuration instructions on the WebSphere web sitefor configuring the bridge between IHS and WebSphere.Requests for dynamic resources are now forwarded to WebSphere whenreceived by IHS.

5. Ensure that the bridge between the web server and web application serveris working by pointing a browser to the web server and verifying thatdynamic content from the web application server is served correctly.For example, visit the URL: http://mywebserver.mycompany.com:80/snoop/.


7. Configure wdeploy environment to separate content between the webserver and the web application server. This is known as "split" mode.The wdeploy configuration files for IHS and WebSphere are located in<BOE_INSTALL_DIR>\deployment.• Edit config.apache. For example:

#Business Objects Configuration Utilityws_dir=C:\Program Files\Apache Software Foundation\Apache 2.2connector_type=websphere7deployment_dir=C:\Program Files\Apache SoftwareFoundation\Apache 2.2\htdocs

• Edit config.websphere7. For example:

#Business Objects Configuration Utilityas_soap_port=8880#as_admin_username=admin#as_admin_password=passwordas_dir=C:\Program Files\IBM\WebSphere\AppServeras_instance=server1as_virtual_host=default_hostas_admin_is_secure=falseenforce_file_limit=truews_instance=webserver1



8. Use wdeploy predeploy in split mode to split source web applications intoseparate static and dynamic resources.For example:• Run the following command to extract static content for the IHS web

server.

wdeploy.bat websphere7 -Das_mode=split-Dws_type=apache predeployall

The dynamic content of web applications is located in: <BOE_INSTALL_DIR>\deployment\workdir\websphere7\application.

The static content is located in: <BOE_INSTALL_DIR>\deployment\workdir\websphere7\resources.

9. Run wdeploy deployonlyall command to deploy the dynamic content toWebSphere application server and static content to IHS.If IHS and WebSphere are on the same machine, static and dynamiccontent will be automatically deployed to servers by the followingcommand:

wdeploy.bat websphere7 -Das_mode=split-Dws_type=apache deployonlyall


If IHS and WebSphere are on different machines, dynamic content willbe automatically deployed to WebSphere by the following command.Static content must be manually deployed to the remote IHS machineafterwards.

wdeploy.bat websphere7 -Das_mode=splitdeployonlyall



STALL_DIR>\deployment\workdir\websphere7\resources.



• Copy these folders from the WebSphere web application server to theIHS <WS_DIR>\htdocs folder on the IHS server.

• Copy the bobj.<application>.conf files from the WebSphereweb application server to the IHS <WS_DIR>\conf folder on the IHSserver.

• Update IHS httpd.conf under <WS_DIR>\confwith the applicationconfig files. For each web application, you must include an entry inhttpd.conf. For example, to include AnalyticalReporting, you wouldenter:


10. Propagate the plugin-cfg.xml file from the application server to theweb server using the administrative console. Click Servers >Web server.Select the web server, then click Propagate Plug-in. Web servers otherthan IHS require manual propagation.• For IHS, click Servers > Web server. Select the web server, then

click Propagate Plug-in.• For all other web servers, copy plugin-cfg.xml from the <pro

file_root>/config/cells/<cell_name>/nodes/node_name/servers/<Web_server_name> directory on the WebSphere web application server to the<plugins_root>/config/<Web_server_name> directory on theIHS web server.

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




Classes loaded with application class loader first

Ensure that your WebSphere 7.0 web application server is installed,configured, and running. Use the wdeploy command to deploy your webapplications to WebSphere 7.0.

Log in to the WebSphere "Integrated Solutions Console" with theAdministrator account. You can run the WebSphere "Administrative console"program, or use a web browser to open http://WAS_HOSTNAME:PORT/ibm/console where WAS_HOSTNAME is the name of yourWebSphere server, and PORT is the port number on which the server listensfor login requests. The default port number is 9060.

1. Select Applications > Application Type > WebSphere enterpriseapplications in the menu.The "Enterprise Applications" screen appears.

2. Choose the web application deployed by wdeploy from the list ofadministered resources.The "Enterprise Applications" configuration screen appears.

3. Click Manage Modules.The "Manage Modules" screen appears.

4. Select the web application module (click the link shown in the "Module"column).The "Manage Modules General Properties" screen appears.

5. SelectClasses loaded with application class loader first (parent last)from the "Class loader order" property.A confirmation message appears.

6. Click Save directly to the master configuration.The web application configuration is saved and you are returned to the"Manage Modules" screen.

7. Click OK.A master configuration change confirmation message appears.

8. Click Save directly to the master configuration.The web application configuration is saved and you are returned to the"Enterprise Applications" screen.



9. Select the web application checkbox and click Start.A message appears to confirm that the web application startedsuccessfully.

When depoying more than one web application, repeat steps 2-9 for eachweb application.

Web Services on WebSphere 7.0

After using the wdeploy command to deploy Web Services to WebSphere7.0, the List of Web Services link is not available in the SAPBusinessObjects Enterprise Web Services portal interface.

Note:SAP BusinessObjects Enterprise Web Services is only fully supported onWebSphere 7.0 in SAP BusinessObjects Enterprise XI 3.1 Service Pack 3.

To work around this issue, ensure that SAP BusinessObjects Enterprise XI3.1 Service Pack 3 is installed and follow these steps:

1. Start the WebSphere 7.0 web application server.2. Use the wdeploy command to deploy dswsbobje.war and Busi

nessProcessBI.war.3. Stop the WebSphere 7.0 web application server.4. Copy the file<WEBSPHERE7_INSTALL_DIR>\profiles\AppSrv01\in

stalledApps\<WS7_NODE_NAME>\dswsbobje.ear\dswsbobje.war\WEB-INF\modules\addressing-1.3.mar to a new file as:<WEBSPHERE7_INSTALL_DIR>\profiles\AppSrv01\installedApps\<WS7_NODE_NAME>\dswsbobje.ear\dswsbobje.war\WEB-INF\lib\addressing-1.3.jar.For example:

cd <WEBSPHERE7_INSTALL_DIR>\profiles\AppSrv01\installedApps\<WS7_NODE_NAME>\dswsbobje.ear\dswsbobje.war\WEB-INF\modulescopy addressing-1.3.mar ..\lib\addressing-1.3.jar

Note:Do not remove or rename addressing-1.3.mar in the modules folder.Ensure that the file is named addressing-1.3.jar in the lib folder.



5. Restart the WebSphere 7.0 web application server.6. Launch Web Services.

The List of Web Services link now displays a list of Web Services.

To deploy web applications on a remotemachine

Use the procedure below to deploy web applications to a remote machine.In this procedure Box 1 refers to the machine hosting your BusinessObjectsEnterprise installation, and Box 2 is the remote machine on which noBusinessObjects Enterprise resources are currently installed.

1. Create on Box 2 the following directories.• <BOE_INSTALL_DIR>\deployment\. The deployment folder

contains the wdeploy scripts and configuration files.• <BOE_INSTALL_DIR>\BusinessObjects Enterprise

12.0\java\applications\• <BOE_INSTALL_DIR>\Performance Management 12.0\

These directories reflect the default directory structure installed on Box1.

Tip:Although you can customize the folder structure to meet your specificrequirements, it is recommended that you maintain files within the samefolder structure or hierarchy in Box 2 as in Box 1.

2. Copy the following files from Box 1 to Box 2.• Copy the contents of <BOE_INSTALL_DIR>\deployment\

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

• Copy the contents of <BOE_INSTALL_DIR>\BusinessObjectsEnterprise 12.0\java\applications

• From <BOE_INSTALL_DIR>\Performance Management 12.0\copy InitConfig.properties

• From <BOE_INSTALL_DIR>\ copy LanguagePacks.xml


3Deploying with wdeployTo deploy web applications on a remote machine

3. Set the JAVA_HOME environment variable to JDK directory.4. If the WAR filecopied from Box 1 is kept in a custom location on Box 2,

you must pass the -Dwar_dir parameter to wdeploy when deploying.5. Modify the wdeploy configuration file for your web application server. You

must provide all the required information to enable wdeploy to deploy theweb application.For example, to modify the configuration file for WebLogic 10, you wouldmodify the file to:

as_domain_dir=C:\bea10\user_projects\domains\base_domainas_instance=AdminServeras_admin_port=7001as_admin_username=weblogicas_admin_password=weblogic

The configuration file is located in the following directory:<BOE_INSTALL_DIR>\deployment\config.<appserver> .

6. If the Performance Management 12.0 files you copied in step 2 are notlocated under the same folder structure as Box 1, to deploy Dashboardand Analytics you must do the following:a. Change directory to <BOE_INSTALL_DIR>\BusinessObjects

Enterprise 12.0\java\applications.b. Create a temporary directory named PerformanceManagement.

For example, type mkdir PerformanceManagement to create thetemporary directory.

c. Extract the file PerformanceManagement.war into the temporarydirectory named PerformanceManagement.For example, use the command jar xvfPerformanceManagement.war -C PerformanceManagement.

Note:The Java bin directory must be included in your PATH environmentvariable to use the jar command. The jar command is located in<BOE_INSTALL_DIR>/javasdk/bin/jar.

d. Rename PerformanceManagement.war to create a backup of theoriginal file.For example, type move PerformanceManagement.warPerformanceManagement.original to rename the WAR file.


Deploying with wdeploy3 To deploy web applications on a remote machine

e. Use a text editor to open the file PerformanceManagement/WEB-INF/web.xml and set the af.configdir parameter to the location ofthe InitConfig.properties file.The modified file should look like the example below.

<context-param><param-name>af.configdir</param-name><param-value>C:\Performance Management

12.0</param-value></context-param>

f. Save the changes to web.xml.g. Create a new PerformanceManagement.war in place of the original

one you renamed in step 4. This new WAR will contain the updatedweb.xml file.For example, the command jar cvfPerformanceManagement.war -C PerformanceManagementwill create PerformanceManagement.war from the contents of thePerformanceManagement directory.

h. Deploy PerformanceManagement.war using either the wdeploycommand or the web application server administrative console.

i. Verify that the web application deployed successfully, then removethe temporary PerformanceManagement directory.

7. Run the wdeploy script from its location in Box 2 by opening commandline console and entering the following:

<BOE_INSTALL_DIR>\deployment\wdeploy.bat<appserver>-Dwar_dir=

“<BOE_INSTALL_DIR>\BusinessObjects Enterprise12.0\java\applications\”

deployall

You can pass the -Dwar_dir (with the path to the WAR files) in thecommand line to specify the location from which wdeploy accesses noncustomized WAR files.

Tip:You can drop the deployable WAR files to non-default location by passingthe parameter -Dwork_dir=your_desired_location as part of thewdeploy command.


3Deploying with wdeployTo deploy web applications on a remote machine

Related Topics• The wdeploy configuration file• Prerequisites for using wdeploy


Deploying with wdeploy3 To deploy web applications on a remote machine

Manually deploying to a webapplication server

4

BusinessObjects Enterprise WAR filesThe functionality that makes up BusinessObjects Enterprise is dividedbetween several web applications to make it easy to deploy only thecomponents required by your organization.

The web applications are shipped in a format that cannot be deployed. Thewdeploy tool is used to automate the process of building the generic WARfiles, applying updates required by a specific web application server, andarchiving a new WAR file that can be deployed to the web application server.While it is possible for an experienced administrator to manually convert ageneric WAR file into a deployable format, it is strongly recommended thatthe wdeploy tool be used to automate the process.

Note:The BusinessObjects Enterprise setup program will automatically run wdeployto deploy web applications after installation. The following information is onlyrequired if you plan to deploy web applications after the initial installation ofBusinessObjects Enterprise is complete.

The setup program places the source code to be bundled into WAR files in<BOE_INSTALL_DIR>\BusinessObjects Enterprise12.0\java\applications. These files are extracted and modified bywdeploy in <BOE_INSTALL_DIR>\BusinessObjects Enterprise12.0\warfiles\WebApps.

The following table lists the WAR files the web applications that require them.

Web application(s)WAR file

CMC (administration tool)AdminTools.war

Web Intelligence, Desktop Intelligence, CMC, InfoViewAnalyticalReporting.war

Web services componentsBusinessProcessBI.war

CMC (entry point)CmcApp.war

CMCCmcAppActions.war


Manually deploying to a web application server4 BusinessObjects Enterprise WAR files

Web application(s)WAR file

Crystal Reports, CMC, InfoViewCrystalReports.war

Web services componentsdswsbobje.war

InfoView (entry point)InfoViewApp.war

InfoViewInfoViewAppActions.war

Open DocumentOpenDocument.war

Dashboard and Analytics, CMC, InfoViewPerformanceManagement.war

CMC, InfoViewPlatformServices.war

Dashboard and AnalyticsPMC_Help.war

CMC, InfoViewVoyagerClient.war

Xcelsius data presentationXCelsius.war

Xcelsius data presentationXCTemplateUploader.war

WAR file context rootsAll WAR files, with the exception of InfoViewApp and CmcApp, can bedeployed to fixed context root locations on your web application server. Thefollowing table lists the context roots that must be used, unless otherwisenoted.


4Manually deploying to a web application serverWAR file context roots

Default context pathWAR file

/AdminToolsAdminTools

/AnalyticalReportingAnalyticalReporting

/BusinessProcessBIBusinessProcessBI

/CmcApp

Note:You may use a different root context for CmcApp as long asthe root context matches the name of the WAR file. For exam-ple, a root context of /MyOrgCmc requires the WAR file to benamed MyOrgCmc.war.

CmcApp

/CmcAppActionsCmcAppActions

/CrystalReportsCrystalReports

/dswsbobjedswsbobje

/InfoViewApp

Note:You may use a different root context for InfoViewApp as longas the root context matches the name of the WAR file. For ex-ample, a root context of/MyOrgInfoView requires the WARfile to be named MyOrgInfoView.war.

InfoViewApp

/InfoViewAppActionsInfoViewAppActions

/OpenDocumentOpenDocument

/PerformanceManagementPerformanceManagement

/PlatformServicesPlatformServices


Manually deploying to a web application server4 WAR file context roots

Default context pathWAR file

/PMC_HelpPMC_Help

/VoyagerClientVoyagerClient

/XCelsiusXCelsius

/XCTemplateUploaderXCTemplateUploader

Predeployment without access to WebApplication servers

The wdeploy command can separate static and dynamic content fordeployment to web and web application servers.

When wdeploy is installed on a dedicated web server, the wdeploypredeploy or wdeploy predeployall commands can be used to deploystatic content directly to the web server's content directory. Some parametersare mandatory for particular web or web application servers:

Parameters required for predeploymentWeb or web appli-cation server

as_virtual_hostWebSphere Applica-tion Server

ws_dir, deployment_dir, connector_type

Note:When using Oracle HTTP Server with Oracle ApplicationServer, the following parameters must also be specified:connector_host, connector_port

Apache


4Manually deploying to a web application serverPredeployment without access to Web Application servers

Guidelines for deploying WAR filesTo successfully deploy the WAR files and to ensure your BusinessObjectsweb applications run properly, you should use the following guidelines.

1. Your web application server must be installed and running before youdeploy any WAR file.

2. The order in which you deploy the WAR files for your web applicationsdoes not matter. However, if your deployment environment involvesreverse proxy, there is a specific order you must follow. For moreinformation see “Modifying Default Security Behavior ” in the SAPBusinessObjects Enterprise Administrator's Guide.

3. When deploying a web application with functionality shared betweenmultiple WAR files, each WAR file must reside within the same level ofthe context path.

4. As a general rule, do not rename the WAR files.

Note:

• Only two web applications can be renamed: InfoViewApp and CmcApp. To rename InfoViewApp you can rename the applicationusing the web application server administration console.

• To rename CmcApp, you must update the appservice.url.defaultparameter in the web.xml file located in the WEB-INF directory of theCmcApp.war and CmcAppActions.war. Change CmcApp in the<param-value> tag shown below, to the new application name.

<context-param><param-name>appservice.url.default</param-name><param-value>/NewCMC/App/appService.jsp</param-value></context-param>

To manually deploy web applicationsEnsure that your web application server and CMS are both running.

The following steps will deploy a web application on a web application serverusing the application server's administrative console.


Manually deploying to a web application server4 Guidelines for deploying WAR files

The wdeploy tool must be used to generate deployable WAR files beforethey can be deployed to your web application server.1. Run the wdeploy predeploy command to prepare a single web

application, or wdeploy predeployall to prepare all web applications.

Example 1: using wdeploy predeploy to prepare InfoViewApp fordeployment to Tomcat.


Example 2: using wdeploy predeployall to prepare all webapplications for deployment to Tomcat.


Note:The predeploy and predeployall commands can be used onmachines that do not host a web application server, as long as theparameters required by the predeploy or predeployall commandsare specified.

The wdeploy command will prepare web applications for deployment ona web application server, and creates WAR or EAR files in <BOE_INSTALL_DIR>\deployment\workdir\<appserver>\applicationunless you specify the -Dwork_dir parameter.

2. Follow the manual deployment procedure specific to your web applicationserver.

Your web applications can now be manually deployed on your web applicationserver.

Repeat these steps for any other web applications that need to be installed.Related Topics• Where to find wdeploy• To deploy web applications on a remote machine• The wdeploy configuration file


4Manually deploying to a web application serverTo manually deploy web applications

Deployment with the administrativeconsole

JBoss

JBoss 4.2.3 manual deployment

Note:JBoss 4.2.3 is only supported by SAP BusinessObjects Enterprise XI 3.1Service Pack 3 or newer.

The JMX administrative console does not deploy web applications to JBossautomatically. To deploy web applications to JBoss, you must manually copythe web application file into the deploy directory.

Ensure that your JBoss web application server is installed, configured, andrunning before deploying WAR files.

The Java Server Faces (JSF) bundled with the JBoss web application serversmust be disabled for the Central Management Console (CMC) and InfoViewweb clients to work correctly.

To disable JSF, the following directories must be removed and JBossrestarted:• JBOSS_HOME\server\default\deploy\jboss-web.deploy

er\jsf-libs• JBOSS_HOME\server\default\tmp• JBOSS_HOME\server\default\work

Note:To use the Java log4j logging included with BusinessObjects Enterprise,refer to section 10.3.7 Using your own log4j.properties file - class loaderscoping in the JBoss Development Process Guide:http://docs.jboss.org/process-guide/en/html/logging.html#d0e3341.

The following deployment paths are based upon the different levels of service:• JBOSS_HOME\server\all\deploy• JBOSS_HOME\server\default\deploy


Manually deploying to a web application server4 Deployment with the administrative console

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

• JBOSS_HOME\server\minimal\deploy

1. Copy your WAR files to the appropriate context root sub-directory underone of the above paths, based upon the level of service provided by JBossfor your deployment.The web application will be automatically deployed by JBoss when thefile is copied to the appropriate directory.

2. Check the JBoss server log, and you should see a message similar tothe one shown below to confirm that the WAR deployment succeeded.

09:54:28,703 INFO [TomcatDeployer] deploy, ctxPath=/InfoViewApp,warUrl=.../tmp/deploy/tmp43109InfoViewApp-exp.war/

Oracle Application Server

Oracle Application Server 10g R3 administrative consolemanualdeployment

Ensure that your Oracle Application Server web application server is installed,configured, and running before deploying WAR files. You must also havecreated an Oracle container for Java (OC4J) container in which to runBusinessObjects Enterprise.

1. Open the Oracle Application Server Enterprise Manager server page athttp://WAS_HOSTNAME:PORT/em. Replace WAS_HOSTNAME with thehostname or IP address of your web application server, and PORT withthe port number used for HTTP. The default port for Oracle ApplicationServer is 7777.The Oracle Application Server Control page is displayed.

2. Click on the home OC4J container.The home group is displayed under the Groups heading.

3. In the home OC4J container, click on the Applications tab.Currently deployed web applications are displayed.

4. Click on the Deploy button.The Deploy: Select Archive window is displayed.


4Manually deploying to a web application serverDeployment with the administrative console

5. Ensure that the Archive is present on local host option is selected,unless the web application is already running on the server, in which caseselect Archive is already present on the server where ApplicationServer Control is running.

6. In the "Deployment Plan" section, ensure that Automatically create anew deployment plan is selected.

7. Enter the full path, or browse, to the WAR file in the Archive Locationfield.

8. Press theNext button to advance to the next step in the WAR deploymentwizard.Step 2 of 3, Deploy: Application Attributes is displayed.

9. Enter the application name and context root of the file you wish to deploy.By default, the context root will contain the application name. For example,for InfoView.war, the application name will be InfoView. When ready,press Next to proceed.The Step 3 of 3, Deploy: Deployment Settings page is displayed.

10. Select the class loading options you want enabled for the WAR file andpress Next to proceed.If your application requires any class libraries, click on Configure ClassLoading from the Deployment Tasks section.

11. Click on the Deploy button to complete the deployment.Check the output of the Progress Messages log field to ensure that webapplication deployed.


SAP NetWeaver

Prerequisites for deployment on SAP NetWeaver

Before deploying BusinessObjects Enterprise web applications to an SAPNetWeaver Application Server (any version), you must turn off HTMLcompression. For example, in SAP NetWeaver AS 7.0:



1. Logon to your SAP Visual Administrator tool (Windows) or DeployTool(Unix) using your Administrator account.

2. Navigate to: Cluster > Server > Services > HTTP Provider.3. Click the Properties tab on the right side of the screen.4. Select the AlwaysCompressed key and remove text/html and

*.html.5. Select the NeverCompressed key. At the bottom of the Value field, add

"text/html" (without the quotes).6. Click Update.7. Click the Save Properties button at the top of the screen.8. Restart your SAP NetWeaver Application Server.

SAP NetWeaver AS Java 7.0 administrative console manualdeployment

Ensure that your SAP NetWeaver AS Java 7.0 web application server isinstalled, configured, and running. Use the wdeploy predeploy commandto create WAR files that can be deployed to SAP NetWeaver AS Java 7.0.For more information, see Overview of wdeploy.

Use the wdeploy predeploy command to create WAR files that can bedeployed to SAP NetWeaver AS Java 7.0. For more information, seeOverview of wdeploy.1. Start the "Visual Administrator" tool by running go.bat from

<SAP_HOME>\sap\<System ID>\<JCxx>\j2ee\admin (e.g.<SAP_HOME>\sap\J2E\JC01\j2ee\admin). Connect to your J2EE engineusing the Administrator account.

2. In the "Visual Administrator", select the Cluster tab and expand theServer > Services > Deploy node within the J2EE tree.

3. Click Deploy & Start in the Runtime tab of the right-hand pane. If youwould like to start the web application manually later, click the Deploybutton instead.

4. In the "Deploy & Start" dialog window that appears, select the EAR filearchive you created earlier. Click OK when done.

5. In the "Deploy Dialog" window, verify the root context and display nameproperties. Press OK to deploy.The web application will now be deployed.




Tomcat

Tomcat 5.5 administrative console manual deployment

Ensure that your Tomcat 5.5 web application server is installed, configured,and running before deploying WAR files.

Log on to the "Tomcat Manager Console".• http://WAS_HOSTNAME:PORT/manager/html

1. Set theContext Path for the web application to be deployed. The contextpath must be the name of the WAR file, but without its extension. Forexample, to deploy a web application packaged as YOUR_WEB_APPLICATION.war, the context path must be YOUR_WEB_APPLICATION.

2. Set the XML Configuration File setting to be an XML file that containsthe context path and document base. For example: <ContextdocBase="<M>/YOUR_WEB_APPLICATION.war" path="<context_path>" crossContext="false" debug="0" reloadable="false" trusted="false"/>

3. Enter the full path to the WAR file and press the Deploy buttonThe WAR file is deployed.


Tomcat 6 administrative console manual deployment

Ensure that your Tomcat 6 web application server is installed, configured,and running before deploying WAR files.

Note:Tomcat 6 is only supported when using release 6.0.18 or newer.



Log on to the "Tomcat Manager Console".• http://WAS_HOSTNAME:PORT/manager/html

1. Set theContext Path for the web application to be deployed. The contextpath must be the name of the WAR file, but without its extension. Forexample, to deploy a web application packaged as YOUR_WEB_APPLICATION.war, the context path must be YOUR_WEB_APPLICATION.

2. Set the XML Configuration File setting to be an XML file that containsthe context path and document base. For example: <ContextdocBase="<M>/YOUR_WEB_APPLICATION.war" path="<context_path>" crossContext="false" debug="0" reloadable="false" trusted="false"/>

3. Enter the full path to the WAR file and press Deploy.The WAR file is deployed.


Tomcat 7 administrative console manual deployment

Ensure that your Tomcat 7 web application server is installed, configured,and running before deploying WAR files.

Log on to the "Tomcat Manager" application.• http://WAS_HOSTNAME:PORT/manager/html (HTML GUI)

1. Set the Context Path for the web application to be deployed.The context path must be the name of the WAR file, but without itsextension and prefaced by a forward-slash. For example, to deploy a webapplication packaged as YOUR_WEB_APPLICATION.war, the contextpath must be /YOUR_WEB_APPLICATION.

2. Set the XML Configuration File setting the location of an XML file thatcontains the context path and document base.

The document base is the predeployed WAR file you created with thewdeploy predeploy command. For example:

<ContextdocBase="<M>/YOUR_WEB_APPLICATION.war"path="<context_path>"



crossContext="false" debug="0" reloadable="false"trusted="false"/>

3. Enter the full path to the WAR file and press Deploy.The WAR file is deployed.


Special considerations for deploying on Tomcat clusters

To manually deploy web applications to a Tomcat web application clusterdistributed over multiple machines, you need to deploy the web applicationson to each Tomcat instance. You can use the administrative console todeploy the BusinessObjects Enterprise web applications to the webappssubfolder in the Tomcat home directory for each server instance.

Tip:It is recommended that you install and configure a hardware or software loadbalancer if running BusinessObjects Enterprise web applications on a Tomcatweb application cluster. To configure the load balancer and cluster setupplease consult your Tomcat documentation.

WebLogic

WebLogic 10 or 10.3 administrative consolemanual deployment

Ensure that your WebLogic 10 or 10.3 web application server is installed,configured, and running before deploying WAR files. You must also havecreated a WebLogic domain in which to run BusinessObjects Enterprise.See your WebLogic 10 or 10.3 documentation for information about creatinga new domain.

Note:

• Deployable web applications for WebLogic are in the following format inthe wdeploy workdir folder:



WebServices (ProcessProcessBI and dswsbobje) are folders.•• AnalyticalReporting and PerformanceManagement are EAR files.• The remaining web applications are in WAR file format.

• WebLogic deployments must use an extracted dswsbobje.war. See Todeploy dswsbobje.war to WebLogic.

1. Open the "WebLogic Administrative Console" with a web browser at ahttp://WAS_HOSTNAME:PORT/console where WAS_HOSTNAME isthe name of your WebLogic server and PORT is the port number on whichthe admin server listens.The "WebLogic Server Administration Console" web page is displayed.

2. In the left-hand navigation pane, clickDomain Structure >Deployments.The "Summary of Deployments" page is displayed.

3. Click the Lock and Edit button in the left-hand pane.The domain is locked for editing.

4. Press the Install button and navigate to the WAR file you wish to deploy.Select the Install this deployment as an application option. Whenyou've selected the file and specified any other parameters in the wizard,click the Finish button to deploy the file.The WAR file is deployed to the WebLogic server.

5. Press the Activate Changes button to apply you're the changes to theweb application server.Your changes are saved.

6. When your WAR file has been deployed, you must press the Start buttonto initiate its execution.The web application starts.


To deploy to a WebLogic clusterTo manually deploy BusinessObjects Enterprise web applications to aWebLogic cluster distributed over multiple machines, you need to deploy theweb applications to the machine hosting the WebLogic administration server.



Once all the required web applications have been installed, you can use theWebLogic administration console to deploy these applications to the cluster.

Tip:It is recommended that you install and configure a hardware or software loadbalancer if running BusinessObjects Enterprise web applications on aWebLogic web application cluster. To configure the load balancer and clustersetup please consult your WebLogic documentation.

To deploy to a WebLogic cluster use the following general workflow:

1. After installing and setting up the WebLogic cluster, you need to createa WebLogic XML registry using the following default settings and targetit to all managed servers as shown below:

ValueProperty

Registry nameName

weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl

Document Builder Facto-ry

weblogic.apache.xerces.jaxp.SAXParserFactoryImpl

SAX Parser Factory

weblogic.apache.xalan.processor.TransformerFactoryImpl

Transformer Factory

2. If BusinessObjects Enterprise is installed to the same machine hostingthe WebLogic administration server, skip to step 6. If BusinessObjectsEnterprise and the WebLogic administration server run on differentmachines, you must first copy the wdeploy tool and environment to themachine hosting the WebLogic administration server.

If you plan to deploy PerformanceManagement.war to the WebLogiccluster, you must copy InitConfig.properties from<BOE_INSTALL_DIR>\Performance Management 12.0\ to eachmanaged server and ensure the file path of InitConfig.properties matchesthe value specified for af.configdir param in web.xml in PerformanceManagement.war as shown below:

<context-param><param-name>af.configdir</param-name>

<param-value>C:\Program Files\BusinessObjects\Performance Management 12.0



</param-value><context-param>

3. Modify the config.weblogic10 or the config.weblogic9 locatedin <BOE_INSTALL_DIR>\deployment\.You need to specify information for the administration server. For example:

as_domain_dir=c:\bea\user_projects\domains\base_domainas_instance=AdminServeras_admin_port=7001as_admin_username=weblogicas_admin_password=password

4. Modify the PersistentStoreType setting in the weblogic.xml file locatedin the following directory:<BOE_INSTALL_DIR>\deployment\templates\weblogic.xml.The modified weblogic.xml settings will look like the example below:

<weblogic-web-app><session-descriptor>

<session-param><param-name>PersistentStoreType</param-

name><param-value>replicated</param-

value></session-param>

</session-descriptor>

5. Open a command-line console and run the following command:

wdeploy.bat weblogic10 predeployall

6. Use the WebLogic administration console to separately install each webapplication you want to deploy from the following directory:<BOE_INSTALL_DIR>\deployment\workdir\weblogic10\application\.

7. In the "Select deployment targets" workflow select the cluster name andAll servers in the cluster.

8. After the "Select deployment targets" is complete, select all the installedapplications and go to Start > Servicing all requests.



Example:

“Deploying the complex deployment scenario” in this manual includes astep-by-step description of how to deploy web applications to a WebLogic10 cluster.

Related Topics• To deploy the WAR files to WebLogic 10• To prepare the WAR files for deployment

To deploy dswsbobje.war to WebLogicBefore deploying web services WAR file on a WebLogic application server,the user must extract dswsbobje.war. If the WAR file is not extracted andredeployed, web services applications may display the error message “AnXSD Exception occurred”.

1. Extract dswsbobje.war to a directory on the WebLogic web applicationserver.

2. Log on to the "WebLogic Administration Console".3. Click Lock & Edit.4. Go to Domain Structure > Deployments and click Install.5. Browse to the extracted dswsbobje.war directory.6. Select the directory and click Next.7. Select Install this deployment as an application and click Next.8. Verify the settings and click Finish.

A message will be displayed when the dswsbobje.war web applicationhas been successfully deployed. The list of web applications contains thedswsbobje web application.

9. Select the dswsbobje web application and click Start.10. Click Activate Changes.11. Select the dswsbobje web application and click Start.12. Press OK to confirm the changes.

The dswsbobje web application is started.

13. Open the web application in a web browser to confirm that it now runs.Related Topics• After deploying web applications



WebSphere

WebSphere 6.1 administrative console manual deployment

Ensure that your WebSphere 6.1 web application server is installed,configured, and running before deploying WAR files.

Log in to the "WebSphere Application Server Administration" console usingthe following URL: http://WAS_HOSTNAME:PORT/admin. The WebSphereadmin console's default port number is 9060.

1. Under the Applications heading of the console navigation menu, clickEnterprise Applications on the left navigational pane.

2. Click the Install button and navigate to the location of the WAR file todeploy. If deploying from a remote file system, select the Remote FileSystem option.

3. Enter a context root for the WAR file (e.g. /CmcApp for CmcApp.war)and press the Next button.

4. On the "Step 1" screen, give a unique name for your web application andproceed to the "Step 2" screen.

5. Under "Map Modules to Servers", highlight the server you created (orhighlight server1 if you didn't create your own) from the Clusters andServers and enable the Select checkbox. Proceed to the "Step 3" screen.

6. Select the virtual host you created (or default_host if you didn't createyour own) from the Virtual Host drop-down list. Proceed to the "Step 4"screen.

7. Review the summary page, and press Finish when done.8. Click Save to Master Configuration.9. Click the Save link, then the Save button.10. Under the Applications heading of the console navigation menu, click

Enterprise Applications on the left navigational pane.11. Verify that the WAR file was deployed, then click the Start button.

Repeat steps 1 to 11 for each web application being deployed.




WebSphere 7.0 administrative console manual deployment

Ensure that your WebSphere 7.0 web application server is installed,configured, and running. Use the wdeploy predeploy command to createWAR files that can be deployed to WebSphere 7.0. For more information,see Overview of wdeploy.

Log in to the WebSphere "Integrated Solutions Console" with theAdministrator account. You can run the WebSphere "Administrative console"program, or use a web browser to open http://WAS_HOSTNAME:PORT/ibm/console where WAS_HOSTNAME is the name of yourWebSphere server, and PORT is the port number on which the server listensfor login requests. The default port number is 9060.

1. Select Applications > Application Type > WebSphere enterpriseapplications in the menu.The "Enterprise Applications" screen appears.

2. Click Install.The "Preparing for the application installation" screen "Path to the newapplication" appears.

3. Click Browse and choose the web application's WAR file.The fully-qualified path to the web application's WAR file appears in the"Full Path" field.

4. Proceed to the next screen.The "How do you want to install the application?" screen appears.

5. Accept the default option of "Fast Path" and proceed to the next screen.The "Install New Application" screen "Step 1: Select install options"appears.

6. Accept the default options and proceed to the next screen.The "Step 2: Map modules to servers" screen appears.

7. Accept the default options and proceed to the next screen.The "Step 3: Map virtual hosts for Web modules" screen appears.

8. Accept the default options and proceed to the next screen.The "Step 4: Map context roots for Web modules" screen appears.



9. Enter a context root for the web module selected and proceed to the nextscreen.For example, when deploying CmcApp.war, the context root could be/CmcApp.The "Step 5: Summary" screen appears.

10. Review the summary and click Finish.The web application is installed and a master configuration changeconfirmation message appears.

11. Click Save directly to the master configuration.The web application configuration is saved and you are returned to the"Enterprise Applications" screen. Notice that the web application is notyet running.

12. Choose the web application from the list of administered resources.The "Enterprise Applications" configuration screen appears.

13. Click Manage Modules.The "Manage Modules" screen appears.

14. Select the web application module (click the link shown in the "Module"column).The "Manage Modules General Properties" screen appears.

15. SelectClasses loaded with application class loader first (parent last)from the "Class loader order" property.A confirmation message appears.

16. Click Save directly to the master configuration.The web application configuration is saved and you are returned to the"Manage Modules" screen.

17. Click OK.A master configuration change confirmation message appears.

18. Click Save directly to the master configuration.The web application configuration is saved and you are returned to the"Enterprise Applications" screen.

19. Select the web application checkbox and click Start.A message appears to confirm that the web application startedsuccessfully.



The web application has been deployed, configured, and started. Test theweb application by using the root context you provided above. Repeat thesesteps for each web application.Related Topics• After deploying web applications

Web Services on WebSphere 7.0After using the wdeploy command to deploy Web Services to WebSphere7.0, the List of Web Services link is not available in the SAPBusinessObjects Enterprise Web Services portal interface.



1. Start the WebSphere 7.0 web application server.2. Use the wdeploy command to deploy dswsbobje.war and Busi

nessProcessBI.war.3. Stop the WebSphere 7.0 web application server.4. Copy the file<WEBSPHERE7_INSTALL_DIR>\profiles\AppSrv01\in








Disable WebSphere JSF implementation

If pages rendered by WebSphere 7 do not show cached values correctly, itmay be using its own version of the Java Server Faces (JSF) library, ratherthan the JSF implementation supplied with BusinessObjects Enterprise. Tocorrect this problem, you must manually reconfigure WebSphere for eachweb application that uses JSF: CmcApp, CmcAppActions, andPlatformServices.

To disable the JSF implementation supplied with WebSphere, follow theinstructions below.

1. Log in to the "WebSphere Application Server Administration" consoleusing the following URL: http://WAS_HOSTNAME:PORT/admin. TheWebSphere administration console's default port number is 9060.

2. Browse to YOUR_WEB_APPLICATION > Manage Modules >YOUR_WEB_APPLICATION.warReplace YOUR_WEB_APPLICATION in the example above with the nameof your web application.

3. Stop the web application, so its settings can be modified.4. SelectClasses loaded with application class loader first (parent last)

from the combo box.Restart the web application.

5. Repeat these steps for all other web applications that use JSF.

Reload pages that display cached values. Cached values are now displayedcorrectly.

To deploy to a WebSphere cluster

To manually deploy BusinessObjects Enterprise web applications to aWebSphere web application cluster distributed over multiple machines, youneed to deploy the web applications to the machine hosting the WebSphereDeployment Manager. Once all the required web applications have beeninstalled, you can use the WebSphere Integrated Solutions Console toseparately deploy these applications to the cluster.



Tip:It is recommended that you install and configure a hardware or software loadbalancer if running BusinessObjects Enterprise web applications on aWebSphere web application cluster. To configure the load balancer andcluster setup please consult your WebSphere documentation.

To deploy your web applications to a WebSphere cluster use the followinggeneral workflow:

1. If BusinessObjects Enterprise is installed to the same machine hostingthe WebSphere Deployment Manager, skip to step 3. If BusinessObjectsEnterprise and the WebSphere Deployment Manager runs on differentmachines, you must first copy the wdeploy tool and environment to themachine hosting the WebSphere administration server.

If you plan to deploy PerformanceManagement.war to the WebSpherecluster, you must copy InitConfig.properties from<BOE_INSTALL_DIR>\Performance Management 12.0\ to eachmanaged server and ensure the file path of InitConfig.properties ismatches the value specified for af.configdir parameter in web.xml inPerformanceManagement.war as shown below:

<context-param><param-name>af.configdir</param-name>

<param-value>C:\Program Files\BusinessObjects\Performance Management 12.0

</param-value><context-param>

Note:The InitConfig.properties file should be located in C:\ProgramFiles\BusinessObjects\Performance Management 12.0 oneach machine hosting a managed WebSphere server.

2. Modify the config.websphere6 file located in <BOE_INSTALL_DIR>\deployment\.You need to specify information for the administration server. For example:

as_dir=C:\Program Files\IBM\WebSphere\AppServeras_soap_port=8779as_virtual_host=default_hostas_admin_is_secure=falseenforce_file_limit=true



3. Open a command-line console and run the following command:wdeploy.bat websphere6 predeployall

4. Open the WebSphere Integrated Solutions Console.5. Go toApplications > Enterprise Applications to separately install each

web application you want to deploy from the following directory::<BOE_INSTALL_DIR>\deployment\workdir\websphere6\application\

Note:All web applications are stored as EAR modules.

6. Follow the Install new application steps in the console to install the webapplication

Note:In "Map modules to servers", make sure that you highlight the targetcluster and select the module to install before clicking Apply.

7. After installing the application, click Save.8. Repeat steps 5-7 for each EAR file you want to install.9. Go toSystem administration >Nodes and select the nodes in the cluster

that are not indicated as synchronized10. Click Synchronize.11. Go to Applications > Enterprise Applications to start the application

you just installed.



Sample DeploymentScenarios

5

Overview of deployment scenariosThis section provides three sample deployment scenarios to illustrate howSAP BusinessObjects Enterprise can be configured. Each example includesa deployment diagram, key tasks, configuration details, functionalrequirements and pre-conditions. The three scenarios are:• Desktop client to server• Basic n-tier• Complex deployment

Desktop client to server scenario

Desktop client to server overview

This scenario illustrates a simple client to server scenario which involves adesktop client application - Desktop Intelligence - connecting to theBusinessObjects Enterprise back-end server behind a firewall.

System layers

• Data Tier: one machine with existing database server• Server Tier: one machine for hosting the framework servers and another

for all other BusinessObjects servers• Client Tier: one machine for installing and running Desktop Intelligence

Configuration details• A firewall exists between client and server tiers• Only the ports required for the communication between the desktop client

and the server tier are open on the firewall• BusinessObjects servers are distributed over two machines.


Sample Deployment Scenarios5 Overview of deployment scenarios

Windows Server 2003 SP2 EnterpriseEdition

Installation platform for BusinessObjects Enterprise

Microsoft SQL Server 2005Database for Central Management Server (CMS)

Not relevantWeb application server

Linux iptablesFirewall

Desktop client to server diagram

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

Summary of required tasks

The desktop client to server deployment scenario involves the following tasksin the order listed below.

1. Setting up the data tier.2. Setting up the server tier.3. Setting up the client tier.4. Setting up the firewall.


5Sample Deployment ScenariosDesktop client to server scenario

Deploying the desktop client to server scenario

To set up the data tier

This scenario calls for Microsoft SQL Server 2005 running on a supportedMicrosoft Windows operating system. Advanced administrative knowledgeof Microsoft SQL Server 2005 and Microsoft Windows products is assumed.

Install a version of Microsoft Windows with the appropriate service packsand updates required by Microsoft SQL Server 2005. If your CMS anddatabase servers are installed on separate computers, ensure that you havea working network connection between the machines.1. Install Microsoft SQL Server 2005.

Make note of the following settings you use during the installation. Youwill need these settings when you come to install BusinessObjectsEnterprise servers and clients.

ExampleSetting

DBSERVER1_sqlName of database server instance

saAdministrator account name

passwordAdministrator account password

UTF-8Database character set encoding

Microsoft SQL Server 2005 is now installed and ready to be used byBusinessObjects Enterprise.

2. Create or import a new database for the CMS data, as well as auditingor Dashboard and Analytics databases if required.Record the settings used for creating of the CMS database.


Sample Deployment Scenarios5 Desktop client to server scenario

ExampleCMS database setting

BOE120CMS database name

bobjuserUsername for CMS database access

mypasswordPassword for CMS database access

A CMS database is now available for use.

3. Set up a DSN database connection on the machine hosting the CMS,plus any clients that need direct database access.On each system that needs to access the database, create a SystemDSN entry in the Microsoft "ODBC Data Source Administrator" ControlPanel tool. Enter the settings you used when you created the databasesabove.The machine hosting the CMS is now able to communicate with thenewly-created Microsoft SQL Server 2005 databases.

You have set up machines to run the CMS and its databases.

Verify the connectivity between your machine running the CMS and databasemachine by attempting to connect to the database(s) from the CMS machine.The default port used by Microsoft SQL Server is 1433. The port numberused by your database must be entered during the BusinessObjectsEnterprise installation.

Note:This scenario does not include a network firewall between the CMS anddatabase machines.

Remember:The ability to connect to your database server from the machine running theCMS may require a change to the Windows Firewall settings on bothmachines.

To set up the server tier - framework servers

Windows Server 2003 SP2 Enterprise Edition has to be installed and running.You need administrative privileges on both machines that will host theBusinessObjects Enterprise server components. Designate a machine asSERVER 1 on which you will install framework servers. Designate secondmachine, SERVER 2, on which you will install all other server components.



Follow the instructions below to install the framework servers.1. Run setup.exe from the root directory of your product distribution.

The "Please Choose Setup Language" dialog is displayed.

2. Select your language for the installation setup from the pull-down listprovided and click OK.

The "Welcome to the BusinessObjects Enterprise Installation Wizard" isdisplayed.

3. Click Next.The "License Agreement" screen is displayed.

4. Select I accept the License Agreement and click Next.The "User Information" screen is displayed.

5. Enter the requested information for Full Name, Organization, andProduct Keycode. Click Next.The "Choose Language Packs" screen is displayed.

6. Select any Language Packs you want to install. Click Next.

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

The "Install Type" screen is displayed

7. Choose Custom or Expand install.The "Select Features" screen is displayed.

8. Left-click on the icon beside Web Tier Components and select Entirefeature will be installed on local hard drive.

9. Left-click on the icon beside Client Components and select Entirefeature will be unavailable.

The Client Components icon changes to .

10. Left-click on the icon beside Server Components and select Entirefeature will be unavailable.

11. Expand Server Components.a. Left-click on the icon beside Central Configuration Manager and

select Entire feature will be installed on local hard drive.b. Left-click on the icon beside Central Management Server and select

Will be installed on local hard drive.



The Central Management Server option will be installed but not thetwo subfeatures listed under the item: MySQL and Auditing.

c. Left-click on the icon beside Event Server and select Entire featurewill be installed on local hard drive.

d. Left-click on the icon beside Input File Repository Server and selectEntire feature will be installed on local hard drive

e. Left-click on the icon beside Output File Repository Server andselect Entire feature will be installed on local hard drive

f. Click Next.The "CMS Clustering" screen is displayed.

12. Select Yes, Enter information for the new CMSFields are provided for you to enter and confirm a password for the CMSAdministrator.

13. Enter BOBJ_admin in bothCMSAdministrator Password andConfirmpassword.

14. Click Next.The "Server Intelligence Agent" screen is displayed.

15. Enter SIA1 in the Node Name field and click Next.



The "CMS Database Information" screen is displayed.

16. Select SQL Server (ODBC) from the Select existing CMS databasedrop-down list and click Browse.The "SQL Server Logon" screen is displayed

17. Enter the following SQL Server user information and then click Next.a. Select my company database as the data source.b. Enter bobjuser as your Login ID and password as your Password.c. Select BOE120 from the Database drop-down list

d. Click OK.You are returned to the "CMS Database Information" screen.

18. Click Next.The "Start Installation" screen is displayed.

19. Click Next to start the installation.



Click Finish once the following screen is displayed.

Click Finish once the following screen is displayed.

You must now install all remaining BusinessObjects Enterprise servercomponents on SERVER 2.

To add servers to the server tierYou need to install the framework servers on SERVER 1 before you can addany servers to the server tier.

Use the following instructions to add BusinessObjects Enterprise servers tothe CMS cluster you have installed on SERVER 1.1. Run setup.exe from the root directory of your product distribution.


Note:If you are installing from a DVD and if the Autoplay is enabled for yourDVD-ROM drive, the Autorun program will start automatically.








6. Select any Language Packs you want to install. Click Next.

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

The "Install Type" screen is displayed




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


select Entire feature will be unavailable.b. Left-click on the icon beside Central Management Server and select

Entire feature will be unavailable.c. Left-click on the icon beside Event Server and select Entire feature

will be unavailable.d. Left-click on the icon beside Input File Repository Server and select

Entire feature will be unavailable.e. Left-click on the icon beside Output File Repository Server and

select Entire feature will be unavailable.



After implementing the selections, the "Select Features" screen shouldappear as shown in the following image.

11. Click Next.The "CMS Clustering" screen is displayed.

12. Enter SERVER1 for CMS Host Name, and password in both CMSAdministrator Password and Confirm password.


14. Enter SIA2 in the Node Name field and click Next.The "Start Installation" screen is displayed.

15. Click Next to start the installation.16. Click Finish once the following screen is displayed.



To assign static port values to serversAccess the Central Management Console (CMC) on the machine namedSERVER1. Use the machine you designated to run the client tier, and opena browser and type in the following URL: http://SERVER1:8080/CmcApp/App/.

You need to assign static port values to the following servers:

Server name

SIA1.CentralManagementServer

SIA1.InputFileRepository

SAI1.OutputFileRepository

1. Type the following configuration information and click Log On.



Required configuration informationField

SERVER1System

AdministratorUser Name

BOBJ_adminPassword

EnterpriseAuthentication Type

The CMC Home page is displayed.

2. Click Servers under the "Organize" column.A list of all available servers is displayed in a new screen.

3. Double-click the SIA1.CentralManagementServer entry.The SIA1.CentralManagementServer properties are displayed.

4. Deselect Auto assign and type 6402 in Request Port under "CommonSettings".

5. Click Save & Close.The list of available servers is displayed again.

6. Repeat steps 3-5 for the following servers:

Port number to specifyServer name

6404SIA1.InputFileRepository

6406SIA1.OutputFileRepository

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

To configure the firewall

The iptables firewall is running on a supported Red Hat Linux operatingsystem with two network interface cards (NIC). One network card (interfaceeth0) is connected to an internal secure network, the other (interface eth1)is connected to an external unsecure network, such as the internet.



Note:Advanced administrative knowledge of Red Hat Linux products is requiredfor these steps.

The following steps illustrate how to forward requests from clients on anunsecure external (interface eth1) network to the server tier running on asecure, firewalled network (interface eth0).1. Log in to your Red Hat Linux server.

Note:As iptables is configured from the command-line, you need root priviliges.This can be achieved with the su or sudo commands, by becoming amember of the admin group, or by logging in as the root user.

2. Determine the network IP address, interface, and media access card(MAC) information for each NIC in your system.

Tip:The command ifconfig -a will display network interface information.

Record the network information in a safe place.

3. Add exceptions to the iptables firewall rules that forward incoming clientrequests to the server tier on the appropriate ports.

For example, the sever named CMS Server uses two port numbers tocommunicate with clients. You must forward both ports on the firewall'sexternal NIC to the CMS server connected to the internal NIC.

Note:This must be done for each port used by every server you want accessiblefrom outside your network. Typical servers used by external clients includethe CMS, Desktop Intelligence, and the Connection Server.

In this scenario, four ports must be forwarded to the server tier fromexternal clients on the external network (eth1):• CMS Name Server port: 6400.• CMS Request port: 6402.• Input File Repository Server (FRS) port: 6404.• Output FRS port 6406.

Tip:To determine which ports are used by servers, open the CentralManagement Console (CMC) and go to Servers >Central Management



Server > your server and note the number for Request Port and NameServer Port.

Clients on an unsecured network outside the firewall can now access theserver tier through the firewall.

To set up the client tier

Windows Server 2003 SP2 Enterprise Edition has to be installed and runningon the machine on which you will install Desktop Intelligence.

Follow the steps below to Desktop Intelligence and

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

"Please Choose Setup Language" is displayed.

3. Select the language for the installation setup from the pull-down listprovided and click OK.



The "Welcome to the BusinessObjects Enterprise Installation Wizard" isdisplayed after you specify a language for the installation setup.

4. Click Next to proceed with the installation setup.The "License Agreement" screen is displayed.



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

6. Select the language packs and click Next.The "Directory Selection" screen is displayed.



7. Accept the default directory by clicking "Next".The "Select Features" screen is displayed.


The Client Components icon changes to

9. Expand Client Components and left- click on Desktop Intelligence.



10. Select Entire feature will be installed on local hard drive and click Next.The "Start Installation" screen is displayed.

11. Click Next to start the installation.The installation process begins and is completed once "BusinessObjectsEnterprise Client Tool has been successfully installed" is displayed.



12. Click Finish.The Desktop Intelligence is now installed on your machine.

13. Go to Programs > BusinessObjects XI 3.5 > BusinessObjectsEnterprise Client Tools > Desktop IntelligenceThe "User Identification" dialog is displayed.

14. Provide the following information:a. Type SERVER1 for System.b. Type Administrator for User Name.c. Type password for Password.



The "New Report Wizard" is displayed.

15. Select Generate a standard report and click Begin.



Basic N-tier scenario

N-tier scenario overview

This section describes how to setup a scenario in which a web browseraccesses BusinessObjects Enterprise system through web applications.

System layers

• Data Tier: One machine used to host the database server.• Server Tier: Three machines hosting the framework, processing and

performance management (PMC) servers.• Web Tier: One machine in hosting the web application server.• Client Tier: One machine running the Live Office application.

Configuration details



Oracle 10g R2Database for Central Management Server (CMS)

Oracle 10g R3Web application server

Linux iptablesFirewall

Basic n-tier diagram



Sample Deployment Scenarios5 Basic N-tier scenario


The basic n-tier deployment scenario involves the following tasks in the orderlisted below.

1. Setting up the data tier2. Setting up the server tier3. Setting up the web tier4. Setting up the firewall5. Setting up the client tier

Deploying the N-tier scenario


The following steps require that you have already installed a version ofMicrosoft Windows that meets the installation requirements for Oracle 10gR2. Advanced administrative knowledge of Oracle and Microsoft Windowsproducts is assumed.


5Sample Deployment ScenariosBasic N-tier scenario

This database will be used to hold CMS data. Additional database will becreated for auditing or performance management if required.

If your CMS and database servers are installed on separate computers,ensure that you have a working network connection between the machines.

Note:In addition to databases for CMS, auditing, or performance management,you also require access to your existing corporate reporting database. Thisis the database that hosts your organization's data, against whichBusinessObjects Enterprise applications run.

1. Install Oracle 10g R2.Make note of the following settings you use during the installation. Youwill need these settings when you come to install BusinessObjectsEnterprise servers and clients.

ExampleSetting

DBSERVER1_oraName of database server

systemAdministrator account name



An Oracle database is now installed and ready to be used byBusinessObjects Enterprise.

2. Create or import a new tablespace for the CMS, as well as auditing orDashboard and Analytics databases if required.Record the settings used for creating of the CMS database.




mycompanyCMS tablespace name

mycompanyuserUsername for CMS ta-blespace access

mypasswordPassword for CMS ta-blespace access

create table, create session, create procedureSystem privileges for useraccess

A CMS tablespace is now available for use.

3. Create or import a new tablespace for the auditing database, if required.Record the settings used for creating of the auditing tablespace.

ExampleAuditing database setting

audituserUsername for auditing tablespaceaccess

auditpasswordPassword for auditing tablespaceaccess

create table, create session, createprocedure

System privileges for user access

An auditing database is now available for use.

4. Create or import a new tablespace for the Dashboard and Analyticstablespace, if required.Record the settings used for creating of the Dashboard and Analyticstablespace.



ExampleDashboard and Analyticsdatabase setting

pmuserUsername for Dashboard and Ana-lytics database access

pmpasswordPassword for Dashboard and Analyt-ics database access

create table, create session, createprocedure

System privileges for user access

A Dashboard and Analytics tablespace is now available for use.

5. Install the Oracle database drivers onto all machines that make up theCMS, plus any clients that need direct database access.The machines for your CMS are now able to communicate with the newlycreated Oracle 10g R2 databases.

You have set up machines to run the CMS and its databases.

Verify the connectivity from the machines running the CMS to the machinesrunning the database, by attempting to connect to the database from theCMS machine(s).

Note:This scenario includes a network firewall between the client web browserand web application server. Ensure that this firewall is configuredappropriately.

Remember:The ability to connect to your database server from the machine running theCMS may require a change to the Windows Firewall settings on bothmachines.

To set up the server tier

Windows Server 2003 SP2 Enterprise Edition has to be installed and runningon the three machines running the server tier. You need administrativeprivileges on the three machines that will host the BusinessObjects Enterpriseservers. Designate the machines SERVER1, SERVER2, and SERVER3.

Follow the instructions below to install all the servers on SERVER1.1. Run setup.exe from the root directory of your product distribution.









6. Select any Language Packs you want to install. Click Next.The "Install Type" screen is displayed

7. Select New and Use an existing database server in the "Install Type"screen. Click Next.The Server Components Configuration screen is displayed.

8. Enter password in both Password and Confirm password. Click Next..The "Server Intelligence Agent" screen is displayed.

9. Enter SIA1 in Node Name and click Next.The "CMS Database Information" screen is displayed.

10. Select Oracle from the CMS database drop-down list.The "SQL Server Logon" screen is displayed.

11. In the fields provided provide the following configuration for your Oracledatabase:

valueSetting

DBSERVER1_oraServer

systemUsername

passwordPassword

12. Select Auditing Database and repeat steps 10-11.



13. Select the Install Tomcat application server option and click Next.The "Configure Tomcat" screen is displayed

14. Do not modify any of the values in the input fields and click Next.The "Start Installation" screen is displayed.

15. Click Next to start the installation.The installation process begins and is completed when "BusinessObjectsEnterprise has been successfully installed" is displayed.

16. Select Launch BusinessObjects Administration Console and clickFinish to exit.A new browser window opens and within a few seconds you are promptedto log into the Central Management Console (CMC).

17. Verify the connectivity between the BusinessObjects CMS and your MSSQL server by logging onto the CMC.a. Type SERVER1 in System.b. Type Administrator in User name .c. Type password in Password.d. Click Log On to access the CMC.

Accessing the CCM home page, verifies that the BusinessObjectsEnterprise CMS is communicating with the Microsoft SQL Server 2005database server.

You must now install another set of BusinessObjects Enterprise servers onthe machine designated SERVER2.

To add processing servers to clusterYou need to install the framework servers on SERVER 1 before you can addany servers on SERVER2.

Use the following instructions to install BusinessObjects Enterprise serversto SERVER2.1. Run setup.exe from the root directory of your product distribution.



3. ClickNext in the "Welcome to the BusinessObjects Enterprise InstallationWizard".The "License Agreement" screen is displayed.











select Entire feature will be unavailable .b. Left-click on the icon beside Event Server and select Entire feature

will be unavailable.c. Left-click on the icon beside Input File Repository Server and select

select Entire feature will be unavailable.d. Left-click on the icon beside Output File Repository Server and

select Entire feature will be unavailable.e. Left-clickDashboard andAnalytics Servers and selectEntire feature

will be unavailable.f. Left-clickCentral Management Server and select Entire feature will

be unavailable. .



After implementing the selections, the "Select Features" screen shouldappear as shown in the following image.


12. Enter SERVER1 for CMS Host Name, 6400 for Existing CMS Port, andpassword for CMS Administrator Password.


14. Enter SIA2 in the Node Name field and click Next.The "Start Installation" screen is displayed.

15. Click Next to start the installation.16. Click Finish once the following screen is displayed.



To add PMC servers to the clusterYou need to install the framework servers on SERVER1 before you can addany servers to the server tier.

Use the following instructions to add BusinessObjects Enterprise servers toSERVER3.1. Run setup.exe from the root directory of your product distribution.













10. Left-click on the icon beside Server Components and select Entirefeature will be unavailable.

11. Expand Server Components. Left-click Dashboard and AnalyticsServers and select Entire feature will be installed on local hard drive.


13. Enter SERVER1 for CMS Host Name, 6400 for Existing CMS Port, andpassword for CMS Administrator Password.


15. Enter SIA3 in the Node Name field and click Next.16. Select Oracle from the CMS database drop-down list.

The "SQL Server Logon" screen is displayed.

17. Select Auditing Database and repeat steps 10-11.18. Click Next to start the installation.19. Click Finish once the following screen is displayed.



To set up the web tier

You need to install and configure Oracle Application Server 10g R3 on amachine running Windows Server 2003 SP2 Enterprise Edition. To configurethe application use the following setup parameters.

valueSetup parameter

8080Port

adminUsername

oraclePassword

WEBSERVER1Server Instance

c:\product\10.1.3\Oracle_AS1Installation Directory

Use the following steps to install the web applications to the“managedserver1” machine.



1. Run setup.exe from the root directory of your product distribution.The "Please Choose Setup Language" dialog is displayed.







7. Choose Web Tier and click Next .The "Select Features" screen is displayed.

8. Expand Web Tier Components.9. Left-click on the icon beside Tomcat and select Entire Feature will be

unavailable. Click Next.The "CMS Clustering" screen is displayed.

10. Type SERVER1 for Existing CMS Hostname, 6400 for Existing CMSPort, and password for CMS Administrator Password. Click Next.



The "Select Web Application Server" screen is displayed.

11. Choose Oracle Application Server 10g R3 from list of supported webapplication servers and click Next.



The "Configure Web Application Server" screen is displayed.

12. Type 8080 for Port, admin for Username, password for Password, andWEBSERVER1 for Server Instance.



13. Click Next twice to start the installation.The installation process begins and is completed when "BusinessObjectsEnterprise has been successfully installed" is displayed.

14. Click Finish to exit.


The iptables firewall is running on a supported Red Hat Linux operatingsystem with two network interface cards (NIC). One network card (interfaceeth0) is connected to an internal secure network, the other (interface eth1)is connected to an external unsecure network, such as the internet.


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



1. Log in to your Red Hat Linux server.





3. Add an exception to the iptables firewall rules that forwards incomingclient requests on port 8080 to port 8080 on the web application server.

Clients on an unsecured network outside the firewall can now access theweb application server through the firewall on port 8080.

To set up the client tier

You need to install Microsoft Office 2003 on the machine on which you runthe client tier.

1. Insert the BusinessObjects Live Office disc into the computer's DVDreader.

2. Choose your preferred language for the installation setup from the list onthe left and click Install.The Live Office Installation Wizard is displayed.

3. Follow the on-screen instructions in the Live Office Installation Wizard tocomplete the installation procedure.

4. Click Start > Programs > Microsoft Office, and select Microsoft Excel,Word, or PowerPoint to launch the application.

5. Click LiveOffice > Options > Enterprise.6. When the Options dialog box appears, enter your BusinessObjects

Enterprise credential in the following fields:• User name

• Password



7. Enter http://WEBSERVER1:8080/dswsbobje/services/session in theWebService URL and System fields.

8. Select the Enterprise authentication method from the drop-down list, clickLog On and then click OK.

Complex deployment scenario

Complex deployment overview

The following scenario illustrates an end to end scenario which combinessplit web and server tiers. The web tier contains a load balancer and clusteredweb applications clustered on two separate machines. The server tiercomprises clustered Central Management (CMS) and File Repository servers,and multiple instances of the remaining servers clustered on two separatemachines..

System layers

• Data Tier: contains databases used by the CMS and File Repositoryservers.

• Server Tier: all BusinessObjects Enterprise servers installed on twomachine running as a cluster.

• Web Tier: two web application servers installed on separate machinesrunning as a cluster with failover support through load balancer.

• Client Tier: a browser used to log into Central Management Console(CMC).


5Sample Deployment ScenariosComplex deployment scenario

Configuration details



Microsoft SQL Server 2005Database for Central Management Server (CMS)

WebLogic 10Web application server

Cisco CSS 11500 series load bal-ancer

Load balancer

Linux iptables running on Red HatLinux with two network interface cards(NIC)

Firewall

Complex deployment diagram


Web application clustering support

The Central Management Console (CMC) and InfoView web applicationscan be used in environments with a variety of different clustered, load


Sample Deployment Scenarios5 Complex deployment scenario

balanced, or fault tolerant configurations. The table below lists configurationsupport for CMC and InfoView web applications.

Fault tol-erant

Load balanceswithout sessionaffinity

Load balancerswith sessionaffinity

Clustered webapplicationservers

Web ap-plication

YesSupportedSupportedSupportedInfoView(stateless)

NoUnsupportedSupportedSupportedCMC(stateful)


The complex deployment scenario involves the following tasks in the orderlisted below.

1. Setting up the data tier2. Setting up the server tier3. Setting up the web tier4. Configuring the load balancer5. Setting up the firewall6. Setting up the client tier

Deploying the complex deployment scenario


This scenario calls for Microsoft SQL Server 2005 running on a supportedMicrosoft Windows operating system. In the examples below, this databasesystem is named DBSERVER1.

Install a version of Microsoft Windows with the appropriate service packsand updates required by Microsoft SQL Server 2005. If your CMS anddatabase servers are installed on separate computers, ensure that you havea working network connection between the machines.



1. Install Microsoft SQL Server 2005.Make note of the following settings you use during the installation. Youwill need these settings when you come to install BusinessObjectsEnterprise servers and clients.

ExampleSetting

DBSERVER1_sqlName of database server instance

saAdministrator account name



Microsoft SQL Server 2005 is now installed and ready to be used byBusinessObjects Enterprise.

2. Create or import a new database for the CMS, as well as auditing orDashboard and Analytics databases if required.Record the settings used for creating of the CMS database.


BOE120CMS database name

bobjuserUsername for CMS database access

mypasswordPassword for CMS database access

A CMS database is now available for use.

3. Create or import a new database for auditing database, if required.Record the settings used for creating of the auditing database.

ExampleAuditing database setting

bobjauditAuditing database name

audituserUsername for auditing database access

auditpasswordPassword for auditing database access

An auditing database is now available for use.



4. Create or import a new database for Dashboard and Analytics database,if required.Record the settings used for creating of the Dashboard and Analyticsdatabase.

ExampleDashboard and Analytics database setting

bobjpmDashboard and Analytics database name

pmuserUsername for PM database access

pmpasswordPassword for PM database access

A Dashboard and Analytics database is now available for use.

5. Set up a DSN database connection on the BusinessObjects EnterpriseCMS and any clients that need direct database access.On each system that needs to access the database, create a SystemDSN entry in the Microsoft "ODBC Data Source Administrator" ControlPanel tool. Enter the settings you used when you created the database(s)above.Your CMS server are now able to communicate with your newly createdMicrosoft SQL Server 2005 databases.

You have set up CMS, auditing, and performance management databases,as required. You have also installed a file repository server network-shareddirectory. The default listener port number used by SQL Server is 1433. Thedatabase port number must be entered during the BusinessObjects Enterpriseinstallation.

Verify the connectivity between your CMS and database machines byattempting to connect to your database(s) from the CMS server(s) afterinstalling BusinessObjects Enterprise.

Note:This scenario does not include a network firewall between the CMS anddatabase servers.

Remember:The ability to connect to your database server from your CMS server mayrequire a change to the Windows Firewall settings on both machines.



To set up the server tier

Windows Server 2003 SP2 Enterprise Edition has to be installed and running.You need administrative privileges on both machines that will host theBusinessObjects Enterprise servers. Designate one machine SERVER1 andthe other SERVER2.

Follow the instructions below to install all the servers on SERVER1.1. Run setup.exe from the root directory of your product distribution.








7. Select New and Use an existing database server in the "Install Type"screen. Click Next.The Server Components Configuration screen is displayed.

8. Enter password in both Password and Confirm password. Click Next..The "Server Intelligence Agent" screen is displayed.

9. Enter SIA1 in Node Name and click Next.The "CMS Database Information" screen is displayed.

10. Select SQL Server (ODBC) from the CMS database drop-down list andclick Browse.The "SQL Server Logon" screen is displayed.



11. Input your Microsoft SQL Server user credentials through thepreconfigured ODBC DSN.a. Select my company database from the list under Data Source Name.b. Enter bobjuser and paword in the Login ID and Password fields.c. Select BOE120 from the list under Database.

d. Click OK to validate and save your user credential information.The "CMS Database Information" screen is once again displayed.

12. Select Auditing Database and repeat steps 10-11 to configure usercredentials through the ODBC DSN for the auditing database. WhenODBC DSN is displayed in the "CMS Database Information" screen clickNext.The "Select Web Application Server" screen is displayed.

13. Select the Install Tomcat application server option and click Next.The "Configure Tomcat" screen is displayed

14. Do not modify any of the values in the input fields and click Next.The "Start Installation" screen is displayed.

15. Click Next to start the installation.



The installation process begins and is completed when "BusinessObjectsEnterprise has been successfully installed" is displayed.

16. Select Launch BusinessObjects Administration Console and clickFinish to exit.A new browser window opens and within a few seconds you are promptedto log into the Central Management Console (CMC).

17. Verify the connectivity between the BusinessObjects CMS and your MSSQL Server by logging onto the CMC.a. Type SERVER1 in System.b. Type Administrator in User name .c. Type password in Password.d. Click Log On to access the CMC.

Accessing the CCM home page, verifies that the BusinessObjectsEnterprise CMS is communicating with the Microsoft SQL Server 2005database server.

You must now install another set of BusinessObjects Enterprise servers onthe machine designated SERVER2.

To set up a CMS clusterWindows Server 2003 SP2 Enterprise Edition has to be installed and running.You need administrative privileges on the SERVER2 machine.

Follow the instructions below to install BusinessObjects Enterprise servercomponents which will be clustered to the CMS you installed on SERVER1.










7. Choose Custom or Expand and click Next.The "Select Features" screen is displayed.

8. Configure the screen as follows:a. Left-click on the icon beside Client Components and select Entire

feature will be unavailable.b. Left-click on the icon besideWeb Tier Components and select Entire

feature will be unavailable.c. Expand Server Components > Central Management Server.d. Left-click on the icon beside MySQL and select Entire Feature will

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

be unavailable.f. Click Next.

The "CMS Cluster" screen is displayed.

9. Select the If No...option and provide the following configuration detailsa. Type 6401 in New CMS Port.b. Type SERVER1 in Existing CMS Hostname.c. Type 6400 in Existing CMS Port.d. Type password in CMS Administrator Password and click Next.



The "Server Intelligence Agent" screen is displayed.

10. Type SIA2 in Node Name and 6415 in Port. Click Next.The "CMS Database Information" screen is displayed.

11. Select SQL Server (ODBC) from the CMS database drop-down list andclick Browse.The "SQL Server Logon" screen is displayed.

12. Input your Microsoft SQL Server user credentials through thepreconfigured ODBC DSN.a. Select my company database from the list under Data Source Name.b. Enter bobjuser and paword in the Login ID and Password fields.c. Select BOE120 from the list under Database.



d. Click OK to validate and save your user credential information.The "CMS Database Information" screen is once again displayed.

13. Select Auditing Database and repeat steps 10-11 to setup configureuser credentials through the ODBC DSN for the auditing database. WhenODBC DSN is displayed in the "CMS Database Information" screen clickNext.The "Start Installation" screen is displayed.



To cluster File Repository serversYou need to create a Filestore folder on SERVER1 in the followingdirectory: C:\Program Files\Business Objects\BusinessObjectsEnterprise 12.0\FileRep. This folder will store data for the FileRepository servers installed on SERVER1 and SERVER2. The folder mustcontain two subfolders: Input and Output. You have to enable sharing forthe Filestore folder and set Full, Change, and Read permissions for Ev



eryone. Name the shared folder FileRep. You must be logged into the CentralManagement Console on SERVER1 for the procedure below.

To complete the server tier setup, you must cluster all the File Repositoryservers.


2. Double-click the SIA1.InputFileRepository entry.The SIA1.InputFileRepository properties are displayed.

3. Replace the current value in the FileStore Directory field by typingC:\Program Files\Business Objects\BusinessObjectsEnterprise 12.0\FileRep\Input\ .

4. Click Save.5. Repeat steps 2-3 for the servers listed in the following table and provide

the specific configuration for each server.

FileStore Directory settingServer name

\\Server1\FileRep\Input\SIA2.InputFil-eRepository

C:\Program Files\Business Objects\BusinessObjectsEnterprise 12.0\FileRep\Output\

SIA1.OutputFil-eRepository

\\Server1\FileRep\Output\SIA2.OutputFil-eRepository

The server tier setup is now complete. You should now set up the web tier.

To assign static port values to serversAccess the Central Management Console (CMC) on the machine namedSERVER1. Use the machine you designated to run the client tier, and opena browser and type in the following URL: http://SERVER1:8080/CmcApp/App/.

You need to assign static port values to the following servers:



Server name

SIA1.CentralManagementServer

SIA1.InputFileRepository

SAI1.OutputFileRepository

1. Type the following configuration information and click Log On.

Required configuration informationField

SERVER1System

AdministratorUser Name

BOBJ_adminPassword

EnterpriseAuthentication Type

The CMC Home page is displayed.


3. Double-click the SIA1.CentralManagementServer entry.The SIA1.CentralManagementServer properties are displayed.

4. Deselect Auto assign and type 6402 in Request Port under "CommonSettings".

5. Click Save & Close.The list of available servers is displayed again.

6. Repeat steps 3-5 for the following servers:

Port number to specifyServer name

6404SIA1.InputFileRepository

6406SIA1.OutputFileRepository

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



To prepare your web application servers

Before setting up the BusinessObjects Enterprise web tier you need to installand prepare your web application servers. For this scenario you require twomachines running on Windows Server 2003 SP2 Enterprise Edition.Designate one machine managedserver1 and the other managedserver2.1. Install WebLogic 10 on both managedserver1 and managedserver2 .

For more information consult your WebLogic 10 documentation.

2. Configure the WebLogic 10 server names on each machine according tothe machine name.The server on managedserver1 is called “managedserver1”, and theserver on managedserver2 is called “managedserver2”.

3. Create a cluster on the machine running “managedserver1” with thefollowing settings

ValueSetting

cluster1Cluster name

AdminServerAdministration server

managedserver1

managedserver2

Managed servers

8001AdminServer listen port

7001managedserver1 listen port

7001managedserver2 listen port

weblogicUsername for AdminServer

passwordPassword for AdminServer

For more information on how to create a cluster on WebLogic see yourWebLogic 10 documentation.

4. Create a WebLogic XML Registry for each server using the followingentries:



ValueProperty

BusinessObjectsName

weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl

DocumentBuilder Facto-ry

weblogic.apache.xerces.jaxp.SAXParserFactoryImpl

SAX Parser Factory

weblogic.apache.xalan.processor.TransformerFactoryImpl

Transformer Factory

For more information on WebLogic XML registries see your WebLogic10 documentation.

You can now proceed to install the web applications and setup theBusinessObjects Enterprise web tier.

To install the web applicationsUse the following steps to install the web applications to the“managedserver1” machine.




3. ClickNext in the "Welcome to the BusinessObjects Enterprise InstallationWizard" . .The "License Agreement" screen is displayed.






7. Choose Web Tier and click Next .The "Select Features" screen is displayed.

8. Expand Web Tier Components.9. Left-click on the icon beside Tomcat and select Entire Feature will be

unavailable. Click Next.The "CMS Clustering" screen is displayed.

10. Enter the requested information for the CMS on SERVER1 in the fieldsprovided and click Next.

Type SERVER1, 6400, and password. C

The "Select Web Application Server" screen is displayed.

11. Choose WebLogic 10 from list of supported web application servers.



12. Select I will manually deploy web components at a later time and clickNext.The "Start Installation" screen is displayed.



The WAR files used to deploy the web applications have to be preparedbefore you can deploy them to your WebLogic 10 cluster.

To prepare the WAR files for deploymentYou need to prepare the WAR files in the BusinessObjects Enterpriseinstallation on managedserver1 so that they can be deployed on WebLogic.1. Open the weblogic.xml file which is located in the following directory:

C:\Program Files\Business Objects\deployment\templates\



2. Type in the following information after the <weblogic-web-app> tag:

<session-descriptor><session-param>

<param-name>PersistentStoreType</param-name>

<param-value>replicated</param-value></session-param>

</session-descriptor>

3. Save and close the weblogic.xml file.4. Open the config.weblogic10 file which is located in:

C:\Program Files\Business Objects\deployment\.

5. Modify the file to read as follows:

as_domain_dir=c:\bea\user_projects\domains\base_domainas_instance=AdminServeras_admin_port=8001as_admin_username=weblogicas_admin_password=password

6. Save and close the config.weblogic10 file.7. Open a command-line console and run the following command:

C:\Program Files\Business Objects\deployment>wdeploy.bat weblogic10 predeployall

The WAR file have been prepared for deployment and are located in thefollowing directory:

C:\Program Files\BusinessObjects\deployment\workdir\weblogic10\application\.

You can now deploy the WAR files using the WebLogic AdministrationConsole.

To deploy the WAR files to WebLogic 10You need to log on to the WebLogic Server Administration console.

Once the WAR files have been prepared for deployment, you can use theWebLogic 10 Administration console to deploy the web applications.

1. Click Deployments under "Domain Structure".The "Summary of Deployments" is displayed on the right.



2. Click Install under the Control tab.The "Install Application Assistant" is displayed.

3. Click Lock & Edit under "Change Center".4. In the Location area navigate to the following folder:

C:\Program Files\BusinessObjects\deployment\workdir\weblogic10\application\.

5. Select InfoViewApp.war and click Next.6. ClickNext in the screen that displays to accept the selected default setting

Install this deployment as an application."Select deployment targets" is displayed.

7. Under "Clusters" select cluster1 and All servers in the cluster. ClickNext."Optional settings" is displayed.

8. Click Finish to accept all the defaults settings.The "Install Application Assistant" is closed.

9. Click Activate Changes under "Change Center".10. Repeat steps 1-8 for all the files in the C:\Program Files\Business

Objects\deployment\workdir\weblogic10\application\directory.All the files to be deployed are listed in "Summary of Deployments "underthe Control tab.

11. Select all the files under the Control tab.12. ClickStart > Servicing all requests.

The files are deployed and ready to run.

To set up the hardware load balancer

This section illustrates the configuration of a Cisco CSS 11500 series loadbalancer for use with two clustered WebLogic web application servers.Advanced administrative knowledge of Cisco load balancer products isrequired. The load balancer must be configured to use persistent (sticky)sessions.



The load balancer provides content switching for incoming external clientrequests to the web application servers in the web tier.1. Create a VLAN circuit IP address. This will allow administrators to connect

to the load balancer remotely.Below, a VLAN circuit named VLAN189 is created with an IP address of10.50.96.78.

CSS11503#configCSS11503(config)#circuit VLAN189CSS11503(config−circuit[VLAN189])#ip address10.50.96.78 255.255.252.0CSS11503(config−circuit−ip[VLAN189−10.50.96.78])#exitCSS11503(config−circuit[VLAN189])#exitCSS11503(config)# exitCSS11503#

2. Configure the IP address and the port number to be used for incomingweb requests. Web clients will sent web requests to load balancer at thisaddress and port number.Below, a virtual, load balanced server named arrowpoint-weblogic at10.50.96.79 port 7001 is created. To a web client, arrowpoint-weblogicwill appear to be a single WebLogic server.

CSS11503# configureCSS11503(config)# owner transCreate owner <trans>, [y/n]:yCSS11503(config-owner[trans])# content arrowpoint-weblogicCreate content <arrowpoint-weblogic>, [y/n]:yCSS11503(config-owner-content[trans-arrowpoint-weblogic])# vip address 10.50.96.79CSS11503(config-owner-content[trans-arrowpoint-weblogic])# protocol tcpCSS11503(config-owner-content[trans-arrowpoint-weblogic])# port 7001

3. Create a service for each WebLogic server in the cluster, entering theservice name, IP address, and other connection information. The loadbalancer will distribute requests received from web clients among theseservers.



Below, services are created for each WebLogic server:LB01-ARROWPOINT at 10.50.96.76, and LB02-ARROWPOINT at10.50.96.77.

CSS11503# configureCSS11503(config)# service <LB01-ARROWPOINT>Create service LB01-ARROWPOINT, [y/n]:yCSS11503(config-service[LB01-ARROWPOINT])# ip address10.50.96.76CSS11503(config-service[LB01-ARROWPOINT])# string LB01CSS11503(config-service[LB01-ARROWPOINT])# keepalivetype tcpCSS11503(config-service[LB01-ARROWPOINT])# keepaliveport 7001CSS11503(config-service[LB01-ARROWPOINT])# activeCSS11503(config-service[LB01-ARROWPOINT])# exitCSS11503(config)# exitCSS11503#

CSS11503# configureCSS11503(config)# service <LB02-ARROWPOINT>Create service LB02-ARROWPOINT, [y/n]:yCSS11503(config-service[LB02-ARROWPOINT])# ip address10.50.96.77CSS11503(config-service[LB02-ARROWPOINT])# string LB02CSS11503(config-service[LB02-ARROWPOINT])# keepalivetype tcpCSS11503(config-service[LB02-ARROWPOINT])# keepaliveport 7001CSS11503(config-service[LB02-ARROWPOINT])# activeCSS11503(config-service[LB02-ARROWPOINT])# exitCSS11503(config)# exitCSS11503#

4. Add each of the WebLogic services to the load balancer. Requestsreceived by the load balancer will then be distributed between each ofthe services.Below, LB01-ARROWPOINT and LB02-ARROWPOINT are added to theload balancer as services.

CSS11503(config-owner-content[trans-arrowpoint-weblogic])# add service LB01-ARROWPOINTCSS11503(config-owner-content[trans-arrowpoint-weblogic])# add service LB02-ARROWPOINT



5. Configure session persistence, so that requests can be managed by allWebLogic servers in the cluster.Below, session persistence is activated.

CSS11503(config-owner-content[trans-arrowpoint-weblogic])# advanced-balance arrowpoint-cookieCSS11503(config-owner-content[trans-arrowpoint-weblogic])# activeCSS11503(config-owner-content[trans-arrowpoint-weblogic])# exitCSS11503(config-owner[trans])# exitCSS11503(config)#

The load balancer is now configured to accept requests from web clients asvirtual server arrowpoint-weblogic at 10.50.96.79 port 7001. Thearrowpoint-weblogic virtual server distributes the requests between WebLogicservers configured as services LB01-ARROWPOINT at 10.50.96.76 port7001 and LB02-ARROWPOINT at 10.50.96.77 port 7001.

!Generated on 10/02/2007 13:09:44!Active version: sg0730005

configure

!*************************** GLOBAL**************************ip route 0.0.0.0 0.0.0.0 10.50.96.1 1

!************************* INTERFACE*************************interface e9trunkvlan 189

!************************** CIRCUIT**************************circuit VLAN189ip address 10.50.96.78 255.255.252.0

!************************** SERVICE**************************service LB01-ARROWPOINTip address 10.50.96.76string LB01keepalive type tcpkeepalive port 7001active



service LB02-ARROWPOINTip address 10.50.96.77string LB02keepalive type tcpkeepalive port 7001active

!*************************** OWNER***************************owner trans

content arrowpoint-weblogicvip address 10.50.96.79advanced-balance arrowpoint-cookieprotocol tcpport 7001add service LB01-ARROWPOINTadd service LB02-ARROWPOINTactive

!*************************** GROUP***************************group transadd destination service LB01-ARROWPOINTadd destination service LB02-ARROWPOINTvip address 10.50.96.79active


The iptables firewall is running on a supported Red Hat Linux operatingsystem with two network interface cards (NIC). One network card (interfaceeth0) is connected to an internal secure network with a hardware loadbalancer , the other (interface eth1) is connected to an external unsecurenetwork, such as the internet.


The following steps illustrate how to forward requests from clients on anunsecure external (interface eth1) network to port 7001 on a hardware loadbalancer running on a secure, firewalled network (interface eth0).1. Log in to your Red Hat Linux server.







3. Add an exception to the iptables firewall rules that forwards incomingclient requests on port 7001 to port 7001 on the Cisco CSS 11500 serieshardware load balancer.

Clients on an unsecured network outside the firewall can now access theclustered WebLogic web application servers tier through the firewall on port7001.

To set up a client tier

To set up the client tier in this scenario all you need is a machine running onWindows Server 2003 SP2 Enterprise Edition and a web browser.

1. Open your web browser2. Access the cluster by entering the following

URL:http://10.50.96.79:7001/InfoViewApp/The "Log On to InfoView" page appears.

3. Type SERVER1 for System; Administrator forUser name; and passwordfor Password.



4. Click Log On.The "InfoView" home page is displayed.



You have successfully completed the scenario.



Appendix

6

Reference for wdeployThe wdeploy command-line deployment tool has many properties, options,and actions. This guide shows how to use wdeploy for administrators whowant to take advantage of some wdeploy's advanced features. Documentationis also available as a README.txt file in the deployment directory on aBusinessObjects Enterprise server.

Configuration Information

There are two types of configuration file used by wdeploy.

1. Server command-line parameter files

Each supported web or web application server has its own parameterfile, from which the wdeploy tool reads default parameter values for eachweb application server. Configuring a parameter in this file means that itmust no longer be given on the command-line when calling wdeploy. Anydefault values stored in this file are overridden when the same parameteris given on the command-line, so the parameter file does not need to bechanged for different commands. The server parameter files can be foundas:

<BOE_INSTALL_DIR>\deployment\config.<WEB_APP_SERVER>

Replace <WEB_APP_SERVER> with the name of the web applicationserver.

2. Web application properties files

Each web application has its own properties file, which wdeploy uses todetermine the name of the web application archive, directory, and otherinformation, when deploying the web application to a web applicationserver. The web application properties files can be found as:

<BOE_INSTALL_DIR>\deployment\apps\<WEB_APPLICATION>.properties

Replace <WEB_APPLICATION> with the name of the web applicationto be deployed.


Appendix6 Reference for wdeploy

The wdeploy configuration file

The wdeploy configuration file contains web or web application server-specificsettings saved in a key-value pair text format. Read by wdeploy when itstarts, options and parameters saved in the configuration file are used asdefault settings and no longer need to be given on the command-line.However, all options and parameters can still be given on the command-line,which overrides the configuration file.

As each web application server requires different wdeploy settings, there isone configuration file for each supported web or web application server inthe format:

<BOE_INSTALL_DIR>\deployment\config.<WEB_APP_SERVER>

Substitute the <WEB_APP_SERVER> suffix for the name of your webapplication server. The suffix must be the same web application server nameused as the second parameter in the wdeploy command-line syntax.

Valid configuration file names are:

• config.jboss4 (JBoss 4.2.3)• config.oas1013 (Oracle Application Server 10g R3)• config.sapappsvr7 (SAP NetWeaver AS Java 7.0)• config.sapappsvr73 (SAP NetWeaver AS Java 7.3)• config.tomcat55• config.tomcat7• config.weblogic10 (WebLogic 10 and WebLogic 10.3)• config.weblogic11 (WebLogic 10.3.3 (11gR1))• config.websphere6• config.websphere7

When deploying web applications to a dedicated web server in splitdeployments, use the name of the supported web server:

• config.apache (Apache Web Server or IBM IHS)

Note:It is recommended that web application server administrator accountpasswords are not stored in the wdeploy configuration file, but rather passed


6AppendixReference for wdeploy

to wdeploy from the command-line with the parameter -Das_admin_password=<PASSWORD>.

The following tables list the wdeploy configuration file options and parametersrequired for each supported web application server.

Web application .properties files

The properties files stored as <BOE_INSTALL_DIR>\deployment\apps\<WEB_APPLICATION>.properties are pre-configured bythe BusinessObjects Enterprise setup program. Use the table below to addor change properties when deploying to a complex environment.

Table 6-1: wdeploy properties

DescriptionStatusParameter

Path to append to the web ap-plication server's JavaCLASSPATH environmentvariable.

Optionaladdtoclasspath

Path to append to the web ap-plication server's Java LIBPATH environment variable.

Optionaladdtolibpath

Boolean value to indicatewhether or not the web appli-cation is deployed as a file tree(expanded WAR). False bydefault.

Optionalapp_as_a_filetree

Path to the folder that containsthe web application's sourcecode.

Optionalapp_source_dir

Path to the parent of the folderthat contains the web applica-tion's source code.

Optionalapp_source_tree

Web application context root.Mandatoryappvdir




Name of the supplemental AntXML build file containing addi-tional configuration proceduresfor the web application. The.xml build file is in the samedirectory as the web applica-tion .properties file.

Optionalbuildfile

Boolean value to indicatewhether or not the web appli-cation supports static and dy-namic content separation.When "true" in split mode,static content is separated forthe web server and static plusdynamic content are distribut-ed in the web applicationserver. On WebSphere 6.1web application server,[FileServingServlet]is enabled. False by default.

Optionaldont_split_content

Boolean value to indicatewhether or not the web appli-cation contains more than65,535 files, as this may causethe web application server toreach the maximum numberof open files. False by default.

For WebSphere 6.1file_limit_reached




Name of the folder that con-tains the web application WARor EAR files.

The default directory is<BOE_INSTALL_DIR>\BusinessOb-jects Enterprise12.0\java\applica-tions.

This parameter is mandatorywhen wdeploy is launchedfrom a folder other than thedefault.

Optionalwar_dir

Name of the web applicationWAR or EAR file. This param-eter is mandatory ifapp_source_dir orwin_app_source_dir arenot defined. The WAR or EARfiles are located in war_diror win_war_dir.

Mandatorywarfile

Number of properties to set inthe target application server.The default value is 0.

Optionalwdeploy.prop.count

Name of the property to set onthe target application server.. "#" corresponds to thewdeploy.prop.count val-ue. See infoview.properties.

Optionalwdeploy.prop#.name




Value of the property to set onthe target application server."#" corresponds to the wdeploy.prop.count value.See infoview.properties.

Optionalwdeploy.prop#.value

A list of supported platformsthat supports the prop#property. "#" corresponds tothe wdeploy.prop.countvalue.

Supported platforms are: so-laris_sparc, aix_rs6000,hpux_pa-risc, linux_x86 andwin32_x86. The list is sepa-rated by spaces. By defaultthe list is empty that corre-sponds to all the platforms.When the platform that holdsthe application server is notin the list, the property is notset in the application server'sconfiguration. See[styles.properties]file.

Optionalwdeploy.prop#.applies_to

See win_war_dir andapp_source_dir.Optionalwin_app_source_dir

Name of the folder that con-tains the web application WARor EAR files on Windows sys-tems. win_war_dir takesprecedence over the value ofwar_dir.

Optionalwin_war_dir




Name of the static resourcefile for the application presentin war_dir.

Optionalzipfile

wdeploy parameters

Table 6-2: Parameters for wdeploy

Example valueDescriptionParameter

InfoViewApp

Name of the web applicationto deploy, as found in theWAR or EAR file name andthe web application propertiesfile:

<BOE_INSTALL_DIR>\deployment\apps\<WEB_APP>.properties

APP

false (default)

true

For web application serversthat use SSL encryption duringweb application deployment,such as Oracle ApplicationServer or Sun Java Applica-tion Server.

Note:Setting this value to true indi-cates requires that you alsogive an administrator ac-count name and password.

as_admin_is_secure




password

Mandatory for NetWeaver,Oracle Application Server, SunJava application server, andWebLogic.

Web application server ad-ministrative account pass-word.

as_admin_password

8080


Port number for web applica-tion server administrativeaccess.• For WebSphere, the

SOAP port. If not set, thedefault SOAP port will beused.

• For Oracle ApplicationServer (oas1013): wde-ploy expects the requestport of the <notification-server> elementin the file opmn.xml.

as_admin_port

administrator


Web application server ad-ministrative account user-name.

as_admin_username




oracleas.mycompany.com

For Oracle Application Server.

The name of the target appli-cation server.

as_appserver_name

C:\tomcat55

Installation directory of theweb application server.

For WebLogic applicationservers, as_domain_dir isthe domain root.

as_domain_dir

Default_group

For Oracle Application Server.

The server group to whichthe target web applicationserver belongs.

as_group_id

localhost

Mandatory for all the applica-tion servers.

Name of the web applicationserver instance.

as_instance

standalone

split

Type of web application de-ployment.

A standalone is a web appli-cation server that servesboth static and dynamic webcontent. A split deploymentuses a dedicated web serverto serve static content, anda web application server toserve dynamic content.

as_mode




HKLM\SOFTWARE\ApacheSoftware Foundation\Procrun2.0\<AS_SERVICE_NAME>\Parameters\Java

For Tomcat running on Win-dows.

When installed as a service,the name of the Windowsregistry key where the JVMstartup parameters arestored.

as_service_key


When installed as a service,the value of Windows reg-istry key where the JVMstartup parameters arestored.

as_service_key_value

Tomcat55


The name of the Tomcatservice.

as_service_name

AS1Mandatory for NetWeaver.The system id of the target in-stance.

as_sid

8880

Mandatory for WebSphere.Port number for SOAP applica-tion server administration. Ifnot set, the default SOAP portnumber will be used.

as_soap_port

default_host

For WebSphere only.

Virtual host to which the ap-plication must be bound.

as_virtual_host




classloader_package_filtering=com.ctc.wstx.*,javax.xml.*,org.apache.*

For WebLogic 10.

When the property is set, theapplication is turned into anEAR, and a filtering Classloader is setup with thepackage list. This parameteris a coma-separated list ofpackages to filter from theclassloader.

classloader_package_filtering

<WS_DIR>/opii.conf

For Sun Java System WebServer.

Name of the configurationfile holding the Oracle Appli-cation Server connectorconfiguration.

connector_conf_file

www.mycompany.com

For split deployments usingOracle Application Server.

The host name of the webapplication server to contact.

connector_host

passthrough

For Sun Java System WebServer only.

The name of the object thatdescribes the connector ser-vice to the application server,in the configurationfileobj.conf.

connector_name

7002

For split deployments usingOracle Application Server.

The ajp13 port number.connector_port




tomcat55

For web servers running insplit mode, such as Apache,Oracle HTTP Server, or SunJava System Web Server.

The type of connector toconfigure for split deploy-ments.

connector_type

false (default)

true

For WebLogic web applicationservers.

Indicates whether the appli-cation must be deployed asa file tree (expanded format)or as a packaged WAR orEAR file.

deploy_as_a_filetree

C:\apache2\htdocs

Directory under which wdeploycreates a subdirectory forstatic content served by adedicated web server. Thisname must match the webapplication name, and thename of the .zip archive thatcontains the application's stat-ic resources.

wdeploy creates a virtual di-rectory on the web server,mapping the subdirectory tothe URL.

deployment_dir




false (default)

true

Tells wdeploy whether or notthe web application containsmore than 65,535 files.

Set to false by default, ex-cept for Sun Java SystemApplication Server andWebSphere 6.

enforce_file_limit

<BOE_INSTALL_DIR>\deployment\workdir

Directory in which wdeploymanipulates the web applica-tions (typically when it splitsthe static and dynamic contentof an application), stores theresults of the pre-deploy ac-tion, and stores data to beable to undeploy applications.

work_dir

C:\apache2

For web servers running insplit mode, such as Apache,Oracle HTTP Server, or SunJava System Web Server.

The web server home direc-tory.

ws_dir

webserver1

For WebSphere 6 only.

The name of the web serverwhere the application is in-stalled, in split mode.

ws_instance




apache

For web servers running insplit mode, such -as Apache,Oracle HTTP Server, or SunJava System Web Server.

The name of the web server,as found to the <BOE_INSTALL_DIR>\deployment\config.<WEB_SERVER> file.

Note:Apache, Oracle HTTP Serv-er, and Sun Java SystemWeb Server, all have aws_type of apache.

ws_type

Mandatory parameters

Parameters are required for some deployment configurations. For example:• Split deployments (separate web and web application servers) must have

the -Das_mode=split parameter given on the command-line or set inthe server configuration file.

• Split deployments where the web server runs on the same system as theweb application server must use the -Dws_type=<WEB_SERVER_TYPE>and -Dws_dir=<WEB_SERVER_DIR> parameters on the command-lineor set in the configuration file.

• Split deployments must have the -Dconnector_type=<CONNECTOR_TYPE> parameter given on the command-line or set in the serverconfiguration file.

The following list of parameters can be given on the command-line or savedin the server configuration file config.<WEB_APP_SERVER>.



wdeploy actions

The last parameter of a wdeploy command is the action to be performed.The following section defines each valid action, and what each does.

Table 6-3: wdeploy Actions

DescriptionAction

The wdeploy predeploy command prepares a web application fordeployment to the target web application server.

The web application's web.xml configuration file is updated, alongwith any other changes required to make the web application deployable to the target web application server.

Once configured, the web application is packaged into a WAR orEAR file and saved to <BOE_INSTALL_DIR>\deployment\workdir\<WEB_APP_SERVER>.

This file can be deployed manually through the web applicationserver's administrative console, or with the wdeploy deploycommand.

Use wdeploy predeploy to prepare the InfoViewApp web application so that it is ready for deployment to a specific web applicationserver.

wdeploy.bat <WEB_APP_SERVER>-DAPP=InfoViewApppredeploy

Substitute <WEB_APP_SERVER> for the name of the web applicationserver.

predeploy



DescriptionAction

The wdeploy predeployall command performs the wdeploypredeploy command for all web applications located in the Busi-nessObjects Enterprise web application source directory:

<BOE_INSTALL_DIR>\warfiles\webapps

Use wdeploy predeployall to apply the wdeploy predeploycommand to all web applications.

wdeploy.bat <WEB_APP_SERVER> predeployall


predeployall

The wdeploy deploy command is a concatenation of the wdeploypredeploy andwdeploy deployonly commands, which preparesand deploys a web application to the target web application server withjust one command.

Use wdeploy deploy to prepare and deploy the InfoView webapplication to the target web application server.

wdeploy.bat <WEB_APP_SERVER>-DAPP=InfoViewAppdeploy

Use wdeploy deploy to prepare and deploy the InfoView webapplication to the target web application server.

wdeploy.bat <WEB_APP_SERVER>-DAPP=InfoViewAppdeploy


deploy



DescriptionAction

The wdeploy deployall command performs the wdeploy de-ploy command for all web applications located in the BusinessOb-jects Enterprise web application source directory:

<BOE_INSTALL_DIR>\warfiles\webapps

Use wdeploy deployall to apply the wdeploy deploy com-mand to all web applications.

wdeploy.bat <WEB_APP_SERVER> deployall


deployall

The wdeploy deployonly command deploys a prepared webapplication to the target web application server.

Deployable WAR or EAR files located in <BOE_INSTALL_DIR>\deployment\workdir\<WEB_APP_SERVER> are deployed to theweb application server by the wdeploy predeploy command invoking the web application server's command-line interface.

If a web application has not already been prepared for deployment,the wdeploy predeploy command will be called automatically.

Use wdeploy deployonly to deploy a prepared InfoViewAppweb application to a web application server.

wdeploy.bat <WEB_APP_SERVER>-DAPP=InfoViewAppdeployonly


deployonly



DescriptionAction

Use wdeploy deployonlyall to apply the wdeploy deploy-only command to all prepared web applications.

wdeploy.bat <WEB_APP_SERVER> deployonlyall


deployonlyall

Lists all the available, installed applications described in the$BOE_INSTALL_DIR\deployment\apps directory.

Example: wdeploy[.sh|.bat] tomcat55 listapps

Lists all available applications.

listapps

listappsall

The wdeploy undeploy command invokes the target web appli-cation server's command-line interface to remove a deployed Busi-nessObjects Enterprise web application from the server.

Use the wdeploy undeploy command to undeploy the In-foViewApp web application from the target web application server.

wdeploy.bat <WEB_APP_SERVER>-DAPP=InfoViewAppundeploy


undeploy

The wdeploy undeployall command performs the wdeployundeploy command for all BusinessObjects Enterprise web appli-cations deployed to the target web application server.

undeployall



DescriptionAction

Validates the wdeploy configuration for the supported web applica-tion servers to ensure that the deployment can be successful.

Example: wdeploy [.sh|.bat] tomcat55 validateconfig

Checks the as_dir and as_instance values.

validateconfig

Web application updates made by wdeploy

Table 6-4: Changes made to web application configuration by wdeploy

Description of updatesWeb application server

For each application, ${ws_dir}/conf/bobj.${APP}.conffile is created, containing connector configuration, directory andservlet mapping information. File${ws_dir}/conf/httpd.conf is modified to include that file.

Apache web server

Files added to the classpath are dropped in${as_dir}/shared/lib

${as_dir}/bin/bobjeEnv.${APP}.[sh|bat] file is created, containing library path modifications, and java propertiesmodifications to add the application's properties.

${as_dir}/bin/catalina.[sh|bat] file is modified toinclude this file.

On Windows, additionnal java properties are added to thetomcat service startup parameters. Library path modificationsmust manually be made to the system-wide PATH environmentvariable

Restart Tomcat to take changes into account.

Tomcat




The JSF package shipped with JBoss is deleted if it is detected(directory ${as_dir}/server/${as_instance}/deploy/jbossweb-tomcat55.sar/jsf-libs is deleted)

Files added to the classpath are dropped in${as_dir}/server/${as_instance}/lib.

File ${as_dir}/bin/bobjeEnv.${APP}.[sh|bat] iscreated, containing library path modifications, and java properties modifications to add the application's properties. File${as_dir}/bin/run.[sh|bat] is modified to include thisfile.

Restart JBoss to take changes into account.

JBoss

Files to add to the classpath are bundled in the application(added to WEB-INF/lib). Additionnal library path and applicationproperties modifications are not supported yet.

Such modifications must be done manually using NetWeaver'sconfiguration interface.

NetWeaver

Files to add to the classpath are bundled in the application(added to WEB-INF/lib).

Library path and application specific properties are set into${as_dir}/opmn/conf/opmn.xml.

Restart your application server to take changes into account.

Oracle




Properties are added as JVM options. Library path modificationsare done modifying JVM's native library path suffix. The java.policy file is modified to add some permissions as:

"grant {permission java.util.PropertyPermission "*","read,write";permission java.lang.RuntimePermission "createClassLoader";permission java.lang.RuntimePermission "getClassLoader";permission java.lang.RuntimePermission "shutdownHooks";permission java.io.FilePermission "<businessobjects installation directory>","read,write,execute";permission java.net.SocketPermission "*","connect,listen,accept,resolve"; };"

Sun Java System Applica-tion Server

For each application, ${ws_dir}/obj.conf file is modified, toadd connector configuration, directory and servlet mapping infor-mation.

NameTrans fn=pfx2dir from="${appvdir}"dir="${deployment_dir}/${APP}"

Sun Java System WebServer


${as_domain_dir}/bin/bobjeEnv.${APP}.[sh|cmd]fileis created, containing library path and java properties modifica-tions.

${as_domain_dir}/bin/startWebLogic.[sh|cmd] fileis modified to include this file.

WebLogic





Properties are added as JVM custom properties. Library pathmodifications are done modifying the environment of the JVM.Web Server plugin gets automatically regenerated. The wdeploytool also disables the WebSphere JSF implementation.

WebSphere

Troubleshooting wdeploy

WASX7017E: Exception deploying in WebSphere

If you receive the following exception:

WASX7017E: Exception "workdir/websphere/application/install.scr"; exception information:

com.ibm.websphere.management.exception.ConfigServiceException

com.ibm.websphere.management.exception.ConnectorException

org.apache.soap.SOAPException: [SOAPException: faultCode=SOAP-ENV:Client;

msg=Read timed out; targetException=java.net.SocketTimeoutException: Read timed out]

Try raising or removing the SOAP connection timeout set by the property:

com.ibm.SOAP.requestTimeout=0

in:

$WS_INSTALL_DIR/profiles/<profile>/properties/soap.client.props file,


6AppendixTroubleshooting wdeploy

and in:

$WS_INSTALL_DIR/profiles/<profile>/temp/soap.client.props.

Apache or Sun Java SystemWeb server/Oracle 10GR3 application server split deployment

To launch Infoview portal configure the module mod_oc4j in static mode toperform Static Routing.

Add to mod_oc4j.conf file the following entry: Oc4jRoutingModeStatic.

Web application not removed from server

If a web application was not removed with the wdeploy undeploy orundeployall comamands, use the administrative console to stop all webapplications and restart the server, then re-run the undeploy or undeployall command.

Known issues

Java fails to run in an IPv6 solo environment

If you run a Java program on HPUX_IA64 in an IPv6 solo environment, youmay receive this message: “failed to log on with token”. If this occurs, youmust add the following to the list of program arguments: -jvmArgsDjava.net.preferIPv4Stack=false


Appendix6 Known issues

Known web application server issues

Web application deployment in a clustered environment

The deployment of web applications to clustered web application servers iscurrently not supported by the wdeploy tool. Web applications must bedeployed manually on clustered web application servers.

Web Services with separate web and web application servers

If you have deployed Web Services to separate HTTP and web applicationservers, you may encounter a NullPointer exception when launching a webservices URL.

The deployment to separate web and web application servers is currentlynot supported for Web Services.

Fail-over is not supported for the Central Management Console(CMC) in a clustered environment

Clustered Java application servers can be configured to work in fault tolerantmode (the session gets serialized to a state server or replicated acrossmultiple application servers in a clustered environment), or in high availabilitymode (the session is not saved). In fault tolerant mode, if one of theapplication servers crashed, then the request will be processed on anotherapplication server within the cluster; the session will be restored from thestate server or from the data that has been cached in memory.

• For BusinessObjects Enterprise XI 3.1, only InfoView supports faulttolerant mode.

• For BusinessObjects Enterprise XI 3.1, both the CMC and InfoViewsupport non-fault tolerant (high-availability) mode.

Conclusion: both the CMC and InfoView are supported in a clustered javaapplication server environment. However, only InfoView is supported in faulttolerant mode (which requires session serialization), and both the CMC andInfoview are supported in non-fault tolerant (high availability) mode.


6AppendixKnown issues

Furthermore, please ensure that your load balancer supports and providessession affinity.

Note:Session state replication in a clustered application server environment issupported for InfoView and is not supported for the CMC.

Using wdeploy in a pure IPv6 environment

Using the wdeploy command in a pure IPv6 environment with the Sun JavaDevelopment Kit (JDK), the Sun JDK may not allow the web applicationserver to bind with an IPv6 address, causing wdeploy commands to fail.

This is because the Sun JDK defaults to use IPv4 addresses. Change theSun JDK settings so that Java uses IPv6 addresses by setting the JAVA_OPTIONS variable in your environment or start-up script:

JAVA_OPTIONS="-Djava.net.preferIPv6Addresses=true"

For example, on a WebLogic web application server, add JAVA_OPTIONS="-Djava.net.preferIPv6Addresses=true" to the setDomainEnv.shor setDomainEnv.cmd scripts.

Restart your web application server, and verify connectivity with the ::1 orlocalhost alias in the hosts file.

Oracle Application Server

Deployment to Oracle 10g with separate web and web application serversWhen using a separate web and web application server to deploy webapplications to Oracle 10g R3 Application Server, an HTTP 404 error (filenot found) may be displayed when launching InfoView, the CentralManagement Console (CMC), or other web applications.

To work around this issue, edit mod_oc4j.conf and append the followingline:

Oc4jRoutingMode Static



Restart Oracle 10g R3 Application Server and the Oracle 10g R3 HTTPServer.

SAP NetWeaver AS Java

Timeout deploying to SAP NetWeaver AS Java 7.3Using the wdeploy deployall command to deploy web applications toSAP NetWeaver AS Java 7.3 may fail with a timeout exception message ifthe MaxDB database log volume reaches capacity.

To work around this problem, add another volume to the MaxDB log:

1. Install and launch the SAP MaxDB Database Manager.2. Click Register Instance.3. Enter the hostname or IP address of the SAP NetWeaver AS Java 7.3

web application server into the "Database Server" field.4. Press Add Server button followed by OK.5. Navigate to the left and click on the name or IP address just entered.6. Enter a username and password. The control user account is used by

default. Press OK.7. Select Configuration > Volumes and right-click on the "LOG" tab.8. Right click each volume and select New Volume (with size 6 GB) to

create another volumes for each log.9. When the log files all have new volumes, restart the deployment with the

wdeploy command-line tool.

Deployment to SAP NetWeaver AS Java 7.0 or 7.3 with separate web and webapplication servers

The wdeploy tool does not support deployment onto SAP NetWeaver ASJava 7.0 or 7.3 when using separate web and web application servers.

SAP NetWeaver AS Java 7.0 with language packsWhen using SAP NetWeaver AS Java 7.0 with more than two languagepacks installed, the deployment of web applications make take a long time,and eventually fail. To work around this problem:• Allocate a minimum of 2 GB of data space for MaxDB (the SAP NetWeaver

AS Java 7.0 database).• Add more data volumes to MaxDB.



• Copy the deployment folder to a location closer to the drive volume rootdirecotry (C:\ in Windows, or / in Unix).

• Switch to Java 1.5 for the duration of the deployment.

Second deployment to SAP NetWeaver AS Java 7.3

The second deployment of a web application to SAP NetWeaver AS Java7.3 may fail with the error message "javax.xml.transform.TransformerFactoryConfigurationError: Providerorg.apache.xalan.processor.TransformerFactoryImpl notfound" logged to SAP log file defaultTrace_00.0.trc.

To work around this issue, restart SAP NetWeaver AS Java 7.3 and redeploythe web application that failed.

Sun Java System Web Server

First login attempt for Sun Java System Web Server 7 in split deploymentsWhen using SAP BusinessObjects Enterprise Service Pack 2, usersattempting to log in for the first time on split deployments running Sun JavaSystem Web Server 7 may receive the error message "The web page cannotbe found." Refreshing the page and logging in a second time succeeds.

This issue is fixed in Service Pack 3.

To work around this problem, so that the first login attempt can succeed,locate and modify the Sun Java System Web Server 7 configuration fileobj.conf:1. Open the file <SJSWS_HOME>/https<INSTANCE_NAME>/con

fig/obj.conf with a text editor.2. Search for /PlatformServices/*.object.3. On the line below /PlatformServices/*.object, add a following

line:

NameTrans fn="assign-name" from="/PlatformServices/*.object;jsessionid=*" name="<CONNECTOR_NAME>"

Replace <CONNECTOR_NAME> with the name of the connector used toconnect the web and web application server. This is the same parameter



used for the -Dconnector_name parameter for the wdeploy command.For example:

NameTrans fn="assign-name" from="/PlatformServices/*.object;jsessionid=*" name="passthrough"

4. Save the file and restart Sun Java System Web Server.

Tomcat

Using Tomcat in IPv6-only mode on Windows Vista or 2008

If you are using Tomcat on a Windows Vista or 2008 server in IPv6-onlymode, disable IPv4 through the Windows Control Panel's NetworkConnections. Do not uninstall IPv4. If you do, Tomcat may not start.

This is a known issue with Java JDK 5 and 6.

Undeploy web applications from Tomcat using wdeployThe wdeploy undeploy command on a Tomcat web application servermay encounter an error if the web application server is not shut down andstill in use. Work around this issue by shutting down the Tomcat webapplication server before attempting to run the wdeploy undeploycommand.

Unexpected message when creating a Web Intelligence document on Tomcat 6

When creating a new Web Intelligence document in the InfoView applicationdeployed on Tomcat 6 (using JDK 1.6), you may encounter the followingmessage: HTTP Status 404 - /AnalyticalReporting/WebiCreate.do . This problem occurs on both Windows and Unix deployments.

To resolve this problem:1. Stop your Tomcat service.2. Navigate to the \bin\ folder within your Tomcat home directory and

open the catalina.sh file for editing.3. Add the following options to the Java environment variable:

JAVA_OPTS=-Djava.awt.headless=true -Dsun.lang.ClassLoader.allowArraySyntax=true



4. Save and close catalina.sh.5. Restart your Tomcat service.

After restarting Tomcat, logon to InfoView and create your new WebIntelligence document.

WebLogic

Undeploy web services from WebLogicUsing the wdeploy undeploy or wdeploy undeployall commandsmay not remove the BusinessProcessBI.war or dswsbobje.war filesfrom a WebLogic 10 web application server.

To work around this problem, stop both the BusinessProcessBI anddswsbobje web applications with the administrative console, and restart theweb application server. When the web application server has restarted, youcan now use the wdeploy undeploy or wdeploy undeployall toremove BusinessProcessBI.war and dswsbobje.war.

WebLogic with Sun JDKWhen using WebLogic 10 with the Sun JDK 1.5.x, the deployment may runout of file handles and display the following exception:

<Error> <Deployer> <BEA-149202> <Encountered an exceptionwhile attempting to commit the 1 task for the application” using WDEPLOY or manual deployment

To work around this problem, use the JRockit JDK.

WebSphere

Central Management Console (CMC) with WebSphere on AIXIf you have deployed the CMC to WebSphere running on AIX, the "FolderLimits" pages may generate an HTTP 500 error.

To resolve the Folder Limits HTTP 500 error, these steps must be followed.1. Launch the WebSphere administrative console and stop the CmcApp.war

and CmcAppActions.war applications.



2. In the WebSphere console, go to Enterprise Applications >YOUR_WEB_APPLICATION > Manage Modules > YOU_WEB_APPLICATION.war and select Classes loaded with application class loaderfirst from the combo box.

3. Remove the xml-apis.jar from CmcApp and CmcAppActions, if itappears.

4. Restart the web application.

Deploy to WebSphere secured modeA validation error may be generated when using wdeploy with a WebSphereinstallation that uses Secure Socket Layer (SSL) encryption. To work aroundthis issue, use the wsadmin command to manually accept the SSL certificatebefore attempting to deploy with wdeploy.

For example, change directories to <WEBSPHERE_INSTALL_DIR>\AppServer\bin and run the following command:

wsadmin -conntype SOAP -port <SOAP_admin_port>-user <as_admin_username> -password <as_ad

min_password>

Replace <SOAP_admin_port> with the port number used by WebSphere(e.g. 8880), <as_admin_username> with the username for youradministrator account (e.g. admin), and <as_admin_password> with thepassword for the account you specified for <as_admin_username>.

Press Y to accept the certificate, then proceed with the web applicationdeployment using wdeploy.

Web Services on WebSphere 7.0After using the wdeploy command to deploy Web Services to WebSphere7.0, the List of Web Services link is not available in the SAPBusinessObjects Enterprise Web Services portal interface.



1. Start the WebSphere 7.0 web application server.



2. Use the wdeploy command to deploy dswsbobje.war and BusinessProcessBI.war.

3. Stop the WebSphere 7.0 web application server.4. Copy the file<WEBSPHERE7_INSTALL_DIR>\profiles\AppSrv01\in








More Information

A

LocationInformation Resource

http://www.sap.comSAP BusinessObjects productinformation

Navigate to http://help.sap.com/businessobjects and onthe "SAP BusinessObjects Overview" side panel click AllProducts.

You can access the most up-to-date documentation cover-ing all SAP BusinessObjects products and their deploymentat the SAP Help Portal. You can download PDF versionsor installable HTML libraries.

Certain guides are stored on the SAP Service Marketplaceand are not available from the SAP Help Portal. Theseguides are listed on the Help Portal accompanied by a linkto the SAP Service Marketplace. Customers with a mainte-nance agreement have an authorized user ID to accessthis site. To obtain an ID, contact your customer supportrepresentative.

SAP Help Portal

http://service.sap.com/bosap-support > Documentation• Installation guides: https://service.sap.com/bosap-inst

guides• Release notes: http://service.sap.com/releasenotes

The SAP Service Marketplace stores certain installationguides, upgrade and migration guides, deployment guides,release notes and Supported Platforms documents. Cus-tomers with a maintenance agreement have an authorizeduser ID to access this site. Contact your customer supportrepresentative to obtain an ID. If you are redirected to theSAP Service Marketplace from the SAP Help Portal, usethe menu in the navigation pane on the left to locate thecategory containing the documentation you want to access.

SAP Service Marketplace


More InformationA

http://www.sap.com

http://help.sap.com/businessobjects

http://service.sap.com/bosap-support

https://service.sap.com/bosap-instguides

https://service.sap.com/bosap-instguides

http://service.sap.com/releasenotes


https://cw.sdn.sap.com/cw/community/docupedia

Docupedia provides additional documentation resources,a collaborative authoring environment, and an interactivefeedback channel.

Docupedia

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

https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibraryDeveloper resources

https://www.sdn.sap.com/irj/boc/businessobjects-articles

These articles were formerly known as technical papers.

SAP BusinessObjects articleson the SAP Community Net-work

https://service.sap.com/notes

These notes were formerly known as Knowledge Base ar-ticles.

Notes

https://www.sdn.sap.com/irj/scn/forumsForums on the SAP Communi-ty Network

http://www.sap.com/services/education

From traditional classroom learning to targeted e-learningseminars, we can offer a training package to suit yourlearning needs and preferred learning style.

Training


The SAP Support Portal contains information about Cus-tomer Support programs and services. It also has links toa wide range of technical information and downloads.Customers with a maintenance agreement have an autho-rized user ID to access this site. To obtain an ID, contactyour customer support representative.

Online customer support


AMore Information

https://cw.sdn.sap.com/cw/community/docupedia

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

https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibrary

https://www.sdn.sap.com/irj/boc/businessobjects-articles

https://service.sap.com/notes

https://www.sdn.sap.com/irj/scn/forums

http://www.sap.com/services/education



http://www.sap.com/services/bysubject/businessobjectsconsulting

Consultants can accompany you from the initial analysisstage to the delivery of your deployment project. Expertiseis available in topics such as relational and multidimensionaldatabases, connectivity, database design tools, and customized embedding technology.

Consulting


More InformationA



Index8-dot-3 filenames support 24

AAIX 218

Bbasic web tier scenario

configuration details 146diagram 146overview 146system layers 146

BusinessObjects Enterpriseclient 186documentation 10

CCentral Management Console (CMC) 213

clustering 17, 164fault tolerance 17, 164load balancing 17, 164session affinity 17, 164

Cisco load balancer 181client

set up 186clustering 213

File Repository Servers 173support 17, 164

clustersWebLogic configuration 176

CMC 218config. files 191cookie persistence 18, 181

Ddeployment 213

documentation 10JBoss 106load balancers 18Oracle Application Server 107SAP NetWeaver AS Java 7.0 109Tomcat 5.5 110Tomcat 6 110Tomcat 7 111Tomcat clusters 112verifying 35WebLogic 10.3 112WebLogic clusters 113WebSphere 6.1 117WebSphere cluster 121

deployment scenariocomplex 163diagram 163

deployment scenariosdesktop client to server 126general overview 126

deployment, manualWebSphere 7.0 118

dswsbobje.warWebLogic deployment 116

Ffault tolerance

session affinityweb application support 17, 164

support 17, 164


Fault tolerant 213Folder Limits 218

HHigh-availability 213

IInfoView 213

clustering 17, 164fault tolerance 17, 164load balancing 17, 164session affinity 17, 164

installationmodes 16web application server 26

JJAVA_HOME 25JBoss

manual deployment 106

Lload balancer 181

support 17, 164load balancers 18

Mmod_oc4j.conf file 212

OOc4jRoutingMode Static entry 212Oracle Application Server


SSAP Application Server 7.0

manual deployment 109servers

assigning static ports 136, 174clustering File Repository servers 173

SOAPtimeout 211

sticky session persistence 18, 181supported platforms 8

TTomcat 5.5

manual deployment 110Tomcat 6

manual deployment 110Tomcat 7

manual deployment 111Tomcat clusters


WWAR file

verifying deployment 35war files

preparing for WebLogic 179WAR files

configuring 95context roots 101deploying to remote server 95deploying to WebLogic 10 180deployment guidelines 104web services 100

wdeploycommand-line 34configuration file 27, 191hardware requirements 25log file 23options 23


Index

wdeploy (continued)overview 20, 27prerequisites 24reference 190split mode 21standalone mode 20Tomcat 5.5 48Tomcat 6.0 54Tomcat 7.0 60with JBoss 36with Oracle 38with SAP NetWeaver AS Java 7.0 42with SAP NetWeaver AS Java 7.3 45with WebLogic 10.3 66with WebLogic 10.3.3 (11gR1) 72with WebSphere 6.1 79with WebSphere 7 85

wdeploy tool 213web application deployment

on remote machines 95web application server

initial installation 26

web services 100, 213WebLogic

preparing cluster 176WebLogic 10.3

deploying with wdeploy 66manual deployment 112

WebLogic 10.3.3 (11gR1)deploying with wdeploy 72

WebLogic administration consoledeploying WAR files 180

WebLogic clustersmanual deployment 113

WebSphere 213, 218JSF implementation 88, 121

WebSphere 6.1manual deployment 117

WebSphere 7.0manual deployment 118

WebSphere clusterdeploying to 121

what's new 8


Index


Index

xi31 sp5 webappd win en

Documents