Training Module:
Portal
Web-based configuration and administration of your Instances, Data Source connections, and User Access
Table of ContentS
Prerequisites & Concepts
go to Table of Contents
Prerequisites & ConceptS
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 set up SQL Server Developer edition for TimeXtender for non-production use, create a sandbox.
OR
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.
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
Customers
Sign-up Free
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 user's 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 its 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.
What's an Instance?
Instances are the metadata components of your TimeXtender Data Estate.
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.
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
Create Instances
go to Table of Contents
Add odx instance
This is the Username and Password created when you set up 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.
This is the IP Address or Hostname of the machine where the ODX Server software is running. See Client-Server Setup above...
Add MDW instance
This is the Username and Password created when you set up 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
Add Users
go to Table of Contents
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 USERs (Instance User Access)
OPtional
Add Data Sources
go to Table of Contents
Add Data Source: SQL Server
Required (Training Exercises use this data source)
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 into the portal are protected with 256-bit AES encryption.
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:
You may also download and explore your own copy of the database from Microsoft here:
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.
Add Data Source: CSV
OPtional
To learn more about data source connections, please check out Connect to CSV Data Sources.
Add Data Source: Excel
OPtional
To learn more about data source connections, please check out Connect to Excel Data Sources.
Add Data Source: Rest API (JSON)
OPtional
JSON, XML, CSV, and SOAP are supported connection types, with the RESTful API data source connections. To learn more about data source connections, please check out Connect to REST API Data Sources.
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.
Install & Configure:
TimeXtender Desktop and ODX Server
go to Table of Contents
Create ODX & MDW Storage
create storage
In this step you will have TimeXtender create the database (or data lake container) you specified when you created the instance in the portal.
Configure Firewall
OPtional
For more information and troubleshooting tips, please check out Configure Your Firewall.
TimeXtender Desktop | ODX Server | Additional Servers |
Instance databases:
| Updating CData components:
|
|
Client secret authentication, data sources provider download and updates:
| If using Azure Data Lake Storage
| |
Sign-in to Desktop, ODX configuration
| If using Azure Data Factory Data Sources
| |
Ensure that inbound rules are added for the ports used for the ODX instances |
Multiple Environments
go to Table of Contents
multiple enviRoNmentS
What are Multiple ENvironments?
TimeXtender supports multiple environment deployments that allow developers to create separate environments for development, testing, and production. These environments can be comprised of separate instances that can then be related to one another.
For example, a common configuration is to use three (3) environments, representing Development, Testing/User Acceptance, and Production, (a.k.a “Dev, Test, Prod”). By using three environments, we experience several benefits.
create New enviRoNment in Portal
Transfer instances
WARNING: Only tasks relating to one ODX instance can be added to a job. In other words, tasks from different ODX instances cannot be added to the same job.
For more information on tasks, see Multiple Environments.
Section Quiz...
Planning to take the Solution Architect exam? Then you want to be sure these questions are easy to answer.
What are the 6 components of a TimeXtender Solution?
What is a TimeXtender Instance?
How are my connection details kept private?
When you're ready, see Answers Below
Section Quiz Answers
Planning to take the Solution Architect exam? Then you want to be sure these questions are easy to answer.
What are the 6 components of a TimeXtender Solution?
What is a TimeXtender Instance?
The metadata components of a TimeXtender Data Estate.
How are my connection details kept private?
All credentials entered into the portal are protected with 256-bit AES encryption.
Congratulations! You've completed the training module
Portal