3
.. i18n: single: maintenance
4
.. i18n: single: support
10
.. i18n: Support and maintenance
11
.. i18n: =======================
13
Support and maintenance
14
=======================
16
.. i18n: It's when you actually use your ERP that you will obtain value from your investment. For that reason
17
.. i18n: maintenance and support are critical for your long term success.
19
It's when you actually use your ERP that you will obtain value from your investment. For that reason
20
maintenance and support are critical for your long term success.
22
.. i18n: * Support aims to ensure that end users get the maximum productivity from their use of Open ERP by
23
.. i18n: responding to their questions on the use of the system. Support can be technical or functional.
25
.. i18n: * Maintenance aims to ensure that the system itself continues to function as required. It includes
26
.. i18n: system upgrades, which give you access to the latest functionality available.
28
* Support aims to ensure that end users get the maximum productivity from their use of Open ERP by
29
responding to their questions on the use of the system. Support can be technical or functional.
31
* Maintenance aims to ensure that the system itself continues to function as required. It includes
32
system upgrades, which give you access to the latest functionality available.
34
.. i18n: Some partners offer preventative maintenance. This makes sure that all the specific developments for
35
.. i18n: your system are revised and tested for each new version so that they remain compatible with the base
38
Some partners offer preventative maintenance. This makes sure that all the specific developments for
39
your system are revised and tested for each new version so that they remain compatible with the base
42
.. i18n: Tiny themselves have changed their support strategy from time to time. At the time of writing
43
.. i18n: they propose a maintenance contract supplied either direct to the end user or through partners
44
.. i18n: that guarantees a quick fix to any faults discovered in the covered code. Although you can
45
.. i18n: expect these fixes to become available to all users of the code in time, maintenance
46
.. i18n: guarantees quick attention. And you're likely to get quicker migration support to new upgrades.
48
Tiny themselves have changed their support strategy from time to time. At the time of writing
49
they propose a maintenance contract supplied either direct to the end user or through partners
50
that guarantees a quick fix to any faults discovered in the covered code. Although you can
51
expect these fixes to become available to all users of the code in time, maintenance
52
guarantees quick attention. And you're likely to get quicker migration support to new upgrades.
54
.. i18n: If you haven't anticipated your needs with a preventive maintenance contract, the costs of migration
55
.. i18n: after a few years can become significant. If special modules that you developed have been allowed to
56
.. i18n: become too old you may eventually need a new development to your specifications.
58
If you haven't anticipated your needs with a preventive maintenance contract, the costs of migration
59
after a few years can become significant. If special modules that you developed have been allowed to
60
become too old you may eventually need a new development to your specifications.
63
.. i18n: single: update
64
.. i18n: single: upgrade
66
.. i18n: Updates and Upgrades
67
.. i18n: --------------------
76
.. i18n: There are four sources of code change for Open ERP:
78
There are four sources of code change for Open ERP:
80
.. i18n: * patches supplied by Tiny to correct faults: after validation these patches shouldn't cause any
81
.. i18n: secondary effects,
83
.. i18n: * minor updates, which gather the fault corrections together in one package, and are generally
84
.. i18n: announced with a modification of the version number, such as from 5.0.0 to 5.0.1,
86
.. i18n: * upgrades, which bundle both the fault corrections and the improvements to the functionality in a
87
.. i18n: major release such as from 5.0.3 to 5.2.0.
89
.. i18n: * new functions generally released in the form of new modules.
91
* patches supplied by Tiny to correct faults: after validation these patches shouldn't cause any
94
* minor updates, which gather the fault corrections together in one package, and are generally
95
announced with a modification of the version number, such as from 5.0.0 to 5.0.1,
97
* upgrades, which bundle both the fault corrections and the improvements to the functionality in a
98
major release such as from 5.0.3 to 5.2.0.
100
* new functions generally released in the form of new modules.
102
.. i18n: You should establish a procedure with your supplier to define how to respond to changes in the
103
.. i18n: Open ERP code.
105
You should establish a procedure with your supplier to define how to respond to changes in the
108
.. i18n: For simple updates your maintenance team will evaluate the patches to determine if they are
109
.. i18n: beneficial to the use of your Open ERP. These patches should be tested on an offline instance of
110
.. i18n: Open ERP before being installed in your live production version.
112
For simple updates your maintenance team will evaluate the patches to determine if they are
113
beneficial to the use of your Open ERP. These patches should be tested on an offline instance of
114
Open ERP before being installed in your live production version.
116
.. i18n: The maintenance team would also take charge of regular updates to the software.
118
The maintenance team would also take charge of regular updates to the software.
120
.. i18n: Patches and updates can only be installed if you have the necessary access to the Open ERP server.
121
.. i18n: You must first install the patch or update and then restart the server using the command line: \
122
.. i18n: ``–update=all``\ .
124
Patches and updates can only be installed if you have the necessary access to the Open ERP server.
125
You must first install the patch or update and then restart the server using the command line: \
128
.. i18n: Once Tiny has released a new upgraded version your response should be a cautious one. If you're
129
.. i18n: perfectly satisfied with the existing system it would be best to not touch the new version. If you
130
.. i18n: want to have access to the new functionality supplied by an upgraded version, you have a delicate
131
.. i18n: operation to carry out. Most upgrades require your data to be migrated because the databases before
132
.. i18n: and after the upgrade can be a little different.
134
Once Tiny has released a new upgraded version your response should be a cautious one. If you're
135
perfectly satisfied with the existing system it would be best to not touch the new version. If you
136
want to have access to the new functionality supplied by an upgraded version, you have a delicate
137
operation to carry out. Most upgrades require your data to be migrated because the databases before
138
and after the upgrade can be a little different.
141
.. i18n: single: migration
146
.. i18n: Version Migration
147
.. i18n: -----------------
152
.. i18n: Open ERP has a system to manage migrations semi-automatically. To update specific modules, or the whole
153
.. i18n: database, you only need to start the server with the argument:–\ ``update=NAME_OF_MODULE``\ or \
154
.. i18n: ``–update=all``\ (that's minor module changes).
156
Open ERP has a system to manage migrations semi-automatically. To update specific modules, or the whole
157
database, you only need to start the server with the argument:–\ ``update=NAME_OF_MODULE``\ or \
158
``–update=all``\ (that's minor module changes).
160
.. i18n: New stable versions of Open ERP sometimes require operations that aren't provided in the automated
161
.. i18n: migration. Tiny, the creator and maintainer of Open ERP, has a policy of supporting migration from
162
.. i18n: all official stable releases to the latest. Scripts are provided for each new release of a stable
163
.. i18n: version. These carry out the upgrade from the previous major version to the new major version.
165
New stable versions of Open ERP sometimes require operations that aren't provided in the automated
166
migration. Tiny, the creator and maintainer of Open ERP, has a policy of supporting migration from
167
all official stable releases to the latest. Scripts are provided for each new release of a stable
168
version. These carry out the upgrade from the previous major version to the new major version.
170
.. i18n: Managers responsible for the migration between two versions of Open ERP will find the
171
.. i18n: documentation and the necessary scripts in the directory \ ``doc/migrate``\ of the Open ERP
174
Managers responsible for the migration between two versions of Open ERP will find the
175
documentation and the necessary scripts in the directory \ ``doc/migrate``\ of the Open ERP
178
.. i18n: The changes between version 4 and 5 made the migration process more difficult than in the past
179
.. i18n: so there was a greater delay in the provision of migration assistance and more manual work
182
The changes between version 4 and 5 made the migration process more difficult than in the past
183
so there was a greater delay in the provision of migration assistance and more manual work
186
.. i18n: The procedure for migrating runs like this:
188
The procedure for migrating runs like this:
190
.. i18n: #. Make a backup of the database from the old version of Open ERP
192
.. i18n: #. Stop the server running the old version
194
.. i18n: #. Start the script called \ ``pre.py``\ for the versions you're moving between.
196
.. i18n: #. Start the new version of the server using the option –\ ``update=all``\
198
.. i18n: #. Stop the server running the new version.
200
.. i18n: #. Start the script called post.py for the versions you're moving between.
202
.. i18n: #. Start the new version of the server and test it.
204
#. Make a backup of the database from the old version of Open ERP
206
#. Stop the server running the old version
208
#. Start the script called \ ``pre.py``\ for the versions you're moving between.
210
#. Start the new version of the server using the option –\ ``update=all``\
212
#. Stop the server running the new version.
214
#. Start the script called post.py for the versions you're moving between.
216
#. Start the new version of the server and test it.
218
.. i18n: A migration is never an easy process. It may be that your system doesn't function as it did before
219
.. i18n: or that something requires new developments in the functionality of the modules that have already
220
.. i18n: been installed. So you should only move to a new version if you have a real need and should engage a
221
.. i18n: competent partner to help if the version that you use differs greatly from the basic version of
224
A migration is never an easy process. It may be that your system doesn't function as it did before
225
or that something requires new developments in the functionality of the modules that have already
226
been installed. So you should only move to a new version if you have a real need and should engage a
227
competent partner to help if the version that you use differs greatly from the basic version of
230
.. i18n: Similarly you should take care that this migration does not incorrectly change any setting
231
.. i18n: that has already been made. The main menu structure might have been modified in place
232
.. i18n: without proper recording of the changes.
233
.. i18n: So you could find that you're making the wrong assumptions about that structure
234
.. i18n: when later loading data in that was recorded with the Module Recorder.
236
Similarly you should take care that this migration does not incorrectly change any setting
237
that has already been made. The main menu structure might have been modified in place
238
without proper recording of the changes.
239
So you could find that you're making the wrong assumptions about that structure
240
when later loading data in that was recorded with the Module Recorder.
242
.. i18n: .. Copyright © Open Object Press. All rights reserved.
244
.. Copyright © Open Object Press. All rights reserved.
246
.. i18n: .. You may take electronic copy of this publication and distribute it if you don't
247
.. i18n: .. change the content. You can also print a copy to be read by yourself only.
249
.. You may take electronic copy of this publication and distribute it if you don't
250
.. change the content. You can also print a copy to be read by yourself only.
252
.. i18n: .. We have contracts with different publishers in different countries to sell and
253
.. i18n: .. distribute paper or electronic based versions of this book (translated or not)
254
.. i18n: .. in bookstores. This helps to distribute and promote the Open ERP product. It
255
.. i18n: .. also helps us to create incentives to pay contributors and authors using author
256
.. i18n: .. rights of these sales.
258
.. We have contracts with different publishers in different countries to sell and
259
.. distribute paper or electronic based versions of this book (translated or not)
260
.. in bookstores. This helps to distribute and promote the Open ERP product. It
261
.. also helps us to create incentives to pay contributors and authors using author
262
.. rights of these sales.
264
.. i18n: .. Due to this, grants to translate, modify or sell this book are strictly
265
.. i18n: .. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
266
.. i18n: .. written authorisation for this.
268
.. Due to this, grants to translate, modify or sell this book are strictly
269
.. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
270
.. written authorisation for this.
272
.. i18n: .. Many of the designations used by manufacturers and suppliers to distinguish their
273
.. i18n: .. products are claimed as trademarks. Where those designations appear in this book,
274
.. i18n: .. and Open Object Press was aware of a trademark claim, the designations have been
275
.. i18n: .. printed in initial capitals.
277
.. Many of the designations used by manufacturers and suppliers to distinguish their
278
.. products are claimed as trademarks. Where those designations appear in this book,
279
.. and Open Object Press was aware of a trademark claim, the designations have been
280
.. printed in initial capitals.
282
.. i18n: .. While every precaution has been taken in the preparation of this book, the publisher
283
.. i18n: .. and the authors assume no responsibility for errors or omissions, or for damages
284
.. i18n: .. resulting from the use of the information contained herein.
286
.. While every precaution has been taken in the preparation of this book, the publisher
287
.. and the authors assume no responsibility for errors or omissions, or for damages
288
.. resulting from the use of the information contained herein.
290
.. i18n: .. Published by Open Object Press, Grand Rosière, Belgium
292
.. Published by Open Object Press, Grand Rosière, Belgium