Package Structure for Customization Artifacts
Your customizations are built and deployed by the Code and Configuration Deployment (CCD) utility. You must organize your customization artifacts as per the package structure shown below for them to be processed by this utility.
The package structure prescribes a set of directories for specific categories of configuration and customization. The main categories supported currently are:
• BAC Package – Configurations exported using the BAC utility
• Schema changes – Configurations that define schema changes
• Other configuration artifacts - Load files, xconf, etc
• Code – Custom code artifacts
The following image displays two structures:
• Source package structure: The location and structure for organizing your customization artifacts (source view)
• Target package structure: The location and structure in which the CCD utility deploys your source artifacts (deployment view)
 |
The structure of the target location is provided here only to facilitate troubleshooting, if necessary. You must not modify files in the target location directly. The modifications in the target location are not retained. They are removed during deployment by the CCD utility.
|
This package structure isolates the custom code from the OOTB code so that customizations can be managed independently.
The default location for the customization package is /opt/ptc/customization.
Alternatively, you can specify a different location, using the property wt.customizationSource.dir.path=<path to source code> present in the <WT_HOME>/bin/customizationTools/customizationTools.properties file.
|
|
The CCD utility must have read, write, modify, and execute access to the location of the customization package.
|
After the installation of the CCD utility, the system copies the content in the loadFiles folder in the compile view to the loadFiles folder in the deployment view. Similarly, the system compiles the Java files in the src folder in the compile view and then adds them to jar which is copied to the lib folder in the deployment view.
Consider the compile view as the source view and the deployment view as the target view.
|
|
The deployment folder structure must be manually created.
|
The next example shows the mapping between the compile view and deployment view:
