You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@streampipes.apache.org by ri...@apache.org on 2025/12/15 14:55:49 UTC
(streampipes-website) branch dev updated: Release 0 98 0 (#224)
This is an automated email from the ASF dual-hosted git repository.
riemer pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/streampipes-website.git
The following commit(s) were added to refs/heads/dev by this push:
new ce5173495 Release 0 98 0 (#224)
ce5173495 is described below
commit ce517349503f52cc081129853986b9d467247ef7
Author: Philipp Zehnder <te...@users.noreply.github.com>
AuthorDate: Mon Dec 15 15:55:43 2025 +0100
Release 0 98 0 (#224)
* Update version on website
* Update docs to version 0.98.0
* Add warning that default broker changed
---
docs/01_try-installation.md | 2 +-
website-v2/docusaurus.config.js | 2 +-
website-v2/src/components/download/DownloadBox.tsx | 27 +-
website-v2/src/pages/download.tsx | 2 +-
.../version-0.98.0}/01_try-installation.md | 2 +-
.../version-0.98.0/01_try-overview.md | 134 +++++
.../version-0.98.0/01_try-tutorial.md | 20 +
.../version-0.98.0/02_concepts-adapter.md | 7 +
.../version-0.98.0/02_concepts-data-streams.md | 7 +
.../version-0.98.0/02_concepts-glossary.md | 7 +
.../version-0.98.0/02_concepts-overview.md | 46 ++
.../version-0.98.0/02_concepts-pipeline.md | 7 +
.../version-0.98.0/02_introduction.md | 85 +++
.../version-0.98.0/03_use-configurations.md | 48 ++
.../version-0.98.0/03_use-connect.md | 72 +++
.../version-0.98.0/03_use-dashboard.md | 66 +++
.../version-0.98.0/03_use-data-explorer.md | 102 ++++
.../03_use-install-pipeline-elements.md | 9 +
.../version-0.98.0/03_use-managing-pipelines.md | 52 ++
.../version-0.98.0/03_use-notifications.md | 25 +
.../version-0.98.0/03_use-pipeline-editor.md | 62 +++
.../03_use-programmatically-create-adapters.md | 154 ++++++
.../03_use-programmatically-create-pipelines.md | 164 ++++++
.../05_deploy-choosing-the-right-flavor.md | 47 ++
.../version-0.98.0/05_deploy-docker.md | 92 ++++
.../05_deploy-environment-variables.md | 88 +++
.../version-0.98.0/05_deploy-kubernetes.md | 269 +++++++++
.../version-0.98.0/05_deploy-retention-config.md | 207 +++++++
.../version-0.98.0/05_deploy-security.md | 178 ++++++
.../version-0.98.0/05_deploy-use-ssl.md | 35 ++
.../version-0.98.0/06_extend-archetypes.md | 46 ++
.../versioned_docs/version-0.98.0/06_extend-cli.md | 190 +++++++
.../version-0.98.0/06_extend-client.md | 204 +++++++
.../version-0.98.0/06_extend-customize-ui.md | 226 ++++++++
.../version-0.98.0/06_extend-first-processor.md | 54 ++
.../version-0.98.0/06_extend-sdk-event-model.md | 141 +++++
.../version-0.98.0/06_extend-sdk-functions.md | 127 +++++
.../version-0.98.0/06_extend-sdk-migration-sd.md | 117 ++++
.../version-0.98.0/06_extend-sdk-migrations.md | 179 ++++++
.../06_extend-sdk-output-strategies.md | 348 ++++++++++++
.../06_extend-sdk-static-properties.md | 267 +++++++++
.../06_extend-sdk-stream-requirements.md | 181 ++++++
.../version-0.98.0/06_extend-setup.md | 50 ++
.../version-0.98.0/06_extend-tutorial-adapters.md | 612 +++++++++++++++++++++
.../06_extend-tutorial-data-processors.md | 454 +++++++++++++++
.../06_extend-tutorial-data-sinks.md | 272 +++++++++
.../version-0.98.0/07_technicals-architecture.md | 110 ++++
.../version-0.98.0/07_technicals-messaging.md | 65 +++
.../07_technicals-runtime-wrappers.md | 37 ++
.../version-0.98.0/07_technicals-user-guidance.md | 7 +
.../versioned_docs/version-0.98.0/08_debugging.md | 7 +
.../versioned_docs/version-0.98.0/08_monitoring.md | 7 +
.../versioned_docs/version-0.98.0/09_contribute.md | 17 +
.../versioned_docs/version-0.98.0/09_get-help.md | 25 +
.../version-0.98.0/faq-common-problems.md | 73 +++
...he.streampipes.connect.adapters.image.stream.md | 38 ++
.../org.apache.streampipes.connect.adapters.iss.md | 39 ++
...mpipes.connect.iiot.adapters.influxdb.stream.md | 41 ++
...che.streampipes.connect.iiot.adapters.iolink.md | 90 +++
...streampipes.connect.iiot.adapters.netio.mqtt.md | 64 +++
...streampipes.connect.iiot.adapters.netio.rest.md | 64 +++
...apache.streampipes.connect.iiot.adapters.oi4.md | 88 +++
...ache.streampipes.connect.iiot.adapters.opcua.md | 76 +++
...s.connect.iiot.adapters.plc4x.generic.ab-eth.md | 100 ++++
...ipes.connect.iiot.adapters.plc4x.generic.ads.md | 108 ++++
...onnect.iiot.adapters.plc4x.generic.bacnet-ip.md | 102 ++++
....connect.iiot.adapters.plc4x.generic.canopen.md | 100 ++++
...ipes.connect.iiot.adapters.plc4x.generic.eip.md | 102 ++++
...nnect.iiot.adapters.plc4x.generic.genericcan.md | 99 ++++
....iiot.adapters.plc4x.generic.iec-60870-5-104.md | 100 ++++
...onnect.iiot.adapters.plc4x.generic.knxnet-ip.md | 114 ++++
...es.connect.iiot.adapters.plc4x.generic.logix.md | 105 ++++
...ect.iiot.adapters.plc4x.generic.modbus-ascii.md | 102 ++++
...nnect.iiot.adapters.plc4x.generic.modbus-rtu.md | 102 ++++
...nnect.iiot.adapters.plc4x.generic.modbus-tcp.md | 102 ++++
...ct.iiot.adapters.plc4x.generic.open-protocol.md | 100 ++++
...connect.iiot.adapters.plc4x.generic.profinet.md | 102 ++++
...pipes.connect.iiot.adapters.plc4x.generic.s7.md | 119 ++++
...reampipes.connect.iiot.adapters.plc4x.modbus.md | 75 +++
...e.streampipes.connect.iiot.adapters.plc4x.s7.md | 96 ++++
...apache.streampipes.connect.iiot.adapters.ros.md | 64 +++
...ipes.connect.iiot.adapters.simulator.machine.md | 92 ++++
...treampipes.connect.iiot.protocol.stream.file.md | 90 +++
...treampipes.connect.iiot.protocol.stream.http.md | 38 ++
...ipes.connect.iiot.protocol.stream.httpserver.md | 51 ++
...reampipes.connect.iiot.protocol.stream.kafka.md | 38 ++
...treampipes.connect.iiot.protocol.stream.mqtt.md | 53 ++
...treampipes.connect.iiot.protocol.stream.nats.md | 69 +++
...eampipes.connect.iiot.protocol.stream.pulsar.md | 38 ++
...mpipes.connect.iiot.protocol.stream.rocketmq.md | 38 ++
...eampipes.connect.iiot.protocol.stream.tubemq.md | 54 ++
.../org.apache.streampipes.connectors.ros.sink.md | 60 ++
...ssification.jvm.generic-image-classification.md | 52 ++
...cessor.imageclassification.jvm.image-cropper.md | 43 ++
...essor.imageclassification.jvm.image-enricher.md | 43 ++
...ampipes.processor.imageclassification.qrcode.md | 68 +++
...pipes.processors.changedetection.jvm.welford.md | 72 +++
...e.streampipes.processors.enricher.jvm.jseval.md | 55 ++
...processors.enricher.jvm.processor.expression.md | 61 ++
...rocessors.enricher.jvm.processor.limitsalert.md | 113 ++++
...sors.enricher.jvm.processor.limitsenrichment.md | 104 ++++
...rocessors.enricher.jvm.processor.math.mathop.md | 56 ++
...ors.enricher.jvm.processor.math.staticmathop.md | 56 ++
...ocessors.enricher.jvm.processor.trigonometry.md | 56 ++
...eampipes.processors.enricher.jvm.valuechange.md | 52 ++
...e.streampipes.processors.filters.jvm.compose.md | 50 ++
...he.streampipes.processors.filters.jvm.enrich.md | 47 ++
...che.streampipes.processors.filters.jvm.limit.md | 70 +++
...che.streampipes.processors.filters.jvm.merge.md | 57 ++
...ampipes.processors.filters.jvm.movingaverage.md | 46 ++
...pipes.processors.filters.jvm.numericalfilter.md | 56 ++
...s.processors.filters.jvm.numericaltextfilter.md | 67 +++
...ocessors.filters.jvm.processor.booleanfilter.md | 52 ++
...e.streampipes.processors.filters.jvm.project.md | 48 ++
...he.streampipes.processors.filters.jvm.schema.md | 46 ++
...pache.streampipes.processors.filters.jvm.sdt.md | 85 +++
...treampipes.processors.filters.jvm.textfilter.md | 53 ++
...streampipes.processors.filters.jvm.threshold.md | 56 ++
...ampipes.processors.filters.jvm.throughputmon.md | 56 ++
...cessors.geo.jvm.jts.processor.buffergeometry.md | 95 ++++
...processors.geo.jvm.jts.processor.bufferpoint.md | 82 +++
...mpipes.processors.geo.jvm.jts.processor.epsg.md | 64 +++
...ssors.geo.jvm.jts.processor.latlngtojtspoint.md | 73 +++
...rocessors.geo.jvm.jts.processor.reprojection.md | 68 +++
....processors.geo.jvm.jts.processor.trajectory.md | 83 +++
...ors.geo.jvm.jts.processor.validation.complex.md | 86 +++
...sors.geo.jvm.jts.processor.validation.simple.md | 80 +++
...tlong.processor.distancecalculator.haversine.md | 61 ++
...processor.distancecalculator.haversinestatic.md | 74 +++
...eo.jvm.latlong.processor.geocoder.googlemaps.md | 61 ++
....latlong.processor.geocoder.googlemapsstatic.md | 62 +++
...vm.latlong.processor.revgeocoder.geocityname.md | 67 +++
...rs.geo.jvm.latlong.processor.speedcalculator.md | 59 ++
...g.apache.streampipes.processors.siddhi.count.md | 66 +++
...pache.streampipes.processors.siddhi.increase.md | 65 +++
....streampipes.processors.siddhi.listcollector.md | 51 ++
...che.streampipes.processors.siddhi.listfilter.md | 53 ++
...treampipes.processors.siddhi.numericalfilter.md | 63 +++
...rg.apache.streampipes.processors.siddhi.topk.md | 53 ++
...treampipes.processors.textmining.jvm.chunker.md | 69 +++
...ampipes.processors.textmining.jvm.namefinder.md | 65 +++
...pipes.processors.textmining.jvm.partofspeech.md | 62 +++
....processors.textmining.jvm.sentencedetection.md | 59 ++
...eampipes.processors.textmining.jvm.tokenizer.md | 59 ++
...sors.transformation.jvm.booloperator.counter.md | 66 +++
...ors.transformation.jvm.booloperator.inverter.md | 51 ++
...sors.transformation.jvm.booloperator.logical.md | 42 ++
....transformation.jvm.booloperator.timekeeping.md | 70 +++
...essors.transformation.jvm.booloperator.timer.md | 58 ++
....processors.transformation.jvm.changed-value.md | 46 ++
...es.processors.transformation.jvm.count-array.md | 55 ++
...es.processors.transformation.jvm.csvmetadata.md | 77 +++
...pipes.processors.transformation.jvm.datetime.md | 78 +++
...processors.transformation.jvm.duration-value.md | 51 ++
...s.processors.transformation.jvm.field-mapper.md | 74 +++
...es.processors.transformation.jvm.fieldhasher.md | 55 ++
...es.processors.transformation.jvm.fieldrename.md | 59 ++
....transformation.jvm.measurementunitconverter.md | 53 ++
...ansformation.jvm.processor.booloperator.edge.md | 58 ++
...nsformation.jvm.processor.booloperator.state.md | 63 +++
...formation.jvm.processor.state.labeler.number.md | 58 ++
....transformation.jvm.processor.staticmetadata.md | 74 +++
...formation.jvm.processor.stringoperator.state.md | 51 ++
...nsformation.jvm.processor.timestampextractor.md | 58 ++
...eampipes.processors.transformation.jvm.round.md | 72 +++
...es.processors.transformation.jvm.split-array.md | 60 ++
...rs.transformation.jvm.stringoperator.counter.md | 65 +++
...sors.transformation.jvm.stringoperator.timer.md | 66 +++
...s.processors.transformation.jvm.taskduration.md | 50 ++
...sors.transformation.jvm.transform-to-boolean.md | 53 ++
...che.streampipes.sinks.brokers.jvm.bufferrest.md | 58 ++
...org.apache.streampipes.sinks.brokers.jvm.jms.md | 60 ++
...g.apache.streampipes.sinks.brokers.jvm.kafka.md | 61 ++
...rg.apache.streampipes.sinks.brokers.jvm.mqtt.md | 61 ++
...rg.apache.streampipes.sinks.brokers.jvm.nats.md | 78 +++
....apache.streampipes.sinks.brokers.jvm.pulsar.md | 63 +++
...pache.streampipes.sinks.brokers.jvm.rabbitmq.md | 73 +++
...rg.apache.streampipes.sinks.brokers.jvm.rest.md | 52 ++
...pache.streampipes.sinks.brokers.jvm.rocketmq.md | 59 ++
....apache.streampipes.sinks.brokers.jvm.tubemq.md | 61 ++
...ache.streampipes.sinks.brokers.jvm.websocket.md | 52 ++
...org.apache.streampipes.sinks.databases.ditto.md | 73 +++
...ache.streampipes.sinks.databases.jvm.couchdb.md | 63 +++
...che.streampipes.sinks.databases.jvm.influxdb.md | 85 +++
...apache.streampipes.sinks.databases.jvm.iotdb.md | 91 +++
...apache.streampipes.sinks.databases.jvm.opcua.md | 65 +++
...e.streampipes.sinks.databases.jvm.postgresql.md | 73 +++
...apache.streampipes.sinks.databases.jvm.redis.md | 87 +++
...ache.streampipes.sinks.internal.jvm.datalake.md | 97 ++++
....streampipes.sinks.internal.jvm.notification.md | 63 +++
...he.streampipes.sinks.notifications.jvm.email.md | 73 +++
....streampipes.sinks.notifications.jvm.msteams.md | 86 +++
...treampipes.sinks.notifications.jvm.onesignal.md | 63 +++
...he.streampipes.sinks.notifications.jvm.slack.md | 66 +++
...streampipes.sinks.notifications.jvm.telegram.md | 70 +++
.../version-0.98.0/user-guide-first-steps.md | 209 +++++++
.../version-0.98.0/user-guide-tour.md | 305 ++++++++++
.../version-0.98.0-sidebars.json | 210 +++++++
website-v2/versions.json | 1 +
199 files changed, 16061 insertions(+), 7 deletions(-)
diff --git a/docs/01_try-installation.md b/docs/01_try-installation.md
index 55d3082cd..bd92e48e9 100644
--- a/docs/01_try-installation.md
+++ b/docs/01_try-installation.md
@@ -33,7 +33,7 @@ best experience), Firefox or Edge.
## Install StreamPipes
-<DownloadSection version={'0.97.0'} releaseDate={'2025-02-17'}></DownloadSection>
+<DownloadSection version={'0.98.0'} releaseDate={'2025-12-15'}></DownloadSection>
## Setup StreamPipes
diff --git a/website-v2/docusaurus.config.js b/website-v2/docusaurus.config.js
index 8d377aa65..f58389d71 100644
--- a/website-v2/docusaurus.config.js
+++ b/website-v2/docusaurus.config.js
@@ -100,7 +100,7 @@ module.exports = {
textColor: 'white',
isCloseable: false,
content:
- 'Apache StreamPipes 0.97.0 is available! βοΈ',
+ 'Apache StreamPipes 0.98.0 is available! βοΈ',
},
"image": "img/favicon.png",
"footer": {
diff --git a/website-v2/src/components/download/DownloadBox.tsx b/website-v2/src/components/download/DownloadBox.tsx
index a7269aeb3..3e5af5ec7 100644
--- a/website-v2/src/components/download/DownloadBox.tsx
+++ b/website-v2/src/components/download/DownloadBox.tsx
@@ -1,5 +1,4 @@
-import React, { FC } from 'react';
-
+import * as React from 'react';
const DownloadBox = (props) => {
return (
@@ -47,6 +46,29 @@ const DownloadBox = (props) => {
</tbody>
</table>
</div>
+
+ <div className="row">
+ <div className="col-12" style={{paddingLeft: '20px', paddingRight: '20px'}}>
+ <div
+ className="alert alert-danger"
+ role="alert"
+ aria-live="polite"
+ style={{
+ backgroundColor: '#f8d7da',
+ color: '#721c24',
+ border: '1px solid #f5c6cb',
+ padding: '15px',
+ marginTop: '20px',
+ marginBottom: '20px',
+ borderRadius: '4px'
+ }}
+ >
+ <i className="fas fa-exclamation-triangle" style={{marginRight: '8px'}} aria-hidden="true"></i>
+ <strong>Important:</strong> If you update from 0.97.0 to 0.98.0 and have been using the Kafka broker, you must use <strong>docker-compose.kafka.yml</strong> to run StreamPipes. The default docker-compose now uses NATS as the broker. Existing Kafka-based instances cannot be migrated automatically and cannot simply be switched to the default compose file.
+ </div>
+ </div>
+ </div>
+
<div className="row">
<div className="alert alert-info" role="alert" style={{marginLeft: '20px', marginRight: '20px'}}>
<p>
@@ -69,4 +91,3 @@ const DownloadBox = (props) => {
}
export default DownloadBox;
-
diff --git a/website-v2/src/pages/download.tsx b/website-v2/src/pages/download.tsx
index c4c16fb15..ad10e19ea 100644
--- a/website-v2/src/pages/download.tsx
+++ b/website-v2/src/pages/download.tsx
@@ -29,7 +29,7 @@ const Downloads: FC = () => (
<div className="installation-manual-part">
<h5 className="feature-item-margin"><span className="feature-highlights-bg">Installation</span></h5>
<ul>
- <DownloadSection version={'0.97.0'} showMoreInfo={true} releaseDate={'2025-02-17'}></DownloadSection>
+ <DownloadSection version={'0.98.0'} showMoreInfo={true} releaseDate={'2025-12-15'}></DownloadSection>
<hr/>
</ul>
</div>
diff --git a/docs/01_try-installation.md b/website-v2/versioned_docs/version-0.98.0/01_try-installation.md
similarity index 97%
copy from docs/01_try-installation.md
copy to website-v2/versioned_docs/version-0.98.0/01_try-installation.md
index 55d3082cd..bd92e48e9 100644
--- a/docs/01_try-installation.md
+++ b/website-v2/versioned_docs/version-0.98.0/01_try-installation.md
@@ -33,7 +33,7 @@ best experience), Firefox or Edge.
## Install StreamPipes
-<DownloadSection version={'0.97.0'} releaseDate={'2025-02-17'}></DownloadSection>
+<DownloadSection version={'0.98.0'} releaseDate={'2025-12-15'}></DownloadSection>
## Setup StreamPipes
diff --git a/website-v2/versioned_docs/version-0.98.0/01_try-overview.md b/website-v2/versioned_docs/version-0.98.0/01_try-overview.md
new file mode 100644
index 000000000..29a059d4a
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/01_try-overview.md
@@ -0,0 +1,134 @@
+---
+id: user-guide-introduction
+title: Apache StreamPipes Documentation
+sidebar_label: Overview
+---
+
+This is the documentation of Apache StreamPipes.
+
+<img class="docs-image docs-image-small docs-image-no-shadow" style={{padding: '10px'}} src="
+/img/01_try-overview/01_streampipes-overview.png" alt="StreamPipes Overview"/>
+
+
+<div class="container grid col-3">
+ <div class="column">
+ <div class="toc-box">
+ <div class="toc-header border-thin">
+ π Try
+ </div>
+ <div class="toc-content">
+ <div class="toc-section-header"><b>Your first steps with Apache StreamPipes:</b></div>
+ <a href="../try-installation/">Install StreamPipes π</a>
+ </div>
+ </div>
+ </div>
+ <div class="column">
+ <div class="toc-box">
+ <div class="toc-header border-thin">
+ π‘ Concepts
+ </div>
+ <div class="toc-content">
+ <div class="toc-section-header"><b>Learn about some general concepts of StreamPipes:</b></div>
+ <a href="../concepts-overview/">Overview π</a>
+ </div>
+ </div>
+ </div>
+ <div class="column">
+ <div class="toc-box">
+ <div class="toc-header border-thin">
+ π Use
+ </div>
+ <div class="toc-content">
+ <div class="toc-section-header"><b>Learn how to use the various modules of StreamPipes:</b></div>
+ <a href="../use-connect/">StreamPipes Connect π</a>,
+ <a href="../use-pipeline-editor/">Pipeline Editor π</a>,
+ <a href="../use-managing-pipelines/">Managing Pipelines π</a>,
+ <a href="../use-live-dashboard/">Live Dashboard π</a>,
+ <a href="../use-data-explorer/">Data Explorer π</a>,
+ <a href="../use-notifications/">Notifications π</a>
+ </div>
+ </div>
+ </div>
+ <div class="column">
+ <div class="toc-box">
+ <div class="toc-header border-thin">
+ π Pipeline Elements
+ </div>
+ <div class="toc-content">
+ <div class="toc-section-header"><b>Available pipeline elements in StreamPipes:</b></div>
+ <a href="../pe/org.apache.streampipes.connect.iiot.protocol.stream.kafka/">Adapters π</a>,
+ <a href="../pe/org.apache.streampipes.processors.transformation.jvm.booloperator.counter/">Data Processors π</a>,
+ <a href="../pe/org.apache.streampipes.sinks.databases.jvm.couchdb/">Data Sinks π</a>
+ </div>
+ </div>
+ </div>
+ <div class="column">
+ <div class="toc-box">
+ <div class="toc-header border-thin">
+ β‘ Deploy
+ </div>
+ <div class="toc-content">
+ <div class="toc-section-header"><b>How to set up StreamPipes in test and production environments:</b></div>
+ <a href="../deploy-docker/">Docker π</a>,
+ <a href="../deploy-kubernetes/">Kubernetes π</a>,
+ <a href="../deploy-use-ssl/">Use SSL π</a>
+ </div>
+ </div>
+ </div>
+ <div class="column">
+ <div class="toc-box">
+ <div class="toc-header border-thin">
+ π» Extend
+ </div>
+ <div class="toc-content">
+ <div class="toc-section-header"><b>Write your own pipeline elements for StreamPipes:</b></div>
+ <a href="../extend-setup/">Development Setup π</a>, <a href="../extend-cli/">CLI π</a>, <a href="../extend-archetypes/">Maven Archetypes π</a>,
+ <a href="../extend-tutorial-data-sources/">Tutorial Data Sources π</a>,
+ <a href="../extend-tutorial-data-processors">Tutorial Data Processors π</a>,
+ <a href="../extend-tutorial-data-sinks/">Tutorial Data Sinks π</a>,
+ <a href="../extend-sdk-event-model.html/">Event Model π</a>,
+ <a href="../extend-sdk-stream-requirements/">Stream Requirements π</a>,
+ <a href="../extend-sdk-static-properties/">Static Properties π</a>,
+ <a href="../extend-sdk-output-strategies/">Output Strategies π</a>
+ </div>
+ </div>
+ </div>
+ <div class="column">
+ <div class="toc-box">
+ <div class="toc-header border-thin">
+ π§ Technicals
+ </div>
+ <div class="toc-content">
+ <div class="toc-section-header"><b>Learn about technical concepts behind the curtain:</b></div>
+ <a href="../technicals-architecture/">Architecture π</a>,
+ <a href="../technicals-user-guidance/">User Guidance π </a>,
+ <a href="../technicals-runtime-wrappers/">Runtime Wrappers π</a>,
+ <a href="../technicals-messaging/">Messaging π</a>,
+ <a href="../technicals-configuration/">Configuration π</a>
+ </div>
+ </div>
+ </div>
+ <div class="column">
+ <div class="toc-box">
+ <div class="toc-header border-thin">
+ πͺ Community
+ </div>
+ <div class="toc-content">
+ <div class="toc-section-header"><b>Get support and learn how to contribute to StreamPipes:</b></div>
+ <a href="../community-get-help/">Get Help π</a>,
+ <a href="../community-contribute/">Contribute π</a>
+ </div>
+ </div>
+ </div>
+ <div class="column">
+ <div class="toc-box">
+ <div class="toc-header border-thin">
+ π StreamPipes Python
+ </div>
+ <div class="toc-content">
+ <div class="toc-section-header"><b>Discover what we offer for the Python world:</b></div>
+ <a href="/docs/docs/python/latest/">Python Documentation π</a>
+ </div>
+ </div>
+ </div>
+</div>
diff --git a/website-v2/versioned_docs/version-0.98.0/01_try-tutorial.md b/website-v2/versioned_docs/version-0.98.0/01_try-tutorial.md
new file mode 100644
index 000000000..c13d6f1dc
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/01_try-tutorial.md
@@ -0,0 +1,20 @@
+---
+id: try-tutorial
+title: Interactive Tutorial
+sidebar_label: Interactive Tutorial
+---
+
+Once you've installed StreamPipes and see the home screen, you'll see a number of modules that are part of the StreamPipes toolbox.
+As a first step, you might be interested in taking the interactive tutorial that helps you create your first pipeline.
+Switch to the **Pipeline Editor** and you will see a dialog that asks you for the start of the interactive tutorial:
+
+<img className="docs-image" src="/img/01_try-tutorial/01_tutorial-welcome.png" alt="Tutorial Welcome Page"/>
+
+Click **Start Tour** to start the tour. In this tour, you'll build a simple pipeline that monitors (simulated) live data from a water tank system.
+Within the tour, perform the actions as recommended and click **Next** to trigger the next steps. Some tour steps won't require to select **Next**, but wait for you to take the recommended action.
+You can cancel the tour anytime by clicking the **Exit Tour** button.
+
+<img className="docs-image" src="/img/01_try-tutorial/02_tutorial-process.png" alt="Tutorial Welcome Page"/>
+
+Now after you've built your first pipeline, you might be interested in reading about some of our core [concepts](concepts-overview)
+
diff --git a/website-v2/versioned_docs/version-0.98.0/02_concepts-adapter.md b/website-v2/versioned_docs/version-0.98.0/02_concepts-adapter.md
new file mode 100644
index 000000000..a94c38268
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/02_concepts-adapter.md
@@ -0,0 +1,7 @@
+---
+id: concepts-adapter
+title: Data Adapters
+sidebar_label: Data Adapters
+---
+
+tbd
diff --git a/website-v2/versioned_docs/version-0.98.0/02_concepts-data-streams.md b/website-v2/versioned_docs/version-0.98.0/02_concepts-data-streams.md
new file mode 100644
index 000000000..329f9b908
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/02_concepts-data-streams.md
@@ -0,0 +1,7 @@
+---
+id: concepts-data-streams
+title: Data Streams
+sidebar_label: Data Streams
+---
+
+tbd
\ No newline at end of file
diff --git a/website-v2/versioned_docs/version-0.98.0/02_concepts-glossary.md b/website-v2/versioned_docs/version-0.98.0/02_concepts-glossary.md
new file mode 100644
index 000000000..b401d1829
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/02_concepts-glossary.md
@@ -0,0 +1,7 @@
+---
+id: concepts-glossary
+title: Glossary
+sidebar_label: Glossary
+---
+
+tbd
\ No newline at end of file
diff --git a/website-v2/versioned_docs/version-0.98.0/02_concepts-overview.md b/website-v2/versioned_docs/version-0.98.0/02_concepts-overview.md
new file mode 100644
index 000000000..f26f3cc07
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/02_concepts-overview.md
@@ -0,0 +1,46 @@
+---
+id: concepts-overview
+title: StreamPipes Concepts
+sidebar_label: Overview
+---
+
+To understand how StreamPipes works, it is helpful to understand a few core concepts, which are illustrated below.
+These encompass the entire data journey within StreamPipes: Starting with data collection ([adapters](#adapter)),
+through data exchange ([data streams](#data-stream)) and data processing ([data processors](#data-processor) and [pipelines](#pipeline)),
+to data persistence and distribution ([data sinks](#data-sink)).
+
+<img src="/img/02_concepts-overview/components-overview.png" alt="Overview of concepts"/>
+
+## Adapter
+An adapter connects to any external data source (e.g., OPC-UA, MQTT, S7 PLC, Modbus) and forwards the events it receives to the internal StreamPipes system.
+Adapters can either be created by using a predefined adapter for a data source available in our marketplace [StreamPipes Connect](./03_use-connect.md).
+An overview of all available adapters can be found under the menu bar **π Pipeline Elements**.
+When you select one of these adapters, you can easily connect to the data source using an intuitive and convenient UI dialog (see the Connect section for more details).
+Alternatively, you can define your own adapter by [using the provided Software Development Kit (SDK)](./06_extend-tutorial-adapters.md).
+Creating an adapter is always the first step when you want to get data into StreamPipes and process it further.
+
+## Data Stream
+**Data streams** are the primary source for working with events in StreamPipes.
+A stream is an ordered sequence of events, where an event typically consists of one or more observation values and additional metadata.
+The `structure` (or `schema` as we call it) of an event provided by a data stream is stored in StreamPipes' internal semantic schema registry.
+Data streams are primarily created by adapters, but can also be created by a [StreamPipes Function](./06_extend-sdk-functions.md).
+
+## Data Processor
+**Data processors** in StreamPipes transform one or more input streams into an output stream.
+Such transformations can be simple, such as filtering based on a predefined rule, or more complex, such as applying rule-based or learning-based algorithms to the data.
+Data processors can be applied to any data stream that meets the input requirements of a processor.
+In addition, most processors can be configured by providing custom parameters directly in the user interface.
+Processing elements define stream requirements, which are a set of minimum characteristics that an incoming event stream must provide.
+Data processors can maintain state or perform stateless operations.
+
+## Data Sink
+**Data sinks** consume event streams similar to data processors, but do not provide an output data stream.
+As such, data sinks typically perform some action or trigger a visualization as a result of a stream transformation.
+Similar to data processors, sinks also require the presence of specific input requirements from each bound data stream and can be customized.
+StreamPipes provides several internal data sinks, for example, to generate notifications, visualize live data, or persist historical data from incoming streams.
+In addition, StreamPipes provides several data sinks to forward data streams to external systems such as databases.
+
+## Pipeline
+A pipeline in Apache StreamPipes describes the transformation process from a data stream to a data sink.
+Typically, a pipeline consists of at least one data stream, zero or more data processors, and at least one data sink.
+Pipelines are created graphically by users using the [Pipeline Editor](./03_use-pipeline-editor.md) and can be started and stopped at any time.
diff --git a/website-v2/versioned_docs/version-0.98.0/02_concepts-pipeline.md b/website-v2/versioned_docs/version-0.98.0/02_concepts-pipeline.md
new file mode 100644
index 000000000..3d2c5369b
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/02_concepts-pipeline.md
@@ -0,0 +1,7 @@
+---
+id: concepts-pipelines
+title: Pipelines
+sidebar_label: Pipelines
+---
+
+tbd
\ No newline at end of file
diff --git a/website-v2/versioned_docs/version-0.98.0/02_introduction.md b/website-v2/versioned_docs/version-0.98.0/02_introduction.md
new file mode 100644
index 000000000..6dc71b384
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/02_introduction.md
@@ -0,0 +1,85 @@
+---
+id: introduction
+title: Introduction
+sidebar_label: Introduction
+---
+
+## What is StreamPipes?
+
+Apache StreamPipes is a self-service Industrial IoT toolbox to enable non-technical users to connect, analyze and
+explore IoT data streams. The main goal of StreamPipes is to help users bridging the gap between operational
+technology (OT) and information technology (IT). This is achieved by providing a set of tools which help to make
+industrial data accessible for downstream tasks such as data analytics and condition monitoring.
+When working with industrial data and especially when building upon an open source stack for such tasks, users are often
+faced with the management and integration of a variety of different tools for data connectivity, messaging &
+integration, data enrichment, data storage, visualization and analytics. This results in an increasing operational
+complexity and hardly manageable software stacks.
+
+Apache StreamPipes addresses this problem: It provides a complete toolbox with a variety of different tools to easily
+gather data from OT systems such as Programmatic Logic Controllers (PLCs), industrial protocols (e.g., OPC-UA or
+Modbus), IT protocols (e.g., MQTT) and others. Data is integrated in the form of live data streams. Based on connected
+data, StreamPipes provides another module called the pipeline editor, which can be used to apply real-time analytics
+algorithms on connected data stream. To this end, a library of pre-defined algorithms can be used. Out of the box,
+StreamPipes provides more than 100 pipeline elements tailored at manufacturing data analytics. This includes simple
+rule-based algorithms (e.g., flank detection, peak detection, boolean timers), as well as the possibility to integrate
+more sophisticated ML-based algorithms. Finally, the pipeline editor allows to integrate with third-party systems by
+using a variety of data sinks (e.g., to forward data to messaging brokers such as Apache Kafka, MQTT or RocketMQ, to
+store data in databases such as PostgreSQL or Redis or to trigger notifications). Besides pipelines, an included data
+explorer allows to visually analyze industrial IoT data. For this purpose, a number of visualizations are integrated
+that allow non-technical users to quickly get first insights. Examples are correlations between several sensor values,
+value heatmaps, distributions or time-series visualizations. Further tools include a dashboard used for real-time
+monitoring, e.g., for visualizing live KPIs at shopfloor level.
+
+But StreamPipes is much more than just the user interface and an orchestration system for pipelines: It can be used as a
+whole developer platform for Industrial IoT application. Apache StreamPipes is made for extensibility - it provides
+several extension points, which allow the definition of custom algorithms, additional interfaces to third-party tools
+and proprietary data sources.
+
+StreamPipes includes developer support for Java and Python, making it easy to integrate custom-trained machine learning
+models into the data processing environment. With the built-in Python support, it is also possible to run online machine
+learning methods directly on data streams gathered by StreamPipes.
+
+## Where does StreamPipes help?
+
+Being positioned in the industrial IoT domain, the overall goal of StreamPipes is to help manufacturing companies to
+quickly build up an industrial IoT infrastructure and to analyse IIoT data without the need for manual programming.
+Oftentimes, StreamPipes is compared to other tools in this area such as Node-RED for visually wiring of pipelines, which
+is often used together with Grafana for data visualization and InfluxDB for time-series storage. The disadvantage of
+such architectures is the system complexity beyond the first prototype, especially when it comes to production
+deployments. Maintaining and securing multiple software instances is often a hard task requiring for substantial
+development effort. In addition, implementing single-sign-on and providing a unified user experience is another hurdle.
+This is where StreamPipes, as a single integrated tool with production-critical features such as access and role
+management, provides many advantages.
+StreamPipes has already a wide user range from the manufacturing domain. It helps users to quickly do the first steps
+related to industrial analytics but can also be used for monitoring whole production facilities, analysing data streams
+from multiple plants and sensors in real time using the integrated algorithm toolbox. Customization to individual use
+cases is easy due to several extension points:
+
+* Software development kit for adapters, data processors and sinks: The functionality of StreamPipes can be extending by
+ using the integrated SDK. For instance, it is possible to integrate custom-tailored algorithms for proprietary sensors
+ or models into the toolbox. Additional algorithms and data sinks can be installed at runtime.
+* Additional user interface plugins: StreamPipes allows to extend the default installation with additional UI views,
+ making use of a micro frontend approach. For instance, users can extend the system with custom-tailored views for a
+ specific machine or plant. Developers can use a platform API to communicate with the core StreamPipes instance.
+* UI customization: To ensure a consistent look and feel, StreamPipes can be customized to the companyβs corporate
+ identity.
+
+## How does StreamPipes technically work in a nutshell?
+
+
+<img className="docs-image docs-image-no-shadow" src="/img/architecture/streampipes-architecture-components.png" alt="Overview StreamPipes Architecture"/>
+
+
+To foster extensibility, Apache StreamPipes is based on a microservice architecture as illustrated above. The main
+services provided or used by StreamPipes are the a) user interface, b) the core, c) a time-series storage, d) a
+publish/subscribe messaging layer and e) extensions services. Adapters are created over the user interface using an
+intuitive configuration wizard and connect to the underlying source systems. Raw events coming from adapters can be
+pre-processed (e.g., measurement unit conversions or datatype conversions). Afterwards, events are sent to the message
+broker, which is the central backbone to provide IIoT data to internal and external applications.
+
+Besides adapters, extensions microservices can also integrate additional business logic in form of data processors and
+data sinks. StreamPipes comes with over 100 built-in processors and sinks, covering basic use cases out-of-the-box. The StreamPipes core cares about orchestration of these pipeline elements and communicates with the user
+interface. In addition, a time-series storage ensures persistence and can be used by any extensions service to write
+data into the internal storage. The StreamPipes core provides a query interface to access historical data, which is, for
+instance, used by the data explorer UI component. The user interface itself provides several built-in modules but can
+also be extended with additional micro frontends.
diff --git a/website-v2/versioned_docs/version-0.98.0/03_use-configurations.md b/website-v2/versioned_docs/version-0.98.0/03_use-configurations.md
new file mode 100644
index 000000000..4aa953fbb
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/03_use-configurations.md
@@ -0,0 +1,48 @@
+---
+id: use-configurations
+title: Configurations
+sidebar_label: Configurations
+---
+
+The configuration section is an admin-only interface for system-wide settings.
+
+## General configuration
+
+<img className="docs-image" src="/img/03_use-configurations/01_general-configuration.png" alt="General configuration"/>
+
+The general configuration serves to provide basic system settings. The basic settings allow to configure the app name (which is used, e.g., for mails sent by StreamPipes).
+Additionally, the externally available host and port can be set which is used by the mail system to add links to emails.
+
+Furthermore, self-registration and password recovery features can be activated in this view. Note that both features require a working email configuration.
+
+## Datalake
+
+<img className="docs-image" src="/img/03_use-configurations/02_datalake-configuration.png" alt="Datalake configuration"/>
+
+Here, stored data lake databases can be truncated or deleted. The view also gives information on the number of data points currently stored in a measurement series.
+
+## Email configuration
+
+<img className="docs-image" src="/img/03_use-configurations/03_email-configuration.png" alt="Email configuration"/>
+
+In this section, the email configuration is set. The email configuration is used to send mails to users. Most standard mail server settings are supported. The configuration can be validated by triggering a test mail that is sent to a given recipient.
+
+## Messaging
+
+<img className="docs-image" src="/img/03_use-configurations/04_messaging-configuration.png" alt="Messaging configuration"/>
+
+Messaging configuration is used to control parameters used for communication between pipeline elements. Individual Kafka settings can be configured, as well as the priority of selected message formats and protocols during pipeline creation.
+
+## Pipeline Element Configuration
+
+<img className="docs-image" src="/img/03_use-configurations/05_pipeline-element-configuration.png" alt="Pipeline element configuration"/>
+
+Individual configurations of extensions services are available in this view. The available configurations depend on the provided configuration variables in the service definition of each extensions service.
+
+## Security
+
+<img className="docs-image" src="/img/03_use-configurations/06_security-configuration.png" alt="Messaging configuration"/>
+
+The security configuration allows to manage existing user accounts, service accounts and groups. New users can be added and roles can be assigned.
+
+Please also read more about security [here](05_deploy-security.md).
diff --git a/website-v2/versioned_docs/version-0.98.0/03_use-connect.md b/website-v2/versioned_docs/version-0.98.0/03_use-connect.md
new file mode 100644
index 000000000..ba8146481
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/03_use-connect.md
@@ -0,0 +1,72 @@
+---
+id: use-connect
+title: StreamPipes Connect
+sidebar_label: StreamPipes Connect
+---
+
+StreamPipes Connect is the module to connect external data sources with Apache StreamPipes directly from the user interface.
+StreamPipes Connect offers various adapters for common communication protocols and some specific sensors. Besides connecting data, StreamPipes Connect offers ways to pre-process data without the need to build pipelines and integrates a schema guesser that listens for incoming data and recommends the recognized event schema.
+
+The screenshot below illustrates the data marketplace, which shown after navigating to "StreamPipes Connect" and then clicking the "New adapter" button at the top.
+
+<img className="docs-image" src="/img/03_use-connect/01_connect-overview.png" alt="StreamPipes Connect Overview"/>
+
+## Connecting new data sources
+
+### Data Marketplace
+The data marketplace shows a list of all adapters that are currently installed in Apache StreamPipes. Each adapter offers various configuration options which depend on the specifics of the adapter.
+Adapters are distinguished a) by the data source concept they provide (data set or data stream) and b) the adapter type, where we distinguish between _generic adapters_, which usually implement a generic communication protocol such as MQTT or Apache Kafka or a specific sensor interface (e.g., for Netio power sockets).
+Several filter options are available to find a suitable adapter. The configuration of a new adapter starts with selecting one of the available adapters, which starts an assistant that supports the adapter generation.
+
+### Protocol/Basic Settings
+In the first step, basic configurations need to be provided. For instance, for an Apache PLC4X adapter, the IP address of the PLC needs to be provided. In this example, we provide basic settings for connecting to an Apache Kafka broker. After all values are provided, the "Next" button opens the next step.
+
+<img className="docs-image" src="/img/03_use-connect/06_connect-create.png" alt="StreamPipes Connect Basic Settings"/>
+
+### Format Specification
+The next step, format generation, is only available for generic adapters which support different message formats to be sent over the corresponding protocol. Think of a message broker that is able to consume messages in both JSON format or binary format.
+Currently supported formats include XML, various JSON representations, images and CSV. After a format has been selected, further format configurations can be provided (depending on the selected format) to further customize the incoming message format.
+
+<img className="docs-image" src="/img/03_use-connect/02_customize-format.png" alt="StreamPipes Connect Format Selection"/>
+
+### Schema Editor
+In the next step, based on the previously provided protocol and format settings, the system will either provide the fixed/pre-defined schema of the adapter or, in case of specific adapters, will connect to the underlying system and try to listen for incoming data. After a few seconds, the schema editor will appear that provides a list of detected fields from the incoming events (the schema).
+
+<img className="docs-image" src="/img/03_use-connect/03_schema-editor.png" alt="StreamPipes Connect Schema Editor"/>
+
+In the toolbar, several configuration options are available which transform the original schema:
+
+* **Add Nested Property**. This option allows to modify the structure of the event by creating a nested structure. The schema can be simply changed by dragging and dropping fields into the nested structure.
+* **Add Static Value**. This option allows to add a field containing a static value (e.g., an identifier) to the event.
+* **Add Timestamp**. This options appends the current timestamp to each incoming event, useful in case the timestamp is not provided by the origin.
+* **Refresh**. Re-triggers the schema guessing.
+* **Delete field**. Select one or more fields by clicking the checkbox on the right and trigger the delete button.
+* **Property scope**. For each field, a property scope can be defined which is either _Measurement_, _Dimension_ or _Header_. These values are later be used in the pipeline editor to assist in configuring pipeline elements and do not have any functional consequence.
+Use _Measurement_ to indicate the field measures a value (e.g., a temperature value from a sensor), use _Dimension_ for any identifier (e.g., the sensor ID) and use _Header_ for any other metadata such as timestamps.
+
+For each field (also called event property) of the schema, additional configuration options are available by clicking the _Edit_ button:
+
+* **Label**. Used to provide a human-readable label for the field, which will ease the identification of fields when building pipelines.
+* **Runtime Name.** This is the identifier of the field in the underlying message representation format (e.g., the JSON key). Renaming the runtime name will trigger a so-called _transformation rule_ which renames the incoming field name to the new field name before forwarding it to StreamPipes.
+* **Domain Property/Semantic Type**. To help StreamPipes better understand the value which is represented by the field, semantic type information can be given. Up from StreamPipes 0.68.0, the semantic type can be selected from a wide range of available options. Additionally, an URL can be manually provided that indicates the meaning of the value (e.g., http://schema.org/Temperature).
+* **Mark as Timestamp**. Indicates that the selected value represents a timestamp. When selected, a _timestamp converter_ can be configured which will convert incoming timestamps to the UNIX timestamp.
+* **Runtime Type**. Here, the data type can be changed
+* **Unit**. Allows to specify the unit in which the value is measured. Once selected, you can also automatically convert the unit to a target unit, which will then be inserted into the data stream produced by the adapter (see screenshot below).
+
+<img className="docs-image" src="/img/03_use-connect/04_schema-editor-conversion.png" alt="StreamPipes Connect Unit Conversion"/>
+
+Assigning a timestamp is mandatory and can be either done by adding a timestamp from the menu, or by choosing an existing field and marking it as timestamp.
+
+### Adapter Generation
+Finally, the adapter is ready to be started. In the _Adapter Generation_ page, a name and description for the resulting data stream must be provided.
+Once started, StreamPipes creates your new adapter and displays a preview of the connected data, which refreshes about once per second.
+Afterwards, the newly created data stream is available in the pipeline editor for further usage.
+
+<img className="docs-image" src="/img/03_use-connect/05_adapter-generation.png" alt="StreamPipes Connect Adapter Generation"/>
+
+## Managing adapters
+
+Currently running adapters are available in the "Running adapters" section of StreamPipes Connect. Existing adapters can be stopped and deleted. Currently, there is no mechanism to edit an existing adapter or to stop the adapter without deleting it.
+
+### Adapter Templates
+For frequently used configurations, adapter templates can be created. An adapter template is a pre-configured adapter which can be further customized by users. Created adapter templates are available in the marketplace similar to standard adapters.
diff --git a/website-v2/versioned_docs/version-0.98.0/03_use-dashboard.md b/website-v2/versioned_docs/version-0.98.0/03_use-dashboard.md
new file mode 100644
index 000000000..339bf6b57
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/03_use-dashboard.md
@@ -0,0 +1,66 @@
+---
+id: use-dashboard
+title: Live Dashboard
+sidebar_label: Live Dashboard
+---
+
+The live dashboard can be used to visualize live data of data streams using a set of visualizations
+The entry page of the live dashboard lists all created dashboards as in the screenshot below:
+
+<img className="docs-image" src="/img/03_use-dashboard/01_dashboard-overview.png" alt="StreamPipes Dashboard Overview"/>
+
+## Visualizing Data Streams
+
+To visualize data streams in the live dashboard, a pipeline must be created that makes use of the so-called **Data Lake** sink.
+Any data stream or data processor can serve as an input of the data lake sink. Switch to the pipeline editor, create a pipeline and configure the data lake sink. The visualization name is used to identify the sink in case multiple data lake sinks are used within a single pipeline.
+
+## Managing Dashboards
+Multiple dashboards can be created, e.g., to organize different assets in a single dashboard view.
+
+A new dashboard can be created by clicking the _New Dashboard_ button, which opens a dialog that requires basic dashboard settings such as the title and description of the new dashboard.
+Once created, the dashboard will be shown in the overview. Here, the following dashboard actions are available:
+
+* **Show** opens the dashboard.
+* **Window** opens the dashboard in a new window with reduced controls, e.g., without the StreamPipes navigation and toolbar. This is a useful view for standalone displays that should visualize key parameters.
+* **Settings** allows to modify the basic dashboard settings.
+* **Edit** opens the dashboard in edit mode, where widgets can be added to the dashboard.
++ **Delete** deletes the selected dashboard.
+
+## Creating Visualizations
+
+Visualizations can be added to each dashboard in form of widgets. To add new visualizations, switch to the dashboard in _Edit_ mode.
+In edit mode, a button appears that allows to add a new visualization.
+
+Adding a new visualization is supported by a wizard consisting of three steps:
+
+<img className="docs-image" src="/img/03_use-dashboard/02_add-widget.png" alt="StreamPipes Dashboard Pipeline Selection"/>
+
+* **Select pipeline** is the first step where a pipeline is selected on which the visualization is based. In this view, all pipelines are listed that have at least one **Dashboard Sink**. In case a pipeline contains multiple data lake sinks, the visualization name is listed below the pipeline name which eases discovering of the proper visualization.
+* **Select widget** is the next step where the visualization widget must be selected. StreamPipes automatically filters this list based on input requirements of widgets. For instance, image visualizations are only visible if the input data stream provides an image object.
+* **Configure widget** provides widget-specific settings to configure the visualization. In most cases, colors and titles of widgets can be modified. Additionally, chart-specific settings such as axis value ranges can be configured.
+
+<img className="docs-image" src="/img/03_use-dashboard/03_configure-widget.png" alt="StreamPipes Dashboard Widget Configuration"/>
+
+By clicking _Create_, the new widget is placed on the canvas. Size and positioning of visualizations can be flexibly changed based on the provided grid. To change the widget configuration, the _Settings_ button of each widget can be clicked to re-open the configuration dialog.
+
+Once created, the dashboard provides a live view of all visualizations:
+
+<img className="docs-image" src="/img/03_use-dashboard/04_live-dashboard.png" alt="StreamPipes Live Dashboard"/>
+
+
+Before the dashboard is closed, make sure to click the _Save_ button to persist the updated dashboard. Changes can be discarded by clicking the _Discard_ button.
+
+
+## Available widgets
+
+The following visualizations are available in the latest release:
+
+* Area Chart
+* Gauge
+* HTML page (renders HTML markup)
+* Image
+* Line Chart
+* Raw (displays the raw JSON input for debugging purposes)
+* Single Value (displays a single measurement)
+* Table
+* Traffic Light
diff --git a/website-v2/versioned_docs/version-0.98.0/03_use-data-explorer.md b/website-v2/versioned_docs/version-0.98.0/03_use-data-explorer.md
new file mode 100644
index 000000000..f84323bf6
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/03_use-data-explorer.md
@@ -0,0 +1,102 @@
+---
+id: use-data-explorer
+title: Data Explorer
+sidebar_label: Data Explorer
+---
+
+The data explorer can be used to visualize and explore data streams that are persisted by using the **Data Lake** sink.
+
+<img className="docs-image" src="/img/03_use-data-explorer/01_data-explorer-overview.png" alt="StreamPipes Data Explorer Overview"/>
+
+It provides a canvas (i.e. a data view) where various visualizations from multiple pipelines can be placed. For each data view, you can set a date and time range for the configured visualizations.
+
+## Using the data explorer
+
+### Get the data
+
+In the data explorer, any pipeline that uses the so-called **Data Lake** sink can be explored in the data explorer. Switch to the pipeline editor and add the data lake sink to a data processor or stream.
+The sink requires an index name as a configuration parameter, which is used as an identifier in the data explorer.
+
+### Data Views & Widgets
+
+After your data is stored in the data lake, you can switch over to the data-explorer tab to create a novel data view and the widgets of your choice. In StreamPipes, a data view organizes a set of related widgets (i.e. data visualizations or plots) and gets assigned a single date and time range. The standard date and time range consists of the last 15 minutes of the current date and time. You can select predefined ranges (e.g. day or month) or configure the exact date and time range you w [...]
+
+<img className="docs-image" src="/img/03_use-data-explorer/02_data-explorer-overview-2.png" alt="StreamPipes Data Explorer Component"/>
+
+First create and name your data view and select the edit icon to proceed. In your data view, you can now add a new widget congiguration (plus icon) to configure and create your first widget. The widget configuration consists of (i) data, where the individual data sources in the data lake are selected, the properties for the widget are chosen and filters on the data sources are defined and applied, (ii) visualization, where the type of widget is chosen and the respective configuration for [...]
+
+### Data Configuration
+
+The data configuration is the first step to define your widget. You can add several data sources (i.e. data sinks) and need to configure each added data source individually. This gives you sufficient freedom to combine the needed information, potentially consisting of different data resolutions, filters or types of information.
+
+<img className="docs-image" src="/img/03_use-data-explorer/03_data-explorer-data.png" alt="StreamPipes Data Explorer Data Configuration"/>
+
+After selecting the initial data source, you can choose if the underlying data query is to be performed raw, aggregated or single. Raw queries refer to using the data as-is, where you can define a limit on the number of events to guarantee performant usage in the application. In aggregated mode, you can choose among predefined aggregation granularites (e.g. day, minute, second).
+
+In the next step, you can choose the fields (i.e. properties of your data source) you are interested in exploring. If you selected aggregation or single mode, you can also modify the type of aggregation to be performed on the selected property.
+
+You can also filter your data source by adding conjunctive conditions.
+
+### Visualization Configuration
+
+The visualization configuration is dependent on the visulization type, which needs to be selected first. The data-explorer currently supports the following types:
+
+#### Table
+
+The table view formats the selected properties in table format.
+
+<img className="docs-image" src="/img/03_use-data-explorer/04_data-explorer-table.png" alt="StreamPipes Data Explorer Table"/>
+
+#### Map
+
+The map allows to visualize and explore coordinates on the world map. The configuration requires to choose the property which comprises the coordinates, allows to choose the marker style, a zoom level as well as the tooltip content.
+
+<img className="docs-image" src="/img/03_use-data-explorer/05_data-explorer-map.png" alt="StreamPipes Data Explorer Map"/>
+
+#### Heatmap
+
+The heatmap widget visualizes data in terms of the available intensity, where higher values are interpreted as being more intense. You only need to select the property which you want to visualize. Note that it might be interesting to aggregate the data in the data configuration to get more insights in your heatmap.
+
+<img className="docs-image" src="/img/03_use-data-explorer/06_data-explorer-heatmap.png" alt="StreamPipes Data Explorer Heatmap"/>
+
+#### Time Series
+
+The time series widget allows you to do exploration and analysis for your numerical and boolean data properties. You can easily visualize your data properties in various styles (i.e. scatter, line, scattered line, bar or symbol) and colors, and configure a second y-axis for better interpretation of varying property ranges.
+
+<img className="docs-image" src="/img/03_use-data-explorer/07_data-explorer-timeseries-1.png" alt="StreamPipes Data Explorer Time Series 1"/>
+
+<img className="docs-image" src="/img/03_use-data-explorer/08_data-explorer-timeseries-2.png" alt="StreamPipes Data Explorer Time Series 2"/>
+
+<img className="docs-image" src="/img/03_use-data-explorer/09_data-explorer-timeseries-3.png" alt="StreamPipes Data Explorer Time Series 3"/>
+
+#### Image
+
+The image widget enables to integrate and visualize your image data.
+
+#### Indicator
+
+The indiator widget lets you visualize a single numerical value as well as (optionally) the delta to another indicator. You only need to configure the respective properties.
+
+<img className="docs-image" src="/img/03_use-data-explorer/11_data-explorer-indicator.png" alt="StreamPipes Data Explorer Indicator"/>
+
+#### 2D Correlation
+
+The correlation plot currently supports analyzing the relationship of two properties. Once selected, you can choose between a scatter view of the plotted data points or directly extract correlations in a density chart.
+
+<img className="docs-image" src="/img/03_use-data-explorer/12_data-explorer-correlation-1.png" alt="StreamPipes Data Explorer Correlation 1"/>
+
+<img className="docs-image" src="/img/03_use-data-explorer/13_data-explorer-correlation-2.png" alt="StreamPipes Data Explorer Correlation 2"/>
+
+#### Distribution
+
+In the distribution widget, you can quickly get an overview of your data range and common data values. You can either choose a histrogram view, where a bar chart is used to show data the frequency of automatically extracted data ranges or a pie view, where you can also select the granularity of how your data is clustered in terms of frequency.
+
+<img className="docs-image" src="/img/03_use-data-explorer/14_data-explorer-distribution-1.png" alt="StreamPipes Data Explorer Distribution 1"/>
+
+<img className="docs-image" src="/img/03_use-data-explorer/15_data-explorer-distribution-2.png" alt="StreamPipes Data Explorer Distribution 2"/>
+
+### Appearance Configuration
+
+Finally, you can change the title of your created widget as well as background and text colors in the appearance configuration.
+
+<img className="docs-image" src="/img/03_use-data-explorer/16_data-explorer-appearance.png" alt="StreamPipes Data Explorer Appearance"/>
diff --git a/website-v2/versioned_docs/version-0.98.0/03_use-install-pipeline-elements.md b/website-v2/versioned_docs/version-0.98.0/03_use-install-pipeline-elements.md
new file mode 100644
index 000000000..852693200
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/03_use-install-pipeline-elements.md
@@ -0,0 +1,9 @@
+---
+id: use-install-pipeline-elements
+title: Install Pipeline Elements
+sidebar_label: Install Pipeline Elements
+---
+
+## Install Pipeline Elements
+
+(coming soon)
diff --git a/website-v2/versioned_docs/version-0.98.0/03_use-managing-pipelines.md b/website-v2/versioned_docs/version-0.98.0/03_use-managing-pipelines.md
new file mode 100644
index 000000000..2c64b53ee
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/03_use-managing-pipelines.md
@@ -0,0 +1,52 @@
+---
+id: use-managing-pipelines
+title: Managing Pipelines
+sidebar_label: Managing Pipelines
+---
+
+The pipeline view lists all created pipelines and provides several views and actions to manage the lifecycle of pipelines.
+
+In the entry screen, an overview of all created pipelines is shown:
+
+<img className="docs-image" src="/img/03_use-managing-pipelines/01_pipeline-overview.png" alt="StreamPipes Pipeline Overview"/>
+
+## Pipeline Actions
+Within the pipeline overview, for each pipeline several actions are available:
+* **Start/Stop pipeline** Starts or stops the selected pipeline. Once clicked, StreamPipes will trigger the selected action for all pipeline elements and open a success or error dialog as illustrated below.
+* **Show details** opens the pipeline detail view (see below).
+* **Modify pipeline** opens the pipeline in the pipeline editor, where the pipeline can be modified. Note that this button is only visible if the pipeline is not running.
+* **Delete pipeline** opens a confirm dialog, which subsequently deletes the selected pipeline.
+
+The screenshot below shows the status of a pipeline after it has been successfully started. By clicking the _Show details_ button, more information on the status of each corresponding pipeline element microservice becomes available. In case of failures, the failure reason will be shown for each pipeline element that has failed to start.
+
+<img className="docs-image" src="/img/03_use-managing-pipelines/02_pipeline-start-dialog.png" alt="StreamPipes Pipeline Start Dialog"/>
+
+## Organizing Pipelines into Categories
+Pipelines can be organized into categories, which is a useful feature in case a larger amount of pipelines is created.
+All categories will be shown as separate tabs in the pipeline overview. The same pipeline can be assigned to multiple categories.
+
+To add a new category or to add a new pipeline to an existing category, click the _Manage Categories_ button and configured the category and assigned pipelines in the dialog.
+
+## Pipeline Details
+The pipeline details view can be opened by clicking the _Show details_ button in the pipeline overview panel.
+
+<img className="docs-image" src="/img/03_use-managing-pipelines/03_pipeline-details.png" alt="StreamPipes Pipeline Details"/>
+
+### Overview
+The overview section displays the graphical structure of the pipeline and provides some statistics about recent pipeline actions. Additionally, pipelines can be directly started, stopped, modified and deletes within this view.
+
+### Monitoring
+Monitoring features will become available in version 0.68.0.
+
+### Errors
+Monitoring of failures and logs will become available in version 0.69.0.
+
+### QuickEdit
+The quick edit feature (only available for pipelines that are not running) is a quick and convenient way to modify some pipeline element configurations without opening the pipeline in the pipeline editor.
+To use the quick edit feature, switch to the _QuickEdit_ tab, which will display the selected pipeline.
+
+By clicking a pipeline element from the preview canvas, available configuration options of the selected pipeline element can be modified. Note that only modifications that do not affect the pipeline structure (e.g., different output streams) can be changed.
+
+<img className="docs-image" src="/img/03_use-managing-pipelines/04_pipeline-quick-edit.png" alt="StreamPipes Pipeline Quick Edit"/>
+
+After a configuration value was changed, make sure to click the _Update Pipeline_ button to save the changes.
diff --git a/website-v2/versioned_docs/version-0.98.0/03_use-notifications.md b/website-v2/versioned_docs/version-0.98.0/03_use-notifications.md
new file mode 100644
index 000000000..b5c64ed98
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/03_use-notifications.md
@@ -0,0 +1,25 @@
+---
+id: use-notifications
+title: Notifications
+sidebar_label: Notifications
+---
+
+The notification module can be used to create internal notifications.
+
+<img className="docs-image" src="/img/03_use-notifications/01_notifications-overview.png" alt="StreamPipes Notifications"/>
+
+## Using notifications
+
+Any pipeline that includes the data sink **Notification** can trigger notifications that appear in the notification view. To configure a new notification, switch to the pipeline editor and append the notification sink to a data processor or data stream.
+The sink requires a title and message as configuration parameters.
+
+### Placeholders
+
+The notification message can include placeholders for fields which are replaced with the actual value at runtime.
+
+## Managing notifications
+
+The notification view is split into two parts. The left sides lists all pipelines which include a notification sink. By selecting a pipeline, available notifications will be shown in the right panel.
+By scrolling up, older notifications become visible. Notifications that have appeared in the detail view will be automatically marked as read, so that only new, unread notifications will appear in the left toolbar.
+
+
diff --git a/website-v2/versioned_docs/version-0.98.0/03_use-pipeline-editor.md b/website-v2/versioned_docs/version-0.98.0/03_use-pipeline-editor.md
new file mode 100644
index 000000000..f09cf8486
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/03_use-pipeline-editor.md
@@ -0,0 +1,62 @@
+---
+id: use-pipeline-editor
+title: Pipeline Editor
+sidebar_label: Pipeline Editor
+---
+
+The pipeline editor module supports building pipelines that transform a data stream using a set of resuable data processors and data sinks.
+The empty pipeline editor looks similar to the illustration below after a new installation.
+
+<img className="docs-image" src="/img/03_use-pipeline-editor/01_pipeline-editor-overview.png" alt="StreamPipes Pipeline Editor Overview"/>
+
+## Pipeline Elements
+The four main concepts data sets, data streams, data processors and data sinks are available at the top of the pipeline editor. By switching the tabs, the individual pipeline elements for each category can be found.
+By clicking the questionmark symbol, which appears when hovering over an element, additional information can be viewed (e.g., for data streams a live preview of incoming data and the documentation of the pipeline element for data processors and sinks).
+
+<img className="docs-image" src="/img/03_use-pipeline-editor/02_pipeline-element-info.png" alt="StreamPipes Pipeline Element Info"/>
+
+## Creating Pipelines
+Pipelines are built by dragging data streams, processors and sinks into the pipeline assembly area. Typically, a pipeline is built step-by-step starting with a data soure (stream or set).
+Afterwards, data processors and sinks are subsequently added to the pipeline. Connections between pipeline elements are made by selecting the gray connector of the source and moving it to the target pipeline element.
+Once a connection is made, StreamPipes performs a quick validation step and, in case two pipeline elements are compatible, automatically opens a configuration window.
+
+### Configuring Pipeline Elements
+The configuration depends on the selected pipeline element and looks similar to the screenshot below.
+In general, pipeline elements are configured by providing the required values. Once the pipeline element is fully configured, the _Save_ button activates and can be used to save the configuration for the pipeline element.
+
+<img className="docs-image" src="/img/03_use-pipeline-editor/03_configure-pipeline-element.png" alt="StreamPipes Pipeline Element Configuration"/>
+
+In addition, the following options are available in the pipeline element configuration menu:
+* **Show documentation** extends the view and displays the pipeline element's documentation next to the configuration view.
+* **Show only recommended settings** filters the list of available fields provided by the connected input data stream based on the _property scope_, e.g., so that only measurement values are displayed and dimension fields from the input stream are not available for selection. If deactivated, selections contain the full list of available fields that match the input requirement of the data processor.
+
+### Pipeline Element Options
+Further options for a pipeline element can be displayed by hovering over a pipeline element in the assembly area, so that additional buttons appear around the pipeline element:
+
+* **Configure element** re-opens the configuration view to update the pipeline element configuration (only available for data processors and sinks)
+* **Delete element** removes the pipeline element from the pipeline
+* **Help** opens the pipeline element's documentation
+* **Compatible element** opens a dialog which shows all pipeline elements that are compatible to the current element's output data stream. The dialog offers an alternative to selecting pipeline elements directly from the pipeline element selection in the top.
+* **Pipeline Element Recommendation** opens a dialog which shows all recommended pipeline elements that are compatible the current element's output data stream. The recommendation is based on previously connected pipeline elements and is displayed below.
+
+### Pipeline Editor Options
+Several pipeline editor options are available in the menu bar of the pipeline assembly:
+
+<img className="docs-image" src="/img/03_use-pipeline-editor/05_pipeline-editor-options.png" alt="StreamPipes Pipeline Editor Options"/>
+
+* **Save pipeline** opens the save dialog (see below)
+* **Pan** allows to pan within the assembly area, useful for larger pipelines that do not fit in the screen
+* **Select** is visible if pan mode is active and switches back to the default select mode
+* **Zoom in/out** triggers the zoom in the pipeline assembly
+* **Auto Layout** layouts the pipeline in a much more beautiful way than you are able to do by yourself ;-)
+* **All pipeline modification saved** is displayed if the current pipeline has been cached. Cache updates are triggered after every change of the pipeline so that changes are not lost after reloading the window.
+* **Hints** are shown to display current errors (e.g., incomplete pipelines). Details can be opened by clicking the hint button.
+* **Clear assembly** clears the assembly and removes the current pipeline.
+
+### Saving a pipeline
+To save a pipeline, press the _save pipeline_ button. A dialog pops up where a name and description of the pipeline can be entered (only name is mandatory).
+Additionally, a pipeline can be directly started after it has been stored by checking the corresponding button.
+
+<img className="docs-image" src="/img/03_use-pipeline-editor/06_save-pipeline.png" alt="StreamPipes Save Pipeline Dialog"/>
+
+
diff --git a/website-v2/versioned_docs/version-0.98.0/03_use-programmatically-create-adapters.md b/website-v2/versioned_docs/version-0.98.0/03_use-programmatically-create-adapters.md
new file mode 100644
index 000000000..1c791dc39
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/03_use-programmatically-create-adapters.md
@@ -0,0 +1,154 @@
+---
+id: use-programmatically-create-adapters
+title: Adapters as Code
+sidebar_label: Adapters as Code
+---
+
+In Apache StreamPipes, adapters are typically created via the web interface.
+However, it is possible to create adapters programmatically using a compact YAML format and the StreamPipes REST API.
+Programmatic creation of adapters can be a useful feature in cases where many similar adapters have to be created.
+In this case, an externally managed YAMl file containing the full adapter configuration can be used and modified.
+
+## Introduction
+
+In StreamPipes, adapters are responsible for collecting data from various industrial data sources.
+While the UI simplifies this process, you can also manage adapters programmatically for better automation, integration with CI/CD pipelines, or infrastructure-as-code practices.
+
+This guide demonstrates how to define and create adapters using a YAML format and StreamPipes REST API, offering more flexibility to manage adapters programmatically.
+
+## Adapter YAML Structure
+
+An adapter in StreamPipes can be defined using a YAML file, which contains a compact description of the adapter configuration.
+The basic structure of the YAML format for an adapter definition includes:
+
+- **Name**: The name of the adapter.
+- **ID**: A unique ID for the adapter
+- **Description**: An additional description of the adapter
+- **AppID**: The adapter type
+- **Configuration**: Configuration details such as connection details, polling intervals, data format, and more
+- **Schema**: Schema refinements, e.g., additional label, description, semantic type and property scope
+- **Enrich**: Enrichment rules. Currently, only timestamp enrichment rules are supported in the YAML specification
+- **Transform**: Transformation rules. Currently, rename and measurement unit transforms are supported.
+- **CreateOptions**: Additional operations that are executed upon adapter generation.
+
+Hereβs a sample structure to define an OPC-UA adapter:
+
+```yaml
+name: My OPC Adapter
+id: testadapter
+description: Test
+appId: org.apache.streampipes.connect.iiot.adapters.opcua
+configuration:
+ - opc_host_or_url: OPC_URL
+ opc_server_url: opc.tcp://localhost:62541/milo
+ - adapter_type: PULL_MODE
+ pulling_interval: 1000
+ - access_mode: UNAUTHENTICATED
+ - available_nodes:
+ - "ns=2;s=Leakage Test Station/temperature"
+ - "ns=2;s=Leakage Test Station/pressure"
+
+schema:
+ temperature:
+ propertyScope: measurement
+ label: Temp
+ description: Temperature value
+ semanticType: http://schema.org/temperature
+
+enrich:
+ timestamp: timestamp
+
+transform:
+ rename:
+ pressure: pressure3
+
+createOptions:
+ persist: true
+ start: true
+```
+
+## Programmatically creating adapters
+
+Here is a walkthrough to create an adapter programmatically over the API:
+
+### Background: Internal adapter generation process
+
+The YAML definition file is a more compact notation of StreamPipes internal data format to represent an adapter.
+When creating an adapter over the user interface, StreamPipes requires some basic, adapter-specific settings.
+Afterwards, a `Guess Schema` step is executed. In this step, StreamPipes connects to the underlying data sources, receives some samples of live data, determines the exact schema of the data stream and provides user with the source schema.
+This schema can be further refined using `Transformation Rules`.
+
+When an adapter is created using the more compact YAML notation, the same process is applied. Based on the provided configuration, the API connects to the given data source and determines the schema.
+The transformation rules provided in the YAMl definition are then applied on the original schema.
+Therefore, it is important that the provided schema refinement and transformation steps fit the original schema.
+
+### Getting a valid definition file
+
+The easiest way to create a valid YAML file is the user interface. Within the StreamPipes Connect view, it is possible to export the YAML definition for all existing adapters.
+In addition, the adapter generation wizard also offers the option to view the adapter configuration before creating the adapter by clicking the `Code` checkbox:
+
+<img className="docs-image" src="/img/03_use-programmatically-create-adapters/01_adapter-generation-code.png" alt="StreamPipes Adapter Code View"/>
+
+Another option is to open the adapter details view:
+
+<img className="docs-image" src="/img/03_use-programmatically-create-adapters/02_adapter-details-view-code.png" alt="StreamPipes Adapter Details Code View"/>
+
+You can copy this definition and modify it according to your needs.
+
+#### Configuration
+
+For each configuration option in the user interface, there is a mapping to the YAMl definition.
+
+A configuration value is a key/value pair, where the key corresponds to the internal name of the configuration and the value depends on the configuration type.
+
+#### Schema
+
+Schema definitions enhance the metadata of each field from the input stream.
+The following configurations are supported:
+
+* `label` to add an additional (human-readable) label to the field
+* `description` for an additional description
+* `propertyScope` to determine the type of the field (HEADER_PROPERTY, DIMENSION_PROPERTY or MEASUREMENT_PROPERTY)
+* `semanticType` to provide the semantic type of the field (e.g., `https://schema.org/temperature`)
+
+#### Enrich
+
+* `timestamp` defines that an additional field named timestamp is added to each incoming event containing the ingestion time as a UNIX timestamp.
+
+#### Transform
+
+Currently, the following transforms are supported:
+
+* `rename` defines renaming of individual fields from the input stream. A valid configuration consists of a key/value pair, where the key indicates the original field name and the value the target field name.
+* `measurementUnit` defines a value transformation between measurement units. A valid configuration consists of a key/value pair, where the key indicates the field name and the value the target measurement unit.
+
+#### CreateOptions
+
+Currently, two settings can be provided in the `CreateOptions` section:
+
+* `persist` indicates whether the data stream produced by the adapter should also be stored. In this case, a `Persist Pipeline` is automatically created.
+* `start` indicates whether the adapter should be immediately started after creation.
+
+### API
+
+To create a new adapter, call the StreamPipes API as follows:
+
+```
+POST /streampipes-backend/api/v2/connect/compact-adapters
+Content-type: application/yml
+Accept: application/yml
+```
+
+You must provide valid credentials by either adding a Bearer token or an API key:
+
+```
+X-API-USER: your username
+X-API-KEY: your api key
+```
+
+The body of the request should contain the YAML definition.
+
+:::info
+It is also possible to provide the adapter specification as a JSON document. In this case, change the `Content-type` to `application/json`.
+
+
diff --git a/website-v2/versioned_docs/version-0.98.0/03_use-programmatically-create-pipelines.md b/website-v2/versioned_docs/version-0.98.0/03_use-programmatically-create-pipelines.md
new file mode 100644
index 000000000..a3a117bbc
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/03_use-programmatically-create-pipelines.md
@@ -0,0 +1,164 @@
+---
+id: use-programmatically-create-pipelines
+title: Pipelines as Code
+sidebar_label: Pipelines as Code
+---
+
+In Apache StreamPipes, pipelines represent the flow of data from sources (streams), through processors (filters, transformations, etc.), and finally to sinks (third-party-systems, storage, notifications).
+Traditionally, pipelines are created through the web-based user interface.
+However, they can also be defined programmatically as code, offering the flexibility to manage pipelines using Infrastructure as Code (IaC) practices.
+
+This guide explains how to define and create pipelines programmatically using a YAML structure.
+
+## Introduction
+
+Defining pipelines as code allows you to automate the creation, management, and deployment of StreamPipes pipelines.
+This is especially useful for managing multiple StreamPipes instances across environments.
+Pipelines are written in a YAML format (or alternatively as JSON) and can be deployed programmatically via the StreamPipes REST API.
+
+This guide provides an overview of how to structure pipeline definitions in YAML and deploy them using the API.
+
+## Pipeline YAML Structure
+
+A pipeline in YAML consists of several key sections:
+
+- **ID**: A unique identifier for the pipeline.
+- **Name and Description**: Optional fields to describe the pipeline.
+- **Pipeline Elements**: The components that make up the pipeline, including streams (data sources), processors (data transformations), and sinks (output destinations).
+- **Create Options**: Specifies how and when to start the pipeline (e.g., `start: false` means the pipeline won't start automatically).
+
+Hereβs a high-level breakdown of the structure:
+
+```yaml
+id: my-pipeline
+name: ""
+description: ""
+pipelineElements: # Define pipeline components here
+ - type: stream # Data source
+ ref: <reference> # Unique reference ID
+ id: <data-stream-id> # ID of the stream
+
+ - type: processor # Data transformation
+ ref: <reference> # Unique reference ID
+ id: <processor-id> # ID of the processor
+ connectedTo: # Previous pipeline element reference(s)
+ - <reference>
+ configuration: # Processor-specific configurations
+ - <configuration-option>
+
+ - type: sink # Data sink (output)
+ ref: <reference> # Unique reference ID
+ id: <sink-id> # ID of the sink
+ connectedTo: # Previous pipeline element reference(s)
+ - <reference>
+ configuration: # Sink-specific configurations
+ - <configuration-option>
+
+createOptions:
+ start: <true|false> # Whether to start the pipeline immediately
+```
+
+## Pipeline Elements
+
+### Building blocks
+
+The key building blocks of a pipeline include:
+
+#### Stream
+A stream represents a data source in the pipeline, such as a sensor feed, API, or message queue. It is referenced by a unique ID that identifies the data stream.
+
+#### Processor
+A processor transforms, filters, or enriches the data coming from a stream or another processor. Each processor has configuration parameters that control its behavior, such as filtering criteria or mapping options.
+
+#### Sink
+A sink sends the processed data to a final destination, such as a database, file storage, or another service. Sinks may also have configuration options that specify where and how the data should be sent.
+
+A pipeline element is selected by providing its ID. For processors and sinks, the ID refers to the `appId` of the pipeline element, e.g., `org.apache.streampipes.processors.filters.jvm.numericalfilter`.
+For data streams, the ID refers to the `elementId` of the data stream.
+
+To define connections between pipeline elements, the `ref` and `connectedTo` fields can be used.
+`ref` can be a short string (e.g., `stream01` or `processor01`) which will be used as an internal identifier of the pipeline element.
+Within the `connectedTo` list, connections to other pipeline elements can be defined.
+Each item of the list should relate to an existing `ref`.
+
+### Configuration
+
+In the `configuration` section, which only applies for data processors and sinks, the pipeline element configuration can be applied.
+The configuration options depend on the pipeline element and have the same structure as the adapter configuration (see [Adapters as Code](use-programmatically-create-adapters))
+The easiest way to determine a valid configuration is the web interface.
+
+After creating a pipeline in the web interface and clicking on `Save pipeline`, the option `Show pipeline configuration as code` shows the current pipeline configuration in YAML or JSON format:
+
+<img className="docs-image" src="/img/03_use-programmatically-create-pipelines/01_pipeline-editor-pipeline-as-code.png" alt="StreamPipes Pipeline Editor Code View"/>
+
+Another option is to view the pipeline details for an existing pipeline. Here, the YAMl definition of the pipeline can be viewed by clicking the `View pipeline as code` button:
+
+<img className="docs-image" src="/img/03_use-programmatically-create-pipelines/02_pipeline-details-pipeline-as-code.png" alt="StreamPipes Pipeline Editor Code View"/>
+
+
+## Example pipeline as Code
+
+Here's an example of a pipeline written in YAML format:
+
+```yaml
+id: my-pipeline
+name: "Density Filter Pipeline"
+description: "A pipeline that filters data based on the density and stores it in a data lake."
+pipelineElements:
+ - type: stream
+ ref: stream01
+ id: sp:spdatastream:GWWzMD
+ - type: processor
+ ref: processor01
+ id: org.apache.streampipes.processors.filters.jvm.numericalfilter
+ connectedTo:
+ - stream01
+ configuration:
+ - number-mapping: s0::density
+ - operation: <
+ - value: "12"
+ - type: sink
+ ref: sink01
+ id: org.apache.streampipes.sinks.internal.jvm.datalake
+ connectedTo:
+ - processor01
+ configuration:
+ - timestamp_mapping: s0::timestamp
+ - db_measurement: my-measurement
+ - schema_update: Update schema
+ - dimensions_selection:
+ - sensorId
+ - ignore_duplicates: false
+createOptions:
+ start: false
+```
+
+Stream: The pipeline begins with a data stream (sp:spdatastream:GWWzMD) referenced by stream01. This is the source of the data.
+
+Processor: The data is passed through a numerical filter processor (org.apache.streampipes.processors.filters.jvm.numericalfilter) which checks if the field s0::density is less than 12. The filter is connected to the stream via reference stream01.
+
+Sink: The filtered data is then sent to a data lake (org.apache.streampipes.sinks.internal.jvm.datalake). The sink is configured with several parameters including the mapping of the timestamp (s0::timestamp) and schema update options. The sink is connected to the processor via reference processor01.
+
+Create Options: The pipeline is set to not start automatically (start: false).
+
+## API
+
+To create a new pipeline, call the StreamPipes API as follows:
+
+```
+POST /streampipes-backend/api/v2/compact-pipelines
+Content-type: application/yml
+Accept: application/yml
+```
+
+You must provide valid credentials by either adding a Bearer token or an API key:
+
+```
+X-API-USER: your username
+X-API-KEY: your api key
+```
+
+The body of the request should contain the YAML definition.
+
+:::info
+It is also possible to provide the pipeline specification as a JSON document. In this case, change the `Content-type` to `application/json`.
diff --git a/website-v2/versioned_docs/version-0.98.0/05_deploy-choosing-the-right-flavor.md b/website-v2/versioned_docs/version-0.98.0/05_deploy-choosing-the-right-flavor.md
new file mode 100644
index 000000000..a140bf46e
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/05_deploy-choosing-the-right-flavor.md
@@ -0,0 +1,47 @@
+---
+id: choosing-the-right-flavor
+title: Choosing the right flavor
+sidebar_label: Service selection options
+---
+
+
+## Introduction
+
+StreamPipes comes with many different options to customize a deployment. This section introduces the various options you can choose from when installing StreamPipes.
+
+You can choose between various **deployment modes**, choose from two different core packages and several extension packages, wich are described below.
+
+## Deployment Mode
+
+For the deployment model, you choose between a standard multi-container `Docker-Compose` installation and the `Kubernetes` installation.
+we provide several `Docker-Compose` files for the various options shown here and a `helm chart`.
+See [Docker Deployment](05_deploy-docker.md) and [Kubernetes Deployment](05_deploy-kubernetes.md) for more details.
+
+### Running StreamPipes in a non-containerized environment
+
+Of course, it is also possible to launch StreamPipes in a non-containerized environment.
+You will need to build your own executable binaries by running `mvn package`.
+In addition, it is required to install the required 3rd party services (see [Architecture](07_technicals-architecture.md)) and configure the environment variables as described in [Environment Variables](05_deploy-environment-variables.md).
+
+## Core Service
+
+We provide two different pre-packaged versions of core services. The default `streampipes-service-core` is a packaged JAR file which includes client libraries for the various messaging systems StreamPipes supports at the cost of a larger file size.
+In case you plan to run StreamPipes on less resource-intensive hardware, we recommend to switch to the `streampipes-service-core-minimal` package, which only includes support for MQTT and NATS, but has a smaller file size and slightly improved startup performance.
+
+## Extension Services
+
+Similar to the core, we provide several pre-packaged extension services which differ mainly by their file size, number of supported adapters and pipeline elements and messaging systems.
+
+The following packages exist:
+
+* `streampipes-extensions-all-jvm` is the largest package and includes all official StreamPipes adapters and pipeline elements. It also includes support for all messaging systems Streampipes currently supports.
+* `streampipes-extensions-all-iiot` is a subset of the aforementioned package and excludes adapters and pipeline elements which are often not relevant for IIoT use cases. For instance, the package excludes text mining-related pipeline elements.
+* `streampipes-extensions-iiot-minimal` is a subset of the aforementioned package and includes only support for the lightweight messaging systems MQTT and NATS.
+
+Generally said, in cases where you plan to deploy StreamPipes on a resource-limited edge device, we recommend a combination of the `streampipes-service-core-minimal` and `streampipes-extensions-iiot-minimal` package. This could, for instance, be a device with less than 4GB memory.
+In other cases, it depends on the use case and if you need all adapters and pipeline elements or are ok with the IIoT-related extensions.
+
+## Messaging System
+
+StreamPipes can be configured to use different messaging systems for exchanging events between adapters and pipeline elements.
+The section [Messaging](07_technicals-messaging.md) includes detailed information on the configuration of messaging systems.
diff --git a/website-v2/versioned_docs/version-0.98.0/05_deploy-docker.md b/website-v2/versioned_docs/version-0.98.0/05_deploy-docker.md
new file mode 100644
index 000000000..08dbfaa19
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/05_deploy-docker.md
@@ -0,0 +1,92 @@
+---
+id: deploy-docker
+title: Docker Deployment
+sidebar_label: Docker Deployment
+---
+
+StreamPipes Compose is a simple collection of user-friendly `docker-compose` files that easily lets gain first-hand experience with Apache StreamPipes.
+
+> **NOTE**: We recommend StreamPipes Compose to only use for initial try-out and testing. If you are a developer and
+> want to develop new pipeline elements or core feature, use the [StreamPipes CLI](06_extend-cli.md).
+
+#### TL;DR: A one-liner to rule them all :-)
+
+```bash
+docker-compose up -d
+```
+Go to http://localhost to finish the installation in the browser. Once finished, switch to the pipeline editor and start the interactive tour or check the [online tour](https://streampipes.apache.org/docs/user-guide-tour/) to learn how to create your first pipeline!
+
+## Prerequisites
+* Docker >= 17.06.0
+* Docker-Compose >= 1.17.0 (Compose file format: 3.4)
+* Google Chrome (recommended), Mozilla Firefox, Microsoft Edge
+
+Tested on: **macOS, Linux, Windows 10 upwards** (CMD, PowerShell, GitBash)
+
+**macOS** and **Windows** users can easily get Docker and Docker-Compose on their systems by installing **Docker for Mac/Windows** (recommended).
+
+> **NOTE**: On purpose, we disabled all port mappings except of http port **80** to access the StreamPipes UI to provide minimal surface for conflicting ports.
+
+## Usage
+We provide several options to get you going:
+
+- **default**: Default docker-compose file, called `docker-compose.yml`.
+- **nats**: The standard installation which uses Nats as message broker,called `docker-compose.nats.yml`.
+- **full**: Contains experimental Flink wrappers, called `docker-compose.full.yml`.
+
+:::info
+
+Other options include configurations for the internally used message broker. The current default is `Kafka`, but you can also start StreamPipes with `Nats`, `MQTT` or `Apache Pulsar`.
+Use one of the other provided docker-compose files.
+
+:::
+
+**Starting** the **default** option is as easy as simply running:
+> **NOTE**: Starting might take a while since `docker-compose up` also initially pulls all Docker images from Dockerhub.
+
+```bash
+docker-compose up -d
+# go to `http://localhost` after all services are started
+```
+After all containers are successfully started just got to your browser and visit http://localhost to finish the installation. Once finished, switch to the pipeline editor and start the interactive tour or check the [online tour](https://streampipes.apache.org/docs/user-guide-tour/) to learn how to create your first pipeline!
+
+**Stopping** the **default** option is similarly easy:
+```bash
+docker-compose down
+# if you want to remove mapped data volumes, run:
+# docker-compose down -v
+```
+
+Starting the **nats** option is almost the same, just specify the `docker-compose.nats.yml` file:
+```bash
+docker-compose -f docker-compose.nats.yml up -d
+# go to `http://localhost` after all services are started
+```
+**Stopping** the **nats** option:
+```bash
+docker-compose -f docker-compose.nats.yml down
+```
+
+
+Starting the **full** option is almost the same, just specify the `docker-compose.full.yml` file:
+```bash
+docker-compose -f docker-compose.full.yml up -d
+#go to `http://localhost` after all services are started
+```
+Stopping the **full** option:
+```bash
+docker-compose -f docker-compose.nats.yml down
+#docker-compose -f docker-compose.nats.yml down -v
+```
+
+## Update services
+To actively pull the latest available Docker images use:
+```bash
+docker-compose pull
+```
+
+## Upgrade
+To upgrade to another StreamPipes version, simply edit the `SP_VERSION` in the `.env` file.
+```
+SP_VERSION=<VERSION>
+```
diff --git a/website-v2/versioned_docs/version-0.98.0/05_deploy-environment-variables.md b/website-v2/versioned_docs/version-0.98.0/05_deploy-environment-variables.md
new file mode 100644
index 000000000..c4066fb70
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/05_deploy-environment-variables.md
@@ -0,0 +1,88 @@
+---
+id: deploy-environment-variables
+title: Environment Variables
+sidebar_label: Environment Variables
+---
+
+## Introduction
+
+A StreamPipes installation can be configured in many ways by providing environment variables.
+The following lists describe available environment variables along with a description.
+
+## StreamPipes Core Service
+
+### Internal
+
+| Env Variable Name | Default Value | Description |
+|--------------------------------|---------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|
+| SP_DEBUG | false | Should only be set for local development to reroute traffic to localhost |
+| SP_INITIAL_ADMIN_EMAIL | admin@streampipes.apache.org | Installation-time variable for defining the default user name |
+| SP_INITIAL_ADMIN_PASSWORD | admin | Installation-time variable for defining the default user password |
+| SP_INITIAL_SERVICE_USER | sp-service-client | Installation-time variable for defining the initial service user (must be same to the configured user in the extension service) |
+| SP_INITIAL_SERVICE_USER_SECRET | my-apache-streampipes-secret-key-change-me | Installation-time variable for defining the initial service secret (minimum 35 chars) |
+| SP_JWT_SECRET | Empty for Docker, Auto-generated for K8s | JWT secret, base64-encoded, minimum 256 bits |
+| SP_JWT_SIGNING_MODE | HMAC | HMAC or RSA, RSA can be used to authenticate Core-Extensions communication |
+| SP_JWT_PRIVATE_KEY_LOC | Empty | Required id SP_JWT_SIGNING_MODE=RSA, path to the private key, can be generated in the UI (Settings->Security->Generate Key Pair) |
+| SP_ENCRYPTION_PASSCODE | eGgemyGBoILAu3xckolp for Docker, Auto-generated for K8s | Encryption passcode for `SecretStaticProperties` |
+| SP_PRIORITIZED_PROTOCOL | kafka | Messaging layer for data exchange between extensions |
+
+
+### Third-party services
+
+| Env Variable Name | Default Value | Description |
+|------------------------|---------------|---------------------------------------------------------------------------|
+| SP_COUCHDB_HOST | couchdb | The hostname or IP of the CouchDB database |
+| SP_COUCHDB_PROTOCOL | http | The protocol (http or https) of the CouchDB database |
+| SP_COUCHDB_PORT | 5984 | The port of the CouchDB database |
+| SP_COUCHDB_USER | admin | The user of the CouchDB database (must have permissions to add databases) |
+| SP_COUCHDB_PASSWORD | admin | The password of the CouchDB user |
+| SP_TS_STORAGE_HOST | influxdb | The hostname of the timeseries storage (currently InfluxDB) |
+| SP_TS_STORAGE_PORT | 8086 | The port of the timeseries storage |
+| SP_TS_STORAGE_PROTOCOL | http | The protocol of the timeseries storage (http or https) |
+| SP_TS_STORAGE_BUCKET | sp | The InfluxDB storage bucket name |
+| SP_TS_STORAGE_ORG | sp | The InfluxDB storage org |
+| SP_TS_STORAGE_TOKEN | sp-admin | The InfluxDB storage token |
+
+The InfluxDB itself can be configured by providing the variables `DOCKER_INFLUXDB_INIT_PASSWORD` and `DOCKER_INFLUXDB_INIT_ADMIN_TOKEN`. See the `docker-compose` file for details.
+
+## StreamPipes Extensions Service
+
+### Internal
+
+| Env Variable Name | Default Value | Description |
+|--------------------------------|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------|
+| SP_CLIENT_USER | Empty | Service account for communication with Core |
+| SP_CLIENT_SECRET | Empty | Service secret for communication with Core |
+| SP_EXT_AUTH_MODE | sp-service-client | When set to AUTH: all interfaces are only accessible with authentication (requires SP_JET_PRIVATE_KEY_LOC in Core) |
+| SP_JWT_PUBLIC_KEY_LOC | my-apache-streampipes-secret-key-change-me | Path to the public key of the corresponding SP_JWT_PRIVATE_KEY defined in Core |
+
+### Third-party services
+
+The following variables are only required for extensions which require access to the internal time-series storage (the `Data Lake Sink`).
+
+| Env Variable Name | Default Value | Description |
+|------------------------|---------------|---------------------------------------------------------------------------|
+| SP_TS_STORAGE_HOST | influxdb | The hostname of the timeseries storage (currently InfluxDB) |
+| SP_TS_STORAGE_PORT | 8086 | The port of the timeseries storage |
+| SP_TS_STORAGE_PROTOCOL | http | The protocol of the timeseries storage (http or https) |
+| SP_TS_STORAGE_BUCKET | sp | The InfluxDB storage bucket name |
+| SP_TS_STORAGE_ORG | sp | The InfluxDB storage org |
+| SP_TS_STORAGE_TOKEN | sp-admin | The InfluxDB storage token |
+
+
+## Recommended variables
+
+For a standard deployment, it is recommended to customize the following variables:
+
+* Initiales Admin-Passwort (SP_INITIAL_ADMIN_PASSWORD, Core)
+* Initiales Client Secret (SP_INITIAL_SERVICE_USER_SECRET, Core)
+* Client Secret Extensions (SP_CLIENT_USER, Extensions)
+* Encryption Passcode (SP_ENCRYPTION_PASSCODE, Core)
+* CouchDB-Password (SP_COUCHDB_PASSWORD, Core + Extensions + CouchDB)
+* InfluxDB Storage Password (DOCKER_INFLUXDB_INIT_PASSWORD, InfluxDB)
+* InfluxDB Storage Token (SP_TS_STORAGE_TOKEN (Core, Extensions)
+ * DOCKER_INFLUXDB_INIT_ADMIN_TOKEN (InfluxDB service)
+
+## Auto-generation of variables in K8s setups
+
+See the [Kubernetes Guide](05_deploy-kubernetes.md) for an overview of auto-generated variables.
diff --git a/website-v2/versioned_docs/version-0.98.0/05_deploy-kubernetes.md b/website-v2/versioned_docs/version-0.98.0/05_deploy-kubernetes.md
new file mode 100644
index 000000000..6734676b4
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/05_deploy-kubernetes.md
@@ -0,0 +1,269 @@
+---
+id: deploy-kubernetes
+title: Kubernetes Deployment
+sidebar_label: Kubernetes Deployment
+---
+
+## Prerequisites
+Requires Helm (https://helm.sh/) and an actively running Kubernetes cluster.
+
+## Usage
+We provide helm chart options to get you going in the `installer/k8s`folder.
+
+**Starting** the default helm chart option is as easy as simply running the following command from the root of this folder:
+> **NOTE**: Starting might take a while since we also initially pull all Docker images from Dockerhub.
+
+```bash
+helm install streampipes ./
+```
+After a while, all containers should successfully started, indicated by the `Running` status.
+
+The `values.yaml` file contains several configuration options to customize your StreamPipes installation. See the section below for all configuration options.
+
+## Ingress
+
+The helm chart provides several options to configure an Ingress or to define an Ingressroute that directly integrates with Traefik.
+
+## Dynamic Volume Provisioning
+
+You can override the `storageClassName` variable to configure StreamPipes for dynamic volume provisioning.
+
+## Parameters
+
+Here is an overview of the supported parameters to configure StreamPipes.
+
+### Common parameters
+
+| Parameter Name | Description | Value |
+|--------------------------------------------------|---------------------------------------------------------|-----------------------------------------|
+| deployment | Deployment type (lite or full) | lite |
+| preferredBroker | Preferred broker for deployment | "nats" |
+| monitoringSystem | Enable monitoring system (true/false) | false |
+| pullPolicy | Image pull policy | "Always" |
+| restartPolicy | Restart policy for the container | Always |
+| persistentVolumeReclaimPolicy | Reclaim policy for persistent volumes | "Delete" |
+| persistentVolumeAccessModes | Access mode for persistent volumes | "ReadWriteOnce" |
+| initialDelaySeconds | Initial delay for liveness and readiness probes | 60 |
+| periodSeconds | Interval between liveness and readiness probes | 30 |
+| failureThreshold | Number of consecutive failures for readiness probes | 30 |
+| hostPath | Host path for the application | "" |
+
+### StreamPipes common parameters
+
+| Parameter Name | Description | Value |
+|-------------------------------------------------|---------------------------------------------------------|------------------------------------------|
+| streampipes.version | StreamPipes version | "0.93.0-SNAPSHOT" |
+| streampipes.registry | StreamPipes registry URL | "apachestreampipes" |
+| streampipes.auth.secretName | The secret name for storing secrets | "sp-secrets" |
+| streampipes.auth.users.admin.user | The initial admin user | "admin@streampipes.apache.org" |
+| streampipes.auth.users.admin.password | The initial admin password (leave empty for autogen) | "admin" |
+| streampipes.auth.users.service.user | The initial service account user | "sp-service-client" |
+| streampipes.auth.users.service.secret | The initial service account secret | empty (auto-generated) |
+| streampipes.auth.encryption.passcode | Passcode for value encryption | empty (auto-generated) |
+| streampipes.core.appName | StreamPipes backend application name | "backend" |
+| streampipes.core.port | StreamPipes backend port | 8030 |
+| streampipes.core.persistence.storageClassName | Storage class name for backend PVs | "hostpath" |
+| streampipes.core.persistence.storageSize | Size of the backend PV | "1Gi" |
+| streampipes.core.persistence.claimName | Name of the backend PersistentVolumeClaim | "backend-pvc" |
+| streampipes.core.persistence.pvName | Name of the backend PersistentVolume | "backend-pv" |
+| streampipes.core.service.name | Name of the backend service | "backend" |
+| streampipes.core.service.port | TargetPort of the StreamPipes backend service | 8030 |
+| streampipes.ui.appName | StreamPipes UI application name | "ui" |
+| streampipes.ui.resolverActive | Flag for enabling DNS resolver for Nginx proxy | true |
+| streampipes.ui.port | StreamPipes UI port | 8088 |
+| streampipes.ui.resolver | DNS resolver for Nginx proxy | "kube-dns.kube-system.svc.cluster.local" |
+| streampipes.ui.service.name | Name of the UI service | "ui" |
+| streampipes.ui.service.type | Type of the UI service | "ClusterIP" |
+| streampipes.ui.service.nodePort | Node port for the UI service | 8088 |
+| streampipes.ui.service.port | TargetPort of the StreamPipes UI service | 8088 |
+| streampipes.ingress.active | Flag for enabling Ingress for StreamPipes | false |
+| streampipes.ingress.annotations | Annotations for Ingress | {} |
+| streampipes.ingress.host | Hostname for Ingress | "" |
+| streampipes.ingressroute.active | Flag for enabling IngressRoute for StreamPipes | true |
+| streampipes.ingressroute.annotations | Annotations for IngressRoute | {} |
+| streampipes.ingressroute.entryPoints | Entry points for IngressRoute | ["web", "websecure"] |
+| streampipes.ingressroute.host | Hostname for IngressRoute | "" |
+| streampipes.ingressroute.certResolverActive | Flag for enabling certificate resolver for IngressRoute | true |
+| streampipes.ingressroute.certResolver | Certificate resolver for IngressRoute | "" |
+
+
+### Extensions common parameters
+
+| Parameter Name | Description | Value |
+|-------------------------------------------------|---------------------------------------------------------|------------------------------------------|
+| extensions.iiot.appName | IIoT extensions application name | extensions-all-iiot |
+| extensions.iiot.port | Port for the IIoT extensions application | 8090 |
+| extensions.iiot.service.name | Name of the IIoT extensions service | extensions-all-iiot |
+| extensions.iiot.service.port | TargetPort of the IIoT extensions service | 8090 |
+
+
+### External common parameters
+
+#### Couchdb common parameters
+
+| Parameter Name | Description | Value |
+|-------------------------------------------------|----------------------------------------------------------|------------------------------------------|
+| external.couchdb.appName | CouchDB application name | "couchdb" |
+| external.couchdb.version | CouchDB version | 3.3.1 |
+| external.couchdb.user | CouchDB admin username | "admin" |
+| external.couchdb.password | CouchDB admin password | empty (auto-generated) |
+| external.couchdb.port | Port for the CouchDB service | 5984 |
+| external.couchdb.service.name | Name of the CouchDB service | "couchdb" |
+| external.couchdb.service.port | TargetPort of the CouchDB service | 5984 |
+| external.couchdb.persistence.storageClassName | Storage class name for CouchDB PVs | "hostpath" |
+| external.couchdb.persistence.storageSize | Size of the CouchDB PV | "1Gi" |
+| external.couchdb.persistence.claimName | Name of the CouchDB PersistentVolumeClaim | "couchdb-pvc" |
+| external.couchdb.persistence.pvName | Name of the CouchDB PersistentVolume | "couchdb-pv" |
+
+#### Influxdb common parameters
+
+| Parameter Name | Description | Value |
+|-------------------------------------------------|----------------------------------------------------------|------------------------------------------|
+| external.influxdb.appName | InfluxDB application name | "influxdb" |
+| external.influxdb.version | InfluxDB version | 2.6 |
+| external.influxdb.username | InfluxDB admin username | "admin" |
+| external.influxdb.password | InfluxDB admin password | empty (auto-generated) |
+| external.influxdb.adminToken | InfluxDB admin token | empty (auto-generated) |
+| external.influxdb.initOrg | InfluxDB initial organization | "sp" |
+| external.influxdb.initBucket | InfluxDB initial bucket | "sp" |
+| external.influxdb.initMode | InfluxDB initialization mode | "setup" |
+| external.influxdb.apiPort | Port number for the InfluxDB service (API) | 8083 |
+| external.influxdb.httpPort | Port number for the InfluxDB service (HTTP) | 8086 |
+| external.influxdb.grpcPort | Port number for the InfluxDB service (gRPC) | 8090 |
+| external.influxdb.service.name | Name of the InfluxDB service | "influxdb" |
+| external.influxdb.service.apiPort | TargetPort of the InfluxDB service for API | 8083 |
+| external.influxdb.service.httpPort | TargetPort of the InfluxDB service for HTTP | 8086 |
+| external.influxdb.service.grpcPort | TargetPort of the InfluxDB service for gRPC | 8090 |
+| external.influxdb.persistence.storageClassName | Storage class name for InfluxDB PVs | "hostpath" |
+| external.influxdb.persistence.storageSize | Size of the InfluxDB PV | "1Gi" |
+| external.influxdb.persistence.storageSizeV1 | Size of the InfluxDB PV for v1 databases | "1Gi" |
+| external.influxdb.persistence.claimName | Name of the InfluxDBv2 PersistentVolumeClaim | "influxdb2-pvc" |
+| external.influxdb.persistence.claimNameV1 | Name of the InfluxDBv1 PersistentVolumeClaim | "influxdb-pvc" |
+| external.influxdb.persistence.pvName | Name of the InfluxDBv2 PersistentVolume | "influxdb2-pv" |
+| external.influxdb.persistence.pvNameV1 | Name of the InfluxDBv1 PersistentVolume | "influxdb-pv" |
+
+
+#### Nats common parameters
+
+| Parameter Name | Description | Value |
+|-------------------------------------------------|----------------------------------------------------------|------------------------------------------|
+| external.nats.appName | NATS application name | "nats" |
+| external.nats.port | Port for the NATS service | 4222 |
+| external.nats.version | NATS version | |
+| external.nats.service.type | Type of the NATS service | "NodePort" |
+| external.nats.service.externalTrafficPolicy | External traffic policy for the NATS service | "Local" |
+| external.nats.service.name | Name of the NATS service | "nats" |
+| external.nats.service.port | TargetPort of the NATS service | 4222 |
+
+
+#### Kafka common parameters
+
+| Parameter Name | Description | Value |
+|-------------------------------------------------|----------------------------------------------------------|------------------------------------------|
+| external.kafka.appName | Kafka application name | "kafka" |
+| external.kafka.version | Kafka version | 2.2.0 |
+| external.kafka.port | Port for the Kafka service | 9092 |
+| external.kafka.external.hostname | Name which will be advertised to external clients. Clients which use (default) port 9094 | "localhost"
+| external.kafka.service.name | Name of the Kafka service | "kafka" |
+| external.kafka.service.port | TargetPort of the Kafka service | 9092 |
+| external.kafka.service.portOutside | Port for Kafka client outside of the cluster | 9094 |
+| external.kafka.persistence.storageClassName | Storage class name for Kafka PVs | "hostpath" |
+| external.kafka.persistence.storageSize | Size of the Kafka PV | "1Gi" |
+| external.kafka.persistence.claimName | Name of the Kafka PersistentVolumeClaim | "kafka-pvc" |
+| external.kafka.persistence.pvName | Name of the Kafka PersistentVolume | "kafka-pv" |
+|
+
+#### Zookeeper common parameters
+
+| Parameter Name | Description | Value |
+|-------------------------------------------------|----------------------------------------------------------|------------------------------------------|
+| external.zookeeper.appName | ZooKeeper application name | "zookeeper" |
+| external.zookeeper.version | ZooKeeper version | 3.4.13 |
+| external.zookeeper.port | Port for the ZooKeeper service | 2181 |
+| external.zookeeper.service.name | Name of the ZooKeeper service | "zookeeper" |
+| external.zookeeper.service.port | TargetPort of the ZooKeeper service | 2181 |
+| external.zookeeper.persistence.storageClassName | Storage class name for ZooKeeper PVs | "hostpath" |
+| external.zookeeper.persistence.storageSize | Size of the ZooKeeper PV | "1Gi" |
+| external.zookeeper.persistence.claimName | Name of the ZooKeeper PersistentVolumeClaim | "zookeeper-pvc" |
+| external.zookeeper.persistence.pvName | Name of the ZooKeeper PersistentVolume | "zookeeper-pv" |
+
+
+#### Pulsar common parameters
+
+| Parameter Name | Description | Value |
+|-------------------------------------------------|----------------------------------------------------------|------------------------------------------|
+| external.pulsar.appName | pulsar application name | "pulsar" |
+| external.pulsar.version | pulsar version | 3.0.0 |
+| external.pulsar.port | Port for the pulsar service | 6650 |
+| external.pulsar.service.name | Name of the pulsar service | "pulsar" |
+| external.pulsar.service.port | TargetPort of the pulsar service | 6650 |
+| external.pulsar.persistence.storageClassName | Storage class name for pulsar PVs | "hostpath" |
+| external.pulsar.persistence.storageSize | Size of the pulsar PV | "1Gi" |
+| external.pulsar.persistence.claimName | Name of the pulsar PersistentVolumeClaim | "pulsar-pvc" |
+| external.pulsar.persistence.pvName | Name of the pulsar PersistentVolume | "pulsar-pv" |
+
+### Monitoring common parameters
+
+#### Monitoring - Prometheus
+
+| Parameter Name | Description | Value |
+|-------------------------------------------------|----------------------------------------------------------|------------------------------------------|
+| prometheus.appName | Prometheus application name | "prometheus" |
+| prometheus.version | Prometheus version | 2.45.0 |
+| prometheus.port | Prometheus port | 9090 |
+| prometheus.service.name | Prometheus service name | "prometheus" |
+| prometheus.service.port | Prometheus service port | 9090 |
+| prometheus.persistence.storageClassName | Prometheus storage class name | "hostpath" |
+| prometheus.persistence.storageSize | Prometheus storage size | "2Gi" |
+| prometheus.persistence.claimName | Prometheus PVC claim name | "prometheus-pvc" |
+| prometheus.persistence.pvName | Prometheus PV name | "prometheus-pv" |
+| prometheus.persistence.tokenStorageSize | Prometheus token storage size | "16Ki" |
+| prometheus.config.scrapeInterval | Prometheus scrape interval | 10s |
+| prometheus.config.evaluationInterval | Prometheus evaluation interval | 15s |
+| prometheus.config.backendJobName | Prometheus backend job name | "backend" |
+| prometheus.config.extensionsName | Prometheus extensions job name | "extensions-all-iiot" |
+| prometheus.config.tokenFileName | Prometheus token file name | "token" |
+| prometheus.config.tokenFileDir | Prometheus token file directory | "/opt/data"
+
+#### Monitoring - Grafana
+
+| Parameter Name | Description | Value |
+|-------------------------------------------------|----------------------------------------------------------|------------------------------------------|
+| grafana.appName | Grafana application name | "grafana" |
+| grafana.version | Grafana version | 10.1.2 |
+| grafana.port | Grafana port | 3000 |
+| grafana.service.name | Grafana service name | "grafana" |
+| grafana.service.port | Grafana service port | 3000 |
+| grafana.persistence.storageClassName | Grafana storage class name | "hostpath" |
+| grafana.persistence.storageSize | Grafana storage size | "1Gi" |
+| grafana.persistence.claimName | Grafana PVC claim name | "grafana-pvc" |
+| grafana.persistence.pvName | Grafana PV name | "grafana-pv" |
+
+
+## Auto-generation of parameters.
+
+The helm chart includes a `secrets.yaml` file which auto-generates several settings as follows:
+
+```yaml
+
+apiVersion: v1
+kind: Secret
+metadata:
+ name: sp-secrets
+ namespace: {{ .Release.Namespace | quote }}
+type: Opaque
+data:
+ sp-initial-admin-password: {{ ternary (randAlphaNum 10) .Values.streampipes.auth.users.admin.password (empty .Values.streampipes.auth.users.admin.password) | b64enc | quote }}
+ sp-initial-client-secret: {{ ternary (randAlphaNum 35) .Values.streampipes.auth.users.service.secret (empty .Values.streampipes.auth.users.service.secret) | b64enc | quote }}
+ sp-encryption-passcode: {{ ternary (randAlphaNum 20) .Values.streampipes.auth.encryption.passcode (empty .Values.streampipes.auth.encryption.passcode) | b64enc | quote }}
+ sp-couchdb-password: {{ ternary (randAlphaNum 20) .Values.external.couchdb.password (empty .Values.external.couchdb.password) | b64enc | quote }}
+ sp-ts-storage-password: {{ ternary (randAlphaNum 20) .Values.external.influxdb.password (empty .Values.external.influxdb.password) | b64enc | quote }}
+ sp-ts-storage-token: {{ ternary (randAlphaNum 20) .Values.external.influxdb.adminToken (empty .Values.external.influxdb.adminToken) | b64enc | quote }}
+
+```
+
+
+## Deleting the current helm chart deployment:
+```bash
+helm uninstall streampipes
+```
diff --git a/website-v2/versioned_docs/version-0.98.0/05_deploy-retention-config.md b/website-v2/versioned_docs/version-0.98.0/05_deploy-retention-config.md
new file mode 100644
index 000000000..f19a68114
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/05_deploy-retention-config.md
@@ -0,0 +1,207 @@
+---
+id: deploy-retention-config
+title: Enable Datalake Retention
+sidebar_label: Enable Datalake Retention
+---
+
+This page provides instructions on how to enable and test the Datalake retention feature. The Datalake retention feature automates the process of deleting and saving the contents of the Datalake to either a local filesystem or a cloud provider (currently, only S3-compatible providers are supported) at predefined intervals. Retention actions are carried out as scheduled CRON jobs, executing at specified times.
+
+## Prerequisites
+
+To use a cloud provider, you must have an existing S3-compatible provider, along with the necessary authentication key, secret, and bucket. Alternatively, you can use the test settings provided below.
+
+## Settings
+
+### Deployment Setting
+
+To enable the usage of the retention feature depending on the exact setting, two environment variables need to be set during streampipes deployment.
+
+```yaml
+
+ "SP_RETENTION_LOCAL_DIR":"/output",
+ "SP_DATALAKE_SCHEDULER_CRON":"0 1 0 * * 6"
+
+```
+
+The `SP_DATALAKE_SCHEDULER_CRON` environment variable defines when the CRON job will run. By default, the job runs every Saturday at 00:01 (using the cron expression "0 1 0 * * 6"). For development environments, shorter intervals are often more useful. For example, setting it to "0 */2 * * * *" will execute the job every two minutes.
+
+When using local file storage, you can specify the storage directory via the `SP_RETENTION_LOCAL_DIR` variable. If you need the data to be accessible outside the Docker container, an additional volume mapping will be required in the backend.
+
+```yaml
+[...]
+ backend:
+ [...]
+ volumes:
+ - ./output/:/output
+
+[...]
+```
+
+### Configure Retention for a Measure
+
+The retention configuration must be set individually for each desired DataLake. To configure retention settings:
+
+1. Navigate to **Configuration > DataLake**.
+2. Click on the **Retention Rate** icon in the corresponding column.
+3. A dialog will appear, allowing you to configure the following options:
+ - **Data to Retain**: Select which data should be retained.
+ - **Retention Action**: Choose the retention action:
+ - **Delete**
+ - **Save**
+ - **Save and Delete**
+
+If **Save** is selected, you can also configure:
+
+- **Export Format**: Specify the format in which the data will be exported.
+- **Export Destination**: Choose the destination for the saved data:
+ - **Folder**: No further configuration needed.
+ - **S3**: Requires an existing Export Provider to be set up (see the section below for details).
+
+To create a new export provider go to `Configuration > DataLake`, click on `+` and provide the access key, secret, endpoint, bucket name, and region.
+
+<img className="docs-image" src="/img/05_deploy-retention-config/NewExportProvider.png" alt="New Export Provider"/>
+
+For the Test Setting below this might be:
+- **Access Key**: test
+- **Access Secret**: test
+- **Endpoint**: http://0.0.0.0:4566
+- **Bucket**: random
+- **Region**: us-east-1
+
+
+
+
+
+## Test Setting
+For Testing and Developing S3-based Export Provider it is possible to rely on locally hosted docker container e.g., localstack.
+```yaml
+services:
+ localstack:
+ image: localstack/localstack:latest
+ container_name: localstack_main
+ environment:
+ - DOCKER_HOST=unix:///var/run/docker.sock
+ - AWS_ACCESS_KEY_ID=test
+ - AWS_SECRET_ACCESS_KEY=test
+ - DEFAULT_REGION=us-east-1
+ - SERVICES=s3
+ ports:
+ - "4566:4566"
+ volumes:
+ - "/var/run/docker.sock:/var/run/docker.sock"
+ - "localstack_data:/var/lib/localstack"
+volumes:
+ localstack_data:
+ driver: local
+```
+
+For local testing start the container `docker compose up`, create a new bucket with the following java script:
+
+```java
+
+import java.net.URI;
+import java.nio.file.Path;
+import java.nio.file.Paths;
+
+import software.amazon.awssdk.auth.credentials.AwsBasicCredentials;
+import software.amazon.awssdk.auth.credentials.StaticCredentialsProvider;
+import software.amazon.awssdk.regions.Region;
+import software.amazon.awssdk.services.s3.S3Client;
+import software.amazon.awssdk.services.s3.model.*;
+
+public class S3TestClean {
+
+ private static final String ACCESS_KEY = "test";
+ private static final String SECRET_KEY = "test";
+ private static final String ENDPOINT = "http://0.0.0.0:4566";
+ private static final Region REGION = Region.US_EAST_1;
+ private static final String BUCKET_NAME = "random";
+
+
+ public static void main(String[] args) {
+ System.setProperty("software.amazon.awssdk.enableDefaultMetrics", "true");
+
+ try (S3Client s3 = createS3Client()) {
+ createBucketIfNotExists(s3, BUCKET_NAME);
+ listBuckets(s3);
+ listObjects(s3);
+ } catch (Exception e) {
+ e.printStackTrace();
+ }
+ }
+
+ private static S3Client createS3Client() {
+ return S3Client.builder()
+ .endpointOverride(URI.create(ENDPOINT))
+ .region(REGION)
+ .credentialsProvider(
+ StaticCredentialsProvider.create(
+ AwsBasicCredentials.create(ACCESS_KEY, SECRET_KEY)
+ )
+ )
+ .build();
+ }
+
+ private static void createBucketIfNotExists(S3Client s3, String bucketName) {
+ System.out.println("Checking if bucket exists: " + bucketName);
+ try {
+ ListBucketsResponse response = s3.listBuckets();
+ boolean exists = response.buckets().stream()
+ .anyMatch(bucket -> bucket.name().equals(bucketName));
+
+ if (!exists) {
+ System.out.println("Bucket does not exist. Creating: " + bucketName);
+ s3.createBucket(CreateBucketRequest.builder().bucket(bucketName).build());
+ } else {
+ System.out.println("Bucket already exists: " + bucketName);
+ }
+ } catch (S3Exception e) {
+ System.err.println("Failed to check/create bucket: " + e.awsErrorDetails().errorMessage());
+ }
+ }
+
+ private static void listBuckets(S3Client s3) {
+ System.out.println("Listing S3 buckets:");
+ try {
+ ListBucketsResponse response = s3.listBuckets();
+ response.buckets().forEach(bucket -> System.out.println(" - " + bucket.name()));
+ } catch (S3Exception e) {
+ System.err.println("Failed to list buckets: " + e.awsErrorDetails().errorMessage());
+ }
+ }
+
+ private static void listObjects(S3Client s3) {
+ System.out.println("Listing objects in bucket: " + BUCKET_NAME);
+ try {
+ ListObjectsV2Request request = ListObjectsV2Request.builder()
+ .bucket(BUCKET_NAME)
+ .build();
+
+ ListObjectsV2Response response = s3.listObjectsV2(request);
+ response.contents().forEach(obj -> System.out.println("File: " + obj.key()));
+ } catch (S3Exception e) {
+ System.err.println("Failed to list objects: " + e.awsErrorDetails().errorMessage());
+ }
+ }
+
+
+}
+
+```
+Pom.xml dependencies:
+
+```xml
+ <dependency>
+ <groupId>software.amazon.awssdk</groupId>
+ <artifactId>s3</artifactId>
+ <version>2.25.14</version> <!-- Use latest -->
+ </dependency>
+
+ <dependency>
+ <groupId>org.slf4j</groupId>
+ <artifactId>slf4j-api</artifactId>
+ <version>2.0.17</version>
+ </dependency>
+
+
+```
\ No newline at end of file
diff --git a/website-v2/versioned_docs/version-0.98.0/05_deploy-security.md b/website-v2/versioned_docs/version-0.98.0/05_deploy-security.md
new file mode 100644
index 000000000..01c2e024c
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/05_deploy-security.md
@@ -0,0 +1,178 @@
+---
+id: deploy-security
+title: Security
+sidebar_label: Security
+---
+
+## Overriding default settings
+
+At installation time, StreamPipes checks for available environment variables relevant for the securing the system. If they are not set, it will use the default values.
+
+The following variables are checked by the core at installation time:
+
+* SP_INITIAL_ADMIN_EMAIL The email address of the initial administrator.
+* SP_INITIAL_ADMIN_PASSWORD The password of the initial administrator.
+* SP_INITIAL_CLIENT_USER The initial client user, used by the extensions modules to make authenticated API requests to the core.
+* SP_INITIAL_CLIENT_SECRET The default password of the initial client user.
+* SP_SETUP_INSTALL_PIPELINE_ELEMENTS Indicates whether pipeline elements should be installed.
+* SP_ENCRYPTION_PASSCODE The encryption passcode, used for securely storing secrets (e.g., database connection strings).
+* SP_JWT_SECRET The JWT secret, used for signing JWT tokens.
+
+In addition, all extensions services that perform requests to the core will need to have the following environment variables set:
+
+* SP_CLIENT_USER The client user, used by the extensions modules to make authenticated API requests to the core.
+* SP_CLIENT_SECRET The password of the client user.
+
+Note that there are default values for all environment variables that are set at installation time - make sure to change these settings when moving to production!
+
+## Configuration
+
+Most security-related settings can be set in the configuration section of StreamPipes. The *General* section allows to set self-service registration and password recovery (both are disabled by default and require a valid email configuration).
+In the *Security* section, users, service accounts, roles and groups can be configured.
+
+
+## User types
+
+StreamPipes distinguishes between User Accounts (real users that interact with StreamPipes over the UI or an API) and Service Accounts (user-independent accounts which solely use StreamPipes over the API).
+
+User accounts are typically used by extensions service that require API access to the core (e.g., to get a list of running pipelines).
+
+## Permissions
+
+StreamPipes v0.69.0 comes with more advanced mechanisms to manage permissions.
+For each major resource (pipeline elements, pipelines, StreamPipes Connect adapters, dashboards, data explorer views), permissions can be assigned individually to users and groups.
+
+To ease permission handling, StreamPipes comes with a default number of roles with pre-assigned privileges:
+
+### Roles
+
+* Admin The administrator role has full access to all resources.
+* Service Admin The service administrator role has full access to all resources, but has no access to the UI.
+* Pipeline Admin has full control of pipelines (create, edit, delete, start, stop, pause, resume, etc.).
+* Pipeline User has limited control of pipelines (read only).
+* Dashboard Admin has full control of dashboards (create, edit, delete, etc.).
+* Dashboard User has limited control of dashboards (read only).
+* Data Explorer Admin has full control of data explorer views (create, edit, delete, etc.).
+* Data Explorer User has limited control of data explorer views (read only).
+* Connect Admin has full control of StreamPipes Connect adapters (create, edit, delete, etc.).
+
+### Groups
+
+Roles can be either assigned to specific users or groups. Any group can contain several members.
+The permissions of a user are the union of the permissions of all roles assigned to the user and the groups to which the user belongs.
+
+### Changing permissions
+
+Any resource has a resource owner, which is the authority that created the resource. Resources can be either public or private. Public resources are available to all users, while the user role determines what the user can do with the resource.
+E.g., a public pipeline created by a user of role ROLE_ADMIN can be edited by all users with role PIPELINE_ADMIN, while the same pipeline can be read by all users with role PIPELINE_USER.
+
+Permissions can only be changed by admin users currently.
+In the overview section of each resource (e.g., pipelines and dashboards), a permission dialog is available to users with role ROLE_ADMIN. The dialog allows to assign users and groups to the individual resource.
+
+
+## OAuth configuration
+
+It is possible to connect StreamPipes to an external authentication provider such as Keycloak, Azure AD or GitHub.
+Multiple providers can be configured.
+
+To enable login over OAuth, several environment variables are available
+
+### General settings
+
+* `SP_OAUTH_ENABLED` set to `true` to enable OAuth
+* `SP_OAUTH_REDIRECT_URI` set to the base URI where StreamPipes is running, e.g., `http://localhost:80`
+
+### Provider-specific settings
+
+For each configured provider, individual settings can be provided. The scheme for environment variables is `SP_OAUTH_{PROVIDER_ID}.*`.
+For instance, if you want to define two providers Azure and GitHub, you can add an individual block `SP_OAUTH_PROVIDER_AZURE.*` and `SP_OAUTH_PROVIDER_GITHUB` to provide the individual authentication settings for each provider.
+
+The following provider-specific settings are available:
+
+* `SP_OAUTH_PROVIDER_{PROVIDER_ID}_AUTHORIZATION_URI`, the authorization URI
+* `SP_OAUTH_PROVIDER_{PROVIDER_ID}_CLIENT_ID`, the OAuth client id
+* `SP_OAUTH_PROVIDER_{PROVIDER_ID}_CLIENT_NAME`, the OAuth client name
+* `SP_OAUTH_PROVIDER_{PROVIDER_ID}_CLIENT_SECRET`, the OAuth client secret
+* `SP_OAUTH_PROVIDER_{PROVIDER_ID}_EMAIL_ATTRIBUTE_NAME`, the JWT attribute name for the email field, e.g., `email`
+* `SP_OAUTH_PROVIDER_{PROVIDER_ID}_FULL_NAME_ATTRIBUTE_NAME`, the JWT attribute name for the full username, e.g., `name`(optional)
+* `SP_OAUTH_PROVIDER_{PROVIDER_ID}_ISSUER_URI`, the OAuth issuer URI
+* `SP_OAUTH_PROVIDER_{PROVIDER_ID}_JWK_SET_URI`, the OAuth JWK Set URI
+* `SP_OAUTH_PROVIDER_{PROVIDER_ID}_NAME`, The provider name (used to display the login button in the UI), e.g. `Azure`
+* `SP_OAUTH_PROVIDER_{PROVIDER_ID}_SCOPES`, the requested OAuth scopes, comma-separated, e.g., `openid,profile,email`
+* `SP_OAUTH_PROVIDER_{PROVIDER_ID}_TOKEN_URI`, the OAuth token URI
+* `SP_OAUTH_PROVIDER_{PROVIDER_ID}_USER_ID_ATTRIBUTE_NAME`, the JWT attribute name for the user ID field, e.g. `sub`
+* `SP_OAUTH_PROVIDER_{PROVIDER_ID}_USER_INFO_URI`, the OIDC user info endpoint, e.g., `https://graph.microsoft.com/oidc/userinfo`
+
+### Example: Authentication with Azure AD
+
+This example shows how to configure Azure AD as an authentication backend. The example is provided as an IntelliJ env file as used by the StreamPipes core:
+Replace the placeholders and the `SP_OAUTH_REDIRECT_URI` with your individual settings.
+
+```xml
+<component name="ProjectRunConfigurationManager">
+ <configuration default="false" name="core" type="SpringBootApplicationConfigurationType" factoryName="Spring Boot">
+ <envs>
+ <env name="SP_OAUTH_PROVIDER_AZURE_AUTHORIZATION_URI" value="https://login.microsoftonline.com/{TENANT_ID}/oauth2/v2.0/authorize" />
+ <env name="SP_OAUTH_PROVIDER_AZURE_CLIENT_ID" value="{CLIENT_ID}" />
+ <env name="SP_OAUTH_PROVIDER_AZURE_CLIENT_NAME" value="{CLIENT_NAME}" />
+ <env name="SP_OAUTH_PROVIDER_AZURE_CLIENT_SECRET" value="{CLIENT_SECRET}" />
+ <env name="SP_OAUTH_PROVIDER_AZURE_EMAIL_ATTRIBUTE_NAME" value="email" />
+ <env name="SP_OAUTH_PROVIDER_AZURE_FULL_NAME_ATTRIBUTE_NAME" value="name" />
+ <env name="SP_OAUTH_PROVIDER_AZURE_ISSUER_URI" value="https://login.microsoftonline.com/{TENANT_ID}/v2.0" />
+ <env name="SP_OAUTH_PROVIDER_AZURE_JWK_SET_URI" value="https://login.microsoftonline.com/{TENANT_ID}/discovery/v2.0/keys" />
+ <env name="SP_OAUTH_PROVIDER_AZURE_NAME" value="Azure" />
+ <env name="SP_OAUTH_PROVIDER_AZURE_SCOPES" value="openid,profile,email" />
+ <env name="SP_OAUTH_PROVIDER_AZURE_TOKEN_URI" value="https://login.microsoftonline.com/{TENANT_ID}/oauth2/v2.0/token" />
+ <env name="SP_OAUTH_PROVIDER_AZURE_USER_ID_ATTRIBUTE_NAME" value="sub" />
+ <env name="SP_OAUTH_PROVIDER_AZURE_USER_INFO_URI" value="https://graph.microsoft.com/oidc/userinfo" />
+ <env name="SP_OAUTH_REDIRECT_URI" value="http://localhost:8082" />
+ <env name="SP_OAUTH_ENABLED" value="true" />
+ </envs>
+ <module name="streampipes-service-core" />
+ <option name="SPRING_BOOT_MAIN_CLASS" value="org.apache.streampipes.service.core.StreamPipesCoreApplication" />
+ <method v="2">
+ <option name="Make" enabled="true" />
+ </method>
+ </configuration>
+</component>
+```
+
+### Example: Authentication with GitHub
+
+Note that you need to provide the environment variables `SP_OAUTH_REDIRECT_URI` and `SP_OAUTH_ENABLED` only once in case you configure more than one provider.
+
+```xml
+<component name="ProjectRunConfigurationManager">
+ <configuration default="false" name="core" type="SpringBootApplicationConfigurationType" factoryName="Spring Boot">
+ <envs>
+ <env name="SP_OAUTH_PROVIDER_GITHUB_AUTHORIZATION_URI" value="https://github.com/login/oauth/authorize" />
+ <env name="SP_OAUTH_PROVIDER_GITHUB_CLIENT_ID" value="{CLIENT_ID}" />
+ <env name="SP_OAUTH_PROVIDER_GITHUB_CLIENT_NAME" value="{CLIENT_NAME}" />
+ <env name="SP_OAUTH_PROVIDER_GITHUB_CLIENT_SECRET" value="{CLIENT_SECRET}" />
+ <env name="SP_OAUTH_PROVIDER_GITHUB_EMAIL_ATTRIBUTE_NAME" value="email" />
+ <env name="SP_OAUTH_PROVIDER_GITHUB_NAME" value="Github" />
+ <env name="SP_OAUTH_PROVIDER_GITHUB_SCOPES" value="read:email" />
+ <env name="SP_OAUTH_PROVIDER_GITHUB_TOKEN_URI" value="https://github.com/login/oauth/access_token" />
+ <env name="SP_OAUTH_PROVIDER_GITHUB_USER_ID_ATTRIBUTE_NAME" value="id" />
+ <env name="SP_OAUTH_PROVIDER_GITHUB_USER_INFO_URI" value="https://api.github.com/user" />
+ <env name="SP_OAUTH_REDIRECT_URI" value="http://localhost:8082" />
+ <env name="SP_OAUTH_ENABLED" value="true" />
+ </envs>
+ <module name="streampipes-service-core" />
+ <option name="SPRING_BOOT_MAIN_CLASS" value="org.apache.streampipes.service.core.StreamPipesCoreApplication" />
+ <method v="2">
+ <option name="Make" enabled="true" />
+ </method>
+ </configuration>
+</component>
+```
+
+### Notes
+
+:::warning
+This feature should be considered experimental. Currently, there is no mapping between external users and StreamPipes roles and all newly registered users will be assigned the role `ROLE_ADMIN`.
+:::
+
+Roles can be assigned to users in the same way as default users. In the `Security` settings (see above), for each user the provider is shown. For local users (tagged with the `local` provider), all user settings can be changed.
+For other providers, only roles can be changed and it is not possible to modify the username or email, since these are managed by the external system.
+
diff --git a/website-v2/versioned_docs/version-0.98.0/05_deploy-use-ssl.md b/website-v2/versioned_docs/version-0.98.0/05_deploy-use-ssl.md
new file mode 100644
index 000000000..d5762b8dc
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/05_deploy-use-ssl.md
@@ -0,0 +1,35 @@
+---
+id: deploy-use-ssl
+title: Use SSL
+sidebar_label: Use SSL
+---
+
+This page explains how SSL Certificates can be used to provide transport layer security between your Browser and the Streampipes Backend.
+
+## Prerequisites
+You need a valid Certificate consisting of a Private and a Public Key. Both Keys must be in PEM Format. Please note that your Private Key should never be shared, otherwise the communication can not be considered secure.
+
+## Edit docker-compose.yml
+In order to use SSL you have to open port 443 on the nginx Service. Incoming insecure Traffic on Port 80 will be automatically rerouted to Port 443.
+
+The Environment-Variable NGINX_SSL must be set to "true".
+
+Finally you have to inject the Certificates into the Docker-Container. In the example below, the Certificates are placed in the directory /etc/ssl/private/ on the host machine. Please change the path according to the place where the Certificates are located on your machine. The path after the colon should not be changed!
+```yaml
+[...]
+ nginx:
+ image: apachestreampipes/ui
+ ports:
+ - "80:80"
+ - "443:443"
+ environment:
+ - NGINX_SSL=true
+ volumes:
+ - /etc/ssl/private/private.pem:/etc/nginx/ssl/ssl.pem
+ - /etc/ssl/private/public.pem:/etc/nginx/ssl/cert.pem
+ depends_on:
+ - backend
+ networks:
+ spnet:
+[...]
+```
diff --git a/website-v2/versioned_docs/version-0.98.0/06_extend-archetypes.md b/website-v2/versioned_docs/version-0.98.0/06_extend-archetypes.md
new file mode 100644
index 000000000..a6907f0ee
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/06_extend-archetypes.md
@@ -0,0 +1,46 @@
+---
+id: extend-archetypes
+title: Maven Archetypes
+sidebar_label: Maven Archetypes
+---
+
+In this tutorial we explain how you can use the Maven archetypes to develop your own StreamPipes processors and sinks.
+We use IntelliJ in this tutorial, but it works with any IDE of your choice.
+
+## Prerequisites
+You need to have Maven installed, further you need an up and running StreamPipes installation on your development computer.
+
+## Create Project
+To create a new project, we provide multiple Maven Archteypes.
+Currently, we provide archetypes for standalone Java-based microservices and archetypes for the experimental Flink wrapper.
+The commands required to create a new pipeline element project can be found below. Make sure that you select a version compatible with your StreamPipes installation.
+Copy the command into your terminal to create a new project.
+The project will be created in the current folder.
+First, the ``groupId`` of the resulting Maven artifact must be set.
+We use ``groupId``: ``org.example`` and ``artifactId``: ``ExampleProcessor``.
+You can keep the default values for the other settings, confirm them by hitting enter.
+
+:::info Choosing the right version
+Make sure that the version used to create your archetype matches your running Apache StreamPipes version.
+In the example below, replace `{sp.version}` with the proper version, e.g., `0.92.0`.
+:::
+
+```bash
+mvn archetype:generate \
+ -DarchetypeGroupId=org.apache.streampipes \
+ -DarchetypeArtifactId=streampipes-archetype-extensions-jvm \
+ -DarchetypeVersion={sp.version}
+```
+
+
+## Project structure
+Open the project in your IDE.
+If everything worked, the structure should look similar to the following image.
+In the *main* package, it is defined which processors / sinks you want to activate and the *pe.example* package contains two skeletons for creating a data processor and sink.
+For details, have a look at the other parts of the Developer Guide, where these classes are explained in more depth.
+
+<img src="/img/archetype/project_structure.png" width="30%" alt="Project Structure"/>
+
+## Next steps
+
+Click [here](06_extend-first-processor.md) to learn how to create your first data processor.
diff --git a/website-v2/versioned_docs/version-0.98.0/06_extend-cli.md b/website-v2/versioned_docs/version-0.98.0/06_extend-cli.md
new file mode 100644
index 000000000..a5325119f
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/06_extend-cli.md
@@ -0,0 +1,190 @@
+---
+id: extend-cli
+title: StreamPipes CLI
+sidebar_label: StreamPipes CLI
+---
+
+The StreamPipes command-line interface (CLI) is focused on developers in order to provide an easy entrypoint to set up a suitable dev environment, either planning on developing
+
+* new extensions such as **connect adapters, processors, sinks** or,
+* new core features for **backend** and **ui**.
+
+The main difference between the standard Docker/K8s installation is an improved communication between services running as containers and services running locally for development.
+
+The CLI can be found in the [main repository](https://github.com/apache/streampipes/tree/master/installer/cli) or in the ``installer/cli`` folder of the downloaded source code.
+
+## TL;DR
+
+```bash
+streampipes env --list
+[INFO] Available StreamPipes environment templates:
+pipeline-element
+...
+streampipes env --set pipeline-element
+streampipes up -d
+```
+> **NOTE**: use `./installer/cli/streampipes` if you haven't add it to the PATH and sourced it (see section "Run `streampipes` from anywhere?").
+
+## Prerequisites
+The CLI is basically a wrapper around multiple `docker` and `docker-compose` commands plus some additional sugar.
+
+* Docker >= 17.06.0
+* Docker-Compose >= 1.26.0 (Compose file format: 3.4)
+* Google Chrome (recommended), Mozilla Firefox, Microsoft Edge
+* For Windows Developer: GitBash only
+
+
+Tested on: (***macOS**, **Linux**, **Windows***)
+
+> **NOTE**: If you're using Windows the CLI only works in combination with GitBash - CMD, PowerShell won't work.
+
+
+## CLI commands overview
+
+```
+StreamPipes CLI - Manage your StreamPipes environment with ease
+
+Usage: streampipes COMMAND [OPTIONS]
+
+Options:
+ --help, -h show help
+ --version, -v show version
+
+Commands:
+ clean Remove StreamPipes data volumes, dangling images and network
+ down Stop and remove StreamPipes containers
+ env Inspect and select StreamPipes environments
+ info Get information
+ logs Get container logs for specific container
+ ps List all StreamPipes container for running environment
+ pull Download latest images from Dockerhub
+ restart Restart StreamPipes environment
+ up Create and start StreamPipes container environment
+
+Run 'streampipes COMMAND --help' for more info on a command.
+```
+
+## Usage: Along dev life-cycle
+
+**List** available environment templates.
+```bash
+streampipes env --list
+```
+
+**Inspect** services in an available environment to know what kind of services it is composed of.
+```bash
+streampipes env --inspect pipeline-element
+```
+
+**Set** environment, e.g. `pipeline-element`, if you want to write a new pipeline element.
+```bash
+streampipes env --set pipeline-element
+```
+
+**Start** environment ( default: `dev` mode). Here the service definition in the selected environment is used to start the multi-container landscape.
+> **NOTE**: `dev` mode is enabled by default since we rely on open ports to core service such as `couchdb`, `kafka` etc. to reach from the IDE when developing. If you don't want to map ports (except the UI port), then use the `--no-ports` flag.
+
+```bash
+streampipes up -d
+# start in production mode with unmapped ports
+# streampipes up -d --no-ports
+```
+Now you're good to go to write your new pipeline element :tada: :tada: :tada:
+
+> **HINT for extensions**: Use our [Maven archetypes](https://streampipes.apache.org/docs/extend-archetypes/) to set up a project skeleton and use your IDE of choice for development. However, we do recommend using IntelliJ.
+
+> **HINT for core**: To work on `backend` or `ui` features you need to set the template to `backend` and clone the core repository [streampipes](https://github.com/apache/streampipes) - check the prerequisites there for more information.
+
+**Stop** environment and remove docker container
+```bash
+streampipes down
+# want to also clean docker data volumes when stopping the environment?
+# streampipes down -v
+```
+
+## Additionally, useful commands
+
+**Start individual services only?** We got you! You chose a template that suits your needs and now you only want to start individual services from it, e.g. only Kafka and InfluxDB.
+
+> **NOTE**: the service names need to be present and match your current `.spenv` environment.
+
+```bash
+streampipes up -d kafka influxdb
+```
+
+**Get current environment** (if previously set using `streampipes env --set <environment>`).
+```bash
+streampipes env
+```
+
+**Get logs** of specific service and use optional `--follow` flag to stay attached to the logs.
+```bash
+streampipes logs --follow backend
+```
+
+**Update** all services of current environment
+```bash
+streampipes pull
+```
+
+**Restart** all services of current environment or specific services
+```bash
+streampipes restart
+# restart backend
+# streampipes restart backend
+```
+
+**Clean** your system and remove created StreamPipes Docker volumes, StreamPipes docker network and dangling StreamPipes images of old image layers.
+```bash
+streampipes clean
+# remove volumes, network and dangling images
+# streampipes clean --volumes
+```
+
+## Modify/Create an environment template
+As of now, this step has to be done **manually**. All environments are located in `environments/`.
+
+```bash
+βββ adapter # developing a new connect adapter
+βββ backend # developing core backend features
+βββ basic # wanna run core, UI, connect etc from the IDE?
+βββ full # full version containing more pipeline elements
+βββ lite # few pipeline elements, less memory
+βββ pipeline-element # developing new pipeline-elements
+βββ ui # developing UI features
+```
+**Modifying an existing environment template**. To modify an existing template, you can simply add a `<YOUR_NEW_SERVICE>` to the template.
+> **NOTE**: You need to make sure, that the service your are adding exists in `deploy/standalone/service/<YOUR_NEW_SERVICE>`. If your're adding a completely new service take a look at existing ones, create a new service directory and include a `docker-compose.yml` and `docker-compose.dev.yml` file.
+
+```
+[environment:backend]
+activemq
+kafka
+...
+<YOUR_NEW_SERVICE>
+```
+
+**Creating a new** environment template. To create a new environment template, place a new file `environments/<YOUR_NEW_ENVIRONMENT>` in the template directory. Open the file and use the following schema.
+> **IMPORTANT**: Please make sure to have `[environment:<YOUR_NEW_ENVIRONMENT>]` header in the first line of your new template matching the name of the file. Make sure to use small caps letters (lowercase) only.
+
+```
+[environment:<YOUR_NEW_ENVIRONMENT>]
+<SERVICE_1>
+<SERVICE_2>
+...
+```
+
+## Run `streampipes` from anywhere? No problem
+Simply add the path to this cli directory to your `$PATH` (on macOS, Linux) variable, e.g. in your `.bashrc` or `.zshrc`, or `%PATH%` (on Windows).
+
+For **macOS**, or **Linux**:
+
+```bash
+export PATH="/path/to/streampipes-installer/installer/cli:$PATH"
+```
+
+For **Windows** add `installer\cli` to environment variables, e.g. check this [documentation](https://helpdeskgeek.com/windows-10/add-windows-path-environment-variable/).
+
+
+## Upgrade to new version
+To upgrade to a new version, simply edit the version tag `SP_VERSION` in the `.env` file.
diff --git a/website-v2/versioned_docs/version-0.98.0/06_extend-client.md b/website-v2/versioned_docs/version-0.98.0/06_extend-client.md
new file mode 100644
index 000000000..f584c3d2c
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/06_extend-client.md
@@ -0,0 +1,204 @@
+---
+id: extend-client
+title: StreamPipes Client
+sidebar_label: StreamPipes Client
+---
+
+
+:::info Looking for Python support?
+
+This section explains how to use the Apache StreamPipes Java Client. Please read the Python docs to find out how to use
+the client for Python.
+
+:::
+
+## About the StreamPipes client
+
+Sometimes you don't want to write your own extensions to StreamPipes, but want to interact with StreamPipes from
+external application.
+One example is to influence the lifecycle of pipelines - think of a feature which automatically starts or stops specific
+pipelines that monitor the production of a specific product.
+
+Another example is to gather live data from Apache StreamPipes, e.g., to consume data that has been previously connected
+by an external, standalone application.
+
+For such use cases, we provide the StreamPipes client, which is currently available in Python and Java. This section
+covers the usage of the Java client.
+
+## Using the StreamPipes client
+
+:::info Choosing the right version
+
+Your client library version should match the installed Apache StreamPipes version. Replace `${streampipes.version}` with
+the version of your installation, e.g., `0.92.0`.
+
+:::
+
+In your Java project, add the following dependency to your pom file:
+
+```xml
+
+<dependency>
+ <groupId>org.apache.streampipes</groupId>
+ <artifactId>streampipes-client</artifactId>
+ <version>${streampipes.version}</version>
+</dependency>
+
+```
+
+## Obtaining an API token
+
+<img className="docs-image" src="/img/screenshots/streampipes-profile-token.png" alt="Overview StreamPipes Architecture"/>
+
+To communicate with Apache StreamPipes, you need to provide proper credentials. There are two ways to obtain
+credentials:
+
+* An API token, which is bound to a user. The API token can be generate from the UI clicking on the user icon and then
+ navigate to `Profile/API`.
+* A service user, which can be created by users with role `Admin`.
+
+Service users can have their own permissions, while API tokens inherit all permissions from the corresponding user.
+
+## Connecting to StreamPipes
+
+Once you have your API token and configured your dependencies, you can connect to an Apache StreamPipes instance as
+follows:
+
+```java
+
+CredentialsProvider credentials=StreamPipesCredentials
+ .withApiKey("admin@streampipes.apache.org","YOUR_API_KEY");
+
+// Create an instance of the StreamPipes client
+ StreamPipesClient client=StreamPipesClient
+ .create("localhost",8082,credentials,true);
+
+```
+
+The following configurations are required:
+
+* The `withApiKey` method expects the username and the API key. Alternatively, use the `withServiceToken` method to
+ authenticate as a service user.
+* The client instance requires the hostname or IP address of your running StreamPipes instance. In addition, you need to
+ provide the port, the credentials object and a flag which needs to be set in case the StreamPipes instance is not
+ served over HTTPS.
+* There are short-hand convenience options to create a client instance.
+
+## Working with the client
+
+Here are some examples how you can work with the StreamPipes client:
+
+```java
+
+// Get streams
+List<SpDataStream> streams=client.streams().all();
+
+// Get a specific stream
+ Optional<SpDataStream> stream=client.streams().get("STREAM_ID");
+
+// see the schema of a data stream
+ EventSchema schema=stream.get().getEventSchema();
+
+// print the list of fields of this stream
+ List<EventProperty> fields=schema.getEventProperties();
+
+// Get all pipelines
+ List<Pipeline> pipelines=client.pipelines().all();
+
+// Start a pipeline
+ PipelineOperationStatus status=client.pipelines().start(pipelines.get(0));
+
+// Stop a pipeline with providing a pipeline Id
+ PipelineOperationStatus status=client.pipelines().stop("PIPELINE_ID");
+
+// Get all pipeline element templates
+ List<PipelineElementTemplate> templates=client.pipelineElementTemplates().all();
+
+// Get all data sinks
+ List<DataSinkInvocation> dataSinks=client.sinks().all();
+
+
+```
+
+## Consuming live data
+
+StreamPipes supports a variety of messaging protocols to internally handle data streams. If you plan to gather live data
+from the client library, you also need to add one or more of the supported messaging
+protocols to the pom file. The default protocol depends on the StreamPipes configuration and is set in the `.env` file
+in your installation folder.
+
+```xml
+
+<!-- For Kafka support -->
+<dependency>
+ <groupId>org.apache.streampipes</groupId>
+ <artifactId>streampipes-messaging-kafka</artifactId>
+ <version>${streampipes.version}</version>
+</dependency>
+
+ <!-- For Nats support -->
+<dependency>
+<groupId>org.apache.streampipes</groupId>
+<artifactId>streampipes-messaging-nats</artifactId>
+<version>${streampipes.version}</version>
+</dependency>
+
+
+ <!-- For MQTT support -->
+<dependency>
+<groupId>org.apache.streampipes</groupId>
+<artifactId>streampipes-messaging-mqtt</artifactId>
+<version>${streampipes.version}</version>
+</dependency>
+
+```
+
+In addition, add the message format that is used internally by StreamPipes. The default message format used by
+StreamPipes is JSON, so let's include the dependency as well:
+
+```xml
+
+<!-- For JSON support -->
+<dependency>
+ <groupId>org.apache.streampipes</groupId>
+ <artifactId>streampipes-dataformat-json</artifactId>
+ <version>${streampipes.version}</version>
+</dependency>
+
+```
+
+Once you've imported the dependencies, it is easy to consume live data. First, register the protocols and formats in
+your client instance:
+
+```java
+
+client.registerProtocol(new SpKafkaProtocolFactory());
+
+// or Nats:
+ client.registerProtocol(new SpNatsProtocolFactory());
+
+// data format:
+ client.registerDataFormat(new JsonDataFormatFactory());
+
+```
+
+Then, you are ready to consume data:
+
+```java
+
+client.streams().subscribe(dataStreams.get(0),new EventProcessor() {
+@Override
+public void onEvent(Event event) {
+ // example
+ MapUtils.debugPrint(System.out,"event",event.getRaw());
+ }
+ });
+
+```
+
+:::tip
+
+There are many more options to work with the StreamPipes Client - e.g., you can trigger emails directly from the API.
+Just explore the various classes and interfaces provided by the client!
+
+:::
diff --git a/website-v2/versioned_docs/version-0.98.0/06_extend-customize-ui.md b/website-v2/versioned_docs/version-0.98.0/06_extend-customize-ui.md
new file mode 100644
index 000000000..c09823ffb
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/06_extend-customize-ui.md
@@ -0,0 +1,226 @@
+---
+id: extend-customize-ui
+title: UI customization
+sidebar_label: UI customization
+---
+
+
+## Custom theme
+
+It is possible to use a custom theme with individual styles, logos and images instead of the default StreamPipes theme.
+
+In this section, we describe the necessary steps to build and deploy a custom theme.
+
+
+### Prerequisite: Learn how to run and build the UI
+
+To use a custom theme, it is required to build the UI with the custom settings.
+In general, the UI can be found in the `ui` folder of the source code.
+
+Perform the following steps to build the UI;
+
+```bash
+
+# Install all necessary packages
+npm install
+
+# Start the UI for development purposes
+npm run start
+
+# Build the StreamPipes UI
+npm run build
+
+```
+
+## Customizable assets
+
+The following assets can be provided in a customized theme:
+
+* **Logo** This is the main logo image, which is shown e.g., on the login page.
+* **Navigation Logo** This is the logo which appears in the top navigation bar after successful login
+* **Favicon** The favicon is shown in the browser navbar. It is also used as the loading animation in StreamPipes.
+* **String constants** Customizable strings, e.g., when you want to use another application name than **Apache StreamPipes**.
+* **Theme variables** An scss file which defines custom colors and layouts.
+
+## Customize constants
+
+To customize constants, you can create a custom file `app.constants.ts` and modify the content based on the template below:
+
+```javascript
+
+import {Injectable} from '@angular/core';
+
+@Injectable()
+export class AppConstants {
+
+ public readonly APP_NAME = "Apache StreamPipes";
+ public readonly APP_TITLE = 'Apache StreamPipes';
+ public readonly EMAIL = "admin@streampipes.apache.org";
+}
+
+
+```
+
+## Customize theme
+
+To customize the theme, we provide a file named `variables.scss` which can be overridden with default color and style settings.
+
+See the example below:
+
+```scss
+
+/*!
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+$sp-color-primary: rgb(57, 181, 74);
+$sp-color-primary-600: #06c12a;
+
+$sp-color-accent: #1b1464;
+
+$sp-color-accent-light-blue: rgb(59, 92, 149);
+$sp-color-accent-light: rgb(156, 156, 156);
+$sp-color-accent-light-transparent: rgba(156, 156, 156, 0.4);
+
+$sp-color-accent-dark: #83a3de;
+
+$sp-color-adapter: #7f007f;
+$sp-color-stream: #ffeb3b;
+$sp-color-processor: #009688;
+$sp-color-sink: #3f51b5;
+
+$sp-color-error: #b71c1c;
+
+body {
+ --color-data-view: rgb(122, 206, 227);
+ --color-dashboard: rgb(76, 115, 164);
+ --color-adapter: rgb(182, 140, 97);
+ --color-data-source: #ffeb3b;
+ --color-pipeline: rgb(102, 185, 114);
+ --color-measurement: rgb(39, 164, 155);
+ --color-file: rgb(163, 98, 190);
+
+ --button-border-radius: 5px;
+ --iconbar-width: 35px;
+ --navbar-icon-border-radius: 0;
+ --navbar-icon-padding: 0;
+}
+
+:root {
+ --color-loading-bar: #{$sp-color-accent};
+}
+
+.dark-mode {
+ --color-primary: #{$sp-color-primary};
+ --color-accent: #{$sp-color-accent-dark};
+ --color-bg-outer: var(--color-bg-1);
+ --color-bg-page-container: var(--color-bg-0);
+ --color-bg-main-panel-header: var(--color-bg-0);
+ --color-bg-main-panel-content: var(--color-bg-0);
+ --color-bg-navbar-icon: inherit;
+ --color-bg-navbar-icon-selected: inherit;
+ --color-bg-0: #121212;
+ --color-bg-1: #282828;
+ --color-bg-2: #404040;
+ --color-bg-3: #424242;
+ --color-bg-4: #5f5f5f;
+ --color-bg-dialog: rgb(66, 66, 66);
+ --color-shadow: #c4c4c4;
+ --color-pe: #404040;
+ --color-default-text: rgba(255, 255, 255, 0.87);
+ --color-warn: #b36161;
+
+ --color-tab-border: #cccccc;
+
+ --color-navigation-bg: var(--color-primary);
+ --color-navigation-link-text: var(--color-bg-0);
+ --color-navigation-text: #121212;
+ --color-navigation-selected: #{$sp-color-primary};
+ --color-navigation-hover: #{$sp-color-primary-600};
+ --color-navigation-bg-selected: var(--color-bg-1);
+ --color-navigation-divider: #{$sp-color-primary};
+
+ --content-box-color: #404040;
+ --canvas-color: linear-gradient(
+ 90deg,
+ rgba(50, 50, 50, 0.5) 10%,
+ transparent 0%
+ ),
+ linear-gradient(rgba(50, 50, 50, 0.5) 10%, transparent 0%);
+}
+
+.light-mode {
+ --color-primary: #{$sp-color-primary};
+ --color-accent: #{$sp-color-accent};
+ --color-bg-outer: var(--color-bg-1);
+ --color-bg-page-container: var(--color-bg-0);
+ --color-bg-main-panel-header: var(--color-bg-0);
+ --color-bg-main-panel-content: var(--color-bg-0);
+ --color-bg-navbar-icon: inherit;
+ --color-bg-navbar-icon-selected: inherit;
+ --color-bg-0: #ffffff;
+ --color-bg-1: #fafafa;
+ --color-bg-2: #f1f1f1;
+ --color-bg-3: rgb(224, 224, 224);
+ --color-bg-4: rgb(212, 212, 212);
+ --color-bg-dialog: #ffffff;
+ --color-shadow: #555;
+ --color-pe: #ffffff;
+ --color-default-text: #121212;
+ --color-warn: #b71c1c;
+
+ --color-tab-border: #cccccc;
+
+ --color-navigation-bg: var(--color-primary);
+ --color-navigation-link-text: var(--color-bg-0);
+ --color-navigation-text: #ffffff;
+ --color-navigation-selected: #{$sp-color-primary};
+ --color-navigation-hover: #{$sp-color-primary-600};
+ --color-navigation-bg-selected: var(--color-bg-1);
+ --color-navigation-divider: var(--color-primary);
+
+ --content-box-color: rgb(156, 156, 156);
+ --canvas-color: linear-gradient(
+ 90deg,
+ rgba(208, 208, 208, 0.5) 10%,
+ transparent 0%
+ ),
+ linear-gradient(rgba(208, 208, 208, 0.5) 10%, transparent 0%);
+}
+
+```
+## Run a customized build
+
+To create a new UI build with customized themes, use the following command:
+
+````bash
+
+UI_LOC=PATH_TO_FOLDER_WITH_CUSTOM_TEMPLATES \\
+THEME_LOC=$UI_LOC/_variables.scss \\
+LOGO_HEADER_LOC=$UI_LOC/img/logo.png \\
+FAVICON_LOC=$UI_LOC/img/favicon.png \\
+LOGO_NAV_LOC=$UI_LOC/img/logo-navigation.png \\
+CONSTANTS_FILE=$UI_LOC/app.constants.ts \\
+npm run build
+
+````
+
+First, we create a helper environment variable that links to a folder which includes custom logos, the theme file and constants.
+Next, we set the variables above to override default logos and stylings.
+Finally, the usual build process is executed.
+
+Once finished, you've successfully customized an Apache StreamPipes instance!
diff --git a/website-v2/versioned_docs/version-0.98.0/06_extend-first-processor.md b/website-v2/versioned_docs/version-0.98.0/06_extend-first-processor.md
new file mode 100644
index 000000000..96080508f
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/06_extend-first-processor.md
@@ -0,0 +1,54 @@
+---
+id: extend-first-processor
+title: Your first data processor
+sidebar_label: Your first data processor
+---
+
+In this section, we will explain how to start a pipeline element service and install it using the StreamPipes UI.
+
+Open the class *ExampleDataProcessor* and edit the ``onEvent`` method to print the incoming event, log it to the console and send it to the next component without changing it.
+
+```java
+@Override
+public void onEvent(Event event, SpOutputCollector collector) {
+ // Print the incoming event on the console
+ System.out.println(event);
+
+ // Hand the incoming event to the output collector without changing it.
+ collector.collect(event);
+}
+```
+
+## Start Processor
+Starting from StreamPipes 0.69.0, the IP address of an extensions service (processor, adapter or sink) will be auto-discovered upon start.
+The auto-discovery is done by the StreamPipes service discovery mechanism and should work for most setups.
+Once you start an extensions service, you will see the chosen IP in printed in the console. Make sure that this IP does not point to localhost (127.0.0.1).
+If you see such an IP or the extensions service complains that it cannot resolve the IP, you can manually set the IP address of the extensions service. You can do so by providing an <code>SP_HOST</code> environment variable.
+
+
+<img src="/img/archetype/endpoint.png" width="90%" alt="Project Structure"/>
+
+To check if the service is up and running, open the browser on *'localhost:8090'* (or the port defined in the service definition). The machine-readable description of the processor should be visible as shown below.
+
+
+:::caution Common Problems
+If the service description is not shown on 'localhost:8090', you might have to change the port address.
+This needs to be done in the configuration of your service, further explained in the configurations part of the developer guide.
+
+If the service does not show up in the StreamPipes installation menu, click on 'MANAGE ENDPOINTS' and add 'http://<span></span>YOUR_IP_OR_DNS_NAME:8090'.
+Use the IP or DNS name you provided as the SP_HOST variable or the IP (if resolvable) found by the auto-discovery service printed in the console.
+After adding the endpoint, a new processor with the name *Example* should show up.
+:::
+
+Now you can go to StreamPipes.
+Your new processor *'Example'* should now show up in the installation menu ("Install Pipeline Elements" in the left navigation bar).
+Install it, then switch to the pipeline view and create a simple pipeline that makes use of your newly created processor.
+In case you opened the StreamPipes installation for the first time, it should have been automatically installed during the setup process.
+
+<img src="/img/archetype/example_pipeline.png" width="80%" alt="Project Structure"/>
+
+Start this pipeline.
+Now you should see logging messages in your console and, once you've created a visualization, you can also see the resulting events of your component in StreamPipes.
+
+Congratulations, you have just created your first processor!
+From here on you can start experimenting and implement your own algorithms.
diff --git a/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-event-model.md b/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-event-model.md
new file mode 100644
index 000000000..42cc8d472
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-event-model.md
@@ -0,0 +1,141 @@
+---
+id: extend-sdk-event-model
+title: "SDK Guide: Event Model"
+sidebar_label: "SDK: Event Model"
+---
+
+## Introduction
+
+This guide explains the usage of the event model to manipulate runtime events for data processors and data sink.
+
+## Prerequisites
+
+This guide assumes that you are already familiar with the basic setup of [data processors](06_extend-first-processor.md).
+
+### Property Selectors
+
+In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned ``MappingProperty`` (see the guide on [static properties](extend-sdk-static-properties)).
+
+Mapping properties return a ``PropertySelector`` that identifies a field based on (i) the **streamIndex** and (ii) the runtime name of the field.
+Let's assume we have an event with the following structure:
+
+```json
+{
+ "timestamp" : 1234556,
+ "temperature" : 37.0,
+ "deviceId" : "sensor1",
+ "running" : true,
+ "location" : {"latitude" : 34.4, "longitude" : -47},
+ "lastValues" : [45, 22, 21]
+}
+```
+
+In addition, we assume that a data processor exists (with one input node) that converts the temperature value (measured in degrees celsius) to a degree fahrenheit value.
+In this case, a mapping property (selected by the pipeline developer in the StreamPipes UI) would link to the ``temperature`` field of the event.
+
+The mapping property value will be the ``PropertySelector`` of the temperature value, which looks as follows:
+
+```
+s0::temperature
+```
+
+``s0`` identifies the stream (in this case, only one input streams exist, but as data processors might require more than one input stream, a stream identifier is required), while the appendix identifies the runtime name.
+
+Note: If you add a new field to an input event, you don't need to provide the selector, you can just assign the runtime name as defined by the [output strategy](extend-sdk-output-strategies).
+
+### Reading Fields
+
+You can get a field from an event by providing the corresponding selector:
+
+```java
+
+@Override
+ public void onEvent(Event event, SpOutputCollector out) {
+
+ PrimitiveField temperatureField = event.getFieldBySelector(PROPERTY_SELECTOR).getAsPrimitive();
+ }
+
+```
+
+Similarly, if your mapping property links to a nested property, use
+
+```java
+
+@Override
+ public void onEvent(Event event, SpOutputCollector out) {
+
+ NestedField nestedField = event.getFieldBySelector(PROPERTY_SELECTOR).getAsNested();
+ }
+
+```
+
+and for a list-based field:
+
+```java
+
+@Override
+ public void onEvent(Event event, SpOutputCollector out) {
+
+ ListField listField = event.getFieldBySelector(PROPERTY_SELECTOR).getAsList();
+ }
+
+```
+
+### Parsing Fields
+
+#### Primitive Fields
+
+A ``PrimitiveField`` contains convenience methods to directly cast a field to the target datatype:
+
+```java
+
+// parse the value as a float datatype
+Float temperatureValue = event.getFieldBySelector(temperatureSelector).getAsPrimitive().getAsFloat();
+
+// or do the same with a double datatype
+Double temperatureValue = event.getFieldBySelector(temperatureSelector).getAsPrimitive().getAsDouble();
+
+// extracting a string
+String deviceId = event.getFieldBySelector(deviceIdSelector).getAsPrimitive().getAsString();
+
+// this also works for extracting fields from nested fields:
+Double latitude = event.getFieldBySelector(latitudeSelector).getAsPrimitive().getAsDouble();
+
+// extracting boolean values
+Boolean running = event.getFieldBySelector(runningSelector).getAsPrimitive().getAsBoolean();
+```
+
+In rare cases, you might want to receive a field directly based on the runtime name as follows:
+
+```java
+Double temperature = event.getFieldByRuntimeName("temperature").getAsPrimitive().getAsDouble();
+```
+
+#### List Fields
+
+Lists can also be retrieved by providing the corresponding selector and can automatically be parsed to a list of primitive datatypes:
+
+```java
+
+List<Integer> lastValues = event.getFieldBySelector(lastValueSelector).getAsList().parseAsSimpleType(Integer.class);
+
+```
+
+(coming soon: parsing complex lists)
+
+
+### Adding/Updating Fields
+
+Primitive fields can easily be added to an event by providing the runtime name and the object:
+
+```java
+
+ // add a primitive field with runtime name "city" and value "Karlsruhe"
+ event.addField("city", "Karlsruhe");
+
+ // remove the field "temperature" from the event
+ event.removeFieldBySelector(temperatureSelector);
+
+ // add a new field
+ event.addField("fahrenheit", 48);
+```
diff --git a/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-functions.md b/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-functions.md
new file mode 100644
index 000000000..659690b71
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-functions.md
@@ -0,0 +1,127 @@
+---
+id: extend-sdk-functions
+title: "SDK Guide: Functions"
+sidebar_label: "SDK: Functions"
+---
+
+## Introduction
+
+Pipeline elements such as data processors and data sinks are a great way
+to create _reusable_ components that can be part of pipelines.
+However, creating a pipeline element is not always the best choice:
+
+* The behaviour of a data processor is bound to a specific input stream _and_
+* A data processor doesn't contain any user-defined configuration _and_
+* The intended action is fixed or known at build time and the data processor shouldn't be available in the pipeline editor.
+
+To cover such use cases, we provide _StreamPipes Functions_. Functions
+are a great way to define custom processing logic based on previously
+connected data streams.
+
+Functions can be registered in a similar way to pipeline elements, but define expected input
+streams at startup time. Functions are started once the corresponding _extensions service_ starts
+and run until the service is stopped.
+
+## Writing a function
+
+:::caution Work in Progress
+
+Functions are currently in preview mode and are not yet recommended for production usage.
+APIs are subject to change in a future version.
+
+:::
+
+
+To define a function, create a new extensions service using the [Maven Archetypes](06_extend-archetypes.md) or use an already existing service.
+
+### Skeleton
+
+Functions can be defined by creating a new class which extends the ``StreamPipesFunction`` class.
+
+The basic skeleton looks like this:
+
+```java
+public class StreamPipesFunctionExample extends StreamPipesFunction {
+
+ @Override
+ public FunctionId getFunctionId() {
+ return FunctionId.from("my-function-id", 1);
+ }
+
+ @Override
+ public List<String> requiredStreamIds() {
+ return List.of("<id of the required stream>");
+ }
+
+ @Override
+ public void onServiceStarted(FunctionContext context) {
+ // called when the service is started
+ }
+
+ @Override
+ public void onEvent(Event event, String streamId) {
+ // called when an event arrives
+ }
+
+ @Override
+ public void onServiceStopped() {
+ // called when the service is stopped
+ }
+}
+
+```
+
+The structure of a function class is easy to understand:
+* _getFunctionId_ requires an identifier in form of a ``FunctionId``, which defines the id itself along with a version number that can be freely chosen.
+* _requiredStreamIds_ expects a list of references to data streams that are already available in StreamPipes. See below to learn how to find the id of a stream in StreamPipes.
+* _onServiceStarted_ is called once the extensions service is started and can be used to initialize the function.
+* _onEvent_ is called every time a new event arrives and provides a ``streamId`` as a reference to the corresponding stream, which is useful in case multiple data streams are received by the function.
+* _onServiceStopped_ is called when the extensions service is stopped and can be used to perform any required cleanup.
+
+### Getting a stream ID
+
+Functions require a reference to all data streams that should be retrieved by the function.
+Currently, the only way to get the ID of a function is by navigating to the ``Asset Management`` view in the StreamPipes UI.
+Create a new asset, click on ``Edit Asset`` and open ``Add Link`` in the _Linked Resources_ panel.
+Choose ``Data Source`` as link type, select one of the available sources, copy the ``Resource ID`` and provide this ID in the ``requiredStreamIds`` method.
+
+### Function Context
+
+The ``onServiceStarted`` method provides a function context which provides several convenience methods to work with functions:
+
+* _getFunctionId_ returns the current function identifier
+* _getConfig_ returns a reference to configuration options of the extensions service
+* _getClient_ returns a reference to the StreamPipes client to interact with features from the REST API.
+* _getStreams_ returns the data model of all data streams defined in the ``requiredStreamIds`` method.
+* _getSchema_ returns the schema of a specific data stream by providing the ``streamId``
+
+
+## Registering a function
+
+Registering a function is easy and can be done in the _Init_ class of the service.
+E.g., considering a service definition as illustrated below, simply call ``registerFunction`` and
+provide an instance of your function.
+
+```java
+
+ @Override
+ public SpServiceDefinition provideServiceDefinition() {
+ return SpServiceDefinitionBuilder.create("my-service-id",
+ "StreamPipes Function Example",
+ "",
+ 8090)
+ .registerFunction(new MyExampleFunction())
+ .registerMessagingFormats(
+ new JsonDataFormatFactory())
+ .registerMessagingProtocols(
+ new SpNatsProtocolFactory())
+ .build();
+ }
+
+```
+
+## Metrics & Monitoring
+
+Similar to pipeline elements, function register at the StreamPipes core.
+Running functions can be seen in the pipeline view of the user interface under _Functions_, right below the list of available pipelines.
+Similar to pipelines, simple metrics, monitoring info and exceptions can be viewed in the _Details_ section of each function.
diff --git a/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-migration-sd.md b/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-migration-sd.md
new file mode 100644
index 000000000..1fd5200ad
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-migration-sd.md
@@ -0,0 +1,117 @@
+---
+id: extend-sdk-migration-service-discovery
+title: "Migration Guide: New Service Discovery in 0.69.0"
+sidebar_label: "Migration Guide: 0.69.0"
+---
+
+
+## Introduction
+As part of our roadmap towards a release 1.0, Apache StreamPipes 0.69.0 features a new service discovery approach along with performance improvements related to a new storage layer for pipeline element descriptions.
+
+The new service discovery approach is better suited for cloud-native scenarios, as the hostname of a pipeline element is now decoupled from its description. As such, StreamPipes now supports recovery of pipeline elements independent from their assigned host.
+In addition, the new approach simplifies development of StreamPipes, e.g., in cases where the core is running in Docker and pipeline elements are developed on a local machine. In this case, the IP of the host machine should now be auto-discovered so that provision of environement variables should now be obsolete in most cases.
+The second large improvement is related to the replacement of RDF4J as the storage engine with a NoSQL database. This leads to much faster load times (you will notice this especially at system startup).
+
+While we are heavily working towards a stable release 1.0, we decided to put our efforts into the remaining features required for 1.0 and do not provide an auto-migration related to some breaking changes.
+Therefore, we recommend to reinstall StreamPipes when updating to 0.69.0. We currently plan to have at most two more releases before releasing the first 1.x version of StreamPipes.
+
+## Installation
+* Before upgrading to 0.69.0, clean any existing installation (e.g., by running ``docker-compose down -v``) and make sure that no volumes of StreamPipes are left.
+* Upgrade to the latest installer version (can be found at [streampipes/installer](https://github.com/apache/streampipes/tree/dev/installer))
+* Upon restart, make sure that the setup dialog appears (make sure that the new StreamPipes logo appears) and re-initialize the system.
+
+## SDK changes
+
+0.69.0 comes with a new ``ServiceDefinitionBuilder`` for pipelines, which simplifies the definition of a pipeline element.
+
+The ServiceDefinitionBuilder requires an ID of your extensions service, an optional title and description and a default port.
+It is best to provide 8090 as the default port, so that this will be the standard port of all StreamPipes extensions services at deployment time in a containerized environment.
+The port port can always be overriden by providing an ``SP_PORT`` environment variable.
+
+### Init class
+
+Modify the Init class of your pipeline element service as follows:
+
+```java
+public class ExamplesInit extends StandaloneModelSubmitter {
+
+ public static void main(String[] args) {
+ new ExamplesInit().init();
+ }
+
+ @Override
+ public SpServiceDefinition provideServiceDefinition() {
+ return SpServiceDefinitionBuilder.create("org.apache.streampipes.processors.examples.jvm",
+ "StreamPipes Code Examples",
+ "",
+ 8090)
+ .registerMessagingProtocols(new SpKafkaProtocolFactory(), new SpJmsProtocolFactory())
+ .registerMessagingFormats(new JsonDataFormatFactory())
+ .registerPipelineElement(new MyPipelineElementController())
+ .registerAdapter(new MyAdapter())
+ .build();
+ }
+}
+```
+
+You can now easily define a StreamPipes extensions service that supports both custom adapters and pipeline elements by using the following Maven dependency:
+This is optional and no changes to your existing Maven dependencies (except the version, e.g., 0.69.0-SNAPSHOT) are required.
+
+```maven
+<dependency>
+ <groupId>org.apache.streampipes</groupId>
+ <artifactId>streampipes-container-extensions</artifactId>
+</dependency>
+```
+
+
+### Configs
+Prior to version 0.69.0, additionally configs had to be provided in a separate ``Config`` class. This is now obsolete - configs can be directly provided within the builder class as follows:
+
+```java
+
+ @Override
+ public SpServiceDefinition provideServiceDefinition() {
+ return SpServiceDefinitionBuilder.create("org.apache.streampipes.processors.examples.jvm",
+ "StreamPipes Code Examples",
+ "",
+ 8090)
+ .registerPipelineElement(new MyPipelineElement())
+ .registerAdapter(new MyAdapter())
+ .addConfig("key", 1)
+ .addConfig("my-string-config", "myvalue")
+ .build();
+ }
+```
+
+Configs can be easily accessed from the ``EventProcessorRuntimeContext`` (or ``EventSinkRuntimeContext``):
+
+```java
+@Override
+ public void onInvocation(Parameters params,
+ SpOutputCollector spOutputCollector,
+ EventProcessorRuntimeContext context) {
+
+ Integer myConfigValue = context.getConfigStore().getConfig().getInteger("key");
+ }
+```
+
+
+### Service Discovery
+An extensions service can be started by executing the Init class.
+StreamPipes will now automatically select the proper service IP address and register the service at the backend.
+You can inspect the selected IP address in the console:
+
+```
+2024-05-16T11:03:37.158+02:00 INFO --- [ main] o.a.s.commons.networking.Networking : Using auto-discovered IP: 192.168.178.22
+2024-05-16T11:03:37.158+02:00 INFO --- [ main] o.a.s.commons.networking.Networking : Using port from provided environment variable SP_PORT: 7023
+2024-05-16T11:03:37.372+02:00 INFO --- [ main] a.s.s.e.StreamPipesExtensionsServiceBase : Registering service org.apache.streampipes.extensions.all.jvm with id org.apache.streampipes.extensions.all.jvm-FUt84Y at core
+2024-05-16T11:03:37.814+02:00 INFO --- [ main] o.a.s.s.extensions.CoreRequestSubmitter : Successfully registered service at core.
+2024-05-16T11:03:37.814+02:00 INFO --- [ main] a.s.s.e.StreamPipesExtensionsServiceBase : Registering 1 service configs for service org.apache.streampipes.extensions.all.jvm
+```
+
+In some (rare) cases, a non-resolvable IP will be selected. In this case, you can manually override the IP by providing a ``SP_HOST`` environment variable. This falls back to a similar behaviour as in pre-0.69.0-versions and will use the manually provided IP.
+
+
+
+
diff --git a/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-migrations.md b/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-migrations.md
new file mode 100644
index 000000000..bf822c1b8
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-migrations.md
@@ -0,0 +1,179 @@
+---
+id: extend-sdk-migration
+title: "SDK Guide: Pipeline Element Migration"
+sidebar_label: "SDK: PE Migration"
+---
+
+Pipeline element migrations allow you to automatically update and migrate both existing and pipeline elements when a new
+version of StreamPipes is installed. This means that whenever you upgrade StreamPipes, all existing and future
+pipeline elements will be directly compatible with the new version without any manual interaction. Pipeline elements
+include adapters, data processors, and data sinks.
+
+:::info
+Migrations will make their debut in StreamPipes version `0.93.0` and will be an integral part of the system going
+forward.
+However, it's important to note that this feature is not available in any of the previous versions of StreamPipes. To
+take full advantage of migrations and their benefits, it is recommended to upgrade to version `0.93.0` or later. This
+will
+ensure that you have access to the latest enhancements and maintain compatibility with the evolving StreamPipes
+platform.
+:::
+
+## Define Migrations
+
+Whenever a pipeline element, be it an adapter, data processor, or data sink, undergoes changes that result in
+modifications to its configuration options, developers must additionally create a migration procedure. This migration
+process should be capable of smoothly transitioning all affected instances from the previous version to the new one.
+The migration itself is automatically managed and executed by StreamPipes. Developers are only responsible for two key
+aspects:
+
+* **Implementing the concrete migration**: Developers need to craft the specific migration logic that facilitates the
+ seamless transition of configuration options.
+* **Registering the migration**: Developers should register their migration procedures at the extensions service,
+ allowing StreamPipes to identify and apply the necessary updates to affected instances.
+
+By adhering to these two essential tasks, developers can ensure a hassle-free evolution of pipeline elements while
+StreamPipes handles the orchestration of the migration process.
+
+The following gives a concrete example of creating a migration for
+the [S7 adapter](./pe/org.apache.streampipes.connect.iiot.adapters.plc4x.s7.md).
+Thereby, we assume this adapter has received a new input element which determines whether the connection should be made
+authenticated or not.
+This is represented by a simple boolean that is visualized as a toggle button in the UI.
+
+### Implementing a Concrete Migration
+
+StreamPipes offers three distinct migration mechanisms tailored to specific types of pipeline
+elements: `IAdapterMigrator`, `IDataProcessorMigrator`, and `IDataSinkMigrator`.
+These migration mechanisms are presented as interfaces and require the implementation of two fundamental methods:
+
+* `config()`: This method defines the configuration for the migration, encompassing all essential metadata related to
+ the migration process.
+* `migrate()`: Within this method, the actual migration logic is to be implemented. It serves as the operational core
+ for facilitating the migration for the respective pipeline element.
+
+In accordance with the example described above, we will implement the `Plc4xS7AdapterMigrationV1` in the following.
+
+:::note
+Before we begin, it's important to familiarize ourselves with two key conventions that guide our approach to migrations:
+
+* To maintain clarity and organization, all migration classes associated with a specific pipeline element are located
+ within a dedicated sub-package named `migration`. This sub-package is nested within the package of the respective
+ pipeline element.
+* Migration classes are named according to a specific schema: `<elementClassName>MigrationV<targetVersion>`. For
+ example, if you are working on a migration for the PLC4x S7 adapter targeting version 1, the migration class would be
+ named `Plc4xS7AdapterMigrationV1`.
+:::
+
+Let's begin with providing the migration's configuration:
+
+```java
+@Override
+public ModelMigratorConfig config() {
+ return new ModelMigratorConfig(
+ "org.apache.streampipes.connect.iiot.adapters.plc4x.s7",
+ SpServiceTagPrefix.ADAPTER,
+ 0,
+ 1
+ );
+}
+```
+
+The migration config consists of the following four parts:
+
+* `targetAppId`: this needs to equal the app id of the targeted element
+* `modelType`: the type of the element to be migrated, this can be one
+ of: `SpServiceTagPrefix.ADAPTER`, `SpServiceTagPrefix.DATA_PROCESSOR`, `SpServiceTagPrefix.DATA_SINK`.
+* `fromVersion`: the version of the element that the migration expects as input
+* `toVersion`: the version the element has after the migration (needs to be at least `fromVersion + 1`)
+
+The second step is to implement the actual migration logic.
+In our example, we need to extend the existing static properties by an additional boolean property.
+
+```java
+@Override
+public MigrationResult<AdapterDescription> migrate(AdapterDescription element, IStaticPropertyExtractor extractor) throws RuntimeException {
+
+ var config = element.getConfig();
+
+ var slideToggle = new SlideToggleStaticProperty();
+ slideToggle.setDefaultValue(false);
+ slideToggle.setLabel("Authentication required?");
+ config.add(slideToggle);
+
+ element.setConfig(config);
+ return MigrationResult.success(element);
+}
+```
+
+We've completed all the necessary steps for our migration. The final task remaining is to register the migration within
+the service definition.
+
+### Registering the Migration
+
+Only when the migration is registered at the service definition, the migration is sent to the StreamPipes core service.
+Therefore, we need to add the migration to the same service definition as the element to migrate.
+In our example this is defined in `ConnectAdapterIiotInit`:
+
+```java jsx {22-24} showLineNumbers
+@Override
+public SpServiceDefinition provideServiceDefinition() {
+ return SpServiceDefinitionBuilder.create("connect-adapter-iiot",
+ "StreamPipes connect worker containing adapters relevant for the IIoT",
+ "",
+ 8001)
+ .registerAdapter(new MachineDataSimulatorAdapter())
+ .registerAdapter(new FileReplayAdapter())
+ .registerAdapter(new IfmAlMqttAdapter())
+ .registerAdapter(new RosBridgeAdapter())
+ .registerAdapter(new OpcUaAdapter())
+ .registerAdapter(new Plc4xS7Adapter())
+ .registerAdapter(new Plc4xModbusAdapter())
+ .registerAdapter(new KafkaProtocol())
+ .registerAdapter(new MqttProtocol())
+ .registerAdapter(new NatsProtocol())
+ .registerAdapter(new HttpStreamProtocol())
+ .registerAdapter(new PulsarProtocol())
+ .registerAdapter(new RocketMQProtocol())
+ .registerAdapter(new HttpServerProtocol())
+ .registerAdapter(new TubeMQProtocol())
+ .registerMigrators(
+ new Plc4xS7AdapterMigrationV1()
+ )
+ .build();
+```
+
+<br />
+
+## How Migrations are Handled Internally
+
+Migrations are handled by an interplay between the Extension Service, which provides the migrations,
+and the StreamPipes Core Service, which manages the migrations, as shown in the figure below:
+<img src="/img/06_sdk_migrations/migration-flow.png" alt="Interplay of extensions service and core to handle migrations"/>
+
+When an extensions service is initiated and has successfully registered itself with the core, it proceeds to send a
+request to the core. This request includes a comprehensive list of all available migrations that have been registered
+for it. Since this collection of migrations may encompass multiple migrations that affect the same pipeline element,
+the migrations are first de-duplicated and then sorted based on their version range before being transmitted.
+
+Upon receiving these migrations, the core's actions can be categorized into two distinct parts:
+
+* Update descriptions for new elements
+* Update descriptions for existing elements
+
+### Update Descriptions for New Elements
+
+Each migration transmitted from the extensions service to the core triggers the core to update the description of the
+corresponding element stored in CouchDB. This is achieved by requesting the current configuration from the extensions
+service and subsequently overwriting the existing configuration in the storage.
+
+### Update Descriptions for Existing Elements
+
+For each migration sent from the extensions service to the core, the core conducts a thorough check to determine if any
+existing elements are affected by this migration. If such elements are identified, the extensions service is tasked with
+requesting and subsequently executing the migration on behalf of the core.
+
+In scenarios where multiple applicable migrations exist for a single pipeline element, they are sequentially applied.
+Success in this process allows the core to seamlessly update the configuration. However, if any issues arise, the
+corresponding pipeline element is halted. In the case of processors and sinks, the associated pipeline is even marked
+with a `needs attention` label, which comes apparent in the UI.
diff --git a/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-output-strategies.md b/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-output-strategies.md
new file mode 100644
index 000000000..feb224856
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-output-strategies.md
@@ -0,0 +1,348 @@
+---
+id: extend-sdk-output-strategies
+title: "SDK Guide: Output Strategies"
+sidebar_label: "SDK: Output Strategies"
+---
+
+## Introduction
+In StreamPipes, output strategies determine the output of a data processor.
+As the exact input schema of a processor is usually not yet known at development time (as processors can be connected with any stream that matches their requirements), output strategies are a concept to define how an input data stream is transformed to an output data stream.
+
+The following reference describes how output strategies can be defined using the SDK.
+
+:::tip Code on Github
+
+For all examples, the code can be found on [Github](https://www.github.com/apache/streampipes-examples/tree/dev/streampipes-pipeline-elements-examples-processors-jvm/src/main/java/org/apache/streampipes/pe/examples/jvm/outputstrategy/)
+
+:::
+
+
+## Reference
+
+The methods described below to create static properties are available in the ``ProcessingElementBuilder`` class and are usually used in the ``declareModel`` method of the controller class.
+
+As follows, we will use the following example event to explain how output strategies define the output of a data processor:
+
+```json
+{
+ "timestamp" : 1234556,
+ "temperature" : 37.0,
+ "deviceId" : "1"
+
+}
+```
+
+### Keep Output
+
+A ``KeepOutputStrategy`` declares that the output event schema will be equal to the input event schema.
+In other terms, the processor does not change the schema, but might change the values of event properties.
+
+A keep output strategy can be defined as follows:
+
+```java
+
+@Override
+ public DataProcessorDescription declareModel() {
+ return ProcessingElementBuilder.create("org.streampipes.examples.outputstrategy" +
+ ".keep", "Keep output example example", "")
+ .requiredStream(StreamRequirementsBuilder.
+ create()
+ .requiredProperty(EpRequirements.anyProperty())
+ .build())
+ .supportedProtocols(SupportedProtocols.kafka())
+ .supportedFormats(SupportedFormats.jsonFormat())
+
+ // declaring a keep output strategy
+ .outputStrategy(OutputStrategies.keep())
+
+ .build();
+ }
+
+```
+
+According to the example above, the expected output event schema of the example input event would be:
+
+```json
+{
+ "timestamp" : 1234556,
+ "temperature" : 37.0,
+ "deviceId" : "1"
+
+}
+```
+
+Data processors that perform filter operations (e.g., filtering temperature values that are above a given threshold) are a common example for using keep output strategies.
+
+
+### Fixed Output
+
+A ``FixedOutputStrategy`` declares that the data processor itself provides the event schema. The output schema does not depend on the input event.
+
+Fixed output strategies need to provide the event schema they produce at development time:
+
+```java
+
+ @Override
+ public DataProcessorDescription declareModel() {
+ return ProcessingElementBuilder.create("org.streampipes.examples.outputstrategy" +
+ ".fixed", "Fixed output example", "")
+ .requiredStream(StreamRequirementsBuilder.
+ create()
+ .requiredProperty(EpRequirements.anyProperty())
+ .build())
+ .supportedProtocols(SupportedProtocols.kafka())
+ .supportedFormats(SupportedFormats.jsonFormat())
+
+ // the fixed output strategy provides the schema
+ .outputStrategy(OutputStrategies.fixed(EpProperties.timestampProperty("timestamp"),
+ EpProperties.doubleEp(Labels.from("avg", "Average value", ""), "avg", SO.Number)))
+
+ .build();
+ }
+
+```
+
+In this example, we declare that the output schema always consists of two fields (``timestamp`` and ``avg``).
+
+Therefore, an output event should look like:
+
+```json
+{
+ "timestamp" : 1234556,
+ "avg" : 36.0
+}
+```
+
+
+### Append Output
+
+An ``AppendOutputStrategy`` appends additional fields to a schema of an incoming event stream. For instance, data processors that perform enrichment operations usually make use of append output strategies.
+
+Similar to the fixed output strategy, the additional fields must be provided at development time in the controller method as follows:
+
+```java
+ @Override
+ public DataProcessorDescription declareModel() {
+ return ProcessingElementBuilder.create("org.streampipes.examples.outputstrategy" +
+ ".append", "Append output example", "")
+
+ // boilerplate code not relevant here, see above
+
+ // declaring an append output
+ .outputStrategy(OutputStrategies.append(EpProperties.integerEp(Labels.from("avg",
+ "The average value", ""), "avg", SO.Number)))
+
+ .build();
+ }
+```
+
+In this case, the output event would have an additional field ``avg``:
+
+```json
+{
+ "timestamp" : 1234556,
+ "temperature" : 37.0,
+ "deviceId" : "1",
+ "avg" : 123.0
+
+}
+```
+
+### Custom Output
+
+In some cases, pipeline developers using the StreamPipes UI should be able to manually select fields from an input event schema. For such use cases, a ``CustomOutputStrategy`` can be used:
+
+```java
+
+@Override
+ public DataProcessorDescription declareModel() {
+ return ProcessingElementBuilder.create("org.streampipes.examples.outputstrategy" +
+ ".custom", "Custom output example", "")
+
+ // boilerplate code not relevant here, see above
+
+ // declaring a custom output
+ .outputStrategy(OutputStrategies.custom())
+
+ .build();
+ }
+
+```
+
+If a data processor defines a custom output strategy, the customization dialog in the pipeline editor will show a dialog to let users select the fields to keep:
+
+<img src="/img/dev-guide-output-strategies/os-custom.png" width="80%" alt="Number Parameter"/>
+
+Taking our example, and assuming that the user selects both the ``timestamp`` and the ``temperature`` the expected output event should look like this:
+
+```json
+{
+ "timestamp" : 1234556,
+ "temperature" : 37.0
+}
+```
+
+How do we know which fields were selected once the data processor is invoked? Use the proper method from the extractor in the ``onInvocation`` method:
+
+```java
+@Override
+ public ConfiguredEventProcessor<DummyParameters> onInvocation(DataProcessorInvocation graph, ProcessingElementParameterExtractor extractor) {
+
+ List<String> outputSelectors = extractor.outputKeySelectors();
+
+ return new ConfiguredEventProcessor<>(new DummyParameters(graph), DummyEngine::new);
+ }
+```
+
+### Transform Output
+
+A ``TransformOutputStrategy`` declares that one or more fields of an incoming event stream are transformed. Transformations can be applied to the datatype of the property, the runtime name of the property, or any other scheam-related declaration such as measurement units.
+
+#### Static Transform Operations
+
+Static transform operations do not depend on any user input (at pipeline development time) in order to know how to transform a field of an incoming event schema.
+
+Let's say our data processor transforms strings (that are actually a number) to a number datatype. In this case, we can use a static transform output strategy:
+
+```java
+
+ @Override
+ public DataProcessorDescription declareModel() {
+ return ProcessingElementBuilder.create("org.streampipes.examples.outputstrategy" +
+ ".transform", "Transform output example example", "")
+ .requiredStream(StreamRequirementsBuilder.
+ create()
+ .requiredPropertyWithUnaryMapping(EpRequirements.stringReq(), Labels.from
+ ("str", "The date property as a string", ""), PropertyScope.NONE)
+ .build())
+ .supportedProtocols(SupportedProtocols.kafka())
+ .supportedFormats(SupportedFormats.jsonFormat())
+
+ // static transform operation
+ .outputStrategy(OutputStrategies.transform(TransformOperations
+ .staticDatatypeTransformation("str", Datatypes.Long)))
+
+ .build();
+ }
+
+```
+
+Note the mapping property that we use to determine which field of the input event should be transformed.
+
+The expected output event would look like this:
+
+```json
+{
+ "timestamp" : 1234556,
+ "temperature" : 37.0,
+ "deviceId" : 1
+}
+```
+
+#### Dynamic Transform Operations
+
+Sometimes, user input depends on the exact transform output. Let's take a field renaming processor as an example, which lets the user rename a field from an input event schema to another field name.
+For such use cases, we can use a ``DynamicTransformOperation``:
+
+```java
+
+ @Override
+ public DataProcessorDescription declareModel() {
+ return ProcessingElementBuilder.create("org.streampipes.examples.outputstrategy" +
+ ".transform", "Transform output example example", "")
+ .requiredStream(StreamRequirementsBuilder.
+ create()
+ .requiredPropertyWithUnaryMapping(EpRequirements.stringReq(), Labels.from
+ ("str", "The date property as a string", ""), PropertyScope.NONE)
+ .build())
+ .supportedProtocols(SupportedProtocols.kafka())
+ .supportedFormats(SupportedFormats.jsonFormat())
+
+ // the text input to enter the new runtime name
+ .requiredTextparameter(Labels.from("new-runtime-name", "New Runtime Name", ""))
+
+ // static transform operation
+ .outputStrategy(OutputStrategies.transform(TransformOperations
+ .dynamicRuntimeNameTransformation("str", "new-runtime-name")))
+
+ .build();
+ }
+
+```
+
+For dynamic transform operations, an additional identifier that links to another static property can be assigned and later be fetched in the ``onInvocation`` method.
+
+Assuming we want to rename the field ``temperature`` to ``temp``, the resulting output event should look like this:
+
+```json
+{
+ "timestamp" : 1234556,
+ "temp" : 37.0,
+ "deviceId" : 1
+}
+```
+
+### Custom Transform Output
+
+Finally, in some cases the output schema cannot be described at pipeline development time. For these (usually rare) cases, a ``CustomTransformOutput`` strategy can be used.
+
+In this case, a callback function will be invoked in the controller class just after a user has filled in any static properties and clicks on ``Save`` in the pipeline editor.
+
+To define a custom transform output, we need to implement an interface in the controller class:
+
+```java
+public class CustomTransformOutputController extends
+ StandaloneEventProcessingDeclarer<DummyParameters> implements
+ ResolvesContainerProvidedOutputStrategy<DataProcessorInvocation, ProcessingElementParameterExtractor> {
+
+
+@Override
+ public EventSchema resolveOutputStrategy(DataProcessorInvocation processingElement, ProcessingElementParameterExtractor parameterExtractor) throws SpRuntimeException {
+
+ }
+}
+```
+
+In addition, the output strategy must be declared in the ``declareModel`` method:
+
+```java
+
+@Override
+ public DataProcessorDescription declareModel() {
+ return ProcessingElementBuilder.create("org.streampipes.examples.outputstrategy" +
+ ".customtransform", "Custom transform output example example", "")
+ .requiredStream(StreamRequirementsBuilder.
+ create()
+ .requiredPropertyWithUnaryMapping(EpRequirements.stringReq(), Labels.from
+ ("str", "The date property as a string", ""), PropertyScope.NONE)
+ .build())
+ .supportedProtocols(SupportedProtocols.kafka())
+ .supportedFormats(SupportedFormats.jsonFormat())
+
+ // declare a custom transform output
+ .outputStrategy(OutputStrategies.customTransformation())
+
+ .build();
+ }
+
+```
+
+Once a new pipeline using this data processor is created and the configuration is saved, the ``resolveOutputStrategy`` method will be called, so that an event schema can be provided based on the given configuration. An extractor instance (see the guide on static properties) is available to extract the selected static properties and the connected event stream.
+
+```java
+@Override
+ public EventSchema resolveOutputStrategy(DataProcessorInvocation processingElement, ProcessingElementParameterExtractor parameterExtractor) throws SpRuntimeException {
+ return new EventSchema(Arrays
+ .asList(EpProperties
+ .stringEp(Labels.from("runtime", "I was added at runtime", ""), "runtime", SO.Text)));
+ }
+```
+
+In this example, the output event schema should look like this:
+
+```json
+{
+ "runtime" : "Hello world!"
+}
+```
+
diff --git a/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-static-properties.md b/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-static-properties.md
new file mode 100644
index 000000000..39c2d5d6c
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-static-properties.md
@@ -0,0 +1,267 @@
+---
+id: extend-sdk-static-properties
+title: "SDK Guide: Static Properties"
+sidebar_label: "SDK: Static Properties"
+---
+
+## Introduction
+Static properties represent user-faced parameters that are provided by pipeline developers.
+Processing elements can specify required static properties, which will render different UI views in the pipeline editor.
+
+The following reference describes how static properties can be defined using the SDK.
+
+:::tip Code on Github
+
+For all examples, the code can be found on [Github](https://github.com/apache/streampipes-examples/tree/dev/streampipes-pipeline-elements-examples-processors-jvm/src/main/java/org/apache/streampipes/pe/examples/jvm/staticproperty).
+
+:::
+
+## Reference
+
+The methods described below to create static properties are available in the ``ProcessingElementBuilder`` and ``DataSinkBuilder`` classes and are usually used in the ``declareModel`` method of the controller class.
+
+### Mapping property
+
+In StreamPipes, processing elements usually operate on fields of an event stream. For instance, a filter processor operates on a specific field from an input stream (e.g., a field measuring the temperature).
+Typically, pipeline developers should select the exact field where the operations is applied upon by themselves.
+As this field is not yet known at pipeline element development time (as it is defined by the pipeline developer in the pipeline editor), mapping properties serve to map a stream requirement to a specific field from the actual input event stream.
+
+### Unary mapping property
+
+A unary mapping property maps a stream requirement to an actual field of an event stream. Therefore, the ``StreamRequirementsBuilder`` provides the opportunity to directly add a mapping property based along with a property requirement:
+
+```java
+.requiredStream(StreamRequirementsBuilder.
+ create()
+ .requiredPropertyWithUnaryMapping(EpRequirements.numberReq(),
+ Labels.from("mp-key", "My Mapping", ""),
+ PropertyScope.NONE)
+ .build())
+```
+
+This leads to a selection dialog in the pipeline element customization which provides the user with a selection of all event properties (fields) from the input stream that match the specified property requirement:
+
+<img src="/img/dev-guide-static-properties/sp-mapping-unary.png" width="80%" alt="Text"/>
+
+At invocation time, the value can be extracted in the ``onInvocation`` method as follows:
+
+```java
+// Extract the mapping property value
+String mappingPropertySelector = extractor.mappingPropertyValue("mp-key");
+```
+
+Note that this method returns a ``PropertySelector``, which can be used by the event model to extract the actual value of this field.
+
+### N-ary mapping property
+
+N-ary mapping properties work similar to unary mapping properties, but allow the mapping of one requirement to multiple event properties matching the requirement:
+
+```java
+.requiredStream(StreamRequirementsBuilder.
+ create()
+ .requiredPropertyWithNaryMapping(EpRequirements.numberReq(),
+ Labels.from("mp-key", "My Mapping", ""),
+ PropertyScope.NONE)
+ .build())
+```
+
+This renders the following selection, where users can select more than one matching event property:
+
+<img src="/img/dev-guide-static-properties/sp-mapping-nary.png" width="80%" alt="Text"/>
+
+The following snippet returns a list containing the property selectors of all event properties that have been selected:
+
+```java
+// Extract the mapping property value
+List<String> mappingPropertySelectors = extractor.mappingPropertyValues("mp-key");
+```
+
+### Free-Text Parameters
+
+A free-text parameter requires the pipeline developer to enter a single value - which can be a string or another primitive data type.
+The input of free-text parameters can be restricted to specific value ranges or can be linked to the value set of a connected input data stream.
+
+#### Text Parameters
+
+A text parameter lets the user enter a string value. The following code line in the controller class
+
+```java
+.requiredTextParameter(Labels.from(SP_KEY, "Example Name", "Example Description"))
+```
+
+leads to the following input dialog in the pipeline editor:
+
+<img src="/img/dev-guide-static-properties/sp-text-parameter.png" width="80%" alt="Text"/>
+
+Users can enter any value that will be converted to a string datatype. To receive the entered value in the ``onInvocation`` method, use the following method from the ``ParameterExtractor``
+
+```java
+String textParameter = extractor.singleValueParameter(SP_KEY, String.class);
+```
+
+#### Number parameters
+
+A number parameter lets the user enter a number value, either a floating-point number or an integer:
+
+```java
+// create an integer parameter
+.requiredIntegerParameter(Labels.from(SP_KEY, "Integer Parameter", "Example Description"))
+
+// create a float parameter
+.requiredFloatParameter(Labels.from("float-key", "Float Parameter", "Example Description"))
+
+```
+
+leads to the following input dialog in the pipeline editor only accepting integer values:
+
+<img src="/img/dev-guide-static-properties/sp-number-parameter.png" width="80%" alt="Number Parameter"/>
+
+The pipeline editor performs type validation and ensures that only numbers can be added by the user. To receive the entered value in the ``onInvocation`` method, use the following method from the ``ParameterExtractor``
+
+```java
+// Extract the integer parameter value
+Integer integerParameter = extractor.singleValueParameter(SP_KEY, Integer.class);
+
+// Extract the float parameter value
+Float floatParameter = extractor.singleValueParameter("float-key", Float.class);
+
+```
+
+#### Numbers with value specification
+
+You can also specify the value range of a number-based free text parameter:
+
+```java
+// create an integer parameter with value range
+.requiredIntegerParameter(Labels.from(SP_KEY, "Integer Parameter", "Example Description"), 0, 100, 1)
+
+```
+
+which renders the following input field:
+
+<img src="/img/dev-guide-static-properties/sp-number-parameter-with-range.png" width="80%" alt="Number Parameter"/>
+
+Receive the entered value in the same way as a standard number parameter.
+
+#### Free-text parameters linked to an event property
+
+
+### Single-Value Selections
+
+Single-value selections let the user select from a pre-defined list of options.
+A single-value selection requires to select exactly one option.
+
+```java
+.requiredSingleValueSelection(Labels.from("id", "Example Name", "Example Description"),
+ Options.from("Option A", "Option B", "Option C"))
+
+```
+
+Single-value selections will be rendered as a set of radio buttons in the pipeline editor:
+
+<img src="/img/dev-guide-static-properties/sp-single-selection.png" width="80%" alt="Number Parameter"/>
+
+To extract the selected value, use the following method from the parameter extractor:
+
+```java
+// Extract the selected value
+String selectedSingleValue = extractor.selectedSingleValue("id", String.class);
+```
+
+:::tip Declaring options
+
+Sometimes, you may want to use an internal name that differs from the display name of an option.
+For that, you can use the method Options.from(Tuple2{'<'}String, String{'>'}) and the extractor method selectedSingleValueInternalName.
+
+:::tip
+
+
+### Multi-Value Selections
+
+Multi-value selections let the user select from a pre-defined list of options, where multiple or no option might be selected.
+
+```java
+.requiredMultiValueSelection(Labels.from("id", "Example Name", "Example Description"),
+ Options.from("Option A", "Option B", "Option C"))
+
+```
+
+Multi-value selections will be rendered as a set of checkboxes in the pipeline editor:
+
+<img src="/img/dev-guide-static-properties/sp-multi-selection.png" width="80%" alt="Number Parameter"/>
+
+To extract the selected value, use the following method from the parameter extractor:
+
+```java
+// Extract the selected value
+List<String> selectedMultiValue = extractor.selectedMultiValues("id", String.class);
+```
+
+### Domain Concepts
+
+(coming soon...)
+
+### Collections
+
+You can also define collections based on other static properties.
+
+```java
+// create a collection parameter
+.requiredParameterAsCollection(Labels.from("collection", "Example Name", "Example " +
+ "Description"), StaticProperties.stringFreeTextProperty(Labels
+ .from("text-property","Text","")))
+```
+
+While the items of the collection can be provided in the same way as the underlying static property, the UI provides buttons to add and remove items to the collections.
+
+<img src="/img/dev-guide-static-properties/sp-collection.png" width="80%" alt="Number Parameter"/>
+
+To extract the selected values from the collection, use the following method from the parameter extractor:
+
+```java
+// Extract the text parameter value
+List<String> textParameters = extractor.singleValueParameterFromCollection("collection", String.class);
+```
+
+### Runtime-resolvable selections
+
+In some cases, the options of selection parameters are not static, but depend on other values or might change at runtime. In this case, you can use runtime-resolvable selections.
+
+First, let your controller class implement ``ResolvesContainerProvidedOptions``:
+
+```java
+public class RuntimeResolvableSingleValue extends
+ StandaloneEventProcessingDeclarer<DummyParameters> implements ResolvesContainerProvidedOptions { ... }
+```
+
+Next, define the parameter in the ``declareModel`` method:
+
+```java
+// create a single value selection parameter that is resolved at runtime
+ .requiredSingleValueSelectionFromContainer(Labels.from("id", "Example Name", "Example " +
+ "Description"))
+```
+
+Finally, implement the method ``resolveOptions``, which will be called at runtime once the processor is used:
+
+```java
+ @Override
+ public List<RuntimeOptions> resolveOptions(String requestId, EventProperty linkedEventProperty) {
+ return Arrays.asList(new RuntimeOptions("I was defined at runtime", ""));
+ }
+```
+
+The UI will render a single-value parameter based on the options provided at runtime:
+
+<img src="/img/dev-guide-static-properties/sp-single-selection-remote.png" width="80%" alt="Number Parameter"/>
+
+The parameter extraction does not differ from the extraction of static single-value parameters.
+
+
+:::info Multi-value selections
+
+Although this example shows the usage of runtime-resolvable selections using single value selections, the same also works for multi-value selections!
+
+:::
+
+
diff --git a/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-stream-requirements.md b/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-stream-requirements.md
new file mode 100644
index 000000000..409c5164d
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/06_extend-sdk-stream-requirements.md
@@ -0,0 +1,181 @@
+---
+id: extend-sdk-stream-requirements
+title: "SDK Guide: Stream Requirements"
+sidebar_label: "SDK: Stream Requirements"
+---
+
+## Introduction
+
+Data processors and data sinks can define ``StreamRequirements``. Stream requirements allow pipeline elements to express requirements on an incoming event stream that are needed for the element to work properly.
+Once users create pipelines in the StreamPipes Pipeline Editor, these requirements are verified against the connected event stream.
+By using this feature, StreamPipes ensures that only pipeline elements can be connected that are syntactically and semantically valid.
+
+This guide covers the creation of stream requirements. Before reading this section, we recommend that you make yourself familiar with the SDK guide on [data processors](extend-first-processor).
+
+
+:::tip Code on Github
+
+For all examples, the code can be found on [Github](https://www.github.com/apache/streampipes-examples/tree/dev/streampipes-pipeline-elements-examples-processors-jvm/src/main/java/org/apache/streampipes/pe/examples/jvm/requirements/).
+
+:::
+
+
+## The StreamRequirementsBuilder
+
+Stream requirements can be defined in the ``declareModel`` method of the pipeline element class. Start with a method body like this:
+
+```java
+
+@Override
+ public DataProcessorDescription declareModel() {
+ return ProcessingElementBuilder.create(ID, PIPELINE_ELEMENT_NAME, DESCRIPTION)
+ .requiredStream(StreamRequirementsBuilder.
+ create()
+
+ .build())
+
+ .supportedProtocols(SupportedProtocols.kafka())
+ .supportedFormats(SupportedFormats.jsonFormat())
+ .outputStrategy(OutputStrategies.keep())
+
+ .build();
+ }
+```
+
+The ``StreamRequirementsBuilder`` class provides methods to add stream requirements to a pipeline element.
+
+## Requirements on primitive fields
+
+As a very first example, let's assume we would like to create a data processor that filters numerical values that are above a given threshold.
+Consequently, any data stream that is connected to the filter processor needs to provide a numerical value.
+
+The stream requirement would be assigned as follows:
+
+```java
+@Override
+ public DataProcessorDescription declareModel() {
+ return ProcessingElementBuilder.create(ID, PIPELINE_ELEMENT_NAME, DESCRIPTION)
+ .requiredStream(StreamRequirementsBuilder
+ .create()
+ .requiredProperty(EpRequirements.numberReq())
+ .build())
+
+ .supportedProtocols(SupportedProtocols.kafka())
+ .supportedFormats(SupportedFormats.jsonFormat())
+ .outputStrategy(OutputStrategies.keep())
+
+ .build();
+ }
+```
+
+Note the line starting with ``requiredProperty``, which requires any stream to provide a datatype of type ``number``.
+
+In many cases, you'll want to let the user select a specific field from a data stream from all available fields that match the specified requirement. For that, you simply use the method ``requiredPropertyWithUnaryMapping`` as follows:
+
+```java
+@Override
+ public DataProcessorDescription declareModel() {
+ return ProcessingElementBuilder.create(ID, PIPELINE_ELEMENT_NAME, DESCRIPTION)
+ .requiredStream(StreamRequirementsBuilder
+ .create()
+ .requiredPropertyWithUnaryMapping(EpRequirements.numberReq(),
+ Labels.from("number-mapping", "The value that should be filtered", ""), PropertyScope.NONE)
+ .build())
+
+ .supportedProtocols(SupportedProtocols.kafka())
+ .supportedFormats(SupportedFormats.jsonFormat())
+ .outputStrategy(OutputStrategies.keep())
+
+ .build();
+ }
+```
+
+See also the developer guide on [static properties](extend-sdk-static-properties) to better understand the usage of ``MappingProperties``.
+
+Requirements on primitive fields can be specified for all common datatypes:
+
+```java
+ @Override
+ public DataProcessorDescription declareModel() {
+ return ProcessingElementBuilder.create("org.streampipes.examples.requirements" +
+ ".simple", "Simple requirements specification examples", "")
+ .requiredStream(StreamRequirementsBuilder.
+ create()
+ .requiredProperty(EpRequirements.numberReq()) // any number
+ .requiredProperty(EpRequirements.doubleReq()) // any field of type double
+ .requiredProperty(EpRequirements.booleanReq()) // any field of type boolean
+ .requiredProperty(EpRequirements.integerReq()) // any field of type integer
+ .requiredProperty(EpRequirements.stringReq()) // any field of type string
+
+ .requiredProperty(EpRequirements.anyProperty()) // any field allowed (no restriction)
+ .requiredProperty(EpRequirements.timestampReq()) // any timestamp field
+ .build())
+
+
+ .supportedProtocols(SupportedProtocols.kafka())
+ .supportedFormats(SupportedFormats.jsonFormat())
+ .outputStrategy(OutputStrategies.keep())
+
+ .build();
+```
+
+### Specifying semantics
+
+For some algorithms, only specifying the datatype is not sufficient. Let's consider a geofencing algorithm that detects the precense some geospatial coordinate (e.g., from a vehicle) within a given location.
+
+You could specify something like this:
+
+```java
+ StreamRequirementsBuilder
+ .create()
+ .requiredPropertyWithUnaryMapping(EpRequirements.doubleEp(), Labels.from("mapping-latitude", "Latitude", ""), PropertyScope.NONE)
+ .requiredPropertyWithUnaryMapping(EpRequirements.doubleEp(), Labels.from("mapping-longitude", "Longitude", ""), PropertyScope.NONE)
+ .build()
+```
+
+However, this would allow users to create strange pipelines as users could connect any stream containing a double value to our geofencing algorithm.
+To avoid such situations, you can also specify requirements based on the semantics of a field:
+
+```java
+ StreamRequirementsBuilder
+ .create()
+ .requiredPropertyWithUnaryMapping(EpRequirements.domainPropertyReq(SO.Latitude), Labels.from("mapping-latitude", "Latitude", ""), PropertyScope.NONE)
+ .requiredPropertyWithUnaryMapping(EpRequirements.domainPropertyReq(SO.Longitude), Labels.from("mapping-longitude", "Longitude", ""), PropertyScope.NONE)
+ .build()
+```
+
+Note that in this case, we make use of Schema.org's ``Latitude`` concept ([https://schema.org/latitude](https://schema.org/latitude)). StreamPipes already includes popular vocabularies for specifying semantics. You are also free to use your own vocabularies.
+
+
+## Requirements on lists
+
+Similarly to primitive requirements, you can define processors that require data streams with list fields, see the following examples:
+
+```java
+@Override
+ public DataProcessorDescription declareModel() {
+ return ProcessingElementBuilder.create("org.streampipes.examples.requirements" +
+ ".list", "List requirements specification examples", "")
+ .requiredStream(StreamRequirementsBuilder.
+ create()
+ .requiredProperty(EpRequirements.listRequirement(Datatypes.Integer))
+ .requiredProperty(EpRequirements.listRequirement(Datatypes.Double))
+ .requiredProperty(EpRequirements.listRequirement(Datatypes.Boolean))
+ .requiredProperty(EpRequirements.listRequirement(Datatypes.String))
+ .build())
+
+
+ .supportedProtocols(SupportedProtocols.kafka())
+ .supportedFormats(SupportedFormats.jsonFormat())
+ .outputStrategy(OutputStrategies.keep())
+
+ .build();
+ }
+```
+
+## Requirements on nested properties
+
+(coming soon, see the Javadoc for now)
+
+
+
diff --git a/website-v2/versioned_docs/version-0.98.0/06_extend-setup.md b/website-v2/versioned_docs/version-0.98.0/06_extend-setup.md
new file mode 100644
index 000000000..12a96eb8e
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/06_extend-setup.md
@@ -0,0 +1,50 @@
+---
+id: extend-setup
+title: Development Setup
+sidebar_label: Development Setup
+---
+
+Pipeline elements in StreamPipes are provided as standalone microservices. New pipeline elements can be easily developed using the provided Maven archetypes and can be installed in StreamPipes at runtime.
+
+In this section, we describe our recommended minimum setup for locally setting up a development instance of StreamPipes needed to develop, run and test new pipeline elements.
+
+## IDE & required dev tools
+StreamPipes does not have specific requirements on the IDE - so feel free to choose the IDE of your choice.
+The only requirements in terms of development tools are that you have Java 17 and Maven installed.
+
+## StreamPipes CLI: Docker-based local StreamPipes instance
+In order to quickly test developed pipeline elements without needing to install all services required by StreamPipes, we provide a CLI tool that allows you to selectively start StreamPipes components.
+The CLI tool allows to switch to several templates (based on docker-compose) depending on the role.
+
+The documentation on the usage of the CLI tool is available [here](06_extend-cli.md).
+
+## Override the SP_HOST variable
+
+By default, the backend/core of StreamPipes registers itself within StreamPipes' service discovery mechanism using an auto-discovered hostname.
+Usually, this will be an IP address from the Docker network, which is not resolvable from outside. Therefore, for local development you need to override the hostname with an IP address which is accessible from your local host where you develop extensions.
+When using the CLI, open the CLI folder ``installer/cli``, navigate to ``deploy/standalone/backend``, open the ``docker-compose.dev.yml`` file and add the SP_HOST env variable, e.g.
+
+```
+version: "3.4"
+services:
+ backend:
+ ports:
+ - "8030:8030"
+ environment:
+ - SP_HOST=host.docker.internal
+```
+
+Note that host.docker.internal will work as an alias under Docker for Desktop on Windows and Mac, but not on Linux or M1. In this case, provide a resolvable hostname or IP address manually.
+
+## Starter projects
+
+Now, once you've started the development instance, you are ready to develop your very first pipeline element.
+Instead of starting from scratch, we recommend using our provided maven archetypes:
+
+### Maven archetypes
+
+Create the Maven archetype as described in the [Maven Archetypes](06_extend-archetypes.md) guide.
+
+### Examples
+
+We provide several examples that explain the usage of some concepts in this [Github repo](https://github.com/apache/streampipes-examples).
diff --git a/website-v2/versioned_docs/version-0.98.0/06_extend-tutorial-adapters.md b/website-v2/versioned_docs/version-0.98.0/06_extend-tutorial-adapters.md
new file mode 100644
index 000000000..4e95cba9a
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/06_extend-tutorial-adapters.md
@@ -0,0 +1,612 @@
+---
+id: extend-tutorial-adapters
+title: "Tutorial: Build Custom Adapters"
+sidebar_label: "Tutorial: Adapters"
+---
+
+In this tutorial, we will create a new data source consisting of a single data stream.
+By the end of the tutorial, you will be able to implement custom adapters that allow you to connect to data sources
+other than those officially supported by StreamPipes.
+To do this, we will split the tutorial into two parts.
+The [first part](#building-a-basic-adapter) focuses on creating the adapter and defining the event stream.
+At the end, we will have a working adapter that produces an event stream that can be used in StreamPipes.
+This adapter does not provide any way to configure its behavior, so in
+the [second part](#building-a-more-advanced-adapter-by-processing-ui-input) of the tutorial
+to show how we can extend our existing adapter to be configurable via the UI.
+
+:::info
+This tutorial shows how to build your own type of adapter.
+It is intended for people who are interested in extending StreamPipes to meet their own needs.
+If you are here to explore StreamPipes and are interested in using an adapter, you may want to
+continue [here](./03_use-connect.md).
+:::
+
+## Objective
+
+We are going to create an adapter that will simulate a stream of data generated by a control station in a logistics
+center that is used to sort packages.
+This station consists of two sensors: a light barrier that detects when a package passes through, and a weight sensor.
+
+This sensor produces a continuous stream of events containing the current time stamp, an indicator of whether a package
+is present or the conveyor is empty, and the weight of the package in kilograms.
+The events are published in JSON format as follows
+
+```json
+{
+ "timestamp": 1697720916959,
+ "parcelPresent": true,
+ "weight": 3.520
+}
+```
+
+In the following section, we will show you how to develop an adapter that is capable of generating this stream so that
+it is available for further processing in StreamPipes.
+
+## Project Set Up
+
+Instead of creating a new project from scratch, we recommend to use our Maven archetype to create a new project
+skeleton (`streampipes-archetype-extensions-jvm`).
+Enter the following command in a command line of your choice (please ensure
+that [Apache Maven](https://maven.apache.org/install.html) isinstalled):
+
+```bash
+mvn archetype:generate \
+-DarchetypeGroupId=org.apache.streampipes -DarchetypeArtifactId=streampipes-archetype-extensions-jvm \
+-DarchetypeVersion=0.93.0 -DgroupId=org.apache.streampipes \
+-DartifactId=streampipes-archetype-extensions-jvm -DclassNamePrefix=ParcelControlStation -DpackageName=parcelcontrol
+```
+
+This command will ask you for input twice, you can just skip both of them by hitting *enter*.
+The first dialog sets the version to use for our `streampipes-archetype-extensions-jvm` module.
+Feel free to change this if you like.
+
+```bash
+Define value for property 'version' 1.0-SNAPSHOT: :
+
+ Y: :
+```
+
+The `mvn archetype:generate` command generates some required files, the required file structure, and some boilerplate
+code.
+The generated file structure should look like the following:
+
+:::info
+Note that you can customize the parameters of the mvn command to affect the file structure and file naming.
+:::
+
+```bash
+
+|streampipes-archetype-extensions # name is determined by '-DartifactId'
+|-- development
+| |-- env
+|-- src
+| |-- main
+| | |-- java.org.apache.streampipes # name after .java. is determined by '-DgroupId'
+| | | |-- pe.parcelcontrol # name after .pe. is determined by '-DpackageName'
+| | | | |-- ParcelControlStationDataProcessor.java # class name is determined by '-DclassNamePrefix'
+| | | | |-- ParcelControlStationDataSink.java
+| | | | |-- ParcelControlStationGenericAdapter.java
+| | | | |-- ParcelControlStationSpecificAdapter.java
+| | | |-- Init.java
+| | |-- resources
+| | | |-- org.apache.streampipes.pe.parcelcontrol.genericadapter
+| | | | |-- documentation.md
+| | | | |-- icon.png
+| | | | |-- strings.en
+| | | |-- org.apache.streampipes.pe.parcelcontrol.processor
+| | | | |-- documentation.md
+| | | | |-- icon.png
+| | | | |-- strings.en
+| | | |-- org.apache.streampipes.pe.parcelcontrol.sink
+| | | | |-- documentation.md
+| | | | |-- icon.png
+| | | | |-- strings.en
+| | | |-- org.apache.streampipes.pe.parcelcontrol.specificadapter
+| | | | |-- documentation.md
+| | | | |-- icon.png
+| | | | |-- strings.en
+| |-- test.java.org.apache.streampipes # name after .java. is determined by '-DgroupId'
+| | |-- InitTest.java
+|-- Dockerfile
+|-- pom.xml
+
+```
+
+:::tip
+In addition to the basic project skeleton, the sample project also includes a sample `Dockerfile` that you can use to
+package your application into a Docker container.
+:::
+
+## Building a Basic Adapter
+
+In the following, we will demonstrate how to use the boilerplate code generated by the Maven plugin (
+see [Project setup](#project-setup)).
+Within this section, we will focus on creating an event stream that can be used within StreamPipes.
+The following section shows how to configure the created adapter with UI input.
+
+Attentive readers may have noticed that two adapter classes have been generated.
+We will focus on the `ParcelControlStationSpecificAdapter` first, the `ParcelControlStationSimulatorGenericAdapter` will
+be used later for more advanced adapter features.
+First, let us take a look at the `ParcelControlStationSpecificAdapter.java` file as generated by the Maven
+archetype.
+
+```java jsx showLineNumbers
+package org.apache.streampipes.pe.parcelcontrol;
+
+import org.apache.streampipes.commons.exceptions.connect.AdapterException;
+import org.apache.streampipes.extensions.api.connect.IAdapterConfiguration;
+import org.apache.streampipes.extensions.api.connect.IEventCollector;
+import org.apache.streampipes.extensions.api.connect.StreamPipesAdapter;
+import org.apache.streampipes.extensions.api.connect.context.IAdapterGuessSchemaContext;
+import org.apache.streampipes.extensions.api.connect.context.IAdapterRuntimeContext;
+import org.apache.streampipes.extensions.api.extractor.IAdapterParameterExtractor;
+import org.apache.streampipes.model.AdapterType;
+import org.apache.streampipes.model.connect.guess.GuessSchema;
+import org.apache.streampipes.sdk.builder.adapter.AdapterConfigurationBuilder;
+import org.apache.streampipes.sdk.builder.adapter.GuessSchemaBuilder;
+import org.apache.streampipes.sdk.helpers.Labels;
+import org.apache.streampipes.sdk.helpers.Locales;
+
+import java.util.HashMap;
+import java.util.Map;
+
+public class ParcelControlStationSpecificAdapter implements StreamPipesAdapter {
+
+ private boolean running = false;
+
+ @Override
+ public IAdapterConfiguration declareConfig() {
+ return AdapterConfigurationBuilder.create(
+ "org.apache.streampipes.pe.parcelcontrol.specificadapter",
+ ParcelControlStationSpecificAdapter::new
+ )
+ .withAssets(Assets.DOCUMENTATION, Assets.ICON)
+ .withCategory(AdapterType.Manufacturing)
+ .withLocales(Locales.EN)
+ .buildConfiguration();
+ }
+
+ @Override
+ public void onAdapterStarted(IAdapterParameterExtractor extractor,
+ IEventCollector collector,
+ IAdapterRuntimeContext adapterRuntimeContext) throws AdapterException {
+
+ Runnable demo = () -> {
+ while (running) {
+ // make event
+ Map<String, Object> event = new HashMap<>();
+ // forward the event to the adapter pipeline
+ collector.collect(event);
+ }
+ };
+ running = true;
+ new Thread(demo).start();
+ }
+
+ @Override
+ public void onAdapterStopped(IAdapterParameterExtractor extractor,
+ IAdapterRuntimeContext adapterRuntimeContext) throws AdapterException {
+
+ // do cleanup
+ running = false;
+ }
+
+ @Override
+ public GuessSchema onSchemaRequested(IAdapterParameterExtractor extractor,
+ IAdapterGuessSchemaContext adapterGuessSchemaContext) throws AdapterException {
+
+ // build the schema by adding properties to the schema builder and a preview if possible
+ return GuessSchemaBuilder
+ .create()
+ .build();
+ }
+ }
+
+```
+
+The class extends `StreamPipesAdapter`, which is the interface that all adapters within StreamPipes must implement.
+This interface requires us to implement four methods:
+
+* `declareConfig()`: This method is expected to return the configuration of the adapter. The configuration includes
+ metadata about the adapter and its input parameters.
+* `onAdapterStarted()`: This method is expected to contain the actual adapter logic. It is called when the adapter is
+ started, and is responsible for sending incoming data to StreamPipes as an event.
+* `onAdapterStopped()`: This method is called when the adapter is stopped and is responsible for gracefully exiting the
+ adapter.
+ gracefully and usually performs some cleanup tasks.
+* `onSchemaRequested()`: This method is expected to return the schema of the event stream. This is ideally done
+ dynamically based on some incoming data (*guess*) or provided statically if not otherwise possible.
+
+### Describing the Adapter via the Configuration
+
+The standard code generated here is already sufficient for us.
+So let's have a quick look at the important aspects:
+
+* `Line 4`: Here we define a unique identifier for our adapter. This allows us to identify all instances of the same
+ adapter. Including your own namespace is always a good choice to avoid conflicts.
+* `Line 7`: Here we define what assets are available for this adapter. In this case, we provide a documentation file and
+ an icon. Both assets are located in the `resource' directory (see file tree above).
+* `Line 8`: This defines a rough categorization along predefined adapter types.
+* `Line 9`: Here we define which locales are available for this adapter. Since we only provide one `strings.en' file so
+ far (see file tree above), the current selection is sufficient. Theoretically you can support multiple languages, but
+ this is not fully supported yet.
+
+```java jsx {4,7-9} showLineNumbers
+ @Override
+ public IAdapterConfiguration declareConfig() {
+ return AdapterConfigurationBuilder.create(
+ "org.apache.streampipes.pe.parcelcontrol.specificadapter",
+ ParcelControlStationSpecificAdapter::new
+ )
+ .withAssets(Assets.DOCUMENTATION, Assets.ICON)
+ .withCategory(AdapterType.Manufacturing)
+ .withLocales(Locales.EN)
+ .buildConfiguration();
+ }
+```
+
+Before we continue, let's quickly have a look at the `strings.en` file that defines our locales.
+Here we can define a meaningful and human-readable adapter tile in the first line and a short description:
+
+```text
+org.apache.streampipes.pe.parcelcontrol.specificadapter.title=Parcel Control Station (simple)
+org.apache.streampipes.pe.parcelcontrol.specificadapter.description=This adapter simulates data coming from a parcel control station in a logistics center.
+```
+
+Now we have successfully configured our adapter and prepared all descriptive elements, we can focus on the actual logic.
+
+### Creating the Data Stream
+
+The logic that creates events that are then populated via StreamPipes is defined in `onAdapterStarted()`.
+Within this method, connectors usually connect to the data source and extract data.
+In our case, however, we simply want to create some sample data directly.
+The two main parts that should always happen within this method are highlighted in the provided skeleton code:
+
+* `Line 10`: Creating an event is crucial for our adapters. This event is then filled with data by the adapter before it
+ is distributed.
+* `Line 13`: The event must finally be passed to the `collector`, which then takes the data and distributes it within
+ StreamPipes in the form of a [data stream](./02_concepts-overview.md#data-stream).
+
+```java jsx {10,13} showLineNumbers
+@Override
+public void onAdapterStarted(IAdapterParameterExtractor extractor,
+ IEventCollector collector,
+ IAdapterRuntimeContext adapterRuntimeContext) throws AdapterException {
+
+ Runnable demo = () -> {
+ while (running) {
+
+ // make event
+ Map<String, Object> event = new HashMap<>();
+
+ // forward the event to the adapter pipeline
+ collector.collect(event);
+ }
+ };
+ running = true;
+ new Thread(demo).start();
+}
+```
+
+So the only thing left to do is to create the actual events.
+In our scenario, we want to create two types of events: one describing an empty conveyor and one describing a detected
+and weighed package.
+To keep the implementation simple, we simply want to have a parcel event every five seconds. We can implement this as
+follows:
+
+```java
+ Runnable parcelControl = () -> {
+ while (running) {
+
+ // get the current time in seconds
+ long timestamp = System.currentTimeMillis();
+ long timeInSeconds = (int) timestamp / 1000;
+
+ // make event
+ Map<String, Object> event = new HashMap<>();
+ event.put("timestamp", timestamp);
+
+ if (timeInSeconds % 5 == 0) {
+ event.put("parcelPresent", true);
+ event.put("weight", ThreadLocalRandom.current().nextDouble(0, 10));
+
+ } else {
+ event.put("parcelPresent", false);
+ event.put("weight", 0);
+ }
+
+ // forward the event to the adapter pipeline
+ collector.collect(event);
+
+ try {
+ Thread.sleep(1000);
+ } catch (InterruptedException e) {
+ throw new RuntimeException(e);
+ }
+ }
+ };
+ running = true;
+ new Thread(parcelControl).start();
+```
+
+This is already enough to get a data stream into StreamPipes.
+As the next step we need to describe to event schema.
+
+### Defining the Event Schema
+
+In StreamPipes, each data stream comes with an event schema that describes what information the event contains,
+in what data formats, and some semantic type information.
+This allows StreamPipes to provide easy and convenient stream handling with a lot of automatic conversions and
+validations.
+For example, whether a particular data processor is suitable for a given event stream.
+This event schema is provided by `onSchemaRequested()`:
+
+```java
+@Override
+public GuessSchema onSchemaRequested(IAdapterParameterExtractor extractor,
+ IAdapterGuessSchemaContext adapterGuessSchemaContext) throws AdapterException {
+
+ // build the schema by adding properties to the schema builder and a preview if possible
+ return GuessSchemaBuilder
+ .create()
+ .build();
+ }
+
+```
+
+Normally, the event schema is determined automatically and dynamically, since an adapter is usually quite generic (read
+more in the [Advanced section](#advanced)).
+But in our case, we already know the event schema, and it never changes, so we can just define it:
+
+```java jsx {3,13-20} showLineNumbers
+@Override
+public GuessSchema onSchemaRequested(IAdapterParameterExtractor extractor,
+ IAdapterGuessSchemaContext adapterGuessSchemaContext) throws AdapterException {
+
+ // build the schema by adding properties to the schema builder and a preview if possible
+ return GuessSchemaBuilder.create()
+ .property(timestampProperty("timestamp"))
+ .sample("timestamp", System.currentTimeMillis())
+ .property(PrimitivePropertyBuilder
+ .create(Datatypes.Boolean, "parcelPresent")
+ .label("Parcel Present")
+ .description("Indicates if a parcel is weighed.")
+ .domainProperty(SO.BOOLEAN)
+ .scope(PropertyScope.MEASUREMENT_PROPERTY)
+ .build())
+ .sample("parcelPresent", true)
+ .property(PrimitivePropertyBuilder
+ .create(Datatypes.Double, "weight")
+ .label("Parcel Weight")
+ .description("Parcel weight")
+ .domainProperty(SO.WEIGHT)
+ .scope(PropertyScope.MEASUREMENT_PROPERTY)
+ .build())
+ .sample("weight", 3.520)
+ .build();
+```
+
+An attribute of an Event is referred to as `property` in StreamPipes.
+So in our case we have three properties.
+Since StreamPipes creates a sample event in the UI when configuring the adapter (
+see [here](./03_use-connect.md#schema-editor)),
+providing a meaningful sample value for every property allows StreamPipes to demonstrate its full potential.
+
+Since every event schema is required to have a timestamp property, we provide a convenience definition (see `line 3`).
+For all other properties the recommend way of definition is using the `PrimitivePropertyBuilder` (see `line 13-20`) and
+consists of the following steps:
+
+* `Line 14`: every property must have a data type specified and a property name
+* `Line 15`: In addition to the property name we can define a label that is designed for the end user and shown in the
+ UI.
+* `Line 16`: Assigns a human-readable description to the event property. The description is used in the StreamPipes UI
+ for better explaining users the meaning of the property.
+* `Line 17`: Specifies the semantics of the property (e.g., whether a double value stands for weight or temperature
+ value).
+* `Line 18`: Assigns a property scope to the event property. This determines how the property is handled internally.
+
+:::note
+StreamPipes does not require you to provide all of this information about a property.
+Anything beyond line `14` (up to line `20`) is optional, but the more you provide, the better StreamPipes can show it's
+full potential and feature richness.
+:::
+
+This makes our adapter almost complete, there is only one little step left.
+
+### Defining the Adapter Termination
+
+As a final step, we need to define what should happen if the adapter is stopped.
+In general, the adapter should not fire any events after that.
+Normally, this step includes things like closing connections and clearing resources.
+In our case this is quite simple, we just need to stop our thread:
+
+```java
+@Override
+public void onAdapterStopped(IAdapterParameterExtractor extractor,
+ IAdapterRuntimeContext adapterRuntimeContext) throws AdapterException {
+
+ // do cleanup
+ running = false;
+}
+```
+
+Now it's time to start our adapter and observe it in action!
+
+### Register and Run the Adapter
+
+Before we actually use our adapter, let's take a quick look at the `Init` class. This class is responsible for
+registering our adapter service with the core to make the adapter available in StreamPipes.
+This is done within `provideServiceDefinition()`. Since we don't have the generic adapter ready yet,
+we'll comment out its registration (`line 7`). Now we can run the `Init` class to register the adapter with your running
+StreamPipes instance. If you don't have a running instance at your hand,
+you can take a look at our [Installation Guide](./01_try-installation.md).
+
+```java jsx {7-8} showLineNumbers
+@Override
+public SpServiceDefinition provideServiceDefinition() {
+ return SpServiceDefinitionBuilder.create("org.apache.streampipes",
+ "human-readable service name",
+ "human-readable service description", 8090)
+ .registerRuntimeProvider(new StandaloneStreamPipesRuntimeProvider())
+ //.registerAdapter(new ParcelControlStationGenericAdapter())
+ .registerAdapter(new ParcelControlStationSpecificAdapter())
+ .registerMessagingFormats(
+ new JsonDataFormatFactory(),
+ new CborDataFormatFactory(),
+ new SmileDataFormatFactory(),
+ new FstDataFormatFactory())
+ .registerMessagingProtocols(
+ new SpKafkaProtocolFactory(),
+ new SpJmsProtocolFactory(),
+ new SpMqttProtocolFactory(),
+ new SpNatsProtocolFactory(),
+ new SpPulsarProtocolFactory())
+ .build();
+}
+ ```
+
+:::tip
+When executing the `main()` method of the `Init` class, make sure that all environment variables are set from
+the `development/env` file are set.
+If they are not set, the adapter may not be able to register with StreamPipes.
+:::
+
+Once you see the following log message in the console, the adapter is ready, and you can switch to the UI of your
+StreamPipes instance.
+
+```bash
+s.s.e.c.ConnectWorkerRegistrationService : Successfully connected to master. Worker is now running.
+```
+
+Please go to the connect module and click on `New Adapter`,
+you should now be able to see your adapter `Parcel Control Station (simple)`:
+<img src="/img/06_tutorial_adapter/adapter-demo.gif" alt="Demo of parcel adapter"/>
+
+The adapter runs successfully in StreamPipes, you can now play around with the data stream that the
+adapter, or continue with the next section to learn how to make an adapter configurable through the UI.
+
+### Building a more Advanced Adapter by Processing UI Input
+
+In this section, we will extend our previous build apter by adding the ability to configure the minimum and maximum
+package
+in the UI from which the weight value is retrieved.
+The beauty of building adapters for StreamPipes is that you don't have to worry about the UI.
+StreamPipes provides a set of pre-built input elements for adapters that you can simply add to your adapter
+configuration.
+So the first thing we need to customize is `declareConfig()`:
+
+```java jsx {10-11} showLineNumbers
+@Override
+public IAdapterConfiguration declareConfig() {
+ return AdapterConfigurationBuilder.create(
+ "org.apache.streampipes.pe.parcelcontrol.specificadapter",
+ ParcelControlStationSpecificAdapter::new
+ )
+ .withAssets(Assets.DOCUMENTATION, Assets.ICON)
+ .withCategory(AdapterType.Manufacturing)
+ .withLocales(Locales.EN)
+ .requiredFloatParameter(Labels.withId("min-weight"), 0.0f)
+ .requiredFloatParameter(Labels.withId("max-weight"), 10.f)
+ .buildConfiguration();
+}
+
+```
+
+In line `9-10` we have introduced two input parameters that expect float values as input. They have a default value
+of `0` or `10` resp. The defined identifier (`min-weight` and `max-weight`) can be used two provide a caption and
+a description via the `strings.en` file:
+
+```text
+min-weight.title=Minimum Parcel Weight
+min-weight.description=The lower bound from which the weight values are sampled randomly.
+
+max-weight.title=Maximum Parcel Weight
+max-weight.description=The upper bound from which the weight values are sampled randomly.
+```
+
+As a last step, we now need to modify the calculation of the parcel weight, so that the provided parameters are actually
+applied.
+This is done in `onAdapterStarted()`.
+
+```java jsx {6-9,24} showLineNumbers
+@Override
+public void onAdapterStarted(IAdapterParameterExtractor extractor,
+ IEventCollector collector,
+ IAdapterRuntimeContext adapterRuntimeContext) throws AdapterException {
+
+ var ex = extractor.getStaticPropertyExtractor();
+
+ float minWeight = ex.singleValueParameter("min-weight", Float.class);
+ float maxWeight = ex.singleValueParameter("max-weight", Float.class);
+
+ Runnable parcelControl = () -> {
+ while (running) {
+
+ // get the current time in seconds
+ long timestamp = System.currentTimeMillis();
+ long timeInSeconds = (int) timestamp / 1000;
+
+ // make event
+ Map<String, Object> event = new HashMap<>();
+ event.put("timestamp", timestamp);
+
+ if (timeInSeconds % 5 == 0) {
+ event.put("parcelPresent", true);
+ event.put("weight", ThreadLocalRandom.current().nextDouble(minWeight, maxWeight));
+
+ } else {
+ event.put("parcelPresent", false);
+ event.put("weight", 0);
+ }
+
+ // forward the event to the adapter pipeline
+ collector.collect(event);
+
+ try {
+ Thread.sleep(1000);
+ } catch (InterruptedException e) {
+ throw new RuntimeException(e);
+ }
+ }
+ };
+ running = true;
+ new Thread(parcelControl).start();
+}
+```
+
+* line `6-9`: We use an `StaticPropertyExtractor` to retrieve both user inputs
+* line `24`: We calculate the parcel weight by passing the configured values vor the minimum and maximum value.
+
+You can now run the `main()` method of the `Init` class to register the adapter at StreamPipes.
+The UI dialog to create a new instance of our parcel control station adapter looks now the following:
+<img src="/img/06_tutorial_adapter/adapter-with-ui-dialog.png" alt="Adapter with UI dialog"/>
+
+:::caution
+Please make sure that you uninstall the parcel adapter in `Install Pipeline Elements` before
+you restart the execution of the `Init` class, if you have already done so.
+Otherwise, the changes made in this section will have no effect.
+:::
+
+### Read More
+
+Congratulations! You've just created your first StreamPipes adapter π <br />
+
+There are many more things to explore and data sources can be defined in much more detail.
+If this is of interest to you, the [advanced section](#advanced) will satisfy your needs.
+
+If anything within this tutorial did not work for you or you had problems following it,
+please feel free to provide some feedback by opening an [issue on GitHub](https://github.com/apache/streampipes/issues/new?assignees=&labels=bug%2Cdocumentation%2Cwebsite&projects=&template=doc_website_issue_report.yml).
+
+<!-- ## Advanced
+
+There is more to come about advanced features of our adapters. Stay tuned!
+
+### Forward Log Messages to the UI to Allow Debugging for the End User
+
+### Determine the Event Schema Based on the Concrete Data Structure
+
+### Implement a Generic Adapter that is Capable of Multiple Input Formats
+
+### Extend the Existing Pool of Parsers by Your Own Parser
+
+### Introduce a Vew Version of an Adapter and Ensure Migration of Existing Adapters -->
diff --git a/website-v2/versioned_docs/version-0.98.0/06_extend-tutorial-data-processors.md b/website-v2/versioned_docs/version-0.98.0/06_extend-tutorial-data-processors.md
new file mode 100644
index 000000000..4c2d5ee25
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/06_extend-tutorial-data-processors.md
@@ -0,0 +1,454 @@
+---
+id: extend-tutorial-data-processors
+title: "Tutorial: Data Processors"
+sidebar_label: "Tutorial: Data Processors"
+---
+
+In this tutorial, we will add a new data processor.
+
+From an architectural point of view, we will create a self-contained service that includes the description of the data
+processor and an implementation.
+
+## Objective
+
+We are going to create a new data processor that realizes a simple geofencing algorithm - we detect vehicles that enter
+a specified radius around a user-defined location.
+This pipeline element will be a generic element that works with any event stream that provides geospatial coordinates in
+form of a latitude/longitude pair.
+
+The algorithm outputs every location event once the position has entered the geofence.
+
+:::note
+
+The implementation in this tutorial is pretty simple - our processor will fire an event every time the GPS location is
+inside the geofence.
+In a real-world application, you would probably want to define a pattern that recognizes the _first_ event a vehicle
+enters the geofence.
+
+This can be easily done using a CEP library.
+
+:::
+
+## Project setup
+
+Instead of creating a new project from scratch, we recommend to use the Maven archetype to create a new project
+skeleton (streampipes-archetype-extensions-jvm).
+Enter the following command in a command line of your choice (Apache Maven needs to be installed):
+
+```
+mvn archetype:generate \
+-DarchetypeGroupId=org.apache.streampipes -DarchetypeArtifactId=streampipes-archetype-extensions-jvm \
+-DarchetypeVersion=0.93.0 -DgroupId=my.groupId \
+-DartifactId=my-example -DclassNamePrefix=MyExample -DpackageName=mypackagename
+```
+
+You will see a project structure similar to the structure shown in the [archetypes](06_extend-archetypes.md) section.
+
+:::tip
+
+Besides the basic project skeleton, the sample project also includes an example Dockerfile you can use to package your
+application into a Docker container.
+
+:::
+
+Now you're ready to create your first data processor for StreamPipes!
+
+## Adding data processor requirements
+
+First, we will add a new stream requirement.
+Create a new class `GeofencingProcessor` which should look as follows:
+
+```java
+package org.apache.streampipes.pe.example;
+
+import org.apache.streampipes.extensions.api.pe.IStreamPipesDataProcessor;
+import org.apache.streampipes.extensions.api.pe.config.IDataProcessorConfiguration;
+import org.apache.streampipes.extensions.api.pe.context.EventProcessorRuntimeContext;
+import org.apache.streampipes.extensions.api.pe.param.IDataProcessorParameters;
+import org.apache.streampipes.extensions.api.pe.routing.SpOutputCollector;
+import org.apache.streampipes.model.runtime.Event;
+import org.apache.streampipes.sdk.builder.ProcessingElementBuilder;
+import org.apache.streampipes.sdk.builder.StreamRequirementsBuilder;
+import org.apache.streampipes.sdk.builder.processor.DataProcessorConfiguration;
+import org.apache.streampipes.sdk.helpers.EpProperties;
+import org.apache.streampipes.sdk.helpers.EpRequirements;
+import org.apache.streampipes.sdk.helpers.Labels;
+import org.apache.streampipes.sdk.helpers.OutputStrategies;
+import org.apache.streampipes.sdk.helpers.SupportedFormats;
+import org.apache.streampipes.sdk.helpers.SupportedProtocols;
+import org.apache.streampipes.vocabulary.SO;
+
+public class GeofencingProcessor implements IStreamPipesDataProcessor {
+
+ private static final String LATITUDE_CENTER = "latitude-center";
+ private static final String LONGITUDE_CENTER = "longitude-center";
+
+
+ public IDataProcessorConfiguration declareConfig() {
+ return DataProcessorConfiguration.create(
+ GeofencingProcessor::new,
+ ProcessingElementBuilder.create(
+ "org.apache.streampipes.tutorial-geofencing"
+ )
+ .category(DataProcessorType.ENRICH)
+ .withAssets(Assets.DOCUMENTATION, Assets.ICON)
+ .build());
+ }
+
+ @Override
+ public void onPipelineStarted(IDataProcessorParameters params,
+ SpOutputCollector collector,
+ EventProcessorRuntimeContext runtimeContext) {
+
+ }
+
+ @Override
+ public void onEvent(Event event,
+ SpOutputCollector collector) {
+
+ }
+
+ @Override
+ public void onPipelineStopped() {
+
+ }
+}
+
+
+```
+
+In this class, we need to implement three methods: The `declareConfig` method is used to define abstract stream
+requirements such as event properties that must be present in any input stream that is later connected to the element
+using the StreamPipes UI.
+The second method, `onPipelineStarted` is triggered once a pipeline is started.
+The `onEvent` method is called for every incoming event.
+Finally, the `onPipelineStopped` method is called once the pipeline is stopped.
+
+Similar to data sources, the SDK provides a builder class to generate the description for data processors.
+
+The current code within the `declareConfig` method creates a new data processor with the ID.
+The ID is used as the internal ID of the data processor, but also used to reference additional assets in the `resources` folder, such as a `strings.en` file, used to configure labels and description, and a `documentation.md` file, which will later servce as a markdown documentation in the UI.
+But first, we will add some _stream requirements_ to the description. As we'd like to develop a generic pipeline element that
+works with any event that provides a lat/lng pair, we define two stream requirements as stated below:
+
+```java
+.requiredStream(StreamRequirementsBuilder
+ .create()
+ .requiredPropertyWithUnaryMapping(
+ EpRequirements.domainPropertyReq(Geo.LAT),
+ Labels.from("latitude-field","Latitude","The event property containing the latitude value"),
+ PropertyScope.MEASUREMENT_PROPERTY
+ )
+ .requiredPropertyWithUnaryMapping(
+ EpRequirements.domainPropertyReq(Geo.LNG),
+ Labels.from("longitude-field","Longitude","The event property containing the longitude value"),
+ PropertyScope.MEASUREMENT_PROPERTY
+ )
+ .build())
+```
+
+The first line, `.requiredStream()` defines that we want a data processor with exactly one input stream. Adding more
+stream requirements would create elements with multiple input connectors in StreamPipes.
+Stream requirements can be assigned by using the `StreamRequirementsBuilder` class.
+In our example, we define two requirements, so-called _domain property requirements_. In contrast to _data type
+requirements_ where we'd expect an event property with a field of a specific data type (e.g., float), domain property
+requirements expect a specific semantic type (called domain property), e.g., from a vocabulary such as the WGS84 Geo vocab.
+
+Once a pipeline is deployed, we are interested in the actual field (and its field name) that contains the latitude and
+longitude values.
+In some cases, there might be more than one field that satisfies a property requirement, and we would like users to
+select the property the geofencing component should operate on.
+Therefore, our example uses the method `requiredPropertyWithUnaryMapping`, which will map a requirement to a real event
+property of an input stream and let the user choose the appropriate field in the StreamPipes UI when pipelines are
+defined.
+
+Finally, the `PropertyScope` indicates that the required property is a measurement value (in contrast to a dimension
+value). This allows us later to provide improved user guidance in the pipeline editor.
+
+Similar to mapping properties, text parameters have an internalId (radius), a label and a description.
+In addition, we can assign a _value specification_ to the parameter indicating the value range we support.
+Our example supports a radius value between 0 and 1000 with a granularity of 1.
+In the StreamPipes UI, a required text parameter is rendered as a text input field, in case we provide an optional value
+specification, a slider input is automatically generated.
+
+For now, we've assigned parameters with an internal ID, a label and a description.
+To decouple human-readable labels and description from the actual data processor description, it is possible to extract the strings to a properties file.
+In the `resources` folder, switch to a folder with the same name as the data processor's ID. If you've used the Maven archetype to build our project, there should be a `strings.en` file.
+In this file, we can configure labels and descriptions. For instance, instead of writing
+
+```java
+
+.requiredPropertyWithUnaryMapping(
+ EpRequirements.domainPropertyReq(Geo.LAT),
+ Labels.from("latitude-field","Latitude","The event property containing the latitude value"),
+ PropertyScope.MEASUREMENT_PROPERTY
+ )
+
+```
+
+it is recommended to write
+
+```java
+
+.requiredPropertyWithUnaryMapping(
+ EpRequirements.domainPropertyReq(Geo.LAT),
+ Labels.withId("latitude-field"),
+ PropertyScope.MEASUREMENT_PROPERTY
+ )
+
+```
+
+and add the following line to the `strings.en` file:
+
+```properties
+
+latitude-field.title=Latitude
+latitute-field.description=The event property containing the latitude value
+
+```
+
+This feature will also ease future internationalization efforts.
+
+Besides requirements, users should be able to define the center coordinate of the Geofence and the size of the fence
+defined as a radius around the center in meters.
+The radius can be defined by adding a simple required text field to the description:
+
+```java
+.requiredIntegerParameter("radius","Geofence Size","The size of the circular geofence in meters.",0,1000,1)
+```
+
+Such user-defined parameters are called _static properties_. There are many different types of static properties (see
+the [Processor SDK](06_extend-sdk-static-properties.md) for an overview). Similar to stream requirements, it is also recommended to type `Labels.withId("radius")` and move labels and descriptions to the resource file.
+
+In this example, we'll further add two very simple input fields to let users provide latitude and longitude of the
+geofence center.
+
+Add the following line to the `declareConfig` method:
+
+```java
+ .requiredFloatParameter(Labels.from(LATITUDE_KEY,"Latitude","The latitude value"))
+ .requiredFloatParameter(Labels.from(LONGITUDE_KEY,"Longitude","The longitude value"))
+
+```
+
+Now we need to define the output of our Geofencing pipeline element.
+As explained in the first section, the element should fire every time some geo-located entity arrives within the defined
+geofence.
+Therefore, the processor outputs the same schema as it receives as an input.
+Although we don't know the exact input right now as it depends on the stream users connect in StreamPipes when creating
+pipelines, we can define an _output strategy_ as follows:
+
+```java
+.outputStrategy(OutputStrategies.keep())
+```
+
+This defines a _KeepOutputStrategy_, i.e., the input event schema is not modified by the processor.
+There are many more output strategies you can define depending on the functionality you desire, e.g., _AppendOutput_ for
+defining a processor that enriches events or _CustomOutput_ in case you would like users to select the output by
+themselves.
+
+That's it! We've now defined input requirements, required user input and an output strategy.
+In the next section, you will learn how to extract these parameters once the pipeline element is invoked after a
+pipeline was created.
+
+## Pipeline element invocation
+
+Once users start a pipeline that uses our geofencing component, the _onPipelineStarted_ method in our class is called. The
+interface `IDataProcessorParameters` includes convenient access to user-configured parameters a users has selected in the pipeline
+editor and information on the actual streams that are connected to the pipeline element.
+
+Next, we are interested in the fields of the input event stream that contains the latitude and longitude value we would
+like to compute against the geofence center location as follows:
+
+```java
+ String latitudeFieldName = params.extractor().mappingPropertyValue("latitude-field");
+ String longitudeFieldName = params.extractor().mappingPropertyValue("longitude-field");
+```
+
+We use the same `internalId` we've used to define the mapping property requirements in the `declareModel` method.
+
+Next, for extracting the geofence center coordinates, add to class variables centerLatitude and centerLongitude and
+assign the selected values using the following statements:
+
+```java
+ this.centerLatitude = params.extractor().singleValueParameter(LATITUDE_CENTER,Float.class);
+ this.centerLongitude = params.extractor().singleValueParameter(LONGITUDE_CENTER,Float.class);
+```
+
+The radius value can be extracted as follows:
+
+```java
+ int radius = params.extractor().singleValueParameter("radius",Float.class);
+```
+
+Great! That's all we need to describe a data processor for usage in StreamPipes. Your processor class should look as
+follows:
+
+```java
+
+package org.apache.streampipes.pe.example;
+
+import org.apache.streampipes.extensions.api.pe.IStreamPipesDataProcessor;
+import org.apache.streampipes.extensions.api.pe.config.IDataProcessorConfiguration;
+import org.apache.streampipes.extensions.api.pe.context.EventProcessorRuntimeContext;
+import org.apache.streampipes.extensions.api.pe.param.IDataProcessorParameters;
+import org.apache.streampipes.extensions.api.pe.routing.SpOutputCollector;
+import org.apache.streampipes.model.runtime.Event;
+import org.apache.streampipes.sdk.builder.ProcessingElementBuilder;
+import org.apache.streampipes.sdk.builder.StreamRequirementsBuilder;
+import org.apache.streampipes.sdk.builder.processor.DataProcessorConfiguration;
+import org.apache.streampipes.sdk.helpers.EpProperties;
+import org.apache.streampipes.sdk.helpers.EpRequirements;
+import org.apache.streampipes.sdk.helpers.Labels;
+import org.apache.streampipes.sdk.helpers.OutputStrategies;
+import org.apache.streampipes.sdk.helpers.SupportedFormats;
+import org.apache.streampipes.sdk.helpers.SupportedProtocols;
+import org.apache.streampipes.vocabulary.SO;
+
+public class GeofencingProcessor implements IStreamPipesDataProcessor {
+
+ private static final String LATITUDE_CENTER = "latitude-center";
+ private static final String LONGITUDE_CENTER = "longitude-center";
+
+ private float centerLatitude;
+ private float centerLongitude;
+ private String latitudeFieldName;
+ private String longitudeFieldName;
+
+ private int radius;
+
+ public IDataProcessorConfiguration declareConfig() {
+ return DataProcessorConfiguration.create(
+ GeofencingProcessor::new,
+ ProcessingElementBuilder.create("org.streampipes.tutorial-geofencing")
+ .category(DataProcessorType.ENRICH)
+ .withAssets(Assets.DOCUMENTATION, Assets.ICON)
+ .withLocales(Locales.EN)
+ .requiredStream(StreamRequirementsBuilder
+ .create()
+ .requiredPropertyWithUnaryMapping(EpRequirements.domainPropertyReq(Geo.lat),
+ Labels.from("latitude-field", "Latitude", "The event " +
+ "property containing the latitude value"), PropertyScope.MEASUREMENT_PROPERTY)
+ .requiredPropertyWithUnaryMapping(EpRequirements.domainPropertyReq(Geo.lng),
+ Labels.from("longitude-field", "Longitude", "The event " +
+ "property containing the longitude value"), PropertyScope.MEASUREMENT_PROPERTY)
+ .build())
+ .outputStrategy(OutputStrategies.keep())
+ .requiredIntegerParameter("radius", "Geofence Size", "The size of the circular geofence in meters.", 0, 1000, 1)
+ .requiredFloatParameter(Labels.from(LATITUDE_CENTER, "Latitude", "The latitude value"))
+ .requiredFloatParameter(Labels.from(LONGITUDE_CENTER, "Longitude", "The longitude value"))
+ .build()
+ );
+ }
+
+ @Override
+ public void onPipelineStarted(IDataProcessorParameters params,
+ SpOutputCollector collector,
+ EventProcessorRuntimeContext runtimeContext) {
+ this.centerLatitude = params.extractor().singleValueParameter(LATITUDE_CENTER, Float.class);
+ this.centerLongitude = params.extractor().singleValueParameter(LONGITUDE_CENTER, Float.class);
+ this.latitudeFieldName = params.extractor().mappingPropertyValue("latitude-field");
+ this.longitudeFieldName = params.extractor().mappingPropertyValue("longitude-field");
+ this.radius = params.extractor().singleValueParameter("radius", Integer.class);
+ }
+
+ @Override
+ public void onEvent(Event event,
+ SpOutputCollector collector) {
+
+ }
+
+ @Override
+ public void onPipelineStopped() {
+
+ }
+}
+
+```
+
+## Adding an implementation
+
+Everything we need to do now is to add an implementation.
+
+Add the following piece of code to the onEvent method, which realizes the Geofencing functionality:
+
+```java
+
+ @Override
+ public void onEvent(Event event,
+ SpOutputCollector collector) {
+ float latitude = event.getFieldBySelector(latitudeFieldName).getAsPrimitive().getAsFloat();
+ float longitude = event.getFieldBySelector(longitudeFieldName).getAsPrimitive().getAsFloat();
+
+ float distance = distFrom(latitude,longitude, centerLatitude, centerLongitude);
+
+ if(distance <= radius){
+ collector.collect(event);
+ }
+ }
+
+ public static float distFrom(float lat1, float lng1, float lat2, float lng2) {
+ double earthRadius = 6371000;
+ double dLat = Math.toRadians(lat2-lat1);
+ double dLng = Math.toRadians(lng2-lng1);
+ double a = Math.sin(dLat/2)*Math.sin(dLat/2) +
+ Math.cos(Math.toRadians(lat1))*Math.cos(Math.toRadians(lat2)) *
+ Math.sin(dLng/2)*Math.sin(dLng/2);
+
+ double c = 2*Math.atan2(Math.sqrt(a),Math.sqrt(1-a));
+
+ return(float)(earthRadius*c);
+ }
+```
+
+We won't go into details here as this isn't StreamPipes-related code, but in general the class extracts latitude and
+longitude fields from the input event (which is provided as a map data type) and calculates the distance between the
+geofence center and these coordinates.
+If the distance is below the given radius, the event is forwarded to the next operator.
+
+See the [event model](06_extend-sdk-event-model.md) guide to learn how to extract parameters from events.
+
+## Registering the pipeline element
+
+The final step is to register the data processor in the `Init` method. Add the following line to
+the `SpServiceDefinitionBuilder`:
+
+```java
+ .registerPipelineElement(new GeofencingProcessor())
+```
+
+## Starting the service
+
+:::tip
+
+Once you start the service, it will register in StreamPipes with the hostname. The hostname will be auto-discovered and
+should work out-of-the-box.
+In some cases, the detected hostname is not resolvable from within a container (where the core is running). In this
+case, provide a SP_HOST environment variable to override the auto-discovery.
+
+:::
+
+:::tip
+
+The default port of all pipeline element services as defined in the `create` method is port 8090.
+If you'd like to run multiple services at the same time on your development machine, change the port here. As an
+alternative, you can also provide an env variable `SP_PORT` which overrides the port settings. This is useful to use
+different configs for dev and prod environments.
+
+:::
+
+Now we are ready to start our service!
+
+Configure your IDE to provide an environment variable called ``SP_DEBUG`` with value ``true`` when starting the project.
+
+Execute the main method in the class `Init` we've just created.
+
+The service automatically registers itself in StreamPipes.
+To install the just created element, open the StreamPipes UI and follow the manual provided in
+the [user guide](03_use-install-pipeline-elements.md).
+
+## Read more
+
+Congratulations! You've just created your first data processor for StreamPipes.
+There are many more things to explore and data processors can be defined in much more detail using multiple wrappers.
+Follow our [SDK guide](06_extend-sdk-static-properties.md) to see what's possible!
diff --git a/website-v2/versioned_docs/version-0.98.0/06_extend-tutorial-data-sinks.md b/website-v2/versioned_docs/version-0.98.0/06_extend-tutorial-data-sinks.md
new file mode 100644
index 000000000..09baeff71
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/06_extend-tutorial-data-sinks.md
@@ -0,0 +1,272 @@
+---
+id: extend-tutorial-data-sinks
+title: "Tutorial: Data Sinks"
+sidebar_label: "Tutorial: Data Sinks"
+---
+
+In this tutorial, we will add a new data sink using the standalone wrapper.
+
+From an architectural point of view, we will create a self-contained service that includes the description of the data
+sink and a corresponding implementation.
+
+## Objective
+
+We are going to create a new data sink that calls an external HTTP endpoint to forward data to an external service.
+
+For each incoming event, an external service is invoked using an HTTP POST request. In this example, we'll call an
+endpoint provided by [RequestBin](https://requestbin.com/).
+To setup your own endpoint, go to [https://requestbin.com/](https://requestbin.com/) and click "Create a request bin".
+Copy the URL of the newly created endpoint.
+
+## Project setup
+
+Instead of creating a new project from scratch, we recommend to use the Maven archetype to create a new project
+skeleton (streampipes-archetype-extensions-jvm).
+Enter the following command in a command line of your choice (Apache Maven needs to be installed):
+
+```
+mvn archetype:generate -DarchetypeGroupId=org.apache.streampipes \
+-DarchetypeArtifactId=streampipes-archetype-extensions-jvm -DarchetypeVersion=0.93.0 \
+-DgroupId=org.streampipes.tutorial -DartifactId=sink-tutorial -DclassNamePrefix=Rest -DpackageName=mypackage
+```
+
+You will see a project structure similar to the structure shown in the [archetypes](06_extend-archetypes.md) section.
+
+:::tip
+
+Besides the basic project skeleton, the sample project also includes an example Dockerfile you can use to package your
+application into a Docker container.
+
+:::
+
+Now you're ready to create your first data sink for StreamPipes!
+
+## Adding data sink requirements
+
+First, we will add a new stream requirement.
+Create a class `RestSink` which should look as follows:
+
+```java
+package org.apache.streampipes.pe.example;
+
+import org.apache.streampipes.extensions.api.pe.IStreamPipesDataSink;
+import org.apache.streampipes.extensions.api.pe.config.IDataSinkConfiguration;
+import org.apache.streampipes.extensions.api.pe.context.EventSinkRuntimeContext;
+import org.apache.streampipes.extensions.api.pe.param.IDataSinkParameters;
+import org.apache.streampipes.model.DataSinkType;
+import org.apache.streampipes.model.runtime.Event;
+import org.apache.streampipes.model.schema.PropertyScope;
+import org.apache.streampipes.sdk.builder.DataSinkBuilder;
+import org.apache.streampipes.sdk.builder.StreamRequirementsBuilder;
+import org.apache.streampipes.sdk.builder.sink.DataSinkConfiguration;
+import org.apache.streampipes.sdk.helpers.EpRequirements;
+import org.apache.streampipes.sdk.helpers.Labels;
+import org.apache.streampipes.sdk.helpers.Locales;
+import org.apache.streampipes.sdk.utils.Assets;
+
+public class RestSink implements IStreamPipesDataSink {
+
+ @Override
+ public IDataSinkConfiguration declareConfig() {
+ return DataSinkConfiguration.create(
+ RestSink::new,
+ DataSinkBuilder.create("org.apache.streampipes.tutorial.pe.sink.rest")
+ .category(DataSinkType.NOTIFICATION)
+ .withAssets(Assets.DOCUMENTATION, Assets.ICON)
+ .withLocales(Locales.EN)
+ .requiredStream(StreamRequirementsBuilder
+ .create()
+ .requiredPropertyWithNaryMapping(EpRequirements.anyProperty(), Labels.withId(
+ "fields-to-send"), PropertyScope.NONE)
+ .build())
+ .build()
+ );
+ }
+
+ @Override
+ public void onPipelineStarted(IDataSinkParameters params,
+ EventSinkRuntimeContext eventSinkRuntimeContext) {
+
+ }
+
+ @Override
+ public void onEvent(Event event) {
+
+ }
+
+ @Override
+ public void onPipelineStopped() {
+
+ }
+
+
+```
+
+In this class, we need to implement three methods: The `declareConfig` method is used to define abstract stream
+requirements such as event properties that must be present in any input stream that is later connected to the element
+using the StreamPipes UI.
+The second method, `onPipelineStarted` is called once a pipeline using this sink is started. The third method, `onEvent`, is
+called for every incoming event.
+
+The `DataSinkBuilder` within the ``declareConfig`` method describes the properties of our data sink:
+
+* ``category`` defines a category for this sink.
+* ``withAssets`` denotes that we will provide an external documentation file and an icon, which can be found in
+ the ``resources`` folder
+* ``withLocales`` defines that we will provide an external language file, also available in the ``resources`` folder
+* ``requiredStream`` defines requirements any input stream connected to this sink must provide. In this case, we do not
+ have any specific requirements, we just forward all incoming events to the REST sink. However, we want to let the user
+ display a list of available fields from the connected input event, where users can select a subset. This is defined by
+ defining a Mapping from the empty requirement. This will later on render a selection dialog in the pipeline editor.
+
+The ``onPipelineStarted`` method is called when a pipeline containing the sink is started. Once a pipeline is started, we
+would like to extract user-defined parameters.
+In this example, we simply extract the fields selected by users that should be forwarded to the REST sink. Finally, we
+return a new configured event sink containing the parameters.
+
+## Pipeline element invocation
+
+Once users start a pipeline that uses our geofencing component, the _onInvocation_ method in our class is called. The
+interface `IDataSinkParameters` includes methods to extract the configuration parameters a user has selected in
+the pipeline editor and information on the actual streams that are connected to the pipeline element.
+
+## Adding an implementation
+
+Now we'll add a proper implementation (i.e., the Rest call executed for every incoming event) to the following methods:
+
+Our final class should look as follows:
+
+```java
+package org.apache.streampipes.pe.example;
+
+import org.apache.streampipes.commons.exceptions.SpRuntimeException;
+import org.apache.streampipes.dataformat.SpDataFormatDefinition;
+import org.apache.streampipes.dataformat.json.JsonDataFormatDefinition;
+import org.apache.streampipes.extensions.api.pe.IStreamPipesDataSink;
+import org.apache.streampipes.extensions.api.pe.config.IDataSinkConfiguration;
+import org.apache.streampipes.extensions.api.pe.context.EventSinkRuntimeContext;
+import org.apache.streampipes.extensions.api.pe.param.IDataSinkParameters;
+import org.apache.streampipes.model.DataSinkType;
+import org.apache.streampipes.model.runtime.Event;
+import org.apache.streampipes.model.schema.PropertyScope;
+import org.apache.streampipes.sdk.builder.DataSinkBuilder;
+import org.apache.streampipes.sdk.builder.StreamRequirementsBuilder;
+import org.apache.streampipes.sdk.builder.sink.DataSinkConfiguration;
+import org.apache.streampipes.sdk.helpers.EpRequirements;
+import org.apache.streampipes.sdk.helpers.Labels;
+import org.apache.streampipes.sdk.helpers.Locales;
+import org.apache.streampipes.sdk.utils.Assets;
+
+import com.google.common.base.Charsets;
+import org.apache.http.client.fluent.Request;
+import org.apache.http.entity.StringEntity;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import java.io.IOException;
+import java.util.List;
+import java.util.Map;
+
+public class RestSink implements IStreamPipesDataSink {
+
+ private static final Logger LOG = LoggerFactory.getLogger(RestSink.class);
+
+ private static final String REST_ENDPOINT_URI = YOUR_REQUEST_BIN_URL;
+ private List<String> fieldsToSend;
+ private SpDataFormatDefinition dataFormatDefinition;
+
+ @Override
+ public IDataSinkConfiguration declareConfig() {
+ return DataSinkConfiguration.create(
+ RestSink::new,
+ DataSinkBuilder.create("org.apache.streampipes.tutorial.pe.sink.rest")
+ .category(DataSinkType.NOTIFICATION)
+ .withAssets(Assets.DOCUMENTATION, Assets.ICON)
+ .withLocales(Locales.EN)
+ .requiredStream(StreamRequirementsBuilder
+ .create()
+ .requiredPropertyWithNaryMapping(EpRequirements.anyProperty(), Labels.withId(
+ "fields-to-send"), PropertyScope.NONE)
+ .build())
+ .build()
+ );
+ }
+
+ @Override
+ public void onPipelineStarted(IDataSinkParameters params,
+ EventSinkRuntimeContext eventSinkRuntimeContext) {
+ this.dataFormatDefinition = new JsonDataFormatDefinition();
+ this.fieldsToSend = params.extractor().mappingPropertyValues("fields-to-send");
+ }
+
+ @Override
+ public void onEvent(Event event) {
+ Map<String, Object> outEventMap = event.getSubset(fieldsToSend).getRaw();
+ try {
+ String json = new String(dataFormatDefinition.fromMap(outEventMap));
+ Request.Post(REST_ENDPOINT_URI).body(new StringEntity(json, Charsets.UTF_8)).execute();
+ } catch (SpRuntimeException e) {
+ LOG.error("Could not parse incoming event");
+ } catch (IOException e) {
+ LOG.error("Could not reach endpoint at {}", REST_ENDPOINT_URI);
+ }
+ }
+
+ @Override
+ public void onPipelineStopped() {
+
+ }
+}
+
+```
+
+The only class variable you need to change right now is the REST_ENDPOINT_URL. Change this url to the URL provided by
+your request bin.
+In the ``Γ²nEvent`` method, we use a helper method to get a subset of the incoming event.
+Finally, we convert the resulting ``Map`` to a JSON string and call the endpoint.
+
+## Preparing the service
+
+The final step is to register the sink as a pipeline element.
+
+Go to the class `Init` and register the sink:
+
+```java
+.registerPipelineElement(new RestSink())
+```
+
+## Starting the service
+
+:::tip
+
+Once you start the service, it will register in StreamPipes with the hostname. The hostname will be auto-discovered and
+should work out-of-the-box.
+In some cases, the detected hostname is not resolvable from within a container (where the core is running). In this
+case, provide a SP_HOST environment variable to override the auto-discovery.
+
+:::
+
+:::tip
+
+The default port of all pipeline element services as defined in the `create` method is port 8090.
+If you'd like to run multiple services at the same time on your development machine, change the port here. As an
+alternative, you can also provide an env variable `SP_PORT` which overrides the port settings. This is useful to use
+different configs for dev and prod environments.
+
+:::
+
+Now we are ready to start our service!
+
+Configure your IDE to provide an environment variable called ``SP_DEBUG`` with value ``true`` when starting the project.
+
+Execute the main method in the class `Init` we've just created. The service automatically registers itself in
+StreamPipes.
+
+To install the created element, open the StreamPipes UI and follow the manual provided in
+the [user guide](03_use-install-pipeline-elements.md).
+
+## Read more
+
+Congratulations! You've just created your first data sink for StreamPipes.
+There are many more things to explore and data sinks can be defined in much more detail using multiple wrappers.
+Follow our [SDK guide](../dev-guide-sdk-guide-sinks) to see what's possible!
diff --git a/website-v2/versioned_docs/version-0.98.0/07_technicals-architecture.md b/website-v2/versioned_docs/version-0.98.0/07_technicals-architecture.md
new file mode 100644
index 000000000..e62ba4625
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/07_technicals-architecture.md
@@ -0,0 +1,110 @@
+---
+id: technicals-architecture
+title: Architecture
+sidebar_label: Architecture
+---
+
+## Architecture
+
+<img className="docs-image" src="/img/07_technicals/architecture.png" alt="StreamPipes Architecture"/>
+
+Apache StreamPipes implements a microservice architecture as shown in the figure above.
+
+## StreamPipes Core
+
+The StreamPipes Core is the central component to manage all StreamPipes resources.
+It delegates the management of adapters, pipeline elements, pipelines and functions to registered extensions services (see below) and monitors the execution of extensions.
+The Core also provides internal REST interfaces to communicate with the user interface, as well as public REST interfaces that can be used by external applications and StreamPipes clients.
+
+Configuration and user data are stored in an Apache CouchDB database.
+
+## StreamPipes Extensions
+
+An Apache StreamPipes extensions service is a microservice which contains the implementation of specific adapters, data streams, data processors, data sinks and functions.
+Multiple extension services can be part of a single StreamPipes installation.
+Each service might provide its own set of extensions. Extensions services register at the StreamPipes Core at startup. Users are able to install all or a subset of extensions of each service.
+This allows StreamPipes to be extended at runtime by starting a new service with additional extensions.
+
+Extensions can be built using the SDK (see [Extending StreamPipes](06_extend-setup.md)).
+Extensions services can be provided either in Java or in Python.
+
+:::info
+
+As of version 0.93.0, the Python SDK supports functions only. If you would like to develop pipeline elements in Python as well, let us know in a [Github discussions](https://github.com/apache/streampipes/discussions) comment, so that we can better prioritize development.
+
+:::
+
+
+An extensions service interacts with the core by receiving control messages to invoke or detach an extension.
+In addition, the core regularly fetches monitoring and log data from each registered extensions service.
+
+
+## StreamPipes Client
+
+The Apache StreamPipes Client is a lightweight library for Java and Python which can be used to interact with StreamPipes resources programmatically.
+For instance, users use the client to influence the control flow of pipelines, to download raw data from the data lake APIs or to realize custom applications with live data.
+
+
+## Third-party systems
+
+In addition to the core components, an Apache StreamPipes version uses several third-party services, which are part of the standard installation.
+
+* Configurations and user data is stored in an [Apache CouchDB](https://couchdb.apache.org) database.
+* Time-series data is stored in an [InfluxDB](https://github.com/influxdata/influxdb) database.
+* Events are exchanged over a messaging system. Users can choose from various messaging systems that StreamPipes supports. Currently, we support [Apache Kafka](https://kafka.apache.org), [Apache Pulsar](https://pulsar.apache.org), [MQTT](https://mqtt.org/) and [NATS](https://nats.io/). The selection of the right messaging system depends on the use case. See [Messaging](07_technicals-messaging.md) for more information.
+
+:::info
+
+Versions prior to 0.93.0 included Consul for service discovery and registration. Starting from 0.93.0 onwards, we switched to an internal service discovery mechanism.
+
+:::
+
+All mentioned third-party services are part of the default installation and are auto-configured during the installation process.
+
+## Programming Languages
+
+Apache StreamPipes is mainly written in Java.
+Services are based on Spring Boot.
+The included [Python integration](https://streampipes.apache.org/docs/docs/python/latest/) is written in Python.
+
+The user interface is mainly written in TypeScript using the Angular framework.
+
+
+## Data Model
+
+Internally, Apache StreamPipes realizes a stream processing layer where events are continuously exchanged over a messaging system.
+When building a pipeline, data processors consume data from a topic assigned by the core and publish data back to another topic, which is also assigned by the core.
+
+At runtime, events have a flat and easily understandable data structure, consisting of key/value pairs. Events are serialized in JSON, although StreamPipes can be configured to use other (binary) message formats.
+
+This allows for easy integration with other systems which want to consume data from Streampipes, since an event could look as simple as this:
+
+```json
+{
+ "timestamp": 1234556,
+ "deviceId": "ABC",
+ "temperature": 37.5
+}
+```
+
+However, this wouldn't be very expressive, right? To [assist users](07_technicals-user-guidance.md), StreamPipes provides a rich description layer for events. So under the hood, for the `temperature` field shown above StreamPipes can also store the following:
+
+```json
+{
+ "label": "Temperature",
+ "description": "Measures the temperature during leakage tests",
+ "measurementUnit": "https://qudt.org/vocab/unit/DEG_C",
+ "runtimeName": "temperature",
+ "runtimeType": "xsd:float",
+ "semanticType": "https://my-company-vocabulary/leakage-test-temperature"
+}
+```
+
+By dividing the description layer from the runtime representation, we get a good trade-off between expressivity, readability for humans and lightweight runtime message formats.
+The schema is stored in an internal schema registry and available to the client APIs and user interface views to improve validation and user guidance.
+
+StreamPipes also supports arrays and nested structures, although we recommend using flat events where possible to ease integration with downstream systems (such as time-series storage).
+
+
+
+
diff --git a/website-v2/versioned_docs/version-0.98.0/07_technicals-messaging.md b/website-v2/versioned_docs/version-0.98.0/07_technicals-messaging.md
new file mode 100644
index 000000000..d5308a6d8
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/07_technicals-messaging.md
@@ -0,0 +1,65 @@
+---
+id: technicals-messaging
+title: Messaging
+sidebar_label: Messaging
+---
+
+## Architecture
+
+To exchange messages at runtime between individual [Extensions Services](07_technicals-architecture.md), StreamPipes uses external messaging systems.
+This corresponds to an event-driven architecture with a central message broker and decoupled services which consume and produce events from the messaging system.
+
+There are many different open source messaging systems on the market, which each have individual strengths.
+To provide a flexible system which matches different needs, StreamPipes can be configured to use various messaging systems.
+
+## Supported messaging systems
+
+The following messaging systems are currently supported:
+
+* Apache Kafka
+* Apache Pulsar
+* MQTT
+* NATS
+
+## Configure StreamPipes to use another messaging system
+
+Configuring StreamPipes for one of these messaging system is an installation-time configuration.
+We currently do not recommend to change the configuration at runtime.
+
+The protocol can be configured with the environment variable `SP_PRIORITIZED_PROTOCOL` assigned to the core with one of the following values:
+
+```bash
+SP_PRIORITIZED_PROTOCOL=kafka # Use Kafka as protocol
+SP_PRIORITIZED_PROTOCOL=pulsar # Use Pulsar as protocol
+SP_PRIORITIZED_PROTOCOL=mqtt # Use MQTT as protocol
+SP_PRIORITIZED_PROTOCOL=nats # Use NATS as protocol
+```
+
+Note that each extension service can support an arbitrary number of protocols. For instance, you can have a lightweight extension service which only supports NATS, but have another, cloud-centered service which supports Kafka, both registered at the Core.
+To select a protocol when multiple protocols are supported by two pipeline elements, StreamPipes selects a protocol based on a priority, which can be configured in the [Configuration View](03_use-configurations.md).
+StreamPipes ensures that only pipeline elements which have a commonly supported protocol can be connected.
+
+Note that you might need to change the installation files. For the `Docker-Compose` based installation, we provide various compose file for different messaging setups. For the `Kubernetes` installation, we provide variables which can be set in the helm chart's `values.yaml` file.
+
+### Configure broker addresses
+
+By default, StreamPipes assumes that the messaging system is started from its own environment, e.g., the system configured in the selected `Docker-Compose` file.
+
+Besides that, it is also possible to let StreamPipes connect to an externally provided messaging system. For this purpose, various environment variables exist.
+
+* `SP_PRIORITIZED_PROTOCOL` to set the prioritized protocol to either `kafka`, `mqtt`, `nats` or `pulsar`
+
+* `SP_KAFKA_HOST`, `SP_KAFKA_PORT` to configure Kafka access
+* `SP_MQTT_HOST`, `SP_MQTT_PORT` to configure MQTT access
+* `SP_NATS_HOST`, `SP_NATS_PORT` to configure NATS access
+* `SP_PULSAR_URL` to configure Pulsar access
+
+
+Most settings can also be set in the UI under `Settings->Messaging`.
+
+:::warning Installation-time configurations
+Although it is currently possible to change messaging settings in the user interface, we do not support dynamic modification of messaging systems.
+Choosing a proper system is considered an installation-time setting which should not be changed afterwards.
+Already existing Adapters and pipeline elements are not properly updated after changes of the messaging layer.
+:::
+
diff --git a/website-v2/versioned_docs/version-0.98.0/07_technicals-runtime-wrappers.md b/website-v2/versioned_docs/version-0.98.0/07_technicals-runtime-wrappers.md
new file mode 100644
index 000000000..9cebadfd2
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/07_technicals-runtime-wrappers.md
@@ -0,0 +1,37 @@
+---
+id: technicals-runtime-wrappers
+title: Runtime Wrappers
+sidebar_label: Runtime Wrappers
+---
+
+## Overview
+
+In general, StreamPipes has an exchangeable runtime layer, e.g., the actual processing of incoming events can be delegated to a third-party stream processing system such as Kafka Streams or Apache Flink.
+
+The default runtime wrapper is the StreamPipes Native Wrapper, called the `StandaloneWrapper`.
+
+Although not recommended for production, we invite interested developers to check out our experimental wrappers:
+
+* Kafka Streams runtime wrapper at [https://github.com/apache/streampipes/tree/dev/streampipes-wrapper-kafka-streams](https://github.com/apache/streampipes/tree/dev/streampipes-wrapper-kafka-streams)
+* Apache Flink runtime wrapper at [https://github.com/apache/streampipes/tree/dev/streampipes-wrapper-flink](https://github.com/apache/streampipes/tree/dev/streampipes-wrapper-flink)
+
+## Assigning a runtime wrapper to an extension service
+
+Runtime wrappers can be assigned in the `Service Definition` of the `Init` class of an extension service:
+
+```java
+
+ @Override
+ public SpServiceDefinition provideServiceDefinition(){
+ return SpServiceDefinitionBuilder.create("org.apache.streampipes.extensions.all.jvm",
+ "StreamPipes Extensions (JVM)",
+ "",8090)
+ ...
+ .registerRuntimeProvider(new StandaloneStreamPipesRuntimeProvider())
+ ...
+ .build();
+ }
+
+```
+
+Please let us know through our communication channels if you are interested in this feature and if you are willing to contribute!
diff --git a/website-v2/versioned_docs/version-0.98.0/07_technicals-user-guidance.md b/website-v2/versioned_docs/version-0.98.0/07_technicals-user-guidance.md
new file mode 100644
index 000000000..697411861
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/07_technicals-user-guidance.md
@@ -0,0 +1,7 @@
+---
+id: technicals-user-guidance
+title: User Guidance
+sidebar_label: User Guidance
+---
+
+tbd
\ No newline at end of file
diff --git a/website-v2/versioned_docs/version-0.98.0/08_debugging.md b/website-v2/versioned_docs/version-0.98.0/08_debugging.md
new file mode 100644
index 000000000..95892c175
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/08_debugging.md
@@ -0,0 +1,7 @@
+---
+id: debugging-debugging
+title: Debugging
+sidebar_label: Debugging
+---
+
+tbd
\ No newline at end of file
diff --git a/website-v2/versioned_docs/version-0.98.0/08_monitoring.md b/website-v2/versioned_docs/version-0.98.0/08_monitoring.md
new file mode 100644
index 000000000..6680b5d86
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/08_monitoring.md
@@ -0,0 +1,7 @@
+---
+id: debugging-monitoring
+title: Monitoring
+sidebar_label: Monitoring
+---
+
+tbd
\ No newline at end of file
diff --git a/website-v2/versioned_docs/version-0.98.0/09_contribute.md b/website-v2/versioned_docs/version-0.98.0/09_contribute.md
new file mode 100644
index 000000000..119568929
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/09_contribute.md
@@ -0,0 +1,17 @@
+---
+id: community-contribute
+title: Contribute
+sidebar_label: Contribute
+---
+
+## Contribute
+
+We welcome contributions to StreamPipes. If you are interested in contributing to StreamPipes, let us know! You'll
+get to know an open-minded and motivated team working together to build the next IIoT analytics toolbox.
+
+Here are some first steps in case you want to contribute:
+* Subscribe to our dev mailing list [dev-subscribe@streampipes.apache.org](mailto:dev-subscribe@streampipes.apache.org)
+* Send an email, tell us about your interests and which parts of Streampipes you'd like to contribute (e.g., core or UI)!
+* Ask for a mentor who helps you to understand the code base and guides you through the first setup steps
+* Find an issue on [GitHub](https://github.com/apache/streampipes/issues) which is tagged with a _good first issue_ tag
+* Have a look at our **developer wiki** at [https://cwiki.apache.org/confluence/display/STREAMPIPES](https://cwiki.apache.org/confluence/display/STREAMPIPES) to learn more about StreamPipes development.
diff --git a/website-v2/versioned_docs/version-0.98.0/09_get-help.md b/website-v2/versioned_docs/version-0.98.0/09_get-help.md
new file mode 100644
index 000000000..0104f6810
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/09_get-help.md
@@ -0,0 +1,25 @@
+---
+id: community-get-help
+title: Get Help
+sidebar_label: Get Help
+---
+
+The Apache StreamPipes community is happy to help with any questions or problems you might have.
+
+## Questions
+Subscribe to our user mailing list to ask a question.
+
+[Mailing Lists](https://streampipes.apache.org/community/mailing-lists/)
+
+To subscribe to the user list, send an email to [users-subscribe@streampipes.apache.org](users-subscribe@streampipes.apache.org)
+
+You can also ask questions on our Github discussions page:
+[Github Discussions](https://github.com/apache/streampipes/discussions)
+
+## Bugs and Feature Requests
+
+If you've found a bug or have a feature that you'd love to see in StreamPipes, feel free to create an issue on [GitHub](https://github.com/apache/streampipes/issues)
+or [discuss your ideas](https://github.com/apache/streampipes/discussions/categories/ideas).
+
+
+
diff --git a/website-v2/versioned_docs/version-0.98.0/faq-common-problems.md b/website-v2/versioned_docs/version-0.98.0/faq-common-problems.md
new file mode 100644
index 000000000..14195c0f0
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/faq-common-problems.md
@@ -0,0 +1,73 @@
+---
+id: faq-common-problems
+title: Common Problems
+sidebar_label: Common Problems
+---
+
+* Windows 10: Consul, Kafka, Zookeeper, or Kafka-Rest did not start
+* Linux / OSX: Consul does not start
+* Run StreamPipes in a VM in Windows
+* Only few processors are available in the pipeline editor
+* No data is shown in the live dashbord
+* Windows 10: Should I use settings windows containers or docker containers?
+* Configurations are not deleted
+* Help us to improve StreamPipes and this documentation
+* Docker Network already used
+
+## Windows 10: Consul, Kafka, Zookeeper, or Kafka-Rest did not start
+**Problem:** You get an error message similar to: `ERROR: for consul Cannot start service consul: b'driver failed programming external connectivity on endpoint sp-test_consul_1 (eae0457fc03c1364b8e81a6e155ca4b95ee1e1d01bb3c1aa9dd5192bdcb7b91a): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:8600:tcp:172.30.0.9:8600: input/output error`
+
+**Solution:** To resolve this problem, stop StreamPipes with `streampipes stop` and restart Docker via the Docker settings in the task bar.
+After Docker was restarted, run `streampipes start`.
+
+## Consul does not start
+**Problem:** After starting StreamPipes with `streampipes start`, there is an error with Consul:
+
+**Solution:** To resolve this, execute `streampipes stop`, wait a minute and start it again with `streampipes start`. If you've installed an old version of StreamPipes (before the installer was available), make sure that no network suffixed with `spnet` exists in Docker. Type `docker network ls` to check and `docker network rm NETWORK_NAME` to remove the existing network before running the installer.
+
+## Run StreamPipes in a VM in Windows
+**Problem:** StreamPipes does not work properly with Docker under Windows 8 or earlier versions.
+
+**Solution:** We do support virtual machines (VMs), but if you run them under Windows, there might be problems with docker and its network configurations.
+Please use Windows 10, OSX or Linux.
+You can also use a VM from a cloud provider to test StreamPipes.
+
+
+## Only few processors are available in the pipeline editor
+**Problem:** In the Pipeline Editor, only a few processors can be used in pipelines.
+
+**Solution:** In the demo/desktop version, we only integrated a few processors. To ensure that you can easily try out StreamPipes (even on your laptop),
+ we tried to make it as lightweight as possible. If you are interested in more sophisticated algorithms, pleas contact us.
+
+
+## No data is shown in the live dashboard
+**Problem:** The live dashboard does not show any data.
+
+**Solution:** If this is the case, your IP is probably configured wrong.
+You can reinstall the system by running `streampipes clean` and then `streampipes start` again.
+This will delete all StreamPipes configurations. StreamPipes is designed as a server application and requires a fixed IP.
+We created a version to easily run it on your laptop and test it, but on your laptop you usually get a new IP when you change the network.
+This problem only occurs in testing scenarios, in production scenarios the IP can also be changed manually without data loss.
+
+## Windows 10: Should I use settings windows containers or docker containers
+**Problem:** StreamPipes does not work with Windows 10.
+
+**Solution:** You should use docker containers. Go to the docker settings on our taks bar and select 'Switch to Docker containers'.
+
+## Configurations are not deleted
+**Problem:** The configurations are not deleted from the host system. Even after manually removing the 'config/' folder StreamPipes settings are note deleted.
+Also the Consul settings are still there.
+
+**Solution:** Probably Docker did not mount a volume in the 'config/' folder. You must delete the anonymous docker volumes manually. See in docker [documentation](https://docs.docker.com/engine/reference/commandline/volume_rm/).
+
+
+## Docker Network already used
+**Problem:** When starting StreamPipes the error message: "Creating network 'streampipes-cli_spnet' with driver 'bridge' Pool overlaps with other one on this address space" is shown.
+
+**Solution:** Delete old networks for example with "docker network prune".
+
+## Help us to improve StreamPipes and this documentation
+Help us to improve this section.
+If you have any problems with the system or with the documentation, do not hesitate to contact us.
+Our goal is to continuously improve StreamPipes.
+Your help and feedback is welcome.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.adapters.image.stream.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.adapters.image.stream.md
new file mode 100644
index 000000000..a03806d9e
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.adapters.image.stream.md
@@ -0,0 +1,38 @@
+---
+id: org.apache.streampipes.connect.adapters.image.stream
+title: Image Upload (Stream)
+sidebar_label: Image Upload (Stream)
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.adapters.image.stream/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+Upload a zip file of images and create an event per image
+
+***
+
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.adapters.iss.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.adapters.iss.md
new file mode 100644
index 000000000..ab27d577d
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.adapters.iss.md
@@ -0,0 +1,39 @@
+---
+id: org.apache.streampipes.connect.adapters.iss
+title: ISS Location
+sidebar_label: ISS Location
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.adapters.iss/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+Shows the live position of the International Space Station (ISS), updated every two seconds.
+
+
+***
+
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.influxdb.stream.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.influxdb.stream.md
new file mode 100644
index 000000000..d01a6ac50
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.influxdb.stream.md
@@ -0,0 +1,41 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.influxdb.stream
+title: InfluxDB Stream Adapter
+sidebar_label: InfluxDB Stream Adapter
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.influxdb.stream/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+Creates a data stream for an InfluxDB measurement.
+
+***
+
+## Configuration
+
+
+
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.iolink.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.iolink.md
new file mode 100644
index 000000000..38363c96e
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.iolink.md
@@ -0,0 +1,90 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.iolink
+title: ifm IOLink
+sidebar_label: ifm IOLink
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.iolink/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+This adapter enables the integration of IO-Link sensor data produced by an ifm IO-Link Master
+(e.g., AL1350) with Apache StreamPipes. To use this adapter, you need to configure your IO-Link
+master to publish events to an MQTT broker. This can be achieved through a REST interface or via
+the browser at `http://##IP_OF_IO_LINK_MASTER##/web/subscribe`. For detailed instructions,
+please refer to the ifm documentation.
+
+### Requirements
+The JSON events should include the following information:
+- `deviceinfo.serialnumber`
+- Only the pdin value is required for each port (e.g., `port[0]`).
+- The event `timer[1].datachanged` can be used as a trigger.
+Using this adapter, you can create a stream for sensors of the same type.
+
+### Restrictions
+This version supports a single IO-Link master. If you want to connect multiple masters, they must have the same setup.
+If you have different requirements, please inform us through the mailing list or GitHub discussions.
+
+***
+
+## Configuration
+
+Here is a list of the configuration parameters you must provide.
+
+### Broker URL
+
+Enter the URL of the broker, including the protocol (e.g. `tcp://10.20.10.3:1883`)
+
+### Access Mode
+
+If necessary, provide broker credentials.
+
+### Ports
+
+Select the ports that are connected to the IO-Link sensors.
+
+### Sensor Type
+
+Choose the type of sensor you want to connect. (**IMPORTANT:** Currently, only the VVB001 is supported)
+
+## Output
+
+The output includes all values from the selected sensor type. Here is an example for the `VVB001 sensor`:
+```
+{
+ "aPeak": 6.6,
+ "aRms": 1.8,
+ "crest": 3.7,
+ "out1": true,
+ "out2": true,
+ "port": "000000001234",
+ "status": 0,
+ "temperature": 22,
+ "timestamp": 1685525380729,
+ "vRms": 0.0023
+}
+```
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.netio.mqtt.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.netio.mqtt.md
new file mode 100644
index 000000000..80cb04156
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.netio.mqtt.md
@@ -0,0 +1,64 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.netio.mqtt
+title: NETIO MQTT M2M
+sidebar_label: NETIO MQTT M2M
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.netio.mqtt/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+Connect Robots running on ROS
+
+
+***
+
+## Required input
+
+This sink does not have any requirements and works with any incoming event type.
+
+***
+
+## Configuration
+
+Describe the configuration parameters here
+
+### Ros Bridge
+
+Example: test-server.com (No protocol)
+
+### Port
+
+The port of the ROS instance.
+
+### Topic
+
+Example: /battery (Starts with /)
+
+
+## Output
+
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.netio.rest.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.netio.rest.md
new file mode 100644
index 000000000..83c741ecc
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.netio.rest.md
@@ -0,0 +1,64 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.netio.rest
+title: NETIO http JSON
+sidebar_label: NETIO http JSON
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.netio.rest/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+Connect Robots running on ROS
+
+
+***
+
+## Required input
+
+This sink does not have any requirements and works with any incoming event type.
+
+***
+
+## Configuration
+
+Describe the configuration parameters here
+
+### Ros Bridge
+
+Example: test-server.com (No protocol)
+
+### Port
+
+The port of the ROS instance.
+
+### Topic
+
+Example: /battery (Starts with /)
+
+
+## Output
+
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.oi4.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.oi4.md
new file mode 100644
index 000000000..1621d8702
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.oi4.md
@@ -0,0 +1,88 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.oi4
+title: OI4
+sidebar_label: OI4
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+# Open Industry 4.0 (OI4)
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.oi4/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+---
+
+
+
+The OI4 adapter facilitates the integration of any OT-device compliant with the OI4 standard into Apache StreamPipes.
+For detailed information about this standard, please refer to their [development guide](https://openindustry4.com/fileadmin/Dateien/Downloads/OEC_Development_Guideline_V1.1.1.pdf).
+
+### Requirements
+
+Your OI4-compatible device should emit data via an MQTT broker.
+
+### Restrictions
+
+This adapter exclusively allows data consumption from a specific MQTT topic.
+If you have different requirements, please notify us through the mailing list or GitHub discussions.
+
+---
+
+## Configuration
+
+Below is a list of the configuration parameters you need to provide.
+
+### Broker URL
+
+Enter the URL of the broker, including the protocol and port number (e.g., `tcp://10.20.10.3:1883`).
+
+### Access Mode
+
+Choose between unauthenticated access or input your credentials for authenticated access.
+
+### Sensor Description
+
+You should provide information about the sensor you want to connect to. This can be achieved in two ways:
+
+a) **By Type**: Specify the type of sensor you want to connect to, e.g., `'VVB001'`. <\br>
+b) **By IODD**: Simply upload the IODD description of the respective sensor. Please note: This feature is not yet available! If you're interested in this feature, please notify us through the mailing list or GitHub discussions and share your use case with us.
+
+### Selected Sensors
+
+Configure which sensors of the master device you want to connect to. You can either select `All`, which will provide data from all sensors available on the respective MQTT topic, or choose `Custom Selection` and provide a list of sensor IDs in a comma-separated string (e.g., `000008740649,000008740672`).
+
+## Output
+
+The output consists of all values from the selected sensor type. Below is an example for the `VVB001 sensor`:
+
+```json
+{
+ "a-Rms": 1.8,
+ "OUT2": true,
+ "SensorID": "000008740649",
+ "Temperature": 22,
+ "Crest": 3.7,
+ "v-Rms": 0.0023,
+ "OUT1": true,
+ "Device status": 0,
+ "timestamp": 1685525380729
+}
+```
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.opcua.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.opcua.md
new file mode 100644
index 000000000..76a65ca55
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.opcua.md
@@ -0,0 +1,76 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.opcua
+title: OPC UA
+sidebar_label: OPC UA
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.opcua/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+Reads values from an OPC-UA server repeatedly
+
+***
+
+## Required Input
+
+***
+
+## Configuration
+
+### Polling Interval
+
+Duration of the polling interval in seconds
+
+### Anonymous vs. Username/Password
+
+Choose whether you want to connect anonymously or authenticate using your credentials.
+
+ **Anonymous**: No further information required <br/>
+ **Username/Password**: Insert your `username` and `password` to access the OPC UA server
+
+### OPC UA Server
+
+Where can the OPC UA server be found?
+
+ **URL**: Specify the server's full `URL` (including port), can be with our without leading `opc.tcp://`<br/>
+ **Host/Port**: Insert the `host` address (with or without leading `opc.tcp://`) and the `port`<br/>
+
+### Namespace Index
+
+Requires the index of the namespace you want to connect to.
+
+### Node ID
+
+The identifier of the node you want to read from, numbers and strings are both valid.
+
+### Available Nodes
+
+Shows all available nodes once namespace index and node ID are given.
+Select as much as you like to query.
+
+***
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.ab-eth.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.ab-eth.md
new file mode 100644
index 000000000..5986afdf9
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.ab-eth.md
@@ -0,0 +1,100 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.plc4x.generic.ab-eth
+title: Allen Bradley ETH
+sidebar_label: Allen Bradley ETH
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.ab-eth/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The adapter allows to connect devices supporting Allen Bradley ETH.
+
+***
+
+## Configuration
+
+The following configuration options are available when creating an adapter:
+
+### PLC Address
+
+This field requires the PLC address in form of the IP without the prefixed protocol (e.g., 192.168.34.56).
+
+### Polling Interval
+
+The polling interval requires a number in milliseconds, which represents the interval in which the adapter will poll the
+PLC for new data. For instance, a polling interval of 1000 milliseconds will configure the adapter to send a request to
+the PLC every second.
+
+### Supported Transports
+
+The following transports are supported by this adapter:
+
+* tcp
+
+### Transport Metadata
+
+#### Required
+
+**tcp**
+
+
+
+#### Advanced
+
+**tcp**
+
+* keep-alive: Should keep-alive packets be sent? (BOOLEAN)
+* no-delay: Should packets be sent instantly or should we give the OS some time to aggregate data. (BOOLEAN)
+* default-timeout: Timeout after which a connection will be treated as disconnected. (INT)
+
+### Protocol Metadata
+
+#### Required
+
+
+
+#### Optional
+
+* station: Id of the station we want to connect to (INT)
+
+### Tags
+
+The syntax to define tags is based on the PLC4X syntax, see https://plc4x.apache.org/users/protocols/s7.html.
+Address Pattern:
+
+```
+propertyName=%{Memory-Area}{start-address}:{Data-Type}[{array-size}]
+
+temperature=%I0.0:INT
+```
+
+## Best Practices
+
+Instead of creating a large event containing all nodes that should be available in StreamPipes, consider to group the
+fields logically into smaller adapters.
+This will ease the definition of pipelines for users and eases future modifications.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.ads.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.ads.md
new file mode 100644
index 000000000..ecf546303
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.ads.md
@@ -0,0 +1,108 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.plc4x.generic.ads
+title: Beckhoff TwinCat ADS
+sidebar_label: Beckhoff TwinCat ADS
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.ads/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The adapter allows to connect devices supporting Beckhoff TwinCat ADS.
+
+***
+
+## Configuration
+
+The following configuration options are available when creating an adapter:
+
+### PLC Address
+
+This field requires the PLC address in form of the IP without the prefixed protocol (e.g., 192.168.34.56).
+
+### Polling Interval
+
+The polling interval requires a number in milliseconds, which represents the interval in which the adapter will poll the
+PLC for new data. For instance, a polling interval of 1000 milliseconds will configure the adapter to send a request to
+the PLC every second.
+
+### Supported Transports
+
+The following transports are supported by this adapter:
+
+* tcp
+
+### Transport Metadata
+
+#### Required
+
+**tcp**
+
+
+
+#### Advanced
+
+**tcp**
+
+* keep-alive: Should keep-alive packets be sent? (BOOLEAN)
+* no-delay: Should packets be sent instantly or should we give the OS some time to aggregate data. (BOOLEAN)
+* default-timeout: Timeout after which a connection will be treated as disconnected. (INT)
+
+### Protocol Metadata
+
+#### Required
+
+* target-ams-net-id: AMS-Net-Id of the target. An AMS-Net-Id has the regular format of an IPv4 IP-Address, however with 6 segments instead of 4. (STRING)
+* target-ams-port: AMS port of the target. (INT)
+* source-ams-net-id: AMS-Net-Id of the source. An AMS-Net-Id has the regular format of an IPv4 IP-Address, however with 6 segments instead of 4. (STRING)
+* source-ams-port: AMS port of the source. (INT)
+
+#### Optional
+
+* target-ams-net-id: AMS-Net-Id of the target. An AMS-Net-Id has the regular format of an IPv4 IP-Address, however with 6 segments instead of 4. (STRING)
+* target-ams-port: AMS port of the target. (INT)
+* source-ams-net-id: AMS-Net-Id of the source. An AMS-Net-Id has the regular format of an IPv4 IP-Address, however with 6 segments instead of 4. (STRING)
+* source-ams-port: AMS port of the source. (INT)
+* timeout-request: Default timeout for all types of requests. (INT)
+* load-symbol-and-data-type-tables: Configures, if when connecting the data-type- and symbol-table should be read. This is an optimization that can help in cases, where the PLC program is pretty large and downloading the full tables is causing problems. When disabled, symbolic addresses will manually be resolved as soon as an address is used. (BOOLEAN)
+
+### Tags
+
+The syntax to define tags is based on the PLC4X syntax, see https://plc4x.apache.org/users/protocols/s7.html.
+Address Pattern:
+
+```
+propertyName=%{Memory-Area}{start-address}:{Data-Type}[{array-size}]
+
+temperature=%I0.0:INT
+```
+
+## Best Practices
+
+Instead of creating a large event containing all nodes that should be available in StreamPipes, consider to group the
+fields logically into smaller adapters.
+This will ease the definition of pipelines for users and eases future modifications.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.bacnet-ip.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.bacnet-ip.md
new file mode 100644
index 000000000..5a50c2b4e
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.bacnet-ip.md
@@ -0,0 +1,102 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.plc4x.generic.bacnet-ip
+title: BACnet/IP
+sidebar_label: BACnet/IP
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.bacnet-ip/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The adapter allows to connect devices supporting BACnet/IP.
+
+***
+
+## Configuration
+
+The following configuration options are available when creating an adapter:
+
+### PLC Address
+
+This field requires the PLC address in form of the IP without the prefixed protocol (e.g., 192.168.34.56).
+
+### Polling Interval
+
+The polling interval requires a number in milliseconds, which represents the interval in which the adapter will poll the
+PLC for new data. For instance, a polling interval of 1000 milliseconds will configure the adapter to send a request to
+the PLC every second.
+
+### Supported Transports
+
+The following transports are supported by this adapter:
+
+* udp
+* tcp
+* pcap
+
+### Transport Metadata
+
+#### Required
+
+**udp**
+
+
+
+#### Advanced
+
+**udp**
+
+* local-port: Some connections require a UDP listener to listen on a fixed port.
+Use this configuration option in order to define the port number of the local port. (INT)
+
+### Protocol Metadata
+
+#### Required
+
+
+
+#### Optional
+
+* ede-file-path: Path to the location of a single EDE file, that contains the descriptor for the target device. (STRING)
+* ede-directory-path: Path to the directory used for storing multiple EDE files. These files contain the descriptors for the possible target devices. (STRING)
+
+### Tags
+
+The syntax to define tags is based on the PLC4X syntax, see https://plc4x.apache.org/users/protocols/s7.html.
+Address Pattern:
+
+```
+propertyName=%{Memory-Area}{start-address}:{Data-Type}[{array-size}]
+
+temperature=%I0.0:INT
+```
+
+## Best Practices
+
+Instead of creating a large event containing all nodes that should be available in StreamPipes, consider to group the
+fields logically into smaller adapters.
+This will ease the definition of pipelines for users and eases future modifications.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.canopen.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.canopen.md
new file mode 100644
index 000000000..ac969d5b9
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.canopen.md
@@ -0,0 +1,100 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.plc4x.generic.canopen
+title: CAN open
+sidebar_label: CAN open
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.canopen/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The adapter allows to connect devices supporting CAN open.
+
+***
+
+## Configuration
+
+The following configuration options are available when creating an adapter:
+
+### PLC Address
+
+This field requires the PLC address in form of the IP without the prefixed protocol (e.g., 192.168.34.56).
+
+### Polling Interval
+
+The polling interval requires a number in milliseconds, which represents the interval in which the adapter will poll the
+PLC for new data. For instance, a polling interval of 1000 milliseconds will configure the adapter to send a request to
+the PLC every second.
+
+### Supported Transports
+
+The following transports are supported by this adapter:
+
+* socketcan
+
+### Transport Metadata
+
+#### Required
+
+**socketcan**
+
+
+
+#### Advanced
+
+**socketcan**
+
+
+
+### Protocol Metadata
+
+#### Required
+
+
+
+#### Optional
+
+* node-id: CAN node identifier. Depending on used CAN version it might be 11 or 29 bit unsigned int. (INT)
+* heartbeat: Forces PLC4X to send CANopen heartbeat (NMT) messages to the bus. (BOOLEAN)
+* request-timeout: Time after which dispatched BUS operation (ie. SDO request) will be marked as failed. (INT)
+
+### Tags
+
+The syntax to define tags is based on the PLC4X syntax, see https://plc4x.apache.org/users/protocols/s7.html.
+Address Pattern:
+
+```
+propertyName=%{Memory-Area}{start-address}:{Data-Type}[{array-size}]
+
+temperature=%I0.0:INT
+```
+
+## Best Practices
+
+Instead of creating a large event containing all nodes that should be available in StreamPipes, consider to group the
+fields logically into smaller adapters.
+This will ease the definition of pipelines for users and eases future modifications.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.eip.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.eip.md
new file mode 100644
index 000000000..f7a18bdb9
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.eip.md
@@ -0,0 +1,102 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.plc4x.generic.eip
+title: EthernetIP
+sidebar_label: EthernetIP
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.eip/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The adapter allows to connect devices supporting EthernetIP.
+
+***
+
+## Configuration
+
+The following configuration options are available when creating an adapter:
+
+### PLC Address
+
+This field requires the PLC address in form of the IP without the prefixed protocol (e.g., 192.168.34.56).
+
+### Polling Interval
+
+The polling interval requires a number in milliseconds, which represents the interval in which the adapter will poll the
+PLC for new data. For instance, a polling interval of 1000 milliseconds will configure the adapter to send a request to
+the PLC every second.
+
+### Supported Transports
+
+The following transports are supported by this adapter:
+
+* tcp
+
+### Transport Metadata
+
+#### Required
+
+**tcp**
+
+
+
+#### Advanced
+
+**tcp**
+
+* keep-alive: Should keep-alive packets be sent? (BOOLEAN)
+* no-delay: Should packets be sent instantly or should we give the OS some time to aggregate data. (BOOLEAN)
+* default-timeout: Timeout after which a connection will be treated as disconnected. (INT)
+
+### Protocol Metadata
+
+#### Required
+
+
+
+#### Optional
+
+* backplane: Without using routing information the backplane defaults to 1. This is overridden if communicationPath is provided. (INT)
+* slot: The slot within the backplane the CPU is located. (INT)
+* bigEndian: Configure if the connection should be set to transport data in Big-Endian format, or not. (BOOLEAN)
+
+### Tags
+
+The syntax to define tags is based on the PLC4X syntax, see https://plc4x.apache.org/users/protocols/s7.html.
+Address Pattern:
+
+```
+propertyName=%{Memory-Area}{start-address}:{Data-Type}[{array-size}]
+
+temperature=%I0.0:INT
+```
+
+## Best Practices
+
+Instead of creating a large event containing all nodes that should be available in StreamPipes, consider to group the
+fields logically into smaller adapters.
+This will ease the definition of pipelines for users and eases future modifications.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.genericcan.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.genericcan.md
new file mode 100644
index 000000000..0195018c7
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.genericcan.md
@@ -0,0 +1,99 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.plc4x.generic.genericcan
+title: Generic CAN
+sidebar_label: Generic CAN
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.genericcan/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The adapter allows to connect devices supporting Generic CAN.
+
+***
+
+## Configuration
+
+The following configuration options are available when creating an adapter:
+
+### PLC Address
+
+This field requires the PLC address in form of the IP without the prefixed protocol (e.g., 192.168.34.56).
+
+### Polling Interval
+
+The polling interval requires a number in milliseconds, which represents the interval in which the adapter will poll the
+PLC for new data. For instance, a polling interval of 1000 milliseconds will configure the adapter to send a request to
+the PLC every second.
+
+### Supported Transports
+
+The following transports are supported by this adapter:
+
+* socketcan
+
+### Transport Metadata
+
+#### Required
+
+**socketcan**
+
+
+
+#### Advanced
+
+**socketcan**
+
+
+
+### Protocol Metadata
+
+#### Required
+
+
+
+#### Optional
+
+* node-id: Node id of the target device. (INT)
+* request-timeout: Default timeout for all types of requests. (INT)
+
+### Tags
+
+The syntax to define tags is based on the PLC4X syntax, see https://plc4x.apache.org/users/protocols/s7.html.
+Address Pattern:
+
+```
+propertyName=%{Memory-Area}{start-address}:{Data-Type}[{array-size}]
+
+temperature=%I0.0:INT
+```
+
+## Best Practices
+
+Instead of creating a large event containing all nodes that should be available in StreamPipes, consider to group the
+fields logically into smaller adapters.
+This will ease the definition of pipelines for users and eases future modifications.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.iec-60870-5-104.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.iec-60870-5-104.md
new file mode 100644
index 000000000..87891175e
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.iec-60870-5-104.md
@@ -0,0 +1,100 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.plc4x.generic.iec-60870-5-104
+title: IEC 60870-5-104
+sidebar_label: IEC 60870-5-104
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.iec-60870-5-104/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The adapter allows to connect devices supporting IEC 60870-5-104.
+
+***
+
+## Configuration
+
+The following configuration options are available when creating an adapter:
+
+### PLC Address
+
+This field requires the PLC address in form of the IP without the prefixed protocol (e.g., 192.168.34.56).
+
+### Polling Interval
+
+The polling interval requires a number in milliseconds, which represents the interval in which the adapter will poll the
+PLC for new data. For instance, a polling interval of 1000 milliseconds will configure the adapter to send a request to
+the PLC every second.
+
+### Supported Transports
+
+The following transports are supported by this adapter:
+
+* tcp
+
+### Transport Metadata
+
+#### Required
+
+**tcp**
+
+
+
+#### Advanced
+
+**tcp**
+
+* keep-alive: Should keep-alive packets be sent? (BOOLEAN)
+* no-delay: Should packets be sent instantly or should we give the OS some time to aggregate data. (BOOLEAN)
+* default-timeout: Timeout after which a connection will be treated as disconnected. (INT)
+
+### Protocol Metadata
+
+#### Required
+
+
+
+#### Optional
+
+* request-timeout: Default timeout for all types of requests. (INT)
+
+### Tags
+
+The syntax to define tags is based on the PLC4X syntax, see https://plc4x.apache.org/users/protocols/s7.html.
+Address Pattern:
+
+```
+propertyName=%{Memory-Area}{start-address}:{Data-Type}[{array-size}]
+
+temperature=%I0.0:INT
+```
+
+## Best Practices
+
+Instead of creating a large event containing all nodes that should be available in StreamPipes, consider to group the
+fields logically into smaller adapters.
+This will ease the definition of pipelines for users and eases future modifications.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.knxnet-ip.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.knxnet-ip.md
new file mode 100644
index 000000000..cd15c4c5b
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.knxnet-ip.md
@@ -0,0 +1,114 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.plc4x.generic.knxnet-ip
+title: KNXNet/IP
+sidebar_label: KNXNet/IP
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.knxnet-ip/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The adapter allows to connect devices supporting KNXNet/IP.
+
+***
+
+## Configuration
+
+The following configuration options are available when creating an adapter:
+
+### PLC Address
+
+This field requires the PLC address in form of the IP without the prefixed protocol (e.g., 192.168.34.56).
+
+### Polling Interval
+
+The polling interval requires a number in milliseconds, which represents the interval in which the adapter will poll the
+PLC for new data. For instance, a polling interval of 1000 milliseconds will configure the adapter to send a request to
+the PLC every second.
+
+### Supported Transports
+
+The following transports are supported by this adapter:
+
+* udp
+* pcap
+* raw
+
+### Transport Metadata
+
+#### Required
+
+**udp**
+
+
+
+#### Advanced
+
+**udp**
+
+* local-port: Some connections require a UDP listener to listen on a fixed port.
+Use this configuration option in order to define the port number of the local port. (INT)
+
+### Protocol Metadata
+
+#### Required
+
+
+
+#### Optional
+
+* knxproj-file-path: Path to the `knxproj` file. The default KNXnet/IP protocol doesn't provide all the information needed to be able to fully decode the messages. (STRING)
+* knxproj-password: Optional password needed to read the knxproj file. (STRING)
+* group-address-num-levels: KNX Addresses can be encoded in multiple ways. Which encoding is used, is too not provided by the protocol itself so it has to be provided externally:
+
+- 3 Levels: {main-group (5 bit)}/{middle-group (3 bit)}/{sub-group (8 bit)}
+- 2 Levels: {main-group (5 bit)}/{sub-group (11 bit)}
+- 1 Level: {sub-group (16 bit)}
+
+The default is 3 levels. If the `knxproj-file-path` this information is provided by the file. (INT)
+* connection-type: Type of connection used to communicate. Possible values are:
+
+- 'LINK_LAYER' (default): The client becomes a participant of the KNX bus and gets it's own individual KNX address.
+- 'RAW': The client gets unmanaged access to the bus (be careful with this)
+- 'BUSMONITOR': The client operates as a busmonitor where he can't actively participate on the bus. Only one 'BUSMONITOR' connection is allowed at the same time on a KNXnet/IP gateway. (STRING)
+
+### Tags
+
+The syntax to define tags is based on the PLC4X syntax, see https://plc4x.apache.org/users/protocols/s7.html.
+Address Pattern:
+
+```
+propertyName=%{Memory-Area}{start-address}:{Data-Type}[{array-size}]
+
+temperature=%I0.0:INT
+```
+
+## Best Practices
+
+Instead of creating a large event containing all nodes that should be available in StreamPipes, consider to group the
+fields logically into smaller adapters.
+This will ease the definition of pipelines for users and eases future modifications.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.logix.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.logix.md
new file mode 100644
index 000000000..65a06979f
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.logix.md
@@ -0,0 +1,105 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.plc4x.generic.logix
+title: Logix CIP
+sidebar_label: Logix CIP
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.logix/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The adapter allows to connect devices supporting Logix CIP.
+
+***
+
+## Configuration
+
+The following configuration options are available when creating an adapter:
+
+### PLC Address
+
+This field requires the PLC address in form of the IP without the prefixed protocol (e.g., 192.168.34.56).
+
+### Polling Interval
+
+The polling interval requires a number in milliseconds, which represents the interval in which the adapter will poll the
+PLC for new data. For instance, a polling interval of 1000 milliseconds will configure the adapter to send a request to
+the PLC every second.
+
+### Supported Transports
+
+The following transports are supported by this adapter:
+
+* tcp
+
+### Transport Metadata
+
+#### Required
+
+**tcp**
+
+
+
+#### Advanced
+
+**tcp**
+
+* keep-alive: Should keep-alive packets be sent? (BOOLEAN)
+* no-delay: Should packets be sent instantly or should we give the OS some time to aggregate data. (BOOLEAN)
+* default-timeout: Timeout after which a connection will be treated as disconnected. (INT)
+
+### Protocol Metadata
+
+#### Required
+
+
+
+#### Optional
+
+* communication-path: The communication path allows for connection routing across multiple backplanes. It uses a common format found in Logix controllers.
+It consists of pairs of values, each pair begins with either 1 (Backplane) or 2 (Ethernet), followed by a slot in the case of a backplane address,
+or if using Ethernet an ip address. e.g. [1,4,2,192.168.0.1,1,1] - Routes to the 4th slot in the first rack, which is a ethernet module, it then connects to the address 192.168.0.1, then finds the module in slot 1. (STRING)
+* backplane: Without using routing information the backplane defaults to 1. This is overridden if communicationPath is provided. (INT)
+* slot: The slot within the backplane the CPU is located. (INT)
+* bigEndian: Configure if the connection should be set to transport data in Big-Endian format, or not. (BOOLEAN)
+
+### Tags
+
+The syntax to define tags is based on the PLC4X syntax, see https://plc4x.apache.org/users/protocols/s7.html.
+Address Pattern:
+
+```
+propertyName=%{Memory-Area}{start-address}:{Data-Type}[{array-size}]
+
+temperature=%I0.0:INT
+```
+
+## Best Practices
+
+Instead of creating a large event containing all nodes that should be available in StreamPipes, consider to group the
+fields logically into smaller adapters.
+This will ease the definition of pipelines for users and eases future modifications.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.modbus-ascii.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.modbus-ascii.md
new file mode 100644
index 000000000..540fddeed
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.modbus-ascii.md
@@ -0,0 +1,102 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.plc4x.generic.modbus-ascii
+title: Modbus ASCII
+sidebar_label: Modbus ASCII
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.modbus-ascii/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The adapter allows to connect devices supporting Modbus ASCII.
+
+***
+
+## Configuration
+
+The following configuration options are available when creating an adapter:
+
+### PLC Address
+
+This field requires the PLC address in form of the IP without the prefixed protocol (e.g., 192.168.34.56).
+
+### Polling Interval
+
+The polling interval requires a number in milliseconds, which represents the interval in which the adapter will poll the
+PLC for new data. For instance, a polling interval of 1000 milliseconds will configure the adapter to send a request to
+the PLC every second.
+
+### Supported Transports
+
+The following transports are supported by this adapter:
+
+* tcp
+* serial
+
+### Transport Metadata
+
+#### Required
+
+**tcp**
+
+
+
+#### Advanced
+
+**tcp**
+
+* keep-alive: Should keep-alive packets be sent? (BOOLEAN)
+* no-delay: Should packets be sent instantly or should we give the OS some time to aggregate data. (BOOLEAN)
+* default-timeout: Timeout after which a connection will be treated as disconnected. (INT)
+
+### Protocol Metadata
+
+#### Required
+
+
+
+#### Optional
+
+* request-timeout: Default timeout for all types of requests. (INT)
+* unit-identifier: Unit-identifier that identifies the target PLC (On RS485 multiple Modbus Devices can be listening). Defaults to 1. (INT)
+
+### Tags
+
+The syntax to define tags is based on the PLC4X syntax, see https://plc4x.apache.org/users/protocols/s7.html.
+Address Pattern:
+
+```
+propertyName=%{Memory-Area}{start-address}:{Data-Type}[{array-size}]
+
+temperature=%I0.0:INT
+```
+
+## Best Practices
+
+Instead of creating a large event containing all nodes that should be available in StreamPipes, consider to group the
+fields logically into smaller adapters.
+This will ease the definition of pipelines for users and eases future modifications.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.modbus-rtu.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.modbus-rtu.md
new file mode 100644
index 000000000..e820a9742
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.modbus-rtu.md
@@ -0,0 +1,102 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.plc4x.generic.modbus-rtu
+title: Modbus RTU
+sidebar_label: Modbus RTU
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.modbus-rtu/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The adapter allows to connect devices supporting Modbus RTU.
+
+***
+
+## Configuration
+
+The following configuration options are available when creating an adapter:
+
+### PLC Address
+
+This field requires the PLC address in form of the IP without the prefixed protocol (e.g., 192.168.34.56).
+
+### Polling Interval
+
+The polling interval requires a number in milliseconds, which represents the interval in which the adapter will poll the
+PLC for new data. For instance, a polling interval of 1000 milliseconds will configure the adapter to send a request to
+the PLC every second.
+
+### Supported Transports
+
+The following transports are supported by this adapter:
+
+* tcp
+* serial
+
+### Transport Metadata
+
+#### Required
+
+**tcp**
+
+
+
+#### Advanced
+
+**tcp**
+
+* keep-alive: Should keep-alive packets be sent? (BOOLEAN)
+* no-delay: Should packets be sent instantly or should we give the OS some time to aggregate data. (BOOLEAN)
+* default-timeout: Timeout after which a connection will be treated as disconnected. (INT)
+
+### Protocol Metadata
+
+#### Required
+
+
+
+#### Optional
+
+* request-timeout: Default timeout for all types of requests. (INT)
+* unit-identifier: Unit-identifier that identifies the target PLC (On RS485 multiple Modbus Devices can be listening). Defaults to 1. (INT)
+
+### Tags
+
+The syntax to define tags is based on the PLC4X syntax, see https://plc4x.apache.org/users/protocols/s7.html.
+Address Pattern:
+
+```
+propertyName=%{Memory-Area}{start-address}:{Data-Type}[{array-size}]
+
+temperature=%I0.0:INT
+```
+
+## Best Practices
+
+Instead of creating a large event containing all nodes that should be available in StreamPipes, consider to group the
+fields logically into smaller adapters.
+This will ease the definition of pipelines for users and eases future modifications.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.modbus-tcp.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.modbus-tcp.md
new file mode 100644
index 000000000..f0071ab46
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.modbus-tcp.md
@@ -0,0 +1,102 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.plc4x.generic.modbus-tcp
+title: Modbus TCP
+sidebar_label: Modbus TCP
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.modbus-tcp/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The adapter allows to connect devices supporting Modbus TCP.
+
+***
+
+## Configuration
+
+The following configuration options are available when creating an adapter:
+
+### PLC Address
+
+This field requires the PLC address in form of the IP without the prefixed protocol (e.g., 192.168.34.56).
+
+### Polling Interval
+
+The polling interval requires a number in milliseconds, which represents the interval in which the adapter will poll the
+PLC for new data. For instance, a polling interval of 1000 milliseconds will configure the adapter to send a request to
+the PLC every second.
+
+### Supported Transports
+
+The following transports are supported by this adapter:
+
+* tcp
+
+### Transport Metadata
+
+#### Required
+
+**tcp**
+
+
+
+#### Advanced
+
+**tcp**
+
+* keep-alive: Should keep-alive packets be sent? (BOOLEAN)
+* no-delay: Should packets be sent instantly or should we give the OS some time to aggregate data. (BOOLEAN)
+* default-timeout: Timeout after which a connection will be treated as disconnected. (INT)
+
+### Protocol Metadata
+
+#### Required
+
+
+
+#### Optional
+
+* request-timeout: Default timeout for all types of requests. (INT)
+* unit-identifier: Unit-identifier that identifies the target PLC (On RS485 multiple Modbus Devices can be listening). Defaults to 1. (INT)
+* ping-address: Simple address, that the driver will use to check, if the connection to a given device is active (Defaults to reading holding-register 1). (STRING)
+
+### Tags
+
+The syntax to define tags is based on the PLC4X syntax, see https://plc4x.apache.org/users/protocols/s7.html.
+Address Pattern:
+
+```
+propertyName=%{Memory-Area}{start-address}:{Data-Type}[{array-size}]
+
+temperature=%I0.0:INT
+```
+
+## Best Practices
+
+Instead of creating a large event containing all nodes that should be available in StreamPipes, consider to group the
+fields logically into smaller adapters.
+This will ease the definition of pipelines for users and eases future modifications.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.open-protocol.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.open-protocol.md
new file mode 100644
index 000000000..b1ed7bdec
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.open-protocol.md
@@ -0,0 +1,100 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.plc4x.generic.open-protocol
+title: Open-Protocol
+sidebar_label: Open-Protocol
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.open-protocol/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The adapter allows to connect devices supporting Open-Protocol.
+
+***
+
+## Configuration
+
+The following configuration options are available when creating an adapter:
+
+### PLC Address
+
+This field requires the PLC address in form of the IP without the prefixed protocol (e.g., 192.168.34.56).
+
+### Polling Interval
+
+The polling interval requires a number in milliseconds, which represents the interval in which the adapter will poll the
+PLC for new data. For instance, a polling interval of 1000 milliseconds will configure the adapter to send a request to
+the PLC every second.
+
+### Supported Transports
+
+The following transports are supported by this adapter:
+
+* tcp
+
+### Transport Metadata
+
+#### Required
+
+**tcp**
+
+
+
+#### Advanced
+
+**tcp**
+
+* keep-alive: Should keep-alive packets be sent? (BOOLEAN)
+* no-delay: Should packets be sent instantly or should we give the OS some time to aggregate data. (BOOLEAN)
+* default-timeout: Timeout after which a connection will be treated as disconnected. (INT)
+
+### Protocol Metadata
+
+#### Required
+
+
+
+#### Optional
+
+
+
+### Tags
+
+The syntax to define tags is based on the PLC4X syntax, see https://plc4x.apache.org/users/protocols/s7.html.
+Address Pattern:
+
+```
+propertyName=%{Memory-Area}{start-address}:{Data-Type}[{array-size}]
+
+temperature=%I0.0:INT
+```
+
+## Best Practices
+
+Instead of creating a large event containing all nodes that should be available in StreamPipes, consider to group the
+fields logically into smaller adapters.
+This will ease the definition of pipelines for users and eases future modifications.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.profinet.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.profinet.md
new file mode 100644
index 000000000..63246e250
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.profinet.md
@@ -0,0 +1,102 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.plc4x.generic.profinet
+title: Profinet
+sidebar_label: Profinet
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.profinet/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The adapter allows to connect devices supporting Profinet.
+
+***
+
+## Configuration
+
+The following configuration options are available when creating an adapter:
+
+### PLC Address
+
+This field requires the PLC address in form of the IP without the prefixed protocol (e.g., 192.168.34.56).
+
+### Polling Interval
+
+The polling interval requires a number in milliseconds, which represents the interval in which the adapter will poll the
+PLC for new data. For instance, a polling interval of 1000 milliseconds will configure the adapter to send a request to
+the PLC every second.
+
+### Supported Transports
+
+The following transports are supported by this adapter:
+
+* raw
+
+### Transport Metadata
+
+#### Required
+
+**raw**
+
+
+
+#### Advanced
+
+**raw**
+
+* resolve-mac-address: If set to true, the transport will automatically resolve the MAC address for a given IP address (Allows connecting to a raw-socket device using the devices host-name or ip-address). (BOOLEAN)
+* support-vlans: Should VLan packets be automatically unpacked? (BOOLEAN)
+* protocol-id: When provided, filters all packets to let only packets matching this ethernet protocol-id pass. (INT)
+
+### Protocol Metadata
+
+#### Required
+
+* gsd-directory: (STRING)
+
+#### Optional
+
+* gsd-directory: (STRING)
+* dap-id: (STRING)
+* ip-address: (STRING)
+
+### Tags
+
+The syntax to define tags is based on the PLC4X syntax, see https://plc4x.apache.org/users/protocols/s7.html.
+Address Pattern:
+
+```
+propertyName=%{Memory-Area}{start-address}:{Data-Type}[{array-size}]
+
+temperature=%I0.0:INT
+```
+
+## Best Practices
+
+Instead of creating a large event containing all nodes that should be available in StreamPipes, consider to group the
+fields logically into smaller adapters.
+This will ease the definition of pipelines for users and eases future modifications.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.s7.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.s7.md
new file mode 100644
index 000000000..6669f47a3
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.s7.md
@@ -0,0 +1,119 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.plc4x.generic.s7
+title: Siemens S7 (Basic)
+sidebar_label: Siemens S7 (Basic)
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.plc4x.generic.s7/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The adapter allows to connect devices supporting Siemens S7 (Basic).
+
+***
+
+## Configuration
+
+The following configuration options are available when creating an adapter:
+
+### PLC Address
+
+This field requires the PLC address in form of the IP without the prefixed protocol (e.g., 192.168.34.56).
+
+### Polling Interval
+
+The polling interval requires a number in milliseconds, which represents the interval in which the adapter will poll the
+PLC for new data. For instance, a polling interval of 1000 milliseconds will configure the adapter to send a request to
+the PLC every second.
+
+### Supported Transports
+
+The following transports are supported by this adapter:
+
+* tcp
+
+### Transport Metadata
+
+#### Required
+
+**tcp**
+
+
+
+#### Advanced
+
+**tcp**
+
+* keep-alive: Should keep-alive packets be sent? (BOOLEAN)
+* no-delay: Should packets be sent instantly or should we give the OS some time to aggregate data. (BOOLEAN)
+* default-timeout: Timeout after which a connection will be treated as disconnected. (INT)
+
+### Protocol Metadata
+
+#### Required
+
+
+
+#### Optional
+
+* local-rack: Rack value for the client (PLC4X device). (INT)
+* local-slot: Slot value for the client (PLC4X device). (INT)
+* local-tsap: Local Transport Service Access Point. (INT)
+* remote-rack: Rack value for the remote main CPU (PLC). (INT)
+* remote-slot: Slot value for the remote main CPU (PLC). (INT)
+* remote-rack2: Rack value for the remote secondary CPU (PLC). (INT)
+* remote-slot2: Slot value for the remote secondary CPU (PLC). (INT)
+* remote-tsap: Remote Transport Service Access Point. (INT)
+* pdu-size: Maximum size of a data-packet sent to and received from the remote PLC. During the connection process both parties will negotiate a maximum size both parties can work with and is equal or smaller than the given value is used. The driver will automatically split up large requests to not exceed this value in a request or expected response. (INT)
+* max-amq-caller: Maximum number of unconfirmed requests the PLC will accept in parallel before discarding with errors. This parameter also will be negotiated during the connection process and the maximum both parties can work with and is equal or smaller than the given value is used. The driver will automatically take care not exceeding this value while processing requests. Too many requests can cause a growing queue. (INT)
+* max-amq-callee: Maximum number of unconfirmed responses or requests PLC4X will accept in parallel before discarding with errors. This option is available for completeness and is correctly handled out during the connection process, however it is currently not enforced on PLC4Xβs side. So if a PLC would send more messages than agreed upon, these would still be processed. (INT)
+* controller-type: As part of the connection process, usually the PLC4X S7 driver would try to identify the remote device. However some devices seem to have problems with this and hang up or cause other problems. In such a case, providing the controller-type will skip the identification process and hereby avoid this type of problem. Possible values are:/n- S7_300
+- S7_400
+- S7_1200
+- S7-1500
+- LOGO (STRING)
+* read-timeout: This is the maximum waiting time for reading on the TCP channel. As there is no traffic, it must be assumed that the connection with the interlocutor was lost and it must be restarted. When the channel is closed, the "fail over" is carried out in case of having the secondary channel, or it is expected that it will be restored automatically, which is done every 4 seconds. (INT)
+* ping: Time for supervision of TCP channels. If the channel is not active, a safe stop of the EventLoop must be performed, to ensure that no additional tasks are created. (BOOLEAN)
+* ping-time: If your application requires sampling times greater than the set "read-timeout" time, it is important that the PING option is activated, this will prevent the TCP channel from being closed unnecessarily. (INT)
+* retry-time: Time value in seconds at which the execution of the PING will be scheduled. Generally set by developer experience, but generally should be the same as (read-timeout / 2). (INT)
+
+### Tags
+
+The syntax to define tags is based on the PLC4X syntax, see https://plc4x.apache.org/users/protocols/s7.html.
+Address Pattern:
+
+```
+propertyName=%{Memory-Area}{start-address}:{Data-Type}[{array-size}]
+
+temperature=%I0.0:INT
+```
+
+## Best Practices
+
+Instead of creating a large event containing all nodes that should be available in StreamPipes, consider to group the
+fields logically into smaller adapters.
+This will ease the definition of pipelines for users and eases future modifications.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.modbus.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.modbus.md
new file mode 100644
index 000000000..4239ba8b3
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.modbus.md
@@ -0,0 +1,75 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.plc4x.modbus
+title: PLC4X MODBUS
+sidebar_label: PLC4X MODBUS
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.plc4x.modbus/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The Modbus adapter allows to connect to a PLC using the Modbus specification.
+
+***
+
+## Configuration
+
+The following configuration options are available when creating the adapter:
+
+### PLC Address
+
+The IP address of the Modbus device without any prefix, which will be added automatically when creating the adapter.
+
+### PLC Port
+
+The PLC port refers to the port of the PLC, such as 502.
+
+### Node ID
+
+The Node ID refers to the ID of the specific device.
+
+### Nodes
+
+The `Nodes` section requires configuration options for the individual nodes.
+Nodes can be either imported from a comma-separated CSV file, or can be directly assigned in the configuration menu.
+
+The following fields must be provided for each node:
+
+* Runtime Name: Refers to the field to internally identify the node, e.g., in the data explorer or pipeline editor.
+* Node Address: Refers to the address of the Node in Modbus, e.g., 1
+* Object Type: Can be selected from the available options `DiscreteInput`, `Coil`, `InputRegister`,
+ or `HoldingRegister`.
+
+An example CSV file looks as follows:
+
+```
+Runtime Name,Node Address,Object Type,
+field1,1,Coil
+temperature,2,Coil
+```
+
+Note that the CSV header must exactly match the titles `Runtime Name`, `Node Address` and `Object Type`.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.s7.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.s7.md
new file mode 100644
index 000000000..9e22be6df
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.plc4x.s7.md
@@ -0,0 +1,96 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.plc4x.s7
+title: PLC4X S7
+sidebar_label: PLC4X S7
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.plc4x.s7/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The adapter allows to connect with a Siemens S7 PLC.
+
+***
+
+## Configuration
+
+The following configuration options are available when creating an adapter:
+
+### PLC Address
+
+This field requires the PLC address in form of the IP without the prefixed protocol (e.g., 192.168.34.56).
+
+In addition to the pure IP, other parameters supported by Apache PLC4X can be provided as an URL parameter:
+
+* `local-rack`
+* `local-slot`
+* `local-tsap`
+* `remote-rack`
+* `remote-slot`
+
+Additional configs are separated by `&`.
+
+Example address: `192.68.34.56?remote-rack=0&remote-slot=3&controller-type=S7_400`
+
+See the <a href="https://plc4x.apache.org/users/protocols/s7.html">Apache PLC4X documentation</a> for more information.
+
+### Polling Interval
+
+The polling interval requires a number in milliseconds, which represents the interval in which the adapter will poll the
+PLC for new data. For instance, a polling interval of 1000 milliseconds will configure the adapter to send a request to
+the PLC every second.
+
+### Nodes
+
+In the Nodes section, the PLC nodes that should be gathered are defined.
+There are two options to define the nodes:
+
+* Manual configuration: The address must be assigned manually by providing a runtime name, the node name and the
+ datatype. The `Runtime Name` will be the StreamPipes-internal name of the field, which will also show up in the data
+ explorer and pipeline editor. The `Node Name` refers to the node address of the PLC, e.g., `%Q0.4`. Finally, the data
+ type can be selected from the available selection. Currently available data types
+ are `Bool`, `Byte`, `Int`, `Word`, `Real`, `Char`, `String`, `Date`, `Time of Day` and `Date and Time`.
+* Instead of providing the node information manually, a CSV file can be uploaded. The CSV file can, for instance, be
+ exported from TIA and then be enriched with the appropriate runtime names. This is especially useful when many fields
+ should be added as nodes. Here is an example export enriched with the runtime name:
+
+```
+Runtime Name,Path,Data Type,Node Name
+I_High_sensor,Tag table_1,Bool,%I0.0,
+I_Low_sensor,Tag table_1,Bool,%I0.1,
+I_Pallet_sensor,Tag table_1,Bool,%I0.2,
+I_Loaded,Tag table_1,Bool,%I0.3,
+```
+
+Note that the CSV can contain additional columns, but only the columns `Runtime Name`, `Data Type` and `Node Name` are
+used, while all other columns will be ignored.
+
+## Best Practices
+
+Instead of creating a large event containing all nodes that should be available in StreamPipes, consider to group the
+fields logically into smaller adapters.
+This will ease the definition of pipelines for users and eases future modifications.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.ros.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.ros.md
new file mode 100644
index 000000000..aeac39947
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.ros.md
@@ -0,0 +1,64 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.ros
+title: ROS Bridge
+sidebar_label: ROS Bridge
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.ros/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+Connect Robots running on ROS
+
+
+***
+
+## Required input
+
+
+
+***
+
+## Configuration
+
+Describe the configuration parameters here
+
+### Ros Bridge
+
+Example: test-server.com (No protocol)
+
+### Port
+
+The port of the ROS instance.
+
+### Topic
+
+Example: /battery (Starts with /)
+
+
+## Output
+
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.simulator.machine.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.simulator.machine.md
new file mode 100644
index 000000000..be0b3bf20
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.adapters.simulator.machine.md
@@ -0,0 +1,92 @@
+---
+id: org.apache.streampipes.connect.iiot.adapters.simulator.machine
+title: Machine Data Simulator
+sidebar_label: Machine Data Simulator
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.adapters.simulator.machine/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+This adapter publishes simulated machine sensor data at a configurable time interval. It is ideal for exploring the
+capabilities of StreamPipes without needing your own data or for testing purposes. Three different sensor scenarios are
+available:
+
+* Flowrate
+* Pressure
+* Water Level
+
+All scenarios include an error or anomaly condition, making them suitable for trend detection, anomaly detection, and
+similar applications.
+
+### Flowrate Sensor
+
+This scenario simulates a flowrate sensor in a piping system, including a sensor defect situation. The generated data
+stream includes:
+
+- **Sensor ID**: The identifier or name of the sensor, such as `sensor01`.
+- **Mass Flow**: Numeric value denoting the current mass flow in the sensor, ranging from 0 to 10.
+- **Volume Flow**: Numeric value denoting the current volume flow, ranging from 0 to 10.
+- **Temperature**: Numeric value denoting the current temperature in degrees Celsius, ranging from 40 to 100.
+- **Density**: Numeric value denoting the current density of the fluid, ranging from 40 to 50.
+- **Sensor Fault Flags**: Boolean indicator of sensor issues.
+
+The sensor defect scenario is as follows: Normally, temperature values range between 40 and 50 degrees Celsius. After
+thirty seconds, the simulation switches to defect mode for another thirty seconds, with temperatures ranging from 80 to
+100 degrees Celsius and `Sensor Fault Flags` set to `true`.
+
+### Pressure Sensor
+
+This scenario simulates a pressure sensor in a gas tank, including an anomaly situation. The generated data stream
+includes:
+
+- **Sensor ID**: The identifier or name of the sensor, such as `sensor01`.
+- **Pressure**: Numeric value denoting the current pressure in the tank, ranging from 10 to 70.
+
+The anomaly scenario is as follows: Normally, pressure values range between 10 and 40. After thirty seconds, the
+simulation switches to anomaly mode for another thirty seconds, with pressure values ranging from 40 to 70.
+
+### Water Level Sensor
+
+This scenario simulates a sensor in a water tank, including an overflow situation. The generated data stream includes:
+
+- **Sensor ID**: The identifier or name of the sensor, such as `sensor01`.
+- **Level**: Numeric value denoting the current water level in the tank, ranging from 20 to 80.
+- **Overflow**: Boolean indicator of tank overflow.
+
+The overflow scenario is as follows: Normally, level values range between 20 and 30. After thirty seconds, the
+simulation switches to overflow mode for another thirty seconds, with level values ranging from 60 to 80 and `Overflow`
+set to `true`.
+
+## Configuration
+
+When creating the adapter, the following parameters can be configured:
+
+- **Wait Time**: The time in milliseconds between two sensor events. Defaults to 1000 (1 second).
+- **Sensor**: Select one of the sensor scenarios described above: `flowrate`, `pressure`, `waterlevel`.
+
+***
\ No newline at end of file
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.file.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.file.md
new file mode 100644
index 000000000..79efd7ca3
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.file.md
@@ -0,0 +1,90 @@
+---
+id: org.apache.streampipes.connect.iiot.protocol.stream.file
+title: File Stream
+sidebar_label: File Stream
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.protocol.stream.file/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+The File Stream Adapter enables continuous streaming of file contents to Apache StreamPipes, creating a data stream for utilization within StreamPipes. It's particularly handy when you prefer not to connect directly to the data source via StreamPipes or for testing and demonstration purposes. Currently, it supports the following file types:
+
+- CSV
+- JSON
+- XML
+
+### Example
+
+Suppose we have a CSV file (`temperature.csv`) containing data from a temperature sensor recording data every second:
+
+```text
+time,temperature
+1715593295000,36.3
+1715593296000,37.5
+1715593297000,37.0
+1715593298000,37.2
+1715593299000,37.2
+1715593210000,37.6
+1715593211000,37.4
+1715593212000,37.5
+1715593213000,37.5
+1715593214000,37.7
+```
+
+When creating a new File Stream Adapter:
+- Upload the file
+- Select `yes` for `Replay Once`
+- Choose `CSV` as the `Format` with `,` as the `delimiter`, check `Header`
+
+After creating the adapter, it will output one line of the CSV as an event every second.
+Further details on configuration options are provided below.
+
+---
+
+## Configuration
+
+### File
+
+This section determines the file to be streamed by the adapter. Options include:
+
+- `Choose existing file`: Select from files already present in StreamPipes.
+- `Upload new file`: Upload a new file, also available for other adapters. Supports `.csv`, `.json`, and `.xml` file types.
+
+### Overwrite file time
+Enable this option to always pass the current system time as the timestamp when emitting an event. If your file lacks timestamp information, this should be enabled. Conversely, if your file has timestamp information, enabling this option will overwrite it with the current system time. By default, this option is disabled, leaving timestamp information unaffected.
+
+### Replay Once
+Distinguishes between replaying all data contained in the file only once or in a loop until the adapter is manually stopped.
+If enabled, this will cause events from the file to be emitted multiple times. In this case, it is recommended to enable `Overwrite file time` if the resulting stream is to be persisted in StreamPipes, otherwise existing events with the same timestamp will be overwritten.
+
+### Replay Speed
+
+Configures the event frequency:
+- **Keep original time**: Events are emitted based on the timestamp information in the file.
+- **Fastest**: All data in the file is replayed as quickly as possible, with no waiting time.
+- **Speed Up Factor**: Adjusts the waiting time of the adapter based on the provided speed up factor, considering the time between two events in the file.
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.http.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.http.md
new file mode 100644
index 000000000..e24df3a09
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.http.md
@@ -0,0 +1,38 @@
+---
+id: org.apache.streampipes.connect.iiot.protocol.stream.http
+title: HTTP Stream
+sidebar_label: HTTP Stream
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.protocol.stream.http/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+Continuously fetched events from an HTTP REST endpoint.
+
+***
+
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.httpserver.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.httpserver.md
new file mode 100644
index 000000000..366b7ccce
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.httpserver.md
@@ -0,0 +1,51 @@
+---
+id: org.apache.streampipes.connect.iiot.protocol.stream.httpserver
+title: HTTP Server
+sidebar_label: HTTP Server
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.protocol.stream.httpserver/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+This adapter provides an HTTP endpoint for ingesting events.
+Data sent to this endpoint via POST requests is transformed into StreamPipes events.
+
+### Configuration
+
+#### Endpoint Appendix
+ Specify the name of the endpoint resource. The endpoint can be accessed at {host of StreamPipes UI}/endpoints/{endpointName}
+
+#### Configuration
+##### Manual
+Provides an option to define the event schema manually.
+
+##### Import from file
+Use a file with example data to automatically detect a first event schema.
+
+***
+
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.kafka.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.kafka.md
new file mode 100644
index 000000000..d2b380f23
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.kafka.md
@@ -0,0 +1,38 @@
+---
+id: org.apache.streampipes.connect.iiot.protocol.stream.kafka
+title: Apache Kafka
+sidebar_label: Apache Kafka
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.protocol.stream.kafka/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+Consumes messages from an Apache Kafka broker
+
+***
+
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.mqtt.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.mqtt.md
new file mode 100644
index 000000000..d3f374c07
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.mqtt.md
@@ -0,0 +1,53 @@
+---
+id: org.apache.streampipes.connect.iiot.protocol.stream.mqtt
+title: MQTT
+sidebar_label: MQTT
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.protocol.stream.mqtt/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+Consumes messages from a broker using the MQTT protocol
+
+
+***
+
+## Configuration
+
+Describe the configuration parameters here
+
+### Broker Url
+
+Example: tcp://test-server.com:1883 (Protocol required. Port required)"
+
+### Access Mode
+
+Unauthenticated or Authenticated (Username/Password)
+
+## Output
+
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.nats.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.nats.md
new file mode 100644
index 000000000..0e43cf54b
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.nats.md
@@ -0,0 +1,69 @@
+---
+id: org.apache.streampipes.connect.iiot.protocol.stream.nats
+title: NATS
+sidebar_label: NATS
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.protocol.stream.nats/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+Consumes events from a NATS broker.
+
+***
+
+## Configuration
+
+### NATS Subject
+
+The subject (topic) where events should be received from. When using wildcard subjects, all messages need to have the same format currently.
+
+### NATS Broker URL
+
+The URL to connect to the NATS broker. It can be provided multiple urls separated by commas(,).
+(e.g., nats://localhost:4222,nats://localhost:4223)
+
+### Username
+
+The username to authenticate the client with NATS broker.
+
+It is an optional configuration.
+
+### NATS Broker URL
+
+The password to authenticate the client with NATS broker.
+
+It is an optional configuration.
+
+### NATS Connection Properties
+
+All other possible connection configurations that the nats client can be created with.
+It can be provided as key value pairs separated by colons(:) and commas(,).
+(e.g., io.nats.client.reconnect.max:1, io.nats.client.timeout:1000)
+
+It is an optional configuration.
+
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.pulsar.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.pulsar.md
new file mode 100644
index 000000000..f9adc56ce
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.pulsar.md
@@ -0,0 +1,38 @@
+---
+id: org.apache.streampipes.connect.iiot.protocol.stream.pulsar
+title: Apache Pulsar
+sidebar_label: Apache Pulsar
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.protocol.stream.pulsar/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+Consumes messages from an Apache Pulsar broker
+
+***
+
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.rocketmq.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.rocketmq.md
new file mode 100644
index 000000000..d6c5cb32d
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.rocketmq.md
@@ -0,0 +1,38 @@
+---
+id: org.apache.streampipes.connect.iiot.protocol.stream.rocketmq
+title: Apache RocketMQ
+sidebar_label: Apache RocketMQ
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.protocol.stream.rocketmq/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+Consumes messages from an Apache RocketMQ broker
+
+***
+
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.tubemq.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.tubemq.md
new file mode 100644
index 000000000..0f321339c
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connect.iiot.protocol.stream.tubemq.md
@@ -0,0 +1,54 @@
+---
+id: org.apache.streampipes.connect.iiot.protocol.stream.tubemq
+title: Apache TubeMQ (InLong)
+sidebar_label: Apache TubeMQ (InLong)
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connect.iiot.protocol.stream.tubemq/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+Consumes messages from an Apache TubeMQ broker.
+
+***
+
+## Configuration
+
+### TubeMQ Master Information
+
+This field describes the endpoints of all the TubeMQ masters.
+
+The format should be like `ip1:port1,ip2:port2,ip3:port3`.
+
+### TubeMQ Topic
+
+The topic where events should be sent to.
+
+### TubeMQ Consumer Group
+
+The consumer group of the TubeMQ Consumer.
+
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connectors.ros.sink.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connectors.ros.sink.md
new file mode 100644
index 000000000..c8416d3ae
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.connectors.ros.sink.md
@@ -0,0 +1,60 @@
+---
+id: org.apache.streampipes.connectors.ros.sink
+title: ROS Bridge Sink
+sidebar_label: ROS Bridge Sink
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.connectors.ros.sink/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+This data sinks can publish events to ROS over websocket.
+
+
+***
+
+## Required input
+
+User-defined parameters include the hostname of the ROS bridge, the port of the ROS instance and the topic.
+
+## Configuration
+
+Describe the configuration parameters here
+
+### Ros Bridge
+
+Example: test-server.com (No protocol)
+
+### Port
+
+The port of the ROS instance.
+
+### Topic
+
+Example: /battery (Starts with /)
+
+
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processor.imageclassification.jvm.generic-image-classification.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processor.imageclassification.jvm.generic-image-classification.md
new file mode 100644
index 000000000..fb42a1a00
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processor.imageclassification.jvm.generic-image-classification.md
@@ -0,0 +1,52 @@
+---
+id: org.apache.streampipes.processor.imageclassification.jvm.generic-image-classification
+title: Generic Image Classification
+sidebar_label: Generic Image Classification
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.processor.imageclassification.jvm.generic-image-classification/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+Image + Classification Description (Generic Model)
+
+***
+
+## Required input
+
+Input events require to have an image field.
+
+***
+
+## Configuration
+
+Describe the configuration parameters here
+
+### Image field
+
+Field that contains the image.
+
+## Output
\ No newline at end of file
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processor.imageclassification.jvm.image-cropper.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processor.imageclassification.jvm.image-cropper.md
new file mode 100644
index 000000000..e2cd6b0e6
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processor.imageclassification.jvm.image-cropper.md
@@ -0,0 +1,43 @@
+---
+id: org.apache.streampipes.processor.imageclassification.jvm.image-cropper
+title: Image Cropper
+sidebar_label: Image Cropper
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.processor.imageclassification.jvm.image-cropper/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+Image Enrichment: Crops an + image based on + given bounding box coordinates
+
+***
+
+## Required input
+An image and an array with bounding boxes.
+A box consists of the x and y coordinates in the image as well as the height and width
+
+## Output
+A new event for each box containing the cropped image
\ No newline at end of file
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processor.imageclassification.jvm.image-enricher.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processor.imageclassification.jvm.image-enricher.md
new file mode 100644
index 000000000..8a09f3ae8
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processor.imageclassification.jvm.image-enricher.md
@@ -0,0 +1,43 @@
+---
+id: org.apache.streampipes.processor.imageclassification.jvm.image-enricher
+title: Image Enricher
+sidebar_label: Image Enricher
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.processor.imageclassification.jvm.image-enricher/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+Image Enrichment: Enriches an + image with + given bounding box coordinates
+
+## Required input
+
+An image and an array with bounding boxes, an array with scores and an array with labels.
+A box consists of the x and y coordinates in the image as well as the height and width, and the classindex with score
+
+## Output
+A new event containing the image with bounding boxes rendered according to the boxes of the input event
\ No newline at end of file
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processor.imageclassification.qrcode.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processor.imageclassification.qrcode.md
new file mode 100644
index 000000000..74f12344f
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processor.imageclassification.qrcode.md
@@ -0,0 +1,68 @@
+---
+id: org.apache.streampipes.processor.imageclassification.qrcode
+title: QR Code Reader
+sidebar_label: QR Code Reader
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.processor.imageclassification.qrcode/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+
+QR Code Reader: Detects a QR Code in an image
+
+***
+
+## Required input
+
+Input events require to have an image field.
+
+***
+
+## Configuration
+
+### Image
+
+Image of the QR code
+
+### Send placeholder value if no qr code is detected
+
+It is a boolean selection.
+
+### Placeholder value
+
+Place holder value
+
+## Output
+
+Outputs a similar event like below.
+
+```
+{
+ 'qrvalue': 'http://githhub.com/',
+ 'timestamp': 1621244783151
+}
+```
\ No newline at end of file
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processors.changedetection.jvm.welford.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processors.changedetection.jvm.welford.md
new file mode 100644
index 000000000..10f95361f
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processors.changedetection.jvm.welford.md
@@ -0,0 +1,72 @@
+---
+id: org.apache.streampipes.processors.changedetection.jvm.welford
+title: Welford Change Detection
+sidebar_label: Welford Change Detection
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<!--
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.processors.changedetection.jvm.welford/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+-->
+
+***
+
+## Description
+
+Performs change detection on a single dimension of the incoming data stream. This implementation tracks the mean and the
+standard deviation using Welford's algorithm, which is well suited for data streams. A change is detected if the
+cumulative deviation from the mean exceeds a certain threshold.
+
+***
+
+## Required input
+
+The welford change dectection processor requires a data stream that has at least one field containing a numerical value.
+
+***
+
+## Configuration
+
+### Value to observe
+
+Specify the dimension of the data stream (e.g. the temperature) on which to perform change detection.
+
+### Parameter `k`
+
+`k` controls the sensitivity of the change detector. Its unit are standard deviations. For an observation `x_n`, the
+Cusum value is `S_n = max(0, S_{n-1} - z-score(x_n) - k)`. Thus, the cusum-score `S` icnreases
+if `S_{n-1} - z-score(x_n) > k`.
+
+### Parameter `h`
+
+The alarm theshold in standard deviations. An alarm occurs if `S_n > h`
+
+## Output
+
+This processor outputs the original data stream plus
+
+- `cumSumLow`: The cumulative sum value for negative changes
+- `cumSumHigh`: The cumulative sum value for positive changes
+- `changeDetectedLow`: Boolean indicating if a negative change was detected
+- `changeDetectedHigh`: Boolean indicating if a positive change was detected
\ No newline at end of file
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processors.enricher.jvm.jseval.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processors.enricher.jvm.jseval.md
new file mode 100644
index 000000000..3fe018306
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processors.enricher.jvm.jseval.md
@@ -0,0 +1,55 @@
+---
+id: org.apache.streampipes.processors.enricher.jvm.jseval
+title: JavaScript Eval
+sidebar_label: JavaScript Eval
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.processors.enricher.jvm.jseval/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+A pipeline element that allows writing user defined JavaScript function to enrich events.
+
+***
+
+## Required input
+This processor does not have any specific input requirements.
+
+***
+
+## Configuration
+User can specify their custom enrichment logic within the `process` method. Please note that the `process` function
+must be in the following format and it must return a map of data which is compatible with the output schema.
+```javascript
+ function process(event) {
+ // do processing here.
+ // return a map with fields that matched defined output schema.
+ return {id: event.id, tempInCelsius: (event.tempInKelvin - 273.15)};
+ }
+```
+
+## Output
+A new event with the user defined output schema.
\ No newline at end of file
diff --git a/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processors.enricher.jvm.processor.expression.md b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processors.enricher.jvm.processor.expression.md
new file mode 100644
index 000000000..1e7dee69f
--- /dev/null
+++ b/website-v2/versioned_docs/version-0.98.0/pe/org.apache.streampipes.processors.enricher.jvm.processor.expression.md
@@ -0,0 +1,61 @@
+---
+id: org.apache.streampipes.processors.enricher.jvm.processor.expression
+title: Math Expression
+sidebar_label: Math Expression
+---
+
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ ~
+ -->
+
+
+
+<p align="center">
+ <img src="/img/pipeline-elements/org.apache.streampipes.processors.enricher.jvm.processor.expression/icon.png" width="150px;" class="pe-image-documentation"/>
+</p>
+
+***
+
+## Description
+A pipeline element that evaluates Math expressions using the Apache Commons JEXL library.
+
+***
+
+## Required input
+This processor works with any input stream that contains numerical values.
+
+***
+
+## Configuration
+A math expression can be defined using the JEXL syntax (see https://commons.apache.org/proper/commons-jexl/index.html).
+
+Example:
+
+```
+flow_rate*2
+```
+
+It is also possible to use methods from `java.lang.Math`:
+
+```
+Math.pow(flow_rate^2)
+```
+
+All fields from th einput stream are available as variables.
+
... 7588 lines suppressed ...