An XMA component can be started by activating a HTTP link to it in a browser. The link is composed of the component URL as described above extended with the extension .xma and optional parameters. The parameters are coded the same way as URL-coded form parameters in HTTP.

<component-url>.xma[?<name>=<value>[&<name>=<value>]*]

Example:

http://localhost:7001/krimicee/KrimiShell.xma?idClient=34235

All URLs ending with .xma are mapped to a special servlet (XmaLauncherServlet, this is delivered with the XMA-Bootruntime which has to be registered by the XMA application). The response of this servlet has the MIME-Type application/x-xmalauncher, which should cause the browser to pass it to the XMA-Boot-Runtime's executable at the client-side (if the XMA-Boot-Runtime installation registered the MIME-Type correctly this is done automatically for Internet Explorer). The parameters in the URL are passed to the started XMA-Component.

An XMA application started by a browser link is not able to return any values. It is also not possible that the caller waits (blocks) until the XMA application is finished if started by a browser link.