Service Dependencies
The In-app service uses or is used by a several other services in the Emarsys realm. On this page we’ll list them and their related configuration.
Uses
Msg-generator Service
The mobile engage msg-generator service is used by in-app to deliver push-notifications when testing an overlay message. This is done using a synchronous endpoint to make sure that we receive any error that might occur during delivery.
The client is being used in test-message-sender.
RTI Service
When cancelling an In-app campaign we use the RTI-service to verify that it’s not being used in an active program to avoid errors in the program.
See event-center-client for how it’s being used in in-app.
Personalization-Sync-Adapter Service
For In-app campaigns using any kind of personalization that needs to be evaluated by the personalization-service before shown to the user we register the template and save the id so that the device-event-service can use this id and evaluate the message.
Configuration
| Config | Default | Comment |
|---|---|---|
PERSONALIZATION_SYNC_ADAPTER_BASE_URL |
URL without path part |
|
PERSONALIZATION_SYNC_ADAPTER_ESCHER_KEYID |
mobile-engage_personalization-sync-adapter_v1 |
|
PERSONALIZATION_SYNC_ADAPTER_ESCHER_SECRET |
See staging, production |
|
PERSONALIZATION_SYNC_ADAPTER_ESCHER_CREDENTIAL_SCOPE |
eu/personalization-sync-adapter/ems_request |