310 likes | 591 Views
Introduction. Migrating a SeeBeyond Solution to BizTalk Server (A Black Box Approach). Overview of SeeBeyond. Integrated Composite Application Network (ICAN) Highly Customizable Enterprise Application Integration software with many separate modules eWay Adapter module - 80+ prebuilt adapters
E N D
Introduction Migrating a SeeBeyond Solution to BizTalk Server (A Black Box Approach)
Overview of SeeBeyond • Integrated Composite Application Network (ICAN) • Highly Customizable Enterprise Application Integration software with many separate modules • eWay Adapter module - 80+ prebuilt adapters • Purchased by Sun in late August 2005
Overview of BizTalk Server • Powerful, customizable end to end process management, application integration and trading partner management • Adapter framework and 3rd party adapter partners as well as OEM adapters • Fastest growing integration software, with 4500+ customers in over 4 years
Benefits of BizTalk Server • Solid Development Environment • Bigger Adapter Community • Reduced Custom Coding • Standard Languages (no MONK) • Lower Licensing costs and TCO • ***Easy to use***
Scenario – Background • Fabrikam – “Pretend Company” • Creator of widgets • Few trading partners with very different connections • HTTP/S • WS • WebSphere MQ • Etc. • Using SeeBeyond to handle EAI and TPI • 1 Administrator that knows end to end ICAN implementation
Scenario – Challenge • Upgrade in ICAN is resource intensive • Reduce amount of custom coding • Reduce TCO and maintenance cost • Add additional feature • Cancelled Order Tracking • Inventory Report
Scenario – Resolution • Executives want a better solution • Microsoft and Partners contacted • Shocker!!!! • ICAN administrator just resigned!!!
Beginning of the Solution Review Microsoft Solutions Framework
Scenario – Envisioning and Planning • Review Fabrikam Requirements BizTalk Server is the Solution!
Scenario – Solution Treat SeeBeyond as a Black Box! • Completion of Planning Envisioning Phase • Little documentation • ICAN admin gone!!! • Full documentation on what is coming in/out • Documentation of new requirements and features
MSF – Tips for Envisioning and Planning • Envisioning and Planning • Ensure to limit scope to transaction functionality only • Take careful note of SLA’s and performance requirements • Add extra time for new environment • Keep backup of blackbox around with plan to back out!
Business Logic and Workflow Migration • Easier to recreate workflow and mappings rather than trace SeeBeyond
Business Logic and Workflow Migration • New Functionality
Business Logic and Workflow Migration Tips • Review workflow documents and ensure that the documents are the latest • Use sniffers and/or error logs to capture message incoming/outgoing message formats • Prepare debugging/logging switches in code to capture messages
Internal Connectivity Migration • Migrating the Internal Connectivity
Internal Connectivity Migration Tips • Create test harnesses with good logging to validate connectivity • Verify code sets and character sets • ASCII vs. EBCDIC • Any other flags for TP when switching from SeeBeyond to Windows • Set up times with Trading Partner for testing with proper people • Obtain WORKING Trading Partner incoming and outgoing data samples
Trading Partner Channel Migration • Migrating the partner communication protocols
WebSphere MQ Introduction • Formerly MQ Series • Provides Enterprise Service Bus • High availability, high capacity queuing software • Guaranteed Message delivery • Common with SeeBeyond and EAI engagements
WebSphere MQ Scenarios • Questions that must be answered: • Trading Partner’s MQ Server Operating System • Guaranteed Message Delivery Required • Access via the network to Trading Partner’s system • MQ Server on Fabrikam site • Push vs. Pull of messages
Requirements for MQ Series Adapter • MQ Server required on Fabrikam • MQ Server must be Windows OS • Guaranteed Message Delivery • Capability for both Push and Pull messages
Host Integration Server • WebSphere MQ to MSMQ bridge • Guaranteed Message Delivery • Capability for both Push and Pull messages
WebSphere MQ Client • .NET API to MQ Client • NO Guaranteed Message Delivery • Capability for both Push and Pull messages
General Tips • Review MONK and java code for hints of Business logic • Allocate extra time for TP testing • Separate business logic and connectivity testing • Use separate hosts in BizTalk for each TP • Be wary of MQ settings that have little documentation • MQ support pack to run listener as service • MQC CSID for code set • MQ application ID make sure it is Windows
Testing and Deployment • Test all business rules • Use TP’s to test in “TEST” or “DEV” environments as much as possible • Allocate extra time for deployment • New systems and/or • New technology • Do not skimp over • HA tests • Failovers test • Backup/recovery • Operational procedures
Sample Project Timeline Release Day 9 Day 10 Day 14 Day 0 Day 3 Planning Development Test Project Working Start Launch
Thank You • Winson Woo, Cactus • winson@cactus.ca Best of Luck with your conversions! Phone: 1.888.CACTUS.0