| This article is part of the
Payment Processing Software Library
|Connect to it...|
|Set it up...|
|Learn to use it...|
|More Info ...|
→ Looking for better rates? Get a Free Credit Card Processing Cost Comparison!
- 1 Upgrading From Older Versions
- 2 Migration
- 3 Directory Structure
- 4 Important Files
- 5 Encryption Keys
- 6 BIN Ranges
- 7 Terminal Registration File
- 8 Backups
- 9 Also See
Upgrading From Older Versions
→ Your setup will be preserved during upgrade!
Upgrading from 4.1 Build1102 (PCI 1.0) to 4.1.3(SP3) Build 1186 (PCI 2.0)
Please, see the following checklist: Upgrading to 4.1.3 Build 1186
- Make sure to batch out everything before upgrading to avoid journal corruption.
- In rare cases, when upgrading from non-IP versions 2.19 and older, you may incur a small upgrade fee - please contact your dealer for more information before installing the new version.
- Batch any outstanding transactions, first.
- If upgrading from a credit card software version prior to 3.00.00, please uninstall your old version, first. This will ensure that all non-compliant utilities and programs are removed from your system. You will not loose your data.
- Stop all CreditLine Applications and Service (if installed)
Stopping CreditLine Applications
- If the CreditLine Service is installed, verify the Services list in Windows Advanced Computer Management Console
If you are running CreditLine Credit Card Software Service and are upgrading remotely, you can use the following commands to stop and start the service:
sc \\hostname stop CreditServer sc \\hostname start CreditServer
- Search the Task Manager for CreditLine Server and Manager and end the process. Make sure to click Image Name to sort by name
Backup the entire 911 directory to a safe location.
- Other Auths do not match with default auth!
- This warning is due to some card setups differing from the default auth setup. For instance, VISA is setup with one merchant account and Discover is setup with another. See Apply To All Auths Feature in CreditLine Settlement Configuration Dialog for a quick fix.
- Did not batch for 15 days!
- Informs you that the site did not batch for 15 days or more. You can ignore this warning at the time of the upgrade since it is only valid after the first batch with the new version.
- Settlement And Authorization Do Not Match
- This means that settlement and authorization setups differ. See Apply To All Auths Feature in CreditLine Settlement Configuration Dialog for a quick fix.
- Invalid Setup File
- The setup file is corrupted or otherwise incorrectly setup. You can try checking Reset Config in CreditLine Business Configuration.
- Dialup phone numbers do not match the default for the processor
- The dialup numbers used do not match the ones that the program knows to be the default phone numbers for the chosen processor. If you are sure, that the phone numbers are ok, you can ignore this error. For Dial-up: the default dial-up numbers are programmed into CreditLine. If the phone number field is empty, it will be auto-filled after you click OK in Merchant Setup in CreditLine Settlement Configuration dialog. In the latest versions, you can also click Default next to the Phone Numbers fields to auto-fill them, otherwise, delete the phone numbers before entering Merchant Setup to use the auto-fill feature.
Simply follow the Installation Procedure and it will upgrade your system to the latest version.
→For multiple merchant installs, make sure your merchant index access is setup correctly by user.
Note: CreditLine does not facilitate delivering patches and upgrades via RDP to satisfy specific PCI requirements. Please use download link to obtain the new versions.
911 Software does not use the registry, so you can easily move the software to a new location just by moving the 911 folder.
Update the shortcuts after the move - see Multiple Terminal Setup for details.
Alternatively, you can uninstall the software, reinstall it in a new directory and copy over DATA, JOR and LOG directories.
To move individual components, please see Directory Structure for description and significance of individual folders and files.
NOTE: in version 3.01.07 and older the software ALWAYS looks for \911\bin from the root of the drive regardless of the installation path or working directory set. The working directory only points out the root drive.
|C:\911\JOR||Historical Journal, automaticly created. For multiple merchant setups it is JOR? where ? is the merchant index.|
|C:\911\LOG||Historical Log, automaticly created. For multiple merchant setups it is LOG? where ? is the merchant index.|
|C:\911\MESSAGES||Text-Based Communication Files|
The following two files must always accompany the #Transaction Journal: 911\data\DataEncryptingKey.ini and \911\data\KeyEncryptingKey.ini
The journal of all transactions is under the 911\data directory in ccv_jor.dat (or ccv_jor?.dat where ? is merchant index if you are using a multiple merchant setup. Make sure that the encryption keys 911\data\DataEncryptingKey.ini and \911\data\KeyEncryptingKey.ini always follow any moves of the data to and from the system or permanent corruption of the Transaction Journal File may result.
→Deleting this file will remove all unbatched transactions.
The merchant and other setup is under the 911\data directory in ccv_info.dat file(or ccv_info?.dat where ? is merchant index if you are using a multiple merchant setup.
The card number BIN ranges are the starting 6 digits of the card numbers that help us to identify the card types. \911\data\ccv_range.ini contains the defined BIN ranges for the setup
Terminal Registration File
The following file is used to register Terminals/Lanes manually, when required by processor compliance (e.g. Elavon 5/3rd Bank): 911\data\POSREGISTRATION.ini
- Server Activity Log
- The log is stored under the 911\data directory in ccv_log.dat file (or ccv_log?.dat where ? is merchant index if you are using a multiple merchant setup. The log can be viewed in CreditLine Manager by using CreditLine View Log Dialog. Older logs can be viewed by using the CreditLine Log Archive List Dialog.
- Error Statistic File
- The error statistic file can be used for reliability testing and is stored under the 911\data directory in ccv_error.csv. The header for the file describes the fields, separated by '|', e.g. "DATE|TIME|MERCHANT NAME|ERROR DESCRIPTION|ERROR TYPE|TRANS TYPE|PROCESSOR NAME|COMM TYPE|COMM PARAMETER"
The advanced configuration is under the 911\data directory in 911_ccv.ini. See CreditLine Advanced Setup for more info.
The connection settings for various processors and modems is under the 911\data directory in ccv_link.ini.
Important File Summary
|C:\911\DATA\CCV_INFO.DAT|| Site Configuration - this file contains all the merchant specific information|
→ multiple merchant setups use multiple files of format C:\911\DATA\CCV_INFO?.DAT where ? is the merchant index.
|C:\911\DATA\CCV_JOR.DAT|| Current Day Journal - deleting this file will remove all authorized transactions|
→ multiple merchant setups use multiple files of format C:\911\DATA\CCV_JOR?.DAT where ? is the merchant index.
|C:\911\DATA\CCV_LOG.TXT||Current Day Log|
You can view and manipulate the Journal Backups in the CreditLine Batch Archive Dialog
→In some extreme cases the transactions that you are looking for can only be found by clicking the Radio Buttons "Before Batch" and "Daily Backup" in the CreditLine Batch Archive Dialog
The number of days that the journals are backed up is specified in CreditLine Business Configuration Dialog. To restore the journal/batch you can rename the desired journal backup file to ccv_jor.dat and move it to 911\DATA directory. Don't forget to reload the configuration to apply the changes.
→ For multiple merchant setups replace JOR below with JOR? where ? is the merchant index.
|C:\911\JOR\b<time_stamp>.??||"BEFORE" BACKUP. Backup of the journal before the batch was run|
|C:\911\JOR\j<time_stamp>.??||"BATCH" BACKUP. Backup of the journal that was batched|
|C:\911\JOR\d<time_stamp>.??||"DAY" BACKUP. Incremental Backup of the journal for a business day appended at the time of the batch|
|C:\911\JOR\u<time_stamp>.??||"UN-BATCHED" BACKUP. Backup of un-batched transactions that were carried over to the next batch (for instance un-finalized Auths)|
→ For multiple merchant setups replace LOG below with LOG? where ? is the merchant index.
|C:\911\LOG\l<time_stamp>.??||Backup of the logs|
To restore the setup file you can rename the desired setup backup file to ccv_info.dat and move it to 911\DATA directory. Don't forget to reload the configuration to apply the changes.
→ For multiple merchant setups replace JOR below with JOR? where ? is the merchant index.
|C:\911\JOR\n<time_stamp>.??||Backup of CreditLine Setup File - generated after every batch|
|C:\911\JOR\i<time_stamp>.??||Backup of CreditLine Setup File - generated before every batch|
The encryption keys are backed up in the 911\Backup directory.
There are two keys: DataEncryptingKey.ini (backup file starting with d), KeyEncryptingKey.ini (backup file starting with k)
To restore the keys:
- Batch out any outstanding accessible transactions
- Backup current DataEncryptingKey.ini and KeyEncryptingKey.ini in 911\Data directory, by renaming them to DataEncryptingKey.ini.bad and KeyEncryptingKey.ini.bad
- Enter 911\Backup directory and sort by Date Modified';
- Pick the desired pair of keys, copy them to 911\Data directory and rename to DataEncryptingKey.ini and KeyEncryptingKey.ini respectively.
- Restart the CreditLine server/service and CreditLine Manager
- Attempt to view the journal
- If unsuccessful, try the next pair in the list.