Schema/DB name, federation layer and deployment

[system]

Hello everyone,

I am new to BOBJ and currently working on multi source universe with federation layer that has SQL Server 2016 input tables. Input tables in the federation layer contain database schema name in the definition (i.e MYSCHEMA_DEV.dbo).
The challenge is that we have different database name in production (i.e MYSCHEMA_PROD.dbo) so the objects become invalid when LCMBIAR file is promoted to the prod environment. We cannot use CMS to CMS to deployment since there is no connection between DEV and PROD domains.

Please advise and thanks in advance.

Ilia

---

ilia.t (BOB member since 2019-02-21)

[MarkP]

This may help:

120×120 10.4 KB

I work in DB2 and have to change the Schema for my database in each environment (DEV, TEST, PRODUCTION) to accommodate our database structure. In UDT, changing the schema was pretty simple… select all the tables, right click, rename table, and change the Owner. In IDT, it seems like a much more manual process. I have to go into the BLX layer, do a find/replace and run that. Then, do the same in the DLX layer. I also have 63 joins in my database - and it looks as though I have to go into each j…

[system]

It is very unlikely we are going to be able access production environment with the client tools - is there any way we can abstract db name in input table definition besides using synonyms?
Or perhaps there are ways to edit LCMBIAR file? I am aware LCMBIAR file is just nested archives with metadata files but we are unable to edit files inside it (7-Zip errors out with read-only error).
We also tried to extract all the files in LCMBIAR, edit FederationLayer metadata and re-pack it back, but then promotion manager errors out with the manifest error.

---

ilia.t (BOB member since 2019-02-21)

[JohnBClark]

You say you are using a multi-source universe, but you only mention one connection. How many connections do you have?

By default, the universe will use the database name that is specified in the connection unless it is changed in the design tool. I would assume that this would still be the case for a multi-source universe.

Try confirming that the appropriate database name is configured in the connection(s) you are using. Remove the schema name from the database foundation layer of your universe.

While I consider including the schema name in the data foundation as a best practice, this is a use case where you need to remove it.

[system]

From what I see there is only one reference to the database name in configuration - in system DSN (ODBC data sources), I tried removing default database in DSN connection and then selecting federation layer input table from the catalog and it still pulls schema name along with the db name…

---

ilia.t (BOB member since 2019-02-21)

[JohnBClark]

Try it the other way around. Specify the database name in the system DSN and try to remove the schema name in the federation layer.

[system]

Hi John,

Thanks for your response, Edit option is disabled for input tables in the federation layer, the only option available is “Replace by”, when I select “Replace by” option it gives me the same catalog tree to select from and then pulls the schema name along with the dev db name when the table is selected.

---

ilia.t (BOB member since 2019-02-21)