EBS / Chrome -- Jar Resources in JNLP file are not signed by the same certificate -- After Enabling JWS on Multi-Node

As you may already know, Chrome users must enable Java Web Start(JWS) on their EBS instance, in order to be able to run Oracle EBS applications on their browsers. (Otherwise, they encounter java problems while opening the forms apps)

Chrome hasn't not supported the Java plug-in, since the release 45 and therefore, Java Web Start is a key for the EBS Chrome users. The Forms applications and regular Java applets as part of the Oracle E-Business Suite can only run with Java Web Start. Note that, we have EBS Forms Plugin for Chrome and we were using it in the past, but it is not feasible anymore.. 

In this post, I will not go into the details of enabling the JWS. It is already addressed on MOS - "Using Java Web Start with Oracle E-Business Suite (Doc ID 2188898.1)". But, I will give you a solution to a particular problem that you may face with, after enabling the JWS.

This issue may be encountered especially in the multi apps node environments.

As you see above, the exception is "JAR Resources In JNLP File Are Not Signed By Same Certificate". Files related with the jar signing should be checked, and in order to solve this, we do the following:

We just stop service on the second node.

Backup the adkeystore.dat and adsign.txt (located in $APPL_TOP_NE/ad/admin), and copy those files from the primary node. -- overwriting the current ones. 

Lastly, we regenerate the jar files with force option and start the services..

Note that, we don't expect this issue in the EBS environments configured with shared JAVA_TOP. In those environments, we have the files shared by the nodes already. This issue is expected only on non-shared EBS Application filesystem environments.. With that, we have no problem to believe that those copy operations are appropriate , and can be considered as the solution to this problem..

That's it. That was the quick tip of the day. I hope you 'll find it useful.