Kbase 21562: How ISVs Can Migrate End User WebClient Application From 9.1B To 9.1C
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/7/2007 |
|
Status: Unverified
GOAL:
How ISVs Can Migrating End User WebClient Application From 9.1B To 9.1C
FIX:
The ISV will have two options for getting the end users upgraded to 9.1C. The first will involve having them uninstall and reinstall their application as well as uninstalling and reinstalling WebClient.
The second will mean maintaining two distinct links on their website supporting two prowcapp files (9.1B and 9.1C) until all users are upgraded. The initial step is to choose which of these options to pursue.
The second step is to prepare their application for 9.1C. This means defining components and possibly System Tasks and a 4GL-based installer using the Application Assembler. They should remove any references to an external installer. During this preparation phase they should continue to maintain their 9.1B application to accommodate current users. At this point they should proceed according to the migration method they have chosen.
"Uninstall/Reinstall" Method
1) Use the Application Assembler to generate an initial version of the
application.
2) The ISV should contact their users and have them uninstall their
application.
3) The end users should also uninstall WebClient. There is a chance
that they have 9.1C for the purpose of running another application
so they should be directed to uninstall 9.1B WebClient.
4) These users must be directed to the new version of the application
that is available via a link on their website. This will trigger
an install of 9.1C WebClient prior to installing the updated
application.
"Two Prowcapps" Method
1) Use the Application Assembler to generate an initial 9.1C version
of the application.
- Specify an Update Install URL on the Options tab in order to
create the Registry entries that will be required by 9.1C -- this
requires the development of the External installer in the
preparation stage identified above.
2) The ISV must create one last version of their 9.1B configuration
file that will direct their current users of the 9.1B application
to the new version of WebClient and the 9.1C version of the
application. The necessary updates (done via the 9.1B Prowcapp
Editor) are:
- Specify 9.1C as the WebClient version.
- Specify a WebClientInstallURL, the URL that points to the 9.1C
WebClient.
- Specify the URL of the 9.1C configuration file. This updates the
registry on the end user's system for the next time the
application is run in shortcut mode.
3) The ISV must add a link to the website which points to the 9.1C
configuration file (in addition to the link already present which
points to the 9.1B configuration file). The ISV must somehow
indicate to the end users that they should choose the 9.1B link to
acquire the update and choose the 91.C link from that point on.
4) All current users will be automatically upgraded when they access
the updated 9.1B configuration file (either via the link on the
ISV's website or the shortcut).
5) During the transition of users from the 9.1B application to the
9.1C application the ISV must maintain both the 9.1B and 9.1C
configuration files. The old configuration file is the only ticket
for the 9.1B end users to the 9.1C application. The ISV can retire
the 9.1B configuration file and remove the link on the website to
it when all users have moved to the 9.1C version of the
application. They can also remove the Update Install URL from the
configuration file since everyone will have been updated to 9.1C
registry requirements.