Your SlideShare is downloading. ×
0
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Rapid Integration of Software-as-a-Service with On-Premise Applications Using IBM WebSphere Cast Iron

643

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
643
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
26
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. IBM Innovate 2012:Rapid Integration of Software-as-a-Service withOn-Premise Applications Using IBM WebSphereCast IronPrithvi SrinivasanSolution Architect - Prolificspsrinivasan@prolifics.comArup DattaSr. Consultant - Prolificsadatta@prolifics.com
  • 2. The Premier Event for Software and Systems Innovation OVERVIEW 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.2 2
  • 3. The Premier Event for Software and Systems Innovation Cloud Service Model3 3
  • 4. The Premier Event for Software and Systems Innovation Cloud Deployment Model Public Cloud Community Cloud Private Cloud Hybrid Cloud • Cloud environment • Cloud environment • Cloud environment • Cloud environment is a that provides shared by several operated solely for a composition of two or resources to organizations and single more clouds (private, individuals and supports a specific organization, whether community, or public) organizations over the community that has managed internally or that remain unique public internet. shared concerns. by a third-party and entities but are bound hosted internally or together by externally standardized or proprietary technology that enables data and application portability4 4
  • 5. The Premier Event for Software and Systems Innovation Service To Deployment Model Mapping5 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 Focus6 6
  • 7. The Premier Event for Software and Systems Innovation7
  • 8. The Premier Event for Software and Systems Innovation Cast Iron Solution Overview Complete Flexibility Total Connectivity Complete Reusability For All Types of Projects UI Mashups TIP Exchange Cast Iron Cloud2™ TIP Development Kit Process Integration Physical Appliances Virtual Appliances TIP Community Data Migration8 © 8
  • 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 Large companies Large companies and Global Global 5000 and mid-market Profile 5000 companies companies Environment Already has IBM hardware; Already a virtualization shop; Limited or no hardware Requires new hardware for Ability to use existing hardware infrastructure the solution Centricity Many on premise apps + Many on premise apps + Many cloud apps + few Cloud apps few Cloud apps few on premise apps Scenario Cloud to On Premise; Cloud to On Premise; Cloud to Cloud; On premise to on premise On premise to on premise Cloud to On premise Performance Best for large volume / Optimal for CPU bound, Greater variability due to / Resource large message sizes not I/O bound scenarios external factors Constraints 100 jobs per orchestration 100 jobs per orchestration Good for smaller data sets Hybrid scenario – Hybrid scenario – (must chunk large data sets) 300k records/hr* 150k records/hr* 10 jobs per orchestration Short-duration jobs (<30 min) Hybrid scenario – <100k records/hr* Security & Stringent – seek “inside out” Suited for HIPPA and Happy with “outside in” Compliance integration international needs integration” Suited for HIPAA and Not best fit for HIPAA and international needs international needs9
  • 10. The Premier Event for Software and Systems Innovation ARCHITECTURE COMPONENTS10 10
  • 11. The Premier Event for Software and Systems Innovation WebSphere Cast Iron Capabilities11
  • 12. The Premier Event for Software and Systems Innovation The Cast Iron Approach No Coding Beyond Configuration Preconfigured Templates (TIPs)12
  • 13. The Premier Event for Software and Systems Innovation Cast Iron Secure Connector13 13
  • 14. The Premier Event for Software and Systems Innovation Connector Development Kit (CDK)14
  • 15. The Premier Event for Software and Systems Innovation Demo Salesforce Logging and DB2 Integration SOAP/HTTP Retrieve Salesforce Account data CAST IRON Physical Virtual Multi Tenant Integration Integration Cloud Appliance Appliance On-premise backend database DB215 15
  • 16. The Premier Event for Software and Systems Innovation Demo Salesforce CRM Cloud Integration with Enterprise backend16 16
  • 17. The Premier Event for Software and Systems Innovation Summary WebSphere Cast Iron17 17
  • 18. The Premier Event for Software and Systems Innovation18
  • 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 havethe 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 IBMsoftware. 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 capabilitiesreferenced 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 featureavailability 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 MachinesCorporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others. 19
  • 20. The Premier Event for Software and Systems Innovation Additional Slides20
  • 21. The Premier Event for Software and Systems Innovation Best Practices Error 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 jobs21
  • 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 wont 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 SFPwd22

×