Get a shop manual for your car. The same one the dealer uses to repair your car. You need this to be able to track what components your car has.
If you decode the commands I believe there is information there that ID's the module it is coming from and to. I have a shop manual for my GM truck and I should be able to use this along with the CAN data to decode most commands and duplicate them. The manual gives me the names of the modules, where they are, what they are responsible for, and their CAN id addresses so with this information I should be able to communicate with them.
If you look at where the commands are coming from and where they are going to and the order they happen you will likely be able to figure out what is going on. Since the CAN bus has been somewhat standardized since 1996 with ODBII you should be able to find information on the structure of a command and it should become simple. There are generic commands that are spelled out in the protocol but there is plenty of room for proprietary commands which all manufacturers use but they still use the same structure so you should be able to decode them relatively easily.
This is NOT a simple mater of just recording the information and playing it back as you have noticed. You will likely have a command response sequence you need to follow.