Deployment/Publishing

Omniscope deployment options

Share visualisations and data-driven interactivity in a wide variety of formats 

This section deals with various options for deploying data-bearing and non-data bearing report/'dashboard' files assembled, refreshed and managed in Omniscope (both as IOK/IOM files and exportable HTML5/JavaScript interactive visualisations created in Omniscope). Omniscope has the full range of deployment options, enabling anyone to create and refresh a single IOK file that will  address an unlimited range of recipients using all types of devices, from browser-only HTML5/JavaScript deployments to devices that do not support the Java free Viewer (like iPads, Android tablets & Chromebooks) to full Windows tablets that DO support the free Viewer, to Windows, Mac & Linux desktop/server machines etc.

Interactive Options:

IOK files: Omniscope IOK files can be saved to shared folders, exchanged via email, or posted for download on intranet/extranet web pages. They can be accessed by others with the free Omniscope Viewer or a licensed edition installed, or using Java Web Start (below). Omniscope .IOM files are produced by Workgroup Editions of Omniscope and are the same as .IOK files, except that they can only be opened in activated Editions of Omniscope, not the free Viewer.

Omniscope Web Server HTML5/JavaScript (2.9+): Once you have fully-populated and configured an IOK file, you may choose to export interactive visualisation tabs via links that will display in any modern browser, including the browsers on devices that do not support the Java free Viewer, like iPads and Android tablets.

 

Web Integration: Omniscope is a 'hybrid' desktop/web application, with internal browser windows (Web Views) and the ability to act as a universal web services local client. In web service client mode, Omniscope facilitates user interaction and input on the user desktop, then enables to user to submit their selections and input to configured remote web services. The HTML-formatted response from the remote server can be displayed in an adjacent Omniscope Web View or the users' default browsers. The response may also return other formats, including other Omniscope IOK  files, HTML5/JavaScript visualisations and static images displayed 'on demand'.

Omniscope Web Start: The Omniscope Online option uses Java Web Start, standard Java technology for deploying Java applications temporarily over the web. Launched from a single link (known as a JNLP link) on your website or in an e-mail, Web Start allows an audience to use the Omniscope Viewer, without fully installing it, to open and explore your IOK files. Please note that Omniscope Online has some minor Web Start-imposed performance and feature limitations compared to the fully-installed Omniscope free Viewer.

Omniscope Custom JARs: You may also choose to combine your IOK data/report/dashboard file with a free Viewer in a single Java JAR file, which almost any computer with Java installed will open. The combined files can be too large to email, since they include free Viewer installers, but they can be downloaded and synchronised via folder delivery/synch services such as DropBox, GDrive, Skydrive etc.

Publishing DataPlayer .SWFs (legacy): DataPlayers created and exported from Omniscope are stand-alone universally-accessible Flash .SWF files that contain all the data, visualisations and interactive query devices in a single file. DataPlayers greatly increase the ultimate reach of Omniscope-based reporting solutions as they can be posted and re-posted/overwritten to web pages just like any other SWF file, as easy as uploading a picture. They can also be embedded in common document files such as PowerPoint, Excel and Acrobat .PDF with full interactivity. Export options from the DataPlayer View of Omniscope include exporting the DataPlayer .SWF in an HTML wrapper for posting, or exporting as a standalone .SWF to overwrite the existing file of the same name already on the web server with a newer one containing refreshed data. 

Applet Limitations: This article provides more detail on why Java Web Start/custom JARs (and not Applets) provide the better results for no-installation deployments of Omniscope-based solutions.