Maintaining deployed applications (OpenInsight Specific)
At 30 JAN 1998 11:41:56AM Don Bakke wrote:
As we begin to distribute our runtime applications my concern over maintaining them grows. Particularly in the areas of repairing GFE's and rebuilding indexes.
What is the official method for taking care of these issues? I'd rather design the application to handle them, but is that permissible under the license or even supported by the runtime engine?
Regarding indexes, what happens if the index becomes so corrupted that it requires a manual rebuild? Will they be able to do this or is this an area that falls under the "Tech Support/Warranty" banner, and they'll have to find a way to send us their data table so we can build them a new index table? If they can perform their own rebuilds, this usually ends up with the OS file name for this index getting a new name, which then causes the media map of the deployed applications becoming out of synch with our master development media map. Can this be prevented?
As you can see, we are trying to self-contain our runtime apps as much as possible and would appreciate any ideas on how to acheive this goal.
Thanks,
At 04 FEB 1998 02:35AM Mike Jeremy - LLES Sydney wrote:
I'd also be interested in a reply to this one.
We can't deploy at the moment precisely because of the nightmare in support we would experience.
We are shipping the App with a copy of Developer - Which is an expensive alternative to deploying runtime!
Mike Jeremy
LLES Sydney
At 06 FEB 1998 05:19AM Tony Marler wrote:
Donald,
Notice no answer to this yet. Keep chasing because we are having the same issues.
Tony.
At 06 FEB 1998 11:16AM Don Bakke wrote:
Tony,
Notice no answer to this yet. Keep chasing because we are having the same issues.
I eventually went straight to my sales rep, who then went to Kurt Baker for a response. Here's the bottom line as I understand it:
1. We provide the service which means that the end user must send us their files and we'll fix/update them
2. We sell them a developer's engine which means they have to log everyone out of the runtime, swap engines, fix/update themselves, and then swap the engines again. I suppose they could install the developer OI in a separate directory and run it against the same data files without have to log the user off - but it's still a hassle.
3. We sell them the development ready SDK so that their runtimes can do these common fixes and updates.