Deploying An Application


To deploy an application, you should have already performed the following tasks:


To deploy an application, follow this process:

  1. Access the application from the CCM UI and click Applications.

  2. Search for the required application in the Applications page. The following screenshot shows an example.

  3. To deploy an application, left click on it. This brings up Page 1 of the Deploy form, as shown in the following screenshot.

    In the General Settings section, you must give the deployment a name. You can also optionally select a deployment environment, policy or policies, timezone, tags, terminate/suspend protection, and add metadata as required. The deployment environment boards display the name, description, and list of clouds available in this environment.

    Tags do not influence the application of policies and users can enter custom tags in the deploy form in addition to selecting from the pre-populated tags for both the application profile and the deployment environment. Additionally, users can delete tags if they are not locked.

    While the Aging, Suspension, and Security policies dropdown options are populated based on the deployment environment, the Scaling policies dropdown options are populated based on the application profile. See Policies for additional context.

    The tags are populated based on both the deployment environment and the application profile. You can also add on custom tags for the entire deployment and for each tier in the deploy form at deploy time. See System Tags for additional context.

  4. Scroll down to the enter any global parameters, if defined in the Application Profile, and any per tier settings. The following screenshot shows an example.

    You can optionally provide per-tier settings for each tier in your application. Keep scrolling down to see all tiers. Some tiers will have settings for other parameters based on the Application Profile requirements.

  1. Click Next to go to Page 2 of the Deploy form and select the cloud provider and then the cloud account, as shown in the following screenshot.

Cloud-Specific Configuration

This section provides details on configuring the Cloud Settings section and the Network Settings section for each cloud.

If you do not see the required instance type listed in this section, be sure to add the instance type first. See Manage Instance Types for additional context.

Once you configure the cloud settings, you have two control options to identify if the Cloud Settings should be:

  • Visible (Default) to your end users by toggling the control switch.

  • Configurable (Default) by your end users by toggling the control switch.

Toggle the required settings as required for your deployment environment defaults.


One-Click Deployment

When you submit the application for deployment, CloudCenter reads the application profile and orchestrates the following tasks with one click:

During each orchestration stage, CloudCenter sends status messages to the CCM for users to track the application deployment phase and status.

After the application is deployed in the cloud, it is listed  click Access<app name> to open the IP address where the application is hosted.

Depending on the context path of the application in the application server, you may need to specify the full path in the browser (for example, http(s)://<IP address>/app-context-path).

Configure the Launch URL field with this path when creating the application profile.

Once the application is running, the CloudCenter application provides the ability to securely access cloud VMs using SSH or VNC to directly launch the application from any browser. You can use this method to troubleshoot or run one-off custom commands or scripts.