Search Engine: Elastic

Article ID: 111323, created on May 24, 2011, last review on May 11, 2017

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1
  • Operations Automation 6.0
  • Operations Automation 5.5

Release Notes

Operations Automation updates installer is a utility for downloading and installing updates and hotfixes.

It is invoked via the command line on the management node.


  • Linux:

    # /usr/local/pem/bin/pa_updates_installer COMMAND [options]
  • Windows (5.5 version):

    C:\> "C:\Program Files (x86)\SWsoft\PEM\bin\pa_updates_installer.exe" COMMAND [options]
  • Windows (6.0 version):

    C:\>python.exe "C:\Program Files (x86)\SWsoft\PEM\bin\pa_updates_installer" COMMAND [options]

    Note that Python version 2.7 must be used.

This command specifies the utility's working mode:

  1. Check for product updates (default):

    # pa_updates_installer

    This will check for updates and hotfixes for the product installed on the system.

  2. Download product updates:

    # pa_updates_installer --download

    This will download all updates and hotfixes available for the installed product(s). If an update already has been downloaded, the utility will check its checksum. If it does not match, the existing file will be removed and the update will be downloaded again. Otherwise, it will skip the update download.

  3. Run prechecks:

    # pa_updates_installer --precheck

    This will download prechecks for available product updates and run them. Prechecks do not modify the system and are run to discover issues which could block product update installation. It is recommended you run this command several days before actually installing product updates. Note: This command is only available in versions from Operations Automation 5.5.

  4. Install product updates:

    # pa_updates_installer --install

    This will install all the updates and hotfixes available for the installed product(s).

    If required, the updates will be downloaded as they would be when using the "download" command. Also, this command implies running prechecks.

    Important! When installing a hotfix that has a billing component, you may see the following warning:

        [WARNING] Host #2 ( is one of Billing hosts and have to be updated later, with launch "pa_updates_installer --update-billing"   

    If you faced this warning then run the command pa_updates_installer --update-billing right after pa_updates_installer --install finishes. Also note that Billing will restart when you run that command.

Additional Options The tool also has some additional options and configuration files that you can use to configure its behavior.

--version=serial number of update

This option can limit product updates which will be considered by pa_updates_installer. For example, only install Operations Automation 5.5.2 when there is already Operations Automation 5.5.3 by specifying --version=2.


Specifies the base URL of the updates repository. The default is ""


Specifies the log file location.

The default location is:

  • Windows:

    C:\Program Files (x86)\SWsoft\PEM\var\log\pa_updates_installer\pa_updates_installer.log

  • Linux:


Use of Privacy Proxy

pa_updates_installer requires access to the internet to download product updates. In most cases, there is no direct access to the internet from the Operations Automation management node. To overcome this limitation, the Privacy Proxy service must be deployed in a system. The latter will be automatically discovered by pa_updates_installer.

  • Known issues

Many parameters that were adjusted manually, such as coordinator-environment, might be overwritten in

/usr/local/pem/jboss-eap-6.2/standalone/configuration/standalone-full.xml file during updates installation.

  • Please make sure to create a backup of this file before installing updates.

  • After updates installation is completed, compare the file to the saved copy, return the required values (that were overwritten) and restart pem:

    service pem stop
    service pau restart
    service pem start

5b048d9bddf8048a00aba7e0bdadef37 caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d 8c199f0ee4305da1a577740620df4a51 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF