Central SLD vs SLD for each XI instance

[deidre_logan]

We are starting our SAP XI project. We are on XI 3.0 sp 9. We are trying to make a decision on which of the SLD configurations is the best for our company. We will have 3 SAP XI systems (dev, qa and Prd) should each have an SLD or should their be a central SLD? What is working for people currently in production? What are lessons learned? Thanks

[Former Member]

Hi,

We do not have yet implemented production XI environment but as SAP IT consultant, I am thinking about system architecture design based on SAP NetWeaver platform.

So I would say for good performance, it will be better that each XI connect to its own SLD system but for system landscape maintenance I would advise to have a central SLD only if each XI systems (dev, qa and prod) communicates with the same system landscape.

You also have to think about XI object transport from dev to qa and prod...as XI design and configuration objects are based on SLD model (business system, software components) you should have the same SLD

in each environment...so in that case a central SLD could be a good option but you could also imagine as an alternative solution an SLD model replication strategy between each SLD systems

But we still have the question of SLD maintenance security and I really do not think that it is a good idea for dev purposes to allow changes in a central SLD used by an XI production system !!!

The last point is that in some NetWeaver scenario SLD is not only used by XI but also by EP - WebDynpro with JCo connection for instance - so if you would want to use other NetWeaver components I would say to have a standalone SLD system for security reason and shared efficiency.

So you should have at least two SLD systems (one for dev/qa and one for prod) but we could imagine the following architecture :

1- XI dev with its own built in SLD system which one has an SLD namespace for dev purposes (dev_namespace) as a sand box and an other namespace (rep_namespace) which is the replication of the prod landscape (prod_namespace)

2- XI qa with its own built in SLD system with only one SLD namespace (qa_namespace) as a copy of rep_namespace

3- a standalone SLD system with one namespace (prod_namespace) to share it with other NetWeaver components without the risk to break down connection in case of XI prod problems.

XI prod points to this standalone SLD

4- if you are not using others NetWeaver components, a standalone SLD for production is not useful and then production SLD is in the production XI system itself.

So that my first feeling...but still open for discussion on that important point of system architecture design.

I hope it helps you a bit to have a decision.

Greetings

Nicolas

[Former Member]

Hi Deidre,

We have a similar environment and currently have still not decided what exactly we are going to do. One option we are thinking about implementing (and what the basis team is strongly favouring) is to have one common SLD for the Dev and QA systems, and another for the Prod.

Regards

Manish