BEA Logo BEA WebLogic Tuxedo Connector Release 6.1

  Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy

   WebLogic Tuxedo Connector ATMI Programmer's Guide:   Previous topic   |   Next topic   |   Contents   

 

Introduction to JATMI Programming

 

The following sections provide information about the development environment you will be using to write code for applications that interoperate between WebLogic Server and Tuxedo:

Developing WebLogic Tuxedo Connector Applications

In addition to the Java code that expresses the logic of your application, you will be using the Java Application -to-Transaction Monitor Interface (JATMI) to provide the interface between WebLogic Server and Tuxedo. This allows you to develop clients and servers without modifying existing Tuxedo services.

Note: For more information on the WebLogic Tuxedo Connector JATMI, view the WebLogic Tuxedo Connector Javadoc by opening the index.html file in the doc directory of your WebLogic Tuxedo Connector installation.

Developing WebLogic Tuxedo Connector Clients

A client process takes user input and sends a service request to a server process that offers the requested service. WebLogic Tuxedo Connector JATMI client classes are used to create clients that access services found in Tuxedo. These client classes are available to any service that is made available through the WebLogic Tuxedo Connector XML configuration file in the StartUpClass of your WebLogic Server.

Developing WebLogic Tuxedo Connector Servers

Servers are processes that provide one or more services. They continually check their message queue for service requests and dispatch them to the appropriate service subroutines. WebLogic Tuxedo Connector uses EJBs to implement services which Tuxedo clients invoke.

WebLogic Tuxedo Connector JATMI Primitives

The JATMI is a set of primitives used to begin and end transactions, allocate and free buffers, and provide the communication between clients and servers.

Table 1-1 JATMI Primitives

Name

Operation

tpacall

 

Use for asynchronous invocations of a Tuxedo service.

 

tpcall

 

Use for synchronous invocation of a Tuxedo service.

 

tpdequeue

 

Use for receiving messages from a Tuxedo /Q.

 

tpenqueue

 

Use for placing a message on a Tuxedo /Q.

 

tpgetreply

 

Use for retrieving replies from a Tuxedo service.

 

tpterm

 

Use to close a connection to a Tuxedo object.

 

WebLogic Tuxedo Connector Typed Buffers

Note: UNICODE strings are not supported on the Tuxedo environment.

WebLogic Tuxedo Connector provides an interface called TypedBuffers that corresponds to Tuxedo typed buffers. Messages are passed to servers in typed buffers. The WebLogic Tuxedo Connector provides the following buffer types:.

Table 1-2 TypedBuffers

Buffer Type

Description

TypedString

 

Buffer type used when the data is an array of characters that terminates with the null character. Tuxedo equivalent: STRING.

 

TypedCArray

 

Buffer type used when the data is an undefined array of characters (byte array), any of which can be null. Tuxedo equivalent: CARRAY.

 

TypedFML

 

Buffer type used when the data is self-defined. Each data field carries its own identifier, an occurrence number, and possibly a length indicator. Tuxedo equivalent: FML.

 

TypedFML32

 

Buffer type similar to TypeFML but allows for larger character fields, more fields, and larger overall buffers. Tuxedo equivalent: FML32.

 

TypedXML

 

Buffer type used when data is an XML based message. Tuxedo equivalent: XML for Tuxedo Release 7.1 and higher.