A long ID for applications, modules, or services can be generated in the browser for the selected configuration by performing the command Tools => Compute long ID.
The computation uses the name of the application, the module, or the service.
General use case
It is not necessary to set the ID for an application, a module, or a service. If you don't do it, the framework will perform the generation itself. It will also ensure that all the names will be different:
No two applications will have the same ID
No two modules in the same application will have the same ID
No two services will have the same ID. Note that for services two services with different namespaces will still have two different IDs
It will be the case even if by mistake you give the same ID to two different applications, modules, or services. In that case, the framework will reset the ID to the second element to ensure the unicity.
Usage with external applications
When you use the framework with an external application (for example by using the ExternalComm module), the bytes exchanged by UDP or TCP between the external application and the ExternalComm module will use the long ID of the services to identify the services. This means that in this case you must know the long ID of the services.