2 Install and Configure

This chapter describes issues that are related to Oracle Fusion Middleware product installation and configuration.

The following topics are covered in this chapter:

• Issues Related to Product Installation
  
• Issues Related to Product Configuration
  
• Issues Related to Product Installation and Configuration Documentation
  
• Documentation Errata
  

Issues Related to Product Installation

This section contains the following topics:

• Checking for Available Software Patches
  
• Downloading and Applying Required Patches
  
• Applying a Mandatory Patch for Oracle Business Activity Monitoring
  

Checking for Available Software Patches

Before you install any Oracle Fusion Middleware product, it is good practice to review the product information available on My Oracle Support:

http://support.oracle.com/

When you register for My Oracle Support, you have easy access to important information about available patches and other important Oracle Fusion Middleware product information.

Note:

• The generic install jar file name and the quickstart jar file name has been modified to remove the word generic from the jar name. For example,

  • fmw_12.2.1.3.0_idm_generic.jar to fmw_12.2.1.3.0_idm.jar

  • fmw_12.2.1.3.0_idmquickstart_generic.jar to fmw_12.2.1.3.0_idmquickstart.jar

  • fmw_12.2.1.3.0_idmquickstart_generic2.jar to fmw_12.2.1.3.0_idmquickstart2.jar

• The Null Pointer Exceptions that are seen in the .err logs while installing the Forms and Reports (forms builder standalone mode) does not have any functional impact on the product.

Downloading and Applying Required Patches

After you install Oracle Fusion Middleware 12c (12.2.1.3.0), there might be cases where additional patches are required to address specific known issues.

Patches for Oracle Fusion Middleware 12c are available from My Oracle Support:

http://support.oracle.com

The following table lists the Oracle Fusion Middleware patch that was available at the time the release note was published.

Patch Set Exception (PSE) Bug	Patch Description
24737021	A mandatory patch that must be applied for the bug after you install Fusion Middleware 12c (12.2.1.3.0) for Oracle Database Client shared libraries, which has been updated at install time with a previous Bundle Patch. Select the version 12.1.0.2.170418 to download and apply this additional overlay patch. See the README file for patching instructions.

To download a patch:

1. Log in to My Oracle Support.

2. Click the Patches & Updates tab.

3. In the Patch Search area, select Patch Name or Number.

4. Enter the patch number.

5. Click Search. The Patch Search Results page appears.

6. Download and install the patch.

Applying a Mandatory Patch for Oracle Business Activity Monitoring

Before you install Oracle Business Activity Monitoring (Oracle BAM) 12c, be sure to review the My Oracle Support Document ID 1682371.1, which is available from My Oracle Support.

This Support Note provides important information about a mandatory patch that must be applied to Oracle BAM 12c immediately after installation.

Issues Related to Product Configuration

This section contains the following topics:

• Warnings Appear in the Oracle Traffic Director Node Manager Log on Solaris on SPARC (64-bit)
  
• A Partition with Japanese Name Cannot Be Created from Fusion Middleware Control
  

Warnings Appear in the Oracle Traffic Director Node Manager Log on Solaris on SPARC (64-bit)

After you install Oracle Traffic Director (OTD) on Solaris on SPARC (64–bit), you might see warning messages similar to the following examples in the Node Manager log when you start the OTD Node Manager:

WARNING: Key store file keystores.xml integrity check failed. Location: 
/home/oracle/config/domains/OTDDomain/config/fmwconfig/ 
Jul 19, 2016 10:44:36 PM  
oracle.security.jps.internal.keystore.file.FileKeyStoreManager openKeyStore

WARNING: Opening of file based keystore failed. Reason : 
oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06502: 
Failed to read keystore. Reason javax.xml.bind.UnmarshalException

The first warning is a security warning, and the second warning is because of file synchronization issues with the keystores.xml file. There is no workaround, as there is no impact on the OTD functionality. You can ignore these warnings.

A Partition with Japanese Name Cannot Be Created from Fusion Middleware Control

A partition with a Japanese name cannot be created by using Fusion Middleware Control.

As a workaround, you can either use Fusion Middleware Control to create a partition that uses an English name or use the WebLogic Server Administration Console to create a partition with a Japanese name.

Issues Related to Product Installation and Configuration Documentation

This section contains the following topics:

• Registering Node Manager as a Windows Service
  
• An Incorrect Step Appears on the Installation Complete Screen
  
• An Error Message Appears When An Incorrect Version of JDK Is Used for Installation
  
• An Incorrect Error Message Appears if the JDK Is Not Compatible with the Operating System
  
• Warning Messages in make.log File
  
• Simple Security Mode Does Not Function with OAM Server
  
• Domain Creation Fails if the Correct Server Groups Are Not Selected While Configuring OSB and SOA
  
• An Incorrect config.xml File Is Generated While Extending a SOA Cluster with OSB
  
• The install<time-stamp>.out File Is Not Created in the MFT Installation Log Directory
  
• An Error Message Appears in the oblog.log File After You Configure OHS WebGate
  
• Configuring Oracle WebLogic Server to Access Oracle Internet Directory over SSL
  
• Switching to Authentication Against an LDAP Directory (WebCenter Sites)
  

Registering Node Manager as a Windows Service

To register Node Manager as a Windows Service serving either one of the following:

• A standalone OHS domain

• A domain with a collocated ODI agent

Do the following after you have created the domain:

1. Set the JAVA_OPTIONS environment variable so that it points to the proper Oracle home and Domain home directories.

   set JAVA_OPTIONS=-Dohs.product.home=ORACLE_HOME -Dweblogic.RootDirectory=DOMAIN_HOME
   

   For example:

   set JAVA_OPTIONS=-Dohs.product.home=C:\Oracle\product\OHS\OracleHome -Dweblogic.RootDirectory=C:\Oracle\config\domains\OHSDomain
   

2. Go to the Domain home directory and run the following command:

   installNodeMgrSvc.cmd

An Incorrect Step Appears on the Installation Complete Screen

When you complete a standalone OHS installation, the step Start Node Manager and Domain Servers is displayed as one of the next steps you should take after installation.

This information is incorrect, as there are no domain servers configured during the standalone installation.

An Error Message Appears When An Incorrect Version of JDK Is Used for Installation

When you attempt to install a Fusion Middleware product on a 64-bit system, using a JDK for a 32-bit system, an error message is displayed before the installation begins.

Refer to the Oracle Fusion Middleware System Requirements and Specifications document for your product, and download a suitable JDK from the following location, before you install the Fusion Middleware software:

http://www.oracle.com/technetwork/java/javase/downloads/index.html

An Incorrect Error Message Appears if the JDK Is Not Compatible with the Operating System

If you run the installer jar file from a 32-bit JDK7 JVM on a 64-bit machine, the installer displays an incorrect message that the version of the JVM is correct and the version of the operating system on which the software is installed is incorrect.

Refer to the System Requirements and Specifications document for your product, and download a suitable JDK from the following location, before you install the Fusion Middleware software:

http://www.oracle.com/technetwork/java/javase/downloads/index.html

Note:

From 12c (12.2.1.3.0), you can install and use the new version of JDK after installing and configuring an Oracle Fusion Middleware product. See, Updating the JDK After Installing and Configuring an Oracle Fusion Middleware Product

Warning Messages in make.log File

While installing Oracle Web Tier 12c on AIX operating systems, warning messages may appear in the ORACLE_HOME/install/make.log file.

These messages can be safely ignored.

Simple Security Mode Does Not Function with OAM Server

On the AIX Platform, Simple Security Mode does not function with OAM Server.

While registering new Webgate Agent for artifacts generation, select Open or Cert Security Mode in the OAM Server Console.

Domain Creation Fails if the Correct Server Groups Are Not Selected While Configuring OSB and SOA

If you configure an OSB and SOA cluster without selecting the correct server groups, then the domain creation fails with the following notice:

Preparing... 
Extracting Domain Contents... 
Creating Domain Security Information... 
Starting OPSS Security Configuration Data Processing... 
The OPSS Security Configuration Data Processing Completed... 
Domain Creation Failed!

To avoid this error, select OSB-MGD-SVRS-COMBINED and SOA-MGD-SVRS server groups for all managed servers on the Managed Servers screen.

An Incorrect config.xml File Is Generated While Extending a SOA Cluster with OSB

While extending your SOA cluster domain with OSB, if you delete the existing Managed Server and create a new Managed Server, an incorrect config.xml file is generated. For example, if you delete the existing soa_server1 and replaced it with osb_server1 you get an incorrect config.xml file. Specifically, the following SAF tags are missing from config.xml:

<saf-agent> 
    <name>ReliableWseeSAFAgent_auto_1</name> 
    <target>osb_server1 (migratable)</target> 
    <store>WseeFileStore_auto_1</store> 
  </saf-agent> 
  <saf-agent> 
    <name>ReliableWseeSAFAgent_auto_2</name> 
    <target>ms2 (migratable)</target> 
    <store>WseeFileStore_auto_2</store> 
  </saf-agent> 

To avoid this issue, while extending your SOA cluster, create new Managed Servers for OSB.

The install<time-stamp>.out File Is Not Created in the MFT Installation Log Directory

In Managed File Transfer the, install<timestamp>.out file is not created in the log inventory.

This is not an error.

An Error Message Appears in the oblog.log File After You Configure OHS WebGate

After you configure OHS WebGate and restart the servers, the following error message is displayed in oblog.log file in the Domain_Home/server/ohs1/logs/oblog.log directory:

2014/06/10@05:56:29.81679       14314   27      INIT    ERROR   
 0x000003B6      ../oblistrwutil.cpp:225 "Could not read file"   
 filename^/scratch/aime/1213FMW/ASCORE/RC4BColocated/MW_HOME/webgate/ohs/config 
 /oblog_config.xml 
     2014/06/10@05:56:43.14915       14313   9       INIT    ERROR   
 0x000003B6      ../oblistrwutil.cpp:225 "Could not read file"   
 filename^/scratch/aime/1213FMW/ASCORE/RC4BColocated/MW_HOME/webgate/ohs/config 
 /oblog_config.xml 

To work around this issue, do the following:

1. Run:

   cp Oracle_Home/webgate/ohs/config/oblog_config_wg.xml $ Oracle_Home/webgate/ohs/config/oblog_config.xml

2. Restart all the servers.

Configuring Oracle WebLogic Server to Access Oracle Internet Directory over SSL

If you want to configure Oracle WebLogic Server to access Oracle Internet Directory (OID) over SSL, then you need to obtain and add an OID server certificate to the WebLogic domain. The OID certificate is necessary for a successful SSL handshake and to successfully set up a connection from Oracle WebLogic Server to Oracle Internet Directory.

For information on obtaining the required certificate and adding it to the WebLogic Server store, see Enabling SSL Communication Between the Middle Tier and the Hardware Load Balancer in Enterprise Deployment Guide for Oracle SOA Suite.

Switching to Authentication Against an LDAP Directory (WebCenter Sites)

Use this procedure to switch WebCenter Sites to authentication against an external LDAP directory.

This procedure replaces Switching to Authentication Against an LDAP Directory in Installing and Configuring Oracle WebCenter Sites.

To switch WebCenter Sites to authentication against an external LDAP directory:

1. If the LDAP server is case-sensitive (Optional) set or change the value Modify the ldap.caseAware property value to true .
   The default value of ldap.caseAware is false. Login fails if you are using a case-sensitive LDAP server and this property is set to false. To modify the ldap.caseAware value to True:

   1. Log in to the WebCenter Sites Admin interface and navigate to Admin tree tab>System Tools>Property Management option.

   2. Search for ldap and change its value from False to True.

   3. Restart the Managed Server.

   Note:

   If the user data in LDAP is separated by a comma, data is not retrieved during Sites and LDAP integration. For example: test,user. To retrieve the data, you must change the dir.ini file syntax. The file is located in the ..sites/install directory from "syntax.escape=\\ to syntax.escape=\#".
2. Access the LDAP Configurator at http://sites-host:sites-port/sites-context/ldapconfig, follow the instructions on the screen, and enter the values for your environment.
3. Restart the WebCenter Sites Managed Server and go to the same LDAP Configurator URL.

   Nothing is written to your LDAP Server. An LDIF file is created in the DOMAIN_HOME/wcsites/wcsites/config/ldap folder. This is the default install location of the WebCenter Sites application. Oracle recommends that you make all customizations and path modifications after a successful LDAP integration. The peopleparent, groupparent, username, and other fields are not prepopulated, as in the previous release.

4. (Optional) Modify the LDIF file located in DOMAIN_HOME/wcsites/wcsites/config/ with values appropriate for your environment.

   Because the fields are not prepopulated, follow this example for ORACLEDIR:

   ldap server type -- ORACLEDIR
   ldap DSN -- dc=oracle,dc=com
   ldap host -- localhost
   ldap port -- 389
   ldap username -- cn=orcladmin
   ldap password -- password
   ldap peopleParent -- cn=Users,dc=oracle,dc=com
   ldap groupparent -- cn=Groups,dc=oracle,dc=com

   If Oracle Virtual Directory is your LDAP authentication provider, WebCenter Sites generates an LDIF file. You can import the file to your Oracle Internet Directory server and then create an adapter in Oracle Virtual Directory to connect to the Oracle Internet Directory server. You cannot import an LDIF file directly to an Oracle Virtual Directory LDAP server because it does not have storage of its own.
5. Import the LDIF file into the external LDAP authentication provider.
6. Restart the Managed Server running this WebCenter Sites instance.

Documentation Errata

There are no known issues at this time.