Prerequisites

Make sure that all the prerequisites are met before you install Z Refactoring Assistant.

CPU, RAM, and storage requirements

  • CPU: 4 cores
  • RAM: 16 GB
  • Disk: 500 GB

Supported platforms and versions

  • Red Hat® Enterprise Linux® version 8 or later on an AMD64 system

Prerequisite software

  • Required tools and packages
    • podman version 4 or later
    • podman-plugins package
    • openssl command
    • keytool command (from Java 8 or higher Runtime Environment)
  • Network access to IBM® Application Discovery and Delivery Intelligence for IBM Z® (IBM ADDI)
    • Version 6.1.3 or later
  • Supported Internet browsers (used for accessing Z Refactoring Assistant)
    • Google Chrome (recommended)
    • Mozilla Firefox
    • Microsoft Edge

Configuring IBM ADDI for Z Refactoring Assistant

Z Refactoring Assistant uses IBM ADDI's Authentication Server (DEX). Before you install Z Refactoring Assistant, you need to configure IBM ADDI to recognize Z Refactoring Assistant as a valid client first.

To configure IBM ADDI for Z Refactoring Assistant, complete the following steps:

  1. On the IBM ADDI host where DEX is running, edit the <IBM_ADDI Installation Folder>/Authentication Server (DEX)/conf/dex.yaml file with the following changes:
    • Add the following entry to the list of static clients:
      staticClients:
      - id: refactoring-assistant
        name: Z Refactoring Assistant
        redirectURIs:
        # List of locations where Z Refactoring Assistant runs, e.g. https://localhost:9443 or https://linuxvm.mydomain.com:9443
        - << URL >>
        secret: pkce
    • Optional: The credentials that are configured in DEX are the same ones that you use to log into Z Refactoring Assistant. However, for evaluation purposes only, you can enable a test user with the following credentials.
      • User ID: tester@demo.ibm.com
      • Password: password
      To enable the test user, add the following entry to the list of static passwords:
      staticPasswords:
      - email: tester@demo.ibm.com
        hash: $2a$12$m2dGtrCtc320uPbjgIOydeYxjePRhPU3WZ34z4CF.iK7oiYcEwRwe
    • To enhance your security with DEX, set the token expiration time in DEX to a shorter time, for example, 30 minutes:
      1. Locate the existing expiry entry in the dex.yaml file you use.
      2. Replace the value for idTokens with 30m as the following example:
        expiry:
          idTokens: 30m
  2. Restart DEX.