Hi,

I have just completed a re-write of an application that I created in OI 2.61. I upgraded to OI 7.1.1. I tried to do a full deploy but get the error message that "SYSUPGRADE" table is not in the destination directory. I also tried an application and upgrade deploy but got nowhere.

Then I tried the "Examples" application. This deployed, but when I double-clicked the "OINSIGHT.EXE" in the Examples directory, I got the error that "Oinsight revboot up failed."

RDK and I don't seem to get along. I thought that I followed the instructions, but apparently not. How do I RDK?

TIA,

Marty

This might help

[email protected]

The Sprezzatura Group Web Site

World Leaders in all things RevSoft

It was just what I needed. Thank you!

Marty,

As Sprez indicated, you need to get the runtime Oengine.dll from RevSoft.

Also, some have found that the easiest way to get a runtime system together is to

1. Clone your development system and then delete all applications and remove non-runtime complient code - leaving a striped down deployment master.

2. Create the Application layers in the RDK master.

3. Do an RDK extract (Module/update) for the application layers and run RDK_Import in your Master.

4. Set the application entry point and finally swap out the development Oengine.dll and replace with the runtime Oengine.dll that you have got from RevSoft.

Hereafter it is simple process of doing an rdk extract for updates and RDK_Import of that material.

Why this rather convoluted path and not the full system or full application? My experience has been that the Development master often contains junk and refuse accumulated over time that inhibits a clean full extract, plus you dont want that stuff ending up in the deployed system anyway. Real important to do some helth & hygiene work on you development application - using ScanRep etc to get rid of orphan events etc - before doing an RDK extract.

Richard Bright

BrightIdeas New Zealand

[email protected]

Hi Richard,

Your advice is excellent. I wondered about the excess 'junk' and unused code, etc. The first app has been deployed successfully and is in use. The advantage that I have now is that the first few apps are going to be used only by me. This gives me an excellent opportunity to practice. I copied your note to a file so that I may access it again at a later date until all this becomes second nature to me.

Thanks,

Marty

Marty,

I cant over-emphasise the importance of getting a 'clean' system for the RDK process. Most problems concerning extract or install can be traced to derelect code, orphaned events etc that trip up the extract / import process.

With a system set up and the right RDK management tools it should take no time at all to roll out an update. On a good day I can extract a minor update and have it into the target system within about two to five minutes.

If you need any further help just email.

Richard Bright

BrightIdeas New Zealand

Hi Richard,

I appreciate the help and the advice. I did as you suggested and 'cloned' the original and cleaned it out. It's nice to have the apps belong to me as it gives me a lot of practice opportunity to RDK.

Thanks for the help and the offer for future help.

Marty

View this thread on the forum...