http://3.86.49.49/ 2026-04-17T15:01:38+00:00 http://3.86.49.49/ http://3.86.49.49/lib/tpl/docnavwiki/images/favicon.ico text/html 2021-06-25T10:09:56+00:00 Anonymous (anonymous@undisclosed.example.com) http://3.86.49.49/doku.php?id=development:applications:ebonding:howto:commonissues&rev=1624612196&do=diff Common Issues Author : Brian Coffey Date : 2017-02-07 Below are a list of common issues the support team may face with eBonding. These includes the actual issue, the cause and the resolution No form field value in the Ticketer Ticket Cause: The form fields are populated using CustomerMessageMappings which link an XPath to and errigalKey (i.e the form field database name), therefore either the errigalKey or the XPath location within the XML is incorrect text/html 2021-06-25T10:09:56+00:00 Anonymous (anonymous@undisclosed.example.com) http://3.86.49.49/doku.php?id=development:applications:ebonding:howto:rabbitmqgui&rev=1624612196&do=diff RabbitMQ GUI Author : Brian Coffey Date : 2017-02-03 Overview The RabbitMQ GUI shown below can be accessed from port 15672 and is currently only active on ExteNet server - it is usually run on the loadbalancer Queues The queues currently present for eBonding are shown below. Currently 4 queues are implemented; eBonding inbound, eBonding outbound, ticketer inbound, soap outbound. These queues are explained in more detail at text/html 2021-06-25T10:09:56+00:00 Anonymous (anonymous@undisclosed.example.com) http://3.86.49.49/doku.php?id=development:applications:ebonding:howto:xpaths&rev=1624612196&do=diff XPaths Author : Brian Coffey Date : 2017-02-01 XPath Overview Xpaths are a powerful method of extracting information from an incoming XML message. NOTE that tML-Base and tML-TA are replaced in the code as Xpath does not work well with messages like