Verifying the BEA Tuxedo Software Installation


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

Installing the BEA Tuxedo System

To verify that you have successfully installed the BEA Tuxedo system software on a server platform, check the directory structure added to your system for the BEA Tuxedo system files, and try configuring and executing the sample application provided. This section describes the directory structure and provides instructions for running the sample application.

Checking the Directory Structure After BEA Tuxedo System Installation

When the BEA Tuxedo system is installed, the directories shown in the following diagram are created. This diagram reflects the directory structure when all packages in the BEA Tuxedo development environment are installed.

BEA Tuxedo System Directory Structure

The contents of each directory are described below. $TUXDIR is the base directory for the BEA Tuxedo system software. $TUXDIR must be an empty directory for which you have read, write, and search (execute) permissions.

$TUXDIR/bin: Contains executable programs.
$TUXDIR/cobinclude: Contains copylib entries for use in COBOL programs.
$TUXDIR/help: Contains the on-line help files for the BEA Administration Console.
$TUXDIR/include: Contains C language header files. May include subdirectories such as rpc, depending on the platform.
$TUXDIR/lib: Contains compiled object files, including dynamic shared libraries (for platforms on which the BEA Tuxedo system uses dynamic shared libraries) and other object files needed to build BEA Tuxedo system clients and servers.
$TUXDIR/locale: Contains subdirectories to support the localization of system messages.
$TUXDIR/locale/C: Contains message catalogs for the default locale (U.S. English).
$TUXDIR/samples: Contains several subdirectories with sample applications.
$TUXDIR/udataobj: Contains other files required by the BEA Tuxedo system.
$TUXDIR/udataobj/jolt: Contains the files for the Jolt software components you selected to install.
$TUXDIR/udataobj/webgui: Contains the Java and image files for the BEA Administration Console.

Running a Sample Application

To verify that you have successfully installed the BEA Tuxedo system software on a server platform, run the simpapp application, which can be found in the directory $TUXDIR/samples/atmi/simpapp.

Note: Instructions for setting up and running simpapp through the BEA Administration Console are provided in the BEA Administration Console Online Help.

simpapp is a non-distributed application consisting of a server, client, and configuration file. This "simple application" converts strings from lowercase to uppercase. The server simpserv offers a single service called TOUPPER. The client simpcl is invoked with a single argument, which is a lower-case 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

Configuring and Running simpapp

To configure and run simpapp, complete the following 10-step procedure.

Note: This procedure is also provided in the README file in $TUXDIR/samples/atmi/simpapp, and in Tutorial for simpapp, a Simple C Application in Tutorials for Developing a BEA Tuxedo Application.

Set and export the environment variables used by the BEA Tuxedo system. You can do this by executing the Bourne shell script $TUXDIR/tux.env.
Create a working directory for your sample application and cd to it.
```
cd /home/me
mkdir workplace
cd workplace
```
Then set and export an environment variable for your working directory.
```
MYDIR=/home/me/workplace
export MYDIR
```
Copy the simpapp files to your working directory. You will need to edit one of them: the configuration file, ubbsimple. Make sure that the client and server files, simpcl and simpserv, are executable, and that the configuration file, ubbsimple, is writable. For example:
```
cp $TUXDIR/samples/atmi/simpapp/* .
chmod 755 simpserv simpcl
chmod 644 ubbsimple
```
Note: If compiled client and server programs are not available in your simpapp directory, you must compile the source files for them now by entering the following commands.
```
buildclient -o simpcl -f simpcl.c
buildserver -o simpserv -f simpserv.c -s TOUPPER
```
In the sample configuration file (ubbsimple), replace the strings shown in angle brackets with values appropriate to your BEA Tuxedo system installation. Comments in ubbsimple explain how to customize the file. Set the following parameters in the UBBSIMPLE file:
- Set IPCKEY to a valid IPC key. This value must be greater than 32,768 and less than 262,143.
- Set APPDIR to the same value as MYDIR.
- Set TUXCONFIG to the literal path name corresponding to $MYDIR/tuxconfig (in our example, /home/me/workplace/tuxconfig).
- Set machine-name to the name of your system. To determine the name of your system on a UNIX machine enter the command:
```
uname -n
```
Initialize and export the TUXCONFIG environment variable, which is used by several BEA Tuxedo system commands.
```
TUXCONFIG=$MYDIR/tuxconfig
export TUXCONFIG
```
Create the binary version of your edited configuration file by invoking tmloadcf(1), which produces a file named tuxconfig. This file, referenced by the TUXCONFIG environment variable, provides the BEA Tuxedo system with a description of the application configuration at run time.
```
tmloadcf -y ubbsimple
```

Boot simpapp by typing the following command.

tmboot -y

If the boot succeeds, output similar to the following is displayed and you can proceed to step 9.

Output produced by tmboot -y

Booting all admin and server processes in /home/me/workplace/tuxconfig
INFO: BEA TUXEDO(r) System Release 7.1
INFO: Serial #: 000102-9125503751, Maxusers 25
Booting admin processes ...
exec BBL -A:
     process id=24180 ... Started.
Booting server processes ...
exec simpserv -A :
     process id=24181 ... Started.
2 processes started.

If the boot fails, examine the log named ULOG.mmddyy in your application directory ($MYDIR). The string mmddyy is a placeholder for the date (digits representing the current month, day, and year) that will make up the end of the filename. If you see a message such as the following, near the end of the log
```
can't create enough semaphores for BB
```
then the Interprocess Communication (IPC) resources configured in your operating system are not adequate for running simpapp.

To confirm this hypothesis, invoke the BEA Tuxedo system command tmloadcf(1) and specify the name of your configuration file, as shown in the following example.
```
tmloadcf -c $MYDIR/ubbsimple
```
If the current value of any IPC parameter configured in your operating system is less than a minimum (either variable or fixed) listed in the tmloadcf output, you must increase the value of that parameter. For instructions on determining and changing the current IPC values for your platform, see the data sheet for your platform in Platform Data Sheets.
If the boot succeeded, you can invoke the client. For example, enter the following command.
```
simpcl "hello world"
```
The following is displayed.
```
Returned string is: HELLO WORLD
```
When you have finished, shut down simpapp with the following command.
```
tmshutdown -y
```