SAP Portal深度解析：开发与实施指南

5星 · 超过95%的资源需积分: 30 22 浏览量更新于2024-08-01 3 收藏 8.48MB PDF 举报

"SAP Portal是SAP公司提供的一款企业级门户解决方案，用于集成各种业务应用，提供统一的访问入口和个性化用户体验。SAP NetWeaver 2004s是其核心平台，支持开发、实施和部署SAP Portal。这份Developer’s Guide详细介绍了如何运行一个企业门户，并提供了版本1.70的文档，发布于2006年3月。文档可能包含对SAP AG及其他软件供应商的专有软件组件的描述。" 在深入理解SAP Portal之前，我们首先需要了解SAP作为全球领先的企业软件提供商的角色。SAP Portal是SAP NetWeaver技术栈的一部分，它允许用户通过单一登录系统访问企业内部的各种应用、数据和服务，从而提高效率和协作。SAP NetWeaver作为一个集成平台，提供了开发、运行和管理SAP应用程序所需的基础设施。在SAP Portal中，"开发"环节涉及创建和定制门户内容，如信息页面、工作流和用户界面。这通常涉及到使用SAP提供的开发工具，如WebDynpro，用于构建动态的、交互式的Web应用，以及Portal Content Management (PCM) 工具来管理和组织门户内容。 "实施"阶段涉及将SAP Portal配置到企业的IT环境中，包括设置用户权限、安全策略、集成其他SAP或非SAP系统、以及调整性能参数以满足特定需求。这个过程需要对企业的业务流程有深入了解，以便正确地配置门户以支持这些流程。 "部署"是指将SAP Portal解决方案上线并进行持续的维护。这包括定期更新、性能监控、故障排查和用户支持。SAP Portal的部署可以选择在本地服务器上，也可以利用云服务，如SAP Cloud Platform，提供更高的灵活性和可扩展性。文档提到的“Enterprise Portal”是SAP Portal的一个关键组件，它为企业提供了一个集中的信息中心，员工可以在这里访问内部邮件（如Microsoft Outlook）、报表、业务流程和其他关键信息。此外，SAP Portal还支持个性化，用户可以根据自己的角色和职责定制门户视图。该文档可能涵盖了以下主题： 1. SAP Portal的基础架构和组件 2. 安装和配置SAP NetWeaver 2004s 3. 开发和定制门户内容 4. 集成SAP和其他非SAP系统 5. 用户管理与安全性 6. 性能优化和监控 7. 故障排除和维护 8. 与第三方技术（如Microsoft、IBM、Oracle等）的互操作性由于文档已注明版权，这里没有提供具体的章节内容，但上述概述了SAP Portal的主要方面和开发者可能遇到的关键任务。对于想要深入研究SAP Portal的企业和个人，这份文档无疑是一份宝贵的参考资料。

Getting Involved March 2006

Portal Runtime

Running an Enterprise Portal 11

1.1.1.4.1.2 Components

The <components> element defines the portal components that are part of this application,

and includes configuration information for each. The element includes one or more

<component> elements, each of which defines one portal component.

The following is an example of a <components> element:

<component-config>

<property name="ClassName"

value="com.sap.portal.MyComponent"/>

</component-config>

<component-profile>

</component-profile>

</component>

</components>

Each <component> element contains a name attribute, which defines the name of the

component.

Each <component> element contains the following elements:

● <component-config>: Provides static configuration that cannot be changed by an

administrator or personalized by an end user.

The following are standard properties for component configuration:

Name Description

AuthRequirement

The initial minimal authentication needed to execute the

component. This property is supported for backward compatibility

only.

The property can be one of the following values:

● User: Authenticated user

● Admin: Administrator

● None: Anonymous user

● <role list>: Users with the listed role

ClassName

The name of the implementation class of the portal component.

ComponentType

The type of component, which can be one of the following:

● servlet

● jspnative

The property is not required. If blank, an implementation of

IPortalComponent must be specified by the ClassName

property.

JSP

If ComponentType is set to jspnative, this property specifies

the path of the JSP page that implements the portal component.

This path is relative to the PORTAL-INF folder).

Getting Involved March 2006

Portal Runtime

Running an Enterprise Portal 12

ResourceBundleName

The name of the component’s resource bundle, which is used to

store localized text strings.

The resource bundle should be placed in the /PORTAL-

INF/private/classes folder.

Specify the resource without the .properties extension but

include the file in the PAR with the extension.

SafetyLevel

The safety level for the component.

For more information, see Permission Model [Page

26].

● <component-profile>: Provides configuration that can be changed by an

administrator or personalized by an end user. For each property, different values can

be set for each iView derived from the component, and for each end user (if

personalization is permitted).

The following are standard properties for a component profile:

Name Description

ALLOW_BROWSER

Indicates whether the portal uses the browser cache to render the

component. The value can be one of the following:

● Yes: The content is stored in the browser cache and in

the PRT cache.

● No: The content is stored in the PRT cache, but not in the

browser cache.

● BrowserCache: The content is stored in the browser

cache, but not in the PRT cache.

CachingLevel

The scope of the cache, which can be one of the following:

● Shared: The cache content is shared among all users.

● User: The content is private for each user.

● Session: The content of the component is cached for the

(servlet) session, whether or not a user is connected. This

level is used to cache information related to the browser's

sessions.

EPCFLevel

Indicates whether the enterprise portal client framework (EPCF) is

used.

If two or more embedded iViews with different EPCFLevel values

are rendered on a page (within the same frame), the effective level

is computed as the maximum of all EPCFLevel values on the

page.

The property can have the following values:

● 0: This component does not use EPCF. Neither scripts nor

applets are included.

● 1: This component uses all EPCF features implemented

with pure JavaScript.

● 2: This component uses all EPCF features implemented

with pure JavaScript and applets.

The default value is level 2.

Getting Involved March 2006

Portal Runtime

Running an Enterprise Portal 15

ClassName

The name of the implementation class of the portal service. This class must

implement the IService interface.

startup

If set to true, the service is started at when the portal is started. If set to

false or left blank, the service is started on demand.

Each <service> element can also contain a <service-profile> element that provides

custom properties that can be modified by the system administrator.

There is only one set of values for these properties of a service.

1.1.1.4.1.4 Registry

The <registry> element defines any entries to be added or modified in the registry.

The following is an example of a <registry> element:

</registry>

The <registry> element can contain one or more <entry> elements, each of which

defines one of the following:

● Registry Entry: A key-value pair. The entry is placed in the path specified by the

registry subcontext specified by the path attribute. The key is the final part of the path

attribute and the value is specified by the name attribute.

For example, the following creates the key myTransformer with the value

TransformerProvider in the subcontext runtime/transformers:

<entry path="runtime/transformers/myTransformer"

name="TransformersProvider" type="service"/>

Any other values specified in the entry are attributes of the registry entry. In the

example above, type is an attribute of the TransformersProvider entry with the

value service.

● Registry Subcontext: A new subcontext to be created in the existing registry

subcontext specified by the path attribute. The type attribute must be subcontext.

The following creates the subcontext transformers in the runtime registry

subcontext:

1.1.1.4.1.5 Deployment Descriptor Example

The following is an example of a deployment descriptor (portalapp.xml) file for an

application that contains one portal service and one portal component.

<application-config>

</application-config>

<component-config>

<property name="ClassName"

剩余902页未读，继续阅读

willisaway

粉丝: 2
资源: 10

SAP Portal深度解析：开发与实施指南

SAP portal

SAP Portal（EP）的菜单和权限配置及操作手册

sap portal

sap portal安装手册

SAP Portal权限配置手册

基于.Net的SAP Portal开发

SAP Portal 7.3 性能优化 Performance Tuning

SAP Enterprise Portal Fundamentals

SAP_PORTAL概述.pdf

EP200 SAP Enterprise Portal System Administration

最新资源