Configuring the middleware
Once installed the middleware is ready to be run and configured. Launching the JaCa-Android Middleware application you will see the following screen.
This GUI allows you to manually run/stop the middleware and to configure it. In detail what you can configure are:
The automatic launch of the middleware at each startup of the device.
If the auto-start preference is selected then the middleware is run at each startup of the device and any application that needs to use it can have directly access to its functionalities without experiencing any lags (because the middleware is already running in the background). Instead if the auto-start preference is not selected each time an application requires some middleware-related functionalities the middleware is started in background automatically (you will see an icon in the device status bar indicating that the middleware is starting up) and the application will be able to use the desired functionality once the middleware is booted (and if the corresponding artifact was selected in the middleware configuration, see below).
The set of artifacts contained into the MiddlewareServices (the middleware shared workspace).
The configuration of the MiddlewareServices workspace is left to the complete user discretion. So the user can autonomously select which artifacts include in the workspace, and so which features make available to the applications that intend to use the middleware shared workspace. As a general guideline it is suggested to keep in the MiddlewareServices workspace all the artifacts supported by your device, allowing then JaCa-Android applications to cooperatively use these artifacts. This is because the functionalities managed by these artifacts are strictly device-related functionalities and so their management affect globally each application running on the device (e.g. if an application turn off the device WiFi connectivity, all the other applications will experience this change). So having just one instance of this artifacts allows to all the application to have a general and consistent view of the functionalities provided by the device (along with their current status).
If needed you can create your own private instance of the artifacts contained in the MiddlewareServices workspace in your application, but this is not suggested, or at least not the standard approach. For an overview of the functionalities provided by these artifacts, and to see how use them in practice please take a look at the JaCa-Android by example guide.