Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document compatibility with java 21 additionally to java 17 (#218) #227

Merged
merged 1 commit into from
Apr 26, 2024
Merged

Document compatibility with java 21 additionally to java 17 (#218) #227

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file modified modules/ROOT/images/architecture.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
2 changes: 1 addition & 1 deletion modules/ROOT/pages/first-look/linux-first-look.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
= Linux first look guide

== Prerequisites
* Java 17
* Java 17 or 21
* A Neo4j cluster meeting *xref:addition/instance-requirements.adoc[these]* requirements

NOTE: The query log feature is only available for DBMSs with instances that are running Neo4j 5.1.0 or higher.
Expand Down
4 changes: 2 additions & 2 deletions modules/ROOT/pages/installation/server.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,8 @@ In any case, please extract the content from the downloaded `.zip` or `.tar.gz`

== Prerequisites

* Windows or Unix-based operating system
* Java 17
* Windows or unix-based operating system
* Java 17 or 21
* Key pair and certificate (as a PKCS12 file) to be used for TLS protected endpoints (see xref:installation/self-signed-certificate.adoc[] for test and demo purposes).
If key pair and certificate were generated with OpenSSL, ensure that OpenSSL version 3.x or later was used.

Expand Down
2 changes: 1 addition & 1 deletion modules/ROOT/pages/introduction/architecture.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ image::architecture.png[width=500]
* *Front end* - The user connects to NOM using a web interface.
This web application communicates with the NOM Server using GraphQL API requests.

* *NOM Server* - The NOM server is a Java application, packaged in a JAR file which is deployed to a Java server (running Java 17).
* *NOM Server* - The NOM server is a Java application, packaged in a JAR file which is deployed to a Java server.

* *NOM persistence* - The NOM server requires a Neo4j database (persistence) to store the operational data, and the recommendation is that this is a dedicated Neo4j single instance running just NOM to minimise impact on other databases.

Expand Down
4 changes: 2 additions & 2 deletions modules/ROOT/pages/introduction/deployment.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Currently, support is available for Linux and Windows using tarball or zip file

The NOM server can be deployed as a Docker container with newly published images.

Currently, suppport for Kubernetes deployments is available only for NOM server with Helm Charts.
Currently, support for Kubernetes deployments is available only for NOM server with Helm Charts.

Support for package managers will be added in a later release.

Expand All @@ -19,7 +19,7 @@ Support for Aura instances and the ability to run NOM as a Service will be provi
The agent should be deployed as a service on the host operating system of each Neo4j DBMS instance to be managed by NOM.
Where more than one instance is hosted on the same host, only a single agent is required.

The NOM server should be installed on a server with Java 17. This could be a dedicated server, or a shared application server.
The NOM server can be installed on a dedicated server, or on a shared application server.

The NOM persistence database should be created on a Neo4j instance.
Ideally this would be a dedicated single instance for NOM with only the NOM persistence database deployed (in which case a license is supplied).
Expand Down
Loading