AnsweredAssumed Answered

Catalog SLA impact on Application

Question asked by chris157.157 on May 31, 2018
Latest reply on Jun 5, 2018 by Louis_van_Amelsfort

Afternoon

We are currently using Catalog 14.1.02 (implementation of Cum#5 is imminent within the next 3 days) installed on 2 servers (load-balanced and Cluster aware) with the data stored on a separate SQL2014 DB.

The environment supports 8 catalogs with approximately 2000 service options (between 150 and 300 per catalog).  Each of these service options has between 1 and multiple tasks for fulfillment and each of these tasks has an associated SLA.

It has now become necessary to add an SLA to every service option to manage the end to end fulfillment of the service option.

Is there any manner of determining what the impact of this will be on the application. 

Does anyone know of any type of calculation that can be performed to determine the impact of additional SLA's on the application. 

Is there any documentation of what process runs that manages the SLA's, how it runs and how often it runs?.

 

Regards

Chris Saunders

Outcomes