INT403: How to Implement an EAI Architecture with Sybase Technologies - PowerPoint PPT Presentation

paul
slide1 l.
Skip this Video
Loading SlideShow in 5 Seconds..
INT403: How to Implement an EAI Architecture with Sybase Technologies PowerPoint Presentation
Download Presentation
INT403: How to Implement an EAI Architecture with Sybase Technologies

play fullscreen
1 / 22
Download Presentation
INT403: How to Implement an EAI Architecture with Sybase Technologies
677 Views
Download Presentation

INT403: How to Implement an EAI Architecture with Sybase Technologies

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. INT403: How to Implement an EAI Architecture with Sybase Technologies Marius Roets System Manager: Integration Solutions MariusRoets@woolworths.co.za August 15-19, 2004

  2. Agenda • Overview of Woolworths • Rules for implementing an Enterprise Application Integration Strategy • Critical Success Factors for Application Integration • The Integration Competency Center • Benefits for Woolworths • Woolworths Technical Environment • Existing integration architecture challenges • Sybase Technology as part of the EAI Architecture • Questions

  3. Overview of Woolworths • Store environment • 180 Corporate stores in South Africa • Textiles: 180 • Foods: 120 • 55 Franchise stores • 50 International stores • 25 Cross Border Stores • 5 Convenient Franchise Foods stores @ petrol stations Distribution Centers • 3 Textile DC • 4 Foods DC

  4. Overview of Woolworths

  5. Rules for implementing an Enterprise Application Integration Strategy • Create an application integration competency center. • Develop an integration city plan for your enterprise. • Focus on both B2B and A2A. • Document all application interfaces. • Select integration products by focusing on key requirements. • Run a proof of concept before buying. • Select the right implementation partner.

  6. Critical Success Factors for Application Integration • Executive Sponsorship. • Appoint the best resources into the integration competency center. • Start off Right: Selecting your Enterprise Integration Broker. • Looking Beyond “Silos”. • Limiting Customization in legacy applications. • Plan for Professional Services. • No “One-Size-Fits-All” Integration Solution. • Organization is crucial.

  7. Key Objectives of the Integration Competency Center • Get application integration recognized as the formal discipline it needs to be for the business and IT • Combine the skills and processes associated with application integration into a single group, making better use of a scarce resource • Build and develop skills, capability and best practices for integration processes and operations • Monitor and assess integration technology and tools and select a flexible set of approved tools

  8. The Skills of the Integration Competency Center • Middleware Specialists • Interface Designers • System and Software Engineers • Operational Support Specialists • Leadership, Management and Relationship Management

  9. How would a competency center group relate to an architectural group? • Potentially significant overlaps between the integration group and any existing architectural group. • The key difference is that the competency center brings together • architectural, • development and • operational roles into one group. • The character of the groups is also different — architects design, teach and move on, but much of what the integration group does is more mundane. • Those with architectural roles within the integration group can, and indeed should, play an active role in the architectural group.

  10. Benefits for Woolworths • Preserves existing systems – minimal impact on existing architecture • Integrated, comprehensive solution • Component-based architecture on Sybase e-Biz Impact Integration broker simplified maintenance • TCO for integration broker very affordable for business • Integrated architecture help business to think differently how they want to implement new systems/applications • Integration architecture assist in the implementation of business activity monitoring

  11. Overview of the technical environment • More than 250 business applications in Woolworths • Application hardware platforms • Mainframe – MVS – 2 LPARS (110 MIBS) • AIX Unix – All stores (store back office applications), all DC’s & head office • AIX Unix – Data warehouse (3 TG Informix database) • AIX Unix MQ Server Cluster • Microsoft Windows 2003 servers on IBM & Dell servers – 50 Applications servers & 3 MS SQL Server database clusters

  12. Mainframe Foods order management Textiles merchandising system Transaction Control Finance Systems (Walker) Woolworths Financial Services Systems (Vision Plus) Unix Foods supply chain Textiles demand forecasting Data warehouse Store applications WebSphere MQ Series Windows NT Microsoft Exchange RightFax Integration broker WebSphere MQ Series Staff Planner Peoplesoft Postilion payment gateway switch Microsoft Internet Servers / Microsoft Transaction Servers Overview of the technical environment

  13. Existing Integration environment in Woolworths Hardware: 2 * IBM Netfinity Servers in Microsoft Windows 2003 Cluster for Impact 4.1 & 5.3 4 GB memory, 8 * 2 GHz processors, 300 GB disk 2 * Dell Power Edge Servers in Microsoft Cluster for Microsoft SQL Server 8 GB memory, 4 * 800 MHz processors, 600 GB disk Software: Sybase Impact v4.1 in production Sybase E-Biz Impact v5.3 in production Sybase Adaptive Server Anywhere (Unix / NT) Sybase Enterprise Application Server Sybase Enterprise Portal Opalis Robot – Windows Scheduler Microsoft MOM – Management & monitoring SQL Server 2000 Enterprise edition Informix 9 on Unix platforms (Stores, DC, Data warehouse) WebSphere MQ Server v5.3 for Windows NT & Unix WebSphere MQ Server v5.2 for IBM Mainframe Qpasa for WebSphere MQ management Q-Liner for FTP compression over FTP / MQ / TCP Postilion – Payment Gateway to banks SMS Enterprise Server

  14. Existing Integration environment in Woolworths • Mainframe • 150 different transaction types (Assembler, Cobol, Easytrieve) – Plan to migrate all of this onto Impact v5.3 before October 2003 • 0.5 million transactions per day from/to mainframe (3 GB data / day) • Average MAP message size 1 MB, reading 55 MB for some interfaces • Main protocol is FTP, but MQ is also used in some interfaces to/from mainframe • Impact v4.1 configuration • 240 different transaction types • 30% of interfaces are database acquisition and/or delivery aims • 40% of interfaces are MQ interfaces • 10% of interfaces are Microsoft DCOM interfaces • 8 interfaces use TCP/IP Socket for interfacing with banks and mainframe (CICS transactions) • 10% of interfaces are Flat file / FTP interfaces • Process 5 GB data / day

  15. Existing Integration environment in Woolworths E-Biz Impact v5.3 statistics • 65 different transaction types • 30% of interfaces are database acquisition and/or delivery aims • 40% of interfaces are MQ interfaces • 2% of interfaces are Microsoft DCOM interfaces • 1 interfaces use TCP/IP Socket for interfacing with banks and mainframe (CICS transactions) • 28% of interfaces are Flat file / FTP interfaces Impact v5.3 configuration • 5 Clusters • 13 Controllers • 29 Applications

  16. Existing integration architecture challenges • Real-time interfaces into business logic that exist in Java classes and Microsoft COM+ components • Real-time interface from Java classes and Microsoft COM+ components to receive messages for processing in Sybase e-Biz Impact • Unified comprehensive web front-end for the integration database and documentation that is accessible from different hardware devices. • Guaranteed delivery of interfaces into web services. • Integration strategy must assist in bringing the TCO of information technology down. • Integration architecture is the base platform for delivering business activity monitoring.

  17. Sybase Technology as part of the EAI Architecture • Sybase Enterprise Application Server (EAServer) • Use EAServer to create web services for e-Biz Impact • Integrate into Java business logic from e-Biz Impact through JMS & EAServer • Integration into Microsoft DCOM+ from e-Biz Impact through JMS & EAServer • EAServer is the application server for our integration portal that runs on Sybase Enterprise Portal

  18. Sybase Technology as part of the EAI Architecture • Sybase Adaptive Server Anywhere (ASA) • Store transmission system (180 stores) • Use it as a staging database in the store environment for the MQ components • ASA runs on AIX O/S that IBM does not support anymore (ASA v6 for AIX v4.1, ASA v9 for ASA v4.3 or higher) • Security database for e-Biz Impact run on ASA v8.0 • Sybase South Africa develop a management console to monitor and manage all the ASA databases centrally from Woolworths service management center.

  19. Sybase Technology as part of the EAI Architecture • Sybase Enterprise Portal • Sybase Enterprise Portal is the integration team management portal for all interfaces • Functionality implemented in Sybase Enterprise Portal: • Data flow alert application to manage all alerts from applications, interfaces & infrastructure • Interface documentation repository • Resend application for messages to/from e-Biz Impact v5.3 and/or Impact v4.1 • Impact v4.1 / E-Biz Impact v5.3 database configuration application for the management of interface configuration • New store / Store conversion application for the management of interface routing

  20. Sybase Technology impact on integration competency • Pro • One vendor that support Woolworths integration strategy • Local support available from vendor • Integration challenges between different Sybase product easier because one vendor look after all our products in the integration competency • Development resources available from Sybase South Africa for projects • Cons • More technology & applications to support in the integration competency • Skill level of integration competency not always inline with the technology directions of the different Sybase products. • Platform certification timing issues

  21. Closing • Enterprise application integration is a complex endeavor, but it’s feasible if addressed properly. • Technology is not the most important aspect of application integration initiatives. • Proper organization and a clear understanding of your short-term and long-term needs maybe as critical as choosing the “best” product.

  22. Q & A