1.1Installation Overview

The installation program provides a complete framework for the installation and uninstallation of your entire Oracle software product, or individual components, as desired. You can install Oracle Enterprise Repository using the default option, which enables you to install Oracle Enterprise Repository and its examples.

The following section provides an overview of the modes available in the Oracle Products installation program.

1.1.1Installation Modes

You can use the Oracle Products installation program in one of the following modes:

If you want to run graphical-mode installation, the console attached to the computer on which you are installing the software must support a Java-based GUI. All consoles for Windows systems support Java-based GUIs, but not all consoles for UNIX systems do.

Note:

If you attempt to start the installation program in graphical mode on a system that cannot support a graphical display, the installation program automatically starts console-mode installation.

1.1.1.3Silent Mode

Silent-mode installation is a non-interactive method of installing your software that requires the use of an XML properties file for selecting installation options. You can run silent-mode installation in either of two ways: as part of a script or from the command line. Silent-mode installation is a way of setting installation configurations only once and then using those configurations to duplicate the installation on many computers. For information on running the installation program in the silent mode, see Section 2.2.3, "Running the Installation Program in Silent Mode".

1.2Oracle Enterprise Repository Sizing Guidelines

Oracle Enterprise Repository offers greatest capacity on a 64-bit architecture. Oracle Enterprise Repository is essentially a single Java process. With a 32 -bit architecture any process is limited to 4GB (a little less on Windows), regardless of how much memory is in the system. With a 64-bit architecture the processes are limited to the amount of memory in the system and the JDK is more tunable. This enables you to make much larger amounts of memory available to the application server, which includes the cache that the assets load into.

Minimum 2GB RAM available for application server usage (dependent on the number of assets expected within the Oracle Enterprise Repository). Creating large numbers of assets and complex taxonomies consumes memory.

Rule of thumb on DB drive size is 10 X physical table and index size for 100K tables and index at 1.1GB so figure 10 or 11 GB for DB drive space. This varies based on how the DBAs have configured the drives.

1.3.1Oracle Enterprise Repository

Oracle Enterprise Repository manages the metadata for any type of software asset, from business processes and web services to patterns, frameworks, applications, and components. It maps the relationships and interdependencies that connect those assets to improve impact analysis, promote and optimize their reuse, and measure their impact on the bottom line.

Oracle Enterprise Repository consists of the following subcomponents that can be installed on your system:

Core Repository with Examples: Installs everything necessary for Oracle Enterprise Repository. The evaluation customers should choose just this option.

Oracle Enterprise Repository Plug-in for Eclipse: This plug-in allows access to the repository from Eclipse. The Repository Access View supports browsing, searching, and retrieval of assets from Oracle Enterprise Repository.

Oracle Enterprise Repository Plug-ins

The Oracle Enterprise Repository plug-in depends upon the OEPE plug-in for Eclipse. The OEPE plug-in depends on the Eclipse WST project, therefore making WST a transitive dependency for Oracle Enterprise Repository. You can retrieve the WST project from the following location:

1.4.1Web Distribution

In the Downloads panel, click Oracle Enterprise Repository to go to the Oracle Enterprise Repository Downloads page. From the list of operating systems, choose the appropriate operating system to download the installer to your local computer.

Note:

You must accept the license agreement, before you download the installer.

To run the .jar installation programs, you must have the appropriate version of the JDK installed on your system, and include the bin directory of the JDK at the beginning of the PATH variable definition. It is important that you use a JDK because the installation process assigns values to JAVA_HOME and related variables to point to the JDK directory.

JDBC

The Oracle Enterprise Repository installation program requires the location of supported JDBC driver file(s) to communicate with a supported database server.

Ensure that the JDBC driver file(s) are compatible with your application server's JDK/JRE version, before proceeding with the Oracle Enterprise Repository installation.

When using the IBM WebSphere application server, the bundled JDK/JRE does not support JDBC drivers that are compiled using a newer JDK. For example, the Oracle 11g JDBC driver, ojdbc6.jar, does not function within a WebSphere 6.1.0.5 installation, however, the ojdbc5.jar driver would be appropriate.

1.5.2Temporary Disk Space Requirements

The Oracle installation program uses a temporary directory into which it extracts the files necessary to install the software on the target system. During the installation process, your temporary directory must contain sufficient space to accommodate the compressed Java Runtime Environment (JRE) bundled with the installation program and an uncompressed copy of the JRE that is expanded into the temporary directory. The extracted files are deleted from the temporary directory after the installation process. As a general rule, installation programs require approximately 2.5 times the amount of temporary space that is ultimately required by the installed files.

By default, the installation program uses the following temporary directories:

Windows platforms: directory referenced by the TMP system variable

UNIX platforms: system-dependent temporary directory

Note:

If you do not have enough temporary space to run the installation program, you are prompted to specify an alternate directory or exit the installation program.

To ensure that you have adequate temporary space, you may want to allocate an alternate directory for this purpose. To do so, follow the instructions provided in the following table.

Platform

To allocate more space in the temp folder

Windows

Do one of the following:

Set the TMP system variable to a directory of your choice.

If starting the installation program from the command line, include the -Djava.io.tmpdir=tmpdirpath option, replacing tmpdirpath with the full path of the directory that you want to designate as a temporary storage area for the Oracle Enterprise Repository installation program. For example:

java -jar OER1111xx_generic.jar -Djava.io.tmpdir=D:\Temp

UNIX

Enter the following option on the command line when you start the installation program:

java -jar OER1111xx_generic.jar -Djava.io.tmpdir=tmpdirpath

Here, tmpdirpath is the full path of the directory that you want to designate as a temporary storage area for the Oracle Enterprise Repository installation program.

1.6Database Installation Procedures

The database administrator must create an empty database for Oracle Enterprise Repository to install its files into. A user for this database must also be created (for example, OER_USER) and that user must have database owner privileges on the Oracle Enterprise Repository database.

1.6.1.1Oracle Database

From a SQL Plus command prompt, run: select * from nls_database_parameters where Parameter='NLS_CHARACTERSET';

The output has two columns, Parameter and Value. The most common Values are:

UTF-8 Encoding: AL32UTF8 (International support)

ISO-8859-1 Encoding: WE8ISO8859P1 (U.S. English Encoding)

1.6.1.2Prerequisites

You must verify the following database prerequisites before beginning the Oracle Enterprise Repository installation process.

A login with database administrator privileges

The name of the supported JDBC driver for Oracle: You could use either ojdbc5.jar or ojdbc6.jar depending on the JDK used by your application server. The supported Oracle Database versions are - 10.2.0.4.0, 11.1.0.7.0, and 11.2.

1.6.2Oracle Real Application Clusters Database Installation

The Oracle Enterprise Repository 11g Release 1 (11.1.1.7) Installer does not support the installation into Oracle Real Application Cluster (Oracle RAC) environments, but supports Oracle RAC postinstall configurations. The Oracle Enterprise Repository installer requires a standard SID to connect and create relations, and also to insert the sample data for use with the initial installation of Oracle Enterprise Repository.

The Oracle Database administrators should assist in the database configuration of Oracle Enterprise Repository when the migration from SID to an Oracle RAC environment is required. After the Oracle RAC environment is configured and verified by the Oracle Database administrator, then the database.properties file in the Oracle Enterprise Repository application contains the appropriate values for the db.url property, as mentioned in the following example:

1.7Selecting Directories for Your Installation

1.7.1Choosing an Oracle Home Directory

During the installation of the Oracle software, you are prompted to specify an Oracle home directory. This directory serves as a repository for common files that are used by various Oracle products installed on the same computer. For this reason, the Oracle home directory can be considered a central support directory for all the Oracle products installed on your system.

The files in the Oracle home directory are essential to ensuring that Oracle software operates correctly on your system. These files:

Facilitate checking of cross-product dependencies during installation

Facilitate Service Pack installation

The default Oracle home directory where these files are installed is:

$ORACLE_HOME/repository111

All files related to the application installation are found under this Oracle home directory. In the case of a WebLogic Server installation, the application domain template file is found in the $ORACLE_HOME/wl_server11.x/templates/applications directory.

Note:

On some UNIX platforms, the installation program does not install the JDK. During installation of your Oracle software, you are prompted to choose an existing Oracle home directory or specify a path to create an Oracle home directory. If you choose to create a directory, the installation program automatically creates it for you.

Oracle recommends that you do not exceed a maximum of 12 characters when naming your Oracle home directory. If the name of this directory has more than 12 characters, or if there are spaces in the directory name, the CLASSPATH may not be resolved properly. You can install only one instance of each version of an Oracle product in a single Oracle home directory.

If the Oracle home directory is populated and it does not contain registry.xml, or if any of the other installation directories are not empty, the following messages are displayed. You are then prompted to continue installation, or return to the directory selection task with the one of the error message as shown in Listing 2-1:

Listing 2-1

For Oracle home directory selection task: Oracle_HOME directory is not empty. Proceed with installation?

For product installation directories selection task:One or more installation directories are not empty. Proceed with installation?

The product maintenance level of the current installer must be compatible with the maintenance level of the product already installed. If not, an error message is displayed and you must obtain the compatible installer or perform maintenance to achieve compatibility.

1.7.2Choosing Product Installation Directory

The product installation directory contains all the software components that you choose to install on your system, including program files and examples. You are prompted during your initial installation to choose a product installation directory. If you accept the default on a Windows system, for example, your software is installed in the following directory:

<ORACLE_HOME>/repositoryXXX

where, ORACLE_HOME is the Oracle home directory and repositoryXXX is the product installation directory for the Oracle Enterprise Repository software. However, you can specify any name and location on your system for your product installation directory; you need not name the directory repositoryXXX or create it under the Oracle home directory.

1.8Running the Oracle Enterprise Repository Product Installation

To run the Oracle Enterprise Repository product installation:

If you are planning to use a Generic Application Server (Tomcat, JBoss, Jetty.), then a supported JDK is required to be installed before the installation of Oracle Enterprise Repository.

Use of the JDK that is installed with WebSphere or WebLogic Server as your JAVA_HOME environment variable and the JAVA_HOME/bin directory being prepended to your PATH environment variable.

Run the following command-line option to start the Oracle Enterprise Repository installer:

java -jar OER1111xx_generic.jar

1.9Generating a Verbose Installation Log

If you launch the installation from the command line or from a script, you can specify the -log option to generate a verbose installation log. The installation log stores messages about events that occur during the installation process, including informational, warning, error, and irrecoverable messages. This type of file can be especially useful for silent installations.

Note:

You may see some warning messages in the installation log. However, unless a irrecoverable error occurs, the installation program completes the installation successfully. The installation user interface indicates the success or failure of each installation attempt, and the installation log file includes an entry indicating that the installation was successful.

Syntax

To create a verbose log file during installation, include the -log=full_path_to_log_file option in the command line. For example:

The path must specify a file. You cannot create a folder simply by including a name for it in a path name; your path should specify only existing folders. If your path includes a nonexistent folder when you execute the command, the installation program does not create the log file.