1 / 75

Systems for E-Business

Systems for E-Business. Integration and Optimization on the Web. Major Issues. Majority of organizations are faced with a number of major issues: Address Web application development Address Web applications scalability and reliability Address Web applications integration

alodie
Télécharger la présentation

Systems for E-Business

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Systems for E-Business Integration and Optimization on the Web

  2. Major Issues • Majority of organizations are faced with a number of major issues: • Address Web application development • Address Web applications scalability and reliability • Address Web applications integration • Provide framework for Web application integration • Integrate Web and back-end applications • Move from “Web-sites to Web applications to Web transactions” • Selecting the right enabling technologies for Web application development and Integration • CORBA, MTS/COM, Commercial Web Application Servers, Object Transaction Monitors, EJB etc • Enterprise Application Integration and Web Enterprise Application Integration are key • (W)EAI = Middleware?

  3. Web Integration Requirements • Web Server Integration • Enterprise Middleware Integration • Application Development Integration • Integrating back-end databases • Intelligent Data Transformation • Leveraging legacy applications

  4. #1 DBMS/Web Integration: Integrate the relational database into the e-commerce/web architecture by providing a Web-interface to database access and supporting transactions on the Web #2 Defragmentation: Integrate multiple different data sources and applications into the e-commerce architecture #3Function Extension: to create new interactive Composite Applications with a Web interface: to the user the applications appears to be a new Web applications but behind the scenes, it may invoke one or more mainframe or UNIX/NT applications and databases Out-of-Scope: Data Consistency Management: This is the ability to provide consistency of data stored in physically disparate databases. DBMS replication as well as message queuing middleware can be used to develop application-specific synchronization processes Different Views on Database Integration on the Web

  5. Database Integration and Optimization Prerequisites: CORBA and JEB

  6. CORBA Architecture

  7. Java Enterprise API’s

  8. Client Protocols... • HTTP • Hypertext Transfer Protocol • Intended for stateless text transfer • Applets, Active Server Pages • Some vendors put tags into the html stream • resolve at the server to calls to application code running under the application server. • RMI • Remote Method Invocation • Originally intended for Java-only application distribution • Java-to-Java • Objects passed by value • As an API over IIOP • Objects passed by reference

  9. Client protocols ... • IIOP • Internet Inter-Orb Protocol (OMG/CORBA) • Intended for CORBA-compliant application distribution

  10. Database Integration and Optimization E-architectures for Database Integration

  11. Web Integration Technologies vs Web Integration Patterns High Middleware Web Ext .(at the client) Object Web-Enabled Transaction Message Monitors Brokers Host Web Functional Servers Complexity Web Web Terminal Web Web Application Emulators Integration Screen Servers Servers Scrapers Low Function “GUI-ification” User Interface Defragmentation Extension Redesign Web Enablement Pattern Source: Gartner Group, December 10, 1998

  12. Web Integration(1) via Web Application Servers(WAS) Examples: IBM WebPhere Oracle Application Server BEA WebLogic Netscape Application Server Web Browser HTML WAS RDBMS Web Browser Apps Apps HTML Apps Apps Web Browser Business Logic Wrappers HTML

  13. Web Application Servers Fill the Gap WWW Middleware • TP Monitors • CORBA OTM • Messaging • Database Integration • Legacy Application Integration • ERP Integration • Universal client • Stateless • No transactions • Weak persistence • Simple applications Web Servers Web Application Servers Firewalls/Security

  14. Web Application Servers Fill the Gap • State/session management • Transaction management • Scalability and high performance • Robustness and manageability • Enhanced security • Persistence • Most important … provide necessary integration with back-end infrastructure

  15. Web Application Servers Fill the Gap • Web Application Servers (WAS) have to perform multiple roles • Host business logic • Make it accessible • Scalability, integrity, security, responsiveness • Integrated management • Comprehensive run-time • Well defined integration points • Provide a single and consolidated application development environment • Foundation for EC

  16. Web Application Server Provide • Web Application Servers can host a variety of applications including Java applications, C++ applications, Visual Basic etc. • Integration with back-end infrastructure and middleware • CORBA, MOM and other types of middleware • Enterprise Resource Planning Applications (Peoplesoft, SAP, Baan etc) • Legacy Applications • CICS, IMS, Legacy Databases

  17. Dispatcher Group of Server Applications Packages (SAP, PeopleSoft) Native SQL ODBC JDBC Access Components Generic Web Application Server Architecture Firewall Integrated Development Environment Web Server HTTP CGI,NSAPI,ISAPI Client Component Legacy Applications via: CICS, IMS, MQSeries Load Balancing Internet HTML HTTP Security HTML + Java Extranet IIOP Management Client/Server applications (C, C++) Java Intranet IIOP

  18. WebLogic - Product Architecture Java & MS COM Client Apps WebLogic Server

  19. Common Application Server Components • Web Server APIs • NSAPI, ISAPI, CGI, Servlets • Application Manager • Hosts Application Logic • Cgi-bin programs, Java objects, Java Servlets etc. • Manage application instances • Web “Transaction” Manager • Manage Web based “Transactions” • Database “Interaction” Manager • Database connection management • Database connection pooling • Results caching etc • Session/State Manager • Manages state/session information

  20. Generic Web Application Server Functionality Web Application Server EnterpriseAdapters Data storeAdapters MiddlewareAdapters Business Logic StateMgmt. SessionMgmt. WorkloadMgmt. ProcessMgmt. RulesEngine Web Server Presentation Logic, HTML Page Server Web Browser

  21. WAS Application Server Products • Secant: Extreme Server • Bluestone: Sapphire/Web • Gemstone J • Sun: NetDynamics • BEA: WebLogic Server • Oracle Application Server • Sybase: Enterprise Application Server • Netscape Application Server • IBM: WebSphere • Silverstream Software: SilverStream • Novera: Jbusiness • Persistence: PowerTier • Progress: Apptivity • Inprise Application Server • Forte: SynerJ • Apple: WebObjects • Information Builders: Parlay

  22. Web Integration(2) via Web-Enabled Message Brokers Web Browser HTML RDBMS Web Browser Flow Control Transfor- mation Manage-ment Apps Apps HTML Apps Apps Web Browser HTML

  23. Web Application Servers vs. OTMs • Web Application Server strength: • Integrated development tools for Web-based applications • Some provide rich set of classes / frameworks • Address specific requirements of Web-based applications (e.g. state & session management) • OTM strength: • Support for distributed transactions (ACID properties) • Proven scalability • 24 x 7 availability • Most WAS vendors focus on Java/EJB - OTMs provide wider choice of language support and runtime environments

  24. Combining Web Application Servers and OTMs NetworkComputing (NC)Clients WebServer CGI WebBrowser: NetscapeorInternetExplorer NSAPI/ISAPI Servlets ObjectTransactionMonitor(OTM) WAS WASApp GUIClients

  25. Web Application Server vs. OTM Evolution WAS OTM Web Security Back-end Security Web Server Integration Middleware Integration HTML Failover/ Recovery Scalability Java Result Caching IIOP Auditing & Logging State Management Transactions Session Management Availability

  26. Basic 3-tier CGI/HTTP Client/Server Architecture HTTP Server Web Browser Internet HTML docs HTTP HTML HTTP RDBMS SQL API CGI/ ISAPI RDBMS Apps SQL API Tier 2 Application Logic Tier 1 GUI Tier 3 Data

  27. Integrating Back-end Databases Web browser Web server document report spreadsheet image audio video animation static content CGI NSAPI ISAPI dynamic content Database Gateway Web Server-side Gateway Multi media data • Universal data access • Universal and uniform access to diverse data sources • not just the popular relational databases • It is estimated that 65% of corporate data are not stored in relational databases

  28. Basic 3-tier CGI/HTTP Architecture HTTP Server Order/Entry database Web Browser Internet HTML docs Order pizza HTML Order pizza Order pizza Warehouse database Pizza can be delivered @ 19:15, but we’re out of olives Can order be fulfilled? CGI Workforce Scheduling database Apps When can pizza be delivered? Tier 1 Tier 2 Tier 3

  29. Basic 3-tier CORBA/Java Client/Server Architecture Internet WAS Web Browser CORBA IIOP RDBMS CORBA CORBA ORB HTML Java CORBA IIOP JDBC Server Objects Tier 2 Application Logic Tier 1 GUI Tier 3 Data

  30. Basic 3-tier CORBA/Java Client/Server Architecture RDBMS Type A HTTP Server (1) Get HTML Page HTML docs SQL API CGI/ ISAPI Web Browser (2) Get Applet RDBMS Type B Apps SQL API HTML/ Java CORBA Server (3) Load Applet (4) Invoke CORBA CORBA CORBA ORB (5) CORBA IIOP RDBMS Type C JDBC Server Objects Tier 2 Application Logic Tier 1 GUI Tier 3 Data

  31. Basic 3-tier CGI/HTTP and CORBA Client/Server Architecture RDBMS CORBA Server which interprets HTTP Web Browser Internet HTML docs HTTP HTTP SQL API CGI/ ISAPI HTML RDBMS Apps SQL API CORBA IIOP Web Browser CORBA CORBA IIOP CORBA ORB HTML/ Java RDBMS JDBC Server Objects Tier 2 Application Logic Tier 1 GUI Tier 3 Data

  32. HTTP/CGI versus Java/CORBA ORB’s

  33. Predictions on Java/CORBA Integration • “More than 80 percent of large enterprises will use COM and some aspect of CORBA or IIOP somewhere in their enterprise applications by 2001 (0.8 probability)” • “COM will be functionally complete as an OTM by 1999 and mature enough to support demanding, mainstream, mission-critical applications by 2001 (0.7 probability) • “By 2002, the CORBA and Enterprise JavaBeans programming models will evolve into a common multilingual programming model: Enterprise Beans (0.8 probability)”

  34. Database Integration and Optimization Architectures for Database Middlware

  35. SQL Middleware Models • Single vendor option • Common SQL Interface option • Open SQL Gateway option • Federated Databases

  36. Integrated Single Vendor HTML docs HTTP Server (1) Get HTML Page Web Browser (2) Get Applet HTML/ Java CORBA Server (3) Load Applet (4) Invoke CORBA Server Object Server Object CORBA ORB Server Object Sybase Server (5) CORBA IIOP dblib OpenClient FAP Driver Driver Protocol Protocol TCP/ IP

  37. Middleware Solution#1: Common SQL Interface HTML docs HTTP Server (1) Get HTML Page Dbms Server A FAP A FAP B FAP C Web Browser (2) Get Applet CORBA ORB Driver A Protocol HTML/ Java Server Object Server Object Server Object CORBA Server (3) Load Applet (4) Invoke CORBA JDBC / ODBC Driver A Driver B Driver C (5) CORBA IIOP Protocol Dbms Server C Driver C Protocol

  38. Middleware Solution #2: Open SQL Gateway HTML docs HTTP Server (1) Get HTML Page Dbms Server A Gateway FAP Gateway Server Web Browser (2) Get Applet CORBA ORB Protocol HTML/ Java Server Objects Server Objects Dbms Server B CORBA Server (3) Load Applet (4) Invoke CORBA Common SQL API Gateway Server Gateway Driver Protocol (5) CORBA IIOP Protocol Dbms Server C Gateway Server Protocol

  39. Middleware Solution #3: The Ideal World HTTP Server (1) Get HTML Page Dbms Server A Standard SQL FAP Protocol Web Browser (2) Get Applet CORBA ORB HTML/ Java Appl Appl Dbms Server B CORBA Server (3) Load Applet (4) Invoke CORBA Common SQL API Protocol Global Query Control (5) CORBA IIOP Standard SQL Driver Protocol Dbms Server C Protocol

  40. ODBC Architecture Appl Appl Appl Key Points: • ODBC is a Microsoft extension of the SQL Access Group’s CLI • It provides the possibility for writing DBMS-independent C code • A Driver Manager is used to ensure that the right DBMS-driver is loaded automatically at database connect time • An ODBC driver must provide at the very least ANSI SQL89 functionality • ODBC 2.0 defines 61 API calls divided into: • Core (DB connection, execution, commit, rollback, results handling, exception handling) • Level 1 (access to metadata, BLOB’s, driver specific functions) • Level 2 (cursor support) • ODBC is an example of a CLI that supports non-relational sources e.g. MS Excel spreadsheets. • JDBC support transactions against a DBMS ( ODBC API ODBC Driver Manager Service provider API MS SQL Driver Sybase Driver Oracle Driver ESQL/DRDA NetLib SQL*Net TCP/IP DB2 Sybase Oracle

  41. JDBC Architecture Java Appl Java Appl Java Appl Key Points: • JDBC is a SQL CLI written entirely in Java • It provides the possibility for writing DBMS-independent Java code • A Driver Manager is used to ensure that the right DBMS-driver is loaded automatically at database connect time • JDBC drivers are ODBC-bridged or native • A JDBS driver must provide at the very least ANSI SQL92 Emtry Level functionality • JDBC Interfaces are divided into: • JDBC Core • Java Language Extensions • Java Utility Extensions • SQL Metadata • JDBC support transactions against a DBMS (commit, rollback, auto commit) • JDBC does not support 2-phase commit against multiple databases JDBC API JDBC Driver Manager Service provider API JDBC-ODBC Driver Driver to Sybase Driver to Oracle ODBC Driver NetLib SQL*Net Protocol MS SQL Server Sybase Oracle

  42. Database Integration and Optimization JDBC Scenarios

  43. JDBC Scenario 1: Invoking a SQL Query JDBC Driver Manager Client Connection getConnection Statement createStatement ResultSet executeQuery next getInt getString close close

  44. JDBC Scenario 2: Invoking a Prepared Command Driver Manager Client Connection getConnection PreparedStatement prepareStatement setAutoCommit setInt setShort executeUpdate commit close close

  45. JDBC Scenario 3: Invoking a Stored Procedure JDBC Driver Manager Client Connection getConnection CallableStatement prepareCall registerOutputParameter registerOutputParameter execute getXXX close close

  46. JDBC 2-tier HTML Dbms Server JDBC Driver Manager Dbms Server Driver Driver Tier 1 Client Tier 2 DBMS

  47. JDBC 3-tier (a) HTML Driver Dbms Server ORB ORB JDBC Driver Manager Driver Dbms Server Tier 3 DBMS Tier 2 JDBC Server Tier 1 Client

  48. JDBC 3-tier (b) HTML Driver Dbms Server ORB ORB JDBC Driver Manager Driver Dbms Server Server Objects Tier 3 DBMS Tier 2 Web Server Tier 1 Client

  49. Datbase Integration and Optimization OTM Characteristics - Transactions on the Web

  50. Object Management Architecture Vertical Domain Interfaces Horizontal Interfaces Compound Docs Object Linking Application Objects Common Facilities Object Request Broker Lifecycle Event Naming Persistence Transactions Concurrency Externalization Security Licensing Relationship Trader Messaging Notifications CORBAServices

More Related