![]() You can also specify a combination of these criteria for output files.Īdapters is referred to as the file write operation. The output files can be created based on the following criteria: time elapsed, file size, and number of messages. This functionality of the Oracle File and FTPĪdapters is referred to as the file read operation.įor outbound files sent from Oracle BPEL PM or Mediator, the Oracle File and FTPįormat the XML contents as specified at design time. Publish the translated content as an XML message. Native data is translated based on the native schema (NXSD) defined at design time. Poll the file system looking for matches. Based on the direction, the Oracle File and FTPĪdapters perform different sets of tasks.įor inbound files sent to Oracle BPEL PM or Mediator, the Oracle File and FTPĪdapters perform the following operations: The translator can handle both XML and non-XML (native) formats of data.Īdapters exchange files in the inbound and outbound directions. The native data can be simple (just a flat structure) or complex (with parent-child relationships). The translator enables the Oracle File and FTPĪdapters to convert native data in various formats to XML, and from XML to other formats. See also Large Payload Support, for a description of attachment support. Opaque/base-64 representation is usually used for passing binary data within XML. Note that opaque representation base-64 encodes the payload and increase the size of the payload in-memory by a third. The opaque option handles binary data such as Jpgs and GIFs, whose structure cannot be captured in an XSD or data you do not want to have translated. Adapters can read and write the following file formats and use the adapter translator component at runtime:Īdapters can also treat file contents as an opaque object and pass the contents in their original format (without performing translation).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |