Any changes to a configuration in iWD Manager are not activated automatically. The Deploy functionality performs this task by distributing department and process configuration to iWD services.
Note: Any changes made to Services will also be deployed.
The following attributes and actions are available in the Deploy function:
Undeployed Changes/ Undeployed Changes Details |
Detailed information about activities that are performed in iWD Manager since the last deployment. For more details, see History. |
Comments |
Deployment comments. They are displayed as version comments in the Change History. |
Deploy |
Deploys the configuration. Depending on the configuration’s complexity and runtime environment characteristics, this action can take several seconds. |
Undeploy |
Stops all of the services of a solution, and undeploys the configuration from all available runtime nodes. If any runtime node that is defined in the solution is not available, iWD Manager will display a warning message. All configured services are deactivated. Deployed configuration files are removed and the runtime node reloads the empty configuration. |
Schedule Deployment |
Allows deployment to be performed on a specific date/hour. This allows you to deploy changes during a quiet period, when there is nothing happening in the system. Note: If you have more than one iWD Manager instance connected to a single iWD configuration database, the iwd.host parameter in the iwd.properties file must be unique for every host on which iWD Manager is running. The iwd.properties file can be found in the web application server’s webapps folder for iWD Manager. For example, for Tomcat this might be <TomcatDirectory>\webapps\iwd_manager\WEB-INF\classes |