The Java Simpapp Sample Application

The chapter discusses the following topics:

• How the Java Simpapp sample application works

• Software prerequisites

• The Object Management Group (OMG) Interface Definition Language (IDL) for the Java Simpapp sample application

• Building and running the Java Simpapp sample application

• Using the Java Simpapp sample application

• Using the C++ client application with the Java Simpapp sample application

• Stopping the Java Simpapp Sample Application

Refer to Readme.txt in the \WLEdir\samples\corba\simpapp_java directory for troubleshooting information and the latest information about using the Java Simpapp sample application.

How the Java Simpapp Sample Application Works

The Java Simpapp sample application consists of a Java client application that sends requests to a Java server application. The Java server application provides an implementation of a CORBA object that has the following two methods:

• The upper method accepts a string from the Java client application and converts the string to uppercase letters.

• The lower method accepts a string from the Java client application and converts the string to lowercase letters.

Figure 2-1 illustrates how the Java Simpapp sample application works.

Figure 2-1 The Java Simpapp Sample Application

Software Prerequisites

To run the idltojava compiler used by the Java Simpapp sample application, you need to install Visual C++ Version 5.0 with Service Pack 3 for Visual Studio.

The OMG IDL Code for the Java Simpapp Sample Application

The Java Simpapp sample application implements the CORBA interfaces listed in Table 2-1:

Listing 2-1 shows the simple.idl file that defines the CORBA interfaces in the Java Simpapp sample application. This is the same OMG IDL file used by the C++ Simpapp sample application shipped with version 4.2 of the WebLogic Enterprise (WLE) software. The runme command automatically copies it from the \corba\simpapp_java directory.

Listing 2-1 OMG IDL Code for the Java Simpapp Sample Application

---

Perform the following steps to build and run the Java Simpapp sample application:

1. Copy the files for the Java Simpapp sample application into a work directory.

2. Change the protection attribute on the files for the Java Simpapp sample application.

3. Verify the environment variables.

4. Execute the runme command.

The following sections describe these steps.

Copying the Files for the Java Simpapp Sample Application into a Work Directory

You need to copy the files for the Java Simpapp sample application into a work directory on your local machine. The files for the Java Simpapp sample application are located in the following directories:

Windows NT

drive:\WLEdir\samples\corba\simpapp_java

UNIX

/usr/local/WLedir/samples/corba/simapp_java

You will use the files listed in Table 2-2 to build and run the Java Simpapp sample application.

Changing the Protection Attribute on the Files for the Java Simpapp Sample Application

During the installation of the WLE software, the sample application files are marked read-only. Before you can edit or build the files in the Java Simpapp sample application, you need to change the protection attribute of the files you copied into your work directory, as follows:

Windows NT

prompt>attrib -r drive:\workdirectory\*.*

UNIX

prompt>/bin/ksh

ksh prompt>chmod u+w /workdirectory/*.*

On the UNIX operating system platform, you also need to change the permission of runme.ksh to give execute permission to the file, as follows:

ksh prompt>chmod +x runme.ksh

Verifying the Settings of the Environment Variables

Before building and running the Java Simpapp sample application, you need to ensure that certain environment variables are set on your system. In most cases, these environment variables are set as part of the installation procedure. However, you need to check the environment variables to ensure they reflect correct information.

Table 2-3 lists the environment variables required to run the Java Simpapp sample application.

To verify that the information for the environment variables defined during installation is correct, perform the following steps:

Windows NT

1. From the Start menu, select Settings.

2. From the Settings menu, select the Control Panel.

   The Control Panel appears.

3. Click the System icon.

   The System Properties window appears.

4. Click the Environment tab.

   The Environment page appears.

5. Check the settings for TUXDIR and JAVA_HOME.

UNIX

ksh prompt>printenv TUXDIR

ksh prompt>printenv JAVA_HOME

To change the settings, perform the following steps:

Windows NT

1. On the Environment page in the System Properties window, click the environment variable you want to change or enter the name of the environment variable in the Variable field.

2. Enter the correct information for the environment variable in the Value field.

3. Click OK to save the changes.

UNIX

ksh prompt>export TUXDIR=directorypath

ksh prompt>export JAVA_HOME=directorypath

Executing the runme Command

The runme command automates the following steps:

1. Setting the system environment variables

2. Loading the UBBCONFIG file

3. Compiling the code for the client application

4. Compiling the code for the server application

5. Starting the server application using the tmboot command

6. Starting the client application

7. Stopping the server application using the tmshutdown command

   Note: You can also run the Java Simpapp sample application manually. The steps for manually running the Java Simpapp sample application are described in the Readme.txt file.

To build and run the Java Simpapp sample application, enter the runme command, as follows:

Windows NT

prompt>cd workdirectory

prompt>runme

UNIX

ksh prompt>cd workdirectory

ksh prompt>./runme.ksh

The Java Simpapp sample application runs and prints the following messages:

Testing simpapp
    cleaned up
    prepared
    built
    loaded ubb
    booted
    ran
    shutdown
    saved results
  PASSED

Note: After executing the runme command, you may get a message indicating the Host, Port, and IPCKEY parameters in the UBBCONFIG file conflict with an existing UBBCONFIG file. If this occurs, you need to set these parameters to different values to get the Java Simpapp sample application running on your machine. See the Readme.txt file for information about how to set these parameters.

The runme command starts the following application processes:

• TMSYSEVT

  The BEA TUXEDO system event broker.

• TMFFNAME

  The following three TMFFNAME server processes are started:

  • The TMFFNAME server process started with the -N and -M options is the master NameManager service. The NameManager service maintains a mapping of the application-supplied names to object references.

  • The TMFFNAME server process started with only the -N option is the slave NameManager service.

  • The TMFFNAME server process started with the -F option contains the FactoryFinder object.

• JavaServer

  The Java Simpapp sample application server process. The JavaServer process has one option, simple, which is the Java Archive (JAR) file that was created for the application.

• ISL

  The IIOP Listener process.

Table 2-4 lists the files in the work directory generated by the runme command.

Table 2-5 lists files in the results directory generated by the runme command.

Using the Java Simpapp Sample Application

This section describes how to use the Java Simpapp sample application after the runme command is executed.

Run the Java server application in the Java Simpapp sample application, as follows:

Windows NT

prompt>tmboot

UNIX

ksh prompt>tmboot

Run the Java client application in the Java Simpapp sample application, as follows:

Windows NT

prompt>java -classpath .;%TUXDIR%\udataobj\java\jdk\m3envobj.jar
-DTOBJADDR=%TOBJADDR% SimpleClient
String?
Hello World
HELLO WORLD
hello world

UNIX

ksh prompt>java -classpath .:$TUXDIR/udataobj/java/jdk\
/m3envobj.jar -DTOBJADDR=$TOBJADDR SimpleClient
String?
Hello World
HELLO WORLD
hello world

Note: The Java Simpapp sample client application uses the client-only JAR file m3envobj.jar. However, you could also use the m3.jar file to run the client application.

Using the C++ Client Application with the Java Simpapp Sample Application

A C++ client application is provided with the Java Simpapp sample application to demonstrate interoperabililty between a Java server application and a C++ client application. This section describes the process of building and running the C++ client application.

Build the C++ client application in the Java Simpapp sample application as follows:

1. Copy the files from the following directory to a work directory:

   Windows NT

   \WLEdir\samples\CORBA\simpapp_java

   UNIX

   /usr/local/WLEdir/samples/corba/simapp_java

   Note: The work directory for the Java Simpapp sample application cannot be the same as the work directory for the C++ Simpapp sample application.

2. Change the protection on the files using the following commands:

   Windows NT

   prompt>attrib -r drive:\workdirectory\*.*

   UNIX

   prompt>/bin/ksh

   ksh prompt>chmod u+w /workdirectory/*.*

3. Make sure the UNIX make command or the Windows NT nmake command is in the path of your machine.

4. Set the M3SIMPDIR environment variable to your work directory.

5. Build the C++ client application, as follows:

   Windows NT

   prompt>cd %M3SIMPDIR

   prompt>nmake -f makefile.nt simple_client.exe

   UNIX

   ksh prompt>cd %M3SIMPDIR

   ksh prompt>make -f makefile.mk simple_client

Run the Java server application in the Java Simpapp sample application, as follows:

Windows NT

prompt>tmboot

UNIX

ksh prompt>tmboot

Run the C++ client application in the Java Simpapp sample application, as follows:

Windows NT

prompt>%M3SIMPDIR%\simple_client
String? Hello
HELLO
hello

UNIX

ksh prompt>$M3SIMPDIR/simple_client
String? Hello
HELLO
hello

Stopping the Java Simpapp Sample Application

Before using another sample application, enter the following commands to stop the Java Simpapp sample application and to remove unnecessary files from the work directory:

Windows NT

prompt>tmshutdown -y

prompt>nmake -f makefile.nt clean

UNIX

ksh prompt>tmshutdown -y

ksh prompt>make -f makefile.mk clean