Subscriptions

The Apple Push subscriber is a notification subscriber that allows message delivery to an Apple iOS device, such as an iPhone or iPad. The subscriber pushes messages from FME Server to an iOS app installed on the target iOS device by means of a cloud service—the Apple Push Notification Service.

The email protocol allows users to have notifications delivered to an email address or several email addresses. Below is a description of the fields that must be completed by users adding new subscriptions of this type:

• SMTP Server – Mail exchanger server host name or IP address used for sending email.
• SMTP Server Port – Mail exchanger TCP port used for sending email.
• SMTP Account – If the SMTP server requires authentication, this is the user name.
• SMTP Password – If the SMTP server requires authentication, this is the user password.
• SMTP Connection Security- The encryption mechanism used for the connection, if any.
• Email To – Corresponds to the To field in standard email messages.
• Email CC – Corresponds to the CC field in standard email messages.
• Email From – Corresponds to the From field in standard email messages, if users reply to the notification email message it will be directed to this email address.
• Email Subject – Corresponds to the Subject field in standard email messages.
• Email Format - The format of the email, either plain text or HTML.
• Email Content Template – The message body to use for delivery. This is a template that allows the use of various tags that are replaced with dynamic information before delivery. When the message is provided by an FME Server web service, such as the Data Download or Job Submitter service, the following tags are supported:

• {StatusMessage} – The status message of the transformation job that completed.
• {id} – The transformation job’s ID.
• {urlPrefix} – Prefix of the URL used to download any job transformation result files.
• {ResultRootDir} – Root directory fragment part of the URL used to download any job transformation result files.
• {@getFilename(@zip(OutputLocation))} – Retrieves the filename fragment part of the URL used to download any job transformation result files. The result files are compiled into a zip file.

The FTP subscriber receives notifications and uploads files to specified FTP hosts. Below is a description of the fields that must be completed by users adding new subscriptions of this type:

• Host: The FTP host name.
• Port: The FTP port number.
• Username: The FTP user name for authentication.
• Password: The FTP user password for authentication.
• Encryption: The encryption type, depending on the FTP server connection requirements. Options are None, FTPS and FTPES encryption protocols.
• Transfer Type: The transfer method. "Auto" means the FTP subscription will guess the file type of the file being transferred. "ASCII" and "Binary" are available options when the file type is known.
• Destination Path: The destination path to upload the file. File paths must use forward slashes (/) or escaped backslashes (\\).
• Source Path: The path to the source file to upload. Use the Browse tab to select a path in a Resource Management directory. Use the Specify Location tab to enter your own location. File paths must use forward slashes (/) or escaped backslashes (\\). Template macros are supported for this field (see below).
• Zip Source: "Yes" means the source file should be zipped for delivery. "No" means the source file should not be zipped.

The Google Cloud Messaging subscriber is a notification subscriber that allows message delivery to a Google Android device, such as a Samsung Galaxy S3. The subscriber pushes messages from FME Server to an Android app installed on the target Android device by means of a cloud service—the Google Cloud Messaging (GCM) service.

The Java Message System (JMS) subscriber communicates with JMS-compliant message brokers, such as IBM WebSphere MQ.

The logger protocol allows users to have notifications delivered to the FME Server notifications log file.

• Log Level – Determines how detailed the notification message appears in the log file.

  • Low – The log message provides confirmation that a notification message is received.

  • Normal – The log message provides confirmation that a notification message is received and topic name details.

  • High – The log message provides confirmation that a notification message is received, topic name details and all notification content.

The push protocol allows users to have notifications posted to a target URL on the Internet. The result is posted to the URL using an HTTP POST. Below is a description of the fields that must be completed by users adding new subscriptions of this type:

• Target URL – The target URL on the Internet (or in your intranet) to which notifications on the associated topics are delivered to via HTTP POST.
• HTTP Authentication User – If the target URL requires HTTP authentication, this is the user name to use.
• HTTP Authentication Password – If the target URL requires HTTP authentication, this is the user password to use.

The Amazon Simple Storage Service (S3) subscriber uploads objects to an Amazon bucket upon receiving a notification from a Notification Service topic.

1. Bucket: The name of the Amazon SSS bucket to which you want to upload.
2. AWS Access Key ID and AWS Secret Access Key: The security credentials for the Amazon Web Services (AWS) account that owns the Amazon SSS bucket.
3. Encryption: (Optional) When enabled, Amazon S3 server-side encryption encrypts your data using AES-256 as it writes to disk in its data centers.
4. Destination Path: (Optional) If left blank, objects are uploaded to the bucket’s root. If the specified folder does not exist, it is created during the upload. Specify a destination path with forward slashes (/).
5. Source Path: The location of the file/folder to be uploaded. Use the Browse tab to select a path in a Resource Management directory. Use the Specify Location tab to enter your own location. The path must be specified with either forward slashes (/) or escaped backslashes (\\).
6. Zip Source : (Optional) If Yes, the source file is uploaded in compressed .zip form
7. Enable File Versioning: (Optional) Enables/disables versioning for the specified bucket. Leave as “Default” if you do not have permission to set bucket versioning or to maintain the current behavior.

The Amazon Simple Notification Service (SNS) subscriber receives notifications from an FME Server and publishes them to an Amazon SNS topic.

• Topic Amazon Resource Name (ARN) - The ARN of the Amazon Simple Notification Service (SNS) topic.
• AWS Access Key ID and Secret Access Key - The security credentials for the Amazon Web Services (AWS) account that owns the Amazon SNS topic.
• Subject - Optional.
• Notification Content Template - The default message to publish to the Amazon SNS topic. This message can be up to 64 KB of Unicode text.

The Amazon Simple Queue Service (SQS) subscriber sends messages to an Amazon SQS queue upon receiving a notification from a Notification Service topic.

1. SQS Queue URL: The URL of the Amazon SQS queue to which you want to send messages.
2. AWS Access Key ID and AWS Secret Access Key: The security credentials for the Amazon Web Services (AWS) account that owns the Amazon SQS queue.
3. Message Body Template: The default message you want to send to the queue. The message can be up to 64 KB of text in any format.

The WebSocket subscriber receives notifications from the FME Server Notification Service and publishes them over TCP to WebSocket-supported clients that are connected to the FME Server WebSocket server or another target URL.