Sappress Content Integration Sap Netweaver Portal

Bonn � Boston

Marty McCormick, Matt Stratford

Content Integration with SAP NetWeaver® Portal

226.book Seite 3 Freitag, 29. August 2008 4:26 16

Contents at a Glance

SECTION I

1 Introduction ........................................................................ 15

2 Federated Portal Network ................................................... 43

SECTION II

3 Business Package for Manager and Employee

Self-Services ........................................................................ 63

4 SAP Composite Application Resource and Portfolio

Management ....................................................................... 89

5 SAP NetWeaver Business Intelligence .................................. 117

6 SAP Supplier Relationship Management .............................. 169

7 SAP Customer Relationship Management ............................ 197

8 SAP ERP .............................................................................. 219

SECTION III

9 Managing a Content-Driven Architecture ............................ 243

10 Organizing and Administering Portal Content ...................... 283

11 Content Impacts to Portal Performance ............................... 307

12 Conclusion .......................................................................... 335

APPENDIX

A Configuration Steps ............................................................. 347

B The Authors ........................................................................ 381


7

Contents

Section I

1 Introduction ................................................................. 15

1.1 Book Overview ............................................................... 151.1.1 About This Book ................................................ 191.1.2 Our Goal in Writing This Book ........................... 231.1.3 SAP Supporting Information ............................... 241.1.4 Product Versions ................................................ 25

1.2 Evolution of SAP NetWeaver Portal ................................ 251.3 Portal Content Overview ................................................ 29

1.3.1 SAP Business Packages ....................................... 291.3.2 Delivered Composite Applications ..................... 341.3.3 Integration of Nondelivered SAP Content .......... 341.3.4 Integration of Non-SAP Content ........................ 37

1.4 SAP NetWeaver Composition Environment ..................... 381.4.1 SAP NetWeaver CE Architecture ........................ 391.4.2 SAP NetWeaver CE Tools ................................... 401.4.3 SAP NetWeaver CE and SAP NetWeaver Portal .. 41

1.5 Introduction Wrap Up .................................................... 41

2 Federated Portal Network ........................................... 43

2.1 Federated Portals Overview ............................................ 432.2 Federated Portal Usage Scenarios ................................... 46

2.2.1 Using FPN for Portal Content ............................. 472.2.2 When to Use an FPN ......................................... 492.2.3 Federated Portal User Persistence Stores ............ 512.2.4 Using FPN with Non-SAP Content ..................... 52

2.3 Content Integration Options ........................................... 522.3.1 Remote Delta Link (RDL) ................................... 532.3.2 Remote Role Assignment (RRA) ......................... 532.3.3 Remote Application Integration (RAI) ................ 54

2.4 Configuring a Federated Portal Network ......................... 552.4.1 Prerequisites ...................................................... 552.4.2 Configuration ..................................................... 562.4.3 FPN Usage Tips .................................................. 60


Contents

8

Section II

3 Business Package for Manager and Employee Self-Services ................................................................. 63

3.1 Business Content Integration .......................................... 633.1.1 Brief History ....................................................... 643.1.2 Employee Self-Service ........................................ 663.1.3 Manager Self-Service .......................................... 68

3.2 Configuration of the XSS Business Package ...................... 693.2.1 Installation Requirements ................................... 703.2.2 XSS Configuration Steps ..................................... 71

3.3 Architecture Impacts ....................................................... 743.3.1 Using FPN with XSS ........................................... 763.3.2 Deploying XSS to an Existing Portal .................... 773.3.3 SAP NetWeaver Dependencies ........................... 78

3.4 Development Impacts ..................................................... 803.4.1 Web Dynpro Implicit Personalization ................. 803.4.2 Web Dynpro Implicit Personalization Example ... 813.4.3 XSS Java Customization ...................................... 863.4.4 XSS ABAP Development ..................................... 87

3.5 Resource Requirements .................................................. 87

4 SAP Composite Application Resource and Portfolio Management ................................................................ 89

4.1 Business Content Integration .......................................... 894.1.1 Product Overview .............................................. 904.1.2 Portal Content for xRPM .................................... 92

4.2 Technical Architecture Considerations ............................. 934.2.1 Technical Components ....................................... 944.2.2 Deployment Options .......................................... 974.2.3 Landscape Considerations .................................. 1014.2.4 Landscape Configuration .................................... 104

4.3 Portal Configuration of xRPM Content ............................ 1074.3.1 Configuration Process Overview ......................... 1084.3.2 Configuration — Case Study ............................... 108


Contents

9

4.4 Development Impacts ..................................................... 1124.4.1 Modification of SAP-Delivered Screens .............. 1134.4.2 Custom Development Scenarios ......................... 113

4.5 Resource Requirements .................................................. 114

5 SAP NetWeaver Business Intelligence ......................... 117

5.1 Portal Content Integration .............................................. 1175.1.1 Product Overview .............................................. 1185.1.2 Portal Content for SAP NetWeaver BI ................ 119

5.2 Technical Architecture Considerations ............................ 1265.2.1 Deployment Options ......................................... 1265.2.2 Portal Landscape Considerations ........................ 1315.2.3 Seamless Federated Portal .................................. 133

5.3 Configuration of SAP NetWeaver BI Portal ...................... 1345.3.1 Installation Requirements .................................. 1345.3.2 Configuration Steps ............................................ 1355.3.3 Manual Configuration ........................................ 137

5.4 Development Impacts ..................................................... 1475.4.1 Query-Based iViews ........................................... 1485.4.2 Information Broadcasting ................................... 1525.4.3 Visual Composer ................................................ 1555.4.4 SAP NetWeaver BI and Custom Java

Development ..................................................... 1625.4.5 Development Wrap Up ...................................... 163

5.5 SAP and Business Objects ............................................... 1645.6 Resource Requirements .................................................. 166

6 SAP Supplier Relationship Management ..................... 169

6.1 Business Content Integration .......................................... 1696.1.1 Product Overview .............................................. 1706.1.2 Portal Content for SAP SRM ............................... 170

6.2 Technical Architecture Considerations ............................ 1756.2.1 UME Store Considerations ................................. 1806.2.2 Internal Portal .................................................... 1816.2.3 External Portal ................................................... 181

6.3 Portal Configuration of SAP SRM Content ....................... 1826.3.1 Internal Portal .................................................... 183


Contents

10

6.3.2 External Portal .................................................... 1856.4 Development Impacts ..................................................... 1936.5 Resource Requirements .................................................. 1936.6 Looking Forward — eSourcing and SAP SRM 7.0 ............ 194

7 SAP Customer Relationship Management ................... 197

7.1 Business Content Integration .......................................... 1977.1.1 Portal Integration with SAP CRM ....................... 1997.1.2 SAP CRM Business Packages ............................... 200

7.2 Configuration of SAP CRM Portal Content ...................... 2087.2.1 General Business Package Configuration ............. 2097.2.2 Detailed Configuration Example ......................... 210

7.3 Architecture, Development, and Resource Impacts ......... 2147.3.1 Architecture Impacts .......................................... 2147.3.2 Development Impacts ........................................ 2167.3.3 Resource Impacts ............................................... 217

8 SAP ERP ........................................................................ 219

8.1 Portal Content Integration .............................................. 2198.1.1 SAP-Delivered iViews ......................................... 2238.1.2 SAP-Delivered Business Packages ....................... 229

8.2 SAP Technical Architecture Considerations ..................... 2308.3 Portal Configuration of SAP ERP Content ........................ 2338.4 Development Impacts ..................................................... 2358.5 Resource Requirements .................................................. 238

Section III

9 Managing a Content-Driven Architecture ................... 243

9.1 A New Set of Challenges ................................................. 2439.2 Adobe Document Services .............................................. 247

9.2.1 Functionality Overview ...................................... 2479.2.2 Architecture Considerations ............................... 2499.2.3 Configuration ..................................................... 252

9.3 System Landscape Directory ............................................ 2599.3.1 Functionality Overview ...................................... 260


Contents

11

9.3.2 Architecture Considerations ............................... 2629.3.3 Configuration ..................................................... 267

9.4 SAP NetWeaver Development Infrastructure .................. 2689.4.1 Functionality Overview ...................................... 2689.4.2 Architecture Considerations ............................... 2729.4.3 Configuration Overview ..................................... 277

9.5 Wrap Up ........................................................................ 281

10 Organizing and Administering Portal Content ............ 283

10.1 Best Practices for the Portal Content Directory ............... 28310.1.1 PCD Overview ................................................... 28410.1.2 PCD Organization .............................................. 28510.1.3 PCD Permissions ................................................ 28910.1.4 Managing Content on Producer Portals .............. 289

10.2 Portal Change and Transport Management ..................... 29110.2.1 Portal Transport Process ..................................... 29210.2.2 Enhanced CTS+ and SAP NetWeaver Portal ........ 29410.2.3 Sample Transport Process Using Enhanced CTS+ 29610.2.4 CTS+ Architecture Considerations ...................... 29910.2.5 Configuration ..................................................... 301

11 Content Impacts to Portal Performance ...................... 307

11.1 Portal Content Directory Performance ............................ 30911.2 Caching .......................................................................... 310

11.2.1 Navigation Caching ............................................ 31111.2.2 Application Caching ........................................... 31111.2.3 Custom Object Caching ...................................... 313

11.3 Overall Performance Recommendations ......................... 31511.3.1 Tune the JVM .................................................... 31511.3.2 Enable Caching .................................................. 31611.3.3 Reduce Logging ................................................. 31611.3.4 Keeping a Light Landing Page ............................ 31711.3.5 Browser Settings ................................................ 318

11.4 Performance Tools and Problem Diagnosis ..................... 31811.4.1 Methodology ..................................................... 31911.4.2 Solution Manager Diagnostics ............................ 32211.4.3 Sherlok .............................................................. 324


Contents

12

11.4.4 SAP NetWeaver Administrator ........................... 32511.4.5 SAP NetWeaver Portal Monitoring Tools ............ 327

11.5 Federated Portal Performance ......................................... 33011.6 Content Performance Wrap Up ....................................... 333

12 Conclusion .................................................................... 335

12.1 All for a Seamless End-User Experience ........................... 33512.2 Key Points ...................................................................... 336

12.2.1 Federated Portals ............................................... 33712.2.2 Content Integration ............................................ 33712.2.3 Architecture and Landscape Impacts .................. 33812.2.4 Custom Development Practices .......................... 33912.2.5 SAP NetWeaver Landscape Considerations ......... 34012.2.6 Impacts to Content Administration ..................... 34112.2.7 Portal Performance ............................................. 341

12.3 Looking Forward ............................................................. 342

Appendix

A Configuration Steps ..................................................... 347

A.1 SSO Configuration Between the SAP NetWeaver Portal and the ABAP System ..................................................... 347A.1.1 Steps on the SAP NetWeaver Portal (Java Stack) . 348A.1.2 Configuration for SSO in the ABAP System ......... 350

A.2 SSO Configuration Between Two SAP NetWeaver Portals 354A.2.1 Export J2EE certificate ........................................ 354A.2.2 Configure Target J2EE for SSO ............................ 354

A.3 Creating a Portal System Object for a Backend ABAP System with System Alias ................................................ 357

A.4 iView Creation Process .................................................... 363A.5 Downloading, Deploying, and Running a Business

Package .......................................................................... 368A.6 Multiple Property Replacement ...................................... 376

B The Authors .................................................................. 381

Index ................................................................................................ 383


63

In this chapter, you’ll learn about the Business Package for Manager and Employee Self-Services (XSS). Although it’s one of the most widely implemented SAP Business Packages, it’s also one of the most challenging to implement. In addition to com-plex configuration, there is often confusion around the impacts relative to customization, development, and architecture.

3 Business Package for Manager and Employee Self-Services

After completing this chapter, you’ll be familiar with how to configurethe Business Package for Manager and Employee Self-Services (XSS) inSAP NetWeaver Portal. In addition, you’ll understand how to addressarchitecture and development challenges often experienced during anXSS implementation.

3.1 Business Content Integration

In terms of portal functionality, few business packages can offer as muchas the Business Package for Employee Self-Service (ESS) and ManagerSelf Service (MSS). They are often implemented in parallel, and manyconcepts relating to configuration, architecture, and development areconsistent across both business packages. Although these two businesspackages contain the portal content directory (PCD) content necessary,such as iViews and pages, the actual code is delivered in the form ofJava-based software components. The underlying technology used isWeb Dynpro Java, and there are several components that make up SAPSelf Services (XSS).

XSS componentsTechnically speaking, XSS consists of the following components, whichare delivered as software component archive (.sca) files:


Business Package for Manager and Employee Self-Services

64

3

� SAP MSS — SAP Manager Self-Service

� SAP ESS — SAP Employee Self-Service

� SAP ASR — SAP ERP HCM Administrative Services

� SAP PSS — SAP Project Self-Service

� PCUI — Floor Plan Manager (FPM)

The focus of this chapter is primarily ESS and MSS, although we’ll pointout the ASR or PSS components when appropriate. These componentsadhere to the Java-based SAP Component Model, and the last compo-nent in the list (PCUI) is the most vital to the others. PCUI is the centralWeb Dynpro component that provides the underlying framework for anapplication within ESS or MSS. As such, to implement MSS, ESS, ASR, orPSS you’ll always need to deploy the PCUI component. We’ll discussPCUI and the overall configuration framework for self-services later inSection 3.4, “Development Impacts.”

3.1.1 Brief History

XSS screens Before the release of SAP NetWeaver 6.40, the business packages for ESSand MSS were based on SAP transactions that were delivered in theform of Internet Transaction Server (ITS) services known as InternetApplication Components (IACs). ESS and MSS deployments included astandalone ITS infrastructure in addition to the SAP Enterprise Portaland backend SAP R/3 system. Because the screens were standard SAPtransaction screens, casual company users who were not used to SAPscreens and navigation components were required to learn it for self-ser-vices such as benefits, personal data, and so on. With the release of SAPERP 2004 (ECC 5.0) and the SAP NetWeaver 6.40 Java stack, SAP rede-signed the self-services application to be based on Web Dynpro.

As shown in Figure 3.1, the Web Dynpro-based XSS screens resemble amore traditional web-based look and feel that is often seen at commer-cial websites. This is highly beneficial because the self-service applica-

Note

Often, professionals in the SAP industry refer to XSS as a whole to include thebusiness package and the Java-based software components; we’ll do the samein this chapter.


Business Content Integration

65

3.1

tions within XSS are often used by casual SAP users who may not befamiliar with the intricate nature of traditional SAP screens. The emer-gence of the XSS business package has also resulted in the ability toleverage a large amount of functionality from your Java-based SAPNetWeaver systems.

For example, users can now work with SAP Interactive Forms usingAdobe Document Services (ADS), which is built into the SAP NetWeaver7.0 Java AS. In this section, we’ll provide an overview of the XSS func-tionality available to integrate into your SAP NetWeaver Portal. The ver-sions that we base our documentation on is a SAP NetWeaver 7.0 SPS 15system with ECC 6.0 backend.

Delivered portal content

In the next few sections, we’ll provide an overview of the SAPNetWeaver Portal content that is provided with the XSS business pack-ages. The functionality described in these sections highlights some ofthe commonly used areas of XSS but isn’t an exhaustive list. As always,consult the official, most recent SAP documentation for each businesspackage for detailed explanations.

Figure 3.1 Comparison of ITS and Web Dynpro iViews

Web Dynpro JavaITS IAC



66

3

3.1.2 Employee Self-Service

Within the ESS business package, iViews are grouped into several cate-gories, which are assembled together into portal worksets in the deliv-ery of the ESS application. Of course, these iViews can be assembledinto your own portal roles in a manner specific to your organizationalstructure. Figure 3.2 shows the main ESS page and the associated workareas or groups.

The Benefits and Payment applications allow employees to view infor-mation related to their benefits package, such as current and pastincome statements, retirement planning assistance, and health and den-tal benefit information. Users can update their benefit options, such asupdates to 401K contribution percentages. As the name suggests, thePersonal Information applications allow employees to update personaldata, such as addresses, phone number, bank information, and family-related information. The address book workset contains iViews thatenable employees to access certain personal information from otheremployees. In addition, they can make updates to their own informationin the corporate directory. One of the most sophisticated sets of applica-tions is the Life and Work Events functionality. In this area of ESS, userscan manage significant events such as changes to employment status orfamily events such as the birth of a child or divorce. In addition, various

Figure 3.2 Overview of ESS


Business Content Integration

67

3.1

important events are linked with tasks and supporting documentationnecessary to address each event.

The ability to trigger workflow-related processes specific to an employeeevent is highly configurable. In fact, placeholders to include customizedHTML content are included with each application, making it easier forcontent administrators to manage your company-specific documentsand distribute them to end users.

ExampleAs a drill-down example to the previous paragraph, Figure 3.3 showsthe Web Dynpro for Java-based Benefits and Payment iView. From thisiView, employees can manage their plan participation relative to bene-fits. Furthermore, during open enrollment, employees can use thisiView as the launch point to enroll or change their benefit plans. Weused this iView as an example because it’s often one of those pieces offunctionality that gets hit really hard once a year (i.e., the two weeksduring open enrollment) and has relatively low volume the rest of thetime. Thus, as a system architect or performance engineer, you shouldaccount for these peaks when sizing your environment. Also, as shownin Figure 3.3, this iView allows employees to check items related to theircompensation and access online pay statements — which is anotherpeak period as employees often check their pay statement once per payperiod, often as soon as they get in on payday.

Figure 3.3 ESS Benefits and Payment iView



68

3

ESS functionality The ESS business package is also used for a wide variety of work-relatedadministrative tasks. The Working Time application allows users to per-form actions related to functions such as time entry and leave requests.In addition, users can link time entry to specific tasks or SAP objects aswell as make corrections to previous time entered as they view thehours worked in a specific time period using a calendar graphical dis-play. Users can also trigger a leave request, which initiates approval pro-cesses that are actually linked to functionality delivered in MSS. Travelmanagement functionality is also included in ESS. iViews included inthe Travel and Expenses workset allow employees to perform tasks suchas entering expenses from business trips and submitting them forapproval. They can also create new trip requests and even book theirtravel plans for lodging and transportation. Authorized users can alsoperform travel functions for other users, which may be useful for secre-taries who work for executives who travel frequently for business. TheLearning and Career applications allow users to manage functions suchas internal job moves and updates to their skills profile. In addition,users can search for internal positions and save search profiles for futureuse. There is also functionality to apply directly for a desired position orrelease your candidate profile.

3.1.3 Manager Self-Service

The MSS business package contains applications that allow managerswithin various areas of an organization to perform several of theirrespective job functions through the SAP NetWeaver Portal. The appli-cations within MSS are organized by the type of operational role that amanager plays within an organization. As shown in Figure 3.4, MSS isorganized in worksets containing similar tasks relating to both genericHR functions as well as business-related activities such as project plan-ning and financial management.

MSS functionality The Team workset provides managers with a snapshot of various typesof information about their team and gives them the ability to executenearly a managerial task for one of their employees. Managers can viewand, in certain cases update, all employee-related HR data. In addition,this workset provides the ability to manage requests generated by ESSapplications, such as business trip or vacation requests. Recruiting


Configuration of the XSS Business Package

69

3.2

requests, headcount planning, and compensation management andplanning are also examples of functionality found in this workset.

The Budget workset gives managers insight into the finances at the orga-nizational entities in which they oversee or have a stake in. For example,this is where a manager could view how their respective cost center wasdoing at a given point in a quarter. In addition, costs related to assetssuch as computer-related equipment is available through the Budgetworkset. The Work Overview workset includes SAP-related items that amanager must complete. The Universal Worklist (UWL) is includedwithin this functionality.

MSS additional worksets

Several other worksets aren’t part of the MSS core but are often used be-cause they relate to manager tasks. For example, the Projects workset in-tegrates project management functionality if that area of SAP is usedwithin your organization. The Reports workset integrates SAP Net-Weaver BI content as well as iViews from the Business Package for Com-mon Parts. Each of the former related business packages are optionaland by nature complementary to the MSS functionality.

3.2 Configuration of the XSS Business Package

XSS requires substantial configuration within SAP NetWeaver Portal andthe J2EE engine. There is also configuration needed on the backend SAPERP software into which the business package applications connect too.In addition, optional configuration exists to enable functionality relating

Figure 3.4 MSS Workset Content from a PCD Perspective



70

3

to integration with ADS and SAP NetWeaver BI. In this section, wereview the common steps required to configure an XSS system in SAPNetWeaver 7.0.

3.2.1 Installation Requirements

A fully functional XSS implementation requires several SAP NetWeaverusage types with various components deployed to them. On the SAPNetWeaver Portal system, you’ll need the AS Java, EP, and EPC usagetypes. The default SAP NetWeaver Java installation contains componentsthat need to be configured such as ADS and the System Landscape Direc-tory (SLD). For both ADS and SLD, you may elect to use a separate, exist-ing AS Java system for such functionality depending on your SAP land-scape. We discuss options like this in great detail in Chapter 9, in Sections9.2, “Adobe Document Services,” and 9.3, “System Landscape Directory.”

Requiredcomponents

On SAP NetWeaver Portal, you must deploy the following softwarecomponents:

� Business packagesThe Business Packages for Employee & Manager Self Services providethe portal content required for XSS. Furthermore, based on projectrequirements, the Business Package for Common Parts and ProjectSelf-Services may be required. The business packages can be down-loaded from the SDN content Portfolio, https://www.sdn.sap.com/irj/sdn/contentportfolio.

� Web Dynpro software componentsYou must deploy the following components to enable runtime execu-tion of XSS screens in the portal: PCUI_GP, MSS, ESS, and SAP_PSSand SAP_ASR depending on your requirements. PCUI_GP is manda-tory; the rest are optional. You can find these software components athttp://service.sap.com/patches � SAP Application Components � SAPERP � SAP ERP 6.0 � Entry By Component � SAP XSS (Self Services). Atthis location, you’ll find subareas for ESS, MSS, PCUI, ASR, and PSS.

Backendrequirements

In addition to the items just listed, your ECC 6.0 system must have theextensions installed for Financials (EA-FIN) and Human Resources (EA-HR). For the MSS components, you also have the option to use SAP sys-tems such as SAP NetWeaver Business Intelligence (SAP NetWeaver BI)



71

3.2

7.0, SAP Supplier Relationship Management (SRM) 5.0, SAP StrategicEnterprise Management (SEM) 6.0, and Collaboration Projects(cProjects) 4.0, although these aren’t required.

3.2.2 XSS Configuration Steps

After downloading the files required for your project, it’s time to startthe installation and configuration process. The first step is to deploy thedownloaded archives to the SAP NetWeaver system. You can use theJava Support Pack Manager (JSPM) or the Software Deployment Man-ager (SDM) to deploy these components, although JSPM is the preferredmethod starting with SAP NetWeaver 7.0. You can find detailed steps ondeploying components using JSPM in Appendix A.

After deployment, the first step is to ensure that your SLD is successfullyconfigured. Particularly, you should make sure that your SLD is updatedwith the latest component repository (CR) content. Furthermore, youneed to ensure that the SLD that SAP NetWeaver Portal is using containsthe ECC system as a technical ABAP system. This is a prerequisite for theJava Connector (JCo) configuration step. Typically, an SAP productionlandscape has one SLD that all SAP systems replicate their informationfor. SLD concepts are further discussed in Section 9.3.

Single Sign-On (SSO)

The next step is to configure Single Sign-On (SSO) between the SAPNetWeaver Portal system running XSS and ECC 6.0. Refer to AppendixA for exact steps on configuring SSO between a SAP NetWeaver Javaand ABAP system. After ensuring the SLD and SSO configuration, younow need to enable communication between the SAP NetWeaver Javasystem and backend ECC system by configuring the JCo destinations forthe Web Dynpro applications. These are configured through the WebDynpro Content Administrator, which can be accessed through the por-tal under Content Administration � Web Dynpro. As shown in Figure3.5, after deploying the business package, the required destinations

Note

SAP Note 669669 contains instructions on how to update your SLD with thelatest CR (component repository) content.



72

3

show up in the tool, and you need to configure them. The JCo destina-tions beginning with SAP_R3_* should be configured.

JCo users As shown in Figure 3.6, when configuring JCo destinations, there aretwo types of connections for each JCo destination, Dictionary MetaData and Application Data. For the JCo destinations of type DictionaryMeta Data, you should use a service or technical user so that the metadata connection retrieves information about the RFC connection itselfand returns no real application data. This service user would typicallyhave no dialog permissions on the backend ECC system.

Figure 3.5 Web Dynpro Content Administrator

Figure 3.6 Editing a JCo Destination



73

3.2

For the JCo destinations of type Application Data, most likely, the UsedMethod will be of type Ticket, which uses the SAP Logon Ticket of theuser signed into the SAP NetWeaver Portal for SSO to the backend sys-tem. User mapping, while rarely used due to the manual effort needed,is another option. Either way, these connection types return actualapplication data, and user-defined data on the actual destination is rarelyused except in development and testing scenarios.

Portal system object

After successfully configuring and testing the JCo destinations used bythe Web Dynpro applications as shown in Figure 3.7, you need toensure that you have a portal system object configured for the Java WebDynpro runtime.

Figure 3.7 JCo Destination User Connection for Application Data

Figure 3.8 Successful JCo Destination



74

3

Portal system Within the portal, you create a new system object with alias SAP_WebDynpro_XSS. The only property category that needs to be filled out isthe Web Application Server (AS), and an example is shown in Figure 3.9.The Web AS Host Name should be the J2EE where the XSS Java compo-nents are deployed. The Web AS Path should be set to /webdynpro/dis-patcher. Appendix A contains detailed information on how to create aportal system object and configure the Web Application Server (WebAS) Property Category.

Assuming HR is successfully configured in ECC, you should be good togo from a configuration standpoint after completing these steps. If thereare issues connecting to your ECC system using any of these connec-tions, pay close attention to the service users. In addition, check thesecurity traces to ensure all necessary authorizations are assigned to thedialog users as well.

3.3 Architecture Impacts

With SAP NetWeaver 7.0, one of the key aspects to XSS that must beconsidered from an architecture perspective is the fact that the applica-tions in XSS are dependent on the portal runtime when they are exe-cuted. Technically speaking, the Web Dynpro runtime in AS Java doesnot require a portal. However, the Web Dynpro for Java applicationsthat are used in the XSS-based iViews actually run in the portal frame-

Figure 3.9 AS Connection for XSS


Architecture Impacts

75

3.3

work and use features such as implicit personalization (discussed indetail in Section 3.4 “Development Impacts”). Figure 3.10 shows a logi-cal overview of the XSS architecture from a portal perspective.

Runtime requirements

This dependency is very significant and is contrary to previous versionsof XSS. Prior to this version, the Web Dynpro applications (or ITS/IAC-based iViews) used in self-services were executed outside of the portalframework. Previously, for Web Dynpro-based packages, you couldinstall a separate J2EE-only system used for Web Dynpro and point theiViews to that system. For ITS- or IAC-based iViews, of course, they ranin the SAP ERP system.

As outlined in Figure 3.11, this new architecture essentially leaves youwith two choices. First, you can install your XSS applications on yourexisting portal. Although simplistic, the obvious drawback to thisapproach is the potential performance impacts the new XSS applicationswill cause on your portal environment. In addition, you’re introducingversion dependencies among XSS, your existing portal, and, of course,the backend system.

Figure 3.10 XSS Logical Software Architecture

Web Dynpro Java Runtime

NetWeaver 7.0 AS Java

Portal Framework(Usage Type EP Core)

XSS Java Components

NetWeaver 7.0 AS Java

Portal Framework(Usage Type EP Core)

XSS Business Package

Can Be Combined or Separated

NetWeaver 7.0 AS ABAP

SAP ERP 2005

XSS ABAP Component

JCO Destinations Call ECC



76

3

XSS and FPN The second option is to use FPN to integrate XSS into your existing por-tal. This protects your current portal from potential negative perfor-mance impacts of the XSS content. If your existing portal wasn’t sized tohandle the resource-intensive Web Dynpro-based XSS iViews, this is avery good option. In addition, you gain the advantages previously dis-cussed when using FPN, such as separating the XSS business contentfrom an implementation perspective and the ability to scale XSS (or yourconsumer portal) independently of the other system.

3.3.1 Using FPN with XSS

Implementing self-services functionality is no longer as simple as install-ing a standalone ITS, deploying the business package to your centralportal and beginning end-user rollout. Since SAP NetWeaver 6.40, theself-services functionality is now written in Java, and the footprintrequired to run the XSS applications is much larger on a SAP NetWeaver

Figure 3.11 XSS Architecture Choices

Combine XSS Java with Existing Portal

Pros- Simple Approach with Streamlined Installation- Only Need to Maintain One Portal Environment- Avoid Additional Portal Requirement - No Need to Implement FPN

Cons- Performance Issues in XSS Applications- Unable to Isolate XSS Applications from Existing

Portal- Version Dependencies Created Between XSS Java Components and Portal

Implement FPN

Pros- Existing Corporate or “Primary” Portal Not Impacted

by XSS Performance Issues or Version Dependencies - Flexible Content Integration Options Offered by FPN- Ability to Scale Portals Independently of Each Other

Cons- Must Stand Up Additional Portal Environment



77

3.3

Java Portal system. Further complicating things is the fact that the XSSJava components have dependencies to the underlying SAP NetWeaverJ2EE version and also to the ABAP backend patch level.

Architecture recommendation

As such, running XSS in an FPN configuration is recommended. Becauseyour users of self-service functionality will require a user ID in the ABAPuser store anyway, you’ll often see the XSS portal leverage the ECCABAP client as its user store. However, you may choose to use LDAP forboth SAP NetWeaver Portals if you want to assign the same LDAP groupto portal roles on both systems.

Essentially, to implement XSS, most likely you’ll be looking at addinganother J2EE instance to your landscape. Depending on high availabil-ity, sizing, and performance requirements, decisions such as running aJ2EE add-in versus standalone instance need to be made by the technicalinfrastructure team in conjunction with SAP Basis teams. We outlinedthe advantages and disadvantages to these items in Section 2.2.

From an FPN content-usage perspective, if XSS is the only FPN producernode in your landscape, it probably makes most sense to use RDL andintegrate XSS content into roles on the consumer portal. However, eachimplementation is unique, and there may be requirements where RRAmakes the most sense, such as the HR team wanting to own and admin-ister their own roles.

3.3.2 Deploying XSS to an Existing Portal

Although an FPN configuration has advantages, it does require an addi-tional SAP NetWeaver Java system to be installed and maintained inyour SAP landscape. This, of course, equates to cost and additional workfor your technical staff. If the overhead is too much for your organiza-tion, you can deploy XSS to an existing SAP NetWeaver Portal environ-ment.

Consolidation considerations

If you choose to go this route, you must be sure to consider severalimportant factors. We’ve already talked about the fact that Web Dynpro-based iViews can be very resource intensive on your portal. This is a keyitem to keep in mind because often a portal is used as simply a gatewayto applications running on separate systems. With XSS, you’re using



78

3

your portal as a runtime environment for the execution of a largeamount of content.

In addition, be aware that you’re creating a dependency between ver-sions of the XSS business package and the SAP NetWeaver Portalinstance. If a problem is discovered during testing of XSS that requiresan upgrade, your entire portal landscape may be affected in that youmay be forced to apply a new Support Package to the engine. This oftenintroduces a new series of regression testing for other portal functional-ity that potentially could impact other areas of an SAP project.

Performancetesting importance

To mitigate the risk from a performance perspective, running a perfor-mance stress test early against an environment that is production orclosely mirrors production is a good idea. Although this may require alot of coordination and additional work, it’s time well spent and willsave many headaches after going live. Performance testing is discussedin further detail in Chapter 11, mainly Section 11.4, “Performance Toolsand Problem Diagnosis.”

3.3.3 SAP NetWeaver Dependencies

XSS interacts with many system components that may be run outside ofyour immediate XSS landscape, regardless of whether you choose to useFPN or not. In Chapter 9, Managing a Content Driven Architecture, wediscuss services that are embedded in the AS Java system but are oftenshared by several systems for reasons such as simplified configurationand performance. Two examples of these services used heavily by XSSare ADS and SLD (see Figure 3.12).

Important Points in Deploying XSS Java to an Existing Portal

� Ensure hardware is properly sized for the new functionality.

� Conduct performance tests of XSS applications prior to rollout.

� Be ready to scale your portal (add dialog instances) if needed.

� Regularly monitor individual XSS applications and the portal environmentas a whole.

� Understand all version dependencies.



79

3.3

As discussed in detail in Section 9.2, ADS extends Adobe integration toSAP NetWeaver applications for areas such as form processing, printing,and the development and execution of SAP Interactive Forms. Althoughit’s installed in every AS Java system, you may elect to run parts of ADSon a central server. XSS heavily uses ADS in various applications.

SLD and XSSThe SLD stores various types of data about your SAP (and non-SAP) land-scape such as version information, development configurations, andconnection data. The SLD is required by XSS for the connections fromWeb Dynpro-based iViews to the SAP ERP system. If the SLD goesdown, your XSS applications won’t be accessible. In Chapter 9, we dis-cuss the impacts of this in great detail.

Finally, XSS may lead to the introduction of SAP NetWeaver Develop-ment Infrastructure (NWDI) in your SAP landscape. NWDI is used tomanage SAP Java development projects and is a separate SAPNetWeaver usage type that typically requires a dedicated AS Java sys-tem. XSS may need NWDI if your developers choose to customize SAP-delivered screens. We also discuss NWDI in detail in Section 9.4, “SAPNetWeaver Development Infrastructure,” of Chapter 9.

Figure 3.12 SAP NetWeaver Java Dependencies for XSS

Application Server Java

XSS JavaComponents


System Landscape Directory


Adobe Document Services

NetWeaver DevelopmentInfrastructure (NWDI)

XSS Business Package


OptionalOptionalRequired



80

3

3.4 Development Impacts

As mentioned, XSS is probably one of the most widely implementedbusiness packages and is also one of the only SAP software packages thathas a heavy Java footprint and that has the source code delivered bySAP. XSS is also unique in that a lot of the portal configuration is actuallycontained on the ABAP side. For example, the navigation links from themain page area in ESS are actually configured in the IMG within thebackend ECC system.

Customizing XSS If you want to modify the delivered XSS functionality by custom devel-opment through configuration or new development, three main optionsare available for you to leverage. First, you can use Web Dynpro ImplicitPersonalization (WD Implicit Personalization). Second, you can modifythe Java-based Web Dynpro components by editing source code or cre-ating your own Java components. Finally, you can write new function-ality on the ABAP side by using Web Dynpro or even classic Dynproscreens.

3.4.1 Web Dynpro Implicit Personalization

One of the most powerful features of Web Dynpro is the concept ofImplicit Personalization. All of the Web Dynpro-based iViews in the XSSbusiness package support WD Implicit Personalization. WD Implicit Per-sonalization allows content administrators to make changes to thescreens, such as adding text or hiding fields, using a WYSIWYG editordirectly in SAP NetWeaver Portal. This is an important concept becausefunctional teams typically want to make what they consider simple mod-ifications that are more aesthetic and UI based, or example, changing thecolor of a text on a screen to produce emphasis, adding additional ver-biage on a screen (i.e., benefit enrollment due date), or simply hidingfields that aren’t required functionality for a specific implementation.The changes made are stored as iView properties.

Note

It’s important to stress the fact that WD Implicit Personalization can be usedto visually alter UIs with no additional configuration or development effort.


Development Impacts

81

3.4

Furthermore, WD Implicit Personalization works on two levels. First, asshown in the example in the next section, WD Implicit Personalizationcan be used by a content administrator to distribute a change to a groupof users at a global level. However, WD Implicit Personalization can alsobe enabled at the end-user level so that an end user can use it to modifythe screens just for themselves.

3.4.2 Web Dynpro Implicit Personalization Example

As WD Implicit Personalization may be a new concept to even the mostseasoned SAP NetWeaver Portal professionals, we’ll walk through aquick example so you can see it in action. Our sample scenario has usmodifying the header text for the ESS Overview application shown inFigure 3.13 to include specific company text.

ExampleBecause we want this change to apply to all users, the content adminis-trator uses the portal content studio to edit the iView. WD Implicit Per-sonalization is based on the object’s runtime PCD URL, which meansthat you need to edit the iView from within its runtime structure. To putit another way, you shouldn’t edit the iView as it sits under a PCDfolder, but rather open the role where the iView resides and edit fromhere. In Figure 3.14, we’ve opened the Employee Self-Service role forediting.

Figure 3.13 ESS Screen Before WD Implicit Personalization



82

3

Page editor After selecting the Overview page, select the Open button to view thepage editor as shown in Figure 3.15.

After further drilling down, select the Overview iView, and select theOpen button. Now we’re at the actual iView properties screen as shownin Figure 3.16.

From here, we’re ready to perform our modifications. WD ImplicitModifications are set from the iViews preview mode. Select the Previewbutton in Figure 3.16. In Figure 3.17, we’re now viewing the Overviewapplication preview.

Figure 3.14 Overview Page Within the ESS Role

Figure 3.15 Overview Page


Development Impacts

83

3.4

Figure 3.16 Overview iView Properties

Figure 3.17 ESS Overview Screen — Preview Mode



84

3

To use WD Implicit Personalization from either administrator or end usermode, you hold down the Ctrl key and right-click. The user is presentedwith the WD Implicit Personalization editor, as shown in Figure 3.18.

Applyingcustomization

Once in the editor, you’re given a list of the Web Dynpro elements onthe screen, and you can personalize each individually. In Figure 3.19, wechange the Semantic Color to the value Positive, change the valuewithin the Text input field, and also check the box to Disable end userpersonalization for this iView. By disabling personalization for endusers, you prevent them from Ctrl and right-clicking and customizingthe iView for themselves.

After saving, a series of iView properties are stored on the iView notingour changes. Now when we navigate to the ESS Overview page, we cansee our changes, as shown in Figure 3.20.

WD Implicit Personalization, including supporting documentation, isn’twidely known by SAP professionals. It’s extremely important that youand your project team explore this option to see if it meets your needsbefore deciding to go the route of custom code and moving into anNWDI implementation.

Figure 3.18 Web Dynpro Implicit Personalization Mode


Development Impacts

85

3.4

WD Implicit Personalization advantages

There are significant advantages to using this functionality rather thanmaking code modifications. The primary reason is that you don’t needto install and configure an NWDI infrastructure, thereby reducing over-all costs. In addition, upgrades are much easier to manage because thereis no code involved. With NWDI, you need to merge code into newreleases of the product, which is quite a process as discussed in the nextsection. However, with WD Implicit Personalization, the iView proper-ties aren’t impacted during an upgrade.

Figure 3.19 Web Dynpro Implicit Personalization Modifications

Figure 3.20 After Web Dynpro Implicit Personalization



86

3

The bottom line is that WD Implicit Personalization is a powerful fea-ture to use and will greatly minimize your development and mainte-nance efforts.

3.4.3 XSS Java Customization

Modify deliveredsource code

If you need to perform modifications that can’t be met by using WDImplicit Personalization, you’ll most likely need to modify the deliveredsource code, which is written in Java. SAP delivers the source code inthe form of software component archives (*.sca). The only way to mod-ify the source code is to implement NWDI and place the XSS archivesunder management by NWDI. There is in-depth discussion of NWDI inChapters 9 and 10.

After configuring NWDI for XSS, SAP NetWeaver Developer Studio(NWDS) is the tool used to carry out code modifications. If you’realready using NWDI on your project, then this isn’t a big deal to addadditional Change Management Service (CMS) tracks because you prob-ably already have the infrastructure in place to support XSS. However, ifyou’re like most customers and new to NWDI and the Java-based SAPconcepts such as the SAP Component Model, this will be a significantundertaking for your Basis and development teams. It’s important tonote that XSS modifications and more broadly Web Dynpro componentsare only supported as development components and require the use ofNWDI. Unfortunately, when it comes to XSS, there is no backdoor man-ual workaround to avoid using NWDI on your XSS implementation ifyou require code modifications.

Note

Another important advantage to WD Implicit Personalization is that whenmodifications are made in content administrator mode, they are transport-able. This means a content administrator could make the changes in a DEVportal and have them transported through the environment. However, likeother types of end-user personalization, end-user personalizations made inWD Implicit Personalization aren’t transportable.


Resource Requirements

87

3.5

Ideal developer skillset

As previously stated, Java source code from the XSS components is mod-ified using NWDS. However, in most cases, it helps if the Java resourceperforming the modifications possesses working knowledge of HR froman ABAP standpoint as well because many of the fields and screens forXSS are named after their functional counterparts. As shown in this sec-tion, the resources required for implementing NWDI can be significantboth from an infrastructure and human capital perspective. Upgradesare also a somewhat manual process and can be very time consuming.Therefore, we strongly advise checking whether Web Dynpro ImplicitPersonalization can meet your needs before heading down the NWDIroute.

3.4.4 XSS ABAP Development

As we outline in the next section, in addition to strong SAP NetWeaverPortal and Java resource, XSS implementations also often require some-one with a strong ABAP background from a configuration and possiblydevelopment perspective because quite a bit of portal configuration isactually done on the ABAP side. Furthermore, if new functionality isrequired (e.g., a new form that isn’t delivered in the XSS packages), thensome project teams will opt to write the application as a Web DynproABAP due to the fact that they most likely already have strong ABAPskills and may be light on Java. The nice thing about using Web Dynproas the UI is that end users won’t be able to tell the difference regardlessof what language it’s written in (ABAP or Java).

3.5 Resource Requirements

From a resource perspective, XSS implementations will most likelyrequire a portal content developer to cross into the realm of ABAP con-

Note

There is a SAP Note that provides instructions on how to configure your CMStracks and perform initial modifications and subsequent upgrades to the XSScomponent. This is known as the XSS cookbook, and the document isattached to SAP Note 872892.



88

3

figuration and vice versa — or require a very good communication chan-nel between these two individuals or teams. This is because much of theportal configuration in terms of runtime links and information is actu-ally configured in the backend ECC application. Depending on yourrequirements, as a project manager, you should plan for the followingresources on your project:

Typical projectresources

� SAP project manager who will be responsible for the coordination ofall teams and managing the overall rollout

� SAP NetWeaver Basis team skilled in both Java and ABAP administra-tion, especially configuring Web Dynpro JCo destinations, SLD, andpotentially with the installation/configuration of NWDI

� Portal content developer to configure all PCD content from a portalperspective

� Java developer, if modifications to XSS are necessary, who alsoshould possess knowledge of NWDI and how to use it with NWDSand the web-based tools

� Skilled technical HR ABAP resource to assist with any changes in thebackend ECC system

Overall, the project time frame for XSS can range anywhere from a fewshort weeks to many months. Several factors come into play, such as ifthis is a new HR rollout or an upgrade, and if there is no customizationor several development objects. Project rollout size will also bear someweight on the amount of testing that adds in to the project time frame.


383

Index

A

ABAP user store 97ABAP Workbench 249, 269Active Component Framework (ACF)

250Active Directory 181Activity Data Collector 330Adobe Document Services (ADS) 22, 70,

78, 243, 244, 245, 247, 251Adobe Flex 156Adobe LiveCycle Designer 249AJAX 340Application caching 311Application component 172Application FPN 47Architecture 230

B

BE � Bidding EngineBEx (Business Explorer)

Broadcaster 123Portfolio 122Web 338Web Analyzer 120, 123, 148, 154

Bidding Engine (BE) 176, 180, 182, 186Bidding scenarios 195Broadcasting layout 122, 154BSP (Business Server Page) 221, 227,

357, 365BSP iView 365Business area FPN 48Business Explorer (BEx) 118

Role 122Business Intelligence (BI) 54Business Objects (BOBJ) 164Business Package 31, 229

Configuration 209for Employee and Manager Self-Services

(XSS) 48for PPM 90

Business Package (cont.)for PPMDC 92, 94For SAP SRM 170, 175For SAP SRM 5.0 171Portal configuration 184

Business Planning and Analytical Services 118

Business Planning role 121

C

Cache 310, 313, 316Catalog Content Management (CCM)

170, 172Catalog Procurement 178cFolders 90, 92, 101, 185Change and Transport System (CTS)

269, 283, 291Change Management Service (CMS)

268, 270, 274, 279, 294Collaboration 96, 124, 195Component Build Service (CBS) 268,

270, 271, 275, 341Component matrix 177Component repository (CR) 261Composite application 34, 44, 46, 89Connector property 284Consumer portal 45Content administration role 363Contract Management 195cProjects 90, 92, 101CPRXRPM 94, 95CPRXRPM_UI 94, 95, 96CRM (Customer Relationship Manage-

ment) 91, 93, 197CTS Deploy Web Service 301CTS+ 296CTS+ architecture 299Custom code 308


Index

384

D

Data Supplier Bridge 265Data Supplier Service 267Dedicated xRPM Java system 100Delta link 309Design Time Repository (DTR) 268, 270,

274Access through NWDI 270

Development Infrastructure (DI) 246Digital signature 248DMZ (Demilitarized Zone) 173, 179

E

Enhanced CTS+ 292, 294, 295Enhancement Package (EhP) 164, 340Enterprise Buyer (EB) 176, 195Enterprise Data Warehousing 118Enterprise Reporting, Query, and Analy-

sis 118Enterprise service-oriented architecture

(enterprise SOA) 339eSourcing 194ESS 68ESS business package 66External Portal 232

F

Federated portal performance 330Financials Supply Chain Management

(FSCM) 185Floor Plan Manager (FPM) 64FP_PDF_TEST_00 257FPN (Federated Portal Network) 16, 43,

44, 45, 49, 50, 52, 55, 56, 58, 60, 77, 106, 126, 131, 263, 291, 331, 332, 337

Free characteristics 123

G

Going Live Analysis 342

H

Hardware requirementsof Java Development Infrastructure

274Hardware sizing 308High availability (HA) 104, 251, 265,

274HTTP access 222

I

IAC (Internet Application Component) 172

ICH (Inventory Collaboration Hub) 173, 185

ICM (Internet Communication Mana-ger) 314

IGS (Internet Graphics Server) 112IMG (Implementation Guide) 211, 212Industry-Specific SAP CRM Business

Packages 207Information Broadcasting 147, 152Integrated ITS 231Integrating FPN content 52Interactive form 248Internet Application Component (IAC)

220, 228Internet Communication Framework

(ICF) 257ITS (Internet Transaction Server) 221,

357iView 223, 224, 227iView creation process 363

J

J2EE Administrator 317Java Connector (JCo) 222, 238Java Support Package Manager (JSPM)

31, 71Java UME 97


Index

385

JCo destination 72, 73, 111, 145, 261, 265

JVM (Java Virtual Machine) 315

K

Knowledge Management (KM) 90, 96, 195, 216

Knowledge Management favorite 148Knowledge Management transport 293

L

LAC (Live Auction Cockpit) 180Landing page 317Live auction 174Login Ticket Client 350

M

MDM (Master Data Management) 172Microsoft Active Directory 51, 106MSS business package 68

N

Navigation caching 311, 312NetWeaver Business Client (NWBC) 343Nonproduction SLD 265NWA (NetWeaver Administrator) 325

Logging 327NWDI (NetWeaver Development Infra-

structure) 246, 261, 262, 268, 270, 272, 273, 275, 294, 295, 335, 341

NWDS (NetWeaver Development Studio) 246, 339

O

Operational Purchaser 171

P

P4 connection 57PCD (Portal Content Directory) 309

Cache 310

PCD (Portal Content Directory) (cont.)Organization 286Performance 309

Performance 307, 309Problem diagnosis 318Tools 318

Pioneer 164Plan Driven Procurement (PDP) 170,

178, 179Portal

Content Catalog 212Content Composer 339Content Directory (PCD) 283Framework 47Monitoring tools 327Permissions 289Transport editor 292Transport package editor 292

PPM 90, 114PPMD_WD_MODELDATA_DIST 111PPMD_WD_RFC_METADATA_DIST

111PPMDC business package 92, 93Producer portal 45Producer registration 59Production SLD 264Project and Portfolio Management 90Project Manager 194

R

Remote Application Integration (RAI) 54, 149, 164

Remote Delta Link (RDL) 53, 54, 60, 105, 151

Remote Portlet 52Remote Role Assignment (RRA) 53, 105,

151RFC destination 257RFC destination for CTS+ 302RFx 174, 182RFx1 171Roles 202, 204, 205, 206RZ10 350


Index

386

S

SAINT 94Sample transport process using Enhanced

CTS+ 296SAP Catalog Content Management 172SAP Component Model 269SAP composite application for Resource

and Portfolio Management (xRPM) 48, 89

SAP CRMArchitecture and landscape considerati-

ons 215Business Package 200, 215Business role upload 212FPN scenarios 216Frontend access methods 199Overview 198Portal integration with 199Role upload 211Usage scenarios 200WebClient 202

SAP CRM 5.0 business package 203SAP CRM Portal Content

Configuration of 208SAP CRM WebClient 210SAP CRM WebClient UI 202SAP Developer Network (SDN) 183SAP Employee Self-Service (ESS) 64SAP ERP 91, 93, 173, 176SAP ERP HCM Administrative Services

(ASR) 64SAP Financials Supply Chain Manage-

ment (FSCM) 185SAP GUI 176, 226

for HTML 223for Windows 223SSO 226

SAP Help Portal 246SAP IACs 184SAP Interactive Forms by Adobe 100SAP Inventory Collaboration Hub (ICH)

185, 187SAP ITS Transaction iView 225SAP LoadRunner 324SAP Logon Ticket 347, 351, 361

SAP Manager Self-Service (MSS) 64SAP NetWeaver 6.40 27SAP NetWeaver 7.0 28SAP NetWeaver 7.1 40SAP NetWeaver Administrator (NWA)

260, 277, 325, 342Configuration wizard 277

SAP NetWeaver BI 47, 49, 91, 101, 117, 171, 173, 176, 183, 184, 196, 250, 338Content 93Java 126, 134, 178Java Software Development Kit (SDK)

162SAP NetWeaver Business Client 343SAP NetWeaver Composition Environ-

ment (SAP NetWeaver CE) 17, 38, 40, 339

SAP NetWeaver Developer Studio (NWDS) 36, 113, 246, 249

SAP NetWeaver Development Infrastruc-ture (NWDI) 36, 79, 243, 246, 268

SAP NetWeaver PortalAnd Java UI configuration 107

SAP NetWeaver Process Integration (SAP NetWeaver PI) 176, 179, 195, 260, 264, 265, 299Server 176

SAP NetWeaver Visual Composer (SAP NetWeaver VC) 17, 41, 156

SAP Online Help 183SAP Project Self-Service (SAP PSS) 64SAP Service Marketplace 107SAP SRM 169, 183, 184

2007 1952007 Business Package 1955.0 1706.0 1707.0 194ABAP UME 181Administrator 171Bidding Engine 173, 174Business package 181, 183Enterprise Buyer 178MDM Catalog 172, 176, 178SUS � Supplier Self-Serivces


Index

387

SAP Supplier Network Collaboration 173

SAP transaction parameters 224SAP transaction template 223SAP Web Dispatcher 180, 232Scaled NWDI landscape 274SE80 246, 269Security Provider Service 253Self-Service Procurement 170Service account 109Service Marketplace 177, 183Service Procurement 170Sherlok 324Single Sign-On (SSO) 71, 109, 111

Common requirement for FPN scenario 354

Configuration 354SLD (System Landscape Directory) 22,

70, 71, 78, 102, 110, 243, 244, 245, 260, 266Data Supplier Service 110

SM59 256, 301Software Component Archive (SCA) 94,

269Software Deployment Manager (SDM)

71, 304Solution Manager 102, 183, 260, 264,

299, 300Solution Manager Diagnostics 196, 322,

323, 342Spend Analysis 170SPNego 317SRM (Supplier Relationship Manage-

ment) 93Strategic Sourcing 178Strategic Sourcing Scenario 178STRUSTSSO2 351Supplier administrator 175Supplier Application Starter 187Supplier Collaboration 174, 180Supplier Collaboration Business Package

170, 173, 175, 185Supplier Portal Administration Role 193Supplier Relationship Management

(SRM) 91, 169

Supplier Self-Services (SUS) 171, 176, 179

Support Catalog Procurement 178Synchronization of production and non-

production SLD 266System landscape object 284System template 358

T

Template Installer 136, 277Three-tiered landscape 104Tracks 271Trading partner directory (TPD) 171,

175, 187Transport Management System (TMS)

292Transport Organizer UI 304, 306

U

Universal Worklist (UWL) 124, 174, 195User administration 175User management 362User Management Engine (UME) 51,

52, 347store considerations 180

User management with FPN 51User persistence 51

V

verify.der 351Visual Administration tool 356Visual Administrator 56, 112, 305Visual Composer (VC) 114, 339

W

Web Application Designer 125Web Based Transport Organizer 297Web Dynpro 33, 336, 340

ABAP 228, 237, 340, 357, 361Content Administrator 71, 72, 261Implicit Personalization 80, 81, 84, 85iView 176


Index

388

Web Dynpro (cont.)Java 228, 340, 364Java application 187JCo destination 266Suspendability 315

WEB GUI 221, 225Web Services 52, 114Web Services for Remote Portlets (WSRP)

38Web Services Navigator 255Web-based Distributed Authoring and

Versioning (WebDAV) 133, 270, 293WebEx 90Wily Introscope for SAP NetWeaver 322WSRP (Web Services for Remote Portlets)

52WYSIWYG tool 339

X

xApps 89Xcelsius+ 164XML Upload 213XMLA 163xRPM 48, 89, 93, 98, 103, 104, 105,

3384.5 101

xRPM (cont.)And Adobe integration 100Deployment scenario 99Development impact 113Java runtime component 110Landscape considerations 103Master Guide 107Master Note 96Production landscape 106Setup 107Software component 101With FPN 105

XSS 48, 49, 51, 63, 64, 74, 77, 246, 250, 261, 266, 275ABAP Development 87And FPN 76Components 63Configuration 69Configuration steps 71Customizing 80Installation requirements 70Java Customization 86Screens 64

Z

Zero Client Install (ZCI) 249


Documents

Sappress Content Integration Sap Netweaver Portal