Use Runtime.deployment.Deployer when you do not have access to a browser or graphical user interface environment, and you want to perform deployment tasks. You can also use Runtime.deployment.Deployer when you want to automate deployment tasks through batch processes.

An automated deployment through a batch mode can be initiated by configuring the DeploymentConfiguration.properties file located in the URL http://<host>:53307/CentraSite/CentraSite/ino:dav/ino:dav/projects/CentraSite/configuration.

BatchSize is the maximum number of Virtual Services to be pushed to the Mediator before a syncpoint is taken. The default BatchSize is 50. To improve performance, you can set a BatchSize to define the maximum number of Virtual Services to be pushed between two syncpoints using the property line:

The BatchSize property can be set at any time. If a bulk deployment is already in progress, the current batch is sized according to the previous batch size. Subsequent batches use the new size. Suppose if the BatchSize is set to zero and changed while a deploy operation is already in progress, that operation loads the data as a single batch. Any subsequent deploy operations on the same CentraSite Control use the new BatchSize.

TransactionTimeout specifies the maximum time, in milliseconds, allowed for deployment operations (deployment or undeployment) that were pushed to Mediator to respond. Any such operations that do not respond before this timeout occurs are rolled back. The default TransactionTimeout is 6000 (ms). To improve performance, you can set a TransactionTimeout to define the maximum time for the deployment operations to respond using the property line:

For example, if a deployment operation attempts to set a transaction timeout of 360 seconds, and the TransactionTimeout setting is 300 seconds, the TransactionTimeout setting of 300 seconds is used. After the TransactionTimeout of 300 seconds the deployment operations roll back.