Data Studio Settings

This topic explains the Data Studio settings on the Data Studio tool.

This settings on the Data Studio navigation menu and the Data studio overview page enables you to use the associated Cloud Service, configure AI profile and configure SMTP.

This helps in defining the data during the load. This setting sets a variety of general preferences like setting default credentials to define the data you load, configure SMTP for data sharing, configure AI profile and configure Marketplace cloud link access.

To set the Data Studio Settings, on the General tab of the wizard, specify the email address to configure your profile for Marketplace and Sharing.

On the Cloud Services tab of the wizard, under Cloud Object Store Access, specify the following field values:

  • OCI Credential: Selecting an OCI credential enables you to discover the OCI buckets. Click + to create OCI Credentials.
  • OCI Compartment: This drop-down field lists the buckets present in your compartment for loading and linking from Oracle cloud services. If you select any other cloud service provider apart from Oracle, this field displays None by default.
  • AWS Credential: Selecting an AWS credential in Data Studio Settings enables you to discover the S3 buckets. Click + to create credentials for Amazon S3 cloud storage.
  • Azure Credential: Selecting an Azure credential in preferences enables you to discover the Azure BLOB storage. Click + to create credentials for Microsoft Azure BLOB storage and Azure Data Lake Storage.
    Click Check Object Store Access to check if you have access to the object store. You will view a Policy Check wizard with the following bucket lists:
    • OCI list buckets
    • AWS list buckets
    • Azure list buckets

    The Object Storage Listing Policy checker evaluates if you have access to the buckets. If yes, the checker box is highlighted in green with a check sign, else the checker box displays the policy highlighted in red with a red cross.

Under Cloud Service Provider for AI: Select any of the following options from the drop-drown field:
  • Oracle Cloud Interface (OCI)
  • Amazon Web Services (AWS)

Click Check Cloud Service Access.

You will view the following options in the Cloud Services Policy Checker dialog box. The AI cloud policies listed below must be checked against the listed policies and approved by the Cloud Service vendors for support. The Data Studio tool will test these services and inform you if the data you load in the tool is able to access the services.

On the AI Profile tab of the Data Studio Settings wizard, you can configure your AI preferences.

  1. Select AI Profile (Experimental) from the drop-down use this AI profile for facilitating and configuring the translation of natural language prompts to SQL statements.
    • To utilize the AI services in Data Studio, you must have either an OCI AI or OpenAI or Cohere or Azure OpenAI service account.
    • You must also have access to DBMS_CLOUD_AI package to set your AI profile.
    • If you have Select AI set up using either OpenAI or Cohere or Azure OpenAI service, you can enhance your data by loading small reference data tables that are generated by large language models. Try out the suggested prompts or come up with your own to generate data to load into the autonomous database.

      You can also use this AI profile to generate Marketplace dataset description and tags. This AI profile is used to generate table description in Catalog App.

      See Use DBMS_CLOUD_AI to Configure AI Profiles to create and configure your AI profile.

  2. Click Check AI Access.

    The AI Policy checker checks for the following service:

    • Generative AI- The Data Studio tool checks if it has access to the Generative AI service.

  3. Click View Profile to view the details related to the AI profile you use. You can view the AI Provider, AI Model and the Credential you use to create the AI profile.

  4. Click Create Profile to create a new AI profile. Specify the following field values:
    • Profile Name: Enter the name of the AI profile. For example, OCI AI.
    • AI Provider: Select any of the following providers from the drop-down field:
      • OCI AI
      • AI Azure
      • Cohere
    • Model: Select any of the following models from the drop-down field:
      • Llama
      • Cohere
    • Credential: Select any of the credentials from the drop-down to create an AI profile.
    • Click Show Code to view the equivalent PL/SQL code to create AI profile.
      BEGIN 
    C##CLOUD$SERVICE.DBMS_CLOUD_AI.CREATE_PROFILE(
        PROFILE_NAME => 'new_profile',
        ATTRIBUTES => '{"credential_name":"my_credential_name","model":"","provider":""}');
END;
/

    Click Create AI Profile.

You have successfully set and configured your AI profile in the Data Studio Settings wizard.

On the SMTP tab of the Data Studio Preferences wizard, you can configure email service like a local email client on your system (e.g., Thunderbird).

Note:

You must configure SMTP only once and then the system uses the saved configuration from that point forward.
Specify the following field values in the SMTP tab of the wizard:
  1. Server host: Enter the endpoint used to send the email. For example, internal-mailrouter.oracle.com.
  2. Server port: Enter the SMTP port used to accept an email. Email Delivery supports TLS on port 25. Sender:
  3. Enter the email address of the sender. For example, oaapgens_us@oracle.com.
  4. Server Encryption: This field indicates if TLS, the standard means of performing encryption in transit for emails, is being used. Providers must encrypt emails while it's in transit to the Oracle Cloud Infrastructure Email Delivery service. Encrypted emails are protected from being read during transit. If there is no encryption, enter, None.
  5. Select credential to use for SMTP connection from the drop-down. If there is no available credential in the drop-down, you can create credential by clicking Create Credential icon.

Click Save to save your changes and Test the test the ongoing process of setting preferences.

On the Marketplace tab, you can set the configurations you require for the Data Marketplace tool.

Access to data in Data Marketplace is restricted based on user authorizations. As non admin users you have permission to access the Data Marketplace tool based on the Data Studio Settings configuration. You can view the following options:
  • Restricted, Requires Authorization:

    Selecting this option enables you to publish restricted cloud links and, consequently, restricted marketplace listings. You will have the ability to grant and revoke access to these listings to specific OCIDs.

  • Publish:

    This option specifies who and from where you are allowed to access the registered table.

    You can choose from any of the following available options:
    • TENANCY: You can grant remote data access to any resource, tenancy, compartment, or database in the tenancy of the Autonomous Database instance that is registering the data set. This scope is more restrictive than the REGION scope.
    • COMPARTMENT: You can grant remote data access to any resource, compartment, or database in the compartment of the Autonomous Database instance that is registering the data set.
    • REGION: You can grant remote data access via cloud links to other tenancies in the Autonomous Database instance that is registering the data set.

      Note:

      Marketplace listing currently can only be published up to the compartment level. The tool does not allow you to publish a marketplace listing to entire region for security reasons.
    • None: You do not have access to any resource.
  • Read:

    This option allows READ access for the specific user to access the registered table.

Select Apply Changes to save and apply the configuration you made in the Marketplace tab of the Data Settings dialog.

You have successfully set and configured your preferences in the Data Studio Settings wizard.