SAP NetWeaver MDM MDM Import and Syndication Server & Port Concept

Transcription

1 Welcome to your RKT Live Expert Session SAP NetWeaver MDM MDM Import and Syndication Server & Port Concept Michael Reil SAP NetWeaver Product Management Please note that we are recording this session!

2 Your Instructor Michael Reil SAP NetWeaver MDM Product Management SAP AG 2005, SAP NetWeaver MDM / 2

3 SAP NetWeaver MDM MDM Import and Syndication Server & Port Concept

4 Content Overview MDM 5.5 SP03 Port Concept Encapsulates all of the configuration and logistical information associated with inbound and outbound processing MDM Import Server Load master data records periodically from various sources MDM Syndication Server Distribute master data records periodically to defined destinations SAP AG 2005, SAP NetWeaver MDM / 4

5 New Components in the Architecture Thin Client Search / View Data Maintenance OCI User Interface Rich Client Data Manager Image Manager Import Manager Publisher Syndicator Major Building Blocks Import Server Import Core Server Services Parsing Loading Structural Mapping Value Mapping Parsing Record Matching Key Mapping Key Matching Master Data Server Core Services Memory Cache Database Abstraction Repository Management Syndication Server Syndication Core Services Server Extraction Structural Mapping Value Mapping Number Extraction Assignment Key Mapping Structural Transformation Transformation Key Mapping Value Mapping Scheduling Inbound Ports Raw Object Data Outbound Ports Messages SAP NetWeaver XI SAP NetWeaver Application Server SAP NetWeaver XI Inbound Processing API / Monitoring Outbound Processing SAP AG 2005, SAP NetWeaver MDM / 5

6 In the context of MDM IT Scenarios Master-Data Consolidation Load Master Data Consolidate Master Data Master-Data Harmonization Load Master Data Consolidate Master Data Distribute Master Data Central Master-Data Management MDM Import Server Create Master Data Distribute Master Data MDM Syndication Server SAP AG 2005, SAP NetWeaver MDM / 6

7 Port Concept Overview What is a Port*? Key Information encapsulated by a Port Name Display Name Code Technical Name (name of the folder) Type Direction (inbound or outbound) Format File Format (e.g. Excel, XML Schema) XML Schema XML Schema file (e.g. DEBMDM06.xsd) Client System Client System Map Map File Basis for automated Imports & Exports A port represents the logical point of contact between MDM and the outside world (e.g. SAP XI or a user of the MDM Import Manager). It represents the physical staging location of data and a logical handle by which to identify all of the encapsulated information. Ports are designed to eliminate inbound and outbound processing complexity By eliminating manual selections, ports reduce the likelihood of errors, which could lead to incorrect or incomplete processing Features Program Files SAP MDM 5.5 Server Distributions DBMS Server Repository Direction Client System Port Benefits SAP AG 2005, SAP NetWeaver MDM / 7 * For further details see MDM Console User Guide

8 Port Concept Configuration Five Steps to configure Ports Step 1 to 3 are prerequisites to be able to create ports. If Client Systems with assigned maps are already exist only step 4 and 5 is relevant. Configure Ports Click to start screen cam 1 Create a New Client System Any logical system that can supply data to or receive data from MDM is known as a client system. 2 Assign Import Map To transfer maps among client systems they can be exported into a map file in the file system. These map files can be import into another client system. 3 Assign Syndication Map (see 2) 4 Create Inbound Port How to create a port for inbound processing 5 Create Outbound Port How to create a port for outbound processing SAP AG 2005, SAP NetWeaver MDM / 8

9 Port Concept Configuration (cont.) Five Steps to configure Ports (cont.) Automatically created Folder Structure The files associated with ports are stored in a shared file system location with a fixed directory structure beneath a configurable root. Its location is specified in the mds.ini file: [MDM Server] Distribution Root Dir=C:\Program Files\SAP MDM 5.5\Server\Distributions\ The following folder structure was automatically created as result of the described port configuration: Configure Ports Program Files SAP MDM 5.5 Server Distributions DBMS Server Repository Direction Client System Port SAP AG 2005, SAP NetWeaver MDM / 9

10 Use Case MDM Import Server* Overview Automated Import Load master data records periodically from various sources based on the extended port concept. This new component separates the core processing of source data import to a background process (service), from the front-end processing (import map generation). Can be utilized in addition to MDM Import Manager or Import Mgr Batch. Create an import map once, and re-use of the map for future source data import without any operator intervention Once the data is delivered by SAP XI on a specific port, it will automatically get picked within a configurable time interval and queued up for import processing The outcome of the import processing are updated or new master data records in the repository and log files of the entire load process Master data imports can be easily automated and run in the background No user interaction required Provides monitoring capabilities for data import Enables scalability and load balancing for data imports SAP AG 2005, SAP NetWeaver MDM / 10 Features MDM Import Manager (GUI) MDM Server Repository MDM Import Server Benefits * Currently available for Windows platform

11 MDM Import Server Further Information Service* MDM Import Server run-time configuration can be specified in mdis.ini file, which is located in the install directory oft MDM Import Server. Technical Details Ports** Encapsulates all of the configuration and logistical information associated with inbound and outbound processing of data from client systems. Extended port folder structure to store log files. Runtime Since by definition a service does not have a UI, the MDM Import Server functionality may be checked using the tools available on the platform that the service is deployed on. MDM Import Server connects to each repository in order, then retrieves inbound distribution port info and imports the data. new Program Files SAP MDM 5.5 Server Distributions Log Files Status Files Source Files DBMS Server Repository Direction Client System Port Monitoring Capabilities Step-by-step audit trail of the import and a status indicating whether the import succeeded or not. These log files are accessible via MDM Console. Availability monitoring integrated into CCMS SAP AG 2005, SAP NetWeaver MDM / 11 Export Import * Currently available for Windows platform ** For further details see MDM Console User Guide Log Files

12 MDM Import Server Configuration mdis.ini file Server Interval Automap Unmapped Value Unmapped Value Handling Always Use Unmapped Value Handling [Customers*] Specifies the computer name of the MDM Server which MDM Import Server connects to Specifies the time interval between import cycles Determine if unmapped values should be mapped automatically if possible If set to true the following Unmapped Value Handling is activated IgnoreNewValue = 0 or AddNewValue = 1 (see images at the bottom) This section is created for each loaded repository and supplies the connection parameters for that repository Configuration All other configuration is kept in the import maps! SAP AG 2005, SAP NetWeaver MDM / 12

13 MDM Import Server Example This example shows an automated import Load Customer Records 1 Start MDM Import Server service The MDM Import Server will be started manually in this case. To automatically start the MDM Import Server change the start type to Automatic. 2 Deliver data file to port The data file (XML message) will be copied into the port folder Ready. In a real business environment the data would be delivered by SAP XI. 3 Monitor import processing results Log files (stored in the port folder Log) are accessible via MDM Console. 4 Review master data records and key mapping Use the MDM Data Manager to review the newly imported master data records and corresponding key mapping. Click to start screen cam SAP AG 2005, SAP NetWeaver MDM / 13

14 Use Case MDM Syndication Server* Overview Automated Export Distribute master data records periodically to defined destinations based on the extended port concept. This new component separates the core processing of master data export to a background process (service), from the front-end processing (syndication generation). Can be utilized in addition to MDM Syndicator or Syndicator Batch. Create a syndication once, and re-use of the syndication for future master data export without any operator intervention Delivers master data records as data files (e.g. XML messages) to outbound ports triggered by a simple scheduling mechanism The outcome of the export are data files (e.g. XML messages) for further processing by SAP XI and log files of the entire syndication process Features MDM Syndicator (GUI) MDM Server Repository MDM Syndication Server Master data exports can be easily automated and run in the background No user interaction required Provides monitoring capabilities for data export Enables scalability and load balancing for data exports SAP AG 2005, SAP NetWeaver MDM / 14 Benefits * Currently available for Windows platform

15 MDM Syndication Server Further Information Service* MDM Syndication Server run-time configuration can be specified in mdss.ini file, which is located in the install directory oft MDM Syndication Server. Technical Details Ports** Encapsulates all of the configuration and logistical information associated with inbound and outbound processing of data from client systems. Extended port folder structure to store log files. Runtime Since by definition a service does not have a UI, the MDM Syndication Server functionality may be checked using the tools available on the platform that the service is deployed on. MDM Import Server connects to each repository in order, retrieves outbound distribution port info and exports the data. new Program Files SAP MDM 5.5 Server Distributions Log Files Data Files DBMS Server Repository Direction Client System Port Monitoring Capabilities Step-by-step audit trail of the export and a status indicating whether the export succeeded or not. These log files are accessible via MDM Console. Availability monitoring integrated into CCMS SAP AG 2005, SAP NetWeaver MDM / 15 Export Import * Currently available for Windows platform ** For further details see MDM Console User Guide Log Files

16 MDM Syndication Server Configuration mdss.ini file MDM Server Name Specifies the computer name of the MDM Server which MDM Syndication Server connects to Configuration Auto Syndication Task Enabled Auto Syndication Task Delay String Resource Dir Default Interface Language Code & Default Interface Country Code Boolean parameter tells whether the MDM Syndication Server should start upon startup: true start / false do not start Specifies the time interval between auto export cycles. Zero means starting next cycle right away (continuous execution). Delay parameter is read in the end of each cycle Specifies the location of language files Parameters are not relevant at the moment [Customers*] This section is created for each loaded repository and supplies the connection parameters for that repository All other configuration is kept in the syndication maps! SAP AG 2005, SAP NetWeaver MDM / 16

17 MDM Syndication Server Example This example shows an automated export Distribute Master Data 1 Review Port Configuration In this case there are three outbound ports defined. One of them (NCS2) is configured to generate new keys for records sent to this client system. 2 Start MDM Syndication Server service The MDM Syndication Server will also be started manually. To automatically start the MDM Import Server change the start type to Automatic. 3 Examine data in the port folder structure The data files (here XML messages) are stored in the port folder Ready. In a real business environment the data files would picked-up by SAP XI for further processing. 4 Monitor import processing results Log files (stored in the port folder Log) are accessible via MDM Console. 5 Export Results Data and Log files have been created for all defined outbound ports. Key mapping was updated accordingly. Click to start screen cam SAP AG 2005, SAP NetWeaver MDM / 17

18 MDM Syndication Server Export Results 1 Situation before the first MDM Syndication Server run 2 Updated data will be sent to client system NCS1 3 New data will be sent to NCS2 with a new target system specific key 4 Key mapping information will be updated accordingly 5 Exemplary key mapping information for a BI system SAP AG 2005, SAP NetWeaver MDM / 18

19 Hints and Troubleshooting A port is locked for the duration of import, meaning no other import with MDM Import Manager can be done using this port The same applies for MDM Syndication Server MDM Import Server can not trigger workflows on import (planned enhancement for next release) Batch files can be used to start or stop MDM Import Server and MDM Syndication Server instead of navigating through the Windows menus Hints Grayed out No data available or port is locked To stop use option stop instead of start If an MDM Import Server run failed the according inbound port will be locked. To unlock the port do the following steps: Troubleshooting Check log file to find out if the issue is related to the data and/or map If caused by an incorrect map stop MDM Import Server Connect to port using MDM Import Manager and check Import Status Repair and save map (do not execute import!) Leave MDM Import Manager and start MDM Import Server again Verify if data now has been processed successfully The same applies for MDM Syndication Server SAP AG 2005, SAP NetWeaver MDM / 19

20 Thank you for your kind interest Questions?? Please do not hesitate to ask them now SAP AG 2005, SAP NetWeaver MDM / 20

21 Copyright 2005 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, 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 SAP AG 2005, SAP NetWeaver MDM / 21