Container Maintenance
This page contains information about common scenarios for the Enterprise Glossary container stack.
Stop the Enterprise Glossary Stack
To stop all containers, run the PowerShell script stop.ps1 provided in the installation package or use the following Docker command:
Access Data in Volumes
Docker stores data in volumes in internal directories. Use the following commands to inspect or edit files:
# Docker --- find the volume mount point
docker volume inspect enterpriseglossary-project_sync-config
# Copy Config.xml into the volume
docker cp ./Config.xml enterpriseglossary-syncservice:/app/config/Config.xml
# Or use a temporary container
docker run --rm -v enterpriseglossary-project_sync-config:/data -v $(pwd):/src alpine \
cp /src/Config.xml /data/Config.xml
Change Ports
To change the ports used by Enterprise Glossary:
- Open the
.envfile in a text editor. - Update the values of
WEB_HTTP_PORTandWEB_HTTPS_PORT:
- Run the
stop.ps1PowerShell script to stop the container. - Run the
run.ps1PowerShell script to stop the container.
Enterprise Glossary is available on the new ports.
Run Multiple Instances Side-by-Side
To run multiple instances of Enterprise Glossary:
- Extract the content of the Xtract Universal.iQ Enterprise Glossary setup package into a separate folder.
-
Open the
.envfile in a text editor of your choice and change thePROJECT_NAMEand ports to avoid conflicts:title "Example" PROJECT_NAME=eg-testing-instance2 WEB_HTTP_PORT=8081 WEB_HTTPS_PORT=8444 -
Run the
run.ps1PowerShell script.
A new instance of Enterprise Glossary is available.
Use a Different Certificate
To replace an existing TLS certificate:
- Replace the certificate
eg.pfxin thecerts/folder with a new certificate by the same name. - Open the
.envfile in a text editor of your choice and update the value forCERT_PASSWORDwith the new password. - Restart the stack.
Enterprise Glossary now uses the new certificate.
Connect to a Database on the Host Machine
To connect Enterprise Glossary with a database, use the IP address of the database server in your connection string. Alternatively, use host.docker.internal as the server address in the application's connection string (the compose file maps host.docker.internal to the host gateway).
Remove Persistent Data
To delete all persistent application data stored in named volumes, run the following Docker commands:
docker volume rm enterpriseglossary-project_app-data
docker volume rm enterpriseglossary-project_uploads
docker volume rm enterpriseglossary-project_sync-config
docker volume rm enterpriseglossary-project_sync-logs
This permanently deletes all application data, uploaded files, and synchronization configuration. Back up any files you want to keep, e.g., Config.xml before running the commands.