Questions about ISD with REST 2.0 binding
Posted: Fri Dec 09, 2016 10:03 am
All of our current ISD apps are deployed using SOAP over HTTP and tested using SoapUI. Now I am getting into REST and JSON and have a bunch of questions.
I have deployed a simple test job in ISD with REST 2.0 binding and the GET HTTP Action and have managed to piece together the URL (according to the pattern outlined in the documentation) and was able access it OK, eventually.
1. In the ISD Console when viewing deployed applications, with the app expanded and the service selected, there is an empty field called URL. Why is the URL empty, and when you click the View button next to it, why does nothing happen? Are these the expected behaviors? I was hoping to get the URL from here instead of manually piecing it together.
2. I have deployed the REST 2.0 test without having selected confidentiality for https. I found that using http:// in the URL leads to an IE error that the page cannot be displayed. If I use https:// prefix then it works. But I did not enable https. Why the surprise here?
3. When testing using the org's standard web browser, IE11, every test prompts with a pop up about what to do with the results - open or save. Open pops up the results in a new window, like Notepad. What are some more efficient ways to test and view the results?
4. Has anyone got suggestions for useful naming conventions on the ISD applications, services, and operations? Our existing ones are quite lengthy and difficult to look at. What might a user-friendly one look like?
Thank you!
I have deployed a simple test job in ISD with REST 2.0 binding and the GET HTTP Action and have managed to piece together the URL (according to the pattern outlined in the documentation) and was able access it OK, eventually.
1. In the ISD Console when viewing deployed applications, with the app expanded and the service selected, there is an empty field called URL. Why is the URL empty, and when you click the View button next to it, why does nothing happen? Are these the expected behaviors? I was hoping to get the URL from here instead of manually piecing it together.
2. I have deployed the REST 2.0 test without having selected confidentiality for https. I found that using http:// in the URL leads to an IE error that the page cannot be displayed. If I use https:// prefix then it works. But I did not enable https. Why the surprise here?
3. When testing using the org's standard web browser, IE11, every test prompts with a pop up about what to do with the results - open or save. Open pops up the results in a new window, like Notepad. What are some more efficient ways to test and view the results?
4. Has anyone got suggestions for useful naming conventions on the ISD applications, services, and operations? Our existing ones are quite lengthy and difficult to look at. What might a user-friendly one look like?
Thank you!