Library IP based redirection: If you are going be using Library based redirection then copy a preconfigured lib_ips.txt file to the /home/gpls/GenaSYS-2.1.1/custom folder before continuing.

Note: this is the file that allows in-library OPAC stations to default to their location as opposed to all of PINES.

Zip Codes for libraries: If you are using mutliple zip codes for libraries copy a preconfigured zips.txt file to the /home/gpls/GenaSYS-2.1.1/custom folder before continuing.

Note: this file allows the staff client to automatically populate the city, county, and state fields once the ZIP code is entered in the Evergreen User Editor.

Action Trigger Filters: If you are using customized action trigger filters then copy the custom action_trigger_filters.json file to the /home/gpls/GenaSYS-2.1.1/custom folder before continuing.

Note: this file is required for any custom action/trigger event setups that are configured.

Custom Maintenance Page: If you are using a customized maintenance page then copy the custom index.html or index.php file and any image files .jpg or .png to the /home/gpls/GenaSYS-2.1.1/custom folder before continuing.

Note: the maintenance page appears when you detach all bricks from the cluster.

This is where the DNS name for your cluster is entered.

An SSL Certificate is required for Evergreen to function correctly. If you have purchased a certificate from a CA then please copy the certificate files (server.crt, server.key and ca.crt if applicable) to /home/gpls/GenaSYS-2.1.1/ssl_cert. If you do not have a purchased certificate from a CA, GenaSYS will generate a self-signed certificate automatically.

Where you define the number and configuration of . GenaSYS automatically sets up brick clustering and management scripts.

This step defines on which server the NFS share for reports outputs resides. The reports process itself is located on reporter01.

This step creates the Linux "opensrf" user, which is used by the system to run all OpenSRF processes, including Apache.

This step creates the password for the PostgreSQL "evergreen" user.

This step creates the Evergreen administrative user, which is able to log into the staff client with these credentials and administer the system from the GUI.

Default is 10.0.1.0/24, but can be anything within the private network IP range.

You will then be shown a summary of the configuration options that you’ve chosen as they are entered into the genasys.conf file. If any values need correcting, you can start over by selecting ®etry.

Messages will appear on the screen as the files are processed.

After the files are processed and packaged, you will be shown a summary of the full cluster configuration, including installation instructions. This information will be stored in a file named [cluster name]_network_config.txt. As it contains the entered passwords in clear text, you will want to secure this file.\

Copy the setup tar.gz files one at a time to the respective nodes in the cluster, extract and run the installation and reboot each one before starting on the next one. Install in the order listed below.