Administration Utilities

To aid in fabric administration, Appistry provides administrative utilities. The administrative installation enables you to install the administrative utilities on a workstation without installing a fabric. You may install these utilities on as many workstations as you wish. Please note that the fabric worker installers automatically install these utilities on a worker.

Topics 

• Installing the Administration Utilities

When should I use this installer? If you are going to perform a fabric worker installation on the target computer (or have already done so), you do not need this installer. The worker installation contains everything that the administrative and software development  kit installers do, and more. If you are setting up a developer workstation using the software development  kit installer, you do not need this installer. The software development  kit installer contains everything that the administrative installer does, and more. Basically, if you just need the administrative utilities alone, then this installer is for you.

Installing the Administration Utilities

If Java is installed on your system, and you intend to package, deploy, and run Java fabric tasks, you will want to do one of the following:

Automatic setup of Fabric Java environment

• Copy /etc/fabric_env to this system from a system that has a worker installation (not necessary if there is a worker installed on this system).
• Add ". /etc/fabric_env" to the user's .bashrc to setup their environment.

Manually setup the Fabric Java environment

• 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

Java Settings and Packaging If you intend to use the fabric administrative utilities to package fabric applications that include Java fabric tasks, it is important to make sure that the settings described above for the LD_LIBRARY_PATH are correct. If they are not, the Fabric Package command will not be able to validate the Java tasks during the packaging process, and will fail.

Proceeding with the administrative installation

1. Obtain the appistry-eaf-admin-<version>-<OS>.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 appistry-eaf-admin-<version>-<OS>.rpm file.
3. On the command line, type the following command with the correct installation filename.

   rpm -i appistry-eaf-admin-<version>-<OS>.rpm

   • The following things occur during installation
     • Installs Appistry EAF administrative tools into /usr/local/fabric.
4. If you copied /etc/fabric_env to this system (or a worker installation already resides on this system)
   • Add ". /etc/fabric_env" to your .bashrc
     or
   • Make the following changes to your .bashrc or .bash_profile
   • Set the FABRIC_HOME environment variable. The default FABRIC_HOME setting is /usr/local/fabric/system.
   • Add FABRIC_HOME to both your PATH and LD_LIBRARY_PATH