3 Configuring Oracle Service Bus

This chapter describes how to configure Oracle Service Bus after you have installed the software. It includes the following topics:

3.1 Configuration Instructions

After the installation is complete, you must run the Oracle Fusion Middleware Configuration Wizard to create and configure a new WebLogic domain, and choose the products that you want to configure in that domain. If you have an existing domain, you can use the Configuration Wizard to extend the existing domain to support additional products and features.

This new domain will contain the Administration Server and other Managed Servers depending on the products you choose to configure.

After you have created a new domain, you can later extend that domain if you want to add more products to that domain.

See "Understanding Oracle WebLogic Server Domains" in Oracle Fusion Middleware Understanding Domain Configuration for Oracle WebLogic Server for more information about Oracle WebLogic Server administration domains.

3.1.1 Using Default Settings for Managed Servers

During the configuration, the Oracle Fusion Middleware Configuration Wizard automatically creates managed servers in the domain to host the Fusion Middleware system components. Oracle recommends that you use the default configuration settings for these managed servers. If you modify the default configuration settings, then you will have to perform some manual configuration steps before the Fusion Middleware environment can be started.

3.1.2 Using Default Setting for Targeting Deployments and Services

On the Select Optional Configuration screen, if you select Deployments and Services, you will get the following two screens for additional configuration:

These screens allow you to select deployments, such as applications and libraries, and services to target them to a particular cluster or server. However, you should not change the Oracle Service Bus deployment targets unless specifically instructed in the documentation.

3.1.3 Shutting Down Running Managed Servers

Before you start the Configuration Wizard, you must shut down any Managed Servers that are currently running. If you do not, validation of your Managed Servers will fail due to port number conflicts from the managed servers that are currently running.

For more information, see "Starting and Stopping Oracle Fusion Middleware" in Oracle Fusion Middleware Administrator's Guide.

3.1.4 Starting the Oracle Fusion Middleware Configuration Wizard

The Configuration Wizard is located in the OSB_ORACLE_HOME/common/bin (on UNIX operating systems) or OSB_ORACLE_HOME\common\bin (on Windows operating systems) directory. Go to this directory, then run the config.sh (on UNIX operating systems) or config.cmd (on Windows operating systems) script to start the Configuration Wizard:

On UNIX operating systems:

./config.sh

On Windows operating systems:

config.cmd

If you are using a 32-bit operating system, Oracle JRockit SDK is installed as part of the Oracle WebLogic installation. This is the JDK that the Configuration Wizard will use by default. If you want to invoke the Configuration Wizard with the Sun JDK, do the following prior to starting the Configuration Wizard:

  1. Set the JAVA_HOME environment variable to the location of the Sun JDK. For example, you can set it to the Sun JDK that was installed with Oracle WebLogic Server in the MW_HOME/jdk160_21 (on UNIX operating systems) or MW_HOME\jdk160_21 (on Windows operating systems) directory.

  2. Set the JAVA_VENDOR environment variable to "Sun."

After you have started the Configuration Wizard, find the scenario that best describes your environment, and proceed to that section to configure your domain:

3.1.5 Configuration Log Files

To create a log file for your configuration session, use the -log=log_filename parameter when you start the Configuration Wizard.

On UNIX operating systems:

./config.sh -log=log_filename

On Windows operating systems:

config.cmd -log=log_filename

Log files of your configuration session are created in the OSB_ORACLE_HOME/common/bin (on UNIX operating systems) or OSB_ORACLE_HOME\common\bin (on Windows operating systems) directory. For more information about the Configuration Wizard log files, see Section D.2, "Installation and Configuration Log Files".

3.2 Creating a WebLogic Domain with Only Oracle Service Bus

This section describes how to create a WebLogic Domain with only Oracle Service Bus. Performing the instructions 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

Begin by starting the Configuration Wizard, as described in Section 3.1.4, "Starting the Oracle Fusion Middleware Configuration Wizard".

After you have started the Configuration Wizard, follow the instructions in "Creating a WebLogic Domain" in Oracle Fusion Middleware Creating Domains Using the Configuration Wizard to create a new WebLogic domain for your Oracle Service Bus components.

The following screens have special instructions for configuring Oracle Service Bus; they are described in the remainder of this section:

Select Domain Source Screen

On the Select Domain Source screen, select Generate a domain configured automatically to support the following products:, then select one of the following options:

  • Oracle Service Bus for Developers - 11.1.1.4 [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.

  • Oracle Service Bus - 11.1.1.4 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

After selecting either option, the following components are also selected by default as dependencies:

  • Oracle JRF - 11.1.1.0 [oracle_common]

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

In addition, after selecting either Oracle Service Bus for Developers - 11.1.1.4 [Oracle_OSB1] or Oracle Service Bus - 11.1.1.4 [Oracle_OSB1], you can also select Oracle Service Bus OWSM Extension - 11.1.1.4 [Oracle_OSB1] to create a domain with Oracle Service Bus with runtime support for Oracle Web Services Manager policies. If you select this component, Oracle WSM Policy Manager - 11.1.1.0 [oracle_common] is also selected as a dependency.

In addition, select Oracle Enterprise Manager - 11.1.1.0 [oracle_common] 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).

Configure JDBC Component Schema Screen

If you choose to use the Derby evaluation database, make sure the following are selected on this screen:

  • 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.

3.3 Creating a Single WebLogic Domain with Oracle Service Bus and Oracle SOA Suite

This section describes how to create a single WebLogic Domain with both Oracle Service Bus and Oracle SOA Suite components. Performing the instructions 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

3.3.1 Installing the Latest Version of Oracle SOA Suite

If you do not already have Oracle SOA Suite installed on your system, follow the instructions in Oracle Fusion Middleware Installation Guide for Oracle SOA Suite and Oracle Business Process Management Suite to install the latest version of Oracle SOA Suite.

3.3.2 Instructions for Creating the Domain

After you have Oracle Service Bus and Oracle SOA Suite installed on your system, begin domain creation by starting the Configuration Wizard, as described in Section 3.1.4, "Starting the Oracle Fusion Middleware Configuration Wizard".

After you have started the Configuration Wizard, follow the instructions in "Creating a WebLogic Domain" in Oracle Fusion Middleware Creating Domains Using the Configuration Wizard to create a new WebLogic domain for your Oracle Service Bus and Oracle SOA Suite components.

The following screens have special instructions for this configuration; they are described in the remainder of this section:

Select Domain Source Screen

On the Select Domain Source screen, select Generate a domain configured automatically to support the following products: and then select the following:

  • Oracle SOA Suite - 11.1.1.0 [Oracle_SOA1]

    Both Oracle JRF - 11.1.1.0 [oracle_common] and Oracle WSM Policy Manager - 11.1.1.0 [oracle_common] are automatically selected as dependencies.

  • Oracle Service Bus - 11.1.1.4 [Oracle_OSB1]

    WebLogic Advanced Web Services for JAX-RPC Extension - 10.3.4.0 [wlserver_10.3] is also automatically selected as a dependency.

Configure Managed Servers Screen

If you want 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.

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

This section describes how to extend an existing Oracle Service Bus domain to support Oracle SOA Suite. Performing the instructions 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

3.4.1 Installing the Latest Version of Oracle SOA Suite

If you do not already have Oracle SOA Suite installed on your system, follow the instructions in Oracle Fusion Middleware Installation Guide for Oracle SOA Suite and Oracle Business Process Management Suite to install the latest version of Oracle SOA Suite.

3.4.2 Instructions for Extending the Domain

Begin by starting the Configuration Wizard, as described in Section 3.1.4, "Starting the Oracle Fusion Middleware Configuration Wizard".

After you have started the Configuration Wizard, follow the instructions in "Extending WebLogic Domains" in Oracle Fusion Middleware Creating Domains Using the Configuration Wizard to extend your existing Oracle Service Bus domain for Oracle SOA Suite.

The following screens have special instructions for this configuration; they are described in the remainder of this section:

Select Extension Source Screen

On the Select Extension Source screen, select the Oracle SOA Suite - 11.1.1.0 [Oracle_SOA1] domain configuration option. The Oracle WSM Policy Manager - 11.1.1.0 [oracle_common] option is also automatically selected.

Configure Managed Servers Screen

If you want 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.

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

This section describes how to extend an existing Oracle SOA Suite domain to support Oracle Service Bus. Performing the instructions 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

3.5.1 Selecting the "Refresh Replica at Startup" Option

This scenario requires that the following procedure be performed prior to configuring the domain and components:

  1. Go to the WebLogic Server Administration console.

  2. Select Domain (top of the tree in the navigation panel on the left side).

  3. Select the Security tab.

  4. Select the Embedded tab.

  5. Select the Refresh Replica At Startup option.

  6. Save and apply your changes.

3.5.2 Configuring Your Domain

Begin by starting the Configuration Wizard, as described in Section 3.1.4, "Starting the Oracle Fusion Middleware Configuration Wizard".

After you have started the Configuration Wizard, follow the instructions in "Extending WebLogic Domains" in Oracle Fusion Middleware Creating Domains Using the Configuration Wizard to extend your Oracle SOA Suite domain for Oracle Service Bus.

The following screens have special instructions for this configuration; they are described in the remainder of this section:

Select Extension Source Screen

On the Select Extension Source screen, select the Oracle Service Bus - 11.1.1.4 [Oracle_OSB1] domain configuration option. The WebLogic Advanced Web Services for JAX-RPC Extension - 10.3.4.0 [wlserver_10.3] option is also automatically selected.

Configure Managed Servers Screen

If you want 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.

3.6 Starting the Servers

To get your deployments up and running, you must start the Administration Server and various Managed Servers:

3.6.1 Starting the Administration Server

To start the Administration Server, run the startWebLogic.sh (on UNIX operating systems) or startWebLogic.cmd (on Windows operating systems) script in the directory where you created your new domain.

On UNIX systems:

DOMAIN_HOME/startWebLogic.sh

On Windows systems:

DOMAIN_HOME\startWebLogic.cmd

The DOMAIN_HOME consists of your domain location and domain name, which was specified on the Specify Domain Name and Location Screen in the Configuration Wizard.

3.6.2 Starting the Managed Servers

To start the Managed Servers, run the DOMAIN_HOME/bin/startManagedWebLogic.sh (on UNIX operating systems) or DOMAIN_HOME\bin\startManagedWebLogic.cmd (on Windows operating systems) script. These Managed Servers must be started from the command line.

This command also requires that you specify a server name. The servers that need to be started (depending on your configuration) are:

  • soa_server1 (Oracle SOA Server)

  • osb_server1 (Oracle Service Bus Server)

For example, to start Oracle SOA Server on a UNIX system:

DOMAIN_HOME/bin/startManagedWebLogic.sh soa_server1

On Windows systems:

DOMAIN_HOME\bin\startManagedWebLogic.cmd soa_server1

Before the managed server is started, you will be prompted for the WebLogic Server user name and password. These were provided on the Configure Administrator Username and Password Screen in the Configuration Wizard.

If you do not know the names of the Managed Servers that need to be started, you can view the contents of the following file on UNIX systems:

DOMAIN_HOME/startManagedWebLogic_readme.txt

On Windows systems:

DOMAIN_HOME\startManagedWebLogic_readme.txt

Or, you can access the Administration Server console at the following URL:

http://host:admin_server_port/console

Supply the user name and password that you specified on the Configure Administrator Username and Password Screen of the Configuration Wizard. Then, navigate to Environment > Servers to see the names of your managed servers.

3.6.3 Starting the Servers Using Non-Default Port Numbers and Remote Hosts

If your Administration Server is using a non-default port, or resides on a different host than your managed servers (in a distributed environment), you must also specify the URL to access your Administration Server.

On UNIX systems:

DOMAIN_HOME/bin/startManagedWebLogic.sh soa_server1 http://administration_server_host:administration_server_port

On Windows systems:

DOMAIN_HOME\bin\startManagedWebLogic.cmd soa_server1 http://administration_server_host:administration_server_port

Instead of being prompted for the Administration Server user name and password, you can also specify them directly from the command lime.

On UNIX systems:

DOMAIN_HOME/bin/startManagedWebLogic.sh soa_server1 http://administration_server_host:administration_server_port -Dweblogic.management.username=user_name -Dweblogic.management.password=password

On Windows systems:

DOMAIN_HOME\bin\startManagedWebLogic.cmd soa_server1 http://administration_server_host:administration_server_port -Dweblogic.management.username=user_name -Dweblogic.management.password=password

3.6.4 Verifying That the Servers Have Started

When the servers are 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>

3.7 Verifying Your Oracle Service Bus Installation and Domain Configuration

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

  • Verify whether you can access the Oracle Service Bus Administration Console.

    The URL for the console is:

    http://hostname:osb_port_number/sbconsole

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

  • 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:

    • On Windows operating systems, go to the Start menu and select Programs > Oracle Service Bus 11g - Home 1 > Oracle Enterprise Pack for Eclipse.

    • On UNIX operating systems, go to the MW_HOME/oepe_11gR1PS3 directory and run the following command:

      ./eclipse

  • Verify your Oracle Service Bus directory structure.

    Use Figure 1-2, "Sample Topology for a Development Environment Installation" and Figure 1-4, "Sample Topology for a Production Environment Installation" as guides.

3.8 Start Menu Commands on Windows Operating Systems

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

Description of startone.jpg follows
Description of the illustration startone.jpg

Oracle Service Bus

Description of starttwo.jpg follows
Description of the illustration starttwo.jpg

3.9 Getting Started with Oracle Service Bus After Installation and Configuration

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