Hmmm….seems Fusion MW is Peter Panish – a child that doesn’t want to grow up.
Our team is currently using in production the 22.214.171.124.0 FMW (RH 5) install using the Standalone Forms and Reports 32-bit version. Having encountered memory leaks with this version we are now attempting to migrate to 126.96.36.199 64-bit (RH 5).
The documentation to upgrade from 188.8.131.52 to 184.108.40.206 is full of links that take you from one place to another – I am flying over these docs looking for landmarks to get me to where I want to go – Never Never Land. I expect to have lots of fun with little to no consequences when I get there. But alas the following document is giving me fits! Those nasty pirates have been here first.
220.127.116.11.0 seems to be the only ending point (at this writing it doesn’t look to have a standalone Forms Reports install available for 18.104.22.168.0)…what if you need to stop at a different version along the way. AAGH!
Following the above documentation, I assume the way to get to Never Never Land is to start with WebLogic 10.1.3.2, install FMW 22.214.171.124.0, verify installation, upgrade Weblogic to 10.1.3.4, install 126.96.36.199.0 patchset. But these steps lead me elsewhere as shown by the following error on starting the WebLogic Node Manager after four successful (no errors reported) product installations.
WARNING: Uncaught exception in server handlerjavax.net.ssl.SSLHandshakeException: FATAL Alert:HANDSHAKE_FAILURE – The handshake handler was unable to negotiate an acceptable set of security parameters. javax.net.ssl.SSLHandshakeException: FATAL Alert:HANDSHAKE_FAILURE – The handshake handler was unable to negotiate an acceptable set of security parameters. at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source) at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source) at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source) at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source) at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source) at com.certicom.tls.record.handshake.HandshakeHandler.handleVersion2HandshakeMessages(Unknown Source) at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source) at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source) at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source) at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source) Time to talk to the
Go to the Fairies that live in Pixie Hollow to ask for help (AKA entering a Service Request on MOS).
Tinkerbell comes back with a revised install for the 64-bit Version of 188.8.131.52.0 Standalone Forms/Reports:
Please download the following from http://edelivery.oracle.com
- Oracle WebLogic Server 11gR1 (10.3.4)
- Oracle Portal, Forms, Reports and Discoverer 11g (184.108.40.206.0) (4 parts)
- Oracle Portal, Forms, Reports and Discoverer 11g Patch Set 3 (220.127.116.11.0)
Order of installations
- 1. Install 64 bit JDK – jdk-6u21-linux-x64-rpm.bin (at this writing)
- 2. Install WLS 10.3.4
- 3. Install but do not configure FMW 18.104.22.168
- 4. Install FMW 22.214.171.124
- 5. execute config.sh from the OracleHome/bin folder
I ask Tinkerbell why is her list different from the documentation from MOS Note: How to Install Fusion Middleware 11g Forms and Reports Only (Note:854117.1).
She brightly sighs, shrugs her shoulders and winks at me! ================================
Since we are using a 64-bit OS, we need the Sun JDK 6 64-bit.
The jdk-6u21-linux-x64-rpm.bin can be downloaded from http://java.sun.com/javase/downloads/widget/jdk6.jsp
Verify the correct version of java is installed.
/usr/java/jdk1.6.0_21/bin/java java -version
In my environment there was a symbolic link for an older version of java 1.4 in /usr/bin/java which I removed. This may not be correct for your system, talk to your system administrator about the best way to install a JDK version for system-wide use.
Also you may run out of OS-level file descriptors if left unset. On Linux I edited /etc/security/limits.conf adding the following entries:
* soft nofile 4096
* hard nofile 4096 # End of file
Again, see your System Administrator especially if you want limit the number of open files by user. The example above allows any logon to have those limits.
Install WebLogic 10.1.3.4
This is a typical installation, change the directory if desired.
Install WebLogic. Unzip the file and execute
java -Xmx1024m -jar wls1034_generic.jar
Choose Middleware Home Directory
Create a new Middleware Home – /aux/oracle/middleware
Register for Security Updates
Hit Next to bypass (this is not a mandatory step)
Choose Install Type
Select the 1.6.0_21 version (probably already selected)
Choose Product Installation Directories
WebLogic Server – /aux/oracle/middleware/wlserver_10.3
Install Forms Reports 126.96.36.199
The important thing is to install the software only at this time.
Install Forms Reports. Unzip the files and execute
Specify Inventory Directory
screen Directory: /aux/oracle/oraInventory
Group name: dba (If prompted, run the createCentralInventory.sh as directed.)
Select Installation Type Select Install ONLY!..….you will configure using config.sh script later. Doing this method also installs all of the components but the configuration step allows you to choose which ones to configure.
If you receive an error like Checking for openmotif-2.2.3; not found; failed, Install the missing rpm
Specify Security Updates
Upgrade Forms Reports 188.8.131.52
Install Forms Reports patchset. Unzip the appropriate file and execute
cd Disk1 ./runInstaller
Configure Forms Reports 184.108.40.206
Execute config.sh from the $Oracle_Home/bin folder. This is a configuration tool that can be run as a GUI or command-line.
Other documents that were helpful to our team:
- Upgrading Oracle Middleware 11g; How to Check that the Core Components are Running Successfully? [ID 1086348.1]
- Location Of Different Forms Configuration Files in Fusion Middleware Forms and Reports 220.127.116.11, 18.104.22.168 and 22.214.171.124 Installations [ID 854124.1]
- Maintain FMW 1073776.1
Disable IPV6 for WebCache
We disabled IPV6 because webcache wouldn’t start….see the instructions below.
14.5.3 Disabling IPv6 Support for Oracle Web Cache
By default, IPv6 support is enabled for Oracle Web Cache. You can disable it in the
webcache.xml file, which is located in the following directory:
In the file, change the value of the IPV6 element to “NO”. For example:
If the IPV6 element does not exist in the webcache.xml file, you can add the element to the
file. Add it after the MULTIPORT element, as shown in the following example:
<LISTEN IPADDR=”ANY” PORT=”7786″ PORTTYPE=”ADMINISTRATION”/>
<LISTEN IPADDR=”ANY” PORT=”7788″ PORTTYPE=”INVALIDATION”/>
<LISTEN IPADDR=”ANY” PORT=”7787″ PORTTYPE=”STATISTICS”/>