Summary

Synopsis

Discussion

1. Copy the contents of the drive to the scan server. If you are running separate core and scan servers, the CL does not need to be copied to the core server. If you are running multiple scan servers, repeat these steps for each scan server.

   For example:

   cd /mount/CL_230_RC1_EXT
   mkdir -p /opt/palamida/CL
   cp -rv PDL/CL/2.30 /opt/palamida/CL

2. Verify the integrity of the local copy of the signatures.

   On Linux

   run the Validate CL Signatures Script script, for example:

   bash tools/validateSigMD5s.sh /opt/palamida/CL/2.30

   You should see the message:

   INFO: The signature is intact

   On Windows

   Use the file included on the CL drive named CL2.xx_RC1.md5.

   You can use this third-party tool (http://code.kliu.org/hashcheck/) and double-click on the .md5 file, which will launch a verification window like so:

   

   All the MD5s should match.

3. Update the config/scanEngine/scan.properties file on the scan server to point to the new location:

   Note: On Windows systems, use / for paths, or escape the backslashes \\

   # Palamida Data Library Location
   signaturesDirPath = /opt/palamida/CL/2.30

4. Restart Tomcat on the scan server:

   cd $PALAMIDA_HOME/tomcat/bin
   ./shutdown.sh

   Ensure the Tomcat Java process is stopped before starting:

   ./startup.sh && tail -f ../logs/catalina.out

   Check for any errors in the logs before continuing.

5. Log into the WebUI and go to Help > About to verify the CL version.

   

Additional Information