Why DSN with same name is required on Server and local machine to work on universe

[former_member371433]

Hello All,

I have a BO PROD server where I have created DSNs for different database universe with BO Service user, consider it as BOAdmin (having read rights on PROD Database server).

Now, user wants to import universe on a different server which is having IDT and UDT installed and have all connections establishment with PROD Server.

User has imported universe successfully from PROD Server. Now, I need to explain, why DSN with same name and created by same username is also necessary to create on local machine to test the connection successfully.

(Yes, we can create DSN with other username on local machine and assign this DSN to imported universe onwards, But then it won't be feasible to change every time a new DSN to universe).

I want to establish consistency by creating DSN with same name and created by same user name as created on PROD server.

Please suggest me the way I can convince to user to create same name DSN with same user name, if I am not wrong.

Please Help!

Thanks
Kushal

[former_member198519]

What do they expect, Universe to take any random connections?

Best way is to show them the connection information in Universe. I don't think you need to do anything else to convince them to create the same database connection as the universe is using.

[Former Member]

Hi Kushal,

DSN's are required on the local machine so that the client tools can communicate to the DB. This communication will take place locally and hence we need the DSN's on the local machines.

DSN's are available for ODBC middleware, even for other middleware's like JDBC or Native Clients manual configurations are required on the local machines. This is a by-design behavior.

One way to bypass DSN is to use OLE DB drivers (Only available for SQL Server). In this you only need the drivers to be installed on the local machine and DSN's are not required.

In IDT there is an option 'Server Middleware' under 'Window-->Preferences-->Information Design Tool --> Secured Connections'. This will use the drivers from server box but only for projects retrieved from the repository and not for newly created connections(.cnx)

Hope it helps!

Regards,

Adil Raj