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   |   Programming   |   Topic List   |   Previous   |   Next   |   Contents

   Using the BEA Tuxedo System /Q Component

While it might prove interesting to build and run the sample application using runserver, you will probably find it more instructive to examine the individual pieces of the application. In this topic, we suggest some things that we recommend you look at and try; you will undoubtedly be able to think of others as you explore the application more closely.

The script setenv is an example of a file often used in BEA Tuxedo development. Three of the variables that are set (TUXDIR, APPDIR, and PATH) are needed whenever you are working with the BEA Tuxedo system. Notice that if you are running on a SUN machine, there is another bin you must have at the beginning of your PATH variable. LD_LIBRARY_PATH, SHLIB_PATH, or LIBPATH are important if you are building the system with shared libraries. The correct variable to use depends on your operating system. TUXCONFIG must be set before you can boot the system. QMADMIN can be set in a variable or provided on the qmadmin(1) command line.

Points to consider: should you plan to have such a file where you will be doing your BEA Tuxedo /Q work? Should you have a command in your .profile so that you set your environment as you log in?

Notice that the makefile uses buildserver(1) and buildclient(1) to build the server and client, respectively. You can, of course, execute these commands individually or use the capability of make to keep the application current.

While we are on the subject of the makefile, this might be a good time to look through the .c files for the client and server programs. Of particular interest in connection with BEA Tuxedo /Q are the tpenqueue and tpdequeue calls. Notice particularly the values for the qspace and the qname arguments. When we look at the configuration file, we will see where those values come from.

The three most pertinent entries in the configuration file are the CLOPT parameters for the TMQUEUE and TMQFORWARD servers and the OPENINFO parameter in the *GROUPS entry. We will extract those items to call them to your attention here:

# First the CLOPT parameter from TMQUEUE:
        CLOPT = "-s QSPACENAME:TMQUEUE --  "
# Then the CLOPT parameter from TMQFORWARD:
        CLOPT="-- -i 2 -q STRING"
# Finally, the OPENINFO parameter from the QUE1 group:
        OPENINFO = "TUXEDO/QM:<APPDIR pathname>/QUE:QSPACE"

The CLOPT parameter from TMQUEUE specifies a service alias of QSPACENAME. Look back again at client.c and check the qspace argument of tpenqueue and tpdequeue. The CLOPT parameter for TMQFORWARD specifies a service STRING by means of the -q option. This is also the name given to the queue where messages are enqueued for that service and is specified as the qname argument of tpenqueue in client.c.

The tmloadcf(1) command is used to compile the ASCII configuration file into a TUXCONFIG file.

The script in crlog invokes tmadmin(1) to create a device list entry for the TLOG and then create the log for the site specified in our configuration. Because all messages for the queued message facility are enqueued and dequeued within transactions, you must have a log in which to keep track of transactions managed by the TMS_QM server.

The script in crque invokes qmadmin(1) to create the queue space and queues for the sample application. Notice that the queue space is named QSPACE (that is also the name specified as the last argument of the OPENINFO parameter in the configuration file). Queues named STRING and RPLYQ are created. In the qspacecreate portion of the script an error queue is named, but the script does not include any qcreate command to create that queue. That is a modification you might want to make later.

After making the application programs, loading TUXCONFIG, and creating the queue space and queues, the next step is to boot the application and run it. The command to boot is

tmboot -y

The -y option keeps tmboot from prompting for an okay before booting.

The sample application is run simply by entering the command:

client

The tmshutdown command is used to bring the application down.

The runsample script includes three commands that restore the environment to the state it was in before the script was run. The make clean command uses make to remove the object and executable files for the client and server.

The rmipc command is included because the IPC resources for the queue space are not automatically removed by tmshutdown (which does remove the BEA Tuxedo IPC resources used by the application). If you look at rmipc you will find that it invokes qmadmin and uses its version of the ipcrm command, naming QSPACE to identify resources to be removed.

The final command in the script is the rm command, which removes a number of files that are generated by the application. There is no harm in leaving these files; in fact, as you work more with the sample application you will probably want to keep tuxconfig, QUE, and TLOG to save having to recreate them.