CodeReady Containers – Exploring a home loan mortgage process

As a cloud-native developer you've installed an OpenShift Container Platform development environment on your local machine, but what's next?

What can you do with the fully stocked container registry provided to you?

There is no better way to learn about container technologies, cloud native methods, and container-based application development than getting hands-on with great open technologies.

This article targets getting you started on your new OpenShift Container Platform 4.6 by putting the latest process automation developer tooling at your disposal together with a real project for you to deploy and explore.  Even better, if you need more help getting started, we'll provide a free online workshop where you can build this project yourself.

This articles outlines getting started exploring a home loan mortgage project on OpenShift platform. Let's get started right now exploring the new developer tooling for process design, user tasks, forms, rules, and business logic in just a few simple steps.

Process automation developer tooling


process automation toolingThis article walks through installing the Red Hat Process Automation Manager on OpenShift Container Platform on your local machine using the provided operator. It's leveraging CodeReady Containers and delivers a fully functioning container-native development experience.This means upon logging in, you'll find a project ready to go and it delivers on the promise of a fully functioning developer process automation tooling containerized on your OpenShift Container Platform.

Install on CodeReady Containers

There are two options to install and run this project on the OpenShift Container Platform; use your own existing installation or to install on CodeReady Containers which provides you with a local OpenShift cluster.
  1. Ensure you have installed OpenShift with CodeReady Containers Easy Install

  2. Download and unzip this demo.

Datasources, what, why, how?

Hope this post clarifies how a datasource works within a Java EE server and the reasons why you would need a XA Datasource when you have distributed transactions.

The origin of this post is to provide a basic understanding so that the user feels confident when to use or not to use Datasources and XA Datasources.

Where Can We Actually Use DevSecOps?

DevOps is widely adopted as it has shortened the software and application development life cycle by combining IT operations and software development. With DevOps incorporated in many organizations, they are releasing software, features, and updates faster than ever and with greater changes. This means that there are serious challenges in applying and scaling security testing in these processes without drastically slowing down the time taken for such releases.

Hence, security in DevOps has not been embraced as effectively as DevOps itself. Introducing security checks early on in the development process is crucial for effective security. Although many businesses agree that introducing security early in the development life cycle is important, few actually do so. In spite of the risk of missing security threats early on and the headache of rework by adding security to the app development process too late, many businesses continue to incorporate security far too late in the development cycle.