JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Developing Oracle Java CAPS Projects     Java CAPS Documentation
search filter icon
search icon

Document Information

Developing Java CAPS Projects

Connecting to a Repository

To Connect to a Repository

Creating a Repository-Based Project

To Create a Top-level Repository-Based Project

Opening a Repository-Based Project

To Open a Top-level Repository-Based Project

Adding and Connecting Project Components

Project Nesting

Using the Connectivity Map Editor

Linking Services and Destinations

To Link Services and Destinations

Adding and Setting Up Schedulers

To Add a Scheduler to the Project

To Configure the Schedule

To Configure the Time Zone

Project Context Menu

Project Component Context Menu

Connectivity Map Editor Toolbar

Project Component Overview

Project Components

External Applications

Services

Message Destinations

Connectors

Definitions

Mapping Entities

Business Processes

Collaborations

Message Destinations

External Applications

Web Service Applications

Web Connectors

WLM Connectors

Collaboration Definitions

Object Type Definitions

Web Service Definitions

XML Schema Definitions

Constants and Variables

Connectivity Maps

Deployment Profiles

Index

Collaboration Definitions

Figure 16 Collaboration Definition Icon

image:Image of a Java Collaboration Definition icon.

Collaboration Definitions define how data should be processed and routed between Project components, how databases should be queried in response to requests, and how APIs to one or more applications should be invoked. The external data formats that characterize the input and output data structures in a Collaboration Definition are described by Object Type Definitions (OTDs).

A Collaboration will typically receive a message containing the external representation of a particular OTD. It will use the unmarshal method of an instance of that OTD to parse the data and make it accessible though the hierarchical data structure. Then it will perform some operation— for example, copying parts of the data to another OTD instance. Finally, it will invoke the marshal method on the other OTD instance to render the contents of its data structure as a single, serialized data stream for further transport.

At run time, an OTD instance is accessed directly from Java, using accessors resembling JavaBeans. Each of the nodes comprising the hierarchy of the data structure has a set of properties with get and set methods.

A Java-based Collaboration Definition provides a single operation that can be invoked from a Business Process. You can create multiple methods in a Java-based Collaboration Definition, but the additional methods can only be invoked from within the Collaboration Definition.