Release Infrastructure/BOSS Participant

Revision as of 10:11, 12 August 2010 (view source) Ahma (Talk | contribs) m ← Older edit		Revision as of 10:19, 12 August 2010 (view source) Ahma (Talk | contribs) m (→Participant Coding Guidelines) Newer edit →
Line 16:		Line 16:
	=== Participant Coding Guidelines ===		=== Participant Coding Guidelines ===
		+
		+	BOSS participant is written in Python language (other bindings will be available later).
		+
		+	==== Import ====
		+
		+	from  RuoteAMQP.workitem import Workitem
		+	from  RuoteAMQP.participant import Participant
	=== Participant Example Code ===		=== Participant Example Code ===

---

Revision as of 10:19, 12 August 2010

Contents 1 BOSS Participant 1.1 What is BOSS Participant 1.2 Participant Coding Guidelines 1.2.1 Import 1.3 Participant Example Code

BOSS Participant

BOSS is a workflow orchestrator, a system that can be configured to automate your workflow requirements; it interacts with the OBS and with people and systems around it to apply your workflow steps. For more BOSS related general information, see Infrastructure/BOSS.

What is BOSS Participant

BOSS Participant the actual actor in BOSS architecture. Participant wraps other systems and services related to software development, quality assurance and integration, allowing BOSS to interact with different parties in automated way.

BOSS Participant action explained in three simple steps:

• Receive a workitem from BOSS server
• Process it, interacting with underlying (read: wrapped) system or service
• Return the filled worksheet back to BOSS server

Participant Coding Guidelines

BOSS participant is written in Python language (other bindings will be available later).

Import

 from  RuoteAMQP.workitem import Workitem
 from  RuoteAMQP.participant import Participant

Participant Example Code