Hi Rob, How do you manage your federated ESB architecture? Is their built in management support in Crossvision? I assume Crossvision manages the routing dependant on local or are these sites disaster recovery sites? I am currently working on a canonical data model for our endpoints; however, I am having trouble grasping how to connect databases. How do you present your data model?
We have less of a need for connecting internal applications and more of a customer centric approach. I believe it would be wise to provide access to each service via UDDI as we go. Governance will be critical to us. In a basic form I was thinking of developing unit tests for each endpoint and build servers which polled each to log and report availability, usage, etc. My main sticking point is in understanding how to represent the data model for DB to DB needs such as implementations where data is transformed from disparate methods into our data model. I'm not entirely sure this belongs in the ESB; however, it seems that it can fit. Look forward to your posts. Thanks, Bryan -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Brooks-Bilson Sent: Thursday, April 03, 2008 12:16 AM To: CFCDev Subject: [CFCDEV] Re: architecture question: communication between applications Hi Bryan, I'm working on the post, slowly ;-). In the meantime, right now, we have a federated ESB architecture with one ESB in the US and one in the Philippines (probably will be adding a third in Korea eventually). Our current ESB is Software AG's Crossvision Service Orchestrator. Since SAG recently bought WebMethods, the combined company will be combining their ESB/Integration server products into a new offering later this year. We'll eventually upgrade to that product. We are using web services, message queues, JDBC connectors, FTP, email, directory watching, http post, and custom Java adapters for our endpoints. We have canonical data model for most of our transaction types (this is one of the most important things you will need to do), and we're currently transforming and pushing millions of messages through the bus a month. Our ESB is used for both internal integration, and for RosettaNet based B2B integration. We've been at this for a little over two years now, and are just heading down the governance road where we'll be putting the infrastructure, policies, etc. in place to better manage what we've built. UDDI will be a part of this. Right now, we're not exposing much in the way of services to our application developers, so it's been relatively easy to manage up until now (we've mostly been using the ESB to integrate existing systems). There are several governance products we've looked at, and there is a lot of promise, but there's also a lot of complexity (and cost) to most of them. -Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
