IBM PaaS Strategy for Business Partners

1. IBM PaaS Strategy for Business Partners Sherwood Yao IDR PaaS Strategy Lead syao@us.ibm.com WAP12390-USEN-00

2. The driver behind Cloud and PaaS: outsource as much as you can A Cloud strategy is an outsource strategy, it impacts both revenue and cost Outsource non-core activity to fuel innovation in core competency Enable new cloud optimized business models (subscription, usage based) Reduce time to value to make more money with the same staffing Drive top-line growthandinnovation Simplify the solution stack based on standard, outsource non-core biz Leverage automation and reduced product deployment complexity to reduce cost of delivery/manage apps Use the same product to serve both private and public cloud need Reduce operating costs

3. 2 1 Infrastructure as a Service (PureFlex, VMware) Platform as a Service (PureAS, Force.com) Applications Applications Data Data Runtime Runtime Middleware Middleware O/S O/S Virtualization Virtualization Servers Servers Storage Storage Networking Networking ISV headache Abstracted service value PaaS allows partner outsource ALL non-core-competency Traditional On-Premises Applications ISV core competency Data Runtime Middleware Middleware O/S Virtualization Servers Infrastructure Storage Networking

4. PaaS: three fundamental pillars of abstraction 3 Mobile-delivery abstraction 2 Runtime abstraction 1 DevOps abstraction PureApplication System SmartCloud App Services IBM Worklight IBM Mobile Foundation SmartCloud Foundations SmartCloud App Services App enablement on cloud Workload optimization Multi-channel enablement • Abstract middleware capabilities (JEE, MQ, DBaaS) as services to enable rapid application development • Use predefined application pattern to rapidly migrate legacy application to cloud • Abstract core runtime IT capability as services to enable enterprise deployment with high SLAs • Application created once, runs on both private and public cloud • Abstract mobile delivery capabilities to enable automatic mobile+desktop multi-channel app delivery. • Application created once, runs on all major mobile devices (iOS, Android, blackberry)

5. The way IBM implements abstraction: patterns A Software Application pattern is… a model of a multi-server environment …represented as a file (persistent definition) …which can be interpreted by a deployment tool …and shared between users/teams Software Application Patterns… Can be created in any IBM PaaS dev tools Can be exported and imported for sharing across multiple PaaS systems (including SCAS, IWD, and PureApplication) Are available in two types: Virtual Applications and Virtual Systems

6. OK, now I want enable my app on PaaS, but why IBM? IBM is the only vendor in the PaaS marketplace that provide standard based IaaS + PaaS Cloud services for both public and private cloud Deploy your same app in both private (IBM PureSystems) and public (IBM Smartcloud) We offer full life cycle PaaS to help you build, enable and extend your app on Cloud Enable your app over IBM PaaS takes less than 1 person month Drive top-line growthandinnovation IBM PaaS is based on industry standard, no vendor lock-in cost… lower switching cost Leverage IBM PaaS built in automation to simplify product deployment and reduce cost of delivery/manage apps… lower operation cost Same skill set needed for enabling the app anywhere… lower staffing cost Reduce operating costs

7. Monitoring Lifecycle Management Patterns of Expertise: Proven best practices and expertise for complex tasks learned from decades of client and partner engagements that are captured, lab tested and optimized into a deployable form What is a Pattern? • The pre-defined architecture of an application • For each component of the application (i.e. database, web server, etc) • Pre-installation on an operating system • Pre-integration across components • Pre-configured & tuned • Pre-configured Monitoring • Pre-configured Security • Lifecycle Management • In a deployable form, resulting in repeatable deployment with full lifecycle management • Delivering superior results: • Agility: Faster time-to-value • Efficiency: Reduced costs and resources • Simplicity: Simpler skills requirements • Control: Lower risk and errors

8. Three types of Patterns to choose from: (vary in cloud optimization) Softwareapplication Virtual Appliance Virtual Appliance Virtual Appliance Virtual Appliance Virtual Appliance HTTP Server Application Server Softwareapplication Application Server Operatingsystem Operatingsystem Operatingsystem Operatingsystem Virtual Application Patterns Virtual System Patterns Metadata Metadata Metadata Metadata Virtual Appliances • Highly automated deployments using expert patterns • Business policy driven elasticity • Built for the cloud environment • Leverages elastic workload management services • Standard software installation and configuration on OS • Imagescreated through extend/capture • Traditional administration and management model • Infrastructure driven elasticity • Automated deployment of middleware topologies • Traditional administration and management model • Application and infrastruture driven elasticity Virtual Application Patterns Virtual System Patterns Virtual Appliances Improved TCOvirtualizedapplications Standard TCO existingapplications Best TCO cloudapplications

9. What the business wants… Monitoring Lifecycle Management What’s required…

10. Monitoring Lifecycle Management Built-in Web Application Pattern delivers proven expertise Managed environments scale up and down based upon business SLAs you specify Auto Scaling Failed virtual machines are replaced with new VMs which are configured with the old VM’s identity Failover Web requests are automatically load balanced across multiple virtual application servers Load Balancing ACL’s for application sharing and management access, LDAP integration for application security Security All components of virtual application environments are monitored by PureApplication System Monitoring Built-in components are pre-configured, tuned, and tested to enable efficient, minimal click deployment and single point of maintenance Lifecycle Management

11. How can ISV create patterns to run on IBM PaaS? Start with Virtual App Pattern first Virtual App Pattern (VAP) • Enable your web based app using built in JEE web apppattern directly or create new plugin to fully customize its user experience. • Web app pattern support limited WAS+DB2 configuration • Highest level of built in expertise in deploying and managing elastic workload. Virtual System Pattern (VSP) • Enable your app using bundled HV images AND creating script package. • More flexible WAS+DB2 configuration, ISV can also add its own middleware via customized image • Manual implementation of elasticity and limited built in automation. Recommended

12. IBM Mobile Pattern: the extension of PaaS Web app Web app enabled on IBM Websphere The industry standard #1JEE container, natively supported on SmartCloud Foundation and PureSystems Mobile transformation on IBM Worklight Support iOS, Android, Blackberry - The most complete, extensible environment with maximum per-device optimization Mobile runtime on IBM Mobile Foundation Industry standard mobile device management (MDM) and security management solution (based on Tivoli Endpoint Mgr).

13. what can ISVs do with IBM Worklight • Build and develop mobile apps on a single platform to support multiple devices & BYOD* • Build Native, Hybrid and HTML web-based apps using the same software and skills • Use pre-built interfaces and templates to reduce application development cycle • Securely control access to the corporate network and data • Integrate control of devices and applications through Mobile Device Management (MDM) Native Apps Platform specific. Requires unique expertise but can deliver higher user experience. WEB App Browser access. Written in web technology. Quick and cheap but less powerful than native. Hybrid Apps- Mixed User augments web code with native for unique needs and maximizes user experience Worklight enables ISVs to enter the mobile space easily and quickly * BYOD – Bring Your Own Device

14. Extensibility from the broadest ecosystem is made easy New IBM PureSystems Centre: • Gain access to a broad community of IBM and certified partner expertise • Download optimized, deployable application patterns from 100+ leading ISV partners • Search by solution area, industry or system • Download fixes and patches • Access to developer community Also run your existing applications today*

15. Enterprise PHP workload Your ISV workload Java Enterprise worklad Auto scaling, fast dependable Auto scaling, fast dependable Auto scaling, fast dependable Summary: Key ISV message 1: Flexible. Enable once, deploy anywhere IBM Pattern based PaaS offers ISV maximum flexibility to enable ISV solution on cloud + What: Select your solution Virtual Appliance Factory Virtual System Pattern Virtual Application Pattern How:Select how much cloud optimization Cloud optimized Cloud aware Run-on Cloud Private Cloud Public Cloud + Where:Select where to run your cloud enabled solution Client-managed Service Level Agreements IBM-managed Service Level Agreements

16. Entry Cloud Core Cloud Advanced Cloud Key ISV message 2: Open. IBM is converging our Cloud Management offerings onto a common architecture • SmartCloud and SWG private cloud offering are based on a common, standards based architecture • Entry points and offering packages are modular serving different markets, buyers, and price points • IBM’s recent announcement to join Openstack demonstrate our commitment to open standard SmartCloud Orchestration Control Complexity SmartCloud Provisioning • OSLC Automate Optimized Workloads SmartCloud Entry • OASIS TOSCA Manage Delivery of IT Resources • OpenStack • DMTF CIMI & OVF2.0 • SNIA CDMI Cloud Common Stack Modular Extensible Comprehensive

17. Key ISV message 3: Complete. IBM provides complete PaaS life cycle service to deliver your app to your customer Deployment Cloud Middleware Development Mobile Runtime optimization Virtualization

18. Question? • Please contact Sherwood Yao (syao@us.ibm.com)