We’ve made a copy of the production repository, put it in a test server to use as a test repository, created a test BOMAIN.key file, upgraded it and let the users test it. Since the test and production are mirrors of each other, how can the user tell the difference besides keeping the BOMAIN.key file straight? Is there a way to see in Supervisor what physical server it’s pointing to?
Thanks.
Lucia
Listserv Archives (BOB member since 2002-06-25)
Nope. I would stay away from 2 repositories if at all possible and switch to using 1 repository with multiple domains. It is a very ugly process to move documents from 1 repository to another.
Listserv Archives (BOB member since 2002-06-25)
Lucia,
In case you are using WebI the users can see all the reports in production via Web I and have BOMain.key on their m/c pointing to development repository and test the identical dev reports simultaneously …In Supervisor you can go to Tools->Repository and properties to find out the physical server its pointng to …
Anyway every user needs to maintain 2 different BOMain.key files (for prod and dev) on their m/cs if they need to compare the reports from diff repositories .
If you are not using Web I then you will have to manually swap BOMain.key files and find out the behaviour of queries in different repos. correspondingly …
Thanks,
Vikas
Listserv Archives (BOB member since 2002-06-25)
The repositories are on different servers but with the exact same database names. Is there anywhere that lists the server name? Lucia
From: shaila [SMTP:shaila%xenonc.com@internet.kraft.com] Sent: Wednesday, March 08, 2000 1:33 PM
Lucia,
If these repositories are on two different instances/databases, then log on to the supervisory module as General Supervisor, click tools, repository, it will list all the domains, expand the column that says connection which instance/databse the security domain is pointing to.
hope this helps
We’ve made a copy of the production repository, put it in a test server
to
use as a test repository, created a test BOMAIN.key file, upgraded it and let the users test it. Since the test and production are mirrors of each other, how can the user tell the difference besides keeping the
BOMAIN.key
file straight? Is there a way to see in Supervisor what physical server it’s pointing to?
Thanks.
Lucia
Pls report bounces in response to postings to BUSOB-L-Request@listserv.aol.com
Web archives (24 hrs. a day now!): listserv.aol.com/archives/busob-l.html
OR search: Mail to listserv@listserv.aol.com, ‘search a_phrase in BUSOB-L’
Unsubscribe: Mail to listserv@listserv.aol.com, ‘unsubscribe BUSOB-L’
Listserv Archives (BOB member since 2002-06-25)
You are right if you can manage with just one server (no test server) then having 2 domains in the same repository with 2 diff universes in each of them is the best way .
Listserv Archives (BOB member since 2002-06-25)
I am not sure whether I am on the right track here but… taking ORACLE as an example database, you will have two entries in the TNSNAMES.ORA file for connections to two different servers and those names are used for connection. Can you not use this information…
Swati.
Date: Wed, 8 Mar 2000 10:38:40 -0600
The repositories are on different servers but with the exact same database names. Is there anywhere that lists the server name? Lucia
From: shaila [SMTP:shaila%xenonc.com@internet.kraft.com] Sent: Wednesday, March 08, 2000 1:33 PM
Lucia,
If these repositories are on two different instances/databases, then log on to the supervisory module as General Supervisor, click tools, repository, it will list all the domains,
expand
the column that says connection which instance/databse the security
domain
is pointing to.
hope this helps
We’ve made a copy of the production repository, put it in a test server
to
use as a test repository, created a test BOMAIN.key file, upgraded it
and
let the users test it. Since the test and production are mirrors of
each
other, how can the user tell the difference besides keeping the
BOMAIN.key
file straight? Is there a way to see in Supervisor what physical
server
it’s pointing to?
Thanks.
Lucia
______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com
Listserv Archives (BOB member since 2002-06-25)
I agree with Steve - it is cleaner to have only one security domain and multiple universe/dcoument domains. But to answer your question, not really. When you do what shaila said, what you’ll see depends on the type of database you use. You’ll always see the username and password for the database account. If you use Oracle, you’ll see the reference to TNSNAMES.ORA that is being used. If you use an ODBC connection like SQL Server, you’ll see the data source name that is being used. The actual name of the server is referenced from that “lower” level, so BusinessObjects has no knowledge of, nor does it care, what that happens to be.
Paul
Listserv Archives (BOB member since 2002-06-25)
Hi, Lucia
First of all, I agree with the consensus – have only 1 repository with multiple domains. In cases where this is not possible, what I do is to modify the universe slightly. Each of my universes contains a dummy class with the name of the repository (Test or Production) and two objects, the server and the database. Use whatever functions are appropriate to your database.
Basically, I use the Test universe for testing. When I am ready to migrate the universe to Production, I modify the dummy class to reflect that it is a Production universe and then export it. Kind of kludgy, but it works.
Hope that helps,
–
Michael Malone
Senior Consultant
WCI Consulting
Listserv Archives (BOB member since 2002-06-25)
Lucia,
If these repositories are on two different instances/databases, then log on to the supervisory module as General Supervisor, click tools, repository, it will list all the domains, expand the column that says connection which instance/databse the security domain is pointing to.
hope this helps
We’ve made a copy of the production repository, put it in a test server to use as a test repository, created a test BOMAIN.key file, upgraded it and let the users test it. Since the test and production are mirrors of each other, how can the user tell the difference besides keeping the BOMAIN.key file straight? Is there a way to see in Supervisor what physical server it’s pointing to?
Thanks.
Lucia
Listserv Archives (BOB member since 2002-06-25)
Thank you for your help.
Lucia
From: Vats, Vikas (GEL, MSX)
Lucia,
In case you are using WebI the users can see all the reports in production via Web I and have BOMain.key on their m/c pointing to development repository and test the identical dev reports simultaneously …In Supervisor you can go to Tools->Repository and properties to find out the physical server its pointng to …
Anyway every user needs to maintain 2 different BOMain.key files (for prod and dev) on their m/cs if they need to compare the reports from diff repositories .
If you are not using Web I then you will have to manually swap BOMain.key files and find out the behaviour of queries in different repos. correspondingly …
Thanks,
Vikas
We’ve made a copy of the production repository, put it in a test server to use as a test repository, created a test BOMAIN.key file, upgraded it and let the users test it. Since the test and production are mirrors of each other, how can the user tell the difference besides keeping the BOMAIN.key file straight? Is there a way to see in Supervisor what physical server it’s pointing to?
Thanks.
Lucia
Pls report bounces in response to postings to BUSOB-L-Request@listserv.aol.com
Web archives (24 hrs. a day now!): listserv.aol.com/archives/busob-l.html
OR search: Mail to listserv@listserv.aol.com, ‘search a_phrase in BUSOB-L’
Unsubscribe: Mail to listserv@listserv.aol.com, ‘unsubscribe BUSOB-L’
Pls report bounces in response to postings to BUSOB-L-Request@listserv.aol.com
Web archives (24 hrs. a day now!): listserv.aol.com/archives/busob-l.html
OR search: Mail to listserv@listserv.aol.com, ‘search a_phrase in BUSOB-L’
Unsubscribe: Mail to listserv@listserv.aol.com, ‘unsubscribe BUSOB-L’
Listserv Archives (BOB member since 2002-06-25)