esb

Where, when and why did you use ESB in a PHP-project? Where, when and why do you think that it would make sense to use ESB in a PHP-project? Does ESB (and ESB-facilitators like Mule) do provide any capability PHP and native LAMP-technologies are lacking? Edit My motivation for this question is stemming from my assumption that you actually never really need Mule. Mule will facilitate communication with external services which you could handle without mule. At the end of the day also Mule will create costs and overhead. So my question is steering at having somebody tell me about scenarios where

How to convert xml to soap message using XSLT in mule? I am using mule community addition so I can't use mule datamapper. Can any one help me how to convert xml to soap message using XSLT tranformation? I have below xml: <file> <header> <documentType>CEN_ORD</documentType> <version>1.0</version> <createDate>01/01/15 02:11</createDate> <originator>IKEA</originator> <timeZone>PST</timeZone> <dateFormat>MM/dd/yy HH:mm</dateFormat> <currencyFormat>USD</currencyFormat> <weightUnits>lbs</weightUnits> <linearUnits>meter</linearUnits> <priceBuCode>158</priceBuCode> <routeBuCode>158</routeBuCode>

I am working on a flow that will, when triggered by an HTTP request, download files from an FTP server. In order to do this on request, instead of on polling, I am using the Mule Requester. I have found that without the requestor, FTP connector will set the "incomingFilename" on the inboundProperties collection for each of the files. When used with the Mule Requester, the filename property is not set, therefore I have no idea what file I am processing... or in this case saving to the file system. In the code below I am using the 'counter' variable for thefilename in the case the the filename

I would like to convert SOAP ws to REST. Is there any elegant solution to this problem? REST should take input in json format. {key:value} This json should be put inside Body/Order/data tags: <soapenv:Body> <myApp:Order> <data>{key:value}</data> </myApp:Order> </soapenv:Body> I guess Mule ESB should be best in doing this. Step 1 : You can expose a rest service via http endpoint which should accept your JSON. Step 2: Then a Custom Transformer can be used to prepare the SOAP request for the SOAP service which needs to be called. Step 3: OutBound Call to SOAP Web-Service Step 4: Transformer to

Is anyone able to indicate if this project ( Managed Service Engine ) has been abandoned? I need to make a decision on whether or not to use this as part of my enterprises service virtualisation plans. I see a number of competing solutions from Microsoft at the moment like AppFabric Server, Olso and custom WCF, but none offer the level of governance like the MSE enables. I do not want to be known as the guy that choose poorly in a year from now when the unified solution appears. If MSE is no longer under development, do you think that by adopting it anyway, solutions built in it will be

I have a running Mule application I am using in my project. What I would like to do is add some component that would clear some database table everytime the Mule server is started up. What would be the component to use in this matter? Preferably I'd like it to happen from XML and not some Java component I have to write (JDBC and such) Thanks! Done with: A notification listener to be informed when Mule is initialized, Implemented in Groovy so all code is in the XML config, A JDBC endpoint to purge the data so no JDBC is needed. Here is the config: <?xml version="1.0" encoding="UTF-8"?> <mule

I have the below route. In unit test, since I doesn't have the FTP server available, I'd like to use camel's test support and send an invalid message to "ftp://hostname/input" and verify that it failed and routed to "ftp://hostname/error" . I gone through the documentation which mainly talks about using the "mock:" endpoint but I am not sure how to use it in this scenario. public class MyRoute extends RouteBuilder { @Override public void configure() { onException(EdiOrderParsingException.class).handled(true).to("ftp://hostname/error"); from("ftp://hostname/input") .bean(new OrderEdiTocXml())

I know theres already a good question on this, but it doesn't really answer what I'm looking for. From what I understand: 1.both are used as a central focal point between applications 2.both can use routing/mediation/transformation etc. between services/apps But the only difference i can really see is that hub and spoke typically have many different formats entering the hub(SOAP/REST/XML/JSON...) while ESB typically has a standard format(Usually just SOAP.) Also I keep reading that hub and spoke introduces a single point of failure compared to an ESB. So is the physical deployment the