Configuring Server Properties – Deployment and Backup
See also: Server Administration Application Home Page, Deployment Overview
Click the Save button at the bottom of the page to save the properties. These properties are saved to file deploy.properties in the ebaseConf folder of the web application e.g. userdata/apps/<webappname>/ebaseConf/deploy.properties.
The icon shown to the left of a property indicates that the server must be restarted before a property change is activated. Changes to all other properties are effective immediately.
Click More Info.. at the right-hand side of each property to display help for that property.
Label |
Property Name |
Requires Restart |
Description |
Deployment.location |
No |
The folder where all files and logs relating to inbound deployments are stored. See Deployment Overview for more details. |
|
Deployment.holdOnServer |
No |
If checked, all inbound deployments are held on the server as they arrive and are not installed automatically. These deployments are then shown as pending in the Deployments page of the Server Administration Application and must be manually installed. If unchecked, inbound deployments are installed and activated as they are received. See Deployment Overview for more details. |
|
Deployment.token |
No |
This is an optional security token which can provide additional security for deployment. If specified, all users deploying to this server must also specify this token using the designer deployment security credentials. |
Label |
Property Name |
Requires Restart |
Description |
Backup.location |
No |
The folder where backups are stored. |