= Deploying NetarchiveSuite w/ application placed outside the KB and SB network = With the !DeployApplication it is straight-forward to place the harvesters on a different physical location than on Kb and SB (location OUTSIDE). Just define location OUTSIDE as a physicalLocation in the deploy configuration file. Note that the harvester-machines on location OUTSIDE need to have * write-access to a FTP-server, that can be seen from the bitarchiv servers on both SB and KB. * access to the JMSbroker on the Administrative machine in the netarkivet prod-environment. Note that FTP or SFTP is required as the transport method, as it is not possible to push data with the current network grouping of the Bitarchive-machines at KB, and therefore can't use the PUSH-transport methods (http or https). Deploying !NetarchiveSuite on location OUTSIDE can be done as we do today when deploying on KB and SB: * Run the deployApplication * Generate installation-packages for the three locations KB, SB, and OUTSIDE. * Copy the installation-packages to the respective locations * CLO coordinates the installation and starting of !NetarchiveSuite on the three locations == Template for configuring an OUTSIDE location in the deploy config file == {{{ lib/dk.netarkivet.harvester.jar lib/dk.netarkivet.archive.jar lib/dk.netarkivet.viewerproxy.jar lib/dk.netarkivet.monitor.jar -Xmx1536m .. .. /home/netarkiv netarkiv FTP-SERVER-ACCESSABLE-FROM-OUTSIDE-LOCATION ... ... OUTSIDE LOCATION MAILSERVER dk.netarkivet.common.utils.EMailNotifications prod@ADMIN-MACHINE clo@netarkivet.dk KB lib/dk.netarkivet.harvester.jar lib/dk.netarkivet.archive.jar lib/dk.netarkivet.viewerproxy.jar lib/dk.netarkivet.monitor.jar high_8081 8190 8290 HIGHPRIORITY 8380 8480 controlRole ... harvester_high_8081 high_8082 8191 8291 HIGHPRIORITY 8381 8481 controlRole ... harvester_high_8082 high_8083 8192 8292 HIGHPRIORITY 8382 8482 controlRole ... harvester_high_8083 }}}