Embed Size (px)
Citation preview
IBM Innovate 2012:Rapid Integration of Software-as-a-Service withOn-Premise Applications Using IBM WebSphereCast Iron
Prithvi SrinivasanSolution Architect - [email protected]
Arup DattaSr. Consultant - [email protected]
2
The Premier Event for Software and Systems Innovation
OVERVIEW
2
What is Cloud Computing?“Cloud computing is the delivery of computing as a service rather than a product, where by
shared resources, software, and information are provided to computers and other devices as a utility over a network”
IBM WebSphere Cast Iron Cloud Integration?
“WebSphere Cast Iron cloud integration projects enables companies to rapidly connect their hybrid world of public clouds, private clouds and on-premise applications”.
Goal is to make it easier for customers to move from legacy systems to hybrid cloud model.
3
The Premier Event for Software and Systems Innovation
Cloud Service Model
3
4
The Premier Event for Software and Systems Innovation
Cloud Deployment Model
4
5
The Premier Event for Software and Systems Innovation
Service To Deployment Model Mapping
5
6
The Premier Event for Software and Systems Innovation
Cloud
Challenges Control & Security of Business Data
Regulations & Compliance
Standards and Interoperability
Governance & Processes
Service Level Agreements & Enforcement
Benefits Business Agility
Reducing capital expenditures
Business Focus
6
7
The Premier Event for Software and Systems Innovation
8
The Premier Event for Software and Systems Innovation
Complete Flexibility
Cast Iron Cloud2™
Virtual Appliances
Physical Appliances
©2010 Cast Iron Systems, an IBM Company • Confidential
Total Connectivity Complete Reusability
TIP Exchange
TIP Development Kit
TIP Community
For All Types of Projects
UI Mashups
Process Integration
Data Migration
8
Cast Iron Solution Overview
9
The Premier Event for Software and Systems Innovation
Criteria Physical – XH40 Virtual – Hypervisor Cloud – Cast Iron Live
Integration On Premise Integration As A Service
Company Profile
Large companies Large companies and Global 5000 companies
Global 5000 and mid-market companies
Environment Already has IBM hardware; Requires new hardware for the solution
Already a virtualization shop; Ability to use existing hardware
Limited or no hardware infrastructure
Centricity Many on premise apps + few Cloud apps
Many on premise apps + few Cloud apps
Many cloud apps + few on premise apps
Scenario Cloud to On Premise; On premise to on premise
Cloud to On Premise; On premise to on premise
Cloud to Cloud;Cloud to On premise
Performance / Resource Constraints
Best for large volume / large message sizes100 jobs per orchestrationHybrid scenario – 300k records/hr*
Optimal for CPU bound, not I/O bound scenarios100 jobs per orchestrationHybrid scenario – 150k records/hr*
Greater variability due to external factorsGood for smaller data sets (must chunk large data sets)10 jobs per orchestrationShort-duration jobs (<30 min)Hybrid scenario – <100k records/hr*
Security & Compliance
Stringent – seek “inside out” integrationSuited for HIPAA and international needs
Suited for HIPPA and international needs
Happy with “outside in” integration”Not best fit for HIPAA and international needs
10
The Premier Event for Software and Systems Innovation
ARCHITECTURE COMPONENTS
10
11
The Premier Event for Software and Systems Innovation
WebSphere Cast Iron Capabilities
12
The Premier Event for Software and Systems Innovation
The Cast Iron Approach
No Coding Beyond Configuration Preconfigured Templates(TIPs)
13
The Premier Event for Software and Systems Innovation
Cast Iron Secure Connector
13
14
The Premier Event for Software and Systems Innovation
Connector Development Kit (CDK)
15
The Premier Event for Software and Systems Innovation
Demo
Salesforce Logging and DB2 Integration
15
DB2
SOAP/HTTP
Multi Tenant Cloud
Physical Integration Appliance
Virtual Integration Appliance
On-premise backend database
Retrieve Salesforce Account data
CAST IRON
16
The Premier Event for Software and Systems Innovation
Demo
Salesforce CRM Cloud Integration with Enterprise backend
16
17
The Premier Event for Software and Systems Innovation
Summary WebSphere Cast Iron
17
18
The Premier Event for Software and Systems Innovation
19
The Premier Event for Software and Systems Innovation
© Copyright IBM Corporation 2012. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials 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 these materials 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 these materials 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. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.
20
The Premier Event for Software and Systems Innovation
Additional Slides
21
The Premier Event for Software and Systems Innovation
Best PracticesError Handling
Use Try Activity to catch and handle exceptions
Check status in response messages for other errors
Use the Log Message, Send Email and Invoke Web Service activities to notify users of errors
Write a generic error handling orchestration and deploy as a Web service
Monitoring
Use a custom job key for every orchestration for better tracking
Manage the number of job logs retained
Set notifications to monitor system resources
Performance
Filter data at the source or as soon as possible in the orchestration
Use XPath predicates to filter data before looping through it
Reduce the number of activities, combine mappings into one activity if possible
Use lowest logging level in production
Manage number of concurrent jobs
22
The Premier Event for Software and Systems Innovation
Best Practices (Contd)
Maintainability
Split large orchestrations into reusable sub orchestrations
Use configuration properties so the orchestration behavior can be changed from the WMC without modifying the project e.g. endpoint username, password, server, URI
Use XSLT for complex mappings
Remove unused variables
Use a source code control system to give you a project change history and back up
Naming Conventions
Rename all orchestrations, endpoints, variables and activities to more descriptive names
Limit activity names to 30 characters (WMC won't display more than that)
Choose naming standards and be consistent e.g. Lowercase for variables, Uppercase for orchestrations and endpoints
Configuration properties are listed in alphabetical order in the WMC so put the endpoint at the start of the name to group them together e.g. FTPPassword, FTPPort, FTPServer, FTPUsername, SalesforcePassword, SalesforceURI, SalesforceUsername
Do not abbreviate names e.g. SalesforcePassword is easier to understand than SFPwd
