Updating Salesware Modules

Transcription

1 Updating Salesware Modules Version 4.4 accesso 302 Camino de la Placita Taos, NM

2 Copyright Copyright 2015 accesso Technology Group, plc. All rights reserved. NOTICE: All information contained herein is the property of accesso Technology Group, plc. No part of this publication (whether in hardcopy or electronic form) may be reproduced or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written consent of accesso Technology Group, plc. The software, which includes information contained in any databases, described in this document is furnished under a license agreement and may be used or copied only in accordance with the terms of that agreement. This publication and the information herein is furnished AS IS, is subject to change without notice, and should not be construed as a commitment by accesso Technology Group, plc. accesso Technology Group, plc. assumes no responsibility or liability for any errors or inaccuracies, makes no warranty of any kind (express, implied, or statutory) with respect to this publication, and expressly disclaims any and all warranties of merchantability, fitness for particular purposes, and non-infringement of third party rights.

3 INTRODUCTION... 3 The basic process for updating Salesware version 4.4 modules is the following:... 3 UPDATE PLANNER... 4 DOWNLOADS... 4 UPDATE PREREQUISITES... 4 CLOSE ALL APPLICATIONS... 5 BACK UP DATA... 5 To make a copy of your SiriusSQL database:... 5 SET THE DATABASE COMPATIBILITY LEVEL... 6 RUN SQL SERVER UPDATE SCRIPT... 7 CREATE A TEMPORARY DOWNLOADS FOLDER... 8 DOWNLOAD UPDATE FILES FROM THE ACCESSO WEB SITE... 8 INSTALL MODULE UPDATES FROM DOWNLOADS FOLDER... 9 UPDATING MIDDLEWARE UPDATING THE INSTALLERS UPDATING INDIVIDUAL COMPUTERS RESET MAXKEYS ON THE SERVER UPDATING E-COMMERCE MODULE Two steps are required to update E-Commerce module: Updating ww.dll To update your existing ww.dll to the new version:

4 Updating E-Commerce Pages To Perform a bin change update: UPDATING ZIP CODES Salesware module uses zip codes for two purposes: To update zip code data on your server (used by SysManager): To update the zip code data on your local salespoints: APPENDIX A: UPDATE FILES MUST BE DIGITALLY SIGNED

5 Introduction This document describes the process for updating Salesware version 4.4 modules. When a new version of software is available clients are notified by . If you are updating to Salesware version 4.4 from 4.3, please see the What s New in 4.4 documentation for complete updating instructions. Important: As indicated in the table at the end of this document (in the section Install module updates from Downloads folder), clients with the Rentals, E-Commerce and Print At Home Tickets modules need to contact accesso Siriusware Technical Support to perform special steps to update those modules. If you use these modules, please call accesso Siriusware Technical Support before initiating any updates to Salesware (even updates to other modules). Note: If you use replication, please contact accesso Siriusware Technical Support to help with your update. Replication can be complex and every client who uses it can have a different situation. Note: As indicated in the table at the end of this document (in the section Install module updates from Downloads folder), clients with TallyMan and/or ScanMan modules need to consult the Salesware Retail (TallyMan) and/or Salesware Access Control (ScanMan) documentation to perform their updates. For convenience, you can install your new TallyMan and ScanMan software before taking your site offline and performing the other updates described in this document. If you use TallyMan and/or ScanMan modules, you can skip to the Create a temporary Downloads folder and Download update files from the accesso web site sections of this document and download the TallyMan and/or ScanMan update files first. For complete information on all Salesware modules and their methods of installation and updating, see the Salesware Modules, Licensing and Maintenance document, available from The basic process for updating Salesware version 4.4 modules is the following: 1. Shut down all Salesware applications. 2. Verify you are on SQL Server Version 2008 or newer. 3. Back up your data! 4. Set Database Compatibility level 5. Run any database update scripts 6. Download the files necessary for an update. 7. Install.NET Place the update files in the on the computer where SQL Server resides. The default path to the is C:\Siriusware\Updates. 9. Update installers 10. Update Middleware 11. Update individual computers 12. Reset Maxkeys on Server 3

6 13. Check SysManager Global.INI path settings 14. Re-start the Salesware applications. These steps are detailed in the sections that follow. As part of their startup procedure, the Salesware loader programs checks to see if new updates exist in the. If new updates are found, the updates are installed and the new versions of the programs are launched. To the Salesware user, the update process is transparent. Update planner This planner is designed to prepare and alert you to significant steps that are necessary prior to installation. This pre-planning helps ensure the success of your accesso upgrade. 1. Do you have a current version of Microsoft SQL server? The most current version is SQL Server We recommend this version for all accesso clients upgrading to version Custom Reports and Integrations: Any update to the software can affect custom integrations or reports. Known potential problems are detailed in our Known Issues documentation. We are not aware of any other issues at this time. Please note that any work required to update your custom reports or integrations to function with new versions is not covered under any support contract and would be billable. Please provide this information to accesso when you call to schedule your update. Downloads When a new version of software is available, clients are notified by . This provides information on updating as well as links to the updates and necessary documentation. accesso provides each client with an account on the accesso Siriusware Information Portal ( The portal provides access to the most current software versions for a client s particular implementation. Each client is provided with a unique log-in id and password to access the portal. From the portal, clients access the downloads they need to update. Please call accesso Siriusware Technical Support with log-in and password questions. Update prerequisites All updates should be completed during off-hours. All modules with updates should be updated simultaneously to avoid version conflicts. TallyMan and ScanMan modules are exceptions. They do not use the, so can be updated before or after the other updates. If you are updating E-Commerce module, the steps described in the section Updating E-Commerce should be performed after you update the other modules. Follow the steps in the order presented in this document. If you experience difficulties with any part of your update, please call accesso Siriusware Technical Support. 4

7 Close all applications Shut down all Salesware applications. Note: With version 4.4, Salesware module supports a number of new Windows services for Middleware and other functions. You do not need to shut down these services when updating. The services are updated behind the scenes when they are invoked and an update has already been placed in the Updates folder. The accesso Siriusware Update Service was added for Salesware module to provide this functionality. You can see it running in Windows services but it functions in a way that is transparent to the user. Back up data Before updating, it is important to make a backup of your existing SiriusSQL database. More information on creating full database backups and differential backups is provided in the Salesware Modules, Licensing and Maintenance document. To make a copy of your SiriusSQL database: 1. Go to your SQL Server. 2. Open SQL Server Management Studio (SQL Server 2008 and 2012) and drill down into the folders until you get to the Databases folder (Microsoft SQL Servers > SQL Server Group > Local > Databases by default in Enterprise Manager and one level below the root in Management Studio). 3. Highlight the SiriusSQL database and right-click. Select Tasks > Back Up (Management Studio). 4. On the dialog that is displayed, select SiriusSQL in the Database: dropdown. 5. Select the Database Full in the Backup Type: dropdown. 6. In the Destination area click the Add button and the Select Backup Destination dialog is displayed. 7. If backing up to the hard drive, select the Filename: radio button. (If backing up to another device, select the Backup device: radio button.) 8. The default location for backing up to the hard drive is filled in the box (usually it is C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\). You can use this default or click the ellipsis ( ) to browse to another location. 9. Enter a name for the backup file after the backup location path in the Filename: field and click OK. 10. Verify that the Append to media radio button is selected in the Append to the existing backup set radio button is selected in the Overwrite media section on the Options page. Note: You can select Overwrite if you are running low on hard disk space on the drive where you are backing up. It s not absolutely necessary to select Append. Each time you back up with Append, you preserve the old backup set and create a new backup set in the same backup file. If you then need to Restore, you can select the latest backup or a previous backup. Sometimes clients are confused by this step and accidentally restore the wrong backup. Typically, you just need to restore the latest backup, so always selecting Overwrite is sufficient and saves hard drive space. But that is totally your option. 5

8 11. Click OK and the backup operation commences. 12. When the backup is complete, you get a message that the backup was successful. Click OK. 13. Exit Management Studio. Note: It is vital that data and other important Salesware files are backed up daily during off-hours. If a catastrophic event (such as server crash, theft or fire) occurs, this makes restoring the system possible. Note: Before they update, some clients run a Period Sales Report for a recent time period, for example, the current season or the last six months. This report is printed as a PDF so it can be compared to the same report (using Adobe Reader or Adobe Acrobat) after the update. This check is especially useful if you had to restore a backup (to ensure that the restore worked properly). Only allow salespoints to reconnect after you know the numbers are good. Set the database compatibility level 1. In SQL Studio Manager, Right Click on the SiriusSQL database in SQL Management Studio and choose Properties. 2. Click on Options on the left side of the dialog. If you are running SQL Server 2008 you can select SQL SQL Server 2008 (100) click on OK to save. Note: If it was already set correctly simply click OK 6

9 Run SQL Server update script For some updates, accesso provides a database update script. This SQL script is run from the Microsoft SQL Server Management Studio (SQL Server 2008 and 2012) and updates your SQL Server database so that it complies with the latest version of SiriusSQL application. For more information on how to run this script, see Salesware Modules, Licensing and Maintenance, available from The modules that are updated in the next step in this document may use new fields and other changes made to the database by a database update script. In some cases, you may be required to run more than one database update script. If this is the case, it is specified in the update notice. Note: The SQL Server update script cannot be run until you back up your database as described in Back up data. You get an error message if you try to run it without creating a backup (at any time earlier that day). You do not, however, get an error message if you are updating your training database and you fail to back it up. 7

10 With everyone out of the accesso Siriusware System go ahead and run the 4.4 SQL update script(s). Once the script(s) finish running, verify that the results at the bottom of the SQL query window indicate that the script completed WITHOUT errors. Note: If you see any errors at all, STOP and call accesso Siriusware Technical Support as the database backup must be restored immediately. Create a temporary Downloads folder A temporary destination folder for the downloaded software files needs to be created. Note: Veteran Salesware module updaters may choose to download directly to the. Create the folder in C:\Siriusware\Updates on the database server and name it Downloads. Note: If shared Salesware files are in a location other than C:\Siriusware\ on the database server, put the Downloads folder there instead. Placing the files in this location makes copying the files easier. accesso recommends that files be downloaded first to this folder. Once each downloaded file is moved to the (see Install module updates from Downloads folder), the contents of Downloads are deleted so that it is clean for the next downloading session. Download update files from the accesso web site Note: Please call accesso Siriusware Technical Support with questions about the download process. Using an Internet Explorer or Firefox browser, navigate to the accesso Siriusware Information Portal at Click Log-in and enter your Username and Password. Click the Log-in button. Information regarding the update and all core Salesware downloads are available, after you log-in, from the Downloads > Updates > 4.4 Salesware menu. Downloads specific to your site are available from Downloads > Updates > 4.4 Optional modules. (Access to downloads of optional modules is handled on a client-by-client basis, so ensure that you can access all of the updates for the modules that you use. Contact accesso Siriusware Technical Support if there are any discrepancies.) Using as a reference the that you received from accesso, download the updates that correspond to the modules deployed at your site. If you have questions about what any of the files are used for, consult the Salesware Modules, Licensing and Maintenance documentation at 8

11 Exit the browser and navigate to the Downloads folder. Verify that the files necessary for all of the relevant module updates are located there. If any of the files is missing, the download process needs to be repeated for the missing file. Note: When downloading each file, ensure that the entire file gets downloaded. Install module updates from Downloads folder The following table lists Salesware modules/products and their methods of update. Note: If there is not an update for a particular module/product, then it is not listed in the notification . Not all modules/products are updated with every update from accesso. Nearly all products are updated using the. As already noted at the beginning of this document, clients with the Rentals, E-Commerce and Print At Home Tickets modules need to contact accesso Technical Support to perform special steps required to update those modules. If your installation includes Rentals module, be sure you consult with accesso Siriusware Technical Support before updating any of your modules, as described in this section. Clients with TallyMan and/or ScanMan modules need to consult the Salesware Retail and/or Salesware Access Control documentation available from to perform installations for these modules. For complete information on all Salesware modules and their methods of update and installation, see the Salesware Modules, Licensing and Maintenance document, available from Module/product Ticketing Membership/Passes Instructor Payroll Private Instruction Activity/Facility Scheduling Charge Cards In-House Cards Folio Charge Quick Service Food and Beverage Table Service Food and Beverage Access Control Reservations Method of update 9

12 Module/product Tee Sheet Kiosk Gate Access (GateKeeper) Retail MessengerService Reserved Seating (RSWebApp) Resource Scheduling ww.dll Mobile Sales Rentals E-Commerce (including Print At Home Tickets) Handheld Access (ScanMan) Handheld Retail Inventory (TallyMan) Method of update Download app from Apple itunes Store Contact accesso Siriusware Technical Support Contact accesso Siriusware Technical Support See Salesware Access Control document See Salesware Retail document Copy the downloaded software update files from Downloads to the. The default location for this folder is C:\Siriusware\updates. Restart all Salesware applications: Pool Service, salespoints, ReportManager, SysManager, Gatekeeper, etc. Updating Middleware 1. Make sure you are logged in the computer as an Administrator. Note: It is necessary to update Pool Service application each time a new version of Pool Service is installed. In order to update Pool Service application please follow the instructions listed below. 2. Disconnect all salespoints from the Middleware. 3. Put c_poolservice_4400.xxxx.exe into your Updates folder 4. On your middleware server, go to any of the Update Pool icons that are now is installed on the desktop by the Pool installer in Salesware 4.4 module. 5. Double-click on any of the Update shortcuts (Update BookEZ, Update SalesEZ, etc.) -- you need to do this to cause the Salesware Update Service to kick in and update the Pool Service application itself, even though you didn't need to update SalesEZ, BookEZ, etc., applications. 10

13 Note: Be sure to include the c_s_misc.exe file for zip codes for Sales. Service Monitor (c_servicemonitor_xxxx.exe) is used to monitor Middleware. Updating the installers 1. Delete all the existing accesso Siriusware application installation files from the server in C:\Siriusware\Install 2. Copy the new Siriusware 4.4 installers into this same folder Updating individual computers 1. Launch each accesso Siriusware application installed on that computer and it updates the application automatically. Reset Maxkeys on the server 1. In SysManager > Utilities > select Data Maintenance > select MaxKeys on Server Updating E-Commerce module Your E-Commerce site needs to be updated at the same time as the rest of your applications. This must be scheduled in advance and requires a minimum of two weeks lead time and possibly longer depending on the number of current requests already in the queue. Two steps are required to update E-Commerce module: 1. Update ww.dll This is a generic update that can be used for any release of ww.dll. 2. Update the pages This update is specific to each release of E-Commerce module. Note: The version of ww.dll that you are using and the version of the pages that you are using need to match. Updating ww.dll To update your existing ww.dll to the new version: 1. Download the c_ww_440x.xxxx.exe file and place in your Downloads folder. 2. Move this file into the C:\Program Files\Siriusware\. 3. Click on the Update ww.dll icon shortcut on the desktop 11

14 Updating E-Commerce Pages To Perform a bin change update: 1. Download and run Ecommerce_pages_xxx.xxxx.exe. 2. Choose or create a temporary folder to unzip the files. Note: Do not unzip them directly into your live web site at this time. 3. Back up (Copy) the files in your /bin directory for your web site. Repeat this process for all web sites you want to update. 4. Copy and replace all files under the /bin directory in your temporary folder to the /bin directory in the root of your web site. Repeat this process for all web sites you want to update. 5. Reset IIS. 6. Test the web site. Look for the new version in about.aspx, and delete the temporary files once you have validated the site. Updating zip codes Salesware module uses zip codes for two purposes: 1. To provide auto-population of City and State fields when inputting data (these fields are auto-populated when you tab through those fields to the Zip code field and type in the Zip code.) 2. To validate that correct Zip codes are entered (this capability must be configured by using the ValidateZip.INI setting at the salespoint.) Zip codes (and their corresponding cities and states) are stored on the server and in local salespoint data (Zipcode.cdx and Zipcode.dbf). Zip code update files are available from the accesso Siriusware Information Portal (Downloads > Updates > 4.2 Zipcodes). To update zip code data on your server (used by SysManager): 1. Download the Utility to update zipcodes for SiriusSQL (Update_Zipcodes_4200.exe) and unzip it to a folder on your SQL server. 2. Run the utility on your SQL server (an installer program starts), select your database(s) (SiriusSQL, SiriusSQL_Training or one you can specify) and follow the prompts. Note: The utility requires osql.exe, which is installed with SQL server. Note: This utility deletes any zip codes that do not exist in the new zip code table that you are installing. If you added your own custom zip codes to the SQL database, you may lose them. 12

15 To update the zip code data on your local salespoints: 1. Obtain the appropriate c_s_misc.exe file from the accesso Siriusware Information Portal (U.S. only, US/Canadian, Australian, etc.) 2. Put the c_s_misc.exe into your, over-writing the old version. 3. Re-start Sales on each salespoint. If the date on the c_s_misc.exe file in the is later than the date on the c_s_misc.exe file currently in the local Siriusware\Sales directory, and then, the new c_s_misc.exe is copied to the salespoint, overwriting the old c_s_misc.exe file. Sales executes c_s_misc.exe, overwriting the Zipcode.cdx and Zipcode.dbf files in the Sales\Data directory. Note: Double-check to ensure that the above step completed. If the Zipcode.cdx and Zipcode.dbf files are not the latest, yet the new c_s_misc.exe was copied into the Siriusware\Sales directory, and then, simply execute (double-click on) c_s_misc.exe and the new files are written into the Sales\Data directory. Note: When local data is deleted and rebuilt at a salespoint (this is done sometimes to re-initialize the data at a salespoint), the Zipcode.cdx and Zipcode.dbf files are empty. You must double-click on the c_s_misc.exe file in the Sales directory to copy the zip code files into the Sales\Data directory. Appendix A: Update files must be digitally signed With 4.4, Salesware module requires all update files to be digitally signed. Also note that on Windows Embedded systems you may have to actually view the certificate for the file that Runexe application is trying to unzip before you can actually install and accept it. The root certificate authority (CA) on the accesso Siriusware certificate, when not in Windows list of trusted root CA s, can cause errors in the Runexe log. You can see whether this is listed by right-clicking on the downloaded c_xxxxxxxxxx.exe and entering properties, going to the Digital Signatures tab, highlight the accesso Siriusware signature and clicking Details: 13

16 Selecting View Certificate and going to the Certification Path tab shows the details of the certification chain: 14

17 This illustrates that Windows hasn t received the updated official list of trusted CA s distributed by Microsoft. After checking Update Root Certificates here and installing that feature, you are able to run accesso Siriusware applications. More information on the issue, including help for other versions of Windows, is available here: Microsoft actually recommends having your own trusted certificate store on your network and not configuring every individual box to automatically update root certificates. However, for now, we are enabling this at salespoints and also researching ways of getting around going back to every salespoint and installing this feature. 15