In our continuing series on alternatives for commercial Oracle GlassFish features , in this article we are looking at Hazelcast - a replacement for Oracle's Coherence ActiveCache.

Today, continuing our series on alternatives to commercial Oracle GlassFish features, we will look at backup and restoring domains with Payara Server.

See here for part one of the GlassFish to Payara Server migration series: 'Migrating away from the Load Balancer Configurator Plugin' .

In the first of our series on migrating away from Oracle GlassFish Server, we will look at replacing the functionality of the Load Balancer Configurator, and its potential alternatives.

One of the biggest challenges when developing applications for the web is understanding how applications need to be fine-tuned when releasing them into a production environment. This is no exception for Java Enterprise applications deployed on Payara Server.

In this three-parts article series I'm illustrating the implementation of the LDAP integration using a sample scenario: integrate Payara Server with a LDAP user directory and manage the authentication and authorization of a sample web application.

In Part 1, I showed you how to start the LDAP Server, while in Part 2  we configured the LDAP realm. Now you are probably wondering how to get the user’s information (first and last name, email address, etc.) that resides in the LDAP server. Unfortunately, the JAAS API doesn’t offer any standard mechanisms to access this user attributes in the directory tree. But there are other options available:

See 'Part 1 - Configuring the LDAP Server' here.

In this three-parts article series I will illustrate the implementation of the LDAP integration using a sample scenario: integrate Payara Server with a LDAP user directory and manage the authentication and authorization of a sample web application.

If you work in an organization with a robust IT department, it's very likely that you are using a LDAP server to handle your user directory information. You probably have to follow some general guidelines dictating that all web applications deployed within the organization’s infrastructure must access this user directory; and must authenticate and authorize the users that will interact with them. This is a very common scenario nowadays.

As you probably know, Payara Server was created as an effort to fill the gaps that Oracle left when they dropped commercial support offerings for Glassfish Open Source Edition 4.x versions. However, our goal at Payara Services is not only to fill these gaps in support, but to strengthen the Community around Payara and GlassFish as well. For this to happen, we encourage all Payara Server & Payara Micro users to contribute to the Community - and there are a couple of ways to do so.

As part of the new features introduced with the release of Payara Server 162, you can now form a cluster of Payara Server instances using the concept of Hazelcast “Lite Nodes”. This can help you create more flexible cluster topologies.

Click here to see part 1 (Installation)

Access Configuration

Now that the ForgeRock tools have been installed, we will configure them with some basic access configuration. First, proceed to login to the OpenAM application (context /openam) with the amadmin user, and the application will show you the current realm configuration for your domain: