mobile

Building Red Hat Mobile Applications on your own hardware

Building Red Hat Mobile Applications on your own hardware

This guide is related to the recent deprecation of the Red Hat Mobile Application Platform Build Farm. Throughout this guide, we’ll guide you through the steps required to build on a machine of your own an application that was originally built using the Build Farm. Further information surrounding the Build Farm deprecation is available in our product release notes.

Red Hat Mobile Supported Configurations Documentation

Before getting started, it’s important to be aware of the versions of the tools, frameworks, and SDKs that the Build Farm uses to build mobile applications. This information can be found on the Red Hat Mobile Application Platform Supported Configurations page. This guide will call out the specific versions in each section and also note where you need to confirm versions for your specific project and/or requirements.

Continue reading “Building Red Hat Mobile Applications on your own hardware”

Share
Configuring the MongoDB WiredTiger memory cache for RHMAP

Configuring the MongoDB WiredTiger memory cache for RHMAP

This article describes how to configure MongoDB’s WiredTiger memory cache in Red Hat Mobile Application Platform (RHMAP) to prevent high-usage memory issues and Nagios alerts. If the WiredTiger cache consumes all the memory available for a container, memory issues and Nagios alerts will occur.

The WiredTiger storage engine is the default storage engine starting in MongoDB version 3.2. It uses MultiVersion Concurrency Control (MVCC) architecture for write operations in order to allow multiple different modifications to the same document at the same time.

WiredTiger also caches data and creates checkpoints to give you the ability to recover anytime it’s necessary. For example, if a MongoDB image deployed in a container fails, it is useful to recover the data that was not persisted. Additionally, WiredTiger can recover un-checkpointed data with its journal files. See the journal documentation and snapshots and checkpoint documentation for more information.

Continue reading “Configuring the MongoDB WiredTiger memory cache for RHMAP”

Share
Integrating Intercede RapID with Red Hat Mobile and OpenShift

Integrating Intercede RapID with Red Hat Mobile and OpenShift

At Red Hat Mobile we understand the need for a flexible product that enables our customers to integrate with the tools they need to build their current and future applications. Our position as a leading contributor to the Kubernetes project ensures that the Red Hat OpenShift Container Platform offers this tremendous flexibility to customers and end users.

Red Hat Mobile also supports highly flexible integrations to a range of 3rd party services and products. In this article, we’ll demonstrate how Red Hat Mobile v4 and OpenShift v3 enable customers to rapidly deploy and secure their mobile applications by integrating with a third party product provided by Intercede. We’ll be using Intercede’s RapID product to enable two-way TLS (often referred to as Client Certificate Authentication or CCA) for our mobile application.

Continue reading “Integrating Intercede RapID with Red Hat Mobile and OpenShift”

Share
After Years of Linux on ARM, when is the Year of Red Hat on ARM servers?

After Years of Linux on ARM, when is the Year of Red Hat on ARM servers?

From hobbyist SoC devices such as the ubiquitous Raspberry Pi to a complete domination of the mobile device market, ARM processors have proven the value of the architecture. It is easy to see why ARM processors were able to explode in this market, given that they are able to pack quite a bit of performance into a rather small physical space. Take for instance Qualcomm’s Snapdragon 400 processor, which is used in many products including the Huawei Watch This processor provides a dual core, fast, performance using 14-nanometer design. This makes it small enough to fit on your wrist, and it is efficient enough to limit power consumption enough to run on a battery, which can also fit on your wrist. The usefulness in these spheres of ARM processors is well known, and the fact that RHEL seems to have little interest in the mobile, embedded device, or hobbyist market is also fairly well known. What should be of interest to Red Hat developers, though, is the potential for the Enterprise Server market that ARM processors seem to be displaying. While x86 devices likely are to remain in place for workstations and laptops, the low power usage and small physical design of ARM processors make it interesting to the server market, where power consumption and space are also limitations.

Continue reading “After Years of Linux on ARM, when is the Year of Red Hat on ARM servers?”

Share
Working with peer, scoped and private npm dependencies in RHMAP

Working with peer, scoped and private npm dependencies in RHMAP

RHMAP Environments

An RHMAP Environment provides a Node.js runtime for Mobile Backends. There are 2 environment types: Dynofarm & OpenShift. The former is an LXC based PaaS, written in Node.js & bash. It is superseded by OpenShift environments. However, there are still many Dynofarm environments in use in the RHMAP SaaS offering.

Continue reading “Working with peer, scoped and private npm dependencies in RHMAP”

Share
Scaling Sync

Scaling Sync

Introduction

One of the biggest challenges for developers to build mobile applications is data synchronization. It’s the foundation for many different types of mobile applications, but it’s very complicated and very hard to implement.

Continue reading “Scaling Sync”

Share