Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
46 views7 pages

BES Repoint Instructions

BBSE BlackBerry Enterprise Server Migration Switch to Production Infrastructure. Document outlines requirements and steps required to migrate a BES to production infrastructure.

Uploaded by

Ali Raza
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
46 views7 pages

BES Repoint Instructions

BBSE BlackBerry Enterprise Server Migration Switch to Production Infrastructure. Document outlines requirements and steps required to migrate a BES to production infrastructure.

Uploaded by

Ali Raza
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

BBSE BlackBerry Enterprise Server Migration Switch to Production Infrastructure

Version 3.1 Document ID: 6704576

2.0 For RIM internal use only. Not for external distribution except parties covered by the Non Disclosure agreement.

2007 Research In Motion Limited. All rights reserved.

www.rim.com

Revision History
Date 2005, Oct, 26 2005, Jan, 13 2006, Sep, 12 2007, Feb, 06 Version 1.0 2.0 3.0 3.1 Author Ricardo Torrijos Nicholas Wiles Nicholas Wiles N.Wiles Description Initial document. Changes to wording and inclusion of EMEA details. Updated to match 4.0.3 onwards and 4.1 BES Updated. Including KB Articles for clarification on country codes. Updated link to KB Articles and SRP Address

2007 Research In Motion Limited. All rights reserved.

www.blackberry.com

BBSE BlackBerry Enterprise Server Migration to Production Infrastructure 3 of 7

Contents
1 2 3 4 Introduction................................................................................................................. 4 Requirements ............................................................................................................. 4 Migration..................................................................................................................... 4 Alternative SRP Addresses ........................................................................................ 6

For distribution under Non Disclosure Agreement.


Last saved: 06/02/2007 www.rim.com

BBSE BlackBerry Enterprise Server Migration to Production Infrastructure 4 of 7

1 Introduction
During the process of launching BlackBerry, you might be asked to switch your BlackBerry Enterprise Server (BES) to the Production Infrastructure. This document outlines the requirements and steps required to migrate a BES to Production Infrastructure. Detailed reference to the BlackBerry Enterprise Server, SRP addresses and troubleshooting can be found in the BES Guides at this link: http://www.blackberry.com/support/documentation/server/index.shtml

2 Requirements
Prior to perform the BES migration to the Production Infrastructure, the following requirements must be met: 1- You must have completed and sent us a brief Device Testing document called the User Acceptance Tests (UAT). This ensures that you can register the BlackBerry on the network, send PIN-to-PIN messages from BlackBerry, and use the BlackBerry successfully on your network. 2- Complete the Working Level Procedure (WLP) document. 3- Complete the NOC-to-NOC Communications Test. 4- You must have received a confirmation by Partner Launch Manager (PLM) of your Production Provisioning setup and understood the new setup of your SIMs and services. 5- Agreed a migration cutover date for the Infrastructure changes (considering Change Management guidelines) and changes to VPN and network infrastructure have been confirmed by the CSM team at RIM and your network team. 6- You must have opened the firewall port 3101 for the new correct IP Address if necessary. See sections 3 and 4 below for more information.

3 Migration
This section describes the necessary steps to switch your BlackBerry Enterprise Server from External Test Infrastructure (srp.etr.blackberry.net) to RIM Production Infrastructure which has a different SRP address. These steps apply to all types of BlackBerry Enterprise Server; Microsoft Exchange, IBM Lotus Domino, and Novell GroupWise. Prior to performing the migration of your server; please ensure that you comply with the requirements listed in section 2. 1. Shut down the BlackBerry Services in the BlackBerry Manager or Windows Services applications. You can shut down just the BlackBerry Router and BlackBerry Controller if you prefer. 2. Launch the BlackBerry Server Configuration Panel by going to Control Panel BlackBerry Server Configuration. A similar BlackBerry Configuration Panel will be

For distribution under Non Disclosure Agreement.


Last saved: 06/02/2007 www.rim.com

BBSE BlackBerry Enterprise Server Migration to Production Infrastructure 5 of 7 launched similar to the one displayed below:

3. Select BlackBerry Router tab. 4. In SRP Address field, enter the SRP Address of the new Production Infrastructure SRP that you received from RIM. E.g. srp.na.blackberry.net for North America, srp.ap.blackberry.net for Asia Pacific, srp.eu.blackberry.net for Europe (EMEA). Please see section entitled Alternative SRP Addresses below for further information. 5. Leave the Port field as it was before e.g. 3101. 6. Click Test Network Connection button and verify you can successfully connect to the production Infrastructure. Error numbers can be found in the BES Guides. 7. Click the OK button to confirm your change. 8. Restart all the services you shut down before, ensure that the following Windows services are running: BlackBerry Router and BlackBerry Controller 9. Register each BlackBerry handheld on the new network by performing a Register Now from the Host Routing Table in the handheld Options menu. Billing and SIM Provisioning should now be effective and can be managed by your Provisioning team.

For distribution under Non Disclosure Agreement.


Last saved: 06/02/2007 www.rim.com

BBSE BlackBerry Enterprise Server Migration to Production Infrastructure 6 of 7 10. You should now be able to confirm a PIN to PIN message from two handhelds and also that Email is flowing between the BES and the BlackBerry handhelds within half an hour of starting all the BES services.

4 Alternative SRP Addresses


Each country has been allocated a similar unique address which works exactly the same as srp.eu.blackberry.net, srp.ap.blackberry.net or srp.na.blackberry.net addresses mentioned above. They all use the Production Infrastructure. You can use the eu, ap or na address or the country code address with the same result, as long as you are in that area. The PING command can confirm the IP Address for each name. See the BES Guides too if necessary. This Knowledge Base Article will help with the IP Address and the Country Codes. By default the BES install will provide you with your SRP address based on your country. You must have opened the firewall port 3101 for the new correct IP Address if necessary. The link below refers to the IP Address and country code on the RIM production network: https://www.blackberry.com/SRPAddressLookup/ The process for changing the SRP Address is similar if the BlackBerry Router has been installed separately to the BES itself, perhaps in the DMZ of your organisation.

For distribution under Non Disclosure Agreement.


Last saved: 06/02/2007 www.rim.com

BBSE BlackBerry Enterprise Server Migration to Production Infrastructure 7 of 7

2007 Research In Motion Limited. All rights reserved. The BlackBerry and RIM families of related marks, images and symbols are the exclusive properties and trademarks of Research In Motion Limited. RIM, Research In Motion, 'Always On, Always Connected' and BlackBerry are registered with the U.S. Patent and Trademark Office and may be pending or registered in other countries. The BlackBerry handheld and/or associated software are protected by copyright, international treaties, and various patents, including one or more of the following U.S. patents: 6,278,442; 6,271,605; 6,219,694; 6,075,470; 6,073,318; D445,428; D433,460; D416,256. Other patents are registered or pending in various countries around the world. Visit www.rim.com/patents.shtml for a current listing of applicable patents. This document is provided as is and Research In Motion Limited (RIM) assumes no responsibility for any typographical, technical, or other inaccuracies in this document. RIM reserves the right to periodically change information that is contained in this document; however, RIM makes no commitment to provide any such changes, updates, enhancements, or other additions to this document to you in a timely manner or at all. RIM MAKES NO REPRESENTATIONS, WARRANTIES, CONDITIONS, OR COVENANTS, EITHER EXPRESS OR IMPLIED (INCLUDING, WITHOUT LIMITATION, ANY EXPRESS OR IMPLIED WARRANTIES OR CONDITIONS OF FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, MERCHANTABILITY, DURABILITY, TITLE, OR RELATED TO THE PERFORMANCE OR NONPERFORMANCE OF ANY SOFTWARE REFERENCED HEREIN, OR PERFORMANCE OF ANY SERVICES REFERENCED HEREIN). IN CONNECTION WITH YOUR USE OF THIS DOCUMENTATION, NEITHER RIM NOR ITS AFFILIATED COMPANIES AND THEIR RESPECTIVE DIRECTORS, OFFICERS, EMPLOYEES, OR CONSULTANTS SHALL BE LIABLE TO YOU FOR ANY DAMAGES WHATSOEVER BE THEY DIRECT, ECONOMIC, COMMERCIAL, SPECIAL, CONSEQUENTIAL, INCIDENTAL, EXEMPLARY, OR INDIRECT DAMAGES, EVEN IF RIM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, INCLUDING, WITHOUT LIMITATION, LOSS OF BUSINESS REVENUE OR EARNINGS, LOST DATA, DAMAGES CAUSED BY DELAYS, LOST PROFITS, OR A FAILURE TO REALIZE EXPECTED SAVINGS. This document might contain references to third-party sources of information and/or third-party web sites (Third-Party Information). RIM does not control, and is not responsible for, any Third-Party Information, including, without limitation, the content, accuracy, copyright compliance, legality, decency, links, or any other aspect of Third-Party Information. The inclusion of Third-Party Information in this document does not imply endorsement by RIM of the third party in any way. Any dealings with third parties, including, without limitation, compliance with applicable licenses, and terms and conditions are solely between you and the third party. RIM shall not be responsible or liable for any part of such dealings.

For distribution under Non Disclosure Agreement.


Last saved: 06/02/2007 www.rim.com

You might also like