Files for the Application Server

 

When you install WebLogic Server and WebLogic Portal, the installation programs set up a fully configured application server, sample applications and supporting EJBs, and other files that you use as a reference point for developing your enterprise application.

These reference resources are appropriate for installing in a development environment. In a production environment, if you do not want to use all of the files as they are organized by the installation programs, refer to the sections of this topic:

• Required Files and Directories

• Recommended Files and Directories

• Support for Developing Applications

 

---

Required Files and Directories

You must make the files and directories listed in Listing 2-1 available to any environment in which you want to run a WebLogic Portal application server.

Table 2-1 Required Files and Directories

Required Component	Description
The BEA_HOME directory	Named bea by default. For information about the files in the BEA_HOME directory, refer to "Preparing to Install WebLogic Server" in the WebLogic Server Installation guide. You must specify the name and location of BEA_HOME when you start the application server. For more information, refer to Starting and Shutting Down a Server.
The JDK	By default, the WebLogic Server installer includes the required JDK version. For information on the required version, refer to "Supported Platforms" in the Installation Guide.
The BEA_HOME/wlserver6.1 directory	Contains files and directories for running the application server. The WebLogic Server installer includes an option for installing only required files.
PORTAL_HOME/lib	Provides JARs that extend WebLogic Server with WebLogic Portal features. Some of the JARs in this directory must be named in the CLASSPATH environment variable. (For more information, refer to Add Directories to CLASSPATH.) Do not modify any of these files and directories.
PORTAL_HOME/ weblogiccommerce.properties	A file that configures domains and servers (in addition to standard J2EE deployment descriptors). It is deprecated along with the sections of Java code that it configures.

 

---

Recommended Files and Directories

Listing 2-2 lists files and directories that are not required. However we recommend that you include them in an environment to facilitate installing service packs, upgrading, and starting and stopping a server instance.

Table 2-2 Recommended Files and Directories

Recommended Component	Description
BEA_HOME/registry.xml	Contains a persistent record of all BEA products installed on the target system. This registry contains product-related information, such as version level, Service Pack level, and installation directory. It facilitates the installation of Service Packs and upgrades.
BEA_HOME/utils/*	Contains utilities that are used to support the installation of all BEA WebLogic Server products. The utils.jar file contains code that supports the UpdateLicense utility. It facilitates the installation of Service Packs and upgrades.
PORTAL_HOME/ StartPortal and StopPortal, or their equivalents	Scripts that start and stop WebLogic Portal domains. For more information, refer to Starting and Shutting Down a Server.
PORTAL_HOME/bin/ set-environment.bat (or.sh)	A script that sets all environment variables required for the run-time environment. For more information, see Setting Environment Variables.
PORTAL_HOME/ uninstaller	A directory that contains files for uninstalling WebLogic Portal.

 

---

Support for Developing Applications

WebLogic Portal installs the files and directories in Listing 2-3 to support your development efforts. You do not need to deploy them in a production environment.

Table 2-3 Files and Directories that Support Development

Development Component	Description
PORTAL_HOME/config	The domain repository (parent directory) for the sample WebLogic Portal domains. The config directory that the installer creates is for development purposes. Your production environment must include a config directory, but it does not need to contain the sample domains, and it does not need to be located below PORTAL_HOME. For more information, see Deploying Domains and Server Configurations.
PORTAL_HOME/applications	A directory that contains sample enterprise applications. You can deploy your enterprise applications in this or other directories. For more information, refer to Assembling and Deploying Enterprise Applications.
PORTAL_HOME/bin	A directory that contains platform-specific scripts for setting up your environment.
PORTAL_HOME/db	A directory that contains the Cloudscape database.Use this database for demonstration purposes only. To see a list of databases that we support for development and production, refer to Supported Platforms in the Installation Guide. This directory also contains scripts for creating and migrating schemas for development and production databases, and for loading those databases with sample data. You might need to modify some of these scripts, depending on your environment. We recommend that you make a backup copy of the entire directory tree or place it under source control before you modify it.
PORTAL_HOME/dmsBase	Directories that contain content to support the sample enterprise applications.