Skip Headers
Oracle® Fusion Middleware SOA Suite VM Template for Exalogic Readme File

E51439-01
 
 

Oracle® Fusion Middleware SOA Suite VM Template for Exalogic

Readme File

E51439-01

February 6, 2014

This document contains the following sections:

1 Purpose and Overview of the Oracle SOA Suite VM Template

Use the Oracle SOA Suite VM template to demonstrate how to quickly download, deploy, and use a prepackaged, Oracle-provided Oracle SOA Suite 11g Release 1 (11.1.1.7.0) VM template in an Exalogic Elastic Cloud virtual environment.

Specifically, the VM template is supported on the Exalogic Elastic Cloud Software (EECS) 2.0.6.0.0 software.

The Oracle SOA Suite VM template topology consists of a single Oracle WebLogic Server domain with a SOA Cluster, an Oracle Service Bus (OSB) Cluster, and an Oracle Web Services Manager (OWSM) Cluster shared by SOA and OSB. The deployment profile is a single machine installation with one managed server per cluster.

This physical environment for this template was built using the standard Oracle WebLogic Server and Oracle Fusion Middleware installation and configuration tools.

2 Understanding the Oracle SOA Suite VM Template Topology

The following sections describes the characteristics of the Oracle WebLogic Server and Coherence assembly:

2.1 Topology Diagram for the Oracle SOA Suite VM Template

Figure 1 shows the software components that are installed when you create a vServer on an Exalogic machine by using the Oracle SOA Suite VM template.

For a description of the topology, see Section 2.2.

Figure 1 Oracle SOA Suite VM Template Default Topology After Deployment on Exalogic

Surrounding text describes Figure 1 .

2.2 Description of the Default VM Template Topology Diagram

The following sections describe the Oracle SOA Suite VM Template topology:

2.2.1 Exalogic Rack and Oracle Virtual Environment Configuration

The Oracle SOA Suite VM Template is designed to be deployed to an Exalogic machine in a virtual configuration. During deployment, the VM Template is deployed to an Oracle VM Server (OVS) node and as a single vServer instance on the OVS Node.

You can later scale out the environment by adding additional vServers, but by default, the VM template is deployed as a single vServer.

For more information about creating and managing the Exalogic vDC, see the Oracle Exalogic Elastic Cloud Administrator's Guide.

2.2.2 Overview of the Oracle WebLogic Server Domain Configuration

The Oracle SOA Suite VM Template includes an Oracle WebLogic Server domain that is configured to work as a starting point for a Oracle SOA Suite production environment.

The domain used to create the VM Template was configured using the standard Oracle WebLogic Server and Oracle Fusion Middleware installation and configuration tools. It is based on a standard installation of Oracle WebLogic Server 10.3.6 and Oracle SOA Suite 11g Release 1 (11.1.1.7.0).

The domain was configured using the standard best practices, which are documented in the Oracle Fusion Middleware High Availability Guide and Oracle Fusion Middleware Order Demo Developer's Guide for Oracle SOA Suite in the Oracle Fusion Middleware 11g Release 1 (11.1.1.7.0) documentation library.

From this initial topology, you can later scale up (add additional Managed servers for more computing power and better performance) or scale out (add additional vServers for load balancing and high availability) as necessary and as your application deployment and business needs grow.

2.2.3 Managed Servers and Clusters in the Domain

To serve as a foundation for a production environment, the Oracle WebLogic Server domain includes:

  • An Administration Server, where the Oracle WebLogic Server Administration Console and Oracle Enterprise Manager Fusion Middleware Control are deployed.

  • An Oracle WebLogic Server cluster for the core SOA Infrastructure components (soa_cluster), which contains a single Managed Server (SOAServer_1)

  • A cluster for Oracle Service Bus (osb_cluster), which contains a single Managed Server (OSBServer_1)

  • A cluster for Oracle Web Services Manager (OWSM) (wsm_cluster), which contains a single Managed Server (WSMServer_1)

The various Oracle SOA Suite and Oracle Web Services Manager services are targeted to the clusters for maximum performance, so there's no need to target services manually.

The goal is to provide the required targeting and clusters that enable you to easily scale out and scale up this environment for the best performance for your custom Oracle SOA Suite applications.

Figure 2 shows how the servers appear in the Oracle WebLogic Server Administration Console after you deploy the VM template.

Figure 2 Default Managed Servers Configured in the Oracle SOA Suite VM Template

Surrounding text describes Figure 2 .

2.2.4 Oracle WebLogic Server Machines Configured in the Domain

The Oracle WebLogic Server clusters configured in the VM Template domain are targeted to a single Oracle WebLogic Server machine (machine_1), which is listening on the standard listening port for the vServer.

The Administration Server is targeted to a separate Oracle WebLogic Server machine (admin).

Both machines are listening on the default listening IP address of the vServer.

Figure 3 shows how the default machines appear in the Oracle WebLogic Server Administration Console after you deploy the VM template.

Figure 3 Default Oracle WebLogic Server Machines in the Oracle SOA Suite VM Template

Surrounding text describes Figure 3 .

2.2.5 JMS Services Configured in the Domain

When you first deploy the VM Template, the Oracle WebLogic Server domain is configured with six JMS servers, which are either required or recommended for a typical Oracle SOA Suite topology. By default, the JMS servers use a file-based persistence store.

You can later create additional JMS Servers and JMS services if your specific applications require them.

Figure 4 shows how the default JMS Servers appear in the Oracle WebLogic Server Administration Console after you deploy the VM Template.

Figure 5 shows how the default JMS modules appear in the Administration Console.

Figure 4 JMS Servers Configured in the Oracle SOA Suite VM Template

Surrounding text describes Figure 4 .

Figure 5 JMS Modules Configured in the Oracle SOA Suite VM Template

Surrounding text describes Figure 5 .

2.2.6 About Oracle Database Express Edition (XE)

Specific components of Oracle SOA Suite and the supporting Oracle technologies require product-specific schemas, which must be installed in a supported database. By default, the VM Template provides an instance of the Oracle Database XE 11g (11.2.0) software, with the required schemas pre-installed.

The Oracle XE database allows you to quickly get started using the environment after you deploy the VM Template. After you deploy the template, you can consider modifying the topology so it uses a remote Oracle Database, Oracle RAC Database, or an Oracle Exadata Machine database to support the Oracle SOA Suite software and your applications.

For more information about the Oracle XE Database and the other Oracle Database editions, see "The Oracle Database Product Family" in the Oracle Database Licensing Guide.

2.2.7 Data Sources Defined for the Oracle WebLogic Server Domain

To connect to the required schemas installed in the Oracle Database XE instance, the VM Template also provides a set of predefined data sources.

Figure 6 shows how the data sources appear in the Oracle WebLogic Server Administration Console after you deploy the template.

Figure 6 Default Data Souces Configured in the Oracle SOA Suite VM Template

Surrounding text describes Figure 6 .

2.3 Directory Structure of the Deployed VM Template

The directory structure used by the VM Template consists of an Oracle base directory that contains:

  • A product directory structure, which contains the product binaries

  • A config directory structure, which contains the Oracle WebLogic Server domain configuration files

Figure 7 shows a diagram of the basic directory structure for the Oracle SOA Suite VM Template.

Table 1 lists the variables used to reference key directories for Oracle SOA Suite VM Template, as well as sample values for the directory variables.

Figure 7 Directory Structure of a Typical Oracle Fusion Middleware Assembly

Surrounding text describes Figure 7 .

Table 1 Directory Locations for the Oracle SOA Suite VM Template

Directory Variable Description Example Value

ORACLE_BASE

The base directory under which Oracle products are installed.

/u01/app/oracle/

MW_HOME

The Middleware home, which is the directory where the Oracle Fusion Middleware binary files are installed.

ORACLE_BASE/product/fmw/

JAVA_HOME

The location where the JDK binary files are installed.

MW_HOME/jrockit_160_29_D1.2.0-10/

WL_HOME

The Oracle WebLogic Server home, which is the directory where the Oracle WebLogic Server binary files are installed. The Weblogic Server home is inside the Middleware home.

MW_HOME/wlserver_10.3/

SOA_ORACLE_HOME

The Oracle home where the Oracle SOA Suite software binaries are installed.

MW_HOME/Oracle_SOA1/

OSB_ORACLE_HOME

The Oracle home where the Oracle Service Bus (OSB) software binaries are install.

MW_HOME/Oracle_OSB1/

DOMAIN_HOME

The location of the Oracle WebLogic Server domain configuration files. These are typically stored in a separate location from the Middleware home binary files, because a single Middleware home can be used to configure multiple domains.

ORACLE_BASE/config/domains/soa_osb_domain

DB_HOME

The Oracle home where the Oracle Database Express Edition (XE) software binaries are installed.

ORACLE_BASE/product/11.2.0/xe

3 Predeployment Requirements for the VM Template

Before you deploy the Oracle WebLogic Server and Coherence assembly, consider the following predeployment requirements:

3.1 User Requirements

Before you deploy this VM Template, you should be familiar with basic Exalogic Elastic Cloud administration tools and tasks, as well as the basics of Oracle SOA Suite.

You should also be familiar with the virtual environment configured on Exalogic Elastic Cloud. In particular, you should be familiar with the concepts and procedures discussed in the Oracle Exalogic Elastic Cloud Administrator's Guide.

3.2 Virtual Environment Requirements

Before you deploy a VM template, you should have already accomplished the following tasks:

  • The Exalogic machine must be properly installed and configured in a virtual environment.

    In particular, the following tasks should have been performed:

    • Installation of Oracle VM Server

    • Configuration of the Exalogic and the Exalogic vDC software

    These tasks are performed by fully trained and qualified Oracle personnel or by formally accredited Oracle partners.

  • Create a 64GB vServer Type.

    For more information, see "Creating vServer Types" in the Oracle Exalogic Elastic Cloud Administrator's Guide.

  • Configure the following networks, which are required by the VM template:

    • An Ethernet over Infiniband (EoIB) network (which allows communication between the vServer and clients external to Exalogic).

      For more information, see "Creating External EoIB Networks" in the Oracle Exalogic Elastic Cloud Administrator's Guide.

    • A private vNet for IP over Infiniband (IPoIB) for connectivity between vServers, if more vServers are added later.

      For more information, see "Creating Private vNets" in the Oracle Exalogic Elastic Cloud Administrator's Guide.

3.3 System Requirements

The Oracle SOA Suite VM Template is a single-machine deployment. The system where you deploy the template must have at least 32GB of available memory.

3.4 Database Requirements

The Oracle SOA Suite VM template contains a pre-configured Oracle Databse Express Edition (XE) database instance, loaded with SOA schemas that can be used in developer mode.

Optionally, you can use a script, provided as part of the Oracle SOA Suite VM Template distribution, to connect to a supported external Oracle Database or Exadata machine. The script assumes you have installed the required schemas in the external database. For more information, see Section 6, "Configuring Oracle SOA Suite to Use an External Database".

4 Deploying for the VM Template

The following sections describe how to deploy the Oracle SOA Suite VM Template on the Exalogic Elastic Cloud virtual environment:

4.1 Uploading and Registering the Oracle SOA Suite VM Template

The first step in deploying the Oracle SOA Suite VM Template to the Exalogic Elastic Cloud is to upload the template archive so it is available for deployment. Optionally, if you want to make the template available to other users in other accounts, then you can register the template.

Follow these instructions to upload and register the template:

  1. Download the Oracle SOA Suite VM Template from the Oracle Technology Network (OTN).

    The file name for the template is:

    exa_soa_suite_11g_ps6_vm.tgz

    You can copy the archive file to a location on disk, or to a location that is available via HTTP or FTP. Do not unpack the archive. Instead, you upload the compacted archive file to the repository.

  2. Follow the instructions in "Uploading and Registering a Server Template" in the Oracle Exalogic Elastic Cloud Administrator's Guide.

    When prompted for the URL, enter the local path, HTTP URL, or FTP URL to the downloaded archive (.tgz) file.

4.2 Creating and Starting the SOA vServer

After you upload and register the VM template, you can create a vServer for the Oracle SOA Suite environment.

Use the instructions in "Creating vServers" in the Oracle Exalogic Elastic Cloud Administrator's Guide to create the vServer, but note the specific actions in Table 2, which apply when you are creating the Oracle SOA Suite vServer.

Table 2 Creating the Oracle SOA Suite vServer Using the Create vServer Wizard

Create vServer Wizard Screen Actions to take for the Oracle SOA Suite vServer

vServer Details

  • Enter SOA vServer in the vServer Name field.

  • Be sure to clear the High Availability Support check box.

vServer Type

Select a 64GB memory configuration type.

This step assumes you have created a 64GB vServer type, as described in Section 3.2, "Virtual Environment Requirements".

Attach Volumes

Skip this screen.

Instead of attaching a volume, you will later configure shared storage for the Oracle SOA Suite software on the ZFS storage appliance.

vNet Selection

Select Ethernet over Infiniband (EoIB), Infiniband (IB), and the IPoIB-vserver-shared-storage network. The EoIB and IPoIB-vserver-shared-storage networks are the networks described in Section 3.2, "Virtual Environment Requirements".

4.3 Configuring the SOA vServer

The following sections provide instructions for configuring the SOA vServer:

4.3.1 Connecting to the SOA vServer and Updating the root Password

After you create the SOA vServer, connect to the server and reset the root password:

  1. Locate the IP address of the vServer for the EoIB network:

    1. Log in to Exalogic Control as a Cloud User.

    2. From the navigation pane on the left, select vDC Management.

    3. Under vDC Accounts, expand the name of your account, and select the vServer for which you want to configure access to the storage appliance.

      The vServer dashboard is displayed.

    4. Select the Network tab, and note the IP address of the vServer for the EoIB network.

  2. Use SSH to log in as the root user, using the default password of ovsroot.

    For example:

    # SSH root@vserver_ip_address

  3. Change the root password to a unique and secure password.

    For example:

    passwd root
  Changing password for user root
  New UNIX password:
  Retype new UNIX password:

  4. Exit from root and the SSH client, and return to your login session.

4.3.2 Creating the Required Virtual Hosts

The Oracle SOA Suite VM template environment requires a set of virtual host names so requests can be routed to the correct Managed Server, Administration Server, or database.

You configure these virtual hosts using the /etc/hosts file for the vServer. These entries map the vServer host name and the virtual host names required by the pre-configured Oracle SOA Suite domain to valid IP address in the Exalogic rack.

Alternatively, if the clients and servers configured in the Exalogic rack are using a common Domain Name Service (DNS) that resolves the host names to valid IP address, then there is no need to edit the /etc/hosts file.

If you are using the /etc/hosts file to map the host names to IP addresses, then refer to Example 1 for a sample /etc/hosts file that maps the required host names to the EoIB IP address of the SOA vServer.

Example 1 Sample Entries for the Oracle SOA Suite Virtual Hosts in the /etc/hosts File

SOA-vServer-IP-Address SOA-vServer-host-name DBHOST
SOA-vServer-IP-Address admin.mycompany.com ADMINHOST
SOA-vServer-IP-Address soa.mycompany.com SOAHOST1
SOA-vServer-IP-Address soa-internal.mycompany.com SOAHOST1-IMB

4.3.3 Setting the Oracle User Password

Reset the Oracle user account password to a unique and secure password:

You must perform this action as the root user:

passwd oracle
    Changing password for user oracle.
    New UNIX password:
    passwd: all authentication tokens updated successfully.

4.3.4 Setting Up Access to the ZFS Storage Appliance

To set up a share on the on the Sun ZFS Storage appliance and configure the vServer so it can access the share, follow the instructions in "Setting Up Access to the ZFS Storage Appliance for a vServer" in the Oracle Exalogic Elastic Cloud Administrator's Guide.

4.4 Installing and Starting the Oracle SOA Suite Software

The following sections describe how to install and start the Oracle SOA Suite software:

4.4.1 Installing the Oracle SOA Suite Software

To install the Oracle SOA Suite software, unpack the archive on the mounted share on the Sun ZFS Storage appliance:

  1. Log into the Oracle SOA Suite vServer as the oracle user.

    Use the password you set in Section 4.3.3, "Setting the Oracle User Password".

  2. Change directory to the mounted share:

    cd /u01/app/oracle

  3. Unpack the archives, which are available by default in the /u01/software directory on the Oracle SOA Suite vServer local disk:

    tar -zxvf /u01/software/soa-osb_11g_ps6_middleware.tgz

4.4.2 Starting the Oracle Database XE Instance

To start the Oracle Database XE instance:

  1. Locate the scripts directory for the VM Template.

    By default, the scripts are stored in the /u01/scripts directory.

  2. Run the Oracle database start script that is packaged with the template:

    /u01/scripts/oracle-xe start

    Note:

    The oracle-xe script is a wrapper script. On first run, it uses the database archive file in the /u01/software directory to install and configure the database with the required Oracle SOA Suite schemas. On subsequent runs, it skips the installation and configuration steps and simply starts the database instance.

    If you need to stop the database instance, use the following script:

    /u01/scripts/oracle-xe stop

4.4.3 Starting Node Manager, Administration Server, and the Oracle SOA Suite Managed Servers

Use the following procedure start the Node Manager, Administration Server, and Oracle SOA Suite Managed Servers:

  1. Set the JAVA_HOME system variable:

    setenv JAVA_HOME /u01/app/oracle/product/fmw/jrockit_160_29_D1.2.0-10

  2. Locate and run the VM Template start script.

    /u01/scripts/edg_scripts/tools/start.py -v DOMAIN_HOME MW_HOME

    For example:

    /u01/scripts/edg_scripts/tools/start.py \
            -v /u01/app/oracle/config/domains/soa_osb_domain \
            /u01/app/oracle/product/fmw

    This script starts the Node Manager, Administration Server, and the Oracle SOA Suite Managed Servers.

5 Exploring the Oracle SOA Suite VM Template Environment

The following sections describe some typical evaluation tasks you can perform on the Oracle WebLogic Server and Oracle Coherence assembly:

5.1 Reviewing the Default User Accounts and Passwords

The Oracle SOA Suite VM template is configured with the following default users and passwords:

  • The root user password for all Oracle Exalogic VM templates is ovsroot.

    To change the default password, run the passwd root command, as described in Section 4.3.1, "Connecting to the SOA vServer and Updating the root Password".

  • The oracle user password is the owner of the the entire Oracle SOA suite installation.

    To change this password, see Section 4.3.3, "Setting the Oracle User Password".

  • All the Oracle SOA Suite schemas installed in the Oracle Database XE instance use the welcome1 as the schema password. The prefix for all the schemas is PS6_.

  • The Oracle Fusion Middleware Control (EM) and Weblogic Server Admin console user is weblogic. The default password is weblogic1.

    The start.py script will prompt to change this default password during the initial script startup.

5.2 Browsing the Directory Structure

After you deploy and start the Oracle SOA Suite domain, take a few minutes and browse the directory structure of the VM template that you just deployed.

Refer to Section 2.3, "Directory Structure of the Deployed VM Template" for details about where specific files are located in the domain.

Note that if you are using the included Oracle Database XE instance, the database start up script also creates the following database directories:

/u01/app/oracle/oradata/XE
/u01/app/oracle/admin
/u01/app/oracle/diag
/u01/app/oracle/fast_recovery_area

5.3 Accessing the Administration Console and Fusion Middleware Control

After you deploy the assembly, you can use the Oracle WebLogic Server Administration Console and Fusion Middleware Control to perform typical Oracle WebLogic Server management tasks.

To access the Oracle WebLogic Server Administration Console:

admin_server_vm:port/console

For example:

soavm1:7021/console

To access Fusion Middleware Control:

admin_server_vm:port/em

For example:

soavm1:7021/em

Note that 7021 is the default administration port used by the VM Template.

Figure 8 shows how the domain appears from Oracle Enterprise Manager Fusion Middleware Control.

Figure 8 Viewing the Oracle SOA Suite Domain from Fusion Middleware Control

Surrounding text describes Figure 8 .

5.4 Reviewing the Exalogic Optimization Settings

The Oracle SOA Suite VM template is configured to take advantage of several key Oracle SOA Suite optimizations, which improve performance of the Oracle SOA Suite software on the Exalogic Elastic Cloud platform.

See the following sections to review and verify the Exalogic Optimization Settings for Oracle Fusion Middleware:

5.4.1 Verifying the Exalogic Optimization Setting in Fusion Middleware Control

To verify that the Exalogic optimization settings are enabled in Oracle Enterprise Manager Fusion Middleware Control:

  1. Open a Web browser and log in to Fusion Middleware Control.

  2. From the WebLogic Domain menu on the Domain home page, select Administration, and then select General Settings.

  3. Verify that the Enable Exalogic Optimizations check box is selected.

5.4.2 Viewing the Exalogic Optimization Settings in the Domain Configuration Files

Note the following modifications to the Oracle WebLogic Server domain configuration files:

  • Optimization of the domain JVM settings in the setDomainEnv.sh configuration file:

    # Enable Java Exalogic optimizations
EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES}
 -Xlargepages:exitOnFailure=false -Doracle.xdkjava.exalogic.optimization=true
 -Dweblogic.ScatteredReadsEnabled=true
 -Dweblogic.GatheredWritesEnabled=true
 -Dweblogic.replication.enableLazyDeserialization=true"
export EXTRA_JAVA_PROPERTIES

# Update coherence configuration. Enable Java EL optimizations. 
# Use Infiniband Message Bus (IMB) for Coherence
  EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES}
   -Dsoa.archives.dir=${SOA_ORACLE_HOME}/soa 
   -Dsoa.oracle.home=${SOA_ORACLE_HOME} 
   -Dsoa.instance.home=${DOMAIN_HOME}
   -Dtangosol.coherence.clusteraddress=227.7.7.9
   -Dtangosol.coherence.clusterport=9778 
   -Dtangosol.coherence.log=jdk
   -Dtangosol.coherence.transport.reliable=imb
   -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl
   -Dweblogic.transaction.blocking.commit=true
   -Dweblogic.transaction.blocking.rollback=true 
   -Djavax.net.ssl.trustStore=${WL_HOME}/server/lib/DemoTrust.jks"
   export EXTRA_JAVA_PROPERTIES

#Enable local storage for Bpel cache in Weblogic process by setting system 
# property "bpel.cache.localStorage" to true. Enable local storage, configuring cache 
# sizes and worker threads.
 EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES}
   -Dbpel.cache.localStorage=true -Dbpel.cache.threadCount=20
   -Dbpel.cache.cubeInstance.sizeLimit=4g
   -Dbpel.cache.invokeMessage.sizeLimit=2g
   -Dbpel.cache.deliveryMessage.sizeLimit=2g
   -Dbpel.cache.deliverySubscription.sizeLimit=2g"
   export EXTRA_JAVA_PROPERTIES

  • Optimizations in the domain JVM settings in the setSOADomainEnv.sh configuration file:

    # Configure heap
PORT_MEM_ARGS="-Xms8g -Xmx8g"
# Enable SDP
EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES}
   -Djava.net.preferIPv4Stack=true"
    export EXTRA_JAVA_PROPERTIES

  • Optimizations in the Oracle Service Bus reliable-transport, which enable Oracle Service Bus to use IMB. These changes are in the osb-coherence-cache-config.xml file:

    ...
<caching-schemes>
   <distributed-scheme>
       <scheme-name>expiring-distributed</scheme-name>
       <service-name>ORA-OSB-deployments</service-name>
       <reliable-transport>imb</reliable-transport>
       <backing-map-scheme>
          <local-scheme>
                <scheme-ref>expiring-backing-map</scheme-ref>
          </local-scheme>
       </backing-map-scheme>
       <autostart>true</autostart>
   </distributed-scheme>
...

5.4.3 Additional Documentation Resources for the Oracle Fusion Middleware Optimizations for Exalogic

For more information about the Oracle Fusion Middleware optimizations for Exalogic, refer to "Oracle WebLogic Server Optimizations for Exalogic Elastic Cloud Software" in the Oracle Fusion Middleware Licensing Information.

5.5 Accessing Additional Oracle SOA Suite Administration and Development Consoles

After the Oracle SOA Suite VM template is deployed, and after you have started the domain servers, you can also verify the Oracle SOA Suite software by displaying and reviewing the information available in the various Oracle SOA Suite monitoring and development consoles.

Refer to the following sections for more information:

5.5.1 SOA Component Verification URLs

Use the following URLs to verify the Oracle SOA Suite software. Each of these URLs is associated with the SOA Managed Server (SOAServer_1):

SOA-Infra: http://<exa-vserver-host>:7031/soa-infra  
SOA-Infra (SSL): https://<exa-vserver-host>:7032/soa-infra
SOA Composer: http://<exa-vserver-host>:7031/soa/composer  
SOA Composer (SSL): https://<exa-vserver-host>:7032/soa/composer
UMS Configuration: http://<exa-vserver-host>:7031/sdpmessaging/userprefs-ui  
UMS Configuration (SSL): https://<exa-vserver-host>:7032/sdpmessaging/userprefs-ui

5.5.2 Oracle Service Bus (OSB) Verification URLs

Use the following URLs to verify the Oracle Service Bus (OSB) software. Each of these URLs is associated with the OSB Managed Server (OSBServer_1):

OSB Console: http://<exa-vserver-host>:7021/sbconsole  
OSB Console (SSL): https://<exa-vserver-host>:7022/sbconsole

5.5.3 Oracle Web Services Manager (OWSM) Verification URLs

Use the following URLs to verify the Oracle Web Services Manager (OWSM) software. Each of these URLs is associated with the OWSM Managed Server (WSMServer_1):

Policy Manager: http://vserver-host:7051/wsm-pm  
Policy Manager (SSL): https://vserver-host:7052/wsm-pm

6 Configuring Oracle SOA Suite to Use an External Database

To use an external database other than the pre-configured Oracle Database Express Edition (XE) that is packaged with the VM template, you can use a script that is included in the Oracle SOA Suite VM template archive file to automate the process of re-wiring the Oracle SOA Suite software so it uses a supported Oracle Database.

The database can be a single-instance Oracle Database, a highly available Oracle RAC Database, or an Exadata Oracle database.

To configure the Oracle SOA Suite software to use a different database:

  1. Verify that you have installed and configured a database that is certified for use with the Oracle Fusion Middleware 11g Release 1 (11.1.1.7.0) software, and verify that you are able to connect to the database from the Oracle SOA Suite vServer.

    For more information, see Oracle Fusion Middleware Supported System Configurations on the Oracle Technology Network (OTN).

  2. Shut down all the servers in the domain, including the Managed Servers and the Administration Server.

  3. Stop the Node Manager for the domain.

  4. Run the following script, which is packaged with the Oracle SOA Suite VM template:

    /u01/scripts/edg_scripts/scripts/configDS.py

    You can run the script by itself and respond to a series of prompts, or you can provide an initialization (.ini) file, which contains the database connection information and schema information for the script.

    A sample inititialization file is available in the following directory after you deploy the VM template:

    /u01/scripts/edg_scripts/samples

    Example 2 shows an example initialization file for a standalone Oracle Database 11g (11.2.0.3) database. Example 3 shows an example initialization file for an Oracle RAC 11g (11.2.0.3) database.

  5. Start the Node Manager, the Administration Server, and the Managed Servers, using the start.py script, as described in Section 4.4.3.

Example 2 Sample configDS.py Initialization File for an Oracle Database 11g (11.2.0.3) Instance

;;;Sample Input File for Datasource Config
 ;;;Small Production EDG Scripts
 ;;;Version 11.0.2

 ;;; Domain specific info, required for locating WLST and
 ;;;   the Domain to be configured
 [Domain Info]
 oracle_home = /u01/app/oracle/product/fmw/
 domain_home = /u01/app/oracle/config/domains/soa_osb_domain/

 ;;; DB Specific Info
 ;;; The DB_ONS_List is only required if RAC is being used.
 ;;;   Otherwise it may be left blank
 [DB Info]
 schema_prefix = EXA
 service_name = orcl
 listeners = DBHOST1:1521
 ons_list =
 protocol = TCP

Example 3 Sample configDS.py Initialization File for an Oracle RAC Database 11g (11.2.0.3)

;;;Sample Input File for Datasource Config
 ;;;Small Production EDG Scripts
 ;;;Version 11.0.2

 ;;; Domain specific info, required for locating WLST and
 ;;;   the Domain to be configured
 [Domain Info]
 oracle_home = /u01/app/oracle/product/fmw/
 domain_home = /u01/app/oracle/config/domains/soa_osb_domain/

 ;;; DB Specific Info
 ;;; The DB_ONS_List is only required if RAC is being used.
 ;;;   Otherwise it may be left blank
 [DB Info]
 schema_prefix = EXA
 service_name = orcl
 listeners = DBHOST1:1521,DBHOST2:1521
 ons_list = DBHOST-NODE1:6200,DBHOST-NODE2:6200, DBHOST-NODE3:6200
 protocol = TCP

7 Documentation Accessibility

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

Access to Oracle Support

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

Oracle Fusion Middleware SOA Suite VM Template Readme File

E51439-01

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

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

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

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

U.S. GOVERNMENT 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.

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 failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

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

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

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