Article ID: 128036, created on Jan 12, 2016, last review on Jul 14, 2016

  • Applies to:
  • Operations Automation
  • Business Automation

Overview of Windows Platform migration to Linux is here.

This part includes migration of the next components:

  1. Operation Automation Management Node
  2. Business Automation Application Server
  3. Business Automation Database Server
  4. Business Automation Online Store Server

Limitations

  • Migration is possible only for OSA 6.0.6 with HOTFIX 128148 PAU v3 and later.
  • Migration to RHEL/CentOS 6.5 (x64)
  • DB Server: PostgreSQL
  • Location of DB server for OA MN: Management Node
  • Location of DB server for BA: BA Database Server
  • After migration, new Linux hosts own old used IPs of Windows nodes

Scheme

  • Deploy new Linux nodes with new temporary IPs (RHEL/CentOS 6.5 (x64)) for:
    • OA MN
    • BA DB
    • BA APP
    • BA Store
  • Install the same version of OSA on the new nodes.
  • Install the same set of packages/containers as on Windows.
  • Migrate OA MN:
    • Migrate DB from MSSQL to PostgreSQL
    • Modify DB to Linux environment
    • Adopt OSA configuration files on new Linux MN
    • Move IP address and hostname from old MN to the new node
  • Migrate BA:
    • Migrate DB
    • Configure Linux BA App
    • Move IP address and hostname
    • Register BA App and DB nodes in OA
  • Migrate BA Store.
    • Move IP address and hostname from Windows BA Store to Linux BA Store

Deployment of new OSA set

Before migration, prepare new complete OSA set on Linux nodes. You need to deploy OA Management Node, BA Application, Database and Online Store nodes. All BA nodes should be registered in Operation Automation.

  1. Deploy a new node for Operations Automation Management Node:

    Use the instructions from the Linux Platform Deployment guide to deploy new hosts for a Management Node.

  2. Deploy new nodes for Business Automation:

    Use Business Automation Deployment guide for Linux to deploy new hosts for Business Automation Database/Application/Online Store servers.

  3. Install the same version of OSA on the new nodes (the set of updates and hotfixes should match on Linux and Windows MN) Use the instructions from the Linux Platform Deployment guide for installation.

  4. Install BA nodes according to the instructions from the Business Automation Deployment guide for Linux.

  5. Check that both MN servers have the same list of installed modules:

    PCP > Infrastructure > Modules

  6. Install missing modules on the destination server.
  7. Check that both MN servers have the same list of installed packages:

    Infrastructure > Service Nodes > [MN NODE] > Packages

  8. Install missing packages on the destination server from UI:

    Infrastructure > Service Nodes > [MN NODE] > Packages > Install Package

  9. Check that both BA App servers have the same list of installed components. The list of installed components is located in the configuration file containers-list (Default location is C:\Program Files\Parallels\PBA\etc\ssm.conf.d\containers-list).

  10. Install missing components on Linux node according the instructions from the Business Automation Deployment guide for Linux.

OA MN Migration

Use the KB article to migrate OA Management Node.

BA App+DB Migration

Use the KB article to migrate BA Database and Application servers.

BA Store Migration

Use the KB article to migrate BA Online Store server.

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae

Email subscription for changes to this article
Save as PDF