esb

Is orchestration an ESB responsibility?

风格不统一 提交于 2019-12-04 08:45:03
问题 Is an Enterprise Service Bus (a tool that acts as a mediator, a message broker, a service enabler, schema transformation enhancer, transparent location provider, service aggregator, load balancer, monitor, and all that stuff) responsible to orchestrate services ? What about putting an automated business business process with more than thousand steps and dozens of service invocations inside your enterprise service bus? Would you do it, or would you use a specialist in orchestration such as a

BizTalk 2009 ESB Confusion

做~自己de王妃 提交于 2019-12-04 08:42:47
I have a little experience with BizTalk and am trying to understand BizTalk 2009 ESB Toolkit 2 without using it. Firstly, I am wondering whether anyone can clear up a couple of concepts for me: What is the difference between an "on-ramp" and a "receive port"? Why do you need itineraries, can you not simply create the same using ports and orchestrations? I am obviously missing something here. A couple of more general questions: Do all messages still have to go through the Message Box? Thanks in advance for any insight. On-ramps The on-ramps are web service based receive port but they are a bit

Consume a web service method with multiple args in Mule esb

邮差的信 提交于 2019-12-04 06:22:02
问题 Hello what I want to apply seems very simple but I don't know how, need some clarifications. here is the scenario: I want to call a web service method, this method name is find() and accept as argument an object, the object represent a composed primary key, composed by two strings an id and a type. the object -which is the primary key- representation in soap is : <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsd="http://wsdouane/"> <soapenv:Header/>

WSO2 ESB - writing files out of base64

大兔子大兔子 提交于 2019-12-04 05:29:18
问题 I have a proxy which accepts XML files with Base64 encoded files in it. For example the XML looks like: <message> <content>Hello World</content> <attachements> <attachement>*Base64 code here*</attachement> <attachement>*Base64 code here*</attachement> <attachement>*Base64 code here*</attachement> </attachements> </message> My Problem: I like to save the decoded files from the message into a folder of the filesystem of the server running the ESB. But how can I do this? If I encode a simple

Mule ESB:Context Property Placeholder

早过忘川 提交于 2019-12-04 01:48:58
I have a question regarding Mule's context property placeholder, I have two files set up like this: <context:property-placeholder location="classpath:mule-app-1.properties, file:///etc/mule/conf/mule-app-2.properties" /> Firstly is this a valid configuration, secondly which file will take precedence over the other? app1 or app2 file? -S Each will be loaded in turn, overwriting duplicate properties from the first one. So in your case, properties defined in mule-app-2.properties will take precedence. Towards the end of this article I described using this method to provide environment specific

REST APIs and messaging

|▌冷眼眸甩不掉的悲伤 提交于 2019-12-04 00:45:56
I have a system that exposes a REST API with a rich set of CRUD endpoints to manage different resources. The REST API is used also by a front-end application that executes calls by using Ajax. I would like to make some of these calls asynchronous and add reliability. The obvious choice seems a message broker (ActiveMQ, RabbitMQ, etc...). Never used message brokers before and I am wondering if they can be "put in front of" the REST API without having to rewrite them. I do not want to access the REST API only through the messaging system: for some endpoints, a call must always be synchronous and

EDA/SOA/ESB 的实践摘要-引用

时间秒杀一切 提交于 2019-12-03 23:39:46
引用说明:原文来自于 http://www.ibm.com/developerworks/cn/webservices/1010_wanghq_eda/1010_wanghq_eda.html ,为了方便本人阅读,文本格式略有调整。 EDA/SOA/ESB 的实践摘要 事件驱动架构 (Event-Driven Architecture,EDA) 面向服务架构 (Service-Oriented Architecture, SOA) 是一种 IT 架构策略,其基于面向服务的概念之上 企业服务总线(Enterprise Service Bus, ESB) 消息中间件(Message Oriented Middleware, MOM) 下图是一个证券公司股票交易系统的简图: 图 1. 证券公司股票交易系统概略图 从上图我们可以看出,整个应用被分为很多子系统,各个子系统之间存在着大量的信息交互。而且大部分应用输入都需要经历一个比较长的生命周 期,比如说一个客户订单输入到系统后,会先后经历前台系统 (Front Office),中台系统 (Middle Office) 以及后台系统 (Back Office),而且每个系统内部又包括很多服务组件。除了系统层面的跨度外, 这个生命周期也体现在时间长度上。而且,如今所有的金融系统都追求 STP (Straight Through

Java远程通讯可选技术及原理

家住魔仙堡 提交于 2019-12-03 22:38:28
原文网址链接http://www.blogjava.net/BlueDavy/archive/2008/03/04/182077.html 在分布式服务框架中,一个最基础的问题就是远程服务是怎么通讯的,在Java领域中有很多可实现远程通讯的技术,例如:RMI、MINA、ESB、Burlap、Hessian、SOAP、EJB和JMS等,这些名词之间到底是些什么关系呢,它们背后到底是基于什么原理实现的呢,了解这些是实现分布式服务框架的基础知识,而如果在性能上有高的要求的话,那深入了解这些技术背后的机制就是必须的了,在这篇blog中我们将来一探究竟,抛砖引玉,欢迎大家提供更多的实现远程通讯的技术和原理的介绍。 基本原理 要实现网络机器间的通讯,首先得来看看计算机系统网络通信的基本原理,在底层层面去看,网络通信需要做的就是将流从一台计算机传输到另外一台计算机,基于传输协议和网络IO来实现,其中传输协议比较出名的有http、tcp、udp等等,http、tcp、udp都是在为某类应用场景而定义出的传输协议,网络IO,主要有bio、nio、aio三种方式,所有的分布式应用通讯都基于这个原理而实现,只是为了应用的易用,各种语言通常都会提供一些更为贴近应用易用的应用层协议。 应用级协议 远程服务通讯,需要达到的目标是在一台计算机发起请求,另外一台机器在接收到请求后进行相应的处理并将结果返回给请求端

WSO2 ESB unknown error code 102511

前提是你 提交于 2019-12-03 22:27:18
问题 I have recently upgraded WSO2 ESB to version 4.7 on the Windows Server 2008 R2 and encountered the next error while simply proxying SOAP request to an endpoint: Receiving response while the handler is in an inconsistent state REQUEST_HEAD ERROR_CODE : 102511 ERROR_MESSAGE : Error in Sender ERROR_DETAIL : Error in Sender ERROR_EXCEPTION : null Thing is, that this error code is not described in the documentation and without an exception it is not obvious what to make of it. The closest code I

Mule ESB 3.3 - Receiving IMAPS mail (Gmail)

我的梦境 提交于 2019-12-03 21:33:36
Anyone has a working example of reading mails from IMAP over SSL (IMAPS) from Gmail? Some info I have gathered, but without any success: Mule ESB: Retrieving email messages from Gmail using IMAP connector IMAP Questions Mule ESB IMAP questions and of course the infamous documentation The thing just sits there doing nothing. Here is my flow: <mule> <imaps:connector name="imapsConnector" checkFrequency="5000" backupEnabled="true" mailboxFolder="INBOX" deleteReadMessages="false" doc:name="IMAP"> <imaps:tls-client /> <imaps:tls-trust-store /> </imaps:connector> <expression-transformer name=