Skip Headers
Oracle® Fusion Middleware Installation Guide for Oracle Enterprise Repository
11g Release 1 (11.1.1.4.0)

Part Number E15745-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

1 Preparing for Your Installation

This chapter provides information that you must know before installing your Oracle software:

This chapter contains the following sections:

1.1 Installation 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 sections provide an overview about:

1.1.1 Installation Modes

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

1.1.1.1 Graphical Mode

Graphical-mode installation is an interactive, GUI-based method for installing your software. It can be run on both Windows and UNIX systems. For installation procedures, see Section 2.2.1, "Running the Installation Program in Graphical Mode".

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.2 Console Mode

Console-mode installation is an interactive, text-based method for installing your software from the command line, on either a UNIX system or a Windows system. For instructions for using this method, see Section 2.2.2, "Running the Installation Program in Console Mode".

1.1.1.3 Silent Mode

Silent-mode installation is a noninteractive 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.2 Oracle Enterprise Repository Sizing Guidelines

This section describes the Oracle Enterprise Repository sizing guidelines:

1.3 Installable Product Components

Using the Oracle Products installation program, you can install the following components on your system:

For additional information about:

1.3.1 Oracle 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:

    http://download.eclipse.org/webtools/updates/

    The following list describes the plug-ins available in Oracle Enterprise Repository:

    • Development Environments (IDEs)

      • Oracle JDeveloper

      • Eclipse

      • VS .NET

    • Service Registry

      • Oracle Service Registry

      • UDDI v3.0

    • Version Control Systems

      • Clear Case

      • CVS

      • PVCS

      • Harvest

      • Serena

    • Workflow Engine

      • Oracle BPM

    • Harvester Plug-ins for

      • WLST

      • Ant

      • Oracle Enterprise Manager Management Pack Plus for SOA

      • JDeveloper

      • Eclipse

    • Defect Tracking Systems

      • ClearQuest

1.4 Product Distribution Methods

Your Oracle software is distributed on the Oracle Web site.

1.4.1 Web Distribution

You can download your software from the Oracle Web site at http://www.oracle.com/technologies/soa/enterprise-repository.html.

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.

1.5 Installation Prerequisites

The following sections specify the installation prerequisites:

Note:

For more information about the Oracle Enterprise Repository sizing guidelines, see Section 1.2, "Oracle Enterprise Repository Sizing Guidelines".

1.5.1 System Requirements

The system requirements for your installation are given in the following table.

Table 1-1 System Requirements

Component Requirement

Platform configuration

A supported configuration of hardware, operating system, application server, JDK, and database is required. See Oracle Products Supported Configurations.

The Supported Configurations documentation specifies other prerequisites and recommendations, such as recommended versions of the JDK.

Processor

2-GHz CPU recommended

Hard Disk Drive

A complete installation requires approximately 1.2 GB of disk space.

Memory

A minimum of 2 GB RAM

Character Encoding

UTF-8/Unicode character encoding must be configured for your supported database and application server.

Color bit depth display and size

For graphical user interface (GUI) mode installation, 8-bit color depth (256 colors) is required.

For console-mode and silent-mode installation, there is no color bit depth requirement.

JDK

The Oracle Enterprise Repository installation program requires a Java run-time environment (JRE) to run.

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.2 Temporary 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 run-time 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.6 Database 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.

This section contains the following topics:

1.6.1 Oracle Database Installation

Appropriate administrative privileges are necessary to complete this process. This section contains the following topics:

1.6.1.1 Oracle Database

  1. Connect to the database as a DBA.

  2. 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.2 Prerequisites

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.

    For supported Oracle Enterprise Repository JDBC Drivers, see Table 2-1, "Oracle Enterprise Repository 11g Supported JDBC Driver Information".

    Note:

    The Oracle Database driver that you use should be based on your application servers JDK.
  • JDK 1.5.x or higher on the current workstation/server

  • SQL *Plus Client tools

1.6.1.3 Create the Tablespaces

Follow these steps to create the necessary tablespaces before installing Oracle Enterprise Repository:

  1. Log in to Oracle (system or DBA privileges are required).

  2. Create a data tablespace named OER_DATA with at least 300M of available space.

  3. Create an index tablespace named OER_INDEX with at least 300M of available space.

Example Tablespace Creation Script

The following example scripts show how to create the OER_DATA and OER_INDEX tablespaces.

Note:

These scripts are for a UNIX/Linux based DataFile. For Windows, a file path value of c:\oracle\...\file.dbf is appropriate syntax.
CREATE TABLESPACE OER_DATA
    DATAFILE '/opt/oracle/oradata/oer/oer_data.dbf' SIZE 300M
 AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
    EXTENT MANAGEMENT LOCAL AUTOALLOCATE
    LOGGING
    ONLINE
    SEGMENT SPACE MANAGEMENT AUTO;

CREATE TABLESPACE OER_LOB
    DATAFILE '/opt/oracle/oradata/oer/oer_lob.dbf' SIZE 300M
 AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
    EXTENT MANAGEMENT LOCAL AUTOALLOCATE
    LOGGING
    ONLINE
    SEGMENT SPACE MANAGEMENT AUTO;
CREATE TABLESPACE OER_INDEX
    DATAFILE '/opt/oracle/oradata/oer/oer_index.dbf' SIZE 300M
 AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
    EXTENT MANAGEMENT LOCAL AUTOALLOCATE
    LOGGING
    ONLINE
    SEGMENT SPACE MANAGEMENT AUTO;

1.6.1.4 Build a Database User

Follow these steps to create the necessary database user before installing Oracle Enterprise Repository:

  1. Log in to Oracle (administrative privileges required).

  2. Create a user and password.

  3. Ensure that the user has the following privileges:

    • Privilege to create sessions

    • Ability to create tables

    • Default tablespace is oer_data

    • Assigned quota of 300M for oer_data

    • Assigned quota of 300M for oer_lob

    • Assigned quota of 300M for oer_index

Example User Creation Script

The following example script show how to create a user for newly created Oracle Enterprise Repository Tablespaces.

CREATE USER OER IDENTIFIED BY OER_PWD
DEFAULT TABLESPACE OER_DATA
    TEMPORARY TABLESPACE TEMP;
GRANT CREATE MATERIALIZED VIEW TO OER;
GRANT CREATE SEQUENCE TO OER;
GRANT CREATE SESSION TO OER;
GRANT CREATE SYNONYM TO OER;
GRANT CREATE TABLE TO OER;
GRANT CREATE TRIGGER TO OER;
GRANT CREATE VIEW TO OER;
GRANT UNLIMITED TABLESPACE TO OER;

1.6.2 Oracle Real Application Clusters Database Installation

The Oracle Enterprise Repository 11g Release 1 (11.1.1.4.0) 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. Once 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:

db.url=jdbc:oracle:thin:@(DESCRIPTION = (load_balance = true) (failover =true) (ADDRESS = (PROTOCOL = TCP)(HOST = db_host1)(PORT = 1521)) (ADDRESS =(PROTOCOL = TCP)(HOST = db_host2)(PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = siprc)(failover_mode = (type = session) (method = basic) (retries = 0) (delay = 0))))

1.6.3 SQL Server 2008 Database Installation

Appropriate administrative privileges are necessary to complete this process. These instructions assume the use of Enterprise Manager. This section contains the following topics:

1.6.3.1 SQL Server 2008 Database

SQL Server is automatically configured to support UTF-8/Unicode character encoding. No additional configuration is necessary.

1.6.3.2 Prerequisites

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

  • A login with database administrator privileges (Usually the SA account).

  • The name of the supported JDBC driver for SQL Server 2008: sqljdbc.jar (driver version 1.1.1501.101)

1.6.3.3 Create a Database

Follow these steps to create the necessary database before installing Oracle Enterprise Repository:

  1. Open the SQL Server 2008 Management Studio.

  2. Right-click the Databases folder and select New Database.

  3. In the New Database window, enter Oracle Enterprise Repository as the database name.

  4. In the Database files section, change the Logical Name of Oracle Enterprise Repository to OER_DATA.

  5. Enter OER_USER as the database owner (or choose a Windows login account as appropriate for your security policy).

  6. Click Add to create a Filegroup, as follows:

    1. In Logical Name, enter OER_INDX.

    2. Click the Filegroup cell and select <new filegroup>.

    3. On the New Filegroup for Oracle Enterprise Repository page, enter INDEX for the name.

    4. Click OK.

  7. Click OK again to create the database.

1.6.3.4 Create a Database User

Follow these steps to create the necessary user before installing Oracle Enterprise Repository:

Note:

This step is only necessary if you are using SQL Server Authentication for the Oracle Enterprise Repository application installation.
  1. Open the SQL Server 2008 Management Studio.

  2. Expand the Server tree to open the Security folder.

  3. Right-click Logins and select New Login.

  4. Enter OER_USER as the Login name (or choose a Windows login account as appropriate for your security policy).

  5. Select SQL Server Authentication.

  6. Enter a password that meets your password policy into the Password and Confirm password fields.

  7. Change the default database to Oracle Enterprise Repository.

  8. Select a page list, select User Mappings, and then in the Map column select the Oracle Enterprise Repository database option.

  9. Grant database roles for public and db_owner.

  10. Click OK to create the user account.

1.6.4 UDB Database Installation

Appropriate administrative privileges are necessary to complete this process. This section contains the following topics:

1.6.4.1 UDB Database

  1. Connect to the database as a DBA.

  2. From a DB2 shell command prompt, run the following:

    > get db cfg

    The output should include the line Database code set = UTF-8. If this line does not appear, it is necessary to create a UTF-8 database.

1.6.4.2 Prerequisites

You must ensure a successful login to the database using the administrator privileges, before beginning the Oracle Enterprise Repository installation process.

1.6.4.3 Create a Database

To create the required database before installing Oracle Enterprise Repository, perform the following steps:

  1. Open the DB2 Command Editor.

  2. Run db2 -tv to start the DB2 shell command prompt with semicolon command termination.

  3. Create a database named OER that includes bufferpools and tablespaces.

    1. Name the bufferpools as: OER32kDataBP, OER32kIndxBP, OER32kBlobBP, and OER32kTempBP.

    2. Create three large tablespaces named: OERDataTS, OERIndxTS, and OERLobTS with at least 300M of available space.

    3. Create one temporary tablespace named: OERTempTS with at least 100M of available space.

    Note:

    The tablespace names OERDataTS, OERIndxTS, and OERLobTS are necessary for the Oracle Enterprise Repository installation process.

    Example 1-1 Example Database Create Script

    CREATE DATABASE OER USING CODESET UTF-8 TERRITORY US;
    -- Connect to the OER database
    -- Replace <user> and <password> with the user who would own the OER schema.
    CONNECT TO OER USER <user> USING <password>;
    -- Create the OER 32K Buffer Pools
    CREATE BUFFERPOOL OER32KDATAbp SIZE 1000 PAGESIZE 32K;
    CREATE BUFFERPOOL OER32KINDXbp SIZE 1000 PAGESIZE 32K;
    CREATE BUFFERPOOL OER32KBLOBbp SIZE 1000 PAGESIZE 32K;
    CREATE BUFFERPOOL OER32KTEMPbp SIZE 1000 PAGESIZE 32K;
    CONNECT RESET;
    -- Same <user> and <password> replacements as before are required.
    CONNECT TO OER USER <user> USING <password>;
    CREATE LARGE TABLESPACE oerdatats PAGESIZE 32 K MANAGED BY DATABASE USING(file
     '/opt/IBM/DB2/data/oerdatats.dat' 300M) extentsize 512k BUFFERPOOL OER32KDATAbp;
    CREATE LARGE TABLESPACE oerindxts PAGESIZE 32 K MANAGED BY DATABASE USING(file
     '/opt/IBM/DB2/data/oerindxts.dat' 300M) extentsize 512k BUFFERPOOL OER32KINDXbp;
    CREATE LARGE TABLESPACE oerlobts  PAGESIZE 32 K MANAGED BY DATABASE USING(file
     '/opt/IBM/DB2/data/oerlobts.dat' 300M) extentsize 512k BUFFERPOOL OER32kBLOBbp;
    -- Create the OER Temp Tablespace
    CREATE TEMPORARY TABLESPACE oertempts PAGESIZE 32 K MANAGED BY DATABASE
     USING(file '/opt/IBM/DB2/data/oertempts.dat' 128M) BUFFERPOOL OER32KTEMPbp;
    

1.6.4.4 Tune the Database

To configure the tuning parameters, perform the following steps in the Configuration Advisor Wizard:

  1. In the DB2 Control Center, click Tools, Wizards, and then select Configuration Advisor. The Configuration Advisor Wizard - Introduction page is displayed.

  2. Select the new Oracle Enterprise Repository database, and click Next. The Configuration Advisor Wizard - Server page is displayed.

  3. Select a percentage of memory to allocate to the Oracle Enterprise Repository database in DB2, and then click Next. The Configuration Advisor Wizard - Workload page is displayed.

  4. Select the Mixed option in the Optimize for Workload Type list, and then click Next. The Configuration Advisor Wizard - Transactions page is displayed.

  5. Select the More than 10(long transactions) option in the Average Number of SQL Statements Per Unit of Work list. Take the default number of transactions per minute.

  6. Click Next. The Configuration Advisor Wizard - Priority page is displayed.

  7. Select a database administration priority. The default option is Both.

  8. Click Next. The Configuration Advisor Wizard - Populated page is displayed.

  9. Select No, as the database is not yet populated with data. Then, click Next. The Configuration Advisor Wizard - Connections page is displayed.

    Note:

    On all future visits to this wizard for the Oracle Enterprise Repository database, select the answer as "Yes".
  10. Select 0 local and 25 remote as the average number of connected applications, and then click Next. The Configuration Advisor Wizard - Isolation page is displayed.

  11. Select the Cursor Stability (many locks of short duration) option, and then click Next. The Configuration Advisor Wizard - Results page is displayed.

  12. Accept the suggested modifications, and click Finish to apply changes to your database.

Note:

Since many tuning parameters are data dependent, this Wizard can be re-run following the load of significant amounts of data, or after a designated period, for example, monthly or quarterly.

1.7 Selecting Directories for Your Installation

During the installation process, you must specify locations for the following directories:

1.7.1 Choosing 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 a 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.2 Choosing 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.8 Running the Oracle Enterprise Repository Product Installation

This section describes the steps to run the Oracle Enterprise Repository product installation:

  1. 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.

  2. 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.

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

    java -jar OER1111xx_generic.jar

1.9 Generating 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:

$JAVA_HOME/bin/java -jar OER1111xx_generic.jar -log=c:\logs\OER_install.log

where JAVA_HOME represents the path the users java.

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.

Note:

For information about upgrading your software, see the Oracle Fusion Middleware Upgrade Guide for Oracle Enterprise Repository.