...
With this feature, it is possible to inject the parameters by using the $FILE: prefix followed by the relevant key used to map the original value.
Supported parameters
Endpoint parameters
Configure the Endpoint parameters in your synapse configuration as shown below.
| Endpoint Type | Parameters |
|---|---|
| Address Endpoint | uri |
| HTTP Endpoint | uri |
| Loadbalance Endpoint | hostname and port |
| RecipientList Endpoint | hostname and port |
| Template Endpoint | uri |
| WSDL Endpoint | wsdlURI |
Data service parameters
DriverURLUsernamePassword
Scheduled Task parameters
The pinned servers parameter can be set as an environment variable for a scheduled task or proxy service. See the examples given below.
Inbound Endpoint parameters
See the list of properties that can be defined as environment variables:
- HTTP Inbound Protocol
- HTTPS Inbound Protocol
- HL7 Inbound Protocol
- CXF WS-RM Inbound Protocol
- JMS Inbound Protocol
- RabbitMQ Inbound Protocol
Injecting proxy service parameters
The pinned servers parameter as well as all the service-level transport parameters:
Injecting Message Store parameters
| Message Store Type | Parameters |
|---|---|
| JMS Message Store |
|
| WSO2 MB Message Store | |
| RabbitMQ Message Store |
|
| JDBC Message Store |
|
| Resequence Message Store |