Resources

Remarks

Introduction

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)

...

To interact with yuuvis® it is necessary to log in with a user account. The user accounts are managed by at least one external identity provider.

...

1. - HTTP request to any API endpoint, sending basic authentication or bearer token

2. - verify credentials externally

3. - receive auth code to authentication with auth code

4. - request roleset acquisition

5. - query user roleset externally

6. - receive user roleset

7. - present roleset

8. - provide authentication token and proceed with initial API request

9. - request information from other parts of the system

10. - obtain requested information

11. - produce API response

12. - send HTTP response to user

Webhook entry points

*1 - user.info

Expand
title Click here to show the authentication flow (application) >>
	Image Removed

Include Page
Authentication Flow (Application) Authentication Flow (Application)

1. - HTTP request to any API endpoint

2. - Redirect to Identification Provider

3. - Verify Credentials externally

4. - Redirect to authentication with Auth code

5. - Send Auth code to Authentication Service

6. - Retrieve UserId using Auth code

7. - Recieve UserId

8. - Request roleset acquisition

9. - Query user roleset

10. - Recieve user roleset

11. - Present roleset

12. - Provide authentication token and Proceed with initial API request

13. - Request information from other parts of the System

14. - Obtain requested information

15. - Produce API response

16. - Send HTTP response to User

Webhook entry points

*1 - user.info

Expand
title Click here to show the authentication flow (browser) >>
	Image Removed

Include Page
Authentication Flow (Browser) Authentication Flow (Browser)

Note
The authentication flow is always part of all described flows. It is used to get a valid authentication token for further processing.

To interact with yuuvis® Momentum, it is necessary to log in with a user account. The user accounts are managed by at least one external identity provider.
>> Concept: Authentication against the Core API
>> Example Tutorial: Login to the Core API (Java)

Anchor
graphicalOverview_ImportingDocuments graphicalOverview_ImportingDocuments

Importing Documents

Documents can be imported into a yuuvis® Momentum system using the provided core API's HTTP requests for importing documents (POST /api/dms/objects). 
>> >> Example Tutorial: Importing Documents via Core API

Retrieval of Content by ID / Older Version

The content of already imported documents into the yuuvis® Momentum system can be retrieved using the provided core API's HTTP requests for retrieving content files (GET /api/dms/objects/{objectId}/contents/file). If a specific version of the document's content is to be requested, the endpoint to be called changes and includes the specific version (GET /api/dms/objects/{objectId}/versions/{versionNr}/contents/file). 
>> >> Example Tutorial: Retrieving Documents via Core API

Retrieval of Metadata by ID / Older Version

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 response

10. - Return metadata object metadata

11. - Write CONTENT_ACCESSED audit entry

12. - Create API response from metadata

13. - Return HTTP metadata response

Webhook entry points

...

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}). 
>> >> Example Tutorial: Retrieving Documents via Core API

...

...

...

...

1. - HTTP get request to object URL

2. - Enrichment of request with authentication Token

3. - Request metadata

4. - Query objectId in database

5. - DB metadata response

6. - Write METADATA_ACCESSED audit entry

7. - Return metadata object metadata

8. - Create API response from metadata

9. - Return HTTP metadata response

Webhook entry points

*1 - dms.response.objects

Search Queries

Already imported objects into the yuuvis® Momentum system can be queried using the provided core API's HTTP request with the search query as request body (POST /api/dms/objects/search).
>> CMIS-Based  
>> Concept: Search Query Language

Update Content

The content of an already imported document into the yuuvis® Momentum system can be updated using the provided core API's HTTP requests for updating the content (POST /api/dms/objects/{objectId}/contents/file). 
>> >> Example Tutorial: Updating Documents via Core API

Update Metadata

The metadata of an already imported document into the yuuvis® Momentum system can be updated using the provided core API's HTTP requests for updating the metadata (POST /api/dms/objects/{objectId} / PATCH /api/dms/objects/{objectId}). 
>> >> Example Tutorial: Updating Documents via Core API

Deletion

An already imported document into the yuuvis® Momentum system can be deleted using the provided core API's HTTP requests for deleting documents (DELETE /api/dms/objects/{objectId}). 
>> >> Example Tutorial: Deleting Documents via Core API

Summary

...

Read on

...

...

Another Tutorial

Brief summary of the article linked.

...

Another interesting Tutorial

...