on 03-27-2009 3:50 AM
I uploaded the Apache Axis Adapter as outlined in note 1028961. For SAP PI 7.1. This upload has caused my normal SOAP Adapter to have errors when I select the normal HTTP mode and receiver. When messages are successfully sent out asynch via the soap adapter I am getting the following error in my adapter engine
Message processing failed. Cause: org.apache.axis.ConfigurationException: adapter is null org.apache.axis.ConfigurationException: adapter is null at com.sap.aii.adapter.axis.modules.HandlerCore.process(HandlerCore.java:58) at com.sap.aii.adapter.axis.modules.HandlerBean.process(HandlerBean.java:75) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext
I have verified I setup the sda upload as described in the note above correctly, but I did name it as com.sap.aii.af.axisproviderlib.sda instead of axisproviderlib.sda as I didn't think this would matter.
Has anyone seen this behavior when uploading this fix.
On another note I initially uploaded this for access to create info in the soap header which doesn't seem to work also, but when I check that the sda got uploaded correctly all seems fine.
If anyone has any info I would greatly appreciate it, otherwise we are going to do a restore
Cheers
Devlin
Actually an update the HTTP with AXIS does work fine in sending out requests, but the original HTTP with Message Protocol of of SOAP 1.1 (this is original) doesn't work, it's as if you update the files you can only use the axis version.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was just rereading the instructions and it is named correctly, in the download zip they include an empty .sda file with the name com.sap.aii.af.axisproviderlib.sda
In the instructions it states The included SDA archive may be deployed directly.
Has anyone tried to upload this product, or is there a way to undeploy this without doing a restore?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Devlin,
You wrote something like ,,,,
but I did name it as com.sap.aii.af.axisproviderlib.sda instead of axisproviderlib.sda as I didn't think this would matter.
I think it mattered.
If not revert back the system.
Regards
joel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.