Task 5.3 Install File-AID Rules Engine (FARE) on z/OS Unix
This task is only required if you plan to use the File-AID Data Privacy plug-in to disguise z/OS data using the BMC's File-AID mainframe products running on z/OS. A z/OS UNIX console tool (for example, TELNET or OMVS) must be used to install the FARE.
- If using OMVS as a console to z/OS UNIX, be sure your TSO region size is large enough to run Java. Also make sure that the ASSIZEMAX setting for OMVS segment is sufficient for running Java. This setting limits the maximum address space size, and the installation requires it to be at least 256m. The current value can be checked by executing the command ulimit -a.
- The FARE requires a minimum of 150MB of space — ensure there is sufficient space in the upload and target directories to contain the files.
- The user ID must have a default OMVS segment (or equivalent) specifying a valid, non-zero z/OS Unix user ID (UID), home directory, and shell command. The user ID should have authority to write to at least two directories — one directory to contain the install files and the other for the FARE files. Each directory requires sufficient space to contain the installation files or the installed software.
To install the FARE in z/OS UNIX on a target LPAR.
Run setup.exe on File-AID Services media image downloaded from an electronic distribution order, or from the Data Studio media.
- Select the File-AID Rules Engine tab in the media browser and select the Install File-AID Rules Engine for z/OS UNIX button.
Use the built in FTP facility to transfer the FARE installer files to z/OS UNIX. Supply the host, user ID, password, and the target path name of an existing z/OS UNIX directory. Select the Upload Files to the Mainframe button to initiate the FTP transfer.
- In z/OS UNIX, locate the path to a current Java Virtual Machine (JVM). The File-AID Rules Engine requires Java JRE 1.8. (For example: /usr/lpp/java/java8). For validation purposes, execute the shell command:
[path]/bin/java -version (where [path] is the path name to the JVM —for example: /usr/lpp/java/java8/bin/java -version). - Execute the installer by issuing the shell command: sh installfare.sh.
- If you do not have a supported JVM, you will be prompted to provide the directory path to the current Java Virtual Machine (JVM) you located as part of Step 4.
Accept the default installation destination path (/opt/BMC/fare) or specify a path to which you have write access and has at least 150MB of free space.
- Specify whether you will be working with Oracle databases. If you select Yes, you will be asked to accept the Oracle license agreement.
(For Windows) Specify whether you will be working with IBM Db2 databases. If you select Yes, you will be asked to supply the pathname to the folder containing IBM Db2 JDBC driver file db2jcc.jar and the corresponding appropriate license files for Db2 UDB on z/OS.
(For Mainframe) Use the DB2 drivers and license files that reside in the IBM jdbc/classes directory. If you are using DB2 12, note that drivers and license files are located at /usr/lpp/db2c10/jdbc/classes.
Task 5.3.1 Add Database Drivers for File-AID Rules Engine (FARE)
If you did not select a database type during the initial installation and now find the need to configure a database, you need only rerun the FARE installation (as described in ), this time making sure you select the drivers you need. If you are using the IBM Db2 driver you will be prompted to supply the location of the folder containing the Db2 JDBC driver file db2jcc.jar and the appropriate corresponding license files for Db2 UDB on LUW and/or z/OS. Read permissions must be granted on the drivers for FARE to load them.
The following types of database drivers can be installed on the FARE:
- Derby (installed by default and required for Data Privacy security database)
- IBM Db2: For more information, refer to the following documentation provided by IBM:
- Oracle
- Microsoft SQL Server and Sybase
Task 5.3.2 Configure Data Studio Components on Mainframe
Refer File-AID Installation and Configuration Guide:
- For New Installations, refer to the information about configuring Data Studio’s Data Privacy Environment.
- For Upgrades, refer to the information about updating Data Studio’s Data Privacy Environment.
- Then refer to the milestones for finalizing configuration and preparing for Workbench for Eclipse integration.