Well, let's try the scenario about how to set up a remote respository step by step.
1. Set up a http server and expose the repository: assume you have a server(ip address:184.108.40.206) running http service which can be accessed via http:\\220.127.116.11, and the plugins repository is on the server under /tmp/plugins directory. Then update <HTTPServer_HOME>/conf/http.conf by adding the following blocks after you stopped httpd daemon:
Options Indexes FollowSymLinks
Order allow, deny
Allow from all
Save and exit. Restart httpd daemon.
2. Copy geronimo-plugins.xml and relevant plugins into /tmp/plugins(You may try Geronimo sample plugins for this test).
3. From another server running Geronimo, go to admin console and add a remote repository named "http:\\18.104.22.168\plugins". Then click Show plugins in the repository you will see all the plugins ready for download.
The real challenge would be how you manage numbers of plugins and make sure each time users get the most updated ones, how to automate the whole update process from server side. Export applications from Admin console mannually works but for a great number of plugins, I'd pefer car-maven-plugin just as David Jencks mentioned.
Hope this could answer your questions. Anything else, please let us know.
I think there are two ways to do this:
On Mar 9, 2009, at 7:34 PM, James D Carroll wrote:
I really hate hijack the OP, but in truth none of the scenarios you
mentioned are what I'd like to be able to do:
My group creates products that other areas of the company may or may not
find useful. Vacation tracker, time sheets, workflow, whatever. What
I'm trying to make the case for is that instead of those groups running
on our servers (and us getting the bill), we give them a copy of
Geronimo and show them how to point to and install only those
applications/plugins that they want from the Admin Console. Creating a
custom server for them to start would certainly be possible and easy
enough to do from what I can see, but at the end of the day, we want to
basically say "Here's your container, here's the repository of what we
make, grab what you want".
As for Maven, all I can say is that every time I've tried to use it (in
Eclipse) I've just gotten very frustrated. I'm sure its much more my
problem than Maven's and it looks like it has TONS to offer. I just
don't have the patience to get it right.
1. non-maven (relies on running scripts by hand, editing files by hand, difficult to automate)
Set up a geronimo instance somewhere to use as your geronimo plugin repository. Deploy your apps into it, and either copy a suitable geronimo-plugin.xml into the appropriate place in the unpacked plugin in the geronimo repository or edit it using the admin console. (I haven't checked the admin console geronimo-plugin.xml editor recently to see how functional it is)
2. maven (more automated, pretty much everything important is in scm)
Build your apps into plugins using maven with the car-maven-plugin. The geronimo-plugin.xml will be constructed for you from your pom.xmls. At this point you can either install your plugins into a geronimo instance somewhere acting as your geronimo plugin repository or use maven to deploy into nexus.
If you deploy into geronimo, geronimo will generate a plugin catalog for you. If you use nexus, you'll have to generate one yourself and make it available somewhere. (I guess you can deploy it as an artifact in nexus?? I haven't tried this) The car-maven-plugin will update a local plugin catalog for you automatically and there's also a goal to scan your local repo and construct a catalog.
I've been using maven for years and can't quite imagine life without it, despite all the annoyances. I've just recently tried using it in eclipse, using m2eclipse and I'm not sure how much added value that brings. Help with editing poms is nice but I haven't found much use for eclipse running maven for me.
On Mon, 2009-03-09 at 11:19 -0700, David Jencks wrote:
Could you outline your goal a little more from a higher level viewpoint?
If you are trying to produce a consistent reproducible server image
with known contents through your build system I recommend assembling a
custom server using maven.
If you are trying to install plugins to an existing server using
scripts I recommend gshell.
If you are building plugins using maven (highly recommended) I
recommend sonatype nexus as a remote plugin repository. You can
easily set up a company-wide nexus instance and arrange for maven to
deploy your plugins into it.
IIRC in trunk the geronimo-maven-plugin can also be used to install
plugins into a running geronimo server. I don't recall if this made
it into the 2.1.x series.
On Mar 9, 2009, at 10:50 AM, RickI wrote:
You can also use tomcat/jetty that comes with geronimo to expose
What I try to do is to install plugin from remote repo without web
I try to do it from ant by calling deploy command line tool,
or from java code by calling gbean.
RunHua Chi wrote:
Alright, to accomplish what you expected, it's more likely about
up a http server and expose the file via http url.
Here is the topic for your information.
http://httpd.apache.org/docs/2.2/sections.html.(Assume you are using
And farming,load balancing and clustering topics using Geronimo,
On Sun, Mar 8, 2009 at 11:35 AM, James D Carroll <
The example showed 2 'remote' repositories (for apache) as does my
install, so that's why I was thinking that it was possible.
And the scenario you gave of a company wide repository is
I was asking. I work at a very large/ global company and my group
creates web based apps, but in PHP running on Apache. I'm trying
the case that we should move to Java/Geronimo so that we can
code and post it to the repository. Then the other areas could
get it whenever they wanted; perhaps to a test instance first, then
their prod server could pick it up from there when it was approved.
I haven't tried it either; Networking is my kryptonite and gettin it
runnin in VirtualBox is gonna kill me. :) I wanna workthrough/
understand farming/load balancing/clustering too.
On Sun, 2009-03-08 at 08:44 +0800, chi runhua wrote:
James, the page you mentioned is about how to build a local pluginhttp://cwiki.apache.org/GMOxDOC22/converting-applications-into-plugins-using-the-administrative-console.html
repository and import plugins from it. I guess it could be
the remote repository as well, as long as you have a
geronimo-plugins.xml and all plugins ready for import.
For example, you have a remote repository with url http:\
\www.yourcompany.com\plugins, and you've already placed a
geronimo-plugins.xml file in. Then add your url to your repository
list from geronimo admin console and plugins will be listed for
I didn't try the scenario yet, but I think it's possible.
Anything incorrect or misleading, please someone, just hop in.
On Sun, Mar 8, 2009 at 5:42 AM, James D Carroll
I'm confused. Isn't this page saying that it is possible:
Namely the ability to have an instance of Geronimo point at
at least some remote reposotory) and install new
Maybe that wasn't the OPs question, but I was hoping you
that for me.
On Fri, 2009-03-06 at 13:31 -0800, David Jencks wrote:
On Mar 6, 2009, at 12:41 PM, RickI wrote:remote
Is there any gbean that can be use to install plugin from
The PluginInstallerGBean is used to do this from the console
View this message in context:
atSent from the Apache Geronimo - Users mailing list archive
View this message in context: http://www.nabble.com/Gbean-to-install-plugin-from-remote-repository--tp22380105s134p22413720.html
Sent from the Apache Geronimo - Users mailing list archive at