Known issues
- If you have a plug-in that you developed using theUEM Integration SDKversion 12.9 or earlier andUEMversion 12.9 or earlier, complete the following steps to update the Core and UI launchers. If you are developing a plug-in using SDK version 12.10 or later andUEMversion 12.10 or later, this task is not required.
- InEclipse, delete theCore Serverlauncher andHosted Core Templatelauncher.
- Add the following arguments to the UI Server launcher:"-Dcerticom.keyagreement.ecdh=rawECDH" "-Djdk.tls.ephemeralDHKeySize=2048" "-Djdk.tls.namedGroups=secp256r1,secp384r1,secp521r1"
- From theUEM Plug-in Toolsmenu, run theUEM Integration Setupprocess again.
- BlackBerry UEM12.9 and later usesGoogleWeb Toolkit (GWT) version 2.8.2. GWT 2.8.2 restricts access to some JAXB libraries. If any of your customUEMplug-ins use restricted JAXB classes, the plug-ins will not be able to access these classes when running inUEMversion 12.9 or later. As a result of this change, it is recommended that you update any affectedUEMplug-ins to remove JAXB-related dependencies from GWT code.For more information about this GWT change, see JEP 320: Remove the Java EE and COREBA Modules.
- When you start the process to integrate yourEclipsedevelopment environment with the localUEMinstallation, a window prompts you to choose whichUEMservices to stop so that you can complete the integration. After you select the services and click OK, the integration process does not stop the services. (2195939)Workaround:In theWindowsServices, stop theUEMservices manually.