With my latest installations of 12c & 11g, I had issue getting the keys mapped properly & after loads and loads of googling I decided to add the same key to all available instances of cgicmd.dat one after another.
So I started with the first instance of cgicmd.dat file, that was found under
which is WLS_REPORTS temporary folder. I added the key, restarted the WLS_REPORTS server & the key was mapped as required!
This could be a nasty bug because I don’t remember adding the keys to multiple files while I tried out forms and reports 11g Release 2 almost 2 years back!
The most interesting part of the entire exercise is, once the key mapping happens successfully, you can remove the keys from cgicmd.dat file that in the temporary location and everything works! Could be the magic of cache
So if you come across key mapping issues, you know where to look at for a quick fix.
Update (19th October 2015): I’m yet to find proper solutions for screen capturing in Windows 10. My favorite OBS doesn’t render the dropdown menus while screen recorded (thread here). Once it’s done, I will make the video as promised with my last update.
Update (12th October 2015) : I’m not promising, however, if possible, I will soon post a video with my Youtube channel explaining how you can configure both forms and reports server for hosting applications. Stay tuned :)
There are excellent articles explaining installing WebLogic 10.3.6 64Bit on Windows. Most of the installation methods are applicable to Windows 7, 8.x & on Windows 10 also. I opted to do a factory reset (the new reset option available with Windows 10) and was forced to re-install & configure WebLogic. I thought of sharing my experiences with you, as usual :)
(There were not a single hiccup experienced throughout the installation, to say it short)
Environment: Windows 10 Professional 64Bit, i5 Processor, 8GB memory, 1TB HDD, Dell laptop
Update 12th October 2015
Weblogic server 10.3.6 has identified issues with IPV6, hence I will suggest you to disable it in case if you are expecting a better experience with your Weblogic servers (forms & reports). ISA, the firewall client also could be a problem.
Once the IPV6 disabled, if you are in a home network or domain network, ping your machine and make sure that your ping replies are coming from your IPV4 address, instead of IPV6. If your computer is a domain member, ask your administrator to delete the IPV6 DNS entries for your box, disable IPV6 in your computer and restart. Ping again to confirm the replies are from IPV4. The issues are random, I had my Windows 8.1 machine with both the protocols enabled and my Weblogic servers just ran smoothly, however my Windows 10 box was adamant and until I disabled IPV6, couldn’t get the report server functional properly.
Install JDK 7 to a folder without spaces in between, preferably C:\ (eg: C:\jdk or D:\jdk). Avoid installing JRE that comes with the JDK package.
Copy your WebLogic installation .jar file to a folder (eg: D:\downloads)
Now kick start the installation, as seen with the below image. It may take a while to deflate the .jar file and the installation to start
Try to install the weblogic server in a folder that doesn’t have spaces in it’s name. I always installed it in D:\weblogic
You don’t have a support for the product most of the times, so uncheck the “I wish…”
Choose the “Typical” for install type
As you started the installation from the JDK installation folder, the local JDK will be already chosen
Select the defaults for components installations(unless you know how to handle it thoroughly)
Install WebLogic for all users
Uncheck “Run Quickstart” and exit the installation by clicking the Close button
Step 4 – Install Developer Suite 11gR2
Installation media for Developer Suite 11gR2 comes as 3 disks. Download (if still available) and start the “Setup.exe” from Disk 1
Select “Skip Software Updates” which requires a paid support from Oracle. If you have one, please set it up prior going ahead with the installation
Select “Install Software – Do Not Configure”. We’ll configure it as part of our Classic Instance setup.
You can ignore the error, details mentions about unsupported operating system, well that’s all our intentions
Unless you have specific requirements, accept the defaults
You don’t have a paid support from Oracle, you don’t get updates. Uncheck “I wish to …”
The installation will start now and it takes quite a while, in my case around 30 minutes. Sit back and relax
Exit the installation clicking “Finish” button.
Step 5 – Configure a Classic Instance
Even though you have installed Developer Suite 11gR2, you cannot yet use the development tools unless a classic domain is set up. Below please see how a classic domain is configured with Developer forms and reports.
A default installation of Oracle Developer Suite should create a folder “Oracle Classic 11g -Home1” under programs. You can activate the classic home setup by invoking menu item “Configure Classic Instance”
(I’m using ClassicShell start menu, I can’t really work with the latest “Start Menu”, so don’t get confused with the below image. You can use the search to find “Configure Classic Instance”)
Select “Configure for Deployment”
Skip the below by unchecking the “I wish to …”
Unless mandatory, accept the defaults
Provide a alphanumeric password for “weblogic” account for the domain. Please note it down, incase if you fear of forgetting it (I do many times)
Important: By default “Oracle Forms and Reports 11g R2” is unchecked, You must check this option to install the developer tools. After checking, proceed with the configuration
Select “Auto Port Configuration”
Select “Do not use proxy settings”. Proxy settings could make weblogic experiences cumbersome. I suggest you use a computer that doesn’t require proxy settings
We are not going to use the Identity store for a local development machine, if you do, please provide the details.
Initiate the configurations by clicking “Configure” button
Configuration should complete in around 30 minutes, so sit back and relax
The above concludes the installation of WebLogic Server 10.3.6 & Developer Suite 11gR2 64Bit on Windows 10.
Let us checkout few essentials those will make sure that you have a seamless experience with the fresh installation.
Unlike the 32Bit, 64Bit installation of WebLogic server doesn’t install node manager Windows service. So you must install the windows service using the scripts provided by the installation process. If you didn’t change any of the default paths while installing the WebLogic server, the node manager windows service installation script file will be available …\wlserver_10.3\server\bin path
Shutdown all running servers using the WebLogic console and restart the computer, this will avoid any sort of complication that could arise while the below exercise are executed.
From an elevated command prompt, running “installNodeMgrSvc.cmd” script will create this node manager windows service for you, which is mandatory for the WebLogic console to maintain your forms & reports servers (start, shutdown)
Once you created the node manager service, you should create a service for WebLogic admin server as well. This will help you from running the batch files manually & having a cluttered desktop later. More than, once created these services can restart themselves whenever you restart the box!
[code language=”text” gutter=”false”]
set MEM_ARGS=-Xms512m -Xmx512m
Copy the above script to a text file and save with a name like “InstallAdminServer.cmd” or with a name that ends with .cmd extension. I will always prefer saving the file in the same folder where we had the node manager service installation script.
Now, from an elevated command prompt, run the script, which should create Admin Server Windows Service for you.
If you followed the instructions, you should see all the services as listed above. You can start the ones which are not running, Please wait a while before trying to access the WebLogic admin console after starting the service. It takes few minutes for the admin server to come online.
I do hope this post will help you to install and configure WebLogic Server and Developer Suite 11gR12 on Windows 10 successfully. Have questions or problems? please update me with the comment section.
Howdy guys? We were busy upgrading uninstalling Weblogic 10.3.6, Forms & Reports 11g R1 and installing 64bit software throughout last few days.
For the installation part, you are not going to get better write up than one available here
However the installation procedure described there is limited to installing the Weblogic Server. You may refer to our earlier post for a “know how to” install and configure Forms & Reports 11g (both R1 & R2)
We tried the following combinations
Weblogic 10.3.6 64Bit with Forms & Reports 11g R1 32Bit. The results were quite disappointing. Installation and configurations went all fine, however once after a restart, we were not able to start the OPMN, thus all the services depending upon OPMN were failing. Even the uninstallation process was terminating without giving any prompts, forcing us to physically remove dozens of entries from registry and other places
Then we opted for a full 64Bit installation, which went smooth and after a restart everything was in place! intact
Setting up the forms using Oracle Enterprise Manager (R2 sets it up properly, against R1)
Just logon to Oracle EM, go to forms node and make changes and just apply. Many changes may not even require a server restart.
Few examples here
Web Configuration for “default”
Setting up LOV buttons, required field highlighting
Calling forms based applications once after the above are set is quite easy. Just point your browser to
However, calling a report may not be that easy. The report server(s) are pretty much sensitive to your network settings. For example, we are using one Windows 8.1 64Bit machine for the entire testing and on which we have multiple oracle products installed
To make the scenarios once again complex, we have both class C and Public IPs set as static addresses for testing multiple products at the same time and VirtualBox’s own network interface (disable it!)
We will try to analyze the most common errors one may come across while trying to run reports
REP-52005: The specified key <keyname: in our case the key userlogin> does not exist in key map file.
just tries to call the available report instance to cater the report. If you want to know how many reports instances are up and running in your server, you can use the EM or rwdiag.bat –findAll command
Common configurations for Reports 11g(11.1.2)
Leave alone the below
Additional settings (if required)
We are hoping to detail this post in near future. Too much typing for a day! Please note, these testing and solutions provided here are coming from novice like you guys, hence if you find anything which is not technically correct, please do let us know through comments section.
Upgrading Forms & Reports developer 11g could be equally confusing & interesting, as there are not many documents explaining a how to. Recently we were closely following up an “issue” raised by one of the visitors and opted to “upgrade” the development machine to check the feasibility of Forms & Reports 11g over Windows 8.1 64Bit
We were able to complete the upgrade process without much issues and the steps followed were described as below
As we were on 32Bit environment for the Weblogic, we downloaded the 32Bit packages for the upgrade. The total download should be roughly around 1.8GB
Once the downloaded archives are extracted, you can start with the upgrade process.
Prior the upgrade process, please make sure you stopped both Weblogic Admin server service & Weblogic Node manager service to avoid any kind of failures with the process.
You can kick start the upgrade process by executing the “setup.exe”
You should “Skip” the software update, as usual :)
Select “Install software – do not configure”
There could be multiple warnings about incompatible setups, you can “Safely” ignore and continue with the installation. We warn you, you shouldn’t install uncertified Oracle products on any OS, in case if you are going to use such setups for Production purposes
Setup should automatically pickup the “Middleware Home & Oracle Home Directory”
Going ahead will produce an error stating another installation is available in the selected location, ignore and continue
Unless you have a valid Oracle support contract, uncheck “I wish to receive…” and continue with the upgrade process
We got an error at 19%, all about certain java components. If you are familiar with LINUX, most of the times you could monitor a log file, as it is being updated using “tail” command. With latest versions of Windows OS you can use powershell to monitor the log file online.
Open up powershell and copy the installation log name like following
It does the job and if errors are found, go ahead and cancel the installation and start over, which should deal with the java related errors. The total installation will be stuck unless.
You may save the setup steps and try out your upgraded forms & reports now. The only one element what we have noticed as “created” new as part of the installation was
Start Forms designer and check the about window and you must having the following information.
Forms [32 Bit] Version 126.96.36.199.0 (Production) Oracle Toolkit Version 188.8.131.52.0 (Production) PL/SQL Version 184.108.40.206.0 (Production) Oracle Procedure Builder V220.127.116.11.0 – Production PL/SQL Editor (c) WinMain Software (www.winmain.com), v1.0 (Production) Oracle Query Builder 18.104.22.168.0 – Production Oracle Virtual Graphics System Version 22.214.171.124.0 (Production) Oracle Tools GUI Utilities Version 126.96.36.199.0 (Production) Oracle Multimedia Version 188.8.131.52.0 (Production) Oracle Tools Integration Version 184.108.40.206.0 (Production) Oracle Tools Common Area Version 220.127.116.11.0 Oracle CORE 18.104.22.168.0 Production
That’s it folks. Give it a try and post us your issues, success notes.
We have recently noticed something very interesting about Oracle’s services were absconding (means not to be seen) from Services listing, however the Oracle products are intact in all other means.
Earlier we shared a post explaining recreating the missing database services. Today we will try to explain how you can recreate missing Weblogic services. You MUST have Administrative access to the box, and en elevated command prompt (right click, start as administrator)
Assuming you have installed the Weblogic 10.3.6 server in the folder “D:\WebLogic\Middleware>” let us start
Start an elevated command prompt. Switch to “D:\WebLogic\Middleware>”
Let us do an old DOS trick to print all the .cmd files available with the repository
If you really know where exactly the .cmd files are, you may go ahead with the rest of the exercises. So the Node manager installer script is residing under D:\WebLogic\Middleware\wlserver_10.3\server\bin folder. Switch to the folder and execute the .cmd file
Executing the .cmd file should create a new service and available to start within services console.
So once we created the Node Manager Service, we can start re-creating the optional service(s). We will limit ourselves to Weblogic Admin Console service, which is the maximum for our exercises. You may refer to our other post about installing & Configuring Weblogic 10.3.6 for details about creating individual services for Forms and Reports services.
Based on the application domain(the directory export will clearly give you an idea of the folders where components are installed) you have chosen during the installation, switch to the domain folder now
Oracle Enterprise Manager(em) allows you to configure, re-configure multiple elements for Oracle forms and reports repositories as well as other deployed applications.
EM is the GUI tool provided by Oracle to configure, say, look and feel for your forms instance. Instead of manually editing formsweb.cfg, default.env, registry.dat files, using the GUI you can configure the elements related those whole configuration files, to say the least.
A default installation of Weblogic 10.3.6 does include Oracle Enterprise Manager, however if you created a service for the Weblogic Admin Server using installSvc.cmd at later stages to start the Weblogic Admin Server, most probably the Enterprise Manager will not start automatically as JAVA classpath variable misses out certain elements, thus throwing the error
“Error java.lang.ClassNotFoundException: oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener Message icon – Warning Errors were encountered while performing this operation.”
After going through a number of OTN discussions, we managed to come up with a solution! by including “setDomainEnv.cmd” within installSvc.cmd batch file.
Please note, if you already created a windows service for Weblogic Admin Server, you must delete the service prior creating a new service. Once the service is gracefully stopped, go to elevated command prompt(Windows 8/ Windows Server 2008 Rx) and type
SC DELETE “beasvc yourdomain_AdminServer”
Refresh the Services.msc console and make sure the service is deleted.
Now backup your installSvc.cmd file
We will modify the installSvc.cmd file (Location: example, D:\WebLogic\Middleware\wlserver_10.3\server\bin) like following (use a decent text editor like Notepad++ )
The following are the default entries you would find with “installSvc.cmd” file
[sourcecode language='text' padlinenumbers='true']
Which we will modify like following
[sourcecode language='text' ]
Now go to folder, where you have created the .cmd file(s) for creating Windows services for
Admin Server Console
In our case we created all those “.cmd” files here
Once the service is created, start it. Login to the console and check the status of “em” under deployments.
If the State is “Active” and Health is “OK”, your Enterprise manager is up and running. You can try to access the Enterprise manager from http://localhost:7001/em
You should provide the same credentials for the Weblogic Admin Console to login with EM.
From the EM Console, as said above, you can configure many parameters for Forms and Reports.
Even though you have managed to “fix” the EM access problem, there could be another issue, once after this exercise. You may not able to access the Forms or Report Server, though the Weblogic console shows them as running with Health being “Ok”
Stop the OPMN processes manually, and restart them and try again.
From elevated command prompt (if you haven’t sourced the environment variable for OPMN, change the working directory to, example: D:\WebLogic\Middleware\asinst_1\bin>)
stop OPMN processes by issuing “opmnctl stopall”
Check the status of the OPMN by issuing “opmnctl status”
Wait until all the processes are stopped
then restart the OPMN processes by issuing “opmnctl startall”
Check the status and make sure all the processes are with a status “Alive”