For installation purpose, you can use the silent install, will do the job and documented
For cells data synchronisation you can do it by scripting and manage all cases (some are complex) or user ProactivePack DDA Replicator module
Thank you. I’m aware of the silent install option and that’s what we’re suing for the manual cell installs for our basic infrastructure build-out (enrichment and correlation sells, etc…). However we will be installing a number of cells above and beyond that (there will be far too many to install manually). I realize that installation using the silent install image can be automated. However, if there is a common custom configuration (classes, rules, actions, etc…), I believe it might be beneficial to do the configuration on one system to build the “gold standard cell configuration), tar it up and drop it in on any Linux system where we plan to install this “cloned” cell. I’ve heard that this is possible. I want to verify that and find out as much as I can about how to do it.
Thinking about this, it probably will work to just move the common classes, KB, and os-relevent actions over and untar them. I wonder though about the mcell.conf and mcell.dir files that you would probably want to be local to the given server. Also registering wtih ias, this can probably be scripted but I think your cell has to be unique, correct? Will these cells know about all other cells, or is is sufficient that they just know about the next one backwards or forward?
Doing a silent install to roll out all the cells might be best, and then stop all the cells, use the "gold standard cell configuration" to overwrite all the non-unique KB files, then start the cells might work. This should be able to be automated as well.
2 of 2 people found this helpful
Once cell is installed you have to separate:
-Cell files (in kb dir) and can easily copied from one box to other (may do a mccomp after and restart cell)
-Cell data (used by rules/policies). Data is located in mcdb with events
For data, not so easy beaucse data can change from rules or external source.
That said, once you've create a great KB you should only need to change data and make everything as dynamic as business need.
Thank you! I appreciate your response.