NetarchiveSuite|
⇤ ← Revision 1 as of 2010-02-09 13:17:04
Size: 83
Comment:
|
Size: 816
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
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 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).