xi31_sp5_webappd_unix_en.pdf

8/10/2019 xi31_sp5_webappd_unix_en.pdf

http://slidepdf.com/reader/full/xi31sp5webappdunixenpdf 1/218

Web Application Deployment Guide

for UNIX

SAP BusinessObjects Enterprise XI 3.1 Service Pack 5

unix



© 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, Crystal

Decisions, Web Intelligence, Xcelsius, and other Business Objects products andservices mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is anSAP company.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, 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. Nationalproduct 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 be

liable for errors or omissions with respect to the materials. The only warranties for SAP 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? ....................................................................................8

About this documentation............................................................................9

Who should read this documentation .......................................................10

SAP BusinessObjects Enterprise guides...................................................10

What is BusinessObjects Enterprise?.......................................................12

Deploying web applications after installation 15Chapter 2

Overview of post-installation deployment..................................................16

Web application clustering support......................................................17

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

Deploying with wdeploy 19Chapter 3

Overview of wdeploy..................................................................................20Standalone mode.................................................................................20

Split mode............................................................................................21

Actions for wdeploy....................................................................................23

Log file creation....................................................................................23

Prerequisites for using wdeploy.................................................................24

Minimum rights for deploying web applications....................................24

Set the JAVA_HOME............................................................................34

Hardware requirements........................................................................35

Before you deploy web applications.....................................................35

How to use wdeploy...................................................................................36

Where to find wdeploy..........................................................................37

Web Application Deployment Guide for UNIX 3



The wdeploy configuration file..............................................................37

Command-line usage of wdeploy.........................................................45

After deploying web applications..........................................................47

Deploying to web application servers with wdeploy..................................47

JBoss 4.2.3 with wdeploy.....................................................................47

Oracle Application Server 10g R3 with wdeploy..................................50

SAP NetWeaver AS Java 7.0 with wdeploy.........................................53

SAP NetWeaver AS Java 7.3 with wdeploy.........................................56

Sun Java Application Server 8.2 with wdeploy....................................59

Tomcat 5.5 with wdeploy......................................................................67

Tomcat 6.0 with wdeploy......................................................................73Tomcat 7.0 with wdeploy......................................................................79

WebLogic 10 or 10.3 with wdeploy.......................................................85

WebLogic 10.3.3 (11gR1) with wdeploy...............................................91

WebSphere 6.1 with wdeploy...............................................................98

WebSphere 7.0 with wdeploy.............................................................104

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

Manually deploying to a web application server 119Chapter 4

BusinessObjects Enterprise WAR files....................................................120

WAR file context roots.............................................................................121

Predeployment without access to Web Application servers....................123

Guidelines for deploying WAR files.........................................................124

To manually deploy web applications......................................................124

Deploying with the Administration console..............................................126

JBoss..................................................................................................126

Oracle Application Server...................................................................127

SAP NetWeaver.................................................................................129Sun Java Application Server..............................................................130

Tomcat................................................................................................134

WebLogic...........................................................................................136

4 Web Application Deployment Guide for UNIX

Contents



WebSphere........................................................................................140

Sample Deployment Scenarios 149Chapter 5

Overview of deployment scenarios..........................................................150

Desktop client to server scenario............................................................150

Desktop client to server overview .....................................................150

Summary of required tasks................................................................151

Deploying the client to server scenario..............................................152

Basic N-tier scenario................................................................................160

N-tier scenario overview.....................................................................160

Summary of required tasks................................................................161Deploying the basic N-tier scenario...................................................162

Appendix 175Chapter 6

Reference for wdeploy.............................................................................176

Configuration Information...................................................................176

wdeploy parameters ..........................................................................182

wdeploy actions..................................................................................189

Web application updates made by wdeploy.......................................194Troubleshooting wdeploy.........................................................................197

WASX7017E: Exception deploying in WebSphere ...........................197

Instance configuration was modified in Sun Java Web Server..........198

Sun Java System Web Server connector information for Tomcat......198

Sun Java System Web Server connector information for WebLogic...198

Sun Java SystemWeb Server connector information for WebSphere.199

Apache or Sun Java System Web server/Oracle 10G R3 applicationserver split deployment .....................................................................199

Web application not removed from server..........................................199Known issues...........................................................................................200

Java fails to run in an IPv6 solo environment.....................................200


Contents



Known web application server issues................................................200

More Information 211Appendix A

Index 215


Contents



Getting Started

1



What's new in the SAP BusinessObjects

Enterprise Web Application DeploymentGuide?

For a list of supported platforms, databases, web application servers, webservers, and other systems supported by this release, see the Products

Availability Report (Supported Platforms), available on the SAPBusinessObjects section of the SAP Support Portal at: https://ser

vice.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 since

BusinessObjects Enterprise XI 3.1 and what has changed in Service Pack5:

Supported in

XI 3.1 SP5

Supported in

XI 3.1 SP4

Supported in

XI 3.1 SP3

Supported in

XI 3.1 SP2

Supported in

XI 3.0 SP1 or

XI 3.1

Java Web ap-

plication

server

YesYesYesYesYesTomcat 5.5

YesYesYesYesNoTomcat 6

YesNoNoNoNoTomcat 7

YesYesYesYesYesWebSphere

6.1

YesYesYesYesNoWebSphere 7

NoYesYesYesYesWebLogic 9.2

YesYesYesYesYesWebLogic 10

YesYesYesYesNoWebLogic

10.3


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

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






Supported in

XI 3.1 SP5

Supported in

XI 3.1 SP4

Supported in

XI 3.1 SP3

Supported in

XI 3.1 SP2

Supported in

XI 3.0 SP1 or

XI 3.1

Java Web ap-

plication

server

YesYesNoNoNo

WebLogic

10.3.3

(11gR1)

YesYesYesYesYesNetWeaver

7.0

NoNoYesYesNoNetWeaver

7.1

YesYesNoNoNoNetWeaver 7.3

NoNoNoYesYesJBoss 4.0.4

YesYesYesNoNoJBoss 4.2.3

YesYesYesYesYesSunOne 8.1

YesYesYesYesYesOracle 10g R3

NoYesYesYesYesWebSphereCommunity

Edition 2.0

About this documentation

This documentation provides information, procedures, and options for deploying 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 Started

About this documentation



Note:

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

Who should read this documentation

This documentation is intended for the system administrator or IT professionalworking with BusinessObjects Enterprise on a UNIX or Linux 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 Microsoft Windows

operating system, please read the SAP BusinessObjects EnterpriseInstallation Guide for Windows.

SAP BusinessObjects Enterprise guides

The 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 your installationof SAPBusinessObjects 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 Started

SAP BusinessObjects Enterprise guides



DescriptionGuide

Provides an overview of the publishingprocess, working with publications, pub-lishing Crystal reports, publishing WebIntelligence documents, publishing Desk-top Intelligencedocuments, 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 forupgrades 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 your information technology infrastructure. Support for many industry-standard

database systems makes it easier to access your organization's data for analysis. The use of common industry standards for security allow you touseyour 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/

http://help.sap.com/



As a system administrator, you will be facedwith 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 Started

What is BusinessObjects Enterprise?




Getting Started1 What is BusinessObjects Enterprise?



Deploying web applicationsafter installation

2



Overview of post-installation deployment

The 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, or with 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 wdeploy

predeploy command automates this process.

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

Administrative con-

sole

wdeploycommand-

line

Setup program post-

installation

Web application

server

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 or newer) *

Tomcat 7.0 ****

SAP NetWeaver ASJava 7.0


Deploying web applications after installation2 Overview of post-installation deployment



Administrative con-

sole

wdeploycommand-

line

Setup program post-

installation

Web application

server

SAP NetWeaver ASJava 7.3 **

Oracle ApplicationServer 10g R3

Sun Java ApplicationServer 8.2

JBoss 4.2.3 **

• * 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 installation

Overview of post-installation deployment



Fault tol-

erant

Load balances

without session

affinity

Load balancers

with session

affinity

Clustered web

application

servers

Web ap-

plication

YesSupportedSupportedSupportedInfoView(stateless)

NoUnsupportedSupportedSupportedCMC(stateful)

Failover and load balancing

SAP 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 wdeploy

The 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 for deployment to separate web and web application servers (split modedeployment). For detailed information on the wdeploy tool, see Deploying to

web application servers with wdeploy .

For more information on the system architecture of BusinessObjectsEnterprise, see the Architecture chapter of the SAP BusinessObjects

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

Planning 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) for processing (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 of users 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 wdeploy

Overview 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

• Sun Java Web Server with Sun Java Application Server

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 for deployment to web and web application servers.

When wdeploy is installed on a dedicated web server, the wdeploy

predeploy or wdeploy predeployall commands can be used to deploy

static 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

ws_dir, ws_config_dir, deployment_dir, connector_type,connector_host, connector_port, connector_conf_file

Sun Java Web Serv-er


Deploying with wdeploy3 Overview of wdeploy



Actions for wdeploy

There 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 webapplication server.

• predeployall: Prepares all web applications for deployment to a webapplication 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 webapplication 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 webapplication 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 <BOE_IN

STALL_DIR>/bobje/deployment/workdir/wdeploy.log log file.



Actions for wdeploy



Prerequisites for using wdeploy

Where to find wdeploy

The wdeploy (wdeploy.sh) command-line tool is included withBusinessObjects Enterprise to aide the command-line deployment of webapplications to Java-based web application servers. The tool and itsconfiguration files are located in <BOE_INSTALL_DIR>/deployment/.

To deploy BusinessObjects Enterprise web applications to a web applicationserver, you must have BusinessObjects Enterprise and all of the requiredWAR files installed. If the target web application server is on the samemachine as BusinessObjects Enterprise, you can proceed to run the wdeploy

script.

If the target web application server is hosted on a remote machine you willhave to follow specific steps for preparing the wdeploy environment.

Related Topics

• To deploy web applications on a remote machine

• Minimum rights for deploying web applications

Minimum rights for deploying web applications

Tip:

We recommend that you use the same user account for installingBusinessObjects Enterprise and your web application server.

To deploy web applications using a user account different from the one usedto install the web application server, you must ensure that theBusinessObjects Enterprise user account has the privileges listed in thefollowing table.

Note:In addition to the right to execute files or folders mentioned in the tablesbelow, the right to execute is also required on the parent directory.


Deploying with wdeploy3 Prerequisites for using wdeploy



JBoss 4.2.3

Example commandOther GroupUser Recur-

sive

Directory

chmod 755~<JBOSS_US

ER>

r-xr-xrwxNoJBoss user account home and

BusinessObjects Enterprise user

folder subdirectory

chmod -R 777

<JBOSS_HOME>/server/default/deploy

rwxrwxrwxYesWeb application deploymentdirec-

tory ($as_dir/serv

er/$as_instance/deploy)

chmod -R 777

<JBOSS_HOME>/server/default/deploy/jboss-tomcat55.sar

rwxrwxrwxYesJBoss web application SAR

($as_dir/server/$as_in

stance/deploy/jbossweb-

tomcat55.sar)

chmod 755

<JBOSS_HOME>/bin

r-xr-xrwxNoJBoss binaries ($as_dir/bin)

chmod 755

<JBOSS_HOME>/lib

r-xr-xrwxNoJBoss libraries ($as_dir/lib)

Oracle 10g R3

Example

command

Other GroupUser Recur-

sive

Directory

r-xr-xrwxNo






Example

command


sive

Directory

Oracle application server user account

home and BusinessObjects Enterpriseuser folder subdirectory

chmod 755~<ORA_USER>

chmod 755<ORA_HOME>

r-xr-xrwxNoWeb application deployment directory

($as_dir)

chmod 755

<ORA_HOME>/j2ee

r-xr-xrwxNoOracle AS J2EE directory

($as_dir/j2ee)

chmod -R755<ORA_HOME>/j2ee/home

r-xr-xrwxYesOracle AS J2EE/home directory

($as_dir/j2ee/home)

chmod 755

<ORA_HOME>/opmn

r-xr-xrwxNoOracle AS opmn directo-

ry($as_dir/opmn)

chmod -R777

<ORA_HOME>/opmn/conf

rwxrwxrwxYesOracle AS opmn configuration directory

($as_dir/opmn/conf)

chmod -R755<ORA_HOME>/opmn/lib

r-xr-xrwxYesOracle AS opmn library directory

($as_dir/opmn/lib)





SAP NetWeaver Java AS

Note:

If SAP is intalled in the folder hierarchy like /netweaver/sap, then the

rights outlined below must be given to both the SAP and NetWeaver directories, as outlined below.







sive

Directory

chmod 755~<SAPAS_US

ER>

r-xr-xrwxNoSAP application server account

user account home and Busines-sObjects Enterprise user folder

subdirectory

chmod 777<SAPAS_HOME>

rwxrwxrwxNoSAP AS installation directory

chmod 777

<SAPAS_HOME>/sap

rwxrwxrwxNoSAP AS directory ($as_dir)

chmod 777

<SAPAS_HOME>/sap/CTB

rwxrwxrwxNoSAP AS SID directory

($as_dir/$as_sid)

chmod 777

<SAPAS_HOME>/sap/CTB/JC00

rwxrwxrwxNoSAP AS instance directory

($as_dir/$as_sid/$as_in

stance)

chmod 777

<SAPAS_HOME>/sap/CTB/JC00/j2ee

rwxrwxrwxNoSAP AS J2EE directory


stance/j2ee)

chmod 777

<SAPAS_HOME>/sap/CTB/JC00/j2ee/deploying

rwxrwxrwxNoJ2EE deploying subdirectory


stance/j2ee/deploying)

rwxrwxrwxNo






sive

Directory

J2EE cluster subdirectory

($as_dir/$as_sid/$as_instance/j2ee/cluster)

chmod 777

<SAPAS_HOME>/sap/CTB/JC00/j2ee/cluster

chmod 777

<SAPAS_HOME>/sap/CTB/JC00/j2ee/

cluster/server0

rwxrwxrwxNoJ2EE cluster server subdirectory


stance/j2ee/cluster/serv

er0)

chmod 777

<SAPAS_HOME>/sap/CTB/JC00/j2ee/cluster/server0/apps

rwxrwxrwxNoJ2EE cluster server subdirectory


stance/j2ee/cluster/serv

er0/apps)

chmod 777

<SAPAS_HOME>/sap/CTB/JC00/j2ee/cluster/server0/apps/sap.com

rwxrwxrwxNoJ2EE cluster domain subdirectory

($as_dir/$as_sid/$as_instance/j2ee/cluster/serv

er0/apps/sap.com)

Tomcat

Examplecommand

Other GroupUser Recur-sive

Directory

r-xr-xrwxNoTomcat user account home and Busines-

sObjects Enterprise user folder subdirec-

tory






Example

command


sive

Directory

chmod 755

~<TOMCAT_USER>

chmod 777

<TC_HOME>/webapps

rwxrwxrwxNoWeb application deployment directory

($as_dir/webapps)

chmod 777

<TC_HOME>/bin

rwxrwxrwxNoTomcat binary directory

($as_dir/bin)

chmod -R777

<TC_HOME>/conf

rwxrwxrwxYesTomcat configuration directory

($as_dir/conf)

chmod 755

<TC_HOME>/lib/*

r-xr-xrwxNoTomcat library directory

($as_dir/lib)

WebLogic


sive

Directory






sive

Directory

WebLogic user account home and

BusinessObjects Enterprise user folder subdirectory

chmod 755<WL_USER>

r-xr-xrwxNo

chmod 777<WL_HOME>/

user_projects/domains/base_domain/bin

rwxrwxrwxNoWeb domain binaries

($WL_HOME/<PROJECT>/<DO

MAIN>/<BASE>/bin)

chmod 755<WL_SERVER>/user_projects

/lib

r-xr-xrwxNoWebLogic server libraries

($WL_HOME/server/lib)

chmod 775<WL_SERVER>/user_projects/bin

r-xrwxrwxNoWebLogic server binaries

($WL_HOME/server/do-

mains/base_domain com-

mon/bin)

chmod 775<WL_SERV

ER>/modules

r-xrwxrwxNoWebLogic server modules($WL_HOME/server/do-

mains/base_domain mod-

ules)

chmod 775<WL_SERV

ER>/jdk150_06

r-xrwxrwxNoWebLogic Java

($WL_HOME/jdk150_06)

WebSphere







sive

Directory

WebSphere user account home

and BusinessObjects Enterpriseuser folder subdirectory

chmod 755~<WEB

SPHERE_USER>

r-xr-xrwxNo

chmod -R 777<WEB

SPHERE_HOME>/AppServer/profiles

rwxrwxrwxYesWebSphere profiles directory

($WEBS_HOME/AppServ

er/profiles)

chmod 755<WEB

SPHERE_HOME>/bin/wsadmin.sh

r-xr-xrwxNoWebSphere admin script($as_dir/bin/wsadmin.sh)

chmod 755<WEB

SPHERE_HOME>/bin/GenPluginCfg.sh

r-xr-xrwxNoWebSphere plugin script

($as_dir/bin/GenPlug

inCfg.sh)

chmod 755<WEB

SPHERE_HOME>/bin/securityProcs.jacl

r-xr-xrwxNoWebSphere security

($as_dir/bin/securi

tyProcs.jacl)

chmod 755<WEB

SPHERE_HOME>/bin/LTPA_LDAPsecurityProcs.jacl

r-xr-xrwxNoWebSphere security

($as_dir/bin/LTPA_LDAPse

curityProcs.jacl)






sive

Directory

WebSphere plugins directory

($as_dir/plugins) chmod 755<WEB

SPHERE_HOME>/plugins

r-xr-xrwxNo

chmod 755<WEB

SPHERE_HOME>/java

r-xr-xrwxNoWebSphere Java directory

($as_dir/java)

chmod 755<WEB

SPHERE_HOME>/deploytool

r-xr-xrwxNoWebSpheredeployment tool direc-tory ($as_dir/deploytool)

chmod 755<WEB

SPHERE_HOME>/properties

r-xr-xrwxNoWebSphere properties directory

($as_dir/properties)

Note:

You must accept the WebSphere web application server SSL certificatebefore you can use wdeploy. To accept the certificate, use wsadmin

command in the format

<WEBSPHERE_HOME>/AppServer/bin/wsadmin-conntype SOAP -port <ADMIN_PORT> -user <AS_AD

MIN_USERNAME>-password <AS_ADMIN_PASSWORD>

. For example:

./wsadmin -conntype SOAP-port 8880 -user administrator -password websphere






Sun Java System Application Server

Example com-

mand


sive

Directory

chmod 755~<SO_USER>

r-xr-xrwxNoSun Java System Application Server

user account home and BusinessOb-

jects Enterprise user folder subdirecto-

ry

chmod -R 777

<SO_HOME>/do

mains/d1/config

rwxrwxrwxYesSun Java System Application Server

($as_dir/domains/$as_do

main/config)

Note:

You must accept the Sun One web application server SSL certificate beforeyou can use wdeploy. To accept the certificate, use wsadmin command in

the format

<SO_HOME>/bin/asadmin

get --port <ADMIN_PORT> --user admin --secure '*'. For example:

./asadmin get --port 4849--user admin --secure '*'

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 must





install 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 whereJava is installed. If the JAVA_HOME variable is not set, or is invalid, the

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

• 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 attempt

to install BusinessObjects Enterprise. Consult your web application server documentation for installation instructions.

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






It is recommended that you change the minimum and maximum heapsizeand the maximum Permanent Generation size settings of your JVM to-Xms128m -Xmx1024m -XX:MaxPermSize=256m. If using Tomcat for example, 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.

How to use wdeploy

The 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 installationdirectory.

2. How to update the wdeploy configuration file to contain the default optionsand 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


Deploying with wdeploy3 How to use wdeploy



Where to find wdeploy

The wdeploy tool and its configuration files are located in the deploymentsubdirectory of the BusinessObjects Enterprise install directory IN

STALL_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 <INSTALL_DIR>/deployment/con

fig.<WEB_APP_SERVER>. Substitute the <WEB_APP_SERVER> suffixfor the name of your web application server. The suffix must be the sameweb application 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.sunone82 (Sun Java Application Server 8.2)

• 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, for split web application and web

server deployments)• config.iplanet (Sun Java System Web Server 7)

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



How to use wdeploy



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.





Required parametersWeb application

server

• as_soap_port: SOAP port for application server administration. If

not set, the default SOAP port will be used (for example “8880”).

• as_admin_username: WebSphere administrator account username

(for example “administrator”).

Note:

If as_admin_is_secure is false, a value for as_admin_username

does not need to be specified.

• as_admin_password: WebSphere administrator account password

(for example “password”).

Note:

If as_admin_is_secure is false, a value for as_admin_password does

not need to be specified.

• as_instance: The name of your WebSphere application server in-

stance (for example “server1”).

• as_virtual_host: The virtual host to which the application must be

bound (for example “default_host”).

• as_admin_is_secure: Instructs wdeploy that WebSphere security is

enabled (for example “false”).

Note:

Values for as_admin_username and as_admin_password must be

set when as_admin_is_secure is “true”).

• as_dir: WebSphere installation directory (for example

“/opt/IBM/WebSphere/AppServer”).

• ws_instance: The name of the web server where the application is

installed, in split mode (for example “server1”).

• enforce_file_limit: Indicates to wdeploy whether or not the web appli-

cation server may encounter issues loading applications that contain

more than 65,535 files (“False” by default).

WebSphere 6.1 or 7.0

WebLogic 10, 10.3, or

10.3.3 (11gR1)



How to use wdeploy




server

• as_admin_port: Administration port of the application server (for

example “7001”).

• as_admin_username: WebLogic administrator account username

(for example “weblogic”).

• as_admin_password: WebLogic administrator account password

(for example “weblogic”).

• as_instance: The name of your WebLogic application server instance

(for example “AdminServer”).

• as_domain_dir: WebLogic domain directory (for example

“/opt/bea/weblogic/user_projects/domains/base_do

main”).

• as_instance: Name of the web application server instance currently

used (for example “localhost”).

• as_dir: Installation directory of the web application server (for exam-

ple “/opt/tomcat”).

• as_service_key_value: Tomcat's Java parameters, and the value of

the registry key as_server_key.

Tomcat 5.5, 6.0, or 7.0

• as_dir: The location of your application server (for example

<SAP_INSTALL_DIR> /SAP).

• as_sid: The SAP system id of the target instance. (for example

“AS2”).

• as_instance: The name of your application server instance (for ex-

ample “JC01”).

• as_admin_port: The port number used by the server (for example

“50004”).

• as_admin_username: The administrator username (for example

“Administrator”).

• as_admin_password: The administrator password (for example

“password”).

SAP NetWeaver AS

Java 7.0






server

• as_dir: The location of your application server (for example

<SAP_INSTALL_DIR> /SAP).

• as_sid: The SAP system id of the target instance. (for example

“AS2”).

• as_instance: The name of your application server instance (for ex-

ample “JC01”).

• as_admin_port: The port number used by the server (for example

“50004”).

• as_admin_username: The administrator username (for example

“Administrator”).

• as_admin_password: The administrator password (for example

“password”).

• clear.temp.dirs (passed to SAP NetWeaver AS Java during deploy-

ment): toggles the automatic removal of temporary files. Should be

set to "true".

• use.deploy.controller (passed to SAP NetWeaver AS Java during

deployment): toggles use of the SAP Deploy Controller tool. Should

be set to "true".

• time.to.wait.factor (passed to SAP NetWeaver AS Java during de-

ployment): wait time in seconds for the wdeploy script to wait for the

web application server to complete deployment (for example "1600").

SAP NetWeaver AS

Java 7.3



How to use wdeploy




server

• as_admin_port: Administration port of the application server. This

is the request port of the notification server, found in the <notifi

cation-server> section of configuration file opmn.xml (for ex-

ample “6003”).

• as_admin_username: Oracle Application Server administrator ac-

count username (for example “oc4jadmin”).

• as_admin_password: OracleApplicationServeradministratoraccount

password (for example “oracle10g”).

• as_instance: The name of your Oracle Application Server application

server instance (for example “home”).

• as_admin_is_secure: Instructs wdeploy that Oracle Application

Server SSL security is enabled (for example “false”).

Note:

If as_admin_is_secure is not enabled, you will still have to specify

the username and password to access the server.

• as_dir: Oracle Application Server installation directory (for example

“/opt/product/10.1.3/OracleAS_1”).

• as_appserver_name: Name of the target application server (for ex-

ample “myserver.domain.com”).

• as_group_id: Name of theserver group to which the target application

belongs (for example “Default_group”).

Oracle Application

Server 10gR3

• as_dir: The location of the JBoss application server (for example

“/opt/jboss”).

• as_instance: The name of the JBoss application server instance (for

example “default”).

JBoss 4.2.3

Sun Java Application

Server 8.2






server

• as_dir: The location of the Sun Java application server (for example

“/opt/SUNWappserver82e”).

• as_instance: The name of the Sun Java application server instance

(for example “server”).

• as_domain: The domain the application server instance is attached

to (for example, “domain1”).

• as_admin_port: The port number of the server (for example “4849”).

• as_admin_username: The Sun Java Application Server administrator

account username (for example “admin”).

• as_admin_password: The Sun Java Application Server administrator

account password (for example “password”).

• as_admin_is_secure: Instructs wdeploy that Sun Java Application

Server SSL security is enabled (for example “true”).

Note:

If as_admin_is_secure is not enabled, you will still have to specify

the username and password to access the server.

The following table lists the required wdeploy configuration file details for the Apache web server, which can only be used when using a split web and webapplication server deployment. For more details on these parameters, seethe Appendix Reference for wdeploy .



How to use wdeploy



Required Configuration detailsWeb Server

• ws_dir: The Apache web server installation directory (for

example "/opt/apache2").

• connector_host: The hostame of the machine running

Apache.

• connector_port: The port number on which the Apache

server listens.

• connector_type: The Apache connector type used to config-

ure split mode (for example "apache").

• deployment_dir: Directory under which wdeploy creates a

subdirectory for static content served by the web server.

This name must match the application name, and the name

of the .zip archive that contains the application's static re-

sources. wdeploy creates a virtual directory on the web

server, mapping the subdirectory to the URL (for example

"/opt/apache2/htdocs").

• connector_host: The ajp13 connector hostname for Oracle

Application Server (for example "localhost"). Only used with

Oracle Application Server.

• connector_port: The ajp13 connector port number for Oracle

Application Server (for example "8009"). Only used with Or-

acle Application Server.

Apache 2.x

Sun Java System Web Server 7 (iPlanet)





Required Configuration detailsWeb Server

• ws_dir: The iPlanet web server installation directory that

contains the config and doc subdirectories (for example

"/opt/iplanet").

• ws_config_dir: The iPlanet config directory. By default:

${ws_dir}/config (for example "/opt/iplanet/config").

• connector_name: The name of the object declaring the

connector service in obj.conf (for example "passthrough").

• connector_type: The connector type used to configure split

mode (see the wdeployREADME file, located in the same

directory as wdeploy) (for example "iplanet").

• deployment_dir: The document root. By default:

${ws_dir}/docs. The path has to be an absolute path (for

example "/opt/iplanet/docs").

• connector_conf_file: The configuration file that contains Or-

acleconnector information(forexample"${ws_dir}/opii.conf").

Only used with Oracle Application Server.

• connector_host: The ajp13 connector hostname for Oracle

Application Server (for example "localhost"). Only used with


• connector_port: The ajp13 connector port number for Oracle

Application Server (for example "8009"). Only used with Or-

acle Application Server.

Command-line usage of wdeploy

The wdeploy tool requires three types of parameters:

wdeploy.sh<WEB_OR_WAS >

[-D<PROPERTY >]<ACTION >

Where:

• <WEB_OR_WAS > is the configuration file for the web or web applicationserver (e.g. tomcat55).



How to use wdeploy



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

override 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 <INSTALL_DIR>/deployment

wdeploy.sh tomcat55-Das_mode=split-Das_dir=/opt/tomcat-Das_instance=localhost

-Dws_type=apache-Dws_dir=/opt/apache-Dwork_dir=/tmp/wdeploy-Dconnector_type=tomcat55-Ddeployment_dir=/opt/apache/htdocs-DAPP=InfoViewAppdeploy

Note:

Advanced users can run just the predeploy or predeployall commands

and 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 the wdeploycommand.

For more detailed information on wdeploy see Deploying to web application

servers with wdeploy .

Related Topics






After deploying web applications

After deploying your web applications on the web or web application server using 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 or web application server, and PORT with the port number used for either HTTP

or HTTPS communication. The default root context used for InfoView is In

foViewApp; the default context used for the CMC is CmcApp.

Deploying to web application serverswith wdeploy

JBoss 4.2.3 with wdeploy

Note:

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

Using predeploy and predeployall

The predeploy command creates resources and configuration files for aspecific web application, then copies the WAR application to <BOE_IN

STALL_DIR>/deployment/workdir/jboss4, but does not deploy the

web application to the web application server. The predeployall commandperforms the predeploy command for all web applications.



Deploying to web application servers with wdeploy



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

wdeploy.sh jboss4-DAPP=InfoViewApp

predeploy

Example 2: using wdeploy predeployall to predeploy allwebapplications

to JBoss.

wdeploy.sh jboss4predeployall

Using deployonly and deployonlyall

The deployonly command deploys a web application that is specificallyconfigured for the target web application server. The deployonlyall

command performs the deployonly command for all web applications.

Example 1: InfoViewusing wdeploy deployonly to deploy a predeployedInfoView to JBoss.

wdeploy.sh jboss4-Das_dir=/opt/jboss4-Das_instance=default-DAPP=InfoViewAppdeployonly

Example 2: using wdeploy deployonlyall to deploy all predeployed

web applications to JBoss.

wdeploy.sh jboss4-Das_dir=/opt/jboss4-Das_instance=defaultdeployonlyall

Using deploy and deployall

The deploy command creates resources and configuration files for a specific

web application, which is then deployed to the web application server. Thedeployall command performs the deploy command for all web

applications.


Deploying with wdeploy3 Deploying to web application servers with wdeploy



Running deploy is equivalent to running a predeploy command followedby a deployonly command. Running deployall is equivalent to running

a predeployall command followed by a deployonlyall command.

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

wdeploy.sh jboss4-Das_dir=/opt/jboss4-Das_instance=default-DAPP=InfoViewAppdeploy

Example 2: using wdeploy deployall to predeploy, then deploy, all web

applications to JBoss.

wdeploy.sh jboss4-Das_dir=/opt/jboss4-Das_instance=defaultdeployall

Using undeploy and undeployall

The undeploy command uninstalls a previously deployed web application

from the web application server. The undeployall command performs the

undeploy command for all web applications.Example 1: using wdeploy undeploy to undeploy InfoView from JBoss.

wdeploy.sh jboss4-Das_dir=/opt/jboss4-Das_instance=default-DAPP=InfoViewAppundeploy

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

wdeploy.sh jboss4-Das_dir=/opt/jboss4-Das_instance=defaultundeployall






Oracle Application Server 10g R3 with wdeploy



STALL_DIR>/deployment/workdir/oas1013, but does not deploy the


Example 1: using wdeploy predeploy to predeploy InfoView to Oracle

Application Server.

wdeploy.sh oas1013-DAPP=InfoViewApppredeploy


to Oracle Application Server.

wdeploy.sh oas1013predeployall




Example 1: using wdeploy deployonly to deploy a predeployed InfoView

to Oracle Application Server.

wdeploy.sh oas1013-Das_dir=/opt/oracle10gasr3/oracleas_1

-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6013-Das_admin_username=oc4jadmin-Das_admin_password=oracle12





-DAPP=InfoViewAppdeployonly


web applications to Oracle Application Server.

wdeploy.sh oas1013-Das_dir=/opt/oracle10gasr3/oracleas_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6013-Das_admin_username=oc4jadmin-Das_admin_password=oracle12deployonlyall


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 followed

by 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 to


wdeploy.sh oas1013-Das_dir=/opt/oracle10gasr3/oracleas_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6013-Das_admin_username=oc4jadmin-Das_admin_password=oracle12-DAPP=InfoViewAppdeploy






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

wdeploy.sh oas1013

-Das_dir=/opt/oracle10gasr3/oracleas_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6013-Das_admin_username=oc4jadmin-Das_admin_password=oracle12deployall


The undeploy command uninstalls a previously deployed web applicationfrom the web application server. The undeployall command performs the

undeploy command for all web applications.

Example 1: using wdeploy undeploy to undeploy InfoView from Oracle Application Server.

wdeploy.sh oas1013-Das_dir=/opt/oracle10gasr3/oracleas_1-Das_instance=home-Das_appserver_name=oc4j_inst1

-Das_group_id=default_group-Das_admin_port=6013-Das_admin_username=oc4jadmin-Das_admin_password=oracle12-DAPP=InfoViewAppundeploy

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

wdeploy.sh oas1013-Das_dir=/opt/oracle10gasr3/oracleas_1-Das_instance=home-Das_appserver_name=oc4j_inst1-Das_group_id=default_group-Das_admin_port=6013-Das_admin_username=oc4jadmin





-Das_admin_password=oracle12undeployall

Related Topics


SAP NetWeaver AS Java 7.0 with wdeploy

Note:

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



STALL_DIR>/deployment/workdir/sapappsvr7, but does not deploythe web application to the web application server. The predeployall

command performs the predeploy command for all web applications.

Example 1: using wdeploy predeploy to predeploy InfoView to SAP

NetWeaver AS Java 7.0.

wdeploy.sh sapappsvr7-DAPP=InfoViewApppredeploy


to SAP NetWeaver AS Java 7.0.

wdeploy.sh sapappsvr7predeployall


The deployonly command deploys a web application that is specifically

configured for the target web application server. The deployonlyall







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

wdeploy.sh sapappsvr7

-Das_dir=/usr/sap-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50004-DAPP=InfoViewAppdeployonly


web applications to SAP NetWeaver AS Java 7.0.

wdeploy.sh sapappsvr7-Das_dir=/usr/sap-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50004deployonlyall




applications.




SAP NetWeaver AS Java 7.0.

wdeploy.sh sapappsvr7-Das_dir=/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.sh sapappsvr7-Das_dir=/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.


-Das_dir=/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 applications

from SAP NetWeaver AS Java 7.0.


-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1






-Das_admin_port=50004undeployall

Related Topics


SAP NetWeaver AS Java 7.3 with wdeploy

Note:

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



STALL_DIR>/deployment/workdir/sapappsvr73, but doesnot deploythe web application to the web application server. The predeployall


Example 1: using wdeploy predeploy to predeploy InfoView to SAP

NetWeaver AS Java 7.3.

wdeploy.sh sapappsvr73-DAPP=InfoViewApppredeploy


to SAP NetWeaver AS Java 7.3.

wdeploy.sh sapappsvr73predeployall









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


-Das_dir=/usr/sap-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50004-DAPP=InfoViewAppdeployonly


web applications to SAP NetWeaver AS Java 7.3.

wdeploy.sh sapappsvr73-Das_dir=/usr/sap-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50004deployonlyall




applications.




SAP NetWeaver AS Java 7.3.

wdeploy.sh sapappsvr73-Das_dir=/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.


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


-Das_dir=/usr/sap-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1-Das_admin_port=50004-DAPP=InfoViewAppundeploy


from SAP NetWeaver AS Java 7.3.


-Das_instance=JC01-Das_sid=AS2-Das_admin_username=Administrator-Das_admin_password=password1





-Das_admin_port=50004undeployall

Related Topics


Sun Java Application Server 8.2 with wdeploy

Note:

After you deploy a web application to Sun Java Application Server, you mustrestart the domain to which the server is attached.

If you are deploying Performance Management applications to Sun Java Application Server, you must first edit Sun Java's startup configuration. For more information, see “To deploy Performance Management to Sun Java

Application Server”.


The predeploy command creates resources and configuration files for a

specific web application, then copies the WAR application to <BOE_IN

STALL_DIR>/deployment/workdir/sunone82, but does not deploy the


Example 1: using wdeploy predeploy to predeploy InfoView to Sun Java Application Server.

wdeploy.sh sunone82-Das_admin_is_secure=true-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy allwebapplicationsto Sun Java Application Server.

wdeploy.sh sunone82-Das_admin_is_secure=truepredeployall









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

wdeploy.sh sunone82-Das_dir=/opt/SUNWappserver82e-Das_instance=server-Das_domain=domain1-Das_admin_port=4849-Das_admin_username=admin-Das_admin_password=password

-Das_admin_is_secure=true-DAPP=InfoViewAppdeployonly

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

wdeploy.sh sunone82-Das_dir=/opt/SUNWappserver82e-Das_instance=server-Das_domain=domain1

-Das_admin_port=4849-Das_admin_username=admin-Das_admin_password=password-Das_admin_is_secure=truedeployonlyall


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 web

applications.







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

wdeploy.sh sunone82

-Das_dir=/opt/SUNWappserver82e-Das_instance=server-Das_domain=domain1-Das_admin_port=4849-Das_admin_username=admin-Das_admin_password=password-Das_admin_is_secure=true-DAPP=InfoViewAppdeploy


applications to Sun Java Application Server.wdeploy.sh sunone82

-Das_dir=/opt/SUNWappserver82e-Das_instance=server-Das_domain=domain1-Das_admin_port=4849-Das_admin_username=admin-Das_admin_password=password-Das_admin_is_secure=truedeployall




Example 1: using wdeploy undeploy to undeploy InfoView from Sun Java Application Server.

wdeploy.sh sunone82-Das_dir=/opt/SUNWappserver82e-Das_instance=server-Das_domain=domain1-Das_admin_port=4849-Das_admin_username=admin-Das_admin_password=password-Das_admin_is_secure=true






-DAPP=InfoViewAppundeploy


from Sun Java Application Server.

wdeploy.sh sunone82-Das_dir=/opt/SUNWappserver82e-Das_instance=server-Das_domain=domain1-Das_admin_port=4849-Das_admin_username=admin-Das_admin_password=password-Das_admin_is_secure=trueundeployall

Related Topics

• To deploy Performance Management to Sun Java Application Server

To deploy Performance Management to Sun Java Application

Server

To deploy Performance Management applications to Sun Java ApplicationServer, you must first edit the Sun Java Application Server's start up

configuration. The start up configuration is found in the<sunone_dir> /lib/processLauncher.xml file. After you edit this file,you can deploy Performance Management through wDeploy or through theadministrative console.

1. In the <BOE_INSTALL_DIR> /bobje/enterprise120/java

directory, extract the xalan.jar and xercesImpl.jar files from

the PerformanceManagement.war file.

2. Copy the files to the $<SUNONE_INSTALL_DIR> /lib/endorsed

directory.

3. Modify Sun Java Application Server's startup configuration so that thejavax.xml.transform.TransformerFactory property points toxalan.jar file that you copied. The startup configuration is found in the

<SUNONE_INSTALL_DIR> /lib/processLauncher.xml file.

a. Open processLauncher.xml and locate the <process

name=“s1as8-<as_instance> ”> tag, where <as_instance> is





the application server instance, as documented in wdeploy's con

fig.sunone82 file.

b. Under the <process name> tag, locate the <sysproperty

key=“javax.xml.transform.TransformerFactory” value=“...”/>.

c. Change the value of this property to org.apache.xalan.processor.TransformerFactoryImpl.

<sysproperty key="javax.xml.transform.TransformerFactory" value="org.apache.xalan.processor.TransformerFactoryImpl"/>

4. Restart the Sun Java Application Server.

5. Use either wdeploy or the Sun Java Application Server administrative

console to deploy Performance Management.

To deploy to separate Sun Java System web servers and Sun

Java application servers

To reduce the load on a web application server, you can set up a separate,dedicated, web server to serve static content. All static content will be servedby 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 Sun Java System Web Server and ensure that it is workingcorrectly. Load a web page, such as Sun's default test page, to verify thatthe 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. For example: http://mywebserver.mycompany.com:<port> .

2. Ensure that your Sun Java 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:4849.






Note:

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

3. Download the web server plug-in from the SUN web site. The plug-inallows you to connect a Sun Java System web server with a Sun Javaapplication server, so the web server can forward requests for dynamicresources to application server.

4. Follow the plug-in configuration instructions on the Sun web site for configuring the bridge between Sun Java System web server and SunJava application server.

Requests for dynamic resources are now forwarded to Sun Javaapplication server when received by Sun Java System web server.

5. Ensure that the bridge between the web server and web application server is working by pointing a browser to the web server and verifying thatdynamic content from the web application server is served correctly.

For example, visit the URL: http://mywebserver.mycompa

ny.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 as

BusinessObjects 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 Sun Java are located in <BOE_IN

STALL_DIR>/deployment.

• Edit config.sunone82. For example:

#Business Objects Configuration Utilityas_admin_port=4849as_admin_username=adminas_admin_password=passwordas_instance=serveras_domain=domain1as_dir=/opt/SUNWappserver82eas_is_admin_secure=true





• Edit config.iplanet. For example:

#Business Objects Configuration Utility

ws_dir=/opt/sunwebserver7u1/webserver7/https-banpgspf01ws_config_dir=/opt/sunwebserver7u1/webserver7/https-banpgspf01/configconnector_type=sunone82connector_name=passthroughdeployment_dir=/opt/sunwebserver7u1/webserver7/https-banpgspf01/docs

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 Sun Java

System web server and dynamic content for Sun Java applicationserver.

./wdeploy.sh sunone82 -Das_mode=split-Dws_type=iplanet predeployall

The dynamic content in: <BOE_INSTALL_DIR>/deploy

ment/workdir/sunone82/application. Static content is located

in: <BOE_INSTALL_DIR>/deployment/workdir/sunone82/re

sources.

9. Run wdeploy deployonlyall command to deploy the dynamic content toSun Java application server and static content to Sun Java System webserver.

If the Sun Java application and web servers are on the same machine,static and dynamic content will be automatically deployed to the serversby the following command:

./wdeploy.sh sunone82 -Das_mode=split

-Dws_type=iplanet deployonlyallNote:

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

If the Sun Java System web server and Sun Java application server areon different machines, dynamic content will be automatically deployed to






the application server by the following command. Static content must bemanually deployed to the remote web server machine afterwards.

./wdeploy.sh sunone82

-Das_mode=split-Das_admin_password=passworddeployonlyall

Note:


Copy static content to the docs directory on the web server:

• Extract the zip files on the web application server under <BOE_IN

STALL_DIR>/deployment/workdir/sunone82/resources.

• Copy these folders from Sun Java application server to the Sun JavaSystem web server <WS_DIR>/docs folder on the Sun Java Systemweb server.

• Copy the bobj.<application>.conf files from the Sun Javaapplication server to the <WS_DIR>/conf folder on the Sun Java

System web server.

• Update the Sun Java System web server obj.conf under

<WS_DIR>/conf with the application config files. For each web

application, you must copy the content from bobj.<applica

tion>.conf to the obj.conf file, under the <Object

name=“default”> section. For example, to include AnalyticalReporting, you would enter:





• <Object name="default">...PathCheck fn="find-index" index-names="default.htm,index.htm,default.html,index.html,in

dex.jsp"NameTrans fn="assign-name" from="/AnalyticalReporting/*.do" name="passthrough"NameTrans fn="assign-name" from="/AnalyticalReporting/*.object" name="passthrough"NameTrans fn="assign-name" from="/AnalyticalReporting/Webi/cdzServlet" name="passthrough"NameTrans fn="assign-name" from="/AnalyticalReporting/webiApplet/*" name="passthrough"NameTrans fn="assign-name" from="/AnalyticalReporting/*.faces" name="passthrough"NameTrans fn="assign-name" from="/AnalyticalReport

ing/ure/*" name="passthrough"NameTrans fn="assign-name" from="/AnalyticalReporting/ajaxUre/*" name="passthrough"NameTrans fn="assign-name" from="/AnalyticalReporting/*.jsp" name="passthrough"NameTrans fn="pfx2dir" from="/AnalyticalReporting"

dir="/export/home/qaunix2/sunwebserver7u1/webserver7/https-banpgspf01/docs/AnalyticalReporting"...</Object>

Static content is now served by a dedicated web server, and dynamic content

is served by a dedicated web application server.

Tomcat 5.5 with wdeploy



STALL_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 InfoViewApp to Tomcat5.5.

wdeploy.sh tomcat55

-DAPP=InfoViewApppredeploy

Example 2: using wdeploy predeployall to predeploy allwebapplicationsto Tomcat 5.5.

wdeploy.sh tomcat55predeployall





Example 1: using wdeploy deployonly to deploy a InfoView to Tomcat

5.5.

wdeploy.sh tomcat55-Das_dir=/opt/tomcat-Das_instance=localhost-DAPP=InfoViewAppdeployonly

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

wdeploy.sh tomcat55-Das_dir=/opt/tomcat-Das_instance=localhostdeployonlyall









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

wdeploy.sh tomcat55-Das_dir=/opt/tomcat-Das_instance=localhost-DAPP=InfoViewAppdeploy


applications to Tomcat 5.5.

wdeploy.sh tomcat55-Das_dir=/opt/tomcat-Das_instance=localhostdeployall




undeploy command for all web applications.Note:

It is recommended that you stop Tomcat before using the undeploy or un

deployall commands to undeploy web applications from a Tomcat 5.5server.

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

wdeploy.sh tomcat55

-Das_dir=/opt/tomcat-Das_instance=localhost-DAPP=InfoViewAppundeploy






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

wdeploy.sh tomcat55

-Das_dir=/opt/tomcat-Das_instance=localhostundeployall

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.

Related Topics



To deploy to separate Apache web and Tomcat 5.5 web

application servers


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

example: http://mywebserver.mycompany.com:80.

2. Ensure that your Tomcat web application server is working correctly.






Note:


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

4. Follow the plug-in configuration instructions on the Apache web site for configuring the bridge between Apache web server and Tomcat webapplication server.

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




Note:





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=/opt/Tomcat5520as_instance=localhostas_service_name=Tomcat5






• Edit config.apache. For example:

#Business Objects Configuration Utilityws_dir=/opt/apache224

connector_type=tomcat55deployment_dir=/opt/apache224/htdocs

8. Use wdeploy predeploy in split mode to split source web applications intoseparate static and dynamic resources. The command must be run oncefor Apache and once for Tomcat.

For example:

• Run the following command to extract static content for the Apacheweb server.

./wdeploy.sh 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.sh tomcat55 -Das_mode=split-Dws_type=apache deployonlyall

Note:


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.sh tomcat55 -Das_mode=splitdeployonlyall

Note:


Copy static content to the htdocs directory on the web server:






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 the Apache server.

• Update Apache httpd.conf under <WS_DIR>/conf with the

application 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




Note:

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


STALL_DIR>/deployment/workdir/tomcat6, but does not deploy theweb application to the web application server. The predeployall command

performs the predeploy command for all web applications.






Example 1: using wdeploy predeploy to predeploy InfoViewApp to Tomcat6.0.

wdeploy.sh tomcat6



wdeploy.sh tomcat6predeployall






6.0.


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











wdeploy.sh tomcat6-Das_dir=/opt/tomcat-Das_instance=localhost-DAPP=InfoViewAppdeploy


applications to Tomcat 6.0.

wdeploy.sh tomcat6-Das_dir=/opt/tomcat-Das_instance=localhostdeployall




undeploy command for all web applications.Note:


deployall commands to undeploy web applications from a Tomcat 6.0server.


wdeploy.sh tomcat6

-Das_dir=/opt/tomcat-Das_instance=localhost-DAPP=InfoViewAppundeploy






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

wdeploy.sh tomcat6

-Das_dir=/opt/tomcat-Das_instance=localhostundeployall

Note:


Related Topics




application servers


Note:



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

example: http://mywebserver.mycompany.com:80.







Note:








Note:







#Business Objects Configuration Utilityas_dir=/opt/tomcat6as_instance=localhostas_service_name=Tomcat6







#Business Objects Configuration Utilityws_dir=/opt/apache224

connector_type=tomcat6deployment_dir=/opt/apache224/htdocs


For example:

• Run the following command to extract static content for the Apacheweb server.





Note:


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.


Note:








STALL_DIR>/deployment/workdir/tomcat6/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




you would enter:



Related Topics







STALL_DIR>/deployment/workdir/tomcat7, but does not deploy the


Example 1: using wdeploy predeploy to predeploy InfoViewApp to Tomcat

7.0.

wdeploy.sh tomcat7-DAPP=InfoViewApppredeploy







wdeploy.sh tomcat7

predeployall





7.0.



web applications to Tomcat 7.0.




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.






wdeploy.sh tomcat7

-Das_dir=/opt/tomcat-Das_instance=localhost-DAPP=InfoViewAppdeploy

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

wdeploy.sh tomcat7-Das_dir=/opt/tomcat-Das_instance=localhost

deployall





Note:


deployall commands to undeploy web applications from a Tomcat 7.0

server.


wdeploy.sh tomcat7-Das_dir=/opt/tomcat-Das_instance=localhost-DAPP=InfoViewAppundeploy


from Tomcat 7.0.

wdeploy.sh tomcat7-Das_dir=/opt/tomcat






-Das_instance=localhostundeployall

Note:


Related Topics




application servers


Note:



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. For example: http://mywebserver.mycompany.com:80.


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:












Note:


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.




#Business Objects Configuration Utilityas_dir=/opt/tomcat7as_instance=localhostas_service_name=Tomcat7


#Business Objects Configuration Utilityws_dir=/opt/apache224connector_type=tomcat7deployment_dir=/opt/apache224/htdocs







For example:• Run the following command to extract static content for the Apache

web server.





Note:


If Apache and Tomcat are on different machines, dynamic content willbe automatically deployed to Tomcat by the following command. Static

content must be manually deployed to the remote Apache machineafterwards.


Note:




STALL_DIR>/deployment/workdir/tomcat7/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 webapplication server to the Apache <WS_DIR>/conf folder on the

Apache server.







you would enter:



Related Topics



WebLogic 10 or 10.3 with wdeploy

Note:

If you are deploying to AIX using the wdeploy tool, see the “Wdeploy tool for WebLogic 10.3 deployment not supported on AIX 5.3, 6.1, or 7.1” sectionfor information and known issues before beginning.



STALL_DIR>/deployment/workdir/WS_VERSION , but does not deploythe web application to the web application server. The predeployall


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

wdeploy.sh weblogic10







Example 2: using wdeploy predeployall to predeploy allwebapplicationsto WebLogic 10 or 10.3.


predeployall





to WebLogic 10 or 10.3.

wdeploy.sh weblogic10-Das_domain_dir=/opt/bea/user_projects/domains/base_do

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


web applications to WebLogic 10 or 10.3.


main-Das_admin_port=7001-Das_instance=AdminServer-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_username=weblogic-Das_admin_password=weblogic-DAPP=InfoViewAppdeploy


applications to WebLogic 10 or 10.3.


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

deployall




Example1: using wdeploy undeploy to undeploy InfoView from WebLogic10 or 10.3.


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






-DAPP=InfoViewAppundeploy


from WebLogic 10 or 10.3.


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

To deploy to separate Apache web and WebLogic 10 or 10.3 web

application servers


Note:

This configuration requires that you use the wdeploy command to split web

application resources into static and dynamic content that can be deployedto separate web and web application servers.



2. Ensure that your WebLogic web application server is working correctly.


Note:






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 for dynamic resources to WebLogic.

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

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




Note:



7. Configure wdeploy environment to separate content between the web

server 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 or config.weblogic10. For example:

#Business Objects Configuration Utilityas_admin_port=7001as_admin_username=weblogicas_admin_password=weblogicas_instance=AdminServeras_domain_dir=/usr/bea/user_projects/domains/base_domain


#Business Objects Configuration Utilityws_dir=/opt/apache224/






connector_type=weblogic10deployment_dir=/opt/apache224/htdocs

8. Use wdeploy predeploy in split mode to split source web applications into

separate 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.sh weblogic10 -Das_mode=split-Dws_type=apache predeployall

The dynamic content is located in: <BOE_INSTALL_DIR>/deploy

ment/workdir/weblogic10/application.

Static content is located in: <BOE_INSTALL_DIR>/deploy

ment/workdir/weblogic10/resources.

9. Run wdeploy deployonlyall to deploy the dynamic content to WebLogicapplication 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.sh weblogic10 -Das_mode=split

-Dws_type=apache deployonlyall

Note:


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.sh weblogic10 -Das_mode=split

deployonlyall

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 web




you would enter:

Include conf/bobj.AnalyticalReporting.conf


Related Topics



WebLogic 10.3.3 (11gR1) with wdeploy

Note:

If you are deploying to AIX using the wdeploy tool, see “WebLogic 10.3.3(11gR1) on AIX prerequisites” for information and known issues beforebeginning.











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



Example 2: using wdeploy predeployall to predeploy allwebapplicationsto WebLogic 10.3.3 (11gR1) .

wdeploy.sh weblogic11predeployall






to WebLogic 10.3.3 (11gR1) .


main-Das_admin_port=7001-Das_instance=AdminServer-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_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.




WebLogic 10.3.3 (11gR1) .


-Das_domain_dir=/opt/bea/user_projects/domains/base_domain-Das_admin_port=7001-Das_instance=AdminServer-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_username=weblogic-Das_admin_password=weblogicdeployall









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


-Das_domain_dir=/opt/bea/user_projects/domains/base_domain

-Das_admin_port=7001-Das_instance=AdminServer-Das_admin_username=weblogic-Das_admin_password=weblogic-DAPP=InfoViewAppundeploy


from WebLogic 10.3.3 (11gR1) .


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

To deploy to separate Apache web and WebLogic 10.3.3 (11gR1)

web application servers


Note:

This configuration requires that you use the wdeploy command to split webapplication resources into static and dynamic content that can be deployed

to separate web and web application servers.1. Set up the Apache web server and ensure that it is working correctly.

Load a web page, such as Apache's default test page, to verify that theweb server is serving content correctly.






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.

Note:


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 a

WebLogic web application server, so Apache can forward requests for dynamic resources to WebLogic.

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

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


For example, visit the URL: http://mywebserver.mycompany.com:80/jsp-examples/.

Note:


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

To deploy web applications on a remote machine.7. Configure wdeploy environment to separate content between the web

server and the web application server. This is known as "split" mode.

The wdeploy configuration files for Apache and WebLogic are located in<BOE_INSTALL_DIR>/deployment.






• Edit config.weblogic11 or config.weblogic11. For example:

#Business Objects Configuration Utilityas_admin_port=7001

as_admin_username=weblogicas_admin_password=weblogicas_instance=AdminServeras_domain_dir=/usr/bea/user_projects/domains/base_domain


#Business Objects Configuration Utilityws_dir=/opt/apache224/connector_type=weblogic11deployment_dir=/opt/apache224/htdocs


For example:

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

./wdeploy.sh 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>/deploy

ment/workdir/weblogic11/resources.

9. Run wdeploy deployonlyall to deploy the dynamic content to WebLogicapplication 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.sh weblogic11 -Das_mode=split-Dws_type=apache deployonlyall

Note:






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




you would enter:



Related Topics








WebSphere 6.1 with wdeploy



STALL_DIR>/deployment/workdir/WS_VERSION , but does not deploy

the web application to the web application server. The predeployall


Example 1: using wdeploy predeploy to predeploy InfoViewto WebSphere

6.1.

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


to WebSphere 6.1.

wdeploy.sh websphere6-Das_virtual_host=default_host

predeployall





to WebSphere 6.1.

wdeploy.sh websphere6-Das_dir=/opt/ibm/WebSphere/AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_soap_port=8880





-DAPP=InfoViewAppdeployonly


web applications to WebSphere 6.1.

wdeploy.sh websphere6-Das_dir=/opt/ibm/WebSphere/AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_soap_port=8880deployonlyall




applications.



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

wdeploy.sh websphere6-Das_dir=/opt/ibm/WebSphere/AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_soap_port=8880-DAPP=InfoViewAppdeploy


applications to WebSphere 6.1.

wdeploy.sh websphere6-Das_dir=/opt/ibm/WebSphere/AppServer-Das_instance=server1-Das_virtual_host=default_host






-Das_soap_port=8880deployall





Example 1: using wdeploy undeploy to undeploy InfoView from

WebSphere 6.1.

wdeploy.sh websphere6-Das_dir=/opt/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.1.

wdeploy.sh websphere6-Das_dir=/opt/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 web

application servers

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

by the web server, while dynamic content will be served by the webapplication server.

Note:






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.


2. Ensure that your WebSphere web application server is working correctly.


Note:


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 server

is working by pointing a browser to the web server and verifying thatdynamic content from the web application server is served correctly.


ny.com:80/snoop/.



The wdeploy configuration files for IHS and WebSphere are located in<BOE_INSTALL_DIR>/deployment.







#Business Objects Configuration Utilityws_dir=/opt/apache

connector_type=websphere6deployment_dir=/opt/apache/htdocs

• Edit config.websphere6. For example:

#Business Objects Configuration Utilityas_soap_port=8880#as_admin_username=admin#as_admin_password=passwordas_dir=/opt/websphere/appserveras_instance=server1as_virtual_host=default_host

as_admin_is_secure=falseenforce_file_limit=truews_instance=webserver1


For example:

• Run the following command to extract static content for the IHS webserver.

./wdeploy.sh websphere6 -Das_mode=split-Dws_type=apache predeployall

The dynamic content of web applications is located in: <BOE_IN

STALL_DIR>/deployment/workdir/websphere6/application.

The static content is located in: <BOE_INSTALL_DIR>/deploy

ment/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.sh websphere6 -Das_mode=split-Dws_type=apache deployonlyall





Note:


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.sh websphere6 -Das_mode=splitdeployonlyall

Note:




STALL_DIR>/deployment/workdir/websphere6/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 WebSphere

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

• Update IHS httpd.conf under <WS_DIR>/conf with the application

config 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 the

web server using the administrative console. Click Servers > Web server .Select the web server, then click Propagate Plug-in. Web servers other than IHS require manual propagation.

• For IHS, click Servers > Web server . Select the web server, then

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

file_root>/con

fig/cells/<cell_name>/nodes/node_name/servers/<Web_serv

er_name> directory on the WebSphere web application server to the






<plugins_root>/config/<Web_server_name> directory on the

IHS web server.

11. Ensure that both static and dynamic content are correctly configured by

trying to access a web application through the web server. For example,create a URL that includes the address of the web server with the 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.


Related Topics

• The wdeploy configuration file• To deploy web applications on a remote machine

WebSphere 7.0 with wdeploy






Example 1: using wdeploy predeploy to predeploy InfoViewto WebSphere

7.0.

wdeploy.sh websphere7-Das_virtual_host=default_host-DAPP=InfoViewApp

predeploy





Example 2: using wdeploy predeployall to predeploy allwebapplicationsto WebSphere 7.0.

wdeploy.sh websphere7

-Das_virtual_host=default_hostpredeployall





Note:

After deploying to WebSphere 7.0, ensure that the setting Classes loaded

with application class loader first is enabled for each deployed webapplication. For detailed instructions, see Classes loaded with application

class loader first .

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

wdeploy.sh websphere7-Das_dir=/opt/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.0.

wdeploy.sh websphere7-Das_dir=/opt/ibm/WebSphere/AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_soap_port=8880deployonlyall







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.



Note:

After deploying to WebSphere 7.0, ensure that the setting Classes loaded

with application class loader first is enabled for each deployed webapplication. For detailed instructions, see Classes loaded with application

class loader first .


WebSphere 7.0.

wdeploy.sh websphere7-Das_dir=/opt/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.0.

wdeploy.sh websphere7-Das_dir=/opt/ibm/WebSphere/AppServer-Das_instance=server1-Das_virtual_host=default_host-Das_soap_port=8880deployall



from the web application server. The undeployall command performs theundeploy command for all web applications.





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


-Das_dir=/opt/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.0.


-Das_dir=/opt/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, rather

than 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. The

WebSphere administration console's default port number is 9060.

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

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

3. Stop the web application, so its settings can be modified.






4. Select Classes 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 web

application servers

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

by the web server, while dynamic content will be served by the webapplication server.

Note:


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.


2. Ensure that your WebSphere web application server is working correctly.


Note:

If you have any existing BusinessObjects Enterprise web applications

running on the server, they must be undeployed before continuing.

3. Run the web server plug-in installation wizard to install the plug-in 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 server

is working by pointing a browser to the web server and verifying thatdynamic content from the web application server is served correctly.


ny.com:80/snoop/.



The wdeploy configuration files for IHS and WebSphere are located in<BOE_INSTALL_DIR>/deployment.


#Business Objects Configuration Utilityws_dir=/opt/apacheconnector_type=websphere7deployment_dir=/opt/apache/htdocs

• Edit config.websphere7. For example:

#Business Objects Configuration Utilityas_soap_port=8880#as_admin_username=admin#as_admin_password=passwordas_dir=/opt/websphere/appserveras_instance=server1as_virtual_host=default_hostas_admin_is_secure=falseenforce_file_limit=truews_instance=webserver1


For example:






• Run the following command to extract static content for the IHS webserver.

./wdeploy.sh websphere7 -Das_mode=split

-Dws_type=apache predeployall

The dynamic content of web applications is located in: <BOE_IN

STALL_DIR>/deployment/workdir/websphere7/application.

The static content is located in: <BOE_INSTALL_DIR>/deploy

ment/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.sh websphere7 -Das_mode=split-Dws_type=apache deployonlyall

Note:


If IHS and WebSphere are on different machines, dynamic content will

be automatically deployed to WebSphere by the following command.Static content must be manually deployed to the remote IHS machineafterwards.

./wdeploy.sh websphere7 -Das_mode=splitdeployonlyall

Note:



• Extract the zip files on the web application server under <BOE_INSTALL_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 WebSphere

web application server to the IHS <WS_DIR>/conf folder on the IHS

server.

• Update IHS httpd.conf under <WS_DIR>/conf with the applicationconfig files. For each web application, you must include an entry inhttpd.conf. For example, to include AnalyticalReporting, you would

enter:


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 other than 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 <pro

file_root>/con

fig/cells/<cell_name>/nodes/node_name/servers/<Web_serv

er_name> directory on the WebSphere web application server to the

<plugins_root>/config/<Web_server_name> directory on the

IHS web server.

11. Ensure that both static and dynamic content are correctly configured by

trying to access a web application through the web server. For example,create a URL that includes the address of the web server with the 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.


Related Topics








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 the Administrator account. You can run the WebSphere "Administrative console"program, or use a web browser to open http://WAS_HOST

NAME :PORT /ibm/console where WAS_HOSTNAME is the name of your

WebSphere server, and PORT is the port number on which the server listens

for login requests. The default port number is 9060.

1. Select Applications > Application Type > WebSphere enterprise

applications in the menu.

The "Enterprise Applications" screen appears.

2. Choose the web application deployed by wdeploy from the list of

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


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.


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 WebSphere

7.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\dswsbob

je.war\WEB-INF\modules\addressing-1.3.mar to a new file as:<WEBSPHERE7_INSTALL_DIR>\profiles\AppSrv01\in

stalledApps\<WS7_NODE_NAME>\dswsbobje.ear\dswsbob

je.war\WEB-INF\lib\addressing-1.3.jar.

For example:

cd <WEBSPHERE7_INSTALL_DIR>\profiles\AppSrv01\installedApps\<WS7_NODE_NAME>\dswsbobje.ear\dswsbob

je.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>/bobje/enterprise120/java/applica

tions/

• <BOE_INSTALL_DIR>/Performance_Management_120/

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 contents of <BOE_INSTALL_DIR>/bobje/deployment/

Tip:

Remove the contents under <BOE_INSTALL_DIR>/bobje/deploy

ment/workdir after the file copy if that folder is not empty.

• Copy the contents of <BOE_INSTALL_DIR>/bobje/enter

prise120/java/applications/.

• From <BOE_INSTALL_DIR>/Performance_Management_120/

copy InitConfig.properties.

• From <BOE_INSTALL_DIR>/ copy LanguagePacks.xml


Deploying with wdeploy3 To 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. Youmust 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=/bea10/user_projects/domains/base_domain

as_instance=AdminServeras_admin_port=7001as_admin_username=weblogicas_admin_password=weblogic

The configuration file is located in the following directory:<BOE_IN

STALL_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>/bobje/enter

prise120/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 temporary

directory named PerformanceManagement.

For example, use the command jar xvf

PerformanceManagement.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 the

original file.

For example, type move PerformanceManagement.war

PerformanceManagement.original to rename the WAR file.



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 of

the InitConfig.properties file.

The modified file should look like the example below.

<context-param><param-name>af.configdir</param-name><param-value>/home/Performance_Manage

ment_120</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 updated

web.xml file.For example, the command jar cvf

PerformanceManagement.war -C PerformanceManagement

will create PerformanceManagement.war from the contents of thePerformanceManagement directory.

h. Deploy PerformanceManagement.war using either the wdeploy

command 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.sh<appserver> deployall -Dwar_dir=<BOE_IN

STALL_DIR>/bobje/enterprise120/java/applications

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 the wdeploycommand.

Related Topics






• Prerequisites for using wdeploy



To deploy web applications on a remote machine



Manually deploying to a webapplication server

4



BusinessObjects Enterprise WAR files

The 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 extracting 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:

TheBusinessObjectsEnterprise setup program will automatically runwdeployto deploy web applications after installation. The following information is onlyrequired if you plan to deploy web applications after the initial installation of BusinessObjects Enterprise is complete.

The setup program places the source code to be bundled into WAR files in<BOE_INSTALL_DIR>/bobj/enterprise120/java/applications.

These files are extracted and modified by wdeploy in <BOE_IN

STALL_DIR>/bobje/enterprise120/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 componentsBusinessProcess

BI.war

CMC (entry point)CmcApp.war

CMCCmcAp

pActions.war

Crystal Reports, CMC, InfoViewCrystalRe

ports.war


Manually deploying to a web application server 4 BusinessObjects Enterprise WAR files



Web application(s)WAR file

Web services componentsdswsbobje.war

InfoView (entry point)InfoViewApp.war

InfoViewInfoViewAppActions.war

Open DocumentOpenDocument.war

Dashboard and Analytics, CMC, InfoViewPerformanceMan

agement.war

CMC, InfoViewPlatformServices.war

Dashboard and AnalyticsPMC_Help.warCMC, InfoViewVoyager

Client.war

Xcelsius data presentationXCelsius.war

Xcelsius data presentationXCTemplateUploader.war

WAR file context roots All 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 server

WAR file context roots



Default context pathWAR file

/AdminToolsAdminTools

/AnalyticalReportingAnalytical

Reporting

/BusinessProcessBIBusi

nessPro

cessBI

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

named MyOrgCmc.war.

CmcApp

/CmcAppActionsCmcAp

pActions

/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 WAR

file to be named MyOrgInfoView.war.

In

foViewApp

/InfoViewAppActionsInfoViewAp

pActions

/OpenDocumentOpenDocu

ment

/PerformanceManagementPerfor

manceMan

agement

/PlatformServicesPlatformServices


Manually deploying to a web application server 4 WAR file context roots



Default context pathWAR file

/PMC_HelpPMC_Help

/VoyagerClientVoyager

Client

/XCelsiusXCelsius

/XCTemplateUploaderXCTemplate

Uploader

Predeployment without access to Web

Application serversThe wdeploy command can separate static and dynamic content for deployment to web and web application servers.

When wdeploy is installed on a dedicated web server, the wdeploy

predeploy or wdeploy predeployall commands can be used to deploy

static 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



Predeployment without access to Web Application servers



Guidelines for deploying WAR files

To 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 SAP

BusinessObjects Enterprise Administrator's Guide.

3. When deploying a web application with functionality shared between

multiple WAR files, each WAR file must reside within the same level of the context path.

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

Note:

• Only two web applications can be renamed: InfoViewApp and Cm

cApp. To rename InfoViewApp you can rename the application

using 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 the

CmcApp.war and CmcAppActions.war. Change CmcApp in the<param-value> tag shown below, to the new application name.

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

value></context-param>

To manually deploy web applicationsEnsure that your web application server is running.

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


Manually deploying to a web application server 4 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 for

deployment to Tomcat.

wdeploy.sh tomcat55-Das_dir=/opt/usr/tomcat-Das_instance=localhost-Das_service_name=Tomcat55-DAPP=InfoViewApppredeploy

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

wdeploy.sh tomcat55-Das_dir=/opt/usr/tomcat-Das_instance=localhost-Das_service_name=Tomcat55predeployall

Note:

The predeploy and predeployall commands can be used onmachines that do not host a web application server, as long as the

parameters 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_IN

STALL_DIR>/deployment/workdir/<appserver>/application

unless 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

• Prerequisites for using wdeploy




To manually deploy web applications




Deploying with the Administrationconsole

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 servers

must 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 loader

scoping in the JBoss Development Process Guide:http://docs.jboss.org/process-guide/en/html/logging.html#d0e3341.

The following deployment paths are based upon the different levels of service:


Manually deploying to a web application server 4 Deploying with the Administration console

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

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



• JBOSS_HOME /server/all/deploy

• JBOSS_HOME /server/default/deploy

• JBOSS_HOME /server/minimal/deploy

1. Copy your WAR files to the appropriate context root sub-directory under one of the above paths, based upon the level of service provided by 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 console manual

deployment

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 the

hostname or IP address of your web application server, and PORT with

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



Deploying with the Administration console



4. Click on the Deploy button.

The Deploy: Select Archive window is displayed.

5. Ensure that the Archive is present on local host option is selected,

unless the web application is already running on the server, in which caseselect Archive is already present on the server where Application

Server Control is running.

6. In the "Deployment Plan" section, ensure that Automatically create a

new deployment plan is selected.

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

field.

8. Press the Next 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 Class

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

Related Topics






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 console manual deployment

Ensure that your SAP NetWeaver AS Java 7.0 web application server isinstalled, configured, and running. Use the wdeploy predeploy command

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

deployed to SAP NetWeaver AS Java 7.0. For more information, seeOverview of wdeploy .

1. Start the DeployTool by running ./DeployTool from<SAPUSER_HOME>/sap/<System ID>/<JC-->/j2ee/admin. Connect

to your J2EE engine using the Administrator account.

2. In the DeployTool, select the Cluster tab and expand the Server >Services > Deploy node within the J2EE tree.






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

button instead.

4. In the "Deploy & Start" dialog window that appears, select the EAR filearchive created earlier with the wdeploy tool. 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.

Related Topics


Sun Java Application Server

Sun Java Application Server 8.2 administrative console manual

deployment

Ensure that your Sun Java Application Server web application server isinstalled, configured, and running before deploying WAR files.

Note:

Sun Java Application Server imposes a strict default security policy. Youmust modify the security policy before the InfoView and Central ManagementConsole can operate normally:

1. Edit <SUNONE_INSTALL_DIR>/domains/domain1/config/serv

er.policy

2. Assign write permission to java.util.PropertyPermission.

3. Assign execute and delete permission to java.io.FilePermission.

4. Assign listen andacceptpermissions to java.net.SocketPermission.

For example:

// Basic set of required permissions granted to all remaining code

grant {permission java.lang.RuntimePermission "loadLi

brary.*";permission java.lang.RuntimePermission





"queuePrintJob";permission java.net.SocketPermission "*",

"connect, listen, accept";permission java.io.FilePermission "<<ALL

FILES>>", "read, write, execute, delete";

// work-around for pointbase bug 4864405permission java.io.FilePermission

"${com.sun.aas.instanceRoot}${/}lib${/}databases${/}-", "delete";

permission java.io.FilePermission "${java.io.tmpdir}${/}-", "delete";

permission java.util.PropertyPermission "*","read, write";

permission java.lang.RuntimePermission "modifyThreadGroup";};

If you are deploying Performance Management applications to Sun Java Application Server, you must first edit Sun Java's startup configuration. For more information, see “To deploy Performance Management to Sun Java

Application Server”.

Note:

The version of jsf-impl.jar included with Sun Java System Application

Server Enterprise Edition 8.2 is not compatible with the Central ManagementConsole (CMC), and may prevent the processing of some HTML form values.To fix this problem, stop the web application server and copy the jsf-im

pl.jar file in jsfadmin.war from {SJSASEE_INSTALL_DIR}/do

mains/domain1/applications/j2ee-modules/jsfadmin/WEB-

INF/lib to {SJSASEE_INSTALL_DIR}/lib. Then restart the web

application server.

Follow this procedure for each WAR file that you want to deploy.

1. Log on to the Sun Java Application Server Admin Console.

For example: https://<YourServer> :4849/asadmin, whereYourServer is the name of the system that the Domain Admin Server isrunning on. Port 4849 is the default administrative console's default portnumber. If you changed the port number when you installed the Sun Java

Application Server administrative console, use that port number instead.






Note:

Because the Admin Console is a secure web application, you must useHTTPS instead of HTTP.

2. Under Common Tasks, select Applications > Web Applications.3. On the right-hand pane, click Deploy.

4. On the "Deploy Web Module" page:

a. If you are accessing the administrative console locally, select Specify

a package file or a directory path that must be accessible from

the server and browse to the WAR file to deploy.

b. If you are accessing the administrative console remotely, selectSpecify a package file or a directory path that must be accessible

from the server and enter the full path to the WAR file.

5. On the next "Deploy Web Module" page, type the application name andcontext root of the web application that you want to deploy. In the "Targets"area, select the instance to deploy under "Available" and add it to the"Selected" area.

Note:

It is recommended that you use the application name as the context root.

6. Click OK.

The WAR file that you chose is deployed. Repeat steps 4 to 7 for anyadditional WAR files that you want to deploy.

7. To grant the web application access to web services, add the followinglines at the end of the server.policy file, located in the

Sun\AppServer\domains\domain1\config directory:

grant codeBase "file:${com.sun.aas.instanceRoot}/domains/domain1/applications/j2ee-modules/BusinessProcessBI/-"{

permission java.security.AllPermission;};

grant codeBase "file:${com.sun.aas.instanceRoot}/domains/domain1/applications/j2ee-modules/dswsbobje/-"{

permission java.security.AllPermission;};





Related Topics

• To deploy Performance Management to Sun Java Application Server

To deploy Performance Management to Sun Java Application Server

To deploy Performance Management applications to Sun Java ApplicationServer, you must first edit the Sun Java Application Server's start upconfiguration. The start up configuration is found in the<sunone_dir> /lib/processLauncher.xml file. After you edit this file,you can deploy Performance Management through wDeploy or through theadministrative console.

1. In the <BOE_INSTALL_DIR> /bobje/enterprise120/java

directory, extract the xalan.jar and xercesImpl.jar files from

the PerformanceManagement.war

file.

2. Copy the files to the $<SUNONE_INSTALL_DIR> /lib/endorsed

directory.

3. Modify Sun Java Application Server's startup configuration so that thejavax.xml.transform.TransformerFactory property points to

xalan.jar file that you copied. The startup configuration is found in the

<SUNONE_INSTALL_DIR> /lib/processLauncher.xml file.

a. Open processLauncher.xml and locate the <process

name=“s1as8-<as_instance> ”> tag, where <as_instance> is

the application server instance, as documented in wdeploy's con

fig.sunone82 file.b. Under the <process name> tag, locate the <sysproperty

key=“javax.xml.transform.TransformerFactory” val

ue=“...”/>.

c. Change the value of this property to org.apache.xalan.processor.TransformerFactoryImpl.

<sysproperty key="javax.xml.transform.TransformerFactory" value="org.apache.xalan.processor.TransformerFactoryImpl"/>

4. Restart the Sun Java Application Server.

5. Use either wdeploy or the Sun Java Application Server administrativeconsole to deploy Performance Management.






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 the Context Path for the web application to be deployed. The contextpath must be the name of the WAR file, but without its extension. For

example, to deploy a web application packaged as YOUR_WEB_APPLICA

TION .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: <Context

docBase="<M>/YOUR_WEB_APPLICATION .war" path="<con

text_path>" crossContext="false" debug="0" reload

able="false" trusted="false"/>

3. Enter the full path to the WAR file and press the Deploy button

The WAR file is deployed.

Related Topics


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 the Context Path for the web application to be deployed. The contextpath must be the name of the WAR file, but without its extension. For example, to deploy a web application packaged as YOUR_WEB_APPLICA

TION .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: <Context

docBase="<M>/YOUR_WEB_APPLICATION .war" path="<con

text_path>" crossContext="false" debug="0" reload

able="false" trusted="false"/>

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


Related Topics


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.


Related Topics


Special considerations for deploying on Tomcat clusters

To manually deploy web applications to a Tomcat web application cluster distributed over multiple machines, you need to deploy the web applicationson to each Tomcat instance. You can use the administrative console todeploy the BusinessObjects Enterprise web applications to the webapps

subfolder 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 console manual 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 To

deploy dswsbobje.war to WebLogic .

1. Open the "WebLogic Administrative Console" with a web browser at a

http://WAS_HOSTNAME :PORT /console where WAS_HOSTNAME isthe name of your WebLogic server and PORT is the port number on which

the admin server listens.

The "WebLogic Server Administration Console" web page is displayed.

2. In the left-hand navigation pane, click Domain 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.

Related Topics


To deploy to a WebLogic cluster

To manually deploy BusinessObjects Enterprise web applications to aWebLogic cluster distributed over multiple machines, you need to deploy the

web applications to the machine hosting the WebLogic administration server.Once all the required web applications have been installed, you can use 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 a

WebLogic web application cluster. To configure the load balancer and cluster setup please consult your WebLogic documentation.

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

1. After installing and setting up the WebLogic cluster, you need to 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.DocumentBuilder FactoryImpl

Document Builder Facto-

ry

weblogic.apache.xerces.jaxp.SAXParserFactoryImpl

SAX Parser Factory

weblogic.apache.xalan.processor.Transformer FactoryImpl

Transformer Factory

2. If BusinessObjects Enterprise is installed to the same machine hosting

the 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_IN

STALL_DIR>/Performance_Management_120 to each managed

server and ensure the file path of InitConfig.properties is matches thevalue specified for af.configdir param in web.xml in PerformanceMan

agement.war as shown below:

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

<param-value>/home/Performance_Management_120

</param-value><context-param>





3. Modify the config.weblogic10 or the config.weblogic9 located

in <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 located

in the following directory:

<BOE_INSTALL_DIR>/deployment/templates/weblogic.xml.

The modifiedweblogic.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:

<BOE_INSTALL_DIR>/deployment>wdeploy.sh 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/appli

cation/.

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

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

To deploy dswsbobje.war to WebLogic

Before deploying web services WAR file on a WebLogic application server,the user must extract dswsbobje.war. If the WAR file is not extracted and






redeployed, web services applications may display the error message “AnXSD Exception occurred”.

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

server.2. Log on to the "WebLogic Administration Console".

3. Click Lock & Edit.

4. Go to Domain Structure > Deployments and click Install.

5. Browse to the extracted dswsbobje.war directory.

6. Select the directory and click Next.

7. Select Install this deployment as an application and click Next.

8. Verify the settings and click Finish.

A message will be displayed when the dswsbobje.war web 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


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 followingURL: http://WAS_HOSTNAME :PORT /admin. TheWebSphere

admin 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 to

deploy. 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 (or highlight server1 if you didn't create your own) from the Clusters and

Servers 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 create

your 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, clickEnterprise 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.

Related Topics


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 the Administrator account. You can run the WebSphere "Administrative console"program, or use a web browser to open http://WAS_HOST

NAME :PORT /ibm/console where WAS_HOSTNAME is the name of your






WebSphere server, and PORT is the port number on which the server listens

for login requests. The default port number is 9060.

1. Select Applications > Application Type > WebSphere enterprise

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






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.


from the "Class loader order" property. A confirmation message appears.


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.


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







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, rather than 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. The

WebSphere administration console's default port number is 9060.

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

Replace YOUR_WEB_APPLICATION in the example above with the name

of your web application.

3. Stop the web application, so its settings can be modified.


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, you

need 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 run 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_IN

STALL_DIR>/Performance_Management_120 to each managedserver and ensure the file path of InitConfig.properties is matches thevalue specified for af.configdir parameter in web.xml in Performance

Management.war as shown below:

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

<param-value>/home/boe120/Performance_Management_120

</param-value><context-param>

Note:

The InitConfig.properties file should be located in

<BOE_INSTALL_DIR>/BusinessObjects/Performance

Management 12.0 on each machine hosting a managed WebSphereserver.

2. Modify the config.websphere6 file located in <BOE_IN

STALL_DIR>/deployment/.

You need to specify information for the administration server. For example:

as_dir=<IBM_INSTALL_DIR>/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.sh websphere6 predeployall

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

web application you want to deploy from the following directory:

<BOE_INSTALL_DIR>/deployment/workdir/websphere6/appli

cation/

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 4-6 for each EAR file you want to install.

9. Go to System administration > Nodes and select the nodes in the cluster that are not indicated as synchronized

10. Click Synchronize.

11. Go to Applications > Enterprise Applications to start the applicationyou just installed.

Related Topics







Sample DeploymentScenarios

5



Overview of deployment scenarios

To improve your experience in installing and deploying BusinessObjectsEnterprise this section provides two sample scenarios. These examples arefor illustrative purposes. Each example includes a deployment diagram, keytasks, key configuration details, functional requirements and pre-conditions.The scenarios focus on two deployment characteristics:

• Desktop client to server

• Basic n-tier

Desktop client to server scenario

Desktop client to server overview

This scenario illustrates a simple client to server scenario which involves 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.

• The firewall uses NAT (Network Address Translation).

• Only the ports required for the communication between the desktop client

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


Sample Deployment Scenarios5 Overview of deployment scenarios



Solaris 10Installation platform for BusinessObjects Enterprise

Oracle 10g R2 (10.2)Database 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 Scenarios




Deploying the client to server scenario

To set up the data tier

The following steps require that you have already installed a version of SunSolaris 10 that meets the installation requirements for Oracle 10g R2.

Advanced administrative knowledge of Oracle Database and Sun Solaris 10products is required.

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

will need these settings when you come to install BusinessObjectsEnterprise servers and clients.

ExampleSetting

DBSERVER1_oraName of database server

system Administrator account name

password Administrator account password

UTF-8Database character set encoding

An Oracle database is now installed and ready to be used byBusinessObjects Enterprise.

2. Create or import a new tablespace 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 tablespace name

bobjuser Username for CMS ta-blespace access

mypasswordPassword for CMS ta-blespace access

create table, createsession, createprocedureSystem privileges for user access

A CMS tablespace is now available for use.

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 Oracle is 1521. The port number used by your database must be entered during the BusinessObjects Enterprise 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 the

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

To set up the server tier

You need to install and setup Solaris 10 on the two machines that will hostthe BusinessObjects Enterprise server components. Designate a machineas SERVER 1 on which you will install framework servers. Designate secondmachine, SERVER 2, on which you will install a second set of server components.

1. Mount the device that contains the installation files.

2. Type ./install.sh in the command line and press Enter .

The installation setup program is launched.

3. Select a language for the installation and press Enter .

The software license agreement is displayed.






4. Type y to agree to the terms.

5. Enter your BusinessObjects Enterprise product activation keycode in theBusiness Objects Enterprise Product Keycode field and press Enter .

6. Specify the installation directory for your BusinessObjects Enterpriseinstallation.

7. Select the language pack you want to install and press Enter .

You are prompted to select either a user or system installation.

8. Select user and press Enter .

The "Installation Type" screen is displayed.

9. Select Custom from the list of options on the Installation Type screenand press Enter .

The "Features" screen is displayed.

10. Deselect the following top level features by typing X in all thecorresponding markers.

Items to deselect

Client Components

Server Components

Ensure that the deselected features appear as [ ] before continuing.

11. Expand Server Components and select the following:

Items to select

Central Management Server

Event Server

Input File Repository Server

Output File Repository Server

a. Under Central Management Server deselect the following:





Items to deselect

Auditor

MySQL

b. Press Enter .

You are prompted if this is the first CMS cluster in your deployment

12. Select Yes and press Enter .

The "Enter the information for your new CMS" screen is displayed.

13. Press Enter to accept the default values in the Enter the information

for your new CMS and leave the password fields blank.

You are prompted to select a system database option.14. Select Oracle and press Enter .

A screen is displayed to provide configuration details for the oracledatabase server.

15. Type the following details and press Enter .

Type the followingField

DBSERVER1_oraOracle TNSNAME

mycompanyuser User ID

mypasswordPassword

A new screen prompts you about reinitializing the database.

16. Select Yes.

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

17. Type SIA1 in Server Intelligence Agent Node and press Enter .

the "Select Web Application Server" screen is displayed.

18. Select the Install Tomcat, deploy web applications and press Enter .The "Please enter port numbers for the Tomcat installation screen" isdisplayed.

19. Press Enter to accept the default values.

A screen is displayed with your specified installation directory.






20. Press Enter to start the installation.

The installation program validates your system before installingBusinessObjects Enterprise in the specified directory.

To add servers to the server tier

You need to install the framework servers on SERVER 1 before you can 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. Mount the device that contains the installation files .












9. Choose Custom or Expand. in the "Installation Type" screen.

10. Deselect all the following top-level features by typing X in all thecorresponding markers:

Items to deselect

Client Components

Web Tier Components

Note:

Ensure that the markers appear as [ ] before continuing.

11. Expand Server Components and deselect the following items:





Server name

SIA1.CentralManagementServer

SIA1.InputFileRepository

SAI1.OutputFileRepository

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

Required configuration informationField

SERVER1System

Administrator User 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 unsecured 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 anunsecured 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 privileges.This can be achieved with the su or sudo commands, by becoming a

member of the admin group, or by logging in as the root user.

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

Tip:

The command ifconfig -a will display network interface information.

Record the network information in a safe place.

3. Add exceptions to the iptables firewall rules that forward incoming 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 Name

Server Port.

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

Basic N-tier scenario

N-tier scenario overview

This section describes how to setup a scenario in which a web browser accesses BusinessObjects Enterprise system through web applications.

System layers

• Data Tier: One machine used to host the database server.• Server Tier: Three machines hosting the framework, processing and

performance management (PMC) servers.

• Web Tier: One machine in hosting the web application server.

• Client Tier: One machine running the Live Office application.


Sample Deployment Scenarios5 Basic N-tier scenario



4. Setting up the firewall

5. Setting up the client tier

Deploying the basic N-tier scenario

To set up the data tier

The following steps require that you have already installed a version of SunSolaris 10 that meets the installation requirements for MySQL. Advancedadministrative knowledge of MySQL and Sun Solaris 10 products is required.

This database will be used to hold CMS data. Additional databases 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 MySQL.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_mysqlName of database server

system Administrator account name

password Administrator account password

UTF-8Database character set encoding

A database is now installed and ready to be used by BusinessObjectsEnterprise.





2. Create or import a new tablespace for the CMS, as well as auditing or Dashboard and Analytics databases if required.

Record the settings used for creating of the CMS database.

ExampleCMS database setting

mycompanyCMS tablespace name

mycompanyuser Username for CMS tablespace access

mypasswordPassword for CMS tablespace access

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

bobjaudit Auditing tablespace name

audituser Username for auditing tablespace access

auditpasswordPassword for auditing tablespace 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 Analytcstablespace.

ExampleDashboard and Analytics database setting

bobjpmDashboard and Analytics database name

pmuser Username for PM database access

pmpasswordPassword for PM database access

A Dashboard and Analytics tablespace is now available for use.

5. Create a network-shared directory on the database server's local filesystem to contain shared files for the file repository server (FRS).






Note:

The network permissions for FRS directory must included “read”, “write”,and “execute” permissions for the networked users.

6. Extract the FRS template file (e.g. FileStore_02-22-2008.zip) withinthe FRS directory you created in the last step.

You have set up CMS, auditing, and performance management databases,as required. You have also installed a file repository server network-shareddirectory. The default listener port number used by MySQL is 3306. Thedatabase port number must be entered during theBusinessObjectsEnterpriseinstallation.

Verify the connectivity between your CMS and database machines byattempting to connect to your database(s) from the CMS server(s).

Note:This scenario includes a network firewall between the CMS and databaseservers. Ensure that this firewall is configured appropriately.

Remember:

The ability to connect to your database server from your CMS server mayrequire a change to the firewall settings on both machines.

Connection Server in heterogenous environments

The SAP BusinessObjects Enterprise Connection Server provides accessto databases for the Web Intelligence server and Web Intelligence rich clients.In heterogenous environments, where there is a mixture of UNIX andWindows systems, the Connection Server can be used to access databasesrunning on platforms other than the operating system used by the CentralManagement Server (CMS) .

For example, a UNIX-based CMS, with a Web Intelligence server and WebIntelligence rich clients, can use a connection server running on Windowsto provide a database connection to a Microsoft SQL Server database server.

A number of connection servers can be used by a SAP BusinessObjectsEnterprise system at the same time, allowing UNIX-based deployments to

access Windows-based databases without the need to install ODBC driverson UNIX systems.





Items to deselect

Client Components

Web Tier ComponentsServer Components

Note:


11. Expand Server Components and select the following servers:

Items to select


Event Server



12. Expand Central Management Server and deselect MySQL and Auditor.

13. Press Enter to submit your custom installation selections.

You are prompted in a new screen to specify if this is your first CMS in

your deployment.14. Select Yes - this is the first CMS in this deployment.

You are prompted to provide information on the CMS you are about toinstall.

15. Press Enter to accept the default CMS settings.

You are prompted to select a database type for the CMS.

16. Select MySQL.

The MySQL configuration screen is displayed.

17. Type the following information for the MySQL database and press Enter to submit the database configuration details.





Enter the followingField

DBSERVER1_mysqlHost Name

systemUser ID for CMS database

passwordPassword for CMS database

3306MySQL port number

mycompanyDatabase name for CMS

A new screen prompts you about reinitializing the database.

18. Select Yes press Enter .

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

19. Type SIA1 in Choose a name for the Server Intelligence Agent Node

and Press Enter .



The installation program validates your system before installingBusinessObjects Enterprise in the specified directory.

To add processing servers to the server tier















6. Specify the installation directory for your BusinessObjects Enterprise

installation.7. Select the language pack you want to install and press Enter .




9. Choose Custom or Expand in the "Installation Type" screen.


10. Deselect all the following top-level features by typing X in all the

corresponding markers:

Items to deselect

Client Components

Web Tier Components

Note:


11. Expand Server Components and deselect the following items:

Items to deselect


Event Server



Dashboard and Analytics Servers

Note:

Ensure that the markers appear as [ ] before continuing. Scroll downthe "Features" screen to access Dashboard and Analytics Servers.

12. Press Enter to submit your custom installation sections.





You are prompted to enter the name and port number of an existing CMS.

13. Type SERVER1 in CMS Hostname; leave Port and Existing CMS

Administrator Password blank. Press Enter .

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


and Press Enter .



The installation program validates your system before installingBusinessObjects Enterprise servers in the specified directory.

To add performance management servers to the server tier













8. Select user and press Enter .The "Installation Type" screen is displayed.

9. Choose Custom or Expand in the "Installation Type" screen.







10. Deselect all the following top-level features by typing X in all thecorresponding markers:

Items to deselect

Client Components

Web Tier Components

Server Components

Note:


11. Expand Server Components and select Dashboard and Analytics

Servers.Note:

Scroll down the "Features" screen to access Dashboard and Analytics

Servers.

12. Press Enter to submit your custom installation sections.

You are prompted to enter the name and port number of an existing CMS.

13. Type SERVER1 in CMS Hostname; leave Port and Existing CMS

Administrator Password blank. Press Enter

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


and Press Enter .



The installation program validates your system before installingBusinessObjects Enterprise servers in the specified directory.

To set up the web tier

Sun Solaris 10 has to be installed and running on the machine that will hostthe web tier.

Follow the procedure to install Tomcat 5.5 and deploy the BusinessObjectsEnterprise web applications.





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 unsecured 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 anunsecured external (interface eth1) network to port 8080 on for a Oracle

Application Server 10g R3 web application server running on a secure,

firewalled network (interface eth0).

1. Log in to your Red Hat Linux server.

Note:

As iptables is configured from the command-line, you need root privileges.This can be achieved with the su or sudo commands, by becoming 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 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 BusinessObjectsEnterprise credential in the following fields:

• User name

• Password

7. Enter http://WEBSERVER1:8080/dswsbobje/services/session in the Web

Service URL and System fields.

8. Select the Enterprise authentication method from the drop-down list, clickLog On and then click OK.






Appendix

6



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 web

application 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.sapappsvr73 (SAP NetWeaver AS Java 7.3)• config.sunone82 (Sun Java Application Server 8.2)

• 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 split

deployments, use the name of the supported web server:

• config.apache (Apache Web Server or IBM IHS)

• config.iplanet (Sun Java System Web Server 7)


6 Appendix

Reference for wdeploy



Note:

It is recommended that web application server administrator accountpasswords are not stored in the wdeploy configuration file, but rather passedto wdeploy from the command-line with the parameter -Das_admin_pass

word=<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>\deploy

ment\apps\<WEB_APPLICATION >.properties are pre-configured by

the 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 environment

variable.

Optionaladdtoclasspath

Path to append to the web ap-plication server's Java LIB

PATH 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


Appendix6 Reference for wdeploy




Path to the parent of the folder

that 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-tionalconfiguration 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 for the 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 number of open files. False by default.

For WebSphere 6.1file_limit_reached


6 Appendix





Name of the folder that con-

tains the web application WARor EAR files.

The default directory is<BOE_INSTALL_DIR>\en

terprise120\java\ap

plications.

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 if app_source_dir or

win_app_source_dir are

not defined. The WAR or EARfiles are located in war_dir

or 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 the

wdeploy.prop.count val-

ue. See infoview.properties.

Optionalwdeploy.prop#.name

Value of the property to set onthe target application server."#" corresponds to the wde

ploy.prop.count value.

See infoview.proper

ties.

Optionalwdeploy.prop#.value






A list of supported platforms

that supports the prop#property. "#" corresponds to

the wdeploy.prop.count

value.

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 and

app_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 takes

precedence over the value of war_dir.

Optionalwin_war_dir

Name of the static resourcefile for the application present

in war_dir.

Optionalzipfile


6 Appendix




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>/de

ploy

ment/apps/<WEB_APP >.prop

erties

APP

false (default)

true

For web application serversthat use SSLencryption 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, and

WebLogic.Web application server ad-ministrative account pass-word.

as_admin_password






8080

Mandatory for NetWeaver,

Oracle Application Server, SunJava application server, andWebLogic.

Port number for web applica-tion server administrativeaccess.

• For WebSphere, theSOAP port. If not set, thedefault SOAP port will beused.

• For Oracle ApplicationServer (oas1013): wde-ploy expects the requestport of the <notifica

tion-server> element

in the file opmn.xml.

as_admin_port

administrator

Mandatory for NetWeaver,Oracle Application Server, SunJava application server, and

WebLogic.

Web application server ad-ministrative account user-name.

as_admin_username

oracleas.mycompa

ny.com

For Oracle Application Server.

The name of the target appli-cation server.

as_appserver_name

/opt/tomcat55

Installation directory of theweb application server.

For WebLogic applicationservers, as_domain_dir is

the domain root.

as_domain_dir


6 Appendix





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 server to serve static content, anda web application server toserve dynamic content.

as_mode

HKLM\SOFTWARE\ApacheSoftware Founda

tion\Procrun

2.0\<AS_SER

VICE_NAME >\Parame

ters\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






For Tomcat running on Win-

dows.When installed as a service,the value of Windows reg-istry key where the JVMstartup parameters arestored.

as_service_key_value

Tomcat55

For Tomcat running on Win-dows.

The name of the Tomcat

service.

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. If not set, the default SOAP port

number 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_pack

age_filtering=com.ctc.wstx.*,javax.xml.*,org.apache.*

For WebLogic 10.

When the property is set, theapplication is turned into anEAR, and a filtering Class

loader is setup with thepackage list. This parameter is a comma-separated list of packages to filter from theclassloader.

classloader_package_filtering


6 Appendix





<WS_DIR>/opii.conf

For Sun Java System Web

Server.Name of the configurationfile holding the Oracle Appli-cation Server connector configuration.

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

7002For 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






<BOE_INSTALL_DIR>/de

ployment/workdir

Directory in which wdeploy

manipulates 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

/opt/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 server where 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_IN

STALL_DIR>/deploy

ment/config.<WEB_SERV

ER> 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-line

or set in the configuration file.

• Split deployments must have the -Dconnector_type=<CONNEC

TOR_TYPE > parameter given on the command-line or set in the server

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


6 Appendix




Table 6-3: wdeploy Actions

DescriptionAction

The wdeploy predeploy command prepares a web application for deployment to the target web application server.

The web application's web.xml configuration file is updated, along

with 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 or EAR file and saved to <BOE_INSTALL_DIR>/deploy

ment/workdir/<WEB_APP_SERVER>.

This file can be deployed manually through the web applicationserver's administrative console, or with the wdeploy deploy

command.

Use wdeploy predeploy to prepare the InfoViewApp web appli

cation so that it is ready for deployment to a specific web applicationserver.

wdeploy.sh <WEB_APP_SERVER>-DAPP=InfoViewApppredeploy

Substitute <WEB_APP_SERVER> for the name of the web applicationserver.

predeploy





DescriptionAction

The wdeploy predeployall command performs the wdeploy

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

command to all web applications.

wdeploy.sh <WEB_APP_SERVER> predeployall

Substitute <WEB_APP_SERVER> for the name of the web application

server.

predeployall

The wdeploy deploy command is a concatenation of the wdeploypredeploy and wdeploy deployonly commands,which prepares

and deploys a web application to the target web application server with just one command.

Use wdeploy deploy to prepare and deploy the InfoView web

application to the target web application server.

wdeploy.sh <WEB_APP_SERVER>-DAPP=InfoViewAppdeploy

Use wdeploy deploy to prepare and deploy the InfoView web

application to the target web application server.

wdeploy.sh <WEB_APP_SERVER>-DAPP=InfoViewAppdeploy


deploy


6 Appendix




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.sh <WEB_APP_SERVER> deployall


server.

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>/de

ployment/workdir/<WEB_APP_SERVER> are deployed to theweb application server by the wdeploy predeploy command in

voking 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.sh <WEB_APP_SERVER>-DAPP=InfoViewAppdeployonly


deployonly





DescriptionAction

Use wdeploy deployonlyall to apply the wdeploy deploy-

only command to all prepared web applications.

wdeploy.sh <WEB_APP_SERVER> deployonlyall


server.

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.sh <WEB_APP_SERVER>-DAPP=InfoViewAppundeploy


undeploy

The wdeploy undeployall command performs the wdeploy

undeploy command for all BusinessObjects Enterprise web appli-

cations deployed to the target web application server.

undeployall


6 Appendix




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}.conf

file 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 cre

ated, containing library path modifications, and java propertiesmodifications to add the application's properties.

${as_dir}/bin/catalina.[sh|bat] file is modified to

include 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






Properties are added as JVM options. Library path modifications

are done modifying JVM'snative 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, to

add connector configuration, directory and servlet mapping infor-mation.

NameTrans fn=pfx2dir from="${appvdir}"

dir="${deployment_dir}/${APP}"

Sun Java System WebServer

Files to add to the classpath are bundled in the application

(added to WEB-INF/lib).

${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






Files to add to the classpath are bundled in the application

(added to WEB-INF/lib).Properties are added as JVM custom properties. Library pathmodifications are done modifying the environment of the JVM.Web Serverplugin 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/in

stall.scr"; exception information:

com.ibm.websphere.management.exception.ConfigServiceEx

ception

com.ibm.websphere.management.exception.ConnectorException

org.apache.soap.SOAPException: [SOAPException: fault

Code=SOAP-ENV:Client;

msg=Read timed out; targetException=java.net.SocketTime

outException: 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>/proper

ties/soap.client.props file,


6 Appendix

Troubleshooting wdeploy



and in:

$WS_INSTALL_DIR/profiles/<pro

file>/temp/soap.client.props.

Instance configuration was modified in Sun Java Web Server

After deploying into Sun Java System Web server, if the following warningis displayed in the Administration consoleInstance configuration was

modified, click on the warning then select "Pull and deploy configuration

from <instance name>" and click Ok.

Sun Java System Web Server connector informationfor Tomcat

For Tomcat

Add to obj.conf

<Object name="jknsapi">ObjectType fn=force-type type=text/plainService fn="jk_service" method="*" worker="worker1"</Object>

where 'jknsapi' is the connector_name to pass to wdeploy

Related Topics

• http://tomcat.apache.org/connectors-doc/howto/nes.html

Sun Java System Web Server connector informationfor WebLogic

For WebLogic


Appendix6 Troubleshooting wdeploy

http://tomcat.apache.org/connectors-doc/howto/nes.html

http://tomcat.apache.org/connectors-doc/howto/nes.html



Add to obj.conf

<Object name="weblo">Service fn="wl_proxy" WebLogicHost="localhost" WebLogic

Port="7001"</Object>

where 'weblo' is the connector name to pass to wdeploy.

Related Topics

• http://e-docs.bea.com/wls/docs81/plugins/nsapi.html

Sun Java System Web Server connector informationfor WebSphere

For WebSphere, see the web site referenced below.

Related Topics

• http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?top

ic=/com.ibm.websphere.base.doc/info/aes/ae/tins_manualWebIPL.html

Apache or Sun Java System Web 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: Oc4jRoutingMode

Static.

Web application not removed from server

If a web application was not removed with the wdeploy undeploy or undeployall comamands, use the administrative console to stop all webapplications and restart the server, then re-run the undeploy or undeploy

all command.


6 Appendix

Troubleshooting wdeploy

http://e-docs.bea.com/wls/docs81/plugins/nsapi.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tins_manualWebIPL.html




http://e-docs.bea.com/wls/docs81/plugins/nsapi.html



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

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 be

deployed 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 another


Appendix6 Known issues



application 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 fault

tolerant mode.• For BusinessObjects Enterprise XI 3.1, both the CMC and InfoView

support 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.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_OP

TIONS 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.sh

or setDomainEnv.cmd scripts.

Restart your web application server, and verify connectivity with the ::1 or

localhost alias in the hosts file.


6 Appendix

Known issues



Oracle Application Server

Deployment to Oracle 10g with separate web and web application servers

When 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 following

line:

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

Using the wdeploy deployall command to deploy web applications toSAP NetWeaver AS Java 7.3 may fail with a timeout exception message if the 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.3web 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) tocreate another volumes for each log.

9. When the log files all have new volumes, restart the deployment with thewdeploy command-line tool.





Deployment to SAP NetWeaver AS Java 7.0 or 7.3 with separate web and web

application servers

The wdeploy tool does not support deployment onto SAP NetWeaver AS

Java 7.0 or 7.3 when using separate web and web application servers.

SAP NetWeaver AS Java 7.0 with language packs

When 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 GBof 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.Trans

formerFactoryConfigurationError: Provider

org.apache.xalan.processor.TransformerFactoryImpl not

found" 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 Application Server

Deployment to Sun Java System Application Server on Sun Solaris

If you are using Sun Java System Application Web Server 8.2 on Solarisand you are unable to:

• Use BusinessObjects web services.

• Select format or recipient while publishing Crystal Reports, WebIntelligence, or Desktop Intelligence reports.

• Set format via publication properties (or while creating a publication).


6 Appendix

Known issues



Add the following lines to the file <sunone_installdir>/domains/<DO

MAIN_NAME>/config/server.policy (replace <DOMAIN_NAME> withthe name of your web application server domain):

//--for BOBJgrant codeBase "file:${com.sun.aas.installRoot}/domains/<DOMAIN_NAME>/applications/j2ee-modules/dswsbobje/-" {permission java.security.AllPermission;};

//--for BOBJgrant codeBase "file:${com.sun.aas.installRoot}/domains/<DOMAIN_NAME>/applications/j2ee-modules/BusinessProcessBI/-" {permission java.security.AllPermission;};

// Basic set of required permissions granted to all remaining codegrant {

<...>permission java.lang.reflect.ReflectPermission

"suppressAccessChecks";<...>

};

Note:

The ellipses above (<...>) indicate that lines may already exist for thegrant {} structure.

First login attempt for Sun Java System Web Server 7 in split deployments

When 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 to

connect 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

Undeploy web applications from Tomcat using wdeploy

The wdeploy undeploy command on a Tomcat web application server may 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 undeploy

command.

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/WebiCre

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


6 Appendix

Known issues



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 WebLogic

Using the wdeploy undeploy or wdeploy undeployall commandsmay not remove the BusinessProcessBI.war or dswsbobje.war files

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

Deploy to WebLogic with IBM JDK on AIX

When deploying a BusinessObjects web application to WebLogic 10 withIBM JDK 1.5.0 on AIX 5.3, you may encounter a "too many files open" error message.

To work around this problem, increase the ulimit open file descriptor limitin WebLogic's commEnv.sh file. Increase the default value of 1024 to 2000

or above. For example, in <BEA_INSTALL_DIR>/weblogic92/com

mon/bin/commEnv.sh:

maxfiles=ùlimit -H -nìf [ "$?" = "0" -a èxpr ${maxfiles} : '[0-9][0-

9]*$'` -eq 0 ]; thenulimit -n 2000

Note:

Another option is to increase the hardware and software open file descriptorslimit to a high numerical value, but not "unlimited".





WebLogic with Sun JDK

When 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 applica

tion” using WDEPLOY or manual deployment

To work around this problem, use the JRockit JDK.

WebLogic 10.3 with JDK 1.6 on Linux

A deployment to a Linux WebLogic 10.3 system with Sun JDK 1.6 or IBMJDK 1.6 (32 or 64-bit) may fail with the error message:"java.util.zip.ZipException: error in opening zip file(too many files open)."

To work around this issue, increase the number of files that can be openedby both WebLogic and the operating system:

For WebLogic, increase the default value of the "ulimit" open file descriptor limit from 1024 to 2000. This can be done by modifying the file <BEA_IN

STALL_DIR>/weblogic103/common/bin/commEnv.sh to look like theexample shown below:

maxfiles=ùlimit -H -nìf [ "$?" = "0" -a èxpr ${maxfiles} : '[0-9][0-9]*$'`-eq 0 ]; thenulimit -n 2000

For Linux, increase the value of the "ulimit" open file descriptor to 4096. Thiscan be done by modifying the file /etc/security/limits.conf to look like theexample shown below. Note: root access is required.

soft nofile 4096hard nofile 4096

Restart Linux after making changes to /etc/security/limits.conf.

For more information, see http://support.bea.com/application_content/prod

uct_portlets/support_patterns/wls/TooManyOpenFilesPat

tern.html#Known_WebLogic_Server_Issues.


6 Appendix

Known issues

http://support.bea.com/application_content/product_portlets/support_patterns/wls/TooManyOpenFilesPattern.html#Known_WebLogic_Server_Issues








WebLogic 10.3 with JDK 1.6 on AIX

WebLogic 10.3 with JDK 1.6 is only supported in SAP BusinessObjectsEnterprise XI 3.1 Service Pack 3.

To use WebLogic 10.3 with JDK 1.6, ensure that SAP BusinessObjectsEnterprise XI 3.1 Service Pack 3 is installed.

WebLogic 10.3 and 10.3.3 (11gR1) on AIX prerequisites

Before deploying SAP BusinessObjects Enterprise XI 3.1 Service Pack 5web applications using the wdeploy tool to WebLogic 10.3 or 10.3.3 (11gR1)on AIX, you must remove the xercesImplnoservices.jar andxercesImpl.jar files from the PlatformServices.war web application

archive (WAR).

Remove the JAR files from one of the following locations and then use thewdeploy tool to deploy your web applications:

• <BOE_INSTALL_DIR>/bobje/warfiles/WebApps/PlatformSer

vices/WEB-INF/lib

Note:

If you remove the JAR files from this location, then when deploying withthe wdeploy tool you must pass the -Dapp_source_tree parameter.For example, on WebLogic 10.3.3 (11gR1): ./wdeploy.sh weblog

ic11 -Dapp_source_tree=<BOE_INSTALL_DIR>/bob

je/warfiles/WebApps deployall

• <BOE_INSTALL_DIR>/bobje/java/applications/PlatformSer

vices.war/WEB-INF/lib

WebSphere

Central Management Console (CMC) with WebSphere on AIX

If you have deployed the CMC to WebSphere running on AIX, the "Folder

Limits" 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.





More Information

A



LocationInformation Resource

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-sdklibrary Developer resources

https://www.sdn.sap.com/irj/boc/businessobjects-articles

These articles were formerly known as technical papers.

SAP BusinessObjects articles

on 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 your learning needs and preferred learning style.

Training

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

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://www.sdn.sap.com/irj/sdn/businessobjects-sdklibrary



https://www.sdn.sap.com/irj/scn/forums





https://www.sdn.sap.com/irj/scn/forums



https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibrary





LocationInformation Resource

http://www.sap.com/services/bysubject/businessobjectscon

sulting

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

http://www.sap.com/services/bysubject/businessobjectsconsulting






Index

A

AIX 208

B

basic web tier scenarioconfiguration details 160diagram 160overview 160system layers 160

BusinessObjects Enterprisedocumentation 10

C

Central Management Console (CMC) 200clustering 17fault tolerance 17

load balancing 17session affinity 17

clustering 200support 17

CMC 208config. files 177connection server 164cookie persistence 18

D

data tier setting up Solaris with Oracle 10g R2 152setting up with Solaris and MySQL 162

deployment 200documentation 10

deployment (continued)

JBoss 126load balancers 18Oracle Application Server 127post-installation 16SAP NetWeaver AS Java 7.0 129Sun Java Application Server 130Tomcat 5.5 134

Tomcat 6 134Tomcat 7 135Tomcat clusters 136verifying 47WebLogic 10.3 136WebLogic clusters 137WebSphere 6.1 140WebSphere cluster 145

deployment scenariosdesktop client to server 150general overview 150

deployment, manualWebSphere 7.0 141

dswsbobje.war WebLogic deployment 139

F

fault tolerancesession affinity

web application support 17support 17

Fault tolerant 200

firewalliptables configuration 159

Folder Limits 208




H

High-availability 200

I

InfoView 200clustering 17fault tolerance 17load balancing 17session affinity 17

installationweb application server 35

iptables 159

J

JAVA_HOME 34JBoss

manual deployment 126

L

load balancer support 17

load balancers 18

M

mod_oc4j.conf file 199

O

obj.conf file 198Oc4jRoutingMode Static entry 199Oracle Application Server

manual deployment 127

S

SAP NetWeaver AS Java 7.0manual deployment 129

serversassigning static ports 157

SOAPtimeout 197

sticky session persistence 18Sun Java Application Server

manual deployment 130supported platforms 8

T

Tomcat 5.5manual deployment 134

Tomcat 6manual deployment 134

Tomcat 7manual deployment 135

Tomcat clustersmanual deployment 136

U

user rightsdeploying web applications 24

W

WAR fileverifying deployment 47

WAR filesconfiguring 114context roots 121deploying to remote server 114deployment guidelines 124war services 120

wdeploycommand-line 45


Index



wdeploy (continued)

configuration file 37, 177hardware requirements 35log file 23options 23overview 20, 36prerequisites 24reference 176split mode 21standalone mode 20Tomcat 5.5 67Tomcat 6.0 73Tomcat 7.0 79with JBoss 47

with Oracle 50with SAP NetWeaver AS Java 7.0 53with SAP NetWeaver AS Java 7.3 56with Sun Java 59with WebLogic 10.3 85with WebLogic 10.3.3 (11gR1) 91with WebSphere 6.1 98

wdeploy (continued)

with WebSphere 7.0 104wdeploy tool 200web application deployment

on remote machines 114web application server

initial installation 35web services 120, 200WebLogic 10.3

manual deployment 136WebLogic clusters

manual deployment 137WebSphere 200, 208

JSF implementation 107, 145

WebSphere 6.1manual deployment 140

WebSphere 7.0manual deployment 141

WebSphere cluster deployment 145

what's new 8


Index



Index

xi31_sp5_webappd_unix_en.pdf

Documents