IBM WebSphere Cast Iron Cloud Integration

IBM WebSphere Cast Iron Cloud Integration

Andrew Daniel

Katherine Sanders

Agenda

Cast Iron Overview

What's New – Cast Iron Express with Demo

What's New – Additional Support & Improvements Hybrid Cloud Integration

Connector Development Kit (CDK) with Demo Best Practices

Cast Iron Overview

Integrate Cloud and On-Premise Application in Days

The fastest way to integrate Cloud and On-Premise applications Two main usage scenarios:

- Cloud and on-premise application integrations

- Rapid on-premise packaged application integration Why have Cloud customers adopted Cast Iron?

- Eliminate “swivel chair” approach & maximise Cloud user productivity

- 25% to 80% savings compared to custom code and other mid-market tools

Configuration, not coding approach; Reusable TIP templates

Cloud Applicat ions

Cloud Applications

What's New - Cast Iron Express

Entry-Level Self-Service offering – Integrate in hours Basic Salesforce.com integration use-cases:

- SalesForce and Databases (DB2, MySQL, MS SQL, Oracle) - SalesForce and Flat-files / FTP

Connectivity, Data Mapping

What's New - Additional Support & Improvements

Physical Appliance is on the new 9005 datapower 1U platform Connector Development Kit (CDK)

Service Management Extensions for Hybrid Cloud Integration

Managing hybrid environments requires more than application integration:

● How do I provision cloud assets?

● Can I sync my user registry between cloud and on-premise?

● How do I get one view of my IT landscape irrespective of cloud or on-premise?

Extension to existing Tivoli products, installable as plugin in Cast Iron

https://www-304.ibm.com/software/brandcatalog/ismlibrary/details?catalog.label=1TW10TS0D

Applications

Infrastructure

Hybrid Cloud Solution

On-premise to off-premise Application Integration - On-premise Backend to SaaS

Sync customer records

Directory Integration & Identity Federation: Synchronize on premise LDAP and

LotusLive Domino directory Sync on-premise

identity model and directory

Hybrid Monitoring

Tivoli Monitoring Server

LDAP Directory

Management and Provisioning to

Public Cloud

Acquiring Resources from IBM Cloud and/or Amazon

Connect off-premise monitoring with on-premise monitoring

system

Backend

Systems Tivoli Service Automation

Manager

Connector Development Kit (CDK)

● Create custom connectors that will be available in the standard set of activities in Studio ● Must use the existing activities in Studio to implement the connector

Wizard Driven Development

Zero Coding Complete Platform

● Allows iterative development ● Ability to unit test

● Simplified integration testing ● Local Repository

Connector Development Kit (CDK) Demo

● This simple example demonstrates the connector development lifecycle

● Further information is available in the Getting Started with IBM WebSphere Cast Iron Cloud

Integration Redbook:

● http://www.redbooks.ibm.com/Redbooks.nsf/RedpieceAbstracts/sg248004.html

● See chapter 8 for a more realistic example that creates a connector for Google Calendar.

● The CDK documentation is available online:

● http://publib.boulder.ibm.com/infocenter/wci/v6r1m0/topic/com.ibm.websphere.cast_iron.cdk.doc

Best Practices

● 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

Best Practices

● Split large orchestrations into reusable sub orchestrations

● Use configuration properties so the orchestration behaviour 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. lowerCamelCase for variables,

UpperCamelCase 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

Thank You

Any final questions?

[email protected]

[email protected]