Home arrow Oracle arrow Page 2 - J2EE Applications: Maintenance and Monitoring

Maintaining and Monitoring Applications - Oracle

In this final article of a six-part series, you will learn how to deploy, maintain, and monitor J2EE applications. You'll also review the content of all of the parts; a self-test is included at the end. It is excerpted from chapter eight of the Oracle 10g Application Server Exam Guide, written by Sam Alapati (McGraw-Hill; ISBN: 0072262710).

TABLE OF CONTENTS:
  1. J2EE Applications: Maintenance and Monitoring
  2. Maintaining and Monitoring Applications
  3. TWO-MINUTE DRILL
  4. SELF TEST
  5. SELF TEST ANSWERS
By: McGraw-Hill/Osborne
Rating: starstarstarstarstar / 2
March 22, 2007

print this article
SEARCH DEV SHED

TOOLS YOU CAN USE

advertisement

The OC4J home page shows all the deployed Web and EJB modules for an OC4J instance. The same page also shows a summary of application performance statistics, such as request processing time and method execution time. You can perform various management tasks by clicking the appropriate links which are grouped under the properties, resources, and security groups.

If you want to drill down into an individual application, click the link to the relevant application on the OC4J home page to get to the OC4J Application home page. Figure 8-8 shows the OC4J Application home page. From an application’s


Figure 8-8.  The OC4J Application Home Page

home page, you can monitor the status and performance metrics in the General section, right at the top of the page.

The two important sections in the Application home page are the Web Module and EJB Modules sections, which show the status and performance details about these two types of modules. You can drill down to the home pages of the various components of the two types of modules such as servlets, JSPs, and EJBs from the Web Module and EJB Module home pages.

Deploying and Registering Web Providers

You use Web providers to provide content to OracleAS Portal. Chapter 7 explains how Web and database providers work. Deploying Web providers is similar to deploying J2EE applications, because Web providers are regular J2EE applications. Portlet developers can use EAR files to deploy Web providers to the OracleAS Middle Tier. After you deploy a Web provider, you test the deployment using the URL of the provider adapter server, as shown here:

  http://hostname:port/context_root/ providers

If your deployment is successful, you’ll see the test page. If you disable the test page, client browsers will get a "403 Forbidden" response.

All Web providers must be registered with the OracleAS Portal, using the OracleAS Portal Web user interface. Registering the providers lets OracleAS Portal know how to access the providers. The portlet developer must provide the portal administrator the necessary deployment and registration instructions.



 
 
>>> More Oracle Articles          >>> More By McGraw-Hill/Osborne
 

blog comments powered by Disqus
escort Bursa Bursa escort Antalya eskort
   

ORACLE ARTICLES

- Oracle Java Security Woes Continue
- Oracle's New IaaS Cloud Option: There's a Ca...
- Oracle Acquires Eloqua to Boost Cloud Presen...
- Choosing Innovation: Oracle Survey Insights
- Oracle Fixes Privilege Escalation Bug
- Oracle`s Communications Service Availability...
- Oracle Releases Exalytics, Taleo Plans
- Oracle Releases Communications Network Integ...
- Oracle Releases Communications Data Model 11...
- Oracle Releases PeopleSoft PeopleTools 8.52
- Oracle Integrates Cloudera Apache Distro, My...
- Oracle Releases MySQL 5.5.18
- Oracle Announces NoSQL Database Availability
- Sorting Database Columns With the SELECT Sta...
- Retrieving Table Data with the LIKE Operator

Developer Shed Affiliates

 


Dev Shed Tutorial Topics: