diff --git a/openidm-doc/src/main/asciidoc/getting-started/chap-basic-install.adoc b/openidm-doc/src/main/asciidoc/getting-started/chap-basic-install.adoc index c74ae7ff3..cd40fd165 100644 --- a/openidm-doc/src/main/asciidoc/getting-started/chap-basic-install.adoc +++ b/openidm-doc/src/main/asciidoc/getting-started/chap-basic-install.adoc @@ -86,7 +86,7 @@ On Windows systems, after installing Java, set the `JAVA_HOME` environment varia ==== -. Locate your JRE or JDK installation directory. For a default installation of Java 8 on Windows 10, you should find the directory here: `C:\Program Files\Java\jre-version`. +. Locate your JRE or JDK installation directory. For a default installation of Java 11 on Windows 10, you should find the directory here: `C:\Program Files\Java\jre-version`. . Press `Windows + R` to launch the Windows Run prompt Properties window. diff --git a/openidm-doc/src/main/asciidoc/integrators-guide/appendix-jetty.adoc b/openidm-doc/src/main/asciidoc/integrators-guide/appendix-jetty.adoc index 944a8d46f..2529bfd07 100644 --- a/openidm-doc/src/main/asciidoc/integrators-guide/appendix-jetty.adoc +++ b/openidm-doc/src/main/asciidoc/integrators-guide/appendix-jetty.adoc @@ -184,7 +184,7 @@ A list of servlet names to which the filter should apply. The default is `"OpenI A list of URL patterns to which the filter applies. The default is `["/*"]`. `"initParams"`:: -Filter configuration initialization parameters that are passed to the servlet filter `init` method. For more information, see link:http://docs.oracle.com/javaee/5/api/javax/servlet/FilterConfig.html[http://docs.oracle.com/javaee/5/api/javax/servlet/FilterConfig.html, window=\_top]. +Filter configuration initialization parameters that are passed to the servlet filter `init` method. For more information, see link:https://jakarta.ee/specifications/servlet/4.0/apidocs/javax/servlet/filterconfig[https://jakarta.ee/specifications/servlet/4.0/apidocs/javax/servlet/filterconfig, window=\_top]. -- diff --git a/openidm-doc/src/main/asciidoc/integrators-guide/chap-resource-conf.adoc b/openidm-doc/src/main/asciidoc/integrators-guide/chap-resource-conf.adoc index 1b17a6b8c..50f5e09f2 100644 --- a/openidm-doc/src/main/asciidoc/integrators-guide/chap-resource-conf.adoc +++ b/openidm-doc/src/main/asciidoc/integrators-guide/chap-resource-conf.adoc @@ -122,9 +122,6 @@ string + Version 1.5.0.0 of the OpenICF framework supports a new communication protocol with remote connector servers. This protocol is enabled by default, and its value is `websocket` in the default configuration. -+ -For compatibility reasons, you might want to enable the legacy protocol for specific remote connectors. For example, if you deploy the connector server on a Java 5 or 6 JVM, you must use the old protocol. In this case, remove the `protocol` property from the connector server configuration. - + For the .NET connector server, the service with the new protocol listens on port 8759 and the service with the legacy protocol listens on port 8760 by default. diff --git a/openidm-doc/src/main/asciidoc/integrators-guide/chap-security.adoc b/openidm-doc/src/main/asciidoc/integrators-guide/chap-security.adoc index c4e282b84..b9d7892d0 100644 --- a/openidm-doc/src/main/asciidoc/integrators-guide/chap-security.adoc +++ b/openidm-doc/src/main/asciidoc/integrators-guide/chap-security.adoc @@ -38,7 +38,7 @@ In a production environment, avoid the use of communication over insecure HTTP, [#security-management-service] === Accessing the Security Management Service -OpenIDM stores keystore and truststore files in a folder named `/path/to/openidm/security`. These files can be managed by using the `keytool` command, or over the REST interface, at the URL `\https://localhost:8443/openidm/security`. For information about using the `keytool` command, see link:http://docs.oracle.com/javase/6/docs/technotes/tools/solaris/keytool.html[http://docs.oracle.com/javase/6/docs/technotes/tools/solaris/keytool.html, window=\_top]. +OpenIDM stores keystore and truststore files in a folder named `/path/to/openidm/security`. These files can be managed by using the `keytool` command, or over the REST interface, at the URL `\https://localhost:8443/openidm/security`. For information about using the `keytool` command, see link:https://docs.oracle.com/en/java/javase/11/tools/keytool.html[https://docs.oracle.com/en/java/javase/11/tools/keytool.html, window=\_top]. The following sections describe how to manage certificates and keys over REST.