NewHaven Software Wiki - User contributions [en]

Enabling Log Truncation

2019-06-18T05:02:33Z

Luke steinmetzer: Created page with '=Overview= The CMS Database is a sybase database that runs with a Transaction log. This log is used by the database for a varity of reasons, but as a result can get rather large…'

=Overview=

The CMS Database is a sybase database that runs with a Transaction log. This log is used by the database for a varity of reasons, but as a result can get rather large.

To help ablivate this problem you can enable a feature called "Truncate the log" This will slim down the log as it will only contain the last days worth of transactions, and as a result ensure that your log does not take up more space then needed.

To enable this feature please follow the instructions below.

=Enabling Log Truncation=

* Step 1: Log into your PCI Administrator account.

* Step 2: Select PCI Administration at the top

* Step 3: Select Administration

* Step 4: Select Daily Backup

* Step 5: Check mark the Truncate the Log box

* Step 6: Select Save These Settings Now
==Subtitle 1==
=Header 2=
=Header 3=

[[Category:Blank]]

Server Update

2019-06-06T08:18:21Z

Luke steinmetzer:

=Overview=

This article details the instructions for updating CMS to version 8, 9 and 10.

=Preparing for the Installation=

Before you begin installing or updating your Server please review the list below.

==Server System Requirements==
To verify that your system meets CMS system requirements please review: http://wiki.newhavensoftware.com/index.php/CMS_System_Requirements#Servers

== Updating reports ==

If you are updating to CMS version 10 from CMS version 8 or older and you use custom CMS forms or crystal reports. We may need to update those reports. Please contact support@newhavensoftware.com directly so we can review this with you.

==Backing up CMS==

Below is information about backing up your CMS information before updating.

===Creating backups when updating from CMS 7 to 8===

When updating CMS from version 7 to 8 it will automatically create the following Backups in your NewHaven Software directory:
*A backup of your database is added to your Data folder as (name of your database).bak
*All of your CMS Reports are zipped up and added to the Reports folder as Reports-backup.7z

If you need access to the backup file, just rename the .bak extension to .db

If needed you can unzip your reports with the free software program 7 zip. You can download this from the link below
http://www.7-zip.org/

===Creating backups if doing a CMS 8 or later update===

Before updating CMS to a new version of 8 or 9, you will want to create a Database backup. To do this please review the instructions in the link below.
http://wiki.newhavensoftware.com/index.php/Creating_a_Database_Backup

==Download the CMS Installer==
Please visit http://updates.newhavensoftware.com/
For information on using the update page and downloading the installer please review the video : http://youtu.be/dBbd94k7b0A

==Time to Update the Server==
Please note: If you are updating CMS 7 to 8, that due to the upgrade from Sybase ASA 8.0.2 to Sybase SQL Anywhere 12.0.1, the server update can take longer then normal. While time to do this is extremely variable, we recommend planning for 2 hours of downtime. Newer versions of CMS can typically be updated in roughly 1 hour (possibly longer depending on the size of the database).

==Workstation Updates==
'''Note: If you are updating CMS 7 to CMS 8, you will be required to run a Workstation update on all of your CMS Workstations. This is because your Workstations will require a new ODBC driver to function. If you do NOT do this, your workstations will not function.'''

For information on this process please click the link below. http://wiki.newhavensoftware.com/index.php/Workstation_Install

==Release Notes==
Please take your time to review our release notes after an update. You can do so by clicking on the link below https://updates.newhavensoftware.com/release_notes.htm

=Server Update=
Note: Once you have verified that you meet the above prerequisites, follow the instructions below to Update your Server.

*'''BEFORE GOING ANY FURTHER PLEASE MAKE SURE EVERYONE IS LOGGED OUT OF CMS'''

To begin double click the CMS installer, then follow the screenshots shown below.

[[image:Serverupdate1.png]]

[[image:Serverupdate2.png]]

[[image:Serverupdate3.png]]

[[image:Serverupdate4.png]]

[[image:Serverupdate5.png]]

[[image:Serverupdate6.png]]

[[image:Serverupdate7.png]]

[[image:Serverupdate8.png]]

[[image:Serverupdate9.png]]

 

After following these instructions you should now be able to sign into CMS.

Folder sharing in Windows

2019-06-06T08:10:28Z

Luke steinmetzer:

Below are instructions on how to both share a folder in Windows and disable those shares.

NOTE: These instructions are for a 3rd party operating system created by Microsoft, Microsoft has no affiliation with either NewHaven Software or our software CMS. If you have any questions or issues with the below instructions please contact Microsoft directly at http://www.microsoft.com/

==How to share a folder==
===Vista / 7 / Server 2008===

1. Right click on the folder you wish to share.

2. Select Proprieties

3. Select the Sharing tab at the top

4. Select "Share" under Network File and Folder Sharing

5. On the "Choose people on your network to share with" window that comes up select who on your network you wish to have access to this folder. You will need to make this selection based of what your network requires to remain secure. However CMS does require that all Workstations have both Read and Write access to the NewHaven Software directory to function.

6. Select "Share"

===Windows XP===

1. Right click on the folder you wish to share.

2. Select Proprites

3. Select the Sharing tab at the top

4. Select "Share this folder"

5. Select "Permissions"

6. Set the permissions you wish to have for this folder. You will need to make this selection based of what your network requires to remain secure. However CMS does require that all Workstations have both Read and Write access to the NewHaven Software directory to function.

==How to disable a shared folder==

===Vista / 7 / Server 2008===

1. Right click on the folder you wish to share.

2. Select Proprieties

3. Select the Sharing tab at the top

4. Select "Advanced Sharing"

5. Remove the checkmark "Share this folder"

6. Select ok

===Windows XP===

1. Right click on the folder you wish to share.

2. Select Proprieties

3. Select the Sharing tab at the top

4. Select "Do not share this folder"

===Windows 10===

1. Please review the official Microsoft documentation at:

https://support.microsoft.com/en-us/help/4092694/windows-10-changes-to-file-sharing-over-a-network

Dazzle

2018-06-19T17:11:43Z

Luke steinmetzer:

=Endicia Account Creation=
Here is a link to setting up a new account with Endicia's Dazzle Softwarare - https://account.endicia.com/?billingtype=PM&referredby=pnhv

This link also automatically prompts you to sign up at the proper subscription level (Premium, currently 15.95/mo).

=Configuring CMS for use with Endicia/DaZzle=
# To access the Shipping Choices, select the Setup button, select the Shipping Tab, and select the Shipping Choices button (or from the main menu select Admin, Setup, Shipping, Shipping Choices).
# On the Shipping Choices Screen, click on Endicia under the Category section.
# Make sure the “Use Endicia for printing labels?” box is checked
# Click on the Browse button to locate where the Dazzle.exe software is installed.
# Double click in the Layout Location next to each Ship Method to locate where the desired label definition is (these are .lyt files installed with Dazzle, typically under Users\Public\Public Documents\Endicia\DAZzle). In earlier versions of Dazzle, you used to have to define a layout for each shipping method used. This is no longer required. You can now use the same label layout for all domestic labels and Dazzle will get the proper shipping method from CMS.
# Select the “Test Mode” box in CMS until sure labels are printing correctly. Then return to Setup, and uncheck the “Test Mode” box. Please contact Endicia’s support if you require any assistance with the installation, setup or configuration of their software or labels.
# Select the “Auto Close After Printing Label” box. If you notice a delay in printing the labels, you can uncheck the “Auto Close After Printing Label” box. If CMS times out waiting for a response from Dazzle, increase the "read delay" value up from 2 (default).

*Screenshots of a recommended setup (exluding workstation specific settings) - http://screencast.com/t/PUUmUGBRoYC
==International Configuration==
CMS does support international shipping with Endicia. International shipping requires some additional configuration and that you have added customs information to your products. The [http://updates.newhavensoftware.com/v803release_notes.htm#link-1-2 CMS 8.0.3 Release Notes] details these settings and capabilities.

==Customizing Endicia Labels==
http://www.endicia.com/Support/TechNote/LabelCustomization/

=Using Endicia=
Once setup is complete, your USPS (and UPS) shipping can be performed in the CMS Manifest screen found in Fulfillment>Manifest. There you just add the package by package number, entering or scanning, or you can add a range, and then verify the weight and click on the Endicia button to immediately print the label. Once printed the ship date is set on the package/invoice and the delivery confirmation is imported into the package’s tracking number field.

CMS is capable of high levels of shipping automation with UPS and USPS if properly configured. This can be as fast and simple as placing a package on the scale, scanning its bar-code, and the label will print out. This requires a compatible scale and scanner, a list of which can be found on our [http://wiki.newhavensoftware.com/index.php/CMS_System_Requirements System Requirements] page. Please contact NHS Support for assistance with setting up these peripherals and related automation options.

=Support=
=== Endicia Errors ===
*When sending a shipment to Endicia via the CMS manifest, this error comes up: '''Error creating printer device context, cannot print'''. This is because there is no printer set up for the current layout. To fix:
# Click OK on the error dialog.
# Click '''File->Printer Setup...'''.
#* Note that the Printer, Paper Feed Source, and Printer Paper Size fields are blank.
# Select the appropriate printer from the drop-down.
# Select a paper source from the list.
# Select a Printer Paper Size that matches the destination media.
# Check the box labeled "Save Printer Information with Layout".
# Click OK.
# Click '''File->Save Layout'''.
Export the order from CMS again - this time it should print normally.

*Endicia reports it is in '''Test Mode'''
#Start by confirming that CMS is not in Test Mode by verifying the checkbox in Setup>Shipping>Shipping Choices>Endicia
#If that is confirmed to be off and you've restarted CMS, there is likely a problem with the template in DaZzle. Someone has likely edited it or not set it up correctly so it does not match the shipping type setup in CMS, for example. Remember that CMS requires you to use a unique DaZzle layout for each USPS service type (shipping method) and each layout's method must match the method in CMS it has been associated with.

*Here are possible error responses Dazzle may report back and their meanings (per the Dazzle integration docs)
'''Value Description'''
‐3 Address Verification failed (return code less than 25)
‐4 Unsupported mail class for international mail or invalid weight/rate values
‐6 USPS Delivery Confirmation error – denied, service unavailable or communication error
‐7 USPS Express Mail error – denied, service unavailable or communication error
‐8 USPS Customs Forms error – denied, service unavailable or communication error
‐9 International Mail Shipping Label (large or small) processing error
‐10 CONFIRM service error – denied, service unavailable or communication error
‐11 Express Mail International, Priority Mail International, or First‐Class Mail International Error–no “to phone” for mail addressed to P. O. Boxes.

*Server Status
To check to see if the dazzle service, (or other Endicia services) are experiencing problems, please click on the link below:

https://status.endicia.com/

CMS System Requirements

2018-04-16T18:21:31Z

Luke steinmetzer:

CMS system requirements are fairly meager considering the capabilities of today's machines. As such, most anything you buy or already own may be more than adequate. You do, however, want to make sure you're meeting the following system requirements.

=64-bit vs 32-bit=
This option affects both your hardware and software. Some Windows operating systems are available in either a 32-bit or 64-bit version. Either will work both with CMS and CMS's database server software - Sybase SQL Anywhere. The 64-bit version does not offer any benefits to CMS over its 32-bit counterpart for the workstations. Sybase, on the other hand, would stand to benefit from a 64-bit OS on the server, not the least of which is its support of additional RAM. If you're looking at running Windows Vista we'd recommend sticking with the 32-bit editions. If you're considering Windows 7, 8.1, or 2008 Server you may opt for either the 32 or 64-bit editions. Note that Windows Server 2008 R2 and Server 2012 are only available in 64-bit.

=Hardware=
==Servers==
This section applies to machines that are operating as pure servers or for stand-alone installations which are acting as both a server and workstation.

'''Minimum Requirements'''
For small volume companies with one or few workstations
* Pentium 4 - 1.8 GHz or faster CPU
* 1 Gigabyte RAM
* 128 GB Hard Drive with '''at least''' 2x your CMS database size always available in disk space
* CD-ROM or CD-R/RW Drive
* SVGA Monitor

'''Database Server - Additional Recommendations'''
Server enhancements to consider as your server demands increase (higher volume, more workstation connections, larger/multiple databases)
#The best things you can do to improve the performance and capability of your CMS server is to maximize your RAM, purchase fast hard drives, and ensure adequate available disk space. The speed and number of processors has less to do with CMS performance than does I/O (disk read/write speed) and being able to cache some or all of the database into RAM. This should be your first goal when purchasing a new server or optimizing and existing server. Read more about [http://wiki.newhavensoftware.com/index.php/CMS_System_Requirements#What_is_.22database_caching.22.3F database caching] options below to make the most of your available RAM.
#Solid State Drives (SSD) can be an attractive option/addition to your server. They are essentially RAM and are extremely fast.
#Isolate your CMS database onto its own drive so it is not sharing a drive with your operating system or other server files.
#Isolate CMS onto its own server so is not also being used for Exchange, file shares, etc. to achieve optimal performance (also recommended for PCI compliance)
#Disable Windows Themes (typically is disabled or not installed at all on server operating systems)
#Check your Power Options (Control Panel>Hardware>Power Options) and select High Performance (not necessary to do this and running in Balanced mode may be fine but consider this if experiencing performance issues)
#The CMS database server (Sybase) can make use of dual processors but, as a rule, processing speed does not play a huge role in performance. Consider this nice to have but not a necessity and lower in priority than the RAM and fast drive recommendations above.
#Fast network cards - Especially useful if you run a lot of reports from your workstations. In conjunction, evaluate speed and age of switches (replace hubs) and network cabling.
#[http://en.wikipedia.org/wiki/RAID RAID] 6 or other drive array. Priority of redundancy over striping if going with a different RAID configuration. Your server is at the heart of your company's operation and you need to make sure you can keep it going. Redundancy will help you sleep at night.
#Backups - While not a performance issue, this is an important consideration for a new server. You'll want to have an automated system in place to move the nightly CMS backup (must be turned on and configured) to other storage locations. Ideally you'd have a rolling backup routine that allows you to store backups for each night without overwriting the previous backups and then move the last backup of the week off-site (DVD, tape or online backup location). This way even if your place of business was in a natural disaster or your server was stolen, you would reasonably be able to recover. We unfortunately had a customer of ours go out of business because they were unable to recover when their server was lost in a fire. Protect yourself from the same fate.

'''Configuration'''

When running directly on a Windows server (2003 and up), CMS will not be able to make web service calls until the following configuration change is made. This can impact some CMS integrations so the following setting should be made on your server. Go into Control Panel->System & Security->System->advanced System Settings->Performance->Settings and choose the Data Execution Prevention tab.

The default setting is Turn on DEP for all programs and services except those I select, and there is no reason to change it for CMS. However, you need to add CMS to the exception list, which will then allow CMS to communicate with web services.

*Themes - CMS 8.0 and later requires Windows Themes be enabled if you are running CMS on your server (including Terminal Services).

==CMS workstations==
Workstations are those machines that are running CMS from a server on your network. If you are running CMS on only one machine or that machine is your server, please see the Server requirements above.

'''Minimum Requirements'''
* Pentium III 500 MHz or faster
* 1 GB RAM
* CD-ROM Drive
* 20GB Hard Drive with 2GB available
* SVGA Monitor
* 10Mbps Network Card(s) or faster

'''CMS Workstation Recommendations'''

Very little processing, disk space or hardware is required to run CMS on a workstation. Most everything takes place on the server or in memory so your workstation requirements are reasonably small. Our only recommendation, beyond the above minimums, is to upgrade your RAM to 4 Gig.

==[http://en.wikipedia.org/wiki/Peripheral Peripherals]==
CMS will work with most any peripheral (e.g. printers) as long as the manufacture still supports it and offers drivers for your operating system. If the manufacture does not support your device and offer drivers for your operating system, NewHaven Software cannot assist you with it. It may work with CMS but, if not, you must upgrade your device to a currently supported model.

While this may seem like we're just washing our hands of supporting older hardware, there is really more to it. CMS, like most other Windows applications, relies on Windows to operate as an intermediary with its peripherals. CMS communicates to Windows and then Windows handles the communication with the peripheral. If Windows does not have a current driver, that communication may fail or operate in unexpected ways. In other words, any problems with the peripheral are outside of our software and control.

===[[POS Module]]===
The only place where CMS has more specific hardware requirements are the peripherals used with its POS Module. The Point of Sale Module only supports specific models of printers, cash drawers, credit card swipes and UPC bar code scanners.

*'''Printers''' - Most any Windows compatible printer should work but the following are the 80 column thermal printers we have tested and can support:
**Star TSP143II
**Samsung SRP-350

*'''[[Barcode Scanners]]''' - CMS requires either USB serial emulation mode or USB HID POS. Contact Support for a programming guide suitable for your model of scanner. If you are not purchasing these models through NewHaven Software, '''be sure that you are supplied with a proper cable to allow USB serial emulation if USB HID POS is not supported'''.

*'''Cash Drawer'''
**APG 320 MultiPro
**MMC 225151644204

*'''Credit card swipe/reader''' - Magtek model 21040102 (many look the same but are not, it must be this model)

*'''Pole Display''' - Logic Controls PD-3000 series

Other hardware may work with CMS but these are the only models we have tested and can support or offer configuration instructions for. The credit card reader, however, is unlikely to work unless you have the specific model we have recommended.

===Shipping Station===

===='''Barcode scanners'''====
CMS supports the USB HID POS, USB/serial, and keyboard wedge style scanner (albeit with reduced capability, not recommended). Read this article on [[Barcode Scanners]] for more information and a list of supported models.

We also provide a [http://updates.newhavensoftware.com/Manifest_Function_Key_Bar_Codes.pdf sheet of barcodes] suitable for use at the shipping station. Print this and tape it to your monitor for fast and easy hands-free shipping.

===='''Scales'''====
*CMS version 7 or earlier - CMS will work with most any scale that connects via a serial connection and can emulate a Mettler Toledo (models 8213 or PS60) or the UPS Fairbanks scale.
*CMS 8.0 or later - USB connections are supported for the Toledo models PS60 and PS90 (in addition to supporting serial connections for the scale models mentioned above.)
*[http://updates.newhavensoftware.com/v9release_notes.htm#link-1-9 CMS 9.0.5] or later - Any of the above plus the Adam brand scale - CPWplus models (e.g. CPWplus 35). These scales require a serial connection with '''null modem cable''' which is not included or can be used in conjunction with a USB:serial converter if your computer has no serial port (although a $15 serial card is cheaper and better.)

If you are using a scale provided by UPS or FedEx, you may need to change a setting in the scale's menu to restore it to default settings (so it is no longer using a proprietary communication protocol).

Other scanners or scales may work with CMS but these are the ones we support and can assist you with configuration. Please contact us if you'd like us to evaluate other hardware (typically requires shipping a unit to us for testing.)

See our article on [[Shipping_Station_-_Best_Practices]] for more tips!

=Operating Systems=
The following are operating systems currently supported by Microsoft and NewHaven Software for use with CMS. NewHaven Software will only support use of CMS on operating systems currently supported by Microsoft. Noting also the PCI Compliance requires that your payment application (CMS) be used on an operating system that has current security updates.
==Servers==
*Windows Server 2008 - (Note: TLS 1.2 must be enabled, it is not by default. See https://technet.microsoft.com/en-us/library/dn786418.aspx#BKMK_SchannelTR_TLS12)
**Server 2008 R2 Editions supported - Standard, Small Business Server, Enterprise
*Windows Server 2012 (CMS v9.0.9 or later)
**Server 2012 R2 Editions supported - Essentials, Standard

NOTE: Microsoft ended support for Windows 2003 Server on July 14, 2015.

==Workstations or CMS Solo (i.e. single-user)==
*Windows 7 Professional
*Windows 7 Ultimate
*Windows 8.1 Pro (only) - Supported only in CMS 9.0.9 or later. An updated Sybase database driver is required to support Win 8.1 and workstation updates will be required.
*Windows 10 - CMS 10.0.5 or later (noting that some barcode scanners do not work with Windows 10 due to a manufacture's driver issue. Please see the above section on scanners for more information.

NOTE: Microsoft ended support for Windows XP Professional on April 8, 2014 and Vista on April 11, 2017.

=Remote Connections=
There are many options available to you when wanting to run CMS remotely. The core issue that must be observed is that CMS must be running on a machine that is connected locally to its database server. As long as that is true, you'll have no troubles running CMS remotely. You cannot, however, have CMS running locally on your workstation and connect to a remote server. The following are some remote access solutions and tips.

==Remote Access Software==
Software like TeamViewer, LogMeIn, and GoToMyPC are inexpensive remote access tools that allow you to connect to your PC via their website, thus from any other PC. Performance is a little slower than other solutions but is low cost, flexible and easy to use.

==[http://en.wikipedia.org/wiki/Remote_Desktop_Services Remote Desktop and Terminal Server]==
*Our preferred method is to use Windows' built-in remote access options. Remote Desktop (RDP) allows you to connect to your work machine with CMS on it and control it remotely. To do this you must first establish a virtual private network (VPN) connection.
*[http://www.emazzanti.net/the-12-advantages-of-terminal-services/ Terminal Services] or Remote Desktop Services (RDS) is also an option that will allow you to VPN into your server and create/run a remote session right on the server and without the need for a dedicated workstation. This is also a popular option but does require purchasing Windows client access licenses (CALs). Note: Running CMS 8.0 or later on terminal services will require that you enable Windows themes (usually off or not installed with Windows Server OS's). Also note that when running CMS in terminal services, all users share the same 'Workstation Specific' settings (In CMS see Setup>General>Workstation Specific to review these settings and assess if this trade-off is acceptable.)
*We've written a separate article on configuration recommendations for RDP - http://wiki.newhavensoftware.com/index.php/CMS_over_Microsoft_Remote_Desktop

Printing can present some challenges under Terminal Services, not to CMS but in general. Here is an excellent resource to help address them - http://wiki.newhavensoftware.com/index.php/CMS_over_Microsoft_Remote_Desktop#Printing

===Warning===
At this time Endicia's Dazzle software is not supported by Endicia for use on a Terminal Services server. Please take into account your use of peripherals and integrations to make sure they are supported and will work as expected under Terminal Services.

==Cloud Computing==
===Licensing===
Only one database server can be running concurrently. Connections to that database server must come from the same domain. As stated above, CMS must be run on network local to the database server (i.e. you can remote into a vm, machine, or terminal server hosting CMS). You cannot run CMS locally and connect to a remote server.

===Peripherals and Integrations===
While cloud deployment does not present any inherent challenges to CMS, there can be complications with getting a remote instance of CMS to properly interact with local hardware. While printers are commonly used and not typically a problem, communication with serial or USB devices (e.g. bar code scanners, scales, card swipes, pole displays) can be more challenging. Testing of existing/needed peripherals must be done before launching into production to ensure all users can continue to operate efficiently. We recommend you read our separate article on running CMS via RDP, including peripheral sharing, for some guidance that may be helpful - http://wiki.newhavensoftware.com/index.php/CMS_over_Microsoft_Remote_Desktop

If you are using any other integrations with CMS, specifically if they are not done with web services, you'll also want to test those to ensure expected operation is possible.

===PCI Compliance===
There are PCI implications when moving your CMS database (which stores credit card data) to the cloud. It will add risk and corresponding cost/effort to mitigate that risk in order to remain PCI compliant. Here is a document from the PCI Council for guidance - https://www.pcisecuritystandards.org/pdfs/PCI_DSS_v2_Cloud_Guidelines.pdf

Another helpful article from TechTarget detailing some of the cloud deployment challenges stemming from the recent PCI-DSS 3.0 spec - http://searchcloudsecurity.techtarget.com/tip/PCI-DSS-30-Three-key-requirements-to-maintain-cloud-compliance
=Network Requirments=
During the Setup of CMS on your network, you need to also ensure that your network security software is set to allow the following through it:
*TCP/IP 2638
*HTTP 80
*HTTPS 443
*CMS.exe
=Virtual Machines=
NewHaven Software will support CMS running on a virtual machine as long as the operating system (OS) running in the virtual machine is also supported. However, if NHS is unable to reproduce an issue, the customer may be asked to reproduce the problem running natively on the supported OS, outside the virtual environment. NHS does not explicitly test or certify products running in a virtual environment.

In other words, NHS can support CMS running in virtual environments but not the environments themselves. We strongly recommend that if you decide to pursue running virtual machines that you have someone with related expertise to assist with the setup and administration of these, much the same as you would network administration.

==Recommendations==
CMS can run on a virtual machine/server as long as it is provided enough resources (e.g. disk space, memory, processor). We in fact run CMS here at NewHaven Software on a virtual server and have had great success with it. We have been using VMware ESXi v4.0 and have also had successful tests with Xen Server 5.6 Feature Pack 1 although have yet to run CMS in production on Xen Server. We do have several CMS clients running live on virtual servers presently as well.

As a rule, CMS and the database server will run with no particular technical issues although performance may not be as good as running on a dedicated non-virtual server. Reinforcing what has been said above, lots of RAM and fast drives (disk I/O) are the biggest factors that impact CMS performance. Our recommendations for running CMS on a virtual server is simply to ensure that sufficient resources are allocated.

If you think virtualization is in your future, please contact us for assistance in setting up a test environment. Before deploying into production we of course strongly recommend testing. You'll want to validate that performance is acceptable and that all connectivity, including from peripherals (if applicable), and all integrations are working and performing at acceptable levels.

=3rd Party Software=
Many 3rd party software solutions can be used in conjunction with CMS but it is important to note that we do not support these software solutions. Examples of 3rd party software include Crystal Software, Microsoft Access, Mapforce, etc. The NHS technical staff is not responsible for answering any questions about features/functionality or bugs within these software programs. Please view your Software License and Support Agreement for details.

We are, however, happy to provide assistance as a professional service. For more details, please contact your account manager.

=FAQ's=
==Can I use Windows 10?==
We support running CMS on Windows 10 workstations under CMS versions 10.0.5 and later.

NOTE: If you're using older peripherals (scales/printers) the manufacture may never release a Win10 compatible driver. Something to consider before replacing a machine or updating its operating system. Either research to make sure compatible drivers are available or be prepared to replace the peripherals with newer models that are compatible.

SCANNERS: We've learned that Honeywell is not yet able to get serial emulation working with the USB bar code scanners. If you are using a scanner on a machine you intend to upgrade to Win10 you will need to obtain a scanner that can work in USB HID POS mode. Read the [http://wiki.newhavensoftware.com/index.php/CMS_System_Requirements#POS_Module POS section of our System Requirements] page for more details.

==Do I need a new machine to run CMS?==
Probably not. The operating system is far more important than your hardware. If your operating system is no longer supported by Microsoft, you may be able to update it or reinstall a supported operating system on your current machine. Please consult Microsoft for their minimum requirements for the operating system your selecting. Generally if it meets Microsoft's requirements for their operating system, it will be good enough for CMS as well. From there, you need to decide if good enough is in fact really good enough and that will be clear in the performance of Windows, CMS or other applications. Often times poor performance is a factor of limited memory and, since memory is typically quite cheap, you should consider maximizing RAM before replacing a machine (and on any new machine).

==My operating system is currently supported, do I need a new machine?==
Hardware is rarely an issue with CMS and you could be running old machines and still experience reasonable performance. If you're satisfied with the speed of CMS, you're able to run a supported operating system without errors, and you have adequate disk space, you may choose to continue to run on your existing machine(s).

If you were to do only one thing, it should be to max the amount of RAM your machine will take. RAM is cheap, too cheap to not have plenty of it.

Secondarily, a CMS server needs a lot of disk space not just for its database but also requires additional free gigabytes of space for temp files that the database server creates and destroys through normal usage to optimize performance. You should never have less than 2x your database size in free drive space on your server (and this only considers CMS's needs, not Windows or other processes). Here too, drive space is too cheap for this to be a limiting factor.

There may be other compelling reasons to upgrade your machines, be it for speed, other applications or compatibility with other new technologies. New machines that are capable of running 64-bit operating systems, for example, are capable of handling more than 4 Gigabytes of RAM. While this would rarely be a CMS consideration for a workstation, if you have a database (.db file) that is larger than 2 Gig, you should seriously consider a server with more than 4G of RAM.

As a rule, the performance you need from CMS is merely a factor of hardware. As your company grows, CMS can scale perfectly well with you but may require improved hardware to keep up with the increased server load. Evaluating CPU/memory usage and free disk space during the heat of the day will give you an indication of how well your server is handling the load and if more resources are needed.

==Why can't I continue to use an older operating system?==
Even if has worked fine with CMS for years, if Microsoft no longer supports it, you really don't want to be using it. Once Microsoft stops offering security patches, as they have for Windows XP and 2003 Server, you become vulnerable to new threats (viruses, hacks, etc.) and you may find that new versions of CMS will no longer work. Such was the case with Windows 2000 as it did not contain the encryption components needed for newer versions of CMS to run properly and satisfy PCI requirements. [http://wiki.newhavensoftware.com/index.php/Windows_2000_and_CMS This link] provides more information on this subject.

PCI requirements also dictate that your systems must be kept up to date with current security patches. In other words, you cannot be PCI compliant while running CMS on machines with unsupported operating systems.

==Can I run CMS on my Mac?==

CMS does not run natively on a Mac but there are solutions for running Windows applications on a Mac.

*Microsoft’s free [http://www.techrepublic.com/article/pro-tip-remote-desktop-on-mac-what-you-need-to-know/ remote desktop solution] can run on non-Intel Macs running OS 10.5.8 or later. This is desktop sharing (connecting to a remote PC/server).

*[http://www.parallels.com/landingpage/pd/windows-on-mac/ Parallels] is one of several solutions worth exploring if you prefer not to remote into a Windows machine. They have a 14 day free trial.

In either case, there is no USB/HID support, meaning printers are the only supported peripherals (no scale, scanner, card reader, or pole display).

==What about my network?==
Our recommendations here are pretty generic. If you're still on the old 10mbps cards you should consider upgrading. 1Gbps is pretty standard these days. CMS doesn't need a lot of bandwidth but could benefit from 100mbps over 10mbps...depending on what other network traffic you might expect. If you have hubs or old switches, that would be a good place to look at upgrading.

==Will CMS work with wireless?==
Yes, although CMS must maintain a constant connection with its database and even momentary interruptions in that connection can be enough to cause errors. As such, we do not recommend running CMS over a wireless network connection. You can, however, use Remote Desktop via wireless to connect to a machine that is on your physical network and, in that scenario, you would not be subject to disconnect issues.

==Can I run CMS remotely?==
Yes, but it must be done using RDP (remote desktop), terminal services or remote access software like Logmein. CMS must be running on the same network/domain as its database server. You'll need to remote into Windows first and then run CMS from that machine. You cannot have CMS installed locally and connect to a remote network/server. See the section on [http://wiki.newhavensoftware.com/index.php/CMS_System_Requirements#Remote_Connections remote connections] above.

==Can NewHaven Software assist with purchasing or configuring my hardware/network?==
We can make recommendations, like we have in this article, but the actual purchase, configuration and maintenance of your hardware and network must be performed by someone at your location. This would either be done by someone on staff that is capable or a local contractor that can provide these services and expertise to you. We're happy to consult with your staff or contractors on any CMS related configurations.

Moving CMS to a New Server

2017-11-30T23:15:25Z

Luke steinmetzer:

=Overview=
This article details the instructions for moving your CMS installation from an old server to a new server including moving your data.

This process is a large undertaking that will require CMS to be down during the move. As a result please inform NewHaven Support of the day you plan to do the server migration. This is so we may either set up a appointment with you to guide you through the process, or at least ensure we have staff available to you in case you find you require assistance.

The following instructions have 4 major themes to them:

# Preparing to move CMS to the new System.
# Installing CMS on the new System.
# Moving the old Database to the new System.
# Updating the old Database to the new version of CMS

The above list is to help outline what exactly the following instructions are attempting to accomplish and to give you an overview of the process you are about to undertake.

=Moving CMS on to a new server=
== Step 1 - Prerequisites==
CRITICAL! ALL USERS MUST EXIT CMS PRIOR TO INSTALLING CMS SERVER ON ANOTHER COMPUTER!

CRITICAL! YOU MUST BE LOGGED IN AS THE COMPUTER ADMINISTRATOR OR A USER THAT IS A MEMBER OF THE ADMINISTRATORS GROUP!

==Step 2 - Make a backup image of CMS Database files==
We need to create a backup of your current live database to transfer to the new server.
To create a backup of your database please review the link below:

http://wiki.newhavensoftware.com/index.php/Creating_a_Database_Backup

== Step 3 - Stop and Disable the Sybase service on your old system ==
Next we will need to disable the Sybase service on your old system. This step is done to ensure there is no conflict with the database services when we do the install on the new system.

#If you are migrating CMS version 7 or older to a new server, please follow the information in the link below:
http://wiki.newhavensoftware.com/index.php/How_to_stop_and_start_the_Sybase_service#How_to_Stop_the_Sybase_service_if_running_CMS_7.0_or_earlier
#If you are migrating CMS version 8 or newer to a new server, please follow the information in the link below:
http://wiki.newhavensoftware.com/index.php/How_to_stop_and_start_the_Sybase_service#How_to_Stop_the_Sybase_service_if_running_CMS_8.0_or_later

== Step 4 - Disable sharing on the NewHaven Software folder ==
This is to ensure we do not accidentally connect workstations to the old server after the migration is complete.

For information on how to do this please visit http://wiki.newhavensoftware.com/index.php/Folder_sharing_in_Windows

== Step 5 - Install CMS Server on the new computer. ==

To do so please follow the information in the link below.
http://wiki.newhavensoftware.com/index.php/Server_Update

== Step 6 - Stopping the Sybase service on the new computer ==
We need to stop the Sybase service now to transfer in the copy of the database from the old server.

To do so please follow the links below:

#If you are migrating CMS version 7 or older to a new server, please follow the information in the link below:
http://wiki.newhavensoftware.com/index.php/How_to_stop_and_start_the_Sybase_service#CMS_7.0_or_earlier
#If you are migrating CMS version 8 or newer to a new server, please follow the information in the link below:
http://wiki.newhavensoftware.com/index.php/How_to_stop_and_start_the_Sybase_service#CMS_8.0_or_later

== Step 7 - Copying over your Database and log file to the new system ==
#Create a new folder in the NewHaven Software\Data folder. Name it CLEAN.
#There should be two files in the NewHaven Software\Data\ ( Your Database Name) folder; one with a .db extension and one with a .log extension. Move both of these files into the NewHaven Software\Data\Clean folder you just created.
#Copy the .db and .log file from the old CMS Server computer into the NewHaven Software\Data\ (Your Database Name) folder on your new CMS Server computer.

== Step 8 - Copying over the CMSDBO.ini file and Custom Reports ==
We now need to copy of the CMSDBO.ini file to ensure CMS is able to start, as well as any custom reports.

# Check the NewHaven Software folder on the old server, see if there is a file present called CMSDBO.ini, if it is not there skip the next step.
# If this file is present please copy and move it into the NewHaven Software folder on your new system.
# Also if you have any custom reports please make sure to move them to the new server as well.

== Step 9 - Restart the Sybase service on the new computer ==
You will now need to stop the Sybase service on the new computer. To do so please follow the links below:

#If you are migrating CMS version 7 or older to a new server, please follow the information in the link below: http://wiki.newhavensoftware.com/index.php/How_to_stop_and_start_the_Sybase_service#How_to_Start_the_Sybase_service_if_running_CMS_7.0_or_earlier
#If you are migrating CMS version 8 or newer to a new server, please follow the information in the link below:
http://wiki.newhavensoftware.com/index.php/How_to_stop_and_start_the_Sybase_service#How_to_Start_the_Sybase_service_if_running_CMS_8.0_or_later

== Step 10 - Log into CMS ==
Log into CMS and confirm it is working. If you get a database mismatch error message, you will need to rerun the setup and reboot the computer in order to sync up the CMS application and database. To do so please follow the instructions in http://wiki.newhavensoftware.com/index.php/Server_Update

== Step 11 - Check your backup ==

Check your CMS backup settings in to ensure the path that it is using to backup its files is still valid on this server. To access this please follow the information in the link below:

http://wiki.newhavensoftware.com/index.php/Creating_a_Database_Backup

== Step 12 - Sharing the NewHaven Software folder ==
Once you confirm CMS is working on the new installation, you can share out the NewHaven Software folder so your workstations are able to connect to it. For information on how to do this please visit http://wiki.newhavensoftware.com/index.php/Folder_sharing_in_Windows

== Step 13 - Connecting Workstations to CMS ==
If the server is on the same network as your old server. All you need to do is remap the NewHaven Software shared drive on the workstations to the new server. For information on how to do that please review the video below:
http://youtu.be/dBbd94k7b0A

If these workstations are on a NEW network along with the server, or you are also installing new workstations, please follow the link below:
http://wiki.newhavensoftware.com/index.php/Workstation_Install

== Step 14 - Removing CMS from the old system ==
Uninstall CMS Server from the old computer to ensure the potentially conflicting Sybase service is removed and that everyone is running CMS from the same directory on the new CMS Server computer.

== Step 15 - Updating CMS to the latest version ==

At this point if you need to update CMS to the latest version, please follow the information in the link below:
http://wiki.newhavensoftware.com/index.php/Server_Update

Inventory Troubleshooting

2015-09-21T09:45:45Z

Luke steinmetzer: Created page with '=Overview= This article will review common issues with your inventory and how to troubleshoot them. =Missing Stock= If you ever run into a situation where you have stock miss…'

=Overview=

This article will review common issues with your inventory and how to troubleshoot them.

=Missing Stock=

If you ever run into a situation where you have stock missing from a product and you are unsure why that stock is missing there are a few things to check on as listed below

==Identify When your stock went missing==

To first troubleshooting why you are missing stock, you need to know when it went missing. This can be identified with the use of 2 reports.
*Reports > Inventory > Inventory Tracking. This report can be used to identify, at a glance, when orders where placed that would withdraw that stock. What lot the stock was pulled from, and when. This is your primary tool for tracking down this information. You should be able to see a direct correlation between product sold and lot stock levels.
*Reports > Sales > Product Sales Detail. This report is used
==Subtitle 1==
=Header 2=
=Header 3=

[[Category:Blank]]

Crystal Reports

2014-12-18T18:28:22Z

Luke steinmetzer: Created page with '=Overview= CMS reporting is creating using a program called Crystal Reports 9. Below is some more detailed information for those looking to find out more about our reports or fo…'

=Overview=

CMS reporting is creating using a program called Crystal Reports 9. Below is some more detailed information for those looking to find out more about our reports or for those interested in creating there own.

=Information on CMS Crystal Reports=

CMS includes a detailed manual that covers a wide variety of pre built Crystal Reports. This Manuel can be accessed in CMS by going to Help > CMS Manuals > CMS Reports Guide. For more information on CMS reporting I recommend reading through this document. On top of that at the end of this Manuel we detail the various tables in CMS itself. This information is invaluable if you are starting to create your own reports.

=What is needed to create your own Crystal Report=

To create a report that will run in CMS via Reports > Use Custom, you will need a copy of Crystal Reports 9: Professional Edition. The reason you want the Professional Edition is due to the fact it will let you create an ODBC connection directly with our Sybase database. This function is critical to get good reporting and is a feature not present in the standard edition.

That said Crystal Reports 9 is also an older version of Crystal at this point. It can be very difficult to find. If you do look into getting a new edition of Crystal, be aware you will still be able create your own reports but any reports you create or modify may not work when run through CMS (you can still run them in Crystal.)

[[Category:Blank]]

Updating the CMS License Code

2014-12-05T19:47:39Z

Luke steinmetzer:

=Overview=

This article details the instructions for updating your CMS license code. This process is required when you have been provided a new license code to update your support, you have added or changed models in CMS, or you are adding workstation licenses to CMS.

=Finding your new CMS license. =

Your new CMS license is available at: http://updates.newhavensoftware.com/

After signing into the update page you will see your license code at the top of the screen.

=Preparing to update your CMS license=

# Please make sure everyone is signed out of CMS. TIP: If you can delete the CMSNET.dat file, everyone is out of CMS (and CMS will recreate this file automatically next time someone logs in.)
# Make sure you are on your CMS Server and not a workstation.

= Updating your CMS license via Manage CMS =
Note: These instructions assume you are on CMS version 7 or later. Also you will need to be on your CMS Server.

[[image:license1.png]]

[[image:license2.png]]

[[image:license3.png]]

[[image:license4.png]]

[[image:license5.png]]

[[image:license6.png]]

[[image:license7.png]]

[[image:license8.png]]

[[image:license9.png]]
 

After following these instructions your license will be updated and you can sign back into CMS.

CMS System Requirements

2014-10-23T20:31:30Z

Luke steinmetzer:

CMS system requirements are fairly meager considering the capabilities of today's machines. As such, most anything you buy or already own may be more than adequate. You do, however, want to make sure you're meeting the following system requirements.

=64-bit vs 32-bit=
This option affects both your hardware and software. Some Windows operating systems are available in either a 32-bit or 64-bit version. Either will work with CMS and CMS's database server software - SQL Anywhere. The 64-bit version does not offer any benefits to CMS over its 32-bit counterpart. Sybase, on the other hand, would stand to benefit to some degree from a 64-bit OS, at least in its support of additional RAM. If you're looking at running Windows Vista or 2003 Server we'd recommend sticking with the 32-bit editions. If you're considering Windows 7, 8.1, or 2008 Server you may opt for either the 32 or 64-bit editions. Note that Windows Server 2008 R2 is only available in 64-bit.

=Hardware=
==Servers==
This section applies to machines that are operating as pure servers or for stand-alone installations which are acting as both a server and workstation.

'''Minimum Requirements'''
For small volume companies with one or few workstations
* Pentium 4 - 1.8 GHz or faster CPU
* 1 Gigabyte RAM
* 128 GB Hard Drive with '''at least''' 2x your CMS database size in available disk space
* CD-ROM or CD-R/RW Drive
* SVGA Monitor

'''Database Server - Additional Recommendations'''
Server enhancements to consider as your server demands increase (higher volume, more workstation connections, larger/multiple databases)
#The best things you can do to improve the performance and capability of your CMS server is to maximize your RAM, purchase fast hard drives, and ensure adequate available disk space. The speed and number of processors has less to do with CMS performance than does I/O (disk read/write speed) and being able to cache some or all of the database into RAM. This should be your first goal when purchasing a new server or optimizing and existing server. Read more about [http://wiki.newhavensoftware.com/index.php/CMS_System_Requirements#What_is_.22database_caching.22.3F database caching] options below to make the most of your available RAM.
#Solid State Drives (SSD) can be an attractive option/addition to your server. They are essentially RAM and are extremely fast.
#Isolate your CMS database onto its own drive so it is not sharing a drive with your operating system or other server files.
#Isolate CMS onto its own server so is not also being used for Exchange, file shares, etc. to achieve optimal performance (also recommended for PCI compliance)
#Disable Windows Themes (typically is disabled or not installed at all on server operating systems)
#Check your Power Options (Control Panel>Hardware>Power Options) and select High Performance (not necessary to do this and running in Balanced mode may be fine but consider this if experiencing performance issues)
#The CMS database server (Sybase) can make use of dual processors but, as a rule, processing speed does not play a huge role in performance. Consider this nice to have but not a necessity and lower in priority than the RAM and fast drive recommendations above.
#Fast network cards - Especially useful if you run a lot of reports from your workstations. In conjunction, evaluate speed and age of switches (replace hubs) and network cabling.
#[http://en.wikipedia.org/wiki/RAID RAID] 6 or other drive array. Priority of redundancy over striping if going with a different RAID configuration. Your server is at the heart of your company's operation and you need to make sure you can keep it going. Redundancy will help you sleep at night.
#Backups - While not a performance issue, this is an important consideration for a new server. You'll want to have an automated system in place to move the nightly CMS backup (must be turned on and configured) to other storage locations. Ideally you'd have a rolling backup routine that allows you to store backups for each night without overwriting the previous backups and then move the last backup of the week off-site (DVD, tape or online backup location). This way even if your place of business was in a natural disaster or your server was stolen, you would reasonably be able to recover. We unfortunately had a customer of ours go out of business because they were unable to recover when their server was lost in a fire. Protect yourself from the same fate.

'''Configuration'''

When running directly on a Windows server (2003 and up), CMS will not be able to make web service calls until the following configuration change is made. This can impact some CMS integrations so the following setting should be made on your server:

*'''Server 2003:''' Go into Control Panel->System->Advanced->Performance->Settings
*'''Server 2008:''' Go into Control Panel->System & Security->System->advanced System Settings->Performance->Settings
*Choose the Data Execution Prevention tab.

The default setting is Turn on DEP for all programs and services except those I select, and there is no reason to change it for CMS. However, you need to add CMS to the exception list, which will then allow CMS to communicate with web services.

*Themes - CMS 8.0 and later requires Windows Themes be enabled if you are running CMS on your server (including Terminal Services).

==CMS workstations==
Workstations are those machines that are running CMS from a server on your network. If you are running CMS on only one machine or that machine is your server, please see the Server requirements above.

'''Minimum Requirements'''
* Pentium III 500 MHz or faster
* 1 GB RAM
* CD-ROM Drive
* 20GB Hard Drive with 2GB available
* SVGA Monitor
* 10Mbps Network Card(s) or faster

'''CMS Workstation Recommendations'''

Very little processing, disk space or hardware is required to run CMS on a workstation. Most everything takes place on the server or in memory so your workstation requirements are reasonably small. Our only recommendation, beyond the above minimums, is to upgrade your RAM to 4 Gig.

==[http://en.wikipedia.org/wiki/Peripheral Peripherals]==
CMS will work with most any peripheral (e.g. printers) as long as the manufacture still supports it and offers drivers for your operating system. If the manufacture does not support your device and offer drivers for your operating system, NewHaven Software cannot assist you with it. It may work with CMS but, if not, you must upgrade your device to a currently supported model.

While this may seem like we're just washing our hands of supporting older hardware, there is really more to it. CMS, like most other Windows applications, relies on Windows to operate as an intermediary with its peripherals. CMS communicates to Windows and then Windows handles the communication with the peripheral. If Windows does not have a current driver, that communication may fail or operate in unexpected ways. In other words, any problems with the peripheral are outside of our software and control.

===[[POS Module]]===
The only place where CMS has more specific hardware requirements are the peripherals used with its POS Module. The Point of Sale Module only supports specific models of printers, cash drawers, credit card swipes and UPC bar code scanners.

*'''Printers''' - Most any Windows compatible printer should work but the following are the 80 column thermal printers we have tested and can support:
**Star TSP143II
**Samsung SRP-350

*'''[[Barcode Scanners]]''' - CMS requires USB serial emulation mode. Contact Support for a programming guide suitable for your model of scanner. If you are not purchasing these models through NewHaven Software, '''be sure that you are supplied with a proper cable to allow USB serial emulation'''.
**Honeywell 1300G (replaced the 3800G) - ''Supports both USB serial and USB HID POS''
**Honeywell Voyager MS9520 - ''Supports both USB serial and USB HID POS''
**Honeywell (Metrologic) Fusion MS3780 - ''Supports both USB serial and USB HID POS''
**Honeywell (HandHeld) 3800G - ''Supports both USB serial and USB HID POS'' (this model has been replaced by the 1300g above)
**Honeywell (Metrologic) Voyager MS9540 (with MX009 USB cable only and only known to work with USB Serial, not USB HID POS)

'''CMS 10.0''' added support for USB HID POS interface which works in lieu of USB serial emulation. Not all scanners support USB HID POS but, for those that do, configuration should be easier and you may have more scanner models to choose from. The following '''Honeywell''' models support USB HID POS and should work with CMS (with no programming other than putting the scanner into HID POS mode), but these models have not been specifically tested by NewHaven Software:
**MS5145 Eclipse
**MS9590 VoyagerGS
**MS9591 VoyagerGS HD
**MS9521 VoyagerHD
**MS9524 VoyagerPDF
**MS9540 VoyagerCG
**MS9541 VoyagerHD
**MS9544 VoyagerPDF
**MS9535 VoyagerBT
**MS1633 FocusBT
**MS1690 Focus
**MS1691 FocusHD
**MS9590i VoyagerGS
**MS1890 Focus
**MS7120 Orbit
**MS7180 OrbitCG
**MS3580 QuantumT
While these scanners do have to be programmed to work in the USB HID POS mode (aka USB HID serial mode, '''not''' USB HID SurePOS or USB HID keyboard) there should be no driver installation necessary as there is with USB serial emulation. You'll just need to find the proper bar code to scan in the scanner's programming guide for USB HID. You can purchase a scanner and ship it to us if you'd like us to add it to our supported scanner list. We can then provide documentation on proper setup and help with troubleshooting any future issues.

*'''Cash Drawer'''
**APG 320 MultiPro
**MMC 225151644204

*'''Credit card swipe/reader''' - Magtek model 21040102 (many look the same but are not, it must be this model)

*'''Pole Display''' - Logic Controls PD-3000 series

Other hardware may work with CMS but these are the only models we have tested and can support or offer configuration instructions for. The credit card reader, however, is unlikely to work unless you have the specific model we have recommended.

===Shipping Manifest===

===='''Barcode scanners'''====
CMS supports the USB/serial scanners listed above under POS Module and also can work with any keyboard wedge style scanner albeit with reduced capability. Read this article on [[Barcode Scanners]] for more information.

===='''Scales'''====
*CMS version 7 or earlier - CMS will work with most any scale that connects via a serial connection and can emulate a Mettler Toledo (models 8213 or PS60) or the UPS Fairbanks scale.
*CMS 8.0 or later - USB connections are supported for the Toledo models PS60 and PS90 (in addition to supporting serial connections for the scale models mentioned above.)
*[http://updates.newhavensoftware.com/v9release_notes.htm#link-1-9 CMS 9.0.5] or later - Any of the above plus the Adam brand scale - CPWplus models (serial connection with null modem cable which is not included)

If you are using a scale provided by UPS or FedEx, you may need to change a setting in the scale's menu to restore it to default settings (so it is no longer using a proprietary communication protocol).

Other scanners or scales may work with CMS but these are the ones we support and can assist you with configuration. Please contact us if you'd like us to evaluate other hardware (typically requires shipping a unit to us for testing.)

=Operating Systems=
The following are operating systems currently supported by Microsoft and NewHaven Software for use with CMS.
==Servers==
*Windows Server 2003 SP2 - Server 2003 is expected to continue to work with CMS for the foreseeable future but for new servers we recommend Server 2008 since [http://windows.microsoft.com/en-US/windows/products/lifecycle Microsoft has announced Server 2003 is End of Life] (EoL) on April 8th, 2014 (also true for Windows XP)
**Server 2003 Editions supported - Standard, Small Business Server, Enterprise
*Windows Server 2008
**Server 2008 R2 Editions supported - Standard, Small Business Server, Enterprise

Windows Server 2012 is currently in testing and in use by NewHaven Software as well. Official support for Server 2012 is expected early 2014.

==Workstations or CMS Solo (i.e. single-user)==
*Vista Business Edition SP2
*Vista Ultimate SP2
*7 Professional
*7 Ultimate
Windows 8.1 (not RT) In CMS Version 10 (not yet released)

NOTE: Microsoft ended support for Windows XP Professional on April 8, 2014.

=Remote Connections=
There are many options available to you when wanting to run CMS remotely. The core issue that must be observed is that CMS must be running on a machine that is connected locally to its database server. As long as that is true, you'll have no troubles running CMS remotely. You cannot, however, have CMS running locally on your workstation and connect to a remote server. The following are some remote access solutions and tips.

==Remote Access Software==
Software like TeamViewer, LogMeIn, and GoToMyPC are inexpensive remote access tools that allow you to connect to your PC via their website, thus from any other PC. Performance is a little slower than other solutions but is low cost, flexible and easy to use.

==[http://en.wikipedia.org/wiki/Remote_Desktop_Services Remote Desktop and Terminal Server]==
*Our preferred method is to use Windows' built-in remote access options. Remote Desktop (RDP) allows you to connect to your work machine with CMS on it and control it remotely. To do this you must first establish a virtual private network (VPN) connection.
*[http://www.emazzanti.net/the-12-advantages-of-terminal-services/ Terminal Services] is also an option that will allow you to VPN into your server and create/run a remote session right on the server and without the need for a dedicated workstation. This is also a popular option but does require purchasing Windows client access licenses (CALs). Note: Running CMS 8.0 or later on terminal services will require that you enable Windows themes. Also note that when running CMS in terminal services, all users share the same 'Workstation Specific' settings (In CMS see Setup>General>Workstation Specific to review these settings and assess if this trade-off is acceptable.)
*We've written a separate article on configuration recommendations for RDP - http://wiki.newhavensoftware.com/index.php/CMS_over_Microsoft_Remote_Desktop

==Cloud Computing==
===Licensing===
Only one database server can be running concurrently. Connections to that database server must come from the same domain. As stated above, CMS must be run on network local to the database server (i.e. you can remote into a vm, machine, or terminal server hosting CMS). You cannot run CMS locally and connect to a remote server.

===Peripherals===
While cloud deployment does not present any inherent challenges to CMS, there can be complications with getting a remote instance of CMS to properly interact with local hardware. While printers are commonly used and not typically a problem, communication with serial or USB devices (e.g. bar code scanners, scales, card swipes, pole displays) can be more challenging. Testing of existing/needed peripherals must be done before launching into production to ensure all users can continue to operate efficiently. We recommend you read our separate article on running CMS via RDP, including peripheral sharing, for some guidance that may be helpful - http://wiki.newhavensoftware.com/index.php/CMS_over_Microsoft_Remote_Desktop

===PCI Compliance===
There are PCI implications when moving your CMS database (which stores credit card data) to the cloud. It will add risk and corresponding cost/effort to mitigate that risk in order to remain PCI compliant. Here is a document from the PCI Council for guidance - https://www.pcisecuritystandards.org/pdfs/PCI_DSS_v2_Cloud_Guidelines.pdf

Another helpful article from TechTarget detailing some of the cloud deployment challenges stemming from the recent PCI-DSS 3.0 spec - http://searchcloudsecurity.techtarget.com/tip/PCI-DSS-30-Three-key-requirements-to-maintain-cloud-compliance

=Virtual Machines=
NewHaven Software will support CMS running on a virtual machine as long as the operating system (OS) running in the virtual machine is also supported. However, if NHS is unable to reproduce an issue, the customer may be asked to reproduce the problem running natively on the supported OS, outside the virtual environment. NHS does not explicitly test or certify products running in a virtual environment.

In other words, NHS can support CMS running in virtual environments but not the environments themselves. We strongly recommend that if you decide to pursue running virtual machines that you have someone with related expertise to assist with the setup and administration of these, much the same as you would network administration.

==Recommendations==
CMS can run on a virtual machine/server as long as it is provided enough resources (e.g. disk space, memory, processor). We in fact run CMS here at NewHaven Software on a virtual server and have had great success with it. We have been using VMware ESXi v4.0 and have also had successful tests with Xen Server 5.6 Feature Pack 1 although have yet to run CMS in production on Xen Server.

We also hope to look at [http://en.wikipedia.org/wiki/Desktop_virtualization VDI] in the future. We do have some CMS customers running live on a virtual server presently as well.

As a rule, CMS and the database server will run with no particular technical issues although performance is not as good as running on a dedicated non-virtual server. Reinforcing what has been said above, lots or RAM and fast drives (read/write) are the biggest factors that impact CMS performance. Our recommendations for running CMS on a virtual server simply are to ensure that sufficient resources are allocated.

If you think virtualization is in your future, please contact us for assistance in setting up a test environment. Before deploying into production we of course strongly recommend testing. You'll want to validate that performance is acceptable and that all connectivity, including from peripherals, and all integrations are working and performing at acceptable levels.

=3rd Party Software=
Many 3rd party software solutions can be used in conjunction with CMS but it is important to note that we do not support these software solutions. Examples of 3rd party software include Crystal Software, Microsoft Access, Mapforce, etc. The NHS technical staff is not responsible for answering any questions about features/functionality or bugs within these software programs. Please view your Software License and Support Agreement for details.

We are, however, happy to provide assistance as a professional service. For more details, please contact your account manager.

=FAQ's=
==Do I need a new machine to run CMS?==
Probably not. The operating system is far more important than your hardware. If your operating system is no longer supported by Microsoft, you may be able to update it or reinstall a supported operating system on your current machine. Please consult Microsoft for their minimum requirements for the operating system your selecting. Generally if it meets Microsoft's requirements for their operating system, it will be good enough for CMS as well. From there, you need to decide if good enough is in fact really good enough and that will be clear in the performance of Windows, CMS or other applications. Often times poor performance is a factor of limited memory and, since memory is typically quite cheap, you should consider maximizing RAM before replacing a machine.

==My operating system is currently supported, do I need a new machine?==
Hardware is rarely an issue with CMS and you could be running old machines and still experience reasonable performance. If you're satisfied with the speed of CMS, you're able to run a supported operating system without errors, and you have adequate disk space, you may choose to continue to run on your existing machine(s).

If you were to do only one thing, it should be to max the amount of RAM your machine will take. RAM is cheap, too cheap to not have plenty of it.

Secondarily, a CMS server needs a lot of disk space not just for its database but also requires additional free gigabytes of space for temp files that the database server creates and destroys through normal usage to optimize performance. You should never have less than 2x your database size in free drive space on your server (and this only considers CMS's needs, not Windows or other processes). Here too, drive space is too cheap for this to be a limiting factor.

There may be other compelling reasons to upgrade your machines, be it for speed, other applications or compatibility with other new technologies. New machines that are capable of running 64-bit operating systems, for example, are capable of handling more than 4 Gigabytes of RAM. While this would rarely be a CMS consideration for a workstation, if you have a database (.db file) that is larger than 2 Gig, you should seriously consider a server with more than 4G of RAM.

As a rule, the performance you need from CMS is merely a factor of hardware. As your company grows, CMS can scale perfectly well with you but may require improved hardware to keep up with the increased server load. Evaluating CPU/memory usage and free disk space during the heat of the day will give you an indication of how well your server is handling the load and if more resources are needed.

==Why can't I continue to use an older operating system?==
Even if has worked fine with CMS for years, if Microsoft no longer supports it, you really don't want to be using it. Once they stop offering security patches, as they just have stopped doing for Windows 2000, you become vulnerable to new threats (viruses, hacks, etc.) and you may find that CMS will no longer work. Such is the case with Windows 2000 as it does not contain the components need for CMS to run properly. [http://wiki.newhavensoftware.com/index.php/Windows_2000_and_CMS This link] provides more information on this subject.

PCI requirements also dictate that your systems must be kept up to date with current security patches.

==What is "database caching"?==
One of the great features of your CMS database is that it requires little to no maintenance. There is no re-indexing, server administration, etc. It largely just takes care of itself.

One thing you can do, however, to maximize your database performance is to use a setting for database caching. This option requires more RAM but RAM is cheap and the performance gains are worthwhile. With this option, you can force Windows to allocate a specific amount of RAM to your database to allows some or all of your database to be loaded into memory and thus can have significant affects on your server performance.

Limitations (applicable to v8 thru v12) are as follows:

*Maximum cache size for (Win32) Windows Server 2003 Web Edition, Windows Server 2003 Standard Edition, Windows 2008, Windows 7, Windows 8.1 - '''1.8 Gb'''

*Maximum cache size for (Win32) Windows Server 2003 Enterprise Edition, Windows Server 2003 Datacenter Edition, Windows Vista Ultimate, Windows Vista Enterprise, Windows Vista Business, Windows Vista Home Premium, Windows Vista Home Basic - '''2.7 Gb'''

*Maximum cache size (Win 64) limited by physical memory on 64-bit engines - ''NOTE: Our experience to date has shown that caching beyond 1.8G is not possible even with 64bit operating systems.''

Source - http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.sqlanywhere.12.0.0/dbadmin/da-limits.html

To update your cache size, you'll want to modify the registry key for the service (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASANYs_NHSDataService\Parameters) like this:
-n NHSDataServer "C:\NewHaven Software\Data\Company\Company.db" -c 1800M -ti 0 -tl 0

The above is a cache of 1800 Meg (1.8 Gig.) K, M and G are recognizable increments and they must be in caps. It does not accept decimals however so if you want 1.5G you should do 1500M as shown in the above example. You can experiment with other or higher values but if the service doesn't start you may need to back your number down or revert to an earlier setting.

If you're interested in this option and have enough RAM, please contact NewHaven Technical Support for information on how to enable this option.

==What about my network?==
Our recommendations here are pretty generic. If you're still on the old 10mbps cards you should consider upgrading. 1Gbps is pretty standard these days. CMS doesn't need a lot of bandwidth but could benefit from 100mbps over 10mbps...depending on what other network traffic you might expect. If you have hubs or old switches, that would be a good place to look at upgrading.

==Will CMS work with wireless?==
Yes, although CMS must maintain a constant connection with its database and even momentary interruptions in that connection can be enough to cause errors. As such, we do not recommend running CMS over a wireless network connection. You can, however, use Remote Desktop via wireless to connect to a machine that is on your physical network and, in that scenario, you would not be subject to disconnect issues.

==Can I run CMS remotely?==
Yes, but it must be done using RDP (remote desktop), terminal services or remote access software like Logmein. CMS must be running on the same network/domain as its database server. You'll need to remote into Windows first and then run CMS from that machine. You cannot have CMS installed locally and connect to a remote network/server. See the section on [http://wiki.newhavensoftware.com/index.php/CMS_System_Requirements#Remote_Connections remote connections] above.

==Can NewHaven Software assist with purchasing or configuring my hardware/network?==
We can make recommendations, like we have in this article, but the actual purchase, configuration and maintenance of your hardware and network must be performed by someone at your location. This would either be done by someone on staff that is capable or a local contractor that can provide these services and expertise to you. We're happy to consult with your staff or contractors on any CMS related configurations.

Arrival Date

2014-08-12T23:41:29Z

Luke steinmetzer: Created page with '=Overview= This Wiki will talk about the Arrival Date feature in CMS. =What are Arrival Dates?= CMS has always allowed you to schedule an item or order to ship on a future dat…'

=Overview=
This Wiki will talk about the Arrival Date feature in CMS.

=What are Arrival Dates?=

CMS has always allowed you to schedule an item or order to ship on a future date. In version 9.0 or later, you can instead select the date you'd like the item to arrive! CMS will then calculate the date it needs to ship based on your selected shipping method. Even if you choose not to set arrival dates, CMS will display estimated arrival dates for you on all orders, even those not future shipped.

The calculation of dates is fairly elaborate and takes into account both the days your company considers shipping days and the delivery days for the carriers. Also factored in are weekends, holidays, and user-defined non-shipping days (e.g. days you are closed for inventory, moving, etc.) You also have the option to pad the time in transit information from the carrier so, if UPS says that Ground to zone 4 is four days, you can pad it to 5 if you find they are often late to that zone or want some cushion to err on the early side.

=Why would you use Arrival Dates?=

In practice, the Arrival Date option is used as an alternative to choosing a Fulfill Date. In other words, you are in an Arrival Date mode or a Fulfill Date mode. Whichever mode you are in, CMS will calculate and display the counterpart date. So, if you choose an Arrival Date, CMS will also display the date it will fulfill, or vice versa.

=Arrival Date Setup Options=

*Ability for operators to specify arrival dates - Setup>Order Entry Options>Items
*Holidays and other non-shipping days - Setup>Fulfillment Options>Holidays
*Days in Transit and Cheapest Shipping options - Setup>Shipping>Carriers and Methods>Shipping Rules

[[Category:Blank]]

Address Matching in CMS

2014-07-23T20:05:20Z

Luke steinmetzer:

=Overview=
When an order or catalog request is imported into CMS, from any source, CMS must take steps to identify if this is a new or existing customer. If it is a new customer you'd want CMS to create a new customer record. On the other hand, if it is for an existing customer you'd want CMS to attach the order or catalog request to its matching/existing customer record and not create a duplicate customer.

This article explains the logic used by CMS uses when trying to determine that customer match during an import. A similar process is used to determine if the recipient (ship-to) is different from the buyer and this too is covered here.

=Matching orders to existing customers during order import=
All imported orders that are not imported with the [[Automated Imports Module]] option must go through a verification process (Fulfillment>Verify Imports) so you can ensure the imported order is one that should be converted into a real order. During that verification process you can tell if a customer match was found by looking at the Cust# field on the View Invoice screen (the first screen you are presented with when verifying an order.) If there is a number in this field you know CMS has matched it up to a customer in your mail list. If no match was found, the Cust# field will instead say "<new>".
The logic CMS uses to find such matches is as follows:
<ol>
<li>If a customer number was passed in the file, CMS will use that customer number to match against the customer number in CMS and will append to that customer. No further matching logic will be used. Most sources of orders will not be able to establish and/or pass the proper customer number so, while it will be considered the best match if present...it usually isn't.</li>
<li>The next matching will be done on email address (CMS 9.0.1 or later. To disable the option you need to be on CMS version 9.0.4 or later and then removing the check on the setup option under Fulfillment Options>Import). CMS will match the order to a unique customer record it finds with the same email address. If more than one customer record is found with the same email address, no match will be made by email address. '''Note:''' in the XML only the <nowiki><Order><Customer><ContactAddress><Address><Email></nowiki> element is used for email address matching</li>
<li>If no customer number or email match it is then up to CMS to scrutinize the name and address to find a match. In this case CMS will match the last name and all of the numbers from the address and 5 digit zip code. (Note: this matching is done by comparing the customer's mailing address against the order's mailing/primary address, not billing or shipping.) Only when there is a perfect match will CMS link the imported order to a customer. The reason CMS uses numbers only for the address and only a last name is to ensure the match does not get tripped up by middle initials, misspellings, punctuation and abbreviations. Here is an example:</li>
</ol>

<blockquote>
William Smith 
123 Main Street Apt 3 
Evanston, IL 60202-1234 
 
will still match 
 
Bill P. Smith 
123 Main St. #3 
Evenston, IL 60202
</blockquote>

If you should find that CMS has matched up an order to the wrong customer or did not find a customer that it should have, during the verification of the order you can still go to the first screen on the order (Customer) and retrieve the proper customer there. Be warned that when retrieving a customer in this manner it will replace the billing and shipping addresses from the imported order with the default addresses from the retrieved customer record. We expect this behavior to change in the future so CMS will retain the addresses from the imported order or give you the option which to use.

=Multi-recipient and Gift orders=
CMS is capable of handling and importing orders with multiple recipients and/or gift orders (where the recipient is different than the buyer.) In either of the two scenarios the purchaser may or may not be receiving merchandise themselves. When importing such orders, CMS needs to determine if the recipient(s) is the same as the purchaser or if they should be treated as someone else. The reason for this is CMS will can (optionally) create new customer records for recipients and when printing invoices/pick-tickets CMS will suppress prices from showing so the recipient will not see what you paid.

This is logic used to determine if the recipient is the same as the buyer works in the following ways:
<ol>
<li>In our XML specification document (CMSxml.xsd) there is an attribute of the <Recipient> tag that reads 'IsPurchaser'. If the system that is generating the output for CMS to import is capable, our first recommendation would be to use this attribute. In use it looks like: <Recipient IsPurchaser="false"> In this example the value of 'false' is telling CMS that the recipient is not the same as the purchaser and as such should treat this as a gift order, even if there are no gift notes. If the purchaser is shipping to themselves, even at a different address, this value should be 'true'.</li>
<li>If any gift notes are present, CMS assumes the buyer is not sending themselves a gift and will make the order a gift order (multiple ship-to, in this case with just one recipient.)</li>
<li>If there are no gift notes and there is no 'IsPurchaser' attribute passed, CMS then has to determine if the recipient and purchaser are the same or not. In this case CMS is only using the last name. If the last name matches exactly, CMS will treat the recipient as if they are the purchaser, even if the addresses or any other information is different. While there are a few scenarios where this logic fails (parents shipping to their kid at college) it is the best CMS can do without having the information from 1 and 2 above. It does ensure though that the more common scenario of a person shipping to themselves at another address (work, vacation, etc.) will be handled correctly as a normal, non-gift type order.</li>
</ol>

Note: CMS uses an internal address_id to uniquely identify the recipient in an order. This means the same customer/recipient cannot appear more than once in the order but otherwise there is no reason why you cannot have two recipients with the same name (as long as they are different customers.) This has changed in CMS 9.0 where you can now have the same recipient on the order multiple times.

=Customer Duplicate Report=

Also worthy of note is the Customer Duplicate report used for finding possible duplicates. This report is found in the Reports menu under the category Customers. The logic this report uses is a bit different than CMS's and can be a good tool to find those that made it past CMS's logic. The most notable difference in logic is that it is matching on physical or email address, not by name.

Matches are on state, city, 5-digit zipcode, then first 10 digits of either the address3 line or Address1 line, depending on which has data.

This system has a lot of merit in that it is total independent of name spellings or most cases of address spellings (even St vs Street) since only the first 10 characters are considered. (UPDATE: As of CMS 8.0 this report now allows you to select how many characters to consider which allows you to control the level of sensitivity.) This system is really matching on the address vs the customer so if you had a husband and wife with diff names at the same address, you'd find them as a possible dupe match. This should prove to be a good tool to find duplicates that escaped CMS's customer matching (or dupes created by operators for non-imported orders.)

Alternate search terms - customer matching, order imports, order importing, name matching

ECMS Templates

2014-07-17T15:40:58Z

Luke steinmetzer:

==What is a template?==

eCMS uses the [http://www.smarty.net/ Smarty] template system. Smarty is [http://www.php.net PHP] based and is currently the most popular templating system of it's kind. Template allow you to easily control the presentation (visual) layer of your site without the need understand the application (logic) layer.

From the Smarty [http://smarty.incutio.com/?page=SmartyFrequentlyAskedQuestions#basics-1 FAQ Page:]

'''Q: What's a template engine and why should I use one?'''

A: (copied from Smarty manual)

Smarty is a template engine for PHP. More specifically, it facilitates a managable way to separate application logic and content from its presentation. This is best described in a situation where the application programmer and the template designer play different roles, or in most cases are not the same person. For example, let's say you are creating a web page that is displaying a newspaper article. The article headline, tagline, author and body are content elements, they contain no information about how they will be presented. They are passed into Smarty by the application, then the template designer edits the templates and uses a combination of HTML tags and template tags to format the presentation of these elements (HTML tables, background colors, font sizes, style sheets, etc.) One day the programmer needs to change the way the article content is retrieved (a change in application logic.) This change does not affect the template designer, the content will still arrive in the template exactly the same. Likewise, if the template designer wants to completely redesign the templates, this requires no changes to the application logic. Therefore, the programmer can make changes to the application logic without the need to restructure templates, and the template designer can make changes to templates without breaking application logic.[http://smarty.incutio.com/?page=SmartyFrequentlyAskedQuestions#basics-1]

==Additional Resources==

* [http://www.smarty.net Smarty.net] - The main site for the Smarty product. Here you can find a vast amount of documentation.
* [http://smarty.incutio.com/?page=SmartyFrequentlyAskedQuestions Smarty Frequently Asked Questions (FAQ)] - A list of commonly asked questions related to Smarty.
* [http://www.smarty.net/manual/en/smarty.for.designers.php Smarty Documentation (for Designers] - All site have this level of access to the Smarty template system.
* [http://www.smarty.net/docs.php All Smarty.net docs] - This includes printable versions of Smarty documentation.
* [http://www.smarty.net/forums/ Smarty Forums] - Come here to ask questions or if want to see how others may have come up with a solution.
* [http://www.smarty.net/resources.php Smarty Mailing Lists] - Great way to learn more about how people are using Smarty. There is also a searchable archive

ECMS Templates

2014-07-17T15:40:33Z

Luke steinmetzer:

==What is a template?==

eCMS uses the [http://www.smarty.net/ Smarty] template system. Smarty is [http://www.php.net PHP] based and is currently the most popular templating system of it's kind. Template allow you to easily control the presentation (visual) layer of your site without the need understand the application (logic) layer.

From the Smarty [http://smarty.incutio.com/?page=SmartyFrequentlyAskedQuestions#basics-1 FAQ Page:]

'''Q: What's a template engine and why should I use one?'''

A: (copied from Smarty manual)

Smarty is a template engine for PHP. More specifically, it facilitates a managable way to separate application logic and content from its presentation. This is best described in a situation where the application programmer and the template designer play different roles, or in most cases are not the same person. For example, let's say you are creating a web page that is displaying a newspaper article. The article headline, tagline, author and body are content elements, they contain no information about how they will be presented. They are passed into Smarty by the application, then the template designer edits the templates and uses a combination of HTML tags and template tags to format the presentation of these elements (HTML tables, background colors, font sizes, style sheets, etc.) One day the programmer needs to change the way the article content is retrieved (a change in application logic.) This change does not affect the template designer, the content will still arrive in the template exactly the same. Likewise, if the template designer wants to completely redesign the templates, this requires no changes to the application logic. Therefore, the programmer can make changes to the application logic without the need to restructure templates, and the template designer can make changes to templates without breaking application logic.[http://smarty.incutio.com/?page=SmartyFrequentlyAskedQuestions#basics-1]

== Template upgrades ==
Some eCMS features require either us or Cv3 to process a template upgrade for a customer. You can see an example of this below:

[[image:Template_upgrade_example.png]]

 

To enable this feature the customer will need to get in touch with either us or Cv3 to upgrade that template. If we are the ones to publish this template, that upgrade message will remain until we get in touch with Cv3. As a result we typically request that customers who encounter this message get in touch with us to verify that the templates are enabled and so we can get the message removed.

==Additional Resources==

* [http://www.smarty.net Smarty.net] - The main site for the Smarty product. Here you can find a vast amount of documentation.
* [http://smarty.incutio.com/?page=SmartyFrequentlyAskedQuestions Smarty Frequently Asked Questions (FAQ)] - A list of commonly asked questions related to Smarty.
* [http://www.smarty.net/manual/en/smarty.for.designers.php Smarty Documentation (for Designers] - All site have this level of access to the Smarty template system.
* [http://www.smarty.net/docs.php All Smarty.net docs] - This includes printable versions of Smarty documentation.
* [http://www.smarty.net/forums/ Smarty Forums] - Come here to ask questions or if want to see how others may have come up with a solution.
* [http://www.smarty.net/resources.php Smarty Mailing Lists] - Great way to learn more about how people are using Smarty. There is also a searchable archive

ECMS Templates

2014-07-17T15:38:00Z

Luke steinmetzer:

==What is a template?==

eCMS uses the [http://www.smarty.net/ Smarty] template system. Smarty is [http://www.php.net PHP] based and is currently the most popular templating system of it's kind. Template allow you to easily control the presentation (visual) layer of your site without the need understand the application (logic) layer.

From the Smarty [http://smarty.incutio.com/?page=SmartyFrequentlyAskedQuestions#basics-1 FAQ Page:]

'''Q: What's a template engine and why should I use one?'''

A: (copied from Smarty manual)

Smarty is a template engine for PHP. More specifically, it facilitates a managable way to separate application logic and content from its presentation. This is best described in a situation where the application programmer and the template designer play different roles, or in most cases are not the same person. For example, let's say you are creating a web page that is displaying a newspaper article. The article headline, tagline, author and body are content elements, they contain no information about how they will be presented. They are passed into Smarty by the application, then the template designer edits the templates and uses a combination of HTML tags and template tags to format the presentation of these elements (HTML tables, background colors, font sizes, style sheets, etc.) One day the programmer needs to change the way the article content is retrieved (a change in application logic.) This change does not affect the template designer, the content will still arrive in the template exactly the same. Likewise, if the template designer wants to completely redesign the templates, this requires no changes to the application logic. Therefore, the programmer can make changes to the application logic without the need to restructure templates, and the template designer can make changes to templates without breaking application logic.[http://smarty.incutio.com/?page=SmartyFrequentlyAskedQuestions#basics-1]

== Template upgrades ==
Some eCMS features require either us or Cv3 to process a template upgrade for a customer. You can see an example of this below:

[[image:Template_upgrade_example.png]]
 

To enable this feature the customer will need to get in touch with either us or Cv3 to upgrade that template. If we are the ones to publish this template, that upgrade message will remain until we get in touch with Cv3. As a result we typically request that customers who encounter this message get in touch with us to verify that the templates are enabled and so we can get the message removed.

==Additional Resources==

* [http://www.smarty.net Smarty.net] - The main site for the Smarty product. Here you can find a vast amount of documentation.
* [http://smarty.incutio.com/?page=SmartyFrequentlyAskedQuestions Smarty Frequently Asked Questions (FAQ)] - A list of commonly asked questions related to Smarty.
* [http://www.smarty.net/manual/en/smarty.for.designers.php Smarty Documentation (for Designers] - All site have this level of access to the Smarty template system.
* [http://www.smarty.net/docs.php All Smarty.net docs] - This includes printable versions of Smarty documentation.
* [http://www.smarty.net/forums/ Smarty Forums] - Come here to ask questions or if want to see how others may have come up with a solution.
* [http://www.smarty.net/resources.php Smarty Mailing Lists] - Great way to learn more about how people are using Smarty. There is also a searchable archive

CMS Setup

2014-03-18T18:03:15Z

Luke steinmetzer:

:1. [[CMS Setup]] (37)
::1.1. CMS Install (44)
:::1.1.1. [[Server_Update|CMS Server Install/Update]] (44)
:::1.1.2. [[Workstation_Install]] (44)
:::1.1.3. [[Moving_CMS_to_a_New_Server]] (44)
:::1.1.4. [https://updates.newhavensoftware.com/ CMS Update Page] (44)
::1.2. CMS Backups (44)
:::1.2.1. [[Creating_a_Database_Backup]] (44)
:::1.2.2. [http://updates.newhavensoftware.com/videos/CMS-5-Creating-Backup/CMS-5-Creating-Backup.htm/ CMS v5 Backup creation] (44)
:::1.2.3. [http://updates.newhavensoftware.com/videos/Rpt-YearEndReporting-BU/Rpt-YearEndReporting-BU.htm/ CMS Year End Reporting backup creation] (44)
::1.3. CMS Company Information (44)
:::1.3.1. [http://updates.newhavensoftware.com/videos/CMS-5-Email-Order-Confirmations/CMS-5-Email-Order-Confirmations.htm/ CMS Order Confirmation Email setup] (44)
:::1.3.2. [[Setting_up_CMS_email_through_Exchange]] (44)
::1.4. CMS Accounting (44)
:::1.4.1. [http://site.newhavensoftware.com/video-tutorials/cms-year-end-reporting-review/ CMS End of Year Reporting Review] (44)
:::1.4.2. [http://site.newhavensoftware.com/video-tutorials/reporting-payment-audit-report-update/ Payment Audit Report] (44)
:::1.4.3. [http://site.newhavensoftware.com/video-tutorials/reporting-ar-aging-report-update/ AR Aging Report] (44)
:::1.4.4. [http://site.newhavensoftware.com/video-tutorials/reporting-ar-aging-customer-report-update/ AR Aging by Customer Report] (44)
::1.5.[CMS Shipping (44)
:::1.5.1. [[UPS_WorldShip]] (44)
:::1.5.2. [[UPS_Shipping_XML]] (44)
:::1.5.3. [[FedEx_Ship_Manager]] (44)
:::1.5.4. [http://updates.newhavensoftware.com/videos/CMS-Endicia-Setup-and%20-Integration/CMS-Endicia-Setup-and%20-Integration.htm/ Dazzle Setup Video] (44)
:::1.5.5. [[Dazzle|Dazzle/Endicia]] (44)
::1.6. CMS Inventory (44)
:::1.6.1. [http://site.newhavensoftware.com/video-tutorials/reporting-inventory-tracking-report.htm/ Inventory Tracking Report] (44)
::1.7. CMS Fulfillment (44)
:::1.7.1. [http://updates.newhavensoftware.com/videos/CMS-5-Setup-Crystal-Invoices/CMS-5-Setup-Crystal-Invoices.htm/ CMS v5 Crystal Invoice Setup] (44)
::1.8. CMS Advertising (44)
:::1.8.1. [[Compound_Mail_List_Filters]] (44)
::1.9. CMS Point of Sale (44)
:::1.9.1. [[CMS_System_Requirements#POS_Module|POS_Hardware]] (44)
:::1.9.2. [[POS_Module]] (44)

Main Page

2014-03-18T18:02:34Z

Luke steinmetzer:

NewHaven Software Wiki

 

==Introduction==
Thank you for visiting our wiki! We want to help provide answers to some of the common questions regarding our [http://www.newhavensoftware.com/cmspro Commerce Management System (CMS)] and our integrated [http://www.newhavensoftware.com/ecms shopping cart eCMS]. Besides this wiki CMS also has an internal help system that we regularly update. Currently this is a closed wiki so it cannot be edited by anyone other than NewHaven Software, but if you would like to contribute or make any suggestions please let us know.

==Wiki Overview==
The following links are to help you find the information you are looking for.

<div style="float: left; margin-right: 1%; width: 49%">
; [[CMS]]: Information related to CMS Use, setup, and troubleshooting.

; [[Newest Articles Added]]: Select this option to see a list of the latest articles.

</div>

<div style="float: left; width: 50%">
; [[PCI Compliance]]: For information on our commitment to security please see our detailed [[PCI Compliance]] article.

; [[ECMS_Help|Web]]: Information related to CMS web integrations, use, setup, and troubleshooting.

<div style="clear: both"></div>

Main Page

2014-03-18T18:00:08Z

Luke steinmetzer:

NewHaven Software Wiki

 

==Introduction==
Thank you for visiting our wiki! We want to help provide answers to some of the common questions regarding our [http://www.newhavensoftware.com/cmspro Commerce Management System (CMS)] and our integrated [http://www.newhavensoftware.com/ecms shopping cart eCMS]. Besides this wiki CMS also has an internal help system that we regularly update. Currently this is a closed wiki so it cannot be edited by anyone other than NewHaven Software, but if you would like to contribute or make any suggestions please let us know.

==Wiki Overview==
The following links are to help you find the information you are looking for.

<div style="float: left; margin-right: 1%; width: 49%">
; [[CMS]]: Information related to CMS Use, setup, and troubleshooting.

; [[Newest Articles Added]]: Select this option to see a list of the latest articles.

</div>

<div style="float: left; width: 50%">
; [[PCI Compliance]]: For information on our commitment to security please see our detailed [[PCI Compliance]] article.

; [[ECMS_Help|Web]]: Information related to CMS web integrations, there use, setup, and troubleshooting.

<div style="clear: both"></div>

Main Page

2014-03-18T17:59:23Z

Luke steinmetzer:

NewHaven Internal Wiki

 

==Introduction==
Thank you for visiting our wiki! We want to help provide answers to some of the common questions regarding our [http://www.newhavensoftware.com/cmspro Commerce Management System (CMS)] and our integrated [http://www.newhavensoftware.com/ecms shopping cart eCMS]. Besides this wiki CMS also has an internal help system that we regularly update. Currently this is a closed wiki so it cannot be edited by anyone other than NewHaven Software, but if you would like to contribute or make any suggestions please let us know.

==Wiki Overview==
The following links are to help you find the information you are looking for.

<div style="float: left; margin-right: 1%; width: 49%">
; [[CMS]]: Information related to CMS Use, setup, and troubleshooting.

; [[Newest Articles Added]]: Select this option to see a list of the latest articles.

</div>

<div style="float: left; width: 50%">
; [[PCI Compliance]]: For information on our commitment to security please see our detailed [[PCI Compliance]] article.

; [[ECMS_Help|Web]]: Information related to CMS web integrations, there use, setup, and troubleshooting.

<div style="clear: both"></div>

CMS Setup

2014-03-18T17:58:49Z

Luke steinmetzer:

:1. [[CMS Setup]] (37)
::1.1. CMS Install (44)
:::1.1.1. [[Server_Update|CMS Server Install/Update]] (44)
:::1.1.2. [[Workstation_Install]] (44)
:::1.1.3. [[Moving_CMS_to_a_New_Server]] (44)
:::1.1.4. [https://updates.newhavensoftware.com/ CMS Update Page] (44)
::1.2. CMS Backups (44)
:::1.2.1. [[Creating_a_Database_Backup]] (44)
:::1.2.2. [http://updates.newhavensoftware.com/videos/CMS-5-Creating-Backup/CMS-5-Creating-Backup.htm/ CMS v5 Backup creation] (44)
:::1.2.3. [http://updates.newhavensoftware.com/videos/Rpt-YearEndReporting-BU/Rpt-YearEndReporting-BU.htm/ CMS Year End Reporting backup creation] (44)
::1.3. CMS Company Information (44)
:::1.3.1. [http://updates.newhavensoftware.com/videos/CMS-5-Email-Order-Confirmations/CMS-5-Email-Order-Confirmations.htm/ CMS Order Confirmation Email setup] (44)
:::1.3.2. Setting_up_CMS_email_through_Exchange (44)
::1.4. CMS Accounting (44)
:::1.4.1. [http://site.newhavensoftware.com/video-tutorials/cms-year-end-reporting-review/ CMS End of Year Reporting Review] (44)
:::1.4.2. [http://site.newhavensoftware.com/video-tutorials/reporting-payment-audit-report-update/ Payment Audit Report] (44)
:::1.4.3. [http://site.newhavensoftware.com/video-tutorials/reporting-ar-aging-report-update/ AR Aging Report] (44)
:::1.4.4. [http://site.newhavensoftware.com/video-tutorials/reporting-ar-aging-customer-report-update/ AR Aging by Customer Report] (44)
::1.5.[CMS Shipping (44)
:::1.5.1. [[UPS_WorldShip]] (44)
:::1.5.2. [[UPS_Shipping_XML]] (44)
:::1.5.3. [[FedEx_Ship_Manager]] (44)
:::1.5.4. [http://updates.newhavensoftware.com/videos/CMS-Endicia-Setup-and%20-Integration/CMS-Endicia-Setup-and%20-Integration.htm/ Dazzle Setup Video] (44)
:::1.5.5. [[Dazzle|Dazzle/Endicia]] (44)
::1.6. CMS Inventory (44)
:::1.6.1. [http://site.newhavensoftware.com/video-tutorials/reporting-inventory-tracking-report.htm/ Inventory Tracking Report] (44)
::1.7. CMS Fulfillment (44)
:::1.7.1. [http://updates.newhavensoftware.com/videos/CMS-5-Setup-Crystal-Invoices/CMS-5-Setup-Crystal-Invoices.htm/ CMS v5 Crystal Invoice Setup] (44)
::1.8. CMS Advertising (44)
:::1.8.1. [[Compound_Mail_List_Filters]] (44)
::1.9. CMS Point of Sale (44)
:::1.9.1. [[CMS_System_Requirements#POS_Module|POS_Hardware]] (44)
:::1.9.2. [[POS_Module]] (44)

CMS Setup

2014-03-18T17:58:23Z

Luke steinmetzer:

:1. [[CMS Setup]] (37)
::1.1. CMS Install (44)
:::1.1.1. [[Server_Update|CMS Server Install/Update]] (44)
:::1.1.2. [[Workstation_Install]] (44)
:::1.1.3. [[Moving_CMS_to_a_New_Server]] (44)
:::1.1.4. [https://updates.newhavensoftware.com/ CMS Update Page] (44)
::1.2. CMS Backups (44)
:::1.2.1. [[Creating_a_Database_Backup]] (44)
:::1.2.2. [http://updates.newhavensoftware.com/videos/CMS-5-Creating-Backup/CMS-5-Creating-Backup.htm/ CMS v5 Backup creation] (44)
:::1.2.3. [http://updates.newhavensoftware.com/videos/Rpt-YearEndReporting-BU/Rpt-YearEndReporting-BU.htm/ CMS Year End Reporting backup creation] (44)
::1.3. CMS Company Information (44)
:::1.3.1. [http://updates.newhavensoftware.com/videos/CMS-5-Email-Order-Confirmations/CMS-5-Email-Order-Confirmations.htm/ CMS Order Confirmation Email setup] (44)
:::1.3.2. Setting_up_CMS_email_through_Exchange (44)
::1.4. CMS Accounting (44)
:::1.4.1. [http://site.newhavensoftware.com/video-tutorials/cms-year-end-reporting-review/ CMS End of Year Reporting Review] (44)
:::1.4.2. [http://site.newhavensoftware.com/video-tutorials/reporting-payment-audit-report-update/ Payment Audit Report] (44)
:::1.4.3. [http://site.newhavensoftware.com/video-tutorials/reporting-ar-aging-report-update/ AR Aging Report] (44)
:::1.4.4. [http://site.newhavensoftware.com/video-tutorials/reporting-ar-aging-customer-report-update/ AR Aging by Customer Report] (44)
::1.5.[CMS Shipping (44)
:::1.5.1. [[UPS_WorldShip]] (44)
:::1.5.2. [[UPS_Shipping_XML]] (44)
:::1.5.3. [[FedEx_Ship_Manager]] (44)
:::1.5.4. [http://updates.newhavensoftware.com/videos/CMS-Endicia-Setup-and%20-Integration/CMS-Endicia-Setup-and%20-Integration.htm/ Dazzle Setup Video] (44)
:::1.5.5. [[Dazzle/Endicia]] (44)
::1.6. CMS Inventory (44)
:::1.6.1. [http://site.newhavensoftware.com/video-tutorials/reporting-inventory-tracking-report.htm/ Inventory Tracking Report] (44)
::1.7. CMS Fulfillment (44)
:::1.7.1. [http://updates.newhavensoftware.com/videos/CMS-5-Setup-Crystal-Invoices/CMS-5-Setup-Crystal-Invoices.htm/ CMS v5 Crystal Invoice Setup] (44)
::1.8. CMS Advertising (44)
:::1.8.1. [[Compound_Mail_List_Filters]] (44)
::1.9. CMS Point of Sale (44)
:::1.9.1. [[CMS_System_Requirements#POS_Module|POS_Hardware]] (44)
:::1.9.2. [[POS_Module]] (44)

CMS Setup

2014-03-18T17:57:17Z

Luke steinmetzer:

:1. [[CMS Setup]] (37)
::1.1. CMS Install (44)
:::1.1.1. [[Server_Update|CMS Server Install/Update]] (44)
:::1.1.2. [[Workstation_Install]] (44)
:::1.1.3. [[Moving_CMS_to_a_New_Server]] (44)
:::1.1.4. [https://updates.newhavensoftware.com/ CMS Update Page] (44)
::1.2. CMS Backups (44)
:::1.2.1. [[Creating_a_Database_Backup]] (44)
:::1.2.2. [http://updates.newhavensoftware.com/videos/CMS-5-Creating-Backup/CMS-5-Creating-Backup.htm/ CMS v5 Backup creation] (44)
:::1.2.3. [http://updates.newhavensoftware.com/videos/Rpt-YearEndReporting-BU/Rpt-YearEndReporting-BU.htm/ CMS Year End Reporting backup creation] (44)
::1.3. CMS Company Information (44)
:::1.3.1. [http://updates.newhavensoftware.com/videos/CMS-5-Email-Order-Confirmations/CMS-5-Email-Order-Confirmations.htm/ CMS Order Confirmation Email setup] (44)
:::1.3.2. Setting_up_CMS_email_through_Exchange (44)
::1.4. CMS Accounting (44)
:::1.4.1. [http://site.newhavensoftware.com/video-tutorials/cms-year-end-reporting-review/ CMS End of Year Reporting Review] (44)
:::1.4.2. [http://site.newhavensoftware.com/video-tutorials/reporting-payment-audit-report-update/ Payment Audit Report] (44)
:::1.4.3. [http://site.newhavensoftware.com/video-tutorials/reporting-ar-aging-report-update/ AR Aging Report] (44)
:::1.4.4. [http://site.newhavensoftware.com/video-tutorials/reporting-ar-aging-customer-report-update/ AR Aging by Customer Report] (44)
::1.5.[CMS Shipping (44)
:::1.5.1. [[UPS_WorldShip]] (44)
:::1.5.2. [[UPS_Shipping_XML]] (44)
:::1.5.3. [[FedEx_Ship_Manager]] (44)
:::1.5.4. [http://updates.newhavensoftware.com/videos/CMS-Endicia-Setup-and%20-Integration/CMS-Endicia-Setup-and%20-Integration.htm/ Dazzle Setup Video] (44)
:::1.5.5. [[Dazzle]] (44)
:::1.5.6. [[USPS_Endicia_System_Install%2C_Setup_and_CMS_Integration]] (44)
::1.6. CMS Inventory (44)
:::1.6.1. [http://site.newhavensoftware.com/video-tutorials/reporting-inventory-tracking-report.htm/ Inventory Tracking Report] (44)
::1.7. CMS Fulfillment (44)
:::1.7.1. [http://updates.newhavensoftware.com/videos/CMS-5-Setup-Crystal-Invoices/CMS-5-Setup-Crystal-Invoices.htm/ CMS v5 Crystal Invoice Setup] (44)
::1.8. CMS Advertising (44)
:::1.8.1. [[Compound_Mail_List_Filters]] (44)
::1.9. [[CMS Point of Sale]] (44)
:::1.9.1. [[CMS_System_Requirements#POS_Module|POS_Hardware]] (44)
:::1.9.2. [[POS_Module]] (44)

CMS Setup

2014-03-18T17:56:11Z

Luke steinmetzer:

:1. [[CMS Setup]] (37)
::1.1. CMS Install (44)
:::1.1.1. [[Server_Update|CMS Server Install/Update]] (44)
:::1.1.2. [[Workstation_Install]] (44)
:::1.1.3. [[Moving_CMS_to_a_New_Server]] (44)
:::1.1.4. [https://updates.newhavensoftware.com/ CMS Update Page] (44)
::1.2. CMS Backups (44)
:::1.2.1. [[Creating_a_Database_Backup]] (44)
:::1.2.2. [http://updates.newhavensoftware.com/videos/CMS-5-Creating-Backup/CMS-5-Creating-Backup.htm/ CMS v5 Backup creation] (44)
:::1.2.3. [http://updates.newhavensoftware.com/videos/Rpt-YearEndReporting-BU/Rpt-YearEndReporting-BU.htm/ CMS Year End Reporting backup creation] (44)
::1.3. CMS Company Information (44)
:::1.3.1. [http://updates.newhavensoftware.com/videos/CMS-5-Email-Order-Confirmations/CMS-5-Email-Order-Confirmations.htm/ CMS Order Confirmation Email setup] (44)
:::1.3.2. Setting_up_CMS_email_through_Exchange (44)
::1.4. CMS Accounting (44)
:::1.4.1. [http://site.newhavensoftware.com/video-tutorials/cms-year-end-reporting-review/ CMS End of Year Reporting Review] (44)
:::1.4.2. [http://site.newhavensoftware.com/video-tutorials/reporting-payment-audit-report-update/ Payment Audit Report] (44)
:::1.4.3. [http://site.newhavensoftware.com/video-tutorials/reporting-ar-aging-report-update/ AR Aging Report] (44)
:::1.4.4. [http://site.newhavensoftware.com/video-tutorials/reporting-ar-aging-customer-report-update/ AR Aging by Customer Report] (44)
::1.5.[CMS Shipping (44)
:::1.5.1. [[UPS_WorldShip]] (44)
:::1.5.2. [[UPS_Shipping_XML]] (44)
:::1.5.3. [[FedEx_Ship_Manager]] (44)
:::1.5.4. [http://updates.newhavensoftware.com/videos/CMS-Endicia-Setup-and%20-Integration/CMS-Endicia-Setup-and%20-Integration.htm/ Dazzle Setup Video] (44)
:::1.5.5. [[Dazzle]] (44)
:::1.5.6. [[USPS_Endicia_System_Install%2C_Setup_and_CMS_Integration]] (44)
::1.6. CMS Inventory (44)
:::1.6.1. [http://site.newhavensoftware.com/video-tutorials/reporting-inventory-tracking-report.htm/ Inventory Tracking Report] (44)
::1.7. [[CMS Customers]] (44)
::1.8. [[CMS Order Entry]] (44)
::1.9. [[CMS Payment]] (44)
::1.10. CMS Fulfillment (44)
:::1.10.1. [http://updates.newhavensoftware.com/videos/CMS-5-Setup-Crystal-Invoices/CMS-5-Setup-Crystal-Invoices.htm/ CMS v5 Crystal Invoice Setup] (44)
::1.11. CMS Advertising (44)
:::1.11.1. [[Compound_Mail_List_Filters]] (44)
::1.12. [[CMS Point of Sale]] (44)
:::1.12.1. [[CMS_System_Requirements#POS_Module|POS_Hardware]] (44)
:::1.12.2. [[POS_Module]] (44)

CMS Use

2014-03-18T17:54:10Z

Luke steinmetzer:

:1. [[CMS Use]] (37)
::1.1. Order Entry (44)
:::1.1.1. [http://updates.newhavensoftware.com/videos/CMS-Contact-Manager-and-Basic-Order-Entry/CMS-Contact-Manager-and-Basic-Order-Entry.htm/ CMS Contact Manager and Basic Order Entry] (44)
::1.2. Customer Management (44)
:::1.2.1. [[CMS_Customer_Filter_for_customers_with_a_specific_item_on_Back_Order]] (44)
:::1.2.2. [[Customer_Searches]] (44)
:::1.2.3. [[Exporting_customer_list_from_CMS]] (44)
::1.3. Product management (44)
:::1.3.1. [[Kit_Builder]] (44)
::1.4. Address Verification (44)
:::1.4.1. [http://site.newhavensoftware.com/video-tutorials/address-validation-module-demonstration/ Address Validation Module] (44)
:::1.4.2. [[Address_Validation_Module]] (44)
:::1.4.3. [[Address_Matching_in_CMS]] (44)
::1.5. Fulfillment (44)
:::1.5.1. [[Package_Creation_Logic]] (44)
:::1.5.1. [http://updates.newhavensoftware.com/videos/CMS-Overview-Fulfillment/CMS-Overview-Fulfillment.htm/ CMS Fulfillment Overview] (44)
::1.6. Advertising Analysis (44)
:::1.6.1. [[NCOA]] (44)
::1.7. CMS reports (44)
:::1.7.1. [[End_of_Year_Reporting]] (44)

CMS Use

2014-03-18T17:50:55Z

Luke steinmetzer: Created page with ':1. CMS Use (37) ::1.1. General Navigation (44) ::1.2. Order Entry (44) :::<…'

:1. [[CMS Use]] (37)
::1.1. [[General Navigation]] (44)
::1.2. [[Order Entry]] (44)
:::1.2.1. [http://updates.newhavensoftware.com/videos/CMS-Contact-Manager-and-Basic-Order-Entry/CMS-Contact-Manager-and-Basic-Order-Entry.htm/ CMS Contact Manager and Basic Order Entry] (44)
::1.3. [[Customer Management]] (44)
:::1.3.1. [[CMS_Customer_Filter_for_customers_with_a_specific_item_on_Back_Order]] (44)
:::1.3.2. [[Customer_Searches]] (44)
:::1.3.3. [[Exporting_customer_list_from_CMS]] (44)
::1.4. [[Product management]] (44)
:::1.4.1. [[Kit_Builder]] (44)
::1.5. [[Inventory Management]] (44)
::1.6. [[Address Verification]] (44)
:::1.6.1. [http://site.newhavensoftware.com/video-tutorials/address-validation-module-demonstration/ Address Validation Module] (44)
:::1.6.2. [[Address_Validation_Module]] (44)
:::1.6.3. [[Address_Matching_in_CMS]] (44)
::1.7. [[Fulfillment]] (44)
:::1.7.1. [[Package_Creation_Logic]] (44)
:::1.7.1. [http://updates.newhavensoftware.com/videos/CMS-Overview-Fulfillment/CMS-Overview-Fulfillment.htm/ CMS Fulfillment Overview] (44)
::1.8. [[Advertising Analysis]] (44)
:::1.8.1. [[NCOA]] (44)
::1.9. [[Accounting]] (44)
::1.10. [[CMS reports]] (44)
:::1.10.1. [[End_of_Year_Reporting]] (44)

CMS Setup

2014-03-18T17:50:13Z

Luke steinmetzer: Created page with ':1. CMS Setup (37) ::1.1. CMS Install (44) :::1.1.1. [[Server_Update|CMS Server Install/Update]…'

:1. [[CMS Setup]] (37)
::1.1. [[CMS Install]] (44)
:::1.1.1. [[Server_Update|CMS Server Install/Update]] (44)
:::1.1.2. [[Workstation_Install]] (44)
:::1.1.3. [[Moving_CMS_to_a_New_Server]] (44)
:::1.1.4. [https://updates.newhavensoftware.com/ CMS Update Page] (44)
::1.2. [[CMS Backups]] (44)
:::1.2.1. [[Creating_a_Database_Backup]] (44)
:::1.2.2. [http://updates.newhavensoftware.com/videos/CMS-5-Creating-Backup/CMS-5-Creating-Backup.htm/ CMS v5 Backup creation] (44)
:::1.2.3. [http://updates.newhavensoftware.com/videos/Rpt-YearEndReporting-BU/Rpt-YearEndReporting-BU.htm/ CMS Year End Reporting backup creation] (44)
::1.3. [[CMS Company Information]] (44)
:::1.3.1. [http://updates.newhavensoftware.com/videos/CMS-5-Email-Order-Confirmations/CMS-5-Email-Order-Confirmations.htm/ CMS Order Confirmation Email setup] (44)
:::1.3.2. [[Setting_up_CMS_email_through_Exchange]] (44)
::1.4. [[CMS Accounting]] (44)
:::1.4.1. [http://site.newhavensoftware.com/video-tutorials/cms-year-end-reporting-review/ CMS End of Year Reporting Review] (44)
:::1.4.2. [http://site.newhavensoftware.com/video-tutorials/reporting-payment-audit-report-update/ Payment Audit Report] (44)
:::1.4.3. [http://site.newhavensoftware.com/video-tutorials/reporting-ar-aging-report-update/ AR Aging Report] (44)
:::1.4.4. [http://site.newhavensoftware.com/video-tutorials/reporting-ar-aging-customer-report-update/ AR Aging by Customer Report] (44)
::1.5. [[CMS Shipping]] (44)
:::1.5.1. [[UPS_WorldShip]] (44)
:::1.5.2. [[UPS_Shipping_XML]] (44)
:::1.5.3. [[FedEx_Ship_Manager]] (44)
:::1.5.4. [http://updates.newhavensoftware.com/videos/CMS-Endicia-Setup-and%20-Integration/CMS-Endicia-Setup-and%20-Integration.htm/ Dazzle Setup Video] (44)
:::1.5.5. [[Dazzle]] (44)
:::1.5.6. [[USPS_Endicia_System_Install%2C_Setup_and_CMS_Integration]] (44)
::1.6. [[CMS Inventory]] (44)
:::1.6.1. [http://site.newhavensoftware.com/video-tutorials/reporting-inventory-tracking-report.htm/ Inventory Tracking Report] (44)
::1.7. [[CMS Customers]] (44)
::1.8. [[CMS Order Entry]] (44)
::1.9. [[CMS Payment]] (44)
::1.10. [[CMS Fulfillment]] (44)
:::1.10.1. [http://updates.newhavensoftware.com/videos/CMS-5-Setup-Crystal-Invoices/CMS-5-Setup-Crystal-Invoices.htm/ CMS v5 Crystal Invoice Setup] (44)
::1.11. [[CMS Advertising]] (44)
:::1.11.1. [[Compound_Mail_List_Filters]] (44)
::1.12. [[CMS General]] (44)
::1.13. [[CMS Point of Sale]] (44)
:::1.13.1. [[CMS_System_Requirements#POS_Module|POS_Hardware]] (44)
:::1.13.2. [[POS_Module]] (44)

CMS

2014-03-18T17:49:23Z

Luke steinmetzer: Created page with '==Overview== This page will provide links with information on a variety of topics to assist you in setting up, running, and working with CMS. <div style="float: left; margin-ri…'

==Overview==
This page will provide links with information on a variety of topics to assist you in setting up, running, and working with CMS.

<div style="float: left; margin-right: 1%; width: 49%">
; [[CMS Setup]]: Select the above link for general information on setting up and installing CMS. This includes updating your license code and CMS system requirements.

; [[CMS Use]]: Select the above link for information on how to use and configure CMS.

</div>

Main Page

2014-03-18T17:48:20Z

Luke steinmetzer:

NewHaven Internal Wiki

 

==Introduction==
Thank you for visiting our wiki! We want to help provide answers to some of the common questions regarding our [http://www.newhavensoftware.com/cmspro Commerce Management System (CMS)] and our integrated [http://www.newhavensoftware.com/ecms shopping cart eCMS]. Besides this wiki CMS also has an internal help system that we regularly update. Currently this is a closed wiki so it cannot be edited by anyone other than NewHaven Software, but if you would like to contribute or make any suggestions please let us know.

==Wiki Overview==
The following links are to help you find the information you are looking for.

<div style="float: left; margin-right: 1%; width: 49%">
; [[CMS Support|CMS]]: Information related to CMS Use, setup, and troubleshooting.

; [[Newest Articles Added]]: Select this option to see a list of the latest articles.

</div>

<div style="float: left; width: 50%">
; [[PCI Compliance]]: For information on our commitment to security please see our detailed [[PCI Compliance]] article.

; [[ECMS_Help|Web]]: Information related to CMS web integrations, there use, setup, and troubleshooting.

<div style="clear: both"></div>

Main Page

2014-03-18T17:46:29Z

Luke steinmetzer:

NewHaven Internal Wiki

 

==Introduction==
Thank you for visiting our wiki! We want to help provide answers to some of the common questions regarding our [http://www.newhavensoftware.com/cmspro Commerce Management System (CMS)] and our integrated [http://www.newhavensoftware.com/ecms shopping cart eCMS]. Besides this wiki CMS also has an internal help system that we regularly update. Currently this is a closed wiki so it cannot be edited by anyone other than NewHaven Software, but if you would like to contribute or make any suggestions please let us know.

==Wiki Overview==
The following links are to help you find the information you are looking for.

<div style="float: left; margin-right: 1%; width: 49%">
; [[CMS Support]]: Information related to CMS Use, setup, and troubleshooting.

; [[ECMS_Help|ECMS Support]]: Information related to CMS web integrations, there use, setup, and troubleshooting.

; [[Newest Articles Added]]: Select this option to see a list of the latest articles.

</div>

<div style="float: left; width: 50%">
; [[PCI Compliance]]: For information on our commitment to security please see our detailed [[PCI Compliance]] article.

; [[Web Resources]]: This is a list of helpful resources for web design and web development.

<div style="clear: both"></div>

CMS over Microsoft Remote Desktop

2014-01-25T01:15:43Z

Luke steinmetzer:

Remote Desktop, sometimes refered to as RDP allows a client to connect to a remote machine as though they were sitting in front of it. With CMS there are some hurdles to running CMS over RDP, here we will discuss them and provide solutions.

* '''Note:''' You'll want to have the most current version of Remote Desktop Connection for this to work as expected. Also note, that while these solutions have been tested and work, Remote Desktop is a 3rd party application. As a result we do not provide direct support for it.

== Printing ==

To setup your workstation so a local printer may print from the remote system please follow the instructions below:
* Open '''remote desktop connection'''
* Click on the '''Options >>''' button to open more options
* Click on the '''Local Resources''' tab
* Make sure '''Printers''' is checked.

After setting these configurations, you'll want to save the connection.
* Click on the '''General''' tab
* Click '''Save''' or '''Save As''' if this is a new connection

'''Note:''' In order for most printers to work on Remote Desktop, they need to be installed on the '''host''' system, the computer you are connecting to.

Once the printers are configured and tested in windows, you can configure your workstation settings to use those new printers.

== Scale ==

To setup your workstation so a local scale may be used with the remote system please follow the instructions below:

* '''Note:''' If for some reason your COM port is not being read correctly, restart both the host and client system to reset the ports.

* Open '''remote desktop connection'''
* Click on the '''Options >>''' button to open more options
* Click on the '''Local Resources''' tab
* Click on the '''More...''' button
* Make sure '''Serial ports''' is checked.
* Click OK

After setting these configurations, you'll want to save the connection.
* Click on the '''General''' tab
* Click '''Save''' or '''Save As''' if this is a new connection

== Scanner ==
If the scanner creates a com port see the Scale setup info. If the scanner is strickly USB see the credit card swiper info.

== Credit Card Swiper / Pole Display ==

To setup your workstation so a local credit card swiper or Pole display may be used with the remote system, please follow the instructions below:

'''Note:''' You'll need to turn off the redirector to use the card swiper locally. Also this requires a third party software that costs money, though it has a 15 day trial for testing. See [[USB Redirector]] for more information. 

*Install http://www.incentivespro.com/downloads.html on both the Terminal Server (host) and the workstation (client)
*Start the redirection software on the server
*Start the redirection software on the client
*Connect to the RDP session
*Connect the USB device.

At this point if the USB device requires a driver it will ask for that information on the host. Otherwise it will be available and ready to go.

== Troubleshooting Info ==
*Firewalls and other security measures may prevent the use of some of the configurations above. Please make sure to add CMS in any "Trusted" lists your security software may use. Also a list of common ports that CMS works across is provided below, you will need to make sure these ports are open for CMS to communicate on.
*Outgoing CMS is communicating on standard ports 443, 80 (for most webservices/ecms) and the default Sybase port of 2638. Email can communicate on the ports you specify in email setup. The default is 25 other, with other smtp port include 465, 587.

CMS over Microsoft Remote Desktop

2014-01-25T01:11:07Z

Luke steinmetzer:

Remote Desktop, sometimes refered to as RDP allows a client to connect to a remote machine as though they were sitting in front of it. With CMS there are some hurdles to running CMS over RDP, here we will discuss them and provide solutions.

* '''Note:''' You'll want to have the most current version of Remote Desktop Connection for this to work as expected. Also note, that while these solutions have been tested and work, Remote Desktop is a 3rd party application. As a result we do not provide direct support for it.

== Printing ==

To setup your workstation so a local printer may print from the remote system please follow the instructions below:
* Open '''remote desktop connection'''
* Click on the '''Options >>''' button to open more options
* Click on the '''Local Resources''' tab
* Make sure '''Printers''' is checked.

After setting these configurations, you'll want to save the connection.
* Click on the '''General''' tab
* Click '''Save''' or '''Save As''' if this is a new connection

'''Note:''' In order for most printers to work on Remote Desktop, they need to be installed on the '''host''' system, the computer you are connecting to.

Once the printers are configured and tested in windows, you can configure your workstation settings to use those new printers.

== Scale ==

To setup your workstation so a local scale may be used with the remote system please follow the instructions below:

* '''Note:''' If for some reason your COM port is not being read correctly, restart both the host and client system to reset the ports.

* Open '''remote desktop connection'''
* Click on the '''Options >>''' button to open more options
* Click on the '''Local Resources''' tab
* Click on the '''More...''' button
* Make sure '''Serial ports''' is checked.
* Click OK

After setting these configurations, you'll want to save the connection.
* Click on the '''General''' tab
* Click '''Save''' or '''Save As''' if this is a new connection

== Scanner ==
If the scanner creates a com port see the Scale setup info. If the scanner is strickly USB see the credit card swiper info.

== Credit Card Swiper / Pole Display ==

To setup your workstation so a local credit card swiper or Pole display may be used with the remote system, please follow the instructions below:

'''Note:''' You'll need to turn off the redirector to use the card swiper locally. Also this requires a third party software that costs money, though it has a 15 day trial for testing. See [[USB Redirector]] for more information. 

*Install http://www.incentivespro.com/downloads.html on both the Terminal Server (host) and the workstation (client)
*Start the redirection software on the server
*Start the redirection software on the client
*Connect to the RDP session
*Connect the USB device.

At this point if the USB device requires a driver it will ask for that information on the host. Otherwise it will be available and ready to go.

== Troubleshooting Info ==
*Outgoing (from CMS) is communicating on standard ports 443, 80 (for most webservices/ecms) and the default Sybase port of 2638 and email can communicate on the ports you specify in email setup default is 25 other smtp port include 465, 587.
*Adding CMS to the "trusted" list is usually the recommended solution.
*DEP does do a lot of blocking with webservices which is what AVM, eCMS, etc use. Also, if the rest of CMS workstation is working, then most likely it's not a port blocking issue or I'm sure 2638 would also be blocked.

CMS over Microsoft Remote Desktop

2014-01-25T01:07:54Z

Luke steinmetzer:

Remote Desktop, sometimes refered to as RDP allows a client to connect to a remote machine as though they were sitting in front of it. With CMS there are some hurdles to running CMS over RDP, here we will discuss them and provide solutions.

* '''Note:''' You'll want to have the most current version of Remote Desktop Connection for this to work as expected. Also note, that while these solutions have been tested and work, Remote Desktop is a 3rd party application. As a result we do not provide direct support for it.

== Printing ==

To setup your workstation so a local printer may print from the remote system please follow the instructions below:
* Open '''remote desktop connection'''
* Click on the '''Options >>''' button to open more options
* Click on the '''Local Resources''' tab
* Make sure '''Printers''' is checked.

After setting these configurations, you'll want to save the connection.
* Click on the '''General''' tab
* Click '''Save''' or '''Save As''' if this is a new connection

'''Note:''' In order for most printers to work on Remote Desktop, they need to be installed on the '''host''' system, the computer you are connecting to.

Once the printers are configured and tested in windows, you can configure your workstation settings to use those new printers.

== Scale ==
Com ports can be finicky some time. If you can't get them working restart both the host and client system to reset the ports.

* Open '''remote desktop connection'''
* Click on the '''Options >>''' button to open more options
* Click on the '''Local Resources''' tab
* Click on the '''More...''' button
* Make sure '''Serial ports''' is checked.
* Click OK

After setting these configurations, you'll want to save the connection.
* Click on the '''General''' tab
* Click '''Save''' or '''Save As''' if this is a new connection

== Scanner ==
If the scanner creates a com port see the Scale setup info. If the scanner is strickly USB see the credit card swiper info.

== Credit Card Swiper / Pole Display ==

'''Note:''' You'll need to turn off the redirector to use the card swiper locally. Also this requires a third party software that costs money, though it has a 15 day trial for testing. See [[USB Redirector]] for more information. 

*Install http://www.incentivespro.com/downloads.html on both the Terminal Server (host) and the workstation (client)
*Start the redirection software on the server
*Start the redirection software on the client
*Connect to the RDP session
*Connect the USB device.

At this point if the USB device requires a driver it will ask for that information on the host. Otherwise it will be available and ready to go.

== Troubleshooting Info ==
*Outgoing (from CMS) is communicating on standard ports 443, 80 (for most webservices/ecms) and the default Sybase port of 2638 and email can communicate on the ports you specify in email setup default is 25 other smtp port include 465, 587.
*Adding CMS to the "trusted" list is usually the recommended solution.
*DEP does do a lot of blocking with webservices which is what AVM, eCMS, etc use. Also, if the rest of CMS workstation is working, then most likely it's not a port blocking issue or I'm sure 2638 would also be blocked.

CMS over Microsoft Remote Desktop

2014-01-25T01:06:30Z

Luke steinmetzer:

Remote Desktop, sometimes refered to as RDP allows a client to connect to a remote machine as though they were sitting in front of it. With CMS there are some hurdles to running CMS over RDP, here we will discuss them and provide solutions.

* '''Note:''' You'll want to have the most current version of Remote Desktop Connection for this to work as expected. Also note, that while these solutions have been tested and work, Remote Desktop is a 3rd party application. As a result we do not provide direct support for it.

== Printing ==
* Open '''remote desktop connection'''
* Click on the '''Options >>''' button to open more options
* Click on the '''Local Resources''' tab
* Make sure '''Printers''' is checked.

After setting these configurations, you'll want to save the connection.
* Click on the '''General''' tab
* Click '''Save''' or '''Save As''' if this is a new connection

'''Note:''' In order for most printers to work on Remote Desktop, they need to be installed on the '''host''' system, the computer you are connecting to.

Once the printers are configured and tested in windows, you can configure your workstation settings to use those new printers.

== Scale ==
Com ports can be finicky some time. If you can't get them working restart both the host and client system to reset the ports.

* Open '''remote desktop connection'''
* Click on the '''Options >>''' button to open more options
* Click on the '''Local Resources''' tab
* Click on the '''More...''' button
* Make sure '''Serial ports''' is checked.
* Click OK

After setting these configurations, you'll want to save the connection.
* Click on the '''General''' tab
* Click '''Save''' or '''Save As''' if this is a new connection

== Scanner ==
If the scanner creates a com port see the Scale setup info. If the scanner is strickly USB see the credit card swiper info.

== Credit Card Swiper / Pole Display ==

'''Note:''' You'll need to turn off the redirector to use the card swiper locally. Also this requires a third party software that costs money, though it has a 15 day trial for testing. See [[USB Redirector]] for more information. 

*Install http://www.incentivespro.com/downloads.html on both the Terminal Server (host) and the workstation (client)
*Start the redirection software on the server
*Start the redirection software on the client
*Connect to the RDP session
*Connect the USB device.

At this point if the USB device requires a driver it will ask for that information on the host. Otherwise it will be available and ready to go.

== Troubleshooting Info ==
*Outgoing (from CMS) is communicating on standard ports 443, 80 (for most webservices/ecms) and the default Sybase port of 2638 and email can communicate on the ports you specify in email setup default is 25 other smtp port include 465, 587.
*Adding CMS to the "trusted" list is usually the recommended solution.
*DEP does do a lot of blocking with webservices which is what AVM, eCMS, etc use. Also, if the rest of CMS workstation is working, then most likely it's not a port blocking issue or I'm sure 2638 would also be blocked.

CMS over Microsoft Remote Desktop

2014-01-25T01:04:47Z

Luke steinmetzer: Created page with 'Remote Desktop, sometimes refered to as RDP allows a client to connect to a remote machine as though they were sitting in front of it. With CMS there are some hurdles to running …'

Remote Desktop, sometimes refered to as RDP allows a client to connect to a remote machine as though they were sitting in front of it. With CMS there are some hurdles to running CMS over RDP, here we will discuss them and provide solutions.

* '''Note:''' You'll want to have the most current version of Remote Desktop Connection for this to work as expected. Also note, that while these solutions have been tested and work, they are not strictly "supported".

== Printing ==
* Open '''remote desktop connection'''
* Click on the '''Options >>''' button to open more options
* Click on the '''Local Resources''' tab
* Make sure '''Printers''' is checked.

After setting these configurations, you'll want to save the connection.
* Click on the '''General''' tab
* Click '''Save''' or '''Save As''' if this is a new connection

'''Note:''' In order for most printers to work on Remote Desktop, they need to be installed on the '''host''' system, the computer you are connecting to.

Once the printers are configured and tested in windows, you can configure your workstation settings to use those new printers.

== Scale ==
Com ports can be finicky some time. If you can't get them working restart both the host and client system to reset the ports.

* Open '''remote desktop connection'''
* Click on the '''Options >>''' button to open more options
* Click on the '''Local Resources''' tab
* Click on the '''More...''' button
* Make sure '''Serial ports''' is checked.
* Click OK

After setting these configurations, you'll want to save the connection.
* Click on the '''General''' tab
* Click '''Save''' or '''Save As''' if this is a new connection

== Scanner ==
If the scanner creates a com port see the Scale setup info. If the scanner is strickly USB see the credit card swiper info.

== Credit Card Swiper / Pole Display ==

'''Note:''' You'll need to turn off the redirector to use the card swiper locally. Also this requires a third party software that costs money, though it has a 15 day trial for testing. See [[USB Redirector]] for more information. 

*Install http://www.incentivespro.com/downloads.html on both the Terminal Server (host) and the workstation (client)
*Start the redirection software on the server
*Start the redirection software on the client
*Connect to the RDP session
*Connect the USB device.

At this point if the USB device requires a driver it will ask for that information on the host. Otherwise it will be available and ready to go.

== Troubleshooting Info ==
*Outgoing (from CMS) is communicating on standard ports 443, 80 (for most webservices/ecms) and the default Sybase port of 2638 and email can communicate on the ports you specify in email setup default is 25 other smtp port include 465, 587.
*Adding CMS to the "trusted" list is usually the recommended solution.
*DEP does do a lot of blocking with webservices which is what AVM, eCMS, etc use. Also, if the rest of CMS workstation is working, then most likely it's not a port blocking issue or I'm sure 2638 would also be blocked.

Ad codes

2013-11-15T22:49:02Z

Luke steinmetzer: Blanked the page

Word Processor in CMS

2013-10-10T15:37:34Z

Luke steinmetzer: Created page with '=Summary= Review of the capabilities and some of the technical aspects related to the word processor build into CMS. =Details= CMS includes a third-party Wordpad-style text edit…'

=Summary=
Review of the capabilities and some of the technical aspects related to the word processor build into CMS.

=Details=
CMS includes a third-party Wordpad-style text editor which is used when composing letters/emails in various sections of CMS. It is also employed in the Tech Info note for products to allow for greater formatting capabilities. We may see this word processor employed elsewhere in future versions of CMS such as the Primary Notes in Contact Manager or the product's Upsell Notes, for example.

This word processor uses RVF which is [http://www.trichview.com/help/index.html?richview_format__rvf__overview.html Rich View Format]. This is similar to [http://en.wikipedia.org/wiki/Rich_Text_Format RTF] but optimized for application use (smaller and faster than RTF). The side-effect of our using an RVF word processor is much the same as if we were using Word or even an RTF word processor: the data is no longer plain text, it is now encoded with special formatting and not simply readable in Notepad nor can the plain text data be accessed reasonably via an ODBC connection (exporting, reports, etc.)

Composition in CMS is always done in the RVF format and one must take care when pasting from Word, for example, since all formatting does not transfer correctly. Bullets, hyphens, and other characters may look OK but when it sends they end up being exclamation points as unrecognized characters. You should always send test emails to yourself to ensure proper rendering before using an email in production, particular if not composed in CMS.

On the point of rendering, CMS relies on the word processor to properly render the email in HTML or text, depending on your choice when the letter was saved. This is a hands-off process for CMS and we have no control over it shy of having some parameters that we can pass. If formatting problems are found we may have some recourse with the author and can pursue the issue with them.

We would expect the word processor to properly handle the conversion of URL's to hyperlinks and hypertext where appropriate as well as the proper handling of any formatting done in CMS (bullets/lists, margins, paragraphs, fonts, inline images, charts, etc.) Essentially anything available from the word processor's formatting toolbar (elaborated on in our [http://wiki.brodieware/wiki/index.php/File:Helpsystem.png Help system]). That said, the word processor is not an HTML editor and does not accept HTML coding in the body of the document.

There is a handy Preview option in the word processor's toolbar (button with small red checkmark) that will let you see the letter with its merge fields completed (if done from Contact Manager with a retrieved customer). Sadly it will not show you how it will render as text, only as HTML.

=Example=
==In CMS==

[[Image:Example2.png]]

==Sent as HTML==
Notice it is nearly identical to the letter composed in CMS except that the email client converted our www.google.com URL to a link. Normally the word processor will convert all URL's to links but this will only happen if you hit Enter or Spacebar after the URL. If instead you tab or click away, the link conversion is skipped as you can see in my example above for www.google.com.

[[Image:HTMLExample.png]]

==Sent in Text format==
All of the text is preserved but without the formatting. There is also no ugly HTML code but we do lose the in-line image (not preserved as an attachment.) You can see again that my email client has converted the text URL's into links (yrmv) but of course we lose the hypertext link (Google).

[[Image:Plaintextexample.png]]

File:Plaintextexample.png

2013-10-10T14:57:45Z

Luke steinmetzer:

File:HTMLExample.png

2013-10-10T14:57:29Z

Luke steinmetzer:

File:Helpsystem.png

2013-10-10T14:57:15Z

Luke steinmetzer:

File:Example2.png

2013-10-10T14:56:59Z

Luke steinmetzer:

Server Update

2013-10-02T14:38:35Z

Luke steinmetzer:

=Overview=

This article details the instructions for updating CMS to version 8 and 9.

=Preparing for the Installation=

Before you begin installing or updating your Server please review the list below.

==Server System Requirements==
To verify that your system meets CMS system requirements please review : http://wiki.newhavensoftware.com/index.php/CMS_System_Requirements#Servers

== Updating reports ==

If you are updating to CMS version 9 from CMS version 8 or older and you use custom CMS forms or crystal reports. We may need to update those reports. Please contact support@newhavensoftware.com directly so we can review this with you.

==Backing up CMS==

Below is information about backing up your CMS information before updating.

===Creating backups when updating from CMS 7 to 8===

When updating CMS from version 7 to 8 it will automatically create the following Backups in your NewHaven Software directory:
*A backup of your database is added to your Data folder as (name of your database).bak
*All of your CMS Reports are zipped up and added to the Reports folder as Reports-backup.7z

If you need access to the backup file, just rename the .bak extension to .db

If needed you can unzip your reports with the free software program 7 zip. You can download this from the link below
http://www.7-zip.org/

===Creating backups if doing a CMS 8 to 8 or 8 to 9 update===

Before updating CMS to a new version of 8 or 9, you will want to create a Database backup. To do this please review the instructions in the link below.
http://wiki.newhavensoftware.com/index.php/Creating_a_Database_Backup

==Download the CMS Installer==
Please visit http://updates.newhavensoftware.com/
For information on using the update page and downloading the installer please review the video : http://youtu.be/dBbd94k7b0A

==Time to Update the Server==
Please note: If you are updating CMS 7 to 8, that due to the upgrade from Sybase ASA 8.0.2 to Sybase SQL Anywhere 12.0.1, the server update can take longer then normal. While time to do this is extremely variable, we recommend planning for 2 hours of downtime.

==Workstation Updates==
'''Note: If you are updating CMS 7 to CMS 8, you will be required to run a Workstation update on all of your CMS Workstations. This is because your Workstations will require a new ODBC driver to function. If you do NOT do this, your workstations will not function.'''

For information on this process please click the link below. http://wiki.newhavensoftware.com/index.php/Workstation_Install

==Release Notes==
There are a number of large changes that come with the update to CMS 8. Please take your time to review our release notes on these update. You can do so by clicking on the link below http://updates.newhavensoftware.com/v8release_notes.html

=Server Update=
Note: Once you have verified that you meet the above prerequisites, follow the instructions below to Update your Server.

*'''BEFORE GOING ANY FURTHER PLEASE MAKE SURE EVERYONE IS LOGGED OUT OF CMS'''

To begin double click the CMS installer, then follow the screenshots shown below.

[[image:Serverupdate1.png]]

[[image:Serverupdate2.png]]

[[image:Serverupdate3.png]]

[[image:Serverupdate4.png]]

[[image:Serverupdate5.png]]

[[image:Serverupdate6.png]]

[[image:Serverupdate7.png]]

[[image:Serverupdate8.png]]

[[image:Serverupdate9.png]]

 

After following these instructions you should now be able to sign into CMS.

Workstation Install

2013-09-19T07:41:33Z

Luke steinmetzer:

=Overview=

This article details the instructions for installing or updating a CMS 8 or 9 Workstation.

=Prerequisite=

Before you begin installing or updating your workstation please check that you meet the requirements for all the steps below.

==Step 1: Workstation System Requirements ==
Note: Workstation system requirements have not changed from CMS 7 to 8.
To verify that your system meets CMS system requirements please review : http://wiki.newhavensoftware.com/index.php/CMS_System_Requirements#CMS_workstations

==Step 2: Download the CMS Installer==

Please visit http://updates.newhavensoftware.com/
For information on using the update page and downloading the installer please review the video : http://youtu.be/dBbd94k7b0A (Note: The video is focused on Windows XP, however the setup steps are the same for Windows 7)

==Step 3: Setup a Shared drive to the CMS server==
Note: This is only needed if you are installing a new workstation.
For Information on how to setup a Shared drive please review the video : http://youtu.be/D1IBcjWCmPs

=Workstation Install/Update=
Note: The steps between updating or installing a CMS workstation are the same. Once you have verified that you meet the above prerequisites, follow the instructions below to Install/Update your workstation.

To begin double click the CMS installer, then follow the screenshots shown below.

[[image:Workstation1.png]]

[[image:Workstation2.png]]

[[image:Workstation3.png]]

[[image:Workstation4.png]]

[[image:Workstation5.png]]

[[image:Workstation6.png]]

[[image:Workstation7.png]]

[[image:Workstation8.png]]

[[image:Workstation9.png]]
 

After following these instructions you should now be able to sign into CMS.

Server Update

2013-07-10T23:42:09Z

Luke steinmetzer:

=Overview=

This article details the instructions for updating CMS to version 8.

=Preparing for the Installation=

Before you begin installing or updating your Server please review the list below.

==Server System Requirements==
To verify that your system meets CMS system requirements please review : http://wiki.newhavensoftware.com/index.php/CMS_System_Requirements#Servers

== Updating reports ==

If you are updating to CMS version 9 from CMS version 8 or older and you use custom CMS forms or crystal reports. We may need to update those reports. Please contact support@newhavensoftware.com directly so we can review this with you.

==Backing up CMS==

Below is information about backing up your CMS information before updating.

===Creating backups when updating from CMS 7 to 8===

When updating CMS from version 7 to 8 it will automatically create the following Backups in your NewHaven Software directory:
*A backup of your database is added to your Data folder as (name of your database).bak
*All of your CMS Reports are zipped up and added to the Reports folder as Reports-backup.7z

If you need access to the backup file, just rename the .bak extension to .db

If needed you can unzip your reports with the free software program 7 zip. You can download this from the link below
http://www.7-zip.org/

===Creating backups if doing a CMS 8 to 8 or 8 to 9 update===

Before updating CMS to a new version of 8 or 9, you will want to create a Database backup. To do this please review the instructions in the link below.
http://wiki.newhavensoftware.com/index.php/Creating_a_Database_Backup

==Download the CMS Installer==
Please visit http://updates.newhavensoftware.com/
For information on using the update page and downloading the installer please review the video : http://youtu.be/dBbd94k7b0A

==Time to Update the Server==
Please note: If you are updating CMS 7 to 8, that due to the upgrade from Sybase ASA 8.0.2 to Sybase SQL Anywhere 12.0.1, the server update can take longer then normal. While time to do this is extremely variable, we recommend planning for 2 hours of downtime.

==Workstation Updates==
'''Note: If you are updating CMS 7 to CMS 8, you will be required to run a Workstation update on all of your CMS Workstations. This is because your Workstations will require a new ODBC driver to function. If you do NOT do this, your workstations will not function.'''

For information on this process please click the link below. http://wiki.newhavensoftware.com/index.php/Workstation_Install

==Release Notes==
There are a number of large changes that come with the update to CMS 8. Please take your time to review our release notes on these update. You can do so by clicking on the link below http://updates.newhavensoftware.com/v8release_notes.html

=Server Update=
Note: Once you have verified that you meet the above prerequisites, follow the instructions below to Update your Server.

*'''BEFORE GOING ANY FURTHER PLEASE MAKE SURE EVERYONE IS LOGGED OUT OF CMS'''

To begin double click the CMS installer, then follow the screenshots shown below.

[[image:Serverupdate1.png]]

[[image:Serverupdate2.png]]

[[image:Serverupdate3.png]]

[[image:Serverupdate4.png]]

[[image:Serverupdate5.png]]

[[image:Serverupdate6.png]]

[[image:Serverupdate7.png]]

[[image:Serverupdate8.png]]

[[image:Serverupdate9.png]]

 

After following these instructions you should now be able to sign into CMS.

Test Install

2013-02-14T12:58:31Z

Luke steinmetzer:

=Overview=

This article details the instructions for creating a CMS 9.0 Testbed.

=Preparing for the Installation=

Before you begin installing your 9.0 testbed please review the list below.

==Server System Requirements==
To verify that your system meets CMS system requirements please review : http://wiki.newhavensoftware.com/index.php/CMS_System_Requirements#Servers

==Creating a CMS backup ==

Before installing your CMS 9.0 testbed, you will want to create a Database backup. To do this please review the instructions in the link below.
http://wiki.newhavensoftware.com/index.php/Creating_a_Database_Backup

==Download the CMS Installer==
Please visit http://updates.newhavensoftware.com/
For information on using the update page and downloading the installer please review the video : http://youtu.be/dBbd94k7b0A

==Time to Install the Testbed==
Please note: If you are updating CMS 7 to 8, that due to the upgrade from Sybase ASA 8.0.2 to Sybase SQL Anywhere 12.0.1, the server update can take longer then normal. While time to do this is extremely variable, we recommend planning for 2 hours of downtime.

== Workstation install for your testbed ==

For information on this process please click the link below. http://wiki.newhavensoftware.com/index.php/Test_Workstation_Install

==Release Notes==
There are a number of large changes that come with the update to CMS 9. Please take your time to review our release notes on this update. You can do so by clicking on the link below http://updates.newhavensoftware.com/v9release_notes.html

=Testbed install=
Note: Once you have verified that you meet the above prerequisites, follow the instructions below to install your testbed.

*'''BEFORE GOING ANY FURTHER PLEASE MAKE SURE EVERYONE IS LOGGED OUT OF CMS'''

To begin double click the CMS installer, then follow the screenshots shown below.

[[image:Testinstall_1.png]]

[[image:Testinstall_2.png]]

[[image:Testinstall_3.png]]

[[image:Testinstall_4.png]]

[[image:Testinstall_5.png]]

[[image:Testinstall_6.png]]

[[image:Testinstall_7.png]]

[[image:Testinstall_8.png]]

[[image:Testinstall_9.png]]

[[image:Testinstall_10.png]]

[[image:Testinstall_11.png]]

[[image:Testinstall_12.png]]

 

After following these instructions you should now be able to sign into CMS.

File:Testinstall 1.png

2013-02-14T12:55:14Z

Luke steinmetzer: uploaded a new version of "File:Testinstall 1.png"

Test Workstation Install

2013-02-14T12:50:53Z

Luke steinmetzer:

=Overview=

This article details the instructions for installing CMS workstation to your version 9 testbed. These steps can be followed even if you have a Workstation install active on your system to your live database.

=Preparing for the Installation=

Before you begin installing or updating your workstation please check that you meet the requirements for all the steps below.

*Workstation System Requirements
To verify that your system meets CMS system requirements please review : http://wiki.newhavensoftware.com/index.php/CMS_System_Requirements#CMS_workstations
(Workstation system requirements have not changed from CMS 7.x to 8.x)
*Download the CMS Installer
Please visit http://updates.newhavensoftware.com/
For information on using the update page and downloading the installer please review the video : http://youtu.be/dBbd94k7b0A
*Setup a Shared drive to the CMS 9.0 Testbed
For Information on how to setup a Shared drive please review the video : http://youtu.be/D1IBcjWCmPs

=Workstation Install=
Once you have verified that you meet the above prerequisites, follow the instructions below to Install your workstation.

To begin double click the CMS installer, then follow the screenshots shown below.

[[image:testwork1.png]]

[[image:testwork2.png]]

[[image:testwork3.png]]

[[image:testwork4.png]]

[[image:testwork5.png]]

[[image:testwork6.png]]

[[image:testwork7.png]]

[[image:testwork8.png]]

[[image:testwork9.png]]

[[image:testwork10.png]]
 

After following these instructions you should now be able to sign into CMS.

File:Testwork10.png

2013-02-14T12:50:19Z

Luke steinmetzer:

File:Testwork9.png

2013-02-14T12:50:11Z

Luke steinmetzer:

File:Testwork8.png

2013-02-14T12:50:02Z

Luke steinmetzer:

File:Testwork6.png

2013-02-14T12:49:53Z

Luke steinmetzer: