Note that WSO2 EI is shipped with the following changes to what is mentioned in this documentation :
repository/samples/directory that includes all Integration profile samples is changed to
repository/samples/resources/directory that includes all artifacts related to the Integration profile samples is changed to
Objective: Demonstrate the priority based dispatching of NHTTP transport.
- Deploy the
SimpleStockQuoteServicein sample Axis2 server and start it on port 9000. Priority is applied only when ESB is loaded with enough messages to consume its core number of threads. So to observe the priority based dispatching it is required to use a load testing tool like JMeter, SOAP UI or Apache bench.
<EI_HOME>/conf directoryand uncomment the following parameter to the configuration
priorityConfigFile. Set the value to
- Start ESB with the sample configuration 150:
wso2esb-samples.sh -sn 150
In this sample, client should send a HTTP header that specifies the priority of the message. This header name is "priority". This header is retrieved in the priority configuration. Then it is matched against the value 1 and 10. Depending on this value message is executed with priority 1 or 10. Messages with smaller priority number will get higher priority.
Here are two sample XML files that can be used to invoke the service using a tool like JMeter, or Apache Ab. For SOAP user interface, the user can use the WSDL
<EI_HOME>/conf/sample/resources/proxy/sample_proxy_1.wsdl to create the request. The only difference between the two requests demonstrated here is the symbol. One has the symbol as IBM and other has MSFT. For one type of request set the priority header to 1 and for the next set the priority header to 10. Then load ESB with high volume of traffic from both types of requests using the load testing tool. It prints the symbol of the incoming requests in the back end server. User should be able to see more of high priority symbol.