Search Engine: Elastic

Article ID: 118363, created on Nov 1, 2013, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 5.4
  • Business Automation 5.4


The article describes steps to perform after the PBA for Linux migration from RHEL 4/CentOS 4 to RHEL 6/CentOS 6.

Refer to the main Knowledgebase article #116940 PBA for Linux Migration to RHEL6/CentOS6: Procedure, Known Issues, and Limitations.

PBA for Linux Post Migration

  1. For non-PVC based installation switch IP addresses of the target PBA servers to original ones.

    Follow the instruction in the PBA documentation:

  2. Get the list of PBA RPM packages on the new servers and compare it with the list of packages on source servers prepared during the pre-migration procedure to make sure that all required components are installed, use the commend below to get it:

    # rpm -qa | grep '^bm'

    Make sure all custom plugins are installed on the new PBA Application server.

  3. Check iptables rules on the new PBA servers, compare them with original rules saved during the pre-migration procedure and adjust if necessary.

  4. Check and restore if necessary external Internet connection from within new PBA servers.

    Refer to the Parallels Knowledgebase article #116081 for more details.

  5. Re-install all available hotfixes for the current version using the /usr/local/bm/tools/ script on the PBA Application server.

  6. If source PBA containers use bridged network mode, IP addresses should be configured manually on the target servers after migration.

  7. Check the mail relay host name in the /usr/local/bm/conf/AMAIL-users.db file - if localhost ( is used, copy sendmail configuration file /etc/mail/ from the source PBA Application server.

  8. Verify that IP addresses of all POA UI (User Interface) and Branding servers are configured in the /usr/local/bm/conf/ip_access.db file.

  9. If some external (non PBA) host(s) had access to the PBA database before migration then configure such access in the /var/lib/pgsql/data/pg_hba.conf file on the new PBA Database server.

  10. Configure custom cron jobs saved during the pre-migration procedure.

  11. If the PBA system had custom script to backup database and save backup to another host configured consider to restore it manually after the migration. SSH auth keys may have to be restored as well.

  12. Migration script will not move custom PHP files from the /usr/local/bm/templatestore/webroot/phpcode folder on the source Online Store server, it should be done manually if necessary.

  13. If redirect from external systems is defined in the /etc/xinetd.d/xmlrpc on the source PBA Application server, it should be configured on destination server as well.

  14. Disable old PBA servers:

    PVC-based installation:

    vzctl set CT_ID --save --onboot no --disable yes

    Parallels Virtual Machine based installation:

    prlctl set VMNAME --autostart off 

    Replace CT_ID and VMNAME in the commands above with actual ID of container or Virtual Machine name, repeat the commands for all old PBA servers.

  15. Check XML customization after migration and adjust if necessary.

  16. Check custom locales.

  17. Check timezone on new PBA servers.

  18. Check SELinux mode on the PBA Application server, it must be set to permissive.

    Refer to the Parallels Knowledgebase article #117641 for more details.

If you want to keep the current IP's (new IP's) on the migrated container and do not want to change them, follow the steps below:

  1. In POA DB execute query: SELECT * FROM bmbridge_settings;

and check value of "" and ""

  1. If old IP is there - then you should change it to new IP.

  2. Then you need to make sure that hostname specified in "" resolves to current frontnet IP of PBA application server from POA core and POA UI - you just need to add or edit existing entry for this hostname in hosts file on POA core and POA UI server and check hosts files on other servers in your PA environment.

In DNS this URL must resolve to new public IP of PBA-E application server

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 210d017ddc3a076d22f0f865b1cf0730 92711db0799e8aefe8e51f12dace0496 5356b422f65bdad1c3e9edca5d74a1ae ac82ce33439a9c1feec4ff4f2f638899 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF