Application Pack Deployment

The Application Pack Deployment tool enables you to automatically install and upgrade Application Pack plug-ins on multiple Agents, from a single point of access, and with no Agent downtime for Application Pack 9.0.18.200 and higher. Application Pack jobs that are executing during the upgrade continue as normal, to completion. Jobs that are submitted after the upgrade completes are processed by the new plug-in version, and the previous version installation files are deleted after a predefined set of time. This process eliminates the need to designate a maintenance period on every Agent and coordinate between application owners and Control-M Administrators.

From the CCM, you can copy Application Pack installation packages to multiple Agents and install or upgrade Application Pack on Agents 9.0.18 and higher, on UNIX and Windows.

For more information, see Control-M Application Pack Installation.

The following procedures describe how to deploy and roll back Application Pack on one or more Agents:

Deploying Application Pack

This procedure describes how to transfer Application Pack installation packages to existing Agents and install or upgrade Application Pack on UNIX or Windows.

You cannot simultaneously upgrade Application Pack on multiple Agents on the same computer.

Before You Begin

  • Verify that you have Full access to the Configuration and Operation categories in Admin Management in the Configuration domain, as described in Role Authorizations.

  • (Windows only) If the Control-M/Agent Windows service is set to Log on as > This account, you must upgrade with this user account.

  • You cannot install a lower version of Application Pack on Control-M/Agent 9.0.21 and higher.

  • Control-M/EM Server and Control-M/Server must be the same version.

  • If you use IBM Db2 Connect for Control-M for Databases, verify that a license file is properly installed, as described in Db2 License Files.

  • Control-M for Hadoop must be installed on an Agent that is on the Edge node of the Hadoop cluster.

Begin

  1. From the Manage tab in the CCM, select Deployment.

    The Deployment window appears.

  2. Click New Activity, click Application Pack, and then click Install/Upgrade.

    The Application Pack Upgrade window appears.

  3. Do the following:

    1. In the Activity Name field, type a new name for this deployment activity.

    2. (Optional) In the Description field, describe the purpose of this activity.

    3. (Optional) In the E-Mail Notification field, type one or more email addresses where notifications about this activity are sent.

      You must also define the email server parameters, as described in SMTP Parameters.

  4. Select one of the following actions:

    • Send Application Pack to Control-M/Agent(s): Transfers the Application Pack installation package to specific Agents. After the package is transferred, you can manually start the upgrade process at any time from the Agent Deployment window or upgrade with the CLI, as described in ccmcli.

    • Send and Install Application Pack to Control-M/Agent(s): Transfers the Application Pack installation package to specific Agents and starts the upgrade process.

    • The Application Pack installation package is deleted after is successfully upgrades. If the upgrade fails, the installation package remains on the Agent until the next successful upgrade.

    • The Application Pack installation package remains on the Control-M/Server computer for 30 days. To change this limit, redefine the Control-M/Server system parameter AD_RETAIN_PACKAGES, as described in Deployment Parameters.

  5. Click Next.

  6. Select the Agents to deploy Application Pack.

    (Windows only) If you select an Agent that is set to Logon as User, you must define the Run As User for each Agent, as described in Adding a Run as User.

  7. In the Set Java Home Directory Location for the Selected Agents field, type the path that points to the external Java installation for all selected Agents.

    If the path is incorrect and the deploy fails, you can update the path in the Properties pane.

    You can only define one Java home directory for this deployment activity. If you need to deploy Application Pack to platforms with different Java paths, you must create a separate deployment activity for each platform. To view the OS type for each Agent, see the Operating System column in the Components table. For more information, see Control-M External Java Installation.

  8. Click Transfer or Install, depending on the action you selected.

    The transfer process starts and progress messages appear in the right pane of the deployment activity.

    To view and troubleshoot the internal upgrade stages, click Log from the Agent Deployment window.

    If you selected Transfer, you can upgrade or install Application Pack any time after the transfer completes. A job executes on the Agents to verify that the upgrades succeeded.

Rolling Back Application Pack

This procedure describes how to roll back the Application Pack upgrade from multiple Agents. You can only roll back the Application Pack if it was upgraded with the Deployment tool.

Before You Begin

  • Verify that all jobs on the selected Agents have ended. Jobs that are still running during the rollback might fail.

  • Verify that you have Full access to the Configuration and Operation categories in Admin Management in the Configuration domain, as described in Role Authorizations.

  • (Windows only) If the Control-M/Agent Windows service is set to Log on as > This account, you must upgrade with this user account.

Begin

  1. From the Manage tab in the CCM, select Deployment.

    The Deployment window appears.

  2. Click New Activity, click Application Pack, and then click Rollback.

    The Application Pack Rollback window appears.

  3. Do the following:

    1. In the Activity Name field, type a new name for this deployment activity.

    2. (Optional) In the Description field, describe the purpose of this activity.

    3. (Optional) In the E-Mail Notification field, type one or more email addresses where notifications about this activity are sent.

      You must also define the email server parameters, as described in SMTP Parameters.

  4. Click Next.

  5. Select the Agents with Application Pack to roll back.

  6. Click Rollback.

    The rollback process begins immediately and Application Pack rolls back to its previous version. To view and troubleshoot the internal stages of the rollback, click Log from the Deployment window.