TM1 Forum

Hi Everyone,

Has anyone been able to create the ODBO connection between two Tm1 severs (x64) ?

I have two x64 Tm1 9.5.2 servers with CAM authentication. They are located on the same adminhost.
I need to create ODBO connection between them. The thing is IBM have a very poor section (Connecting
to an OLE DB for OLAP Datasource When Using CAM Authentication ) in the TurboIntegrator Guide.

If you are running a 64-bit version of the TM1 server, you must specify the CAM namespace ID through a
connection string, using the same format noted above. For example the following connection string specifies a CAM namespace ID named NTLM_NAMESPACE:

Provider=TM1OLAP.1;Location=localhost;Data Source=empty;UserID=tm1user;Password="abc123";
Provider String="CAMNamespace=NTLM_NAMESPACE";InitialCatalog=empty

You cannot use the TurboIntegrator user interface to specify the CAM namespace when running a 64-bit TM1 server; you must use a connection string.

Underlined bold text says us that we should use connection string instead of TI user interface. The question is what means 'connection string' here?

Thank you in advance for sharing your experience!

Has anybody been able to do this? The online knowledge center for version hasn't changed. It still say you need to use a connection string, yet it mentions the connection string nowhere else. I have found other sites that mention nothing about doing something different for 64-bit. I think it's down to my CAM Namespace being wrong but I just wanted to make sure,

Jim.

We did it at a client last year. It worked, but it wasn't a pretty sight, and I wouldn't want to put lots of volume through it.
We have also been putting together a Java component using the 10.2.2 Java Extensions and REST/ODATA API. Results are promising but there's work to be done. Server to server interfacing is something I've been after for many, many years - I recall pitching the need to Manny Perez and Arthur Lee at the Black Belt conference in 2010 - Manny thought it was 'rather specialist'

Andrew,

Out of curiosity, what are you trying to do by connecting the two servers? Just transfer data or dimensions as well?

If it helps, there are several ways to transfer data:

1) Flat files on a shared network drive.
2) Replication

You can also use OLEDB and ODBC (via third party application) but they are not well suited if you are sending across mass amounts of data.

David Usherwood wrote:We did it at a client last year. It worked, but it wasn't a pretty sight, and I wouldn't want to put lots of volume through it.
We have also been putting together a Java component using the 10.2.2 Java Extensions and REST/ODATA API. Results are promising but there's work to be done. Server to server interfacing is something I've been after for many, many years - I recall pitching the need to Manny Perez and Arthur Lee at the Black Belt conference in 2010 - Manny thought it was 'rather specialist'

To be fair to Manny it's not something I've done everyday. I would say however that with TM1 now being in the enterprise market it needs to have this kind of functionality for replicating data across different servers. While IBM will push replication we all know it's got more flake than cadbury and it doesn't always fit. If your testing a new release in UAT you may not want all the data copying down from Production. The old fashioned method of exporting to flat file won't cut it with most IT departments,

Jim.

With all due respect to Manny, this is NOT a bit specialist and it's a glaring weakness in the product. Replication? Are you kidding me???? It breaks down faster than a Yugo. If IBM wants TM1 to truly be "Enterprise" they're going to have to fill this gap. If this really worked I would use it all the time for DEV/UAT/PROD migrations. It could make life so much easier for that type stuff.

tomok wrote:With all due respect to Manny, this is NOT a bit specialist and it's a glaring weakness in the product. Replication? Are you kidding me???? It breaks down faster than a Yugo. If IBM wants TM1 to truly be "Enterprise" they're going to have to fill this gap. If this really worked I would use it all the time for DEV/UAT/PROD migrations. It could make life so much easier for that type stuff.

I swear I pretty much just said exactly that???

I was slightly more diplomatic in my language at the time...
Anyway it's no longer Manny's, or Arthur's problem. Vision's looming up, now's the time to corner the team in the bar and do the Ancient Mariner act

I would write it on a club and hit em over the head with it, but with the amount of requests outstanding it would be a very large club!!!!

We have beat them over the head with this since around 1998 (we first had a global company needing to transfer data between servers) but because it doesn't impact a sales demo, it keeps falling on deaf ears. Manny considered it a 'technical issue'. Perhaps now that there is this thing such as "Cloud" it might get a bit more attention.

What is ironic is that because of the old TM1 locking issues, the recommendation was to create a planning server and a reporting server so that writers wouldn't affect readers. This is what they told customers what they recommended, but didn't give any tools to do such. Replication was a joke (and still is). We ended up having to build a complete job scheduling system in TM1 that took care of it all along with extensive logging and such. (stepping down from my soapbox).

Anyway, hopefully we will see some more interest in this area. With Prism being introduced, though, I don't see it happening anytime soon.

blackhawk wrote:We have beat them over the head with this since around 1998 (we first had a global company needing to transfer data between servers) but because it doesn't impact a sales demo, it keeps falling on deaf ears.

Bang on. Until it has impact on possible sales they're oblivious.

blackhawk wrote:Manny considered it a 'technical issue'. Perhaps now that there is this thing such as "Cloud" it might get a bit more attention.

Possibly but I'm guessing they'll need more sales and more people banging this drum before they really pay attention.

blackhawk wrote:What is ironic is that because of the old TM1 locking issues, the recommendation was to create a planning server and a reporting server so that writers wouldn't affect readers. This is what they told customers what they recommended, but didn't give any tools to do such. Replication was a joke (and still is). We ended up having to build a complete job scheduling system in TM1 that took care of it all along with extensive logging and such. (stepping down from my soapbox).

Stay on it all you like. We've all got big gripes with what's been going on over the last few years. You're just joining the choir.

blackhawk wrote:Anyway, hopefully we will see some more interest in this area. With Prism being introduced, though, I don't see it happening anytime soon.

Fingers firmly crossed but we've been let down so many times before. They've been like that relative that promises you a bike for Christmas then ends up giving you a scooter.

Andrew_M wrote:Hi Everyone,

Has anyone been able to create the ODBO connection between two Tm1 severs (x64) ?

I have two x64 Tm1 9.5.2 servers with CAM authentication. They are located on the same adminhost.
I need to create ODBO connection between them. The thing is IBM have a very poor section (Connecting
to an OLE DB for OLAP Datasource When Using CAM Authentication ) in the TurboIntegrator Guide.

If you are running a 64-bit version of the TM1 server, you must specify the CAM namespace ID through a
connection string, using the same format noted above. For example the following connection string specifies a CAM namespace ID named NTLM_NAMESPACE:

Provider=TM1OLAP.1;Location=localhost;Data Source=empty;UserID=tm1user;Password="abc123";
Provider String="CAMNamespace=NTLM_NAMESPACE";InitialCatalog=empty

You cannot use the TurboIntegrator user interface to specify the CAM namespace when running a 64-bit TM1 server; you must use a connection string.

Underlined bold text says us that we should use connection string instead of TI user interface. The question is what means 'connection string' here?

Thank you in advance for sharing your experience!

Have you seen the IBM Technote 1964631 ?

http://www-01.ibm.com/support/docview.w ... wg21964631
Documentation update: Connecting to an OLE DB for OLAP Data Source When Using CAM Authentication

Technote (troubleshooting)

Problem(Abstract)
The IBM Cognos TM1 Turbo Integrator Guide does not clearly explain how to connect to an OLE DB for OLAP data source when CAM authentication is being used.