cancel
Showing results for 
Search instead for 
Did you mean: 

SAP BOXIR4 Webservices SDK Login issues

Former Member
0 Kudos

Hi,

I am able to login successfully into R4 environment using BO Enterprise SDK. However, I am facing issues while trying to login using R4 Webservices SDK’s on R4 environment. But if I use the R3 Webservices SDK’s, I am able to successfully login into R4 environment without changing code.

After analyzing further, I found that there could be some issues with the following R4 jar files.

axiom-api-1.2.13.jar

axiom-impl-1.2.13.jar

dsws-session.jar

Stack Trace:

login The exception is of a known origin. (Error: WSE 99999) S2login The exception is of a known origin. (Error: WSE 99999)session.dsws.businessobjects.com/loginjava.lang.NoSuchMethodErrororg/apache/axiom/om/OMXMLBuilderFactory.createOMBuilder(Ljavax/xml/transform/Source;)Lorg/apache/axiom/om/OMXMLParserWrapper;java.lang.NoSuchMethodError: org/apache/axiom/om/OMXMLBuilderFactory.createOMBuilder(Ljavax/xml/transform/Source;)Lorg/apache/axiom/om/OMXMLParserWrapper; at com.businessobjects.dsws.session.SessionStub.toOM(SessionStub.java:4256) at com.businessobjects.dsws.session.SessionStub.toOM(SessionStub.java:4244) at com.businessobjects.dsws.session.SessionStub.toEnvelope(SessionStub.java:4496) at com.businessobjects.dsws.session.SessionStub.login(SessionStub.java:3053) at com.businessobjects.dsws.session.Session.login(Session.java:439) at com.ibm._jsp._login._jspService(_login.java:169) at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:99) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1224) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:774) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:456) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:122) at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:216) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1032) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3748) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:962) at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:459) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:526) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:312) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:283) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1814)

After reading the AXIOM documentation from the below link, I could understand that OMXMLBuilderFactory class has been moved into a different package and I am not sure SessionStub class from BO Webservices (dsws-session.jar) is referring the right package.

http://ws.apache.org/axiom/userguide/ch04.html#changes-1.2.11

P/s: This AXIOM change is reflecting in R4 version of Webservices SDK’s and hence we don’t have any issues with R3 Webservices SDK’s.

Can I get some solution/work around on this?

Thanks,

Jinesh

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Jinesh,

Can you give more details about the BO product Version?

Also which application server you are using to deploy your application?

Is it websphere?

Try to give preferrence to the application jars over the application server jars and test the results.

-Prithvi

Former Member
0 Kudos

Hi Prithvi,

  I am using BOXI 4.1 jars and the jars version were mentioned in my original post. I am using Websphere Application server 8.5 and I am already giving the preference in the project build path to the BOXI R4 jars which I copied from the installation folder. I did a simple test by replacing the R4 webservices SDK jars with R3 webservices SDK jars which is perfectly working fine and able to login into R4 environment.

Thanks,

Jinesh

Former Member
0 Kudos

Hi Prithvi,

  Do you have any updates on this?

Thanks,

Jinesh

Former Member
0 Kudos

Hi Jinesh,

Sorry for not able to reply as was not following the forums.

Please refer to SAP Note: 1957639 - Login The exception is of a known origin. (Error: WSE 99999)

Thanks,

Prithvi

Former Member
0 Kudos

I am not able to login into the Market place server with my credentails by clicking the linking which you have provided.

https://websmp230.sap-ag.de/sap/support/notes/1957639

Former Member
0 Kudos

Hi Jinesh,

Please follow the below the below steps.

   

After deployment, modify the application configuration to enable parent last class loading for the Web module. Below are the steps for the same

1. Login to WebSphere admin console.

2. Navigate to Applications-->Application Types-->Websphere enterprise applications.

3. Navigate to the the configuration page for the enterprise application.

4. Click on Manage Modules.

5. Click on application name.

6. Change the class loader order option to Classes loaded with local class loader first (parent last).

7. Re-run the application and you would be able to login.

I have tested it and it has worked for me.

For SAP Note Access, you can login to service market place with your S user ID account and access the Note. Above I have pasted the solution which is same as to SAP Note.

-Prithvi

Former Member
0 Kudos

Hi Prithvi,

  I tried the steps which you have provided and getting the same error.

[7/17/14 10:12:38:558 EDT] 00000061 SystemErr     R org.apache.axis2.AxisFault: constructor The exception is of a known origin. (Error: WSE 99999)

[7/17/14 10:12:38:558 EDT] 00000061 SystemErr     R  at com.businessobjects.dsws.Consumer.CreateAxisFault(Consumer.java:767)

[7/17/14 10:12:38:559 EDT] 00000061 SystemErr     R  at com.businessobjects.dsws.Consumer.propagateAsDSWSException(Consumer.java:859)

[7/17/14 10:12:38:559 EDT] 00000061 SystemErr     R  at com.businessobjects.dsws.Consumer.<init>(Consumer.java:129)

[7/17/14 10:12:38:559 EDT] 00000061 SystemErr     R  at com.businessobjects.dsws.session.Session.<init>(Session.java:145)

[7/17/14 10:12:38:559 EDT] 00000061 SystemErr     R  at com.ibm._jsp._authentication._jspService(_authentication.java:174)

[7/17/14 10:12:38:559 EDT] 00000061 SystemErr     R  at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:99)

[7/17/14 10:12:38:559 EDT] 00000061 SystemErr     R  at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)

[7/17/14 10:12:38:559 EDT] 00000061 SystemErr     R  at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1224)

[7/17/14 10:12:38:559 EDT] 00000061 SystemErr     R  at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:774)

[7/17/14 10:12:38:559 EDT] 00000061 SystemErr     R  at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:456)

[7/17/14 10:12:38:559 EDT] 00000061 SystemErr     R  at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)

[7/17/14 10:12:38:559 EDT] 00000061 SystemErr     R  at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:122)

[7/17/14 10:12:38:559 EDT] 00000061 SystemErr     R  at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:216)

[7/17/14 10:12:38:560 EDT] 00000061 SystemErr     R  at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1032)

[7/17/14 10:12:38:560 EDT] 00000061 SystemErr     R  at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3748)

[7/17/14 10:12:38:560 EDT] 00000061 SystemErr     R  at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)

[7/17/14 10:12:38:560 EDT] 00000061 SystemErr     R  at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:962)

[7/17/14 10:12:38:560 EDT] 00000061 SystemErr     R  at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662)

[7/17/14 10:12:38:560 EDT] 00000061 SystemErr     R  at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195)

[7/17/14 10:12:38:560 EDT] 00000061 SystemErr     R  at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:459)

[7/17/14 10:12:38:560 EDT] 00000061 SystemErr     R  at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:526)

[7/17/14 10:12:38:560 EDT] 00000061 SystemErr     R  at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:312)

[7/17/14 10:12:38:560 EDT] 00000061 SystemErr     R  at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:87)

[7/17/14 10:12:38:560 EDT] 00000061 SystemErr     R  at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)

[7/17/14 10:12:38:560 EDT] 00000061 SystemErr     R  at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)

[7/17/14 10:12:38:560 EDT] 00000061 SystemErr     R  at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)

[7/17/14 10:12:38:561 EDT] 00000061 SystemErr     R  at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)

[7/17/14 10:12:38:561 EDT] 00000061 SystemErr     R  at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)

[7/17/14 10:12:38:561 EDT] 00000061 SystemErr     R  at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)

[7/17/14 10:12:38:561 EDT] 00000061 SystemErr     R  at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)

[7/17/14 10:12:38:561 EDT] 00000061 SystemErr     R  at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1814)

However, If I switch back to R3 jars, its perfectly working fine. Can you please confirm the R4 AXIOM and AXIS jar versions which you are using?

Thanks,

Jinesh

Former Member
0 Kudos

Also, can you list me all the R4 jars with versions to login into R4 environment using webservices SDK? I just want to make sure we both are on the same page.

Thanks,

Jinesh

Former Member
0 Kudos

Hi Prithvi,

   I am able to successfully login now with the Websphere configuration changes as you suggested. Thank you so much for your help.

Thanks,

Jinesh

Answers (0)