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
This needs only to be done if `include.module.scheduler` in `extensions/build.properties` was set to `false`. Then eXistdb has to be rebuild to enable the scheduler module. Shutdown the database and in the root of the eXistdb project simply call
44
-
45
-
```shell
46
-
./build.sh
47
-
```
48
-
49
-
After starting the database again, the remote monitoring tab should show no more error warnings.
36
+
#### Adding an instance to monitor
50
37
51
-
#### Adding an eXistdb instance to monitor
52
-
53
-
For each eXistdb instance to monitor its url and its unique token is needed. The token can be found in the data directory on the filesystem . The file is called `jmxservlet.token`. The path to the data directory can be found in `$existdb_home/conf.xml`
38
+
For each instance to monitor its URL and its unique token is needed. The token can be found in the data directory on the filesystem . The file is called `jmxservlet.token`. The path to the data directory can be found in `etc/conf.xml`
Each eXistdb installation to monitor is added as an instance entry at `/db/apps/monex/instances.xml`.
44
+
Each installation to monitor is added as an instance entry at `/db/apps/monex/instances.xml`.
60
45
61
46
#### Sample Monex Instances
62
47
@@ -81,31 +66,45 @@ In the Monex Remote Monitoring tab click "Run" to start all remote monitoring jo
81
66
82
67
If you wish to build Monex from source code you should follow these steps:
83
68
84
-
1. Ensure you have Git, Apache Maven 3.3+, and Java JDK 8 installed and available:
69
+
1. Ensure you have Git, GnuPG, Apache Maven 3.3+, and Java JDK 21 installed and available. If you wish to run the test suite, you will also need to have Docker installed.
This project is configured to use the [Maven Release Plugin](https://maven.apache.org/maven-release/maven-release-plugin/) to make creating and subsequently publishing a release easy.
@@ -126,17 +125,24 @@ Only users with push access to the GitHub repo can act as release manager.
126
125
Before creating the release, check if:
127
126
128
127
-[ ] the changelog is up-to-date for the planned release?
129
-
-[ ] the target versions for eXistdb are correctly declared in `pom.xml`?
128
+
-[ ] the target versions for the Database API and Implementation are correctly declared in `monex-parent/pom.xml`?
You will be prompted for the answers to a few questions along the way. The default response will be provided for you, and you can simply press "Enter" (or "Return") to accept it. Alternatively you may enter your own value and press "Enter" (or "Return").
161
167
162
168
```bash
163
-
What is the release version for"monex"? (org.exist-db.apps:monex) 2.3.1: : 2.4.0
164
-
What is SCM release tag or label for"monex"? (org.exist-db.apps:monex) 2.4.0: :
165
-
What is the new development version for"monex"? (org.exist-db.apps:monex) 2.4.1-SNAPSHOT: :
169
+
What is the release version for"monex"? (org.exist-db.apps:monex) 4.3.0:
170
+
What is SCM release tag or label for"monex"? (org.exist-db.apps:monex) 4.3.0:
171
+
What is the new development version for"monex"? (org.exist-db.apps:monex) 4.3.1-SNAPSHOT:
166
172
```
167
173
168
174
- For the `release version`, please sensibly consider using the next appropriate [SemVer 2.0.0](https://semver.org/) version number.
0 commit comments