ESB File Adapter data validation issue

I have a really simple ESB process.
File Adapter Read
(XML format with XSD) --> Routing Service --> SOAP Call to BPEL Process
Quite simply, the ESB uses the File Adapter to read an XML file which has an associated XSD. The contents are then routed to a BPEL Process.
If the XML file is valid in syntax but contains an element which is not in the XSD, the file contents are pushed to the BPEL process which has validateXML set to true - thus the error is caught and handled by the BPEL process.
This is what I want to happen.
If the XML file is invalid in syntax - for example -
<TAG>hello</WRONGTAG>
The ESB process rejects the file and stops dead.
I would rather the invalid file is pushed to the BPEL so that the BPEL can handle the error.
Why?
Because my error handling in the BPEL picks up the invalid XML format and emails the users to inform them there is a problem.
Can someone help? Is this possible? Thanks.
Message was edited by:
IanBaird

Hello again! You are now aware of the problem as there has been a lot of conversation between myself and Dave Berry [and you!] regarding this issue.
For the rest of the readers - here is a brief summary of progress so far. Sorry but there has been so much communication that I think the best way is to direct you to various links.
If an adapter fails in ESB, then it is possible to trap these failures and handle them as documented here:
Dave Berry said:
you need to look into the adapter rejection handlers which are documented on OTN ESB page in the exception handling lesson and the adapters OTN dev resources page http://www.oracle.com/technology/products/integration/adapters/dev_support.html
I had also devised my own solution in the meantime, which involves reading the input file as opaque schema and passing this to a BPEL process which converts it to an XML document! This can then be validated and use standard BPEL error handling to find any problems in the file format etc.
See my blog for a tutorial on doing this:
http://soastuff.wordpress.com/2007/06/06/handling-opaque-datatypes-in-bpelesb/
The only problem with this at the moment is that the BPEL function ora:parseEscapedXML has a bug in it - so it fails if the XML does not comply with the XSD it tries to convert to.
This in turn causes an ORABPEL-09500 error which does not seem to get handled by the BPEL process so the process fails.
As things stand, this bug remains - though Dave Berry has been very helpful in identifying it and bringing it to Muruga's attention. Hopefully we can get a fix (?) and a workaround whilst the fix is being implemented (?)
Cheers.

Similar Messages

File Adapter : read XML file with data validation and file rejection ?

Hello,
In order to read a XML file with the file adapter, I have defined a XSD that I have imported to my project.
Now the File Adapter reads the file correctly but it does not give an error when:
- the data types are not valid. Ex: dateTime is expected in a node and a string is provided
- the XML file has invalid attributes.
How can I manage error handling for XML files ?
Should I write my own Java XPath function to validate the file after is processed ? (here is an example for doing this : http://www.experts-exchange.com/Web/Web_Languages/XML/Q_21058568.html)
Thanks.

one option is to specify validateXML on the partnerlink (that describes the file adapter endpoint) such as shown here
<partnerLinkBinding name="StarLoanService">
<property name="wsdlLocation"> http://<hostname>:9700/orabpel/default/StarLoan/StarLoan?wsdl</property>
<property name="validateXML">true</property>
</partnerLinkBinding>
hth clemens

Listener on ESB file adapter does not appear to listen

I am new to the world of SOA, ESB, and BPEL and am starting with something simple such as reading a file from one directory performing a data transformation and writing the file to a different directory. I understand that Oracle's ESB and BPEL are very similar in functionality. I have successfully been able to read files in using a file adapter and listener in BPEL. When I try to set up a new ESB application with a file adapter and listener in ESB, I register the project with the Integration Server without any problems, and am able to see all components in the ESB Control. When I drop a new file into the directory that the adapter is attached and listening to, nothing happens. The file is not picked up and there are no new instances of any ESB services. Am I missing something? Is there a log that could be checked to see if the service is even checking the directory?
Along the same lines, I am wondering if there is an easy way to update the directory that is being listened to once the service has been registered/deployed (with either ESB or BPEL). Is there a config file that someone other than a developer could update without having to redeploy the service again.
Any help would be greatly appreciated. Thanks.

What platform are you running and what install option did you use, basic or advanced?
There are known issues with adapters enabling automatically on Linux that require you to restart the container. See Re: Changing File Adapter target directory - container bounce required?
You can change the polling directory by following the instructions in this thread.
Changing File Adapter target directory - container bounce required?

Process multi-record & multi-record-format files using ESB & File Adapter

I am looking to process/parse an in-bound file with the following make-up and to load into a database table using the File Adapter, ESB and DB Adapter.
File Make-Up:
- each line in the file is a record
- each record is made up of 12 fields
- there are multiple record types denoted by the first field in the line
- record types may or may not have common fields
- where there are common fields, the field may be in different columns
- each record is to be inserted into a database table
Sample File:
3,,"03-0243-0188132-00",.20,26,075,"","000000006026","","","22/04/08",03 1303
3,,"03-0243-0188132-00",20.00,26,075,"","","","","22/04/08",03 0579
5,,"03-0243-0188132-00",99.60,,,"OPENING BALA",,,"ACME GROUP","22/04/08",
6,,"03-0243-0188132-00",99.60,,,"CLOSING BALA",,,"ACME GROUP","22/04/08",
8,,"03-0243-0188132-00",-346119.05,16,000,"DEBITS",,,,"22/04/08",
8,,"03-0243-0188132-00",346119.05,349,050,"CREDITS",,,,"22/04/08",
9,,"03-0243-0188132-00",-346119.05,16,000,"DEBITS",,,,"22/04/08",
9,,"03-0243-0188132-00",346119.05,349,050,"CREDITS",,,,"22/04/08",
Record Types and corresponding format:
3, Corp ID, A/C Number, Trans Amt, Serial Number, Trans Code, Particulars, Analysis Code, Reference, Other Party Name, Transaction Date, Originating Bank
5, Corp ID, A/C Number, Opening Balance, Serial Number, Trans Code, Particulars, Analysis Code, Reference, Other Party Name, Transaction Date, Originating Bank
6, Corp ID, A/C Number, Closing Balance, Serial Number, Trans Code, Particulars, Analysis Code, Reference, Other Party Name, Transaction Date, Originating Bank
8, Corp ID, A/C Number, Amount, Number, 000, “DEBITS”, Analysis Code, Reference, Other Party Name, Transaction Date, Originating Bank
8, Corp ID, A/C Number, Amount, Number, 050, “CREDITS”, Analysis Code, Reference, Other Party Name, Transaction Date, Originating Bank
9, Corp ID, A/C Number, Amount, Number, 000, “DEBITS”, Analysis Code, Reference, Other Party Name, Transaction Date, Originating Bank
9, Corp ID, A/C Number, Amount, Number, 050, “CREDITS”, Analysis Code, Reference, Other Party Name, Transaction Date, Originating Bank
Please note that record types 8 and 9 have 2 fixed fields.
I have tried playing around with the File Adapter and the ESB but not having much luck. Can someone provide any suggestions on how I can handle this?

James,
Thanks for your prompt response. I have come across your post previously.
Please excuse my in-experience (very new to SOA and Oracle SOA Suite) but i have not understood how your post regarding the manual creation of an XSD will assist with my problem. Could you possibly further elaborate on the overall approach i should be taking?
Regards,
Simon

Receiving file adapter content conversion issue

Guys,
Could someone please help me with a Receiving file adapter issue?
My output structure is something like this:
Vendor_file_MT (occurence 1)
--Recordset (occurence 0..unbounded)
Vendor (occurence 1)
Field1
Field2
Field3
Field73
Field74
My content conversion is very simple:
Recordset Structure: Vendor
Parameters:
Vendor.fieldFixedLengths   30,30,30, (...) ,1,27
Vendor.fixedLengthTooShortHandling   Cut
Vendor.endSeparator   'nl'
If I don't do the content conversion, it works fine, I get all the fields in the XML format.
When I do the content conversion however, I get multiple lines but only the very first field of each line.
What could be the problem? What am I missing here? Any idea?
Your help would be much appreciated.
Thanks,
Viktor

Varga:
Its little strange that its not working even after adding that. Did you check the receiver channel in your RWB for any logs. Add the statement in my previous post and Also try to clear the Cache and activate the channel again..See if it works
Glad it worked
Edited by: Guru on Apr 21, 2008 3:15 PM

File Adapter Data Compression

I'd like to extend file adapter behavior to add data compression features like unzip after read file and zip before write file. I read oracles's file adapter documentation but i didn't find any extension point

if its java mapping, just create a DT with any structure as you wish.
ex.
DT_Dummy
|__ Dummy_field
java mapping does not validate the xml against the DT you created

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 - XML files containing multiple messages

Hi,
In all the examples on file adapters I read, if files contain multiple messages, it always concerns non-XML files, such as CSV files.
In our case, we have an XML file containing multiple messages, which we want to process separately (not in a batch). We selected "Files contain Multiple Messages" and set "Publish Messages in Batches of" to 1.
However, the OC4J log files show the following error:
ORABPEL-12505
Payload Record Element is not DOM source.
The Resource Adapter sent a Message to the Adapter Framework which could not be converted to a org.w3c.dom.Element.
Anyone knows whether it's possible to do this for XML files?
Regards, Ronald

Maybe I need to give a little bit more background info.
Ideally, one would only read/pick-up small XML documents in which every XML document forms a single message. In that way they can be processed individually.
However, in our case an external party supplies multiple messages in a single batch-file, which is in XML format. I want to "work" on individual messages as soon as possible and not put a huge batch file through our ESB and BPEL processes. Unfortunately we can not influence the way the XML file is supplied, since we are not the only subscriber to it.
So yes, we can use XPath to extract all individual messages from the XML batch-file and start a ESB process instance for each individual message. But that would require the creation of another ESB or BPEL process which only task is to "chop up" the batch file and start the original ESB process for each message.
I was hoping that the batch option in the File adapter could also do this for XML content and not only for e.g. CSV content. That way it will not require an additional process and manual coding.
Can anyone confirm this is not supported in ESB?
Regards,
Ronald
Message was edited by:
Ronald van Luttikhuizen

Can we read a ZIP file through ESB file adapter?

Hi,
Is it possible to read a ZIP file from a specified locaiton either through a FTP adapter or file adapter as a opaque element and place it in another specified locaiton?
So far the available options are to read a txt, csv, fixed length or cobol file.
I tried to create a ESB reading ZIP file and place it in another locaiton. but it was not reading the ZIP file.
Is it first possible for the ESB to read the ZIP file? if so then is there any specific configuratuion that we have to do for it to work?

how can we read a MSWORD file through java?You can read it like any other file using FileInputStream
and similar.
Howvere, if you want do do something with it, like display
it, you have a problem. AFAIK Microsoft do not release
information about their document formats, and i have not
seen a .doc viewer for java.

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

ESB file adapter on shared directory

Hi
I am trying to use file adapter on a mapped network drive, windows machine.
I am getting this error:
ORABPEL-11001
Invalid Input Directory.
The value specified for the input (Physical/Logical)Directory activation parameter has an invalid value "O:\BCRSignatures"
Ensure that the following conditions are satisfied for the input directory :
1) It exists and is a directory (not a file). and
2) It is readable (file read permissions). and
3) If activation parameter "DeleteFile" is set to "true" then the directory should also have granted write permissions. and
4) If using a logical name, then ensure that the mapping from logical name<->physical directory is correctly specified in the deployment descriptor
The location is accesible for read and write within Windows.
The error persists even with "no delete files after processing" and "no archive processed files", options.
Any ideeas? Sugestions?
Metalink is poor on this.
Thank you,
Liviu

HI BPEL Gurus,
Everytime i m facing ORABPEL-11001 Errors . I dont know why its coming.can u someone give suggestion to this regards. i attach the logs as follows
<2007-11-23 09:53:29,825> <INFO> <dev.collaxa.cube.activation> <File Adapter::Inbound> Recovery still not possible after 151110 attempts due to ORABPEL-11001
Invalid Input Directory.
The value specified for the input (Physical/Logical)Directory activation parameter has an invalid value "D:\igefi\bpelinterfaces\mfond\dev\Wrk_Imp_Swap_Price\WORKDIRS\input".
Ensure that the following conditions are satisfied for the input directory :
1) It exists and is a directory (not a file). and
2) It is readable (file read permissions). and
3) If activation parameter "DeleteFile" is set to "true" then the directory should also have granted write permissions. and
4) If using a logical name, then ensure that the mapping from logical name<->physical directory is correctly specified in the deployment descriptor.
the above message i m getting in domain.log and opmn.log
Regards
Hameed

BPEL File Adapter Logical Path Issue

I am trying to write the BPEL Error Messages using a file adapter. But I could not parameterize the logical directory. I need a solution of changing it in the BPEL console after deploying it
I am Invoking a FileAdapter Web service using logical direcotry, in the FileService partnerlink I set the file_loc property with type"LogicalDirectory" and set the value to " D:/BPEL_Errors" etc. This is working fine but except in the BPEL Console I could not edit it, All the Partner Link properties seems to be read only and not editable. I tried creating a user property for the BPEL process which can be editable but How do I refer this user property in partner link since I cannot use XPATH expression there?.
I guess this should be a very generic problem all I am looking for is parameterizing the File Location. Any Ideas?
Thanks,
Chitra

Thanks James. It would be really nice if the first option works, do you have any idea why its not editable. I am having the following in bpel.xml
<partnerLinkBinding name="FileService">
<property name="wsdlLocation">FileService.wsdl</property>
<property name="BPEL_LOG">D:\JDeveloper\jdev\mywork\BPEL_LOG</property>
When I deploy the above, In the console I see BPEL_LOG as non editable field. Is am doing anything wrong?.
Regarding the second option , I guess you are talking about modifying the Outbound message header by adding a new property called directory, as mentioned in the following link.
http://download.oracle.com/docs/cd/B31017_01/integrate.1013/b28994/adptr_file.htm#CACFFAHI
Since there are many bpel processes which use the fileservice, I need to edit the fileAdapterOutboundHeader.wsdl in multiple places. Please let me know whether I can make the first option to work

File Adapter - Schema Reference Issue

Hi Experts,
I am working on project in SOA Suite 11.1.1.6
The project has a File Adapter which writes the files to a particular destination.
Following is the WSDL of WRITE File Adapter :
<wsdl:definitions name="QCCCEQFileWriteOutbound"
targetNamespace="XXXXXXXXX"
xmlns:tns="XXXXXXXXX"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:opaque="http://xmlns.oracle.com/pcbpel/adapter/opaque/"
xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
<plt:partnerLinkType name="Write_plt">
<plt:role name="Write_role">
<plt:portType name="tns:Write_ptt"/>
</plt:role>
</plt:partnerLinkType>
<wsdl:types>
<schema targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/opaque/"
xmlns="http://www.w3.org/2001/XMLSchema">
<element name="opaqueElement" type="base64Binary"/>
</schema>
</wsdl:types>
<wsdl:message name="Write_msg">
<wsdl:part name="opaque" element="opaque:opaqueElement"/>
</wsdl:message>
<wsdl:portType name="Write_ptt">
<wsdl:operation name="Write">
<wsdl:input message="tns:Write_msg"/>
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>
When the process is running on TST server, if DEV server is DOWN its throwing this error:
<bindingFault>
<part name="summary">
<summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Write' failed due to: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.file.outbound.FileInteractionSpec due to: XSD Resolution problem. XSD Resolution problem. Unable to load Translation schemas from for http://xmlns.oracle.com/pcbpel/adapter/opaque/ due to: Unable to lookup schema for 'http://xmlns.oracle.com/pcbpel/adapter/opaque/' Please make sure all used XML schemas are imported/included correctly. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary>
</part>
<part name="detail">
<detail>Tried all: '1' addresses, but could not connect over HTTP to server: 'XXXdev.XXXXXXXX.com', port: '80'</detail>
</part>
<part name="code">
<code>null</code>
</part>
</bindingFault>
Why is Test File Adapter WSDL is trying to connect DEV Server. I haven't added anything specific is File Adapter WSDL its the default generated WSDL of File Adapter. I am also not using MDS in project
Please help me in this regards. Thanks in Advance.

Hi Mathieu, Vijay,
Here is the import and reference of File Write Adapter which is failing from composite.xml. It doesn't have any DEV references as its an Adapter pointing to JCA file.
<import namespace="http://xmlns.oracle.com/pcbpel/adapter/file/XXX/XXXXProcess/XXXFileWriteOutbound"
location="XXXFileWriteOutbound.wsdl" importType="wsdl"/>
<reference name="XXXFileWriteOutbound"
ui:wsdlLocation="XXXFileWriteOutbound.wsdl">
<interface.wsdl interface="http://xmlns.oracle.com/pcbpel/adapter/file/XXX/XXXProcess/XXXFileWriteOutbound#wsdl.interface(Write_ptt)"/>
<binding.jca config="XXXFileWriteOutbound_file.jca"/>
</reference>
There are other references which are pointing to DEV, which I replacing with deployment plan. This service is failing at the Adapter call with the message i mentioned in initial post.
I checked the WSDL Binding in System Mbean Browser - the values are properly replaced with TST URIs.
Please share your thoughts, thanks again for your response.

JBO-JHS-00114: JHS-00114: Unknown date validation issue

Hi,
I am facing a strange issue while filling date field values in certain pages of application.
I have assigned Date Format to 'MM/dd/yyyy' at Service level in Jheadstart app structure definition .I have custom datefield velocity template to display hint along with data field.I assigned this to FORM_DATE_FIELD template.
Now I generated pages in my application. All pages works as expected except couple of pages.Even though I enter valid value in date field, It throws me an error "JBO-JHS-00114: JHS-00114: Date 09/04/2007 must be of format dd-MMM-yyyy ".
I could not quite understand where it is picking up this special format?
I went through generated JSPX file code, it is fetching from nls.datepattern.This code is same across all pages.Then where is this error coming from?
Thanks.

Here is custom date velocity template,
<af:selectInputDate #ITEM_ID_IN_FORM() #ITEM_VALUE_IN_FORM() #ITEM_PROMPT_IN_FORM()
#ITEM_PARTIAL_TRIGGERS() #ITEM_REQUIRED_IN_FORM()
#ITEM_READ_ONLY_IN_FORM() #ITEM_RENDERED_IN_FORM()
#ITEM_DISABLED_IN_FORM() tip="(mm/dd/yyyy)" #DEPENDS_ON_ITEM_PROPS_FORM()>
<af:convertDateTime pattern="#{nls.datepattern}"/>
</af:selectInputDate>

Receiver File Adapter Module processor issue

Hello all,
I have deployed (using SDM) a specific module for one of my file communication channel.
In MDT, I have the following error :
Exceptions survenues pour Adapter Framework : Object not found in lookup of Module0001
La diffusion du message vers l'application via File_http://sap.com/xi/XI/System a échoué en raison de : com.sap.aii.af.ra.ms.api.RecoverableException: Object not found in lookup of Module0001.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of Module0001.
Where can be the source of this problem ?
Thanks a lot

Jean
Also check if the "JNDI" name that you have specified in the Receiver Adapter module
excluding localejbs matches the deployed name in the "J2ee Aministartor Deploy service.
for example if you have
localejbs/sap.com/BeanName
you should have
the service deployed under
/sap.com/BeanName
regards
krishna

ESB File Adapter data validation issue

Similar Messages

Maybe you are looking for