Enabler Upgrades - Revision history

Brant: /* Is the scheduler setup the same for all machines? */

2016-02-18T22:44:37Z

Is the scheduler setup the same for all machines?

← Older revision		Revision as of 22:44, 18 February 2016
Line 105:		Line 105:
	#On the HO Server, start Back Office		#On the HO Server, start Back Office
	#Select Global Setup		#Select Global Setup
			#On the left hand side of the screen, ensure the company is selected at the highest level.
	#On the right hand side of the screen select:		#On the right hand side of the screen select:
	#Transaction Processing / Comms → Scheduler Setup → Config		#Transaction Processing / Comms → Scheduler Setup → Config
	#When prompted, choose either 'Store Server' or 'Tills'		#When prompted, choose either 'All', 'Store Server' or 'Tills'
	#~~Complete~~ the details as required for each machine type:		#Review the details as required for each machine type:
	#:		#:
	[[Image:Enabler_Upgrades_Figure_5.jpg\|400px\|link=]]		[[Image:Enabler_Upgrades_Figure_5.jpg\|400px\|link=]]

Brant: /* Is the scheduler setup the same for all machines? */

2016-02-18T22:43:10Z

Is the scheduler setup the same for all machines?

← Older revision		Revision as of 22:43, 18 February 2016
Line 101:		Line 101:
	It is important that all machines in the store have the same scheduled setup times. End of day (EoD) shuts down any Enabler applications that might be running and resume till restarts them. The upgrade needs to be scheduled so it does not conflict with overnight scheduled processes.		It is important that all machines in the store have the same scheduled setup times. End of day (EoD) shuts down any Enabler applications that might be running and resume till restarts them. The upgrade needs to be scheduled so it does not conflict with overnight scheduled processes.

	<span style="color: red">'''Note:''' Ideally the upgrade should run overnight after EoD and purge and backup has completed and before the Till resumes. Please refer to [[#Enabler_Backup_and_Restore\|The Oracle wiki article]] on setting up backup on machines</span>		<span style="color: red">'''Note:''' Ideally the upgrade should run overnight after EoD and purge and backup has completed and before the Till resumes. Please refer to [[Enabler_Backup_and_Restore\|The Oracle wiki article]] on setting up backup on machines</span>

	#On the HO Server, start Back Office		#On the HO Server, start Back Office

Brant: /* Is the scheduler setup the same for all machines? */

2016-02-18T22:42:43Z

Is the scheduler setup the same for all machines?

← Older revision		Revision as of 22:42, 18 February 2016
Line 101:		Line 101:
	It is important that all machines in the store have the same scheduled setup times. End of day (EoD) shuts down any Enabler applications that might be running and resume till restarts them. The upgrade needs to be scheduled so it does not conflict with overnight scheduled processes.		It is important that all machines in the store have the same scheduled setup times. End of day (EoD) shuts down any Enabler applications that might be running and resume till restarts them. The upgrade needs to be scheduled so it does not conflict with overnight scheduled processes.

	<span style="color: red">'''Note:''' Ideally the upgrade should run overnight after EoD and purge and backup has completed and before the Till resumes. Please refer to [[#~~Enabler Backup and Restore~~\|The Oracle wiki article]] on setting up backup on machines</span>		<span style="color: red">'''Note:''' Ideally the upgrade should run overnight after EoD and purge and backup has completed and before the Till resumes. Please refer to [[#Enabler_Backup_and_Restore\|The Oracle wiki article]] on setting up backup on machines</span>

	#On the HO Server, start Back Office		#On the HO Server, start Back Office

Brant: /* Is the scheduler setup the same for all machines? */

2016-02-18T22:40:33Z

Is the scheduler setup the same for all machines?

← Older revision		Revision as of 22:40, 18 February 2016
Line 101:		Line 101:
	It is important that all machines in the store have the same scheduled setup times. End of day (EoD) shuts down any Enabler applications that might be running and resume till restarts them. The upgrade needs to be scheduled so it does not conflict with overnight scheduled processes.		It is important that all machines in the store have the same scheduled setup times. End of day (EoD) shuts down any Enabler applications that might be running and resume till restarts them. The upgrade needs to be scheduled so it does not conflict with overnight scheduled processes.

	<span style="color: red">'''Note:''' Ideally the upgrade should run overnight after EoD and purge and backup has completed and before the Till resumes. Please refer to [[#~~Enabler_Backup_and_Restore~~\|The Oracle wiki article]] on setting up backup on machines</span>		<span style="color: red">'''Note:''' Ideally the upgrade should run overnight after EoD and purge and backup has completed and before the Till resumes. Please refer to [[#Enabler Backup and Restore\|The Oracle wiki article]] on setting up backup on machines</span>

	#On the HO Server, start Back Office		#On the HO Server, start Back Office

Brant: /* Configure Scheduler for all machines in a store */

2016-02-18T22:40:06Z

Configure Scheduler for all machines in a store

← Older revision		Revision as of 22:40, 18 February 2016
Line 98:		Line 98:
	StoreServerName = the Store Server’s machine name or IP Address		StoreServerName = the Store Server’s machine name or IP Address

	===~~Configure Scheduler~~ for all machines ~~in a store~~===		=== Is the scheduler setup the same for all machines? ===
	It is important that all machines in the store have the same scheduled setup times. 'End of day (EoD)' shuts down any Enabler applications that might be running and ~~'Resume Till'~~ restarts them. The upgrade needs to be scheduled so it does not conflict with overnight scheduled processes.		It is important that all machines in the store have the same scheduled setup times. End of day (EoD) shuts down any Enabler applications that might be running and resume till restarts them. The upgrade needs to be scheduled so it does not conflict with overnight scheduled processes.

	<span style="color: red">'''Note:''' ~~It is important that~~ the upgrade ~~is scheduled to occur between EOD~~ and ~~Resume~~ Till ~~times~~. ~~Nibbler is required~~ to ~~be running~~ on ~~all tills flagged as online for auto upgrade to successfully proceed.~~</span>		<span style="color: red">'''Note:''' Ideally the upgrade should run overnight after EoD and purge and backup has completed and before the Till resumes. Please refer to [[#Enabler_Backup_and_Restore\|The Oracle wiki article]] on setting up backup on machines</span>

	#On the HO Server, start Back Office		#On the HO Server, start Back Office

Brant: /* Downloading upgrade packs from the web site */

2016-02-18T22:33:55Z

Downloading upgrade packs from the web site

← Older revision		Revision as of 22:33, 18 February 2016
Line 10:		Line 10:

	Clicking on the title of the upgrade pack will enable the file to be opened or downloaded.		Clicking on the title of the upgrade pack will enable the file to be opened or downloaded.

			Contact Magenta Support for credentials to log onto the FTP site to download files

	Click on save to download upgrade packs to a local directory.		Click on save to download upgrade packs to a local directory.
Line 15:		Line 17:
	The upgrade version and type of upgrade can be identified by the file name.		The upgrade version and type of upgrade can be identified by the file name.

	The auto upgrade pack is a zip file and identified by the file name starting with _u ie: _u406602.zip. Do NOT extract this file. The upgrade file is copied to branches and Enabler executes the upgrade process as a scheduled task. Nibbler must be running on all tills in the branch during upgrade process. Refer to the [[#Auto Upgrades\|Auto Upgrades]] section for further details		The auto upgrade pack is a zip file and identified by the file name starting with _u ie: _u406602.zip. Do NOT extract this file. The upgrade file is copied to branches and Enabler executes the upgrade process as a scheduled task. Nibbler must be running on all online tills in the branch during upgrade process. Refer to the [[#Auto Upgrades\|Auto Upgrades]] section for further details

	A ~~manual~~ Upgrade file should be extracted and the upgrade is executed via a command prompt manually. All Enabler applications including nibbler must be shut down prior to running the upgrade command. The upgrade process only upgrades the till ~~it’s~~ being ~~run~~ on. Refer to the [[#Manual Upgrades\|Manual Upgrades]] section for further details		A Manual Upgrade file should be extracted and the upgrade is executed via a command prompt manually. All Enabler applications including nibbler must be shut down prior to running the upgrade command. The upgrade process only upgrades the till it is being applied on. Refer to the [[#Manual Upgrades\|Manual Upgrades]] section for further details

	'''Note:''' If you are looking for a specific version of Enabler other than the latest release, please contact [mailto:support@magentaretail.com.au Magenta Support] and we will provide details for downloading required version.		'''Note:''' If you are looking for a specific version of Enabler other than the latest release, please contact [mailto:support@magentaretail.com.au Magenta Support] and we will provide details for downloading required version.

Brant: /* Store Till Upgrade Path Setup */

2016-02-18T05:51:29Z

Store Till Upgrade Path Setup

← Older revision		Revision as of 05:51, 18 February 2016
Line 90:		Line 90:
	The auto upgrade path differs between Store Servers and Tills and must be configured separately. The store server (master) will copy the auto upgrade pack locally from Head office prior to running the upgrade. The store till (node) will use the upgrade pack copied on the store server.		The auto upgrade path differs between Store Servers and Tills and must be configured separately. The store server (master) will copy the auto upgrade pack locally from Head office prior to running the upgrade. The store till (node) will use the upgrade pack copied on the store server.

	~~##StoreServerName~~ = ~~the Store Server’s machine name or IP Address~~		[[Image:Enabler_Upgrades_EnablerNodesToConfigure.jpg\|400px\|link=]]

	[[Image:Enabler_Upgrades_Figure_4.jpg\|400px\|link=]]		[[Image:Enabler_Upgrades_Figure_4.jpg\|400px\|link=]]

			StoreServerName = the Store Server’s machine name or IP Address

	===Configure Scheduler for all machines in a store===		===Configure Scheduler for all machines in a store===

Brant: /* Store Server Upgrade Path Setup */

2016-02-18T05:50:26Z

Store Server Upgrade Path Setup

← Older revision		Revision as of 05:50, 18 February 2016
Line 75:		Line 75:
	#When prompted to apply changes, choose "Store Server"		#When prompted to apply changes, choose "Store Server"
	#Complete the database paths for all Store servers (this assumes all servers have enabler installed on same drive letter otherwise make changes at each branch level)		#Complete the database paths for all Store servers (this assumes all servers have enabler installed on same drive letter otherwise make changes at each branch level)
			[[Image:Enabler_Upgrades_EnablerNodesToConfigure.jpg\|400px\|link=]]

	[[Image:Enabler_Upgrades_Figure_3.jpg\|400px\|link=]]		[[Image:Enabler_Upgrades_Figure_3.jpg\|400px\|link=]]

Brant: /* Configure the correct upgrade path for all machines in a store */

2016-02-18T05:47:42Z

Configure the correct upgrade path for all machines in a store

← Older revision		Revision as of 05:47, 18 February 2016
Line 66:		Line 66:
	The auto upgrade path differs between Store Servers and Tills and must be configured separately. The store server will copy the auto upgrade pack locally from Head office prior to running the upgrade. The store till will use the upgrade pack copied on the store server.		The auto upgrade path differs between Store Servers and Tills and must be configured separately. The store server will copy the auto upgrade pack locally from Head office prior to running the upgrade. The store till will use the upgrade pack copied on the store server.

	#Complete the details as follows for each machine type:		Complete the details as follows for each machine type:

	====Store Server Upgrade Path Setup====		====Store Server Upgrade Path Setup====

Brant: /* Auto Upgrades */

2016-02-18T05:41:58Z

Auto Upgrades

← Older revision		Revision as of 05:41, 18 February 2016
Line 62:		Line 62:
	'''Note:''' This guide assumes that the Enabler folder on the Head Office Server and Store Servers has been shared as the share name: enserver. It is also assumed that the store connects to the HO Server via a standard TCP/IP based WAN.		'''Note:''' This guide assumes that the Enabler folder on the Head Office Server and Store Servers has been shared as the share name: enserver. It is also assumed that the store connects to the HO Server via a standard TCP/IP based WAN.
	For a document that outlines upgrades via Batch File Comms, contact Magenta Support.		For a document that outlines upgrades via Batch File Comms, contact Magenta Support.

	===Configure the correct upgrade path for all machines in a store===		===Configure the correct upgrade path for all machines in a store===
	The auto upgrade path differs between Store Servers and Tills and must be configured separately. The store server will copy the auto upgrade pack locally from Head office prior to running the upgrade. The store till will use the upgrade pack copied on the store server.		The auto upgrade path differs between Store Servers and Tills and must be configured separately. The store server will copy the auto upgrade pack locally from Head office prior to running the upgrade. The store till will use the upgrade pack copied on the store server.

			#Complete the details as follows for each machine type:

			====Store Server Upgrade Path Setup====
	#On the Head Office Server, start Back Office		#On the Head Office Server, start Back Office
	#Select Global Setup		#Select Global Setup
			#On the left hand side of the screen, ensure the company is selected at the highest level.
	#On the right hand side of the screen select: Transaction Processing/Comms → Version Control Setup → Config		#On the right hand side of the screen select: Transaction Processing/Comms → Version Control Setup → Config
	#When prompted, choose ~~either '~~Store Server~~' or 'Tills'~~		#When prompted to apply changes, choose "Store Server"
	#Complete the ~~details as follows~~ for each ~~machine type~~:		#Complete the database paths for all Store servers (this assumes all servers have enabler installed on same drive letter otherwise make changes at each branch level)
	~~===~~=~~Store Server Upgrade Path Setup====~~		[[Image:Enabler_Upgrades_Figure_3.jpg\|400px\|link=]]
	~~This is the correct configuration for a store server~~

	HOServerName = the HO Server’s machine name or IP Address		HOServerName = the HO Server’s machine name or IP Address

	~~[[Image:Enabler_Upgrades_Figure_3.jpg\|400px\|link=]]~~

	====Store Till Upgrade Path Setup====		====Store Till Upgrade Path Setup====
	~~This~~ is the ~~correct configuration~~ for a till ~~in a~~ store.		#On the Head Office Server, start Back Office
			#Select Global Setup
			#On the left hand side of the screen, ensure the branch is selected
			#On the right hand side of the screen select: Transaction Processing/Comms → Version Control Setup → Config
			#When prompted to apply changes, choose "Tills”"
			#Complete the database paths for all tills
			The auto upgrade path differs between Store Servers and Tills and must be configured separately. The store server (master) will copy the auto upgrade pack locally from Head office prior to running the upgrade. The store till (node) will use the upgrade pack copied on the store server.

	StoreServerName = the Store Server’s machine name or IP Address		##StoreServerName = the Store Server’s machine name or IP Address

	[[Image:Enabler_Upgrades_Figure_4.jpg\|400px\|link=]]		[[Image:Enabler_Upgrades_Figure_4.jpg\|400px\|link=]]
Line 86:		Line 95:
	It is important that all machines in the store have the same scheduled setup times. 'End of day (EoD)' shuts down any Enabler applications that might be running and 'Resume Till' restarts them. The upgrade needs to be scheduled so it does not conflict with overnight scheduled processes.		It is important that all machines in the store have the same scheduled setup times. 'End of day (EoD)' shuts down any Enabler applications that might be running and 'Resume Till' restarts them. The upgrade needs to be scheduled so it does not conflict with overnight scheduled processes.

	'''Note:''' ~~Ideally~~ the upgrade ~~should run overnight after EoD~~ and ~~purge and backup has completed and before the~~ Till ~~resumes~~. ~~Please refer~~ to ~~[[Enabler_Backup_and_Restore\|Enabler Backup and Restore]]~~ on ~~setting up Enabler backups on machines~~		<span style="color: red">'''Note:''' It is important that the upgrade is scheduled to occur between EOD and Resume Till times. Nibbler is required to be running on all tills flagged as online for auto upgrade to successfully proceed.</span>

	#On the HO Server, start Back Office		#On the HO Server, start Back Office