UploadManager and Archive function

(imported topic written by zomv91)

Dear forum members,

I am looking for a solution that can upload a file from a TEM client to the TEM Server and then automatically copy that file to a user accessable location on the TEM server.

I understand that the UploadManager can be used to upload files to the BES server, however this data is then stored in a directory: xxx/xxxx/SHA1/aa/bbbbbb

where aa is the last two digits of the Internal TEM clientID and bbbbbbb is the full TEM clientID

this is how we want to solve this:

Action 1) run on Source TEM client: Upload the file

Action 2) run on TEM Server TEM client: Copy the uploaded file to the desired location these actions run as a Baseline and get there input (file name etc) from a config file that is downloaded and evaluated at the beginning of each Action.

Question 1)

Is there a way to determine the clientID of a given server on the TEM server (using relevance or whatever)

Is there a way to get the full directory path for the uploaded file on the TEM server (remember it is an automated script no user interaction) Is there an Uploadmanger log on the TEM server we can query or do we need to do a file scan on the complete directory structure?

I hope you can help me with this.

Cheers,

Mick van der Vegt

(imported comment written by SystemAdmin)

Mick,

This isn’t as easy as it could/should be. However it is doable. (Wishlist item for IBM/TEM: flexibility to designate the folder structure into which Upload manager deposits files, preferably based on a regex/convention.)

We run a four step process daily. The first two are on the clients, the last two are on the server.

  1. Dump whatever logs/files into a common location locally. We also create a file called computername.txt into which is echoed the computer name. This becomes important later.

  2. Upload parameters are set and the actual upload occurs from the client.

  3. On the server, we have a folder structure for all of the various types of data being uploaded. The previous contents are cleared. Then a batch file is dynamically built each day that basically xcopies files based on naming convention or file type into the respective folder structure location. This is the tricky part to get correct. It is also where the computername.txt file comes into play.

Appendfile {(“xcopy %22” & item 0 of it & “file_convention.log%22 %22d:\destination_folder_structure%22 /E /C /I /Y%0d%0a” ) of ((pathnames of it, lines 1 of files “Name_0_computername.txt” of it as string) of folders of folders of it ) of folders “e:\BigFix Enterprise\BES Server\UploadManagerData\BufferDir\sha1” whose (exists file “name_0_computername.txt” of folders of folders of it)}

Repeat lines like this as necessary substituting file conventions and folder structures as needed. Then execute the batch.

WARNING: Make sure you have plenty of IOPS available on your disk subsystem before you do any amount of files. Depending on the amount of files, server CPU, and disk subsystem, it may take a while to build the batch (which might be several MB by the time you’re done) and execute it. Do this processing off-hours.

  1. Clear the upload manager folder structure (under the SHA1 folder) to prepare for tomorrow’s files. Sometimes we also automate compressing the uploaded files into an archive, then ftping them to their final destination.

This process has moved tens of thousands and GB of files for us. Careful planning of the execution times (policy actions) of these steps is key. Also having substantial I/O capability is recommended such as RAID 10 on enterprise grade disk.

(imported comment written by zomv91)

John,

Thanks for the reply, I was already a bit worried that a process like described is needed …

Thanks again.

Cheers,

Mick

(imported comment written by BenKus)

My favorite way to do it is to modify the right-click computer menu to browse to the server upload manager folder… Here is how:

  1. Make the “UploadManagerData” folder in your BigFix Server folder a Windows share.

  2. Create a .reg file (change “shareservername” to the name of the BigFix Server) with the info below…

  3. Import the .reg file on each console.

HKEY_CURRENT_USER\Software\BigFix\Enterprise Console\Settings\ComputerListContextMenuExtensions\uploadmanager
"MenuDisplayName"="&View Upload Manager Files"
“MaxComputerSetSize”=dword:00000005
"ComputerApplicabilityRelevance"=“true”
“ShellCommandRelevance”="“cmd.exe /C explorer %22\\shareservername\UploadManagerData\bufferdir\sha1\” & last 2 of (id of current computer as string)& “\” &(id of current computer as string)&"%22""

Ben

1 Like