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
The JAR can be retrieved by compiling the project:
@@ -227,7 +227,7 @@ These are instructions on what to do when we release a new version of the knowle
227
227
The code conventions of the knowledge-engine can be found in the `/ide` folder in the Eclipse IDE format. The format can often also be imported in other Java IDEs like IntelliJ, VSCode or Netbeans.
228
228
229
229
## (advanced) Administering a Knowledge Engine runtime
230
-
To start a new instance of the REST API knowledge engine version 1.3.2, make sure you have `git checkout 1.3.2` the tag `1.3.2`. Now make sure you run the `mvn clean install` command successfully from the root of the repository.
230
+
To start a new instance of the REST API knowledge engine version 1.4.0, make sure you have `git checkout 1.4.0` the tag `1.4.0`. Now make sure you run the `mvn clean install` command successfully from the root of the repository.
231
231
232
232
### Starting the Knowledge Engine in local mode
233
233
When no additional configuration parameters are provided, the Knowledge Engine will by default run in local mode. This means you can create multiple smart connectors that can communicate with each other through the REST API, but the Knowledge Engine will not connect to a knowledge directory and will not be able to connect with smart connectors running in other runtimes.
@@ -241,13 +241,13 @@ cd smart-connector-rest-dist/target
241
241
Finally, start the server (note that you can configure a log file by including the `-Dorg.slf4j.simpleLogger.logFile=ke.log` system property to the JVM):
If you want to run in it in the background, you can use the `nohup` linux command (which does not use the simpleLogger configuration system property, but redirects the standard err/out):
The `nohup` command can be used to run the process in the background. On overview of the registered Knowledge Engine runtimes can be found on `http://localhost:8080/ker/` (or another host or port if you desire).
Copy file name to clipboardExpand all lines: docs/docs/get-started/smart-connector.md
+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
@@ -9,7 +9,7 @@ import TabItem from '@theme/TabItem';
9
9
This page describes how to connect to an (existing) Knowledge Network using a Smart Connector.
10
10
11
11
To connect to a Knowledge Network, you need a Knowledge Engine Runtime (KER).
12
-
Every KER in distributed mode consists of two APIs: [Knowledge Engine Developer REST API](https://github.com/TNO/knowledge-engine/blob/1.3.2/smart-connector-rest-server/src/main/resources/openapi-sc.yaml) and the [Inter-Knowledge Engine Runtime API](https://github.com/TNO/knowledge-engine/blob/1.3.2/smart-connector/src/main/resources/openapi-inter-ker.yaml).
12
+
Every KER in distributed mode consists of two APIs: [Knowledge Engine Developer REST API](https://github.com/TNO/knowledge-engine/blob/1.4.0/smart-connector-rest-server/src/main/resources/openapi-sc.yaml) and the [Inter-Knowledge Engine Runtime API](https://github.com/TNO/knowledge-engine/blob/1.4.0/smart-connector/src/main/resources/openapi-inter-ker.yaml).
13
13
The former is started on port `8280` by default, and you use this API to register your Knowledge Base and Knowledge Interactions.
14
14
The latter API is meant for internal communication between KERs and you do not need to use it yourself.
15
15
However, you do need to make sure this API is reachable for other KERs in the Knowledge Network.
Copy file name to clipboardExpand all lines: examples/edc-example/README.md
+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
@@ -53,8 +53,8 @@ One knowledge base asks for information and the other two provide an answer to t
53
53
### Executing the example
54
54
Execute the following steps to run the example:
55
55
1. In this project, execute a `mvn clean install`.
56
-
2. In the `knowledge-directory` directory in this project, execute `docker build . -t testkd:1.3.3-SNAPSHOT`.
57
-
3. In the `smart-connector-rest-dist` directory in this project, execute `docker build . -t testsc:1.3.3-SNAPSHOT`.
56
+
2. In the `knowledge-directory` directory in this project, execute `docker build . -t testkd:1.4.0`.
57
+
3. In the `smart-connector-rest-dist` directory in this project, execute `docker build . -t testsc:1.4.0`.
58
58
4. In the `examples/edc-example` directory in this project, execute `docker compose build`.
59
59
5. In the `examples/edc-example` directory in this project, execute `docker compose up -d tke-edc-one tke-edc-two tke-edc-three`. This starts three EDC-IDS Connectors.
60
60
6. Wait around 10 seconds to give the EDC Connectors time to finish setting up. Then, execute `docker compose up -d` to start three KERs, three linked Knowledge Bases and a Knowledge Directory.
0 commit comments