Versions Compared

Old Version 2

changes.mady.by.user Leena Gopal

Saved on

compared with

New Version 3

changes.mady.by.user Leena Gopal

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel6
outlinefalse
typelist
printablefalse

Overview

This procedure outlines the steps to be performed in the SnapLogic Classic IIP when the JCC node VM of the Groundplex is migrated to another region. For example, you can use these steps to migrate the VM from the US West region to the US East region (Azure platform).

Prerequisite

Ensure the Firewall firewall rules are updated with the new hostnames host names and IP addresses to enable inter-node communication. For more information, refer to Groundplex Deployment Planning.

Steps to migrate the Groundplex

  1. As an Org admin, log into in to SnapLogic and open Monitor from the Apps menu on the right side of the header. The SnapLogic Monitor System overview displays information about Snaplexes and their nodes. This is as shown in the images below:

Image Modified

  1. Open the System overview from the Infrastructure link in the navigation pane. Click a node to view its details in the node map or list view. The Node details include the current status, resource usage, and the associated pipeline execution history.

For more information, refer to

  1. Learn more at https://docs.snaplogic.com/monitor/monitor-snaplex.html

  1. From the header of the node details panel:

    1. Click the Snaplex name to open and view the details.

    2. For Groundplexes, the Org admins can click the gear icon to restart or put the node in maintenance mode.

  2. Setting Maintenance mode completes any current jobs on the node and prevents additional jobs from running on that node. (In Classic IIP, this is under the Snaplex Health tab on the Dashboard).

  3. Ensure that there are no running Pipelines pipelines by checking the Pipeline pipeline wall of the Snaplex Dashboard.

Image RemovedImage Added

 

 

  1. Log

on

  1. in to the Linux server as a root or sudo user, and execute the below commands to stop the JCC node and the service:
    $ sudo /opt/snaplogic/bin/jcc.sh stop
    $ sudo systemctl stop snaplogic.serviceUse the command /opt/snaplogic/etc directory and backup the *.properties files (if any) and the .slpropz file.

  2. Complete the region migration to the

desired

  1. required region for the Linux server/VM. Learn more on Azure region migration at https://learn.microsoft.com/en-us/azure/resource-mover/tutorial-move-region-virtual-machines.

  2. If the migration is not performed using the Azure move utility, then install JCC on the new VM. (i.e. If a new VM is being provisioned in the new region).

For

  1. Learn more

information, refer to

  1. Installing a Snaplex on Linux

  2. Download the Configurationfile for the Groundplex from the Manager > Project Spaces > shared > Snaplex > Downloads tab.

    Image Modified

  1. Update the load balancer URL under the Snaplex Settingstab only if there is a change to the load balancer hostnamehost name.

  2. Use the following commands to restart the JCC node and service by logging on in to the migrated or new Linux server:
    $ sudo /opt/snaplogic/bin/jcc.sh start
    $ sudo systemctl stop snaplogic.service

  3. Verify the migration by successfully executing a few Triggered and Scheduled tasks.

  1. Repeat the procedure steps from 1 to 10 for the other Snaplex nodes.

Info

For the migration, no additional temp license configurations are required.

 

Related content:

https://docs.snaplogic.com/admin-manager/admin-manager-about.html

Installing a Snaplex on Linux