Setting Up Your Environment

This chapter describes how to configure up your WebLogic Enterprise (WLE) application so that you can run the University sample applications. This chapter includes the following sections:

• Software prerequisites

• Editing the setenv and UBBCONFIG files

A copy of the Readme.txt file with troubleshooting information and the latest information about setting up the sample applications is included in each sample application directory.

For information about setting up a database so that it can be used with the University sample applications, see Appendix A, "Setting Up the Database."

System Prerequisites

For information about the operating system platforms supported by the product, see Installing the WebLogic Enterprise Software.

To run the client applications in the University sample applications, you need the following development tools:

• Visual C++ Version 5.0 with Service Pack 3

• If you want to run the ActiveX client application, Visual Basic Version 5.0 with Service Pack 3

• If you want to run the CORBA Java client application, Java Development Kit (JDK) Version 1.1.6 or greater or JDK Version 1.2.

  • The UNIX platforms supported by Version 4.2 of the WLE software use the JDK Version 1.1.6 or greater.

  • The Windows NT platforms supported by Version 4.2 of the WLE software use the JDK Version 1.2.

Editing the setenv and UBBCONFIG Files

You need to set several parameters in the setenv and UBBCONFIG files in order for the University sample applications to work properly, as follows:

• The setenv file sets the system environment variables needed to build and run the sample applications. Each sample application directory contains a unique setenv file. The name of the setenv file designates which sample application the file is to be used with. For example, setenvb is for the Basic sample application. Each sample application directory contains a setenv file for the Windows NT and UNIX operating systems. For a list of the specific file names for the setenv file, see Table 2-1.

• The UBBCONFIG file is the configuration file for the sample application. The UBBCONFIG file defines parameters for how the client and server applications in the sample application should work. Each sample application directory contains a unique UBBCONFIG file. The name of the UBBCONFIG file designates which sample application the file is to be used with. For example, ubb_b is for the Basic sample application. Each sample application directory contains a UBBCONFIG file for the Windows NT and UNIX operating systems. For a list of the specific file names for the UBBCONFIG file, see Table 2-1.

The information in the setenv and UBBCONFIG files must match. The following sections explain how to edit the setenv and UBBCONFIG files.

Naming Conventions for the setenv and UBBCONFIG Files

Table 2-1 describes the naming conventions for the setenv and UBBCONFIG files.

Table 2-1 Naming Conventions for setenv and UBBCONFIG Files

Setting setenv Parameters

Table 2-2 lists the parameters you need to modify in the setenv file.

Setting the UBBCONFIG Parameters

Table 2-3 lists the parameters you need to modify in the UBBCONFIG file.

Running the setenv Command

Before you can use the University sample applications, you need to run the setenv script to ensure your system environment variables reflect all the changes made in the process of setting up the Oracle database and your configuration. Instructions for running the setenv command are included in the descriptions of building the individual sample applications.

Note: The makefiles for the University sample applications assume Microsoft Visual C++ is installed in the following location on Windows NT: c:\Progra~1\Devstu~1\VC

If your copy of Microsoft Visual C++ is not installed in that directory, run the following command procedure to set the appropriate system environment variables.

c:\Progra~1\Devstu~1\VC\Bin\VCVARS32.bat

The Oracle Pro*C/C++ compiler uses short names so you need to use ~ in the directory path to ensure the system variable is set correctly.