Navigation :

Migration Tools Installation

Overall Installation Steps

The high-level steps for installing and configuring the N2SNS migration tools are:

Ensure the installation pre-requisites are met.
Install the migration tools package.
Perform any required post-installation steps.
Update the migration tool configuration as desired.

Installation Pre-requisites

OS-specific Setup

Refer to the specific Red Hat or Debian instructions for any pre-requisites as required.

Perl

The N2SNS SMS node requires several Perl packages to be available prior to installation. The package names may vary depending on your OS type:

RPM-based Systems	DEB-based Systems
`perl` >= 1:5.12 `perl(Carp::Always)` `perl(Clone)` `perl(DBI)` `perl(Data::Dumper)` `perl(Digest::MD5)` `perl(File::Basename)` `perl(Getopt::Long)` `perl(IO::Handle)` `perl(JSON)` `perl(POSIX)` `perl(Storable)` `perl(Switch)` `perl(Time::HiRes)` `perl(Time::Local)` `perl(XML::LibXML)` `perl(base)` `perl(lib)` `perl(strict)` `perl(warnings)`	`perl` >= 5.12 `perl-base` `perl-modules` `libcarp-always-perl` `libclone-perl` `libdbi-perl` `libjson-perl` `libswitch-perl` `libxml-libxml-perl`

For each of these packages (or with all as one command), execute the instructions specific to your operating system:

RHEL 8	Other RPM-based Systems	DEB-based Systems
`sudo dnf install <package(s)>`	`sudo yum install <package(s)>`	`sudo apt-get install <package(s)>`

Installation Steps

Follow the appropriate installation steps depending on your installation sources.

From N-Squared Repository

Execute the instructions specific to your operating system:

RHEL 8	Other RPM-based Systems	DEB-based Systems
`sudo dnf install n2sns-mig`	`sudo yum install n2sns-mig`	`sudo apt-get install n2sns-mig`

Post-Installation Steps

Database Integration

Oracle Database Drivers

If migrating to N2SNS from an Oracle database, the Oracle-provided client packages must be installed.

Follow the Oracle-provided installation instructions to install your preferred version of the following packages:

Basic Package (*instantclient-basic*)
SQL *Plus Package (*instantclient-sqlplus*)
SDK Package (*instantclient-devel*) For RPM-based systems, RPM packages are provided and recommended. For DEB-based systems, third-party tools such as alien may be used to convert the RPM packages.

NCC Migration

When migrating to N2SNS from the Oracle NCC platform, some configuration will have to be changed in order to connect to the incumbent platform.

To set these values, in the file /usr/share/n2sns/migration/NCC/migrate.pl, locate the following section:

# Site defaults.
my $ncc_dbconnect           = 'dbi:Oracle:host=REPLACE_WITH_NCC_HOSTNAME;sid=SMF';
my $ncc_dbusername          = 'smf';
my $ncc_dbpassword          = 'REPLACE_WITH_NCC_DB_PASSWORD';
my $n2_dbconnect            = 'dbi:Pg:dbname=n2in;host=REPLACE_WITH_N2SNS_DB_HOSTNAME;port=REPLACE_WITH_N2SNS_DB_PORT;';
my $n2_dbusername           = 'n2sns_owner';
my $n2_dbpassword           = 'REPLACE_WITH_N2SNS_DB_PASSWORD';
my $migration_user          = 'Migration';

Replace the sentinel values as follows:

REPLACE_WITH_NCC_HOSTNAME must be updated to the address of the primary NCC database node to connect to.
REPLACE_WITH_NCC_DB_PASSWORD must be updated to the smf database user’s password on the NCC platform.
REPLACE_WITH_N2SNS_DB_HOSTNAME must be updated to the address of the primary N2SNS database node (or proxy) to connect to.
REPLACE_WITH_N2SNS_DB_PORT must be updated to the listening port configured for the primary N2SNS database node (or proxy).
REPLACE_WITH_DB_PASSWORD must be updated to the n2sns_owner database user’s password, as created during database preparation.

In the same file, locate the following section:

# N2SNS/NCC defaults.
my $migration_user          = 'Migration';

These default values may be updated as required:

Migration is the username that is added to each migrated record as the last change and creation user. This does not need to be an actual N2SNS database user.

Firewall

The firewall (if any) on the migration tools node must be updated to allow:

Outbound database requests to the platform to migrate from.
Outbound database requests to the DB node(s).

The exact commands to do this will depend both on the firewall on your platform and also which port(s) are in use. For example, to allow the default Oracle and PostgreSQL ports when using firewalld, the commands might be:

firewall-cmd --zone=public --add-port=1521/tcp --permanent
firewall-cmd --zone=public --add-port=5432/tcp --permanent
service firewalld restart