| 50 | | The global topology file states what clusters will be connected by the MTO, and on which port the MTO will communicate with other MTO's. It should be the same for all the MTO's participating. The local configuration states how the MTO can be contacted by MUSCLE within the cluster. It also implies that MUSCLE can only use a limited port range on a given cluster. Each cluster should use a different port range. To make this information available to MUSCLE 2, create the file `MUSCLE_HOME/etc/muscle.defaults` matching the `mto-config.cfg` file, containing |
| | 50 | The global topology file states what clusters will be connected by the MTO and on which port it will listen for connecting MTOs. The file should be the same for all participating MTOs. |
| | 51 | |
| | 52 | The local configuration states how the MTO can be contacted by MUSCLE 2 within the cluster. It also specifies a limited port range on a given cluster, which should be different for each participating cluster. The `internalAddress` may be set to an IP-address or hostname that is accessible from all nodes in the cluster. If the host has multiple internet interfaces, the wildcard address `*` may also be specified here. For example, the wildcard is useful for aliasing the hostnames `localhost` and the fully qualified domain name and for running the MTO in a virtual machine. |
| | 53 | |
| | 54 | To make the information about the local MTO available to MUSCLE 2, create the file `$MUSCLE_HOME/etc/muscle.defaults` matching the `mto-config.cfg` file, containing |
| | 55 | |
