Impact2013 tsa 1416--api mgmt

56
© 2013 IBM Corporation Introduction to IBM API Management and What’s New Laura (Olson) Heritage, IBM Product Manager API Management Session :1416

Transcript of Impact2013 tsa 1416--api mgmt

Page 1: Impact2013 tsa 1416--api mgmt

© 2013 IBM Corporation

Introduction to IBM API Management and What’s New Laura (Olson) Heritage, IBM Product Manager API Management

Session :1416

Page 2: Impact2013 tsa 1416--api mgmt

2 2 © 2013 IBM Corporation

Please Note

IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion.

Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision.

The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

Page 3: Impact2013 tsa 1416--api mgmt

3 3 © 2013 IBM Corporation

Agenda

•  Why API Management Is Import

•  Setting the Stage for API Management

•  IBM API Management Solution Overview

•  Demonstration

Page 4: Impact2013 tsa 1416--api mgmt

4 4 © 2013 IBM Corporation

Agenda

•  Why API Management Is Import

•  Setting the Stage for API Management

•  IBM API Management Solution Overview

•  Demonstration

Page 5: Impact2013 tsa 1416--api mgmt

5 5 © 2013 IBM Corporation

Businesses are evolving

Website

Smart Phone

Tablet Partners

Connected Appliances

Connected Cars

Game Consoles

Internet TVs

Trillions  2013  →    

Website

Millions  ~1999  -­‐  2000  

stores (800) ###s web sites

Not  having  an  API  today  is  like  not  having  a  website  in  the  1990s…  

Consumers  expect  to  access  data  any  Gme  across  mulGple  devices  

 Companies  can  re-­‐invent  

interacGons  with  customers,  suppliers  &  partners  

 Explosion  of  potenGal  clients  increases  opportunity,  risk  and  

innovaGon  

Page 6: Impact2013 tsa 1416--api mgmt

6 6 © 2013 IBM Corporation

The Business of APIs

Grow  revenues…  

…  While  reducing  overhead  

“$7bn  worth  of  items  on  eBay  through  APIs”  Mark  Carges  (Ebay  CTO)  

The  API  which  has  easily  10  4mes  more  traffic  then  the  website,  has  been  really  very  important  to  us.”      Biz  Stone  (Co-­‐founder,  TwiKer)  

“The  adopLon  of  Amazon’s  Web  services  is  currently  driving  more  network  acLvity  then  everything  Amazon  does  through  their  tradiLonal  web  sites.”  Jeff  Bar  (Amazon  evangelist)  /  Dion  Hinchcliffe  (Journalist)  

Page 7: Impact2013 tsa 1416--api mgmt

7 7 © 2013 IBM Corporation

Apps, APIs and API Mgmt…

Business Owner IT

Developer

Consumers

New  business  opportuniLes  •   New  markets  •   Increase  customers  •   Enhance  branding  •   CompeLLve  advantage    Extend  development  team  • Increase  innovaLon  • Increase  scale    Partner/supplier    alignment  

Benefits

Challenges  Business  strategy  

 Infrastructure  

•   Security  •   CreaLon  

•   Scalability    

OperaLonal  control  •   Publish  •   Analyze  •   Monitor    

Page 8: Impact2013 tsa 1416--api mgmt

8 8 © 2013 IBM Corporation

APIs are Emerging Across All Industries

Energy and Utilities

Government Healthcare Transportation Retail

Banking Insurance Teleco Chemical/Petroleum Electronics

Page 9: Impact2013 tsa 1416--api mgmt

9 9 © 2013 IBM Corporation

Agenda

•  Why API Management Is Import

•  Setting the Stage for API Management

•  IBM API Management Solution Overview

•  Demonstration

Page 10: Impact2013 tsa 1416--api mgmt

10 10 © 2013 IBM Corporation

Companies Need to Become an Engaging Enterprise

Apps

Customer

Business User

IT

Enterprise

App Developer

• Business Users want to engage Customers in new markets

•  They need to Externalize the Enterprise

•  They need to get Apps in front of these Customers

• Apps need APIs that Externalize the Enterprise

• App Developers use APIs

• App Developers are now External to the Enterprise

•  IT Guys need to secure, scale and support the externalized Enterprise

• Business Users and IT Guys needs Insights so they can respond to business needs

The Platform

Enterprises wants to tap into innovation from a large

community of developers, not just developers they employ

Page 11: Impact2013 tsa 1416--api mgmt

11 11 © 2013 IBM Corporation

11  

SOA Principles are at the Core of the Engaging Enterprise

1960- 1990- 2010- Time

Reach

Transaction Systems

Mainframe, IMS and CICS

WebSphere, Information Management

New Era Platforms

Web, e-business and SOA

Mobile, Cloud, Big Data

Page 12: Impact2013 tsa 1416--api mgmt

12 12 © 2013 IBM Corporation

Performance and scalability are table stakes

•  High Scalability – will your API handle un-expected load?

•  Secure – is it secure for common attacks?

Page 13: Impact2013 tsa 1416--api mgmt

13 13 © 2013 IBM Corporation

Lessons learned

•  Business driven, IT owned Ø Design from the outside-in, not inside-out Ø More than a security gateway Ø New question everyday: strong analytics is a must

•  Design for rapid change Ø Rapid development, independently from core systems Ø Minimize coding"Ø Manage the asset, not the code"

•  Move quickly, think strategically Ø Easy to create, hard to retire Ø Where are your developers? Ø Create your own practice

Page 14: Impact2013 tsa 1416--api mgmt

14 14 © 2013 IBM Corporation

Success Requires Addressing Needs of Multiple Stakeholders

Business  User  •   How  can  I  rapidly  release  &    

update  my  APIs?  •   How  do  I  publicize  my  API?  •   How  do  I  measure  success?  

IT  OperaLons  •   How  do  I  assemble  APIs?  

•   How  do  I  manage  security?  •   How  will  my  infrastructure  scale?  •   How  do  I  measure  performance?  

App  Developer  •   Where  do  I  access  APIs?  •   How  do  I  understand  the  APIs?  •   How  do  I  measure  success?  

Page 15: Impact2013 tsa 1416--api mgmt

15 15 © 2013 IBM Corporation

A Little More Info on the Types Of API Exposures

Public, Open-To-All APIs

Protected, Open-To-Partner APIs

Private, Open-To-Employee APIs

• APIs are open to any developer who wants to sign up

• Apps are more targeted towards end consumers

• The business driver is to engage customers through external developers

• APIs are open to select business partners

• Apps could be targeted at end consumers or business users

• The business driver is usually different, based on the data and type of business of the enterprise

• APIs are exposed only to existing developers within the enterprise

• Apps are usually targeted at employees of the enterprise

• The business driver is more around productivity of employees

Page 16: Impact2013 tsa 1416--api mgmt

16 16 © 2013 IBM Corporation

User Roles Defined AGAIN

Steve Steve is the API Product Manager

Jane Jane is the technical user who creates and manages the APIs from and IT Operations perspective

Will Will has the operations roles and is responsible for administration the systems environments

Joe Joe is the app developer who maybe outside the enterprise or inside the enterprise. He is the consumer of the APIs

Page 17: Impact2013 tsa 1416--api mgmt

17 17 © 2013 IBM Corporation

Agenda

•  Why API Management Is Import

•  Setting the Stage for API Management

•  IBM API Management Solution Overview

•  Demonstration

Page 18: Impact2013 tsa 1416--api mgmt

18 18 © 2013 IBM Corporation

ConnecLvity  &  IntegraLon  •  A single, comprehensive solution to create, socialize, and manage APIs

§  Grow your business by entering the fastest growing channel of APIs quickly.

§  Increase speed of innovation by sourcing all types of developers internally and externally.

§  Connect to business partners in a matter of days not months.

§  What’s new: –  New On-Premise API Management

–  Ability to edit an API implementation while its running and then reactivate to push changes

–  First class support for creating new REST APIs from SOAP based services

–  Support Standard Security Mechanisms for API Management such as Oauth and Basic Auth

–  Enhanced operational metrics

–  Can leverage existing DataPower XI52s or XG45s

Reach new markets

Engage with partners, customers, and employees

Innovate faster

IBM API Management v2.0

Extend Your Services Beyond Your Enterprise

Page 19: Impact2013 tsa 1416--api mgmt

19 19 © 2013 IBM Corporation

Now Available In the Cloud and On-premise

In the cloud On-premise Multi-tenant

1 2

Power by IBM DataPower gateway appliances, the industry leading security & integration gateway appliance

Page 20: Impact2013 tsa 1416--api mgmt

20 20 © 2013 IBM Corporation

20  

Share  with  developers  

3

Create,  assemble  and  define  an  API  

1

Manage  growth  &  analyze  results  

4

Secure  &  scale    the  API  

2

Introducing IBM API Management: “A Complete API Management Solution”

Page 21: Impact2013 tsa 1416--api mgmt

21 21 © 2013 IBM Corporation

User Roles Defined AGAIN

Steve Steve is the API Product Manager

Jane Jane is the technical user who creates and manages the APIs from and IT Operations perspective

Will Will has the operations roles and is responsible for administration the systems environments

Joe Joe is the app developer who maybe outside the enterprise or inside the enterprise. He is the consumer of the APIs

Page 22: Impact2013 tsa 1416--api mgmt

22 22 © 2013 IBM Corporation

Create & Secure… Simple interface accelerates iterative development and deployment of APIs

•  IntuiLvely  and  iteraLvely  define  APIs  and  associated  policies  

•  Rapidly  assemble  APIs  via  configuraLon-­‐  not  coding  

•  Minimize  risk  with  industry  leading  security  &  scalability  

Page 23: Impact2013 tsa 1416--api mgmt

23 23 © 2013 IBM Corporation 23 IBM Confidential – Shared under NDA

Iteratively Create and Expose APIs through Single Simple User Interface

Define

API Developer

Assemble

Meter

Secure Test & Debug

Monitor

Scale

Version

Reduces the time and skill needed to create and manage APIs : •  Assemble the API through configuration

•  Establish entitlement in order to meter API usage

•  Define and Apply Security to the API through an intuitive configuration UI

•  Test and Debug an API through embedded tools •  Monitor the API through operational analytics in

order to spot issues before they occur

•  Scale the API through configurable caching capabilities

•  Copy an APIs configuration to create new versions or a similar API

•  Snapshot versions of the APIs configuration for embedded and controlled change management

Page 24: Impact2013 tsa 1416--api mgmt

24 24 © 2013 IBM Corporation

Easily Define APIs

•  Define the API you wish to expose

•  Then configure the API by proxying an existing REST API or assemble a new API

•  Provide examples of the request and response messages, headers and parameters

Page 25: Impact2013 tsa 1416--api mgmt

25 25 © 2013 IBM Corporation

Assemble New APIs Through Configuration

•  Connect to one or more datasource ‒  DB2 ‒  MySQL ‒  SQL Server ‒  Oracle ‒  Salesforce.com ‒  SOAP to REST ‒  HTTP

•  Drag and connect linking the request and response messages

•  Transform the message elements with a click

Page 26: Impact2013 tsa 1416--api mgmt

26 26 © 2013 IBM Corporation

Meter through API Entitlements

Management of Entitlements:

•  Create an Entitlement once and reuse across several APIs

•  Apply entitlement at API and method (get, put, post,delete) levels

•  Easily change existing entitlements and activate the changes

•  View which APIs the Entitlements are applied to.

Specify Entitlement:

•  Limit based on number of calls

•  Per period of time

•  Specify requirements for App Key, and Secrets

•  Specify an request approval is needed to use this entitlement level

Page 27: Impact2013 tsa 1416--api mgmt

27 27 © 2013 IBM Corporation

Secure with Industry Leading Technology

Basic Auth Support

•  LDAP

•  Authentication URL

Page 28: Impact2013 tsa 1416--api mgmt

28 28 © 2013 IBM Corporation

Secure with Industry Leading Technology

•  Configure your LDAP Server inline or globally and reuse configuration

•  See which APIs are leveraging the LDAP Server

Page 29: Impact2013 tsa 1416--api mgmt

29 29 © 2013 IBM Corporation

Secure with Industry Leading Technology

Simplified OAuth 2.0 through a Configuration Approach

•  Configure an Oauth Profile that can be applied to the APIs

•  View APIs which leverage the OAuth Profile

Page 30: Impact2013 tsa 1416--api mgmt

30 30 © 2013 IBM Corporation

Test APIs Without Leaving the Management Center

•  Get instant feedback on the API

Page 31: Impact2013 tsa 1416--api mgmt

31 31 © 2013 IBM Corporation

31  

Debug an Assembly and Supply Custom Error Message

§ Inspect request, assembly and response messages

§ Define custom error messages

Page 32: Impact2013 tsa 1416--api mgmt

32 32 © 2013 IBM Corporation

Monitor Your APIs to Ensure You Meet the QofS You Defined in Your Entitlements

•  Pinpoint fluctuations

•  Details of the Response time of each API

•  Number of Call Received

•  Export the Analytics

Page 33: Impact2013 tsa 1416--api mgmt

33 33 © 2013 IBM Corporation

Scale at the Click of a Button

API Requests

•  Improve your APIs response time with configurable response caching

Page 34: Impact2013 tsa 1416--api mgmt

34 34 © 2013 IBM Corporation

Version and Snapshot for Simplified Management

•  Edit an API configuration while the API is actively running

•  Push minor changes out to consumer with out large disruptions

•  Version the API Configuration

•  Revert prior version

•  Create a duplicate of the API for a major version change or to create a similar API

Page 35: Impact2013 tsa 1416--api mgmt

35 35 © 2013 IBM Corporation

Promote APIs To Various Environments

•  Promote API definitions to various environments or tenants through export

•  Ability to substitute new values for configuration properties on import

Page 36: Impact2013 tsa 1416--api mgmt

36 36 © 2013 IBM Corporation

User Roles Defined AGAIN

Steve Steve is the API Product Manager

Jane Jane is the technical user who creates and manages the APIs from and IT Operations perspective

Will Will has the operations roles and is responsible for administration the systems environments

Joe Joe is the app developer who maybe outside the enterprise or inside the enterprise. He is the consumer of the APIs

Page 37: Impact2013 tsa 1416--api mgmt

37 37 © 2013 IBM Corporation 37

Socialize... Expose your APIs through a Branded Developer Portal

•  Branded to your company look and feel through configuration •  Quick exploration of API •  Easy developer sign ups •  Features apps built by the developers •  Hooks into social communities •  Enables developers to manage their applications

Page 38: Impact2013 tsa 1416--api mgmt

38 38 © 2013 IBM Corporation 38

Breadth & depth of dW audience ILLUSTRATED BY 2011 TECH TRENDS RESPONDENTS

Socialization Through The Millions of Developers In developerWorks to and collaboration with millions of users to drive adoption of APIs

93 countries

developerWorks by the numbers

4 million unique visitors

a month

1 million registered users

40,000 resources in dW technical library

7 local language sites account for

33% traffic

34 industry awards

APIs need Socialization to Drive Adoption Beyond Individual Portals

38  

Page 39: Impact2013 tsa 1416--api mgmt

39 39 © 2013 IBM Corporation

User Roles Defined AGAIN

Steve Steve is the API Product Manager

Jane Jane is the technical user who creates and manages the APIs from and IT Operations perspective

Will Will has the operations roles and is responsible for administration the systems environments

Joe Joe is the app developer who maybe outside the enterprise or inside the enterprise. He is the consumer of the APIs

Page 40: Impact2013 tsa 1416--api mgmt

40 40 © 2013 IBM Corporation

Manage API’s with Business Controls 40  

Manage Developers •  Approve entitlement

requests •  Send email •  Block a developer •  View usage

Manage External Experience •  Self documenting APIs •  Ability to add samples and

tutorials •  Control Visibility Of APIs

Manage API Entitlement •  Define entitlement criteria •  Assign Entitlements to APIs

and Resources

Page 41: Impact2013 tsa 1416--api mgmt

41 41 © 2013 IBM Corporation 41

Manage the APIs with Business Insight through Analytics

Pinpoint key market fluctuations and find correlations related to your business •  Business Analytics for both API provider and

application developer:

•  Top traffic producing API ,

•  Top APP producing traffic

•  GeoLocation of the traffic

•  Structured Filtered Search across analytics for example

•  country:USA, color:red

•  Saved Searches and Filters for easy and consistent retrieval

•  Billing for API consumption by developers •  Export as CVS files for audit trails

Page 42: Impact2013 tsa 1416--api mgmt

42 42 © 2013 IBM Corporation

User Roles Defined AGAIN

Steve Steve is the API Product Manager

Jane Jane is the technical user who creates and manages the APIs from and IT Operations perspective

Will Will has the operations roles and is responsible for administration the systems environments

Joe Joe is the app developer who maybe outside the enterprise or inside the enterprise. He is the consumer of the APIs

Page 43: Impact2013 tsa 1416--api mgmt

43 43 © 2013 IBM Corporation

An Environment Console for Easy Management

•  Easily configure and scale your API Management environment with the new Environment Console

•  Create and manage the environment’s tenants

Page 44: Impact2013 tsa 1416--api mgmt

44 44 © 2013 IBM Corporation

Key capabilities in IBM API Management solution

Configuration, no coding"

•  Create and deploy a new API in just minutes •  Create a developer portal in minutes, and socialize your APIs to over 1 million developers •  ROI in a matter of days instead of months and years

Out of the box business analytics and operation insight "

•  Ability to pinpoint key market fluctuations and find correlations related to your business •  Drill down debug inspections of request and response messages reduce the time to

problem determine of orchestrated APIs in production and development time.

Support for continuous iterative development " •  Provide updates to the APIs with minimal to no interruption to your

consumers. •  Test out minor fixes and push to production in matter of minutes •  Revert to a previous snap shot to restore last know good

configuration at the touch of a button API Developer

Industry best security and integration in one solution"

•  Based on IBM market leading DataPower gateway •  Available as a service, providing risk free, full featured, no hassle 90 day trial •  Sign in and begin deploying APIs in less than 5 minute

Page 45: Impact2013 tsa 1416--api mgmt

45 45 © 2013 IBM Corporation 45

•  Analytic Business Insight Across All Channels

45

IBM API Management Provides Agility to Your Enterprise Opening New Channels

Leverages API to build company and customer Mobile Application

Leverages API across all websites and application

Leverages API to Build New Business and Partnerships

Company Web Sites and Applications

•  Lower Development Cost through simple assemble

•  Saves time with reuse of API

•  Control API Usage

•  Consistency of experience for customer and employees

IBM API Management

45  

secure

Page 46: Impact2013 tsa 1416--api mgmt

46 46 © 2013 IBM Corporation

IBM API Management

DataPower    XG45(With  DIM)  or  XI50/B,XI52  and  the  AO  OpMon  

REQUIRED  components  

•   Physical  or  VE  

• Purchase  new  or  re-­‐use  exis4ng  appliances ���

Secure, Control, Optimize

Cast  Iron  Standard  EdiMon  

•   OPTIONAL  component  

• Physical  or  HVE  

• Purchase  new  or  re-­‐use  exis4ng  appliances ���

Create (Assemble)

IBM  API  Management  

•   2  Hypervisor  Installs  

Create, Manage, Socialize

Leveraging your existing IBM DataPower and Cast Iron Investments

Page 47: Impact2013 tsa 1416--api mgmt

47 47 © 2013 IBM Corporation

IBM API Management

Secure, Control, & Optimized

Create (Assemble)

Create, Manage, Socialize

1 Solution, 1 Pane of Glass

Leveraging your existing IBM DataPower and Cast Iron Investments

Page 48: Impact2013 tsa 1416--api mgmt

48 48 © 2013 IBM Corporation

Expanding your Enterprise to new heights IBM Offering - API Centric Architecture Assessment Roadmap

What’s New? –  A methodical process of evaluating the existing

API Centric Architecture of an organization

–  An assessment approach to determine the alignment of existing API strategy with the business strategy, objectives, and needs along with the technical architecture & capabilities

–  Deliverables 1.  An API Architecture Baseline Assessment 2.  An API Management and Governance Model 3.  API Capabilities (Current & Future) 4.  API Transition Plan 5.  Executive Briefing Package

IBM Confidential until April 24, 2012

Driving market demands and challenges in deploying a

strategy and roadmap for API Economy

Connectivity & Integration

Promotions

Payment

API Service Management

AP

I

AP

I

AP

I

Commerce Mobile Social

Loyalty

Monitoring Throttling

Governance API-Catalog

API

API

API

The API Economy

Serv

ices

Pat

tern

Value-added Solutions

Bank

Telco

Retail

Enterprise Capabilities

Enterprise Capabilities

Enterprise Capabilities

API

API

Enterprise Partners

API

API

The API Centric Assessment and Roadmap offering is a

prescriptive analysis for both Business and IT, which guides

and helps determine the deployment and management of

an API Centric Architecture to determine the API roadmap for enterprises, in support of their

business objectives.

Page 49: Impact2013 tsa 1416--api mgmt

49 49 © 2013 IBM Corporation

Extend Your Services Beyond Your Enterprise IBM Software Services for API Management

IBM Confidential until April 24, 2013

Connectivity & Integration

Get API Management

operational rapidly while ensuring best practices are applied

§  Get API management operational and make APIs available rapidly

§  Learn and apply best practice for API design and exposure

§  Ensure your APIs are well secured, managed, and analyzed

§  Educate your team on APIs and API management

New Software Services: Our practitioners will work collaboratively with you to

–  Install, configure, test, and validate IBM API Management environments and ensure production readiness.

–  Design, expose, manage, secure, and analyze your APIs

–  Assemble new APIs from existing resources

–  Construct your developer portal and socialize your APIs

–  Transfer API management expertise to your team

Page 50: Impact2013 tsa 1416--api mgmt

50 50 © 2013 IBM Corporation

Expanding to APIs – IBM Services has the Expertise to Ensure Your Success

50  

•  What should my API Strategy be? •  How are APIs being used in my industry? •  What is needed to expose and manage APIs? •  What security do I need? •  Who are my target developers? •  How do I delivery and measure business value?

•  How do I get IBM API Management setup quickly? •  Help me design my APIs? •  How do I expose my backends as APIs? •  Help me secure and scale my APIs? •  How do I deliver reports to my management? •  How do I integrate with existing infrastructure?

API Centric Architecture Assessment Roadmap

IBM Software Services for API Management

Page 51: Impact2013 tsa 1416--api mgmt

51 51 © 2013 IBM Corporation

Get Started In the Cloud Today

http://webapi.castiron.com

51  

90 Day Free No Hassle Trial

Page 52: Impact2013 tsa 1416--api mgmt

52 52 © 2013 IBM Corporation

Agenda

•  Why API Management Is Import

•  Setting the Stage for API Management

•  IBM API Management Solution Overview

•  Demonstration

Page 53: Impact2013 tsa 1416--api mgmt

53 53 © 2013 IBM Corporation

Business IT Developer

Create & Secure Socialize Sign-Up Access, Test

Analyze Manage & Analyze

IBM API Management Demonstration

Page 54: Impact2013 tsa 1416--api mgmt

54 54 © 2013 IBM Corporation

Key API Management Sessions at IMPACT •  1416 Introduction to IBM API Mgmt & What's New

‒  Mon 1:00 ; Lando 4301B ‒  Thu 1:00 ; Marcello 4401A

•  2678 Introduction to Web APIs ‒  Mon 2:30 ; Lando 4305 ‒  Tue 5:15 ; Lando 4305

•  2763 Extending Enterprise Integration with IBM API Mgmt ‒  Mon 4:00 ; Lando 4305

•  2372 Recommended Practices for Designing a Web API ‒  Tue 4:00 ; Lando 4305

•  1411 Defining Your Business Strategy for APIs ‒  Tue 2:30 ; Lando 4305

•  1576 SOA & APIs ‒  Tue 10:15 ; Palazzo P

•  2731 API Management Security ‒  Tue 10:15 ; Lando 4305

•  1500 Hands-On Lab: Building a Web API Management Solution with Cast Iron Web API

Ø Tue 8:30 -11:15 ; Murano 3303

Page 55: Impact2013 tsa 1416--api mgmt

© 2013 IBM Corporation

Page 56: Impact2013 tsa 1416--api mgmt

56 56 © 2013 IBM Corporation

Legal Disclaimer

•  © IBM Corporation 2013. All Rights Reserved. •  The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in

this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.

•  References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.

•  If the text contains performance statistics or references to benchmarks, insert the following language; otherwise delete: Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

•  If the text includes any customer examples, please confirm we have prior written approval from such customer and insert the following language; otherwise delete: All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer.

•  Please review text for proper trademark attribution of IBM products. At first use, each product name must be the full name and include appropriate trademark symbols (e.g., IBM Lotus® Sametime® Unyte™). Subsequent references can drop “IBM” but should include the proper branding (e.g., Lotus Sametime Gateway, or WebSphere Application Server). Please refer to http://www.ibm.com/legal/copytrade.shtml for guidance on which trademarks require the ® or ™ symbol. Do not use abbreviations for IBM product names in your presentation. All product names must be used as adjectives rather than nouns. Please list all of the trademarks that you use in your presentation as follows; delete any not included in your presentation. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both.

•  If you reference Adobe® in the text, please mark the first use and include the following; otherwise delete: Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.

•  If you reference Java™ in the text, please mark the first use and include the following; otherwise delete: Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

•  If you reference Microsoft® and/or Windows® in the text, please mark the first use and include the following, as applicable; otherwise delete: Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

•  If you reference Intel® and/or any of the following Intel products in the text, please mark the first use and include those that you use as follows; otherwise delete: Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

•  If you reference UNIX® in the text, please mark the first use and include the following; otherwise delete: UNIX is a registered trademark of The Open Group in the United States and other countries.

•  If you reference Linux® in your presentation, please mark the first use and include the following; otherwise delete: Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.

•  If the text/graphics include screenshots, no actual IBM employee names may be used (even your own), if your screenshots include fictitious company names (e.g., Renovations, Zeta Bank, Acme) please update and insert the following; otherwise delete: All references to [insert fictitious company name] refer to a fictitious company and are used for illustration purposes only.