Preparing for Your Installation 1-3
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.
■
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
1.3 Installable Product Components
Using the Oracle Products installation program, you can install the following components on your system:
■
Section 1.3.1, Oracle Enterprise Repository 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 Products Supported Configurations.
Note: Oracle Enterprise Repository has not been tested with HA
databases.
1-4 Oracle Fusion Middleware Installation Guide for Oracle Enterprise Repository
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.orgwebtoolsupdates 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
