CI HUB

Preconditions

Ci-Hub Specific Licences

In order for CI HUB to work, the following licenses are needed:

  • Licence for OMN CI-Hub connector needed

  • Subscription for corresponding desktop licenses from CI-Hub needed

Installation

Versioning must not be activated in order to use CI HUB. In case you want to be able to update an asset, then versioning must be activated.

CI HUB specific configurations

1) FSTable - Version Number Activation

The CI HUB FSTable must include the attribute "Number of versions", so that in the CI HUB Search the count of Asset Versions can be determined.

CI HUB FSTable configuration number of versions

2) Search

An Advanced Search must be configured, which includes the CI-HUB related FSTable.

CI HUB Advanced Search

3) AssetView

An AssetView must be configured

CI HUB AssetView

4) FSDetail (IPTC)

If IPTC attributes shall be included, they need to be configured in the config client

CI HUB FSDetail IPTC config client

CI HUB FSDetail with IPTC

Ci-Hub Specific Settings

Special settings in nginx

If you have installed OMN with accelerator, you could skip these settings since they are automatically done by accelerator.

Rule must be defined so that keycloak endpoints can be accessed by public.

endpoint for getting omn user roles:

location ~* /api/v1/login {
    proxy_pass $omn_backend_proto://$omnsrv:$omn_backend_port;
}

Dispatcher for keycloak endpoints:

location /auth {
    proxy_set_header X-Forwarded-For $proxy_protocol_addr; #To forward the original client's IP address
    proxy_set_header X-Forwarded-Proto $scheme; #To forward the  original protocol (HTTP or HTTPS)
    proxy_set_header Host $host; #To forward the original host requested by the client
    proxy_pass http://web:8085;
}

Keycloak settings

If you have installed OMN with accelerator, you could skip these settings since they are automatically done by accelerator.

Currently we have keycloak integration only for accelerator installation

Useful properties can be seen here

For the native installation if you want to use keycloak, please contact developer.

Property settings

For Asset endpoint we need this property to retrieve the preview URLs

omn.eai.common.includeUrls=true

This property is used to set which components are available (active). The value is separated by comma.

omn.eai.enabled-components=omn-search,omn-versioning

Versioning

If versioning will not be enabled, the create new version function in CI HUB will overwrite the existing file.

Configuration corresponding XML - Import files

Purpose Download for XML Hints

FSTable

Download the example FSTable plugin

Create and add FSTable plugin. The FSTable is needed for the search in CI HUB to work. The fields must be configured as in the sample xml file. If additional fields are configured, they will not be evaluated by CI HUB.

AdvancedSearch

Download the example AdvancedSearch plugin

Create and add AdvancedSearch plugin. The Search is required because the search attributes stored for the search are also available in the CI-Hub search. The configuration identifier of the AdvancedSearch must be "P.AdvancedSearch.CI-HUB.DAM" like in the example xml file, otherwise the search will not work.

AssetView

Download the example AssetView plugin

Create and add AssetView plugin. The AssetView is needed to retrieve information about an asset from OMN in CI-Hub

FSDetail

Download the example FSDetail plugin

Create and add FSDetail plugin. The FSDetail is needed to maintain / view the IPTC data supported by CI-Hub in our integration.

Restart Container

If you change anything, please restart the docker container 'OMN-Web' to make the new settings work.

Welcome to the AI Chat!

Write a prompt to get started...