Desktop Launching Component
Overview #
The Desktop Launching Component is a Desktop UX component that is responsible of managing the environments on local user system.
Features #
The desktop launcher component will get list of environments from the API server.
It also ensure the sanity of local enviroments folder to automatically detect any obsolate environment that is not present on API server and clean that up.
The desktop launcher component have a way to ensure that local runtime of an environment should be always up to date with the server environment.
The desktop launcher component will automatcally detect if the environent is updated on server and update the desktop runtime of local enviornment.
Installation #
Desktop Launching component will be delivered as a zip file containing a batch file to run the launching components and configuration file to to configure the properties.
Configurations #
The Environment esktop Launching component depends on some configuration parameters. Below are the configurations parameters
server_uri
#
This parameter defines the Environment API sever url to which the desktop launcher should be connected.
authorization_client_id
#
This parameter defines the client id of the OAuth2 authorization server.
Default value: sics-desktop-launcher
authorization_endpoint
#
This parameter defines the authorization url of OAuth2 authorization server.
Default value: http://localhost:8180/realms/sics/protocol/openid-connect/auth
token_endpoint
#
This parameter defines the token url of OAuth2 authorization server.
Default value: http://localhost:8180/realms/sics/protocol/openid-connect/token
environments_root_path
#
This parameter defines the root folder on the user local system where the environments will be locally installed.
Default value: C:/TEMP/SICS
These configuration values should be changed accordingly in config.properties file which is present inside conf folder in the delivered zip file.
Logging configuration #
The deskop launcher component logs information, which will helpful in case of debugging if anything is not working properly.
The behaviour of the logging can be configured using log4j2.xml which is present inside the conf folder.
Launching desktop for an Environment #
As soon as user launch the desktop launcher, ti will be redirect to OAuth2 Login URL as shown below.
Once user logged in in Environment Launching component, user can see list of environments present on server as shown below.
User can select an environment and launch by clicking Launch button or Launch menu time from File menu as shown below.
If the desktop for an environment is launched first time, the desktop launcher download the runtime zip file from its hosted URL and install in the local configured directory. Once done the desktop launcher will launch the Assure Reinsurance Desktop.
During subsequent launch, the desktop launcher will detect the latest runtime, in case the runtime is not latest, desktop launcher cleans the local enviroment and re-install the desktop client for the selected environment.
If the runtime is latest, Assure Reinsurance Desktop will be launched.
Update of environments list #
The desktop launcher update the environment list from server, every time a user login to desktop launching component.
User can also manually update the environment list by using Refresh menu item from File menu.