Creating new stores with EEE - Revision history

Luke at 00:07, 30 July 2019

2019-07-30T00:07:20Z

Brant: /* Process for creating new stores with EEE & Enabler */

2014-10-03T05:49:36Z

Process for creating new stores with EEE & Enabler

Brant: /* Add the printers (LPT) */

2014-10-03T05:47:03Z

Add the printers (LPT)

← Older revision		Revision as of 05:47, 3 October 2014
Line 132:		Line 132:
	=====Add the printers (LPT)=====		=====Add the printers (LPT)=====

	1. Select Start, Settings, Printers		# Select Start, Settings, Printers
	2. Select Add Printer		# Select Add Printer
	3. Select Local Printer click on Next		# Select Local Printer click on Next
	4. Highlight LPT1 click on Next		# Highlight LPT1 click on Next
	5. Highlight Generic then Generic/Text Only click on Next		# Highlight Generic then Generic/Text Only click on Next
	6. Select Keep existing driver click on Next		# Select Keep existing driver click on Next
	7. Select No click on Next		# Select No click on Next
	8. Select Do not share this printer click on Next		# Select Do not share this printer click on Next
	9. Select Yes to print a windows test page		# Select Yes to print a windows test page
	~~10.~~ Select Next then Finish		# 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.		# 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. “		# 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		# 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 .		# 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 Printer2 but as a receipt printer and connect to Generic Text/Only Drivers.

	=====Add the printers (USB)=====		=====Add the printers (USB)=====

Brant: /* Check that nibbler messages are getting from the tills to the server */

2014-10-03T05:46:13Z

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

← Older revision		Revision as of 05:46, 3 October 2014
Line 122:		Line 122:
	=====Check that nibbler messages are getting from the tills to the server=====		=====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)		(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		# 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		# 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		# 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>		# Key in 88888 as the user ID then press <enter>
	5. You should see a ‘Invalid User ID’ message		# You should see a ‘Invalid User ID’ message
	6. Go to Back Office on the Store Server		# 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.		# 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)=====		=====Add the printers (LPT)=====

Brant: /* Install & configure enabler */

2014-10-03T05:45:25Z

Install & configure enabler

← Older revision		Revision as of 05:45, 3 October 2014
Line 82:		Line 82:
	Password - isl_pickup		Password - isl_pickup
	If a specific version is required a request can be made to the magenta support desk.		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)		# 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)

	2. 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)		# 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)
	3. From Start Menu right click Back Office icon and run as administrator		# From Start Menu right click Back Office icon and run as administrator
	4. 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)		# 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)
	5. Enter till number for till being configured.		# Enter till number for till being configured.
	6. 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.		# 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/		http://licensing.magentaretail.com.au/weblic/
	7. Shut down Back Office and restart all enabler apps from start menu as administrator.		# 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 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		If configured as a till (node) Nibble.exe will attempt to connect to store server over the LAN

Brant: /* Process for creating new stores with EEE & Enabler */

2014-10-03T05:44:30Z

Process for creating new stores with EEE & Enabler

Show changes

Brant at 04:56, 3 October 2014

2014-10-03T04:56:16Z

Show changes

Trevor at 04:29, 14 January 2011

2011-01-14T04:29:37Z

Trevor at 00:58, 19 October 2009

2009-10-19T00:58:34Z

← Older revision		Revision as of 00:58, 19 October 2009
Line 1:		Line 1:
	Created: 14 October 2009. Last Reviewed: 15 October 2009		Created: 14 October 2009. Last Reviewed: 19 October 2009


Line 26:		Line 26:
	# If you have multiple tills and wish to backup your Enabler databases and configuration to another machine on the local network, follow this step.Select Transaction Processing / Comms, Backup Options Setup then replace the backup path with the path to another machine on your local network, e.g. \\tillanme\en\enabler\backup		# If you have multiple tills and wish to backup your Enabler databases and configuration to another machine on the local network, follow this step.Select Transaction Processing / Comms, Backup Options Setup then replace the backup path with the path to another machine on your local network, e.g. \\tillanme\en\enabler\backup
	# If there is only one machine (store server) in the new branch, skip to “export the configuration”.<br/> '''Add Any Tills (nodes)'''		# If there is only one machine (store server) in the new branch, skip to “export the configuration”.<br/> '''Add Any Tills (nodes)'''
	# Highlight a till(node on an existing branch then click ~~omn~~ Clone.		# Highlight a till(node on an existing branch then click on Clone.
	# Click on the name of the Branch where you are adding the new till, then key in the 2 digit till number, Press Tab then key in the name/location of the till, then press Enter.		# Click on the name of the Branch where you are adding the new till, then key in the 2 digit till number, Press Tab then key in the name/location of the till, then press Enter.
	# Highlight the new till on the left hand side		# Highlight the new till on the left hand side

Trevor at 01:11, 15 October 2009

2009-10-15T01:11:12Z

← Older revision		Revision as of 01:11, 15 October 2009
Line 1:		Line 1:
	Created: 14 October 2009. Last Reviewed: 14 October 2009		Created: 14 October 2009. Last Reviewed: 15 October 2009

← Older revision		Revision as of 00:07, 30 July 2019
Line 74:		Line 74:
	=====Install & configure enabler=====		=====Install & configure enabler=====
	Latest Install and upgrade files are available on the magenta website page,		Latest Install and upgrade files are available on the magenta website page,
	~~http~~://~~www.~~magentaretail.com.au/downloads~~.php~~		https://magentaretail.com.au/downloads/
	~~User - islguest~~
	~~Password - isl_pickup~~
	If a specific version is required a request can be made to the magenta support desk.		If a specific version is required a request can be made to the magenta support desk.
	# 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)		# 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)
Line 85:		Line 84:
	# Enter till number for till being configured.		# Enter till number for till being configured.
	# 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.		# 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/		https://licensing.magentaretail.com.au/weblic/
	# Shut down Back Office and restart all enabler apps from start menu as administrator.		# 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 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.

← Older revision		Revision as of 05:49, 3 October 2014
Line 23:		Line 23:

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


	=====Add the new branch in Enabler (no EEE environment)=====		=====Add the new branch in Enabler (no EEE environment)=====
Line 33:		Line 32:
	#* Ensure offline flag is set correctly. Once disabled maintenance files will be created for new branch.		#* Ensure offline flag is set correctly. Once disabled maintenance files will be created for new branch.
	# Select OK enter to save new branch records		# Select OK enter to save new branch records


	=====Add the store server in Enabler=====		=====Add the store server in Enabler=====
Line 47:		Line 45:
	#*Time Server (UNC name) \\servername		#*Time Server (UNC name) \\servername
	# If you have multiple tills and wish to backup your Enabler databases and configuration to another machine on the local network, follow this step. <br /><br />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''		# If you have multiple tills and wish to backup your Enabler databases and configuration to another machine on the local network, follow this step. <br /><br />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=====		=====Add tills (nodes) in Enabler=====
Line 95:		Line 91:

	=====Enabler Sharing=====		=====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.		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’		Not mandatory but on the till (node) share the drive containing Enabler or the Enabler folder as ‘en’
Line 110:		Line 105:

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

	# On the Enabler Head Office Server from Back Office go to the File Menu		# On the Enabler Head Office Server from Back Office go to the File Menu
	# Select Full Branch load		# Select Full Branch load
Line 131:		Line 125:

	=====Add the printers (LPT)=====		=====Add the printers (LPT)=====

	# Select Start, Settings, Printers		# Select Start, Settings, Printers
	# Select Add Printer		# Select Add Printer
Line 148:		Line 141:

	=====Add the printers (USB)=====		=====Add the printers (USB)=====

	(Adding USB printer may differ for different models of printer so any issues please contact Magenta Support)		(Adding USB printer may differ for different models of printer so any issues please contact Magenta Support)
	# Connect the printer to computer and allow the system to identify an install printer using printer manufacturer drivers		# Connect the printer to computer and allow the system to identify an install printer using printer manufacturer drivers
Line 169:		Line 161:

	=====Adjust a float amount=====		=====Adjust a float amount=====

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

	=====Program the scanners to read formats used by Enabler=====		=====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.		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=====		=====Test the peripherals=====

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

Line 186:		Line 175:

	=====Use Company logo in POS=====		=====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).		Add the company logo *.bmp (bitmap) files to the \enabler folder (if configured to use non-standard bitmaps to display in POS screens).

← Older revision		Revision as of 04:29, 14 January 2011
Line 1:		Line 1:
	Created: 14 October 2009. Last Reviewed: ~~19 October 2009~~		Created: 14 October 2009. Last Reviewed: 14 January 2011


Line 10:		Line 10:


	# The new store should be initially created EEE from Location Management->Branch. As all branches must have a unique branch code and logical address, you can use the Branch browse screen to determine whether a branch code has already been used. Till Maintenance (Point Of Sales->Pos Till Maintenance) can be used to identify what logical addresses have been used. As an example, if you are adding a branch and that branch is in a region whose logical address is 02, you could search in Till Maintenance for all tills than contain 02, including those starting with 02.		# The new store should be initially created in EEE from Location Management->Branch. As all branches must have a unique branch code and logical address, you can use the Branch browse screen to determine whether a branch code has already been used. Till Maintenance (Point Of Sales->Pos Till Maintenance) can be used to identify what logical addresses have been used. As an example, if you are adding a branch and that branch is in a region whose logical address is 02, you could search in Till Maintenance for all tills than contain 02, including those starting with 02.
	# When creating a new branch in EEE, the Logical Address and Directory must be the same. When you populate the Logical Address field, this value will also be placed in the Directory field. All Mandatory fields are marked with an <nowiki>*</nowiki>.When a new store is created the following fields are ticked by default. If they don't apply, you should remove the ticks where applicable.(i) Consider Branch when re-ordering(ii) Consider branch when replenishing(iii) Allow purchase ordering for this branch(iv) Maintain Costs(v) Maintain Prices(vi) Maintain Min Max		# When creating a new branch in EEE, the Logical Address and Directory must be the same. When you populate the Logical Address field, this value will also be placed in the Directory field. All Mandatory fields are marked with an <nowiki>*</nowiki>.When a new store is created the following fields are ticked by default. If they don't apply, you should remove the ticks where applicable.(i) Consider Branch when re-ordering(ii) Consider branch when replenishing(iii) Allow purchase ordering for this branch(iv) Maintain Costs(v) Maintain Prices(vi) Maintain Min Max
	# If the Enabler machines are not being setup at the same time as the branch is being created, you should turn on the flag “Do not export data to this branch”, otherwise Data exporter will export data and continue to re-export data as it won't be receiving an acknowledgement for the exported data.		# If the Enabler machines are not being setup at the same time as the branch is being created, you should turn on the flag “Do not export data to this branch”, otherwise Data exporter will export data and continue to re-export data as it won't be receiving an acknowledgement for the exported data.
	# After clicking on SAVE to create the branch, you are then prompted whether to clone Prices, Costs, Branch Purge Parameters and Min/Max from another branch. You also have the option of skipping the cloning process. To clone, from another branch, enter a branch code beside each option and then press OK to proceed with cloning. If you don't clone data here, you must populate at least costs and prices from another method ~~otherwise~~ otherwise when data is exported to the store, products will have no prices or costs.		# After clicking on SAVE to create the branch, you are then prompted whether to clone Prices, Costs, Branch Purge Parameters and Min/Max from another branch. You also have the option of skipping the cloning process. To clone, from another branch, enter a branch code beside each option and then press OK to proceed with cloning. If you don't clone data here, you must populate at least costs and prices from another method otherwise when data is exported to the store, products will have no prices or costs.
	# If the option “Do not export data to this branch” was not ticked, you will be prompted to set the last export date for stores. If you want all master file data exported from Enabler, then select the option “Leave Last Export Date/Time Unchanged”, otherwise you can specify an date and all data modified since that date will be exported to Enabler.		# If the option “Do not export data to this branch” was not ticked, you will be prompted to set the last export date for stores. If you want all master file data exported from Enabler, then select the option “Leave Last Export Date/Time Unchanged”, otherwise you can specify an date and all data modified since that date will be exported to Enabler.
	# The creation of the branch in EEE is now complete. To get the branch details into Enabler HO so that you can create the tills, perform an export of new data from EEE to Enabler HO using EEE Data Exporter.		# The creation of the branch in EEE is now complete. To get the branch details into Enabler HO so that you can create the tills, perform an export of new data from EEE to Enabler HO using EEE Data Exporter.
Line 23:		Line 23:
	# Key in the new branch details, press enter.		# Key in the new branch details, press enter.
	# Select Sales, Docket Setup then key in the correct header details, press enter.		# Select Sales, Docket Setup then key in the correct header details, press enter.
	# Select Transaction Processing / Comms, Communication then replace the machine ~~nam e~~ with the store servers machine name in the following fields: Database server (UNC name) \\servername Time Server (UNC name) \\servername		# Select Transaction Processing / Comms, Communication then replace the machine name with the store servers machine name in the following fields: Database server (UNC name) \\servername Time Server (UNC name) \\servername
	# If you have multiple tills and wish to backup your Enabler databases and configuration to another machine on the local network, follow this step.Select Transaction Processing / Comms, Backup Options Setup then replace the backup path with the path to another machine on your local network, e.g. \\~~tillanme~~\en\enabler\backup		# If you have multiple tills and wish to backup your Enabler databases and configuration to another machine on the local network, follow this step.Select Transaction Processing / Comms, Backup Options Setup then replace the backup path with the path to another machine on your local network, e.g. \\tillname\en\enabler\backup
	# If there is only one machine (store server) in the new branch, skip to “export the configuration”.<br/> '''Add Any Tills (nodes)'''		# If there is only one machine (store server) in the new branch, skip to “export the configuration”.<br/> '''Add Any Tills (nodes)'''
	# Highlight a till(node on an existing branch then click on Clone.		# Highlight a till(node on an existing branch then click on Clone.
Line 31:		Line 31:
	# Select Sales, Docket Setup then key in the correct header details, then press Enter.		# Select Sales, Docket Setup then key in the correct header details, then press Enter.
	# Select Transaction Processing / Comms, Communication then replace the machine name with the 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'''		# Select Transaction Processing / Comms, Communication then replace the machine name with the 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'''
	# Select Database Setup then replace the machine name with the store servers machine name in the following fields:-Lan Transactions [//servername/enserver/enabler/lantran \\servername\enserver\enabler\lantran]Lan Master Files [//servername/enserver/enabler/local \\servername\enserver\enabler\local]Lan Maintenance files [//servername/enserver/enabler/lanmnt \\servername\enserver\enabler\lanmnt]		# Select Database Setup then replace the machine name with the store servers machine name in the following fields:-Lan Transactions [file://servername/enserver/enabler/lantran \\servername\enserver\enabler\lantran]Lan Master Files [file://servername/enserver/enabler/local \\servername\enserver\enabler\local]Lan Maintenance files [file://servername/enserver/enabler/lanmnt \\servername\enserver\enabler\lanmnt]
	# 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 \\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 the Enabler Configuration'''		# Select Transaction Processing / Comms, Version Control Setup then replace the machine name with the store servers machine name:Upgrade Package Path [file://servername/enserver/enabler/comms/upgpack \\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 the Enabler Configuration'''
	# From Back Office select Global Setup		# From Back Office select Global Setup
	# Highlight the Store Branch Name		# Highlight the Store Branch Name