Author/Assessor: Anna Dowling

The Ticketer Source Configuration creates the database connection for accessing the Ticketer application. The Ticketer Source Configuration is set on a per Company Configuration basis. To enable a particular Ticketer config, it must be assigned to the active Company Configuration. This can be found through the admin UI in Company Configurations.

Upon clicking on this Ticketer configuration entry we are presented with a number of values:

The first item to note is the Database Profile setting. This will point to the Ticketer database on a particular server depending on the customer that this is configured for. As we saw with the SNMP Configuration, the database profile settings contain login credentials, driver information and connection url endpoints.

This is the public url associated with the ticketer application. This usually points at the load balancer and once again is customer specific.

The list of queries which are assigned tie back to the View Preferences in the Noc Portal.

• For example the queries prefixed with PM relate to the Preventative Maintenance View Preferences.
• The queries prefixed with Change Management relate to the Change Management View Preferences.

As we saw in the SNMP Configuration, there are also settings for Query Length in Days and Query Limit.

1. In the Noc Portal find the active company configuration.
2. Locate the Ticketer configuration associated with this company config.
3. Name the database profile which this Ticketer config points to.
4. List the connection url that is associated with this database profile.
5. Outline how you would connect to this database to verify data returned in the Noc Portal.
6. Demonstrate an understanding of how the PM Quarterly Cluster Query is used to display results in the Noc Portal.
7. Locate the associated Ticketer public url.
8. Demonstrate an understanding of the return types from the Default Ticketer Query.