DE4A Checklist for Connectathon

From DE4A
Revision as of 11:13, 28 June 2022 by Mpttfp eduardo.moreno (talk | contribs) (Created page with "This guide will provide some check points that should be done prior to a Connectathon session. Assuming you have already setup your own SMP and Connector instance. SMP • Che...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This guide will provide some check points that should be done prior to a Connectathon session. Assuming you have already setup your own SMP and Connector instance. SMP • Check the participant ID (Service Group) • Check your participant ID has the Canonical Evidences Types for your tests. • If you are a DE you will manage Response messages • If you are a DO you will manage Request messages • The Endpoint Reference will be the base URL of your Connector followed by ‘/phase4’ i.e. https://de4a.redsara.es/de4a-connector/phase4 • The certificate you will be using Once this configuration is proven correct, it will not be necessary to check it everytime.

Connector Once the application.properties configuration is set, it will not change Regarding the de-do.json, you can check the wiki page that shows the endpoint addresses that should be included. Again, once it is properly setup and working, you will not need to change it.

Wiki Page It will have centralized information about the pilot’s environment. We will need to maintain it updated. Whenever a partner updates anything or their side, it should also be updated in the wiki, so it is available for everyone.

General Tips • It would be helpful when testing a specific use case that you have access to the connector log file. • When having issues, it is better to test it before the connectathon in case it can be easily solved. Then we will avoid blocking issues during the live session. • Use Slack channels for support, your issue might be previously solved or could help others when experiencing the same issue.