{"metadata":{"image":[],"title":"","description":""},"api":{"url":"","auth":"never","results":{"codes":[]},"settings":"","params":[]},"next":{"description":"","pages":[]},"title":"Verify Service Ownership","type":"basic","slug":"testing-allowed-only-for-your-own-services","excerpt":"Load testing is only allowed for the services you own","body":"Spatineo Performance is a powerful tool to creating considerable amounts of load for the target services. It’s quite easy to create tests which take so much of the server’s resources that those services become unavailable to all other users. Normally you should only run the heavier tests during the service maintenance breaks or before launching a service in public. It’s always a good idea to start testing a new service with a reasonably low request rate test and then increase the load in the next tests to see how the increasing load affects your services and the it’s backend systems like databases and disks.\n\nBecause of the potentially harmful effects for running the tests, the load testing with Spatineo Performance is limited only to the services that you own or have full control over. The ownership is verified by the claiming process during which you have to install a specifically created, organisation specific text file under the web server domain used for hosting the tested WMS, WFS or WMTS services. The same claiming process is used also for Spatineo Monitor, so you only need to claim each the service once.\n\nSpatineo Performance will automatically guide you through the service claiming process when you create a test for non-claimed service.","updates":[],"order":14,"isReference":false,"hidden":false,"sync_unique":"","link_url":"","link_external":false,"_id":"5ccaf606c63d3c013b50f6ac","category":{"sync":{"isSync":false,"url":""},"pages":[],"title":"Spatineo Performance","slug":"spatineo-performance","order":2,"from_sync":false,"reference":false,"_id":"5ccaf606c63d3c013b50f6a8","version":"5ccaf606c63d3c013b50f6bc","project":"544f6e49698ab40800b4f41e","createdAt":"2014-10-28T12:09:46.911Z","__v":0},"user":"544f6e19cf9f86080080129a","project":"544f6e49698ab40800b4f41e","version":{"version":"3.13","version_clean":"3.13.0","codename":"","is_stable":true,"is_beta":false,"is_hidden":false,"is_deprecated":false,"categories":["5ccaf606c63d3c013b50f6a6","5ccaf606c63d3c013b50f6a7","5ccaf606c63d3c013b50f6a8"],"_id":"5ccaf606c63d3c013b50f6bc","project":"544f6e49698ab40800b4f41e","__v":0,"forked_from":"5a5879a7086a05001c4317ac","createdAt":"2018-01-12T09:02:31.335Z","releaseDate":"2018-01-12T09:02:31.335Z"},"createdAt":"2014-10-28T20:15:06.547Z","githubsync":"","__v":0}

Verify Service Ownership

Load testing is only allowed for the services you own

Spatineo Performance is a powerful tool to creating considerable amounts of load for the target services. It’s quite easy to create tests which take so much of the server’s resources that those services become unavailable to all other users. Normally you should only run the heavier tests during the service maintenance breaks or before launching a service in public. It’s always a good idea to start testing a new service with a reasonably low request rate test and then increase the load in the next tests to see how the increasing load affects your services and the it’s backend systems like databases and disks. Because of the potentially harmful effects for running the tests, the load testing with Spatineo Performance is limited only to the services that you own or have full control over. The ownership is verified by the claiming process during which you have to install a specifically created, organisation specific text file under the web server domain used for hosting the tested WMS, WFS or WMTS services. The same claiming process is used also for Spatineo Monitor, so you only need to claim each the service once. Spatineo Performance will automatically guide you through the service claiming process when you create a test for non-claimed service.