How Do I: Create a Tuxedo Control

Type the WTC imported service name. This name should match the service name that is mapped in Create a WebLogic Tuxedo Connector (WTC) Service.

If you are not sure of the service name, you can click Browse and a list of imported WTC service names display. If the service is listed in the WTC Imported Services dialog, you can select it and click Select. If the service you want is not listed, then the service has not been imported into WebLogic Server.

To import a service from the WTC Imported Services dialog, click Import and the Workstation Address dialog displays.

Note that this field corresponds to the annotation attribute: @tuxedo(serviceName).

For information about importing WTC services, see Import New Tuxedo Services.

Service Type

Select the type of service from the menu. This specifies the type of interaction that the Tuxedo Control supports in the Tuxedo service.

Possible values are:

• service: supports synchronous request/response.
• oneway: supports request without response.
• queue: supports tpenqueue and tpdequeue.
• conversational: supports asynchronous request/response.

Note: For more information about specifying queue service types, see How Do I: Create a Tuxedo Control That Uses Queue Type Services.

The default is service.

This field corresponds to the annotation attribute @tuxedo(serviceType).

Buffer Type

Select the type of buffer from the menu. This specifies the type of buffer that the Tuxedo Control will construct to send to the Tuxedo service.

Possible values are:

• Carray used when the data is an unspecified array of characters (byte array), any of which can be null. Tuxedo equivalent: CARRAY.
• FML used when the data contains named fields of simple types each with a maximum length of 65 K bytes.
• FML32 used when the data contains named fields including nested FML32 fields each having a maximum length of 4 GB.
• String used when the data contains a simple string as its only contents.
• View used to define C or COBOL structures for a Tuxedo application and to define an equivalent Java TypedView buffer for a WebLogic application. A view description file in which the fields and types that appear in the data structure are defined, must be available to client and server processes that use a data structure described in a VIEW typed buffer. Encoding and decoding are performed automatically if the buffer is passed between machines of different types.
• View32 is equivalent to VIEW but uses 32 bits for length and count fields, which allows for larger and more fields.
• XML used when data is an XML document. Data input to methods must be in the form of a Java String or an XML Bean. Tuxedo equivalent: XML for Tuxedo Release 7.1 and higher.

Note: For input XML using data dependent routing, remove all comments generated by the Workshop test browser in the XML buffer. Depending on the location of the comments in the buffer, Tuxedo may have problems parsing the buffer.

• XCOMMON is a synonym for the view buffer type. An XCOMMON buffer is represented by a Java class extending the TypedXCommon class. It is identical in semantics to a view buffer.
• XCTYPE is a synonym for the view buffer type. An XCTYPE buffer is represented by a Java class extending the TypedXCType class. It is identical in semantics to a view buffer.
• XOCTET is simply a byte array and is a synonym for the CARRAY buffer type in Tuxedo.
• none used when no input buffer is to be used in the request to the Tuxedo service. If the method signature contains input parameters, an error is generated.
• unknown

The default is none.

Note that this field corresponds to the annotation attribute: @tuxedo(bufferType).

Field Tables

Type the name of the field table for the Tuxedo service when using fml or fml32 buffers. You should specify the field table when using fml or fml32 buffers that are sent or act as reply buffers from the called service. The name of the field table should match the classes generated with the mkfldclass or mkfldclass32 utilities.

For buffer types fml and fml32, WTC needs the names and types of the fields the buffer can contain. These are described in field table classes created with mkfldclass and mkfldclass32 utilities.

For more information about mkfldclass and mkfldclass32 utilities, see WebLogic Server Javadoc.

Note that this field corresponds to the annotation attribute: @tuxedo(fieldTables).

Return View Classes

Type the names of the view classes that correspond to the view buffer types that can be received from the Tuxedo service. This field is only required when the Tuxedo service returns a view or view32 buffers. These classes are independent from the Send View Class attribute which is used to specify the view or view32 class that represents the view buffer the Tuxedo service expects as an input.

Note: The value of this attribute may be a list of classes so that a single Tuxedo service can respond with different VIEW buffers.

For information about viewj and viewj32 utilities, see WebLogic Server Javadoc.

Note that this field corresponds to the annotation attribute: @tuxedo(viewClasses).

Send View Class

If you have selected view or view32 in the Buffer type field, the Send View Class field becomes active. This attribute provides the name of the class that represents the view/view32 buffer the service is expecting as an input buffer. This view class is used to create the TypedView buffer.

Note that this field corresponds to the annotation attribute: @tuxedo(sendViewClass).