Axis, response to file receiver
We have an Axis receiver channel. We want to send the response message to a file destination, and use the provided example from the "fAQ for Axis Adapter" using the UnPivotHandler as the guide.
However, we run into an error. The audit log shows the following:
30.10.2012 23:38:19.196 Information Axis: continuing to response message 80b7063c-22e2-11e2-c1ac-0000028f53de
30.10.2012 23:38:19.197 Information MP: processing local module localejbs/AF_Adapters/axis/HandlerBean
30.10.2012 23:38:19.198 Information MP: processing local module localejbs/AF_Adapters/axis/HandlerBean
30.10.2012 23:38:19.198 Information Axis: invoking handler mc of java:com.sap.aii.axis.soap.MessageContextPropertiesHandler
30.10.2012 23:38:19.198 Information MP: processing local module localejbs/AF_Adapters/axis/HandlerBean
30.10.2012 23:38:19.199 Information Axis: invoking handler file of java:com.sap.aii.axis.transport.file.FileSender
30.10.2012 23:38:19.233 Error Axis: error in invocation: java.io.IOException: failed to rename ./temp/d92a9050-4347-f006-e100-00000a8c00f36615050845103192964.tmp to /import_cifs/sapdata/1001/TestDiv/d92a9050-4347-f006-e100-00000a8c00f3
30.10.2012 23:38:19.233 Error MP: exception caught with cause java.io.IOException: failed to rename ./temp/d92a9050-4347-f006-e100-00000a8c00f36615050845103192964.tmp to /import_cifs/sapdata/1001/TestDiv/d92a9050-4347-f006-e100-00000a8c00f3
30.10.2012 23:38:19.234 Error Adapter Framework caught exception: ; nested exception is: java.io.IOException: failed to rename ./temp/d92a9050-4347-f006-e100-00000a8c00f36615050845103192964.tmp to /import_cifs/sapdata/1001/TestDiv/d92a9050-4347-f006-e100-00000a8c00f3
30.10.2012 23:38:19.235 Error Transmitting the message to endpoint <local> using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: failed to rename ./temp/d92a9050-4347-f006-e100-00000a8c00f36615050845103192964.tmp to /import_cifs/sapdata/1001/TestDiv/d92a9050-4347-f006-e100-00000a8c00f3.
Now, the obvious interpretation is that we have missing authorizations for the target folder, but we are certain that is not the issue (full authorizations for everyone set).
This is our processing seq. and module configuration:
Has anyone sucessfully implemented this scenario, any idea what could be wrong for us?
Thanks!