Source Control

TIBCO does not provide its own source control management product, preferring to integrate with the enterprise's choice for source control management.

One problem that occurs when dealing with processes across their normal life cycle (from creation, testing, rollout to maintenance), is how to know that a given process created by the analyst, elaborated by the solution engineer, and signed off by the process owner, is exactly the one that is in use in a specific environment (for example, a development, user-acceptance or production environment).

Particularly in large and complex projects where data is shared or modified by several people, a source control system becomes necessary. Most enterprises have one or more products for Source Configuration Management (SCM). This may be a commercial product such as Perforce, Rational's Clearcase or an open source solution such as:

The Eclipse feature for integrating with such an SCM product is known as the Team Synchronization. Since Eclipse provides CVS by default, the following section describes how to use Subversion; you should contact your SCM vendor for commercial plug-ins.

Note: SCM is one part of Application Lifecycle Management (ALM) dealing only with the preservation of revisions of software at different times, not the editorial and approval processes that drive those different revisions.

Standards Support

TIBCO Business Studio supports the industry standards Business Process Model and Notation (BPMN) and XML Process Definition Language (XPDL).

Business Process Model and Notation (BPMN)

BPMN is a graphical notation, developed by the Business Process Management Initiative (BPMI) and now part of the Object Management Group (OMG), for representing the steps and flow of business procedures.

The TIBCO Business Studio Process Editor is based on the BPMN 2.0 specification.

For more information, see http://www.bpmn.org.

XML Process Definition Language (XPDL)

XPDL is used to represent the underlying structure of a business process to TIBCO Business Studio.

Packages are stored in XPDL 2.1 format. Normally, you do not use XPDL directly, but indirectly by creating a process package then editing a process within it using the Process Editor.

For more information, see http://www.bpmn.org.