Skip to main content

Pentaho+ documentation has moved!

The new product documentation portal is here. Check it out now at docs.hitachivantara.com. 

 
Version LDC
Hitachi Vantara Lumada and Pentaho Documentation

Managing configurations

  1. Last updated
  2. Save as PDF

Parent article

In Lumada Data Catalog, you can change specific configuration properties that are used by scripts when gathering catalog metadata, business terms, and term associations.

To update configuration properties, navigate to Manage and click Configuration. The tile displays the number of current configurations. The configuration controls are organized into sections for the Data Catalog Application Server (app-server) and the Data Catalog Agent (local-agent) categories. If you have installed multiple agents, then a configuration section for each agent is displayed. The tile displays the number of current configurations per group for each listed component.

The following configuration categories are available:

  • app-server

    SECURITY

    TOOLS

  • local-agent

    DISCOVERY

    DISCOVERY_PROFILER

    MISC

    MetadataService

For other properties, see the Hitachi Vantara Lumada and Pentaho Support Portal.

Parent Topic
Child Topics

Searching configurations

You can search the Configurations page for a specific property that you want to update. The search box accepts keyword searches, so even if you do not know the exact label for the configuration property you want, a keyword triggers a list of possible matches for the keyword you entered. Results will return a list of the applicable sections and group names that contain the property that matches your search term; you must click on the group name to see the list or matching properties.

Parent Topic

Changing configuration settings

When you click the drop-down menu on the right side of the screen for a property, if the property can be modified there is a Value text box to change the value of the property and 3 buttons:

  • Reset - Reset to the last saved value
  • Set to default - Set the property's value back to the default value
  • Save change - Save the property value specified in the text box

Users assigned the administrator role can configure most properties in the Configurations page, however some properties are read-only, and you will not be able to access the drop-down menu for these values. An example of read-only values are the SECURITY settings for app-server.

Once you have changed the value of the property, ensure that you save this change. For certain configuration properties, you are then required to restart the component. These configuration properties are indicated with an asterisk (*) next to Value in the property’s drop-down menu. Currently only agents use these kinds of properties, see Restart an agent.

Parent Topic

Restart an agent

Properties that have an asterisk (*) next to Value in their drop-down menu require an agent restart so that the agent will use the new property values.

  1. After you have updated your properties for the agent, return to the Configurations page.
  2. The configurations section for your agent should now have a warning icon next to the Restart Local Agent button, indicating that a change to the configuration has been made, but isn’t currently being used by the agent. This icon will be displayed until a restart has been executed. Click the Restart <agent> button.
  3. Click Manage, then click Agents to check the status of the LDC Agent. The Connected column for the LDC Agent should have a green checkmark icon.
Parent Topic

Large properties configuration

A common use case for managing configurations is changing the settings for large properties for an agent. In Data Catalog, the large properties location is where the agent will store metadata from profile jobs. You can set up large properties location in a file system like HDFS, or on object storage like AWS S3. The following is an example of setting the large properties configuration for an AWS S3 bucket

Procedure

  1. Navigate to Management, then click Configuration.

  2. Locate the configuration section for the agent where the large properties location has to be set up. In that section, click the > for the MISC group to view all miscellaneous properties for that agent.

  3. Open the Attributes for discovery cache metadata store property and provide credentials and the endpoint for your AWS S3 bucket

    fs.s3a.access.key=<AWS S3 access key>
fs.s3a.secret.key=<AWS S3 secret key>
fs.s3a.endpoint=<AWS S3 endpoint>
fs.s3a.path.style.access=true
fs.s3a.threads.max=40
fs.s3a.connection.maximum=200

  4. Click the Save Change button for the property.

  5. Open the Relative location for a large properties metadata store property. In the value field, provide a folder location in your S3 bucket. For example. /lp1.

  6. Click the Save Change button for the property.

  7. Open URI for discovery cache metadata store property and provide the URI for the S3 bucket. For an AWS S3 URI, this will be in one of two formats depending on the agent you are configuring these properties for:

    • For a remote agent running on EMR: s3://<Bucket Name>
    • Otherwise: s3a://<Bucket Name>

  8. Click the Save Change button for the property.

  9. Navigate back to Manage Configuration page and click the restart link of the respective agent.

Parent Topic