Creating Abstract Applications

An abstract application is an application that is created not as an executable, but to be a parent providing configuration defaults for executable applications.

To simplify application configuration, an application can specify a parent application to provides default configuration settings needed to run the application. You should create your own abstract application and use it as the parent for a set of programs that share common configurations.

Tip: If you use this inheritance mechanism efficiently, you can configure new applications with only a few entries in a configuration file.

To specify an abstract application, set the Abstract attribute to TRUE.

Important: Abstract applications can only be defined in the application server configuration file, they cannot be defined in an external application configuration file.

Example for Web applications

<APPLICATION Id="defaultwa" Abstract="TRUE">
  <EXECUTION Using="cpn.wa.execution.local"/>
  <OUTPUT>
    <HTTP_HEADER Id="Cache-Control">no-cache</HTTP_HEADER>
    <HTTP_HEADER Id="Pragma">no-cache</HTTP_HEADER>
    <HTTP_HEADER Id="Expires">-1</HTTP_HEADER>
    <MAP Id="DUA_GDC" Allowed="TRUE">
      <TIMEOUT Using="cpn.wa.timeout"/>
      <PICTURE>
        <PATH>$(connector.uri)/pics</PATH>
      </PICTURE>
      <RENDERING Using="cpn.rendering.wa"/>
      <THEME Using="cpn.theme.default.gdc"/>
    </MAP>
  </OUTPUT>
</APPLICATION>

In this example, DUA_GDC is OutputMap, which indicates the Front End used to display the application. Note that all OutputMap are enabled as the attribute Allowed is set to TRUE.

Example for GDCAX applications

<MAP Id="DUA_GDC" Allowed="TRUE">
  <TIMEOUT Using="cpn.wa.timeout"/>
  <RENDERING Using="cpn.rendering.wa"/>
  <THEME Using="cpn.theme.default.gdc"/>
</MAP>