Local sld pull from central sld

We are in the process of configuring a brand new sp19 solution manager server. We have a central sld on a dedicated server with several systems already registered on it  I created a local sld on the new solution manager server. I want to pull the systems from this central sld server into the solution manager server, but cant' seem to find any documentation on how to do it.
I've read the SLD planning guide, the sld post-installation guide,, and the sld user guide. If there are any steps that document how to do this, I've missed them.
Can anybody help?
--Carl

On your central SLD: Administration -> Data Suppliers -> Add SLD...
Type in URL, valid user and pass and that should be it. It works this way on SLD based on NW70.

Similar Messages

  • SRM SWCV not geting synched up in CMS from Central SLD

    Hi,
    We set up SRM SWCV in Central SLD and using that in Dev system.
    We want to transport this SWCV from Dev to QA using CMS.When we are trying to do this transport we are getting error and the reason is there is no entry of SRM stuff in CMS.
    Our CMS is pointing to Central SLD and when we are trying to Update CMS it is pulling all other SWCV s from Central SLD except SRM stuff..So we couldn't add SRM SWCV in CMS...
    So,please let us know what we are doing wrong...or Should we approach differently to load SRM content in QA systems..
    Thanks in advance
    Venu

    Yes Venu,
    You need to import SRM Content into QA syste.
    DO NOT TRANSPORT CONTENTS....!
    Thanks

  • Migrate local SLDs to a centralized SLD

    We are in a big SAP project with one full landscape for each new SAP product (e.g. SRM, ECC, EP, BI, etc.)
    We have a centralized SLD on a SM7.0.
    We have 2 options when installing each system:
    1) use the centralized SLD for each new install
    2) use the local SLD for each new install, then change all local SLDs to the centralized SLD.
    What will be the pros and cons of each option?
    Thanks!

    Hello Linda,
    Eventually ,you want to register your systems to the central SLD.
    You can do it in both ways,but during installation when you select the option of Configure a Local SLD SAPinst says that it will take longer time ,thats it no other issues.
    So best is that you register your systems to Cenral/Remote SLD.The remote SLD should be running and available at that time.
    Have a look at this blog /people/boris.zarske/blog/2008/03/21/sld-general-recommendation-how-to-set-up-the-system-landscape-directory , it will give you more wider view of planning the SLD.
    Regards
    Ajay

  • Switching from central SLD to local SLD

    Hello,
    i have installed BI Java with central sld.
    Could I switch back from cetral sld to local sld?
    I didn't find any documentation or posts.
    Thanks,
    Sabrina

    Hi,
    Yes you can change the SLD configuration from  local to central  or a vice versa...
    Please check the following SAP Note for your reference
    Note 720717 - Reduce the number of System Landscape Directories (SLD)
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/29b1f3ea-0c01-0010-2dae-cc64bb381c97
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e5e7cc9b-0501-0010-adb2-ffbe7f1f7e6f
    Hope this helps,
    Regards
    CSM Reddy

  • Local SLD and Central SLD

    Hi,
    Can we still change Local SLD to Central SLD after the installation has been done?
    Rgds,
    Hapizorr Rozi Alias

    Hello Rozi/Naveen,
    Yes u can change the SLD configuration from central to local or a vice versa...
    Please check the following SAP Note for u r ready reference
    Note 720717 - Reduce the number of System Landscape Directories (SLD)
    If usefull then give  reward point..
    Thanks

  • Best Recommendation to link Central SLD to LMDB

    hi
    What is your suggestion to connect central SLD on SAP Netweaver to LMDB on Solution Manager 7.1 ?
    Q1.
    I can think of 2 options:
    1) Central SLD (NW) > Local SLD (SM7.1) > LMDB
    2) Central SLD (NW) > LMDB 
    Is it necessary to configure a local SLD on solution manager 7.1 and pull data from the central sld (NW) to syn to the LMDB?
    Or can we direct syn from central SLD to LMDB?
    What are the pro and cons for the 2 options?
    Q2.
    During the setup of the solution manager, it is required to choose an option of the SLD Destination
    1) Register in existing central SLD
    2) Configure a local SLD
    I realise both questions are somehow link and can affect my setup.
    For instance:
    if i decided for (Central SLD (NW) > Local SLD (SM7.1) > LMDB) , i will need to choose Configure a local SLD
    If i decided for (Central SLD (NW) > LMDB), i will choose Register in existing central SLD.
    So which is  better decision? Secondly, SAP recommended to configure a local SLD. Can i configure and not used it if i happened to go for Central SLD (NW) > LMDB? SInce no local SLD is required.
    Pls advise. Thanks in advance
    Regards
    Gary

    Hello Gary,
    The right option is
    2) Central SLD (NW) > LMDB
    Is it necessary to configure a local SLD on solution manager 7.1 and pull data from the central sld (NW) to syn to the LMDB?
    No, it is not necessary. Solution Manager's LMDB needs to be fed with a SLD, local or not.
    Or can we direct sync from central SLD to LMDB?
    Yes, you can.
    What are the pro and cons for the 2 options?
    There aren't really pros and cons. It's up to you to maintain a SLD centrally outside Solman or a local SLD in the Solution Manager.
    Regarding your Q2, please make sure you are not refeering to Solution Manager 7.0 EHP1 recommendations, because the documentation for EHP1 in fact recommends a local SLD.
    For configuration options and examples, check the [Setup Guide Landscape Management Database|https://websmp109.sap-ag.de/%7Esapidb/011000358700000551222011E.URL]. Also there's a Wiki topic article: http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=250514114
    I will leave the official recommendation part to another contribuitor to share thoughts in this topic. Meanwhile may you please point out where did you see such recommendation?
    Regards
    Guilherme
    Edited by: Guilherme Balbinot on Sep 30, 2011 11:40 AM

  • Central SLD Configuration

    Dears,
    Recently we installed PI DEV and PI QAS server.At time of configuration we choose local SLD option for configuration.
    But now we are getting requirement to configure central SLD.
    So please confirm which strategy is good between them and if it is central SLD,Please suggest the
    procedure to change local SLD configuration to central SLD.
    Shivam

    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

  • Central SLD

    I try to import SW Component Version into Repository from Central SLD, System gives me the messagebelow:
    <b>Unable to read software component versions from System Landscape Directory "brckxiprd.internal.borusan.com:50000"</b>
    What must I do to fix this problem?
    thanks.

    hello cemil,
    Check out these note :
    Note 720198 - Integration Repository cannot access SLD
    Note 836093 - IFR: Updating the application components => error
    It may help you out....
    regards
    Prasad

  • Unable to import the SWCV fom the central sld ?

    Hi Guys,
    I have connfigured xi for central sld
    and when i try to import the swcv from central sld i am getting the message as unable to read the data from the <hostname> : port number
    I have given the following in the exchange profile
    com.sap.aii.connect.cr.name -- central sld host name
    com.sap.aii.connect.directory.name -- sap xi host name
    can anybody tell me the values for the above parameters and any help would be really appreciated
    LCRSAPRFC and SAPSLDAPI are on the xi server and works fine.
    Thanks,
    Srini

    Hi Sridhar,
    LCRSAPRFC - poinitng to SAP XI server Gatewayhost and Gateway service -- works fine
    SAPSLDAPI - pointing to SOLMANGR Gatewayhost and Gateway service -- works fine
    I am maintaining the Hostname of the solmagr in SLDAPICUST. can you explain little bit more on the url in sldapicust.
    Do you mean i need to give http://hostname:port/sld instaed of just the host name ?
    Thanks,
    Srini

  • Switching from local to central SLD

    I installed the ESS business package with a local SLD. Now there is another SLD server we need to use (a central SLD instance). Can we switch easily from an existing local SLD instance to a remote SLD instance?
    Tiberiu

    Hi Tiberiu,
    It's a while since this message was created. Have you solved your problem? I have our SLD's set slightly differently to the suggestion made earlier, although I would say that I'm an expert in this area. For dual stacks I have the CIM.... tab pointing at itself and the HTTP tab pointing at the central SLD. This seems to work for us in all cases where there is a dual stack. We are having a few issues in java only systems which we are trying to solve. At present both tabs point to the central SLD and "seem" to be working!!
    Regards,
    Paul

  • Migration of local SLD to Central SLD on different host.

    Hello Experts,
    We have migrate the local SLD existing on the SAP PI System to a new Central SLD on a different host on SAP Solution Manager system.
    I followed the OSS Note 720717, which contains the description of the changes that have to be exectued in the SAP XI/PI Environment, during the SLD Migration. This note does not give any details of the description of changes for the other SAP Systems such as SAP ECC, BI etc registered in the SLD.
    Can anyone provide the OSS Notes, SAP Doc URL or the steps on how to migrate the local SLD existing on SAP XI/PI System to the new Central SLD on the SAP Solution Manager system.
    Thanks for help in advance.
    Best Regards,
    Haleem

    Firstly
    I recommend to avoid having 1 SLD for multiple clients - like Solution Manager, BI, ECC
    This is because clients may end up having conflicting requirements for the same SLD
    - for example the small user group for Solution Manager may have a flexible and easy going policy on J2EE downtime
    - but if you take down the Solution Manager J2EE that houses the SLD and PI uses this SLD - then you could have a severe affect on PI useage
    Secondly
    Although you can migrate content - this still does not guarantee the target landscape will work
    - you may still need to manually re-implement target landscape configuration
    let me give you an example
    SLD 1 is being moved to SLD 2
    Portal 1 is pointing to SLD 1
    Even if you migrate the content of SLD 1 - including the ECC and Portal technical system landscape information
    Portal 1 is still pointing to SLD 1 - this then needs to be manually re-pointed to SLD2
    and that might not be all the complete steps either !
    The complete steps of migration from the client side may not be available  (I have found only steps to
    migrate SLD content not migrate client use of the SLD)
    - they may only be available as the documentation for the original configuration steps required to step SLD and the client
    - therefore when migrating SLD you must go through the client setup documentation for SLD and check your
    target landscape is consistent
    Lastly - other considerations include
    Lets say you also export model and CIM content from SLD 1 to SLD 2 - this means SLD 2 has an import line from SLD 1
    - if you decomission SLD1 then you need to switch the import line which is not recommended - this could cause severe problems and may require you to create a new import line to upload content from SAP /swdc (which you need to keep the SLD bug free and latest definitions)
    Just a few thoughts on issues you may encounter
    Best wishes
    Stuart

  • Local SLD not updating a central SLD

    Hi,
    In my company landscape, I have
    SolMan7.1 with Central SLD (Let's call this SLDA)
    Portal 7.02 with local SLD (Let's call this SLDB)
    ECC6
    Both the Portal and ECC systems are updating SLDB, so I can see both technical systems in SLDB.
    SolMan is updating SLDA, so I can see SolMan technical system in SLDA.
    I linked SLDB to SLDA via
    From SLDB> administration> data suppliers --> add SLDA
    For this setting, I use the user SLDDSUSER, which have a role LcrInstanceWriterAll.
    The problem now is SLDA does not get the data from SLDB. In SLDA, I see only the SolMan Technical System.
    How often does SLDB update SLDA? Can we manually trigger an update SLDB->SDLA?
    How can we troubleshoot the SLDB -> SLDA update?
    What else needs to be configured other than "From SLDB> administration> data suppliers --> add SLDA" ?
    Thanks
    Edited by: Nick Foo on Sep 27, 2011 3:53 AM

    Hi Sunny,
    yes I have done those steps. Very short and easy setup steps to link to another SLD.
    OK, just one thing to confirm here.
    After Add SLD, the SLD URL syntax should be           http://host:port   correct?
    I have tried all sorts of entires for the URL
    http://host:port
    http://host:port/sld
    http://host:port/
    All not working
    Checked the user, user is ok, even tried giving the user Administrator role and still not working

  • Moving Central SLD from XI Development to XI Production ?

    Hi,
    Please advise what is the impact of changing Central SLD from XI Development to XI Production Server.
    Because during initial installation the XI production still not available so our Basis only install SLD in our XI development server and other SAP development like FI, BW also pointing to this SLD.
    now the XI production is ready. could i just install new SLD in production and changes all connection from
    dev to prod ?
    Please advise on the step that i have to do.
    Thank you and best Regards
    Fernand

    Hi,
    http://www.riyaz.net/blog/index.php/2008/05/28/xipi-step-by-step-guide-to-xi-transports-using-cms-part-i/
    http://www.riyaz.net/blog/index.php/2008/05/28/xipi-step-by-step-guide-to-xi-transports-using-cms-part-ii/
    http://www.riyaz.net/blog/index.php/2008/05/29/xipi-step-by-step-guide-to-xi-transports-using-cms-part-iii/
    Refer this article
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f85ff411-0d01-0010-0096-ba14e5db6306 
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b01876ac-abbb-2a10-788e-95a7c5a5aeca
    Regards,
    Suryanarayana

  • Central SLD/Local SLD

    Hello All,
    Is there limitation with central SLD over Local SLD?.
    To deploy Webdynpro applications (Mobile) please let me know if there are any limitations
    Thanks

    Hello.
    SLD architecture is a long discussion
    There are different views on how to set up SLD's.
    In my oppinion, the limitations of SLD is that it's a central component to a growing number of netweaver component.
    Right now, the portal, webdynpro, xi, nwdi wouldn't work very well without the SLD.
    Considering this there is aspects on how to set up the SLD's. Usually critical systems have a local SLD, with supplyer briges to central SLD's.
    You would have a separate SLD landscape for Production servers, since they usually run on different SLA (service level agreements).
    If you're using NWDI, it's usually a good place to have you're central SLD.
    If you're running a smaller landscape, go for the local SLD only and don't complicate your landscape too much.
    Check this document (about last slide) with different SLD scenarios. https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/204994f3-0e44-2a10-17b3-808fbd8db4aa
    Regards, Mikael Löwgren

  • Pointing to central SLD inplace of local SLD

    Hi ,
    I want to change point local SLD to central sld link in  http://hostname:50000/rep/start/index.jsp.
    Please advise me.
    Regards,
    Kirthi S

    Hi ,
    Thanks for replying.
    As per the note am trying to change the Aii parameters to central SLD in xchange profile but xiprofile is throwing a error
    http://10.232.255.56:50000/webdynpro/resources/sap.com/com.sap.xi.exprofui/XIProfileApp
    dbconnect.prop: failed to load properties file 
    Please help me on this.
    thanks
    Kirthi

Maybe you are looking for