https://www.infra-repository.org/oiar-2013/index.php?action=history&feed=atom&title=BT.DeploymentBT.Deployment - Revision history2026-05-06T13:56:40ZRevision history for this page on the wikiMediaWiki 1.40.0https://www.infra-repository.org/oiar-2013/index.php?title=BT.Deployment&diff=131&oldid=prevJan Schoonderbeek: start2012-11-11T23:22:21Z<p>start</p>
<p><b>New page</b></p><div>{{Maturity|2}}<br />
{{Pageheaderbox4BBT<br />
|name=Deployment<br />
|WorkingArea=Security & Support (SS)<br />
|version=0.21<br />
|owner=J.A.H. Schoonderbeek<br />
}}<br />
A Deployment facility serves as a means to install and configure (software) objects on a specified (remote) location with a certain level of automation. An important feature of this facility is that after deployment the software objects are ready for use (should require no, or relatively little, manual modification). Note however that this is independent of the ''configuration'' of the deployed software object.<br />
<br />
Examples are:<br />
* Automated provisioning of virtual servers,<br />
* automated deployment of web applications to a web farm,<br />
* "rolling out" PC images from a central server to distributed PC systems,<br />
* sending firmware updates to devices.<br />
{{FunctionIcon<br />
|image=Icon BBT Deployment.png<br />
}}<br />
{{BBT Text Footer}}</div>Jan Schoonderbeek