SAP BO 4.0 Web应用部署Windows指南

需积分: 10 118 浏览量更新于2024-07-29 收藏 1.06MB PDF 举报

本资源是一份名为"SAP Business Objects Web application deploy on windows"的指南，针对的是SAP Business Objects Business Intelligence platform 4.0 Support Package 2011-10-11版本。该文档详细阐述了如何在Windows系统上部署SAP Business Objects Web应用程序，特别是对于SAP BOBJ (Business Objects Java)的相关组件和技术，如WebIntelligence、Xcelsius等。 SAP BOBJ WebAppDeploy是SAP Business Objects套件中的关键组件之一，它负责将业务智能应用程序打包并发布到不同的平台，确保在企业环境中的一致性和高效性。在Windows环境下部署时，可能涉及的步骤包括但不限于： 1. **环境准备**：首先，确保Windows系统满足SAP BOBJ WebAppDeploy所需的最低系统要求，这通常包括操作系统版本、Java运行环境（JRE）、内存和磁盘空间。 2. **Support Package安装**：从SAP官方下载适用于4.0版本的Support Package，这个包包含了必要的软件和配置文件，用于部署Web应用程序。 3. **工具和组件**：使用SAP Web Application Deployment Tool或Web IDE（Web Intelligence Development Environment）进行部署，这两个工具分别为命令行界面和图形化界面，方便开发者根据具体需求选择使用。 4. **应用程序构建**：确保源代码或应用程序包已经通过版本控制系统（如Git）管理，并遵循标准的开发流程，包括单元测试和集成测试。 5. **部署流程**：在WebAppDeploy过程中，需配置应用程序的部署目标，如目标服务器的URL、用户权限、数据源连接等。同时，可能还需要处理应用程序的打包、传输和解压。 6. **安全性**：考虑到数据安全和隐私保护，确保在部署过程中设置了合适的访问控制策略，包括身份验证、授权和审计功能。 7. **性能优化**：可能涉及到对Web应用程序进行性能调优，比如调整内存设置、缓存策略和并发用户限制，以提高系统的响应速度和稳定性。 8. **监控与维护**：部署后，需要监控Web应用程序的运行状态，定期更新补丁和修复可能存在的问题。此外，文档中也提到的其他产品如Sybase、SQLAnywhere等，如果在部署过程中涉及这些技术，也需要相应的管理和维护。 9. **版权和许可**：在阅读和使用这份文档时，请注意其中关于版权和商标的声明，确保遵守SAP和其他供应商的知识产权规定。这份文档提供了关键的信息和步骤，帮助用户在Windows平台上成功地部署和管理SAP Business Objects Web应用程序，确保业务流程的顺利执行和数据的高效分析。对于IT专业人员来说，这是提升业务智能应用部署能力的重要参考资料。

Description

Deployed au-

tomatically?

Web application archive

(may be WAR or EAR)

OSGi archive of core web applications, including:

• Analytical Reporting

• CMC

• SAP Crystal Reports

• BI launch pad (formerly InfoView)

• Eclipse IDE support

• Lifecycle Manager

• Monitoring

• OpenDocument

• BI workspace (formerly Dashboard Builder)

• Platform search

• Platform services

• Visual difference

• SAP Crystal Dashboard Design (formerly Xcelsius)

YesBOE

This web application is deprecated. It provides support for

legacy Crystal Reports web services and SDK components,

including:

• Crystal Enterprise

• Crystal Reports Report Application Server (RAS)

• SAP Crystal Dashboard Design (formerly Xcelsius)

• SAP BusinessObjects Analysis, OLAP edition (formerly

Voyager)

YesBusinessProcessBI

(deprecated)

Web Services components, including:

• Session

• BI platform

• BI catalog

• Federation Administration tool

• Live Office

• Web service query tool (formerly Query as a Web Ser-

vice)

• Publishing

• Report Engine

• SAP BusinessObjects Web Intelligence (formerly Web

Intelligence)

• SAP Crystal Dashboard Design web services (formerly

Xcelsius)

Yesdswsbobje

Java Server Faces support and examples.Nojsfplatform

2011-10-1116

Overview of web application deployment

The SAP BusinessObjects Business Intelligence platform installation program does not deploy the

MobileOTA14 web application that provides support for mobile applications.

To use mobile applications, you must deploy the MobileOTA14 archive (MobileOTA14.war or Mo

bileOTA14.ear) manually once the installation process is complete.

Note:

The WDeploy GUI tool cannot be used to deploy individual web applications. To deploy an individual

web application, such as MobileOTA14, use the WDeploy command-line tool.

Before deploying the MobileOTA14 web application, ensure that the WDeploy configuration file

config.<WEB_APPLICATION_SERVER> has been configured appropriately for your web application

server. See WDeploy configuration files.

Deploy the MobileOTA14 web application.

To deploy the MobileOTA14 web application, use the following WDeploy command:

wdeploy.bat <WEB_APPLICATION_SERVER>

-Dwar_dir=<LOCATION_OF_MOBILEOTA14.WAR>

-DAPP=MobileOTA14

deploy

For example, the following command deploys MobileOTA14 to a WebSphere 7 web application

server:

wdeploy.bat websphere7

-Dwar="C:\Program Files (x86)\SAP BusinessObjects\Mobile 14\Client"

-DAPP=MobileOTA14

deploy

Restart the web application server.

Access the following URL to ensure that the MobileOTA14 web application is working:

http://<HOSTNAME>:<PORT>/MobileOTA14

Substitute <HOSTNAME> for the web application server hostname, and <PORT> for the web application

server port number.

For more information on mobile products, refer to the

SAP BusinessObjects Mobile Installation and

Deployment Guide

2.3.2 To deploy OpenSearch.war for OpenSearch support

The installation program does not deploy the OpenSearch web application that provides support for

OpenSearch applications.

To use OpenSearch applications, you must deploy the OpenSearch.war archive manually once the

installation process is complete.

Note:

The WDeploy GUI tool cannot be used to deploy individual web applications. To deploy an individual

web application, such as OpenSearch, use the WDeploy command-line tool.

2011-10-1118

Overview of web application deployment

Ensure that web application server's connection details have been set in the WDeploy web application

server configuration file. The file is located in:

<BOE_INSTALL_DIR>\SAP BusinessObjects Enterprise XI

4.0\wdeploy\conf\config.<WEB_APP_SERVER>

For more information on the WDeploy web application server configuration file, see “Configuration

files” in the

SAP BusinessObjects Business Intelligence platform Web Application Deployment Guide

Update the OpenSearch configuration in the OpenSearch web application's config.properties

file. The file is located in:

<BOE_INSTALL_DIR>\SAP BusinessObjects Enterprise XI

4.0\warfiles\OpenSearch\WEB-INF

Ensure that the following parameters are configured for your server:

• cms: the CMS hostname and CMS port number. For example, use the format: <CMS_HOST

NAME>:<PORT>.

• opendoc: the URL of the OpenDocument web application. For example:

http://<WEB_APP_SERVER>:<PORT>/BOE/OpenDocument/opendoc/openDocument.jsp.

• proxy.rpurl: reverse proxy URL, if your organization uses a reverse proxy server.

• proxy.opendoc.rpurl: the OpenDoc reverse proxy server URL, if your organization uses an

OpenDoc reverse proxy server.

Deploy the OpenSearch web application.

To deploy the OpenSearch web application, use the following WDeploy command:

wdeploy.bat <WEB_APPLICATION_SERVER>

-Dapp_source_dir=<LOCATION_OF_OPENSEARCH_WEB_APP_SOURCE_TREE>

-DAPP=OpenSearch

deploy

For example, the following command deploys the OpenSearch web application to a WebSphere 7

web application server:

wdeploy.bat websphere7

-Dapp_source_dir="C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI

4.0\warfiles\OpenSearch"

-DAPP=OpenSearch

deploy

For more information on OpenSearch related products, refer to “OpenSearch” section of the

SAP

BusinessObjects Business Intelligence Platform Administrator Guide

2.4 Default context roots

All web applications can be deployed to a custom context root on your web application server. The

following table lists the context roots for each web application.

2011-10-1119

Overview of web application deployment

Context pathWeb application

/BOE/CMCCentral Management Console (CMC)

/BOE/BIBI launch pad

/BOE/OpenDocumentOpen Document

/BusinessProcessBICrystal Reports BI Processes (deprecated)

/dswsbobjeWeb Services

2.5 Custom root contexts and context paths

SAP BusinessObjects Business Intelligence platform web applications can be deployed to a custom

location on a web application server. This location is reflected in the URL used to access the web

application from a web browser, and is often known as the “context”.

A root context is the top-level folder on a web application server in which web applications are located.

The default root context for SAP BusinessObjects Business Intelligence platform web applications is

/BOE. For example, on a web application server named www.mycompany.com, the URL prefix used

to access web applications on the server would be http://www.mycompany.com/BOE/.

A context path (sometimes referred to as a virtual directory) is a folder within a root context, in which

a web application is located. For example, the default context path for the BI launch pad application is

/BI. The URL used to access the BI launch pad web application on a web application server named

www.mycompany.com would be http://www.mycompany.com/BOE/BI.

Both the root context and the context path can be changed to suit the needs of your organization. The

following table lists examples of deploying a web application named MyApp to different root and web

application context paths. The following topics describe how to customize root and web application

context paths.

2.5.1 To change the root context

You can change the root context used by SAP BusinessObjects Business Intelligence platform web

applications. The default setting is to have an empty root context, so the web application context path

is shown directly after the server address in a URL.

For example, an empty root context results in a URL such as http://localhost:8080/BOE/CMC,

where http://localhost:8080/ is the server and port number, there is no root context, and

BOE/CMC is the web application context path. Setting the root context to

MY_COMPANY

would change

the URL example shown above to http://localhost:8080/MY_COMPANY/BOE/CMC.

2011-10-1120

Overview of web application deployment

剩余127页未读，继续阅读

richardch

粉丝: 0
资源: 5

SAP BO 4.0 Web应用部署Windows指南

sap bo 开发文档

sap bo 9.3安装

"Plugin Output: Path : /opt/sapbo/bobje/tomcat7/bin/ Installed version : 7.0.27 Fixed version : 7.0.82"

sap gui770 win.zip

sap online help中文版

sap select left join on where

SAP Query、SAP ABAP、SAP BW

Python打开sap后怎么才能关掉这个应用程序

how to learn sap abap fast

python 打开 SAP ，进入 P79，然后进入 Mb51 命令

最新资源