Update wiki Home page for ignite-set

Home.md

@@ -1,21 +1,33 @@
-# Deploy the Project on CamelX Platform
+# Ignite Sets
 
-Deploy on CamelX Platform in three steps
+Interact with Ignite Set data structures.
 
-## Step 1: Create a release
-From the project space, click on **"Create a release"**
+## Metadata
 
-The new version is automatically available in the list
+| Property | Value |
+|----------|-------|
+| Scheme | `ignite-set` |
+| Support Level | Stable |
+| Labels | cache,clustering |
+| Version | 4.10.2 |
 
-## Step 2: Deploy
-Click on **"Deploy"**
+## Maven Dependency
 
-- **Version:** Select the desired release
-- **Environment:** Choose `Development`, `Staging`, or `Production` 
-- **Configuration:** Select the configuration source
-- **Resources:** Set CPU and Memory
+```xml
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-ignite</artifactId>
+    <version>4.10.2</version>
+</dependency>
+```
 
-## Step 3: Expose
-Enable **"Expose"**
+## Endpoint Properties
 
-Choose an **API Gateway** (Internal, Public, etc.)
+| Name | Type | Required | Default | Description |
+|------|------|----------|---------|-------------|
+| `name` | string | ✓ |  | The set name. |
+| `configuration` | object |  |  | The collection configuration. Default: empty configuration. You can also conveniently set inner properties by using configuration.xyz=123 options. |
+| `operation` | object |  |  | The operation to invoke on the Ignite Set. Superseded by the IgniteConstants.IGNITE_SETS_OPERATION header in the IN message. Possible values: CONTAINS, ADD, SIZE, REMOVE, ITERATOR, CLEAR, RETAIN_ALL, ARRAY.The set operation to perform. |
+| `propagateIncomingBodyIfNoReturnValue` | boolean |  | `true` | Sets whether to propagate the incoming body if the return type of the underlying Ignite operation is void. |
+| `treatCollectionsAsCacheObjects` | boolean |  | `false` | Sets whether to treat Collections as cache objects or as Collections of items to insert/update/compute, etc. |
+| `lazyStartProducer` | boolean |  | `false` | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |