Difference between revisions of "Documentation/DevGuide/Extensions/Migration of Update Information"
From Apache OpenOffice Wiki
< Documentation | DevGuide
(Initial author Sun Microsystems, Inc.) |
(FINAL VERSION FOR L10N) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
|NextPage=Documentation/DevGuide/Extensions/Description of the Update Information | |NextPage=Documentation/DevGuide/Extensions/Description of the Update Information | ||
}} | }} | ||
| + | {{Documentation/DevGuideLanguages|Documentation/DevGuide/Extensions/{{SUBPAGENAME}}}} | ||
{{DISPLAYTITLE:Migration of Update Information}} | {{DISPLAYTITLE:Migration of Update Information}} | ||
It could become necessary to change the server which hosts the update feed or ''update information''. If this results in a different URL for these files, then the automatic update will not work. Therefore the following procedure is recommended. | It could become necessary to change the server which hosts the update feed or ''update information''. If this results in a different URL for these files, then the automatic update will not work. Therefore the following procedure is recommended. | ||
| Line 14: | Line 15: | ||
{{PDL1}} | {{PDL1}} | ||
| − | [[Category: Extensions]] | + | |
| + | [[Category:Documentation/Developer's Guide/Extensions]] | ||
Latest revision as of 10:12, 13 May 2009
- Display Name
- Icon
- Extension Description
- Extension Identifiers
- Extension Versions
- Target Platform
- Simple License
- Dependencies
- Publisher Information
- System Integration
- Online Update of Extensions
- Running Online - Update
- Concept
- Example Scenario for Providing Updates
- Migration of Update Information
- Description of the Update Information
- Description of Atom Feed
- Examples
It could become necessary to change the server which hosts the update feed or update information. If this results in a different URL for these files, then the automatic update will not work. Therefore the following procedure is recommended.
- Plan for a transition period, that is long enough for most users to get a new update.
- Set up the new server, or the locations for hosting the update information, and run both servers in parallel. That is, the same update information and updates should be available from both servers.
- Prepare new versions for extensions that contain an URL to the new server.
- Switch off the old server after the transition period. Users, which have obtained the update, will be able to use the update mechanism as before. All other users will not be able to get an update anymore.
| Content on this page is licensed under the Public Documentation License (PDL). |
