SLD Deployment
4 likes•1,706 views
- The document discusses how Australia Post transformed their System Landscape Directory (SLD) from a maintenance overhead to a valuable asset by carefully planning the SLD and establishing proper governance. - It explains SLD concepts like how it is used to define the landscape, software components, and how it is updated manually or automatically. - It also covers considerations for Australia Post's SLD strategy like where to run it, having separate SLDs for development and production, and ensuring high availability.
![QUESTIONS? How to contact me: Tony de Thomasis [email_address]](https://image.slidesharecdn.com/masteringtechnologiestdt-090519065527-phpapp02/85/SLD-Deployment-22-320.jpg)
SLD Deployment
- 1. Management of the NetWeaver SLD in a Complex Landscape Tony de Thomasis NetWeaver Infrastructure Architect Australia Post
- 2. Introduction In this presentation I will explain how Australia Post transformed the System Landscape Directory (SLD) from a maintenance overhead into an asset. With careful planning and proper governance, the SLD will become the single version of the landscape truth.
- 3. Introduction & Overview Concepts Considerations Landscape Synchronisation Futures More detail Wrap-up What We’ll Cover …
- 4. SLD Concepts – What is it ? SLD is central repository for all SAP system landscape information Products and versions (e.g. SAP CRM V5.0 or SAP PI V7.1) Software components (e.g. SAP Basis 7.0 or SAP ABA 7.0) Software units (for example CRM Java or CRM Server) Landscape definition (a description of the Australia Post SAP landscape and systems) Name reservation (unique definitions of objects created by Australia Post)
- 5. SLD Concepts - How is it updated ? Manually, using the SLD browser screen http://<host>:<port>/SLD Automatically (RZ70, Java data supplier, SAPOSCOL, SLDREG) Automatically by SAP from the Service Marketplace Using the SAP transport mechanism (enhanced CTS) Export / Import (full or delta) Support packages, enhancement packs, CIM maintenance or upgrades SLD bridge, auto forwarding, uni and bi directional synchronisation Note 7.1 to 7.0 limitation
- 6. SLD Concepts - How is it used ? Application Usage Process Integration Business system names for receiver determination Business system mapping rules Product and software component names and versions End to end monitoring definitions Adapter configuration cache Development Infrastructure Object name reservation Storage of development configuration Product and software component names and versions Web Dynpro To resolve adaptive RFC and Web Service calls Solution Manager End to end root cause analysis (remote administration) Landscape reporting Adaptive Computing Landscape data for stopping and starting systems
- 7. SLD Concepts – If it’s not available ? Application Effects of unavailable SLD Process Integration Unable to start PI Cannot create PI development objects Unable to refresh PI caches (old system definitions used) No end to end monitoring possible Development Infrastructure Unable to log onto DI No development namespace reservation available Web Dynpro Unable to resolve Web Services and RFC connections (application error) Solution Manager No end to end root cause analysis available No central administration of systems possible No discovery of new systems in the landscape Adaptive Computing No central stopping and starting of systems possible
- 8. SLD Considerations – Local drivers ? The more SLD’s you have, the harder maintenance becomes Think about geographic, audit, legal and organisational issues Consider security and firewall issues Are you outsourced – skill may be an issue. How complex is your landscape Are you going to upgrade to 7.1 soon? Do you have resources to change and test changes to the SLD now? Best practice is to have at least 2 SLD’s (design time and run rime) Motivation for SLD strategy (support costs, central tools, high availability) Solution Manager SMSY, ST06n, DBACOCKPIT, Wily It will come down to availability, performance, flexibility and cost.
- 9. SLD Considerations – Where to run it ? PI has the most reliance on the SLD PI has no performance issues and is on most scalable infrastructure PI has the best HA and DR design in the Australia Post landscape PI is a dual stack which always comes with an SLD The PI system is already at NetWeaver version 7.1 (many benefits for 7.1) PI approach is currently best practice as defined the SLD planning guide This may change once CE becomes mainstream This may change as Solution Manager evolves
- 10. SLD Landscape – AusPost view DEV TST R/3 BI EP/KM R/3 BI EP/KM PRD R/3 BI EP/KM PI PI PI CRM CRM CRM SCM SCM SCM PRJ DEV PRJ TST R/3 BI EP/KM R/3 BI EP/KM PI PI CRM CRM SCM SCM Solution Manager Solution Manager NWDI NWDI MI MI SRM SRM MI SRM GRC GRC
- 11. SLD Landscape – System Groups CRM BI SRM SCM EP/KM ERP MI DEVELOPMENT PI & SLD CRM BI SRM SCM EP/KM ERP MI PRODUCTION PI & SLD NWDI Non-Production (Design Time) Production (Run Time) Solution Manager & SLD OTHER PI & SLD CRM BI SRM SCM EP/KM ERP MI Administration Other Solution Manager Development
- 12. SLD Landscape - Design Time Development PI & SLD NWDI MI MI MI SCM SCM SCM SRM SRM SRM CRM CRM CRM EP/KM EP/KM EP/KM ERP ERP ERP BI BI BI PI PI SLDREG SLDREG Development
- 13. SLD Landscape - Run Time Production PI & SLD MI SCM SRM CRM EP/KM ERP BI Production
- 14. SLD Landscape - Other groups Sandpit PI & SLD NWDI MI SCM SRM CRM EP/KM ERP BI PI Volume PI & SLD MI SCM SRM CRM EP/KM ERP BI PI Solution Manager & SLD Sandpit Volume Test Administration
- 15. SLD Synchronisation Design Time Run Time Volume Sandpit Administration Bridge CTS+ Automatic Synch. Uni Directional Export/Import Bridge Bridge
- 16. SLD futures – What Improvements ? SLD performance reporting and error detection High Availability for Design Time SLD Deciding if NetWeaver CE has a role to play at AusPost Effects of restoring a non PI system on the SLD Future Solution Manager requirements Impact of upgrading PI production Impact of enhancement packs on SLD Importance of regular CIM maintenance Taking care during system refreshes
- 17. More Details – Important Links Link Document sdn.sap.com/irj/snd/nw-sld SLD Planning Guide SLD Post-Installation Guide SLD User Manual Configuring, Working with and Administering SLD Registration of Third-Party Systems in the SLD service.sap.com/installnw70 Master Guide – SAP NetWeaver
- 18. More Details – Important Notes SAP Note Number Title 935474 Grouping SLD instances 936318 Splitting an SLD instance 935245 Importance of “Object Server” SLD parameter 720717 Reducing the number of System Landscape Directories 954820 Compatibility of SLD in the system landscape 764393 Configuration of the SAP System Landscape Directory 669669 Updating the SAP Component Repository 1148028 SLD Planning 825116 Clustered SLD 1101564 SMSY reading third party products from the SLD
- 19. Bonus information Create individual SLD landscapes to group systems together (e.g. Sandpit) landscapes -> new landscape (from SLD main screen) The SLD bridge will report messages if different CIM levels are used administration -> logs (from SLD main screen) Regularly clean up old systems administration -> automatically updated data (from SLD main screen) To check the SLD in Solution Manager use transaction SMSY_SETUP To change RZ70 default system transfer settings -> menu -> expert settings To check SLD user settings use transaction SLDAPICUST To check SLD connectivity use transaction SLDCHECK To add a new SLD server, use transaction LCRSERVADDR
- 20. 3 Key Points to Take Home Highest system in the landscape owns SLD Separate SLD for Solution Manger One design time, one run time, one SolMan
- 21. Your local requirements are different to mine Central SLD is key to SolMan, ST06n, DBACOCKPIT and E2E RCA Make sure your systems are registered properly in SMP SLD should be on 7.1 system CTS+ nice and easy Learn the bridge Conclusion
- 22. QUESTIONS? How to contact me: Tony de Thomasis [email_address]