Skip to content

Using the HTTPS Inbound Endpoint

This sample demonstrates how an HTTPS inbound endpoint can act as a dynamic https listener. Many https listeners can be added without restarting the server. When a message arrives at a port it will bypass the inbound side axis2 layer and will be sent directly to the sequence for mediation.The response also behaves in the same way.

Synapse configuration

Following are the integration artifacts that we can used to implement this scenario. See the instructions on how to build and run this example.

<?xml version="1.0" encoding="UTF-8"?>
<inboundEndpoint name="HttpsListenerEP"
                 suspend="false" sequence="TestIn" onError="fault" >
    <p:parameters xmlns:p="">
        <p:parameter  name="inbound.http.port">8081</p:parameter>
        <p:parameter name="keystore">
        <p:parameter name="truststore">
<?xml version="1.0" encoding="UTF-8"?>
<sequence xmlns="" name="TestIn">
    <send receive="reciveSeq">
            <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
<?xml version="1.0" encoding="UTF-8"?>
<sequence xmlns="" name="reciveSeq">

Build and run

Create the artifacts:

  1. Set up WSO2 Integration Studio.
  2. Create an ESB Solution project
  3. See the instructions on creating mediation sequences to define the two sequences given above ('Sequence 1' and 'Sequence 2').
  4. See the instructions on creating an inbound endpoint to define the inbound endpoint given above.
  5. Deploy the artifacts in your Micro Integrator.

Set up a back-end service for the sample.

Invoke the inbound endpoint.

Analyze the output debug messages for the actions in the dumb client mode. You will see that the Micro Integrator receives a message when the Micro Integrator Inbound is set as the ultimate receiver. You will also see the response from the back end in the client.