Upgrading PINsafe on Microsoft Windows
From Swivel Knowledgebase Wiki
Contents |
Overview
This document covers upgrading PINsafe on Microsoft Windows and supplements the article Upgrade PINsafe which should be used with this article.
Prerequisites
- Existing PINsafe installation on Microsoft Windows, 2000, 2003, 2008, XP, Vista, Win7
- Latest PINsafe software
- Latest PINsafe backup (requires the Tomcat service to be stopped if the internal Db is used)
- To upgrade to PINsafe 3.8 or later, you need Java 1.6. It is recommended that you update to the latest version of Java anyway.
- PINsafe 3.8 is compatible with versions of Tomcat versions 5.5 to 7.
If an external database such as MySQL or MSSQL is used make a backup of the database, since it may be modified if it was upgraded and you may need to go back to the previous version database state should something go wrong.
Moving PINsafe to another server
The steps detailed here can be used to move PINsafe to another Microsoft Windows Server. As an overview the steps required are:
- Make a copy of the PINsafe data;
- Install new instance of PINsafe, on a new server;
- Copy configuration and data files, to new PINsafe server.
See below specific information on each of these steps.
Upgrading PINsafe on the same server
The steps detailed here can be used to upgrade an existing PINsafe instance on the same Microsoft Windows Server. As an overview the steps required are:
- Make a copy of the PINsafe data;
- Remove the old instance of PINsafe;
- Install new instance of PINsafe;
- Copy configuration and data files, to new PINsafe instance.
See below specific information on each of these steps.
Microsoft Windows PINsafe Upgrade steps
Upgrade Java if required
Check what version of Java you are running. If you are on 1.5, upgrade to 1.6 or 7 - you should be able to download the latest version from the Oracle website: http://www.oracle.com/technetwork/java/javase/downloads/index.html.
If you upgrade Java, make sure that Tomcat is reconfigured to use the new version. The simplest way to do this is through the Tomcat Control Panel. If this is not already running, select Monitor Tomcat from the start menu. You may need to right-click and select Run As Administrator. Right-click on the taskbar icon and select Configure. Select the Java tab, and make sure that Use default is checked.
Make a copy of the PINsafe files
- Stop the Apache Tomcat service;
- It is highly recommended that you take a copy of the entire <path to Tomcat>\webapps\pinsafe\WEB-INF\ folder. DO NOT copy the files within the Tomcat folder, as this might cause multiple instances of PINsafe to run. Make sure the backup is outside the Tomcat root folder, and preferably on a different computer altogether for safety.
Specifically the files you will need are:
<path to Tomcat>\webapps\pinsafe\WEB-INF\conf\config.xml <path to Tomcat>\webapps\pinsafe\WEB-INF\conf\ranges.xml <path to Tomcat>\webapps\pinsafe\WEB-INF\conf\config.properties <path to Tomcat>\webapps\pinsafe\WEB-INF\data\repository.xml
- If using the database "Internal" you will need:
<path to Tomcat>\webapps\pinsafe\WEB-INF\db
- If using an external database such as MySQL or MSSQL or Oracle, ensure you take a complete backup of the database
- If you have any custom transport classes, note that classes from 3.5 or earlier are not compatible with 3.6 or 3.7. Check with Swivel Secure if there is an upgrade available. When upgrading from 3.6 to 3.7, back up any custom transports as follows:
<path to Tomcat>\webapps\pinsafe\WEB-INF\classes\com\swiveltechnologies\pinsafe\server\transport
- If the Internal, or MySQL DB is not being used, backup the DB driver file you are using from <path to Tomcat>\webapps\pinsafe\WEB-INF\lib
Remove the old instance of PINsafe
(This is only necessary if you are upgrading on the same server).
- Ensure that the Tomcat service is started.
- Delete the current pinsafe.war in <path to Tomcat>\webapps
- Wait for the pinsafe folder to disappear. If the folder still remains after 30 seconds, you may need to delete it manually, as follows:
- If the pinsafe folder has not completely gone, stop Tomcat, delete the folder and then restart Tomcat.
Install a new instance of PINsafe
Note: If moving to a new Microsoft Windows server, carry out the following install steps on the new server.
- Ensure that the Tomcat service is started.
- Copy the latest pinsafe.war file into the webapps folder and wait for the pinsafe folder to deploy;
- Once the new pinsafe instance has deployed (the pinsafe folder has been created within webapps), verify that the PINsafe server can be connected to and displays the new PINsafe version, from the local host use:
- Stop Tomcat
Copy configuration and data files
- Copy the previously made copies of the following files and folders to the new instance of PINsafe.
Note: If moving to a new Microsoft Windows Server copy from the backup to location to the new server.
<path to Tomcat>\webapps\pinsafe\WEB-INF\conf\config.xml <path to Tomcat>\webapps\pinsafe\WEB-INF\conf\ranges.xml <path to Tomcat>\webapps\pinsafe\WEB-INF\data\repository.xml
- If using the database "Internal" you will need:
<path to Tomcat>\webapps\pinsafe\WEB-INF\db
- Start Tomcat, pinsafe will startup and begin to upgrade the database configured in the config.xml
Testing
Verify that the PINsafe server can be connected to, from the local host use:
