Boy, that title was a mouth full.
Now if you want more information on Docker, you can check out reference [3]. Or if you're looking for Java 11 GraalVM Dockerimages suitable for Jelastic, you can check out [1] and [2].
This blog is more about the contents of the Dockerimage than Docker itself.
GraalVM
Well, I've been using Jelastic for a while now, and it suited my needs, until it didn't.
They provide GraalVM out of the box, but not the Java 11 version yet.
I was using a Payara Server image for Jelastic, and I had good results just installing GraalVM on the Image afterwards and run Payara using that, but I was looking for something a little more lean.
Sooo, in short, I used the GraalVM image used by Jelastic as a baseline in my Docker image (jelastic/javaengine:graalvm-21.0.0.2).
Then it was just install the JDK11 version of GraalVM and create my Image.
Less troublesome than I thought it would be.
Payara Micro
So Payara Micro is awesome. The way this differs from Microprofile, is that Microprofile contains only Microprofile and the Payara Micro basically seems to be a small Payara server run from the command line. It is based off the Payara Embedded Web release. See [4].
So there's basically two things:
- you run it from the command line using java and the payara-micro-5.2020.7.jar
- you provide a postboot file containing the settings
Example
Let's try an example.
The example basically runs a Payara Micro instance, with some wars deployed and a JDBC library for connecting to a database.
All configuration of the database connection is done using the afore mentioned postboot file.
Some notes on the postboot file.
- I am not interested in Hazelcast, so I turned this off. The main result should be faster startup.
I added eclipselink.target-database to the jdbc string, otherwise the JDBC driver will identify itself as MariaDB driver, and it is unknown. You can immediately tell by the following error message in the log:
Not able to detect platform for vendor name [MariaDB[10.4.20-MariaDB, 10]]. Defaulting to [org.eclipse.persistence.platform.database.DatabasePlatform]. The database dialect used may not match with the database you are using. Please explicitly provide a platform using property "eclipselink.target-database".
- I also added a config property to it. Microprofile (which is included) has support for Configuration. And it's great!
Secure Socket Layer
There's a simple self signed SSL Certificate included in the Payara Micro, which works fine, unless, like me, you wish to use a genuine SSL Certificate.
The idea here is to expand on the command line (see above in run.sh) with SSL options, for example as follows:
- -Djavax.net.ssl.trustStore="/home/jelastic/cacerts.jks"
- -Djavax.net.ssl.keyStore="/home/jelastic/keystore.jks"
- -Djavax.net.ssl.trustStorePassword="changeit"
- -Djavax.net.ssl.keyStorePassword="changeit"
References
- [1] Dockerhub - my jelastic graal with jdk 11 docker image
- https://hub.docker.com/r/maartenl22/jelasticgraaljdk11
- [2] Github - Docker file
- https://github.com/maartenl/jelasticgraaljdk11
- [3] MyBlog - Docker
- https://randomthoughtsonjavaprogramming.blogspot.com/2021/06/docker.html
- [4] Payara Micro Documentation
- https://docs.payara.fish/community/docs/documentation/payara-micro/payara-micro.html
- Releases - graalvm/graalvm-ce-builds
- https://github.com/graalvm/graalvm-ce-builds/releases
- How to install GraalVM on Linux with alternatives
- https://gist.github.com/ricardozanini/fa65e485251913e1467837b1c5a8ed28
- GraalVM - GraalVM Community Images
- https://www.graalvm.org/docs/getting-started/container-images/
- Github - graalvm-ce
- https://github.com/orgs/graalvm/packages/container/package/graalvm-ce
No comments:
Post a Comment