WebLogic Tuxedo Connector Programmer's Guide
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
The following sections discuss the Field Manipulation Language (FML) and describe how the WebLogic Tuxedo Connector uses FML.
Note: For more information about using FML, see Programming a BEA Tuxedo Application Using FML.
FML is a set of java language functions for defining and manipulating storage structures called fielded buffers. Each fielded buffer contains attribute-value pairs in fields. For each field:
Note: The WebLogic Tuxedo Connector implements a subset of FML functionality. For more information regarding FML32, refer to FML32 Considerations.
The FML application program interface (API) is documented in the weblogic.wtc.jatmi
package included in the Javadocs for WebLogic Server Classes.
Field tables are generated in a manner similar to Tuxedo field tables. The field tables are text files that provide the field name definitions, field types, and identification numbers that are common between the two systems. To interoperate with a Tuxedo system using FML, the following steps are required:
#Copyright (c) 1990 Unix System Laboratories, Inc.
#All rights reserved
#ident "@(#) apps/bankapp/bankflds $Revision: 1.3 $"
# Fields for database bankdb
# name number type flags comments
ACCOUNT_ID 110 long - -
ACCT_TYPE 112 char - -
ADDRESS 109 string - -
.
.
.
mkfldclass
utility supplied in the weblogic.wtc.jatmi
package. This class is a utility function that reads a FML32 Field Table and produces a Java file which implements the FldTbl interface. There are two instances of this utility:
import java.io.*;
import java.lang.*;
import java.util.*;
import weblogic.wtc.jatmi.*;public final class bankflds
implements weblogic.wtc.jatmi.FldTbl
{
/** number: 110 type: long */
public final static int ACCOUNT_ID = 33554542;
/** number: 112 type: char */
public final static int ACCT_TYPE = 67108976;
/** number: 109 type: string */
public final static int ADDRESS = 167772269;
/** number: 117 type: float */
.
.
.
javac bankflds.java
The result is a bankflds.class
file. When loaded, the WebLogic Tuxedo Connector uses the class file to add, retrieve and delete field entries from an FML32 field.
WebLogic Tuxedo Connector provides a property that provides an alternate method to compile FML tables. You may need to use the DynRdHdr
utility if:
.java
method created by the mkfldclass32 class exceeds the internal Java Virtual Machine limit on the total complexity of a single class or interface. .java
method.Use the following steps to use the DynRdHdr
property when compiling your FML tables:
The arguments for this command are defined as follows:
Once you have created the userTable.class
file, you can modify the FML table and deploy the changes without having to manually create an updated userTable.class
. When the WTC Service is started, WebLogic Tuxedo Connector will load the updated FML table using the location specified in the Resources tab of your WTC service configuration. If the Path_to_Your_FML_Table attribute changes, you will need to use the preceding procedure to update your userTable.java
and userTable.class
files.
Note: The data type specified must be FLAT or NO. If any other data type is specified, the redirection fails.
The TranslateFML
element of the WTCtBridgeRedirect MBean is used to indicate if FML32 translation is performed on the message payload. There are two types of FML32 translation: FLAT and NO.
The message payload is translated using the WebLogic Tuxedo Connector internal FML32/XML translator. Fields are converted field-by-field values without knowledge of the message structure (hierarchy) and repeated grouping.
In order to convert an FML32 buffer to XML, the tBridge pulls each instance of each field in the FML32 buffer, converts it to a string, and places it within a tag consisting of the field name. All of these fields are placed within a tag consisting of the service name. For example, an FML32 buffer consisting of the following fields:
NAME JOE
ADDRESS CENTRAL CITY
PRODUCTNAME BOLT
PRICE 1.95
PRODUCTNAME SCREW
PRICE 2.50
The resulting XML buffer would be:
<FML32>
<NAME>JOE</NAME>
<ADDRESS>CENTRAL CITY</ADDRESS>
<PRODUCTNAME>BOLT</PRODUCTNAME>
<PRODUCTNAME>SCREW</PRODUCTNAME>
<PRICE>1.95</PRICE>
<PRICE>2.50</PRICE>
</FML32>
No translation is used. The tBridge maps a JMS TextMessage into a Tuxedo TypedBuffer (TypedString) and vice versa depending on the direction of the redirection. JMS BytesMessage are mapped into Tuxedo TypedBuffer (TypedCarray) and vice versa.
Remember to consider the following information when working with FML32:
STRING
values. For example, <STRING></STRING>
is skipped in the resulting FML32 buffer. All other types cause WTC to log an error resulting in translation failure.
An alternative option to using the tBridge to automatically translate XML buffers to and from FML/FML32 is to use the XmlFmlCnv
class. The following code listing is an example that uses the XmlFmlCnv
class for conversion to and from XML buffer formats.
import weblogic.wtc.jatmi.TypedFML32;
import weblogic.wtc.jatmi.FldTbl;
import weblogic.wtc.gwt.XmlFmlCnv;
public class xml2fml
{
public static void main(String[] args) {
String xmlDoc = "<XML><MyString>hello</MyString></XML>";
TypedFML32 fmlBuffer = new TypedFML32(new MyFieldTable());
XmlFmlCnv c = new XmlFmlCnv();
fmlBuffer = c.XMLtoFML32(xmlDoc, fmlBuffer.getFieldTables());
String result = c.FML32toXML(fmlBuffer);
System.out.println(result);
}
}
A TypedMBString
object can be used almost identically as a TypedString
object in a WTC application code. The only difference is that TypedMBString
has a codeset encoding name associated to the string data.
This section includes the following topics.
When a Tuxedo message that contains an MBSTRING data is sent to another Tuxedo domain, TypedMBString
uses the conversion function of java.lang.String
class to convert between Unicode and an external encoding. The TypedMBString
has a codeset encoding name associated to the string data.
When a TypedMBString
object is created by a WTC application code, the encoding name is set to null. The null value of the encoding name means that the default encoding name is used for Unicode string to byte array conversion while sending the MBSTRING data to a remote domain. By default, the Java's default encoding name for byte array string is used for the default encoding name.You can specify encoding or accept the default encoding. The following order defines the order of precedence for TypedMBString
.
When a Tuxedo message that contains an MBSTRING data is received from a remote domain, the following actions take place.
FLD_MBSTRING is a field type added to TypedFML32
. In this case, a TypedMBString
object is passed to the TypedFML32
method as the associated object type of FLD_MBSTRING. You can specify the encoding name used for the MBSTRING conversion for a FLD_MBSTRING field.
The following order defines the order of precedence for TypedFML32.
Notes: The following methods must be updated when using FLD_MBSTRING: Fldtype()
, Fchg()
, Fadd()
, Fget()
, and Fdel()
.
The on-demand encoding methods and auto-conversion methods needed in Tuxedo, such as Fmbpack32()
and Fmbunpack32()
are not needed by WebLogic Tuxedo Connector.
![]() ![]() |
![]() |
![]() |