How-to Guide

SAP xApps

How To…
Write xRPM
Custom iView
in ABAP Web
Dynpro Using
Java Web
Services
Version 1.00 – April 2007

Applicable Releases:
SAP xRPM 4.0
© Copyright 2005 SAP AG. All rights reserved. These materials are subject to change without notice. These
materials are provided by SAP AG and its affiliated companies
SAP Library document classification: PUBLIC ("SAP Group") for informational purposes
only, without representation or warranty of any kind, and SAP
No part of this publication may be reproduced or transmitted in Group shall not be liable for errors or omissions with respect to
any form or for any purpose without the express permission of the materials. The only warranties for SAP Group products and
SAP AG. The information contained herein may be changed services are those that are set forth in the express warranty
without prior notice. statements accompanying such products and services, if any.
Nothing herein should be construed as constituting an additional
Some software products marketed by SAP AG and its warranty.
distributors contain proprietary software components of other
software vendors. These materials are provided “as is” without a warranty of any
kind, either express or implied, including but not limited to, the
Microsoft, Windows, Outlook, and PowerPoint are registered implied warranties of merchantability, fitness for a particular
trademarks of Microsoft Corporation. purpose, or non-infringement.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, SAP shall not be liable for damages of any kind including
MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, without limitation direct, special, indirect, or consequential
pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, damages that may result from the use of these materials.
WebSphere, Netfinity, Tivoli, and Informix are trademarks or SAP does not warrant the accuracy or completeness of the
registered trademarks of IBM Corporation in the United States information, text, graphics, links or other items contained within
and/or other countries. these materials. SAP has no control over the information that
you may access through the use of hot links contained in these
Oracle is a registered trademark of Oracle Corporation. materials and does not endorse your use of third party web pages
nor provide any warranty whatsoever relating to third party web
UNIX, X/Open, OSF/1, and Motif are registered trademarks of pages.
the Open Group.
SAP NetWeaver “How-to” Guides are intended to simplify the
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, product implementation. While specific product features and
VideoFrame, and MultiWin are trademarks or registered procedures typically are explained in a practical business
trademarks of Citrix Systems, Inc. context, it is not implied that those features and procedures are
the only approach in solving a specific business problem using
HTML, XML, XHTML and W3C are trademarks or registered SAP NetWeaver. Should you wish to receive additional
trademarks of W3C®, World Wide Web Consortium, information, clarification or support, please refer to SAP
Massachusetts Institute of Technology. Consulting.

Java is a registered trademark of Sun Microsystems, Inc. Any software coding and/or code lines / strings (“Code”)
included in this documentation are only examples and are not
JavaScript is a registered trademark of Sun Microsystems, Inc., intended to be used in a productive system environment. The
used under license for technology invented and implemented by Code is only intended better explain and visualize the syntax and
Netscape. phrasing rules of certain coding. SAP does not warrant the
correctness and completeness of the Code given herein, and SAP
MaxDB is a trademark of MySQL AB, Sweden. shall not be liable for errors or damages caused by the usage of
the Code, except if such damages were caused by SAP
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP intentionally or grossly negligent.
NetWeaver, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or
registered trademarks of SAP AG in Germany and in several
other countries all over the world. All other product and service
names mentioned are the trademarks of their respective
companies. Data contained in this document serves information
purposes only. National product specifications may vary.
Content
Introduction ...................................................................................................................................... 5
Prerequisites ................................................................................................................................ 5
Using SAP xRPM 4.0 Java Web Service..................................................................................... 5
Deploying SAP xRPM 4.0 Java Web Service in SAP NetWeaver Application Server............. 5
Creating an RFC Destination ................................................................................................... 5
Configuring Logical Port ........................................................................................................... 6
Writing Custom iView in Web Dynpro for ABAP ...................................................................... 7
Access xRPM4.0 UI Web Service in ABAP Web Dynpro controller ........................................ 8
Creating a new Web Dynpro for ABAP Project ...................................................................... 10
Create ABAP Web Dynpro Application .................................................................................. 11
Placing Custom iView on xRPM4.0 Navigation Panel ........................................................... 11
Introduction
With this documentation, you can write xRPM custom iView in ABAP Web Dynpro for your
business needs. To get required the xRPM object context information from the Java side, SAP
provides a Java web service for requesting object context information. This document gives you
guideline on how to use xRPM Java web service in ABAP Web Dynpro and how to integrate the
custom iView into the SAP xRPM standard solution in SAP Enterprise Portal (EP).

Prerequisites
• The SAP_QAP_LPCONFIG role has been assigned to your user, to work on logical port
configuration.
• You have knowledge of ABAP Web Dynpro.
• You understand the basics of how the web service works.
• It is beneficial to be familiar with SAP system transactions.
• You have downloaded and installed SAP NetWeaver. You can deploy Java Web Service
into the SAP NetWeaver application server and browse the service using the web service
navigator. You can develop your ABAP Web Dynpro application using SAP Web Dynpro
for ABAP. All tools for ABAP development are integrated in the ABAP Workbench and are
delivered with the SAP NetWeaver application server ABAP (SAP NW AS ABAP). ABAP
development takes place on a central development system.

Using SAP xRPM 4.0 Java Web Service

Deploying SAP xRPM 4.0 Java Web Service in SAP NetWeaver
Application Server
• You can skip this step if CPRXRPMUI08_0.sca has been deployed already.
• To use the provided web service, you need to start SAP software deployment manager,
deploy sap.com~xapps~cprxrpm~webservice.ear into application server.
• There are two development components in Java stack to handle Java side web services.
One is xapps~cprxrpm~webservice~ejb~sap.com, which is an EJB component to handle
business logic, another is xapps~cprxrpm~webservice~sap.com, which is the wrapper DC
for java web service.
• The provided EJB service has the following methods that are available in the generated
client proxy in ABAP:
{ GET_RPMOBJECT_GUID
{ GET_RPMOBJECT_ID
{ GET_RPMOBJECT_TYPE
{ GET_RPMPARENT_GUID
{ GET_RPMPORTFOLIO_GUID

Creating an RFC Destination

...

1. Logon to your SAP backend development system and go to transaction sm59.

2. Create an RFC connection using connection type G HTTP Connections to External
Server.
3. In the Technical Settings tab page, setup target system settings of your Java Web Service
server as follows:
{ Target Host: <servername.domainname> or <server IP address>
 Service No.: Port number of service such as 53000
{

Path Prefix: /RPMUIContext/Config1/porttypes?wsdl&style=document

{

You can use the default settings for all other settings.
Example

Configuring Logical Port

...

1. Choose transaction LPConfig and choose /RPM/CO_UICONTEXT_VI_DOCUMEN proxy

class.
2. Enter logical port ZRPM_JAVA
3. On the Call Parameters tab page, choose HTTP Destination and select RPMPORT you
defined in Creating an RFC Destination section.
Example

Writing Custom iView in Web Dynpro for ABAP

Generating Client Proxy
You can skip this step if you want to use /RPM/CO_UICONTEXT_VI_DOCUMEN as client proxy
to access xRPM Java Web Services.
...

1. Right click on the chosen package, to show the context menu. Choose Create →
Enterprise Service / Web Service → Proxy Object.
2. In the subsequent dialog box, choose URL/http destination as the WSDL source.
3. Enter the URL of the WSDL document for the SAP xRPM Java Web Service that is already
deployed in the portal as follows:
<protocol>://<server>.<domain>:<port>/RPMUIContext/Config1?wsdl&style=document.
For example: http://pwdf2720.wdf.sap.corp:53000/RPMUIContext/Config1?wsdl
4. In the subsequent dialog box, enter the name of the package where you want to create the
proxy objects. To avoid naming conflicts with names that already exist in the system, you
can also specify a prefix for the names of all objects to be created.
The generated proxy is as follows and contains several available methods as mentioned before:
Accessing SAP xRPM 4.0 UI Web Service in ABAP Web Dynpro
Controller
In the custom controller or component controller, create a method for xRPM Java web service call.
SAP provides the class /RPM/CL_PORTAL_CONTEXT to handle web service using call.
Example

For example, the method Get_User_Object_Guid is as follows:

Creating a new Web Dynpro for ABAP Project
SAP delivers the ABAP Web Dynpro project example: /RPM/WEBSERVICE_EXAMPLE. For
information about how to call the web service methods provided as described in class
/RPM/CL_PORTAL_CONTEXT, you can refer to the method GETRPMUICONTEXT in the view
WEBSERVICEVIEW. For example, call get_user_object_guid.
If you have an ABAP Web Dynpro project, you can skip the following step.
...

1. In your SAP system, choose transaction se80.

2. To create a Web Dynpro project, right click the package and then choose Create → Web
Dynpro → Web Dynpro component.

Creating ABAP Web Dynpro Application

...

1. In the same package, go to context menu.

2. Create an ABAP Web Dynpro application by choosing Create → Web Dynpro → Web
Dynpro application.

Placing Custom iView on SAP xRPM 4.0 Navigation Panel

As ABAP Web Dynpro iView and Java Web Dynpro iView might sit in different systems, you need
to create the system for ABAP Web Dynpro iView separately.
Creating an ABAP Web Dynpro System
...

1. Logon to the portal and choose System Administration → System Configuration.

2. Choose System Landscape → Portal Content. For example in the Systems folder, create a
system ABAP_WebDynpro. In WAS AS part, make the following settings:

3. Enter the system alias, for example ABAP_WebDynpro.

Creating iView in Portal Content

...

1. Create an iView in the portal using the custom application you created under Content
Administration → Portal Content → Content provided by SAP → End user content → Proj.
Port.Mgmt. and Design Coll. → iViews → Portfolio Management.
2. The iView ID prefix is: com.sap.pct.cprxrpm
Name space: rpm
Note: You have to create the iView by choosing iView Template → SAP Web Dynpro iView →
Web Dynpro for ABAP.
Creating Portal Page
...

1. Create a portal page using the default portal page with one column.
2. Enter the custom iView you created into the page.

Adding to Workset
...

1. Open Portfolio Management workset including hidden pages.

2. Add your page into a hidden page, for example, Portfolio Hidden.

Setting Up Customizing
...

1. Go to SAP xRPM 4.0 backend Customizing and define navigation links, by choosing Global
Customizing → Process and Service Settings → Define Navigation. Specify description,
tool tip, link type, relative navigation and Portal Page ID in Link Definition.
2. The link definition is derived from PCD location of your page which is added to the workset
hidden page.
{ The full PCD location looks like this:
portal_content/com.sap.pct/every_user/com.sap.pct.cprxrpm.ppmdc/com.sap.pct.cp
rxrpm.worksets/com.sap.pct.cprxrpm.ws_port_mgmt/com.sap.pct.cprxrpm.port_hidd
en/mypage.
{ The link definition is the part after
com.sap.pct.cprxrpm.worksets/com.sap.pct.cprxrpm.ws_port_mgmt/, for example,
com.sap.pct.cprxrpm.port_hidden/mycustomiview.
3. If a new link group is necessary, create Link Groups Definition. Map link groups to an
object context.
4. Add the link definition of the page to the link group elements of the link groups definition, for
example, portfolio management link group.
5. Save your entries.

As a result, a new link will be shown in SAP xRPM 4.0 navigation panel. By clicking the link, your
custom iView is rendered in the portal.