• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 93 subscribers
  • Views 1368 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

History Service

Steve.Knott
over 5 years ago

Hi

I noticed in the release notes for OneIM 8.1 that the History service for the HDB will use viNetworkService.exe
Does anyone know if there are any reasons why the viNetworkService.exe cannot also be used as the History service in previous versions? (8.0.x)
From the release note:
Issue ID 28058
"The One Identity Manager History Service and the One Identity Manager Service
are both installed when the One Identity Manager History Database is installed.
To correct the problem, the HDBService.exe file has been removed. The
installation of the History Database service will now be carried out by the
viNetworkService.exe"
  • 0 over 5 years ago

    As far as I remember, the HDBService existed for 2 reasons. Reason one, if you installed the service using installuil.exe (like in the old days), you automatically got a different service name in the Service Manager. Reason two, to be able to distinguish the two services by the process name in the task manager in case of any monitoring requirements.

    With the changed and optimized installation procedures in 7.x and higher, we have seen several issues where either both service where installed when you install the HDB service on the same machine as a normal Job Service or auto-update was confusingly installing or removing components.

    To clean the mess it was decided, that removing the HDBService was the best option (in combination with some other options in the setup like having the option to rename an additionally installed service).

    HtH

  • 0 over 5 years ago in reply to Markus Weiss-Ehlers
    Markus, Thanks for the explanation.
     
    In the customers deployment the intention is to deploy the service for the history database on a separate VM to any other components.
     
    It seems the service itself is functionally similar to the main OneIM job server service.
     
    To take it one step further, do you think it is possible to deploy the standard oneim-job docker container and use this as for the history service?
    Do you see any issues with this?
     
    We have an AWS image with the standard oneim-job docker container currently working and I think it would be much easier, if possible, to just to copy the existing automated AWS image setup and then just change the secrets (CONNSTRING) and a few other parameters to point to the history database.
  • 0 over 5 years ago in reply to Steve.Knott

    I think it should work to use the standard oneim-job docker container but I haven't tested it.