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:
Provide technical functionality primarily for Managed File Transfer. Examples are File Accelerator, FTP Accelerator and Web services Accelerator.
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.
A script command used to synchronize chains of asynchronous events.
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".
Meta data added to the information in a Node or a Partner.
Categories are used to organize entities in the Administrator. Categories may be hierarchically built and are stored in tree structures which means that each category in the tree has a parent category.
Categories can be used to visualize Scenarios, Adapters, Packages etc.
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 compiled script that specifies one or several tasks that will be performed if the stated conditions are met.
A component may be an application component or a system component. Application and system components are two terms used when marketing the product, to distinguish between standard components and components that may be developed by a consultant when adapting a system to customer needs.
The definition of an Adapterflow, Script or Workflow which is used in a component configuration.
A translation from one value to another value (used by scripts).
An identity of something that happens in the system, which may initiate a processing.
A Process Server function that manages timers to trigger events.
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 comprehensive identity for information that has passed 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 one business partner (used by scripts).
A "best practice" showing which building blocks the described processing should contain to get the best possible result. For more information, see Pattern example.
A way to describe a flow (on a higher level). Each phase may contain one or many processings. For more information, see Phase example.
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.
An NT Service performing all automatic processing in the system.
An "example" of a Script, Adapterflow or Workflow, which always has to be "Saved as..." before it can be used. A Template may need more or less modification before it can be executed.
Simple examples of 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 "Save as..." or cut and paste from it.
Graphic description of a processing.