Reference Implementations (RIs) exist for the core components of the trouble ticket integration package:

The following requirements and conditions complete chapter 1.3.3 (Main requirements and conditions) and chapter 2.5 (RFP Guidelines) in terms of implementation specific requirements. These requirements are out of scope for this TT solution package but recommended for the behavior of a real end-to-end integration scenario. They are not only valid for the integration solution itself, they should be supported by all involved applications [server and client]

• Performance
  • Ticket transmission performance
    • Tickets must not be blocked by processing of tickets of lower priority
    • Ticket processing should be << 1 min
    • If an end-to-end ticket processing takes more than one minute it will be treated as an error.
  • The transmission of attribute changes (e.g. update of the description attribute) will be triggered by the status change only.
  • [for JMS profile implementations:] In case of several Client or Server added to the system, the server implementations should be able to do a topic filtering in order to reduce the system load.
• Security / Authentication
  • The solution has to secure that access to the system is only permitted with user and password credentials. A usage of LDAP authentication and encryption is desirable.
  • The solution has to verify that a user has permission to take specific action.