Connecting a B&OM installation to an external Communications Manager instance

The following additional configuration steps are required when a Batch & Output Management installation is connected to a Communications Manager instance that is located on a different server:

  1. On the Communications Manager instance, run the InfoPorts.exe tool from the <deploy>/CommunicationsManager/Software/Management folder.

    Open the created information XML file, and find the CoreService and Repository ports.

    For Communications Manager instance 1 (and on Docker), these ports default to 10504 and 10600, respectively.

  2. Make sure that the Batch & Output Management server can connect to the Communications Manager instance server on both the CoreService and Repository ports. This may require opening ports on a firewall and/or creating port forwarding rules.

  3. Configure Core to accept connections from outside.

    See the Grant or restrict network access topic in the Communications Manager Core Developer's Guide for more information.

  4. Configure Batch & Output Management to connect to the Communications Manager instance:

    • Open Communications Manager Studio.

    • In the Administration tab, click System Administration. Next, click the system object.

    • Set the Host and Port properties of Communications Manager Core and Communications Manager Repository.

A secondary Batch & Output Management always connects to a remote instance. Therefore, its configuration always requires these steps.