generated from camel.apache.org/component
Update wiki Home page for bonita
parent
1aa3fad153
commit
206836ce55
41
Home.md
41
Home.md
@ -1,21 +1,34 @@
|
||||
# Deploy the Project on CamelX Platform
|
||||
# Bonita
|
||||
|
||||
Deploy on CamelX Platform in three steps
|
||||
Communicate with a remote Bonita BPM process engine.
|
||||
|
||||
## 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 | `bonita` |
|
||||
| Support Level | Stable |
|
||||
| Labels | workflow |
|
||||
| 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-bonita</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 |
|
||||
|------|------|----------|---------|-------------|
|
||||
| `operation` | object | ✓ | | Operation to use |
|
||||
| `hostname` | string | | `localhost` | Hostname where Bonita engine runs |
|
||||
| `port` | string | | `8080` | Port of the server hosting Bonita engine |
|
||||
| `processName` | string | | | Name of the process involved in the operation |
|
||||
| `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. |
|
||||
| `password` | string | | | Password to authenticate to Bonita engine. |
|
||||
| `username` | string | | | Username to authenticate to Bonita engine. |
|
||||
|
||||
Loading…
Reference in New Issue
Block a user