Automation using Action Regenerator for custom file distribution

Customizations
1

(imported topic written by phil_imray91)

We have a requirement to automatically distribute a file that may be updated daily.

I understand the action regenerator works for externally subscribed sites where the source fixlet is updated. In the Action Regenerator example, it is the Anti-Pest updates being shown and from looking at this I see that the name of the download file changes for each update.

Is there an accepted method of automatically updating the source fixlet such that it’s signature can be authenticated and the Action Regenerator recognises that it is different to the last file that was downloaded?

Thanks, Phil

2

(imported comment written by BenKus)

Hey Phil,

How big is the file you are sending around? Is the name/location of the file predetermined?

It seems likely that you will want to use the BigFix API for this function (the action regenerator is based on the BigFix API).

Ben

3

(imported comment written by phil_imray91)

Hi Ben,

The files are around 5Mb in size but as they are XML, we will compress them (unless BigFix compresses data being transferred on the fly?).

The location and the name of the file is within our control and so can be the same or different each time.

Any further pointers would be great!

Rgds. Phil

4

(imported comment written by BenKus)

Hi Phil,

Try this:

  1. Install the BigFix Platform API (the action regenerator comes with the BigFix API that you can install) on one of your systems (you can do it on the BigFix Server if you want).

  2. Download our BESImportFile.exe from http://software.bigfix.com/download/bes/util/BESImportFile.exe

  3. Create an action in BigFix that downloads your file.

  4. Export your action to a file downloadfileaction.bes.

Using the BESImportFile.exe, you can import Fixlets/Tasks/Properties/Actions/Baselines into the BES Console. So…

  1. Modify your exported downloadfileaction.bes file to download the new file.

  2. Run BESImportFile.exe to import your action into the console (note that it will run as if you targeted “all computers”). For example:

besimportfile.exe username password bes_bfenterprise “C:\BES Keys\publisher.pvk” “C:\downloadfileaction.bes”

And your action will be run…

So the only trick will be to automatically modify the .bes file with the new file and run that command line periodically.

Ben