Your browser was unable to load all of the resources. They may
have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.
Unfortunately QB does not support to move partial of configuration tree from one server to another. It is a all-or-none deal. However, you may write an external program utilizing the RESTful API to read confiurations from one server and write them to another server. For RESTful API details, please refer to developer's guide: http://wiki.pmease.com/display/qb30/RESTful+API
this is very important feature for running two systems ( Production and pre-production ). We constantly have problems maintaning one system with builds broken due to errors in QB scripting.
Now we are running two parallel systems and manually copy changes from one to another once proven safe.
Hi, I tried to migrate configuration using restful API. Generally it works fine, but QB removes all '\n' characters from multi-line fields when I create new configuration using exported xml file. This corrupts scripts and templates. Can I modify exported xml somehow to keep '\n' in place after import?
You may try with step "maintenance/sync configuration", it allows to sync part of configuration trees between two servers, and will not strip off the new line character.
When an older client makes a request to ws/savedCriteria with an authenticated user = foouser, should I return a 301 with ws/users/foouser/config/savedCriteria? Every distinct user who requests ws/savedCriteria will be redirected to a different URL, so a "Moved Permanently" seems not quite right. However, 302 implies moved temporarily, which is also wrong. 303 looks technically correct since the RFC says, "The new URI is not a substitute reference for the originally requested resource. The 303 response MUST NOT be cached, but the response to the second (redirected) request might be cacheable." However, I have never seen 303 used this way.