From 5eb78d10f87ea01bd8b46f43f155e1459ef0be60 Mon Sep 17 00:00:00 2001 From: Sean Arms <67096+lesserwhirls@users.noreply.github.com> Date: Thu, 9 Jan 2025 15:07:51 -0700 Subject: [PATCH] Updates to TDM docs --- docs/adminguide/src/site/pages/reference/TdmRef.md | 6 +----- docs/devguide/src/site/pages/thredds/TdmRef.md | 6 +----- docs/quickstart/src/site/pages/thredds/TdmRef.md | 6 +----- docs/userguide/src/site/pages/thredds/TdmRef.md | 6 +----- 4 files changed, 4 insertions(+), 20 deletions(-) diff --git a/docs/adminguide/src/site/pages/reference/TdmRef.md b/docs/adminguide/src/site/pages/reference/TdmRef.md index 4a1458fd06..7ac51f29c5 100644 --- a/docs/adminguide/src/site/pages/reference/TdmRef.md +++ b/docs/adminguide/src/site/pages/reference/TdmRef.md @@ -86,7 +86,7 @@ bg The TDM scans the files in the feature collection, and when it detects that the collection has changed, rewrites the index files. If enabled, it will send a trigger message to the TDS, and the TDS will reload that dataset. To enable this, you must configure the TDS with the `tdsTrigger` role, and add the user `tdm` with that role. -Typically, you do that by editing the `${tomcat_home}/conf/tomcat-user.xml` file, e.g.: +Typically, you do that by editing the `${tomcat_home}/conf/tomcat-users.xml` file, e.g.: ~~~xml @@ -152,16 +152,12 @@ Point the TDM to the content directory using `-Dtds.content.root.path= - ~~~ * `` element for the TDM * `rewrite="test"` tells the TDM to test for dataset changes * `rescan="0 0/15 * * * ? *"` rescan directories every 15 minutes. -* `` element for the TDS - * `startup="never"` tells the TDS to read in the `featureCollection` when starting up, using the existing indices - * `trigger="allow"` enables the TDS to receive messages from the TDM when the dataset has changed ## `GCPass1` diff --git a/docs/devguide/src/site/pages/thredds/TdmRef.md b/docs/devguide/src/site/pages/thredds/TdmRef.md index 65561a94ee..6d989d6739 100644 --- a/docs/devguide/src/site/pages/thredds/TdmRef.md +++ b/docs/devguide/src/site/pages/thredds/TdmRef.md @@ -84,7 +84,7 @@ bg The TDM scans the files in the feature collection, and when it detects that the collection has changed, rewrites the index files. If enabled, it will send a trigger message to the TDS, and the TDS will reload that dataset. To enable this, you must configure the TDS with the `tdsTrigger` role, and add the user `tdm` with that role. -Typically, you do that by editing the `${tomcat_home}/conf/tomcat-user.xml` file, e.g.: +Typically, you do that by editing the `${tomcat_home}/conf/tomcat-users.xml` file, e.g.: ~~~xml @@ -150,16 +150,12 @@ Point the TDM to the content directory using `-Dtds.content.root.path= - ~~~ * `` element for the TDM * `rewrite="test"` tells the TDM to test for dataset changes * `rescan="0 0/15 * * * ? *"` rescan directories every 15 minutes. -* `` element for the TDS - * `startup="never"` tells the TDS to read in the `featureCollection` when starting up, using the existing indices - * `trigger="allow"` enables the TDS to receive messages from the TDM when the dataset has changed ## `GCPass1` diff --git a/docs/quickstart/src/site/pages/thredds/TdmRef.md b/docs/quickstart/src/site/pages/thredds/TdmRef.md index 45756a5e86..8188559857 100644 --- a/docs/quickstart/src/site/pages/thredds/TdmRef.md +++ b/docs/quickstart/src/site/pages/thredds/TdmRef.md @@ -84,7 +84,7 @@ bg The TDM scans the files in the feature collection, and when it detects that the collection has changed, rewrites the index files. If enabled, it will send a trigger message to the TDS, and the TDS will reload that dataset. To enable this, you must configure the TDS with the `tdsTrigger` role, and add the user `tdm` with that role. -Typically, you do that by editing the `${tomcat_home}/conf/tomcat-user.xml` file, e.g.: +Typically, you do that by editing the `${tomcat_home}/conf/tomcat-users.xml` file, e.g.: ~~~xml @@ -150,16 +150,12 @@ Point the TDM to the content directory using `-Dtds.content.root.path= - ~~~ * `` element for the TDM * `rewrite="test"` tells the TDM to test for dataset changes * `rescan="0 0/15 * * * ? *"` rescan directories every 15 minutes. -* `` element for the TDS - * `startup="never"` tells the TDS to read in the `featureCollection` when starting up, using the existing indices - * `trigger="allow"` enables the TDS to receive messages from the TDM when the dataset has changed ## `GCPass1` diff --git a/docs/userguide/src/site/pages/thredds/TdmRef.md b/docs/userguide/src/site/pages/thredds/TdmRef.md index fbb3e15c8f..addc05d46e 100644 --- a/docs/userguide/src/site/pages/thredds/TdmRef.md +++ b/docs/userguide/src/site/pages/thredds/TdmRef.md @@ -84,7 +84,7 @@ bg The TDM scans the files in the feature collection, and when it detects that the collection has changed, rewrites the index files. If enabled, it will send a trigger message to the TDS, and the TDS will reload that dataset. To enable this, you must configure the TDS with the `tdsTrigger` role, and add the user `tdm` with that role. -Typically, you do that by editing the `${tomcat_home}/conf/tomcat-user.xml` file, e.g.: +Typically, you do that by editing the `${tomcat_home}/conf/tomcat-users.xml` file, e.g.: ~~~xml @@ -150,16 +150,12 @@ Point the TDM to the content directory using `-Dtds.content.root.path= - ~~~ * `` element for the TDM * `rewrite="test"` tells the TDM to test for dataset changes * `rescan="0 0/15 * * * ? *"` rescan directories every 15 minutes. -* `` element for the TDS - * `startup="never"` tells the TDS to read in the `featureCollection` when starting up, using the existing indices - * `trigger="allow"` enables the TDS to receive messages from the TDM when the dataset has changed ## `GCPass1`