Alexander,

First please ensure you are using the latest version. See this post:
http://forums.visokio.com/discussion/3023/2.9-2.9-plus-webstart-support


Secondly, if your clients are using Chrome:

Chrome no longer supports the Java Plugin. You only need this if you want auto-detection of Java.

We can assume your clients already have Java installed. If they didn't, they wouldn't be able to use Web Start at all. In which case they would need installation privileges, and would do better installing Omniscope itself.

So you should bypass the Java Plugin check altogether, and instead of the launch button, host a link to the JNLP file. For example here is our own non-customised JNLP file:
http://tc.visokio.com/webstart/launch.jnlp?branch=2.9&rand=

When the client clicks this, the JNLP file will be downloaded and Chrome will show this at the bottom of the window. Your client should click this to launch the app.


Thirdly, please note:

Web Start and general support for Java within browsers is slowly being phased out by browser vendors.

Ultimately we will advise our clients to use Omniscope Mobile, but at present some aspects of Mobile are not fully featured enough to satisfactorily transition your existing reports.

In the interim you can also consider distributing the free Viewer "JAR" version of Omniscope along with the IOK file. Your clients would download and double-click the JAR to launch Omniscope without any installation privileges required. You can streamline this by creating a custom JAR in 2.9.

Hi Steve, We are using the link to the jnlp file. And our JAR is up-to-date.

One specific user is using Java 7 update 60. Would you expect any problems?

Alexander,

Java 7 is past end-of-life and no longer supported by Oracle. Accordingly it is no longer supported by us. Consequently we are no longer testing it, and don't know whether using Webstart will continue to work.

Your customer should update to Java 8, which should be done for security reasons alone anyway.

Your last resort is to distribute a JAR to download and double-click as advised above.

Steve

HI Steve,

A client is not allowed to update to latest Java8 Update 66. Company IT department says Java 8 Update 35 is the highest they are able to install...

Java 8 update 35 is not a solution for making JNLP work. What would you do?

Thanks!

Can they install Omniscope? Or can they download and double-click Omniscope.jar?
E.g. as currently downloaded here:
http://downloads.visokio.com/omni29/auto/2-9-rc-Plus_b1793/Omniscope.jar

Will check! Thanks!

The jar works.

Our jar does not work, what do we need to investigate?

So our JAR (linked above) works and yours doesn't? What's customised in your JAR? Is it code-signed? Send us your JAR or a link to it and we'll compare.

Hi Steve,

Thanks. Just send you an email with a link to our jar.

Your JAR is the 2.9 b1792 version, unchanged. The JAR I linked above is 2.9 Plus b1793, in fact a substantially different version ("Plus" is a much more recent development stream).

I don't see why the older 2.9 JAR would not work. Both versions work fine for us upon double-clicking.

For whom does it not work? Just your client, or yourself also?
What do they see, exactly?

It works fine for me. Our client is getting "Application blocked by Java Security"

Steve, just send you an email.

As discussed by email, this issue was resolved by using "2.9 Plus", rather than the older "2.9" JAR.