Configuring Oracle HTTP Server

Starting with WDT 1.8.0, you can configure and update Oracle HTTP Server (OHS) using the Create Domain, Update Domain, and Deploy Applications Tools, in offline mode only. To discover the OHS configuration, use the Discover Domain Tool, in offline mode only. NOTE: The Deploy Applications Tool is deprecated in WDT 4.0.0.


In order to configure and use OHS, it must be installed in the Oracle Home directory used to create the domain. You can download OHS here.

The OHS template must be present in the WDT domain type definition file used to create or update the domain. For more information on creating a custom definition, see Domain type definitions.

You create a copy of an existing domain type definition file, add the template to that file, and then reference that file on the WDT command line. For example, if you want to create a domain with Oracle HTTP Server based on a Restricted JRF domain, then you would first create a copy of the file WLSDEPLOY_HOME/lib/typedefs/RestrictedJRF.json in the same directory, such as WLSDEPLOY_HOME/lib/typedefs/HttpServer.json. In this example, you would change the existing extensionTemplates section to include the additional OHS template. The original value is:

"extensionTemplates": [ "Oracle Restricted JRF", "Oracle Enterprise Manager-Restricted JRF" ],

The revised value would be:

"extensionTemplates": [ "Oracle Restricted JRF", "Oracle Enterprise Manager-Restricted JRF", "Oracle HTTP Server (Restricted JRF)" ],

The file name of this new domain type (without the .json extension) is used with the -domain_type argument on the WDT command line. For example, the command line to create a domain using the HttpServer.json file from the previous steps would look like:

$ WLSDEPLOY_HOME/bin/createDomain -oracle_home /etc/oracle ... -domain_type HttpServer

Configuring the model

Configuring OHS typically involves adding two top-level folders to the resources section of the model, SystemComponent and OHS. Here is an example:

            ComponentType: OHS
            Machine: my-machine
            AdminPort: 9324
            ListenPort: 7323
            SSLListenPort: 4323
            ServerName: http://localhost:7323

Each name under the OHS folder must match a name under the SystemComponent folder in the model, or the name of a SystemComponent element that has been previously created. In this example, the name my-ohs is in both places.

The ComponentType field of the SystemComponent element must be set to OHS in order to allow configuration of the corresponding OHS folders.

You can use the Model Help Tool to determine the complete list of folders and attributes that can be used in these sections of the model. For example, this command will list the attributes in the OHS folder:

$ ${WDT_HOME}/bin/ -oracle_home /tmp/oracle resources:/OHS