Skip Navigation

Known issues

  • If you have a plug-in that you developed using the 
    UEM Integration SDK
     version 12.9 or earlier and 
    UEM
     version 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 and 
    UEM
     version 12.10 or later, this task is not required.
    1. In 
      Eclipse
      , delete the 
      Core Server
       launcher and 
      Hosted Core Template
       launcher.
    2. Add the following arguments to the UI Server launcher:
      "-Dcerticom.keyagreement.ecdh=rawECDH" "-Djdk.tls.ephemeralDHKeySize=2048" "-Djdk.tls.namedGroups=secp256r1,secp384r1,secp521r1"
    3. From the 
      UEM Plug-in Tools
       menu, run the 
      UEM Integration Setup
       process again.
  • BlackBerry UEM
     12.9 and later uses 
    Google
     Web Toolkit (GWT) version 2.8.2. GWT 2.8.2 restricts access to some JAXB libraries. If any of your custom 
    UEM
     plug-ins use restricted JAXB classes, the plug-ins will not be able to access these classes when running in 
    UEM
     version 12.9 or later. As a result of this change, it is recommended that you update any affected 
    UEM
     plug-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 your 
    Eclipse
     development environment with the local 
    UEM
     installation, a window prompts you to choose which 
    UEM
     services 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 the 
    Windows
     Services, stop the 
    UEM
     services manually.