Databases Reference
In-Depth Information
Most of the business logic development for APEX is done using PL/SQL. Although PL/SQL does support
function and code reusability to a degree, this does not extend outside of the business tier. For instance,
in traditional development tools, you could create different buttons that all inherit from a single generic
button class containing a common set of behavior. This level of OOP in the user interface is not
supported in APEX.
Lastly, it's important to keep in mind that APEX is a platform with standard behavior and functionality. It
doesn't offer the same freedom that a traditional development tool does, so if you need to achieve
certain functionality that APEX does not provide out of the box, you will need to get your hands dirty
with JavaScript, AJAX, and DHTML.
1-2. Identifying an APEX Deployment Model
Problem
You want to deploy APEX. You've heard there are a couple of different ways to do it, and you're not sure
which deployment model would suit your needs.
Solution
The main decision fork when deploying APEX is deciding which HTTP server to use to serve your APEX
applications. Oracle provides two types of HTTP servers:
•
Oracle XML DB HTTP Server (embedded PL/SQL gateway)
•
Oracle HTTP Server and mod_plsql
Choose the Oracle XML DB HTTP Server if:
•
You want a simpler two-tier deployment (web browser and database server).
•
Your priority is to simply get up and running in the shortest time possible with as
little configuration as possible.
•
You don't wish to install a separate server to host the HTTP server.
•
You are deploying APEX on a personal PC as a standalone system.
Choose the Oracle HTTP Server and mod_plsql approach if:
•
You want a full three-tier deployment (web browser, HTTP web server, and
database server).
•
You are deploying APEX in an enterprise environment and need access to an
extensive set of web server configuration and log settings.
•
You intend to expose the APEX application to the Internet. This is for security
purposes and will be explained in detail in the “How It Works” section.
•
You need Single Sign On (SSO) integration.
•
You need mid-tier load balancing and failover features.
