How to build a test environment for ServiceDesk Plus
- Building a test environment is very helpful while upgrading ServiceDesk Plus. When you are planning to upgrade ServiceDesk 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.
Step 1: Stop Manage Engine Service Desk Plus service on the production server.
Step 2: From command prompt, go to [SDP-Home]\bin directory and execute backUpData.bat command to start the data backup. Where, [SDP-Home]-> Drive:\ManageEngine\ServiceDesk
Once the backup is complete, a backup file with .data extension is placed in the Backup folder under ServiceDesk Plus Home directory. This backup file contains information such as the Build number of ServiceDesk Plus, and the date and time of when the backup was performed. Here is the format of the backup file.
"Backup_ ServiceDesk_ [Build number] _Month _date _ Year _ Hour _Minutes"
For example, a backup taken in Version 9 and Build 9213 of ServiceDesk Plus looks like this
Step 3: Install ServiceDesk Plus on the new server.
Data can be restored only to the same builds of ServiceDesk Plus version. (i.e.) data backed up in 9213 build of ServiceDesk Plus can be restored only in 9213 build. Please check if the old build and new build are of same build versions.
Build version can be checked,
- By clicking on the About link in the application. [OR]
From buildInfo.xml file under [SDP-Home]/server/default/conf directory.
If you are going to use the production MSSQL server for the test instance too, then invoke ChangeDBServer.bat from [SDP-Home]/bin directory and create a new database(say servicedesktest) as the default database name(servicedesk) may point to the production database running. Once new database is created, start and stop the application once so tables will be created.
Step 4: Copy the backup taken from the production server to the Test server.
Step 5: To restore the backed up data, Go to [SDP-Home]\bin directory and execute restoreData.bat. Choose the backup file while prompted as in the screenshot given below,
cmd> restoreData.bat >out.txt
out.txt is a file redirected to bin directory which will store the restore activity, it helps us to analyse in case restore fails.
- Step 6: Click 'No' when it prompts for a user input to choose whether it's the production server restore you are trying to do, by saying 'No' it will disable Mail fetching, Sending activities automatically.
Step 7: Start the ServiceDesk Plus server once after restoring the data in the Test server and log in to check if everything looks fine.
How to setup Python on the Server
This article explains how to set up the ServiceDesk plus server to run python scripts. 1. The first step is to install python on the application server and you can download it from here . Any version above 3.4.1 should work fine. Start the setup and ...
How to update ServiceDesk Plus to the latest version
1: Stop the ManageEngine ServiceDesk Plus service from the Services console(services.msc). 2: Backup the existing build (recommended). Launch the command prompt, go to [your drive]:\ManageEngine\ServiceDesk\bin directory, and run the backUpData.bat. ...
How to restore your data in ServiceDesk Plus
1. Stop the ManageEngine ServiceDesk Plus service from the Services console(services.msc). 2. Click the Windows icon and select Command Prompt (Admin). 3. Go to Bin directory and run restoreData.bat 4.Browse to the backup file from backup ...
How to integrate ServiceDesk Plus with DesktopCentral
Log in to ServiceDesk Plus 1. Go to Admin>>General Settings >>ME Integrations. 2. Click Desktop Central 3. Provide the Desktop Central server name and port number. 4. Generate the API key from DesktopCentral. 5. Click Test Connection and Save. Log ...
How to integrate ServiceDesk Plus with OpManager
Log in to ServiceDesk Plus. 1. Go to Admin>>General Settings >>ME Integrations. 2. Click on OpManager. 3. Provide the OpManager server name, port number, and protocol information. 4. Click Test Connection and Save. Log in to OpManager. 1. Go to Basic ...