Administer > Deploy > Overview: WCBD tool
Configure and run the build process
Overview
- Extract source code with user-provided Ant script.
- Consolidate and compile Java source code, creating a global *.jar for compiling each module individually.
This helps resolve classpath circular dependencies during the compilation phase using javac.
- For each connector module, compile and create an expanded *.rar file.
- For each EJB module, compile, deploy, and create a *.jar file.
- For each Java utility module, compile and create a *.jar file.
- For each Web module, compile and create an expanded *.war.
- If set to run, create a server deployment package by consolidating assets from source, archived modules and WCBD.
- If set to run, create a toolkit deployment package by consolidating assets from source, archived modules and WCBD.
Deployment targets are categorized using identifiers such as prod, test, dev.
Dataload assets are organized into common and target-specific directories in the DataLoad project. The deployment target value provided during launch is matched to target-specific directories. Data in both common and target-specific directories are loaded during deployment.
Uncompressed EAR assets, such as...
- EAR properties
- EAR XML files
- files in Web modules
...can use a specific file naming convention to identify the target environment to which the files are deployed. A file of name...
name.extension
...specific to a target environment target-env can be renamed to...
name.targetable.target-env.extension
...and checked into the repository.
Consider the scenario where the struts configuration for the Stores module is different between the dev and prod environments. For example, dev may have configuration settings that are not ready to be deployed to prod. To ensure the correct version of the file is deployed to each environment, the files can be renamed and checked into the repository...
- workspace/Stores/WebContent/WEB-INF/struts-config-ext.targetable.dev.xml
- workspace/Stores/WebContent/WEB-INF/struts-config-ext.targetable.prod.xml
During the deployment process, a deployment target value is provided when the deployment process is executed. If this value is dev the struts-config-ext.targetable.dev.xml file will be renamed to struts-config-ext.xml and deployed to the system.
This feature is useful for...
- files that differ between target environments, such as wc-server.xml
- files that contain target-specific paths, URLs and port numbers
It also provides developers access to files for all target environments in the development environment.
Configure and run the build process