Skip to end of metadata
Go to start of metadata

Set up a domain account during installation

FEATURE AVAILABILITY STARTING FROM RELEASE 1.11.3

SET-97 - User should be able to point to a hibernate configuration file during setup Released

Users can create their own hibernate configuration file and make the installer use this file. The hibernate.connection.url property in this file should include the IntegratedSecurity=true setting, no user name and password are specified. This configuration will implicitly use the domain account that the JobScheduler Master / Agent is running for.

Set up a domain account for an existing JobSchedule installation

If you wanted to use a connection to a SQL Server for JobScheduler with a Windows domain account then it could happen that you receive an error during set-up:

The given userid that is used by this connection presents itself as a SQL\USER account, instead of a DOMAIN\USER account.

A check on the SQL Server indicates that the given userid that was used to establish the connection presents itself as a SQL\USER account, instead of a DOMAIN\USER account.
You can continue the set-up but the database tables will not be created and the JobScheduler doesn't start.

Follow these steps to fix the problem after the set-up

  • edit $SCHEDULER_DATA/config/sos_settings.ini

    for MSSQL JDBC driver add IntegratedSecurity=true
    for jTDS JDBC driver add domain=<domainname>

    Then start $SCHEDULER_HOME\install\scheduler_install_tables.cmd to create the database tables.

     

  • edit $SCHEDULER_DATA/config/factory.ini

    for MSSQL JDBC driver add IntegratedSecurity=true
    for jTDS JDBC driver add domain=<domainname>

edit $SCHEDULER_DATA/config/hibernate.cfg.xml

for MSSQL JDBC driver add IntegratedSecurity=true
for jTDS JDBC driver add domain=<domainname>