Verifying prerequisites

This topic describes the system and hardware requirements for this product.

File-AID/EX Execution Server

Hardware requirements	Processor: 3 GHz minimum; we recommend multiple cores or CPUs for better scalability and performance. Hard Disk: 700 MB minimum; additional disk space is required for extracting large sets of data and caching data from translation tables. Because fast I/O is critical for performance, we recommend solid-state drives or high-performance RAID arrays. RAM: 4 GB minimum
Operating systems	Microsoft Windows 8.1, 10, 11, Microsoft Windows Server: 2012, 2016, 2019, 2022, 2011 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, 2.5

Data Studio 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, 11 Microsoft Windows Server 2012, 2016, 2019, 2022, 2011
Notes	BMC requires that all current maintenance be applied to the companion products. To use the latest 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, 11 Microsoft Windows Server 2012, 2016, 2019, 2022, 2011

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

Hardware requirements	Hard Disk: 150 MB
Operating systems	IBM z/OS V2.3, 2.4, 2.5 (z/OS UNIX for File-AID Rules Engine)
Java Runtime Environment	IBM Java 31-bit SDK V11.0 if using File-AID V21 IBM Java 64-bit SDK V11.0 if using File-AID V21

Corequisites

BMC AMI Common Enterprise Services (CES) 19.05.01 or higher
Enterprise Common Components 21.1
File-AID Common Components 21.1
File-AID for Db2 21.1
File-AID for IMS 21.1
File-AID/RDX 21.1
File-AID/Data Solutions 21.1

Tip

Day one support for IBM hardware and software is for toleration-only. For more information about day-one support, contact BMC Support.

Network configuration

Port numbers

The following port numbers, represent the default designation. To change the default, see the appropriate documentation and the case comments.
Valid port numbers for all BMC AMI DevX ports are from 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

HTTPS Port 3081 — HTTPS communication between File-AID Services and Workbench for Eclipse Client, for editing and saving Data Privacy Projects and assets. To receive metadata from and send criteria response to File-AID Rules Engine (FARE), regardless of distributed or z/OS UNIX platform.
HTTP Port 4180 — HTTP communication to FAS for Data Privacy execution, to receive metadata from and send criteria response to File-AID Rules Engine (FARE), regardless of distributed or z/OS UNIX platform. We strongly recommend users to use the https port in place of the http port.
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): Workbench for Eclipse 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 Workbench for Eclipse Server.