generated from camel.apache.org/component
Update wiki Home page for smooks
parent
ea87866421
commit
f371238ec5
38
Home.md
38
Home.md
@ -1,21 +1,31 @@
|
||||
# Deploy the Project on CamelX Platform
|
||||
# Smooks
|
||||
|
||||
Deploy on CamelX Platform in three steps
|
||||
Use Smooks to transform, route, and bind both XML and non-XML data, including EDI, CSV, JSON, and YAML.
|
||||
|
||||
## 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 | `smooks` |
|
||||
| Support Level | Stable |
|
||||
| Labels | transformation |
|
||||
| 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-smooks</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 |
|
||||
|------|------|----------|---------|-------------|
|
||||
| `smooksConfig` | string | ✓ | | Path to the Smooks configuration file |
|
||||
| `reportPath` | string | | | File path to place the generated HTML execution report. The report is a useful tool in the developers arsenal for diagnosing issues or comprehending a transformation. Do not set in production since this is a major performance drain |
|
||||
| `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. |
|
||||
| `allowExecutionContextFromHeader` | boolean | | `false` | Allow execution context to be set from the CamelSmooksExecutionContext header |
|
||||
|
||||
Loading…
Reference in New Issue
Block a user