Setting General Deployment Defaults

Option	Entry
Large File Support	For Integration Server packages and webMethods files, indicate whether you want Deployer to stream from the source server to Deployer and from Deployer to the target server by default for all projects. If you choose not to stream, the build size of a project containing Integration Server packages and webMethods files cannot exceed the amount of RAM configured for the source or target Integration Server or Deployer. If it does, you will have to distribute the Integration Server packages and webMethods files across multiple projects (and thus multiple project builds) instead. If you choose to stream, the build size of a project containing Integration Server packages and webMethods files can be up to 4GB. For streaming to work, you must set certain extended settings on every source and target Integration Server, and on the Integration Server that hosts Deployer. In Integration Server Administrator, go to the Settings > Extended > Edit Extended Settings page. Type the following server configuration parameters and values in the box. For complete information about these server configuration parameters, see the webMethods Integration Server Administrator’s Guide. watt.server.tspace.timeToLive=time watt.server.tspace.location=full_path_on_local_machine watt.server.tspace.max=maximum
	If your project contains BPM process models or Integration Server packages, set the following additional server configuration parameters: watt.server.SOAP.MTOMStreaming.enable=true watt.server.SOAP.MTOMStreaming.cachedFiles.location=directory_path watt.server.SOAP.MTOMStreaming.threshold=number_of_bytes Click Save Changes and restart the Integration Server. Note: Streaming is available only over HTTP. If your source or target environment uses HTTPS, you cannot choose to stream. This option is available for runtime-based deployment only.
Optimize UI Response	(Runtime-based deployment only) Click Yes to increase the Deployer GUI responsiveness for large projects. This setting causes Deployer to bypass the ping requests from the GUI that Deployer usually performs during the map and define dependency checks. The default setting is No.
Checkpoint Creation	(Runtime-based deployment only) To have Deployer automatically create a checkpoint for target servers before deploying, click Automatic. If you want to generate checkpoints when you choose, click Manual. Note: If deployment sets in a project include deletion sets, Deployer ignores these settings. Instead, Deployer automatically creates checkpoints for target servers.
Rollback on Error	(Runtime-based deployment only) To have Deployer automatically create checkpoints before deploying and roll back deployments if they fail, click Automatic. If you want to roll back deployments when you choose, click Manual. Note: If deployment sets in a project include deletion sets, Deployer ignores these settings. Instead, Deployer automatically rolls back the target servers.
Enable Concurrent Deployment	To set Deployer to deploy assets concurrently, click Yes (the default). If you want to deploy assets sequentially, click No. For more information about concurrent and sequential deployment, see Concurrent and Sequential Deployment.
DeployerService Timeout	The amount of time (in milliseconds) to wait before Deployer services time out waiting for a response. This setting overrides the watt.net.timeout and watt.server.SOAP.request.timeout server configuration properties for Deployer. Note: When using the Integration Server or BPM server ping operations, Deployer calls a service that returns cluster information. If the target Integration Server or BPM server is down, this service can take a long time to time out. To reduce the amount of time to wait, set the clusterServiceInvokeTimeout property in the WmDeployer/config/deployer.cnf file. The default value is 2000 milliseconds. Change this value according to your system’s requirements and reload the Deployer package for the changes to take effect.
Batch Size for Runtime Deployment	Sets the number of assets that Deployer deploys at one time for runtime-based deployment. Enter the maximum number of assets to build and deploy as a batch at one time. This limits the number of assets in each deployment to only the number indicated. The default value is 10. By batching deployments, you break the transportation of large assets into smaller batches, which decreases the memory utilization. If you set this property to 0, then Deployer does not limit the number of assets during build, checkpoint, rollback, and deploy operations.
Batch Size for Repository Deployment	Sets the number of assets that Deployer deploys at one time for repository-based deployment. Enter the maximum number of assets to build and deploy as a batch at one time. This limits the number of assets in each deployment to only the number indicated. The default value is 1. Note: If you are deploying BPM or Optimize assets, set this parameter to 0.
Maximum Plugin Objects Displayed	Sets the maximum number of assets Deployer displays in the tree for deployment and deletion sets. The default is 2500.