Using the ODX
In the Discovery Hub architecture, the ODX - Operational Data eXchange - is where data comes in from sources. In TimeXtender, the ODX layer is implemented as a stand-alone server that is optimized for handling very big amounts of data. In this chapter, you will learn how to set up and manage an ODX server.
The Structure of an ODX
The illustration below illustrates the different parts that make up the ODX part of the Discovery Hub architecture.
The ODX server sits in the middle of it all and copies data from data sources to a data storage, which can both be on-premise or in the cloud, and, when requested by TimeXtender, on to modern data warehouses.
For storing meta data about sources and storages as well as the tasks it needs to run, the server uses a local backlog that is continuously synced with the cloud repository. The cloud repository is divided into projects. Each ODX server has one project open at a time and two ODX servers should never use the same project at the same time.
The repository is not tied to a specific license. Instead, each company has one shared repository managed by TimeXtender. The ODX server gets the information it needs to connect to the cloud repository from the cloud service.
ODX is a client/server solution. The server runs as a service with no GUI. Once initial setup has been completed, management of the ODX server happens through the TimeXtender application that resides on the TimeXtender server.
If you want to manage an ODX server or simply use data from it in your data warehouse projects, you add the ODX server in Options in TimeXtender.
Installation of the ODX server is covered in the next section. To learn more about managing the ODX server, see Copying Data to the ODX. To learn more about using data from the ODX, see Copying Data from an ODX to a Data Warehouse.