› Communications Manager Installation Guide › Manual component installation › Communications Manager structure installation

Communications Manager structure installation

This section describes the installation of the Tungsten Communications Manager structure to a single server where it hasn't been installed yet. The Tungsten Communications Manager structure is a prerequisite for adding Tungsten Communications Manager components.

To install the Tungsten Communications Manager structure, use the command-line tool PrepareServer.exe.

Additional requirements

This section lists the prerequisites and preparatory steps you have to take before you run PrepareServer.exe.

The <deploy root> folder where you are going to install the software, must consist of ASCII characters.

Before you start, make sure that your environment satisfies the general Tungsten Communications Manager installation requirements.

  1. Prepare the user account for the Windows services of Tungsten Communications Manager, which will be used by all Tungsten Communications Manager components. This account must have the local Administrator permissions on the target server.

  2. Unless you only plan to install Batch & Output Management on the server, prepare the user account for the web applications of Tungsten Communications Manager that will be used by all Tungsten Communications Manager web components. Additionally, make sure that the server contains Java and Tomcat installations that are supported by Tungsten Communications Manager.

    The user account can be a local or a domain account. It requires:

    • Logon as a service right.

    • Read and execute permission on the Tomcat installation folder.

  3. If you plan to install the Contract Manager and/or Tungsten Communications Manager Control Center on the server, designate ports that can be used for public access. The server must be accessible on these ports from all client machines.

    Additionally, prepare a SSL certificate for encrypting connections to those ports. The certificate must be a password protected file in a format that is supported by Tomcat (for example, JKS or PKCS12). Also assign read permissions on the SSL certificate for the web services user.