Accelerator is a generic name used to describe packaged functionality facilitating the creation of an Adapter. An Accelerator may consist of one or many building blocks. The building blocks may be Scripts, Adapterflows or Workflows.
If the name of a building block starts with _ and is not a Template or a Use sample, it is complete and only needs configuration.
There are two types of Accelerators:
- Basic accelerators
Provide technical functionality primarily for Managed File Transfer. Examples are File Accelerator, FTP Accelerator and Web services Accelerator.
- Advanced accelerators
Provide pre-packaged functionality for connection towards an ERP system or another business application. Examples are M3/Movex Accelerators, Dynamics AX Accelerator and B2B/EDI Accelerator.
The complete (loose) coupling between an ESB and an application, for example an ERP system, an FTP site, a file directory, a web shop etc.
An Adapter is created by assembling and configuring different building blocks, such as Scripts, Adapterflows and Workflows. In many cases, there is an Accelerator facilitating the creation of the Adapter.
A wizard-based description of a processing. Adapterflow is a special case of Workflow, where the possibility set conditions has been removed in order to facilitate the configuration.
An Adapterflow always starts with an entry point, but may then contain a number of different activities. Examples of such activities are "SaveToFile" and "MSMQWriter".
Adding an entity "inline" means that a definition entity is added/created directly from a configuration.
The most common approach is to start with the main Component definitions and Event types in the integration flow, test them out in the Run Component tool, and then move on to decide the runtime conditions by creating the Component configurations and Event configurations.
However, in some scenarios (for example when you are modifying an existing flow) it can be easier to add a new Event configuration and then add the executing Component inline.
A computer that is attached to an iCore system.
Meta data added to the information in a Node, Partner, or Setting.
Categories are used to organize entities in an iCore system.
Code Generator Definition (CGD)
Defines how to create code to facilitate mappings. The Code Generator Definition is run by the Code Generator Tool.
Code Generator Tool (CGT)
A tool used, for example, to create template Scripts and facilitate mapping.
A Component configuration describes how and where a Component definition is executed at runtime. Several Component configurations can use the same Component definition.
Event types and Component configurations are used in Event configurations to describe the process flow.
Component definitions describe various processings that are used either in a Component configuration or as a sub-part of another Component definition. For example, a Workflow definition might invoke a Script definition.
There are three types of Component definitions: Adapterflows, Scripts and Workflows.
All Component definitions require compilation.
A translation from one or two keys to one or two result values.
An identity of something that happens in the system, which may initiate a processing.
Events are "runtime links" between Jobs and are also part of the tracking of a process flow as defined by Event configurations and Component definitions.
A Server part that creates Events based on Timers.
The context in which a Component is executed. All tracking entities (Events, Log entries and Nodes) are created as a relation to a Job.
A Node is an information container for inbound or outbound information flowing through the system.
A package of exportable entities from iCore. The different packages provide different types of functionality, for example maintenance and error handling.
A comprehensive term for a group of Settings applying to a business partner.
A “best practice” showing which building blocks the described processing is to contain in order to get the best possible result.
A way to describe a flow (on a higher level). Each phase may contain one or many processings.
A system thread, used by the Event Dispatcher to execute Events. One machine may be able to run several processes, depending on its capacity (CPUs).
The execution of a Component.
A scenario is used to describe an end-to-end solution, for example the complete order flow from a Web shop to an ERP system. Also referred to as a use case.
A dialog-based description of a processing or mapping. iCore Scripts are created and compiled in the iCore Developer.
The iCore system runtime consists of one or more Servers. Each Server takes on one or several roles and each server role is specified by setting which vital Server parts and which Application pools (if any) it implements.
An "example" of a Script, Adapterflow or Workflow, that may need more or less modification before it can be executed. A template always has to be "Saved as..." before it can be used.
A use sample is a simple example that shows how to use certain functionality. A Use sample requires a relatively high degree of modification in order to be executable. To use a Use sample, you must either make modifications and "Save as..." or copy and paste from it.
Graphic description of a processing.