In ODI 11 we could make the ODI agent run as a service in Windows. The ODI agent technology changed in ODI 12c making this not possible. True, I can execute the agent start cmd as a windows service, but this is not a proper service, is very kludgy and does not allow me to control the agent from the Services Control panel
In ODI I can create a Nodemanager Windows service, but that is not the agent - that component is started afterwards through a WLST script. This does not meet my goal of having the ODI Agent starting automatically when the server starts (and dependent on the MS SQL Server database hosted on the same box being up).
Apart from the simple answer of an at-boot-time script to start the agent does anyone have a solution to auto starting the agent using Windows services?
Is is feasible to make some WLST changes to node manager so that the agent auto-starts?