How to Reconfigure SLD from Central to Local

June/July 2010 On NetWeaver®

How to Reconfigure a Central SLD to Local SLD
By Bijay Shrestha

Editor's Note: At some point in your SAP career, chances are you’re going to have reconfigure
your System Landscape Directory (SLD) from a Central SLD to a Local SLD in a complex
NetWeaver landscape. The question is, do you know how to do this or has that knowledge base
disappeared from your organization? If you’re left holding the bag, fear not; this step by step
article by is a perfect primer for anyone who is familiar with SLD, and is looking to make this
process easier.

Overview
As we all know, nothing is permanent in this world. When it comes to the IT world, it’s even more
accurate to say that everything we do today is permanent only for today, because technology
changes so fast that nothing can keep up with it. Similarly, what we configure today with the
given set of parameters/variables needs to be reconfigured after some time because of the
changes in one or more of many parameters/variables, which could be either business
requirements or technical requirements; e.g., upgrades.
®
SAP Landscape is becoming more complex than
ever after the introduction of SAP NetWeaver and
SAP® Landscape is becoming
with all the new and old components in existence.
In this article, I’ll not talk about what SLD (System
more complex than ever after the
Landscape Directory) is and how to do an initial introduction of SAP NetWeaver
configuration of SLD. For initial configuration, one and with all the new and old
can read the SAP publications, “SLD Planning components in existence.
Guide” and the “SLD Post Installation Guide for
NetWeaver 7.0”, which is a very good document.

Today when a NetWeaver/Basis Architect installs NetWeaver or any other SAP IT scenarios, he
or she will almost always have to configure SLD during the installation process. In the initial
installation of SAPinst GUI, there are two options for SLD configuration: (1) integrate an existing
central SLD server or (2) create a new local SLD server for that instance. See Figure 1.
.

Copyright © 2010 by Klee Associates, Inc.
www.ERPtips.com


Figure 1: SAP Installation Screen for SLD Configuration

Now, if the Company already has some SAP Landscape running and SLD strategy is in place,
then it’s easy to make the decision. The best practice is to integrate into existing central SLD.
However, if you are in a new implementation project where no prior SAP landscape exists and no
strategies are in place yet, especially around SLD, most probably you will just pick one option
using your best guess. In new implementation projects, normally everyone is working under
heavy pressure of time and resources, so lots of things are done in a hurry and there’s always a
lot to clean up after Go-Live when all the consultants are gone. Knowledge transfers are done in
a hurry too, with a lot for an employee to chew in very short time. Then after some time, when
problems arise, there’s a gap in the knowledge needed to troubleshoot and resolve the problem.
This article will help switch the SLD configuration from central SLD to local SLD or vice versa.

For example, one typical scenario is: in one of my projects, one of the Basis Administrators used
central SLD that was part of the Solution Manager instance. Initially it was just Solution Manager
and ECC installed in the landscape. Then as the project started moving to another phase, the
Portal, Business Intelligence was added into the landscape. Initially the portal contents were very
basic; the company later added ESS, BI reports, etc. Until ESS came into play, the SLD was
used very minimally. If Solution Manager/SLD went down, no one even noticed.

ESS and MSS applications are heavily dependent on SLD. One day, Basis shut down Solution
Manager for maintenance purpose, and the ESS got choked. Everybody got panicked because
the ESS application was giving all kind of errors. Therefore the best practice is to have one
dedicated central SLD server. If you are in a very large company where you have distributed
systems by regions, e.g., North America and Europe, you might want to consider distributed SLD.
This article will also help to reconfigure the SLD consolidation project from distributed to single
SLD server or vice versa.

For best SLD strategy, please check the SAP guide “Using System Landscape Directory in
Integrative Applications” and a few other documents on SLD.

In the example for this article, I first choose to integrate with existing central SLD during my
installation of the NetWeaver suite. At this stage we are setting up only the Development
Landscape. No Production instance has been added into the Landscape yet.

Copyright © 2010 by Klee Associates, Inc. www.ERPtips.com Page 2


In this example, I have both Solution Manager (SM1) and NW1 installed on the same server.
However, for less confusion, I’ll call them “Server_1” for Solution Manager (SM1) and “Server_2”
for NW1. In the Production Landscape, the best practice is to set up SLD in a single server.

The portal applications (e.g., ESS and MSS) are configured in a dual stack of ECC instance
“NW1” in server_2. Web Dynpro applications in portal will not work without SLD configuration. In
the initial installation of the Portal, I chose to use central SLD in SM1; later I decoupled from the
central SLD and reconfigured to run on a local SLD server for NW Portal.

As I have mentioned above, as well as being the best practice for a large and complex
NetWeaver landscape, a separate central SLD server just by itself is recommended.

In this current scenario, if one has to shutdown SM1 for any reason, the portal Web Dynpro
applications, e.g., ESS and MSS, will fail because of SLD server unavailability. Please refer to
the SAP guide “Post Installation Guide – System Installation Guide”. That guide talks about all
the possible different SLD architectures, e.g., single central SLD server, Distributed SLD servers,
etc. If multiple SLD servers are in existence, then there should be a strategy in place to
synchronize all the SLD servers.

In a nutshell, we will first configure SLD in the new server and then turn off the old SLD. You
cannot turn off the old SLD until the new one is fully configured and functional.

Here are the steps to decouple ESS and MSS applications from central SLD in SM1 and integrate
to local SLD in SAP Portal. This procedure could be used to change the configuration from a
central SLD system to local SLD servers or vice versa.

Solution:
1. First of all create an ID in NW1 ABAP client "001" with j2ee_admin and SLD admin role so
that you can login into new SLD (NW1 local).
2. Go to new URL http://server_2:port/sld and log in. The port is normally 50000 by default, but
in this example the port is 50200.
3. Configure SLD as if it were a new SLD installation.
a. Go to the Administration page and Stop Server.
b. Click on Profile link:
i. Choose Data Supplier from dropdown and update with correct Gateway Host
(Server_2) and Service (sapgw00).
ii. Then Server Settings  server name (Server_2).
c. Go back to the Administration Page and Start Server.
d. Click on link "Import" under Content on the right side of the screen.



Fill in "C:usrsapEC1SYSglobalsldmodelCR_Content.zip" in the Selected File field
and click on the Import button. It'll take a while until it successfully imports all the
objects. See Figure 2.

Figure 2: SLD CIM Import

4. Login into Visual Admin and go to Cluster  J2E  Server  Services  SLD Data
Supplier.

In the Runtime tab page, select HTTP Settings tab. See Figure 3.

Figure 3: SLD Data Supplier Setup in Visual Administration

Fill in Server_2 port (in this example port is 50200 instead of 50000), SLD user ID and
password, then click on “test connection” button. It’s highly recommended to use
“Slddsuser” ID, but if you use a different ID, make sure it is in the Admin group and has
the correct SLD Admin role.

If the connection test is successful, you can now move to NW1 ABAP

5. Go to Tcode RZ70, fill in the SLD bridge host name and Gateway service, and test the
connection. See Figure 4.



If the connection is successful, then go back to new SLD Home page
“http://server_2:port/sld”.

Figure 4: SLD Bridge Configuration in ABAP Side

6. Go to Technical Systems and you'll be able to see NW1 system in both ABAP and Java
system drop downs.
7. Login into Portal. Because of the SLD change, the JCo connection has been disabled too.
Therefore we need to go to the Web Dynpro console and create all those ESS related JCo
connections and test them. See Figure 5.

Figure 5: Maintain JCo Connection in Portal

8. You can now shut down SLD in “Server_1”.
9 SLD configuration is now complete.

I hope this article was helpful to reconfigure the SLD in your NetWeaver Portal and redirect from
SLD in server_1 to SLD in Server_2. It could be from central SLD to local SLD or vice versa.



Bijay Shrestha is an experienced SAP Tech and Solution Architect. He has over 22
years of business management and technical consulting experience, including12 years
of SAP, with multiple implementations under his belt with Fortune 500 companies. He
has worked as a freelance SAP consultant since 2005 and is President of SAPMANDO
Services, LLC. He has been a speaker at BITI ASUG Technology Forum. You may
contact the author at SAP.Authors@ERPtips.com. Be sure to mention the author’s
name and/or the article title.

The information in our publications and on our website is the copyrighted work of Klee Associates, Inc. and is owned by
Klee Associates, Inc.

NO WARRANTY: This documentation is delivered as is, and Klee Associates, Inc. makes no warranty as to its accuracy
or use. Any use of this documentation is at the risk of the user. Although we make every good faith effort to ensure
accuracy, this document may include technical or other inaccuracies or typographical errors. Klee Associates, Inc.
reserves the right to make changes without prior notice.

NO AFFILIATION: Klee Associates, Inc. and this publication are not affiliated with or endorsed by SAP AG. SAP AG
software referenced on this site is furnished under license agreements between SAP AG and its customers and can be
used only within the terms of such agreements. SAP AG and mySAP are registered trademarks of SAP AG.

All other company and product names used herein may be trademarks or registered trademarks of their respective
owners.


How to Reconfigure SLD from Central to Local

Recomendados

Recomendados

Mais conteúdo relacionado

Último

Último (20)

Destaque

Destaque (20)

How to Reconfigure SLD from Central to Local