esb

WSO2 ESB 4.9.0: what means error 101500

孤街浪徒 提交于 2021-02-10 07:10:27
问题 In a connection to a server we get errors such as: <errorCode>101500</errorCode><errorMessage>Error in Sender</errorMessage> Is there a way to get more information on the cause, except from "Error in Sender"? Note: In the SSL transport sender I have set AllowAll for the HostnameVerifier <transportSender name="https" class="org.apache.synapse.transport.passthru.PassThroughHttpSSLSender"> <parameter name="non-blocking" locked="false">true</parameter> <parameter name="http.proxyHost" locked=

Create and deploy custom mediator in WSO2 ESB

半腔热情 提交于 2021-02-08 11:34:41
问题 I have created custom mediator with Factory and Serializer classes. Created jar with \META-INF\services\ files and put it to dropins folder. But after restart when I deployed test proxy with my mediator, I always get error like this: org.apache.synapse.SynapseException: Unknown mediator referenced by configuration element : at org.apache.synapse.config.xml.MediatorFactoryFinder.getMediator(MediatorFactoryFinder.java:218) It looks like ESB isn't able to find the Factory class. Where is my

Wso2 ESB GET PROXY NAME

感情迁移 提交于 2021-01-28 06:24:38
问题 I would like to know how can I get the name of the proxy in use in a sequence: <proxy xmlns="http://ws.apache.org/ns/synapse" name="PROXYNAME" transports="https,http" statistics="disable" trace="disable" startOnLoad="true"> <target> <inSequence> <property> *GET-NAME OF THIS PROXY...* </property> </inSequence> </target> <publishWSDL uri="http://localhost/Test2/Service.asmx?wsdl" /> </proxy> EDIT In order to get the Name of the proxy (which should be contained in the header 'To' I am trying

Add basicHttpBinding to BizTalk ESB Toolkit WCF Service /ESB.ItineraryServices.WCF/ProcessItinerary.svc

三世轮回 提交于 2021-01-28 03:50:27
问题 Just getting started with the ESB Toolkit 2.0 on BizTalk Server 2009. I can get a .NET client to talk to the ESB Toolkit WCF Service /ESB.ItineraryServices.WCF/ProcessItinerary.svc with no problem at all, however, we use a client technology that cannot process wsHttpBindings at all, it can only see the basicHttpBinding. Does anyone have any idea how to add a basicHttpBinding to the web.config for this service? The web.config is shown below. Many thanks for any help you can provide. Andrew <

Add basicHttpBinding to BizTalk ESB Toolkit WCF Service /ESB.ItineraryServices.WCF/ProcessItinerary.svc

冷暖自知 提交于 2021-01-28 02:53:39
问题 Just getting started with the ESB Toolkit 2.0 on BizTalk Server 2009. I can get a .NET client to talk to the ESB Toolkit WCF Service /ESB.ItineraryServices.WCF/ProcessItinerary.svc with no problem at all, however, we use a client technology that cannot process wsHttpBindings at all, it can only see the basicHttpBinding. Does anyone have any idea how to add a basicHttpBinding to the web.config for this service? The web.config is shown below. Many thanks for any help you can provide. Andrew <

WSO2 EI/ESB: Aggregate mediator for nested Iterate

心不动则不痛 提交于 2020-06-17 13:26:29
问题 I am implementing Iterate mediator inside Iterate mediator. After that, I have an Aggregate mediator in out-sequence. <inSequence> <iterate attachPath="json-eval($.Entity.names)" expression="json-eval($.Entity.names)" id="iterate-over-names" preservePayload="true"> <target> <payloadFactory media-type="json"> <format>[{"value" : 1},{"value" : 2},{"value" : 3},{"value" : 4},{"value" : 5},{"value" : 6},{"value" : 7},{"value" : 8},{"value" : 9}]</format> <args/> </payloadFactory> <iterate

WSO2 EI/ESB: Append payload from Payload Factory to Path Parameter in backend call

僤鯓⒐⒋嵵緔 提交于 2020-06-01 07:41:07
问题 I have a payload factory like below: <payloadFactory media-type="json"> <format>[{"value" : 1},{"value" : 2},{"value" : 3}]</format> <args/> </payloadFactory> <iterate expression="json-eval($)" id="iterate-over-nameAddress"> <call> <endpoint> <http method="get" uri-template="https://backend.com/names/value+{uri.var.value}/address"/> </endpoint> </call> </iterate> In the above code, in backend call, I want the path-parameter " value+{uri.var.value} " to change dynamically according to the