Hi Curt,
I don't know if it will help you, but we deploy multiple web components
inside and orion instance using different .ear. But I guess that if they
all had to be inside the same .ear, things wouldn't be that different.
What we do is:
in file server.xml, we first define the applications and their origin
...
<!-- mandatory global application -->
<global-application
name="Global"
path="../Global.ear"
/>
<!-- extra applications -->
<application
name="Extra1"
path="../Extra1.ear"
/>
<application
name="Extra2"
path="../Extra2.ear"
/>
....
in file web-site.xml (what by default is default-web-site.xml), we
define the mappings to the applications:
...
<!-- The default web-app for this site, bound to the root -->
<default-web-app
application="Global"
name="Global"
/>
<web-app
application="Extra1"
name="Extra1"
root="/extra1"
load-on-startup="true"
/>
<web-app
application="Extra2"
name="Extra2"
root="/extra2"
load-on-startup="true"
/>
...
And that's pretty much all. Having different .ear for different modules,
allows us to update each module independently. And we have an orion
instance for every two-three modules, so they are even more independent
in case we have to stop an instance (if the DB goes down, for example).
Supposedly, if you want the different modules inside the .ear file, you
would just define the different web modules (.war files) and their
mappings inside the application.xml descriptor, and then define one
application in orion. Orion should then extract the information from the
descriptor and define the mappings apropriately, or at least that's what
I would expect. I haven't verified that, though.
Good luck,
D.
Curt Smith wrote:
>>> My 2 cents worth is this is the order of importance of documentation
>>> that is
>>> needed right now to do REAL professional deployments and developments
>>> with Orion/OC4J
>>>
>>>
>>> 1) Orion specific deployment settings explained
>>> these are not really explained anywhere right now.
>
> My configuration challeng that I haven't figured out is; how to support
> multiple
> web components.
>
> I'm prefering the expanded tree deployment where I'd have multiple
> web/WEB-INF/web.xml trees. All need to be in the same restricted
> single-signon scope. I.E.
>
> root/web1/WEB-INF/web.xml
> /web2/WEB-INF/web.xml
>
> ....
>
> The confusion between default-web-site.xml, orion-web.xml,
> application-name, name
> ... :-/
>
> Anybody have configuration to share of multiple .ear in one application
> or multiple
> web directories??
>
> Thanks and have a great TG holidays,
>
> curt
