Read file inside BPEL using Xpath function

To read a file in SOA composite, we can use the following options
    1. Using file adapter
    2. Using java embedding
    3. Using xpath function i.e. ora:readFile()

We generally use file adapter to read, write or poll files from different file locations. But, in case if don't want to create a file adapter and don't want to go for java embedding. We can make use of BPEL xpath extension functions. In this article, we will discuss about reading a file using xpath function ora:readFile().

Xpath expression:

    ora:readFile('fileName',['schemaLocation'],['rootElement'])    

xmlns:ora = http://schemas.oracle.com/xpath/extension

'fileName': Refers to absolute path of file along with extension. This is mandatory field. 

'schemaLocation' : Refers to location of nxsd schema for the file to be read. This is an optional field. If you don't provide the schema location, then data from the file will be read and converted to base64 encoded string

'rootElement' : Refers to root element in nxsd schema. This is optional field but required if we provide schema location.

Example:

Sample CSV file with absolute file path: C:\Users\test\SOA\test1.csv

S.No,Field1,Field2,Field3
1,t1,t2,t3
2,s1,s2,s3

Sample NXSD Schema:

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd" xmlns:tns="http://TargetNamespace.com/ServiceName" targetNamespace="http://TargetNamespace.com/ServiceName" elementFormDefault="qualified" attributeFormDefault="unqualified" nxsd:version="NXSD" nxsd:stream="chars" nxsd:encoding="UTF-8" nxsd:hasHeader="true" nxsd:headerLines="1" nxsd:headerLinesTerminatedBy="${eol}">
  <xsd:element name="Root-Element">
    <xsd:complexType>
      <xsd:sequence>
        <xsd:element name="row" minOccurs="1" maxOccurs="unbounded">
          <xsd:complexType>
            <xsd:sequence>
              <xsd:element name="S.No" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy="&quot;"/>
              <xsd:element name="Field1" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy="&quot;"/>
              <xsd:element name="Field2" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy="&quot;"/>
              <xsd:element name="Field3" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="${eol}" nxsd:quotedBy="&quot;"/>
            </xsd:sequence>
          </xsd:complexType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
  </xsd:element>
</xsd:schema>


Xpath statement without schema, which will give output as base64 schema.
    ora:readFile('file:///C:/Users/test/SOA/test1.csv')



Output:
    Uy5ObyxGaWVsZDEsRmllbGQyLEZpZWxkMw0KMSx0MSx0Mix0Mw0KMixzMSxzMixzMw0K

Xpath statement with schema, which will give output as xml
    ora:readFile('file:///C:/Users/test/SOA/test1.csv','Schemas/nxsd_schema1.xsd','Root-Element')



Output:
<Root-Element xmlns="http://TargetNamespace.com/ServiceName">
<row>
<S.No>1</S.No>
<Field1>t1</Field1>
<Field2>t2</Field2>
<Field3>t3</Field3>
</row>
<row>
<S.No>2</S.No>
<Field1>s1</Field1>
<Field2>s2</Field2>
<Field3>s3</Field3>
</row>
</Root-Element>

Using either of the above statements we can read file in assign activity directly, without using file adapter or java embedding.


-

Comments

Post a Comment

Popular posts from this blog

DateTime formatting using xp20:format-dateTime ()

xs:dateTime Format In XML, we generally use xs:dateTime(xs:xmlns="http://www.w3.org/2001/XMLSchema") data type to store date time data. The generic representation of date time, that is supported by xs:dateTime in xml: YYYY-MM-DDThh:mm:ss[.SSS][Z|(+|-)hh:mm] Example :  2019-09-11T10:16:31.943+05:30 Code Description Example YYYY represents a 4-digit year 2019 MM represents a 2-digit month 09 DD represents 2-digit date 11 hh represents 2-digit hours 10 mm represents minutes in 2-digits 16 ss represents seconds in 2-digits 31 SSS represents milliseconds 943 T represents time separator T Z represents UTC time zone or 0 time zone offset (+|-)hh:mm represents time zone offset +5:30 Few more valid examples : 2019-09-11T21:32:52, 2019-09-11T21:32:52+02:
Read more

Create Delimited String from XML Nodes and Vice Versa in SOA 12c

A delimited string is a string representation of data separated by a delimiter(e.g. ","). A simple representation of the delimited string will look like. Delimited String Examples Sample-1-- Delimiter as ","        Value1,Value2,Value3   Sample-2-- Delimiter as "|"        Value1|Value2|Value3 If we want to represent the above set of delimited values in the form of an XML document under some root and parent tag. The representation will look like this. XML Example <root xmlns="http://test.com/sample/xml">   <Values>     <value>Value1</value>     <value>Value2</value>     <value>Value3</value>   </Values> </root> Sometimes we may need to convert values coming in delimited string to an xml document or vice versa. Since delimited string is similar to csv format. We can create
Read more

Import and Export MDS artifacts in SOA 12c

Image
Oracle SOA-MDS (Metadata Store) repository can be used to access artifacts that can be shared among various SOA composites. For example, we have one common schema for a business fault that is consumed by various applications. Instead of having a localized copy of that schema file in each SOA composite, we can have it in a centralized repository (SOA-MDS). Another benefit of using SOA-MDS is that we can change the file at runtime and need not redeploy the complete code. While developing SOA composites, we use SOA design-time repository, later these changes can be synced to the SOA servers. In this article, we will discuss 2 ways to sync the artifacts available in the SOA design-time repository and the SOA servers. Establishing the connection to SOA-MDS in Jdeveloper. Using SOA em console or Fusion Middleware control console. Moving a file between SOA composite to SOA design-time MDS repository Let's assume, we created a businessFault.xsd which wi
Read more