Before I begin figuring out how to do this, thought I'd ask if it is possible.

I have an Apache2 server hosting what 'looks like' 2 applications, in that they use different urls. Apache correctly picks up the different index.html pages based on the url. Then, using oicgi I have calls to different inet_ functions, but they are really all in the same OI application.

Well, it is getting close to time to split one out to its own OI APP name. I'm working on setting up oecgi, and learning how to call oengine, but not finding the references I need to acomplish all this.

Since the current effort is sort of a 'proof of concept' demo, oicgi provides adequate performance. At this point, I want to minimize my time on 'plumbing' and focus on the application. I see no way to run 2 simultanious OI applications using oicgi. I think it is possible with oecgi, but don't see a clear path and want to avoid getting bogged down in the 'plumbing' changes for oecgi if I can.

I'm running Apache2 on a win2000 box. OI and data files are on another win2000 box with an old NT service 1.5. Running OI 7.0 recent build. I use another win2000 box for the development workstation.

Any ideas or guidance greatly appreciated!

arcs@arcscustomsoftware.com

ARCS, Inc. [img]http://www.arcscustomsoftware.com/arcslogo.gif[/img] </QUOTE> ---- === At 20 FEB 2004 12:04PM Donald Bakke wrote: === <QUOTE>Paxton, Sprezz has the ability to do what you want. This is not a normal feature of the OECGI. FWIW, we have one OECGI app serving the needs of multiple OI apps. We created a special application, WEBAPP, that attaches all the necessary tables needed by each OI application. We then have to add our INET routines to this app or SYSPROG. dbakke@srpcs.com [url=http://www.srpcs.com]SRP Computer Solutions, Inc.

Thanks, Don. That is sort of what I figured, and what I am doing now.

Paxton

Thanks for the mention Don. It is very much horses for courses - as in - we developed zzCGI because our clients specifically wanted different URLs to fire different applications. The major disadvantage of this over OECGI with dynamic engines is that even if using dynamic engines with zzCGI you need a WDP - as the license currently stands the only way to avoid a WDP is to use dynamic OECGI.

The Sprezzatura Group

World Leaders in all things RevSoft

You could have one master app which uses a case statement plus the rbasic createengine statement to connect to a second engine running the appropriate application, based on info in the request.

Bob

View this thread on the Works forum...