Standard Web Application

The ds9 Standard Web Application (ds9App) is the easiest way to deploy a ds9 solution to end users.

ds9App

Viewers are grouped in projects and end users can be granted access to these projects and viewers.

Access to Viewers in ds9App

To publish the results of a ds9 solution or project to end users you need a ds9App installation. This ds9App installation is usually running on the same host as your ds9 system but could as well be hosted in your company's Intranet.

Whatever viewers are defined in a ds9 solution or project can be published via the Webservice API.

For the ds9App installation to get access to a published viewer, a technical user needs to be granted access in the User Rights Management of ds9 Solution or ds9 Developer's Edition.

Multiple viewers from different ds9 systems can be combined into one or more ds9App projects. End users can be granted access to ds9App projects or individual viewers in these ds9App projects.

The layout and look and feel of the ds9App and the viewers can be customized to correspond with the corporate identity or intranet presentation of your company.

 

ds9App Stub

Integrating ds9App into Third Party Applications

ds9App is available as program stub that can be integrated into third party web applications. At the moment the stub is available for Java applications, but upon customer request we would provide a stub for other programming languages, .NET, Python, PHP,...

Integrating the ds9App Stub into third party web applications requires only a few steps:
  • Adaptation of CSS styles and image resources to match the layout of the third party application
  • Configuration of the URL of the ds9 system that is to be connected to
  • Configuration of the id of the viewer that is to be accessed
  • Configuration of the user credentials of the technical user that is authorized to access the viewer via Webservice API
The ds9App Stub requests viewers from their ds9 system. The viewer response is a full HTML page that loads styles and Javascript resources from the local application, so that it can be customized. The HTML page of the viewer looks to the third party application as if coming from the same origin (server) and is therefore not causing any Cross Resource Sharing (CORS) issues. Subsequent requests to the viewer only transfer JSON data and HTML chunks.

The third party application could itself be part of a corporate website, so that the viewer could be published on the web accessible by all visitors of the website without the need to login. Use cases for this could be:
  • A Search Engine for the website
  • A News Tracker widget scrolling through some latest information
  • A Search Engine for a specific topic, linking to external web content