SAP NetWeaver Master Data Management 5.5 SP3

SAP NetWeaver MDM 5.5 SP3 SAP Portal iViews Installation & Configuration

Ron HendrickxSAP NetWeaver RIG AmericasFoundation Team

SAP AG 2005, SAP NetWeaver MDM 5.5 SP3 SAP Portal iViews Installation & Configuration/ Ron Hendrickx / 2

Prerequisites

RequiredRequiredRequiredRequired::::

� Basic MDM knowledge

� Basic EP6 content management

RecommendedRecommendedRecommendedRecommended::::

� Experience with EP6 content administration


Agenda

Configuration demoConfiguration demoConfiguration demoConfiguration demo

Questions & answers Questions & answers Questions & answers Questions & answers

Connectivity with MDM repositoryConnectivity with MDM repositoryConnectivity with MDM repositoryConnectivity with MDM repository

Requirements and package contentRequirements and package contentRequirements and package contentRequirements and package content

MDM iViews capabilitiesMDM iViews capabilitiesMDM iViews capabilitiesMDM iViews capabilities

MDM Package installation in EP6MDM Package installation in EP6MDM Package installation in EP6MDM Package installation in EP6


MDM 5.5 SP3 Portal integration

Benefits•Easy to deploy

•Fast configuration

•Highly Flexible :

any repository

content display

•Support BLOB objects

•MDM Performances

•“SSO” enabled


MDM Portal iViews requirements

Portal :

� EP6 SP12 minimum

� If weak encryption J2EE installation (note 796540)

�Check Parameter ume.usermapping.unsecure=TRUE

� MDM JAVA API library build according to MDM server release

MDM server :

� 5.5 SP3 required

� It is recommended not to change the repository port once configured

Landscape constraints :

� All connected MDM servers should have the same build level, the build of the JAVA API used in portal.

� Used network ports open between portal and MDM servers

� Need to update JAVA API library if server build changes


Restrictions (note 822019)

See SAP Note 822018 “MDM 5.5 Release Restriction Note”.

Connection from Portal to MDM Server:

� works only with User Mapping (no Single Sign On SSO)

� it is language dependent: a system object must be created for a combination of MDM Server, Repository, Schema Language, and Repository Language. The languages must be set during design time of system object. – if wrong language is supplied to Connector API, then connection not possible to repository. The language must be preset. The language code in portal not the same with language code from MDM Server (allows regions). The language must be set in system object with a value code that exists in Repository.

� As a result: The iViews will display content in a language that is set in system object / alias. As a result: for each language a new iView must be created. A business package cannot be used in the same time by multiple users with different languages – if this is required, then each language must have its business package. The shipped business package is an English package.Theportal end user cannot choose a language since that is set in system object / alias and this is used by iViews.

Repository metadata must be available during iView design time. No change management supported for iViews.


Package components : SAP J2EE engine

SDA files (to deploy with SDM in the SAP J2EE engine) :

� com.sap.mdm.tech.mdm4j.sda : MDM for JAVA APIs, should be the same build as the MDM server used for connection=> to be deployed first

� com.sap.mdm.tech.connector.sda : MDM connector based on SAP Connector Framework & JCA 1.0=> to deploy after the API sda file

Maintenance/patch :

� Minimum : Deploy only the new mdm4j sda file according to the server build

� Alternative Update : deploy also the updated MDM connector sda file if you experienced connectivity problems, but you may need to update also the content (PAR files)

Benefits :

� You can also develop your own J2EE application and reuse the MDMopen connections through the MDM Connector.


Package components : Portal content

SCA files (to deploy with SDM in the SAP J2EE engine) will create portal content

� BPMDMTECHN00_0.sca => to be deployed first

� BPMDMAPPLI00_0.sca


Agenda








SDM tool for J2EE deployment

Start "SDM remote GUI"…

… and follow the wizard until confirmation\usr\sap\<SID>\JC00\SDM\program\RemoteGui.bat


Portal content deployment

Again, use SDM and follow the wizard to completion


Agenda








Configuration steps : connect MDM repository


Wizard for new repository connection


MDM connection : create alias (mandatory)

Alias is used in iviewsconfiguration settings


Check connection to MDM server

1

3

45

6

7

8

First, maintain user logondata to the created alias. 2


Agenda








Role

workset 1workset 1 workset 2workset 2 workset 3workset 3

WS2.1WS2.1 WS2.2WS2.2

service 1service 2service 3service 4

service 1service 2service 3service 4

service 1service 2

service 1service 2

Portal basics : content management

Role

A content template consisting of one or more worksets that model a typical job

Workset

A set of coherent activities that belong to one or more related work areas

Service

A (complex) task or service that is performed in the context of a workset : it can be a one or many pages containing one or many iviewsPage 1

Page 2

Page 1

íView 1iView 2


MDM iView library

� The MDM iView Library provides a set of iViews to search an MDM repository in multiple dimensions.

� By mixing and matching iViews, portal administrators can design and configure a collection of specialized portal pages for a specific set of user requirements, offering one or more highly tailored interfaces to the same repository.

The iViews are

� fully adaptive to the schema structure of the MDM repository to which they are connected

� Fully collaborative with other iViews on the page (eventing)

Design time


�Pick list search - for selecting values from flat or hierarchical lookup tablesoptions : list type, visible rows,

null/all display, width

MDM search criteria iViews

� Hierarchy search – for selecting nodes in hierarchical/ taxonomy lookup tablesOptions : load entire hierarchy

header visible, root node display

� Attribute search – for dynamic selection of attribute values connected to selected taxonomy nodesOptions : Attribute priority to display

view mode (Full/compact)width

Pick list search

Hierarchy search

Attribute search


MDM search related iViews

�Text search – for performing a free-form keyword search(need fields to be keyword)

Options : search typetext match type

�Show the current search state (active selection criterias)needed to remove defined search criteria or reset search

Text search

Search state


MDM data display iviews

Result set

�Show the current result list,according to the selected criteriaOptions : display columns

page size, width,image height

Item details

�Display/Change record details based on a selected record in the result setOptions : header fields

Item details fieldsTaxonomy fields (table)


Configured MDM Search page sample

Search and maintain functionalitySearch and maintain functionalitySearch and maintain functionalitySearch and maintain functionality

RuntimeRuntimeRuntimeRuntime


6 Steps for iViews configuration and page creation

1. Create needed iViews through the wizards by selecting accordingly the tables and fields to display/use as search criteria.

2. Create one page at least and add created iviews as content

3. Manage the iview arrangement in the page layout : select layout and use drag and drop for iviews relative positionning

4. Create a Workset and add created page to the workset. Set "Entry point" property to yes to enable menu entry in portal

5. Create a role and add created workset to the role.

6. Assign role to the user.

Note : user must maintain their user mapping before using the page.


Agenda








Thank you !

Additional Additional Additional Additional information:information:information:information:

http://service.sap.com/rkt-netweaver

http://service.sap.com/mdm -> installation and operation guides -> operation guides ->MDM :

� iViews library documentation

� https://websmp106.sap-ag.de/nw04operation for the BP install document

http://service.sap.com/nw-howtoguides -> Master Data Management :

� MDM Connector documentation

http://service.sap.com/installations�Navigate by "Entry by Application Group" and then Netweaver -> MDM -

> MDM 5.5


Contact


� 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, 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, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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

Copyright 2005 SAP AG. All Rights Reserved

SAP NetWeaver Master Data Management 5.5 SP3

Documents

Transcript of SAP NetWeaver Master Data Management 5.5 SP3