-
Content Composer version EP4 or higher.
-
Minimum two Content Composer REST API servers for communication with Content Composer Studio and Web Client.
For more information, see "About Configuring the MWS REST API Communication Channel" in the Content Composer Installation Guide.
-
A front-end web server. The Content Composer Web Client must be hosted in IIS on another system or one of the Rest API servers.
-
A load balancer server and its DNS name.
-
A Content Composer Studio installation on a computer other than the servers.
-
A database server, accessible from the Content Composer servers and Content Composer Studio.
-
At least two different IP ports, one for WCF communication between the Content Composer services and Content Composer Studio, and another port for the MWS Rest API and Content Composer Web Client.
-
All Content Composer servers must have access to the shared network directory in which the configuration files reside.
-
The Windows user account that executes the Content Composer service Composer.Core must have full access to the shared network directory.
-
An SSL certificate. For more information, see Installing the Certificate.
-
Content Composer servers and Studio must be configured so that they all use the same port that is open for external network communication.
-
Content Composer server, Studio, and Web Client must be configured to use HTTPS.
-
The Content Composer servers must be configured to use a common database using the database server name.
-
The Content Composer servers must be configured to use a shared folder to access the shared configuration files.
-
The system must support TLS 1.2