Transport configurations are saved in the embedded registry and loaded from there.
| Info | ||
|---|---|---|
| ||
WSO2 Carbon also supports the traditional axis2.xml file-based transport configuration model. |
You can override the transport configurations in the registry by specifying the relevant configurations in the CARBON_HOME/repository/conf/axis2.xml file. In other words, transport configuration details given in the axis2.xml file gets priority over the transport configuration details saved in the registry. Keep in mind that any changes to axis2.xml file require a server restart to take effect.
| Info | ||
|---|---|---|
| ||
You can configure only enabled transports. |
Follow the instructions below to configure transports.
1. Log on to the Data Services Server Management Console.
2. Click the "Configure" menu and select "Transports" to access "Transport Management."
3. The "Transport Management" page lists the available transport listeners and senders. From here, you can enable, disable and configure transport listeners and senders separately, without having to restart the server (Also refer to Enabling and Disabling Transports).
Click on the "Configure" link of a certain transport listener/sender.
4. You will be taken to a page, where you can #add and #edit transport parameters.
5. Do your configuration and click the "Update" button to save the changes. The updated settings will take effect immediately and the corresponding transport listener or sender will be restarted.
Adding Transport Parameters
| Anchor | ||||
|---|---|---|---|---|
|
1. Enter the parameter's name and click the "Add" button.
2. Edit the parameter's value.
Editing Transport Parameters
| Anchor | ||||
|---|---|---|---|---|
|
You can edit the parameter's value right in the textarea.
