Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. A sample knowledge repository is distributed with the OpenCDS deployment file (the 'war').
  2. Download opencds-knowledge-repository-data.zip from the OpenCDS website | Members | Binary Downloads | at http://develop.opencds.org/OpenCDSDemo/latest/opencds-knowledge-repository-data.zip
  3. Unzip it to the location specified in the OpenCDS Configuration discussion above.
    1. The location must be on a filesystem visible to the running instance of Tomcat.

Jar-based Method

NOTE: This option is for developers and advanced users.

  1. A test repository is included in the war, and may be updated with custom repository elements .The procedure for updating the jar within the war is as follows:
  2. Build the filesystem consistent with a the folder hierarchy and contents of the opencds-knowledge-repository-data.zip file.
    1. e.g., resources_v1.1/...
  3. Get the name of the jar that will be replaced:

    Code Block
    jar -tvf opencds-decision-support-service.war

    The file in the current SNAPSHOT version is located as "WEB-INF/lib/opencds-knowledge-repository-data-1.2.0-SNAPSHOT.jar"; look for this file or a file similar to it.

  4. create a jar with the contents:

    Code Block
    jar -cvf opencds-knowledge-repository-data.jar resources_v1.1

    This will package the "resources_v1.1" folder hierarchy into the jar.

  5. Replace the jar in the war, e.g.:

    Code Blockjar -uvf opencds-decision-support-service.war WEB-INF/lib/opencds-knowledge-repository-data-1.2.0-SNAPSHOT.jarby following the standard procedures for manipulating jar files.
  6. NOTE: Developers may update their local copies of the codebase to automatically build the war with a custom repository.  However, please do not commit this to the repository.

...