REQUIREMENTS
1) BESNG On-Prem must continue to support the BES10 Push Service for BB10. The Push Service is to be supported in such a way that any deployed Enterprise applications will not need to be changed and/or re-compiled to continue to use the Push service. In other words, the migration from BES10 push support to BESNG On-Prem push support is to be seamless for existing, deployed applications.
2) Enterprise Push service is to be supported with all applicable BESNG Secure Connectivity solutions (eg. Relay, P2E). More specifically, Blackcomb is to continue to support the Push service regardless of whether the Enterprise uses Relay/MDS-CS or P2E as their secure connectivity solution for BB10 devices.
3) Enterprise Push must remain as secure and encrypted as it is currently ie. Enterprise Push currently is transported over MDS-CS which provides a secure channel for these Push messages.
Note the current push 8KB data limit is expected to remain with the BESNG implementation.
Push Overview Information:
BlackBerry MDS Connection Service connects apps on devices to push applications, which are applications on your organization's application servers or web servers that push data to apps on devices. After an app is installed on a device, the app can receive data from push applications. This capability is called the Enterprise Push service.
The Push service enables Enterprise developers and third party developers to develop applications that can "push" this data to a device and app as required.
BES10 (BDS) and BB10 support the Enterprise Push service. The Push service has been available for a number of years and there are Enterprise applications and Enterprises that actively use this service.
Key Use Cases:
1) Open Text Livelink BB application on device is able to receive Workflow notifications from the Open Text Livelink server through the use of the Push service. The notification is sent by the OT Livelink server to the BES10, which sends the message on to the device using the Push service.
Business Justification:
1) Enterprise push is part of overall BlackBerry enterprise value proposition.
2) Enterprise push is currently used by various Enterprises with applications already developed by Enterprises/3rd Parties
3) For those Enterprises that use apps with the push service, not supporting these applications on BESNG will be a barrier to upgrade to BESNG
REQUIREMENTS
1) BESNG On-Prem must continue to support the BES10 Push Service for BB10. The Push Service is to be supported in such a way that any deployed Enterprise applications will not need to be changed and/or re-compiled to continue to use the Push service. In other words, the migration from BES10 push support to BESNG On-Prem push support is to be seamless for existing, deployed applications.
2) Enterprise Push service is to be supported with all applicable BESNG Secure Connectivity solutions (eg. Relay, P2E). More specifically, Blackcomb is to continue to support the Push service regardless of whether the Enterprise uses Relay/MDS-CS or P2E as their secure connectivity solution for BB10 devices.
3) Enterprise Push must remain as secure and encrypted as it is currently ie. Enterprise Push currently is transported over MDS-CS which provides a secure channel for these Push messages.
Note the current push 8KB data limit is expected to remain with the BESNG implementation.
Push Overview Information:
BlackBerry MDS Connection Service connects apps on devices to push applications, which are applications on your organization's application servers or web servers that push data to apps on devices. After an app is installed on a device, the app can receive data from push applications. This capability is called the Enterprise Push service.
The Push service enables Enterprise developers and third party developers to develop applications that can "push" this data to a device and app as required.
BES10 (BDS) and BB10 support the Enterprise Push service. The Push service has been available for a number of years and there are Enterprise applications and Enterprises that actively use this service.
Key Use Cases:
1) Open Text Livelink BB application on device is able to receive Workflow notifications from the Open Text Livelink server through the use of the Push service. The notification is sent by the OT Livelink server to the BES10, which sends the message on to the device using the Push service.
Business Justification:
1) Enterprise push is part of overall BlackBerry enterprise value proposition.
2) Enterprise push is currently used by various Enterprises with applications already developed by Enterprises/3rd Parties
3) For those Enterprises that use apps with the push service, not supporting these applications on BESNG will be a barrier to upgrade to BESNG
การแปล กรุณารอสักครู่..