4.4. Services
Prev | Chapter 4. Configuration and Services | Next

## 4.4. Services

Services in Orchestra is all about pluggability. To allow that, each service has been thought in terms of an interface with different possible implementations. In the following lines you will find a description of main services supported in Orchestra.

The PVM includes a framework to allow the injection of services and objects that will be leveraged during the process definition and execution. Objects and services required in Orchestra are defined through an XML file. A dedicated parser and wiring framework in the PVM is in charge of creating those objects.

A default environment file (environment.xml) is provided in the installed package.

Currently, following objects are required for the execution environment :

- publisher

- invoker

- repository

- persistence

- timer

- journal and history

- querier

Example of implementation classes for these objects are embedded into the Orchestra jar and defined into the environment.xml file.

### 4.4.1. Publisher

The publisher service sets the way the services proposed by the BPEL processes will be published. The default implementation of this service uses the Axis Web Service Container.

Prev | Up | Next
4.3. Services Container | Home | 4.4.2. Invoker