FMW 11g "IDM" or "Portal/Forms/Reports/Discoverer" Configuration Wizards on 64bit Platforms Hang at 0% 'Creating Domain'

FMW 11g "IDM" or "Portal, Forms, Reports, Discoverer" Configuration Wizards on 64bit Platforms Hang

FMW 11g "IDM" or "Portal/Forms/Reports/Discoverer" Configuration Wizards on 64bit Platforms Hang at

Titleimage

Posted by Patrick Hamou on 2017:09:07 18:30:36

APPLIES TO:

Oracle Fusion Middleware - Version 11.1.1.1.0 to 11.1.1.9.0 [Release Oracle11g]
Information in this document applies to any platform.

SYMPTOMS

The objective is to install either Fusion Middleware 11g 'Portal/Forms/Reports/Discoverer' or 'Identity Management' on a 64bit platform.

The Oracle WebLogic 11g 64bit has been installed successfully

The 'Portal/Forms/Reports/Discoverer' or 'Identity Management' binaries install fine

The Configuration Wizard, however, hangs at 0% at the 'Creating Domain' stage. 

It does not matter the Configuration Wizard is run as part of the overall first install process or run separately post install by running configuration wizard.

The installActions log has this error stack 

oracle.as.provisioning.util.ConfigException: 
Error while starting the domain. 
Cause: 
Starting the Admin_Server timed out. 
Action: 
See logs for more details. 
at oracle.as.provisioning.util.ConfigException.createConfigException(ConfigException.java:123) 
at oracle.as.provisioning.weblogic.ASDomain.startDomain(ASDomain.java:3085) 

The install .out file shows 

*** AdminServer port is 7001 
trying to connect to MYMACHINE 7001 
null 

The JDK wasn't found in directory C:\FMW11g\jrockit_160_05_R27.6.2-20. 
Please edit the setWLSEnv.cmd script so that the JAVA_HOME variable points to the location of your JDK. 
Your environment has not been set.

CAUSE

The issue occurs because Oracle Weblogic Server ( Generic - 64bit ) has been mistakely installed using a 32bit JDK.

It is not supported / certified to configure Portal/Forms/Reports/Discoverer or Identity Management 11g against Oracle Weblogic Server 64bit which has been installed using a 32bit JDK. 

In more detail: 

The Weblogic environmental context of a Domain, when is it created, is based on the contents of the file

MS Windows: commEnv.cmd
Unix: commEnv.sh

which resides in the directory <wl_server_home>/common/bin/

The 'Portal/Forms/Reports/Discoverer' or 'Identity Management' Configuration Wizard creates a Weblogic domain using the environment variable values in this file.

This file contains the settings for

JAVA_HOME=<location of JDK>
JAVA_VENDOR=<Sun or Oracle> 
JAVA_USE_64BIT=<true or false>


If JAVA_VENDOR = Oracle, then Weblogic will default to creating domains based on JRockit. 
If JAVA_VENDOR = Sun, then Weblogic will default to creating domains based on Sun JDK. 

The values given to the environment variables in the commEnv file depend upon the JDK used at Weblogic Server install time. If you install the Weblogic Server 64bit using the Sun JDK 32bit, you will end up with settings like 

Example: MS Windows 64bit

set JAVA_HOME=C:\FMW11g\jrockit_160_05_R27.6.2-20 
set JAVA_VENDOR=Oracle 
set JAVA_USE_64BIT=true


The jrockit directory will not actually exist because Weblogic Generic 64bit does not bundle Sun JDK or JRockit. Only the platform specific 32bit Weblogic media bundles them. Installing 64bit Weblogic with a Sun JDK 32bit results in the JAVA_VENDOR and JAVA_HOME values being set based on the default Weblogic 32bit environment settings. These are not settings that will work. The 'Portal/Forms/Reports/Discoverer' or 'Identity Management' configuration wizard will hang at 0% simply because it cannot locate the java binaries specified by the JAVA_HOME in the commEnv file.

SOLUTION

For 64bit platform, 64bit versions of the Oracle Fusion Middeware 11g media should be used. Furthermore, the Oracle Weblogic Server 64bit must be installed using a 64bit JDK as the installation guide prescribes. In summary proceed as follows:

1. Deinstall the previous failed Weblogic and 'Portal/Forms/Reports/Discoverer' attempts.

- For the 'Portal/Forms/Reports/Disco' binaries and system components part of the install run

MS Windows:

<Middleware Home>\<Oracle Home>\oui\bin\setup.exe -deinstall


Unix

<Middleware Home>/<Oracle Home>/oui/bin/runinstaller -deinstall


- To install the Weblogic part of the technology stack run

MS Windows:

<Middleware Home>\<WebLogic Home>\uninstall\uninstall.cmd


Unix

<Middleware Home>/<WebLogic Home>/uninstall/uninstall.sh


Once done, manually remove anything that remains in the <Middleware Home> directory

Now start the build again - see next points below

2. Install Weblogic Generic (i.e the 64bit version of the Weblogic media) as per the instructions in the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server

In particular, read

Chapter 2 Preparing for Installation
and
Installing WebLogic Server on 64-Bit Platforms Using a 64-Bit JDK

3. Install and configure the chosen Fusion Middleware install type (e.g 'Portal/Forms/Reports/Discoverer' or 'Identity Management') using the 64bit version of the install type software.

REFERENCES

BUG:8676107 - INSTALL DOC (CLASSIC/IDM/WEBCENTER/SOA) SHOULD MORE CLEARLY DESCRIBE JDK SYS REQ

NOTE:862838.1 - FMW 11g 'Portal/Forms/Reports/Discoverer' Config Wizard Fails - "Error creating ASInstance" .. Unable to Connect to 'Admin Server' ..PermGen Space

Return to Blog