Skip to main content

Invoke two endpoints in same sequence

Scenario: invoke two different endpoints in the same sequence. The first invoke is only for logging purpose and its result has no impact on the rest of the process.

https://docs.wso2.com/display/ESB481/Clone+Mediator

Here's the sample sequence. Here I have used Clone Mediator

<sequence name="sequence1">
<clone>
<target>
<sequence>
<log level="custom">
<property name="LOG_IN_TARGET1" value="target1 called ...."/>
</log>
<property name="OUT_ONLY" value="true" />
<call>
<endpoint key="logAccessEP" />
</call>
</sequence>
</target>
<target>
<sequence>
<log level="custom">
<property name="LOG_IN_TARGET2" value="target2 called ...."/>
</log>
<send>
<endpoint>
<address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
</endpoint>
</send>
</sequence>
</target>
</clone>
</sequence>
view raw WSO2_config_13 hosted with ❤ by GitHub
Use the call mediator instead of send mediator in first target, if you do not expect any response from the endpoint it's good to set the OUT_ONLY property before the call mediator.

<property name="OUT_ONLY" value="true" />
<call>
<endpoint key="logAccessEP" />
</call>
view raw WSO2_config_14 hosted with ❤ by GitHub
https://docs.wso2.com/display/ESB481/Call+Mediator
https://docs.wso2.com/display/ESB481/Generic+Properties#GenericProperties-OUT_ONLY


If you use the Send mediator here, the outSequence will be invok for all the response coming into the ESB.
When the first time outSequence called it invokes logAccessEP endpoint and then logAccessEP returns a reponse to the ESB, then again ESB invokes outSequence and then logAccessEP endpoint .... like wise it goes as a loop.


Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

How to generate random unique number in SOAP UI request

eg 1: ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} eg 2: ${=java.util.UUID.randomUUID()} ${=java.util.UUID.randomUUID()} ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf
Post a Comment
Read more

WSO2 ESB communication with WSO2 ESB Analytics

This blog post is about how & what ports involved when connecting from WSO2 ESB to WSO2 ESB Analytics. How to configure: This document explains how to configure it https://docs.wso2.com/display/ESB500/Prerequisites+to+Publish+Statistics Let's say we have WSO2 ESB  and WSO2 ESB Analytics packs we want to run in same physical machine, then we have to offset one instance.  But we don't want to do that since WSO2 ESB Analytics by default come with the offset. So WSO2ESB will run on 9443 port, WSO2 ESB Analytics will run on 9444 port WSO2 ESB publish data to the WSO2 ESB Analytics via thrift. By default thrift port is 7611 and corresponding ssl thrift port is 7711 (7611+100), check the data-bridge-config.xml file which is in analytics server config directory .  Since we are shipping analytics products with offset 1 then thrift ports are 7612 and ssl port is 7712. Here, ssl port (7712) is used for initial authentication purposes of data publisher ...
Post a Comment
Read more

Tips on using environment variables in WSO2 Integration Cloud

Environment variables allow you to change an application's internal configuration without changing its source code. Let’s say you want to deploy the same application in development, testing  and production environments. Then database related configs and some other internal configurations may change from one environment to another. If we can define these configurations as an environment variables we can easily set those without changing the source code of that application. When you deploy your application in WSO2 Integration Cloud, it lets you define environment variables via the UI. Whenever you change the values of environment variables, you just need to redeploy the application for the changes to take effect. Predefined environment variables Key Concepts - Environment Variables   provides you some predefined set of environment variables which will be useful when deploying applications in WSO2 Integration Cloud. Sample on how to use environment variables ...
Post a Comment
Read more