Because instruction is for "fresh" install, I propose run apxremov.sql script before install APEX 5.1.

It will remove also APEX static files from database

It is mentioned in documentation A.4.2 Removing Oracle Application Express from the Database.

And of course you run script that comes with XE, and not version you going to install.

You find script from your XE installation $ORACLE_HOME/apex

Few more comment:

Instead altering default profile by command

alter profile default limit password_life_time unlimited;

I would create new profile where password not expire and assign that for needed users.

Just wonder where you need this below?

alter system set job_queue_processes=100 scope=spfile;

And maybe you check how these parameters works. Do you really need 250 sessions and why set processes parameter.

alter system set sessions=250 scope=spfile;
alter system set processes=200 scope=spfile;

I would remove Tomcat HTTP connector.

In HTTPD I would use something like below for APEX static files so you don't need define separately file types.

And you can use longer expire.

# Alias to APEX static files
Alias "/i/" "/var/www/apex/images/"
<Directory "/var/www/apex/images/">
  AllowOverride   none
  Require         all granted
   <IfModule expires_module>
    ExpiresActive   on
    ExpiresDefault  "access plus 10 year"
    <IfModule headers_module>
      Header append   Cache-Control "public"
     </IfModule>
   </IfModule>
</Directory>

Denis Savenko wrote:

 

It is better to combine both approaches (in order to cache apllication-based static files as well).

I didn't quite understand what you mean by this.

Could you please explain?

If you mean e.g. workspace and application static files that are stored to database, APEX 5.1.x adds by default needed headers that client caches files.

And you can cache those also in HTTPD, see this blog post

Denis Savenko wrote:

Didn't you think about sharing your blogging platform with the community?

Yes, I have think. Application is available in SourceForge.
Unfortunately, SourceForge having some issues right now. At least I get error when try access there.

And unfortunately I haven't yet find time to publish new version for APEX 5.x.

But it is coming some point and maybe I move project to GitHub

Ok,

Keep us up to date.

regards

Denis Savenko wrote:

 

Just wonder where you need this below?

Excerpt from the docs: JOB_QUEUE_PROCESSES determine the maximum number of concurrently running jobs. In Oracle Application Express transactional support and SQL scripts require jobs. If JOB_QUEUE_PROCESSES is not enabled and working properly, you cannot successfully execute a script. I don't remember clearly, but also I read somewhere that APEX processes also utilize JOBs for running.

Link is bad for me.  I found a similar document. But, the quoted section of text was in the EPG Deployment section.

I can see EPG using job_queue_processes threads.

You can probably skip this step if you're using ORDS.

My $0.02

MK