A protocol is a system of data exchange between FME Server and a client.

We already know that FME sends and receives notifications. Protocols are the method by which these notifications are sent and received. Each Publication and Subscription is defined using a particular communication protocol.

To trigger a Publication by email – for example – you would use the Email protocol. To send a notification to subscribers with an Apple mobile device, you would use the Apple Push protocol.

There are many different protocols available in FME Server; some of them are only for use on Publications, some are only for Subscriptions, and some of them can be used with both notification types.

This table lists the different Publication and Subscription protocols and the following pages go into detail on some of the most important.

Amazon S3Communication with Amazon’s Simple Storage ServiceYY
Amazon SNSCommunication with Amazon’s Simple Notification ServiceYY
Amazon SQSCommunication with Amazon’s Simple Queue ServiceYY
Apple Push NotificationCommunication with Apple mobile devicesY
Directory WatchMonitoring a folder for new files as a trigger mechanismY
Dropbox WatchLike Directory Watch, but monitoring folders stored in the Dropbox web serviceY
DropboxCommunication of a notification (file) to the Dropbox web serviceY
Email (IMAP)Communication via an email serviceY
Email (SMTP)Communication via an email serverYY
FTP/SFTP/FTP WatchCommunication with an FTP siteYY
Google Cloud MessagingCommunication with Android mobile devicesY
JMSCommunication with a Java Message ServiceYY
LoggerOutput to a simple log fileY
PushCommunication via HTTP requestsY
UDPCommunication via a User Datagram Protocol portY
WebSocketsCommunication via a WebSockets channelYY
WorkspaceCommunication of notifications to an FME workspaceY

The Dropbox subscription and Dropbox Watch publication protocols are new for FME2016.1

Protocols are pre-defined components in the FME Server architecture and do not need to be defined in the Web User Interface.

However, a number of fields are made available to configure them when a Publication or Subscription chooses to make use of that protocol.

For example, here are the parameters for an Amazon SQS Subscription:

These parameters must be set when the Subscription is created as they are needed in order to be able to send out a notification using the protocol.

Miss Vector says...
Tell me, which one of these statements is correct:

1. SMTP and IMAP can both be used as either a Subscription and/or a Publication protocol
2. SMTP can be used as both a Subscription and a Publication; IMAP can only be used for a Publication
3. SMTP can only be used for a Publication; IMAP can only be used as both a Subscription and a Publication
4. SMTP can only be used for a Subscription; IMAP can only be used for a Publication

results matching ""

    No results matching ""