SLD Strategy

Hi,
We are currently installing XI and are looking at a strategy for an SLD....we only have an SLD installed for the XI dev box.
Is it best to
i) Create one SLD...but if you have installed it on DEV should u move it to production?
ii) create two sld's....one for dev,qa and another for production?
iii) Create Master for full SAP landscape and then have XI SLD read from the Master....and if so do u still have a two XI SLD's?
Thanks in Advance
Jim
Does anyone have any advice or could tell me what strategy they followed.

Hi,
Thanks for the advice....
I just have another question....
Michal your advice of one SLD seems to tie into all the documentation and makes sense but.....
When applying SP to J2EE or ABAP can that affect the SLD...
What my colleagues fear is that we apply or SP to dev,qa and then when you go to production the worst thing happens and the SLD is affected screwing up the system. They feel if you had a seperate SLD at qa or dev you avoid this scenario.
I don't have enough knowledge to argue this point but i would of thought the SLD is designed not to be affected by any upgrades or SP's.
Thanks
Jim

Similar Messages

What is the best SLD strategy for CE?

We have some options like a single centralized SLD or a local SLD or something between them, e.g. an SLD for dev systems, etc.
Could you share your opinion -- what is a good SLD strategy for CE? Thanks!

Hi,
It wud depend on the landscape u have and requirement stategy.............
If you have a productive version...............obviously centralised SLD wud be preferred.....
Either case......juz to touch-base features of CE 7.1 i.e for exploration and R&D purpose..........lacal SLD and developer edition wud do.......

Defining an SLD Strategy for XI Migration using CMS

Can the following scenario occur? Please explain if any of my assumption are incorrect.
-> An XI DEV, QA, and PRD environments each with a separate "slave" SLD.
-> A separate "master" SLD that contains all XI dimensions (i.e. transport, solution, and technical).
-> This "master" SLD will deploy all relevant SLD components (Products (versions), SC (versions), Technical Systems, and Business Systems) to the specified SLD "slave" environment. For instance, the master SLD will provide only DEV SLD components to the DEV "slave" SLD specific instance. No QA or PRD SLD relevant components will be stored on the DEV "slave" SLD.
-> All Integration Repository (IR) and Integration Directory (ID) objects will be exported from DEV "slave" SLD and imported into the "master" SLD.
-> All ID components will have transport targets defined in the master SLD for DEV to QA and QA to PRD, respectively.
-> CMS will perform all transports from DEV to QA and from QA to PRD for both IR and ID components by defining "tracks" for specific SC and development configurations for each of the development states of an SC.

The following scenario can occur. That's what we're doing at our customer site.
-The only thing is that you can import QA and PRD relevant components to DEV. If you want to define the transport targets between the systems, then this information will need to be the individual SLDs (slave SLDs).
I hope this helps.
Regards,
Jay Malla
SAP XI Consultant
Licensed To Code

SLD Downtime

In our prod, SLD in local to XI or in other words SLD using XI java engine.
I installed the De-Central Adapter Engine and some of our important interfaces goes through it.
If XI java goes out of memory, it is going to be restarted by its own, till that XI java comes up. SLD will be down
because it uses XI java engine. It takes usually 6 minutes to come up. In mean time will effect my interfaces running through
De-central adapter engine? my understanding for every 3 to 5 minutes XI runs reports to update the cache ? in this time it communicates with SLD and not for every single interface execution.
Can my De-Central adapter will able to manage this SLD downtime ?? If not sure ? is there any way to avoid this ?? by installing another SLD and making a bridge between this SLD and that SLD ?? or like that ?? I'm not sure if this possible ?
Please share your knowledge and thoughts.
Thanks
Sagar

May be you can employ a backup SLD strategy - refer to -
/people/wolf.hengevoss/blog/2010/01/28/sld-topology-how-to-gather-and-distribute-sld-data-in-your-it-landscape
VJ

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

SLD landscape Strategy

Hi All
Can anyone please point me to SLD installation/implementation strategy. Can SLD/Solution Mgr can be installed on the physical box.
Thanks you.

Hi Julio,
SLD is a concept introduced by SAP from its netweaver releases. Yes solution manager can be installed on a physical box.
For SLD implementation strategy please visit:
http://help.sap.com/bp_epv170/EP_US/Documentation/How-to/Configuration/Post_Install_SLD_NW_2004s.pdf
Please award points for helpful info.
Regards.
Ruchit.

SLD Naming strategy

I have different application that sends files into FTP in different folders.
Do I need to create <b>one</b> business/techical system in SLD with generic name like FILE_SYSTEM? This system will have several channell in ID.
Or I need to create each business/techical system for each applicatiuon in SLD.
What are your suggestions?

Hi Sergey,
both is possible. One more alternative is only to create a business service without SLD entries. If you have a good reason to reduce number of directory objects use only one system with more channels; if you prefer a extendable solution (X-Path routing) use more systems with only one channel.
Regards,
Udo

Strategy/Recommendations for SLD content

Hi All,
lets take below business case of a project:
there are 3 non-SAP applications.
nonSapApplOne_Java
nonSapApplTwo_DotNet
nonSapApplThree_CustomLegacy
there are 2 SAP applications.
sapApplFour_ECC6_Module_HCM
sapApplFour_ECC6_Module_FICO
sapApplFive_R3
I would like to know the options/recomendations for creating Products/SWCVs and BusinessSystems.
e.g.
should we create each product for each application (for each sap and nonsap applications)?
should we create one product for nonSAP applications, and one product for SAP applications?
should we create one product for entire project, and a SWCV for each application (for each nonsap and sap application)?
or can we represent/separate the applications by namespaces within same SWCV?
should we create a separate SWCV for storing the objects that use multiple applications design objects e.g. mapping objects, process integration scenarios etc.?
for each SAP module like HCM, FICO, should there be different namespaces when integrating with other applications.
do we need to use business system groups for organising sap and nonsap business systems.?
these mostly need to be designed/decided in the beginning of the project, as it forms the base of the rest of the deveopment.
Can you pls share your comments and recommendations for above kind of queries.
thanks in advance,
Madhu.

should we create one product for entire project, and a SWCV for each application (for each nonsap and sap application)?
I am not sure what is meant by a Product! The creation of a SWCV should be related to a business unit that your organization has (at least we follow this practice). Suppose your organization has three Business Units (Sales, Manufacturing, Maintenance) then in such a case you can create three different SWCV with each containing BU-specific development. So all the development related to Sales will come under the SWCV for sales and so on.
or can we represent/separate the applications by namespaces within same SWCV?
answer as implied above.....not a good practice to develop namespaces based on the applications...namespaces should be related to the interface name...say you have an interface for salesorder transfer from system X to Y then your namespace should reflect salesorder in it and if you have multiple salesorder processes then you can append some terms to the NS which will help differentiate between the individual SO processes.
should we create a separate SWCV for storing the objects that use multiple applications design
objects e.g. mapping objects, process integration scenarios etc.?
If you mean object reuse...then you can define a common namespace within a SWCV and develop the commonly used objects in it and then refer these in other flows (namespaces) defined within the SWCV.
for each SAP module like HCM, FICO, should there be different namespaces when integrating with other applications.
Suppose you have 5 different Integrations involving HCM ---> FICO (or other combination) then your namespaces should be in such a way that there is a clear differentiation between the 5 integrations
For more information on how your objects should be defined you can go through this document:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90b213c2-d311-2a10-89bf-956dbb63aa7f
All the above mentioned points are my personal...the implemenation should be in accordance to the best practices suggested by SAP and secondly according to the organizational needs.
Regards,
Abhishek.

[SLD] Autoregistration of ABAP System in SLD

Hi,
want to registrate an ABAP system in SLD.
RZ70 create errors, because RFC destination is missing.
Trying to create a destination type T to the SLD sytstem. I'm
using same parameter as define in another system that is
also connect to SLD, but he doesn't recognize the gateway service.
Without gateway information he says that the programm is not
registered yet.
Where to register the programm? In ABAP system or XI?
thanks

Hi,
you can find the solution here.........
XI Software Logistics Solution III: CMS
XI Software Logistics Solution III: CMS
XI Software Logistics II: Overview
XI Software Logistics II: Overview
XI Software Logistics 1: SLD Preparation
XI Software Logistics 1: SLD Preparation
SLD: General recommendation how to set up the system landscape directory
SLD: General recommendation how to set up the system landscape directory
TechEd '07: LCM228 - SAP NetWeaver System Landscapes
TechEd '07: LCM228 - SAP NetWeaver System Landscapes
TechEd '07: LCM112 - System Landscape Directory of SAP NetWeaver: Concepts and Best Practices
TechEd '07: LCM112 - System Landscape Directory of SAP NetWeaver: Concepts and Best Practices
Sizing a System for the System Landscape Directory of SAP NetWeaver
Sizing a System for the System Landscape Directory of SAP NetWeaver
An overview of the documentation required to set up the system landscape directory (SLD) of SAP NetWeaver
An overview of the documentation required to set up the system landscape directory (SLD) of SAP NetWeaver
Planning a Strategy for the System Landscape Directory (SLD) of SAP NetWeaver
Planning a Strategy for the System Landscape Directory (SLD) of SAP NetWeaver
ULM206: Landscape Strategies for the System Landscape Directory of SAP NetWeaver
ULM206: Landscape Strategies for the System Landscape Directory of SAP NetWeaver
Thanks,
Madhu

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.

Adding additional sld

Hello,
we have 1 sld - configured on the portal dev -
i would like to add additional sld - configure it on the portal production - all the production systems will be added to this sld, and all the qa and dev systems will remain on the sld opn the portal dev
what are the specific pahses in adding additional sld , updating it if neccasary, and moving the relevent systems
Regards,
Moshe

Hi
The task could be done like this:
1) Activate the SLD in the EP prod and configure post-processing accord. to SLD guide
2) Ensure that the DEV-SLD and new PRD-SLD has the same CIM model version and SAP_CR version
3) Export the content from DEV-SLD (export line ALL)
4) Import this export into PRD-SLD
5) Configure all production systems "SLD data provider" to send technical data to PRD-SLD
6) Configure all production systems "SLD client role" to work with PRD-SLD
...now the DEV-SLD will only get technical data from the non-productions systems. If you want both SLD's to have a full view of alle systems then ALL systems could use PRD-SLD as target for their data suppliers and a sync from PRD-SLD to DEV-SLD can be set up... You maybe also need to supplement this strategy with manuel export/import of SLD content.
BR
Tom Bo

Tranport Considerations cross different SLDs

We came cross following situation:
There are different SLDs in different Landscape:
Saying we have Dev SLD and Test SLD, there is no one is master SLD. They are peer-to-peer right now.
We have development done and now we need to transport our deployment to Test:
But right now, the two SLD contents are messy: In Test SLD, it also have TS and BS created (not imported) that already created in Dev SLD.
What are the best approach to clean up the SLD contents ?
Thanks
Liang

Vijay,
Are you sure you had deviced the strategy you had mentioned here? If it was the same did it work ?
Cause if i understand you correctly then i dont agree with you.
>Then the Production SLD would need to have pnly the Prodcution TS and BS.
Do you think CMS will work in that case? Shoudnt the production SLD have QA BS.? It should have.
>For Dev to QA, the target must be mentioned in Dev
Why do we need to mention the target in Dev SLD?
For Dev-QA - the source system should be mentioned in the QA SLD. There is no need to mention the target in the Dev SLD. And as you said the target should be available in the QA SLD.
>From Qa to Prd, the target must be mentioned in QA and the target must be available in PRD.
We would need to do the same way as mentioned above.
>QA will have all QA and PRD TS and BS
QA SLD doesnt need to have PRD TS/BS. QA needs to have QA & DEV TS/BS.
>PRD will have all PRD TS and BS only
PRD SLD needs to have PRD TS/BS as well as QA TS/BS.
Regards,
Sumit

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.

How to move Software componet and product from One SLD to another

Hi Experts,
I want to move the software component that i created in the development SLD and the product from dev system to Prod system SLD. Our development and the quality share the same SLD so i didnt have to do anything. How do i export the software component and the Product form dev SLd to Prod SLD Or what steps do we need to follow to move the Software component from SLD -> SLD.
I am new to PI and this is the 1st time in am doing this activity. Request you help.
BR Heth.

Hi,
Please ensure to read note #[1540435 |http://service.sap.com/sap/support/notes/1540435]and to decide which update strategy/scenario you
need and in the "[SLD Planning Guide|http://www.sdn.sap.com/irj/sdn/nw-sld?rid=/library/uuid/e0a1a8fb-0527-2a10-f781-8b67eab16582]".
You should ensure that your CIM Model and CR Content on your SLD are updated as
per SAP note [669669 |http://service.sap.com/sap/support/notes/669669]on both SLDs.
Regards,
Aidan

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

SLD Strategy

Similar Messages

Maybe you are looking for