Alpaca CLI 4.2

Enterprise Migration

Introduction

A BroadWorks's Service Provider or Enterprise can be highly customized with Groups, Users, Devices, Service Instances, and settings. The bulk of provisioning level settings reside under this umbrella of information. Because of this is it highly time consuming to build and configure an Enterprise will all of it's corresponding components. If later the Enterprise needs to be moved to a different application server cluster the process of collecting all the settings and information regarding the Enterprise is daunting.

This feature, Enterprise Migration, provides a function that allows BroadWorks' Enterprises to be moved from one BroadWorks system to another without the loss of Groups, Users, Devices, settings, passwords, greetings, or corresponding attached files.

Procedure

Enterprise Migration performs a sequence of information retrieval prior to migration to ensure that the Enterprise meets the set of requirements that will allow the Enterprise to successfully migration to the destination system. There are two types of restrictions that would prevent a valid migration - Requirements and Encumbrances. If either one of the restrictions contains errors then the migration will not be allowed to procede. See the Limitations section for further information.

  • Check Migration Validity
  • Remove Groups
  • Remove Enterprise Trunk Number Ranges
  • Remove Enterprise
  • Create New Enterprise
  • Authorize Services and Service Packs
  • Add Enterprise Settings
  • Add Service Settings
  • Add Enterprise Service Settings (Entperprise Only)
  • Add Devices
  • Add Groups and their Users
  • Add Enterprise Settings that need to be added after Groups
  • Assign Users and Devices
  • Add Credentials

Recovery

Following the information retrieval process the full details of the Enterprise are backed up for recovery purposes. The settings information retrieved is backed up as JSON. Announcement files and device configuration files are backed up in their original format. These files collectively can be used for recovery purposes.

Limitations

These items are not included in Enterprise Migration.

  • Service Pack Migration Tasks
  • Enterprise Call Center Branding

Requirements

Requirements are restrictions that are determined by inspecting the desired Destination Application Server to determine if the Enterprise can be moved into the Destination Application Server successfully.

  • Domains
    • The Domains (e.g., "xyz.com") that are available and being used by the Service Provider must exist in the target system.
  • Device Types
    • The Destination system must have all Identity Device profile types as currently used on the source system.

Encumbrances

Encumbrances are restrictions that are contained within the Enterprise's settings. These restrictions do not require a Destination Application Server to be determined and can be checked in advance for potential migration targets.

  • System Access Device
    • If a User in the Service Provider is assigned to an Identity/Device Profile, and this is a System level resource, then the Service Provider cannot be moved.