ORACLE SOA System Requirements

1

Oracle® Fusion MiddlewareSystem Requirements and Specifications

11g Release 1 (11.1.1)

E18558-01

April 2012

This document contains system and platform-specific information for Oracle Fusion Middleware products.

The following topics are covered in this document:

■ Section 1, "New Product Names in 11g Release 1 (11.1.1.6.0)"

■ Section 2, "Finding Oracle Fusion Middleware Certification Information"

■ Section 3, "Understanding the 32-Bit and 64-Bit Oracle Fusion Middleware Environment"

■ Section 4, "Oracle Fusion Middleware Memory and Space Requirements"

■ Section 5, "Oracle Fusion Middleware System Configuration Requirements"

■ Section 6, "Oracle Universal Installer (OUI) Requirements"

■ Section 7, "System Requirements for UNIX Operating Systems"

■ Section 8, "System Requirements for Windows Operating Systems"

■ Section 9, "Oracle WebLogic Server Information"

■ Section 10, "Certified Databases"

■ Section 11, "Repository Creation Utility (RCU) Requirements"

■ Section 12, "Documentation Accessibility"

1 New Product Names in 11g Release 1 (11.1.1.6.0)Starting with Oracle Fusion Middleware 11g Release 1 (11.1.1.6.0), Oracle WebCenter and Oracle Enterprise Content Management Suite have been rebranded. Refer to "New Product Names for Oracle WebCenter and Oracle Enterprise Content Management Suite" in Oracle Fusion Middleware Patching Guide for details.

2 Finding Oracle Fusion Middleware Certification InformationIf you are looking for latest certification information for current and previous releases, go to the Oracle Fusion Middleware Supported System Configurations page:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

The System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document contains certification information related to supported 32-bit and 64-bit



2

operating systems, databases, web servers, LDAP servers, adapters, IPv6, JDKs, and third-party products.

If you use My Oracle Support, you can also refer to "My Oracle Support Certification Tool for Oracle Fusion Middleware Products" (Doc ID 1368736.1) for certification information.

3 Understanding the 32-Bit and 64-Bit Oracle Fusion Middleware EnvironmentThis section contains the following:

■ Section 3.1, "Oracle Fusion Middleware Support for 64-Bit JDKs"

■ Section 3.2, "Oracle Fusion Middleware Support for 32-Bit Products on 64-Bit Operating Systems"

3.1 Oracle Fusion Middleware Support for 64-Bit JDKsThe Oracle WebLogic Server requires a Java run-time environment (JRE) to run. When you install Oracle WebLogic Server, a JRE is bundled in the Windows 32-bit and Linux x86 installation programs, as well as in some UNIX installation programs (those with file names ending in .bin).

For other platforms, the installation program does not install a JDK (file names for these installation programs end in .jar). 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.

If your Oracle Fusion Middleware components are running in a 64-bit JVM environment, ensure that WebLogic Server is installed with the 64-bit JDK or is using a supported 64-bit JDK on your system. You cannot mix components using a 32-bit JVM with those using a 64-bit JVM.

3.2 Oracle Fusion Middleware Support for 32-Bit Products on 64-Bit Operating SystemsRefer to the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 on the Oracle Fusion Middleware Supported System Configurations page for details about installing a 32-bit product on a 64-bit operating system. A link to this document is provided in Section 2, "Finding Oracle Fusion Middleware Certification Information".

For those products that support installing the 32-bit version on a 64-bit operating system, there may be special considerations for starting the product installer. For more information, see Section 6.3, "Running the 32-Bit Installer on 64-Bit Operating System".

4 Oracle Fusion Middleware Memory and Space RequirementsThis section contains the minimum memory and disk space requirements for Oracle Fusion Middleware products. The following topics are covered:

■ Section 4.1, "General Memory Requirements"

■ Section 4.2, "Oracle Web Tier Disk Space Requirements"

■ Section 4.3, "Oracle SOA and Oracle BAM Requirements"

3

■ Section 4.4, "Oracle Portal, Forms, Reports and Discoverer Requirements"

■ Section 4.5, "Oracle Identity Management Memory and Disk Space Requirements"

■ Section 4.6, "Oracle Business Intelligence Requirements"

■ Section 4.7, "Oracle Data Integrator Requirements"

■ Section 4.8, "Oracle Data Profiling and Data Quality Requirements"

4.1 General Memory RequirementsUnless otherwise noted, Table 1 lists the general minimum memory requirements for Oracle Fusion Middleware products. For the purposes of this document, "minimum available memory" is defined as the amount of physical memory (RAM) and swap memory combined.

4.2 Oracle Web Tier Disk Space RequirementsOracle Web Tier requires a minimum of 2400 MB of free disk space.

4.3 Oracle SOA and Oracle BAM RequirementsThis section contains the following:

■ Section 4.3.1, "Oracle SOA and Oracle BAM System Requirements"

■ Section 4.3.2, "Oracle BAM Client Requirements"

■ Section 4.3.3, "Additional Requirements for Optional Excel View in Oracle BAM Active Viewer or Oracle BAM Active Studio"

■ Section 4.3.4, "Additional Notes for Microsoft Internet Explorer and Pop-Up Blockers in Oracle BAM Web Applications"

4.3.1 Oracle SOA and Oracle BAM System RequirementsBelow are the recommended hardware and system configuration requirements for Oracle SOA and Oracle BAM:

■ CPU: dual-core Pentium, 1.5GHz or greater

■ Disk Space: 15GB or more

4.3.2 Oracle BAM Client RequirementsTable 2 shows the general requirements for the Oracle BAM client.

Table 1 Memory Requirements

Operating SystemMinimum Physical Memory Required

Minimum Available Memory Required

Linux 2 GB 4 GB

UNIX 2 GB 4 GB

Windows 2 GB 4 GB

4

4.3.3 Additional Requirements for Optional Excel View in Oracle BAM Active Viewer or Oracle BAM Active StudioThe Oracle BAM Excel view type requires that Microsoft Excel version XP, 2003, or 2007 is installed on the client computer.

4.3.4 Additional Notes for Microsoft Internet Explorer and Pop-Up Blockers in Oracle BAM Web ApplicationsIf you are using the Microsoft Windows pop-up blocker, or any other tool that blocks pop-up browser windows, you must configure it to allow pop-up windows while using the Oracle BAM Web applications. Turn off pop-up blockers in Microsoft Internet Explorer for the URL on which the Oracle BAM Web applications are hosted.

The Microsoft Internet Explorer installation on client systems must be a standard version, and it must not include customizations such as add-in tool bars or hot bars for other Web sites.

4.4 Oracle Portal, Forms, Reports and Discoverer RequirementsBelow are the recommended hardware and system configuration requirements for Oracle Portal, Forms, Reports and Discoverer 11g Release 1 (11.1.1):


■ Temp Space: 150MB or more

■ Swap Space: 512MB or more

Table 2 Oracle BAM Client Requirements

Category Requirements

Platforms (Microsoft Windows Intel x86-32)

Microsoft Windows XP Professional, Service Pack 2 or higher

Microsoft Windows Vista

Web Browsers Microsoft Internet Explorer 7.x

Microsoft Internet Explorer 8.x

Hardware 1 CPU at 1.2 GHz or faster minimum (a faster processor may be necessary to view complex dashboards)

512MB RAM minimum

5MB of free disk space

Display Oracle BAM Active Studio requires 1024 x 768 minimum resolution

Oracle BAM Active Viewer requires 800 x 600 or higher resolution

Note: Although the general Oracle Fusion Middleware product memory requirement is 4GB (Section 4.1, "General Memory Requirements"), on some Windows 32-bit operating systems the available memory is limited to 3GB. For components that are certified on such systems, Oracle recommends using the /3GB switch, as specified in Microsoft Knowledge Base Article #291988.

For more information, see the certification information, as described in Section 2, "Finding Oracle Fusion Middleware Certification Information".

5

If you are upgrading Oracle Portal, Forms, Reports and Discoverer from Oracle Application Server Release 10g (10.1.2.0.2), below are the recommended hardware and system configuration requirements:


■ Available Memory: 6GB or more

■ Temp Space: 950MB or more

■ Swap Space: 3GB or more

4.5 Oracle Identity Management Memory and Disk Space RequirementsThe specific memory requirements for your Oracle Identity Management 11g Release 1 (11.1.1) deployment depends on which components, or combination of components, you install. The following list identifies memory requirements for various components. Use the list as a guideline for determining the memory requirements specific to your deployment:

■ WebLogic Administration Server: 750 MB

■ WebLogic Managed Server running Oracle Directory Integration Platform and Oracle Directory Services Manager: 720 MB

■ WebLogic Managed Server running Oracle Identity Federation: 650 MB

■ Oracle Internet Directory: 75 MB

■ Oracle Virtual Directory: 105 MB

■ Oracle Enterprise Manager (EM) Agent: 25 MB

■ Oracle Process Manager and Notification Server (OPMN): 5 MB

Oracle Identity Management requires 2,200 MB of disk space if you are only installing the software (you select the Install Software - Do Not Configure installation type). If you configure the software, an additional 150 MB of space are required if all components are selected for configuration; less space is required if fewer components are selected.

4.6 Oracle Business Intelligence RequirementsThis section contains important information for the system on which you are installing Oracle Business Intelligence and the database containing the schemas. The following topics are covered:

■ Section 4.6.1, "Installation System Requirements for Oracle Business Intelligence"

■ Section 4.6.2, "Database Requirements for Oracle Business Intelligence"

4.6.1 Installation System Requirements for Oracle Business IntelligenceBelow are the recommended hardware and system configuration requirements for an Oracle Business Intelligence installation:


■ Available Memory: 4GB or more for 32-bit operating systems, or 8GB or more for 64-bit operating systems

■ Temp Space: 2GB or more

6

■ Swap Space: 4GB or more for 32-bit operating systems, or 8GB or more for 64-bit operating systems

4.6.2 Database Requirements for Oracle Business IntelligenceBelow are the recommended disk space requirements for the database containing the Oracle Business Intelligence Scheduler database tables.

■ 500MB on Oracle and Microsoft SQL Server databases for standalone and Business Intelligence applications and deployments.

■ 500MB on IBM DB2 databases for standalone deployments.

4.7 Oracle Data Integrator RequirementsThis section contains the following topics:

■ Section 4.7.1, "Oracle Data Integrator in a Clustered Environment"

■ Section 4.7.2, "Hardware and System Configuration Requirements for Oracle Data Integrator"

■ Section 4.7.3, "Additional Requirements for Oracle Data Integrator Java EE Components"

■ Section 4.7.4, "Database Requirements for Oracle Data Integrator"

4.7.1 Oracle Data Integrator in a Clustered EnvironmentThe installation of Oracle Data Integrator is not supported in a clustered environment.

4.7.2 Hardware and System Configuration Requirements for Oracle Data IntegratorBelow are the recommended hardware and system configuration requirements for Oracle Data Integrator Studio and Standalone Agents:



■ Available Memory: 2GB or more

4.7.3 Additional Requirements for Oracle Data Integrator Java EE ComponentsJava EE components require the presence of an application server on your system.

For 11g Release 1 (11.1.1.6.0) and earlier, only Oracle WebLogic Server can be used as the application server; make sure your system also meets the Oracle WebLogic Server system requirements before you install the Java EE components for Oracle Data Integrator.

4.7.4 Database Requirements for Oracle Data IntegratorBelow are the recommended storage space requirements for the database containing the Oracle Data Integrator Repository tables:

■ Master Repository: 60 Mb of storage space.

■ Work Repository: 80 Mb of storage space.

7

4.8 Oracle Data Profiling and Data Quality RequirementsThis section contains the requirements for Oracle Data Profiling and Oracle Data Quality for Data Integrator. The following topics are covered:

■ Section 4.8.1, "Oracle Data Quality Client Requirements"

■ Section 4.8.2, "Oracle Data Profiling and Quality Server Requirements"

■ Section 4.8.3, "Additional Requirements for Servers"

4.8.1 Oracle Data Quality Client RequirementsBelow are the recommended hardware and system configuration requirements for the Oracle Data Quality Client:


■ Disk Space: 500MB or more

■ Available Memory: 512MB or more

4.8.2 Oracle Data Profiling and Quality Server RequirementsBelow are the recommended hardware and system configuration requirements for the Oracle Data Profiling and Quality Server:

■ CPU: The CPU Requirement for Oracle Data Profiling and Quality Servers are listed in Table 3.

■ Disk space: 1.5GB or more.

■ Available memory: 2GB or more. 4GB is recommended (8GB for a power server).

Note: The storage space required may vary depending on the size of your models and projects, and on the volume of execution logs you keep in this repository.

Note: Disk usage for the postal tables and for data processing should be taken into account in addition to this space. The amount of space used by postal table varies according to the countries and options you purchase. The amount of space used for data processing varies according to your data volume.

Table 3 CPU Requirements for Oracle Data Profiling and Quality Server

Platform ServerMinimum CPU Processor

IBM AIX RS/6000 900 MHz eServerP5 and pSeries Platform Power 5

Sun Solaris Sun Sparc 900 MHz Ultrasparc IV

HP-UX (PA Risc) HP PA RISC (PA 2.0) 750 MHz PA RISC PA 8800

HP-UX (IA64/Itanium) HP Itanium (IA 64) 1.4 GHz Intel Itanium 2

Linux and Windows Any 3 GHz Intel Xeon MP

8

4.8.3 Additional Requirements for ServersThe Inetd (XInetd for Linux) component is required and must be installed on UNIX servers.

5 Oracle Fusion Middleware System Configuration RequirementsThis section contains important information if you are installing Oracle Fusion Middleware on a DHCP host, non-network host, or multihomed host.

The following topics are covered:

■ Section 5.1, "Configuration Requirements for Installing on a DHCP Host"

■ Section 5.2, "Configuration Requirements for Installing on a Non-Networked Computer"

■ Section 5.3, "Configuration Requirements for Installing on a Multihomed Computer"

■ Section 5.4, "Configuration Requirements for Installing OPMN"

5.1 Configuration Requirements for Installing on a DHCP HostIf you are installing your Oracle Fusion Middleware products on a DHCP host, you must follow the configuration steps in this section for your platform.

5.1.1 For Linux x86 PlatformsOn Linux x86 operating systems, configure the host to resolve host names to the loopback IP address by modifying the /etc/hosts file to contain the following entries:

127.0.0.1 hostname.domainname hostname127.0.0.1 localhost.localdomain localhost

After doing so, check that the hostname resolves to the loopback IP address by entering the following command:

/bin/ping hostname.domainname

5.1.2 For Windows x86 PlatformsOn Windows systems, install a loopback adapter on the single DHCP host that obtains an IP address from the DHCP server (see Section 5.1.2.1, "Installing a Windows Loopback Adapter"). This assigns a local IP address to your computer.

After installing the adapter, add a line to the %SYSTEMROOT%\system32\drivers\etc\hosts file with the following format, immediately after the localhost line:

IP_address hostname.domainname hostname

Replace IP_address with the local IP address of the loopback adapter.

Instructions for removing the loopback adapter are provided in Section 5.1.2.2, "Removing a Windows Loopback Adapter".

5.1.2.1 Installing a Windows Loopback Adapter To install a loopback adapter on Windows 2003 or Windows XP:

1. Open the Windows Control Panel.

9

Windows 2003: Select Start > Control Panel > Add Hardware.

Windows XP: Select Start > Control Panel, then double-click Add Hardware.

2. In the "Welcome" window, click Next.

3. In the "Is the hardware connected?" window, select Yes, I have already connected the hardware, then click Next.

4. In the "The following hardware is already installed on your computer" window, in the list of installed hardware, select Add a new hardware device, then click Next.

5. In the "The wizard can help you install other hardware" window, select Install the hardware that I manually select from a list, then click Next.

6. In the "From the list of hardware types, select the type of hardware you are installing" window, select Network adapters, then click Next.

7. In the "Select Network Adapter" window, make the following selections:

■ Manufacturer: Microsoft

■ Network Adapter: Microsoft Loopback Adapter

8. Click Next.

9. In the "The wizard is ready to install your hardware" window, click Next.

10. In the "Completing the Add Hardware Wizard" window, click Finish.

11. If you are using Windows 2003, restart your computer.

12. Right-click My Network Places on the desktop and choose Properties. This displays the Network Connections Control Panel.

13. Right-click the connection that was just created. This is usually named "Local Area Connection 2". Choose Properties.

14. On the "General" tab, select Internet Protocol (TCP/IP), then click Properties.

15. In the "Properties" dialog box, click Use the following IP address and do the following:

a. IP Address: Enter a non-routable IP for the loopback adapter. Oracle recommends the following non-routable addresses:

192.168.x.x (x is any value between 1 and 255)10.10.10.10

b. Subnet mask: Enter 255.255.255.0.

c. Record the values you entered, which you will need later in this procedure.

d. Leave all other fields empty.

e. Click OK.

16. In the "Local Area Connection 2 Properties" dialog, click OK.

17. Close Network Connections.

18. Restart the computer.

5.1.2.2 Removing a Windows Loopback Adapter To remove a loopback adapter on Windows 2003 or Windows XP:

1. Start the System Control panel.

10

Windows 2003: Select Start > Control Panel > System.

Windows XP: Select Start > Control Panel, then double-click System.

2. In the "Hardware" tab, click Device Manager.

3. In the "Device Manager" window, expand Network adapters. You should see Microsoft Loopback Adapter.

4. Right-click Microsoft Loopback Adapter and select Uninstall.

5. Click OK.

5.2 Configuration Requirements for Installing on a Non-Networked ComputerYou can install your Oracle Fusion Middleware product on a non-networked computer, such as a laptop. Because a non-networked computer has no access to other computers, you have to install all the components that you need on the computer.

In addition, you must follow the instructions in Section 5.1, "Configuration Requirements for Installing on a DHCP Host" to install a loopback adapter and modify the hosts file on your system.

5.3 Configuration Requirements for Installing on a Multihomed ComputerYou can install your Oracle Fusion Middleware product on a multihomed computer. A multihomed computer is associated with multiple IP addresses. This is typically achieved by having multiple network cards on the computer. Each IP address is associated with a host name; additionally, you can set up aliases for each hostname.

The installer picks up the fully qualified domain name from the first entry in /etc/hosts (on UNIX operating systems) or %SYSTEMROOT%\system32\drivers\etc\hosts (on Windows operating systems) file. So if your file looks like the following:

127.0.0.1 localhost.localdomain localhost10.1.1.1 examplehost1.example.com examplehost110.2.2.2 examplehost2.example.com examplehost2

examplehost1.example.com would be picked for configuration.

For specific network configuration of a system component, refer to the individual component’s configuration documentation.

In any situation where you change any combination of the host name, domain name, or IP address of a host, you also change the information for Java components and system components. See "Changing the Network Configuration of Oracle Fusion Middleware" in Oracle Fusion Middleware Administrator's Guide for more information about additional steps that need to be performed.

5.4 Configuration Requirements for Installing OPMNIf you are installing an Oracle Fusion Middleware product that also installs Oracle Process Manager and Notification Server (OPMN), you must make sure the installation system has valid entries in the hosts (/etc/hosts on UNIX systems and C:\windows\system32\drivers\etc\hosts on Microsoft Windows systems) file. You must make sure that the IP address is valid and corresponds to the network setup on the system.

11

You can check your system’s IP address and host name as follows:

On UNIX operating systems:

ipconfig -a

On Microsoft Windows operating systems:

ipconfig /all

The IP address and corresponding host name in your hosts file must match the IP address and host name you get from the ipconfig command. Otherwise, the opmn.xml file will contain incorrect configuration information, and OPMN will not start.

6 Oracle Universal Installer (OUI) RequirementsThis section contains prerequisite information for the Oracle Universal Installer (OUI). The requirements in this section must be met in order for the installer to start:

■ Section 6.1, "Environment Variables"

■ Section 6.2, "Startup Requirements"

■ Section 6.3, "Running the 32-Bit Installer on 64-Bit Operating System"

■ Section 6.4, "Special Startup Requirements for Linux x86 or Linux x86-64 Operating Systems"

■ Section 6.5, "Installing on Operating Systems Not Certified at the Time of Product Release"

6.1 Environment VariablesThe environment variables on your system must be set as described in Table 4:

Table 4 Oracle Universal Installer Environment Variable Requirements

Variable Description

ORACLE_HOME Applies to: all configuration tools for all products on all platforms.

This variable is automatically set by the configuration tool to the Oracle home from where the configuration tool is started. This is true even if the ORACLE_HOME variable is already set.

ORACLE_SID Applies to: all installers for all products on all platforms.

For the Oracle Portal, Forms, Reports and Discoverer installer, this variable must not be set.

For all other installers, there are no restrictions as to whether this variable is set or not set.

PATH Applies to: all installers for products with system components only on Windows operating systems. See "Resolving PATH and Directory Issues on Windows" in the Oracle Fusion Middleware Release Notes for Microsoft Windows for important additional information.

This variable is automatically set by the installer and prepended with ORACLE_HOME\bin.

NOTE: make sure this variable does not contain a reference to any other Oracle home directory.

12

6.2 Startup RequirementsThe items in Table 5 are checked as the installer is being started:

SHLIB_PATH Applies to: all installers for products with system components only on HP-UX and HP-IA operating systems.

This variable is automatically set by the installer and prepended with ORACLE_HOME/lib.

LIBPATH Applies to: all installers for products with system components only on AIX operating systems.


LD_LIBRARY_PATH Applies to: all installers for products with system components only on Linux and Solaris operating systems.


NOTE: make sure this variable does not contain a reference to any other Oracle home directory.

DISPLAY Applies to: all installers for all products on all platforms.

If you are installing with a graphical user interface (GUI), this variable must be set to the monitor where you want the installer GUI to appear.

Refer to your operating system documentation for specific instructions on how to do this, as procedures vary depending on your exact operating system.

TMP

TMPDIR

Applies to: all installers for all products on all platforms.

Optional variable. If not set, then the default value is /tmp.

TNS_ADMIN

ORA_NLS

LD_BIND_NOW

Applies to: all installers for all products on all platforms.

For the Oracle Portal, Forms, Reports and Discoverer installer, these variables must not be set.

For all other installers, there are no restrictions as to whether these variables are set or not set.

Table 4 (Cont.) Oracle Universal Installer Environment Variable Requirements

Variable Description

13

6.3 Running the 32-Bit Installer on 64-Bit Operating SystemThis section contains important information for those products that support installing the 32-bit version on a 64-bit operating system:

■ Section 6.3.1, "Starting the 32-Bit Oracle Web Tier Installer on a 64-Bit Linux Operating System"

■ Section 6.3.2, "Starting the Generic Installer with a 32-Bit JDK on a 64-Bit Operating System"

6.3.1 Starting the 32-Bit Oracle Web Tier Installer on a 64-Bit Linux Operating SystemIf you are installing the 32-bit version of Oracle Web Tier on a 64-bit Linux operating system, there are extra steps that must be performed before Oracle Web Tier can be installed. Instructions are provided in the Oracle Fusion Middleware Installation Guide for Oracle Web Tier. Installing a 32-bit version of Oracle Web Tier on a 64-bit Windows operating system is not supported.

6.3.2 Starting the Generic Installer with a 32-Bit JDK on a 64-Bit Operating SystemIf you are installing Oracle SOA Suite, Oracle WebCenter Portal, Oracle WebCenter Content, Oracle Application Developer, Oracle Service Bus, or Oracle Identity and Access Management on any supported 64-bit operating system with a 32-bit JDK, you must specify the JRE_LOCATION using the -jreLoc parameter from the command line when you start the product installer. For example:

./runInstaller -jreLoc JRE_LOCATION

Normally, if you do not use the -jreLoc parameter you will be prompted to specify the JRE_LOCATION from the command line. However, this option is not supported in such cases, and the installer will not start.

Table 5 Oracle Universal Installer Startup Requirements

Category Accepted or Minimum Values

Platforms For a complete list of supported platforms, refer to the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document on the Oracle Fusion Middleware Supported System Configurations page, as described in Section 2, "Finding Oracle Fusion Middleware Certification Information".

CPU Speed At least 300MHz

Temp Space Varies by installer:

■ The generic installers (for example, Oracle SOA Suite, Oracle WebCenter Portal, Oracle Application Developer) require 150MB.

■ Oracle Data Integrator (ODI), while it is a generic installer, requires 500MB.

■ The platform-specific installers (for example, Oracle Web Tier, Oracle Identity Management, Oracle Portal, Forms, Reports and Discoverer, Oracle Business Intelligence) require 400MB.

Swap Space At least 500MB

Monitor At least 256 colors (this is a requirement for the graphical user interface mode only)

14

6.4 Special Startup Requirements for Linux x86 or Linux x86-64 Operating SystemsIf you are running Oracle Universal Installer on Linux x86 or Linux x86-64 operating systems, you must modify the value of the SHMMAX kernel parameter to avoid seeing errors generated by the Oracle Universal Installer. To do so:

1. Change the value of SHMMAX to 4294967295 by including the following line in /etc/sysctl.conf:

kernel.shmmax = 4294967295

2. Activate the new SHMMAX setting by running the command:

/sbin/sysctl -p

3. Start the Oracle Universal Installer and install your software.

6.5 Installing on Operating Systems Not Certified at the Time of Product ReleaseIn some cases, an operating system will become certified for use with Oracle Fusion Middleware products after a particular release has been made available. If you try to install your Oracle Fusion Middleware product on one of these newly-certified operating systems, the product installer will give you a warning message during startup, indicating that the operating system on which you are installing is not valid. For example:

Warning:Checking operating system certificationExpected result: One ofenterprise-5.4,enterprise-4,enterprise-5,redhat-5.4,redhat-4,redhat-5,SuSE-10Actual Result:SuSE-11Check complete. The overall result of this check is: FailedProblem: This Oracle software is not certified on the current operating system.

To work around this issue, you can click the Continue button to ignore this warning message, or you can start the installer with the -ignoreSysPrereqs option. For example:

./runInstaller -ignoreSysPrereqs

This issue is currently seen in the platform, product, and release combinations described in Table 6:

15

Table 6 When is -ignoreSysPrereqs Needed?

PlatformTo Install This Release: Perform These Steps:

Use -ignoreSysPrereqs?

SUSE 11

IBM AIX 7.1

Oracle Portal, Forms, Reports and Discoverer for:

11g Release 1 (11.1.1.3.0)

11g Release 1 (11.1.1.4.0)

11g Release 1 (11.1.1.5.0)

11g Release 1 (11.1.1.6.0)

1. Install 11g Release 1 (11.1.1.2.0) Yes

2. Run the Patch Set Installer to patch 11g Release 1 (11.1.1.2.) to 11g Release 1 (11.1.1.3.0), 11g Release 1 (11.1.1.4.0), 11g Release 1 (11.1.1.5.0), or 11g Release 1 (11.1.1.6.0)

No

Oracle Linux 6 Oracle Fusion Middleware 11g Release 1 (11.1.1.5.0)

For all certified 11g Release 1 (11.1.1.5.0) products (see Section 2, "Finding Oracle Fusion Middleware Certification Information"), run the installer as described in that product’s installation guide.

Yes

For all certified 11g Release 1 (11.1.1.5.0) products (see Section 2, "Finding Oracle Fusion Middleware Certification Information") that require an 11g Release 1 (11.1.1.2.0) installer, run the 11g Release 1 (11.1.1.2.0) installer as described in that product’s installation guide and then use the Patch Set Installer to update your software to 11g Release 1 (11.1.1.5.0) as described in Oracle Fusion Middleware Patching Guide.

Yes when running the 11g Release 1 (11.1.1.2.0) product installer.

No when running the Patch Set Installer.

Note: The -ignoreSysPrereqs option should only be used if ALL of the following conditions are met:

■ It should only be used with the specific combination of products, releases, and operating systems listed in Table 6.

■ Your operating system is certified for use with Oracle Fusion Middleware, as described in the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document (see Section 2, "Finding Oracle Fusion Middleware Certification Information").

■ Your operating system adheres to all the requirements and specifications as described in Section 7, "System Requirements for UNIX Operating Systems" and Section 8, "System Requirements for Windows Operating Systems".

16

7 System Requirements for UNIX Operating SystemsThis section contains system requirement information for UNIX operating systems.

In some cases, a particular platform may be de-supported for use with Oracle Fusion Middleware products. While this particular platform’s requirements may remain in this document for legacy purposes, it would no longer be listed in the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document and would no longer be considered a "certified" platform.

The System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document is located on the Oracle Fusion Middleware Supported System Configurations page, as described in Section 2, "Finding Oracle Fusion Middleware Certification Information".

All packages listed are minimum versions.

The following topics are covered in this section:

■ Section 7.1, "Supported Linux Operating System Versions, Packages, and Patches"

■ Section 7.2, "Supported Solaris Operating System Versions, Packages, and Patches"

■ Section 7.3, "Supported HP-UX Operating System Versions, Packages, and Patches"

■ Section 7.4, "Supported IBM AIX Operating System Versions, Packages, and Patches"

■ Section 7.5, "Open File Limit"

■ Section 7.6, "Applying Solaris Patches in Non-Global Zones"

■ Section 7.7, "Enabling Unicode Support"

7.1 Supported Linux Operating System Versions, Packages, and PatchesTable 7 lists the platform, operating system, package, and patch information for Linux operating systems that are either currently supported or were supported in a previous release.

17

Table 7 Supported UNIX Operating Systems

Platform

Operating System Version Supported Packages

Operating System Patches

Linux x86 Oracle Linux 4 (UL7+)

Red Hat Linux 4 (UL7+)

gcc-3.4.3-22.1

gcc-c++-3.4.3-22.1

openmotif21-2.1.30-11.RHEL4.4

setarch-1.6-1

pdksh-5.2.14-30

sysstat-5.0.5-1

gnome-libs-1:1.4.1.2.90-44.1

libaio-0.3.105

libaio-devel-0.3.105

libstdc++-3.4.3-22.1

libstdc++-devel-3.4.3-22.1

compat-libstdc++-296-2.96-132.7.2

compat-db-4.1.25-9

control-center-2.8.0-12

glibc-common-2.3.4-2.9

binutils-2.15.92.0.2-13

make-1:3.80-5

xscreensaver-4.18-5.rhel4.2

openmotif22-2.2.3 (for Oracle Reports Server)

openmotif-2.2.3 (for Oracle Reports Server)

Kernel 2.6.9

Linux x86 Oracle Linux 5 (UL3+)


gcc-4.1.0-28.4

gcc-c++-4.1.0-28.4

setarch-1.6-1

sysstat-5.0.5-1

libaio-0.3.106


libstdc++-4.1.0-28.4


compat-libstdc++-296-2.96-132.7.2

compat-db-4.1.25-9

control-center-2.8.0-12

glibc-common-2.3.4-2.9

binutils-2.16.91.0.5-23.4

make-3.80-202.2

openmotif22-2.2.3 (for Oracle Reports Server)


Kernel 2.6.18

18

Linux x86 SUSE 10 (SP1+) gcc-4.1.0-28.4

glibc-devel-2.4-31.2

gcc-c++-4.1.0-28.4

libaio-0.3.104

libaio-0.3.106 (32 bit)


libgcc-4.1.0-28.4


libstdc++-4.1.0-28.4

binutils-2.16.91.0.5-23

compat-libstdc-296-2.96-132.7.21

compat-libstdc++-5.0.7-22.2

compat-2006.1.25-11.2

make-3.80-202.2

openmotif21-libs-2.1.30


Kernel 2.6.16.21

Linux x86 SUSE 11 (all SP levels included)

binutils-2.19-11.28

gcc-4.3-62.198

gcc-c++-4.3-62.198

glibc-2.9-13.2

glibc-devel-2.9-13.2

libaio-0.3.104-140.22

libaio-0.3.106 (32 bit)

libaio-devel-0.3.104-140.22

libgcc43-4.3.3_20081022-11.18

libstdc++43-4.3.3_20081022-11.18

libstdc++43-devel-4.3.3_20081022-11.18

make-3.81-128.20

sysstat-8.1.5-7.8

openmotif22-libs-2.2.4-138.17 (for Oracle Reports)2

openmotif-2.3.1-3.132

openmotif21-libs-2.1.30MLI4-143.92

openmotif-libs-2.3.1-3.132

openmotif-devel-2.3.1-3.132

Kernel 2.6.27.19-5-default

Table 7 (Cont.) Supported UNIX Operating Systems

Platform



19

Linux x86-64

Oracle Linux 4 (UL7+)


binutils-2.15.92.0.2

compat-libstdc++-33-3.2.3

compat-libstdc++-33-3.2.3 (32-bit)

elfutils-libelf-0.97

elfutils-libelf-devel-0.97

gcc-3.4.5

gcc-c++-3.4.5

glibc-2.3.4-2.19

glibc-2.3.4-2.19 (32-bit)

glibc-common-2.3.4

glibc-devel-2.3.4

glibc-devel-2.3.4 (32-bit)

glibc-devel-2.12-1.7.el6.i686.rpm

libaio-0.3.105

libaio-0.3.105 (32-bit)


libgcc-3.4.5

libgcc-3.4.5 (32-bit)

libstdc++-3.4.5

libstdc++-3.4.5 (32-bit)

libstdc++-devel 3.4.5

make-3.80 sysstat-5.0.5

openmotif21-2.1.30-11.RHEL4.4 (for Oracle Portal, Forms, Reports and Discoverer)

openmotif-2.2.3 (64-bit) (for Oracle Reports Server)

Kernel 2.6.9


Platform



20

Linux x86-64

Oracle Linux 5 (UL3+)


binutils-2.17.50.0.6

compat-libstdc++-33-3.2.3

compat-libstdc++-33-3.2.3 (32-bit)

elfutils-libelf-0.125

elfutils-libelf-devel-0.125

gcc-4.1.1

gcc-c++-4.1.1

glibc-2.5-12

glibc-2.5-12 (32-bit)

glibc-common-2.5

glibc-devel-2.5

glibc-devel-2.5-12 (32-bit)


libaio-0.3.106

libaio-0.3.106 (32-bit)


libgcc-4.1.1

libgcc-4.1.1 (32-bit)

libstdc++-4.1.1

libstdc++-4.1.1 (32-bit)

libstdc++-devel 4.1.1


openmotif22-2.2.3 (64-bit) (for Oracle Reports Server)


redhat-lsb-3.1-12.3.EL.0.2

Kernel 2.6.18


Platform



21

Linux x86-64

Oracle Linux 6 binutils (version 2.20.51.0.2-5.11.el6)

compat-libcap (version 1-1.10-1)

compat-libstdc++-33 (version 3.2.3-69.el6)

libgcc (version 4.4.4-13.el6)

libstdc++ (version 4.4.4-13.el6)

libstdc++-devel (version 4.4.4-13.el6)

sysstat (version 9.0.4-11.el6)

gcc (version 4.4.4-13.el6)

gcc-c++ (version 4.4.4-13.el6)

glibc (version 2.12-1.7.el6)

glibc-devel (version 2.12-1.7.el6)


libaio (version 0.3.107-10.el6)

libaio-devel (version 0.3.107-10.el6)

Kernel 2.6.32-100.28.5.el6

Linux x86-64

SUSE 10 (SP1+) binutils-2.16.91.0.5

compat-libstdc++-5.0.7-22.2

gcc-4.1.0 gcc-c++-4.1.0

glibc-2.4-31.2

glibc-32bit-2.4-31.2 (32-bit)

glibc-devel-2.4


glibc-devel-32bit-2.4 (32-bit)

libaio-0.3.104


libelf-0.8.5

libgcc-4.1.0

libstdc++-4.1.0

libstdc++-devel-4.1.0


openmotif21-libs-2.1.30 (for Oracle Portal, Forms, Reports and Discoverer)


Kernel 2.6.16.21


Platform



22

Linux x86-64

SUSE 11 (all SP levels included)

binutils-2.19-11.28

gcc-32bit-4.3

gcc-4.3-62.198

gcc-c++-4.3-62.198

glibc-2.9-13.2

glibc-32bit-2.9

glibc-devel-2.9


glibc-devel-32bit-2.9-13.2

ksh-93t

libaio-0.3.104-140.22

libaio-32bit-0.3.104

libaio-devel-0.3.104-140.22

libaio-devel-32bit-0.3.104

libstdc++33-3.3.3

libstdc++33-32bit-3.3.3

libstdc++-devel-4.3

libstdc++43-32bit-4.3.3_20081022

libgcc43-4.3.3_20081022-11.18

libstdc++43-4.3.3_20081022-11.18

libstdc++43-devel-4.3.3_20081022-11.18

libstdc++43-devel-32bit-4.3.3_20081022

make-3.81-128.20

sysstat-8.1.5-7.8

Packages required for Oracle Reports:

openmotif-2.3.1-3.132

openmotif-devel-32bit-2.3.1-3.132

openmotif22-libs-32bit-2.2.4-138.172

openmotif-libs-2.3.1-3.132

openmotif-devel-2.3.1-3.132

openmotif-libs-32bit-2.3.1-3.132

openmotif21-libs-32bit-2.1.30MLI4-143.22

openmotif22-libs-2.2.4-138.172

Kernel 2.6.27.19-5-default

1 This package is required for Oracle Discoverer to work properly, but is not available for SUSE 10. To work around this issue, you must install compat-libstdc++-296-2.96-132.7.2 or higher from any Red Hat Linux or Oracle Enterprise Linux distribution.

2 To obtain openmotif packages for SUSE11, go to the public download location http://ftp.novell.com/partners/oracle/sles-11/openmotif_FUSION_SLES11.tgz. This is a single zip file from Novell and includes a README file with details about package names, versions, and source.


Platform



23

7.2 Supported Solaris Operating System Versions, Packages, and PatchesTable 8 lists the platform, operating system, package, and patch information for Solaris operating systems that are either currently supported or were supported in a previous release.

Table 8 Supported Solaris Operating Systems

Platform



Solaris SPARC64 Solaris 9 Update 9+

SUNWarc, SUNWbtool, SUNWhea

SUNWlibC, SUNWlibm, SUNWlibms

SUNWsprot, SUNWtoo, SUNWi1of

SUNWi1cs, SUNWi15cs, SUNWxwfnt SUNWsprox

Motif: 2.1.0 (for Oracle Portal, Forms, Reports and Discoverer only)

GCC: package 3.4.2 or higher in /usr/local/packages (for Oracle I/PM). The LD_LIBRARY_PATH environment variable must also be set to /usr/local/packages/gcc-3.4.2/lib before starting the Oracle I/PM Managed Server.

118558-22

112874-39

112760-051

114370-052

1 "C 5.5: Patch for S1S8CC C compiler" patch required only if the installed version of Studio 11 does not already include this patch (or a superseded version).

2 Symlink patch required only if the method of installing Solaris 9 Update 9 was via a Solaris Patch Cluster and that version of the Solaris Patch Cluster did not already include this patch (or a superseded version).

Solaris SPARC64 Solaris 10 Update 4+




SUNWi1cs, SUNWi15cs, SUNWxwfnt

Motif: 2.1.0 (for Oracle Portal, Forms, Reports, and Discoverer only)


127111-02

137111-04

Solaris x86-64 Solaris 10 Update 6+




SUNWi1cs (ISO8859-1)

SUNWi15cs (ISO8859-15)

SUNWxwfnt, SUNWcsl


120754-06

119964-14

119961

139556-08

127112-023

137112-04

3 For additional details about patches 127112 and 137112, see notes 1000642.1 and 1019395.1 on My Oracle Support.

24

7.3 Supported HP-UX Operating System Versions, Packages, and PatchesTable 9 lists the platform, operating system, package, and patch information for HP-UX operating systems that are either currently supported or were supported in a previous release.

Table 9 Supported HP-UX Operating Systems

PlatformOperating System Version Supported Packages


HP-UX Itanium HP-UX 11i v2 (11.23)

B.11.23.0703.059a Base Quality Pack Bundle for HP-UX 11i v2, March 2007


PHCO_35524

PHCO_36673

PHKL_35029

PHKL_35478

PHSS_35978

PHSS_35979

PHSS_37201

HP-UX Itanium HP-UX 11i v3 (11.31)



PHKL_36248

PHKL_36249

PHSS_37202

PHSS_37501

PHCO_38050

PHSS_38139

HP-UX PA-RISC HP-UX 11i v2 (11.23)



PHCO_35524

PHCO_36673

PHKL_35029

PHKL_35478

PHKL_35767

PHKL_36853

PHSS_35101

PHSS_35102

PHSS_35103

PHSS_35176

PHSS_35978

PHSS_35979

PHSS_37201

HP-UX PA-RISC HP-UX 11i v3 (11.31)



PHKL_36248

PHKL_36249

PHSS_37202

PHSS_37501

PHCO_38050

PHSS_38139

25

7.4 Supported IBM AIX Operating System Versions, Packages, and PatchesTable 10 lists the platform, operating system, package, and patch information for IBM AIX operating systems that are either currently supported or were supported in a previous release.

7.5 Open File LimitOn all UNIX operating systems, the minimum Open File Limit should be 4096. You can see how many files are open with the following command:

Table 10 Supported IBM AIX Operating Systems

Platform



AIX 7100-01 Motif: 2.1.0 (for Oracle Portal, Forms, Reports and Discoverer only)

IZ89165s02.101217.epkg.Z (for Oracle Business Intelligence)


bos.adt.base

bos.adt.lib

bos.adt.libm

bos.loc.utf.EN_US (for Oracle Business Intelligence)

bos.perf.libperfstat 6.1.2.1 or later

bos.perf.perfstat

bos.perf.proctools

rsct.basic.rte

rsct.compat.clients.rte

xlC.aix61.rte:10.1.0.0 or later

gpfs.base 3.2.1.8 or later (Only for RAC)


bos.adt.base

bos.adt.lib

bos.adt.libm

bos.perf.libperfstat 5.3.9.0 or later

bos.perf.perfstat

bos.perf.proctools

rsct.basic.rte

rsct.compat.clients.rte

xlC.aix50.rte:10.1.0.0 or later

gpfs.base 3.2.1.8 or later (Only for RAC)

26

/usr/sbin/lsof | wc -l

To check your open file limits, use the commands below.

For C-shell:

limit descriptors

For Bash:

ulimit -n

To change the open file limits, login as root and edit the /etc/security/limits.conf file. Look for the following two lines:

* soft nofile 2048* hard nofile 2048

Change the values from 2048 to 4096, then reboot the machine.

7.6 Applying Solaris Patches in Non-Global ZonesOn Solaris operating systems, the prerequisite patches that are applied in the global zone can be considered applied in the non-global zones. There is only one kernel running on the system, and all zones must be at the same patch level with respect to the kernel and other Solaris system components. Kernel patches can only be applied from the global zone, and they affect the global and all non-global zones equally.

To check if a kernel patch is applied in the global zone, use the following command:

showrev -p | grep patch_number

For example, to check if patch 137111-04 is applied:

showrev -p | grep 137111

7.7 Enabling Unicode SupportYour operating system configuration can influence the behavior of characters supported by Oracle Fusion Middleware products.

On UNIX operating systems, Oracle highly recommends that you enable Unicode support by setting the LANG and LC_ALL environment variables to a locale with the UTF-8 character set. This enables the operating system to process any character in Unicode. Oracle SOA Suite technologies, for example, are based on Unicode.

If the operating system is configured to use a non-UTF-8 encoding, Oracle SOA Suite components may function in an unexpected way. For example, a non-ASCII file name can make the file inaccessible and cause an error. Oracle does not support problems caused by operating system constraints.

In a design-time environment, if you are using Oracle JDeveloper, select Tools -> Preferences -> Environment -> Encoding -> UTF-8 to enable Unicode support.

Note: The following examples are for Linux operating systems. Equivalent commands should be followed for other operating systems.

27

8 System Requirements for Windows Operating SystemsThis section contains the following information regarding Microsoft Windows operating systems:

■ Section 8.1, "Certified Windows Operating Systems"

■ Section 8.2, "Enabling User Account Control (UAC) on Windows Operating Systems"

■ Section 8.3, "Required Installation Privileges for Oracle Identity Management and Oracle Forms and Reports on Windows Operating Systems"

■ Section 8.4, "Installing and Configuring Java Access Bridge"

8.1 Certified Windows Operating SystemsRefer to the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document for the latest information on certified Windows operating systems. This document is available in the Oracle Fusion Middleware Supported System Configurations page, as described in Section 2, "Finding Oracle Fusion Middleware Certification Information".

8.2 Enabling User Account Control (UAC) on Windows Operating SystemsOn Microsoft Windows Vista, Windows Server 2008, or Windows 7 operating systems, you must enable User Account Control (UAC) so that the correct permissions are applied to the cwallet.sso file.

To enable UAC:

1. Run secpol.msc from the command prompt.

2. Select Security Settings > Local Policies > Security Options.

3. Set the User Account Control:Run all Administrator in Admin Approval Mode option to enabled.

4. Restart the host.

5. Restart the servers.

8.3 Required Installation Privileges for Oracle Identity Management and Oracle Forms and Reports on Windows Operating SystemsIn order to install Oracle Identity Management, Oracle Forms and Reports, or use the Oracle Forms and Reports Builders after installation on a Microsoft Windows Vista or newer operating system, the operating system user must have Windows "Administrator" privileges.

Even when a user with "Administrator" privileges logs in to the machine, the administrative role is not granted for default tasks. In order to access the Oracle home files and folders, the user must launch the command prompt or Windows Explorer as "Administrator" explicitly, even if the user is logged in as the administrator.

To do so, you can do either one of the following:

■ Find the Command Prompt icon (for example, from the Start menu or from the Desktop), right-click on the icon, and select Run as Administrator. Then you can

28

run the executables (for example, the WebLogic Server installer) from the command line.

■ Start Windows Explorer, find the executable you want to run (for example, rcu.bat for RCU, config.bat for the Configuration Wizard, or setup.exe for the installer), right-click on the executable, and select Run as Administrator.

8.4 Installing and Configuring Java Access BridgeIf you are installing on a Windows machine, you have the option of installing and configuring Java Access Bridge for Section 508 Accessibility. This is only necessary if you require Section 508 Accessibility features.

Installation instructions are available in the Oracle Java Access Bridge Installation and Application Developer's Guide:

http://docs.oracle.com/javase/accessbridge/2.0.2/toc.htm

9 Oracle WebLogic Server InformationMost Oracle Fusion Middleware products require the presence of Oracle WebLogic Server on your system. The version of Oracle WebLogic Server that is required depends on the version of Oracle Fusion Middleware you are installing. See Table 11 for more information.

Oracle WebLogic Server can be obtained from the following URL:

http://www.oracle.com/technetwork/middleware/weblogic/downloads/

Refer to the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document to see if there are additional versions of Oracle WebLogic Server that can be used with your version of Oracle Fusion Middleware. This document is available in the Oracle Fusion Middleware Supported System Configurations page, as described in Section 2, "Finding Oracle Fusion Middleware Certification Information".

10 Certified DatabasesRefer to the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document on the Oracle Fusion Middleware Supported System Configurations page for the latest information on certified databases. A link to this document is provided in Section 2, "Finding Oracle Fusion Middleware Certification Information".

Table 11 Required Oracle WebLogic Server Versions

Oracle Fusion Middleware VersionRequired Oracle WebLogic Server Versions

Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) Oracle WebLogic Server 11gR1 (10.3.1)






Oracle WebLogic Server 11gR1 (10.3.6)

29

See the Current System Certification tab for Oracle databases, or the Non Oracle DBs Certification tab for third-party databases.

This section contains the following topics:

■ Section 10.1, "Using Oracle Database 11g (11.1.0.7) with Oracle Identity Manager"

■ Section 10.2, "Using Oracle Database 11g (11.2.0.1) with OID and Oracle Data Vault"

■ Section 10.3, "Using Oracle Express Edition (XE) Database for Oracle SOA Suite"

■ Section 10.4, "Supported Databases for the MDS Schema"

10.1 Using Oracle Database 11g (11.1.0.7) with Oracle Identity ManagerIf you are using Oracle Database 11g (11.1.0.7) with Oracle Identity Management 11g, there are certain database patches that must be applied.

See "Patch Requirements for Oracle Database 11g (11.1.0.7)" in the "Oracle Identity Manager" chapter of the Oracle Fusion Middleware Release Notes for Linux x86 or Oracle Fusion Middleware Release Notes for Microsoft Windows (32-Bit). Patches for all operating systems (Linux, 32-bit Windows and 64-bit Windows) are identified.

10.2 Using Oracle Database 11g (11.2.0.1) with OID and Oracle Data VaultIf you are using Oracle Database 11g (11.2.0.1) and you choose to configure Oracle Internet Directory (OID) with Oracle Data Vault:

1. Apply patch 8897382 (see the README file in the patch for instructions).

2. In the ORACLE_HOME/ldap/datasecurity/dbv_oid_command_rules.sql (on UNIX operating systems) or ORACLE_HOME\ldap\datasecurity\dbv_oid_command_rules.sql (on Windows operating systems) file, find the following code:

/declare.begin.

dvsys.dbms_macadm.CREATE_COMMAND_RULE(command => 'CONNECT',rule_set_name => 'OID App Access',object_owner => 'ODS',object_name => '%',enabled => 'Y');

.commit;.end;/

Change the following line:

,object_owner => 'ODS'

to:

,object_owner => '%'

30

10.3 Using Oracle Express Edition (XE) Database for Oracle SOA SuiteOracle Database is the recommended database for SOA Suite deployments. Oracle Express Edition (XE) database is not supported.

10.4 Supported Databases for the MDS SchemaThe Oracle Metadata Services (MDS) Repository contains metadata for certain types of deployed applications. This includes custom Java EE applications developed by your organization and some Oracle Fusion Middleware component applications, such as Oracle B2B.

The MDS Repository supports Oracle databases, as well as non-Oracle databases, including SQL Server, DB2, and MySQL. For more information about the supported versions of these databases, see the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document on the Oracle Fusion Middleware Supported System Configurations page, as described in Section 2, "Finding Oracle Fusion Middleware Certification Information".

This section contains the following:

■ Section 10.4.1, "Notes for Using an Oracle Database for the MDS Schema"

■ Section 10.4.2, "Notes for Using a Microsoft SQL Server Database for the MDS Schema"

■ Section 10.4.3, "Notes for Using an IBM DB2 Database for the MDS Schema"

■ Section 10.4.4, "Notes for Using a MySQL Database for the MDS Schema"

10.4.1 Notes for Using an Oracle Database for the MDS SchemaNote that when you use an Oracle Database, the MDS database user created by Repository Creation Utility (RCU) requires EXECUTE privilege on DBMS_OUTPUT and DBMS_LOB. When you create a metadata repository using RCU, if PUBLIC does not have EXECUTE privilege on DBMS_OUTPUT and DBMS_LOB, the RCU user must have the privilege to grant EXECUTE privilege on DBMS_OUTPUT and DBMS_LOB to the MDS user.

To ensure that you have the correct privileges, login to RCU as a SYSDBA or as a DBA user who has EXECUTE privilege with GRANT OPTION on DBMS_OUTPUT and DBMS_LOB.

10.4.2 Notes for Using a Microsoft SQL Server Database for the MDS SchemaNote the following about using SQL Server as the database for MDS:

■ To create a metadata repository in SQL Server, set READ_COMMITTED_SNAPSHOT to ON for the hosting database. This enables the needed row versioning support. This feature can be enabled using the SQL command ALTER DATABASE, as in the following example:

ALTER DATABASE mds SET READ_COMMITTED_SNAPSHOT ON

■ You should use case-sensitive collation to support the case-sensitive semantics in the metadata repository. For example, if Latin1_General is used, select the SQL_Latin1_General_CP1_CS_AS collation using the following SQL command:

ALTER DATABASE mds COLLATE SQL_Latin1_General_CP1_CS_AS

In the example, the substring CS denotes case sensitivity. In you ned to configure your database for case-insensitive collation, use the CI substring.

31

■ When installed on SQL Server, Oracle Content Server 10g requires a database instance with case-insensitive collation. As a result, it cannot exist in the same SQL Server database instance as MDS. If you want to install both MDS and Oracle Content Server 10g, you must create a separate database instance with case-insensitive collation for installing the Oracle Content Server 10g schema.

■ There are some minor differences between an Oracle schema and a SQL Server schema. The length of the certain text fields are shorter for a SQL Server schema. For example, the full path name of the metadata in SQL Server is limited to 400 characters.

10.4.3 Notes for Using an IBM DB2 Database for the MDS SchemaNote the following about using DB2 as the database for MDS:

■ DB2 9.7 or later must be used for MDS repository to work properly.

Make sure that CUR_COMMIT is set to "ON", which is the default value for a newly installed DB2 9.7 database. This setting can be verified using following DB2 command:

db2 connect to your_database user admin_userdb2 "get db cfg" | grep -I commitCurently Committed (CUR_COMMIT) = ON

■ Set the lock timeout parameter of the database to a low value. Unlike Oracle databases, with DB2, if one user is updating a row, under some conditions, another user may be blocked when updating a different row and must wait until the transaction is committed or rolled back by the first user. To facilitate better concurrency, do not specify -1, which sets the lock timeout to infinity.

To query the lock timeout value for your DB2 database, use the following command:

db2 'get database config for database_alias' | grep -i timeout

If the value is too high, change it. For example, to change the lock timeout value to 180 seconds, use the following command:

db2 'update database config for database_alias using locktimout 180'

Choose a proper value for the locktimeout parameter. If a large value is used, it will affect system throughput, since the transaction has to wait a very long time before giving up. If the value is set too small, users will see many timeout exceptions if the database is processing many long running transactions.

■ Set the DB2 registry variables DB2_EVALUNCOMMITTED, DB2_SKIPINSERTED, and DB2_SJIPDELETED to OFF to avoid deadlock and locking issues. By default, they are set to OFF. To view the current registry variables setting, use the db2set -all command.

If they are not set to OFF, use the following commands:

db2set DB2_EVALUNCOMMITTED=OFFdb2set DB2_SKIPINSERTED=OFFdb2set DB2_SKIPDELETED=OFF

Restart the database server using the using db2stop and db2start commands.

■ DB2 may escalate a row lock to a table lock due to memory stress or lock usage. As the result, a user's transaction may be rolled back as a victim of deadlock or lock

32

timeout. To reduce lock escalation, you can increase the size of the MAXLOCKS and LOCKLIST configuration parameters. Use the following commands:

db2 'update database config for database_alias using locklist value'db2 'update database config for database_alias using maxlocks value'

■ The isolation level must be set to Currently Committed. To verify the setting, use the following command:

db2 'get database config for database_alias' | grep -i commit

To set the isolation level to Currently Committed, use the following command:

db2 'update database config for database_alias using CUR_COMMIT ON'

■ If the database transaction log is often full, increase the database configuration parameter to allow for a larger log file. A larger log file requires more space, but it reduces the need for applications to retry the operation. You should set the log file size to at least 10000 and the number of primary log files to at least 50. Use the following commands:

db2 'update database config for database_alias using LOGFILESIZ 10000'db2 'update database config for database_alias using LOGPRIMARY 50'\

■ If an MDS DB2 data source is created under an IBM WebSphere application server and the IBM DB2 JCC driver is chosen for the data source, the progressiveStreaming=2 property must be added to the property list of the data source. In effect, progressive streaming will be disabled. Without this property setting, MDS may run into issues in accessing document contents saved in a large object (LOB) column in the MDS repository.

10.4.4 Notes for Using a MySQL Database for the MDS SchemaNote the following about using MySQL as the database for MDS:

■ MySQL 5.5.14 or later must be used for the MDS repository to work properly.

■ You must select MySQL's Innodb engine as the database engine during database installation.

■ Set the lock timeout parameter of the database to a low value. To query the lock timeout value for your MySQL database, use the following command under the MySQL client:

show variables like 'innodb_lock_wait_timeout';

If the value is too high, change it. For example, to change the lock timeout value to 600 seconds at database level, use the following command:

set global innodb_lock_wait_timeout=600

The database will not remember this setting after it is rebooted. To keep the setting, make the corresponding changes in the my.cnf file.

Choose a proper value for the innodb_lock_wait_timeout parameter. If a large value is used, it will affect system throughput, since the transaction has to wait a very long time before giving up. If the value is set too small, users will see many timeout exceptions if database is processing many long running transactions.

33

■ MySQL provides several my.cnf templates under the mysql_home/support-files directory. To configure MySQL to work property with MDS, use my-large.cnf as the starting point for your my.cnf and make the following setting changes:

# The following stack memories must be set to a large enough value:thread_stack=1024k# Increase max_allowed_packet to allow for longer lobs.max_allowed_packet = 64M# max_sp_recursion_depth should be 64max_sp_recursion_depth=64 # Set the sql_mode to STRICT_TRANS_TABLES, so MySQL will report an error if a# string value is too long for the table field. By default, MySQL willsilently truncate a string value.# Also set NO_BACKSLASH_ESCAPES so strings like '\' will be accepted.sql_mode=STRICT_TRANS_TABLES,NO_BACKSLASH_ESCAPES # Set collation and character set for the server. character-set-server=utf8mb4collation-server=utf8mb4_bin # Transaction isloatoin has to be "READ-COMMITED".transaction-isolation=READ-COMMITTED

# Uncomment the following settings for InnoDB tablesinnodb_data_home_dir = /usr/local/mysql/datainnodb_data_file_path = ibdata1:10M:autoextendinnodb_log_group_home_dir = /usr/local/mysql/data# You can set .._buffer_pool_size up to 50 - 80 %# of RAM but beware of setting memory usage too highinnodb_buffer_pool_size = 256Minnodb_additional_mem_pool_size = 20M# Set .._log_file_size to 25 % of buffer pool sizeinnodb_log_file_size = 64Minnodb_log_buffer_size = 8Minnodb_flush_log_at_trx_commit = 1innodb_lock_wait_timeout = 50 # The following three parameters will ensure that MDS repository indexes# can be created successfully. innodb_file_per_table=trueinnodb_file_format=Barracudainnodb_large_prefix=true # If log-bin is turned on, the following parameter# must be on to ensure MDS triggers can be created successfully.log_bin_trust_function_creators=ONbinlog_format=mixed # In the [client] section of the configuration file, set the character set.default_character_set=utf8mb4

■ Oracle WebLogic Server 10.3.5 and earlier versions do not have MySQL JDBC driver configured. Use a later version of Oracle WebLogic Server if you want to choose a MySQL database as a data source.

■ Tips for starting MySQL Server using mysqld_safe: It is suggested to use the "--defaults-file=your_my.cnf" parameter when you start mysqld_safe, which will ensure a desired copy of my.cnf is used by your mySQL server. The

34

"--defaults-file" parameter has to be the first parameter of your mysqld_safe command. For example:

./mysqld_safe --defaults-file=/etc/my.cnf --user=mysql &

Be sure to set the access privileges of your my.cnf file to "-rw-r--r--". MySQL will ignore your my.cnf if other users have "write" access.

11 Repository Creation Utility (RCU) RequirementsThis section contains the following:

■ Section 11.1, "RCU Supported Platforms and Versions"

■ Section 11.2, "RCU Requirements for Oracle Databases"

■ Section 11.3, "RCU Requirements for Microsoft SQL Server Databases"

■ Section 11.4, "RCU Requirements for IBM DB2 Databases"

■ Section 11.5, "RCU Requirements for MySQL Databases"

11.1 RCU Supported Platforms and VersionsThis section contains the following:

■ Section 11.1.1, "RCU Supported Platforms"

■ Section 11.1.2, "Using the Correct RCU Version"

11.1.1 RCU Supported PlatformsRCU is available only on 32-bit x86 Linux and 32-bit Microsoft Windows operating system platforms. You can run RCU from these machines to connect to any certified local or remote Oracle, IBM DB2, MySQL, or Microsoft SQL Server database in order to create the schemas required by Fusion Middleware components. The database can be running on any operating system platform that is supported by that particular database.

For Release 11.1.1.4.0 and later, RCU can also be run on 64-bit x86 Linux and 64-bit Microsoft Windows operating systems. On 64-bit Linux operating systems, you must run the following command before starting RCU:

set linux32 bash

11.1.2 Using the Correct RCU VersionMake sure that the RCU version number matches the version number of the Oracle Fusion Middleware product you are installing and using. You may encounter problems if your RCU version number does not match your product version number.

For more information, refer to the Oracle Fusion Middleware Download, Installation, and Configuration Readme Files, which contain the correct RCU version to download for each Oracle Fusion Middleware release.

11.2 RCU Requirements for Oracle DatabasesThis section contains information pertaining to running RCU and creating schemas on Oracle databases. The following topics are covered:

■ Section 11.2.1, "General Oracle Database Requirements"

35

■ Section 11.2.2, "Setting the parallel_max_servers Parameter for the ODS Schema"

■ Section 11.2.3, "Setting the nls_length_semantics Parameter in your Oracle Database for Oracle Discoverer"

■ Section 11.2.4, "Applying Oracle Database Patch 8625762 for Oracle Business Process Management Suite"

■ Section 11.2.5, "Installing Oracle Text for Oracle Portal"

■ Section 11.2.6, "Using RCU 11g Release 1 (11.1.1.1.0) with Oracle Database 11g (11.2.0.1)"

■ Section 11.2.7, "Component-Specific Requirements for Oracle Databases"

11.2.1 General Oracle Database RequirementsRCU checks for the following on Oracle databases:

■ Database version is equal to or higher than 10.2.0.4.0 in 10g or equal to or higher than 11.1.0.7.0 in 11g.

■ Database user has SYSDBA role.

If you are creating schemas on an Oracle database, you must have SYSDBA privileges. For example, you can use the default database user SYS with SYSDBA privileges, or you must use a database user that has been granted the role of SYSDBA.

If you using a user other than SYS with SYSDBA privileges, you must grant the user permissions as follows:

GRANT execute on sys.dbms_lock to user_name with grant option

For example, if you have created and are using the user named system, you would use the following command to grant the necessary privileges to system:

GRANT execute on sys.dbms_lock to system with grant option

Refer to your Oracle database documentation for more information about database users and roles.

■ Character set is AL32UTF8.

If your database does not use the AL32UTF8 character set, you will see the following warning when running RCU:

The database you are connecting is with non-AL32UTF8 character set. Oraclestrongly recommends using AL32UTF8 as the database character set.

You can ignore this warning and continue using RCU.

■ The SHARED_POOL_SIZE is greater than or equal to 147456KB.

Note: If you are installing Oracle WebCenter Portal or Oracle Identity Management, you must configure your database to use AL32UTF8 character set encoding. If your database is not already configured to do so, refer to your database documentation for instructions. If you are installing a new database, be sure to configure your database to use AL32UTF8 character set encoding.

36

■ The SGA_MAX_SIZE is greater than or equal to 147456KB.

■ The DB_BLOCK_SIZE is greater than or equal to 8KB

11.2.2 Setting the parallel_max_servers Parameter for the ODS SchemaFor the Oracle Internet Directory (ODS) schema, set parallel_max_servers=1. This setting should be used for 11gR2 Oracle RAC systems with more than 32 CPUs.

After Oracle Internet Directory is up and running, you should set the parallel_max_servers parameter to a higher value. For more information, see "PARALLEL_MAX_SERVERS" in the Oracle Database VLDB and Partitioning Guide.

11.2.3 Setting the nls_length_semantics Parameter in your Oracle Database for Oracle DiscovererOracle Discoverer only supports schemas in a byte-mode database. The nls_length_semantics initialization parameter on the database where the schemas reside must be set to BYTE; setting this parameter to CHAR is not supported.

To check the values of this parameter using SQL*Plus, you can use the show parameters command:

prompt> sqlplus "sys/password as sysdba"SQL> show parameters nls_length_semantics

Replace password with the actual password for the SYS user.

Alternatively, you can check the values by querying the V$PARAMETER view:

prompt> sqlplus "sys/password as sysdba"SQL> select name,value from v$parameter;

11.2.4 Applying Oracle Database Patch 8625762 for Oracle Business Process Management SuiteIf you are installing Oracle Business Process Management Suite (part of Oracle SOA Suite) and you are using an Oracle database, you must apply patch 8625762 to avoid error ORA-03137 and OutOfMemory exception.

You can obtain the patch by specifying the patch ID in My Oracle Support (formerly MetaLink):

1. Access and log into My Oracle Support at the following location:

http://support.oracle.com/

2. Click the Patches & Updates link.

3. Enter the Patch ID or Number, then click Search. A Patch Search Results table appears.

4. Using the Release and Platform columns, find the desired patch, then click the associated Patch ID.

5. In the page that now appears, click the Download button in the right-hand column.

11.2.5 Installing Oracle Text for Oracle PortalOracle Text must be installed on your Oracle Database in order for the Oracle Portal schema to be configured. To check if Oracle Text is available on your database, use the following SQL command:

select count(*) from dba_views where owner = 'CTXSYS' and view_name = 'CTX_

37

VERSION';

The count should be greater than 0. Refer to your Oracle Database documentation for more information about Oracle Text.

11.2.6 Using RCU 11g Release 1 (11.1.1.1.0) with Oracle Database 11g (11.2.0.1)If you are using the version of RCU that is available in Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) with Oracle Database 11g (11.2.0.1), you will receive the following warning message:

The database you are connecting is not a supported version. Enter Databasewith version equal to or higher than 10.2.0.4.0 in 10g or version equal tohigher than 11.1.0.7.0 in 11g. Refer to the certification matrix forsupported DB versions.

This warning can be safely ignored and you can proceed with your RCU operations.

This warning will not appear in the version of RCU available in Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0).

11.2.7 Component-Specific Requirements for Oracle DatabasesTable 12 lists all of the supported schemas for Oracle databases, along with any component-specific prerequisite information that must be met for RCU to be able to create the schema. Refer to the Oracle Database Administrator's Guide to find instructions on how to modify database parameters.

When the tablespaces are created, RCU will automatically create them with the necessary tablespace sizes.

The "Oracle EBR?" column indicates whether or not the schema is also supported on Oracle Databases with Edition-Based Redefinition (EBR).

All requirements listed are the minimum requirements; please read them carefully as some components within the same product have different requirements. For example, if you are performing a full Oracle Identity Management installation including Oracle Identity Manager, then the open_cursors parameter must be set to 800. However, if you are installing Oracle Identity Management without Oracle Identity Manager, then open_cursors can be set to 500, which is required for Oracle Internet Directory.

Table 12 RCU Component-Specific Requirements for Oracle Databases

Component Schema Owner RequirementOracle EBR?

AS Common Schemas

Metadata Services prefix_MDS None. Yes

Audit Services prefix_IAU None. Yes

Audit Services for OES prefix_IAUOES None. Yes

Enterprise Scheduler Services

prefix_ESS None. Yes

Oracle Platform Security Services

prefix_OPSS None. Yes

Identity Management Schemas

Oracle Internet Directory

prefix_ODS processes: 500

open_cursors: 500

No

38

Oracle Identity Federation

prefix_OIF None. Yes

Oracle Identity Manager prefix_OIM open_cursors: 800 Yes

Oracle Access Manager prefix_OAM None. Yes

Oracle Adaptive Access Manager

prefix_OAAM processes: 250

sessions: 250

Oracle Database must be Enterprise Edition.

Yes

Oracle Adaptive Access Manager (Partition Support)

prefix_OAAM_PARTN processes: 500

sessions: 500

Oracle Database must be Enterprise Edition.

Yes

Authorization Policy Manager

prefix_APM None. Yes

Oracle Data Integrator Schemas

Master and Work Repository

prefix_ODI_REPO None. Yes

Oracle Business Intelligence Schemas

Business Intelligence Platform

prefix_BIPLATFORM None. Yes

WebCenter Content Schemas

Oracle Information Rights Management

prefix_ORAIRM None. No

Oracle WebCenter Content Server - Complete

prefix_OCS None. Yes

Oracle WebCenter Content Server - Search Only

prefix_OCSSEARCH None. Yes

Oracle WebCenter Content: Records

prefix_URMSERVER None. Yes

Oracle WebCenter Content: Imaging

prefix_IPM None. Yes

WebLogic Communication Services Schemas

Presence prefix_ORASDPXDMS None. No

SIP Infrastructure Subscriber Data Service

prefix_ORASDPSDS None. No

SIP Infrastructure Location Service

prefix_ORASDPLS None. No

SOA and BPM Infrastructure Schemas

Oracle BAM prefix_ORABAM None. No

SOA Infrastructure prefix_SOAINFRA processes: 200 Yes

Table 12 (Cont.) RCU Component-Specific Requirements for Oracle Databases


39

11.3 RCU Requirements for Microsoft SQL Server DatabasesThis section contains information pertaining to running RCU and creating schemas on Oracle databases. The following topics are covered:

■ Section 11.3.1, "General Microsoft SQL Server Database Requirements"

■ Section 11.3.2, "Creating Oracle WebCenter Portal Schemas on Microsoft SQL Server Databases"

■ Section 11.3.3, "Component-Specific Requirements for Microsoft SQL Server Databases"

11.3.1 General Microsoft SQL Server Database RequirementsRCU checks for the following on Microsoft SQL Server databases:

■ Database version is equal to or higher than 2005.

■ Database user (db_owner) should have SYSDBA or DBA privileges.

User Messaging Server (ORASDPM)

prefix_ORASDPM None. Yes

WebCenter Portal Schemas

Spaces and Services prefix_WEBCENTER processes: 300 Yes

Discussions prefix_DISCUSSIONS None. Yes

Portlet Producers prefix_PORTLET The database user, in connection with the target-DB, must have rdbms-implementation equivalent of:

■ Create/Modify User/Schema

■ Create/Modify Table

■ Create/Modify Sequence

■ Create/Modify Index

■ Grant Resource Privilege

■ Grant Connect privilege

Yes

Activity Graph and Analytics

prefix_ACTIVITIES None. Yes

Portal and Business Intelligence Schemas

Oracle Portal prefix_PORTAL Portal schema name cannot be longer then 30 characters.

No

Oracle Discoverer prefix_DISCOVERER None. No

Enterprise Performance Management Schemas

Registry prefix_EPM None.

Table 12 (Cont.) RCU Component-Specific Requirements for Oracle Databases


40

11.3.2 Creating Oracle WebCenter Portal Schemas on Microsoft SQL Server DatabasesIf you are creating the schemas in a Microsoft SQL Server database, a database instance must be created prior to running RCU. The MDS schema has some specific requirements; see "Databases Supported by MDS" in Oracle Fusion Middleware Administrator's Guide for more information.

In addition, the MDS schema requires a database with case sensitive collation, while Oracle Content Server 10g requires a database instance with case insensitive collation.

If you wish to install Oracle Content Server 10g on a SQL Server database, you will need to create two database instances (one with case sensitive collation and one with case insensitive collation) and run RCU twice: once to install the Oracle Content Server 10g schemas into the database instance with case insensitive collation, and a second time to install all of the other WebCenter Portal schemas into the database instance with case sensitive collation.

11.3.3 Component-Specific Requirements for Microsoft SQL Server DatabasesTable 13 lists all of the supported schemas for Microsoft SQL Server databases, along with any component-specific prerequisite information that must be met for RCU to be able to create schema.


Table 13 RCU Component-Specific Requirements for Microsoft SQL Server Databases

Component Schema Owner Requirement

AS Common Schemas

Metadata Services prefix_MDS See Section 10.4.2, "Notes for Using a Microsoft SQL Server Database for the MDS Schema".


Master and Work Repository

prefix_ODI_REPO None.

Business Intelligence Schemas

Business Intelligence Platform

prefix_BIPLATFORM None.


Oracle Information Rights Management

prefix_ORAIRM None.

Oracle WebCenter Content Server - Complete

prefix_OCS Database must be configured to use case sensitive collation.

See Section 10.4.2, "Notes for Using a Microsoft SQL Server Database for the MDS Schema" for more information.

Oracle WebCenter Content: Records

prefix_URMSERVER None.

Oracle WebCenter Content: Imaging

prefix_IPM None.

SOA Infrastructure Schemas

41

11.4 RCU Requirements for IBM DB2 DatabasesThis section contains information you need to know about configuring IBM DB2 databases for schema creation. The following topics are covered:

■ Section 11.4.1, "Creating Database Operating System Users"

■ Section 11.4.2, "Size Limit for Schema Prefixes (Linux Only)"

■ Section 11.4.3, "Configuring Your DB2 Database"

■ Section 11.4.4, "RCU Supported Schemas for IBM DB2 Databases"

SOA Infrastructure prefix_SOAINFRA The read_committed_snapshot option must be turned on, and the database must be configured to use case sensitive collation.


User Messaging Service prefix_ORASDPM The read_committed_snapshot option must be turned on, and the database must be configured to use case sensitive collation.


WebCenter Portal Schemas

Spaces and Services prefix_WEBCENTER The read_committed_snapshot option must be turned on, and the database must be configured to use case sensitive collation.


Discussions prefix_DISCUSSIONS The read_committed_snapshot option must be turned on, and the database must be configured to use case sensitive collation.


Portlet Producers prefix_PORTLET The read_committed_snapshot option must be turned on, and the database must be configured to use case sensitive collation.


Activity Graph and Analytics

prefix_ACTIVITIES Database must be configured to use case insensitive collation.


Table 13 (Cont.) RCU Component-Specific Requirements for Microsoft SQL Server


42

11.4.1 Creating Database Operating System UsersIBM DB2 authenticates its database users using equivalent operating system users. Therefore, prior to running RCU, one operating system user must be created for each schema. The operating system user name must match the schema owner name and must contain only lowercase letters; no all-uppercase or mixed-case names are allowed. For example:

■ If you create a schema named DEV_SOA on an IBM DB2 database running on a Linux operating system, then you must also create the operating system user dev_soa (matching name, all lowercase letters).

■ If you create a schema named DEV_SOAINFRA on an IBM DB2 database running on a Windows operating system, then you must also create the operating system user dev_soainfra (matching name, all lowercase letters).

11.4.2 Size Limit for Schema Prefixes (Linux Only)IBM DB2 has an eight character limit for schema names. Therefore, the schema names are shortened to a maximum of three characters (plus schema prefix and underscore), making the maximum size of the user defined prefix four characters.

For example, on IBM DB2 databases running on a Windows operating system, and all supported Oracle and Microsoft SQL Server databases, the SOA Infrastructure schema you create might be called DEV_SOAINFRA. However, on an IBM DB2 database running on a Linux operating system, this schema name must be shortened to DEV_SOA.

11.4.3 Configuring Your DB2 DatabaseFor important information about configuring your IBM DB2 database, refer to Section 10.4.3, "Notes for Using an IBM DB2 Database for the MDS Schema".

11.4.4 RCU Supported Schemas for IBM DB2 DatabasesNot all of the schemas that are supported in Oracle and Microsoft SQL Server databases are supported on IBM DB2 databases. Table 14 shows the schemas that are supported in IBM DB2 databases.


Note: Table 14 lists the schema names for an IBM DB2 database running on a Linux operating system, due to a restriction on the number of characters (including the prefix) in the schema name. For more information, see Section 11.4.2, "Size Limit for Schema Prefixes (Linux Only)".

If you are creating schemas in an IBM DB2 database running on a Windows operating system, the schema names are the same as the ones for a Microsoft SQL Server or Oracle database.

See Section 11.4.1, "Creating Database Operating System Users" for important information about creating the operating system users.

43

11.5 RCU Requirements for MySQL DatabasesNot all schemas are supported on MySQL databases. Table 15 shows the schemas that are supported in MySQL databases.


Table 14 Supported Schemas for IBM DB2 Databases

ComponentIBM DB2 Schema Name

Operating System User Name

AS Common Schemas

Metadata Services prefix_MDS prefix_mds

SOA and BPM Infrastructure Schemas

SOA Infrastructure prefix_SOA prefix_soa

User Messaging Service prefix_UMS prefix_ums

Oracle WebCenter Portal Schemas

Spaces and Services prefix_WC prefix_wc

Portlet Producers prefix_PT prefix_pt

Discussions prefix_DS prefix_ds

Activity Graph and Analytics prefix_AG prefix_ag

Oracle Business Intelligence Schemas

Business Intelligence Platform prefix_BI prefix_bi


Master and Work Repository prefix_ODI prefix_odi


Oracle Information Rights Management prefix_IRM prefix_irm

Oracle WebCenter Content Server prefix_OCS prefix_ocs

Oracle WebCenter Content: Records prefix_URM prefix_urm

Oracle WebCenter Content: Imaging prefix_IPM prefix_ipm

Table 15 RCU Component-Specific Requirements for MySQL Databases


AS Common Schemas

Metadata Services prefix_MDS See Section 10.4.4, "Notes for Using a MySQL Database for the MDS Schema".


Master and Work Repository prefix_ODI_REPO

44

12 Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle SupportOracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Copyright © 2012 Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

ORACLE SOA System Requirements

Documents

sp levels

systemrootsystem32drivers

ctxaccamp

ux 11i v3

ux 11i v2

microsoft

oracle fusion

oracle business