Was this page helpful?

Migration and upgrade

     

    1. Migration

    1.1 NEP Migration

    Important : Please note that all migration (ex. from one infrastructure to another) needs NEP migration expertise. Our Consulting team propose migration service to our clients. Newtest team (specially Support team) is not reponsible to any migration action done by customers themselves and will not take charge of incidents caused by such migration. 

    What is a migration in Newtest?

    There are different types of migration according to the nature of needs.

    1. Move the whole solution from on infrastructure to another

    If you are willing to move your NEP solution installed on one/several Windows Server to other infrastructures and if you are using virtual solution, the ideal way is to move the entire virtual infrastructure to the new platform.

    However, when you are technically limited to move the entire infrastructure, either you are using physical machines or your virtual solution does not support changes like this, you will then need a migration of solution Newtest.

    2. Major version upgrade

    If you are using a version older than the current version and you are willing to catch up with the latest release, please firstly check your current solution version which is shown on the NMC web interface.

    With a version one major release away from the version which you are willing to upgrade to, you will need a migration instead of simple upgrade action.

    For example, from NEP 2.2.1 to NEP 3.0.0 or from NEP 3.0.1 to NEP 3.1.0, you will need a migration.

    3. Optional modules upgrade

    If you are using an optional module, such as CLT( collector ), NAM (Newtest Alarm Module), DRP (Disaster Recovery Plan), etc., their versions may be different from the main NEP modules. In the case that you need to upgrade their version, you may need a migration plan.

     

    1.2 Probes Migration

    In the case of a probe, you will first need to check if the future Robot version is compatible with your NEP solution version.

    Before applying the new version of Robot to all your current probes, you will need to adapt your scenarios with an NTBR of this latest version. Once all scenarios are validated on an NTBR, we highly suggest you upload the configuration to the NRFT (Newtest Robot For Testing) for at least two weeks in order to confirm the adaption.

    Once your scenarios are all compatible with the latest Robot version, you could apply the new version to your probes with the adjusted configuration.

     

    2. Upgrade

    When we talk about the upgrade, it is for minor version updates. Especially on cumulative patch level.

    For example, from NEP 3.0.1R0 to NEP 3.0.1R1 or from Robot 7.6.0R115 to Robot 7.6.0R116.

    Patch upgrade requires less technical expertise than a migration that you may process it yourself.

    2.1 NEP upgrade

    If you have any doute about performing the upgrade, please contact the Newtest Expert team first before taking any action.

    To upgrade an NEP solution, you will surely have a short interruption of supervision or access to Newtest web suite during the installation. It usually takes less than 30 minutes. You may apply cumulative patches with the following steps.

    1. Download patches from IP-LABEL extranet

    Place the NMC, NRS, DWH patches to the servers and unzip them.

    2. Upgrade your DWH procedures

    The DWH installer is a simple extracting package of upgrade procedures.

    After having executed the installer, you may choose the path to extract contents.

    You will then need to execute manually the queries extracted.

    3. Upgrade your NMC

    Execute the NMC patch on the server where NMC modules are installed.

    Once the installation is done, your supervision will return. If not, you may need to restart the NRM service (Newtest Remote Manager) on the server.

    4. Upgrade your NRS

    Execute the NRS patch on the server where NRS modules are installed.

    If after applying the patch, you find certain reports are no longer available from the NRS web interface, it might be caused by report publishing failure.

    You may first need to check in "C:\Program Files (x86)\ip-label\Newtest\Setupfiles\NewtestReporting X.X.X RX\UpdateReports.log" if the reports in question are mentioned in this file.

    To force a report publishing, you will simply need to execute the file "C:\NewtestReporting\Reports\PatchReports\UpdateReports.cmd"

     

    Once all patches are installed, you will need to manually re-launch the NRM proxy.

     

    2.2 Probes upgrade

    Applying a cumulative patch of Robot to its current version is considered as a Probe upgrade.

    Before applying a cumulative patch of Robot to all your current running probes, you will need to adapt your scenarios with an NTBR of this patch version. Once all scenarios are validated on an NTBR, we highly suggest you upload the configuration to the NRFT (Newtest Robot For Testing) for at least two weeks in order to confirm the adaption.

    Once your scenarios are all compatible and stable with the patch version, you could apply the patch to your probes with the adjusted configuration.

    To upgrade probes, you have several different methods :

    2.2.1. NMC Distribution Package

    An NMC distribution package allows you to install the same patch to several probes via NMC web interface.

    1. Download NMC Distribution Package from IP-LABEL extranet

    Place the unzipped installer SUITE-xxxRxxx-Distribution-Package-for-NMC-Buildxxx on the NMC server and execute it.

    2. Choose probes to apply the patch

    On NMC web interface -> Operation -> Patches tab, you could find the new patch appear in the list.

    Click on the patch name, the web interface will automatically generate a list of probes on which you could apply the patch.

    Select the probes that you want to upgrade.

    3. Choose when to apply the patch

    Once probes are selected, you will need to choose when to apply the patch. We propose two options :

    a. Apply Now

    When you click on Apply Now, the selected probes will detect in short that there is a patch to apply. They will then download the patch, upgrade themselves and restart directly.

    b. Apply Later

    This option allows selected probes to wait until next reboot to apply the patch. Normally it will be til the daily reboot.

     

    2.2.2 NOUI Installation Package

    If your company has a centralised installation or patching system/procedure, you may use the NOUI Installation Package to patch your probes with your internal tool.

    1. Download NOUI Installation Package from IP-LABEL extranet

    The NOUI installer is ROBOT-xxxRxxx-NOUI_Buildxxx on our extranet.

    2. Stop your Robot properly

    Remember to stop your Robot properly via NMC supervision interface or with NWS (Newtest Web Services) commandes.

    3. Deploy the patch with your tool

    Once applied the patch with your patching system, remember to start all your robots.

     

    2.2.3 GUI Installation Package

    You may of course upgrade your probes one by one with the GUI Installation Package.

    1. Download GUI Installation Package from IP-LABEL extranet

    Place the unzipped installer ROBOT-xxxRxxx_Buildxxx on the Robot machine.

    2. Stop your Robot properly

    Remember to stop your Robot properly by the NRM Proxy -> Stop Robot or via NMC supervision interface.

    3. Execute the installer

    A machine reboot might be necessary after the installation is done.

     

    Was this page helpful?
    Tag page (Edit tags)
    • No tags
    Page statistics
    8028 view(s), 6 edit(s) and 8288 character(s)

    Comments

    You must login to post a comment.

    Attach file

    Attachments