Project Component Overview

This topic briefly outlines the various components of a Repository-based Project.

Project Components

In a Repository-based Project, you specify the business logic for the specific implementation by defining the required Project components. For each of these components you specify logical properties, which are independent from the physical implementation. Projects are where you add and name message destinations, by dragging and dropping topics and queue icons onto the Connectivity Map canvas. See Connectivity Maps for additional information.

On links between message destinations and their subscribers and publishers, there is a JMS client properties icon. By double-clicking the JMS client properties icon in the Connectivity Map, you can configure the connection for such items as persistent or non-persistent delivery mode, XA, and concurrent processing.

After having added the components for message destinations, you create the Object Type Definitions (OTDs) and Collaboration Definitions. After defining the Collaboration Definitions, you then create the relationships between the components by associating Collaboration Definitions with services. This defines a service as a Collaboration, and binds the Collaboration to its Collaboration Definition.

External Applications

Generally speaking, external applications are the beginning and end points of the Project data path.

See:

• External Applications

• Web Service Applications

Services

Services include Business Processes and Collaborations, which are the logical transformations to be performed on the data.

See:

• Business Processes

• Collaborations

Message Destinations

Message destinations (topics or queues) are internal storage and routing nodes within the Project.

See:

• Message Destinations

Connectors

Connectors provide links between Project components where JMS Clients are not appropriate, generally aside from the main data paths. They are used primarily when mapping Business Processes.

See:

• Web Connectors

• WLM Connectors

Definitions

There are several Project components that are incorporated into other components as definitions. As such, they are not independently mappable and do not appear in the Connectivity Map Editor.

See:

• Collaboration Definitions

• Object Type Definitions

• Web Service Definitions

• XML Schema Definitions

• Constants and Variables

Mapping Entities

Some additional Project components do not themselves appear in the data path, but rather affect those data path components in a global manner. Since they provide mapping information, they are not mappable in themselves, and do not appear in the Connectivity Map Editor.

See:

• Connectivity Maps

• Deployment Profiles