Child pages
  • Installation guide for a ChecksumPillar

Versions Compared

Key

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

Excerpt

This is a installation guide for version 1.4 6 of the ReferenceChecksumPillar using a PostgreSQL database and certificates. Installation being performed on Linux.

...

...

Download the software for the ChecksumPillar:
> wget http://sbforge.org/nexus/content/repositories/releases/org/bitrepository/reference/bitrepository-reference-pillar/1.46/bitrepository-reference-pillar-1.46-distribution.tar.gz

Unpack the package:
> tar xvf bitrepository-reference-pillar-1.46-distribution.tar.gz

Install the database

...

Place the RepositorySettings.xml, the ReferenceSettings.xml and the certificate in the 'conf' directory.

ReferenceSettings

Change the following in the ReferenceSettings (The dots means parts of the ReferenceSettings, which you can ignore):

<ReferenceSettings xmlns="http://bitrepository.org/settings/ReferenceSettings.xsd">
...
  <PillarSettings>
    <PillarID>YOUR_PILLAR_ID</PillarID>
    <PillarType>CHECKSUM</PillarType>
...
    <AuditTrailContributerDatabase>
      <DriverClass>org.postgresql.Driver</DriverClass>
      <DatabaseURL>jdbc:postgresql:auditdb</DatabaseURL>
      <Username>bitmag</Username>
      <Password>bitmag</Password>
    </AuditTrailContributerDatabase
    <ChecksumDatabase>
      <DriverClass>org.postgresql.Driver</DriverClass>
      <DatabaseURL>jdbc:postgresql:checksumdb</DatabaseURL>
      <Username>bitmag</Username>
      <Password>bitmag</Password>
    </ChecksumDatabase>
...
  </PillarSettings>
</ReferenceSettings>

Bitmag.sh

Change the path to the certificate in the bitmag.sh file in the 'bin' folder.

Setup as a Service

Turn the pillar into a Linux service. Place the following script in '/etc/init.d/' (remember to replace the path):

#!/bin/sh
#-----------------------------------------------------------------------
#
# chkconfig: 345 84 14
#
# description: Service script (start, stop status) for BitMag pillar service.
#
#-----------------------------------------------------------------------

USER_ACCT="modisk01"

case "$1" in
'start')
        su - $USER_ACCT -c "/path/to/pillar/bin/pillar.sh start"
        ;;

'stop')
        su - $USER_ACCT -c "/path/to/pillar/bin/pillar.sh stop"
        ;;

'status')
        su - $USER_ACCT -c "/path/to/pillar/bin/pillar.sh status"
        ;;
*)
        echo "Usage: $0 { start | stop | status }"
        exit 1
        ;;
esac
exit $?

Validate

Start the service and look in the log (under log folder). It should have the following lines (dots for ignore the begining and/or the end the line):

  • ... Initializing ActiveMQMessageBus...
  • ... Settings component filter to: <PILLARID>
  • ... Creating the connection to the database 'DatabaseSpecifics [driverClass=org.postgresql.Driver, ...

  • ... Starting the ReferencePillar of type 'CHECKSUM'

Ensure that the pillar did not erroneous automatically create a Derby database, by validating the no 'checksumDB' or 'auditDB' folders is located either the installation directory or a conf/checksum folder.