Red Hat Software Collections can make your life as a programmer or admin immensely easier.
Like death, taxes and zombies, dealing with different versions of software is something you just can’t avoid. It’s a nasty but necessary fact of life.
Traditionally, when developers and system admins grapple with this issue, they have to sacrifice something. If you want to run the latest and greatest version of a web app, it might not support users with outdated browsers. If you install the newest beta release of Python so you can test development code, it might break Python scripts written for older releases. If you have a system with multiple users, you might want a different version of Ruby over another. And so on.
Software Collections provide a solution to conundrums like these. They let you have your cake and eat it, too.
In other (more technical) words, Software Collections make it possible to have multiple versions of the same software on the same system. You use a simple tool to tell the system which version to activate as needed.
If that sounds awesome, it is. Keep reading for a more detailed explanation of how Software Collections work, and an overview of using them on your Red Hat system.
Continue reading “Red Hat Software Collections: Why They’re Awesome, and How to Use Them”
Red Hat JBoss Core Services Collection is a group of common services that are critical for application developers. The services included change as new services and projects are added over time, but the idea is to include common, developer-friendly projects under a single subscription. The collection makes it much easier for developers to access these services.
The launch of the Core Services Collection includes services that focus on three areas: web servers, security, and monitoring.
There are six components available in the launch of Core Services Collection:
- JBoss Operations Network, which is based on the former RHQ project (now Hawkular). From a high level, this is a monitoring and management server, but the key is that it is developed in parallel with other JBoss products, so there is tight integration with other JBoss products. This centralizes all management for JBoss middleware products and also for Java applications running on JBoss EAP.
- An integrated single sign-on server based on the Keycloak project. This SSO server supports SAML 2.0, OAuth, and OpenID and it can work with LDAP servers and Active Directory for user identity management. Keycloak SSO makes it a lot easier to define user domains, federated identities, and client applications because it has a very simple graphical UI, as well as REST APIs.
- The Apache Commons Jsvc daemon provides a way to manage Java virtual machines on Unix/Linux; in general, this is used as a wrapper for Java applications so that those applications can be managed by native system tools.
- Apache HTTP server is the most-used web server in the world. Web servers are used to route traffic and load balance requests to JBoss EAP and other middleware servers.
- Web connectors provide a connection with third-party web servers which need to interact with JBoss middleware products and may not have a native connection. For this release, there are two connectors available:
- Microsoft IIS
- Oracle iPlanet
Continue reading “An Announcement for JBoss Core Services Collection”
On developers.redhat.com you can find short, focused guides to help you start developing with a number of Red Hat technologies. With the recent release of Red Hat Software Collections (RHSCL) 2.2, a number of Get Started guides have been updated to use the newest software collections, such as Node.js 4.4, Python 3.5, and Ruby 2.3. These guides give you the steps you need to install the software and get to a simple “Hello, World” in a few minutes. The guides include a few additional package management examples to help you go farther.
Continue reading Node.js 4.4, Python 3.5, and Ruby 2.3 Get Started guides on developers.redhat.com
MongoDB has evolved into one of the most popular open source “NoSQL” databases—so-called because they dispense with the tabular storage schema of relational databases like MySQL and Postgres. NoSQL databases offer a variety of advantages in many cases
The biggest advantage is that MongoDB databases don’t require developers to define schemas before adding data to a database. Instead, they use a flexible document-based model, similar to Python dictionaries or Ruby hashes. With MongoDB, you don’t need to spend time creating tables before you can process your data. That makes the NoSQL approach ideal for situations where you don’t know how much data you have to handle, what form it is in, or how quickly it is going to move around.
There’s a lot more to say about what makes MongoDB, and NoSQL in general, a better fit for some situations. (I could also write a great deal about when not to use NoSQL—and that’s important, because despite NoSQL’s current trendiness, it’s not better in all contexts.)
But that’s all fodder for a separate blog post. For now, let’s move onto the meat of this post, which is how to install MongoDB on Red Hat Enterprise Linux (RHEL) in order to take advantage of NoSQL databases.
Continue reading “Installing MongoDB on Red Hat Enterprise Linux”