2
.. i18n: The installation of Open ERP
3
.. i18n: ============================
5
The installation of Open ERP
6
============================
8
.. i18n: Whether you're from a small company investigating how Open ERP works, or on the IT staff of a
9
.. i18n: larger organization and have been asked to assess Open ERP's capabilities, your first requirement
10
.. i18n: is to install it or to find a working installation.
12
Whether you're from a small company investigating how Open ERP works, or on the IT staff of a
13
larger organization and have been asked to assess Open ERP's capabilities, your first requirement
14
is to install it or to find a working installation.
16
.. i18n: The table below summarizes the various installation methods that will be described in the following
19
The table below summarizes the various installation methods that will be described in the following
22
.. i18n: .. csv-table:: Comparison of the different methods of installation on Windows or Linux
23
.. i18n: :header: "Method","Average Time","Level of Complexity","Notes"
24
.. i18n: :widths: 20,15,15,30
26
.. i18n: "All-in-one Windows Installer","A few minutes","Simple","Very useful for quick evaluations because it installs all of the components pre-configured on one computer (using the GTK client)."
27
.. i18n: "Independent installation on Windows","Half an hour","Medium","Enables you to install the components on different computers. Can be put into production use."
28
.. i18n: "Ubuntu Linux packages","A few minutes","Simple","Simple and quick but the Ubuntu packages aren't always up to date."
29
.. i18n: "From source, for all Linux systems","More than half an hour","Medium to slightly difficult","This is the method recommended for production environments because it's easy to keep it up to date."
31
.. csv-table:: Comparison of the different methods of installation on Windows or Linux
32
:header: "Method","Average Time","Level of Complexity","Notes"
35
"All-in-one Windows Installer","A few minutes","Simple","Very useful for quick evaluations because it installs all of the components pre-configured on one computer (using the GTK client)."
36
"Independent installation on Windows","Half an hour","Medium","Enables you to install the components on different computers. Can be put into production use."
37
"Ubuntu Linux packages","A few minutes","Simple","Simple and quick but the Ubuntu packages aren't always up to date."
38
"From source, for all Linux systems","More than half an hour","Medium to slightly difficult","This is the method recommended for production environments because it's easy to keep it up to date."
40
.. i18n: Each time a new release of Open ERP is made, Tiny supplies a complete Windows auto-installer for
41
.. i18n: it. This contains all of the components you need – the PostgreSQL database server, the Open ERP
42
.. i18n: application server and the GTK application client.
44
Each time a new release of Open ERP is made, Tiny supplies a complete Windows auto-installer for
45
it. This contains all of the components you need – the PostgreSQL database server, the Open ERP
46
application server and the GTK application client.
48
.. i18n: This auto-installer enables you to install the whole system in just a few mouse-clicks. The initial
49
.. i18n: configuration is set up during installation, making it possible to start using it very quickly as
50
.. i18n: long as you don't want to change the underlying code. It's aimed at the installation of everything
51
.. i18n: on a single PC, but you can later connect GTK clients from other PCs, Macs and Linux boxes to it as
54
This auto-installer enables you to install the whole system in just a few mouse-clicks. The initial
55
configuration is set up during installation, making it possible to start using it very quickly as
56
long as you don't want to change the underlying code. It's aimed at the installation of everything
57
on a single PC, but you can later connect GTK clients from other PCs, Macs and Linux boxes to it as
60
.. i18n: The first step is to download the Open ERP installer. At this stage you must choose which version
61
.. i18n: to install – the stable version or the development version. If you're planning to put it straight
62
.. i18n: into production you're strongly advised to choose the stable version.
64
The first step is to download the Open ERP installer. At this stage you must choose which version
65
to install – the stable version or the development version. If you're planning to put it straight
66
into production you're strongly advised to choose the stable version.
69
.. i18n: single: stable versions
72
single: stable versions
74
.. i18n: .. note:: Stable versions and development versions
76
.. i18n: Open ERP development proceeds on two parallel tracks: stable versions and development versions.
78
.. i18n: New functionality is integrated into the development branch. This branch is more advanced than the
79
.. i18n: stable branch, but it can contain undiscovered and unfixed faults. A new development release is
80
.. i18n: made every month or so, and Tiny have made the code repository available so you can download the
81
.. i18n: very latest revisions if you want.
83
.. i18n: The stable branch is designed for production environments. Releases of new functionality there are
84
.. i18n: made only about once a year after a long period of testing and validation. Only fault fixes are
85
.. i18n: released through the year on the stable branch.
87
.. note:: Stable versions and development versions
89
Open ERP development proceeds on two parallel tracks: stable versions and development versions.
91
New functionality is integrated into the development branch. This branch is more advanced than the
92
stable branch, but it can contain undiscovered and unfixed faults. A new development release is
93
made every month or so, and Tiny have made the code repository available so you can download the
94
very latest revisions if you want.
96
The stable branch is designed for production environments. Releases of new functionality there are
97
made only about once a year after a long period of testing and validation. Only fault fixes are
98
released through the year on the stable branch.
101
.. i18n: single: installation; Windows (all-in-one)
104
single: installation; Windows (all-in-one)
106
.. i18n: To download the version of Open ERP for Windows, follow these steps:
108
To download the version of Open ERP for Windows, follow these steps:
110
.. i18n: #. Navigate to the site http://openerp.com.
112
.. i18n: #. Click :menuselection:`Downloads` on the menu at the left then, under :guilabel:`Windows Installers`,
113
.. i18n: :menuselection:`All in One`.
115
.. i18n: #. This brings up the demonstration version Windows installer,
116
.. i18n: currently :program:`openerp-allinone-setup-5.0.0-3`.
118
.. i18n: #. Save the file on your PC - it's quite a substantial size because it downloads everything including
119
.. i18n: the PostgreSQL database system, so will take some time.
121
#. Navigate to the site http://openerp.com.
123
#. Click :menuselection:`Downloads` on the menu at the left then, under :guilabel:`Windows Installers`,
124
:menuselection:`All in One`.
126
#. This brings up the demonstration version Windows installer,
127
currently :program:`openerp-allinone-setup-5.0.0-3`.
129
#. Save the file on your PC - it's quite a substantial size because it downloads everything including
130
the PostgreSQL database system, so will take some time.
133
.. i18n: single: installation; administrator
136
single: installation; administrator
138
.. i18n: To install Open ERP and its database you must be signed in as an Administrator on your PC. Double-
139
.. i18n: click the installer file to install it and accept the default parameters on each dialog box as you go.
141
To install Open ERP and its database you must be signed in as an Administrator on your PC. Double-
142
click the installer file to install it and accept the default parameters on each dialog box as you go.
144
.. i18n: If you had previously tried to install the all-in-one version of Open ERP, you have to uninstall
145
.. i18n: that first because various elements of a previous installation could interfere with your new installation.
146
.. i18n: Make sure that all Tiny ERP, Open ERP and PostgreSQL applications are removed:
147
.. i18n: you're likely to have to restart your PC to finish removing all traces of them.
149
If you had previously tried to install the all-in-one version of Open ERP, you have to uninstall
150
that first because various elements of a previous installation could interfere with your new installation.
151
Make sure that all Tiny ERP, Open ERP and PostgreSQL applications are removed:
152
you're likely to have to restart your PC to finish removing all traces of them.
154
.. i18n: The Open ERP client can be opened, ready to use the Open ERP system, once you have completed
155
.. i18n: the all--in-one installation. The next step consists
156
.. i18n: of setting up the database, and is covered in the final section of this chapter :ref:`sect-creatingdb`.
158
The Open ERP client can be opened, ready to use the Open ERP system, once you have completed
159
the all--in-one installation. The next step consists
160
of setting up the database, and is covered in the final section of this chapter :ref:`sect-creatingdb`.
163
.. i18n: single: installation; Windows (independent)
166
single: installation; Windows (independent)
168
.. i18n: Independent installation on Windows
169
.. i18n: -----------------------------------
171
Independent installation on Windows
172
-----------------------------------
174
.. i18n: System administrators can have very good reasons for wanting to install the various components of a
175
.. i18n: Windows installation separately. For example, your company may not support the version of PostgreSQL
176
.. i18n: or Python that's installed automatically, or you may already have PostgreSQL installed on the server
177
.. i18n: you're using, or you may want to install the database server, application server and web server on
178
.. i18n: separate hardware units.
180
System administrators can have very good reasons for wanting to install the various components of a
181
Windows installation separately. For example, your company may not support the version of PostgreSQL
182
or Python that's installed automatically, or you may already have PostgreSQL installed on the server
183
you're using, or you may want to install the database server, application server and web server on
184
separate hardware units.
186
.. i18n: For this situation you can get separate installers for the Open ERP server and client from the same
187
.. i18n: location as the all-in-one auto-installer. You'll also have to download and install a suitable
188
.. i18n: version of PostgreSQL independently.
190
For this situation you can get separate installers for the Open ERP server and client from the same
191
location as the all-in-one auto-installer. You'll also have to download and install a suitable
192
version of PostgreSQL independently.
194
.. i18n: You must install PostgreSQL before the Open ERP server, and you must also set it up with a user
195
.. i18n: and password so that the Open ERP server can connect to it. Tiny's web-based documentation gives
196
.. i18n: full and current details.
198
You must install PostgreSQL before the Open ERP server, and you must also set it up with a user
199
and password so that the Open ERP server can connect to it. Tiny's web-based documentation gives
200
full and current details.
202
.. i18n: Connecting users on other PCs to the Open ERP server
203
.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
205
Connecting users on other PCs to the Open ERP server
206
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
208
.. i18n: To connect other computers to the Open ERP server you must set the server up so that it's
209
.. i18n: visible to the other PCs, and install a GTK client on each of the those PCs:
211
To connect other computers to the Open ERP server you must set the server up so that it's
212
visible to the other PCs, and install a GTK client on each of the those PCs:
214
.. i18n: #. Make your Open ERP server visible to other PCs by opening the Windows Firewall in the Control
215
.. i18n: Panel, then asking the firewall to make an exception of the Open ERP server. In the
216
.. i18n: :guilabel:`Exceptions` tab of Windows Firewall click on :guilabel:`Add a program...` and choose
217
.. i18n: :guilabel:`Open ERP Server` in the list provided. This step enables other computers to see the
218
.. i18n: Open ERP application on this server.
220
.. i18n: #. Install the Open ERP client (:program:`openerp-client-5.X.exe`), which you can download in the
221
.. i18n: same way as you downloaded the other Open ERP software, onto the other PCs.
223
#. Make your Open ERP server visible to other PCs by opening the Windows Firewall in the Control
224
Panel, then asking the firewall to make an exception of the Open ERP server. In the
225
:guilabel:`Exceptions` tab of Windows Firewall click on :guilabel:`Add a program...` and choose
226
:guilabel:`Open ERP Server` in the list provided. This step enables other computers to see the
227
Open ERP application on this server.
229
#. Install the Open ERP client (:program:`openerp-client-5.X.exe`), which you can download in the
230
same way as you downloaded the other Open ERP software, onto the other PCs.
232
.. i18n: .. tip:: Version matching
234
.. i18n: You must make sure that the version of the client matches that of the server. The version number is
235
.. i18n: given as part of the name of the downloaded file. Although it's possible that some different
236
.. i18n: revisions of client and server will function together, there's no certainty about that.
238
.. tip:: Version matching
240
You must make sure that the version of the client matches that of the server. The version number is
241
given as part of the name of the downloaded file. Although it's possible that some different
242
revisions of client and server will function together, there's no certainty about that.
245
.. i18n: single: administrator
248
single: administrator
250
.. i18n: To run the client installer on every other PC you'll need to have administrator rights there. The
251
.. i18n: installation is automated, so you just need to guide it through its different installation steps.
253
To run the client installer on every other PC you'll need to have administrator rights there. The
254
installation is automated, so you just need to guide it through its different installation steps.
256
.. i18n: To test your installation, start by connecting through the Open ERP client on the server machine
257
.. i18n: while you're still logged in as administrator.
259
To test your installation, start by connecting through the Open ERP client on the server machine
260
while you're still logged in as administrator.
262
.. i18n: .. note:: Why sign in as a PC Administrator?
264
.. i18n: You'd not usually be signed on as a PC administrator when you're just running the Open ERP client,
265
.. i18n: but if there have been problems in the installation it's easier to remain as an administrator after
266
.. i18n: the installation so that you can make any necessary fixes than to switch user as you alternate
267
.. i18n: between roles as a tester and a software installer.
269
.. note:: Why sign in as a PC Administrator?
271
You'd not usually be signed on as a PC administrator when you're just running the Open ERP client,
272
but if there have been problems in the installation it's easier to remain as an administrator after
273
the installation so that you can make any necessary fixes than to switch user as you alternate
274
between roles as a tester and a software installer.
276
.. i18n: Start the GTK client on the server through the Windows Start menu there. The main client window
277
.. i18n: appears, identifying the server you're connected to (which is \ ``localhost``\ – your own server
278
.. i18n: PC – by default). If the message :guilabel:`No database found, you must create one` appears then
279
.. i18n: you've **successfully connected** to an Open ERP server containing, as yet, no databases.
281
Start the GTK client on the server through the Windows Start menu there. The main client window
282
appears, identifying the server you're connected to (which is \ ``localhost``\ – your own server
283
PC – by default). If the message :guilabel:`No database found, you must create one` appears then
284
you've **successfully connected** to an Open ERP server containing, as yet, no databases.
286
.. i18n: .. figure:: images/new_login_dlg.png
287
.. i18n: :align: center
290
.. i18n: *Dialog box on connecting a GTK client to a new Open ERP server*
292
.. figure:: images/new_login_dlg.png
296
*Dialog box on connecting a GTK client to a new Open ERP server*
299
.. i18n: single: protocol; XML-RPC
300
.. i18n: single: protocol; NET-RPC
301
.. i18n: single: XML-RPC
302
.. i18n: single: NET-RPC
305
single: protocol; XML-RPC
306
single: protocol; NET-RPC
310
.. i18n: .. note:: Connection modes
312
.. i18n: In its default configuration at the time of writing,
313
.. i18n: the Open ERP client connects to port 8069 on the server using the
314
.. i18n: XML-RPC protocol (from Linux) or port 8070 using the NET-RPC protocol instead (from Windows).
315
.. i18n: You can use either protocol from either operating system.
316
.. i18n: NET-RPC is quite a bit quicker, although you may not notice that on the GTK client in normal use.
317
.. i18n: Open ERP can run XML-RPC, but not NET-RPC, as a secure connection.
319
.. i18n: The all-in-one installer also provides a web server, but this was not yet working at the time
322
.. note:: Connection modes
324
In its default configuration at the time of writing,
325
the Open ERP client connects to port 8069 on the server using the
326
XML-RPC protocol (from Linux) or port 8070 using the NET-RPC protocol instead (from Windows).
327
You can use either protocol from either operating system.
328
NET-RPC is quite a bit quicker, although you may not notice that on the GTK client in normal use.
329
Open ERP can run XML-RPC, but not NET-RPC, as a secure connection.
331
The all-in-one installer also provides a web server, but this was not yet working at the time
334
.. i18n: Resolving errors with a Windows installation
335
.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
337
Resolving errors with a Windows installation
338
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
340
.. i18n: If you can't get Open ERP to work after installing your Windows system you'll find some ideas for
341
.. i18n: resolving this below:
343
If you can't get Open ERP to work after installing your Windows system you'll find some ideas for
344
resolving this below:
346
.. i18n: #. Is the Open ERP application working? Signed in to the server as an administrator, stop and
347
.. i18n: restart the service using :guilabel:`Stop Service` and :guilabel:`Start Service` from the menu
348
.. i18n: :menuselection:`Start --> Programs --> OpenERP Server` .
350
.. i18n: #. Is the Open ERP application server set up correctly? Signed in to the server as
351
.. i18n: Administrator, open the file \ ``openerp-server.conf``\ in \
352
.. i18n: ``C:\Program Files\OpenERP AllInOne``\ and check its content. This file is generated during
353
.. i18n: installation with information derived from the database. If you see something strange it's best to
354
.. i18n: entirely reinstall the server from the demonstration installer rather than try to work out what's
357
#. Is the Open ERP application working? Signed in to the server as an administrator, stop and
358
restart the service using :guilabel:`Stop Service` and :guilabel:`Start Service` from the menu
359
:menuselection:`Start --> Programs --> OpenERP Server` .
361
#. Is the Open ERP application server set up correctly? Signed in to the server as
362
Administrator, open the file \ ``openerp-server.conf``\ in \
363
``C:\Program Files\OpenERP AllInOne``\ and check its content. This file is generated during
364
installation with information derived from the database. If you see something strange it's best to
365
entirely reinstall the server from the demonstration installer rather than try to work out what's
368
.. i18n: .. figure:: images/terp_server_conf.png
369
.. i18n: :align: center
372
.. i18n: *Typical Open ERP configuration file*
374
.. figure:: images/terp_server_conf.png
378
*Typical Open ERP configuration file*
380
.. i18n: #. Is your PostgreSQL server running? Signed in as administrator, select :guilabel:`Stop Service`
381
.. i18n: from the menu :menuselection:`Start --> Programs --> PostgreSQL`. If, after a couple of seconds,
382
.. i18n: you can read :guilabel:`The PostgreSQL4OpenERP service has stopped` then you can be reasonably sure
383
.. i18n: that the database server was working. Restart PostgreSQL.
385
.. i18n: #. Does PostgreSQL work at all? Still in the PostgreSQL menu, start
386
.. i18n: the pgAdmin III application which you can use to explore the database. Double-click on the \
387
.. i18n: ``PostgreSQL4OpenERP``\ connection.
388
.. i18n: You can find the password in the Open ERP server configuration file.
389
.. i18n: If the database server is working
390
.. i18n: you'll be able to see some information about the empty database. If it's not then an error message
391
.. i18n: will appear.
393
.. i18n: #. Are your client programs correctly installed? If your Open ERP GTK clients haven't started then
394
.. i18n: the swiftest approach is to reinstall them.
396
.. i18n: #. Can remote client computers see the server computer at all? Check this by opening a command prompt
397
.. i18n: window (enter \ ``cmd``\ in the window :menuselection:`Start --> Run...` ) and enter \ ``ping
398
.. i18n: <address of server>``\ there (where \ ``<address of server>``\ represents the IP address of the
399
.. i18n: server). The server should respond with a reply.
401
.. i18n: #. Have you changed any of the server's parameters? At this point in the installation the port
402
.. i18n: number of the server must be 8069 using the protocol XML-RPC.
404
.. i18n: #. Is there anything else in the server's history that can help you identify the problem? Open the file
405
.. i18n: \ ``openerp-server.log``\ in \ ``C:\Program Files\OpenERP AllInOne``\
406
.. i18n: (which you can only do when the server is stopped) and scan through the
407
.. i18n: history for ideas. If something looks strange there, contributors to the Open ERP forums can often
408
.. i18n: help identify the reason.
410
#. Is your PostgreSQL server running? Signed in as administrator, select :guilabel:`Stop Service`
411
from the menu :menuselection:`Start --> Programs --> PostgreSQL`. If, after a couple of seconds,
412
you can read :guilabel:`The PostgreSQL4OpenERP service has stopped` then you can be reasonably sure
413
that the database server was working. Restart PostgreSQL.
415
#. Does PostgreSQL work at all? Still in the PostgreSQL menu, start
416
the pgAdmin III application which you can use to explore the database. Double-click on the \
417
``PostgreSQL4OpenERP``\ connection.
418
You can find the password in the Open ERP server configuration file.
419
If the database server is working
420
you'll be able to see some information about the empty database. If it's not then an error message
423
#. Are your client programs correctly installed? If your Open ERP GTK clients haven't started then
424
the swiftest approach is to reinstall them.
426
#. Can remote client computers see the server computer at all? Check this by opening a command prompt
427
window (enter \ ``cmd``\ in the window :menuselection:`Start --> Run...` ) and enter \ ``ping
428
<address of server>``\ there (where \ ``<address of server>``\ represents the IP address of the
429
server). The server should respond with a reply.
431
#. Have you changed any of the server's parameters? At this point in the installation the port
432
number of the server must be 8069 using the protocol XML-RPC.
434
#. Is there anything else in the server's history that can help you identify the problem? Open the file
435
\ ``openerp-server.log``\ in \ ``C:\Program Files\OpenERP AllInOne``\
436
(which you can only do when the server is stopped) and scan through the
437
history for ideas. If something looks strange there, contributors to the Open ERP forums can often
438
help identify the reason.
441
.. i18n: single: installation; Linux (Ubuntu)
444
single: installation; Linux (Ubuntu)
446
.. i18n: Installation on Linux (Ubuntu)
447
.. i18n: ------------------------------
449
Installation on Linux (Ubuntu)
450
------------------------------
452
.. i18n: This section guides you through installing the Open ERP server and client on Ubuntu, one of the
453
.. i18n: most popular Linux distributions. It assumes that you're using a recent release of Desktop Ubuntu
454
.. i18n: with its graphical user interface on a desktop or laptop PC.
456
This section guides you through installing the Open ERP server and client on Ubuntu, one of the
457
most popular Linux distributions. It assumes that you're using a recent release of Desktop Ubuntu
458
with its graphical user interface on a desktop or laptop PC.
460
.. i18n: .. note:: Other Linux distributions
462
.. i18n: Installation on other distributions of Linux is fairly similar to installation on Ubuntu. Read this
463
.. i18n: section of the book so that you understand the principles, then use the online documentation and
464
.. i18n: the forums for your specific needs on another distribution.
466
.. note:: Other Linux distributions
468
Installation on other distributions of Linux is fairly similar to installation on Ubuntu. Read this
469
section of the book so that you understand the principles, then use the online documentation and
470
the forums for your specific needs on another distribution.
472
.. i18n: For information about installation on other distributions, visit the documentation section by
473
.. i18n: following :menuselection:`Product --> Documentation` on http://www.openerp.com. Detailed instructions
474
.. i18n: are given there for different distributions and releases, and you should also check if there are
475
.. i18n: more up to date instructions for the Ubuntu distribution as well.
477
For information about installation on other distributions, visit the documentation section by
478
following :menuselection:`Product --> Documentation` on http://www.openerp.com. Detailed instructions
479
are given there for different distributions and releases, and you should also check if there are
480
more up to date instructions for the Ubuntu distribution as well.
482
.. i18n: Installation of Open ERP from packages
483
.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
485
Installation of Open ERP from packages
486
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
488
.. i18n: At the time of writing this book, Ubuntu hadn't yet published packages for Open ERP, so this
489
.. i18n: section describes the installation of version 4.2 of Tiny ERP. This is very similar to Open ERP and
490
.. i18n: so can be used to test the software.
492
At the time of writing this book, Ubuntu hadn't yet published packages for Open ERP, so this
493
section describes the installation of version 4.2 of Tiny ERP. This is very similar to Open ERP and
494
so can be used to test the software.
496
.. i18n: Here's a summary of the procedure:
498
Here's a summary of the procedure:
500
.. i18n: #. Start Synaptic Package Manager, and enter your root password as required.
502
.. i18n: #. Check that the repositories \ ``main``\ \ ``universe``\ and \ ``restricted``\ are enabled.
504
.. i18n: #. Search for a recent version of PostgreSQL, for example \ ``postgresql-8.3``\ then select it for
505
.. i18n: installation along with its dependencies.
507
.. i18n: #. Search for \ ``tinyerp``\ then select \ ``tinyerp-client``\ and \ ``tinyerp-server``\ for
508
.. i18n: installation along with their dependencies. Click :guilabel:`Update Now` to install it all.
510
.. i18n: #. Close Synaptic Package Manager.
512
#. Start Synaptic Package Manager, and enter your root password as required.
514
#. Check that the repositories \ ``main``\ \ ``universe``\ and \ ``restricted``\ are enabled.
516
#. Search for a recent version of PostgreSQL, for example \ ``postgresql-8.3``\ then select it for
517
installation along with its dependencies.
519
#. Search for \ ``tinyerp``\ then select \ ``tinyerp-client``\ and \ ``tinyerp-server``\ for
520
installation along with their dependencies. Click :guilabel:`Update Now` to install it all.
522
#. Close Synaptic Package Manager.
524
.. i18n: Installing PostgreSQL results in a database server that runs and restarts automatically when the PC
525
.. i18n: is turned on. If all goes as it should with the tinyerp-server package then tinyerp-server will also
526
.. i18n: install, and restart automatically when the PC is switched on.
528
Installing PostgreSQL results in a database server that runs and restarts automatically when the PC
529
is turned on. If all goes as it should with the tinyerp-server package then tinyerp-server will also
530
install, and restart automatically when the PC is switched on.
532
.. i18n: Start the Tiny/Open ERP GTK client by clicking its icon in the :menuselection:`Applications` menu,
533
.. i18n: or by opening a terminal window and typing \ ``tinyerp-client``\ . The Open ERP login dialog box
534
.. i18n: should open and show the message :guilabel:`No database found you must create one!`.
536
Start the Tiny/Open ERP GTK client by clicking its icon in the :menuselection:`Applications` menu,
537
or by opening a terminal window and typing \ ``tinyerp-client``\ . The Open ERP login dialog box
538
should open and show the message :guilabel:`No database found you must create one!`.
540
.. i18n: Although this installation method is simple and therefore an attractive option, it's better to
541
.. i18n: install Open ERP using a version downloaded from http://openerp.com. The downloaded revision is
542
.. i18n: likely to be far more up to date than that available from a Linux distribution.
544
Although this installation method is simple and therefore an attractive option, it's better to
545
install Open ERP using a version downloaded from http://openerp.com. The downloaded revision is
546
likely to be far more up to date than that available from a Linux distribution.
548
.. i18n: .. note:: Package versions
550
.. i18n: Maintaining packages is a process of development, testing and publication that takes time. The
551
.. i18n: releases in Open ERP (or Tiny ERP) packages are therefore not always the latest available. Check
552
.. i18n: the version number from the information on the website before installing a package. If only the
553
.. i18n: third digit group differs (for example 5.0.1 instead of 5.0.2) then you may decide to install it because
554
.. i18n: the differences may be minor – fault fixes rather than functionality changes between the package
555
.. i18n: and the latest version.
557
.. note:: Package versions
559
Maintaining packages is a process of development, testing and publication that takes time. The
560
releases in Open ERP (or Tiny ERP) packages are therefore not always the latest available. Check
561
the version number from the information on the website before installing a package. If only the
562
third digit group differs (for example 5.0.1 instead of 5.0.2) then you may decide to install it because
563
the differences may be minor – fault fixes rather than functionality changes between the package
564
and the latest version.
566
.. i18n: Manual installation of the Open ERP server
567
.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
569
Manual installation of the Open ERP server
570
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
572
.. i18n: In this section you'll see how to install Open ERP by downloading it from the site
573
.. i18n: http://openerp.com, and how to install the libraries and packages that Open ERP depends on, onto a
574
.. i18n: desktop version of Ubuntu. Here's a summary of the procedure:
576
In this section you'll see how to install Open ERP by downloading it from the site
577
http://openerp.com, and how to install the libraries and packages that Open ERP depends on, onto a
578
desktop version of Ubuntu. Here's a summary of the procedure:
580
.. i18n: #. Navigate to the page http://openerp.com with your web browser,
582
.. i18n: #. Click :menuselection:`Downloads` on the left menu,
584
.. i18n: #. Download the client and server files from the *Sources (Linux)* section into your home directory
585
.. i18n: (or some other location if you've defined a different download area).
587
#. Navigate to the page http://openerp.com with your web browser,
589
#. Click :menuselection:`Downloads` on the left menu,
591
#. Download the client and server files from the *Sources (Linux)* section into your home directory
592
(or some other location if you've defined a different download area).
594
.. i18n: To download the PostgreSQL database and all of the other dependencies for Open ERP from packages:
596
To download the PostgreSQL database and all of the other dependencies for Open ERP from packages:
598
.. i18n: #. Start Synaptic Package Manager, and enter the root password as required.
600
.. i18n: #. Check that the repositories \ ``main``\ \ ``universe``\ and \ ``restricted``\ are enabled.
602
.. i18n: #. Search for a recent version of PostgreSQL (such as \ ``postgresql-8.3``\ then select it for
603
.. i18n: installation along with its dependencies.
605
.. i18n: #. Select all of Open ERP's dependences, an up-to-date list of which should be
606
.. i18n: found in the installation documents on Tiny's website,
607
.. i18n: then click :guilabel:`Update Now` to install them.
609
#. Start Synaptic Package Manager, and enter the root password as required.
611
#. Check that the repositories \ ``main``\ \ ``universe``\ and \ ``restricted``\ are enabled.
613
#. Search for a recent version of PostgreSQL (such as \ ``postgresql-8.3``\ then select it for
614
installation along with its dependencies.
616
#. Select all of Open ERP's dependences, an up-to-date list of which should be
617
found in the installation documents on Tiny's website,
618
then click :guilabel:`Update Now` to install them.
621
.. i18n: single: Python
626
.. i18n: .. note:: Python programming language
628
.. i18n: Python is the programming language that's been used to develop Open ERP. It's a dynamic, non-typed
629
.. i18n: language that is object-oriented, procedural and functional. It comes with numerous libraries that
630
.. i18n: provide interfaces to other languages and has the great advantage that it can be learnt in only a
631
.. i18n: few days. It's the language of choice for large parts of NASA's, Google's and many other
632
.. i18n: enterprises' code.
634
.. i18n: For more information on Python, explore http://www.python.org.
636
.. note:: Python programming language
638
Python is the programming language that's been used to develop Open ERP. It's a dynamic, non-typed
639
language that is object-oriented, procedural and functional. It comes with numerous libraries that
640
provide interfaces to other languages and has the great advantage that it can be learnt in only a
641
few days. It's the language of choice for large parts of NASA's, Google's and many other
644
For more information on Python, explore http://www.python.org.
646
.. i18n: Once all these dependencies and the database are installed, install the server itself using the
647
.. i18n: instructions on the website.
649
Once all these dependencies and the database are installed, install the server itself using the
650
instructions on the website.
652
.. i18n: Open a terminal window to start the server with the command \ ``sudo -i -u postgres
653
.. i18n: openerp-server``\ , which should result in a series of log messages as the server starts up. If the server
654
.. i18n: is correctly installed, the message :guilabel:`[...] waiting for connections...` should show within 30
655
.. i18n: seconds or so, which indicates that the server is waiting for a client to connect to it.
657
Open a terminal window to start the server with the command \ ``sudo -i -u postgres
658
openerp-server``\ , which should result in a series of log messages as the server starts up. If the server
659
is correctly installed, the message :guilabel:`[...] waiting for connections...` should show within 30
660
seconds or so, which indicates that the server is waiting for a client to connect to it.
662
.. i18n: .. figure:: images/terps_startup_log.png
663
.. i18n: :align: center
666
.. i18n: *Open ERP startup log in the console*
668
.. figure:: images/terps_startup_log.png
672
*Open ERP startup log in the console*
675
.. i18n: single: client; GTK
676
.. i18n: single: installation; GTK client
680
single: installation; GTK client
682
.. i18n: Manual installation of Open ERP GTK clients
683
.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
685
Manual installation of Open ERP GTK clients
686
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
688
.. i18n: To install an Open ERP GTK client, follow the steps outline on the website installation document for
689
.. i18n: your particular operating system.
691
To install an Open ERP GTK client, follow the steps outline on the website installation document for
692
your particular operating system.
694
.. i18n: .. tip:: Survey: Don't Cancel!
696
.. i18n: When you start the GTK client for the first time, a dialog box appears asking for various details
697
.. i18n: that are intended to help the Tiny company assess the prospective user base for its software.
699
.. i18n: If you click the :guilabel:`Cancel` button, the window goes away – but Open ERP will ask the
700
.. i18n: same questions again next time you start the client. It's best to click :guilabel:`OK`, even if you
701
.. i18n: choose to enter no data, to prevent that window reappearing next time.
703
.. tip:: Survey: Don't Cancel!
705
When you start the GTK client for the first time, a dialog box appears asking for various details
706
that are intended to help the Tiny company assess the prospective user base for its software.
708
If you click the :guilabel:`Cancel` button, the window goes away – but Open ERP will ask the
709
same questions again next time you start the client. It's best to click :guilabel:`OK`, even if you
710
choose to enter no data, to prevent that window reappearing next time.
712
.. i18n: .. figure:: images/terp_client_startup.png
713
.. i18n: :align: center
716
.. i18n: *Open ERP client at startup*
718
.. figure:: images/terp_client_startup.png
722
*Open ERP client at startup*
724
.. i18n: Open a terminal window to start the client using the command openerp-client. When you start the
725
.. i18n: client on the same Linux PC as the server you'll find that the default connection parameters will
726
.. i18n: just work without needing any change. The message :guilabel:`No database found, you must create
727
.. i18n: one!` shows you that the connection to the server has been successful and you need to create a
728
.. i18n: database on the server.
730
Open a terminal window to start the client using the command openerp-client. When you start the
731
client on the same Linux PC as the server you'll find that the default connection parameters will
732
just work without needing any change. The message :guilabel:`No database found, you must create
733
one!` shows you that the connection to the server has been successful and you need to create a
734
database on the server.
736
.. i18n: Creating the database
737
.. i18n: ^^^^^^^^^^^^^^^^^^^^^
739
Creating the database
740
^^^^^^^^^^^^^^^^^^^^^
742
.. i18n: You can connect other GTK clients over the network to your Linux server. Before you leave your
743
.. i18n: server, make sure you know its network address – either by its name (such as \
744
.. i18n: ``mycomputer.mycompany.net``\ ) or its IP address (such as \ ``192.168.0.123``\ ).
746
You can connect other GTK clients over the network to your Linux server. Before you leave your
747
server, make sure you know its network address – either by its name (such as \
748
``mycomputer.mycompany.net``\ ) or its IP address (such as \ ``192.168.0.123``\ ).
751
.. i18n: single: port (network)
754
single: port (network)
756
.. i18n: .. note:: Different networks
758
.. i18n: Communications between an Open ERP client and server are based on standard protocols. You can
759
.. i18n: connect Windows clients to a Linux server, or vice versa, without problems. It's the same for Mac
760
.. i18n: versions of Open ERP – you can connect Windows and Linux clients and servers to them.
762
.. note:: Different networks
764
Communications between an Open ERP client and server are based on standard protocols. You can
765
connect Windows clients to a Linux server, or vice versa, without problems. It's the same for Mac
766
versions of Open ERP – you can connect Windows and Linux clients and servers to them.
768
.. i18n: To install an Open ERP client on a computer under Linux, repeat the procedure shown earlier in this
769
.. i18n: section. You can connect different clients to the Open ERP server by modifying the connection
770
.. i18n: parameters on each client. To do that, click the :guilabel:`Change` button on the connection dialog
771
.. i18n: and set the following field as needed:
773
To install an Open ERP client on a computer under Linux, repeat the procedure shown earlier in this
774
section. You can connect different clients to the Open ERP server by modifying the connection
775
parameters on each client. To do that, click the :guilabel:`Change` button on the connection dialog
776
and set the following field as needed:
778
.. i18n: * :guilabel:`Server` : \ ``name``\ or \ ``IP address``\ of the server over the network,
780
.. i18n: * :guilabel:`Port` : the port, whose default is \ ``8069``\ or \ ``8070``\ ,
782
.. i18n: * :guilabel:`Connection protocol` : \ ``XML-RPC``\ or \ ``NET-RPC``\ .
784
* :guilabel:`Server` : \ ``name``\ or \ ``IP address``\ of the server over the network,
786
* :guilabel:`Port` : the port, whose default is \ ``8069``\ or \ ``8070``\ ,
788
* :guilabel:`Connection protocol` : \ ``XML-RPC``\ or \ ``NET-RPC``\ .
790
.. i18n: .. figure:: images/terp_client_server.png
791
.. i18n: :align: center
794
.. i18n: *Dialog box for defining connection parameters to the server*
796
.. figure:: images/terp_client_server.png
800
*Dialog box for defining connection parameters to the server*
802
.. i18n: It's possible to connect the server to the client using a secure protocol to prevent other network
803
.. i18n: users from listening in, but the installation described here is for direct unencrypted connection.
805
It's possible to connect the server to the client using a secure protocol to prevent other network
806
users from listening in, but the installation described here is for direct unencrypted connection.
808
.. i18n: If your Linux server is protected by a firewall you'll have to provide access to port
809
.. i18n: \ ``8069``\ or \ ``8070``\ for users on other computers with Open ERP GTK clients.
811
If your Linux server is protected by a firewall you'll have to provide access to port
812
\ ``8069``\ or \ ``8070``\ for users on other computers with Open ERP GTK clients.
815
.. i18n: single: installation; eTiny web server
816
.. i18n: single: installation; Open ERP client-web server
819
single: installation; eTiny web server
820
single: installation; Open ERP client-web server
822
.. i18n: Installation of an Open ERP web server
823
.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
825
Installation of an Open ERP web server
826
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
828
.. i18n: Just as you installed a GTK client on a Linux server, you can also install the Open ERP client-web
830
.. i18n: You can install it from sources after installing its dependencies from packages as you did
831
.. i18n: with the Open ERP server,
832
.. i18n: but Tiny have provided a simpler way to do this for eTiny – using a system known as ez_setup.
834
Just as you installed a GTK client on a Linux server, you can also install the Open ERP client-web
836
You can install it from sources after installing its dependencies from packages as you did
837
with the Open ERP server,
838
but Tiny have provided a simpler way to do this for eTiny – using a system known as ez_setup.
840
.. i18n: Before proceeding, confirm that your Open ERP installation is functioning correctly with a GTK
842
.. i18n: If it's not you'll need to go back now and fix it, because you need to be able to use it fully for
843
.. i18n: the next stages.
845
Before proceeding, confirm that your Open ERP installation is functioning correctly with a GTK
847
If it's not you'll need to go back now and fix it, because you need to be able to use it fully for
850
.. i18n: To install client-web follow the up-to-date instructions in the installation document on the website.
852
To install client-web follow the up-to-date instructions in the installation document on the website.
854
.. i18n: .. note:: Ez tool
856
.. i18n: Ez is the packaging system used by Python. It enables the installation of programs as required just
857
.. i18n: like the packages used by a Linux distribution. The software is downloaded across the network and
858
.. i18n: installed on your computer by ez_install.
860
.. i18n: :program:`ez_setup` is a small program that installs ez_install automatically.
864
Ez is the packaging system used by Python. It enables the installation of programs as required just
865
like the packages used by a Linux distribution. The software is downloaded across the network and
866
installed on your computer by ez_install.
868
:program:`ez_setup` is a small program that installs ez_install automatically.
870
.. i18n: The Open ERP Web server connects to the Open ERP server in the same way as an Open ERP client
871
.. i18n: using the NET-RPC protocol. Its default setup corresponds to that of the Open ERP server
872
.. i18n: you've just installed, so should connect directly at startup.
874
The Open ERP Web server connects to the Open ERP server in the same way as an Open ERP client
875
using the NET-RPC protocol. Its default setup corresponds to that of the Open ERP server
876
you've just installed, so should connect directly at startup.
878
.. i18n: #. At the same console as you've just been using, go to the Openerp web directory by typing
879
.. i18n: :command:`cd openerp-web-5.X`.
881
.. i18n: #. At a terminal window type :command:`start-openerp-web` to start the Open ERP Web server.
883
#. At the same console as you've just been using, go to the Openerp web directory by typing
884
:command:`cd openerp-web-5.X`.
886
#. At a terminal window type :command:`start-openerp-web` to start the Open ERP Web server.
888
.. i18n: .. _fig-webwel:
890
.. i18n: .. figure:: images/web_welcome.png
892
.. i18n: :align: center
894
.. i18n: *Open ERP web client at startup*
896
.. i18n: You can verify the installation by opening a web browser on the server and navigating to
897
.. i18n: http://localhost:8080 to connect to eTiny as shown in the figure :ref:`fig-webwel`.
898
.. i18n: You can also test this from
899
.. i18n: another computer connected to the same network if you know the name or IP address of the server over
900
.. i18n: the network – your browser should be set to http://<server_address>:8080 for this.
904
.. figure:: images/web_welcome.png
908
*Open ERP web client at startup*
910
You can verify the installation by opening a web browser on the server and navigating to
911
http://localhost:8080 to connect to eTiny as shown in the figure :ref:`fig-webwel`.
912
You can also test this from
913
another computer connected to the same network if you know the name or IP address of the server over
914
the network – your browser should be set to http://<server_address>:8080 for this.
916
.. i18n: Verifying your Linux installation
917
.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
919
Verifying your Linux installation
920
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
923
.. i18n: single: pgAdmin III
928
.. i18n: You've used default parameters so far during the installation of the various components.
929
.. i18n: If you've had problems, or you just want to set this up differently,
930
.. i18n: the following points provide some indicators about how you can set your installation up.
932
You've used default parameters so far during the installation of the various components.
933
If you've had problems, or you just want to set this up differently,
934
the following points provide some indicators about how you can set your installation up.
936
.. i18n: .. tip:: **psql** and **pgAdmin** tools
938
.. i18n: psql is a simple client, executed from the command line, that's delivered with PostgreSQL. It
939
.. i18n: enables you to execute SQL commands on your Open ERP database.
941
.. i18n: If you prefer a graphical utility to manipulate your database directly you can install pgAdmin III
942
.. i18n: (it is commonly installed automatically with PostgreSQL on a windowing system, but can also be
943
.. i18n: found at \ ``http://www.pgadmin.org/`` \ ).
945
.. tip:: **psql** and **pgAdmin** tools
947
psql is a simple client, executed from the command line, that's delivered with PostgreSQL. It
948
enables you to execute SQL commands on your Open ERP database.
950
If you prefer a graphical utility to manipulate your database directly you can install pgAdmin III
951
(it is commonly installed automatically with PostgreSQL on a windowing system, but can also be
952
found at \ ``http://www.pgadmin.org/`` \ ).
954
.. i18n: #. The PostgreSQL database starts automatically and listens locally on port 5432 as standard: check
955
.. i18n: this by entering \ ``sudo netstat -anpt``\ at a terminal to see if port 5432 is visible there.
957
.. i18n: #. The database system has a default role of \ ``postgres``\ accessible by running under the Linux
958
.. i18n: postgres user: check this by entering \ ``sudo su postgres -c psql``\ at a terminal to see the psql
959
.. i18n: startup message – then type \ ``\q``\ to quit the program.
961
.. i18n: #. Start the Open ERP server from the postgres user (which enables it to access the PostgreSQL
962
.. i18n: database) by typing \ ``sudo su postgres -c tinyerp-server.``\
964
.. i18n: #. If you try to start the Open ERP server from a terminal but get the message ``socket.error: (98,
965
.. i18n: 'Address already in use')`` then you might be trying to start Open ERP while an instance of
966
.. i18n: Open ERP is already running and using the sockets that you've defined (by default 8069 and 8070).
967
.. i18n: If that's a surprise to you then you may be coming up against a previous installation of Open ERP
968
.. i18n: or Tiny ERP, or something else using one or both of those ports.
970
.. i18n: Type \ ``sudo netstat -anpt``\ to
971
.. i18n: discover what is running there, and record the PID. You can check that the PID orresponds to a
972
.. i18n: program you can dispense with by typing \ ``ps aux | grep <PID>``\ and you can then stop the
973
.. i18n: program from running by typing \ ``sudo kill <PID>``\ . You need additional measures to stop it from
974
.. i18n: restarting when you restart the server.
976
.. i18n: #. The Open ERP server has a large number of configuration options. You can see what they are by
977
.. i18n: starting the server with the argument \ ``–help``\ By efault the server configuration is stored
978
.. i18n: in the file \ ``.terp_serverrc``\ in the user's home directory (and for the postgres user that
979
.. i18n: directory is \ ``/var/lib/postgresql``\ .
981
.. i18n: #. You can delete the configuration file to be quite sure that the Open ERP server is starting with
982
.. i18n: just the default options. It is quite common for an upgraded system to behave badly because a new
983
.. i18n: version server cannot work with options from a previous version. When the server starts without a
984
.. i18n: configuration file it will write a new one once there is something non-default to write to it – it
985
.. i18n: will operate using defaults until then.
987
.. i18n: #. To verify that the system works, without becoming entangled in firewall problems, you can start
988
.. i18n: the Open ERP client from a second terminal window on the server computer (which doesn't pass
989
.. i18n: through the firewall). Connect using the XML-RPC protocol on port 8069 or NET-RPC on port 8070. The
990
.. i18n: server can use both ports simultaneously. The window displays the log file when the client is
991
.. i18n: started this way.
993
.. i18n: #. The client setup is stored in the file \ ``.terprc``\ in the user's home directory.
994
.. i18n: Since a GTK client can be started by any user, each user would have their setup defined in a
995
.. i18n: configuration file in their own home directory.
997
.. i18n: #. You can delete the configuration file to be quite sure that the Open ERP client is starting with
998
.. i18n: just the default options. When the client starts without a configuration file it will write a new
999
.. i18n: one for itself.
1001
.. i18n: #. The web server uses the NET-RPC protocol. If a GTK client works but the web server doesn't then the
1002
.. i18n: problem is either with the NET-RPC port or with the web server itself, and not with the Open ERP server.
1004
#. The PostgreSQL database starts automatically and listens locally on port 5432 as standard: check
1005
this by entering \ ``sudo netstat -anpt``\ at a terminal to see if port 5432 is visible there.
1007
#. The database system has a default role of \ ``postgres``\ accessible by running under the Linux
1008
postgres user: check this by entering \ ``sudo su postgres -c psql``\ at a terminal to see the psql
1009
startup message – then type \ ``\q``\ to quit the program.
1011
#. Start the Open ERP server from the postgres user (which enables it to access the PostgreSQL
1012
database) by typing \ ``sudo su postgres -c tinyerp-server.``\
1014
#. If you try to start the Open ERP server from a terminal but get the message ``socket.error: (98,
1015
'Address already in use')`` then you might be trying to start Open ERP while an instance of
1016
Open ERP is already running and using the sockets that you've defined (by default 8069 and 8070).
1017
If that's a surprise to you then you may be coming up against a previous installation of Open ERP
1018
or Tiny ERP, or something else using one or both of those ports.
1020
Type \ ``sudo netstat -anpt``\ to
1021
discover what is running there, and record the PID. You can check that the PID orresponds to a
1022
program you can dispense with by typing \ ``ps aux | grep <PID>``\ and you can then stop the
1023
program from running by typing \ ``sudo kill <PID>``\ . You need additional measures to stop it from
1024
restarting when you restart the server.
1026
#. The Open ERP server has a large number of configuration options. You can see what they are by
1027
starting the server with the argument \ ``–help``\ By efault the server configuration is stored
1028
in the file \ ``.terp_serverrc``\ in the user's home directory (and for the postgres user that
1029
directory is \ ``/var/lib/postgresql``\ .
1031
#. You can delete the configuration file to be quite sure that the Open ERP server is starting with
1032
just the default options. It is quite common for an upgraded system to behave badly because a new
1033
version server cannot work with options from a previous version. When the server starts without a
1034
configuration file it will write a new one once there is something non-default to write to it – it
1035
will operate using defaults until then.
1037
#. To verify that the system works, without becoming entangled in firewall problems, you can start
1038
the Open ERP client from a second terminal window on the server computer (which doesn't pass
1039
through the firewall). Connect using the XML-RPC protocol on port 8069 or NET-RPC on port 8070. The
1040
server can use both ports simultaneously. The window displays the log file when the client is
1043
#. The client setup is stored in the file \ ``.terprc``\ in the user's home directory.
1044
Since a GTK client can be started by any user, each user would have their setup defined in a
1045
configuration file in their own home directory.
1047
#. You can delete the configuration file to be quite sure that the Open ERP client is starting with
1048
just the default options. When the client starts without a configuration file it will write a new
1051
#. The web server uses the NET-RPC protocol. If a GTK client works but the web server doesn't then the
1052
problem is either with the NET-RPC port or with the web server itself, and not with the Open ERP server.
1054
.. i18n: .. hint:: One server for several companies
1056
.. i18n: You can start several Open ERP application servers on one physical computer server by using
1057
.. i18n: different ports. If you have defined multiple database roles in PostgreSQL, each connected through
1058
.. i18n: an Open ERP instance to a different port, you can simultaneously serve many companies from one
1059
.. i18n: physical server at one time.
1061
.. hint:: One server for several companies
1063
You can start several Open ERP application servers on one physical computer server by using
1064
different ports. If you have defined multiple database roles in PostgreSQL, each connected through
1065
an Open ERP instance to a different port, you can simultaneously serve many companies from one
1066
physical server at one time.
1068
.. i18n: .. Copyright © Open Object Press. All rights reserved.
1070
.. Copyright © Open Object Press. All rights reserved.
1072
.. i18n: .. You may take electronic copy of this publication and distribute it if you don't
1073
.. i18n: .. change the content. You can also print a copy to be read by yourself only.
1075
.. You may take electronic copy of this publication and distribute it if you don't
1076
.. change the content. You can also print a copy to be read by yourself only.
1078
.. i18n: .. We have contracts with different publishers in different countries to sell and
1079
.. i18n: .. distribute paper or electronic based versions of this book (translated or not)
1080
.. i18n: .. in bookstores. This helps to distribute and promote the Open ERP product. It
1081
.. i18n: .. also helps us to create incentives to pay contributors and authors using author
1082
.. i18n: .. rights of these sales.
1084
.. We have contracts with different publishers in different countries to sell and
1085
.. distribute paper or electronic based versions of this book (translated or not)
1086
.. in bookstores. This helps to distribute and promote the Open ERP product. It
1087
.. also helps us to create incentives to pay contributors and authors using author
1088
.. rights of these sales.
1090
.. i18n: .. Due to this, grants to translate, modify or sell this book are strictly
1091
.. i18n: .. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
1092
.. i18n: .. written authorisation for this.
1094
.. Due to this, grants to translate, modify or sell this book are strictly
1095
.. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
1096
.. written authorisation for this.
1098
.. i18n: .. Many of the designations used by manufacturers and suppliers to distinguish their
1099
.. i18n: .. products are claimed as trademarks. Where those designations appear in this book,
1100
.. i18n: .. and Open Object Press was aware of a trademark claim, the designations have been
1101
.. i18n: .. printed in initial capitals.
1103
.. Many of the designations used by manufacturers and suppliers to distinguish their
1104
.. products are claimed as trademarks. Where those designations appear in this book,
1105
.. and Open Object Press was aware of a trademark claim, the designations have been
1106
.. printed in initial capitals.
1108
.. i18n: .. While every precaution has been taken in the preparation of this book, the publisher
1109
.. i18n: .. and the authors assume no responsibility for errors or omissions, or for damages
1110
.. i18n: .. resulting from the use of the information contained herein.
1112
.. While every precaution has been taken in the preparation of this book, the publisher
1113
.. and the authors assume no responsibility for errors or omissions, or for damages
1114
.. resulting from the use of the information contained herein.
1116
.. i18n: .. Published by Open Object Press, Grand Rosière, Belgium
1118
.. Published by Open Object Press, Grand Rosière, Belgium
added
removed
i18n/vi/source/book/1/1_1_Inst_Config/1_1_Inst_Config_install.rst
