Update wiki Home page for hazelcast-atomicvalue

Home.md

@@ -1,21 +1,33 @@
-# Deploy the Project on CamelX Platform
+# Hazelcast Atomic Number
 
-Deploy on CamelX Platform in three steps
+Increment, decrement, set, etc. Hazelcast atomic number (a grid wide number).
 
-## 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 | `hazelcast-atomicvalue` |
+| Support Level | Stable |
+| Labels | cache,clustering |
+| 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-hazelcast</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 |
+|------|------|----------|---------|-------------|
+| `cacheName` | string | ✓ |  | The name of the cache |
+| `defaultOperation` | object |  |  | To specify a default operation to use, if no operation header has been provided. |
+| `hazelcastConfigUri` | string |  |  | Hazelcast configuration file. |
+| `hazelcastInstance` | object |  |  | The hazelcast instance reference which can be used for hazelcast endpoint. |
+| `hazelcastInstanceName` | string |  |  | The hazelcast instance reference name which can be used for hazelcast endpoint. If you don't specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. |
+| `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. |