Embracing the Cloud A Java Developer’s Guide to Jakarta EE on The Cloud - A Real-World Example

This talk will focus either on AWS or Azure (depending on the platform of choice).

This talk provides a comprehensive walkthrough of how to package and deploy Jakarta EE applications to be cloud-ready for deployment.

The session begins with an overview of Jakarta EE and the cloud platform, highlighting their unique features and advantages. This sets the stage for understanding the synergy between these two powerful platforms.

The core of the session is a detailed, step-by-step tutorial on packaging a Jakarta EE application for the cloud. This covers creating a WAR file, configuring the application for the cloud, and testing the application locally before deployment, then deploying the packaged application to the cloud. This involves creating the cloud App Service, configuring deployment settings, and uploading the WAR file.

Once the application is live, the session explores how to monitor its performance using the cloud’s built-in monitoring tools. Attendees will learn how to interpret these metrics to ensure their application is running optimally.

By attending this session, Java developers will gain a solid understanding of how to leverage the cloud for their Jakarta EE applications. They will leave equipped with practical knowledge and skills to embrace the cloud confidently.

1. Embracing
the Cloud
A Java Developer’s Guide to Jakarta
EE on The Cloud -A Real-World
Example.

2. ●Senior Full Stack Enterprise Java
Developer, Engineer and
Consultant, Sindi Technologies
(Pty) Ltd
○18+ years of Java development
experience.
●Jakarta EE Ambassador
●Tech speaker / Blogger
●Devoxx4Kids South Africa (Non-
Profit Organisation) founder and
event organiser
About Me

3. Where to find me?
https://linktr.ee/theEliteGentleman
[email protected]
@EliteGentleman
www.sindi.co.za
www.devoxx4kids.org.za
https://jakartaee-ambassadors.io/

4. To my
parents…
What (is it) exactly do I do for a living?

5. ●Business brings problems that they want solution to make it go
away.
●I scope their problem into a solution.
●-> -> ->
(code) (build) (deploy) (ship)
●Programming language: Java (as in )
●Preferred framework to build business applications using Java:
Jakarta EE (previously known as Java EE). EE -> Enterprise Edition.
I foresee every step of the business lifecycle of the project, from
inception to release.
A glorified work life

6. Your JakartaEE
application
Configuration settings and
infrastructures
01

7. ●A Health provider medical claim system.
●Written fully in Java
○Mavenised
○JDK 17+
○Jakarta EE 10 (Faces 4, CDI, JPA with JNDI DataSource, Jakarta SOAP
WS –JAX-WS, Jakarta REST –JAX-RS, JavaMail)
○Certificates (HTTP security), static IP addresses for HTTP transport
communication
●Database
○PostgreSQL 16.2 or higher
●Application server
○Any Jakarta EE 10 certified product –OpenLiberty24.0.0.1 or higher
Introducing Kuanza

8. https://kuanza.southafricanorth.azurecontainer.io:9443/

9. Getting started
●https://start.jakarta.ee
●For starting your Jakarta EE
journey from scratch.
●Generate MavenizedJakarta
EE projects
●Supported via popular IDEs
oIntelliJ, NetBeans, Eclipse, Visual
Studio Code.

10. Prepping for
cloud-readiness
02

11. ●Containerization
○Only your application code is bundled, as well as all necessary files,
libraries and Operating System libraries and dependencies required to
run the code are packaged into a single executable (container) that
runs on any infrastructure.
●Benefits
○Portability: A container can run on multiple infrastructure and
environments without changing code.
■Prevent “But it does work on my machine” problem.
○Scalable: Containers are lightweight. Bootup is faster (no OS bootup
needed). Multiple containers can run on a single machine.
○Isolation: Containers doesn’t require knowledge of hardware and OS.
Prepping for cloud-readiness

12. ●Containerized
○Simplified to run on any platform.
■Prevent “But it does work on my machine” problem.
○Containerized PostgreSQL database.
○Containerized OpenLibertyApplication Server.
●Cloud Provider of choice: Azure
○Quick response time to enterprise customer problem.
○Business chose this.
○Not sponsored talk by Microsoft! (No joke!)
For Kuanza
https://www.slideshare.net/BuhakeSindi/dockerizing-
your-java-development-environment

13. PostgreSQL Compose
FROMopen-liberty:full-java17-openj9
COPY--chown=1001:0 src/main/liberty-
docker/postgresql-42.7.3.jar
/opt/ol/wlp/lib/postgresql-42.7.3.jar
COPY--chown=1001:0 src/main/liberty-
docker/config/server.xml
/config/server.xml
COPY--chown=1001:0 src/main/liberty-
docker/config/ccert.medikredit.co.za.p12
/output/resources/security/key.p12
COPY--chown=1001:0 target/*.war
/config/apps/
ENVSEC_TLS_TRUSTDEFAULTCERTS=true
ARGTLS=true
RUNconfigure.sh
OpenLibertyDockerfile

14. Let’s hack with
Azure
Get your DevOps hat ready!
03

15. ●Azure subscription.
○Get an Azure account, get a subscription ID.
○Get an Azure region location for your region group.
●Install Azure CLI
●Basic knowledge of Linux
○Commands such as: chown, wget, curl, cat, etc.
○Windows: Use WSL (Windows Subsystem for Linux), notGit Bash
●Basic knowledge of Docker scripting (Dockerfileand/or Docker
compose)
Requirements

16. https://www.digitalocean.com/community/tutorials/linux -
commands

17. ●Azure Resource Group (cluster everything in 1 resource group)
●Azure for PostreSQLSingle Server *
○* Soon to be replaced with Azure PostgreSQL Flexible Server
(single server will be decommissioned in 2025 by Microsoft)
●Azure Container Registry (Private Docker Registry)
●Azure Container Instance (containerapp)
●Azure Kubernetes Service (AKS) –should you need advanced
metrics that Kubernetes provides.
○Not used for this presentation.
Azure services

18. ●https://portal.azure.com/
○View the progress of your services that you create.
○Useful for monitoring of your services to make decisions such as scaling.
Azure Portal

19. ●Login to your Azure cloud using Azure CLI
○Grab the subscription ID once you’ve successfully logged in.
○Command: azlogin
1. Login to Azure

20. ●Command: azaccount set
2. Set subscription, if necessary

21. ●Command: azaccount list-locations -o table
3. Select a region

22. ●A resource group contains all your services (resources) which you
create.
○Useful for managing all your resources as a group.
●Command: azgroup create
4. Create a Resource Group

23. ●Azure for PostgreSQL Database is a relational database service based on
open-source Postgres database engine. It is fully managed database-as-a-
service offering which is available with 2 different offerings: Single Server and
Flexible Server.
○For this presentation, we’ve used Single Server offering.
○Documentation:
■Flexible Server: https://learn.microsoft.com/en-us/azure/postgresql/
■Single Server: https://learn.microsoft.com/en-us/azure/postgresql/single-
server/concepts-servers
●Command: azpostresserver create
5a. Install PostgreSQL on Azure

24. 5. Install PostgreSQL on Azure

25. 5. Install PostgreSQL on Azure

26. ●Once your server has been created, the fully qualified domain name of your
PostgreSQL server should be in the format:
[AZURE_POSTGRES_SERVER_NAME].postgres.database.azure.com
●This can be retrieved from the JSON response value of
fullyQualifiedDomainName
●Command: azpostgresserver show
5b. Verifying PostgreSQL on Azure

27. 5b. Verifying PostgreSQL on Azure

28. ●Azure PostgreSQL server is secured by default. It doesn’t accept
incoming connection.
○1. Get IP address from your IP address. For WSL users, use cat
/etc/resolve.confto get IP address.
6. Setup Azure Firewall Rule for PostgreSQL Server

29. ●From Azure Portal (under Connection security in my database)
6. Setup Azure Firewall Rule for PostgreSQL Server

30. ●The PostgreSQL server that you created earlier is empty. We need
to create a new database.
●Command: azpostgresdbcreate
Create PostgreSQL Database

31. ●Login to your empty database (with admin credentials) and run the following
script.
Create non-admin (superuser) user and grant

32. ●The default Azure JDBC URL for the PostgreSQL Server is of the format:
jdbc:postgresql://{AZURE_POSTGRES_SERVER_NAME}.postgres.database.azure.com:5432
/{AZURE_POSTGRES_SERVER_DATABASE_NAME}?user={DATABASE_USER}@{AZURE_PO
STGRES_SERVER_NAME}?&password={DATABASE_PASSWORD}&sslmode=require
●On OpenLiberty(inside your server.xml):
<properties.postgresqlURL="jdbc:postgresql://kuanza-
db.postgres.database.azure.com:5432/kuanza_db?user=kuanza_root@kuanz
a-
db&amp;password={PASSWORD}& amp;sslmode=require&amp;stringtype=u
nspecified" />
JDBC URL

33. ●Azure Container Registry is a managed, private Docker Registry
service to store and manage your Docker container images (based
on Open-source Docker Registry 2.0)
●There are 4 SKU available when creating your ACR: Basic, Classic,
Premium, Standard.
●Our Jakarta EE Application Docker image will be stored here.
●Command: azacrcreate
7a. Setup Azure Container Private Registry

34. ●Login to ACR to get the ACR server name
○ACR server name is of format [ACR_NAME].azurecr.io
●Command: azacrlogin
●Command: azacrshow
7a. Login to Azure Container Private Registry

35. ●Build your Jakarta EE project into a WAR file
○Command: mvnclean package
●Build the Docker Image and push it to the Azure Container
Registry.
8. Build and push the image to Azure Container
Registry

36. ●Azure Container Instances allows you to run a container in Azure
without having to manage any VMs and/or adopt any higher -level
services.
●We are now ready to deploy our Jakarta EE application to Azure
Container Instances. When deploying to ACI, you need to specify a
custom DNS name.
9. Deploy the application to Azure Container Instances

37. ●We will need the password for Azure Container Registry
●Command: azacrcredential show
9. Deploy the application to Azure Container Instances

38. ●Create the container with the password provided previously
●Command: azcontainer create
9. Deploy the application to Azure Container Instances

39. ●Result is default JSON format
9. Deploy the application to Azure Container Instances

40. ●http(s)://[DNS_NAME_LABEL].[AZURE_LOCATION].azurecontainer.i
o[:PORT]/
●For Kuanza:
https://kuanza.southafricanorth.azurecontainer.io:9443/
Result

41. Further
improvement…
04

42. ●Automated Deployment
○CI/CD build tools (Jenkins, BitBucket)
●Monitoring of resources
○For up/down scaling of resources as needed, over time.
●Automation of Cloud Infrastructure
○Terraform
●Applying custom domain to resources.

43. Thank you!

44. Demo!

45. Questions?