EnterpriseMobileToday PDAStreet

Home | News | Reviews | Features | Tips | Mobile Product Watch | Forums



Internet.com's premiere site for mobile managers and IT professionals is where wireless meets business. Our expert analysis and tips will guide you in buying, deploying, securing and managing mobile technology in the enterprise. You'll find strategic analysis, best practices, news, buyer.s guides and practical advice on how to evaluate and support a wide range of devices in the workforce.


PDAStreet.com > Features > RIM's Checklists for Upgrading to BES 4.1

RIM's Checklists for Upgrading to BES 4.1

By BlackBerryToday Staff
June 6, 2006

Research In Motion covieniently offers two checklists to follow when upgrading from BlackBerry Enterprise Server 4.0 to 4.1. One covers IBM Lotus Domino environments and the other Microsoft SQL Server 2000 Service Pack 3 Microsoft SQL Server 2005. The guide recommends you see the Installation Guide and the System Administration Guide to verify your system requirements before moving on to each checklist.

It also adds that the deployment of IBM Lotus Sametime to BlackBerry wireless devices requires the BlackBerry Collaboration Service to be running. As a result, you do not need to install BlackBerry MDS Services. In addition, the provisioning of mobile application support through BlackBerry MDS Studio and BlackBerry MDS Runtime requires the BlackBerry MDS Services - Apache Tomcat Service to be running. As a result, you need to install BlackBerry MDS Services.

IBM Lotus Domino Environment Checklist

  1. Verify that there is only one notes.ini file. Rename duplicate copies and remove any unused ones.
  2. Check that the following parameters of the notes.ini file are maintained correctly:
    • Directory=C:LotusDominoData
    • NotesProgram=C:LotusDomino
    • ServerKeyFileName=<server.id>

    Note: The above settings may differ depending on your environment setup; however, do not maintain the full file path for ServerKeyFileName.

    Warning: The following procedure may involve modifying the computer registry. This can cause substantial damage to the Microsoft Windows® operating system. Document and back up the existing registry entries prior to implementing any changes.

  3. Go to HKEY_LOCAL_MACHINESoftwareLotusDomino and verify Datapath and Path registry keys are present. Make sure they are updated with the correct values.
  4. Note: The values should be the same as the values in the notes.ini file (for example, the default value for Datapath is C:LotusDominoData).

  5. Back up the BlackBerry Enterprise Server folder located in C:LotusDominoData.
  6. Back up a copy of the notes.ini file.
  7. Make note of the Service Routing Protocol (SRP) Identifier, SRP Authentication Key, and Client Access License (CAL).

Microsoft SQL Server Environment Checklist

  1. Verify the Microsoft Data Access Components (MDAC) version is as follows:
    • MDAC 2.8 with Security Patch MS04-003 (version 2000.85.1025.00)
    • OR

    • MDAC 2.8 Service Pack 2 (version 2000.86.1830.00)
    • Note: MDAC 2.8 Service Pack 2 is shipped only with Windows Server® 2003 Service Pack 1.

  2. Install the appropriate Java™ Database Connectivity (JDBC™) driver:
  3. Remove any existing copies of Java 2 Runtime Environment installed.
  4. Note: Java™ 2 Platform, Standard Edition (J2SE™) Runtime Environment version 5.0 update 4 is installed during the installation.

  5. Verify that the Windows service account used for the installation has the following:
    • System administrator permission on the computer that hosts the BlackBerry Enterprise Server.
    • System Administrator and Database Creator permissions on the SQL Server.
  6. Verify that mixed mode authentication has been enabled by creating the following registry key for Microsoft Data Engine (MSDE) or SQL Server:
    • Go to HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSSQLServerMSSQLServer.
    • Create a REG_DWORD value called LoginMode.
    • Set the decimal value to 2 for mixed mode authentication.
    • Note: For more information, see article 325022 on the Microsoft Support Knowledge Base.

  7. Verify that you are using an MSDE or SQL Server with a Default Instance as the data source.
  8. Note: For information about BlackBerry Mobile Data System™ (BlackBerry MDS™) Services installation failing with the Named Instance, see KB-04954.

  9. Verify that you are using the default SQL port 1433:
    • Go to HKEY_LOCAL_MACHINESoftwareResearch in MotionBlackBerry Enterprise ServerDatabase.
    • Create a new DWORD value called Port (this is case-sensitive).
    • As a decimal value, type the custom SQL port number you are using.
    • Note: For information about BlackBerry MDS Services installation failing if the non-default SQL port is used, see KB-04940.

  10. Verify that Named Pipe and TCPIP protocols have been enabled for the SQL Network Utility tool on your remote SQL Server.
  11. If you are currently using SQL authentication for the BlackBerry® Configuration SQL Database, make sure to type a new SQL account during the installation of the BlackBerry MDS Services. Also make sure that a password is typed for this new SQL account.
  12. Note: Using a different SQL account for the MDS Services installation is a requirement. For information, see the Installation Guide.



Related Links:

  • Mobile Messaging: Part II - The MMS Conundrum
  • Dispelling Mobile Marketing Myths III: Staying Connected with Your Audience
  • Tip: BlackBerry OS 4.1 Enhances Compose Screen
  • Chapter Excerpt: BlackBerry Hacks - Tips & Tools
  • Mobile Device Security I: Threats Real, Time to Act Now

     
     Printable Version  Get the Full Story
     Email this Story to a Friend