What Enterprises Need: Systems that Require Low Day-to-Day Management
By Jean Ouellette | July 12, 2011
2 minute read
This is the ninth installment in our weekly technical blog series about Enterprise Content Transformation: What Enterprises Need. The series kicked off with an overview of the reasons your organization needs linear scalability, high availability, easy integration with existing systems, a highly configurable platform, built-in monitoring and alerting , system reporting , and central platform management .
Today’s IT departments have more systems to manage and less people to manage them, so you need systems that require as little day–to-day management as possible. We believe we’ve minimized this with the new Adlib Platform. We recommend that the following activities be performed on a daily basis on our enterprise content transformation platform:
- Confirm All System Components are Running– We believe this is important to do even if the Adlib Platform automatically executed component monitoring and failure alerting, since a component may be stopped manually by IT staff, but was not re-started due to distractions or other priorities. The Adlib Platform system status page allows you to review the status of every component in the system in a few seconds as the list can be easily filtered and sorted.
- Confirm the Job Processing Time – This activity is important to confirm that the system is achieving the job processing time Service Level Agreement (SLA) commitment. SLA is one of the most common ways to measure system performance. The SLA can be negatively affected if new lines of business are added to the system that has a high volume of jobs or long-running jobs. Adlib’s job processing time report provides the processing time for every job. Jobs that took longer than the SLA can be easily filtered in the list. The list can also be sorted by processing time to determine any deviation from the committed SLA.
- Confirm Job Success Rate – This activity is important to confirm that the system is processing jobs as expected. Adlib’s job success report provides the percentage of jobs that completed successfully. There are various reasons why a job may fail, such as password protected documents, corrupted files, etc. In addition, Enterprise Content Transformation often integrates with the applications used to create the document; if the application has failed or is otherwise unavailable, the corresponding jobs will fail as well. This information is logged in the system with the job. It is important to correct failed applications in order to achieve a high job success rate.
The combination of the Adlib Platform central system reporting, logging and system component monitoring and alerting significantly reduces the day–to-day management effort to a few minutes a day and enables you to keep the system operating as efficiently as possible.