Updating, Editing and Maintaining Containers

Save to PDF

Applies to: Cloudhouse Containers, Container Editor

13/06/2019 Cliff Hobbs

Updating a Container to use the latest Cloudhouse components

The Cloudhouse Container Editor can be used to create a new version of a Container, e.g. Container.1 with the latest versions of the following Container components and their supporting DLLs.

Note

Automated rollback is provided for AppAccelerator components only. If you need to rollback to previous versions of one or more of the above executables, then please use the original Container folder, e.g. Container which remains unchanged.

To update a Container to use the latest Cloudhouse components:

  1. On the computer where the Auto Packager is currently installed, launch the Auto Packager so that it can get the latest versions of the Auto Packager, Container Editor, and Cloudhouse Container components.

Note

If the computer on which you have installed the Auto Packager does not have Internet access, see Installing/Updating the Auto Packager on a Computer without Internet Access for details of how to update the Auto Packager. 

  1. Close the Auto Packager.
  2. Navigate to the common application data folder containing the Container Editor:
    • On Windows 7 (or later), navigate to the %ProgramData%\Cloudhouse\packager\Tools\ContainerEditor folder.
    • On Windows XP, navigate to the %ALLUSERSPROFILE%\Cloudhouse\packager\Tools\ContainerEditor folder.
  1. Double-click Cloudhouse.Package.Editor.exe to launch the Container Editor.
  2. With the Home tab selected (which it should be by default), click Open an existing Container.
  3. Browse to the Container you want to update.
  4. Click the Details tab.
  5. Select Update.
  6. Select the version you want to update the Container to, and select Change to this version.
  7. To rollback to the original version of AppAccelerator components, select Change version.
  8. Close the Container Editor.

Adding a Reporting Token to the Container

To add a Reporting Token to a Container:

  1. Navigate to the common application data folder containing the Container Editor:
    • On Windows 7 (or later), navigate to the %ProgramData%\Cloudhouse\packager\Tools\ContainerEditor folder.
    • On Windows XP, navigate to the %ALLUSERSPROFILE%\Cloudhouse\packager\Tools\ContainerEditor folder.
  2. Double-click Cloudhouse.Package.Editor.exe to launch the Container Editor.
  3. Ensure you have updated to a version of the Container that supports HTTPS Usage Reporting (the version must be 4.5.249.480, or later).
  4. With the Home tab selected (which it should be by default), click Open an existing Container.
  5. Browse to the Container you want to update.
  6. Click the Details tab.
  7. Select + in the Usage Reporting field, then browse to the token file.
  8. Select Save to apply the changes before closing the Container Editor.

Tip

Ensure the CHMetadata.json contains the following entries (add them if they are not present):

"AuthUrl": "https://auth.cloudhouse.com/oauth/token",
"UsageReportingUrl": "https://containers.cloudhouse.com/api/UsageEvents"

Upgrading Applications in Containers

To apply new versions, updates, hotfixes or service packs to an application use the Container Editor, watch this video to find out how. The Editor supports reboots, enabling you to include an application update that requires a reboot during install.

Warning

The Container Editor should only be used to update applications, file and registry redirections on the same architecture the original container was created on. For example, if the Container was created on an x86 computer, then the Container Editor must update the Container on an x86 computer.

To upgrade applications in a Container:

  1. Navigate to the common application data folder containing the Container Editor:
    • On Windows 7 (or later), navigate to the %ProgramData%\Cloudhouse\packager\Tools\ContainerEditor folder.
    • On Windows XP, navigate to the %ALLUSERSPROFILE%\Cloudhouse\packager\Tools\ContainerEditor folder.
  2. Double-click Cloudhouse.Package.Editor.exe to launch the Container Editor.
  3. With the Home tab selected (which it should be by default), click Open an existing Container.
  4. Browse to the Container you want to update.
  5. Click the Details tab.
  6. Select Update.
  7. When prompted, click Next to install the application patch, or update to the latest version.
  8. Click Next to update the Container.

The Files tab allows you to review the files and folders added to or removed from, the Container. All changes are displayed by default. The following filters can be turned on/off:

  • New -  Shows all files added to the Container.
  • Modified - Shows all files that changed by the update.
  • Deleted - Shows all files removed during the application update.

In the same way, the Registry tab allows you to review the registry keys and values added to or removed from, the Container. All changes are displayed by default. The following filters can be turned on/off:

  • New - Shows all registry entries added to the Container during the update.
  • Modified - Shows all registry entries that changed during the update.
  • Deleted - Shows all registry entries removed during the application update.
  1. Click Save to save the Container.

Note

If you close the Container Editor without saving your changes, any changes will be lost.

Programs and Executables

To modify the Programs started by a Container's run conditions: 

  1. Open the Cloudhouse Container folder in Windows Explorer.
  2. Open Programs.xml with an XML text editor.
  3. Each <Program> section represents an executable within the package.

Run Conditions

Run Conditions specify the commands that will be executed, either by shortcuts or by other user actions.

  • Initial - The default action and will run if no other Run Conditions have been specified.
  • Always -  Will run, even when other Run Conditions have been specified.
  • Custom Run Condition - Will only run when specified by the run Tool. For example Run1, RunAfter, RunBefore

If the Programs.xml file contains Run Conditions with the same name, then Cloudhouse.Container.Run.exe will execute both commands.

Multiple Run Conditions can be specified, for example:

Cloudhouse.Container.Run.exe /runconditions RunBefore,Run1,RunAfter

Shortcuts

To modify the Shortcuts installed by a Container:

  1. Open the Cloudhouse Container folder in Windows Explorer.
  2. Open Shortcuts.xml with an XML text editor.
  3. Each <Shortcut> section represents a Shortcut that will be created during deployment. The required /RunConditions can be found in Programs.xml.

File Type Associations

To modify the File Type Associations installed by a Container:

  1. Open the Cloudhouse Container folder in Windows Explorer.
  2. Open FileAssociations.xml with an XML text editor.

Re-directions

To modify the file and registry re-directions used by the Container:

  1. Open the Cloudhouse Container folder in Windows Explorer.
  2. Open Redirections.xmlwith an XML text editor and use:
    • ExactMatch to redirect from one file to another
    • FolderMatch to redirect an entire folder from one location to another
    • KeyMatch to redirect Registry Key/Values

Add/ Remove Programs Entries

Containers register the applications they deploy with Add/Remove Programs in Windows. Default values are provided which can be changed by editing the CHMetadata.json file to reflect the desired names. For example, the name of the company who created the Container could be specified as the Vendor or the name of the publisher of the software that is included in the Container.

To change the name/vendor for an application:

  1. Open the Cloudhouse Container folder in Windows Explorer.
  2. Open CHMetadata.json with an XML text editor.
  3. Set the desired Name, Vendor, etc. for the application. For example:
{
    "PackageId": "IE_Java_Demo_4864",
    "IsTelemetryEnabled": "true",
    "TelemetryApiUrl": "https://qatelemetry.cloudhouse.com/telemetry",
    "Icon": "icon for container exe",
    "Name": "Name of the Application that appears in the Add/Remove details page",
    "Publisher": "Name of the Publisher as it should appear in Add/Remove Programs",
    "Version": "Version of the entry that appears in Add/Remove Programs"
}

Adding a Pre or Post Deployment Task

Containers can be configured with tasks that run before and after the Container is deployed.

Install

The Container is copied to the deployment directory first, and then each program under the <Programs> element will be executed. This allows MSIs, driver files or other pre-requisites to be deployed from the Container. 

Uninstall

Each program under the <Programs> element will be executed before the Container is uninstalled from the computer.

Programs will be executed ordered by the value configured for the Order attribute. Without the Order attribute, programs are executed in the order they appear in the file.

To modify the install/uninstall tasks for the Container:

  1. Open the Cloudhouse Container folder in Windows Explorer.
  2. Open DeploymentScript.xml with an XML text editor (if this file does not exist, create it). The contents should be as shown below if the file has not been edited:
<Deployment>
    <Install>
    <!--
      <Programs>
        <Program Order="0">
           <ProcessWindowStyle>Normal</ProcessWindowStyle>
           <Path>Program2</Path>
           <Args>arg2</Args>
           <WaitCondition TimeoutInSeconds="0">None</WaitCondition>
        </Program>
      </Programs>-->
    </Install>
    <Uninstall>
      <!--
      <Programs>
        <Program Order="0">
          <ProcessWindowStyle>Normal</ProcessWindowStyle>
          <Path>Program2</Path>
          <Args>arg2</Args>
          <WaitCondition TimeoutInSeconds="0">None</WaitCondition>
        </Program>
      </Programs>-->
    </Uninstall>
</Deployment>
  1. Un-comment the relevant entries of the Install or Uninstall tag as required.
  2. Save the DeploymentScript.xml file.
Source:
Was this article helpful?

Table of Contents

    Can't find what you're looking for?

    Contact Support