mySAP SRM

WebDynpro Technical
Configuration

SAP AG 2007

Objectives

Contents
z mySAP SRM WebDynpro Technical Configuration

Objectives
At the end of this chapter, you will be able to:
z Describe the WebDynpro (ABAP+Java) Architecture
z Perform the technical configuration of a WebDynpro ABAP
Application in SRM
z Perform the technical configuration of a WebDynpro JAVA
Application in SRM
z Understand WebDynpro Debugging

SAP AG 2007

SRM WebDynpro Overview

SRM WebDynpro ABAP Configuration
SRM WebDynpro JAVA Configuration
WebDynpro Debugging

SAP AG 2007

What is Web Dynpro?

Web Dynpro
Is SAPs strategic development environment for creating
professional UIs for business applications
Includes sophisticated runtime services
Minimizes manual coding because of its model-driven
approach
Uses visual tools to design and reuse UI components
Is based on a powerful and flexible Model View Controller
architecture that ensures a clear separation between UIs and
backend services
Gives developers full control of the generated code at all
stages of the development process

SAP AG 2007

WebDynpro Architecture
J2EE
J2EE
Backend
Backend
Server
Server

Business
Data

Web
Web Service
Service
Provider
Provider
Business
Data
Web
Service

EJB (e.a.)
RMI

ABAP
ABAP
Backend
BackendBusiness
Backend
Application
Server
Data
Server
Business
API (BAPI)

SOAP
RFC

Web Dynpro
Web DynproApp
App

SAP
NetWeaver
Developer
Studio

J2EE
J2EE
Web
Web Dynpro
Dynpro
Runtime
Runtime

ABAP
ABAP
Web
Web Dynpro
Dynpro
Runtime
Runtime

XML

Conversion
Conversion
of
of existing
existing
screens
screens
ABAP
ABAP Workbench
Workbench

Web Dynpro
Application

SAP
SAP Enterprise
Enterprise
Portal
Portal
SAP AG 2007

Web
Web Dynpro
Dynpro
Web
Dynpro
Web DynproApp
App
App
App

WebDynpro Application
A Web Dynpro application can be called from the user interface
It consists if a Controller, Model and a View component
It connects a user accessable URL with a WebDynpro window (View)
It contains no information about the elements of the corresponding
component or components behind the interface view

Request

Handlesevents
events
Handles
Updatesapplication
applicationdata
data
Updates
Definescontrol
controlflow
flow
Defines

Controller

Model

Response

SAP AG 2007

View

Defines
Definesapplication
applicationdata
data
Usually
connected
to
Usually connected to
business
businessfunctionality
functionality

Visualizes
Visualizesthe
theapplication
application
data
data

SRM WebDynpro Overview

SRM WebDynpro ABAP Configuration
SRM WebDynpro JAVA Configuration
WebDynpro Debugging

SAP AG 2007

WebDynpro ABAP (WDA) Configuration

Before developing Web Dynpro applications, the configuration settings
described below must be made:
HTTP/HTTPS must be set in the ICM (see graphics below)
ICF services must be activated. For more information see SAP note 517484.
SSO must be set up on the relevant application server (For details, see Unit
SRM Portal Configuration
Always use Fully Qualified Domain Names (FQDN)
Portal integration, the prerequisites described under Portal Integration
Requirements must be met. Also see SAP note 903662.
Setup Adobe Integration (if needed, see Unit SRM Adobe Configuration)

SAP AG 2007

ICF Services for WebDynpro ABAP

You
You can
can activate
activate an
an ICF
ICF service
service as
as follows:
follows:
1.
1. Select
Select the
the ICF
ICF service
service in
in the
the ICF
ICF tree
tree in
in transaction
transaction SICF.
SICF.
a)
a) For
For WebDynpro
WebDynpro ABAP,
ABAP, choose
choose
default
default host
host ->
-> sap
sap ->
-> bc
bc ->
-> webdynpro
webdynpro
2.
2. You
You can
can then
then activate
activate the
the services
services in
in one
one of
of the
the following
following ways:
ways:
a)
a) Menu
Menu option
option "Service/Virt.
"Service/Virt. Host
Host ->
-> Activate"
Activate"
b)
b) Context
Context menu
menu (right
(right mouse
mouse button)
button) and
and "Activate
"Activate service"
service"

SAP AG 2007

WebDynpro ABAP ICF Services Security

When creating Web applications using Web Dynpro for ABAP
programming models, and for the scenario variant Developing
ABAP Applications Using Web Dynpro, it is important to consider
security issues. Security functions are available both for when you
create Web applications as well as for when you operate them.
In a productive system the following HTTP service nodes
(transaction SICF) are not active for the Configuration, since a
configuration always represents a development:
/sap/bc/webdynpro/sap/CONFIGURE_APPLICATION
/sap/bc/webdynpro/sap/CONFIGURE_COMPONENT
/sap/bc/webdynpro/sap/WD_ANALYZE_CONFIG_APPL
/sap/bc/webdynpro/sap/WD_ANALYZE_CONFIG_COMP
/sap/bc/webdynpro/sap/WD_ANALYZE_CONFIG_USER

SAP AG 2007

Fully Qualified Domain Names (FQDN)

Always use Fully Qualified Domain Names

2
3

SAP AG 2007

Easy Portal Integration of Web Dynpro Applications

Easy
Easy integration
integration of
of Web
Web Dynpro
Dynpro applications
applications with
with the
the wizard.
wizard.
Application
Application parameters
parameters can
can be
be passed
passed to
to the
the Web
Web Dynpro
Dynpro application
application as
as
start-up
start-up parameters.
parameters.
SAP AG 2007

SRM WebDynpro Overview

SRM WebDynpro ABAP Configuration
SRM WebDynpro JAVA Configuration
WebDynpro Debugging

SAP AG 2007

WebDynpro Java - Technical Configuration Steps

11

22

33

44

55

66

SAP AG 2007

Create
Create and
and configure
configure users
users and
and
authorizations
authorizations
Create,
Create, Configure
Configure and
and distribute
distribute
certificates
certificates

Covered in Unit
SRM Portal Configuration

Create
Create WebDynpro
WebDynpro Alias
Alias

Create
Create and
and configure
configure the
the JCO
JCO
connections
connections
Covered on the following
Slides in this Unit
Perform
Perform the
the SAP
SAP license
license installation
installation

Perform
Perform aa configuration
configuration test
test

SRM WebDynpro JAVA Configuration

WebDynpro Alias Creation
JCO Configuration

SAP AG 2007

WebDynpro System Definition

Please Note:
The system object must be maintained, even if the WebDynpro and the
Portal are running on the same J2EE engine !

Systemobject:
WAS Hostname:
WAS path:

<SID WebDynpro>
H123456:5NN00

/webdynpro/dispatcher/

Systemalias:

SAP_WebDynpro

WebDynpro Application
Enterprise Portal
AS-JAVA

SAP AG 2007

SRM WebDynpro Java Connectivity

ALIAS
ALIAS
SAP_WebDynpro
SAP_WebDynpro

BP-SRM for Category Mgmt.

Enterprise Portal
WebDynpro Application
HTTP(S)
22

System Landscape Directory

AS-JAVA

JCO

33

RFC

RFM

SAP SRM Server (AS-ABAP)

SAP AG 2007

11

HTTP(S)

Connection to Category Management

Define
Define aa new
new system
system object
object for
for the
the
WebDynpro
WebDynpro System
System in
in the
the Portal
Portal
Configure
Configure itit as
as Web
Web AS
AS Connection
Connection
1

Do
Do not
not forget
forget to
to define
define the
the System
System Alias
Alias
SAP_WebDynpro
SAP_WebDynpro in
in the
the Portal
Portal

SAP AG 2007

SRM WebDynpro JAVA Configuration

WebDynpro Alias Creation
JCO Configuration

SAP AG 2007

JCO Communication in SRM CatMan Overview

Service

CatMan
1.
The SRM user calls
a service in the Web
browser

JCOUSER

J2EE

SAP SRM
Server

UME

2.

SAP SRM
Category Mgmt.

1.

Create a generic J2EE communication user (JCOUSER)

2.

Create the JCO connections

WD_CMA_RFC_METADATA_DEST for transferring metadata
and
WD_CMA_MODELDATA_DEST for transferring application data

SAP AG 2007

Web Dynpro - Content Administrator Tool

Start
Start URL
URL http://<webdynpro-hostname>:<port>/index.htm
http://<webdynpro-hostname>:<port>/index.htm

2
3

SAP AG 2007

WebDynpro JCO Connection Overview

There
There are
are many
many JCO
JCO connections:
connections:
Create
Create only
only those
those connection
connection which
which are
are required
required according
according to
to your
your
component
component installation
installation guide
guide
SAP AG 2007

WebDynpro Configure JCO Connections (1)

First
First step:
step:
Create
Create the
the connection
connection
Enter
Enter the
the destination
destination name,
name, and
and aa client
client
Enter
Enter Parameters
Parameters for
for the
the JCO
JCO Pool
Pool (optional)
(optional)

Do
Do not
not use
use Copy
Copy from
from existing
existing JCO
JCO destination,
destination, because
because an
an
undesired
language
setting
might
be
copied,
too.
undesired language setting might be copied, too.

SAP AG 2007

WebDynpro Configure JCO Connections (2)

Second
Second step:
step:

Choose
Choose J2EE
J2EE Engine
Engine

Choose
Choose Use
Use local
local Engine
Engine or
or

Enter
Enter J2EE
J2EE Engine
Engine of
of the
the desired
desired Portal
Portal

Please
Please note:
note:

The
The system
system name
name (in
(in this
this example
example E2E
E2E on
on
p163045)
p163045) is
is obtained
obtained from
from the
the SLD
SLD

Therefore
Therefore all
all systems
systems being
being used
used in
in JCO
JCO
Destinations
Destinations must
must be
be previously
previously defined
defined in
in the
the SLD
SLD
SAP AG 2007

WebDynpro Configure JCO Connections (3)

Third step:
Choose a connection type:
Meta Data
only used during the first connection to the application
general data, not user-specific
static data, small, is buffered in the memory of the generic SRMUSER
Application Data
used during second connection
data is user-specific
dynamic data, large, is buffered in the memory of the application user
(see SM04->Goto Memory)

SAP AG 2007

WebDynpro Example SelfService JCO Connections (4)

Fourth
Fourth step:
step:

Enter
Enter the
the hostname,
hostname, SID
SID and
and logon
logon group
group of
of
your
message
server
(of
the
SAP
SRM
System)
your message server (of the SAP SRM System)

The
The system
system name
name (in
(in this
this example
example
E2D
E2D on
on p163045)
p163045) is
is obtained
obtained
from
from the
the SLD
SLD
Therefore
Therefore all
all systems
systems being
being used
used
in
in JCO
JCO Destinations
Destinations must
must be
be
previously
defined
in
the
SLD
previously defined in the SLD

IfIf the
the JCO
JCO connection
connection is
is established
established through
through aa SAProuter,
SAProuter, the
the
SAProuter
SAProuter string
string can
can be
be specified
specified here
here
Format:
Format: /H/<routerhost>/S/<routerport>/S/<SAPhost>/S/<SAPport>
/H/<routerhost>/S/<routerport>/S/<SAPhost>/S/<SAPport>
SAP AG 2007

WebDynpro Example SelfService JCO Connections (5)

Fifth
Fifth step:
step:

Configure
Configure the
the user
user authentication
authentication

For
For Meta
Meta Data
Data Connections:
Connections:
Use
Use Method
Method User/Password
User/Password
For
For Application
Application Data
Data Connections:
Connections:
Use
Use Method
Method Ticket
Ticket
Use
Use the
the Ticket
Ticket which
which you
you
previously
previously created
created and
and imported
imported

Do
Do not
not set
set any
any language
language here.
here. The
The locale
locale settings
settings should
should be
be taken
taken
from
the
browser
frontend
of
the
individual
user.
from the browser frontend of the individual user.
SAP AG 2007

SLD JCO Connections to SRM CatMan Summary

As
As aa result,
result, all
all JCO
JCO connections
connections will
will appear
appear in
in the
the SLD:
SLD:
Choose
Choose Content
Content Maintenance,
Maintenance,
class
class JCO_Message_Server_Destinations
JCO_Message_Server_Destinations

1
2

SAP AG 2007

Portal Object to JCO Destination Assignment

IfIf you
you want
want to
to find
find out,
out, which
which JCO
JCO Destination
Destination is
is
used
used by
by which
which part
part of
of your
your application
application you
you can:
can:
Launch
Launch the
the WebDynpro
WebDynpro Content
Content Administrator
Administrator
Browse
Browse deployed
deployed content
content

1
2

In
In the
the General
General or
or Connection
Connection tab,
tab, you
you can
can see
see
the
the name
name of
of the
the respective
respective JCO
JCO Destination
Destination

3
4

SAP AG 2007

Open
Open aa WD
WD Model,
Model, for
for example
example
sap.com/srm~cma~ui~model
sap.com/srm~cma~ui~model

SRM WebDynpro Overview

SRM WebDynpro ABAP Configuration
SRM WebDynpro JAVA Configuration
WebDynpro Debugging

SAP AG 2007

Activate Debugging for WebDynpro ABAP

Debugging is possible on a
per-user basis
Activate HTTP Debugging in
the SRM Server:
SE80 -> Enter the name of
the RFC BAPI which you
want to debug
SE80 -> Utilities ->
Settings -> Tab Editor ->
Tab HTTP Debugging
Set HTTP breakpoint(s)

SAP AG 2007

Prepare Debugging for WebDynpro JAVA

Important Prerequisite for Debugging (especially when SSO is used):
Call the WebDynpro content administrator
Create or modify JCO destination WD_MODELDATA_DEST
Disable load balancing for this destination

SAP AG 2007

Activate Debugging for WebDynpro JAVA

In your NetWeaver Developer Studio, open the J2EE Engine view and
enable debugging for your J2EE server process

For detailed information, refer to http://service.sap.com/webdynpro

SAP AG 2007

Category Management Test JCO Connection

2a 3a

2b

3b

SAP AG 2007

Summary

Contents
z mySAP SRM WebDynpro Technical Configuration

Now you are able to:

z Describe the WebDynpro (ABAP+Java) Architecture
z Perform the technical configuration of a WebDynpro ABAP
Application in SRM
z Perform the technical configuration of a WebDynpro JAVA
Application in SRM
z Understand WebDynpro Debugging

SAP AG 2007

Copyright 2007 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p,
System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC
are trademarks or registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP 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 informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior
written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments,
and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this
document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items
contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This
limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in
these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

SAP AG 2007