Centro stella dei pagamenti elettronici
  • Centro Stella
    • Instructions for Agenzia delle Entrate Mandate
      • How to join
        • 01. Sign the Agreement
        • 02. Integrate PagoPA Environments
          • Open routes
          • Request the mutual authentication certificates
          • Obtain an API key
          • Wait for activation email
          • Check if you are enabled for PagoPA UAT environment
        • 03. Configure the Batch Service
          • Prepare the Java KeyStore
          • Install the software
            • How to install JAR version
              • Download JAR file
              • Prepare the working directories
              • Define environment variables
            • How to install Docker version
              • Download Docker image
              • Define environment variables
              • Choose working directory to mount
          • Run the software
            • Run from JAR
            • Run with Docker
        • 04. Test and monitor integration
          • Test UAT
          • Test PROD
        • 05. Go live!
      • Releases / Changelog
        • Note regarding the modifications from 2.2.0 to 2.2.3
        • Note regarding the modifications from 2.1.2 to 2.2.0
        • Note regarding the modifications of the yaml file from 2.0.0 to 2.1.0
        • Note regarding the modifications of the yaml file from 1.5.1 to 2.0.0
        • Note regarding the modifications of the yaml file from 1.4.1 to 1.5.0
        • Note regarding the modifications of the yaml file from 1.3.2 to 1.4.1
        • Note regarding the modifications of the yaml file from 1.2.5 to 1.3.2
      • Appendixes
        • Appendix 1 - Environments
        • Appendix 2 - Input file specifications
        • Appendix 3 - AdE output file specifications
          • Appendix 3 - AdE output file specifications v1.2.5
        • Appendix 4 - AdE errors file specifications
        • Appendix 5 - Logback configuration
        • Appendix 6 - Configuration properties
        • Appendix 7 - Console log overview
        • Appendix 8 - Database connection for Spring Batch
        • Appendix 9 - FAQ & Troubleshooting
        • Appendix 10 - Python and Poetry installation
        • Appendix 11 - List of output and log files
      • Api Integration
  • Glossary
  • RTD documentation
    • Input file specifications
Powered by GitBook
On this page
  • Input files
  • AdE Output files
  • Log files
  • Pending files
  • File Reports
  1. Centro Stella
  2. Instructions for Agenzia delle Entrate Mandate
  3. Appendixes

Appendix 11 - List of output and log files

Input files

Once the input files are processed they are moved to a subdirectory named success (ACQ_BATCH_SUCCESS_PATH) or error (ACQ_BATCH_ERROR_PATH) by default, depending on the processing result.

There are 2 scenarios where a file remains inside the input folder

  • the naming convention is not complaint: the files are ignored and the batch service does not process them

  • the sender code check (between the sender code in file name and the sender code in the file records) fails: this may happen if the sender code is not set correctly or if every rows inside the file is discarded during the process. In this scenario the file will remain in the input folder and has to be removed or fixed manually.

AdE Output files

AdE output files are sent to Centro Stella APIs, a copy of the file may be saved locally according to the value of the variable ACQ_BATCH_DELETE_OUTPUT_FILE that defines the policy applied to the output files:

  • with the value ALWAYS the files will be deleted at the end of the batch execution

  • with the value ERROR the files will be deleted only if the batch ended with an error status

  • with the value KEEP the files will be kept inside the ACQ_BATCH_OUTPUT_PATH folder

Log files

The log files generated by the batch service, inside the folder ACQ_BATCH_TRX_LOGS_PATH, are:

Naming
Description

[timestamp]_Ade_FilteredRecords_[input_filename]

records discarded for parsing* errors in ade flow

[timestamp]_Rtd_ErrorRecords_[input_filename]

records discarded for validation* errors in RTD and ADE flows

application.log

application logs

* Please note the difference between the two steps: the parsing occur when the file is loaded and the rows are read, the validation step looks inside the fields and evaluates the content

By default the batch service deletes the empty log files at the end of the batch.

Pending files

When a file upload fails the batch service moves the file into the pending directory. By default the directory is located in output/pending but the position is customizable with the env var ACQ_BATCH_PENDING_PATH.

The files will be send with an automatic retry in the next runs of the batch service and will be deleted once the upload is completed. It is recommended to not remove these files or the folder manually.

File Reports

The report contains the list of the files recently uploaded (last 15 days) with some related information in json format.

The fields in the report are:

Field
Format
Description

fileName

Alphanumeric

The output AdE file name sent (with pgp extension)

status

Alphanumeric

Status of the file

size

Numeric

Dimension of the pgp file in byte

transmissionDate

ISO Date (e.g. 2022-12-02T15:35:55.586)

Transmission date of the pgp file

dataSummary

Object

Summary about the file content

The possible status values are:

Value
Description

RECEIVED_BY_PAGOPA

The file has been sent and received by PagoPA

VALIDATED_BY_PAGOPA

The file is formally correct and validated

SENT_TO_AGENZIA_DELLE_ENTRATE

The file has been sent to AdE

The field dataSummary is composed by:

Field
Format
Description

minAccountingDate

ISO Date (e.g. 2022-12-02)

Value of the oldest operation_date

maxAccountingDate

ISO Date (e.g. 2022-12-02)

Value of the latest operation_date

numberOfMerchants

Numeric

Count distinct of the field merchantId

countNegativeTransactions

Numeric

Sum of all transaction_number of negative transactions (operation type 01)

countPositiveTransactions

Numeric

Sum of all transaction_number of positive transactions (operation type 00)

sumAmountNegativeTransactions

Numeric

Sum of amount of the negative transactions in cents

sumAmountPositiveTransactions

Numeric

Sum of amount of the positive transactions in cents

sha256OriginFile

Alphanumeric

sha256 of the input file with transactions with the format "#sha256sum:xxxxxx"

An example of a report containing one file:

{
    "filesRecentlyUploaded": [
        {
            "name": "ADE.12345.TRNLOG.20240510.150000.001.01.csv.pgp",
            "size": 104000,
            "status": "SENT_TO_AGENZIA_DELLE_ENTRATE",
            "transmissionDate": "2024-05-03T13:31:17.587",
            "dataSummary": {
                "minAccountingDate": "2024-04-30", 
                "maxAccountingDate": "2024-05-03",
                "numberOfMerchants": 8,
                "countNegativeTransactions": 7,
                "countPositiveTransactions": 27,
                "sumAmountNegativeTransactions": 1825110,
                "sumAmountPositiveTransactions": 4642246,
                "sha256OriginFile": "#sha256sum:xxxxxx"
            }
        }
    ]
}

PreviousAppendix 10 - Python and Poetry installationNextApi Integration

Last updated 1 year ago