This chapter provides information about how to install Oracle Enterprise Repository.
This chapter includes the following sections:
Section 1.2, "Oracle Enterprise Repository Sizing Guidelines"
Section 1.8, "Running the Oracle Enterprise Repository Product Installation"
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.
You can use the Oracle Products installation program in one of the following modes:
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.
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".
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".
This section describes the Oracle 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.
Treat virtualized environments just like actual hardware when sizing your environment.
Minimum Configuration
32 -bit architecture
Application Server
Supported Platforms
For the list of Oracle Enterprise Repository supported platforms, see http://www.oracle.com/technology/products/soa/repository/index.html
.
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.
Initial RAM size for application server: 1GB
Initial Disk Space usage for application server: 2GB (Including Eclipse)
Minimum CPU Speeds: 1.8Ghz (Recommended 2.4Ghz Dual Core processors)
Minimum Network Speeds connecting Application Server and Database Server: 100Mbit (Recommended 1Gbit)
Large Configuration
64-bit architecture
Multiple CPU cluster
Isolated development and test environments
Typical Database Configuration
Using Oracle 11g
20MB for Data (including blob data)
20MB for Index
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.
A properly configured database server has enough drives to optimize disk usage. Oracle's performance testing database server for Oracle Enterprise Repository has 6 drives.
Note:
Oracle Enterprise Repository has not been tested with HA databases.
The Oracle Enterprise Repository design is one of the most important performance components and the following can impact performance:
Number of assets (Oracle Enterprise Repository is easily capable of storing hundreds of thousands of assets. There are however some limitations with the GUI.)
Number of asset types
Nested taxonomies (Complexity of the taxonomy can have a huge impact on performance, not to mention decrease the usability for asset consumers)
Number of relationships
Number of active users
Using the Oracle Products installation program, you can install the following components on your system:
For additional information about:
The features and capabilities of Oracle Enterprise Repository, see Section 1.3.1, "Oracle Enterprise Repository".
Operating systems and hardware supported by your software, see Oracle Product Supported Configurations.
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
Your Oracle software is distributed on the Oracle web site.
You can download your software from the Oracle web site at
http://www.oracle.com/technetwork/middleware/repository/downloads/index.html?ssSourceSiteId=ocomen
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.
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".
The system requirements for your installation are given in the following table.
Component | Requirement |
---|---|
Platform configuration |
A supported configuration of hardware, operating system, application server, JDK, and database is required. See Oracle Product 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 Runtime 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. |
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:
|
UNIX |
Enter the following option on the command line when you start the installation program:
Here, |
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:
Appropriate administrative privileges are necessary to complete this process. This section contains the following topics:
Connect to the database as a DBA.
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)
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
To create the necessary tablespaces before installing Oracle Enterprise Repository:
Log in to Oracle (system or DBA privileges are required).
Create a data tablespace named OER_DATA
with at least 300M of available space.
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;
To create the necessary database user before installing Oracle Enterprise Repository:
Log in to Oracle (administrative privileges required).
Create a user and password.
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
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;
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:
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))))
Appropriate administrative privileges are necessary to complete this process. These instructions assume the use of Enterprise Manager. This section contains the following topics:
SQL Server is automatically configured to support UTF-8/Unicode character encoding. No additional configuration is necessary.
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)
To create the necessary database before installing Oracle Enterprise Repository:
Open the SQL Server 2008 Management Studio.
Right-click the Databases folder and select New Database.
In the New Database window, enter Oracle Enterprise Repository as the database name.
In the Database files section, change the Logical Name of Oracle Enterprise Repository to OER_DATA
.
Enter OER_USER
as the database owner (or choose a Windows login account as appropriate for your security policy).
Click Add to create a Filegroup, as follows:
In Logical Name, enter OER_INDX
.
Click the Filegroup cell and select <new filegroup>
.
On the New Filegroup for Oracle Enterprise Repository page, enter INDEX
for the name.
Click OK.
Click OK again to create the database.
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.
Open the SQL Server 2008 Management Studio.
Expand the Server tree to open the Security folder.
Right-click Logins and select New Login.
Enter OER_USER
as the Login name (or choose a Windows login account as appropriate for your security policy).
Select SQL Server Authentication.
Enter a password that meets your password policy into the Password and Confirm password fields.
Change the default database to Oracle Enterprise Repository.
Select a page list, select User Mappings, and then in the Map column select the Oracle Enterprise Repository database option.
Grant database roles for public and db_owner.
Click OK to create the user account.
Appropriate administrative privileges are necessary to complete this process. This section contains the following topics:
Connect to the database as a DBA.
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.
You must ensure a successful login to the database using the administrator privileges, before beginning the Oracle Enterprise Repository installation process.
To create the required database before installing Oracle Enterprise Repository:
Open the DB2 Command Editor.
Run db2 -tv
to start the DB2 shell command prompt with semicolon command termination.
Create a database named OER that includes bufferpools and tablespaces.
Name the bufferpools as: OER32kDataBP, OER32kIndxBP, OER32kBlobBP, and OER32kTempBP.
Create three large tablespaces named: OERDataTS, OERIndxTS, and OERLobTS with at least 300M of available space.
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;
To configure the tuning parameters, perform the following steps in the Configuration Advisor Wizard:
In the DB2 Control Center, click Tools, Wizards, and then select Configuration Advisor. The Configuration Advisor Wizard - Introduction page is displayed.
Select the new Oracle Enterprise Repository database, and click Next. The Configuration Advisor Wizard - Server page is displayed.
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.
Select the Mixed option in the Optimize for Workload Type list, and then click Next. The Configuration Advisor Wizard - Transactions page is displayed.
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.
Click Next. The Configuration Advisor Wizard - Priority page is displayed.
Select a database administration priority. The default option is Both.
Click Next. The Configuration Advisor Wizard - Populated page is displayed.
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".
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.
Select the Cursor Stability (many locks of short duration) option, and then click Next. The Configuration Advisor Wizard - Results page is displayed.
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.
During the installation process, you must specify locations for the following directories:
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:
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.
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.
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
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.
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 Oracle Fusion Middleware Upgrade Guide for Oracle Enterprise Repository.