DNS CNAMES are canonical names given to the servers so that they are easily identifiable. E.g. its easier to remember Essbase.production.thexyzcompany.com than us-esb01v-trg.thexyzcompany.com.
The best thing about cnames is whenever a migration or server change happens, users dont have to worry about changing the connection details in their maxl scripts or vba macros.
Using CNAMEs during Installation: At the time of installation, using cnames is best avoided (unless you have a replicated instance). If a cname mapping is changed, we must make sure that everything works fine.
Using CNAMEs by Planners:
Although users can change the server names to cnames in their urls and scripts, you will have to modify the 'datasources.xml' file from Shared Services and rename the connections by replacing the server names with DNS CNAMES. Not that it causes any problem, but in the 'Essbase server' or 'Planning' node of SmartView shared connections, you will see the server name instead of the CName, something that might confuse the users.
Check out this blog to see how Datasources.xml is modified. Stalwarts have been doing this for ages !
Do note that the same setting is not available in EPM 11.1.2.4 since it is stored in Shared services registry database.
http://www.orahyplabs.com/2011/03/how-to-get-smartview-1112-shared.html
Cheers !
The best thing about cnames is whenever a migration or server change happens, users dont have to worry about changing the connection details in their maxl scripts or vba macros.
Using CNAMEs during Installation: At the time of installation, using cnames is best avoided (unless you have a replicated instance). If a cname mapping is changed, we must make sure that everything works fine.
Using CNAMEs by Planners:
Although users can change the server names to cnames in their urls and scripts, you will have to modify the 'datasources.xml' file from Shared Services and rename the connections by replacing the server names with DNS CNAMES. Not that it causes any problem, but in the 'Essbase server' or 'Planning' node of SmartView shared connections, you will see the server name instead of the CName, something that might confuse the users.
Check out this blog to see how Datasources.xml is modified. Stalwarts have been doing this for ages !
Do note that the same setting is not available in EPM 11.1.2.4 since it is stored in Shared services registry database.
http://www.orahyplabs.com/2011/03/how-to-get-smartview-1112-shared.html
Cheers !
No comments:
Post a Comment