PRODUCT

AAssure – Diagnostic Utility

Information in this document is subject to change

without notice.
No part of this document may be reproduced or
transmitted in any form or by any means, for any
purpose, without the express written permission
of TEMENOS HEADQUARTERS SA.
© 2022 Temenos Headquarters SA -
all rights reserved.
Table of Contents

Table of Contents ....................................................................................................................................................................................2

Document History...................................................................................................................................................................................3
1. Overview ..........................................................................................................................................................................................4
1.1 Inline Checks ............................................................................................................................................................................. 4
1.2 Offline Checks .......................................................................................................................................................................... 4
2. Parameter Configuration .............................................................................................................................................................4
2.1 Offline Configuration .............................................................................................................................................................. 4
2.1.1 Online service ...................................................................................................................................................................... 5
2.1.2 COB SERVICE ........................................................................................................................................................................ 6
2.1.3 OUTPUT EXTRACTION ....................................................................................................................................................... 6
2.2 Inline Configuration ................................................................................................................................................................ 6
3. Sample Output ...............................................................................................................................................................................7
4. Support .......................................................................................................................................................................................... 10

2
Document History

Author Version Date Comment

Munis 0.1 March 21 2018 Initial version

Hariharane 0.2 March 22 2018 Amended version

Comments:

{Add any comments here}

3
1. Overview
AAssure is a diagnostic tool that does a health check of all the arrangements and reports in case any of them have
issues. The aim is to catch issues as soon as they are found and reported for suitable remedy action. AAssure supports
both inline checks and offline checks. About 35 health checks are verified, and any lapses are recorded for action.
The purpose of this document is to cover the scope of the AAssure diagnostic utility, the options it supports, and the
procedure to enable them.

1.1 Inline Checks

The inline check happens at the end of every activity. Even when an activity results in a few secondary activities, the
check happens for each activity. It makes a comparison between the pre-image details and post-image details of a
few records to verify if the integrity of the arrangement is maintained within this activity. The advantage is that this
directly finds the activity that is causing an issue and assists in quicker root cause analysis.
Enabling the Inline checks is based on a parameter table AA.PARAMETER, where the below options are available
through the attribute ACTIVITY.INTEGRITY.CHECK.
▪ Log – When set to Log, during the execution of an activity, if any issues are identified, the system will still
complete the activity but record the details in a table AA.EXCEPTION.LOG.
▪ Error – When set to Error, during the execution of an activity, if any issues are identified, the system will raise
an error and abort the transaction. However, the logs with the required details will be collected for further
analysis.
The development environment contains the option Error so that the transaction is not processed. As we have no error
as a criterion for promotion, it will assist us not to leak out any errors that are caught by these health checks as well.

1.2 Offline Checks

The offline check was the one we developed first with the intention of covering the health check of arrangements.
This comes as a service running during close of business, but the frequency in which it has to be run could be
determined by the clients. Our recommendation is to run it at least once a week if not more frequently.
The following are the significant points to compare between inline & offline checks:
▪ Inline checks will be able to point out the activity that has caused the issue, whereas offline checks can only
mention that there is an issue with the arrangement and cannot detail beyond that.
▪ If the arrangement had an issue due to an activity(assuming with Log option), any further activities running
on top of the arrangement will be reported as problematic in inline checks only if the subsequent activities
are going to cause any incremental issues. However, when it comes to offline checks until the arrangement is
restored to normalcy, it will be picked up every time the service is run – no matter even if the following
activities do not cause any further issues.

2. Parameter Configuration
2.1 Offline Configuration
Kindly check the SPF and ensure the AA_Utility is installed in the environment before proceeding with the following
setup.
BATCH > AA.SYSTEM.CHECKS (COB Batch)
NOTE: Kindly open this record in input mode and set the batch job frequency as desired by you i.e Daily or Weekly
and authorise the same. Our recommendation is to run this job on a weekly basis. In case of multi-company
environment, the Id will be prefixed by Company Mnemonic – Eg: BNK/AA.SYSTEM.CHECKS

4
The utility can be run in two methods:
1. Online Service
2. COB service

2.1.1 Online service

To run the service as online, kindly set the TSA.SERVICE record AA.INTEGRITY.CHECK as START.

5
Now starting the TSM service would run the service automatically and the results of the utility would be stored in your
&SAVEDLISTS& folder as below.
AA.INTEGRITY_US0010001_20180105.csv - the output file id would be combination of the company code and the
date on which the service was run.
Please note that the folder &SAVEDLISTS& is the “current” directory defined in tafj.properties through the variable
temn.tafj.runtime.directory.current.

2.1.2 COB SERVICE

To make the utility run during cob process, kindly set the job frequency as per your requirement in the batch record
AA.SYSTEM.CHECKS. On the frequency date system would run the batch job during ONLINE stage, i.e., post to
completion of your Start of Day batch and during the online stage.
The output of the utility would then be stored in &SAVEDLISTS& folder under id with a similar format as the service.

2.1.3 OUTPUT EXTRACTION

Each of the &SAVEDLISTS& records is a simple delimited text file and can be opened in notepad or excel.

Online service
To run the service as inline, kindly set the TSA.SERVICE record AA.INTEGRITY.CHECK as START

Now starting the TSM service would run the service automatically, and the results from the utility would be stored in
your &SAVEDLISTS& folder.

2.2 Inline Configuration

This inline integrity utility will be enabled through a parameter table. Only if this is set up, the utility will report the
inconsistency. Kindly find the below steps to enable the utility through the parameter.

6
In table AA.PARAMETER the field ACTIVITY.INTEGRITY.CHECK should be set to enable the inline evaluation. The
system allows two options to be input
1. Error – It throws an error and stops the transaction
2. Log – It allows the transaction to commit but logs the exception details in AA.EXCEPTION.LOG

3. Sample Output
Offline:
Please find the &SAVEDLIST& folder path from .properties record.

Upon opening the generated report, the details can be viewed.

7
Inline:
Below are the two scenarios that were tested. One with the parameter set as error and the second with parameter set
as LOG.

When ERROR is set, system does not allow to commit the transaction by throwing an error, as shown below.

8
 1. LOG is set in ACTIVITY.INTEGRITY.CHECK

When LOG is set, system logs the exception details in the AA.EXCEPTION.LOG as shown below, while the transaction
gets committed.

9
4. Support
If you require more details/clarification about the Integrity Check utility, please feel free to contact the Product
AAssure team at Product_AAssuresupport@temenos.com.

10