Skip Headers
Oracle® Fusion Middleware Installation Guide for Oracle SOA Suite
11g Release 1 (11.1.1)

Part Number E13925-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

E Troubleshooting

This appendix describes solutions to common problems that you might encounter when installing Oracle SOA Suite. It contains the following sections:

E.1 General Troubleshooting Tips

If you encounter an error during installation:

E.2 Troubleshooting Oracle Fusion Middleware Installation

This section contains solutions to common problems that you might encounter when installing Oracle Fusion Middleware. The following topics are covered:

E.2.1 Installation Log Files

The installer writes logs files to the Oracle_Inventory_Location/log (for UNIX) or Oracle_Inventory_Location\logs (for Windows) directory. On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the SOA_ORACLE_HOME/oraInst.loc file. On 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

If you start the installer with the -printtime parameter, the timeTakendate-time-stamp.log file is created in the same directory.

E.2.2 Configuration Log Files

To create a log file of your configuration session, start the Configuration Wizard with the -log option, as shown below:


% ./ -log=log_filename

On Windows:

G:\ config.cmd -log=log_filename

If you specify an absolute path with your log_filename then your log file will be created there. If you only specify a file name with no path, then the log files are created in the SOA_ORACLE_HOME/common/bin (for UNIX) or SOA_ORACLE_HOME\common\bin (for Windows) directory.

E.2.3 Configuring Oracle BAM with Custom Port Numbers

The default port number of the Oracle BAM managed server (bam_server1) is 9001. If, during configuration, you changed this port number or specified a listen address using the WebLogic Configuration Wizard, you must make the following changes:

  1. Manually change the port number from 9001 to the new port number in the SOA_ORACLE_HOME/bam/config/BAMICommandConfig.xml (for UNIX) or SOA_ORACLE_HOME\bam\config\BAMICommandConfig.xml (for Windows) file. The parameter that needs to be changed is shown below:

  2. Oracle BAM single-instance web application configuration information is maintained in the MW_HOME/user_projects/domains/domain_name/servers/BAM_server_name/tmp/_WL_user/oracle-bam_11.1.1/yhryfp/APP-INF/classes/config (for UNIX) or MW_HOME\user_projects\domains\domain_name\servers\BAM_server_name\tmp\_WL_user\oracle-bam_11.1.1\yhryfp\APP-INF\classes\config (for Windows) directory. The properties in these files can be modified by using the Mbeans exposed in the Oracle Enterprise Manager Fusion Middleware Control. The properties exposed through MBeans are specific to each server:

    1. Changes in BAMCommonConfig.xml:

      The <ApplicationURL> parameter should contain the new URL.

    2. Changes in BAMServerConfig.xml:

    3. Changes in BAMWebConfig.xml:


E.2.4 Deploying Oracle SOA and Oracle BAM on Different Servers

Oracle SOA and Oracle BAM are configured in their own managed servers by default (soa_server1 for Oracle SOA and bam_server1 for ORacle BAM). If you choose to configure Oracle SOA on AdminServer by deleting soa_server1 in the Configuration Wizard, and if Oracle BAM is also selected for configuration, then Oracle BAM also needs to be targeted on AdminServer by deleting bam_server1 in the Configuration Wizard.

E.3 Invoking SOA Composites Over SSL

If Oracle WebLogic Server is configured to use custom trust key store, you must manually revise the setDomainEnv.cmd (for Windows)/ (for UNIX) file so that the parameter points to the custom trust keystore file. For example:

E.4 Synchronizing Clocks When Working with Clusters

Oracle SOA uses Quartz, which is an open source job-scheduling framework. When you are setting up clusters on multiple systems, Quartz requires that the clocks on all the systems be synchronized. For more information, refer to the following URL:

Also refer to the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite and Oracle Fusion Middleware High Availability Guide for more information about clustering in advanced topologies.

E.5 Using Data Sources with an SSL-Enabled Database

If you are using an SSL-enabled database, follow the instructions below so that your data sources will work with SSL connections:

  1. Create a truststore and add the ./root/b64certificate.txt as a trusted certificate to the truststore using a keytool:

    keytool -importcert -trustcacerts -alias dbroot -keystore ./truststore -storepass welcome1 -file ./b64certificate.txt
  2. In the WebLogic Server console, navigate to the "Connection Pool" tab of the data source you are using. Modify the following properties accordingly:

    1. Requires Authentication:
    2. Does Not Require Authentication:
  3. In the URL field, enter the following:

  4. In the JDBC data source files, modify the <property> parameter as shown below:

    @ <name></name>

E.6 Extending an Identity Management Domain with a SOA Installation

If you create a domain by installing Oracle Identity Management, then extend it by installing Oracle SOA Suite, the Oracle SOA installer changes the ORACLE_HOME environment variable. This breaks the Oracle Identity Federation (OIF) WebLogic Scripting Tool (WLST) environment, which relies on the value of ORACLE_HOME as set by the Identity Management installation.

To work around this issue, do the following:

  1. Follow the instructions in "Setting up the WLST Environment" in Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation.

  2. Copy all of the .py files in the OIF_ORACLE_HOME/fed/script (on UNIX) or OIF_ORACLE_HOME\fed\script (on Windows) directory to the WebLogic_Home/common/wlst (on UNIX) or WebLogic_Home\common\wlst (on Windows) directory.

  3. Append the OIF_ORACLE_HOME/fed/script (on UNIX) or OIF_ORACLE_HOME\fed\script (on Windows) directory to the CLASSPATH environment variable.

E.7 Need More Help?

If this appendix does not solve the problem you encountered, try these other sources:

If you do not find a solution for your problem, open a service request.