With SAP NetWeaver 7.1 "full automatic synchronization" becomes available as a new feature of the System Landscape Directory (SLD). It allows setting up SLDs so that all their content is replicated from the source to the target SLD.
All SLD data is to be taken seriously: All landscape data (such as technical systems), all data from the software catalog (provided by SAP or added for NWDI-based development), all manually added data (such as the business systems), and even the CIM Model is sent. (Note that an SLD of SAP NetWeaver 7.0 based on SP Stack 12 and above can be used as the source system for unidirectional synchronization.)
This makes the full automatic sync a mighty tool to propagate and backup SLD data and reduces manual synchronization effort. However, the full synchronization also includes deletions so pick your strategy wisely when using this feature. One thing especially should be taken into account: You can set it up to work one way or in both directions when connecting two SLDs.
The Story:
As a prerequisite for this demonstration, we have two SLDs both running on SAP NetWeaver 7.1 - to learn where you can find this type of installation see
How to Get an SAP NetWeaver 7.1 System Landscape Directory? Just to have some data, in each SLD an SAP NetWeaver AS (one ABAP, one Java) is registered. Without the synchronization each application server is only known to the SLD its data supplier is connected to.
- In the first part of the demo full automatic synchronization is set up unidirectional: In this type of setup the target SLD gets all the data from the source SLD. This is shown by the technical systems data.
- In the second part of the demo a bidirectional setup replaces the unidirectional. It is demonstrated using the technical systems information and of newly created manual information - a business system and description.
Note that in this setup both SLDs are source SLD for each other really, when in both data is changed.
.
.
.
