Skip to main content
Version: 2.10

Preparing for the installation

Before installing Document.One, make sure that you have a prepared infrastructure for installing the D1 system components. This page describes steps that you need to perform to prepare for the installation.

To prepare the infrastructure for DocumentOne system installation

  1. Review the Deployment use cases and specify what use case applies to you.
  2. Review the System requirements, and based on your deployment use case prepare servers for installing D1 components:
    • One or more servers for D1 (depends on your deployment case)
    • One or more servers for Conversion Service (depends on your deployment case)
    • If you are installing a production system, you will also need load balancers:
      • A load balancer for D1
      • A load balancer for Conversion Service.
  3. Review the Database requirements, install one or more databases (depends on your deployment case).
  4. For the production system, you must also configure the file system to be shared between D1 and Conversion Service nodes, so that all nodes have access to same files.
  5. Make sure that the installed databases are ready for installation of D1 and Conversion Service. For each database in your deployment type, the following conditions must be met:
    • The database is up and running, and you have the URL (host name and port) and user credentials for the database.
    • The database is accessible by the servers on which you plan to install D1 or Conversion Service.
    • The database user has permissions to create tables.
  6. Make sure that you have write permissions on the file system of the installation server.
  7. Make sure that the Document.One team has provided you with the following artifacts:
    • A valid license file
    • Deployment packages for the Conversion Service and D1.
Where to go from here

Go to Preparing files necessary for installation and review the contents of the installation package. If you experience database connection errors, go to Troubleshooting database errors.