JS7 JobScheduler

Space shortcuts

Page tree

Problem

The JOC Cockpit's user interface and the joc.log file may report an error message like this:

Error Message when accessing Notifications
2022-06-13T05:58:03,959 INFO  qtp1099855928-9546   c.s.j.c.JOCDefaultResponse                   -
REQUEST: ./xmleditor/read
PARAMS: {"controllerId":"jobscheduler","objectType":"NOTIFICATION"}
USER: root
2022-06-13T05:58:03,959 ERROR qtp1099855928-9546   c.s.j.c.JOCDefaultResponse                   - java.nio.file.NoSuchFileException: /var/sos-berlin.com/js7/joc/resources/joc/xsd/notification/Notification_configuration_v1.0.xsd
java.nio.file.NoSuchFileException: /var/sos-berlin.com/js7/joc/resources/joc/xsd/notification/Notification_configuration_v1.0.xsd

Analysis

Notifications are managed from the Configuration->Notification sub-view of JOC Cockpit.

  • The configuration format for notifications is XML. The JOC Cockpit offers an XSD schema-aware XML Editor for configuration purposes.

  • The XSD Schema file is added by the JOC Cockpit installer. 

    • When using JS7 - JOC Cockpit Installation for Containers then the JOC Cockpit setup is not executed as JOC Cockpit ships preinstalled with the container image.
    • For container images the file is included with the image's file system.
  • If users have previously created their own volumes from earlier JOC Cockpit releases that did not include the XSD Schema then the JETTY_BASE/resources/joc/xsd directory might be missing. In fact the directory is included with the image but is not visible when an existing volume is mounted to the JETTY_BASE/resources/joc directory.
    • This problem is limited to use of volumes with containers.
    • This problem does not occur when installing JOC Cockpit on premises.

Solution

Download the XSD Schema from the indicated link and store the file in JETTY_BASE/resources/joc/xsd/notification/Notification_configuration_v1.0.xsd

If required create the xsd/notification directory in JETTY_BASE/resources/joc.