Portal - TimeXtender Training

COURSE OVERVIEW

Photo of Triangle Shape Digital Wallpaper

Training Module:

Portal

Web-based configuration and administration of your Instances, Data Source connections, and User Access

Prerequisites

To complete this module you will need to have a data storage resource such as On-Prem SQL Server, Azure SQL Database or Data Lake Storage Account.

Sandbox

For a quick and easy way to setup SQL Server Developer edition for TimeXtender for non-production use, create a sandbox.

Reference Architecture

If you already have a SQL environment ready, or would prefer a more production-ready environment please review and configure one of our preferred reference architectures: On-Prem SQL Server, Azure SQL Database or Azure Synapse Dedicated SQL Pool.

Anatomy of a TimeXtender data estate

1. The ODX Server

Windows-based server software installed on a centrally located physical or virtual machine. This software orchestrates the ingestion of data from various sources. This separates data movement from the desktop software, while ensuring data never leaves a users environment.

2. The ODX Storage

A SQL database or Azure Data Lake where raw data is stored after ingestion from sources. By storing data in it's raw form, it can be used for later analysis, or retrieval.

3. The MDW Storage

A SQL Database or Synapse Dedicated SQL Pool where data from multiple sources is cleansed, transformed, and consolidated into a single version of truth.

4. SSL Endpoints

A subset of related data combined into a single model or "mart". This model can be exported to multiple endpoints such as Power BI, Qlik, Tableau, Analysis Services, or CSV.

5. TimeXtender Portal

A web portal handling the administration of your TimeXtender Data Estate. Instances hold the storage connection details as well as maintain the configuration information implemented in TimeXtender Desktop.

6. TimeXtender Desktop

Windows-based Desktop-client software where each instance can be configured & implemented through a single, integrated user-interface.

Client-Server Setup

When working in a sandbox environment, the Desktop and Server software can be installed, run, and controlled all from the same machine.

However, in production-ready setups, multiple concurrent users are necessary. Ideally, each client runs their own local instance of TimeXtender Desktop and connect remotely to the ODX Server.

Please note: With a client-server setup, the ODX Server IP Address or Hostname must be "reachable" by each client machine. More Info.

Server software should be installed on a centrally located server so it can be controlled by multiple clients.

Each TimeXtender user should install and use TimeXtender Desktop on their own "client" machine

Sign-in or Sign-up Free

To access the TimeXtender Portal, simply go to app.TimeXtender.com and sign-in.

But what if I don't already have an account?

Partners

As a Partner, you get free access to the Premium tier. Check your inbox for an invitation.
If you don't already have access, reach out to your solution specialist or company admin to get partner-level access.
If you don't know your solution specialist or company admin, email support@timextender.com

Customers

If you don't already have access, reach out to your partner or company admin to get user access to your customer account.

Sign-up Free

TimeXtender is Free. To sign-up, just go to app.TimeXtender.com and click Start Free

What's an Instance?

Instances are the metadata components of your TimeXtender Data Estate.

They store the connection info to the associated target storage.
They contain the metadata for how this area of TimeXtender is configured. (e.g. What tables are selects in an ODX Data Source, What relations & transformations exist in your MDW, etc.)
They maintain versioning, so each individual instance can be rolled back a previous version.
Any instance can be copied to another instance of the same type. Allowing you to migrate your instance configuration to another storage type or environment.
All credentials entered in the portal are protected with 256 bit AES encryption.

Add odx instance

This is the the Username and Password created when you setup SQL Server in your Sandbox.

(the default System Administrator account Username is SA)

Click Data Estate > Instances
Click Add Instance > Add ODX
Enter Instance Name and Description
Storage Info

Select Storage Type > SQL database storage
Enter Server Name: localhost
Enter Database Name: ODX Dev
Enter Username: SA
Enter Password

ODX Server Connection info

Enter IP or Hostname: localhost

Click: Save

It is not necessary for the database to exist at this point. We will have TimeXtender create them later.

This is the the IP Address or Hostname of the machine where the ODX Server software is running. See Client-Server Setup above...

Add MDW instance

Click Data Estate > Instances
Click Add Instance > Add Data Warehouse
Enter Instance Name and Description
Storage Info

Select Storage Type > SQL database storage
Enter Server Name: localhost
Enter Database Name: MDW Dev
Authentication > SQL Server Authentication
Enter Username and Password

Click: Save

This is the the Username and Password created when you setup SQL Server in your Sandbox.

(the default System Administrator account Username is SA)

It is not necessary for the database to exist at this point. We will have TimeXtender create them later.

Add SSL instance

Click Data Estate > Instances
Click Add Instance > Add Semantic Model
Enter Instance Name and Description
Add an Endpoint

Endpoint Type > CSV Endpoint
Click: Add
Enter Name: CSV Endpoint
Enter Directory: C:\SSL
Enter File Extension: CSV

Click: Save

Add Data Source connection

Data Source Connections are added and stored here in the portal. They can then be easily copied and/or mapped to an ODX Instance for later configuration in TimeXtender Desktop.

All credentials entered in the portal are protected with 256 bit AES encryption.

Click Data Estate > Data Sources
Click: Add Data Source
Choose Data Source > TimeXtender SQL Data Source
Enter Name and Description
Enter Server: txtraining.database.windows.net
Enter Database: AdventureWorks
Authentication > SQL Server Authentication
Enter Username: txlogin
Enter Password: TimeXtenderRocks!
Check the box for Trust server certificate
Click: Add

What's adventureWorks?

This training uses the AdventureWorks sample database. For training purposes, we host a fully managed version of this database which you can access with the below connection details:

Server: txtraining.database.windows.net
Database: AdventureWorks
SQL Server Authentication
Username: txlogin
Password: TimeXtenderRocks!

You may also download and explore your own copy of the database from Microsoft here:

AdventureWorks sample databases.

AdventureWorks is a commonly used sample dataset that closely represents common online transactional processing (OLTP) systems. It is based on a fictitious manufacturer and distributor of bicycles, outdoor equipment, and apparel. In this training we will perform common extract, transform, and load (ETL) techniques on this data. To become more familiar with the dataset, click to expand and explore the AdventureWorks entity relationship diagram.

MAP Data Source

By Mapping a Data Source to an ODX instance you are specifying which ODX should be allowed to connect and transfer this source data. This will be useful later when you have multiple ODX instances.

Click Data Estate > Instances
Click: ODX Dev
Scroll to Mapped Data Sources section and click: Add
Data Source > Adventure Works
Click: Add

ADD USERs

Optional

Users can be added here in the portal and mapped to a specific instance. When these users log into TimeXtender Desktop, they will only be able to access the instances which they have been mapped to.

Add User