Deploying a Basic Application

Transcription

1 Module Deploying a Basic Application At the end of this module you will be able to ¾ identify the main steps in deploying a basic Tuxedo application ¾ configure a very basic Tuxedo application ¾ start up and shutdown a Tuxedo application ¾ use some basic commands to monitor an application ¾ be able to verify the installation of Tuxedo software -1 Copyright -1

2 Road Map ƒ Basic Configuration and Administration ƒ Verifying a Tuxedo Software Installation ƒ Lab Workshop -2 Copyright -2

3 Section 1 Basic Configuration and Administration At the end of this section you will be able to ¾ edit a simple Tuxedo configuration file ¾ build a binary Tuxedo configuration file ¾ start-up and shutdown a Tuxedo application ¾ list the main steps in deploying a Tuxedo application -3 Copyright -3

4 The Tuxedo Configuration File ƒ Referred to as the UBBCONFIG file but can be any file name;it defines the parameters for Tuxedo to boot (start-up) an application ƒ The UBBCONFIG file is typically created by application developers and modified by the application administrator ƒ The configuration file exists in two formats ¾ UBBCONFIG: text version ¾ TUXCONFIG: binary version, compiled from the UBBCONFIG file; this is the file that is used to actually boot the Tuxedo application domain -4 UBBCONFIG The UBBCONFIG file is an ASCII version of the configuration file. You can create and edit this version with any editor. Sample configuration files are provided with each of the Tuxedo sample applications, including the simple sample simpapp. You must create a UBBCONFIG file for each new application. You can use any of the sample UBBCONFIG files as a starting point and edit it to meet the requirements of your particular application. The syntax used for entries in the file is described in detail in the ubbconfig(5) reference pages in the BEA TUXEDO Reference Manual. TUXCONFIG The TUXCONFIG file is a binary version of the configuration file that you generate from the ASCII version using the tmloadcf command. You cannot create this file directly; a UBBCONFIG file must be created first. You can, however, dynamically modify many (but not all) configuration parameters while the application is running. The TUXCONFIG file contains information used by tmboot to start the Tuxedo administrative server and initialize the bulletin board of a BEA TUXEDO system. The tmadmin command line utility uses the configuration file (or a copy of it) in its monitoring activity. The tmshutdown command references the configuration file for information needed to shut the application down. Copyright -4

5 Simple UBBCONFIG Layout *RESOURCES <parameter>... <value> 6HFWLRQVÃDUHÃGHILQHGÃE\Ã6(&7,21! 5(6285&(6Ã$1'Ã0$&+,1(6ÃDUHÃÃ UHTXLUHGÃ6HFWLRQVÃDQGÃPXVWÃEHÃWKHÃÃÃ ILUVWÃWZRÃVHFWLRQVÃLQÃWKDWÃRUGHU *MACHINES <machine s system name> <parameter>=<value> *52836ÃVHFWLRQÃPXVWÃEHÃGHILQHGÃEHIRUHÃ6(59(56 *GROUPS <Server Group Name> <parameter>=<value> *SERVERS <Server Executable File> <parameter>=<value> SDUDPHWHU YDOXH!ÃPD\ÃEHÃGHILQHGÃDV RQHÃSHUÃOLQHÃRUÃPXOWLSOHÃSDUDPHWHUVÃSHUÃOLQH -5 The Tuxedo Configuration File (UBBCONFIG ) Layout The configuration file is made up of a number of sections indicated by *<SECTION-NAME>. Parameters are defined for a particular section until the next *< SECTION-NAME > is defined. For now we will only define four main sections :RESOURCES, MACHINES, GROUPS, and SERVERS. The *RESOURCES Section defines parameters that are application wide in nature, such as resource (Table Size) limits for the number of Servers or Services for the application. Most of these parameters assume default values if they are not specified and so you will not always see these parameters specified in a UBBCONFIG file. The *MACHINES Section defines parameters for each machine in the configuration and there must be at least one (which will also be the the MASTER machine) entry. The entry is defined by the first parameter which is the actual system/node name assigned to that machine. The *GROUPS Section defines Server Groups. Server Groups (for now) are a convenient method of grouping Servers to facilitate Administration tasks. You can think of these as being similar to users belonging to user groups. However there are other reasons for having Server Groups as we we see later in the course. The *SERVERS section defines the actual application servers that will process the service requests from Tuxedo clients. A server entry is defined by the first parameter which is the server executable file that will be used to start the server process. Except in the RESOURCES section, multiple parameter values can also be especified on a line. Tabs can also be used to enhance readability. Copyright -5

6 A Simple Configuration Example *RESOURCES IPCKEY MASTER SITE1 MODEL SHM *MACHINES GUMBY *GROUPS GROUP1 *SERVERS simpserv,3&ã.h\ãdvvljqhgã E\ÃWKHÃ8VHU 6\VWHP1RGHÃ1DPHÃ IRUÃWKLVÃPDFKLQH LMID=SITE1 /RJLFDOÃ0DFKLQHÃ1DPH DVVLJQHGÃE\ÃWKHÃ8VHU TUXDIR= c:\bea\tux80 APPDIR= c:\tuxa11\exercises\depl" TUXCONFIG="c:\tuxa11\exercises\depl\tuxconfig" LMID=SITE1 GRPNO=1 *URXSÃ1DPHÃDQGÃ*URXSÃ1XPEHUÃDVVLJQHGÃE\ÃWKHÃ8VHU SRVGRP=GROUP1 SRVID=10 ([HFXWDEOHÃ)LOHÃ1DPHÃLQÃ$33',5ÃIRUÃWKLVÃ6HUYHU 6HUYHUÃ,'ÃQXPEHUÃ DVVLJQHGÃE\ÃWKHÃ8VHU -6 *RESOURCES IPCKEY This number is used to allocate O/S IPC resources for the application and must not be in use by other applications on the machine/s. greater than 32,768 and less than 262,143. MASTER This specifies a logical name for the machine that will be the master machine for the application. Any string can be specified - the example uses SITE1. MODEL Defines either a single machine (SHM) or multiple-machine (MP) configuration. *MACHINES <system-name> The machine s system/node name. Obtained with uname -n on UNIX systems, or by looking up the Computer Name value in the Windows Network Control Panel. LMID A user-defined logical name assigned to this machine. This logical name will be used to refer to this machine in other configuration parameters. TUXDIR The absolute pathname of the directory where the Tuxedo software is installed. APPDIR The absolute pathname of the directory where the application servers are located. TUXCONFIG The absolute pathname of the binary configuration file that will be used to boot. *GROUPS <group-name> A user-defined logical name assigned to this server group. LMID The LMID of the machine on which this group of servers is to run. GRPNO A user-defined number assigned to this group. Must be unique for this entry. *SERVERS <server executable file> The file name of the server executable program (in APPDIR). SRVGRP The logical group name to which this server belongs. SRVID A user-defined number assigned to this server; it must be unique within a group. Copyright -6

7 The Deployment Process buildclient &OLHQW F buildserver &OLHQWÃ([HFXWDEOH 6HUYHU F +HDGHUÃ)LOHVÃK 2WKHUÃ2EMHFWÃ)LOHVÃÉÃ /LEUDULHV RÃÉÃOLE 2WKHUÃ+HDGHUÃ)LOHVÃ K 6HUYHUÃ([HFXWDEOH tmboot ERRWV 2WKHUÃ VRXUFHÃILOHV (QYLURQPHQW 9DULDEOHV 'HSOR\HG $SSOLFDWLRQ tmloadcf 8%%&21),* 78;&21),* -7 The Deployment Process The main steps in the deployment sequence are: 1. Set the environment variables. 2. Build the client executables (usually done by the Application Developer). 3. Build the server executables (usually done by the Application Developer). 4. Create/edit the UBBCONFIG text configuration file. Generate the TUXCONFIG binary configuration file. 5. Boot the application (administrative and application servers). Copyright -7

8 Setting Environment Variables ƒ Before running Tuxedo commands we need to set some environment variables ¾ These can usually be set using a batch/shell command script file set TUXDIR=C:\bea\tuxedo80 set PATH=%TUXDIR%\bin;%PATH set TUXCONFIG=C:\labs\\exercises\tuxconfig setenv.bat 7X[HGRÃURRWÃGLUHFWRU\ /RFDWLRQÃRIÃ7X[HGRÃ ELQDU\ÃFRQILJXUDWLRQÃILOH,QFOXGHÃ78;',5ELQ export TUXDIR=/opt/bea/tuxedo80 LQÃWKHÃ3$7+ export PATH=$TUXDIR/bin;%PATH #also need to set library path - shown for SVR4 export LD_LIBRARY_PATH=$TUXDIR/lib:$LD_LIBRARY_PATH export TUXCONFIG=/home/stu01//exercises/tuxconfig setenv.ksh 2QÃ81,;Ã$OVRÃQHHG WRÃVHWÃWKHÃOLEUDU\Ã SDWKÃHQYLURQPHQW YDULDEOH -8 Setting the Environment Variables The variables TUXDIR, PATH, and LD_LIBRARY_PATH (for UNIX, this environment variable may be different depending on UNIX version) always need to be set. Before you can invoke BEA Tuxedo commands, you need to set several environment variables. If you are using Windows, you can explicitly set the environment variables in each window or you can set them up globally through the Control Panel->System->Environment panel or you can use the Control Panel->BEA Tuxedo tool to do so. TUXDIR contains the full pathname of the directory in which the Tuxedo software you installed. UNIX: TUXDIR=/var/opt/tuxedo; export TUXDIR Windows: set TUXDIR=C:\tuxedo You should include the BEA Tuxedo /bin subdirectory in the search path PATH for commands. UNIX: PATH=$PATH:$TUXDIR/bin; export PATH Windows: set PATH=%PATH%:%TUXDIR%\bin LD_LIBRARY_PATH (on SVR4-based systems such as Solaris), SHLIB_PATH (on HP-UX), and LIBPATH (on AIX) define the search path for dynamic shared libraries. For example: LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$TUXDIR/lib; export LD_LIBRARY_PATH Additionally, TUXCONFIG needs to be set before certain Tuxedo commands are executed. It is set to the full pathname of the binary configuration file of a specific BEA Tuxedo application. UNIX: TUXCONFIG=/var/opt/tuxapp1/tuxconfig; export TUXCONFIG Windows: set TUXCONFIG=C:\tuxapp1\tuxconfig Copyright -8

9 Compiling the UBBCONFIG File ƒ Use tmloadcf to build the binary configuration file from the UBBCONFIG \> tmloadcf -y ubbconfig.nt \> dir ubbconfig.nt WPORDGFIÃFUHDWHVÃWKHÃELQDU\ tuxconfig HTXLYDOHQWÃRIÃ ubbconfig.nt... tmloadcf Options -y Description overwrite existing TUXCONFIG unconditionally only perform syntax checks on the UBBCONFIG file -n ƒ Use tmunloadcf to obtain the text version of a TUXCONFIG binary file ¾ tmunloadcf > UBB_text -9 Creating the TUXCONFIG File The UBBCONFIG application configuration file can be created/modified with any text editor. BEA Tuxedo uses a binary file generically known as TUXCONFIG for its actual operation. The tmloadcf(1) command is used to compile the UBBCONFIG text file to a TUXCONFIG file. When tmloadcf is executed, the TUXCONFIG environment variable must be set to the full path name of the device or system file where TUXCONFIG is to be loaded. The UBBCONFIG and TUXCONFIG files can be assigned any file name by the Administrator. tmunloadcf The tmunloadcf(1) command can convert a TUXCONFIG back to a text file (UBBCONFIG). The file that is read is determined by the TUXCONFIG environment variable. This command produces output that is a superset of the UBBCONFIG file as all the default parameter settings are also output. Example use: tmunloadcf > output_text Copyright -9

10 Building the Client ƒ Use buildclient to build the client ([DPSOH8VHRIbuildclient \> buildclient -o simpcl 1DPHÃRIÃUHVXOWLQJ FOLHQWÃH[HFXWDEOHÃILOH \> dir ubbconfig.nt tuxconfig simpcl.c simpcl.obj simpcl.exe... -f simpcl.c &OLHQWÃ&ÃVRXUFH SURJUDP buildclient FRPSLOHVÃWKHÃ&ÃVRXUFHÃ ILOHÃFUHDWHVÃREMHFWÃILOHVÃDQGÃOLQNVÃ WKHPÃLQWRÃDQÃH[HFXWDEOHÃSURJUDPÃILOH -10 As an Administrator, you would probably never need to build the client executables as these are activities performed by the Application Developers. However, knowing the process of doing so will enable you to build and run a test application to verify that the Tuxedo software has been correctly installed after a new installation or upgrade. Copyright -10

11 Building the Server ƒ Use buildserver to build the server ([DPSOH8VHRIbuildserver \> buildserver -o simpserv 1DPHÃRIÃUHVXOWLQJ VHUYHUÃH[HFXWDEOHÃILOH \> dir ubbconfig.nt tuxconfig simpcl.c simpcl.obj simpcl.exe... simpserv.obj simpserv.exe -f simpserv.c 6HUYHUÃ&ÃVRXUFH SURJUDP -s TOUPPER 1DPHÃRIÃWKHÃ6(59,&(Ã SURYLGHGÃLQÃWKLVÃVHUYHU buildserver FRPSLOHVÃWKHÃ&ÃVRXUFHÃ ILOHÃFUHDWHVÃREMHFWÃILOHVÃDQGÃOLQNVÃ WKHPÃLQWRÃDQÃH[HFXWDEOHÃILOH -11 The buildserver is run with parameters similarly to buildclient but a service name or names must be specified with the -s option for the server. Copyright -11

12 Booting the Tuxedo Application ƒ Boot the Tuxedo application with tmboot WPERRW VWDUWVÃDOOÃDGPLQLVWUDWLYH ([DPSOHÃ8VHÃRIÃtmboot DQGÃDSSOLFDWLRQÃVHUYHUV \ÃLVÃWRÃLQGLFDWHó\HV ÃWRÃDQ\ÃSURPSW \> tmboot -y Booting all admin and server processes in tuxconfig INFO: BEA TUXEDO, Version 7.1 INFO: Serial #: , Expiration , Maxusers 20 INFO: Licensed to: BEA SYSTEMS *** SYSTEM TEST *** Booting admin processes... exec BBL -A : process id= Started. Booting server processes exec simpserv -A : process id= Started. 2 processes started. 7KLVÃLVÃWKHÃ%XOOHWLQÃ%RDUGÃ/LDLVRQ %%/ÃDGPLQLVWUDWLYHÃSURFHVV 7KLVÃLVÃWKHÃVLPSVHUY VHUYHUà DSSOLFDWLRQÃZHÃMXVWÃFUHDWHG 7KHÃ$ÃRSWLRQÃLVÃWRÃDGYHUWLVH DOOÃWKHÃVHUYHU VÃVHUYLFHV \> -12 Some Options to the tmboot command Most of the options to tmboot are related to booting parts of the entire application. A partial list of some useful options: -A causes only the administrative servers (BBL etc.) to be booted -g grpname causes only the servers belonging to this specific group to be booted -i srvid causes all servers with a specific server ID to be booted -S causes all application servers to be booted -s server-name causes all servers with a specific server (executable file )name to be booted Using tmboot The user that created the TUXCONFIG file is the administrator of the application. If security is enabled, only the administrator can execute the tmboot command. Copyright -12

13 Monitoring an Active Application ƒ Use tmadmin(1)to ¾ Monitor a running system - some commands» printserver (psr) to get information on servers» printservice (psc) to get information on services ¾ Perform administrative tasks» Boot and shut down the application or parts of it such as specific server processes ƒ Run-time administration is covered in more detail later in the course ¾ There is also the graphical Administration Console tool but we will focus on using tmadmin in this course -13 Monitor a Running System: tmadmin(1) It is possible to monitor a running system through the tmadmin(1) program. System parameters and statistics may be displayed. Analysis of the information may lead you to boot additional servers or change service priorities. The most frequently used commands allow you to examine available servers (psr), services (psc), message queues (pq), and client (pclt) information Copyright -13

14 Example of tmadmin usage & output printserver (psr) -14 Print Server Information: psr The slide shows sample output from the printserver (psr) command. Some of the information displayed: Prog Name: server executable file name Queue Name: name of the queue to which the server is attached Grp Name: server group name (UBBCONFIG *SERVERS section SRVGRP parameter) ID: numeric identifier of the server (UBBCONFIG *SERVERS SRVID) RqDone: number of service requests the server has performed Load Done: (we have not discussed the service load factor yet) Current Service: the current service the server is performing. The entry will say IDLE if the server is not currently doing any work. For more information on the tmadmin command, refer to tmadmin(1) in the BEA Tuxedo Reference section documentation. Copyright -14

15 printservice (psc) tmadmin - psc -15 Print Service Information: psc The slide shows sample output from the printservice (psc) command: The command lists information on all services offered by all executable servers of the system. The output columns are explained as follows: Service Name: the service name actually advertised by BEA Tuxedo, which may be called by a service request from a client Routine Name: the function name of the service (usually the same as service name) Prog Name: the server executable name (the + indicates some text was truncated) Grp Name: the group name for that server (SRVGRP) ID: the numeric identifier of the server (SRVID) Machine: the LMID of the machine on which the server resides # Done: the number of requests the service routine has performed Status: the current status of the service Copyright -15

16 Running the Client Application ƒ Run the client using the client executable 7KHÃHQYLURQPHQWÃYDULDEOHVÃ78;',5Ã3$7+Ã78;&21),*ÃQHHGÃWRÃEHà VHWÃEHIRUHÃUXQQLQJÃDÃ7X[HGRÃFOLHQW 7KHÃ/LEUDU\Ã3DWKÃYDULDEOHÃPD\ÃDOVRÃEHÃQHHGHGÃIRUÃ81,;ÃV\VWHPV 5XQQLQJÃWKHÃ7X[HGR VLPSFO &OLHQW \> simpcl hello WoRlD HELLO WORLD \> 5XQÃWKHÃFOLHQWÃH[HFXWDEOHà VLPSFO ZLWKÃDÃWH[Wà DUJXPHQWÃVXFKÃDVÃóhElLo WoRlD VLPSFO FDOOVÃWKHÃ72833(5à VHUYLFH VLPSFO GLVSOD\VÃWKHÃUHVXOWÃIURPà WKHÃVHUYHUÃWKHÃWH[WÃKDVÃEHHQà FRQYHUWHGÃWRÃXSSHUFDVH -16 Running a Tuxedo Client Once the Tuxedo client has been built, it can be run at any time just as a regular executable program. However the environment variables TUXDIR, PATH, and TUXCONFIG need to be set before running the client. Copyright -16

17 Viewing the User Log File ƒ All Tuxedo system messages are logged to the user log (ULOG) file, ULOG.mmddyy ƒ A ULOG message consists of two parts ¾ Tag - time of day (hhmmss), the name of the machine, and the name and identifier of the process logging the message ¾ Text - BEA Tuxedo system message, with a message catalog name, a message number, and the text of the message ([DPSOH gumby!simpserv.27190: LIBTUX_CAT:262: std main starting -17 User Log File All Tuxedo system messages are logged to a text file, referred to as the ULOG file. The actual filename is ULOG.mmddyy, where yy is year, mm is the month, and dd is the day in two-digit numeric formats. A new file is created for every day that the Tuxedo application is running. For example, the ULOG file for August 15, 2001 would be named ULOG A user log message consists of the following two parts: Tag - Includes the time of day (hhmmss), the name of the machine as returned by the -n option of uname, and the name and identifier of the process logging the message Text - Includes a Tuxedo message with a message catalog name, a message number, and the text of the message. You can use the catalog name and number as an index to the BEA Tuxedo System Message Manual, which contains detailed information on a message. In the example on the slide, the logged message indicates a server process starting up. Further information (any any corrective action) on the LIBTUX_CAT:262 message can be obtained in the Messages section of the Tuxedo documentation. Copyright -17

18 Shutting Down the Application ƒ Shutdown the servers with the command tmshutdown ([DPSOHÃ8VHÃRI tmshutdown 6KXWGRZQÃDOOÃVHUYHUVÃUHPRYHÃ,3&Ã UHVRXUFHV 8VHÃtmshutdown -y WRÃDYRLGÃJHWWLQJÃ WKHÃSURPSWÃWRÃVKXWGRZQ -18 Shut Down an Application: tmshutdown(1) The tmshutdown(1) command is the reverse of the tmboot(1) command and shuts down part or all of the BEA Tuxedo application. The options tmboot uses for partial booting (-A, -g, -i, -S, -s) are also supported in tmshutdown. Using tmshutdown The user that created the TUXCONFIG file is the administrator of the application and the one that can boot and shutdown the application. The application only can be shut down from the machine designated as the MASTER in the configuration file. When the entire application is shut down, tmshutdown removes the IPC resources associated with the application. The associated IPC resources may not be removed if the BBL process is stopped or killed without using tmshutdown. If this happens, the IPC recoursec have to be removed manually using the ipcrm command. Copyright -18

19 Review In this section, we discussed ¾ the required sections and parameters of the Tuxedo configuration file ¾ the main steps in deploying a Tuxedo application ¾ setting the Tuxedo environment variables ¾ building a binary Tuxedo file ¾ starting and stopping a Tuxedo application ¾ monitoring a Tuxedo application -19 Copyright -19

20 Road Map ƒ Basic Configuration and Administration ƒ Verifying a Tuxedo Software Installation ƒ Lab Workshop -20 Copyright -20

21 Section 2 Verifying a Tuxedo Software Installation ƒ At the end of this section you will be able to ¾ run the Tuxedo sample application to verify an installation of the Tuxedo software -21 Copyright -21

22 A Test Application ƒ A sample application simpapp is provided with the Tuxedo software ¾ <TUXDIR>/ apps/simpapp (Tuxedo 6.5) ¾ <TUXDIR>/ samples/atmi/simpapp (Tuxedo 7.1, 8.0) ƒ simpapp: A simple, single-machine application; one server & one client ¾ Server : offers a single service, TOUPPER ¾ Client : run with one argument, a string that will be converted to upper case by TOUPPER ¾ This is the same application used in the upcoming lab exercise -22 Testing a Sample Application To verify that you have successfully installed the BEA Tuxedo system software on a server platform, you can try configuring and executing the sample application found in the sample applications directory Tuxedo 6.x: <TUXDIR>/apps/simpapp (Tuxedo 7.1, 8.0): <TUXDIR>/samples/atmi/simpapp This is the same application that we just ran in the previous lab exercise! Copyright -22

23 Running the Simple Application ƒ Determine the machine s hostname ¾ uname -n (UNIX); Computer Name (Windows) ƒ Set the environment variables TUXDIR, PATH, (LD_LIBRARY_PATH) ƒ Modify the configuration file ¾ IPC key, Machine Name, file/directory names ƒ Compile the configuration file, programs ƒ Boot the Tuxedo application ƒ Run the client ƒ Shutdown the Tuxedo application -23 Running a Sample Application The simple application simpapp consists of the following files server C source, client C source, and configuration files. The server simpserv offers a single service called TOUPPER. The client simpcl is invoked with a single argument, which is a string to be converted to upper case. The server returns the converted string to the client, which prints it out. For example, the invocation simpcl "hello world" results in the output Returned string is: HELLO WORLD To configure and run simpapp, follow the steps in the Install Lab in the Lab Exercises. This procedure is also described in the README file in the simpapp application directory. An overview of running this application is discussed on the following pages. Copyright -23

24 Running the Application - Example ƒ The Notes section describes the main steps; sample output after executing tmboot is shown below -24 Running a Sample Application (the main steps) 4. Set the environment variables TUXDIR and PATH as described previously. Initialize and export the TUXCONFIG environment variable, which is used by the Tuxedo system commands. On UNIX: export TUXCONFIG=$MYDIR/tuxconfig On Windows: set TUXCONFIG=%MYDIR%\tuxconfig 5. Build the cleint and server executables: buildclient -f simpcl.c -o simpcl buildserver -f simserv.c -o simpserv -s TOUPPER Edit the ubbsimple configuration file to change the IPC key, machine name, directory names. Create the binary version of your edited configuration file by invoking tmloadcf(1), which produces a file named tuxconfig (as defined by the TUXCONFIG environment variable).this file is then used by the BEA Tuxedo system at runtime to start the application configuration. tmloadcf -y ubbsimple Boot simpapp by typing this: tmboot -y If the application starts up successfully, you will see output similar to that on the slide. Run the simple client: simpcl Hello The output from the program should be the string HELLO that was converted and returned by the TOUPPER service in the simpserv server. Copyright -24

25 Review In this section, we discussed ¾ running the Tuxedo simpapp application to verify the installation of the Tuxedo software -25 Copyright -25

26 Review In this module, we talked about ¾ The basic parameters of the UBBCONFIG file ¾ Deploying a Tuxedo application ¾ Setting the Tuxedo application environment ¾ Booting a Tuxedo application ¾ Shutting down a Tuxedo application ¾ Monitoring an active Tuxedo application ¾ Running a test application to verify Tuxedo installation -26 Copyright -26

27 Lab Workshop Please refer to the Lab Exercises guide and do lab. The suggested time for this lab is 20 minutes. The Instructor will determine when it is appropriate to stop. -27 Copyright -27