This chapter describes the management tools available with the Oracle HTTP Server. It includes information on Oracle HTTP Server management, how to access Fusion Middleware Control, how to access the Oracle HTTP Server home page, and how to use the WebLogic Scripting Tool (WLST).
Oracle provides the following management tools for Oracle HTTP Server:
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.
WebLogic Scripting Tool, which is a command-driven scripting tool. For more information, see Understanding the WebLogic Scripting Tool.
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".
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.
This chapter includes the following sections:
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. This section described some of the basic Oracle HTTP Server administration tasks you can perform with Fusion Middleware Control.
See Also:Administering Oracle Fusion Middleware
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:
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:
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.
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 the target's menu is displayed at the top of the page, in the context pane.
To display the Oracle HTTP Server home page and the server menu, select an Oracle HTTP Server component from the HTTP Server folder. You can also display the Oracle HTTP Server menu by right-clicking the Oracle HTTP Server target in the navigation pane.
Section 3.1.3, "Understanding the Oracle HTTP Server Home Page" describes the target navigation pane and the home page of Oracle HTTP Server.
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.
The Oracle HTTP Server home page contains the following regions:
General Region: Shows the name of the component, its state, host, port, and machine name, and the location of the Oracle Home.
Key Statistics Region: Shows the processes and requests statistics.
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.
Figure 3-1 shows the target navigation pane and the home page of Oracle HTTP Server.
See Also:Administering Oracle Fusion Middleware contains detailed descriptions of all the items on the target navigation pane and the home page.
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 an Oracle HTTP Server 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. For instructions on how to edit a configuration file from Fusion Middleware Control, see Section 5.1.2, "Editing a Configuration File for a WebLogic Server Domain."
The WebLogic Scripting Tool (WLST) is a command-driven scripting tool. For detailed information on WLST, see Understanding the WebLogic Scripting Tool.
For more information on the WLST custom commands that are available for Oracle HTTP Server, see Appendix A, "Oracle HTTP Server WLST Custom Commands."
This section contains the following information:
WLST provides Oracle HTTP Server-specific commands for server management in WebLogic Server Domains. For more information on the commands, see Appendix A, "Oracle HTTP Server WLST Custom Commands."
The following are online commands, which require a connection between WLST and the administration server for the domain.
Oracle recommends that you use the
ohs_deleteInstance commands to create and delete Oracle HTTP Server instances instead of using the Configuration Wizard. These commands perform additional error checking and, in the case of instance creation, automatic port assignment.
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 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 22.214.171.124, "Starting Oracle HTTP Server Instances Using WLST"); however, you must use the
nmConnect() command to actually connect to offline WLST. For both Linux and Windows, the format of the command is the same:
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.