Configuring Quick publish to call EAR Updater for non-federated environments
If you have a non-federated environment, Quick Publish does not call the EAR Updater. In a federated environment, Quick Publish calls and uses the EAR Updater to publish your changed files to your production server. You can configure Quick Publish to call the EAR Updater in a non-federated environment to help copy your changed files to your production server if the EAR Updater is configured to use FTP prototype.
For more information about configuring FTP, see Configuring FTP or file system copy for extracting managed assets.
About this task
forceEARUpdate
option
to true in the wc-resource-containers.xml file.
You can set the following configuration option to ensure that Quick
Publish calls the EAR Updater. Quick Publish can use the EAR updater
to copy changed files with FTP to your production environment if the
EAR Updater is configured to use FTP. - forceEARUpdate
- Determines whether Quick Publish calls the EAR Updater in a non-federated
environment.
false
(default) – Quick Publish does not call the EAR Updater. When set to false, you must manually copy your changed files to your production environment.true
– Quick Publish calls the EAR Updater in a non-federated environment. The EAR Updater can be used by Quick Publish to copy your changed files to your production environment.