SAP NETWEAVER PORTAL

SAP Netweaver Portal

Abstract

Today's enterprises face high costs and the complexity of implementing business-critical processes that are by nature distributed; run on heterogeneous infrastructure; and touch multiple parties including customers, partners, and suppliers. With ever-evolving changes in business, coupled with constant evolution of technology that promises increasingly efficient ways of doing business, enterprises running on traditional 3-tier infrastructures are migrating to distributed service-oriented platforms. SAP customers that have been running their business processes on traditional SAP R/3 Basis platforms are migrating to the SAP NetWeaver infrastructure and Enterprise Services Architecture (ESA) to gain business agility through distributed architecture. This paper discusses the impact of performance of creating users in SAP Netweaver Portal using different methods like ERP, etc, to find out that is it possible or not.

Table of Contents

ABSTRACTII

INTRODUCTION1

LITERATURE REVIEW3

EXPERIMENT17

RESULTS55

EVALUATION/CONCLUSION58

FURTHER WORK61

REFERENCES62

APPENDICES69

Introduction

The migration path for SAP customers will be evolutionary in nature. Although newer SAP applications are developed on top of the SAP NetWeaver platform, most business applications continue to reside on traditional platforms such as SAP R/3. SAP business processes implemented on the SAP NetWeaver platform typically also connect to traditional backends such as SAP R/3. Therefore, the products that can truly manage SAP business processes must be heterogeneous in their platform support, must cover both J2EE- and ABAP-based applications, and must be able to correlate traditional and non-traditional metrics into the overall business transaction the end user cares about. What does this mean for line of business (LOB), SAP application support, and quality teams? SAP application support and quality teams need to understand the effect of this heterogeneous environment on their existing business processes from the following perspectives: (Vladimir 2006:112-120)

Can their applications provide the needed functionality with reliability and performance?

Can they sustain service levels to customers through the migration path to SAP NetWeaver?

Can they test business processes end-to-end on both SAP NetWeaver and SAP R/3® before going live?

Can they leverage optimization techniques between testing and operations to ensure predictable business process performance in production?

Customers want solutions that allow them to manage heterogeneous infrastructures across the entire performance lifecycle. Performance lifecycle refers to best practices and constituent processes that ensure business process performance objectives are met before going live, and sustained during production. Mercury is the only vendor in the market that offers a complete performance lifecycle solution that is well-integrated with SAP's management infrastructure and can reduce customers' TCO in the following ways: Optimize customers' business processes running on heterogeneous SAP and non-SAP application environments. Leverage optimization techniques across the performance lifecycle — during pre-production and production — through integration with Mercury LoadRunner® and Mercury Business Availability Centre™ respectively. Reduce mean time to resolution (MTTR) of performance bottlenecks associated with complex business processes. (Peter 2002:16-54)

This paper discusses the impact of performance of creating users in SAP Netweaver Portal using different methods like ERP, etc, to find out that is it possible or not.

Literature Review

SAP Enterprise Portal is a component of the SAP NetWeaver platform that provides end users a single point of entry into enterprise information and distributed ...