Running the Axis2 Server
Samples described in this tutorial involve routing messages to a Web Service
through the Synapse ESB. In real world applications, these Web Services could be
hosted in a web server in your organization, or practiacally anywhere in the
Internet. In this tutorial we will be using a sample Web Service that ships with
Synapse and we will deploy it in the sample Axis2 server that comes bundled with
Synapse.
To deploy the sample service in the Axis2 server, go to
{SYNAPSE_HOME}/samples/axis2Server/src/SimpleStockQuoteService directory and run
'ant'. You will see an output similar to the following as the service is built
and deployed to the sample Axis2 server.
user@domain:/opt/synapse-2.0.0/samples/axis2Server/src/SimpleStockQuoteService$ ant
Buildfile: build.xml
clean:
init:
[mkdir] Created dir: /opt/synapse-2.0.0/samples/axis2Server/src/SimpleStockQuoteService/temp
[mkdir] Created dir: /opt/synapse-2.0.0/samples/axis2Server/src/SimpleStockQuoteService/temp/classes
[mkdir] Created dir: /opt/synapse-2.0.0/samples/axis2Server/repository/services
compile-all:
[javac] Compiling 9 source files to /opt/synapse-2.0.0/samples/axis2Server/src/SimpleStockQuoteService/temp/classes
build-service:
[mkdir] Created dir: /opt/synapse-2.0.0/samples/axis2Server/src/SimpleStockQuoteService/temp/SimpleStockQuote
[mkdir] Created dir: /opt/synapse-2.0.0/samples/axis2Server/src/SimpleStockQuoteService/temp/SimpleStockQuote/META-INF
[copy] Copying 1 file to /opt/synapse-2.0.0/samples/axis2Server/src/SimpleStockQuoteService/temp/SimpleStockQuote/META-INF
[copy] Copying 9 files to /opt/synapse-2.0.0/samples/axis2Server/src/SimpleStockQuoteService/temp/SimpleStockQuote
[jar] Building jar: /opt/synapse-2.0.0/samples/axis2Server/repository/services/SimpleStockQuoteService.aar
BUILD SUCCESSFUL
Total time: 1 second
Now go to {SYNAPSE_HOME}/samples/axis2Server directory and start the sample server
by executing the following command.
Linux / Unix: . axis2server.sh
Windows: axis2server.bat
This will start the Axis2 server on HTTP port 9000. You can see the WSDL of the
sample service by launching your web browser and navigating to the URL
http://localhost:9000/services/SimpleStockQuoteService?wsdl.
Message Mediation
Now we are all set to try our first scenario with Synapse. We will be starting
Synapse using the sample configuration found in synapse_sample_0.xml file which
resides in {SYNAPSE_HOME}/repository/conf/sample directory. This configuration
enables Synapse to log all the messages passing through the service bus:
<definitions xmlns="http://ws.apache.org/ns/synapse">
<sequence name="main">
<log level="full"/>
<send/>
</sequence>
</definitions>
To start the ESB with the above configuration go the {SYNAPSE_HOME}/bin directory
and execute the following command.
Linux / Unix: . synapse.sh -sample 0
Windows: synapse.bat -sample 0
Following messages will be displayed on the console as Synapse boots up with the
above configuration.
Starting Synapse/Java ...
Using SYNAPSE_HOME: /opt/synapse-2.0.0
Using JAVA_HOME: /opt/jdk1.6.0_16
Using SYNAPSE_XML: /opt/synapse-2.0.0/repository/conf/sample/synapse_sample_0.xml
2010-11-26 01:33:03,651 [-] [main] INFO SynapseServer Starting Apache Synapse...
2010-11-26 01:33:03,683 [-] [main] INFO SynapseControllerFactory Using Synapse home : /opt/synapse-2.0.0
2010-11-26 01:33:03,683 [-] [main] INFO SynapseControllerFactory Using Axis2 repository : /opt/synapse-2.0.0/repository
2010-11-26 01:33:03,683 [-] [main] INFO SynapseControllerFactory Using axis2.xml location : /opt/synapse-2.0.0/repository/conf/axis2.xml
2010-11-26 01:33:03,683 [-] [main] INFO SynapseControllerFactory Using synapse.xml location : /opt/synapse-2.0.0/repository/conf/sample/synapse_sample_0.xml
2010-11-26 01:33:03,683 [-] [main] INFO SynapseControllerFactory Using server name : localhost
2010-11-26 01:33:03,698 [-] [main] INFO SynapseControllerFactory The timeout handler will run every : 15s
2010-11-26 01:33:03,808 [-] [main] INFO Axis2SynapseController Initializing Synapse at : Fri Nov 26 01:33:03 IST 2010
2010-11-26 01:33:04,536 [-] [main] ERROR SandeshaModule Could not load module policies. Using default values.
2010-11-26 01:33:04,560 [-] [main] INFO HttpCoreNIOSSLSender Loading Identity Keystore from : lib/identity.jks
2010-11-26 01:33:04,576 [-] [main] INFO HttpCoreNIOSSLSender Loading Trust Keystore from : lib/trust.jks
2010-11-26 01:33:04,668 [-] [main] INFO HttpCoreNIOSender HTTPS Sender starting
2010-11-26 01:33:04,674 [-] [main] INFO HttpCoreNIOSender HTTP Sender starting
2010-11-26 01:33:04,675 [-] [main] INFO JMSSender JMS Sender started
2010-11-26 01:33:04,677 [-] [main] INFO JMSSender JMS Transport Sender initialized...
2010-11-26 01:33:04,681 [-] [main] INFO VFSTransportSender VFS Sender started
2010-11-26 01:33:04,828 [-] [main] WARN JmxAdapter Using unsecured JMX remote access!
2010-11-26 01:33:04,959 [-] [main] INFO HttpCoreNIOSSLListener Loading Identity Keystore from : lib/identity.jks
2010-11-26 01:33:04,961 [-] [main] INFO HttpCoreNIOSSLListener Loading Trust Keystore from : lib/trust.jks
2010-11-26 01:33:04,976 [-] [main] INFO Axis2SynapseController Loading mediator extensions...
2010-11-26 01:33:05,013 [-] [main] INFO XMLConfigurationBuilder Generating the Synapse configuration model by parsing the XML configuration
2010-11-26 01:33:05,114 [-] [main] INFO SynapseConfigurationBuilder Loaded Synapse configuration from : /opt/synapse-2.0.0/repository/conf/sample/synapse_sample_0.xml
2010-11-26 01:33:05,158 [-] [main] INFO Axis2SynapseController Deploying the Synapse service...
2010-11-26 01:33:05,175 [-] [main] INFO Axis2SynapseController Deploying Proxy services...
2010-11-26 01:33:05,175 [-] [main] INFO Axis2SynapseController Deploying EventSources...
2010-11-26 01:33:05,190 [-] [main] INFO MailTransportListener MAILTO Listener started
2010-11-26 01:33:05,212 [-] [main] INFO HttpCoreNIOListener HTTPS Listener started on port : 8243
2010-11-26 01:33:05,215 [-] [main] INFO HttpCoreNIOListener HTTP Listener started on port : 8280
2010-11-26 01:33:05,215 [-] [main] INFO VFSTransportListener VFS Listener started
2010-11-26 01:33:05,215 [-] [main] INFO Axis2SynapseController Management using JMX available via: service:jmx:rmi:///jndi/rmi://hiranya.wso2.com:1099/synapse
2010-11-26 01:33:05,215 [-] [main] INFO ServerManager Server ready for processing...
2010-11-26 01:33:05,216 [-] [main] INFO SynapseServer Apache Synapse started successfully
Note that by default Synapse listens for HTTP requests on port 8280.
Executing the Sample Client
Now we have a Web Service hosted in Axis2 and a Synapse ESB instance which
is configured to log and route messages. All that is left is to send some requests
to Synapse and see the magic happen. Synapse comes bundled with a sample
Web Service client that can be used to send different kinds of requests. Go to
{SYNAPSE_HOME}/samples/axis2Client directory and execute the following command
to send a request to Synapse.
ant stockquote -Daddurl=http://localhost:9000/services/SimpleStockQuoteService -Dtrpurl=http://localhost:8280 -Dmode=quote -Dsymbol=IBM
You should get the following output on the conosle.
Buildfile: build.xml
init:
[mkdir] Created dir: /opt/synapse-2.0.0/samples/axis2Client/target/classes
compile:
[javac] Compiling 22 source files to /opt/synapse-2.0.0/samples/axis2Client/target/classes
[javac] Note: /opt/synapse-2.0.0/samples/axis2Client/src/samples/userguide/PWCallback.java uses or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: /opt/synapse-2.0.0/samples/axis2Client/src/samples/userguide/LoadbalanceFailoverClient.java uses unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
stockquote:
[java] 2010-11-26 01:35:16,414 [-] [main] ERROR SandeshaModule Could not load module policies. Using default values.
[java] 2010-11-26 01:35:16,485 [-] [main] INFO MailTransportSender MAILTO Sender started
[java] 2010-11-26 01:35:16,496 [-] [main] INFO JMSSender JMS Sender started
[java] 2010-11-26 01:35:16,497 [-] [main] INFO JMSSender JMS Transport Sender initialized...
[java] Standard :: Stock price = $99.14593325984416
BUILD SUCCESSFUL
Total time: 5 seconds
This sends a stock quote request for the symbol 'IBM' with the transport URL set
to http://localhost:8280 (Synapse) and the WS-Addressing EPR set to
http://localhost:9000/services/SimpleStockQuoteService (Axis2). Synapse first
logs the message and then forwards it to the URL given in the WS-Addressing
headers. The actual message sent by the client is as follows.
POST / HTTP/1.1
Content-Type: text/xml; charset=UTF-8
SOAPAction: "urn:getQuote"
User-Agent: Axis2
Host: 127.0.0.1
Transfer-Encoding: chunked
218
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header>
<wsa:To>http://localhost:9000/services/SimpleStockQuoteService</wsa:To>
<wsa:MessageID>urn:uuid:D538B21E30B32BB8291177589283717</wsa:MessageID>
<wsa:Action>urn:getQuote</wsa:Action>
</soapenv:Header>
<soapenv:Body>
<m0:getQuote xmlns:m0="http://services.samples">
<m0:request>
<m0:symbol>IBM</m0:symbol>
</m0:request>
</m0:getQuote>
</soapenv:Body>
</soapenv:Envelope>0
Now take a look at the console running Synapse. You will see that all the
details of the mediation are logged along with all the SOAP messages
passed through Synapse. If you execute Synapse in debug mode by editing
the lib/log4j.properties file and setting "log4j.category.org.apache.synapse"
as "DEBUG" instead of INFO, you will see even more information as follows after
a restart and on replay of the above scenario.
2010-11-26 01:39:42,958 [-] [HttpServerWorker-1] DEBUG SynapseMessageReceiver Synapse received a new message for message mediation...
2010-11-26 01:39:42,959 [-] [HttpServerWorker-1] DEBUG SynapseMessageReceiver Received To: http://localhost:9000/services/SimpleStockQuoteService
2010-11-26 01:39:42,959 [-] [HttpServerWorker-1] DEBUG SynapseMessageReceiver SOAPAction: urn:getQuote
2010-11-26 01:39:42,959 [-] [HttpServerWorker-1] DEBUG SynapseMessageReceiver WSA-Action: urn:getQuote
2010-11-26 01:39:42,960 [-] [HttpServerWorker-1] DEBUG Axis2SynapseEnvironment Injecting MessageContext
2010-11-26 01:39:42,960 [-] [HttpServerWorker-1] DEBUG Axis2SynapseEnvironment Using Main Sequence for injected message
2010-11-26 01:39:42,961 [-] [HttpServerWorker-1] DEBUG SequenceMediator Start : Sequence <main>
2010-11-26 01:39:42,961 [-] [HttpServerWorker-1] DEBUG SequenceMediator Sequence <SequenceMediator> :: mediate()
2010-11-26 01:39:42,961 [-] [HttpServerWorker-1] DEBUG LogMediator Start : Log mediator
2010-11-26 01:39:42,989 [-] [HttpServerWorker-1] INFO LogMediator To: http://localhost:9000/services/SimpleStockQuoteService, WSAction: urn:getQuote, SOAPAction: urn:getQuote, ReplyTo: http://www.w3.org/2005/08/addressing/anonymous, MessageID: urn:uuid:881AF81981B97048961290715782743, Direction: request, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:To>http://localhost:9000/services/SimpleStockQuoteService</wsa:To><wsa:MessageID>urn:uuid:881AF81981B97048961290715782743</wsa:MessageID><wsa:Action>urn:getQuote</wsa:Action></soapenv:Header><soapenv:Body><m0:getQuote xmlns:m0="http://services.samples"><m0:request><m0:symbol>IBM</m0:symbol></m0:request></m0:getQuote></soapenv:Body></soapenv:Envelope>
2010-11-26 01:39:42,990 [-] [HttpServerWorker-1] DEBUG LogMediator End : Log mediator
2010-11-26 01:39:42,990 [-] [HttpServerWorker-1] DEBUG SendMediator Start : Send mediator
2010-11-26 01:39:42,990 [-] [HttpServerWorker-1] DEBUG SendMediator Sending request message using implicit message properties..
Sending To: http://localhost:9000/services/SimpleStockQuoteService
SOAPAction: urn:getQuote
2010-11-26 01:39:42,993 [-] [HttpServerWorker-1] DEBUG Axis2FlexibleMEPClient Sending [add = false] [sec = false] [rm = false] [to=Address: http://localhost:9000/services/SimpleStockQuoteService]
2010-11-26 01:39:42,997 [-] [HttpServerWorker-1] DEBUG Axis2FlexibleMEPClient Message [Original Request Message ID : urn:uuid:881AF81981B97048961290715782743] [New Cloned Request Message ID : urn:uuid:5e919190-98a9-4441-8bb0-d09271c2758a]
2010-11-26 01:39:43,003 [-] [HttpServerWorker-1] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the cache
2010-11-26 01:39:43,003 [-] [HttpServerWorker-1] DEBUG MiscellaneousUtil The name with 'synapse.global_timeout_interval' cannot be found. Using default value : 86400000
2010-11-26 01:39:43,004 [-] [HttpServerWorker-1] INFO TimeoutHandler This engine will expire all callbacks after : 86400 seconds, irrespective of the timeout action, after the specified or optional timeout
2010-11-26 01:39:43,004 [-] [HttpServerWorker-1] DEBUG SynapsePropertiesLoader Retrieving synapse properties from the cache
2010-11-26 01:39:43,004 [-] [HttpServerWorker-1] DEBUG MiscellaneousUtil The name with 'synapse.timeout_handler_interval' cannot be found. Using default value : 15000
2010-11-26 01:39:43,039 [-] [HttpServerWorker-1] DEBUG SynapseCallbackReceiver Callback added. Total callbacks waiting for : 1
2010-11-26 01:39:43,144 [-] [HttpServerWorker-1] DEBUG SendMediator End : Send mediator
2010-11-26 01:39:43,145 [-] [HttpServerWorker-1] DEBUG SequenceMediator End : Sequence <main>
2010-11-26 01:39:43,271 [-] [HttpClientWorker-1] DEBUG SynapseCallbackReceiver Callback removed for request message id : urn:uuid:5e919190-98a9-4441-8bb0-d09271c2758a. Pending callbacks count : 0
2010-11-26 01:39:43,271 [-] [HttpClientWorker-1] DEBUG SynapseCallbackReceiver Synapse received an asynchronous response message
2010-11-26 01:39:43,271 [-] [HttpClientWorker-1] DEBUG SynapseCallbackReceiver Received To: null
2010-11-26 01:39:43,271 [-] [HttpClientWorker-1] DEBUG SynapseCallbackReceiver SOAPAction:
2010-11-26 01:39:43,271 [-] [HttpClientWorker-1] DEBUG SynapseCallbackReceiver WSA-Action:
2010-11-26 01:39:43,272 [-] [HttpClientWorker-1] DEBUG SynapseCallbackReceiver Body :
<?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns:getQuoteResponse xmlns:ns="http://services.samples"><ns:return xmlns:ax21="http://services.samples/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ax21:GetQuoteResponse"><ax21:change>-2.533440547346707</ax21:change><ax21:earnings>12.865664096815566</ax21:earnings><ax21:high>-62.37116432061533</ax21:high><ax21:last>63.140427676860845</ax21:last><ax21:lastTradeTimestamp>Fri Nov 26 01:39:43 IST 2010</ax21:lastTradeTimestamp><ax21:low>65.32586424659065</ax21:low><ax21:marketCap>3.6215661345786005E7</ax21:marketCap><ax21:name>IBM Company</ax21:name><ax21:open>64.94029146457328</ax21:open><ax21:peRatio>23.84144924463005</ax21:peRatio><ax21:percentageChange>-3.6037604984655096</ax21:percentageChange><ax21:prevClose>70.29991444840613</ax21:prevClose><ax21:symbol>IBM</ax21:symbol><ax21:volume>9723</ax21:volume></ns:return></ns:getQuoteResponse></soapenv:Body></soapenv:Envelope>
2010-11-26 01:39:43,274 [-] [HttpClientWorker-1] DEBUG Axis2SynapseEnvironment Injecting MessageContext
2010-11-26 01:39:43,274 [-] [HttpClientWorker-1] DEBUG Axis2SynapseEnvironment Using Main Sequence for injected message
2010-11-26 01:39:43,274 [-] [HttpClientWorker-1] DEBUG SequenceMediator Start : Sequence <main>
2010-11-26 01:39:43,275 [-] [HttpClientWorker-1] DEBUG SequenceMediator Sequence <SequenceMediator> :: mediate()
2010-11-26 01:39:43,275 [-] [HttpClientWorker-1] DEBUG LogMediator Start : Log mediator
2010-11-26 01:39:43,275 [-] [HttpClientWorker-1] INFO LogMediator To: http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction: , ReplyTo: http://www.w3.org/2005/08/addressing/anonymous, MessageID: urn:uuid:5e919190-98a9-4441-8bb0-d09271c2758a, Direction: response, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns:getQuoteResponse xmlns:ns="http://services.samples"><ns:return xmlns:ax21="http://services.samples/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ax21:GetQuoteResponse"><ax21:change>-2.533440547346707</ax21:change><ax21:earnings>12.865664096815566</ax21:earnings><ax21:high>-62.37116432061533</ax21:high><ax21:last>63.140427676860845</ax21:last><ax21:lastTradeTimestamp>Fri Nov 26 01:39:43 IST 2010</ax21:lastTradeTimestamp><ax21:low>65.32586424659065</ax21:low><ax21:marketCap>3.6215661345786005E7</ax21:marketCap><ax21:name>IBM Company</ax21:name><ax21:open>64.94029146457328</ax21:open><ax21:peRatio>23.84144924463005</ax21:peRatio><ax21:percentageChange>-3.6037604984655096</ax21:percentageChange><ax21:prevClose>70.29991444840613</ax21:prevClose><ax21:symbol>IBM</ax21:symbol><ax21:volume>9723</ax21:volume></ns:return></ns:getQuoteResponse></soapenv:Body></soapenv:Envelope>
2010-11-26 01:39:43,275 [-] [HttpClientWorker-1] DEBUG LogMediator End : Log mediator
2010-11-26 01:39:43,275 [-] [HttpClientWorker-1] DEBUG SendMediator Start : Send mediator
2010-11-26 01:39:43,275 [-] [HttpClientWorker-1] DEBUG SendMediator Sending response message using implicit message properties..
Sending To: http://www.w3.org/2005/08/addressing/anonymous
SOAPAction:
2010-11-26 01:39:43,282 [-] [HttpClientWorker-1] DEBUG SendMediator End : Send mediator
2010-11-26 01:39:43,282 [-] [HttpClientWorker-1] DEBUG SequenceMediator End : Sequence <main>
And with that you have successfully completed the first part of this guide. Now let's
look at the next scenario, service mediation with proxy services.
Service Mediation (Proxy Services)
As the name implies, a proxy service acts as an intermediary service hosted in
Synapse, and typically fronts an existing service endpoint. A proxy service can be
created and exposed on a different transport, schema, WSDL, or QoS setup (such
as WS-Security, WS-Reliable Messaging) than the real service. Proxy services
are capable of mediating requests before they are delivered to the actual
endpoint. Similarly responses from the actual service can be mediated before
they are sent back to the client.
Clients can send proxy service requests directly to Synapse. From the client's
perspective, proxy services are simply Web Services hosted on Synapse. They can
append the '?wsdl' suffix to the proxy service endpoints to get the WSDLs of these
virtual services. But in the Synapse configuration, service requests can be handled
in anyway you like. Most obvious thing would be to do some processing on the
message and send it to the actual service, which could be running on a different host.
But it is not necessary to always send the messages to an actual service. You may
list any combination of tasks to be performed on the messages received by
the proxy service and terminate the flow or send some response back to the
client even without sending it to any service.
Let's explore a simple proxy services scenario step-by-step to get a better feeling.
As you have downloaded and installed Synapse in the previous section, now you
just run the scenario straightaway. This scenario also requires the same stock
quote service we used in the previous example. So have it deployed in Axis2 and make
sure Axis2 server is up and running.
We are going to start Synapse with a configuration which contains a proxy service.
The configuration in synapse_sample_150.xml file in repository/conf/sample directory
matches well with the scope of this tutorial.
<definitions xmlns="http://synapse.apache.org/ns/2010/04/configuraiton">
<proxy name="StockQuoteProxy">
<target>
<endpoint>
<address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
</endpoint>
<outSequence>
<send/>
</outSequence>
</target>
<publishWSDL uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
</proxy>
</definitions>
The above configuration exposes a proxy service named StockQuoteProxy
and specifies an endpoint
(http://localhost:9000/services/SimpleStockQuoteService) as the target for the
proxy service. Therefore, messages coming to the proxy service will be
directed to the address http://localhost:9000/services/SimpleStockQuoteService
specified in the endpoint. There is also an out sequence for the proxy
service, which will be executed for response messages. In the out sequence,
we just send the messages back to the client. The publishWSDL tag
specifies an WSDL to be published for this proxy service. Let's start
Synapse with this sample configuration by running the below command from
the {SYNAPSE_HOME}/bin directory.
Linux / Unix: . synapse.sh -sample 150
Windows: synapse.bat -sample 150
Synapse will display a set of messages as it boots up just like in the previous
section describing the start-up procedure. Before running the client, it
is time to observe another feature of proxy services. That is displaying
the published WSDL. Just open a web browser and point it to the URL
http://localhost:8280/services/StockQuoteProxy?wsdl. You will see the
sample_proxy_1.wsdl specified in the configuration but containing the
correct EPRs for the service over HTTP/S.
Executing the Sample Client
Now we can invoke the proxy service by sending a request from our sample Axis2
client. Go to the {SYNAPSE_HOME}/samples/axis2Client directory and run the
following command.
ant stockquote -Dtrpurl=http://localhost:8280/services/StockQuoteProxy -Dmode=quote -Dsymbol=IBM
The above command sends a stock quote request directly to the provided
transport endpoint at http://localhost:8280/services/StockQuoteProxy. The
proxy service will forward the message to the Axis2 server and route the
response from Axis2 back to the client. You will see the response from the
server displayed on the console as follows:
Standard :: Stock price = $165.32687331383468
More on Proxy Services
Proxy services are among the most powerful functional components of Apache
Synapse. They can be used to perform transport switching, message format
switching and lot more. This quick start tutorial only covers the simple
usecases of proxy services. Please refer samples #150 and above in the
Synapse samples catalog, for in depth coverage on more advanced use cases.