Agresso framework

Job details

Parameters

Job Summary

Purpose

• The purpose of this job is to check whether there is an installation of the Agresso application in any of the databases managed by dbWatch Control Center.

Why This Job Is Important

• This job is critical in verifying the existence and installation status of the Agresso framework across various databases registered under dbWatch.
• Identifying the presence of Agresso is crucial for organizations that rely on its applications for business processes because it impacts visibility on application deployments and versions.

Manual Checking

• You can check the existence of Agresso manually by executing the following SQL commands in the corresponding database:

SELECT * FROM sys.objects WHERE name LIKE '%agltransact%' OR name LIKE '%asyssetup%';

Technical Details

Dependencies

• The task depends on two main objects: ‘agresso_framework_proc’ (a stored procedure to perform the check) and ‘agresso_framework_info’ (a table to store information).

Job Execution

• The SQL procedure ‘agresso_framework_proc’ systematically checks each database in the SQL Server except the system databases. It determines if the databases are online and if they are a primary replica in an availability group.
• The procedure searches for specific objects indicating Agresso installation (‘agltransact’ and ‘asyssetup’) and updates ‘agresso_framework_info’ with details about the schema and version whenever found.
• The process involves frequent updates on the status of the checks into the dbWatch task values for real-time monitoring.

Error Handling

• The task has built-in mechanisms to handle errors during execution. It logs exceptions and continues the check across databases, ensuring comprehensive coverage without halting due to singular issues.

Reporting

Reporting Structure

• A DBWatch Report Template titled “Agresso statistics” is geared to display details from the ‘agresso_framework_info’ table.
• The report includes a specific chapter “Agresso reports” which summarizes Agresso installations with detailed attributes of each database including DB name, schema ID and names, Agresso version, and the history date when checks were done.

Data Points in Report

• This report covers a gallery of up to 20 distinct values at a time with data points plotted against database names, schema ID, schema name, Agresso version, and last checked dates.

Scheduling and Version

• The job is set to run at 6:04 every day, as per its default schedule, ensuring regular checks.
• The versions described are ‘1.21′ for the current procedure and ‘2′ for the reporting template, with consistent updates from a previous version ‘1.2′.

This job setup ensures that administrators have up-to-date information on Agresso installations across their managed databases, allowing for efficient management of these business-critical applications.