Automate - Upgrading to Rampiva Automate 8
The material in this document is for informational purposes only. This guide assumes that the most recent version of Rampiva Automate is in use unless otherwise noted in the prerequisites or introduction. The products it describes are subject to change without prior notice, due to the manufacturer’s continuous development program. Rampiva makes no representations or warranties with respect to this document or with respect to the products described herein. Rampiva shall not be liable for any damages, losses, costs or expenses, direct, indirect or incidental, consequential or special, arising out of, or related to the use of this material or the products described herein.
Introduction
This article covers recommended considerations prior to upgrading to Rampiva Automate version 8 from version 7.
Prerequisites
Local Administrative privileges to install software
Internet connection to download software
Microsoft SQL Administrative privileges (if applicable)
Upgrading Rampiva Automate
A. Considerations
| 1 | Deprecated desktop version of Workflow The desktop version of Workflow Designer and Workflow Execution have been deprecated. You can still open previously created workflows, however new operations cannot be added or edited with the deprecated Workflow Designer. | To create new workflows or edit existing workflows, use the web version of Nuix Rampiva. Workflows can be added and edited in the Library section. |
| 2 | Migrated third-party service configurations to Third-Party Services settings The Relativity and Microsoft Purview services configurations have been migrated to the Third-Party Services settings tab. |
|
| 3 | Third-Party Services license Each Third-Party Service requires the Rampiva license to be enabled for the service hostname. | Contact Rampiva support to update your license profile to include the service hostnames in scope. |
| 4 | Relativity license format The format of the Rampiva license for Relativity has changed, and now contains only the Relativity hostname. | Contact Rampiva support to update your license profile to include the service hostnames in scope. |
| 5 | Legal Hold triggers The Legal Hold triggers have been changed from only being able to trigger ECC collections to being able to trigger arbitrary Rampiva jobs. |
|
| 6 | Purview and Legal Hold only workflows Workflows that have a Purview Service parameter can only be submitted from the Jobs → Purview section. Workflows that have a Legal Hold Service parameter can only be submitted from the Legal Holds. |
|
B. Upgrade Steps
| 1 | Take note of the memory settings used to run the Scheduler service, in the C:\Program Files\Rampiva\Automate\Scheduler\runService.bat file. If you did not modify the memory settings of the Scheduler service, this step can be skipped. If desired, make a backup copy of this file. |  |
| 2 | Take note of the account (Log On As) under which the Rampiva Scheduler and the Rampiva Engine Server services run, on both the Scheduler server as well the Engine Servers. |  |
| 3 | Backup the Automate database. |
|
| 4 | Uninstall the Rampiva Automate version 7 on all servers. |
|
| 5 | Download and install Rampiva Automate version 8 on all servers, from https://downloads.rampiva.com/automate/release/index.html |
|
| 6 | Update the memory settings used to run the Scheduler service, in the C:\Program Files\Rampiva\Automate\Scheduler\runService.bat file. See the note taken at step 1. | |
| 7 | Update the account (Log On As) under which the Rampiva Scheduler and the Rampiva Engine Server services run, on both the Scheduler server as well the Engine Servers. See the note taken at step 2. |
|
| 8 | If the OData Standalone Server was installed, update the configuration of the service by modifying the config.yml file for this service, located at C:\ProgramData\Rampiva\Automate\ODataServer\config\config.yml |
|
Related articles