Central SLD vs SLD for each XI instance

We are starting our SAP XI project.  We are on XI 3.0 sp 9.  We are trying to make a decision on which of the SLD configurations is the best for our company.  We will have 3 SAP XI systems (dev, qa and Prd)  should each have an SLD or should their be a central SLD?  What is working for people currently in production?  What are lessons learned?  Thanks

Hi,
We do not have yet implemented production XI environment but as SAP IT consultant, I am thinking about system architecture design based on SAP NetWeaver platform.
So I would say for good performance, it will be better that each XI connect to its own SLD system but for system landscape maintenance I would advise to have a central SLD only if each XI systems (dev, qa and prod) communicates with the same system landscape.
You also have to think about XI object transport from dev to qa and prod...as XI design and configuration objects are based on SLD model  (business system, software components)  you should have the same SLD
in each environment...so in that case a central SLD could be a good option but you could also imagine as an alternative solution an SLD model replication strategy between each SLD systems
But we still have the question of SLD maintenance security and I really do not think that it is a good idea for dev purposes to allow changes in a central SLD used by an XI production system !!!
The last point is that in some NetWeaver scenario SLD is not only used by XI but also by EP - WebDynpro with JCo connection for instance - so if you would want to use other NetWeaver components I would say to have a standalone SLD system for security reason and shared efficiency.
So you should have at least two SLD systems (one for dev/qa and one for prod) but we could imagine the following architecture :
1- XI dev with its own built in SLD system which one has an SLD namespace for dev purposes (dev_namespace) as a sand box and an other namespace (rep_namespace) which is the replication of the prod landscape (prod_namespace)
2- XI qa with its own built in SLD system with only one SLD namespace (qa_namespace) as a copy of rep_namespace
3- a standalone SLD system with one namespace (prod_namespace) to share it with other NetWeaver components without the risk to break down connection in case of XI prod problems.
XI prod points to this standalone SLD
4- if you are not using others NetWeaver components, a standalone SLD for production is not useful and then production SLD is in the production XI system itself.
So that my first feeling...but still open for discussion on that important point of system architecture design.
I hope it helps you a bit to have a decision.
Greetings
Nicolas

Similar Messages

  • Can I use local SLD for each system?

    Hi!
    Our company is a big SAP outsourcing with hundreds of SAP systems.
    We plan to use the local SLD for each new system (>640).
    Is this a possible and good solution?
    Point guaranteed.

    Jenni,
    Please have a look at the below doc on how to place SLD in your landscape, its worth reading and you can decide your dimensions of placing the SLD.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/29b1f3ea-0c01-0010-2dae-cc64bb381c97
    Best regards,
    raj.

  • 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

  • Central SLD and Webdynpro

    Dear all,
    I have a new EP 6.0 installation running ESS/MSS and BW reporting and implemented central SLD.The SLD server was the CEN Solution Manager system. Because of some issues with support pack application in the solution manager system, the solution manager system was unavailable for a week. As the Webdynpro JCOs that are used in ESS/MSS use SLD, ESS/MSS in my portal systems became unavailable for my users. I had to configure local SLDs for each portal system to avoid the application downtime
    I am wondering what people are doing out there to avoid what happened to me: High Availability? Seems a bit over the top as we do not have HA for our mySAP ERP production system which is the most important system of the landscape. Any other thoughts or SAP recommendations would be very much appreciated
    Many thanks
    Andreas

    Hi,
    Ofcourse HA should be one of the strategies you should think about. But now that you don't have it in place and cause for downtime is something like upgrade or maintenance, which is unavoidable, you can maintain the ECC system (HCM System) in your SLD, point the JCo Connections to your ECC system and thereby you should be able to use ESS-MSS. This won't take more that an hour, trust me.
    Would also like to know what's your User Management Strategy ? If you are using the solution manager as your datasource for user management on portal, then you can hardly do anything.
    Cheers,
    Sunil
    PS: Reward points for helpful answers.

  • 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

  • Central SLD - Manipulations

    We want to prepare a central SLD by merging many instances of current local SLDs.
    We found note about merging and grouping instances... it is ok.
    My question deals with next steps because we want to keep local SLD in Production instances (PI, BW instances)...
    We will need to export data of central SLD when built, into local production SLD... but some of local production SLD already have data. Do we need to purge them before import ? If yes how ? Is there a risk to create duplicates entries, associations ?
    Thanks a lot

    Hi,
    Since even bringing up the useradmin web page is slow, it cannot be the SLD.
    Bad response time is caused by cpu, memory and/or network.  Is the SLD server on the same network subnet as XI or your PC?
    You can also logon to the SLD server and examine the cpu and memory utilization.
    Examine the J2EE log to see if there are any errors.  This can also cause response time problem.
    Regards,
    Bill

  • Need suggetions on Central SLD as Solution Manager!

    Hi Experts,
    I need a help/ suggestion on deciding the Central SLD system in our landscape. 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 is not recommending using Solution Manager as Central SLD System. So please tell me, is it recommended or not and what problems may occur in future if we continue Solution Manager as Central SLD.
    Thanks,
    Ajay.

    Read these three blogs. They have the answers that you need.
    /people/boris.zarske/blog/2007/06/10/an-overview-of-the-documentation-required-to-set-up-the-system-landscape-directory-sld-of-sap-netweaver
    Solution Manager 7.0 and SLD => /people/dolores.correa/blog/2007/10/19/solution-manager-70-and-sld
    /people/boris.zarske/blog/2008/03/21/sld-general-recommendation-how-to-set-up-the-system-landscape-directory

  • 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

  • Does CE7.1 need a central SLD?

    We are going to use CE7.1 with ESR.
    We are not sure which is better in terms of SLD strategy: using the local SLD  on CE7.1  OR  using our centralized
    SLD?
    Please advise. Thanks!

    > We are not sure which is better in terms of SLD strategy:
    > using the local SLD  on CE7.1  OR  using our centralized SLD?
    Use the centralized SLD for the CE like for any other application system.
    Regards
    Stefan

  • Executing a message mapping for each instance of a sub-message

    Hi,
    I have a message struct like the following.
    MT_TEST (1..1)
             |----
    >IDOC (1..Unbounded)
    There is a field in each instance of Idoc, depending on its value, I need to perform receiver determination.
    The target for each IDOC instance will be different for each value of the field.
    How do I write a XPath expression to achieve this?
    Also, is there any other method of achieving the same goal?
    Cheers,
    Earlence

    Hmmm.. so idoc is at source side..... Ok so multiple idocs are coming in one bundle BUT you cannot just divide the payload based on some conditions in Receiver Determination.
    In your mapping you can map the source date to different targets but that is different thing.
    Note: You can either send the whole payload to one receiver or nothing. You cannot send a part of the payload to 2 different receivers.
    So it means it doesn't seems to be possible.
    Regards,
    Sarvesh

  • 1 server, multiple oracle_homes for each instance (dev, test, uat, etc)...

    Hello,
    We have one beefy server to hold our dev and test and maybe more non-production databases. My plan was to install separate oracle_homes for each so that I can patch and only affect one instance at a time. Is anybody else doing this? Does this sound right? Any gotchas that you have run into with this type of environment?
    I read something about you should only have one active listener...
    Same concept, but with the ASM instance. Can I also install multiple oracle_homes for each asm instance on the same box? Is anybody else doing this? Again any gotchas people have run into to? For ASM, should I also have only one active listener?
    Am I right that the only thing that affects all instances is at the OS, hardware level such as Linux patches, anything to do with users, groups, shared folders, nics, etc?
    Thank you for your input!

    For ASM, should I also have only one active listener?ASM does NOT require any listener & none should exist for ASM.

  • Using a Single HTTP Server for Multiple APEX Instances

    Our company's DBA Manager has asked if it would be possible to externalize the HTTP server portion of APEX from the DB Servers. In other words, he would strongly prefer that the DB Servers *only* run Oracle Database software.
    We know that we can install the HTTP server on another box but, in thinking about how to do this, we were wondering if it is really necessary to create a separate HTTP server installation for each APEX instance. What we'd really like to do is have one HTTP server for all our our Dev boxes and several (but, not one to one) for each of our upper environments; staging, qa, prod, etc.
    Right now, each instance have a single dads.conf file on each DB box. So, if we we're to attempt to consolidate them, we'd need some way to embed multiple dads files and to associate each instance with the correct one.
    Has anyone ever done this or (preferably) have some examples?
    Thanks,
    -Joe

    Joe,
    I don´t know a specific reference for it, I remembered it because when I was looking the documentation on the site, I saw the reference "Support for multiple database connections" in the URL: APEX Listener New Features 2.0</title><meta name="Title" content="APEX Listener New Features 2.0…
    I´ve tried to use APEX listener some time ago, but in a earlier version together with glassfish. So, since for me was only one database, I created the necessary amount of DAD´s on my database, each one for a specific port.
    Check the link and you´ll see the same information I saw.
    Thanks.
    José Valdézio
    "Neo, everything that Oracle told me, became true, except extinguish bugs in a first release."

  • Listener configuration for 2 db instance in a single node

    Hi,
    I have configure a 11gR2 server with 2 db instance (A and B), but I have only one listener (default) to server this two db instances.
    Is this the recommended configuration or should I have one listener for each db instance? e.g Listener_A and Listener_B. I think it will be usefull in cases when I need to block the access to one db instance (A) without shutting down the database, by just turning off the proper Listener.
    With my current configuration I am not able to do that since if I turn of the only listener that I have both dbs will not receive any other connections.
    Am I correct?
    Regards,
    Edited by: ashum on May 13, 2011 8:21 AM

    You are right that there is some value in going to the trouble to set up a separate listener for each database. Whether you take this approach depends mainly on how satisfied you are with the alternatives and how much trouble you want to incur in setting up and maintaining multiple listeners. We use separate listeners for each of our databases and really like the granularity it provides in limiting the scope of outages.
    If you take the multiple listener approach, you will need to either use separate ports for each listener, or bring up a virtual ip on your server so that the second listener can run on the virtual ip.

  • How to configure PI for Central SLD ?

    HI Guys,
    we have installed PI 7.0 NW2004s SR2 and now we need to configure the syatem as Central SLD.  can any body breifly explain how to do this ?
    any help would be really appreciated
    Thanks,
    srini

    Hi srinivas...
    As for my understanding ...you need to do post installation to configure your PI server,,,,
    Goto http://<Host>:<port>/nwa
    There you find the administration --> Click on DEPLOYandCHANGE Tab
    righthand side corner you find the Templates...select the PI...
    click on Execute template ....
    finally click on install button...It will perform all the necessary action to configure PI server...
    I hope this might help you..
    regards,
    vasanth

  • What is recommended hardware requirement for central SLD?

    We plan to have cental SLD for the entire landscape(Small size-ECC 6.0, EP and BI).
    So what is the recommended hardware requirement for this SLD?

    Hello Sanjai,
    Please use the following link to find the complete information about System Landscape Directory. (My recommendation is read the Planing Guide for SLD).
    System Landscape Directory (SLD) the SLD paper to develop your strategy.
    Hope it helps.
    Regards,
    Satish.

Maybe you are looking for