Demo: The Full Automatic Sync Feature in the SLD of SAP NetWeaver 7.1
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.
How to Use the Demo:
This is quite easy: The demo runs as a self-contained exe file including a narration. To pause and restart the demo use the space bar or the menu bar of the demo. Apart from the system you’ll see very few slides also, which will introduce the demo scenario and its two parts.
To start the demo of SLD full automatic synchronization click here.
Hi Wolf,
Thanks for this excellent Demo as it helps to have a better understanding of SLD sync.
I have read different documentations about topology and pre requisites for SLD sync.
I was not able to find information about Data Suppliers.
What if I want to sync Solman from PI?
I cant find Synchronization in Solman 7.1.
Regards,
Adel
Dear Adel,
I guess you have already read "SLD Topology: How-To Gather and Distribute SLD-Data in Your IT-Landscape?"...
Information on data suppliers is available at the SAP Help Portal (Architecture Overview of the SLD Data Suppliers - SAP NetWeaver by Key Capability - SAP Library)
As for your question: SAP Solution Manager registers as any othe Dual-Stack system. I'm not too sure what you mean with syncing "SolMan from PI" - pleae refer to documentation of Process Integration.
I hope that helps...
Best Regards,
W. Hengevoss,
SAP SE
BTW: For a list of data suppliers and how to use them, see SAP Note 1869701.
Best regards, Steffi
Dear Wolf,
Yes I did. I just read it another time just to be sure to not miss any important point.
I have kept in mind the unique path principle.After reading again my question I can see that it is not very clear.
First of All, I am SAP Basis so, I am looking into SLD from Solman perspective.
Our Path is PI dev -> Qua ->Prod and then to Solman.
Regarding Data Suppliers: I wanted to say that I wasnt able to find information about what it is doing exactly and the difference with Synchronization (on SLD Administration -> Data Suppliers)
It seems very similar in term of settings but not sure if it works the same way.
Also, I wanted to Say that in Solman I cant find the same menu as in PI.
Maybe a screenshot will be better
So as for Solman and MOPZ, we need information up to date in SLD. That s why we need SLD from PI to be sync with Solman SLD.
I hope it is more clear.
PS: Thanks Stephanie for the note.
Regards,
Adel
Dear Adel,
the difference in the menus of your SAP Solution Manager SLD compared to the PI is that SLD version is very probably different. I'll ask Stephanie Daum, who already is in the thread to check, where to find the required information.
Best regards,
W. Hengevoss
SAP SE
Hi Adel,
The local SLD of SAP Solution Manager (on the Java stack) is actually the same as any remote SLD. But it is based on NW 7.02. So maybe you are a little confused if you are used to a later version. Menu and navigation to the systems via Administration etc. are slightly different.
An SLD can only serve as a source if it is based on a NW lower than 7.1. Since the local SLD in SolMan 7.1 is only NW 7.02, it cannot work as a target. So you cannot make the synchronization settings, here.
This is also indicated in the Planning Guide - System Landscape Directory (p. 20ff.), but maybe not clearly enough...
Does that help?
Best regards, Steffi
Hi Steffi,
Many thanks for your reply.
Yes it helps a lot. But it rises new questions. I have re read this part and honestly I still can t see about NW version.
If I understand it right, by configuring Data Supplier on Solman, it will be only to update another SLD and not receive data from PI (or other SLD).
If I configure a bi-directional bridge forwarding in PI Production, will it bypass this limitation?
Or if i present it differently, how can I make Solman SLD to communicate with PI?
Regards,
Adel
I asked my colleagues, there is a way to transport PI data to SolMan 7.1 via "PI carrier":
See SAP Note 1631346 - Solution Manager 7.1: SLD configuration for PI monitoring.
Can you check if this does help?
For troubleshooting, see the following sources:
In addition to what I just mentioned above, also see the Troubleshooting Wiki for PI Monitoring at PiMon_TroubleshootingGuide - Technical Operations - SCN Wiki.