Telpro Integration
•Download as PPTX, PDF•
0 likes•158 views
The presentation discusses Telpro Integration, a web-based integration designer that allows users to visually design integration configurations between disparate systems. It supports building blocks for common integration patterns out of the box. The designer deploys configurations to target systems, enabling easy collaboration. An example was shown where an input file activates a process, with outputs sent to billing via HTTP and to a warehouse for storage. Future directions include monitoring and cloud-based deployment.
Recommended
More Related Content
What's hot
Similar to Telpro Integration
Similar to Telpro Integration (20)
Recently uploaded
Recently uploaded (20)
Telpro Integration
- 1. Telpro Integration By: Rex Sheridan
- 2. Agenda Overview Integration Concepts Demo Future Directions
- 3. Overview
- 4. Scenarios
- 5. What makes these scenarios so complex?
- 12. Change the design of your systems on demand
- 13. Easy collaboration on designs
- 14. Auto deployment to multiple configured systems
- 16. Integration Example Activation based on an input file with one or more Records. The output is sent to billing via HTTP and to a warehouse for storage.
- 17. Integration Example Activation based on an input file with one or more Records. The output is sent to billing via HTTP and to a warehouse for storage.
- 18. Integration Example Activation based on an input file with one or more Records. The output is sent to billing via HTTP and to a warehouse for storage.
- 19. Integration Example Activation based on an input file with one or more Records. The output is sent to billing via HTTP and to a warehouse for storage.
- 20. Integration Example Activation based on an input file with one or more Records. The output is sent to billing via HTTP and to a warehouse for storage.
- 21. Integration Example Activation based on an input file with one or more Records. The output is sent to billing via HTTP and to a warehouse for storage.
- 22. Integration Example Activation based on an input file with one or more Records. The output is sent to billing via HTTP and to a warehouse for storage.
- 23. Demo
- 24. Future Directions Monitoring Cloud based deployment
- 25. Extra Slides The following slides were not presented but may prove useful for anyone viewing them after the conference.
- 26. Messaging Concepts Channel: Virtual pipes that connects a sender to a receiver of a message Message: Message is an atomic packet of data the can be transmitted on a channel. Routing: The route a message should take to its final recipient might be complex. The sender simply sends the message to a router. The router is responsible to determine the route a message takes and through which channels.
- 27. Messaging Concepts Transformation: Messages between sender and receiver may differ in format. A transformation action changes incoming messages to the recipient’s format. Endpoints: Application way to interact with a messaging system. Pipes and Filters: Actions may need to be taken onto a message after it is sent and before it is received by the final recipient
- 28. Integration Concepts Applications Magically Connected
Editor's Notes
- Communication service providers need to offer new services on new networks while maintaining legacy systemsFrequently new services are developed in parallel on legacy networks at significant additional expense which leads vertical “silos” supporting the different services.Having vertical nature of legacy delivery environments tends to isolate services to different domains where it it will become difficult to offer new services with old services.First Bullet:Maintaining legacy service environments and networks often hamper strategic efforts to innovate and deploy breakthrough functionality.Second bullet: Without proper integration, the OSS will end up with redundant investments to deploy next-generation services on both legacy and next-generation environments. The result is often closed, vertical “silos”, where specific services are tied to specified networks.Third bullet: Take the example where network has fiber and and copper. If each technology is in it is domain, it will be hard to implement VOICE on copper and VIDEO on fiber for the same customer. With a flexible platform, we can utilize new and old networks transparently.
- Four reasons: disparate systems, different interaction styles, multiple data formats, complex routing rules
- Most applications do not have any build-in capability to interface with a messaging system. Rather they must contain a layer of code that knows both how the application works and how the messaging system works.
- Most applications do not have any build-in capability to interface with a messaging system. Rather they must contain a layer of code that knows both how the application works and how the messaging system works.
- Most applications do not have any build-in capability to interface with a messaging system. Rather they must contain a layer of code that knows both how the application works and how the messaging system works.
- Most applications do not have any build-in capability to interface with a messaging system. Rather they must contain a layer of code that knows both how the application works and how the messaging system works.
- Most applications do not have any build-in capability to interface with a messaging system. Rather they must contain a layer of code that knows both how the application works and how the messaging system works.
- Most applications do not have any build-in capability to interface with a messaging system. Rather they must contain a layer of code that knows both how the application works and how the messaging system works.
- Most applications do not have any build-in capability to interface with a messaging system. Rather they must contain a layer of code that knows both how the application works and how the messaging system works.
- Channel:Virualpilethat
- Channel:Virualpilethat
- Most applications do not have any build-in capability to interface with a messaging system. Rather they must contain a layer of code that knows both how the application works and how the messaging system works.
- Most applications do not have any build-in capability to interface with a messaging system. Rather they must contain a layer of code that knows both how the application works and how the messaging system works.