Active Directory data point is used to configure connectivity to Active Directory services. For each Active Directory user, a separate data point will have to be created. The Active Directory data point will be associated to any Active Directory data object created.

To work with Active Directory Data Point, follow below steps:

Step I: Create a New Data Point

Step II: Provide connection details

1. To connect to Active Directory database following details need to be provided in the Properties tab.

  • Host: Specify the hostname or the IP address of the Active Directory system
  • Port: Specify the port associated to the Active Directory system
  • App User: Specify the user id that will be used to connect to the Active Directory system. This user should have necessary privileges to access the data in the databases.
  • Password: Specify the password for the App User. To use the project parameter for the password, check the Use Project Parameters option, and you can view and select the required Project Parameter from the Password drop-down.
  • Jdbc Options: Specify the options that should be used along with JDBC URL to connect to Active Directory. 
    For example, following details are provided in JDBC Options to connect to Active Directory: user=diyotta, password=****, db=TEST_DB.
  • Base DN: Specify the Base DN details to which the data point must be connected.

Note:

  • Mandatory field names are suffixed with *. To establish the connection, provide all the mandatory property field values.
  • All the fields in the Properties tab can be parameterized using project parameters. To parameterize the fields, refer Working with Project Parameters.

2. Assign Agent: To assign or change the associated agent click Change. The Change Agent window appears and displays the list of available Agents. From the list, select the required Agent Name.

Note: To search for a specific agent, enter the keyword in the search bar, and the window displays the search result list. Select the required agent and click Ok.
  • If Default agent is assigned to the Project then automatically, the Default agent will be associated with the new Data point created.
  • If Default agent is not assigned to the Project then, no agent will be assigned automatically and appropriate agent needs to be assigned to the data point.
  • When connecting to the Agent server then, the agent installation user should have appropriate privilege to access the path where file will be placed.
  • When connecting to the remote server then, the firewall needs to be opened from the Agent server to it and user specified to connect should have appropriate privilege to access the path where file will be placed.

Step III: Test the data point connection

  • To validate that the data point is able to connect to the Active Directory data point database using the details provided, refer Test Data Point Connection. 

Step V: Save the data point 

Note:

Step VI: Modify the configured Extract properties

When moving data from one system to another the data is extracted from the source system, moved over the network and loaded into the target system. The SQLs and commands generated during execution of the jobs to extract data are generated based on the properties defined for these. The properties associated with the extraction of data should depend on the format, performance and variety of the data being moved. These properties vary based on the environment and the type of the system. Diyotta comes with default properties that covers most of the known scenarios. 

To modify these properties, refer Editing Extract Properties in Active Directory Data Point.

  • The default values for extract properties can be configured in the Admin module and these properties reflect in the Studio module.
  • The extract properties set in data point are by default used in the source and target instance of the data flow and the job flows.
  • It is a good practice to set the extract properties as per the company standards in the data point.
  • However, if needed any specific property can be overridden in the data flow or job flow.