i have build Development server for SAP PI 7.3,with local SLD now we are in phase of building QA server.
my query is I have to create Local SLD for QA also? or i can join with Dev SLD?. i heard PI recommended local SLD
what is advice able for best landscape.
Thanks & Regards,
you can go with a local SLD for dev , qa and prod. This way you can connect systems from other landscapes like ECC , CRM to corresponding SLD's. Say a dev ecc systemt to Dev PI , and Q.A ECC to Q.A PI.
If you have a solution manager where all your systems are connected then you can also let PI feed the data to Solman.
The choice is yours. You can have one singluar SLD and hence one single SLD master for all your non-production systems and one production systems.
Or you can one common SLD for DEV/QA systems, one for pre-production and one for production (if you have 4 system landscape).
Or else have one for each of DEV,QA...PROD.
And while choice is urs you need a consider the business requirements when deciding as well.
I would suggest you a 3-tier SLD architecture in which all PI systems should have a local SLD, all non-production systems should point to non-production SLD and all production systems should point to production SLD. As a result you can avoid SPOF as you separated SLD for each environment.
Thank you all for your replay.
think is that we have a 2 dedicated server for SLD, Non-production and production.
all DEV and QA are routed to Non-production and PRD routed to production.vsersion of SLD is sap Netweaver 7.0 ehp1.
and we are running SAP PI on NetWeaver 7.3, and also we are planing to upgrade our SLD server from 7 to 7.3.
now in my environment we have 4 SLD is running 1 with solman. 2 SLD for ECC,BI and EP landscape this all are sap netweaver 7.0+ehp1 and 1 for PI DEV sap netweaver 7.3.
my question is , sap require local SLD for PI landscape? or can add QA to my other SLD server which is SAP netweaver 7.0+ehp1?
what is advantage of have single or multiple SLD ?.
thanks and Regards,
PI needs SLD for sure... local or remote I don't think that should be critical .However as it happened SAP came much earlier with higher releases of PI than other products and the recommendation is that the SLD master must be the highest hence PI ended up local SLD.
I believe with SOLMAN 7.1 in landscape the requirement for highest release too act asSLD master goes out of window.
In your case you can have PI 7.3 still as SLD master or have the dedicated 7.3 SLD master. In the later case SLD migraition wiill be needed for missing systems
For PI systems SLD is important as it gets business data from it. So, you should design SLD landscape in such a way that you should not create any single point of failure. So, if PI has its own local SLD and if your production/non-production SLD is down. so, it would not impact PI systems.
Good point and od like to add is that SLD itself can be made a part of HA. To do this either make the primary application sever designated to run SLD as part of HA (i.e like ASCS/SCS instance) however this approach is not documented though I have implemented it.
However the approach I think is more suitable,documented and defintely supported is using SAP Web dispatcher. Nor NW 7.3 PI please check OSS note 1614690
Following SLD planning guide has very good information how to plan SLD architecture:
Chapter 188.8.131.52 has very simple overall recommendation for SLD architecture. Such landscape is easy to maintain, it is fairly straightforward to adopt and such configuration is easy to understand.
I my opinion, if you want to have design-time sld, qa sld and runtime sld it is also fine when you want to a) validate sld transports b) test sld transport mechanisms before production c) isolate development and test sld from each other.
Chapter 3.4.3 Where to Run SLD in Your System Landscape has some points for your question.
I recommend: keep it simple!