Join us for a free, webinar on Thursday, December 15, 2016 on deploying a containerized application to a Kubernetes cluster.
Welcome to our monthly series of blinded stories to highlight how customers are using Red Hat solutions to address business challenges and promote innovation.
In any industry, relying on paperwork can lead to data entry errors, slower work, and higher processing costs. In the healthcare industry, these challenges can affect the end customer experience.
This month we are highlighting a major health insurance provider with more than half a million customers that submit claims and receipts each year. The provider sought to eliminate these challenges for its internal operations teams and, as a result, improve the customer experience.
Part 1: Adding Unit Tests to Native iOS Red Hat Mobile Application Platform Application
A robust and agile mobile application development environment requires continuous integration and delivery. It also requires an integrated and automated unit testing process that helps bring applications to market successfully. This two-part series details my work done at the Red Hat Open Innovation Labs and as a Mobile Technical Account Manager to capture these mobile innovations in a useful, repeatable way. In part one of this two-part series, I break down the steps to create and unit test a native iOS application using Red Hat Mobile Application Platform. In part two, I’ll show how Jenkins can be used to automate continuous integration and unit testing of that Mobile app. If you would like to try out our Red Hat Mobile Application Platform product please visit our Red Hat Mobile Application Platform site.
- Xcode 7.3
- Red Hat Mobile Application Platform 3.12 (or later)
- Mac OSX El Capitan
This article was originally posted on OpenSourceArchitects.org.
What is an SOE?
Modern IT departments face huge changes in the way they deploy and maintain servers. When I first entered the industry, UNIX, and hence Linux servers were in the parlance of cloud workloads, ‘pets’: few in number, lovingly tended machines that were individually configured and maintained by hand. They often ran many workloads at the same time (mail server, file server, database, shell accounts) on expensive hardware. A typical ratio of system administrators to servers might be 1:10 yet hardware costs, rather than labour, accounted for the greatest share of the IT department’s budget.