Migrating from Astera 7.x to Astera 8
Last updated
Last updated
Astera 8 is a major release and not a direct upgrade of Astera 7.6. This means that migrating from Astera 7.x to Astera 8 won’t require you to uninstall Astera 7 since Astera 8 can be installed side by side with Astera 7 on a system.
Astera 8 is backward compatible, and therefore, most of the flows created on Astera 7 can run on Astera 8 without modifications. However, as with most major releases of any complex software, we recommend that you upgrade your lower-level environment first, so you have an opportunity to test and verify any existing flows.
This will make it possible to identify any migration issues you may encounter early on in the upgrade cycle. In this document, we will cover how you can migrate from Astera 7.x to the all-new Astera 8.
The installation package for Astera 8 (64-bit) contains two setups (.exe) files:
AsteraDataIntegrator.exe – for Astera client, and
IntegrationServer.exe – for Astera Integration Server
The setup files for Astera 8 can be downloaded from .
Click to learn how to install Astera 8 client and server.
Unlike the previous releases of Astera, Astera 8 comes with a single licensing key (for the server) rather than two separate keys for the Astera server and client. The licensing key for Astera 8 has changed which means you cannot use your Astera 7 key to register Astera 8.
The single licensing key for Astera 8 is used to register the Astera server and it controls how many clients can connect to the server as well as the functionality available to the connected clients.
If you’re planning to migrate to Astera 8, please contact to get your new Astera 8 license key. The server threshold to accept licenses will depend on the number of licenses you purchase. So, for instance, if you have purchased 50 licenses, the server will accept up to 50 licenses at most.
The Astera 8 client can be configured with multiple different servers, however, it can only connect with one server at a time. The jobs scheduled, queued, or running on the other registered server will continue to run without interruption even if the client is not currently connected to the server.
All servers pointing to a single repository database will form a cluster of servers sharing the common workload of queued jobs. A cluster of v8 servers you configure will be up and running and processing jobs in a similar way to 7.6, despite the fact that the v8 client can only connect to and manage one v8 server at a time. You can see which server in the cluster has actually processed a job by right clicking the Cluster and opening the Server Jobs window.
You need to set up a new repository to communicate with the Astera 8 server. While upgrading the previous releases of Astera 7, you would simply go to Server > Upgrade Cluster Database.
However, while migrating to Astera 8, you need to set up a repository in a new database from scratch to communicate with the server(s) and store the record of server activity. To set up a repository in Astera 8, go to Server menu > Configure > Build Repository Database and Configure Server.
Once you have built a cluster repository in Astera 8, the next step is to migrate the scheduled jobs you created in Astera 7.
For this, open Scheduler in Astera 7 from Server > Job Schedules.
You will see all the scheduled jobs listed in the Scheduler. Select the jobs you want to migrate.
Click the ‘Export Schedule’ button in the Scheduler toolbar.
Point to the directory and folder where you want to save the scheduled jobs and click OK.
Now Astera will create a separate XML file with a ‘.Sched’ extension for each scheduled job and save it in the designated folder.
A message window will pop up to notify you that your scheduled jobs have been successful. Click OK.
Now you have to import the job files in Astera 8 to complete the migration process. For this, open the Astera 8 client and go to Server > Job Schedules.
This will open the Scheduler tab in the Astera client. To import the existing jobs, click the ‘Import Schedule’ button in the Scheduler toolbar.
Point the path to the directory where you have saved the schedule files. Select all the scheduled jobs you want to import and click ‘Open.’
You can see that the existing jobs scheduled in Astera 7 have been successfully migrated to Astera 8 and a new Job ID has been assigned to each job.
Prior to any upgrade, we strongly recommend that you take a full backup of your repository database. Also, upgrading a lower-level environment first (such as QA, UAT, etc.) is recommended prior to upgrading the Production environment. This will make it possible to sort out/resolve any issues before upgrading Production.
Steps to Upgrade:
Using the Astera 7 client, run the following dataflow to export existing schedules into a comma-delimited file.
Take note of any existing Cluster Settings. You can check it by right clicking the cluster in Server Explorer and selecting ‘Cluster Settings’ in the context menu. These settings will need to be re-configured manually after the upgrade.
It may be helpful to take screenshots of those settings for later reference. The settings include Staging Directory, Purge Job Frequency Options, Email Notification Setup, and optionally, Server Profiles if a non-default profile was used prior to the upgrade.
Open the Astera 8 client. Go to Server menu > Manage > Build Cluster Database. Point it to the database hosting the Astera repository.
Use the dataflow below to import the schedules you have exported in Step 1.
Note: Prior to running the dataflow, you will need to change the Database Table Destination object to point to the database where the Astera 8 repository resides.
Open Server Explorer, right-click your cluster, and select ‘Cluster Settings’. Manually reconfigure the relevant settings from Step 2. Optionally, you can manually reconfigure the Server Profiles setting if a non-default profile was used prior to the upgrade.
Restart the Astera server.
This completes the upgrade.
You can download the flows by clicking on the link below:
When you are starting the migration process, it is recommended to keep the Astera 7 and Astera 8 servers running in parallel. This is to avoid any interruption in jobs that are currently running.
We also recommend you initiate the migration process with a lower level, testing environment and then promote your deployment to a higher-level environment as needed. This will help ensure a smooth migration process with any flow compatibility issues spotted early in the transition cycle.
Follow through the steps explained in to build a cluster database and set up a repository in Astera 8.
Download attached dataflow:
Install the Astera 8 client and server on your machine. You can read more on installing the Astera 8 client and server in document.
Download the attached example dataflow:
(70 KB)
(60 KB)
