Skip to main content

Connecting to ADW in Oracle NetSuite Analytics Warehouse

Using Oracle Autonomous Data Warehouse with NetSuite Analytics Warehouse

Introduction

The wallet is a .zip file that contains credentials necessary to connect to the Oracle Autonomous Data Warehouse (ADW) instance associated with NetSuite Analytics Warehouse (NSAW). This blog post will guide you on how to use it effectively.

Downloading the Wallet

The wallet file is downloaded from the NSAW Console, under the Warehouse tile. The wallet.zip file will be downloaded to your local computer, ready for use.

Connecting to ADW in Oracle SQL Developer

The wallet file plays a crucial role in establishing a connection to the ADW instance in Oracle SQL Developer. Here are the steps:

  1. When creating a new connection in Oracle SQL Developer, set the connection type to "Cloud Wallet".
  2. Use the wallet.zip file as the Configuration File.
  3. The wallet file, along with the ADMIN user and the password set using Reset Credentials on the same screen in NSAW, are used to access ADW.
  4. Connecting to ADW in OAC

    To create a direct connection to the ADW instance from Oracle Analytics Cloud (OAC) within NSAW, the wallet.zip file is required. Follow these steps:

    1. When creating a new connection, select "Oracle Autonomous Data Warehouse" as the connector type.
    2. Upload the wallet.zip file. The cwallet.sso file will be auto-populated from the wallet.
    3. Enter the admin password set using the Reset Credentials function in NSAW.

    Security

    The wallet file and the associated admin user/password provide access to the ADW instance, so it should be stored securely. It is important to share wallet files only with authorized users. If wallet files are transmitted in a way that might be accessed by unauthorized users, the wallet password should be transmitted separately and securely.

    OAX_USER Connection

    After the initial connection to the ADW with the wallet using the ADMIN user, it is necessary to set the password for the OAX_USER using the following SQL command: ALTER USER OAX_USER IDENTIFIED BY <new_password>. This will ensure that all tables will be created under the OAX_USER node and not under the ADMIN node when persisting the data into the data warehouse. The connection to the ADW in OAC can then be made using the OAX_USER credentials and the same wallet file.

    Reach out to us at support@dataants.org to get help with your NetSuite Analytics Warehouse implementation or maintenance

Comments

Popular posts from this blog

Complete Guide to NetSuite AI Connector via Claude AI

NetSuite AI Connector to Claude AI - Complete Setup Guide Overview The NetSuite AI Connector Service enables direct integration between NetSuite and Claude AI, allowing you to access NetSuite data and functionality through natural language interactions with Claude. This integration leverages the Model Context Protocol (MCP) to provide secure, real-time access to your NetSuite environment. It's important to note that Claude is currently the only AI agent supported by NetSuite's AI Connector Service. Prerequisites NetSuite Requirements Active NetSuite account with Administrator privileges (for initial setup) NetSuite AI Connector Service enabled in your account Access to Setup > Integration > Manage Integrations Understanding of your NetSuite account structure and customizations Claude Requirements Claude Pro subscription Access to claude.ai Modern web browser (Chrome, Firefox, Safari, or Edge) Security Consideration...

NetSuite Is Killing TBA in 2027 - Here's How to Prepare

NetSuite Is Killing TBA in 2027 — Here's How to Prepare In a significant move that will impact many businesses and their integrations, NetSuite has announced the phasing out of Token-Based Authentication (TBA) by 2027. This decision marks a pivotal change in how users will authenticate and connect to NetSuite's services. As businesses increasingly rely on seamless integration for operational efficiency, understanding the implications of this transition and preparing adequately is crucial. Here’s everything you need to know about this change and a step-by-step guide on how to prepare. What’s Actually Happening? NetSuite is moving away from Token-Based Authentication due to evolving security standards and technological advancements. From 2027 onwards, new TBA integrations will not be allowed, and the use of TBA with SOAP web services will be phased out entirely by 2028. This aligns with a broader industry trend towards more secure and efficient authentication methods. Why the...

Guide to Creating Groups in NetSuite

Understanding and Creating Groups in NetSuite NetSuite, a leading cloud-based ERP solution, offers a handy feature called 'Groups' to streamline communication and collaboration within your business. A group in NetSuite is a set of employees, contacts, customers, partners, or vendors, created for the purpose of communicating with a certain set of individuals. For instance, you can create a group in your organization to share specific folders in the File Cabinet, invite a group to a meeting, or even email a saved search to a group. There are two types of groups in NetSuite: 1. Static Group A Static group is stable in nature. You can manually add or remove members to this group. The membership of static groups does not change automatically. 2. Dynamic Group On the other hand, a Dynamic group is one whose membership changes dynamically to include anyone who meets the group's criteria. A saved search is created to pull all records of that search during the time of crea...