Skip to main content

Downloads

Downloadable example packages for Uxopian AI. Each package is a ZIP archive containing Docker Compose files and configuration templates.

Available packages

Docker Compose quickstart

A minimal stack: OpenSearch, uxopian-ai, and uxopian-gateway with DevProvider for local development.

Contents:

  • uxopian-ai-stack.yml: Docker Compose file
  • gateway-application.yaml: Gateway configuration with DevProvider
  • config/: All required YAML configuration files for uxopian-ai

See Quickstart with Docker Compose for step-by-step instructions.

Docker Compose with ARender

Full stack including ARender services (UI, DSB, renderer, text handler, converter), uxopian-ai, and uxopian-gateway. Includes ARender configuration files for the AI top-panel integration.

Contents:

  • uxopian-ai-stack.yml: Docker Compose file with ARender services
  • gateway-application.yaml: Gateway configuration
  • config/: uxopian-ai configuration files
  • arender/configurations/: ARender plugin and top-panel configuration files

See Quickstart with ARender for step-by-step instructions.

FlowerDocs scope files

Static scope files for embedding the Uxopian AI chat panel in FlowerDocs. These files are installed in the FlowerDocs scope Maven build, not deployed as a Docker stack.

See Quickstart with FlowerDocs for step-by-step instructions, or Integrate with FlowerDocs for the production-ready setup.

FileNet ICN plugin

Source-only — no prebuilt JAR is distributed, so you build and control what's deployed to WebSphere.

Download

uxopian-icn-plugin.zip — Maven project to build for your environment

Source package contents:

  • pom.xml: Maven build descriptor
  • icn-plugin.p12: Default PKCS12 keystore — replace before production
  • src/: Java sources for plugin, proxy service, action, feature, and JWT utilities
  • src/main/resources/com/uxopian/icn/WebContent/actionHandler.js: Dojo frontend module

navigatorAPI.jar (IBM's proprietary Navigator API) is not bundled — supply it from your own ICN installation (see Integrate with FileNet, 1.1).

See Getting started with FileNet for the integration path, or Integrate with FileNet for deployment instructions.