Setting | Description |
Always | Tells Deployer to automatically check dependencies regularly as you modify the project and progress through the different phases of deployment. |
Reduced | Tells Deployer to automatically check dependencies when you create a project build and when you deploy. You can trigger additional dependency checking at different steps yourself. |
Manual | You will trigger dependency checking at different steps yourself. |
Setting | Description |
Large File Support | For Integration Server packages and webMethods files, indicates whether Deployer will stream from the source server to Deployer and from Deployer to the target server by default. Streaming is available only over HTTP. If your source or target environment uses HTTPS, you cannot choose to stream. 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. 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 server configuration parameters as well: watt.server.SOAP.MTOMStreaming.enable=true watt.server.SOAP.MTOMStreaming.cachedFiles.location=directory_path watt.server.SOAP.MTOMStreaming.threshold=number_of_bytes After saving the changes, you must restart Integration Server. |
Optimize UI Response | Bypasses the ping requests from the GUI that Deployer usually performs during the map and define dependency checks. The default setting is No. If set to Yes, the responsiveness of the Deployer GUI for large projects gets better. |
Checkpoint Creation | 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 | 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. |
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. |
Asset | Description | Value |
Triggers | Allow all running trigger operations to complete, then suspend all trigger execution and document retrieval on the target Integration Servers. Note: If you choose All, Deployer suspends execution and document retrieval for ALL triggers on the target Integration Servers, not just for the triggers that you include in the project. | All |
Do not suspend triggers. | None | |
Suspend individual triggers. You choose the triggers to suspend when you set package properties (see
Setting Package Properties). | Selected | |
Ports | Whether to disable ports on the target Integration Servers that match ports you are trying to deploy. | |
Scheduled Tasks | Whether to prevent scheduled tasks on the target Integration Servers that match scheduled tasks you are trying to deploy from running. Note: Tasks that are already running at deployment time are not affected by deployment. | |
Adapters | Do not suspend adapter listeners or polling notifications. | None |
Suspend individual adapter listeners and polling notifications. You choose the notifications to suspend when you set package properties (see
Setting Package Properties). | Selected |
Asset | Indicate whether Deployer should | Value |
TN Rules | Replace the entire rule list. | Replace All |
Overwrite existing rules and deploy new rules into the rule set. | Merge | |
ACL Maps | Deploy the mapping of ACLs to services for any services you choose to deploy. Deploy ACL maps if you want to assign the same ACLs to the deployed services on the target Integration Server that you assigned to the source services on the source Integration Servers. | |
Other Non-Package Assets | Overwrite existing assets. This option applies to all assets except the following: Trading Networks processing rules (see the previous step). Integration Server ACL maps (see ACL Maps). Integration Server packages. You specify the overwrite option for Integration Server packages on a package-by-package basis, as described in
Setting Package Properties. | |
Scheduled Tasks By | This property can be set to either Service Name or ID. If this property is set to Service Name, and if a scheduled task with the same service name already exists, Deployer overwrites it with the one being deployed. If this property is set to ID, then based on the task ID which is present on the target, Deployer either overwrites the task if the source and target task IDs are same, or creates a new one. |
Asset | Indicate whether Deployer should |
Ports | Activate newly deployed ports. Note: If you choose to activate ports, and one of the ports you deploy uses the same port number as an existing port on a target Integration Server, Deployer will display a message to that effect and will not activate the port. |
Scheduled Tasks | Activate newly deployed scheduled tasks. |
Adapters | Activate newly deployed adapter connections, notifications, and listeners. Note: If you choose to not activate, the deployed adapter connections, notifications, and listeners will be in the same state they are in on the source server. |
For this option... | Indicate whether Deployer should... |
Compile Java Services | Compile the package during deployment. When Integration Server packages contain Java sources and are deployed using runtime-based deployment, the Java sources will get compiled on the target Integration Server if the Compile Java Services property is set to Yes. |
Reload Packages | If the Reload Packages option is set to Yes, deployed packages get reloaded after the package is activated. If the property is set to No, packages will not be reloaded after deployment. The default value is No. |