...
- use the GUI to do a pull or push (http://server_name:8042/omk/opHA/), select the server you want to push to or pull from (or select all to test them all) and press the appropriate button
the output will be a JSON document, with a hash entry for each successful file transfer:
Code Block { source: "vali", success: "Transfer complete", file_name: "nmis-summary8h", destination: "localhost" },
On error there will be a hash entry with an error key along with information to help you solve the problem
Code Block { url: "http://vali:443/login", error: "Error signing in", server_signin_url: "http://localhost:8042/omk/opHA/servers/vali/signin", message: "Transaction was not a success.", server_name: "vali" },
- check the logs and watch the transfers happen
- view the list of configured servers and check the "Last Update" column
Push/Pull Configurations
opHA allows to change some default connection settings to influence in the connection with the peer.
Code Block | ||
---|---|---|
| ||
'opha' => {
...
'opha_connect_status_expiry_time' => 5,
'opha_connect_timeout' => 3,
'opha_inactivity_timeout' => 5,
'opha_remote_endpoints' => [],
'opha_request_timeout' => 9,
'opha_websocket_reconnect_time' => 3
} |
opHA also allow to control the data that we are going to pull/push:
Code Block | ||
---|---|---|
| ||
'opha' => {
...
'opha_transfer_files' => [
{
'destination_dir' => 'var',
'destination_file_name' => '',
'source_dir' => 'conf',
'source_file_name' => 'Nodes'
},
{
'destination_dir' => 'var',
'destination_file_name' => '',
'source_dir' => 'var',
'source_file_name' => 'nmis-nodesum'
},
{
'destination_dir' => 'var',
'destination_file_name' => '',
'source_dir' => 'var',
'source_file_name' => 'nmis-summary8h'
},
{
'destination_dir' => 'var',
'destination_file_name' => '',
'source_dir' => 'var',
'source_file_name' => 'nmis-summary16h'
},
{
'destination_dir' => 'var',
'destination_file_name' => '',
'source_dir' => 'var',
'source_file_name' => 'nmis-event'
}
],
} |
Running a Master Collection
...