Hi Shivam
The SLD planning guide provided previously is the key source to plan, implement and run an SLD landscape
However what it may not deal with specifically is changing an existing SLD landscape to accomodate a local PI specific
SLD and a new Central SLD for Solution Manager (or other purposes)
Some things to consider when selecting Sync options
1) 1 Dual purpose SLD is not recommended - a central SLD might have different administration requirements than a PI specific SLD
2) Where possible do not change established import or export lines in either SLD
3) Keep all SLDs involved in the sync at the same J2EE version, SP landscape and CIM model/content
As the PI SLD can be productive critical - full consideration has to be given to this SLD as you can
still maintain systems manually in a central SLD manually - or indeed in Solution Manager itself (both manually and automatically via RFC) - therefore I would recommend a unidirectional sync from local PI SLD to Central SLD of PI landscape data only - either manually or automatically or indeed explore any available options to have data suppliers update both SLDs (there was some options similiar to this in older SLD versions - but I am not completely familiar with the latest SLD builds)
I would not however encourage full sync or CIM based sync as there maybe established CIM import lines on either SLD nor would I specifically encourage the Central SLD to influence data on the Local existing PI SLD
Best wishes
Stuart
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.