Getting started (back-end)
Check-list to start the FORGE/NEXUS back-end
The Project team has to
- Create the VESPER custom entities in the Content Manager (see References)
- Set up the AWS SQS (see SQS Queue Setup)
- Set up the queue for the FORGE-VESPER Connector/Importer (see Connector configuration and Importer configuration)
- Add a support ticket on Vesper's Jira asking to configure VESPER to send events (entity changes) to the AWS SQS Queues for the many environments of the Project.
- (Only for clients who already use VESPER) Run the first VESPER-to-FORGE synchronization (see First VESPER-to-FORGE synchronization (if needed))
- Monitor the VESPER-to-FORGE synchronization (see Continuous VESPER to FORGE synchronization)
First VESPER-to-FORGE synchronization
Run the first synchronization only when clients have VESPER already in place.
The FORGE VESPER Importer is the service that imports for the first time the VESPER entities into FORGE. Is meant to run only once.
Check-list to run the Importer
- Get the CSV listing of the entities to import into FORGE from the VESPER team.
- Feed the Importer with the CSV by calling this endpoint: Import a CSV file.
How to observe the Importer
Swagger UI (ask the project team for the URL).
VESPER-to-FORGE synchronization
The FORGE VESPER Connector is the service that imports the VESPER entities into FORGE at any time a change occurs on VESPER.
Check-list to run the Connector
No action needed.
Changing entity names
Projects can change the name of the VESPER custom entities. In this case, the custom entity mapping must be updated as explained in Vesper events to FORGE custom entities mapping.
Projects cannot change the properties of the VESPER custom entities. The field-to-field mapping between VESPER entities and the corresponding custom entities is hard-coded.
How to observe the Connector
Swagger UI (ask the project team for the URL).