| Page Properties |
|---|
|
| Status | |
|---|
| Priority | 1 |
|---|
| Note |
|
|---|
| Assignee | Max (+DEV), Inga |
|---|
Resources |
...
By chunking up the system into microservices it can be tough to keep the overview of all available services, their relationships and dependencies to each other. The following graphical overview of our microservice architecture offers you a first entry point into the yuuvis® Momentum landscape. By providing further and more detailed examples based on special use cases (flows) you'll get a better and easy way of understanding our entire landscape.
Graphical Overview
For visualizing the topology of our microservices the following overview shows - on a higher level - many of our core microservices.
For understanding various flows - on a more granular level - check out the detailed diagrams visualizing special use case.
Login to the Core API - Authentication (Browser / Application)
...
| Expand |
|---|
| title | Click here to show the content retrieval flow by ID >> |
|---|
|
 Image Removed Image Added
| 1. - HTTP get request to object URL 2. - Enrichment of request with authentication Token 3. - Check for User Authorization using search service query 4. - Query elastic search for object ID 5. - Elasticsearch metadata response (if user is authorized) 6. - Repository url of objectId 7. - Request content of objectID 8. - Query objectId in Storage Provider 9. - Storage Provider metadata binary content response 10. - Return metadata object metadataobject binary content 11. - Write CONTENT_ACCESSED audit entry 12. - Create API response from metadatafrom binary content 13. - Return HTTP metadata response Webhook entry points *1 - dms.response.objects binary content response |
|
| Expand |
|---|
| title | Click here to show the content retrieval flow by ID (older version) >> |
|---|
|
 Image Removed Image Added
| 1. - HTTP get request to object URL 2. - Enrichment of request with authentication Token 3. - Check for User Authorization using search service query 4. - Query elastic search for object ID 5. - Elasticsearch metadata response (if user is authorized) 6. - Verify that user has object access rights 7. - Retrieve metadata version using Registry Service 8. - Query object metadata version from database 9. - Return metadata including Repository URL of content 10. - Return content Repo URL 11. - Request content of objectID 12. - Query objectId in Storage Provider 13. - Storage Provider metadata binary content response 14. - Return metadata object metadataobject binary content 15. - Write CONTENT_ACCESSED audit entry 16. - Create API response from metadatafrom binary content 17. - Return HTTP metadata binary content response Webhook entry points *1 - dms.response.objects |
|
Retrieval of Metadata by ID / Older Version
The metadata of already imported documents into the yuuvis® Momentum system can be retrieved using the provided core API's HTTP requests for retrieving the metadata (GET /api/dms/objects/{objectId}). If a specific version or all versions of the document's metadata is to be requested, the endpoints the endpoint to be called change changes and include includes the versions specific version (GET /api/dms/objects/{objectId}/versions / GET /api/dms/objects/{objectId}/versions/{versionNr}). >> Retrieving Documents via Core API
...
| Info |
|---|
|
Read on
| Section |
|---|
| Column |
|---|
| Another Tutorial Brief summary of the article linked.
|
| Column |
|---|
| Another Concept Article Brief summary of the article linked. |
| Column |
|---|
| Another interesting Tutorial Brief summary of the article linked. |
|
|