Oracle Application Server

Oracle Application Server
Name	Oracle Application Server
Developer	Oracle Corporation
Released	1999
Latest release version	integrated into Oracle Fusion Middleware
Operating system	Solaris (operating system), Linux, Microsoft Windows
Platform	x86 (architecture), SPARC
License	Proprietary

Oracle Application Server is a middleware suite produced by Oracle Corporation that provided web server, application server, and integration services for enterprise deployments. It served as a foundation for Oracle Fusion Middleware and interoperated with Oracle Database, Oracle E-Business Suite, and third-party products from vendors such as IBM, Microsoft, and Red Hat. The platform was positioned alongside competitors like IBM WebSphere Application Server, BEA WebLogic Server, and Apache Tomcat in the application server market.

Overview

Oracle Application Server offered a set of services for hosting Java Platform, Enterprise Edition applications, CORBA components, and Servlet-based web applications. It integrated with Oracle Internet Directory and Oracle9i Database to provide identity and data services, while supporting standards from Java Community Process, IETF, and W3C. Enterprises running SAP SE solutions, PeopleSoft deployments, or custom systems used the server to deliver transactional systems, portals, and service-oriented architectures like those advocated by Gartner and Forrester Research.

Architecture

The architecture combined a web tier, application tier, and infrastructure tier. The web tier included an HTTP listener derived from work compatible with Apache HTTP Server and integrated with mod_plsql-like capabilities for PL/SQL. The application tier implemented Java EE containers, thread pools, and connection management influenced by specifications from Jakarta EE and the Java Community Process; it coexisted with a process manager inspired by designs from Sun Microsystems and BEA Systems. The infrastructure tier leveraged directory services such as Oracle Internet Directory and distributed coordination technologies conceptualized in research from MIT and Carnegie Mellon University for clustering and failover.

Components and Features

Core components included a web listener, OC4J-style Java container, administration console, clustering services, and management frameworks. Features covered JDBC connection pools for Oracle Database, JMS messaging integration compatible with standards from OASIS and Java Messaging Service specifications, and support for SOAP and REST web services architectures discussed at W3C and OASIS. Additional modules interfaced with Oracle Forms, Oracle Reports, and enterprise portal technologies similar to offerings from SAP NetWeaver and Microsoft SharePoint.

Deployment and Configuration

Deployment workflows used tools influenced by Ant (software), Apache Maven, and corporate configuration practices from HP Enterprise Services and Accenture. Administrators commonly deployed on virtualized hosts provided by vendors such as VMware and Oracle VM, and automated configuration using patterns popularized by Puppet (software) and Ansible (software). Integration with enterprise directories like Microsoft Active Directory and Novell eDirectory enabled centralized user and role provisioning, while management consoles allowed change control practices aligned with standards from ITIL.

Security and Authentication

Security mechanisms encompassed SSL/TLS support based on protocols standardized by IETF, integration with LDAP directory services, and role-based access control compatible with models from NIST. Authentication options included integration with Kerberos deployments used in environments such as MIT Kerberos installations and support for federated identity through SAML assertions as specified by OASIS. The platform interoperated with hardware security modules from firms like Thales Group and Entrust for key management and with audit tools from Splunk and IBM QRadar to meet compliance regimes referenced by PCI DSS and SOX legislation.

Performance and Scalability

Scalability strategies used clustering, session replication, and load balancing compatible with appliances from F5 Networks and Citrix Systems. Tuning guidance often referenced benchmarking practices developed by SPEC and techniques advocated by Oracle Corporation engineers drawing on research from Stanford University and UC Berkeley. Caching strategies leveraged patterns from Varnish (software) and Memcached to reduce database load on Oracle Database instances, while asynchronous messaging via JMS improved throughput in architectures resembling those used by Amazon Web Services and Google Cloud Platform for large-scale services.

History and Versioning

The product evolved through releases that culminated in integration into Oracle Fusion Middleware and consolidation with technologies from acquisitions such as BEA Systems and Sun Microsystems components. Major milestones coincided with Oracle initiatives around Oracle9i, Oracle10g, and Oracle11g databases and paralleled industry movements studied by analysts at Gartner and Forrester Research. The lifecycle reflected enterprise adoption patterns seen in customers like AT&T, Bank of America, and CERN, and contributed to Oracle's positioning against competitors including IBM, Microsoft, and Red Hat.

Category:Oracle Corporation software