webService not working with new RAM 7.2
Hi I am not able to use the web services provided with the new version of RAM. Earlier with previous version of RAM (7.1.1.1), I was consuming the web services in my web application with out any problem.
Now with the new version, it is giving me SAXException while accessing the search feature. Stacktrace is given at the end.. One thing I noticed - when we generate the client jars from wsdl, it creates jars which have different version from the ones available in ramclient jars.. Please help org.apache.axis.client.Call invoke Exception: org.xml.sax.SAXException: Invalid element in com.ibm.ram.common.data.AssetIdentification - repositoryIdentification at org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258) at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java(Compiled Code)) at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165) at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141) at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236) at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384) at org.apache.axis.client.Call.invoke(Call.java:2467) at org.apache.axis.client.Call.invoke(Call.java:2366) at org.apache.axis.client.Call.invoke(Call.java:1812) at com.ibm.ram.repository.web.ws.core.RAM1SoapBindingStub.search(RAM1SoapBindingStub.java:9059) |
6 answers
Hi,
The web services are internal use only within RAM. They are not supported API and can change at any time. They are different between fixpacks. The official API is RAMClient. That is the supported way to access RAM problematically. Rich |
Hello,
Reiterating Rich's previous message that this is internal API subject to change, it looks like you are not getting back SOAP responses - your client is expecting XML and is getting back some other format (possibly HTML)? Can you please make sure you are pointing to the right endpoint (http://server:port/ram.ws/RAMSecure/services/RAM1), or if you have a firewall, or if you are not connected to the right network, etc. Regards, Srimanth. On 5/20/2010 7:53 AM, jaintjose wrote: Hi I am not able to use the web services provided with the new version |
|
Hi Rich,
Can I use RAMClient within a web application? Also any firewall restrictions will apply?. Infact I tried to use RAMClient as a Java Application and it worked well. I included all jar files in RAMClient.zip in the build path. But when I tried it with a web application(in WAS7.0), it was giving me "Exception created : java.lang.NoClassDefFoundError: com.ibm.ram.repository.web.ws.core.v72.RAM1ServiceLocator" Here also I added all jar files in RAMClient.zip to the BuildPath of Web Application. thanks Hi, |
|
Hi Srimanth,
The service endpoint works fine, means when I am accessing it in browser, "{http://core.ws.web.repository.ram.ibm.com}RAM1 Hi there, this is a Web service!" is coming. Not sure if any other format is returned by the webservice. thanks Hello, Hi I am not able to use the web services provided with the new version |
|
Hi,
If you are in a separate web application from RAM then yes RAMClient will work inside a web application. However you must step up to 7.2.0.2. WAS 7 breaks RAM 7.2 GA. With 7.2.0.2 if you are not using the trial license then you will also require 7.2.0.2's test fix 2. If you are using the trial license then this won't be necessary until you switch to an actual license. Thanks, Rich |
|
Hello,
Though RAMClient will work, it is an internal class and subject to change. If you have access to RAMClient, you should also have access to RAMSession class, and that is the Java API RAM provides. It is highly recommended you use RAMSession for support and code simplicity. Additional documentation about RAMSession can be found in the product's help: http://publib.boulder.ibm.com/infocenter/ramhelp/v7r2m0/index.jsp?topic=/com.ibm.ram.doc/topics/t_using_api.html Regards, Srimanth. On 5/21/2010 4:38 AM, jaintjose wrote: Hi Srimanth, |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.