These docs are for v20.3.44. Click to read the latest docs for v20.3.186.

Discussions

Ask a Question
Back to All

How to inspect Rest calls made by Rise to learn by example

It would be valuable for developers to be able to view the Rest calls that a Rise page makes to understand how ASI is using Rest on a page to view, save or update data. Then, rather than having to request on the forum each time for an example of how a given call should be made we could just inspect the page's behavior to learn more about the calls. This would allow developers to move forward more quickly to cloud friendly development without relying on ASI to publish examples of all the calls we need to make.

To attempt this, I set up fiddler as a proxy server (hat tip to Jake) that inspects all traffic to the scheduler service and then forwards it on to the scheduler. After configuring fiddler and IIS I am able to see imis making some calls to the rest service. These calls are being made by the w3wp process (not the browser) so it looks like I am successfully intercepting calls made by the Rise server side code. I'm able to see lots of calls that we don't have samples for yet which is exactly what I was hoping for.

The challenge is that there aren't enough calls being made to render all the data on the screen. For example, on page "CertificationManagement/CertificationProgram.aspx" there is data on the page retrieved server-side that would require a call to the CertificationProgram endpoint if the page was using Rest. But the only calls I'm seeing to rest are some calls to /token /authorizationprovider /vactivetranslationcultures. No calls are being captured to /CertificationProgram endpoint. That indicates to me that one of the following are true.

  1. Not all data access calls are going through the scheduler endpoint. Some of the data access calls are still being filled other ways (SOA, SQL, ibo, etc...). This is contrary to my understanding that Rise was now using Rest almost exclusively for all calls.
  2. Some of the calls are being routed to rest using some other route than what is configured in the "EntityManagerDefaultBaseUri" setting from the web.config and I'm not capturing them.
  3. Maybe I am have managed to configure fiddler in a way that would capture some of the calls, but not all.

Could ASI provide some clarity on whether all/most data access calls in Rise are now being filled by rest and could this method be a viable way to capture more examples of how to use Rest until ASI is able to publish more in the SDK?