> [!CAUTION]
> **Caution:** This documentation covers Edge for Private Cloud 4.16.05, which is no longer supported. Google does not provide security patches, bug fixes, or technical support for this version. The current supported version is 4.54.00. See the [Edge for Private Cloud documentation](https://docs.apigee.com/private-cloud/latest/overview) for the current version, or [All versions](https://docs.apigee.com/private-cloud/versions) to compare releases.

*Edge for Private Cloud v. 4.16.05*

The checklist covers the preceding prerequisites and provides a list of required files to
obtain before proceeding. Here is a summary of the primary requirements covered there.

> [!NOTE]
> **Note:** If an older version of Apigee Edge for Private Cloud was installed on the machine, ensure that you delete the folder /tmp/java before a new installation.
>
> If user "apigee" was created prior to the installation, ensure that "/home/apigee" exists as
> home directory and is owned by "apigee:apigee".

- **Edge system administrator credentials** : As part of the installation, you are prompted to specify an email address and password used to create the Edge system administrator account. Never use these credentials for anything other than Edge system administration. You can later create different users and user types to create and manage API proxies, apps, and all other user-level tasks.   

  To change the administrator password do not use the Edge UI to change the administrator password. See [Resetting Edge Passwords](https://docs.apigee.com/private-cloud/v4.16.05/resetting-passwords) for more information.
- **OS** : For operating system requirements, see [https://apigee.com/docs/api-services/reference/supported-software](https://docs.apigee.com/release/supported-software).
- **Java** : Java requirements are covered under Prerequisites above. Refer to [https://apigee.com/docs/api-services/reference/supported-software](https://docs.apigee.com/release/supported-software).  

  Ensure that JAVA_HOME points to the root of the JDK for the user performing the installation.
- **Firewalls** : Firewall/host requirements are covered under Prerequisites above. See [Installation Requirements](https://docs.apigee.com/private-cloud/v4.16.05/installation-requirements) before proceeding.
- **TCP Wrappers** : TCP Wrappers can block communication of some ports and can affect OpenLDAP, Postgres, and Cassandra installation. On those nodes, check /etc/hosts.allow and /etc/hosts.deny to ensure that there are no port restrictions on the required OpenLDAP, Postgres, and Cassandra ports.
- **SELinux** : Depending on your settings for SELinux, Edge can encounter issues with installing and starting Edge components. If necessary, you can disable SELinux or set it to permissive mode during installation, and then re-enabling it after installation. See [Install the Edge apigee-setup utility](https://docs.apigee.com/private-cloud/v4.16.05/install-edge-apigee-setup-utility) for more.
- **iptables** : Validate that there are no iptables policies preventing connectivity between nodes on the required Edge ports. If necessary, you can stop iptables during installation using the command:  
  \> sudo /etc/init.d/iptables stop  

  On CentOS 7.x: \> systemctl stop firewalld
- **License file** : A valid license file must be obtained to install Apigee Edge. Licensing information is covered under Prerequisites above. Refer to [Installation Requirements](https://docs.apigee.com/private-cloud/v4.16.05/installation-requirements) before proceeding.
- **Distribution files**: The Apigee Edge distribution files are installed as a set of RPMs and dependencies.
- **System limits** :
  - On Cassandra nodes, set soft and hard memlock, nofile, and address space (as) limits for installation user (default is "apigee") in /etc/security/limits.conf as shown below:  
    apigee soft memlock unlimited  
    apigee hard memlock unlimited  
    apigee soft nofile 32768  
    apigee hard nofile 65536  
    apigee soft as unlimited  
    apigee hard as unlimited
  - On Message Processor nodes, set the maximum number of open file descriptors to 64K by using the command:  
    \> ulimit -n 65535  

    If necessary, you can raise that limit. For example, if you have a large number of temporary files open at any one time.
- **Disable DNS lookup on IPv6 when using NSCD**   
  If you have installed and enabled NSCD (Name Service Cache Daemon) you might notice that Message Processors make two DNS lookups: one for IPv4 and one for IPv6.  

  To disable the DNS lookup on IPv6:
  1. On every Message Processor node, edit /etc/nscd.conf.
  2. Set the following property:  
     enable-cache hosts no