Search This Document
- The Push Service SDK setup application runs in graphical mode by default for both the Windows® and Linux® platforms. If the setup application is unable to run in graphical mode, it switches to console mode. A command line switch is avilable to force console mode. Separate setup applications for console mode are no longer available.
- An installation option is available to configure the SDK so that the sample and helper applications use system memory instead of a database. Installing and using the SDK in memory mode is suggested for testing purposes only.
- The setup application creates two separate folders in the SDK installation location, one containing the components that provide low-level APIs and the other containing the components that provide high-level APIs.
- An installation option is available to configure the SDK so that the sample and helper applications can use both the Push Service and the BlackBerry® MDS Connection Service (a component of the BlackBerry® Enterprise Server) simultaneously to deliver content.
- The version of Apache Tomcat™ that the setup application installs in the Distribution+Tomcat option is updated to version 6.0.32 (from version 6.0.20).
- If the setup application detects that the previous version of the Push Service SDK (version 126.96.36.199) is installed on the computer, it prompts to upgrade the database used with the previous version to make it compatible with the new version of the SDK (version 188.8.131.52). During the installation process the migration scripts run in the background to complete the database upgrade. The setup application does not upgrade any other components of the SDK (for example, the server-side library components, configuration files, or third-party components).
Next topic: Configuration files
Previous topic: New features