problem about SLD

[Former Member]

Hi, everyone, help please,

I have meet a problem about SLD when I monitor components in RWB using browser.

It says 'Error during communication with System Landscape Directory: HTTP response code: 404(Not found)',

Stack trace for the above error message is:

com.sap.aii.rwb.exception.BuildLandscapeException: Error during communication with System Landscape Directory: HTTP response code: 404 (Not found)

at com.sap.aii.rwb.agent.server.SLDAgentBean.convertException(SLDAgentBean.java:1472)

........

The system is regular before, I meet the problem after my vacation.

I restart the system several times, but the problem remains.

Thanks in advance, your effort will be appreciated !!

[Former Member]

Hi,

I think you can try the below options:

1. Peform SLDCHECK and check if everything is fine. You would get more details on the issue there.

2. 404 error could be due to mainly due to authentication issues. Check if the user ID and password are correctly configured for the SLD setup.

3. Check if there are any changes made to the SLD recently, like change of settings, pointer settings etc.

4. Check if all the required services are active in the transaction SICF.

Please try the above options and update accordingly.

Regards,

Subbu

[former_member472138]

Here is your solution.

Check the following:

 Check the outbound binding of the message in transaction SXMB_MONI

 Find the party/communication component/channel the message is sent to in the tags SAP:PartyName, SAP:ServiceName, SAP:ChannelName

 Find this channel in the Integration Directory and check which Adapter Engine is used  central Adapter Engine or af.<sid>.<host>

 Call transaction SXI_CACHE and choose Goto  Adapter Engine Cache

 Check the URL for the Adapter Engine (CA stands for the Integration Server u2013 central Adapter Engine), for example

https://server:J2EE-port/MessagingSystem/receive/AFW/XI

 Try to execute the URL in the browser using the user XIISUSER/PIISUSER(name as set during installation).

o The specified path cannot be found using the server:port

o Check that the port really is the ICM HTTP port (transaction SMICM) and not the Java port.

o If the port is wrong, change the pipeline URL in the SLD in the business system of the Integration Server.

o Restart the Java Engine to reset the SLD buffer of the Adapter Engine.

Regards

Pothana

[Former Member]

I meet the problem after login RWB sucessfully using PISUPER. The problem occurs when I click 'Display' button under 'Component Monitoring', so I think it is not authority issue. I have executed SLDCHECK, everything is fine, and performed chache delta refresh, cache is up to date.

Edited by: Donnie126 on Jul 5, 2011 3:08 AM

[Former Member]

Hi,

Can you please check the parameters maintained in your exchange profile, specially under the Runtime tab.

Go to your XI home page --> Administration --> you will find a link called EXCHANGE PROFILE On the Right Had side for your IR , ID and RWB . You can edit the values of the exchange profile here

Refer the below links for the exchange profile parameters

http://help.sap.com/saphelp_nw2004s/helpdata/en/ea/f02840d89d185de10000000a1550b0/content.htm

http://help.sap.com/saphelp_nw70/helpdata/en/c6/6f1741b393f26fe10000000a1550b0/frameset.htm

Regards

[naveen_chichili]

Try by providing fully qualified domain name in your url

Regards,

Naveen

[Former Member]

yes, I give it fully qualified domain name , but it doesn't take effect. The following is the issue detail.

when I click 'Message Monitoring' from http://<host>:5<sys#>00/rwb, the error ocurs. It says:

Following error occurred while executing the application:

Error during communication with System Landscape Directory: HTTP response code: 404 (Not found)

Stack trace for the above error message is:

com.sap.aii.rwb.exceptions.BuildLandscapeException: Error during communication with System Landscape Directory: HTTP response code: 404 (Not found)

at com.sap.aii.rwb.agent.server.SLDAgentBean.convertException(SLDAgentBean.java:1472)

at com.sap.aii.rwb.agent.server.SLDAgentBean.buildSLD(SLDAgentBean.java:773)

at com.sap.aii.rwb.agent.server.SLDAgentBean.provideSld(SLDAgentBean.java:269)

at com.sap.aii.rwb.agent.server.SLDAgentBean.getXIDomain(SLDAgentBean.java:711)

at com.sap.aii.rwb.agent.api.SLDAgentObjectImpl0.getXIDomain(SLDAgentObjectImpl0.java:375)

at com.sap.aii.rwb.agent.api.SLDAgent_Stub.getXIDomain(SLDAgent_Stub.java:436)

at com.sap.aii.rwb.agent.client.EJBAgent.getXIDomain(EJBAgent.java:255)

at com.sap.aii.rwb.util.web.model.AppMainModel.getSelectedDomain(AppMainModel.java:137)

at com.sap.aii.rwb.util.web.model.DomainRep.build(DomainRep.java:100)

at com.sap.aii.mdt.util.MmMainModel.getMsgCompList(MmMainModel.java:262)

at com.sap.aii.mdt.util.MmMainModel.getListModel(MmMainModel.java:244)

at com.sap.aii.mdt.util.SelectModel.getListModel(SelectModel.java:132)

at jsp_monitor_new1310051169453._jspService(jsp_monitor_new1310051169453.java:177)

at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)

at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:68)

at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:427)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:358)

at com.sap.aii.rwb.web.messagemonitoring.viewcontroller.MmDynPage.doProcessBeforeOutput(MmDynPage.java:69)

at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:123)

at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)

at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)

at jsp_FC_Secure1310051167796._jspService(jsp_FC_Secure1310051167796.java:24)

at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)

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)

[Former Member]

where can I find the application ? from SICF ? Provided it is, which one is the right application(detail path)?

thanks for everyone.

[Former Member]

Hi,

"Error during communication with System Landscape Directory: HTTP response code: 404 (Not found)".

Your application is nothing but your "RWB Application Component of PI"

I guess this is the connection issue between RWB and SLD, where RWB is unable to find (Not found) the defined SLD Host.

So Please check following:

1. Open SLD from Integration Builder Home Page. Check the correct SLD Server Host Name under SLD Administration page.

2. See whether same Host name is maintained in Exchange Profile -- SLD Parameters.

Regards

Praveen K

[Former Member]

The problem is solved. The hosts file is changed because some reason.

Thanks for everyone!

Edited by: Donnie126 on Jul 13, 2011 4:17 AM