Creating a BEA Tuxedo ATMI Server


	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

Developers use the ATMI programming interface to create a BEA Tuxedo client and server. However, BEA Tuxedo servers are not written by application developers as complete programs (that is, with a standard main). Instead, application developers write a set of specific business functions (known as services) that are compiled along with the BEA Tuxedo binaries to produce a server executable.

When a BEA Tuxedo server is booted, it continues running until it receives a shutdown message. A typical BEA Tuxedo server may perform thousands of service calls before being shut down and rebooted.

Server Tasks

Application developers write the code and the BEA Tuxedo ATMI servers invoke the tpsvrinit() function only when the BEA Tuxedo server is booted. Programmers use this function to open an application resource (such as a database) for later use.
Application developers write the code and the BEA Tuxedo ATMI servers invoke the tpsvrdone() function only when the BEA Tuxedo server is shut down. Programmers use this function to close any application resources opened by tpsvrinit().
Application developers write the code and the BEA Tuxedo ATMI servers request named application services that process client requests. BEA Tuxedo ATMI clients do not call servers by name; they call services. A BEA Tuxedo ATMI client does not "know" the location of the server processing its request.
ATMI servers call the tpreturn() function to end a service request and return a buffer, if required, to the calling client.
Tasks Performed by a Server