Comparing Oracle SOA Suite on OC4J and Oracle WebLogic Server

Oracle SOA Suite, WebCenter, and ADF Information for 10g Users 3-3 Figure 3–2 Oracle SOA Suite Installed on an OC4J Instance and an Oracle WebLogic Server Domain

3.2.2 Comparing the Oracle SOA Suite Directory Structure on OC4J and Oracle WebLogic Server

When you install and configure the Oracle SOA Suite, you create a Oracle WebLogic Server domain that has been extended to support the SOA system components. The resulting files on disk consist of the SOA domain directory structure, as well as the SOA Oracle home, which contains the SOA component binary and support files, and the Oracle Common home, which contains Oracle Enterprise Manager Fusion Middleware Control and the Java Required Files JRF. The SOA Oracle home must be installed inside the Middleware home; the Oracle comon is installed automatically. This is in contrast to the single Oracle home that was created during an Oracle Application Server 10g Release 3 10.1.3 installation. Figure 3–3 shows the directory structure that results from installing and configuring the Oracle SOA Suite domain. Figure 3–3 The Directory Structure of an Oracle Fusion Middleware SOA Suite Installation

3.2.3 Upgrading an Oracle SOA Suite Enterprise Deployment

The instructions in this guide provide the steps for upgrading a basic Oracle SOA Suite environment. After reviewing the content of this guide, you should be able to transfer this knowledge to a more complex production environment. 3-4 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF For specific information about setting up a production environment that takes advantage of clustering and high availability, refer to the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite. For an overview of the high-level tasks you must perform when upgrading an enterprise deployment, see Planning an Enterprise Deployment in the Oracle Fusion Middleware Upgrade Planning Guide. 3.2.4 About Oracle BAM and Oracle B2B in Oracle Application Server 10g and Oracle Fusion Middleware 11g Unlike the other Oracle SOA Suite components, Oracle BAM 10g and Oracle B2B were installed an configured separately. Oracle BAM was supported on the Microsoft platform only, and Oracle B2B was installed on a separate server from the other Oracle SOA Suite 10g components. For Oracle Fusion Middleware 11g, Oracle BAM 11g and Oracle B2B 11g are integrated with the other Oracle SOA Suite components. Oracle BAM can be deployed as part of the same Oracle WebLogic Server domain, and Oracle B2B is installed and configured automatically with the other Oracle SOA Suite components.

3.3 Information for Oracle WebCenter Users

Oracle Application Server 10g Release 3 10.1.3 provided installation options that allowed you to install and configure the WebCenter system components as part of an Oracle Application Server install. You could then use Oracle JDeveloper to develop and deploy WebCenter applications on the OC4J instances where the WebCenter system components were installed. Similarly, for Oracle Fusion Middleware, you can install and configure a Oracle WebLogic Server domain that supports the WebCenter system components. Refer to the following sections for more information: ■ Comparing Oracle WebCenter on OC4J and Oracle WebLogic Server ■ Comparing the Oracle WebCenter Directory Structure on OC4J and Oracle WebLogic Server

3.3.1 Comparing Oracle WebCenter on OC4J and Oracle WebLogic Server

Figure 3–4 shows the how the Oracle WebCenter system components are installed as part of an OC4J 10g instance and compares that to how the Oracle WebCenter components are installed on a managed server when you install and configure the Oracle Fusion Middleware 11g. Note that the WebCenter system components require a set of WebCenter schemas, which you install using the Repository Creation Utility RCU. For more information about the schemas installed by RCU, refer to the Oracle Fusion Middleware Repository Creation Utility User’s Guide.