“EIS Managed” indicates that the EIS initiates the
connection to SAP Mobile Server to
retrieve updates. When “Notify EIS to Fetch Operation” is selected,
SAP Mobile Server sends a
notification to the EIS to inform the availability of the updates.
However, the EIS is still responsible to fetch the operations from
SAP Mobile Server using the HTTP
interface.
Note: SAP Mobile Server does not guarantee notifications are
delivered in order. It is possible that the "upload" notifications
are sent to the EIS out of order if clients are uploading multiple
times before the EIS is able to process any of the generated
"upload" notifications. It is also possible that the EIS receives
the same notification twice due to HTTP usage as the delivery
protocol. Duplicate notification is not considered harmful since
each operation contains an identifier, but the EIS may want to
implement logic that does not react to a notification if it is a
duplicate.
When “Notify EIS to Fetch Operation” is not
selected, the EIS still fetches the operations from SAP Mobile Server. The difference is that the
schedule to fetch is EIS determined and not configured in SAP Mobile Server.
Run-time mapping: you must map the REST Web
service development connection profile to a run-time connection to which
notifications are sent. You can do this either:
- During package deployment – when deploying the package to the SAP Mobile Server, select the REST
Web service connection to which you are mapping, if one
exists, or <New Server
Connection...> to create a new one from
the Server Mapping Connection screen.
- From SAP Control Center – any EIS connections defined here, display
during package deployment.
Note: If the Web service pointed to by the REST
connection profile requires HTTP authentication, supply the
credentials (for example, the technical user name and password) when
mapping or creating the run-time connection profile. SSO is not
supported.