SM100 SAP Solution Manager Operations

Full text

(1)606$36ROXWLRQ0DQDJHU2SHUDWLRQV. 60 6$36ROXWLRQ0DQDJHU2SHUDWLRQV. .

(2)

(3)  SAP AG 2006. © SAP AG 2005. . Software components used in the course. . 2006/Q62. . Material number 50082608. .

(4) &RS\ULJKW. &RS\ULJKW 6$3$*$OOULJKWVUHVHUYHG. 1RSDUWRIWKLVSXEOLFDWLRQPD\EHUHSURGXFHGRUWUDQVPLWWHGLQ DQ\IRUPRUIRUDQ\SXUSRVHZLWKRXWWKHH[SUHVVSHUPLVVLRQRI 6$3$*7KHLQIRUPDWLRQFRQWDLQHGKHUHLQPD\EHFKDQJHG ZLWKRXWSULRUQRWLFH.  SAP AG 2006. . 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.. . …. .

(5) . 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..

(6) &RXUVH 3UHUHTXLVLWHV. 5HFRPPHQGHG .QRZOHGJH. 6$37(& $'0 6$3.  SAP AG 2006. .

(7) 7DUJHW$XGLHQFH. 7KLVFRXUVHLVLQWHQGHGIRUWKHIROORZLQJDXGLHQFHV. 6\VWHP$GPLQLVWUDWRUV. 7HFKQLFDO&RQVXOWDQWV 'XUDWLRQ GD\V.  SAP AG 2006. . 8VHUQRWHV. . These training materials are QRWDWHDFK\RXUVHOISURJUDP. They complement the explanations provided by your course instructor. Space is provided on each page for you to note down additional information.. . There may not be sufficient time during the course to complete all the exercises. The exercises provide additional examples that are covered during the course. You can also work through these examples in your own time to increase your understanding of the topics.. .

(8)

(9) &RXUVH2YHUYLHZ &RQWHQWV Course Goals Course Objectives Course Content Course Overview Diagram Main Business Example. .  SAP AG 2006. © SAP AG. SM100. 1-1.

(10) &RXUVH*RDOV. $IWHUFRPSOHWLQJWKLVFRXUVH\RXZLOOEHDEOHWR Administer all necessary tools and features to know around the SAP Solution Manager Know all the basic functionalities of the SAP Solution Manager. .  SAP AG 2006. . Conduct: ausführen, durchführen. © SAP AG. SM100. 1-2.

(11) &RXUVH&RQWHQW — — — — — — — —. L5#MI+ G(HA1#IJEK6,#6

(12) F D8A@B1< !.+ +&,#E*6#"6 F :5;< = &>1

(13) ?8A@B1<

(14) C+,, ,, + 4

(15) 5,#6

(16) .789 '(*) +,&.-/0!1 2+,+&, 3,. — — — — —. , V8A@B1<

(17) .2+, +&#87H +& Q , RS

(18) +#Q@ 2TU+ ,) @ #I , P5#I6 3C6 @ 1 .8

(19) @=1Q A -8!#Q B & , AGN5#I6 .78@B 6,,# , AG,GO1 % .L5#" 2

(20) "

(21) #$ = &. ! "#$ % &

(22) . .  SAP AG 2006. © SAP AG. SM100. 1-3.

(23) © SAP AG. SM100. 1-4.

(24) 8QLW &RXUVH&RQWHQW — — — — — — — —. K4"LH*

(25) F'G@0"HIDJ5+"5 E C 7@?A0 ; -* *%+"D)5 "!5 E 9 4:; < %=0 >7@?A0 ; B*++++

(26) * 3 4+"5

(27) -678 &')( *+%-,. / 0 1*+*%+ 2+ . — — — — —. + U 7@?A0 ; -1*+ *%"76G *% P

(28) + QR *"P? 1ST*

(29) +(? "H + O 4"H5

(30) 2B 5 ?0 -7 ?<0 P @ ,7 "P A % + @FM 4"H5

(31) -67?A 5++" + @F+F N0 $ -K4"!

(32) 1 ! "# < %. !"# $ %

(33) . .  SAP AG 2006. © SAP AG. SM100. 2-1.

(34) 2EMHFWLYHV6ROXWLRQ0DQDJHU2YHUYLHZ. $IWHUFRPSOHWLQJWKLVXQLW\RXZLOOEHDEOHWR. 'HVFULEHWKHDQGDYDQWDJH RIWKH6$3 6ROXWLRQ0DQDJHU. *HWDQJHQHUDORYHUYLHZRIWKH6$36ROXWLRQ 0DQDJHUIXQFWLRQDOLWLHV. ([SODLQWKHJHQHUDODQGUHOHDVHVWUDWHJ\RI WKH6$36ROXWLRQ0DQDJHU. .  SAP AG 2006. © SAP AG. SM100. 2-2.

(35) 6$36ROXWLRQ 0DQDJHU 2YHUYLHZ 0RWLYDWLRQ. 6XSSRUWIRU,7,/3URFHVVHV $YDLODEOH)XQFWLRQDOLWLHV 5HOHDVH6WUDWHJ\. . © SAP AG. SM100. 2-3.

(36) &RQVLGHU&XVWRPHUV 6LWXDWLRQ RI7RGD\« Global operations. Heterogeneous solutions. . Business processes. 'LIIHUHQWORFDWLRQV 'LIIHUHQWFRXQWULHV 'LIIHUHQWODQJXDJHV 'LIIHUHQWWLPH]RQHV &HQWUDOYVGLVWULEXWHG. .  SAP AG 2006. . Large companies today are facing a lot of new challenges in their system management, what is due to. . Global Operations. . Heterogeneous Solutions. . Integrated Business Processes. . The challenges in global operations are. . Different locations, countries, languages, time zones. . There is always a tradeoff between central and distributed solutions. © SAP AG. SM100. 2-4.

(37) &RQVLGHU&XVWRPHUV6LWXDWLRQRI7RGD\« Global operations. Heterogeneous solutions . 5LVN Æ. Business processes. 'LIIHUHQWDSSOLFDWLRQV 'LIIHUHQWWHFKQRORJLHV 'LIIHUHQWYHQGRUV 3RLQWWRSRLQWLQWHJUDWLRQ &XVWRPPDGHVROXWLRQV. 'LIIHUHQWDSSOLFDWLRQVWHFKQRORJLHVDQGYHQGRUV “Who has the skills to understand and handle all the different technologies. 5LVN Æ 5LVN Æ. your solution is based upon“. 3RLQWWRSRLQWLQWHJUDWLRQ “Who are the responsible persons for the increasing number of interfaces and do they know the business impact of their actions?“. &XVWRPPDGHVROXWLRQV. “Can you perform upgrades without endangering the stability of your solution?“. .  SAP AG 2006. . As a result of heterogeneous solutions in terms of different applications, technologies, vendors a lot of risks occur in the operation of these solutions: • The skill profile for the staff is growing • The number of interfaces is growing • The customer specific parts of the solutions is growing. © SAP AG. SM100. 2-5.

(38) &RQVLGHU&XVWRPHUV6LWXDWLRQRI7RGD\« Global operations. Heterogeneous solutions. ¶ iP· c ¸¹]`!Z g]c`H`º· i![;cH``\;g!h_i]^ ¹Ha<Z i]ge;\!g!h!`][\]Y]c W#X!Y!Z []\;^_PX`baAc]dfe]\]!g!h!`![!\]Y]ca i+jc k d Y]^ cPdc;ga c;h lm$non<p q |}t<~ yosAom$Ay lb!}o r!w w]t<v$rHtAs$x$t<y$u z#v yAvo{ w;t<l:v<q t<Ax<{ y$yoz#zy<v<{ ¿ ¡: ¾ A A H A A H $ ¡$ :o~ p t<t<vovoAv<nAu vA:x ~ { lbq ${ y$z ¼<½A ¤ ¢ b A A b A H < : !Á r lb ³ l »o¥ $b b µ ¥ ¤ 5LVN Æ. V. Business processes. ¦ §ª ® ¨H¯ ¬©< ª «« ° ¬ ± ¬ ¬ ² ® ¯ HlrHqt$A~ ~{ uy$y<z ~ A £½A$b Á Â< À A ¥ o . rlbmoqA { :{ y<z#z yo~ ¡: H ¢ob ¡o b £$ b <¡: ¤ ¥ ¤ . ,QWHJUDWHG%XVLQHVV3URFHVVHV. Do you know which business process step runs on which system?. V V. Do you know the responsible persons in case of problems? Does your IT Department know how its daily work affects your business processes?. .  SAP AG 2006. . Good business process management needs a concept. This concept should include: • Roles and responsibilities for all persons involved in the customer’s support and monitoring organization • Documentation of the core business processes including all relevant process steps, involved interfaces, business process owners, availability requirements, performance and throughput requirements, and functional dependencies • Procedures for business-process oriented monitoring, error handling, and escalation management for a company’s core business processes • Techniques for integration management regarding interface operation and the interfaces’ impact on business processes to ensure data quality and consistency, interface security, and recovery reliability • Procedures for program scheduling management including the planning, controlling, and monitoring of all system and business-process related operational activities in a distributed system landscape • Methods for master data maintenance regarding the exchange of master data between different software components in a distributed system landscape • Procedures for data management and archiving to check for and correct data inconsistencies and to avoid unnecessary data growth • Definition of Service Level Reporting requirements. © SAP AG. SM100. 2-6.

(39) 0LVVLRQ6WDWHPHQW With SAP Solution Manager you can manage your SAP solution throughout the entire life cycle to ... Ensure reliability. Reduce Total Cost of Ownership. Increase Return on Investments. SAP Solution Manager is delivered as part of your annual license fee!!! $QGKHUHLVKRZ\RX FDQDFKLHYHWKHEHQHILWV. .  SAP AG 2006. © SAP AG. SM100. 2-7.

(40) 6XSSRUWIRU,7,/3URFHVVHV. 0RWLYDWLRQ. 6XSSRUWIRU,7,/3URFHVVHV $YDLODEOH)XQFWLRQDOLWLHV 5HOHDVH6WUDWHJ\. .  SAP AG 2006. © SAP AG. SM100. 2-8.

(41) &RPPRQGHIDFWR6WDQGDUGVIRU,70DQDJHPHQW ,QIRUPDWLRQ7HFKQRORJ\,QIUDVWUXFWXUH/LEUDU\. V V. First developed by Central Computer and Telecommunications Agency (CCTA) in 1989. Most widely accepted approach to IT Service Management.. V. Series of books giving best practice for Service Support and Delivery Processes.. www.itsmf.com (for Germany www.itsmf.de). 02) 0LFURVRIW2SHUDWLRQV)UDPHZRUN

(42). V V. Best practices in IT Service Management based on Microsoft technology.. Combines ITIL with specific guidelines for using Microsoft products and technologies.. www.microsoft.com/germany/ms/businessrategien/infrastruktur/sicherheit/mof.htm. 35,1&( 35RMHFWV ,1&RQWUROHG (QYLURQPHQWV

(43). V V. UK de-facto standard for project management developed by the Government. Was re-launched in October 1996.. www.projectsmart.co.uk/prince2.html. .  SAP AG 2006. . Even though ITIL is not yet a legal standard it has become a de facto standard for IT Service Management worldwide. ITIL is focused on processes in operations (Service and Support delivery). It describes on theoretical basis which processes and tasks are necessary. ITIL is not a software and not a part of SAP NetWeaver. ITIL consists of books that provide a description of the processes.. . Other de facto standards in similar areas are MOF and PRINCE2. MOF is to see as the interpretation of ITIL with help of Microsoft tools. ITIL should be seen as the theoretical frame, how to operate software and hardware landscapes. MOF is the ITIL fulfillment by Microsoft. MOF describes which Microsoft tools could be used in which ITIL process.. . In contrast to ITIL PRINCE2 is a de facto standard for the project management. PRINCE 2 could be used during implementation phase of projects.. . Many of our big customers consider and follow actively the ITIL standard. Due to this it might happen that they ask us for SAP tools to fulfill ITIL or even if SAP‘s Service and Support Consultants are ITIL certified.. . It is useful be aware at least of ITIL terminology and differences to the SAP internal use of certain terms. It is also important to share a high-level understanding of what ITIL is behind the scenes. To claim at our customers that we as representatives of SAP Active Global Support are aligned with ITIL, it is not a formal requirement to have every employee ITIL certified.. . Actually SAP‘s way of operating and supporting matches with the ITIL standard. Due to this we could use ITIL for our own purposes. One of the advantages of ITL is to have the same terms and a definition of the processes in service and support.. © SAP AG. SM100. 2-9.

(44) &RPELQLQJ:KDWDQG+RZ. :KDW. +RZ. ,7,QIUDVWUXFWXUH/LEUDU\. 6$36ROXWLRQ0DQDJHU. Process Descriptions. Process Execution. Best practices and recommendations for implementations. Ã. What to consider in establishing and operating IT service management?. Developed with help of IT service specialists. Tool-set for use in IT implementation and operations. Ã. How to execute the processes by using tools in SAP Solution Manager?. Based on more than 30 years experience in managing business applications. .  SAP AG 2006. . ITIL provides best practice guidelines for service management. They describe the different processes in IT service management and what has to be considered in establishing and operating these services. SAP Solution Manager takes care of the execution of the services. It provides the tools required for running the services. The cooperation of ITIL and SAP Solution Manager is a meaningful combination of ‘What has to be done (ITIL)’ and ‘How can this be done (SAP Solution Manager)’ .. © SAP AG. SM100. 2-10.

(45) ,7,/DQG6$37RROV ,7,/%DVLV)UDPHZRUN. 6$36ROXWLRQ0DQDJHU. Í* ?o A %ÇB L!

(46)

(47) ? I+L@Îo

(48) + 4**% Ê ÎA

(49) + ;Ï K"] É? 2Ï')(*% Ï' L] A% 0"*; ÎA

(50) + Ð@" ÊË *? . "5

(51) 26 8 È Message Handling È Notes and SAP Note Assistant È SAP Support Packages È Reporting. 'f(*% -*+* % - . ')(* %Ê,./ 0 1** % Ê. 'Ä ;"] ?A?< A+%IÅ @ " A %. 4 ?A0 ; -Ë** %"41 ! "; $+% (SAP Alert Monitoring RZ20). @"5

(52) -B 5? ** %2. ÄB>*+Ê7@?A0 ; A2,4+ "] A%. .' **

(53) b-1**%+- Ä5 * A? *É <?A -*+*+% Ê 'Ä ; <0 -Ë* * % +Ì+ . ÆKÇ4"H5

(54) È Solution Management Assessment È Solution Management Optimization È EarlyWatch Alert / GoingLive. .  SAP AG 2006. . This slide describes which ITIL processes are defined and which SAP tools the SAP Solution Manager is offering to follow this ITIL standard.. . ITIL consists at the moment of descriptions for Service Support, Support delivery and Application management.. . ITIL groups the process into Service Support and Service Delivery processes: • Support are all processes which are necessary to operate a concrete software solution day to day. These are e.g. the Hot line which deals with incoming incidents. • Delivery are all processes which are necessary to offer the service support. It is more the long term planning and improvement of the IT services. • Service Desks is an exception within the ITIL processes. The service desk is to be seen as an function not as a process.. . Very important terms within the processes are customer, provider, supplier and user. A customer is a recipient of a service. If you have in mind an outsourcer. The outsourcer would be the provider. He is responsible to fulfill the requirements of the customer. May be there exist underpinning contracts with a third party e.g. another Hardware provider. These partners are called supplier. The user is a person who uses the service on a daily basis.. © SAP AG. SM100. 2-11.

(55) 6HUYLFH'HOLYHU\ZLWK6$36ROXWLRQ0DQDJHU ,70DQDJHPHQW. 4+"5

(56) -B 5 +? ** %Ì. Capacity data. SL and Solution Reporting. '.**

(57) b Ë**%+ - . Service Desk Accounting. Ó Ô Ó ÕËÖ×$ØÙ}Ú}Û}ÛÜÚ}Û ä Ø ê çãé!æ Øëfì.íåëÝíÝîÚå×Ô ØØê Û. G5* A? *É A?A Ê**+%+ Ê . 'Ä P <0 ** %Ì. EarlyWatch Alert, Quick Sizer. Î ÐÇÑ <*

(58) *+? 1*+*%+ 2+ Ò. Performance and availability. Change request. ')(*+%+ ** %Ì. Solution Monitoring Change request. ÎA

(59) + ** % - . ,7,QIUDVWUXFWXUH. ÙÝØÜÞÝÚ×<Úàß1áãâfäÚå×AÞæ Ù}ÚGäçåèèÝØ ×Aé ïð èàí×Aéê âfÙ}ØÜÞÝÚ×<Úàß. .  SAP AG 2006. . This slide shows the different ITIL processes from the Service Delivery area and the tools supported.. . Furthermore it shows the connection from the Service Delivery to the Service Support (the Change Management and Incident Management).. © SAP AG. SM100. 2-12.

(60) 6HUYLFH6XSSRUWZLWK6$36ROXWLRQ0DQDJHU ,7(QGXVHU Incidents, Service requests. Problems. ö øö û ùõöõ ÷øúÌøöû. õ õ ÿ û ù1õ+öõ÷+ø ú2øöû. Service Desk. ü4ý!þ ÿ ø ú ùõöõ ÷ø úÌøö û Service Desk. Request for change. Ó Ô Ó ÕËÖ×$ØÙ}Ú}Û}ÛÜÚ}Û ä Ø ê çãé!æ Øëfì.íåëÝíÝîÚå×Ô ØØê Û. Note Assistant, Change Request Management. Change authorization. Requests for change. ófôõö ÷øÊùõ+ö+õ÷ø ú-øö û. Request for change. ó þ ö ÷ ý õû þ ö-ùõöõ+÷ú Central system data and Customizing. Incidents. óG õ õ

(61) û ùËõö õ÷ø úÌøö û. Change authorization. ø øõ øÊùõöõ+÷ø úÊøö û Upgrade Managm. **. ,7,QIUDVWUXFWXUH. ÙÝØÜÞÝÚ×<Úàß1áãâfäÚå×AÞæ Ù}ÚGäçåèèÝØ ×Aé ïbïð æ ëGßåÚñÞàÚåê Ø èàòfÚëãé. .  SAP AG 2006. . The change management component is new in the SAP Solution Manager 3.2, and is designed closely to support the ITIL scenario.. . The change management is responsible to make changes requested by problem management for solving problems. They need standardized methods to do the changes fast and controlled. Impacts because of the changes should be minimized.. . For each RfC (Request for change) a priority and a category is to be defined. The priority is again the sum of urgency and impact. The category depends on the necessary resources for implementing the changes.. . The change advisory board is the community which decides about major and immediate RfCs. It has to pay intention to the different views: Users, Customer, Technical view, business view.. . After the implementation of an RfC the change management has to review the results of the change. Does the change fulfill the request?. © SAP AG. SM100. 2-13.

(62) $SSOLFDWLRQ0DQDJHPHQWZLWK6$36ROXWLRQ0DQDJHU %+'Ú & çÜæ ×<ÚÜòÚëñé<Û ø

(63) ý ø ú-øöû áçñÛæ ëñÚ}ÛàÛJè×$ØÙ}ÚãÛÝÛÝÚñÛ • Change Request Management. !"û ú #åø • SAP Services • Upgrade Management • Change Management • Optimization Projects. !$ø. 0RQLWRULQJ. Ó Ô Ó ÕËÖ×$ØÙ}Ú}Û}ÛÜÚ}Û ä Ø ê çãé!æ Øëfì.íåëÝíÝîÚå×Ô ØØê Û. • Business Blueprint, • Central System Data, • Mapping of Business Processes to IT Landscape.

(64) . ý õûbø. • System Monitoring • Business Process Monitoring • Central System Admin. • EarlyWatch Alerts. ø ÷@ö.

(65) ø . þ . • Test Workbench • Global Roll-Out • Customizing Synchronization. • Implementation of mySAP based on Business Processes • Central Documentation of Implementation Project • Setup Business Process Monitoring. .  SAP AG 2006. . Diese Folie zeigt die verschiedenen ITIL Prozesse aus dem Bereich Application Management und durch welche Tools sie unterstützt werden.. . Weitere Infos zu den Prozessen und Tools sind im Word-Dokument zu finden.. © SAP AG. SM100. 2-14.

(66) $YDLODEOH)XQFWLRQDOLWLHV. 0RWLYDWLRQ. 6XSSRUWIRU,7,/3URFHVVHV $YDLODEOH)XQFWLRQDOLWLHV 5HOHDVH6WUDWHJ\. .  SAP AG 2006. © SAP AG. SM100. 2-15.

(67) 7HFKQLFDO'HWDLOV6$36ROXWLRQ0DQDJHU 6$36ROXWLRQ0DQDJHU. V. runs on SAP basis technology. V V. &50. can service all SAP technologies integrates non-SAP products and. 6$36ROXWLRQ 0DQDJHU. 5. $32. (*),+.-0/132 /465 /67. V centralized: 8 8 8 8 8 8 8 8. Process description Documentation Testing Configuration and Customizing Note handling Monitoring Service delivery and execution Landscape definition. .  SAP AG 2003 2006. . SAP Solution Manager, as part of SAP NetWeaver, serves as a central instance within the solution landscape to manage the complete solution.. . This includes applications developed by SAP, customer and 3rd-party applications based on SAP NetWeaver, as well as other applications.. . As central instance, SAP Solution Manager provides a variety of centralized services both for implementing and operating your SAP solutions.. . The advantages are that you have a central point of access, that you can do end-to-end process control, that you can ensure consistency within your landscape, and that dependencies between different components are taken into account.. © SAP AG. SM100. 2-16.

(68) 7KH 6$36ROXWLRQ0DQDJHU$SSURDFK 7KH6$36ROXWLRQ0DQDJHULVDQHZW\SHRIDSSOLFDWLRQZKLFK«. V. Takes a consistent business-process and phase-oriented approach. V. End-to-end functionality for application management and continuous improvement. V. Provides full life-cycle support and collaboration with SAP. V V. 9 ö þ :; 6ø ÷ø < ø û ù1õö õ÷øú2øöû ùõ+öõ÷+ø ú2øöû. Contains best practices for implementation, operation and optimization of SAP solutions Is delivered as part of your annual maintenance fee. üý]>þ = ø û ùõ+öõ ÷ ø+úÌø+ö û. @ þ û þ ö ù þ

(69) ö û þ ý $ö÷. Implement. BDCEGFIHGJKEE LNMPORQGJKEE 9. ö þ6:? ø6 ÷ø <@ý õö Hø ý. @4ø ý ø ø A. Optimize. ó)ôõ+ö+÷ø ùËõöõ ÷ ø+úÌø+ö û . @4ø ý ø ø ø ý . .  SAP AG 2006. . The SAP Solution Manager is NOT positioned against existing knowledge management, solution management and other best-of-breed solutions.. . Our strategy is not to replace existing software products at customer sites, but to coexist and bring additional value to the customer.. . If a best-of-breed product is chosen because it offers more functionality in a specific area, we recommend to evaluate the SAP Solution Manager nevertheless.. . We think that the SAP Solution Manager offering is compelling because of its integrated, process- and life-cycle-oriented approach and should therefore be actively used at all customer sites.. © SAP AG. SM100. 2-17.

(70) 6$36ROXWLRQ0DQDJHUIRUP\6$3(53 +RZLV6$36ROXWLRQ0DQDJHUWHFKQLFDOO\OLQNHGWR P\6$3(53" Installations and Upgrades to mySAP ERP ONLY possible if SAP Solution Manager is installed at customer site. :K\ 6$36ROXWLRQ0DQDJHUIRUP\6$3(53". Faster implementation and more efficient operation of mySAP ERP All available implementation and upgrade content included Optimal support of all operations, maintenance and improvement activities. Optimal access to all support services Faster issue resolution through optimal collaboration with Active Global Support. 6LJQLILFDQWUHGXFWLRQRI7&2RIP\6$3(53. .  SAP AG 2006. © SAP AG. SM100. 2-18.

(71) ,PSOHPHQWLQJ 6$36ROXWLRQV ² 3URFHVVLQ'HWDLO

(72) <ö ø N ø

(73) ý oöû. ü4ýþ= ø û ü4ý ø õ ý õû þ ö. Aö õ ü@ý ø õ ý õû þ ö +õ V ö

(74) XW þZY ø. ó þ ö UA÷ ý õ û þ ö. 6$36ROXWLRQ0DQDJHU • •. ø <ö øT ý]þ= ø6 û @4øû

(75) ; ûHø ú õö6 õ ø. ø Aö+ø? û þ ú-ø þ û þ ö ÿ õ ø þ @ Æ ü ýþ ø ø. •* . ö. ý. •. ó þ ö ÷* ý ø ý]þ ø ø. @G ö +ô ý]þ ö #Üø ó ûSøûHûAö+÷ . • D. !ý þ ø ø <@ý õ

(76) Aö$ö÷ • •. < ø ûR. 3URMHFW$GPLQLVWUDWLRQ. ,VVXH7UDFNLQJ0RQLWRULQJ5HSRUWLQJ 5RDGPDSV. .  SAP AG 2006. . Solution Manager for Implementation. . Procedure Model (Roadmaps) • Focus: product-specific information; no project management • Knowledge transfer to project team and technical implementation aspects are key elements • Available services aligned with the Procedure Model. . Implementation Content • Business process repository as initial input for a process-driven design of a customer solution • Initial focus: mySAP CRM and mySAP SCM implementations. . Tools • Basic ASAP tools (Blueprint and Master List functionality) • Integrated use of customizing and test tools • Focus: scoping, process-oriented configuration and testing, status and issue tracking. © SAP AG. SM100. 2-19.

(77) 6$36ROXWLRQ0DQDJHUDVFHQWUDO FROODERUDWLRQ KXE 6$3&XVWRPHU @ Æü. ó þ ö

(78) ûAö+÷ 6ROXWLRQ/DQGVFDSH. Experts. h3hUijiNfIfId d. SAP Solution Manager Service Marketplace. [U[U\g\^]]S_a_a`c`cb b d d e ef f [3[3\g\g]S]S\k\k]3]3l l [3[3\^\g]]`Ùp p m m mnmne eo o d d e eqnqn_ _. Knowledge. 6HUYLFH,QIUDVWUXFWXUH $SSOLFDWLRQ0DQDJHPHQW. ü õ ý û;öø ý ó þ ö û$ö÷. ó û þ ú-ø ý r ó þ ús ø ûø+ö øIóøöû!ø ý. .  SAP AG 2006. . Issues:. . Harmonize Visualization of System Landscapes in SLM and Solution Manager. . Scenarios are shipped via BPR/Service Marketplace and Master Component Repository. . Scenarios implemented are stored in Solution Manager and SLD. . Clarify relationship between Versions in Solution Manager and and Editions in Solution Builder (PPMS). . Interfaces between Solution Manager and SLM have to be defined. . Define Use Cases. © SAP AG. SM100. 2-20.

(79) 6$36ROXWLRQ0DQDJHU² 9DOXH3URSRVLWLRQ &ROODERUDWLRQ. ä7 Ö +ÚñÞÝÚê Ø èåòÚåë}é ä7 Ö w çãÛÝé:Ø ò Ú}Þ}Úê ØèåòÚëñé ä 7D Ö Ùñéæ ÞàÚ ê Ø áÝíêãäçåèèÝØ ×Aé ä 7Ö ØëãÛ çÜê éæ ë}î . w. ä7 Ö xßçàÙñí}éæ Øë ä. Ö +ØÜÛÝé!æ ëÝî. Ó òÆèê ÚåòÚëñéoíñéæ ØëØ>y ä 7ÖJä Ø ê çñéæ ØëãÛ +ä Øê çñéæ Øë ì7Ø ëæ éoØ ×bæ ëÝî æ íÝî ë}ØåÛ}é!æ Ù Û. &XVWRPHU x>yIyæ Ùåæ Úë}Ùãâ. {^^| |''. 6$36ROXWLRQ 0DQDJHU w íåëàîÜÚ % Ú'& ç}Ú}Û}é ì4íë}íàî òD. äÚå×AÞæ Ù}Ú ÚñÛ . Ô+×$íåëñÛèñí×AÚë}Ùãâ. ó þ ýø. Aö ø ü4ý!þ ø . z

(80) {v|'}v~>'|. z {g | èÜî×<íàßÚÄ>Ø y ä 7ÖJä+Ø ê çãé!æ ØëñÛ Úê æ ÞÝÚ× âSØ y ä 7ÖJä Ú× Þ æ Ù}ÚÝÛ. w. Ø ëãé!×$Ø ê. tê Úvuæ áæ ê æ é<â. @@ûõ+ö6õ ý #ø X<öû!ø ÷ ý õûø õ õû þ ö úÌõöõ ÷+ø ú2ø+ö û. 7KHVXSSRUWKXEDQGWKHJDWHZD\WR6$3. .  SAP AG 2006. . On the right-hand two-thirds of the slide you have a greyed-blue box representing the customer’ s environment. Their IT landscape contains the applications we’ d expect to see – some SAP and some not. In the center of this landscape we have the core business processes that drive the company, and the IT group’ s charter – to implement, operate, and continually optimize these processes, as well as the applications. The goals of the CIO are represented in black in this box – efficiency, transparency, control, and flexibility. (These are the four core value props that SAP Solution Manager provides) That is, if a CIO could maximize these four goals then the chances of success in their mission would be significantly increased. Moving to the left, the customer’ s IT landscape is connected to the SAP Solution Manager.. . SAP Solution Manager is a unique solution stack which enables several of its integrated business processes to seamlessly interact with the customer’ s IT landscape (change management, service desk, etc). These business processes are core function within SAP Solution Manager and replace the customer’ s need to purchase, implement, and maintain separate software and hardware solutions that provide these functions. This is one very significant benefit that SAP Solution Manager brings – the ability to replace several un-integrated tools with a single product which provides seamless integration, a single user interface (for ease of use), and which comes at no extra cost as a part of their SAP Standard Support. The importance of SAP Solution Manager in both cost and efficiency terms cannot be over-stated.. . However, there’ s an additional benefit with SAP Solution Manager, and that is its role as a gateway to SAP’ s Active Global Support (AGS) organization and the network of over 12,000 professionals we can call upon to assist our customers. Specifically (on the far left-hand of the slide), AGS is able to interact with a number of SAP organizations to ensure that our customers receive the right assistance at the right time. These organizations would include SAP Development, SAP Consulting, and so on. This unique solution stack logs the information AGS needs to address a customer’ s OSS issue, which in turn means we can respond faster and more accurately than otherwise. That is, SAP Solution Manager provides our customers with all the productivity and response time benefits of e-support as well as with the certainty that their needs and challenges are being dealt with by the most expert resource available.. © SAP AG. SM100. 2-21.

(81) 6$36ROXWLRQ0DQDJHU6FHQDULRV ,PSOHPHQWDWLRQ RI6$3VROXWLRQV. 6ROXWLRQ PRQLWRULQJ. Global rollout. EarlyWatch Alert. SAP Methods & Tools. System monitoring. Customizing sync.. Service level reporting. E-learning mgmt.. Test management 8SJUDGHRI 6$3VROXWLRQV. SAP Methods & Tools. E-learning mgmt.. Business process monitoring {kg| |v. Central system administration. &RUH %XVLQHVV 3URFHVV. Test management. z {g |. 'HOLYHU\RI 6$3VHUYLFHV. Onsite/remote delivery SAP Safeguarding. z

(82) {v|'}v~>'|. 6HUYLFHGHVN. Best Practices for messaging. Solution Manager Diagnostics. &KDQJHUHTXHVW PDQDJHPHQW. Follows ITIL standards. Maintenance processes. .  SAP AG 2006. © SAP AG. SM100. 2-22.

(83) 6$36ROXWLRQ0DQDJHU /LFHQVLQJ *HQHUDO. All licenses to support customers own, licensed SAP systems are included in the standard maintenance fee, e.g. CRM, BI and KW licenses.. 0RQLWRULQJ ,PSOHPHQWDWLRQ. Licenses to implement or monitor customers own non-SAP solutions are included in the standard maintenance fee as well. 6HUYLFH'HVN. Each user working on non-SAP messages needs an own professional user in the SAP Solution Manager system. .  SAP AG 2006. . Details on licensing has to be clarified with your local account representative.. © SAP AG. SM100. 2-23.

(84) 5HOHDVH6WUDWHJ\. 0RWLYDWLRQ. 6XSSRUWIRU,7,/SURFHVVHV $YDLODEOH)XQFWLRQDOLWLHV 5HOHDVH6WUDWHJ\. .  SAP AG 2006. © SAP AG. SM100. 2-24.

(85) (YROXWLRQIURP$6$3WR6$36ROXWLRQ0DQDJHU 6$36ROXWLRQ0DQDJHU. <ö

(86) û õ . ø ø õø; . ø øõ ø? . þ úZ. ø ø õ ø6I . ø ø õø; . þ ö øö û. Front-end to SAP Service Infrastructure. Solution Implementation Service Desk, Monitoring & Distribution Upgrade. ø øõ ø"

(87) . Change Request Management. Cooperation + Continuous Improvement. Manage Technical Change. Optimize Collaboration with SAP Services. ÿ øöø û

(88) * úZ ý;þ

(89) ø+úÊøö û Mitigate Risk. Pro-active Monitoring. Accelerate Optimize Implementations IT Support. .  SAP AG 2006. © SAP AG. SM100. 2-25.

(90) 5HOHDVH6WUDWHJ\DQG0DLQWHQDQFH ¸º¹ »

(91) ¼N½¾¿R½ À6Á ÁÂ. ì.íåæ ëñÛÝé×<ÚÝíàòDÉoì4íæ ëñéoÚåëÝíåëàÙñÚ. Ã ÄÈ Å^ÆÇ Æ. »

(92) ¼j½ ÕGÖ ×3ØÙÖ ÚÛ Ö

(93) Ü ÁÂ. ì4íæ ëñÛ}é×<ÚÝíÜòDÉ$ì7íåæ ëñéoÚë}íëÝÙ}Ú. ÃÄÈ ÅgÆIÇ Æ. »¼j½»Ý

(94) Þß P× à Ý

(95) á ârÚ á Ú

(96) ã Ö

(97) Ü Â å Á ÃÄIÈ Å^ÆÇ Æ. »¼j½»Ý

(98) Þß ×Pà Ý

(99) á ârÚ á Ú

(100) ã Ö

(101) ÜKä ånæ Ã ÄÈ Å^ÆÇ Æ. 'k. ì4íæ ëñÛÝéH×$Ú}íÜòjÉ:ì4íæ ëñé$Úë}íë}ÙÝÚ. ì7íæ ëãÛ}é!×AÚàíÜòjÉoì7íåæ ë}é$ÚëñíëÝÙ}Ú ¥ ¦§. ¨ ©ª. ¥ ¦§ '^. vv. ° ·Ì° Ì bvÊ¶ ´Ë ·n °n·¶ ·3³n° Í Î ÏaÐ ÑkÔPÐgÓ. _P«¬ ®3¯° ±¬ ² ° ³ ´ µ ´ ³ bk¶ ´ ·I °3·n¶· ³n°. ° · Ì °Ì b'Ê3¶n´Ë ·I ° · ¶ ·³n° Í Î ÏaÐ6ÑgÒgÐaÓ. ° · Ì° Ì b'Ê¶ Ë´ ·I ° · ¶ ·³n° Í Î ÏaÐ6ÑgÔgÐaÓ. _a« ¬I ®U¯'° ±¬ ² °n³´ µ ´ ³ bv¶ ´ ·n °· ¶· ³ °. ì7íæ ëãÛÝé!×<ÚÝíàòjÉoì7íæ ëãé:Úåë}íåëàÙñÚ. ÃÄÈ ÅgÆIÇ Æ. »¼j½»Ý

(102) Þß ×Pà Ý

(103) á ârÚ á Ú

(104) ã Ö

(105) Üä

(106) å À. ° · Ì °Ì bvÊ3¶ Ë´ ·n ° · ¶ ·3³I° Í Î ÏgÐ Ñ^ÒaÐaÓ. _P«¬ ®U¯'° ±3¬²°n³ ´ µ ´ ³ b'¶ ´ ·n ° ·n¶3· ³n°. _P«¬ ®3¯° ±U¬² ° ³ ´ µ ´ ³ b'¶n´ ·I °3·n¶· ³n°. _g« ¬ ®U¯'° ±3¬3² °n³ ´ µ ´ ³ b'¶ ´ ·n ° · ¶ · ³ °. ¥ ¦§. 'k ¡'^¢. ¥ ¦§ ¨ ©ª. ¥ ¦§ vv£. vv¤. 'c. ¨ ©ª 'v. ¨ ©ª c. ¨ ©ª P. . .  SAP AG 2006. . The Mainstream Maintenance of the SAP Solution Manager 4.0 is geared to the Extended Maintenance of the SAP NetWeaver 04 release.. . SAP Solution Manager 3.2 will stay in mainstream maintenance until March 2009. Afterwards, it will move into customer-specific maintenance.. . SAP Solution Manager 4.0 is focusing on optimizing support processes, collaboration, and implementing continuous improvement processes. The mass shipment of SAP Solution Manager 4.0 has started in April 2006.. © SAP AG. SM100. 2-26.

(107) 5RDGPDSIRU6$36XSSRUW,QIUDVWUXFWXUH çrIé. çº'Ié çjIè çrIè. ý ùõ ý. . è è. ø ". SAP Solution Manager required for root cause analysis of all SAP solutions Corporate functionality only via SAP Solution Manager. SAP Solution Manager 4.0. Mass shipment SAP Solution Manager 4.0. WebAS 7.00. Start of Ramp-Up SAP Solution Manager 4.0. Solution Manager Diagnostics required for root cause analysis of Java based SAP solutions Mass shipment SAP Solution Manager 3.2 mySAP ERP 2004 requires SAP Solution Manager Improved message entry process via SAP Support Portal. SAP Solution Manager 3.2 WebAS 6.20. Solution Manager Diagnostics WebAS 6.40. Mass shipment Solution Manager Diagnostics. .  SAP AG 2006. . 6$36ROXWLRQ0DQDJHU. . This upcoming release will focus on three major aspects:. . Enhanced support of \RXUNH\VXSSRUWSURFHVVHV The SAP Solution Manager 4.0 release will offer functionality to assist you with your major application management tasks. For example, it will allow you to implement support packages and SAP notes end-to-end. SAP Solution Manager 4.0 will provide functionality to automatically identify relevant patches, and document and manage their implementation, testing, and import to your production systems.. . &RQWLQXRXVLPSURYHPHQW services: The SAP Solution Manager has detailed information about your solution, such as key business processes and the SAP system landscapes. If your SAP competence center selects the new continuous improvement service offering, an appointed SAP contact will be named, and will actively work with you on a regular basis to solve your business-critical SAP issues.. . 7HFKQLFDOLQWHJUDWLRQ of Solution Manager Diagnostics into the SAP Solution Manager platform.. © SAP AG. SM100. 2-27.

(108) 6$36ROXWLRQ0DQDJHU .H\%HQHILWV 'HOLYHUHGDWQRDGGLWLRQDOFRVW ,QFUHDVLQJUHOLDELOLW\RI,7VROXWLRQ 5HGXFLQJFRVWRILPSOHPHQWDWLRQ RSHUDWLRQVDQGFKDQJHPDQDJHPHQW SURMHFWV $FFHOHUDWLQJWLPHWREHQHILW /HYHUDJLQJH[LVWLQJ,7LQYHVWPHQWV $YDLODEOHIRUH[LVWLQJ 6$3VROXWLRQV. .  SAP AG 2006. . mySAP ERP 2004 is designed to meet today’s changing demands on ERP. It enables new levels of business process and technology integration while laying the foundation for incremental evolution of your solution.. . Using the SAP Solution Manager along the lifecycle of your mySAP ERP solution leads to a IDVWHU LPSOHPHQWDWLRQDQGPRUHHIILFLHQWRSHUDWLRQ by providing all implementation and upgrade content for commonly used standard processes. In addition, projects become more transparent by having the up-to-date central project documentation all in one place at any point in time. To ensure the availability of this application management platform, a SAP Solution Manager system (minimum requirement 3.1 SP20) is WHFKQLFDOO\UHTXLUHG to perform any upgrade or installation of mySAP ERP 2004.. © SAP AG. SM100. 2-28.

(109) 6XPPDU\. 6$36ROXWLRQ0DQDJHUHQVXUHV« 7UDQVSDUHQF\. … entire IT landscape – SAP and non-SAP … entire solution lifecycle. (IILFLHQF\. … gateway to SAP services … aligned with SAP’s best practices. )OH[LELOLW\. … tools, content, and services … scenario driven. &RQWURO. … full integration. .  SAP AG 2006. . These four points represent the core value proposition of SAP Solution manager. • Transparency – the ability for a CIO‘s solution lifecycle and IT landscape (SAP and non-SAP) to be made transparent through SAP Solution Manager‘s functionality • Efficiency – a platform (SAP Solution Manager) which provides best-in-class best practices – which promote efficiency and operational effectiveness, as well as providing a gateway to SAP‘s support. This gateway function is important because it leverages the EarlyWatch alerts which are automated, seamless ‚health checks‘ for the customer‘s SAP landscape and core business processes. • Flexibility – the capability to utilize SAP Solution Manager in a number of different ways (use cases) to maximize its impact on the organization and minimize operating costs. • Control – this is a critical and elusive target for a CIO, and SAP Solution Manager is able to provide it because of its complete integration as well as the way in which it can automatically map and analyze the core business processes within the SAP application landscape. Inevitably, such a degree of control will lower the time it takes to achieve a return on the implementation of SAP Solution Manager.. © SAP AG. SM100. 2-29.

(110) 6ROXWLRQ0DQDJHU2YHUYLHZ8QLW6XPPDU\. <RXVKRXOGQRZEHDEOHWR. 'HVFULEHWKHDQGDYDQWDJH RIWKH6$36ROXWLRQ 0DQDJHU. *HWDQJHQHUDORYHUYLHZRIWKH6$36ROXWLRQ 0DQDJHUIXQFWLRQDOLWLHV. ([SODLQWKHJHQHUDODQGUHOHDVHVWUDWHJ\RIWKH6$3 6ROXWLRQ0DQDJHU. .  SAP AG 2006. © SAP AG. SM100. 2-30.

(111) 8QLW&RXUVH&RQWHQW — — — — — — — —. K4"LH*

(112) F'G@0"HIDJ5+"5 E C 7@?A0 ; -* *%+"D)5 "!5 E 9 4:; < %=0 >7@?A0 ; B*++++

(113) * 3 4+"5

(114) -678 &')( *+%-,. / 0 1*+*%+ 2+ . — — — — —. + U 7@?A0 ; -1*+ *%"76G *% P

(115) + QR *"P? 1ST*

(116) +(? "H + O 4"H5

(117) 2B 5 ?0 -7 ?<0 P @ ,7 "P A % + @FM 4"H5

(118) -67?A 5++" + @F+F N0 $ -K4"!

(119) 1 ! "# < %. !"# $ %

(120) . .  SAP AG 2006. © SAP AG. SM100. 3-1.

(121) 2EMHFWLYHV´6HWWLQJ8S6ROXWLRQ/DQGVFDSHVµ. $WWKHFRQFOXVLRQRIWKLVXQLW\RXZLOOEHDEOHWR 'HVFULEHWKHXVHRI6/'DQG706/,6 6HWXS\RXUV\VWHPVLQWUDQVDFWLRQ606< *HQHUDWHWKHQHFHVVDU\5)&FRQQHFWLRQV 8VHWKH6ROXWLRQ'LUHFWRU\ /RJLFDO&RPSRQHQWV. 6ROXWLRQ$WWULEXWHV. 6HWXS%XVLQHVV3URFHVVHV. &UHDWLQJ6ROXWLRQ/DQGVFDSHV. .  SAP AG 2006. © SAP AG. SM100. 3-2.

(122) 6HWWLQJXS6ROXWLRQ /DQGVFDSHV 6$36ROXWLRQ0DQDJHULQ6\VWHP/DQGVFDSH 6\VWHP/DQGVFDSH 7UDQVDFWLRQ606<

(123) *HQHUDWH5)&'HVWLQDWLRQV /RJLFDO&RPSRQHQWV. 6ROXWLRQ/DQGVFDSHV 6ROXWLRQ'LUHFWRU\ %XVLQHVV3URFHVVHV. . © SAP AG. SM100. 3-3.

(124) 6\VWHP/DQGVFDSH'LUHFWRU\ 6/'

(125) 6\VWHP/DQGVFDSH'LUHFWRU\ 6/'

(126). 6\VWHP/DQGVFDSH'LUHFWRU\LVDQ6$31HW:HDYHU FRPSRQHQW. ,WLVFRPSOHWHO\LPSOHPHQWHGZLWK-DYDWHFKQRORJ\DQG GHSOR\HGDVD-DYDFRPSRQHQWRQWKH6$3:HE$SSOLFDWLRQ 6HUYHU. $V6\VWHP/DQGVFDSH'LUHFWRU\LVDOUHDG\FRQWDLQHGLQWKH LQVWDOODWLRQRIHYHU\6$3:HE$SSOLFDWLRQ6HUYHU-DYD RUKLJKHU. ,WSURYLGHVLQIRUPDWLRQWKDWLVUHTXLUHGIRUDYDULHW\RI DSSOLFDWLRQVDQGSURFHVVHV 6RIWZDUH/LIHF\FOH0DQDJHPHQW 6$3([FKDQJH,QIUDVWUXFWXUH 6$31HW:HDYHU'HYHORSPHQW,QIUDVWUXFWXUH 6\VWHP0DQDJHPHQW /DQGVFDSHUHODWHGVXSSRUWVHUYLFHV EDVHGRQ6$36ROXWLRQ0DQDJHU

(127). .  SAP AG 2006. . Today’s system landscapes consist of multiple distributed software components with different platform dependencies, different interfaces, and different requirements placed on installation and change management. An overall concept is required that facilitates the implementation, upgrade, and maintenance of your system landscapes – including the SAP NetWeaver system landscape you are installing. This is where 6\VWHP/DQGVFDSH'LUHFWRU\(SLD) comes into play.. . The most straightforward scenario is the use of a single SLD. However, depending on organizational, operational, or security reasons, it is also possible to have more than one SLD distributed over the system landscape. Automatic message forwarding as well as sophisticated data export and import functions are provided to support the operation of multiple SLDs.. © SAP AG. SM100. 3-4.

(128) 6$36ROXWLRQ0DQDJHU6\VWHP/DQGVFDSHDQG6/' $OVR6$36ROXWLRQ0DQDJHUSURYLGHVDV\VWHPGDWD UHSRVLWRU\ 7UDQVDFWLRQ&RGH606<

(129) %RWKV\VWHPGDWDUHSRVLWRULHV606<DQG6/'FDQEHXVHG LQGHSHQGHQWO\RIHDFKRWKHU 6\QFKURQL]DWLRQSRLQWV H[LVW606<FDQUHDGGDWDIURP6/' 7KHXVHRIWKHVHUHSRVLWRULHVGHSHQGVXSRQFXUUHQW FXVWRPHUµVODQGVFDSH ,IWKHUHDUHRQO\$%$3 FRPSRQHQWVLQSODFH Æ 6/' LVRSWLRQDO. ,IWKHUHDUHDOVR-DYD FRPSRQHQWVLQSODFH 6$31HW:HDYHU (QWHUSULVH3RUWDO6$31HW:HDYHU([FKDQJH,QIUDVWUXFWXUHHWF

(130) Æ 6/' LVPDQGDWRU\. .  SAP AG 2006. . You set-up the automatic data transfer from the Landscape Information System. . (LIS) and the System Landscape Directory (SLD), to get system data for the. . 6ROXWLRQ0DQDJHU6\VWHP/DQGVFDSH.. . The SAP Solution Manager can get server, database and system data. . automatically with this data.. . 3UHUHTXLVLWHV. . For using the /DQGVFDSH,QIRUPDWLRQ6\VWHP /,6

(131) : • You have assigned the Solution Manager to a transport domain in the Transport Management System (STMS) • Or you have specified the Solution Manager system as the new domain controller in the transport management system.. . For using the 6\VWHP/DQGVFDSH'LUHFWRU\ 6/'

(132) : • You have setup the System Landscape Directory (SLD).. © SAP AG. SM100. 3-5.

(133) (VWDEOLVK&RQQHFWLRQIURP6$36ROXWLRQ0DQDJHUWR6/'. .  SAP AG 2006. . The Solution Manager system data should be saved in its SLD. 5HTXLUHPHQWV. • <RXKDYHLQVWDOOHGD6ROXWLRQ0DQDJHU'RXEOH6WDFN A connection to send system data to SLD is created automatically. • To send data from SLD to ABAP you must start a server in Java. This server will wait for ABAP calls. • For the communication between ABAP and Java the SAP Solution Manager needs the user SAPJSF. • The user SAPJSF is assigned in the Visual Administrator. This User is used to read data from SLD. • You have to activate an RFC connection (such as sapsldapi_J2E) in the Visual Administrator for SLD under -FR5)&3URYLGHU -> 5)&GHVWLQDWLRQ.. © SAP AG. SM100. 3-6.

(134) 6HWXS'DWD7UDQVIHU2SWLRQ 6ZLWFKWR6/'DVV\VWHPGDWDUHSRVLWRU\ 7REHGHILQHGLQWUDQVDFWLRQ606<B6(783. .  SAP AG 2006. . . You should choose the System Landscape Directory (SLD) as the source for the data transfer, if SLD is set-up in your system landscape. The Landscape Information System (LIS) only gets data about system names, clients and software components in the systems, for systems in the transport domain. SLD gets server and database data independently of the transport domain. To access the 6\VWHP/DQGVFDSH'LUHFWRU\ 6/'

(135) : • Choose (GLW → ([SHUW6HWWLQJV.. • Specify the server from which SLD data is to be read, as 6/'+RVW. • You can change the other options. • You can also change these options when setting-up the System Landscape Directory. • You can write data back into SLD by entering a value for :ULWH'DWD%DFNLQWR6/'. • Choose &RQWLQXH.. . For further information, see 6\VWHP/DQGVFDSH'LUHFWRU\ in the SAP Library.. © SAP AG. SM100. 3-7.

(136) $XWRPDWLF6\VWHP'DWD&DSWXULQJXVLQJ/,6706RU6/' /DQGVFDSH,QIUDVWUXFWXUH6HUYHU /,6706

(137) . 5HDGVWKHGDWDIURPWKH7UDQVSRUW0DQDJHPHQWV\VWHPZKHUH DOOV\VWHPVLQFOXVLYHWKH6$36ROXWLRQ0DQDJHUEHORQJVWR. 6\VWHP/DQGVFDSH'LUHFWRU\ 6/'

(138) . ,VWKHFHQWUDOLQIRUPDWLRQSURYLGHULQDV\VWHPODQGVFDSH. .HHSVLQIRUPDWLRQDERXWDOODYDLODEOH6$3SURGXFWV FRPSRQHQWVDQGYHUVLRQV. &DQUHJLVWHUDQ\WKLUGSDUW\SURGXFWVLQWKHV\VWHP ODQGVFDSH. 6/'VKRXOGEHXVHGLI6$3([FKDQJH,QIUDVWUXFWXUH ;,

(139) LV DOVRLQXVH. .  SAP AG 2006. . Systems outside of LIS and SLD can not be imported automatically. If you have systems outside of LIS and SLD, you will need to maintain the configuration manually. The job will check whether system data (client, application server or new system) has changed and updates this data in transaction SMSY.. © SAP AG. SM100. 3-8.

(140) :KLFKGDWDLVUHWULHYHGIURP/,6706DQGIURP6/'" 'DWDUHWULHYHGIURP/,6 )RU$%$3V\VWHPV. 'DWDUHWULHYHGIURP6/' )RU$%$3V\VWHPV. V 4 W* X V 4 W0+ZY+" V 1 * % I+"5++" V 'J?A H\[! < L "!2*P L;";

(141) ?A +H*Y? ^]M MM _ Va` b*?<? \+LbcE*"d>

(142) = b. 7KLVGDWDLVFROOHFWHGIRUDOO V\VWHPVHPEHGGHGLQWRWKH WUDQVSRUWGRPDLQRI6$36ROXWLRQ 0DQDJHU. V H e*+X V H e+0+ZY" V *%"H5 " V ')?A ^[ $L! "dX*; ALP"d

(143) +?< *Y+? >]MM+M_ Vf` H*?A? - Lb:E*"!I

(144) = @ : g "!? *++g* Z*d

(145) +(-? 5? V ` H*

(146) IL;( 1 H V 4"5 "H^* % ^!^P(+\ A H*

(147) V 4"5 " *H* V 64* b*Y * ^+L *1 H+ V 4"5 " +L*\ * b*Y* . )RU-DYDV\VWHPV. V ` H*

(148) IL;( 1 H V 4"5 "H^* % ^!^P(+\ A H*

(149) V 4"5 "4"! ? ^[bb _ V ` H*?A? - Lb:E*"!I

(150) = @ :g "!? *++g* Z*d

(151) +(-? 5? . .  SAP AG 2006. . . The System Landscape Directory (SLD) contains two kinds of contents: the FRPSRQHQWLQIRUPDWLRQand the ODQGVFDSHGHVFULSWLRQ: The ODQGVFDSHGHVFULSWLRQprovides an exact picture of installed landscape elements including the connections between the systems. The content of the landscape description is created during the landscape implementation and automatically maintained through the whole software life-cycle.. The FRPSRQHQWLQIRUPDWLRQdescribes the building blocks of solutions and their possible combinations and dependencies. It describes the world of installable landscape elements. The various types of dependencies between building blocks play an important role in landscape implementation, change management and solution validation. The content of the component information is delivered by SAP and can be updated - for more information about updating the component information, see SAP Note 669669.. © SAP AG. SM100. 3-9.

(152) 6\VWHP/DQGVFDSH'LUHFWRU\ &RQWHQW 7KUHHFDWHJRULHV &RPSRQHQWUHSRVLWRU\ &5

(153) . 3URGXFWVDQGVRIWZDUHFRPSRQHQWV. /DQGVFDSHGDWD /'

(154). 6\VWHPVDQGV\VWHPJURXSV. VHUYHUV. FOLHQWV. EXVLQHVVV\VWHPV. 1DPHUHVHUYDWLRQGDWD 15

(155) YLHZDQGFKDQJH&,0GDWD. &,0FODVVGHILQLWLRQV. PDQDJHQDPHUHVHUYDWLRQIRUGHYHORSPHQW. .  SAP AG 2006. . CR- is the component repository data. It includes the possible versions, support packages and it‘s combinations for pre-selections. e.g. For product R/3 there are the allowed version 3.1, 4.0b. 4.0B, 4.0C,…this would be CR. With help of CR content SAP avoid wrong or non existing LD data for SAP products.. . LD- these are the concrete descriptions of existing systems e.g. There is a R/3 System version 3.1 SID Support Package xxx …. . NR- is important for development if you have reserved name spaces for developed objects.. . CIM-Common Information Model -> Skip to next slide. © SAP AG. SM100. 3-10.

(156) 6\VWHP/DQGVFDSH'LUHFWRU\ 6WDQGDUGV &RPPRQ,QIRUPDWLRQ0RGHO &,0 &,0LVDFRPPRQGDWDPRGHORIDQLPSOHPHQWDWLRQ QHXWUDOVFKHPDIRUWKHGHVFULSWLRQRIRYHUDOO LQIRUPDWLRQLQDQHWZRUNHQWHUSULVHHQYLURQPHQW ,VDQ,PSOHPHQWDWLRQRIWKH'LVWULEXWHG0DQDJHPHQW 7DVN)RUFH V '07)

(157) :HE%DVHG(QWHUSULVH 0DQDJHPHQW :%(0

(158) LQLWLDWLYH '07)DVWKHLQGXVWU\RUJDQL]DWLRQOHDGLQJ GHYHORSPHQWDGRSWLRQDQGXQLILFDWLRQRIPDQDJHPHQW VWDQGDUGVDQGLQLWLDWLYHVIRUGHVNWRSHQWHUSULVHDQG ,QWHUQHWHQYLURQPHQWV /DQGVFDSH'HVFULSWLRQDQG&RPSRQHQW,QIRUPDWLRQ EDVHGRQ&RPPRQ,QIRUPDWLRQ0RGHO &,0

(159) RIWKH '07). .  SAP AG 2006. . SLD is the SAP solution of a proposal by Distributed Management Task Force (DMTF). They founded an initiative called Web-Based Enterprise Management. SAP is in leadership at DMTF.. . The common Information Model is one outcome. It has become a de facto standard for describing and storing data on a system landscape. The System Landscape Directory bases on that CIM.. © SAP AG. SM100. 3-11.

(160) &HQWUDO6/'IRUDOO6$31HW:HDYHU$SSOLFDWLRQV 6/'. 6$3 6ROXWLRQ 0DQDJHU. 6/'. +$&OXVWHU. $ ~} <|4|: <. hPidj NetWeaver Development Infrastructure. hPi!j. kmlon. hPi!j p!q rHs. :HE '\QSUR. P ym. kol#n. pdq rHs. kmlon. p!q rHs t u7vwyxyz{}|~ ~H <|H HzH A. :HE '\QSUR. .  SAP AG 2006. . &HQWUDO6/'IRU$OO$SSOLFDWLRQV • Simplicity is often the key to robust and easy to handle system landscapes. The use of only one central SLD for an entire system landscape is shown above. Possible SLD clients are the SAP Exchange Infrastructure (SAP XI), SAP Solution Manager, WebDynpro applications, and the SAP NetWeaver Development Infrastructure (NWDI). These systems may consist of several instances for development (Dev), quality assurance (QA), and production (Prod). Nevertheless, all instances are bound to one central SLD. This imposes high demands on the SLD regarding availability and stability. +LJKDYDLODELOLW\concerning operation, maintenance, and upgrade of the SLD is crucial for clients that depend on SLD data.. © SAP AG. SM100. 3-12.



(163) 7UDQVDFWLRQ606<² &UHDWLQJ6HUYHU(QWULHV. {} yzy z@b)z <|cG|~} . ¡ ~}¢{G$z{~ z| £ c| . ¤¢¥ ~| ¦.¦y)z}|~ £ } ~¢ z z ~! A|yz £ : | . .  SAP AG 2006. . The system determines the displayed data automatically, if you have set-up automatic data capture for the system landscape. The system cannot determine all server data automatically, so you can complete it, e.g. with the frequency.. . You create attributes for servers, databases, systems, system components and main instances, to be able to assign additional properties to them, e.g. hardware attribute information or the person responsible for a system.. © SAP AG. SM100. 3-14.

(164) 7UDQVDFWLRQ606<² &UHDWLQJ'DWDEDVH(QWULHV. {} ) z zy4b)zy $|}$|)~ £ |c|y§|}. ¡ ~}¢{G$z{~ z| £ c| . ¤¢¥ ~| ¦.¦y)z}|~ £ } ~¢ z z ~! A|yz £ : | . .  SAP AG 2006. . 3UHUHTXLVLWHV. • You are in the 6ROXWLRQ0DQDJHU6\VWHP/DQGVFDSH transaction SMSY).. . 3URFHGXUH. • Select the landscape component 'DWDEDVHV, and choose &UHDWH in the context menu. • Enter the required data. • Choose attribute values from the possible entries help in the Other Attributes tab. • Save the changes.. © SAP AG. SM100. 3-15.

(165) 7UDQVDFWLRQ606<² &UHDWLQJ6\VWHP(QWULHV. {} ) z zy4b)zy $|}$|)~ ¦c. t z} H{ ¨}v |~y~ £© ¨v $ £ z ~ © |~ £ !{} ¨ ~c| £ v $ £ z} ª A ~ ©. 4| ~:| ~¢!{öt z} ~G7| ~ ~}:|~z} ©. .  SAP AG 2006. . You create systems to be able to use them in Solution Manager projects.. . The system determines the displayed data automatically for ABAP-based SAP products, if you have setup automatic data capture for the system landscape. You can enhance this data or switch the data source to manual maintenance.. . For non-ABAP-based SAP products, and non-SAP-products, you must create systems yourself, to use them in your solution landscape in operational processing.. . You can also create systems under the guidance of assistants. To call the assistant, select the landscape component 6\VWHPV, and choose &UHDWH1HZ6\VWHPZLWK$VVLVWDQWV, in the context menu.. © SAP AG. SM100. 3-16.



(168) 3UHUHTXLVLWHV 6DWHOOLWH6\VWHPV3UHSDUDWLRQ &KHFN8VHU3URILOHVLQ6DWHOOLWH6\VWHPV <RXUHTXLUHDXVHULQVDWHOOLWHV\VWHPVZLWKDXWKRUL]DWLRQV IRUWKHIROORZLQJIXQFWLRQV *HQHUDWH5)&FRQQHFWLRQV DXWKRUL]DWLRQREMHFW6B5)&

(169). *HQHUDWH5)&FRQQHFWLRQVRIWKH7UXVWHGW\SH DXWKRUL]DWLRQ REMHFW6B5)&$&/QRWSDUWRI6$3B$//

(170). 7REHDEOHWRJHQHUDWHDQGXVH7UXVWHG6\VWHPVWKHXVHU ,'VRIWKHWZRV\VWHPVPXVWEHWKHVDPH. (QVXUHWKDWWKH6ROXWLRQ0DQDJHULVDEOHWRFROOHFWGDWD IRU6ROXWLRQ0RQLWRULQJLQWKHVDWHOOLWHV\VWHPV 6XSSRUW6HUYLFHVUHTXLUHWKHDSSURSULDWH67$3,LQWKH VDWHOOLWHV\VWHPDVVSHFLILHGLQQRWH. .  SAP AG 2006. © SAP AG. SM100. 3-18.

(171) *HQHUDWH5)&'HVWLQDWLRQV , 5)&'HVWLQDWLRQVZLWKLQWKH6ROXWLRQ0DQDJHU. 60B6,'!&/17&OLHQW!B5($'. V. This RFC will be used to “Read system data remote” from transaction SMSY, to read the “Data Collection method” for System Monitoring.. 60B60B6,'!&/17&OLHQW!B70:. V. This RFC will be used for the Change Manager.. 60B6,'!&/17&OLHQW!B/2*21. V. This RFC will be used by the System Monitoring for accessing the “Analysis Method”.. 5)&'HVWLQDWLRQVLQERWKWKH6$36ROXWLRQ0DQJHUDQGLQWKH 6DWHOOLWH6\VWHP 60B6,'!&/17&OLHQW!B75867('. V. This RFC will be used by the Customizing Synchronization functionality and by the System Monitoring for accessing the “Analysis Method”.. 5)&'HVWLQDWLRQUHTXLUHGLQWKH6DWHOOLWH6\VWHPRQO\. 60B6,'!&/17&OLHQW!B%$&.. V. This RFC will be used to send Service Data and Support Desk messages from the Satellite system to the SAP Solution Manager system.. .  SAP AG 2006. . From the “System Landscape”, transaction SMSY, select “Landscape Components” and in the tree “Systems” Æ <Product> Æ <SID> Æ <Instance>.. . Go to the tab “Clients”, select the client and choose the “Generate RFC Destinations” button. A new screen “Generate RFC Destinations” will be displayed. Select the RFC Destinations to be created by marking the check boxes, and choose the “User Option”. You can generate RFCs automatically from transaction SMSY.. © SAP AG. SM100. 3-19.

No results found