Installation SLD

Hi,
in our current project we will use XI (DEV, QA, PROD).
SAP recommended to use one SLD that contains all system landscapes.
On which XI system we have to install the SLD (DEV, QA or PROD)?
Whats your experience or your recommendation?
Thanks in advance.
Regards
Lutz

HI,
Refer the below weblog for SLD:
SLD preperation very good:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/flatFILETOFLATFILE&
Working with System Landscape Directory (SLD) :
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/workingwithSystemLandscapeDirectory+%28SLD%29&
Configuring SLD in Sneak Preview SAP NetWeaver '04 Sneak:
/people/sugree.phatanapherom/blog/2005/08/14/configuring-sld-in-sneak-preview-sap-netweaver-04-sneak
XI Software Logistics 1: SLD Preparation:
/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
Once you have created SLD in Dev below transport mechanism is used for transporting the obj from DEV to QA and PROD:
Transport mechanism
1. Create Technical System and Business Systems for the QA system.
2. Create Transport Groups in the Business System.
3. Create Transport Targets in the Source Business SYstem.
Check the link for:
Configuring Transport Groups and Tranport Targets
http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm
Your SWCV can be exported and imported using TPZ files into the IR.
The ID also use TPZ files and as the objects are imported , the business system details will be filled up .
Refer How to handle SLD guide for help:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
Look at the below weblog for XI transports.
/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
Thnx
Chirag Gohil

Similar Messages

XI Post Installation - SLD Connection

Hi, I'm following the XI 3.0 post-installation guide. In the step "Maintaining SLD Connection Parameters" I call transaction SLDAPICUST and try to insert a row as described in the guide.
The problem occurs in the password column which is not editable.
Am I missing something?
Thanks
Juan Manuel

Juan, I had the same problem. I was using the Java GUI 6.40R2 and the Password popup does not work. I switched to use the Windows GUI and the password popup came up, I entered the password and all is OK. I went back to the Java GUI and clicked on Password field and the popup is working now - go figure??

Template Installer SLD Local only

I have installed EP and have not configured SLD. I went to the NWA url and noticed a meesage stating Local SLD can only be configured (or something like that).
Can I run the template installer for NWA Configure SLD to point to the central SLD? If not what do I have to do to point to a central SLD.
Thanks
Mikie

Hi,
See this
Note 939592 - PI Usage Configuration versus Central SLD
You can run Template installer for NWA to configure SLD to point Central SLD, but there are constraints.
923359 - Collective Note: Template Installer (CTC)
Br,
Amit Lal
Reward pts if suitable answer.

Problem during installation. sld registration

Hello,
I'm installing a SAP ERP 2005 system. The installation is stopped when sapinst try to register the system in the SLD. (SLD on solution manager 4.0).
Here is the errors from the log:
FRF-0007 (Unable to open RFC connection)
MUT-03025 (Name or password is incorrect).
Connection to http://hostname:50000/sld/admin with user J2EE_ADMIN is ok.
Any ideas?
Does problem come from a bad password entered in sapinst at the beginning?
Could anyone tell me how to force sapinst to enter new sld informations again without restarting all the installation? Note that I've exactly the same problem with another similar installation which also use the same SLD.
Many thanks for your support!
Vanderperre Olivier

My problem is solved!
Sapinst tried to execute the RFC connexion with DDIC on client 300 witch was empty at this moment. I changed to use 001 and the installation finished successfully.
Best Regards,
Vanderperre Olivier

Problem in XI after post installation.

I have done the post installation for PI, everything was fine and sucessfull,
but the problem is, in XI check list there is no objects found in the Integration Repository and Integration Directory with the URL ( http:
emsap008:50100\rep\start\index.asp ).
Let me explain the problem which i faced.
In the transaction SXMB_IFR --> Tool --> Import Design Objects Option, the result displaied is " There is no Objects found ". But as per the document i need to get " PI7_0_BASIS_6.40_18_00.tpz ".
Please clarify my doubt, ask me if my question is insuffecient.

Hi Senthil !!
Here is the guide with necessary steps
http://help.sap.com/bp_bpmv130/Documentation/Installation/XI30InstallGuide.pdf
/people/sravya.talanki2/blog/2006/11/15/post-installation-steps-for-activating-adobe-document-services-in-sap-xi-nw-2004s
You will get the details of post installation activities for SAP XI in its installation guides itself. Have a look:
SAP Exchange Infrastructure Release 3.0 - Installation Guide
SAP Exchange Infrastructure 3.0 SR1 - Installation Guide
Plus you can go through the following docs:
SAP Exchange Infrastructure (XI) 3.0
Troubleshooting Guide - SAP XI 3.0 and 2.0
SAP XI Release 3.0 SPS11Configuration Guide
Also you can have a look at the following thread, you will get some links in these threads too:
Post installation of XI?
XI INSTALLATION and POSTINSTALLATION
XI Post Installation....Need help...
XI Post Installation - Help
XI Post Installation - SLD Connection
refre this thread
Post Installation of PI - PI template Installer not found
Pls rewards if useful

Post installation for XI

Hi All,
I have installed ECC 6.0. I have added XI component also. Now i need to perform post installation steps for XI alone. i have downloaded the NW7 installation Guide MAXDB. is that enough? or should i need more documents....
Also, i found out a document for post installation guide system landscape directory of SAP Netweaver 7.0....
Which one should i follow?
Please clarify....
Thanks in advance,
Madhukar

Hi madhukar !!
Is this what you are looking for:
https://websmp103.sap-ag.de/~sapidb/011000358700001697502004E.PDF
Also check this thread..
Re: XI INSTALLATION and POSTINSTALLATION
those describe din XI installation and configuration guides:
http://help.sap.com/bp_bpmv130/Documentation/Installation/XI30InstallGuide.pdf
http://help.sap.com/bp_bpmv130/Documentation/Installation/Configuration_Guide_FP.pdf
check this thread for SLD configuration soon after XI installation
SLD configuration
Check this link also it has the procedure.
http://help.sap.com/saphelp_nw2004s/helpdata/en/78/20244134a56532e10000000a1550b0/frameset.htm
Here is the guide with necessary steps
http://help.sap.com/bp_bpmv130/Documentation/Installation/XI30InstallGuide.pdf
/people/sravya.talanki2/blog/2006/11/15/post-installation-steps-for-activating-adobe-document-services-in-sap-xi-nw-2004s
You will get the details of post installation activities for SAP XI in its installation guides itself. Have a look:
SAP Exchange Infrastructure Release 3.0 - Installation Guide
SAP Exchange Infrastructure 3.0 SR1 - Installation Guide
Plus you can go through the following docs:
SAP Exchange Infrastructure (XI) 3.0
Troubleshooting Guide - SAP XI 3.0 and 2.0
SAP XI Release 3.0 SPS11Configuration Guide
Also you can have a look at the following thread, you will get some links in these threads too:
Post installation of XI?
XI INSTALLATION and POSTINSTALLATION
XI Post Installation....Need help...
XI Post Installation - Help
XI Post Installation - SLD Connection
Post Installation of PI - PI template Installer not found
Pls reward if useful

Self registration of the java engine in central sld

hi all,
iam installing solution manager on windows2003, with maxdb..
i have two options one is .1) register in existing sld
and the other is 2) configure local sld
so i chose the 1st one.
need to know how to register it like sld host name, sld port and so on...
Thank you,
ravi.

Hi,
For SLD configuration during installation,
SLD HTTP HOST - can be any name need not be your computer name. E.g <SID>SLD or <SID>SLDSRV or something like that.
SLD HTTP PORT - the port would be 50<instancenumber>00
eg:- 500100 where 01 is instance number.
as SLDDATA SUPPLIER USER and SLD ABAP API USER are automatically populated. just maintain your password.
That's it.
This will solve your problem. Feel free to revert back.
--Ragu

Instalation help Central SLD parameters connection

Hi Dear All,
I am installing solman 4.0 SR1 on Windows 2003 and Microsoft SQL.
during the instalation i got a screen which iam not aware of please help me
The scren says :
SELF REGISTRATION OF JAVA ENGINE in CENTRAL SLD:
SLD HTTP HOST -
SLD HTTP PORT -
SLDDATA SUPPLIER USER: SLDDSUSER
PASSWORD:
SELF REGISTRATION OF ABAP ENGINE IN CENTRAL SLD
SLD GATEWAY HOST: -
SLD GATEWAY INSTANCE NUMBER: -
COMMUNICATION WITH CENTRAL SLD:
SLD ABAP API USER: SLDAPIUSER
PASSWORD:
Please help what i have to choose and where i can find the relavent information.
kind regards,
Vamsi.

Hi,
For SLD configuration during installation,
SLD HTTP HOST - can be any name need not be your computer name. E.g <SID>SLD or <SID>SLDSRV or something like that.
SLD HTTP PORT - the port would be 50<instancenumber>00
eg:- 500100 where 01 is instance number.
as SLDDATA SUPPLIER USER and SLD ABAP API USER are automatically populated. just maintain your password.
That's it.
This will solve your problem. Feel free to revert back.
--Ragu

Hello installed xi and trying 2 do post installation but getting problem

Hello,
 I installed SAP XI and trying to do the post installation...
 1)Created one client 100 and user XIUSER....with all rights like sap_all
 2)And created one more user XISUPER......only roles given...
 3)now I am trying with internet expositor
 http://application server:java port/exchangeProfile
 screen came user:xisuper
 p/w: 12345
 BUT IS NOT GOING FORWRD....WHAT MIGHT BE THE PROBLEM..... TRY TO GIVE ME THE SUGGESTION....
Regards,
Sateesh.j

Hi !!!
Here is the guide with necessary steps
http://help.sap.com/bp_bpmv130/Documentation/Installation/XI30InstallGuide.pdf
/people/sravya.talanki2/blog/2006/11/15/post-installation-steps-for-activating-adobe-document-services-in-sap-xi-nw-2004s
You will get the details of post installation activities for SAP XI in its installation guides itself. Have a look:
SAP Exchange Infrastructure Release 3.0 - Installation Guide
SAP Exchange Infrastructure 3.0 SR1 - Installation Guide
Plus you can go through the following docs:
SAP Exchange Infrastructure (XI) 3.0
Troubleshooting Guide - SAP XI 3.0 and 2.0
SAP XI Release 3.0 SPS11Configuration Guide
Also you can have a look at the following thread, you will get some links in these threads too:
Post installation of XI?
XI INSTALLATION and POSTINSTALLATION
XI Post Installation....Need help...
XI Post Installation - Help
XI Post Installation - SLD Connection
refre this thread
Post Installation of PI - PI template Installer not found
just check also have you done this step ?
This step is not covered by the PI template.
You need these files The files SCM4003_00.ZIP and SCMBASIS4003_00.ZIP
Further reference
http://help.sap.com/saphelp_nw04s/helpdata/en/44/5755451622311ee10000000a155369/content.htm
Another thing are the j2ee adapters and the adapter engine visible in the ID just check once. If not then go through these.
1)Yeap you need the basis component imported first.
2) Apply SAP Note 764176.
3. /people/venugopalarao.immadisetty/blog/2007/03/15/adapter-engine-cannot-be-found-in-integration-directory
pls reward if useful

Possible to migrate installation w/ SLD to new system using 'tar'/'untar'?

I have a CRM installation with TREX, that I need to move from one unix system to another (same patch level). As SLD is setup, can I 'tar' the entire installation on the old system, 'untar' the bundle on the new system, and bring the SAP setup back into function mode? It should be doable if SLD is not setup. But since there is SLD bundled in the setup, I am not sure if 'tar' is the way to port the installation. I can give the new system the same hostname, but ip address would be different. Any pointer is highly appreciated! Many Thanks!

Hi,
You can perform asystem copy, even SLD can be set up later accroding to your need.
Regards,
Vamshi.

Error during installation of a new SLD

Hello people,
During installation of a new SLD I got different kind of errors in the Log. Does anyone has a suggestion what to do?
#79 09/10/2007 14:04:01.536 [Thread-74] INFO com.sap.lcr.pers.delta.importing.ImportHandler: Finished full import into namespace sld/active: More...
#78 09/10/2007 14:04:01.528 [Thread-74] INFO com.sap.lcr.pers.jdbc.JdbcPersistence: Deleted namespace: sld/import/temp0 (Duration: 46 ms)
#24 09/10/2007 13:34:57.879 [Thread-74] INFO com.sap.lcr.pers.delta.importing.ObjectLoader: The following errors occurred during the import: More...
#23 09/10/2007 13:34:23.46 [Thread-74] INFO com.sap.lcr.pers.delta.importing.ObjectLoader: The following errors occurred during the import: More...
#22 09/10/2007 13:33:46.802 [Thread-74] INFO com.sap.lcr.pers.delta.importing.ObjectLoader: The following errors occurred during the import: More...
#21 09/10/2007 13:33:15.571 [Thread-74] INFO com.sap.lcr.pers.delta.importing.ObjectLoader: The following errors occurred during the import: More...
#20 09/10/2007 13:32:49.979 [Thread-74] INFO com.sap.lcr.pers.delta.importing.ObjectLoader: The following errors occurred during the import: More...
#19 09/10/2007 13:32:20.687 [Thread-74] INFO com.sap.lcr.pers.delta.importing.ObjectLoader: The following errors occurred during the import: More...
#18 09/10/2007 13:31:50.255 [Thread-74] INFO com.sap.lcr.pers.delta.importing.ObjectLoader: The following errors occurred during the import: More...
#17 09/10/2007 13:31:26.370 [Thread-74] INFO com.sap.lcr.pers.delta.importing.ObjectLoader: The following errors occurred during the import: More...
#16 09/10/2007 13:30:58.647 [Thread-74] INFO com.sap.lcr.pers.delta.importing.ObjectLoader: The following errors occurred during the import: More...
#15 09/10/2007 13:30:28.281 [Thread-74] INFO com.sap.lcr.pers.delta.importing.ObjectLoader: The following errors occurred during the import: More...
#14 09/10/2007 13:15:05.378 [Thread-74] INFO com.sap.lcr.pers.jdbc.JdbcPersistence: Deleted namespace: sld/import/temp0 (Duration: 113 ms)
#13 09/10/2007 12:55:39.244 [SAPEngine_Application_Thread[impl:3]_27] INFO com.sap.lcr.pers.jdbc.JdbcPersistence: Deleted namespace: sld/import/temp0 (Duration: 40 ms)
#12 09/10/2007 12:54:35.280 [SAPEngine_Application_Thread[impl:3]_17] WARNING com.sap.lcr.jsp.importWarning: The following warning has been reported by import precondition checks, user decision required: More...
#11 09/10/2007 12:54:35.270 [SAPEngine_Application_Thread[impl:3]_17] INFO com.sap.lcr.pers.jdbc.JdbcPersistence: Deleted namespace: sld/import/temp0 (Duration: 39 ms)
#10 09/10/2007 12:48:12.210 [Thread-72] INFO com.sap.lcr.pers.delta.importing.ImportHandler: Finished full import into namespace sld/active: More...
#9 09/10/2007 12:48:12.189 [Thread-72] INFO com.sap.lcr.pers.jdbc.JdbcPersistence: Deleted namespace: sld/import/temp0 (Duration: 46 ms)
#8 09/10/2007 12:19:40.871 [Thread-72] INFO com.sap.lcr.pers.jdbc.JdbcPersistence: Deleted namespace: sld/import/temp0 (Duration: 89 ms)
#7 09/10/2007 12:19:29.549 [SAPEngine_Application_Thread[impl:3]_37] WARNING com.sap.lcr.jsp.importWarning: The following warning has been reported by import precondition checks, user decision required: More...
#6 09/10/2007 12:19:29.400 [SAPEngine_Application_Thread[impl:3]_37] INFO com.sap.lcr.pers.jdbc.JdbcPersistence: Deleted namespace: sld/import/temp0 (Duration: 377 ms)
#5 09/10/2007 12:17:44.796 [SAPEngine_Application_Thread[impl:3]_17] WARNING com.sap.lcr.jsp.importWarning: The following warning has been reported by import precondition checks, user decision required: More...
#4 09/10/2007 12:17:44.698 [SAPEngine_Application_Thread[impl:3]_17] INFO com.sap.lcr.pers.jdbc.JdbcPersistence: Deleted namespace: sld/import/temp0 (Duration: 1,929 ms)
#3 09/10/2007 12:14:48.156 [SAPEngine_Application_Thread[impl:3]_0] INFO com.sap.sld.api.builder.app.DefineHostedSystem: JDI system SLD jct11 on T11 on dbt11-se written to SLD at jct11:53300.
#2 09/10/2007 12:14:47.392 [SAPEngine_Application_Thread[impl:3]_0] INFO com.sap.lcr.start.StartDirector: SLD application started successfully.
#1 09/10/2007 12:14:35.244 [SAPEngine_Application_Thread[impl:3]_25] INFO com.sap.lcr.start.StartDirector: SLD application stopped successfully.
#0 09/10/2007 08:41:05.852 [SAPEngine_Application_Thread[impl:3]_6] INFO com.sap.lcr.start.StartDirector: SLD application started successfully.
Kind regards,
Kamran
Message was edited by:
Kamran Vakili

Adding more mystery to the distribution kit error discussed above. I have found that the kit installs successfully on Win 7 x64 machines as well as WinXp x32 machines. However, the installation error message still exists on Win 7 x32 machines. On one of these Win 7 x32 machines the error message infers that there is a .dll file that cannot be found, with no mention or hint as to the file's name. Again, any tips would be appreciated.

Error in the post installation steps of SLD .

Hi
We are working on EP7.0 2004s.We are using local sld.Right now I am doing the post installation steps for SLD.I added the J2EE and UME roles.In the next step I went into the administration tab of SLD for configuring.It is throwing this error.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
This is detailed exception I got.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
at com.sap.sld.wd.main.wdp.InternalMainInterfaceView.wdFirePlugToOldUI(InternalMainInterfaceView.java:154)
at com.sap.sld.wd.main.Head.onActionAdministration(Head.java:277)
at com.sap.sld.wd.main.wdp.InternalHead.wdInvokeEventHandler(InternalHead.java:227)
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:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
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:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Please help me.
Thanx & Regards,
Naresh

Hi Naresh,
Can you let me know the service pack for the portal.
Also try login in using administrator using the http://<localhost><port>/sld
thanks
Pankaj

Error in the post installation of SLD .

Hi
 We are working on EP7.0 2004s.We are using local sld.Right now I am doing the post installation steps for SLD.I added the J2EE and UME roles.In the next step I went into the administration tab of SLD for configuring.It is throwing this error.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
This is detailed exception I got.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
 at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
 at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
 at com.sap.sld.wd.main.wdp.InternalMainInterfaceView.wdFirePlugToOldUI(InternalMainInterfaceView.java:154)
 at com.sap.sld.wd.main.Head.onActionAdministration(Head.java:277)
 at com.sap.sld.wd.main.wdp.InternalHead.wdInvokeEventHandler(InternalHead.java:227)
 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:299)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
 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:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 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(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Please help me.
T
hanx & Regards,
Naresh

Hi Naresh
Try logging off from the current window.
and login again as "Administrator" .
use http://portalhostname:50000/sld
hope this helps
Cheers !!!
Satish Kumar.

Webdynpro error in Post installation steps of SLD

Hi
We are working on EP7.0 2004s.We are using local sld.Right now I am doing the post installation steps for SLD.I added the J2EE and UME roles.In the next step I went into the administration tab of SLD for configuring.It is throwing this error.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
This is detailed exception I got.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
at com.sap.sld.wd.main.wdp.InternalMainInterfaceView.wdFirePlugToOldUI(InternalMainInterfaceView.java:154)
at com.sap.sld.wd.main.Head.onActionAdministration(Head.java:277)
at com.sap.sld.wd.main.wdp.InternalHead.wdInvokeEventHandler(InternalHead.java:227)
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:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
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:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Please help me.
Thanx & Regards,
Naresh

Hey Aviad,
Yes I did, in my case I've installed PDK SP 9 over SP2 which is prohibited. If this is your case as well do the following:
1) From the Undeployment tab of the SDM select the com.sap.pct.pdk..
components.
2) Using the Archive remover tool which can be accessed from
System Administration > Support > Portal Runtime > Administration
Console > Archive Remover --> Remove the portal applications with prefixcom.sap.pct.pdk...
3) Navigate to Content Administration > Portal content > Content
Provided by SAP > Platform Add-Ons > Developer Content
and remove all the contents below this folder.
4) Restart the server
After this you can deploy the SP9 business package using the SDM.
Hope it helps,
Roy

XI installation with central SLD

Hello,
I have installed solution manger to generate key for XI installation. But, when i in stall solution manager, it installed MaxDB and local SLD and also i think WEBAS ABAP. After that i generated the key.
And, I am installing XI on the same host. There is no configuration as such i did.I tried to use the same solution manger DB, but i t failed. So i started with New DB creation. And central SLD........
Is there any configurations that i need to do to install XI with our any errors.
When i used existing SLD, is there any configuration i have to do.
More important, i have to install solution manager and XI on same host
Can anybody any issues here.
Please advice,
Srini

This should be straight forward.
If the SLD is set up for Sol Man, you enter these details on the in the installation wizard.
You will need seperate SIDs and you will need to assign the Virtual host names for each installation.
You will need to check the SLD config after install. the two sm59 conenctions - LCRSAPRFC & SAPSLDAPI, the sldapicust, the JCo Connections in Visual Admin and the SLD Data Supplier in Visual ADmin.

Installation SLD

Similar Messages

Maybe you are looking for