BusinessObjects Web Applications Deployment Guide · 2019. 11. 12. · BusinessObjects Web Applications Deployment Guide . Applies to: SAP BusinessObjects Enterprise XI 3.0 . Summary

BusinessObjects Web Applications Deployment Guide

Applies to: SAP BusinessObjects Enterprise XI 3.0

Summary This document contains detailed information for system administrators who want to deploy BusinessObjects web applications, such as InfoView, to a setup in which the web server and web application server are on separate physical machines.

Author: Yao Sun

Company: SAP

Created on: 21 March 2009

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com © 2009 SAP AG 1


Table of Contents Deployment Scenario .........................................................................................................................................3

Deployment Overview.....................................................................................................................................3 Overview of Deployment .................................................................................................................................3 Recommended Hardware Requirements........................................................................................................4 Recommended Software Requirements .........................................................................................................4

Configuration Instructions ...................................................................................................................................4 Sever Tier Configuration .................................................................................................................................4

Pre-requisites...............................................................................................................................................................4 Install Business Objects on Box 1................................................................................................................................4

Web Tier Configuration ...................................................................................................................................8 WebLogic 10 Web Application Server on Box 2...........................................................................................................8 Configure Apache 2.2 HTTP Server on Box 3 ...........................................................................................................12 Bridge the WebLogic 10 with Apache 2.2 ..................................................................................................................15 Deploy to http server and application server are on separated machines..................................................................16 Configure the CMS name for InfoView.......................................................................................................................18

Known Issues................................................................................................................................................19 Web Application Format Generated by the Wdeploy predeploy Command ...............................................................19 Web Services with Separate Web and Web Application Servers...............................................................................19 Web Service Validation..............................................................................................................................................19 The Map Analytic Cannot be Viewed Via a BEA WebLogic Server ...........................................................................19

Related Content................................................................................................................................................20 Copyright...........................................................................................................................................................21



Deployment Scenario

Deployment Overview

This deployment scenario is a typical N-tier environment which involves the following: Client Tier: Web browser

Web Tier: HTTP server (Apache 2.2) and Web application server (WebLogic 10) are on different machines. BusinessObjects web applications are divided into static and dynamic contents. Static contents go to Apache 2.2 and dynamic content are deployed to WebLogic.

Server Tier: One machine hosting BusinessObjects Enterprise XI 3.0

Data Tier: One machine with existing database server. The database server hosts the CMS database.

Overview of Deployment

Instead of deploying all the web applications to one web application server, you can deploy the static content such as html or images to a web server, and then dynamic content such as .jsp or .asp pages of your web application to an application server.

In BusinessObjects Enterprise XI 3.0, a tool named wdeploy is included that provides the functionality to split the static and dynamic web applications and deploy them to a web server and web application server. The wdeploy command-line tool is included with BusinessObjects Enterprise to assist you in the command-line deployment of WAR files to your web application server. You can choose to deploy all web application resources together on a single web application server (standalone mode), or to separate dynamic and static content for deployment onto de-paired web and web application servers (distributed mode). This document describes exact Wdeploy commands you need to use to:

• Separate the BusinessObjects war files to static and dynamic contents

• Deploy dynamic contents to WebLogic 10 application server

• Deploy static contents to Apache 2.2 web server

For detailed information about the usage of Wdeploy, refer to BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide for Windows and Deploying BusinessObjects Enterprise Web Applications Using wdeploy which can be downloaded from

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


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


Recommended Hardware Requirements

Machine CPU RAM Hard disk space

Box 1 – BusinessObjects Enterprise 2.0 GHz Pentium 4-class processor and above

2 GB RAM 6 GB hard disk space

Box 2 – WebLogic 10 2.0 GHz Pentium 4-class processor and above

2 GB RAM 2 GB hard disk space

Box 3 – Apache 2.2 2.0 GHz Pentium 4-class processor and above

1 GB RAM 512 MB hard disk space

Recommended Software Requirements

Software Version

BusinessObjects Enterprise XI 3.0

WebLogic web application server 10.0

Apache web server 2.2.4

SUN JDK 1.5

Configuration Instructions This deployment scenario is a special web applications deployment. Therefore, the configuration instructions in this document focus on the web- and server-tier setups.

Sever Tier Configuration

Pre-requisites 1. Database server is installed on Box 0 and table spaces are created for CMS database and auditing

databases. 2. Database driver and database client are installed and configured on Box 3. The communication from

Box 3 to the database on Box 0 in data tier is confirmed.

Install Business Objects on Box 1 1. Launch BusinessObjects Enterprise XI 3.0 installer and select the language for your installation. It is

recommended to have the Create log file during installation option selected to generate detailed installation log files.

2. Accept the license agreement and click Next. 3. Type the key code and click Next. 4. Choose language packs and then click Next.



5. Click New and install to the default destination folder C:\Program Files\Business Objects. This setup

uses the CMS database on the data‐tier machine; therefore, select Use an existing database server.

6. Specify the CMS port number (6400 by default) and type the Administrator account password

Note: Ensure that the port that you assigned to the CMS is not used by other applications.



7. On the Server Intelligence Agent dialog box, use the default Node name and port number.

Note: Please make sure the port that you assigned to CMS is not using by other applications.

8. On the CMS Database Information dialog box, select a database type from the Select existing CMS

database drop-down list. Provide all the required information for the database in the fields provided in the CMS Database pane.

9. If you want to enable the Auditing, select the Auditing Database option and type the auditing database information on the right side. The auditing database can use the same table space of the CMS database or it can be on a totally different database.



10. On the Select Web Application Server dialog box, install Tomcat as your application server. Although

the target web applications deployment separates the web and web application servers, it is recommended that you install Tomcat with InfoView and the Central Management Console in order to check the server status after the installation.

11. Accept the default values or specify new port numbers for Connection port, Shutdown port, and

Redirect port for Tomcat and then click Next.



12. Click Next to start the installation process and then click Finish when the installation is completed.

Web Tier Configuration

WebLogic 10 Web Application Server on Box 2

Install WebLogic 10 Web Application Server 1. Launch WebLogic 10 installer and then accept the license agreement. 2. Choose BEA Home Directory (recommend to use the default BEA Home Directory C:\bea).

3. Select Complete install type, clear the Mercury profiling tools option unless it is required for your

development environment, and then click Next. 4. Choose the product installation directories. (It is recommend to use the default product home

c:\bea\wlserver_10.0 and workshop for WebLogic platform c:\bea\workshop_10.0)



5. Accept the default All Users Start Menu Folder and then click Next. 6. Clear the Run Quickstart option box and click Done after the installation is complete.

Create a WebLogic User Project domain 1. Launch WebLogic Configuration Wizard from Start ‐> Programs ‐> BEA Products ‐> Tools ‐>

Configuration Wizard.

2. In Configuration Wizard, select Create a new WebLogic domain, and click Next.



3. In the Select Doman Source dialog box, click Next with the default option selected.

4. Enter username and password for the Administrator account to access weblogic administrator console

and click Next. (For example: User name: weblogic; User password: weblogic).

5. Click Next on the Configure Server Start Mode and JDK dialog box.



6. Click Next on the Customize Environment and Services Settings dialog box with the No option selected. 7. Enter your domain name such as “BOXIR3” and keep default domain location

asC:\bea\user_projects\domains. 8. Click the Create button.

9. Click Done when the domain creation is finished. Your domain name is available under Start ‐> Program

‐> BEA Products ‐> User Projects.

Start Admin Server and logon to Admin Server Console 1. Go to Start ‐> Program ‐> BEA Products ‐> User Projects ‐> <domain_name> and click Start Admin

Server for WebLogic Server Domain. A command console will be launched and wait until you see <Server started in RUNNING mode>.

2. Launch Admin server console from: Start ‐> Programs ‐> BEA Products ‐> User Projects ‐> <domain_name> ‐> Admin server Console. Or you can open an browser and type the address http://localhost:7001/console/


http://localhost:7001/console/


3. In the Admin console webpage, login with the username and password you configured in step 4 of

“Create a WebLogic User Project domain”.

Configure Apache 2.2 HTTP Server on Box 3

Install Apache 2.2 HTTP Server 1. Launch Apache HTTP Server 2.2.4 installer for Windows.



2. Accept the license agreement.

3. Click Next in Read This First dialog. 4. Keep the default settings in the Server Information dialog and click Next.

Note: make sure the port 80 is not using by other application. If you have other web server such as IIS installed on the same machine, make sure that server is turned off.

5. Select Typical install type 6. Install Apache 2.2 to the default location: C:\program files\Apache Software Foundation\Apach2.2



4. Click Install and then click Finish when installation is completed.

Start Apache 2.2 HTTP server 1. After installation, the Apache icon will appear on the right bottom of your desktop on status bar.

2. Double‐click the Apache icon, open the Apache Service Monitor. You can start/stop/restart the Apache

HTTP server from the Apache Service Monitor.

3. To validate if Apache HTTP server is working properly, open a browser and type in the address bar:

http://localhost ,you should see the web page presenting “It works!”


http://localhost/


Bridge the WebLogic 10 with Apache 2.2

Installing the Apache HTTP Server Plug-In for WebLogic 1. On Box 2, locate Apache HTTP Server Plug‐In module mod_wl_22:

C:\bea\wlserver_10.0\server\plugin\win\32. 2. Copy it to a shared location that can be accessed from Box 3. 3. On Box 3, verify that the WebLogic Server Apache HTTP Server Plug‐In mod_so.c module is enabled by

the following commands:

i. Open a command console and type the following and then press <Enter>.

cd “C:\Program Files\Apache Software Foundation\Apache2.2\bin”

ii. Type command httpd –l, you should see mod_so.c in the list

4. On Box 3, install the Apache HTTP Server Plug‐In module for Apache 2.2.x by copying the mod_wl_22.so

file to the C:\Program Files\Apache Software Foundation\Apache2.2\modules directory 5. On Box 3, adding the following lines to your end of C:\Program Files\Apache Software

Foundation\Apache2.2/conf/httpd.conf file manually:

LoadModule weblogic_module modules/mod_wl_22.so <IfModule mod_weblogic.c> WebLogicHost Box 3 WebLogicPort 7001 MatchExpression * </IfModule>

6. On Box 3, verify the syntax of the APACHE_HOME\conf\httpd.conf file with the following command:

httpd -t

The output of this command reports any errors in your httpd.conf file or returns “Syntax OK”. 7. On Box 2, restart WebLogic Server. 8. On Box 3, restart Apache HTTP Server. 9. Test the plug‐in by opening a browser and type the following to display the WebLogic admin console:

http://Box 3/console


http://box3/console


10. On Box 3, adjust the MatchExpression in C:\Program Files\Apache Software

Foundation\Apache2.2/conf/httpd.conf for the deployment to separated web server and web application server:

<IfModule mod_weblogic.c> WebLogicHost Box 3 WebLogicPort 7001 MatchExpression *jsp </IfModule>

11. On Box 2, restart WebLogic Server. 12. On Box 3, restart Apache HTTP Server.

Deploy to http server and application server are on separated machines

Pre-requisites 1. Ensure the WebLogic 10 server is up and running on Box 2 2. JDK 1.5 is installed on Box 2 3. JAVA_HOME is set to the JDK 1.5 install location 4. Ensure the Apache 2.2 web server is up and running on Box 3

Copy Over the Wdeploy Tool to Box 2 1. On Box 2, create directory C:\BOXIR3. 2. Copy the whole folder deloyment under C:\Program Files\Business Objects\ on Box 3 to C:\BOXIR3\ on

Box 2 3. On Box 2, go to C:\BOXIR3\deployment\workdir, delete all the content under this directory

Copy Over the War Files And Configuration Files to Box 2 1. Copy the whole folder applications under C:\Program Files\Business

Objects\BusinessObjects\Enterprise 12.0\java\ on Box 3 to C:\BOXIR3 on Box 2. Now you will have C:\BOXIR3\applications

2. Copy the whole folder C:\Program Files\Business Objects\caf from Box 3 to C:\BOXIR3\ on Box 2.

Special Configuration for Performance Management 1. On Box 2, create folder Performance Management 12.0 under C:\BOXIR3 and copy the

InitConfig.properties from C:\Program Files\Business Objects\BusinessObjects\ Performance Management 12.0\ on Box 3 to that folder

2. On Box 2, go to C:\BOXIR3\applications, extract PerformanceManagement.war 3. Set the af.configdir parameter in theweb.xml file to the location of the InitConfig.properties file.The

web.xml file is located in: PerformanceManagement\WEB‐INF. The modified file should look like the example below.

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



4. Repackage PerformanceManagement.war.

Use Wdeploy to Separate the Static and Dynamic Content on Box 2 1. Locate the wdeploy configuration files for Apache and at C:\deployment. 2. Edit config.weblogic10:

as_admin_port=7001 as_admin_username=weblogic #as_admin_password= as_instance=AdminServer as_dir=C:\bea\user_projects\domains\BOXIR3

Note: It is recommended that not to store the password for weblogic admin console to the configure file. You can pass the as_admin_password to Wdeploy when execute the Wdeploy command.

3. Edit config.apache:

ws_dir= C:\program files\Apache Software Foundation\Apach2.2 connector_type=weblogic10 deployment_dir= C:\program files\Apache Software Foundation\Apach2.2\htdocs

Note: Use the install location of Apache 2.2 on Box 3 for Wdpeloy to configure the static and dynamic content and configuration files for HTTP server. “” should not be used in the ws_dir and deployment_dir.

4. Run the following command in Windows command console to generate static content for the Apache 2.2 web server and dynamic content for WebLogic 10 application server.

cd C:\BOXIR3\deployment wdeploy.bat weblogic10 -Das_mode=distributed -Dws_type=apache –Dwar_dir=C:\BOXIR3\applications –Das_admin_password=weblogic predeployall >> wdeploy.log

You can find the dynamic content in: C:\BOXIR3\deployment\workdir\weblogic10\application. Static content is located in: C:\BOXIR3\deployment\workdir\weblogic10\resources.

Deploy The Dynamic Content To Weblogic 10 Application Server 1. Run the following command in Windows command console

wdeploy.bat weblogic10 -Das_mode=distributed deployonlyall ––Das_admin_password Dwork_dir=C:\BOXIR3\deployment\workdir >> wdeploy.log

2. Launch WebLogic online admin console and login. In the Domain Structure window, navigate to BOXIR3 ‐> Deployments, you should see all the BusinessObjects web applications listed in the Deployments list in the right panel of the admin console.

<weblogic_dep_1>

Deploy The Static Content to Apache 2.2 HTTP Server 1. On Box 2, locate the static web applicaiton content at

C:\BOXIR3\deployment\workdir\WebLogic10\resources. 2. Copy the *.zip from Box 2 to C:\program files\Apache Software Foundation\Apach2.2\htdocs on Box 3 3. Extract the *.zip to the folder with the same name as zip file. 4. Delete the *.zip files



5. On Box 2, locate the bobj.<app.lication>.conf files at C:\BOXIR3\deployment\workdir\WebLogic10\resources

6. Copy the bobj.<application>.conf from Box 2 to C:\program files\Apache Software Foundation\Apach2.2\conf folder on Box 3

7. Update Apache httpd.conf under C:\program files\Apache Software Foundation\Apach2.2\conf with the application config files. For each web application, you must include an entry in httpd.conf. For example, to include AnalyticalReporting type

Include conf\bobj.AnalyticalReporting.conf

8. Restart Apache web server 9. Launch InfoView and CMC from the deparied web server and web application server:

http:\Box 3\InfoViewApp http:\Box 3\CmcApp

Configure the CMS name for InfoView

If you want to configure your InfoView to connect to a CMS other than the one installed on Box 1, what you can do is on Box 2, before your run the Wdeploy command to split the static and dynamic contents, perform the following steps. 1. Extract the InfoViewApp.war from C:\BOXIR3\applications folder to a temporary folder 2. Modify the following param‐value in the web.xml under WEB‐INF directory according to the parameter

values of CMS_name, CMS_visibility, Auth_name and Auth_visibility passed to the Wdpeloy command line:

         <context-param> <param-name>cms.default</param-name> <param-value>MyCMS:6400</param-value> </context-param>   <context-param> <param-name>cms.visible</param-name> <param-value>false</param-value> </context-param>   <context-param> <param-name>authentication.default</param-name> <param-value>secEnterprise</param-value> </context-param>  



<context-param> <param-name>authentication.visible</param-name> <param-value>false</param-value> </context-param>

3. Repackage the war file 4. Follow the steps in Use Wdeploy to separate the static and dynamic content on Box 2 in this document.

If you already finished the whole deployment, you can uninstall the InfoViewApp.war from your WebLogic admin console, and repeat the step 1 to 3 to the InfoViewApp.war under C:\BOXIR3\deployment\workdir\weblogic10\application. And then redeploy that war file to weblogic 10 using the admin console.

Known Issues

Web Application Format Generated by the Wdeploy predeploy Command

Deployable web applications for WebLogic are in the following format in the wdeploy workdir folder: • WebServices (ProcessBI and dswsbobje) are folders • AnalyticalReporting and PerformanceManagement are EAR files • Rest of WebApps are WAR files If you want to manually deploy dswsbobje.war to WebLogic using the admin console, you must deploy the folder instead of the war file. Otherwise web services applications may display the error message “An XSD Exception occurred”.

Web Services with Separate Web and Web Application Servers

If you have deployed Web Services to separate HTTP server and web application servers, you may encounter a NullPointer exception when launching a web services URL. The deployment to separate web and web application servers is currently not supported for Web Services.

Web Service Validation

Live Office or Query as web services (QaaWs) may not validate users if the web service address provided points a WebLogic server. This issue can be resolved by manually depolying the dswsbobje war file. To deploy dswsbobje correctly on a WebLogic 9.2 server, system administrators need to: 1. Deploy dswsbobje in exploded directory format and not as a .war file. 2. Create a Web logic xml file with the following lines:

<weblogic-web-app> <container-descriptor> <prefer-web-inf-classes>true</prefer-web-inf-classes> </container-descriptor> </weblogic-web-app>

3. Place xml file in the dswsbobje WEB‐INF directory. For more information see http://ws.apache.org/axis2/1_2/app_server.html

The Map Analytic Cannot be Viewed Via a BEA WebLogic Server

You cannot view a Map analytic via a BEA WebLogic Server® unless you manually extract the optimap folder from the PerformanceManagement.war file in Web-Inf/Classes/ and place the folder at the root directory of the machine on which Performance Manager is installed.


http://ws.apache.org/axis2/1_2/app_server.html


Related Content BusinessObjects Enterprise Product Portal

Configuring BusinessObjects Enterprise XI 3.0 with Complex NAT Networks

BusinessObjects Enterprise XI 3.0 Administrator's Guide


https://www.sdn.sap.com/irj/boc/enterprise

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00584b41-c2e1-2b10-5088-eb429a10cdea

http://sdnweb.sdn.sap.com/sdncss/uploadedFiles/https___sa_11282008122710PM_v1.pdf



Copyright © 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, 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 express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

These materials are provided “as is” without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages.

Any software coding and/or code lines/strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

Documents

BusinessObjects Web Applications Deployment Guide · 2019. 11. 12. · BusinessObjects Web Applications Deployment Guide . Applies to: SAP BusinessObjects Enterprise XI 3.0 . Summary