Install Oracle Forms Reports 12.2.1.4 With Weblogic 12c 12.2 -

Title: The Last Deployment

Chapter 1: The Legacy Scroll

Elara was a "Forms Keeper," a rare breed of developer in a world drunk on React and Node.js. Her company, Draco Maritime, ran the world’s shipping lanes on a crusty but unbreakable Oracle Forms 6i application. It was ugly, green, and indestructible.

But the ancient Solaris server was wheezing its last breath. The audit demanded modernization. The order came down: Migrate to Oracle Forms & Reports 12.2.1.4 on WebLogic 12.2.

Elara looked at the requirements. It read like an ancient incantation: "Requires JDK 8 (precise update), specific kernel parameters, and a sacrifice to the Middleware gods."

She downloaded the three sacred files:

1. V983833-01.zip (WebLogic 12.2.1.4)
2. V983834-01.zip (Forms & Reports 12.2.1.4)
3. V983835-01.zip (RCU – the Repository Creation Utility)

Chapter 2: The Silent Install

Elara spun up a Linux VM, hostname forms-draco. She ran the RCU first.

"Create schemas for STB and IAS_TOP," she whispered, feeding the Oracle database the credentials. The progress bar crawled. At 87%, it froze.

"PRCR-1006: Insufficient tablespace."

She slapped her forehead. The error logs were hiding in a folder called rcu/logs. She expanded the USERS tablespace, re-ran RCU, and this time, the blue bar finished with a silent thump.

Next, the WebLogic binary install. She ran: java -jar fmw_12.2.1.4.0_wls.jar

The GUI launched. She pointed it to /u01/app/oracle/middleware. No errors. So far, so good.

Chapter 3: The Forms Beast

Now the real boss fight: Installing Forms & Reports into the existing Middleware home. Install Oracle Forms Reports 12.2.1.4 With Weblogic 12c 12.2

The installer asked: "Specify WebLogic Server Home." She browsed to the WebLogic directory. A green checkmark appeared. Relief washed over her.

But as the installer copied the forms and reports modules, it stopped with a cryptic:

"OPatch failed: Prerequisite check 'CheckMinimumJDKVersion' failed."

Elara groaned. She had JDK 11 installed by default. The 12.2.1.4 stack was fussy. It needed JDK 8, update 211 or later, but not 9+.

She removed JDK 11, purged the paths, installed jdk-8u351-linux-x64.rpm, and set JAVA_HOME explicitly in the terminal before launching the installer.

export JAVA_HOME=/usr/java/jdk1.8.0_351-amd64

She launched the installer again. This time, the progress bar marched to 100% like a soldier.

Chapter 4: Configuring the Weave

The binary was on disk, but dead. She needed to "Configure" it—weaving WebLogic and Forms into a living application.

She ran the Configuration Wizard: /u01/app/oracle/middleware/oracle_common/common/bin/config.sh

She chose: "Create a new domain" -> "Oracle Forms - 12.2.1.4 [forms]" -> "Oracle Reports - 12.2.1.4 [reports]"

She set the Admin Server port to 7001. The wizard asked for the RCU schemas. She typed the database details for FRS_DS.

Test Connection. Success.

She hit Create. The domain was born at /u01/app/oracle/user_projects/domains/forms_domain. Title: The Last Deployment Chapter 1: The Legacy

Chapter 5: The Startup Rites

Elara navigated to the domain’s bin folder.

First, start the WebLogic Admin Server: ./startWebLogic.sh

She watched the terminal scroll. "RUNNING mode" appeared. She opened a browser: http://forms-draco:7001/console. Login success.

Second, start the Node Manager (the silent guardian of Managed Servers): ./startNodeManager.sh

Third, start the Managed Server for Forms: ./startManagedWebLogic.sh WLS_FORMS http://forms-draco:7001

This took five minutes. Java heap errors flashed. She edited setDomainEnv.sh and bumped MEM_ARGS to -Xms1024m -Xmx2048m.

She restarted. The terminal finally said: "Server 'WLS_FORMS' started successfully."

Chapter 6: The Oracle (Testing)

She opened a new browser tab. The default Forms test page: http://forms-draco:7001/forms/frmservlet

The Java Web Start launcher downloaded. A gray window appeared.

Then, a miracle: "Forms 12c Builder" rendered on screen.

She loaded a test .fmb file. The form compiled. The REP-* errors were silent.

She ran the Reports servlet: http://forms-draco:7001/reports/rwservlet?showenv V983833-01

The XML environment block returned. The beast was alive.

Epilogue: The Coffee

Elara leaned back. The old 6i system would be decommissioned at dawn. She had wrestled JDK versioning, OPatch hell, tablespace limits, and classpath quirks.

She took a sip of cold coffee. It tasted like victory.

Her manager peered over. "Is it done?"

Elara smiled. "It's not just done. It's deployed. Oracle Forms 12.2.1.4 is sleeping on WebLogic 12c. Don't wake it unless you have an offering of heap space and a backup of the domain."

And in the humming server room, the forms ran—green, ugly, but faster than ever.

The End.

7.1 Access Forms Services

Forms services run on Managed Server at:

http://<host>:9001/forms/frmservlet

Test with default application:

http://<host>:9001/forms/frmservlet?config=default

Scope

High-level overview, prerequisites, architecture, supported platforms, installation steps (core flow), post-install configuration, common gotchas, patching/UPDATES, deployment notes, performance/tuning, security considerations, and useful commands/resources.

Step 4: Install Oracle Forms & Reports 12.2.1.4

Now install the Forms & Reports component into the same Oracle Home.

1. The Node Manager

Start the Node Manager service. This acts as the watchdog for your servers.

cd ORACLE_HOME/wlserver/server/bin
./startNodeManager.sh

1.3 Pre-Installation Checklist

• [ ] OS kernel parameters & ulimit configured (Linux)
• [ ] JDK 8 installed and JAVA_HOME set
• [ ] Database schema (e.g., FR_REPOSITORY) created for Reports repository
• [ ] No previous conflicting Middleware home
• [ ] Hostname/FQDN resolved in /etc/hosts

Step 5: Configure Node Manager and Start Servers