Update wiki Home page for tahu-host

Home.md

@@ -1,21 +1,39 @@
-# Deploy the Project on CamelX Platform
+# Tahu Host Application
 
-Deploy on CamelX Platform in three steps
+Sparkplug B Host Application support over MQTT using Eclipse Tahu
 
-## Step 1: Create a release
+## Metadata
-From the project space, click on **"Create a release"**
 
-The new version is automatically available in the list
+| Property | Value |
+|----------|-------|
+| Scheme | `tahu-host` |
+| Support Level | Stable |
+| Labels | messaging,iot,monitoring |
+| Version | 4.10.2 |
 
-## Step 2: Deploy
+## Maven Dependency
-Click on **"Deploy"**
 
-- **Version:** Select the desired release
+```xml
-- **Environment:** Choose `Development`, `Staging`, or `Production` 
+<dependency>
-- **Configuration:** Select the configuration source
+    <groupId>org.apache.camel</groupId>
-- **Resources:** Set CPU and Memory
+    <artifactId>camel-tahu</artifactId>
+    <version>4.10.2</version>
+</dependency>
+```
 
-## Step 3: Expose
+## Endpoint Properties
-Enable **"Expose"**
 
-Choose an **API Gateway** (Internal, Public, etc.)
+| Name | Type | Required | Default | Description |
+|------|------|----------|---------|-------------|
+| `hostId` | string | ✓ |  | ID for the host application |
+| `checkClientIdLength` | boolean |  | `false` | MQTT client ID length check enabled |
+| `clientId` | string | ✓ |  | MQTT client ID to use for all server definitions, rather than specifying the same one for each. Note that if neither the 'clientId' parameter nor an 'MqttClientId' are defined for an MQTT Server, a random MQTT Client ID will be generated automatically, prefaced with 'Camel' |
+| `keepAliveTimeout` | integer |  | `30` | MQTT connection keep alive timeout, in seconds |
+| `rebirthDebounceDelay` | integer |  | `5000` | Delay before recurring node rebirth messages will be sent |
+| `servers` | string | ✓ |  | MQTT server definitions, given with the following syntax in a comma-separated list: MqttServerName:(MqttClientId:)(tcp/ssl)://hostname(:port),... |
+| `bridgeErrorHandler` | boolean |  | `false` | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
+| `exceptionHandler` | object |  |  | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
+| `exchangePattern` | object |  |  | Sets the exchange pattern when the consumer creates an exchange. |
+| `password` | string |  |  | Password for MQTT server authentication |
+| `sslContextParameters` | object |  |  | SSL configuration for MQTT server connections |
+| `username` | string |  |  | Username for MQTT server authentication |