about SLD configuration
Both of our EP and PI system had installed a local SLD, and both of them need connect to ERP.
But in ERP, the SLD configuratoin can only link to one SLD system , it cann't link to 2 SLD systems at the same time .
As we know, RFC destination SAPSLDAPI , transaction RZ70, can only set to one system;transaction SLDAPICUST must set 1 master system.
Is there a solution to make ERP link to EP SLD and PI SLD at the same time ?
Or the other solution to solve the problem EP and PI need to link to ERP at the same time ?
Thank you !
Gary Jackson replied
There may be situations where you need more than one SLD in your system landscape. SAP recommend that you build and maintain a runtime SLD (perhaps located on your production PI system) and a design time SLD (perhaps located in your development PI system), so that the production SLD was not exposed to development changes, for example.
As data suppliers, all systems in your landscape would supply their landscape information (ABAP stack via RZ70; Java stack via SLD Data Supplier service) to the runtime SLD. So that developers could have visibility of the whole landscape, the runtime SLD can be set to automatically forward its technical landscape information to the design time SLD, in what is known as SLD synchronisation.
In addition to the runtime and design time SLD, you can also manage local SLDs. You may need to do this for a Java application that uses WebDynpro JCO connections and you don't want these to be reliant on the runtime SLD. This local SLD could also be set to automatically receive technical landscape data from the runtime SLD. In this case, the Java application becomes a client of its local SLD (for the JCO connections) but a data supplier to the runtime SLD.
Take a look at the [System Landscape Directory Planning Guide|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0a1a8fb-0527-2a10-f781-8b67eab16582] for a good detailed discussion on SLD topology.