Glossary
Application¶
The application is the Platform 6 packaging unit to deploy a set of pre-configured services on Platform 6 instances.
It is composed of:
- Built-in Platform 6 service items such as scripts, routes, workflow steps, views, data models and reference data.
- Any additional bundled resources such as custom Java JAR files, data files (CSV, Excel…) that are used by built-in service items.
Application Publisher¶
A company or an individual who creates and distributes a Platform 6 application.
Application Publisher Profile¶
The key of the application installed on a Platform 6 instance and which enables an application publisher to develop and package a Platform 6 application.
b2box¶
Platform 6 is the version 6 of Amalto’s e-Business Cloud solution. It used to be called internally b2box.
Common Message¶
The data exchange between Platform 6 services is conducted through what is called common messages. A common message is a generic message with headers and attachments. It consists of a unique identifier, the sender’s identifier and content.
Common Message Bus¶
Hazelcast is a distributed In-Memory Data Grid platform for Java. It is used as a message bus and allows various Platform 6 services to communicate with each other via common messages.
Instance¶
An instance, is the logical deployment unit of Platform 6, it comprises:
- A set of built-in services.
- A PostgreSQL database for persisting service items, transactions and workflow tasks.
- A Common Message Bus for inter-service communication within the instance.
- A REST API to expose the services to the outside world.
P6 Auth¶
The Amalto OAuth2 compliant authentication and authorisation server. It is developed in Java and uses Apache CouchDB for the data replication.
P6 Proxy¶
The Amalto proxy (developed in Node.js), used to offer a unified access to all registered Platform 6 instances from Amalto’s portal.
Package an Application¶
Bundle the application’s components in a container for installation on multiple Platform 6 instances or distribution to other companies.
Packaged/Unpackaged Service Item¶
A packaged item is a service item with an none empty application key, thus belonging to a specific application.
If you do not intend to distribute the items you create locally on your instance, you can leave them un-associated to any application. Hence, an unpackaged item is a service item with an empty application key.
Permission¶
A string of characters structured as follows feature=action and which allows the user to perform a specific action on a specific feature.
Portal¶
Platform 6’s default user interface for users, administrators and application developers. It’s the easiest unified access to manage multiple Platform 6 instances (potentially belonging to different organizations).
Route¶
A route defines one inbound and one or more outbound endpoints for transactions along with mediation rules in-between. Routes are defined using Apache Camel.
Routing Order¶
When transaction flows in a route, it creates a routing order which tracks the execution of the route. Routing orders can be monitored, cancelled, replayed…
Service¶
A Platform 6 instance‘s feature (eg: reports, scripting, workflow, payment …).
Transaction¶
Any secure business exchange of documents between different organizations. Transactions flow in the system through routes.