Synchronzing single SLDs

We plan to use Solution Manager 4.0 as our main SLD (it is configured for that now). As it stands, only Enterprise Portal was pointed to this SLD during installation. We have other systems (XI/PI 7.0 and BI 7.03) that have been configured with their own local SLDs. I have found this note (which is not current in English and is for NetWeaver 2004) that refers to how to synchronize the local SLDs with the central SLD, 764393 Configuration of the SAP System Landscape Directory.
This note discusses an export/import technique. I have found nothing on service.sap.com/sld or elsewhere. Does anyone know how to handle this situation?
Points awarded. Thanks!

Hello Thomas,
Nota 764393 is already in English.
Pleae read the SLD Planning Guide PDF from www.service.sap.com/sld > Media Library, there you can see how to export and import the different contents of SLD.
Also checks notes:
935474 -Grouping SLD instances
954820 - Compatibility of SLD in the system landscape
764393 - Reduce the number of System Landscape Directories
Hope this helps,
Dolores

Similar Messages

Maintaining a Single SLD is Better Or Multiple SLD is Better

Hi All,
Maintaining a Single SLd is Better Or Multiple SLD's are Better While Working with the DEV, QTY, PRD..............
Please Give me the Reason
Regards
Babu

Hi babu,
check this
Difference Between Central SLD & Local SLD
see what Bhabes wrote ....
SAP recommends a Single SLD.
Having a separate SLD for every environment beats the concept of SLD itself. SLD is a place where you can look and understand what components/ system run in your landscape. If you are going to hve one for every Environment, it is against the concept of SLD itself. More maintenance is another issue.
Single SLD as recommended by SLD has the problem that you do not want to provide access to a component that can be used in production to developing teams and so on .What Barry has pointed is something that is a more practical approach.
There are no hard and fast rules. A client present across Geographies, havinng multiple vendors and IT teams handling different geographies would prefer to have multiple SLD's one for each Geography and then maybe a master SLD that is going to conain all info of the other Sld's and so on., There is no direct answer to this question other than it purely depends on individual clients.
Regards
Bill
reward points if it helps u

Single SLD for EP and PI

Hi Experts,
I plan to have a single SLD for EP and PI.
EP is on a diff box...now when im configuring PI after installation...
what do i do?...In tech systab under ep sld i dont see any entries for exchange infrastructure..ne idea?
can i have ur views pls?

Hello
If you wish to use a central SLD on the EP box, you will need to apply the notes below:
1) #720717 Reduce the number of System Landscape Directories (SLD)
2) #768148 Using a separate SLD for XI
Regards
Mark

Multiple oracle instances in single SLD

Hi
There is requirement from management that they need a seperate database in the present SLD (DEV,QAS,PRD). Since they plan to move this database in future to another SLD. I have gone through some SAP notes that u can have multiple SAP systems and underlying databases on a single host. Also I noted that u need to have a seperate transport directory.
My doubt is since SAP SID requires a Database SID during the installation. So how this new database can be incorporated in the present system.
If any white papers,pitfalls are highly appreciated.
Thanks

Hi Erick
It is the same oracle version i.e 9i rel.2. we need a seperate oracle insance. My concern is even though u installed a new database making it available in the present DEV,QAS,PRD is a problem. How the existing Dialog instances will recognise this new oracle instance.
what i came to know from the documents is that u need to have a seperate SAP systems and underlying the new database is quite possible and u need to take care of sizing. I searched on the net but couldn't find a similar scenario.
Any other inputs are higly appreciated.
Thanks

Transport targets for single SLD for (Dev & QA), another SLD for (prod)

Hi All,
My landscape is
systems: DEV ( Dev & QA )----->PRD ( prod ).
i.e, Development and Quality in one sys DEV , Production in the other PRD.
i have two business systems in DEV :
1) BS_Dev1
2) BS_Dev2
i created a group for these , say DEV_GROUP
As Dev and QA are under one SLD, there is no need of quality group right?
so i have created business sys in DEV:
which points the target business systems for BS_Dev1 & BS_Dev2
1) BS_Pro1
2) BS_Pro2
and created a target group for these, say PRO_GROUP
So my question is , as there is no QA in landscape
this would be the procedure to create the Groups and target systems for the objects of DEV (Dev & QA ) to PRD.
And then transport the objects from DEV (SLD -> Administration -> Content -> Export)
to PRD (SLD -> Administration -> Content -> Import).
Correct me if i am wrong.
Thanks
Sai

Hi SAI,
Check the [LINK|http://www.****************/Tutorials/Basis/Transport/Index.htm]
came across few blog on PI transport process..hope it helps:
/people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi
/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
/people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview
/people/sap.india5/blog/2005/11/28/xi-software-logistics-solution-iii-cms
Regards,
Naveen.

Development and Production SLDs

We have completed Development and testing of XI objects and are at a stage to transport the objects to Production. We have two SLDs for XI, one for Non-productive systems and another for the Prod system. As regards to SLD entries for transport to Production, I though the following is the process
1. Create Production Business systems in DEV-SLD putting them in the right Business group
2. Export DEV-SLD entries
3. Import the file into PROD-SLD
4. After go-live only delta SLD entries would be exported and imported into PROD-SLD
In the following Weblog, /people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation, Yuvaraj talked about SLD data supplier bridge from Dev SLD to Production SLD. Is this absolutely necessary? With the bridge operating, what happens if somebody deletes a business system by mistake in Dev SLD?
Any inputs would be appreciated and rewarded

Bhavesh,
My reason for not having prod entries on Dev SLD is that if Prod Entries are going to be on dev SLD, then why have a separate SLD for Prod itself?
My logic for this would be during development, create all the Production Business Systems in DEV-SLD and transport them to PROD-SLD. At runtime system uses Prodcution-SLD. I guess the differernce is design time vs Runtime.
But once again, SAP recommends a single SLD and so when the landscape contains multiple SLD's there are no rules on how to go about this and so either way things will work fine :-)
SAP's recommendations seem to have changed off late. Though in online help they have again and again mentioned that one SLD is recommended, I do know that some internal SAP Consultants recommending separate SLDs for non-productive and productive purposes. There are also documents on Service market place providing information on how to set-up two SLDs for productive and non-productive purposes.

Do XI service users have to exist in the SLD with the same password?

Hi All,
Do XI service users have to exist in the SLD with the same password?
We have a 3 system(development, QA and production) XI landscape with a single SLD. All systems are NW04s with support stack 9.
We are required to change XI service user passwords. I have found OSS note 936093 for changing these passwords. What I am not sure of is if I can change XI service user passwords one system at a time. I am under the impression that XI service users must exist in the SLD with the same password as the XI system. If this is correct, I have to change service user passwords in all three systems at the same time which is not very feasible.
Thanks,
Hamid Lashgari

Creation and Maintain Users
For the transport of Integration Server content, it is a good idea to install CMS on an
existing Integration Server. In this double-stack scenario, where an ABAP and J2EE
stack is used, user management is different from a J2EE only installation.
Note: For more information about using CMS on a J2EE only installation, see the
CMS documentation.
The following section describes the double-stack user management settings required
when CMS is running on the Integration Server in the development environment. See
Figure 2. The description we provide starts with ABAP user management and is followed
by the maintenance in J2EE User Management Engine (UME). You proceed as follows:
Create the service user LSADMIN using transaction SU01.
Assign the ABAP roles SAP_XI_CMS_SERV_USER and
SAP_SLD_ORGANIZER to the LSADMIN service user.
Create the ABAP role SAP_CMS_ADMINISTRATOR and assign this role to the
ABAP dialog user(s) responsible for CMS administration.
In UME, create the role CMSDeveloper with the actions CMS.Display and
CMS.Export.
In UME, create the role CMSAdministrator with the action CMS.Administrate.
In UME, assign the users representing xirepuser and xidiruser to the role
CMSDeveloper.
In UME, assign the group SAP_CMS_ ADMINISTRATOR to the role
CMSAdministrator.
Log on to CMS with the ABAP dialog user responsible for CMS administration.
Maintain the CMS service user (LSADMIN) for the domain.
Task XI Dev
With CMS XI Test XI Prod
Create the service user LSADMIN in TA using transaction
SU01. Yes Yes Yes
Assign the ABAP roles SAP_XI_CMS_SERV_USER and
SAP_SLD_ORGANIZER to the LSADMIN service user. Yes Yes Yes
Create the ABAP role SAP_CMS_ADMINISTRATOR and
assign this role to the ABAP dialog user(s) responsible for
CMS administration.
Yes No No
In UME, create the role CMSDeveloper with the action
CMS.Display and CMS.Export.
Yes No No
In UME, create the role CMSAdministrator with the action
CMS.Administrate.
Yes No No
In UME, assign the group SAP_CMS_ ADMINISTRATOR to
the role CMSAdministrator
Yes No No
Log on to CMS with the ABAP dialog user responsible for
CMS administration.
Yes No No
Maintain the CMS service user (LSADMIN) for the domain. Yes No No
Figure 4: Overview of User Management Tasks in Different Systems

JCo connection and SLD

Greetings, we have a federated portal which is using JCo connections as part of the MSS/ESS business package. We had a situation where the SLD was down therefore the JCo connections were down. Our question is JCo connection completely dependent on SLD. In other words if SLD is down, will that mean our JCo connection will fail thus an outage.
If this is the case what is the best way to make sure SLD is highly available? Our options are to make SLD highly available or distribute SLD on each system.
Also, what is the performance hit on making SLD distributed on all Portal system if this the route we go?
Thanks in advance!

Hi,
The distributed SLD servers can cause higher administration expense with regard to consistent data. Therefore, we recommend that you consider to use a single SLD server first.
but for large system landscapes that are distributed over different geographic locations, a single SLD server might slow down the performance of involved application systems. In this case, a distributed SLDserver installation can be taken into account.
Samrat

Use of Related integration Server in SLD

Hi all,
I understand that Related integration Server from SLD is used when we have proxies. Is there any other use for it?
cheers
danus

Hi,
The Related Integration Server is used to assign your Business System to a Transport Group.
When you create a Transport Group in the SLD you assign the corrsponding Integartion server to this transport Group.
Now, when your create a Business System and assign the Related Integration server , this assigns the Business System to the correspinding Transport Group.
The best use case is when you have a single SLD being shared between Dev , QA and Prod.
The Related Integartion Server has nothing to do with proxuies.
Regards
Bhavesh

Doubt on sld

Hi,
    I'm new to XI plz assist me by answering my questions
           1.if we maintain single sld for dev, con & prod is it necessary to transport
TECH & BUSS.SYST's information to TEST SYST or just we to transport only configured objects to TEST SYST by maintaining B.SYT groups and TRANSPORT
TARGETS?
           2.For testing in Quality systems what procedures will be used ?can we test manually ? if so how would be the procedure?
           3.can any give the procedure how to register a new technical syst in SLD?
Is it necessary to go to RZ70 for registering a new syst after giving host details through data supplier in ADMINSTRATION TAB ?
           Plz answer as briefly as posssible , good answers will be rewarded.
                                                                                Regards,
                                                                                Smitha.

Hi,
Go trhough these blogs
/people/praveen.mayalur/blog/2007/05/31/configuration-of-cms-in-central-nwdi-sld-to-transport-xi-objects
/people/community.user/blog/2007/02/12/placement-of-the-sld-in-large-landscapes--so-confusing
/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
Regards
Hemant
If find helpful plz award points

How many SLD's require for 2 solman system requirements?

Scenario1:
One solman system for entire landscape->One SLD is required.
Is this SLD should be a seperate system or can be within solman?
Scenario2:
One solman system for DEV/QAS and other solman system for PRD.
How many SLDs are required? Can we manage with single SLD?
If two SLDs, Then both should be seperate systems. i.e, One SLD -> DEV/QAS Solman, Another SLD ->PRD Solman.
If only one SLD, Then it should be seperate system or can be within solman?
We do have EP in client enviroinment. Can we use SLD of EP?

Hi,
you can use one SLD for all your systems if you want. You can either use an existing one or the one which comes with Sol Man. That's up to you.
Any scenario is possible.
/cheers

SLD - One vs Two vs Three

We just installed our SAP XI for QA and selected to use SLD on the DEV box.
We are planning to have PROD its own SLD.
Is there any disadvantage in sharing SLD between DEV and QA?
I am reading the past weblogs. Please share any latest experiences.
Regards
Mike

Hi Michael,
In many implementations,SLD will be shared for DEV and QA environment and separate SLD for Productions.
But SAP suggests to go for single SLD. Just refer this note- 720717
Some discussions on the same-
Recommendation on SLD for XI
SLD best practices
How to handle SLD in XI ( https://websmp201.sap-ag.de/nw-howtoguides) from service.sap.com
Hope this helps,
regards,
Moorthy

JDI and SLD question

Hi,
We've DEV and PRD Portal Systems. Currently PRD Webdynpro applications using local SLD on PRD. But we'll install and configure JDI on DEV System. Also aiming to use SLD for JDI which resides on DEV.
So the scema looks like;
JDI uses SLD which is on DEV and PRD Dynpro apps using SLD which is on PRD.
Will it work? Do we need to use single SLD?
regards

Hi Huseyin,
When using 2 SLDs one for DEV and one for PROD, you should export all home developed products/SCs you developed from DEV and import them to PROD as well - keep the CIM consistant. This is the only requirement.
You should do this step every time you are ready to release new product or version.
Regards, Angel

Difference Between Central SLD & Local SLD

Hi All,
Q1) What is the Difference Between Central SLD & Local SLD.
Q2) Maintaining Individual SLD For DEV, QTY, PRD Servers is the Best One Or Maitaining the Single SLD is the Best One ????
Please Ans These Two Q's
Regards
Vamsi

> 2. Maintaining individual SLD for DEV, QTY & PRD
> will be better approach. We follow this approach.
SAP recommends a Single SLD.
Having a separate SLD for every environment beats the concept of SLD itself. SLD is a place where you can look and understand what components/ system run in your landscape. If you are going to hve one for every Environment, it is against the concept of SLD itself. More maintenance is another issue.
Single SLD as recommended by SLD has the problem that you do not want to provide access to a component that can be used in production to developing teams and so on .What Barry has pointed is something that is a more practical approach.
There are no hard and fast rules. A client present across Geographies, havinng multiple vendors and IT teams handling different geographies would prefer to have multiple SLD's one for each Geography and then maybe a master SLD that is going to conain all info of the other Sld's and so on., There is no direct answer to this question other than it purely depends on individual clients.
Regards
Bhavesh

CTS+ Transports in SAP PI 7.1

Hi experts,
we have a new installed SAP PI 7.1. Our scenario is that we have a single SLD for each PI System on dev, test and prod.
Now we are facings some troubles regarding the SLD setup. Our target is to use CTS+ to transport IR and ID objects. In the how to guides I found in SDN I found always settings within the visual admin to get this scenario run. But as I understood there is no more visual admin in SAP PI 7.1.
What are the required steps to connect my sld from dev --> test --> prod and what is additional to perform to get my ID objects transported from dev --> test --> prod.
Regards,
Björn

Hi Bjorn,
CTS+ is a transport mechanism used to transport NWDS, IR, ID objects.....basically JAVA objects......
For CTS+ and NWDI...check it :
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0d96022-9df5-2910-90b8-8e0580e0987e?overridelayout=true
Regards,

Synchronzing single SLDs

Similar Messages

Maybe you are looking for