Upgrading from V11

This section describes upgrading from ActiveBatch version 11 to 2024.x. It is recommended that you perform the steps outlined below on a test Job Scheduler. After testing key jobs in 2024.x to make sure everything runs as expected, upgrade your V11 production environment.

 

The upgrade path to 2024.x is as follows:

 

V11 SP4 or earlier -> V11 SP5 -> V12 SP9 -> 2024.x

 

As per the above upgrade path, you cannot upgrade V11 directly to 2024.x. You must first upgrade to V11 SP5 (if you are running on an earlier service pack), then upgrade to V12 SP9. From V12 SP9 you can upgrade to 2024.x.

 

Note: Only the Job Scheduler server needs to be upgraded to V11 SP5 and V12 SP9. You do not need to upgrade your thick Clients (AbatAdmin) and Execution Agents. The primary purpose of upgrading to V11 SP5 and V12 SP9 is to upgrade the ActiveBatch backend database, which occurs automatically when a Job Scheduler upgrade is performed.

 

It is recommended you test key job types after upgrading to 2024.x. You do not need to test them when upgrading to V11 SP5 or V12 SP9, as these are considered transitional steps. We realize you may have many jobs, and it is likely not feasible to test them all.  We suggest you test jobs based on their type and/or criticality. For example, you may have many Jobs that repeatedly use a certain Jobs Library Job Step, like the MS SQL Server SSIS Package step. Or, you may run many PowerShell scripts. Test some of these job types to see if they run and work as expected.

 

To check which Job Scheduler version your V11 environment is running on, launch the AbatAdmin UI, then navigate to the Object/View Navigation pane. Right click on the Job Scheduler object (at the top of the navigation tree), then select Properties - see Version. If you see something like this: 11.0.5.xxx then you are running on V11 SP5. The xxx depicted in the example is the build number, which may vary if a hotfix was applied. Do not be concerned about the build number.

 

 

Version 11 SP5 is the V11 version posted at our website (earlier service packs are not posted). You can upgrade from any prior V11 service pack to SP5. To access the installation kit, log in to My ASCI. Next, click on the Product Downloads link located on the left-side menu, then select ActiveBatch V11 from the Select Product dropdown list. Download the Windows EXE installer for 32 or 64 bit, depending on the OS type your Job Scheduler is installed on. It is easier to run the EXE (as opposed to the .MSI file) when applying a service pack, which is why we recommend you download the EXE.

 

Before applying V11 SP5, back up the ActiveBatch database. If the database is not backed up and there is a need to roll back to a prior version (a rare event), you will not be able to do so without a database backup.

 

Run the ActiveBatch EXE on the Job Scheduler server. You will not be prompted to enter any information other than to confirm that you wish to run the .EXE. After running the .EXE, your Job Scheduler (if all goes well) will be running on V11 SP5.

 

Note: The assumption is you are upgrading to V11 SP5 on a test Scheduler, and therefore not likely running the test Scheduler in a H/A environment.  However, when going through the upgrade steps in a production environment (after testing the upgrade process) you must shut down the Job Scheduler service on each H/A node to avoid an inadvertent failover during the upgrade process.

 

 

Before upgrading to V12 SP9:

 

  • Back up your V11 SP5 ActiveBatch database. If the database is not backed up and there is a need to roll back to a prior version (a rare event), you will not be able to do so without a database backup.

  • Make a backup copy of abathost.exe.config file on the Scheduler server. This file may have configurations that were modified by your organization to allow for the proper execution of certain Jobs Library Job Steps. For example, the file may consist of configurations (what assembly versions to load) when running SSIS packages or SQL Server Jobs. Look for this file on the V11 Job Scheduler in the following location (the default installation folder): Program Files\ASCI\ActiveBatchV11. It will not be necessary to make a back up this file if you have not made any changes to the file to run specific Jobs Library Job Steps. If you are unsure if changes were made, save it to be on the safe side.

 

Next, when you upgrade to V12 SP9, you will need to have the following available:

 

  • The V12 Installation kit.

    • To download V12 SP9 download, log in to MyASCI at www.advsyscon.com. Next, click on the Product Downloads link located on the left-side menu, then select ActiveBatch V12 from the Select Product dropdown. Only the current service pack will be available for download. Since you are upgrading from one major-release to another (V11 to V12), downloading either the .EXE or .MSI installation kit will work the same. Therefore, download whichever kit you desire.

  • V12 serial keys.

  • The Job Scheduler Windows Service Account. This consists of a username and password. This will likely be the same credentials the Job Scheduler Service ran under in V11.

  • The local Execution Agent Windows Service Account. This consists of a username and password. This will likely be the same credentials the local Execution Agent Service ran under in V11.

  • The name and location of the ActiveBatch backend database.

    • Database information can be accessed using the V11 AbatAdmin client interface. Navigate to the Object/View Navigation pane, then select the Administrators tab. Click on Configuration. Under the Job Scheduler section, navigate to DBConnStr. This is the data link connection string that the Job Scheduler uses to connect to the backend database. This should be helpful in identifying the database. For example, when using SQL Server as the backend database, the connection string looks something like this:

      • Provider=SQLOLEDB;Data Source=DBServerName;Initial Catalog=AbatDBName;Integrated Security=SSPI

        • Note - Integrated Security=SSPI means the Job Scheduler Windows Service Account is being used to access the backend database.  

  • The account that is accessing the backend database. If it is a Windows account, it will be the same as the Job Scheduler Windows Service Account. If it is a database account, you must have the database username and password readily available.

    • If a database account is being used to access the database, you should see some indication of that in the connection string, and the above mentioned Configuration section in the AbatAdmin UI should have a DBUser name configured, along with the DBpassword (masked). If using a database account, please know the user name and password before attempting the upgrade.

 

Upgrade Steps:

 

  • Uninstall V11 SP5 from the Scheduler server. When you uninstall V11 SP5, it does not remove the ActiveBatch backend database.

  • Run the V12 SP9 installation kit. The installation kit installs the software, it does not configure it. Starting with V12, ASCI split the installation process into two distinct tasks - installing the software, and configuring the installed software. When installing the software, leave the Feature Selection window as-is (let it install all the software). After the installation, you must configure the local Execution Agent and Job Scheduler. This is accomplished using the ActiveBatch Management Console application, which should pop up after you complete the software installation. If it does not, you should see an icon on the desktop for this application, allowing you to start it from there. The application is named abatmgmt.exe, and it is stored in the ActiveBatch installation folder, in the bin subdirectory.

  • To configure the local Execution Agent (you must do this first), using the ActiveBatch Management Console, have the Execution Agent Windows Service Account readily available.  Enter the service account information when prompted. Do not be concerned with configuring any other aspect of the Execution Agent - you can accept the default values.

  • Next, configure the Job Scheduler using the ActiveBatch Management Console.

    • As you step through the configuration for the Job Scheduler, you only need to be concerned about entering the serial keys, the Windows Job Scheduler Service Account information, and information about the database. You can accept the default values for all the remaining fields.

    • When it comes to the database, you will need to select your V11 database type (e.g. SQL Server, Oracle), and then select "Initialize or Update an Existing Database". You will need to enter the V11 data source information, and whether access to the database is using a Windows account or a specific user name and password (when using a database account to access the database).

    • Because the database you select is a V11 database, the configuration application will recognize this (that you are installing a V12 Scheduler, but pointing to a V11 database). Because of this, you will be prompted as to whether or not you wish to have key ActiveBatch objects (e.g. jobs, plans, schedules, etc). disabled. This question is asked because the assumption is, when testing a Job Scheduler, you may want to manually enable jobs and other related objects in a controlled fashion, and not have the system start up and immediately begin to run jobs after the upgrade. It is recommended to you opt to disable the objects, so you can pick and choose (when you upgrade to 2024.x) which jobs you wish to enable, then test. When upgrading a production environment, you would likely opt to keep all your objects enabled, because testing is over, and you do want jobs to start to run right away, after the production upgrade.

    • After entering the Scheduler license keys, the Windows Service Account, and database information, you can review your choices and configure the Scheduler. Make sure that the database upgrade is successful. This is the key reason you must upgrade to V12 before upgrading to 2024.x. The database changes must run successfully.  If you see any errors related to the database upgrade where the resolution is not obvious, please contact technical support. If you see any errors not related to the database, they likely can safely be ignored, since you will not be testing any jobs in the V12 SP9 environment.

  • As a reminder, you do not need to upgrade your V11 SP5 Clients or Execution Agents to V12 SP9.

 

 

Like the V11 to V12 upgrade, the V12 SP9 to 2024.x upgrade is considered a major-release upgrade (as opposed to a service pack upgrade). We have strategies for setting up a test Scheduler when moving from a V12 SP9 production environment to 2024.x (which is not the case when moving from V11 to 2024.x). Since this section is all about upgrading from a V11 environment to 2024.x, we will continue the discussion in that context.

 

Before upgrading to 2024.x, back up your V12 SP9 ActiveBatch database. If the database is not backed up and there is a need to roll back to a prior version (a rare event), you will not be able to do so without a database backup.

 

Next, when you upgrade to 2024,x you will need to have the following available:

 

  • The 2024.x installation kit. Since you are upgrading from one major-release to another (V12 to 2024.x), downloading either the .EXE or .MSI installation kit will work the same. Therefore, download whichever kit you desire.

  • V12 serial keys (they will work on a 2024.x Scheduler providing they have not reached their expiration date).

  • The Job Scheduler Windows Service Account. This consists of a username and password. This will likely be the same credentials the Job Scheduler Service ran under in V11/V12.

  • The local Execution Agent Windows Service Account. This consists of a username and password. This will likely be the same credentials the local Execution Agent Service ran under in V11/V12.

  • The name and location of the ActiveBatch backend database.

  • The account that is accessing the ActiveBatch backend database. If it is a Windows account, it will be the same as the Job Scheduler Windows Service Account. If it is a database account, you must have the database username and password readily available.

 

Upgrade Steps:

 

  • Uninstall V12 SP9 from the Scheduler server. When you uninstall V12 SP9, it does not remove the ActiveBatch backend database.

  • Run the 2024.x installation kit. The installation kit installs the software, it does not configure it. Starting with V12, ASCI split the installation process into two distinct tasks - installing the software, and configuring the installed software. When installing the software, leave the Feature Selection window as-is (let it install all the software). After the installation, you must configure the local Execution Agent and Job Scheduler. This is accomplished using the ActiveBatch Management Console application, which should pop up after you complete the software installation. If it does not, you should see an icon on the desktop for this application, allowing you to start it from there. The application is named abatmgmt.exe, and it is stored in the ActiveBatch installation folder, in the bin subdirectory.

  • To configure the local Execution Agent (you must do this first), have the Execution Agent Windows Service Account readily available.  Using the ActiveBatch Management Console, enter the service account information when prompted. Do not be concerned with configuring any other aspect of the Execution Agent - you can accept the default values.

  • Next, configure the Job Scheduler using the ActiveBatch Management Console.

    • As you step through the configuration for the Job Scheduler, you only need to be concerned about entering the serial keys, the Windows Job Scheduler Service Account information, and information about the database. You can accept the default values for all the remaining fields.

    • When it comes to the database, you will need to select your V12 database type (e.g. SQL Server, Oracle), and then select "Initialize or Update an Existing Database". You will need to enter the V12 data source information, and whether access to the database is using a Windows account or a specific user name and password (when using a database account to access the database).

    • Because the database you select is a V12 database, the configuration application will recognize this (that you are installing a 2024.x Scheduler, but pointing to a V12 database). Because of this, you will be prompted as to whether or not you wish to have key ActiveBatch objects (e.g. jobs, plans, schedules, etc). disabled. This question is asked because the assumption is, when testing a Job Scheduler, you may want to manually enable jobs and other related objects in a controlled fashion, and not have the system start up and immediately begin to run jobs after the upgrade. It is recommended to you opt to disable the objects, so you can pick and choose which jobs you wish to enable, then test. When upgrading a production environment, you would likely opt to keep all your objects enabled, because testing is over, and you do want jobs to start to run right away, after the production upgrade. Note: The key objects may already be disabled if you choose this option when upgrading from V11 to V12.

    • After entering the Scheduler license keys, the Windows Service Account, and database information, you can review your choices and configure the Scheduler.

  • Next, if you backed up abathost.exe.config from your V11 Scheduler, copy it to the 2024.x installation "bin" directory. The default directory is Program Files\ASCI\ActiveBatchV14\bin. It is OK to overwrite the existing file with your saved copy, if prompted.

  • Next, run the following script on the Job Scheduler server - Enhanced Data Encryption. Starting with ActiveBatch version 2023.2 (and of course, included in 2024.x), we introduced enhanced data encryption. When the script is run, it will update the objects in your database (where applicable), to utilize this feature. Please note that it is harmless to run the script more than once. This is mentioned because there isn't an obvious way to tell if the database has been updated to include the enhanced data encryption. Therefore, if you are uncertain if the script was run, you can safely run it multiple times. It does add a revision history record to each object it updates, and when doing so, it inherently encrypts any of the object's sensitive data.

  • To test jobs on remote Agents, and not just on the local Scheduler system, you will need to install the 2024.x Agent on the desired system(s). If a prior major-release Agent version already resides on the system, you must uninstall it first, then install the 2024.x Agent.

  • To access the Job Scheduler using the thick client named AbatConsole (it was renamed from AbatAdmin to AbatConsole in V12), you will need to install the AbatConsole on designated user's desktops. A V12 or earlier client cannot connect to a 2024.x Job Scheduler. Uninstall the client if a prior-release version is installed on the target system. Use the Windows 2024.x installation kit to install AbatConsole. You do not need serial keys when installing the client, and the client does not need any post-installation configuration. Using the Windows installer previously downloaded, deselect the other components you do not wish to install, and just install the Client Tools.

 

After upgrading your Scheduler and completing the testing, follow the same steps to upgrade your production environment.