The job manager service can depend on one or more other services.
For example, if the manager was started on the database server, it can only run if the database manager has been started.
Similarly, if it is connected to the database via local Middleware, it can only run if the Middleware has been started.
The installation allows you to specify the functional dependencies between services to avoid having the job manager service fail to start.
Dependencies management is performed using the "-depends" parameter:
If "-depends:none" is specified in the command line, the manager will be installed without services functional dependencies.
This installation is correct if the database and/or Middleware server are located on another machine.
if "-depends:all" is specified in the command line, the manager will be automatically installed with dependencies on all services identified as "potentially" dependent, i.e. on all Adelia Middleware services and all database manager services.
This installation is correct if you require a local database and have only one database service on the PC.
This installation can cause problems if multiple database services exist and some have been deactivated: all dependency services must have been started when the job manager starts.
If the "-depends" parameter has not been specified or has the "ask" value, the installation program will list the Middleware and Database services and ask you to choose any possible dependencies.
In the example provided in the "Job manager in batch mode" topic, a connection has been established in local mode (without Middleware) to a local SQL Server database:
- no dependency on the Middleware service is required...
- selection of the "MSSQLSERVER" service as a dependency...
