Managing Two Applications with One Database

[Chris Kelleher]

My company is in the process of creating new applications (web-based) which
work in concert with our client-based progress app. Essentially what we'd
like to do is setup Roundtable so that 2 different applications access the
same database.

We've come up with 2 options to handle this but each seem to have its own
problems:

1) We setup a separate workspace for each application but how do we manage
one database between two applications?

2) We setup one workspace with new product modules. How does this affect
our deployments when we may only want to deploy only one application at a
time (assuming all schema remains constant)?

Anyone have any experience they'd care to share?

Thanks

-Todd

 

[Chris Kelleher]

Both will work. I like #2.

#1. Either implement a policy or use the hooks in
<RTB install>/rtb_evnt.p to enforce a rule that schema
is only modifed in one of the workspaces. You then
import the changes to the other workspace.

#2. At delployment time, you can select which modules
to bring into your production workspaces. I would
even go a step further and separate them into my test
workspaces. Put the database in its own product and
pmodule. Put code for one app in a separate product
and modules. Put code for the other app in a separate
product and modules. Put common code in a separate
product and modules (giving you four products).

When you source to the app1test workspace, you only
include the app1product and modules, dbproduct, and
common product. In the App2test workspace, you only
source the app2product and modules, db product, and
common product.

You could do it with all one product and toggle
individual modules, but it is cleaner to do it by
product (keeps unwanted modules from showing up in the
drop down box on the desktop when you source as
primary).