Install Akeneo PIM
#Installing Akeneo PIM Enterprise Edition (EE) with the Archive
This document provides step by step instructions to install the PIM with the archive on an environment that fulfills the expected System Requirements.
By default Composer uses packagist.org to retrieve all open source packages and their updates. To download Akeneo PIM Enterprise Edition, you have to get access to our private enterprise edition repository by sending your SSH public key to our system.
#Creating the PIM project
You need to get a PIM Enterprise Standard archive from the Partners Portal. See <https://help.akeneo.com/en_US/akeneo-portal/get-pim-enterprise-edition-ee-archive.html?utm_source=akeneo-docs&utm_campaign=portal_archive>`_
$ tar -xvzf pim-enterprise-standard-v7.0.tar.gz
$ cd pim-enterprise-standard/pim-enterprise-standard
$ composer install
#Initializing Akeneo
Copy the .env into a local .env and make the configuration in the local .env.
Configure the PIM via the .env
file:
APP_ENV=prod
APP_DATABASE_HOST=localhost
APP_DATABASE_PORT=null
APP_DATABASE_NAME=akeneo_pim
APP_DATABASE_USER=akeneo_pim
APP_DATABASE_PASSWORD=akeneo_pim
APP_INDEX_HOSTS='localhost:9200'
#Launching the PIM in dev mode
All make commands must be run from the PIM root directory, either created by the archive or from the composer create project above.
To run the PIM EE in dev mode without docker, you will need to change some configuration files:
$ cp vendor/akeneo/pim-enterprise-dev/config/packages/prod_onprem/oneup_flysystem.yml config/packages/dev/
$ cp vendor/akeneo/pim-enterprise-dev/config/packages/prod_onprem/messenger.yml config/packages/dev/
You can then launch the install with the following command:
$ NO_DOCKER=true make dev
Once this command is finished, the PIM is accessible at http://localhost:8080/
#Launching the PIM in prod mode
$ NO_DOCKER=true make prod
Once this command is finished, the PIM is accessible at http://localhost:8080/
#Setup Akeneo
#Configuring Akeneo
Akeneo PIM is configured with environment variables. The Symfony documentation explains how to use them.
#Running jobs
Akeneo PIM implements a queue for the jobs, as a PHP daemon. This daemon is a Symfony command, that can only execute one job at a time. It does not consume any other job until the job is finished.
You can launch several daemons to allow the execution of several jobs in parallel. A daemon checks every 5 seconds the queue and executes the next job from the queue.
Follow the job queue daemon set up in this dedicated section.
#Cron jobs
The application needs the following tasks to be executed in background on a regular basis. The frequency has to be adapted according to your data volume.
Edit your crontab with crontab -e
and configure your tasks.
Be sure to update the cron of the user used to install the PIM, to be able to run the command
Community Edition and Enterprise Edition cron jobs:
Symfony console command |
Crontab frequency |
Human frequency |
---|---|---|
|
0 1 * * 0 |
At 01:00 AM on Sunday |
|
0 0 1 * * |
At 00:00 AM, every first day of the month |
|
1 * * * * |
Every hour |
|
10 * * * * |
Every hour |
|
40 12 * * * |
At 12:40 AM |
|
0 3 * * * |
At 03:00 AM |
|
0 4 * * * |
At 04:00 AM |
|
15 0 * * * |
At 00:15 AM |
|
*/10 * * * * |
Every 10 minutes |
|
*/30 * * * * |
Every 30 minutes |
|
5 * * * * |
Every hour |
|
4 21 * * 0 |
At 09:04 PM on Sunday |
|
30 0 * * * |
At 00:30 AM |
|
*/10 * * * * |
Every 10 minutes |
|
0 */2 * * * |
Every 2 hours |
Additional Enterprise Edition cron jobs:
Symfony console command |
Crontab frequency |
Human frequency |
---|---|---|
|
0 5,11,17,23 * * * |
At 05:00 AM, 11:00 AM, 05:00 PM, 11:00 PM |
|
20 0 * * * |
At 00:20 AM |
|
0 2 * * * |
At 02:00 AM |
|
0 23 * * * |
At 11:00 PM |
|
0 23 * * * |
At 11:00 PM |
|
5 22 * * * |
At 10:05 PM |
Found a typo or a hole in the documentation and feel like contributing?
Join us on Github!