| Attribute | Description | Type | Required? |
| expanded |
If set to true, this application module is generated in a directory, instead of a
.war archive file.
|
boolean | No Defaults to false |
| secured |
If set to true, this application module declares a security constraint so that only the
specified j2ee role can access the application.
Use this option if you want to leverage the authentication mechanism of your
container (e.g. WebLogic) and Single-Sign-On configurations.
See also attributes rolename and webresourcename.
|
boolean |
No Defaults to the value of secured defined in the enclosing <buildear> task.
|
| rolename | Name of j2ee role to declare when this application module is secured. | String |
No Defaults to the value of rolename defined in the enclosing <buildear> task.
|
| webresourcename |
Descriptive name for the web resources of this module. Used in
<web-resource-name> tag in web.xml deployment descriptor.
|
String |
No Defaults to the value of webresourcename defined in the enclosing <buildear> task.
|
| federated |
Set this option to true if you want to generate a BPM application that connects to
multiple BPM Directories. If true, you must also specify attribute
lookupnamefilemapping.
|
boolean | No |
| uri | URI for this web application module. | String | No |
| lookupnamefilemapping |
Path to properties file defining the list of BPM Directories to connect to.
Use only when building applications for a "federated" (multiple directories) BPM environment.
Example contents of this file: /OraBPMEnterpriseHome/conf/directory1.xml.id=Production1 /OraBPMEnterpriseHome/conf/directory1.xml.lookupname=BPM_Dir1 /OraBPMEnterpriseHome/conf/directory1.xml.priority=0 /OraBPMEnterpriseHome/conf/directory1.xml.authenticate=true /OraBPMEnterpriseHome/conf/directory2.xml.id=Production2 /OraBPMEnterpriseHome/conf/directory2.xml.lookupname=BPM_Dir2 /OraBPMEnterpriseHome/conf/directory2.xml.priority=1 /OraBPMEnterpriseHome/conf/directory2.xml.authenticate=true |
File |
Yes Only if federated is set to true.
|
web.xml deployment descriptors.
You can define <loginconfig> individually for each application module. When this element is specified as a direct child of <buildear>, it becomes the default for the nested application modules.
| Attribute | Description | Type | Required |
When buildling a secured application, the security role must be mapped to a Principal in the application server.
You can define <principals> individually for each application module. When this element is specified as a direct child of <buildear>, it becomes the default for the nested application modules.
| Attribute | Description | Type | Required |