Traceability

When it comes to audit compliance, traceability is a basic requirement for an enterprise application and thus for a BTP programm. This requirement can for instance be accomplished by data historization or by writing a journal.

If data historization is a feature of the persistence layer and thus not the major focus of the BTP-architecture, it might be a necessary requirement to implement journalizing on a functional level within a BTP-environment.

The data obtained by such an implementation also offers valuable support to operations for runtime analysis and troubleshooting.

To allow traceability, the following runtime artefacts of a job need to be logged:

• Applied parameter values
• Functional messages
• Recapitualtions
• Contexts of jobs, slices and messages
• Status transitions of jobs and corresponding slices
• Progress informaiton
• Slice runs

Furthermore, a central repository for these runtime artefacts is desirable. This allows operations to efficiently access the information and also provide a simple access for auditing, if necessary.

The standardization within a framework is most certainly advantageous for the traceability, as it allows the batch developer to efficiently implement standardized features and thus guarantee easy maintenance, error analysis and debugging.