8.4.4. Redeploy an Application to a Standalone Server Instance with the Deployment Scanner
This task shows a method for redeploying applications to a standalone server instance that have been deployed with the deployment scanner. As indicated in the Section 8.1, “About Application Deployment” topic, this method is retained for the convenience of developers, where the Management Console and Management CLI methods are recommended for application management under production environments.
Procedure 8.9. Task
Redeploy the applicationThere are three possible methods to redeploy an application deployed with the deployment scanner. These methods trigger the deployment scanner to initiate a deployment cycle, and can be chosen to suit personal preference.
Redeploy by altering the marker fileTrigger the deployment scanner redeployment by altering the marker file's access and modification timestamp. In the following Linux example, a Unix
touchcommand is used.
Example 8.3. Redeploy with the Unix
The deployment scanner detects a change in the marker file and redeploys the application. A new
.deployedfile marker replaces the previous.
Redeploy by creating a new
.dodeploymarker fileTrigger the deployment scanner redeployment by creating a new
.dodeploymarker file. Refer to the manual deployment instructions in Section 8.4.2, “Deploy an Application to a Standalone Server Instance with the Deployment Scanner”.
Redeploy by deleting the marker fileAs described in Section 8.4.5, “Reference for Deployment Scanner Marker Files”, deleting a deployed application's
.deployedmarker file will trigger an undeployment and create an
.undeployedmarker. Deleting the undeployment marker will trigger the deployment cycle again. Refer to Section 8.4.3, “Undeploy an Application to a Standalone Server Instance with the Deployment Scanner” for further information.
The application file is redeployed.