Installation overview
This topic shows which steps are involved in the installation of the core software components. If you are installing the product in a production environment, various departments within your organization would take care of various parts of the installation.
Step 1: Check hardware prerequisites
Before you start installing, check if the hardware you intend to use meets the minimal hardware requirements.
Step 2: Install the Add-on feature
Installing the Add-on feature consists of the following steps:
- Ensure that the software prerequisites for the database are met.
- Use PowerShell scripts to install the databases.
- Configure the Add-on Service for first-time use, and install the service.
Step 3: Create the Content Manager and Topology Manager databases
Installing the Content Manager and Topology Manager databases consists of the following steps:
- Ensure that the software prerequisites for the databases are met.
- Create a Windows user to access the databases and act as a Content Manager user.
- Use PowerShell scripts to install the databases.
Step 4: Install and configure the Content Manager server and Topology Manager
Installing and configuring the Content Manager server and Topology Manager consists of the following steps:
- Ensure that the software prerequisites for the Content Manager server and Toplogy Manager are met.
- Run the Content Manager Windows installer. This installer installs the Content Manager server and Topology Manager, including the server-side parts of the various clients.
- Configure the Content Manager server core.
- Configure the server-side parts of the various clients.
Step 5: Install and configure the Content Data Store and the Discovery Service and Experience Manager databases
Installing the Content Data Store and the Discovery Service and Experience Manager databases consists of the following steps:
- Ensure that the software prerequisites for the Content Data Store and for the Experience Manager database are met.
- If you intend to publish to a relational database, use a PowerShell script to install the Content Data Store.
- If you intend to use Experience Manager, use a PowerShell script to install the Experience Manager database.
- Always install the Discovery Service database.
Step 6: Install and configure core Content Delivery Server Roles
A Server Role encapsulates the files and resources you need to install on one or more servers to implement and use a certain Content Delivery feature (or the Content Delivery part of an Tridion Sites feature). Note that installing one Server Role may entail the installation of multiple software components: one or more microservices on the one hand, and client and/or API software on the other hand.
The installation and configuration of the Content Delivery environment would typically be the responsibility of the Core IT department.
Installing and configuring Content Delivery Server Role consists of the following steps:
- Ensure that the software prerequisites for the Content Delivery server are met on the machine(s) on which you intend to install the Server Role.
- Install the Content Delivery Server Role on the machine(s).
- Configure the Server Role you installed.
- Register the microservice you installed so that it may be discovered.
Step 7: Set up publishing by configuring Topology Manager
Run a number of PowerShell scripts to configure Topology Manager. The scripts specify the properties and locations of the Content Manager and Content Delivery environments, and create logical components for Content Manager to interact with.
The configuration of Topology Manager would typically be the responsibility of the Business IT department, based on input from the Web content management and Core IT departments.
Step 8: Install and configure the core Content Manager clients
Installing and configuring these clients consists of the following steps:
- Ensure that the software prerequisites for these clients are met.
- Install and configure the clients. Some of these clients are intended for implementers; others are intended for end users. Some run in a browser; others are desktop applications; yet others are plugins to commercial third-party software products.