Re-building the repo

Hi all.

I am looking for a “heads up” here. We have had many problems with our repos ( yes, we have 3 - devl, test and prod). Our problems require scan, repair and compact to be performed frequently. BizO Tech suggested we re-build our repo (actually we are in a position to do it) using 4.1.2. and have only 1 security domain and separate universe and document domains. While waiting for BizO to get a CD sent here, I thought I’d ask the group about what I am going to do. Here is my plan, 1) Create a repo from scratch in our Prod Oracle instance. 2) Create 3 document domains and 3 universe domains for Devl, Test and Prod. 3) Have the Designers export thier universes and reports into the proper domains. They will have to make sure the connect string points to the proper Oracle instance.

Am I missing something here? Can anyone tell me if they have done this, or would or wouldn’t reccommend this? Anything I should watch out for?

TIA,
Sandy Brotje
Roadway Express


Listserv Archives (BOB member since 2002-06-25)

I face a very similar situation. I am the Administrator/General Supervisor in a deployment with two distinct security domains, about 6 distinct development efforts and about 20 different universes and subgroups containing over 200 different user IDs. We currently run 4.0.5.5 and I’m also waiting for my 4.1.2 CD to arrive. We have MSSQL 6.5 databases. I inherited a mess, and until 4.1.X came out, didn’t have a reasonable way of trying to change things.

  1. Create a repo from scratch in our Prod Oracle instance. 2) Create 3 document domains and 3 universe domains for Devl, Test and Prod.
  2. Have the Designers export thier universes and reports into the proper
    domains. They will have to make sure the connect string points to the proper Oracle instance.

Am I missing something here? Can anyone tell me if they have done this, or
would or wouldn’t reccommend this? Anything I should watch out for?

How do you plan on handling security and priviledges? I assume that your Designers currently have different rights in the Development repository than they have in Test or Production. I grant our Designers nearly everything in Development/Quality, but restrict their rights in Production (cannot export documents, cannot delete documents, extremely limited “Designer” module rights, etc.). The only way I can see to do that if I was to shift to one security domain and three document and universe domains would be to create an ID with developer rights, but no others, an ID with Quality rights, but no others, and an ID with Production rights, but no others.

I do want to eliminate our current setup (a Production Security, Document, and Universe domain and a Development/Quality Security, Document, and Universe domain), but I can’t decide what the best way to do that would be. I’d also be curious to know what others who’ve faced similar situations have experienced.

David Berg
Duke Energy Trading & Marketing
dbberg@duke-energy.com


Listserv Archives (BOB member since 2002-06-25)