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

Updates to TDM docs #557

Merged
merged 1 commit into from
Jan 9, 2025
Merged

Updates to TDM docs #557

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
6 changes: 1 addition & 5 deletions docs/adminguide/src/site/pages/reference/TdmRef.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
<?xml version='1.0' encoding='utf-8'?>
Expand Down Expand Up @@ -152,16 +152,12 @@ Point the TDM to the content directory using `-Dtds.content.root.path=<content d
olderThan="5 min"/>

<tdm rewrite="true" rescan="0 0/15 * * * ? *" trigger="allow"/>
<update startup="never" trigger="allow" />
</featureCollection>
~~~

* `<tdm>` element for the TDM
* `rewrite="test"` tells the TDM to test for dataset changes
* `rescan="0 0/15 * * * ? *"` rescan directories every 15 minutes.
* `<update>` 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`

Expand Down
6 changes: 1 addition & 5 deletions docs/devguide/src/site/pages/thredds/TdmRef.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
<?xml version='1.0' encoding='utf-8'?>
Expand Down Expand Up @@ -150,16 +150,12 @@ Point the TDM to the content directory using `-Dtds.content.root.path=<content d
olderThan="5 min"/>

<tdm rewrite="true" rescan="0 0/15 * * * ? *" trigger="allow"/>
<update startup="never" trigger="allow" />
</featureCollection>
~~~

* `<tdm>` element for the TDM
* `rewrite="test"` tells the TDM to test for dataset changes
* `rescan="0 0/15 * * * ? *"` rescan directories every 15 minutes.
* `<update>` 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`

Expand Down
6 changes: 1 addition & 5 deletions docs/quickstart/src/site/pages/thredds/TdmRef.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
<?xml version='1.0' encoding='utf-8'?>
Expand Down Expand Up @@ -150,16 +150,12 @@ Point the TDM to the content directory using `-Dtds.content.root.path=<content d
olderThan="5 min"/>

<tdm rewrite="true" rescan="0 0/15 * * * ? *" trigger="allow"/>
<update startup="never" trigger="allow" />
</featureCollection>
~~~

* `<tdm>` element for the TDM
* `rewrite="test"` tells the TDM to test for dataset changes
* `rescan="0 0/15 * * * ? *"` rescan directories every 15 minutes.
* `<update>` 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`

Expand Down
6 changes: 1 addition & 5 deletions docs/userguide/src/site/pages/thredds/TdmRef.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
<?xml version='1.0' encoding='utf-8'?>
Expand Down Expand Up @@ -150,16 +150,12 @@ Point the TDM to the content directory using `-Dtds.content.root.path=<content d
olderThan="5 min"/>

<tdm rewrite="true" rescan="0 0/15 * * * ? *" trigger="allow"/>
<update startup="never" trigger="allow" />
</featureCollection>
~~~

* `<tdm>` element for the TDM
* `rewrite="test"` tells the TDM to test for dataset changes
* `rescan="0 0/15 * * * ? *"` rescan directories every 15 minutes.
* `<update>` 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`

Expand Down
Loading