Overview

Topaz Enterprise Data provides a single interface to visualize both mainframe and non-mainframe data in a common, intuitive manner, helping developers and data architects better manage both test and production data and meet the demands of digital business.

Product Architecture

Topaz Enterprise Data Architecture

Topaz Enterprise Data is a distributed product, which requires several separate components to be installed, typically on multiple networked computers. These components must then be configured to properly communicate among themselves and with other Compuware products. The above figure illustrates the relationships between the various components by breaking them into three logical layers (Client, Server, and Execution), based on their roles in the overall architecture.

Client Layer

The primary users of Topaz Enterprise Data work directly the applications from the Client layer. The Client layer contains the Topaz Workbench (with the Topaz Enterprise Data feature included), and several additional applications and utilities, such as ConverterPro, ComparePro, Homebase, Repository Management Utility, etc.

Server Layer

The Server layer contains one server application, File-AID Services (FAS). FAS is primarily responsible for management of Data Privacy projects, that include definitions of data elements, privacy rules, etc. Data Privacy projects and other privacy related artifacts are stored in the Data Privacy Rules Repository. During execution of data processing requests, FAS provides analysis of data layout(s) and detects which fields need to be disguised and which rules should be executed for which fields.

File-AID Services also serves as a hub for other Enterprise data components by sharing some configuration settings, such as the connection information to Compuware Enterprise Services (CES) and licensing configuration.

On Windows, File-AID Services installation also includes a separate Windows service, 'File-AID EX communication manager', which serves as a proxy in communication with the execution servers. It also provides access to the File-AID/EX repository, which stores definitions of requests and various artifacts that File-AID/EX works with, such as applications relationships or selection criteria.

There are two types of communication managers used by Topaz Enterprise Data:

• Local, which are installed as part of Topaz Workbench. Local communication managers are used by default and typically don't require any configuration. They are launched in a separate Windows process (named fa_commgr.exe), whenever it is required for communicating an execution requests or for browsing repository. Local communication managers define their own lists of connected repositories, including local (non-shared) repositories, and support communication with local (embedded into Topaz Workbench) execution servers.
• Shared, which are installed with File-AID Services (currently only on Window), as a separate Windows service. Shared communication managers provide access to all Enterprise Data clients to the same sets of repositories. They are also a good option for automated unattended execution of data processing requests, such as execution of Topaz for Total Test test-steps from a Topaz CLI environment. Note that shared communication managers cannot communicate with local execution servers (see below) and local repositories.

Execution Layer

The Execution layer contains the components required for execution of data processing requests. Topaz Enterprise Data supports two types of requests – mainframe and distributed.

The mainframe requests typically come from BMC Compuware File-AID mainframe products, such as BMC Compuware File-AID/Related Data XPERT, File-AID for Db2 or File-AID for IMS. To apply Data Privacy rules, the File-AID products launch File-AID Rules Engine (FARE), which runs in IBM Java Runtime Environment. FARE makes calls to FAS for instructions on which rules need to be executed, then applies those rules to certain fields.

The distributed requests are handled by File-AID/EX  execution servers, which can be installed on Windows or UNIX/Linux platforms. The Topaz Enterprise Data feature of Topaz Workbench includes a Local execution server, which is launched automatically when the local Topaz Enterprise Data applications need to communicate with it. Local execution servers are not intended for processing production data or automated (batch) executions, but rather for developing and debugging File-AID/EX specifications. Automated executions and processing of large volumes of data should be performed on "Standalone execution servers”, in which case they are running as a Windows service or a Unix daemon and can be shared by multiple users. To support data privacy, execution servers need to have the File-AID Rules Engine (FARE) installed.

A File-AID/EX execution server has the ability to access mainframe data via the (optional) File-AID/EXExecutive module.

File-AID/EX Scheduling Agent can be used for scheduling File-AID/EX (distributed) requests from the mainframe.