Creating a BEA Tuxedo ATMI Client


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Documentation \| Tutorials for Developing BEA Tuxedo ATMI Applications \| Local Topics \| Previous Topic \| Next Topic \| Contents

Creating a BEA Tuxedo client is just like creating any other program in the C or C++ programming language. The BEA Tuxedo system provides you with a C-based programming interface known as the BEA Tuxedo Application-to-Transaction Monitor Interface or ATMI. The ATMI is an easy-to-use interface that enables the rapid development of BEA Tuxedo clients and servers.

Note: BEA Tuxedo ATMI also supports a COBOL interface. (The examples shown here illustrate the C/C++ API.)

Client Tasks

Clients perform the following basic tasks:

Clients may need to call tpchkauth() to determine the level of security required to join an application. Possible responses are: no security enabled, application password enabled, application authentication enabled, access control lists enabled, link-level encryption, public key encryption, auditing. (This is optional depending on whether you are using security levels.)
Clients call tpinit() to connect to a BEA Tuxedo application. Any required security information is passed to the application as arguments for tpinit().
Clients perform service requests.
Clients call tpterm() to disconnect from a BEA Tuxedo application.
Tasks Performed by a Client

See Also

Writing Clients in Programming BEA Tuxedo ATMI Applications Using C
Administering Security in Using Security in CORBA Applications
Using BEA Tuxedo Messaging Paradigms in Your Application
What Are Typed Buffers? in Introducing BEA Tuxedo ATMI
What You Can Do Using the ATMI in Introducing BEA Tuxedo ATMI
Setting Up Security in Introducing BEA Tuxedo ATMI