Deploying and troubleshooting applications

ReferenceAutomationTroubleshooting

This example shows how to deploy the application multiple times with different runtime conditions.

First run

In the applications list, clicking and selecting New Run opens the dialog box where you can set the runtime settings.

  • In the Select Process drop-down, select the process where deployment starts.

  • In the Select Environment field, select the environment.

  • You can select a snapshot in the Select a Snapshot field if you have one or more.

  • For the first run, all artifacts are deployed.

  • Smart Deploy and Stage Artifacts are enabled.

Click OK to start the application run.

The Application Deployments list shows the progress of the application run:

  • The blue steps are running (in progress).

  • The green steps were completed successfully.

  • The red steps failed.

  • The gray steps are skipped.

Select a deployment to open the details page where you can begin the troubleshoot the step.

Subsequent runs

After the first application run, you can deploy the Run process to another environment with other deployment options.

Based on the last run

Select Run and then Last Run opens the dialog box where you can set the runtime settings. It displays the runtime settings from the previous. You can deploy the application using the same settings as the previous run or you can modify one or more them for the current run.

Based on schedules

Select Run and then Schedule opens the list of schedules for the application. If there are no schedules, click There are no Run Schedules to add one.

  • Select Create new to create a new schedule, and then enter the schedule details .

  • Select from Previous Runs to create a schedule based on a previous application run.

A list of the last five application runs appears. Select an application run, and then enter the schedule details.

In the Run Schedule Details dialog box, enter the schedule details and click Next when finished.

The dialog box where you can set the runtime settings appears. You can also modify the runtime settings at this time. Click OK. A configuration message is displayed with the deployment run time.

When you view the list of schedules for the application again, the schedule that you created appears in the list.

Runtime settings

  • Clicking opens the list of artifacts and containers that can be deployed in the application process. Artifacts are grouped by application tier. You can enable or disable an artifact within a tier or the entire tier itself as part of a deployment.

*If you want to only deploy the DB artifact (cleanup.sql), click in the "1 App Server" column to deselect (disable the selection of) the Config and Heatclinic components (based on the env.sh and mycompany.war artifacts), and click OK.

+

The Artifacts field now looks like this for a partial run:

With microservices and containers, you can enable or disable a service. You cannot, however, disable an individual container within a service.

Partial deploy with specific artifact versions and with smart deploy and artifact staging are enabled:

I* n the list of artifacts to be deployed in the application process, click in the 2 DB row to deselect the Cleanup DB component (based on the cleanup.sql ` artifact), select the Latest version of the `mycompany.war artifact, and click OK.

+

+ The Artifacts field now looks like this for the partial run:

+

  • Snapshot with partial deploy and with smart deploy and artifact staging are enabled. In the Select a Snapshot field, click the down arrow and select the Upgrade_latestMC snapshot.

  • In the list of artifacts to be deployed in the application process, click in the "1 Config" row to deselect (disable the selection of) the Config component (based on the env.sh artifact) and click OK.

  • The Select a Snapshot and Artifacts fields now look like this for the partial run:

Viewing the real-time progress of deployments

This example shows the job details for a specific step. Clicking in the cleanup db step opens the Job Details page:

This example shows that the rollback step has not run yet:

Clicking in the rollback step opens the Job Details page, showing that the status is Waiting for Precondition . This step will not run until the precondition is met.

Troubleshooting deployments

This example shows that the "start server" step was Completed with Errors .

Clicking in the start server step opens the Job Details page.

Clicking in the Diagnostics tab can provide more information about the errors.