Page History

Sometimes getting a taste of success is all that's need to charge ahead and make technology magic. Therefore, before diving in and creating new APIs, let's make sure that the default APIs are responding correctly to incoming requests.

...

Before we get too eager to test our APIs, let's make sure we have the Engine Server running. Otherwise our testing will fail quite abruptly with . If using a browser, this usually results in a connection time out response (if using a browser) or a page. If using an API test utility like Postman, you'll see a message like "Unable to connect to Engine Server localhost:8088 - The attempt to connect was forcefully rejected." type of message (if using an API test utility like Postman)

The 103-966 OpenInsight OEngineServer Configuration.pdf document provides thorough instructions for installing the Engine Server as a true Windows service as well as how to launch it from a command prompt (aka "debug" mode). We recommend starting out by running the Engine Server from a command prompt since developers will need access to the OpenInsight Debugger when writing and troubleshooting their web APIs.

It is possible to test the SRP HTTP Framework without having to go through the effort of creating any APIs. This will not guarantee that all possible configuration details have been properly updated, but at this point we just want to make sure that HTTP requests are getting received by the SRP HTTP Framework and a proper response is being sent back.

...