Enabling HTTPS for the MWS REST API Communication Channel - Installation - Foundation 23.2 - Foundation 23.2 - Ready - Content Composer - external

Content Composer Installation
Platform
Content Composer
Product
Installation
Release
Foundation 23.2
License
To enable HTTPS, complete the following steps on the Content Composer server:

Prerequisite

An SSL certificate from a Certificate Authority.

This certificate must have a subject name or subject alternative name that matches the DNS name of your Content Composer server.

  1. Import your SSL certificate into the certificate store under Local Computer > Personal.
  2. Verify that Certification Path and Certificate status are correct.
  3. To reserve the URL endpoint for non-administrator users and accounts, complete the following substeps:
    1. Identify the Windows user account that is configured to execute the Windows service Composer.MWS.
    2. Open a Command Prompt window with Administrator rights.
    3. To reserve the MWS URL, run the following command. Replace Windows-user-account before with the user account used to run the Windows Composer.MWS service. 
      netsh http add urlacl url=https://+:9010/ user=Windows-user-account
  4. From the Content Composer installation directory, open Composer.MWS.exe.config with a text editor that supports UTF-8.
  5. Find the following line within the <runtimeservices> element and uncomment it. 
    <service name="mwswebapi" assembly="ModusSuite.Runtime.MWSRuntimeService" type="ModusSuite.Runtime.MwsRuntimeServiceWebApi" />
    Note: If the line is not present, insert it within the <runtimeservices> element.
  6. Insert the following line within the <appSettings> element if it is not already present. 
    <add key="manVarResultXmlElementType" value="manvar2" />
  7. To configure the MWS REST API, complete the following substeps:
    1. Find the following line. 
      <mwswebapi ipport="9010" enablessl="true" allowedorigins="*" alivetimeouthour="100" />
    2. Ensure that the value of the enablessl attribute is set to true.
  8. Restart all Content Composer services.