Search Engine: Elastic

Article ID: 116201, created on May 30, 2013, last review on Sep 14, 2015

  • Applies to:
  • Business Automation


When configuring the newly installed PBA update, it is necessary to install new versions of custom plug-ins' RPM packages.

Otherwise, if custom plug-ins are not installed during the PBA update, they will not work after the PBA was updated - it will be impossible to start the corresponding PBA container, some screens in the PBA Control Panel may display error messages if they (screens) depend on the plug-in.

During PBA update custom plugins are getting un-installed automatically. Installation script announces this action as follows:

Jan 11 2012 00:45:37 [:25785] NOTICE: Below the list or RPMs which will be removed addittionaly:
Jan 11 2012 00:45:37 [:25785] NOTICE:

So, it is necessary to install new versions of custom plug-ins' RPM packages to ensure correct PBA functioning after update.


  1. Login as root to the PBA Application server.

  2. Copy the new RPM packages built with the new version of SDK.

  3. Update the RPM packages using the following command:

    # rpm -Uvh <PLUGIN_RPM>

    where <PLUGIN_RPM> is the path to the RPM file.

  4. Run the PBA configuration script:

    # /usr/local/bm/tools/

caea8340e2d186a540518d08602aa065 198398b282069eaf2d94a6af87dcb3ff e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF