|Oracle Enterprise Manager Configuration Guide
Part Number A96673-01
This chapter will describe how to run the Enterprise Manager Console and its management applications from a web browser.
With Oracle Enterprise Manager, an administrator is not limited to managing targets from a particular machine where the product has been installed. Instead, administrators can deploy the Enterprise Manager Web Site in order to run the Enterprise Manager Console from any supported web browser.
Browser-based Oracle Enterprise Manager is only supported with web browsers on the following operating systems: Windows 2000, Windows XP, Windows NT, and Windows 98.
All Enterprise Manager products and applications are web-enabled with the following exceptions:
In order to see any Management Pack applications from browser-based Enterprise Manager you must install the corresponding Management Pack(s) on the Management Server machine to which you intend to connect.
In order to run Oracle Enterprise Manager from a web browser, you must perform the following installation and configuration steps.
Ensure that a supported web browser is installed on the client(s) machines that will run web-enabled Enterprise Manager.
Supported web browsers are listed below:
Using Microsoft® Internet Explorer when it is run from a Microsoft® Active Desktop is not supported.
By default, it is installed with the Management Server under the
Oracle_Home/oem_webstage/ directory. In addition, the Enterprise Manager web site automatically installs a preconfigured Oracle HTTP server to act as its web server. The Oracle HTTP server is automatically started. This is the same HTTP server that is used by the Enterprise Manager Reporting web site.
On Windows NT:
To start the Oracle HTTP Server:
You can start the Oracle HTTP Server from the command line using the command:
To stop the Oracle HTTP Server, perform the following steps:
On Windows NT:
To stop the Oracle HTTP Server:
You can stop the Oracle HTTP Server from the command line using the command:
If you want to use a web server other than the default configured Oracle HTTP Server for the browser-based Enterprise Manager, you must install and manually configure another supported web server. Additional supported web servers include:
For examples on configuring the non-Oracle web servers for use with browser-based Enterprise Manager, refer to "Configuring the Web Server and Directory Mapping for Web Site".
After performing the above configuration steps, you are ready to start the browser-based Oracle Enterprise Manager.
In order to run Enterprise Manager from a web browser, you must remove any proxies that are configured for use by your web browser. You can do this by either:
If you should experience problems with the proxies, refer to "Troubleshooting the Web Browser".
http://<webserver hostname>:<port number>/
Note: The default preconfigured Oracle HTTP Server's port number is 3339.
The index (
emwebsite.html) page will appear. The index page allows you to start the Enterprise Manager Console, Enterprise Manager Reporting web site, and documentation, and access various web sites. For information on setting up the Enterprise Manager Reporting Web Site, see "Configuring Enterprise Manager Reporting".
On Netscape, you are automatically prompted to install the plug-in.
Note: Once you are prompted to install the plug-in and you exit or cancel before installing it, you will no longer be prompted to install it the next time you start the browser-based Enterprise Manager. In this situation, to install the plug-in, select Download Plug-in on the index page to download the java plug-in.
On Microsoft Internet Explorer, you can select Download Plug-in on the index page to download the plug-in.
The Console applet has been started from the browser window. Closing the dialog will cause the applet to stop.
You will not be able to close the Oracle Enterprise Console window without stopping the Console since the application has been started from this browser window.
You can exit the emwebsite.html page without exiting the Console.
In addition, the Oracle Enterprise Manager Console Login will appear.
Note: Starting the browser-based Oracle Enterprise Manager for the first time may take several minutes, and if you are running a dial up connection, download times will typically be longer and vary based on the line speed. A progress dialog will appear the first time you start browser-based Oracle Enterprise Manager.
These credentials are for the default Super Administrator account. The first time you start Enterprise Manager, you must login as this Super Administrator. After other administrator accounts have been created using the Super Administrator account, you can login as a different administrator.
Note: If you are not able to connect to the Management Server specified, you must return to the index (
emwebsite.html) page to enter a different Management Server machine name. You cannot simply enter a new Management Server machine name at the Oracle Enterprise Manager Console Login.
Note: You can access only one URL for running browser-based Enterprise Manager applications. You cannot access browser-based Enterprise Manager applications from multiple URLs from a single machine.
If you want to use a web server other than the default preconfigured Oracle HTTP server for browser-based Enterprise Manager, you must install and manually configure another supported web server. Additional supported web servers include:
To configure the Apache Server and Microsoft Internet Information Server, refer to the following instructions.
httpd.conflocated in the
The same rules about trailing "/" apply to ScriptAlias directives as to Alias.
/private/ora92/ is your Oracle Home.
Note that if you include a trailing "/" on fakename, then the server requires that it is present in the URL. In this example, "/icons" is not aliased. "/icons/" is aliased.
Note: /private/ora92/ is your Oracle Home.
/cgi-bin" to where your ScriptAliased CGI directory exists, if you have that configured.
<Directory "/usr/local/apache/cgi-bin"> to
To use the Internet Information Server, you will need to create three virtual directories pointing to the oem_webstage directory and two subdirectories inside of that directory. The oem_webstage directory is created automatically by the installation procedure when the Oracle Enterprise Manager Web Site component is installed:
Access: Read, Execute
Access: Read, Execute
ORACLE_HOME\oem_webstage\java-pluginwith the following settings:
Note: Make sure you do not enable execute permissions; otherwise, you will not be able to download the plug-in.