User Tools
Writing /app/www/public/data/meta/development/applications/ticketer/ebonding/start.meta failed
development:applications:ticketer:ebonding:start
Differences
This shows you the differences between two versions of the page.
| development:applications:ticketer:ebonding:start [2017/02/03 16:55] – old revision restored (2017/02/03 08:53) adowling | development:applications:ticketer:ebonding:start [2021/06/25 10:09] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== The Ticketer and eBonding ====== | ||
| + | |||
| + | ===== Introduction: | ||
| + | The Ticketer interacts with the eBonding project by facilitating the need to keep both the Carrier and the Customer Ticketing systems in sync. The eBonding application components are as follows: The Ticketer, ebonding_component and soap_component. All three of these applications have been integrated to use RabbitMQ. For further information on RabbitMQ click here: [[development: | ||
| + | |||
| + | The focus of this entry will be to provide details on the level of interaction which the Ticketer application provides with this project. | ||
| + | |||
| + | The following areas will be covered: | ||
| + | |||
| + | - [[development: | ||
| + | - [[development: | ||
| + | - [[development: | ||
| + | - [[development: | ||
| + | - [[development: | ||
| + | - [[development: | ||
| + | - [[development: | ||
| + | |||
| + | For further questions on ticketer interaction with eBonding contact: | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
Page Tools
