### Tuxedo Transport Configuration page (Business Services)

Use this page to configure transport settings for a proxy service using the Tuxedo transport protocol. For more information about the Tuxedo transport, see AquaLogic Service Bus Interoperability Solution for Tuxedo.

Option | To create or edit...
--- | ---
Field Table Classes | Enter the name of the class or classes describing the `FML`/`FML32` buffer received. These are used for the `FML`/`FML32-to-XML` conversion routines to map field names to element names. This is a space separated list of fully qualified class names.
View Classes | Enter the name of the class or classes describing the `VIEW`/`VIEW32` buffer received or sent. These are used for the `VIEW`-to-`XML` or `VIEW32`-to-`XML` conversion routines to map field names to element names. This is a space separated list of fully qualified class names.
Classes Jar | Select a JAR Resource that contains a JAR file with the `FML`/`FML32` or `VIEW`/`VIEW32` classes necessary for this endpoint operation.
Remote Access Point(s) | Select a remote access point from the drop down list that is associated with the Import. The list contains remote access points configured in WTC. A business service cannot be created if there is no associated remote access point. If no remote access points exist or to create a new one, select New. Enter the corresponding Access Point Name and Network Address in the adjacent fields. Upon validation of the endpoint, the access point is added to the WTC configuration for each WTC server. If no WTC server exists, one is created. If more than one URI has been specified, there will be one remote access point field per URI and the URI displays for informative purposes. If more than one URI exists, each requires a different remote access point. If the URI specified already corresponds to an existing WTC resource, the corresponding remote access point displays, but cannot be modified.
Local Access Point(s) | This field appears only when you select New in the Remote Access Point field. From the drop-down list, select a local access point to be associated with the newly created remote access point. If none exist or to create a new one, select New. Enter the corresponding Local Access Point Name and Local Network Address in the adjacent fields.
Request Buffer Type | Select the type of buffer that the remote Tuxedo service will receive.
Request Buffer Subtype | This option is enabled if the previous Request Buffer Type value is VIEW or VIEW32. Enter the buffer subtype with which to associate the request buffer.
Response Required? | Select this check box to indicate a bidirectional call. If not checked, the underlying `tpcall` is invoked with `TPNOREPLY` flag, and a null response is posted asynchronously.
Suspend Transaction? | Select this check box to suspend the transaction, if it exists. This is useful when the remote service does not support transactions.
Dispatch Policy | Select the instance of WebLogic Server Work Manager that you want to use for the dispatch policy for this endpoint. The default Work Manager is used if no other Work Manager exists. This Work Manager is used to asynchronously post a null reply in the case of a one-way invocation. For information about Work Managers, see Using Work Managers to Optimize Scheduled Work and Create Work Manager in the WebLogic Server Administration Console Online Help.
Request Encoding | Specify a character set encoding for requests in Tuxedo transports.
Response Encoding | Specify a character set encoding for responses in Tuxedo transports.
Timeout | Specify the maximum amount of time (in seconds) that the transport run time waits for replies; an integer value that is greater than or equal to 0. If not specified or set to zero (default), replies will time out at BLOCKTIME, the maximum number of seconds that the local WTC access point allows for a blocking call.
Transformation Style | Select one of the following: None - (default) The order of fields may not be respected. Ordered - The fields are presented with all their occurrences in the correct order. Ordered and Grouped - If the fields are logically structured as records, the fields are ordered by occurrence and grouped by record.