Creating new stores with EEE

Created: 14 October 2009. Last Reviewed: 3 October 2014

Process for creating new stores with EEE & Enabler

The following process should be followed when creating new stores when you are using both EEE and Enabler. This process doesn't include installing Enabler on the store computers and getting the store ready for trading. For information about Staging a new store, refer to the document “Staging and Support”.

The store should be initially created in EEE and then exported from EEE to Enabler HO. Once the store is in Enabler HO, you can then clone a Store Server and Tills from another store.

Add the new branch in EEE (with a EEE environment)

1. From the EEE menu select Location Management
2. From the Location menu select Branch and then click on ADD
3. Type in the required details for the new branch. Items shown with a red * are mandatory fields. Ensure that the logical address you used when setting up the store in Enabler H/O, is entered in the Logical Address field on this screen, and the branch is setup in the same Region as was used in Enabler H/O. (If the store is not ready to go online, you must tick the option “Exclude this branch from data exports”)
4. Click on Save to save the new branch.
5. On save of a new branch a prompt to clone Prices, Costs, Purge Parameters, and Min/Max levels from another branch will occur.
   • If you don’t clone prices/costs etc from another store, then there will be no prices/costs available to export to a store until they have been entered. You have an option to SKIP this step and perform the cloning at a later stage.

Enter new branch code to “clone to branch” and enable the prices required and branch code that prices will be cloned from.

Set the last export date/time for master file exports. Data cannot be exported to a branch until the export date and time has been completed for that branch.

Set the Last Export Date/Time. Master file records will only be exported from this date onwards.

Any records modified before this date will not be sent. (If you have a large product database, you can keep a master copy of the master file databases as at a certain date, and then only export records modified since that date. This will make processing the initial isl-file.dat much quicker. The master copy of the databases would be copied to the store machines when they are being set up).

Leave Export Date/Time unchanged. This will result in all Master file records being exported to the branch.

Add the new branch in Enabler (no EEE environment)

1. On the Enabler Head Office Server from Back Office select Global Setup
2. Highlight region code and select Add for a new branch record
3. Enter All Branch details required.
   • Branch code (can be either alpha or numerical or both)
   • Logical address is normally four digits made up of region code and branch code.
   • Ensure offline flag is set correctly. Once disabled maintenance files will be created for new branch.
4. Select OK enter to save new branch records

Add the store server in Enabler

1. On the Enabler Head Office Server from Back Office select Global Setup and highlight new branch. (If using EEE confirm new branch code has been added and flowed down to Enabler H/O . Can be manually exported from EEE using data exporter to send branch records but will usually flow down during scheduled export if H/O branch is included in exports from EEE)
2. To add new server we always recommend cloning from an existing store so configurations are consistent. Need to first highlight an existing store server then click on the clone button (try to clone off a store server that has Enabler installed on the same drive as the new branch. Always clone a store server from a store server and a till (node) from another till (node)if possible)
3. Drag and click clone arrow over the name of the Branch where you are adding the new store server
4. Key in the branch code, press Tab then key in the 2 digit till number, key in the name/location of the till, press enter to save
5. Highlight the new server on the left hand side then highlight System Parameters on left and click on config button to open screen
6. Key in the new branch details, press enter to save
7. Highlight the new server on the left hand side then expand Sales and highlight Docket Setup, click on config button to open screen then key in the correct header details, press enter to save
8. Highlight the new server on the left hand side then expand Transaction Processing / Comms, highlight Communication click on config button to open screen. Replace the cloned machine name with the store servers machine name in the following fields:
   • Database server (UNC name) \\servername
   • Time Server (UNC name) \\servername
9. If you have multiple tills and wish to backup your Enabler databases and configuration to another machine on the local network, follow this step.
   
   Highlight the new server on the left hand side then expand Transaction Processing / Comms, highlight, Backup Options Setup click on config button to open screen. Replace the backup path with the path to another machine on your local network or to a another drive letter , e.g.: \\tillname\en\enabler\backup or d:\backup

Add tills (nodes) in Enabler

1. On the Enabler Head Office Server from Back Office select Global Setup
2. Highlight a till (node) in any existing branch then click on Clone (select a till where enabler is installed on same drive as new till)
3. Drag and click clone arrow over the name of the Branch where you are adding the new till then key in the 2 digit till number, then key in the name/location of the till, press enter to save.
4. Highlight the new branch on the left hand side
5. Highlight the new branch on the left hand side then highlight System Parameters on left and click on config button to open screen. Select All to update till docket setup configurations with those already configured for the server.
6. As above highlight branch and Expand Sales and highlight Docket Setup, click on config button to open screen, Select All to update till docket setup configurations with those of the server. press enter to save changes to till
7. This screen requires access at till level so ensure the till is highlighted, expand Transaction Processing / Comms, and highlight Communication click on config button to open screen. Replace the machine name with the new store servers machine name in the following fields:
   • Database server (UNC name) \\servername
   • Time Server (UNC name) \\servername
   • Configuration Base directory \\servername\enserver\enabler\comms\config
8. This screen requires access at till level so ensure the till is highlighted Highlight Database Setup click on config button to open screen then replace the machine name with the store servers machine name in the following fields:
   • Lan Transactions \\servername\enserver\enabler\lantran
   • Lan Master Files \\servername\enserver\enabler\local
   • Lan Maintenance files \\servername\enserver\enabler\lanmnt
9. Select Transaction Processing / Comms, Version Control Setup then replace the machine name with the store servers machine name:
   Upgrade Package Path: \\servername\enserver\enabler\comms\upgpack
   (if the upgrade path refers to a central location rather than the store server, then leave this setting unchanged)

Export configuration

1. On the Enabler Head Office Server from Back Office select Global Setup
2. Always highlight the Store at Branch Name level for exporting of configuration
3. Click on the Export button
4. Enter in the export path name when prompted (folder needs to exist if exporting to a shared network path).
5. A message ‘Destination path will be erased, ok to continue?” Press OK to allow enabler to export configuration to destination path.
6. A message “Include Data common to all stores but maintained by EEE”. This will only display if configured with option “This store has a EEE H/O”, select NO to this option if EEE is in use.
7. You should see a configuration successfully exported message when finished. If export was unsuccessful, ensure the destination path is accessible

Install & configure enabler

Latest Install and upgrade files are available on the magenta website page, http://www.magentaretail.com.au/downloads.php User - islguest Password - isl_pickup If a specific version is required a request can be made to the magenta support desk.

1. Run the Enabler Install executable on machine (install.exe), Enabler by default will be installed on C: drive option to change location and folder name is available. (ensure drive that enabler is installed on is same as the drive referred to in database setup configurations for till)

1. Once install is complete run the manual upgrade command to upgrade till to the currently Enabler version H/O enabler is on. Stores can be on a previous version or the same but never a greater version to H/O Enabler (manual upgrade files need to be extracted to upgrade folder prior to running command refer to upgrade documentation for more help)
2. From Start Menu right click Back Office icon and run as administrator
3. Select the diskette option when prompted and enter path where configuration have been exported to from H/O enabler (import can be done form local folder , a USB memory stick or a network shared folder)
4. Enter till number for till being configured.
5. A valid license number is required to be entered in licence prompt after import of configurations to enable POS to run; a NEW license can be retrieved from the online licensing function.

http://licensing.magentaretail.com.au/weblic/

1. Shut down Back Office and restart all enabler apps from start menu as administrator.

If configured as a store server Nibble.exe will attempt to create and write computer name to a file called workstation.dat in the configured import path. Failure to access this location or write to file because already exist with another compute name may result in nibble displaying red or presenting a warning that another server with same name exists. If configured as a till (node) Nibble.exe will attempt to connect to store server over the LAN

Enabler Sharing

On store server the drive containing Enabler or the Enabler folder is shared as “enserver” depending on what level the databases communication paths are share name set in configurations. Not mandatory but on the till (node) share the drive containing Enabler or the Enabler folder as ‘en’

Update the new store server with master files from EEE

1. If EEE is in use the Data Exporter is used to send master files from EEE to Store (The store would be updated during the first comms session)

From the Enabler Enterprise Edition program group, select EEE Data Exporter

1. Select the Company you wish to export master files for, and then select the Branch name to receive the master file. Branch will only be available to receive exported data, if the option “exclude this branch from data exports” is not ticked in EEE > Location >Branch Maintenance.
2. Select Add All for all tables to be exported, highlight tables not required and double click or select Remove to exclude table from export.
3. On the very first export for branch from the Export method, select Full Export and Generate Zap command for Enabler. This will export all records with a zap command so it clears tables at store and replaces with exported records.
4. Click on EXPORT to commence exporting the selected files.
5. Store server import path ends need to configure to same location exported file is sent to be able to import file. Standard path is \\ EEEservername\eeedata\export\%laddr
6. A Full Masterfile load of new data imported on store server will be automatically sent to store till (node) as a masterfile load if till is configured to receive and is online at time store server imports the file. If till not configured until after import of masterfile a manual masterfile load from store server to till can be performed via Back Office > File Menu> Full Masterfile load

Update the new store server with master files from Enabler H/O (no EEE in Use)

1. On the Enabler Head Office Server from Back Office go to the File Menu
2. Select Full Branch load
3. Select enter to open Full Branch option and again to accept warning to proceed.
4. Enter or select branch code data is being exported to in Send to branches field.
5. Select All for selection of all master file to send to store or highlight each masterfile required and double client or select add.
6. Press OK enter to confirm export and sending of data to branch.
7. A *.bld file will be created in the enabler\comms\tobr\<%laddr> folder and if nibbler is configured to copy data over network will retrieve file when access to location is available and rename file to *.zld and move to enabler\comms\fromho folder and import immediately.
8. If till is configured to receive maintenance and is online at time store server imports the branch load file data will be automatically sent to till as a full load. If till is not configured until after import , a Full Masterfile load can be sent from store server to till when till is communicating with server via Back Office > File Menu> Full Masterfile load

Check that nibbler messages are getting from the tills to the server

(If store till (node) has been setup and configured to communicate with store server test communications is correctly configured) 1. Start-up nibble.exe by right clicking icon in start menu and run as administrator 2. Confirm nibble application has access to LAN error will display if LAN not accessible. Nibble will display as a yellow icon in taskbar tray 3. On a till (node) go to the PoS main screen press <enter> to start a sale 4. Key in 88888 as the user ID then press <enter> 5. You should see a ‘Invalid User ID’ message 6. Go to Back Office on the Store Server 7. Select Reports then Event Log. You should see an invalid user ID event for the till (node) confirming communication is successful.

Add the printers (LPT)

1. Select Start, Settings, Printers 2. Select Add Printer 3. Select Local Printer click on Next 4. Highlight LPT1 click on Next 5. Highlight Generic then Generic/Text Only click on Next 6. Select Keep existing driver click on Next 7. Select No click on Next 8. Select Do not share this printer click on Next 9. Select Yes to print a windows test page 10. Select Next then Finish 11. Open Back Office on till select Till setup, expand Equipment and highlight Receipt printer. Click on config to open configuration screen. Select default printer settings and then connect device to Generic /Test Only drivers. 12. Any integrated EEE functions that need to access the store printer required the store receipt printer to be available on the network and have the required permissions set for User “ EEEservices. “ 13. Add A4 printer and set it as the default so enabler reports can display in correct format 14. For report printing select Till setup, expand equipment and highlight Report Printers. Enable the “Is a report printer attached” option for Printer1, enter printer description and type of printer. Then click on connect device and select A4 printer driver installed. Do the same for Printer 2 but as a receipt printer and connect to Generic Text /Only Drivers .

Add the printers (USB)

(Adding USB printer may differ for different models of printer so any issues please contact Magenta Support)

1. Connect the printer to computer and allow the system to identify an install printer using printer manufacturer drivers
2. Once printer is installed test perform a windows test print through printer properties
3. Select Add Printer and use wizard to add new printer
4. Select Local Printer click on Next
5. Highlight LPT1 click on Next
6. Highlight Generic then Generic/Text Only click on Next
7. Select Keep existing driver click on Next
8. Select No click on Next
9. Select Do not share this printer click on Next
10. Select NO to print a windows test page
11. Select Next then Finish
12. Go into printer properties and assign the USB port to printer drivers
13. Perform a windows test print through printer properties.
14. Open Back Office on till select Till setup, expand Equipment and highlight Receipt printer. Click on config to open configuration screen. Select default printer settings and then connect device to Generic /Test Only drivers.
15. Any integrated EEE functions that need to access the store printer required the store receipt printer to be available on the network and have the required permissions set for User “ EEEservices. “
16. Add A4 printer and set it as the default so enabler reports can display in correct format
17. For report printing select Till setup, expand equipment and highlight Report Printers. Enable the “Is a report printer attached” option for Printer1, enter printer description and type of printer. Then click on connect device and select A4 printer driver installed. Do the same for Printer 2 but as a receipt printer and connect to Generic Text /Only Drivers .

Adjust a float amount

On each till from the PoS main screen, select Till Control, then Float Adjustment.

Program the scanners to read formats used by Enabler

Enabler uses Code39 and Interleave 2of5 formats. Barcode scanners will need to be configured to identify these codes. Once scanner has been configured, test scanning in POS to make sure the product barcodes and transaction barcodes printed on dockets scan in Enabler successfully.

Test the peripherals

Option to test hardware connected to POS is available from the POS main screen

Select File Menu > Peripherals Test Utility

Add POS to startup

To ensure POS is automatically opened on till, add the winpos.exe and nibble.exe from \enabler folder into start up menu for user

Use Company logo in POS

Add the company logo *.bmp (bitmap) files to the \enabler folder (if configured to use non-standard bitmaps to display in POS screens).