3 Understanding Oracle HTTP Server Management Tools

This chapter describes the management tools available with the Oracle HTTP Server (OHS). It includes information on OHS management, how to access Fusion Middleware Control, how to access the OHS home page, and how to use the WebLogic Scripting Tool (WLST).

Oracle provides the following management tools for Oracle HTTP Server:

The Configuration Wizard, which enables you to create and delete Oracle HTTP Server instances. For more information, see Installing and Configuring Oracle HTTP Server.
Fusion Middleware Control, which is a browser-based management tool. For more information, see Administering Oracle Fusion Middleware.
The WebLogic Scripting Tool, which is a command-driven scripting tool. For more information, see Understanding the WebLogic Scripting Tool.

Note:

The management tools available to your Oracle HTTP Server implementation depend on whether you have configured it in a WebLogic Server domain (with FMW Infrastructure) or in a standalone domain. For details, see Section 1.4, "Domain Types".

This chapter includes the following sections:

Section 3.1, "Overview of Oracle HTTP Server Management"
Section 3.2, "Special Note on Oracle HTTP Server Mbeans"
Section 3.3, "Accessing Fusion Middleware Control"
Section 3.4, "Accessing the Oracle HTTP Server Home Page"
Section 3.5, "Using Fusion Middleware Control to Edit Configuration Files"
Section 3.6, "Using the WebLogic Scripting Tool"

3.1 Overview of Oracle HTTP Server Management

The main tool for managing Oracle HTTP Server is Fusion Middleware Control, which is a browser-based tool for administering and monitoring the Oracle Fusion Middleware environment.

3.2 Special Note on Oracle HTTP Server Mbeans

The Oracle HTTP Server MBeans, which might be visible in Fusion Middleware Control or the WebLogic Scripting Tool (WLST) are provided for the use of Oracle management tools. The interfaces are not supported for other use and are subject to change without notice.

3.3 Accessing Fusion Middleware Control

To display Fusion Middleware Control, you enter the Fusion Middleware Control URL, which includes the name of the WebLogic Administration Server host and the port number assigned to Fusion Middleware Control during the installation. The following shows the format of the URL:

http://hostname.domain:port/em

If you saved the installation information by clicking Save on the last installation screen, the URL for Fusion Middleware Control is included in the file that is written to disk.

Display Fusion Middleware Control by entering the URL in your Web browser. For example:
```
http://host1.example.com:7001/em
```
The Welcome page appears.
Enter the Fusion Middleware Control administrator user name and password and click Login.

The default user name for the administrator user is weblogic. This is the account you can use to log in to the Fusion Middleware Control for the first time. The weblogic password is the one you supplied during the installation of Fusion Middleware Control.

3.4 Accessing the Oracle HTTP Server Home Page

The Oracle HTTP Server Home page in Fusion Middleware Control contains menus and regions that enable you to manage the server. Use the menus for monitoring, managing, routing, and viewing general information.

3.4.1 Navigating Within Fusion Middleware Control

When you select a target, such as a WebLogic Managed Server or a component, such as Oracle HTTP Server, the target's home page is displayed in the content pane and that target's menu is displayed at the top of the page, in the context pane. For example, if you select an Oracle HTTP Server instance from the Web Tier folder, the Oracle HTTP Server menu is displayed. You can also view the menu for a target by right-clicking the target in the navigation pane.

Figure 3-1 shows the target navigation pane and the home page of Oracle HTTP Server.

Figure 3-1 Oracle HTTP Server Home in Fusion MIddleware Control

Description of ''Figure 3-1 Oracle HTTP Server Home in Fusion MIddleware Control''

The Oracle HTTP Server home page contains the following regions:

Virtual Hosts Region: Shows the virtual hosts for Oracle HTTP Server.
Module Request Statistics Region: Shows the modules for Oracle HTTP Server.
Response and Load Region: Provides information such as the number of active requests, how many requests were submitted, and how long it took for Oracle HTTP Server to respond to a request. It also provides information about the number of bytes processed with the requests.
CPU and Memory Usage Region: Shows how much CPU (by percentage) and memory (in megabytes) are being used by an Oracle HTTP Server instance.
Resource Center: Provides links to books and topics related to Oracle HTTP Server.

3.5 Using Fusion Middleware Control to Edit Configuration Files

The Advanced Server Configuration page in Fusion Middleware Control enables you to edit your Oracle HTTP Server configuration without directly editing the configuration (.conf) files (for details, see Section 1.6.3, "Modifying a Configuration File"). Be aware that Fusion Middleware Control and other Oracle software that manage the Oracle HTTP Server configuration might save these files in a different, equivalent format. After using the software to make a configuration change, multiple configuration files might be rewritten.

3.6 Using the WebLogic Scripting Tool

This section contains the following information:

Section 3.6.1, "Oracle HTTP Server-Specific WLST Commands"
Section 3.6.2, "Using WLST in a Standalone Environment"
Section 3.6.3, "Connecting to the Node Manager in a Collocated Environment"
Section 3.6.4, "Finding More Information on WLST Commands"

3.6.1 Oracle HTTP Server-Specific WLST Commands

Five OHS-specific WLST commands are provided for management of Oracle HTTP Server in WebLogic Server Domains. Most are online commands, which require a connection between WLST and the administration server for the domain.

createOHSInstance()
deleteOHSInstance()
addOHSAdminProperties()
addOHSNMProperties()

One off-line command is provided for creating a domain appropriate for testing OHS:

createOHSTestDomain()

It is recommended to use the createOHSInstance() and deleteOHSInstance() commands to create and delete Oracle HTTP Server instances instead of using the Configuration Wizard or offline WLST, as these custom commands perform additional error checking and, for instance creation, automatic port assignment.

3.6.2 Using WLST in a Standalone Environment

If your Oracle HTTP Server instance is running in a standalone environment, you can use WLST but must use the offline, or "agent", commands that route tasks through . The specific WLST commands are described elsewhere in Chapter 4, "Running Oracle HTTP Server", in the context of the task they perform (for example, the WLST command for starting a standalone Oracle HTTP Server instance is documented in Section 4.3.2.2, "Starting Oracle HTTP Server Instances by Using WLST"); however, you will need to use the nmConnect() command to actually connect to offline WLST. For both Linux and Windows, enter:

nmConnect('login','password','hostname','port','<domainName>')

For example:

nmConnect('weblogic','welcome1','localhost','5556','myDomain')

If you have a remote Oracle HTTP Server in a managed mode and another in standalone with the remote administration mode enabled, you can use WLST to perform management tasks such as SSL configuration. A vanilla Oracle HTTP Server in a standalone domain can be used only as a WebLogic Server and for Oracle HTTP Server start/stop purposes. You can also do this by using a command-line script.

3.6.3 Connecting to the Node Manager in a Collocated Environment

When using WLST to connect to the Node Manager in a collocated environment (either full domain or compact domain), three security-related messages are returned. These messages are harmless and can be ignored.These messages do not appear if connecting to the Node Manager in a standalone environment.

The following Node Manager connection command line provides an example of the security messages that are returned:

wls:/offline> nmConnect('weblogic','welcome1','localhost','5556','OHSDomain')
Connecting to Node Manager ...
<May 9, 2014 2:41:48 PM PDT> <Info> <Security> <BEA-090905> <Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true.>
<May 9, 2014 2:41:48 PM PDT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG128 to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true.>
<May 9, 2014 2:41:48 PM PDT> <Info> <Security> <BEA-090909> <Using the configured custom SSL Hostname Verifier implementation: weblogic.security.utils.SSLWLSHostnameVerifier$NullHostnameVerifier.>
Successfully Connected to Node Manager.

3.6.4 Finding More Information on WLST Commands

For more information on the custom WLST commands for Oracle HTTP Server, see "Oracle HTTP Server Custom WLST Commands" in the WLST Command Reference for Infrastructure Components.