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've seen the complete architecture of Open ERP includes the following elements:

  • 数据库服务器,

  • an Open ERP application server,

  • 一个OpenERP客户端的Web服务器,

  • several clients that access the Open ERP server: they can either be web clients if the client-web server is installed, or GTK clients.



Deployment is the process of putting a Open ERP database into a production-ready state, where it can be used by everyone in your business for their daily work. You'd usually configure Open ERP 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 Open ERP in your company, several options are available to you:

  • an 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 Open ERP partner,

  • hosting by a server supplier on which Open ERP 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's also known as On-Demand.

It's 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 don't 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 Open ERP SaaS solution:

  • an unbeatable return on investment (cost of implementation: 0, cost of licenses: 0),

  • costs that are controlled and without surprises (the offer includes maintenance, frequent migrations and support),

  • 整体解决方案,在安装後不到二十四小时內,

  • 安裝包适应和预先设定的不同部门的活动,

  • a very robust architecture guaranteed to have constant and permanent access, reachable from anywhere.

So this server is recommended for small companies with fewer than about fifteen employees.

Hosting by a supplier

At first sight a hosted Open ERP system appears similar to SaaS: it provides Open ERP 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:

  • 服务器硬件,

  • 主机,

  • 维护,

  • 未来的迁移,

  • 备份,

  • 服务器冗余,

  • 电话支持和Email支持,

  • 频繁更新的模块。


  • the version of Open ERP proposed,

  • 实施成本(配置,导入数据,培训),

  • the cost of configuration (if it's proposed),

  • 该技术用于保护您的数据库程序,

  • 为防止系统因技术和程序故障,

  • 用于恢复故障系统的技术和程序,

  • 在用户数量上的限制,同时使用的用户数,以及数据库的大小,

  • 支持及其费用水平,

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

  • the procedure adopted for Open ERP 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 Open ERP to them, especially if you need to use customized or extension modules that aren't in the stable version released by Tiny.


Large and medium-large companies typically install Open ERP 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 Open ERP 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. Turn the initial implementation over to a partner to limit the risks and delays of integration. That enables them to be managed by experts and to obtain a high quality configuration.

  2. Take charge of the simple needs for themselves once the software has been implemented. It's 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 an SaaS package or hosted service. Even if you put yourself in charge of it all, you'll take quite a bit of time learning how to manage the implementation unless the team already has experience of Open ERP. This represents a significant risk.

However, an internal implementation can be particularly interesting where:

  • 你想保存你的数据到你公司去,

  • 你想改动你写的软件,

  • 你想拿到一个特定的模块包,

  • you'd like a very fast response time,

  • 你希望软件即使你未连上Internet互联网依然都可以使用。

These factors, and access to the resources needed to handle an implementation and the subsequent maintenance, are the reasons that large and medium-large companies usually do it for themselves, at least partly.


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

When you've 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

Open ERP 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's an odd number, (for example 4.3.2 or 5.1.0) it's for a development version which isn't designed for a production environment. The even numbers are for stable versions.

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

You can use the Open ERP database backup procedure at different stages of configuration (see 安装与初始配置). Then if you've made a false step that you can't 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're managing the super-administrator password. Make sure that the connection between a PC client and the two servers is correctly secured. You can configure Open ERP to use the HTTPS protocol, which provides security for data transfer



The HTTPS protocol (Secured Hyper Text Transfer Protocol) is the standard HTTP protocol secured by using the SSL (Secure Socket Layer) or TLS (Transport Layer Security) security protocols. It allows a user to verify her identify to the site to which she wants access, using a certificate of authentication. It also guarantees the integrity and confidentiality of the data sent between the user and the server. It can, optionally, provide highly secure client authentication by using a numbered certificate.

默认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 serve.