Projects Assets and Project Organization

A project is a container for all the assets that may be required when deploying an application to BPM. Projects help to facilitate the sharing and organization of resources. Before modeling your business process or defining your organization model, you must create a project to contain your assets.

A project can contain the following assets:

• Business Assets. There are the following categories of project-related business assets in TIBCO Business Studio:
  • Quality process. Business cases, project plans, and so on.
  • Ad-hoc assets. Supporting documents, spreadsheets, and so on that are not part of the quality process.
• Processes. A process models the business process.
• Forms. You can define forms to collect user input in a user task within a business process.
• Business Object Model. A business object model is a set of business terms and relationships specific to your corporate environment (for example, in a financial environment, broker, counterparty, and so on).
• Emulations. You can add emulation files to emulate a process and add test data at certain activities, thus enabling you to check the data flow at various activities in a process.
• Organization models. An organization model defines the organizational structure of your enterprise and the relationships between the different components (for example, organization units and positions) within your organization.
• Workforce management. Workforce management stores your library of tasks. Having a library of tasks enables you to reuse tasks in different processes.
• Service descriptors. Service assets include the WDSL files for any web services that you import into your project.
• TIBCO SOA platform. If you want to deploy an application to the TIBCO SOA Platform, you must create special folders to contain the SOA assets. Refer to the appropriate BPM Composite Development Guide for more information about developing applications for use with the TIBCO SOA platform.

When creating a project for use with BPM, you must do the following:

• Decide what assets you want and how they should be distributed across projects. See Distribution of Assets Across Multiple Projects.
• Create or obtain a project. See Creating or Obtaining a Project for BPM.
• Create and develop the assets that the project must contain.
• Deploy the project to BPM for use at runtime. See Deployment of a Project, and refer to TIBCO ActiveMatrix BPM Deployment Guide.
  Note: When creating projects and deciding what to put into a project remember that one project is the deployment package and you cannot deploy a subset of it. If you have a main process and dependent sub-processes (which are not used from other main processes as well) you can put them into the same project, but it is recommended that you put them into different xpdls so users can work on it in parallel. If you have processes which you want to deploy separately, you need to have them in different projects.