Class EventProcessingRegistration
java.lang.Object
com.mparticle.sdk.model.registration.EventProcessingRegistration
The EventProcessingRegistration object should be constructed by Firehose integrations that wish to function
as event-integrations within the mParticle platform. Upon receiving a
ModuleRegistrationRequest
,
it's up to the Firehose integration to response with a populated ModuleRegistrationResponse
.-
Constructor Summary
-
Method Summary
Modifier and TypeMethodDescriptionGets the account-level settings registered by this integration.Gets the subscription-level settings registered by this integration.int
Get the push messaging provider ID.setAccountSettings
(List<Setting> accountSettings) Register the account-level settings of this integration.setAuthentication
(AuthenticationConfiguration authentication) setConnectionSettings
(List<Setting> connectionSettings) Register the specific connection-level settings of this integration.setMaxDataAgeHours
(int maxDataAgeHours) setPushMessagingProviderId
(String pushMessagingProviderId) Set the push messaging provider ID.setSupportedEventTypes
(List<Event.Type> supportedEventTypes) setSupportedRuntimeEnvironments
(List<RuntimeEnvironment.Type> supportedRuntimeEnvironments) setSupportedSystemNotifications
(List<SystemNotification.Type> supportedSystemNotifications)
-
Constructor Details
-
EventProcessingRegistration
public EventProcessingRegistration()
-
-
Method Details
-
getAccountSettings
Gets the account-level settings registered by this integration. mParticle integrations may be configured with two different sets of settings: - Account-level settings, meant to be reused across platforms and/or apps - Subscription-level settings, meant to change specific behaviors for each instance of an output/integration As a Firehose integration developer, it's up to *you* to define which settings should be account-level, and which should be configured on a per-integration-instance basis.- Returns:
- account settings registered by the integration
- See Also:
-
setAccountSettings
Register the account-level settings of this integration. mParticle integrations may be configured with two different sets of settings: - Account-level settings, meant to be reused across platforms and/or apps - Subscription-level settings, meant to change specific behaviors for each instance of an output/integration As a Firehose integration developer, it's up to *you* to define which settings should be account-level, and which should be configured on a per-integration-instance basis.- Parameters:
accountSettings
- account-level settings to register for this integration- Returns:
- returns this EventProcessingRegistration object for method chaining
- See Also:
-
getConnectionSettings
Gets the subscription-level settings registered by this integration. mParticle integrations may be configured with two different sets of settings: - Account-level settings, meant to be reused across platforms and/or apps - Subscription-level settings, meant to change specific behaviors for each instance of an output/integration As a Firehose integration developer, it's up to *you* to define which settings should be account-level, and which should be configured on a per-integration-instance basis.- Returns:
- account settings registered by the integration
- See Also:
-
setConnectionSettings
Register the specific connection-level settings of this integration. mParticle integrations may be configured with two different sets of settings: - Account-level settings, meant to be reused across platforms and/or apps - Connection-level settings, meant to change specific behaviors for each instance of an output/integration As a Firehose integration developer, it's up to *you* to define which settings should be account-level, and which should be configured on a per-integration-instance basis.- Parameters:
connectionSettings
- subscription-level settings to register for this integration- Returns:
- returns this EventProcessingRegistration object for method chaining
- See Also:
-
getSupportedEventTypes
- Returns:
- requested event types
-
setSupportedEventTypes
- Parameters:
supportedEventTypes
- requested event types- Returns:
- returns this EventProcessingRegistration object for method chaining
-
getMaxDataAgeHours
public int getMaxDataAgeHours()- Returns:
- acceptable age of the incoming events
-
setMaxDataAgeHours
- Parameters:
maxDataAgeHours
- acceptable age of the incoming events- Returns:
- returns this EventProcessingRegistration object for method chaining
-
getSupportedRuntimeEnvironments
- Returns:
- supported mobile platforms
-
setSupportedRuntimeEnvironments
public EventProcessingRegistration setSupportedRuntimeEnvironments(List<RuntimeEnvironment.Type> supportedRuntimeEnvironments) - Parameters:
supportedRuntimeEnvironments
- supported mobile platforms- Returns:
- returns this EventProcessingRegistration object for method chaining
-
getSupportedSystemNotifications
-
setSupportedSystemNotifications
public EventProcessingRegistration setSupportedSystemNotifications(List<SystemNotification.Type> supportedSystemNotifications) -
getPushMessagingProviderId
Get the push messaging provider ID. The push messaging provider ID is required as a security measure to ensure that integrations only receive push receipts originally sent by their service. For example, the company Acme Inc., when sending a push notification to either Apple's push messaging service or Google GCM/FCM, must include a unique key, such as "acme-id", within the payload of the push message. In that case, Acme Inc., should register for a push messaging provider id of "acme-id". When forwarding push message receipts, the mParticle platform will only send push receipt messages that contain your push messaging provider id to your Firehose integration.- Returns:
-
setPushMessagingProviderId
Set the push messaging provider ID. The push messaging provider ID is required as a security measure to ensure that integrations only receive push receipts originally sent by their service. For example, the company Acme Inc., when sending a push notification to either Apple's push messaging service or Google GCM/FCM, must include a unique key, such as "acme-id", within the payload of the push message. In that case, Acme Inc., should register for a push messaging provider id of "acme-id". When forwarding push message receipts, the mParticle platform will only send push receipt messages that contain your push messaging provider id to your Firehose integration.- Parameters:
pushMessagingProviderId
-- Returns:
-
getAuthentication
- Returns:
- authentication
-
setAuthentication
- Parameters:
authentication
- event authentication settings- Returns:
- this
-