Portal 72723b

\j2ee\JSPM directory to launch JSPM Enter SDM , so that JSPM can connect to SDM

© SAP 2008 / LES Portal Advanced Page 14

Page 7

JSPM – Deployment Options Choose „Deployment“, and then „New Software Components“ to apply new Java components to an existing system


SDM – Deploy Business Package SRM 7.0


Page 8





Page 9

Checking the Deployment Logon Logon to to your your portal portal with with an an , , go to to Content Content istration istration -> Portal Portal Content. Content. The The following following objects objects should should be be added added to to your your portal portal content: content:


Demo - Creating a new portal iView

Select iView template

Create portal iView

Edit the portal iView for defining parameters etc


Page 10

Pick up the iView and add to navigation

Creating a new portal iView




Page 11





Page 12





Page 13





Page 14





Page 15



Agenda

re ictu r a p slide o f ple er sam e divid in th

Introduction Migration Strategy SRM Business Packages Portal Connections Authentication & SSO Configuration Portal Roles & s UWL Configuration Netweaver Business Client Appendix – Multiple SRM Integration


Page 16

Systems and System Aliases To use the Business Package for SAP SRM 7.0, you must create a system object in the Portal to establish a connection to the SAP SRM 7.0 server. You must assign the alias SAP_SRM to this system object. For the Business Intelligence (BI) Reports to be displayed, you must create an additional system object which points to a SAP BI system. You must assign the alias SAP_BW to this system object. This following slides outline how to configure the following: Creating System Objects Configuring System Objects for Backend Systems Creating and Adding a Backend System Alias Portal layer Business package for SAP SRM 7.0

Portal core http(s)

SAP BW 7.0 BI_CONT 7.0.3

WD

SAP R/3 back-end system

SAP SRM 2007 server

FI/CO

Basis plug-in EBP

SAP R/3 plug-in


Connection to AS-ABAP (in SRM System)


Page 17

Connection to AS-ABAP (in SRM System)

Press next and open the new system for editing


Connection to AS-ABAP (in SRM System) 2 1

3


Page 18

Connection Alias to SRM System

The portal alias is an unique alias name representing a system connected to the portal.


Performing a Connection Test


Page 19

Agenda

re ictu p a r de le fo ider sli p m v sa e di in th

Introduction Migration Strategy SRM Business Packages Portal Connections Authentication & SSO Configuration Portal Roles & s UWL Configuration Netweaver Business Client Appendix – Multiple SRM Integration


Portal WebDynpro Authentication

: ABC BP-SRM WebDynpro Application Enterprise Portal AS-JAVA

Important facts: Identical name in all systems Local assignment to roles/ authentications

Certificate

: ABC

SAP SRM Server (AS-ABAP)


Page 20

Certificate Configuration

To To implement implement Single Single Sign-On Sign-On (SSO), (SSO), Certificates Certificates must must be be created created and and distributed distributed

SRM System

Enterprise Portal + Web Dynpro Java System

ABAP

J2EE

1. 1. Create Create Portal Portal Certificate Certificate 2. 2. Export Export Portal Portal Certificate Certificate

3. 3. Import Import Portal Portal Certificate Certificate 4. 4. Distribute Distribute Portal Portal Certificate Certificate

For For aa detailed detailed description, description, see see SAP SAP Note Note 711768 711768


Enterprise Portal - Create Portal Certificate

Create Create aa new new Portal Portal certificate, certificate, by by using using the the “Keystore “Keystore istration” istration” utility utility in in the the Enterprise Enterprise Portal Portal

1

2


Page 21

SRM System - Import Portal Certificate

Import Import the the Portal Portal Certifcate Certifcate (Example: (Example: KTP.cert) KTP.cert) into into the the backend backend system system (/nSTRUSTSSO2) (/nSTRUSTSSO2) Choose Choose type type “Base64” “Base64” and and “Add “Add to to certificate certificate List” List” Now, Now, the the new new System System (here:KTP) (here:KTP) appears appears in in the the SSO SSO List List

3

2

1

4 © SAP 2008 / LES Portal Advanced Page 43

SAP SRM System – Distribute Certificate Do Do not not forget forget to to distribute distribute the the Certificates Certificates

1


Page 22

SAP SRM System – Check SSO Profile Parameters Parameter : /accept_sso2_ticket = 1 Parameter : /create_sso2_ticket = 2 Example: /accept_sso2_ticket: Description: You can use SSO tickets to allow Single Sign-On (SSO) between SAP systems, and even beyond to nonSAP systems. An SSO ticket can be a logon ticket or an assertion ticket. The logon ticket is transferred as a cookie with the name MYSAPSSO2.The assertion ticket is transferred as an HTTP header variable with the name MYSAPSSO2. SSO component systems should permit logon by SSO ticket (/accept_sso2_ticket = 1). Procedure (for all involved SAP systems): 1.

Logon to the SRM system via SAPGui

2.

Open transaction /nrz10 (Edit profiles)

3.

Display your R3 instance profile (extenden maintenance option)

4.

Check both parameters and create them if not available


SAP SRM System – Check SSO Profile Parameters

1

2

3

4


Page 23

Agenda


Introduction Migration Strategy SRM Business Packages Portal Connections Authentication & SSO Configuration Portal Roles & s UWL Configuration Netweaver Business Client Appendix – Multiple SRM Systems


Management Scenarios There are a number of potential scenarios for Management: Use Application Server ABAP as Data Source Use Database as Data Source Use LDAP Directory as Data Source

Enterprise Portal UME

LDAP Data Source

Local DB


Page 24

ABAP Data Source

Management Scenario – ABAP data source s accessed from the ABAP data source Add the ECC roles and SRM roles for a and assign portal roles in the Enterprise Portal Logon to ECC system Add the roles for this in the ECC system Logon to the SRM system Add the roles for this in the SRM System Logon to the Enterprise Portal and access the through the istration tab (as a Portal ) ECC roles and the SRM roles appear as Assigned groups for the in the Enterprise Portal Assign the appropriate portal roles for this to access the content of the Business Package for SRM7.0

Enterprise Portal (Assign Portal roles) ECC roles as *Groups* SRM roles as *Groups*

ABC

SRM system (Assign roles) ABC (PPOMA_BBP attributes)

ECC System (Assign roles)

ABC


Agenda




Page 25

Universal Worklist - Feature Overview

The Universal Worklist enables SAP portal s to manage their work by bringing together assignments from different workflow systems. Features of the UWL are: Gives you a unified and centralized way to access your work and the relevant information Aggregates workflow task items from multiple and different systems in one universal list (example: SRM, ESS, etc..) Displays additional information as required from document and object repositories, including attachments and other details Enables you to make direct decisions and actions Helps you to personalize how work items are presented Enables you to assign another to your work items as a substitute in case of planned or unplanned absence


Configure the Universal Worklist (UWL) Configure the Universal Worklist for the Business Package for mySAP SRM 7.0 A system connection for the SRM backend must already exist Create the UWL system: System istration System Configuration Universal Worklist & Workflow Universal Worklist istration New the UWL system under: System istration System Configuration Universal Worklist & Workflow Universal Worklist istration


Page 26

Change UWL configuration With SRM 7.0 an own UWL Configuration file is delivered for displaying alerts and tasks within the UWL iView. The UWL Configuration File is delivered as part of the SRM 7.0 Business Package (Configuration Name: com.sap.pct.srm.core). the configuration file (in zip-format) to your local machine. Goto System istration System Configuration Universal Worklist & Workflow Universal Worklist istration Click to istrate Item Types and View definitions


Change UWL configuration – rename tab entry points As an example let’s change the name of the tab names. “My Alerts” should be displayd instead of “Alerts”. The names of tabs are specified in the corresponding language files within the UWL configuration zip-file. For example, pick up the english language file com.sap.pct.srm.core_en.properties to do this.


Page 27

Change UWL configuration – tab entries

Change the name to „my Alerts“, save it and put it back to the UWL configuration file.


new UWL configuration After changing the XML file, put the XML configuration file into the zip-archive and the modified version into the Portal. Goto “ New Configuration”, specify the configuration name, pick up the zip-file and it to the portal, press “yes, if you are asked to overwrite the current configuration.


Page 28

Change UWL configuration – rename tab entry points Result: name of the tab changed to My Alerts Recommendation: to makes sure that your configuration won’t be overwritten after a Business Package update, simply change the configuration name and the configuration zip file. the new configuration to your portal. Example: com.sap.pct.srm.core.customer and com.sap.pct.srm.core.customer.zip


Change UWL configuration – disable tab entry points Example: disable notification tab

Solution: 1. open the com.sap.pct.srm.core.xml file and goto entry Tab: Notification 2. delete the entries for notifications and save your file 3. put the com.sap.pct.srm.core.xml file back to your zip archive and the configuration


Page 29

Agenda




Using SAP Netweaver Business Client in SRM 7.0 About SAP Netweaver Business Client: The SAP NetWeaver Business Client (NWBC) is a new, desktop-based SAP integration platform that provides end s with a seamless integration of portalbased transactions, classic SAP GUI-based transactions, and new applications developed in Web Dynpro (ABAP and Java). Existing browser-based SAP applications can also be integrated. With the new UI front end of the Business Client existing UI portal services such as roles and navigation can be reused. The NetWeaver Business Client is interface (UI) software running on the desktop that communicates via HTTP(s) to a server in order to display application interfaces. The interfaces make it easy for the to start the required application. Fully ed by Business Suite applications.


Page 30

Using SAP Netweaver Business Client in SRM 7.0 Main Components of Business Client UI: The frame contains standard menu entries in the upper area, and miniature images of open sessions and transactions that enable simple navigation between screens (session tab area). The left part of the screen contains the role-based functions for the (home area). The actual transaction the is working in is displayed on the canvas or application content area. The canvas represents the native technology in which the source application created its screens. Practically all standard UI technologies can be presented on a canvas: Portal applications Web Dynpro ABAP/Java applications BSP Applications HTML pages, Interactive forms and print forms (pdf) Dynpro screens based on the classic dynpro programming model of SAP


Using SAP Netweaver Business Client in SRM 7.0


Page 31

Working with the SAP Netweaver Business Client Before you start: Install the SAP Netweaver Business Client Software on your local machine. Please follow the documentation on SAP Service Marketplace. Or, logon to the SAP Citrix Client. You will find a SAP Netweaver Business Client Installation on your desktop.

Double klick on the SAP Netweaver Business Client Icon on your desktop


Working with the SAP Netweaver Business Client In the first step you have to connect the Business Client to your SRM 7.0 system.


Page 32

Working with the SAP Netweaver Business Client



Select your SRM system and press „Switch To“. Now, you will be asked for /.


Page 33





Page 34

Additional Informations SAP Netweaver Business Client help pages NWBC Wiki pages: http://nwbc.wdf.sap.corp:1080/

SAP Help: http://help.sap.com/saphelp_nw70/helpdata/EN/46/961aa951b3581ce10000000a155 3f7/frameset.htm


Agenda




Page 35

Example: Integration of two SRM 7.0 systems into a single portal instance Redirect to SRM System1

1

SRM 7.0 System 1 Logon to portal

(Development)

Alias 1

Portal Instance 2

Logon to portal Redirect to SRM System2

SRM 7.0 System 2 (Q-System)

Alias 2


Example: one portal and two SRM 7.0 systems Prerequisites: SRM 7.0 SP01/SP02 SRM s are unique, means you don’t have the same ID in different SRM systems. SRM 7.0 Business Package SP01/SP02 deployed Single-Sign-On is configured as described in Solution Manager

Steps in detail: 1.

Create two SRM 7.0 systems with two alias names. An alias is an unique identifier for every system connected to the portal.

2.

Create two UWL system connections based on the alias names used in step 1.

3.

Create a new portal folder for new content


Page 36

Example: one portal and two SRM 7.0 systems

Steps in detail: 4.

Copy all SRM 7.0 roles to the new portal folder (Delta Copy).

5.

Change ID and names of the copied roles.

6.

Change the default alias SAP_SRM for all iViews which are linked to the copied roles.

7.

Assign new roles to portal s

8.

Test connections

Demo-Portal: http://p190963.wdf.sap.corp:50000/irj/portal

Demo-: de_manager/training and maneu/training * Check the Appendix - 1 for a detailed step-by-step instructions


Further Information

SAP Public Web: SAP Developer Network (SDN): http://www.sdn.sap.com/ General Portal Information: https://www.sdn.sap.com/irj/sdn/netweaver Portal on SDN: http://www.sdn.sap.com/irj/sdn/nw-portalandcollaboration SAP Help Portal: http://help.sap.com/ Search for SAP Notes: http://service.sap.com/notes Product Availability Matrix http://service.sap.com/pam SP Stack Schedule http://service.sap.com/sp-stacks http://www.sap.com/platform/netweaver/itpractices/productivity.epx

Related SAP Education and Certification Opportunities http://www.sap.com/education/


Page 37

Copyright 2008 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. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are trademarks or ed trademarks of SAP AG in and in several other countries all over the world. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or ed trademarks of Business Objects S.A. in the United States and in several other countries. Business Objects is an SAP Company. All other product and service names mentioned and associated logos displayed 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. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Business Objects und das Business-Objects-Logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius und andere im Text erwähnte Business-Objects-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der Business Objects S. A. in den USA und anderen Ländern weltweit. Business Objects ist ein Unternehmen der SAP. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen. Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, nur mit ausdrücklicher schriftlicher Genehmigung durch SAP AG gestattet. Bei dieser Publikation handelt es sich um eine vorläufige Version, die nicht Ihrem gültigen Lizenzvertrag oder anderen Vereinbarungen mit SAP unterliegt. Diese Publikation enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts. SAP entsteht aus dieser Publikation keine Verpflichtung zu einer bestimmten Geschäfts- oder Produktstrategie und/oder bestimmten Entwicklungen. Diese Publikation kann von SAP jederzeit ohne vorherige Ankündigung geändert werden. SAP übernimmt keine Haftung für Fehler oder Auslassungen in dieser Publikation. Des Weiteren übernimmt SAP keine Garantie für die Exaktheit oder Vollständigkeit der Informationen, Texte, Grafiken, Links und sonstigen in dieser Publikation enthaltenen Elementen. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. SAP haftet nicht für entstandene Schäden. Dies gilt u. a. und uneingeschränkt für konkrete, besondere und mittelbare Schäden oder Folgeschäden, die aus der Nutzung dieser Materialien entstehen können. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. Die gesetzliche Haftung bei Personenschäden oder Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab. Alle Rechte vorbehalten. © SAP 2008 / LES Portal Advanced Page 75

Page 38

Portal 72723b

Overview 5o1f4z

More details 6z3438

Related Documents c2h70

Portal 72723b

Shopping Portal 6y5d2m

Student Portal 3b6u3n

Alumni Portal e255m

Portal - Uaq 6e3y20

Portal Akademik 713b3o