The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "GGUS:Ticketing System Recommendation FAQ"
Jump to navigation
Jump to search
| (8 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
__NOEDITSECTION__ | __NOEDITSECTION__ | ||
{{DEFAULTSORT:{{PAGENAME}}}} | {{DEFAULTSORT:{{PAGENAME}}}} | ||
Site decommissioned | |||
<!-- | |||
[[Category:FAQ Interfaces (GGUS)]] | [[Category:FAQ Interfaces (GGUS)]] | ||
<hr />'''GGUS ticketing system recommendations''' | <hr />'''GGUS ticketing system recommendations''' | ||
| Line 8: | Line 10: | ||
==Purpose== | ==Purpose== | ||
This document provides a technical description on how to interface any other ticketing system with GGUS. It describes the interface of choice and gives some examples for tools that can be used to reach this goal. | This document provides a technical description on how to interface any other ticketing system with GGUS. It describes the interface of choice and gives some examples for tools that can be used to reach this goal. | ||
It does not give a description of the things to be done on management level before implementing an interface to GGUS. As the things to be done on management level are currently not documented please submit a | It does not give a description of the things to be done on management level before implementing an interface to GGUS. As the things to be done on management level are currently not documented please submit a [https://ggus.eu/pages/ticket.php GGUS ticket] or add your request for interfacing GGUS system to the [https://rt.egi.eu/rt/Dashboards/2636/GGUS-Requirements GGUS shopping list]. The GGUS shopping list is a RT queue for collecting and discussing change requests for GGUS system. | ||
==Current situation== | ==Current situation== | ||
In the past many interfaces of GGUS to other systems have been implemented. Each of them was unique in its kind. They can be classified into three different groups: | In the past many interfaces of GGUS to other systems have been implemented. Each of them was unique in its kind. They can be classified into three different groups: | ||
* Interfaces based on email for communication from GGUS to the remote system and on web services for communications from the remote system to GGUS | * Interfaces based on email for communication from GGUS to the remote system and on web services for communications from the remote system to GGUS | ||
* Interfaces based on web services for both communication directions, from GGUS to the remote system and from the remote system to GGUS. | * Interfaces based on web services for both communication directions, from GGUS to the remote system and from the remote system to GGUS. | ||
| Line 21: | Line 22: | ||
===Interfaces based on SOAP web services=== | ===Interfaces based on SOAP web services=== | ||
Web service interfaces are very reliable. The ticketing systems are synchronized permanently. Failing web services throw an error message at once. So the user gets notified about it. | Web service interfaces are very reliable. The ticketing systems are synchronized permanently. Failing web services throw an error message at once. So the user gets notified about it. | ||
Most of the ticketing tools mentioned in chapter | Most of the ticketing tools mentioned in the chapter [[#Tools]] don't provide web services out of the box. Some implementation work is needed for a web service interface. | ||
== | ==System recommendations== | ||
Regarding the advantages and disadvantages described in | Regarding the advantages and disadvantages described in chapter [[#Current situation]] an email interface can be set up rather quick but is not that reliable. SOAP web services are very reliable but need some implementation work. | ||
However the goal of GGUS is to avoid setting up new email interfaces and to replace existing ones. If setting up a new ticketing system GGUS recommends using a ticketing tool which allows the implementation of SOAP web services. RT is an example for such a tool. | However the goal of GGUS is to avoid setting up new email interfaces and to replace existing ones. If setting up a new ticketing system GGUS recommends using a ticketing tool which allows the implementation of SOAP web services. RT is an example for such a tool. | ||
==Tools== | ==Tools== | ||
The GGUS system is based on BMC Remedy Action Request System (ARS). Remedy ARS is able to provide web services as well as to consume web services. So data transfer can be done by web services in both directions. | The GGUS system is based on BMC Remedy Action Request System (ARS). Remedy ARS is able to provide SOAP web services as well as to consume SOAP web services. So data transfer can be done by SOAP web services in both directions. | ||
For | For interfacing a ticketing system with GGUS a couple of tools are available. Tools which are already interfaced in production are: | ||
* Xoops/Xhelp, | * Xoops/Xhelp, | ||
* OneOrZero , | * OneOrZero , | ||
| Line 41: | Line 42: | ||
===SOAP web services provided by OneOrZero=== | ===SOAP web services provided by OneOrZero=== | ||
Information on OneOrZero is available at http://www.oneorzero.com/. | Information on OneOrZero is available at http://www.oneorzero.com/. | ||
==Web services provided by GGUS system== | ==Web services provided by GGUS system== | ||
The web services provided by GGUS system offer four different operations for | The web services provided by GGUS system offer four different operations for | ||
* creating a new ticket | * creating a new ticket, | ||
* modifying an existing ticket | * modifying an existing ticket, | ||
* getting data of one existing ticket | * getting data of one existing ticket and | ||
* getting a list of existing tickets | * getting a list of existing tickets. | ||
These | These web services are described in the relevant [[GGUS:SOAP_Interface_FAQ | FAQ]] | ||
===Examples and documentation=== | ===Examples and documentation=== | ||
Examples of interfaces in production are available for tools based on PHP and Perl. They can be found | Examples of interfaces in production are available for tools based on PHP and Perl. They can be found in the interfaces [https://wiki.egi.eu/wiki/Category:FAQ_Interfaces_%28GGUS%29 FAQs]. There is also information about available tools used for help desk systems to be interfaces with GGUS system on this page. | ||
===Developing and testing=== | ===Developing and testing=== | ||
For developing and testing an interface to GGUS | For developing and testing an interface to GGUS a test and training system is available. This system is a copy of the production system. See the [http://train-ars.ggus.eu/arsys/WSDL/public/train-ars/GGUS WSDL-file] for details. | ||
For further information please contact the GGUS team. | For further information please contact the GGUS team. | ||
== What if I have questions which are not dealt with by this FAQ? == | == What if I have questions which are not dealt with by this FAQ? == | ||
Open a {{GGUS ticket}} indicating that it should be directed at the GGUS team. | Open a {{GGUS ticket}} indicating that it should be directed at the GGUS team. | ||
{{GGUS search}} | {{GGUS search}} | ||
--> | |||
