B OracleAS Adapters for Tuxedo Message Buffer Support and Data Type Support

OracleAS Adapters for Tuxedo Message Buffer Support

Oracle Connect provides support for all standard types of OracleAS Adapters for Tuxedo message buffers as I/O, as follows:

STRING: A null terminated character array. The data type is character and its length is determined by counting the characters in the buffer until reaching the null character. It is commonly used by C programs.

CARRAY: An array of un-interpreted arbitrary binary data. The application must specify the buffer length for CARRAY message buffers when used as input to ATMI functions.

XML: An XML formatted data. This buffer type enables Tuxedo applications to use XML for exchanging data within and between applications. Tuxedo applications can send and receive simple XML buffers, and route them to the appropriate servers. Data dependent routing is supported for this buffer type.

VIEW (16-bit): A C structure layout. This buffer is used for fixed collections of data elements, structures or records. VIEW records support integral data types such as long integer, character, and decimal. VIEW records do not support structures within structures, nor do they support arrays of structures or pointers.

FML (16-bit): An abstract data type, used to create, access, modify and delete fields. It is a data structure that stores tagged values. Values are typed, can be specified multiple times, and vary in length. Additionally, FML buffers support storage of multiple values for a field. The variable length format of fielded buffers enables multiple field occurrences to be stored and retrieved.

FML (32-bit): An FML type where 32-bit FML identifiers are used.

Note:

Synonyms such as X_C_TYPE, and X_OCTET are also recognized.

Unstructured message buffers are wrapped within a record as follows:

A message buffer of type STRING is wrapped within a record containing a single field of type string with a fixed size.

A message buffer of type CARRAY is wrapped within a record containing a single field of type binary with a fixed size.

A message buffer of type XML is wrapped within a record containing a single field of type XML.

User-Defined Message Buffers

Data Type Support

Data Type Mapping

OracleAS Adapters for Tuxedo support several data types that are used to define metadata in Oracle Studio. The data types are mapped from the Tuxedo data types during the import procedure.

Note:

The mapping of data types between OracleAS Adapters for Tuxedo and Oracle Application Server is performed internally by Oracle Connect.

Table B-1 Data Type Mapping: Tuxedo and Oracle Connect

Tuxedo Data Type

Oracle Connect Data Type

carray

binary

char

string

double

double

float

double

int

int

long

int

short

int

string

string

Data Type Handling

OracleAS Adapters for Tuxedo handle the fields contained in the VIEW file as follows:

Specifying a value greater than one in the COUNT field of the Tuxedo field definition within a VIEW file, translates to array=xx attribute.

Specifying a value in the SIZE field of Tuxedo field definition within a VIEW file, translates to size=yy attribute.

Specifying C in the FLAG field of Tuxedo field definition within a VIEW file, imposes generation of an extra leading COUNTER field to hold the actual count value.

Specifying L in the FLAG field of Tuxedo field definition within a VIEW file, imposes generation of an extra leading LENGTH field to hold the actual length value.

Note:

The L flag is applicable for STRING and CARRAY data types only.

In the case where a COUNT value greater than one is specified for the field, the extra leading LENGTH field is generated as an array. The array entries should hold the actual length values of the corresponding field array entries.

Specifying a value in the NULL field of Tuxedo's field definition within a VIEW file is not reflected in Oracle Connect back-end adapter record.