Hi Geeks This week I started to implement the chance for the administrator to set up a farm of JBoss servers and then deploy services on all of these member of the farm. Later on it is possible to deploy also applications etc. on the farm.
Definition: FARM A farm is a set of computers running the same version (or at least compatible versions) JBoss but with their own Naming Service (NO clustering). Right now the user has to set up each member of the farm on its own by deploying the FarmMemberSerice (FMS) MBean. This member will try to connect to all given other members (by JNDI-Server name and Adaptor JNDI-name) which in turn reconnect back. This builds up the entire farm network. When a service gets deployed on the farm it will be deployed locally as well as on each other member of the farm. Right now the member which starts deploying pushes the file to all other members but will be maybe replaced later by a pull model to avoid unnecessary file transfers. Initial idea was to intercept the Auto Deployer and then hand over the requests locally to the Service Deployer but the problem is that not all service files should be deployed on the entire farm. The idea now is that the FMS is another deployer added to the autodeployer and listen for a special directory. All the deployed services are stored allowing a new member starting up to check if there are new version available on the farm. Hopefully I can add an ALPHA version by the end of today. Have fun xxxxxxxxxxxxxxxxx Andreas Schaefer Senior Consultant JBoss Group, LLC xxxxxxxxxxxxxxxxx _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
