Externalizing the Derby Database to a DB2 Library will allow you to share these from any/all machines if you have the Clustering License. If you are looking at running a large amount of Monitors, you will find that clustering will be a better solution for you. That way they would all be run under the same Database, and modifying a monitor from any server affects all servers. And execution time would be better when spread across multiple servers.
Bottomline is that you wouldn't have to transfer them to each box.
** SIDENOTE **
The Monitors do not have an Export/Import/Promote feature attached to them. So, in general terms you would have to re-create the Monitor on the Target box by hand. This is due to the database links necessary to create the Monitor for executing, and attaching it to the desired Project with permissions to perform.