Serving Edited EAS Console JNLP File

There are 2 problems with EAS that, as far as I know, have been around since version 11.1.2.1:
  

1. EAS Console will not be able to connect when using an SSL-offloaded, load-balanced EAS URL (such as https://example.com/easconsole/)

2. Periodically EAS will need to be restarted. The EAS Console will not be able to authenticate successfully  and the logs will be filled with “response already committed” errors.

The fix for both of these errors is to edit the “easconsole.JNLP” file. With the first we must add “:443” to the EAS Console URLs, to ensure that SSL communication will happen over port 443. For the second we have to add a line with ‘<update check="background"/>’ to the file.

In order to serve up this edited JNLP file with EAS, we must make a few changes to OHS. First we must add a directory called “easconsole” under the “E:\Oracle\Middleware\EPMSystem11R1\common\epmstatic\” folder, and place the edited JNLP file into it.

Then we must add the JNLP MIME type to OHS by editing the file “E:\Oracle\Middleware\user_projects\epmsystem1\httpConfig\ohs\config\OHS\ohs_component\mime.types”. We must add in the following line:

application/x-java-jnlp-file jnlp

Then we must edit the file “E:\Oracle\Middleware\user_projects\epmsystem1\httpConfig\ohs\config\OHS\ohs_component\epm_rewrite_rules.conf” (change as appropriate for other versions of EPM).  We must add the following line:

RewriteRule ^/easconsole/easconsole.jnlp /epmstatic/easconsole/easconsole.jnlp [PT]

Restarting OHS will put this new configuration into place. Congratulations, your “Launch” button just became useful again!