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">8085</p:parameter>
        <p:parameter name="keystore">
            <KeyStore xmlns="">
        <p:parameter name="truststore">
            <TrustStore xmlns="">
<?xml version="1.0" encoding="UTF-8"?>
<sequence xmlns="" name="TestIn">
            <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>

Build and run

Set up the back-end service:

  1. Download the back-end service.
  2. Extract the downloaded zip file.
  3. Open a terminal, navigate to the axis2Server/bin/ directory inside the extracted folder.
  4. Execute the following command to start the axis2server with the SimpleStockQuote back-end service:


Create the artifacts:

  1. Set up WSO2 Integration Studio.
  2. Create an integration project with an ESB Configs module and an Composite Exporter.
  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.


    Be sure to add an empty namespace for the keystore and truststore elements (xmlns="") in the inbound endpoint as shown above. This is necessary when you run this example in the embedded Micro Integrator of WSO2 Integration Studio.

  5. Deploy the artifacts in your Micro Integrator.

Invoke the inbound endpoint with the below request.


Be sure to add basic auth from the http client you use.

POST https://localhost:8085 HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: "urn:getQuote"
Content-Length: 492
Host: localhost:8290
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
Authorization: Basic YWRtaW46YWRtaW4=

<soapenv:Envelope xmlns:soapenv="" xmlns:ser="http://services.samples" xmlns:xsd="http://services.samples/xsd">
      <ser:getQuote xmlns:ser="http://services.samples" xmlns:xsd="http://services.samples/xsd">

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.