Skip Headers
Oracle® Fusion Middleware Release Notes
11g Release 1 (11.1.1) for Solaris Operating System (SPARC 64-Bit)
Part Number E14772-05
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
View PDF

2 Installation and Configuration

This chapter describes issues associated with Oracle Fusion Middleware installation and configuration. It includes the following topics:

2.1 Installation Issues and Workarounds

This section describes installation issue and workarounds. It includes the following topics:

2.1.1 Oracle Fusion Middleware Support of 64-bit JDK

If you are using a 64-bit JVM in your environment, ensure that all your Oracle Fusion Middleware components are using the 64-bit JVM. You cannot mix components using a 32-bit JVM with those using a 64-bit JVM.

Refer to the Oracle Fusion Middleware Certifications matrix for information on the platforms that support a 64-bit JDK:

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

2.1.2 Upgrading Sun JDK 1.6.0_07 in the Oracle Home Directory

Certain installations, including Oracle Identity Management, Oracle Portal, Forms, Reports and Discoverer, and Oracle Web Tier will install Sun JDK version 1.6.0_07 in the Oracle Home directory. This JDK is used internally and should not be used to deploy Oracle SOA, Oracle WebCenter, or any custom J2EE applications.

If you want a single JDK version deployed for all types of applications, you can upgrade Sun JDK 1.6.0_07 to Sun JDK 1.6.0_11 or higher, using the following steps:

  1. Shut down all processes.

  2. Back up your existing JDK (for example, Sun JDK 1.6.0_07).

  3. Install the new JDK (for example, Sun JDK 1.6.0_11) in the same location as your existing JDK.

  4. Restart all processes.

2.1.3 Prerequisite Warnings During Installation

Vendor release updates cummulative patches and/or packages that may superseed our listed Oracle Fusion Middleware 11g Release 1 prerequisites for platforms. As long as vendor approved patches and/or packages are installed, the prerequisite warnings could be ignored and the installation completed.

Another option is to use -ignoreSysPreReqs command line additional argument to the runInstaller as:

$  Mount_Point/runInstaller -ignoreSysPreReqs other required install options

2.1.4 Installing Oracle SOA Suite on a Dual Stack Host with IPv4

If you install Oracle SOA Suite on a dual stack host and the SOA front end URL is only set to IPv4, Oracle BPM Worklist or asynchronous callbacks from IPv6-only clients may have problems resolving IPv4 callback URLs (and vice-versa).

The work around is to use either a split Domain Name System (DNS) or another forward proxy configuration. This enables the IPv6-only client to connect to a dual stack box through its IPv6 interface.

2.1.5 Managing the Oracle WebLogic Server Node Manager Utility for Oracle Identity Management Installations

For Oracle Identity Management Installations that require Oracle WebLogic Server, you must perform the following steps after installing Oracle WebLogic Server and before installing Oracle Identity Management:

  1. Verify the Oracle WebLogic Server Node Manager utility is stopped. If it is running, kill the process.

    Note:

    The Oracle Fusion Middleware Installation Guide for Oracle Identity Management and the Oracle Fusion Middleware Quick Installation Guide for Oracle Identity Management both state that the Oracle WebLogic Server's Node Manager utility must be running when you install Oracle Identity Management. This is incorrect. If the Oracle WebLogic Server Node Manager utility is running, you must stop it before installing Oracle Identity Management.

  2. Determine if the nodemanager.properties file is present in the WL_HOME/common/nodemanager/ directory.

    • If the nodemanager.properties file is not present, continue installing Oracle Identity Management.

    • If the nodemanager.properties file does exist, open it and verify that the ListenPort parameter is included and that it is set. If the ListenPort parameter is not included or set, edit the nodemanager.properties file so that it is similar to the following, where NODE_MANAGER_LISTEN_PORT represents the port the Node Manager listens on, such as 5556:

      ListenPort=NODE_MANAGER_LISTEN_PORT

2.1.6 Problems Installing in Thai and Turkish Locales

Turkish and Thai users are recommended to install and run Oracle Fusion Middleware using the English locale. Oracle Fusion Middleware does support Turkish and Thai locales as clients.

2.1.7 Installing Oracle UCM in Stand-Alone Mode

The Oracle WebCenter installation gives you the option of installing Oracle Universal Content Management (UCM). If you choose not to install Oracle UCM during the Oracle WebCenter installation, you can install Oracle UCM separately in stand-alone mode. Installation instructions are available at the following location:

http://download.oracle.com/docs/cd/E10316_01/owc.htm

These installation instructions are missing some important information, which is covered below. The following topics are covered:

2.1.7.1 Do Not Include Folders_g in the Installation

The last question is during the installation procedure is:

Select components to install.
         1. ContentFolios: Collect related items in folios
         2. Folders_g: Organize content into hierarchical folders
         3. LinkManager8: Hypertext link management support
         4. OracleTextSearch: External Oracle 11g database as
            search indexer support
         5. ThreadedDiscussions: Threaded discussion management
Enter numbers separated by commas to toggle, 0 to unselect all, F to finish:

Malke sure you DO NOT include number 2 (Folders_g) for this answer; you should not install Folders_g using the installation script. Folders_g will be installed when the wc_contentserverconfig.sh script is run.

2.1.7.2 Disable Trash in the Installation

Instead of installing an new Content Server to use with Oracle WebCenter, you have the option of using an existing Content Server. Any existing Content Server used with Oracle WebCenter should have the Trash disabled. Trash will only be in the Content Server if you have installed a foldering component.

To see if Trash is enabled in the Content Server:

  1. Go to Administration.

  2. Go to Folder Configuration.

  3. Go to System Folder Configuration.

    The colour of the dot next to the Trash folder indicates whether or not the Trash is enabled:

    • Green = enabled

    • Gray = disabled

To disable the Trash:

  1. Ensure you can edit marked folders:

    1. Open the stellent_dir/custom/Folders_g/folders_environment.cfg (on UNIX) or stellent_dir\custom\Folders_g\folders_environment.cfg (on Windows) file.

    2. Verify that the CollectionReadOnlyMarkedFolders value is set to true:

      CollectionReadOnlyMarkedFolders=true

  2. Restart the Content Server if you changed the folders_environment.cfg file.

  3. Log in to the Content Server Home Page as a user with Administrator privileges.

  4. Go to Administration.

  5. Go to Folder Configuration.

  6. Go to System Folder Configuration.

  7. Click on the green dot next to Trash. This will disable the Trash folder and will turn the dot grey.

  8. Restore the value of CollectionReadOnlyMarkedFolders if you had changed it and restart the Content Server.

2.1.8 Ports are not Checked Across Multiple Oracle Home Directories

For Oracle Fusion Middleware 11g Release 1 (11.1.1), each product requires its own Oracle Home directory. Currently, there is no provision for ensuring that port conflicts do not occur across multiple Oracle Home directories.

The best way to work around this problem is to use the staticports.ini file, so that you will have a record of all the ports that are in use.

2.1.9 Administration Server Ports are not Checked Across Multiple Domains

If you are creating multiple domains inside a single Middleware Home, there is no provision for checking port conflicts with the Administration Server in each domain. You must manually ensure that the Administration Server in each domain uses a unique port number.

You can configure custom port numbers for your Administration Server as follows:

  1. Start the Configuration Wizard from the ORACLE_HOME/common/bin directory.

  2. Navigate to the Select Optional Configuration screen, and select Administration Server.

  3. On the Configure Administration Server screen, specify a unique port number for this Administration Server.

2.1.10 Setting the nls_length_semantics Parameter in your Database

Oracle Fusion Middleware only supports schemas in a byte-mode database. The nls_length_semantics initialization parameter on the database where the schemas reside must be set to BYTE; setting this parameter to CHAR is not supported.

To check the values of this parameter using SQL*Plus, you can use the show parameters command:

prompt> sqlplus "sys/password as sysdba"SQL> show parameters nls_length_semantics

Replace password with the actual password for the SYS user.

Alternatively, you can check the values by querying the V$PARAMETER view:

prompt> sqlplus "sys/password as sysdba"SQL> select name,value from v$parameter;

2.1.11 Proper Deinstallation for Reinstallation in the Event of a Failed Installation

In the event that an installation fials, and you want to deinstall the failed installation and then reinstall the software to the same location, you must do the following:

  1. Make sure that all the managed servers in the failed installation are shut down. You must verify this in the Administration Console; the word "SHUTDOWN" must appear next to the managed server name.

  2. Deinstall the binaries in the Oracle Home directory using the deinstaller in the ORACLE_HOME/oui/bin directory.

  3. Delete all the managed servers from the failed installation in the config.xml file by using the Administration Console or WLST.

  4. Delete all directories in the DOMAIN_HOME/servers directory:

This procedure will enable you to reinstall the software to the same location, using the same managed server names.

2.1.12 Deinstalling Oracle Instances Registered to a Domain

If you want to remove an Oracle instance which is registered with a WebLogic domain, make sure to launch the deinstaller from Oracle Home directory that is associated with the Oracle instance you are removing.

The deinstaller will list all instances associated with same WebLogic domain; make sure you choose to remove the instances that are associated with the Oracle Home from where you launched the deinstaller only.

2.1.13 Misleading Error Message in the Oracle Identity Management Installation

During the Oracle Identity Management installation, on the "Select Domain" screen, if you enter "weblogic" as the domain password, you will receive an error message telling you that you have used invalid characters in the password, and that only alphanumeric characters are allowed.

The actual problem is that the password must contain at least one number. For example, "weblogic1" would be a valid password.

2.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

2.2.1 Changing the Listen Address of a Managed Server

When you run the Configuration Wizard after installing Oracle Identity Management or Oracle Portal, Forms, Reports and Discoverer, the listen address for WebLogic managed servers is left blank by default (to listen to all network interfaces). If you change the listen address to the actual host name, the managed server stops listening from outside the machine.

It is recommended that you either leave the listen address blank, or specify the IP address of the host rather than using the host name.

2.2.2 Expand Cluster Requires Changes to the emd.properties File

After running the Oracle Fusion Middleware Configuration Wizard to expand a cluster, the EMD_URL parameter in the INSTANCE_HOME/EMAGENT/EMAGENT/sysman/config/emd.properties (on UNIX) or INSTANCE_HOME\EMAGENT\EMAGENT\sysman\config\emd.properties (on Windows) file contains the values shown below:

EMD_URL=http://localhost.localdomain:port/emd/main

You must edit this parameter and replace localhost and localdomain with the actual host and domain information of your environment. For example, using 5160 as the port number:

EMD_URL=http://myhost.mydomain.mycompany.com:5160/emd/main

2.2.3 Schemas Are Not Visible After Upgrade of Oracle Identity Management

After upgrading Oracle Identity Management from Release 10g (10.1.4.3) to 11g Release 1 (11.1.1), the Oracle Directory Service schemas (ODS and ODSSM) are not visible in the Repository Creation Utility (RCU).

The reason for this is because RCU is not used during the upgrade process, and RCU only recognizes schemas that are created by RCU. Refer to Oracle Fusion Middleware Repository Creation Utility User's Guide for more information.

2.2.4 Error Message When Configuring Oracle Identity Federation

During the configuration of Oracle Identity Federation (OIF), the following error message regarding key store and password may be seen in the configuration log file:

[app:OIF module:/fed path:/fed spec-version:2.5
version:11.1.1.1.0]: Failed while destroying servlet: usermanager.
java.lang.RuntimeException: The server could not initialize properly:
oracle.security.fed.sec.util.KeySourceException: Invalid/unsupported
key store or incorrect password. Please verify that the password is correct
and the store is a valid PKCS#12 PFX wallet or Java KeyStore file.

This error message can be safely ignored if OIF is running properly.

2.2.5 Ensure There Are No Missing Products When Using unpack.sh or unpack.cmd

Oracle SOA Suite, Oracle WebCenter, and Application Developer all contain the pack.sh and unpack.sh (on UNIX systems) or pack.cmd and unpack.cmd (on Window systems) commands in their respective ORACLE_HOME/common/bin (on UNIX systems) or ORACLE_HOME\common\bin (on Windows systems) directories.

The pack.sh and pack.cmd scripts are used to create a template archive (.jar) file that contains a snapshot of either an entire domain or a subset of a domain. The unpack.sh and unpack.cmd scripts are used to create a full domain or a subset of a domain used for a Managed Server domain directory on a remote machine.

The unpack.sh and unpack.cmd commands will fail if any installed products are missing from the machine where you are running the unpack.sh or unpack.cmd command.

2.2.6 Running unpack.sh or unpack.cmd on a Different Host

If you are running the unpack.sh (on UNIX) or unpack.cmd (on Windows) command to unpack a domain on a remote host, the Oracle Home location and the Middleware Home location on the remote host should match the locations on the host where the pack was performed.

Below is a valid example:

Host 1:
MW_HOME = /user/home/Middleware
ORACLE_HOME =/user/home/Middleware/Oracle_SOA1

@ Host 2:
MW_HOME = /user/home/Middleware
ORACLE_HOME =/user/home/Middleware/Oracle_SOA1

The example below is NOT valid because the Oracle Homes do not match:

Host 1:
MW_HOME = /user/home/Middleware
ORACLE_HOME =/user/home/Middleware/Oracle_SOA1

@ Host 2:
MW_HOME = /user/home/Middleware
ORACLE_HOME =/user/home/Middleware/SOA_Home

The example below is NOT valid because the Middleware Homes do not match:

Host 1:
MW_HOME = /user/home/Middleware
ORACLE_HOME =/user/home/Middleware/Oracle_SOA1

@ Host 2:
MW_HOME = /user/home/MWHome
ORACLE_HOME =/user/home/Middleware/Oracle_SOA1

2.2.7 Rerouting to Original URL After SSO Authentication in Firefox Browser

When configuring Oracle Portal, Forms, Reports and Discoverer, when both Oracle HTTP Server and Oracle Web Cache are selected for configuration, re-routing (back to the original URL) after Single Sign-On (SSO) authentication does not work in Firefox Browser when the initial request comes from Oracle HTTP Server.

The work arounds are to either use the Internet Explorer browser, or manually modify the INSTANCE_HOME/config/OHS/instance_name/httpd.conf file and change the ServerName entry to include the port number. For example:

ServerName myhost.mydomain.com

should be changed to:

ServerName myhost.mydomain.com:port

Replace port with the actual port number.

2.3 Known Issues

This section describes known issues. It includes the following topics:

2.3.1 Oracle Universal Installer Lists Errors While Checking For Required Operating System Patches On Solaris 10

When the Oracle Universal Installer (OUI) checks for Solaris operating system patches 127111-02 and 137111-04 on Solaris 10, OUI lists failures even if superseding patches exist on the server. If superseding patches exist, these errors can be safely ignored. Following is an example of checking if a patch that supersedes patch 127111-02 is installed on the server:

showrev -p | grep 127111

If this line returns a superseding patch, the OUI error can be safely ignored and the installation can continue.

2.3.2 Deinstall Command Runs Into java.lang.UnsatisfiedLink Error

When command runInstaller -deinstall is run on Solaris Operating System (SPARC 64-Bit) with Sun 64bit JVM to deinstall WebCenter or SOA shiphome, it fails to start deinstalling OUI and runs into java.lang.UnsatisfiedLink error. This happens as -d64 flag is missing in oraparam.ini jre memory options.

Workaround

Run command runInstaller -deinstall -J-d64 to continue the deinstallation process.

2.3.3 Forms and Reports Builder Not Supported

Forms and Reports Builder is not suported on Linux x86-64, Solaris Operating System (SPARC 64-Bit), AIX Based Systems (64-Bit), HP-UX PA-RISC (64-Bit), HP-UX Itanium, and Microsoft Windows x64 platforms. It is supported on Linux x86 and Microsoft Windows (32-Bit) platforms only.

2.4 Documentation Errata

This section describes documentation errata. It includes the following topics:

2.4.1 Errors in the Quick Install Guides

The Oracle Fusion Middleware quick installation guides contain the following documentation errata:

2.4.1.1 Links to System Requirements and Certification are Truncated

In the PDF versions of the quick installation guides, the links to the system requirements and certification documents are hyphenated due to the limitations of the page size. This causes the links to be formed incorrectly.

The correct link to the Oracle Fusion Middleware System Requirements document is:

http://www.oracle.com/technology/software/products/ias/files/fusion_requirements.htm

The correct link to the Oracle Fusion Middleware Certification document is:

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

2.4.1.2 Inaccurate Database Information Provided

The quick installation guides in the Oracle Fusion Middleware documentation set contain the following database requirement:

Oracle Database 10g (10.2.0.4 or later for non-XE database) using the AL32UTF8 character set.

The AL32UTF8 is strongly recommended but is not a requirement. For the latest RCU database requirements, refer to the system requirements document on Oracle Technology Network (OTN):

http://www.oracle.com/technology/software/products/ias/files/fusion_requirements.htm

2.4.2 Errors in the Oracle Fusion Middleware Installation Guide for Oracle Identity Management

The Oracle Fusion Middleware Installation Guide for Oracle Identity Management contains the following documentation errata:

2.4.2.1 Correction for the inspre11.pl Script's CONNECT_STRING Option

In Chapter 10, "Installing Oracle Single Sign-On and Oracle Delegated Administration Services Against Oracle Internet Directory," of the Oracle Fusion Middleware Installation Guide for Oracle Identity Management, the description for the inspre11.pl script's CONNECT_STRING option is incorrect. The document refers to the option as DB_CONNECT_STRING, however, it should be described as follows:

CONNECT_STRING: Represents the directory database connect string. If you already have a tnsnames.ora file configured, then this is the net service name specified in that file, which is located by default in the ORACLE_HOME/config (on UNIX) or ORACLE_HOME\config (on Windows) directory.

2.4.3 Errors in the Oracle Fusion Middleware Installation Guide for Application Developer

The Oracle Fusion Middleware Installation Guide for Application Developer contains the following documentation errata:

2.4.3.1 Schema Creation is not Required for Application Developer Installation

The Oracle Fusion Middleware Installation Guide for Application Developer incorrectly states that schema creation is necessary for installation and configuration. Disregard all references to schema creation in this document.

2.4.3.2 Incorrect Reference to Oracle SOA Suite

In Section 1.1.3, "Install Oracle WebLogic Server and Create the Middleware Home," the following note appears:

Note:

In order to be configured properly, Oracle SOA Suite requires that Configuration Wizard and Upgrade Framework is selected.

The reference to Oracle SOA Suite is an error; the note should read as follows:

Note:

In order to be configured properly, Application Developer requires that Configuration Wizard and Upgrade Framework is selected.

2.4.3.3 Extraneous Deinstall Instructions

The following sections in Chapter 3, "Deinstalling Application Developer" are not applicable and should be skipped when deinstalling Application Developer:

  • Section 3.1.1, "Stopping Oracle Fusion Middleware"

  • Section 3.1.2, "Removing the Application Developer Schemas"

2.4.4 Oracle RAC Database Not Supported for Oracle UCM Installation

The Oracle WebCenter installation gives you the option of installing Oracle Universal Content Management (UCM). If you choose to install Oracle UCM, you will be asked to provide connection details to your Oracle database.

Section A.7, "Specify UCM Database Details Screen" in Oracle Fusion Middleware Installation Guide for Oracle WebCenter contains incorrect information suggesting that an Oracle Real Applications Cluster (RAC) database may be specified at the time of installation. Support for Oracle RAC databases is not available out-of-the-box. You must configure your Oracle RAC database after Oracle UCM is installed.

Refer to "Reconfiguring the Content Server to Support RAC" in Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter for more information.

2.4.5 Oracle Fusion Middleware Installation Planning Guide Contains Inaccurate Reference to File-Based Repository

The Oracle Fusion Middleware Installation Planning Guide contains the following text in Section 1.3.7, "Oracle Metadata Repository:"

Although a metadata repository can be database-based or file-based, it is recommended that database-based repositories be used in a production environment. If you initially configured your environment with a file-based repository, you can change it to a database-based repository.

This is incorrect because only database-based repositories are supported for Oracle Fusion Middleware 11g Release 1 (11.1.1).

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us