Documentation Center

Back end server

The back end server's main responsibility is to provide execution for all queued actions initiated by user actions or web service calls, including translation functionality.

Three roles are required to accomplish this

  • The Web role allows accessing Organize Space and the web services from the same server.
  • The Default background task role provides execution for the Background task component.
  • The Translation role provides functionality for translation-related flows.

The back end server is in other words the work horse for the non-interactive and long running flows. The Web role exposes internal endpoints through the Internet Information Services which is the default web engine on a Microsoft Windows Server operating system. All the endpoints are secured with secure sockets layer (SSL) to provide the https schema. The SSL certificate has to be configured with intranet accessibility only in mind.

The certificate's subject name must match the hostname for the endpoints that the clients will be using. Since the accessibility to this server is only through intranet, Organize Space and the web service client use fully qualified domain name (FQDN) based endpoints like https://back.ish.example.com/ISHCSORA19/ (where ish refers to an example related to Content Manager, and back specifies it further as a back end server) and https://back.ish.example.com/ISHWS/Wcf/API25/Application.svc.

The Default background task role is configured out of the box to execute all possible handlers. This means that all dependencies must be installed and properly configured on this server. For example third party renderer licenses must be properly configured when this server will be used to publish. If the dependencies are not present, the Default background task role will execute the pending items but error's will be raised.

The Translation role also requires configuration, like the target endpoints of WorldServer or TMS for example.

We recommend re-purposing the existing Full text indexing role, typically installed on a front end server, by forwarding the requests of the back end server.