res workspace manager unattended installation

Res workspace manager unattended installation update#

This way, you can perform the upgrades in DTAP order and remove the risk of downtime on the production environment.īut how do you control which machines connect to which database? You don’t want to create different images for each database and you probably don’t want to change it manually whenever you boot your machines. That means a dedicated ROW database for each environment.

The only viable solution to use DTAP is on the database level.

Res workspace manager unattended installation update#

The DTAP approach on the Workspace Container level doesn’t work in these situations since the update is on a higher level. So how would you use the DTAP approach in this situation? Sometimes when you upgrade the database also gets an update. This should suit you for about 90% of all your workspace related changes.īut what if you want to test a new ROW Service Release? Or even an upgrade to a complete new version? While I have RES in really high regard, most new versions do usually have some quirks in them and because of this, testing is in order. You could create a DTAP setup on that level. RES ONE Workspace (ROW from here on) of course has the very useful Workspace Containers. It also reduces the risk of downtime when developing or testing the new application.Ĭan you use this approach in combination with RES ONE Workspace? This method defines specific steps in the development of a new application or an update of a current one. After that de customer/(key-)users can approve of it in the Acceptance environment and when successful it can be deployed in de Production environment. The version is then tested in the Testing environment. An application gets developed for the specific organization in the Development environment. When implementing software, an organization usually wants to go for the DTAP approach (Development, Testing, Acceptance and Production).