Red Hat Mobile Application Platform lets teams extend their development capabilities to mobile by developing collaboratively, centralizing control of security and using back-end integration with a range of cloud deployments.
We have just completed the deployment of the Red Hat Mobile Application Platform v3.12 and v4.1 to all our actively updated grids. The main features of this release are:
v4.1 of our MBaaS, which runs on the OpenShift Container Platform 3, includes the following:
- Support for OpenShift Container Platform 3.2
- Support for Node.js 4.4.2 LTS from Red Hat Software Collections (RHSCL)
- Support for MongoDB 3.2 from RHSCL
We recommend that all existing MBaaS 4.0 installation upgrade to 4.1 and also upgrade from OpenShift 3.1 to 3.2
Instructions on how to upgrade from 4.0 to 4.1 MBaaS are here.
A new summary document with a step-by-step guide on how to install 4.1 MBaaS is here.
Important Note: Whilst MongoDB 3.2 is available on MBaaS 4.1, we have not yet moved to it on RHMAP Hosted (3.12), due to the complex nature of MongoDB upgrades. This will be available in a later release, TBA.
Firebase Cloud Messaging (FCM) support in Unified Push Server
Firebase Cloud Messaging (FCM) is Google's cross-platform messaging solution. Our integrated Unified Push Server and SDKs now have support for FCM. You can learn more about our Push capabilities here and dig into the developer details here.
Open Sourcing of Server SDKs
We are really pleased to announce more progress on our Open Source journey. Our Node.js Server SDKs have just been fully Open Sourced. You can find out more information over on feedhenry.org and see a list of the SDKs here.
- Ability to delete OpenShift-based Environments
- WFM bug-fixes and refinements
- All WFM code now available on the FeedHenry RainCatcher GitHub organization
- Many fixes for Cordova, Build Farm and Forms
- The old feedhenry.com Developer Blog has now been archived and will no longer be updated.
Android Release builds of Forms Apps on the Build Farm are currently failing. This is related to the version of the Barcode Scanner plugin being used. A Support KCS article will shortly be available which will explain how to work around this. Please contact Support in the meantime for guidance if you encounter this issue.
Last updated: March 16, 2023