To build the server environment for WebSphere MQ for Windows:
Change the fields identified by <> in the following, to the directory paths:
<MQMDIR> the directory path specified when WebSphere MQ was installed, for example g:\Program Files\IBM\WebSphere MQ <TUXDIR> the directory path specified when TUXEDO was installed, for example f:\tuxedo <APPDIR> the directory path to be used for the sample application, for example f:\tuxedo\apps\mqapp To build the server environment and samples:
- Create an application directory in which to build the sample application, for example:
f:\tuxedo\apps\mqapp- Copy the following sample files from the WebSphere MQ sample directory to the application directory:
amqstxmn.mak amqstxen.env ubbstxcn.cfg- Edit each of these files to set the directory names and directory paths used on your installation.
- Edit ubbstxcn.cfg (see Figure 1) to add details of the machine name and the queue manager that you want to connect to.
- Add the following line to the TUXEDO file <TUXDIR>udataobj\rm
MQSeries_XA_RMI;MQRMIXASwitchDynamic; <MQMDIR>\tools\lib\mqmxa.lib <MQMDIR>\tools\lib\mqm.libwhere <MQMDIR> is replaced as above. Although shown here as two lines, the new entry must be one line in the file.- Set the following environment variables:
TUXDIR=<TUXDIR> TUXCONFIG=<APPDIR>\tuxconfig FIELDTBLS=<MQMDIR>\tools\c\samples\amqstxvx.fld LANG=C- Create a TLOG device for TUXEDO. To do this, invoke tmadmin -c, and enter the command:
crdl -z <APPDIR>\TLOGwhere <APPDIR> is replaced as above.- Set the current directory to <APPDIR>, and invoke the sample makefile (amqstxmn.mak) as an external project makefile. For example, with Microsoft Visual C++ , issue the command:
msvc amqstxmn.makSelect build to build all the sample programs.
Figure 1. Example of ubbstxcn.cfg file for WebSphere MQ for Windows*RESOURCES IPCKEY 99999 UID 0 GID 0 MAXACCESSERS 20 MAXSERVERS 20 MAXSERVICES 50 MASTER SITE1 MODEL SHM LDBAL N *MACHINES <MachineName> LMID=SITE1 TUXDIR=“f:\tuxedo” APPDIR=“f:\tuxedo\apps\mqapp;g:\Program Files\IBM\WebSphere MQ\bin” ENVFILE=“f:\tuxedo\apps\mqapp\amqstxen.env” TUXCONFIG=“f:\tuxedo\apps\mqapp\tuxconfig” ULOGPFX=“f:\tuxedo\apps\mqapp\ULOG” TLOGDEVICE=“f:\tuxedo\apps\mqapp\TLOG” TLOGNAME=TLOG TYPE=“i386NT” UID=0 GID=0 *GROUPS GROUP1 LMID=SITE1 GRPNO=1 TMSNAME=MQXA OPENINFO=“MQSeries_XA_RMI:MYQUEUEMANAGER” *SERVERS DEFAULT: CLOPT=“-A -- -m MYQUEUEMANAGER” MQSERV1 SRVGRP=GROUP1 SRVID=1 MQSERV2 SRVGRP=GROUP1 SRVID=2 *SERVICES MPUT1 MGET1 MPUT2 MGET2Change the directory names and directory paths to match your installation. Also change the queue manager name MYQUEUEMANAGER to the name of the queue manager that you want to connect to. Other information that you need to add is identified by <> characters.
The sample ubbconfig file for WebSphere MQ for Windows is listed in Figure 1. It is supplied as ubbstxcn.cfg in the WebSphere MQ samples directory.
The sample makefile (see Figure 2) supplied for WebSphere MQ for Windows is called ubbstxmn.mak, and is held in the WebSphere MQ samples directory.
Figure 2. Sample TUXEDO makefile for WebSphere MQ for WindowsTUXDIR = f:\tuxedo MQMDIR = g:\Program Files\IBM\WebSphere MQ APPDIR = f:\tuxedo\apps\mqapp MQMLIB = $(MQMDIR)\tools\lib MQMINC = $(MQMDIR)\tools\c\include MQMSAMP = $(MQMDIR)\tools\c\samples INC = -f “-I$(MQMINC) -I$(APPDIR)” DBG = -f “/Zi” amqstx.exe: $(TUXDIR)\bin\mkfldhdr -d$(APPDIR) $(MQMSAMP)\amqstxvx.fld $(TUXDIR)\bin\viewc -d$(APPDIR) $(MQMSAMP)\amqstxvx.v $(TUXDIR)\bin\buildtms -o MQXA -r MQSeries_XA_RMI $(TUXDIR)\bin\buildserver -o MQSERV1 -f $(MQMSAMP)\amqstxsx.c \ -f $(MQMLIB)\mqm.lib -v $(INC) $(DBG) \ -r MQSeries_XA_RMI \ -s MPUT1:MPUT -s MGET1:MGET $(TUXDIR)\bin\buildserver -o MQSERV2 -f $(MQMSAMP)\amqstxsx.c \ -f $(MQMLIB)\mqm.lib -v $(INC) $(DBG) \ -r MQSeries_XA_RMI \ -s MPUT2:MPUT -s MGET2:MGET $(TUXDIR)\bin\buildclient -o doputs -f $(MQMSAMP)\amqstxpx.c \ -f $(MQMLIB)\mqm.lib -v $(INC) $(DBG) $(TUXDIR)\bin\buildclient -o dogets -f $(MQMSAMP)\amqstxgx.c \ -f $(MQMLIB)\mqm.lib $(INC) -v $(DBG) $(TUXDIR)\bin\tmloadcf -y $(APPDIR)\ubbstxcn.cfg
Parent topic:
Building the server environment
fg17860_