Hi all,
I am using TM1 10.2.2 FP7 and would like to use TI debugger to help debug some of the TIs in the newly-built model.
I follow this http://cogknowhow.tm1.dk/?s=debugger&submit=Search page but clicking on the login button didnt lead me anywhere. I even tested it on the "planning sample" database exactly the same as the example used in the page, and still, nothing happened after clicking on "Login", the debugger login just froze, i had to kill it in taskmanager.
Can you please advise?
regards
YY
Using IBM TM1 Turbo integrator Debugger
-
- Posts: 27
- Joined: Tue Apr 18, 2017 1:20 am
- OLAP Product: TM1
- Version: PA2.0.8
- Excel Version: MS 2016
Using IBM TM1 Turbo integrator Debugger
- Attachments
-
- Capture.JPG (36.79 KiB) Viewed 4369 times
-
- MVP
- Posts: 3103
- Joined: Mon Dec 29, 2008 6:26 pm
- OLAP Product: TM1, Jedox
- Version: PAL 2.0.9.18
- Excel Version: Microsoft 365
- Location: Brussels, Belgium
- Contact:
Re: Using IBM TM1 Turbo integrator Debugger
Hello,
Are you sure the port number is correct ?
You added EnableTIdebugging=T ?
For me it works fine with:
Are you sure the port number is correct ?
You added EnableTIdebugging=T ?
For me it works fine with:
Best regards,
Wim Gielis
IBM Champion 2024
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
Wim Gielis
IBM Champion 2024
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
-
- Posts: 27
- Joined: Tue Apr 18, 2017 1:20 am
- OLAP Product: TM1
- Version: PA2.0.8
- Excel Version: MS 2016
Re: Using IBM TM1 Turbo integrator Debugger
Thanks Wim,
You are right, the port number is 12354, I had it as 12345. Very silly mistake!
Thanks again.
YY
You are right, the port number is 12354, I had it as 12345. Very silly mistake!
Thanks again.
YY
-
- Community Contributor
- Posts: 295
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Re: Using IBM TM1 Turbo integrator Debugger
Just recording some observations
0. The debugger icon looks like the coronavirus
1. Use TID with PAW Admin thread viewer to make sure you dont get multiple TI debugger sessions which is when it all fails to work. Only way to destroy a TI debug session is continue to the end AFAICS or kill in PAWATW.
2. Execute takes you to the first statement.
3. You will NOT be able to set breakpoints by clicking in the margin a la VBA. Instead highlight the line and right click an select add breakpoint.
4. Multiline statements can be given a breakpoint for each line. I believe you should set the breakpoint at the last line for it to be triggered.
5. Right clicking in the breakpoint area launches Breakpoint editor which allows you to bp other TIs than the main. This facility is crude in that you must know the line no in advance.
6. There are data change breakpoints and locks gained breakpoints too.
7. You will need to have tm1server.log open too as when an exception is thrown such as processquit or file not found it does not show in the debugger. it just goes back to being ready to execute.
0. The debugger icon looks like the coronavirus
1. Use TID with PAW Admin thread viewer to make sure you dont get multiple TI debugger sessions which is when it all fails to work. Only way to destroy a TI debug session is continue to the end AFAICS or kill in PAWATW.
2. Execute takes you to the first statement.
3. You will NOT be able to set breakpoints by clicking in the margin a la VBA. Instead highlight the line and right click an select add breakpoint.
4. Multiline statements can be given a breakpoint for each line. I believe you should set the breakpoint at the last line for it to be triggered.
5. Right clicking in the breakpoint area launches Breakpoint editor which allows you to bp other TIs than the main. This facility is crude in that you must know the line no in advance.
6. There are data change breakpoints and locks gained breakpoints too.
7. You will need to have tm1server.log open too as when an exception is thrown such as processquit or file not found it does not show in the debugger. it just goes back to being ready to execute.