3 Preparing to Install Oracle Service Bus

This chapter provides information you should review before installing Oracle Service Bus 11g. It includes the following topics:

3.1 Oracle Fusion Middleware Certification

The Oracle Fusion Middleware Supported System Configurations document provides certification information for Oracle Fusion Middleware, including supported installation types, platforms, operating systems, databases, JDKs, and third-party products related to Oracle Service Bus 11g Release 1 (11.1.1.3).

You can access the Oracle Fusion Middleware Supported System Configurations document by searching the Oracle Technology Network (OTN) web site:

http://www.oracle.com/technology/

3.2 System Requirements

This topic describes the system requirements for installing Oracle Service Bus 11g Release 1 (11.1.1.3) and includes the following sections:

3.2.1 Most Recent Information

The information in this topic is current at the time of publication. For the most recent information, refer to the Oracle Fusion Middleware System Requirements, Prerequisites, and Specification document, which contains information related to hardware, software, disk space, memory, system library, and patch requirements.

You can access the Oracle Fusion Middleware System Requirements, Prerequisites, and Specification document by searching the Oracle Technology Network (OTN) web site:

http://www.oracle.com/technology/

3.2.2 Installer Startup Requirements

When you start the Installer, it checks for the requirements listed in Table 3-1. The Installer will notify you if any requirements are not met.

Table 3-1 Installer Startup Requirements

Category Minimum or Accepted Value

Platform

UNIX:

  • Solaris 9, Solaris 10

  • HP-UX 11i (11.23), HP-UX 11i (11.31)

  • Oracle Enterprise Linux 4, Oracle Enterprise Linux 5, Red Hat Linux 4, Red Hat Linux 5, SUSE 10

  • IBM AIX 5.3, IBM AIX 6.1

Windows:

  • Windows XP SP2 (Win32 platforms only), Windows 2003, Windows 2008, Windows Vista

CPU Speed

At least 300 MHZ

Temp Space

At least 500 MB

Swap Space

At least 500 MB

Monitor

At least 256 colors


3.2.3 Memory Requirements

Table 3-2 lists the minimum memory requirements to install Oracle Service Bus 11g Release 1 (11.1.1.3):

Table 3-2 Minimum Memory Requirements

Operating System Minimum Physical Memory Minimum Available Memory

Linux

2 GB

1 GB

UNIX

2 GB

1 GB

Microsoft Windows

2 GB

1 GB


The specific memory requirements for your Oracle Service Bus 11g Release 1 (11.1.1.3) deployment depends on which components, or combination of components, you install. The following list identifies memory requirements for various components. Use the list as guidelines for determining the memory requirements specific to your deployment:

  • WebLogic Administration Server: 750 MB

3.3 Installing and Configuring Java Access Bridge (Windows Only)

If you are installing Oracle Service Bus on a Windows operating system, 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:

  1. Download Java Access Bridge from the following URL:

    http://java.sun.com/javase/technologies/accessibility/accessbridge/
    
  2. Install Java Access Bridge.

  3. Copy access-bridge.jar and jaccess-1_4.jar from your installation location to the jre\lib\ext directory.

  4. Copy the WindowsAccessBridge.dll, JavaAccessBridge.dll, and JAWTAccessBridge.dll files from your installation location to the jre\bin directory.

  5. Copy the accessibility.properties file to the jre\lib directory.

3.4 Installing Oracle WebLogic Server and Creating the Oracle Middleware Home

Before you can install Oracle Service Bus 11g Release 1 (11.1.1.3), you must install Oracle WebLogic Server and create the Oracle Middleware Home directory.

Note:

If you wish to use the rich IDE for Oracle Service Bus development, you must install Oracle Enterprise Pack for Eclipse (OEPE), which is bundled in the Oracle WebLogic Server Installer. You are prompted to enter the name and location of your Oracle Enterprise Pack for Eclipse (OEPE) home while installing the custom IDE component of Oracle Service Bus.

Complete the following steps to install Oracle WebLogic Server and create the Oracle Middleware Home directory. You can refer to the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server for complete information about installing Oracle WebLogic Server.

  1. Insert the Oracle WebLogic Server CD-ROM or download the Oracle WebLogic Server Installer from the following URL:

    http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html
    
  2. Locate the appropriate executable file for your system, such as:

    • oepe111150_wls1033_linux32.bin for 32-bit Linux systems - WebLogic Server with Oracle Enterprise Pack for Eclipse

    • oepe111150_wls1033_win32.exe for 32-bit Windows systems - WebLogic Server with Oracle Enterprise Pack for Eclipse

    • wls1033_generic.jar for all 64-bit platforms - WebLogic Server without Oracle Enterprise Pack for Eclipse

    • wls1033_linux32.bin for 32-bit Linux systems - WebLogic Server without Oracle Enterprise Pack for Eclipse

    • wls1033_win32.exe for 32-bit Windows systems - WebLogic Server without Oracle Enterprise Pack for Eclipse

    The 32-bit executable files are bundled with the appropriate JDK version. If you use the 64-bit installer, you will need to invoke the installer with a supported JDK for your platform. This JDK must be installed on your system before you install Oracle WebLogic Server. Refer to the Oracle Fusion Middleware certification document for a list of supported JDKs for your platform:

    http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
    
  3. Run the Oracle WebLogic Server Installer directly from the CD-ROM, or copy the file to your local system and run it locally.

    For example, on 32-bit systems:

    Linux:

    ./wls1033_linux32.bin
    

    Windows:

    wls1033_win32.exe
    

    For example, on 64-bit systems:

    UNIX:

    JAVA_HOME/bin/java -jar wls1033_generic.jar
    

    Solaris Sparc with Sun JDK 64-bit and HP-UX with 64-bit JDK:

    JAVA_HOME/bin/java -d64 -jar wls1033_generic.jar
    

    Windows:

    JAVA_HOME\bin\java -jar wls1033_generic.jar
    

    For 64-bit installations:

    • Before running the installer, set the DISPLAY environment variable on your system.

    • Replace JAVA_HOME with the installation location of the supported JDK you installed for your platform.

    • Use the -d64 flag when using 32/64-bit hybrid JDKs (such as the HP JDK for HP-UX and SUN JDK for Solaris SPARC).

    • Execute JAVA_HOME/bin/java -version (or JAVA_HOME/bin/java -d64 -version on 32/64-bit hybrid JDKs) to ensure that your JAVA_HOME refers to a 64-bit JDK.

    Note:

    After you start the Oracle WebLogic Server Installer, the Welcome screen appears.
  4. Click Next. The Choose Middleware Home Directory screen appears.

  5. Select Create a new Middleware Home and identify the desired location for your new Middleware Home directory, which is the top-level directory for all Oracle Fusion Middleware products. The WebLogic Home directory will be created inside the Middleware Home directory.

    Note:

    If the Middleware Home directory already exists on your system, it must be an empty directory. Do not enter any special characters in the name of the Middleware Home directory.

    Click Next. The Register for Security Updates screen appears.

  6. Select whether or not you want to receive the latest product and security updates. If you choose not to receive anything, you will be asked to verify your selection before continuing.

    Click Next. The Choose Install Type screen appears.

  7. Select the Typical install type and click Next. The Choose Product Installation Directories screen appears.

  8. Specify the desired location for your WebLogic Server Home directory and click Next.

    If you are installing Oracle WebLogic Server on a UNIX system, the Installation Summary screen appears. Go to step 9 now.

    If you are installing Oracle WebLogic Server on a Windows system, the Choose Shortcut Location screen appears. Specify a location where you want Windows to create a shortcut to Oracle products and click Next. The Installation Summary screen appears.

  9. Click Next on the Installation Summary screen.

    The Installation Progress screen appears.

  10. Click Next. The Installation Complete screen appears.

  11. De-select Run Quickstart and click Done to exit the Installer.

Notes:

  • A separate home for Oracle Enterprise Pack for Eclipse (OEPE) is created under your new Middleware Home directory.

  • The same user that installed Oracle WebLogic Server must install Oracle Service Bus.

  • Do not log in to the Oracle WebLogic Server Administration Console during Oracle Service Bus installation.

3.5 Completing Database Requirements

This section discusses database requirements, including the schemas, for installing Oracle Service Bus in production and development environments.

Database schemas are not mandatory for installing Oracle Service Bus. You must create and load schemas if you wish to use the Reporting features in Oracle Service Bus or the Oracle Web Services Manager policies.

To Use Reporting Features in Oracle Service Bus

In a production environment, you must run the Repository Creation Utility (RCU) to create the database tables required for the Reporting feature. Specifically, you must create and load the SOA Infrastructure schema under SOA and BPM Infrastructure. By default, when you select the SOA Infrastructure schema in RCU, the following schemas are also selected:

  • User Messaging Service under SOA and BPM Infrastructure

  • Metadata Services under AS Common Schemas

In a development environment, you can use Derby, an evaluation database included in your Oracle WebLogic Server installation. In this case, you are not required to use RCU to create and load schemas if the Oracle Web Services Manager functionality for Oracle Service Bus is not required. Be sure to select Evaluation Database if you are using the Custom installation option to install Oracle WebLogic Server. If you are using the Typical installation option, the Evaluation Database is installed, by default. Reporting tables for Oracle Service Bus are created in the Evaluation Database when the server starts up for the first time. If you are using Oracle Fusion Middleware Configuration Wizard to create the Oracle Service Bus domain, configure the database type reporting as Derby, and set the password appropriately. You can ignore the Test Connections action in the wizard because the Evaluation Database starts only when Oracle WebLogic Server is started.

Tip:

After installing Oracle WebLogic Server, verify that a directory named derby exists in the following directory:
  • On Windows: <Middleware_Home>\wlserver_10.3\common

  • On UNIX: <Middleware_Home>/wlserver_10.3/common

To Use Oracle Web Services Manager Policies with Oracle Service Bus

In both production and development environments, you must run the Repository Creation Utility (RCU) to create the schema required for Oracle Web Services Manager.

Specifically, ensure that you create and load the Metadata Services schema under AS Common Schemas.

Note:

Repository Creation Utility (RCU) is compatible with Oracle databases. If you do not have an Oracle database installed, you must install an Oracle database before creating and loading database schemas in RCU.

3.5.1 Installing Oracle Database

You must install an Oracle Database if you wish to use RCU to create schemas. The database must be up and running to create and load the required schemas. The database does not have to be on the same system where you are installing Oracle Service Bus.

Note:

You can locate the most recent information about supported databases by referring to the "Oracle Fusion Middleware Certification" topic in this chapter.

Table 3-3 lists the databases requirements for RCU at the time of publication:

Table 3-3 RCU Database Requirements

Category Minimum or Accepted Value

Version

Oracle Database 11g (11.1.0.7 or later for non-XE database) using the AL32UTF8 character set.

Shared Pool Size

147456 KB

SGA Maximum Size

147456 KB

Block Size

8 KB

Processes

500


Note:

After installing the Oracle 11g database, you must complete the following steps:
  1. Log in to the database as the sys (default) user.

  2. Run the following scripts:

    alter system set session_cached_cursors=100 scope=spfile;

    alter system set processes=500 scope=spfile;

  3. Bounce the database and continue with the installation of Repository Creation Utility (RCU) and loading of schemas.

3.6 Creating Database Schema Using the Repository Creation Utility (RCU)

You must create and load the appropriate Oracle Fusion Middleware schema in your database.

You create and load Oracle Fusion Middleware schema in your database using the RCU, which is available in the Oracle Fusion Middleware 11g Release 1 (11.1.1) release media and on the Oracle Technology Network (OTN) web site. You can access the OTN web site at:

http://www.oracle.com/technology/index.html

Note:

RCU is available only on Linux and Windows platforms. Use the Linux RCU to create schemas on supported UNIX databases. Use Windows RCU to create schemas on supported Windows databases.

When you run RCU, create and load only the schemas for using the Reporting features and Oracle Web Services Manager policies. For more information, see Completing Database Requirements. Do not select any other schema available in RCU.

Note:

When you create schema, be sure to remember the schema owner and password that is shown in RCU.

If you are creating schemas on databases with Oracle Database Vault installed, note that statements such as CREATE USER, ALTER USER, DROP USER, CREATE PROFILE, ALTER PROFILE, and DROP PROFILE can only be issued by a user with the DV_ACCTMGR role. SYSDBA can issue these statements by modifying the Can Maintain Accounts/Profiles rule set only if it is allowed.

3.7 Optional Environment-Specific Preparation

This topic describes optional environment-specific tasks you may want to perform before installing Oracle Service Bus 11g Release 1 (11.1.1.3). This topic includes the following sections:

3.7.1 Using Symbolic Links

If you want to install Oracle Service Bus using symbolic links, you must create them before installation. For example, you could create symbolic links for the installation by executing the following commands:

prompt> mkdir /home/basedir
prompt> ln -s /home/basedir /home/linkdir

Then, when you run the Installer to install Oracle Service Bus, you can specify /home/linkdir as the Oracle Home.

After installation, you cannot create symbolic links to the Oracle Home. Also, you cannot move the Oracle Home to a different location and create a symbolic link to the original Oracle Home.

3.7.2 Installing Oracle Service Bus on DHCP Hosts

If you plan to install Oracle Service Bus components on a DHCP server, you must ensure the Installer can resolve host names. This may require editing the /etc/hosts file on UNIX systems, and installing a loopback adapter on Windows systems. The following information provides general examples, you should alter these examples to make them specific to your environment.

On UNIX systems:

Configure the host to resolve host names to the loopback IP address by modifying the /etc/hosts file to contain the following entries. Replace the variables with the appropriate host and domain names:

127.0.0.1 hostname.domainname hostname
127.0.0.1 localhost.localdomain localhost

Confirm the host name resolves to the loopback IP address by executing the following command:

ping hostname.domainname

On Windows systems:

Install a loopback adapter on the DHCP server, which assigns a local IP address to your system.

After installing the adapter, add a line to the %SYSTEMROOT%\system32\drivers\etc\hosts file immediately after the localhost line and using the following format, where IP_address represents the local IP address of the loopback adapter:

IP_address   hostname.domainname   hostname

3.7.3 Installing Oracle Service Bus on a Multihomed System

You can install Oracle Service Bus components on a multihomed system. A multihomed system is associated with multiple IP addresses, typically achieved by having multiple network cards on the system. Each IP address is associated with a host name and you can create aliases for each host name.

The Installer retrieves the fully qualified domain name from the first entry in /etc/hosts file on UNIX, or the%SYSTEMROOT%\system32\drivers\etc\hosts file on Windows. For example, if your file looks like the following, the Installer retrieves myhost1.mycompany.com for configuration:

127.0.0.1 localhost.localdomain localhost
10.222.333.444 myhost1.mycompany.com myhost1
20.222.333.444 devhost2.mycompany.com devhost2

For specific network configuration of a system component, refer to the individual component's documentation listed in "Related Documents" for more information.