WSO2 Business Process Server v3.1.0 Documentation

##### Overview

- Home
- Release Note
- WS-BPEL Compliance
- License

##### Downloads

- Releases

##### Installation Guide

- Installing WSO2 BPS

##### Quick Start Guide

- Modeling the process
- Deploying the process
- Testing the process

##### User Guide

- Deploying BPEL Processes
- Deploying Human Tasks
- Managing BPEL processes
- Managing BPEL process instances
- QoS for BPEL processes
- Securing BPEL processes
- Invoking secured partner services
- Versioning
- Management API

##### Human Task Guide

- Human Tasks Quick Start Guide
- Deploying HumanTasks
- Managing Tasks
- Developing a Human Task Artifact
- Human Task Management and Configuration
- Human Task Concepts

##### Administrator Guide

- External data sources Configuration
- Registry Configuration
- Events
- Unified Endpoints
- BPEL Extensions
- Transaction Factory Configuration
- Message Exchange Interceptors
- OpenJPA specific properties
- JMS Transport Configuration
- Process Instance Cleanup Tasks
- Process Hydration and Dehydration
- Enabling Peer-to-Peer(P2P) Communication
- Setting up a BPS Cluster

##### Best Practices

- Process Deployment Best Practices

##### Concepts

- Process Versioning
- Process instance events
- Partner links

##### WS-BPEL Extensions

- Activity Failure and Recovery
- Extension Activities and Extensible Assign Operations
- XPath Extensions
- Iterable ForEach
- Flexible Assigns
- BPEL4People Extension

##### Samples

- HelloWorld
- If-Else
- ForEach
- While
- Repeat Until
- Flow and Links
- Pick
- Synchronous and Asynchronous Service Invocations
- Fault Handling
- Split
- XslTransform
- Compensation Handler
- Event Handler

##### Resources

- FAQ
- External Articles
- Library
- Source Code

##### Community

- Forum
- Mailing Lists

##### Project Information

- Issue Tracking

# Transport Management

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.

Figure: Transport Management Home Page

Transport configurations are saved in the embedded registry and are loaded from there. Please note that WSO2 Carbon also supports the traditional axis2.xml file based transport configuration model. For instance you can override the transport configurations in the registry by specifying the relevant configurations n the [CARBON_HOME]/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.

HTTP and HTTPS transports are configured in the axis2.xml and thus are always loaded at the server startup from the axis2.xml. Also HTTP and HTTPS transports cannot be disabled since those transports are required by the Carbon management console and related administrative services.

To enable a transport listener or a sender simply click on the corresponding Enable link. Then you will be taken to a page where you can specify configuration parameters for the transport listener or the sender you want to enable. You will notice that all the required fields are already populated with a set of default values. Change the default values to suit the requirements of your deployment.

Figure: Transport Configure Form

Once you specify the transport configuration details you can click on the Enable button on the same page to activate the transport listener or the sender. A confirmation dialog will appear and to enable the particular transport click Yes.

Figure: Transport Enable Confirmation Dialog

If any of the dependencies required to enable the transport listener or the sender are missing the transport will not be enabled and you will be redirected back to the Transport Management page. You will notice that the Enable option is still available for that particular transport listener or sender, indicating that it hasn't been enabled. Therefore it is important that you put all the required jars in the [CARBON_HOME]/repository/components/dropins directory before attempting to activate a transport listener or a sender.

Once enabled a given transport can be further configured or disabled. To configure a transport listener or a sender click on the Configure link associated with it in the Transport Management page. Then you will be taken to a page where you can add and edit transport parameters. Once you are satisfied with the configuration click on the Update button to save the changes. The updated settings will take effect immediately and the corresponding transport listener or sender will be restarted.

To disable an already active transport listener or a sender use the Disable links given on the Transport Management page. A confirmation dialog will appear and by clicking on Yes button you can turn off the transport listener or the sender.

Figure: Transport Disable Confirmation Dialog

In case of HTTP/HTTPS transport listeners and senders you will receive a warning dialog indicating that those transports cannot be disabled.