Update wiki Home page for jms-pooled-apache-artemis-source

Home.md

@@ -1,21 +1,33 @@
-# Deploy the Project on CamelX Platform
+# JMS Pooled - Apache Artemis Source
 
-Deploy on CamelX Platform in three steps
+Receive data from an Apache Artemis message broker by using JMS Pooled Connection.
 
-## 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 |
+|----------|-------|
+| Type | source |
+| Group | JMS |
+| Namespace | Messaging |
+| Support Level | Stable |
+| Provider | Apache Software Foundation |
 
-## Step 2: Deploy
+## Properties
-Click on **"Deploy"**
 
-- **Version:** Select the desired release
+| Name | Type | Required | Default | Description |
-- **Environment:** Choose `Development`, `Staging`, or `Production` 
+|------|------|----------|---------|-------------|
-- **Configuration:** Select the configuration source
+| `destinationType` | string |  | `queue` | The JMS destination type (queue or topic). |
-- **Resources:** Set CPU and Memory
+| `destinationName` | string | ✓ |  | The JMS destination name. |
+| `brokerURL` | string | ✓ |  | The JMS URL. |
+| `username` | string |  |  | The JMS Broker Username. |
+| `password` | string |  |  | The JMS Broker Password. |
+| `maxSessionsPerConnection` | int |  | `500` | The maximum number of pooled sessions per connection in the pool |
+| `maxIdleSessionsPerConnection` | int |  | `500` | The number of idle sessions allowed per connection before they are closed. |
+| `connectionIdleTimeout` | int |  | `30000` | The maximum time a pooled Connection can sit unused before it is eligible for removal (in milliseconds) |
 
-## Step 3: Expose
+## Dependencies
-Enable **"Expose"**
 
-Choose an **API Gateway** (Internal, Public, etc.)
+- `camel:jms`
+- `camel:kamelet`
+- `mvn:org.apache.activemq:artemis-jakarta-client-all:2.39.0`
+- `mvn:org.messaginghub:pooled-jms:3.1.7`