Hello Michael,

thank you for bringing this up.

>While those provide some value, the real value would be in triggering a report either based on some event or via a schedule. 
Jason has said this. Use triggered schedules. I can confirm this.

We have seen customer doing so and triggering 50.000+ reports at the end of the month with sales provisions for insurance retails on 100% unix environments (but of course using CLI and host access).

>Would also like to open a discussion in general of what anyone else is using the API for. Seems like it's pretty basic for now.

We have used SDK (SOAP) API extensively for configuring, skinning, deployments, user rights, group rights and testing reports (2.500+ reports with over a hundred parameters in serial) .... everything in Java, tested against CA8+10+11.0+11.1
I would be happy to share code.

We have used Angular + "REST API" for automating almost anything related to report and data retrieval that the portal offers. Presented this in Miami 2018 and  at IBM think 2019 in SF - including authentication, interactive report running, retrieval of save outputs in different formats ending up in Dashboard with First Contentful Paint in less then 0.5s and fully interactive in less then 2s.

Apart of that we automated some features we were missing by recording click paths and re-running them in test automators. I imagine that triggering something would be feasible.

We built quite an extensive testsuite around this and combined it with FOSS test emulators. Testing Querystudio ... create reports, run reports, change sorting, ordering ... Testing cubes: open report on cube, get a cube dimension and test that all expected members are there in the right order ... Would love to share the code and experience.

We have all projects on github in private repos and have asked @Jason Tavoularis, @RACHEL SU and Chris McPerson on going public. Steve Macko was asked to review if we can open the repos to the public. --> topic is loading, we hope to get a positive response soon. In the meantime I would be happy to share details with licenced IBM Cognos users for sure.

In the IBM Cognos usergroup for DACH (Germany, Austria, Switzerland) there is a thread about SDK.​​​ I think it must not be limited to "german".

Ah ... almost forgot the loadtesting plans with jMeter. We have prepared plans with RAMPUP + timing to understand where our environments start queuing in order to calculate expected concurrency and the involved hardware dimensions.

Looking forward to ideas on the topic.

trigger.bat http://localhost:9300/p2pd/servlet/dispatch usernamepassword namespace databaserefreshtriggername,emailtriggername

Hello Michael,

thank you for bringing this up.

>While those provide some value, the real value would be in triggering a report either based on some event or via a schedule. 
Jason has said this. Use triggered schedules. I can confirm this.

We have seen customer doing so and triggering 50.000+ reports at the end of the month with sales provisions for insurance retails on 100% unix environments (but of course using CLI and host access).

>Would also like to open a discussion in general of what anyone else is using the API for. Seems like it's pretty basic for now.

We have used SDK (SOAP) API extensively for configuring, skinning, deployments, user rights, group rights and testing reports (2.500+ reports with over a hundred parameters in serial) .... everything in Java, tested against CA8+10+11.0+11.1
I would be happy to share code.

We have used Angular + "REST API" for automating almost anything related to report and data retrieval that the portal offers. Presented this in Miami 2018 and  at IBM think 2019 in SF - including authentication, interactive report running, retrieval of save outputs in different formats ending up in Dashboard with First Contentful Paint in less then 0.5s and fully interactive in less then 2s.

Apart of that we automated some features we were missing by recording click paths and re-running them in test automators. I imagine that triggering something would be feasible.

We built quite an extensive testsuite around this and combined it with FOSS test emulators. Testing Querystudio ... create reports, run reports, change sorting, ordering ... Testing cubes: open report on cube, get a cube dimension and test that all expected members are there in the right order ... Would love to share the code and experience.

We have all projects on github in private repos and have asked @Jason Tavoularis, @RACHEL SU and Chris McPerson on going public. Steve Macko was asked to review if we can open the repos to the public. --> topic is loading, we hope to get a positive response soon. In the meantime I would be happy to share details with licenced IBM Cognos users for sure.

In the IBM Cognos usergroup for DACH (Germany, Austria, Switzerland) there is a thread about SDK.​​​ I think it must not be limited to "german".

Ah ... almost forgot the loadtesting plans with jMeter. We have prepared plans with RAMPUP + timing to understand where our environments start queuing in order to calculate expected concurrency and the involved hardware dimensions.

Looking forward to ideas on the topic.

trigger.bat http://localhost:9300/p2pd/servlet/dispatch usernamepassword namespace databaserefreshtriggername,emailtriggername

Hello Michael,

thank you for bringing this up.

>While those provide some value, the real value would be in triggering a report either based on some event or via a schedule. 
Jason has said this. Use triggered schedules. I can confirm this.

We have seen customer doing so and triggering 50.000+ reports at the end of the month with sales provisions for insurance retails on 100% unix environments (but of course using CLI and host access).

>Would also like to open a discussion in general of what anyone else is using the API for. Seems like it's pretty basic for now.

We have used SDK (SOAP) API extensively for configuring, skinning, deployments, user rights, group rights and testing reports (2.500+ reports with over a hundred parameters in serial) .... everything in Java, tested against CA8+10+11.0+11.1
I would be happy to share code.

We have used Angular + "REST API" for automating almost anything related to report and data retrieval that the portal offers. Presented this in Miami 2018 and  at IBM think 2019 in SF - including authentication, interactive report running, retrieval of save outputs in different formats ending up in Dashboard with First Contentful Paint in less then 0.5s and fully interactive in less then 2s.

Apart of that we automated some features we were missing by recording click paths and re-running them in test automators. I imagine that triggering something would be feasible.

We built quite an extensive testsuite around this and combined it with FOSS test emulators. Testing Querystudio ... create reports, run reports, change sorting, ordering ... Testing cubes: open report on cube, get a cube dimension and test that all expected members are there in the right order ... Would love to share the code and experience.

We have all projects on github in private repos and have asked @Jason Tavoularis, @RACHEL SU and Chris McPerson on going public. Steve Macko was asked to review if we can open the repos to the public. --> topic is loading, we hope to get a positive response soon. In the meantime I would be happy to share details with licenced IBM Cognos users for sure.

In the IBM Cognos usergroup for DACH (Germany, Austria, Switzerland) there is a thread about SDK.​​​ I think it must not be limited to "german".

Ah ... almost forgot the loadtesting plans with jMeter. We have prepared plans with RAMPUP + timing to understand where our environments start queuing in order to calculate expected concurrency and the involved hardware dimensions.

Looking forward to ideas on the topic.