In some scenarios, you may need to run Curator Server as HTTP. This may be necessary in some of the following cases:

• A cloud Environment where a load balancer is being used.
• A non-public-facing Curator system.
• A Curator system whereby certificates are not being used.

 This guide will explain how to configure your system in order to allow for this to happen.

Curator Server Configuration

The steps below show how to update the configuration of the Curator Server to run as HTTP

1. Back up the Curator Server Service Configuration File.
   This can be found at the following location by default:
   "C:\Program Files\IPV\Curator\Server\Services.CuratorServer.Hosts.WindowsService.exe.Config"
2. Open Services.CuratorSever.Hosts.WindowsServices.exe.Config in Notepad++
3. Use Find within Notepad++ to locate the following line:
   <SslCertificateConfiguration storeName="My" thumbprint="*ThumbPrintValue*"/>
4. Remove the value assigned to Thumbprint (see below for an example):
   <SslCertificateConfiguration storeName="My" thumbprint=""/>
5. Locate the commented-out HTTP service config within the Configuration file. Use Find within Notepad++ to locate the following line:
   <!--  HTTP service config
6. Copy everything between the following lines from within the commented-out section:
   <service behaviorConfiguration="serviceBehavior" name="Services.CuratorServer.Library.CCuratorServer">
   AND
    </service> 
7. Navigate to the following section of the config using Find:
   <service behaviorConfiguration="serviceBehavior" name="Services.CuratorServer.Library.CCuratorServer">
8. Select everything between the following line from within the HTTPS active section:
   <service behaviorConfiguration="serviceBehavior" name="Services.CuratorServer.Library.CCuratorServer">
   AND
   </service>
9. Once selected, paste the section which was previously copied which will overwrite the HTTPS configuration section with the HTTP configuration.
10.  Start Curator Service within services.msc. The service will now be running as HTTP.

Curator Gateway API Route Configuration

The steps below show how to update the API routes within Gateway for Curator Server to run as HTTP

1. Browse to Curator Gateway URL
2.  Select API Routes from the right tab selection in UI
   
3. Select the /curatorserver/{catchall} API route:
4. Change Scheme using the drop-down from HTTPS to HTTP.
5. Select Save from the bottom left of the UI.
6. Repeat the above steps for the API route /curatorservernotifications/{catchall}Below is a complete update:

Process Engine Monitor Configuration

The steps below show how to update the Process Engine Hosts so that Curator Server runs as HTTP

1. Launch Process Engine Monitor UI via Curator Gateway
2. From the home page, select Configure Hosts
3. Update Curator Server Host URL to be HTTP instead of HTTPS. See below:Example URL if blank - http://*CS_HOST_NAME*:11210
4. Select Save and Run Setup – System Setup V2 will run.
5. Once the workflow has completed, Curator Server Service will be now running as HTTP.

Once the above has been configured, the Curator system should now work successfully using HTTP.