How to build a test environment and try upgrade in SupportCenter Plus ?

How to build a test environment and try upgrade in SupportCenter Plus ?

When you are planning to upgrade SupportCenter Plus to the latest version, it is highly advisable to try the upgrade on the test environment first so that you will be confident about the upgrade on the Production server. Make sure the test setup is not accessible via the internet or not accessible to other tools so that the Mails will not be fetched or sent / SMS will not be sent from this test setup.

Steps to follow :

1. Stop the ManageEngine SupportCenter service on the production server.

Only trimmed backup is needed to do this upgrade to minimize the upgrade time.

3. Install Test SupportCenter Plus on the new test server.  You can get related old release builds from our archives here. You should restore the database in the same build number always. You can know your Build number from the About page in the top right of the user interface.

4. Start and shut down the test application once.

5.  Restore the database as mentioned here. Please note a s it's only a test environment, you don't have to copy file attachments, indexes, archive folders to this new setup.

Dont start the test application, till the below queries are executed.
As said above, Make sure this test system is out of your network, such that no new emails will be fetched or notifications will not be sent from this setup.  Please execute the below queries such that it will work as a test setup.

The below steps are applicable from 8118 builds only.

1. Connect to the test database of your test setup.

-- To stop incoming
    update incomingmailserver set HOSTNAME = 'XYZ';

-- To Stop Outgoing mails

update outgoingmailserver set HOSTNAME = 'ALPHA';
update outgoingmailserver set ALTERNATEHOSTNAME = 'BETA';  

Below queries can be used if needed or features are used alone.

-- To Stop Outgoing SMS

delete from Services where serviceid=(Select Serviceid from ServiceAction where serviceactionid=(select serviceactionid from smsconfig));

-- To Disable Schedules (eg. mail fetching, schedule based integrations like analytics, custom schedules etc..)

-- To Disable all Custom Menus

UPDATE Menu_Actions SET ISENABLED='false';

  -- To Disable all Custom Triggers

UPDATE Auto_Actions SET ISENABLED='false';

 -- To Disable FAFRs with Action as Execute Script

UPDATE RuleData SET ISENABLED = 'false' WHERE RULEID IN (SELECT rd.RULEID FROM RuleData rd LEFT JOIN RuleActionsMap ram on rd.RULEID = ram.RULEID LEFT JOIN RuleActionTypes rat on ram.RULEACTIONTYPEID = rat.RULEACTIONTYPEID WHERE rat.ACTIONNAME LIKE 'execute_script_action');

  -- To Disable Telephony Service

Update TelephonyService set enableservice='false'; *.

Once the above queries are executed in your test database 

Start the SupportCenter Plus service and log in to it and check if everything looks fine in this test setup.

Now shut down the application and try the upgrade in this test environment

For any assistance, please contact our support at

How to connect database? (Applicable for less than 11.0 versions alone)

Connect to PostgreSQL Server in Windows

  1. Go to [SupportCenter Plus Home] \ pgsql \ bin in the command prompt.

C:\> cd ManageEngine\SupporCenter\pgsql\bin

  1. Enter the command: psql.exe -U postgres -p 65432 -h supportcenter

      • Related Articles

      • How to upgrade SupportCenter Plus instance ?

        Users who wants to upgrade the Supportcenter Plus instance needs to proceed with the following steps :  Building a test environment is must while upgrading SupportCenter Plus. It is highly advisable to try the upgrade on the test environment first so ...
      • Steps to revert the environment from an upgrade failure situation ?

        1. Rename the failed set up installation folder to <supportcenter_old> . Don't delete the installation folder until the process is completed. Download the existing version which you had before this upgrade from the below archives link. ...
      • How to restore the database of supportcenter plus in a new instance? (Applicable from 11.0 version)

        1. Find out the build number of the live server. You can know it from About Product (inside ? icon)in the top right of the user interface. 2. Download the same version from the below link     *      ...
      • Error - Sanity Failed - Upgrade from 8121 to 11

        While upgrading from 8121 to 11, after executing Updatemanager.bat and if the update fails, You need to check the Updatemanager logs in the path < Support Center Plus Application path -> Server-> Default-> Logs > .  And if you find the below ...
      • 11.0 Upgrade failure Inputs needed for analysis

        To analyze Supportcenter plus upgrade failure cases (Upgrade from 8121 - to 11.0 version), we need following types of logs. 1) If upgrade itself got failed -> need SCP\server\default\log for analysis 2) After upgrade, if the product does not start, ...