Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Getting Started   |   Topic List   |   Previous   |   Next   |   Contents

   Tutorials for Developing a BEA Tuxedo Application

buildserver(1) puts together an executable server built on the BEA Tuxedo systems main(). Options identify the names of the output file, the input files provided by the application, and various libraries that permit you to run a BEA Tuxedo system application in a variety of ways.

buildserver invokes the cc command. The environment variables CC and CFLAGS can be set to name an alternative compile command and to set flags for the compile and link edit phases. The buildserver command is used in bankapp.mk to compile and build each server in the banking application. The following sections describe the six bankapp servers:

• How to Build ACCT Server

• How to Build the BAL Server

• How to Build the BTADD Server

• How to Build the TLR Server

• How to Build the XFER Server

• Step 3: Editing the bankapp Makefile

How to Build ACCT Server

The ACCT server is derived from a file called ACCT.ec that contains the code for the OPEN_ACCT and CLOSE_ACCT functions. It is created in two steps. ACCT.ec is first compiled to an ACCT.o file, which is then specified to the buildserver command so that any compile-time errors can be identified and resolved.

Create the ACCT.o file (performed for you in bankapp.mk):

• The .c file is generated as follows: esql ACCT.ec

• The .o file is generated as follows: cc -I $TUXDIR/include -c ACCT.c

• The ACCT server is created by running the following buildserver command line.

      buildserver -r TUXEDO/SQL \
                  -s OPEN_ACCT -s CLOSE_ACCT \
                  -o ACCT \
                  -f ACCT.o -f appinit.o -f util.o

  Note: The backslash in the preceding command-line entry is a documentation convention that indicates a line break for presentation purposes only. You should enter the command and options on one line.

Following is an explanation of the buildserver command-line options:

• The -r option is used to specify which resource manager access libraries should be link edited with the executable server. The choice is specified with the string TUXEDO/SQL.

• The -s option is used to specify the names of the services in the server that are available to be advertised when the server is booted. If the name of a function that performs a service is different from the corresponding service name, the function name becomes part of the argument to the -s option.
  In bankapp, the function name is always the same as the name of the corresponding service so only the service names themselves need to be specified. It is our convention to spell all service names in all uppercase. For example, the OPEN_ACCT service is processed by the function OPEN_ACCT(). However, the -s option to buildserver does allow you to specify an arbitrary name for the processing function for a service within a server. Refer to the buildserver(1) reference page for details. It is also possible for an administrator to specify that only a subset of the services used to create the server with the buildserver command is to be available when the server is booted.

• The -o option is used to assign a name to the executable output file. If no name is provided, the file is named SERVER.

• The -f option specifies the files that are used in the link-edit phase. (For related information, see the description of the -l option on the buildserver(1) reference page.) The order in which the files are listed depends on function references and the libraries in which those references are resolved. Source modules should be listed before libraries that might be used to resolve their references. If these are .c files, they are first compiled. (In the example above, appinit.o and util.o have been already compiled.) Object files can be either separate .o files or groups of files in archive (.a) files. If more than one filename is given as an argument to the -f option, the list must be enclosed in double quotation marks. Although the -f option takes only one file or one list of files (enclosed in double quotation marks) as an argument, you can include the -f option as many times as necessary on a single command line.

To summarize, the options specified on the buildserver command line used to create the ACCT server performed the following functions:

• The -r option specifies the BEA Tuxedo system SQL resource manager.

• The -s option names the OPEN_ACCT and CLOSE_ACCT services (which are defined by functions of the same name in the ACCT.ec file) to be the services that make up the ACCT server.

• The -o option assigns the name ACCT to the executable output file.

• The -f option specifies that the ACCT.o, appinit.o, and util.o files are to be used in the link-edit phase of the build.

  Note: The appinit.c file contains the system-supplied tpsvrinit() and tpsvrdone(). (Refer to tpservice(3c) reference pages for an explanation of how these routines are used.)

How to Build the BAL Server

The BAL server is derived from a file called BAL.ec that contains the code for the ABAL, TBAL, ABAL_BID, and TBAL_BID functions. As with ACCT.ec, the BAL.ec is first compiled to a BAL.o file before being supplied to the buildserver command so that any compile-time errors can be identified and resolved.

Modify the buildserver command used to create the BAL server as follows.

    buildserver -r TUXEDO/SQL \
                -s ABAL -s TBAL -s ABAL_BID -s TBAL_BID\
                -o BAL \
                -f BAL.o -f appinit.o

Note: The backslash in the preceding command-line entry is a documentation convention that indicates a line break for presentation purposes only. You should enter the command and options on one line.

• Use the -r option to specify the BEA Tuxedo system SQL resource manager.

• Use the -s option to name the ABAL, TBAL, ABAL_BID, TBAL_BID services that make up the BAL server. The functions in the BAL.ec file that define these services have identical names.

• Use the -o option to assign the name BAL to the executable server.

• Use the -f option to specify that the BAL.o and the appinit.o files are to be used in the link-edit phase.

The BTADD server is derived from a file called BTADD.ec that contains the code for the BR_ADD and TLR_ADD functions. The BTADD.ec is compiled to a BTADD.o file before being supplied to the buildserver command.

Modify the buildserver command used to create the BTADD server as follows:

    buildserver -r TUXEDO/SQL \
                -s BR_ADD -s TLR_ADD \
                -o BTADD \
                -f BTADD.o -f appinit.o

Note: The backslash in the preceding command-line entry is a documentation convention that indicates a line break for presentation purposes only. You should enter the command and options on one line.

• Use the -r option to specify the BEA Tuxedo system SQL resource manager.

• Use the -s option to name the BR_ADD and TLR_ADD services that make up the BTADD server. The functions in the BTADD.ec file that define these services have identical names.

• Use the -o option to assign the name BTADD to the executable server.

• Use the -f option to specify that the BTADD.o and appinit.o files are to be used in the link-edit phase.

The TLR server is derived from a file called TLR.ec that contains the code for the DEPOSIT, WITHDRAWAL, and INQUIRY functions. The TLR.ec is also compiled to a TLR.o file before being supplied to the buildserver command.

Modify the buildserver command used to create the TLR server as follows:

    buildserver -r TUXEDO/SQL \
                -s DEPOSIT -s WITHDRAWAL -s INQUIRY \
                -o TLR \
                -f TLR.o -f util.o -f -lm

Note: The backslash in the preceding command-line entry is a documentation convention that indicates a line break for presentation purposes only. You should enter the command and options on one line.

• Use the -r option to specify the BEA Tuxedo system SQL resource manager.

• Use the -s option to name the DEPOSIT, WITHDRAWAL, and INQUIRY services that make up the TLR server. The functions in the TLR.ec file that define these services have identical names.

• Use the -o option to assign the name TLR to the executable server.

• Use the -f option to specify that the TLR.o and the util.o files are to be used in the link-edit phase.

  Note: In this example, the -f option is used to pass an option (-lm) to the cc command, which is invoked by buildserver. The -lm argument to -f causes the math libraries to be linked in at compile time.

(Refer to cc(1) in the UNIX System V User's Reference Manual for a complete list of compile-time options.)

The XFER server is derived from a file called XFER.c that contains the code for the TRANSFER function. The XFER.c is also compiled to an XFER.o file before being supplied to the buildserver command.

Modify the buildserver command used to create the XFER server as follows:

    buildserver -r TUXEDO/SQL \
                -s TRANSFER \
                -o XFER \
                -f XFER.o -f appinit.o

Note: The backslash in the preceding command-line entry is a documentation convention that indicates a line break for presentation purposes only. You should enter the command and options on one line.

• Use the -r option to specify the BEA Tuxedo system SQL resource manager.

• Use the -s option to name the TRANSFER service that makes up the XFER server. The function in the XFER.c file that defines the TRANSFER service has the identical name.

• Use the -o option to assign the name XFER to the executable server.

• Use the -f option to specify that the XFER.o and the appinit.o files are to be used in the link-edit phase.

The topics on creating the bankapp servers are important to your understanding of how the buildserver command is specified. However, in actual practice you are apt to incorporate the build into a makefile; that is the way it is done in bankapp.