Setting up Weblogic 10.3.4 and Fusion MiddleWare Forms

Setting up Weblogic 10.3.4 and Fusion MiddleWare Forms

IMPORTANT: Read the entire article before starting the setup process.


The Setup Stages

1 – Weblogic 10.3.4

2 – Fusion MiddleWare (will not be configured)

3 – Fusion MiddleWare Patch (will not be configured)

4 – Configure using config.bat/ (C:OracleWLSas_1binconfig.bat)


Preparing the operating system

1. The server name shouldn’t be longer than 7 to 8 characters and shouldn’t contain the following list of characters, show in this comma separated list:

_ , – , i , (uppercase) i , ı , I , Ö , ç , ü , ğ , ş

Not following this rule could result in the following error:

FMW 11g Installation Failed In Domain Creation Phase With “An Error Occurred While Starting The Domain” [ID 1056027.1]

2. Configure the regional settings to US English.

3. Begin the setup by starting the console using RAdmin.

4. The setup files should be run as an administrator (right-click menu).

5. When setting up the Temp and tmp files, use the absolute path as shown in the images below.

6. Set a static IP for the server and enter the DNS records (not left empty).

7. After making the necessary changes, the services should be stopped and restarted.

NOTE: The versions that are shown in the screenshots may be different, this isn’t important.

8. In generic Weblogic setups the JDK (Java Development Kit) must first be loaded in order to load Jar files.

It is recommended installing to the C:/java or X:/java folder and enter the path to the MS environment.

For x86 systems: java -Xmx1024m -jar wlsversion_generic.jar

For x64 systems: JAVA -D64 – jar

NOTE: Generic WebLogic server files are for 64 bit systems but can also be setup on 32 bit systems.

9. If Wbls 10.0.4 and FMW are to be installed: installed them in this sequence 10.0.4 > >

Setting up Weblogic Setting up Weblogic 3 Setting up Weblogic Setting up Weblogic Setting up Weblogic Setting up Weblogic Setting up Weblogic Setting up Weblogic Setting up Weblogic Setting up Weblogic Setting up Weblogic Setting up Weblogic

Moving on to installing Fusion MiddleWare Forms Report

Setting up Weblogic Setting up Weblogic Setting up Weblogic Setting up Weblogic

By entering the metalink account details here the setup continues and automatically applies updates.

This is neccessary for 64 bit systems.

Setting up Weblogic Setting up Weblogic Setting up Weblogic Setting up Weblogic Setting up Weblogic Setting up Weblogic

Access Information

Administrator Console: http://server_name:7001/console

EM Console: http://server_name:7001/em

EMAgent URL: http://server_name:5155/emd/main

Forms URL: http://server_name:8888/forms/frmservlet

Reports URL: http://server_name:8888/reports/rwservlet


Possible errors and solutions

Check the statuses of the services using the following command:

If the Reports server’s services aren’t working, a possible solution is to copy msvcr71.dll into system32. Entering the DNS ptr (pointer record) may also be required.


If config.bat is stuck at 0% after being run

There shouldn’t be opening or closing braces in the %path% output.

Running config.bat could also be tried by right-clicking and selecting the ‘run as administrator’ option.

Next, a new command prompt and define a new path as shown:



Situations where *RptSvr_SERVERNAME_asinst_1 server isn’t working may be solved by deleting and recreating it.

opmnctl.bat deletecomponent -componentName RptSvr_SERVER_NAME_asinst_1 -componenttype

ReportsServerComponent -instancename asinst_1

opmnctl.bat createcomponent -componentName RptSvr_SERVER_NAME_asinst_1 -componenttype

ReportsServerComponent -instancename asinst_1

*A FRM-93652 error while the application connects to the database, could be due to Bug 9496636 in Oracle 10G’s Microsoft Windows versions.

This bug causes a error message containing __VInfreq__kpuexec to be dumped into C:Oraclewlsasinst_1FormsComponentformstrace folder. Shifting the database to a Linux environment solves the problem (it is possible that it works without issues in a Windows environment and could be due to Windows updates).


A solution to an error message containing: * PKIX path validation failed: signature check failed is:

1. Delete the existing keys with C:Oraclewlsas_1jdkbinkeytool –delete”

2. Re-sign the certificate using the sign_webutil.bat webutil2 key

If the previous 2 steps don’t solve the error, delete jacob.jar and jacob.dll and copy the new versions.

Create a folder in [b][u]F:Oraclewlsuser_projectsdomainsDomain_NameserversAdminServersecurity, with the following content:

Now when the server opens, there won’t be a password prompt.


These steps should also be applied to the forms and reports.