Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Starting Services (Several web:apps)

If there are several web:apps on the server (Bizview installations), as well as several processing services, then it will not automatically be possible to start/stop the services from within Bizview. In order to get this to work the following need to be done.

First, install the service, as usual. Thereafter, the service needs to be manually started from the web server the first time. When this is done, the service contacts the Bizview web:app and sends a message to this web:app where the service is located (search path on disc). The information is then automatically saved in ServiceConfig.xml (in the same catalog as the ordinary Config.xml).

When opening the Bizview Services GUI, Bizview will retrieve all services installed. Loops these services and checks in which search path the .exe file is installed and thereafter matches that search path to the one registered in ServiceConfig.xml. If Bizview matches the search path(s), the service will be shown in the Services user interface.

This new functionality means that Processing Service, Messenger Service and AD Sync Service will automatically be written to the ServiceConfig.xml when it is registered by Bizview. However it will also be possible to add own search paths manually if there is any other service that the users should be able to start/stop from the Services user interface.

Note: It is a catalog search path that is saved in the ServiceConfig.xml, so all services in that catalog will be visible.

In each node in the ServiceConfig.xml the attributes "name" and "path" exist. The attribute "name" is not used by Bizview so that should only be used for informative purposes.
Published:

Starting Services (Several web:apps)

If there are several web:apps on the server (Bizview installations), as well as several processing services, then it will not automatically be possible to start/stop the services from within Bizview. In order to get this to work the following need to be done.

First, install the service, as usual. Thereafter, the service needs to be manually started from the web server the first time. When this is done, the service contacts the Bizview web:app and sends a message to this web:app where the service is located (search path on disc). The information is then automatically saved in ServiceConfig.xml (in the same catalog as the ordinary Config.xml).

When opening the Bizview Services GUI, Bizview will retrieve all services installed. Loops these services and checks in which search path the .exe file is installed and thereafter matches that search path to the one registered in ServiceConfig.xml. If Bizview matches the search path(s), the service will be shown in the Services user interface.

This new functionality means that Processing Service, Messenger Service and AD Sync Service will automatically be written to the ServiceConfig.xml when it is registered by Bizview. However it will also be possible to add own search paths manually if there is any other service that the users should be able to start/stop from the Services user interface.

Note: It is a catalog search path that is saved in the ServiceConfig.xml, so all services in that catalog will be visible.

In each node in the ServiceConfig.xml the attributes "name" and "path" exist. The attribute "name" is not used by Bizview so that should only be used for informative purposes.
For an optimal Community experience, Please view on Desktop
Powered by Zendesk