Fiorano SOA Platform - Technical Overview
Embed Size (px)
Transcript of Fiorano SOA Platform - Technical Overview
FIORANO SOA PLATFORM - TECHNICAL OVERVIEW
FIORANO PRODUCT OVERVIEWFioranoMQ
Standards (JMS) based Messaging ServerBenchmarked as fastest JMS Server since 2004 Market Leader
Fiorano SOA Platform
Standards based Enterprise Service BusDistributed Services Oriented Architecture Brokered Peer to Peer Platform for High Performance and Linear Scalability
EVOLUTION OF REAL-TIME ENTERPRISESInfrastructureCentralizedDistributed19902000Applications
SERVICE GRID ENABLER: FIORANO ESBReal-Time Information Easy-to-Change Processes Real-Time Business Alerts Better Competitive Positioning Better Customer Service Increased EfficiencyEnterprise Services
FIORANO - SERVICE-ORIENTED PROCESSES
ISSUES WITH TRADITIONAL ARCHITECTURES
FIORANO SOA PLATFORM ARCHITECTURE
FIORANO SOA PLATFORM NETWORK TOPOLOGY
FIORANO SOA PLATFORMMESSAGE-DRIVEN BENEFITSINCREASED SCALABILITY[+] Splitting Data & Control traffic enables a near-linear Performance with Fiorano ESB[-] Combined Data & Control prevents near-linear performance with competing alternatives[+] Fine-grain control over Peer/data and Enterprise Server/control performance at $5K/$25K increments [-] Coarse-grained limitations with multiple Integration Servers at $250K - $500K/each BUILT-IN RELIABILITY[+] Self-healing networks at no extra cost[-] Dual-redundancy could double the costs(1) Performance gains with additional Fiorano Enterprise Server(2) Performance gains with additional Peer (3) Competition: Combined (data+control) degrades performance(4) Potential performance improvements at huge additional costsEXTENSIBILITY[+] Any Distributed processing applications [-] EAI-centric
FIORANO SOA PLATFORM SCALABILITY, REUSABILITY
FIORANO SOA PLATFORMBUILT-IN RELIABILITY
FIORANO SOA PLATFORM SECURITY
FIORANO SOA PLATFORMFEATURE OVERVIEWFundamental ESB ServicesRobustnessScalability and PerformanceSecurityBreadth of ConnectivityTools
FUNDAMENTAL ESB SERVICESStandards supportedJMS, EJB, WebServices, XML, XSLT, SSL, SOAP, UDDI Bus servicesJMS, XML support, Content based routing, Transformation support, Dynamic data routing Support for highly distributed implementationsMulti-platform, Multi-language integration platformService-based approach, Location and Technology transparencySingle point of control via the Enterprise ServerDynamic changes to the business processDeployment support for servicesConfiguration Management support
FUNDAMENTAL ESB SERVICES CONT..
MonitoringSupport for enterprise management frameworks (SNMP)Real-time monitoring for services (Monitoring Tools)Single point of control (Brokered P2P Architecture)Start / stop facilitiesManual routing supportDynamic TracingMessage editing
ROBUSTNESSFault Avoidance Error/Exception sub-flowsStandards adoptionEase of use via Graphical Tools for creation of services and orchestration of Applications
Fault Tolerance Clustering support for Enterprise Server, Peer Server and failover of servicesRouting around failuresRedundancy support for servicesData Recovery
SCALABILITY AND PERFORMANCEPerformancePeer-to-Peer data routes for increased performanceAsynchronous messagingLoad balancingLarge data supportScalabilityAdd more peers servers to the network dynamicallyDynamic change supportTransparent resource addition (services and peers)
SECURITYAccess ControlUser authentication Component authorizationRole based securityNon-repudiation Information SecurityTransport security (SSL)Privacy (encryption)Integrity checking Tools UsageAuthorized users only (Role based) Deployment ManagementRestrict service deployment on specific machines
BREADTH OF CONNECTIVITYConnectivity ServicesWeb Services (SOAP Adapters)J2EE Connectors (EJB Adapter)JMS (JMS Adapters, MSMQ, MQSeries Adapters)RDBMS Connectors Legacy Connectors (EDI)
Other Standards Supported.NETCOM / CORBA
TOOLSUI based Orchestration ToolsApplication Orchestration ToolsService creation WizardsData Mapping ToolsEvent Process composition ToolESB definition ToolData flow definitions ConnectivityWrappers Incremental deployment Life Cycle SupportService, Application versioningDevelopment, Test, QA, Production management
SUMMARY OF FEATURES AND BENEFITS Integration Requirements
Support for Multiple Languages and PlatformsUI based Development, Deployment and Administration ToolsReal time monitoring supportContent based Routing XML/XSD/DTD supportMapping and TransformationWeb Services SupportRemote Deployment, Versioning and Configuration ManagementAudit Trail/Document TrackingScalability and Load BalancingHigh Availability and Failover
FIORANO SOA PLATFORM COMPETITIVE OVERVIEW
Key RequirementsTraditional Leading-edge VendorsFiorano SOAScalable ArchitectureHub-and-Spoke Architecture Limitations Brokered Peer-to-Peer Advantages : centralized control with optimized parallel data flowsBusiness Process AutomationFragmented - Business process and workflow design are handled by different products. Integrated - Combines Business Process composition and workflow deployment without programmingStandards-based InteroperabilityProprietary adaptersProvides support for Web Services, XML, JCA SOAP and WSDL, plus several pre-built adapters growing in 2H03Product License / TCOTime to Utility of EAI solution $500K / $1-2 Million, 12-18 months65-75% cost savings3-4 months Comprehensive SolutionBrand-equity, Large suite of AdaptersMature player in EAI, Enterprise Messaging, Marquee customers, modern solution
FIORANO SOA PLATFORM COMPETITIVE OVERVIEW
Key RequirementsTraditional Leading-edge EAI VendorsFiorano SOAComposing new Workflows across Heterogeneous PlatformsDifficult significant manual programming limited to particular component models (EJB, or .NET, etc.)Simple reduced programming effort Visual drag/drop tools allow rapid synthesis of workflows across platformsDistributed Document TrackingDifficult Documents tracked in the centralized broker only; difficult to monitor stepped changes Simplified Documents tracked across the network, with data capture across network end pointsAdapter and Service ConfigurationLimited configuration options cumbersome, time-consuming changes to flat filesCustom-GUI support on a per-adapter basis, allowing rapid configuration at network end-pointsMulti-Language Support Typically Absent biased towards single language (Java or C++ or .NET)Multi-language development: Java, C, C++, C#, VB, Perl, Scripts and othersDebugging Distributed Data FlowsDifficult to impossible centralized control-flow brokers inhibit debuggingIntuitive, easy to use tools for distributed data debugging, reducing development time
TECHNOLOGY VISION ROADMAP
***Lets begin by taking a look at the evolution of real-time enterprises.
The INFRASTRUCTURE layer began with single computers that got networked into a LAN and then into a distributed WAN called the Internet.
Similarly, the Services that leveraged the Internet called the web services layer began with simple work-flows and business processes as crafted by business users of enterprise information.
As multi-vendor applications and data needed to be available, Enterprise Application Integrators (EAI) like Tibco and Webmethods have deployed EAI infrastructures in a classic hub-and-spoke architecture. Most enterprise web-services are deployed on these custom-built back-end EAI deployments.
However, the journey towards becoming a real-time enterprise requires four fundamental requirements that cannot be met AFFORDABLY both in terms of time and money by current back-end EAI deployments.Real-time Enterprises demand:A real-time availability and adaptability of business processes by business-users, thereby necessitating the solutions to be trivially easy to install, debug and deploy, and we will take a look at some examples.Performance that leverages the growing infrastructure bandwidth and availability Scalability from the dynamically fluid front-office requirements to the easy integration into the back-end EAI as well as enabling devices of any type including the mobile wireless devices to be a part of the new real-time enterprise nervous systemAnd most critically the solutions need to easily integrate into existing EAI back-ends and provide a path to new and developing architectures and benefits such as the peer-to-peer architectures - AFFORDABLY*Lets take a closer look at Enterprise Information Architectures that are members of the Service Grid.
The Networking and Compute Hardware forms the foundation.Traditional EAI systems, like Tibco solutions, form the next layer of integrated applications.And in the last few years, the Web Services vendors form the layer closest to the consumers of the information customers, partners, employees and key business-users.
When put to the test by business-users modifying business-processes, there exists a HUGE CHASM between solutions in either layer. The CIO, stuck with a mandate of bridging these two is facing technical and budget solutions such as:Business-users want Drag and Drop simplicity and responsiveness of creating workflows by tying various services together, without the usual 4-6 week delay and a lot of expense. Making a change in their workflow should be as easy as manipulating a spreadsheet!In the age of doing more with less, each additional service or the task of modifying each additional service should not have have to involve expensive consultants and custom-code per change!As eBusiness information gets global, it is imperative that the deployment and debugging of the overall solution can be done securely from remote locations for all the obvious benefits.CEOs are demanding long-term ROI and TCO benefits of their next investment. Building solutions that adhere to open standards maximize TCO potential by ensuring lower risks of being locked into proprietary solutions. And finally, customers are tired of vendor lock-ins such as Microsofts .NET v/s Suns Java, or solutions geared towards business-users but not rich and powerful enough for developers, or having to choose between extending the traditional hub-and-spoke v/s the peer-to-peer choices.
Net: As customers get more power over vendors in the current economy, they are demanding each of the critical items without having to trade one off against the other.
Tifosi is the ONLY Web-Services Operating Platform that delivers to all of these requirements as we shall discuss through this presentation now.*There are several end-markets that can benefit from Tifosi as a Services Integration Platform, as shown in the top-tier. Based on feedback from our customers over the years, integrating diverse applications within businesses is our first target market. Our initial successes in this market as evinced by our recent $3.5-Million win at POSCO, Korea is a testimony to Forresters finding in a recent report on the size of the EAI market. Forrester claims that the global-3500 companies will spend an average of $6.4-Million EACH in 2003 on their EAI needs.
With Tifosi, we have enabled the centralization of key administrative tasks such as Security and Applications while enabling a network of Tifosi Peer Servers (at $1k/each in volumes) to exchange data in a peer-to-peer fashion.
You get the best of both worlds: Centralized control, and a fluid, limitless scalability with the Peer Servers.
With Tifosi, you can shrink your 12-24 month EAI projects down to 3-6months, at costs that are a magnitude lower than current budgets for EAI. *Before we get to discussing details of the FioranoESB, here is a high-level view of incumbent architectures.
Most of the current Hub-and-Spoke middleware (some with shared storage), requires every single message between the integrated applications to have to traverse a centralized Integration Server the HUB.
These architectures deploy a publish/subscribe model which forces each service (as we have defined it) to embed in it all the routing information for the message itself consisting of topics and queues that come into play.Burying the routing into the service itself has a debilitating effect: The services are not easily reusable.
Other penalties with the hub-and-spoke architecture include: (read through the list on the right).
Now, lets take a closer look at how Fiorano solves these problems at an architectural level.
*Hub-and-Spoke architecture deficiencies addressed and resolved by the Fiorano ESB Architecture include:In a hub/spoke system, all data and control information flows through the hub (and how we are different)The hub is a single point of failure; the way out is multiple hubs which incur exponentially growing costs (ditto)Business logic is split between the hub and each spoke; hence, changes are difficult to implement and result in linearly increasing overhead costs (ditto)Mapping distributed business processes onto centralized hub-and-spoke architectures is unnatural and become prohibitively difficult to scale (ditto)Most importantly, hub-and-spoke architectures are most amenable for DEVELOPERS as end-users, and due to their inherent complexity, difficult for business-users. (ditto)*Think of FioranoESB as consisting of three layers and all messages as consisting of DATA and CONTROL packets:
The top layer consists of Fiorano Peer Servers with their local store/forward and security controls. A ring of arbitrary number of Peer Servers enable peer-peer DATA routing.
FioranoMQ forms an Intelligent Messaging backbone that load-balances all CONTROL messaging traffic to an arbitrary number of centralized Fiorano Enterprise Servers. So, for instance, when you create/modify this service (point to the CRM box in the left hand Peer), it gets registered into a reusable services palette with control signals to the FMQ backbone and on down to ALL connected Fiorano Enterprise Servers (FESs).FioranoMQ leads JMS messaging servers in performance and scalability metrics, and is interoperable with other MQ-products.
And finally, the FESs provide an innately fault-tolerant support for FioranoESB deployments with centralized tasks as mentioned in an earlier slide: Security, Application repository and so on.
FioranoESB can be easily inserted into existing EAI deployments by bridging between FioranoMQ and the resident JMS messaging servers. Some of our customers are deploying FioranoESB in a hybrid mode, and once they see the benefits with FioranoESB within the context of their requirements, the FioranoESB Effect spreads across their current EAI deployments drawn by a clearly superior ROI as measured by customers themselves.*This is a summary of three high-level benefits with FioranoESB.
The benefits versus competitive architectures are: (read the right hand boxes)
*This is the next level look at each benefit, and the FACTORS leading to these benefits.
We contend that Scalable Performance is THE metric to be used instead of just performance or scalability in isolation. Heres how a combination of FESs (Control traffic) and Fiorano Peers (Data) help CTOs achieve fine-grain VISIBILITY and control over scalable performance. (Talk through the Aggregate Traffic on the LHS/bottom)
There are several factors driving up the ROI (Returns on Investment) of EAI solutions. A key driver is the notion of Reusable Services. It should be possible for programmers to create and register their services into a centralized palette and have it be instantaneously available to any business-user within the enterprise seeking to alter/create a business process to match a new business scenario. These reusable services are analogous to the macros in a spreadsheet.
We spoke earlier of how incumbent pub/sub paradigms force the embedding of routing information into each service rendering the reusability of services as a complex, expensive proposition.
Fiorano ESB enables reusable services as shown in these two examples (numbered boxes on the RHS).In the first case, you could take EXISTING/Legacy applications, write or take an off-the-shelf adapter for this service, wrap them with code as enabled by a Services-wizard, and voila! you have just ESBized your legacy service.
The critical difference between the Fiorano ESB approach vs. the incumbent approach is that with the Fiorano ESB model, the developer can (if desired) be completely oblivious to any notion of Topics and Queues. That is, the developer does not have to even maintain a Topic/Queue hierarchy, since all Topics/Queues are created at runtime on demand as dictated by the business-flow requirements.
In the second case, you could write a new service without having to worry about embedding ANY routing overheads. You have two APIs, with N:inputs and X:outputs. This is your programmers sandbox. When plugged into the FioranoESB Network (consisting of distributed Peers and Fiorano Enteprise Servers riding the FMQ backbone) when plugged into this network, FioranoESB instantaneously creates all the routing information needed to ensure correct functionality as expected with incumbent solutions.*Lets talk about Reliability - and High Availability.
Recall our earlier slide about the 3-tier IT stack. Assuming that the foundation-layer and the applications-layer are RELIABLE, the entire enterprise applications and data the lifeblood of any modern business are now ONLY as reliable as the Services Integration Platform! Most incumbent solutions address reliability by demanding redundant replication of the Integration Servers which are an expensive proposition, and add further complexity.
With Fiorano ESB, High Availability is BUILT-INTO each component of the stack.
At the highest level, each a SERVICE can designate another instance (on another machine) as its fall-back in case of its failure. This enables a SERVICE level failover, and as we have defined it, a workflow/distributed application is a collection of services.
At the Peer server level, each Peer can designate a secondary and a tertiary target in case of a failover. Its local store/forward state-engine, as well as queues and messages are instantaneously replicated onto the secondary and tertiary Peers enabling a message level failover.In the event of any messages in transit during a Peer failure, the messages can be retrieved from the secondary Peer. The Peers, by backing each other up in real-time AND ensuring no loss of messages due to any failed Peer constitute a SELF-HEALING FioranoESB Network.
The FioranoMQ servers can be deployed in a fault-tolerant active/standby configuration, or as a server-cluster to achieve higher reliability spread across multiple machines.
And finally, the FESs act in a manner similar to the Peers, with the difference being in the content that is replicated and failed over between FESs.
When either a Peer or a FES is re-inserted into the network, it syncs-up to current operational levels transparent to the business-users using Fiorano-powered business processes.
Reminder: Role-based Security and access controls ensure that only authorized personnel can administer, monitor and control all the availability aspects that form a robust highly available system, as discussed in the next slide.
*Lets talk about Security.
An Enterprise Service Grids Security and Governance policy includes empowering security administrators to limit access and control of a business process at the user, service, and component levels. Fine-grained security support enables a seamless security implementation inside and outside corporate firewalls. Messages can be securely transported using HTTPS and SSL protocols (client and server-side certificates and authentication supported). Security certificates can be stored redundantly in multiple Enterprise Servers (ES) across the Enterprise Service Grid network.
*The power of an ESB to solve an Enterprises integration problems has been discussed by several leading Technology Analysts such as Gartner, IDC, Saint Consulting and others. Says Steve Craggs, VP of the EAI Industry Consortium ESBs offer an excellent basis for integration, delivering a flexible and adaptable environment that enables integration projects to be put in place productively, effectively and in a staged manner. Adds Roy Schulte, Vice President Research at Gartner Inc. An ESB can be a sensible first step toward a systematic Enterprise Nervous System because it provides the basic connectivity backbone. It can interoperate with a variety of disparate application servers simultaneously, smoothing over technical differences and also providing services for communication and integration.
Listed above are critical categories that enterprises need to look at while evaluating ESBs*SOA:oFlexible and extensible Service abstraction model, allowing multiple inputs and outputsoAllows complex integrations to be composed or assembled from pre-built, pre-tested ServicesoPackaged support for EJB, COM, Web Services and CORBA componentsoPackaged support for multi-language services including: C, C++, C#, and Java executables, scripting and legacy servicesStandards:oAllows a for reliability and scalabilityoLeverages standards for connectivity (JCA), Transformation (XSLT) and security (SSL) and Web Services (SOAP, UDDI)Messaging:oXML message support, with integrated Schema validationoIntegrated transformation and mapping tools, with support for XSLT, XPATH and Content Based RoutingoLoosely coupled, external routing for dynamic, on-the-fly changes to application flowsoPluggable JMS-compliant transport layer
Distributed Implementations:oFully distributed service-based architecture with centralized control and distributed, parallel data-flows between services; Peer Messaging Servers enable parallel data-flows between network end-points, enhancing scalability and performanceoInter-Service communication over JMS supported with location transparency; Pluggable transport layer for technology transparencyoDynamic external data routing between services, allowing data-routing changes between running services; Content and message-header based routing supportedoCentralized Control for application monitoring, document tracking, deployment, versioning, service updates/upgrades, dynamic tracing and loggingoDynamic deployment of Services from centralized control point to network end-points.
==============oPre-packaged connectors for Web-Services, J2EE (EJB), JMS, MQSeries (WebSphere MQ)oAdditional middleware connectors including CORBA, MSMQ, Tib/RvoCentralized administration of entire FioranoESB infrastructure networkoSupport for HP-OpenView, IBM Tivoli and other SNMP-compliant network management toolsoServices can be configured, upgraded and automatically deployed to any node in the network using integrated tools from a central pointoService versioning and a rule-based configuration engine allows fine-grained control of service deployments to network end-points oDynamic run-time deployment allows services to be added or replaced on-the-fly within running applications for incremental extensibilityoSub-flows allow complete applications to be packaged into single services, enhancing reusabilityoProblem determination via real-time real-time alerts for service-operations (running, stopped, service-specific messages); comprehensive monitoring API for services; easy adjustment of required alerts at runtime using point and click toolsoIn-built alerts for common system problems : disk-full, thread and process limits, etc. Additioanl problem prediction via service level log-tracking, fault and error flows, and dynamically insertable distributed data-debugging capabilitiesoInternal capture of comprehensive system statisticsoIn-built support for SNMP and other Enterprise Management Framework Agents like OpenView and Tivoli, for comprehensive reportingoSingle point of control for distributed applications through the Fiorano Enterprise Server; composition, monitoring, launching, security and administration tools centralized on a per-domain basis. oRemote start/stop supported at both on a service-instance as well as application levelsoManual routing supported without additional programming via GUI toolsoDynamic service-level tracing allows fine-grained, runtime adjustment of logging informationoMessage-Editing and modification via distributed debugging tools, with support for dynamic break-points*Connectivity Services:oPre-packaged connectors for Web-Services, J2EE (EJB), JMS, MQSeries (WebSphere MQ)oAdditional middleware connectors including CORBA, MSMQ, Tib/Rv
Administration:oCentralized administration of entire FioranoESB infrastructure networkoSupport for HP-OpenView, IBM Tivoli and other SNMP-compliant network management tools
Deployment:oServices can be configured, upgraded and automatically deployed to any node in the network using integrated tools from a central pointoService versioning and a rule-based configuration engine allows fine-grained control of service deployments to network end-points oDynamic run-time deployment allows services to be added or replaced on-the-fly within running applications for incremental extensibilityoSub-flows allow complete applications to be packaged into single services, enhancing reusability
Monitoring:oProblem determination via real-time real-time alerts for service-operations (running, stopped, service-specific messages); comprehensive monitoring API for services; easy adjustment of required alerts at runtime using point and click toolsoIn-built alerts for common system problems : disk-full, thread and process limits, etc. Additioanl problem prediction via service level log-tracking, fault and error flows, and dynamically insertable distributed data-debugging capabilitiesoInternal capture of comprehensive system statisticsoIn-built support for SNMP and other Enterprise Management Framework Agents like OpenView and Tivoli, for comprehensive reporting
System Actions:oSingle point of control for distributed applications through the Fiorano Enterprise Server; composition, monitoring, launching, security and administration tools centralized on a per-domain basis. oRemote start/stop supported at both on a service-instance as well as application levelsoManual routing supported without additional programming via GUI toolsoDynamic service-level tracing allows fine-grained, runtime adjustment of logging informationoMessage-Editing and modification via distributed debugging tools, with support for dynamic break-points*oMultiple standards supported, including XML, JMS, J2EE, SOAP/UDDI, and .NET, with development in all major languagesoEasy-to-use, intuitive GUI tools for composing, deploying, monitoring and administering distributed applications; no programming required to set up and deploy complex processes using pre-built, pre-tested servicesoEnhanced fault avoidance via Sub-flows and error-flows embedded within the application-process flowoDynamic addition of Peer Servers at network end-points for improved scalability and performanceoDynamic message re-routing across services avoids route failures; store-and-forward at local peers ensures data integrity in case of unavailable pathsoRedundant peer-labels for Services ensure automatic fire-up for backup service instances in case of primary node failuresoClustered Enterprise Server with real-time mirroring of application state ensures complete fault-toleranceoCompensating transaction model for recovery and long-running transactions*oHigh-performance JMS backbone with support for asynchronous messaging and multi-threaded services; Messaging servers at network-end points enable direct, parallel data-flows between distributed services, allowing unmatched performance and scalabilityoLoad balancing supported at the Service level, allowing dynamic load-balancing to be added to running applicationsoAvailable APIs for bulk data transferoParallel data-flows between distributed services for linear, unbounded scalability; no centralized bottleneck to communicationoIn-built service-categorization and message prioritization on data-flow routesoIn-built dynamic modification and extension of applications at runtime, with control over individual service instancesoDynamic changes to aMulti-level Service categorization to ease management of service groupsoIncremental, transparent resource addition at both infrastructure as well as Application and Service levels; infrastructure can be extended incrementally at runtime, without disrupting services*oACL-Based, J2EE and LDAP compliant security for User and Service authenticationoIn-built support for sophisticated configuration management for fine-grained runtime control over Service and Application deploymentsoService-level digital signatures oNon-repudiation enforced via document tracking and audit-trails controllable at service-instance leveloPluggable RSA and DSA encryption on all data-flow routesoSSL-based transport level security at trasnport (JMS) level oRole-based security model controls access to and usage of tools on a per-user basis; multiple groups with user-rights assignment *oExtensive third-party support for mainframe and legacy adapters oNative pre-built SAP adapteroPre-built, native bi-directional bridges to JMS, MQSeries, Tib/RV and MSMQ oNative EJB adapter allows asynchronous invocation of WebServices and EJBs hosted on any J2EE compliant AppServer.oNative .NET integration via C#, Visual Basic and ActiveX supportoNative support for Serviced developed in Java, C, C++, Perl and other scripting languages
oNative COM and CORBA components for Service development
oSupport for WebServices and JCA
oNative Services for HTTP connectivity and FTP
*oSophisticated, easy to use GUI tools allow developers to easily create data flow definitions across distributed services with drag-drop-connect metaphoroPre-packaged flow-control Services including Conditionals, Join and Distribution; easy-to-change and modify workflows and data-flows at runtime using graphical toolsSophisticated wrappering API; rich, pre-built, pre-tested components including oRelational Databases, with XML mappings to/from the databaseoSophisticated File Adapters, oAdapters to IBM Websphere MQ (MQSeries), MSMQ, JMS messaging systems, oWeb Services (Componentized WSDL), EJB, SAP, PeopleSoft, and oUtility Adapters including SMTP, POP3, HTTP, FTP and moreoWrappering API and Component model allows existing legacy applications to be incorporated as Services in a completely non-intrusive manneroLocation transparency built into component model; Services can execute anywhere since routing information is detached from Service codeoService-based approach simplifies componentization of existing Web Services, Database, Legacy, and J2EE and .NET software assets, enhancing reuse within enterprise business processesoTools for managing multiple versions of components, allowing version upgrades to be driven from a centralized location via GUI tools oComponent state labeling (Development, QA, Staging, Production), combined with the labeling of network end-points give deployment engineers control over the classes of components running on particular hardware systems within the network, allowing unparalleled deployment flexibility unmatched by any other platform**We understand that end-customers and partners have a dizzying array of choices for their EAI requirements.Most customers regard Fiorano ESB as one of the top-3 contenders for their key EAI projects.
We have architecture, benefit and feature level data comparing Fiorano ESB with products from Tibco, SeeBeyond, webMethods, Vitria and Microsoft(BizTalk). This slide is a high-level summary of what we have gathered as key requirements, and our benefits v/s competitive offerings.
We are towards the end of our hour with you. We would like the opportunity to dig deeper into your business and technical EAI requirements and click down to deeper details as needed.*We understand that end-customers and partners have a dizzying array of choices for their EAI requirements.Most customers regard Fiorano ESB as one of the top-3 contenders for their key EAI projects.
We have architecture, benefit and feature level data comparing Fiorano ESB with products from Tibco, SeeBeyond, webMethods, Vitria and Microsoft(BizTalk). This slide is a high-level summary of what we have gathered as key requirements, and our benefits v/s competitive offerings.
We are towards the end of our hour with you. We would like the opportunity to dig deeper into your business and technical EAI requirements and click down to deeper details as needed.*This is a high-level view of the Fiorano ESB roadmap influenced heavily by our mainstream customers.If you see any of your must have requirements as not listed here, and would like us to consider them we would like to hear them.