<fuego.j2ee : buildconsole>

Description

This task builds the Process Administrator (formerly, Web Console) Web Application as a .war file (or its expanded version).

Example:

  <target name="build-console" description="Build console war">
      <fuego.j2ee:buildconsole fuegobasedir="${fuego.basedir}"
           destfile="${destination.file}"
           workdir="${fuego.workdir}"
           directoryfile="${fuego.directory.file}"
           engineid="${engine.name}"
           uri="/fuego/console"/>
  </target>

Parameters

Attribute Description Type Required?
secured If set to true, this application 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 false.
destdir Destination directory where to build the web application. Set this attribute if you want to build the application in expanded form, and not in a .war archive file. File Yes Either destdir or destfile must be specified.
uri URI for this web application module. String No
directorypreset Specify a "preset" for authentication to the BPM directory. String No Defaults to the "engine" preset.
rolename Name of j2ee role to declare when this application module is secured. String No Defaults to ALBPM_Role. Only used when secured is set to true.
workdir A writable directory where temporary files are generated. All the content of the workDir will be delete before executing the task File Yes The directory must exist and it must be writable.
directoryfile Path to the directory.xml configuration file, used to connect to the BPM directory. File No
destfile Destination file path to the web application archive (.war). File Yes Either destdir or destfile must be specified.
verbose Verbose output. boolean No Default is false
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
engineid The ID of the BPM Engine this application connects to. String Yes Only if the application connects to a J2EE BPM Engine.
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.
fuegobasedir Path to Oracle BPM Enterprise installation directory. File No Defaults to value of fuego.basedir property of your Ant script.
templateset Sub-directory name from which descriptor template files are loaded. For example: <ORABPM_HOME>/weblogic/templates/engine/default/*. String No Defaults to "default".
loaderref Reference to BPM classloader. Used internally. Reference No
webresourcename Descriptive name for the web resources of this module. Used in <web-resource-name> tag in web.xml deployment descriptor. String No Required if secured is set to true.

Parameters accepted as nested elements

<loginconfig> ...

Use this element to specify the login configuration for a web application module. Used for <login-config> tag in 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

<principals> ...

Use this element to specify one or more Principals to map the security role on WebLogic. If you don't specify <principals>, you must deploy the application using the Advanced security model and do the Role-to-Principals mapping using the Weblogic Administration console.

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

© 2008 Oracle Corporation