Marty McCormick, Matt Stratford

Content Integration with SAP NetWeaver Portal

Bonn

Boston

Contents at a Glance
SECTION I 1 2 Introduction ........................................................................ Federated Portal Network ................................................... 15 43

SECTION II 3 Business Package for Manager and Employee Self-Services ........................................................................ 4 SAP Composite Application Resource and Portfolio Management ....................................................................... 5 6 7 8 89 63

SAP NetWeaver Business Intelligence .................................. 117 SAP Supplier Relationship Management .............................. 169 SAP Customer Relationship Management ............................ 197 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 B Configuration Steps ............................................................. 347 The Authors ........................................................................ 381

Contents
Section I 1 Introduction .................................................................
1.1 Book Overview ............................................................... 1.1.1 About This Book ................................................ 1.1.2 Our Goal in Writing This Book ........................... 1.1.3 SAP Supporting Information ............................... 1.1.4 Product Versions ................................................ Evolution of SAP NetWeaver Portal ................................ Portal Content Overview ................................................ 1.3.1 SAP Business Packages ....................................... 1.3.2 Delivered Composite Applications ..................... 1.3.3 Integration of Nondelivered SAP Content .......... 1.3.4 Integration of Non-SAP Content ........................ SAP NetWeaver Composition Environment ..................... 1.4.1 SAP NetWeaver CE Architecture ........................ 1.4.2 SAP NetWeaver CE Tools ................................... 1.4.3 SAP NetWeaver CE and SAP NetWeaver Portal .. Introduction Wrap Up ....................................................

15
15 19 23 24 25 25 29 29 34 34 37 38 39 40 41 41

1.2 1.3

1.4

1.5

Federated Portal Network ...........................................

2.1 2.2 Federated Portals Overview ............................................ Federated Portal Usage Scenarios ................................... 2.2.1 Using FPN for Portal Content ............................. 2.2.2 When to Use an FPN ......................................... 2.2.3 Federated Portal User Persistence Stores ............ 2.2.4 Using FPN with Non-SAP Content ..................... Content Integration Options ........................................... 2.3.1 Remote Delta Link (RDL) ................................... 2.3.2 Remote Role Assignment (RRA) ......................... 2.3.3 Remote Application Integration (RAI) ................ Configuring a Federated Portal Network ......................... 2.4.1 Prerequisites ...................................................... 2.4.2 Configuration ..................................................... 2.4.3 FPN Usage Tips ..................................................

43
43 46 47 49 51 52 52 53 53 54 55 55 56 60

2.3

2.4

Contents

Section II 3 Business Package for Manager and Employee Self-Services .................................................................

3.1 Business Content Integration .......................................... 3.1.1 Brief History ....................................................... 3.1.2 Employee Self-Service ........................................ 3.1.3 Manager Self-Service .......................................... Configuration of the XSS Business Package ...................... 3.2.1 Installation Requirements ................................... 3.2.2 XSS Configuration Steps ..................................... Architecture Impacts ....................................................... 3.3.1 Using FPN with XSS ........................................... 3.3.2 Deploying XSS to an Existing Portal .................... 3.3.3 SAP NetWeaver Dependencies ........................... Development Impacts ..................................................... 3.4.1 Web Dynpro Implicit Personalization ................. 3.4.2 Web Dynpro Implicit Personalization Example ... 3.4.3 XSS Java Customization ...................................... 3.4.4 XSS ABAP Development ..................................... Resource Requirements ..................................................

63
63 64 66 68 69 70 71 74 76 77 78 80 80 81 86 87 87

3.2

3.3

3.4

3.5

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

4.1 Business Content Integration .......................................... 4.1.1 Product Overview .............................................. 4.1.2 Portal Content for xRPM .................................... Technical Architecture Considerations ............................. 4.2.1 Technical Components ....................................... 4.2.2 Deployment Options .......................................... 4.2.3 Landscape Considerations .................................. 4.2.4 Landscape Configuration .................................... Portal Configuration of xRPM Content ............................ 4.3.1 Configuration Process Overview ......................... 4.3.2 Configuration Case Study ...............................

89
89 90 92 93 94 97 101 104 107 108 108

4.2

4.3

Contents

4.4

4.5

Development Impacts ..................................................... 4.4.1 Modification of SAP-Delivered Screens .............. 4.4.2 Custom Development Scenarios ......................... Resource Requirements ..................................................

112 113 113 114

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

5.1 Portal Content Integration .............................................. 5.1.1 Product Overview .............................................. 5.1.2 Portal Content for SAP NetWeaver BI ................ Technical Architecture Considerations ............................ 5.2.1 Deployment Options ......................................... 5.2.2 Portal Landscape Considerations ........................ 5.2.3 Seamless Federated Portal .................................. Configuration of SAP NetWeaver BI Portal ...................... 5.3.1 Installation Requirements .................................. 5.3.2 Configuration Steps ............................................ 5.3.3 Manual Configuration ........................................ Development Impacts ..................................................... 5.4.1 Query-Based iViews ........................................... 5.4.2 Information Broadcasting ................................... 5.4.3 Visual Composer ................................................ 5.4.4 SAP NetWeaver BI and Custom Java Development ..................................................... 5.4.5 Development Wrap Up ...................................... SAP and Business Objects ............................................... Resource Requirements .................................................. 117 118 119 126 126 131 133 134 134 135 137 147 148 152 155 162 163 164 166

5.2

5.3

5.4

5.5 5.6

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

6.1 Business Content Integration .......................................... 6.1.1 Product Overview .............................................. 6.1.2 Portal Content for SAP SRM ............................... Technical Architecture Considerations ............................ 6.2.1 UME Store Considerations ................................. 6.2.2 Internal Portal .................................................... 6.2.3 External Portal ................................................... Portal Configuration of SAP SRM Content ....................... 6.3.1 Internal Portal .................................................... 169 170 170 175 180 181 181 182 183

6.2

6.3

Contents

6.4 6.5 6.6

6.3.2 External Portal .................................................... Development Impacts ..................................................... Resource Requirements .................................................. Looking Forward eSourcing and SAP SRM 7.0 ............

185 193 193 194

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

7.1 Business Content Integration .......................................... 7.1.1 Portal Integration with SAP CRM ....................... 7.1.2 SAP CRM Business Packages ............................... Configuration of SAP CRM Portal Content ...................... 7.2.1 General Business Package Configuration ............. 7.2.2 Detailed Configuration Example ......................... Architecture, Development, and Resource Impacts ......... 7.3.1 Architecture Impacts .......................................... 7.3.2 Development Impacts ........................................ 7.3.3 Resource Impacts ............................................... 197 199 200 208 209 210 214 214 216 217

7.2

7.3

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

8.1 Portal Content Integration .............................................. 8.1.1 SAP-Delivered iViews ......................................... 8.1.2 SAP-Delivered Business Packages ....................... SAP Technical Architecture Considerations ..................... Portal Configuration of SAP ERP Content ........................ Development Impacts ..................................................... Resource Requirements .................................................. 219 223 229 230 233 235 238

8.2 8.3 8.4 8.5

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

9.1 9.2 A New Set of Challenges ................................................. Adobe Document Services .............................................. 9.2.1 Functionality Overview ...................................... 9.2.2 Architecture Considerations ............................... 9.2.3 Configuration ..................................................... System Landscape Directory ............................................ 9.3.1 Functionality Overview ...................................... 243 247 247 249 252 259 260

9.3

10

Contents

9.4

9.5

9.3.2 Architecture Considerations ............................... 9.3.3 Configuration ..................................................... SAP NetWeaver Development Infrastructure .................. 9.4.1 Functionality Overview ...................................... 9.4.2 Architecture Considerations ............................... 9.4.3 Configuration Overview ..................................... Wrap Up ........................................................................

262 267 268 268 272 277 281

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

10.1 Best Practices for the Portal Content Directory ............... 10.1.1 PCD Overview ................................................... 10.1.2 PCD Organization .............................................. 10.1.3 PCD Permissions ................................................ 10.1.4 Managing Content on Producer Portals .............. Portal Change and Transport Management ..................... 10.2.1 Portal Transport Process ..................................... 10.2.2 Enhanced CTS+ and SAP NetWeaver Portal ........ 10.2.3 Sample Transport Process Using Enhanced CTS+ 10.2.4 CTS+ Architecture Considerations ...................... 10.2.5 Configuration ..................................................... 283 284 285 289 289 291 292 294 296 299 301

10.2

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

11.1 11.2 Portal Content Directory Performance ............................ Caching .......................................................................... 11.2.1 Navigation Caching ............................................ 11.2.2 Application Caching ........................................... 11.2.3 Custom Object Caching ...................................... Overall Performance Recommendations ......................... 11.3.1 Tune the JVM .................................................... 11.3.2 Enable Caching .................................................. 11.3.3 Reduce Logging ................................................. 11.3.4 Keeping a Light Landing Page ............................ 11.3.5 Browser Settings ................................................ Performance Tools and Problem Diagnosis ..................... 11.4.1 Methodology ..................................................... 11.4.2 Solution Manager Diagnostics ............................ 11.4.3 Sherlok .............................................................. 309 310 311 311 313 315 315 316 316 317 318 318 319 322 324

11.3

11.4

11

Contents

11.5 11.6

11.4.4 SAP NetWeaver Administrator ........................... 11.4.5 SAP NetWeaver Portal Monitoring Tools ............ Federated Portal Performance ......................................... Content Performance Wrap Up .......................................

325 327 330 333

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

12.1 12.2 All for a Seamless End-User Experience ........................... Key Points ...................................................................... 12.2.1 Federated Portals ............................................... 12.2.2 Content Integration ............................................ 12.2.3 Architecture and Landscape Impacts .................. 12.2.4 Custom Development Practices .......................... 12.2.5 SAP NetWeaver Landscape Considerations ......... 12.2.6 Impacts to Content Administration ..................... 12.2.7 Portal Performance ............................................. Looking Forward ............................................................. 335 336 337 337 338 339 340 341 341 342

12.3

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

A.1 SSO Configuration Between the SAP NetWeaver Portal and the ABAP System ..................................................... A.1.1 Steps on the SAP NetWeaver Portal (Java Stack) . A.1.2 Configuration for SSO in the ABAP System ......... SSO Configuration Between Two SAP NetWeaver Portals A.2.1 Export J2EE certificate ........................................ A.2.2 Configure Target J2EE for SSO ............................ Creating a Portal System Object for a Backend ABAP System with System Alias ................................................ iView Creation Process .................................................... Downloading, Deploying, and Running a Business Package .......................................................................... Multiple Property Replacement ...................................... 347 348 350 354 354 354 357 363 368 376

A.2

A.3 A.4 A.5 A.6

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

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

12

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

Business Package for Manager and Employee Self-Services

After completing this chapter, youll be familiar with how to configure the Business Package for Manager and Employee Self-Services (XSS) in SAP NetWeaver Portal. In addition, youll understand how to address architecture and development challenges often experienced during an XSS implementation.

3.1

Business Content Integration

In terms of portal functionality, few business packages can offer as much as the Business Package for Employee Self-Service (ESS) and Manager Self Service (MSS). They are often implemented in parallel, and many concepts relating to configuration, architecture, and development are consistent across both business packages. Although these two business packages contain the portal content directory (PCD) content necessary, such as iViews and pages, the actual code is delivered in the form of Java-based software components. The underlying technology used is Web Dynpro Java, and there are several components that make up SAP Self Services (XSS). Technically speaking, XSS consists of the following components, which are delivered as software component archive (.sca) files:
XSS components

63

Business Package for Manager and Employee Self-Services

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 well point out the ASR or PSS components when appropriate. These components adhere to the Java-based SAP Component Model, and the last component in the list (PCUI) is the most vital to the others. PCUI is the central Web Dynpro component that provides the underlying framework for an application within ESS or MSS. As such, to implement MSS, ESS, ASR, or PSS youll always need to deploy the PCUI component. Well discuss PCUI and the overall configuration framework for self-services later in Section 3.4, Development Impacts.
Note Often, professionals in the SAP industry refer to XSS as a whole to include the business package and the Java-based software components; well do the same in this chapter.

3.1.1
XSS screens

Brief History

Before the release of SAP NetWeaver 6.40, the business packages for ESS and MSS were based on SAP transactions that were delivered in the form of Internet Transaction Server (ITS) services known as Internet Application Components (IACs). ESS and MSS deployments included a standalone ITS infrastructure in addition to the SAP Enterprise Portal and backend SAP R/3 system. Because the screens were standard SAP transaction screens, casual company users who were not used to SAP screens and navigation components were required to learn it for self-services such as benefits, personal data, and so on. With the release of SAP ERP 2004 (ECC 5.0) and the SAP NetWeaver 6.40 Java stack, SAP redesigned the self-services application to be based on Web Dynpro. As shown in Figure 3.1, the Web Dynpro-based XSS screens resemble a more traditional web-based look and feel that is often seen at commercial websites. This is highly beneficial because the self-service applica-

64

Business Content Integration

3.1

tions within XSS are often used by casual SAP users who may not be familiar with the intricate nature of traditional SAP screens. The emergence of the XSS business package has also resulted in the ability to leverage a large amount of functionality from your Java-based SAP NetWeaver systems.

ITS IAC

Web Dynpro Java

Figure 3.1 Comparison of ITS and Web Dynpro iViews

For example, users can now work with SAP Interactive Forms using Adobe Document Services (ADS), which is built into the SAP NetWeaver 7.0 Java AS. In this section, well provide an overview of the XSS functionality available to integrate into your SAP NetWeaver Portal. The versions that we base our documentation on is a SAP NetWeaver 7.0 SPS 15 system with ECC 6.0 backend. In the next few sections, well provide an overview of the SAP NetWeaver Portal content that is provided with the XSS business packages. The functionality described in these sections highlights some of the commonly used areas of XSS but isnt an exhaustive list. As always, consult the official, most recent SAP documentation for each business package for detailed explanations.
Delivered portal content

65

Business Package for Manager and Employee Self-Services

3.1.2

Employee Self-Service

Within the ESS business package, iViews are grouped into several categories, which are assembled together into portal worksets in the delivery of the ESS application. Of course, these iViews can be assembled into your own portal roles in a manner specific to your organizational structure. Figure 3.2 shows the main ESS page and the associated work areas or groups.

Figure 3.2 Overview of ESS

The Benefits and Payment applications allow employees to view information related to their benefits package, such as current and past income statements, retirement planning assistance, and health and dental benefit information. Users can update their benefit options, such as updates to 401K contribution percentages. As the name suggests, the Personal Information applications allow employees to update personal data, such as addresses, phone number, bank information, and familyrelated information. The address book workset contains iViews that enable employees to access certain personal information from other employees. In addition, they can make updates to their own information in the corporate directory. One of the most sophisticated sets of applications is the Life and Work Events functionality. In this area of ESS, users can manage significant events such as changes to employment status or family events such as the birth of a child or divorce. In addition, various

66

Business Content Integration

3.1

important events are linked with tasks and supporting documentation necessary to address each event. The ability to trigger workflow-related processes specific to an employee event is highly configurable. In fact, placeholders to include customized HTML content are included with each application, making it easier for content administrators to manage your company-specific documents and distribute them to end users. As a drill-down example to the previous paragraph, Figure 3.3 shows the Web Dynpro for Java-based Benefits and Payment iView. From this iView, employees can manage their plan participation relative to benefits. Furthermore, during open enrollment, employees can use this iView as the launch point to enroll or change their benefit plans. We used this iView as an example because its often one of those pieces of functionality that gets hit really hard once a year (i.e., the two weeks during open enrollment) and has relatively low volume the rest of the time. Thus, as a system architect or performance engineer, you should account for these peaks when sizing your environment. Also, as shown in Figure 3.3, this iView allows employees to check items related to their compensation and access online pay statements which is another peak period as employees often check their pay statement once per pay period, often as soon as they get in on payday.
Example

Figure 3.3 ESS Benefits and Payment iView

67

Business Package for Manager and Employee Self-Services

ESS functionality

The ESS business package is also used for a wide variety of work-related administrative tasks. The Working Time application allows users to perform actions related to functions such as time entry and leave requests. In addition, users can link time entry to specific tasks or SAP objects as well as make corrections to previous time entered as they view the hours worked in a specific time period using a calendar graphical display. Users can also trigger a leave request, which initiates approval processes that are actually linked to functionality delivered in MSS. Travel management functionality is also included in ESS. iViews included in the Travel and Expenses workset allow employees to perform tasks such as entering expenses from business trips and submitting them for approval. They can also create new trip requests and even book their travel plans for lodging and transportation. Authorized users can also perform travel functions for other users, which may be useful for secretaries who work for executives who travel frequently for business. The Learning and Career applications allow users to manage functions such as internal job moves and updates to their skills profile. In addition, users can search for internal positions and save search profiles for future use. There is also functionality to apply directly for a desired position or release your candidate profile.

3.1.3

Manager Self-Service

The MSS business package contains applications that allow managers within various areas of an organization to perform several of their respective job functions through the SAP NetWeaver Portal. The applications within MSS are organized by the type of operational role that a manager plays within an organization. As shown in Figure 3.4, MSS is organized in worksets containing similar tasks relating to both generic HR functions as well as business-related activities such as project planning and financial management.
MSS functionality

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

68

Configuration of the XSS Business Package

3.2

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

Figure 3.4 MSS Workset Content from a PCD Perspective

The Budget workset gives managers insight into the finances at the organizational entities in which they oversee or have a stake in. For example, this is where a manager could view how their respective cost center was doing at a given point in a quarter. In addition, costs related to assets such as computer-related equipment is available through the Budget workset. The Work Overview workset includes SAP-related items that a manager must complete. The Universal Worklist (UWL) is included within this functionality. Several other worksets arent part of the MSS core but are often used because they relate to manager tasks. For example, the Projects workset integrates project management functionality if that area of SAP is used within your organization. The Reports workset integrates SAP NetWeaver BI content as well as iViews from the Business Package for Common Parts. Each of the former related business packages are optional and by nature complementary to the MSS functionality.
MSS additional worksets

3.2

Configuration of the XSS Business Package

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

69

Business Package for Manager and Employee Self-Services

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

3.2.1

Installation Requirements

A fully functional XSS implementation requires several SAP NetWeaver usage types with various components deployed to them. On the SAP NetWeaver Portal system, youll need the AS Java, EP, and EPC usage types. The default SAP NetWeaver Java installation contains components that need to be configured such as ADS and the System Landscape Directory (SLD). For both ADS and SLD, you may elect to use a separate, existing AS Java system for such functionality depending on your SAP landscape. We discuss options like this in great detail in Chapter 9, in Sections 9.2, Adobe Document Services, and 9.3, System Landscape Directory.
Required components

On SAP NetWeaver Portal, you must deploy the following software components:
Business packages

The Business Packages for Employee & Manager Self Services provide the portal content required for XSS. Furthermore, based on project requirements, the Business Package for Common Parts and Project Self-Services may be required. The business packages can be downloaded from the SDN content Portfolio, https://www.sdn.sap.com/irj/ sdn/contentportfolio.
Web Dynpro software components

You must deploy the following components to enable runtime execution of XSS screens in the portal: PCUI_GP, MSS, ESS, and SAP_PSS and SAP_ASR depending on your requirements. PCUI_GP is mandatory; the rest are optional. You can find these software components at http://service.sap.com/patches SAP Application Components SAP ERP SAP ERP 6.0 Entry By Component SAP XSS (Self Services). At this location, youll find subareas for ESS, MSS, PCUI, ASR, and PSS.
Backend requirements

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

70

Configuration of the XSS Business Package

3.2

7.0, SAP Supplier Relationship Management (SRM) 5.0, SAP Strategic Enterprise Management (SEM) 6.0, and Collaboration Projects (cProjects) 4.0, although these arent required.

3.2.2

XSS Configuration Steps

After downloading the files required for your project, its time to start the installation and configuration process. The first step is to deploy the downloaded archives to the SAP NetWeaver system. You can use the Java Support Pack Manager (JSPM) or the Software Deployment Manager (SDM) to deploy these components, although JSPM is the preferred method starting with SAP NetWeaver 7.0. You can find detailed steps on deploying components using JSPM in Appendix A. After deployment, the first step is to ensure that your SLD is successfully configured. Particularly, you should make sure that your SLD is updated with the latest component repository (CR) content. Furthermore, you need to ensure that the SLD that SAP NetWeaver Portal is using contains the ECC system as a technical ABAP system. This is a prerequisite for the Java Connector (JCo) configuration step. Typically, an SAP production landscape has one SLD that all SAP systems replicate their information for. SLD concepts are further discussed in Section 9.3.
Note SAP Note 669669 contains instructions on how to update your SLD with the latest CR (component repository) content.

The next step is to configure Single Sign-On (SSO) between the SAP NetWeaver Portal system running XSS and ECC 6.0. Refer to Appendix A for exact steps on configuring SSO between a SAP NetWeaver Java and ABAP system. After ensuring the SLD and SSO configuration, you now need to enable communication between the SAP NetWeaver Java system and backend ECC system by configuring the JCo destinations for the Web Dynpro applications. These are configured through the Web Dynpro Content Administrator, which can be accessed through the portal under Content Administration Web Dynpro. As shown in Figure 3.5, after deploying the business package, the required destinations

Single Sign-On (SSO)

71

Business Package for Manager and Employee Self-Services

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

Figure 3.5 Web Dynpro Content Administrator JCo users

As shown in Figure 3.6, when configuring JCo destinations, there are two types of connections for each JCo destination, Dictionary Meta Data and Application Data. For the JCo destinations of type Dictionary Meta Data, you should use a service or technical user so that the meta data connection retrieves information about the RFC connection itself and returns no real application data. This service user would typically have no dialog permissions on the backend ECC system.

Figure 3.6 Editing a JCo Destination

72

Configuration of the XSS Business Package

3.2

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

Figure 3.7 JCo Destination User Connection for Application Data

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

Portal system object

Figure 3.8 Successful JCo Destination

73

Business Package for Manager and Employee Self-Services

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 is

the 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 components are deployed. The Web AS Path should be set to /webdynpro/dispatcher. Appendix A contains detailed information on how to create a portal system object and configure the Web Application Server (Web AS) Property Category.

Figure 3.9 AS Connection for XSS

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

3.3

Architecture Impacts

With SAP NetWeaver 7.0, one of the key aspects to XSS that must be considered from an architecture perspective is the fact that the applications in XSS are dependent on the portal runtime when they are executed. Technically speaking, the Web Dynpro runtime in AS Java does not require a portal. However, the Web Dynpro for Java applications that are used in the XSS-based iViews actually run in the portal frame-

74

Architecture Impacts

3.3

work and use features such as implicit personalization (discussed in detail in Section 3.4 Development Impacts). Figure 3.10 shows a logical overview of the XSS architecture from a portal perspective. This dependency is very significant and is contrary to previous versions of XSS. Prior to this version, the Web Dynpro applications (or ITS/IACbased iViews) used in self-services were executed outside of the portal framework. Previously, for Web Dynpro-based packages, you could install a separate J2EE-only system used for Web Dynpro and point the iViews to that system. For ITS- or IAC-based iViews, of course, they ran in the SAP ERP system.
Runtime requirements

NetWeaver 7.0 AS Java

Web Dynpro Java Runtime

Portal Framework (Usage Type EP Core)

XSS Java Components

JCO Destinations Call ECC NetWeaver 7.0 AS ABAP

Can Be Combined or Separated NetWeaver 7.0 AS Java

SAP ERP 2005

Portal Framework (Usage Type EP Core)

XSS ABAP Component

XSS Business Package

Figure 3.10 XSS Logical Software Architecture

As outlined in Figure 3.11, this new architecture essentially leaves you with two choices. First, you can install your XSS applications on your existing portal. Although simplistic, the obvious drawback to this approach is the potential performance impacts the new XSS applications will cause on your portal environment. In addition, youre introducing version dependencies among XSS, your existing portal, and, of course, the backend system.

75

Business Package for Manager and Employee Self-Services

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

Figure 3.11 XSS Architecture Choices XSS and FPN

The second option is to use FPN to integrate XSS into your existing portal. This protects your current portal from potential negative performance impacts of the XSS content. If your existing portal wasnt sized to handle the resource-intensive Web Dynpro-based XSS iViews, this is a very good option. In addition, you gain the advantages previously discussed when using FPN, such as separating the XSS business content from an implementation perspective and the ability to scale XSS (or your consumer portal) independently of the other system.

3.3.1

Using FPN with XSS

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

76

Architecture Impacts

3.3

Java Portal system. Further complicating things is the fact that the XSS Java components have dependencies to the underlying SAP NetWeaver J2EE version and also to the ABAP backend patch level. As such, running XSS in an FPN configuration is recommended. Because your users of self-service functionality will require a user ID in the ABAP user store anyway, youll often see the XSS portal leverage the ECC ABAP client as its user store. However, you may choose to use LDAP for both SAP NetWeaver Portals if you want to assign the same LDAP group to portal roles on both systems. Essentially, to implement XSS, most likely youll be looking at adding another J2EE instance to your landscape. Depending on high availability, sizing, and performance requirements, decisions such as running a J2EE add-in versus standalone instance need to be made by the technical infrastructure team in conjunction with SAP Basis teams. We outlined the advantages and disadvantages to these items in Section 2.2. From an FPN content-usage perspective, if XSS is the only FPN producer node in your landscape, it probably makes most sense to use RDL and integrate XSS content into roles on the consumer portal. However, each implementation is unique, and there may be requirements where RRA makes the most sense, such as the HR team wanting to own and administer their own roles.
Architecture recommendation

3.3.2

Deploying XSS to an Existing Portal

Although an FPN configuration has advantages, it does require an additional SAP NetWeaver Java system to be installed and maintained in your SAP landscape. This, of course, equates to cost and additional work for your technical staff. If the overhead is too much for your organization, you can deploy XSS to an existing SAP NetWeaver Portal environment. If you choose to go this route, you must be sure to consider several important factors. Weve already talked about the fact that Web Dynprobased iViews can be very resource intensive on your portal. This is a key item to keep in mind because often a portal is used as simply a gateway to applications running on separate systems. With XSS, youre using
Consolidation considerations

77

Business Package for Manager and Employee Self-Services

your portal as a runtime environment for the execution of a large amount of content.
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 environment as a whole. Understand all version dependencies.

In addition, be aware that youre creating a dependency between versions of the XSS business package and the SAP NetWeaver Portal instance. If a problem is discovered during testing of XSS that requires an upgrade, your entire portal landscape may be affected in that you may be forced to apply a new Support Package to the engine. This often introduces a new series of regression testing for other portal functionality that potentially could impact other areas of an SAP project.
Performance testing importance

To mitigate the risk from a performance perspective, running a performance stress test early against an environment that is production or closely mirrors production is a good idea. Although this may require a lot of coordination and additional work, its time well spent and will save many headaches after going live. Performance testing is discussed in further detail in Chapter 11, mainly Section 11.4, Performance Tools and Problem Diagnosis.

3.3.3

SAP NetWeaver Dependencies

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

78

Architecture Impacts

3.3

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

Application Server Java

XSS Java Components XSS Business Package

Required

Optional

Optional

Application Server Java

System Landscape Directory

Application Server Java

Adobe Document Services

Application Server Java

NetWeaver Development Infrastructure (NWDI)

Figure 3.12 SAP NetWeaver Java Dependencies for XSS

The SLD stores various types of data about your SAP (and non-SAP) landscape such as version information, development configurations, and connection data. The SLD is required by XSS for the connections from Web Dynpro-based iViews to the SAP ERP system. If the SLD goes down, your XSS applications wont be accessible. In Chapter 9, we discuss the impacts of this in great detail. Finally, XSS may lead to the introduction of SAP NetWeaver Development Infrastructure (NWDI) in your SAP landscape. NWDI is used to manage SAP Java development projects and is a separate SAP NetWeaver usage type that typically requires a dedicated AS Java system. XSS may need NWDI if your developers choose to customize SAPdelivered screens. We also discuss NWDI in detail in Section 9.4, SAP NetWeaver Development Infrastructure, of Chapter 9.

SLD and XSS

79

Business Package for Manager and Employee Self-Services

3.4

Development Impacts

As mentioned, XSS is probably one of the most widely implemented business packages and is also one of the only SAP software packages that has a heavy Java footprint and that has the source code delivered by SAP. XSS is also unique in that a lot of the portal configuration is actually contained on the ABAP side. For example, the navigation links from the main page area in ESS are actually configured in the IMG within the backend ECC system.
Customizing XSS

If you want to modify the delivered XSS functionality by custom development through configuration or new development, three main options are available for you to leverage. First, you can use Web Dynpro Implicit Personalization (WD Implicit Personalization). Second, you can modify the Java-based Web Dynpro components by editing source code or creating your own Java components. Finally, you can write new functionality on the ABAP side by using Web Dynpro or even classic Dynpro screens.

3.4.1

Web Dynpro Implicit Personalization

One of the most powerful features of Web Dynpro is the concept of Implicit Personalization. All of the Web Dynpro-based iViews in the XSS business package support WD Implicit Personalization. WD Implicit Personalization allows content administrators to make changes to the screens, such as adding text or hiding fields, using a WYSIWYG editor directly in SAP NetWeaver Portal. This is an important concept because functional teams typically want to make what they consider simple modifications that are more aesthetic and UI based, or example, changing the color of a text on a screen to produce emphasis, adding additional verbiage on a screen (i.e., benefit enrollment due date), or simply hiding fields that arent required functionality for a specific implementation. The changes made are stored as iView properties.
Note Its important to stress the fact that WD Implicit Personalization can be used to visually alter UIs with no additional configuration or development effort.

80

Development Impacts

3.4

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

3.4.2

Web Dynpro Implicit Personalization Example

As WD Implicit Personalization may be a new concept to even the most seasoned SAP NetWeaver Portal professionals, well walk through a quick example so you can see it in action. Our sample scenario has us modifying the header text for the ESS Overview application shown in Figure 3.13 to include specific company text.

Figure 3.13 ESS Screen Before WD Implicit Personalization

Because we want this change to apply to all users, the content administrator uses the portal content studio to edit the iView. WD Implicit Personalization is based on the objects runtime PCD URL, which means that you need to edit the iView from within its runtime structure. To put it another way, you shouldnt edit the iView as it sits under a PCD folder, but rather open the role where the iView resides and edit from here. In Figure 3.14, weve opened the Employee Self-Service role for editing.

Example

81

Business Package for Manager and Employee Self-Services

Figure 3.14 Overview Page Within the ESS Role Page editor

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

Figure 3.15 Overview Page

After further drilling down, select the Overview iView, and select the
Open button. Now were at the actual iView properties screen as shown

in Figure 3.16. From here, were ready to perform our modifications. WD Implicit Modifications are set from the iViews preview mode. Select the Preview button in Figure 3.16. In Figure 3.17, were now viewing the Overview application preview.

82

Development Impacts

3.4

Figure 3.16 Overview iView Properties

Figure 3.17 ESS Overview Screen Preview Mode

83

Business Package for Manager and Employee Self-Services

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

Figure 3.18 Web Dynpro Implicit Personalization Mode Applying customization

Once in the editor, youre given a list of the Web Dynpro elements on the screen, and you can personalize each individually. In Figure 3.19, we change the Semantic Color to the value Positive, change the value within the Text input field, and also check the box to Disable end user personalization for this iView. By disabling personalization for end users, you prevent them from Ctrl and right-clicking and customizing the iView for themselves. After saving, a series of iView properties are stored on the iView noting our changes. Now when we navigate to the ESS Overview page, we can see our changes, as shown in Figure 3.20. WD Implicit Personalization, including supporting documentation, isnt widely known by SAP professionals. Its extremely important that you and your project team explore this option to see if it meets your needs before deciding to go the route of custom code and moving into an NWDI implementation.

84

Development Impacts

3.4

Figure 3.19 Web Dynpro Implicit Personalization Modifications

Figure 3.20 After Web Dynpro Implicit Personalization

There are significant advantages to using this functionality rather than making code modifications. The primary reason is that you dont need to install and configure an NWDI infrastructure, thereby reducing overall costs. In addition, upgrades are much easier to manage because there is no code involved. With NWDI, you need to merge code into new releases of the product, which is quite a process as discussed in the next section. However, with WD Implicit Personalization, the iView properties arent impacted during an upgrade.

WD Implicit Personalization advantages

85

Business Package for Manager and Employee Self-Services

Note Another important advantage to WD Implicit Personalization is that when modifications are made in content administrator mode, they are transportable. This means a content administrator could make the changes in a DEV portal and have them transported through the environment. However, like other types of end-user personalization, end-user personalizations made in WD Implicit Personalization arent transportable.

The bottom line is that WD Implicit Personalization is a powerful feature to use and will greatly minimize your development and maintenance efforts.

3.4.3
Modify delivered source code

XSS Java Customization

If you need to perform modifications that cant be met by using WD Implicit Personalization, youll most likely need to modify the delivered source code, which is written in Java. SAP delivers the source code in the form of software component archives (*.sca). The only way to modify the source code is to implement NWDI and place the XSS archives under management by NWDI. There is in-depth discussion of NWDI in Chapters 9 and 10. After configuring NWDI for XSS, SAP NetWeaver Developer Studio (NWDS) is the tool used to carry out code modifications. If youre already using NWDI on your project, then this isnt a big deal to add additional Change Management Service (CMS) tracks because you probably already have the infrastructure in place to support XSS. However, if youre like most customers and new to NWDI and the Java-based SAP concepts such as the SAP Component Model, this will be a significant undertaking for your Basis and development teams. Its important to note that XSS modifications and more broadly Web Dynpro components are only supported as development components and require the use of NWDI. Unfortunately, when it comes to XSS, there is no backdoor manual workaround to avoid using NWDI on your XSS implementation if you require code modifications.

86

Resource Requirements

3.5

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

As previously stated, Java source code from the XSS components is modified using NWDS. However, in most cases, it helps if the Java resource performing the modifications possesses working knowledge of HR from an ABAP standpoint as well because many of the fields and screens for XSS are named after their functional counterparts. As shown in this section, the resources required for implementing NWDI can be significant both from an infrastructure and human capital perspective. Upgrades are also a somewhat manual process and can be very time consuming. Therefore, we strongly advise checking whether Web Dynpro Implicit Personalization can meet your needs before heading down the NWDI route.

Ideal developer skillset

3.4.4

XSS ABAP Development

As we outline in the next section, in addition to strong SAP NetWeaver Portal and Java resource, XSS implementations also often require someone with a strong ABAP background from a configuration and possibly development perspective because quite a bit of portal configuration is actually done on the ABAP side. Furthermore, if new functionality is required (e.g., a new form that isnt delivered in the XSS packages), then some project teams will opt to write the application as a Web Dynpro ABAP due to the fact that they most likely already have strong ABAP skills and may be light on Java. The nice thing about using Web Dynpro as the UI is that end users wont be able to tell the difference regardless of what language its written in (ABAP or Java).

3.5

Resource Requirements

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

87

Business Package for Manager and Employee Self-Services

figuration and vice versa or require a very good communication channel between these two individuals or teams. This is because much of the portal configuration in terms of runtime links and information is actually configured in the backend ECC application. Depending on your requirements, as a project manager, you should plan for the following resources on your project:
Typical project resources

SAP project manager who will be responsible for the coordination of all teams and managing the overall rollout SAP NetWeaver Basis team skilled in both Java and ABAP administration, especially configuring Web Dynpro JCo destinations, SLD, and potentially with the installation/configuration of NWDI Portal content developer to configure all PCD content from a portal perspective Java developer, if modifications to XSS are necessary, who also should possess knowledge of NWDI and how to use it with NWDS and the web-based tools Skilled technical HR ABAP resource to assist with any changes in the backend ECC system Overall, the project time frame for XSS can range anywhere from a few short weeks to many months. Several factors come into play, such as if this is a new HR rollout or an upgrade, and if there is no customization or several development objects. Project rollout size will also bear some weight on the amount of testing that adds in to the project time frame.

88

Index
A
ABAP user store 97 ABAP Workbench 249, 269 Active Component Framework (ACF) 250 Active Directory 181 Activity Data Collector 330 Adobe Document Services (ADS) 22, 70, 78, 243, 244, 245, 247, 251 Adobe Flex 156 Adobe LiveCycle Designer 249 AJAX 340 Application caching 311 Application component 172 Application FPN 47 Architecture 230 Business Package (cont.) for PPMDC 92, 94 For SAP SRM 170, 175 For SAP SRM 5.0 171 Portal configuration 184 Business Planning and Analytical Services 118 Business Planning role 121

C
Cache 310, 313, 316 Catalog Content Management (CCM) 170, 172 Catalog Procurement 178 cFolders 90, 92, 101, 185 Change and Transport System (CTS) 269, 283, 291 Change Management Service (CMS) 268, 270, 274, 279, 294 Collaboration 96, 124, 195 Component Build Service (CBS) 268, 270, 271, 275, 341 Component matrix 177 Component repository (CR) 261 Composite application 34, 44, 46, 89 Connector property 284 Consumer portal 45 Content administration role 363 Contract Management 195 cProjects 90, 92, 101 CPRXRPM 94, 95 CPRXRPM_UI 94, 95, 96 CRM (Customer Relationship Management) 91, 93, 197 CTS Deploy Web Service 301 CTS+ 296 CTS+ architecture 299 Custom code 308

B
BE Bidding Engine BEx (Business Explorer) Broadcaster 123 Portfolio 122 Web 338 Web Analyzer 120, 123, 148, 154 Bidding Engine (BE) 176, 180, 182, 186 Bidding scenarios 195 Broadcasting layout 122, 154 BSP (Business Server Page) 221, 227, 357, 365 BSP iView 365 Business area FPN 48 Business Explorer (BEx) 118 Role 122 Business Intelligence (BI) 54 Business Objects (BOBJ) 164 Business Package 31, 229 Configuration 209 for Employee and Manager Self-Services (XSS) 48 for PPM 90

383

Index

D
Data Supplier Bridge 265 Data Supplier Service 267 Dedicated xRPM Java system 100 Delta link 309 Design Time Repository (DTR) 268, 270, 274 Access through NWDI 270 Development Infrastructure (DI) 246 Digital signature 248 DMZ (Demilitarized Zone) 173, 179

G
Going Live Analysis 342

H
Hardware requirements of Java Development Infrastructure 274 Hardware sizing 308 High availability (HA) 104, 251, 265, 274 HTTP access 222

E
Enhanced CTS+ 292, 294, 295 Enhancement Package (EhP) 164, 340 Enterprise Buyer (EB) 176, 195 Enterprise Data Warehousing 118 Enterprise Reporting, Query, and Analysis 118 Enterprise service-oriented architecture (enterprise SOA) 339 eSourcing 194 ESS 68 ESS business package 66 External Portal 232

I
IAC (Internet Application Component) 172 ICH (Inventory Collaboration Hub) 173, 185 ICM (Internet Communication Manager) 314 IGS (Internet Graphics Server) 112 IMG (Implementation Guide) 211, 212 Industry-Specific SAP CRM Business Packages 207 Information Broadcasting 147, 152 Integrated ITS 231 Integrating FPN content 52 Interactive form 248 Internet Application Component (IAC) 220, 228 Internet Communication Framework (ICF) 257 ITS (Internet Transaction Server) 221, 357 iView 223, 224, 227 iView creation process 363

F
Federated portal performance 330 Financials Supply Chain Management (FSCM) 185 Floor Plan Manager (FPM) 64 FP_PDF_TEST_00 257 FPN (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

J
J2EE Administrator 317 Java Connector (JCo) 222, 238 Java Support Package Manager (JSPM) 31, 71 Java UME 97

384

Index

JCo destination 72, 73, 111, 145, 261, 265 JVM (Java Virtual Machine) 315

K
Knowledge Management (KM) 90, 96, 195, 216 Knowledge Management favorite 148 Knowledge Management transport 293

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

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

N
Navigation caching 311, 312 NetWeaver Business Client (NWBC) 343 Nonproduction SLD 265 NWA (NetWeaver Administrator) 325 Logging 327 NWDI (NetWeaver Development Infrastructure) 246, 261, 262, 268, 270, 272, 273, 275, 294, 295, 335, 341 NWDS (NetWeaver Development Studio) 246, 339

PCD (Portal Content Directory) (cont.) Organization 286 Performance 309 Performance 307, 309 Problem diagnosis 318 Tools 318 Pioneer 164 Plan Driven Procurement (PDP) 170, 178, 179 Portal Content Catalog 212 Content Composer 339 Content Directory (PCD) 283 Framework 47 Monitoring tools 327 Permissions 289 Transport editor 292 Transport package editor 292 PPM 90, 114 PPMD_WD_MODELDATA_DIST 111 PPMD_WD_RFC_METADATA_DIST 111 PPMDC business package 92, 93 Producer portal 45 Producer registration 59 Production SLD 264 Project and Portfolio Management 90 Project Manager 194

R
Remote Application Integration (RAI) 54, 149, 164 Remote Delta Link (RDL) 53, 54, 60, 105, 151 Remote Portlet 52 Remote Role Assignment (RRA) 53, 105, 151 RFC destination 257 RFC destination for CTS+ 302 RFx 174, 182 RFx1 171 Roles 202, 204, 205, 206 RZ10 350

O
Operational Purchaser 171

P
P4 connection 57 PCD (Portal Content Directory) 309 Cache 310

385

Index

S
SAINT 94 Sample transport process using Enhanced CTS+ 296 SAP Catalog Content Management 172 SAP Component Model 269 SAP composite application for Resource and Portfolio Management (xRPM) 48, 89 SAP CRM Architecture and landscape considerations 215 Business Package 200, 215 Business role upload 212 FPN scenarios 216 Frontend access methods 199 Overview 198 Portal integration with 199 Role upload 211 Usage scenarios 200 WebClient 202 SAP CRM 5.0 business package 203 SAP CRM Portal Content Configuration of 208 SAP CRM WebClient 210 SAP CRM WebClient UI 202 SAP Developer Network (SDN) 183 SAP Employee Self-Service (ESS) 64 SAP ERP 91, 93, 173, 176 SAP ERP HCM Administrative Services (ASR) 64 SAP Financials Supply Chain Management (FSCM) 185 SAP GUI 176, 226 for HTML 223 for Windows 223 SSO 226 SAP Help Portal 246 SAP IACs 184 SAP Interactive Forms by Adobe 100 SAP Inventory Collaboration Hub (ICH) 185, 187 SAP ITS Transaction iView 225 SAP LoadRunner 324 SAP Logon Ticket 347, 351, 361

SAP Manager Self-Service (MSS) 64 SAP NetWeaver 6.40 27 SAP NetWeaver 7.0 28 SAP NetWeaver 7.1 40 SAP NetWeaver Administrator (NWA) 260, 277, 325, 342 Configuration wizard 277 SAP NetWeaver BI 47, 49, 91, 101, 117, 171, 173, 176, 183, 184, 196, 250, 338 Content 93 Java 126, 134, 178 Java Software Development Kit (SDK) 162 SAP NetWeaver Business Client 343 SAP NetWeaver Composition Environment (SAP NetWeaver CE) 17, 38, 40, 339 SAP NetWeaver Developer Studio (NWDS) 36, 113, 246, 249 SAP NetWeaver Development Infrastructure (NWDI) 36, 79, 243, 246, 268 SAP NetWeaver Portal And Java UI configuration 107 SAP NetWeaver Process Integration (SAP NetWeaver PI) 176, 179, 195, 260, 264, 265, 299 Server 176 SAP NetWeaver Visual Composer (SAP NetWeaver VC) 17, 41, 156 SAP Online Help 183 SAP Project Self-Service (SAP PSS) 64 SAP Service Marketplace 107 SAP SRM 169, 183, 184 2007 195 2007 Business Package 195 5.0 170 6.0 170 7.0 194 ABAP UME 181 Administrator 171 Bidding Engine 173, 174 Business package 181, 183 Enterprise Buyer 178 MDM Catalog 172, 176, 178 SUS Supplier Self-Serivces

386

Index

SAP Supplier Network Collaboration 173 SAP transaction parameters 224 SAP transaction template 223 SAP Web Dispatcher 180, 232 Scaled NWDI landscape 274 SE80 246, 269 Security Provider Service 253 Self-Service Procurement 170 Service account 109 Service Marketplace 177, 183 Service Procurement 170 Sherlok 324 Single Sign-On (SSO) 71, 109, 111 Common requirement for FPN scenario 354 Configuration 354 SLD (System Landscape Directory) 22, 70, 71, 78, 102, 110, 243, 244, 245, 260, 266 Data Supplier Service 110 SM59 256, 301 Software Component Archive (SCA) 94, 269 Software Deployment Manager (SDM) 71, 304 Solution Manager 102, 183, 260, 264, 299, 300 Solution Manager Diagnostics 196, 322, 323, 342 Spend Analysis 170 SPNego 317 SRM (Supplier Relationship Management) 93 Strategic Sourcing 178 Strategic Sourcing Scenario 178 STRUSTSSO2 351 Supplier administrator 175 Supplier Application Starter 187 Supplier Collaboration 174, 180 Supplier Collaboration Business Package 170, 173, 175, 185 Supplier Portal Administration Role 193 Supplier Relationship Management (SRM) 91, 169

Supplier Self-Services (SUS) 171, 176, 179 Support Catalog Procurement 178 Synchronization of production and nonproduction SLD 266 System landscape object 284 System template 358

T
Template Installer 136, 277 Three-tiered landscape 104 Tracks 271 Trading partner directory (TPD) 171, 175, 187 Transport Management System (TMS) 292 Transport Organizer UI 304, 306

U
Universal Worklist (UWL) 124, 174, 195 User administration 175 User management 362 User Management Engine (UME) 51, 52, 347 store considerations 180 User management with FPN 51 User persistence 51

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

W
Web Application Designer 125 Web Based Transport Organizer 297 Web Dynpro 33, 336, 340 ABAP 228, 237, 340, 357, 361 Content Administrator 71, 72, 261 Implicit Personalization 80, 81, 84, 85 iView 176

387

Index

Web Dynpro (cont.) Java 228, 340, 364 Java application 187 JCo destination 266 Suspendability 315 WEB GUI 221, 225 Web Services 52, 114 Web Services for Remote Portlets (WSRP) 38 Web Services Navigator 255 Web-based Distributed Authoring and Versioning (WebDAV) 133, 270, 293 WebEx 90 Wily Introscope for SAP NetWeaver 322 WSRP (Web Services for Remote Portlets) 52 WYSIWYG tool 339

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

xRPM (cont.) And Adobe integration 100 Deployment scenario 99 Development impact 113 Java runtime component 110 Landscape considerations 103 Master Guide 107 Master Note 96 Production landscape 106 Setup 107 Software component 101 With FPN 105 XSS 48, 49, 51, 63, 64, 74, 77, 246, 250, 261, 266, 275 ABAP Development 87 And FPN 76 Components 63 Configuration 69 Configuration steps 71 Customizing 80 Installation requirements 70 Java Customization 86 Screens 64

Z
Zero Client Install (ZCI) 249

388