1 / 6

OracleAS in Use

OracleAS in Use. Chris Roderick AB-CO-DM. Outline. Why AB-CO-DM requires a J2EE platform AB-CO-DM non-functional requirements The alternative platforms The AB-CO-DM solution Summary. Why AB-CO-DM requires a J2EE Platform

burton
Download Presentation

OracleAS in Use

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OracleAS in Use Chris Roderick AB-CO-DM J2EE Platform Working Group Meeting

  2. Outline • Why AB-CO-DM requires a J2EE platform • AB-CO-DM non-functional requirements • The alternative platforms • The AB-CO-DM solution • Summary J2EE Platform Working Group Meeting

  3. Why AB-CO-DM requires a J2EE Platform • To run J2EE Applicationsnamely LHC Logging (JSPs, Servlets, Struts, POJOs). • To serve Oracle Forms6i onwards (Applet, Servlets, Java Beans). AB-CO-DM Non-Functional Requirements • Application management(e.g. easy deployment, start / stop, access to application logs, & fine grained data source / security configuration). • Application monitoring(e.g. availability, request, processing & connection monitoring). • Resource monitoring (e.g. memory & CPU monitoring). • Internally supported J2EE platform (e.g. by IT-DB & or AB-CO-IN). • Oracle supported solution (e.g. provision of patches as necessary). • Secure solution that can be patched over time as necessary. • Common solution for J2EE Apps & Oracle Forms. J2EE Platform Working Group Meeting

  4. The Alternatives Platforms OC4J • 1x Oracle J2EE container • 1x HTTP server 9iAS / 10gAS – Java Edition • 1..n Oracle J2EE containers (tested up to 17 containers by IT/DB before problems) • 1x HTTP server – aka OHS • 1x Oracle Enterprise Manager (AS & Application management & monitoring tool) • Oracle Web cache 9iAS / 10gAS – Enterprise Edition as above +  • Oracle Forms Services (Forms 9i & 10g) • Oracle Reports Services • Oracle Portal • Oracle Personalization • etc. J2EE Platform Working Group Meeting

  5. The AB-CO-DM Solution • 9iAS / 10gAS – Java Edition (Used Operationally Since May 2004) • Meets the functional requirements for J2EE apps. • Meets all of the AB-CO-DM non-functional requirements (except for the common solution – see below). • Is highly manageable via the Enterprise Manager Tool. • General configuration (installation, startup, reboot), security, and patching is handled by IT/DB (Nilo & Montse). • OC4J • Although meets the functional requirements for J2EE apps; Does not meet any of the AB-CO-DM non-functional requirements. • 9iAS / 10gAS – Enterprise Edition • This is envisaged as the future solution for AB-CO-DM. This will enable a common platform solution for both J2EE apps & Oracle Forms. This solution is not currently used, as the centrally provided Forms development tools are still related to Forms 6i rather than 9i. J2EE Platform Working Group Meeting

  6. Summary • The Oracle AS does everything OC4J does, but in a more comprehensive manner. • Being able to have multiple OC4J’s on a single machine makes resource pooling a real possibility. • For our requirements, the AS is unofficially supported by IT/DB (Nilo & Montse). • Other CERN units use the Oracle AS (e.g. AIS apps), and so there is existing knowledge / expertise available. • In the future, AB-CO-DM would like to use the AS Enterprise Edition, but this would not be necessary for, nor effect, other project platforms. J2EE Platform Working Group Meeting

More Related