When you run the Desktop Launcher, you may add one or more launcher services that provide connection settings for instances. You may use launcher services as an alternative to manually entering the settings for each instance.
A launcher service is an external web service that returns a list of existing Platform processes to the desktop launcher. The launcher will only know the URL to the service and uses this information to retrieve the list of instances via HTTP GET.
Launcher services are useful in a dynamic environment, e g cloud deployments, where platforms are expected to change IP addresses and ports often. But it can also be useful in a static environments since it reduces the need for manual configuration.
In order for the Desktop Launcher to correct parse the response from launcher service, it must adhere to the following format.
The unique identifier is used for grouping attributes of a instance. You may use e g a UUID for this purpose.
The following attributes are available:
The URL Platform Container host, e g https://example.com. This attribute is mandatory.
An arbitrary name of the instance that will be displayed in the Desktop Launcher. This is attribute is mandatory.
When the Desktop connects to the Platform it retrieves the value of the property pico.rcp.platform port from the STR. If the Desktop will run on a different network than the Platform, you may need to include this attribute in order to override the retrieved value with an external port number. This attribute is optional.
Example - GET request with curl and response from launcher service