Installs (deploys) WAR or EAR in a WAS cell.'deploy' target triggers compilation and packaging of the applicatoin, so that EAR/WAR file will be created for you automatically.
Alternatively, you can also use 'deploy.xar' target which does not depend on compile and package targets. In this case you must explicitly specify EAR/WAR file(s) to deploy. This can be done using the following properties: 'xar.file', 'xar.files', 'xar.dir'/'xar.include.pattern', 'xar.file.path.id'. These properties are mutually exclusive.
| Name | Desciption | Required |
|---|---|---|
| xar.file | Path to EAR or WAR file that we want to deploy. The path can be relative to the current OS directory.Type: Existing file | No |
| xar.files | Comma-delimited list of EAR or WAR files to deploy. | No |
| xar.dir | Root directory of Ant fileset defining what files to deploy. This property is used in conjunction with 'xar.include.pattern'.Type: Existing directory | No |
| xar.include.pattern | Ant file pattern specifying what files to deploy, e.g., '**/*.war'. The pattern is relative to 'xar.dir' property. You must provide 'xar.dir' if you provided the pattern. | No |
| xar.file.path.id | ID of an Ant path structure defined somewhere in a calling Ant script. The path defines what files to deploy. | No |
| was.appname | Name of enterprise application. File name is used if not provided. | No |
| was.deployment.target | Comma-delimited list of server(s) and/or clusters to deploy to.Not required if there is only one cluster in a cell. | No |
| webapp.context.root | Context root for Web applications (WAR files only). | No |
| installedApps.dir | Directory where to install binaries on the target nodes. | No |
| undeploy.before.deployment | Automatically uninstall the application before deployment. Note: this is much more reliable that update mode. Do not turn off unless you're absolutely sure. Type: bool( true, false ) | No; defaults to 'true' |
| was.classloader.mode | Classloader order for Web applications AND jar files inside the EAR. Type: enum( PARENT_LAST, PARENT_FIRST ) | No; defaults to 'PARENT_LAST' |
| was.classloader.policy | Give each WAR its own classloader or use the same one for all. Type: enum( MULTIPLE, SINGLE ) | No |
| was.reload.enabled | Reload classes when application files are updated. Type: bool( true, false ) | No; defaults to 'false' |
| was.reload.interval | Polling interval for updated application classes. Type: Integer | No; defaults to '2' |
| was.virtual.host.name | Virtual host for Web modules. | No; defaults to 'default_host' |
| was.target.war.to.ihs | Automatically target WAR modules to all Web servers in the cell. Type: bool( true, false ) | No; defaults to 'true' |
| was.deploy.ws | Set to True if you want to compile JAX-RPC services during deployment. This is not needed for JAX-WS. Type: bool( true, false ) | No; defaults to 'false' |
| was.start.app | Automatically start the application after deployment. Requires at least one running target server. Type: bool( true, false ) | No; defaults to 'true' |
| was.ensure.all.servers.up | Make sure that ALL servers in the target cluster are up. By default only one running sever is sufficient. Type: bool( true, false ) | No; defaults to 'false' |
| was.free.memory.limit | If free memory falls under this limit (set in Kb), the server is considered 'unhealthy',and deployment or server check will fail. | No; defaults to '1024' |
| was.bounce.servers | Bounce ALL servers an application or a group of applications is deployed to after deployment. First, applications are fully deployed and then servers are bounced. Note that this property can't be set at the application level. Type: bool( true, false ) | No; defaults to 'false' |