Only HEIs that hold an Erasmus Charter for Higher Education (ECHE) can join the EWP network. The list of such HEIs is available in the ECHE list. Organisational units of a given HEI (faculties, departments) or consortia are not allowed to connect to the network separately.
More information about the ECHE list is available in Data sources section of thie Developers Guide. .
Information for the Dashboard users is available in a separate space, see Dashboard.
3rd-party and in-house mobility software providers should follow the steps explained below. Important parts of the procedure are described in two separate sections.
Information about the Collaboration Agreement that is required for 3rd-party and in-house providers to join the EWP network.
A step-by-step guide to the EWP Network
This section explains the process of obtaining technical information, meeting formal requirements, developing software, testing and validating the software, and eventually starting data exchange in the production network.
Providers of the mobility software to be installed in the EWP networks have to follow these steps. Most of them are mandatory, and some may be considered as advice or good practice.
In some steps, assistance from other users will be needed.
Locate sources of technical information, read relevant documents
✓ The EWP Developers Guide contains information for technically oriented readers and also links to other technical resources.
✓ The GitHub repositories contain information on the EWP network architecture and formal specifications of APIs.
Meet other providers and join EWP technical meetings
✓ If you are a 3rd-party provider, ask client HEIs (staff members with the EWP Admin attribute) to confirm their manifest files. Ask the Registration Portal administrator for help if you want to register manifest files with SCHAC codes that do not belong to your clients. For in-house mobility software this step is not necessary, as the manifest are confirmed by default.
Validate and test in the DEV network
✓ Prepare a test plan.
✓ Prepare your solution for testing.
✓ Use validators to test if the generated responses are compliant with the specification. All tests should give positive results, otherwise, the tested software will not be accepted in production.
✓ Test with the partners. If you cannot find testing partners, ask the EWP technical team for assistance. Optionally you can use the DEMO Testbed as the testing partner.
✓ Use test scenarios for testing the exchange of data between nodes in the DEV network.
✓ If you are a 3rd-party provider, ask client HEIs (staff members with the EWP Admin attribute) to confirm their manifest files. For in-house mobility software this step is not necessary, as the manifest are confirmed by default.
Exchange data in the PROD network
✓ As a provider, you are responsible for accurate training of HEIs using mobility software developed by you and for supporting them in using EWP-related functionalities.
✓ Assist your customers with interoperability issues encountered during data exchanges with partners. If necessary, contact other providers and together resolve the problems. Help in resolving issues related to your software raised in the ESCI Service Desk.
✓ Repeat all steps starting from Step 3.2 before releasing new versions in the PROD EWP Network.
Things can go wrong. When institutions violate the use of the EWP network, there should be an exit strategy. Institutions can report implementation issues of any particular node via the ESCI Service Desk. The EWP management will try to settle disputes and has the authority to exclude any institution from the production registry if it is in violation of the terms of usage. The institution will need to prove its ability and trustworthiness again in the development environment.