http://3.86.49.49/ 2026-04-17T14:32:22+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:configuration&rev=1624612196&do=diff eBonding Configuration File The file is located in the usual grails config directory '/usr/local/grails' and is called EBondingConfig.groovy Spring Security grails.plugin.springsecurity.interceptUrlMap = [ [pattern: '/login/**', access: ['permitAll']], [pattern: '/logout/**', access: ['permitAll']], [pattern: '/**', access: ['ROLE_ADMIN']] ] grails.plugin.springsecurity.logout.postOnly = false 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:domains&rev=1624612196&do=diff eBonding Domains Author : Colm Carew Date : 2017-02-01 Customer The purpose of this domain is to store information about a customer. String name - This is the Customer Name String ticketerUser - This is the Customers Name within the Ticketer String ticketerWorkflow - This is the Workflow we want all the String ticketerFormTableName - This is the form database name we want associated with the customer i.e. f_ebonding String ticketerFormPublishedName - This is the published form n… 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&rev=1624612196&do=diff eBonding How Tos * X-Paths * RabbitMQ GUI * Common Issues 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:messages&rev=1624612196&do=diff eBonding Incoming Soap Messages Create - RequestTroubleReportCreationRequest This is the message that creates the ebonding ticket. It has the following possible Exception Responses : AccessDenied : Basically we were sent a service ID (circuit ID) in the message that is not in our eBonding database 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:purpose&rev=1624612196&do=diff eBonding Purpose Author : Colm Carew Date : 2017-02-01 The Need Our current system tracks network elements and our Ticketer is used to Ticket issues. Our customers use our tools to progress tickets through their necessary workflow to resolve the issue. 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:restart&rev=1624612196&do=diff How to Restart the Applications - Soap, eBonding and Ticketer Soap The tomcat directory is located : /var/tomcat/soap/ Soap runs on port 8085 and uses /usr/local/tomcat8 The start up scripts are in the bin folder cd /var/tomcat/soap/bin # Shut down the Application 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:works&rev=1624612196&do=diff eBonding - How it Works Author : Colm Carew Date : 2017-02-01 The eBonding Component Standalone InBound Message To focus on an InBound Message solely from the perspective of the eBonding component what we see is that our eBonding Queue is bound to the soap exchange via the routing key 'eBonding'. When we receive a message on the eBonding queue the eBonding component consumes it and begins to process the message. During the message processing (possibly more than once) it may contact the Ti…