• All Files

HTTP Request Subscriber

The HTTP Request subscriber receives notifications from topics and posts HTTP request to the specified URL.

In the FME Server Web User Interface, select Notifications > Subscriptions, and click New.

  • Request Type: The type of HTTP request: GET, DELETE, PUT, or POST.
  • Target URL: The URL to which notifications on the associated topics are delivered.
  • HTTP Authentication User Name: The user name, if the target URL requires HTTP authentication.
  • HTTP Authentication Password: The user password, if the target URL requires HTTP authentication.
  • Accept Header: Format of the Accept request HTTP header: JSON, XML, or Text.
  • Content Type: The format in which to deliver content: JSON, XML, or Text.
  • Post to Topics(s) on Success/Failure: These fields apply only to an HTTP Request subscriber that is auto-created when an FME Workbench workspace is published to FME Server, registered to the Notification Service, and topics are specified to which the workspace publishes notification content when a transformation succeeds or fails. In FME Workbench, these topics are specified on the Edit Service Properties dialog of the Publish to FME Server wizard, and also appear here.
  • Verify SSL Certificate: If Yes, the connection to the specified Target URL is verified with a valid, signed SSL certificate. If No, the connection is not verified with an SSL certificate. This option is not secure and not recommended unless absolutely necessary, such as when using a self-signed certificate.
  • HTTP  Body: The message body content. If specified, this message replaces the incoming message body.

Keywords

  • push_url
  • push_content_format
  • push_content_encoding
  • subscriber_content

HTTP Request Notification Content

An FME Server notification stores the message content in keyword/value pairs. If the subscriber receives a notification consisting of only one keyword/value pair, it will send the value as the request body. Otherwise, it will format all the keywords and values into JSON or XML based on subscriber.

For example, the notification below will be delivered as value only:

subscriber_content: "This is my notification message"

The request body will be "This is my notification message".

Another notification consisting of multiple keyword/value pairs will be delivered as JSON or XML:

{

"foo": "value 1",

"bar": "value 2"

}

Or:

<?xml version="1.0" encoding="UTF-8"?>

<content>

<foo>value 1</foo>

<bar>value 2</bar>

</content>