Cúram Application Build Structure

This section describes the directory structure created when a Cúram application is built. Cúram Application Build Structure presents the new directories that are created during the build process while Cúram Application Build Structure gives more details on the contents of each directory.

Figure 1. The Cúram Application Build Structure

SERVER_DIR
  + build
    + datamanager
    + ear
      + WAS
      + WLS
    + jar
    + sqlcheck
    + svr
      + cls
      + codetable
        + cls
        + gen
        + scp
        + sql
      + events
        + cls
        + gen
        + scp
      + gen
      + message
        + cls
        + gen
        + scp
      + webservices
      + workflow
      + wsc
      + wsc2
  + buildlogs

Table 1. Build Directory Structure
Name	Contents
build/datamanager	Contains intermediate files produced by the Data Manager and the resulting merge dmx files from the initial, demo and test directories. The Data Manager creates the intermediate files when translating the database independent files into a format which can be loaded onto the database. Five database dependent .sql files are produced as well as one database independent .xml file which is responsible for loading the Large OBjects (LOBs) onto the database.
build/ear/WAS	The .ear file produced for WebSphere Application Server.
build/ear/WLS	The .ear file produced for WebLogic.
build/jar	Jar files created by the command line project build.
build/sqlcheck	A database dependent sqlj file which contains a subset of the dynamic SQL statements from the model and the inserts from the Data Manager collated together.
build/svr	All build artefacts for the server side.
build/svr/cls	All of the compiled class files for the application.
build/svr/gen	Generated server side sources.
build/svr/gen/ddl	Database independent definition scripts that establish the structure of a Cúram server application's database tables are generated into this directory. Some intermediate files (including a representation that is used to build to database dependent sqlj file) are also generated into this directory.
build/svr/gen/<ProjectPackage>	Root of the generated server source code hierarchy.
build/svr/gen/int	Intermediate files produced during the build.
build/svr/codetable/cls	The compiled codetable files.
build/svr/codetable/gen	The generated codetable file artefacts.
build/svr/codetable/scp	A copy of the results of merging the individual codetable files according to the component order (SERVER_COMPONENT_ORDER).
build/svr/events/cls	The compiled event class and event type files. These may be used as constants in the Cúram application.
build/svr/events/gen	The generated events file artefacts which include the .java files containing the event class and event type constants and .dmx files to be used to populate the event class and event type tables on the database.
build/svr/events/scp	A copy of the results of merging the individual event files according to the component order (SERVER_COMPONENT_ORDER).
build/svr/message/cls	The compiled message files.
build/svr/message/gen	The generated message file artefacts.
build/svr/message/scp	A copy of the results of merging the individual message files according to the component order (SERVER_COMPONENT_ORDER).
build/svr/webservices	Compiled class files for the web service support elements of the application.
build/svr/workflow	A copy of the results of determining the individual workflow process definition files to be loaded onto the database according to the component order (SERVER_COMPONENT_ORDER) .
build/svr/wsc2	Compiled class files for the Apache Axis2 -generated client stubs for each registered outbound web service connector.
<app.xml>	Extracted UML model contents, named as per model.
buildlogs	A log file is created each time a build is performed and is stored here. This can be used to investigate any problems with the build process.