Multiple EAR files

Building an Application EAR also takes an optional file to allow for splitting the client components into different WAR and EAR files and also to allow for some more control of some of the EAR configuration and included modules. This file is named deployment_packaging.xml and should be placed in your SERVER_DIR/project/config directory.

The format of the deployment_packaging.xml file is as follows:

<deployment-config>
  <ear name="Curam"
      requireServer="true">
    <components>custom,sample,SamplePublicAccess,core</components>
    <context-root>/Curam</context-root>
  </ear>
  <ear name="CuramExternal">
    <components>SamplePublicAccessExternal</components>
    <context-root>/CuramExternal</context-root>
    <custom-web-xml>${client.dir}/custom_web_xml</custom-web-xml>
  </ear>
</deployment-config>

Each file can have multiple ear elements and results in an EAR file being produced in the SERVER_DIR/build/ear/WAS directory. The options for each element are:

• name

  This option controls the name of the EAR created from the process.

• requireServer

  This optional attribute controls whether the server module is included in the EAR file. Valid entries are true or false. The default value is false. If deploying multiple EAR files to one application server, this attribute must be set to true for only one EAR file as only one IBM Cúram Social Program Management server module should be deployed per cluster. If requireServer is set to true for multiple EAR files, then the other EAR files must be deployed in another cluster to avoid conflicts.

• components

  This option controls which of the client components get placed into the EAR file. It also controls the component order for the rebuild of the client that will need to take place. Usually the core directory doesn't form part of the component order but on this occasion it is important to add this to qualify whether it should be included in a particular WAR file. Entries here should follow the typical order of components defined in the Cúram Server Developer's Guide and should be comma separated.

• context-root

  This option forms the Context Root of the WAR module in the application.xml deployment descriptor. Entries here should begin with a forward-slash.

• custom-web-xml

  This optional element controls whether a custom web.xml file should overwrite the standard version in the WAR file. Entries here should be an Apache Ant path to the directory containing the web.xml file.

  It is possible to use references to environment variables as part of this path. For example, ${client.dir} can be used to point to the web client directory and ${SERVER_DIR} can be used to point to the server directory.

For each web client (i.e., WAR file) a separate web client component is required to contain its customizations. In the case of multiple web clients, your CLIENT_COMPONENT_ORDER environment variable will include all your custom components; but, separate <ear> elements will be required, one for each custom web component (and other components as needed).

As with the standard target, a fully built IBM Cúram Social Program Management application must be available. For details on how to build an application, please refer to the Cúram Server Developer's Guide.