Oracle® Fusion Middleware

Installation Guide for Oracle Service Bus

11g Release 1 (11.1.1.3)

E15017-01

April 2010

Oracle Fusion Middleware Installation Guide for Oracle Service Bus, 11g Release 1 (11.1.1.3)

E15017-01

Copyright © 2001, 2010, Oracle and/or its affiliates. All rights reserved.

Primary Author:  Gururaj B.S.

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 software or related documentation 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 USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software 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 which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software 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.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Understanding Oracle Service Bus 11g Release 1 (11.1.1.3)

- 1.1 What is Oracle Fusion Middleware?

- 1.2 Oracle Service Bus

- 1.3 Prerequisites for installing Oracle Service Bus

- 1.3.1 Oracle WebLogic Server

- 1.3.2 Oracle Coherence

- 1.3.3 Oracle Enterprise Pack for Eclipse

- 1.4 What Does This Guide Cover?

- 1.4.1 Using This Guide

- 1.4.2 Upgrading to 11g Release 1 (11.1.1.3)

- 1.4.3 Installing 11g Release 1 (11.1.1.3) for High Availability

2 Understanding the Oracle Service Bus 11g Release 1 (11.1.1.3) Installation

- 2.1 Overview of Installation Process

- 2.2 Installing Oracle Service Bus and Creating a Domain in Development Environments

- 2.3 Installing Oracle Service Bus and Creating a Domain in Production Environments

- 2.4 Additional 11g Release 1 (11.1.1.3) Installation and Upgrade Information

- 2.4.1 Upgrading to 11g Release 1 (11.1.1.3)

- 2.4.2 Installing 11g Release 1 (11.1.1.3) for High Availability

- 2.5 Silent Installation

- 2.6 Understanding Oracle Service Bus Installation Types

- 2.6.1 Typical Installation

- 2.6.2 Custom Installation

- 2.7 Understanding the State of Oracle Service Bus Components After Installation

- 2.7.1 Default SSL Configurations

- 2.7.2 Administrator Server Password

- 2.8 Understanding the Directory Structure After Installation

- 2.9 Understanding Oracle WebLogic Server Administration Domain Options

- 2.9.1 Create New Domain

- 2.9.2 Extend Existing Domain

- 2.9.3 Expand Cluster

- 2.10 Oracle Service Bus Domain Configuration Scenarios

- 2.11 Screens in Oracle Fusion Middleware Configuration Wizard

3 Preparing to Install Oracle Service Bus

- 3.1 Oracle Fusion Middleware Certification

- 3.2 System Requirements

- 3.2.1 Most Recent Information

- 3.2.2 Installer Startup Requirements

- 3.2.3 Memory Requirements

- 3.3 Installing and Configuring Java Access Bridge (Windows Only)

- 3.4 Installing Oracle WebLogic Server and Creating the Oracle Middleware Home

- 3.5 Completing Database Requirements

- 3.5.1 Installing Oracle Database

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

- 3.7 Optional Environment-Specific Preparation

- 3.7.1 Using Symbolic Links

- 3.7.2 Installing Oracle Service Bus on DHCP Hosts

- 3.7.3 Installing Oracle Service Bus on a Multihomed System

4 Performing Common Installation Tasks

- 4.1 Starting an Installation

- 4.2 Identifying Installation Directories

- 4.2.1 Oracle Middleware Home Location

- 4.2.2 Oracle Home Directory

- 4.2.3 Oracle Common Directory

- 4.2.4 WebLogic Server Directory

- 4.2.5 Oracle WebLogic Domain Directory

- 4.3 Creating and Starting Managed Servers on a Remote Machine

- 4.4 Completing an Installation

- 4.5 Locating Installation Log Files

5 Installing and Configuring Oracle Service Bus 11g

- 5.1 Prerequisites

- 5.2 Installing the Oracle Service Bus 11g Software

- 5.2.1 Components Installed

- 5.2.2 Dependencies

- 5.2.3 Procedure

- 5.3 Creating a WebLogic Domain

- 5.4 Creating a WebLogic Domain with Only Oracle Service Bus 11g

- 5.4.1 Appropriate Installation Environment

- 5.4.2 Components Installed

- 5.4.3 Dependencies

- 5.4.4 Procedure

- 5.5 Installing the Latest Version of Oracle SOA Suite

- 5.5.1 Obtaining the Latest Oracle WebLogic Server and Oracle SOA Suite

- 5.5.2 Installing Oracle WebLogic Server and Creating the Middleware Home

- 5.5.3 Installing Oracle SOA Suite 11.1.1.2.0

- 5.5.4 Patching the Software

- 5.6 Creating a WebLogic Domain with Oracle Service Bus 11g and Oracle SOA Suite in the Same Domain

- 5.6.1 Appropriate Installation Environment

- 5.6.2 Components Installed

- 5.6.3 Dependencies

- 5.6.4 Procedure

- 5.7 Extending an Oracle Service Bus WebLogic Domain to Support Oracle SOA Suite

- 5.7.1 Appropriate Installation Environment

- 5.7.2 Components Installed

- 5.7.3 Dependencies

- 5.7.4 Procedure

- 5.8 Extending an Oracle SOA Suite WebLogic Domain to Support Oracle Service Bus

- 5.8.1 Appropriate Installation Environment

- 5.8.2 Components Installed

- 5.8.3 Dependencies

- 5.8.4 Procedure

- 5.9 After Creating Oracle Service Bus 11g Domain

- 5.10 Verifying Oracle Service Bus 11g Installation and Domain Configuration

- 5.10.1 Verifying the Oracle Service Bus Directory Structure

- 5.11 Start Menu Commands on Windows

- 5.12 Getting Started with Oracle Service Bus 11g After Installation

6 Performing Silent Installations

- 6.1 What is a Silent Installation?

- 6.2 Before Performing a Silent Installation

- 6.2.1 UNIX Systems: Creating the oraInst.loc File

- 6.2.2 Windows Systems: Creating the Registry Key

- 6.3 Creating Response Files

- 6.3.1 Securing Your Silent Installation

- 6.4 Performing a Silent Installation

- 6.5 Installer Command Line Parameters

A Troubleshooting the Installation

- A.1 General Troubleshooting Tips

- A.2 Installation Log Files

- A.3 Need More Help?

B Deinstalling and Reinstalling Oracle Service Bus

- B.1 Deinstalling Oracle Service Bus 11g Release 1 (11.1.1.3)

- B.1.1 Deinstalling Oracle Service Bus Oracle Home

- B.1.2 Deinstalling Oracle Common Home

- B.2 Reinstalling Oracle Service Bus 11g Release 1 (11.1.1.3)

C Oracle Service Bus Software Installation Screens

- C.1 Welcome Screen

- C.2 Select Installation Type Screen

- C.3 Prerequisite Checks Screen

- C.4 Select Components Screen

- C.5 Specify Installation Location Screen

- C.6 Installation Summary Screen

- C.7 Install Progress Screen

- C.8 Installation Completed Screen

D WebLogic Domain Configuration Screens

- D.1 Welcome

- D.2 Select a WebLogic Domain Directory

- D.3 Select Domain Source

- D.4 Select Extension Source

- D.5 Specify Domain Name and Location

- D.6 Configure Administrator User Name and Password

- D.7 Configure Server Start Mode and JDK

- D.8 Configure JDBC Component Schema

- D.9 Test Component Schema

- D.10 Select Optional Configuration

- D.11 Configure the Administration Server

- D.12 Select JMS Distributed Destination Type

- D.13 Configure Managed Servers

- D.14 Configure Clusters

- D.15 Assign Servers to Clusters

- D.16 Configure Machines

- D.17 Assign Servers to Machines

- D.18 Target Deployments to Clusters or Servers

- D.19 Target Services to Clusters or Servers

- D.20 Configure RDBMS Security Store Database

- D.21 Configure JMS File Stores

- D.22 Configuration Summary

E Oracle Service Bus Deinstallation Screens

- E.1 Welcome Screen

- E.2 Deinstall Oracle Home Screen

- E.3 Deinstallation Progress Screen

- E.4 Deinstallation Completed Screen

Index

Preface

This preface includes the following topics:

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

Audience

This document is intended for users of Oracle Service Bus.

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.

Related Documents

For more information, see the following documents in the Oracle Fusion Middleware Release 7.0 documentation set or in the Oracle Other Product Two Release 6.1 documentation set:

- Oracle Fusion Middleware Developer's Guide for Oracle Service Bus

- Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus

- Oracle Fusion Middleware Concepts and Architecture for Oracle Service Bus

- Oracle Fusion Middleware Deployment Guide for Oracle Service Bus

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Understanding Oracle Service Bus 11g Release 1 (11.1.1.3)

This chapter provides an overview of Oracle Service Bus 11g Release 1 (11.1.1.3) and this guide. This chapter includes the following topics:

- What is Oracle Fusion Middleware?

- Oracle Service Bus

- Prerequisites for installing Oracle Service Bus

- What Does This Guide Cover?

See:
The "Related Documents" section in the Preface for a list of documents that provide additional information about the topics described in this chapter.

1.1 What is Oracle Fusion Middleware?

Oracle Service Bus is part of Oracle Fusion Middleware. Oracle Fusion Middleware is a collection of standards-based software products that spans a range of tools and services: From Java EE and developer tools, to integration services, business intelligence, and collaboration. Oracle Fusion Middleware offers complete support for development, deployment, and management.

1.2 Oracle Service Bus

Oracle Service Bus combines intelligent message brokering with service monitoring and administration to provide a unified software product for implementing and deploying Service-Oriented Architecture (SOA) on your enterprise. This converged approach adds a scalable, dynamic routing and transformation layer to your enterprise infrastructure, with service lifecycle management capabilities for service registration, service usage, and Service Level Agreement (SLA) compliance.

Oracle Service Bus relies on Oracle WebLogic Server run-time facilities. It leverages the capabilities inherent in Oracle WebLogic Server to deliver functionality that is highly available, scalable, and reliable.

The installer for Oracle Service Bus features the following sub-components that can be installed on your system:

- Oracle Service Bus Server: The full set of components that comprise Oracle Service Bus, excluding Oracle Service Bus examples and the Oracle Service Bus IDE.

- Oracle Service Bus IDE: Oracle Service Bus Plug-in is an integrated design environment for Oracle Service Bus. You must install Oracle Enterprise Pack for Eclipse to use Oracle Service Bus IDE.

- Oracle Service Bus Examples: The Oracle Service Bus examples provide you with a quick and easy way to experience the run-time capability of using proxy services in your design environment; they demonstrate key features and help you get started with designing and configuring resources and services using the Oracle Service Bus Console. These examples are user-driven, pre-configured scenarios that use Oracle Service Bus to communicate with business services. The examples are based on typical business scenarios that benefit from using Oracle Service Bus proxy services to communicate between clients and business processes. You can run the examples to see how Oracle Service Bus operates in the run-time environment, or you can build the examples in the development environment to get more in-depth knowledge of how to configure the proxy service.

Note:
By default, the Oracle Service Bus examples are not installed in a typical installation. To install the examples, select the custom installation option. For more information, see Understanding Oracle Service Bus Installation Types.

1.3 Prerequisites for installing Oracle Service Bus

If you perform the Typical installation of Oracle WebLogic Server by using the Oracle WebLogic Server Installer, you can obtain the following components required by Oracle Service Bus:

- Oracle WebLogic Server

- Oracle Coherence

- Oracle Enterprise Pack for Eclipse

1.3.1 Oracle WebLogic Server

Oracle WebLogic Server provides the core services that ensure reliability, high availability, scalability, and a high-performing execution environment for your application.

Oracle WebLogic Server consists of the following sub-components that can be installed on your system:

- Server: Oracle WebLogic Server program files that contain the core Java Enterprise Edition 2 (Java EE 2) features and Apache Beehive.

- Server Examples: Oracle WebLogic Server and MedRec example domain and sample applications. These servers and sample applications demonstrate a variety of Java EE 2 features. Resources are provided to help you build, configure, and run each of the sample applications. You must install the Server sub-component to install and use the Server Examples.

1.3.2 Oracle Coherence

Oracle Service Bus uses Oracle Coherence for its business service result caching functionality. Oracle Coherence is installed by default in a typical Oracle WebLogic Server installation. However, if you perform a custom Oracle WebLogic Server installation and do not install Oracle Coherence, result caching is not available for business services. For more information on result caching, see "Improving Performance by Caching Business Service Results" in the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus.

1.3.3 Oracle Enterprise Pack for Eclipse

Oracle Enterprise Pack for Eclipse (OEPE) is a certified set of Eclipse plug-ins designed to help develop, deploy and debug applications for Oracle WebLogic Server. Eclipse plug-ins facilitate development of Java SE, Java EE, Web Service, ORM, and Spring applications on Oracle WebLogic Server.

You must install OEPE to use Oracle Service Bus IDE. OEPE is installed as part of the Typical type of Oracle WebLogic Server installation. If you choose the Custom type of installation of Oracle WebLogic Server, be sure to select OEPE manually.

1.4 What Does This Guide Cover?

This topic describes the scope of information in this guide and how to use it. This topic includes the following sections:

- Using This Guide

- Upgrading to 11g Release 1 (11.1.1.3)

- Installing 11g Release 1 (11.1.1.3) for High Availability

1.4.1 Using This Guide

Each document in the Oracle Fusion Middleware Documentation Library has a specific purpose. The specific purpose of this guide is to explain how to:

1. Install single instances of Oracle Service Bus 11g Release 1 (11.1.1.3) components.

2. Verify the installation was successful.

3. Get started with the component after installation.

This guide covers the most common, certified Oracle Service Bus deployments. The following information is provided for each of these deployments:

- Appropriate Installation Environment: Helps you determine which installation is appropriate for your environment.

- Components Installed: Identifies the components that are installed in each scenario.

- Dependencies: Identifies the components each installation depends on.

- Procedure: Explains the steps for the installation.

As described in "Overview of Installation Process", the procedures in this guide explain how to install Oracle Service Bus components by using the Oracle Service Bus 11g Installer and the Oracle Fusion Middleware Configuration Wizard.

The following is a list of recommendations on how to use the information in this guide to install Oracle Service Bus 11g Release 1 (11.1.1.3):

1. Review Chapter 2, "Understanding the Oracle Service Bus 11g Release 1 (11.1.1.3) Installation," for context.

2. Review Chapter 3, "Preparing to Install Oracle Service Bus," for information about what you should consider before you install Oracle Service Bus.

3. Review Chapter 4, "Performing Common Installation Tasks," to understand the tasks that you must perform for most installations. Understanding this information before you start will expedite and simplify the deployment process.

4. Install, verify, and get started with your Oracle Service Bus component by referring to its specific chapter in this guide.

5. Use the appendixes in this guide as needed.

See Also:
The "Related Documents" section in this guide's Preface for a list of documents that provide additional information about Oracle Service Bus components.

1.4.2 Upgrading to 11g Release 1 (11.1.1.3)

This guide does not explain how to upgrade legacy versions of Oracle Service Bus components, including any previous database schemas, to 11g Release 1 (11.1.1.3). To upgrade a legacy version of Oracle Service Bus, refer to the following documents:

- Oracle Fusion Middleware Upgrade Planning Guide

- Oracle Fusion Middleware Upgrade Guide for Oracle Service Bus

1.4.3 Installing 11g Release 1 (11.1.1.3) for High Availability

This guide does not explain how to install Oracle Service Bus in High Availability (HA) configurations. To install Oracle Service Bus in a High Availability configuration, refer to the following documents:

- Oracle Fusion Middleware High Availability Guide

- Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Service Bus

2 Understanding the Oracle Service Bus 11g Release 1 (11.1.1.3) Installation

This chapter provides an overview of the Oracle Service Bus 11g Release 1 (11.1.1.3) installation. It includes the following topics:

- Overview of Installation Process

- Installing Oracle Service Bus and Creating a Domain in Development Environments

- Installing Oracle Service Bus and Creating a Domain in Production Environments

- Additional 11g Release 1 (11.1.1.3) Installation and Upgrade Information

- Understanding Oracle Service Bus Installation Types

- Understanding the State of Oracle Service Bus Components After Installation

- Understanding the Directory Structure After Installation

- Understanding Oracle WebLogic Server Administration Domain Options

- Silent Installation

- Oracle Service Bus Domain Configuration Scenarios

- Screens in Oracle Fusion Middleware Configuration Wizard

2.1 Overview of Installation Process

Installing Oracle Service Bus 11g Release 1 (11.1.1.3) involves the following steps:

1. Installing the Oracle Service Bus 11g Release 1 (11.1.1.3) software by using the Oracle Service Bus 11g Installer

2. Completing post-installation tasks, if any

As a standard practice, complete the following prerequisites for installing the Oracle Service Bus 11g Release 1 (11.1.1.3) software:

1. Review Oracle Service Bus certification information.

2. Review the system requirements.

3. Satisfy all dependencies, such as installing Oracle WebLogic Server, creating schema, installing Oracle Enterprise Pack for Eclipse, and so on.

4. Perform the installation procedure for the appropriate component.

5. Verify the installation.

Oracle Service Bus components will not start running after installing them using the Oracle Service Bus 11g Installer. For information about starting the components after installation, see the Getting Started topics in specific chapters in this guide.

Table 2-1 lists the Installers and tools used to install and configure Oracle Service Bus 11g at different stages of the installation and domain configuration processes.

Table 2-1 Installation and Configuration Tools

Task

Tool

Install Oracle WebLogic Server

Oracle WebLogic Server Installer

Ensure that the Oracle Enterprise Pack for Eclipse (OEPE) is installed along with the Oracle WebLogic Server by using the Oracle WebLogic Server Installer. OEPE is required for using the Oracle Service Bus IDE.

Install Repository Creation Utility

Repository Creation Utility (RCU) Installer

Create and load schemas

Repository Creation Utility (RCU)

Install Oracle Service Bus 11g

Oracle Service Bus 11g Software-Only Installer

Create or extend a WebLogic administration domain

Oracle Fusion Middleware Configuration Wizard

2.2 Installing Oracle Service Bus and Creating a Domain in Development Environments

The following figure illustrates the process of installing Oracle Service Bus and creating a domain in a development environment.

Note:
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.

2.3 Installing Oracle Service Bus and Creating a Domain in Production Environments

The following figure illustrates the process of installing Oracle Service Bus and creating a domain in a production environment.

2.4 Additional 11g Release 1 (11.1.1.3) Installation and Upgrade Information

This topic describes additional sources for 11g Release 1 (11.1.1.3) deployment information, including documentation on the following subjects:

- Upgrading to 11g Release 1 (11.1.1.3)

- Installing 11g Release 1 (11.1.1.3) for High Availability

See Also:
The "Related Documents" section in this guide's Preface for a list of documents that provide additional information about Oracle Service Bus components.

2.4.1 Upgrading to 11g Release 1 (11.1.1.3)

This guide does not explain how to upgrade previous versions of Oracle Service Bus applications to 11g Release 1 (11.1.1.3). To upgrade an Oracle Service Bus application:

From Oracle Service Bus Release 10g (10.3 or 10.3.1) and AquaLogic Service Bus (2.6 or 3.0) to 11g Release 1 (11.1.1.3), refer to:

- Oracle Fusion Middleware Upgrade Planning Guide

- Oracle Fusion Middleware Upgrade Guide for Oracle Service Bus

2.4.2 Installing 11g Release 1 (11.1.1.3) for High Availability

This guide does not explain how to install Oracle Service Bus in High Availability (HA) configurations. To install Oracle Service Bus in a High Availability configuration, refer to the following documents:

- Oracle Fusion Middleware High Availability Guide

2.5 Silent Installation

In addition to the standard graphical installation option, you can perform silent installation of Oracle Service Bus 11g. A silent installation runs on its own without any intervention, and you do not have to monitor the installation and provide input to dialog boxes.

For more information, see What is a Silent Installation?.

2.6 Understanding Oracle Service Bus Installation Types

During installation, you have the following options for choosing what components of Oracle Service Bus are installed:

- Typical Installation

- Custom Installation

2.6.1 Typical Installation

When you choose the Typical type of installation, the Oracle Service Bus 11g Installer installs the Oracle Service Bus Server and the binaries of Oracle Service Bus Integrated Development Environment (IDE) in a new Oracle Home directory.

2.6.2 Custom Installation

When you choose the Custom type of installation, you can select the following components of Oracle Service Bus to install:

- Oracle Service Bus Server

- Oracle Service Bus Integrated Development Environment

- Oracle Service Bus Examples

Note:
Oracle Service Bus Server is a mandatory component.
If you are installing Oracle Service Bus on a 64-bit machine, select the Custom installation type. You must deselect the Oracle Service Bus IDE option.

2.7 Understanding the State of Oracle Service Bus Components After Installation

This topic provides information about the state of Oracle Service Bus components after installation, including:

- Default SSL Configurations

- Administrator Server Password

2.7.1 Default SSL Configurations

By default, none of the Oracle Service Bus 11g components are installed with SSL configured. You must configure SSL for the Oracle WebLogic Administration Server and Oracle WebLogic Managed Server after installation, that is during domain creation.

See:
The Oracle Fusion Middleware Administrator's Guide for more information.

2.7.2 Administrator Server Password

Password for the Administration Server is configured during domain creation. For security reasons, after installation, you should change the passwords of the various components so they have different values.

See:
The following documents for information about changing passwords for Oracle Service Bus components:

- Oracle Fusion Middleware Administrator's Guide

- Component-specific guides listed in the "Related Documents" section in this guide's Preface.

2.8 Understanding the Directory Structure After Installation

This section describes the directory structure after installation of Oracle WebLogic Server and Oracle Service Bus. It also shows the structure of directories created after Oracle Service Bus is installed and configured in a WebLogic domain.

You can use this information to verify the installation of Oracle WebLogic Server and Oracle Service Bus after installing the software.

Oracle WebLogic Server Directory Structure

After you install Oracle WebLogic Server and create a Middleware Home, a home directory, such as wlserver_10.3, is created for Oracle WebLogic Server under your Middleware Home. This home directory is referred to as WL_HOME or WLS_HOME.

At the same level as WL_HOME, separate directories are created for the following components associated with Oracle WebLogic Server:

- Oracle Coherence - coherence_3.5

- Sun JDK - jdk160_18

- Oracle JRockit - jrockit_160_17_R28.0.0-679

- Oracle Enterprise Pack for Eclipse - oepe_11gR1PS2

Note that WebLogic domains are created in a directory named domains located in the user_projects directory under your Middleware Home.

Oracle Service Bus Directory Structure

After you install the Oracle Service Bus software, an Oracle Home directory for Oracle Service Bus, such as Oracle_OSB1, is created under your Middleware Home. This home directory is also referred to as OSB_HOME.

For more information about identifying installation directories, see Identifying Installation Directories.

2.9 Understanding Oracle WebLogic Server Administration Domain Options

After Oracle Service Bus is installed, you are ready to configure the WebLogic Server Administration Domain for Oracle Service Bus. A domain includes a special WebLogic Server instance called the Administration Server, which is the central point from which you configure and manage all resources in the domain.

This section describes each domain option for configuring an Oracle Service Bus domain:

- Create New Domain

- Extend Existing Domain

- Expand Cluster

See:
The "Understanding Oracle WebLogic Server Domains" chapter in the Oracle Fusion Middleware Understanding Domain Configuration for Oracle WebLogic Server guide for more information about Oracle WebLogic Server administration domains.

2.9.1 Create New Domain

Select the Create New Domain option in the Oracle Fusion Middleware Configuration Wizard to create a new WebLogic Server domain.

2.9.2 Extend Existing Domain

Select the Extend Existing Domain option in the Oracle Fusion Middleware Wizard to add Oracle Service Bus in an existing Oracle WebLogic Server administration domain. When you add Oracle Service Bus using this option, they are essentially "joining" an existing domain.

You can extend any of the following existing domains:

- Oracle WebLogic Server 10.3.3 domain

- Oracle SOA Suite 11.1.1.3.0 domain

- Oracle Service Bus 11.1.1.3.0 domain

2.9.3 Expand Cluster

Select the Expand Cluster option to add Oracle Service Bus to an Oracle WebLogic Server cluster for High Availability (HA). This document does not explain how to install Oracle Service Bus components in HA configurations. Refer to the following documents for more information:

- Oracle Fusion Middleware High Availability Guide

2.10 Oracle Service Bus Domain Configuration Scenarios

Table 2-2 and Table 2-3 describe Oracle Service Bus domain configuration scenarios.

Table 2-2 Oracle Service Bus Only Domain Topologies

Scenario

Description

Domain Configuration Option

A single-server Oracle Service Bus topology in a development environment

In this scenario, you can create a single server to function as WebLogic Administration Server and Managed Server. This domain topology is recommended for development.

Create or extend a WebLogic administration domain to support the following products:

- Oracle Service Bus Extension - Single Server Domain Topology - 11.1.1.3 [Oracle_OSB1]

All domain topologies in a production environment

In this scenario, you can create any of the following:

- A domain with a single server that functions as both Administration Server and Managed Server

- A non-clustered domain with an Administration Server and a single Managed Server

- A domain with an Administration Server and a cluster of one or more Managed Servers

Create or extend a WebLogic administration domain to support the following products:

- Oracle Service Bus Extension - All Domain Topologies - 11.1.1.3 [Oracle_OSB1]

Oracle Service Bus with runtime support for Oracle Web Services Manager policies

In this scenario, you can create a domain with Oracle Service Bus to use Oracle Web Services Manager security policies.

Create or extend a WebLogic administration domain to support the following products:

- Oracle Service Bus OWSM Extension - 11.1.1.3 [Oracle_OSB1]

- Oracle Service Bus Extension - Single Server Domain Topology - 11.1.1.3 [Oracle_OSB1]
Or

Oracle Service Bus Extension - All Domain Topologies - 11.1.1.3 [Oracle_OSB1]

Oracle Service Bus domain with support for Oracle Web Services Manager policies and support for creation or editing of Oracle Web Services Manager policies using Oracle Enterprise Manager Fusion Middleware Control 11g R1 (11.1.1.1.0)

In this scenario, you can create Oracle Service Bus to use Oracle Web Services Manager security policies. In addition, you can create Oracle Web Services Manager security policies using Oracle Service Bus.

Create or extend a WebLogic administration domain to support the following products:

- Oracle Service Bus OWSM Extension - 11.1.1.3 [Oracle_OSB1]

- Oracle Enterprise Manager - 11.1.1.0 [oracle_common]

- Oracle Service Bus Extension - Single Server Domain Topology - 11.1.1.3 [Oracle_OSB1]
Or

Oracle Service Bus Extension - All Domain Topologies - 11.1.1.3 [Oracle_OSB1]

Table 2-3 Oracle Service Bus with Oracle SOA Suite (Co-existence Scenarios)

Scenario

Description

Domain Configuration Option

Oracle Service Bus with Oracle SOA Suite in a New WebLogic Domain

In this scenario, you can create Oracle Service Bus and Oracle SOA Suite in a new WebLogic domain.

For information about installing the latest version of Oracle SOA Suite, see Installing the Latest Version of Oracle SOA Suite.

Create a WebLogic administration domain to support the following products:

- Oracle SOA Suite - 11.1.1.0 [Oracle_SOA1] or Oracle BPM Suite - 11.1.1.0 [Oracle_SOA1]

- Oracle Service Bus Extension - All Domain Topologies - 11.1.1.3 [Oracle_OSB1]

Oracle SOA Suite in an Existing Oracle Service Bus Domain

In this scenario, you can install Oracle SOA Suite in an existing Oracle Service Bus domain.

For information about installing the latest version of Oracle SOA Suite, see Installing the Latest Version of Oracle SOA Suite.

Extend an existing Oracle Service Bus WebLogic administration domain to support the following products:

Oracle SOA Suite - 11.1.1.0 [Oracle_SOA1]

or

Oracle BPM Suite - 11.1.1.0 [Oracle_SOA1]

Oracle Service Bus in an Existing Oracle SOA Suite Domain

In this scenario, you can install Oracle Service Bus in an existing Oracle SOA Suite domain.

For information about installing the latest version of Oracle SOA Suite, see Installing the Latest Version of Oracle SOA Suite.

Extend an existing Oracle SOA Suite WebLogic administration domain to support the following products:

Oracle Service Bus Extension - All Domain Topologies - 11.1.1.3 [Oracle_OSB1]

2.11 Screens in Oracle Fusion Middleware Configuration Wizard

The Oracle Fusion Middleware Configuration Wizard displays screens based on your domain configuration options. Table 2-4 lists the names of screens for the following scenarios:

- Creation and configuration of a new WebLogic administration domain, which involves the configuration of Administration Server parameters, server start mode, and so on.

- Configuration of an existing domain to support Oracle Service Bus components by extending the domain.

Table 2-4 Screens Displayed in Oracle Fusion Middleware Configuration Wizard

Domain Configuration Options

Screens Displayed in the Oracle Fusion Middleware Wizard

Creating a new WebLogic administration domain to support Oracle Service Bus

In this scenario, the Oracle Fusion Middleware Configuration Wizard displays the following screens:

- Welcome

- Select Domain Source

- Specify Domain Name and Location

- Configure Administrator User Name and Password

- Configure Server Start Mode and JDK

- Configure JDBC Component Schema

- Test Component Schema

- Select Optional Configuration

- Configure the Administration Server (Optional)

- Configure JMS Distributed Destination (Optional)

- Configure Managed Servers (Optional)

- Configure Clusters (Optional)

- Configure Machines (Optional)

- Assign Servers to Machines (Optional)

- Target Deployments to Clusters or Servers (Optional)

- Target Services to Clusters or Servers (Optional)

- Configure JMS File Stores (Optional)

- Configure RDBMS Security Store Database (Optional)

- Configuration Summary

Extending an existing WebLogic domain to support Oracle Service Bus

In this scenario, the Oracle Fusion Middleware Configuration Wizard displays the following screens:

- Select a WebLogic Domain Directory

- Select Extension Source

- Configure JDBC Component Schema

- Test Component Schema

- Select Optional Configuration

- Configure JMS Distributed Destination (Optional)

- Configure Managed Servers (Optional)

- Configure Clusters (Optional)

- Configure Machines (Optional)

- Assign Servers to Machines (Optional)

- Target Deployments to Clusters or Servers (Optional)

- Target Services to Clusters or Servers (Optional)

- Configure JMS File Stores (Optional)

- Configuration Summary

See:
The "Customizing the Domain Environment" chapter in the Oracle Fusion Middleware Creating Domains Using the Configuration Wizard guide for more information about configuring your domain.

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:

- Oracle Fusion Middleware Certification

- System Requirements

- Installing and Configuring Java Access Bridge (Windows Only)

- Installing Oracle WebLogic Server and Creating the Oracle Middleware Home

- Completing Database Requirements

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

- Optional Environment-Specific Preparation

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:

- Most Recent Information

- Installer Startup Requirements

- Memory Requirements

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.

See:
The Oracle Fusion Middleware Repository Creation Utility User's Guide for complete information.

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:

- Using Symbolic Links

- Installing Oracle Service Bus on DHCP Hosts

- Installing Oracle Service Bus on a Multihomed System

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.

4 Performing Common Installation Tasks

This chapter describes tasks that are common to most Oracle Service Bus installations and configurations. It includes the following topics:

- Starting an Installation

- Identifying Installation Directories

- Completing an Installation

- Locating Installation Log Files

4.1 Starting an Installation

This topic explains the steps that are common to starting most Oracle Service Bus installations and configurations. It begins with starting the Installer and ends after you complete the steps on the Prerequisites Check screen.

Note:
Starting the Installer as the root user is not supported.

Perform the following steps to start an Oracle Service Bus installation:

1. Start the Installer by executing one of the following commands:
UNIX: <full path to the runInstaller directory>/runInstaller -jreLoc <Middleware_Home>/jrockit_160_17_R28.0.0-670/jre

Windows: <full path to the setup.exe directory>\ setup.exe -jreLoc <Middleware_Home>\jrockit_160_17_R28.0.0-670\jre

Note:
The installer prompts you to enter the absolute path of the JDK that is installed on your system. When you install Oracle WebLogic Server, the jrockit_160_17_R28.0.0-670 directory is created under your Middleware Home. You must enter the absolute path of the JRE folder located in this JDK when launching the Installer. For example, on Windows, if the JRE is located in D:\oracle\Middleware\jrockit_160_17_R28.0.0-670, then launch the installer from the command prompt as follows:
D:\setup.exe -JRELOC D:\oracle\Middleware\jrockit_160_17_R28.0.0-670\jre

If Sun JDK is installed instead of Oracle JRockit, you must specify the path to Sun JDK.

If you are installing Oracle Service Bus on 64-bit UNIX machines, enter the following command to invoke the installer:

<full path to the runInstaller directory>/runInstaller -jreLoc <Middleware_Home>/<JAVA_HOME>/jre

After the Installer starts, the Welcome screen appears. Continue by referring to the appropriate procedure in this document for the installation you want to perform.

4.2 Identifying Installation Directories

This topic describes directories you must identify in most Oracle Service Bus installations—it does not describe one particular Installer screen. During installation, you will have to identify other component-specific directories not described in this topic.

The common directories described in this section include the following:

- Oracle Middleware Home Location

- Oracle Home Directory

- Oracle Common Directory

- WebLogic Server Directory

- Oracle WebLogic Domain Directory

4.2.1 Oracle Middleware Home Location

Identify the location of your Oracle Middleware Home directory. The Installer creates an Oracle Home directory for the component you are installing under the Oracle Middleware Home that you identify in this field. The Oracle Middleware Home directory is commonly referred to as MW_HOME or Middleware_Home.

4.2.2 Oracle Home Directory

Enter a name for the Oracle Home directory of the component. The Installer uses the name you enter in this field to create the Oracle Home directory under the location you enter in the Oracle Middleware Home Location field.

The Installer installs the files required to host the component, such as binaries and libraries, in the Oracle Home directory. The Oracle Home directory is commonly referred to as ORACLE_HOME.

Note:
Avoid using spaces in the directory names, including Oracle Home. Spaces in such directory names are not supported.
A Middleware Home can contain only one Oracle Service Bus Home directory.

4.2.3 Oracle Common Directory

The Installer creates this directory under the location you enter in the Oracle Middleware Home Location field.

The Installer installs the Java Required Files (JRF) required to host the components, in the Oracle Common directory. There can be only one Oracle Common Home within each Oracle Middleware Home. The Oracle Common directory is commonly referred to as oracle_common.

4.2.4 WebLogic Server Directory

Enter the path to your Oracle WebLogic Server Home directory. This directory contains the files required to host the Oracle WebLogic Server. It is commonly referred to as WL_HOME.

4.2.5 Oracle WebLogic Domain Directory

A WebLogic domain includes a special WebLogic Server instance called the Administration Server, which is the central point from which you configure and manage all resources in the domain. Usually, you configure a domain to include additional WebLogic Server instances called Managed Servers. You deploy Java components, such as Web applications, EJBs, and Web services, and other resources to the Managed Servers and use the Administration Server for configuration and management purposes only.

Managed Servers in a domain can be grouped together into a cluster.

The directory structure of a domain is separate from the directory structure of the WebLogic Server home. It can reside anywhere; it need not be within the Middleware home directory. A domain is a peer of an Oracle instance.

The Oracle Fusion Middleware Configuration Wizard creates a domain in a directory named user_projects under your Middleware Home (MW_HOME).

4.3 Creating and Starting Managed Servers on a Remote Machine

To create and start a Managed Server in your WebLogic domain on a remote machine, complete the following steps:

- Use the pack command located in the \common\bin directory under your Oracle WebLogic Server directory to create a Managed Server template that contains a subset of the files in a domain that are required to create a Managed Server domain directory hierarchy on a remote machine.
The -managed={true|false} parameter of the pack command specifies whether the template is to be used to create Managed Servers on remote machines.

- Use the unpack command located in the \common\bin directory under your Oracle WebLogic Server directory to create the Managed Server domain directory on the remote machine.

For more information, see the "Creating and Starting a Managed Server on a Remote Machine" in the guide Oracle Fusion Middleware Creating Templates and Domains Using the Pack and Unpack Commands.

4.4 Completing an Installation

This topic explains the steps that are common to completing most Oracle Service Bus installations and configurations. It begins with the steps on the Installation Summary screen and ends after the Installation Complete screen.

When the Installation Summary screen appears, perform the following steps to complete the installation:

1. Verify the installation and configuration information on the Installation Summary screen.

- Click Save to save the installation response file, which contains your responses to the Installer prompts and fields. You can use this response file to perform silent installations. Refer to Performing Silent Installations for more information.

Note:
The installation response file is not saved by default—you must click Save to retain it.

- Click Install. The Installation Progress screen appears.

2. Monitor the progress of your installation. The location of the installation log file is listed for reference. After the installation progress reaches 100%, click OK. The Installation Complete screen appears.

3. Click Save to save the installation summary file. This file contains information about the configuration, such as locations of install directories, that will help you get started with configuration and administration.

Note:
The installation summary file is not saved, by default—you must click Save to retain it.

Click Finish to close and exit the Installer.

4.5 Locating Installation Log Files

The Installer writes log files to the ORACLE_INVENTORY_LOCATION/logs directory on UNIX systems and to the ORACLE_INVENTORY_LOCATION\logs directory on Windows systems.

On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the ORACLE_HOME/oraInst.loc file.

On Microsoft Windows systems, the default location for the inventory directory is C:\Program Files\Oracle\Inventory\logs.

The following install log files are written to the log directory:

- installDATE-TIME_STAMP.log

- installDATE-TIME_STAMP.out

- installActionsDATE-TIME_STAMP.log

- installProfileDATE-TIME_STAMP.log

- oraInstallDATE-TIME_STAMP.err

- oraInstallDATE-TIME_STAMP.log

5 Installing and Configuring Oracle Service Bus 11g

This chapter explains how to install and configure only Oracle Service Bus. It includes the following topics:

- Prerequisites

- Installing the Oracle Service Bus 11g Software

- Creating a WebLogic Domain

- Creating a WebLogic Domain with Only Oracle Service Bus 11g

- Installing the Latest Version of Oracle SOA Suite

- Creating a WebLogic Domain with Oracle Service Bus 11g and Oracle SOA Suite in the Same Domain

- Extending an Oracle Service Bus WebLogic Domain to Support Oracle SOA Suite

- Extending an Oracle SOA Suite WebLogic Domain to Support Oracle Service Bus

- After Creating Oracle Service Bus 11g Domain

- Verifying Oracle Service Bus 11g Installation and Domain Configuration

- Start Menu Commands on Windows

- Getting Started with Oracle Service Bus 11g After Installation

Oracle Service Bus and Oracle SOA Suite Coexistence Scenarios

This chapter also discusses how to install and configure Oracle Service Bus and Oracle SOA Suite in the same domain. Specifically, read the following sections:

- Installing the Latest Version of Oracle SOA Suite

- Creating a WebLogic Domain with Oracle Service Bus 11g and Oracle SOA Suite in the Same Domain

- Extending an Oracle Service Bus WebLogic Domain to Support Oracle SOA Suite

- Extending an Oracle SOA Suite WebLogic Domain to Support Oracle Service Bus

5.1 Prerequisites

Before installing and configuring Oracle Service Bus, complete all the prerequisites described in Preparing to Install Oracle Service Bus.

5.2 Installing the Oracle Service Bus 11g Software

This topic describes how to install Oracle Service Bus 11g (software only). It includes the following sections:

- Components Installed

- Dependencies

- Procedure

5.2.1 Components Installed

Performing the Typical type of installation in this section deploys the following components:

- Oracle Service Bus Server

- Oracle Service Bus Integrated Development Environment (IDE)

Performing the Custom type of installation in this section deploys the following components based on your choice:

- Oracle Service Bus Server (Mandatory)

- Oracle Service Bus Integrated Development Environment (IDE)

- Oracle Service Bus Examples

5.2.2 Dependencies

The Oracle Service Bus installation depends on the installation of the following components:

- Oracle WebLogic Server

- Oracle Enterprise Pack for Eclipse (for Oracle Service Bus Integrated Development Environment only), which is installed with Oracle WebLogic Server

- JDK (either Oracle WebLogic JRockit JDK or Sun JDK 1.6.0)

5.2.3 Procedure

Complete the following steps to install Oracle Service Bus 11g:

1. Start your installation by performing all the steps in Starting an Installation. After you complete those steps, the Welcome screen appears.

2. Click Next on the Welcome screen. The Select Installation Type screen appears.

3. On the Select Installation Type screen, choose either Typical or Custom. For more information, see Understanding Oracle Service Bus Installation Types. Click Next. The Prerequisites Check screen appears.

Note:
If you are installing Oracle Service Bus on a 64-bit machine, select the Custom installation type. You must deselect the Oracle Service Bus IDE option.

4. If all prerequisite checks pass inspection, click Next. The Specify Installation Location screen appears.

5. On the Specify Installation Location screen, in the Oracle Middleware Home field, enter the path to the Oracle Middleware Home installed on your system. Ensure that Oracle WebLogic Server is already installed on the system in the same Middleware Home. This directory is the same as the Oracle Middleware Home directory created in the Oracle WebLogic Server installation.

6. In the Oracle Home Directory field, enter a name for the Oracle Home folder that will be created under your Middleware Home.

7. In the WebLogic Server Location field, enter the path to the Oracle WebLogic Server installed on your machine. By default, this directory under your Middleware Home is named wlserver_10.3.

8. Optional: If you are installing Oracle Service Bus Integrated Development Environment (IDE), enter the path to the Oracle Enterprise Pack for Eclipse installed on your machine. By default, this directory under your Middleware Home is named oepe_11gR1PS2.
The Summary Page screen displays a summary of the choices that you made. Review this summary and decide whether to start the installation. If you want to modify any of the configuration settings at this stage, select a topic in the left navigation page and modify your choices. To continue installing Oracle Service Bus, click Install.

This installation process copies the Oracle Service Bus software to your system and creates an Oracle Service Bus Home directory under your Middleware Home. You must proceed to create a WebLogic Domain, as described in Creating a WebLogic Domain. In addition, you must configure the Administration Server settings while creating the domain.

5.3 Creating a WebLogic Domain

You can use the Oracle Fusion Middleware Configuration Wizard to create a WebLogic domain or extend an existing domain. For more information about WebLogic administration domain options, see Understanding Oracle WebLogic Server Administration Domain Options.

See:
The "Understanding Oracle WebLogic Server Domains" chapter in the Oracle Fusion Middleware Understanding Domain Configuration for Oracle WebLogic Server guide for more information about Oracle WebLogic Server administration domains.
For information about domain configuration options, see Oracle Service Bus Domain Configuration Scenarios.

5.4 Creating a WebLogic Domain with Only Oracle Service Bus 11g

This topic describes how to create a WebLogic domain with only Oracle Service Bus. It includes the following sections:

- Appropriate Installation Environment

- Components Installed

- Dependencies

- Procedure

5.4.1 Appropriate Installation Environment

Perform the installation and configuration in this topic if you want to create a new domain with only Oracle Service Bus. For information about domain configuration options, see Oracle Service Bus Domain Configuration Scenarios.

5.4.2 Components Installed

Performing the installation and configuration in this section deploys the following:

- WebLogic Administration Server

- Managed Server for Oracle Service Bus

- Application deployed on the Managed Server

- Oracle Service Bus Administration Console deployed on the Oracle Service Bus Server

5.4.3 Dependencies

The installation and configuration in this section depends on the following:

- Oracle WebLogic Server

- Oracle Service Bus 11g

5.4.4 Procedure

Perform the following steps to create a new domain with only Oracle Service Bus:

1. Install the Oracle WebLogic Server, as described in Installing Oracle WebLogic Server and Creating the Oracle Middleware Home.

2. Install the Oracle Service Bus 11g software, as described in Installing the Oracle Service Bus 11g Software.

3. Start the Oracle Fusion Middleware Configuration Wizard by running the following command:
On UNIX: <Middleware_Home>/oracle_common/common/bin/config.sh

On Windows: <Middleware_Home>\oracle_common\common\bin\config.bat.

The Oracle Fusion Middleware Configuration Wizard appears.

4. On the Welcome screen, select the Create a new WebLogic domain option. Click Next. The Select Domain Source screen appears.

5. On the Select Domain Source screen ensure that the Generate a domain configured automatically to support the following products: option is selected. Select a domain configuration option. For more information, see Oracle Service Bus Domain Configuration Scenarios.
The following table summarizes the options for deploying Oracle Service Bus in a WebLogic domain.

Table 5-1 Oracle Service Bus Domain Configuration Options

Domain Template

Description

Oracle Service Bus Extension - Single Server Domain Topology - 11.1.1.3 [Oracle_OSB1]

Use this option to create a single server to function as WebLogic Administration Server and Managed Server. This deployment option is ideal for development environments.

When you select the Oracle Service Bus Extension - Single Server Domain Topology - 11.1.1.3 [Oracle_OSB1] option, the following options are also selected, by default:

- Oracle JRF - 11.1.1.0 [oracle_common]

- WebLogic Advanced Web Services for JAX-RPC Extension - 10.3.3.0 [wlserver_10.3]

Oracle Service Bus Extension - All Domain Topologies - 11.1.1.3 [Oracle_OSB1]

Use this option to install and configure any of the following:

- A domain with a single server that functions as both Administration Server and Managed Server

- A non-clustered domain with an Administration Server and a single Managed Server

- A domain with an Administration Server and a cluster of one or more Managed Servers

When you select the Oracle Service Bus Extension - All Domain Topologies - 11.1.1.3 [Oracle_OSB1] option, the following options are also selected, by default:

- Oracle JRF - 11.1.1.0 [oracle_common]

- WebLogic Advanced Web Services for JAX-RPC Extension - 10.3.3.0 [wlserver_10.3]

Oracle Service Bus OWSM Extension - 11.1.1.3 [Oracle_OSB1]

Use this option to create a domain with Oracle Service Bus with runtime support for Oracle Web Services Manager policies

Note that the Oracle Service Bus OWSM Extension template has a dependency on one of the Oracle Service Bus templates (Single Server Topology, or All Domain Topologies). Therefore, you can select the Oracle Service Bus OWSM Extension - 11.1.1.3 [Oracle_OSB1] option only after you select either Oracle Service Bus Extension - Single Server Domain Topology - 11.1.1.3 [Oracle_OSB1] or Oracle Service Bus Extension - All Domain Topologies - 11.1.1.3 [Oracle_OSB1].

When you select the Oracle Service OWSM Extension - 11.1.1.3 [Oracle_OSB1] option, the following option is also selected, by default:

- Oracle WSM Policy Manager - 11.1.1.0 [oracle_common]

In addition, select the Oracle Enterprise Manager - 11.1.1.0 [oracle_common] option if you want to create or edit Oracle Web Services Manager policies using Oracle Enterprise Manager Fusion Middleware Control 11g R1 (11.1.1.1.0).

6. After selecting your domain configuration options, click Next. The Select Domain Name and Location screen appears.

7. Enter a name and a location for the domain to be created, and click Next. The Configure Administrator User Name and Password screen appears.

8. Configure a user name and a password for the administrator. The default user name is weblogic. Click Next.

9. Choose JRockit SDK 1.6.0_17 and Production Mode in the Configure Server Start Mode and JDK screen of the Oracle Fusion Middleware Configuration Wizard. For Development mode, you can select the Sun JDK. Click Next. The Configure JDBC Component Schema screen is displayed.

10. On the Configure JDBC Component Schema screen, select a component schema, such as the OSB JMS Reporting Provider Schema or the OWSM MDS Schema that you want to modify.
You can set values for Schema Owner, Schema Password, Database and Service, Host Name, and Port. You must run RCU first, and the values must match the ones used for RCU. You can select the OSB JMS Reporting Provider by selecting it.

Note:
If you are using the Evaluation Database, ensure that the following values are selected:

- Driver - Derby's Driver (Type 4) Versions:A

- Vendor - Derby

- DBMS/Service - osbexamples

- Host Name - localhost

You can ignore the results of connection testing if you are using the Evaluation Database.

Click Next. The Test JDBC Component Schema screen appears. After the test succeeds, the Select Optional Configuration screen appears.

11. On the Select Optional Configuration screen, you can configure the Administration Server, Managed Servers, Clusters, Machines, Deployments and Services, RDBMS Security Store, and so on. Select the relevant check boxes and click Next.

- Configure the following Administration Server parameters:

- Name

- Listen Address

- Listen Port

- SSL Listen Port

- SSL Enabled

- Configure JMS Distributed Destination, as required.

- Configure Managed Servers, as required.

- Configure Clusters, as required.

- Assign Managed Servers to Clusters, as required.

- Configure Machines, as needed. This step is useful when you want to run the Administration Server on one machine and Managed Servers on another physical machine.

- Assign the Administration Server to a machine.

- Select Deployments, such as applications and libraries, and Services to target them to a particular cluster or server.

- Configure RDBMS Security Store Database, as required.

12. On the Configuration Summary screen, review the domain configuration, and click Create to start creating the domain.

The WebLogic domain with your configuration attributes is created.

Note:
For information about creating and starting a Managed Server on a remote machine, see Creating and Starting Managed Servers on a Remote Machine.

5.5 Installing the Latest Version of Oracle SOA Suite

Follow the instructions in this section to install the latest version of Oracle SOA Suite.

Installing the latest version of Oracle SOA Suite 11g involves the following steps:

1. Obtaining the Latest Oracle WebLogic Server and Oracle SOA Suite

2. Installing Oracle WebLogic Server and Creating the Middleware Home

3. Installing Oracle SOA Suite 11.1.1.2.0

4. Patching the Software

5.5.1 Obtaining the Latest Oracle WebLogic Server and Oracle SOA Suite

Refer to the following for more information about the latest Oracle WebLogic Server and Oracle Fusion Middleware 11g software:

- You can download the latest Oracle Fusion Middleware 11g software from the Oracle Technology Network (OTN):

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

- At the time this document was published, the latest release of Oracle Fusion Middleware 11g was 11g Release 1 (11.1.1.3.0), which provides new features and capabilities that supersede those available in Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) and 11g Release 1 (11.1.1.2.0).

- Oracle Fusion Middleware 11g also requires the latest version of Oracle WebLogic Server. At the time this document was published, the latest version of Oracle WebLogic Server was Oracle WebLogic Server 11g (10.3.3.0).

- For complete information about patching your Oracle Fusion Middleware 11g to the latest release, refer to the Oracle Fusion Middleware Patching Guide.

5.5.2 Installing Oracle WebLogic Server and Creating the Middleware Home

Oracle SOA Suite requires Oracle WebLogic Server and a Middleware home directory. For more information, see "Install Oracle WebLogic Server" in Oracle Fusion Middleware Installation Planning Guide. In addition, see "Running the Installation Program in Graphical Mode" in Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

Note:
If you have already created a Middleware Home before installing Oracle Service Bus 11g, you do not need to create a new Middleware Home again. You can use the same Middleware Home for installing Oracle SOA Suite.

For information about downloading Oracle WebLogic Server, see "Product Distribution" in the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

5.5.3 Installing Oracle SOA Suite 11.1.1.2.0

Follow the instructions in Table 5-2 to install Oracle SOA Suite 11.1.1.2.0.

If you need additional help with any of the installation screens, click Help to access the online help.

Table 5-2 Installation Flow for Install Only Option

No.

Screen

Description and Action Required

1

Welcome Screen

Click Next to continue.

2

Prerequisite Checks Screen

Click Next to continue.

3

Specify Installation Location Screen

Specify the Middleware Home and Oracle Home locations. You must specify the location of the same Middleware Home that contains Oracle Service Bus.

For more information about these directories, see "Oracle Fusion Middleware Directory Structure and Concepts" in Oracle Fusion Middleware Installation Planning Guide.

Click Next to continue.

4

Specify Security Updates Screen

Provide your E-mail address to be informed of the latest product issues.

Click Next to continue.

5

Installation Summary Screen

Verify the information on this screen.

Click Install to begin the installation.

6

Installation Progress Screen

If you are installing on a UNIX system, you may be asked to run the ORACLE_HOME/oracleRoot.sh script to set up the proper file and directory permissions.

Click Next to continue.

7

Installation Complete Screen

Click Finish to dismiss the installer.

Note:
At this stage of the installation process, do not configure a WebLogic domain for Oracle SOA Suite.

5.5.4 Patching the Software

After the installation is complete, you must run the Patch Set Installer for Oracle SOA Suite to update your software to the latest version 11.1.1.3.0.

For instructions, go to "Applying the Latest Oracle Fusion Middleware Patch Set with the Patch Set Installers" in Oracle Fusion Middleware Patching Guide.

5.6 Creating a WebLogic Domain with Oracle Service Bus 11g and Oracle SOA Suite in the Same Domain

This topic describes how to create a WebLogic domain with Oracle Service Bus and Oracle SOA Suite in the same WebLogic administration domain. It includes the following sections:

- Appropriate Installation Environment

- Components Installed

- Dependencies

- Procedure

5.6.1 Appropriate Installation Environment

Perform the installation and configuration in this topic if you want to create a WebLogic domain with Oracle Service Bus and Oracle SOA Suite in the same WebLogic administration domain. For information about domain configuration options, see Oracle Service Bus Domain Configuration Scenarios.

Note:
You must install Oracle Service Bus and Oracle SOA Suite in the same Middleware Home.

5.6.2 Components Installed

Performing the installation and configuration in this section deploys the following:

- WebLogic Administration Server

- A single Managed Server for Oracle Service Bus and Oracle SOA Suite, or one Managed Server for Oracle Service Bus and one Managed Server for Oracle SOA Suite

- Applications deployed on the Managed Server

- Oracle SOA Suite Console and Oracle Service Bus Administration Console deployed on the Administration Server

5.6.3 Dependencies

The installation and configuration in this section depends on the following:

- Oracle WebLogic Server

- Oracle Service Bus 11g

- Oracle SOA Suite 11g

5.6.4 Procedure

Perform the following steps to create a WebLogic domain with Oracle Service Bus and Oracle SOA Suite in the same WebLogic administration domain:

1. Install Oracle WebLogic Server, as described in Installing Oracle WebLogic Server and Creating the Oracle Middleware Home.

2. Install the Oracle Service Bus 11g software, as described in Installing the Oracle Service Bus 11g Software.

3. Install the Oracle SOA Suite 11g software, as described in Installing the Latest Version of Oracle SOA Suite.

4. Start the Oracle Fusion Middleware Configuration Wizard by running the following command:
On UNIX: <Middleware_Home>/oracle_common/common/bin/config.sh

On Windows: <Middleware_Home>\oracle_common\common\bin\config.bat.

The Oracle Fusion Middleware Configuration Wizard appears.

5. On the Welcome screen, select the Create a new WebLogic domain option. Click Next. The Select Domain Source screen appears.

6. On the Select Domain Source screen ensure that the Generate a domain configured automatically to support the following products: option is selected.
Select the following domain configuration option:

- Oracle SOA Suite - 11.1.1.0 [Oracle_SOA1]

Note:
When you select the Oracle SOA Suite - 11.1.1.0 [Oracle_SOA1] option, the Oracle JRF - 11.1.1.0 [oracle_common] option and the Oracle WSM Policy Manager - 11.1.1.0 [oracle_common] option are also selected, by default.

- Oracle Service Bus Extension - All Domain Topologies - 11.1.1.3 [Oracle_OSB1]
When you select the Oracle Service Bus Extension - All Domain Topologies - 11.1.1.3 [Oracle_OSB1] option, the WebLogic Advanced Web Services for JAX-RPC Extension - 10.3.3.0 [wlserver_10.3] option is also selected, by default.

For more information, see Oracle Service Bus Domain Configuration Scenarios.

7. After selecting the domain configuration options, click Next. The Select Domain Name and Location screen appears.

8. Enter a name and a location for the domain to be created, and click Next. The Configure Administrator User Name and Password screen appears.

9. Configure a user name and a password for the administrator. The default user name is weblogic. Click Next.

10. Choose JRockit SDK 1.6.0_17 and Production Mode in the Configure Server Start Mode and JDK screen of the Oracle Fusion Middleware Configuration Wizard. For Development mode, you can select the Sun JDK. Click Next. The Configure JDBC Component Schema screen is displayed.

11. On the Configure JDBC Component Schema screen, select a component schema, such as the OSB JMS Reporting Provider Schema, the SOA Infrastructure Schema, the User Messaging Service Schema, the OWSM MDS Schema, or the SOA MDS Schema, that you want to modify.
You can set values for Schema Owner, Schema Password, Database and Service, Host Name, and Port. You must run RCU first, and the values must match the ones used for RCU.

Click Next. The Test JDBC Component Schema screen appears. After the test succeeds, the Select Optional Configuration screen appears.

12. On the Select Optional Configuration screen, you can configure the Administration Server, Managed Servers, Clusters, Machines, Deployments and Services, RDBMS Security Store, and so on. Select the relevant check boxes and click Next.

- Configure the following Administration Server parameters:

- Name

- Listen Address

- Listen Port

- SSL Listen Port

- SSL Enabled

- Optional: Configure JMS Distributed Destination, as required.

- To configure a single Managed Server for Oracle Service Bus and Oracle SOA Suite, do the following:
On the Configure Managed Servers screen, delete the default osb_server1 by selecting osb_server1 and clicking Delete. Then modify the name of soa_server1 as osb_server1 by manually editing the name in the Name column. Alternatively, you may delete soa_server1 and rename osb_server1 to soa_server1.

Note:
This optional step is required only if you want to have Oracle SOA Suite and Oracle Service Bus running in the same virtual machine. If you skip this step, you will configure a Managed Server each for Oracle SOA Suite and Oracle Service Bus.

- Optional: Configure Clusters, as required.

- Optional: Assign Managed Servers to Clusters, as required.

- Optional: Configure Machines, as needed. This step is useful when you want to run the Administration Server on one machine and Managed Servers on another physical machine.

- Optional: Assign the Administration Server to a machine.

- Optional: Select Deployments, such as applications and libraries, and Services to target them to a particular cluster or server.

- Optional: Configure JMS File Store, as required.

- Optional: Configure RDBMS Security Store Database, as required.

13. On the Configuration Summary screen, review the domain configuration, and click Create to start creating the domain.

The WebLogic domain with your configuration attributes is created.

Note:
For information about creating and starting a Managed Server on a remote machine, see Creating and Starting Managed Servers on a Remote Machine.

5.7 Extending an Oracle Service Bus WebLogic Domain to Support Oracle SOA Suite

This topic describes how to extend an existing Oracle Service Bus domain to support Oracle SOA Suite. It includes the following sections:

- Appropriate Installation Environment

- Components Installed

- Dependencies

- Procedure

5.7.1 Appropriate Installation Environment

Perform the installation and configuration in this topic if you want to extend an existing Oracle Service Bus 11g domain to support Oracle SOA Suite. For information about domain configuration options, see Oracle Service Bus Domain Configuration Scenarios.

Note:
You must install Oracle SOA Suite in the same Middleware Home that contains Oracle Service Bus.

5.7.2 Components Installed

Performing the installation and configuration in this section deploys the following:

- Oracle SOA Suite and Oracle Service Bus on the same Managed Server, or one Managed Server each for Oracle Service Bus and Oracle SOA Suite

- Applications deployed on the Managed Server

- Oracle Service Bus Administration Console deployed on the Administration Server

5.7.3 Dependencies

The installation and configuration in this section depends on the following:

- Oracle WebLogic Server

- Oracle Service Bus 11g

- Oracle SOA Suite 11g

5.7.4 Procedure

Perform the following steps to extend an existing Oracle Service Bus domain to support Oracle SOA Suite:

1. Install Oracle WebLogic Server, as described in Installing Oracle WebLogic Server and Creating the Oracle Middleware Home.

2. Install the Oracle Service Bus 11g software, as described in Installing the Oracle Service Bus 11g Software.

3. Create a new WebLogic administration domain with Oracle Service Bus, as described in Creating a WebLogic Domain with Only Oracle Service Bus 11g.

4. Install the Oracle SOA Suite 11g software, as described in Installing the Latest Version of Oracle SOA Suite.

5. Start the Oracle Fusion Middleware Configuration Wizard by running the following command:
On UNIX: <Middleware_Home>/oracle_common/common/bin/config.sh

On Windows: <Middleware_Home>\oracle_common\common\bin\config.bat.

The Oracle Fusion Middleware Configuration Wizard appears.

6. On the Welcome screen, select the Extend an existing WebLogic domain option. Click Next. The Select a WebLogic Domain Directory screen appears.

7. On the Select a WebLogic Domain Directory screen, select the location of the existing Oracle Service Bus domain, which should be extended to support Oracle SOA Suite. The Select Extension Source Screen is displayed.

8. On the Select Extension Source screen, select the following domain configuration options:

- Oracle SOA Suite - 11.1.1.0 [Oracle_SOA1]

Note:
When you select the Oracle SOA Suite - 11.1.1.0 [Oracle_SOA1] option, the Oracle WSM Policy Manager - 11.1.1.0 [oracle_common] option is also selected, by default.

For more information, see Oracle Service Bus Domain Configuration Scenarios.

9. After selecting the domain configuration options, click Next. The Configure JDBC Component Schema screen is displayed.

10. On the Configure JDBC Component Schema screen, select a component schema, such as the OSB JMS Reporting Provider Schema, the SOA Infrastructure Schema, the User Messaging Service Schema, the OWSM MDS Schema, or the SOA MDS Schema, that you want to modify.
You can set values for Schema Owner, Schema Password, Database and Service, Host Name, and Port. You must run RCU first, and the values must match the ones used for RCU.

Click Next. The Test JDBC Component Schema screen appears. After the test succeeds, the Select Optional Configuration screen appears.

11. On the Select Optional Configuration screen, you can configure JMS Distributed Destination, Managed Servers, Clusters, and Machines, Deployments and Services, RDBMS Security Store, and so on. Select the relevant check boxes and click Next.

- Optional: Configure JMS Distributed Destination, as required.

- To configure a single Managed Server for Oracle Service Bus and Oracle SOA Suite, do the following:
On the Configure Managed Servers screen, delete the default osb_server1 by selecting osb_server1 and clicking Delete. Then modify the name of soa_server1 as osb_server1 by manually editing the name in the Name column.

Note:
This optional step is required only if you want to have Oracle SOA Suite and Oracle Service Bus running in the same virtual machine. If you skip this step, you will configure a Managed Server each for Oracle SOA Suite and Oracle Service Bus.

- Optional: Configure Clusters, as required.

- Optional: Assign Managed Servers to Clusters, as required.

- Optional: Configure Machines, as needed. This step is useful when you want to run the Administration Server on one machine and Managed Servers on another physical machine.

- Optional: Assign the Administration Server to a machine.

- Optional: Select Deployments, such as applications and libraries, and Services to target them to a particular cluster or server.

- Optional: Configure JMS File Store, as required.

12. On the Configuration Summary screen, review the domain configuration, and click Create to start creating the domain.

The WebLogic domain with your configuration attributes is created.

Note:
For information about creating and starting a Managed Server on a remote machine, see Creating and Starting Managed Servers on a Remote Machine.

5.8 Extending an Oracle SOA Suite WebLogic Domain to Support Oracle Service Bus

This topic describes how to extend an existing Oracle SOA Suite domain to support Oracle Service Bus. It includes the following sections:

- Appropriate Installation Environment

- Components Installed

- Dependencies

- Procedure

5.8.1 Appropriate Installation Environment

Perform the installation and configuration in this topic if you want to extend an existing Oracle SOA 11g domain to support Oracle Service Bus. For information about domain configuration options, see Oracle Service Bus Domain Configuration Scenarios.

Note:
You must install Oracle SOA Suite in the same Middleware Home that contains Oracle Service Bus.

5.8.2 Components Installed

Performing the installation and configuration in this section deploys the following:

- Oracle Service Bus and Oracle SOA Suite on the same Managed Server, or one Managed Server each for Oracle Service Bus and Oracle SOA Suite

- Applications deployed on the Managed Server

- Oracle Service Bus Administration Console deployed on the Administration Server

5.8.3 Dependencies

The installation and configuration in this section depends on the following:

- Oracle WebLogic Server

- Oracle Service Bus 11g

- Oracle SOA Suite 11g

5.8.4 Procedure

Perform the following steps to extend an existing Oracle SOA Suite domain to support Oracle Service Bus:

1. Install Oracle WebLogic Server, as described in Installing Oracle WebLogic Server and Creating the Oracle Middleware Home.

2. Install the Oracle SOA Suite 11g software, as described in Installing the Latest Version of Oracle SOA Suite.

3. Install the Oracle Service Bus 11g software, as described in Installing the Oracle Service Bus 11g Software. Create a new domain for Oracle SOA Suite.

4. Start the Oracle Fusion Middleware Configuration Wizard by running the following command:
On UNIX: <Middleware_Home>/oracle_common/common/bin/config.sh

On Windows: <Middleware_Home>\oracle_common\common\bin\config.bat.

The Oracle Fusion Middleware Configuration Wizard appears.

5. On the Welcome screen, select the Extend an existing WebLogic domain option. Click Next. The Select a WebLogic Domain Directory screen appears.

6. On the Select a WebLogic Domain Directory screen, select the location of the existing Oracle Service Bus domain, which should be extended to support Oracle SOA Suite. The Select Extension Source Screen is displayed.

7. On the Select Extension Source screen, select the following domain configuration options:

- Oracle Service Bus Extension - All Domain Topologies - 11.1.1.3 [Oracle_OSB1]

Note:
When you select the Oracle Service Bus Extension - All Domain Topologies - 11.1.1.3 [Oracle_OSB1] option, the WebLogic Advanced Web Services for JAX-RPC Extension - 10.3.3.0 [wlserver_10.3] option is also selected, by default.

For more information, see Oracle Service Bus Domain Configuration Scenarios.

8. After selecting the domain configuration options, click Next. The Configure JDBC Component Schema screen is displayed.

9. On the Configure JDBC Component Schema screen, select a component schema, such as the OSB JMS Reporting Provider Schema, the SOA Infrastructure Schema, the User Messaging Service Schema, the OWSM MDS Schema, or the SOA MDS Schema, that you want to modify.
You can set values for Schema Owner, Schema Password, Database and Service, Host Name, and Port. Click Next. The Test JDBC Component Schema screen appears. After the test succeeds, the Select Optional Configuration screen appears.

10. On the Select Optional Configuration screen, you can configure JMS Distributed Destination, Managed Servers, Clusters, Machines, Deployments and Services, RDBMS Security Store, and so on. Select the relevant check boxes and click Next.

- Optional: Configure JMS Distributed Destination, as required.

- To configure a single Managed Server for Oracle Service Bus and Oracle SOA Suite, do the following:
On the Configure Managed Servers screen, delete the default soa_server1 by selecting osb_server1 and clicking Delete. Then modify the name of osb_server1 as soa_server1 by manually editing the name in the Name column.

Note:
This optional step is required only if you want to have Oracle SOA Suite and Oracle Service Bus running in the same virtual machine. If you skip this step, you will configure a Managed Server each for Oracle SOA Suite and Oracle Service Bus.

- Optional: Configure Clusters, as required.

- Optional: Assign Managed Servers to Clusters, as required.

- Optional: Configure Machines, as needed. This step is useful when you want to run the Administration Server on one machine and Managed Servers on another physical machine.

- Optional: Assign the Administration Server to a machine.

- Optional: Select Deployments, such as applications and libraries, and Services to target them to a particular cluster or server.

- Optional: Configure JMS File Store, as required.

11. On the Configuration Summary screen, review the domain configuration, and click Create to start configuring the domain.

The WebLogic domain with your configuration attributes is configured.

Note:
For information about creating and starting a Managed Server on a remote machine, see Creating and Starting Managed Servers on a Remote Machine.

5.9 After Creating Oracle Service Bus 11g Domain

After installing and configuring Oracle Service Bus 11g in a new or existing domain, complete the following steps:

1. Start the Administration Server to register the newly created managed servers with the domain. To start the Administration Server, run the following command:

- On Windows: At the command prompt, run the startWebLogic script to start the Administration Server, as in the following example:
\middleware\user_projects\domains\base_domain\bin\startWebLogic

- On UNIX: At the $ prompt, run the startWebLogic.sh script, as in the following example:
sh /Middleware_Home/user_projects/domains/base_domain/bin/startWebLogic.sh

2. Optional: start the Managed Server as follows:
On Windows: At the command prompt, run the startManagedWebLogic script to start a managed server, as in the following example:

\middleware\user_projects\domains\base_domain\bin\startManagedWebLogic osb_server1 http://dadvmh0234:7001

On UNIX: At the $ prompt, run the startManagedWebLogic.sh script, as in the following example:

sh /Middleware_Home/user_projects/domains/base_domain/bin/startManagedWebLogic.sh osb_server1 http://dadvmh0234:7001

Note:
By default, osb_server1 is the name of the new Managed Server. If multiple Managed Servers are configured, the names vary.
This step is not required if you have created a Oracle Service Bus domain with a single server functions as both Administration Server and Managed Server.

3. When prompted, enter the user name and the password for the WebLogic administrator to start the server.

4. When the server is started, at the end of the console, you will see lines similar to the following:
<Apr 16, 2009 5:10:59 PM PDT> <Notice> <WebLogicServer> <BEA-000332> <Started WebLogic Managed Server "osb_server1" for domain "base_domain" running in Development Mode> <Apr 16, 2009 5:10:59 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING> <Apr 16, 2009 5:10:59 PM PDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

Note:
The default port for osb_server1 is 8011.

5.10 Verifying Oracle Service Bus 11g Installation and Domain Configuration

After completing the installation and configuration of Oracle Service Bus, including the post-installation steps, you can verify the installation as follows:

Verify whether you can access the Oracle Service Bus Administration Console:

http://<hostname>:<osb-port>/osbconsole

If the Oracle Service Bus Console starts working, your installation of Oracle Service Bus was successful.

In addition, if you installed Oracle Enterprise Pack for Eclipse with Oracle WebLogic Server, you can try to start the Oracle Service Bus Integrated Development Environment (IDE) to verify the installation.

To launch the Oracle Service Bus IDE, complete the following steps:

- On Windows:
On the Start menu, click Programs > Oracle Service Bus 11g - Home 1 > Oracle Enterprise Pack for Eclipse.

- On UNIX:
Move to the oepe_11gR1PS2 directory under your Oracle Middleware Home, and run the following command:

./eclipse

5.10.1 Verifying the Oracle Service Bus Directory Structure

In addition to the above steps to verify the installation of Oracle Service Bus 11g on your machine, you can verify the directory structure to verify your installation. For more information about the Oracle Service Bus directory structure, see Understanding the Directory Structure After Installation.

5.11 Start Menu Commands on Windows

If you are installing Oracle WebLogic Server and Oracle Service Bus on the Windows operating system, a set of commands are added to the Start menu. You can use them to launch product components and tools, such as Configuration Wizard. You can also use them to perform some basic administrative tasks, such as starting or stopping servers. The Start menu commands are shown as follows:

Oracle WebLogic Server

Oracle Service Bus

5.12 Getting Started with Oracle Service Bus 11g After Installation

After installing Oracle Service Bus, refer to the "Introduction" chapter in the Oracle Fusion Middleware Deployment Guide for Oracle Service Bus.

6 Performing Silent Installations

This chapter describes how to install Oracle Service Bus in silent mode. It contains the following topics:

- What is a Silent Installation?

- Before Performing a Silent Installation

- Creating Response Files

- Performing a Silent Installation

- Installer Command Line Parameters

6.1 What is a Silent Installation?

A silent installation eliminates the need to monitor the Oracle Service Bus installation because no graphical output is displayed and no input by the user is required.

To perform a silent Oracle Service Bus installation, you invoke the Installer with the -silent flag and provide a response file from the command line. The response file is a text file containing variables and parameter values which provide answers to the Installer prompts.

6.2 Before Performing a Silent Installation

This topic describes tasks that may be required before you perform a silent installation. This topic includes the following sections:

- UNIX Systems: Creating the oraInst.loc File

- Windows Systems: Creating the Registry Key

6.2.1 UNIX Systems: Creating the oraInst.loc File

The Installer uses the Oracle inventory directory to keep track of all Oracle products installed on the systems. The inventory directory is stored in a file named oraInst.loc. If this file does not already exist on your system, you must create it before starting a silent installation.

Perform the following steps to create the oraInst.loc file if it does not exist:

1. Log in as the root user.

2. Using a text editor such as vi or emacs, create the oraInst.loc file in any directory. The contents of the file consist of the following two lines:

inventory_loc=oui_inventory_directory
inst_group=oui_install_group

Replace oui_inventory_directory with the full path to the directory where you want the Installer to create the inventory directory. Replace oui_install_group with the name of the group whose members have write permissions to this directory.

3. Exit from the root user.

Note:
After you perform the silent installation on UNIX platforms, you must run the ORACLE_HOME/root.sh script as the root user. The root.sh script detects settings of environment variables and enables you to enter the full path of the local bin directory.

6.2.2 Windows Systems: Creating the Registry Key

If you have not installed Oracle Service Bus on your system, you must create the following Registry key and value:

HKEY_LOCAL_MACHINE / SOFTWARE / Oracle / inst_loc = [inventory_directory]

Replace inventory_directory with the full path to your Installer files. For example: C:Program Files\Oracle\Inventory

6.3 Creating Response Files

Before performing a silent installation, you must provide information specific to your installation in a response file. Response files are text files that you can create or edit in a text editor. The Installer will fail if you attempt a silent installation using a response file that is not configured correctly.

You can create response files using the Installation Summary screen in the Installer. You can install Oracle Service Bus once using the GUI installer to save the response file. This response file can be used for silent installations at a later time.

Alternatively, several default response files, which you can use as templates and customize for your environment, are included in the installation media. These default response files are located in the Disk1/stage/Response directory on UNIX, or in the Disk1\stage\Response directory on Windows.

The following is a list of the default response files included in the installation media:

- custom_installtype.rsp: Use this response file to perform the Custom type of Oracle Service Bus installation.

- typical_installtype.rsp: Use this response file to perform the Typical type of Oracle Service Bus installation.

- deinstall_oh.rsp: Use this response file with the Oracle Service Bus 11g Release 1 (11.1.1.3) Deinstaller to deinstall installed components.

6.3.1 Securing Your Silent Installation

Your response files contain certain passwords required by the Installer. To minimize security issues regarding these passwords in the response file, follow these guidelines:

- Set the permissions on the response files so that they are readable only by the operating system user who will be performing the silent installation.

- If possible, remove the response files from the system after the silent installation is completed.

6.4 Performing a Silent Installation

To perform a silent Oracle Service Bus installation, you invoke the Installer with the -silent flag and provide a response file from the command line.

On UNIX

The following is the syntax for running the Installer from the command line on UNIX systems:

runInstaller [-mode] [-options] [(COMMAND_LINE_VARIABLE=VARIABLE_VALUE)*]

For example:

./runInstaller -silent -response /home/abc/im_install.rsp

On Windows

The following is the syntax for running the Installer from the command line on Windows systems:

setup.exe [-mode] [-options] [(COMMAND_LINE_VARIABLE=VARIABLE_VALUE)*]

For example:

setup.exe -silent -response FILE

6.5 Installer Command Line Parameters

Table (UNKNOWN STEP NUMBER) lists and describes supported Installer command line parameters:

Table 6-1 Installer Command Line Parameters

Parameter

Description

Installation Modes - Only One Mode Can be Specified

-i | -install

Launches the Installer in GUI mode. This is the default mode and is used if no mode is specified on the command line.

-silent

Install in silent mode. The Installer must be passed either a response file or command line variable value pairs.

-d | -deinstall

Launches the Installer in GUI mode for deinstallation.

-p | -prerequisite

Launches the Installer in GUI mode but only checks the prerequisites. No software is installed.

-v | -validate

Launches the Installer in GUI mode and performs all prerequisite and validation checking, but does not install any software.

-sv | -silentvalidate

Performs all prerequisite and validation checking in silent mode. You must pass the Installer either a response file or a series of command line variable value pairs.

Installation Options

-help | --help | --usage

Displays the usage parameters for the runInstaller command.

-invPtrLoc file

Pointer to the inventory location file. Replace file with the full path and name of the oraInst.loc file.

-response file | -responseFile file

Pointer to the response file. Replace file with the full path and name of the response file.

-jreLoc location

Pointer to the location where Java Runtime Environment (JRE) is installed. Replace location with the full path to the jre directory where your JRE is installed.

-logLevel level

Specify the level of logging performed by the Installer; all messages with a lower priority than the specified level will be recorded. Valid levels are:

- severe

- warning

- info

- config

- fine

- finer

- finest

-debug

Obtain debug information from the Installer.

-force

Allow the silent installation to proceed in a non-empty directory.

-printdiskusage

Log debugging information pertaining to disk usage.

-printmemory

Log debugging information pertaining to memory usage.

-printtime

Log debugging information pertaining to time usage. This command causes the timeTakentimestamp.log file to be created.

-waitforcompletion

Windows only - the Installer will wait for completion instead of spawning the Java engine and exiting.

-noconsole

Messages will not be displayed to the console window.

-ignoreSysPrereqs

Ignore the results of the system prerequisite checks and continue with the installation.

-executeSysPrereqs

Execute the system prerequisite checks only, then exit.

-paramFile file

Specify the full path to the oraparam.ini file. This file is the initialization file for the Installer. The default location of this file is Disk1/install/platform.

-novalidation

Disables all validation checking performed by the Installer.

-nodefaultinput

For the GUI install, several screens have information or default values pre-populated. Specifying this option disables this behavior so that no information or values are pre-populated.

Command Line Variables

Installer Variables

Installer variables are specified using varName=value. For example:

ORACLE_HOME=/scratch/install/Oracle_IDM1

Session Variables

Session variables are specified using session:varName=value

A Troubleshooting the Installation

This appendix describes solutions to common problems that you might encounter when installing Oracle Service Bus. It contains the following topics:

- General Troubleshooting Tips

- Installation Log Files

- Need More Help?

A.1 General Troubleshooting Tips

If you encounter an error during installation:

- Consult the Oracle Fusion Middleware 11g Release 1 (11.1.1.3). You can access the Release Notes on the Oracle Technology Network (OTN) Documentation Web site. To access this Web site, go to the following URL:

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

- Verify your system and configuration is certified. See "Oracle Fusion Middleware Certification" for more information.

- Verify your system meets the minimum system requirements. See "System Requirements" for more information.

- Verify you have satisfied the dependencies for the deployment you are attempting. Each deployment documented in this guide contains a "Dependencies" section.

- If you entered incorrect information on one of the installation screens, return to that screen by clicking Back until you see the screen.

- If an error occurred while the Installer is copying or linking files:

1. Note the error and review the installation log files.

2. Remove the failed installation.

3. Correct the issue that caused the error.

4. Restart the installation.

A.2 Installation Log Files

The Installer writes log files to the ORACLE_INVENTORY_LOCATION/logs directory on UNIX systems and to the ORACLE_INVENTORY_LOCATION\logs directory on Windows systems.

On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the ORACLE_HOME/oraInst.loc file.

On Microsoft Windows systems, the default location for the inventory directory is C:\Program Files\Oracle\Inventory\logs.

The following install log files are written to the log directory:

- installDATE-TIME_STAMP.log

- installDATE-TIME_STAMP.out

- installActionsDATE-TIME_STAMP.log

- installProfileDATE-TIME_STAMP.log

- oraInstallDATE-TIME_STAMP.err

- oraInstallDATE-TIME_STAMP.log

A.3 Need More Help?

If you cannot solve a problem using the information in this appendix, look for additional information in My Oracle Support (formerly MetaLink) at http://metalink.oracle.com.

If you cannot find a solution to your problem, open a service request.

B Deinstalling and Reinstalling Oracle Service Bus

This appendix provides information about deinstalling and reinstalling Oracle Service Bus 11g Release 1 (11.1.1.3). It contains the following topics:

- Deinstalling Oracle Service Bus 11g Release 1 (11.1.1.3)

- Reinstalling Oracle Service Bus 11g Release 1 (11.1.1.3)

Note:
Always use the instructions provided in this appendix for removing the software. If you try to remove the software manually, you may experience problems when you try to reinstall the software. Following the procedures in this appendix ensures that the software is properly removed.

B.1 Deinstalling Oracle Service Bus 11g Release 1 (11.1.1.3)

This topic contains procedures for deinstalling Oracle Service Bus 11g Release 1 (11.1.1.3) and contains the following sections:

- Deinstalling Oracle Service Bus Oracle Home

- Deinstalling Oracle Common Home

B.1.1 Deinstalling Oracle Service Bus Oracle Home

The deinstaller attempts to remove the Oracle Home directory from which it was started. Before you choose to remove your Oracle Service Bus Oracle Home directory, make sure that it is not in use by an existing domain and that you stop all running processes that use this Oracle Home.

Deinstalling Oracle Service Bus will not remove any WebLogic administration domains that you have created—it only removes the software in the Oracle Service Bus Oracle Home directory.

This topic describes how to deinstall Oracle Service Bus 11g Release 1 (11.1.1.3) using the graphical, screen-based deinstaller. However, you can also perform a silent deinstallation using a response file. A deinstall response file template that you can customize for your deinstallation is included in the Disk1/stage/Response directory on UNIX, or in the Disk1\stage\Response directory on Windows.

Perform the following steps to deinstall Oracle Service Bus Oracle Home using the graphical, screen-based deinstaller:

1. Verify your Oracle Service Bus Oracle Home is not in use by an existing domain.

2. Stop all processes that use the Oracle Service Bus Oracle Home.

3. Open a command prompt and move (cd) into the Oracle_Service_Bus_Oracle_Home/oui/bin directory (UNIX) or the Oracle_Service_Bus_Oracle_Home\oui\bin directory (Windows).

4. Invoke the Deinstaller from command line using the -deinstall option. For example:
On UNIX:

./runInstaller -deinstall

On Windows:

setup.exe -deinstall

The Welcome screen appears.

5. Click Next. The Deinstall Oracle Home screen appears.

6. In the Deinstall Oracle Home screen, you can save a response file that contains the deinstallation settings before deinstalling. Click Deinstall. The Deinstall Progress screen appears. This screen shows the progress and status of the deinstallation. If you want to quit before the deinstallation is completed, click Cancel.

7. Click Finish after the deinstallation progresses to 100%. The Deinstallation Complete screen appears.

8. Click Finish on the Deinstallation Complete screen to exit the deinstaller.

B.1.2 Deinstalling Oracle Common Home

The ORACLE_COMMON_HOME directory located in the MW_HOME directory contains the binary and library files required for Oracle Enterprise Manager Fusion Middleware Control and Java Required Files (JRF). Before you deinstall the ORACLE_COMMON_HOME directory, ensure that no other Oracle Fusion Middleware software, such as Oracle SOA Suite, depends on ORACLE_COMMON_HOME. You cannot deinstall the ORACLE_COMMON_HOME directory until all software that depends on it has been deinstalled.

Perform the following steps to deinstall the ORACLE_COMMON_HOME directory:

1. Stop all processes that use the ORACLE_COMMON_HOME directory.

2. Deinstall your Oracle Service Bus Oracle Home by performing the steps in Deinstalling Oracle Service Bus Oracle Home.

3. Open a command prompt and move (cd) into the ORACLE_COMMON/oui/bin/ directory (on UNIX) or the ORACLE_COMMON_HOME\oui\bin\ directory (on Windows).

4. Invoke the Deinstaller from command line using the -deinstall option and the -jreLoc option, which identifies the location where Java Runtime Environment (JRE) is installed. For example:
On UNIX:

./runInstaller -deinstall -jreLoc FULL_PATH_TO_JRE_DIRECTORY

On Windows:

setup.exe -deinstall -jreLoc FULL_PATH_TO_JRE_DIRECTORY

The Welcome screen appears.

5. Click Next. The Select Deinstallation Type screen appears.

6. Select the Deinstall Oracle Home option at the top of the Select Deinstallation Type screen.

Note:
The path to the ORACLE_COMMON_HOME directory appears in the text describing the Deinstall Oracle Home option.

Click Next. The Deinstall Oracle Home screen appears.

7. Confirm the correct ORACLE_COMMON_HOME directory is listed and click Deinstall.
The Deinstallation Progress screen appears, along with a Warning dialog box prompting you to confirm that you want to deinstall the ORACLE_COMMON_HOME directory.

8. Click Yes on the Warning dialog box to confirm you want to remove the ORACLE_COMMON_HOME directory. The deinstallation begins.

9. Click Finish after the deinstallation progresses to 100%. The Deinstallation Complete screen appears.

10. Click Finish on the Deinstallation Complete screen to exit the deinstaller.

B.2 Reinstalling Oracle Service Bus 11g Release 1 (11.1.1.3)

Perform the following steps to reinstall Oracle Service Bus 11g Release 1 (11.1.1.3):

1. Verify the directory you want to reinstall Oracle Service Bus into does not contain an existing Oracle Service Bus instance. If it does, you must deinstall it before reinstalling. You cannot reinstall Oracle Service Bus 11g Release 1 (11.1.1.3) in a directory that contains an existing Oracle Service Bus instance.

2. Reinstall Oracle Service Bus as if it was the first installation by performing the steps in the appropriate procedure in this guide.

C Oracle Service Bus Software Installation Screens

This appendix contains screenshots and descriptions for screens in the Oracle Fusion Middleware 11g Service Bus Installer, which is used to install the Oracle Service Bus 11g software.

It contains the following topics:

- Welcome Screen

- Select Installation Type Screen

- Prerequisite Checks Screen

- Select Components Screen

- Specify Installation Location Screen

- Installation Summary Screen

- Install Progress Screen

- Installation Completed Screen

C.1 Welcome Screen

The Welcome screen is displayed each time you start the installer for Oracle Service Bus.

Click Next to continue.

C.2 Select Installation Type Screen

The Select Installation Type screen offers the following options:

- Typical: installs Oracle Service Bus and Oracle Service Bus binaries in the Oracle home.

- Custom: allows you to choose which Oracle Service Bus component you want to install on your system. The components to select from include the Oracle Service Bus server, Oracle Service Bus IDE, and Oracle Service Bus examples.

Click Next to continue after making your selection.

C.3 Prerequisite Checks Screen

The installation program ensures that you have a certified version, the correct software packages, sufficient space and memory to perform the operations that you have selected.

If there is a problem, a short error message appears in the bottom portion of the screen. Fix the error and click Retry to try again.

If you want to ignore the errors or warnings and continue with the installation, click Continue.

Click Abort to stop prerequisite checking for all components.

C.4 Select Components Screen

The Select Components screen is displayed only when you choose the Custom type of installation on the Select Installation Type screen.

Note that the Oracle Service Bus Server is a required component. You can select either Oracle Service Bus IDE or Oracle Service Bus Examples on this screen.

After selecting the components to install, click Next.

C.5 Specify Installation Location Screen

Enter the following information on the Specify Installation Location screen:

- Oracle Middleware Home Location
The absolute path to the directory where WebLogic Server was installed.

- Oracle Home Directory
The directory name for your Oracle Home:

- You can specify a directory that already exists; this must be an empty directory inside the Oracle Middleware Home (for example, you have created an empty directory inside the Middleware Home in advance of this installation and should specify this directory here).

- You can specify a pre-existing Oracle Home directory (for example, you are reinstalling the software into an existing Oracle Home that was created from a previous installation that was incomplete).

- You can specify the name of a new directory that will be created for you inside the Middleware Home.

Your Oracle Home directory where your products will be installed. All software binaries will reside in this directory, and no runtime process can write to this directory.

Note:
This installation directory is referred to as ORACLE_HOME throughout the remainder of this document.

- Oracle WebLogic Server Location
The directory name for your WebLogic Server Home. This directory will automatically be created inside the Middleware Home. The default name for this directory is wlserver_10.3.

- OEPE (Oracle Enterprise Pack for Eclipse) Location
The OEPE directory name. This directory will automatically be created inside the Middleware Home.

Refer to "Oracle Fusion Middleware Directory Structure and Concepts" in Oracle Fusion Middleware Installation Planning Guide for more information about these directories.

If you are performing an installation on a Windows operating system, be sure that your directory paths are valid and do not contain double backslashes (\\).

After specifying the installation directories, click Next.

C.6 Installation Summary Screen

The Installation Summary screen displays the following details:

- Directory Details

- Disk Space

- Components

Click Save to save the installation response file, which contains your responses to the Installer prompts and fields. You can use this response file to perform silent installations.

Note:
The installation response file is not saved, by default—you must click Save to retain it.

Refer to "Oracle Fusion Middleware Directory Structure and Concepts" in Oracle Fusion Middleware Installation Planning Guide for more information about these directories.

Review the contents of this screen, and click Install to start installing the Oracle Service Bus 11g software.

C.7 Install Progress Screen

This screen shows the progress of the installation of Oracle Service Bus products and components. When the installation progress is shown as 100%, click Next.

C.8 Installation Completed Screen

The Installation Completed screen displays the result of the Oracle Service Bus installation. Click Finish to exit.

D WebLogic Domain Configuration Screens

This appendix describes the screens in the Oracle Fusion Middleware Configuration Wizard that enables you to create or extend a WebLogic administration domain. This appendix contains the following topics:

- Welcome

- Select a WebLogic Domain Directory

- Select Domain Source

- Select Extension Source

- Specify Domain Name and Location

- Configure Administrator User Name and Password

- Configure Server Start Mode and JDK

- Configure JDBC Component Schema

- Test Component Schema

- Select Optional Configuration

- Configure the Administration Server

- Select JMS Distributed Destination Type

- Configure Managed Servers

- Configure Clusters

- Assign Servers to Clusters

- Configure Machines

- Assign Servers to Machines

- Target Deployments to Clusters or Servers

- Target Services to Clusters or Servers

- Configure RDBMS Security Store Database

- Configure JMS File Stores

- Configuration Summary

D.1 Welcome

The Welcome screen is displayed each time you start the Oracle Fusion Middleware Configuration Wizard.

Select Create a new WebLogic domain to create a new WebLogic domain in your projects directory.

Select Extend an existing WebLogic domain if you want to add applications and services, or to override existing database access (JDBC) and messaging (JMS) settings.

Click Next to continue.

D.2 Select a WebLogic Domain Directory

This screen is displayed only if you choose to extend an existing WebLogic domain to support the new products.

Select the WebLogic directory to which you want to add your applications, or services, or both.

Click Next to continue.

D.3 Select Domain Source

The Select Domain Source screen enables you to select a domain source from which you want to create a new domain.

Select Generate a domain configured automatically to support the following products: to create your domain to support selected products. Then, select the products for which you want support.

Select Base this domain on an existing template to create your domain based on an existing domain template. By default, domain templates for Oracle Service Bus 11g components are located in your templates directory (Oracle_Home\common\templates\applications on Windows, and Oracle_Home\common\templates\applications on UNIX). Click Browse to navigate your directories to find an existing template.

Click Next to continue.

D.4 Select Extension Source

This screen is displayed only if you choose to extend an existing WebLogic domain to support the new products.

Select Extend my domain automatically to support the following added products: to extend your domain to support selected products. Then, select the products for which you want support.

Select Extend my domain using an existing extension template to extend your domain based on an existing extension template. Click Browse to navigate your directories to find an existing template.

Click Next to continue.

D.5 Specify Domain Name and Location

In this screen, you enter a name and location for the new WebLogic domain being created.

Enter a name for the new WebLogic domain, and select the location where the new domain must be created.

Click Next to continue.

D.6 Configure Administrator User Name and Password

This screen is displayed only if you choose to create a new WebLogic domain.

Create a user that will be assigned to the Administrator role. This user is the default administrator used to start development mode servers.

- User name - Specify the user name.

- User password - Specify the password for the user.

- Confirm user password - Re-enter the user password.

- Description - Enter a description for the user. This field is optional.

Click Next to continue.

D.7 Configure Server Start Mode and JDK

This screen is displayed only if you choose to create a new WebLogic domain.

In the WebLogic Domain Startup Mode section, select one of the following startup modes:

- Development Mode
In this mode, boot.properties is used for user names and passwords, and polling is used for application deployment. Sun JDK is the default for this mode.

- Production Mode
In this mode, user names and passwords are required, and polling is not used for application deployment. WebLogic JRockit JDK is the default for this mode.

In the JDK Selection section, select a JDK from the list of available JDKs, or select Other JDK and click Browse to find another JDK on your system.

Click Next to continue.

D.8 Configure JDBC Component Schema

This screen is displayed only if you choose to extend an existing WebLogic domain to support a new product.

Use this screen to edit the configuration information for each JDBC data source.

A data source contains a pool of database connections. Your application uses a data source by looking it up in the JNDI tree, requesting a connection, using the connection, and then returning the connection to the data source.

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.

Click Next to continue.

D.9 Test Component Schema

This screen displays the test results.

D.10 Select Optional Configuration

This screen provides you with options to configure and customize any of the server or cluster settings listed.

D.11 Configure the Administration Server

This screen is displayed only if you choose to create a new WebLogic domain.

Each WebLogic Server domain must have one Administration Server, which hosts the Administrative Console used to perform administration tasks.

Click Next to continue.

D.12 Select JMS Distributed Destination Type

This screen is displayed only if you select the JMS Distributed Destination option on the Select Optional Configuration screen.

This screen enables you to select either Weighted Distributed Destinations (WDD) or United Distributed Destinations (UDD) as the type of JMS distributed destination. UDD is recommended.

After selecting an option, click Next to continue.

D.13 Configure Managed Servers

This screen enables you to configure Managed Servers. A Managed Server is an instance of Oracle WebLogic Server used to host enterprise applications. A typical production environment has at least one Managed Server.

You can create a domain with one server acting as Administration Server and Manager Server, or you can create a domain with separate Administration Server and Managed Server.

Use this screen to add or delete Managed Servers. By deleting a server in this screen, you are configuring a single server both Oracle Service Bus and Oracle SOA Suite in co-existence scenarios.

For each Managed Server, specify:

- Name
Name of the Managed Server.

- Listen Address
Select an address from the drop-down list; the server will listen on the specified addresses.

- Listen Port
Listen port number.

- SSL Listen Port
Port number for SSL connections - this column is only active if the corresponding "SSL enabled" check box in the same row is selected.

Click Next to continue.

D.14 Configure Clusters

This screen enables you to configure clusters. A cluster contains multiple WebLogic Server instances running simultaneously and working together for scalability and reliability. To clients, a cluster appears as a single WebLogic Server instance.

Use this screen to add or delete configuration information for clusters.

Click Next to continue.

D.15 Assign Servers to Clusters

This screen enables you to assign a Managed Server to the cluster.

Select a cluster in the right pane, and select a Managed Server in the left pane. Assign the Managed Server to the cluster by clicking the right arrow button.

Click Next to continue.

D.16 Configure Machines

This screen enables you to configure machines that host WebLogic Servers.

Use this screen to add or delete machines.

The Administration Server and Node Manager use the machine definition on this screen to start remote servers.

Click Next to continue.

D.17 Assign Servers to Machines

This screen enables you to assign each WebLogic Server instance to the corresponding machine on which it runs.

Select a machine in the right pane, and select a server in the left pane. Assign the server to the machine by clicking the right arrow button.

Click Next to continue.

D.18 Target Deployments to Clusters or Servers

This screen enables you to target your deployments to servers or clusters. Doing so enables WebLogic Server to serve the deployment to clients.

Select clusters or servers in the left pane, and select the check boxes corresponding to applications in the right pane to target them to the selected clusters or servers.

Click Next to continue.

D.19 Target Services to Clusters or Servers

This screen enables you to target your services (for example, JMS, JDBC, startup and shutdown classes) to servers or clusters. Doing so enables your applications to use these services.

Select clusters or servers in the left pane, and select the check boxes corresponding to services in the right pane to target them to the selected clusters or servers.

Click Next to continue.

D.20 Configure RDBMS Security Store Database

This screen enables you to configure an RDBMS security store database.

Click I want to create, change, or remove RDBMS support to make changes to your RDBMS. Make sure that your RDBMS tables are created prior to booting your domain. The scripts used by the DBA are located in the WebLogic Server server/lib directory.

Click I don't want to change anything here if you do not want to make any changes to your security store.

Click Next to continue.

D.21 Configure JMS File Stores

This screen is displayed only if you choose to extend an existing WebLogic domain to support the new product.

In this screen, you can configure a JMS file store. In addition, you can select a synchronous write policy: Cache-Flush, Direct-Write, or Disabled

Click Next to continue.

D.22 Configuration Summary

This screen displays a summary of your domain configuration.

Review the contents of your domain.

Click Create to start configuring your domain.

E Oracle Service Bus Deinstallation Screens

This appendix contains screenshots and descriptions for the Oracle Service Bus 11g software deinstallation screens. The deinstaller wizard enables you to remove the Oracle Service Bus 11g software from your machine.

It contains the following sections:

- Welcome Screen

- Deinstall Oracle Home Screen

- Deinstallation Progress Screen

- Deinstallation Completed Screen

E.1 Welcome Screen

The Welcome screen is displayed each time you start the deinstallation wizard for Oracle Service Bus.

Click Next to continue.

E.2 Deinstall Oracle Home Screen

This screen shows the Oracle Home directory that is about to be deinstalled. It is the Oracle Home directory in which the deinstaller was started.

Verify that this is the correct directory, and also verify that there are no processes associated with this Oracle Home.

Click Deinstall to start the deinstallation process.

E.3 Deinstallation Progress Screen

This screen shows the progress of deinstallation. When the progress is shown as 100%, click Next.

E.4 Deinstallation Completed Screen

The Deistallation Completed screen displays the result of the Oracle Service Bus deinstallation.

After deinstallation, you can reinstall Oracle Service Bus in same ORACLE_HOME, if required.

Index
A  M  O  W

A

accessibility software, Java Access Bridge, C, E

M

Middleware Home, C.5

O

Oracle Home, C.5

W

WebLogic Server directory, C.5

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

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.

License Restrictions Warranty/Consequential Damages Disclaimer

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.

Warranty Disclaimer

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.

Restricted Rights Notice

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 END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

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.

Third-Party Content, Products, and Services Disclaimer

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.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.