Words used in this course
Lesson 25 of 25 4 min read
A glossary of routing and module terms, with how they relate to each other.
Use this page as a quick reference when a term on the screens, or in a ticket, isn't clear. The diagram first shows how the main terms fit together.
Rendering diagram...
Glossary
| Word | Meaning |
|---|---|
| Integration type | A kind of integration, for example Shopify or an SFTP partner. |
| Message type | One of the four steps: Create, Parse, Receive or Send. |
| Service | The Supply Lens application that does the work: Integrations (Main integrations service), AS2 or Peppol. |
| Supported | The integration type does this message type. |
| Routed | A service is assigned to a supported message type. |
| Not routed | Supported, but with no service. Messages are lost. |
| Live | Messages get to the service. |
| Off | A service is assigned, but a switch is off. The reason is shown. |
| Module | The code that does the work for one message type, identified by its key. |
| Module route | A rule that tells a service which module to use, for a type or group, a message type, a document type and organisations. |
| Default | The module route for all organisations. |
| Override | A module route for one organisation. |
| Overridden | A route that is on, but another route wins. |
| Ignored | A route that is off, so the service doesn't use it. |
| Module group | A set of integration types that share module routes for one message type. |
| Available module | A module that a type's routes can name, because it was made available directly or comes from a group the type is in. |
| Published map or profile | A config-driven definition for an organisation. It runs before any module route. |
| Config-driven integration type | A type whose work is defined by published maps and profiles instead of modules. It still needs routing. |
| Coded integration | A type whose work is done by modules in the code. |
| Routing Switches | The emergency switches for services, message types and the links between them. They affect all integration types. |
Recap
- An integration type supports message types, and each supported message type is routed to a service.
- A service looks for a published map or profile, then a coded module, then a module route.
- Module routes name modules; module groups share module routes across types.
- Not routed loses messages; Off pauses them for a stated reason.
Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.