iWay Software Una Compañía Information Builders

Presentación del tema: "iWay Software Una Compañía Information Builders"— Transcripción de la presentación:

1

2 iWay Software Una Compañía Information Builders
Entre los “Top 50” vendedores de software $300 millones de ingresos 30 años de experiencia Más de empleados Más de instalaciones en clientes 47 oficinas y 26 distribuidores en todo el mundo

3 iWay Software Soporte Mundial
Belgium France Portugal Germany Netherlands Spain Switzerland UK Austria Sweden Finland Norway Poland Italy Turkey\ Montreal Toronto Vancouver Atlanta Boston Chicago Cincinnati Dallas Denver Detroit Houston Los Angeles Minneapolis New Jersey New York Orlando Philadelphia Seattle San Jose St. Louis Washington D.C. Japan Korea Taiwan Hong Kong Bahrain Egypt Israel Kuwait Oman Qatar Saudi Arabia Yemen United Arab Emirates Singapore Philippines Malaysia Colombia Venezuela South Africa Sydney Melbourne Argentina

4 iWay Software MetaGroup
Plus: Peoplesoft, SAGENT, Software AG and many more Líderes mundiales en EAI y vendedores de Software de integración usan iWay Adapters por que: mejores y más baratos “time to market” comprar versus construir menor TCO servicio mundial foco en su negocio principal

5 iWay Software GARTNER 68% de proveedores de software de EAI y software de integración usan iWay Adapters por que: mejores y más baratos “time to market” comprar versus construir menor TCO servicio mundial foco en su negocio principal

6 Integración y Empresa

7 Evolución de la Integración
90s: Integración Punto-a-Punto 00’s: Integración “Hub and Spoke” Hoy: Integración Orientada a Servicios 1 2 3 ‘Desarrollo a Medida” Broker Conectores Service Interfaces

8 Evolución de la Integración Integración Punto-a-Punto
CICS gateway ORB Message Screen scrape RPC Down- load file Sockets Message queue APPC Trans- action Integración Punto a Punto Inmantenible Requiere “multi skill sets” Hace la integración compleja No escalable Imposible reutilizar

9 Evolución de la Integración Integración “Hub and Spoke”
Pros: Procesos centralizados Hace procesos visibles Centraliza conocimiento y experiencia Contras: Centraliza la administración de interfaces Mejor: definiciones centralizadas, delegar implementación y administración Fuerza dependencia de personal y vendedores Reduce la habilidad de unidades de negocio individuales para actuar como ellas desean Único punto de fallo Fuerza el conocimiento centralizado de cómo navegar y manipular los sistemas Complejo de escalar Broker Conectores

10 Evolución de la Integración Integración “SOA”
Technical Drivers Un acercamiento pragmático, de “mejores practicas” para el desarrollo de aplicaciones e integración. Mejor alineamiento de IT con el negocio Reduce costes y riesgos en IT Flexibilidad en plataformas Re usabilidad SOA, first and foremost is not a product. It is a best-practices approach for application development and integration. It lives at the convergence of application development and integration. Moving forward as IT matures, the vast majority of App Dev Projects will have an integration component. SOA is the methodology for meeting new business requirements using best practice integration approach. Properly built, SOA reduces complexity and frees up the CIO and his valuable resources to focus on value added tasks, that can be mapped to business value creation, rather than technical tasks. IT and the business it services have historically not been aligned. Successful CIO’s will create competitive advantage for their organization’s using IT, while other CIO’s will struggle to manage the organizational complex operational systems. IT projects are costly and risky. Many fail. Projects requiring integration are costlier and riskier – due to the mish mosh of disparate skill sets required to integrate the disparate systems. IT since its inception has always been too much about platforms and systems, rather than business process. SOA is about IT driving towards presenting a “business-friendly” face to the organization it services. SOA is about presenting reusable business services to the business – to effectively manage these services and sustain them over the long-term, these services should be loosely coupled from the platforms they live on – and hence be vendor agnostic. (iWay is the only vendor that can truly allow IT the flexibility to create, manage and reuse business services on any platform.) Reusability is about cost savings as discussed under business drivers. It is also about achieving a more efficient process for IT – a process that eliminates recreating the wheel and maintaining redundant applications. SOA provides a framework for reuse – reuse of both existing IT assets and the reusable business services that compose the SOA.

11 SOA

12 Integración Orientada a Servicios
SOA disponibiliza los recursos para otros participantes de la red como servicios independientes que son accedidos de una forma estándar. Esto provee de un acoplamiento mas débil y flexible que en arquitecturas tradicionales.

13 Integración Orientada a Servicios
A alto nivel, los desarrolladores de aplicaciones necesitan estar aislados de la complejidad de navegación y manipulación de sistemas y aplicaciones propietarias. A bajo nivel, la integración siempre implicará puntos de navegación y manipulación de recursos de información especializados Un ‘Service Adapter’ es un código customizado, con gestión autocontenida creado por alguien que actualmente conoce como navegar y manipular los sistemas de ‘back-end’ From Coarse-grained interfaces enable service composition in SOA, Jeff Hanson | August 29, 2003

14 SOA Reusable Business Services
From “Coarse-grained interfaces enable service composition in SOA”, Jeff Hanson, 8/29/2003 Composite Applications B2B BPM SOA Service Consumers Black box Business Services SOA Service Providers M o n i t r M a n g e Service Processes Adapters Disparate Information Resources

15 Business Process Ejemplo
Receive Order Check Inventory Ship Order Send Invoice Receive Payment ? ? ? Designing a business process requires business knowledge Implementing, deploying, and changing a business process system requires IT skills. IT and the systems they own are not currently organized, defined or interfaced around business needs or by business terms. Without a GUI-based SOA implementation, the process of deploying a designed business process is costly, prohibitive or even impossible. ? ? IT Mainframe EDI Oracle SP Manugistics Siebel AS400 I2 SOAP SAP IDOC MQ

16 Que necesita el negocio?
Receive Order Check Inventory Ship Order Send Invoice Receive Payment The business wants processes that are enabled by technology systems which are defined by business semantics that can rapidly be adapted when processes change.

17 pero, realmente, que necesita?
Ship Order “ Un Business Service require controlar, gestionar y manejar excepciones “ No CarrierSelection Send Request to Preferred Carrier Response from Preferred Carrier Yes Deploying and Operating a reusable business service requires a lot more than just a few boxes and arrows. An automatic process should be handle failures, errors, exceptions. Deploying a business service means a lot of application interactions. As an example the Shipping process opened. A simple box on top level might imply a lot more !!! Timeout Send DeliveryDate To Customer Receive Proof Of Delivery from Carrier Inform customer About late delivery Timeout

18 Creación de business services re-usables Servicios de Bajo nivel
Programming in PL/SQL Programming in Java Programming in .NET Programming in ABAP Create IDOC files Programming in SOAP Create EDI files Import/Export API wrapper This is what IT faces. In order to connect the business process to the IT systems and business partners all applications must be “SOA enabled”. Without a graphical point and click tool this means a tremendous effort in coding. The skill set of the programmer is required to be very large – it spans multiple programming languages, API’s, standards, systems and protocols. The result required: A set of low-level (fine grained) services that can be orchestrated when starting integration projects. a I 1 III 2 2 c b II 2 1 1 2 4 3 3 Mainframe EDI Oracle SP Manugistics Siebel AS400 I2 SOAP SAP IDOC MQ

19 Creación de business services re-usables Servicios de nivel de negocio
“Agregando funciones de bajo nivel para componer Business Services re-usables y significativos” service Receive PO service Check Inventory service Ship Order service Create Invoice service Receive Payment A set of low-level services is not considered as a “business service”. A business service is a logical service a business user would recognize, eg Receive PO, Create Invoice, Send Inventory, Calculate Forecast etc. Combining a set of low-level calls and API’s into meaningful services is what we call iWay Business Services – sometimes referred to in industry as “Coarse Grained Services” or “high-level services”. In real life this could imply that for a simple Receive PO process first Siebel needs to be checked if the customer is known and valid, next the PO must be stored in Oracle, a last the order history will be fed into Siebel. A number of low level function calls will be logically connected to form a new service that has meaning to the business process. a I 1 2 II 2 2 c b 3 1 1 III 4 3 Mainframe EDI Oracle SP Manugistics Siebel AS400 I2 SOAP SAP IDOC MQ

20 Consumiendo business services
Diseñar, Construir, Desplegar, Mantener y Medir los procesos Receive Order Check Inventory Ship Order Send Invoice Receive Payment service Receive PO service Check Inventory service Ship Order service Create Invoice service Receive Payment Finally the business process can be connected to the SOA layer. The SOA layer exists of exposed webservices, monitoring and registry tools. A business process engine can connect to these already existing webservices and orchestrate (control) a new process. When business requires a change, remodel the process flow and connect to the webservices in different order or with different content = agility. For example: Handling orders via a web portal or handling orders via B2B EDI documents becomes transparent. The process is the same, the channel will differ. a I 1 2 II 2 2 c b 3 1 1 III 4 3 Mainframe EDI Oracle SP Manugistics Siebel AS400 I2 SOAP SAP IDOC MQ

21 Consumiendo business services
B2B Operational BI Portal Trading Partner Manager BI Application Web Entry Form service Receive PO service Check Inventory service Ship Order service Create Invoice service Receive Payment Finally the business process can be connected to the SOA layer. The SOA layer exists of exposed webservices, monitoring and registry tools. A business process engine can connect to these already existing webservices and orchestrate (control) a new process. When business requires a change, remodel the process flow and connect to the webservices in different order or with different content = agility. For example: Handling orders via a web portal or handling orders via B2B EDI documents becomes transparent. The process is the same, the channel will differ. a I 1 2 II 2 2 c b 3 1 1 III 4 3 Mainframe EDI Oracle SP Manugistics Siebel AS400 I2 SOAP SAP IDOC MQ

22 En resumen … orientación a servicios? … un servicio?
Una tarea de negocio que se puede repetir e.g., validar el crédito de un cliente; abrir una nueva cuenta … orientación a servicios? Una forma de integrar el negocio como servicios enlazados y las consecuencias que acarrea … arquitectura orientada a servicios (SOA)? Un estilo de arquitecturas de IT que soporte una orientación a servicios … una combinación de aplicaciones? Un conjunto de servicios relacionados e integrados que soportan procesos de negocio construidos en base a SOA Main Point: Services are repeatable business tasks. Business processes are a series of services snapped together like building blocks. SOA is an architectural style that makes this possible Let’s start by looking at some base-line definitions so we’re all talking about in the same terms. First of all, what is a service? <read definition> It’s important to stress that we’re talking about a part of a business process here. Don’t think about software or IT. Think about what your company does on a day to day basis and break those business processes up into repeatable business tasks or components. If you look at the graphic in the middle, this is the analogy of building blocks <do NOT use the word “Legos”> snapping together to build a structure. Services are the building blocks and they are snapped together into a business process. Second, what is Service Orientation? Building on our definition of a service, Service Orientation is a way of integrating your business as linked services and, more importantly, the outcomes that they bring. We’re still not talking about technology; we’re talking about a thought process and a business philosophy. What is SOA? It is quite simply the IT architectural style that supports the Service Orientation thought process makes it a reality. And finally, what is a Composite Application? <read definition> So composite applications are the actual running services that have been assembled and strung together to support the what your business does. SOA helps make building and adjusting composite applications fast and easy. **Main point** SOA makes it easy to snap together services into a business process just like snapping together building blocks into a structure.

23 Implementando SOA

24 Implementado SOA Agility Necesidad de Negocio = “The industry transition to messaging and ESB … will mark an inflection point triggering a new, massive wave of innovation around businesses use of their information resources.” Roy Schulte, Gartner Tipo de Arquitectura = SOA Web Services Tecnología Usada = “Application integration for a hundredth the cost of proprietary connections.” Forrester Research Producto ESB =

25 Implementado SOA Enterprise: needs to
Help align IT projects with business requirements Decentralize capability across entire organization Interoperate with all enterprise IT assets Service: needs to Support composite business-level services Manage services even through changing requirements Standardize services across SOAP, EDI, EAI, etc. Bus: needs to Work with multiple channels (HTTP, EDIINT, etc.) Work with messaging (MQSeries, TIBCO, etc.) Extend to B2B

26 iWay SOA Middleware

27 iWay SOA Middleware™ A Complete SOA Implementation Solution
Process Manager™ iWay Trading Manager™ iWay Enterprise Index™ Java/.Net Dev Tools 3rd party EAI Tools SOA iWay Service Monitor™ iWay Service Manager™ Lightweight, highly scalable Enterprise Service Bus for message routing and transformation iWay Service Policy Manager™ iWay Business Services Provider™ iWay Service Designer iWay Transformer iWay Explorer Service Manager Developer Workbench™ iWay Partner Agreements iWay Business Process Manager is BPEL-based. iWay Service Manager includes the Business Services Publisher, which provides a Web service interface for anything that we do. That’s not the only interface available, though – we can also support JCA, JMS, etc. iWay Service Designer provides the stateless process management and routing needed to create composite services. iWay Service Transformer handles much, much more than plain old XML. It’s not limited to XSLT, which was really designed for the publishing business – it’s built from the ground up to handle EDI, flat files, and a variety of non-XML formats just as easily and efficiently as XML-to-XML transformations. In other words, we handle non-XML-to-XML, XML-to-XML, XML-to-non-XML, and non-XML-to-non-XML – all quickly and efficiently, in the same GUI. iWay Adaptive Framework is the clear world leader in this space. iWay provides a wide variety of transports. We run on top of existing transports such as WebSphere MQ (to create an “open-transport service bus”), or we can provide our own messaging using ebXML Message Service (ebXML MS) or Web Services-Reliable Messaging (WS-RM) (starting in 2Q06). iWay Universal Adapter Suite™ Transports: HTTP/S, WMQ, JMS, etc. Data Files Apps Docs

28 iWay SOA Middleware™ A Complete Middleware Suite for SOA
For creating reusable iWay Business Services Service Manager™ - Enterprise Service Bus Service Manager Developer Workbench™ Fully integrated tools for process, message transformation, business service deployment, trade agreement creation and management Business Service Provider™ Publishes processes as iWay Business Services (high-level, business oriented Web Services) For managing large-scale SOA implementations Service Management Suite™ Service Monitor™ Monitor iWay Business Services Service Policy Manager™ Create/manage iWay Business Service security policies

29 iWay SOA Middleware™ A Complete Middleware Suite for SOA
For creating large-scale integrated business processes Process Manager™ BPEL-based Business Process Management tool for creating long-running global business processes For managing B2B partner implementations Trading Manager™ Fully integrated B2B trade agreement management For enterprise message search capabilities Enterprise Index™ Powered by Google

30 iWay Service Designer

31 iWay Application Explorer
iWay Explorer The iWay Business Systems Explorer is a great examples of what we mean by integration assembly. In this screen clip. The user has selected an IDOC out of the SAP repository. The Business Systems Explorer can reach in to any major packaged application that supports a procedure catalog. In this case for SAP, a list of all IDOCs, BAPIs, and RFCs are returned. The user selects the desired procedure, then designates how the inputs and outputs of the procedure should be represented. In this case, we’re going to represent the procedure’s arguments as an XML structure file. Doing so will allow us to import it into the XML Transformation Workbench where we can work with it in a nice, intuitive environment. iWay Application Explorer

32 iWay Transformer As we learned earlier, the iWay XML Transformation is geared for point-to-point integration, and it’s particular sweet spot is reformatting transactions as they occur between applications and processes, and transforming or enriching the data contained on those transactions. Reformatting and transformation rules are applied thru the XML Transformation Workbench. On the left, the incoming transaction is represented. The outgoing transaction is represented in the right window pane. The user defines the outgoing format in the tool by using the source transaction layout as a starting point, or by working from a completely different definition of the target transaction. Incoming (source) to outgoing (target) mappings and transformations are then applied. Note in this example, that only selected fields from the source transaction have been chosen to comprise the transaction that will be emitted. A library of transformation routines is provide in the product, and others can be added. The Java-based transform routines are presented in a GUI wizard which makes it easy to manipulate the data. Data-level transformation capabilities are quite robust and can be exercised to change the meaning and format of source fields as they are mapped to their respective target fields. In addition new fields can be created on the target transaction that did not exist on the source transaction. Access to external data for use in the transformation process (data structures, packaged applications, TP environments, etc.), is provided by iWay Connectors and Adapters. The combination of iWay Adapters and the GUI Workbench virtually eliminate custom coding. The entire enterprise is now within reach using only SQL and/or stored procedure execution. The incoming and outgoing transactions can be in non XML or XML format. Once reformatted, transformed and processed, the engine calls an emitter to deposit the finished transaction in a specified destination: file, database, message queue, back on the network, etc.

33 iWay Universal Adapter Suite
Tipos de Adpatadores Data Adapters: Provee de una vista relacional de bases de datos propietarias y sistemas de archivos. Application Adapters: p.e. SAP, Siebel, PeopleSoft, JDE Transaction Adapters: p.e. CICS, IMS, Tuxedo Program Adapters: p.e. 3GL, 4GL, etc. Emulation Adapters: p.e. 3270, 5250 eBusiness Adapters: p.e. EDI, SWIFT, cXML, HIPAA Touchpoint Adapters: p.e. Bill of Materials, Chart of Accounts, Purchase Order, Sales Order, Work Order & more A D P T E R S Data Application TouchPoint Program Emulation eBusiness Transaction Application System Adapters Ariba AXIS Baan BroadVision Clarify Commerce One Hogan Financials i2 Technologies J.D. Edwards Lawson Manugistics Microsoft CRM MySAP.com Oracle Applications PeopleSoft SAP Applications Siebel Vantive Walker Interactive e-Business Adapters AS1/AS2 Comma-Delimited Files cXML ebXML EDI-ANSI X12 (American) EDI-EDIFACT FIX FIXML Flat (positional) Files HIPAA HL7 ISO 15022 OAG BOD Structured Files SWIFT SWIFTML Transora UCCnet XBRL xCBL Data Adapters Adabas Adabas/C ALLBASE/SQL C-ISAM (Informix) C-ISAM (Microfocus) CA-Datacom CA-IDMS/DB CA-IDMS/SQL Cloudscape D-ISAM DB2 DB2/400 DBASE DBMS EJB ENSCRIBE Essbase Excel Flat Files FOCUS Data Access Foxpro IDS-II ImageSQL IMS InfoMan Informix Ingres Interplex ISAM KSAM Lotus Notes Microsoft Access Microsoft OLAP Services Microsoft SQL Server Millennium Model 204 MUMPS (Digital Standard MUMPS) NOMAD NonStop SQL Nucleus Omnidex OpenIngres Oracle PROGRESS QSAM Rdb Red Brick RMS SAP BW SAP R/3 SQL/DS SUPRA Sybase Sybase/IQ System 2000 Teradata TOTAL TurboIMAGE Unisys DMS 1100/2200 UNISYS DMS II UniVerse VSAM XML Transaction Processing Adapters Bull TDS Bull TP8 CICS IMS/TM Software AG Natural Tuxedo Terminal Emulation Adapters 3270 (Mainframe, zSeries) 5250 (AS/400, iSeries) Touchpoint Adapters Analysis Codes Bill of Material Catalogs Change Quality Chart of Accounts Component Issues Container Move Customer Inventory Item Item Maintenance Locations Order Changes Preliminary Invoices Production Order Purchase Order Receipts Requisition Returns Sales Order Suppliers Users Work Order Work Order Status Change Technology Adapters Any J2EE Application Server BEA MessageQ BEA WebLogic Application Server BEA WebLogic Integration C C++ cc:mail (VIM) COBOL COM FOCUS FORTRAN FTP Fujitsu Interstage HTTP IBM WebSphere Application Server IBM WebSphere MQ (MQ Series) IBM WebSphere MQ Integrator Internet Mail (SMTP/MIME) JacORB Java JMS Lotus Notes (VIM) Microsoft BizTalk Server Microsoft Exchange (MAPI) Oracle 9iAS Oracle 9iAS Integration Oracle AQ Oracle PL/SQL Orbix Pascal POP Python RDBMS RPG SAP eXchange Infrastructure (XI) SAP Web Application Server Sonic ESB SonicMQ SunONE Application Server TIBCO JMS TIBCO Rendezvous Visibroker Connector Technologies .NET ActiveX iWay JCA JDBC™ Microsoft DTS MQSeries ODBC OLE DB SOAP Access to your information assets can be broken down into groups or classes of adapters. Listed on this slide, are: Data Adapters – which provide a relational view of any relational or non-relational data structures like DB2, Oracle, SQL Server, VSAM, IDMS, ADABAS, flat files, MUMPS and so much more. Application Adapters provide transaction level access to the most popular ERP, CRM, and SCM packages like SAP, PeopleSoft, Siebel, and more. Transaction Adapters provide fast and efficient access to TP environments like CICS, IMS/TM and Tuxedo. Program Adapters allow organizations to leverage their existing libraries of custom written programs in COBOL, PL1, SQL RPCs and more. Emulation Adapters deliver easy access to legacy green screen applications through screen-scraping technologies for 3270, 5250 and VT100 based applications. e-Business Adapters represent the latest investment of research and development dollars from iWay Software. iWay’s new Adapter Factory has pumped out e-Business transaction adapters like SWIFT and FIX for the finance arena, HIPAA for healthcare industry, and Covisant for the Automotive industry. No other EAI vendor can sole source as many adapters over more adapter classes as iWay Software. In fact, there isn’t even a vendor in the adapter business that can provide the coverage of iWay. So how does everyone else bridge the gap between what iWay delivers and what they don’t?? Well, they ship an SDK – or software development kit. Hey, if you have to build your own access, test it and maintain it That’s not integration assembly. Your back into a integration solution steepedin custom development.