Prepare for the Migration.
Make a Backup of the SoftSlate Commerce Database. Make a back up copy of the current 1.x application database. This is a very important step. If anything goes wrong you can restore the back up and investigate.
Please don't skip this step! Making a backup copy of the database is a very important step, because it means you can always go back to the 1.x version of the application if anything goes wrong.
Deploy SoftSlate Commerce 2.x.
Upload and Deploy SoftSlate Commerce 2.x. Upload the application file for 2.x to your staging area and deploy its contents to your application server. Follow the installation steps outlined in the installation documentation to deploy the application.
Do not run the installer tool or create an empty database. You'll be using the same database as your 1.x installation, after completing the next steps.
Update the Database and Connect 2.x to it.
Update the 1.x Database. Next, update the
database of your 1.x installation with all the new and modified database
objects of 2.x. To do this, find the
directory within the 2.x installation you just deployed. Against your 1.x
database, run all of the SQL statements in all of the
.sql files pertaining to your 1.x installation up
to and including
For example, if your current 1.x version is 1.0.9, you are upgrading to 2.0.4, and your database is MySQL, you would need to run the following files on your database, in this order:
To find out which 1.x version you are running, check the
"databaseObjects" setting in the
table of the database, or go to the
Upgrades -> Upgrades
screen of the Administrator.
As an example, for MySQL, you would run the following command to execute all the statements in one of the files:
mysql -u <user> -p <
Configure the 2.x Database Settings. Next, copy the database settings from the 1.x installation to the 2.x installation.
/WEB-INF/classes/appSettings.propertiesfile under the 1.x installation. This file contains your database connection settings.
/WEB-INF/classes/hibernate.propertiesfile under the 2.x installation. This file tells Hibernate how to connect to the database in 2.x.
hibernate.propertiesfile to the value of the "jndiContext" setting in 1.x, followed by a "/", followed by the value of the "dataSourceName" setting.
hibernate.propertiesfile. Note that in 2.x the c3p0 connection pooling library is used, and you can find documentation for it by visiting the c3p0 web site.
appSettings.propertiesfile under the 1.x installation, find the value of the "twoWayKeyFile" setting. If you are using two-way encryption for passwords or payment information, you need to find this key file on the server and copy it to your 2.x installation, so the application can use it to decrypt existing information.
/WEB-INF/classes/appSettings.propertiesfile under the 2.x installation. Although
hibernate.propertiesstores the database connection settings, this file still holds some important settings in 2.x.
appSettings.propertiesfile under the 2.x installation to point to the file's location, so the application can find it.
appSettings.propertiesfile under the 1.x installation to the
appSettings.propertiesfile under the 2.x installation to "npc". (In 2.x, the database tables are prefixed with ssc by default instead of npc, but you may change the prefix by modifying this setting. Since you are using the same database as 1.x, the prefix should be set to npc.)
Start and Test the 2.x Application. You should now be able to start the 2.x application from within your Java application server. For example, if you are using Tomcat use the Manager application to run the start command:
Test the application to make sure it can connect to your database. You should see the application come up, but without any of the customizations you made to 1.x.
Incorporate 1.x Customizations into the 2.x Installation.
For some suggestions and guidelines on incorporating your 1.x customizations into 2.x, please refer to the following section of this guide.