This is the documentation for older versions of Odoo (formerly OpenERP).

See the new Odoo user documentation.

See the new Odoo technical documentation.


As you have seen, the complete architecture of OpenERP includes the following elements:

  • сервер базы данных,

  • an OpenERP application server,

  • клиент-веб сервер OpenERP,



Deployment is the process of putting an OpenERP database into a production-ready state, where it can be used by everyone in your business for their daily work. You would usually configure OpenERP and load data into it on one development system, train staff on that or another training system and deploy it onto a production system that has better protection against failure, better security and more performance.

Варианты развертывания

To deploy OpenERP in your company, several options are available to you:

  • a SaaS (Software as a Service) or On-Demand offer, which includes the equipment, the hosting, the maintenance and the support on a system configured to your needs in advance,

  • an internal installation, that you manage yourselves or have managed by an IT services company such as an OpenERP partner,

  • hosting by a server supplier on which OpenERP is installed, which enables you to proceed to add adaptations on your server.

Наиболее часто используются первые два подхода.

The SaaS (Software as a Service) Offer

SaaS is a complete package hosted at a supplier, that includes the following services: server hardware, hosting of the generic solution, installation and initial configuration, redundancy of the architecture, backups, system maintenance and support. It is also known as On-Demand.

It is provided in the form of a monthly subscription with a fixed price per user. You can find the detail of Tiny's SaaS packages at

SaaS packages do not permit you to develop specific modules to your needs. On the contrary, they offer a service at a set price based on standard software modules that contain few migration risks. SaaS suppliers are limited generally to the modules certified and validated by the original author and project manager, Tiny.

Here are the main advantages of an OpenERP SaaS solution:

  • прекрасный возврат затрат на внедрение (затраты на внедрение: 0, стоимость лицензий: 0),

  • затраты, которые контролируются, и не содержат сюрпризов (предложение включает обслуживание, частоту миграций и поддержку),

  • решение «под ключ», устанавливаемое менее чем за 24 часа,

  • комплекты адаптированы и предварительно настроены для различных областей активности,

  • очень устойчивая архитектура, с гарантией постоянного и непрерывного доступа, доступная из любого места.

Таким образом, данное расположение рекомендовано для малых компаний, с небольшим количеством сотрудников -- до 15.

Hosting by a Supplier

At first sight, a hosted OpenERP system appears similar to SaaS: it provides OpenERP from a remote installation through a web browser. But in general, the similarities stop there.

To compare it with an SaaS package, you should check if the hosting offer properly includes the following elements:

  • аппаратное обеспечение сервера,

  • хостинг,

  • обслуживание,

  • будущие миграции,

  • резервное копирование,

  • избыточность сервера,

  • поддержку по телефону и электронной почте,

  • частые обновления модулей.

Также войдите в курс следующих элементов:

  • the version of OpenERP proposed,

  • затраты на внедрение (настройка, загрузка данных, обучение),

  • the cost of configuration (if it is proposed),

  • техника и используемые процедуры, используемые для обеспечения безопасности вашей базы данных,

  • техника и процедуры для предотвращения сбоев системы,

  • техника и процедуры восстановления после сбоев системы,

  • ограничения по количеству пользователей, количеству одновременно подключенных пользователей, и размеру базы данных,

  • уровни поддержки и их стоимость,

  • the procedure used to update OpenERP (to fault-fixed versions)

  • the procedure adopted for OpenERP upgrades (to versions that have both fault fixes and new functionality).

Calling such suppliers can be a good solution if you are willing to entrust all the technical specifications for the functioning of OpenERP to them, especially if you need to use customized or extension modules that are not in the stable version released by Tiny.

Внутренняя установка

Large and medium-large companies typically install OpenERP using their own internal company resources. They usually prefer to have their own IT service in charge of maintenance.

Such companies can do the implementation work themselves internally, or turn to an OpenERP partner who will do the ERP implementation work or assist them with it. Generally, companies prefer to adopt an intermediate solution which consists of:

  1. Turning the initial implementation over to a partner to limit the risks and delays of integration. That enables them to be managed by experts and obtain a high quality configuration.

  2. Taking charge of the simple needs for themselves once the software has been implemented. It is quite a lot more convenient for them to be able to modify the database tables, forms, templates and workflows internally than routinely depend on a supplier.

An internal installation will probably prove more costly than a SaaS package or hosted service. Even if you put yourself in charge of it all, you will take quite a bit of time learning how to manage the implementation unless the team already has an experience of OpenERP. This represents a significant risk.

However, an internal implementation can be particularly interesting when:

  • вы хотите хранить ваши данные внутри компании,

  • вы планируете модифицировать программное обеспечение,

  • вам требуется специфический набор модулей,

  • you would like a very fast response time,

  • вы хотите, чтобы программное обеспечение было бы доступно даже при отсутствии соединения с Интернет.

Перечисленные факторы и доступ к необходимым для выполнения работ по внедрению и последующего обслуживания ресурсам являются факторами, почему большие и средние компании обычно хотят произвести внедрение самостоятельно, как минимум частично самостоятельно.

Процедура развертывания

The deployment of a version of OpenERP is quite simple when your server has been configured in your production environment. The security of data will then be a key element.

When you have installed the server, you should create at least two databases:

  • тестовая база данных или база для разработки, в которой пользователи могут тестировать систему и знакомиться с ней,

  • a production database, which will be the one used by the company in daily use.


Version Numbering

OpenERP uses a version numbering model that comprises 3 numbers A.B.C (for example 4.2.2 or 5.0.0) where changes in the number A signify a major functional change, changes to number B signify an update that includes a batch of fault fixes and some new functionality, and the number C generally refers to some limited updates or fixes to the existing functionality.

The number B is special: if it is an odd number, (for example 4.3.2 or 5.1.0) it is for a development version which is not designed for a production environment. The even numbers are for stable versions.

If you have prepared a data module for OpenERP (that is a module that consists just of data, not altered functionality), you should test it in your development version and check that it does not require any more manual adjustments. If the import runs correctly, it shows that you are ready to load your data in the production database.

You can use the OpenERP database backup procedure at different stages of configuration (see Установка и первоначальная настройка). Then, if you have made a false step that you cannot recover from, you can always return to a prior state.

Since your data describes much of your company's value, take particular care both when you need to transfer it (in backups and across your network) and when you are managing the super-administrator password. Make sure that the connection between a PC client and the two servers is correctly secured. You can configure OpenERP to use the HTTPS protocol, which provides security for data transfer



Протокол HTTPS (Secured Hyper Text Transfer Protocol) -- это стандартный протокол HTTP, безопасность которого обеспечивается использованием протоколов безопасности SSL (Secure Socket Layer) или TLS (Transport Layer Security). Это позволяет пользователю подтверждать идентификацию сайта, к которому необходим доступ, используя сертификат аутентификации. Это также гарантирует целостность и конфиденциальность данных, переданных между клиентом и сервером. Это может, необязательно, предоставить высокую безопасность аутентификации клиента с использованием нумерованного сертификата.

Порт по умолчанию для HTTPS -- 443.

You could also use the PostgreSQL database directly to backup and restore data on the server, depending on access rights and the availability of passwords for the server.