Step by Step Oracle APEX Installation On Tomcat 1696484581
Step by Step Oracle APEX Installation On Tomcat 1696484581
Topics:
− Overview
− Architecture
− The Oracle RAD Stack
− Understanding Oracle APEX Installation
− Database
− Web Listener
− Multi-Tenancy
− Environments
− Roles and Responsibilities
Overview
Oracle Application Express (APEX) is a low-code development platform that enables you to build scalable, secure enterprise apps, with
world-class features, that can be deployed anywhere.
Client Browser
Mobile Device
Architecture
This stack provides all the necessary components to develop and deploy
world-class, powerful, beautiful, and scalable apps.
1. Database
2. Web Listener
3. Multi-Tenancy
4. Environments
5. Roles and Responsibilities
• Database
The installation of Application Express creates a separate schema (APEX_230100 for APEX 23.1) to house the programs that make
up the Application Express engine and related metadata tables.
Following the install guide, at a certain moment, we have to run the following command, when logged in as SYS with the SYSDBA
role, on the command line:
@apexins tablespace_apex tablespace_files tablespace_temp images
− tablespace_apex is the name of the tablespace that contains all the objects for the APEX application user.
− tablespace_files is the name of the tablespace that contains all the objects for the APEX files user.
− tablespace_temp is the name of the temporary tablespace of the database.
− images is the virtual directory for APEX images. To support future APEX upgrades, define the virtual image directory
as /i/.
Oracle recommends you create tablespaces specifically for the Application Express engine and Application Express files to enable
better management and monitoring.
For example, Tablespace APEX_TS_230100 would contain the Application Express engine and APEX_TS_FILES for the Application
Express files, but the names are arbitrary.
Your initial installation step, as outlined in the Oracle Application Express Installation Guide, Downloading from Oracle Technology
Network, would then be
@apexins.sql APEX_TS_230100 APEX_TS_FILES TEMP /i/.
In Multitenant architecture, Oracle has a great option to act as a System as a Service (SaaS), and create different databases for
specific applications such as sales database, hr database.
So installing apex in different PDB is good to maintain and you can install apex in different PDB databases.
The key benefit of the Oracle Database 12c or later multitenant architecture is that the database resources, such as CPU and
memory, can be shared across all of the PDBs.
This architecture also enables many databases to be treated as one for tasks such as upgrades or patches, and backups.
by: Sherif Abdelmoneom Ramadan Page 7 of 61
Workshop: Oracle Application Express in a on-premises (or local) installation
• Web Listener
Oracle Application Express uses a simple architecture where pages are dynamically generated using metadata stored within the
Oracle Database.
There is no code generation or file based compilation. Once fully installed, a Uniform Resource Locator (URL) is defined for both
developers and end users to access Oracle Application Express.
Users require only a Web browser and the required URL. No additional client software is required.
The Web listener functions as a communications broker between the Web browser and the Oracle Application Express objects in
the Oracle database by mapping browser requests into database stored procedure calls.
You have a choice of three Web listeners.
− Oracle REST Data Services (preferred option - formerly Oracle Application Express Listener).
− Oracle HTTP Server.
− Embedded PL/SQL gateway.
Using Oracle REST Data Services creates an architecture which consists of:
− A web browser
− Oracle REST Data Services
− Oracle Database containing Oracle Application Express
The major advantage of this architecture is the separation of the mid-tier and the database tier.
• Multi-Tenancy
• Environments
When you install Oracle APEX, you can install two different environments:
− Runtime environment (Run apxrtins.sql). In a runtime environment users can run applications but cannot modify them.
Select this option for production implementations.
− Full development environment (Run apexins.sql). In a full development environment, users can develop, modify, run, and
delete APEX applications. This option provides complete access to the APEX environment.
It's always possible to switch from a runtime to a production environment and vice versa.
− If you want to convert a runtime to a full development environment log in as SYS with the SYSDBA role and on the
command line type @apxdvins.sql. For converting a full development to a runtime environment, type
@apxdevrm.sql. For more details see the installation guide.
− Another way to restrict user access can be accomplished by logging in to the APEX Administration Services, where we
can (among others) manage the APEX instance settings and all the workspaces.
We can do that in two ways:
http://server:port/ords/apex_admin: Log in with the administrator credentials
http://server:port/ords/: Log in to the workspace internal, with the administrator credentials. After logging in,
perform the following steps:
1. Go to Manage Instance → Select Security.
2. Select the appropriate settings for Disable Administrator Login and Disable Workspace Login. These settings can
also be set manually with the APEX_INSTANCE_ADMIN API. See the reference guide for details.
− Besides the environment of APEX itself, the applications can also be installed in a similar way. When importing or
exporting an application the Run Application Only or Run and Build Application options can be selected.
Build Status - Set the build status of the application. Options include:
1. Run Application Only - Users can only run an application. This option is an effective way to protect an application
from modifications from other developers.
2. Run and Build Application - Developers and users can both run and develop the application.
1. Instance administrators are superusers that manage an entire hosted instance using a separate application
called APEX Administration Services. Instance administrators manage workspace provisioning, configure features and instance
settings, and manage security.
2. Workspace administrators can perform administrator tasks specific to a workspace such as configuring workspace
preferences, managing user accounts, monitoring workspace activity, and viewing log files.
3. Developers are users who sign in to a workspace and create and edit applications.
4. End users can only run existing applications.
Oracle APEX release 23.1 requires an Oracle Database release 19c or later.
• Browser Requirements
Oracle APEX requires a JavaScript-enabled browser and supports the current and prior major release of Google Chrome,
Mozilla Firefox, Apple Safari, and Microsoft Edge.
Oracle APEX requires Oracle REST Data Services (ORDS) 20.x or later. ORDS can be deployed on WebLogic, Tomcat or run in
standalone mode. This article describes the installation of ORDS on Tomcat 9.
Java: jdk-11.0.19_windows-
x64_bin.exe
Tomcat: apache-tomcat-
9.0.80.exe
Database 19c: WINDOWS.X64_193000
_db_home.zip
APEX: apex_23.1.zip
ORDS: ords-latest.zip
Oracle SQL sqldeveloper-
Developer 23.1.0.097.1607-x64.zip
(optional):
Stetup Tomcat:
We used the 32-bit/64-bit Windows Service
Installer, so Tomcat would run as a Windows
Service. Install it by double-clicking and
filling in the details when prompted.
Click on Select the type of install dropdown
list and choose the Full install option and
then click Next.
Click Next.
Click Next.
Click Finish.
command:
alter session set container =
apex_pdb_23;
command:
select * from v$tablespace;
command:
CREATE TABLESPACE APEX
DATAFILE
'C:\APEX_DEV\DATABASE\oradata\PDB
S\APEX_PDB_23\apex01.dbf'
SIZE 100M AUTOEXTEND ON NEXT 1M;
command:
select * from v$tablespace;
command:
ALTER PLUGGABLE DATABASE apex_pdb_23
SAVE STATE;
command: exit;
command:
sqlplus sys/sys as sysdba
command: @apex_rest_config.sql
command:
command:
command:
command:
command:
command:
ALTER user ANONYMOUS IDENTIFIED
BY Apex_123 account unlock;
http://server:port/ords/
• APEX Features
• Oracle APEX Universal Theme
• Apps and Plug-ins
• APEX Community
Learning links
Technical topics