Installing Standalone Oracle Http Server 12c R2 (12.2.1.1) on Windows 2012 R2

IMPORTANT!


According to MOS note Oracle Web Tier – Statement of Direction (Doc ID 1576588.1) Oracle mod_plsql in Oracle HttpServer is deprecated as of version OHS 12.1.3.
If you’re reading this to learn how to install OHS because your application depends on mod_plsql functionality, then we have a bad news for you. Oracle removed mod_plsql from OHS 12.2. So, the best help that we can give you is our reference installation note for OHS 12.1.3 installation on Windows 2012 R2.
Oracle recommends to move to Oracle REST Data Services (ORDS) (formerly known as Apex Listener) on top of Oracle WebLogic, Oracle Glassfish or Apache Tomcat.
Of course, if you’re still interested in installation procedure for OHS 12.2 on top of Windows 2012 R2 keep reading….


Once again, we got a brand new server with Windows 2012 R2, on which we wanted to install standalone Oracle HttpServer 12c R2 (12.2.1.1.0). If you read our post from the last year covering Oracle HttpServer 12.1 installation on Windows 2012 R2, you already know that we’re a big fans of Oracle end user friendliness and admiration of Oracle engineering capabilities to transform a mouse to an elephant. Let’s see if this crap excellent piece of software installs as smooth in Release 2 as it did in Release 1.

Find and download fmw_12.2.1.1.0_ohs_win64_Disk1_1of1.zip from OTN, at the time of this writing you should see something like this:

OHS12cR2_otn

Unpack fmw_12.2.1.1.0_ohs_win64_Disk1_1of1.zip and run setup_fmw_12.2.1.1.0_ohs_win64.exe.

Setup will check the system prerequisites, you should be fine if you’re installing on Windows 2012 R2. Now, we’ll show you some screenshots from our installation with comments whenever we think they’re necessary. Basically, we left most options at default (apart from changing the Oracle home).

OHS12cR2_install_01

OHS12cR2_install_02

OHS12cR2_install_03

OHS12cR2_install_04

OHS12cR2_install_05

OHS12cR2_install_05a

According to Oracle documentation:
On the Windows platform, Oracle HTTP Server requires Microsoft Visual C++ run-time libraries to be installed on the system.
To meet this system requirement for Oracle HTTP Server, download the Visual C++ Redistributable for Visual Studio 2012
software from the following URL: https://www.microsoft.com/en-us/download/details.aspx?id=30679D

After we downloaded and installed Visual C++ (VS 2012) redistributable we hit the Rerun button and the check completed successfully…

OHS12cR2_install_05b

OHS12cR2_install_06

OHS12cR2_install_06a

OHS12cR2_install_07

OHS12cR2_install_08

OHS12cR2_install_08a

OHS12cR2_install_08b

OHS12cR2_install_08c

OHS12cR2_install_08d

As you can notice, there is no screenshot of step #9. After we clicked Next on Step #8 the new dialog window opened for a second and immediately closed. Perhaps it was just us….fortunately, we could made an educated guess that the last screen should likely be an informative one, like the one that we saw during OHS 12c R1 installation:

OracleHTTP-12c-08

…suggesting that fun is not over yet and that you need to create domain with the Configuration Wizard. Start configuration Wizard from:

D:\ORACLE\OFM\OFM12\oracle_common\common\bin\config.cmd

and configure Oracle Http Server in standalone mode…
OHS12cR2_ConfigWizard_01

OHS12cR2_ConfigWizard_02

OHS12cR2_ConfigWizard_03

OHS12cR2_ConfigWizard_04

OHS12cR2_ConfigWizard_05

OHS12cR2_ConfigWizard_06

OHS12cR2_ConfigWizard_07

OHS12cR2_ConfigWizard_08

OHS12cR2_ConfigWizard_08a

OHS12cR2_ConfigWizard_09

If you check Windows services at this time you’ll see, well, nothing. We need to create service for Node Manager before we can start Http server.
Note that we installed Oracle HttpServer 12c R2 in ORACLE_HOME: D:\ORACLE\OFM.

First open command prompt (cmd) wit “Run as Administrator” and set the path before you run installNodeMgrSvc.cmd:

 
set DOMAIN_HOME_BIN=D:\ORACLE\OFM\OFM12\user_projects\domains\base_domain\bin
set PATH=%DOMAIN_HOME_BIN%;%PATH%
 
installNodeMgrSvc.cmd

And if everything has gone well you should see the message at command prompt, with the line:

...
Oracle Weblogic base_domain NodeManager (D_ORACLE_OFM_OFM12_wlserver) installed.
...

Script installeNodeMgrSvc.cmd created a new service, that reads, don’t hold your breath….:

"Oracle Weblogic base_domain NodeManager (D_ORACLE_OFM_OFM12_wlserver)"

with path to the executable like this:

D:\ORACLE\OFM\OFM12\wlserver\server\bin\wlsvcX64.exe

Yes, they probably set a World record for the length of a Windows service. What a schmucks.
The service is installed using the default Node Manager listen port (5556). By default Node Manager Listens only on localhost.

Now, we can finally start Oracle HttpServer 12c R2. First, make sure that Node manager service is running and if it’s not then start “Oracle Weblogic base_domain NodeManager (D_ORACLE_OFM_OFM12_wlserver)”.

You can START Oracle HttpServer 12c R2 on command line with:


set DOMAIN_HOME_BIN=D:\ORACLE\OFM\OFM12\user_projects\domains\base_domain\bin
set PATH=%DOMAIN_HOME_BIN%;%PATH%
startComponent ohs1

You’ll be asked to enter password for Node Manager which you entered on screen 6 of Oracle Fusion Middleware Configuration Wizard.

You can STOP Oracle HttpServer 12c R2 on command line with:


set DOMAIN_HOME_BIN=D:\ORACLE\OFM\OFM12\user_projects\domains\base_domain\bin
set PATH=%DOMAIN_HOME_BIN%;%PATH%
stopComponent ohs1

There is also a WLST tool (wlst.cmd) that allow us to manipulate with running OHS.

Using WLST to control OHS:


Open WLST D:\ORACLE\OFM\OFM12\oracle_common\common\bin\wlst.cmd:
 
Initializing WebLogic Scripting Tool (WLST) ...
 
Welcome to WebLogic Server Administration Scripting Shell
 
Type help() for help on available commands
 
wls:/offline> nmConnect('administrator','mysecretpassword','localhost','5556','base_domain','D:/ORACLE/OFM/OFM12/user_projects/domains/base_domain','ssl')
 
// status
wls:/nm/base_domain> nmServerStatus(serverName='ohs1', serverType='OHS')
 
RUNNING
 
// soft restart
wls:/nm/base_domain> nmSoftRestart(serverName='ohs1', serverType='OHS')
 
// stop OHS
wls:/nm/base_domain> nmKill(serverName='ohs1', serverType='OHS')
Killing server ohs1 ...
Successfully killed server ohs1
 
// status
wls:/nm/base_domain> nmServerStatus(serverName='ohs1', serverType='OHS')
 
SHUTDOWN
 
// start
wls:/nm/base_domain> nmStart(serverName='ohs1', serverType='OHS')

And finally, let’s see where is the config file for httpd. According to the Oracle Http 12c documentation there are runtime and staging config files and we should always edit staging config file(s). In our example the config file location is:

Domain home bin        : D:\ORACLE\OFM\OFM12\user_projects\domains\base_domain\bin
httpd.conf             : D:\ORACLE\OFM\OFM12\user_projects\domains\base_domain\config\fmwconfig\components\OHS\ohs1 

Final Test….open IE and go to http://localhost:7777:

OHS12cR2_final_http_test

Posted on 28.07.2016, in Oracle and tagged . Bookmark the permalink. 1 Comment.

  1. For those of you looking for OHS alternative, I would recommend Doug McMahon modplsql_owa package.
    He also wrote an excellent article about migration from mod_plsql to ORDS listener: “Using the ORDS listener to replace modplsql”.