~sagar

Its been another work-around and Xen is the opted card I chose to play.

Making a virtualized environment on CentOS-5 [final] linux distro and SAP on top of both.

Happy Xenning around!!!

I was facing an issue with a newly installed SAP-NWSR2:

Lot of search happened over the net and SDN, but real men keep their words.

Installed components are:

PI-EP-BI-Add-Ins[V.7] SP-09, IBM-JAVA-1.4.2|64 bit on a single RH-AS-4 Linux box with Oracle-10g.

I was able to log onto /exchangeProfile and /irj for portal

RWB throws error after loggin:

Following error occurred while executing the application:

Error during communication with System Landscape Directory: HTTP response code: 403 (Forbidden)

Display Stack Trace

Stack trace for the above error message is:

com.sap.aii.rwb.exceptions.BuildLandscapeException: Error during communication with System Landscape Directory: HTTP response code: 403 (Forbidden)
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:876)
at com.sap.aii.rwb.agent.api.SLDAgent_Stub.getXIDomain(SLDAgent_Stub.java:1665)
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.rwb.web.componentmonitoring.model.ObjectIdentificationTree.getComponentTree(ObjectIdentificationTree.java:102)
at jsp_component_monitoring1184877415279._jspService(jsp_component_monitoring1184877415279.java:209)
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.doPost(PageProcessorServlet.java:22)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)
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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at jsp_FC_Secure1184877411979._jspService(jsp_FC_Secure1184877411979.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(AccessController.java:207)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Wait…

Query being processed

The following error code 500 I am getting when I try:

URL:// port/nwa and /sld

500 Internal Server Error Web Dynpro Container/SAP J2EE Engine/6.40 [Why it shows 640 instead 700]
Failed to process request. Please contact your system administrator.

Root Cause
The initial exception that caused the request to fail, was:

java.lang.StringIndexOutOfBoundsException
at at java.lang.String.substring(String.java:1019)
at at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.fillStaticTemplateContext(HtmlClient.java:516)
at at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.sendResponse(HtmlClient.java:1213)
at at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.retrieveData(HtmlClient.java:252)
at at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRetrieveData(WindowPhaseModel.java:595)


Detailed Error Information
Detailed Exception Chain

java.lang.StringIndexOutOfBoundsException
at java.lang.String.substring(String.java:1019)
at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.fillStaticTemplateContext(HtmlClient.java:516)
at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.sendResponse(HtmlClient.java:1213)
at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.retrieveData(HtmlClient.java:252)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRetrieveData(WindowPhaseModel.java:595)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:156)
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.doGet(DispatcherServlet.java:46)
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.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(AccessController.java:207)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

***The other thing I found was:****


dev_jrfc.trc under /usr/sap/LNW/DVEBMGS00/j2ee/cluster/server0


LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner '127.0.0.1:sapgw00' not reached
TIME Fri Jul 20 17:06:34 2007
RELEASE 700
COMPONENT NI (network interface)
VERSION 38
RC -10
MODULE nixxi.cpp
LINE 2764
DETAIL NiPConnect2
SYSTEM CALL connect
ERRNO 111
ERRNO TEXT Connection refused
COUNTER 2
Return code: RFC_FAILURE(1)
error group: 102
key: RFC_ERROR_COMMUNICATION
Error> occured >Fri Jul 20 17:06:35,859< RfcException:
message: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=blxnws00 SYSNR=00 GWHOST=blxnws00 GWSERV=sapgw00 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner 'blxnws00:sapgw00' not reached
TIME Fri Jul 20 17:06:35 2007
RELEASE 700
COMPONENT NI (network interface)
VERSION 38
RC -10
MODULE nixxi.cpp
LINE 2764
DETAIL NiPConnect2
SYSTEM CALL connect
ERRNO 111
ERRNO TEXT Connection refused
COUNTER 2
Return code: RFC_FAILURE(1)
error group: 102
key: RFC_ERROR_COMMUNICATION

In trace file under work DIR:


Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: No such file or directory jar:file:/opt/IBMJava2-amd64-142/jre/lib/ext/ibmjceprovider.jar

I thought; does IBM-Java sucks!!! Nay….

Why the hell… we have gotta the Support Pack; Mr.Luke go ahead with it SP-11 for ALL execept
BW(ABAP) should be 12 [I suggest].

HappY nights and wee hours again… I have gotta some more midnight oil :)

Responding to a lawsuit filed by Oracle earlier this year, SAP admitted on Tuesday that its TomorrowNow division in the U.S. made some “inappropriate downloads” from an Oracle Web site but said SAP never had access to the material.
“Even a single inappropriate download is unacceptable from my perspective,” Kagermann said in a statement: “We regret very much that this occurred.”

The company launched a Web site where it will publish information related to the case, including court filings and a time line of events.