Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	e-docs.beasys.com   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
WLE Doc Home   |   Security & Related Topics   |   Previous   |   Next   |   Contents   |   Index

The topic contains the following sections:

• Building and Running the Security Sample Application

• Building and Running the Secure Simpapp Sample Application

Building and Running the Security Sample Application

The Security sample application demonstrates using Username/Password authentication. The sample application has both C++ and Java client applications. For a description of the Security sample application, see Writing a WLE CORBA Application That Implements Security This section describes how to build the Security sample application and how to use the client applications in the Security sample application.

Perform the following steps to build the Security sample application:

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

2. Verify the settings of the environment variables.

3. Change the protection on the files for the Security sample application.

4. Set the environment variables.

5. Initialize the database.

6. Load the UBBCONFIG file.

7. Compile the client and server sample applications.

8. Start the server application in the Security sample application.

9. Start the C++ client application in the Security sample application.

10. Start the Java client application in the Security sample application.

The following sections describe these steps.

Refer to Readme.txt in the \ WLEdir \samples\corba\university \security directory for troubleshooting information and the latest information about using the Security sample application.

Step 1: Copy the files for the Security sample application into a work directory.

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

Windows NT

drive :\ WLEdir \samples\corba\university \security

UNIX

/usr/ WLEdir /samples/corba/university /security

In addition, you need to copy the utils directory into your work directory. The utils directory contains files that set up logging, tracing, and access to the database used with the Security sample application.

You will use the files listed in Table 6-1 to create the Security sample application.

Table 6-1 Files Included in the Security Sample Application

File	Description
univs.idl	The OMG IDL code that declares the CourseSynopsisEnumerator , Registrar , and RegistrarFactory interfaces.
univss.cpp	The C++ source code for the server application in the Security sample application.
univs_i.h univs_i.cpp	The C++ source code for method implementations of the CourseSynopsisEnumerator , Registrar , and RegistrarFactory interfaces.
univsc.cpp	The C++ source code for the C++ client application in the Security sample application.
UnivSApplet.java	The Java source code for the Java client application in the Security sample application.
univs_utils.h univs_utils.cpp	The files that define database access functions for the CORBA C++ client application.
univs.icf	The Implementation Configuration File (ICF) for the Security sample application.
setenvs.sh	A UNIX script that sets the environment variables needed to build and run the Security sample application.
setenvs.cmd	An MS-DOS command procedure that sets the environment variables needed to build and run the Security sample application.
ubb_s.mk	The UBBCONFIG file for the UNIX operating system.
ubb_s.nt	The UBBCONFIG file for the Windows NT operating system.
makefiles.mk	The makefile for the Security sample application on the UNIX operating system.
makefiles.nt	The makefile for the Security sample application on the Windows NT operating system.
log.cpp , log.h , log_client.cpp , and log_server.cpp	The client and server applications that provide logging and tracing functions for the sample applications. These files are located in the \utils directory.
oradbconn.cpp and oranoconn.cpp	The files that provide access to an Oracle SQL database instance. These files are located in the \utils directory.
samplesdb.cpp and samplesdb.h	The files that provide print functions for the database exceptions in the sample applications.These files are located in the \utils directory.
unique_id.cpp and unique_id.h	C++ Unique ID class routines for the sample applications.These files are located in the \utils directory.
samplesdbsql.h and samplesdbsql.pc	C++ class methods that implement access to the SQL database. These files are located in the \utils directory.
university.sql	The SQL for the University database. This file is located in the \utils directory.
Readme.txt	The file that provide the latest information about building and running the Security sample application.

Step 2: Verify the settings of the environment variables.

Before building and running the Security 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 6-5 lists the environment variables required to run the Security sample application.

Table 6-2 Required Environment Variables for the Security Sample Application

Environment Variable	Description
APPDIR	The directory path where you copied the sample application files. For example: Windows NT APPDIR=c:\ work \securityapp UNIX APPDIR=/usr/ work /securityapp
TUXCONFIG	The directory path and name of the configuration file. For example: Windows NT TUXCONFIG=c:\work\securityapp\tuxconfig UNIX TUXCONFIG=/usr/ work /securityapp/tuxconfig
TUXDIR	The directory path where you installed the WLE software. For example: Windows NT TUXDIR=c:\WLEdir UNIX TUXCONFIG=/usr/local/WLEdir
JDKDIR	The directory path where you installed the JDK software. For example: Windows NT JDKDIR=c:\jdk1.2.2 UNIX JDKDIR=/usr/local/jdk1.2.1 You need to specify this parameter only if you plan to use the Java version of the Secure 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 of the environment variables.

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

Step 3:Change the Protection on the Files for the Security Sample Application.

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

Windows NT

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

UNIX

prompt>chmod u+rw / workdirectory /*.*

Step 4: Set the Environment Variables

Use the following command to set the environment variables used to build the client and server applications in the Security sample application:

Windows NT

prompt>setenvs

UNIX

prompt>/bin/ksh

prompt>. ./setenvs.sh

Step 5: Initialize the Database

Use the following command to initialize the database used with the Security sample application:

Windows NT

prompt>nmake -f makefiles.nt initdb

UNIX

prompt>make -f makefiles.mk initdb

Step 6: Load the UBBCONFIG File

Use the following command to load the UBBCONFIG file:

Windows NT

prompt>tmloadcf -y ubb_s.nt

UNIX

prompt>tmloadcf -y ubb_s.mk

The build process for the UBBCONFIG file prompts you for an application password. This password will be used to log on to the client applications. Enter the password and press Enter. You are then prompted to verify the password by entering it again.

Step 7: Compile the Security Sample Application

The directory for the Security sample application contains a makefile that builds the client and server sample applications in the Security sample application.

Use the following command to build the C++ client and server applications in the Security sample application:

Windows NT

prompt>nmake -f makefiles.nt

UNIX

prompt>make -f makefiles.mk

To build the Java client application in the Security sample application:

Windows NT

prompt>nmake -f makefiles.nt javaclient

UNIX

prompt>make -f makefiles.mk javaclient

Start the system processes and the server application in the Security sample application by entering the following command:

prompt>tmboot -y

Before using another sample application, enter the following command to stop the system processes and the server application in the Security sample application.

prompt>tmshutdown

Step 8: Start the C++ client application

Start the C++ client application in the Security sample application by performing the following steps:

1. At the MS-DOS prompt, enter the following command:

   prompt>univs_client

2. At the Enter student id: prompt, enter any number between 100001 and 100010.

3. Press Enter.

4. At the Enter domain password: prompt, enter the password you defined when you loaded the UBBCONFIG file.

5. Press Enter.

To run the Java client application in the Security sample application, perform the following steps:

1. Modify the following lines in the UnivSApplet.html file:

   code="UnivSApplet.class"
   codebase=.
   to read as follows:

   code="UnivSApplet"
   archive="UnivSApplet.jar,m3envobj.jar"

2. Copy the modified UnivSApplet.html file to the source directory for the Web server (the directory varies by Web server product).

3. Create a UnivSApplet.jar file, as follows:

   1. Create a tmp directory under the directory where you built the sample application and copy the UniversityS subdirectory and the class files it contains into the tmp directory.

      Copy the class files in the Security sample application directory that were generated by the makefile into the tmp directory, set the directory (cd ) to the tmp directory, and issue one of the following commands to create a jar file that contains all the Security sample application classes:
      
      jar -cf ..\UnivSApplet.jar *.* (Microsoft Windows NT systems)
      jar -cf ../UnivSApplet.jar * (UNIX systems)

4. Copy the UnivSApplet.jar file you just created to the source directory for the Web server (the directory name varies by Web server product).

5. Copy the m3envobj.jar file from the appropriate subdirectory (%TUXDIR%\udataobj\java Microsoft Windows NT systems or ${TUXDIR}/udataobj/java UNIX systems) to the Web server source directory.

6. Make sure the Security server application is running, start up your Web browser, and point it to the node where the Web server is running.

   Note: On Microsoft Windows NT systems, the node name needs to be in all uppercase characters. For example, if the node is specified as SERVER in the UBBCONFIG file and in the UnivSApplet.html file, set your browser to http://SERVER/UnivSApplet.html .

7. Modify the following lines in the UnivSApplet.html file:

   code="UnivSApplet.class"
   codebase=.
   to read as follows:

   code="UnivSApplet"
   archive="UnivSApplet.jar,m3envobj.jar"

8. Copy the modified UnivSApplet.html file to the source directory for the Web server (the directory varies by Web server product).

9. After executing the makefile to build the Security sample application, create a UnivSApplet.jar file, as follows:

   1. Create a tmp directory under the directory where you built the sample application and copy the UniversityS subdirectory and the class files it contains into the tmp directory.

      Copy the class files in the Security sample application directory that were generated by the makefile into the tmp directory, set the directory (cd ) to the tmp directory, and issue one of the following commands to create a jar file that contains all the Production sample application classes:
      
      jar -cf ..\UnivSApplet.jar *.* (Microsoft Windows NT systems)
      jar -cf ../UnivSApplet.jar * (UNIX systems)

10. Copy the UnivSApplet.jar file you just created to the source directory for the Web server (the directory name varies by Web server product).

11. Copy the m3envobj.jar file from the appropriate subdirectory (%TUXDIR%\udataobj\java Microsoft Windows NT systems or ${TUXDIR}/udataobj/java UNIX systems) to the Web server source directory.

12. Make sure the Security server application is running, start up your Web browser, and point it to the node where the Web server is running.

    Note: On Microsoft Windows NT systems, the node name needs to be in all uppercase characters. For example, if the node is specified as SERVER in the UBBCONFIG file and in the UnivSApplet.html file, set your browser to http://SERVER/UnivPApplet.html .

    A logon window appears.

13. Enter a number between 100001 and 100010 in the student ID field.

14. Enter the password you defined when you loaded the UBBCONFIG file in the Domain Password field.

15. Click the Logon button.

16. Enter a search string to find a course.

The Secure Simpapp sample application demonstrates using the SSL protocol and certificate-based authentication to protect communications between client applications and the WLE domain. There are C++ and Java versions of the Secure Simpapp sample application.

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

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

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

3. Verify the environment variables.

4. Execute the runme command.

Before you can use the Secure Simpapp sample application, obtain a certificate and private key (IIOPListener.pem ) for the IIOP Listener/Handler from the certificate authority in your enterprise and load the certificate in a Lightweight Directory Access Protocol (LDAP)-enabled directory service. The runme command prompts you for the pass phrase for the private key for the IIOP Listener/Handler.

Step 1: Copy the Files for the Secure Simpapp Sample Application into a Work Directory

You need to copy the files for the Secure Simpapp sample application into a work directory on your local machine. The following sections detail the directory location and sources files for the C++ and Java versions of the Secure Simpapp sample application.

C++ Version of the Secure Simpapp Sample Application

The files for the C++ version of the Secure Simpapp sample application are located in the following directories:

Windows NT

drive:\WLEdir \samples\corba\simpappSSL

UNIX

/usr/local/WLedir /samples/corba/simappSSL

You will use the files listed in Table 6-3 to build and run the C++ version of the Secure Simpapp sample application.

Table 6-3 Files Included in the C++ Version of the Secure Simpapp Sample Application

File	Description
Simple.idl	The OMG IDL code that declares the Simple and SimpleFactory interfaces.This file is copied from the WLE simpappSSL_java directory by the runme command file.
Simples.cpp	The C++ source code that overrides the default Server::initialize and Server::release methods.
Simplec.cpp	The C++ source code for the client application in the Secure Simpapp sample application.
Simple_i.cpp	The C++ source code that implements the Simple and SimpleFactory methods.
Simple_i.h	The C++ header file that defines the implementation of the Simple and SimpleFactory methods.
Readme.html	This file provides the latest information about building and running the C++ version of the Secure Simpapp sample application.
runme.cmd	The Windows NT batch file that builds and runs the C++ version of the Secure Simpapp sample application.
runme.ksh	The UNIX Korn shell script that builds and executes the C++ version of the Secure Simpapp sample application.
makefile.mk	The makefile for the C++ version of the Secure Simpapp sample application on the UNIX operating system. This file is used to manually build the C++ version of the Secure Simpapp sample application. Refer to the Readme.html file for information about manually building the C++ version of the Secure Simpapp sample application. The UNIX make command needs to be in the path of your machine.
makefiles.nt	The makefile for the C++ version of the Secure Simpapp sample application on the Windows NT operating system. This makefile can be used directly by the Visual C++ nmake command. This file is used to manually build the C++ version of the Secure Simpapp sample application. Refer to the Readme.html file for information about manually building the C++ version of the Secure Simpapp sample application. The Windows NT nmake command needs to be in the path of your machine.

Java Version of the Secure Simpapp Sample Application

The files for the Java version of the Secure Simpapp sample application are located in the following directories:

Windows NT

drive:\WLEdir \samples\corba\simpappSSL_java

UNIX

/usr/local/WLedir /samples/corba/simappSSL_java

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

Table 6-4 Files Included in the Java Version of the Secure Simpapp Sample Application

File	Description
Simple.idl	The OMG IDL code that declares the Simple and SimpleFactory interfaces.This file is copied from the WLE simpappSSL_java directory by the runme command file.
ServerImpl.java	The Java source code that overrides the Server.initialize and Server.release methods.
SimpleClient.java	The Java source code for the client application in the Secure Simpapp sample application.
SimpleFactoryImpl.java	The Java source code that implements the SimpleFactory methods.
SimpleImpl.java	The Java source code that implements the Simple methods.
Simple.xml	The Server Description File used to associate activation and transaction policy values with CORBA interfaces. For the Java version of the Secure Simpapp sample application, the Simple and SimpleFactory interfaces have an activation policy of method and a transaction policy of optional .
Readme.html	The file that provides the latest information about building and running the Java version of the Secure Simpapp sample application.
runme.cmd	The Windows NT batch file that builds and runs the Java version of the Secure Simpapp sample application.
runme.ksh	The UNIX Korn shell script that builds and executes the Java version of the Secure Simpapp sample application.
makefile.mk	The makefile for the Java version of the Secure Simpapp sample application on the UNIX operating system. This file is used to manually build the Secure Simpapp sample application. Refer to the Readme.html file for information about manually building the Secure Simpapp sample application. The UNIX make command needs to be in the path of your machine.
makefiles.nt	The makefile for the Secure Simpapp sample application on the Windows NT operating system. This file is used to manually build the Java version of the Secure Simpapp sample application. Refer to the Readme.html file for information about manually building the Secure Simpapp sample application. The Windows NT nmake command needs to be in the path of your machine.

Step 2: Change the protection attribute on the files for the Secure 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 Secure 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

Step 3: Verify the settings of the environment variables.

Before building and running the Secure 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 6-5 lists the environment variables required to run the Secure Simpapp sample application.

Table 6-5 Required Environment Variables for the Secure Simpapp Sample Application

Environment Variable	Description
APPDIR	The directory path where you copied the sample application files. For example: Windows NT APPDIR=c:\ work \simpappSSL UNIX APPDIR=/usr/ work /simpappSSL
TUXCONFIG	The directory path and name of the configuration file. For example: Windows NT TUXCONFIG=c:\work\simpappSSL\tuxconfig UNIX TUXCONFIG=/usr/ work /simpappSSL/tuxconfig
JDKDIR	The directory path where you installed the JDK software. For example: Windows NT JDKDIR=c:\jdk1.2.2 UNIX JDKDIR=/usr/local/jdk1.2.1 You need to specify this parameter only if you plan to use the Java version of the Secure Simpapp sample application.
TOBJADDR	The host name and port number of the IIOP Listener/Handler. The port number must be defined as a port for SSL communications. For example: Windows NT TOBJADDR=trixie::1111 UNIX TOBJADDR=trixie::1111
JAVA_HOME	The directory path where you installed the JDK software. For example: Windows NT JAVA_HOME=c:\JDK1.2 UNIX JAVA_HOME=/usr/local/JDK1.2 You need to define this environment variable only when you use the Java version of the Secure Simpapp sample application.
RESULTSDIR or JRESULTSDIR	A subdirectory of APPDIR where files that are created as a result of executing the runme command are stored. For example: Windows NT RESULTSDIR=c:\workdirectory\ UNIX RESULTSDIR=/usr/local/workdirectory/ When using the Java version of the Secure Simpapp sample application, specify the JRESULTSDIR environment variable.

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 of the environment variables.

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

Step 4: Execute 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 Secure Simpapp sample application manually. The steps for manually running the Secure Simpapp sample application are described in the Readme.html file.

To build and run the Secure 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 Secure Simpapp sample application runs and prints the following messages:

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

During execution of the runme command, you are prompted for a password. Enter the pass phrase of the private key of the IIOP Listener/Handler.

Table 6-6 lists the C++ files in the work directory generated by the runme command.

Table 6-6 C++ Files Generated by the runme Command

File	Description
Simple_c.cpp	Generated by the idl command, this file contains the client stubs for the SimpleFactory and Simple interfaces.
Simple_c.h	Generated by the idl command, this file contains the client definitions of the SimpleFactory and Simple interfaces.
Simple_s.cpp	Generated by the idl command, this file contains the server skeletons for the SimpleFactory and Simple interfaces.
Simple_s.h	Generated by the idl command, this file contains the server definition for the SimpleFactory and Simple interfaces.
.adm/.keybd	A file that contains the security encryption key database. The subdirectory is created by the tmloadcf command in the runme command.
results	A directory generated by the runme command.

Table 6-7 lists the Java files in the work directory generated by the runme command.

Table 6-7 Java Files Generated by the runme Command

File	Description
SimpleFactory.java	Generated by the m3idltojava command for the SimpleFactory interface. The SimpleFactory interface contains the Java version of the OMG IDL interface. It extends org.omg.CORBA.Object .
SimpleFactoryHolder.java	Generated by the m3idltojava command for the SimpleFactory interface.This class holds a public instance member of type SimpleFactory . The class provides operations for out and inout arguments that are included in CORBA, but that do not map exactly to Java.
SimpleFactoryHelper.java	Generated by the m3idltojava command for the SimpleFactory interface. This class provides auxiliary functionality, notably the narrow method.
_SimpleFactoryStub.java	Generated by the m3idltojava command for the SimpleFactory interface. This class is the client stub that implements the SimpleFactory.java interface.
_SimpleFactoryImplBase.java	Generated by the m3idltojava command for the SimpleFactory interface. This abstract class is the server skeleton. It implements the SimpleFactory.java interface. The user-written server class SimpleFactoryImpl extends _SimpleFactoryImplBase .
Simple.java	Generated by the m3idltojava command for the Simple interface. The Simple interface contains the Java version of the OMG IDL interface. It extends org.omg.CORBA.Object .
SimpleHolder.java	Generated by the m3idltojava command for the Simple interface.This class holds a public instance member of type Simple . The class provides operations for out and inout arguments that CORBA has but that do not match exactly to Java.
SimpleHelper.java	Generated by the m3idltojava command for the Simple interface. This class provides auxiliary functionality, notably the narrow method.
_SimpleStub.java	Generated by the m3idltojava command for the Simple interface. This class is the client stub that implements the Simple.java interface.
_SimpleImplBase.java	Generated by the m3idltojava command for the Simple interface. This abstract class is the server skeleton. It implements the Simple.java interface. The user-written server class SimpleImpl extends _SimpleImplBase .
Simple.ser	The Server Descriptor File generated by the buildjobjserver command in the runme command.
Simple.jar	The server Java Archive file generated by the buildjavaserver command in the runme command.
.adm/.keybd	A file that contains the security encryption key database. The subdirectory is created by the tmloadcf command in the runme command.
results	A directory generated by the runme command.

Table 6-8 lists files in the RESULTS or JRESULTS directory generated by the runme command.

Table 6-8 Files in the results Directory Generated by the runme Command

File	Description
input	Contains the input that the runme command provides to the Java client application.
output	Contains the output produced when the runme command executes the Java client application.
expected_output	Contains the output that is expected when the Java client application is executed by the runme command. The data in the output file is compared to the data in the expected_output file to determine whether or not the test passed or failed.
log	Contains the output generated by the runme command. If the runme command fails, check this file for errors.
setenv.cmd	Contains the commands to set the environment variables needed to build and run the Java Secure Simpapp sample application on the Windows NT operating system platform.
setenv.ksh	Contains the commands to set the environment variables needed to build and run the Java Secure Simpapp sample application on the UNIX operating system platform.
stderr	Generated by the tmboot command, which is executed by the runme command. If the -noredirect JavaServer option is specified in the UBBCONFIG file, the System.err.println method sends the output to the stderr file instead of to the ULOG file.
stdout	Generated by the tmboot command, which is executed by the runme command. If the -noredirect JavaServer option is specified in the UBBCONFIG file, the System.out.println method sends the output to the stdout file instead of to the ULOG file.
tmsysevt.dat	Contains filtering and notification rules used by the TMSYSEVT (system event reporting) process. This file is generated by the tmboot command in the runme command.
tuxconfig	A binary version of the UBBCONFIG file.
ubb	The UBBCONFIG file for the Java Secure Simpapp sample application.
ULOG.<date>	A log file that contains messages generated by the tmboot command.

Using the Secure Simpapp Sample Application

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

Windows NT

prompt>tmboot

UNIX

ksh prompt>tmboot

Run the client application in the Secure 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 Secure Simpapp sample client application uses the client-only JAR file m3envobj.jar . However, you can also use the m3.jar file to run the client application.

Before using another sample application, enter the following commands to stop the Secure 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