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
  • 1. Mutual Authentication certificate validity check PROD
  • 2. API Key validity check PROD
  • 3. Stop the Batch Service execution
  • 4. Configure PROD environment variables
  • 5. Restart the Batch Service execution
  • 6. Upload transactions file in input directory
  1. Centro Stella
  2. Instructions for Agenzia delle Entrate Mandate
  3. How to join
  4. 04. Test and monitor integration

Test PROD

PreviousTest UATNext05. Go live!

Last updated 2 years ago

Before testing in PROD, the UAT checklist must be approved by PagoPA.

If you haven't get them yet, proceed with the and .

1. Mutual Authentication certificate validity check PROD

The first step checks the validity of the client certificate, with a call to a dedicated endpoint using your certificate and your private key.

From the cstar-cli project root run the script with the following command:

sh ./integration_check/scripts/006-mAuth-check-PROD/script.sh /PATH/TO/COMPANY_NAME_PROD.certificate.pem /PATH/TO/COMPANY_NAME_PROD.key

Note that you have to specify the path to your certificate and to the private key as arguments.

The script will print on screen the result, the correct value is 200 .

Example of expected result:

--<TIMESTAMP>--  https://api.cstar.pagopa.it/rtd/mauth/check
Resolving api.uat.cstar.pagopa.it (api.cstar.pagopa.it)... 20.101.29.138
Connecting to api.uat.cstar.pagopa.it (api.cstar.pagopa.it)|20.101.29.138|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 24 [application/json]
Saving to: ‘STDOUT’
-
  "result": "PASS"
-

2. API Key validity check PROD

The second step checks the validity of the API Key, with a cll to a dedicated endpoint using your certificate, your private key and the PROD API Key.

From the cstar-cli project root run the script with the following command:

sh ./integration_check/scripts/007-API-key-check-PROD/script.sh /PATH/TO/COMPANY_NAME_PROD.certificate.pem /PATH/TO/COMPANY_NAME_PROD.key PROD_API_KEY

Note that you have to specify the path to your certificate, the path to the private key and the API key as arguments.

The script will print on screen the result, the correct value is 200 .

Example of expected result:

--<TIMESTAMP>--  https://api.cstar.pagopa.it/rtd/api-key/check
Resolving api.uat.cstar.pagopa.it (api.cstar.pagopa.it)... 20.101.29.138
Connecting to api.uat.cstar.pagopa.it (api.cstar.pagopa.it)|20.101.29.138|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 24 [application/json]
Saving to: ‘STDOUT’
-
  "result": "PASS"
-

3. Stop the Batch Service execution

4. Configure PROD environment variables

5. Restart the Batch Service execution

6. Upload transactions file in input directory

It is preferable to use real data in this step to test Batch Service instance performance.

Configure the environment variables using PROD check preset, according to your running artefact ( or ). This configuration allows to run the Batch Service without sending any data to PagoPA, this way you can test the performance of the software in your environment with production data.

certificate
API key
JAR
Dockerimage