ESP Web Services Provider

The ESP Web Services Provider receives data from a Web service client and publishes it to an ESP stream or window within an ESP project. It supports both Representational State Transfer (REST) and SOAP services.

Install and configure your own Web service client for SOAP or REST before configuring and using the ESP Web Services Provider. You can expose an ESP project as a Web service, and send requests to it using your Web service client.

The SOAP provider sends and receives SOAP messages in XML format over HTTP. Use a SOAP Web service client to send Web service SOAP requests to the SOAP provider and invoke Web service functions, such as publish, in the ESP project that has been exposed as a Web service.

The REST provider sends REST requests in JSON format over HTTP. Use a REST Web service client to send REST requests to the REST provider and publish data to an ESP project that has been exposed as a Web service. See REST Requests for Streams and Windows and REST Requests for Life cycle Management of a Project for additional details on using REST requests to communicate with an ESP project.

For installation details for the provider, see the section on Performing a Custom Installation in the SAP Sybase Event Stream Processor Installation Guide. If you enabled the ESP Web Services Provider using the installer, the configuration is complete and the provider is ready for use. If you did not enable the provider using the installer, see Configuring the ESP Web Services Provider for instructions on manually configuring the provider.

For instructions on exposing a project as a Web service, see Exposing a Project as a Web Service Using the ESP Web Services Provider in the SAP Sybase Event Stream Processor Studio Users Guide.

• Configuring the ESP Web Services Provider
  Use the esp_wsp.xml and axis2.xml configuration files to configure the ESP Web Services Provider.
• Customizing Input Formatting of REST Requests
  Customize the formatting of the input content of REST requests by replacing the existing stream resource jar file with your own implementation. You may wish to do this for several reasons. For example, you may wish to use different formatting for HTTP requests if you have incoming events in your system that have a different or more complex structure, such as nested or structured events. Or you may have an initialization process that you need to execute when the Web Services Provider server first starts up. Or finally, you may want to control the connection and publishing of events to Event Stream Processor.
• Accessing REST API Reference Information
  API documentation for the REST Web Services Provider.
• REST Requests for Streams and Windows
  There are various REST requests (in JSON format) provided with the REST provider that you can use to publish, update, upsert, and delete records from ESP streams or windows.
• REST Requests for Life Cycle Management of a Project
  There are various REST requests (in JSON format) provided with the REST provider that you can use to deploy, start, update, stop, and remove an ESP project.