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.

Similar Messages

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

Switching from local to central SLD

I installed the ESS business package with a local SLD. Now there is another SLD server we need to use (a central SLD instance). Can we switch easily from an existing local SLD instance to a remote SLD instance?
Tiberiu

Hi Tiberiu,
It's a while since this message was created. Have you solved your problem? I have our SLD's set slightly differently to the suggestion made earlier, although I would say that I'm an expert in this area. For dual stacks I have the CIM.... tab pointing at itself and the HTTP tab pointing at the central SLD. This seems to work for us in all cases where there is a dual stack. We are having a few issues in java only systems which we are trying to solve. At present both tabs point to the central SLD and "seem" to be working!!
Regards,
Paul

SRM SWCV not geting synched up in CMS from Central SLD

Hi,
We set up SRM SWCV in Central SLD and using that in Dev system.
We want to transport this SWCV from Dev to QA using CMS.When we are trying to do this transport we are getting error and the reason is there is no entry of SRM stuff in CMS.
Our CMS is pointing to Central SLD and when we are trying to Update CMS it is pulling all other SWCV s from Central SLD except SRM stuff..So we couldn't add SRM SWCV in CMS...
So,please let us know what we are doing wrong...or Should we approach differently to load SRM content in QA systems..
Thanks in advance
Venu

Yes Venu,
You need to import SRM Content into QA syste.
DO NOT TRANSPORT CONTENTS....!
Thanks

Central sld problems ?

Hi Guys,
The scenario is like this.
1. Central SLD installed on solution manager
2. We are trying to connect an XI BOX to this central SLD.
Steps did in XI BOX:
1. SLDAPICUST - points to SLD host.
2. Exchange Profile - values set for Connections like cr.name and landscape.name.
3. SLD Data supplier - in visadm - points to Central SLD - due to this, The Java stack of XIBOX is listed as a technical system in central SLD and data collection works correctly.
3. JcoRfc Destination - LCRSAPRFC_XIBOX - program id registerd in visadm with gateway host and service as XIBOX gateway service itself.
Steps did in Central SLD:
1. Jco Rfc Destination - SAPSLDAPI_XIBOX - program id registered in visadm with gateway host and service as that of the XIBOX.
2. SLD Data Supplier - points to sld itself and when data collection is done - sld itself is added as a technical system in SLD.
Problems:
1. IR and ID are not regsitered in SLD under Technical Systems of type Exchange Infrastructure
2. when trying to import the SWCV from the sld getting the message as "unable to read the data from the centralsldhostname:50000"
3. when i do the cache notifications in ID, i am getting the error as unable to determine the central adapter engine.
4. Adapters not listed under adapter monitoring
5 when i go the administration cache overview, i am not seeing the adapter meta data like af.server
checked the settings according to 720717, 768148, 939592.
any help would be really appreciated
Thanks,
Srini

Hi Agasthuri,
I dont have any issues with the SLDCHECK and it works fine. I have already done the reimporting of the basis component.
Thanks,
Srini
Edited by: srinivas kapu on Jan 29, 2008 2:32 PM

Unable to import the SWCV fom the central sld ?

Hi Guys,
I have connfigured xi for central sld
and when i try to import the swcv from central sld i am getting the message as unable to read the data from the <hostname> : port number
I have given the following in the exchange profile
com.sap.aii.connect.cr.name -- central sld host name
com.sap.aii.connect.directory.name -- sap xi host name
can anybody tell me the values for the above parameters and any help would be really appreciated
LCRSAPRFC and SAPSLDAPI are on the xi server and works fine.
Thanks,
Srini

Hi Sridhar,
LCRSAPRFC - poinitng to SAP XI server Gatewayhost and Gateway service -- works fine
SAPSLDAPI - pointing to SOLMANGR Gatewayhost and Gateway service -- works fine
I am maintaining the Hostname of the solmagr in SLDAPICUST. can you explain little bit more on the url in sldapicust.
Do you mean i need to give http://hostname:port/sld instaed of just the host name ?
Thanks,
Srini

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

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

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

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

Problem with SLD and Creation of JCo

Hello everyone!
I have a problem with the SLD and the Creation of JCo on the Portal, in trying to create the JCo always tells me that the name used there in the SLD, being that the facility is new.
Who performs the installation, set in the SLD the ECC 6 PRD, delete it to see if I could create a JCo but still the error again when creating the ECC 6 PRD in the SLD I said that already exists and can not create it.
I found a forum which recommended re-import the cimsap .... .... zip and zip CR_Content which would clean everything, I managed to import the zip cimsap ... but in trying to raise CR_Content gives me the following message "All incremental updates of the selected aggregate import for export SAP_CR line have already been loaded before. You require a newer import to update your current content SAP_CR version 4.11." .
I recommend, do the installation again, reload the cimsap.zip and CR_Content.zip a copy homogeneous.
from already thank you very much
Text of error to create JCo destination
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   java.lang.NullPointerException
    at at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
    at at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
    at at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionGoForward(ButtonBar.java:505)
    at at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:280)
    at at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
    ... 28 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; InfoPath.1)
Version null
DOM version null
Client Type msie7
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0017.20081210091801.0000 (release=NW04S_17_REL, buildtime=2009-01-12:09:43:27[UTC], changelist=52884, host=pwdfm114), build date: Tue Apr 28 19:28:39 CLT 2009
J2EE Engine 7.00 patchlevel 48199.450
Java VM IBM J9SE VM, version:2.2, vendor: IBM Corporation
Operating system Linux, version: 2.6.18-92.el5, architecture: amd64
Session & Other
Session Locale en
Time of Failure Fri Aug 28 11:43:53 CLT 2009 (Java Time: 1251474233677)
Web Dynpro Code Generation Infos
sap.com/tcwdtools
No information available null
sap.com/tcwddispwda
No information available null
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
java.lang.NullPointerException
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
     at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
     at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionGoForward(ButtonBar.java:505)
     at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:280)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:207)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Hello!!
The "SLD" with which I am working up to Portal, the "ECC" installs itself as "ABAP.
Who did the installation and initial configuration, do not leave any documentation about it.
Now I need to create the systems and "JCo" necessary to enable them to implement the "ESS", but errors are presented above.
Some days ago I managed to update the CR_Content, which allowed me to create the "JCo" but at the time of the test, says' com.sap.mw.jco.JCO $ Exception: (103) RFC_ERROR_LOGON_FAILURE "name or password incorrect .
I managed to also create the portal systems, "System Administration -> System Configuration -> Content Portal" and to test it fails on "Test Connection with Connector", which as noted is associated with the connectors "JCo".
For the creation of the system, I think I should create something in the Visual Administrator ", but within the documentation that I do not see anything about it.
thanks for your help!

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

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?
Under Component monitoring -> Integration server -> Adapter Engine
and it has show all the adapters when we install central AE and with central SLD when we furthur click the show all adapters?
As i mentioned above, u may view all the adapters after clicking
Adapter Engine -> Adapter Monitoring
or is it changed since PI 7.0 to cummunication channel monitoring and no adapter monitoring?
Yes. Now the monitoring of adapters r much intensively done by Communication Channel Monitoring
Regards,
Prateek

Central SLD and Webdynpro

Similar Messages

Maybe you are looking for