Omniscope Online

Omniscope Online

Omniscope Online is an additional Omniscope Viewer deployment option for versions 2.4 and beyond of Omniscope, requiring no installation.

Help

  • If the Launch button does not work, please check you have Java 1.4.2 or later installed. If you are able, visit java.com and install the latest version of Java.
  • If when you click the Launch button you get a file download, you must open the file, instead of saving it to disk.
  • If you still cannot get Omniscope Online to start, please submit a bug report. For other feedback, please submit a support query.

Benefits

  • Zero footprint: Users can start Omniscope Viewer without any installation
  • No administrative privileges are needed
  • Publishers can create links to Omniscope Online which automatically opens the publisher's IOK files, using the link builder service.
  • Cross-platform: works on Windows, Mac and UNIX.

Requirements

  • The user's PC must have Java 1.4.2 or later installed. If this is not the case, the user will be prompted to automatically install the latest version of Java.
  • The organisation's firewall must permit download of Java Web Start files (JNLP files) and the JAR files they reference. If these files are blocked, ask your network administrator to permit access to JNLP files from tc.visokio.com and JAR files from download.visokio.com.

Limitations

  • No free trial, and cannot be activated. Omniscope Online can only be used to explore existing IOK files. To use a licensed Omniscope or the free trial in order to import your own data, you must download and install the full desktop version of Omniscope.
  • Web view, Google Maps and the DataPlayer views are unavailable.
  • Memory allocation is fixed by default. Large files may not open without using a higher memory limit than is configured by default. If this is needed, use the link builder service to configure a higher memory limit - up to 75% of physically installed memory is recommended.

How it works

  • When you click the launch button, Java Web Start software, installed on your PC as part of Java 1.4.2 or later, opens a JNLP file downloaded from Visokio.com.
  • This JNLP file describes the Visokio Omniscope application. Behind the scenes, Java Web Start downloads the necessary files and caches them for quick startup on subsequent occasions. These include the cross-platform JAR file available from the normal download page, which has been signed to verify its origin.
  • When everything is downloaded, Java Web Start asks for your approval to launch the application, before starting Omniscope.

Publishing using Omniscope Online

  • Publishers can configure their own launch buttons to launch Omniscope Online and open an IOK file of their choosing, automatically. See the link builder service for more information.

Troubleshooting

  • You have restricted access to the internet. Your PC (or your company network) has a firewall or proxy server preventing access to the Visokio website.
    Solution: Change your firewall configuration to permit access to the host specified in the error message (in this case "download.visokio.com").
  • Your Java installation needs manual proxy server configuration. When launching Java Web Start applications, your browser's proxy settings should be passed automatically to Java. In some situations Java is unable to correctly obtain proxy settings from the browser.
    Solution: manually configure proxy settings in the Java Control Panel, or contact your network administrator.
  • Java is not properly installed or deployed. Web Start became bundled with Java from version 1.4.2 of Java onwards. Prior to that, it was provided as a separate application, Web Start version 1.2. Older versions of Web Start had instabilities and glitches, which may result in the proxy settings not being obtained correctly from the browser, resulting in this error.
    Solution: re-install Java (version 1.5 recommended, or 1.4.2 as a minimum) or contact your system administrator who should re-deploy a Java 1.5 / 1.4.2 installation with Web Start working and tested.

 

Back to Deployment Options


Knowledge Base Top