Child pages
  • Quickstart
Skip to end of metadata
Go to start of metadata
Documentation of the Bitrepository quickstart package.

Introduction

The Bitrepository quickstart is a package for quickly getting a basic fully functioning bitrepository reference system up on a localhost.

The quickstart will setup a bitrepository comprised of:
  • Webclient
  • AuditTrail service
  • Alarm service
  • Integrity service
  • Monitoring (status) service
  • 1 checksum pillar
  • 2 reference pillars

As the setup is basic – encryption, authentication and authorization is not enabled in the quickstart.

Prerequisites and requirements

For the quickstart to work some prerequisites and requirements exists.

All the quickstart components are meant to run on the same machine in an Linux environment. Possibility accessible from other machines, provided that firewall rules allow.

Infrastructure

The quickstart needs some infrastructure, for message exchange and file exchange

Message bus

The bitrepository needs an Apache Active MQ for sending messages between components. In the quickstart it is assumed that it is accessible on the localhost on the default port using a tcp connection. I.e. tcp://localhost:61616

It must not require any authentication to connect.

The default settings from the Apache Active MQ destribution will suffice, but the user/deployer is free to make changes to the Active MQ installation as long as the MQ can be reached as described above.

If the MQ is not available on the above url, the pillars and services simply will not work.

Apache Active MQ can be obtained from the ActiveMQ download site.

You can run this process in docker with this command

docker run -i -t --rm -e 'ACTIVEMQ_MIN_MEMORY=512' -e 'ACTIVEMQ_MAX_MEMORY=2048' -p 61616:61616  webcenter/activemq:5.12.0 /opt/activemq/bin/activemq console

 

Webserver

Per design the bitrepository uses a webdav server for file transfer. The quickstart configuration assumes that a webdav server is available on http://localhost/dav/.

It must not require any authentication to connect.

If no Webdav server is available see File Exchange Server Setup for references on setup. 

Should there be a HTTP server running on localhost that does not support webdav, or that use of another webdav server is wanted, then the ReferenceSettings.xml files for the AuditTrailService and CommandLine client needs to be have their FileExchange section changed to reflect this.

As the file location is specified per request this is not a hard requirement for deployment of the quickstart package, but something that needs to be taken into consideration.

You can run a apache2 based webdav server in docker with this easy command

docker run -it -v /some/local/folder/dav:/site/dav -p 80:80 --userns=host -u $(id -u):$(id -g) blekinge/apache_webdav

 

Runtime requirements

To run the quickstart a few system requirements must be in place.

A java runtime enviroment 1.8 or newer is needed.

For the quickstart.sh script, the "curl" is needed to retrieve the Tomcat servlet container.

Running the quickstart

When having ensured the above mentioned requirements are in place the quickstart package should be obtained from: Quickstart (newest release, devel version).

The quickstart tar.gz should be unpackaged.

Via the commandline cd to the unpacked directory and run the command "./setup.sh"

The first time running the setup script will adapt the configuration files to work with the deployed destination. Thus the quickstart will stop working if the quickstart directory is moved to another destination after the first run.

Running the setup.sh script does the following:

  • Adapt the configuration files to the environment (first run only)
  • Create sub directories and deploy the needed components to them.
  • Start the pillars
  • Download a Tomcat server for services and webclient
  • Deploy services and webclient to Tomcat server and start it.

After the script has finished the system should be accessible through: http://localhost:8080/bitrepository-webclient

Stopping and restarting the quickstart

Use the quickstart script to stop and start the quickstart components:

./quickstart.sh stop

 

 

  • No labels