Oracle® Application Server Adapter for Tuxedo User's Guide
10g Release 2 (10.1.2) B15802-01 |
|
Previous |
Next |
This appendix contains the following sections:
Oracle Connect provides support for all standard types of OracleAS Adapter for Tuxedo message buffers as I/O:
STRING
: A null terminated character array.
CARRAY
: An array of un-interpreted arbitrary binary data.
XML
: An XML formatted data.
VIEW
: A C structure layout.
VIEW32
: A C structure layout where 32-bit FML identifiers are used.
FML
: A special Tuxedo system type that provides transparent data portability.
FML32
: 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.
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.
This section contains the following topics:
OracleAS Adapter for Tuxedo supports a number of 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 Adapter for Tuxedo and Oracle Application Server is performed internally by Oracle Connect. |
OracleAS Adapter for Tuxedo handles 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.
Tuxedo's restrictions with regard to VIEW fields are preserved.
The following is an example of a VIEW file definition:
VIEW emp #TYPE CNAME FBNAME COUNT FLAG SIZE NULL long lSalary SALARY 1 - - 0 short nDeptnum DEPTNUM 1 - - 0 short nEmpnum EMPLOYEE_NUMBER 1 - - 0 short nJobcode JOBCODE 1 - - 0 string szMessageText MESSAGE_TEXT 1 - 80 "" string szFirstName FIRST_NAME 1 - 16 "" string szLastName LAST_NAME 1 - 21 "" END
The following is an example of a field table that defines the FML field IDs:
*base 100 # name number type flags comments MESSAGE_TEXT 1 string - - # DEPTNUM 100 short - - EMPLOYEE_NUMBER 101 short - - JOBCODE 102 short - - FIRST_NAME 103 string - - LAST_NAME 104 string - - SALARY 105 long - -