Skip Headers
Oracle® Application Server Adapter for Tuxedo User's Guide
10g Release 2 (10.1.2)
B15802-01
  Go To Documentation Library
Home
Go To Product List
Solution Area
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

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

This appendix contains the following sections:

OracleAS Adapter for Tuxedo Message Buffer Support

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


Note:

Synonyms such as X_C_TYPE,and X_OCTET are also recognized.

Unstructured message buffers are wrapped within a record as follows:

User-Defined Message Buffers

Oracle Connect does not support user-defined message buffers.

Data Type Support

This section contains the following topics:

Data Type Mapping

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.

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

Tuxedo Data Type Oracle Connect Data Type
carray string
char string
double double
float double
int int
long int
short int
string string

Data Type Handling

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     -     -