Application Operations Guide. SAP NetWeaver Master Data Management global data synchronization option 2.0

Transcription

1 Application Operations Guide SAP NetWeaver Master Data Management global data synchronization option 2.0 Document Version 1.0 March 11, 2009

2 SAP AG Neurottstraße Walldorf Germany T +49/18 05/ F +49/18 05/ Copyright 2009 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, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. 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. SAP, R/3, xapps, xapp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAP s Support Services and may not be modified or altered in any way. Documentation in the SAP Service Marketplace You can find this documentation at the following Internet address: service.sap.com/instguides

3 Typographic Conventions Type Style Example Text Example text EXAMPLE TEXT Example text Example text <Example text> EXAMPLE TEXT Represents Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation Emphasized words or phrases in body text, titles of graphics and tables Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE. Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. Keys on the keyboard, for example, function keys (such asf2) or the ENTER key. Icons Icon Meaning Caution Example Note Recommendation Syntax

4 Application Operations Guide for SAP NetWeaver MDM GDS Getting Started Global Definitions Important SAP Notes History of Changes Technical System Landscape Scenario/Component Matrix Related Documentation Monitoring of GDS Alert Monitoring with Computer Centre Management System (CCMS) Installing and Setting Up CCMS Monitoring Component-Specific Monitoring Detailed Monitoring and Tools for Problem and Performance Analysis Trace and Log Files Workload Monitors Management of SAP NetWeaver MDM GDS Starting and Stopping Restarting the GDS Console Software Configuration Backup and Restore Application Copy Periodic Tasks Scheduled Periodic Tasks Required Manual Periodic Tasks Load Balancing User Management Printing High Availability (HA) Software Change Management GDS Console MDM Server Troubleshooting MDM is down XI Messages Are Not Sent Out Message Does Not Return to GDS Console March 2009

5 Application Operations Guide for SAP NetWeaver MDM GDS No Menu Item for MDM user Cannot Find an Existing Trade Item Support Desk Management Remote Support Setup Problem Message Handover Appendix Related Guides Related Information...23 March

6 Getting Started Global Definitions 1 Getting Started This guide does not replace the daily operations handbook that we recommend customers create for their specific production operations. About this Guide Designing, implementing, and running your SAP applications at peak performance 24 hours a day has never been more vital for your business success than now. This guide provides a starting point for managing your SAP applications and maintaining and running them optimally. It contains specific information for various tasks and lists the tools that you can use to implement them. This guide also provides references to the documentation required for these tasks, so you will sometimes also need other Guides such as the Master Guide, Technical Infrastructure Guide, and SAP Library. Target Groups Technical Consultants System Administrators Solution Consultants Business Process Owner Support Specialist 1.1 Global Definitions SAP Application: An SAP application is an SAP software solution that serves a specific business area like ERP, CRM, PLM, SRM, SCM. Business Scenario: From a microeconomic perspective, a business scenario is a cycle, which consists of several different interconnected logical processes in time. Typically, a business scenario includes several company departments and involves with other business partners. From a technical point of view, a business scenario needs at least one SAP application (SAP ERP, SAP SCM, or others) for each cycle and possibly other third-party systems. A business scenario is a unit which can be implemented separately and reflects the customer s prospective course of business. Component: A component is the smallest individual unit considered within the Solution Development Lifecycle; components are separately produced, delivered, installed, and maintained. 6 March 2009

7 1.2 Important SAP Notes 1.2 Important SAP Notes Check regularly for updates available for the Application Operations Guide. 1.3 History of Changes Make sure you use the current version of the Application Operations Guide. The current version of the Application Operations Guide is at service.sap.com/instguides on SAP Service Marketplace. The following table provides an overview of the most important changes in prior versions. Version Important Changes 1.0 First version of the GDS Application Operations Guide (previously Solution Operations Guide) 1.1 Updated section 3.1 according to ITSAM validation March

8 Technical System Landscape Scenario/Component Matrix 2 Technical System Landscape 2.1 Scenario/Component Matrix SAP NetWeaver MDM GDS consists of the following components: Back-end system (SAP ERP, SAP ECC, or any other system that can send messages to XI) SAP NetWeaver Process Integration (SAP NetWeaver XI 7.0) MDM Server (Release 7.1) and underlying database (MS SQL, Oracle, or DB2) GDS Console - Java-based application running on SAP NetWeaver Application Server (SAP NetWeaver Application Server) Third-party components o Seeburger AS2 adapter o 1Sync data pools 2.2 Related Documentation The following table lists where you can find more information about the technical system landscape. Topic Guide/Tool Quick Link on SAP Service Marketplace (service.sap.com) Application- and Industryspecific Components such as SAP Financials and SAP Retail Technology Components such as SAP NetWeaver Application Server Master Guide Master Guide instguides instguides Sizing Quick Sizer Tool sizing Technical Configuration Master Guide instguides Scalability Master Guide instguides High Availability Master Guide instguides Security Security Map Application Security Guide security instguides 8 March 2009

9 3.1 Alert Monitoring with Computer Centre Management System (CCMS) 3 Monitoring of GDS Within the management of SAP Technology, monitoring is an essential task. A section has therefore been devoted solely to this subject. You can find more information about the underlying technology in the Technical Operations Manual for SAP Technology in the SAP Help Portal at help.sap.com Documentation SAP NetWeaver SAP NetWeaver 7.0 System Administration Technical Operations Manual. 3.1 Alert Monitoring with Computer Centre Management System (CCMS) Proactive, automated monitoring is the basis for ensuring reliable operations for your SAP system environment. SAP provides you with the infrastructure and recommendations needed to set up your alert monitoring to recognize critical situations for GDS as quickly as possible. CCMS is the Sap NetWeaver standard system that provides central access to the supportability and operability data of the complete landscape Installing and Setting Up CCMS Monitoring The CCMS agent connects to the central monitoring system (CEN) and uploads a configuration file which describes your monitoring scenario. 1. Install the CCMS agent. The CCMS agent connects to the central monitoring system (CEN) and uploads a configuration file which describes your monitoring scenario. For more information about installing the CCMS agent, see SAP Help Portal at help.sap.com SAP NetWeaver SAP NetWeaver 7.0 SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Solution Monitoring Monitoring in the CCMS Configuring the Monitoring Architecture Monitoring: Configuring Java Instances Installing an Agent on a Java Instance. 2. Connect the CCMS agent to the central monitoring system. The central monitoring system must have a release status of SAP Basis 4.6B with ABAP stack of version 6.40 or higher. For more information about support packages that may be required, see SAP Note Upload the configuration files to the central server: a) On the host of the J2EE Engine of the portal, switch to one of the following directories: Microsoft Windows UNIX <J2EE Home directory>\jc<inst. No.>\j2ee\admin\ <J2EE Home directory>/jc<inst. No.>/j2ee/admin/ If you installed the J2EE engine together with an ABAP engine, the character combination in the name of thejc<inst. No.> directory in the above path may vary. b) Start the Visual Administrator by calling the start scriptgo (UNIX) orgo.bat(microsoft Windows), and log on with your user as the J2EE engine administrator. March

10 Monitoring of GDS Alert Monitoring with Computer Centre Management System (CCMS) c) In the navigation bar, choose Cluster Server Services Monitoring, and then choose the GRMG Customizing tab. d) Expand the left side of the screen. All applications that have a prepared GRMG customizing file are displayed. e) Choose <sap.com/is~gds~core~monitoring~app>. f) Transfer the customizing file to the CCMS agent by choosing the Upload pushbutton. g) Repeat steps e) and f) withsap.com/is~gds~ui~monitoring~app. Additional steps in CEN: h) Call transaction GRMG by choosing the Upload pushbutton. Browse and open the appropriate GRMG customizing XML file: GDS Core Monitoring GDS UI Monitoring GRMG_<hostname>_<SID>_<Inst. No.>_sap.com~is~gds~core~monitoring~app.xml GRMG_<hostname>_<SID>_< Inst. No.>_sap.com~is~gds~ui~monitoring~app.xml 4. Log on to the CEN and start the GRMG scenario. 5. Select the newly uploaded scenario. 6. Open the context menu of the start/stop element and choose Start scenarios. A green check mark indicates that the scenario has been successfully started. The SAP recommended monitoring template is SAP GDS2.0 Monitor Set. If you would like to create a customized template, you can use the GRMG_GDS and GRMG_GDS_UI monitoring tree elements (MTEs) for GRMG heartbeat monitoring. You can find the by using the CCMS_GETMTE_BY_CLASS rule when you are creating a rule based node. If the CCMS agent is connected to the Central Monitoring System, you can select that as the R3 System parameter, and enter the GRMG_GDS and GRMG_GDS_UI as MTE class. Change the node name and save the changes. In order to enable the auto-alert mechanism of CCMS, see SAP Note For more information about the monitoring template, see SAP Note Component-Specific Monitoring For information, see SAP Help Portal at help.sap.com Documentation SAP NetWeaver SAP NetWeaver 7.0 System administration Operations Monitoring. Availability Monitoring Monitor Monitoring Object Description GDS BL and UI Application Business Logic This scenario monitors the Business Logic function of GDS GDS BL and UI Application WebDynpro User Interface This scenario monitors the WebDynpro Application of the 10 March 2009

11 3.2 Detailed Monitoring and Tools for Problem and Performance Analysis GDS GDS UI Components WebDynpro User Interface This scenario monitors the WebDynpro Components of the GDS To check the availability of a component, use the following steps: 1. Log on to CEN and call transactionrz Choose SAP Global Data Synchronization 2.0 from the SAP GDS20 Monitor Set. 3. Expand the GDS BL and UI Application and/or GDS UI Components subtrees. Available components are displayed in green Unavailable components are displayed in red 3.2 Detailed Monitoring and Tools for Problem and Performance Analysis Trace and Log Files Trace files and log files are essential for analyzing problems. Important Log and Trace files Component Content File Path UI Core Response Import Export UI component log messages Core component log and trace messages Respone message processing related logs and traces Import message processing related logs and traces Export message processing related logs and traces gds_ui gds gds_export_response gds_import gds_export \log\applicati ons\com.sap.gd s\ \log\applicati ons\com.sap.gd s\ \log\applicati ons\com.sap.gd s\ \log\applicati ons\com.sap.gd s\ \log\applicati ons\com.sap.gd s\ All log and trace entries can be viewed in the log viewer of NetWeaver Administrator. For more information about the log viewer, see SAP Help Portal at help.sap.com SAP NetWeaver SAP NetWeaver 7.0 SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology Administration Manual Supportability and Performance Management Logging Log Configuration. The following categories are relevant for the GDS application logs: Category Description /Applications/GDS General log messages March

12 Monitoring of GDS Detailed Monitoring and Tools for Problem and Performance Analysis /Applications/Common/Security/GDS /Applications/GDSExportProcess /Applications/GDSExportResponseProcess /Applications/GDSImportProcess Security related log messages Export message related logs Response message processing related logs Import message processing related logs The following locations are relevant for the GDS application: Location Description com.sap.gds General trace messages com.sap.gds.core.tmimport Import message processing related traces com.sap.gds.core.export Export message related traces com.sap.gds.core.response Response message processing related traces All categories are set to effective severity level Info, and all trace locations are set to effective severity level Error by default. To increase either severity level, go to the Log Configurator of the Visual Administrator. For more information, see see SAP Help Portal athelp.sap.com SAP NetWeaver SAP NetWeaver 7.0 SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology Administration Manual Supportability and Performance Management Logging Log Configuration Workload Monitors SAP NetWeaver MDM GDS has instrumentation set for the third party tool Intrsocope. To monitor the performance of the application, download Introscope with the most recent NetWeawer Introscope agent. It contains the necessary instrumentation for the application. You can find the performance data in the following location: 1. Open an Introscope Investigator. 2. Open the Super Domain tree. 3. Select your engine, open it, and then open the SAP NetWeaver node. You can find a node for business logic objects (BL) and a node for the back end connectivity objects (BC) under the SAP GDS node. If you select an object, you can see the methods. The Introscope tool can measure five different values for each method: Average response time Concurrent invocations Errors per interval Responses per interval Stall count 12 March 2009

13 4.1 Starting and Stopping 4 Management of SAP NetWeaver MDM GDS SAP provides you with an infrastructure to help your technical support consultants and system administrators effectively manage all SAP components and complete all tasks related to technical administration and operation. For more information about the underlying technology, see the Technical Operations Manual for SAP Technology in the SAP Help Portal at help.sap.com Documentation SAP NetWeaver SAP NetWeaver 7.0 System Administration Technical Operations Manual. 4.1 Starting and Stopping The following table describes the start and stop sequences and tools: Software Component SAP NetWeaver AS Java Start and Stop Sequences and Tools Sequence Tool Detailed Description 1 SAP Management Console MDM Server 2 SAP Management Console For more information, see help.sap.com SAP NetWeaver SAP NetWeaver 7.0 System Administration Technical Operations Manual For more information, see the MDM solution operations guide on SAP Service Marketplace at service.sap.com/inst allmdm SAP NetWeaver MDM 7.1 MDM 7.1 Solution Operations Guide. SAP PI 3 For more information, see help.sap.com SAP NetWeaver SAP NetWeaver PI System Configuration and Administration Technical Operations Manual AS2 Adaptor 4 See relevant Seeburger documentation GDS Console 5 Internet Browser Start using the GDS Console in Internet Explorer For the list of components required for each scenario, see Scenario/Component Matrix. March

14 Management of SAP NetWeaver MDM GDS Restarting the GDS Console 4.2 Restarting the GDS Console 1. Open the Visual Administrator. For example, on a Windows platform run: <Drive>:\user\sap\<SAPSID>\<Instance_Name>\j2EE\admin\go.bat 2. Connect to the J2EE engine on which you have deployed the GDS application. 3. In the left pane, navigate to the Deploy service: Server<server id>>services>deploy 4. In the right pane, choose the Application radio button. 5. Select sap.com/is~gds~core~app. 6. Select Stop Application and then Start Application. The line should be marked with a blue check mark. 4.3 Software Configuration This chapter explains which components or scenarios used by this application are configurable and which tools are available for adjusting. Software Component GDS Core and UI GDS Metadata GDS UI Configuration Transaction/Tool Visual Administrator GDS 2.0 Console GDS 2.0 Console Detailed Description See the installation guide for GDS on the SAP Service Marketplace at service.sap.com/instguides Industry Solutions Industry Solution Guides SAP for Consumer Products SAP MDM GDS 2.0 Installation Guide Application Properties See the GDS 2.0 Console User Guide in the SAP Help Portal at help.sap.com SAP for Industries SAP for Consumer Products SAP MDM GDS 2.0 Metadata Management See the GDS 2.0 Console User Guide in the SAP Help Portal at help.sap.com SAP for Industries SAP for Consumer Products SAP MDM GDS 2.0 User Interface Configuration 4.4 Backup and Restore You need to back up your system landscape regularly to ensure that you can restore and recover it in case of failure. The backup and restore strategy for GDS consists of two parts: 14 March 2009

15 4.5 Application Copy Backup and restore coverage for each component (see table below) Cross-system data dependencies and handling The backup and restore strategy for your system landscape should not only consider SAP systems but should also be embedded in overall business requirements and incorporate your company s entire process flow. In addition, the backup and restore strategy must cover disaster recovery processes, such as the loss of a data center through fire. It is most important in this context that you ensure that backup devices are not lost together with normal data storage (separation of storage locations). The following table lists the components used by GDS and how to backup them: Component Data to be backed up Backup Method / Tool MDM MDM All GDS data is stored in the database managed by the MDM Server. This data can be backed up and restored using the standard database functions. Refer to the relevant database documentation. GDS 2.0 Console Application configuration data In the MDM Console, you can archive and unarchive repositories For more information, see the MDM console reference guide on SAP Service Marketplace at service.sap.com/installmdm SAP NetWeaver MDM 7.1 MDM Console Reference To backup and restore the complete SAP NetWeaver AS Java, see help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SAP NetWeaver 7.0 System Administration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (Application Server for Java) Management Tasks Backing Up and Restoring AS Java Recommended Backup Frequency Weekly Weekly Portal Users and roles Weekly 4.5 Application Copy For more information, see The relevant system copy guides at help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SAP NetWeaver 7.0 System Administration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (Application Server for Java). March

16 Management of SAP NetWeaver MDM GDS Periodic Tasks The solution operations guide for MDM on SAP Service Marketplace at service.sap.com/installmdm SAP NetWeaver MDM 7.1 MDM 7.1 Solution Operation Guide System Copy. 4.6 Periodic Tasks Scheduled Periodic Tasks This chapter describes all automatable tasks required to run periodically in order to keep the application running smoothly over time. Such tasks may be required on component level and are therefore relevant in each scenario that uses the component. You can find the mapping in the chapter Scenario / Component Matrix above. Other tasks may be relevant for certain business scenarios only. It is important that you monitor the successful execution of these tasks on a regular basis. For more information, see The relevant administration tasks at help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SAP NetWeaver 7.0 System Administration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (Application Server for Java). The solution operations guide for MDM on SAP Service Marketplace at service.sap.com/installmdm SAP NetWeaver MDM 7.1 MDM 7.1 Solution Operation Guide Periodic Tasks Required Manual Periodic Tasks This chapter describes all manual tasks required to run periodically in order to keep the application running smoothly over time. A manual task need a person to for each execute in opposite to the scheduled tasks listed above which can be automated using a task scheduler program. Such tasks may be required on component level and are therefore relevant in each scenario that uses the component. You can find the mapping in the chapter Scenario / Component Matrix above. Other tasks may be relevant for certain business scenarios only. It is important that you monitor the successful execution of these tasks on a regular basis. For generic information, see The relevant administration tasks at help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SAP NetWeaver 7.0 System Administration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (Application Server for Java). The solution operations guide for MDM on SAP Service Marketplace at service.sap.com/installmdm SAP NetWeaver MDM 7.1 MDM 7.1 Solution Operation Guide Periodic Tasks. GDS Console Task or Transaction Description Recommended Frequency Check GDS log files Check GDS log and trace files See also the section Monitoring in this Document Weekly 16 March 2009

17 4.6 Periodic Tasks Delete completed workflows Delete completed workflows Weekly For more information about deleting completed workflows see the GDS 2.0 User Guide in the SAP Help Portal at help.sap.com SAP for Industries SAP for Consumer Products SAP MDM GDS 2.0 Workflow Managment Managing Workflow Jobs. MDM Console Task or Transaction Description Recommended Frequency Check log files for MDM Server Check correctness/severity of operations for repository Verify repository and repair/compact if necessary Check log files - Audit, Server, Assertion service.sap.com/installmdm SAP NetWeaver MDM 7.1 MDM Console Reference Guide Repository Maintenance Logs Table Check log files for different Operations See service.sap.com/installmdm SAP NetWeaver MDM 7.1 MDM Console Reference Guide Repository Maintenance Logs Table Check MDM repository integrity See service.sap.com/installmdm SAP NetWeaver MDM 7.1 MDM Console Reference Guide Repository Administration Operations Weekly Weekly Monthly SAP Exchange Infrastructure (SAP XI) Task or Transaction Description Recommended Frequency SAP XI messages (Report RSXMB_RESTART_ MESSAGES) Purge old messages Schedule report to resend failed messages. If messages cannot be resent, you must delete them manually. To avoid data errors, resend the corresponding object manually. Archive and purge old messages in order to maintain available disc space Periodic restart Every 3-6 months March

18 Management of SAP NetWeaver MDM GDS Load Balancing AS2 Adapter Engine Task or Transaction Description Recommended Frequency Restart adapter engine Purge old messages Database Administration Tool During operation of SAP MDM GDS, the buffer of the adapter engine overflows Archive and purge old messages in order to maintain available disc space Periodic restart Every 3-6 months Task or Transaction Description Recommended Frequency Delete Process Log table Delete Process Log table IS_GDS_LOG_KEYS Weekly 4.7 Load Balancing GDS 2.0 does not require load balancing. 4.8 User Management User management is provided in the MDM 2.0 Console. For more information on user management, see the GDS 2.0 User Guide. 4.9 Printing There are the following printing possibilities in GDS 2.0: Trade Item Maintenance search result table Item Hierarchy There are no special requirements for printing from GDS 2.0 For more information, see the GDS 2.0 Console User Guide in the SAP Help Portal at help.sap.com SAP for Industries SAP for Consumer Products SAP MDM GDS March 2009

19 4.9 Printing 5 High Availability (HA) Components with single point of failure Component Detailed Description HA Setup Description MDM SAP NetWeaver 7.0 Without MDM, GDS 2.0 is not able to read application data. Without SAP NetWeaver AS Java, GDS 2.0 is not able to start. service.sap.com/insta llmdm SAP NetWeaver MDM 7.1 MDM 7.1 Solution Operation Guide help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SAP NetWeaver 7.0 System Administration Technical Operations Manual Each of the above components can be a single point of failure in this scenario. In order to achieve HA for the complete scenario it is required that all components with single point of failures are set up with HA. March

20 Software Change Management GDS Console 6 Software Change Management Software Change Management standardizes and automates software distribution, maintenance, and testing procedures for complex software landscapes and multiple software development platforms. These functions support your project teams, development teams, and application support teams. The goal of Software Change Management is to establish consistent, solution-wide change management that allows for specific maintenance procedures, global rollouts (including localizations), and open integration with third-party products. This section provides additional information about the most important software components. 6.1 GDS Console For detailed information about the current status regarding Support Packages of single components, see the master guide for GDS on SAP Service Marketplace at service.sap.com/instguides Industry Solutions Industry Solution Guides SAP for Consumer Products SAP MDM GDS 2.0 Master Guide. Solution Manager Maintenance Optimizer can be used to download the GDS 2.0 support packages. For more information about the Maintenance Optimizer, see SAP Service Marketplace atservice.sap.com/support SAP Support Infrastructure Maintenance Optimizer. Patches can also be downloaded manually from the SAP Service Marketplace. For more information, see service.sap.com/instguides Industry Solutions SAP for Consumer Products SAP MDM GDS 2.0. Do not implement relevant Support Packages during productive operation of SAP GDS 2.0. Applying a patch may cause the MDM Server to be unloaded, which makes GDS 2.0 unavailable in the productive environment. 6.2 MDM Server New functions are delivered through new service packs. Updates of the database (enhancements) do not lead to loss of data. For detailed information about the current status of support packages of individual MDM components, see the master guide for MDM on the SAP Service Marketplace at on SAP Service Marketplace at service.sap.com/installmdm. Do not implement relevant Support Packages during productive operation of SAP MDM. 20 March 2009

21 7.1 MDM is down 7 Troubleshooting 7.1 MDM is down Symptom in standalone mode: Logon screen is disabled and an error message informs the user that MDM is not available. Symptom in portal mode: Blank screen appears instead of the application start screen. Reason: MDM Server is down and/or repository is not loaded. Solution: Check MDM Server and repository, refer to the SAP NetWeaver MDM documentation on SAP Service Marketplace atservice.sap.com/installmdm. 7.2 XI Messages Are Not Sent Out Symptom: When sending out a message (registration, publication or link), on the message sending overview window an error message appears with red status light. Reason: The business system or technical system is not set properly in the System Landscape Directory. Solution: For more information about proper settings, see the configuration guide on SAP Service Marketplace at service.sap.com/instguides Industry Solutions Industry Solution Guides SAP for Consumer Products SAP MDM GDS 2.0 Configuration Guide Message Does Not Return to GDS Console Symptom: Trade items with a pending status (registration, publication or link) frequently go into error status after the specified timeout. Reason: 1SYNC data pool is down, or the message queue is blocked in the XI system. Solution: Check XI Message Monitor. For more information, see help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SAP NetWeaver 7.0 SAP NetWeaver Library SAP NetWeaver by Key Capability Process Integration by Key Capability SAP NetWeaver Exchange Infrastructure. 7.4 No Menu Item for MDM user Symptom: No menu item appears in the navigation tree for the user and an error message reports that no menu items are available for the current user. Reason: Roles not properly set for the current user. Solution: For more information about configuring roles, see the GDS 2.0 User Guide in the SAP Help Portal at help.sap.com SAP for Industries SAP for Consumer Products SAP MDM GDS 2.0 User Interface Configuration Managing Roles. 7.5 Cannot Find an Existing Trade Item Symptom: On the Item Maintenance screen, after filtering the list of trade items in the top row of the result table, a trade item that definitely exisits does not appear in the results list. March

22 Support Desk Management Remote Support Setup Reason: Search filter may be set to display 100 or 500 results. In this case, the filter only searches the first 100 or 500 results. Solution: Conduct a basic search, or refine your search using a drilldown search. For more information on basic and drilldown searches, see the Application Help. 8 Support Desk Management Support Desk Management enables you to set up an efficient internal support desk for your support organization that seamlessly integrates your end users, internal support employees, partners, and SAP Active Global Support specialists with an efficient problem resolution procedure. For support desk management, you need the methodology, management procedures, and tools infrastructure to run your internal support organization efficiently. The following topics are covered: Remote support Component hierarchy relevant for this application 8.1 Remote Support Setup The standard SAP NetWeaver support tools can be used to support GDS 2.0. You can use the Everyone role for support access to the GDS Console. Assign the relevant screens to the role to be available for the support personel. No operations are assigned to the Everyone role by default, which means, that all the screens are available only in read only mode. 8.2 Problem Message Handover To create a ticket, use the component MDM-GDS. To report an error in the GDS 2.0 Console, attach the dump download file to the ticket. You can create the dump download file by choosing Dump Download in the GDS 2.0 Console. Dump Download is only available if you have the Admin role. 22 March 2009

23 9.1 Related Guides 9 Appendix 9.1 Related Guides For more information about installation and configuration, see the master guide on SAP Service Marketplace at service.sap.com/instguides Industry Solutions Industry Solution Guides SAP for Consumer Products SAP MDM GDS 2.0 Master Guide. For more information about customizing validation rules, see the configuration guide on SAP Service Marketplace atservice.sap.com/instguides Industry Solutions Industry Solution Guides SAP for Consumer Products SAP MDM GDS 2.0 Configuration Guide. 9.2 Related Information The following table contains links to information relating to the Application Operations Guide: Content Master Guide, Installation Guide and Upgrade Guide Related SAP Notes Released Platforms Network Security Technical Infrastructure SAP Solution Manager Quick Link to the SAP Service Marketplace (service.sap.com) instguides ibc notes platforms securityguide network ti solutionmanager March