Installation guide

Install a BlackBerry MDS Integration Service pool in an upgraded environment
When you install new BlackBerry® MDS Integration Service instances in an upgraded environment instead of upgrading existing
BlackBerry MDS Integration Service instances, you lose backend notification subscriptions. BlackBerry devices that run
BlackBerry® MDS Runtime Application versions earlier than version 4.5 remove the applications.
1. Install all BlackBerry MDS Integration Service instances in the pool.
2. Publish all existing BlackBerry MDS Runtime Applications.
3. Install all BlackBerry MDS Runtime Applications on a test BlackBerry device.
4. To migrate users from BlackBerry MDS Integration Service version 4.1 to the new BlackBerry MDS Integration Service pool,
in the BlackBerry Administration Service, update the BlackBerry Enterprise Server to associate with the new BlackBerry
MDS Integration Service pool.
After you finish:
• Configure backend notification subscriptions.
• Resend applications to BlackBerry devices that run BlackBerry MDS Runtime Application versions earlier than version 4.5.
• For more information, see the BlackBerry Enterprise Server Installation Guide.
Change applications to support BlackBerry MDS Connection Service failover
In earlier versions of the BlackBerry® Enterprise Server, an organization's push applications connected to only one instance of
the BlackBerry MDS Connection Service central push server. You must make sure that your organization's applications can access
all central push servers.
1. Change the applications to access central push servers only, and not BlackBerry MDS Connection Service instances that
administrators have not configured to also act as central push servers.
2. To change your organization's applications to support central push server failover, perform one of the following actions:
• Configure an HTTP or HTTPS proxy server that applications send requests through. Use this option if the applications
are located on the Internet. Optionally, you can place the proxy server in the DMZ.
• Configure the application servers to use a list of IP addresses to find an available central push server. If a central push
server does not respond to a request, the application can try to connect to another central push server.
• Configure a hardware load balancer such as the BIG-IP® load balancer. The load balancer accepts all requests from the
application servers, and distributes the traffic to the various central push servers. If a central push server does not respond,
the load balancer redistributes the requests to the remaining central push servers.
• Configure the application to use the new HTTP response header x-rim-push-gateways.
Upgrade Guide
Change applications to support BlackBerry MDS Connection Service failover
51