====== 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:applications:rabbitmq|RabbitMQ]]

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:applications:ticketer:ebonding:indentifyTicket:|How to identify an eBonding Ticket]]
  -  [[development:applications:ticketer:ebonding:ebondingForm:|The eBonding form]]
  -  [[development:applications:ticketer:ebonding:create:|Ticket Creation via eBonding process]]
  -  [[development:applications:ticketer:ebonding:search:|Ticket Searching via eBonding process]]
  -  [[development:applications:ticketer:ebonding:update:|Ticket Updates via eBonding process]]
  -  [[development:applications:ticketer:ebonding:config:|Configuration and Bootstrap]]
  -  [[development:applications:ticketer:ebonding:avc:|AVC(Attribute Value Change) Notifications]]

For further questions on ticketer interaction with eBonding contact:  --- //[[anna.dowling@errigal.com|Anna Dowling]]//