On-premise kippy installation - Internal DB - Technical specification

Background

Kippy is available on Google Cloud as a shared or dedicated instance. However, if you need a kippy instance on your own private infrastructure, kippy is also available as a dedicated private instance deployed directly on to your infrastructure. 

Kippy will be deployed on a Java Tomcat Application server, on Linux or Windows, and use its own internal mechanism for persistence.


 

You will need to provide:

A production ready Tomcat application server. 

Remote access with sufficient privileges to install and deploy to the server. 

Outbound internet access over http and ssh.

Our responsibility:

- Deploy kippy

- Configure to connect to your mail server

- Test deployment

- Critical application fixes, patches and upgrades

- Populate kippy with Level1 data and users

- Application support as per agreed support SLAs

Your responsibility:

- All monitoring and alerting

- Networking and security

- User acceptance testing

- Regular backups of virtual machine with file system

- Infrastructure maintenance

- Vulnerability testing

- Penetration testing

Technical notes:

The default installation is a single node deployment - with no failure over or resilience - other options are available.

The data is persisted internally to files. Files must be backed up regularly to restore the system in case of failure.

Kippy requires a minimum of 32Gb of RAM for a typical enterprise deployment. 

Kippy requires a minimum of 2.4 GHz x64-bit CPU (or equivalent)

Kippy requires a minimum of 100 GB of available storage space

Kippy requires a Linux or Windows operating system

All infrastructure must be production ready 

All infrastructure components must be a on modern, supported, stable version