Service

Description

A Service is the provisioning of one or more functions (Operations) within a System environment. It refers to a group of software components that perform a specific business logic.

VulCon / GreenVulcano^® ESB Configuration

A GreenVulcano^® ESB's service is identified by a unique name (id-service), belongs to a group and has an activation state and a number of clients enabled at its invocation (section Client).

You can configure the conditions applied to the routing of Service's flows (Conditions section).

The definitions used here are valid for all flows associated with service and overwrite any global definitions.

Service configuration

The Service element has the attributes:

• id-service: The unique name of the service. Corresponds to the value contained in the 'service' field of the data buffer (GVBuffer).
• group-name: Service group membership. Groups are defined in the Group section.
• service-activation: Activation status of service. The status can be:
  - on: service is active.
  - paused: service is inactive, the asynchronous client's requests are taken in charge by GreenVulcano^® ESB. They will be served when the service return on state 'on'.
  - off: service is inactive and no request are taken in charge by GreenVulcano^® ESB.
  The current version doesn't implement the state 'paused'.
  The attribute's default value is: on.
• creation-date: Service creation date. The information in this field is purely descriptive and has no impact on the functionality of GreenVulcano^® ESB.
  This information will be used for the production of reports on configuration.
• brief-description: Service description. This information will be used for the production of reports on configuration.

and the subelements:

• Description,
• Operation,
• BpelOperation,
• AliasList,
• Conditions.

How to

You can insert a new Service from the Core view right clicking the Services element, Insert after (or Insert before), Service. It is also possible to create a new Service using the Wizard.

The respective part of the GVCore.xml configuration file becomes:

<Service group-name="GVTEST" id-service="Test" service-activation="on" statistics="off">
      <Operation name="RequestReply" operation-activation="on" out-check-type="sys-svc-id" type="operation">
          <Participant id-channel="TEST_CHANNEL_FILE" id-system="GVESB"/>
          <Flow first-node="call_Test" point-x="20" point-y="150">
               ---
          </Flow>
      </Operation>
</Service>