This Blog entry is from the Getting Started in Jube section in Learn Jube.
Integration can of course be accomplished by any tool or programming framework that facilitates HTTP interactions with a web server (e.g. .Net, Java, PHP etc). For testing it is quite common to use a HTTP Post Tool, Utility or Client application. Jube has created a page to support manual testing of HTTP messaging in the application, called Postman.
To navigate to Postman, navigate through the the menus Administration >>> HTTP Post Tools >>> Postman:
The Postman page will be presented:
There are three input parameters worthy of discussion in this Blog entry, keeping in mind that subsequent Blog entries will set about posting to the pre-configured models. The first parameter is represented as radio buttons and select the format of the message to be posted:
The Format option has no bearing on the message being submitted to the server via HTTP and only serves to tell the page how to format the input in the code editor, which affords certain parsing and formatting in the input box.
The second parameter is the URL that the message is to be posted to, which hard codes the Jube https://api.jube.io endpoint and query string delimiter, then expects only querystring parameters separated by the & character:
The final parameter is the Request body, which accepts ether XML or JSON to be posted to the endpoint alongside the querystring parameters:
An important consideration when deciding to use the embedded utility over another tool is that all requests and responses are logged to a database available to Jube support staff. Should any requests not behave as expected, then Jube support can provide more timely intervention having access to the messages and internal error messages.
As mentioned, there are several pre-configured models which exist for the purposes of training and integration testing and comprise the content of several subsequent Blog entries.