The Java Virtual Machine auto-detection mechanism was disabled starting from Panorama 6.0 Service Pack 1, since it was causing problems. Instead, the type of Java Virtual Machine that is used on the client-side (either Sun, Microsoft or J#) is now a parameter in the code, which can only be changed on the server-side, and therefore, generally speaking, all the clients will be using the same type of Java VM. However, see section (1.2) below for a workaround that allows for different clients to use different Java Virtual Machines.
1. Configuring the client-side technology for the welcome.htm entrance page
http://servername/panorama/welcome.htm is the default page which runs the Classic Analytics.
The default Java VM is Sun Java.
Under NovaView home directory (..\panorama\E-BI on the NovaView Server) locate the welcome.htm file and open it for text editing. In the following code locate the TYPE parameter:
And change its value according to the following table:
0: MS Java
1: Sun Java
2: MS J#
4: Flash
Delete the cookies and temporary internet files on the client for the change to take effect.
1.2 Workaround for using several different Java VMs
As you change the TYPE parameter on the server side, every client that accesses this welcome.htm page will be forced to use the JVM defined on the server.
However, it is possible you have different client stations that use different JVMs. In this case, you should create copies of the welcome.htm page on the Novaview server, one for each JVM you intend to use in your organization.
For instance: You would like to use Sun JVM and Microsoft JVM.
You would create two pages, welcomeSun.htm and welcomeMS.htm (the filenames are of no importance, of course). The first file will have the TYPE parameter as 1, and the second will have it as 0.
You can now direct your users to their appropriate page.
2. Configuring the client-side technology in NovaView Dashboards
In NovaView Dashboards, the technology setting is configurable in the UI. Java type is configurable globally per server and the Flash/Java setting is per page.
To change the Java technology, in the NovaView Dashboard Administration backend go to Settings -> Server -> Advanced -> Java Virtual Machine and choose the desired JVM as shown on the following screenshot.
Click OK to confirm.
3. Configuring the client side technology for a custom web page
If you have a custom web page which embeds NovaView applets using the NovaView APIs, edit your code and locate all the BeginNovaView(..) statements. In every such function call, change the last parameter (4th out of 4) to:
0: Flash Analytics
1: Classic Analytics (Java)
The default Java technology is Sun Java. In order to use an alternative technology, add a pnJVMType JavaScript variable before the BeginNovaView() call with the following values:
"Ms" - MS JVM
"Sun" - Sun JVM (default)
"Net" - .NET J# VM
Example:
4. Configuring the client side technology for the NovaView Excel Client
Under NovaView home directory (..\panorama\E-BI on the NovaView Server) locate the welcomeExcel.htm file and open it for text editing. Change the TYPE parameter in a similar way to section (1) above, but add 64 to the TYPE value:
64: MS Java
65: Sun Java
66: MS J#
68: Flash
5. Configuring the page opened with "Run Web Access As..." feature from NV Administrator
The page that opens this feature still uses the old auto-detection mechanism. You can control it by editing the file Panorama\E-BI\AppTemplate.htm.
In it, find the line:
BeginNovaView("100%","100%","master",0);
The parameter in red can be changed to the following values:
0 : Use old Auto-Detection mechanism to determine type of JVM
5 : Force using Microsoft JVM
6 : Force using Sun JVM
