Tuesday, March 28, 2017

Oracle Application Express 5.1.1 now available

Just in time for APEX World 2017, Oracle Application Express 5.1.1 is now released and available for download.  If you wish to download the full release of Oracle Application Express 5.1.1, you can get it from the Downloads page on OTN.  If you have Oracle Application Express 5.1 already installed, then you need to download the APEX 5.1.1 patch set from My Oracle Support.  Look up patch number 25341386.

As is stated in the Patch Set Note that accompanies the Oracle Application Express 5.1.1 patch set:
  • If you have Oracle Application Express release 5.1 installed, download the Oracle Application Express 5.1.1 patch set from My Oracle Support and apply it.  Remember - patch number 25341386.
  • If you have Oracle Application Express release 5.0.4 or earlier installed, download and install the entire Oracle Application Express 5.1.1 release from the Oracle Technology Network (OTN).
  • If you do not have Oracle Application Express installed, download and install the entire Oracle Application Express 5.1.1 release from the Oracle Technology Network (OTN).

As usual, there are a large number of issues corrected in the Application Express 5.1.1 patch set (over 106!).  You can see the full list in the 5.1.1 Patch Set Notes.
at

2 comments:

  1. Arun GuptaApril 10, 2017 3:52 PM

    Joel,
    We are on APEX 3.2 and looking to an upgrade path to the latest version. Since the newer versions recommend using ORDS with Oracle WLS, this is the path we are going to take. The issue we have is that with Oracle HTTP server and mod_plsql, we had created database access descriptors pointing to different environments. So, on the same APEX box, we had dev, UAT and pre-prod APEX instances. How can we do it with WLS? Not sure if I explained it properly.

    Thanks,
    Arun

    ReplyDelete
  2. Joel R. KallmanApril 11, 2017 9:11 AM

    Hi Arun,

    This should be easy. One simple way to achieve this *before you run any configuration with ords.war* is to first copy and rename ords.war, and then deploy that. For example, you could have dev.war, uat.war, preprod.war. And this would be your corresponding context root (e.g., http://server:port/uat/f?p=....).

    I hope this helps.

    Joel

    ReplyDelete