Difference between revisions of "DE4A Checklist for Connectathon"
Jump to navigation
Jump to search
(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...") |
|||
| Line 1: | Line 1: | ||
This guide will provide some check points that should be done prior to a Connectathon session. | 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. | Assuming you have already setup your own SMP and Connector instance. | ||
| − | SMP | + | |
| − | + | === 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 | 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. | Once this configuration is proven correct, it will not be necessary to check it everytime. | ||
| − | Connector | + | === Connector === |
Once the application.properties configuration is set, it will not change | 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. | + | |
| + | 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. | Again, once it is properly setup and working, you will not need to change it. | ||
| − | Wiki Page | + | === 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. | + | 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. In addition, '''whenever technical infrastructure info updates are made in the Wiki an email needs also to be sent to ATOS/WP5 to be aware of those changes.''' |
| + | |||
| + | === 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. | |
| − | |||
Revision as of 10:19, 28 June 2022
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. In addition, whenever technical infrastructure info updates are made in the Wiki an email needs also to be sent to ATOS/WP5 to be aware of those changes.
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.