Synchronizing an existing application, whether in order to fix a problem or to reset an installation. This process is asynchronous, meaning the initial request will start the synchronize process and the initial response will show information about the application being synchronized. However, the synchronize process will proceed after the response is returned. You must continue checking the application status using the applicationGetStatus method until the process is complete.
Required Permissions: full
HTTP method: POST
Supported by Editions: Zend Server, Zend Server Cluster Manager
Request Parameters:
Parameter |
Type |
Required |
Description |
appId |
String |
Yes |
The application ID you would like to synchronize. |
servers |
Array |
No |
A List of server ID's. If defined, the action will be done only on the servers whose ID's are specified and which are currently members of the cluster. |
ignoreFailures |
Boolean |
No |
Ignore failures
during staging or activation if only some servers report failures.
If all servers report failures the operation will fail in any
case. |
Expected Response Code: 202 Accepted - For more information see Response Format.
Response Type: applicationsList
Possible Action Specific Error Codes:
HTTP Code |
Error Code |
Description |
404 |
noSuchApplication |
The provided application ID does not exist. |
Example: Request: POST /ZendServerManager/Api/applicationSynchronize Response: <?xml version="1.0" encoding="UTF-8"?> |
|
|
Important Note:
For Zend Server or Zend Server Cluster Manager on Mac or Linux, this action is also available via the command line using CLI Tools. For more information see CLI Tools.
|
|
Related Links: Deployment Methods |
|
|
|