This document explains how to instantiate a ERP5, a generic and customizable enterprise ERP system consisting of a core and various business templates (bt5s) that provide specific business features (accounting, CRM, et al) or industry templates (government, banking et al). ERP5 is based on five abstract concepts with the idea of being able to model the system to any industry and business scenario.
Note, that the recommended way of installing ERP5 for production environments is to first get a Webrunner and then install ERP5 manually. It is also possible to preinstall ERP5 in a Webrunner which is shown here. Besides these approaches, the single line installer would allow to install ERP5 directly on a machine without accessing SlapOS.
The process of installing (supplying) a software and providing it as a service (instantiation) are the same for all software. However during instantiation each instance can be configured differently.
This section will cover the specific configuration parameters used for a ERP5.
After selecting Services, Adding a new service, selecting ERP5 and the latest release, you should reach the KVM configuration menu.
Note, that at the time of writing, the configuration for ERP5 has to be provided in the XML textarea on the form displayed. Enter the following:
Partition Amount: 15 Pre-selected Software Release: software/erp5 Automatically Deploy Software: true Automatically Deploy Instances: true Automatically Run Sofware/Instance: true Custom Frontend Backend URL: <Leave empty, fill after instance creation, see below> Custom Frontend Backend Type: zope
and then click Proceed to begin compilation.
You will be forwarded back to the list of deployed services. Note that you might have to refresh the page for your new instance to appear. Once you can see it, click on entry to open the connection parameters.
You can follow the compilation by looking at the
# tail opt/slapos/log/slapos-node-software.log -f
Note, it might take a several hours for ERP5 to compile and install. Once the installation is finished, it is necessary to request a custom-frontend-backend-url using the family-default-v6 IPv6 adress for the ERP5 instance. The steps are described in the installation guide mentioned above and not repeated here.
Once the custom-frontend-backend-url is issued, the ERP5 instance can
be accessed. To go to the ERP5 interface, simply append