Enterprises both large and small need to process various types of files and connect them to disparate and distributed applications spread across enterprise data centers. As the underlying infrastructure gets more dispersed and complex, it becomes a challenge to gain end-to-end visibility of transactions that involve files, data transformations, connectivity logic, protocol conversions, and final data posted to different applications.

Table of contents

• Introduction
• Scenario and prerequisites
• File structure used in this scenario
• Creating unique TransactionID for end-to-end traceability
• Configuring Sterling C:D nodes and testing file arrival
• Using IBM Sterling Control Center V5.3 to monitor the C:D nodes
• Integrating IBM Sterling Control Centre with WebSphere MQ
• Conclusion
• Resources
• About the authors
• Comments

Download the document here.