In this weblog, you will get an overview of the documentation that is required to set up a system landscape directory (SLD) in your landscape.
The system landscape directory is part of the AS Java usage type of SAP NetWeaver. So, you do not have to install additional software to bring SLD into operation. Instead, you could set it up potentially in every SAP NetWeaver AS Java system in your landscape by performing a few configuration steps.
Although this sounds quite straight-forward, I received some requests in the last months - both from colleagues and from customers - concerning the implementation documentation required to set up the SLD. As we always stress how easy it is to set up SLD, these requests irritated me initially. Then, I gave it a second thought and realized that we really DO offer several guides without clearly stating what they are good for and in what order one should read these guides. So, in this blog, I hope to be able to provide a short overview of the documentation involved.
To start with a positive statement: I still believe that setting up SLD is easy :-)! You can find all guides described here in SAP Service Marketplace at http://service.sap.com/sld --> Media Library.
Step 1: Planning
If you do not have SLD in your landscape yet and try to get an overview of relevant aspects or want to extend your SLD landscape, start by reading the Planning Guide - System Landscape Directory. It provides you with a central starting point for the planning of your landscape strategy for the system landscape directory of SAP NetWeaver. So, this documentation helps you to decide how many system landscape directories you require + how and where to run them in your landscape.
Step 2a: Setting Up SLD in an SAP NetWeaver 7.0 System
If you want to run the system landscape directory on a new AS Java 7.0 system, use the installation guide for your application, release, operating system, and database (installation documentation is available in SAP Service Marketplace).
The good news: As of SAP NetWeaver 7.0, the configuration of the system landscape directory is already included in the standard implementation process. As a result, you will have a running SLD after the installation, if you performed the corresponding configuration steps part of the implementation procedure. So, no additional documentation would be required in that case.
If you want to run the system landscape directory on an existing system with usage type AS Java, use the Post-Installation Guide - System Landscape Directory for SAP NetWeaver 7.0. There are only five steps that you have to perform on an existing system to bring SLD into operation.
Step Step 2b: Setting Up SLD in an SAP NetWeaver 2004 System
For SAP NetWeaver 2004, you will require the Post-Installation Guide - System Landscape Directory for SAP NetWeaver 2004 in any case (that is, both to set up SLD in an existing system or in a system to be installed). Nevertheless, there are also only five steps that you have to perform after the installation to bring the SLD server into operation. In addition, there is a getting started check list for SAP NetWeaver 2004 that provides an overview of the required steps to configure the system landscape directory. For newer releases, this checklist is contained in the post-installation guide, so you won’t find such a separate document for SAP NetWeaver 7.0 and higher.
Summary
Altogether, you either require no additional guide (for the activation of SLD on an SAP NetWeaver 7.0 system you are going to install), one additional guide (the Post-Installation Guide - System Landscape Directory for SAP NetWeaver 7.0 if you want to activate SLD on an existing AS Java 7.0 system) or two additional guides (the Post-Installation Guide - System Landscape Directory for SAP NetWeaver 2004 and optionally the corresponding getting started check list). In any case, the steps you have to perform won’t take long.
On the media library page in SAP Service Marketplace, you will also find the user manual of SLD. This guide is just a PDF version of the SLD documentation you can also find in the SAP Library.
2 Comments
