SLD - determine critical applications

[Former Member]

Hi

We have a large environment with Java and ABAP system (R/3 Core, BW, XI, HR, ...) and currently one SLD running on the SSM host.

As we like to improve SLD availability, we first like to determine which of these servers are most critical and are candidates to get local SLD.

Surely our HR portal (uses a lot of webdynpros) will get one, but how can we determine impact to other servers if they can't access SLD for some hours or minutes.

What's the easiest way to analyze our environment for SLD requirements?

rgds Patrik

[Former Member]

Have you considered the possiblity to continue with one single SLD but in a real high-availability installation ?

From the document <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808">How To Handle the SLD for SAP XI</a>:

<i>We recommend that you use a single System Landscape Directory (SLD). The cost of

running the SLD infrastructure increases with the number of SLD instances. In particular,

adding a second SLD involves additional costs for synchronizing data between these two

instances. From a cost perspective, it is preferable to configure a single SLD.

The following factors can make a multiple-SLD architecture necessary:

• Legal constraints

• Company rules

• Network constraints (for example, firewalls, availability of resources)</i>

Regards,

Sandro