Rough outline: How I'm setting up "deployment management" for my current client

Discussion forum about all things Gupta, OpenText and the community.
User avatar
Charlie
Canada
Posts: 646
Joined: 07 Mar 2017, 18:52
Location: Fredericton, New Brunswick, Canada

Rough outline: How I'm setting up "deployment management" for my current client

Post by Charlie » 19 Mar 2024, 20:42

Say client has "App A.exe" and "updater.exe" created with Gupta Team Developer.

When user starts "App A", first thing "App A" does is copy the current "updater.exe" from a network drive staging area to the local drive.

Then App A starts updater.exe (with "App A.exe" passed along as a parameter).

"updater.exe" compares local files to the files in the network drive staging area.

Any files that are new or different are copied to the local drive.

When done, "updater.exe" launches App A again with a parameter telling App A to skip over the update process.

The apps, during launch and usage, write out info to INI files on the network. With a "system administration" app that reads those INI files, we can monitor what versions of the applications are on users computers, information about screen resolutions, the last run dates of applications, etc. etc.

Smooth as silk.

OeavDev
Austria
Posts: 98
Joined: 15 May 2018, 11:18
Location: Vienna

Re: Rough outline: How I'm setting up "deployment management" for my current client

Post by OeavDev » 20 Mar 2024, 20:23

Usually running applications can also rename themselves. So, if there is an update, App.exe loads all new files plus App_new.exe into the folder. When downloading is finished, App.exe renames itself to App_old.exe, and App_new.exe to App.exe and finally restart itself - as new version.

User avatar
Charlie
Canada
Posts: 646
Joined: 07 Mar 2017, 18:52
Location: Fredericton, New Brunswick, Canada

Re: Rough outline: How I'm setting up "deployment management" for my current client

Post by Charlie » 20 Mar 2024, 20:59

Yeah, that's how, many moons ago, I had originally set things up.

I switched over to a dedicated "updater.exe" because I had it doing such a large number of things that I did not want to over stuff the end user EXE's.

I also wanted to guarantee that any dependencies (files) used by the end-user application were not opened and blocking their updates. Forcing the end-user exe to close guarantees freeing up all files for updater.exe to replace.

Something like that. Not sure I'm working that right.

visionpro
Mauritius
Posts: 27
Joined: 21 Jun 2017, 02:07
Location: Mauritius

Re: Rough outline: How I'm setting up "deployment management" for my current client

Post by visionpro » 21 Mar 2024, 03:56

Dear Charlie
It will be great if you can share it in the TD Samples on this forum.

Thanks
Samad

User avatar
Charlie
Canada
Posts: 646
Joined: 07 Mar 2017, 18:52
Location: Fredericton, New Brunswick, Canada

Re: Rough outline: How I'm setting up "deployment management" for my current client

Post by Charlie » 21 Mar 2024, 20:00

visionpro wrote:
21 Mar 2024, 03:56
Dear Charlie
It will be great if you can share it in the TD Samples on this forum.

Thanks
Samad
Yeah, I'd like to, but the version I've built for my current client (better than the one I had built for previous client) is not mine to share. The code belongs to the client.

Hence the rough outline (i.e. the design in my head.)

Return to “General Discussion”

Who is online

Users browsing this forum: [Ccbot], monchotgu and 0 guests