You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

To run the JADE History Viewer Setup you need to have a running JobScheduler instance, where the setup will deploy the war file needed to run the web application and some JADE Jobs to store the informations about the JADE backround service to your database.

To get the JADE history viewer up and running take the war file and deploy it to your own servlet container, like Jetty or Tomcat.

Additionally you need to configure an context file, where you can configure under which context the web apllication will be accessible.

If you don´t configure such file, most servlet containers will use a context with the same name as the file. That will change with every release, because the version is part of the filename.

To keep it simple for your users you can make sure that the application will be accessible under the same context even if you change to a newer version of the war file.

The only thing to do is to adjust the path to the war file in the configuration as shown in the example below.

example for a jetty context configuration
<?xml version="1.0" encoding="ISO-8859-1"?>
<Configure class="org.eclipse.jetty.webapp.WebAppContext">
<Set name="contextPath">/jade-history-viewer</Set>
<Set name="war">/PATH_TO_THE_WAR_FILE/jade-history-viewer-<version>.war</Set>
<Set name="extractWAR">true</Set>
</Configure>

Because the configuration of that context differs between different servlet containers, read the documentation for your servlet container for further instructions how to configure the context file properly.

  • No labels