Skip to main content
Skip table of contents

Admin: Google Datastore Configuration

Overview

This section describes how to prepare pre-requisites and configure data connections for the Google Datastore NoSQL auxiliary database.

Obtaining a Google Project ID

  1. In a web browser, log into the Google Cloud console at https://console.cloud.google.com.

  2. Select a project using the dropdown to the right of the Google Cloud Platform header.

    image-20250917-184901.png
  3. Once the selected project is displayed, take note of the currently selected project's ID, as it is required when configuring the Google Datastore connection in Server Workbench.

    image-20250917-184913.png

Configuring Google Application Default Credentials

  1. In the GCP console, go to the API Console Credentials page by navigating to APIs & services > Credentials.

  2. Select your project from the project drop-down.

  3. In the Credentials page, select the Create credentials drop-down, then the Service account key.

  4. From the Service account drop-down, select the App engine app default service account.

  5. For Key type, select the JSON key option, then select Create. The file is automatically downloaded.

  6. Place the downloaded *.json file into your preferred local directory location. The directory must be secure, but accessible to your web server code.

Creating a Google Credentials Environment Variable  

  1. Navigate to Windows Control Panel > System > Advanced System Settings > Advanced Tab > Environment Variables.

    image-20250917-184931.png
  2. In System Variables, add a new variable as follows:

    • Name: GOOGLE_APPLICATION_CREDENTIALS

    • Value: C:\[PATH TO PRIVATE KEY FILE]\<project id>-xxxxxxxxxxxx.json
      Note that the variable value must be set according to the actual directory location of the private key file. 

  3. Use the following connection string format when provisioning an auxiliary database connection utilizing Google DataStore in Server Workbench:
    {"ProjectId": "Project ID", "Namespace":"Database Name"}

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.