X

The Oracle APEX blog is your source for APEX news, technical tips and strategic direction

  • October 12, 2018

Announcing Oracle APEX Static Resources on Content Delivery Network

Joel Kallman
Senior Director, Software Development

[Image by Ludovic of Privacy Canada, is licensed under Creative Commons Attribution-Share Alike 3.0 Unported license]

We are pleased to announce the availability of APEX static resources on a Content Delivery Network (CDN).  

As defined in Wikipedia, "a content delivery network or content distribution network (CDN) is a geographically distributed network of proxy servers and their data centers. The goal is to distribute service spatially relative to end-users to provide high availability and high performance."  If you have an application which is used by an audience geographically distributed around the globe, you can improve the overall performance of your application by having some of the content delivered from servers physically closer to the end-user. 

For example, if I have an application running on the free site https://apex.oracle.com (which is running in a data center in Austin, Texas USA), and a user in Vinnytsia, Ukraine runs my application, they will need to wait for the static files associated with my APEX application to be physically transmitted from Texas to Ukraine.  There is greater network transmission time and higher risk of latency the further away you are from the source.  This results in degraded performance, and is especially perceptible on mobile devices.  But with a CDN, the files may be delivered from a server which is physically closer to the client, and it's all done transparently.

The Oracle APEX 18.1 and APEX 18.2 static resources are available via the following paths:

https://static.oracle.com/cdn/apex/18.1.0.00.45/

https://static.oracle.com/cdn/apex/18.2.0.00.12/

 

It is really easy to make use of this.

1) If you want to convert the entire APEX instance to use the static resources from the CDN, you will want to reset the APEX image prefix for your instance.  You should not do this on a live system, as this process will invalidate many objects in the APEX schema and they will need to be recompiled.  Again - don't do this on a live system.  To accomplish this:

  • Locate your APEX distribution
  • Navigate to the apex/utilities subdirectory
  • Connect to your database as user SYS
  • Run:  @reset_image_prefix.sql
    and when prompted for the image prefix, enter the correct path, like:
    https://static.oracle.com/cdn/apex/18.2.0.00.12/

If you're using Oracle REST Data Services (ORDS) with APEX, you will need to restart ORDS after resetting the image prefix.

 

2) If you simply want to use the CDN-hosted resources in a single APEX application:

  • In Application Builder, edit your application and click Shared Components
  • Click User Interface Attributes
  • In the Image Prefix attribute, enter the correct path:  https://static.oracle.com/cdn/apex/18.2.0.00.12/
  • Click Apply Changes.  That's all there is to it!

 

Anyone on the planet is welcome to use the APEX resources available via the Content Delivery Network.  If you have an application that is used around the world, you should consider using the CDN.  If you have an application which is only used within a specific geography or only within your company, it may remain faster to have the APEX static resources served by your infrastructure.  Testing can prove this.

We will be updating the free site https://apex.oracle.com to make use of the CDN.

 


Updates for later APEX Versions

  • April 7, 2019:  APEX 19.1 static resources are now available at https://static.oracle.com/cdn/apex/19.1.0.00.15/
  • November 19, 2019:  APEX 19.2 static resources are now available at https://static.oracle.com/cdn/apex/19.2.0.00.18/