Milestone 1: Prerequisites

System and Hardware Requirements

This section provides information about the following topics:

File-AID/EX Execution Server
File-AID/EX Enterprise Edition (File-AID/EX Executive)
Topaz for Enterprise Data Client
File-AID Services
File-AID Rules Engine (FARE) on z/OS UNIX
Corequisites
Network Configuration

File-AID/EX Execution Server

Hardware Requirements	Processor: 3 GHz minimum; multiple cores or CPUs are recommended for better scalability and performance. Hard Disk: 700 MB minimum; additional disk space is required for extracting large sets of data, caching data from translation tables, and so on. Fast I/O is critical for performance, so solid-state drives or high-performance RAID-arrays are recommended. RAM: 4 GB minimum
Operating Systems	Microsoft Windows 8.1, 10 Microsoft Windows Server 2012, 2016, 2019 Red Hat Enterprise Linux 6.10, 7.7, 8.0, 8.2

File-AID/EX Enterprise Edition (File-AID/EX Executive)

Operating Systems	IBM z/OS V2.3, 2.4

Topaz Enterprise Data Client

Hardware Requirements	Distributed Systems: Processor: 3 GHz minimum Hard Disk: 1 GB minimum Memory: 4 GB minimum
Operating Systems	Microsoft Windows 8.1, 10 Microsoft Windows Server 2012, 2016, 2019
Notes	Compuware requires that all current maintenance be applied to the companion products. In order to use the newest features, any specified PTFs must be applied; otherwise, companion products will operate in toleration mode and new features will be disabled.

File-AID Services

Hardware Requirements	Processor: 3 GHz minimum Hard Disk: 1 GB (for executables and Derby database) RAM: 4 GB minimum
Operating Systems	Red Hat Enterprise Linux 6.10, 7.7, 8.0, 8.2 Microsoft Windows 8.1, 10 Microsoft Windows Server 2012, 2016, 2019

File-AID Rules Engine (FARE) on z/OS UNIX

Hardware Requirements	Hard Disk: 150 MB
Operating Systems	IBM Mainframe IBM z/OS V2.3, 2.4 (z/OS UNIX for File-AID Rules Engine)
Java Runtime Environment	IBM Java 31-bit SDK V8.0 or higher (only 31-bit Java is supported on z/OS Unix)

Corequisites

Enterprise Common Components 16.5, 17.2
File-AID Common Components 17.2
File-AID for DB2 17.2
File-AID for IMS 17.2
File-AID/RDX 17.2
File-AID/Data Solutions 17.2

Day one support for IBM hardware and software is for toleration-only. Refer to the Compuware Support Center for more information on day one support.

Network Configuration

The following port numbers, represent the default designation. To change from the default, refer to the appropriate documentation and the case comments.
Valid port numbers for all BMC Compuware ports, include 1 through 65,535. All ports are for bi-directional communication, unless noted otherwise.

FA/EX port numbers:

File-AID Executive: Mainframe Port 2600 (initial task: DCLE, default clone task name: DCLECL). TCPIP open socket communication, for FA/EX execution server to access mainframe data on z/OS, via the MVS Executive.
Execution Server: FA/EX Server (local/remote) machine port 4900 (for TCPIP open socket communication from FA/EX Communication Manager).
Communication Manager: FA/EX client machine port 4901 (for TCPIP open socket communication from FA/EX client).

FAS port numbers:

Server: FAS machine port 3081 - HTTPS communication between File-AID Services and Topaz Workbench Client, for editing and saving Data Privacy Projects and assets.
Data Privacy execution: FAS machine port 4180 - HTTP communication for FAS to receive metadata from and send criteria response to File-AID Rules Engine (FARE), regardless of distributed or z/OS UNIX platform.
FA/Data Solutions interface: FAS machine port 5180 - HTTP communication for FA/Data Solutions to request and receive list of Data Privacy Repositories and Projects, from FAS.
FAS notification messages (one-way): Topaz Workbench client machine port 4082 - for handling notification messages. This is currently used by FAS to send job completion notifications to the client, where the job was submitted via a host connection specified on the BMC Compuware Workbench Server.