The Project Catalog

Any non-trivial BPM project will usually need to communicate with outside resources, store complex data about each instance, or interact with the user through a Web-based interface. This is done by using standard or user-defined BPM Objects.

BPM Objects are organized by module. Each module can contain BPM Objects, other modules, or both.

User-Defined Modules

You can add your own modules to the project catalog. You can also add modules within modules, organizing them in the manner of a directory structure. Within a module, you can create the following components:

	Component	Description
	Module	Another module nested within the existing module.
	BPM Object	A user-defined component that contains attributes, methods, and presentations.
	BAM Dashboard	A Business Activity Monitor presentation
	Enumeration	A data type with a fixed set of possible values.
	Business Exception	An exception triggered by a foreseeable business condition.
	PUnit Suite	Unit test suite for processes.
	CUnit Suite	Unit test suite for individual BPM Objects.

You can also catalogue external components into your module. External components are components which contain the information that Studio needs in order to communicate with the software application, service, API, database, or other sofware resource your project needs to exchange information with.

A catalogued external component will act as the "glue" between studio and a given external resource. It provides an interface to that resource that can be used from PBL code. The following external component types are available:

• .NET Component
• AquaLogic Service Bus
• BPM Object
• COM
• CORBA Service
• EJB
• Enumeration
• JMX
• JNDI
• JPD
• Java
• SAP
• SQL
• SQL Query
• Web Service
• XML Schema

• BPM Objects
  
• BPM Object Catalog
  
• External Components