File Adapter's Write Functionality Error

I am using BPEL PM10.1.3.1
and getting problem for the OrderBooking tutorial File Adapter’s Write Functionality
BUILD FAILED
D:\JDeveloper\jdev\mywork\OrderBookworkspace\POAcknowledge\build.xml:79: A problem occured while connecting to server "localhost" using port "9700": bpel_POAcknowledge_1.0.jar failed to deploy. Exception message is: ORABPEL-05215
Error while loading process.
The process domain encountered the following errors while loading the process "POAcknowledge" (revision "1.0"): BPEL validation failed.
BPEL source validation failed, the errors are:
[Error ORABPEL-10902]: compilation failed
[Description]: in "bpel.xml", XML parsing failed because "undefined part element.
In WSDL at "file:/D:/product/10.1.3.1/OraBPEL_1/bpel/domains/default/tmp/.bpel_POAcknowledge_1.0_9cb86657d04e99ccb06091467c82f390.tmp/FileWrite.wsdl", message part element "{http://www.thiscompany.com/ns/sales}POAcknowledge" is not defined in any of the schemas.
Please make sure the spelling of the element QName is correct and the WSDL import is complete.
[Potential fix]: n/a.
If you have installed a patch to the server, please check that the bpelcClasspath domain property includes the patch classes.
at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcessHolder.java:285)
at com.collaxa.cube.engine.deployment.DeploymentManager.deployProcess(DeploymentManager.java:804)
at com.collaxa.cube.engine.deployment.DeploymentManager.deploySuitcase(DeploymentManager.java:670)
at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.deploySuitcase(BPELDomainManagerBean.java:445)
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.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
at com.evermind.server.ThreadState.runAs(ThreadState.java:620)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
at DomainManagerBean_RemoteProxy_4bin6i8.deploySuitcase(Unknown Source)
at com.oracle.bpel.client.BPELDomainHandle.deploySuitcase(BPELDomainHandle.java:317)
at com.oracle.bpel.client.BPELDomainHandle.deployProcess(BPELDomainHandle.java:339)
at deployHttpClientProcess.jspService(_deployHttpClientProcess.java:376)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:453)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:591)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:515)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
I am not able to trace the error....
Please suggest me where I am making mistake or anything else required i.e.Patche etc. to overcome this issue.
Avinash

Hey I found solution to this problem after R&D on JDeveloper BPEL file structure
We just have to
Copy OrderBookingPO.xsd and POAcknowledge.xsd from the Oracle_
Home\integration\orabpel\samples\tutorials\127.OrderBookingTu
torial\PracticeFiles directory to the Oracle_
Home\integration\jdev\jdev\mywork\OrderBookworkspace\POAcknow
ledge\bpel directory.
not in
Oracle_
Home\integration\jdev\jdev\mywork\OrderBookworkspace\POAcknow
ledge directory as mensitioned in Order Booking Tutorial in section Adding Transformation Logic just ignore this instruction and follow up as I have asked to you in above paragraph. Every thing will be ok...
thanx
Avinash Kumar Pandey

Similar Messages

  • File Adapter Issue: Not functioning when used with BIC user modules

    Hi! ALL
    We have been experiencing issue with file adapter, when we SeeBurger BIC user modules in sender file - FTP communication channel.
    The regular FTP functionality is working fine if do not have BIC user modules defined under the module tab.However, when put in BIC user module parameters it is not picking up the file.
    Also, we do not see any error logs; even the communication channel monitoring does not show any error log....only show the polling interval success, without the file being picked up.
    This issue started appearing once we deployed our new sda file....as we changed our BIC mapping.
    We can try doing back to our previous sda file....to see it fixes the problem.
    But, before doing that ....we would like to know where the cause of this issue....Can you point us to any error logs we can find on the PI server.
    Your help is greatly appreciated!!
    Thank you,
    Patrick.

    If you configured your logging correctly you should find in the log folders
    ./applications/com.seeburger.jucon/
    ./applications/com.seeburger.bicxiadapter/
    Try to scan those for recent errors - if the no log files can be found you should check the defaultTrace.

  • Receiver File Adapter:Variable substitution :FATAL  ERROR

    HI all
    as per the previous thread :
    <b>Receiver File Name Variable Substitution :payload: Fatal Error
    in our idoc to file sceanrio, we are using simple <b>graphical mapping.</b>
    for dynamic file name , variable field is at <b>Target message type</b>,So  on using <b>Variable substitution</b>, again the error is same :
    SAXException while parsing XML payload: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) .
    <b>Our XI  Component version : 2004
    WAS 6.4 SP 15</b>
    Thanks
    AR

    Ashutosh,
       There is nothing to do with your mapping programs. Its the mistake in ur reciever file adapter configuration for variable substitution.I asked u whether u changed message mapping in order to implement the UDF!!
    Did u tried checking the audit log. Ok just to see where u are going wrong, instead of using Payload :... in Variable substitution use Message:..... and give some interface name so that to check whether the file is created with Interface name.
    Juz give a try!!!
    Best regards
    raj.

  • Receiver File Adapter - Empty document found error

    Hi,
    I have a slight issue that I do not understand.
    For example, I have a file that is 256 bytes in size and definitely has some content. However, when the file adapter processes the file it says in the log "Empty document found" - but I can see the file has content.
    Any ideas ? I am using using XI 3.0 SP19.
    Cheers
    Colin.

    hi colin,
    i will agree with u,
    may be the XI can not understand your test data,
    can u tell me the language of test data.
    In file adapter go to encoding select TEXT and  UTF-8.
    may be this will works.
    regards
    sandeep.

  • Prevent Sender File Adapter from retrying an error file

    Hi,
    I have a situation where there a number of source files[100+] to be picked from a source directory. The files are then processed by an adapter module before they are sent to the IE. Now, in the lot to be picked up there are files which do not conform to the input file structure validations in the module and consequently these would not[and should not] be picked. These files could occur anywhere in the input set and presently the adapter is re-trying the processing of these error files, with the result that the subsequent files are not processed.
    Is there a method to ensure that the entire input file set is processed regardless of the adapter encountering error files in between?
    Thanks,
    Anand

    Yes,
    In your sender communcation channel, you must activate  "Archive faulty source files" flag and indicate a directory for archiving files with errors.
    Regards,
    Carme

  • Character conversion in File Adapter leads to Mapping Error

    Hello experts,
    I have a problem with file encoding on the file sender adapter. The scenario I'm using just reads a flat file and maps each line of this file to an Idoc field. Normally this works perfect but from time to time we get files contaning the character "'" (dec. 39 or hex 27) which then end up in a mapping exception. In the adapter configuration we use file content conversion, File Type is set to "text" and we haven't set any encoding.
    When I look at the generated XML then I can see that it created a UTF-8 encoding (default) and the "'" has been replaced by "&apos;".
    I tried to load this XML into the mapping in test mode and it faild as well. Only if I change the XML encoding to "ISO-8859-1" it goes through. If I set "ISO-8859-1" as encoding on the sender adapter, it doesn't make any difference.
    What am I doing wrong here and why is character dec 39 affected at all? From my understanding this is in the normal ASCII table between 1 and 128 and should not cause any problem! In the same file I can also see the "&" (dec 38 or hex 26) which is converted in the XML to "&amp;" and works perfect.
    I'd appreciate any helpful statements...
    Thanks in advance
    /Michael

    From your description I would guess that not the apostrophe causes the trouble, but there is any European letter in your source which is not part of ASCII like an German umlaut. Otherwise it should not make any difference whether you use UTF-8 or latin-1 for encoding.
    Could you send me the file that makes the trouble to my email address stefan dot sdn at gmail dot com?
    Regards
    Stefan

  • OSB Error in deploying a project with jca file adapter

    Hi,
    I am facing an issue where I am getting an error when deploying a service from Eclipse. I am using OSB/SOA 11.1.1.5 2 node cluster. I have an OSB service where I am writing to a file and am using file adapater. I created a composite with file adapter to write a file then imported .jac, .wsdl and composite into eclipse and generated a business service out of .jca file. When I deploy the project from eclipse I am getting the below error and am not able to deploy the project.
    Conflicts found during publish.
    Invalid JCA transport endpoint configuration, exception: javax.resource.ResourceException: Cannot locate Java class oracle.tip.adapter.file.outbound.FileInteractionSpec
    Cannot locate Java class oracle.tip.adapter.file.outbound.FileInteractionSpec
    I have FileAdapter deployed and pointed to OSB manage servers cluster. Here is a snippet of config.xml.
    <app-deployment>
        <name>FileAdapter</name>
        <target>SOA_Cluster,OSB_Cluster</target>
        <module-type>rar</module-type>
        <source-path>/app/oracle/fmw/Oracle_SOA1/soa/connectors/FileAdapter.rar</source-path>
        <deployment-order>321</deployment-order>
        <plan-dir xsi:nil="true"></plan-dir>
        <plan-path>/app/oracle/shared/SOA_Cluster/dp/FileAdapterPlan.xml</plan-path>
        <security-dd-model>DDOnly</security-dd-model>
        <staging-mode>nostage</staging-mode>
      </app-deployment>
    Also inside console -> deployments  -> FileAdapter -> Targets and OSB_Cluster is checked also.
    Here is the .jca file
    <adapter-config name="writeFile" adapter="File Adapter" wsdlLocation="writeFile.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
      <connection-factory location="eis/HAFileAdapter"/>
      <endpoint-interaction portType="Write_ptt" operation="Write">
        <interaction-spec className="oracle.tip.adapter.file.outbound.FileInteractionSpec">
          <property name="PhysicalDirectory" value="C:\ORACLE"/>
          <property name="Append" value="false"/>
          <property name="FileNamingConvention" value="a_%SEQ%.doc"/>
          <property name="NumberMessages" value="1"/>
        </interaction-spec>
      </endpoint-interaction>
    </adapter-config>
    Any idea what might be wrong.
    Thanks.

    I already have the fileAdapter JNDI is already configured in console. The error I am getting is during the deployment
    Conflicts found during publish.
    Invalid JCA transport endpoint configuration, exception: javax.resource.ResourceException: Cannot locate Java class oracle.tip.adapter.file.outbound.FileInteractionSpec
    Cannot locate Java class oracle.tip.adapter.file.outbound.FileInteractionSpec
    Thanks

  • Receiver file adapter not functioning

    Hi guys,
    We have developed some interfaces that are exporting some .txt files in ftp locations and therefore they make use of receiver file adapter. Although the receiver file adapter used to function properly some days ago, for some strange reason, it stopped receiving any files. This happens only in XI development system but not in XI production system. In XI development, in Runtime Workbench --> Communication Channel monitoring, I can see this communication channel's status as correctly configured and started, with a green sign on the right, but it is not responding when some files are sent to it, and therefore there are no output files in target directory.
    Any ideas?? It is urgent.
    Best Regards
    Evaggelos

    Udo,
    Hi Amit,
    I went into Message Monitoring for this interface and I can see all the messages for the last 24 hours that should be written into a file that have status "to be delivered".
    When I go into Details -->Audit Log  for a single message:
    2007-06-13 11:49:33 Success Processing child message of multi-message with message ID ff896d50-198a-11dc-cdfa-00145e694b16
    2007-06-13 11:49:33 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
    2007-06-13 11:49:33 Success Message successfully put into the queue.
    And in Message Data there is the following information:
    Status To Be Delivered
    Repeatable Yes
    Cancelable Yes
    Error Category  
    Error Code  
    Start 13.06.2007 11:49:33
    End  
    Sender Party  
    Sender Service TPBS_GR
    Receiver Party  
    Receiver Service TPBS_GR
    Interface http://famar.gr:LoyaltyDataMNSToSRS
    MI_LoyaltyDataMNSToGR_IB
    Quality of Service Exactly Once
    Message b2685674-7626-5141-bfa1-13155ad0d25a
    Reference  
    Conversation ID  
    Serialization Context  
    Direction INBOUND
    Message Type Recv
    Profile XI
    Connection File_http://sap.com/xi/XI/System
    Transport HTTP
    End Point http://fmgralxi01:50000/MessagingSystem/receive/AFW/XI
    Authorization  
    Sequential Number 0
    Number of Retries 3
    Failed 0
    Retries 300000
    Valid to  
    Persist Until 13.07.2007 11:49:33
    Schedule Time 13.06.2007 11:49:33

  • File Adapter failed to write a file

    Greetings,
    I have a simple file adapter that writes information from a message in a pipe-delimited format. During an execution I got the following error:
    file:/D:/OraBPELPM_1/integration/orabpel/domains/default/tmp/.bpel_BPELProcessAppendFile_1.0.jar/AppendFileAdapter.wsdl [ Write_ptt::Write(Root-Element) ] - WSIF JCA Execute of operation 'Write' failed due to: Translation Error. Error while translating message to native format. ; nested exception is: ORABPEL-11017 Translation Error. Error while translating message to native format. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
    I coudn't find a before mentioned error stack in any of log file. This message is all I get and it's not enough to figure out why it fails. Any advice?
    Thank you.

    False alarm. I had incorrect mapping between BPEL variables.

  • File adapter write to network drive fails

    Hi all,
    I have a problem using the FIle adapter. The situation is as follows:
    - SOA Suite 10.1.3.5.0. installed on Windows
    - SOA Suite runs under windows user soaadmin, a user with local admin rights.
    - A network share is mapped as a network drive on a remote (windows) server, assigned drive letter 'T'.
    - user soaadmin is added to a user group on the remote server that has local admin rights on the remote server.
    - In my BPEL process, the file adapter is configured to write files to 'T' drive.
    - At runtime, ORABPEL-11054 occurs: Directory cannot be created successfully. Directory: T:/ cannot be created successfully.
    - If I configure the file adapter to write to 'C' drive all functions well.
    - From the windows explorer, user soaadmin can create files on 'T' successfully soa apparently has the right privileges on 'T'.
    Any clue as to what may be wrong?
    Thanks in advance,
    Regards Rob

    please use FTP adapter instead of File Adapter.
    Thanks,
    Chandra_

  • XI3.0 Receiver file adapter write to windows shared drive

    Hi,
    Our XI server SP09 currently runs on windows 2003 server,  I wish to use the receiver file adapter to create a file on another windows server.  I have created a folder on the other server and set permissions so that anyone can read and write to it. 
    The communication channel has been set-up with a target directory of //server/shared_folder/folder and a transport protocol of 'File system(NFS)'
    When I try and send an XML message to the file adapter I get the following error on the runtime workbench :-
    Last message processing started 09:47:10 2005-06-09, Error: Message processing failed with java.lang.Exception: Message processing failed - configuration error in file receiver adapter (Directory does not exist / cannot be created)
    My questions are as follows :-
    a) Do I have the target directory on the communication channel set-up correctly?  i.e. do I use / or \
    b) What username will need to be set-up on the other server so that the file adapter can write to the shared folder
    c) Is there another way of providing user and password information for connecting to the other server?
    Many thanks
    Ian

    Hi Ian
      as i understood from ur description is that u want ur file to b generated in some other machine then u have to mention that machine in ur SLD using correct specification..
    u go thru this link in order to get more Clearance..
    http://help.sap.com/saphelp_nw04/helpdata/en/31/f0ff69551e4f259fdad799a229363e/frameset.htm
    Hope this ll help u.
    Regards
    Shailesh

  • DB Mutex Error with Outbound operation using Normal File adapter in HA env

    Hi All,
    I Have a simple process which picks data from a weblogic jms queue and writes it to a file. Each day this task is carried out once in a day and it writes approx 30k records to the file. the process is made singleton (singleton property on inbound JMS adapter) and used the HA file adapter to write to the file. This setup gave rise to lot of DB Mutex errors. To avoid the DB mutex issue i pointed the file adapter to use the Normal file adapter connection factory instead of the HA File adapter one used earlier. The surprising thing is even this gave rise to DB mutex errors.
    1. Am i missing something here,according to my understanding using a normal file adapter conn factory even in a HA environment should not be creating multiple locks on the file write.
    2. Can i change the standard DS used in the file adapter to a custom DS? will that solve the problem?
    I hope the scenario is clear. Following is the error extract seen at the process and log level
    Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Write' failed due to: Unable to acquire mutex for interaction. Unable to acquire mutex for interaction. Unable to acquire lock on resource for "DatabaseMutex::acquireNoSave". ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
    Thanks
    Nikhil

    We are getting the same error in 11.1.1.5 PS4 version also.Can you post the content of your .jca file here?
    Regards,
    Anuj

  • Outbound file adapter for multiple record write

    am using jdev 10.1.3.1
    and SOA suite 10.1.3.1
    I am trying to read a table and write the records to a csv file.
    The bpel process I have constructed is :
    receive > assign input value to table select parameter > select records from table > assign table select output values to file input value > invoke file adapter to write a csv file > assign a literal to process out value.
    when i execute this process it is showing me an error on the file adapter invoke activity.
    the error is :
    </part></Invoke_2_Write_InputVariable></input><fault><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>null</code>
    </part><part name="summary"><summary>file:/C:/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_TableReader_1.0_594707f7f819a3a4a2002c98afbd42fa.tmp/WritePersonFile.wsdl [ Write_ptt::Write(People) ] - WSIF JCA Execute of operation 'Write' failed due to: Translation Error.
    Error while translating message to native format.
    ; nested exception is:
         ORABPEL-11017
    Translation Error.
    Error while translating message to native format.
    Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
    </summary>
    any help would be appreciated.
    thanks

    Hi,
    In your case, to write any data to a file, you need to define/use a schema when you are using a file adapter.
    Cheers,
    Abhi

  • File Adapter - Exception / Error handling

    We are using File Adapter in BPEL process to read multiple records from the file. Additionally, we have also handled rejectedMessageHandlers & fatalErrorFailoverProcess exception to lunch custom BPEL process. The process is running fine and also successfully launches custom handler processes too.
    Need help / direction in addressing following issues.
    1. While reading from file, if a records errors out, the custom BPEL process is launched (as specified in rejectedMessageHandlers property). In such instance, the previously read valid records are processed but remaining records are marked as errored out. Our requirement is to make entire record set as invalid and would like to perform rollback of entire process.
    2. Whenever an error occurs during reading the records using File adapter, the associated data file is being deleted from the input directory and also NOT available in archive directory also.
    Are we missing any set up ? We are on 10.1.3.1
    thanks
    -Yj
    Sample Log file:
    <2009-04-20 11:46:14,080> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::init - Initializing the JCA activation agent, processId='bpel://localhost/default/TestFileRead~1.0/
    <2009-04-20 11:46:14,080> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::initiateInboundJcaEndpoint - Creating and initializing inbound JCA endpoint for:
    process='bpel://localhost/default/TestFileRead~1.0/'
    domain='default'
    WSDL location='Read.wsdl'
    portType='Read_ptt'
    operation='Read'
    activation properties={portType=Read_ptt, rejectedMessageHandlers=bpel://default|AdapterError2|initiate|payload}
    <2009-04-20 11:46:14,096> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - endpointActivation for portType=Read_ptt, operation=Read
    <2009-04-20 11:46:14,143> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Endpoint Activation called in File Adapter for endpoint: c:\temp\yj
    <2009-04-20 11:46:14,143> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - successfully completed endpointActivation for portType=Read_ptt, operation=Read
    <2009-04-20 11:46:30,580> <WARN> <default.collaxa.cube.activation> <File Adapter::Inbound> PollWork::run exiting, Worker thread will die
    <2009-04-20 11:47:14,158> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Translated inbound batch index 1 of file {testdata6.txt} with corrupted message count = 1
    <2009-04-20 11:47:14,158> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Sending message to Adapter Framework for rejection to user-configured rejection handlers : {
    fileName=C:\temp\yj\testdata6.txt, startLine=3, startColumn=1, endLine=-1, endCol=-1, Exception=ORABPEL-11168
    Error while reading native data.
    [Line=3, Col=5] Expected "|" for the data starting at the specified position, while trying to read the data for "element with name C2", using "style" as "terminated" and "terminatedBy" as "|", but not found.
    Ensure that "|", exists for the data starting at the specified position.
    <2009-04-20 11:47:14,158> <WARN> <default.collaxa.cube.activation> <AdapterFramework::Inbound> [Read_ptt::Read(Root-Element)]onReject: Sending invalid inbound message to Exception Handler: bpel://default|AdapterError2|initiate|payload
    <2009-04-20 11:47:14,315> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Setting last error record to : -1
    <2009-04-20 11:47:14,658> <ERROR> <default.collaxa.cube.activation> <AdapterFramework::Inbound> onBatchFailure: Batch 'bpel://localhost/default/TestFileRead~1.0//testdata6.txt_1240205493408' (C:\temp\yj\testdata6.txt) has failed due to: ORABPEL-11168
    Error while reading native data.
    [Line=3, Col=5] Expected "|" for the data starting at the specified position, while trying to read the data for "element with name C2", using "style" as "terminated" and "terminatedBy" as "|", but not found.
    Ensure that "|", exists for the data starting at the specified position.

    Any light / idea on the following issue ?
    1. While reading from file, if a records errors out, the custom BPEL process is launched (as specified in rejectedMessageHandlers property). In such instance, the previously read valid records are processed but remaining records are marked as errored out. Our requirement is to make entire record set as invalid and would like to perform rollback of entire process. Even, if we do not configure rejectedMessageHandlers, the behavior is that valid rows are processed with the rest of BPEL process and for Invalid rows, the records are rejected. Our requirement, is that, even if there is one invalid record, the entire set of record should NOT move ahead with the BPEL process
    2. Whenever an error occurs during reading the records using File adapter, the associated data file is being deleted from the input directory and also NOT available in archive directory also. Note, in case of all valid record the file is available in archive directory

  • How to use File Adapter Receiver to write attachments

    Hi,
    i have a scenario, in which our own XInotes adapter sends an XIMessage from an IBM Lotus Notes database into XI. This XIMessage contains an XML document as application main document and several PDF files as additional attachments 
    On the receiver side, i must use a File Adapter to write both the XML documents and the PDF attachments into a directory.
    The problem is i don't know how to use the file adapter receiver to write the attachments. In the Channel Monitoring, i can see that all PDF files are transferred to the file receiver. But the file adapter writes only the XML document into the directory.
    I've also tried the AF_Modules/PayloadSwapBean, but it can only swap one PDF file into the application payload. And the file name must be hard coded in the module configuration as swap.KeyName.
    Could anyone give me any ideas?
    thanks a lot in advance
    Xiang

    hi,
    receiver file adapters do not supprt attachments.
    Only File Sender adapter is capable of handling attachments not the receiver.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/4b/a20c4cfea96b498b1e1af3f32f0670/frameset.htm
    Configuring the sender FILE adapter
    The sender file adapter is configured to pick the normal payload (file1.xml), which is specified in the File
    access parameters, and the additional image file (file1.jpg) that is to be sent as an attachment is configured
    under the Additional File(s) as shown in the screenshot below. The file type would still remain binary.
    Since, by default, XI sends payload and attachments in XML format, we need to call two beans, namely the
    MessageTransformBean and the PayloadSwapBean to help us is transforming the content to jpeg format
    and also change the file extension.
    The PayloadSwapBean module is used to replace the application payload of the XI message that holds the
    data with another payload which is appended to the message as an attachment. In our case, the payload
    would be file1.xml whereas the attachment would be file1.jpg
    The swap module is denoted in our scenario with the module key ‘swap’. It has two parameters from the
    MIME header.
    regards,
    pradeep.

Maybe you are looking for