Communications Manager components

A Communications Manager instance handles document processing for a particular partner and customer (tenant). In an on-premise deployment, Communications Manager instances are represented by numeric IDs (numbers) from 1 to 99, for example, Instance_21. A single Communications Manager instance comprises the following key components:

• Communications Manager Core – a component responsible for document composition by executing Document Templates and producing Document Packs. These jobs are executed by Document Processors. In addition, Communications Manager Core supports PDF processing and the creation of custom Core Services that implement Contract Manager interfaces.

• Communications Manager Repository – a component that stores and manages the Document Template definitions. Each Communications Manager Repository has a Repository server and Repository database that contains data for one particular tenant (that is, partner-customer combination explained in the next paragraph). Every Communications Manager instance requires its own Repository database, as instances do not share these databases.

• Communications Manager Designer – a web-based user interface that enables users to create and test Document Templates. It supports document life cycle management, revision management, and changesets control.

• Communications Manager ComposerUI for HTML5 – a component that supports integration of interactive document composition in a web application.

Each Communications Manager instance registers itself on the Contract Manager, as explained below.

Contract Manager acts as the main entry point that manages connections to Communications Manager instances and hands out work to these instances. Client applications send requests to the Contract Manager, which relays these requests to the appropriate Communications Manager instances according to a number of contracts that are defined at the Contract Manager. Each contract identifies a partner and a customer operating Communications Manager.

Generally, a partner is a Tungsten partner providing content management services by means of Communications Manager, and a customer is consuming these services.

For example, a default contract deployed during the Communications Manager installation sets partner to CCM, meaning that services will be provided by the solution itself. Customer is set to Local, meaning that services will be consumed by a local organization. You can add extra partners if needed, for example, a reseller.

Available operations are defined by contract types and their different versions. Each version of a contract type provides a consistent set of 2025.3 service calls required to handle specific operations. For example:

• The CCMInteractive contract type handles the definition, management, and composition of documents and Document Packs.

• The CCMAdministration contract type deals with common administrative tasks, such as adding a new user, assigning a role to the user for a particular project, and starting a Communications Manager Designer session.

If the predefined contract types are not sufficient, customers can add their own contract types and interfaces. These custom interfaces will need a Core Service for their implementation. See the Tungsten Communications Manager Core Guide and the Tungsten Communications Manager Core Scripting Language Guide for details on Core Services and Core Scripting.

Communications Manager Control Center is a central web application that monitors the entire 2025.3 installation.

Client applications can embed or redirect to Communications Manager Control Center, and Communications Manager Control Center has internal connections to all Communications Manager servers and Communications Manager components.

Communications Manager Batch & Output Management is an optional component that facilitates advanced multi-channel handling of produced output. It relies on an installed Communications Manager instance to provide Document Pack composition.