Big Fix is an IBM Product that specializes in keeping track of clients downstream, that need patches/updates and does it as and when required.
In other words, Big Fix maintains a list of clients ( or as I like to call them 'servers downstream' ) and tracks them periodically and when a user wants to deploy a new patch or an install , then Big Fix looks at a few things like Relevance, and performs some actions and sees to it that the remote servers get the patches.
Several attractive features of the Big Fix makes this operation smooth and simple and requires no manual intervention. The One I found interesting is the "Relevance" feature, which is a rule (or a set of rules ) that tells things like what type of a server, what type of an OS and what range of IP address and things like that . Once these conditions in the rule are met - then Big Fix Server issues a UDP request to the clients ( or servers downstream) that the patch/update is required.
The client(s) then initiate a request and pulls down the patch or an update, and completes the operation.
Some snapshots can be seen in next blog.
In other words, Big Fix maintains a list of clients ( or as I like to call them 'servers downstream' ) and tracks them periodically and when a user wants to deploy a new patch or an install , then Big Fix looks at a few things like Relevance, and performs some actions and sees to it that the remote servers get the patches.
Several attractive features of the Big Fix makes this operation smooth and simple and requires no manual intervention. The One I found interesting is the "Relevance" feature, which is a rule (or a set of rules ) that tells things like what type of a server, what type of an OS and what range of IP address and things like that . Once these conditions in the rule are met - then Big Fix Server issues a UDP request to the clients ( or servers downstream) that the patch/update is required.
The client(s) then initiate a request and pulls down the patch or an update, and completes the operation.
Some snapshots can be seen in next blog.
No comments:
Post a Comment