telpro integration
DESCRIPTION
Telpro Integration presentation at the CADTEL 2010 User ConferenceTRANSCRIPT
Telpro Integration
By:
Rex Sheridan
Slide 2User Conference
April 11 – 13, 2010
Agenda
• Overview• Integration Concepts• Demo• Future Directions
Slide 3User Conference
April 11 – 13, 2010
Overview
Slide 4User Conference
April 11 – 13, 2010
Scenarios
Slide 5User Conference
April 11 – 13, 2010
What makes these scenarios so complex?
Slide 6User Conference
April 11 – 13, 2010
Multiple Disparate Systems
Slide 7User Conference
April 11 – 13, 2010
Multiple Interaction Styles
Slide 8User Conference
April 11 – 13, 2010
Multiple Data Formats
Slide 9User Conference
April 11 – 13, 2010
Complex Routing Rules
Slide 10User Conference
April 11 – 13, 2010
Integration Designer
Slide 11User Conference
April 11 – 13, 2010
Integration Designer
• Web based designer that deploys configurations to target systems based on the diagram
• Change the design of your systems on demand
• Easy collaboration on designs
• Auto deployment to multiple configured systems
• Works with existing Telpro BPM deployments
Slide 12User Conference
April 11 – 13, 2010
Building BlocksThese are supported out of the box. You can also add your own.
Slide 13User Conference
April 11 – 13, 2010
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.
Slide 14User Conference
April 11 – 13, 2010
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.
Slide 15User Conference
April 11 – 13, 2010
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.
Slide 16User Conference
April 11 – 13, 2010
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.
Slide 17User Conference
April 11 – 13, 2010
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.
Slide 18User Conference
April 11 – 13, 2010
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.
Slide 19User Conference
April 11 – 13, 2010
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.
Slide 20User Conference
April 11 – 13, 2010
Demo
Slide 21User Conference
April 11 – 13, 2010
Future Directions
• Monitoring• Cloud based deployment
Slide 22User Conference
April 11 – 13, 2010
Extra Slides
• The following slides were not presented but may prove useful for anyone viewing them after the conference.
Slide 23User Conference
April 11 – 13, 2010
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.
Slide 24User Conference
April 11 – 13, 2010
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
Slide 25User Conference
April 11 – 13, 2010
Integration Concepts
Applications Magically Connected
Slide 26User Conference
April 11 – 13, 2010
Endpoints• Connect an application to messaging channel using a Message
Endpoint, a client of the messaging system that the application can use to send or receive messages.