Input Agents

Input Agents are used in profiles to receive the input data.

There are basically two types of Input Agents in Lobster_data.

  • On the one hand, the event-driven ones, which are passively supplied by a data source at any time.

  • And on the other hand, the time-driven ones, which collect data from a data source at a time defined by the user.

In addition, a distinction can be made between Input Agents that place jobs in a Thread Queue and those that process jobs directly. For now, you can neglect this. If necessary, you will find a note for affected Input Agents.

For a more detailed description of the entire process and a deeper understanding, see section Profiles - Phase 1 of the introduction to Lobster_data.

Copy and Paste of Settings

images/download/attachments/44937161/input_agent_clipboard_EN-version-1-modificationdate-1576648438429-api-v2.png

(1) You can copy the settings of all Input Agents (besides type Manual Upload and Rule) and paste them into an Input Agent of the same type in another profile. You can save one instance of each Input Agent type to the clipboard.

Related Services

images/download/thumbnails/44937161/Service_Lizenz-version-1-modificationdate-1576648062884-api-v2.png


If you see an icon of this type (here at the example of an event-driven OFTP Input Agent), the corresponding service still has to be configured. This can either be done directly in the configuration file ./etc/factory.xml or on the Services site of the Admin Console. After that a restart of the Integration Server is necessary.

You can see which services are running on Lobster_data (the Integration Server) on sites Start and Services of the Admin Console.

You may also need an additional license for the service

You can see which services are licensed on Lobster_data (the Integration Server) in the console output or in file ./logs/wrapper.log if Lobster_data is running as a service.

images/download/attachments/44937161/Konsole_Services-version-1-modificationdate-1576648062879-api-v2.png