DOCSLIB.ORG

Extending the Got Model Into a Multi-Language, Multi-Platform Distributed System Through Interoperable Spacetime Dataframes

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Extending the Got Model Into a Multi-Language, Multi-Platform Distributed System Through Interoperable Spacetime Dataframes UNIVERSITY OF CALIFORNIA, IRVINE Extending the GoT model into a multi-language, multi-platform distributed system through interoperable Spacetime dataframes THESIS submitted in partial satisfaction of the requirements for the degree of MASTER OF SCIENCE in Software Engineering by Shrijith Saraswathi Venkatramana Thesis Committee: Cristina Videira Lopes, Chair Sam Malek James A. Jones 2021 © 2021 Shrijith Saraswathi Venkatramana TABLE OF CONTENTS Page LIST OF FIGURES v LIST OF TABLES vi ACKNOWLEDGMENTS vii ABSTRACT OF THE THESIS viii 1 Introduction 1 2 Related Work 5 2.1 RPC/Distributed Objects . .6 2.2 Message-Oriented . .7 2.3 Publish-Subscribe . .8 2.4 Tuple Spaces . .8 3 The GoT Distributed Computing Model 10 3.1 GoT, Git but for Objects . 11 3.2 GoT Example: Simplified Space Race . 11 3.2.1 Data Model . 13 3.2.2 Server Node: Physics Simulator . 14 3.2.3 Client Node: Player . 15 3.2.4 Conflict Detection and Resolution . 16 3.3 Extending Spacetime into a multi-language, multi-platform system . 17 4 Designing an Interface Definition Language for GoT 18 4.1 The Purpose Behind Creating Interface Definition Languages . 18 4.2 A Brief History of Interface Definition Languages . 19 4.3 Observations on Earlier Systems . 21 4.3.1 Case Study: Technical Issues with the CORBA API . 21 4.4 GoT IDL and Code Generator . 22 4.4.1 Overview . 22 4.4.2 Example Usage . 22 4.4.3 Architecture . 25 4.4.4 Implementation . 25 ii 5 Generic Dataframe Communication Protocol in GoT 28 5.1 Interoperability in CORBA . 28 5.1.1 Object Request Broker (ORB) . 28 5.1.2 Generic Inter-ORB Protocol (GIOP) . 29 5.1.3 Common Data Representation (CDR) . 30 5.2 GoT Communication Protocol . 31 5.2.1 Data Format . 31 5.2.2 Fetch Cycle . 32 5.2.3 Push Cycle . 35 6 Support for Spacetime Dataframes in the Browser 38 6.1 Extended Spacetime Abstraction Layers Overview . 40 6.2 WebAssembly (WASM) . 41 6.3 Emscripten . 42 6.4 The Bindings . 42 6.4.1 Backend Dataframe Inner Bindings (Python bindings) . 43 6.4.2 WASM Dataframe Inner Bindings (Embind) . 44 6.5 Backend Dataframe Core . 45 6.6 Websockify and Network Protocol Compatibility . 46 7 Validation: Building an Online Presence Application 47 7.1 Application Requirements . 47 7.2 Generic Interface Design for the Web Presence Application . 48 7.2.1 Generated Python Class: IPresence.py . 49 7.2.2 Generated Typescript Class: IPresence.ts . 49 7.3 Implementing Application Logic Using the Generated Classes . 51 7.3.1 Client Logic in the Browser Using Typescript Binding . 51 7.3.2 Server Logic in the Backend Using Python Binding . 53 7.4 Websockify: Translate Between WebSockets and POSIX Network Calls . 54 7.5 Result . 55 8 Discussion: Comparison with Parse Platform 56 8.1 Parse Platform Architecture . 58 8.2 Implementing the Web Presence Application in Parse Platform . 58 8.3 Developer API Comparison for Extended Spacetime and Parse Platform . 60 8.4 Feature Comparison for Extended Spacetime and Parse Platform . 61 9 Future Work and Conclusion 64 9.1 Future Work . 64 9.1.1 Object Persistence . 64 9.1.2 Advanced Object Queries . 64 9.1.3 More Language Bindings and Runtimes . 65 9.1.4 Class Level Permissions and ACLs . 65 9.1.5 Advanced Data Types . 65 9.2 Conclusion . 65 iii Bibliography 67 iv LIST OF FIGURES Page 1.1 Extended Spacetime Architecture . .2 2.1 A high-level overview of middleware systems . .6 3.1 Structure of a GoT Node. Arrows denote the direction of data flow. 12 4.1 High level overview of GoT IDL and code generator . 25 4.2 Details of IDL parser and code generator . 26 5.1 The fetch cycle sequence . 33 5.2 The push cycle sequence . 36 6.1 Detailed Layered Spacetime Architecture for enabling heterogeneous function- ality ........................................ 39 6.2 Extended Spacetime bindings: purpose and implementation technologies . 43 7.1 A sample interaction with the Web Presence Application . 55 8.1 Parse Platform Architecture . 57 v LIST OF TABLES Page 1.1 Contribution Details . .3 3.1 API Table for a Dataframe . 12 4.1 History of IDLs in the context of their respective environments . 20 5.1 GoT Protocol Data format . 32 8.1 Application Developer API comparison for Extended Spacetime and Parse Platform . 60 8.2 Summary of comparison between Spacetime and Parse Platform . 61 vi ACKNOWLEDGMENTS I would like to thank my advisor Professor Cristina V. Lopes for her constant support and guidance. I would also like to express my gratitude to Rohan Achar for introducing me to the subject, mentoring me throughout and also for various code contributions. And I want to thank Xiaochin Yu for providing valuable code contributions to the framework's core and technical insights. vii ABSTRACT OF THE THESIS Extending the GoT model into a multi-language, multi-platform distributed system through interoperable Spacetime dataframes By Shrijith Saraswathi Venkatramana Master of Science in Software Engineering University of California, Irvine, 2021 Cristina Videira Lopes, Chair Over the years, the computing landscape at large has become more diverse and heterogeneous in terms of programming languages, operating systems, networking methods, and hardware. With such increasing heterogeneity, any new distributed programming model needs to func- tion successfully across the gamut of languages and platforms. The Global Object Tracker (GoT) is a recently introduced distributed programming model, initially implemented as the Spacetime framework in a single implementation language { Python. In this thesis, we explore the possibility and feasibility of extending Spacetime into a multi-language, multi- platform distributed system through a combination of generic and platform-specific tech- niques. In particular, I explain the design of an Interface Definition Language (IDL) for GoT, in the backdrop of historically significant IDLs. Moreover, we explore the underlying protocol defined in GoT which enables interoperability among heterogeneous components. The thesis is validated by demonstrating a simple Web Presence application where much of the complexity emerging due to heterogeneity is hidden from the application developer. The complexity hiding in the example application is explained in the context of a layered archi- tecture. Moreover, we compare the extended Spacetime framework with the Parse Platform, a contemporary heterogeneous distributed system originally from Facebook. viii Chapter 1 Introduction The Global Object Tracker (GoT) is a recently introduced distributed programming model [13, 12]. During initial introduction, it was implemented in a single implementation language { Python. One of the important challenges for a distributed programming model to re- solve is that of heterogeneity of languages, platforms, and systems. This thesis explores the possibility and feasibility of extending GoT's initial implementation, Spacetime, into a multi-language, multi-platform distributed system. This thesis aims to establish the feasibility of extending Spacetime into a multi-language and multi-platform distributed system through a combination of generic and platform-specific techniques. We go into the details of designing an interface definition language, the protocol underlying the GoT programming model, and platform specific concerns such as networking compatibility. The system is validated by building an application on top of the extended Spacetime framework. Moreover, a comparison with a contemporary system, Parse Platform is included. The extended Spacetime framework described in this thesis in particular takes advantage of various techniques to enable interoperability: 1 Figure 1.1: Extended Spacetime Architecture 2 • Specifying and using an Interface Definition Language (IDL) and accompanying code generator • Taking advantage of GoT's flexible and platform independent protocol for dataframe communication • Building a common C++ core into multiple target platforms • Accessing the common core through language and platform dependent binding tech- niques A high level overview of the extended Spacetime architecture is shown in Figure 1.1. All the aforementioned techniques are represented as various components in the architecture diagram, and subsequent chapters will cover each component in detail. This thesis has benefited greatly from the contributions of various people as detailed in Table 1.1. Table 1.1: Contribution Details Extended Spacetime Component Contributor Version graph core in C++ Xiaochin Yu Python bindings and GoT protocol specification Rohan Achar The rest of the thesis is organized as follows. In Chapter 2, I discuss related work. Chap- ter 3 describes the original GoT programming model and an example application designed for its implementation framework, Spacetime. In Chapter 4, a historical study of IDLs is combined with the design of an IDL for Spacetime. Chapter 5 describes the generic commu- nication protocol in GoT that enables interoperability. Chapter 6 explains how Spacetime was extended to the browser. Chapter 7 describes the validation of the overall framework through an example Web Presence application. Chapter 8 compares Extended Spacetime to 3 the Parse Platform. Chapter 9 outlines Future work and the conclusion. 4 Chapter 2 Related Work As the heterogeneity of components and platforms increase in the computing landscape, successful interoperability is a requirement for any new distributed model. Interoperability of components in complex distributed systems has been a topic of study for quite a while [14]. A very high-level overview of traditional middlware is shown in Figure 2.1. We see that various platform variations are hidden from the application through the middleware abstraction. Extended Spacetime, while based on a uniquely Git-inspired model, still shares many of similarities with traditional interoperability middleware. These traditional middleware systems can be divided into various categories such as [15]: • RPC/Distributed Objects • Message-based Systems • Publish-Subscribe Systems • Tuple Spaces 5 Figure 2.1: A high-level overview of middleware systems 2.1 RPC/Distributed Objects The Remote Procedure Call (RPC) based Distributed Objects paradigm is the oldest form of distributed systems and was introduced as early as 1988 in the form of Network Computing Architecture (NCA) [18].
Load more

Recommended publications
  • Creating Dynamic Web-Based Reporting Dana Rafiee, Destiny Corporation, Wethersfield, CT
    Creating Dynamic Web-based Reporting Dana Rafiee, Destiny Corporation, Wethersfield, CT ABSTRACT OVERVIEW OF SAS/INTRNET SOFTWARE In this hands on workshop, we'll demonstrate and discuss how to take a standard or adhoc report and turn it into a web based First, it is important to understand SAS/INTRNET software and its report that is available on demand in your organization. In the use. workshop, attendees will modify an existing report and display the results in various web based formats, including HTML, PDF Three components are required for the SAS/INTRNET software and RTF. to work. INTRODUCTION 1) Web Server Software – such as Microsoft’s Personal To do this, we’ll use Dreamweaver software as a GUI tool to Web Server/Internet Information Services, or the create HTML web pages. We’ll use SAS/Intrnet software as a Apache Web Server. back end tool to execute SAS programs with parameters selected on the HTML screen presented to the user. 2) Web Browser – Such as Microsoft’s Internet Explorer or Netscape’s Navigator. Our goal is to create the following screen for user input. 3) SAS/INTRNET Software – Called the Application Dispatcher. It is composed of 2 pieces. o SAS Application Server – A SAS program on a Server licensed with the SAS/INTRNET Module. o Application Broker – A Common Gateway Interface (CGI) program that resides on the web server and communicates between the Browser and the Application Server. These components can all reside on the same system, or on different systems. Types of Services 1) Socket Service: is constantly running, waiting for incoming Transactions.
    [Show full text]
  • Modern Web Application Frameworks
    MASARYKOVA UNIVERZITA FAKULTA INFORMATIKY Û¡¢£¤¥¦§¨ª«¬­Æ°±²³´µ·¸¹º»¼½¾¿Ý Modern Web Application Frameworks MASTER’S THESIS Bc. Jan Pater Brno, autumn 2015 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or ex- cerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Bc. Jan Pater Advisor: doc. RNDr. Petr Sojka, Ph.D. i Abstract The aim of this paper was the analysis of major web application frameworks and the design and implementation of applications for website content ma- nagement of Laboratory of Multimedia Electronic Applications and Film festival organized by Faculty of Informatics. The paper introduces readers into web application development problematic and focuses on characte- ristics and specifics of ten selected modern web application frameworks, which were described and compared on the basis of relevant criteria. Practi- cal part of the paper includes the selection of a suitable framework for im- plementation of both applications and describes their design, development process and deployment within the laboratory. ii Keywords Web application, Framework, PHP,Java, Ruby, Python, Laravel, Nette, Phal- con, Rails, Padrino, Django, Flask, Grails, Vaadin, Play, LEMMA, Film fes- tival iii Acknowledgement I would like to show my gratitude to my supervisor doc. RNDr. Petr So- jka, Ph.D. for his advice and comments on this thesis as well as to RNDr. Lukáš Hejtmánek, Ph.D. for his assistance with application deployment and server setup. Many thanks also go to OndˇrejTom for his valuable help and advice during application development.
    [Show full text]
  • Attacking AJAX Web Applications Vulns 2.0 for Web 2.0
    Attacking AJAX Web Applications Vulns 2.0 for Web 2.0 Alex Stamos Zane Lackey [email protected] [email protected] Blackhat Japan October 5, 2006 Information Security Partners, LLC iSECPartners.com Information Security Partners, LLC www.isecpartners.com Agenda • Introduction – Who are we? – Why care about AJAX? • How does AJAX change Web Attacks? • AJAX Background and Technologies • Attacks Against AJAX – Discovery and Method Manipulation – XSS – Cross-Site Request Forgery • Security of Popular Frameworks – Microsoft ATLAS – Google GWT –Java DWR • Q&A 2 Information Security Partners, LLC www.isecpartners.com Introduction • Who are we? – Consultants for iSEC Partners – Application security consultants and researchers – Based in San Francisco • Why listen to this talk? – New technologies are making web app security much more complicated • This is obvious to anybody who reads the paper – MySpace – Yahoo – Worming of XSS – Our Goals for what you should walk away with: • Basic understanding of AJAX and different AJAX technologies • Knowledge of how AJAX changes web attacks • In-depth knowledge on XSS and XSRF in AJAX • An opinion on whether you can trust your AJAX framework to “take care of security” 3 Information Security Partners, LLC www.isecpartners.com Shameless Plug Slide • Special Thanks to: – Scott Stender, Jesse Burns, and Brad Hill of iSEC Partners – Amit Klein and Jeremiah Grossman for doing great work in this area – Rich Cannings at Google • Books by iSECer Himanshu Dwivedi – Securing Storage – Hackers’ Challenge 3 • We are
    [Show full text]
  • Security Guide Release 21.0.2 F10645-01
    1[Oracle®] AutoVue Client/Server Deployment Security Guide Release 21.0.2 F10645-01 October 2018 Oracle® AutoVue Client/Server Deployment Security Guide Release 21.0.2 F10645-01 Copyright © 1999, 2018, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • Oracle Communications Converged Application Server Datasheet
    ORACLE DATA SHEET Oracle Communications Converged Application Server Oracle Communications Converged Application Server is the industry’s most widely used, fastest and most powerful converged Java EE-SIP-IMS application server, delivering a carrier-grade, open, standards-based development and deployment platform for next-generation and enterprise communications applications. As the foundation for several Oracle service delivery products, it is proven to dramatically lower the cost and time of developing and deploying converged Web-telecom applications for communication service providers, enterprises, and contact centers. KEY FEATURES Migration to Communications Application Platforms • Converged Web-telecom application container based on SIP Servlet, IMS, With the explosive proliferation of IP devices such as smartphones, tablets, TVs, home Java EE, Diameter, JSR 309 Media appliances, gaming consoles, and cars, communications service providers (CSP) and Server Control and Web Services enterprises are faced with the operational and business challenges of delivering • SIP Servlet 2.0 built on Java EE 7 innovative services with maximum profitability. In order to achieve this goal, they are includes efficient optimal POJO and CDI interfaces, concurrent session migrating away from expensive, closed, proprietary, application-specific legacy management, web sockets, and platforms, towards virtualized converged communications application platforms. This standard JSON, XML, JAX, JMS dramatically lowers the time and cost of adding new features and extensions to existing interfaces IP-based communication services. It enables CSPs and enterprises to develop and • Virtual Network Function (VNF) deploy applications on a single, unified platform, and re-use those applications across compliance to Network Function Virtualization multiple networks, including the Web, mobile, virtualized, broadband or fixed networks.
    [Show full text]
  • Dynamic Web Acceleration What Is It, Who Needs It, How It Works
    WHITE PAPER Dynamic Web Acceleration What is it, who needs it, how it works TABLE OF CONTENTS Executive Summary ........................................................................................................ 1 The Problem: Inherent Internet Issues ............................................................................. 2 What Causes the Problem? ............................................................................................ 2 The Solution: Dynamic Web Acceleration ....................................................................... 3 Who Can Benefit from Dynamic Web Acceleration ........................................................ 4 The CDNetworks Approach............................................................................................ 4 Case Study: Streamlining the Retail Supply Chain with Dynamic Web Acceleration ........ 5 Conclusion: A Simple Solution for Enhanced eCommerce, Greater Application Adoption, and Lower Costs ............................................................................................................ 6 Appendix: Key Features of CDNetworks’ Dynamic Web Acceleration Solution ............... 7 About CDNetworks ........................................................................................................ 8 Executive Summary Dynamic web acceleration is a service offered by Content Delivery Networks (CDNs) that enables organizations to quickly and reliably deliver applications and dynamic content from a centralized infrastructure to users around the world.
    [Show full text]
  • Session 1 – Main Theme Introduction to Application Servers
    Application Servers Session 1 – Main Theme Introduction to Application Servers Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Agenda 11 IntroductionIntroduction 22 ApplicationApplication ServersServers KeyKey ConceptsConcepts 33 PatternsPatterns andand ApplicationApplication ServersServers 44 ApplicationApplication ServerServer SupportingSupporting TechnologyTechnology 55 ExpectedExpected ApplicationApplication ServerServer FeaturesFeatures 66 RelatedRelated LifecycleLifecycle andand AdoptionAdoption ProcessesProcesses 77 ConclusionConclusion 2 Icons / Metaphors Information Common Realization Knowledge/Competency Pattern Governance Alignment Solution Approach 33 Who am I? - Profile - ¾ 26 years of experience in the Information Technology Industry, including twelve years of experience working for leading IT consulting firms such as Computer Sciences Corporation ¾ PhD in Computer Science from University of Colorado at Boulder ¾ Past CEO and CTO ¾ Held senior management and technical leadership roles in many large IT Strategy and Modernization projects for fortune 500 corporations in the insurance, banking, investment banking, pharmaceutical, retail, and information management industries ¾ Contributed to several high-profile ARPA and NSF research projects ¾ Played an active role as a member of the OMG, ODMG, and X3H2 standards committees and as a Professor of Computer Science at Columbia initially and New York University since 1997 ¾ Proven record of delivering business
    [Show full text]
  • AJAX: Coming to an Application Near
    Introduction to AJAX Bringing Interactivity & Intuitiveness Into Web Applications By : Bhanwar Gupta SD-Team-Member Jsoft Solutions Applications today • You have two basic choices: Desktop applications and Web applications DesktopDesktop applicationsapplications It usually come on a CD and install completely on your computer. The code that runs these applications resides on your desktop. It is usually pretty fast, has great user interfaces and is incredibly dynamic. WebWeb applicationsapplications It runs on a Web server and you access the application with your Web browser It provides services you could never get on your desktop (think about Amazon.com and eBay). waiting for a server to respond, waiting for a screen to refresh, waiting for a request to come back and generate a new page. ☺☺ AjaxAjax attemptsattempts toto bridgebridge thethe gapgap betwbetweeneen thethe functionalityfunctionality andand interactivityinteractivity What is AJAX ? • A Web development technique for creating interactive web applications IntensionIntension Shift a great deal of interaction to the Web surfer's computer Used to retrieve data and update selected parts of the page without refreshing the entire page Example: Google Suggest, Google Maps ☺☺ IncreaseIncrease thethe WebWeb page'spage's interactivity,interactivity, speespeed,d, andand usability;usability; betterbetter useruser experienceexperience The “birth” of Ajax 3/31/05: Google Pioneers Use of Old Microsoft Tools in New Web Programs “Ajax” “a big step toward the Holy Grail of having the kinds
    [Show full text]
  • Application Servers
    Understanding Application Servers Author: Ajay Srivastava & Anant Bhargava TCS, Jan’03 Background Application servers, whatever their function, occupies a large chunk of computing territory between database servers and the end user. This paper will provide an overview of application server and their role in n-tier applications. Intended Audience The paper is intended for anyone interested in knowing application server architecture and it’s role in web applications. The readers of this paper are not require to have an in -depth knowledge of web applications and related technologies but they are require to have an overview of n -tire web application architecture. History of Application Server In the early days of application servers, it was realised that applications (the programs people were using to get work done) themselves, were becoming bigger and more complex -- both to write and to maintain. At the same time, pressure was increasing for applications to share more of their data and sometimes functionality with other applications. More applications were either located on a network or used networks extensively. It seemed logical to have some kind of program residing on the network that would help share application capabilities in an organised and efficient way -- making it easier to write, manage, and maintain the applications. The end result of this thinking was what is now called an application server. However, these servers first appeared in client/server computing and on LANs. At first, they were often associated with "tiered" applications, when people described the functionality of applications as two-tiered (database and client program), three-tiered (database, client program, and application server), or n-tiered (all the above plus whatever).
    [Show full text]
  • C Server Pages: an Architecture for Dynamic Web Content Generation
    C Server Pages: An Architecture for Dynamic Web Content Generation John Millaway Phillip Conrad Dept. of Computer and Information Sciences Dept. of Computer and Information Sciences Temple University Temple University 1805 N. Broad St. 1805 N. Broad St. Philadelphia, PA 19122 Philadelphia, PA 19122 [email protected] [email protected] ABSTRACT curs heavyweight process creation overhead. Approaches that in- This paper introduces C Server Pages (CSP), a highly efficient ar- volve simple template substitution by the web server itself based on chitecture for the creation and implementation of dynamic web so called server-side includes (SSIs) are lightweight, but not very pages. The CSP scripting language allows dynamic web contents to powerful. Application servers such as ColdFusion [3] introduce a be expressed using a combination of C code and HTML. A novel heavyweight run time layer. Interpreted languages such as Java, feature of CSP is that the C portions of the CSP source file are PHP, and Perl are typically slower than compiled languages such compiled into dynamic load libraries that become part of the run- as C. New languages specifically designed for the generation of ning web server, thus avoiding both the overhead of interpreted lan- server side content present an additional learning curve for already guages such as Perl, Java and PHP, as well as the need to create a overburdened developers [8]. separate process. We present an overview of the architecture and This paper introduces an alternative architecture called C Server implementation, and provide results of performance benchmarks Pages (CSP), based on combining languages familiar to many de- showing that CSP outperforms similar mainstream technologies, velopers: HTML, and C.
    [Show full text]
  • Oracle Application Server Containers for J2EE Servlet Developer's Guide
    Oracle® Application Server Containers for J2EE Servlet Developer’s Guide 10g Release 2 (10.1.2) B14017-02 July 2005 Oracle Application Server Containers for J2EE Servlet Developer’s Guide, 10g Release 2 (10.1.2) B14017-02 Copyright © 2002, 2005, Oracle. All rights reserved. Primary Author: Brian Wright Contributing Author: Tim Smith Contributors: Bryan Atsatt, Ashok Banerjee, Bill Bishop, Olivier Caudron, Cania Chung, Olaf Heimburger, Gerald Ingalls, James Kirsch, Sunil Kunisetty, Philippe Le Mouel, David Leibs, Sastry Malladi, Jasen Minton, Debu Panda, Lenny Phan, Shiva Prasad, Paolo Ramasso, Charlie Shapiro, JJ Snyder, Joyce Yang, Serge Zloto, Sheryl Maring, Ellen Siegal The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S.
    [Show full text]
  • IBM Integrated Web Application Server for I
    Agenda Key: 45CF Session Number: 540194 Integrated Web Application Server for i - Removing Excuses Tim Rowe Web Integration for i T/L [email protected] 8 Copyright IBM Corporation, 2009. All Rights Reserved. This publication may refer to products that are not currently available in your country. IBM makes no commitment to make available any products referred to herein. IBM integrated Web application server for i the ‘on-ramp’ to the Web © 2009 IBM Corporation Agenda – Integrated Web Application Server • Introduction – What is ‘it’ – Why did we add this – Why not just use WebSphere Application Server? • How do I create one – Simply of course • Application deployment – What is supported – What is not supported – How do I get my app deployed • Database – What is supported – How do I use the support © 2009 IBM Corporation Introduction • IBM integrated Web application server for i – Goals • IBM i functional enhancement • The Web container is integrated into the operating system • Easy to use • Simplified access, deployment and management • Small, Less resources • Positioned as ‘on-ramp’ to the Web • Replacement for AFS Tomcat © 2009 IBM Corporation Introduction • Integrated Web application server – What is it? • Web container • Based on the OSGI framework • Supports application packaged in a WAR • Runs IBM Technology for Java (32 –bit) • Supports Java Toolbox and Native DB drivers • Web container for ‘simple’ applications © 2009 IBM Corporation Why is this important to the IBM i? • It runs on our smallest boxes • Simple to use • Easy to install
    [Show full text]