TM1 Forum

Hi Guys,

I'm trying to make the TM1Web objects available to Workspace. I followed the procedure given by IBM documentation verbatim, however I don't see the required objects except for the blank server name. Has anybody tried it on Cognos Express 10.2.1 ? I'm following the procedure given by IBM documentation from this link: http://pic.dhe.ibm.com/infocenter/cbi/v ... cogbi.html
I also came across technote, that I thought is relevant, but does not solve the problem.

Also, there was a separate page for TM1 web FAQs, that hinted that this might be a bug. http://www-01.ibm.com/support/docview.w ... wg27039576
However, I've checked the versions of BI with Cognos Express 10.2.1, which I guess is Cognos BI 10.2RP1FP1(i.e. 10.2.1.1).

Is this a known issue, should I check with IBM?

I've tried installing express 10.2.1 but I've hit so many issues. Things work then don't. I've given up on it. I would hold off on looking at Express 10.2 for a while. More features in the software = more things to go wrong.

Thanks for your reply Jim, I see where you're getting. I'll still wait for a while to see if someone has worked on it, else report it to IBM.

Just an update, after a lot of trial & errors I can finally include the TM1 Cube Viewer widgets in workspace. Looks like the problem was due to short server names at various configuration files, I changed following files to include the FQDN :

1. pmpsvc_config.xml
2. fpmsvc_config.xml
3. tm1web_config.xml
4. variables_tm1.xml
5. tm1p.ini
6. tm1s.cfg

The Cube viewer widgets can also talk with the slider & select value filters, which is cool!

However, I'm unable to see the TM1 Web Sheet widgets. The documentation does not mention any separate steps than the changes in atom file & properties file.
Anybody knows how that could be included?
I'm trying to include the following:
http://pic.dhe.ibm.com/infocenter/cx/v1 ... D3_1_3_0_3

Not sure if it's the same but we logged a bug for 10.2.1 FP2 Enterprise BI for not being able to load web sheets in iWidgets. IBM was able to reproduce and logged it with development.

Hi All,

I've had similar problems with this recently and found that the files mentioned earlier:
1. pmpsvc_config.xml
2. fpmsvc_config.xml
3. tm1web_config.xml

But also the files:
1. planning.html
2. tm1web.html
3. tm1_contribution.atom

All need to be referencing the same server name, whether this be FQDN (recommended) or not, in addition to this though, these files also seem to cause issues if the names are in different cases i.e. ServerName vs. servername. I've taken to ensuring that all server setups use lower case and FQDN's now, hope this helps someone.

Thanks
Dan