This appendix describes solutions to common problems that you might encounter when installing Oracle SOA Suite. It contains the following sections:
Section E.2, "Troubleshooting Oracle Fusion Middleware Installation"
Section E.5, "Synchronizing Clocks When Working with Clusters"
Section E.6, "Using Data Sources with an SSL-Enabled Database"
Section E.7, "Extending an Identity Management Domain with a SOA Installation"
If you encounter an error during installation:
Read the Oracle Fusion Middleware Release Notes for the latest updates. The most current version of the release notes is available on Oracle Technology Network (http://www.oracle.com/technology/documentation).
Verify that your computer meets the requirements specified in Section 2.1.1, "System Requirements and Certification".
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:
Note the error and review the installation log files.
Remove the failed installation by following the steps in Chapter 4, "Deinstalling Oracle SOA Suite".
Correct the issue that caused the error.
Restart the installation.
This section contains solutions to common problems that you might encounter when installing Oracle Fusion Middleware. The following topics are covered:
The installer writes logs files to the Oracle_Inventory_Location/log (on UNIX operating systems) or Oracle_Inventory_Location\logs (on Windows operating systems) 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
This is the main log file.
installdate-time-stamp.out
This log file contains the output and error streams during the installation.
installActionsdate-time-stamp.log
This file is used by the installer GUI to keep track of internal information.
installProfiledate-time-stamp.log
This log file contains the overall statistics like time taken to complete the installation, as well as configuration, memory and CPU details.
oraInstalldate-time-stamp.log
This log file contains the output stream of the copy session.
If you start the installer with the -printtime parameter, the timeTakendate-time-stamp.log and timedate-time-stamp.log files are created in the same directory:
timeTakendate-time-stamp.log
This file contains information for the amount of time taken to move between screens (applicable for GUI installations only).
timedate-time-stamp.log
This file contains time information for the copy session.
If you start the installer with the -printmemory parameter, the memorydate-time-stamp.log file is created. This file contains memory usage information for the copy session.
To create a log file of your configuration session, start the Configuration Wizard with the -log option, as shown below:
On UNIX operating systems:
% ./config.sh -log=log_filename
On Windows operating systems:
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 (on UNIX operating systems) or SOA_ORACLE_HOME\common\bin (on Windows operating systems) directory.
The JRE location used by the installer is stored in the SOA_ORACLE_HOME/oui/oraparam.ini (on UNIX operating systems) or SOA_ORACLE_HOME\oui\oraparam.ini (on Windows operating systems) file. This file is used by OPatch and Oracle Universal Installer (OUI) to determine the location of your preferred JRE.
It is possible to change the location of your JRE (for example, the JRE directory is moved out of the Middleware Home). If this happens, you will get an error message when trying to run OPatch or OUI since the JRE location can no longer be found. If this happens, you can do one of the following:
Edit the SOA_ORACLE_HOME/oui/oraparam.ini (on UNIX operating systems) or SOA_ORACLE_HOME\oui\oraparam.ini (on Windows operating systems) file to point to the new JRE location.
Use the -jreLoc command line option to point to the new JRE location. See Section 2.6.1, "Starting the Installer" for more information.
If Oracle WebLogic Server is configured to use custom trust key store, you must manually revise the setDomainEnv.cmd (on Windows operating systems) or setDomainEnv.sh (on UNIX operating systems) file so that the Djavax.net.ssl.trustStore parameter points to the custom trust keystore file. For example:
Djavax.net.ssl.trustStore=/myfolder/mystore/mytrustkeystore.jks
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:
http://www.opensymphony.com/quartz/wikidocs/TutorialLesson11.html
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.
If you are using an SSL-enabled database, follow the instructions below so that your data sources will work with SSL connections:
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
In the WebLogic Server console, navigate to the "Connection Pool" tab of the data source you are using. Modify the following properties accordingly:
Requires Authentication:
javax.net.ssl.keyStore=keystore_password javax.net.ssl.keyStoreType=JKS javax.net.ssl.keyStorePassword=keystore_password javax.net.ssl.trustStore=truststore_location javax.net.ssl.trustStoreType=JKS javax.net.ssl.trustStorePassword=truststore_password
Does Not Require Authentication:
javax.net.ssl.trustStore=truststore_location javax.net.ssl.trustStoreType=JKS javax.net.ssl.trustStorePassword=truststore_password
In the URL field, enter the following:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCPS)(HOST=database_host)(PORT=database_port)))(CONNECT_DATA=(SERVICE_NAME=service_name))(SECURITY=(SSL_SERVER_CERT_DN="distinguished_name" )))
In the JDBC data source files, modify the <property> parameter as shown below:
<property>
@ <name>javax.net.ssl.trustStorePassword</name>
<value>truststore_password</value>
</property>
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:
Follow the instructions in "Setting up the WLST Environment" in Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation.
Copy all of the .py files in the OIF_ORACLE_HOME/fed/script (on UNIX operating systems) or OIF_ORACLE_HOME\fed\script (on Windows operating systems) directory to the WebLogic_Home/common/wlst (on UNIX operating systems) or WebLogic_Home\common\wlst (on Windows operating systems) directory.
Append the OIF_ORACLE_HOME/fed/script (on UNIX operating systems) or OIF_ORACLE_HOME\fed\script (on Windows operating systems) directory to the CLASSPATH environment variable.
If this appendix does not solve the problem you encountered, try these other sources:
Oracle Fusion Middleware Release Notes, available on the Oracle Technology Network (http://www.oracle.com/technology/documentation)
My Oracle Support (formerly OracleMetaLink: http://metalink.oracle.com)
If you do not find a solution for your problem, open a service request.