3
.. i18n: single: maintenance
4
.. i18n: single: support
11
.. i18n: Support and maintenance
12
.. i18n: =======================
15
Support and maintenance
16
=======================
18
.. i18n: It's when you actually use your ERP that you will obtain value from your investment. For that reason
19
.. i18n: maintenance and support are critical for your long term success.
22
It's when you actually use your ERP that you will obtain value from your investment. For that reason
23
maintenance and support are critical for your long term success.
25
.. i18n: * Support aims to ensure that end users get the maximum productivity from their use of Open ERP by
26
.. i18n: responding to their questions on the use of the system. Support can be technical or functional.
28
.. i18n: * Maintenance aims to ensure that the system itself continues to function as required. It includes
29
.. i18n: system upgrades, which give you access to the latest functionality available.
32
* Support aims to ensure that end users get the maximum productivity from their use of Open ERP by
33
responding to their questions on the use of the system. Support can be technical or functional.
35
* Maintenance aims to ensure that the system itself continues to function as required. It includes
36
system upgrades, which give you access to the latest functionality available.
38
.. i18n: Some partners offer preventative maintenance. This makes sure that all the specific developments for
39
.. i18n: your system are revised and tested for each new version so that they remain compatible with the base
43
Some partners offer preventative maintenance. This makes sure that all the specific developments for
44
your system are revised and tested for each new version so that they remain compatible with the base
47
.. i18n: Tiny themselves have changed their support strategy from time to time. At the time of writing
48
.. i18n: they propose a maintenance contract supplied either direct to the end user or through partners
49
.. i18n: that guarantees a quick fix to any faults discovered in the covered code. Although you can
50
.. i18n: expect these fixes to become available to all users of the code in time, maintenance
51
.. i18n: guarantees quick attention. And you're likely to get quicker migration support to new upgrades.
54
Tiny themselves have changed their support strategy from time to time. At the time of writing
55
they propose a maintenance contract supplied either direct to the end user or through partners
56
that guarantees a quick fix to any faults discovered in the covered code. Although you can
57
expect these fixes to become available to all users of the code in time, maintenance
58
guarantees quick attention. And you're likely to get quicker migration support to new upgrades.
60
.. i18n: If you haven't anticipated your needs with a preventive maintenance contract, the costs of migration
61
.. i18n: after a few years can become significant. If special modules that you developed have been allowed to
62
.. i18n: become too old you may eventually need a new development to your specifications.
65
If you haven't anticipated your needs with a preventive maintenance contract, the costs of migration
66
after a few years can become significant. If special modules that you developed have been allowed to
67
become too old you may eventually need a new development to your specifications.
70
.. i18n: single: update
71
.. i18n: single: upgrade
73
.. i18n: Updates and Upgrades
74
.. i18n: --------------------
84
.. i18n: There are four sources of code change for Open ERP:
87
There are four sources of code change for Open ERP:
89
.. i18n: * patches supplied by Tiny to correct faults: after validation these patches shouldn't cause any
90
.. i18n: secondary effects,
92
.. i18n: * minor updates, which gather the fault corrections together in one package, and are generally
93
.. i18n: announced with a modification of the version number, such as from 5.0.0 to 5.0.1,
95
.. i18n: * upgrades, which bundle both the fault corrections and the improvements to the functionality in a
96
.. i18n: major release such as from 5.0.3 to 5.2.0.
98
.. i18n: * new functions generally released in the form of new modules.
101
* patches supplied by Tiny to correct faults: after validation these patches shouldn't cause any
104
* minor updates, which gather the fault corrections together in one package, and are generally
105
announced with a modification of the version number, such as from 5.0.0 to 5.0.1,
107
* upgrades, which bundle both the fault corrections and the improvements to the functionality in a
108
major release such as from 5.0.3 to 5.2.0.
110
* new functions generally released in the form of new modules.
112
.. i18n: You should establish a procedure with your supplier to define how to respond to changes in the
113
.. i18n: Open ERP code.
116
You should establish a procedure with your supplier to define how to respond to changes in the
119
.. i18n: For simple updates your maintenance team will evaluate the patches to determine if they are
120
.. i18n: beneficial to the use of your Open ERP. These patches should be tested on an offline instance of
121
.. i18n: Open ERP before being installed in your live production version.
124
For simple updates your maintenance team will evaluate the patches to determine if they are
125
beneficial to the use of your Open ERP. These patches should be tested on an offline instance of
126
Open ERP before being installed in your live production version.
128
.. i18n: The maintenance team would also take charge of regular updates to the software.
131
The maintenance team would also take charge of regular updates to the software.
133
.. i18n: Patches and updates can only be installed if you have the necessary access to the Open ERP server.
134
.. i18n: You must first install the patch or update and then restart the server using the command line: \
135
.. i18n: ``–update=all``\ .
138
Patches and updates can only be installed if you have the necessary access to the Open ERP server.
139
You must first install the patch or update and then restart the server using the command line: \
142
.. i18n: Once Tiny has released a new upgraded version your response should be a cautious one. If you're
143
.. i18n: perfectly satisfied with the existing system it would be best to not touch the new version. If you
144
.. i18n: want to have access to the new functionality supplied by an upgraded version, you have a delicate
145
.. i18n: operation to carry out. Most upgrades require your data to be migrated because the databases before
146
.. i18n: and after the upgrade can be a little different.
149
Once Tiny has released a new upgraded version your response should be a cautious one. If you're
150
perfectly satisfied with the existing system it would be best to not touch the new version. If you
151
want to have access to the new functionality supplied by an upgraded version, you have a delicate
152
operation to carry out. Most upgrades require your data to be migrated because the databases before
153
and after the upgrade can be a little different.
156
.. i18n: single: migration
162
.. i18n: Version Migration
163
.. i18n: -----------------
169
.. i18n: Open ERP has a system to manage migrations semi-automatically. To update specific modules, or the whole
170
.. i18n: database, you only need to start the server with the argument:–\ ``update=NAME_OF_MODULE``\ or \
171
.. i18n: ``–update=all``\ (that's minor module changes).
174
Open ERP has a system to manage migrations semi-automatically. To update specific modules, or the whole
175
database, you only need to start the server with the argument:–\ ``update=NAME_OF_MODULE``\ or \
176
``–update=all``\ (that's minor module changes).
178
.. i18n: New stable versions of Open ERP sometimes require operations that aren't provided in the automated
179
.. i18n: migration. Tiny, the creator and maintainer of Open ERP, has a policy of supporting migration from
180
.. i18n: all official stable releases to the latest. Scripts are provided for each new release of a stable
181
.. i18n: version. These carry out the upgrade from the previous major version to the new major version.
184
New stable versions of Open ERP sometimes require operations that aren't provided in the automated
185
migration. Tiny, the creator and maintainer of Open ERP, has a policy of supporting migration from
186
all official stable releases to the latest. Scripts are provided for each new release of a stable
187
version. These carry out the upgrade from the previous major version to the new major version.
189
.. i18n: Managers responsible for the migration between two versions of Open ERP will find the
190
.. i18n: documentation and the necessary scripts in the directory \ ``doc/migrate``\ of the Open ERP
194
Managers responsible for the migration between two versions of Open ERP will find the
195
documentation and the necessary scripts in the directory \ ``doc/migrate``\ of the Open ERP
198
.. i18n: The changes between version 4 and 5 made the migration process more difficult than in the past
199
.. i18n: so there was a greater delay in the provision of migration assistance and more manual work
203
The changes between version 4 and 5 made the migration process more difficult than in the past
204
so there was a greater delay in the provision of migration assistance and more manual work
207
.. i18n: The procedure for migrating runs like this:
210
The procedure for migrating runs like this:
212
.. i18n: #. Make a backup of the database from the old version of Open ERP
214
.. i18n: #. Stop the server running the old version
216
.. i18n: #. Start the script called \ ``pre.py``\ for the versions you're moving between.
218
.. i18n: #. Start the new version of the server using the option –\ ``update=all``\
220
.. i18n: #. Stop the server running the new version.
222
.. i18n: #. Start the script called post.py for the versions you're moving between.
224
.. i18n: #. Start the new version of the server and test it.
227
#. Make a backup of the database from the old version of Open ERP
229
#. Stop the server running the old version
231
#. Start the script called \ ``pre.py``\ for the versions you're moving between.
233
#. Start the new version of the server using the option –\ ``update=all``\
235
#. Stop the server running the new version.
237
#. Start the script called post.py for the versions you're moving between.
239
#. Start the new version of the server and test it.
241
.. i18n: A migration is never an easy process. It may be that your system doesn't function as it did before
242
.. i18n: or that something requires new developments in the functionality of the modules that have already
243
.. i18n: been installed. So you should only move to a new version if you have a real need and should engage a
244
.. i18n: competent partner to help if the version that you use differs greatly from the basic version of
248
A migration is never an easy process. It may be that your system doesn't function as it did before
249
or that something requires new developments in the functionality of the modules that have already
250
been installed. So you should only move to a new version if you have a real need and should engage a
251
competent partner to help if the version that you use differs greatly from the basic version of
254
.. i18n: Similarly you should take care that this migration does not incorrectly change any setting
255
.. i18n: that has already been made. The main menu structure might have been modified in place
256
.. i18n: without proper recording of the changes.
257
.. i18n: So you could find that you're making the wrong assumptions about that structure
258
.. i18n: when later loading data in that was recorded with the Module Recorder.
261
Similarly you should take care that this migration does not incorrectly change any setting
262
that has already been made. The main menu structure might have been modified in place
263
without proper recording of the changes.
264
So you could find that you're making the wrong assumptions about that structure
265
when later loading data in that was recorded with the Module Recorder.
267
.. i18n: .. Copyright © Open Object Press. All rights reserved.
270
.. Copyright © Open Object Press. All rights reserved.
272
.. i18n: .. You may take electronic copy of this publication and distribute it if you don't
273
.. i18n: .. change the content. You can also print a copy to be read by yourself only.
276
.. You may take electronic copy of this publication and distribute it if you don't
277
.. change the content. You can also print a copy to be read by yourself only.
279
.. i18n: .. We have contracts with different publishers in different countries to sell and
280
.. i18n: .. distribute paper or electronic based versions of this book (translated or not)
281
.. i18n: .. in bookstores. This helps to distribute and promote the OpenERP product. It
282
.. i18n: .. also helps us to create incentives to pay contributors and authors using author
283
.. i18n: .. rights of these sales.
286
.. We have contracts with different publishers in different countries to sell and
287
.. distribute paper or electronic based versions of this book (translated or not)
288
.. in bookstores. This helps to distribute and promote the OpenERP product. It
289
.. also helps us to create incentives to pay contributors and authors using author
290
.. rights of these sales.
292
.. i18n: .. Due to this, grants to translate, modify or sell this book are strictly
293
.. i18n: .. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
294
.. i18n: .. written authorisation for this.
297
.. Due to this, grants to translate, modify or sell this book are strictly
298
.. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
299
.. written authorisation for this.
301
.. i18n: .. Many of the designations used by manufacturers and suppliers to distinguish their
302
.. i18n: .. products are claimed as trademarks. Where those designations appear in this book,
303
.. i18n: .. and Open Object Press was aware of a trademark claim, the designations have been
304
.. i18n: .. printed in initial capitals.
307
.. Many of the designations used by manufacturers and suppliers to distinguish their
308
.. products are claimed as trademarks. Where those designations appear in this book,
309
.. and Open Object Press was aware of a trademark claim, the designations have been
310
.. printed in initial capitals.
312
.. i18n: .. While every precaution has been taken in the preparation of this book, the publisher
313
.. i18n: .. and the authors assume no responsibility for errors or omissions, or for damages
314
.. i18n: .. resulting from the use of the information contained herein.
317
.. While every precaution has been taken in the preparation of this book, the publisher
318
.. and the authors assume no responsibility for errors or omissions, or for damages
319
.. resulting from the use of the information contained herein.
321
.. i18n: .. Published by Open Object Press, Grand Rosière, Belgium
324
.. Published by Open Object Press, Grand Rosière, Belgium
added
removed
i18n/ru/source/book/8/8_21_Implem/8_21_Implem_support.rst
