My environment has multiple universe/document domains (dev, qa, prod) and I have kernel universes that export custom LOVs. My problem: when a user selects a derived universe(domain) they want and use a LOV for the first time, they are prompted with a dialog box to select a universe(domain). The exact message is “This dialog box allows you to choose the universe on which the query was built”. This makes no sense to me since they already selected the domain when picking the universe, so why would they then have to select a domain again for the LOV?
Does anyone have experience with this issue? Thank you, Celeste
I think for that the kernel universes having custom LOV’s should be exported in the same domain as of derived universe. In that case it shouldn’t prompt for any domain . thanks,
vikas
I do have the kernel universes (ORG, REP, CYC, PROD) and derived (SALES) exported to the same domains. There are all five universes in the development domain and all five universes in the qa domain. I guess the dialog box is prompted because the same universe is in two domains, but I would think that chosing the SALES(qa domain) from reporter would automatically know the LOV should be from the qa domain. Any thoughts?
I’m looking for guidance on setting up multiple UNV and DOC domains. For a large enterprise deployment, is it reasonable to establish dev, test, and production domains for each functional business area? My concern is having too many domains to manage. What is a reasonable number/structure for domains?
Here’s what I tried… One universe and document domain for DEV, CERT, PRODUCTION… then, one more production document domain for each functional group. The logic being use the production domain for enterprise wide reports, then use the functional domains for the specific groups’ reports.
Good luck,
Brent
I’m looking for guidance on setting up multiple UNV and DOC domains. For a
large enterprise deployment, is it reasonable to establish dev, test, and
production domains for each functional business area? My concern is having
too many domains to manage. What is a reasonable number/structure for
domains?
It appears to me that if you want multiple document domains or multiple universe domains, they must reside in separate databases. However, in some of the documentation, it states that the Repository is a database but then shows multiple domains in it?
Can someone confirm the multiple database thing for me?
The “Repository” consists of at least 1 Security Domain, 1 Universe Domain and 1 Document Domain. You may add add addtional Universe and Document Domains but they must have different connection parameters that the first Universe and Document Domains.
It appears to me that if you want multiple document domains or multiple universe domains, they must reside in separate databases. However, in some of the documentation, it states that the Repository is a database but then shows multiple domains in it?
Can someone confirm the multiple database thing for me?
Thanks,
Melissa
_________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at http://profiles.msn.com.
In a message dated 00-09-20 13:09:19 EDT, you write:
It appears to me that if you want multiple document domains or multiple
universe domains, they must reside in separate databases. However, in some of the documentation, it states that the Repository is a database but then shows multiple domains in it?
Can someone confirm the multiple database thing for me?
A lot of this is terminology. The bottom line is that the tables used for the different domains have to be distinguished from each other. In MS Access that is often done by setting up different databases. In Oracle, this can be done by assigning different owners. Either way you can’t have two tables with the same name owned by the same “database”.
As Mike said earlier, you need to have different connection definitions for each domain of the same type. So if you have three document domains, you need three different “databases” (ie data files, owners, or some other separation mechanism) for these domains.
You can have one document domain, one security domain, and one universe domain all owned by the same “database” since they are all different tables.
One thing to add to Mike’s answer that often gets overlooked:
If you are going to add a Universe domain (for development reasons), make sure you add a Document domain with the EXACT same connection string. If you don’t do this, you will not be able to have custom lists of values. This feature is so sensitive that it requires every character of the connection string to be exactly the same. Designer doesn’t check the validity of the string. It simply does a string check. Don’t forget: Case matters.
You can have multiple domains on the same databases, provided they are created under different schemas on the same database. For ex. in Oracle on a single database use can have two sets of universe & document domains in two different schemas in a single database
Rgds
Naveen
It appears to me that if you want multiple document domains or multiple universe domains, they must reside in separate databases. However, in some of the documentation, it states that the Repository is a database but then shows multiple domains in it?
Can someone confirm the multiple database thing for me?
Am I correct in assuming that separate databases are also required for SQL Server?
In a message dated 00-09-20 13:09:19 EDT, you write:
It appears to me that if you want multiple document domains or multiple
universe domains, they must reside in separate databases. However, in
some
of the documentation, it states that the Repository is a database but
then
shows multiple domains in it?
Can someone confirm the multiple database thing for me?
A lot of this is terminology. The bottom line is that the tables used for the
different domains have to be distinguished from each other. In MS Access that
is often done by setting up different databases. In Oracle, this can be done by assigning different owners. Either way you can’t have two tables with the same name owned by the same “database”.
As Mike said earlier, you need to have different connection definitions for each domain of the same type. So if you have three document domains, you need
three different “databases” (ie data files, owners, or some other separation mechanism) for these domains.
You can have one document domain, one security domain, and one universe domain all owned by the same “database” since they are all different tables.