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

Similar Messages

Same wlan both locally switched and centrally switched

Scenario:
1 virtual wireless controller
50 access points, some of them some local to the controller (same site), other on remote sites, all in flexconnect mode.
Is there a way for a wlan to be locally switched for a group of ap's, essentialy those local to the controller, and centrally switched for other groups of ap's, in fact those placed on remote sites?
I've tried configuring flexconnect groups, and ap groups, but no luck, I've found no way to override the globally configured flag "flexconnec local switching".
I've also tried to create two identical wlans, one locally switched and the second globally switched, but the wlc refuses to activate the second one since it has the same ssid of the first one.
Regards,
Massimo.

Since you have vWLC all AP needs to be in FlexConnect mode (If you got a normal WLC you can keep HQ AP in local mode & Remote AP in Flex mode to achieve this)
I think in your case you have to either choose "Central Switching" or "local switching" for your APs.
Regards
Rasika
**** Pls rate all useful responses ****

Wlc flexconnect wlan local authentication and central web authentication maximum rtt

Hi
From the below link below it mentioned that "Round-trip latency must not exceed 300 milliseconds (ms) between the AP and the controller. If the 300 milliseconds round-trip latency cannot be achieved, configure the AP to perform local authentication."
http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Mobility/emob73dg/emob73/ch7_HREA.html#wp1094148.
Is this limitation refer to web authentication also?
Thanks
Anyone???

Central Web Auth (CWA) works different on controllers/APs running in FlexConnect mode. Please check this guide and confirm that you have similar setup.
http://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/116087-configure-cwa-wlc-ise-00.html
If so, please post screen shots with your configs (Redirect ACLs, policies in ISE and the WLC SSD settings).
Also, the version of code that you are running in ISE and your controller.
Thank you for rating helpful posts!

Diffrence Between Local IE And Central IE

Hi All,
What is the difference between the local Integration Engine And the Central Integration Engine ???
Please Explain me
Regards
Vamsi

The systems on which SAP WAS is installed has Integration Engine as one of its components. Now for PI/XI also WAS is a must. Therefore PI/XI also has an Integration Engine called as Integration Server.
Now talking in terms of PI/XI, Integration Server has Adapter Engine, Integration engine (for pipeline steps) and Business Process Engine. This Integration Server is the central Integration Engine.
The Integration Engine of other systems is termed as local Integration Engine
Regards,
Prateek

Solman_setup and central&local solution manager SLD

Hello,
I'm configuring our solution mananger system with transaction solman_setup. The local SLD of the solution manager will also be the central SLD of all our systems. After finishg the basic configuration in solman_setup, and go to "managed system configuration", I can only see the only solution manager system, as ABAP and as JAVA, but no more systems (right, as I haven't defined more systems).
I cannot create more ABAP system with the link "maintain technical systems", the ABAP option when I select create isn't there.
If I create another type of system as a test, for example, third party, the transaction SMSY can see this new system, but the SLD in http://<my_solution_manager_system>:50000/sld doesn't show this new system at all.
Where must I create the systems? and how can I connect the SLD and the SMSY transaction? Should I "add SLD" at the Administration in http://<my_solution_manager_system>:50000/sld and put the suolution manager itsefl system?
Thanks in advance for your help and best regards,
Ana

Hi,
To ensure a system is registering into the SLD and synchronising with SMSY, go to transaction RZ70 and define the Host and Service.
Also, set up a user for accessing the SLD in transaction SLDAPICUST. The user has to exist in the Java stack to log into the SLD.
Also ensure your RFCs are correctly set up for LCRSAPRFC and SAPSLDAPI as per this link:
https://cw.sdn.sap.com/cw/docs/DOC-37953?treeid=DOC-7936
Then use transaction SLDCHECK to ensure your connection is working.
Finally enable SLD synchronisation into SMSY by transaction SMSY > Goto > Setup System Landscape Maintenance. Define the same host and port of your SLD and schedule the data transfer.
This should pick up the system once the landscape_fetch background job executes into SMSY.
You can use this approach for all your managed systems and is the most logical way to connect systems to the SLD.
Regards,
-Rohan

Regarding Central SLD and Local SLD

Hello,
Can we maintain Central SLD as well as Local SLD?
We have maintain central sld during installation , now i want to maintain local sld also.
How can we do this? what is the benifit and disadvantage for maintaing both?
Regards,
V.Singh

Hi V.Singh
You can have as many SLD as you like - the service is available as part of a WAS JAVA install
Bear in mind the more SLD = the more administration and if you wish to sync them there is also many considerations
It is best you check the SLD planning guide at System Landscape Directory (SLD) to select the landscape that
best suits the intend use
The Central SLD concept is primarily to have an SLD containing all systems in your company i.e complete overview - this might not be specifically used for runtime of these systems - say PI useage etc - it might be used to populate Solution Manager with landscape data or just track all systems and changes in the organization
The central SLD concept is also not essential however an SLD (a local or app specific one) is essential for certain applications like PI, ESS etc
Best wishes
Stuart

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

PI 7.1: Central vs. local SLD

We are in the process of setting up a PI 7.1. Our landscape has a central SLD (standalone on 7.00 without any other applications on it).
The PI installation guides recommends to use the local SLD that is synchronized with the central SLD instead of using the central SLD directly.
I remember from some time ago - where we tried to get a synchronization running - that is was not that "easy" and difficult to troubleshoot.
I'm not yet convinced to set up a separate SLD (or more than one for DEV, QA and PRD) instead of having one SLD in the landscape.
Are there any known implications (aside from the inability to use the CTC during setup) when we use an SLD of 7.00 together with a PI 7.1?
Markus

Holà Henrique,
gracias!
We don't use a "classical" cluster scenario but virtualized using Solaris zones (as failover cluster only, not with two nodes).
My question was more regarding functionality with scenarios - are the implications or any known no-go's for running a PI 7.1 against an SLD 7.00? If the SLD is "just" the storage for Technical and business systems and JCos for WD-Java, then it should work
Markus

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

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

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.

How to sync local SLDs to Central SLD.

Hi,
Suppose i have a central SLD system A. and several local SLD system B, C, D...
i want to sync all thoese local SLD information into the central SLD. But i don't know how to create data suppliers and corresponding configuration.
Who can give me some steps about how to do it.
Thanks,
Johnney.

hi Johney..
Check this links..
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/29b1f3ea-0c01-0010-2dae-cc64bb381c97
http://help.sap.com/saphelp_nw04s/helpdata/en/44/7716e1633a12d1e10000000a422035/content.htm
http://www.informatik.uni-hamburg.de/SWT/attachments/LVTermine/TheJavaDevelopmentInfrastructure-Part2-AutomatedBuildandChangeManagement.pdf
URs GS

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

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

Local SLD and Central SLD

Similar Messages

Maybe you are looking for