Adding a Communications Manager Instance
This section describes individual installation of the Communications Manager instance to a single server. This may either be the same server that the Contract Manager resides on, or a separate server. The Communications Manager instance will be added to any existing ones on that server, if any.
Communications Manager instance handles the document processing for a particular partner and customer (tenant). It requires the web services account, the Java installation, and the Tomcat installation to be configured on the Communications Manager server.
You can use a command-line tool AddInstance.exe tool to do add a Communications Manager instance to an existing Communications Manager installation.
The new Communications Manager instance can be installed on the same server with the Contract Manager, or on the remote server.
AddInstance.exe doesn't install the Communications Manager instance in a running state. You can find the instructions on running this component in the Starting Communications Manager Instance section of this guide.
Additional requirements
This section lists the prerequisites and preparatory steps you have to take before you run AddInstance.exe.
Multiple Communications Manager instances with different contracts cannot use the same database for Communications Manager Repository, so make sure you have a dedicated database prepared for each Communications Manager instance you plan to deploy for a new contract.
Secondary instances can share a database (and therefore a contract) that is already in use by a primary instance. For more information, refer to the following topic: Scaling out composition.