Knowledge Discovery Docker Compose Files
The Knowledge Discovery Docker Compose files allow you to quickly set up a system that uses multiple containers, connected together to provide a Knowledge Discovery setup.
There are several sets of Docker Compose files that you can use:
basic-idol
. Set up a simple Knowledge Discovery system so that you can ingest some data and run queries.data-admin
. Set up Data Admin and the components that it requires to run.site-admin
. Set up a simple Knowledge Discovery system so that you can ingest some data and run queries. This setup includes Site Admin to administer the services.
NOTE: The basic-idol
, data-admin
, and site-admin
names are the folder names in the provided Knowledge Discovery Docker Compose package. The examples in this section are based on these standard names. If you change the folder names, or modify the COMPOSE_PROJECT_NAME
environment variable, it affects the container names that Docker produces, and you must adapt the example commands.
Basic Knowledge Discovery Docker Compose
The basic-idol Docker Compose setup has a standard docker-compose.yml
file that creates a small Knowledge Discovery setup. This basic setup includes the following containers:
content
. The Content component, for indexing and query.nifi-minimal
. A basic version of NiFi Ingest, configured with a File System Connector, to allow you to process and ingest files into your Content component.categorization-agentstore
. An Agentstore component configured to work with categorization tasks in NiFi Ingest.find
. The Find user interface, to allow you to view results from your Content index.community
. The Community component, which Find uses to manage users.agentstore
. An Agentstore component configured to store users and agent data for Community.view
. The View component, which Find uses to display document previews.
When you use this setup, you can copy files into an internal volume. This volume is monitored by a File System Connector, running within NiFi. Any files that you copy to the volume are ingested and the resulting documents are indexed into the Content component. You can then log in to Find to send queries to find this data.
By default, this setup does not allow you to access the component ports directly, and does not enable SSL.
OpenText also provides several additional compose files to allow you to extend the basic setup. The following table describes these additional files.
Docker File | Description |
---|---|
docker-compose.add-docsec.yml
|
Adds document security for your documents. This option includes an OmniGroupServer to retrieve user and group information from an LDAP server. |
docker-compose.bindmount.yml
|
Provides a bindmount. This option allows you to copy files to a physical directory for the File System Connector to ingest them, rather than using Docker copy. |
docker-compose.expose-ports.yml
|
Exposes the component ports in the containers, so that you can connect to the components directly. |
docker-compose.ssl.yml
|
Enables SSL communications for the basic Knowledge Discovery components. |
docker-compose.add-mmap.yml
|
Adds Media Server to allow you to process image, audio, and video files in addition to text-based content, and the MMAP application to allow you to perform more advanced analysis on the audio and video. |
docker-compose.add-mmap.ssl.yml
|
Enables SSL communications for MMAP and Media Server. |
Data Admin Docker Compose
The data-admin
Docker Compose setup has a standard docker-compose.yml
file that creates the required containers to run Data Admin.
You can optionally include docker-compose.ssl.yml
to run Data Admin and the components with SSL communications enabled.
You can optionally use docker-compose.expose-ports.yml
, if you want direct access to all of the component ports.
Site Admin Docker Compose
The site-admin
Docker Compose setup has a standard docker-compose.yml
file that creates a small Knowledge Discovery setup, including Site Admin for administering the ACI servers.
You can optionally use docker-compose.expose-ports.yml
, if you want direct access to all of the component ports.