Oracle Enterprise Manager Configuration Guide Release 9.0.1 Part Number A88769-01 |
|
This chapter will describe how to run Enterprise Manager 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 Enterprise Manager from any supported web browser.
Note: Browser-based Oracle Enterprise Manager is only supported with web browsers on the following operating systems: Windows 2000, Windows NT, and Windows 98 |
All Enterprise Manager products and applications are web-enabled with the following exceptions:
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:
Note: Using Microsoft® Internet Explorer when it is run from a Microsoft® Active Desktop is not supported. |
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. 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:
On UNIX:
You can start the Oracle HTTP Server from the command line using the command:
$Oracle_Home/Apache/Apache/bin/apachectl start
To stop the Oracle HTTP Server, perform the following steps:
On Windows NT:
To stop the Oracle HTTP Server on Windows NT, perform the following steps:
On UNIX:
You can stop the Oracle HTTP Server from the command line using the command:
$Oracle_Home/Apache/Apache/bin/apachectl stop
If you want to use a web server other than the default configured Oracle HTTP Server, 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 OEM_Webstage" on page 5-9.
After performing the above configuration steps, you are ready to start the browser-based Oracle Enterprise Manager.
Note: 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" on page F-21. |
http://<webserver hostname>:<port number>/
For example:
http://znripley-sun.us.ovenbird.com:3339/
The index (emwebsite.html) page will appear. The index page allows you to launch 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 page 4-18.
You will not be able to close the Oracle Enterprise Console screen without stopping the Console since the application has been launched from this browser window.
In addition, the Oracle Enterprise Manager Login dialog will appear.
Administrator = sysman
Password = oem_temp
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: 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.conf
located in the Apache home/conf/httpd.conf/.
The same rules about trailing "/" apply to ScriptAlias directives as to Alias.
ScriptAlias /oem_webstage/cgi-bin/ "/private/ora90/oem_webstage/cgi-bin/"
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.
Alias /icons/ "/usr/local/apache/icons/" Alias /oem_webstage/ "/private/ora90/oem_webstage/"
/cgi-bin
" to where your ScriptAliased CGI directory exists, if you have that configured.
<Directory "/usr/local/apache/cgi-bin">
to
<Directory "/private/
ora90/oem_webstage/cgi-bin">
AllowOverride all
Allow from all
</Directory>
apachectl stop apachectl start
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:
oem_webstage
.
Alias: /oem_webstage
Path: ORACLE_HOME\oem_webstage
Access: Read, Execute
Alias: cgi-bin
Path: ORACLE_HOME\oem_webstage\cgi-bin
Access: Read, Execute
ORACLE_HOME\oem_webstage\java-plugin
with the following settings:
Alias: java-plugin
Path: ORACLE_HOME\oem_webstage\java-plugin
Access: Read-only
Note: Make sure you do not enable execute permissions; otherwise, you will not be able to download the plug-in.
|
![]() Copyright © 2001 Oracle Corporation. All Rights Reserved. | | Ad Choices. |
|