TM1 10.2 web URL for specific TM1 server

[manoj928]

Hello ALL,

I am trying to create a URL which let user to go directly to a specific TM1 server (not a specific web-sheet or a cube view), so that they need not to select TM1 server from TM1 web link.

Any suggestion will be appreciated. Please note, i am using TM1 10.2.1 version.

Thanks,
Manoj

[nick_leeson]

http://www-01.ibm.com/support/knowledge ... erenv.html

"Configure Cognos TM1 Web to connect to remote Cognos TM1 servers in your network.
If you want Cognos TM1 Web to connect to a specific Cognos TM1 Admin Server or Cognos TM1 server in your network, configure the AdminHostName and TM1ServerName parameters in the Cognos TM1 Web configuration file, tm1web_config.xml."

[manoj928]

Thanks Nick.

But any setting done in tm1web_config file is universal. what if we have different applications (TM1 servers) and a different set of users for each applications.

I want users tagged with one TM1 server must be routed to that specific server only.

I am trying to have link like below:
http://servername:9510/tm1web/UrlApi.js ... servername

but it seems it is not working. Please let me know if you get any idea.

M

[declanr]

I've only ever used the URL API to open websheets or cubeviews, it might be possible to just log in with it though.

Personally I would have a websheet as a "landing page" for each server though and just use the URL to get to that and from there have links to everything else they might want to use.

[nick_leeson]

Personally I would have a websheet as a "landing page" for each server though and just use the URL to get to that and from there have links to everything else they might want to use.

This is very elegant way of doing it.

[lotsaram]

How to handle this can depend a bit on TM1 version and security method being used. The behaviour of TM1 web since I think either 10.1 (or 9.5?) is that data from multiple TM1 servers can be accessed from the same websheet if the servers are using the same admin host. However in Tm1 web unlike Perspectives there is no requirement to authenticate separately for each server, the user only logs in to one server and if the UserID matches to the other server being referenced then the log in is automatically passed through.

Combined with CAM as the authentication method though this poses some new problems. When using CAM the UserID is automatically created in the Clients dimension upon first login, which means that the administrator loses the ability to control which users are allocated to which server(s). It also renders this method of automatically managing server name references inoperable for TM1 web without some serious tweaking.

I know of one large global implementation where due to server sizing and performance issues a contribution application is geographically split across 5 servers all running on the same physical box and admin host. The application is identical but the data and users are different. To ensure data integrity for the global consolidation is is absolutely critical to ensure that users can only log on to their allocated server depending on their region. For this reason there is an additional server instance that basically does nothing more than hold a lookup for each user for the server instance they are allocated to. This is the instance they actually log onto and their correct server allocation is retrieved as a string and passed as a reference to all DBRW and SUBNM formula references in all websheets. It is quite elaborate, but it works. This is like an extension of Declan's idea of a separate landing page for each server, but means it is possible to have a single central landing page which then farms the users out to the correct server behind the scenes.

(IMO using 10.2 and easier parallelisation of loads to reduce windows and the fact that write locking is more or less a think of the past in this particular example it would probably be better to redesign the application to a single global instance ...)