Types of Derived Artifacts

There are different types of derived artifacts. The derived artifacts that may be available depends on your implementation.

If you need to troubleshoot problems with the generation, you can use the table below to identify the files you should be looking at.

Visible Artifacts (Platform Independent Model) Deployment Artifacts (Platform Specific Model) Description/Purpose
.bom An entire project and its contents (BDS plugin) Business Data Services (BDS) used by both Work Manager and Process Manager to pass and store data.
<packagename>.bds Forms JavaScript project
.bom2Xsd\*.xsd (used for BDS Plugin and GeneratedServices/*.wsdl .xsds generated from boms for use in BDS Plugin and .wsdl generated for process.
.channels .bpm\wp\wpModel.xml Configuration files for work presentation (part of Work Manager).
.form .forms/(gi) /---/.form

.forms/(gwt) /--/.form

.forms/gwt/---/.json

.forms/.properties.xml

 Used to control the user interface to both business processes and pageflows including internationalization.
.om .bpm/*.de Directory Engine (part of Work Manager) configuration files.
project .bpm/*.daa

.bpm/*.composite

.bpm/*.requirements

 These are Application configuration files used by TIBCO Administrator to deploy to the components that make up Process and Work Manager and by the BPM runtime to instantiate and run those applications.
.wsdl .processOut/---/.wsdl

.processOut/pageflow/*.wsdl

 These contain definitions of both the services consumed and exposed.
.xpdl .processOut/process/.bpel

.processOut/pageflow/.bpel

 These are deployed to Process Manager and control the process (as distinct from work items and UI).
.xpdl .bpm/wt.xml <---- Task + Data

.bpm/wm.xml <----Task + Data + Participant

 These are deployed to Work Manager and define work items and their scheduling.