General requirements

You need a valid license to use Communications Manager. When you purchase Communications Manager, you receive either a SAL activation code or a license XML file. The SAL activation code can be used to obtain the API key for the license server access.

When you install Communications Manager, you must provide either the address of the license server in combination with the obtained API key or the license XML file.

<?xml version="1.0" encoding="utf-8"?>
<ccm:Licence Version="1" xmlns:ccm="http://www.aia-itp.com/licence">
    <ccm:Product Name="ITP Server">
        <ccm:SubLicence Type="Base">
            <ccm:CompanyName></ccm:CompanyName>
            <ccm:NumberOfDocumentProcessors></ccm:NumberOfDocumentProcessors>
            <ccm:ExpirationDate></ccm:ExpirationDate>
            <ccm:Certificate></ccm:Certificate>
            <ccm:Environment></ccm:Environment>
            <ccm:LicenceCode></ccm:LicenceCode>
        </ccm:SubLicence>
        <ccm:SubLicence Type="OnLine">
            <ccm:ExpirationDate></ccm:ExpirationDate>
            <ccm:Certificate></ccm:Certificate>
            <ccm:NumberOfUsers></ccm:NumberOfUsers>
            <ccm:LicenceCode></ccm:LicenceCode>
        </ccm:SubLicence>
    </ccm:Product>
    <ccm:Product Name="ITP MDK Repository">
        <ccm:SubLicence Type="Base">
            <ccm:CompanyName></ccm:CompanyName>
            <ccm:ExpirationDate></ccm:ExpirationDate>
            <ccm:Certificate></ccm:Certificate>
            <ccm:Environment></ccm:Environment>
            <ccm:LicenceCode></ccm:LicenceCode>
            <ccm:NumberOfUsers></ccm:NumberOfUsers>
        </ccm:SubLicence>
        <ccm:SubLicence Type="Model Developer">
            <ccm:CompanyName></ccm:CompanyName>
            <ccm:ExpirationDate></ccm:ExpirationDate>
            <ccm:Certificate></ccm:Certificate>
            <ccm:Environment></ccm:Environment>
            <ccm:LicenceCode></ccm:LicenceCode>
            <ccm:NumberOfUsers></ccm:NumberOfUsers>
        </ccm:SubLicence>
        <ccm:SubLicence Type="Textblock Editor">
            <ccm:CompanyName></ccm:CompanyName>
            <ccm:ExpirationDate></ccm:ExpirationDate>
            <ccm:Certificate></ccm:Certificate>
            <ccm:Environment></ccm:Environment>
            <ccm:LicenceCode></ccm:LicenceCode>
            <ccm:NumberOfUsers></ccm:NumberOfUsers>
        </ccm:SubLicence>
    </ccm:Product>
</ccm:Licence>

Communications Manager Core uses Microsoft Word for a number of operations such as printing and conversion of documents. To enable these operations, Microsoft Word must be installed locally on the servers that run Communications Manager Core Document Processors.

You should disable grammar and spelling tools in Microsoft Word. For more information, see the Adjust settings in Microsoft Word section below.

Also, Microsoft Word requires the presence of a Desktop directory. The location of this directory depends on the versions of Microsoft Word and Microsoft Windows. For 64-bit versions of Microsoft Word, create the following directory: %WINDIR%\System32\config\systemprofile\Desktop.

Communications Manager Core attempts to create this directory if it does not exist yet. If it fails, Communications Manager Core is unable to open Microsoft Word documents.

This section describes the requirements for ports that must be satisfied for successful Communications Manager installation.

When deployed, by defaultTungsten Communications Manager uses the following ports. You can configure the installation tool parameters to setup other ports if necessary.

This section describes some decisions you'll have to make during installation regarding the security of communication with Communications Manager server and the artifacts that you have to prepare beforehand.

If you find that self-signed certificates are secure enough for internal communication in Communications Manager, then you can have Communications Manager generate the internal certificates.

This section describes the requirements for databases that must be satisfied for successful Communications Manager installation.

Communications Manager uses databases to store production data.

• If you plan to deploy Communications Manager only (without Batch & Output Management), you will need a Communications Manager Repository database.

  In some cases, you can share the same repository database between multiple Communications Manager installations. For more information, refer to the following topic: Adding a Communications Manager Instance.

• If you also plan to deploy Batch & Output Management, you will need a B&OM Repository database and B&OM Runtime database.

You can find the list of supported databases in the Tungsten Communications Manager Technical Specifications document.

The deployment does not require a dedicated database server. You can use the database server that is already operating in your environment.

1. Create all required databases manually.
2. Before starting the installation, make sure these databases are empty.
3. Back up all databases on a regular basis and follow the best practices recommended by your database provider.
4. Unless following specific instructions from Tungsten Technical Support, do not make database modifications, because they may cause irreversible damage and loss of data.

Communications Manager performs a check on the database access, using the provided database connection string and database user and password. It checks the database access settings before starting the actual execution of various tools. This check is limited and might erroneously show messages about missing permissions.

To override this check, use the Instance!ContinueInstallationOnFailedDatabaseAccessCheck=true or OutputManagement!ContinueInstallationOnFailedDatabaseAccessCheck=trueparameter to indicate that execution should continue even when the check returns a negative result. This does not override the check on an empty database.

The Communications Manager installation and upgrade tools verify that the provided user accounts have the Logon as Service right. This pre-flight check succeeds only if the Logon as Service right is set to the user account directly. When a user account has the Logon as Service as a right via a Group or in any other way, you can disable this check. To do this, use the following steps:

1. Find the KCMTools.ini file. Before installation or upgrade, this file is located in the Software/KCMTools folder of the extracted Communications Manager 2025.3 package.

2. Add a section with name ServiceAccounts.

3. Add a setting with name Trusted and fill it with a comma-separated list of user accounts that should have the Logon as Service pre-flight check disabled. Each user account must appear exactly the same as in the command line.

The strict cookie path of the session cookie that is returned by the Contract Manager may require proxies between the clients and the Contract Manager to rewrite the cookie. In particular, this applies to the proxy rules in the Tungsten TotalAgility web.config file. For Tungsten TotalAgility versions before 2025.2, the following rule should be added to the configuration/system.webServer/rewrite/outboundRules node:

<rule name="UpdateCCMCookiePath">
    <match serverVariable="RESPONSE_Set_Cookie" pattern="(.*); Path=.+?;(.*)"/>
    <conditions>
        <add input="{CACHE_URL}" pattern="https?://[^/]+(/[^/]*)?/CCM/Proxy/.*"/>
    </conditions>
    <action type="Rewrite" value="{R:1}; Path={C:1}/CCM/Proxy;{R:2}"/>
</rule>