Search Engine: Elastic

Article ID: 128111, created on Jan 19, 2016, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation
  • Business Automation


Windows Platform consists of the following components:

  • OA Servers:
    • Management Node
    • DB Server
    • UI Server
    • Branding Server
    • DNS Server
    • Privacy Proxy Server
  • BA Servers:
    • Application Server
    • DB Server
    • Online Store Server

All these servers will be migrated to new Linux servers.

The latest OS RHEL/CentOS 6.5 (x64) should be used for deployment of new servers.

IPs of Windows servers are moved during migration to the new Linux servers, except cases when it is not required to preserve the same addresses (for example, for UI and Privacy Proxy Servers).

Migration can be divided into several major parts:

  1. Platform components:
    1. Privacy Proxy Server
    2. DNS Servers
  2. Platform core:
    1. Management Node + DB Server
    2. BA App + BA DB
    3. BA Store Server
  3. UI Server + Branding Server

The order of platform components migration (Proxy, DNS) does not depend from each other, and it can be performed as you like. Migration of platform components should be completed before migration of Platform Core servers.

Migration of UI/Branding servers is possible after migration of Management Node.

1. Privacy Proxy


  1. Install new Privacy Proxy Server on Linux according to the Deploying Privacy Proxy section of Linux Platform Deployment guide.
  2. Remove the PrivacyProxy service package from the Windows node.



  1. Deploy a new Linux server (RHEL/CentOS 6.5 (x64) for BIND according to the Deploying Linux-based DNS Servers section of Linux Platform Deployment guide.
  2. Change DNS configuration to the BIND server by modifying the activation parameter setting of the "DNS Hosting" resource.
  3. Update domains for the new nameservers with the script from the above-mentioned article.
  4. Move original IP from the MS DNS server to the BIND server.

3. OSA Core components

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

For migration instructions refer to the Windows OSA core components migration to Linux article.


  • 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: MN node
  • Location of DB server for BA: BA DB node
  • After migration, new Linux hosts own old used IPs of Windows nodes


  • 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 the Windows nodes.
  • OA MN migration:
    • 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
  • BA migration:
    • 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

4. UI + Branding


  1. Deploy new UI and Branding servers according to the Deploying Operations Automation UI on Linux section of Linux Platform Deployment guide.

  2. Migrate a brand from the Windows server to Linux according to the Migrating Brands section of Services Upgrade/Migration guide.

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae

Email subscription for changes to this article
Save as PDF