I'm gathering information for our migration from 4.3.6 to 5.2.3. I'd be grateful for any information on setting up mulitple MRE's for establishing development and production environments. Currently we are supporting these using domains. I was hoping that multiple MRE's would allow us to access development tables in one domain and production tables in the other. As it is now we can only access the production tables.

Can anyone offer any advice on the pros and cons I need to consider when deciding Single MRE vs Multiple MRE ?

Thanks

The tables accessed through the MRE are not controlled by the MRE domain, but rather the pathing in the profile of the user that is logged into the Reporting server. It sounds like the pathing to your data sources all resides inside the edasprof (i'm assuming this, so if i'm wrong, i'm wrong) you may want to set up development and production userids - each with separate pathing to the data sources.

You are correct my Edasprof controls the ODBC which points to my production environment. The ACX members contain the tablename path. This doesn't allow me to point to anything other than production (otherwise I effect production). My thought was two machines, two catalog directories of master file definitions and ACX members. The ACX on one machine would point to test the ACX on the other machine would point to production.

Is there a better way ...... ?

If you used the user profiles (.prf) instead of the edasprof.prf to set up your pathing, then each user can have different pointers - to different tables, we do this now. The problem you are having is a result of having the global profile control everything. Try investigating the usage of user.prf instead. It makes things much more flexible. Anytime I want to use test data - instead of prod, i just change my path - obviously this is something only an administrator can control - but if you have access to the profiles, I suggest creating prod and test users.

In MRE 5.2, you can associated a specific WF server or APP PATH setting to individual domains or even individual reports. If both your production and test tables are configured in the same webfocus server, you could store each set of tables (MFD/AFD) in its own application diretory. You could then create 2 domains (PRODDOMAIN & TESTDOMAIN), each pointing to a separate application directory.