Help me EJB deployer, you're my only hope...

Question

This request goes to anyone who has administered remote deployment of EJBs to JServer on any scale and has an opinion about it. I'm only looking for a 30,000 foot level response.
My question is, is it possible to deploy the EJBs to a single Oracle Server, and then Replicate them to other servers, or do EJBs have to be deployed to each server directly?
If not, is there a method for automating the deployment of EJBs to multiple Oracle servers other than replication?
I have a management meeting comming up to present recommendations on whether we want to deploy EJBs to approx 250 remote servers over a 56K fixed line connection, or have a central server for deployment and have the clients at those 250 remote sites pointed to the central repository. The answer is obvious to me, go with the central server. But I haven't had any experience adminstering EJB deployment so I need to have some idea of how estimate the cost in terms of work hours, maintenance and $ to administer the remote deployment.

Answer 1

Some comments/ideas:
How long was the server running after this screenshot?  I ask because store.exe is only got a 1GB of RAM which is really low - it should grab most of the RAM within a few hours.
The server was up for about 12 hours.  I believe an adjustment was made before to limit the Exchange memory usage.
Strange that SearchIndexer (wsearch service) is so high although that may be a startup condition.
The LT* processes seem to be a 3rd party monitoring tool - no idea why it would ever need that much CPU though (I thought you disabled this?).
We had, but we cannot go forever without monitoring our client's server.  It has been pulled off in the past and results on performance are pretty much the same.
The taskmgr process run by amnet_admin has used a lot of total CPU Time.  What is it? (can't see the command line).
That's the user I was logged in as when I took the screenshot.  Even the task manager seems to eat up the CPU.
The sqlserver process right above it is also busy - may want to look at the command line and figure out which SQL database that is (SBS has 3 - WSUS, Sharepoint, and SBS monitoring)
I believe that's the SharePoint database.  They don't currently use their site.  Would you recommend a removal and reinstallation?  I would not completely remove as I know SBS doesn't like you removing parts of the complete package.
Strange that vds.exe is 10% - that is the interface to the disk management interface IIRC.  Perhaps your monitoring service has gone awry here - definitely lose it.
I'll see about pulling it off and I'll see if there are any improvements.
-- Al