The HTTP Utility has built in intelligence and allows users to use Neuron ESB Environmental Variables, Neuron ESB Message properties, Context properties and literal values to configure any Value, Message body or URL as shown below:
![swagger editor json demo swagger editor json demo](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/6025978490/original/blob1466807191530.png)
Users can select “Configure” from the context menu to display the main configuration screen of the HTTP Utility as shown below:įor users familiar with tools like “Postman” and the REST client of Chrome, the HTTP Utility will look very similar and they will find it just as easy to configure. The HTTP Utility is exposed as both a Process Step and Workflow Activity that can be dragged onto either designer. This utility can be used within the Business Process or Workflow Designer to do more advanced levels of HTTP configuration. Rather than requiring that developers use C# to set HTTP properties, CU4 introduces a new tool, the “HTTP Utility”.
SWAGGER EDITOR JSON DEMO CODE
The example below shows how Query string parameters could be set in a Code Editor in the Workflow Designer. The information used to initialize these HTTP elements could come from the existing Neuron ESB Message, Neuron ESB Message or context properties or even Neuron ESB Environmental Variables that may have different values at runtime depending on the runtime environment they are deployed to. Opening the C# Code Editor allowed developers to provide the information they needed to initialize the service call at runtime by primarily using the HTTP object of the Neuron ESB Message as shown below. In previous versions of Neuron ESB, this information could be provided by using a C# Code Editor within either the Business Process Designer or Workflow Designer directly preceding the Service Endpoint activity as depicted below:
![swagger editor json demo swagger editor json demo](https://senya.io/app/uploads/2018/05/senya-swagger-ui-demo-200.gif)
Content Type, Authorization, Accept, etc.) as well as Query string or URL parameters. HTTP Headers usually need to be provided (e.g. GET, POST, PUT, PATCH, etc.) must be provided. These are commonly used to create service aggregation and composition solutions.įor calling REST (HTTP) based Service Connectors (endpoints), it’s not uncommon that various pieces of information need to be provided at runtime according to the REST specification. The latter two options can be used with either the Neuron ESB Workflow Designer or the existing Business Process Designer and allows a user to directly call any Service Connector without the need to publish a request to a Topic, eliminating all pub/sub overhead. These services, which can be either SOAP or REST (HTTP) based, can be called either through the Neuron ESB messaging system via a Topic subscription or by using a Service Endpoint Workflow Activity and Process Step.
![swagger editor json demo swagger editor json demo](https://tomjohnson1492.gitbooks.io/documenting-rest-apis/content/images_api/swaggerpetstoreui.png)
Service Connectors are essentially registrations within Neuron ESB that point to existing services hosted within an organization, by a partner or in a cloud domain. Neuron ESB includes a Service Broker that enables organizations to deploy Neuron ESB as a Service Gateway, providing mediation, security, hosting and a number of other services.