You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/java-embedded/setup.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,9 +17,9 @@ The following examples use the top-level artifact approach.
17
17
18
18
19
19
[NOTE]
20
-
.[enterprise-edition]
21
20
====
22
21
The examples are only valid for Neo4j Community Edition.
22
+
23
23
To add Neo4j Enterprise Edition as a dependency, please get in contact with link:https://neo4j.com/contact-us/[Neo4j Professional Services^].
24
24
See link:{neo4j-docs-base-uri}/operations-manual/{page-version}/introduction[Operations Manual -> Introduction] for details about the Community and Enterprise Editions.
25
25
====
@@ -51,7 +51,7 @@ Where the `artifactId` is found in the <<editions>> table.
51
51
52
52
=== Eclipse and Maven
53
53
54
-
For development in link:http://www.eclipse.org[Eclipse^], it is recommended to install the link:http://www.eclipse.org/m2e/[m2e plugin^] and let Maven manage the project build classpath instead.
54
+
For development in link:https://www.eclipse.org[Eclipse^], it is recommended to install the link:https://www.eclipse.org/m2e/[m2e plugin^] and let Maven manage the project build classpath instead.
55
55
This also adds the possibility to build your project both via the command line with Maven and have a working Eclipse setup for development.
Although SSL for JMX Remote Management is disabled throughout this document, to configure it based on your requirements, you can follow the instructions in the link:https://docs.oracle.com/en/java/javase/11/management/monitoring-and-management-using-jmx-technology.html[Java SE 11 Monitoring and Management Guide^].
46
+
Although SSL for JMX Remote Management is disabled throughout this document, to configure it based on your requirements, you can follow the instructions in the link:https://docs.oracle.com/en/java/javase/21/management/monitoring-and-management-using-jmx-technology.html[Java SE 21 Monitoring and Management Guide^].
47
47
====
48
48
49
49
@@ -53,7 +53,7 @@ Although SSL for JMX Remote Management is disabled throughout this document, to
53
53
Password authentication is enabled by default in JMX Remote Management.
54
54
You can find information about setting up authentication with LDAP and file-based approach in the following sections.
55
55
56
-
Refer to the link:https://docs.oracle.com/en/java/javase/11/management/monitoring-and-management-using-jmx-technology.html[Java SE 11 Monitoring and Management Guide^] for more options, including configuration steps for SSL client authentication.
56
+
Refer to the link:https://docs.oracle.com/en/java/javase/21/management/monitoring-and-management-using-jmx-technology.html[Java SE 21 Monitoring and Management Guide^] for more options, including configuration steps for SSL client authentication.
57
57
58
58
59
59
[[ldap]]
@@ -184,7 +184,7 @@ The `<port>` value is configured by the `com.sun.management.jmxremote.port` prop
184
184
Besides the MBeans, exposed by the JVM, you also see be default `neo4j.metrics` section in the MBeans tab.
185
185
Under that, you have access to all the monitoring information exposed by Neo4j.
186
186
187
-
For opening JMX to remote monitoring access, please see <<jmx-remote>> and link:https://docs.oracle.com/en/java/javase/11/management/monitoring-and-management-using-jmx-technology.html#GUID-805517EC-2D33-4D61-81D8-4D0FA770D1B8[the JMX documention^].
187
+
For opening JMX to remote monitoring access, please see <<jmx-remote>> and link:https://docs.oracle.com/en/java/javase/21/management/monitoring-and-management-using-jmx-technology.html#GUID-805517EC-2D33-4D61-81D8-4D0FA770D1B8[the JMX documention^].
0 commit comments