Glossary
This glossary page explains Enactor specific terms used as part of extending and developing on the Enactor Toolkit.
Action
An action is a small unit of code that makes up an Application Process. An action can for instance be: loading an entity from the database, assigning some variables. An action is implemented as a java class but can also be another Application Process which is called.
Application Update
An application update allows to send a new version of the Enactor software or a customisation to one or more remote devices such as the POS, PDP or Store Server.
Application Process
Connected Process
Either an alternative name for a Process Connection Diagram document, or a reference to a part of one of those documents.
When used to refer to a part of the Process Connection Diagram, they represent the "applications" that are talking to each other in an estate
Eclipse
Eclipse is the Open Source Java IDE that Enactor uses and the Enactor Toolkit is an Eclipse plugin that allows the visualisation and development of Application Processes. See the Eclipse website for more information about Eclipse.
Enactor Home
When running an Enactor application, the working directory where the application runs is called Enactor Home. It contains the configuration files, the log files, and any other data that needs to reside on the file system. For instance local product images, file import, locally stored transaction XML are kept in a folder inside the Enactor Home.
Entity
Process Connection Diagrams
Process Connection Diagrams (sometimes just call Connection Diagrams or Process Connections) are used to specify how different devices in an Enactor estate talk to each other.
Process Details
Process Extension
Process Set
Queue Connector
A Queue Connector is used to transfer messages from one Queue to another. They generally don't understand the contents of the messages they are transporting and are only concerned with the technical aspect of moving messages around an estate.