Central SLD setup

Hi
We have a freshly installed landscape comprising of Solutiona Manager 4.0,EP 7.0,ECC 6.0,BI 7.0.(I am new to netweaver)
We need to setup a central SLD on the solution manager system.Also there is a requirement to monitor all system form the solution manager
NWA.
Currently when I log onto NWA the follwing error messages are shown
system Landscape Directory is not accessible!
Only Local system can be administered!
Could someone tell me the steps to setup the SLD(ie connect different systes),setup central NWA and some basic concepts.
As far as I understand SLD data supplier is used for communication between the j2ee engines.
so for eg: for a pure Java stack like EP is it enough to give the logon details of Solution manager in SLD Data supplier of Ep's Visual administrator..?
Please help.
thanks
rocky
P.S: will reward points for helpful answers.

Hai,
      It is better to mention the central SLD server details during the installation process in the phase,Registration in System Landscape Directory(central SLD,local SLD,no SLD)
We need to setup a central SLD on the solution manager system.Also there is a requirement to monitor all system form the solution manager
NWA.----
> Maintain the Central SLD as Solutionmanager system.Login into the other system and go to Visual Administrator(c:\usr\sap\SID\DVEBMGS<instno>\j2ee\admin\go.bat)->Server->Services->SLD Data Supplier-> In the tabRuntime, HTTP Settings->Give the host name of the Central SLD system(Solman),Port number, SLDDSUSER,and password and save the settings and then in the
CIM Client Generation Settings->Give the hostname of the Central SLD system,port number,SLDDSUSER and Password,save the settings and click on the CIMClient Test to check the CIM Test.
Once the CIMTest is successful,
Click on the button(Assign application roles to user groups) and also on the button (trigger datatransfer to System Landscape Directory(SLD)),this transfer the settings to the Central SLD system.
Thanks and Regards,

Similar Messages

  • PI 7.1 and central SLD

    Hello, colleagues.
    We have already central SLD based on SAP Solution Manager (SM+ERP systems). Now we plan to setup PI 7.1 (three-system configuration).
    Should we include PI-systems in the central SLD or organize second separate SLD for PI-systems?
    We have some doubts about it and cannot yet make right decision.
    Can we hear your suggestions of this matter?

    Hi,
    Personally I recommand to have at least two SLD for PI systems: one for PI prod, and another for PI non-prod (dev, Qua, Pre-prod). As your current SLD is linked to ERP, I presume it has a high criticity, so for me I think you can use it for your PI prod.
    Or you can have only one central SLD (yours) which populate the local SLD of each PI, by synchronization.
    with SLD, there are several choices, but keep in mind that for the SLD of PI prod, it should have a "hight" criticity. If its SLD is shut down, PI can work only during several minutes without SLD info... thanks to its SLD cache, but after that PI exchanges are down.
    Regards.
    Mickael

  • 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

  • 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

  • Connecting local SLD to central SLD

    Hi,
    I have a system with its local SLD, I want this system to connect to Solman's SLD.
    How is this possible?
    Regards
    KVR

    Hi,
    there are many considerations on SLD setup.
    you will have to decide which is central SLD?
    below document will give your clear idea abou integration
    http://help.sap.com/saphelp_nwpi71/helpdata/en/46/2f42f114bc59bde10000000a155369/content.htm
    Regards
    Nagaraju
    Edited by: welcomenag on Jan 22, 2010 5:17 PM

  • Need Suggestion on Central SLD System

    Hi Experts,
    I need a help/ suggestion on deciding the Central SLD system in our landscape. In our current SAP System landscape we do not have XI Servers for Central SLD, So we are using Solution Manager 7.01 as the Central SLD for the new Installations and including the old Systems too. But We came to know that SAP does not recommend using Solution Manager as the productive SLD System.
    So we have stopped the process of including old systems to Solution Manager now and we decided to build the system for central SLD which is recommended by SAP. So please suggest me which system is more recommended by SAP like EP/ ECC/ NW or any other.
    Thanks.

    Hello Ajay,
    you posted the question on wrong forum.
    This forum is for sap business one.
    Post your thread on appropriate forum to get the replies.
    *Close this thread.
    Thanks,
    Neetu

  • Pi 7.1 Central SLD

    I have installed PI 7.1 and will use it as central SLD. I am installing SCM 2007, ECC Oil and Gas and BI 7.0 and want to point these systems to the central SLD in PI system.
    During the install the WAS 7.0 system use SLDDSUSER however there is no user like this on PI 7.1.
    SCM 2007 install had as default SLDDSUSER but that user doesn't exist in the PI 7.1 install.
    I check SAP notes and can't find nay notes regading this change.
    I did find an account that is close to this SLD_DS_DS1 where DS1 is the SID.
    Has anyone ran into this issue with WAS 70 and WAS 71 installations? Is it safe to select SLD_DS_SID as the correct one for hooking in my other component systems into the Central SLD on PI 71?
    Thanks
    Mikie Brogan

    We have the same situation. Can you explain How?
    Thank you
    Raj GA

  • Not Updating in Central SLD

    Hello,
    Upon performing our daily system checks, one of the item is to monitor the sending of SLD data of the installed systems in the System Landscape to the Central SLD which in our case is the XI box. Four of our systems having Java stack did not update. With that, i performed the necessary steps to trigger it so that it'll update in both Web AS ABAP and Web AS Java. With regards to ABAP, i triggered and activated the system to collect and send SLD data via RZ70. As for the Java Systems, i triggered and activated it in the SLD Data Supplier in the visual admin. I performed the CIMOM test and it was a success. Furthermore, i've triggered the send SLD data. In order to check whether it worked or not, i've checked the respective local SLDs of the systems and viewed that it is updated there for both ABAP and JAVA. Furthermore, i've checked the system landscape and viewed the systems are updated for both ABAP and JAVA except for our APO system, both ABAP and JAVA as well. As another step, i reconfigured the Data supplier in the administration of the SLD of APO in order to make sure that the password of xisuper is correct or something. However, until now, it has yet to be updated.
    Hope you could help me.
    Thanks so much!

    Have you checked the Log on the receiving and sending SLDs to see of there is an error?

  • Adapter monitoring with central SLD!

    Hi ,
    we have central SLD in our landscape(different host from XI server),and our basis guys installed PI7.0 SP12.And AE is local as I can see under Integration server.
    I can see JPR in adapter in adapter monitoring.
    I have question here!
    should it needs to show all the list of adapters (FILE,JDBC,JMS,SOAP etc)in adapter monitoring in RWB?does it vary,if sld is central or local ?
    what is the ideal way.
    thank you,
    babu

    <i>where the adapter engine should appear in RWB under integration server or under non central adapter engine if we have installed central AE and central SLD?</i>
    Under Component monitoring -> Integration server -> Adapter Engine
    <i>and it has show all the adapters when we install central AE and with central SLD when we furthur click the show all adapters?</i>
    As i mentioned above, u may view all the adapters after clicking
    Adapter Engine -> Adapter Monitoring
    <i>or is it changed since PI 7.0 to cummunication channel monitoring and no adapter monitoring?</i>
    Yes. Now the monitoring of adapters r much intensively done by Communication Channel Monitoring
    Regards,
    Prateek

  • Access Central SLD Error

    Hi Experts,
    We are using the SLD SOLMAN and we and the ideia is to use it as Central SLD. In order to allowed PI indentifed the Central SLD we must appllied few oss notes like; 939592, 768148 and 720717, but much as we try it to import we got few errors as describe below:
    "Unable to read software component versions from System Landscape Directory "ASPTSSM01:50000"
    Another error occurs when trying to access the SLD by the runtime workbench:
    "Error during communication with System Landscape Directory: HTTP response code: 403 (Forbidden)"
    Anybody help-me.
    Regards,
    HMattos.

    Hi HMattos,
    I hope you have created the PI service users in SOLMAN and assigned the same password as the PI service user password.
    Open /rep on your PI and click SLD. Check if it opens the SOLMAN page.
    Check in VA if SLD data supplier test works fine.
    Check SLDCHECK transaction.
    If you get errors in any of these, the you will get a hint as to where is the issue. If you unable to resolve, then post the results of the above.
    Cheers....,
    Raghu.

  • 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

  • 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

  • How to link XI-Development to the central SLD on XI-Production?

    Hi,
    we have a two systems landscape with XI-DEV and XI-PROD.
    So far, we have used the SLD on XI-DEV.
    Now we want to use one central SLD that is running on XI-PROD for all developments on XI-DEV.
    What is necessary to to that (any documentation available?
    1. First we have done an export/import to copy all technical and business systems to the central SLD.
    2. Then we have set the following parameters in the exchange profile (Section Connections) of XI-DEV:
       com.sap.aii.connect.cr.name: Host of XI-PROD
       com.sap.aii.connect.cr.httpport: Port of XI-PROD
       com.sap.aii.connect.landscape.name: Host XI-PROD
       com.sap.aii.connect.landscape.httpport: Port XI-PROD SLD
    3. Now we have done an SLD data cache cleanup.
    4. TEST: I have created a new business system in the SDL (XI-PROD) to check, if this business system is available in the integration builder on XI-DEV. If i try to assign a new business system, I got the error message:<b>Access to object list of type "BusinessSystem" using the InternalEOAService BusinessSystemAccessor failed</b>.
    Also i get the error: <b>"No connection to SLD"</b> if i try to compare the adapter-specific entries of a business system with the SLD.
    What is the reason? What steps are missing?
    Do i need to maintain transactions like LCRSERVADDR (server address of landscape directory?) and SLDAPICUST or anything else??
    Thanks for any help!

    Chris,
    Follow the OSS Notes
    720717: Reduce the number of System Landscape Direcotries (SLD) &
    768148: Using a separate SLD for XI
    This should solve your problem.
    regards
    Shravan

  • Patching a Central SLD System

    Hi
    we use a central SLD (system landscape directory) in our XI landscape.
    the disadvantage is, that the XI system is not running well, when patching the central sld system.
    is there a guideline from sap, to minimize downtime of the XI system, when patching the central sld system ? or do you have good ideas, to keep the XI system running, when patching the sld system ?
    Thanks in advance,
    peter

    Hi Peter,
         Go though the files for help on minimize downtime:
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/12/5ec33a6e386436e10000000a11402f/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/12/5ec33a6e386436e10000000a11402f/frameset.htm</a>
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/42/2da73a0e547d22e10000000a114084/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/42/2da73a0e547d22e10000000a114084/frameset.htm</a>
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/b1/8c8838754ebb10e10000009b38f8cf/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/b1/8c8838754ebb10e10000009b38f8cf/frameset.htm</a>
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a02397f9-0d8d-2910-e5a0-b8241bbc9381">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a02397f9-0d8d-2910-e5a0-b8241bbc9381</a>
    Regards,
    Subhasha Ranjan

Maybe you are looking for