Move Universe+Reps to other Repository

[apirker]

Hello all!

We have a BO-Repository in our Company for Development.
There are 2 BO-Repositories on the Cusotmer site. One for
Testing and one ist the live-system.

Right now our development is managed like this:
I develop Universes and Reports in our company.
then i transfer them to the customers-testsystem, then
i transfer them from the customers-testsystem to the
live-system.
everyone who have ever done that knows, that this is a VERY long process.

open designer, import universe
set connection to shared.
save vor all users.

open every report.
change every data provider in the report to the shared universe.
save all reports vor all users.

goto customer-test-system.

open universe
change connection to secure-customer-connection
export universe

open ever report
change every data provider in the report to the new-exportet-universe
publish all reports....

and same procedure if the customer says "alright, put it live..."

is there a way to make this less complex??
is there some export or migration tool or something?
i would REALLY appreciate that. (else i commit suicide, i a have to transfer again, 4 universes with about 4-10 reports echt, with about 4 dataproviders each.....)

thanks for every hint....

cheers
Anton

 

[SrikSrikanth]

If your customers are not developing any new Universes or documents for export then there is an easier way. What I mean is, the customer Repositories are completely under your control - meaning what you export is what they see, then there is easier method.

1. Do your exports as you are doing right now on Development.
2. Copy the entire tables to from Development to Test Server of Client.
3. If Testing accepts your changes Then
Copy from Development to Live Server of Client
Else Go to Step 1.

For this u need to be a little careful. The Server Names and Database Names should be maintained constant in the connection strings of the universes. Wheareas the Actual TNS Names (for Oracle) or SQL.Ini (for Sybase) settings should point to the relevant server.

In this set up you export only once - but the other two are handled by SQL scripts which can Drop the entire BO Repository tables on Client servers and copy your tables to the client Servers. This set up cannot be done on a daily basis. Weekly is a good try.

An alternative way and more practical way would be the following

Do this every week:
1. Do your exports to Test Server of Client and intimate the client.
2. If Testing accepts your changes Then Store the Universe in VSS.
Else go to step1.
3. Repeat step 1 thru step 3 for every change if this is not weekend.
4. During the weekend
Take a copy from VSS and export to Test Server of Client.
On the database side, write a script to delete all the BO Repository tables on the
Live server of client and copy the BO Repository tables from Test Server to Live
Server of client.
So your changes will always go into production the following week.

Hope this helps.

Else Go to Step 1.