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

gitea_admin 2026-03-11 14:37:32 +00:00
parent 78b7e89e9e
commit 96cae2de9b

40
Home.md

@ -1,21 +1,33 @@
# Deploy the Project on CamelX Platform
# JMS Pooled - Apache Artemis Sink
Deploy on CamelX Platform in three steps
Send data to an Apache Artemis message broker by using JMS Pooled
## 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 |
|----------|-------|
| Type | sink |
| Group | JMS |
| Namespace | Messaging |
| Support Level | Stable |
| Provider | Apache Software Foundation |
## Step 2: Deploy
Click on **"Deploy"**
## Properties
- **Version:** Select the desired release
- **Environment:** Choose `Development`, `Staging`, or `Production`
- **Configuration:** Select the configuration source
- **Resources:** Set CPU and Memory
| Name | Type | Required | Default | Description |
|------|------|----------|---------|-------------|
| `destinationType` | string | | `queue` | The JMS destination type (queue or topic). |
| `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
Enable **"Expose"**
## Dependencies
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`