Mule Healthcare Toolkit is a collection of features that facilitates integration with healthcare systems by providing the tools needed to easily create, read and transform HL7 version v2.x messages within Mule... Unfortunately, it is available only for Mule ESB Enterprise!!!
Is there a way to implement a complete messaging service based on HL7 using the Community version of Mule?
Best regards, Vi.
Apache Camel has HL7 components that you can use to create HL7 routes. You could possibly then route this to mule via a web service call or a JMS call being hosted by the Mule ESB for example.
Apache camel does not require a full ESB (it is not a ESB) so it could act as some sort of translator proxy.
Might not be your cup of tea though.
I realize this is an old thread, but it appears that the Mule Healthcare Toolkit uses the open source HAPI library for (at least some of) the HL7 v2 message support. You'd have examine it more closely, but I suspect one could create their own Mule components using HAPI.
http://hl7api.sourceforge.net/
Related
I like to call a flow from another project in Mule. Is that possible.
If its so please provide me the details how it can be achieved?
Thanks in advance.
If they are separate projects(even on the same JVM) then you cannot use flow-ref but will have to use a transport such as JMS, HTTP etc. If you are using Mule 3.5 Enterprise Edition then you can use the VM transport to communicate between projects using the new shared resources and domain functionality. More info on that here: http://www.mulesoft.org/documentation/display/current/Shared+Resources
I have a cluster of Mule ESB containers, each of which is running an (identical) application which share responsibility for handling work which arrives as objects in a Hazelcast Distributed Queue.
Question: What's the best way to have these applications monitor the queue?
Conceptually, I imagine a "Hazelcast Queue Endpoint" that sits blocked on the queue until an object shows up-- but I'm not quite sure how to realize this.
(Mule ESB 3.3, community edition).
Thanks.
I would use DevKit to create a custom a Hazelcast Queue Endpoint and build it as a custom module.
This custom module would be usable in Studio and raw Mule.
I have gone through the documentation of how we can integrate mule esb with mule mq. But i couldn't find any download link for mule MQ. Even i read on mule blog the mule mq is out of market now. Can anybody comment on this.
below are the ref links
http://www.mulesoft.org/documentation-3.2/display/MULE2USER/MuleMQ+Integration
http://forum.mulesoft.org/mulesoft/topics/where_to_get_mule_mq_software
MuleSoft has completely abandoned MuleMQ. Use another message broker, like HornetQ, ActiveMQ or RabbitMQ.
Mule MQ is now totally deprecated.But it provides a seamless integration between various MOM which utilized JMS and other tools.
By default, Mule provides a JMS endpoint that can be used to send and receive messages using JMS API.
We can prefer the queuing vendors based upon two need
1.AMQP
Advanced Message Queuing Protocol,which provides so many advanced features in queue to provide the routing needs.RabbitMQ,ActiveMQ etc..
2.MSMQ
MSMQ is MOM provided by Microsoft as a component.If required it can be enabled from Turn Windows Features On or Off.It doesn't implements much features that AMQP provide.It also doesn't have a topic feature which is available in MSMQ.
I hope this answer helps you.
Thanks and Regards
As of now Mule MQ is discontinued, You can user other third party Queue broker solutions like - RabbitMQ, ActiveMQ.
I've got a streaming UDP application that generates a stream of messages in a legacy format. These messages are generated in an un-solicited fashion (that is, it is not request/response).
I'd like to build a custom message mediator to take these messages into an enterprise network.
Can someone please point me to one or more samples in the WSO2 ESB portfolio that are a good starting point for building a custom mediator?
Any other samples, or examples, to serve as a starting point for a WSO2 ESB novice that needs to develop his first custom mediator would be appreciated.
You can refer these links.
(Creating a project by userself and compile a custom mediator jar)
http://docs.wso2.org/wiki/display/ESB460/Writing+a+WSO2+ESB+Mediator
(Using WSO2 Developer studio)
http://achala11.blogspot.com/2012/12/how-to-write-custom-mediator-wso2-esb.html
We have more than 5 corporate applications running on different servers with technologies like spring, struts communication between these application is point to point. We are planning to migrate this to ESB using Mule.
I didnt quite understand how mule works i have few doubts,
Mule is running in a different server do i need to deploy all my 5 aplications into the mule server.
I have spring application delployed on a tomcat server how this application is going to receive messages through mule or what are the configuration changes i need to do in my server or mule server.
Any advice or tutorials.
You need not deploy all you 5 applications in the Mule Server.
You said that all your application are currently point to point (which means that all are talking/communicating now through http protocol), similarly you can also use mule's http endpoints to communicate with all the 5 applications.
I.e. the spring application talking to another spring application can be modified to Spring application talking to Mule and Mule in turn talking to another Spring application .
You must learn the basics from the Documentation
http://www.mulesoft.org/documentation/display/current/Mule+Fundamentals --> browse through the navigation on the lefthand side.
Mule is an integration tool. you no need to change any of your existing applications. All you need is to develop an mule application which can do the mediation/orchestration.
For connecting with your spring application you no need to change any configuration you need to use http:outbound connector inside your mule flow
Just go through http://www.mulesoft.org/documentation/display/current/HTTP+Transport+Reference
So mule is based on SOA principle, so your 5 corporate service need not to be their in a single system. so if you want to consume the service/functionality of any of your 5 application, expose those service as web service, cloud be soap or rest. And you can call those service inside your mule. so in this case you have to create only 5 connection and where ever required you can refer to those connection inside mule configuration file.
#saravanan shanmugavel you need to use Mule ESB to orchestrate the communication between these application...ESB came into the picture to remove your point to point communication...you can create a proxy service for each of your service and one flow which will orchestrate communication between all...
All you need to do is change the application that is configurable according to mule server.
Please refer below link that will be helpful for understanding of mule that helps you better orchestrate communication between all.
https://docs.mulesoft.com/