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

Compare with Current View Page History

« Previous Version 6 Current »

To run the JADE Background Service History Viewer Setup you need to have a running JobScheduler instance: the Setup will deploy the war file needed to run the web application and the JADE Jobs required to write the information about the JADE Background Service to your database.

To get the JADE Background Service History Viewer up and running, take the war file and deploy it to a servlet container such as Jetty or Tomcat.

In addition, you need to configure a context file, where you can configure the context under which the web application will be accessible.

If you don´t configure such a 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 you have to do here is to change 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 required for the context depends on the servlet container used, we recommend that you refer to the documentation of your servlet container for further instructions about how to configure the context file properly.

  • No labels