SAP Web Dynpro 开发入门指南

需积分: 32 119 浏览量更新于2024-07-25 收藏 926KB DOC 举报

"SAP中文帮助文档提供了关于SAP Web Dynpro Java的详细指南，涵盖了从安装、技术前提到开发环境设置、有用工具的介绍，以及Web Dynpro的基础知识、学习路径和项目架构与命名规范。" SAP Web Dynpro是SAP提供的一种企业级应用程序开发框架，特别适用于构建复杂的、业务导向的用户界面。这个框架基于模型-视图-控制器（MVC）设计模式，旨在提高开发效率并提供高度的可维护性和可扩展性。在文档的"Prerequisites"部分，它讨论了安装Web Dynpro的步骤和技术前提。这包括对安装过程的概述，以及确保具备运行Web Dynpro所需的技术条件，如NetWeaver平台和NetWeaver Developer Studio。NetWeaver Developer Studio是用于Web Dynpro开发的主要集成开发环境（IDE），需要正确配置以支持Web Dynpro开发。文档还提到了一些有用的工具，例如Software Development Manager (SDM)用于管理项目，Visual Administrator用于监控和配置系统，以及其他辅助工具。这些工具对于开发过程中的版本控制、性能优化和问题排查至关重要。在"NetWeaver Developer Studio"章节中，详细介绍了各种视角、视图和编辑器的使用，如Web Dynpro透视图、Web Dynpro浏览器、图解视图、大纲视图、编辑窗口和属性窗口，这些都是开发者日常工作的核心组成部分。文档深入解释了Web Dynpro的基本原理，特别是MVC架构。模型（Model）负责存储和管理数据，视图（View）呈现数据，而控制器（Controller）处理用户交互，协调模型和视图的更新。此外，文档为初学者提供了学习路径的建议，包括SAP内部提供的教程、虚拟课堂、NWDS（NetWeaver Developer Studio）的帮助、SAP Developer Network (SDN)论坛，以及专门针对Java的Web Dynpro资源，帮助开发者进一步提升技能。在"Architecture of a WD project and naming convention"一节中，文档详细阐述了Web Dynpro项目的结构，包括根节点、Web Dynpro项目、字典、源代码文件夹、应用程序、Web Dynpro组件、组件使用、组件接口和视图组装。这些内容对于理解和组织Web Dynpro开发项目至关重要，特别是对于理解组件间如何交互以及如何定义和实现用户界面逻辑。这份SAP中文帮助文档为SAP Web Dynpro Java的开发者提供了一套全面的参考，无论他们是初学者还是经验丰富的专业人士，都能从中获益匪浅。

The third important thing for developing Web Dynpro applications is the testing

environment in this case would be the J2EE engine as a part of the SAP Web AS [Application

Server]. You probably need to install a local J2EE engine, and you will have a central server

for testing.

The developing environment and the testing environment at SAP are called SAP

NetWeaver Developer Workplace. If you have not installed everything you need, you could

install it from the following link: http://intranet.sap.com/installation.

After installing, you would need to adjust some settings (see chapter 3.4) and get familiar

with some useful tools.

You also need a browser. You could install Internet Explorer 6.0 or higher or Netscape

Navigator 7.0 or higher.

4.2 Technical prerequisites

The full installation with the SAP DB, the J2EE engine and the Java tool requires about 800

MB RAM memory (to drive the engine and the NWDS), 1.5 GB free hard-disk space and

Pentium 4 Processor and 1.5 GHz processor power. If you do not fulfill these requirements

you will not be able to perform properly.

You would probably need this much hard-disk place, because if you install the J2EE

engine an instance of the SAP database will be installed too. That is needed as a persistence

layer for the engine.

4.3 NetWeaver und NetWeaver Developer Studio

If you are not familiar with NetWeaver I yould give a short

introduction here.

Developers at SAP usually work in larger teams.

Therefore the most common approach for our Java developers

is to have a local developing environment and a local testing

environment as well as a central test environment. As you

probably know this approach delivers benefits, which are

having a shorter correction cycle and for avoiding

inconsistencies between local developers. Therefore, you

would have to develop a project locally.

The central testing environment checks if the components

work together. A component should work as if it is expected

according to its interface. If components do not work

together, you will receive warnings or errors. If you prevent to

access on changed codes locally and guarantee that your

codes work with the existing interfaces and components, you will not have problems running

this changed code in the complete testing environment. Therefore you integrate the changing

codes after proving into the central testing environment.

1) The developing environment is provided by the SAP NWDS [NetWeaver Developer

Studio]. It provides the designing time environment for Web Dynpro Applications. Web

Dynpro tools are plug-ins of the Open-Source Project Eclipse. NWDS is usually installed at

C:\Program Files\SAP\JDT\eclipse at SAP.

2) The testing environment is the Web Dynpro runtime environment that is one part of the

SAP J2EE engine in the SAP Web AS [Application Server] or Application Platform in the

SAP NetWeaver. J2EE engine is sometimes called Java stack or SAP Web AS stack (see

Figure 4).

3) In most cases, your central testing environment has already existed. For IB these are for

example SAP systems like BXI or BXT

Figure 4

- SAP Web AS within

SAP NetWeaver

4.4 NetWeaver Developer Studio settings

In general you can configure a plug-in if it is required through Window → Preferences →

“relevant selction in the tree”.

If you have installed everything correctly you still have to select the J2EE server in the

NWDS (Windows → Preferences → SAP J2EE engine → select SAP J2EE engine is installed

on local host.)

Next thing you have to know is that your default workspace is saved under C:\Documents

and Settings\All Users\Documents\SAP\Workspace. That is where your project will be saved.

If you will use perforce and develop within IB [Integration Builder] then you must change

the workspace into C:\p4\tc\aii\dev\DevWorkplace\ECSetup\workspace.

In general you have to be careful with giving names of elements that generate files. WD

may generate files with longer names. Length should not exceed 255 characters, which are the

limit of Windows. Be aware that the length can only be checked during design time, but not

during deploy time.

4.5 Useful Tools

SAP J2EE engine offers some useful tools for managing your engine.

4.5.1 SDM

The most needed tool is the SDM [Software Deployment Manager]. SDM is a client/server

application that enables you managing the (un-)deployment of software packages. It is the

standard tool for installing J2EE components on the J2EE engine. SDM has a graphical user

interface as a client.

The installation of this tool is usually done during the installation of the SAP Web AS and

is usually started when starting the engine. The SDM server runs on the SAP J2EE engine

side. The SDM Server must be installed and started on the host that you want to access

through a remote connection.

Normally the default user would be set to Administrator. At Web AS 6.40 from SP

[Support Package] 5, you would be allowed to enter a new password for the engine during the

installation. This option does not exist for upgrading with the patch procedure. You could

change the password using the SDM GUI. If you fail to login three times, the SDM server

would stop and you have to restart the engine or the SDM server manually.

The SDM stores data in the SDM repository and from there manages the archives and

recognizes dependencies between archives.

The SDM can deploy archives that are of the format of SDA [Software Deployment

Archive] or SCA [Software Component Archive]. SDAs are the smallest deployable

developing units in the programming languages except ABAP that are ZIP-compatible.

Web Dynpro produces the archive format EAR [Enterprise Archive-variant of

installation]. This is also an SDA file and in this case it is recognized as an SDA but not

renamed. The file <WDProjectName>.ear is stored in the corresponding WD project

directory. During the deployment SDAs and SCAs are deployed in the runtime environment

of the J2EE engine.

4.5.2 %Visual Administrator

The second important tool for managing your engine is the “Visual Administrator” which is a

part of the NetWeaver Developer Studio. You can execute it by the following file:

/usr/sap/<SID>(J2E)/JC<Instance Number>(00)/admin/go.bat (go.sh in Unix system). First,

you have to configure the connection from the Visual Administrator to the J2EE engine. You

also have to specify the properties of the users and the connections.

剩余36页未读，继续阅读

xb_xubin

粉丝: 0
资源: 3

SAP Web Dynpro 开发入门指南

SAP 帮助文档 中文版 资料比较齐全

sap ABAP帮助文件

SAP中文帮助文档

sap bopf 帮助文档

sap abap 在线中文文档

sap打印输出文档又退出sap

sapjco api文档

sap po 官方文档

SAP 搜索帮助重复

sap bpc官方中文在线支持文档

最新资源

SAP 帮助文档中文版资料比较齐全