What is the BPM Object Catalog?

The Project Catalog enables you to catalog the components and organize and group them into modules by some logical criteria. Therefore, a catalog contains the following elements:

Modules	Containers that create logically grouped components.
Components	Business Objects that are available to Process Methods.

Each project has its own catalog of components, so all the processes inside the project are checked and compiled using this catalog. Every time a process is published, the jar file of the BPM Object catalog is also published to the Directory Service. For further information on this topic, see Implementing Business Objects using BPM Objects.

General Features of the BPM Object Catalog

The BPM Object Catalog provides the following functionality:

Supports the ability to efficiently store and manage up to 100,000 components.
Supports unlimited nesting levels of components.
Achieves the above requirements with minimum memory utilization and maximum performance.
Provides simple wizards to simplify configuration and introspection of external resources Java, EJB, SQL, CORBA, etc.

The project catalog of components is stored in your local hard drive. The files are located in the componentCatalog directory that corresponds to the project.

The Project Catalog includes a set of default components. Go to the Help menu and clicking the Component Index option you get the list of all the standard components, the category or module to which it belongs to, and a brief description about it. If you double click on the component, a new tab in the main panel opens for that component. To learn about them please refer to Implementing Business Objects Using Library Components.

BPM Object Catalog Files

Project folders contain a folder called componentCatalog. This folder contains the structure of your catalog, which is a directory tree that corresponds to the catalog modules, and an xcdl (XML Component Definition Language) file for each defined module and component.

When the project is published and deployed, the configurations defined when cataloging the components are deployed in FDI, thus automatically creating a pair. At the same time, the BPM Object class is attached to the project. For the java components. For further information, see Publish & Deploy.