Configuring the Master

See Basic TA Configuration for more information about configuring your TA system and the master.props file.

Configuring the Master for SNMP

If you want to use Simple Network Management Protocol (SNMP) to send traps in TA, you must tell the Master how to connect to the SNMP server. You can configure the Master to use SNMP from the master.props file.

  1. Open the master.props file in a text editor such as Notepad.

    The master.props file is located in the config directory. If you used the default locations during installation, the master.props file is located at: C:/ProgramFiles/TIDAL/Scheduler/master/config/master.props.

  2. Enter the SNMP information: 

    snmphost=<hostname of the SNMP server> 
    snmpport=<port number used by the SNMP server> on separate lines.

  3. Replace the text enclosed in brackets with the hostname and port number for the SNMP server.

  4. Save and close the master.props file.

  5. Restart the Master service from the TA Service Manager.

Configuring the Nice Value for the Master Service

Usually the TA Master service would have the highest priority for CPU resources on the machine where it resides but there may be occasions where you want other services to have a greater priority to CPU resources. You can reconfigure the TA Master service to a lower priority by assigning it a Unix nice value as used in the ps command for the Solaris, HPUX and AIX operating systems.

TA uses a different nice value scale than that used in Unix systems but the formula can be used to convert the TA nice value to a Unix nice value: 20 - (TA nice value -1) = Unix nice value.

Example: A TA nice value of 40 for the Master service would convert to a -19 Unix nice value, 20 - (40-1) = -19.

Changing the Master Database Password

To change the Master database password:

  1. Log on the Master machine.

  2. Navigate to the Master > script directory inside cmd.exe.

  3. Run 

    tesm setpwd tidal97 tidal98.

    Note: In the command above, tidal97 is an example of the current password and tidal98 is an example of the new password. When you execute the command, provide your own current and new passwords.

The master.props will have a line added to it similar to this:

Example: dbpwd=5l1 \\rx((YYYSS

Enabling Multi-Domain Authentication

TA allows for multiple-domain user authentication for the TA Master. The purpose of this function is to allow users defined in different domains to be authenticated within one Master configuration to avoid installing one Master per domain.

To enable this multi-domain authentication:

  1. Add this new property value in master.props, located under <MASTER_INSTALL>\config.

    Security.Authentication.Ext.File=user-auth.xml Where user-auth.xml is the file name.

  2. Build the user-auth.xml file to include all AD/LDAP servers for TA user authentication.

    This example defines two servers:

    <ext-user-auth>
    <user-auth>
    <name>TIDALSOFT</name><desc>Configure AD for user authentication</desc>
    <type>ActiveDirectory</type>
    <host>hou-ad-1.tidalsoft.local</host>
    <port>389</port>
    <ad.usersearchprefix>DC=tidalsoft,DC=local</ad.usersearchprefix>
    <ad.groupsearchprefix>DC=tidalsoft,DC=local</ad.groupsearchprefix>
    </user-auth>
    <user-auth>
    <name>TIDAL-API-ACCESS</name>
    <desc>Configure AD for token authentication</desc>
    <type>ActiveDirectory</type>
    <host>hou-ad-2.tidalsoft.local</host>
    <ad.authenticationmethod>simple</ad.authenticationmethod>
    <port>389</port>
    <ad.usersearchprefix>DC=tidalapi,DC=local</ad.usersearchprefix>
    <ad.groupsearchprefix>DC=tidalapi,DC=local</ad.groupsearchprefix>
    <ad.binduser>dv\tes</ad.binduser>
    <ad.bindpassword>lE?+NE"7;BD7f:AAAAA</ad.bindpassword>
    </user-auth>
    <user-auth>
    <name>ITTIDAL</name>
    <desc>Configure Open LDAP Server for user authentication</desc>
    <type>LDAP</type>
    <host>10.88.103.148</host>
    <port>5389</port>
    <ldap.binddn>ou=People,dc=ittidal,dc=com</ldap.binddn>
    <ldap.userobjectclass>account</ldap.userobjectclass>
    <ldap.userbinddn>dc=ittidal,dc=com</ldap.userbinddn>
    <ldap.groupbinddn>cn=testest,ou=Group,dc=ittidal,dc=com</ldap.groupbinddn>
    <ldap.useridentifiertype>uid</ldap.useridentifiertype>
    </user-auth>
    </ext-user-auth>

In the example above, the authentication process will validate a user using TIDALSOFT first and then using ITTIDAL if the user was not found in TIDALSOFT.

Note: The ldap.useridentifiertype parameter specifies the identifier that is part of the DN. The value of the ldap.useridentifiertype parameter indicates which LDAP attribute is used in a user's DN or Distinguished Name. Possible values are: uid, cn, sn, mail.

Note: The AD/LDAP server configuration found in the master.props file is used first before the configuration specified in the user-auth.xml file is used.