10cd2a061b
This commit aims to improve the documentation's navigability by redefining some categories' purposes and titles. There is a redirection rule for each documentation page moved. This ensures that users won't have a 404 error message. task-3217827 closes odoo/documentation#8061 Signed-off-by: Jonathan Castillo (jcs) <jcs@odoo.com>
107 lines
3.3 KiB
ReStructuredText
107 lines
3.3 KiB
ReStructuredText
|
|
.. _setup/enterprise:
|
|
|
|
===================================
|
|
Switch from Community to Enterprise
|
|
===================================
|
|
|
|
Depending on your current installation, there are multiple ways to upgrade
|
|
your community version.
|
|
In any case the basic guidelines are:
|
|
|
|
* Backup your community database
|
|
|
|
.. image:: community_to_enterprise/db_manager.png
|
|
:class: img-fluid
|
|
|
|
* Shutdown your server
|
|
|
|
* Install the web_enterprise module
|
|
|
|
* Restart your server
|
|
|
|
* Enter your Odoo Enterprise Subscription code
|
|
|
|
.. image:: community_to_enterprise/enterprise_code.png
|
|
:class: img-fluid
|
|
|
|
On Linux, using an installer
|
|
============================
|
|
|
|
* Backup your community database
|
|
|
|
* Stop the odoo service
|
|
|
|
.. code-block:: console
|
|
|
|
$ sudo service odoo stop
|
|
|
|
* Install the enterprise .deb (it should install over the community package)
|
|
|
|
.. code-block:: console
|
|
|
|
$ sudo dpkg -i <path_to_enterprise_deb>
|
|
|
|
* Update your database to the enterprise packages using
|
|
|
|
.. code-block:: console
|
|
|
|
$ python3 /usr/bin/odoo-bin -d <database_name> -i web_enterprise --stop-after-init
|
|
|
|
* You should be able to connect to your Odoo Enterprise instance using your usual mean of identification.
|
|
You can then link your database with your Odoo Enterprise Subscription by entering the code you received
|
|
by e-mail in the form input
|
|
|
|
|
|
On Linux, using the source code
|
|
===============================
|
|
|
|
There are many ways to launch your server when using sources, and you probably
|
|
have your own favourite. You may need to adapt sections to your usual workflow.
|
|
|
|
* Shutdown your server
|
|
* Backup your community database
|
|
* Update the ``--addons-path`` parameter of your launch command (see :doc:`../on_premise/source`)
|
|
* Install the web_enterprise module by using
|
|
|
|
.. code-block:: console
|
|
|
|
$ -d <database_name> -i web_enterprise --stop-after-init
|
|
|
|
Depending on the size of your database, this may take some time.
|
|
|
|
* Restart your server with the updated addons path of point 3.
|
|
You should be able to connect to your instance. You can then link your database with your
|
|
Odoo Enterprise Subscription by entering the code you received by e-mail in the form input
|
|
|
|
On Windows
|
|
==========
|
|
|
|
* Backup your community database
|
|
|
|
* Uninstall Odoo Community (using the Uninstall executable in the installation folder) -
|
|
PostgreSQL will remain installed
|
|
|
|
.. image:: community_to_enterprise/windows_uninstall.png
|
|
:class: img-fluid
|
|
|
|
* Launch the Odoo Enterprise Installer and follow the steps normally. When choosing
|
|
the installation path, you can set the folder of the Community installation
|
|
(this folder still contains the PostgreSQL installation).
|
|
Uncheck ``Start Odoo`` at the end of the installation
|
|
|
|
.. image:: community_to_enterprise/windows_setup.png
|
|
:class: img-fluid
|
|
|
|
* Using a command window, update your Odoo Database using this command (from the Odoo
|
|
installation path, in the server subfolder)
|
|
|
|
.. code-block:: console
|
|
|
|
$ ..\python\python.exe odoo-bin -d <database_name> -i web_enterprise --stop-after-init
|
|
|
|
* No need to manually launch the server, the service is running.
|
|
You should be able to connect to your Odoo Enterprise instance using your usual
|
|
mean of identification. You can then link your database with your Odoo Enterprise
|
|
Subscription by entering the code you received by e-mail in the form input
|