About Service HTTP rules
|
|
| New | Service | Request | Response | History | More.. |
C-2650 5.2 The HTTP integration interface in Process Commander supports interactions between your Process Commander applications and other systems through the HTTP protocol.
Use HTTP services rules when your applications need to process service requests that contain XML or other string data (text) without the need to comply with messaging standards or protocols like SOAP. You can also use HTTP service rules to process HTML POST data submitted to Process Commander from a form.
The content type of the message data sent to a HTTP service rule can
be text or gzip.
A low-overhead stateless alternative to SOAP, Service HTTP rules can implement services in a way that is consistent with REST (Representational State Transfer).
HTTP services generally process service requests synchronously. That is, they immediately perform their requested processing and return a configured response while the calling application waits. However, you can configure HTTP services to process service requests asynchronously, which means the service queues the request for asynchronous execution and the calling application calls back later for the results. Additionally, you can configure synchronous HTTP services to check for specific error conditions that you expect will be temporary — work object locks, for example — and then queue service requests that fail for those reasons for another attempt at a later time.
Use the Application Explorer or the Integration Overview landing page to see Service HTTP rules in your application.
Use the Rules Explorer to list all Service HTTP rules that are
available to you. To access the Integration Overview landing page, select 
> Integration > Overview.
Service HTTP rules belong to the Integration-Services category. A Service HTTP rule is an instance of the Rule-Service-HTTP class.
|
How to unit test a Service HTTP rule |
Integration-Services category
Help Home