Upload
sachinjayade
View
32
Download
3
Embed Size (px)
Citation preview
©SAP AG 2007
mySAP SRM –WebDynpro Technical Configuration
© SAP AG 2007
Objectives
ContentsmySAP SRM WebDynpro Technical Configuration
ObjectivesAt the end of this chapter, you will be able to:
Describe the WebDynpro (ABAP+Java) ArchitecturePerform the technical configuration of a WebDynpro ABAP Application in SRMPerform the technical configuration of a WebDynpro JAVA Application in SRMUnderstand WebDynpro Debugging
©SAP AG 2007
SRM WebDynpro OverviewSRM WebDynpro ABAP Configuration
WebDynpro DebuggingSRM WebDynpro JAVA Configuration
© SAP AG 2007
What is Web Dynpro?
Web DynproIs SAP‘s strategic development environment for creatingprofessional UIs for business applicationsIncludes sophisticated runtime servicesMinimizes manual coding because of its model-drivenapproachUses visual tools to design and reuse UI componentsIs based on a powerful and flexible Model View Controller architecture that ensures a clear separation between UIs and backend servicesGives developers full control of the generated code at all stages of the development process
© SAP AG 2007
WebDynpro Architecture
J2EE Web Dynpro
Runtime
J2EE Web Dynpro
Runtime
Web Dynpro App
Web Dynpro AppWeb Dynpro
AppWeb Dynpro
App
SAP Enterprise Portal
SAP Enterprise Portal
Web DynproApplication
Web DynproApplication
XML
SAP NetWeaver Developer
Studio
SAP NetWeaver Developer
Studio
ABAP Web DynproRuntime
ABAP Web DynproRuntime
Web DynproApp
Web DynproAppWeb Dynpro
AppWeb Dynpro
App
ABAP WorkbenchABAP Workbench
Conversion of existing screens
Conversion of existing screens
J2EE Backend Server
J2EE Backend Server
Backend Application
Backend Application
ABAP Backend Server
ABAP Backend Server
Web Service ProviderWeb Service Provider
Web Service
Web Service
RMI SOAPRFC
BusinessData
BusinessData
BusinessData
BusinessAPI (BAPI)EJB (e.a.)EJB (e.a.)
© SAP AG 2007
WebDynpro Application
A Web Dynpro application can be called from the user interfaceIt consists if a Controller, Model and a View componentIt 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
ControllerRequest
ViewResponse
Model
Handles eventsUpdates application dataDefines control flow
Handles eventsUpdates application dataDefines control flow
Defines application dataUsually connected to business functionality
Defines application dataUsually connected to business functionality
Visualizes the application data
Visualizes the application data
©SAP AG 2007
SRM WebDynpro OverviewSRM WebDynpro ABAP Configuration
WebDynpro DebuggingSRM WebDynpro JAVA Configuration
© 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 can activate an ICF service as follows:
1. Select the ICF service in the ICF tree in transaction SICF.
a) For WebDynpro ABAP, choose “default host -> sap -> bc -> webdynpro”
2. You can then activate the services in one of the following ways:
a) Menu option "Service/Virt. Host -> Activate"
b) Context menu (right mouse button) and "Activate service"
You can activate an ICF service as follows:
1. Select the ICF service in the ICF tree in transaction SICF.
a) For WebDynpro ABAP, choose “default host -> sap -> bc -> webdynpro”
2. You can then activate the services in one of the following ways:
a) Menu option "Service/Virt. Host -> Activate"
b) Context menu (right mouse button) and "Activate 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)
1
3
2
Always use Fully Qualified Domain Names
© SAP AG 2007
Easy Portal Integration of Web Dynpro Applications
Easy integration of Web Dynpro applications with the wizard. Application parameters can be passed to the Web Dynpro application as
start-up parameters.
Easy integration of Web Dynpro applications with the wizard. Application parameters can be passed to the Web Dynpro application as
start-up parameters.
©SAP AG 2007
SRM WebDynpro OverviewSRM WebDynpro ABAP Configuration
WebDynpro DebuggingSRM WebDynpro JAVA Configuration
© SAP AG 2007
WebDynpro Java - Technical Configuration Steps
Create and configure users and authorizations
Create and configure users and authorizations
Create, Configure and distributecertificates
Create, Configure and distributecertificates
Create WebDynpro AliasCreate WebDynpro Alias
Create and configure the JCO connections
Create and configure the JCO connections
Perform the SAP license installationPerform the SAP license installation
11
22
33
44
55
Perform a configuration testPerform a configuration test66
Covered in Unit “SRM Portal Configuration”
Covered on the followingSlides in this Unit
©SAP AG 2007
SRM WebDynpro JAVA ConfigurationWebDynpro Alias CreationJCO Configuration
© SAP AG 2007
WebDynpro System Definition
AS-JAVA
Enterprise Portal
<SID WebDynpro>Systemobject:
WAS Hostname: H123456:5NN00
/webdynpro/dispatcher/WAS path:
Systemalias: SAP_WebDynpro
Please Note:
WebDynpro Application
The system object must be maintained, even if the WebDynpro and thePortal are running on the same J2EE engine !
© SAP AG 2007
SRM WebDynpro Java Connectivity
AS-JAVA
WebDynpro Application
SAP SRM Server (AS-ABAP)
System Landscape Directory
Enterprise Portal
JCO
RFM
RFC
HTTP(S)
HTTP(S)
BP-SRM for Category Mgmt. ALIAS SAP_WebDynpro
ALIAS SAP_WebDynpro
11
22
33
© SAP AG 2007
Connection to Category Management
Define a new system object for the
WebDynpro System in the Portal
Configure it as “Web AS Connection”
Do not forget to define the System Alias„SAP_WebDynpro“ in the Portal
Define a new system object for the
WebDynpro System in the Portal
Configure it as “Web AS Connection”
Do not forget to define the System Alias„SAP_WebDynpro“ in the Portal
2
3
1
©SAP AG 2007
SRM WebDynpro JAVA ConfigurationWebDynpro Alias CreationJCO Configuration
© SAP AG 2007
JCO Communication in SRM CatMan – Overview
SAP SRMServer
SAP SRMCategory Mgmt.
J2EE
UME
CatMan
Service
1.
2.
1. Create a generic J2EE communication user („JCOUSER“)
2. Create the JCO connectionsWD_CMA_RFC_METADATA_DEST for transferring metadataandWD_CMA_MODELDATA_DEST for transferring application data
The SRM user callsa service in the Web
browser
JCOUSER
© SAP AG 2007
Web Dynpro - Content Administrator Tool
Start URL http://<webdynpro-hostname>:<port>/index.htmStart URL http://<webdynpro-hostname>:<port>/index.htm
1
2
3
© SAP AG 2007
WebDynpro – JCO Connection Overview
There are many JCO connections:Create only those connection which are required according to your
component installation guide
There are many JCO connections:Create only those connection which are required according to your
component installation guide
1
3
2
© SAP AG 2007
WebDynpro – Configure JCO Connections (1)
First step:Create the connection
Enter the destination name, and a client
Enter Parameters for the JCO Pool (optional)
First step:Create the connection
Enter the destination name, and a client
Enter Parameters for the JCO Pool (optional)
Do not use „Copy from existing JCO destination“, because an undesired language setting might be copied, too.Do not use „Copy from existing JCO destination“, because an undesired language setting might be copied, too.
1
© SAP AG 2007
WebDynpro – Configure JCO Connections (2)
Second step:Choose J2EE Engine
Choose „Use local Engine“ or
Enter J2EE Engine of the desired Portal
Second step:Choose J2EE Engine
Choose „Use local Engine“ or
Enter J2EE Engine of the desired Portal
2
Please note:The system name (in this example „E2E on
p163045“) is obtained from the SLD
Therefore all systems being used in JCO Destinations must be previously defined in the SLD
Please note:The system name (in this example „E2E on
p163045“) is obtained from the SLD
Therefore all systems being used in JCO Destinations must be previously defined in the 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)
3
© SAP AG 2007
WebDynpro Example – SelfService JCO Connections (4)
Fourth step:Enter the hostname, SID and logon group of your message server (of the SAP SRM System)
Fourth step:Enter the hostname, SID and logon group of your message server (of the SAP SRM System)
If the JCO connection is established through a SAProuter, theSAProuter string can be specified here
Format: /H/<routerhost>/S/<routerport>/S/<SAPhost>/S/<SAPport>
If the JCO connection is established through a SAProuter, theSAProuter string can be specified here
Format: /H/<routerhost>/S/<routerport>/S/<SAPhost>/S/<SAPport>
4
The system name (in this example„E2D on p163045“) is obtainedfrom the SLD
Therefore all systems being usedin JCO Destinations must bepreviously defined in the SLD
The system name (in this example„E2D on p163045“) is obtainedfrom the SLD
Therefore all systems being usedin JCO Destinations must bepreviously defined in the SLD
© SAP AG 2007
WebDynpro Example – SelfService JCO Connections (5)
Fifth step:Configure the user authentication
For Meta Data Connections:
Use Method „User/Password
For Application Data Connections:
Use Method „Ticket“
Use the Ticket which you previously created and imported
Fifth step:Configure the user authentication
For Meta Data Connections:
Use Method „User/Password
For Application Data Connections:
Use Method „Ticket“
Use the Ticket which you previously created and imported
Do not set any language here. The locale settings should be takenfrom the browser frontend of the individual user.Do not set any language here. The locale settings should be takenfrom the browser frontend of the individual user.
5
© SAP AG 2007
SLD JCO Connections to SRM CatMan – Summary
As a result, all JCO connections will appear in the SLD:
Choose “Content Maintenance”,
class “JCO_Message_Server_Destinations”
As a result, all JCO connections will appear in the SLD:
Choose “Content Maintenance”,
class “JCO_Message_Server_Destinations”
1
2
© SAP AG 2007
Portal Object to JCO Destination Assignment
If you want to find out, which JCO Destination is used by which part of your application you can:
Launch the WebDynpro Content Administrator
Browse deployed content
Open a WD Model, for examplesap.com/srm~cma~ui~model
In the „General“ or „Connection“ tab, you can seethe name of the respective JCO Destination
If you want to find out, which JCO Destination is used by which part of your application you can:
Launch the WebDynpro Content Administrator
Browse deployed content
Open a WD Model, for examplesap.com/srm~cma~ui~model
In the „General“ or „Connection“ tab, you can seethe name of the respective JCO Destination
1
3
2
4
©SAP AG 2007
SRM WebDynpro OverviewSRM WebDynpro ABAP Configuration
WebDynpro DebuggingSRM WebDynpro JAVA Configuration
© 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 debugSE80 -> Utilities -> Settings -> Tab Editor -> Tab HTTP DebuggingSet HTTP breakpoint(s)
© SAP AG 2007
Prepare Debugging for WebDynpro JAVA
Important Prerequisite for Debugging (especially when SSO is used):Call the WebDynpro content administratorCreate or modify JCO destination WD_MODELDATA_DESTDisable load balancing for this destination
© SAP AG 2007
Activate Debugging for WebDynpro JAVA
In your NetWeaver Developer Studio, open the J2EE Engine view andenable debugging for your J2EE server process
For detailed information, refer to http://service.sap.com/webdynpro
© SAP AG 2007
Category Management – Test JCO Connection
1 2a
2b
3a
3b
© SAP AG 2007
Summary
ContentsmySAP SRM WebDynpro Technical Configuration
Now you are able to:
Describe the WebDynpro (ABAP+Java) ArchitecturePerform the technical configuration of a WebDynpro ABAP Application in SRMPerform the technical configuration of a WebDynpro JAVA Application in SRMUnderstand 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.