SAP to SFDC channel error

[viswanahreddy]

Hi Members

SAP --> PI---->SFDC

Recently SFDC test server got refreshed with production from then on wards we are facing issues in PI while connecting the login url (communication channel says "error in response") and they couldnt able to see the login request from SFDC but showing exception as (Exception occurred while retrieving the SFDC Session ID on method 'getSFDCSessionId'.)

Username and pwd is ok and there is no changes and the login URL was working fine (confirmed by SFDC team)

Please suggest me how to proceed further.

In integration engine i could see the error as below.

<Trace level="1" type="T">*** END APPLICATION TRACE ***</Trace>

<Trace level="1" type="T">Java mapping com/aei/sfdc/SFDCRequest has thrown a StreamTransformationException. Thrown: com.sap.aii.mapping.api.StreamTransformationException: Exception occurred on method 'transform'. Exception occurred while retrieving the SFDC Session ID on method 'getSFDCSessionId'. java.lang.RuntimeException: Namespace for prefix 'xsi' has not been declared. at com.aei.sfdc.SFDCRequest.transform(SFDCRequest.java:98) at com.sap.aii.ib.server.mapping.execution.JavaMapping.executeStep(JavaMapping.java:112) at com.sap.aii.ib.server.mapping.execution.Mapping.execute(Mapping.java:60) at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:87) at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:71) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:123) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:73) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at sun.reflect.GeneratedMethodAccessor647.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47) 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:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99) at com.sun.proxy.$Proxy665.processFunction(Unknown Source) 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:597) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:183) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:267) 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:185) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)</Trace>

[maheswarareddykonda]

Hello,

I guess in your scenario there must be an java mapping. that mapping must be getting data as one fields contains prefix "xsi:" which is not declared.

ex: <xsi:field></xsi:field>

you must be xsi prefix declared in MT level where we used keep namespace.

also you were saying this is in Production that mean it would have worked earlier , so there could be below reasons

1.only this time came data such prefixes.

2.may be earlier developers might have used standared beans to remove/add such prefixes.(you can compare channel all environments).

Note:also you can check that data in mapping level(put data in test tab in mapping and test)

[viswanahreddy]

Till last month it was working fine and now it is failing...

while testing in Operation Mapping i am getting the below error... as we dont have message mapping.anything else to be placed while testing...please suggest.

[maheswarareddykonda]

Ok..i think you are using value mapping in java mapping code.

so please check first that value mapping got deleted, which is maintained username and password.

you please compare all environments credential related value mapping in ID.

also i guess you can not test your case in OM level..since you had used value mapping depending on Source system..

because whenever you test in OM level always default value for source system(Test_sender_service)..which we wont maintain values against that names in ID.

finally i am thinking that issue currently you are getting is not exactly your issue as per that first post error. mostly that relates to Prefix only.

please check input data for Javamapping ,,in case that data had prefix as xsi:

[viswanahreddy]

username, password and tocken id maintained and there is no issues with that...
can you please instruct me how to test that case in operation mapping

[maheswarareddykonda]

have u checked prefix (xsi) is there or not ?

[viswanahreddy]

Login is not happening from PI to SFDC

As it is failed to get the session id from SFDC and PI couldnt able to create the soapenv