Wegener Communications 6420 user manual Wegener Asset Healing, an Overview

www.wegener.com

800070-01 Rev B

Chapter 3, Page 78

MPcm				CSM		iPump, before resync...				iPump, after resync...
Asset Folder on MPcm:				Asset Folder on CSM:		Asset Folder on remote iPump				Asset Folder on remote iPump
<asset root>\assets\				/var/www/html/media/		(one of N targeted by the				(one of N targeted by the
AssetName	The Goal			AssetName		address in AssetName.ini):				address in AssetName.ini):
						<asset root>\assets\				<asset root>\assets\
						AssetName				AssetName
File:	For this remote			File:		File:				File:
AssetName.ini	address, ether a			AssetName.ini		AssetName.ini				AssetName.ini
[SendChanges]	serial number or			[SendChanges]		[SendChanges]				[SendChanges]
<address>=ObjName				<address>=ObjName		<address>=ObjName				<address>=ObjName
	group...
File:				File:		File:	STEP #3:			File:
FirstMediaFile.mp2				FirstMediaFile.mp2		FirstMediaFile.mp2				FirstMediaFile.mp2
}							In response to the STORAGE
							CONFIRM Action tag, the
	…make sure this						iPump uses Return Path to
	asset, and it’s files,						send a negative ACK to CSM
	are sync’d between						for each and every file spec’d
	the iPumps at the						in “metadata.xml” which is
File:	target address and			File:	iPump is missing files	File:	missing from this asset folder.			File:
	this uplink control
LastMediaFile.mp2	system.			LastMediaFile.mp2	which are still	MissingMediaFile.mp2				MissingMediaFile.mp2
					authorized for this		STEP #4:
					asset
							CSM re-downloads any file flagged
				File:			by a NACK to the target address in
							“AssetName.ini” (which may include
	STEP #1:			metadata.xml
							a group in which this iPump is one
CSM finds all such “hot” assets,
							member).
and copies them over to the
						File:				File:
CSM folder shown. Then it
creates this file in each asset						LastMediaFile.mp2				LastMediaFile.mp2
folder, which summarizes all
files currently in Asset at uplink.							STEP #5:
					iPump has extra files no	File:	In response to the STORAGE			File:
ASSET HEALING:					longer authorized for this	ExtraMediaFile.mp2	CLEANUP Action tag, the iPump			ExtraMediaFile.mp2
					asset		quietly deletes all files not specified
Asset healing is initiated when the
							in “metadata.xml”.
“csm_fsync.pl” script is invoked (from an					STEP #2:
FSYNC shell script called from “cron” on the
			CSM downloads the file “metadata.xml” to the target asset			File:	STEP #6:			File:
COMPEL/CSM machine). This causes the first
				folder in all iPumps at the address spec’d in the		metadata.xml	When done, the iPump renames the			Z_metadata.xml
2 steps to be executed within CSM. The
				“AssetName.ini” file. Included within that file are “Action			“metadata.xml” file to
response to the incoming file NACKs from field
		Tags” which requests the iPump implement the STORAGE					“z_metadata.xml”, deleting any
iPumps is handled by the “mpcm_compel.cgi”
				CONFIRM & STORAGE CLEANUP functions.			previous version of
script. (Note that Step #5 shown does not
							“z_metadata.xml”.
literally occur, in time, after steps #3 and 4. But		NOTE: If asset folder does exist on any addressed iPump,
since the process of getting files re-downloaded
				then it is created and “metadata.xml” is copied therein.
is not connected to the process of deleting the
“unauthorized files”, this is irrelevant to										Non-existent OR
understanding the steps involved.)										deleted file
	WEGENER “Asset Healing”, an Overview								File	}
Rev								Legend
										Existing file
7/21/2009 5:05 PM

Figure 3-16: Asset Healing in operation	iPump
	6420 User’s Manual