Skip to main content

Deployment options

At high-level, ProactivePack can be deployed in 3 ways :

  • The standard product installation consists in installing ProactivePack on a server provided by the customer
  • The appliance is a pre-configured VMWare image that has the ProactivePack software preinstalled.
  • The container is a container image that contains the preconfigured ProactivePack software.

Deployment mode Main prerequisites Pros Cons
Standard product installation

Windows or Linux server including HTTP server (apache or IIS), PHP and perl. See General HW and SW Prerequisites for details.

 

Some modules require a DB server (Postgres, Oracle, MSSQL or MySQL). See Additional prerequisites by module
  • 100% compliance with company policies (OS type, version, patching...)
  • Maximum flexibility (e.g. to install on existing servers, to host other applications, etc.)
  • More time-consuming installation and configuration
Appliance 

VMWare VCenter infrastructure

(For HyperV support, check with ProactivePack support)
  • Preconfigured Linux CentOS 7 appliance, all prereqs installed
  • Minimal configuration required
  • No choice on OS/version - may not comply with company standards
Container Docker infrastructure/server
  • All the agility granted by containers
  • Minimal configuration required
  • Fast deployment
  • Customer must  already use containerized applications

Please consult ProactivePack support if you need guidance about your best option.

Back to top