1 Introduction

Header Files and Shared Libraries

The Message Queue C client includes the header files (mqcrt.h), the C client runtime shared library mqcrt, and its direct dependency libraries. When writing a Message Queue C client application, you should include the header files and link to the runtime library mqcrt.

The header files are located in IMQ_HOME/include, and the 32-bit runtime library is located in IMQ_HOME/lib. A 64-bit runtime library is available for the following platforms in the specified location:

• Linux: IMQ_HOME/lib64

• Solaris SPARC: IMQ_HOME/lib/sparcv9

• Solaris x86: IMQ_HOME/lib/amd64

Pre-Processor Definitions

Use the appropriate compiler for your platform, as described in the Oracle GlassFish Server Message Queue Release Notes.

When compiling a Message Queue C client application, you need to specify the pre-processor definition shown for each platform in Table 1-1. This definition is used to support Message Queue fixed-size integer types.

C++ Runtime Library Support

When building a Message Queue C client application, you should be aware that the Message Queue C runtime library is a multi-threaded library and requires C++ runtime library support:

• On Solaris, this support is provided by the Oracle Solaris Studio libCrun C++ runtime library.

• On Linux, this support is provided by the gcc/g++ libstdc++ runtime library.

• On AIX, this support is provided by the C++ runtime library in the in the XLC/C++ Runtime Environment.

• On Windows, this support is provided by Microsoft Windows Visual C++ runtime library msvcrt.

Building the Basic C-Client Sample Programs

The following commands illustrate the process of building and linking the sample application Producer.c on the Solaris, Linux, AIX, and Windows platforms. The commands include the pre-processor definitions needed to support Message Queue C-API fixed-size integer types. For options used to support multithreading, please consult documentation for your compiler.

CC -compat=5 -mt -DSOLARIS -Iheader_path -o Producer \\
    -Lruntime_path -lmqcrt Producer.c

CC -compat=5 -mt -xarch=v9 -DSOLARIS -I$IMQ_HOME/include -o Producer \\
-L$IMQ_HOME/lib/sparcv9 -lmqcrt Producer.c

g++ -DLINUX -D_REENTRANT -I$IMQ_HOME/include -o Producer \\
-L$IMQ_HOME/lib -lmqcrt Producer.c

xlC_r -qthreaded -DAIX -I$IMQ_HOME/include -o Producer \\
-blibsuff:so -l$IMQ_HOME/lib -imqcrt Producer.c

cl /c /MD -DWIN32 -I%IMQ_HOME%\include Producer.c

link Producer.obj /NODEFAULTLIB msvcrt.lib \\
/LIBPATH:%IMQ_HOME%\lib mqcrt.lib

Running the Basic C-Client Sample Programs

Before you run any sample programs, you should start the broker. You can display output describing the command-line options for each program by starting the program with the -help option.

For example, the following command, runs the program Producer. It specifies that the program should connect to the broker running on the host MyHost and port 8585, and that it should send a message to the destination My Topic :

Producer -h MyHost -p 8585 -d MyTopic

The directories that contain the sample programs also include a README file that explains how you should run their respective samples.

To Set Up Tuxedo as a Distributed Transaction Manager

1. Install Tuxedo.

   See Tuxedo documentation for instructions.

2. Set up the following environment variables:

   Environment Variable	Description
   LD_LIBRARY_PATH	Modify to include Message Queue C-API runtime library path and TUXDIR/lib path
   TUXDIR	Tuxedo install root
   PATH	modify to include $TUXDIR/bin and compiler path
   TUXCONFIG	TUXCONFIG filename path
   TLOGDEVICE	Tuxedo transaction log filename path
   MQ_HOME	Message Queue install root
   MQ_LOG_FILE	Message Queue C-API runtime log file name
   MQ_LOG_FILE_APPEND_PID	Set so that Message Queue C-API runtime log file name will be auto-appended with the Tuxedo server process id

   
   

3. Build the Tuxedo transaction monitor server (TMS).

   1. Add the following entry to the $TUXDIR/udataobj/RM file:

      # SUN_MQ:sun_mq_xa_switch:-lmqcrt

   2. Build the TMS executable using buildtms:

      # buildtms -o $TUXDIR/bin/<exe-name> -r SUN_MQ

4. Configure the Tuxedo servers.

   # tmloadcf config-file

   where config-file is the Tuxedo UBBCONFIG file.

To Build the Distributed Transaction Sample Programs

1. Build the server side of the sample application (jmsserver.c).

   # cc -I$IMQ_HOME/include -I$TUXDIR/include -g -c jmsserver.c
   # buildserver -v -t -r SUN_MQ -s SENDMESSAGES,RECVMESSAGES -o jmsserver
   -f jmsserver.o -f -lmqcrt
   

2. Build the client side of the sample application (jmsclient_sender.c and jmsclient_receiver.c).

   # cc -I$TUXDIR/include -c jmsclient_sender.c
   # buildclient -o jmsclient_sender -f jmsclient_sender.o 
   # cc -I$TUXDIR/include -c jmsclient_receiver.c
   # buildclient -o jmsclient_receiver -f jmsclient_receiver.o
   

To Run the Distributed Transaction Sample Programs

1. Start a Message Queue broker.

   # imqbrokerd -tty
   

2. Start the Tuxedo servers.

   # tmboot
   

3. Run the client-side applications.

   # jmsclient_sender
   # jmsclient_receiver
   

4. Confirm the messages are produced to and consumed from the applicable destination.

   # imqcmd list dst -u admin 
   # imqcmd querry dst -t q -n xatestqueue -u admin