How to Start Oracle WebLogic & Forms Server and Run Your First Oracle Form (12c)

How to Start Oracle WebLogic, Forms & Reports Servers and Run Your First Oracle Form

After installing and configuring Oracle Forms and Reports 12c, the next step is to start the servers and test whether Oracle Forms is working correctly.

In this tutorial, we will create desktop shortcuts for the WebLogic servers, configure automatic login using boot.properties, start the Forms and Reports servers, and run a test form using the HR schema.

We will also configure the browser for this legacy Oracle Forms environment.

Prerequisites

Before starting, make sure you have completed the previous tutorials:

• Oracle Database 12c is installed.
• Java JDK 8 is installed.
• WebLogic Server 12.2.1.4.0 is installed.
• Oracle Forms and Reports 12c is installed.
• A WebLogic domain has been created.

Our example installation paths are:

Setting	Path / Value
Oracle Home	C:\Oracle\Middleware\Oracle_Home
Domain Home	C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain
WebLogic Console	http://localhost:7001/console
Database Service	ORCL
WebLogic Username	weblogic

Important: Replace example usernames, passwords, paths, and database service names with the values from your own installation.

Step 1: Create Desktop Shortcuts for Starting Servers

First, make sure the DOMAIN_HOME environment variable is configured.

Open the Domain Home directory:

%DOMAIN_HOME%\bin

Inside this folder, you will find the scripts used to start the different servers.

Create desktop shortcuts for:

• startNodeManager.cmd
• startWebLogic.cmd
• startComponent.cmd

Also create two separate shortcuts for:

• startManagedWebLogic.cmd — Forms server
• startManagedWebLogic.cmd — Reports server

Configure the Forms Server Shortcut

1. Rename the first managed server shortcut to Start Form Server.
2. Right-click it and select Properties.
3. In the Target field, add WLS_FORMS after the script path.

The target should look similar to:

"C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain\bin\startManagedWebLogic.cmd" WLS_FORMS

Configure the Reports Server Shortcut

Repeat the same process for the second shortcut.

Rename it to Start Reports Server and add WLS_REPORTS at the end of its Target field.

"C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain\bin\startManagedWebLogic.cmd" WLS_REPORTS

You now have separate shortcuts to start the AdminServer, Node Manager, Forms server, and Reports server.

Step 2: Configure Automatic WebLogic Login

By default, WebLogic may ask for your username and password whenever you start a server.

We can avoid entering credentials every time by creating a boot.properties file for each server.

The file contains the WebLogic username and password. WebLogic encrypts these credentials after successfully reading the file during startup.

Method 1: Create Files Using Command Prompt

Open Command Prompt and run the following commands.

For AdminServer:

mkdir "%DOMAIN_HOME%\servers\AdminServer\security"

echo username=weblogic>"%DOMAIN_HOME%\servers\AdminServer\security\boot.properties"
echo password=weblogic1>>"%DOMAIN_HOME%\servers\AdminServer\security\boot.properties"

For Forms Server:

mkdir "%DOMAIN_HOME%\servers\WLS_FORMS\security"

echo username=weblogic>"%DOMAIN_HOME%\servers\WLS_FORMS\security\boot.properties"
echo password=weblogic1>>"%DOMAIN_HOME%\servers\WLS_FORMS\security\boot.properties"

For Reports Server:

mkdir "%DOMAIN_HOME%\servers\WLS_REPORTS\security"

echo username=weblogic>"%DOMAIN_HOME%\servers\WLS_REPORTS\security\boot.properties"
echo password=weblogic1>>"%DOMAIN_HOME%\servers\WLS_REPORTS\security\boot.properties"

Replace weblogic1 with the password configured when creating your WebLogic domain.

Method 2: Create Files Manually

You can also create these files manually.

1. Open your Domain Home directory.
2. Navigate to:

%DOMAIN_HOME%\servers\AdminServer\security

1. Create a file named boot.properties.
2. Add the following content:

username=weblogic
password=weblogic1

1. Create the same security folder and boot.properties file for:

%DOMAIN_HOME%\servers\WLS_FORMS\security
%DOMAIN_HOME%\servers\WLS_REPORTS\security

Use the same WebLogic credentials for all three servers.

Security note: These files initially contain credentials in plain text. Restrict access to the files and use strong passwords. WebLogic normally encrypts the credentials after reading them successfully.

Step 3: Start the WebLogic Servers

Now let's start the servers one by one.

For this demonstration, start them in the following order:

1. Start Node Manager.
2. Start WebLogic AdminServer.
3. Start Forms Server.
4. Start Reports Server.

Run the shortcuts as Administrator where required.

Wait for each server to finish starting before moving to the next one.

Start Node Manager

Double-click the Start Node Manager shortcut.

Wait until Node Manager starts successfully.

Start WebLogic AdminServer

Now double-click the Start WebLogic Server shortcut.

WebLogic should start without repeatedly asking for your credentials if the boot.properties file is configured correctly.

Start Forms Server

After AdminServer has started successfully, double-click Start Form Server.

Step 4: Verify the Servers in WebLogic Console

Open your browser and navigate to:

http://localhost:7001/console

Enter your WebLogic credentials.

For my demonstration environment:

Username: weblogic
Password: YOUR_WEBLOGIC_PASSWORD

After logging in:

1. Open Environment from the left navigation.
2. Select Servers.
3. Check the server status.

You should see your configured servers, including AdminServer, WLS_FORMS, and WLS_REPORTS.

Wait until the required servers show the RUNNING state.

Step 5: Copy the tnsnames.ora File

Oracle Forms needs the database connection information to connect to your Oracle Database.

Locate the tnsnames.ora file in your Oracle Database installation.

Copy it into your WebLogic domain's configuration directory:

C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain\config\fmwconfig

Make sure the file contains the correct database service entry.

For example, your connection may use the service name ORCL.

Step 6: Unlock the HR Schema

To test Oracle Forms, we will use the sample HR schema.

Open SQL*Plus and connect using a database administrator account:

sqlplus system/YOUR_DATABASE_PASSWORD

Run the following SQL command:

ALTER USER HR IDENTIFIED BY HR ACCOUNT UNLOCK;

This command unlocks the HR account and sets its password to HR.

You can now use the following connection details for your test:

Username: HR
Password: HR
Database: ORCL

Only use these simple credentials in a local demonstration environment. Do not use them for a production database.

Step 7: Configure the ORACLE_HOME Environment Variable

Now configure the Oracle Home environment variable.

1. Open Windows Environment Variables.
2. Under System Variables, find ORACLE_HOME.
3. If it does not exist, create it.
4. Set its value to:

C:\Oracle\Middleware\Oracle_Home

1. Save the changes.

If Oracle Home was already configured with an incorrect path, update it.

Step 8: Download and Open the Test Form

Download the test form provided with this tutorial.

https://mega.nz/folder/9RQziAoa#7ilsdaiuyp75vhdCsids7Q

After downloading, copy the form file into:

C:\Oracle\Middleware\Oracle_Home\forms

Now open Oracle Forms Builder.

Connect to the HR schema using:

Username: HR
Password: HR
Connect String: ORCL

Open the downloaded form.

From the menu, select:

Edit → Preferences → Runtime

Click Reset to Default to restore the runtime settings and obtain the Application Server URL.

Click OK.

Now run the form.

Step 9: Fix FRM-18125 – Could Not Find the Web Browser

When running the form, you may encounter this error:

FRM-18125: Could not find the web browser

To resolve this issue in the legacy setup used in this demonstration:

1. Click OK to close the error.
2. In Forms Builder, open Edit → Preferences.
3. Go to the Runtime tab.
4. Find the Web Browser field.
5. Click Browse.
6. Navigate to:

C:\Program Files\Internet Explorer

1. Select iexplore.exe.
2. Save the settings.

Run the form again.

This configures Forms Builder to use the Internet Explorer executable as its browser launcher. On newer Windows installations, Internet Explorer may no longer be available, so this step may need a different approach.

Step 10: Install Java 8 (32-bit)

If the form opens in Microsoft Edge but displays a black screen, the legacy Java runtime may be missing.

For this particular legacy Forms runtime setup, install the 32-bit Java 8 Runtime Environment.

Open the official Java manual download page:

https://www.java.com/en/download/manual.jsp

Find the Windows offline 32-bit installer. In my demonstration, the downloaded file is:

jre-8u511-windows-i586.exe

Run the installer and complete the installation.

Important: This Java installation is for a legacy client-side runtime requirement. Java 8 32-bit is not a general fix for every Oracle Forms black-screen issue. The required runtime depends on how your Forms application is deployed.

Step 11: Configure Microsoft Edge IE Mode

For this legacy browser-based Forms setup, the application may require Internet Explorer compatibility.

Open Microsoft Edge.

1. Click the three-dot menu.
2. Open Settings.
3. Select Default browser from the left menu.
4. Find Allow sites to be reloaded in Internet Explorer mode (IE mode).
5. Change the setting to Allow.
6. Restart Microsoft Edge.
7. Return to Default browser settings.
8. Under Internet Explorer mode pages, click Add.
9. Paste the Application Server URL that opened when you ran the form.

This allows the configured application URL to be opened using IE mode.

Step 12: Add the Application URL to Trusted Sites

To reduce security-zone prompts for your local test application, add the same application URL to Windows Trusted Sites.

1. Open Windows Internet Options.
2. Select the Security tab.
3. Select Trusted sites.
4. Click Sites.
5. Paste the same application URL.
6. Click Add.
7. Close the window and click OK.

For a local HTTP address, Windows may require you to uncheck Require server verification (https:) for all sites in this zone before adding it.

Only add trusted addresses that you control. Do not broadly lower browser security settings.

Step 13: Run and Test Your First Oracle Form

Now return to Oracle Forms Builder and run the test form again.

If the server configuration, database connection, Java runtime, and browser compatibility settings are correct, the application should open or at least progress beyond the previous browser-recognition issue.

You have now completed the basic server startup and test-form configuration process.

Troubleshooting Checklist

Problem	What to check
WebLogic asks for credentials	Verify each server's boot.properties file and credentials.
Forms server does not start	Check AdminServer status and Forms server logs.
Reports server does not start	Check the Reports managed server configuration and logs.
Database connection fails	Verify tnsnames.ora, service name, and database availability.
HR login fails	Confirm the HR schema is unlocked and the password is correct.
FRM-18125 error	Check the configured browser executable.
Black screen in browser	Check the deployed Forms runtime and browser compatibility requirements.
IE mode is unavailable	Check the supported Edge configuration and organizational policies.

Important Security and Compatibility Notes

This tutorial demonstrates a legacy Oracle Forms and Reports 12.2.1.4.0 environment.

• Do not reuse demonstration passwords in production.
• Avoid exposing WebLogic Console or server ports directly to the public internet.
• Keep Java 8 and legacy browser components isolated and updated where possible.
• Internet Explorer is retired. IE mode is a compatibility feature, not a permanent replacement for modern Forms deployment methods.
• For new deployments, review Oracle's supported browser and deployment options for your exact Forms release.

Helpful Resources

• Oracle Forms and Reports Documentation
• Oracle Java 8 Manual Downloads
• Microsoft Edge IE Mode Documentation

Conclusion

In this tutorial, we created desktop shortcuts for Node Manager, WebLogic AdminServer, Forms Server, and Reports Server. We also configured boot.properties for automatic login, started the servers, unlocked the HR schema, configured Oracle Home, and attempted to run a test Oracle Form.

This completes the basic server startup and initial Forms runtime testing stage of our Oracle Forms and Reports 12c series.

In the next tutorial, we can continue with further Oracle Forms and Reports configuration and troubleshooting.

Complex To Easy – Everything Will Be Just Easy!