Search

Home

Home

GRAVITY Process Invocation

GRAVITY Process Invocation

Supported Process Trigger Types

The system includes the following built-in trigger types and start modes:

  • Manual – the process is launched manually from the project configuration window.
  • From another GRAVITY application – a project can contain operators that invoke another application during processing.
  • Scheduler – starts a project based on a time-based scheduling mechanism.
  • Database – starts a project in response to an event occurring in a database.
  • File – starts a project when a new file appears in a specified directory.
  • WebService – starts a project via a REST API call.
  • RabbitMQ – starts a project upon receiving a message from the RabbitMQ server.
  • Event – starts a project when a specific event occurs in the GRAVITY environment.
  • Socket – starts a TCP server on a defined port; when a client sends a message to the server, the project associated with the trigger is launched.
  • AS2 Server – runs an AS2 server that enables receiving and automatically processing EDI documents from defined business partners.

The configuration of automatic triggers is available in GRAVITY.exe under the TRIGGERS tab. Each trigger starts a single project unless that project uses another one — in such a case, the project is additionally invoked by another GRAVITY application.

icon
Before using automatic triggers, make sure to review the Automatic Invocation ServerAutomatic Invocation Server section.
icon
Triggers may be subject to execution queuing rules. These rules are described in the Managing GRAVITY Process QueuesManaging GRAVITY Process Queues section.
Manual InvocationAutomatic Invocation by Another GRAVITY ApplicationAutomatic Invocation via the Scheduling MechanismAutomatic Invocation via Database Notification MechanismAutomatic Trigger by Detecting a New File in a DirectoryAutomatic Invocation via REST APIAutomatic Invocation via RabbitMQ Message ReceptionAutomatic Invocation as a GRAVITY EventAutomatic invocation via a TCP serverAutomatic Invocation via the AS2 Server