On-Premises Deploymentlink

DocuWare Ivy ships as a container image with the DocuWare-branded Portal already inside it. On-premises it runs on a Linux host under Docker Compose and is published to users through the IIS that already serves DocuWare.

These guides are the whole path, in order: to a running engine, then behind IIS, then connected to an identity provider for users and sign-in. The last two are alternatives — either Microsoft Entra ID signs users in, or DocuWare does.

• Prepare the environment
  • Checklist
  • The database
  • 1 · Create the virtual machine
  • 2 · Install Ubuntu
  • 3 · Install Docker
  • 4 · If you work through a jump host
  • 5 · Request the licence, with the right name on it
  • Next
• Install DocuWare Ivy
  • The whole thing, in order
  • How to read the commands
  • 1 · Choose the image
  • 2 · Fill in two files
  • 3 · Copy them to the Linux host
  • 4 · Start
  • 5 · Open the portal
  • 6 · Four checks
  • 7 · Create the first user
  • 8 · Confirm mail works
  • 9 · Upgrading
  • 10 · When something is wrong
  • 11 · Reporting a problem
• Publish through IIS
  • Download the scripts
  • Before you start
  • Run the script
  • Verify
  • Two limits IIS imposes
  • Roll back
  • If something goes wrong
• Connect Microsoft Entra ID
  • Both products, one sign-in
  • The redirect URI is not what you would guess
  • What to ask for when registering the application
  • Configure the engine
  • Who creates the users
  • Skipping Ivy's own login page
  • The DocuWare side
  • Keeping the sign-in proxy in front
  • Signing out
  • Single sign-on is a separate feature
• Sign in with DocuWare
  • Before you start
  • Configure it
  • If DocuWare's certificate is not trusted
  • Add the users
  • Check it works
  • Signing out
  • If something is wrong

infoNote

Note

This is a getting started guide. It shows how to set up DocuWare Ivy on-premises and get it working end to end, and it assumes no prior Linux experience: every command is given in full and every step says what you should see.

It is not a production-ready installation guide. An installation that people depend on has plenty of aspects that must be tailored to the particular target environment, infrastructure and requirements — sizing, availability, backup, monitoring, certificates, network segmentation — and those decisions belong to whoever designs that environment.