Melding Proprietary and Open Source Platform Strategies Joel West San Jose State University, [email protected]

Total Page:16

File Type:pdf, Size:1020Kb

Melding Proprietary and Open Source Platform Strategies Joel West San Jose State University, Joel.West@Sjsu.Edu View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by SJSU ScholarWorks San Jose State University SJSU ScholarWorks Faculty Publications School of Management 2003 How open is open enough?: Melding proprietary and open source platform strategies Joel West San Jose State University, [email protected] Follow this and additional works at: https://scholarworks.sjsu.edu/org_mgmt_pub Recommended Citation Joel West. "How open is open enough?: Melding proprietary and open source platform strategies" Research Policy (2003): 1259-1285. doi:10.1016/S0048-7333(03)00052-0 This Article is brought to you for free and open access by the School of Management at SJSU ScholarWorks. It has been accepted for inclusion in Faculty Publications by an authorized administrator of SJSU ScholarWorks. For more information, please contact [email protected]. How Open is Open Enough? Melding Proprietary and Open Source Platform Strategies Joel West1 College of Business, San José State University, One Washington Square, San José, CA 95192-0070 USA December 31, 2002 Forthcoming in Research Policy special issue on “Open Source Software Development” (Eric von Hippel and Georg von Krogh, editors) Abstract Computer platforms provide an integrated architecture of hardware and software standards as a basis for developing complementary assets. The most successful platforms were owned by proprietary sponsors that controlled platform evolution and appropriated associated rewards. Responding to the Internet and open source systems, three traditional vendors of proprietary platforms experimented with hybrid strategies which attempted to combine the advantages of open source software while retaining control and differentiation. Such hybrid standards strategies reflect the competing imperatives for adoption and appropriability, and suggest the conditions under which such strategies may be preferable to either the purely open or purely proprietary alternatives. Keywords: open source, standards competition, computer architecture, innovation returns Acknowledgments I would like to thank Jason Dedrick, Tineke Egyedi, Scott Ensign and two anonymous reviewers for helpful suggestions and comments, as well as seminar participants at Case Western’s Weatherhead School of Management and the 2002 Academy of Management annual meeting. I am especially grateful to the special issue editors for advice and encouragement that were instrumental in developing the paper. My appreciation goes to the representatives of Apple, IBM and Sun who generously shared their time to both explain various complex technologies and also the institutional relationships behind those technologies. The remaining errors are of course my own. 1 Tel: +1-408-924-7069; fax: +1-408-924-3555. E-mail address: [email protected] prior research to suggest the theoretical 1. Introduction implications of such hybrid strategies. The evolution of the computer industry 2. Proprietary Platform Strategies has been driven by the emergence of standardized platforms which allow modular substitution of complementary assets such as 2.1 Dynamics of Proprietary Platform software and peripheral hardware. Competition The initial platforms were proprietary, in A proprietary platform consists of an which a computer systems manufacturer architecture of related standards, controlled controlled all hardware and software layers by one or more sponsoring firms. For a of the standards architecture. These computer system, the architectural standards platforms were later challenged by two typically encompass a processor, operating hardware-independent operating systems — system (OS), and associated peripherals. Unix and Windows — which reduced Some have also extended the concept of a differentiation between hardware vendors “platform” to include multiple layers of and shifted platform control to the operating software, such as applications that rely on a system vendors. The Unix operating system “middle ware” tool such as Java or a also inspired a more radical shift, the open database (Morris and Ferguson, 1993; source movement in which Linux allowed Bresnahan and Greenstein, 1999; West and users and competitors to control a platform’s Dedrick, 2000). direction. A platform is but a specific example of These various strategies reflect the the general class of technological essential tension of de facto standards innovations studied by Teece (1986), who creation: that between appropriability and links the ability of firms to profit from their adoption. To recoup the costs of developing technological innovations to the a platform, its sponsor must be able to appropriability regime for intellectual appropriate for itself some portion of the property rights (IPR) — either through economic benefits of that platform. But to formal de jure protection (e.g. patents) or obtain any returns at all, the sponsor must through de facto protection such as tacit get the platform adopted, which requires knowledge or trade secrets. Absent such IPR sharing the economic returns with buyers protection, firms selling a given technology and other members of the value chain. can be expected to adopt marginal cost The proprietary and open source pricing and drive profit margins to zero strategies correspond to the two extremes of (Katz and Shapiro, 1986; Beggs and this trade-off. In making a platform strategy Klemperer, 1992). Without appropriability, for the 21st century, leading computer Teece (1986) suggests that firms must use vendors face a dilemma of how much is some combination of speed, timing and luck open enough to attract enough buyers while if they hope to appropriate returns generated retaining adequate returns. by their innovation. First I review the theory and history of Teece (1986) also considers those proprietary computer platform strategies, innovations (such as computer systems) that contrasting that with the Unix-based open require the provision of complementary systems movement. I then examine the assets to commercialize the innovation. origins and motivations of Linux and other When additional investment is required to open source software projects. In three co-specialize the asset to be useful with a abbreviated case studies, I present the hybrid given innovation, the successful adoption of strategies of three platform vendors — the innovation and the related assets are Apple Computer, IBM and Sun mutually reinforcing, providing a positive Microsystems — that combine open source feedback cycle. Thus, to make a successful and proprietary platform strategies in hopes “whole product” solution, the owner of the of obtaining competitive advantage. Finally innovation seeks to attract such an analysis of these cases is combined with complementary assets, in part by sharing the overall returns of the innovation with the West, How Open is Open Enough? Page 2 third party supplier of such assets (Katz and market platforms displaced more specialized Shapiro, 1985; Teece, 1986; Moore, 1991). products, either by providing lower cost or The positive feedback, self-reinforcing addressing a broader range of buyer needs cycle of success between a de facto standard (Morris and Ferguson, 1993). and its co-specialized asset success has been Firms that successfully establish and termed “network externalities” (Katz and maintain a proprietary platform enjoy the Shapiro, 1985) or “demand side economies right to appropriate the returns from a of scale” (Katz and Shapiro, 1986). When success of that platform (Morris and such network effects are coupled with Ferguson, 1993). But platform success is a switching costs between standards and high necessary but not sufficient condition for up front R&D costs, Arthur (1996) predicts profiting from proprietary technology that the dominant technology will enjoy innovation. When competing firms control “increasing returns to scale” that magnify an different layers of the standards architecture, early lead in a technology contest. The platform leadership is unstable because instability and self-reinforcing nature of control of the platform can shift without such a lead has often been referred to as disrupting the buyer’s value proposition. In “tipping” of the contest (e.g. Besen and particular, a firm that can take control of Farrell, 1994). Liebowitz and Margolis access to the complementary assets has an (1999) argue that actual tipping is rare, and incentive to do so to capture the returns from that lasting success is more often explained the platform (Bresnahan and Greenstein, by production economies of scale and firm 1999; West and Dedrick, 2000). execution. In explaining platform success, In the case of computing platforms, most economic research has focused on demand research has focused on one particular type and supply side economies of scale, and the of complementary asset, that of prepackaged broad strategic choices made by sponsoring application software. A computer platform is firms. However, there is also repeated not, in itself, useful without software to evidence that operational execution is solve specific problems. During the 1960s crucial to the relative success or failure of and 1970s, large organizations buying individual platforms (Morris and Ferguson, mainframe computers typically developed 1993; Liebowitz and Margolis, 1999; West, their own custom software. However, the 2003). Also, measures of platform success advent of the mass-market personal have focused on adoption or market share. computers attracted many new users unable The more managerially relevant metric
Recommended publications
  • Validated Products List, 1995 No. 3: Programming Languages, Database
    NISTIR 5693 (Supersedes NISTIR 5629) VALIDATED PRODUCTS LIST Volume 1 1995 No. 3 Programming Languages Database Language SQL Graphics POSIX Computer Security Judy B. Kailey Product Data - IGES Editor U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 July 1995 QC 100 NIST .056 NO. 5693 1995 NISTIR 5693 (Supersedes NISTIR 5629) VALIDATED PRODUCTS LIST Volume 1 1995 No. 3 Programming Languages Database Language SQL Graphics POSIX Computer Security Judy B. Kailey Product Data - IGES Editor U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 July 1995 (Supersedes April 1995 issue) U.S. DEPARTMENT OF COMMERCE Ronald H. Brown, Secretary TECHNOLOGY ADMINISTRATION Mary L. Good, Under Secretary for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY Arati Prabhakar, Director FOREWORD The Validated Products List (VPL) identifies information technology products that have been tested for conformance to Federal Information Processing Standards (FIPS) in accordance with Computer Systems Laboratory (CSL) conformance testing procedures, and have a current validation certificate or registered test report. The VPL also contains information about the organizations, test methods and procedures that support the validation programs for the FIPS identified in this document. The VPL includes computer language processors for programming languages COBOL, Fortran, Ada, Pascal, C, M[UMPS], and database language SQL; computer graphic implementations for GKS, COM, PHIGS, and Raster Graphics; operating system implementations for POSIX; Open Systems Interconnection implementations; and computer security implementations for DES, MAC and Key Management.
    [Show full text]
  • IBM Websphere Studio Application Developer for Windows, Version 4.0 Helps Java Developers to Build, Test, and Deploy J2EE-Based E-Business Applications
    Software Announcement November 6, 2001 IBM WebSphere Studio Application Developer for Windows, Version 4.0 Helps Java Developers To Build, Test, and Deploy J2EE-based e-business Applications Overview flexible source control management, pluggable At a Glance Introducing IBM′s premier Java repositories, as well as adapters development environment for for Concurrent Versioning System WebSphere Studio Application professional developers, the first (CVS) and for Rational ClearCase Developer for Windows, V4.0 product in the WebSphere Studio LT (CCLT) (Application Developer) provides product suite, WebSphere Studio • A comprehensive visual XML an advanced development Application Developer for development environment, environment for J2EE application Windows , V4.0 (Application including components for building development. Developer). DTDs, XML Schemas, XML files, and XSL style sheets Application Developer offers the Application Developer is built on the • Built-in WebSphere test following key functions: WebSphere Studio Workbench, an environment • integrated platform designed to A powerful Java development provide a common set of services Application Developer is next environment, that includes and frameworks unparalleled generation technology for support for JDK 1.3, a development tool integration and VisualAge for Java Enterprise configurable runtime, tool construction. Edition. It combines many popular incremental compilation, features of VisualAge for Java scrapbook, dynamic debugging, Application Developer includes the Enterprise Edition and WebSphere and a Java text editor • following functions: Studio Advanced Edition integrated Advanced Web, Java, and XML development environments • on top of WebSphere Studio An advanced development Workbench. designed to J2SE and J2EE environment for J2EE application specifications development that meets J2SE and Application Developer is focused on • A Relational Schema Center J2EE specifications and EJB optimizing J2EE application (RSC) focused on relational development and deployment and development.
    [Show full text]
  • Solaris 2.5 Software Developer Kit Introduction
    Solaris 2.5 Software Developer Kit Introduction 2550 Garcia Avenue Mountain View, CA 94043 U.S.A. A Sun Microsystems, Inc. Business 1995 Sun Microsystems, Inc. 2550 Garcia Avenue, Mountain View, California 94043-1100 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Portions of this product may be derived from the UNIX® system, licensed from UNIX Systems Laboratories, Inc., a wholly owned subsidiary of Novell, Inc., and from the Berkeley 4.3 BSD system, licensed from the University of California. Third-party software, including font technology in this product, is protected by copyright and licensed from Sun’s Suppliers. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227-19. The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications. TRADEMARKS Sun, Sun Microsystems, the Sun logo, SunSoft, the SunSoft logo, Solaris, SunOS, OpenWindows, DeskSet, ONC, ONC+, NFS, SunExpress, ProCompiler, XView, ToolTalk, XGL, XIL, Solaris VISUAL, Solaris PEX, and AnswerBook are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. CatalystSM is a service mark of Sun Microsystems, Inc.
    [Show full text]
  • ¢¡¤ £¦ ¥ ¡ £ ¥ ¡ £ ¥ ¡ £ ¥ Red Hat §© ¨ / ! " #%$'& ( ) 0 1! 23 % 4'5 6!7 8 9 @%
    ¢¡¤£¦¥ ¢¡¤£¦¥ ¢¡¤£¦¥ Subscription Agreement ¢¡¤£¦¥ ! PLEASE READ THIS AGREEMENT CAREFULLY BEFORE Red Hat §©¨ / PURCHASING OR USING RED HAT PRODUCTS AND "# $% &' ()*+ §©¨ ,- . Red Hat / # # SERVICES. BY USING OR PURCHASING RED HAT # 2©3 456 7 80 9: /.10 PRODUCTS OR SERVICES, CLIENT SIGNIFIES ITS ASSENT ;< 2=©>0 ?@ 'A BC© DE F©G ?1 . TO THIS AGREEMENT. IF YOU ARE ACTING ON BEHALF HI BC© D©: J !K CLM NO1 (P4 Q1RK HI OF AN ENTITY, THEN YOU REPRESENT THAT YOU HAVE STU >0 VWK XY Z1K F©G THE AUTHORITY TO ENTER INTO THIS AGREEMENT ON . 456 , §©¨ ,- M X [!\>0 BEHALF OF THAT ENTITY. IF CLIENT DOES NOT ACCEPT 45©3 Red Hat / THE TERMS OF THIS AGREEMENT, THEN IT MUST NOT PURCHASE OR USE RED HAT PRODUCTS AND SERVICES. @ = ©] ^ _`a b c d e e f gf g 3 e f gf g This Subscription Agreement, including all schedules and e (“ ”) Red Hat Limited hi appendices hereto (the "Agreement"), is between Red Hat # Y j § VWK X k (“Red Hat”) ] Red Hat Limited, Korea Branch ("Red Hat") and the purchaser or user of # §©¨ ©9 9 l ml m n CLo0 l m / (“ l m ”) . Red Hat products and services that accepts the terms of this # pq/r stvustvu 3 456 w,- stvustvu (“ ”) h h Agreement (“Client”). The effective date of this Agreement # !K X k r!9x 456 §©¨ Red Hat / (“Effective Date”) is the earlier of the date that Client signs or h 0 y z{ + |} accepts this Agreement or the date that Client uses Red Hat's r!9 . products or services.
    [Show full text]
  • Introducing Linux on IBM Z Systems IT Simplicity with an Enterprise Grade Linux Platform
    Introducing Linux on IBM z Systems IT simplicity with an enterprise grade Linux platform Wilhelm Mild IBM Executive IT Architect for Mobile, z Systems and Linux © 2016 IBM Corporation IBM Germany What is Linux? . Linux is an operating system – Operating systems are tools which enable computers to function as multi-user, multitasking, and multiprocessing servers. – Linux is typically delivered in a Distribution with many useful tools and Open Source components. Linux is hardware agnostic by design – Linux runs on multiple hardware architectures which means Linux skills are platform independent. Linux is modular and built to coexist with other operating systems – Businesses are using Linux today. More and more businesses proceed with an evolutionary solution strategy based on Linux. 2 © 2016 IBM Corporation What is IBM z Systems ? . IBM z Systems is the family name used by IBM for its mainframe computers – The z Systems families were named for their availability – z stands for zero downtime. The systems are built with spare components capable of hot failovers to ensure continuous operations. IBM z Systems paradigm – The IBM z Systems family maintains full backward compatibility. In effect, current systems are the direct, lineal descendants of System/360, built in 1964, and the System/370 from the 1970s. Many applications written for these systems can still run unmodified on the newest z Systems over five decades later. IBM z Systems variety of Operating Systems – There are different traditional Operating Systems that run on z Systems like z/OS, z/VSE or TPF. With z/VM IBM delivers a mature Hypervisor to virtualize the operating systems.
    [Show full text]
  • The Future of Business Using Enterprise Server
    Market Review Market Review Paper by Bloor Author David Norfolk Publish date June 2021 The Future of Business …using Enterprise Server 3.0 Services A company has to stay“ in business while modernising its systems and any modernisation must have a clearly documented business case and properly managed risk. What this means is that migrating a working system to a new platform may not be a good use of resources, especially as alternative modernisation options (such as the provision of cloud APIs or Application Programming Interfaces) are available. ” Executive summary he Future of Business will Well, the nub of the business issue we be largely built on the past, spotlight here is that migration to Cloud T for existing companies. is often recommended simplistically as Modernisation of what you have already, a platform for future business, almost as presumably “fit for current purpose” (or you a fashion option, with implied promises wouldn’t be in business) avoids waste and of ultimate agility, elastic capabilities mitigates certain classes of risk (although, without limits and low cost; but the if not done properly, it can add new risks). actuality is often different – and never Modernisation, of course, implies fit for quite being able to complete a migration evolution and change – once modernised, off Enterprise Server 3.0, because the you will be making further changes to business realities won’t let you, is accommodate new business. probably the most expensive scenario Modernisation of what For big enterprises, the world still runs of all. Cloud provides a wide choice of you have already,“ on very large, very resilient, servers – often platforms, some with innovative and presumably “fit for current referred to as “mainframes”, although attractive characteristics, but three truths Bloor prefers the term Enterprise Server remain important: purpose” (or you wouldn’t be in business) avoids 3.0.
    [Show full text]
  • Chapter 1. Origins of Mac OS X
    1 Chapter 1. Origins of Mac OS X "Most ideas come from previous ideas." Alan Curtis Kay The Mac OS X operating system represents a rather successful coming together of paradigms, ideologies, and technologies that have often resisted each other in the past. A good example is the cordial relationship that exists between the command-line and graphical interfaces in Mac OS X. The system is a result of the trials and tribulations of Apple and NeXT, as well as their user and developer communities. Mac OS X exemplifies how a capable system can result from the direct or indirect efforts of corporations, academic and research communities, the Open Source and Free Software movements, and, of course, individuals. Apple has been around since 1976, and many accounts of its history have been told. If the story of Apple as a company is fascinating, so is the technical history of Apple's operating systems. In this chapter,[1] we will trace the history of Mac OS X, discussing several technologies whose confluence eventually led to the modern-day Apple operating system. [1] This book's accompanying web site (www.osxbook.com) provides a more detailed technical history of all of Apple's operating systems. 1 2 2 1 1.1. Apple's Quest for the[2] Operating System [2] Whereas the word "the" is used here to designate prominence and desirability, it is an interesting coincidence that "THE" was the name of a multiprogramming system described by Edsger W. Dijkstra in a 1968 paper. It was March 1988. The Macintosh had been around for four years.
    [Show full text]
  • Unravel Data Systems Version 4.5
    UNRAVEL DATA SYSTEMS VERSION 4.5 Component name Component version name License names jQuery 1.8.2 MIT License Apache Tomcat 5.5.23 Apache License 2.0 Tachyon Project POM 0.8.2 Apache License 2.0 Apache Directory LDAP API Model 1.0.0-M20 Apache License 2.0 apache/incubator-heron 0.16.5.1 Apache License 2.0 Maven Plugin API 3.0.4 Apache License 2.0 ApacheDS Authentication Interceptor 2.0.0-M15 Apache License 2.0 Apache Directory LDAP API Extras ACI 1.0.0-M20 Apache License 2.0 Apache HttpComponents Core 4.3.3 Apache License 2.0 Spark Project Tags 2.0.0-preview Apache License 2.0 Curator Testing 3.3.0 Apache License 2.0 Apache HttpComponents Core 4.4.5 Apache License 2.0 Apache Commons Daemon 1.0.15 Apache License 2.0 classworlds 2.4 Apache License 2.0 abego TreeLayout Core 1.0.1 BSD 3-clause "New" or "Revised" License jackson-core 2.8.6 Apache License 2.0 Lucene Join 6.6.1 Apache License 2.0 Apache Commons CLI 1.3-cloudera-pre-r1439998 Apache License 2.0 hive-apache 0.5 Apache License 2.0 scala-parser-combinators 1.0.4 BSD 3-clause "New" or "Revised" License com.springsource.javax.xml.bind 2.1.7 Common Development and Distribution License 1.0 SnakeYAML 1.15 Apache License 2.0 JUnit 4.12 Common Public License 1.0 ApacheDS Protocol Kerberos 2.0.0-M12 Apache License 2.0 Apache Groovy 2.4.6 Apache License 2.0 JGraphT - Core 1.2.0 (GNU Lesser General Public License v2.1 or later AND Eclipse Public License 1.0) chill-java 0.5.0 Apache License 2.0 Apache Commons Logging 1.2 Apache License 2.0 OpenCensus 0.12.3 Apache License 2.0 ApacheDS Protocol
    [Show full text]
  • Open Source Software Notice
    Open Source Software Notice This document describes open source software contained in LG Smart TV SDK. Introduction This chapter describes open source software contained in LG Smart TV SDK. Terms and Conditions of the Applicable Open Source Licenses Please be informed that the open source software is subject to the terms and conditions of the applicable open source licenses, which are described in this chapter. | 1 Contents Introduction............................................................................................................................................................................................. 4 Open Source Software Contained in LG Smart TV SDK ........................................................... 4 Revision History ........................................................................................................................ 5 Terms and Conditions of the Applicable Open Source Licenses..................................................................................... 6 GNU Lesser General Public License ......................................................................................... 6 GNU Lesser General Public License ....................................................................................... 11 Mozilla Public License 1.1 (MPL 1.1) ....................................................................................... 13 Common Public License Version v 1.0 .................................................................................... 18 Eclipse Public License Version
    [Show full text]
  • Installing Mac OS X Developer Preview 2
    LL0113.Book Page 1 Tuesday, October 12, 1999 1:09 PM Installing Mac OS X Developer Preview 2 LL0113.Book Page 2 Tuesday, October 12, 1999 1:09 PM K Apple Computer, Inc. © 1999 Apple Computer, Inc. All rights reserved. Under the copyright laws, this manual may not be copied, in whole or in part, without the written consent of Apple. Your rights to the software are governed by the accompanying software license agreement. The Apple logo is a trademark of Apple Computer, Inc., registered in the U.S. and other countries. Use of the “keyboard” Apple logo (Option-Shift-K) for commercial purposes without the prior written consent of Apple may constitute trademark infringement and unfair competition in violation of federal and state laws. Every effort has been made to ensure that the information in this manual is accurate. Apple is not responsible for printing or clerical errors. Apple Computer, Inc. 1 Infinite Loop Cupertino, CA 95014-2084 408-996-1010 http://www.apple.com Apple, the Apple logo, AppleTalk, AppleVision, FireWire, Mac, Macintosh, PowerBook, and Power Macintosh are trademarks of Apple Computer, Inc., registered in the U.S. and other countries. Disk First Aid, Finder, iMac, and Power Mac are trademarks of Apple Computer, Inc. PostScript is a trademark of Adobe Systems, Inc. OpenGL is a registered trademark of Silicon Graphics, Inc. Other company and product names mentioned herein are trademarks of their respective companies. Mention of third-party products is for informational purposes only and constitutes neither an endorsement nor a recommendation. Apple assumes no responsibility with regard to the performance or use of these products.
    [Show full text]
  • An Introduction to Linux and Open Source
    IBM Systems and Technology Group An Introduction to Linux and Open Source Jim Elliott Consulting Sales Specialist – System z Product Manager – System z Operating Systems IBM Canada Ltd. 1 SHARE 109 - Session 9200 2007-08-13 © 2007 IBM Corporation IBM Systems and Technology Group 9200 – An Introduction to Linux and Open Source Linux and Open Source continue to see substantial growth around the world This session will provide an overview of Open Source and an introduction to Linux (including concepts and terminology) Jim will also provide an overview of Novell's SUSE Linux Enterprise (SLE) 10 and Red Hat Enterprise Linux (RHEL) 5 2 SHARE 109 - Session 9200 2007-08-13 IBM Systems and Technology Group Topics Introduction to Open Source Introduction to Linux Novell SUSE Linux Enterprise 10 Red Hat Enterprise Linux 5 Linux and Open Source on the Web at IBM 3 SHARE 109 - Session 9200 2007-08-13 IBM Systems and Technology Group Linux user presentations on Wednesday All sessions on the 3rd floor, Ford A&B Session Speaker Title 9215 Marcy Cortes – Penguins Board the Stagecoach 1:30pm Wells Fargo for the Linux Frontier: A User Experience with Linux on zSeries 9230 Alain Leclerc – How to Rise Above the Challenges 3:00pm CSPQ and of Deploying z/VM and Linux on David Kreuter – the Mainframe and Thrive VM Resources 9231 Alain Leclerc – Building a Strong z/VM and Linux 4:30pm CSPQ and Architecture on the Mainframe David Kreuter – VM Resources 4 SHARE 109 - Session 9200 2007-08-13 IBM Systems and Technology Group Linux user presentations on Thursday
    [Show full text]
  • Introducing... the IBM Toolbox for Javatm
    Session Number: 403552 Introducing... The IBM Toolbox for Java TM Jeff Lee ([email protected]) © 2010 IBM Corporation IBM Power Systems IBM Toolbox for Java™ What is the Toolbox/JTOpen? A set of Java classes and utilities which provide access to IBM i® data and resources class { Integer id; String name; String address; BigDecimal balance; String ccnumber; String expdate; } 2 © 2010 IBM Corporation 1 IBM Power Systems IBM Toolbox for Java The big picture - Client/Server Your Java TM program IBM Toolbox for Java Java Virtual Machine TCP/IP IBM i Access for Windows is not required! TCP/IP IBM i Host Servers *PGM IFS IBM i data and resources DB2/400 *CMD 3 © 2010 IBM Corporation IBM Power Systems IBM Toolbox for Java The big picture - Toolbox and data on same IBM i Your JavaTM program IBM Toolbox for Java TCP/IP JNI IBM i Host Servers IFS *PGM IBM i data and resources DB2/400 *CMD 4 © 2010 IBM Corporation 2 IBM Power Systems IBM Toolbox for Java Using the Toolbox in client/server applications • Toolbox installed on client • Java application runs on client • IBM i Access for Windows is not required • The same Java application runs on any client with a Java-compatible JVM! TCP/IP • Server running IBM i • Uses existing IBM i host servers • IBM i Java Virtual Machine (JVM) is not required on the server 5 © 2010 IBM Corporation IBM Power Systems IBM Toolbox for Java Using the Toolbox in server applications • Toolbox installed on IBM i • Java application runs on IBM i • Use Toolbox instead of JNI • "Local" sockets used to communicate between Toolbox
    [Show full text]