Minimal Orbeon production deployment configuration?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Minimal Orbeon production deployment configuration?

Andrzej Jan Taramina-2

Are there any instructions on how to build/package a minimal Orbeon deployment
for production?  I looked but was not able to find anything along these lines.

We want to be able to create a minimal Orbeon WAR file that just includes the
XForms processing engine and nothing else.  That is, no XML Pipelines, no
PageFlow, no embedded eXist database, etc, with all unecessary jars and other
items stripped out.

This would be for a separate deployment (app and Orbeon wars would be separate).
Found the FAQ entry for how to do separate deployment and that seems to be
pretty straightforward.

We need a minimal XForms packaging to reduce the footprint, reduce resource
requirements and to control the size of the security exposure.

If someone could point me in the right direction to accomplish this, it would be
very much appreciated...

Thanks!


--
Andrzej Taramina
Coalese Corporation: Knowledge that Acts!
http://www.coalese.com


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Minimal Orbeon production deployment configuration?

Erik Bruchez
Administrator
Andrzej,

BTW XForms, pipeline engine and Page Flow are not separable at the  
moment: they are all in orbeon.jar.

For the rest, it is certainly possible to reduce the size, but we  
don't have instructions to do so. You can try an incremental approach  
and remove JARs until something breaks... Granted it is not an optimal  
way to go ahead.

-Erik

On Jul 17, 2008, at 9:00 AM, Andrzej Jan Taramina wrote:

>
> Are there any instructions on how to build/package a minimal Orbeon  
> deployment for production?  I looked but was not able to find  
> anything along these lines.
>
> We want to be able to create a minimal Orbeon WAR file that just  
> includes the XForms processing engine and nothing else.  That is, no  
> XML Pipelines, no PageFlow, no embedded eXist database, etc, with  
> all unecessary jars and other items stripped out.
>
> This would be for a separate deployment (app and Orbeon wars would  
> be separate). Found the FAQ entry for how to do separate deployment  
> and that seems to be pretty straightforward.
>
> We need a minimal XForms packaging to reduce the footprint, reduce  
> resource requirements and to control the size of the security  
> exposure.
>
> If someone could point me in the right direction to accomplish this,  
> it would be very much appreciated...
>
> Thanks!
>
>
> --
> Andrzej Taramina
> Coalese Corporation: Knowledge that Acts!
> http://www.coalese.com
>
> --
> You receive this message as a subscriber of the [hidden email]  
> mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws