Question on Native XML Builder

Hi everyone,
I am working in SOA11g, using File Adapter component and then using Native XML Builder to convert a cobol copy book file to native xml file.
I have chosen the option to create New> Create cobol copy book to native xml
- I gave the file name with .txt extension.
- Entered TargetNamespace
- Root-Element: Root-Element
- Character Set: UTF-8
- Big endian
Records Delimiter: End of Line ($eol)
Is something wrong with these entries, I get an error 'Unable to generate native format': Is there a way to get the detailed error description.
Please advice.
Thanks.

Hi,
You need to target the cobol copy book schema file, not the data file (just to be sure because it is not clear from the ".txt" extension)
Also, if the schema file is not compliant to Jdev then it will show this kind of error.
Check that all the declarations made in the schema file are supported by Jdev native builder (particularly the iteration one).
http://docs.oracle.com/cd/E23943_01/integration.1111/e10231/nfb.htm#BGBDBFEH
good luck,
mathieu

Similar Messages

Native Format Builder in File Adapter - NXSD:ConditionValue

Hello,
I am trying to build a schema using the Native Format Builder in the File Adapter. I am using the option "Multiple Records of different types"
The CSV file will look like the one shown below, the first column will have either DS, Shipping or an alpha numeric value (not a static value). How should the condition value look like for a dynamic value?
<xsd:element name="RECORD1" nxsd:conditionValue="OrderDetailSKU"> - Static value, the value SKU will not change
*<xsd:element name="RECORD2" nxsd:conditionValue="1"> - This value differs per order, it can be any number or alphabet or a combination of a number and an alphabet*
<xsd:element name="RECORD3" nxsd:conditionValue="DS"> - Static value, the value SKU will not change
<xsd:element name="RECORD4" nxsd:conditionValue="Shipping"> - Static value, the value SKU will not change
SKU,VendorID,PurchaseOrderNumber,RefNum,OrderStatus,Invoice#,InvoiceAmt,FreightCharge,ProcessingFee,Qty,QtyOrdered,QtyShipped,Price,Net,TotalNoBoxes,BoxNo,BoxWeight,BoxWidth,BoxHeight,BoxLength,ShipMethod,TrackingNumber,StatusDate
1,266219,648290074,648290074,Shipped,648290074,17,0,0,1,1,1,15,17,1,1,5,,,,UPSG,,
DS,,648290074,648290074,Shipped,648290074,17,0,0,1,1,1,2,17,1,1,5,,,,UPSG,,
Shipping,,648290074,648290074,Shipped,648290074,17,0,0,1,1,1,0,17,1,1,5,,,,UPSG,1Z4R3E350366250200,
1,,648290075,648290075,Shipped,648290075,77,0,0,5,5,5,15,77,1,1,11,,,,UPSG,,
DS,,648290075,648290075,Shipped,648290075,77,0,0,1,1,1,2,77,1,1,11,,,,UPSG,,
Shipping,,648290075,648290075,Shipped,648290075,77,0,0,1,1,1,0,77,1,1,11,,,,UPSG,1Z4R3E350366250201,
1,,648290076,648290076,Shipped,648290076,32,0,0,1,1,1,15,32,1,1,7,,,,UPSG,,
2,,648290076,648290076,Shipped,648290076,32,0,0,1,1,1,15,32,1,1,7,,,,UPSG,,
DS,,648290076,648290076,Shipped,648290076,32,0,0,1,1,1,2,32,1,1,7,,,,UPSG,,
Shipping,,648290076,648290076,Shipped,648290076,32,0,0,1,1,1,0,32,1,1,7,,,,UPSG,1Z4R3E350366250202,
1,,648290077,648290077,Shipped,648290077,107,0,0,2,2,2,15,107,1,1,11,,,,UPSG,,
5,,648290077,648290077,Shipped,648290077,107,0,0,5,5,5,15,107,1,1,11,,,,UPSG,,
DS,,648290077,648290077,Shipped,648290077,107,0,0,1,1,1,2,107,1,1,11,,,,UPSG,,
Shipping,,648290077,648290077,Shipped,648290077,107,0,0,1,1,1,0,107,1,1,11,,,,UPSG,1Z4R3E350366250203,
1,,648290079,648290079,Shipped,648290079,122,0,0,2,2,2,15,122,1,1,11,,,,UPSG,,
2,,648290079,648290079,Shipped,648290079,122,0,0,3,3,3,15,122,1,1,11,,,,UPSG,,
5,,648290079,648290079,Shipped,648290079,122,0,0,3,3,3,15,122,1,1,11,,,,UPSG,,
DS,,648290079,648290079,Shipped,648290079,122,0,0,1,1,1,2,122,1,1,11,,,,UPSG,,
Shipping,,648290079,648290079,Shipped,648290079,122,0,0,1,1,1,0,122,1,1,11,,,,UPSG,1Z4R3E350366250204,
I need the above CSV to be translated to the below format for each order,
<ns1:order>
     <ns2:order_number>648290076</ns2:order_number>
     <ns2:order_status>Shipped</ns2:order_status>
     <ns2:order_inv_number>648290076</ns2:order_inv_number>
     <ns2:order_inv_amt>32</ns2:order_inv_amt>
     <ns2:order_freight_charge>0</ns2:order_freight_charge>
     <ns2:item_Data>
          <ns0:vendor_item_number>1</ns0:vendor_item_number>
          <ns0:quantity_ordered>1</ns0:quantity_ordered>
          <ns0:quantity_shipped>1</ns0:quantity_shipped>
          <ns0:unit_cost>15</ns0:unit_cost>
          <ns0:extended_cost>32</ns0:extended_cost>
          <ns0:package_id>1</ns0:package_id>
     </ns2:item_Data>
     <ns2:package_Data>
          <ns0:package_id>1</ns0:package_id>
          <ns0:package_Items>
               <ns0:vendor_item_number>1</ns0:vendor_item_number>
               <ns0:quantity_shipped>1</ns0:quantity_shipped>
          </ns0:package_Items>
          <ns0:TrackingNo>
               <ns0:TrackingNum>123456789</ns0:TrackingNum>
          </ns0:TrackingNo>
     </ns2:package_Data>
</ns1:order>

Hi Vlad,
Thanks for the Idea, I tried using the Choice Condition and I am not sure what would be the condition, in my case, there are 3 record, the value in SKU will vary and differentiate the records. The first record (s) (based on no.of items in an order), the value in SKU column will be any value (alpha/numeric/alphanumeric), the next record will have "DS" in the SKU column and the next one will will "Shipping" in the SKU column. The example does look for "Yes" or "No" starting from the "70"th character in the line. I am not sure how to accommodate the condition to check whether the column* "SKU" contains an Item Number or "DS" or "Shipping". The poistion of the column "SKU" may vary every time, so I am not sure how to add a condition to verify that.
Here is the Schema when I used "Delimited" in the choice condition,
<?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"
xmlns:tns="http://TargetNamespace.com/InboundService"
targetNamespace="http://TargetNamespace.com/InboundService"
elementFormDefault="qualified"
attributeFormDefault="unqualified"
nxsd:version="NXSD"
nxsd:stream="chars"
nxsd:encoding="US-ASCII"
nxsd:hasHeader="true"
nxsd:headerLines="1"
nxsd:headerLinesTerminatedBy="${eol}"
>
<xsd:element name="OrderDetail">
<xsd:complexType>
<xsd:choice minOccurs="1" maxOccurs="unbounded" nxsd:choiceCondition="terminated" nxsd:terminatedBy=","*>
<xsd:element name="ItemsRecord" type="tns:Items" nxsd:conditionValue="(!= DS) and (!= Shipping)" />
<xsd:element name="DSRecord" type="tns:ProcessingFee" nxsd:conditionValue="DS" />
<xsd:element name="ShippingRecord" type="tns:ShippingInfo" nxsd:conditionValue="Shipping" />
</xsd:choice>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="ShippingInfo">
<xsd:sequence>
<xsd:element name="OrderDetails" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="VendorID" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="PurchaseOrderNum" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="RefNum" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="OrderStatus" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="InvoiceNum" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="InvoiceAmt" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="FreightCharge" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="" />
<xsd:element name="ProcessingFee" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="SKU" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="QTY" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="QTYOrdered" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="QTYShipped" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Price" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Net" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="TotalNoBoxes" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="BoxNo" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="BoxWeight" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="BoxWidth" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="BoxHeight" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="BoxLength" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="ShipMethod" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="TrackingNumber" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="StatusDate" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="${eol}" />
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Items">
<xsd:sequence>
<xsd:element name="OrderDetail" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="VendorID" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="PurchaseOrderNum" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="RefNum" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="OrderStatus" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="InvoiceNum" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="InvoiceAmt" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="FreightCharge" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="ProcessingFee" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="SKU" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="QTY" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="QTYOrdered" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="QTYShipped" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Price" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Net" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="TotalNoBox" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="BoxNo" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="BoxWeight" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="BoxWidth" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="BoxHeight" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="BoxLength" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="ShipMethod" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="TrackingNumber" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="StatusDate" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="${eol}" />
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ProcessingFee">
<xsd:sequence>
<xsd:element name="OrderDetail" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="VendorID" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="PurchaseOrderNum" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="RefNum" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="OrderStatus" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="InvoiceNum" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="InvoiceAmt" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="FreightCharge" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="ProcessingFee" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="SKU" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="QTY" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="QTYOrdered" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="QTYShipped" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Price" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Net" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="TotelNoBoxes" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="BoxNo" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="BoxWeight" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="BoxWidth" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="BoxHeight" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="BoxLength" type="xsd:float" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="ShipMethod" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="TrackingNumber" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="StatusDate" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="${eol}" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
I thank you once again for your valuable ideas and suggestions.
Thanks,
Venkatesh

Native Schema builder - enhancement request

Hi,
DB and AQ adapters have the nice capability to auto-create XSDs from Oracle ADTs. It will be nice if that can be added to Native Schema Builder wizard as another create schema option.
When you are using the adapter most likely your development skill sets are bound around the adapter technology. We are mostly relational and eBiz shop so the XML/XSD skills are not prevalent in our development team.
Regards,
Rajesh

No, it's not currently in JDeveloper. I think it is perhaps the only or at least one of the few XML development features that XML IDEs such as XML Spy still have as an advantage over JDeveloper.
We discussed this during OOW 2006 in the Regional Directors for Fusion Middleware Meeting and it seemed that product management took very serious note of this 'deficiency' . I have not been given any guarantees, but I would expect something to happen in the not too long term.
regards
Lucas

Error in creating xml builder form

Hi,
I am proceeding with the further steps to create the project under xml builder form I have provided the project id and Project then i tried to save the project now it is showing one error in status bar under Project check tab "The edit form does not contain a save button or link" .Because of this reason when I am trying to save the project the Data model is not showing anything like data schema and Namespace.When I checked the Client Log it is showing AM - (WARN)(Client) com.sapportals.wcm.app.xfbuilder :could not load User settings: Cannot find resource C:\Documents and Settings\my ID\.xfbuilder\usersettings.properties.
Can you help me Pls

Hi,
I think its a warning only.. so u have to add save button for ur xml form, its not a problem.
Regards,
Senthil K.

Opening large ant xml build file(70KB+) hangs JDeveloper 11.1.2.1.0

Hey everyone!
I've been using JDeveloper for about 6 months and I've loved it from the beginning. Everythings seems to be where it's supposed to be and the visual editor greatly speeds up the development. And it's free - amazing. But the team I work with... all of them use IDEA/Eclipse, that is what people got used to - those monstrous IDE's that I'm not realy into - ...So all my persuasions to migrate to JDeveloper crash on one point: when opening large(70KB+) ant xml build files the JDeveloper seems to be doing some syntax checking and just hangs without saying anything. The strange thing is that these files open OK in IDEA/Eclipse.
I use the latest version of JDeveloper 11g Release 2 11.1.2.1.0 on Windows7-64 and 1.6.0_30 java. Can I get some help on this one to increase the JDevelper popularity among fellow java developers? :)
Thanks in advance!
Edited by: 924380 on 29.03.2012 15:30

Do you have access to Oracle Support to file an SR?
Can you post your build.xml file somewhere, and I'd be happy to test?
Another thing to try: run jdev.exe/jdev64.exe (assuming you're on windows) from jdeveloper\jdev\bin. This will open JDev in a command prompt window, and any stack traces that jdev might throw internally would be displayed in the console window. Not that this would help you fix anything, but might give Oracle a clue as to where the issue lies.
John

File Adapter - Native Format Builder

Dear All,
In File Adapter - Native Format Builder exists option "Number of rows to skip". But this means how many rows from beginning of file to skip,
can somebody help to define how to skip n rows from the end of file.
Thanks in advance!

There is no option available to skip rows from end. But if you know how many rows are there in the file and how many you want to skip, then you can use the option of "Number of data rows to process" and process only number of rows you want to actually process.
- Achilles

How to use native XML driver in CR XI 2 (to avoid "Database Logon Failed")?

Hello,
I have a simple scenario:
The Java Part:
-Our Java application creates a pair of files: one XML and one XSD.
-Both files are uploaded to an ASP.NET page along with a report (RPT file - based on the same XSD and some generated XML using the native XML driver) for rendering a PDF.
The ASP.NET(VB) Part:
-Reads and stores 3 files (XML, XSD and RPT) to temporary files.
-Loads the report
-Updates connection attributes ("Local Schema File" and "Local XML File") to point to those temporary files.
-Exports the report to a PDF which is returned to the Java part.
What are the correct steps to accomplish this? I keep on getting "Database logon failed." exceptions.
My code looks like this:
Dim doc As ReportDocument = New ReportDocument
doc.Load(rptPath)
Dim attr As DbConnectionAttributes
attr = New DbConnectionAttributes()
attr.Collection.Set("Local Schema File", xsdPath)
attr.Collection.Set("Local XML File", xmlPath)
Dim conn As IConnectionInfo
conn = doc.DataSourceConnections.Item(0)
conn.Attributes.Collection.LookupNameValuePair("QE_LogonProperties").Value = attr
conn.Attributes.Collection.LookupNameValuePair("QE_ServerDescription").Value = xmlPath & " " & xsdPath
conn.Attributes.Collection.LookupNameValuePair("QE_SQLDB").Value = False
doc.ExportToHttpResponse(ExportFormatType.PortableDocFormat, Response, False, "")
Thank you for any help,
David
(Crystal Reports XI Rel 2. SP4, .NET assembly 11.5.3700)

Hi,
When you get a database logon prompt like this it normally means the dataset you're creating at runtime does not match the schema that the report was designed with.
The simplest thing to do is write out the dataset to XML with Schema after you fill the dataset. Once you've written out the dataset you can go back to the report in Crystal Reports itself and try to point the report to the XML file directly. If you get any errors this confirms that the dataset does not match what the report is expecting.
Try it, address any differences, and you should be all set.
Sincerely,
Amit

File Adapter Wizard - Native Format Builder - no spaces in header?

My project uses a vendor supplied, delimited text file. The first row of the file is a header, followed by data rows. The problem is that the header elements contain spaces, Which are not acceptable by the Native Format Builder.
Has anyone experienced this before and know of a good work-around? Or, is this a known issue?

You can make use of the attribute "headerLines" in the top level "schema" tag. It would look something like this nxsd:headerLines="1".
This will skip first header line and will start from line number 2.
More Info here : http://docs.oracle.com/cd/E23943_01/integration.1111/e10231/nfb.htm#CHDBECJI
Hope it helps.

How to split a file by using Native Format Builder?

Hi all,
Please help me with this issue.
In this project we need to split a file to save in the db.
Following is the sample code and I would like to split this from 'BOH--------------' to 'BOT---------------' (as in BOLD)
But as you can see sometimes 'BOT' line comes up multiple times so I need to skip few 'BOT's until I meet new 'BOH' line.
I guess I have to use complex type in Native Format Builder, but I'm not sure how to..
Please help me with this situation.
Thanks in advance.
BFH0000000101TYO988 203PROD1108021046JP000869
BCH00000002020811110807D110801
BOH000001690316300561110807                       JPY0
BKT0000017006      000011                    015X 988                                               AXSS00000000 00000000 00000000
BKS00000171241108010000119881734947154 0               0FFVV   16300561                    TKTTTYO/TYO           TDHAWK/JL
*BKS00000172301108010000119881734947154 00000006200{0000000000{ SW      0000000200{BP      0000000215{0000007233{0000000000{     JPY0*
*BKS00000173301108010000119881734947154 00000000000{0000000000{ YQ      0000000618{        0000000000{0000000000{0000000000{     JPY0*
*BKS00000174391108010000119881734947154 0I        000000000000000{      000000000000000{000000000000000{0000000000{              JPY0*
BKS00000175461108010000119881734947154 0                                1/2/NON-REF/MZP1M
BKI00000176631108010000119881734947154 01 03AUG03AUG       HND GMP OZ   1035 M 03AUG 2020    OK20K MZPH1M
BKI00000177631108010000119881734947154 02 04AUG03SEP       GMP HND OZ   1045 M 06AUG 1530    OK20K MZPH1M
BAR00000178641108010000119881734947154 0   JPY62000/             JPY2000SW JPY2150BP JPY6180YQ   JPY72330    13150RX5              0
BAR00000179651108010000119881734947154 0NAGASHIMA/HIDEKIMR
BAR00000180661108010000119881734947154 01CASH
BMP00000181731108010000119881734947154 0                                                                                       C
BKF00000182811108010000119881734947154 0 103AUG11 TYO OZ SEL 387.28MZPH1M OZ TYO 387.28MZPH1M
BKF00000183811108010000119881734947154 0 2 NUC774.56END ROE80.044
*BKP0000018484110801000011CA        0000007233{                                                0000000000000000{0000007233{       JPY0*
BKT0000018506      000012                    015X 988                                               AXSS00000000 00000000 00000000
BKS00000186241108010000129881734947155 1               0FFVV   16300561                    TKTTTYO/TYO           TDHAWK/JL
*BKS00000187301108010000129881734947155 10000006200{0000000000{ SW      0000000200{BP      0000000215{0000007233{0000000000{     JPY0*
*BKS00000188301108010000129881734947155 10000000000{0000000000{ YQ      0000000618{        0000000000{0000000000{0000000000{     JPY0*
*BKS00000189391108010000129881734947155 1I        000000000000000{      000000000000000{000000000000000{0000000000{              JPY0*
BKS00000190461108010000129881734947155 1                                1/2/NON-REF/MZP1M
BKI00000191631108010000129881734947155 11 03AUG03AUG       HND GMP OZ   1035 M 03AUG 2020    OK20K MZPH1M
BKI00000192631108010000129881734947155 12 04AUG03SEP       GMP HND OZ   1045 M 06AUG 1530    OK20K MZPH1M
BAR00000193641108010000129881734947155 1   JPY62000/             JPY2000SW JPY2150BP JPY6180YQ   JPY72330    13150RX5              0
BAR00000194651108010000129881734947155 1IWATA/HITOSHIMR
BAR00000195661108010000129881734947155 11CASH
BMP00000196731108010000129881734947155 1                                                                                       C
BKF00000197811108010000129881734947155 1 103AUG11 TYO OZ SEL 387.28MZPH1M OZ TYO 387.28MZPH1M
BKF00000198811108010000129881734947155 1 2 NUC774.56END ROE80.044
*BKP0000019984110801000012CA        0000007233{                                                0000000000000000{0000007233{       JPY0*
BKT0000020006      000013                    017X 988                                               WSPN00000000 00000000 00000000
BKS00000201241108010000139882898050606 0               0FFFF   16300561                    TKTTNGO/NGO           N7ZAXW/1P
*BKS00000202301108010000139882898050606 00000005000{0000000000{ SW      0000000250{BP      0000000154{0000007539{0000000000{     JPY0*
*BKS00000203301108010000139882898050606 00000000000{0000000000{ KX      0000000199{YQ      0000001936{0000000000{0000000000{     JPY0*
*BKS00000204391108010000139882898050606 0I        000000000000000{      000000000000000{000000000000000{0000000000{              JPY0*
BKS00000205461108010000139882898050606 0                                NON-ENDS/QZA14/
BKI00000206631108010000139882898050606 01X02OCT02OCT       NGO ICN OZ     121Q 02OCT 1200    OK20K QLZA14D
BKI00000207631108010000139882898050606 02O02OCT02OCT       ICN REP OZ     737Q 02OCT 1920    OK20K QLZA14D
BKI00000208631108010000139882898050606 03X10OCT10OCT       REP ICN OZ     738Q 10OCT 2340    OK20K QLZA14D
BKI00000209631108010000139882898050606 04 11OCT11OCT       ICN NGO OZ     122Q 11OCT 0910    OK20K QLZA14D
BAR00000210641108010000139882898050606 0JPY   50000/           XT    21350SW     2500BP     1540JPY   75390    52350NT               9
BAR00000211651108010000139882898050606 0WATANABE/FUMIE.MS
BAR00000212661108010000139882898050606 01VI 4297 XXXXXXXXX 1870P0812
BKF00000213811108010000139882898050606 0 1NGO OZ X/SEL OZ REP 312.32OZ X/SEL OZ NGO 312.32NUC624.64 END ROE80.044OZ XT1990KX 1936
BKF00000214811108010000139882898050606 0 20YQ
*BKP0000021584110801000013CCVI4297 0000007539{4297690004451870   0812     701410              0000000000000000{0000000000{       JPY0*
*BKP0000021684110801000013CA        0000000000{                                                0000000000000000{0000000000{       JPY0*
BKT0000021706      000014                    015X 988                                               INFI00000000 00000000 00000000
BKS00000218241108010000149885195702276 678841696569480 5FFVV   16300561                    TKTTNGO/NGO           JMERJU/1F
*BKS00000219301108010000149885195702276 60000002500{0000000000{ SW      0000000250{BP      0000000215{0000003583{0000000000{     JPY0*
*BKS00000220301108010000149885195702276 60000000000{0000000000{ YQ      0000000618{        0000000000{0000000000{0000000000{     JPY0*
*BKS00000221391108010000149885195702276 6I        000000000000000{      000000000000000{000000000000000{0000000000{              JPY0*
BKS00000222461108010000149885195702276 6                                NON-REF/QZA7
BKI00000223631108010000149885195702276 61O16SEP16SEP       NGO ICN OZ   123 Q 16SEP 1745    OK20K QKPMZA7
BKI00000224631108010000149885195702276 62 22SEP22SEP       ICN NGO OZ   124 Q 22SEP 1500    OK20K QKPMZA7
BAR00000225641108010000149885195702276 6JPY   25000/                2500SW     2150BP     6180YQJPY   35830INFI78840      99999999 N0
BAR00000226651108010000149885195702276 6INUKAI/HIROKO MS                                 NTS REF 3607438
BAR00000227661108010000149885195702276 61JC35875900009516110115/ C 018627*
BMP00000228731108010000149885195702276 6                     NTS REF 3607438                                 ANU
BKF00000229811108010000149885195702276 6 116SEP11NGO OZ SEL156.16OZ NGO156.16NUC312.32END ROE80.044
*BKP0000023084110801000014CCJC3587 0000003583{3587590000951611   0115     018627              0000000000000000{0000000000{       JPY0*
*BKP0000023184110801000014CA        0000000000{                                                0000000000000000{0000000000{       JPY0*
BKT0000023206      000015                    014X 988                                               GDSL00000000 00000000 00000000
BKS00000233241108010000159885340399785 458803403997853 6FFVV   16300561                    TKTTNRT/NRT           V7R5WC/1V
*BKS00000234301108010000159885340399785 40000004000{0000000000{ YQ      0000000618{BP      0000000215{0000005087{0000000000{     JPY0*
*BKS00000235301108010000159885340399785 40000000000{0000000000{ SW      0000000204{OI      0000000050{0000000000{0000000000{     JPY0*
*BKS00000236391108010000159885340399785 4I        000000000000000{      000000000000000{000000000000000{0000000000{              JPY0*
BKS00000237461108010000159885340399785 4                                NON-REF-QZA7
BKI00000238631108010000159885340399785 41 08AUG08AUG       NRT ICN OZ   107 Q 08AUG 0900    OK20K QHA2ZA7
BKI00000239631108010000159885340399785 42 10AUG10AUG       ICN NRT OZ   106 Q 10AUG 1510    OK20K QHA2ZA7
BAR00000240641108010000159885340399785 4   JPY40000/              JPY500OI JPY10370XT              JPY50870    588002LNCK           U3
BAR00000241651108010000159885340399785 4TAKAHASHI/AYA MS
BAR00000242661108010000159885340399785 41CASH
BKF00000243811108010000159885340399785 4 1FP CASH FC 8AUG TYO OZ SEL 249.86QHA2ZA7 OZ TYO 249.86QHA2ZA7 NUC499.72END ROE80.044 XT
BKF00000244811108010000159885340399785 4 2 6180YQ 2150BP 2040SW
*BKP0000024584110801000015CA        0000005087{                                                0000000000000000{0000005087{       JPY0*
*BOT000002469316300561110807       00000000030675{00000000019553{00000000000000{00000000006775{00000000000000{SALE 00000000000000{JPY0*
*BKT0000024706      000016                    010 988                                               INFI00000000 00000000 00000000 A*
*BKS00000248241108010000169885195419735 678841696711651 4       16300561                    RFND   /*
*BKS00000249301108010000169885195419735 60000005700}0000000000{ OI      0000000050}SW 0000000204}0000006087}0000000000{     JPY0*
*BKS00000250301108010000169885195419735 60000000000{0000000000{ BP      0000000215}YQ 0000000518}0000000000{0000000000{     JPY0*
*BKS00000251301108010000169885195419735 60000000000{0000000000{ CP      0000000600{        0000000000{0000000000{0000000000{     JPY0*
*BKS00000252391108010000169885195419735 6I        000000000000000{      000000000000000{000000000000000{0000000000{              JPY0*
BKS00000253451108070000169885195419735 2                                                                  1200                110727
BAR00000254651108010000169885195419735 6SATO/YUKIMR
BKP0000025583110801000016 9889AZ5E61I6V
BKP0000025684110801000016CA        0000006087}                                                0000000000000000{0000006087}       JPY0
BKT0000025706      000017                    010 988                                               INFI00000000 00000000 00000000 A
BKS00000258241108010000179885195419736 078841696711481 1       16300561                    RFND   /
*BKS00000259301108010000179885195419736 00000005700}0000000000{ OI      0000000050}SW 0000000204}0000006087}0000000000{     JPY0*
*BKS00000260301108010000179885195419736 00000000000{0000000000{ BP      0000000215}YQ 0000000518}0000000000{0000000000{     JPY0*
*BKS00000261301108010000179885195419736 00000000000{0000000000{ CP      0000000600{        0000000000{0000000000{0000000000{     JPY0*
*BKS00000262391108010000179885195419736 0I        000000000000000{      000000000000000{000000000000000{0000000000{              JPY0*
BKS00000263451108070000179885195419736 3                                                                  1200                110727
BAR00000264651108010000179885195419736 0KANG/SOONBOKMS
BKP0000026583110801000017 9889AZ5E61I6W
BKP0000026684110801000017CA        0000006087}                                                0000000000000000{0000006087}       JPY0
*BOT000002679316300561110807       00000000012174}00000000012174}00000000000000{00000000000774}00000000000000{RFND 00000000000000{JPY0*
*BOT000002689416300561110807       00000000018501{00000000007379{00000000000000{00000000006001{00000000000000{     00000000000000{JPY0*
BOH000002690316300863110807                       JPY0
BKT0000027006      000018                    015X 988                                               AXSS00000000 00000000 00000000
BKS00000271241108010000189881734547779 3               0FFVV   16300863                    TKTTNGO/NGO           47F8J6/JL
BKS00000272301108010000189881734547779 30000005000{0000000000{ SW      0000000250{BP      0000000215{0000006083{0000000000{     JPY0
BKS00000273301108010000189881734547779 30000000000{0000000000{ YQ      0000000618{        0000000000{0000000000{0000000000{     JPY0
BKS00000274391108010000189881734547779 3I        000000000000000{      000000000000000{000000000000000{0000000000{              JPY0
BKS00000275461108010000189881734547779 3                                1/2/NON-REF/MZP1M
BKI00000276631108010000189881734547779 31 07AUG07AUG       NGO ICN OZ   121 M 07AUG 1200    OK20K MZP1M
BKI00000277631108010000189881734547779 32 08AUG07SEP       ICN NGO OZ   124 M 09AUG 1500    OK20K MZP1M
BAR00000278641108010000189881734547779 3   JPY50000/             JPY2500SW JPY2150BP JPY6180YQ   JPY60830    13150OL2              0
BAR00000279651108010000189881734547779 3KAMEGAI/NORIOMR
BAR00000280661108010000189881734547779 31CASH
BMP00000281731108010000189881734547779 3                                                                                       C
BKF00000282811108010000189881734547779 3 107AUG11 NGO OZ SEL 312.32MZP1M OZ NGO 312.32MZP1M N
BKF00000283811108010000189881734547779 3 2UC624.64END ROE80.044
BKP0000028484110801000018CA        0000006083{                                                0000000000000000{0000006083{       JPY0
BKT0000028506      000019                    014X 988                                               AXSS00000000 00000000 00000000
BKS00000286241108010000199881734547801 4               0FFVV   16300863                    TKTTNGO/NGO           5Y5RQQ/JL
BKS00000287301108010000199881734547801 40000008350{0000000000{ SW      0000000250{BP      0000000215{0000009433{0000000000{     JPY0
BKS00000288301108010000199881734547801 40000000000{0000000000{ YQ      0000000618{        0000000000{0000000000{0000000000{     JPY0
BKS00000289391108010000199881734547801 4I        000000000000000{      000000000000000{000000000000000{0000000000{              JPY0
BKI00000290631108010000199881734547801 41      16AUG       NGO ICN OZ   123 C 16AUG 1745    OK30K CRTOZKR
BKI00000291631108010000199881734547801 42      16AUG       ICN NGO OZ   9122 Y 18AUG 1835    OK20K YRTOZKR
BAR00000292641108010000199881734547801 4   JPY83500/             JPY2500SW JPY2150BP JPY6180YQ   JPY94330    13150GI3              0
BAR00000293651108010000199881734547801 4HIRAI/SHUJIMR
BAR00000294661108010000199881734547801 41CASH
BMP00000295731108010000199881734547801 4                                                                                       C
BKF00000296811108010000199881734547801 4 116AUG11 NGO OZ SEL 624.65CRTOZKR OZ NGO 418.51YRTOZ
BKF00000297811108010000199881734547801 4 2KR NUC1043.16END ROE80.044
BKP0000029884110801000019CA        0000009433{                                                0000000000000000{0000009433{       JPY0
BOT000002999316300863110807       00000000015516{00000000015516{00000000000000{00000000002166{00000000000000{SALE 00000000000000{JPY0
BOT000003009416300863110807       00000000015516{00000000015516{00000000000000{00000000002166{00000000000000{     00000000000000{JPY0
BOH000003010316300933110807                       JPY0
BKT0000030206      000020                    009 988                                               INFI00000000 00000000 00000000 A
BKS00000303241108010000209885195510345 178840417924611 4       16300933                    RFND   /
BKS00000304301108010000209885195510345 10000005800}0000000000{ SW      0000000265}YQ 0000000259}0000006074}0000000000{     JPY0
BKS00000305301108010000209885195510345 10000000000{0000000000{ CP      0000000250{        0000000000{0000000000{0000000000{     JPY0
BKS00000306391108010000209885195510345 1I 000000000000000{      000000000000000{000000000000000{0000000000{              JPY0
BKS00000307451108070000209885195510345 4 1000 110727
BAR00000308651108010000209885195510345 1SONG/YOUNGSUKMR
BKP0000030983110801000020 9889AZ5E63G3T
BKP0000031084110801000020CA 0000006074} 0000000000000000{0000006074} JPY0
BKT0000031106 000021 009 988 INFI00000000 00000000 00000000 A
BKS00000312241108010000219885195510346 278840417924641 0 16300933 RFND /
BKS00000313301108010000219885195510346 20000004000}0000000000{ SW      0000000265}YQ 0000000259}0000004274}0000000000{     JPY0
BKS00000314301108010000219885195510346 20000000000{0000000000{ CP      0000000250{        0000000000{0000000000{0000000000{     JPY0
BKS00000315391108010000219885195510346 2I 000000000000000{      000000000000000{000000000000000{0000000000{              JPY0
BKS00000316451108070000219885195510346 5 1000 110727
BAR00000317651108010000219885195510346 2KIM/WONBINMR
BKP0000031883110801000021 9889AZ5E63G3U
BKP0000031984110801000021CA 0000004274} 0000000000000000{0000004274} JPY0
BOT000003209316300933110807 00000000010348}00000000010348}00000000000000{00000000000548}00000000000000{RFND 00000000000000{JPY0
BOT000003219416300933110807       00000000010348}00000000010348}00000000000000{00000000000548}00000000000000{     00000000000000{JPY0
BCT00021143950811 0014500000009520310F00000005400221G00000002821794}00000001540700F00000000000000{          00000000002785PJPY0
BFT0002114499TYO 0014500000009520310F00000005400221G00000002821794}00000001540700F00000000000000{           00000000002785PJPY0
Edited by: 964067 on Oct 14, 2012 11:26 PM
Edited by: 964067 on Oct 14, 2012 11:26 PM

Hi,
Firstly please ensure that the file that you are reading is bound to have a format of some sort.
I will relate this to one of the requirement we did it in previous projects.
We have a requirement to read a csv file coming in:
1) It will be having records for Header (ODH) and Detail (ODL)
2) The Header and Detail records will be repeated 'N' number of times in the input file.
The schema we used it something as below to poll the CSV file:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
xmlns:tns="http://TargetNamespace.com/ReadCSV" targetNamespace="http://TargetNamespace.com/ReadCSV"
elementFormDefault="qualified" attributeFormDefault="unqualified" nxsd:parseBom="true"
nxsd:version="NXSD" nxsd:stream="chars" nxsd:encoding="US-ASCII">
<xsd:element name="Package">
<xsd:complexType>
<xsd:choice minOccurs="1" maxOccurs="unbounded" nxsd:choiceCondition="terminated" nxsd:terminatedBy=",">
<xsd:element name="Header" nxsd:conditionValue="BOH">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="RecordAction" type="xsd:string" minOccurs="0" nxsd:style="terminated"
nxsd:terminatedBy="," nxsd:quotedBy="""/>
<xsd:element name="VisitType" type="xsd:string" minOccurs="0" nxsd:style="terminated"
nxsd:terminatedBy="," nxsd:quotedBy="""/>
<xsd:element name="OrderAction" type="xsd:string" minOccurs="0" nxsd:style="terminated"
nxsd:terminatedBy="," nxsd:quotedBy="""/>
<xsd:element name="Route" type="xsd:int" minOccurs="0" nxsd:style="terminated"
nxsd:terminatedBy="${eol}" nxsd:quotedBy="""/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Lines" nxsd:conditionValue="BOD">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="RecordAction" type="xsd:string" minOccurs="0" nxsd:style="terminated"
nxsd:terminatedBy="," nxsd:quotedBy="""/>
<xsd:element name="OrderCode" type="xsd:string" minOccurs="0" nxsd:style="terminated"
nxsd:terminatedBy="," nxsd:quotedBy="""/>
<xsd:element name="ShippingUnitNumber" type="xsd:int" minOccurs="0" nxsd:style="terminated"
nxsd:terminatedBy="," nxsd:quotedBy="""/>
<xsd:element name="ProdOptDesc" type="xsd:string" minOccurs="0" nxsd:style="terminated"
nxsd:terminatedBy="${eol}" nxsd:quotedBy="""/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:schema>
So the approach we followed is as below:
1) Design two DB tables. One to put the header records in Header table
2) Put the detail records in Trailer table.
3) Poll from these two tables to trigger next business requirements.
Hope this helps.
Thanks,
Deepak.

File Adapter - Native format Builder button not Appearing

Hi,
When We go through the file adapter wizard and on the screen where we define the schema, there is a button 'Native format builder'. But on Jdeveloper Version - 11.1.1.3.0, it is not appearing. Has this been removed in this release?
regards,
Rajesh

at step 8 of 9 of the file adapter wizard, the icon appears as a cog, on the right, with caption "define schema for native format".
I have JDev 11..1.1.3.0
The problem might be with the version of the SOA extensions you have installed....

Special Character Restrictions for Native XML Driver

Hi,
I have found the following special character restrictions in the documentation:
"Because they are handled specially by the Native XML driver, do not use the following special characters to define element types and attributes in your XML schema:u201C.u201D, u201C/u201D, u201C\u201D, u201C:u201D u201C@u201D."
After checking the createad XML-Files in our projects that we will use for CR4E there is often a u201C.u201D in the definition. Because this is delivered from third-party, we wish that the u201C.u201D will be enabled.
In the moment we create the XSD-Files from the XML-File with XML2XSD.
It is possible in the future?
Best Regards
Arnold Meier

The changes aren't in XI Release 2, but in 2008.
Do you still have Nha's XML data? I edited Document_Policy, Policy_AllCoverages, Policy_Beneficiary to Document.Policy, Policy.AllCoverages, Policy.Beneficiary, then use the following code in CR4E 2.0:
reportClientDocument reportClientDocument;
ConnectionInfo connectionInfo;
PropertyBag propertyBag;
* Connect to the Java Print Engine and create a new document.
reportClientDocument = new ReportClientDocument();
reportClientDocument.setReportAppServer(ReportClientDocument.inprocConnectionString);
reportClientDocument.newDocument();
* Define connection to the XML and XSD files.
propertyBag = new PropertyBag();
propertyBag.put("Local XML File", "C:\\Documents and Settings\\tueda\\Desktop\\nha.xml");
propertyBag.put("Local Schema File", "C:\\Documents and Settings\\tueda\\Desktop\\nha.xsd");
propertyBag.put("Convert Multivalue to Table", Boolean.FALSE);
propertyBag.put("Database DLL", "crdb_xml.dll");
connectionInfo = new ConnectionInfo();
connectionInfo.setAttributes(propertyBag);
* Specify the dataset in the XML as a Table, and add to the report.
Table table = new Table();
table.setConnectionInfo(connectionInfo);
table.setName("Document.Policy/Policy.Beneficiary");
table.setAlias("Document_Policy/Policy_Beneficiary");
reportClientDocument.getDatabaseController().addTable(table, null);
* Save report to file C:\local_xml.rpt
reportClientDocument.saveAs("nha_local_xml.rpt", "C:\\", ReportSaveAsOptions._overwriteExisting);
reportClientDocument.close();
Sincerely,
Ted Ueda

Question about "Native ISO" and Color Grading in PP

I have a question about "Native ISO" in the real world and how it relates to color grading. I was shooting 35mm film before all these digital cameras became flat-out amazing practically overnight. Then the goal was always to shoot with the lowest ISO possible to achieve the least amount of grain (unless you were making an artistic decision to get that look). If I was shooting outside plus had a nice lighting package I'd shoot 5201/50 ASA (Daylight) and 5212/100 ASA (Tungsten) 99 times out of 100.
I've recently been shooting a lot with the Blackmagic 4K and have read that its "Native ISO" is 400. Because of my film background this seems counter-intuitive. Yesterday I was shooting for a client and had the camera at an f16 with a 200 ISO. Because of what I'd read, I was tempted stop down to an f22 and change my ISO to 400... but the "little film voice in my head" just wouldn't let me do it. It kept telling me "Higher ISO means more noise... stay at 200 and you will get a cleaner image".
So how does it work with "Native ISO"? Should I really shoot at a 400 ISO every chance I get in order to capture the best image for how the camera is calibrated? Will it really give me more latitude when color grading? Or would I still get a cleaner image staying at ISO 200? I've Googled around quite, but haven't found any articles that answer specifically this question. Would love to hear from someone who knows a bit more on the subject or has a link that could point me in the right direction.
Thanks much.

Hey, shooter ... yea, interesting discussion and always nice to learn. Great pic, too!
jamesp2 ...
Great answer. I've followed quite a bit of the discussion about the BM cams as well, one does feel a need to check out the possibilities for that next beastie one will need to acquire. But ... which one?
I've always been a bit of a hard-case about testing testing testing. For instance, what happens with dome down or use of a flat diffuser vs. dome in the up position in metering? Back in the film days, we had our own lab and did our own printing as well as the um ... difficult images ... from other studios. I needed to know how to get exactly the same diffuse highlight no matter whether it was a "standard" light 3:1 studio shot, or a near-profile with no fill that needs dark shadows. I tested & burned through boxes of medium-format polaroid & 120 film and a lot of color paper. Finding? To get the same print time no matter the contrast or lighting style, needed to be metered either with the flat disc (Minolta) or dome-down (Sekonic) and held at the highlight-location pointed at the main light source. I could meter and nail the exposure every time. Ahh no, insist so many ... one must have the dome on/up and pointed at the camera! Right. Do that, change the contrast, and see what happens to your diffuse forehead highlight on a densitometer ... and see how your printing exposure times change. Oh, and you've just moved your center-of-exposure up or down on the film's H&D curve, which will also change the way the shadows & highlights print. In truth, though it was subtle, we had realistically no matter latitude for a best-case image with pro neg film as one had with chromes. You could probably get away with being "off" easier, but it still wasn't dead-on.
So wading into video ... oi vey, you may have noticed the things claimed here there & everywhere ... this setting is God's Gift to Humanity but no, it's total crap ... this sensor is totally flawed but someone else is certain it's the finest piece out there. Yes, opinions will be all over ... but ... in film, it was the densitometer. In video, it's the scopes. Truth. And getting to that can be a right pain. I've seen quite a few contradictory comments about using the BM cams in film mode and also at ISO 200. Yours above gives the most ... comforting? ... explanation (for me) because of your reference to your scopes & the waveform patterns. Thank you.
Love to learn ...
Neil

Importing native xml in to semi structured storage

hello,
how store the a bibliographic data in the native xml and import or export that data into to the semi structured storage. What are the ways we query the xml database.
Eagerly waiting for the reply
Cheers
Akhil
Thank you in advance

Based on a small extension demo-ed in : http://www.liberidu.com/blog/?p=1053 (demo script demo06.sql)
-- If you can select it you can insert it...
-- drop table OGH_xml_store purge;
create table OGH_xml_store of xmltype
xmltype store as binary xml
commit;
exec get_dir_list( 'G:\OGH\xmlstore' );
set time on timing on
insert into OGH_xml_store
select XMLTYPE(bfilename('OGH_USE_CASE',dl.filename),NLS_CHARSET_ID('AL32UTF8')) AS "XML"
from   dir_list dl
where dl.filename like '%.xml';
set time off timing off
commit;
select count(*) from OGH_xml_store;
prompt pause
pause
clear screen
-- If you can select it you can create resources and files
set time on timing on
commit;
exec get_dir_list( 'G:\OGH\xmlstore' );
select count(*) from dir_list where filename like '%.xml';
set serveroutput on size 10000
DECLARE
XMLdoc       XMLType;
res          BOOLEAN;
v_foldername varchar2(4000) := '/public/OGH/';
cursor c1
is
select dl.filename                                                                  FNAME
,      XMLTYPE(bfilename('OGH_USE_CASE',dl.filename),NLS_CHARSET_ID('AL32UTF8')) XMLCONTENT
from   dir_list dl
where dl.filename like '%.xml'
and rownum <= 100;
BEGIN
-- Create XDB repository Folder
if (dbms_xdb.existsResource(v_foldername))
then
       dbms_xdb.deleteResource(v_foldername,dbms_xdb.DELETE_RECURSIVE_FORCE);
end if;
res:=DBMS_XDB.createFolder(v_foldername);
-- Create XML files in the XDB Repository
for r1 in c1
loop
   if (DBMS_XDB.CREATERESOURCE(v_foldername||r1.fname, r1.xmlcontent))
   then
      dbms_output.put_line(v_foldername||r1.fname);
      null;
   else
      dbms_output.put_line('Loop Exception :'||sqlerrm);
   end if;
end loop;
EXCEPTION WHEN OTHERS THEN
dbms_output.put_line('Others Exception: '||sqlerrm);
END;
set time off timing off
commit;
prompt pause
pause
clear screen
-- FTP and HTTP
clear screen
prompt
prompt *** FTP - Demo ***
prompt
prompt pause
pause
host ftp
-- open localhost 2100
-- user OGH OGH
-- cd public
-- cd OGH
-- ls
-- bye
clear screen
prompt
prompt *** Microsoft Internet Explorer - Demo ***
prompt
prompt pause
pause
host "C:\Program Files\Internet Explorer\IEXPLORE.EXE" http://OGH:OGH@localhost:8080/public/OGH/
prompt pause
pause
-- Accessing the XDB Repository content via Resource View
-- Selecting content from a resource via XBDUriType
clear screen
prompt set long 300
set long 300
prompt Relative Path - (path)
SELECT path(1) as filename
FROM RESOURCE_VIEW
WHERE under_path(RES, '/public/OGH', 1) = 1
and rownum <= 10
prompt pause
pause
clear screen
prompt Absolute Path - (any_path)
select xdburitype(any_path).getClob() as xml
FROM RESOURCE_VIEW
WHERE under_path(RES, '/public/OGH', 1) = 1
and rownum <= 1;
prompt pause
pause

Native XML Driver Deployment

For a while we had trouble using the native xml driver, but it has been worked out here:
VB6 & XML Datasource using Native XML Driver
In that thread there was mention of deploying the driver, and some extra work that needed to happen. I found those instructions repeated again here for another user:
https://boc.sdn.sap.com/node/1428
We have followed the instructions of coping the required files and java runtime to a new test client, but our reports do not launch.. we get this error after a good 30 seconds of hang-time,
Invalid Argument Provided
I've doubled checked the instructions and all files are copied, and edited the crconfig.xml to point to the new j2re bin folder. There doesn't appear to be many discussions with this error, what does it mean? Thanks.
Note that we are using the RDC, Native XML Driver, Crystal Reports XI R2 SP4.

Ok I went over the process again, and am a little confused -
Install the Java (JVM) 2 Runtime Environment (this is essentially the Java Framework needed to launch the crdb_xml native driver 1.4.2 from the java sun web site at:
http://java.sun.com/j2se/1.4.2/download.html.
Create a java folder inside the " C:\Program Files\Business Objects\Common\3.0";.
Copy over the Crconfig.xml(C:\Program Files\Common Files\Business Objects\3.0\java) file from the development machine to the deployed machine in at the following path "C:\Program Files\Common Files\Business Objects\3.0\java" path. Open the crconfig.xml ; this file in Notepad and search for the line <JavaDir>. If JRE is installed to C:\Program Files\Java\j2re1.4.2_12\bin then the value should be look like this <JavaDir> C:\Program Files\Java\j2re1.4.2_12\bin</JavaDir>.
Create a folder called lib in the "C:\Program Files\Common Files\Business Objects\3.0\java".
Copy over the entire contents of the lib folder (especially the external folder) from the development machine to the newly created lib machine on the deployed machine. The point of this is to ensure that the crconfig.xml file contains all the files here which exist at the correct path which they now should because we copied over the lib and external directories.
Copy crdb_xml.dll, crdb_xml_res_en, and all the files with "crdb_xml_res_xx from your development machine to the deployment machine (C:\Program Files\Common Files\Business Objects\3.0\bin).
Restart your machine and try accessing your web application. The reports will show up the data without any issue.
The above is written for CR XI release 1. You may have to adjust the path given above as you do not specify the version of Crystal reports you are using.
On my development machine, there is no Crconfig.xml at this location (C:\Program Files\Common Files\Business Objects\3.0\java) . In fact the java folder is not there either, I only see bin and crystalreportviewers11 folders. Can these instructions be confirmed for me as accurate? I do not even see a 3.5 folder under C:\Program Files\Common Files\Business Objects\

Is Oracle XML DB a native xml database?

Hi!
XML DB provides native data type XMLTYPE, and it can provide traditional storage for xml. So is it a enabled xml database or a native one??
Cheers

It is an XML enabled relational database (XMLType OR storage) but has also native XML database capabilities in the form of binary XML (XMLType Binary XML storage)

Question on Native XML Builder

Similar Messages

Maybe you are looking for