Operations on Interface Tables, Interface Views, Tables, and Views That Contain LOB Data
The Microsoft BizTalk Adapter for Oracle E-Business Suite provides support for the Oracle large object (LOB) data types:
Binary large object (BLOB)
Character large object (CLOB)
National character large object (NCLOB)
Binary file (BFILE). For more information, see Operations on Tables That Contain BFILE Data Types.
In the underlying Oracle database, LOB data types are used to store large amounts of data, up to 4 gigabytes (GB). Except for the BFILE data type, LOB data types support both input and output streaming.
Operations for tables and views
The Oracle E-Business adapter surfaces the following operations for interface tables, interface views, tables and views that contain LOB columns:
Read_<LOBColName>: The
Read_<LOBColName>operation is surfaced for interface tables, interface views, tables and views that contain BLOB, CLOB, NCLOB, and BFILE columns, where <LOBColName> is the name of the column of type BLOB, CLOB, NCLOB or BFILE. By using the Read_<LOBColName> operation, adapter clients can read values in an LOB column as a data stream. This operation takes a filter string as parameter.Note
The
Read_<LOBColName>operation is designed to support input streaming of LOB data in the WCF service model. You should use a table Select operation to read LOB data from a WCF channel model or BizTalk Server solution.Update_<LOBColName>: The
Update_<LOBColName>operation is surfaced for interface tables and tables only that contain BLOB, CLOB, and NCLOB columns, where <LOBColName> is the name of the column of type BLOB, CLOB, and NCLOB. By using the Update_<LOBColName> operation, adapter clients can update values in an LOB column. For the BLOB data type, this operation takes base64binary encoded data as the parameter, whereas for the CLOB and NCLOB data types, this operation takes a string filter as the parameter.Note
The
Update_<LOBColName>operation:- Is not supported for the BFILE data type. Adapter clients can alternatively use the Update operation. For more information, see Operations on Tables That Contain BFILE Data Types.
- Is not exposed for interface views and views.
- Must be performed as part of a transaction. To ensure this, the UseAmbientTransaction binding property must be set to True. For information about the UseAmbientTransaction binding property, see Rad about the BizTalk Adapter for Oracle E-Business Suite Binding Properties.
- Is not supported for the BFILE data type. Adapter clients can alternatively use the Update operation. For more information, see Operations on Tables That Contain BFILE Data Types.
Important
The Oracle E-Business adapter surfaces a Read_<LOBColName> and an Update_<LOBColName> operation for each LOB column in a table. So, if there are two LOB columns in a table (LOBCol1 and LOBCol2), you have two Read_<LOBColName> operations (Read_LOBCol1 and Read_LOBCol2) and two Update_<LOBColName> operations (Update_LOBCol1 and Update_LOBCol2).
More good info
Invoking the
Read_<LOBColName>andUpdate_<LOBColName>operations on a table in the underlying database in Oracle E-Business Suite using BizTalk Server, see Run Operations on Tables with Large Data Types Using BizTalk Server.Message structure and SOAP actions for performing
Read_<LOBColName>andUpdate_<LOBColName>operations, see Message Schemas for Special LOB Operations.