We are getting ready to deploy our first of a few applications in OpenInsight and I'm still not clear on a couple things - maybe someone can help me out. I'm coming to this from an ARev point of view (terminology).

- Can multiple 'applications' (accounts) exist under one 'runtime' environment in OI? This would mean users could log into a specific application(s) under one runtime engine. Or is this limited to a 'full development' type of deployment?

- Is there an equivilant to a 'global' account in OI? Can files be shared between applications?

In ARev we currently have a few different applications, that share files via the global account. I'm looking for the best way to accomplish that in OI. We do have an unlimited runtime liscense for OI - so I would like to keep the apps under this one runtime. My question/concern is - do we need to develop everything under one 'application' to do this, or can we use different applications, and deploy them out to the same runtime environment.

TIA,

Jeff

Jeff,

Can multiple 'applications' (accounts) exist under one 'runtime' environment in OI?

Yes, you can have multiple applications running under a single runtime of OI. The only caveat is that only one application of OI can run on a single machine at the same time (although different machines can be running different applications simultaneously.)

Is there an equivilant to a 'global' account in OI? Can files be shared between applications?

Files can still be under the 'global' account and behave the way they did in AREV (in fact, the OI check-out and appbackup routines create their temporary files in the 'global' account). However, this may not be necessary since OI is able to attach tables from different accounts other than it's own - without the use of an alias. Of course, perhaps deep down inside OI works with these files the same way AREV did with aliases but you don't realize it.

My question/concern is - do we need to develop everything under one 'application' to do this, or can we use different applications, and deploy them out to the same runtime environment.

You can maintain the exact structure of your AREV runtime in OI if you choose. If you are planning any kind of hybrid development (i.e. AREV and OI being used at the same time) it would definitely be best to keep things as they are. So, create the different applications (realizing that OI only allows 8 characters for an application name while AREV didn't care how long it was) and decide for yourself whether or not to keep the tables as global. In OI it really doesn't matter as far as I can tell.

[email protected]

SRP Computer Solutions

Actually, it's sorta kinda possible, in a way, to have two applications running in OI at the same time. This sounds like a good SENL article, since it get's a bit involved, and I have nothing else except indexes to do next, and I don't really want to do that.

Underneath the hood, it calls ALIAS_TABLE. Big difference was that RTI got rid of the 'if the account of the alias table does not exist, you can't attach me' code logic.

Every thing else, as Don says, is basically like it is in ARev.

[email protected]

Sprezzatura, Inc.

Actually, it's sorta kinda possible, in a way, to have two applications running in OI at the same time. This sounds like a good SENL article, since it get's a bit involved, and I have nothing else except indexes to do next, and I don't really want to do that.

I remember reading somewhere in my archives about the ability to launch more than one instance of OI but I believe this is contingent on both applications using the same database. I've never quite understood what this meant but I assume this is what you are referring to.

Anyhow, if you can shed some light here I would love to read about it. I've been trying to figure out a way to be developing/running my client's applications while keeping a copy of our internal application open as well so I can track our development progress and time on/off projects.

[email protected]

SRP Computer Solutions

View this thread on the forum...