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.
You can access the WebLogic server console by visiting http://localhost:7001/console/login/LoginForm.jsp
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!
echo off SETLOCAL set DOMAIN_NAME=ClassicDomain set USERDOMAIN_HOME=D:\WebLogic\user_projects\domains\ClassicDomain set SERVER_NAME=AdminServer set WL_HOME=D:\WebLogic\wlserver_10.3 set WLS_USER=weblogic set WLS_PW=pass123 set PRODUCTION_MODE=true set MEM_ARGS=-Xms512m -Xmx512m call "%USERDOMAIN_HOME%\bin\setDomainEnv.cmd" call "%WL_HOME%\server\bin\installSvc.cmd" ENDLOCAL
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.