• 1. 企业应用整合 --- 异构应用的业务流程自动化
    • 2. 遗留应用的整合企业中还有大量的遗留应用系统,如何将它们与新开发的应用整合起来。 通过异构系统的整合,保护现有的投资,还可以方便地产生新的商务流程从而带来新的利润!
    • 3. 应用的整合为什么重要?是为了: 把事情做得更好 Automate Existing Processes 做一些新的事情 Provide New Services 最终目的是: 节约费用 Take manual Intervention out of a Process (Order Fulfillment, Inventory management, etc.) Coordinate better with Suppliers, Business Partners, or Customers 赚取新的利润 Provide New Products or Services (Web Enabled, (New combinations of Products, Services) Provide Better Service (Complete On-line Loan Approval, Purchase PC and On-line Service with single transaction
    • 4. 应用集成的“噩梦”Internal UsersCustomersSuppliersPartners
    • 5. “噩梦”的解决方案 EAI”涅磐”Internal UsersCustomersSuppliersPartnersEnterprise Application Integration Environment
    • 6. 流程驱动整合!Internal UsersCustomersSuppliersPartnersEnterprise Application Integration
    • 7. EAI 解决的五个问题基础构造: 1. 消息传递 (Middleware) 2. 已有应用系统的接口 (Adapters or Connectors) 3. 将所有数据转换为“世界语” (共同的语言) 4. 翻译“世界语”,解决方言问题。 真正的商务价值产生在业务流程自动化以后。 5. 协调多个系统 – 做什么?什么时候做?谁来做?等等。(管理异构系统之间的业务流成)
    • 8. iPlanet Integration Server 特性由业界最好的技术组成: 流程引擎 Award Winning - Cross Roads ‘A’ List 基于业界标准 - XML and XSLT Sun Java Message Queue – 我们最好的消息中间件 与 OS/390 主机系统由杰出的集成能力 流程引擎具有非常好的处理能力 – 单隔引擎处理超过一百万的商务流程! 轻量的适配器 简单的适配器生成技术
    • 9. 四种工作流(Workflow)Document/Image Workflow Contract development Information fulfillment Change managementEmbedded Workflow ERP HR Desktop appsCollaborative Workflow Messaging based New product development Issue resolution SchedulingProduction Process Management Real-time, in Production Extreme High Scalability Zero Latency and Straight- Through Processing
    • 10. 工作流类型Document/Image Workflow Plexus FloWare Tibco InConcert IBM MQSeries Integrator (formerly Flowmark)Embedded Workflow iPlanet Process Manager SAP embedded Workflow BEA Process Integrator WebMethods Collaborative Workflow Lotus Notes MS OutlookProduction Process Management iPlanet Integration Server
    • 11. BTCellnet英国第二大移动运营商 六百万注册用户 隶属于英国电信(BT) 面临的问题: 通过识别有价值的用户(可能带来更多的利润的客户),销售可以在电话商提供跟好的服务吸引消费者,降低“叛逃率”
    • 12. Call centre applicationBilling (VMS)Hardware Orders(informix)Oracle DatabaseBT Cellnet FastSAVE: The Business View
    • 13. BT Cellnet FastSAVE: Business Process ViewFront OfficeBack Office Receive call Retrieve Customer detailsSave CustomerCustom MiddlewareBillingCustomerStartGet Subscriber InformationOracle DatabaseHardware OrderHardware OrdersUpdate BillingCustom MiddlewareBillingRecord CompletionFinishOracle DatabaseChallenge: Reduce customer churn rate by identifying profitable customers and empowering CSR’s to provision services while on the phone Solution: An EAI solution that consolidated 12 billing systems, reduced inaccurate customer data, and enabled zero latency flow of informationiIS Integration
    • 14. MCI WorldcomIntegrated Order Manager Records Status Decomposes Order Sends Components to COMs On-going Order Management, Status and TrackingComponent Order Managers COM for every line of Business Separate Process for each ProductOthers...Order Entry, CSR 40+ different Entry Points Siebel (Future)Provisioning Service Initiation Exception HandlingLocal COMLD COMWireless COM
    • 15. MCI Worldcom - Business BenefitsReusable Process Framework for All Automation Projects Lower Development Costs Higher Levels of Automation in Process Fewer Rejects Reduced Exception Handling Shorter Provisioning Times Systematized Adding New Products and Bundles to Mix New Products, Bundles Delivered in Less Time Lower Training Costs Less Ramp-up Time for New CSRs
    • 16. 竞争优势 – 给您一些提示我们的核心优势: 有实施大型项目的成功经验 Open (XML, Java, CORBA, DCOM, JMQ, etc.) Robust, scalable process engine Integrated development environments (More True with Forte 4GL than Forte for Java, but FFJ will be folded in over time) 由全面的集成/电子商务解决方案 (SunONE) 具有很好的可扩充性/性能的流程引擎: 流程引擎 – 我们的传统财产 请注意: Workflow - Document or File Management, Low Throughput, email based, DBMS-Centric Architecture versus Production Process Management (Us) - Data-centric, high Throughput, TCP-IP Messages, Memory Resident Architecture 大多数产平源自于 Workflow (Document Management or Collaborative) – 他们的性能被过分夸大了。
    • 17. 请记住我们前面所提的领域特点; 每家公司的技术源自于一种 (Messaging, Transformation, or Process/Workflow) 总体来说,评价一个EAI产品,应该看看他的“根”. Most EAI companies started with a core product and evolved into EAI Their weaknesses will be found in the places where they had to "stretch" their core technology to encompass additional EAI requirements We are Only Ones with Process Background but we have Acquired Excellent Messaging (JMQ) 最为重要的时 --- EAI不是仅仅关于一个产品,他是在培育一个解决方案 获胜者将是拥有最全面解决方案的 竞争优势 – 给您一些提示