Migrating from Bacs.IP to SmarterPay

Size: px

Start display at page:

Download "Migrating from Bacs.IP to SmarterPay"

Gary Bailey
6 years ago
Views:

1 Migrating from Bacs.IP to SmarterPay

2 Copyright Data Interchange Plc. All rights reserved. No part of this document may be disclosed to third parties or reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written permission of Data Interchange.

3 Table of Contents 1 Introduction Notes On Operation Remote SQL Servers Variants of the Product Bundler tool: Version Version Backup Guides Local backup step by step Backup with external SQL step by step Restore Guides Fresh Install Local restore step by step Restore with external SQL step by step... 12

4 1 Introduction The Data Interchange Product Bundler is a utility that is intended create a backup bundle containing the necessary configuration files so that it is possible to upgrade to SmarterPay from BACS.IP, without having BACS.IP installed on the new PC. With the new requirements from SmarterPay and BACSTEL, it may not be possible to directly upgrade from BACS.IP to SmarterPay as BACS.IP may not work correctly on Windows 8 and higher and SmarterPay will not install on Windows XP. Whilst the below instructions are in a step by step format there are likely to be some variables in your configuration and you will require some knowledge of your current setup configuration. If you need any help when following the steps below please contact us and we will be happy to assist you. Backup BACS.IP Restore BACS.IP on new PC Upgrade BACS.IP to SmarterPay Process Overview Page 1

5 2 Notes On Operation 2.1 Remote SQL Servers When running the backup tool and the source database is on a remote SQL Server, it will create a backup data file locally on that remote SQL Servers local drive. This occurs whether the backup is done using SQL Management Studio or the DI SQL Backup utility. The SQL will not backup or restore over a network drive. The drive letter and directory specified in the SQL backup are always assumed by the Microsoft software to be on the SQL machine and therefore not necessarily on the local PC. All restores of SQL databases will need to be done manually using SQL Server management or using the DI SQL Backup utility. If you have any issues with this please contact us and we will be happy to help. 2.2 Variants of the Product Bundler tool: Version 2.0 Version 2.0 is intended for use on PCs running Windows XP with.net 2.0 installed. It can access databases up to and including SQL This Version is the typical version that will be used if backing up BACS.IP on Windows XP but will require Version 4.0 on the new machine when restoring the configuration Version 4.0 Version 4.0 is intended for PCs that have.net 4.5 installed and is able to access SQL servers up to and including Otherwise there are no differences. Page 2

6 3 Backup Guides BACS IP is able to be installed in two different configurations: Both the application and SQL database on the same machine or the application on one machine with the SQL database on a separate machine. The Product Bundler can copy and move both configurations but some manual action is required if we are dealing with a remote SQL instance, as SQL will not backup or restore over a network drive. This section contains step by step instructions on how to back up the application configuration and database for both scenarios. 3.1 Local backup step by step If your SQL instance is installed on the same machine as the application, you can begin by launching the DataInterchangeProductBundler.exe You will be asked to select the product that you are wanting to backup. Select BACS.IP and click next Select the instance of BACS.IP and click next Select the content you want to restore and a location to save the backup bundle to. Click next and the operation will complete successfully. Page 3

7 You will now have all the data backed up in a.dbak file. This package contains all of the application configuration, database files and any log files needed to restore the product to SmarterPay. You can now copy this folder to the machine where the SmarterPay upgrade will be taking place and proceed to restore the package. You can now advance to the Restore Guide. 3.2 Backup with external SQL step by step If your SQL instance is installed on a separate machine from the application you can begin by launching the DataInterchangeProductBundler.exe You will be asked to select the product that you are wanting to backup. Select BACS.IP and click next Select the instance of BACS.IP and click next Page 4

8 Select the content you want to restore and a location to save the backup bundle to. The backup process will start and you will be prompted to copy the backup of the SQL database that has been created by bundler to the machine that you are hosting the application from. Retrieve a copy of the database backup from the remote machine and copy it to the local machine. Browse to the file from within the bundler application and click OK. You will now have all the data backed up in a.dbak file. This package contains all of the application configuration and database files and any log files needed to restore the product to SmarterPay. You can now copy this folder to the machine where the SmarterPay upgrade will be taking place and proceed to restore the package. You can now advance to the Restore Guide. Page 5

9 4 Restore Guides BACS.IP is able to be restored in two different configurations: The application with the SQL database on the same machine or the application on one machine with the SQL database on a separate machine. This section contains step by step instructions on how to restore the application configuration and database for both scenarios. 4.1 Fresh Install Locate the SmarterPay Installer software and open the executable. Once the installer opens, the End-User Licence Agreement (EULA) will appear. This details the terms and conditions of the application usage and will need to be accepted to progress through installation. Once this EULA is accepted, the extraction window will appear. This will extract the installation files to a temporary directory for installation shortly afterwards. These files are extracted to the Program Files directory and will require administrative access to your PC. This may cause the below User Account Control (UAC) warnings to appear. It is required that permission is given to SmarterPay to extract these files. Page 6

included with SmarterPay).NET Framework 4.

10 Once the files have finished extraction, the installation wizard will begin by checking for any missing pre-requisite software. The pre-requisite software for the current version of SmarterPay is: Microsoft C Run-Time Libraries (Included with SmarterPay) SQL Server 2012 (Express edition is included with SmarterPay).NET Framework 4.5 Signing software (Provided by sponsoring bank) Once the pre-requisite software has all been installed, you will be provided with the options of what clients or server to install. If SQL Server 2012 is already installed on the required machine, you may opt to not install SQL Server 2012 express. Click continue to progress to installation. Page 7

Once you click Finish, SmarterPay will have been installed and you can progress to either Local

11 SmarterPay will now install all chosen components, clients and the server if requested. Note that SQL Server Express may take a long time to install depending on the system configuration. Once you click Finish, SmarterPay will have been installed and you can progress to either Local Restore (where SQL Server is on the same machine) or Remote Restore (where the SQL server is on a different machine). Page 8

12 4.2 Local restore step by step Launch DataInterchangeProductBundler 4.0.exe Select Restore and click Next Browse to the backup file that we created in earlier steps when we packaged the old system and click Next. Select the data that we wish to restore and select the location to output the data to and select Next. Page 9

extracted files we need to import to SmarterPay.

13 You will be advised that the database does not exist and will be created, select yes to continue Select yes to proceed with the restore operation The restore will complete and a folder will have been created with all the extracted files we need to import to SmarterPay. Run the SmarterPay Setup Wizard Select to upgrade from an earlier version and click Next Select the earlier version of the product that we are going to be upgrading from and select Next Page 10

14 Confirm the summary of the upgrade and select next You will be warned that the upgrade will begin, select yes and the data will copy from the backup to the new machine. The copy will complete successfully and you are ready to start SmarterPay with all your original settings transferred from the old BACS.IP system Page 11

15 4.3 Restore with external SQL step by step Perform a fresh install of SmarterPay Launch DataInterchangeProductBundler 4.0.exe Select Restore and click Next Browse to the backup file that we created in earlier steps when we packaged the old system and click Next. Select the data that we wish to restore and select the location to output the data to and select Next. Page 12

When restoring to an external SQL server we will be advised that the restore is being done remotely and we will need to

$we can import the file into SQL For this example we will copy the file to the remote SQL server on C:\temp We now need to run$ SQL Server Management Studio to restore the database to a new SQL Instance.

SQL Server Management Studio to restore the database to a new SQL Instance.

16 When restoring to an external SQL server we will be advised that the restore is being done remotely and we will need to select a location locally to extract the backup of the database to and move that manually to the remote machine. We will be advised to click next once the restore is completed We now need to copy the backup file to the SQL server so that we can import the file into SQL For this example we will copy the file to the remote SQL server on C:\temp We now need to run SQL Server Management Studio to restore the database to a new SQL Instance. Ensure that the new database name entered here matches the database name we chose earlier in the bundler. If you have any issues with this please contact us and we will be happy to help. Page 13

Select yes. You will be asked again if you wish to proceed, select yes.

17 Once we have restored the database we can return to the application server and select next to continue with the restore. We will be warned that the database already exists and is this the database we wish to update. Select yes. You will be asked again if you wish to proceed, select yes. The restore will complete and a folder will have been created with all the extracted files we need to import to SmarterPay. Run the SmarterPay Setup Wizard Page 14

from and select Next Select the earlier version of the product that we are going to be

18 Select to upgrade from an earlier version and select Use advanced options for the database and data files Select the earlier version of the product that we are going to be upgrading from and select Next Select the earlier version of the product that we are going to be upgrading from and select Next Enter the details of the remote server and enter a new database name Page 15

19 You will be warned you are creating a new database and do you wish to continue, select yes. Confirm Summary and select Next The copy will complete successfully and you are ready to start SmarterPay with all your original settings transferred from the old BACS.IP system The copy will complete successfully and you are ready to start SmarterPay with all your original settings transferred from the old BACS.IP system Page 16

20 Page 17 Migrating from Bacs.IP to SmarterPay

Setup and Reconfiguration Guide

EPIC Setup and Reconfiguration Guide VM-0001-07 Copyright Data Interchange Plc Peterborough, England, 2012. All rights reserved. No part of this document may be disclosed to third parties or reproduced,