Dashboard > Appistry EAF v3.5 > ... > Installing the Fabric > Fabric Worker CentOS, RHEL, and SUSE installation
Log In   View a printable version of the current page.  
  Fabric Worker CentOS, RHEL, and SUSE installation

Fabric Worker

The worker installation installs the application fabric and administrative utilities on a single worker.

The installation steps described here are appropriate for manually installing:
  • single worker fabrics (such as on a developer's workstation)
  • small multi-worker fabrics being used for evaluation, development, testing, or small production environments
  • a single worker as a preparation step for setting up for using the fabric assimulation features.
The Appistry EAF installation and basic configuration consists of the following procedures.
What about installing larger fabrics, and the fabric assimulation feature?

For information on automating the installation and configuration of fabric workers using the fabric assimulation feature, please refer to Worker Assimilation.

Prepare for installation

If installing fabric workers for production, test, or development Fabrics

    We assume the following:

  • The fabric is segmented from the network by a firewall that restricts MCAST communication.
  • The fabric is on a single network switch.
  • The client and workers are on the same network segment.
  • The operating system is already installed. 
If installing fabric workers on developer workstations, or for an evaluation fabric

    We assume the following:

  • The client and workers are on the same network segment.
  • The operating system is already installed. 

    Personal firewalls
    Personal firewalls, such as Norton Internet Security and Zone Alarm, are known to interfere with fabric communication. Please disable all personal firewalls.
If Java is installed on your system, and you intend to package, deploy, and run Java fabric tasks, verify the following
  • The JAVA_HOME environment variable exists and is set correctly in .bash_profile.
  • For Java JDK
    • PATH includes $JAVA_HOME/bin
    • LD_LIBRARY_PATH includes $JAVA_HOME/lib/i386:$JAVA_HOME/lib/i386/client
  • For Java JRE
    • PATH includes $JAVA_HOME/jre/bin
    • LD_LIBRARY_PATH includes $JAVA_HOME/jre/lib/i386:$JAVA_HOME/jre/lib/i386/client
Set the fabric's logical location
  1. Open a new file in a text editor and type the following where <MulticastAddress> is the desired MCAST address of the fabric. 
    fabric-address=<MulticastAddress>
fabric-address=239.255.0.2
    What about this fabric MCAST address?
    Each fabric is assigned a unique MCAST address. Fabric clients and utilities (like Log Monitor and Fabric Control) use this MCAST address to communicate with the fabric. This address defaults to 239.255.0.1, but can be changed by setting the fabric-address property in the addr.cfg file that is deployed to all fabric workers. The fabric MCAST address specified by clients and utilities must match the fabric-address entry in the addr.cfg or 239.255.0.1 if using the default. As you go through command and code samples, please be sure to use the correct fabric MCAST address for your installation.
  2. Type the following where <port> is the port fabric_ctl uses to connect to the fabric. 
    admin-port=<port>
admin-port=30000
  3. Type the following where <request_port> is the port used for request member communication. 
    request-port=<request_port>
request-port=31000
  4. Save the file as addr.cfg.install.
  5. Move the addr.cfg.install file to the /etc directory.

Install Appistry EAF on a worker

During the installation, Appistry EAF creates a user for administering the fabric. The user name is fabric-admin and the password is fabric-admin . Appistry recommends changing the fabric-admin password after rebooting the worker.

  1. Obtain the AppistryEAF-<version>-<build datetime>.1386.rpm file and copy it to the worker.
    • If you are installing Appistry EAF from a CD, place the Appistry EAF CD into the CD-ROM drive, mount the drive and copy the file.
  2. Go to the directory holding the AppistryEAF-<version>-<build datetime>.1386.rpm file.
  3. On the command line, type the following command with the correct installation filename. 
    rpm -i AppistryEAF-<version>-<build datetime>.1386.rpm
    • The following things occur during installation
      • Installs Appistry EAF worker into /usr/local/fabric.
      • Sets up initialization and termination scripts for init.d for fabric_keeper and fabric_system_service.
      • Creates user fabricuser and group fabricuser.
      • Assigns ownership on /usr/local/fabric to fabricuser:fabricuser.
      • Copies user supplied /etc/addr.cfg.install file to /usr/local/fabric/system/staging/addr.cfg.
      • Installs the file /etc/fabric_env, which is used to set the FABRIC_HOME, PATH, JAVA_HOME, and, LD_LIBRARY_PATH environment settings for the fabric services.
  4. If you intend to have additional fabric users working locally on this worker box
    • you must set the FABRIC_HOME environment variable locally for that user's environment. The default FABRIC_HOME setting is /usr/local/fabric/system.
    • for a user other than "fabricuser" to use the fabric utilities on this worker box, you must set their environment to reflect the values in /etc/fabric_env (in addition to FABRIC_HOME).
  5. If Java is installed, and you intend to use Java fabric tasks
    1. open the file /etc/fabric_env and
    2. verify that the JAVA_HOME variable in the /etc/fabric_env file points to Java's location.
    3. uncomment the last 3 lines in the file, and confirm the correct LD_LIBRARY_PATH settings (particularly for differences between JRE and JDK paths).
      "Java Settings"
      If you intend to use Java fabric tasks, it is important to make sure that the settings in the /etc/fabric_env file are correct. If they are not, the Fabric will not load Java and consequently, Java fabric tasks will not work.
  6. Reboot the worker.

Deploying the license key

You must deploy the license key

The fabric will not run without a valid license key. You are required to deploy the license.cfg file.
Before deploying the fabric application package, verify the following.
  • The fabric is running. If the fabric is not running, refer to Installation for instructions.
  • The Log Monitor is running in a separate window or terminal. To start the Log Monitor run the following command with the correct fabric MCAST address. 
    log_monitor 239.255.0.1:4000
    What about this fabric MCAST address?
    Each fabric is assigned a unique MCAST address. Fabric clients and utilities (like Log Monitor and Fabric Control) use this MCAST address to communicate with the fabric. This address defaults to 239.255.0.1, but can be changed by setting the fabric-address property in the addr.cfg file that is deployed to all fabric workers. The fabric MCAST address specified by clients and utilities must match the fabric-address entry in the addr.cfg or 239.255.0.1 if using the default. As you go through command and code samples, please be sure to use the correct fabric MCAST address for your installation.
Deploying the License Key
  1. The Log Monitor will be displaying errors like the following: 
    Sep 27 12:14:10 00:00:00:00:00:00 FabricKeeper[E:7104] License Key Error: failed to load license file
  2. Change to the directory holding license.cfg file you received from Appistry.
  3. To deploy the license.cfg file, run the following command with the correct fabric administrative user, password, and fabric address. 
    fabric_ctl -d 239.255.0.1:30000 -u fabric-admin/fabric-admin deploy license.cfg
  4. Fabric control sends the license key file to the worker, and the fabric services will begin to startup. The Log Monitor will display a message like the following: 
    Sep 27 12:26:00 00:00:00:00:00:00 FabricKeeper[I:7108] Spreading file: license.cfg
  5. After a few moments, the fabric will be fully started.