Working with delivery methods

Pre-requisites for Editors or Admins to enable the access in watsonx.data delivery method:

1. Required roles:

   1. Community roles: Editor or Administrator

2. Create a watsonx.data Presto connection in the Data Product Hub instance. The credentials in the Presto connection will be used to:

   1. Create a watsonx.data access policy to grant the consumer access to a table.
   2. The user whose credentials are specified in the Presto connection must have Admin access on the catalog in watsonx.data.

3. Engine access:

   1. If the producer chooses not to select any Presto engine while creating the Data Product (DP), the delivery will succeed regardless of the producer’s access to any Presto engines.
   2. If the producer chooses to grant consumers access to a specific Presto engine during DP creation:
      1. The producer must have Admin privileges on the selected Presto engine.
      2. If the producer does not have Admin access:
         • Delivery will fail if the consumer does not already have access to the specified Presto engine.
         • Delivery will succeed if the consumer already has access to the specified Presto engine.

Prequisites for Editors to use the access in watsonx.data delivery method:

1. Required roles:

   1. Community role: Editor

On successful delivery, consumers get access to:

• Data artifact inside data product: Specific table, schema or catalog details which can be viewed in the Data manager view in watsonx.data.
• Producer’s engine: If the producer created the data product by enabling the option to provide access to the producers’s engines in watsonx.data.
• Watsonx.data link: For easy access into the watsonx.data instance in order to verify and work on the delivered data.

Pre-requisites for Editors or Admins to enable the access in watsonx.data delivery method:

The access in watsonx.data delivery method provides you access to a data product created from the watsonx.data instance. In the My Subscriptions page, you can access the data product by selecting the watsonx.data asset details link after the delivery is completed. You will have a view of your data product and specific resources you have access to in the watsonx.data instance.

1. You must have the following accesses in watsonx.data:
   1. Access to a spark engine connected to the target catalog: User
   2. Access to a presto engine (this is only required to make the connection): User
   3. Access to a target iceberg catalog: User role to the full catalog or an access policy that gives some permission to use the catalog. For more information, see Managing data policy in the watsonx.data documentation.
   4. Access to storage used for the target catalog: Writer or above
   5. Access to Cloud Object Storage: Add as a component in the watsonx.data instance. The data extract will land here before being ingested to watsonx.data.

Pre-requisites for Editors to use the deliver as a table in watsonx.data delivery method:

1. Required roles to complete this task

   1. Community role: Editor

2. Create two connections:

   1. Cloud Object Storage: Add as a connection in the Data Product Hub instance, using the same connection as watsonx.data. To create a COS connection in DPH you must use HMAC credentials to configure the Access key and Secret key or the Service credentials authentication method.
   2. IBM watsonx.data Presto: Connect your Presto engine by copying the JSON snippet provided in the watsonx.data instance and pasting it when creating a new connection to the IBM watsonx.data Presto engine in the Data Product Hub instance.