File Adapter Service

Hi All,
I am using BPEL File Adapter service to read a file then archive this file , is there any way to get the name of this archived file using XPath query functions?

Hi,
What you have to do is:
1. Make a new variable of type inboundHeader (you find the type defined in the file adapter partner link definition)
2. Link the variable to the receive activity (Receive -> Adapters -> Header Variable)
3. You can now use the filename part of the header variable anywhere through your process.
Hope this description solves your problem.
Best Regards
Anders

Similar Messages

File Adapter Service debatching issue

I am experimenting with the ESB to enable an inbound file adapter to read multiple records "debatching" from a file with XML content. I am using a router to pass to another FileAdapter for writing each of the child records to a separate XML file. So basically I am just trying to test reading multiple records from a single XML file and then putting each record in its own separate outbound file. Seems like this should be a pretty simple initial experiment with using the ESB. But when I drop this inbound xml file, it is getting picked up properly, but the entire inbound xml file is not getting split up or debatched into separate XML messages from the file input adapter. My confusion is over how the fileadapter works with files with XML content, I have checked the "Files contain multiple messages" checkbox and indicated batches of "1". So shouldn't this tell the file adapter to process one record from the inbound file at a time, passing it thru the router and ultimately to the outbound file adapter? If so, how does the file adapter know what deliminates each record in the XML file? Here is the inbound xml that I am trying to read/break apart and put each child XML element "service request event" in it's own outbound file. Please advice what I am missing here. I am not so sure that debatching in the File Adapter will work with files including XML content? Or perhaps that is a work around or example that someone has to explain how to do this.
<?xml version="1.0" encoding="UTF-8"?>
<ns4:Events xmlns:ns4="http://xmlns.arl.psu.edu/OffboardServicesEvent" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.arl.psu.edu/OffboardServicesEvent Events.xsd">
<ns4:ServiceRequestEvent>
<ns4:summary>Planetary over temp test1</ns4:summary>
<ns4:severity_id>9</ns4:severity_id>
<ns4:urgency_id>64</ns4:urgency_id>
<ns4:status>103</ns4:status>
<ns4:type_id>11124</ns4:type_id>
<ns4:owner_id>100003631</ns4:owner_id>
<ns4:current_serial_number>1748AC16206</ns4:current_serial_number>
<ns4:inventory_item_id>2320011231602</ns4:inventory_item_id>
<ns4:problem_code>1001R3</ns4:problem_code>
</ns4:ServiceRequestEvent>
<ns4:ServiceRequestEvent>
<ns4:summary>Planetary over temp test2</ns4:summary>
<ns4:severity_id>9</ns4:severity_id>
<ns4:urgency_id>64</ns4:urgency_id>
<ns4:status>103</ns4:status>
<ns4:type_id>11124</ns4:type_id>
<ns4:owner_id>100003631</ns4:owner_id>
<ns4:current_serial_number>1748AC16206</ns4:current_serial_number>
<ns4:inventory_item_id>2320011231602</ns4:inventory_item_id>
<ns4:problem_code>1001R3</ns4:problem_code>
</ns4:ServiceRequestEvent>
</ns4:Events>
here is the schema....
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://xmlns.arl.psu.edu/OffboardServicesEvent"
targetNamespace="http://xmlns.arl.psu.edu/OffboardServicesEvent"
xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
elementFormDefault="qualified">
<xsd:element name="ServiceRequestEvent" type="ServiceRequestEventType"/>
<xsd:element name="Events">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="ServiceRequestEvent" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="ServiceRequestEventType">
<xsd:sequence>
<xsd:element name="summary" type="xsd:string"/>
<xsd:element name="severity_id" type="xsd:double"/>
<xsd:element name="urgency_id" type="xsd:double"/>
<xsd:element name="status" type="xsd:double"/>
<xsd:element name="type_id" type="xsd:double"/>
<xsd:element name="owner_id" type="xsd:double"/>
<xsd:element name="current_serial_number" type="xsd:string"/>
<xsd:element name="inventory_item_id" type="xsd:string"/>
<xsd:element name="problem_code" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
I have been scanning thru the Oracle tutorials and googling, but have not found any examples where a single XML document is debatched via the File adapter in this way.
Thanks for any help,
Todd

I figured it out. I was using 10.1.3.1, which does not support XML debatching -- just flat file debatching. I upgraded to 10.1.3.3 and it works now. Before I did that, however, I followed the instructions here: http://www.oracle.com/technology/products/ias/bpel/pdf/10133technotes.pdf (section: Transferring Large Payloads in Oracle BPEL Process Manager) and downloaded those jarfiles. Perhaps they come with 10.1.3.3, but I did not remove them before I upgraded so I'm not sure if those steps were necessary.

ESB File Adapter Service question

I am experimenting with ESB to enable an inbound file adapter to read multiple records from an XML file. I am using a router to pass to another FileAdapter for writing each of the child records to a separate XML file. So basically I am just trying to test reading multiple records from a single XML file and then putting each record in its own separate XML file. Seems like should be a pretty simple initial experiment with using the ESB. But when I drop this inbound xml file, it is getting picked up properly, but the entire inbound xml file is getting written to just a single outbound xmlfile (and is not getting split up). My confusion is over how the fileadapter works, I have checked the "Files contain multiple messages" checkbox and indicated batches of "1". So shouldn't this tell the file adapter to process one record from the inbound file at a time, passing it thru the router and ultimately to the outbound file adapter? If so, how does the file adapter know what deliminates each record in the XML file? Here is the inbound xml that I am trying to read/break apart and put each service request event in it's own outbound file. Please advice what I am missing here.
<Events xmlns="http://www.example.org/test">
<ServiceRequestEvent>
<summary>test1</summary>
<severity_id>9</severity_id>
<urgency_id>64</urgency_id>
<status>103</status>
<type_id>11124</type_id>
<owner_id>100003631</owner_id>
<current_serial_number>1748AC16206</current_serial_number>
<inventory_item_id>2320011231602</inventory_item_id>
<problem_code>1001R3</problem_code>
</ServiceRequestEvent>
<ServiceRequestEvent>
<summary>test2</summary>
<severity_id>9</severity_id>
<urgency_id>64</urgency_id>
<status>103</status>
<type_id>11124</type_id>
<owner_id>100003631</owner_id>
<current_serial_number>1748AC16206</current_serial_number>
<inventory_item_id>2320011231602</inventory_item_id>
<problem_code>1001R3</problem_code>
</ServiceRequestEvent>
</Events>
here is the schema....
<?xml version="1.0" encoding="windows-1252" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.example.org/test"
targetNamespace="www.example.org/test"
xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
elementFormDefault="qualified">

<xsd:element name="Event" abstract="true" type="EventType"/>
<xsd:element name="ServiceRequestEvent" substitutionGroup="Event" type="ServiceRequestEventType"/>
<xsd:element name="PartRequestEvent" substitutionGroup="Event" type="PartRequestEventType"/>
<xsd:element name="CounterEvent" substitutionGroup="Event" type="CounterEventType"/>
<xsd:element name="Events">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="Event" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ServiceRequestEvents">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="ServiceRequestEvent" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="EventType">
<xsd:sequence/>
</xsd:complexType>
<xsd:complexType name="ServiceRequestEventType">
<xsd:complexContent>
<xsd:extension base="EventType">
<xsd:sequence>
<xsd:element name="summary" type="xsd:string"/>
<xsd:element name="severity_id" type="xsd:double"/>
<xsd:element name="urgency_id" type="xsd:double"/>
<xsd:element name="status" type="xsd:double"/>
<xsd:element name="type_id" type="xsd:double"/>
<xsd:element name="owner_id" type="xsd:double"/>
<xsd:element name="current_serial_number" type="xsd:string"/>
<xsd:element name="inventory_item_id" type="xsd:string"/>
<xsd:element name="problem_code" type="xsd:string"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="PartRequestEventType">
<xsd:complexContent>
<xsd:extension base="EventType">
<xsd:sequence>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="CounterEventType">
<xsd:complexContent>
<xsd:extension base="EventType">
<xsd:sequence>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>
The next experiment is to try performing some content based routing based on the type of event. But I need to learn how to crawl first. I have been scanning thru the Oracle tutorials and googling, but have not found any examples where a single XML document is broken apart in this way into multiple output files.
Thanks for any help,
Todd

Thanks for your reply Allan!
I went with your recommendations and was able to get it partially working. I modified my XSLT mapping as you had indicated. I also ran the transform thru Stylus studio and the transform appears to have processed properly.
What I am seeing happen now is that the writer is still only writing 1 file, but now rather than both children being included in the file, just the very first child element is included. I am not sure what happens to the 2nd one. I was expecting it to be written out to a second file. Below is the configuration settings I am using for the adapters...
File reader:
Currently batching turned off (ie unchecked the files contain multiple messages). I originally had this checked with it publishing in batches of 1. This appears to make no difference. The Schema Element is set to the parent element "Events".
Router:
Transform via router. This change appears to be working correctly since I was able to transform via stylus studio and see both child element transformed in the output document.
<xsl:template match="/">
<xsl:for-each select="/imp1:Events/imp1:ServiceRequestEvent">
<imp1:ServiceRequestEvent>
<imp1:summary>
<xsl:value-of select="imp1:summary"/>
</imp1:summary>
File writer:
File naming convention: event_%yyMMddHHmmssSS%.xml (so should be unique)
I tried checking and unchecking "Number of messages Equals = 1", No files are written when this is checked? No errors found in the ESB instance console, appears to have written successfully, but no file. Schema element is set to the child element "ServiceRequestEvent" since I want each output file to include a single ServiceRequestEvent.
So I am a bit confused what I am missing? It is difficult to gain visibility into what is going on under the covers. Is there any debug logging that may show exactly what is happening as the input file is processed, transformed and then written out? I assume that If I can transform the input document via Stylus studio to a document with just the 2 child elements that this is ok, but how does the file adapter know how to distinquish how to break up this output file into separate files without some kind of indication of a record delimiter?
Thanks again for your help!
-T

File adapter not activating

Hi.
I have a frustrating problem. I set up a sender file adapter.However even after activating the adapter it does not show up in the adapter monitor.I can see a entry for file but no lights(Green or Red).The XI file adapter service is activated in the j2ee administration tool.
Running XI sp9.
Any ideas where to go look next.

check out question 3 in the adapter section:
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
this will solve your problem
Regards,
michal

XI 2.0 File Adapter with XI3.0

I am send a file from my pc to XI3.0,using an XI2.0 file adapter on my pc.
My problem is that I cannot get it to correctly generate the name spaces
<ns1:SALES_ORDER xmls:ns1="http://SALES_NS">
instead it generates:
<ns1:SALES_ORDER xmls="http://SALES_NS">
Am I missing a paramter in my file adapter properties file?
Thanks
Patrick

Hello,
We are also having similar type of problems. In our installation the log is at/usr/sap/<INSTANCE>/DVEBMGS00/j2ee/cluster/server0/log/services/com.sap.aii.adapter.file.svc
In the log file, I see
2004:11:11 10:12:12 : File Adapter Administration Intialized
No file adapter configured
Not sure why it says that no adapter is configured even though we have couple File adapters configured with Adapter status active and all the objects have been activated.
I would really appreciate if anyone can point out, if I am missing something that I am supposed do to other than J2EE File adapter service being run and Activating a Fileadapter in the Integration Directory.
Thanks

XI 3 : J2EE File Adapter Trouble

Hi,
I have implemented a scenario file -> XI -> file.
I use XI 3.0 Stack 09.
I have created my scenario in IR and ID (Communciation channel...) and nothing append.
I go in the adapter monitor and the only thing i can see is the status of the JPR.
I should see the status of the File Adapter No ?
Regards,
Vincent.

Hello,
We are also having similar type of problems. In our installation the log is at/usr/sap/<INSTANCE>/DVEBMGS00/j2ee/cluster/server0/log/services/com.sap.aii.adapter.file.svc
In the log file, I see
2004:11:11 10:12:12 : File Adapter Administration Intialized
No file adapter configured
Not sure why it says that no adapter is configured even though we have couple File adapters configured with Adapter status active and all the objects have been activated.
I would really appreciate if anyone can point out, if I am missing something that I am supposed do to other than J2EE File adapter service being run and Activating a Fileadapter in the Integration Directory.
Thanks

Get File name using File Adapter

Does anyone know how to get the file name that has been picked up so it can be past to a variable so it can be used in the BPEL process.
cheers
James

Hi James,
Here the STEPS,
Create File Adapter.
Add File Adapter Service to Receive Activity.
Click Receive Activity and goto Adapters Tab.
Click "Tourch" to get variable names.
Select Variable -> Process -> Variables and Click on "Create New Variable" icon and give name.
Select "Message Type" and click "Tourch" icon.
Now you select "Partner Links" -> FileAdapter WSDL -> Imported WSDL -> Message Type -> InboundHeader_msg and select OK.
It's done.
now you can use this Global Variable to get Filename and Directory name.
Regards,
Bhavesh Thaker.

File Adapter Read not working

Hi All,
I have a file adapter service,which has to read a CSV file.
The configurations i have done is
1)Gave the incming diretory path,delete option is checked
2)Polling frequency - 5 secs
3) gave the xsd.
But the process is not picking up the file,and i dont see any errors in domain.log
Please help.
Regards
Ashwini

Hi Anirudh,
Thanks for the reply.
IS there no solution other than restarting the server ??
below is the xsd i am using.please let me know the modifications that i can do to reject the second invoice if there are any errors in that and proceed further.
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
targetNamespace="http://antony.blog.com/ReadStructuredMasterDetailService"
xmlns:tns="http://antony.blog.com/ReadStructuredMasterDetailService"
elementFormDefault="qualified" attributeFormDefault="unqualified"
nxsd:encoding="ASCII" nxsd:stream="chars" nxsd:version="NXSD">
<xsd:element name="Invoice">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="InvoiceHeader" nxsd:startsWith="$H$" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Supplier_name" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Supplier_Site" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Inv_No" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Invoice_Date" type="xsd:date" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Invoice_Currency" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Invoice_gross_Amount" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Total_Ex_VAT" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy="""/>
<xsd:element name="Total_VAT_Amount" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Scanned_image_Reference_URL" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="${eol}" />
<xsd:element name="InvoiceDtail" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="InvoiceDTL" nxsd:startsWith="$D$"
maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Business_Unit" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="location" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Store_Name" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Department" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Natural_Account" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy=","/>
<xsd:element name="Inc_VAT" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Ex_VAT" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="VAT_Amount" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="VAT_Rate" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="${eol}"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
Regards
Ashwini

Reading File Using JCA File Adapter

Hi ,
I have used Jdeveloper to create File Adapter Service using synchronous Read operation to read .csv file from statically defined physical path, then generated Business Service using eclipse while importing jca, xsd and wsdl generated in Jdeveloper , but when running Buisiness Serrvice i am getting an error as follows saying no data to process while FileB is present in that location containing data also :
The invocation resulted in an error: Invoke JCA outbound service failed with connection error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/file/FileReadService [ SynchRead_ptt::SynchRead(Empty,body) ] - WSIF JCA Execute of operation 'SynchRead' failed due to: No Data to process.
No Data to process.
File D:\ReadFile\"FileB.txt" to be processed was not found or not available or has no content
; nested exception is:
BINDING.JCA-11007
No Data to process.
No Data to process.
File D:\ReadFile\"FileB.txt" to be processed was not found or not available or has no content
Please make sure that the file exists in the specified directory.
com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/file/FileReadService [ SynchRead_ptt::SynchRead(Empty,body) ] - WSIF JCA Execute of operation 'SynchRead' failed due to: No Data to process.
No Data to process.
File D:\ReadFile\"FileB.txt" to be processed was not found or not available or has no content
; nested exception is:
BINDING.JCA-11007
No Data to process.
No Data to process.
File D:\ReadFile\"FileB.txt" to be processed was not found or not available or has no content
Please make sure that the file exists in the specified directory.
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:153)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:571)
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.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
at $Proxy125.sendMessageAsync(Unknown Source)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:603)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:538)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:558)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:426)
at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:377)
at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:345)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_1033_WLStub.invoke(Unknown Source)
at com.bea.alsb.console.test.TestServiceClient.invoke(TestServiceClient.java:174)
at com.bea.alsb.console.test.actions.DefaultRequestAction.invoke(DefaultRequestAction.java:117)
at com.bea.alsb.console.test.actions.DefaultRequestAction.execute(DefaultRequestAction.java:70)
at com.bea.alsb.console.test.actions.ServiceRequestAction.execute(ServiceRequestAction.java:143)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:91)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116)
at com.bea.alsb.console.common.base.SBConsoleRequestProcessor.processActionPerform(SBConsoleRequestProcessor.java:91)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
at com.bea.alsb.console.common.base.SBConsoleRequestProcessor.process(SBConsoleRequestProcessor.java:191)
at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158)
at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133)
at com.bea.alsb.console.common.base.SBConsoleActionServlet.doGet(SBConsoleActionServlet.java:49)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1129)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:687)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142)
at com.bea.portlet.adapter.scopedcontent.StrutsStubImpl.processAction(StrutsStubImpl.java:76)
at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167)
at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:225)
at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/file/FileReadService [ SynchRead_ptt::SynchRead(Empty,body) ] - WSIF JCA Execute of operation 'SynchRead' failed due to: No Data to process.
No Data to process.
File D:\ReadFile\"FileB.txt" to be processed was not found or not available or has no content
; nested exception is:
BINDING.JCA-11007
No Data to process.
No Data to process.
File D:\ReadFile\"FileB.txt" to be processed was not found or not available or has no content
Please make sure that the file exists in the specified directory.
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:263)
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
... 117 more
Caused by: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/file/FileReadService [ SynchRead_ptt::SynchRead(Empty,body) ] - WSIF JCA Execute of operation 'SynchRead' failed due to: No Data to process.
No Data to process.
File D:\ReadFile\"FileB.txt" to be processed was not found or not available or has no content
; nested exception is:
BINDING.JCA-11007
No Data to process.
No Data to process.
File D:\ReadFile\"FileB.txt" to be processed was not found or not available or has no content
Please make sure that the file exists in the specified directory.
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:667)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:357)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:316)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:359)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:257)
... 118 more
Caused by: BINDING.JCA-11007
No Data to process.
No Data to process.
File D:\ReadFile\"FileB.txt" to be processed was not found or not available or has no content
Please make sure that the file exists in the specified directory.
at oracle.tip.adapter.file.outbound.FileReader.readFile(FileReader.java:272)
at oracle.tip.adapter.file.outbound.FileReader.executeFileRead(FileReader.java:178)
at oracle.tip.adapter.file.outbound.FileInteraction.executeFileRead(FileInteraction.java:331)
at oracle.tip.adapter.file.outbound.FileInteraction.execute(FileInteraction.java:395)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:534)
... 122 more
Regards,
Abhinav

Hi ,
When i tied to hit the same service again today after shutting down my server yestrerday , i am getting an error response but yesterday it was working nice i tried all read , syncread , write operations , they were working well .. can u please help to debug ......
The invocation resulted in an error: Invoke JCA outbound service failed with application error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/file/FileReadService [ SynchRead_ptt::SynchRead(Empty,body) ] - WSIF JCA Execute of operation 'SynchRead' failed due to: Could not instantiate InteractionSpec oracle.tip.adapter.file.outbound.FileReadInteractionSpec due to: oracle.tip.adapter.file.outbound.FileReadInteractionSpec; nested exception is:
java.lang.ClassNotFoundException: oracle.tip.adapter.file.outbound.FileReadInteractionSpec; nested exception is:
oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: Could not instantiate InteractionSpec oracle.tip.adapter.file.outbound.FileReadInteractionSpec due to: oracle.tip.adapter.file.outbound.FileReadInteractionSpec; nested exception is:
java.lang.ClassNotFoundException: oracle.tip.adapter.file.outbound.FileReadInteractionSpec
com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/file/FileReadService [ SynchRead_ptt::SynchRead(Empty,body) ] - WSIF JCA Execute of operation 'SynchRead' failed due to: Could not instantiate InteractionSpec oracle.tip.adapter.file.outbound.FileReadInteractionSpec due to: oracle.tip.adapter.file.outbound.FileReadInteractionSpec; nested exception is:
java.lang.ClassNotFoundException: oracle.tip.adapter.file.outbound.FileReadInteractionSpec; nested exception is:
oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: Could not instantiate InteractionSpec oracle.tip.adapter.file.outbound.FileReadInteractionSpec due to: oracle.tip.adapter.file.outbound.FileReadInteractionSpec; nested exception is:
java.lang.ClassNotFoundException: oracle.tip.adapter.file.outbound.FileReadInteractionSpec
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:155)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:571)
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.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
at $Proxy125.sendMessageAsync(Unknown Source)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:603)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:538)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:558)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:426)
at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:377)
at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:345)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_1033_WLStub.invoke(Unknown Source)
at com.bea.alsb.console.test.TestServiceClient.invoke(TestServiceClient.java:174)
at com.bea.alsb.console.test.actions.DefaultRequestAction.invoke(DefaultRequestAction.java:117)
at com.bea.alsb.console.test.actions.DefaultRequestAction.execute(DefaultRequestAction.java:70)
at com.bea.alsb.console.test.actions.ServiceRequestAction.execute(ServiceRequestAction.java:143)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:91)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116)
at com.bea.alsb.console.common.base.SBConsoleRequestProcessor.processActionPerform(SBConsoleRequestProcessor.java:91)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
at com.bea.alsb.console.common.base.SBConsoleRequestProcessor.process(SBConsoleRequestProcessor.java:191)
at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158)
at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133)
at com.bea.alsb.console.common.base.SBConsoleActionServlet.doGet(SBConsoleActionServlet.java:49)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1129)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:687)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142)
at com.bea.portlet.adapter.scopedcontent.StrutsStubImpl.processAction(StrutsStubImpl.java:76)
at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167)
at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:225)
at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/file/FileReadService [ SynchRead_ptt::SynchRead(Empty,body) ] - WSIF JCA Execute of operation 'SynchRead' failed due to: Could not instantiate InteractionSpec oracle.tip.adapter.file.outbound.FileReadInteractionSpec due to: oracle.tip.adapter.file.outbound.FileReadInteractionSpec; nested exception is:
java.lang.ClassNotFoundException: oracle.tip.adapter.file.outbound.FileReadInteractionSpec; nested exception is:
oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: Could not instantiate InteractionSpec oracle.tip.adapter.file.outbound.FileReadInteractionSpec due to: oracle.tip.adapter.file.outbound.FileReadInteractionSpec; nested exception is:
java.lang.ClassNotFoundException: oracle.tip.adapter.file.outbound.FileReadInteractionSpec
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:263)
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
Regards,
Abhinav

File adapter input file format

Here the communication scenario is as follows: read a file and send a message via XI to an inbound interface.
A file adapter service has been defined. Message protocol 'file content conversion' has been chosen for the file adapter service. Next the file format has to be defined in communiction channel settings.
Is it possible to define the input record structure in the file to be red itself?
The first line will list all column names. The data records will follow in line two up till end of file.
Regards
Klaus

Now I can add some more information to the facts.
In XI 2.0 the adapter engine was used to connect the integration engine to external systems. The adapter engine converted input file contents to a XML message. The structure of the records in the input file has to be defined. There was one option to read this structure from the first line of the file itself. This option was called 'fromFile'.
Now the current situation in XI 3.0 is that the integration engine reads the input file. Conversion of file contents is still available but the option to read the record structure from the input file doesn't exist anymore.
Does anybody know whether I am right and this functionality isn't available anymore or how to achieve the desired system function in XI 3.0.
Regards
Klaus

File Adapter BPEL Trigger

Hi,
This should be a really easy thing to do but I'm obviously missing something simple and fundamental.
I want to set up a BPEL process that is initiated by the receipt of a file. All I initially want to get from that trigger is the name of the file and pass that value on to the next step in the chain.
So, I created a new BPEL Process project and added a File Adapter service, filling in all the details for picking up the file from the place that it'll arrive. Reading the "Adapter" manual, I should be able to get the file details (name, directory) by adding UseHeaders="true" into the JCA definition in the File Adapter's WSDL file. I have done this. Doing this creates another WSDL file called fileAdapterInboundHeader.wsdl Now, this is where I get lost. How do I use this?
By default, a new BPEL Process diagram shows a "Client" Partner Link, a receiveInput activity and a replyOutput activity. The receiveInput activity links from the Client Partner Link and the replyOutput activity links back to the Client.
So I'm guessing that I need to replace the Client partner link with my new File Adapter service so that the detection of the file starts my BPEL process, rather than some triggered activity from a client.
This is basically what I've done but it's really not working. How do I get at the filename that's gathered by the File Adapter service? Do I need an XML schema definition to work from?
Perhaps there's a nice simple example of this somewhere that somebody could point me at? I've been searching but not found anything yet.
Thanks,
Andy

I've written up this procedure in a bit more detail than RedRocker originally provided so that people like me who are complete noobs to BPEL and JDeveloper can do this more easily. The example I give here takes the filename and writes it to a database table. The table just has a FILE_ID column (automatically populated from a sequence by an ON-INSERT trigger) and a CONTENTS column (where the file name goes):
How-To Get the name of an Input File and store it in a database table column.
1) Assuming that you're using JDeveloper and you have an Application Workspace, right-click on the Application and choose New Project from the context menu.
2) In the New Gallery, select Projects and then choose BPEL Process Project from the Items list:
3) Create an Empty BPEL Process by choosing Empty BPEL Process from the Template dropdown of the BPEL Project Creation Wizard.
4) This will bring up a completely empty BPEL Process in JDeveloer:
5) From the Component Palette (top-right), choose Services and then locate the File Adapter Service in the list.
6) Drag the File Adapter service from the Component panel to one of the Services columns in the main BPEL process designer (centre window). A Wizard will appear.
7) Enter a name for the Service (eg. GetFileName). Fill in the description if you wish.
8) Choose Read from the Operation Type list (adjust the Operation Name if you like):
9) Enter the physical directory (or logical name for one) where the file is to be read from. Decide on whether you want the file to be deleted after it's been read (it won't be re-processed if it's left there since each poll cycle only looks for files that arrived more recently than its previous cycle), and whether to archive the file.
10) Enter appropriate file selection filter criteria (note that for this BPEL example we're not interested in the file's content at all so the "Files contain Multiple Messages" tickbox and "Publish Messages in Batches of" selector are unimportant):
11) Select an appropriate Polling Frequency:
12) Select an Opaque schema (we're not interested in the file's content in this example)
13) Click Finish
14) Click OK to close the Partner Link creation wizard
15) Click Save All.
16) From the Application Navigator, drill down through the newly created BPEL Project, through the Integration Content folder to find your GetFileName Partner link. Expand this and double-click the GetFileName.wsdl file. In the centre panel, click the Source tab (at the bottom):
17) Scroll down to the <jca:operation> tag and add the attribute UseHeaders="true" at the end
18) Click Save All.
19) Return to the main GetFileName BPEL Process designer by clicking the tab name at the top of the centre window. In the Structure panel (bottom-left), expand the Variables folder, followed by the Process folder and click the exposed Variables folder
20) Create a variable by clicking the "Wand +" icon.
21) Give the variable a meaningful name (FileName) and choose Message Type. Click the Browse flashlight:
22) Choose InboundHeader_msg by drilling down as shown:
23) Click OK and OK.
24) In the Component palette (top-right), choose Process Activities from the dropdown list. Locate the Receive activity and drag it to the centre of the middle panel (ie. the BPEL Designer window) into the area marked "Drop Activity Here":
25) Double-click the new Receive activity to bring up the properties dialogue box. On the General tab, give the activity a meaningful name (eg. ReceiveFilename).
Click the Browse flashlight next to the Partner Link field and choose GetFileName from the list. The Operation dropdown will automatically show "Read" which is correct.
26) Click the Auto-Create Variable ("Wand +") icon next to the Variable field. This variable is merely a placeholder for the content of the file being read. Because we've said that the incoming file's schema is Opaque, this variable will not get populated. However, we still need to have a variable. Give the variable a meaningful name (eg. FileContent) and allow the type to be selected automatically and then click OK on the Create Variable dialogue.
27) Given that we'd want the receipt of a file to be individually traceable, ensure that the Create Instance checkbox is ticked on the General tab:
28) Click the Adapters tab. Click the Browse flashlight next to the Header Variable field and select the FileName variable from the list presented and click OK:
29) Click OK on the Receive activity property page to return to the main BPEL Designer screen.
30) At this point, the data is available within the BPEL process but needs to be assigned to something. In this example, the value is going to be written to the FILE_NAME column in a table called ACH_INUPT_FILE. This will be done through an Insert performed by a Database Adapter. The ACH_INUPT_FILE table is configured to have an ON-INTERT trigger which automatically selects a value from a Sequence for its Primary Key value. Therefore simply inserting a row will provide a Unique value in the FILE_ID column.
The next thing we need to do is create the Partner Link that performs the Insert operation. This will create a variable which we can assign the File Name to when this new Service is linked into the process flow.
From the Component panel, choose Services from the dropdown. Locate the Database Adapter service and drag one onto the BPEL Designer page in the Services column.
The Adapter Configuration wizard appears. Enter a meaningful name from the adapter (eg. WriteFileName). Enter a description if you like and click Next.
31) Choose the appropriate Connection from the dropdown list. Click Next.
32) Choose "Perform an Operation on a Table" for the Operation Type and deselect all operations except Insert Only. Click Next.
33) Click the Import Tables button. From the presented table, ensure that the table that's going to hold the data is selected by shuttling the table from the Available panel to the Selected panel. In this case I've selected the ACH_INPUT_FILE table. Click OK.
34) The Select Table panel shows the ACH_INPUT_FILE table. Click Next.
35) In this example there are no further relationships to make, so click Next on the Relationships page:
36) Click Finish. The Database Adapter's Partner Link properties page is displayed. Note that the Partner Link Type and Partner Role are automatically populated from the information gathered in the previous set of dialogue pages. Note that to change any of those values previously entered, click the Define Adapter Service icon. Click OK.
37) In the Components Palette, select Process Activities from the dropdown. Locate the Invoke activity and drag one to the main BPEL process flow and drop it immediately below the ReceiveFilename activity.
38) Double-click the new Invoke activity and the Invoke property panel is shown. On the General tab, give the Invoke activity a meaningful name (eg. InvokeWriteFileName).
Click the Browse flashlight next to the Partner Link field and select WriteFileName from the list of presented services. Click OK.
39) Note that the operation "insert" is automatically populated into the Operation dropdown.
40) Click the Automatically Create Input Variable icon (Wand +) next to the Input Variable field. Accept the default "InvokeWriteFileName_insert_InputVariable". This creates the variable of the right type that's needed by the WriteFileName service.
41) Click OK to close the WriteFileName Invoke activity property sheet. Note that there is a warning flag next to the new Invoke activity. We need to assign the file name to the Invoke activity's Input Variable.
42) From the Component Palette, drag an Assign activity so that it sits between the Receive and the Invoke activities in the BPEL flow.
43) Double-click the new Assign activity and click the General tab. Enter a meaningful name for the activity (eg. AssignFileNameToDBWriteInput).
44) Click the Copy Operation tab. Click the Create button and select Copy Operation from the list of types.
45) In the From panel, choose Expression from the Dropdown list. From the panel, click the XPath Expression Builder icon (highlighted).
46) From the Function list dropdown under the Functions heading, select Conversion Functions. Double-click the "string()" function. This moves the string() function into the Expression panel at the top as shown.
47) In the Expression panel, click inside the ( and ) brackets. Expand the variable FileName in the BPEL Variables panel below and select the fileName element from the InboundFileHeaderType element. Double-click the fileName to move the XPath expression into the Expression panel:
48) Click OK. In the To panel, ensure that the Type dropdown shows Variable. Drill into the InvokeWriteFileName_insert_InputVariable and select the element that the file name is to be assigned to. In the example illustrated, the variable is called "contents" but that's just because the table has that as the field name rather than "filename".
49) Click OK. The Assign property sheet shows the Copy Operation as below:
50) Click OK. The Invoke operation may still show a warning flag. Click the flag to see the errors/warnings. If there are now errors/warnings shown, click OK to dismiss the panel and the flag will disappear. The BPEL Process is complete and can be deployed.
It is long-winded, but it might just help somebody else.
Andy

Error during mapping service, RFC-XI-File Adapter

Hello,
I have the following problem: I am using RFC to send some data to XI and then to File Adapter, however I get a short dump with "5990 Error during mapping service in XI". Even though mappings works, I tested using the document that comes in XI in Repository without any errors.
       What does this error means and is there any way to get more detailed explanation of my error. Thank you in advance for your help,
               Dmitriy Mindich

Synchronous RFC
1. CALL FUNCTION func DESTINATION dest
                     parameter_list.
Asynchronous RFC
2. CALL FUNCTION func STARTING NEW TASK task
                [DESTINATION {dest|{IN GROUP {group|DEFAULT}}}]
                parameter_list
                [{PERFORMING subr}|{CALLING meth} ON END OF TASK].
Transactional RFC
3. CALL FUNCTION func IN BACKGROUND TASK
                     [DESTINATION dest]
                     parameter_list
                     [AS SEPARATE UNIT].
Use help function of your ABAP editor for more details.
Regards
Stefan

Problem with file adapter (FTP) created under business service

Hi
I am using file adapter in my receiver communication channel. I dont know the physical existance of the system so i have created one business service. Under this business system i have created a file adapter with FTP protocol. I have given all the parameters. But when i am trying to execute my scenarion i am getting the following error in SXMB_MONI.
com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_SQLMediaCodeToCRMCapaign_: RuntimeException in Message-Mapping transformatio~
In RWB i am getting the following error.
Mapping Error
Execption_During_Execution
In Communication Channel monitoring I am not getting any information regarding receiver file adapter. Its not showing any message either error or sucessful. How to find whether my receiver communication channel FTP parameters configured correctly or not.What is the error. Please help me.
Regards
Sowmya

Somya,
Error clearly indicates that issue is with mapping....so there is no point of checking receiver adapter..
BTW for checking whether the FTP site is working properly or not , you can use any ftp client softwares or command prompt of windows also.
---->In Communication Channel monitoring I am not getting any information regarding receiver file adapter. Its not showing any message either error or successful.
Message has not reached up to that level so no point of looking at receiver communication channel.
Regards,

J2Se receiver File adapter-HTTP 503 no listener registered for service

Hi,
We are using J2Se file adapter for one the interfaces and the logs of the J2se adapter engine has shown the following error-
Error: com.sap.aii.messaging.net.TransportException: HTTP 503 no listener registered for service /file/example_outbound
     at com.sap.aii.messaging.net.HTTPRequest.run(ServerHttpImpl.java:416)
I checked with the J2SE File/FTP receiver adapter configuration given at help.sap and found the following the following info related to the error-
Specifications for addressing by the Integration Engine
○       XI.httpPort=<port_no>
<port_no>specifies the HTTP server port that receives the messages from the Integration Engine.
○       XI.httpService=<service>
<service> describes the service part of the address where the Integration Engine must send its messages.
These specifications are mandatory.
If, for example, you have specified XI.httpPort=1234 and XI.httpService=/file/Receiver, the end point address of the file/FTP adapter in the Integration Engine must be specified as follows:
http://<fileadapterhost>:1234/file/Receiver
The end point address must be extended as follows for the Integration Engine in Release 1.0:
http://<fileadapterhost>:1234/file/Receiver?action=execute&pipelineid=Receiver
If the Integration Engine message is sent to a non-specified adapter service, the system displays the following error message:
*No registered listener for <Service> found*
The system displays the same message if the adapter is initialized, but has not been started (status STOPPED or INITIALIZED).
Where I need to check this Integration engine address specifications. I have't found any of the above code in the adapter configuration which we are using presently.The interface is running successfully before but thrown this error now.
Please reply me if some one has faced similar issue and get it resolved.

Hi
How was this issue resolved? I have the same problem.
I only have two receivers - the deafult j2se file receiver and my newly created one which used the default as a template. The ports and service's are different.
I've even tried deleting my custom receive adapter and using only the default one but i still get that error.

EOIO service on Receiver FTP/File Adapter

Hi,
I have a scenario where I would like the sender adapter to be quality of service, EO (Exactly Once), and the receiver ftp/file adapter to be of quality of service, EOIO (Exactly Once in Order). Is there a way to change the quality of service on the receiver adapter only so that it differs from the sender adapter?
Thanks in advance.
Best Regards,
Duke

Hi,
Unfortunately changing the QoS in the adapter module does not solve the issue. The message appears to be put into the queue prior to the module being called. Below is the audit log.
2007-10-26 09:58:30 Success Using connection AFW. Trying to put the message into the receive queue.
2007-10-26 09:58:30 Success Message successfully put into the queue.
2007-10-26 09:58:30 Success The message was successfully retrieved from the receive queue.
2007-10-26 09:58:30 Success The message status set to DLNG.
2007-10-26 09:58:30 Success Delivering to channel: XXXXXXX
2007-10-26 09:58:30 Success ChangeQoS: Module called
2007-10-26 09:58:30 Success File adapter receiver: processing started; QoS required: ExactlyOnceInOrder
As you can see the QoS has been changed to EOIO from the adapter module, but the message is still in Qos EO.
Am I missing something or is there another way this can be achieved? Can we do this in the mapping somehow before it ever gets to the AFW?
Thanks in advance.
Best Regards,
Duke

File Adapter Service

Similar Messages

Maybe you are looking for